[CWS] add check in accessors for potentially out of range uint16

What does this PR do?
This PR makes sure the SetFieldValue checks the uint16 range when set from a potentially out of range value.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Hard coded projectUrl in Fossa plugin

Expected Behavior
configurable projectUrl, akin to sonarqube.baseUrl

Actual Behavior

projectUrl is hard coded
https://github.com/backstage/backstage/blob/f9e2ec25513ec8b746338b30ef3518b04e08d96c/plugins/fossa/src/api/FossaClient.ts#L107
Steps to Reproduce

add fossa configuration for target other than https://app.fossa.io/api, egproxy:
  '/fossa':
    target: https://mycompany.fossa.com/api
    allowedMethods: ['GET']
    headers:
      Authorization: token ${FOSSA_API_TOKEN}

add a component with fossa annotation
click the "view more" button on the component

Context

links from the backstage component page are broken
Your Environment

Browser Information:

Output of yarn backstage-cli info:

Seems like we should make this configurable, would you like to contribute this? :pray:


[INTERNAL] Validate scenarios with BTP and CF Terraform providers

What area do you want to see improved?
terraform provider
Is your feature request related to a problem? Please describe.
Validate scenarios with BTP and CF Terraform providers
Describe the solution you would like
Identify an document any known issues
Describe alternatives you have considered
No response
Additional context
No response

A terraformed version of this discovery center mission would be very nice.
Develop a CAP-based (multitenant) application using GenAI and RAG
https://discovery-center.cloud.sap/missiondetail/4371/4655/


onFail as result isn't calculated

in case:
    const nullOnError = onFail(() => null)(x, null);
    return [nullOnError];
    // or return {nullOnError};


PAPP-26546: Initial Commit

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[ ] Testing of all the changes has been performed (for bug fixes / features)
[ ] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[ ] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[ ] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ ] Verify all checks are passing.
[ ] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[ ] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Security Considerations (REQUIRED)

[ ] If you are exposing any endpoints using a REST handler,
please document them in the readme.html.
[ ] If this is a new connector or you are adding new actions

[ ] Please document in the readme.html all methods (eg, OAuth) used to authenticate
with the service that the connector is integrating with.
[ ] If any actions are unable to run on SOAR Cloud, please document this in the readme.html.

[ ] Are you introducing any new cryptography modules? If yes, please elaborate their purpose:
[ ] Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through
the Vault API.
[ ] Are you are marking code to be ignored by Semgrep with nosemgrep?
If yes, please provide justification in an additional comment next to the ignored code.

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

@pdesai-crest This action is running a variable number of playbooks. The plural "run playbooks" was correct. Please change it back in your feature branch.
This app is also intended to be available for all versions back to 4.9.0. Please change the minimum version back to 4.9.0.

In static test, Min Phantom Version 4.9.0 is required according to external contributor comment

@zamastyle Phantom version 5.2 is more stable and as per the standard process, we have to add min phantom version 5.2.0

static tests are failing due to min phantom version is kept at 4.9.0 as suggested by @zamastyle

Lots of debug statements - can the Crest team confirm that we are not leaking any info that isn't supposed to be logged. Thankss

Just as an assist I went through the debug statements and the only things being printed of significant note are these:
The ID for named repository from the asset (nothing interesting exposed)
The filtered output from rest/scm/ (nothing interesting exposed)
The cached json lookup of rule type to playbook name (nothing interesting exposed)
Playbook names from cache that will be executed during current run (nothing interesting exposed)
Definitely feel free to reach out to me if anyone has concerns about anything found while reviewing the debug lines

Lots of debug statements - can the Crest team confirm that we are not leaking any info that isn't supposed to be logged. Thankss

Just as an assist I went through the debug statements and the only things being printed of significant note are these: The ID for named repository from the asset (nothing interesting exposed) The filtered output from rest/scm/ (nothing interesting exposed) The cached json lookup of rule type to playbook name (nothing interesting exposed) Playbook names from cache that will be executed during current run (nothing interesting exposed)
Definitely feel free to reach out to me if anyone has concerns about anything found while reviewing the debug lines

We checked all the print statements and none of them seems to be logging any secret info


[feature] Option to always run the nightly rustfmt even if the default channel is not nightly.

If this option were enabled, then whenever RA formats the code it would format with the +nightly flag and you'd get the nightly formatter.
I'd like to use stable rust more often for peace of mind, and it's actually rustfmt rather than langauge features that are keeping me on nightly.

This should be possible using these config options:
https://github.com/rust-analyzer/rust-analyzer/blob/189ac4abbf6037419cb195c0a36a179544496ced/editors/code/package.json#L240-L259
probably just extraArgs: ["+nightly"] would work, but the overrideCommand should work for sure.
Optimistically closing this, feel free to reopen if this doesn't solve your issue.

ah excellent!


NuGet package does not exist :(

Can't find it at all

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

ID: e40394ca-9a55-d9b5-d427-7c2a2c00cfc8
Version Independent ID: 5a5c17e2-a683-88f6-07a9-2002e814d54c
Content: Live Reload - Xamarin
Content Source: docs/xamarin-forms/xaml/live-reload.md
Service: xamarin
GitHub Login: @pierceboggan
Microsoft Alias: piboggan

Thanks for reporting this; I can't find Xamarin.LiveReload at NuGet.Org either.  We're looking into this.

Hi there.  Just to add some clarity to this: The Xamarin.LiveReload package isn't available on nuget.org (which is why I couldn't see it there).  Instead, you have to make sure that you install Xamarin Live Reload VSIX.  The, in Visual Studio, when you go to add the Xamarin.LiveReload package, you have to make sure that the Package Source dialog is set to All (and not Nuget.org).  Then you should be able to search and install the Nuget package.

Good day,
The package Xamarin.LiveReload  does not appear, I have performed the steps as indicated by microsoft on your page and the result is the same ... please check the availability of the package so that we can make use of it in our application developments

@topgenorth , please check your sources in NuGet manager - you must have something special in there that we don't :) Or better yet, just move the package to NuGet.org and all will be ok.

@iforlife / @esarmientocoba : The only other tip/trick I can give you is to check the contents of the Package Source dialog. If you don't see Live Reload as a package source, then something went wrong with the VSIX installer.
If you're still unable to install LiveReload, the problem is more significant than an error in the documentation. Please go to   Developer Community and raise an issue there. We can't provide much technical support here as this repo is to raise issues/suggest improvements with documentation.
Sorry I couldn't do much more for you!

If you search for xamarin.livereload through Nuget Package Manager GUI the package isn't found. (Yes I have the pre-release check ticked on)
If you use the Nuget Package Manager Console and issue the command:
install-package xamarin.livereload -prerelease -project myprojectname
It installs fine.

In case anyone needs the package source url, it was this after installing: https://nugetized.blob.core.windows.net/live-reload/index.json

I found that tlhintoq comment worked for me.
Couldn't find the package in the GUI but Console approach worked.
Using VS 2017 15.8.0 Preview 3.0 (Enterprise VS)
LiveReload.Init();  LiveLoad recognised in App.cs
App built and run but no live update of UI on XAML  save.


Submitting the same transaction with the same seq num should fail with "seq num" error

Right now, if I submit the same transaction with the same sequence number, it says "already_finished".
Failing with "incorrect seq num" would be more correct.

I believe you're misunderstanding what "already finished" means.  It means that we looked at the transaction you submitted, and noticed that we have the exact same transaction already committed to the ledger.
You'll get a different error code if the transaction differs in any way from the transaction submitted at that sequence number.
This allows transaction submission to be idempotent, which in general is preferable, but is important in scenarios where it is tough to get a response from the server (for whatever reason):  simply continue submitting the transaction to the server until you get a response.  You need not query the ledger state after each submission, as you would if it were not idempotent.


<EMAIL_ADDRESS>hash check failed

ERROR Hash check failed!
App:         business/vscode
URL:         https://vscode.download.prss.microsoft.com/dbazure/download/stable/fabdb6a30b49f79a7aba0f2ad9df9b399473380f/VSCode-win32-x64-1.96.2.zip
First bytes: 50 4B 03 04 14 00 00 00
Expected:    e9a4af2c79c7a7c1208b5275ab7cc3709135153882a026a0418964dc9b65f387
Actual:      c6c2f97e5cb25a8b576b345f6b8f2021cc168f1726ee370f29d1dbd136ffe9f8

You are right. Thank you for reporting.


Make parsing of crs more lenient

At present, type property of crs is mapped to org.geojson.jackson.CrsType enum. This makes it challenging to parse GeoJSON containing crs.type value outside of those outlined by the spec (and present in the enum).
One such example is government WFS service that provides cadastral data here in Croatia. The crs property of GeoJSON returned by this service contains the following:
"crs": {
    "type": "EPSG",
    "properties": {
        "code": "3765"
    }
}

Attempting to parse such GeoJSON using something like:
JsonMapper.builder().build().readValue("""
        {
            "type": "FeatureCollection",
            "totalFeatures": 0,
            "features": [],
            "crs": {
                "type": "EPSG",
                "properties": {
                    "code": "3765"
                }
            }
        }
        """, FeatureCollection.class);

Fails with InvalidFormatException:
Cannot deserialize value of type `org.geojson.jackson.CrsType` from String "EPSG": not one of the values accepted for Enum class: [link, name]

Additionally, GeoJSON spec linked in introduction is obsoleted by RFC 7946 which actually removes crs from the spec. See Appendix B of the RFC:
Appendix B.  Changes from the Pre-IETF GeoJSON Format Specification

   This appendix briefly summarizes non-editorial changes from the 2008
   specification [GJ2008].

B.1.  Normative Changes

   o  Specification of coordinate reference systems has been removed,
      i.e., the "crs" member of [GJ2008] is no longer used.

All of this IMO supports the case for a more lenient parsing of crs in geojson-jackson.

Forgot to mention, I'm working around the issue by providing something like this as a replacement for org.geojson.FeatureCollection:
@JsonIgnoreProperties(ignoreUnknown = true)
record FeatureCollection(List<Feature> features) {

