Winfspy reports incorrect information about the “..” entry when calling FspFileSystemAddDirInfo

Observe output from VS Debugger immediate window:
DirInfo
0x00000156d7fdb690 {Size=110 FileInfo={FileAttributes=0 ReparseTag=0 AllocationSize=0 ...} NextOffset=...}
    Size: 110
    FileInfo: {FileAttributes=0 ReparseTag=0 AllocationSize=0 ...}
    NextOffset: 0
    Padding: 0x00000156d7fdb6e0 ""
    FileNameBuf: 0x00000156d7fdb6f8 L".."

First the size should be 108 and not 110. This is because FileNameBuf should not contain a L'\0' terminating character. Compute DirInfo->size = sizeof(FSP_FSCTL_DIR_INFO) + FileNameLengthInBytes.
Also, the directory entry is not reported as a directory (observe that FileAttributes=0).
To be fix there:
https://github.com/Scille/winfspy/blob/6cd4d27e922b9a986e67962001f7796dfbc7276c/src/winfspy/operations.py#L604-L616
https://github.com/Scille/winfspy/blob/6cd4d27e922b9a986e67962001f7796dfbc7276c/example/memory.py#L317-L328
Thanks @billziss-gh for reporting this issue and providing the relevant information!

Fixed in #13


sleeplog: Suddenly almost always logged as awake on stable and development branch

Affected hardware version
Bangle 2
Your firmware version
2v21
The bug
Describe the bug
Since around March 28 I notice that the sleep reported by sleeplog is almost always reported as "awake" but never asleep for a long consecutive time (see screenshot).

In the screenshot above I was not wearing the Bangle.JS from 19:40 to 21:40, however it only marked the beginning and end of that period as "not worn".
The time from around 01:00 to 09:00 should be marked as sleep or consecutive sleep, however it's marked as almost only awake, though I did wear the band during that time.

Steps to reproduce

I should add that for testing I installed the stable branch sleeplog version for the duration from 01:00 to 09:00 and the development version (that also contains the latest temperature threshold wear detection features) after I woke up at around 09:00.
I reset the thresholds to the default values and set the temperature wear threshold to 29°C.
I did a full reinstall of sleeplog several times where I also removed all files generated by sleeplog (including source files as well as recorded data)

I first suspected it might be due to the latest temperature checks that were added but it also happens on the stable branch. I also deleted some apps that I suspected might potentially cause issues like activityreminder but this changed nothing.
I'm currently using my own fork but as you can see in the changes at https://github.com/espruino/BangleApps/compare/master...Ishidres:BangleApps:master there are no significant changes that should cause any problems with sleeplog.
Installed apps
widlock (0.08)
notify (0.13)
quicklaunch (0.15)
authentiwatch (0.07)
slevel (0.04)
weather (0.26)
thermom (0.07)
bee (0.03)
intervalTimer (0.01)
pomoplus (0.06)
noteify (0.03)
widbatv (0.03)
info (0.03)
barometer (0.04)
torch (0.11)
iconlaunch (0.19)
scicalc (0.03)
qmsched (0.10)
messagesmusic (0.05)
messages (0.62)
boot (0.60)
widalarm (0.02)
messageicons (0.07)
circlesclock (0.26)
agenda (0.15)
run (0.18)
kbmulti (0.08)
2047pp (0.04)
android (0.34)
icons (0.02)
inspire (0.03)
stopwatch (0.06)
smpltmr (0.09)
widmessages (0.06)
mylocation (0.11)
setting (0.71)
clkinfosunrise (0.05)
edisonsball (0.04)
sleepphasealarm (0.18)
widhr (0.01)
widclk (0.08)
widbthide (0.01)
clock_info (0.09)
sched (0.25)
alarm (0.47)
health (0.30)
hrm (0.13)
recorder (0.42)
messagegui (0.78)
sleeplog (0.17)

Yeah sounds like a regression by either #3317 or #3280, probably like you say, the wear/temperature one since the other was only merged recently. We could narrow it down by reverting to the version before the wear/temperature one - also do you see any console warnings in the IDE?

Good idea, thanks. I think it is related to #3280 because this night I tried the stable version of sleeplog without temperature checks again and it worked. I think it's good to first start reverting #3280 only and not the other PR to narrow it down.

Just as an extra data point: I've been using the SleepLog dev versions without any issues. I set it to 27 C the first day and haven't thought about it since.

Yes it's really strange. I'm now using the stable version of sleeplog from https://banglejs.com/apps/ and I get the same issues that I reported above. That makes me guess that it's unrelated to any of the recent code changes and might be an issue like in #3284 where the time format suddenly changed and the app stopped working. Maybe it's the same issue in sleeplog again and e.g. a firmware update caused new date formats.
I could try upgrading to the cutting edge firmware but I feel like I'll break much more with that.

I could try upgrading to the cutting edge firmware but I feel like I'll break much more with that.

That would probably be the quickest way to verify if it's the date thing. Cutting edge is stable the majority of the time - I virtually always run it. You can always downgrade to stable 2v21 again :)

Thanks for the info and great, I'll soon do that and report my findings here.

I had been on bleeding edge firmware and last night downgraded to 2v21.
It recorded that I was awake at 5am for an hour, which I don't remember. But otherwise it did record sleep the rest of the time I was asleep.

Have you enabled debugging and checked that maybe the thresholds are high enough? Maybe it considered some movement as awake.

Yeah, it was probably motion. I'm not worried about it, just mentioned since it was an oddity. But otherwise it seems to be working as usual for me.

Update: It seems to be related to another installed app, because I uninstalled a bunch of apps and now it seems to be working again (with higher thresholds). I'll try to figure out which app caused this.

I think this was due to changes I made in the health app in my own fork at https://github.com/espruino/BangleApps/compare/master...Ishidres:BangleApps:master#diff-f18170cb5895182061e4aef64b18f44328fc7ee1f84eedc3fdb623d82e1a8587. I replaced health with the stable app loader version and it seems to work, so I think this issue can be closed. Thanks for the help, guys.


[Material Design Icons] -> [Icons]

Added Material Design Icons within the icons section.
[Material Design Icons]
A icon collection allowing designers and developers targeting various platforms to download icons in the format, color and size they need for any project.
Link: https://materialdesignicons.com/
Checklist:

[x] I have performed a self-review of submitted resource and its follows the guidelines of the project.

https://materialdesignicons.com/


Add new MySqlConnector namespace

Fixes issue #402

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

LGTM, thanks for your contribution!


Image upload link to media.

Is it possible to allow the image uploaded through the 'image' field to link to the media file? I.e - When you click on the image it will link to the image.jpg?
Thanks!

Worked it out... just had to add the kirki option as a href above.


Run unit tests to make sure that each deleted portion is highlighted red.

rontend interface code output

already done


Update elastic-conventions plugin to use Develocity Gradle Plugin.

This silences various deprecation warnings seen when running the legacy Gradle Enterprise Gradle Plugin, and makes it possible to stop using the deprecated GE plugin in downstream repos.

Update the gradle-plugins build itself to use the Develocity plugin as well.

See e.g. https://elastic.slack.com/archives/C06TAHFDKNJ/p1729492136785869
To test this locally:

Run ./gradlew publishToMavenLocal
Then, make the following changes:

diff --git a/settings.gradle.kts b/settings.gradle.kts
index 20fe497..7a21188 100644
--- a/settings.gradle.kts
+++ b/settings.gradle.kts
@@ -1,6 +1,13 @@
 import co.elastic.gradle.vault.VaultExtension
 import java.io.File

