Cannot run dev locally

Also since Phoenix 1.5.4 changed a lot in LiveView. Would it be better to stick on 1.4.x in this current version?
Step 10/14 : RUN mix archive.install --force https://github.com/phoenixframework/archives/raw/master/phx_new.ez
 ---> Running in a8386d142f80
** (Mix) fetching from URIs require a checksum to be given

Could not run archive.install for:

    https://github.com/phoenixframework/archives/raw/master/phx_new.ez

Please download the file above to your current directory and run:

    mix archive.install ./phx_new.ez

You can download it either with your browser or via the command line.

On Unix-like operating systems (Linux, macOS):

    wget https://github.com/phoenixframework/archives/raw/master/phx_new.ez

or

    curl -o phx_new.ez https://github.com/phoenixframework/archives/raw/master/phx_new.ez

On Windows / PowerShell (Windows 7 or later):

    powershell -Command "Invoke-WebRequest https://github.com/phoenixframework/archives/raw/master/phx_new.ez -OutFile phx_new.ez"

or

    powershell -Command "(New-Object Net.WebClient).DownloadFile('https://github.com/phoenixframework/archives/raw/master/phx_new.ez', 'phx_new.ez')"

For anyone coming by this project in 2023,
I was able to get the build to run locally by replacing
RUN mix archive.install --force https://github.com/phoenixframework/archives/raw/master/phx_new.ez
in assets/ops/dev/Dockerfile
with
RUN mix archive.install hex phx_new 1.4.18


can't execute queries in v. 10 or 11 on Windows 10

Hi: i've downloaded v. 10 and 11 latest from github, and am able to establish an RDS connection to a postgres server on my network, but when I try to execute a query (any query) I get an error "TypeError: Cannot read property 'label' of undefined". I am guessing that there is a permissions issue reading or writing the settings file, but even if I try to run the app as administrator, I still get the same error?
I see that if I try to designate the save location for the json settings, it defaults to the "documents" folder of the current user, but it doesn't create the file. If I try to specify a different unprivileged location, it doesn't create the settings file there either. It DOES remember the database configuration when I exit and restart the app.

Hi thanks so much for using SeeQR! This is something we'll have to take a look it. I've noted it down for now. We do have certain files being defaulted to the temporary folder to save json configurations for your ERD layout. Like you said, it could be a permissions issue with RDS. We've just released a new version today with a lot of maintainability fixes. Hopefully this might've preemptively fixed the issue, but if not, we'll take tackle it on the next patch release.


Publish all BuildOutput as a pipeline artifact, to enable running additional tests in the future.

This change modifies the build pipeline to publish the entire BuildOutput folder as an artifact, so that we can download it later  in the test stage of the pipeline, and then push it over to Helix. (This is make enabling more tests in Helix easier in the future.)
This also removes the previous build artifact that was published containing the MRT Core test binaries, and uses the BuildOutput artifact instead for running the MRT cores.
(So this is doing both Step 1 & 2 together at the same time.)

/azp run


Formula change for CHEBI:78648 please

Dear ChEBI curators;
This CHEBI still has its old formula which lacks an R, can you please modify it so that we can balance the reactions in RHEA?
Thanks for your help,
Lucila

Dear ChEBI curators;
I just realized CHEBI:78648 might be the same as CHEBI:67090, can you double check and merge if necessary?
Thanks!
Lucila

Hi Lucila,
The entries have now been merged and the formula issue has been sorted. The parent ID is CHEBI:78648.
Kind regards,
Gareth


'View' button in staging CMS needs updating

The 'View' button in the staging CMS is still linking out to the production site. We'll need it to link to the preview of the page on staging instead so we can preview pages easily.
Image:

I've updated this, I imagine it had reverted after the new environments were set up.
It's a little tricky to find so for future reference this can be updated in the CMS by editing the root page (M+ Stories), under the Site Configuration tab you'll find a field called Website Base URL.

Thanks, @rdunk—working as expected. Closing ticket.
CC: @dianewang


Minimum graph for inference

Hello. Thank you for your great work. In nets/SqueezeDet.py we have:
self._add_forward_graph()
self._add_interpretation_graph()
self._add_loss_graph()
self._add_train_graph()
self._add_viz_graph()

What is the purpose of each of these graphs, and which is the minimum needed for inference? I am guessing it is the forward_graph. In this case, what would the names of the output nodes be? In https://github.com/BichenWuUCB/squeezeDet/issues/35, @Lisandro79 uses the following output nodes:
"bbox/trimming/bbox:0",
"probability/score:0",
"probability/class_idx:0"

These are from the interpretation_graph, not the forward_graph. I am making my own custom inference scripts. The speed of the model is not as fast as I would like following the procedure outlined in #35; SqueezeDet is slower than some much larger models I've tested. I think this is due to that I am not saving the correct and/or minimal graph for inference.
I am getting 550-600ms inference speeds (this does not include NMS time) on 512x512 realtime input (i.e., batch size of 1) on an NVIDIA TX2.

[UPDATE:] My questions about forward_graph and interpretation_graph still stand, but I have since been able to get much better performance speeds.
With default TF (roughly 18fps):
Took 0.0535703890491277 secs to perform forward pass
Took 0.024277875083498657 secs to perform NMS

And, with XLA JIT compilation (roughly 30fps):
Took 0.03044898994266987 secs to perform forward pass
Took 0.03193185699637979 secs to perform NMS

Thanks for your question and discovery about the JIT compilation.

self._add_forward_graph()
self._add_interpretation_graph()
self._add_loss_graph()
self._add_train_graph()
self._add_viz_graph()

Not all of them are related to inference. The minimal operations you need is defined in forward and interpretation graphs. You can try to delete others for inference speed purpose, but my understanding is that it should not matter. The inference output does not depend on those operations, they should not have been evaluated during inference.
Besides, you can also try to trim the graph using this function.
Last, NMS is not properly optimized. So if anyone could contribute or point us to an optimized NMS implementation, that would be great.

@villanuevab
Hi,villanuevab.
30 Fps is really amazing to me!
Would you please share something about how you modified the squeezeDet ? (code or tutorial)
I will be really greatful about that.
Best

(update)
I follow the tutorial given by tensorflow, and modify some lines in demo.py
from
    with tf.Session(config= tf.ConfigProto(allow_soft_placement=True)) as sess:
to
    config = tf.ConfigProto(allow_soft_placement=True)
    config.graph_options.optimizer_options.global_jit_level = tf.OptimizerOptions.ON_1
    with tf.Session(config=config) as sess:

and continuously detect 4 .png images and record the spending time info.
then I get :
Total time: 1.4299, detection time: 1.0560, filter time: 0.0094
Image detection output saved to ./data/out/out_000002.png
Total time: 1.5537, detection time: 0.0169, filter time: 0.0148
Image detection output saved to ./data/out/out_000003.png
Total time: 1.6881, detection time: 0.0158, filter time: 0.0105
Image detection output saved to ./data/out/out_000001.png
Total time: 1.8189, detection time: 0.0153, filter time: 0.0160
Image detection output saved to ./data/out/out_000004.png
but the xls jit code seems not working,  the spending time looks very close no matter weather I am opening the jit or not.
NEED HELP!
I am using a 4 TITANX server. and the following infomation during tranning are pested below.
ubuntu@ubuntu-Super-Server:~/LSJ_New/squeezeDet$ python ./src/demo.py
/gpu:1
2018-03-19 21:16:17.094741: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.1 instructions, but these are available on your machine and could speed up CPU computations.
2018-03-19 21:16:17.094794: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.2 instructions, but these are available on your machine and could speed up CPU computations.
2018-03-19 21:16:17.094816: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX instructions, but these are available on your machine and could speed up CPU computations.
2018-03-19 21:16:17.094822: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX2 instructions, but these are available on your machine and could speed up CPU computations.
2018-03-19 21:16:17.094827: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use FMA instructions, but these are available on your machine and could speed up CPU computations.
2018-03-19 21:16:17.435892: I tensorflow/core/common_runtime/gpu/gpu_device.cc:955] Found device 0 with properties:
name: TITAN X (Pascal)
major: 6 minor: 1 memoryClockRate (GHz) 1.531
pciBusID 0000:02:00.0
Total memory: 11.90GiB
Free memory: 11.25GiB
2018-03-19 21:16:17.741368: W tensorflow/stream_executor/cuda/cuda_driver.cc:523] A non-primary context 0x4b76ad0 exists before initializing the StreamExecutor. We haven't verified StreamExecutor works with that.
2018-03-19 21:16:17.742449: I tensorflow/core/common_runtime/gpu/gpu_device.cc:955] Found device 1 with properties:
name: TITAN X (Pascal)
major: 6 minor: 1 memoryClockRate (GHz) 1.531
pciBusID 0000:03:00.0
Total memory: 11.90GiB
Free memory: 11.75GiB
2018-03-19 21:16:18.055598: W tensorflow/stream_executor/cuda/cuda_driver.cc:523] A non-primary context 0x4b7aff0 exists before initializing the StreamExecutor. We haven't verified StreamExecutor works with that.
2018-03-19 21:16:18.056689: I tensorflow/core/common_runtime/gpu/gpu_device.cc:955] Found device 2 with properties:
name: TITAN X (Pascal)
major: 6 minor: 1 memoryClockRate (GHz) 1.531
pciBusID 0000:82:00.0
Total memory: 11.90GiB
Free memory: 11.75GiB
2018-03-19 21:16:18.395128: W tensorflow/stream_executor/cuda/cuda_driver.cc:523] A non-primary context 0x4b7f540 exists before initializing the StreamExecutor. We haven't verified StreamExecutor works with that.
2018-03-19 21:16:18.396372: I tensorflow/core/common_runtime/gpu/gpu_device.cc:955] Found device 3 with properties:
name: TITAN X (Pascal)
major: 6 minor: 1 memoryClockRate (GHz) 1.531
pciBusID 0000:83:00.0
Total memory: 11.90GiB
Free memory: 11.75GiB
2018-03-19 21:16:18.397531: I tensorflow/core/common_runtime/gpu/gpu_device.cc:847] Peer access not supported between device ordinals 0 and 2
2018-03-19 21:16:18.397561: I tensorflow/core/common_runtime/gpu/gpu_device.cc:847] Peer access not supported between device ordinals 0 and 3
2018-03-19 21:16:18.397611: I tensorflow/core/common_runtime/gpu/gpu_device.cc:847] Peer access not supported between device ordinals 1 and 2
2018-03-19 21:16:18.397644: I tensorflow/core/common_runtime/gpu/gpu_device.cc:847] Peer access not supported between device ordinals 1 and 3
2018-03-19 21:16:18.397677: I tensorflow/core/common_runtime/gpu/gpu_device.cc:847] Peer access not supported between device ordinals 2 and 0
2018-03-19 21:16:18.397706: I tensorflow/core/common_runtime/gpu/gpu_device.cc:847] Peer access not supported between device ordinals 2 and 1
2018-03-19 21:16:18.398768: I tensorflow/core/common_runtime/gpu/gpu_device.cc:847] Peer access not supported between device ordinals 3 and 0
2018-03-19 21:16:18.398805: I tensorflow/core/common_runtime/gpu/gpu_device.cc:847] Peer access not supported between device ordinals 3 and 1
2018-03-19 21:16:18.398924: I tensorflow/core/common_runtime/gpu/gpu_device.cc:976] DMA: 0 1 2 3
2018-03-19 21:16:18.398937: I tensorflow/core/common_runtime/gpu/gpu_device.cc:986] 0:   Y Y N N
2018-03-19 21:16:18.398945: I tensorflow/core/common_runtime/gpu/gpu_device.cc:986] 1:   Y Y N N
2018-03-19 21:16:18.398953: I tensorflow/core/common_runtime/gpu/gpu_device.cc:986] 2:   N N Y Y
2018-03-19 21:16:18.398972: I tensorflow/core/common_runtime/gpu/gpu_device.cc:986] 3:   N N Y Y
2018-03-19 21:16:18.398986: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1045] Creating TensorFlow device (/gpu:0) -> (device: 0, name: TITAN X (Pascal), pci bus id: 0000:02:00.0)
2018-03-19 21:16:18.398997: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1045] Creating TensorFlow device (/gpu:1) -> (device: 1, name: TITAN X (Pascal), pci bus id: 0000:03:00.0)
2018-03-19 21:16:18.399006: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1045] Creating TensorFlow device (/gpu:2) -> (device: 2, name: TITAN X (Pascal), pci bus id: 0000:82:00.0)
2018-03-19 21:16:18.399014: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1045] Creating TensorFlow device (/gpu:3) -> (device: 3, name: TITAN X (Pascal), pci bus id: 0000:83:00.0)
Total time: 1.4299, detection time: 1.0560, filter time: 0.0094
Image detection output saved to ./data/out/out_000002.png
Total time: 1.5537, detection time: 0.0169, filter time: 0.0148
Image detection output saved to ./data/out/out_000003.png
Total time: 1.6881, detection time: 0.0158, filter time: 0.0105
Image detection output saved to ./data/out/out_000001.png
Total time: 1.8189, detection time: 0.0153, filter time: 0.0160
Image detection output saved to ./data/out/out_000004.png

