Inheritance Discriminator should be included as property?

From @ferrx on May 31, 2017 19:14
The doc for Inheritance (relational) that covers the Discriminator here https://docs.microsoft.com/en-us/ef/core/modeling/relational/inheritance may need some tweaking.
When you create the blog_type discriminator via Fluent API (or automatically via inheritance), should you also create a property in the Blog class called blog_type ?
In Visual Studio, when you try to add a controller that uses the Blog model, it will extract blog_type as a property it should be using and fail to work. For example, if you created a PostsController where there is a 1-to-many relationship with Blog-Posts, Visual Studio will automatically toss in "blog_type" in a number of areas in the generated view and controller files.
Copied from original issue: aspnet/EntityFramework.Docs#400

From @ajcvickers on June 12, 2017 20:4
@divega This looks like it could be a scaffolding issue. If so, we should file a issue there. Thoughts?

@ajcvickers Definitively an issue in scaffolding. From the description there is no support for shadow-properties.
On the other hand, EF Core could help by creating a way to get a serializable representation of shadow properties, required original values, concurrency tokens, etc.

I stumbled upon the same problem and found a workaround so that discriminator won't be shown in views.
First create your model with custom discriminator:
public abstract class AbstractPage
    {
        public int Id { get; set; }

        [ScaffoldColumn(false)] // set this so codegeneraor won't include it in views
        public string PageType { get; set; } // discriminator
    }

Now configure this custom field to be used as discriminator in ApplicationDbContext:
public class AppDbContext : DbContext
{
    protected override void OnModelCreating(ModelBuilder builder)
    {
        base.OnModelCreating(builder);

        // configure discriminator
        builder.Entity<AbstractPage>(b => { b.HasDiscriminator<string>("PageType"); });
    }
}


fix: Issue #84 No loading effect and skeleton.

fix : Issue no #84 No loading effects and skeleton.

Added loading effects on login and register and a skeleton . which looks great..

Screenshots

I deleted the package-lock-json

@IrfanshaikH-7 please resolve all the changes given. Without that, I can't merge

sorry ! but I'm not sure which changes are you talking about, can you please explain..


⚠ Adacta-fintech.com has degraded performance

In b0b7e27, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 200
Response time: 1966 ms

Resolved: Adacta-fintech.com performance has improved in 2f48e5d.


Overall adjustments

-Added auto gold exchange feature
-Merged auto health and auto mana modules in only one named AutoHeal -Improved AutoHur
-Improved ThreadManager
-Fixed a few application errors

Is this repo stalled? Why isnt this in the project already?


Edits JS code comments block

Edits the JS comments section in the playbook to fix formatting/grammar and adds section about JSDocs.
Additions

Creates comments section sub-sections and adds note about JSDocs.

Changes

Discourages same-line comments.
Proper grammar in comments.

Review

@ascott1
@wpears
@mistergone

How's this PR looking?

:+1: Nice and straightforward.

Sorry I'm late on this, but I like same-line comments when the comment only applies to a single line. Are we taking an official stance on this?

I avoid same-line comments because Idiomatic prohibits them. They also tend to make lines really long.

True. I would only want to allow them in cases where the line doesn't go over 80 characters.

This strikes me as a it's-fine-to-break-this-rule-just-be-consistent-within-your-codebase scenario.

Sounds good to me.

We need a tag for that. IFTBTRJBCWYC


Add integration with Starlette

Starlette is a quite popular ASGI library, in part because it's at the core of the (to me somewhat surprisingly) vastly popular FastAPI project. Since I believe in the spec-first approach (contrary to FastAPI) and in the architectural design of openapi-core, I think it would be great to add an integration with Starlette.

I was thinking about it. I would go even further and try to integrate with FastAPI itself as an alternative to built-in approach.

Hm, I haven't thought about the technical details, but perhaps it's possible to have both because FastAPI is built on top of Starlette? Perhaps via a Starlette middleware like it's done for other sane web frameworks. I'm a bit sceptical about FastAPI to be honest. Starlette looks very clean and modular though.

Awesome, thanks for adding support for Starlette so quickly, @p1c2u! 🙏 🎉


TaskAttribute name is ambigous

With System.Threading.Tasks.Task. Yes, we can use full name like [TaskAttribute] or [BenchmarkDotNet.Tasks.Task], but it maybe better to rename attribute to resolve this frequently occurring naming conflict.

@azhmur Do you have any ideas about a better name for the BenchmarkDotNet.Tasks.Task class?

What about BenchmarkTask, that should less ambigous

My idea was something like BenchmarkSuite, but BenchmarkTask is even better.

@mattwarren, @azhmur, LGTM. I will change it in the next version.

Thanks, you library helped me greatly in researching what can be improved in .Net Tuple implementation.
https://github.com/azhmur/TupleBenchmark

@azhmur, you are welcome!


better optimize otlLib.buildSinglePos

the function that predicts the length of Device table doesn't properly take into account the DeltaFormat and the corresponding variable-length encodings of delta values, see discussion https://github.com/fonttools/fonttools/pull/1539/files#r289047422
/cc @mhosken

I suggest Not Planned, as this is rare.


Order shipment_state not updating after being shipped

We noticed that after shipping an order (from the admin), the shipment state would not change to shipped.
After digging around, it seems this is being caused by the way the order_recalculated event is being handled
The Solidus OrderUpdater class has this method, which updates the shipping state and other things:
def update
  order.transaction do
    update_item_count
    update_shipment_amounts
    update_totals
    if order.completed?
      update_payment_state
      update_shipments
      update_shipment_state
    end
    Spree::Event.fire 'order_recalculated', order: order
    persist_totals
  end
end

When Spree::Event.fire 'order_recalculated', order: order is called, the KlarnaSubsciber calls order.update_klarna_shipments:
  def update_klarna_shipments
    return unless shipment_state_changed? && shipment_state == "shipped"

    captured_klarna_payments.each do |payment|
      payment.payment_method.gateway.shipping_info(
        payment.source.order_id,
        payment.source.capture_id,
        shipping_info: to_klarna(
          payment.payment_method.preferred_country
        ).shipping_info
      )
    end
  end

and the to_klarna method reloads the order:
  def to_klarna(country = :us)
    SolidusKlarnaPayments::OrderSerializer.new(reload, country)
  end

... the order reload in the method above causes the OrderUpdater to no longer see changed values, including the shipment_state.
Maybe this should be a Solidus issue, but figured I would start here since it is only happening with Klarna orders.

Thanks for reporting. This seems like a valid issue. Did you get why to_klarna is calling reload?


Feat/add force_destroy_s3_bucket to main

Hey @oavdeev, can you please give it a check now?
Thanks

Hey @oavdeev , just fixed the commit hook


authentication improvements

First version of #45 issue about new entry points to have new authentication features.
Please note that no emails are sent, they are logged for now.
Here's the password changing: we use the updateMutator to just change the user password and let the hooks of the user model handle the password security logic.

You mean we already have a hook for hashing the password? Password change should have a logic quite similar to signup, the main part being hashing the password correctly. In the signup form, I think we don't use Vulcan but instead directly passport.
Anyway, do whatever works, but please document in the PR how the password hashing will work because that's the critical part

About the changing password, we already have a callback inside the user model that trigger before the update, that uses the same password hashing than the creation hook. It's automatically called when we use the update mutator, so that's how I proceeded (no need to implement it in another way since it's already functional).
The signup form has the same logic: the password is just given to the create mutator without modifications, and the mutator triggers the callbacks inside the user model.

New commit: email verification !
Here we have an Input inside the User admin area that triggers the "email sending" (logged atm).
This leads to a new API entry point "sendVerificationEmail" that creates a token thanks to passport (iron to be precise).
After verifications, the goal was to send an Url to the user shaped like "basicUrl/verify-email/token", but as I said it's only logged atm.
This token is already OK, and there's a page at the corresponding route that uses passport/iron again to decrypt the token and confirm that it corresponds to an user email.
We still need to implement:

the Url creation, since I didn't know how to access the basic app Url (I could have hardcoded "localhost" but I wanted it to be clear)
The email sending
The model logic: we can already know that someone followed the link but it has no effect on the model.
I don't think it's wise to implement a systematic email verification to every new user since it's not always wanted by the developers... If you have any idea i'd be glad to implement something

New commit: forgotten password.
Here, you can access to the new page "forgottenPassword" from the login form.
This page uses the new API entry point "sendResetPasswordEmail", that creates a token containing the email in a similar way than "sendVerificationEmail".
Using this URL, the user will be able to be redirected to "/reset-password/[token]", which allows the user to put his new password and reset it by using the API entry point "changePassword", which is responsible from changing a user's password while connected (see the commit "change password") and now also resetting a password if we provide an email in the input.
So the entry point "changePassword" didn't change: it still uses the update mutator to modify the password field directly.
We still need to implement the Url creation and the email sending.

For the URL you should expect it to be set as a parameter, check how Meteor works for instance, it has a setting like this. You can have the same in Next like "NEXT_PUBLIC_FRONTEND_URL"

On Meteor we seem to use Meteor.absoluteUrl() that is mocked to "http://vulcanjs.org/" on the Git repo; I guess I would put "NEXT_PUBLIC_FRONTEND_URL" on both .env.development and .env.production, but I feel unsure about it so I'll let you take the final decision :)

@Timi-Duban Beware that Meteor.absoluteUrl might be client side only. So maybe the setting we have for this is from Vulcan Meteor and not Meteor. Server-side, you can never tell what the URL is, a server doesn't know its own domain (only its IP).
For Vulcan Next repo:

in .env.development it should be something like http://localhost:3000
in .env.production, it should be https://vulcan-next.vercel.app, that's where we deploy the demo version

Then user are expected to modify it in their .local files

I'll track the rest of the developments there: https://github.com/VulcanJS/vulcan-next/pull/124
Currently, your implementation does too much client-side or using getStaticPaths. Instead, the API route should do most of the security work, and the components should be quite simple, simply triggering calls to the relevant API. See changePassword for instance.
But that's a good working basis!


Exposure Bracketing / Fusion

I have implemented it, but the mid tone has no shading at all, who knows how to do it correctly？

Did some simple searches, which seemed unlikely to produce good results in real time.
https://github.com/megvii-research/HDR-Transformer


Fixed issue with startDate and endDate being reversed

Appears the startDate and endDate were switched somehow.

👍 seeing the same thing

I don't think the label works in the right order if the time falls on the next day, it goes negative ...


fix build on cpu container

Checklist before submitting

[ ] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Recipe tests failed on CPU container with the following error:
from torch._C import *
ImportError: libcupti.so.10.2: cannot open shared object file: No such file or directory

because it used CUDA pytorch-base. And import torch fails for cuda pytorch-base on CPU container due to unavailability of CUDA libs.
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

Closing this PR as this change is not needed.


Where is timescaledb-docker-ha?

Where did the ha image repo go? https://github.com/timescale/timescaledb-docker-ha

It does exist, however it is currently private. Will see how we can make it public.

Thanks!

I am looking forward for this solution as well.

@allen13 the https://github.com/timescale/timescaledb-docker-ha is no public.


Windows 7 dependencies

When running on Windows 7, it appears the following are prerequisites for the agent (although the System Requirements document says there are none)

A version of Windows PowerShell which supports the Unblock-File command - so 3.0 or higher, Windows 7 ships with 2.0
The Universal C Runtime

It would be good if the Requirements document could list this.

Awesome.  Thanks for the heads up.  We will update docs.

You will hit this kind of weird exception in event view.
Faulting application name: Agent.Listener.exe, version: <IP_ADDRESS>, time stamp: 0x57461460
Faulting module name: i-ms-win-crt-runtime-l1-1-0.dll, version: 6.3.9600.18233, time stamp: 0x56bb4ebb
Exception code: 0xc0000135
Fault offset: 0x00000000000ecdd0
Faulting process id: 0xe18
Faulting application start time: 0x01d1e763e1b53193
Faulting application path: C:\WinCoreCLRAgent\bin\Agent.Listener.exe
Faulting module path: i-ms-win-crt-runtime-l1-1-0.dll
Report Id: 1f61bd6f-5357-11e6-80c4-000d3a7028e7
Faulting package full name:
Faulting package-relative application ID:

We don't need this anymore, since we package the CRT with the agent now.

@TingluoHuang Does this also cover the PowerShell 3.0 requirement? (Windows 7 ships with 2.0)

@qmfrederik good point. :)