+pluginManagement {
+    repositories {
+        gradlePluginPortal()
+        mavenLocal()
+    }
+}
+
 plugins {
     id("com.gradle.develocity").version("3.18.1")
     id("co.elastic.elastic-conventions").version(File("version-released").readText().trim())

Then, bump up the version-released file to the newer version (1.0.17)
Now run any Gradle command, e.g. ./gradlew tasks and confirm it no longer has any deprecation warnings caused by the use of the legacy Gradle Enterprise plugin. You should no longer see any of the following warnings:

WARNING: The following functionality has been deprecated and will be removed in the next major release of the Develocity Gradle plugin. Run with '-Ddevelocity.deprecation.captureOrigin=true' to see where the deprecated functionality is being used. For assistance with migration, see https://gradle.com/help/gradle-plugin-develocity-migration.
- The deprecated "gradleEnterprise.buildScan.buildFinished" API has been replaced by "develocity.buildScan.buildFinished"
- The deprecated "gradleEnterprise.buildScan.uploadInBackground" API has been replaced by "develocity.buildScan.uploadInBackground"
- The deprecated "gradleEnterprise.buildScan.server" API has been replaced by "develocity.server"
- The deprecated "gradleEnterprise.buildScan.obfuscation.ipAddresses" API has been replaced by "develocity.buildScan.obfuscation.ipAddresses"
- The deprecated "gradleEnterprise.buildScan.value" API has been replaced by "develocity.buildScan.value"
- The deprecated "gradleEnterprise.buildScan.background" API has been replaced by "develocity.buildScan.background"
- The deprecated "gradleEnterprise.buildScan.link" API has been replaced by "develocity.buildScan.link"
- The "buildScan.publishAlways" API has been removed, the updated Develocity "buildScan.publishing" API publishes a Build Scan by default

Once this PR is merged and (I presume) the new version is built, I will create a follow-up PR to bump the version-released file to 1.0.17. That is, assuming that's the established process.
See e.g. https://github.com/elastic/cloud/pull/133411 for an example of how a downstream repo can be updated to use the newer plugin and get rid of the deprecation warnings from the older Gradle Enterprise plugin.
Noteworthy release notes from the upstream plugin:

Build Scan: Resource usage observability in Build Scan
Build Scan: Configuration cache miss reason is captured
Build Cache: Increase parallel remote build cache operation limit

I just noticed the build never started:

This is probably because it's a public repo and it doesn't have spec.provider_settings.build_pull_request_forks: true set. Should I move my branch from my personal fork into elastic/gradle-plugins and create a new PR, or is there some other way to make it run a build for this PR (like making GitHub aware my repo is not technically third-party)?

You could either move it to the elastic namespace or go into buildkite and punch in refs/pull/<pr_num>/head as the commit.

You could either move it to the elastic namespace or go into buildkite and punch in refs/pull/<pr_num>/head as the commit.

Thanks, that worked. Unfortunately, the build failed with an error Error response from daemon: Get "https://registry-1.docker.io/v2/": unauthorized: your account must log in with a Personal Access Token (PAT) - learn more at docs.docker.com/go/access-tokens.
Just in case that was due to the branch coming from a forked repo, I also tried your suggestion of creating a PR from elastic/gradle-plugins directly but that build fails in exactly the same way. Did I perhaps forget to set up something else?

Yeah, it looks like its trying to login to the public dockerhub vs our internal docker hub.  Im having a look around to see what we can do to fix it.

Yeah, it looks like its trying to login to the public dockerhub vs our internal docker hub. Im having a look around to see what we can do to fix it.

I started a Slack question about this at https://elastic.slack.com/archives/C06TAHFDKNJ/p1730141290615289. Wondering if perhaps the pipeline should be updated to use secret/ci/elastic-cloud/container-registry/dockerhub?

Hi @nordbergm! Is this something you could take a look at? (I know you are OOO today but maybe tomorrow?)

Superseded by https://github.com/elastic/gradle-plugins/pull/99


chore: release main

:robot: I have created a release beep boop
critters-rs: 0.1.0
0.1.0 (2024-11-15)
Features

@critters-rs/critters: add basic tests (bf4f1f3)
add astro integration (ed7f770)
add basic CLI (1ce8a4e)
add biome for formatting/linting (df2f175)
add README.md (7ea48ed)
astro: add README.md (d9f5eda)
cli: add logging support (49c14b2)
cli: add progress bar (ff7d479)
initial commit (6bee6fe)
support building to WASM (add2ec1)
support external stylesheets (d4525a1)
update options to match critters (57873b3)

Bug Fixes

add artifacts command (f803ded)
add create npm dirs command (01cd933)
add packaging information to Cargo.toml (22ef2cb)
build: run cargo using childProcess.spawn (bd95f6a)
correctly inject font preload links (d844640)
critters-rs: remove superfluous slashes from regular expressions (ede2678)
critters/napi: enable logging (275daaf)
improved output path warning (35acadc)
utils: improve pairing function to avoid overflows (ac13deb)

Performance Improvements

parallelize processing of HTML files (a10389c)

critters: 1.0.0
1.0.0 (2024-11-15)
Features

@critters-rs/critters: add basic tests (bf4f1f3)

Bug Fixes

build: run cargo using childProcess.spawn (bd95f6a)

astro: 1.0.0
1.0.0 (2024-11-15)
Features

add astro integration (ed7f770)
astro: add README.md (d9f5eda)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

critters-rs-v0.1.0
critters-v1.0.0
astro-v1.0.0
:sunflower:


Standardise tag selection

It would be good to use the same UI for Audit log environment selection and flag tag selection.
IMO the Audit log UI looks better so we should copy that to the flag tagging UI

https://github.com/Flagsmith/flagsmith/commit/3e7a0ea4b66397b45cfd80d097053455fb4d7571


Potential problem updating MessageMetadata?

https://github.com/Alexandcoats/inx-chronicle/blob/ff39e54886ad148f35353b77bd3ef88021a662b5/bin/inx-chronicle/src/collector/mod.rs#L207-L209
What happens when we want to update the MessageMetadata for a Message that is not in the database yet?

We shouldn't do it. That could leave floating metadata around and that might be weird. The solidifier will request only the metadata if it is missing.

But the InxListener is listening for milestones and then eventually calls this method.
Consider the case of starting up Chronicle, where we could receive the metadata for a message that we didn't have the chance to listen to yet.

Nevermind, it won't throw an Error but rather the UpdateStatus would indicate that nothing changed.


Publishing Blazor to IIS from Visual Studio

When publishing a Blazor Server App (VS16.8.3/Net 5/EF Core) using a Visual Studio publishing profile and publishing to a local file directory, the web site fails to run giving a 500.19 internal server error (in this case, it appears to be looking for a web.config file which does not exist).
The documentation on this page is very lite with regards to publishing to IIS and I expect there is additional IIS configuration that is required to set up that environment - it would be great if this information could be documented as information found so far elsewhere appears to be out of date.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9b20b470-161a-8723-b66d-c0c1804874f0
Version Independent ID: 2712f7a2-90e7-0012-f7d9-f3a7e7e345d7
Content: Host and deploy ASP.NET Core Blazor Server
Content Source: aspnetcore/blazor/host-and-deploy/server.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @AndyWDev ... You're almost in the right spot. See the coverage in the Overview ...
https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/?view=aspnetcore-5.0&tabs=visual-studio
... You need to point IIS to the publish folder.
WRT improving this coverage ... Yes! I will. I'm working though all of the Blazor topics in the first half of this year. When I reach this node of topics, I will make improvements. To make sure that I don't lose your comment here, I've noted it on my tracking issue at https://github.com/dotnet/AspNetCore.Docs/issues/19286.

Hello @AndyWDev ... You're almost in the right spot. See the coverage in the Overview ...
https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/?view=aspnetcore-5.0&tabs=visual-studio
... You need to point IIS to the publish folder.
WRT improving this coverage ... Yes! I will. I'm working though all of the Blazor topics in the first half of this year. When I reach this node of topics, I will make improvements. To make sure that I don't lose your comment here, I've noted it on my tracking issue at https://github.com/dotnet/AspNetCore.Docs/issues/19286.

Hi,
Thanks for your reply.
I did find the web.config as per your post and IIS was already pointing to this directory.  I also set the app-pool to not use managed code.  I was still getting the error.
Next, I installed the IIS core (2.2 I think) for IIS, and then re-installed the .Net 5 SDK again in case my one too old.   I can now run the app in IIS, although for some reason my default page does not load (I get MainLayout and the Nav showing, but not my default content page - it does work when F5 debugging using IIS Express).
These are the things I meant by additional configuration.  I know they are mentioned in different places already, just not in one single place. :)

Hi,
Thanks for your reply.
I did find the web.config as per your post and IIS was already pointing to this directory.  I also set the app-pool to not use managed code.  I was still getting the error.
Next, I installed the IIS core (2.2 I think) for IIS, and then re-installed the .Net 5 SDK again in case my one too old.   I can now run the app in IIS, although for some reason my default page does not load (I get MainLayout and the Nav showing, but not my default content page - it does work when F5 debugging using IIS Express).
These are the things I meant by additional configuration.  I know they are mentioned in different places already, just not in one single place. :)

You did the right thing with a re-install of the hosting bundle and restart of IIS. You may have had an old ASP.NET Core Module that doesn't work well with the latest release.
WRT the default page not loading, I don't know why that would happen. I've never had that happen here. You can ask for help on the usual support channels. We recommend ...

Stack Overflow (tag: blazor)
ASP.NET Core Slack Team
Blazor Gitter

If you still can't figure out the problem, you can open a bug report with the product unit. It's best in this case to put up a repro project on GH and show them screenshots of your folder setup and IIS basic+binding configuration with a screenshot of the Index.razor page not loading. You would open that issue at
https://github.com/dotnet/aspnetcore/issues. I do recommend tho that you try to troubleshoot on your own first with the help of the community. They're crazy busy over there.
I'll work on the topics in this node when I reach them on the tracking issue. I'll review your remarks at that time.

You did the right thing with a re-install of the hosting bundle and restart of IIS. You may have had an old ASP.NET Core Module that doesn't work well with the latest release.
WRT the default page not loading, I don't know why that would happen. I've never had that happen here. You can ask for help on the usual support channels. We recommend ...

Stack Overflow (tag: blazor)
ASP.NET Core Slack Team
Blazor Gitter

If you still can't figure out the problem, you can open a bug report with the product unit. It's best in this case to put up a repro project on GH and show them screenshots of your folder setup and IIS basic+binding configuration with a screenshot of the Index.razor page not loading. You would open that issue at
https://github.com/dotnet/aspnetcore/issues. I do recommend tho that you try to troubleshoot on your own first with the help of the community. They're crazy busy over there.
I'll work on the topics in this node when I reach them on the tracking issue. I'll review your remarks at that time.

... one more note on ...

I know they are mentioned in different places already, just not in one single place. :)

Yes, Blazor docs will not go that far. You will need to access the IIS docs for general config. I think you know already where they are, but here's the link to that section of docs if you didn't see them ...
https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-5.0
What's in the Blazor docs Host and deploy node cover the concepts that apply specifically to Blazor.

... one more note on ...

I know they are mentioned in different places already, just not in one single place. :)

Yes, Blazor docs will not go that far. You will need to access the IIS docs for general config. I think you know already where they are, but here's the link to that section of docs if you didn't see them ...
https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-5.0
What's in the Blazor docs Host and deploy node cover the concepts that apply specifically to Blazor.

Update:  the not loading the default page was due to the application pool identity account not being set causing the DB connection to fail.
There isn't a bug as such -  there isn't enough [up-to-date] information documented (in one place) such that one can publish a Blazor app to IIS.  The issues that I encountered are symptomatic of this.