(update)
seem I haven't compile tenserflow from source and open the jit support. I follow the official guide and install tenserflow 1.0.0, and luckly it works. I see the speed up from about 0.026s to 0.017s in one Titanx GPU
BTW, I found that. hope can help someone.
https://github.com/tensorflow/tensorflow/issues/11730
done.


Update Master with Live

OPS Build status updates of commit 4194764:
:clock10: Preparing: average preparing time is 1 min(s) 27 sec(s)

OPS Build status updates of commit 4194764:
:clock10: Incremental building: average incremental building time is 3 min(s) 1 sec(s)

OPS Build status updates of commit 4194764:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

his/db2oledbv/installing-data-provider-version-6-0.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


feature/remove_find_circle

Nit: remove 'Find Helper Circle' from user drop down menu #173

LGTM!


Component | Stacked Bar, Groped Bar: Smarter bleed calculations

Fixes #178

When xDomain is set to a range that fits all the bars, the bleed spacing is still being applied:

Before

After

@reb-dev Great catch! The coded was not able to handle unsorted data. Fixed in the latest commit.


docs: Provide alternative login option to Azure CLI

I have had difficulty logging into Azure via the az login PowerShell command. Using the option --use-device-code was smooth and easy.
Adding this to the CLI install section to share this knowledge with others (and my future self). 😁
This PR includes the commit only for this issue and replaces https://github.com/MicrosoftDocs/azure-ai-docs/pull/61

#sign-off

#sign-off

@sdgilley
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

Could we proceed with merging this PR if no further changes are needed? If there are any additional changes or feedback required, please let me know. Thank you!

#sign-off


Скласти інтро

Скласти інтро (вступ), де в 2-4 реченнях описати, що замовник робить, що подобається робити, що хочеться робити краще, що важливо робити, тощо.

― I'm the most successful person ever to run for the presidency, by far. Nobody's ever been more successful than me. I'm the most successful person ever to run. Ross Perot isn't successful like me. Romney ― I have a Gucci store that's worth more than Romney. Sorry losers and haters, but my IQ is one of the highest ― and you all know it!  Nobody's ever been more successful than me. I'm the most successful person ever to run. Ross Perot isn't successful like me. Romney ― I have a Gucci store that's worth more than Romney. Sorry losers and haters, but my IQ is one of the highest ― and you all know it!


(MAINT) Fix postgres ENV variable

Using an ENV variable in the definition of another ENV variable in the
Dockerfile doesn't work as expected, as these values are interpreted at
build time, not run time.
Use the envsubst command to handle arbitrary ENV variables in
configuration files, like we do for all our other pupperware containers.
This adds a little size to the puppetdb image, but that's acceptable.
Also bump to the latest ssl.sh which supports DNS_ALT_NAMES, and plumb
that through with an empty default.

CLA signed by all contributors.


[Bug]: Command polybar-msg cmd quit does not work when monitor is disabled

Checklist

[X] I have read the appropriate section in the contributing guidelines
[X] I believe this issue is a problem with polybar itself and not a misconfiguration on my part
[X] I have searched for other open and closed issues that may have already reported this problem
[X] I have checked the known issues page for this problem.
[X] I have followed the debugging guide to narrow down the problem to a minimal config.

Steps to reproduce

Run polybar minimal & to spawn a bar
Run pgrep -x polybar to list polybar processes
Run ./polybar_test.sh to turn off the display, send a signal to terminate all bars and turn on the display again
Run pgrep -x polybar again to see that the polybar processes have not been terminated

Content of polybar_test.sh:
#!/usr/bin/env bash

xrandr --output DP-2 --off
polybar-msg cmd quit
xrandr --output DP-2 --auto

DP-2 should be replaced with the name of the connected monitor found from running xrandr
Minimal config
[bar/minimal]
enable-ipc = true
modules-center = text

[module/text]
type = custom/text
content = test

Polybar log
polybar|notice:  Parsing config file: /home/nilas/.config/polybar/config
polybar|trace: config_parser: Parsing /home/nilas/.config/polybar/config
polybar|info:  Created ipc channel at: /tmp/polybar_mqueue.2006
polybar|warn:  No monitor specified, using "DP-2"
polybar|info:  Loaded monitor DP-2 (1920x1080+0+0)
polybar|info:  Bar geometry: 1920x24+0+0; Borders: 0,0,0,0
polybar|trace: bar: Attach X event sink
polybar|trace: bar: Attach signal receiver
polybar|trace: controller: Install signal handler
polybar|trace: controller: Setup user-defined modules
polybar|info:  Starting application
polybar|trace: controller: Main thread id = 1
polybar|info:  Starting module/text
polybar|info:  Entering event loop (thread-id=1)
polybar|trace: module/text: Thread id = 2
polybar|info:  Eventqueue worker (thread-id=3)
polybar|trace: bar: Create renderer
polybar|trace: renderer: Get TrueColor visual
polybar|trace: renderer: Allocate colormap
polybar|trace: renderer: Allocate output window
polybar|trace: renderer: Allocate window pixmaps
polybar|trace: renderer: Allocate graphic contexts
polybar|trace: renderer: Allocate alignment blocks
polybar|trace: renderer: Allocate cairo components
polybar|trace: renderer: Load fonts
polybar|info:  Configured DPI = 96x96
polybar|warn:  No fonts specified, using fallback font "fixed"
polybar|notice:  Loaded font "fixed" (name=DejaVu Sans, offset=0, file=/usr/share/fonts/TTF/DejaVuSans.ttf)
polybar|info:  Bar window: 0x0e00002
polybar|trace: bar: Reconfigure window
polybar|trace: bar: Set window WM_NAME
polybar|trace: bar: Set window _NET_WM_WINDOW_TYPE
polybar|trace: bar: Set window _NET_WM_STATE
polybar|trace: bar: Set window _NET_WM_DESKTOP
polybar|trace: bar: Set window _NET_WM_PID
polybar|trace: bar: Map window
polybar|trace: bar: Draw empty bar
polybar|trace: bar: Setup tray manager
polybar|info:  Disabling tray manager (reason: missing `tray-position`)
polybar|info:  module/text: Rebuilding cache
polybar|trace: bar: Force update
polybar|info:  Redrawing bar window
polybar|trace: renderer: flush(2 geom=30x24+945+0, falloff=0)
polybar|trace: bar: Received expose event
polybar|trace: bar: Received expose event
polybar|trace: bar: Received expose event
polybar|notice:  randr_screen_change_notify (1920x1080)... reloading
polybar|trace: bar: Received expose event
polybar|trace: bar: Received expose event
polybar|notice:  Termination signal received, shutting down...
polybar|trace: controller: Uninstall sighandler
polybar|trace: controller: Detach signal receiver
polybar|trace: controller: Stop modules
polybar|info:  module/text: Stopping
polybar|trace: module/text: Release sleep lock
polybar|info:  Deconstruction of module/text took 0 ms.
polybar|trace: controller: Joining threads
polybar|trace: module/text: Deconstructing
polybar|trace: ipc: Removing file handle
polybar|info:  Waiting for spawned processes to end
polybar|info:  Re-launching application...
polybar|notice:  Parsing config file: /home/nilas/.config/polybar/config
polybar|trace: config_parser: Parsing /home/nilas/.config/polybar/config
polybar|info:  Created ipc channel at: /tmp/polybar_mqueue.2006
polybar|warn:  No monitor specified, using "DP-2"
polybar|info:  Loaded monitor DP-2 (1920x1080+0+0)
polybar|info:  Bar geometry: 1920x24+0+0; Borders: 0,0,0,0
polybar|trace: bar: Attach X event sink
polybar|trace: bar: Attach signal receiver
polybar|trace: controller: Install signal handler
polybar|trace: controller: Setup user-defined modules
polybar|info:  Starting application
polybar|trace: controller: Main thread id = 1
polybar|info:  Starting module/text
polybar|trace: module/text: Thread id = 2
polybar|info:  Entering event loop (thread-id=1)
polybar|info:  Eventqueue worker (thread-id=3)
polybar|trace: bar: Create renderer
polybar|trace: renderer: Get TrueColor visual
polybar|trace: renderer: Allocate colormap
polybar|trace: renderer: Allocate output window
polybar|trace: renderer: Allocate window pixmaps
polybar|trace: renderer: Allocate graphic contexts
polybar|trace: renderer: Allocate alignment blocks
polybar|trace: renderer: Allocate cairo components
polybar|trace: renderer: Load fonts
polybar|info:  Configured DPI = 96x96
polybar|warn:  No fonts specified, using fallback font "fixed"
polybar|notice:  Loaded font "fixed" (name=DejaVu Sans, offset=0, file=/usr/share/fonts/TTF/DejaVuSans.ttf)
polybar|info:  Bar window: 0x0e00002
polybar|trace: bar: Reconfigure window
polybar|trace: bar: Set window WM_NAME
polybar|trace: bar: Set window _NET_WM_WINDOW_TYPE
polybar|trace: bar: Set window _NET_WM_STATE
polybar|trace: bar: Set window _NET_WM_DESKTOP
polybar|trace: bar: Set window _NET_WM_PID
polybar|trace: bar: Map window
polybar|trace: bar: Draw empty bar
polybar|trace: bar: Setup tray manager
polybar|info:  Disabling tray manager (reason: missing `tray-position`)
polybar|info:  module/text: Rebuilding cache
polybar|trace: bar: Force update
polybar|info:  Redrawing bar window
polybar|trace: renderer: flush(2 geom=30x24+945+0, falloff=0)
polybar|trace: bar: Received expose event