    @JsonCreator
    FeatureCollection(@JsonProperty("features") List<Feature> features) {
        this.features = features;
    }

}

Another, perhaps more elegant, workaround is to provide a mix-in that ignores Crs altogether:
@JsonIgnoreType
class IgnoreTypeMixin {
}

JsonMapper jsonMapper = JsonMapper.builder()
        .addMixIn(Crs.class, IgnoreTypeMixin.class)
        .build();


Text selection format should be consistent

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to login screen
Select autofill email
Select the email

Expected Result:
Text selection formatting should be consistent
Actual Result:
Text selection shows cursor and selection in white.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[x] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.2.90-6
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/228711610-48b7aeeb-e10f-4092-aa85-1d541f4f8f2f.MP4
Expensify/Expensify Issue URL:
Issue reported by: @dinaljivani
Slack conversation:
https://expensify.slack.com/archives/C049HHMV9SM/p1679989314785349
View all open jobs on GitHub

Triggered auto assignment to @muttmuure (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

📣 @alitoshmatov! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.

 Thank you for contributing to Expensify!

I reproduced issue in ios emulator(iphone 14 pro max, ios 16.2) any input field including login, search, personal details has white cursor when selected

I don't think this is a bug and auto-fill behavior is outside of our code.


Reduce the initialization of runtime when using preview&apply

Enhancement
When calling preview or apply, runtime is initialized. However, the initialization will be done every preview/apply call, causing the waste of the I/O and compute. Consider setting the initialed runtimes as an input in domain layer.

For CLI, initialized runtime once should be guaranteed during one ops, for server, should not be initialized again util reboot.

Duplicated https://github.com/KusionStack/kusion/issues/188


Remember search popup size in the edit field

Issue Type: Feature Request
Hi
Please allow to remember searching popup size after closing app.
The part of popup which can be dragged for resize is narrow, and sometimes it is hard to catch it(I have poor eyesight, but it's difficult to do it with glasses)
Or, search bar may be static above edit field, not as popup.
Thanks
VS Code version: Code 1.56.2 (054a9295330880ed74ceaedda236253b4f39a335, 2021-05-12T17:13:13.157Z)
OS version: Windows_NT x64 10.0.19042

This is the find widget @rebornix


Compatibility with Alchemy: HTTP/2 support

I've looked into the flow js sdk and had a couple questions:

It seems like the sdk uses NodeHttpTransport which doesn't support HTTP/2 as a transport. Is this true?
I've been unable to query the https url of Flow's public access nodes (https://access-testnet.onflow.org) with any of my grpc clients besides the flow sdk. Is this because the endpoint doesn't support HTTP/2?

If 1 is true then we will need the sdk to add support for HTTP/2 because it is the only way to query Alchemy's Flow access endpoint (and the canonical way of using gRPC).

Will look into running a proxy for grpc-web https://github.com/improbable-eng/grpc-web/tree/master/go/grpcwebproxy


Add support for GriefDefender(WIP)

Added /integration/griefdefender/GriefDefenderIntegration.java
Added /integration/griefdefender/GriefDefenderIntegrationImpl.java
Modified logic in /integration/Integration.java and /integration/SectionPermissionChecker.java

This commit enables AxiomPaper to support GriefDefender claims. When a world has GriefDefender enabled, players will only be able to use Axiom within claim where they have building permissions. These changes expand AxiomPaper's ability to check for more region protection plugins.

Possible bypass issue found, not fixed yet


fix: Explore gallery cards have unequeal height

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #5077
[ ] Requires deployment <>

Before submitting pull request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </bsx/collection>
[ ] I've tested PR on mobile
[ ] I've written unit tests 🧪
[ ] I've found edge cases

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

pay 20 usd


AspNet Identity with Guid PK example doesn't appear to work

I've tried these docs to try and setup a custom identity setup with Guid primary key.  It doesn't appear to work.  I get an exception when i browse to the homepage:
info: Microsoft.Hosting.Lifetime[14]
Now listening on: https://localhost:7177
info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://localhost:5181
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
Content root path: /Users/ossentoo/Documents/source/azdo/mercle/mercle/temp/testing
fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
An unhandled exception has occurred while executing the request.
System.InvalidOperationException: No service for type 'Microsoft.AspNetCore.Identity.UserManager1[Microsoft.AspNetCore.Identity.IdentityUser]' has been registered.          at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)          at Microsoft.AspNetCore.Mvc.Razor.RazorPagePropertyActivator.<>c__DisplayClass8_0.<CreateActivateInfo>b__1(ViewContext context)          at Microsoft.Extensions.Internal.PropertyActivator1.Activate(Object instance, TContext context)
at Microsoft.AspNetCore.Mvc.Razor.RazorPagePropertyActivator.Activate(Object page, ViewContext context)
at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageCoreAsync(IRazorPage page, ViewContext context)
at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageAsync(IRazorPage page, ViewContext context, Boolean invokeViewStarts)
at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync(ViewContext context)
at Microsoft.AspNetCore.Mvc.TagHelpers.PartialTagHelper.RenderPartialViewAsync(TextWriter writer, Object model, IView view)
at Microsoft.AspNetCore.Mvc.TagHelpers.PartialTagHelper.ProcessAsync(TagHelperContext context, TagHelperOutput output)
at Microsoft.AspNetCore.Razor.Runtime.TagHelpers.TagHelperRunner.g__Awaited|0_0(Task task, TagHelperExecutionContext executionContext, Int32 i, Int32 count)
at AspNetCoreGeneratedDocument.Views_Shared__Layout.b__27_1()
at Microsoft.AspNetCore.Razor.Runtime.TagHelpers.TagHelperExecutionContext.SetOutputContentAsync()
at AspNetCoreGeneratedDocument.Views_Shared__Layout.ExecuteAsync()
at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageCoreAsync(IRazorPage page, ViewContext context)
at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageAsync(IRazorPage page, ViewContext context, Boolean invokeViewStarts)
at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderLayoutAsync(ViewContext context, ViewBufferTextWriter bodyWriter)
at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync(ViewContext context)
at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, String contentType, Nullable1 statusCode)          at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, String contentType, Nullable1 statusCode)
at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ActionContext actionContext, IView view, ViewDataDictionary viewData, ITempDataDictionary tempData, String contentType, Nullable`1 statusCode)
at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor.ExecuteAsync(ActionContext context, ViewResult result)
at Microsoft.AspNetCore.Mvc.ViewResult.ExecuteResultAsync(ActionContext context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|30_0[TFilter,TFilterAsync](ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResultExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultFilters()
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|25_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
at Microsoft.AspNetCore.Routing.EndpointMiddleware.g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
`
using Microsoft.AspNetCore.Identity;
using Microsoft.EntityFrameworkCore;
using testing.Data;
var builder = WebApplication.CreateBuilder(args);
// Add services to the container.
var connectionString = builder.Configuration.GetConnectionString("DefaultConnection") ?? throw new InvalidOperationException("Connection string 'DefaultConnection' not found.");
builder.Services.AddDbContext(options =>
options.UseSqlite(connectionString));
builder.Services.AddDatabaseDeveloperPageExceptionFilter();
builder.Services.AddIdentity<ApplicationUser, ApplicationRole>()
.AddEntityFrameworkStores()
.AddDefaultUI()
.AddDefaultTokenProviders();
builder.Services.AddControllersWithViews();
var app = builder.Build();
// Configure the HTTP request pipeline.
if (app.Environment.IsDevelopment())
{
app.UseMigrationsEndPoint();
}
else
{
app.UseExceptionHandler("/Home/Error");
// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
app.UseHsts();
}
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseRouting();
app.UseAuthentication();
app.UseAuthorization();
app.MapControllerRoute(
name: "default",
pattern: "{controller=Home}/{action=Index}/{id?}");
app.MapRazorPages();
app.Run();
public class ApplicationUser : IdentityUser
{
}
public class ApplicationRole : IdentityRole
{
public string Description { get; set; }
}
`

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

ID: d9869895-9ba2-5027-46cd-89d1d995cba4
Version Independent ID: 8750939b-6ae5-3b9a-6c32-5e84b7fea22c
Content: Identity model customization in ASP.NET Core
Content Source: aspnetcore/security/authentication/customize-identity-model.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @ajcvickers
Microsoft Alias: avickers

I was stuck on this for couple days as well. setup according to this article : https://bel62.wordpress.com/2021/07/12/change-identity-to-use-guid-in-in-ef-core-3-1/
it worked.

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog manageable. If you believe there is a concern which hasn't been addressed, please file a new issue.


Better imresize deprecation warning

Better deprecation warning, which tells the user how to recover the same exact output data when imresize will be taken out.

Damn, I messed up, and I cannot force push.

One second, I'm trying to fix this mess.

CircleCI test failures can be ignored, unrelated.

The deprecation message says it's slate for removal in scipy 1.2.0, which is the current master. So ISTM we either live by the deprecation message and remove it altogether instead, or adjust the message further.

I'm fine with leaving it in till 1.3.0

Fixed, @rgommers.

@Atcold that didn't adjust the message to say 1.3.0 instead of 1.2.0, could you please do that?

Done.

Merged, thanks @Atcold


[add-resource] New Plugin/Theme

Here's a proposal for a new plugin to add blog features to all themes. This is a simple extraction from Antimatter theme of blog parts and rearranged them as a plugin. Here's the link: https://github.com/giansi/grav-plugin-blog.
The screenshots shows the photographer theme within the plugin and without any css customization. I think the result is awesome. I've tried it with twenty theme too and it works fine.
But, I've removed several css parts which are not required, so I'd like to ask someone of you to check them, to help me to avoid removing something that should be kept.

I can add this to GPM when your ready.  You just need to have a release.

You 've got it

added.


Using cocapod 1.1.1 install CLimageEditor, crash when calling initWithimage

If update to use cocapod 1.1.1 and install CLImageEditor
It crash on the following call
CLImageEditor *editor = [[CLImageEditor alloc] initWithImage:image];

Had to revert back to use cocapod 0.39.0 with oldSpec

Crash has similar call stack to this one
https://github.com/yackle/CLImageEditor/issues/74

In my environment, it works fine with cocoapods 1.1.1. I recommend you to review target settings or others.

Can you share your example pod file please?
I have other pods configured the same way but only CLimageEditor has this problem
my looks like this:
source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
use_frameworks!

workspace 'Myworkspace.xcworkspace'
project 'MyProject.xcodeproj'

target 'My Project Target' do
    pod 'CLImageEditor', '~> 0.1.7'
end

Thanks!

Here's my sample pod file. But your pod file also worked.
# Uncomment the next line to define a global platform for your project
platform :ios, '8.0'

target 'sample' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  use_frameworks!

  # Pods for sample
  pod 'CLImageEditor'

end

Thank you for this info, I don't know what I am doing wrong then...

Does this issue occur on new project?

I just tried a new project and it works fine :(

The problem comes down to it can not find the bundle path in my old project for some reason.
    path = [[NSBundle bundleForClass:self.class] pathForResource:self.bundleName ofType:@"bundle"];
    if(path){
        return [NSBundle bundleWithPath:path];
    }
    return nil;

I am able to verify that the bundle file is actually copied over to the simulator...
no idea why path is nil here...

How about removing pod and reinstalling?

I tried removing the pod and reinstalling and same thing happens
I checked again, so the CLImageEditor.bundle does not get copied over to the simulator, that is why the path is nil.
This only happens with simulator for me so far.  I tried on a real device and it works fine.
I need to find out why the bundle file does not get copied over in this case, any ideas?
I am running Xcode Version 8.1 (8B62)

Issue resolved after I removed all pod folder, pod.lock file and workspace file also the Pods.xcconfig in project.  Then cleanly install pod again. I also had to manually remove everything in /Users/xxxxx/Library/Developer/Xcode/DerivedData/Project-aogarsdaowrixsbjrocomctygkid/Build/Products/Debug-iPhonesimulator/
Thank you!

👍


Question: Is data cached / saved or transient with the API call?

Apart from the speed of the (training) pipeline it owuld mean additional complexity on the client side if each API call queries the online sources.
No feature request, I just want to know what I am getting myself into.
Thx for your effort!

Yes, data is cached.
The cache is updated if one of the following occurs:

a new era starts (for get_all_eras())
a new day begins (for get_current_daily())
a new column is added to any of the data sources
a new data source is added


feat: Update OSV schema version to 1.4

Changes

Currently, when querying the DB, fields like schemaVersion or databaseSpecific remain undefined, as sealed db requires an exact match with the target object. The change in this PR aligns with the current schema.
Adds a test for db to validate osvOfflineDb.query functionality
Updates OSV schema, incorporating last_affected field, EVIDENCE as new reference type, CVSS_V2 as a new severity type, affected[].severity field and reorder all elements to ease visual comparison with https://github.com/ossf/osv-schema/blob/main/validation/schema.json

db.spec.ts might need to be db.int.spec.ts as osvOffline.create() makes HTTP calls.

$ npm run test

><EMAIL_ADDRESS>test
> run-s eslint test:unit test:integration

><EMAIL_ADDRESS>eslint
> eslint .

><EMAIL_ADDRESS>test:unit
> jest --testPathPattern=unit.spec.ts

 PASS  packages/osv-offline/src/lib/download.unit.spec.ts
  lib/download
    √ works (2 ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        1.357 s, estimated 2 s
Ran all test suites matching /unit.spec.ts/i.

><EMAIL_ADDRESS>test:integration
> jest --testPathPattern=int.spec.ts --runInBand

 PASS  packages/osv-offline/src/lib/osv-offline.int.spec.ts (5.25 s)
 PASS  packages/osv-offline-db/src/lib/db.int.spec.ts
 PASS  packages/osv-offline/src/lib/download.int.spec.ts

Test Suites: 3 passed, 3 total
Tests:       8 passed, 8 total
Snapshots:   0 total
Time:        11.269 s
Ran all test suites matching /int.spec.ts/i.


Proposal: Allow individual star systems to be exported

The individual star system portion of the sector generator includes some very cool images, that aren't currently exported with the whole sector. Additionally, it may be useful for people who don't want a multi-page pdf and only want to export specific systems, after viewing them in the tool.

Very cool!
What is the reason the system diagram isn't also in the pdf?

Only that it requires a bit of work. Drawing the diagram on a PDF and drawing it on a screen require different code approaches (and I think there are a few limitations with the PDF approach that I'm gonna hafta accept -- things like not being able to use the gradients to make the stars and worlds look a nice as they do on the screen).
It's still part of the plan to get that implemented; I just need time to get there.

I was curious, and assumed there was some sort of code limitation. I still have no idea how exporting anything to pdf works.

Well this is closed as far as I'm concerned. I did notice that in one exported system, because there were several worlds in close proximity to the star, the width of the LCARS AU/distance bar was too small for one of the worlds, so its distance was not written in that bar. But it was still contained in the listing for the world, so it's not a big deal.
But the whole thing is very cool, nicely done!


fix(rxjs-adapter): fix chai typings issue by using<EMAIL_ADDRESS>

[ ] I added new tests for the issue I fixed/built
[x] I ran npm test for the package I'm modifying
[x] I used npm run commit instead of git commit

Fixes build issue due to https://github.com/ReactiveX/rxjs/issues/2112

This is still an issue as per issue linked above.  Closing to wait for updated version.


List on probot.github.io

Hey @clarkbw, this app looks cool.  Would you be interested in having this listed on probot.github.io? Here are the directions for submitting it to the site.

Thanks @bkeepers I'd love to submit it.  I'll go through the requirements list and try to get it started soon.

Hey @clarkbw 🙂, this app would be a great addition to probot.github.io. Any chance of submitting it? Thanks 👍


Ensure Default Service account is not used at a folder level

Possible check to target the following resource

[ ] google_folder_iam_member

closing, tracking in spreadsheet


Installation issue "SetuptoolsDeprecationWarning: setup.py install is deprecated"

Hi,
I'm trying to install the pluging and I'm having following error:
error: subprocess-exited-with-error
× Running setup.py install for backports-datetime-fromisoformat did not run successfully.
│ exit code: 1
╰─> [25 lines of output]
/home/octoprint/python_venvs/octoprint1/lib/python3.7/site-packages/setuptools/version.py:1: UserWarning: Module backports was already imported from None, but /tmp/pip-install-hp3a2ol6/backports-datetime-fromisoformat_a9a7a595b31448e4977bb85b05e7e20d is being added to sys.path
import pkg_resources
running install
/home/octoprint/python_venvs/octoprint1/lib/python3.7/site-packages/setuptools/command/install.py:37: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.setuptools.SetuptoolsDeprecationWarning,
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-37
creating build/lib.linux-x86_64-cpython-37/backports
copying backports/__init__.py -> build/lib.linux-x86_64-cpython-37/backports
creating build/lib.linux-x86_64-cpython-37/backports/datetime_fromisoformat
copying backports/datetime_fromisoformat/__init__.py -> build/lib.linux-x86_64-cpython-37/backports/datetime_fromisoformat
running build_ext
building 'backports._datetime_fromisoformat' extension
creating build/temp.linux-x86_64-cpython-37
creating build/temp.linux-x86_64-cpython-37/backports
creating build/temp.linux-x86_64-cpython-37/backports/datetime_fromisoformat
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -I/home/octoprint/python_venvs/octoprint1/include -I/usr/include/python3.7m -c backports/datetime_fromisoformat/_datetimemodule.c -o build/temp.linux-x86_64-cpython-37/backports/datetime_fromisoformat/_datetimemodule.o
In file included from backports/datetime_fromisoformat/_datetimemodule.
c:66:0:
backports/datetime_fromisoformat/_datetimemodule.h:1:10: fatal error: Python.h: No such file or directory
#include <Python.h>
^~~~~~~~~~
compilation terminated.
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure
× Encountered error while trying to install package.
╰─> backports-datetime-fromisoformat
note: This is an issue with the package mentioned above, not pip.hint: See above for output from the failure.

I'm using OctoPrint 1.8.6 and Python 3.7.15

The message seems to indicate that you are using a manual install of OctoPrint and what instructions/tool did you use to do so? Could you let me know what the base OS is for further troubleshooting? More than likely it's an upstream dependency missing.

That's correct. I'm using Ubuntu 18 as OS.
Linux version 4.15.0-196-generic (buildd@lcy02-amd64-018) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #207-Ubuntu SMP Thu Oct 27 21:24:58 UTC 2022
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.6 LTS"

The pip install error is a new thing that has recently come up. Mu understanding is that the next release of OctoPrint will resolve this issue, but I think it's just a matter of pip installing wheel from the venv folder. Not so certain about the older version of Ubuntu though. @paukstelis have you been seeing this with the install/deploy scripts?

Yes, this is a really a python version thing. I think 18.04 maxes out at 3.6 or 3.7 and OctoPrint now requires 3.8 (I think it is). install/deploy specifies Ubuntu20+ for this reason.

Yeah, OctoPrint is set for >=3.7 for python, so if 3.6 is what's there then that's a larger problem for sure. I see from the venv lines in the log above though that 3.7 is what Peter has installed.

Yeah, OctoPrint is set for >=3.7 for python, so if 3.6 is what's there then that's a larger problem for sure. I see from the venv lines in the log above though that 3.7 is what Peter has installed.

Yes it is indeed 3.7 python

Quick googling on the error indicates that possible running sudo apt-get install python3-dev might fix the issue.

you may have to tell it the version though with sudo apt-get install python3.7-dev.

and if neither of those help sudo apt-get install build-essential may get you back in working order.

Quick googling on the error indicates that possible running sudo apt-get install python3-dev might fix the issue.

Reading package lists... Done
Building dependency tree
Reading state information... Done
python3-dev is already the newest version (3.6.7-1~18.04).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

you may have to tell it the version though with sudo apt-get install python3.7-dev.

That worked like a charm!!!
Thanks a bunch!!

Thank yo uso much @jneilliii for your time. It worked after installing python-dev with the correct version!!


Fixing The About Section Its Not Reponsive

Fixing The About Section Its Not Reponsive Image Added Below.

I want to work on this issue under GSSOC 2023

@Mudassirkhan2 you are assigned!

@Mansi168  Label Of GS0C 2023 ?


Applying particles-js to div through class selector?

Applying particle-js as a .class instead of as an #id does not seem to work.
<div id='realID' class='row particle-js'>
    A bunch more html . . .
    . . .
</div>

I figured I'd just ask before digging.

You can edit the very first line inside the function:
change var canvas_el = document.querySelector( '#' + tag_id + ' > .particles-js-canvas-el' );
to var canvas_el = document.querySelector( tag_id + ' > .particles-js-canvas-el' );
You can then pass IDs or classes, just make sure you add the hash or dot, respectively. Also keep in mind that only the first matching element will be filled with particles, so if you need more than one canvas, you need to use unique class names.

Tried it but seems to be not working, did it work for the TS?

Works for me. Did you replace the other two occurences? Also make sure to pass the CSS class name including the "dot", or if using an ID, the "hash" symbol.

Yes, thanks for the hard work!

Didn't work for me...

any news?

None of the above seem to work for me. I need the header and the footer to have particles-js

Thanks

None of the above seem to work for me. I need the header and the footer to have particles-js

@mateostabio Try this:

["__particles-js-header", "__particles-js-footer"].forEach(
    function (__id, __index) {

        // particlesJS("particles-js", {
        particlesJS(__id, {
            // ..
        });

    }
)

I guess the above mentioned doesn't work for you because it uses jQuery "$". Just try pure JS.


[BUG] Int casting issue when sending tx

Description

Summary generated by Reviewpad on 23 May 23 21:42 UTC
This pull request includes a cleanup and bug fix in module.go that utilizes the shared codec module when marshaling data sent over the wire, and it introduces a hacky workaround to cast a uint32 to a string since it is being passed in as a json.Number through some codeflow. Additionally, the changelog has been updated to reflect these changes.

Origin Document
The error encountered is:
node1.consensus  | 9:11PM level=INFO broadcasting message to network PocketEnvelope={"content":{"type_url":"type.googleapis.com/utility.TxGossipMessage","value":"CtsBCl0KJ3R5cGUuZ29vZ2xlYXBpcy5jb20vdXRpbGl0eS5NZXNzYWdlU2VuZBIyChSZcEXn+ZM7GobRUrdy0giO+GK4dxIUmYBAWIreXuPWzSzOdGeuEMvjmJgaBDEwMDASFDExOTk1NjAzMDY1Mzk4NTAxNTM1GmQKIHuXVS389g22ddtxtHRZjRmsJu41Qe9N1GcGWwPkDEN8EkBMzGmDb7CQn1nbCnl6w9B1/mbzM8PVPnjRDGJMZFxoc8rx+h6O8U1PBE6bdT5srrWBXkhp78g0wjmnMZRGH8MA"}} module=p2p
node1.consensus  | echo: http: panic serving <IP_ADDRESS>:49906: interface conversion: interface {} is json.Number, not string
node1.consensus  | goroutine 484 [running]:
node1.consensus  | net/http.(*conn).serve.func1()
node1.consensus  | 	/usr/local/go/src/net/http/server.go:1850 +0xb8
node1.consensus  | panic({0xe17d80, 0x4005759dd0})
node1.consensus  | 	/usr/local/go/src/runtime/panic.go:890 +0x260
node1.consensus  | net/http.(*timeoutHandler).ServeHTTP(0x4005736fc0, {0x1463e40, 0x40036cd4a0}, 0x4002f05900)
node1.consensus  | 	/usr/local/go/src/net/http/server.go:3412 +0x6f8
node1.consensus  | github.com/labstack/echo/v4/middleware.TimeoutConfig.ToMiddleware.func1.1({0x1480bf8, 0x4003062aa0})
node1.consensus  | 	/go/src/github.com/pocket-network/vendor/github.com/labstack/echo/v4/middleware/timeout.go:125 +0x218
node1.consensus  | github.com/labstack/echo/v4/middleware.RequestLoggerConfig.ToMiddleware.func1.1({0x1480bf8, 0x4003062aa0})
node1.consensus  | 	/go/src/github.com/pocket-network/vendor/github.com/labstack/echo/v4/middleware/request_logger.go:219 +0xe8
node1.consensus  | github.com/labstack/echo/v4.(*Echo).ServeHTTP(0x4000128240, {0x1464d10?, 0x40000e2620}, 0x4002f05900)
node1.consensus  | 	/go/src/github.com/pocket-network/vendor/github.com/labstack/echo/v4/echo.go:646 +0x430
node1.consensus  | net/http.serverHandler.ServeHTTP({0x1460cf8?}, {0x1464d10, 0x40000e2620}, 0x4002f05900)
node1.consensus  | 	/usr/local/go/src/net/http/server.go:2947 +0x2cc
node1.consensus  | net/http.(*conn).serve(0x40058f80a0, {0x1466138, 0x4002f2d9b0})
node1.consensus  | 	/usr/local/go/src/net/http/server.go:1991 +0x544
node1.consensus  | created by net/http.(*Server).Serve
node1.consensus  | 	/usr/local/go/src/net/http/server.go:3102 +0x43c

The following video captures
https://github.com/pokt-network/pocket/assets/1892194/0b90a0f5-74ba-4f59-8042-4a9b9341c56e
The correct fix is to identify where/how a json.Number is propagated to this field, but as a temporary hacky workaround, it was cast to a string. See this StackOverflow answer for more details:

Issue
NA
Type of change
Please mark the relevant option(s):

[ ] New feature, functionality or library
[x] Bug fix
[ ] Code health or cleanup
[ ] Major breaking change
[ ] Documentation
[ ] Other

List of changes

Use the shared codec module resolving a couple techdebt items
Introduce a hacky workaround
...

Testing

[x] make develop_test; if any code changes were made
[ ] make test_e2e on k8s LocalNet; if any code changes were made
[ ] e2e-devnet-test passes tests on DevNet; if any code was changed
[x] Docker Compose LocalNet; if any major functionality was changed or introduced
[ ] k8s LocalNet; if any infrastructure or configuration changes were made

Required Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added, or updated, godoc format comments on touched members (see: tip.golang.org/doc/comment)
[ ] I have tested my changes using the available tooling
[ ] I have updated the corresponding CHANGELOG

If Applicable Checklist

[ ] I have updated the corresponding README(s); local and/or global
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added, or updated, mermaid.js diagrams in the corresponding README(s)
[ ] I have added, or updated, documentation and mermaid.js diagrams in shared/docs/* if I updated shared/*README(s)

@bryanchriswhite I'm going to merge this in just to unblock things but if you can look at // HACK(#783): Figure out why we need a conversion here (in the code) at some point in the future, would appreciate it!


Vulkan renderer not updating screen after computer suspension + memory leak

Godot version
4.0.rc6
System information
Ubuntu 22.10, RTX 2060, Vulkan
Issue description
If I open any Godot 4 project, suspend my computer, then resume it, the renderer no longer updates to the screen. It also causes a memory leak (left it until it hit 4.9 GB). This only occurs when using the Forward+ or Mobility renderer. The Compatibility renderer does not have this issue; it works fine.
It also occurs to exported projects (if Forward+ or Mobility renderer used).
I assume something in the Vulkan renderer is being disconnected by the computer suspension, and is not reconnected when resumed. If I move Godot to a second monitor, then disconnect the monitor, the issue doesn't present, only if I suspend the computer. I cannot test on any other operating system.
Steps to reproduce

open any 4.0 project
set renderer to Forward+ or Mobility
suspend computer
resume computer
attempt to move or interact with anything in the godot window. Resizing also works

Minimal reproduction project
N/A any project works, including default new project

Duplicate of #52738


Feature: Integrated Xdebug for Visual Studio Code.

This pull request adds necessary config files and installs required VSCode plugins on Gitpod and Github Codespaces in order to use Xdebug for Sciencemesh project.

[x] Configure Xdebug config files, add them to Dockerfile.
[x] Xdebug can establish connections from inside container to the host.
[x] Gitpod integration.
[x] Codespaces integration.
[x] Documentation.

off-topic
Also fixes some bash script problems on systems that have space in their path by putting
`pwd`/nc-sciencemesh:/var/www/html/apps/sciencemesh

inside a double quote
"$(pwd)/nc-sciencemesh:/var/www/html/apps/sciencemesh"

@michielbdejong would you review this and this if everything is OK? also we need to rebuild and push to Docker Hub afterwards so I think it needs your credentials to do so.


localizationsDelegates doesn't work in GetMaterialApp

Describe the bug
localizationsDelegates doesn't work in GetMaterialApp
**Reproduction code
GetMaterialApp(
        initialRoute: AppPages.INITIAL,
        getPages: AppPages.routes,
        supportedLocales: const [
          Locale('en', ''), // English, no country code
          Locale('es', ''), // Spanish, no country code
        ],
        localizationsDelegates: const [
          GlobalMaterialLocalizations.delegate,
          GlobalWidgetsLocalizations.delegate,
          GlobalCupertinoLocalizations.delegate,
        ],
      )

Unsupported operation: Cannot set value in unmodifiable Map

The relevant error-causing widget was
GetMaterialApp
lib/my_app.dart:90

Flutter Version:
2.2.3
Getx Version:
4.3.6

I have the same problem.

@jonataslaw  Maybe any response for this?

I have the same issue, I want to display showDatePicker in spanish

Hi,
Any updates on this?
Thanks.

In my case was because I was passing a locale without country code
GetMaterialApp(
        locale: Locale("en", "US"), // <-- here
        localizationsDelegates: const [
          CountryLocalizations.delegate,
          GlobalMaterialLocalizations.delegate,
          GlobalWidgetsLocalizations.delegate,
          GlobalCupertinoLocalizations.delegate,
        ],
        supportedLocales: const [
          Locale('en', 'US'),
          Locale('es', 'ES'),
        ],
      )

Removing this funciton worked for us initializeDateFormatting().

@darwin-morocho  hi, how can you solved this problem ?


New release?

Is there a roadmap for the next release? Thanks.

This is (belatedly) complete. The 0.2.0 release is on pypi, which most notably includes tree_math.struct. See the project README for usage instructions.
I don't have any active plans for development on this project at the moment. If/when new features land, I'll gladly issue a new release.


wayne, ingham, jackson skip question about other requests?

Just tested Wayne and Ingham in LHI and it did ask this question. Is this an intentional change?

Tested Jackson too, and this question is presented.


Security Scorecards integration

See https://github.com/ossf/scorecard for more info.
Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure correct labels applied
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 99.668%. Remained the same when pulling 4f97fa71abee23693a2b092bf6e4c3bbb5ae01ca on scorecards into 010d40b6e5ca741d1ddae21781cdd139e3125edf on main.


chore: temporarily disable macos tests on LLD CI

📝 Description
due to ongoing instabilities with CI macos instance on running Desktop E2E tests, a quick and temporary solution we consider will be to disable the macos tests until we deeply understand the issue and fix it.
LLD being mostly a web project, 99% of the time, bugs happens on all OSs so the risk is reduced. on top of this, most of our developers work on Mac OS so will have tested the feature there. Nevertheless, we still need this restored, simply git revert when the fix is there.
❓ Context

Impacted projects: LLD tests
Linked resource(s): LIVE-9602

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

/generate-screenshots

as it seems there is a flawky case of market-page-btc-star-linux.png , i'm retriggering to see

/generate-screenshots

ok we cancel this idea & will refocus on finding a fix + fix other flaky test issues


verify_licenses unable to detect ISC license?

It would seem that verify_licenses is unable to detect the ISC license of argus-toolbelt / argus-api.
Output from script:
Checking license for package: argus-api ...
argus-api: found license from pip show: License: ISC
FAILURE: argus-api: no approved license found for license: License: ISC
However, in approved_licenses I see this:
"name": "ISC License (ISCL)"
"url": "https://opensource.org/licenses/ISC",
"regex": "ISC License"

Fixed as part of: https://github.com/demisto/dockerfiles/pull/2594


handle IP addresses modification in running nodes and CEPs

Since k8s nodes, pods and CEPs can have their pod IP modified without
being deleted, Cilium needs to be able to handle such cases by deleting
the ipcache entries of the old IP addresses. Failing to do it so, Cilium
will rely on outdated information from those old entries until it
receives new events that can update those entries.
Until the events with the up-to-date information are received, Cilium
might use the old, and potentially wrong, security identity stored for
this IP address. Leveraging any such stale IP to Identity mappings is
difficult given the access required to make use of them and the limited
time window during which an update would be processed, rendering such
entries no longer stale, and identity propagation is transmitted before
a pod is marked as Ready.
Signed-off-by: André Martins<EMAIL_ADDRESS>Handle events with pod IP and node IP addresses being modified

test-me-please

test-me-please


Outstanding technical changes to regridding code

This ticket records outstanding technical changes that we want to make to the regridding code following #1438. Some of these points may require discussion or clarification before implementation.

Tasks from Fiona

[ ] Remove hard coded geoid and instead take information from Iris cube: If you pass in the input cube you can access the coordinate system by doing coord_system = cube.coord("latitude").coord_system If it has the correct metadata I think it should return an iris.coord_systems.GeogCS instance ( https://scitools-iris.readthedocs.io/en/stable/generated/api/iris/coord_systems.html#iris.coord_systems.GeogCS) that should have attributes you can interrogate to find all the geiod information. You can always default to WGS84 parameters if you don't find any on the cube.
[ ] Consider adding more unit tests at the function level.
[ ] Understand the use case for  cube_in_mask and the cube_in bing different resolutions. If not necessary tidy up the code appropriately.

Hi @fionaRust it looks like there is outstanding work here to do, is there anything you're waiting on BOM to do here?

@anja-bom  we're not waiting for it and I think we realised a long time about that this was unlikely to get done. I've linked it to our own ticket for deciding whether to use these methods in our suite, which might include revisiting some of the things on this ticket. Hopefully this means it doesn't get forgotten if we decide to go further with it at some point.


Playback starts with 4s offset in DASH live stream

Media3 Version
ExoPlayer 2.18.4
Devices that reproduce the issue
All devices
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps
Happens only on some contents.
Exoplayer always starts the playback from 4s. But the same content starts at 0s with Shaka player.
Expected result
Playback should start from 0s i.e. start of the manifest.
Actual result
Playback starts at 4s.
Media
I cannot share the media, but will share the manifest to<EMAIL_ADDRESS>Bug Report

[X] You will email the zip file produced by adb bugreport to<EMAIL_ADDRESS>after filing this issue.

The manifest you shared via email is a live stream and the player will start playback at the specified suggestedPresentationDelay="PT13.9304S", meaning 13.9 seconds behind the current real-time. So "start from 0s" is never the expected result for this manifest and doing this sounds more like a bug in Shaka player.
Where exactly in the manifest ExoPlayer starts depends on the exact timing of the playback request because the player aligns it with the current UTC time. Since your manifest doesn't define a UTCTiming element, the player falls back to a NTP request to obtain the current time. Adding a UTCTiming element is also recommend by the DASH interop guidelines to achieve a consistent behavior across clients: https://dashif-documents.azurewebsites.net/DASH-IF-IOP/master/DASH-IF-IOP.html#clock-sync
Possibly related to your question: the manifest also defines minBufferTime="PT4.0S", which means that the player should never attempt to play closer than 4 seconds to the end of the available live window. The value usually represents the level of variation in the content encoding and is recommend to be set to one GOP size. This ensures there is no sudden data underrun for extreme variations in the encoding process. See https://dashif-documents.azurewebsites.net/DASH-IF-IOP/master/DASH-IF-IOP.html#minbuffertime-feature. I wonder if that's the 4s value you are referring to? It's more relevant as an offset from the end of the live window though (not from the start) and doesn't seem to match your problem description.

I thought so too, which is why I am just as perplexed with this behaviour.
About suggestedPresentationDelay and minBufferTime, I have tried hardcoding all possible values to figure out which property is throwing off the player. To be specific, I edited buildMediaPresentationDescription  from DashManifestParser to return this:
  return new DashManifest(
      availabilityStartTime,
      C.TIME_UNSET,
      C.TIME_UNSET,
      dynamic,
      C.TIME_UNSET,
      C.TIME_UNSET,
      C.TIME_UNSET,
      C.TIME_UNSET,
      null,
      utcTiming,
      null,
      null,
      periods);

The behaviour has a slight change:
With the minUpdateTimeMs taken from manifest, the playback is starting from 3.99s i.e. the original issue that I mentioned. But if I set it to C.TIME_UNSET, the playback starts from 5.00s. I confirmed this using EventLogger logs where it shows that the position changes due to a source update.
2023-05-24 21:30:12.845 13687-13687 EventLogger             com.google.android.exoplayer2.demo   D  timeline [eventTime=4.36, mediaPos=3.99, window=0, period=0, periodCount=2, windowCount=1, reason=SOURCE_UPDATE

None of the other properties seem to have any effect on the starting position.
I have also tried adding setLiveConfiguration(new MediaItem.LiveConfiguration.Builder().setTargetOffsetMs(0L).build()) to createMediaItemFromIntent but that caused no change in initial position.
Nevertheless, none of these changes could make the playback start from 00:00. As you can see from the manifest, there are two segments in the pre roll - a 4s one and a 2s one. But in action, I guess only 2s of the pre roll is being played and somehow the first segment is not being played.
Could this be a function of availabilityStartTime and the start property of the period? If there is any other property you would like me to test, please do let me know.
Appreciate you taking the time! Thanks!

@tonihei I have raised a PR to make the minLiveStartPosition configurable: #425
Can you please check this and let me know what you think? Thanks!

@tonihei we are waiting on your review to fix a critical production bug, so would appreciate your help here. Thanks!

I'll close this issue because the general behavior is WAI as far as I can see. The feature request to make the min live position configurable is discussed in #425.


🐛  Camera.onError(unknown/unknown):  outputs must be a non-null, non-empty list

What's happening?
when i run my program, i get " Camera.onError(unknown/unknown): [unknown/unknown] outputs must be a non-null, non-empty list [unknown/unknown: [unknown/unknown] outputs must be a non-null, non-empty list]". i use "Camera.requestCameraPermission();". i got "granted", but i use "const {hasPermission, requestPermission} = useCameraPermission();". hasPermission get false. My camera is get black camera. How to solve the issue? i tried use react-native-vision-camera 3.6.17 and 3.6.16. i still get black screen.
i hope my program can open camera. so, i can add other code in my program.
Thank you very much.
Reproduceable Code
below is my program
export default function Barcode() {
  const device = useCameraDevice('back');
  //const device = devices.back;
  const {hasPermission, requestPermission} = useCameraPermission();

  useEffect(() => {
    getpremission();
  }, []);

  const getpremission = async () => {
    const status = await Camera.requestCameraPermission();
    if (status === 'denied') {
      console.log('permission not granted');
    }

    if (device === null) {
      console.log('null');
      return <NoCameraDeviceError />;
    }

    console.log('54: ' + JSON.stringify(status));
    console.log('55: ' + JSON.stringify(hasPermission));
    if (hasPermission === false) {
      console.log('false');
      requestPermission();
    }
  };

  // eslint-disable-next-line react-hooks/rules-of-hooks
  const onError = useCallback((error: CameraRuntimeError) => {
    console.error(error);
  }, []);

  return (
    <>
      <Camera style={StyleSheet.absoluteFill} device={device} isActive={true} />
    </>
  );
}

Relevant log output
ERROR  Camera.onError(unknown/unknown): [unknown/unknown] outputs must be a non-null, non-empty list [unknown/unknown: [unknown/unknown] outputs must be a non-null, non-empty list]

Camera Device
import {
  Camera,
  useCameraDevice,
  NoCameraDeviceError,
  useCodeScanner,
  useCameraPermission,
} from 'react-native-vision-camera';
const device = useCameraDevice('back');
<Camera style={StyleSheet.absoluteFill} device={device} isActive={true} />

Device
Android
VisionCamera Version
3.6.17 and 3.6.16
Can you reproduce this issue in the VisionCamera Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
Additional information

[ ] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

🙋🏻♂

🙋🏻♂

I solved the black screen when i open apps at first time.
reference: (discord - SteelMan)
Hi, I've not the code here, but my code was something like:
{device &&

}
and I got black screen.
After I tried something like this:
const [isActive, setActive] = useState(false);
useEffect(() => {
if (hasPermission) {
setTimeout(() => setActive(true), 500); // I'm not sure "setTimeout" is needed
}
}, [hasPermission]);
return device && (

)


Go To feature has stopped working

Nothing happens when you click the Go To button (should display an error message if there's an error).
Error 403 (forbidden)
No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8383' is therefore not allowed access. The response had HTTP status code 403.
"You have exceeded the number of monthly transactions included with your current plan. If you need additional transactions, please consider upgrading to a plan that offers additional transactions. If you would like to talk to an Account Manager about Enterprise Edition licensing options, please contact<EMAIL_ADDRESS>

Added a warning message and a console log entry advising the need for a MapQuest API access key.
See https://developer.mapquest.com/


Add Docker4Drupal

As I can see https://github.com/wodby/docker4drupal is missing from the list.

I think I initially tried adding it but had some trouble. I may try again when I get back around to this project at some point.


Log Spam from Riak services in Traffic Ops

I'm submitting a ...

bug report

Traffic Control components affected ...

Traffic Ops

Current behavior:
Traffic Ops will sometimes emit the error:
ERROR: riak_services.go:343: 2020-11-17T14:10:49.716927165Z: getting riak servers: querying riak servers: sql: transaction has already been committed or rolled back

when encountering an error in Riak-related endpoint logic. It's probably calling HandleErr without returning.
Expected behavior:
When a fatal error occurs, handling should end and no further attempts should be made to roll back the linked transaction.
Minimal reproduction of the problem with instructions:
I think you can actually just see it in the default CDN-in-a-Box setup logs.

It's probably calling HandleErr without returning.

If it is, you should see this in the logs:
https://github.com/apache/trafficcontrol/blob/master/traffic_ops/traffic_ops_golang/api/api.go#L134

called after a write already occurred! Not double-writing!

FWIW I've seen that transaction has already been committed or rolled back in the past, after strange query errors. Certain bad queries -- which didn't commit or rollback -- seem to cause all future queries on the same transaction. I don't fully understand why.

Riak KV as a backend for Traffic Vault is deprecated, so we won't be fixing this.


radamsa: 0.4 -> 0.5

Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/radamsa/versions.
These checks were done:

built on NixOS
ran /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5/bin/radamsa -h got 0 exit code
ran /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5/bin/radamsa --help got 0 exit code
ran /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5/bin/radamsa -V and found version 0.5
ran /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5/bin/radamsa --version and found version 0.5
found 0.5 with grep in /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5
directory tree listing: https://gist.github.com/fc1b475926e3a86b55b9d18567458bd4

Success on x86_64-linux (full log)
Attempted: radamsa
Partial log (click to expand)
cat doc/radamsa.1 | gzip -9 > /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5/share/man/man1/radamsa.1.gz
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5
shrinking /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5/bin/radamsa
gzipping man pages under /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5/share/man/
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5/bin
patching script interpreter paths in /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5
checking for references to /build in /nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5...
/nix/store/vjls4rpfr18a844phj56y6zkgjhkk44n-radamsa-0.5

Success on x86_64-darwin (full log)
Attempted: radamsa
Partial log (click to expand)
mkdir -p /nix/store/zvb5jp7c5b7hch0k6cpnanxx8nswkks0-radamsa-0.5/bin
cp bin/radamsa /nix/store/zvb5jp7c5b7hch0k6cpnanxx8nswkks0-radamsa-0.5/bin
mkdir -p /nix/store/zvb5jp7c5b7hch0k6cpnanxx8nswkks0-radamsa-0.5/share/man/man1
cat doc/radamsa.1 | gzip -9 > /nix/store/zvb5jp7c5b7hch0k6cpnanxx8nswkks0-radamsa-0.5/share/man/man1/radamsa.1.gz
post-installation fixup
gzipping man pages under /nix/store/zvb5jp7c5b7hch0k6cpnanxx8nswkks0-radamsa-0.5/share/man/
strip is /nix/store/0fzpxnsanc02i4jsb1yhchjp4p62b2n3-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/zvb5jp7c5b7hch0k6cpnanxx8nswkks0-radamsa-0.5/bin
patching script interpreter paths in /nix/store/zvb5jp7c5b7hch0k6cpnanxx8nswkks0-radamsa-0.5
/nix/store/zvb5jp7c5b7hch0k6cpnanxx8nswkks0-radamsa-0.5

Success on aarch64-linux (full log)
Attempted: radamsa
Partial log (click to expand)
cat doc/radamsa.1 | gzip -9 > /nix/store/062i4h55kiw2ar9128yx6klxhdff76j6-radamsa-0.5/share/man/man1/radamsa.1.gz
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/062i4h55kiw2ar9128yx6klxhdff76j6-radamsa-0.5
shrinking /nix/store/062i4h55kiw2ar9128yx6klxhdff76j6-radamsa-0.5/bin/radamsa
gzipping man pages under /nix/store/062i4h55kiw2ar9128yx6klxhdff76j6-radamsa-0.5/share/man/
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/062i4h55kiw2ar9128yx6klxhdff76j6-radamsa-0.5/bin
patching script interpreter paths in /nix/store/062i4h55kiw2ar9128yx6klxhdff76j6-radamsa-0.5
checking for references to /build in /nix/store/062i4h55kiw2ar9128yx6klxhdff76j6-radamsa-0.5...
/nix/store/062i4h55kiw2ar9128yx6klxhdff76j6-radamsa-0.5


Do we have to do all the massaging we are doing in store_deck

Or can we just translate, add some fields and pass into deck.add_deck?

I removed this when refactoring tapped out to get updated date.


acme: Do not create certificate directory unless certificate fetch succeeded

Fixes: https://github.com/komuw/ong/issues/403

Codecov Report
Attention: 6 lines in your changes are missing coverage. Please review.

Comparison is base (7240d26) 73.01% compared to head (8a2e567) 73.00%.

:exclamation: Current head 8a2e567 differs from pull request most recent head 2fef1d0. Consider uploading reports for the commit 2fef1d0 to get more accurate results

Files
Patch %
Lines

internal/acme/helpers.go
40.00%
5 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #404      +/-   ##
==========================================
- Coverage   73.01%   73.00%   -0.02%
==========================================
  Files          49       49
  Lines        5863     5868       +5
==========================================
+ Hits         4281     4284       +3
- Misses       1268     1270       +2
  Partials      314      314

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


Add Vite template

Fix #93

[ ] Add web-vitals
[ ] Add license with attribution to Vite + React + Testing + TypeScript
[ ] Consolidate configs (see my stashes)
[ ] Use JSX runtime

Looks good as a starting point!


Css pseudo-element "::before" make UI orderless

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

VS Code Version: 1.88.0
OS Version:

Has pseudo-element "::before", UI orderless

When I remove pseudo-element "::before", UI OK

@alexdima I see you add pseudo-element "::before" Here, why we need the style code？what the style code mean? Thanks

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.87.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Honestly, I don't know exactly what that's for. It came in via https://github.com/microsoft/vscode/commit/8a7189599e36d9df0ececb05fc2bc9e109a957b3 . @aeschli any idea?

@alexdima Sorry, no idea


Not working at all.

the notch just does nothing, nothing is working. I am currently using a M2 MBA

I've made a small mistake with writing the sketchybarrc.example file. 1e5e4f7 fixes this. You may need to try performing the command brew services restart sketchybar once again after the installation, though.
But please know that if you've been using dynamic island configs previously, you need to perform a full reinstallation. There has been a change to the example sketchybarrc config file.

i'm on m1 mba, not working


Introduce KeyStore Persistence Manager and Registry KeyStore Persistence Manager implementations

Purpose
Introduce KeyStore Persistence Manager Interface.

addKeystore
getKeyStore
listKeyStores
updateKeyStore
deleteKeyStore
getKeyStoreLastModifiedDate
getKeyStorePassword
getPrivateKeyPassword

Introduce KeyStore Registry Persistence Manager implementations
Part of: https://github.com/wso2/product-is/issues/21206
Previously Reviewed PR: https://github.com/wso2/carbon-kernel/pull/4109

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/11737536121

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/11737536121
Status: success

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/11871159341

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/11871159341
Status: success


Enable file based memory backend

Enable file based memory backing at /dev/shm on the host which will be used primarily (as of this writing) to be virtio-fs cache.

Hi,
Currently, I can only start kata container with virtiofs by setting "enable_hugepages = true" in /etc/kata-containers/configuration.toml. Otherwise, kata will fail to create container using virtiofs.
Do you think it's the same issue here?

Yes @renzhengeek - that’s what Ganesh is working on resolving.


Tags list loads slowly

Opening the tags list loads slowly. I am assuming it's related to counting the untagged files without an index.
Profiling it will test that theory

Other pages also load slowly. It is not limited to the tags list.

The tags list was mostly fixed by 5d8a65d6194923094a7c2b792048a638cd2c9546 then again by ee75168aa8e399d61a95e479aee4cfa61e85c324
With the re-addition of slight randomness to which images are brought up for tagging images tagging is quite slow with a large number of images. Around 11 seconds on my instance to load 20 images. Excluding already tagged images in the query seems to cause huge delays.


Adds offset+count overloads to Publish and Request

Implements #171.

@sixlettervariables Thanks! (as always).  I'll starting reviewing this today.


SPADE: setup.py should download fim.pyd for windows

spade.py fails to import fim module on windows as setup.py downloads only the .so version of the library, while windows requires the .pyd variation.
The windows precompiled pyd files are available in the same  location as the .so

Thanks for the input, I'll have a look into this. I think the Windows version had not been considered so far.

Fixed. but enhancement suggested in follow-up issue #214


Improve user guidance during automatic prompting for mandatory parameter values

Background
In the absence of arguments provided for mandatory cmdlet / advanced function parameters, PowerShell automatically prompts the user.
These prompts support !-prefixed commands:

!? displays the help message associated with the parameter at hand, assuming a helpMessage argument  was provided as part of the parameter's [Parameter()] attribute.

!"" allows entering an empty string as an argument - this is necessary for array-valued parameters that permit empty strings as elements, such as [string[]]-typed parameters with the [AllowEmptyString()] attribute, because submitting nothing (just pressing Enter) signals the end of the input for that parameter, i.e., it is how you signal that all array elements have been entered.

!! is needed to escape a ! at the beginning of a value; e.g., in order to submit !foo, !!foo must be typed.

As an aside: These commands unexpectedly also surface when you use Read-Host -Prompt, even though they serve no purpose there - see #4066.
Problems with the current behavior
Currently, when a mandatory prompt is shown, only the !? command is mentioned, and only if the parameter at hand has a help message defined.
By contrast, the existence of !"" and !! is not mentioned, and currently not even documented.
Similarly, it isn't documented that only literal values can be entered by the user - no references to variables or subexpressions are evaluated as such.
Additional problems (not the focus of this issue):

#4068 discusses how automatic prompting doesn't work (meaningfully) for parameters types [scriptblock], [hashtable] or [bool] / [switch], with a fix being considered that disables automatic prompting for [scriptblock], [hashtable], and fixes [bool] / [switch] prompting to present Y/N-style prompts.

No tab completion is offered for [ValidateSet()]-constrained parameters, and entering an invalid value aborts the prompt rather than given the user a chance to correct the problem.

Conversely, empty input can result in unexpected conversion, such a empty input for a mandatory [int] parameter getting interpreted as 0.

As stated, only input of literals is supported - allowing expressions would have to be carefully designed.

A corollary of the above is that you cannot enter $null (for parameters with [AllowNull()]).

The wording of the prompt messages should be improved.

A potential UX improvement would be to present the resulting command for final inspection to the user before submitting it, both as a safety measure and as a teaching tool (to show how the command could have been submitted non-interactively).

In short: A nontrivial amount of effort would be needed to make automatic prompting work comprehensively and in a user-friendly manner.
The solution proposed here is just a small step in that direction.
Possible solution
Eliminate the prompt commands altogether:

Simply print the help message by default, if present, obviating the need for the !? command.

A ! at the start of a user-typed value would then no longer require escaping as !!.

The only downside is the loss of !"" for entering empty strings, but given the rarity of the need for this and the other holes in the automatic prompting functionality, that price seems worth paying.

Of course, if automatic prompting is ever fixed to work comprehensively, the ability to enter empty strings would need to be restored somehow.
At this point that doesn't sound likely, however.
Environment data
Written as of:
PowerShell Core v6.1.0-preview.3

@vexx32:
Re HelpMessage: Indeed, and it's what I meant to say by:

Simply print the help message by default, if present, obviating the need for the !? command.

I'd love to see the HelpMessage (if any) printed by default.
Further than that, if there is no HelpMessage, I'd like to see the parameter help printed.
If we think that might be overwhelming, add a preference variable like $PSHelpfulPrompts = $true or whatever.


v2.0.1 - Options on bc-flickity attribute are completely ignored

Issue:
Assigning options from the constructor and passing them on the directive argument on the template does not work and ignores all the settings.
Code example (ES6):
export default class CarouselController {

  constructor(FlickityService) {
    this.flickityOptions = {
      cellSelector: '.child-slide',
      setGallerySize: true,
      prevNextButtons: false,
      imagesLoaded: true,
      pageDots: false,
      wrapAround: true
    };
  }
}

.carousel-component(bc-flickity="{{ $ctrl.flickityOptions }}")
  .child-slide(ng-repeat="item in $ctrl.items")
    image-component(image="item.image", url="item.url")

Result:
prevNextButtons, imagesLoaded, pageDots, wrapAround options are ignored and the default setting is always displayed
Demo (forked from your demo):
http://plnkr.co/edit/sU6VoIz7UyODu8Rcxs0k?p=preview
Workaround:
Downgrade to v2.0.0

Apologies for this, @luigimannoni. This was a simple developer error on my part ☹ . I have pushed a fix out for this: https://github.com/benjamincharity/angular-flickity/releases/tag/v2.0.2.
Adding unit tests for this module is next on my list of priorities which should help cut out these simple errors.
Thanks for bringing this to my attention!


[SuperEditor] Combination "+s results in jumpy caret

Steps to reproduce:

Open Demo app
In the editor type"s

Result:
https://user-images.githubusercontent.com/31278849/213761108-7861f943-af07-49aa-a002-81de454dcf1b.mov

This will happen with other combinations like 's, ~s, "r, ~r, etc.

Cc @matthew-carroll

We believe that this issue is now solved with Angelo's recent work. @miguelcmedeiros can you check again and close the ticket if it's resolved?

@angelosilvestre it's fixed!!
Great work 🙌


Allow floating windows under tiled windows

So, I'm trying to replicate aspects of my config from KDE on Hyprland, and everything is coming along nicely. Except that I used to have Cava inside a terminal, positioned to cover the bottom half of my screen, and have it be under all windows.
I managed to get everything I wanted using window rules (and some aspects of it even better than with KDE's window rules):
windowrulev2 = float,          class:(kitty),title:(cava)
windowrulev2 = pin,            class:(kitty),title:(cava)
windowrulev2 = noanim,         class:(kitty),title:(cava)
windowrulev2 = noblur,         class:(kitty),title:(cava)
windowrulev2 = noborder,       class:(kitty),title:(cava)
windowrulev2 = nodim,          class:(kitty),title:(cava)
windowrulev2 = nofocus,        class:(kitty),title:(cava)
windowrulev2 = noinitialfocus, class:(kitty),title:(cava)
windowrulev2 = noshadow,       class:(kitty),title:(cava)
windowrulev2 = rounding 0,     class:(kitty),title:(cava)
windowrulev2 = size 100% 50%,  class:(kitty),title:(cava)
windowrulev2 = move 0% 50.2%,  class:(kitty),title:(cava)

...but I can't get the window under all of the other windows. Basically, the entire point of my visualizer.
Did I miss something, or are floating windows never allowed under tiled windows?
If so, I was thinking I could maybe specify a layer for the window to be in (I mean the things you could see by running hyprctl layers)?
EDIT: searching around more through the issue tracker, I noticed #2081 talks about basically the same feature

I'll close this as a dupe of #2081


Document How to Convert Private to Public Feeds

I already have a private feed with packages in it. I want to convert it to a public feed. This should be documented. Is it even possible?

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

ID: bceed83a-c520-5576-f54d-a28f8345795c
Version Independent ID: c4c0690a-8156-4cd5-0f15-5244b077c971
Content: Share Packages Publicly
Content Source: docs/artifacts/tutorials/share-packages-publicly.md
Product: devops
Technology: devops-artifacts
GitHub Login: @chasewilson
Microsoft Alias: phwilson

@RehanSaeed Thank you for the question.
Public feeds are currently in preview and a feature such as the ability to convert from private to public will be documented as soon as it becomes available.
For now, a good place to keep up-to-date is the Azure DevOps release notes page.


Many vectors don't display at all

Hi there -
When I download master and take a look in my Mac Finder, many vectors don't show up at all:

When I open them in Chrome, they also are blank:

There seems to be a number of icons that are subject to this.
Any thoughts?

The paths aren't visible because they aren't stroked, which makes them easily customizable.
You need to add the stroke attribute or style them with CSS. To display them correctly, you also need to set fill to none, as paths are filled black by default.


TestMediaFilenames incorrectly tests Content-Disposition

Content-Disposition is not a spec defined behaviour (it's not mentioned in https://spec.matrix.org/v1.7/client-server-api/ other than for the filename, and complement should not be prescribing that servers act a certain way without a spec to cover it.
It's up to homeservers to decide what media types may be presented inline or as attachments (and something we're trying to fix in https://github.com/matrix-org/synapse/pull/15988 to fix a unsatisfactory situation).

This appears to have originally come from sytest, which also is testing this behaviour wrongly. https://github.com/matrix-org/complement/pull/639.
Ultimately I'd be in favour of at most checking Content-Disposition is a valid value, but realistically we can't expect developers to pass these tests until the spec defines the requirements.


Update rpc client header (#9276) (#9349)

Description
cherry picks the cherry pick to get the header back https://github.com/celestiaorg/celestia-core/commit/d95e437a08c1e660612602bb886c12a23e403fd0
closes #1095

I feel like I've approved or written a version of this PR 5 or 6 times


model pipeline-service and sprayproxy for promotion

Model the components environment (development, staging and production) in a structured way for promotion. Detailed info: https://issues.redhat.com/browse/PLNSRVCE-1391

close this as per https://github.com/redhat-appstudio/infra-deployments/pull/2383


calicoctl should check rp_filter

On a system where net.ipv4.conf.all.rp_filter is set to 2, calicoctl will successfully launch calico-node, but Felix will stack trace with the following error:
2016-07-28 18:19:24,684 [CRITICAL][307/4] calico.felix.devices 70: Kernel's RPF check is set to 'loose'.  This would allow endpoints to spoof their IP address.  Calico requires net.ipv4.conf.all.rp_filter to be set to 0 or 1.
2016-07-28 18:19:24,684 [ERROR][307/4] calico.felix.felix 259: Exception killing main greenlet
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/calico/felix/felix.py", line 79, in _main_greenlet
    devices.configure_global_kernel_config()
  File "/usr/lib/python2.7/site-packages/calico/felix/devices.py", line 74, in configure_global_kernel_config
    raise BadKernelConfig("net.ipv4.conf.all.rp_filter set to 'loose'")
BadKernelConfig: net.ipv4.conf.all.rp_filter set to 'loose'

Either Calicoctl should be checking this and refusing to launch node, or calicoctl should simply correct it itself.

I was going to say that if calicoctl was going to enforce rp_filter, would it make better sense for Felix to do that instead (rather than just checking).
However, if you're now thinking that calicoctl should only check and warn, that thought no longer applies.

To further complicate things, seems DC/OS is intentionally setting rp_filter=2 at launch.

This vague DC/OS issue seems to suggest this is intentional: https://dcosjira.atlassian.net/browse/DCOS-230
Can we modify Felix so that it is compatible with loose mode?
rp_filter - INTEGER
	0 - No source validation.
	1 - Strict mode as defined in RFC3704 Strict Reverse Path
	    Each incoming packet is tested against the FIB and if the interface
	    is not the best reverse path the packet check will fail.
	    By default failed packets are discarded.
	2 - Loose mode as defined in RFC3704 Loose Reverse Path
	    Each incoming packet's source address is also tested against the FIB
	    and if the source address is not reachable via any interface
	    the packet check will fail.

	Current recommended practice in RFC3704 is to enable strict mode
	to prevent IP spoofing from DDos attacks. If using asymmetric routing
	or other complicated routing, then loose mode is recommended.

	The max value from conf/{all,interface}/rp_filter is used
	when doing source validation on the {interface}.

	Default value is 0. Note that some distributions enable it
	in startup scripts.

There's a comment in the relevant Felix code (devices.py) that seems pretty clear about the situation:
# For IPv4, we rely on the kernel's reverse path filtering to prevent
# workloads from spoofing their IP addresses.
#
# The RPF check for a particular interface is controlled by several
# sysctls:
#
# - ipv4.conf.all.rp_filter is a global override
# - ipv4.conf.default.rp_filter controls the value that is set on a newly
#   created interface
# - ipv4.conf.<interface>.rp_filter controls a particular interface.
#
# The algorithm for combining the global override and per-interface values
# is to take the *numeric* maximum between the two.  The values are:
# 0=off, 1=strict, 2=loose.  "loose" is not suitable for Calico since it
# would allow workloads to spoof packets from other workloads on the same
# host.  Hence, we need the global override to be <=1 or it would override
# the per-interface setting to "strict" that we require.
#
# We bail out rather than simply setting it because setting 2, "loose",
# is unusual and it is likely to have been set deliberately.

'Making Felix compatible with loose mode' could perhaps be done by implementing source address checks ourselves in iptables.  But ISTR there's some reason why it's much better for us to let rp_filter do it.  (As well obviously being less code for us to maintain.)  @fasaxc does this ring any bells?

One more thing: strictly speaking, unprivileged containers can't spoof IPs anyway.
I'd probably want to figure out why Mesos needs (or thinks it needs) loose.

Matt and I just finished digging, seems there's a very specific scenario that requires rp_filter=2 in DC/OS. However, they enable it across all interfaces, when it really only needs to be enabled on one particular VTEP on each host. I'm going open a issue with DC/OS to make that change.

Damn, I forget the details for why it's hard to get an RPF check right in iptables but we did get it wrong when we implemented it that way and we made the switch to using the kernel's version because it's more comprehensive and earlier in the pipeline.
For IPv6, RPF checks are implemented as a dedicated iptables filter rather than a global option (so presumably we could have selective iptables rules that execute the RPF check only on the interfaces we need it).  If the iptables module supports IPv4 too, maybe that'd be an option.  OTOH, that would require a more recent kernel than we currently support.  That RPF check module isn't in the CentOS 6.5 kernel.

@fasaxc so that being said, implementing RPF checks ourselves sounds like something we should continue to avoid. The correct solution to the larger problem is to dial down DC/OS' overreaching configuration of rp_filter=2 to just the relevant interfaces. However, I'm also concerned that we won't have enough time to do that before DC/OS 1.8 is released, meaning calico would not be compatible with at all with the new release.
So, I'd propose the following:

Make the enforcement of rp_filter configurable in Felix, so that we could work in Loose mode. Obviously this is not the ideal solution, but it would at least serve to allow people to trial Calico in DC/OS while we work on the underlying issue.
Improve calicoctl's handling when rp_filter=2 on the host. Enhance it to refuse to launch calico/node when rp_filter=2, but also add some way to bypass that (--ignore-rpfilter) and launch node with felix configured to ignore the rp_filter=2
Submit patch to DC/OS so rp_filter is only set on the relevent interfaces, circumventing the previous two points.

I've opened https://dcosjira.atlassian.net/browse/DCOS-265 and submitted a PR to DC/OS

@djosborne Agreed, I think DC/OS should be fixed.
However, I'm not talking about rolling our own (which is what we used to do).  The kernel has two types of RPF check.  One type is controlled by the flag that we've been discussing, and only applies to IPv4.  The other type is a dedicated iptables match rule:
   rpfilter
       Performs a reverse path filter test on a packet.  If a reply to the packet would be sent via the same interface that the packet arrived on, the packet will  match.   Note  that,  unlike  the  in-kernel
       rp_filter,  packets  protected  by  IPSec are not treated specially.  Combine this match with the policy match if you want this.  Also, packets arriving via the loopback interface are always permitted.
       This match can only be used in the PREROUTING chain of the raw or mangle table.
  ...

for IPv6, you have to use the latter type so that's what we do.  What I'm wondering is, could we use that for IPv4 as well?  If we did that, I don't think it would be bypassed by the global "loose" setting.  the advantage is, we can have a condition on that rule so we say "if interface-name starts with cali and it fails the RPF check, DROP it" so we shouldn't interfere with DC/OS's requirement for loose on the interface it cases about.

Update on the DC/OS PR - the fix isn't as easily implementable in DC/OS as we thought. There are three different components of DC/OS which create a new virtual interface which all need rp_filter=2 to function properly. Currently, none of those components actually set rp_filter themselves, but instead rely on the kernel being configured with rp_filter=2 for default interfaces, so that when an interface is created, it automatically has rp_filter=2. The correct fix is probably to remove that from the default setting and have each component be responsible for setting rp_filter on the interface it just created.
However, it is highly unlikely we will have this implemented across all components in time for the DC/OS 1.8 release, or at all for that matter, as the DC/OS team is not interested in implementing it themselves, for the following reason:
In order for a container to spoof its IP, it would need to be run in privileged mode so that it can open a raw socket with CAP_NET_ADMIN and CAP_SYS_ADMIN. Then, if rp_filter was disabled, it would be able to spoof traffic. But arguably, a container with the privileged access to do this can do much worse than just spoofing traffic. So having rp_filter set to prevent traffic spoofing would be the least of your worries.
Though we can (and probably will) make this change across the necessary DC/OS components, we should assume we won't be able to complete it all in time for 1.8, and should instead allow Calico to run with loose rp_filter.  Additionally, I don't believe we need to go so far as to implement the rp_filter checks in a dedicated iptables match rule. Instead, we should do the necessary work to fix DC/OS before we add unnecessary features to felix.
@caseydavenport and @matthewdupre have agreed with this plan. @fasaxc does it sound agreeable to you?

If we're sure that containers can't spoof anyway then I'm happy to make the check configurable.
That said, the manpage for raw sockets says you only need CAP_NET_RAW, which is a lot narrower than than CAP_NET_ADMIN and CAP_SYS_ADMIN.  Does that change the calculation?  I'm struggling to think of a reason to have CAP_NET_RAW if you're only sending form your own IP but maybe those exist; is there a good place to warn people not to give CAP_NET_RAWto a container if you don't want it to spoof?

@fasaxc I was under the impression that Docker privileges were all or nothing, i.e. you gave a container full root access (--privileged), or you didn't.
But seems you can quite easily add a single privilege with docker run --cap-add=NET_RAW. I fear that there may be scenarios where users could have some reason to grant NET_RAW to a container, which would open them up to a spoof attack if rp_filter=loose.
Seems my original point that "If your container can open up a socket it, it must be root, and can do much worse than spoof traffic" is no longer true - you can only have permission to open NET_RAW without having full root access, and its quite easy to do this.
That being said, I think we still want this to be configurable as you've implemented - otherwise we're still incompatible with DC/OS 1.8, which looks bad on us. So we should definitely give proper warning to anyone who tampers with this setting, and anyone in DC/OS.
I've raised #19 to ensure we warn this to users of Calico in DC/OS.
We could also improve the felix log to point out how easy it is to grant a container the ability to spoof its IP: Should only be set to true if no workloads are run with CAP_NET_RAW. For docker, this means containers should not be run with the flag --cap-add=NET_RAW.

It is now possible to pass in a felix environment into the container to disable this check.  This is in the latest node image (0.21.0)

@djosborne Dan - can we close this?

There's still one piece of this left open - If rp_filter=loose, calicoctl node won't mention any failures, and felix will just continuously stack trace and restart once a container is launched. I think it'd be best to open a seperate issue at this point, as this one has been more of a diagnostic tracker.

We just came across this and although I read most of the comments here, I missed the final one above :(
I'd just opened https://github.com/projectcalico/felix/issues/1190 for our problem as I thought from the discussion here that this issue wouldn't cause felix to restart.
I've worked around it by doing the following for now:
docker stop calico-node
sysctl -w net.ipv4.conf.all.rp_filter=0
docker start calico-node
sysctl -w net.ipv4.conf.all.rp_filter=2

this appears to allow felix to start and continue working after setting the value back to 2.

@davison A configuration setting for Felix was added to degrade the error to just a warning, so that Felix and calico-node will function properly even when rp_filter == loose.
Instead of flipping rp_filter, set IgnoreLooseRPF to True.

@djosborne thanks, I'd seen that code diff but didn't realise it was already released tbh.  Took me a while to work out the actual name of the environment variable that should be used to add this to my docker strap, but I have it working now :)

@djosborne is there anything we can do to the Mesos docs to tell people to set this option?

Good call. Raised #278