Update:  the not loading the default page was due to the application pool identity account not being set causing the DB connection to fail.
There isn't a bug as such -  there isn't enough [up-to-date] information documented (in one place) such that one can publish a Blazor app to IIS.  The issues that I encountered are symptomatic of this.

I understand, but I don't think we'll be going that way with the reference coverage. We don't want to duplicate the ASP.NET Core Host and deploy coverage in the Blazor topics. However, a tutorial for this scenario is worth considering. We have one for a garden variety ASP.NET Core app at ...
https://docs.microsoft.com/en-us/aspnet/core/tutorials/publish-to-iis?view=aspnetcore-5.0&tabs=visual-studio
... so I'll consider creating one like that for Blazor WASM or possibly make that tutorial cover Blazor apps. There's very little difference for Blazor apps. Once IIS is pointed to the right folder/web.config and the little bit of additional content is consumed and addressed, a Blazor app should run fine under IIS following the general ASP.NET Core guidance.

I understand, but I don't think we'll be going that way with the reference coverage. We don't want to duplicate the ASP.NET Core Host and deploy coverage in the Blazor topics. However, a tutorial for this scenario is worth considering. We have one for a garden variety ASP.NET Core app at ...
https://docs.microsoft.com/en-us/aspnet/core/tutorials/publish-to-iis?view=aspnetcore-5.0&tabs=visual-studio
... so I'll consider creating one like that for Blazor WASM or possibly make that tutorial cover Blazor apps. There's very little difference for Blazor apps. Once IIS is pointed to the right folder/web.config and the little bit of additional content is consumed and addressed, a Blazor app should run fine under IIS following the general ASP.NET Core guidance.


[Feature Request] Mouse Gestures Support

Many web browsers either natively support the use of mouse gestures or have extensions that enable this. (E.g. Vivaldi Natively, Microsoft Edge has an official Microsoft Web Extension for this).
A mouse gesture is the ability to hold a modifier key (commonly Right Click) and move the mouse in a direction, and upon letting go of the modifier, a command will be carried out.
Example use cases:

Hold Right Click, Move mouse down, then to the right to: close a tab.
Hold Right Click, Move mouse up, then to the right to: start a debug task

This could also be combined with a scrolling movement, as the editor Notepad++ Supports:

Hold Right Click, Scroll Up to: Cycle to the tab to the left of current

Another common use case is the Rocker Getsure:

Hold Right Click, Click Left to: Go back (alternative to Alt+Left)

More information:

Wikipedia: https://en.wikipedia.org/wiki/Pointing_device_gesture & https://en.wikipedia.org/wiki/Mouse_chording
Edge Extension: https://www.microsoft.com/en-us/store/p/mouse-gestures/9nblggh4nkf9
Vivaldi Implementation: https://help.vivaldi.com/article/mouse-gestures/

Duplicate of #3130


Github Actions Badge

Updated Github Actions Badge link to fix issue.

Looks like you want to rebase instead of merge? I squashed the previous PR down into 1 commit, so then you'd want to rebase to get this on top of the new commit without bringing along the rest of the history of that PR.


Pass this.$el on load

This PR fixes #69 . It passes this.$el to the emit event

There has been some rework for v2.0.0. Feel free to reopen with the change for new versions :)


python3Packages.bottle: 0.12.21 -> 0.12.23

Description of changes
https://github.com/bottlepy/bottle/releases/tag/0.12.22
https://github.com/bottlepy/bottle/releases/tag/0.12.23
bottle 0.12.21 can not be built with Python 3.11 because it uses deprecate function.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This will need to go to staging https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#rebasing-between-branches-ie-from-master-to-staging

I have rebased and retargeted to staging.


Fee insights :  fee insights aren’t accurate/relevant.

[ ] Fee insights :  fee insights aren’t accurate/relevant.

Duplicate of #5225


[Bug report] @vuepress/plugin-shiki not up to date

Bug report
Description
The @vuepress/plugin-shiki is about 10 months old and therefore has fewer themes and languages than the most up-to-date version of shiki. Is it possible to update the plugin please? https://www.npmjs.com/package/@vuepress/plugin-shiki

... is about 10 months old

Sorry? 😅

that’s embarrassing! I totally read the original creation date. Sorry about that 🤦🏻♂


Implement Nystrom approximation for approximate kernel methods

This is another important way to approximate kernel methods
See here for a reference implementation
This paper described the original method
This task is closely related to the random fourier features counterpart, #2768
and the incomplete cholesky one #3057

Hi I started looking at this. I have a pretty good idea of how to proceed. I can check in the irc if I have any questions.

Great. Let's start with kernel ridge regression and uniform sub-sampling.
We can add leverage scores for non-uniform sub-sampling later.
For now I guess we have to think a bit on how to best implement the nystrom + KRR. This needs some changes to the kernel machine I guess. Maybe we can add a Nystrom kernel machine class. This one can deal with the matrix inversions that are simpler for the approximated models. It would be good to do this high up in the hierarchy....but not 100% sure how to do it myself yet. Looking forward to your input :)
The same is actually true for the random fourier features #2768

Both this and Nystrom would start with KRR. KRR should put the method to solve the (K+\lambdaI)^-1 system in a method. A subclass would then overload this method and implement the cheaper matrix inversion for Nystrom or incomplete cholesky

Sounds like a good plan. I'll get back in a few days with hopefully some constructive input :)

You mean we refactor the current 'train_machine_pinv' method to put the matrix inversion in another method, which either calls lapack directly or carries out Nystrom in our subclass?
I wrote a short example implementing KRR. Getting somewhat more familiar with the code base.
Unfortunately I'll miss the reading group tomorrow since I'm moving house :'( Hoping to attend next time :)

There currently is a PR on changing the KRR internals a bit. The nystrom would just overload a single method in there.... #3098

this is a very good reference for the Nystrom method.
We should aim to reproduce the experiments (uniform Nystrom part for now) on the same datasets as in the paper. In addition, we should offer to compute the regularization path over the number of sub-samples as in Algorithm1 in the paper. This requires Cholesyk up and downdates

Thanks I'm starting to settle into my new place. I hope you had a nice Easter break.
Great thanks for the pointer I'll overload the new "solve_krr_system" method in my code.

Some inspiration https://github.com/LCSL/NystromCoRe

Thanks :) I implemented most of the class (called it 'CKrrNystrom' we can change that if you come up with a better name) now I'm going to override the 'solve_krr_system' method. I'll read in the data from the article as well and run some examples comparing with the original krr implementation.

A few test cases that are useful:

m=n should reproduce exactly the KRR result
m=0.9n should lead to a very small deviation compared to the true result

Good idea. I could add the first one (or both) to the unit tests.
Should the example I'm writing where I run both krr and nystrom be added to the 'examples' directory? Read that the example setup is about to change soon though.

Both in separate unit tests is best.
You can add an example, best would be a meta example I think. Check the cookbook readme.
Or you can modify the ipython notebook (or start a new one)

Interesting seminar at gatsby yesterday.
I have finished a first implementation of the solve_krr_system method. It compiles and runs.
My code does the following:

Add tau to the original kernel matrix (had to make m_tau protected instead of private in base class)
Create random vector through SGVector::random(0,n-1)
Sort vector
Picks out these columns/(rows) from the original kernel matrix to create K_{n,m} and K_{m,m} matrices (adjusting for the sampling not having been done without replacement).
Calculate eigenvalues and eigenvectors of K_{m,m} using Eigen3::SelfAdjointEigenSolver
Adjusting the eigenvectors to the approximate eigendecomposition for K_{n,n} as explained in Williams and Seeger
Invert the diagonal eigenvalue matrix to solve for alpha

Some pending items:

run examples on data from article (add data to shogun-data repository?)
various cleanup and check of code
write unit tests
write documentation
something else I haven't thought of

Other comments:

Shouldn't CKernelRidgeRegression::solve_krr_system() be virtual?

Happy to come by at some point :)

Good news!
Yes, the solve_krr should be virtual! :)
Could you send a PR? I am not sure I 100% get what you are doing there. I think we can do this without an (expensive) Eigenvalue decomposition, but just via LLT solving the K_mm.
What dimension does alpha have in your code? The Nystrom basically restricts optimization over the regressor so the space of functions \sum_i a_i k(x_i, .) where i=1...m -- so only the sub-sampled elements. See http://arxiv.org/abs/1507.04717
The apply methods also have to be adjusted as the support vectors (data that spans the regression function), etc. But we can start from the PR....
Looking forward to it!

Thanks for your comments.
Will do some minor cleanup then send a PR :)
My alpha vector currently has dimenstion n.

Hey I made a PR (don't know if I should connect it to this issue somehow).
To comment on your previous comment I am attempting to create an approximation to the entire original kernel matrix through an adjusted eigendecomposition of the reduced matrix, and then solve the system with all y's.
I haven't looked in detail yet at the other article by Rudi et al but was mostly using Seeger & Williams.

Thanks for the patch #3172
Looks good, don't get scared by the number of iteration we have to do -- that is totally normal :)

Thanks for the comments :) I'll look at it tonight.

Done for regression


Also interested in Go based pacemaker_exporter

Hi,
I read you are planning to port the Python pacemaker_exporter to Go. Great :-) ... I'd also be interested to be able to deploy a single binary. If you need testers, I'm in!
Cheers,
Andreas

Hi @akurz,
Could you please test this? What another metrics would you like to have?
Thanks!