I guess this can be referenced in requirements: http://social.technet.microsoft.com/wiki/contents/articles/21016.how-to-install-windows-powershell-4-0.aspx

#823


如何切换大模型？没看到具体的入口

Describe the issue
No response
Steps to reproduce
No response
GraphRAG Config Used
No response
Logs and screenshots
No response
Additional Information

GraphRAG Version:
Operating System:
Python Version:
Related Issues:

看这个视频  https://youtu.be/XiLEZzm7yCk

Please use GitHub issues to post bugs/feature request. We would love to continue engagement with the open source community over in GitHub Discussions at the top of this page.


Add basic developers section and update release settings

Signed-off-by: Ken Finnigan<EMAIL_ADDRESS>

LGTM


minor improvement to sonata-network example

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

Project coverage is 91.24%. Comparing base (c5666ce) to head (d1959fb).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #205   +/-   ##
=======================================
  Coverage   91.24%   91.24%
=======================================
  Files          95       95
  Lines        5708     5708
=======================================
  Hits         5208     5208
  Misses        500      500

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


Change qec-util to qec-utils in pyproject.toml

In the end I changed the repo name from qec-utils to qec-util. The reason is that couldn't find (in the Internet) any particular reason to choose utils over util, and also I already have all the scripts labelled util.py. Therefore, I believe it is better to keep everything as util to ensure consistency.


Kotlin property decompilation

This provides decompilation of most aspects of Kotlin properties, such as typing, flags, custom getters/setters, and delegates. It also provides more wrapper types for additional Kotlin sugaring.

Codecov Report
Patch coverage: 52.30% and no project coverage change.

Comparison is base (02c4ece) 77.40% compared to head (485ab09) 77.40%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@                Coverage Diff                 @@
##             develop/1.10.0     #275    +/-   ##
==================================================
  Coverage             77.40%   77.40%
- Complexity             8199     8258    +59
==================================================
  Files                   233      249    +16
  Lines                 26289    26553   +264
  Branches               6768     6736    -32
==================================================
+ Hits                  20348    20554   +206
- Misses                 3918     3953    +35
- Partials               2023     2046    +23

Impacted Files
Coverage Δ

src/org/jetbrains/java/decompiler/api/Plugin.java
0.00% <ø> (ø)

...ins/java/decompiler/api/language/LanguageSpec.java
0.00% <0.00%> (ø)

...java/decompiler/api/passes/LoopingPassBuilder.java
0.00% <0.00%> (ø)

...ns/java/decompiler/api/passes/MainPassBuilder.java
0.00% <0.00%> (ø)

...etbrains/java/decompiler/api/passes/NamedPass.java
0.00% <0.00%> (ø)

...brains/java/decompiler/api/passes/WrappedPass.java
0.00% <0.00%> (ø)

...s/java/decompiler/main/decompiler/ConsoleHelp.java
0.00% <0.00%> (ø)

...rains/java/decompiler/main/decompiler/GuiHelp.java
0.00% <0.00%> (ø)

...java/decompiler/main/plugins/InJarClassLoader.java
0.00% <0.00%> (ø)

...er/main/plugins/PluginImplementationException.java
0.00% <0.00%> (ø)

... and 82 more

... and 19 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Because of the impending merge of 1.9.x into 1.10 and the failing tests, I'll leave this for now and merge this once main has been merged into 1.10, and I'll fix the tests while doing so.


Could not load "Windows To Do" app error

Status
Available in
Channel Type
Cumulative update

In preview
Windows 11 Insider Preview Build 26120.785
Dev Channel
KB5042847

Dev Home version
1.1501.550.0
Dev Home Azure Extension version
1.1501.550.0
Windows build number
10.0.26120.785
Other software
OS Build Version: 10.0.26120.785.ge_release_svc_im_current_directadept.240609-0212
.NET Version: .NET 8.1.1
Steps to reproduce the bug

Please try restart your computer
Then try open and load "Windows To Do" app

Expected result
"Windows To Do" app will working
Actual result
Error loading "Windows To Do" app
Included System Information
CPU: 11th Gen Intel(R) Core(TM) i7-11370H @ 4.72GHz
Physical Memory: 37.83GB (12.61GB free)
Drive Storage: 119.12GB
Processor Architecture: x64

It sounds like the issue you're having is not related to Dev Home, so this isn't the correct place to open it. Please open your issue in Feedback Hub, and it will be seen by the right people to help.


make  cool

[x] answers
[x] limit number of posts per day or something, to prevent massive spam
[x] don't show questions or answers of banned individuals
[x] final refactor pass to cleanup ui code, maybe model too

done


A warning should be displayed when a build sphere is detected

#100 suggests that build spheres should only be detected if there is some kind of allied presence in it.
To balance this, an important warning message should be displayed when this happens. For example:
'''"Your EWS probe has detected something is building on a9410 in Velantia."'''
Justification: if #100 is fixed and you can detect a buildsphere in the F3 screen, it is because something detected it. It would be most silly to have something this important not triggering a warning message.
Imported from trac ticket #101,  created by bp on 07-01-2010 at 00:38, last modified: 02-25-2012 at 15:46
CCing<EMAIL_ADDRESS>

Alternatively or additionally, the sector in the minimap should flash green while the buildsphere is detected.
Trac comment by anonymous on 07-01-2010 at 12:28

An addendum to this - the minimap and F3 should only update to show a rock has been built on when a probe/ship detects the new base.
This will complement the above change
Trac comment by notjarvis on 07-01-2010 at 13:01

Replying to [comment:2 notjarvis]:

An addendum to this - the minimap and F3 should only update to show a rock has been built on when a probe/ship detects the new base.
This will complement the above change

done.  usually if you can see a build sphere you will see the base and that will trigger a notification.  if you can't stick around to eye the base you must figure out another way to notify your team.
Trac comment by Imago on 07-19-2010 at 06:47


Proposal for *.json

Hey, I'm making the port of the data from .gd to .json already, I think it will be a good first step.
One of the things that I find would be useful is to set the picture parameter always be an array of pictures, instead of a single one.
This way we will be able to use some dynamic usage of GridContainer in order to display said pictures.

If you're doing it as a contributor it's fine, but that's not part of this freelance job. I hope you're not doing it manually! Converting the data to JSON should take little time. I'm booked today but I can do it tomorrow if you want. Anyway, you can work with a .gd file in the meantime, it's just as fast to write. Then I'll convert all presentations with a script.


[1.16] Villagers Trade Enchanger There is no craftable in 1.16.5

I'm playing with some mods on 1.16.5 and I can't make the automatic trade machine with villagers because it doesn't appear to me, I wanted to make an automatic EMC factory using it.
I'm using the latest mod update for 1.16.5

It doesnt exist in 1.16.5


Update en.toml

Updated the en.toml file

I wanted something formal like a Menu or Table, that's why opted for this name.


Looking for contributors! 👨💻👩💻

Created as an experiment for the next project I was going to work on, decided to share the experiment which surprisingly seems to getting attention by GraphQL and React enthusiasts.
If you are interested in contributing to the codebase in any possible way to make it better (build processes, webpack, babel, HMR, better code structure, feature additions, docker image, deployment scripts, optimizations, bug fixes, etc.) please feel free to send PR, open issues or give suggestions.
In open source, we trust!

Hey atul,
I'll try to do my best. Kindly add me as a contributor.
Thank You
Yadu Nandan

Hi,
I'm working on some node.js projects and integration of third party api's. Allow me as a contributor.
Thanks


[fix](inverted index) normal process query for null condition when in…

…dex is missing
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run p0

run p0

run buildall

run p0


How do you use the membership hack??

do you like, make a bookmark or something?

U copy the link and do javascript: and paste the code and go to the very end and delete a space between the semicolon and done

No bookmark


examples: Default example to use LoadBalancerService type

Defaults the example Contour config to use a LoadBalancer service to match the docs provided on the Contour quickstart.
Fixes https://github.com/projectcontour/contour/issues/3319
Signed-off-by: Steve Sloka<EMAIL_ADDRESS>

@stevesloka we will need to support passing an IP, specifically <IP_ADDRESS>, to the Envoy Service for an LB service to work on kind. This is why the example and CI use a "NodePortService". We will eventually need this to support specifying a gateway.spec.addresses[]. Maybe we should remove the test-example-linux job until the example can support all default fields of a Contour. Thoughts?

I see why the test is failing, but not sure why we're hard coding the NodePort. Isn't there a chance that you'll conflict? Also, if you deployed a second instance it for sure would conflict in the same cluster.

True, but I don't think we want to expose managing nodePorts for a "LoadBalancerService" type.

I see why the test is failing, but not sure why we're hard coding the NodePort.

@stevesloka the node ports are being hard-coded due to the kind config:
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
- role: worker
  extraPortMappings:
  - containerPort: 30080
    hostPort: 80
    listenAddress: "<IP_ADDRESS>"
  - containerPort: 30443
    hostPort: 443
    listenAddress: "<IP_ADDRESS>"

Isn't there a chance that you'll conflict? Also, if you deployed a second instance it for sure would conflict in the same cluster.

The NetworkPublishing API does not currently expose port numbers for the NodePortService type. The plan is to add support as identified by https://github.com/projectcontour/contour-operator/issues/159.

It seems like the problem here is that the defaults are currently set to make it easier to test locally - that is, they're defaults for kind. @stevesloka is opening this PR to change the defaults so that they will match the Getting Started documentation in the event that you're installing using the Operator on a cloud or similar.
I think the larger question to answer for this PR is: which default is the right one? If we don't default to kind, then we will need to update the testing runs to ensure that we're testing the right things.
I think there are two options:

accept this PR, change the default to Service of Type Loadbalancer, and update the testing, which may require us adding more to NetworkPublishing to allow it to describe a Kind deployment, as opposed to a generic cloud one.
Change the getting started documentation to indicate that you get a Nodeport and no upstream load balancer unless you add NetworkPublishing bits to your Contour object.

I agree, let's just leave this as-is and update the docs until the endpoint bits are ready.


Langoose - language for goose

it's compiled to current JSON format, so rules on langoose are fully backward compatible with current parser

Langoose is set of helpers. Helper always returns an object (desciptor). There are three types of helpers:

actions - return action descriptors
rules - return rules descriptors
transforms - return transform descriptors

Each descriptor can have a set of modifiers, which add new properties to the descriptor. This set differs between descriptor types, and can be special for specific descriptor. Modifiers start with $ symbol (like in PHP you know lol)
Example:
const a = require('helpers').actions;

