help understanding bundle_adjust ancillary products

I have a quick question about bundle_adjust ancillary products.
How/Why is it possible for the “heights_above_datum” of {output-prefix}-mapproj_match_offsets.txt to be different from the same column in the {output-prefix}-final_residuals_pointmap.csv file? I would have expected those to be equivalent/close to each other.
In my specific case, the “heights_above_datum” from the mapproj_match_offsets are instead similar to the ones in the initial_residuals_pointmap (and similar to the initial DEM, when passing them through point2dem), while the final_residuals_pointmap has much lower “mean_residual” values (as expected) but the “triangulated DEM” looks very “different” (I would only expect a "rigid" transformation, but better/similar internal consistency, given the much lower residuals and the initial "decent" triangulations).
I attach here (from top left to bottom right): the "DEM" obtained by point2dem on the final_residuals_pointmap; the one from the initial_residuals_pointmap; the one from mapproj_match_offsets; the a priori DEM (the rotation between them should only be due to the reprojection inside point2dem).

Thanks for any hints in better understanding these files!

The height of points in {output-prefix}-mapproj_match_offsets.txt is an honest height on the DEM surface, or close to it. The algorithm is as follows (also in the doc): rays are shot from individual matching pixels. Intersections with DEM surface are found. Those are averaged. So, it cannot stray too far from the DEM.
For the pointmap.csv file, each triangulated point need not be on the DEM at all. Its primary job is to be consistent with the pixels back in the cameras, so it is close to the intersection of rays from those matching pixels.
The --heights-from-dem option can pull this triangulated point somewhat vertically towards the DEM, for a very low value of --heights-from-dem-uncertainty it will likely force it to be very close. This assuming that the DEM is well-registered with the cameras.
The reason the initial_residuals_pointmap and mapproj_match_offsets heights are close, is because initial_residuals_pointmap is initialized based on the DEM, if a DEM is passed with --heights-from-dem, but then it is allowed to drift somewhat given the uncertainty and and the constraint that it care first about minimizing reprojection error.
Does this make sense? Just how big is the discrepancy in your case?

Oh ok, that makes sense, thanks!
According to geodiff, after BA I have
Max difference:       27231.4 meters
Min difference:       3.86614e-07 meters
Mean difference:      72.7937 meters
StdDev of difference: 232.504 meters
Median difference:    38.9999 meters

the initial and mapproj geodiff residuals are very close to 0, which I now better understand with your explanation. My --heights-from-dem-uncertainty is set to 1 (meter).

This assuming that the DEM is well-registered with the cameras.

I should probably iterate to register the bundle-adjusted images to the DEM before making further BA iterations, then.
Also, this sentence in the manual:

This is an advanced metric that is only helpful if the images and DEM are known to be very well-aligned, while the DEM is very accurate.

made me wonder if the mapproj_match_offsets percentile residuals can be trusted only if the images (and thus the final heights_above_datum) are well registered to the reference DEM (e.g., to rely on them to locate poorly aligned images to be removed for further BA rounds).

Yeah, mapproj_match_offsets.txt relies on all cameras and the DEM to be well-registered together. And yes, if say 90% of your images have low stats, and the rest have high stats, it means that those with high stats are junk. But if a lot of your images have high stats,  that means your registration is not good.
The stats per image are in mapproj_match_offset_stats.txt.
In my experience with LRO NAC, some images just could not be registered. Those images looked washed out and acquired at a very oblique angle, I think. But most of them do well.

Yes, I usually remove any LRO NAC image with offnadir angle > 5 deg, to be on the safe side.
About the mapproj stats, most of the images have good ones (<1.5 meters when using 1 mpp mapproj images for BA), but even when "aggressively" cleaning up outliers (images with 2+ meters residuals, or even individual "connections" with residuals >2 meters), I still get regions with ghosting in my max-lit.
I also tried making "partial max-lits" by splitting the available images in quartiles based on their residuals from mapproj_match_offset_stats.txt, hoping that at least the best (and optimistically the second best) max-lit would show no ghosting, but they ended up looking quite similar (overall good, but with localized ghostings from misaligned images). Which made me wonder if I could rely on those residuals at all, or if I was in a setting when they are unreliable (e.g., when not properly registered to the DEM). So, I get that's not so critical for using those values in the end, right?

So, I get that's not so critical for using those values in the end, right?

No. The ultimate test is the lack of "ghosting", where apparently you have
problems.
I usually start with the images with the lowest mapproj stats, say the best
50 or so, and do the max-lit mosaic of those. If you still see
misregistration at that point, that means something is systematically bad.
A simple sanity check is to create a stereo terrain from a couple of those
bundle-adjusted images (with good convergence angle) and see if that
terrain has notable disagreements with your LOLA terrain (horizontally and
vertically). If yes, that means the alignment failed.
In the latest project I did I produced around 50 separate stereo DEMs from
pairs in the bundle-adjusted set, mosaicked them all, found the difference
from the mosaic to each, as sanity check, then aligned that one to LOLA and
applied the transforms to the cameras. (That still left around 5 m of
horizontal registration error, that needed finer-grained work.)
On Fri, Nov 1, 2024 at 8:57 PM Stefano Bertone @.***>
wrote:

Yes, I usually remove any LRO NAC image with offnadir angle > 5 deg, to be
on the safe side.
About the mapproj stats, most of the images have good ones (<1.5 meters
when using 1 mpp mapproj images for BA), but even when "aggressively"
cleaning up outliers (images with 2+ meters residuals, or even individual
"connections" with residuals >2 meters), I still get regions with ghosting
in my max-lit.
I also tried making "partial max-lits" by splitting the available images
in quartiles based on their residuals from mapproj_match_offset_stats.txt,
hoping that at least the best (and optimistically the second best) max-lit
would show no ghosting, but they ended up looking quite similar (overall
good, but with localized ghostings from misaligned images). Which made me
wonder if I could rely on those residuals at all, or if I was in a setting
when they are unreliable (e.g., when not properly registered to the DEM).
So, I get that's not so critical for using those values in the end, right?
—
Reply to this email directly, view it on GitHub
https://github.com/NeoGeographyToolkit/StereoPipeline/issues/444#issuecomment-2452845131,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKDU3F5VGL7OO2VOZWRVKTZ6REUDAVCNFSM6AAAAABRBI6IV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSHA2DKMJTGE
.
You are receiving this because you commented.Message ID:
@.***>

To add to previous:

Yes, I usually remove any LRO NAC image with offnadir angle > 5 deg, to
be on the safe side.

that probably throws quite some good data, I'd guess. Anything with up to
20-30 degrees off-nadir should still be fine. In either case, throwing out
data later is better than earlier, as for bundle adjustment as a rule more
images is better even if not great ones, as then more likely tiepoints are
found.
On Fri, Nov 1, 2024 at 9:12 PM Oleg Alexandrov @.***>
wrote:

So, I get that's not so critical for using those values in the end, right?

No. The ultimate test is the lack of "ghosting", where apparently you have
problems.
I usually start with the images with the lowest mapproj stats, say the
best 50 or so, and do the max-lit mosaic of those. If you still see
misregistration at that point, that means something is systematically bad.
A simple sanity check is to create a stereo terrain from a couple of those
bundle-adjusted images (with good convergence angle) and see if that
terrain has notable disagreements with your LOLA terrain (horizontally and
vertically). If yes, that means the alignment failed.
In the latest project I did I produced around 50 separate stereo DEMs from
pairs in the bundle-adjusted set, mosaicked them all, found the difference
from the mosaic to each, as sanity check, then aligned that one to LOLA and
applied the transforms to the cameras. (That still left around 5 m of
horizontal registration error, that needed finer-grained work.)
On Fri, Nov 1, 2024 at 8:57 PM Stefano Bertone @.***>
wrote:

Yes, I usually remove any LRO NAC image with offnadir angle > 5 deg, to
be on the safe side.
About the mapproj stats, most of the images have good ones (<1.5 meters
when using 1 mpp mapproj images for BA), but even when "aggressively"
cleaning up outliers (images with 2+ meters residuals, or even individual
"connections" with residuals >2 meters), I still get regions with ghosting
in my max-lit.
I also tried making "partial max-lits" by splitting the available images
in quartiles based on their residuals from mapproj_match_offset_stats.txt,
hoping that at least the best (and optimistically the second best) max-lit
would show no ghosting, but they ended up looking quite similar (overall
good, but with localized ghostings from misaligned images). Which made me
wonder if I could rely on those residuals at all, or if I was in a setting
when they are unreliable (e.g., when not properly registered to the DEM).
So, I get that's not so critical for using those values in the end, right?
—
Reply to this email directly, view it on GitHub
https://github.com/NeoGeographyToolkit/StereoPipeline/issues/444#issuecomment-2452845131,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKDU3F5VGL7OO2VOZWRVKTZ6REUDAVCNFSM6AAAAABRBI6IV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSHA2DKMJTGE
.
You are receiving this because you commented.Message ID:
@.***>

that probably throws quite some good data, I'd guess. Anything with up to 20-30 degrees off-nadir should still be fine.

you are right, but since at the lunar poles I usually have 1500+ images to "play with", a few off-nadir ones seemed more of a potential issue than a resource. In this case with fewer images though, I could relax that requirement.

No. The ultimate test is the lack of "ghosting", where apparently you have problems.