Hi,
had a look at the metrics and this already looks great ... thanks for your efforts! One metric that would be really useful for us would be to know the number of migration/ban constraints.
Cheers,
Andreas

Hi @akurz,
Thanks for having a look at it. Would you mind sharing with me some crm_mon -X anonymized outputs I could work with? Please feel free to mail me directly or just uploading it to gist.
Best regards,
Mario


Regression tests failed with PG15/14

Hi,
When I run regression tests under PG15/14, it failed with following errors:
$ make installcheck
/home/japin/Codes/postgres/build/pg/lib/pgxs/src/makefiles/../../src/test/regress/pg_regress --inputdir=./ --bindir='/home/japin/Codes/postgres/build/pg/bin'    --inputdir=test --dbname=contrib_regression 00_init 01_oncommitdelete 02_oncommitpreserve 03_createontruncate 04_rename 05_useindex 06_createas 07_createlike 08_plplgsql 09_transaction 10_foreignkey 11_after_error 12_droptable
(using postmaster on Unix socket, default port)
============== dropping database "contrib_regression" ==============
DROP DATABASE
============== creating database "contrib_regression" ==============
CREATE DATABASE
ALTER DATABASE
============== running regression test queries        ==============
test 00_init                      ... ok           77 ms
test 01_oncommitdelete            ... FAILED (test process exited with exit code 2)      208 ms
test 02_oncommitpreserve          ... FAILED (test process exited with exit code 2)       24 ms
test 03_createontruncate          ... FAILED (test process exited with exit code 2)        6 ms
test 04_rename                    ... FAILED (test process exited with exit code 2)        5 ms
test 05_useindex                  ... FAILED (test process exited with exit code 2)        4 ms
test 06_createas                  ... FAILED (test process exited with exit code 2)        4 ms
test 07_createlike                ... FAILED (test process exited with exit code 2)        4 ms
test 08_plplgsql                  ... FAILED (test process exited with exit code 2)        4 ms
test 09_transaction               ... FAILED (test process exited with exit code 2)        8 ms
test 10_foreignkey                ... FAILED (test process exited with exit code 2)        8 ms
test 11_after_error               ... FAILED (test process exited with exit code 2)        5 ms
test 12_droptable                 ... FAILED (test process exited with exit code 2)        5 ms

========================
 12 of 13 tests failed.
========================

The differences that caused some tests to fail can be viewed in the
file "/home/japin/Codes/pg-extensions/pgtt/regression.diffs".  A copy of the test summary that you see
above is saved in the file "/home/japin/Codes/pg-extensions/pgtt/regression.out".

Here is complete errors.

Hi,
I found the PostgreSQL 12 has the same errors, it caused by this commit.


add GM Token

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address: DLFfDA3oATyUjw4PtJUUNzzDzvZQ9VVbTrrvteMXw67t
Token Name: GentleMonkiez
Token Symbol: GM
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>) https://raw.githubusercontent.com/GentleMonkiez/tokenlogo/decc7d709890c3cadfbe7a0f61ee8f43e4192ec4/GM-Token.png
Link to the official homepage of token: https://www.gentlemonkiez.xyz
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

I can help stop wasting your time refer this: #12970


Fix: Bitrise Templates has wrong indentation

Why

Currently, we can't usebitrise.yml since its workflow named deploy_staging is the wrong indentation.
test workflow is using a redundant step with Fastlane n_xcov.

Who Benefits?
iOS guys who are setting up a project 🥳

This was fixed in this PR


docker-compose.vite.yaml: version is obsolete

After run ddev start, there's a warning:
time="2024-07-16T14:50:04-06:00" level=warning msg="/mysite/.ddev/docker-compose.vite.yaml: version is obsolete"
It seems the version is not need it? https://github.com/docker/compose/issues/11628#issuecomment-2000072567
If you agree, you can remove the line 3 here: https://github.com/szenario-fordesigners/craft-vite-starter/blob/main/patches/docker-compose.vite.yaml

Removed in 713b574. Thanks for the notice :)

Release 2.0.1


BrokenPipeError: [Errno 32] Broken pipe

Hello everyone!
I get an error Broken Pipeline when using --do_eval.
Please help me to fix it.
Thank you a lot!

Hi hasontung1999,
I had the same problem, and still have it sometimes when running the evaluation scripts. I think it has something to do with the METEOR-evaluation module, which is written in java.
My way around this problem today is to run the evaluation notebook provided by /tylin/coco-caption/, and restart the runtime till the evaluation works.
I hope this helps. Maybe someone else has a better understanding of this problem.

Hi @jontooy ,
I had this problem when I did test and eval on Flickr dataset. I haven't tested on COCO (which is recommended by the authors), so I dont know if this problem also occurs or not.
I will try your approach. Thank you !


feat(localizations): Added German translation of deletePage section

Description
Add german translation for the deletePage localization.
Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[x] other: Localizations (added German translation for deletePage)

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[x] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Thanks for making the changes, we're nearly there.
As part of this PR we don't want to delete the package-lock.json file so you'll need to remove the file change from PR. Here are some instructions: https://stackoverflow.com/questions/39459467/remove-a-modified-file-from-pull-request
So my earlier comment was meaning: Drop the changes from the PR, not delete the file. Sorry if that was unclear :)

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Performance increase, bug fixes, and better exception handling.

Fixed issue with useEffect causing too many re-renders because of dependencies.
Moved exception handling for missing parameters to PanelContent.tsx.
Removed unnecessary headers from fetch.
Fixed express issue with missing next() function.

Need to commit files again.


[Android] Error after upgrading to 0.18/0.18.1 & clean install on device/emulator

Upgrading RN to 0.18/0.18.1 and got error below on real device/genymotion.

Click 'Reload JS' or press back button will throw new error.

Sometimes the error show 'Unable to connect packager'. So I think I should configure IP server in 'Dev Settings'.
I can open Dev Menu, but when I click 'Debug in Chrome' or 'Dev Settings', the app exit immediately. My console still running react-native start and no error.
[11:07:09] <START> Building Dependency Graph
[11:07:11] <START> Crawling File System
[11:07:11] <START> Loading bundles layout
[11:07:11] <END>   Loading bundles layout (1ms)

React packager ready.

[11:08:51] <END>   Crawling File System (100828ms)
[11:08:51] <START> Building in-memory fs for JavaScript
[11:08:52] <END>   Building in-memory fs for JavaScript (723ms) [11:08:52] <START> Building in-memory fs for Assets
[11:08:53] <END>   Building in-memory fs for Assets (747ms)
[11:08:53] <START> Building Haste Map
[11:08:53] <START> Building (deprecated) Asset Map
[11:08:54] <END>   Building (deprecated) Asset Map (421ms)
[11:09:02] <END>   Building Haste Map (9332ms)
[11:09:02] <END>   Building Dependency Graph (113372ms)

Tested on Mac and Windows machine.

+1

i solved by restart my package server. maybe you can have a try

Yes, it's work on emulator by restart package server, open app, then change 'Debug server host & port device'.
But it doesn't work on my phone. It's exit immediately if I click 'Debug server host & port device'.
Tested on phone: Xiaomi Redmi Note 3G (Android 4.4.2)
Previously no error occured on RN < 0.18.

i think it's the cache package,do you try rm all react-* in you $TMPDIR dir.and restart you server?  it works on my android phone

Hei @MrPluto, thanks for the response.
Unfortunately, it still doesn't work :/
What I've done is:

cd $TMPDIR
rm react-*
cd /go/to/project/folder
react-native start
check the app & still doesn't work
cd android/ && ./gradlew clean && cd .. && react-native run-android
react-native start
check again & still error :sob:

I've tested to my friend's phone (with the same Android version but Acer), and show the same errors.

try  just stoping  the package server and run-android directly ?

Still same error like the first post. It's weird because I can make it work and access 'Debug server host & port device' without crash on emulator.
Unfortunately, I don't have any iOS device. I also work on OS X Mavericks (10.9.5), so I'm unable to open Xcode 7 which is minimum version for setup iOS app.

I've experiment by creating init new RN 0.18 project and it's work on my device. It seems the problem caused by third-party plugins. I need more experiment to figure out the problem & will post it later.

can you tell me what's plugins you used?

  "dependencies": {
    "@remobile/react-native-splashscreen": "^1.0.3",
    "immutable": "^3.7.6",
    "moment": "^2.10.6",
    "react": "^0.14.6",
    "react-native": "^0.18.1",
    "react-native-accordion": "^0.2.4",
    "react-native-action-button": "^1.1.1",
    "react-native-activity-android": "^0.17.3",
    "react-native-dropdown-android": "^0.0.9",
    "react-native-fs": "^1.1.0",
    "react-native-gcm-android": "^0.1.9",
    "react-native-image-picker": "^0.10.0",
    "react-native-material-design": "^0.3.1",
    "react-native-mimetype": "0.0.7",
    "react-native-router-flux": "^2.1.3",
    "react-native-simple-store": "^0.1.0",
    "react-native-system-notification": "^0.0.8",
    "react-native-tabs": "^0.1.10",
    "react-redux": "^3.1.0",
    "redux": "^3.0.5",
    "redux-logger": "^2.3.1",
    "redux-thunk": "^1.0.3"
  },

i am not sure whether the plugins issue or not, i still think it's about the package. did you check the file when you upgrade? i mean they changed a lot android files in 0.18. sorry can't do any other help. please let me know if you catch this error :pray:

No problem, @MrPluto.
I've tried several experiments and now I've fix this problem by deleting file android/app/src/main/assets/index.android.bundle. I have been generate this file by doing curl "http://localhost:8081/index.android.bundle?platform=android" -o "android/app/src/main/assets/index.android.bundle" when I'm working project with RN 0.14.
You right. They changed a lot android files and also mechanism on bundling the script in 0.18. Anyway thanks for your assist :+1:

:beers:


E2vid integration refactor

Still wip.
Modifications on:

test_e2vid.py -> examples/reconstruction_e2vid.py
Many linting errors
Folder rectructure
Remove unnecessary options, Timers, etc.

Still mypy and test (on CPU) fails. I'm working on it.

This PR is toward your branch: e2vid_integration. So if I merge this PR your branch will be affected. @friedhelm-h

Just for me for clarification and future implementation. I can add # type: ignore behind a line to avoid mypy type hinting errors in that line? And how do you decide to do type hinting on a variable like here? Is there a rule?

I can add # type: ignore behind a line to avoid mypy type hinting errors in that line?

Yes. It is not ideal, but it can be a hotfix -- better refactor in future.

And how do you decide to do type hinting on a variable like? Is there a rule?

More ad-hoc for me. Sometimes mypy cannot infer the type of the member variable of the class etc. So I'm giving some hints for mypy then it won't complain. The way I fix the lint is quite debuggy.

mypy and tests pass now, I'm fixing the typeguard.


when Support .net core 3

You can use it in net core, since it support netstandard2

I've managed to compile and run it in .net core 3, even with the pathetic UWP. It will require a few modifications, but it works like a charm.


fix(http): remove view service

Closes #12245
Briefly describe your proposed changes:

[x] Rebased/mergeable
[x] Tests pass
[x] http/swagger.yml updated (if modified Go structs or API)
[x] Sign CLA (if not already signed)

@desa @goller  request a review.

Ping @goller  @desa


Added Atomic Mass Calculator

Fixes Issue🛠
Closes #1063
Description👨💻

Summary of Changes:

Implemented an Atomic Mass Calculator that calculates the atomic mass of a given chemical formula.
Updated HTML structure for a better user experience.
Improved CSS styling to give the web application a more modern appearance.

Issue Fixed

This PR addresses issue #1063: "Added Atomic Mass Calculator."

Dependencies

No external dependencies are required for this change.

Type of change📄

[x] New feature (non-breaking change which adds functionality)

How this has been tested✅

Verified the correct calculation of atomic masses for various chemical formulas, including H2O, C6H12O6, and NaCl.
Tested the input field to ensure it accepts valid chemical formulas.
Checked the responsive design to ensure the application displays correctly on different screen sizes and devices.

Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I am an Open Source Contributor

Pls work on these and make the changes by making commits in this same PR @bristiHalder

Add a Readme file of your calculator in your folder.
Add your calculator part in the main index.html file to display it on the website.
Attach the screenshot of your work here in the PR template above.

We already have Molecular Weight Calculator and your calculator is also doing the same @bristiHalder

It would have been helpful if you mentioned your existing calculator during the initial issue raised, as it could have provided context or clarified similarities sooner.

I can understand but I missed that. Contributors also must check the website, repository, and existing issues thoroughly before creating any issue @bristiHalder


Issues with Speaker Diarization

Can you help me with this error when doing SpeakerDiarization using pyAudioAnalysis:
from pyAudioAnalysis import audioSegmentation as AS
AS.speaker_diarization(filename='sample(3).wav', n_speakers=2)
These are the errors I get:
C:\Users\PycharmProjects\untitled\venv\lib\site-packages\sklearn\discriminant_analysis.py:469:
ChangedBehaviorWarning: n_components cannot be larger than min(n_features, n_classes - 1). Using min(n_features, n_classes - 1) = min(26, 19 - 1) = 18 components.
C:\Users\PycharmProjects\untitled\venv\lib\site-packages\sklearn\discriminant_analysis.py:469:
FutureWarning: In version 0.23, setting n_components > min(n_features, n_classes - 1) will raise a ValueError. You should set n_components to None (default), or a value smaller or equal to min(n_features, n_classes - 1).
Can anyone guide how to fix them

Getting the same problem here. Got any solution?

I have also the same problem. How can we solve it? please help

The only way I got it to work was by disabling flds in CLI or by setting 'lda_dim=0'

The only way I got it to work was by disabling flds in CLI or by setting 'lda_dim=0'