return a.wait('.modal_visible').$inside('body');

returns
{
  type: 'wait',
  scope: '.modal_visible',
  parentScope: 'body'
}

where:
a is set of actions helpers
wait is an action helper, which returns a descriptor (JS object)
$inside is a modifier, which adds parentScope property to the descriptor


"Revision" field disambiguation

Suggestions:
LastAttemptedRevision > LastAttemptedChartRevision
LastAppliedRevision >: LastSuccessfulChartRevision
LastReleaseRevision > no change needed
"ChartRevision" to me helps disambiguate from the "ReleaseRevision" in "LastReleaseRevision', which represents a different kind of revision (chart vs release). I think "Successful" is more accurate than "Applied" since even a failed attempt could be considered applied unless/until it is uninstalled or rolled back.

The LastAppliedRevision/LastAttemptedRevision are intended to be common fields for all the toolkit reconcilers, as of now these are used in kustomize and helm controllers. I get your point that from a Chart/Release perspective they are ambiguous.

We could record the chart revision as given by Helm in another Chart* status field, question is if this gives us anything of additional value.

I see, what about "Source" or "Artifact" rather than "Chart" then:
LastAttemptedSourceRevision
LastSuccessfulSourceRevision
LastAttemptedArtifactRevision
LastSuccessfulArtifactRevision

@seaneagan using the same stats fields e,g, LastAppliedRevision/LastAttemptedRevision as a standard across all toolkit controllers allows other controllers/integrations to rely on those for detecting drift. These integrations don't have to depend on our API packages, using the dynamic client-go you could lookup an object.status and check the 2 fields. If we change them in helm-controller, then it will would break the standard. I propose we document these fields in helm-controller docs and explain what they mean in the Helm context.

Sure, I guess it's easy enough for an end user to distinguish based on the field values what it likely means as well, it's just something that tripped me up for a second when looking at the field names only, before actually using the tool. Thanks for considering!


custom nginx json format support?

Hi,
I'm trying to process an access log in the following format:
log_format json
'{"time":"$time_iso8601",'
'"remote_addr":"$remote_addr",'
'"http_x_forwarded_for":"$http_x_forwarded_for",'
'"request_method":"$request_method",'
'"server_protocol":"$server_protocol",'
'"request_uri":"$request_uri",'
'"status":$status,'
'"request_length":$request_length,'
'"request_time":$request_time,'
'"body_bytes_sent":$body_bytes_sent,'
'"bytes_sent":$bytes_sent,'
'"http_referrer":"$http_referer",'
'"http_user_agent":"$http_user_agent"}';
Is there a guide somewhere on how to process the input format for custom logs?
Thank you!

Please take a look at this post for more details. Otherwise, feel free to post a few lines from your access log and I can take a look.

Thank you for replying, much appreciated.
I think i'm just struggling to get the correct configuration.
Here's a snippet of the log I'm trying to parse, thanks again.
{"time":"2022-09-27T06:18:57+00:00","remote_addr":"<IP_ADDRESS>","http_x_forwarded_for":"<IP_ADDRESS>, <IP_ADDRESS>","request_method":"GET","server_protocol":"HTTP/1.1","request_uri":"/leafmailer2.8.php","status":403,"request_length":794,"request_time":0.000,"body_bytes_sent":192,"bytes_sent":394,"http_referrer":"-","http_user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36"} {"time":"2022-09-27T06:18:58+00:00","remote_addr":"<IP_ADDRESS>","http_x_forwarded_for":"<IP_ADDRESS>, <IP_ADDRESS>","request_method":"GET","server_protocol":"HTTP/1.1","request_uri":"/mailer.php","status":403,"request_length":787,"request_time":0.000,"body_bytes_sent":192,"bytes_sent":394,"http_referrer":"-","http_user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36"} {"time":"2022-09-27T06:18:58+00:00","remote_addr":"<IP_ADDRESS>","http_x_forwarded_for":"<IP_ADDRESS>, <IP_ADDRESS>","request_method":"GET","server_protocol":"HTTP/1.1","request_uri":"/1.php","status":403,"request_length":782,"request_time":0.000,"body_bytes_sent":192,"bytes_sent":394,"http_referrer":"-","http_user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36"} {"time":"2022-09-27T06:18:59+00:00","remote_addr":"<IP_ADDRESS>","http_x_forwarded_for":"<IP_ADDRESS>, <IP_ADDRESS>","request_method":"GET","server_protocol":"HTTP/1.1","request_uri":"/k.php","status":403,"request_length":782,"request_time":0.000,"body_bytes_sent":192,"bytes_sent":394,"http_referrer":"-","http_user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36"}

Sorry for the delay. This should do it:
goaccess access.log --log-format='{ "time": "%dT%t+%^", "http_x_forwarded_for": "%h,%^", "request_method": "%m", "request_uri": "%U", "server_protocol": "%H", "status": "%s", "request_length": "%b", "request_time": "%T", "http_referrer": "%R", "http_user_agent": "%u" }' --date-format='%Y-%m-%d' --time-format=%T

Thanks again! much appreciated


Refactor ProjectReferences in AppHost

At a high-level there are 2 problems with how we are using ProjectReference to reference the individual "service application" projects in the AppHost.

The AppHost may not have a compatible TFM with the referenced application project. For example if the referenced application project was targeting net8-windows.
When we are generating IServiceMetadata code, we are using ReferencePathWithRefAssemblies items, which means if the ProjectReference has ReferenceOutputAssembly="false" on it, no IServiceMetadata code will be generated.

To resolve these issues, we are taking the following approach:

By default ProjectReferences in the AppHost will mean a reference to a "service application", and not a regular project reference. If an AppHost project truly wants a ProjectReference to another project, it can be marked as <ProjectReference Include="..." AppHostLibrary="true" />.
ProjectReferences to service applications will be marked ReferenceOutputAssembly=false, SkipGetTargetFrameworkProperties=true, ExcludeAssets=all. This will cause the AppHost to not reference the service app projects.
Refactor the IServiceMetadata code gen to act directly on ProjectReference items.

Fix https://github.com/dotnet/aspire/issues/1074
Fix https://github.com/dotnet/aspire/issues/1563
Microsoft Reviewers: Open in CodeFlow

Looking forward to checking this out! One scenario I wanted to make sure we could handle is an Aspire AppHost referencing a self contained app - that currently breaks today.

One scenario I wanted to make sure we could handle is an Aspire AppHost referencing a self contained app - that currently breaks today.

Do you have repro steps I can try?
I took eshop, made one of the projects <SelfContained>true</SelfContained> and it still works.

To resolve these issues, we are taking the following approach:

By default ProjectReferences in the AppHost will mean a reference to a "service application", and not a regular project reference. If an AppHost project truly wants a ProjectReference to another project, it can be marked as .

Reversing this behavior might make more sense. The default would be a regular ProjectReference, as one would expect. And for a service-application-project-reference you can set some ServiceApplicationLibrary="true". That would be less surprising.

Reversing this behavior might make more sense.

That would fall into the same category as approach (1) in https://github.com/dotnet/aspire/issues/1563#issuecomment-1898826093 - adding a new item type like AspireProjectResource. The problem with those approaches is that tooling doesn't know how to add a new item, or set this special metadata on ProjectReference. We would need to teach the tooling, for example add a new dotnet add aspire-reference command.
The 80+% case here is that when an AppHost has a ProjectReference, it is to an executable that it wants to start when the AppHost starts. That's why I think using an empty ProjectReference for this case makes the most sense.

Overall comment: Correct me if I'm wrong, but I don't believe this change is braking for most of the existing Aspire apps, right? meaning, for all of the customers that created Aspire apps using preview2, and will now want to upgrade their workload and references to packages, they won't need additional changes for this to work. (unless of course they are using libraries from their apphost)

Overall comment: Correct me if I'm wrong, but I don't believe this change is braking for most of the existing Aspire apps, right? meaning, for all of the customers that created Aspire apps using preview2, and will now want to upgrade their workload and references to packages, they won't need additional changes for this to work. (unless of course they are using libraries from their apphost)

Correct this is not breaking for normal Aspire apps. It is breaking for people using ProjectReferences and needing to reference those projects from their AppHost. In that case, they will need to set AspireHostLibrary=true.

I plan on merging this today in order to get it in for preview3 with enough bake time. Let me know if you have any feedback that would block merging this. We can tweak it as we go after merge as well.


automation: use PR's last commit's hash for filename

Snapshot rpms have a release of '0.${date}git${commit-hash}'
Previously, the commit hash was HEAD, but that was a merge commit hash.
Changed to use HEAD~1 which is the actual last commit from the PR.

ci build please

ci build please

ci build please

ci build please

ovirt-web-ui-1.5.0-0.20181110git3359ba0.el7.noarch.rpm
ovirt-web-ui-1.5.0-0.20181110git3359ba0.fc28.noarch.rpm
^ 'git3359ba0'


Multiple maps in React app not cooperating

Describe the bug
Our React app has mutiple pages containing OpenLayers maps. Some pages even have multiple maps in different components on the page like a tab view. The first load and render of a map works as expected but we have come to notice that subsequent map instance renders have their tile layers disappear and show as white until you hover over a feature or zoom on the map. It appears that the different map instances are having some tile storage collision or something but I don't know enough about OL under the hood to diagnose this properly. I also expect it's to do with us having a React wrapper component to use OL maps in.
Expected behavior
Multiple map instances on app pages to operate independently and not have their tiles disappear until interacted with.
Initial map loads fine:

Subsequent instances on different pages or tabs don't show tiles:

@dechristopher Can you share a minimal repository that exposes the issue?
A workaround could be to call updateSize() on the map when you switch to the other tab.

@ahocevar running updateSize in a react useEffect on tab change did the trick for us. In some cases we also have to poke the map by zooming a fraction of a zoom level in and out to force the tiles to re-render. Closing.


[Reminders] Improve due date change logic

Extension
https://www.raycast.com/extensions/reminders
Description
Currently, in "My Reminders", Cmd+D opens a cool due date change prompt where you can type e.g. "Tomorrow" or "Next week".
This feature request is to change the behavior of typing days like "Thursday" to assign them to the next future Thursday, rather than Thursday in the current week (which could be in the past). So on a Friday, if you change the due date to Thursday, it should change it the Thursday 6 days in the future instead of 1 day in the past. (As far as I know, changing due dates to be a new date in the past is not part of any normal workflow.)
Who will benefit from this feature?
Anyone using Cmd+D in Raycast Reminders extension.
Anything else?
No response

We could not find the extension related to this issue. Please update the issue with the correct link to the extension.

I am unclear what the bot means. https://www.raycast.com/extensions/reminders seems to be the correct link to the extension.

I disagree with the bot, this would be a good improvement 🤷

Looks like this is a baked-in extension of some kind that is not in this code base, even though it works the same as an extension.


Migrate sponsors

Resolves #114 and sets up #73 for the future, continuation of PR #153

One feature in Icarus4's sponsors.js is for a person to remove themselves from someone else's Pro Sponsor channel. I'm thinking:

Rename /sponsors coolkid [user] to /sponsors invite [user]
Rename /sponsors uncoolkid [user] to /sponsors uninvite [user]
Create /sponsors leave [channel] for people who want to leave a Pro Sponsor channel.

One feature in Icarus4's sponsors.js is for a person to remove themselves from someone else's Pro Sponsor channel. I'm thinking:

Rename /sponsors coolkid [user] to /sponsors invite [user]
Rename /sponsors uncoolkid [user] to /sponsors uninvite [user]
Create /sponsors leave [channel] for people who want to leave a Pro Sponsor channel.

@BobbyTheCatfish

Weighing in concerning setup for #73, that setup would likely fall into subcommand of /mod (Likely /mod sponsor [@sponsor] or include a button to grant access for 3 minutes to determine context (time is negotiable, but I figure this isnt something that would need to be dynamic) on the mod card. That is something for the future though...

Rename /sponsors coolkid [user] to /sponsors invite [user]
Rename /sponsors uncoolkid [user] to /sponsors uninvite [user]
Create /sponsors leave [channel] for people who want to leave a Pro Sponsor channel.

Implemented

Weighing in concerning setup for https://github.com/LaughLax/icarus5/issues/73, that setup would likely fall into subcommand of /mod (Likely /mod sponsor [@sponsor] or include a button to grant access for 3 minutes to determine context (time is negotiable, but I figure this isnt something that would need to be dynamic) on the mod card. That is something for the future though...

As discussed on discord, I've added a button to view locked channels to mod flags.

Is this just for pro sponsors or can we add additional channels for Mod override to be used? ie if a flag appears in a Destiny clan chat?

It shows the button for every channel, which can help prevent edge cases where someone can't see a channel that they should be able to, or if channel permissions change.

Excellent, I have no more concerns


Add possibility to move boxes from one to another container

If can add an clone to another box. That must be great.

Can you explain more in detail what you want to do ?

Can you give me some code snapshots, to see how you have done this ?
So i can improve my code for better integration.

Thx, i will have a look later

Looks good :)
So the gif represents now your version of "dnd-grid" based on css grids ?

Okay, so it's the same as in the repo you shared.
I will try to make my code more flexible for this kind of usecase.
But for the next 2 weeks i will not have much time.

@dvdbot Could I have access to your work in progress repo for this. This is the same use case I have been trying to get to work.

@dvdbot  Hi, Is this code published anywhere? Sound great I will be happy to work with it.
Did u share it?

Hi, Did u share it somewhere? I would love to check it also. I'm trying to do the same, drag and drop from other list to this dnd-container.

@dvdbot Could I also have access to your work? We are trying to do the same but with vue-grid-layout, and we will be happy to use yours if it is better.

@DannyGoldner first, please don't comment three times... one is enough 😂
second, I may be able to rewrite it so it will be share-able but that will take sometime and project deadline is tomorrow 😅

Tomorrow? I will wait :-)
Be more than happy to help

@dvdbot Can't wait! please update.
I have tried to do the same with vue-grid-layout but it just don't work.
I was thinking that while dragging, I create new instance of item that should follow the mouse movement untill I drop it, which is the new placement of the new item. Didn't work :-/

@dvdbot Any News?

Also curious, I am really wanting to use this awesome lib but I absolutely need the ability to drop in dynamically added elements. I am roadblocked at

Error in mounted hook: "Error: Can not find container"

@dvdbot , I am also wondering to know what's your latest solutions to get the .gif you had show before, since it had been a year, did you get more advanced solutions?


Investigate how magic link should work

is this still necessary? the functionality should be provided by BE team - more info in #temp-magic-link


Option to disable Suspense (for e.g. Fresh)

Current Behavior

Using any v2.x.x ReactPlayer component results in errors when rendered with Fresh:
[Error] Error: Missing Suspense. The throwing component was: ReactPlayer
	(anonymous function) (main.js:8:842)
	I (chunk-HGUCLWZ2.js:1:7033)
	ce (chunk-HGUCLWZ2.js:1:8896)
	walk (main.js:43:2032)
	walk (main.js:43:2233)
	revive (main.js:43:2242)
	Module Code (520775:39:1800)

This is largely due to react-player forcing the use of Suspense as long as it's rendered in the browser. This approach works fine for most frameworks, but since Fresh's render method is synchronous and non-streaming it doesn't support Suspense boundaries.
Expected Behavior

I would suggest adding an option to disable Suspense, for cases where Suspense is not supported at all. Currently Suspense is always enabled;
https://github.com/cookpete/react-player/blob/662082a2f2edc863e8ca9cefdd7a3c88ad49ea0d/src/ReactPlayer.js#L174-L180
as long as the component is rendered in the browser:
https://github.com/cookpete/react-player/blob/662082a2f2edc863e8ca9cefdd7a3c88ad49ea0d/src/ReactPlayer.js#L12-L18
Steps to Reproduce

deno run -A -r https://fresh.deno.dev repro-example
Add react-player to import-map, e.g.

{
  "imports": {
    "react-player": "https://esm.sh/react-player@2.12.0?alias=react:preact/compat,react-dom:preact/compat:preact/compat&deps=react,react-dom",
  }
}

Render any <ReactPlayer/>.

Environment

URL attempting to play:  Any
Browser: Any
Operating system: Any
jsFiddle example: None

is this still an issue?
is Deno polyfilling window?
see this code in ReactPlayer
https://github.com/cookpete/react-player/blob/64c2130218ae610a1b2ed63647a35530fa7c0a97/src/ReactPlayer.js#L12-L18

is this still an issue?
is Deno polyfilling window?
see this code in ReactPlayer
https://github.com/cookpete/react-player/blob/64c2130218ae610a1b2ed63647a35530fa7c0a97/src/ReactPlayer.js#L12-L18

Yes, they do actually polyfill window but iirc the global document is browser-only. There's lacking documentation on the specifics but the gotcha was at least noted in the Remix docs.

Updated #1632 with a better implementation that doesn't change the API.


Proxy Images

https://www.planttext.com/
Course:
TBD
Learning Path:
https://www.pluralsight.com/paths/design-patterns-in-c

@startuml
title Proxy
class Client
interface IService {
+void SomeMethod()
}
class Proxy {
+void SomeMethod()
}
class RealService {
+void SomeMethod()
}
IService <|-left- Client: Calls
IService <|-down- Proxy: Implements
IService <|-down- RealService: Implements
Proxy -right-|> RealService: Calls
@enduml

@startuml
skinparam Shadowing false
skinparam sequenceArrowThickness 3
skinparam roundcorner 20
skinparam maxmessagesize 200
skinparam ParticipantPadding 20
Client -> Proxy: SomeMethod()
activate Proxy
Proxy -> RealService : SomeMethod()
activate RealService
RealService --> Proxy: SomeMethod() Response
deactivate RealService
Proxy --> Client: SomeMethod() Response
deactivate Proxy
@enduml

@startuml
title Proxy
class Client
class RealService {
+void SomeMethod()
}
class Proxy {
+void SomeMethod()
}
Client - Proxy: Calls >
RealService <|-down- Proxy: Inherits
Proxy -up- RealService: Calls >
@enduml

@startuml
title Proxy
class Client
interface IService {
+void SomeMethod()
}
class Proxy {
+void SomeMethod()
}
class RealService {
+void SomeMethod()
}
IService -left- Client: Calls <
IService <|.down. Proxy: Implements
IService <|.down. RealService: Implements
Proxy -right- RealService: Calls >
@enduml


feature request: add --help option

:bowing_man:

This would almost certainly involve pulling in a CLI crate (i.e. most likely clap) and thus siginifanctly increase the binary size. It's a tradeoff for which I haven't made up my mind yet. Can you expand why you would like an --help option?
Same story for https://github.com/nikstur/userborn/issues/9