Expected behavior
I expect the bar to be terminated
Actual behavior
The bar is not terminated
Window Manager and Version
i3-wm 4.20.1
Linux Distribution
Arch Linux 5.16.2
Polybar version
polybar 3.5.7

Features: +alsa +curl +i3 +mpd +network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) +composite +xkb +xrm +xcursor

Build type: Release
Compiler: /usr/bin/c++
Compiler flags: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions         -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security         -fstack-clash-protection -fcf-protection -Wp,-D_GLIBCXX_ASSERTIONS -Wall -Wextra -Wpedantic -O3 -DNDEBUG
Linker flags: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now

Additional Context / Screenshots
I have done the test both when using my window manager i3 and when starting a Xorg display server with only xterm. In both cases the bar fails to terminate. Only running the command polybar-msg cmd quit from the terminal successfully terminates the bar. Likewise if polybar-msg cmd quit is replaced with killall -q polybar in the script polybar_test.sh the bar will be successfully terminated.

That's interesting. IPC and monitor state shouldn't be related at all. What does the polybar_test.sh script print to the terminal when you run it in your scenario?

Successfully wrote "cmd:quit" to "/tmp/polybar_mqueue.4045"
notice: randr_screen_change_notify (1920x1080)... reloading
notice: Termination signal received, shutting down...
notice: Parsing config file: /home/nilas/.config/polybar/config
warn: No monitor specified, using "DP-2"
warn: No fonts specified, using fallback font "fixed"
notice: Loaded font "fixed" (name=DejaVu Sans, offset=0, file=/usr/share/fonts/TTF/DejaVuSans.ttf)

I think I see what's happening. The config you posted isn't the entire config you're using, right? Your polybar reloads whenever the screen configuration changes because screenchange-reload is set to true in the [settings] section.
The following things happen in this order:

The screen configuration is changed through xrandr
Polybar is notified of this change and initiates a restart because of the screenchange-reload setting.
polybar-msg writes the quit message into the IPC channel while polybar is shutting down but before the channel is deleted
Polybar finishes shutting down, deletes the IPC channel, restarts, and recreates the IPC channel. The pending quit message is lost.

This isn't a bug. Polybar correctly responds to the randr_screen_change_notify signal and restarts, it has no way of knowing that there is a quit message on the way.
The minimal example looks quite contrived, so I'm guessing your use-case looks a bit different. But in any case, you probably don't want screenchange-reload.

The config you posted isn't the entire config you're using, right?

That is true, I somehow overlooked the screenchange-reload setting. What you are describing is indeed what is happening. Commenting out the screenchange-reload setting fixed the problem. Thanks for the help!


Issue getting bitness on netBSD

A person I know is working towards getting this ported onto all of the BSDs. It looks like FreeBSD and DragonFlyBSD are already supported but there is some issues with bitness on NetBSD. It appears in bitness.rs it is just making a call out to the command line to run the
getconf LONG_BIT

On NetBSD, there is no field for that.
A possibly fix could be writing the portion for getting bitness in C and having rust call the C code. From my understanding, it bitness is just seeing the bit length of a "long" type in languages like C. A solution in C that rust could call would be
int get_bitness() {
  int long_length = sizeof(long);
  return long_length * 8;
}

Or possibly take advantage of something like this

#[cfg(target_pointer_width = "64")]
const VAL: u8 = 64;

#[cfg(target_pointer_width = "32")]
const VAL: u8 = 32;

#[cfg(target_pointer_width = "16)]
const VAL: u8 = 16;

Then match VAL


Recognize custom Firefox profile locations

Environment

Operating system (including version): macOS Ventura 13.3.1
mkcert version (from mkcert -version): v1.4.4
Server (where the certificate is loaded): n/a
Client (e.g. browser, CLI tool, or script): n/a

What you did
Ran mkcert -install
What went wrong
The above command was partially successful but returned an error regarding Firefox:
The local CA is already installed in the system trust store! 👍
ERROR: no Firefox security databases found

I believe this is due to how this script (line 19) assumes Firefox profiles are always located at ~/Library/Application Support/Firefox/Profiles. However, Firefox supports custom profile locations. On my machine, the profiles are located elsewhere. Instead of assuming the above path, the script should check the file ~/Library/Application Support/Firefox/Profiles/profiles.ini, which has the following pertinent sections:
[Profile1]
Name=Work
IsRelative=0
Path=/Users/philna/firefox_profiles/phil_work

[Profile0]
Name=Personal
IsRelative=0
Path=/Users/philna/firefox_profiles/personal

I would normally submit a pull request, but I have never used go before so I am not sure it would be very elegant. I can attempt if desired.

+1 in linux environments, firefox-esr uses ~/.mozilla/firefox-esr/ and currently mkcert checks ~/.mozilla/firefox/

FYI https://github.com/FiloSottile/mkcert/pull/566

in general it would be good to allow the developers to override data.  being able to manually provide things like profile dir and name of the CA would really help.


Fixes multiple iOS problems

Kinetic scrolling works now
viewport is not outside of view
viewport doesn't wrap when on small screen size

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks broke.

Comments from Reviewable


fail on ubuntu 22.04

Failed CC version check. Bailing out!
simple running of the script throws:
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
  You are using:           cc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0

Compiler version check failed:

The major and minor number of the compiler used to
compile the kernel:

gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38

does not match the compiler used here:

cc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

It is recommended to set the CC environment variable
to the compiler that was used to compile the kernel.

The compiler version check can be disabled by setting
the IGNORE_CC_MISMATCH environment variable to "1".
However, mixing compiler versions between the kernel
and kernel modules can result in subtle bugs that are
difficult to diagnose.

*** Failed CC version check. Bailing out! ***

make[2]: *** [/var/lib/dkms/nvidia/495.46/build/Kbuild:194: cc_version_check] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1900: /var/lib/dkms/nvidia/495.46/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.15.0-1021-gcp'
make: *** [Makefile:80: modules] Error 2

Environment

Operating system: ubuntu 22.04 from public gcp image ubuntu-2204-lts, (ubuntu-os-cloud project)
Graphics card: one v100 nvidia gpu
fresh created machine (happens everytime), apt-get update and upgrade do not solve the issue

To Reproduce
just create an ubuntu 22.04 machine and run the official recommended installation using this script
Solution
modified the script by adding --no-cc-version-check flag after sh NVIDIA-Linux-x86_64-470.103.01.run -s --dkms

An option here is to determine which gcc to intall based upon
$ cat /proc/version
Linux version 5.15.0-1021-gcp (buildd@lcy02-amd64-108) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #28-Ubuntu SMP Fri Oct 14 15:46:06 UTC 2022
$ apt install gcc-11-base=11.2.0-19ubuntu1
...

the last command forces a downgrade if you have already installed 11.3

@tpdownes Do you have any experience with this? Do you know if ignoring the version difference or forcing downgrade installation can cause the driver to malfunction?
@brandus1 Thank you for reporting this!

I would not rely on ignoring a compiler mismatch in general. I would either make sure the right kernel is installed (if available) or deliberately install an earlier gcc (presumably still available)
That said you could probably try to get away with ignoring the compiler mismatch in this case if you need progress now.


Update Popper.js to v2.x

Hello
Could you please plan the process of updating Popper.js to ver2.0.0. X ?
As a result, a lot of bugs will be fixed: https://github.com/popperjs/popper.js/labels/Fixed in v2
One of them is my https://github.com/popperjs/popper.js/issues/835
I'll be appreciated.
Regards, Dmytro