not work for me (


Replace qemu with Virtualization.framework

Suggest replacing qemu with Virtualization.framework

qemu -accel=hvf uses Virtualization.framework


Fix typos and apply C4LJ style for citations

Looks very good. Fascinating to read; I had to keep going backwards with an editor's eye as I got engrossed in the content.
This pull request fixes some typos and puts the references into the Code4Lib standard. The latter messes up the automated processing of your Markdown flavor. If that is of concern, maybe I can make a separate branch with those changes and apply them myself before copying and pasting the HTML into WordPress.
Also, I assumed the IBM research about the amount of digital content created in a day was the Ainsworth et al citation.  There was no explicit citation in the original text and it seems to make sense.

If you could merge what is there now, then fix the citation, that would be great.  If the Ainsworth citation doesn't go with the data size quote, then I don't see where it was used.  (Maybe it was part of an earlier draft and the citation didn't get removed from the reference list?)
My plan was to copy the HTML from the MacDown editor and paste it into WordPress.  That is probably the path of least resistance.  Let's try that before creating the separate pandoc derivative.

Yup!  I think I can do that.  Copy and paste HTML from the article itself, no?  ;-)

Great! Thanks @dltj – I'm really, really looking forward to seeing this in C4L, and your help is very much appreciated with this. Let us know if we can be of any help with this.


add an option to set custom root CA (#3519)

Closes 3519

What changed?
New option was added to specify custom Root CA path.

Why was this change made?
This change allows to communicate with OIDC provider with custom signed certificates.

How was this change implemented?
New CLI option is added. Helm chart changes are not included in this change - will submit a follow-up PR.

How did you validate the change?
All the unit tests passed.

Release notes

Documentation Changes

There is a simpler way to do this, you can mount the CA and then set SSL_CERT_FILE  to point to it.
<EMAIL_ADDRESS>This doesn't require any changes to the code.
The Helm chart supports it already, via extraVolumeMounts and extraVolumes and envVars.

Closing this as this is already supported in weave-gitops today. Thanks to @bigkevmcd for the tips.


zulip_bots: Enforce default config file schema.

In the end, I decided against removing the section name. While it is redundant, ConfigParser works only with sections and makes config parsing very convenient. This makes the change for the external bots to comply with embedded bots really straightforward.

Thanks @derAnfaenger!


general crayCC compilation failure

I am very interested to use this amazing JSON library for my project. However, I am virtually tied to using the Cray Compiling Environment (CCE) and the Cray C++ compiler (crayCC). I realise that what I am reporting below may well be outside the scope of the developer(s), and that moreover, CrayCC is not on the list of supported compilers. Yet I want to make mention of this, and leave it up to the author to decide what to do with this information. Any help would be appreciated!
I have constructed a minimal working example (hello world) which does absolutely nothing with JSON except include the single header file:
#include <iostream>
#include "nlohmann/json.hpp"

int main()
	{ std::cout << "hello world!" << std::endl; }

this program is compiled with either gcc 7.2.0 producing expected behaviour (hello world!), and with crayCC 8.6.5 (https://pubs.cray.com/content/S-2179/8.6/cray-c-and-c++-reference-manual-s-2179-86/about-the-cray-and-c++-reference-manual).
> CC hello_json.cpp

the output is:
/tmp/pe_38754/hello_json_1.o: In function `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release()':
/opt/gcc/6.1.0/snos/include/g++/bits/shared_ptr_base.h:147: undefined reference to `_ZN23_INTERNAL_b13fd261_main9__gnu_cxx27__exchange_and_add_dispatchEPii$$CFE_id_b13fd261_main'
/opt/gcc/6.1.0/snos/include/g++/bits/shared_ptr_base.h:162: undefined reference to `_ZN23_INTERNAL_b13fd261_main9__gnu_cxx27__exchange_and_add_dispatchEPii$$CFE_id_b13fd261_main'
/tmp/pe_38754/hello_json_1.o: In function `std::__shared_ptr<nlohmann::detail::input_adapter_protocol, (__gnu_cxx::_Lock_policy)2>::~__shared_ptr()':
/users/cpranger/garnet/experiments/json_compilation/hello_json.cpp:1: undefined reference to `_ZN23_INTERNAL_b13fd261_main9__gnu_cxx27__exchange_and_add_dispatchEPii$$CFE_id_b13fd261_main'
/users/cpranger/garnet/experiments/json_compilation/hello_json.cpp:1: undefined reference to `_ZN23_INTERNAL_b13fd261_main9__gnu_cxx27__exchange_and_add_dispatchEPii$$CFE_id_b13fd261_main'
/tmp/pe_38754/hello_json_1.o: In function `std::__shared_ptr<nlohmann::detail::output_adapter_protocol<char>, (__gnu_cxx::_Lock_policy)2>::~__shared_ptr()':
/users/cpranger/garnet/experiments/json_compilation/hello_json.cpp:7488: undefined reference to `_ZN23_INTERNAL_b13fd261_main9__gnu_cxx27__exchange_and_add_dispatchEPii$$CFE_id_b13fd261_main'
/tmp/pe_38754/hello_json_1.o:/users/cpranger/garnet/experiments/json_compilation/hello_json.cpp:7488: more undefined references to `_ZN23_INTERNAL_b13fd261_main9__gnu_cxx27__exchange_and_add_dispatchEPii$$CFE_id_b13fd261_main' follow
/tmp/pe_38754/hello_json_1.o: In function `std::unique_ptr<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >* nlohmann::basic_json<std::map, std::vector, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, long, unsigned long, double, std::allocator, nlohmann::adl_serializer>::create<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)::{lambda(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*)#1}>::~unique_ptr()':
/opt/gcc/6.1.0/snos/include/g++/bits/unique_ptr.h:236: undefined reference to `_ZZN8nlohmann10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerEE6createIS8_JRKS8_EEEPT_DpOT0_ENKUlPS8_E_clESJ_$$CFE_id_b13fd261_main'
/opt/cray/pe/cce/8.6.5/binutils/x86_64/x86_64-pc-linux-gnu/bin/ld: link errors found, deleting executable `a.out'
/usr/bin/X11/sha1sum: a.out: No such file or directory

FYI, _ZN23_INTERNAL_b13fd261_main9__gnu_cxx27__exchange_and_add_dispatchEPii$$CFE_id_b13fd261_main demangles to
_INTERNAL_b13fd261_main::__gnu_cxx::__exchange_and_add_dispatch(int*, int)$$CFE_id_b13fd261_main

and _ZZN8nlohmann10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerEE6createIS8_JRKS8_EEEPT_DpOT0_ENKUlPS8_E_clESJ_$$CFE_id_b13fd261_main demangles to
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >* nlohmann::basic_json<std::map, std::vector, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, long, unsigned long, double, std::allocator, nlohmann::adl_serializer>::create<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)::{lambda(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*)#1}::operator()(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*) const$$CFE_id_b13fd261_main

Please let me know if any more information is required!
Casper

It seems I cannot edit my own issue (older browser?), so I will add here that I am using the version I cloned this morning from the development branch.

That doesn't look like a json library issue, that looks like that the included system headers for the C++ standard std::shared_ptr is using compare-and-swap intrinsics (which is a good thing) that the compiler itself is not resolving.  This looks like an issue either with the compiler (less likely though to be honest) or with the standard libraries being used (this is the most likely issue).

Try compiling something like this using the same steps as you used above and tell what happens:
#include <memory>

void main() {
  std::shared_ptr<void*> test;
}

Thank you for your comment. You may well be right that this is a compiler issue. shared_ptr and unique_prt are used extensively throughout my project without any issues. Your provided test compiles neither in gcc version 7.2.0 nor with crayCC version 8.6.5 (nor in my head, to be honest), with crayCC complaining that:
  No operator "=" matches these operands.
            The operand types are:  std::shared_ptr<void *> =
                      std::shared_ptr<void *> *.
    test = &test;

and gcc making the same complaint in different wording. FYI, I believe the crayCC compiler is using the STL of gcc 6.1.0
Thanks again for your input,
Casper

Eh ignore the test = &test part, it was just a quick add to test equality but feel free to assign 0 to it.  ^.^;

I believe the crayCC compiler is using the STL of gcc 6.1.0

Yeah which is why it makes me thing that the json library is using shared_ptr more completely than your project...
It's definitely hard to tell though, I've never even heard of that compiler, I thought all other systems have basically migrated to clang backends by now instead of inventing their own compilers...  ^.^;

These are hard questions! The compiling environment is kind of opaque to me, so I can not really answer them at this moment. Since you are essentially suggesting that the issue is likely not with the JSON library, I have contacted support of the machine in question and will report back as soon as there is news! In the meantime, thank your for helping!
Casper

I'm exceptionally curious about this.  ^.^
Whatever you find out, please report back!  It 'could' indeed be a bug in this library but based on all information given thus far I'd bet hard money that it's not.  :-)

A helpful computational scientist working at the site of the machine came up with an interesting solution. While my original example didn't compile with crayCC, the following does:
#include <iostream>
#include "nlohmann/json.hpp"

int main()
{
    using nlohmann::json;
    auto a = std::make_shared<double>(5.0);
    std::stringstream ss1;
    ss1 << "[\"foo\",1,2,3,false,{\"one\":1}]";
    json j = json::parse(ss1);
    std::cout << "hello world!" << std::endl;
    std::cout << j << std::endl;
}

It is not clear to me why this would be necessary, and what the general underlying idea is of this fix (though I have asked for clarification on that). It seems that simply using the shared_ptr gets rid of the first few compilation errors, and that actually using JSON gets rid of the last. I'll have to see how this works out in my larger project since JSON will be an optional component, but this is a good start!

That... is very odd!  I'm quite curious in this bug...  What is that compiler doing...

@OvermindDL1, thank you very much for thinking with/for me! I have just implemented the fix posted above in my bigger project and it compiles fine now. Since at the moment I have no further information sources that could lead to a more general solution, I will close this issue. If I get any more feedback (from e.g. technical support of the machine) I will be sure to share!
All the best,
Casper


Add name property on PDFPageFormat

This PR allows retrieving the name of each page format i.e. A4, B3, US Letter etc.
The use case I had for this was wanting to give the user a choice in page format and needing a name to display to them.

Looks good, please change the destination branch to develop and rebase on the latest commit :)

Hi @philprime I noticed your master is much infront of develop.
I started my commit from master cause it was newer. Would you like me to start my branch from develop as well?

You are right, the develop was not updated, but it should not have mattered, because it was only the Ruby dependencies. develop is now up to date

I believe it should not matter anyways, as I will squash your PR

Sounds good 😄

Thank you for the contribution!


WICKET-6528 Don't block user when component not on Page using AJAX

Re-instate the behavior that was in versions < 8.0 that a component
added to an AjaxRequestTarget but is not part of the page, would be
ignored (or failed to refresh with an error in the JavaScript console).
So instead of always throwing an error, we only do so in DEVELOPMENT
mode causing an error page, and in DEPLOYMENT mode we only log the
fault, but don't break the application hard for the user: the component
refresh is ignored, just as it would've been in versions prior to 8.
Fixes WICKET-6528

Is merged with commit https://github.com/apache/wicket/commit/3be55cf5a24982cfca400225aabb6c4296859a7d


"Edit" button should save edited resource into the same folder

An external app which handles intents of EDIT type saves the modified file into random folder, defined in preferences of the app itself apparently. EDIT intent has no parameter to pass to the app to change this. It looks that it is also not easy for our app to know which folder was used to save the resource into.
It is desired to find the new version of modified file in order to track it in our tags system too. It could work with file system monitoring, but this might cause significant load on the operating system if do not specify a folder to monitor.

Solved by #203


[codegen] support optional fields with different conditions

Currently the mechanism we use to support optional fields only supports versions, and assumes that a higher version of a table always contains all the fields of previous versions.
This breaks with post, where 3.0 has fewer fields than 2.0. In addition, there have been a few other instances where we have something like this; for instance in lookup subtables, the markFilteringSet exists conditionally on the appropriate bit being set in the lookup flags.
Overall this would give us more flexibility in codegen, and save us hand-writing code.

That's actually an interesting complication for codegen, this is the first time where we will have a lower version of a table (2.0) that has more fields than a higher version (3.0). We make a bunch of assumptions about fields only being added with versions, so I'll have to think about this some.

Originally posted by @cmyr in https://github.com/googlefonts/fontations/issues/576#issuecomment-1680955670

This also applies to CFF INDEX objects. If the size is zero, the remaining fields are elided. Like lookups, we’re currently betting that these don’t exist at the end of a table, otherwise we’ll fail to parse.

support for fields conditional on a flag is added in #937


Missing ca-ceritficates causing error

I am getting a x509: certificate signed by unknown authority error on any dispatch. This might happen as I am using Let's Encrypt TLS certificates for the pushbits (gotify for matrix) instance for which the root certs are missing.
According to this (kind of random) issue I found on GitHub this might be related to the missing apk add --no-cache ca-certificates && update-ca-certificates in the image.

Thanks for the heads up, @CubicrootXYZ - that does sound about right. I'm pushing a new change right now that should address this! Please reopen the issue if you still have any issues :-)

Ran into this issue today. Ended up mounting the hosts certificates to get around it. Also using a Let's Encrypt certificate.
Tried getting a shell inside the container to see if I could run the apk commands manually to test, but couldn't get a shell with neither bash, ash, nor sh.


Feature: extensions for dat

@maxogden and I talked about adding extensions to Dat when we were making dat-push and dat-archiver. For example, a user could run dat list <args> and that would run the extension dat-list, a npm module.
Why Extensions?
Extensions will allow developers to quickly prototype and ship other features to dat (commit, push, etc.). This will help the core CLI library stay more stable while we add other beta features via extensions.
Implementation
I implemented extensions on this branch and published dat-list as a sample extension. Curious what everyone thinks!
As implemented, the arguments are passed to a function exported by the extension, e.g. require('dat-list')(args). Unfortunately, this means there is no really standard behavior for extensions (each could have their own argument order, options, etc.). We could also send a Dat instance from dat-js to make things more consistent but lose some flexibility for extensions.
Breaking changes!
The best way to do this is by requiring the user to specify the share and download commands, basically as first-class extensions. So Dat would ship with the commands:
dat share: share files
dat download: download files
dat doctor: run doctor extension (installed with dat)
dat <extension>: run another exension

Sounds like a great idea!
I'd say its probably fine for now to have no standard behavior for extensions except some basic flags that we might have already thought about, such as --version, --quiet, --debug. I'd be happy to also add one more, potentially, which would be --path  or --dir

I really like this too! I think it would be even more flexible if it weren't requiring extensions as modules but rather execute them as binaries. So $ dat list ARGS would spawn $ dat-list ARGS.

Yeah, this way people could write them in other languages, too, if they
wanted (??). Sounds like it'd be great to support both though in an ideal
world as there are trade offs.
El domingo, 28 de agosto de 2016, Julian Gruber<EMAIL_ADDRESS>escribió:

I really like this too! I think it would be even more flexible if it
weren't requiring extensions as modules but rather execute them as
binaries. So $ dat list ARGS would spawn $ dat-list ARGS.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/maxogden/dat/issues/506#issuecomment-242966381, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAmotF6mvXe7us6q2ODsC6Q600Z_CZ1lks5qkVxXgaJpZM4Juin-
.

--
Karissa McKelvey
http://karissa.github.io/
Dat Data
http://dat-data.com

Ya! Executing them as binaries sounds good. I updated my branch to try to execute the binaries directly, then if that fails try a local module.
I'm not sure if trying both is worth the tradeoff. It seems like locally install modules may be nice so we can add them as dependencies to Dat (like I was doing for dat-doctor), but that may not be a common thing for third-party extensions.


Adding express route port authorization apis

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Already approved by ARM previously: https://github.com/Azure/azure-rest-api-specs/pull/10491

Have left one comment. Please let me know if that field was added by mistake. Rest looks good

No actually the child resource as a property is intentional. Its help us to add and remove the child resource by doing a PUT on the parent. Data is not duplicated but rather a reference of the child is saved in the parent. NRP allows to serialize/deserialize the child resource at the time of parent GET\PUT. A similar property is “links” here which is also a child resource but also added as a property of parent.
Also a similar property called authorizations is already exists for Express Route Circuithttps://github.com/Azure/azure-rest-api-specs/blob/network-2021-08-01/specification/network/resource-manager/Microsoft.Network/stable/2021-08-01/expressRouteCircuit.json resource and we want the experience of Express Route Ports to be consistent with Circuit. Let me know if you have more questions.
Thanks,
Utkarsh
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: @.>
Sent: Saturday, February 5, 2022 5:07 AM
To: @.>
Cc: Utkarsh @.>; State @.>
Subject: Re: [Azure/azure-rest-api-specs] Adding express route port authorization apis (PR #17582)
Have left one comment. Please let me know if that field was added by mistake. Rest looks good
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F17582%23issuecomment-1030435397&data=04|01|utbarn%40microsoft.com|33418681153d469cce1b08d9e83737ec|72f988bf86f141af91ab2d7cd011db47|1|0|637796146204966499|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=TNcP2nlMJb7lDSvH58lweFc1zv3CBejFahjwh7N91cI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAP2NMIZW6WH3SHJPQMVXASTUZRPJFANCNFSM5NJIYDVQ&data=04|01|utbarn%40microsoft.com|33418681153d469cce1b08d9e83737ec|72f988bf86f141af91ab2d7cd011db47|1|0|637796146204966499|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=sDn%2FHIiE64cqmDZbfwymOkkCQM2rWvSmM7c%2BL3L8jto%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|utbarn%40microsoft.com|33418681153d469cce1b08d9e83737ec|72f988bf86f141af91ab2d7cd011db47|1|0|637796146204966499|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=c08%2B8tZCOupX9Bpo%2ByDopeU3kefTNZ4QACUEftQHBU0%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|utbarn%40microsoft.com|33418681153d469cce1b08d9e83737ec|72f988bf86f141af91ab2d7cd011db47|1|0|637796146204966499|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=KqKDgKAfLItqj2W3OzvNCgjzylm5JzH8aFpH1RwFi5E%3D&reserved=0.
You are receiving this because you modified the open/close state.Message ID: @.***>

Have left one comment. Please let me know if that field was added by mistake. Rest looks good

Responded.

@utbarn-ms - Thank-you: signing off from ARM perspective.


Support draft PRs

Is your feature request related to a problem?
No response
Describe the solution you'd like

*For pull requests, these metrics exclude the time the PR was in draft mode.

It would be nice if this tool supported tracking time from the moment draft PR is created in addition to other metrics (i.e. time from the moment PR is ready for review). In workflows, when draft PR is created ASAP when work on some issue is started, it would allow tracking cycle time of issues through associated PRs.
Describe alternatives you've considered
No response
Additional context
No response

This is a great idea!

Taking a look at this. Working on implementing a "track_draft_prs" env variable. WIP

PR ready for review: https://github.com/github/issue-metrics/pull/415


Eos voter

trying to figure out how to do this

If you're attempting to merge something to the repository, make sure you're using the develop branch and submitting your pull request there. The master branch is quite old at this point, as we've been working on rebranding eos-voter into Anchor and all that work happens in develop.


Ignoring exception in on_ready

This error appears to stop the bot from running, wonder if it's solvable.
2024-04-28 11:55:47 ERROR    discord.client Ignoring exception in on_ready
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/discord/client.py", line 441, in _run_event
    await coro(*args, **kwargs)
  File "/home/ajenbo/test.py", line 269, in on_ready
    await background_task()
  File "/home/ajenbo/test.py", line 255, in background_task
    await client.change_presence(activity=activity)
  File "/usr/lib/python3/dist-packages/discord/client.py", line 2040, in change_presence
    await self.ws.change_presence(activity=activity, status=status_str)
  File "/usr/lib/python3/dist-packages/discord/gateway.py", line 701, in change_presence
    await self.send(sent)
  File "/usr/lib/python3/dist-packages/discord/gateway.py", line 655, in send
    await self.socket.send_str(data)
  File "/usr/lib/python3/dist-packages/aiohttp/client_ws.py", line 151, in send_str
    await self._writer.send(data, binary=False, compress=compress)
  File "/usr/lib/python3/dist-packages/aiohttp/http_websocket.py", line 690, in send
    await self._send_frame(message, WSMsgType.TEXT, compress)
  File "/usr/lib/python3/dist-packages/aiohttp/http_websocket.py", line 601, in _send_frame
    raise ConnectionResetError("Cannot write to closing transport")
ConnectionResetError: Cannot write to closing transport

Why not create a script checking if bot is running and restarting it if it's not? :)

make it write stuff to a file every minute and the script would consume that file, if no file exists when script wants to delete it = restart bot? :P


CCDB AU/006 - Section <IP_ADDRESS>.3

Para 257 Para 259
Comment:
Text mentions developer selection of "common application developer" in 2 places.  I cannot see where this selection choice is present in the cPP.
Proposal:
Please check if "common application developer" is an outdated reference.
Priority: 1

duplicate of #12


Update FluentScanner.cs

I need argument information in the title for non struct objects this way it can be customized

Hi @paulschup , thanks for this pull request. Unfortunately, one of the tests is failing and the build is not passing. Please can you fix the broken test and add some tests for the new feature?


[BUG]: Create NPC nothing happens

Bug Description
Whenever I click the Create NPC button it briefly turns green and says connecting but nothing happens.

Steps To Reproduce

Click Create NPC

Foundry Version
v11.308
Additional Information
No response

hey there @CasualTerror, the free API seems to have been offline for quite some time now. In fact, I'm thinking of removing it in the next update and just leaving the OpenAI one.
If you want to try it, go to https://platform.openai.com/account/api-keys and create a private key to insert in the Foundry module settings. Keep in mind that the OpenAI API is not free (you will get free credit upon signing up), although it is very affordable.


update readme.md to accurately reflect supported python versions

Termgraph uses f-strings in termgraph/termgraph.py", line 327 and this means py3.5 is not supported. F-strings were introduced in 3.6

https://docs.python.org/3/whatsnew/3.6.html - F strings

Thanks for the contribution. :+1:
I merged this PR in 46af0072cf0805bef3aa59ac4612c0b050ad4b21


Document how to create a new environment

Document how to create a new environment. The process is as follows:

complete the prerequisites
create secrets for the new environment
create a new environment
deploy the Terraform modules and delete the configmap
create the Signon API token
check the environment is working

This looks good to me. Think it's fine to merge.


Add TestChild::ensure_dead to replace some kill calls

Version
Zebra main 2020-10-29.
Platform
Microsoft Windows Server 2019
10.0.17763
Datacenter
Description
The zebrad acceptance tests fail, because we try to kill a process that is already dead.
There is a race condition between the child process outputting the final matching log line and exiting, and the test runner matching the final log line and killing the process.
Instead of unconditionally killing the process, we should either:

try to kill the process, and ignore any "access denied" or "process not found" errors
check if the process is running, and then try to kill it

this implementation is worse, because there is still a race condition between the check and kill)

We should replace the kill calls:

in expect_stdout
in tests that use kill for cleanup only - that is, tests that don't call assert_was_killed

Here are the relevant log lines from:
https://github.com/ZcashFoundation/zebra/pull/1196/checks?check_run_id=1320727402#step:7:1397
Oct 28 13:15:04.974  INFO zebra_state::sled_state: stopping at configured height debug_stop_at_height=Height(0) called_from=OnLoad block_height=Height(0) block_hash=block::Hash("00040fe8ec8471911baa1db1266ea15dd06b4a8a5c453883c000b031973dce08")
Error:
   0: Access is denied. (os error 5)

Location:
   /rustc/18bf6b4f01a6feaf7259ba7cdae58031af1b7b39\library\core\src\convert\mod.rs:564

Command:
   "D:\\a\\zebra\\zebra\\target\\debug\\zebrad.exe" "-c" "C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\zebrad_tests.kFBL3T7ZCkLN\\zebrad.toml" "start"

Exit Status:
   command exited successfully with status code 0

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

   0: zebra_test::command::kill::comment with text=Killing child process
      at zebra-test\src\command.rs:163

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
                                ⋮ 10 frames hidden ⋮
  11: core::convert::{{impl}}::into<std::io::error::Error,eyre::Report>
      at /rustc/18bf6b4f01a6feaf7259ba7cdae58031af1b7b39\library\core\src\convert\mod.rs:564
  12: zebra_test::command::{{impl}}::context_from::{{closure}}<mut zebra_test::command::TestChild<tempdir::TempDir>*,tuple<>,std::io::error::Error>
      at D:\a\zebra\zebra\zebra-test\src\command.rs:376
       374 │
       375 │     fn context_from(self, source: C) -> Self::Return {
       376 >         self.map_err(|e| e.into())
       377 │             .map_err(|report| report.context_from(source))
       378 │     }
                                ⋮ 2 frames hidden ⋮
  15: zebra_test::command::TestChild<tempdir::TempDir>::kill<tempdir::TempDir>
      at D:\a\zebra\zebra\zebra-test\src\command.rs:164
       162 │     pub fn kill(&mut self) -> Result<()> {
       163 │         /// SPANDOC: Killing child process
       164 >         self.child.kill().context_from(self)?;
       165 │
       166 │         Ok(())
  16: acceptance::sync_until
      at D:\a\zebra\zebra\zebrad\tests\acceptance.rs:629
       627 │     // For example: "network=Mainnet" or "network=Testnet"
       628 │     child.expect_stdout(stop_regex)?;
       629 >     child.kill()?;
       630 │
       631 │     Ok(child.dir)

This is a bug which doesn't seem to come up any more.


How to know if the kafka stream is ready to starting consuming

Description
Hi!
We are making use of kafka-streams-dotnet library in a dotnet with a pretty simple config:
var streamBuilder = new StreamBuilder();
            streamBuilder.Stream<string, byte[]>(topic)
                .Foreach((k, v) =>
                {
                    // doing some async process with the message consumed (storing to a postgres table)
                });

            var topology = streamBuilder.Build();
            var streamConfig = new StreamConfig<StringSerDes, ByteArraySerDes>
            {
                ApplicationId = "test-app",
                BootstrapServers = bootstrapServer,
                NumStreamThreads = 1
            };
            var stream = new KafkaStream(topology, streamConfig);

            Console.CancelKeyPress += (o, e) => { stream.Dispose(); };

            await stream.StartAsync();

We are trying to test this consumer using test containers and xunit. We are successfully creating the kafka test container but we are facing some issues when consuming messages with the stream. These tests are producing some messages and the expectation is to see the process of them being consumed, but looks like the message produced by the first test is not being consumed.
While taking a look at the code I'm seeing logs like the following one:
1383 [test-app-stream-thread-0] INFO Streamiz.Kafka.Net.Processors.StreamThread - stream-thread[test-app-stream-thread-0] State transition from STARTING to PARTITIONS_ASSIGNED

// other logs related to the execution of the test

1436 [test-app-stream-thread-0] INFO Streamiz.Kafka.Net.Processors.StreamThread - stream-thread[test-app-stream-thread-0] State transition from PARTITIONS_ASSIGNED to RUNNING

And this leads me to think that maybe this first tests is running before the kafka stream is actually running and ready to start consuming. Worth to mention that the following messages produced by the tests are being consumed with no problem.
Question is: does my assumption sound correct? if so, is there a way to know that the stream is ready to consume messages? I'm also new working with dotnet and would appreciate any thoughts on how to make the tests wait until the stream is ready.
Thank you in advance!

Hi @DeaThrash,
First, you need to configure your offset reset policy to :
config.AutoOffsetReset = Confluent.Kafka.AutoOffsetReset.Earliest;

This configuration allow to reset offset to minimum when you consume a topic. (Doc: here)
Also I you want notify when your streams is running, you can make a little code like that :
bool isRunningState  = false;
var timeout = TimeSpan.FromSeconds(100);
            stream.StateChanged += (old, @new) =>
            {
                if (@new.Equals(KafkaStream.State.RUNNING))
                {
                    isRunningState = true;
                }
            };
            await stream.StartAsync();
            while (!isRunningState)
            {
                Thread.Sleep(100);
                if (DateTime.Now > dt + timeout)
                {
                    break;
                }
            }

// Your stream is running with partition assigned

Great! Thank you so much for the response, will try that approach.

Please feel free to close this issue if your question is done 😃


Date mask

I am trying to use ngMask in angular 1.3 with a Date object on the ng-model. It is not changing the output of the date in the input field. Is ngMask compatible with dates?

According to angular migration guide:
"types date, time, datetime-local, month, week now always require a Date object as model (46bd6dc8, #5864)"
Maybe this is causing the issue? Otherwise punker would be nice to reproduce the issue

NgMask is not compatible with date objects yet. I'm rewriting the mask to compress code, fix issues and use an functional approach. It will be covered in near future. However, ngMask 3.0.12 supports angular 1.3.xx (http://candreoliveira.github.io/bower_components/angular-mask/examples/index.html#/).


Make file descriptors into refcount references

fixes #3525
Remove fn dup in trait FileDescription, define struct FileDescriptor(Rc<RefCell<dyn FileDescription>>), and use BTreeMap<i32, FileDescriptor> in FdTable.

There are some refactors similar to the following form:
{  // origin:
    if let Some(file_descriptor) = this.machine.fds.get_mut(fd) {
        // write file_descriptor
        this.try_unwrap_io_result(result)
    } else {
        this.fd_not_found()
    }
}
{  // now:
    let Some(mut file_descriptor) = this.machine.fds.get_mut(fd) else {
        return this.fd_not_found();
    };
    // write file_descriptor
    drop(file_descriptor);
    this.try_unwrap_io_result(result)
}

The origin form can't compile because as using RefCell to get interior mutability, fn get_mut return Option<std::cell::RefMut<'_, dyn FileDescription>> instead of Option<&mut dyn FileDescription> now, and the deref_mut on file_descriptor: RefMut will cause borrow this as mutable more than once at a time.
So this form of refactors and manual drops are are implemented to avoid borrowing this at the same time.

Thanks for the PR! That was quick. :)

define struct FileDescription(Rc<RefCell>)

This sounds the wrong way around. Many file descriptors map to fewer file descriptions, not the other way around.

Awesome, I think we're done. :)
Please squash the commits together.

Thanks a lot!
@bors r+

:pushpin: Commit 41b5a1b4e8294fc620bb3f4450aa01859325add0 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 41b5a1b4e8294fc620bb3f4450aa01859325add0 with merge be0e91ebec475b6c7bf94a81b41db29ceb99c16a...

@Luv-Ray a possible next step, if you want, would be to give read and write access to ecx: &mut InterpCx<'mir, 'tcx, MiriMachine<'mir, 'tcx>>. This will be needed in the future to support blocking on these operations.
To make that work out in terms of borrowing, I think what we will have to do is clone the Rc in the read/write functions in unix/fd.rs, so that we have a fully owned FileDescriptor next to a uniquely borrowed InterpCx.

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing be0e91ebec475b6c7bf94a81b41db29ceb99c16a to master...

Thanks for review! I think I can give it a try on the next step.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1603 ms

Resolved: Bofrost.at performance has improved in 8342de2 after 1 hour, 7 minutes.


feature #858: disconnecting teachers from cathedras

added disconnectTeacherFromCathedra in TeacherService
added documentation in TeacherController

closes fictadvisor/fictadvisor#68

closed as outdated


(CSGO) Can't press F1 after exec slam

Neither F1 or F2, the buttons used to votekick, work after executing SLAM. This has been happening for 2 years at least and I never found a solution.
I always had F5 as my play button, I recently changed it to v and resetted my keybinds, yet still can't press F1. Control+f1 or FN+f1 doesn't work either.

I renamed all my many hundred tracks and found out certain names can cause this. Very weird.

I've had this problem too.
But it might be because CS:GO uses F1 and F2 for voting(yes/no).


IndexError: list index out of range   error  in Convert JMeter Results to JUnit Format task

My Azure devops pipeline is failing at the  Convert JMeter Results to JUnit Format step. I am getting the error below

Any idea what could be wrong?
Here is what the command line task responsible for the conversion of the JMeter Results file  to JUnit Format in my pipeline looks like

@allantargino @leonK-BO @EdiFirst please any suggestion what the issue might be?


Shift multi-callback management from OperationalDeviceProxy to CASESessionManager

Problem
Comments like this one reveal that clean-up of OperationalDeviceProxy instances on failure is just fraught with peril. Currently, callers of FindOrEstablishSession are responsible for releasing OperationalDeviceProxy instances on error. This is really error-prone. The ability for OperationalDeviceProxy to support multiple registered callbacks on the same instance complicates this story.
Proposal
Extending the idea in that comment, up-level the multi-callback management scheme in OperationalDeviceProxy to CASESessionManager. This simplifies OperationalDeviceProxy down to just managing a single callback, while permitting CASESessionManager to now take-over the responsibility of free'ing up the proxy instance on error, while still retaining the multi-callback capability of the high-level FindOrEstablishSession API.

FYI @msandstedt @bzbarsky-apple

So the CASESessionManager would need to keep track of which callbacks go with which proxy, right?  But yes, we could do that...

We use the SecureSessionTable and Sessions directly, so aren't exposed to any of this.  I defer to others on how OperationalDeviceProxy and CASESessionManager should work together.

Dupe of #19259


Changing Url

How can I change current Url on button click event?
I don't want to navigate to component onClick event, Just wanted to change Url
Example:
Current Url:
www.googl.com
New Url:
www.google.com/user/1

<Route render={({ history }) => {
  <button onClick={() => history.push('/the/path') }>click me</button>
}/>

Thanks @mjackson
Is it possible change
Example:-
www.google.com/user1/profile
to
www.google.com/user2/profile
without changing data in catche