if argv[1] == "--help" then
  print("userborn v $version")
  print("usage: userborn <configfile> <directory to write to>"

just that would be a huge improvement
i had to dig into the source code because i had no idea how to operate the program


ci: update codecov workflow to use gcovr

ci: codecov: use gcovr and upload cobertura style file
kernel: fatal: remove LCOV exclusion

Fixes #66656

ci: codecov: use gcovr and upload cobertura style file

Could you please make the commit message slightly more explicit? Is the change motivated by addressing a particular bug/issue with lcov? Or just moving to a more modern tool? Something else?
Thanks!

@nashif Would it make sense to make gcovr the default when we do twister --coverage? Seems odd to have CI run the non-default coverage tool

@nashif Would it make sense to make gcovr the default when we do twister --coverage? Seems odd to have CI run the non-default coverage tool

yeah, we can do that. @golowanow  can you take care of that?

@nashif Would it make sense to make gcovr the default when we do twister --coverage? Seems odd to have CI run the non-default coverage tool

yeah, we can do that. @golowanow can you take care of that?

#66712


Provide mechanism and examples to use QR Code flows for issuance

We should provide examples and add missing functionality (e.g., message validators) for how to use QR Codes to issue and receive a VC.
Issuance flow:

issuer creates VC and puts that VC into a message using DAF. The message contains a simple callback URL.
holder scans the message (e.g., QR Code) and provides it to DAF for further processing.  The response is sent to the callback URL, e.g., approved / not approved. Sending the response is important in some cases to acknowledge that the holder received the VC.

relates to #83

@awoie this example has everything except for callback URL. It is using serviceEndpoint in DIDDoc instead. Can we close this issue? We will implement something like callback URL when implementing JWM reply_url

We will implement something like callback URL when implementing JWM reply_url
I think it is a good idea to separate these concepts.
Most likely not all messages will be JWM

that sounds good. will close this issue.


refactor(api): Remove failed command state

Overview
This goes towards EXEC-301.
This removes this piece of internal Protocol Engine state:
https://github.com/Opentrons/opentrons/blob/7689521103796ee548cea6503ad1f6b6503c0cd9/api/src/opentrons/protocol_engine/state/commands.py#L155-L156
It's only used as a pagination helper for robot-server, and it's sort of semantically problematic in a world where a run has many failed commands and none of them are necessarily fatal.
Test Plan
To do.
Changelog
To do.
Review requests
To do.
Risk assessment
To do.

Closing for now: this tempts us down a robot-server pagination rabbithole that doesn't seem productive right now. I'll go with a different approach that doesn't involve removing this piece of state.


Diagnosing Kestrel Flakiness

Trying to figure out what kestrel test is hanging. Using binary elimination as we have no access to logs easily.

We came up with an idea to put a long running test warning timer directly into our custom test runner.
Or failing that you could turn the xunit diagnostic logs on at least temporarily. They're very noisy but good for finding hangs.

Or, are you not going to check this in i.e. just run the PR validation pipelines until you're done?

This.

Or failing that you could turn the xunit diagnostic logs on at least temporarily. They're very noisy but good for finding hangs.

Sure. I think I can enable it here: https://github.com/aspnet/AspNetCore/blob/3cd5054eb5d8851b25881cd05cccb931aaa022e6/src/Servers/Kestrel/xunit.runner.json

Found it! ContentLengthReadAsyncSingleBytesAtATime is our offender.

This has been updated. I'd like to get this in soon to start unblock more PR builds.


[Feature Request] Integration with Periodic Notes plugin

I've been using the OG Calendar plugin + Periodic Notes for a long time, but I really like a lot of the extra features that OZ Calendar has and I'm excited to try it out. But it would be nice if OZ Calendar could integrate with the Daily/Weekly/Monthly notes the way Calendar does, both for creating notes using the template(s) and for having additional functionality like week and month overviews for those note types.
Full disclosure, another reason I want to move to this plugin is because Calendar appears to be unmatained, and looking now I also see that Periodic Notes is also relatively unmaintained; maybe another option (though a much larger lift) would be baking the Periodic Notes concept in to OZ Calendar?
Related to/Possible dupe of: #5

I'd like to echo this!  This plugin is really great and it would be perfect if I could create daily notes the same way I do with Calendar/Periodic Notes.

Second this too, would be awesome

I saw this plugin recommended by Vlad Campus on YouTube but I agree with others. Currently I would need to keep the original calendar plugin for the Periodic Notes system, so it isn't worth having both. If the Calendar could support PN it would be a great replacement for it.


ColorSplash

ColorSplash Extension:

Hi @Sulagna-Dutta-Roy ,
I hope you're doing well. I've addressed the issue #1366  and created a pull request to resolve it.
Could you please review the PR and let me know if any adjustments are needed?
Also please check the label again and modify it according to my work in PR.
Best regards,
Tanisha Garg
https://github.com/Sulagna-Dutta-Roy/GGExtensions/assets/157527085/d4bb36cb-97d6-4c02-8880-bd7b31bde530

@Sulagna-Dutta-Roy Please check the label of level and if needed then please modify it according to my PR work.

@Sulagna-Dutta-Roy Please check the label of level and if needed then please modify it according to my PR work.

As per the guidelines level1: Entry Level Projects
Level2: Intermediate Projects
Level3: Advanced projects
I checked this PR, currently it's showing as entry level but considering it I added level2. Advanced level project should be unique and big level

@Sulagna-Dutta-Roy Thankyou mam, will keep this thing in mind for future projects.


[Flake e2e (0)] Fail Forward Upgrades when a CSV resource is in a failed state [It] eventually reports a successful state when using skip ranges

Flaky Test Report

Failure Log Link
Failure Log
Relevant Failure Log
------------------------------
• [FAILED] [398.692 seconds]
Fail Forward Upgrades when a CSV resource is in a failed state [It] eventually reports a successful state when using skip ranges
/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/fail_forward_e2e_test.go:389

  Captured StdOut/StdErr Output >>
  waiting 103.714261ms for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - NO_CONNECTION
  waiting 1.705552809s for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - IDLE
  waiting 203.34317ms for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - TRANSIENT_FAILURE
  waiting 594.885807ms for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - CONNECTING
  waiting 200.681952ms for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - TRANSIENT_FAILURE
  waiting 12.99946988s for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - READY
  probing catalog mc-csv-failed-7h6c9 pod with address mc-csv-failed-7h6c9.fail-forward-e2e-w6cdz.svc:50051
  skipping health check
  waiting 103.496755ms for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - NO_CONNECTION
  waiting 2.26095134s for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - IDLE
  waiting 1.188746873s for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - CONNECTING
  waiting 18.594727433s for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - TRANSIENT_FAILURE
  waiting 999.441847ms for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - READY
  probing catalog mc-csv-failed-7h6c9 pod with address mc-csv-failed-7h6c9.fail-forward-e2e-w6cdz.svc:50051
  skipping health check
  waiting 106.62133ms for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - NO_CONNECTION
  waiting 3.604420787s for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - IDLE
  waiting 810.787389ms for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - CONNECTING
  waiting 18.387474948s for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - TRANSIENT_FAILURE
  waiting 1.000335935s for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - CONNECTING
  waiting 19.999753332s for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - TRANSIENT_FAILURE
  waiting 1.646247834s for catalog pod fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9 to be available (for sync) - READY
  probing catalog mc-csv-failed-7h6c9 pod with address mc-csv-failed-7h6c9.fail-forward-e2e-w6cdz.svc:50051
  skipping health check
  Using the kubectl kubectl binary
  Using the artifacts/fail-forward-e2e-w6cdz output directory
  Storing the test artifact output in the artifacts/fail-forward-e2e-w6cdz directory
  Collecting get catalogsources -o yaml output...
  Collecting get subscriptions -o yaml output...
  Collecting get operatorgroups -o yaml output...
  Collecting get clusterserviceversions -o yaml output...
  Collecting get installplans -o yaml output...
  Collecting get pods -o wide output...
  Collecting get events --sort-by .lastTimestamp output...
  << Captured StdOut/StdErr Output

  Timeline >>
  STEP: creating the testing namespace with an OG that enabled fail forward behavior @ 11/06/23 13:55:52.872
  created the fail-forward-e2e-w6cdz testing namespace
  STEP: deploying the testing catalog @ 11/06/23 13:55:52.949
  Creating catalog source mc-csv-failed-7h6c9 in namespace fail-forward-e2e-w6cdz...
  Catalog source mc-csv-failed-7h6c9 created
  STEP: creating the testing subscription @ 11/06/23 13:56:08.797
  STEP: waiting until the subscription has an IP reference @ 11/06/23 13:56:08.805
  13:56:13.0237: subscription fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9-sub state: UpgradePending (csv example-operator.v0.1.0): installPlanRef: &v1.ObjectReference{Kind:"InstallPlan", Namespace:"fail-forward-e2e-w6cdz", Name:"install-gcpf4", UID:"e0a9e18b-3acd-4551-8b2c-a2fd84f44f8e", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"2373", FieldPath:""}
  waiting 4.21[780](https://github.com/operator-framework/operator-lifecycle-manager/actions/runs/6771572912/job/18402234628#step:5:781)5022s for subscription fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9-sub to have installplan ref: has ref &v1.ObjectReference{Kind:"InstallPlan", Namespace:"fail-forward-e2e-w6cdz", Name:"install-gcpf4", UID:"e0a9e18b-3acd-4551-8b2c-a2fd84f44f8e", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"2373", FieldPath:""}
  STEP: waiting for the v0.1.0 CSV to report a succeeded phase @ 11/06/23 13:56:13.023
  waiting for CSV fail-forward-e2e-w6cdz/example-operator.v0.1.0 to reach condition
  waited 196.299543ms for csv fail-forward-e2e-w6cdz/example-operator.v0.1.0 - Installing (InstallSucceeded): waiting for install components to report healthy
  waited 196.310643ms for CSV fail-forward-e2e-w6cdz/example-operator.v0.1.0: to be in phases [Succeeded], in phase Installing (InstallSucceeded): waiting for install components to report healthy
  waited 189.081397ms for csv fail-forward-e2e-w6cdz/example-operator.v0.1.0 - Installing (InstallWaiting): installing: waiting for deployment example-operator-controller-manager to become ready: waiting for spec update of deployment "example-operator-controller-manager" to be observed...
  waited 189.085397ms for CSV fail-forward-e2e-w6cdz/example-operator.v0.1.0: to be in phases [Succeeded], in phase Installing (InstallWaiting): installing: waiting for deployment example-operator-controller-manager to become ready: waiting for spec update of deployment "example-operator-controller-manager" to be observed...
  waited 189.807402ms for csv fail-forward-e2e-w6cdz/example-operator.v0.1.0 - Installing (InstallWaiting): installing: waiting for deployment example-operator-controller-manager to become ready: deployment "example-operator-controller-manager" not available: Deployment does not have minimum availability.
  waited 189.812302ms for CSV fail-forward-e2e-w6cdz/example-operator.v0.1.0: to be in phases [Succeeded], in phase Installing (InstallWaiting): installing: waiting for deployment example-operator-controller-manager to become ready: deployment "example-operator-controller-manager" not available: Deployment does not have minimum availability.
  waited 1.598454321s for csv fail-forward-e2e-w6cdz/example-operator.v0.1.0 - Succeeded (InstallSucceeded): install strategy completed with no errors
  waited 1.598455722s for CSV fail-forward-e2e-w6cdz/example-operator.v0.1.0: to be in phases [Succeeded], in phase Succeeded (InstallSucceeded): install strategy completed with no errors
  STEP: updating the catalog with a broken v0.2.0 csv @ 11/06/23 13:56:15.197
  STEP: removing the existing catalog source @ 11/06/23 13:56:15.197
  STEP: removing the previous catalog source pod(s) @ 11/06/23 13:56:15.399
  waiting for the catalog source mc-csv-failed-7h6c9-z2w6v pod to be deleted...
  STEP: updating the catalog with a new bundle images @ 11/06/23 13:56:16.421
  Creating catalog source mc-csv-failed-7h6c9 in namespace fail-forward-e2e-w6cdz...
  Catalog source mc-csv-failed-7h6c9 created
  STEP: verifying the subscription has installed the current csv @ 11/06/23 13:56:39.597
  13:56:39.7981: subscription fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9-sub state: AtLatestKnown (csv example-operator.v0.1.0): installPlanRef: &v1.ObjectReference{Kind:"InstallPlan", Namespace:"fail-forward-e2e-w6cdz", Name:"install-gcpf4", UID:"e0a9e18b-3acd-4551-8b2c-a2fd84f44f8e", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"2373", FieldPath:""}
  13:56:40.7982: subscription fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9-sub state: UpgradePending (csv example-operator.v0.2.0): installPlanRef: &v1.ObjectReference{Kind:"InstallPlan", Namespace:"fail-forward-e2e-w6cdz", Name:"install-jx7xj", UID:"ae2c98d5-214a-4697-8fc0-2c3be4758933", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"2590", FieldPath:""}
  STEP: waiting for the bad CSV to report a failed state @ 11/06/23 13:56:40.798
  waiting for CSV fail-forward-e2e-w6cdz/example-operator.v0.2.0 to reach condition
  waited 208.0[791](https://github.com/operator-framework/operator-lifecycle-manager/actions/runs/6771572912/job/18402234628#step:5:792)72ms for csv fail-forward-e2e-w6cdz/example-operator.v0.2.0 - Failed (InstallComponentFailed): install strategy failed: Deployment.apps "example-operator-controller-manager&invalid" is invalid: metadata.name: Invalid value: "example-operator-controller-manager&invalid": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
  waited 8m43.288344407s for CSV fail-forward-e2e-w6cdz/example-operator.v0.2.0: to be in phases [Failed], in phase Failed (InstallComponentFailed): install strategy failed: Deployment.apps "example-operator-controller-manager&invalid" is invalid: metadata.name: Invalid value: "example-operator-controller-manager&invalid": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
  STEP: patching the catalog with a fixed version @ 11/06/23 13:56:41.006
  STEP: removing the existing catalog source @ 11/06/23 13:56:41.006
  STEP: removing the previous catalog source pod(s) @ 11/06/23 13:56:41.21
  waiting for the catalog source mc-csv-failed-7h6c9-rdgd7 pod to be deleted...
  STEP: updating the catalog with a new bundle images @ 11/06/23 13:56:42.271
  Creating catalog source mc-csv-failed-7h6c9 in namespace fail-forward-e2e-w6cdz...
  Catalog source mc-csv-failed-7h6c9 created
  STEP: waiting for the subscription to have the example-operator.v0.3.0 status.currentCSV @ 11/06/23 13:57:27.845
  13:57:28.046: subscription fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9-sub state: AtLatestKnown (csv example-operator.v0.2.0): installPlanRef: &v1.ObjectReference{Kind:"InstallPlan", Namespace:"fail-forward-e2e-w6cdz", Name:"install-jx7xj", UID:"ae2c98d5-214a-4697-8fc0-2c3be4758933", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"2590", FieldPath:""}
  14:02:28.1992: subscription fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9-sub never got correct status: v1alpha1.SubscriptionStatus{CurrentCSV:"example-operator.v0.2.0", InstalledCSV:"example-operator.v0.2.0", Install:(*v1alpha1.InstallPlanReference)(0xc000033700), State:"AtLatestKnown", Reason:"", InstallPlanGeneration:2, InstallPlanRef:(*v1.ObjectReference)(0xc000913730), CatalogHealth:[]v1alpha1.SubscriptionCatalogHealth{v1alpha1.SubscriptionCatalogHealth{CatalogSourceRef:(*v1.ObjectReference)(0xc000913650), LastUpdated:time.Date(2023, time.November, 6, 13, 56, 44, 0, time.Local), Healthy:true}, v1alpha1.SubscriptionCatalogHealth{CatalogSourceRef:(*v1.ObjectReference)(0xc0009136c0), LastUpdated:time.Date(2023, time.November, 6, 13, 56, 44, 0, time.Local), Healthy:true}}, Conditions:[]v1alpha1.SubscriptionCondition{v1alpha1.SubscriptionCondition{Type:"CatalogSourcesUnhealthy", Status:"False", Reason:"AllCatalogSourcesHealthy", Message:"all available catalogsources are healthy", LastHeartbeatTime:<nil>, LastTransitionTime:time.Date(2023, time.November, 6, 13, 56, 44, 0, time.Local)}, v1alpha1.SubscriptionCondition{Type:"BundleUnpacking", Status:"False", Reason:"", Message:"", LastHeartbeatTime:<nil>, LastTransitionTime:<nil>}, v1alpha1.SubscriptionCondition{Type:"ResolutionFailed", Status:"True", Reason:"ConstraintsNotSatisfiable", Message:"constraints not satisfiable: clusterserviceversion example-operator.v0.1.0 exists and is not referenced by a subscription, @existing/fail-forward-e2e-w6cdz//example-operator.v0.2.0, @existing/fail-forward-e2e-w6cdz//example-operator.v0.1.0 and mc-csv-failed-7h6c9/fail-forward-e2e-w6cdz/stable/example-operator.v0.3.0 originate from package packageA, subscription mc-csv-failed-7h6c9-sub exists, subscription mc-csv-failed-7h6c9-sub requires at least one of mc-csv-failed-7h6c9/fail-forward-e2e-w6cdz/stable/example-operator.v0.3.0 or @existing/fail-forward-e2e-w6cdz//example-operator.v0.2.0", LastHeartbeatTime:<nil>, LastTransitionTime:<nil>}}, LastUpdated:time.Date(2023, time.November, 6, 13, 57, 27, 0, time.Local)}
  14:02:28.1993: subscription fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9-sub spec: &v1alpha1.SubscriptionSpec{CatalogSource:"mc-csv-failed-7h6c9", CatalogSourceNamespace:"fail-forward-e2e-w6cdz", Package:"packageA", Channel:"stable", StartingCSV:"", InstallPlanApproval:"", Config:(*v1alpha1.SubscriptionConfig)(nil)}
  [FAILED] in [It] - /home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/fail_forward_e2e_test.go:399 @ 11/06/23 14:02:28.204
  STEP: removing the testing catalog resources @ 11/06/23 14:02:28.204
  Deleting config map mc-csv-failed-7h6c9-configmap...
  Deleting catalog source mc-csv-failed-7h6c9...
  waiting for the catalog source mc-csv-failed-7h6c9-7mnhz pod to be deleted...
  Deleting config map mc-csv-failed-7h6c9-configmap...
  Deleting catalog source mc-csv-failed-7h6c9...
  Deleting config map mc-csv-failed-7h6c9-configmap...
  Deleting catalog source mc-csv-failed-7h6c9...
  STEP: deleting the testing namespace @ 11/06/23 14:02:29.488
  collecting the fail-forward-e2e-w6cdz namespace artifacts as the 'eventually reports a successful state when using skip ranges' test case failed
  collecting logs in the ./artifacts/ artifacts directory
  tearing down the fail-forward-e2e-w6cdz namespace
  resetting e2e kube client
  deleting fail-forward-e2e-w6cdz/mc-csv-failed-7h6c9-sub
  deleting fail-forward-e2e-w6cdz/fail-forward-e2e-w6cdz-operatorgroup
  deleting <global>/fail-forward-e2e-w6cdz
  garbage collecting CRDs
  << Timeline

  [FAILED] Expected
      <wait.errInterrupted>:
      timed out waiting for the condition
      {
          cause: <*errors.errorString | 0xc0001ae110>{
              s: "timed out waiting for the condition",
          },
      }
  to be nil
  In [It] at: /home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/fail_forward_e2e_test.go:399 @ 11/06/23 14:02:28.204

  Full Stack Trace
    github.com/operator-framework/operator-lifecycle-manager/test/e2e.glob..func14.4.3()
    	/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/fail_forward_e2e_test.go:399 +0x2a3
------------------------------

Took 8 attempts to fail; 12.5% occurrance.

This is likely due to an error updating the subscription, possibly at a critical time. But, I do see similar errors during a success.
This is from the catalog-operator pod:
2023-11-07T19:43:34.379154025Z stderr F time="2023-11-07T19:43:34Z" level=debug msg="resolving subscriptions in namespace" id=TjnDL namespace=fail-forward-e2e-t25w6
2023-11-07T19:43:34.387130717Z stderr F time="2023-11-07T19:43:34Z" level=warning msg="an error was encountered during reconciliation" error="Operation cannot be fulfilled on subscriptions.operators.coreos.com \"mc-csv-failed-qn8mm-sub\": the object has been modified; please apply your changes to the latest version and try again" event=update reconciling="*v1alpha1.Subscription" selflink=
2023-11-07T19:43:34.388610715Z stderr F E1107 19:43:34.388510       1 queueinformer_operator.go:319] sync {"update" "fail-forward-e2e-t25w6/mc-csv-failed-qn8mm-sub"} failed: Operation cannot be fulfilled on subscriptions.operators.coreos.com "mc-csv-failed-qn8mm-sub": the object has been modified; please apply your changes to the latest version and try again
2023-11-07T19:43:34.388813015Z stderr F time="2023-11-07T19:43:34Z" level=info msg=syncing event=update reconciling="*v1alpha1.Subscription" selflink=

From the e2e log:
  19:44:38.6016: subscription fail-forward-e2e-t25w6/mc-csv-failed-qn8mm-sub state: AtLatestKnown (csv example-operator.v0.2.0): installPlanRef: &v1.ObjectReference{Kind:"InstallPlan", Namespace:"fail-forward-e2e-t25w6", Name:"install-kktrz", UID:"0666549d-ad6f-4d65-abd7-2ab374236509", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"1122", FieldPath:""}
  19:49:38.5972: subscription fail-forward-e2e-t25w6/mc-csv-failed-qn8mm-sub never got correct status: v1alpha1.SubscriptionStatus{CurrentCSV:"example-operator.v0.2.0", InstalledCSV:"example-operator.v0.2.0", Install:(*v1alpha1.InstallPlanReference)(0xc000fc3f40), State:"AtLatestKnown", Reason:"", InstallPlanGeneration:2, InstallPlanRef:(*v1.ObjectReference)(0xc0005fc690), CatalogHealth:[]v1alpha1.SubscriptionCatalogHealth{v1alpha1.SubscriptionCatalogHealth{CatalogSourceRef:(*v1.ObjectReference)(0xc0005fc5b0), LastUpdated:time.Date(2023, time.November, 7, 19, 44, 17, 0, time.Local), Healthy:true}, v1alpha1.SubscriptionCatalogHealth{CatalogSourceRef:(*v1.ObjectReference)(0xc0005fc620), LastUpdated:time.Date(2023, time.November, 7, 19, 44, 17, 0, time.Local), Healthy:true}}, Conditions:[]v1alpha1.SubscriptionCondition{v1alpha1.SubscriptionCondition{Type:"CatalogSourcesUnhealthy", Status:"False", Reason:"AllCatalogSourcesHealthy", Message:"all available catalogsources are healthy", LastHeartbeatTime:<nil>, LastTransitionTime:time.Date(2023, time.November, 7, 19, 44, 17, 0, time.Local)}, v1alpha1.SubscriptionCondition{Type:"BundleUnpacking", Status:"False", Reason:"", Message:"", LastHeartbeatTime:<nil>, LastTransitionTime:<nil>}, v1alpha1.SubscriptionCondition{Type:"ResolutionFailed", Status:"True", Reason:"ConstraintsNotSatisfiable", Message:"constraints not satisfiable: clusterserviceversion example-operator.v0.1.0 exists and is not referenced by a subscription, @existing/fail-forward-e2e-t25w6//example-operator.v0.2.0, @existing/fail-forward-e2e-t25w6//example-operator.v0.1.0 and mc-csv-failed-qn8mm/fail-forward-e2e-t25w6/stable/example-operator.v0.3.0 originate from package packageA, subscription mc-csv-failed-qn8mm-sub exists, subscription mc-csv-failed-qn8mm-sub requires at least one of mc-csv-failed-qn8mm/fail-forward-e2e-t25w6/stable/example-operator.v0.3.0 or @existing/fail-forward-e2e-t25w6//example-operator.v0.2.0", LastHeartbeatTime:<nil>, LastTransitionTime:<nil>}}, LastUpdated:time.Date(2023, time.November, 7, 19, 44, 38, 0, time.Local)}

 Fail Forward Upgrades when a CSV resource is in a failed state eventually reports a successful state when using skips
/go/src/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/fail_forward_e2e_test.go:402
  STEP: creating the testing namespace with an OG that enabled fail forward behavior @ 11/14/23 02:22:51.908
  created the fail-forward-e2e-hm8m2 testing namespace
  STEP: deploying the testing catalog @ 11/14/23 02:22:51.999
  Creating catalog source mc-csv-failed-b47k7 in namespace fail-forward-e2e-hm8m2...
  Catalog source mc-csv-failed-b47k7 created
waiting 148.179373ms for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - NO_CONNECTION
waiting 590.956103ms for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - IDLE
waiting 200.019269ms for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - TRANSIENT_FAILURE
waiting 602.234668ms for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - CONNECTING
waiting 197.393456ms for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - TRANSIENT_FAILURE
waiting 15.656604807s for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - READY
probing catalog mc-csv-failed-b47k7 pod with address mc-csv-failed-b47k7.fail-forward-e2e-hm8m2.svc:50051
skipping health check
  STEP: creating the testing subscription @ 11/14/23 02:23:09.484
  STEP: waiting until the subscription has an IP reference @ 11/14/23 02:23:09.526
  02:23:10.8861: subscription fail-forward-e2e-hm8m2/mc-csv-failed-b47k7-sub state: UpgradePending (csv example-operator.v0.1.0): installPlanRef: &v1.ObjectReference{Kind:"InstallPlan", Namespace:"fail-forward-e2e-hm8m2", Name:"install-sl4wl", UID:"1df970d6-3803-406d-8dc4-214c36af1b22", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"128538", FieldPath:""}
  waiting 1.359020737s for subscription fail-forward-e2e-hm8m2/mc-csv-failed-b47k7-sub to have installplan ref: has ref &v1.ObjectReference{Kind:"InstallPlan", Namespace:"fail-forward-e2e-hm8m2", Name:"install-sl4wl", UID:"1df970d6-3803-406d-8dc4-214c36af1b22", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"128538", FieldPath:""}
  STEP: waiting for the v0.1.0 CSV to report a succeeded phase @ 11/14/23 02:23:10.886
  waiting for CSV fail-forward-e2e-hm8m2/example-operator.v0.1.0 to reach condition
  waited 199.608397ms for csv fail-forward-e2e-hm8m2/example-operator.v0.1.0 - Installing (InstallWaiting): installing: waiting for deployment example-operator-controller-manager to become ready: deployment "example-operator-controller-manager" not available: Deployment does not have minimum availability.
  waited 199.697425ms for CSV fail-forward-e2e-hm8m2/example-operator.v0.1.0: to be in phases [Succeeded], in phase Installing (InstallWaiting): installing: waiting for deployment example-operator-controller-manager to become ready: deployment "example-operator-controller-manager" not available: Deployment does not have minimum availability.
  waited 1.601659075s for csv fail-forward-e2e-hm8m2/example-operator.v0.1.0 - Succeeded (InstallSucceeded): install strategy completed with no errors
  waited 1.601733023s for CSV fail-forward-e2e-hm8m2/example-operator.v0.1.0: to be in phases [Succeeded], in phase Succeeded (InstallSucceeded): install strategy completed with no errors
  STEP: updating the catalog with a broken v0.2.0 csv @ 11/14/23 02:23:12.688
  STEP: removing the existing catalog source @ 11/14/23 02:23:12.688
  STEP: removing the previous catalog source pod(s) @ 11/14/23 02:23:12.892
  waiting for the catalog source mc-csv-failed-b47k7-8ckq6 pod to be deleted...
  STEP: updating the catalog with a new bundle images @ 11/14/23 02:23:13.976
  Creating catalog source mc-csv-failed-b47k7 in namespace fail-forward-e2e-hm8m2...
  Catalog source mc-csv-failed-b47k7 created
waiting 138.410284ms for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - NO_CONNECTION
waiting 2.26910633s for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - TRANSIENT_FAILURE
waiting 2.598714655s for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - CONNECTING
waiting 200.99772ms for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - TRANSIENT_FAILURE
waiting 12.400568791s for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - CONNECTING
waiting 199.285203ms for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - READY
probing catalog mc-csv-failed-b47k7 pod with address mc-csv-failed-b47k7.fail-forward-e2e-hm8m2.svc:50051
skipping health check
  STEP: verifying the subscription has installed the current csv @ 11/14/23 02:23:31.885
  02:23:32.0872: subscription fail-forward-e2e-hm8m2/mc-csv-failed-b47k7-sub state: AtLatestKnown (csv example-operator.v0.1.0): installPlanRef: &v1.ObjectReference{Kind:"InstallPlan", Namespace:"fail-forward-e2e-hm8m2", Name:"install-sl4wl", UID:"1df970d6-3803-406d-8dc4-214c36af1b22", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"128538", FieldPath:""}
  02:23:32.2868: subscription fail-forward-e2e-hm8m2/mc-csv-failed-b47k7-sub state: UpgradePending (csv example-operator.v0.2.0): installPlanRef: &v1.ObjectReference{Kind:"InstallPlan", Namespace:"fail-forward-e2e-hm8m2", Name:"install-m4jh9", UID:"4d3d9467-23cd-4055-884c-34ffc0c08b28", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"128987", FieldPath:""}
  STEP: waiting for the bad CSV to report a failed state @ 11/14/23 02:23:32.286
  waiting for CSV fail-forward-e2e-hm8m2/example-operator.v0.2.0 to reach condition
  waited 207.233924ms for csv fail-forward-e2e-hm8m2/example-operator.v0.2.0 - Pending (RequirementsUnknown): requirements not yet checked
  waited 1m12.23119933s for CSV fail-forward-e2e-hm8m2/example-operator.v0.2.0: to be in phases [Failed], in phase Pending (RequirementsUnknown): requirements not yet checked
  waited 593.392252ms for csv fail-forward-e2e-hm8m2/example-operator.v0.2.0 - InstallReady (AllRequirementsMet): all requirements found, attempting install
  waited 593.428936ms for CSV fail-forward-e2e-hm8m2/example-operator.v0.2.0: to be in phases [Failed], in phase InstallReady (AllRequirementsMet): all requirements found, attempting install
  waited 398.113032ms for csv fail-forward-e2e-hm8m2/example-operator.v0.2.0 - Failed (InstallComponentFailed): install strategy failed: Deployment.apps "example-operator-controller-manager&invalid" is invalid: metadata.name: Invalid value: "example-operator-controller-manager&invalid": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
  waited 398.154075ms for CSV fail-forward-e2e-hm8m2/example-operator.v0.2.0: to be in phases [Failed], in phase Failed (InstallComponentFailed): install strategy failed: Deployment.apps "example-operator-controller-manager&invalid" is invalid: metadata.name: Invalid value: "example-operator-controller-manager&invalid": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
  STEP: patching the catalog with a fixed version @ 11/14/23 02:23:33.486
  STEP: removing the existing catalog source @ 11/14/23 02:23:33.486
  STEP: removing the previous catalog source pod(s) @ 11/14/23 02:23:33.698
  waiting for the catalog source mc-csv-failed-b47k7-297mr pod to be deleted...
  STEP: updating the catalog with a new bundle images @ 11/14/23 02:23:34.793
  Creating catalog source mc-csv-failed-b47k7 in namespace fail-forward-e2e-hm8m2...
  Catalog source mc-csv-failed-b47k7 created
waiting 138.763895ms for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - NO_CONNECTION
waiting 4.050054318s for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - CONNECTING
waiting 19.996456256s for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - TRANSIENT_FAILURE
waiting 1.000994366s for catalog pod fail-forward-e2e-hm8m2/mc-csv-failed-b47k7 to be available (for sync) - READY
probing catalog mc-csv-failed-b47k7 pod with address mc-csv-failed-b47k7.fail-forward-e2e-hm8m2.svc:50051
skipping health check
  STEP: waiting for the subscription to have the example-operator.v0.3.0 status.currentCSV @ 11/14/23 02:24:00.085
  02:24:00.2865: subscription fail-forward-e2e-hm8m2/mc-csv-failed-b47k7-sub state: AtLatestKnown (csv example-operator.v0.2.0): installPlanRef: &v1.ObjectReference{Kind:"InstallPlan", Namespace:"fail-forward-e2e-hm8m2", Name:"install-m4jh9", UID:"4d3d9467-23cd-4055-884c-34ffc0c08b28", APIVersion:"operators.coreos.com/v1alpha1", ResourceVersion:"128987", FieldPath:""}
  02:29:00.4869: subscription fail-forward-e2e-hm8m2/mc-csv-failed-b47k7-sub never got correct status: v1alpha1.SubscriptionStatus{CurrentCSV:"example-operator.v0.2.0", InstalledCSV:"example-operator.v0.2.0", Install:(*v1alpha1.InstallPlanReference)(0xc001b13e40), State:"AtLatestKnown", Reason:"", InstallPlanGeneration:2, InstallPlanRef:(*v1.ObjectReference)(0xc00087ec40), CatalogHealth:[]v1alpha1.SubscriptionCatalogHealth{v1alpha1.SubscriptionCatalogHealth{CatalogSourceRef:(*v1.ObjectReference)(0xc00087e930), LastUpdated:time.Date(2023, time.November, 14, 2, 23, 41, 0, time.Local), Healthy:true}, v1alpha1.SubscriptionCatalogHealth{CatalogSourceRef:(*v1.ObjectReference)(0xc00087e9a0), LastUpdated:time.Date(2023, time.November, 14, 2, 23, 41, 0, time.Local), Healthy:true}, v1alpha1.SubscriptionCatalogHealth{CatalogSourceRef:(*v1.ObjectReference)(0xc00087ea80), LastUpdated:time.Date(2023, time.November, 14, 2, 23, 41, 0, time.Local), Healthy:true}, v1alpha1.SubscriptionCatalogHealth{CatalogSourceRef:(*v1.ObjectReference)(0xc00087eaf0), LastUpdated:time.Date(2023, time.November, 14, 2, 23, 41, 0, time.Local), Healthy:true}, v1alpha1.SubscriptionCatalogHealth{CatalogSourceRef:(*v1.ObjectReference)(0xc00087eb60), LastUpdated:time.Date(2023, time.November, 14, 2, 23, 41, 0, time.Local), Healthy:true}}, Conditions:[]v1alpha1.SubscriptionCondition{v1alpha1.SubscriptionCondition{Type:"CatalogSourcesUnhealthy", Status:"False", Reason:"AllCatalogSourcesHealthy", Message:"all available catalogsources are healthy", LastHeartbeatTime:<nil>, LastTransitionTime:time.Date(2023, time.November, 14, 2, 23, 41, 0, time.Local)}, v1alpha1.SubscriptionCondition{Type:"BundleUnpacking", Status:"False", Reason:"", Message:"", LastHeartbeatTime:<nil>, LastTransitionTime:<nil>}, v1alpha1.SubscriptionCondition{Type:"ResolutionFailed", Status:"True", Reason:"ConstraintsNotSatisfiable", Message:"constraints not satisfiable: @existing/fail-forward-e2e-hm8m2//example-operator.v0.2.0, @existing/fail-forward-e2e-hm8m2//example-operator.v0.1.0 and mc-csv-failed-b47k7/fail-forward-e2e-hm8m2/stable/example-operator.v0.3.0 originate from package packageA, clusterserviceversion example-operator.v0.1.0 exists and is not referenced by a subscription, subscription mc-csv-failed-b47k7-sub exists, subscription mc-csv-failed-b47k7-sub requires at least one of mc-csv-failed-b47k7/fail-forward-e2e-hm8m2/stable/example-operator.v0.3.0 or @existing/fail-forward-e2e-hm8m2//example-operator.v0.2.0", LastHeartbeatTime:<nil>, LastTransitionTime:<nil>}}, LastUpdated:time.Date(2023, time.November, 14, 2, 28, 34, 0, time.Local)}
  02:29:00.4871: subscription fail-forward-e2e-hm8m2/mc-csv-failed-b47k7-sub spec: &v1alpha1.SubscriptionSpec{CatalogSource:"mc-csv-failed-b47k7", CatalogSourceNamespace:"fail-forward-e2e-hm8m2", Package:"packageA", Channel:"stable", StartingCSV:"", InstallPlanApproval:"", Config:(*v1alpha1.SubscriptionConfig)(nil)}
  [FAILED] in [It] - /go/src/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/fail_forward_e2e_test.go:412 @ 11/14/23 02:29:00.488
  STEP: removing the testing catalog resources @ 11/14/23 02:29:00.489
  Deleting config map mc-csv-failed-mkq2q-configmap...
  Deleting catalog source mc-csv-failed-mkq2q...
  Deleting config map mc-csv-failed-mkq2q-configmap...
  Deleting catalog source mc-csv-failed-mkq2q...
  Deleting config map mc-csv-failed-mkq2q-configmap...
  Deleting catalog source mc-csv-failed-mkq2q...
  Deleting config map mc-csv-failed-b47k7-configmap...
  Deleting catalog source mc-csv-failed-b47k7...
  waiting for the catalog source mc-csv-failed-b47k7-29zm8 pod to be deleted...
  Deleting config map mc-csv-failed-b47k7-configmap...
  Deleting catalog source mc-csv-failed-b47k7...
  Deleting config map mc-csv-failed-b47k7-configmap...
  Deleting catalog source mc-csv-failed-b47k7...
  STEP: deleting the testing namespace @ 11/14/23 02:29:02.588
  collecting the fail-forward-e2e-hm8m2 namespace artifacts as the 'eventually reports a successful state when using skips' test case failed
  collecting logs in the /logs/artifacts artifacts directory
  unable to determine kubeconfig path so defaulting to the $KUBECONFIG value
Using the oc kubectl binary
Using the /logs/artifacts/fail-forward-e2e-hm8m2 output directory
Storing the test artifact output in the /logs/artifacts/fail-forward-e2e-hm8m2 directory
Collecting get catalogsources -o yaml output...
Collecting get subscriptions -o yaml output...
Collecting get operatorgroups -o yaml output...
Collecting get clusterserviceversions -o yaml output...
Collecting get installplans -o yaml output...
Collecting get pods -o wide output...
Collecting get events --sort-by .lastTimestamp output...
  tearing down the fail-forward-e2e-hm8m2 namespace
  resetting e2e kube client
  deleting fail-forward-e2e-hm8m2/mc-csv-failed-b47k7-sub
  deleting fail-forward-e2e-hm8m2/fail-forward-e2e-hm8m2-operatorgroup
  deleting <global>/fail-forward-e2e-hm8m2
  garbage collecting CRDs
• [FAILED] [375.072 seconds]
Fail Forward Upgrades when a CSV resource is in a failed state [It] eventually reports a successful state when using skips
/go/src/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/fail_forward_e2e_test.go:402
  [FAILED] Expected
      <wait.errInterrupted>:
      timed out waiting for the condition
      {
          cause: <*errors.errorString | 0xc000250190>{
              s: "timed out waiting for the condition",
          },
      }
  to be nil
  In [It] at: /go/src/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/fail_forward_e2e_test.go:412 @ 11/14/23 02:29:00.488

likely similar culprit in different test


Improve logging of Function Timeouts

Currently a function which times out is not treated as a success or failure, we should emit an event to track these failures

@mamaso Can you clarify, is this about how the execution of the function is represented in our storage based logging and how it appears to the user on the monitoring tab? Or is this about our internal telemetry?

I believe both.
Currently the core sdk logs that there is a function failure when there is a timeout.  However, at the script host level this is untracked, i.e. there is no 'Function completed (Failure/Timeout ...)' event.
I can show you in FunctionsLogs if you like, @christopheranderson also had a viz which showed the issue.

OK so for every timeout I think we want two things:

FunctionsLog entry indicating the execution timed out
FunctionsMetrics timeout entry

Sounds good?

Yep, sounds good!

@mamaso Well @fabiocav and @mathewc think there should be an entry in FunctionsLog... you don't see it?

@mamaso - poke

Ah, missed some clarification here, we have the FunctionsLog entry, but we don't have a FunctionsMetrics timeout entry


Array Type Inference

TypeScript Version:  3.3.0-dev.20181222

Search Terms:

array
type
inference
index

Code
Playground Link
const typed = ['a', 1] as [string, number];
typed[0].length; // Works
typed[1].toPrecision; // Works
typed[2]; // Errors as expected

const array = ['a', 1];
array[0].length; // Error
array[1].toPrecision; // Error
array[2]; // Should error

Expected behavior:
TypeScript infers type of array as [string, number].
Actual behavior:
TypeScript infers type of array as (string | number)[].
Related Issues:
#25516

Known issue - array literals are inferred as a union of their member types.  I don't think it's considered a bug.

I see. I looked through the FAQ pages of other bugs and did not find exactly equivalent.
I'll let them close this if this is desired behavior.
I'm curious what reasons there are for this not being the desired behavior!

It's been discussed on the TypeScript gitter several times in the past, and I was pretty sure there was a GitHub issue that described the design challenges at length, but I can't find it now...
See also #27179, #16656.


NativeDatepicker with MAT_DATE_LOCALE and en-GB swaps day/month continuously

Reproduction
Use StackBlitz to reproduce your issue: https://stackblitz.com/edit/angular-a5a7jk?file=src%2Fapp%2Fdatepicker-overview-example.html
Steps to reproduce:

Add { provide: MAT_DATE_LOCALE, useValue: 'en-GB' },
Focus field and type: "01/12/1988" and blur field
Focus field and press: "backspace" and "8" and blur field

The same thing happens with locales like "de-DE"
Expected Behavior
What behavior were you expecting to see?
You should see "01/12/1988" as you blur the field. When you edit that field with the same value, it should stay as "01/12/1988"
Actual Behavior
What behavior did you actually see?
"01/12/1988" becomes "12/01/1988" and editing it again changes it back and forth to "01/12/1988"
Environment

Angular: 8.2.3
CDK/Material: 8.2.3
Browser(s): OSX Chrome
OS Locale: United Kingdom
navigator.language: "en"

Temporary workaround
Just set the locale to something like "en".
Potentially related: https://github.com/angular/components/issues/7823 and https://github.com/angular/components/issues/7143
After a little bit of debugging I see that: new Date("12/01/1988") is regarded as 1st December (en-US) as opposed to 12th January (en-GB) and then it's formatted using en-GB (opposite)

As you mentioned, by default the datepicker just passes the value straight into the Date constructor and relies on the browser to do the parsing. If you want more control over how it's done, you can provide your own date adapter or use the provided Moment.js one.

This is a limitation of the native Date object in JavaScript.
Currently I recommend using the MomentDateAdapter or another custom date adapter rather than the standard NativeDateAdapter (see https://material.angular.io/components/datepicker/overview#choosing-a-date-implementation-and-date-format-settings)
We should however, try to make a better experience for the NativeDateAdapter.
This issue is being tracked by https://github.com/angular/components/issues/8100


Using RecyclerView inside ParallaxScrollView

Hello,
is it possible to have a RecyclerView inside ParallaxScrollView or do I need to use something else?
rgds Schabi

Hi, try https://github.com/kanytu/android-parallax-recyclerview


How to access to websocket clients from http controller?

Hello everyone,
I have a chat on websocket and i need to push some message entered from http api to everyone from websocket.
i.e. I need to call socket.toEveryone().emit('message', 'From API') (/app/Ws/Controllers/ChatController.js) from /app/Http/Controllers/ApiController.js

Simply grab the chat channel and call the emit message on it. Reference to docs http://adonisjs.com/docs/3.2/websocket#_emit_event_properties_2
Example
const Ws = use('Ws')

// In your controller method
Ws.channel('chat'). emit('message', 'From API')

@thetutlage wow, nice, thank you!
If not difficult, answer a few more questions for me :P

how best to create a static class to store some variables and create a couple of timers in this class

I need to implement Steam Bot in the same nodejs project which is a website and sockets, how to do it better (to have access to sockets and other classes, for example, static class in first question)?

Those are more of general programming questions. I would suggest to have a chat in the gitter room https://gitter.im/adonisjs/adonis-framework.


prisma-1 client to use http proxy to work behind corporate firewalls

Describe the bug
Using "BatchedGraphQLClient" via "prisma-client-lib" does not allow configuring http(s) proxy. This means if the prisma server is running outside the corporate network, the prisma client will not be able to reach it. causing the following error:
FetchError: request to https://us1.prisma.sh/harleen-mann-2fba2c/hackernews-node/dev failed, reason: connect ECONNREFUSED <IP_ADDRESS>:443
    at ClientRequest.<anonymous> (C:\Users\MannH\visualStudioProjects\hackernews-node\node_modules\node-fetch\lib\index.js:1393:11)
    at ClientRequest.emit (events.js:193:13)
    at TLSSocket.socketErrorListener (_http_client.js:397:9)
    at TLSSocket.emit (events.js:193:13)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at processTicksAndRejections (internal/process/task_queues.js:81:17)

To Reproduce
Steps to reproduce the behavior:

Configure "javascript-client" to run behind a corporate proxy
Host the prisma server outside the network. e.g: on app.prisma.io
Start the graph server that talks to prisma server via this prisma client
See error

Expected behavior
The prisma client should be able to use the HTTP_PROXY etc. env variables via an http agent to go via proxy and reach the prisma server
Versions (please complete the following information):

Prisma Server: app.prisma.io
others:

graphql-yoga": "^1.18.3",
"prisma": "^1.34.10",
"prisma-client-lib": "^1.34.10"

OS: Windows 8

My hardcoded solution that worked
I could solve the error by setting the follwing in ...node_modules\prisma-client-lib\dist\Client.js
this._client = new http_link_dataloader_1.BatchedGraphQLClient(endpoint, {
            headers: token
                ? {
                    Authorization: "Bearer " + token,
                }
                : {},
            agent: process.env.https_proxy
            ? new HttpsProxyAgent(process.env.https_proxy ) // 'http://a:a@xxxxx:8080')
            : null
        });

Permanent solution
I am happy to work on a legit solution (rather than hardcoding it) and submit a PR.
Are the maintainers keen on adding this support?

@nikolasburk @mavilein @do4gr @timsuchanek  - should I spend time to fix this and submit a PR?
(since v1 is in maintenance mode)

Hey @mannharleen 👋 apologies for the delay! Unfortunately, we don't work on Prisma 1 any more (this includes merging PRs) unless it's about fixing super critical issues, so we won't be able to spend time reviewing a PR for this 😞

Thanks for your reply. no worries


don't generate a self-signed certificate by default

This clearly doesn't belong a general purpose TLS implementation.

This commit broke not only Minq but also broke the auto-generating functions in the server programs.
What needed to happen here was that newSelfSigned became a public API that other programs could use, no that it was made unavailable and moved into tests.

Here, for instance, is what main.go does:
2018/02/18 14:54:43 server: listen: tls: neither Certificates nor GetCertificate set in Config
exit status 1
14:54:43|~/dev/go/src/github.com/bifurcation/mint (master)$


[ts-sdk] Move Base58 encoding to BCS

Current dependencies on/for this PR:

main

PR #8486   👈

This comment was auto-generated by Graphite.


how to emit like a node client

I use a node client   ,code like this
socket.emit('subscribe', {
         channel: 'foobar',
})

but when my workmate use this client to emit subscribe，he can't let second param has a key channel. how to trans this code to .net

my workmate do it like this,  it works
var mess = new JObject();
mess.Add("channel", "foobar");

socket.Emit("subscribe", mess);

@liyu001989 your connection remain open?


EgorBot for EgorBo in #9

Processing https://github.com/EgorBot/runtime-utils/issues/9#issuecomment-2323505723:

-arm64 -perf -pr 107218
using System;
using System.Runtime.CompilerServices;
using BenchmarkDotNet.Attributes;
using BenchmarkDotNet.Running;

BenchmarkRunner.Run<Bench>(args: args);

public class Bench
{
    [Benchmark]
    public void Foo()
    {
        for (int i = 0; i < 1000; i++)
            Work<char>(1);
    }

    [MethodImpl(MethodImplOptions.NoInlining)]
    static void Work<T>(int size) => GC.KeepAlive(GC.AllocateUninitializedArray<T>(size));
}

Benchmark results on Arm64
BenchmarkDotNet v0.14.0, Ubuntu 22.04.4 LTS (Jammy Jellyfish)
Unknown processor
  Job-IPEEBJ : .NET 10.0.0 (<IP_ADDRESS>424), Arm64 RyuJIT AdvSIMD
  Job-FWPWAC : .NET 10.0.0 (<IP_ADDRESS>424), Arm64 RyuJIT AdvSIMD

Method
Toolchain
Mean
Error
Ratio

Foo
Main
9.682 μs
0.1901 μs
1.00

Foo
PR
16.392 μs
0.0682 μs
1.69

BDN_Artifacts.zip
🔥 Flame graphs: Main vs PR
Hot asm: Main vs PR
Hot functions: Main vs PR
For clean perf results, make sure you have just one [Benchmark] in your app.