Sorry, v2.0.0 isn't released. When this happen we'll revisit it later.

We just released the first alpha (@popperjs/core@2.0.0-alpha.1).
It would be awesome to get some feedback.

If anyone can help us with dropping our custom polyfills and updating the docs accordingly, this is one less thing that's blocking us for v5. Don't forget to CC me if you make a PR.

In the last team group call, we decided that at this point, it might be easier for us to drop IE 11 support from v5. v4 will be supported for as long as we can (we'll update the release repo to reflect his when we release v5), so people who want to support IE can still use v4.
After we remove IE 11 support from master, we can use any help available to update the docs, update popper.js to v2 and so on.
Generally, we could use any help we could get in the JS department, so if anyone's interested in helping us out, please drop by our Slack and DM me.

Drupal 9 is upgrading to popper 2 https://www.drupal.org/node/3112670
To continue using Bootstrap based themes, we should upgrade too.

PRs welcome as usual for master.

👋 I just published a new<EMAIL_ADDRESS>version, it's 1.16.1-lts. It's just like 1.16.1, but without the deprecation warning.
It's meant to be used by those libraries that aren't willing to update to 2.x for whatever reason (for example, Bootstrap 4.x may never update so this LTS allows to not show the deprecation warning to the users).

👋 I just published a new<EMAIL_ADDRESS>version, it's 1.16.1-lts. It's just like 1.16.1, but without the deprecation warning.
It's meant to be used by those libraries that aren't willing to update to 2.x for whatever reason (for example, Bootstrap 4.x may never update so this LTS allows to not show the deprecation warning to the users).

Thx for doing this, however I have a question. With NPM I installed bootstrap (4.4.1) en this 1.16.1-lts version of popper.js, but npm install still gives me this message:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
Any way to get rid of that?

Bootstrap will need to update its peerDependencies to explicitly allow this new version.

They require ^1.16.0 currently. Does the use of letters (-lts) in this version number confuse npm or bootstrap that it doesn't recognize it as a correct version? Or should versioning this version of popper.js not have been 1.16.2 in that case? (mind you I do not have much experience with NPM and the way it checks dependencies etc)

the -lts is a pre-release flag, so the existing ^ selector will not include it. I can't release it as 1.16.2, because doing so all the consumers who update to popper.js@latest would miss the warning.
The -lts strategy, instead, provides a way for library maintainers to explicitly opt in the LTS version.

Gotcha. So now we have to wait until Bootstrap includes the -LTS version as an allowed peerDependency.

Are the bootstrap devs aware of this fact?

We are and keeping spamming us is not helpful.

I'm sorry. I never looked at the address bar in my browser. I thought I was on the popper.js repo 😊  Wasn't my intention to spam you guys.

Congrats on releasing Bootstrap 5 alpha 🎉
I noticed it's still using Popper v1 though, are there plans to migrate to v2 before beta/final release?

Yes we plan to do it ASAP

Can we make Popper.js optional somehow? We don't even use any Bootstrap features that require Popper, but we see this annoying warning every day.

Sorry to bother all of you, but could you provide any updates, please?
appreciate your help.

For anyone who is using v2 globally with vendor code referencing the old v1 class, you could do something like this (I haven't checked the compatibility for all methods etc. but it should allow Popper to be instantiated using both as a class (v1) and by using createPopper() (v2)).
`// Ensure Popper version 2.
if (typeof Popper != 'undefined' && typeof Popper.createPopper == 'function') {
//Stash version 2.
window.Popper2 = Popper;
// Create a constructor for v1 uses.
Popper = function(reference, popper, options) {
return window.Popper2.createPopper(reference, popper, options);
}
// Create the createPopper() method for v2 uses.
Popper.createPopper = function(reference, popper, options) {
return window.Popper2.createPopper(reference, popper, options);
}
}`

Popper modifiers are different in v2, you can't do that


Temporary fix for missing kernel initialization after restarting kernel session

https://github.com/microsoft/vscode-jupyter/pull/7089 will be updated to reflect a proper fix (move all initialization logic out of INotebook into IKernel)

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-2021.08@2e751f6). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head c9b57e2 differs from pull request most recent head 0654104. Consider uploading reports for the commit 0654104 to get more accurate results

@@                Coverage Diff                @@
##             release-2021.08   #7102   +/-   ##
=================================================
  Coverage                   ?     64%
=================================================
  Files                      ?     410
  Lines                      ?   28575
  Branches                   ?    4270
=================================================
  Hits                       ?   18421
  Misses                     ?    8540
  Partials                   ?    1614


Ignore log files when commiting

Most of these are no-ops. https://git-scm.com/docs/gitignore
Which ones of these are you actually observing problems with.

**.log

Which log files are these?

This feels like a pretty trivial change. I'm not against it, but I struggle to raise to the level of caring enough to kick off another build if a flaky test fails or reviewing it.
Essentially it fails a personal test I have for a PR, of whether it's clear whether I'd approve the commit or the revert form of it.  If you submitted the reverse removing the *.log, there would be an arguable case for landing it since we don't have a bunch of logs files accidentally committed as far as I'm aware. Hence trying to understand why it's important we make changes like this.  How is this hurting you currently, what are you solving.

Which log files are these?

I make a build or other tasks then generated several log files, it's easy to commit with them but not expected.
I tried to reproduce that files but failed

When I bumped jsoup version, generated them


PLNSRVCE-1069:  get exporter metrics to work from dashboards

These are the changes I needed to get the pipeline-service-exporter metrics to be visible from the grafana dashboards.
Turns out we need to move the servicemonitor def from infra-deployments to this repo
A couple of minor selector labeling tweaks on top.

/hold
per discussion in scrum, @adambkaplan prefers to leverage dashboards and the inner dev loop work he is doing instead of the openshift console for direct usage of the exporter stats
that said, I'm leaving this PR open for a short while, to assist @ramessesii2 when he returns for sorting out accessing the exporter metrics from grafana
I also asked @adambkaplan and he agreed to use exporter metrics as part of his work, where perhaps he can debug access exporter metrics from grafana

OK @adambkaplan @ramessesii2 I was able to prove that with the changes in this PR, including a hack in the latest dashboard to call exporter metrics vs. tekton ones, coupled with a test branch in infra-deployments pointing to this PR, and using bootstrap / preview from infra-deployments, we can access the exporter's metrics.
The test branch in infra deployments created by boostrap / preview is  https://github.com/gabemontero/infra-deployments/commits/preview-test-pipeline-svc-grafana
I'll attach a couple of screen shots.  One from the metrics panel.  Another from the grafana one.  The prometheus query itself is not something we would use long term, but it worked with my overriding the TaskRuns per Hour chart, and it produced the same value sligthlly above 6.
I'll start iterating on this PR to get it to the meets min.  I think among other things, the servicemonitor needs to move from the developer folder to the operator one.  Examining the system live, there were no other servicemonitors that linked to the pipeline-metrics-exporter deployment/service vian the selector, labels, etc.

confirmed with @amisstea that we should move our servicemonitor out of infra-deployments and into our repo
will use this PR for that @adambkaplan @ramessesii2

The 2 Red Hat Trusted App Pipeline failures are part of @xinredhat working on moving our CI to RHTAP.  Those will start working when he is done.
The 2 jobs on the pipeline-service CI are running per usual.


Define function type without overriding given parameters

In the below example, type returnsStringFunc attempts to describe a function which takes anything, and returns an inner function like (innerParam: string) => string. This type could then be applied to functions A-D, and the type of innerParam would be known. To accomplish this, as far as I can tell, you must write the params as (...args: any[]). However, you then lose the specific param information of the functions you apply this type to.
type returnsStringFunc = (...args: any[]) => (innerParam: string) => string

// This function knows innerParam is a string
const funcA: returnsStringFunc = () => {
	return (innerParam) => innerParam
}

// This function doesn't know what innerParam is (implictly 'any')
const funcB = () => {
	return (innerParam) => innerParam
}

// This function knows innerParam is a string
const funcC: returnsStringFunc = (prefix: string) => {
	return (innerParam) => prefix + innerParam
}

// This function doesn't know what innerParam is (implictly 'any')
const funcD = (prefix: string) => {
	return (innerParam) => prefix + innerParam
}

funcA(1) // No error, passing argument to function which should have none
funcB(1) // Expected 0 arguments, but got 1
funcC(1) // No error, passing number when prefix should be string
funcD(1) // 1 is not string

Once the type returnsStringFunction is applied to a function, that function's params are cast as any[]. It would be useful for the params of funcA-D to stay visible to the compiler somehow, while still being able to define their type signature.

It doesn't make sense for funcB to be inferred to be returnsStringFunc.
Maybe () => <T>(innerParam : T) => T or something similar.
Neither does it make sense for funcD to be inferred to be returnsStringFunc.
Maybe (prefix : string) => (innerParam : any) => string

What is your specific use case?
Does the following code snippet help in any way?
type StringFunctionFactory = (
    (...args: any[]) => (
        (innerParam : string) => string
    )
);
declare function foo<T extends StringFunctionFactory>(t: T): (
    T
);

//() => (innerParam: string) => string
const funcA = foo(() => {
    return (innerParam) => innerParam
});
//(prefix: string) => (innerParam: string) => string
const funcC = foo((prefix: string) => {
    return (innerParam) => prefix + innerParam
});

I know it doesn't make sense for them to be inferred as that type, but I'd like a way to apply that type to the function without losing the params definitions. Your code snippet essentially works, but it requires calling the functions like funcA()('a') and isn't really idiomatic.
Of course I can simply define the return value, such as
const funcA = (): (innerParam: string) => string => {
	return (innerParam) => innerParam
}

This will do what I want. But I'd like a way to generalize and apply this information to the outer function itself, rather than just defining the return value. Then I could use that type definition in interfaces etc, as a whole function type rather than just a return type.

Same here...based on my understanding, I have:
file1.ts
export type DocChangeCallback = (changeType: DocumentChangeType, doc: object) => void;

file2.ts
import {DocChangeCallback} from './file1';

const cb:DocChangeCallback = function (changeType, doc) {
   ...
}

So I really don't want to redefine the exact same interface as for DocChangeCallback again but I keep getting the warning: expected ... to have a typedef first for the call signature and then the function params.
Because at the moment I would be required to do this:
import {DocumentChangeType} from './whatever';
import {DocChangeCallback} from './file1';

const cb:DocChangeCallback = function (changeType: DocumentChangeType, doc: object): void {
   ...
}

which would basically require defining the same interface defined in file1.ts again.
Is there any way to having the type of the function and its params be inferred from its type?


Migrate crate-jdbc to Maven Central

Summary of the changes / Why this is an improvement
This is implementing uploading of crate-jdbc to Maven Central, following the sunsetting of Bintray/JCenter. The process is complicated by the fact that OSSRH (oss.sonatype.org) does quite a bit more checking of the deployed artifacts than bintray used to. It requires that:

There is a -javadoc.jar
There is a -sources.jar
There are .asc signatures for all jars and poms

None of which worked in the previous setup (see https://dl.bintray.com/crate/crate/io/crate/crate-jdbc/2.6.0/).
We had to adapt the gradle build to do this, which proved somewhat problematic. Gradle seems to favour usage of the publish plugin, whereas we were using the (simpler) uploadArchives/mavenDeployer, which refused to upload the .asc files, and required a hack to get them in. If someone with more Gradle knowledge can look at this and comment, that would be awesome.
Checklist

[x] CLA is signed

@mergifio backport 2.6

@Mergifyio backport 2.6


implement etags in FS backend

I just copy and pasted from the fsext implementation,
and it seems to work.
I imagine that most implementers will want etags, since
they add considerable safety.
Ref: #111

It's not so much about its usefulness, but more about the performance implications. In each PROPFIND on directories, it'll create a hash for each file on the first level of that directory - regardless of its size.
This can be a considerably CPU-intensive operation, which is why I don't recommend this for production systems, unless you also implement a decent etag caching mechanism like other NodeJS static file servers probably have already.

Thanks for the explanation, makes sense.
Where would an in-memory cache need to sit in the runtime object hierarchy in order to stick around and be global? It seems based on a quick reading that file nodes get created per-request, so I guess the cache could hang on the tree object?
I could see wanting to have different cache implementations, a simple one invalidating using fs.stat and maybe also an eager one using fs.watch or one of cross platform watchers on npm.

On 17 Feb 2016, at 19:01, Eric Drechsel<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Thanks for the explanation, makes sense.
Where would an in-memory cache need to sit in the runtime object hierarchy in order to stick around and be global? It seems based on a quick reading that file nodes get created per-request, so I guess the cache could hang on the tree object?

The tree object would be a very good place indeed. The node path would be the cache entry identifier, along with the mtime. Or something else that’s smarter.

I could see wanting to have different cache implementations, a simple one invalidating using fs.stat and maybe also an eager one using fs.watch or one of cross platform watchers on npm.

Yeah, that’s possible or be able to pass in ‘cacheOptions’ to the tree/ server instance to configure the caching behavior. Depends on what get implemented.


robot-shop: Restores fail, database already exists on mysql post hook

Similar to #3 , basically the post hook assumes there is no data on the DB... the error is :
oc -n robot-shop logs mysql-1-hook-post
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1007 (HY000) at line 1: Can't create database 'ratings'; database exists

Hook CMD :
    Command:
      /bin/sh
      -c
      sleep 120 && zcat /tmp/mysql-init-scripts/10-dump.sql.gz | /opt/rh/rh-mysql57/root/bin/mysql -h $MYSQL_SERVICE_HOST -u root -pR00t@123 -D $MYSQL_DATABASE -P 3306 && /opt/rh/rh-mysql57/root/bin/mysql -h $MYSQL_SERVICE_HOST -u root -pR00t@123 -P 3306 < /tmp/mysql-init-scripts/20-ratings.sql && sleep 60

Could also potentially use --force to override on the hook....

Fixed with https://github.com/fusor/mig-demo-apps/commit/ab30ff944e18e6be433bbfd371548e33dce602a8
Migration results :
NAME                         READY     STATUS    RESTARTS   AGE
cart-7f78759dc-6h7mx         1/1       Running   0          2m26s
catalogue-67f57b7b56-q74cq   1/1       Running   0          2m26s
dispatch-5c54f84c7d-4vc44    1/1       Running   0          2m26s
mongodb-79f5f7cbf6-l5zz8     1/1       Running   2          2m26s
mysql-1-ct2nf                2/2       Running   0          2m14s
mysql-1-deploy               1/1       Running   0          2m25s
mysql-1-hook-post            1/1       Running   0          119s
payment-df9f6b8b4-krzr4      1/1       Running   0          2m26s
rabbitmq-57f9cd66d9-4mdfc    1/1       Running   0          2m25s
ratings-5849f4cdf9-f4fs9     1/1       Running   0          2m25s
redis-6886b7f87-6xjwq        1/1       Running   0          2m25s
shipping-7f8cf9f599-8ggc2    1/1       Running   0          2m25s
user-7588d6c948-m6s8g        1/1       Running   0          2m25s
web-74745bcd85-p8jqm         1/1       Running   0          2m24s

Closing as new apps worked for me and @fbladilo


Catching exceptions with sentry

Currently all exceptions are catched and returned in a formatted form. This is fine for invalid formatted queries, but for programming errors in my code i'd like these to be reraised, so i can catch them with Sentry for example. I could not find a way to achieve this currently, any ideas?

Hi @pjotterplotter
I just added exception reporting with the logging module.
Your Sentry setup will automatically captures logging outputs by default.
https://docs.sentry.io/platforms/python/guides/logging/


Fix normalized number by removing ( and -) in phone

Normalized number returns blank when the number contains brackets. So got the normalized number by removing the brackes and hyphens in the phone

Thanks @sureshmi. We shouldn't alter whatever's returned by android. If you want to alter the normalized phone number you get by default, you should probably do it in your app directly.


Uncaught ReferenceError: blockNumber is not defined

The following error is being thrown:
ReferenceError: blockNumber is not defined
    at async.series.previousBlockHash (/node_modules/ethereumjs-testrpc/lib/subproviders/delayedblockfilter.js:74:13)
    at /node_modules/ethereumjs-testrpc/node_modules/async/lib/async.js:718:13
    at Immediate.iterate [as _onImmediate] (/node_modules/ethereumjs-testrpc/node_modules/async/lib/async.js:262:13)
    at processImmediate [as _immediateCallback] (timers.js:383:17)

I do not have a simple test case to reliably throw this error.  However, see the following code:
DelayedBlockFilter.prototype.handleGetFilterChanges = function(payload, next, end) {
  // ...
        if (result.length != 0) {
          // blockNumber does not get declared
          c();
        } else {
          // blockNumber gets declared
          c();
        }
      function(c) {
        if (blockNumber) return c();
      }
}

I have a test project which:

Deploys several libraries
Deploys several contracts (using web3 .new with constructor parameters).
Uses default testrpc initialization (auto-mining, etc.)

The above error is reliably thrown, though exactly when it is thrown is a bit unpredictable.

Expected Behavior

ReferenceErrors should not be thrown.  Variables should be declared (and / or the error appropriately caught).
Current Behavior

ReferenceError: blockNumber is not defined
    at async.series.previousBlockHash (/node_modules/ethereumjs-testrpc/lib/subproviders/delayedblockfilter.js:74:13)
    at /node_modules/ethereumjs-testrpc/node_modules/async/lib/async.js:718:13
    at Immediate.iterate [as _onImmediate] (/node_modules/ethereumjs-testrpc/node_modules/async/lib/async.js:262:13)
    at processImmediate [as _immediateCallback] (timers.js:383:17)

Possible Solution

See pull request #183
Steps to Reproduce (for bugs)

Error thrown from delayedblockfilter when result.legth != 0
        if (result.length != 0) {
          // blockNumber does not get declared
          c();
        } else {
          // blockNumber gets declared
          c();
        }
      function(c) {
        if (blockNumber) return c();
      }

Context

I have a test project which:

Deploys several libraries
Deploys several contracts (using web3 .new with constructor parameters).
Uses default testrpc initialization (auto-mining, etc.)

The above error is reliably thrown, though exactly when it is thrown is a bit unpredictable.
I have not tried changing the project to use a raw sendTransaction or some other method that avoids using the web3 checkForContractAddress , nor have I tried playing around with testrpc settings, so, perhaps there could be work-arounds.
Your Environment

Version used: 3.0.0 (project works under previous versions of testrpc)
Operating System and version: Multiple, replicated on Mac OS X Yosemite, Windows 10, and Ubuntu.  Generally node v4.5.0 and<EMAIL_ADDRESS>though the error appears reproducible across multiple OS/dependencies.

Workaround
Changing from Contract.net to using .sendTransaction (which requires encoding any constructor arguments) in tests also appeared to resolve the issue.

Closing as the PR was merged: https://github.com/ethereumjs/testrpc/pull/183


Add "persistence.existingClaim" to documented options

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

Thanks for the contribution, before continue, you need to sign the CLA, also you should increment the chart version in the Chart.yml according to semver:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

This is just a very minor doc edit. No need for a chart version bump.

@spitimage it's required for the CI to pass, even for minor doc changes. We cannot get this merged if the version is not bumped!

/ok-to-test
/lgtm
Thanks a lot @spitimage, sorry about the CI issue!


sdp transform parse webrtc  sdp error

Error handling SDP offer:  TypeError: sdp.split is not a function
at Object.exports.parse (/Users/xiang/Work/soupserver/node_modules/sdp-transform/lib/parser.js:46:7)
i did not dig yet,  just report here.

Are you sure you are passing the SDP string and not the SDP offer object?

yes,  it is sdp string.
maybe it is because of  i change the bandwidth of the sdp.
if i do not change the bandwidth, i will parse well.

sorry my fault


When I click on "Logout", it does not signout neither any error msg.

When I click on "Logout", it does not signout neither any error msg. It actually stores my previously logged in user and eventhough I have clicked on "Logout" that user email shows up for login. When clicked on the existing email, again i see logout page. How do i come out of this loop by successfully logging out?
      <TouchableOpacity onPress={() => {this._signOut(); }}>
        <View style={{marginTop: 50}}>
          <Text>Sign out</Text>
        </View>
      </TouchableOpacity>

_signOut() {
GoogleSignin.revokeAccess().then(() => GoogleSignin.signOut()).then(() => {
this.setState({user: null});
console.log('out');
console.log('delete');
})
.done();
}
thanks
Laxmikant

@lkag2000 Having the same issue. Were you able to resolve this? Any help would be appreciated

I tried reproducing this with the example app but everything seems to be working.
please check out our example app if this persist you can re-open this issue.

I've been facing this issue on iOS, where GoogleSignin.revokeAccess() neither resolves nor rejects. However the GoogleSignin.signOut() method resolves as expected. I've been experiencing this only when I do this: sign in -> reload app -> sign out. Works fine if I don't reload app in between.
As a workaround, I've been calling revokeAccess() synchronously without waiting for it to resolve, like this:
GoogleSignin.revokeAccess()
await GoogleSignin.signOut()


Add toggleMenuBarOnAltPressed option to BrowserWindow.

Hi,
I recently started using Atom and had some issues with the Alt key
toggling menu bar, so I added an option to disable this behavior.
The option can be passed when instanciating a BrowserWindow,
or be changed using the setToggleMenuBarOnAltPressedmethod
on a BrowserWindow instance.
I also added a doesToggleMenuBarOnAltPressed method
to retrieve the current value of the option.
The option is disabled by default, so this will not break or change the behavior of
existing apps.
Background
In some apps, such as Atom, the menu bar can be restored in other ways,
and as it is not something that is done so often (at least for my usage),
I think this option makes sense.
I will explain my issue in Atom, which is my actual motivation for this option.
I use XMonad, and my shortcut to change window focus is alt+j.
When I press alt, menu_bar_alt_pressed becomes true.
Then, when I press j, the keydown event is intercepted by XMonad,
and the focus changes to some other app, let's say my browser.
As Atom did not receive the j keydown event, menu_bar_alt_pressed is still true.
When I then want to go back go Atom, I press alt+j again. I usually release the
j button instantly, and the alt after, so the j keyup is not handled by atom, but
the alt keyup event is, which makes the condition for toggling the menu bar true.
So basically each time I change focus to some other app and go back to Atom,
the menu bar is toggled, which is a little annoying.

Why not just disables the auto-hide menu?

@zcbenz I want the menu to be always hidden, not always shown.

@tuvistavie There is setMenuBarVisibility API to show/hide the menu.

@zcbenz Great, that's perfect! Thank you.

Does using setMenuBarVisibility to disable the menu appearing prevent the menu taking focus as well?

@theFroh It does not seem to. If I press alt+e (at least in Atom), the edit menu and the menu bar shows up even with setMenuBarVisibility set to false. However, if the shortcut is assigned, the assigned binding takes advantage.


R-D curve differences between DCVC-HEM and DCVC-DC papers

Hi, first of all, thanks for your great work!
While looking around the repository to get R-D performances from the figures you provided, I found that reported performances of DCVC-DC and DCVC-HEM papers are really different.
I compared UVG dataset's RGB R-D curves.
Regarding DCVC-HEM's figure (https://github.com/microsoft/DCVC/blob/main/DCVC-HEM/assets/rd_curve_psnr.png),

highest operating point of DCVC shows approximately (37dB, 0.10bpp) R-D performance,
and DCVC-HEM shows approximately (38.5dB, 0.115bpp).

However, regarding DCVC-DC's figure (https://github.com/microsoft/DCVC/blob/main/DCVC-DC/assets/rd_rgb_psnr.png),

DCVC's PSNR is higher than 38dB when it's bpp is much lower than 0.10bpp,
and DCVC-HEM's is also higher than 40.5dB while it's bpp is about 0.09bpp.

I saw that dataset_config_example.json is same between two model's repositories, but are there any differences between two models' test conditions that I missed?
Thanks in advance!

Yes, they are different. The main reason is that the RGB (png) source files are different. We are using BT.709 conversion matrix to generate png data to test RGB sequences in DCVC-DC. More details could be found at https://github.com/microsoft/DCVC/tree/main/DCVC-DC#rgb-content and the DCVC-DC paper.


add proto folder path to proto_path

This fixes the issue @smola had.
Depends on #81. Review just last commits.

Problem with Travis cloning the pr branch :$ Accepting the PR


python311Packages.aiounifi: 69 -> 70

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.aiounifi is: Python library for communicating with Unifi Controller API
meta.homepage for python311Packages.aiounifi is: https://github.com/Kane610/aiounifi
meta.changelog for python311Packages.aiounifi is: https://github.com/Kane610/aiounifi/releases/tag/v70
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 70 with grep in /nix/store/3k1xbrii4lwikbx0n4sxwr0lchmrmhkb-python3.11-aiounifi-70
found 70 in filename of file in /nix/store/3k1xbrii4lwikbx0n4sxwr0lchmrmhkb-python3.11-aiounifi-70

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.unifi
python311Packages.aiounifi

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3k1xbrii4lwikbx0n4sxwr0lchmrmhkb-python3.11-aiounifi-70 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.aiounifi https://github.com/r-ryantm/nixpkgs/archive/bc8b476caad8399d4bbb97511be86267709346a3.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/bc8b476caad8399d4bbb97511be86267709346a3#python311Packages.aiounifi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3k1xbrii4lwikbx0n4sxwr0lchmrmhkb-python3.11-aiounifi-70
ls -la /nix/store/3k1xbrii4lwikbx0n4sxwr0lchmrmhkb-python3.11-aiounifi-70/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

python311Packages.aiounifi

Maintainer pings
cc @peterhoeg for testing.

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

1 package marked as broken and skipped:

home-assistant-component-tests.unifi

2 packages built:

python311Packages.aiounifi
python311Packages.aiounifi.dist

It isn't marked as broken, just as insecure, because it transitively depends on OpenSSL 1.1. Not sure why the nixpkgs-review says that.


header titles not accessible

I'm setting my screen titles using the title property in navigationOptions, and the titles aren't accessible to VoiceOver.
I noticed that the accessible prop is explicitly set to false on the HeaderTitle component. If I change it to true, the titles become accessible.
I'd submit a PR, but the prop was specifically set to false in this commit. So I'm not sure if maybe there's some configuration where it's necessary for the titles not to be accessible.

I added HeaderTitle component from the repo to my project and removed accessible property.
In navigationOptions I use it this way:
// title: 'Screen Title'
headerTitle: <HeaderTitle style={{color: "white"}}>Screen Title</HeaderTitle>

I got the same problem after upgrading from 2.0.1 to 3.0.9. It was working before, so for me it's a regression.


compile with -fPIC

The static library should be compiled with -fPIC (Linux). To do so, you should add in your CMakeLists.txt after line 46 (add_library)
set_property(TARGET ${PROJECT_NAME} PROPERTY POSITION_INDEPENDENT_CODE ON)

Thanks, would you mind create a pr for this change? :)

Sorry, what is a pr? I am sure I can do it.


FileNotFound

Summary of the issue
FileNotFoundException: Could not load file or assembly 'EFSecondLevelCache.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified
Environment
.NET Core SDK version: 3.0.100-preview9-014004
Microsoft.EntityFrameworkCore version: 3.0.0-preview9.19423.6
EFSecondLevelCache.Core version: 2.6.3

Output:
Exception message:
FileNotFoundException: Could not load file or assembly 'EFSecondLevelCache.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified

Run these commands in the main folder of your app to update your entire solution consistently:
dotnet tool install -g dotnet-outdated
dotnet outdated -u
dotnet restore


Error message when using Bun as the engine

What happened?
Steps to Reproduce
Follow the any basic example of using Phoenix but Bun as the engine.
Actual Result
The logs are send and received by the Phoenix service but an error message is logged in the client for every request.
Expected Result
Keep sending the logs but no error messages in the client side.
Additional Details
Switch the JS engine to Node.js makes the system work normally with any error message.
OpenTelemetry Setup Code
import { LangChainInstrumentation } from "@arizeai/openinference-instrumentation-langchain";
import { SEMRESATTRS_PROJECT_NAME } from "@arizeai/openinference-semantic-conventions";
import * as CallbackManagerModule from "@langchain/core/callbacks/manager";
import { diag, DiagConsoleLogger, DiagLogLevel } from "@opentelemetry/api";
import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-proto";
import { Resource } from "@opentelemetry/resources";
// import { ConsoleSpanExporter } from "@opentelemetry/sdk-trace-base";
import {
  NodeTracerProvider,
  SimpleSpanProcessor,
} from "@opentelemetry/sdk-trace-node";
import { ATTR_SERVICE_NAME } from "@opentelemetry/semantic-conventions";

export function setupTracing() {
  // For troubleshooting, set the log level to DiagLogLevel.DEBUG
  diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.INFO);

  const provider = new NodeTracerProvider({
    resource: new Resource({
      [ATTR_SERVICE_NAME]: "user-load-agent",
      [SEMRESATTRS_PROJECT_NAME]: "user-load-agent",
    }),
  });

  const otlpExporter = new OTLPTraceExporter({
    timeoutMillis: 50000,
  });

  // provider.addSpanProcessor(new SimpleSpanProcessor(new ConsoleSpanExporter()));
  provider.addSpanProcessor(new SimpleSpanProcessor(otlpExporter));

  const lcInstrumentation = new LangChainInstrumentation();
  // LangChain must be manually instrumented as it doesn't have a traditional module structure
  lcInstrumentation.manuallyInstrument(CallbackManagerModule);

  provider.register();

  // eslint-disable-next-line no-console
  console.log("👀 OpenInference initialized");

  return {
    forceFlush: async () => {
      otlpExporter.forceFlush();
      provider.forceFlush();
    },
  };
}