I meant that the bad registration is not "critical" to using the residuals from the mapproj_matches_offsets file as reference to identify bad images. For sure I need to solve those ghostings before SfS. :)
I'll try to be more granular by cross-checking with stereo DEMs, too, as you suggest. Thanks for all the explanations!

I ended up using around 1400 images. Kind of outrageous, yeah, but it was
hard to say ahead of time if registration will work with fewer. See how it
goes. Registration is grief.
On Fri, Nov 1, 2024 at 9:37 PM Stefano Bertone @.***>
wrote:

Closed #444
https://github.com/NeoGeographyToolkit/StereoPipeline/issues/444 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/NeoGeographyToolkit/StereoPipeline/issues/444#event-15076569131,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKDU3FAD4FBXFRWR5JJLYDZ6RJHNAVCNFSM6AAAAABRBI6IV6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGA3TMNJWHEYTGMI
.
You are receiving this because you commented.Message ID:
<NeoGeographyToolkit/StereoPipeline/issue/444/issue_event/15076569131@
github.com>


feat: use new unchained-client and chain-adapters types

Description

This consumes the new unchained-client and chain-adapter types from https://github.com/shapeshift/lib/pull/944

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
Contributes to the loose ends of the already closed https://github.com/shapeshift/lib/issues/658
Risk
None if CI passes
Testing
TODO
Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #2352   👈

PR #2257

This comment was auto-generated by Graphite.


keymap can be optional?

both refactor.{smart_rename, navigation} have default keymap table, user can only choose what key to use for a function, but can not choose whether to use that function.
some functions I really not need, such as navigation.list_definitions, but I still have to allocate a keymap to it, and the keymap is {noremap=true}
So is it possible to make a keymap optional? like:
{
    refactor = {
        navigation = {
            keymaps = {
                list_definitions = false,
            }
        }
    }
}

The noop key map should work here <nop>
On Sat, Jun 26, 2021, 3:24 AM 高浩亮 @.***> wrote:

both refactor.{smart_rename, navigation} have default keymap table, user
can only choose what key to use for a function, but can not choose whether
to use that function.
some functions I really not need, such as navigation.list_definitions,
but I still have to allocate a keymap to it, and the keymap is
{noremap=true}
So is it possible to make the a keymap optional? like:
{
refactor = {
navigation = {
keymaps = {
list_definitions = false,
}
}
}
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nvim-treesitter/nvim-treesitter-refactor/issues/23,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPXOSQOOIQ5AI3EPCIZSBTTUWFEPANCNFSM47LD6DIQ
.

This does not work for me when I set multiple mappings to this.
Works:
{
  foo = '<nop>'
}

Works:
{
  foo = '<nop>'
  bar = '<NOP>'
}

Does not work:
{
  foo = '<nop>',
  bar = '<nop>',
}

I used foo and bar as it doesn't matter which function I use here. My goal is to disable them all. I thought that it worked in the past by setting keymaps = { }, but apparently it gets merged now.


Duplicate Credit Card fields on slow connections

On slow connections there is duplication of the credit card fields.
It seems to make a second request from unzer.js after a delay, then loads in the duplicated fields.
Steps to reproduce:

Activate clean WP install with Storefront theme, no other plugins except this one and Woocommerce, set payment option as "Unzer Credit Card– Credit Card"
Load checkout page, with "Slow 3G" selected as the throttle in the Network tab

We are having the same issues as well 👀

hi, both,
Thanks for pointing this out. We will check on our end and get back to you.
In the meantime, if you have any more details, can you please raise a ticket for<EMAIL_ADDRESS>Thanks,
Unzer Plugins team

I raised the ticket with support :)
In assets/js/checkout.js the issue appears to come from the initCard() method being run multiple times.
Inserting a boolean flag which flips at the end of the method appears to correct the issue.

Hi, Chris Parker,
Can you please share the ticket no. for the Support issue?
We tested the card payment and need more details such as test shop credentials for your shop to check this.
Thanks,
Unzer Plugins team

Of course, it's #5692041

Hi, @parkster,
Thank you for your patience.
Please write to<EMAIL_ADDRESS>for further assistance and communication.
Regards,
Unzer Plugins team


Use local execution of verifiers

Stop using the livecode.ch servers to run the verifiers, because my bandwidth is limited. As a bonus, running the verifiers locally is faster!
@sibiraja, Can you try this on your setup, and tell me if it's OK to merge? Thanks!

Should be good!


Log all startup errors in KestrelServer

#1052
@cesarbs

:ship:

Startup exceptions in aspnet/hosting are logged as critical: https://github.com/aspnet/Hosting/blob/dev/src/Microsoft.AspNetCore.Hosting/Internal/HostingLoggerExtensions.cs#L66
Could you log this with level Critical as well? Seems to be the same severity and would make alerting a bit easier.

David once said that you try to avoid logging + re-throwing. Will this exception usually be handled by someone (hosting?) or does this blow up up the process anyway?

@cwe1ss this blows up the process assuming that the caller to WebHost.Start() doesn't catch the exception.
When investigating #1052, we discovered that the windows event log doesn't show the message from the exception that crashes a .NET process (even though it shows up in the console) which is the primary motivation for this change. Unlike with an application error, it's not possible to show some sort of error page to communicate to the developer what's gone wrong, since the server failed to bind to the listening address.
I think making the error critical makes sense though.