package.json
{
  "name": "myapp",
  "private": true,
  "version": "1.0.0",
  "type": "module",
  "module": "src/client.ts",
  "scripts": {
    "build": "tsc",
    "start": "bun run dist/client.js",
    "dev": "bun run --watch src/client.ts"
  },
  "engines": {
    "bun": "1.1.37"
  },
  "dependencies": {
    "@anthropic-ai/sdk": "^0.32.1",
    "@arizeai/openinference-instrumentation-langchain": "^0.2.0",
    "@opentelemetry/exporter-trace-otlp-http": "^0.49.1",
    "@opentelemetry/exporter-trace-otlp-proto": "^0.56.0",
    "@opentelemetry/sdk-trace-base": "^1.22.0",
    "@opentelemetry/sdk-trace-node": "^1.22.0",
    "dotenv": "^16.4.5",
    "express": "^4.21.1",
    "langchain": "^0.3.5",
    "typescript": "^5.6.3",
    "uuid": "^11.0.3",
    "ws": "^8.18.0"
  },
  "devDependencies": {
    "@types/bun": "latest",
    "@types/express": "^5.0.0",
    "@types/ws": "^8.5.13",
    "typescript": "^5.6.3"
  },
  "peerDependencies": {
    "prettier": "^3.3.3",
    "eslint": "^8"
  },
  "prettier": {}
}

Relevant log output
{"message":"Request timed out","originalLine":"59","originalColumn":"25","line":"87","column":"24","sourceURL":"/code/node_modules/@opentelemetry/exporter-trace-otlp-proto/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js","stack":"Error: Request timed out\n    at <anonymous> (/code/node_modules/@opentelemetry/exporter-trace-otlp-proto/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:87:24)\n    at emit (node:events:183:48)\n    at emitCloseNT (node:http:191:21)\n    at <anonymous> (node:http:1074:18)\n    at <anonymous> (native:19:28)\n    at processTicksAndRejections (native:7:39)","name":"Error"}

Operating System and Version
macOS 15.1
Runtime and Version
bun 1.1.31, Node.js v20.17.0

Hi @lostbean - thanks for reaching out.
Please note that bun is currently not supported by this project. If you can provide a fix that still passes the tests for Node.js we're happy to accept a fix.

link to reproducer: https://github.com/pichlermarc/repro-5260
Two observations:

the timeout happens immediately on export
the export never arrives on the collector

@lostbean - in the issue you opened it says that "logs" arrive in Phoenix - are you trying to say that the trace export succeeds and you can see the traces that were exported? Or are you referring to something else? 🤔


can't capture photos at 1280x720 resolution after using SpatialUnderstanding