Thx for your reply!
I guess Critical sounds good in that case. But will this even be usable for people? I guess most people only add logger providers in their Startup.Configure method (because that's in the template). Will this be called before this error is logged?
Or will this only work, if you add an existing ILoggerFactory to the WebHostBuilder?

I've just realized that the server needs the built pipeline, so startup is called before server.start - so just forget my previous comment :)

Last thing: it's a detail but I think it's weird to sometimes use logger methods with 0 as the explicit eventId and sometimes not. unfortunately, aspnet/logging doesn't offer extension methods for cases that also receive an inner exception, that's why KestrelServer.cs now contains both versions.
I've created a PR for this some time ago - maybe you can take a look at it someday if you think this would be useful.

@cwe1ss IServer.Start() is called by WebHost after Startup.Configure completes, so Kestrel will log to whatever loggers are configured there.


unTab window does not open in previously opened tabs

Steps to replicate the issue

Open a couple of tabs in the web browser (we shall refer to these tabs as formers). Make sure that when these tabs are opened, unTab isn't added as an extension.
Now, add unTab as an extension.
Open some more tabs now (we shall refer to these as latters).

One could notice that upon trying to open the unTab window in the formers it does not open, however when we try to do the same in latters it works fine. What causes this issue?
A request to add the question label as welll to this issue.

The reason for this behaviour is following:

UnTab extension works by embedding a script on every page you open after it is activated (which let's us show the interface on top of the existing page)
In case of formers, this script does not get added as after UnTab is installed (it does not embed the script on old pages)
It is important to note that the embedding of script is taken care by the browser itself and it starts embedding the script in tabs opened after the extension is activated (which here is referred to as latter)

Hope that clears the question 🙂

Possible solutions to explore:

see if we can manually embed script on previously opened tabs(formers).
Check out #48 as it is very relevant to this and might be a reasonable solution considering other pages where this script can't even be embedded.

@blenderskool Thanks a lot for the explanation. That sure helped. I'll take a look at #48.


FAQ Q4 answer is no longer correct.

Q4 answer states:
Q: Can I enable single sign-on for only a subset of my Google Cloud / G Suite Connector by Microsoft users?
A: No, turning on single sign-on immediately requires all your Google Cloud / G Suite Connector by Microsoft users to authenticate with their Azure AD credentials. Because Google Cloud / G Suite Connector by Microsoft doesn't support having multiple identity providers, the identity provider for your Google Cloud / G Suite Connector by Microsoft environment can either be Azure AD or Google -- but not both at the same time.
However, this is no longer correct since SSO profiles can be selected per User, Organisational Unit or Group.

This is obviously beneficial to avoid scenarios where either Azure AD authentication is broken, potentially preventing Super Administrators from logging in, or where different Users, OUs or Groups require different Identity Providers.
In the example below I have a group defined in Google Workspace for which the SSO profile is "none". This prevents members of this (Google Workspace group) from being redirected to Azure AD for logon.

Thanks

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

ID: 3fdf59c4-653e-956e-d675-f7e17ed7d488
Version Independent ID: 57b9c048-a938-6e21-633b-e0aabdd59946
Content: Tutorial: Azure AD SSO integration with Google Cloud / G Suite Connector by Microsoft
Content Source: articles/active-directory/saas-apps/google-apps-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

The document was updating with suggested changes.
#please-close


Custom order for commands

lamin --help
gives the commands alphabetically ordered. I think that having them more semantically ordered would be better. The top most results should be login, init, load instead of cache, close, delete.
I'll tackle this if there are no objections.

Yes, please. It should also group the docs then. I raised this already a few a months ago somwhere.


Modify manner of (mainly) main menu

Changes appearance of main menu and sign up page.

Screenshots

Unfortunately, I can't test everything, so if there are visual quirks please let me know :)

Sorry for long wait, managed to completely forget this existed. Thanks for taking the time to make these changes!


Could use some basic reporting

Need a new dashboard page for some basic reporting:

Sales totals
Best sellers
Products Sold
Total Tax
Total Shipping

all should be filterable by date range

I'm going to start on this.

Hey-o @skybluesofa  - any update on this?

@skybluesofa haven't heard from ya so we'll start tackling this ourselves.

Done.


[Application-Token : opaque Token]Gateway is sending an expired backend JWT token to the backend

Description
The gateway is sending an expired backend JWT token to the backend endpoint, causing the endpoint call to fail. Upon investigation, it was found that this issue arises when the API is called using an opaque token (Application Token).
Steps to Reproduce

Configure the backend endpoint in the APIM to validate the expiry time of the received JWT.
Generate an opaque token and invoke the API with high TPS.
Occasionally, the APIM will send an expired token to the backend.

Affected Component
APIM
Version
4.0.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

Hi @piyumaldk ,
Please share the public fix and close this issue.
Regards,
Tharani.

Hi @Tharanidk,
We are still in the process of doing the fix for the latest version. Once it's done, will do the public fix.
Thanks and Regards,
Piyumal

Public fix - https://github.com/wso2/carbon-apimgt/pull/12497 (1st commit)


[MP] Fix broken RPCs after dictionary keys type change

As part of RPCs processing, they need to be sorted reliably across all peers, so that unique IDs can be assigned to greatly optimize the network layer.
The RPC configuration nodes are stored in dictionaries which, until recently (#70096), always casted StringName keys to String.
Since method names (keys) in the RPC configuration were StringName, a side effect of the above change is that sorting the dictionary keys no longer sort them alphabetically by default (StringName are compared using their pointers).
This commit changes the RPC processing logic to use sort_custom to provide a function that can handle the StringName comparison.
Fixes #96889
Regression from #70096

Thanks!


Client side HA with target_session_attrs

With libpq it is possible to specify multiple hosts and require a read-write connection. The client will connect all hosts until it finds the primary. This is a nice way to support HA on the client without a need to put a load balancer in front of the postgres cluster.
pg_auto_failover uses this feature for HA.
We can use SELECT pg_is_in_recovery(); to check if the node is primary or not and periodically check it to see if a failover happened and we need to find a new primary. default_transaction_read_only might also be needed.
Is there a way to achieve this with pgo?

Oh neat, there isn't a way to do anything like this in pgo today. Except for creating multiple pools and then checking which is primary and having some additional indirection of "use this pool" in your application.

As for finding a new primary, does an application really need to do anything like periodically checking? I'd expect that we'd be disconnected by the current primary and forced to reconnect if the cluster is re-configuring.

I don't think we'll get disconnected when the primary is changed manually while the old primary is still up.


[US] PostgREST API Testing and Documentation

As an application configurator, I want to be able to test the content of the API calls, so that I can validate the functionality of the VMD.

MoSCoW
Risk
Story Points

Should have
Low
8

Acceptance Criteria

Ability to test the Usecase's API

Risks

Adding complexity to the VMD

Tasks

[x] Meeting with the Stakeholder
[x] A big exploration of the Usecase's generated API, in order to design the Data Accessor URL builders inside the VMD.
[x] Complete documentation of the API in Mkdocs.
[x] Find a new framework for testing API calls (Postman may not be the route we wish to take, hence research possible testing options).
[x] Writing tests alongside the current Usecase 1.

Please see https://github.com/WillTrem/UInnovate/pull/298 for verifying what happened in this story, and if you have questions ask me :)


Error while running create-react-app command on windows 11 using WSL

Describe the bug
I have setup Ubuntu 20.04 LTS version on Windows 11 system using WSL2 feature.
Every time I am trying to run the command npx create-react-app, it is throwing error as shown in the screenshot.
I also tried installing the package globally using this command npm install -g create-react-app which works fine but after that running npx create-react-app still throws error.

When your using WSL/WSL2 make sure to use the Linux subsystem instead of Windows subsystem, so most of the features works out of the box like hot-refresh.
Try creating a new project inside the Linux subsystem.


Server Engine 2

Minimum changes for server engine to work

Note the build will fail because revel/cmd needs the changes merged as well

@notzippy How from revel.ServerWebSocket I can access *websocket.Conn?

@arvenil
In the Go server engine the ServerWebSocket is implemented by the structure *GoWebSocket inside that structure the native Conn *websocket.Conn lives. In code you can implement this like

func (a *App) EndPoint(ws *revel.ServerWebSocket) {
 // realWs is "golang.org/x/net/websocket"
 realWs := ws.(*revel.GoWebSocket).Conn
// Your code
return a.Render()
}


add konnectivity image annotation to allow the specification of regio…

…nal konnectivity images until the image is included in the openshift payload.

With the way we build our konnectivity image, the server and agent images are the same image.  So I'm not sure if we want to keep passing them separately.  But we can do that as part of a different PR.
/lgtm
/approve


Homuify libfontconfig

@bors-servo r+

:pushpin: Commit 59bd21f has been approved by glennw

:hourglass: Testing commit 59bd21f with merge 669bdf0...

:sunny: Test successful - travis


Enhancing / harmonizing dataset description

opening this issue to discuss if we can harmonize the dataset_description schema with the dandiset schema, which amongst several things, allows for all kinds of linked resources and better descriptors of contributors. it would still be bids 2.0.
example: https://api.dandiarchive.org/api/dandisets/000055/versions/draft/
these are all entered through a metadata editor ui, so people who don't know json can fill in things.
also see https://api.dandiarchive.org/api/dandisets/000008/versions/draft/ which has instances (see the relatedResource section) of the dataset being extended by data in two other archives.
the schema is also not just json compliant (and has a json schema attached) but also jsonld.
schemas are released here: https://github.com/dandi/schema/tree/master/releases

@satra may I move this to https://github.com/bids-standard/bids-2-devel or did you want to have it here for better visibility?

@sappelhoff - this would be bids 2 and we can definitely discuss there.  the main reason i posted this was related to @CPernet 's issue on the genetic dataset descriptors.
is there an active plan / timeline for bids 2?


Window tabs feature on non-macOS OS

I love using macOS Native Tabs but in last time i think of move to Windows 11 or Linux as both of them provides much more possibility for Docker, Gaming, Editing in one platform. Maintaining two or three machine isn't nearly comfort as maintaining single machine (updates, os updates, configs and etc)
But one thing stops me and it's Tabs, not files/editor tab, an Window tabs like already implemented in GitKraken.
Workspaces are nice but i love separate projects by Window and not looking file in left sidebar (many files in Explorer slow-downs me)

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


smpeg: 390 -> 0.4.5

change source to new upstream
http://svn.icculus.org/smpeg/trunk/
they moved to github
0.4.5 is revision 399 on svn
http://svn.icculus.org/smpeg?view=rev&revision=399
https://github.com/icculus/smpeg/tags
Description of changes

Things done

Built on platform(s)

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

[ ] 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

[ ] 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

[ ] Fits CONTRIBUTING.md.

change source to new upstream
http://svn.icculus.org/smpeg/trunk/
they moved to github
0.4.5 is revision 399 on svn
http://svn.icculus.org/smpeg?view=rev&revision=399
https://github.com/icculus/smpeg/tags

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

3 packages marked as broken and skipped:

hedgewars
python310Packages.rl-coach
python39Packages.rl-coach

1 package blacklisted:

appimage-run-tests

6 packages failed to build:

d1x-rebirth-full
d2x-rebirth-full
dxx-rebirth
naev
tuxpaint
worldofgoo

236 packages built:

SDL2_mixer
SDL_mixer
Sylk
_1oom
_20kly
abbaye-des-morts
abuse
alephone
alephone-durandal
alephone-eternal
alephone-evil
alephone-infinity
alephone-marathon
alephone-pathways-into-darkness
alephone-pheonix
alephone-red
alephone-rubicon-x
altair
anki-bin
anytype
appimage-run
apple-music-electron
asc
augustus
ballAndPaddle
barrage
beekeeper-studio
betterdiscord-installer
blobwars
blockattack
bloomrpc
bootstrap-studio
bottles
brutalmaze
btanks
buttercup-desktop
caprine-bin
cataclysm-dda
cataclysm-dda-git
cdogs-sdl
chocolateDoom
chromium-bsu
chrysalis
cider
commandergenius
cozy-drive
crack_attack
craftos-pc
crawlTiles
crispyDoom
crossfire-client
crrcsim
crypto-org-wallet
cuyo
davinci-resolve
devdocs-desktop
ecwolf
eduke32
egoboo
electron-mail
electronplayer
endgame-singularity
enigma
eternity
fheroes2
firefly-desktop
fish-fillets-ng
flare
flexoptix-app
freeciv
freedink
freedroid
freedroidrpg
frescobaldi
frogatto
frozen-bubble
fspy
gargoyle
gav
gemrb
gl117
gnujump
guile-sdl
guile-sdl2
heroic
hyperrogue
instead
instead-launcher
irccloud
itch
itch-setup
ivan
joplin-desktop
julius
jumpnbump
keeweb
kodiPackages.steam-launcher
lbreakout2
lbreakouthd
lbry
ledger-live-desktop
lens
liberal-crime-squad
lightspark
lincity_ng
liquidwar
losslesscut-bin
lpairs2
ltris
lunar-client
lutris
lzwolf
manaplus
mar1d
marktext
mathpix-snipping-tool
meritous
methane
minigalaxy
mobilecoin-wallet
molotov
mycrypto
neo4j-desktop
njam
notable
notion-app-enhanced
np2kai
nuclear
nxengine-evo
ocamlPackages.tsdl-mixer
octant-desktop
odamex
onscripter-en
opendune
openlierox
opensupaplex
openxcom
p3x-onenote
perl532Packages.SDL
perl534Packages.SDL
pinball
pingus
playonlinux
plexamp
pokerth
pokerth-server
powermanga
prboom-plus
protontricks
pysolfc
python310Packages.kivy
python310Packages.pyautogui
python310Packages.pygame
python310Packages.pygame-gui
python310Packages.pygame_sdl2
python310Packages.pygetwindow
python310Packages.pyrect
python310Packages.pysdl2
python310Packages.pytmx
python39Packages.kivy
python39Packages.pyautogui
python39Packages.pygame
python39Packages.pygame-gui
python39Packages.pygame_sdl2
python39Packages.pygetwindow
python39Packages.pyrect
python39Packages.pysdl2
python39Packages.pytmx
radicle-upstream
rambox
rambox-pro
raven-reader
redeclipse
remnote
retrofe
rili
rocksndiamonds
rott
rott-shareware
rrootage
ryujinx
saleae-logic-2
sauerbraten
session-desktop-appimage
sfrotz
simutrans
simutrans_binaries
smpeg
smpeg2
sonixd
space-cadet-pinball
srb2kart
ssb-patchwork
standardnotes
station
steam
steam-run
steam-tui
steamcmd
t4kcommon
taisei
tauon
tecnoballz
teetertorture
tennix
the-legend-of-edgar
timeular
toppler
torus-trooper
trackballs
trezor-suite
tumiki-fighters
tusk
tuxtype
ufoai
uhk-agent
uhk-udev-rules
ultrastardx
unityhub
vectoroids
vengi-tools
via
vial
video2midi
wargus
warmux
wesnoth
widelands
wootility
wpsoffice
xivlauncher
xmoto
ytmdesktop
zettlr
zod
zulip


[plugins/k8s][feat] Add deferred edges to digitalocean

Description
Added the deferred edges capability to the k8s collector. Linking to DigitalOcean resources is now possible.
To-Dos

[x] Add test coverage for new or updated functionality
[ ] Lint and test with tox
[ ] Document new or updated functionality (someengineering/resoto.com#XXXX)

Code of Conduct
By submitting this pull request, I agree to follow the code of conduct.

Codecov Report

Merging #921 (cff3f3e) into main (c017e45) will decrease coverage by 0.02%.
The diff coverage is 64.28%.

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

@@            Coverage Diff             @@
##             main     #921      +/-   ##
==========================================
- Coverage   90.25%   90.22%   -0.03%
==========================================
  Files          68       68
  Lines       10198    10202       +4
==========================================
+ Hits         9204     9205       +1
- Misses        994      997       +3

Flag
Coverage Δ

resotocore
90.22% <64.28%> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...tocore/action_handlers/merge_outer_edge_handler.py
89.02% <64.28%> (-3.29%)
:arrow_down:

Continue to review full report at Codecov.

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


 Recursion detected (same locals & position)
==== 1 failed, 21 passed, 1 skipped, 1 warnings, 2 error in 399.84 seconds =====

how do you run the tests?
see how travis does

I just checked the code out from github, ran "python setup.py install", and then ran
"py.test tests" or "cd tests ; py.test" - it should run out-of-the-box. All the components
like pytest-localserver, firefox, chromium, zope.testbrowser and splinter are up-to-date.
I'm having even more troubles with phantomjs and chrome - see
https://github.com/pytest-dev/pytest-splinter/issues/35
Can you try checking the code out from github in a bare test login,
and run "python setup.py install", and then run "cd tests ; py.test"?
I'm looking forward to using this under pytest-bdd.

preparation of the test environment is in the Makefile:
pip install -e . -r requirements-testing.txt tox coveralls

that's what you need to be able to run py.test tests
or just use tox command (from the root folder)


remove autocast for cpu

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
remove autocast for cpu

What is the current behavior? (You can also link to an open issue here)
we have autocast for CPU, which make arm64 vectorise speed slow

What is the new behavior (if this is a feature change)?
remove autocast for CPU now

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
no

Have unit tests been run against this PR? (Has there also been any additional testing?)
no

Related Python client changes (link commit/PR here)
no

Related documentation changes (link commit/PR here)
no

Other information:
no

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been added / updated (for bug fixes / features)

have you tested that this change improves arm64 vectorising speed?

yes, tested both on my mac and ec2 instance.


Fixed multiple interpolations in a property

related to #20 #21
This change enable to use multiple interpolations in a property at once.
  width: 20px;
  border: ${borderWidth} ${borderStyle} ${color};

is now translated to:
 width: 20px;
 border: $borderWidth -styled-mixin: borderStyle; -styled-mixin: color;

This changes above to:
 width: 20px;
 border: $borderWidth $borderStyle $color;

Cc: @mxstbr

Coverage remained the same at 99.333% when pulling 65eae1489ae0613da9850ff5c6be29154faee097 on taneba:master into 3c43e97f5678ece590cd6a284b0e943fc69073af on styled-components:master.

Coverage increased (+0.04%) to 99.375% when pulling 73ee889febbecab132d56fe8e116ce377942e087 on taneba:master into 3c43e97f5678ece590cd6a284b0e943fc69073af on styled-components:master.

I've refactored by following suggestion by @ismay
How about this?

Thanks for the update @taneba. To me this looks good. If there aren't any objections I think this is ready for merging.

Coverage increased (+0.04%) to 99.375% when pulling 217b0084f64d2976c6457e85c5526bec44d73b16 on taneba:master into 55b94d9d2d3f5c0c7617ce58134485bbafe0e85a on styled-components:master.

Thanks for the PR @taneba !


Fixed syntax highlighting for floating points in C#

Numbers regexp copied from c++.
Before:
float test = 1.0f;

After:
float test = 1.0f;

@isagalaev are you still maintaining this repo?


Fix bug #1516:

update logging instantiation codes to solve issue when invoke the tools/run-fbp-tests with --log option
refer to: https://docs.python.org/2/library/logging.html#module-level-functions

:+1:

I noticed there are CI fail when I re-commit.
By checking details, it seems the CI system got problem.

@otcyanglei I guess your patch is fine. I told the semaphore to try to build again.

+1

Thanks, Lei Yang.
PR merged


After updating to Pfsense 2.5.2 from 2.5.1 Zeek NSM no longer starts

Describe the bug
After trying to start zeek complains about /usr/local/logs not existing in an email sent. Have tried uninstalling and reinstalling and get error on install. Not sure if it is related to /usr/local/logs issue, as emails no longer arrive with this error. It now tries to start and fails. see below for more detail.
To Reproduce
Steps to reproduce the behavior:

In pfsense 2.5.2 uninstall Zeek package
Once uninstalled, install zeek package again.
see errors as below 'permission denied' during install although shows 'success'.
see error in status > system logs > system > general

php-fpm | 42909 | /rc.start_packages: The command '/usr/local/etc/rc.d/zeek.sh  start' returned exit code '1', the output was 'checking configurations  ... zeek scripts failed. fatal error: can't find local.zeek '

Expected behavior
Zeek to start without error
Zeek to install with out error?
Screenshots
If applicable, add screenshots to help explain your problem.
Version information (please complete the following information):

PfSense: 2.5.2
Zeek: 4.0.2
Zeekctl:
pfSense-pkg-zeek: 3.0.6_3

Additional context
>>> Installing pfSense-pkg-zeek...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 6 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	bash: 5.1.8 [pfSense]
	ipsumdump: 1.86 [pfSense]
	lbl-cf: 1.2.5 [pfSense]
	lbl-hf: 1.9 [pfSense]
	pfSense-pkg-zeek: 3.0.6_3 [pfSense]
	zeek: 4.0.2 [pfSense]

Number of packages to be installed: 6

The process will require 68 MiB more space.
13 MiB to be downloaded.
[1/6] Fetching pfSense-pkg-zeek-3.0.6_3.txz: ... done
[2/6] Fetching zeek-4.0.2.txz: .......... done
[3/6] Fetching lbl-hf-1.9.txz: ... done
[4/6] Fetching lbl-cf-1.2.5.txz: . done
[5/6] Fetching bash-5.1.8.txz: .......... done
[6/6] Fetching ipsumdump-1.86.txz: .......... done
Checking integrity... done (0 conflicting)
[1/6] Installing lbl-hf-1.9...
[1/6] Extracting lbl-hf-1.9: ..... done
[2/6] Installing lbl-cf-1.2.5...
[2/6] Extracting lbl-cf-1.2.5: ..... done
[3/6] Installing bash-5.1.8...
[3/6] Extracting bash-5.1.8: .......... done
[4/6] Installing ipsumdump-1.86...
[4/6] Extracting ipsumdump-1.86: ......... done
[5/6] Installing zeek-4.0.2...
===> Creating groups.
Using existing group 'zeek'.
===> Creating users
Using existing user 'zeek'.
[5/6] Extracting zeek-4.0.2: .......... done
Traceback (most recent call last):
  File "/usr/local/bin/zeekctl", line 814, in <module>
    sys.exit(main())
  File "/usr/local/bin/zeekctl", line 781, in main
    loop = ZeekCtlCmdLoop(ZeekCtl, interactive, cmd)
  File "/usr/local/bin/zeekctl", line 29, in __init__
    self.zeekctl = zeekctl_class(ui=self)
  File "/usr/local/lib/zeek/python/zeekctl/ZeekControl/zeekctl.py", line 73, in __init__
    self.config = config.Configuration(
  File "/usr/local/lib/zeek/python/zeekctl/ZeekControl/config.py", line 73, in __init__
    self.config = self._read_config(cfgfile)
  File "/usr/local/lib/zeek/python/zeekctl/ZeekControl/config.py", line 596, in _read_config
    with open(fname, "r") as f:
PermissionError: [Errno 13] Permission denied: '/usr/local/etc/zeekctl.cfg'
[6/6] Installing pfSense-pkg-zeek-3.0.6_3...
[6/6] Extracting pfSense-pkg-zeek-3.0.6_3: ......... done
Saving updated package information...
done.
Loading package configuration... done.
Configuring package components...
Loading package instructions...
Custom commands...
Executing custom_php_install_command()...done.
Executing custom_php_resync_config_command()...done.
Menu items... done.
Services... done.
Writing configuration... done.
=====
Message from zeek-4.0.2:

--
The rc.d script now honors the zeek_user rc.d variable.  To run as
a user other than root (the default) you need to make a few changes.
For example to run as the user zeek, add this to /etc/rc.conf:

    zeek_enable="YES"
    zeek_user="zeek"

Add this to /etc/devfs.conf:

    own     bpf     root:bpf
    perm    bpf     0660

And add zeek to the bpf group:

    bpf:*:81:zeek

and restart the devfs service:

    service devfs restart

or reboot.

If the interface defined in node.cfg is configured for NIC checksum
offloading (the default when this feature is supported by the
hardware) you will want to set ignore_checksums in site/local.zeek:

    redef ignore_checksums = T;
=====
Message from pfSense-pkg-zeek-3.0.6_3:

--
Please visit Services > Zeek NSM menu to configure the package.
>>> Cleaning up cache... done.
Success

The issue is due by the last version of Zeek FreeBSD port.
The quick workaround is to create the file from the sample file:
cp /usr/local/share/zeek/site/local.zeek.sample /usr/local/share/zeek/site/local.zeek
And rerun zeekctl deploy command.
Check #28

Thank you shadonet! I have applied work around and it is now working (started)! I assume the bug fix will end up for pfsense soon.

spoke too soon. New but related error via smtp:
User-Agent: ZeekControl 2.3.0
expire-logs failed
expire-logs: directory not found: /usr/local/logs/stats
creating directory for stats file: /usr/local/logs/stats
--
[Automatically generated.]

Thank you shadonet! I have applied work around and it is now working (started)! I assume the bug fix will end up for pfsense soon.

Yes! It has been fixed in the version 4.0.3_1 of Zeek port which is not yet available in the stable port tree.

commented too soon. New but related error via smtp zeek is still running though :

User-Agent: ZeekControl 2.3.0

expire-logs failed

expire-logs: directory not found: /usr/local/logs/stats

creating directory for stats file: /usr/local/logs/stats

--

[Automatically generated.]

I guess I could recreate the directory?

You could!

OK on trying to recreate the directory it already exists:
seeing as it says creating directory for stats file: /usr/local/logs/stats in the smtp message I totally missed it means what it says! I assumed it was an just an error but it was saying an error occurred as well as the fix! thanks again!


No way of disconnecting from Ethereum wallet in Console

Story
As a a user
**I want to be able to disconnect my Ethereum wallet
So that I can connect with a different wallet
Additional information
Go to deposit page https://console.fairground.wtf/portfolio/deposit
connect and do a deposit.
I now want to do a deposit from another Ethereum wallet (that I connect to via wallet connect)
but it re-establishes the connection with the previous wallet and gives me no way to change wallets.
e.g. from matamask mobile to conqbase mobile app

Also worth noting that the 'disconnect' function should be available on the withdrawal dialog, but is missing.

We can't disconnect nor change an account from the console level. It is possible only from MetaMask extension. Not sure about case when user is connected via WalletConnector, but it's sure when he uses second method, via MetaMaskConnector. It's true that MM connector exposes method disactivate which we use on disconnect button, but it changes only a flag of connection form active to not active. This flag/state would be possible to create something like simulation of session with the account. We could simulate for the user he is connected or not, but in truth he would be still the time connected to the same account and he coudn't change his account from console level.

If we can't disconnect from the front-end, then maybe the 'disconnect' button should just open a dialog that tells them to do it in MetaMask?

I think the key thing is the "...So that I can connect with a different wallet" in the user story.
See how uniswap allows you to hit the power button to disconnect.
Yes, when I hit connect to metamask again I am already connected, but I am able to select Coinbase wallet.
https://user-images.githubusercontent.com/13255539/205828075-a6217ec3-ab20-4d87-9e5c-503887f70084.mov


Setting particle ID in save_initial_distribution

The new version looks awesome.  One use case that looks like it might be missing is setting the particle ID numbers.  This is actually used by people in BBL, when they are looking at core charges vs. shield charges and what have you.  Its also useful for directly computing the particle trajectories (GPT has a method for that, but with easygdf, its basically just as easy to form the trajectories oneself in python).  Can this be added?  Or is it already there?  I didn't see it in:
save_initial_distribution(f, x=None, y=None, z=None, GBx=None, GBy=None, GBz=None, ...)
Saves GPT compatible initial distribution file. All array objects must be the same length (IE the number of particles). If required values (either {x, y, z, GBx, GBy, GBz} or {x, y, z, Bx, By, Bz}) are missing, easyGDF will autofill them with zeros. Only specify the momentum or the velocity of particles, not both.
Parameters
f: filename or open file/stream-like object
x (default: None): numpy array, particle position
y (default: None):numpy array, particle position
z (default: None):numpy array, particle position
GBx (default: None):numpy array, particle momentum
GBy (default: None):numpy array, particle momentum
GBz (default: None):numpy array, particle momentum
Bx (default: None):numpy array, particle velocity
By (default: None):numpy array, particle velocity
Bz (default: None):numpy array, particle velocity
t (default: None):numpy array, particle spawn time
G (default: None):numpy array, Lorentz factor
m (default: None):numpy array, particle mass
q (default: None):numpy array, particle charge
nmacro (default: None):numpy array, number of macroparticles
rmacro (default: None):numpy array, macroparticle size
creation_time (default: current time): int/datetime object creation time written to header (default: time when file is written)
creator (default: "easygdf"): string written to header
destination (default: ""): string written to header
gdf_version (default: (1, 1)): tuple (int, int) written to header. (Don't change unless you like messing with low-level stuff)
creator_version (default: (2, 0)): tuple (int, int) written to header
destination_version (default: (0, 0)): tuple (int, int) written to header
dummy (default: (0, 0)): tuple (int, int) written to header
max_recurse (default: 16): Maximum recursion depth while saving blocks in GDF file

Added in commit 6ca5cf110475631e2dcd0088b0150f5e46231335.  For some reason particle IDs were not mentioned in the GPT documentation used to make the function.
Also added ability to insert arbitrary named arrays into initial distribution files through keyword arguments just in case other important parameters are not included.


Change order of generated input elements in asp-for checkbox helper

When rendering a checkbox input. There is a hidden input with a false value rendered after the checkbox input. See the example below.
<input asp-for="Foo" type="checkbox"/>
Foo?

becomes
<input data-val="true" data-val-required="The Foo field is required." id="Foo" name="Foo" type="checkbox" value="true" />
<input name="Foo" type="hidden" value="false" />
Foo?

It is relatively common to style a label based on a checkboxes checked state e.g.
input[type="checkbox"] + label {
    /* style a */
}
input[type="checkbox"]:checked + label {
     /* style b */
}

The addition of the hidden input breaks this sort of selector.
I would suggest, putting the hidden input first (since it doesn't seem to matter which order the inputs are rendered in). So the above code would become:
<input name="Foo" type="hidden" value="false" />
<input data-val="true" data-val-required="The Foo field is required." id="Foo" name="Foo" type="checkbox" value="true" />
Foo?

@dougbu @DamianEdwards

See http://stackoverflow.com/questions/2860940/why-does-the-checkboxfor-render-an-additional-input-tag-and-how-can-i-get-the-v for an explanation and the history of this.

Solution:

The Html.CheckBox HTML helpers and <input type="checkbox"> tag helper will render only the checkbox inline
These helpers will not render the hidden input, and instead add it to the current form's context
The form HTML helper will render all the extra hidden inputs at the bottom of the form
A new "hidden" <form> tag helper (editorbrowsable=never) will capture all <form> elements regardless of attributes and its sole job is to render the extra hidden inputs at the bottom of the form
If the HTML/tag helper cannot find a form context then it will fall back to the current behavior of rendering the hidden input immediately after the checkbox

d40e6612a4e77f701fe99ceab40a238564fec238


[NEW SHEET] [En Garde]  from GDW / Small Furry Creatures Press

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x ] The pull request makes changes to files in only one sub-folder.
[x ] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is:  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: < GDW & Small Furry Creatures Press > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is:  (i.e. Dungeons & Dragons, FATE)
https://rpggeek.com/rpgitem/66957/en-garde

[X] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description
Initial release

Character Sheet Info Roll20 Internal Use only.


update meetings app in toc

Docs Build status updates of commit e12c689:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning
View
Details

msteams-platform/apps-in-teams-meetings/Design your meeting app/designing-in-meeting-dialog.md
:warning:Warning
View
Details

msteams-platform/apps-in-teams-meetings/Design your meeting app/designing-in-meeting-tab.md
:warning:Warning
View
Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:warning:Warning
View
Details

msteams-platform/TOC.yml

Line 62, Column 14: [Warning-file-not-found] Invalid file link: 'apps-in-teams-meetings/designing-in-meeting-dialog.md'.
Line 64, Column 14: [Warning-file-not-found] Invalid file link: 'apps-in-teams-meetings/designing-in-meeting-tab.md'.

msteams-platform/apps-in-teams-meetings/Design your meeting app/designing-in-meeting-dialog.md

Line 25, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-participant-view.png'.
Line 33, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-anatomy.png'.
Line 48, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-sizing.png'.
Line 58, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-position.png'.
Line 73, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-scroll.png'.
Line 111, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-steps-do.png'.
Line 119, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-steps-dont.png'.
Line 132, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-interactions-do.png'.
Line 136, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-interactions-dont.png'.
Line 143, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-tab-do.png'.
Line 151, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-tab-dont.png'.
Line 164, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-layout-do.png'.
Line 172, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-layout-dont.png'.
Line 185, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-size-do.png'.
Line 193, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-size-dont.png'.
Line 206, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-controls-do.png'.
Line 214, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-controls-dont.png'.
Line 236, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

msteams-platform/apps-in-teams-meetings/Design your meeting app/designing-in-meeting-tab.md

Line 24, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-organizer-view.png'.
Line 37, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-anatomy.png'.
Line 59, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-scroll.png'.
Line 65, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav.png'.
Line 97, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-before-meeting.png'.
Line 105, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-during-meeting.png'.
Line 118, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-theming-do.png'.
Line 126, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-theming-dont.png'.
Line 139, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-scroll-do.png'.
Line 147, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-scroll-dont.png'.
Line 160, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-layout-do.png'.
Line 168, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-layout-dont.png'.
Line 181, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav-do.png'.
Line 189, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav-dont.png'.
Line 202, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav-caution.png'.
Line 218, Column 3: [Warning-file-not-found] Invalid file link: '../tabs/design/tabs.md'.
Line 219, Column 3: [Warning-file-not-found] Invalid file link: '../tabs/design/tabs-mobile.md'.
Line 226, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md

Line 24, Column 143: [Warning-file-not-found] Invalid file link: 'designing-in-meeting-dialog.md'.
Line 266, Column 26: [Warning-file-not-found] Invalid file link: 'designing-in-meeting-dialog.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b50b112:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: Docs Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit b50b112:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/design-your-meeting-app/designing-in-meeting-dialog.md
:warning:Warning
View
Details

msteams-platform/apps-in-teams-meetings/design-your-meeting-app/designing-in-meeting-tab.md
:warning:Warning
View
Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/design-your-meeting-app/designing-in-meeting-dialog.md

Line 25, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-participant-view.png'.
Line 33, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-anatomy.png'.
Line 48, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-sizing.png'.
Line 58, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-position.png'.
Line 73, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-scroll.png'.
Line 111, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-steps-do.png'.
Line 119, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-steps-dont.png'.
Line 132, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-interactions-do.png'.
Line 136, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-interactions-dont.png'.
Line 143, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-tab-do.png'.
Line 151, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-tab-dont.png'.
Line 164, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-layout-do.png'.
Line 172, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-layout-dont.png'.
Line 185, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-size-do.png'.
Line 193, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-size-dont.png'.
Line 206, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-controls-do.png'.
Line 214, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-controls-dont.png'.
Line 236, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

msteams-platform/apps-in-teams-meetings/design-your-meeting-app/designing-in-meeting-tab.md

Line 24, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-organizer-view.png'.
Line 37, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-anatomy.png'.
Line 59, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-scroll.png'.
Line 65, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav.png'.
Line 97, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-before-meeting.png'.
Line 105, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-during-meeting.png'.
Line 118, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-theming-do.png'.
Line 126, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-theming-dont.png'.
Line 139, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-scroll-do.png'.
Line 147, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-scroll-dont.png'.
Line 160, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-layout-do.png'.
Line 168, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-layout-dont.png'.
Line 181, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav-do.png'.
Line 189, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav-dont.png'.
Line 202, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav-caution.png'.
Line 218, Column 3: [Warning-file-not-found] Invalid file link: '../tabs/design/tabs.md'.
Line 219, Column 3: [Warning-file-not-found] Invalid file link: '../tabs/design/tabs-mobile.md'.
Line 226, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md

Line 24, Column 143: [Warning-file-not-found] Invalid file link: 'designing-in-meeting-dialog.md'.
Line 266, Column 26: [Warning-file-not-found] Invalid file link: 'designing-in-meeting-dialog.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 9ce7dd3:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:x:Error

Details

msteams-platform/apps-in-teams-meetings/design-your-meeting-app/designing-in-meeting-dialog.md
:warning:Warning

Details

msteams-platform/apps-in-teams-meetings/design-your-meeting-app/designing-in-meeting-tab.md
:warning:Warning

Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:warning:Warning

Details

msteams-platform/TOC.yml

Line 367, Column 12: [Error-violate-schema] Error converting value "In-meeting dialog" to type 'System.Collections.Generic.List`1[Microsoft.Docs.Build.SourceInfo`1[Microsoft.Docs.Build.TableOfContentsNode]]'.
Line 368, Column 11: [Warning-file-not-found] Invalid file link: 'apps-in-teams-meetings/designing-in-meeting-dialog.md'.
Line 370, Column 11: [Warning-file-not-found] Invalid file link: 'apps-in-teams-meetings/designing-in-meeting-tab.md'.

msteams-platform/apps-in-teams-meetings/design-your-meeting-app/designing-in-meeting-dialog.md

Line 25, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-participant-view.png'.
Line 33, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-anatomy.png'.
Line 48, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-sizing.png'.
Line 58, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-position.png'.
Line 73, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-scroll.png'.
Line 111, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-steps-do.png'.
Line 119, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-steps-dont.png'.
Line 132, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-interactions-do.png'.
Line 136, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-interactions-dont.png'.
Line 143, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-tab-do.png'.
Line 151, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-tab-dont.png'.
Line 164, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-layout-do.png'.
Line 172, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-layout-dont.png'.
Line 185, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-size-do.png'.
Line 193, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-size-dont.png'.
Line 206, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-controls-do.png'.
Line 214, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-dialog-controls-dont.png'.
Line 236, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

msteams-platform/apps-in-teams-meetings/design-your-meeting-app/designing-in-meeting-tab.md

Line 24, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-organizer-view.png'.
Line 37, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-anatomy.png'.
Line 59, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-scroll.png'.
Line 65, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav.png'.
Line 97, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-before-meeting.png'.
Line 105, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-during-meeting.png'.
Line 118, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-theming-do.png'.
Line 126, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-theming-dont.png'.
Line 139, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-scroll-do.png'.
Line 147, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-scroll-dont.png'.
Line 160, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-layout-do.png'.
Line 168, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-layout-dont.png'.
Line 181, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav-do.png'.
Line 189, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav-dont.png'.
Line 202, Column 1: [Warning-file-not-found] Invalid file link: '../assets/images/calls-and-meetings/in-meeting-tab-nav-caution.png'.
Line 218, Column 3: [Warning-file-not-found] Invalid file link: '../tabs/design/tabs.md'.
Line 219, Column 3: [Warning-file-not-found] Invalid file link: '../tabs/design/tabs-mobile.md'.
Line 226, Column 3: [Warning-file-not-found] Invalid file link: '../concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md'.

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md

Line 24, Column 143: [Warning-file-not-found] Invalid file link: 'designing-in-meeting-dialog.md'.
Line 266, Column 26: [Warning-file-not-found] Invalid file link: 'designing-in-meeting-dialog.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


how to produce *.bnvib file

Hi CTCaer, I just wonder is there any means to produce *.bnvib file from wav file? I expect getting your help.

hey, if you still have the program could I take a look at it? I'm trying to make a midi to bnvib program myself and it'd be so much easier if I had something to work off of


database

Hi,
does anyone know how I can connect to the database and change staff name, I spelt it wrong :-(
Kind Regards
ET

@tigerbones24 as an admin user you should be able to edit any employee's name.

@tigerbones24 as an admin user you should be able to edit any employee's name.

@tigerbones24 as an admin user you should be able to edit any employee's name.

yes, I thought that as well but when you try to save it, it sats user exists already :-(

@tigerbones24 as an admin user you should be able to edit any employee's name.

yes, I thought that as well but when you try to save it, it sats user exists already :-(

Oh, I have figured it out, if you watch closely when you go into the record your will see that the email field changes from theres to your own email, if you correct the email to the staff's email, it lets you change it, just so your aware it then goes back to the admin email for some reason.
Kind Regards,
Tiger

Oh, I have figured it out, if you watch closely when you go into the record your will see that the email field changes from theres to your own email, if you correct the email to the staff's email, it lets you change it, just so your aware it then goes back to the admin email for some reason.
Kind Regards,
Tiger

Looks like browser is too smart:)

Looks like browser is too smart:)

Looks like browser is too smart:)

oh doaaaaaaaaaaaaaaaaahhhhhhh its my password manager hahaha, I feel silly now

Looks like browser is too smart:)

oh doaaaaaaaaaaaaaaaaahhhhhhh its my password manager hahaha, I feel silly now


Maketing

[ ] Producthunt
[ ] Awesome curation list
[ ] Zenn.dev
[ ] dev.to

https://dev.to/hiroga/aws-peacock-management-console-enables-to-change-console-color-as-you-like-9oa
https://www.producthunt.com/posts/aws-peacock-management-console-peacock
https://zenn.dev/hiroga/articles/aws-peacock-management-console-kodawari

if star counts become greater than 100, register to awesome list.


Missing License file

Even that we say in the package.json the license this project is using the text needs to be distributed with the code, otherwise there is no license being applied and people can't use this software because it is still closed.

Good catch! Created one.


FindEndpoints_LookedUpByCriteria_MultipleMatches weirdness

https://github.com/aspnet/Routing/commit/25b5ab2c3980569907d7c467dff185d00b9fbd64#diff-d27ab64c4b8a9e9cc5f4487c4b7f2864R227
FindEndpoints_LookedUpByCriteria_MultipleMatches is producing odd results. The same endpoint is returned 3 times. Is this expected?
Also the assert in the test is duplicated.
// @drieseng

@JamesNK is this already resolved?

Was fixed with https://github.com/aspnet/Routing/pull/910


CheckboxListTile is missing checkColor

Use case
The material Checkbox widget has a checkColor property.
The CheckboxListTile is missing this color, forcing the checkColor to be white.
Proposal
In some cases this would be useful to have.

Fixed by #37636


Failed to Initialize Starlight Project: NPM create command issue

What version of starlight are you using?
0.14
What version of astro are you using?
3.2.3
What package manager are you using?
npm
What operating system are you using?
Windows
What browser are you using?
Chrome
Describe the Bug
While trying to initiate a new starlight project using npm create (referring to link ) following errors came in screenshot provided

I switched to pnpm create but the process felt slower than usual.
Link to Minimal Reproducible Example
Not applicable
Participation

[ ] I am willing to submit a pull request for this issue.

something to clarify, the install dependencies step can be done later after the choose typescript by npm i command and the project works 💯

Update: npm create is functioning nicely now. pnpm create is better as well (though I might have become accustomed to it after running multiple times)
I could not replicate this issue further for recording purposes (sorry Hideoo 🙏)
I would ask to close the Issue as there are no further proofs for the Issue

I could not replicate this issue further for recording purposes (sorry Hideoo 🙏)
I would ask to close the Issue as there are no further proofs for the Issue

No worries at all, glad it's working for you now. I guess it was a fluke, maybe an internet connection one or on the side of npm, I guess we'll never know ^^
Thanks for following up and I'll close the issue.


implement persistent time index as zdx

Filling from discussion from https://github.com/brimsec/zq/pull/600 : When we're ready to create a persistent version of a zng time index, we can implement it as a zdx file, storing offsets to the zng streams, and using LookupClosest (or similar) in zdx finder.go to find the relevant section for a search.

Done in https://github.com/brimsec/zq/pull/1537 : for zar archives, we store a seek index that maps record time to file offsets.


No error raised if xml has only one failed row

Hi.
We are making some failure tests with spark-xml package within Databricks
We discovered that a xml file containing only one failing row will throw nothing.
Let me explain it with a simple example.
I've used your /tests samples for reproduction:
Here a good malformatted xml file:
<?xml version="1.0"?>
<catalog>
   <book id="Malformed attribute with " caracter ">
      <author>Kress, Peter</author>
      <title>Paradox Lost</title>
      <genre>Science Fiction</genre>
      <price>6.95</price>
      <publish_date>2000-11-02</publish_date>
      <description>After an inadvertant trip through a Heisenberg
      Uncertainty Device, James Salway discovers the problems
      of being quantum.</description>
   </book>
   <book id='I'm malformed too!'>
      <author>O'Brien, Tim</author>
      <title>Microsoft .NET: The Programming Bible</title>
      <genre>Computer</genre>
      <price>36.95</price>
      <publish_date>2000-12-09</publish_date>
      <description>Microsoft's .NET initiative is explored in
      detail in this deep programmer's reference.</description>
   </book>
   <book id="bk111">
      <author>O'Brien, Tim</author>
      <title>MSXML3: A Comprehensive Guide</title>
      <genre>Computer</genre>
      <price>36.95</price>
      <publish_date>2000-12-01</publish_date>
      <description>The Microsoft MSXML3 parser is covered in
      detail, with attention to XML DOM interfaces, XSLT processing,
      SAX and more.</description>
   </book>
   <book id="bk112">
      <author>Galos, Mike</author>
      <title>Visual Studio 7: A Comprehensive Guide</title>
      <genre>Computer</genre>
      <price>49.95</price>
      <publish_date>2001-04-16</publish_date>
      <description>Microsoft Visual Studio 7 is explored in depth,
      looking at how Visual Basic, Visual C++, C#, and ASP+ are
      integrated into a comprehensive development
      environment.</description>
   </book>
</catalog>

The test is using the FAILFAST option, but the default PERMISSIVE option will have the same behavior at the end.
So far, the test is:
# COMMAND ----------
file_location = "/FileStore/tables/books_malformed_attributes-345be.xml"

df = (spark.read.format("xml")
  .option("rowTag", "book")
  .option("mode", "FAILFAST")
  .load(file_location))

display(df)

and the expected result is:
SparkException: Job aborted due to stage failure: Task 0 in stage 42.0 failed 4 times, most recent failure: Lost task 0.3 in stage 42.0 (TID 73, <IP_ADDRESS>, executor 0): java.lang.IllegalArgumentException: Malformed line in FAILFAST mode: <book id="Malformed attribute with " caracter ">
      <author>Kress, Peter</author>
      <title>Paradox Lost</title>
      <genre>Science Fiction</genre>
      <price>6.95</price>
      <publish_date>2000-11-02</publish_date>
      <description>After an inadvertant trip through a Heisenberg
      Uncertainty Device, James Salway discovers the problems
      of being quantum.</description>

But now, if I have a file with only one failing row, like this:
<?xml version="1.0"?>
<catalog>
   <book id="Malformed attribute with " caracter ">
</catalog>

Now, with the same test, the expected result should be pretty the same as the last test, but unfortunatelly, the result is:
(2) Spark Jobs
df:pyspark.sql.dataframe.DataFrame
OK

Any thought ?
Additional question : Just to know, do you support the databricks option "badRecordsPath" ?

The issue here is that in the second example, <book> is never closed. It is never even considered a valid input to parse. You end up with no error because there is no input. If you close it, you'll find it throws an error as expected even with just one instance.
Now, arguably that should be an error. If a start tag is found, but no end, something's wrong. Right now it's silently ignored. I think I can see a way to implement it: return whatever text it found after the start tag, which will certainly fail to parse correctly later, and then PERMISSIVE/FAILFAST works.
There's a subtle issue here in any event. If an end tag is missing, it will keep reading. If it's followed by valid row tags, they are considered nested. It will just eat the rest of the file and not recover to parse the valid tags. Allowing nested row tags is a valid use case, so don't want to change that. At least one would get a real chance to handle the error with a change like the above.

Hey @srowen Thanks for the quick update and PR !
Awesome job.
Will make a new integration test once the 0.9 version will be available.
Thanks !

Shoudn't it throw an error if it can't find a start tag at all, i mean if a json file is there in the path instead of xml, it should throw and error
Atleast that how the .format('json') reader works

Good question. I hesitate to do it because, well, the current behavior is to just return nothing (which doesn't mean it's correct). The XML data source is a little bit different in that it's meant to potentially just examine a small subset of larger files in general, so maybe it's less unusual to accept not finding any row tags in input sometimes?
What I think we might want to do is throw an error if the schema is auto-inferred, but it's entirely empty. This doesn't seem like a meaningful outcome and could/should be an error?


Automatic scatter count detection

Description of feature
Implement automatic scatter count detection based on the BED file. This way the pipeline will run in the most efficient way

Added in #35


Update PetaPoco to Nuget Reference and fix TableName attribute bug

Summary
In PR #2764, we upgraded PetaPoco which caused our custom mapper, PetaPocoMapper, to never register at runtime. This caused all of our custom attributes to stop functioning.
namespace My.CustomModule.Data.Models
{
    [TableName("CustomModule_CustomEntries")]
    [PrimaryKey("Id", AutoIncrement = true)]
    [Scope("ModuleId")]
    public class CustomEntry : Entity
    {
        public string Title { get; set; }
        public DateTime Date { get; set; }
        public string Details { get; set; }
    }
}

Which would throw the following exception.
DotNetNuke.Services.Exceptions.ModuleLoadException: Invalid object name CustomEntry

This PR fixes that, and it also swaps out the direct local reference to PetaPoco to the Nuget package PetaPoco.Compiled and updates us again from v6.0.404 to v6.0.415. I also checked the license and it hasn't changed so we do not need any updates to the licenses folder.
TL;DR: GetMapper in v5.0.1 didn't have a default param and would return a StandardMapper instead of our custom PetaPocoMapper when the mapper wasn't registered yet. Now we are setting a new variable to be a StandardMapper and passing it into the GetMapper call.

@ohine thanks for the detailed explanations here, I have no issues with holding up this PR at all and the information you provided is very useful.


Update README.md

Just noticed that this is the wrong URL and it took me longer than I'd like to admit to find it

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Thanks @BakeryD. Could you please sign the CLA and I'll get this merged.

@BakeryD Just checking in to see if you can sign the CLA please?

Thanks @BakeryD. There can be a delay from signing to GitHub picking up the change. Will merge this in.


⚠ HopeAlley Ecards has degraded performance

In d73a68d, HopeAlley Ecards (https://hopealley.com/ecards) experienced degraded performance:

HTTP code: 200
Response time: 5882 ms

Resolved: HopeAlley Ecards performance has improved in 734127f after 6 minutes.


Multi-Architecture Builds on Debian

Accommodations need to be made for building across multiple architectures on Debian.
This needs to be be resolved before rolling Unibuild into production code.
This is possible on RPM but is a hassle.  We will likely need to build for aarch64 (which appears to be the same thing as armhf) since Alma supports it.
Determining Architecture
Two possible methods:
Explicit Configuration
Add a top-level file, maybe called unibuild-architectures, that dictates what architectures are cross-built:
# Packaging   Architectures (* = Adds the native architecture if not already explicitly specified)
deb           amd64 armel armhf *
rpm           *

Note that Debian's architecture name for Intel doesn't match uname -m, so the determination will have to be packing-specific.
Automagic
Let let which architectures are installed on the system be the driver of what's built, making system prep responsible for what architectures are supported.
# dpkg --add-architecture armel
# dpkg --add-architecture armhf
# dpkg --add-architecutre amd64
# apt-get update

# (dpkg --print-architecture && dpkg --print-foreign-architectures) | sort | uniq
amd64
armel
armhf

[MF] I like this method better because it doesn't require enumerating architectures in every repository.
Multi-Arch Build
Could use input from @tonin  on how this is accomplished.
Possibly-useful reference material:

https://wiki.debian.org/CrossCompiling
https://wiki.debian.org/Multiarch

Notes from a conversation with @tonin:
Problem
The concern about not duplicating effort stems from the fact that builds on non-Intel architectures are run under QEMU and run at about 20% of the speed of a native system.
This will probably become an issue with EL systems as well if we start building for ARM.
Solution
Unibuild will be modified to produce a copy of the build order as an artifact.  See #10.
The native (x86_64) build will do a full build of everything (binaries and sources).
The result of that build will trigger and be handed to separate Jenkins jobs that do builds for each architecture under QEMU.
That job will be consist of a non-Unibuild script that is given the entire set of artifacts from a native build and does roughly this inside the QEMU environment:
Create an artifact directory where the built packages will be stored.

For each package in the build order:

  If the package in the native build is architecture-independent:
    Copy the existing binary package from the native build into the artifact directory
    Continue

  Build the package from the source package (absent any involvement from Unibuild)
  Copy the resulting binary package into the artifact directory

Additionally to that, I think we'd want to keep a few more build artifacts, at the very least, the source package to build the other binaries.
What we currently publish to the public repository for a package named pkgname are the following files (for 4 different architectures):
pkgname_version-revision_amd64.deb
pkgname_version-revision_arm64.deb
pkgname_version-revision_armhf.deb
pkgname_version-revision_ppc64el.deb
pkgname_version-revision.debian.tar.xz
pkgname_version-revision.dsc
pkgname_version-revision_amd64.build
pkgname_version-revision_amd64.buildinfo
pkgname_version-revision_amd64.changes
pkgname_version-revision_amd64.deb
pkgname_version-revision_arm64.buildinfo
pkgname_version-revision_arm64.changes
pkgname_version-revision_arm64.deb
pkgname_version-revision_armhf.buildinfo
pkgname_version-revision_armhf.changes
pkgname_version-revision_armhf.deb
pkgname_version-revision_ppc64el.buildinfo
pkgname_version-revision_ppc64el.changes
pkgname_version-revision_ppc64el.deb
pkgname_version-revision_source.buildinfo
pkgname_version-revision_source.changes
pkgname_version.orig.tar.bz2

There doesn't seem to be much more that we can do on this from the Unibuild end.  Closing.


DEPLOY hyrax-5-upgrade branch to staging

Deploy hyrax-5-upgrade failed with:
 Error: UPGRADE FAILED: unable to build kubernetes objects from current release manifest: resource mapping not found for name: "hyku-***-hyrax" namespace: "" from "": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1"

Rob said he'll correct the version ingress which should allow for a successful deploy.
This will unblock us from starting the Hyku test plan.

try running the app locally in production mode to replicate

https://demo.hyku-demo.notch8.cloud/


Report iOS app readiness right after launch

When app launches, do not wait for app to become idle to report that app is ready. Readiness does not mean that app should be idle.

I don’t understand, why is this change submitted? From out investigation, this was necessary, and why we have it.

@LeoNatan having a hybrid app with native first screen, we don't instantiate RN context immediately. That means WXRNLoadIdlingResource doesn't become idle until we show screen with RN content, and the app doesn't report that it's ready until that. But we have no chance to advance from the native start screen to the RN screen because we can't run any test until the app is ready. It's like a deadlock.
And in the mentioned case, the app is ready to accept messages from Detox server, just it's currentStatus is not "idle". Anything that requires app to be idle will still not be executed until the app actually becomes idle.

This doesn’t sound right to me. WXRNLoadIdlingResource only becomes busy if a bundle starts loading. You can check the implementation yourself.  How did you determine it comes from WXRNLoadIdlingResource?

I’m closing this PR. If you see an issue in idling resources, please open an issue.

I see that grey_busyResourcesReturnEarly: returns set containing WXRNLoadIdlingResource. Changing notification name in waitForReactNativeLoadWithCompletionHandler: from RCTContentDidAppearNotification to RCTJavaScriptDidLoadNotification resolves the issue also, as long as we load RN bundle on start but don't display any RN content on first screen. Straightforward readiness report without waiting for app to become idle (which I submitted in this PR) works too.
I think the same problem was described in #615, but that issue is closed and the problem seems to remain relevant. I also think that I should've opened another issue instead of PR submission.
@LeoNatan what do you think about the two possible fixes I described? Maybe it's a good idea to choose RN notification name in ReactNativeSupport depending on type of application (we can specify app type in package.json).


[OSF-8007] Cancel changes button on admin preprint config

Purpose
When modifying preprint info on the admin page there's no way of discarding your changes, even if you restart the page everything is cached and your likely to forget your initial configuration. This fix gives the user a hard refresh in the form of a Discard button.
Changes
Add a new discard buttom with a js prompt that restarts the page without a cache.
Side effects
None that I know of.
Before

After

Ticket
https://openscience.atlassian.net/browse/OSF-8007

@brianjgeiger did you find any?

Hmmmm. I wonder if that was supposed to say, "Check on potential alternate implementations." If not, it probably should at this point. So: See if you can find a decent way to do that without, you know, writing a whole big thing for it. If this were a normal admin app, we could just enable the cancel button and be done with it. But if there's a quick, "store all the contents of these fields into a variable and, if the cancel button is hit, reset those fields to what they were when the page loaded" type of control, then yay. If not, we can go with this for now.

I checked on typical ways you might think to repopulate things with js nothing seemed remotely appetizing a lot of the data is templated server-side and not exposed to js anyway so rest assured this is the most palatable option for now.


the point dimension?

Hello ,the implementation only support clustering the points with two dimensions ?

Yes - but, in theory can be done for n dimensions - the logic is the same

It is on the todo list


Merge pull request #179 from linkwk7/s3_upgrade_checklist

Add 0.2.0 s3 upgrade checklist

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.7 out of 8 committers have signed the CLA.:white_check_mark: WillemJiang:white_check_mark: pswai:white_check_mark: tigerwangyb:white_check_mark: linkwk7:white_check_mark: Clark0:white_check_mark: wordhardqi:white_check_mark: gaodayue:x: cao.liu.lcao.liu.l seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Posts and Comments data delay?

Hi @Netherdrake ,
First, thank you very much for provide this amazing service: steemdata.com.
But in recent days, I could not fetch fresh posts and comments data.
There seems some delay of those two collections/tables.
For example:
I try run this command in python shell:

posts=db ['Posts'].find({'created': {'$gte': dateutil.parser.parse('2017-07-2 00:00:00.000Z')}})
print(posts.count())
0
And, Now, It's 2017-07-03 13:11 (UTC +0)

Could you look into this issue? Thank you very much for your help.

Im looking to deploy our own steemd node to fix the lag.


bug: vertical window splits do not size and resize as expected

Did you check docs and existing issues?

[X] I have read all the edgy.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of edgy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.1
Operating system/version
14.5
Describe the bug
Vertical splits do now size correctly.
Creating a vertical split normally has 50% width.
But with edgy it has the width ~1/3 on the right side.
Interestingly adding more v splits halfs the last split correctly.
Invoking resize equally has no effect then ( https://neovim.io/doc/user/windows.html#_6.-window-resizing )
Or am i missing something?

Steps To Reproduce

add vertical split ( CTRL-W v)
add another vertical split ( CTRL-W v)
resize equally ( CTRL-W = )

Expected Behavior
Adding splits should half the current space.
Invoking resize equally should make all buffers the same size.

Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "folke/edgy.nvim", opts = {} },
    -- add any other plugins here
  },
})

Weird, it seems to work in another project with different source files.
But does not work in the .lua project.


Improve jobstart

I heard that jobstart may get stuck in Vim, so I tried to improve it.
It may not be cured because it has not been reproduced.

Thanks a lot. I confirm that it works as well for my vim.