This is a duplicate of issue 520 that I have entered in the HoloToolkit-Unity project and was advised to enter here as well.
REPRO CASE:

Open HoloToolkit-Unity in Unity 5.5.1f1.
Create new scene.
Create a game object with the atached PhotoCaptureExample.cs script. (This script is based on https://docs.unity3d.com/ScriptReference/VR.WSA.WebCam.PhotoCapture.html, but the resolution is changed to 1280x720.)
Add the SpatialMapping prefab to your scene.
Add the SpatialUnderstanding prefab to your scene. In the Spatial Understanding component, uncheck the Auto Begin Scanning property.
In player settings, publishing, check the WebCam checkbox.
Build and run the project on HoloLens.

result: The following error occurs and then the application unexpectedly exists:
Failed to set capture resolution (hr = 0xC00D36B4)
(Filename: C:/buildslave/unity/build/Runtime/VR/HoloLens/WebCam/PhotoCapture.cpp Line: 1180)
expected: PhotoCaptureExample script succeeds and prints "OnCapturedPhotoToMemory succeeded". Note that you can currently get the expected result either by changing the resolution to 2048x1152 or by skipping over the call to SpatialUnderstanding_Init.
You can access a repro case from my fork at https://github.com/ForrestTrepte/HoloToolkit-Unity/tree/issues/520_SpUndPhCap_FailedMinRepro. Use the scene Assets/Issue520.unity.
PhotoCaptureExample.txt

Hi! I have a similar issue when I'm scanning and even after request_finsih I cant access the camera. It never initializes. Anyone Haveing any idea about why spatialUnderstanding is accessing the camera?

It appears that this is due to SpatialUnderstanding changing the floating point rounding mode. See https://github.com/Microsoft/HoloToolkit-Unity/issues/520 for more info.

I'm working on a fix. (This may take a little while if I only get the chance to work on it a little bit each day.)


Feature Request: Create a chocolatey package for installation of PCT

First off, love your work.  Using your PCT tools along with puppet to automate our deployments.  As such I was wondering if you could create a chocolatey package for PCT to help automate the deployment of environments that use your wonderful tools.
https://github.com/chocolatey/choco/wiki/CreatePackages
I'm happy to give it a crack (create a chocolatey package) for your tools but thought it would be polite to ask you first in case you want to create and control that part of it.

I don't have plans myself for Chocolatey packages, so feel free to build them !


youtube-dl: build the lazy_extractors module to improve startup time

Motivation for this change
youtube-dl imports every extractor it has unless the youtube_dl/extractor/lazy_extractors.py module is built.
This updates nixpkgs' youtube-dl to build the module, improving startup time.
Testing on an Intel 4790K / NVMe drive:
before:
# time youtube-dl --help > /dev/null
youtube-dl --help > /dev/null  0.26s user 0.06s system 100% cpu 0.322 total

# strace youtube-dl 'https://www.youtube.com/watch?v=nJ9IdzcQMoc' 2>&1 | grep extractor/ | grep \.pyc | wc -l
789

after:
# time youtube-dl --help > /dev/null
youtube-dl --help > /dev/null  0.13s user 0.05s system 100% cpu 0.182 total

# strace youtube-dl 'https://www.youtube.com/watch?v=nJ9IdzcQMoc' 2>&1 | grep extractor/ | grep \.pyc | wc -l
6

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

hmm, backport or to not backport...

I would leave it in master for a bit first to see if anything breaks.


gcp:pubsub/schema:Schema gets replaced on schema changes with a PROTOCOL_BUFFER schema

What happened?
I created a gcp:pubsub/schema:Schema resource. Then, I tried changing the schema (i added an extra field, which should be a legal proto revision change). According to documentation a new revision should have been created, but instead the schema is being replaced:
$ pulumi up
Previewing update (stack):
     Type                  Name                                 Plan        Info
     pulumi:pulumi:Stack   stack                                2 messages
 +-  └─ gcp:pubsub:Schema  schema                               replace     [diff: ~definition]

Is this expected behavior?
I would like to be able to create a new revision, instead of re-initializing to prevent having to delete the the topic and all subscriptions to update a schema
Example
import * as gcp from "@pulumi/gcp";

const definition: string = ...

export const schema = new gcp.pubsub.Schema(
  "schema",
  {
    name: "schema",
    project: gcp.config.project,
    type: "PROTOCOL_BUFFER",
    definition: definition,
  }
);

Output of pulumi about
CLI
Version      3.92.0
Go Version   go1.21.3
Go Compiler  gc

Plugins
NAME        VERSION
gcp         6.39.0
kubernetes  4.4.0
nodejs      unknown

Host
OS       darwin
Version  14.0
Arch     arm64

This project is written in nodejs: executable='/opt/homebrew/bin/node' version='v21.1.0'

...

Dependencies:
NAME                VERSION
@pulumi/pulumi      3.89.0
@types/node         16.18.59
typescript          4.9.5
@pulumi/gcp         6.39.0
@pulumi/kubernetes  4.4.0

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

nvm, updating to 7.2.0 fixed it


Instance delete is failing

$ for uuid in `sf-client --simple instance list | grep -v uuid | cut -f 1 -d "," | head -1`; do   sf-client instance delete $uuid; done
Traceback (most recent call last):
  File "/usr/local/bin/sf-client", line 8, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/click/decorators.py", line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/shakenfist/client/main.py", line 533, in instance_delete
    CLIENT.delete_instance(instance_uuid)
  File "/usr/local/lib/python3.6/dist-packages/shakenfist/client/apiclient.py", line 186, in delete_instance
    '/instances/' + instance_uuid)
  File "/usr/local/lib/python3.6/dist-packages/shakenfist/client/apiclient.py", line 109, in _request_url
    'API request failed', method, url, r.status_code, r.text)
shakenfist.client.apiclient.APIException: ('API request failed', 'DELETE', 'http://localhost:13000/instances/23000e33-25cd-47f2-a857-6ca6721cc86f', 500, '{"error": "server error", "status": 500, "traceback": "Traceback (most recent call last):\\n  File \\"/usr/local/lib/python3.6/dist-packages/shakenfist/external_api/app.py\\", line 91, in wrapper\\n    return func(*args, **kwargs)\\n  File \\"/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py\\", line 107, in wrapper\\n    verify_jwt_in_request()\\n  File \\"/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py\\", line 32, in verify_jwt_in_request\\n    jwt_data, jwt_header = _decode_jwt_from_request(request_type=\'access\')\\n  File \\"/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py\\", line 294, in _decode_jwt_from_request\\n    decoded_token = decode_token(encoded_token, csrf_token)\\n  File \\"/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/utils.py\\", line 118, in decode_token\\n    allow_expired=allow_expired\\n  File \\"/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/tokens.py\\", line 140, in decode_jwt\\n    leeway=leeway, options=options, issuer=issuer)\\n  File \\"/usr/local/lib/python3.6/dist-packages/jwt/api_jwt.py\\", line 92, in decode\\n    jwt, key=key, algorithms=algorithms, options=options, **kwargs\\n  File \\"/usr/local/lib/python3.6/dist-packages/jwt/api_jws.py\\", line 156, in decode\\n    key, algorithms)\\n  File \\"/usr/local/lib/python3.6/dist-packages/jwt/api_jws.py\\", line 223, in _verify_signature\\n    raise InvalidSignatureError(\'Signature verification failed\')\\njwt.exceptions.InvalidSignatureError: Signature verification failed\\n"}')

Another example of proxy auth issues:
Jun 23 20:29:36 sf-2 External API request: <Request 'http://sf-2:13000/instances/23000e33-25cd-47f2-a857-6ca6721cc86f' [DELETE]>
Jun 23 20:29:36 sf-2 External API request: <bound method arg_is_instance_uuid_as_virt.<locals>.wrapper of <shakenfist.external_api.app.Instance object at 0x7f7ddc0c0518>> () {'instance_uuid': '23000e33-25cd-47f2
-a857-6ca6721cc86f'}
Jun 23 20:29:36 sf-2 Returning API error: 500, server error#012    Traceback (most recent call last):#012      File "/usr/local/lib/python3.6/dist-packages/shakenfist/external_api/app.py", line 91, in wrapper#01
2        return func(*args, **kwargs)#012      File "/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py", line 107, in wrapper#012        verify_jwt_in_request()#012      File "/usr/loc
al/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py", line 32, in verify_jwt_in_request#012        jwt_data, jwt_header = _decode_jwt_from_request(request_type='access')#012      File "/usr/loca
l/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py", line 294, in _decode_jwt_from_request#012        decoded_token = decode_token(encoded_token, csrf_token)#012      File "/usr/local/lib/python
3.6/dist-packages/flask_jwt_extended/utils.py", line 118, in decode_token#012        allow_expired=allow_expired#012      File "/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/tokens.py", line 140, in
decode_jwt#012        leeway=leeway, options=options, issuer=issuer)#012      File "/usr/local/lib/python3.6/dist-packages/jwt/api_jwt.py", line 92, in decode#012        jwt, key=key, algorithms=algorithms, opti
ons=options, **kwargs#012      File "/usr/local/lib/python3.6/dist-packages/jwt/api_jws.py", line 156, in decode#012        key, algorithms)#012      File "/usr/local/lib/python3.6/dist-packages/jwt/api_jws.py",
 line 223, in _verify_signature#012        raise InvalidSignatureError('Signature verification failed')#012    jwt.exceptions.InvalidSignatureError: Signature verification failed
Jun 23 20:29:36 sf-1 Proxied DELETE http://sf-2:13000/instances/23000e33-25cd-47f2-a857-6ca6721cc86f returns: 500, {"error": "server error", "status": 500, "traceback": "Traceback (most recent call last):\n  Fil
e \"/usr/local/lib/python3.6/dist-packages/shakenfist/external_api/app.py\", line 91, in wrapper\n    return func(*args, **kwargs)\n  File \"/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py\", line 107, in wrapper\n    verify_jwt_in_request()\n  File \"/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py\", line 32, in verify_jwt_in_request\n    jwt_data, jwt_header = _decode_jwt_from_request(request_type='access')\n  File \"/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py\", line 294, in _decode_jwt_from_request\n    decoded_token = decode_token(encoded_token, csrf_token)\n  File \"/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/utils.py\", line 118, in decode_token\n    allow_expired=allow_expired\n  File \"/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/tokens.py\", line 140, in decode_jwt\n    leeway=leeway, options=options, issuer=issuer)\n  File \"/usr/local/lib/python3.6/dist-packages/jwt/api_jwt.py\", line 92, in decode\n    jwt, key=key, algorithms=algorithms, options=options, **kwargs\n  File \"/usr/local/lib/python3.6/dist-packages/jwt/api_jws.py\", line 156, in decode\n    key, algorithms)\n  File \"/usr/local/lib/python3.6/dist-packages/jwt/api_jws.py\", line 223, in _verify_signature\n    raise InvalidSignatureError('Signature verification failed')\njwt.exceptions.InvalidSignatureError: Signature verification failed\n"}
Jun 23 20:29:36 localhost gunicorn.sf.access: [29108] <IP_ADDRESS> - - [23/Jun/2020:20:29:36 +1000] "DELETE /instances/23000e33-25cd-47f2-a857-6ca6721cc86f HTTP/1.1" 500 1551 "-" "Mozilla/5.0 (Ubuntu; Linux x86_64) ShakenFist/0.1.2"

It seems like we can't just pass the Authorization header around like we do?
Jun 23 20:29:36 sf-2 External API request: <Request 'http://sf-2:13000/instances/23000e33-25cd-47f2-a857-6ca6721cc86f' [DELETE]>
Jun 23 20:29:36 sf-2 External API request: <bound method arg_is_instance_uuid_as_virt.<locals>.wrapper of <shakenfist.external_api.app.Instance object at 0x7f7ddc0c0518>> () {'instance_uuid': '23000e33-25cd-47f2
-a857-6ca6721cc86f'}
Jun 23 20:29:36 sf-2 Returning API error: 500, server error#012    Traceback (most recent call last):#012      File "/usr/local/lib/python3.6/dist-packages/shakenfist/external_api/app.py", line 91, in wrapper#01
2        return func(*args, **kwargs)#012      File "/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py", line 107, in wrapper#012        verify_jwt_in_request()#012      File "/usr/loc
al/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py", line 32, in verify_jwt_in_request#012        jwt_data, jwt_header = _decode_jwt_from_request(request_type='access')#012      File "/usr/loca
l/lib/python3.6/dist-packages/flask_jwt_extended/view_decorators.py", line 294, in _decode_jwt_from_request#012        decoded_token = decode_token(encoded_token, csrf_token)#012      File "/usr/local/lib/python
3.6/dist-packages/flask_jwt_extended/utils.py", line 118, in decode_token#012        allow_expired=allow_expired#012      File "/usr/local/lib/python3.6/dist-packages/flask_jwt_extended/tokens.py", line 140, in
decode_jwt#012        leeway=leeway, options=options, issuer=issuer)#012      File "/usr/local/lib/python3.6/dist-packages/jwt/api_jwt.py", line 92, in decode#012        jwt, key=key, algorithms=algorithms, opti
ons=options, **kwargs#012      File "/usr/local/lib/python3.6/dist-packages/jwt/api_jws.py", line 156, in decode#012        key, algorithms)#012      File "/usr/local/lib/python3.6/dist-packages/jwt/api_jws.py",
 line 223, in _verify_signature#012        raise InvalidSignatureError('Signature verification failed')#012    jwt.exceptions.InvalidSignatureError: Signature verification failed

But then it worked before. I wonder if this is a token expiry thing?

The docs say the default is a 15 minute lifetime for a token, so that seems unlikely? https://flask-jwt-extended.readthedocs.io/en/stable/options/#configuration-options

This is definitely repeatedly happening to me. Further debugging required.

New theory, I need to generate a new token for that user before proxying the request, like I do for admin tokens.


componentizing avatar

taking a stab at componentizing a small piece of interactive UI (so we can add to the Styleguide)

Looking good except that one note.


Fix cut acceptance plotting

Fix the n_minus_1 plotting option in the get_cut_eff

Thanks again @ghusheng for capturing this important bug. Now it should be fixed.

np


Add config to cancel in-progress CI tasks on a new commit

Housekeeping to minimize CI resource usage on old commits.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.89%. Comparing base (7bf89a7) to head (601550f).
Report is 1 commits behind head on trunk.

Additional details and impacted files
@@           Coverage Diff           @@
##            trunk      #51   +/-   ##
=======================================
  Coverage   96.89%   96.89%
=======================================
  Files          28       28
  Lines        1225     1225
=======================================
  Hits         1187     1187
  Misses         38       38

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


Added to_buffer function for std::vector.

Codecov Report

Merging #77 (3f16f9e) into main (535f66f) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #77   +/-   ##
=======================================
  Coverage   89.70%   89.70%
=======================================
  Files          92       92
  Lines        9953     9960    +7
=======================================
+ Hits         8928     8935    +7
  Misses       1025     1025

Files Changed
Coverage Δ

include/async_mqtt/packet/packet_iterator.hpp
100.00% <100.00%> (ø)


Duplicating an instanced scene in code doesn't duplicate attached materials even when set local to scene

Godot version
3.4
System information
Fedora 35 (64-bit)
Issue description
Take a scene with an node with a material set to "local to scene" (such as the example GUI in 3D project).
If I duplicate the scene in the editor I get another instance with separate materials. However, if I duplicate the same scene using Node.duplicate instead I get a new instance that shares the same material as the parent. This is with or without passing the DUPLICATE_USE_INSTANCING flag.
Steps to reproduce

Duplicate a scene using Node.duplicate
Observe the material is shared between both instances

Minimal reproduction project
This can be seen in the examples GUI in 3D project. Simply add the following C# script to the scene root:
using Godot;
using System;

public class gui_in_3d : Spatial
{
    public override void _Ready()
    {
        Spatial gui = GetNode<Spatial>("GUIPanel3D");
        Node clone = gui.Duplicate();
        AddChild(clone);

        // So they don't overlap.
        gui.Translate(new Vector3(0.0f, 2.0f, 0.0f));

        // Read out the materials and paths.
        PrintInfo(gui);
        PrintInfo(clone);
    }
    private void PrintInfo(Node gui)
    {
        SpatialMaterial mat = (SpatialMaterial) gui.GetNode<MeshInstance>("Quad").GetActiveMaterial(0);
        GD.Print("Material for ", gui.GetPath(), " ", mat);
    }
}

Running this will then clone the GUIPanel3D node and show that both the original node and the new clone share the same material.

It might be worth noting for some reason in one of my projects this wasn't the case in 3.3.x, but is in 3.4. However, every time I try and simplify that down to a minimal reproduction I can't. The minimal reproduction I described will repro this issue in 3.3.x.

This seems to apply to textures too. I get the same thing when using a Sprite3D with a local to scene Texture.

I think this might be the same bug as #47918.

Duplicate of #45350.


Completed beta katas not marked as completed

Steps to reproduce this issue

Any katas published accidentally without removing  the initial JS version
Click the JS icon from the kata list to directly navigate to .../train/javascript
Find out the JS version does not meant to be shown up and do in another version
Before (maybe not necessary) completing the kata, the author removed the JS version
Then the kata would not marked as completed in the list (even if i try to submit the solution again)

Here, the Fix the bug kata is the sample

Also this kata is not in the /users/.../unfinished list.
This issue may be realted to #282, but if i begin to train in language A and complete in language B, the kata would be correctly marked as completed in the list.

If i complete before the author removing the JS version, everything works fine.

If you make a translation of the kata and the translation gets approved, the katas will be marked as completed again.