text:
Add placement permissin for acm foundation

Description
In 2.10, the ocm-controller components will create a global placement to select all managed clusters in the open-cluster-management-global-set ns, this PR will grant the ocm-controller permission to managed this placement.
Related Issue
If applicable, please reference the issue(s) that this pull request addresses.
https://github.com/stolostron/multicloud-operators-foundation/pull/707
Changes Made
Add get, list, watch, create placement permission for the ocm-controller
Screenshots (if applicable)
Add screenshots or GIFs that demonstrate the changes visually, if relevant.
Checklist

[ ] I have tested the changes locally and they are functioning as expected.
[ ] I have updated the documentation (if necessary) to reflect the changes.
[ ] I have added/updated relevant unit tests (if applicable).
[ ] I have ensured that my code follows the project's coding standards.
[ ] I have checked for any potential security issues and addressed them.
[ ] I have added necessary comments to the code, especially in complex or unclear sections.
[ ] I have rebased my branch on top of the latest main/master branch.

Additional Notes
Add any additional notes, context, or information that might be helpful for reviewers.
Reviewers
Tag the appropriate reviewers who should review this pull request. To add reviewers, please add the following line: /cc @reviewer1 @reviewer2
Definition of Done

[ ] Code is reviewed.
[ ] Code is tested.
[ ] Documentation is updated.
[ ] All checks and tests pass.
[ ] Approved by at least one reviewer.
[ ] Merged into the main/master branch.

@dislbenn please take a review, we need this to manage a global placement by the ocm-controller

/lgtm

repo: stolostron/backplane-operator


text:
Revert "[release-2.4] maintain the cluster name label by import controller"

Reverts stolostron/clusterclaims-controller#28
Signed-off-by: Wei Liu liuweixa@redhat.com

Signed-off-by: Wei Liu liuweixa@redhat.com

source: gharchive/pull-request

repo: stolostron/clusterclaims-controller

license_type: permissive

license_source: github-api


text:
Implement attach for hive cluster

For the time being the attach only accept,
manual attach, with kubeconfig or server/token.
If it is a hive cluster created, no need for the kubeconfig or server/token.

Now the import-managed-operator support that,

source: gharchive/issue

repo: stolostron/cm-cli


text:
ACM-2869

Signed-off-by: Maggie Chen magchen@redhat.com
https://issues.redhat.com/browse/ACM-2869

@jeswanke the fourth files doesn't look right to me... will take a look tomorrow

/retest

/retest

/hold

/unhold

/lgtm

repo: stolostron/console


text:
[release-2.6] Code coverage increase

Signed-off-by: dislbenn dbennett@redhat.com

/test test-e2e

authors: dislbenn subbarao-meduri


text:
Add-support-for-the-metadataComplianceType-field

https://github.com/stolostron/backlog/issues/19517
Signed-off-by: Chunxi Luo chuluo@redhat.com

@mprahl  So two updates: 1) add metadataComplianceType under policyDefault, 2) only add non empty metadataComplianceType into objTemplate, updated all test cases for these

repo: stolostron/policy-generator-plugin


text:
Kill jQuery

If you know of any other places where jQuery is used, please let me know. I ran through the basic section and did not detect any problems.
@wilzbach

This would drop support for IE 8, a browser that released seven years ago.

This would drop support for IE 8, a browser that released seven years ago.

No worries, angular doesn't support that either.
For dlang.org @CyberShadow and I agreed that only supporting IE 11 is quite reasonable - after all the total share of IE users is less than 0.5% for dlang.org :)

If you know of any other places where jQuery is used, please let me know. I ran through the basic section and did not detect any problems.

Nope - we are all good :)
Thanks a lot!

authors: JackStouffer wilzbach

repo: stonemaster/dlang-tour


text:
New predatory Journal:  Insight - Automatic Control highlights

I have been invited and, initially accepted the invitation of a new predatory Journal. Later I found, however, that this journal practices predatory publishing :
Insight - Automatic Control highlights
http://insight.piscomed.com/index.php/IAC
This journal is part of a larger system of "scientific" journals index:
http://ojs.piscomed.com/
In this index, there are dozens of electronic "open access" journals. All of them are fake.

I will make a pull request

Sent as an update in journals.csv

license: mit

license_source: bigquery


text:
fix: allow to display the code samples when try it panel is hidden

Changes

Modified the rendering logic of the TryIt component to ensure it generates request data regardless of the TryIt panel's visibility.
Ensured that the request sample is consistently displayed on the page by decoupling the request data generation from the TryIt panel's display state.

Rationale
Previously, the request sample could not be displayed without rendering the TryIt panel, which was a limitation. This change allows the request sample by not visually rendering the TryIt Panel when its opted out off.
Testing

Verified that the request sample is correctly displayed when the TryIt panel is hidden.
Ensured no regressions in the display of the TryIt panel and its functionality.

Elements Default PR Template
In general, make sure you have: (check the boxes to acknowledge you've followed this template)

[X] Read CONTRIBUTING.md

Other Available PR Templates:

Release: https://github.com/stoplightio/elements/compare?template=release.md

[ ] Read the release section of CONTRIBUTING.md

LGTM!

@weyert Can we also update the docs please

Yeah, I will do. Probably tomorrow.

Totally forgot about it @mnaumanali94 I have added the call out in the documentation now.

repo: stoplightio/elements


text:
allow for empty request bodies to skip validation, fixes #1939

Addresses #1939
Summary
inspects the request content-length header for making the decision to enforce the content-type on the request. if it is >1 then the content-type header must be one of the request body types.
Checklist

The basics

[x] I tested these changes manually in my local or dev environment

Tests

[x] Added or updated
[ ] N/A

Event Tracking

[ ] I added event tracking and followed the event tracking guidelines
[x] N/A

Error Reporting

[ ] I reported errors and followed the error reporting guidelines
[x] N/A

thanks for the fix. Could it be that with this an empty PSOT request body doesn't trigger exception when a body payload is required? In my case I somehow can't get an exception triggered on missing body...!?
I quick drafted a potential test case here:
====test====
Given a request declaring a content-type but has no body although it is required
then return 400
====spec====
openapi: '3.1.0'
paths:
  /path:
    post:
      requestBody:
        content:
          application/json:
            schema:
              type: object
              required:
                - foo
               properties:
                 foo:
                   type: string
      responses:
        200:
          content:
            text/plain:
              example: ok
       400:
          content:
            text/plain:
              example: body required
====server====
mock -p 4010 ${document}
====command====
curl -i -X POST http://localhost:4010/path -H "Content-Type: application/json"
====expect====
HTTP/1.1 400 Bad Request
content-type: text/plain

body required

authors: daniel-white rngtng

repo: stoplightio/prism


text:
[Bug]

Describe the bug
nycrcPath does not seem to be working.
A clear and concise description of what the bug is.
I am trying to use nyc.config.js but setting this in nycrcPath doesnt do anything.
Steps to reproduce the behavior

add addons to  /.storybook/main.ts
{
name: "@storybook/addon-coverage",
options: {
istanbul: {
nycrcPath: './../nyc.config.sb.js',
},
},
},

create nyc.config.sb.js at /nyc.config.sb.js

add lines to nyc.config.sb.js
'use strict';
module.exports = {
"tempDirectory": './.nyc_customout'
};

Run storybook test runner

Expected behavior
expected the temporary directory to use .nyc_customout temp directory during test runner but .nyc_out is being used which is the default temporary directory
Screenshots and/or logs
If applicable, add screenshots and/or logs to help explain your problem.
Environment

OS: iOS
Node.js version: v18.16.1
NPM version: 9.5.1
Browser (if applicable): [e.g. chrome, safari]
Browser version (if applicable): [e.g. 22]
Device (if applicable): [e.g. iPhone6]

Additional context
Add any other context about the problem here.

Does your project use Vite or Webpack?

repo: storybookjs/addon-coverage

license: MIT


text:
Add carbon to examples page

What I did
Added Carbon Design System to list of example pages
How to test
Check example page
Thanks to @ndelangen for the suggestion. Let me know if any changes need to be made 👍

Tested

I'll publish it when i get home

Thanks!

repo: storybooks/storybook


text:
add a11y link to gallery

Issue:
What I did
I added a
How to test
This is only an update to the documentation

Thank you @cortopy !

authors: cortopy ndelangen


text:
fixed expected MASK output behaviour for GroundingDinoSAMSegment Node

should fix https://github.com/storyicon/comfyui_segment_anything/issues/7

LGTM, thank you for your contribution.


text:
CICD pushes new docker images packages on new tags

On tags, create a new docker image release through CICD.
0ver or Semver?

Closing. This has been completed.

repo: strangelove-ventures/cosmos-operator


text:
Missing Transport Client Dependencies

When attempting to use the Shaded Elasticsearch Transport client provided by the following dependency:
<dependency>
    <groupId>com.strapdata.elasticsearch.client</groupId>
    <artifactId>transport</artifactId>
    <version>5.5.0</version>
</dependency>

You encounter the following when trying to perform a mvn clean package:
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building elassaandra-bug 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for com.strapdata.elasticsearch.plugin:transport-netty3-client:jar:5.5.0 is missing, no dependency information available
[WARNING] The POM for com.strapdata.elasticsearch.plugin:transport-netty4-client:jar:5.5.0 is missing, no dependency information available
[WARNING] The POM for com.strapdata.elasticsearch.plugin:reindex-client:jar:5.5.0 is missing, no dependency information available
[WARNING] The POM for com.strapdata.elasticsearch.plugin:lang-mustache-client:jar:5.5.0 is missing, no dependency information available
[WARNING] The POM for com.strapdata.elasticsearch.plugin:percolator-client:jar:5.5.0 is missing, no dependency information available
[WARNING] The POM for com.strapdata.elasticsearch.plugin:parent-join-client:jar:5.5.0 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.599 s
[INFO] Finished at: 2018-05-10T10:35:11+01:00
[INFO] Final Memory: 14M/479M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project elassaandra-bug: Could not resolve dependencies for project com.example.elassandra:elassaandra-bug:jar:1.0-SNAPSHOT: The following artifacts could not be resolved: com.strapdata.elasticsearch.plugin:transport-netty3-client:jar:5.5.0, com.strapdata.elasticsearch.plugin:transport-netty4-client:jar:5.5.0, com.strapdata.elasticsearch.plugin:reindex-client:jar:5.5.0, com.strapdata.elasticsearch.plugin:lang-mustache-client:jar:5.5.0, com.strapdata.elasticsearch.plugin:percolator-client:jar:5.5.0, com.strapdata.elasticsearch.plugin:parent-join-client:jar:5.5.0: Failure to find com.strapdata.elasticsearch.plugin:transport-netty3-client:jar:5.5.0 in http://nexus.technotomy.com/content/groups/allrepos was cached in the local repository, resolution will not be reattempted until the update interval of home has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

Upon inspection it appears that the following compile dependencies are not included in the central maven repository:

Is this intentional?
If you want to perform operations using the Elasticsearch transport client on Elassandra which client library should you be using? The shaded one or the original from Elasticsearch? Or should we be excluding those dependencies and be using original Elasticaearch versions?
There isn't any mention of how to use a Transport client outside of the Enterprise section within the documentation, which mentions a secured Transport client being provided by Strapdata, with the class of com.strapdata.elasticsearch.plugins.ssl.PreBuiltSslTransportClient. The client provided by the shaded transport client dependency matches Elasticsearch's original org.elasticsearch.client.transport.TransportClient.
Previously when using the Transport client I have run into issues to do with binary incompatibilities between server and client when minor/patch versions differed (admittedly this was with the Elasticsearch 2.X.X versions), and assumed that the shaded client was provided because of potential issues with any changes you have made.

Yes, the issue is that we cannot append a digit to the elasticsearch version number in order to publish our releases because plugins' version must match elasticsearch version.
The workaround is to install locally strapdata artifacts in your maven repository to build your projects. Just clone the elassandra project (with --recurse-submodules), and run:
gradle publishToMavenLocal -Dbuild.snapshot=false -Dmaven.repo.local=/Users/xxxxx/.m2/repository

authors: LyndonArmitage vroyer

repo: strapdata/elassandra


text:
Update accessing parent data guide with lazy type declaration

Description
The "accessing parent data" guide did not actually work as written because the strawberry.Parents need to use lazy declarations if the class is not yet defined.
This was identified and discussed in https://github.com/strawberry-graphql/strawberry/issues/3481#issuecomment-2503867702
The strawberry lazy incantation is quite verbose, hence why "self" remains useful.
I'm definitely not a doc writer, so just did my best. Feel free to suggest edits.
Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[x] Documentation

Issues Fixed or Closed by This PR

https://github.com/strawberry-graphql/strawberry/issues/3481

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Summary by Sourcery
Documentation:

Update the 'accessing parent data' guide to use lazy type declarations for unresolved class references.

Checking the changes to the docs here I wonder if straightforward cases like this, where Parent is something in the same file where it is defined, could avoid requiring lazy
i.e. lazy is mostly useful for when we want to avoid circular import issues, and because of that, we need to import the other type inside a if TYPE_CHECKING statement.
For the cases documented here, User is defined in the same file so I would expect that it would work without requiring lazy.
Maybe we should try to fix the issue instead? What do you think @mattalbr ?

@mattalbr I'll try to play around with that during the weekend and see if I can come up with a solution :)

repo: strawberry-graphql/strawberry


text:
Add Ruff as Python linter and code formatter

Ruff is an extremely fast Python linter and code formatter, written in Rust. ⚡
Drop-in parity with Flake8, isort, and Black
The pre-commit-config.yml file would look like below:
# Run the Ruff formatter.
- repo: https://github.com/astral-sh/ruff-pre-commit
  # Ruff version.
  rev: v0.0.291
  hooks:
    - id: ruff-format
# Run the Ruff linter.
- repo: https://github.com/astral-sh/ruff-pre-commit
  # Ruff version.
  rev: v0.0.291
  hooks:
    - id: ruff
      args: [ --fix, --exit-non-zero-on-fix ]

Also there would be no need for .flake8, .isort.cfg.
Ruff can replace black, isort, and black as a dependency.

I like the idea but ideally as you say Ruff should replace all three tools. At least the formatting part, and to lesser extent the linting part is still pretty new.
So I generally agree with the idea, but I wouldn't do the switch just yet.

Sounds good!

I decided that it is time and replaced isort, flake8 and Black with ruff!

authors: stribny tugrulpinar

repo: stribny/sidewinder


text:
feat: Particle example

This is a fairly simple particle example.
This also adds an extension to be able to add the particle render stage to the graphics compositor.

This was also on my ToDo so we can enjoy particles. Thanks for being a step ahead! 🙂

authors: Doprez VaclavElias


text:
feat: add ui server implementation

Note: this is in progress, and is likely to be a large PR.

adds TS config (derived from #29)
implements server build
adds placeholder dockerfile to use the build
implements server + client module (in ts)
updates client code to be ts based
updates linting config for ts
updates doc around build/commands to run

Closes: #36
Signed-off-by: Matthew Chirgwin chirmatt@uk.ibm.com

@dlabaj @nictownsend / @JQrdan now ready for review - I am looking into how we could test the main.ts file at the root of the server - I have something which works, but fails to collect coverage. The tests could be included if desired, but have no coverage captured. Thoughts?

Do you see these too? Are they expected?

Everything was passing for me when I went from draft -> full PR. Let me double check I haven't broken anything.

When I run the dev server with npm run start I see servers start on ports 8080 (webpack-dev-server), 9080 (mockadminserver) and 3000 (Strimzi-ui server). Going to http://localhost:3000/ fails with a 404 - is https://github.com/matthew-chirgwin/strimzi-ui/blob/36-ui-server/utils/dev_config/server.dev.config.js#L20 supposed to be set to true or would we not expect to exercise the UI via the server in dev mode? Should we only use the webpack-dev-server for client side dev/testing?

When running npm run start, webpack dev server hosts the client, so a request to http://localhost:3000/ will 404 - as there is no (built) client to host. When run via e2e tests, the client is built and served by express as per a prod topology, so that will return index.html

Additionally, when I try the http://localhost:3000/api endpoint, I get a 404 response, even though the api module and the mockapi modules are enabled in the Strimzi-ui and mockadminserver respectively. It looks like the express handler may be stripping the api part off the url, when it gets proxied to the mockadminserver..

Good spot! /api should not be removed - will fix and add a test!

Tests are now passing after re-clearing out my node_modules and running npm run clean. Comment above updated. :)

I have added a new configuration option for the context root, which will resolve the issue @ajborley mentioned re the proxying of requests loosing their context root. As we know what the context root will be for development I have set it up in the configuration so it will work as expected. Once Strimzi-admin is hosting an api, a further update will be needed to change the default context root value to the actual value.

@nictownsend / @dlabaj / @ajborley I have just updated the PR given the CI work delievered yesterday. Some notable changes:

the 'main' tests for the server have been removed. They are not reliable, and fail in isolation (with no other tests running) in CI. I do not want to hold the PR up, and will look at alternatives in/as a part of #13
multiple quality of life changes around actions

make sure Jest exits
use LTS npm (fixing an issue where it would error/kill the PR workflow)
add a placeholder e2e cclient test so that check completes
tidy up the response from the commenter action

Print NA rather than Infinity in / 0 calculations
Support multiple bundles
Note: the comment is not appearing in this PR - (node:1) UnhandledPromiseRejectionWarning: HttpError: Resource not accessible by integration - suggests a permission issue with the action - would suggest a follow on issue.

regenerate/update of the package-lock due to rebase changes

This is a sizable change - can I please request final reviews from you all?

authors: ajborley matthew-chirgwin

repo: strimzi/strimzi-ui


text:
Update jQuery and Bootstrap to latest versions

Update jQuery and Bootstrap to latest versions.
I tested this locally with no problems - both changes are very minor with no breaking changes,

Hi @coliff -- this is just an example page. I don't think there's a particular need to bump these deps. Thanks though!

authors: coliff jenan-stripe


text:
Restore S3 tests

Restore S3 tests, now that we have a good S3 test account again.
Also run tests verbosely, so that we can actually tell that S3 tests are running and not skipped.

God speed.
LGTM

authors: scottjab-stripe vasi-stripe

repo: stripe/sequins


text:
Deep linking to a specific stripe account

Sometimes a user belongs to multiple stripe accounts.
When using deep links , how do we create a link that will direct the user to a specific stripe account?

Also can the stripe app access custom query string parameters that we add to the link?

We don't support deep linking into specific user accounts from outside of Stripe today. With Install Links you can pass state along when you onboard your users outside of the Stripe Dashboard.
What is the experience and scenario you want to enable @clement911 ?

@auchenberg-stripe  The scenario is just a normal deep link scenario.
That is, we want to share links in an email or in our app/website so that the user navigates to a specific page into their stripe dashboard.
We know the exact account_id that we want to direct the user to.
The issue arises when the user belongs to multiple Stripe accounts. Deep links (and any link to the dashboard in general) seem to always load the dashboard  with the most recently used stripe account.
Ideally, we could pass an additional query string account_id param to specify that we want to load the dashboard for a specific account.
For example: https://dashboard.stripe.com/customers?account_id=acct_XXXXX&open_drawer_app=com.example.app

This is not related to stripe apps, but we have the same problem with customers that we have transferred using the PAN copy feature. They now exist in multiple stripe accounts with the same customer ID and it would be great to be able to deep link to a customer in a specific stripe account.

Oha, seems this is still not solved 😢
Use-case: My internal customer management collects entries for multiple Stripe accounts, supports multiple accounts via webhooks ...  Now (thanks to Murphys law) whenever I want to e.g. see a customer invoice I land on an error page, telling me that this customer does not exist.
Now I have to switch the account, close the page, click the deep link to the invoice again.
As I have to do that quite often every day, the only workaround is using multiple browsers. As you can imagine this is error prone as well.
While this doesn't sound too complicated to implement, my hopes are low, considering the age of this issue.

@kevinpapst I was independently just trying to figure out how I can link to a specific account in the stripe dashboard, and I’m seeing you can just make it the first part of the URL path, like:
https://dashboard.stripe.com/{acct_XXXXX}/customers

I’ve never worked with Stripe deep links though, so IDK if this helps with that, but it helps with the issue I’m encountering.

repo: stripe/stripe-apps


text:
createPaymentMethod not resolved with test card on live mode on android

Describe the bug
createPaymentMethod is not resolved when using stripe's test cards on live mode on android.
To Reproduce
Steps to reproduce the behavior:

Create CardField input
Enter stripe's testing card eg: 4242 4242 4242 4242
Submit card data with const { paymentMethod, error } = await createPaymentMethod({ type: "Card", billingDetails }) method
Promise not resolved neither with error or exception.

Expected behavior
Promise to be resolved with error {"code": "Failed", "message": "Your card was declined"}
Smartphone (please complete the following information):

Device: Samsung S9
OS: Android 10
Version 0.1.0

@aganov thanks for flagging this! Indeed a bug.

authors: aganov thorsten-stripe

repo: stripe/stripe-react-native


text:
iOS | onDidFinishInstallingUpdate callback | Result error object incorrect formatting

Describe the bug
When an error occurs during installing an update, the resulting error object on iOS is incorrectly formatted.
To Reproduce
Steps to reproduce the behavior:

Connect to a reader that has a required software update (simulated or physical). Ensure logLevel is set to "verbose"
While updating, turn off the physical reader or trigger an error with a simulated reader
See console, error object is shown and improperly formatted

Example: The error message is double nested, to access it requires setting a constant to result.error?.error?.message
 [Stripe terminal]: didFinishInstallingUpdate Object {
  "deviceSoftwareVersion": "2.01.00.15-SZZZ_Prod_US_v1-480001",
  "error": Object {
    "error": Object {
      "code": "ReaderSoftwareUpdateFailedBatteryLow",
      "message": "Updating the reader software failed because the reader's battery is too low. Charge the reader before trying again.",
    },
  },
  "estimatedUpdateTime": "estimate5To15Minutes",
  "requiredAt": "1664312899915",
}

Expected behavior
I expected the error object to look like it does on android, allowing access like so  result.error?.message
Example:
 [Stripe terminal]: didFinishInstallingUpdate Object {
  "deviceSoftwareVersion": "2.01.00.15-SZZZ_Prod_US_v1-480001",
    "error": Object {
      "code": "ReaderSoftwareUpdateFailedBatteryLow",
      "message": "Updating the reader software failed because the reader's battery is too low. Charge the reader before trying again.",
    },
  "estimatedUpdateTime": "estimate5To15Minutes",
  "requiredAt": "1664312899915",
}

Smartphone (please complete the following information):

Device: iPhone 13
OS: iOS 16.0
Expo: SDK 45

thanks for reporting and sorry for the delay getting to this. #412 should fix up the unintentional double nesting there!

authors: bric-stripe parkerbo

repo: stripe/stripe-terminal-react-native


text:
Get rid of ArtifactManagementServiceImplTest#setArtifactsTimestampAndRedeploy

Task Description
Currently there is workaround method ArtifactManagementServiceImplTest#setArtifactsTimestampAndRedeploy which targets to make SNAPSHOT timestamps suit for MavenRepositoryFeatures.removeTimestampedSnapshots logic when SNAPSHOT versions should be removed by date. We need to rework the MavenRepositoryFeatures.removeTimestampedSnapshots parameters to be able to pass a date as parameter when removing SNAPSHOT versions older then specified amount of days.
Tasks
The following tasks will need to be carried out:

[ ] There should be a new MavenRepositoryFeatures method

    public void removeTimestampedSnapshots(String storageId,
                                           String repositoryId,
                                           String artifactPath,
                                           int numberToKeep,
                                           Date keepDate)

this method should be called by original removeTimestampedSnapshots with keepPeriod parameter.

[ ] Use removeTimestampedSnapshots method with Date keepDate parameter within testRemoveTimestampedSnapshotsWithPreviousDate test case
[ ] Drop the setArtifactsTimestampAndRedeploy method from ArtifactManagementServiceImplTest

Task Relationships
This task:

Relates to: PR #1434

Help

Our chat
Points of contact:

@carlspring
@fuss86
@sbespalov
@steve-todorov

Can I work on this issue?

Hi @us3rna ,
If course! Is the description clear enough? Please, feel free to join our chat channel for more help.
Martin

@Daniel-Jacob
are you still working on this?

@carlspring @sbespalov
Can I start working on this issue?

Hi @pyashwanthkumar ,
Yes, please!

I almost finished development on the issue. There is a small part which needs fixing i.e promoting backward compatibility of our java method. Currently, I am working on that. Will update once its done.

Hi @carlspring @sbespalov
removeTimestampedSnapshots with keepPeriod parameter should call the new removeTimestampedSnapshots with keepDate parameter. How do we set this date? Should we derive it from keepPeriod?

@pyashwanthkumar : Did you open a pull request for this?

authors: carlspring pyashwanthkumar sbespalov us3rna

repo: strongbox/strongbox


text:
Retina displays - 404 error when there is no @2x image

Hi,
we are facing a problem with retina.js on retina screens. We have premium template that has no retina images, but we use the script because of our buyers, so they don't have to include it by themselves.
The problem is that template doesn't have retina images, only regular ones. On MAc, retina display, the normal image apears, but script is generating 404 errors in console (as it can't find @2x images). Can you help us to solve this issue. I think that the script should just ignore if there is no retina images, not showing 404 error in console. Here is the link to template in question: http://www.pixel-industry.com/html/trucking/
Thank you in advance.
Kind regards,
Andrijana

This is not a bug, it is a feature. On HTTP methods, even OPTIONS, HEAD or GET they obviously return 404 Not Found if the file is not found. Retina.js performs this to check if the file exists to be replaced... So, if you want, you can add data-no-retina to your images tags to avoid requesting the retina version of them. It is in the docs.

Wouldn't it be easier to add a class for images that has hi-res copy and avoid tons of 404 errors that are really bad...
http://www.firmthemes.com/jquery/how-to-avoid-retina-js-404-errors/

I agree, but this breaks backwards-compatibility. Maybe for 2.0 @strues ?

This is fixed in version 2.0 of Retina.js. We'll be releasing it officially in the next couple of days.

Has this been fixed? I am using v2.1 and still get 404 errors in my console.

The project seems to be abandoned

Sorry guys I lost the ability to merge code after the company which put out RetinaJS went under.

Thanks for the update. I'll see if I can fix it. Cheers.

No problem. I'll see what I can do about getting write permission

Years later, is this code available for me to implement myself?

Hi there, do you guys have  any good news about this problems?

Hi, is there already a solution for this?

Add this to the .htaccess
# This block of code needs to go above your Wordpress rules
<IfModule rewrite_module>
  #This is to short circuit non existent Retina image requests generated by retina.js
  # without this, the whole wordpress 404 stack will be executed which is very expensive
  # We simply redirect the request to the non @2x version of the file, if one exists, otherwise, send a 404 status
  RewriteEngine on
  RewriteBase /
  RewriteCond %{REQUEST_FILENAME} @2x\.[a-z]+$
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule ^(.*)@2x(.*)$ $1$2 [E=NORETINA:1]
  RewriteCond %{ENV:NORETINA} 1
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule .* - [L,R=404]
</IfModule>

do this   // i.setAttribute("src", e),
in line 28

authors: Smitty17 clemensg djalexa kleuter lucasff melesch nouser33 pixel-industry steve231293 strues terzom

repo: strues/retinajs


text:
Change Stage input name in Analysis.Define Gh comp.

#681

repo: strusoft/femdesign-api


text:
Unicode emoji support in the console reporter

Add unicode emoji support to the console reporter.
For more info, see #975

@JoshuaKGoldberg Do you want to do this during hacktoberfest (starting next week)?
Or @noamyogev84 Do you still have plans to do this?

All you, go ahead 😁

Nop. go ahead :)

All right, closing this issue for now.

https://twitter.com/JoshuaKGoldberg/status/1484551399551778826?t=8Gh5U1jI_PxJ7J8UHHuqfA&s=19 👀👀

authors: JoshuaKGoldberg nicojs noamyogev84 simondel

repo: stryker-mutator/stryker-js


text:
Feature/configurable ng test

Fixing #1105

Need some help with the tests?

authors: YoeriVD nicojs

repo: stryker-mutator/stryker


text:
Improve browser compatibility

For example, by removing the use of fetch!

It's already relying on ES2015, any browser that supposed things like template literals and arrow functions would also support fetch.

I don't think so - as far as I know, Safari supports everything I used except fetch.

Yup, you're right. I actually just got bitten by this in a prototype!

Added babel transpilation to get safari support. close enough!

authors: developit stubailo

repo: stubailo/microhn


text:
🛑 Beefs and Beers is down

In 11fcca8, Beefs and Beers (https://beefsandbeers.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beefs and Beers is back up in 9291339 after 14 minutes.

repo: studiovlijmscherp/uptime


text:
🛑 Status is down

In 9610838, Status (https://status.xoro-hosting.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Status is back up in c64ff3b after 8 minutes.

repo: stxrlite/xoro-updates


text:
Add error system

Prod builds went down from 9522 to 8892 bytes (min + gzipped).

@Andarist Thank you for kicking this off. I'm taking a bit of a breather from V2 before diving in to V3 work, but Ill aim to get some initial comments in next week.
Also, I updated this to be agains the version-3 branch since this is currently on the roadmap for that release (#354)

Take your time, this doesnt have to wait till v3 though - what I mean is it shouldnt be a breaking change.

Pulled this code into #398. Thanks for the contribution @Andarist!

authors: Andarist bhough

repo: styled-components/polished


text:
Does using css inside a styled component cause a performance hit?

Hi. I posted this question over on stack overflow and thought it would be helpful to post here as well there isn't a lot of SC traffic over there.
https://stackoverflow.com/questions/60663197/does-using-the-css-function-inside-a-styled-component-cause-a-performance-hit
To get proper code completion, linting, and coloring of styled-components code using Visual Studio Code we've been using the css function as a template wrapper.
Here's an example.  Without the css function all the css code is simply great text without any auto-complete.

Does this have a performance impact?
Are we be better off foregoing the code editor conveniences and using simple template literals?

https://stackoverflow.com/questions/60663197/does-using-the-css-function-inside-a-styled-component-cause-a-performance-hit

repo: styled-components/styled-components


text:
Override library CSS (React Semantic UI)

Cool lib!
We're using React Semantic UI and we want to use Styled components to override the styles.
React Semantic UI makes a component like <Card className="ui card inverted" />. The selector they are using then is .ui.card.inverted. When we add styled components, the component becomes <Card className="ui card inverted STYLED-COMPONENT-ID" />.
The problem here is that the React Semantic UI css rules "win", because they are more specific.
Is there anything we can do to make the Styled Components CSS "win"?

The simplest but not so clean solution would be to append !important to every rule. You could also bump specificity of styled-components with
const styled = styled.div`
  &&& {
    // You rules
  }
`

This should work because your selector would be .STYLED-COMPONENT-ID.STYLED-COMPONENT-ID.STYLED-COMPONENT-ID and has the same specificity as React Semantic UI.

Cool, thanks. Will try that :)

We are about to decide whether to use Semantic UI in a ReactJS framework and truly love Styled Components. So my question is:
Did it work @arthurvi ?
Thanks in advance.

@cbroberg It ought to have worked, since this is clearly a specificity issue, that we've seen with a lot of third party css frameworks unfortunately :/

You can always add more &s too. If only ! was a valid char for a function name in JS like it is in Ruby. You could write: styled.div!!!! to let existing CSS know you mean business 😜
If you're ever in doubt about specificity (the & trick above won't work if you have ID selectors in existing CSS), https://specificity.keegan.st/ is great.

This solution worked perfectly for me. Great solution @k15a. More flexible than !important, but it gets the job done.
const Styledbutton = styled(Button)  &&& {       font-size: 1rem;    } ;

There's a Babel plugin that does this automatically for you now! https://github.com/QuickBase/babel-plugin-styled-components-css-namespace

A lot of times Semantic UI has specificity that's greater than what the &&& solution can offer. For example, when styling menu components, the items will include contexts and pseudoselectors, which I believe doing &&& basically can't do anything about. This is generally an issue with CSS/Semantic UI, not with styled-components, but, for what it's worth, I don't know that I'd recommend using Semantic (or any framework like it) with styled-components.
Does anyone know of any frameworks that use styled-components internally in such a way that they are easier to override using .extend and theme providers?

I think this prospective feature could help with that scenario: https://github.com/styled-components/styled-components/issues/1789

My temporary solution works fine:
const Anchor = styled.span`
  a {
    color: black;
    font-weight: bold;
    cursor: pointer;
    font-size: 1.2em;
  }
`;

but it's wrong because generate all the time new span element

It feels strange that this is so hard to achieve using a component for React, don't we all extend the component in some way? Is theming an option?

ugh. wish semantic-ui just used BEM to begin with, this wouldn't even be a problem then.

For me Semantic UI React goes very well with Styled Components.
In my case I only use the semantic-ui-react for components, I dont use the Semantic styles.
E.g. when the Semantic Dropdown is active you can still use that classes.
e.g.:
const StyledDropdown = styled(Dropdown)`
  background: #000;
  padding: 10px;
  &.active {
   background: #f0f0f0;
 }
`

In some cases you can even use your own props, so you don't need the Semantic classes e.g.:
StyledSidebar = styled(Sidebar)`
  display: ${ props => props.visible ? 'block' : 'none' };
`

// isVisible, some state boolean.. ?
render (
  <StyledSidebar visible={ isVisible } ></StyledSidebar>
)

In this case we don't use the built in Semantic active class, but just toggle the display style.

Hi, One thing you could do, is not use the semantic ui style dependency, which I prefer.. But I don't know how big your project is.
So basically I'm trying to say, just use the semantic components only for their functional purpose.
Other way you can try is to override it like this:
const MyStyledComponent = styled(InlineStyledComponent)  &[style] {     font-size: 12px !important;     color: blue !important;   }
instead of &&& using &[style]
Regards

Van: Ignacio Giagante notifications@github.com
Verzonden: woensdag 24 juli 2019 23:22
Aan: styled-components/styled-components styled-components@noreply.github.com
CC: iweurman iweurman@outlook.com; Comment comment@noreply.github.com
Onderwerp: Re: [styled-components/styled-components] Override library CSS (React Semantic UI) (#501)
Hi. I'm having an issue with Semantic UI & Styled-components. Basically, I think Semantic-ui overrides the styles added using &&&. It does not work. Any idea?
[semantic-ui-styled-components]https://user-images.githubusercontent.com/3419609/61834936-2e5d6480-ae50-11e9-8998-07cc53da1b98.png
Component & Form
import { Dropdown } from 'semantic-ui-react'
import Chevron from './assets/right-thin-chevron.png'
export const DropdownStyled = styled(Dropdown)  &&& {     display: 'inline-block';     font-Family: 'Helvetica';     font-Style: 'italic';     font-Weight: '300';     font-Size: '20px';     line-Height: '23px';     color: '#BCB4B4';     padding: '.6em 1.4em .5em .8em';     width: '100%';     max-width: '100%';     box-sizing: 'border-box';     margin: '0';     border: '1px solid #AC8B13';     border-radius: '4px';     background-color: 'white';     background-image: 'url(${Chevron})';     background-repeat: 'no-repeat, repeat';     background-position: 'right .7em top 50%, 0 0';     background-size: '.65em auto, 100%';     appearance: 'none';   };
import React from 'react'
import { Button, Checkbox, Form } from 'semantic-ui-react'
import { DropdownStyled } from './style'
const options = [
{ key: 1, text: 'Choice 1', value: 1 },
{ key: 2, text: 'Choice 2', value: 2 },
{ key: 3, text: 'Choice 3', value: 3 }
]
const FormExampleForm = () => (

First Name

Last Name

Submit

)
export default FormExampleForm```
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/styled-components/styled-components/issues/501?email_source=notifications&email_token=AG2SIH5XNWL4Y2423XL4AVTQBDP3FA5CNFSM4DAFZDC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2X4CJI#issuecomment-514834725, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AG2SIH44KM6NU5XI7W6ID4DQBDP3FANCNFSM4DAFZDCQ.

authors: RevolutionParts-Justin airtonix arthurvi cbroberg geelen iweurman k15a mxstbr notflip philpl probablyup rivertam xargr


text:
Warning: React does not recognize the X prop on a DOM element

I use ant design and styled-component
and then I use styled-system for custom some style but I got this error
const Footers = () => {
  return (
    <StyledFooter textAlign="center">BisMarck</StyledFooter>
  )
}

Warning: React does not recognize the textAlign prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase textalign instead. If you accidentally passed it from a parent component, remove it from the DOM element

I think it is a styled-components trouble, related with this:
https://styled-system.com/guides/removing-props-from-html/#styled-components

Yes, it is. See https://styled-system.com/guides/removing-props-from-html

A way to managed this on styled-components is by using  withConfig. You can tweak the shouldForwardProps to return true or false.
e.g
const StyledTitle = styled(Title).withConfig({
  shouldForwardProp: (prop) => !['justifyContent', 'alignItems'].includes(prop),
})<FlexboxProps>`
  ${flexbox}
 `

authors: jxnblk klawingco localnet niawjunior

repo: styled-system/styled-system


text:
V15 support?

https://github.com/stylelint/stylelint/blob/4f49f93297461d0f60f5b958a591dd145710c848/docs/migration-guide/to-15.md

v15 was just released 4 hours ago so I'm sure this hasn't had a chance to get updated. That being said, it does seem that the peerDeps need updating.

authors: Mister-Hope reintroducing


text:
🛑 su2umarathon is down

In 5522fbb, su2umarathon (https://su2umarathon.netlify.app/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: su2umarathon is back up in 3e56e98.


text:
Miui 12 Sağlık Uygulaması

Suat üstad kolay gelsin 12 sağlık uygulamasında uyku bölümüne girince hata veriyor

sağlık uygulamasında aynı sorun var Uyku basınca hata raporu veriyor

sağlık uygulamasında aynı sorun var Uyku basınca hata raporu veriyor

Ben farklı birşey söyledim sanırım

sağlık uygulaması "ayarlar"a basınca da hata verip kapanıyor

20.5.7 sürümünde sağlık uygulamasındaki uyku sorunu halen devam ediyor uyku ya tıklayınca hata veriyor

Bu sorun uzun zamandır var. Miui 11 de Sağlık uygulaması için global apk kullanılıyordu sorun yine vardı. Miui 12 de yeni sürüm ile benim çeviriye geçildi sorun yine devam ediyor. Açıkçası sorunun sebebini ve çözümünü şuan için bilmiyorum.

Bu sorun uzun zamandır var. Miui 11 de Sağlık uygulaması için global apk kullanılıyordu sorun yine vardı. Miui 12 de yeni sürüm ile benim çeviriye geçildi sorun yine devam ediyor. Açıkçası sorunun sebebini ve çözümünü şuan için bilmiyorum.

Desene android 10 a geçişte kameradan galeriye geçiş sorunu gibi bir kronik sorun daha oluştu kötü olmuş :-(

@mahmutuslu evet o sorunda Türkçe dilinde olan bir sorundu, ama düzeltmeyi güncelleme ile xiaomi kendisi yaptı. Maalesef buda tam onun gibi bir durum.

@suatsari şimdi bunu xiaomi ye anlatmak mesele işte sana yazması kolay türkçe çünkü xiaomi ye anlatma kısmı beni aşar işte inşallah biri anlatır

@suatsari hocam miui12 sağlık uygulaması ile ilgili mi9se de adımsayar da da problem var sağlık uygulamasının içine girinceye kadar uygulama kasasındaki adım sayar takibini güncellemiyor sağlık uygulamasina girince guncelliyor İngilizcede sorun yok

@mahmutuslu hocam Çin sürümü üzerinden çeviri yaptığımız için geri bildirim yapamıyoruz. Zaten orijinal apk'da Türkçe yok. Global apk olsaydı, içerisinde resmi olarak Türkçe çevirisi olduğu için hata kodlarını gönderebilirdik.

@serserim09 hocam miuipro çeviri ekibinin başındaki arkadaştan yardım istedim. Sistem dili Rusça, Sağlık uygulaması dili Türkçe olarak bana video gönderdi, hiçbir sorun yok, bütün menüler çalışıyor. Sistem dilini Türkçe yapınca hata veriyor. Oda işin içinden çıkamadı. Şuan için bu konuda ne yapabilirim bilemiyorum maalesef...

@mahmutuslu hocam Çin sürümü üzerinden çeviri yaptığımız için geri bildirim yapamıyoruz. Zaten orijinal apk'da Türkçe yok. Global apk olsaydı, içerisinde resmi olarak Türkçe çevirisi olduğu için hata kodlarını gönderebilirdik.

19 mayısta global tanıtılacakmış bu durumda eğer globale koyarlarsa bu sağlık uygulamasını o zaman işimiz kolay doğru mu anladım suat hocam

@serserim09 hocam miuipro çeviri ekibinin başındaki arkadaştan yardım istedim. Sistem dili Rusça, Sağlık uygulaması dili Türkçe olarak bana video gönderdi, hiçbir sorun yok, bütün menüler çalışıyor. Sistem dilini Türkçe yapınca hata veriyor. Oda işin içinden çıkamadı. Şuan için bu konuda ne yapabilirim bilemiyorum maalesef...

Elinize emeğinize sağlık hocam biz kesin olarak eminiz ki siz elinizden gelenin fazlasını yapıyorsunuz. MİUİ12 globala çıkınca biraz daha rahat olur düzenlemeler. ilginiz için teşekkürler.

@mahmutuslu evet hocam, sorun var mı yok mu ve sorunu anlamamız açısından faydalı olacaktır. İnşallah global de de sorun devam eder, o zaman düzeltme işi onlara düşer :)

@mahmutuslu evet hocam, sorun var mı yok mu ve sorunu anlamamız açısından faydalı olacaktır. İnşallah global de de sorun devam eder, o zaman düzeltme işi onlara düşer :)

Teşekkürler üstad bu arada bu haftaki mi room 20.5.14 ü kurdum aynı sorun devam ediyor gerçi bende akıllı saat var çok dert etmiyorum ama çin betada kullanmıştım onu uykudayken horlamanı falan kaydediyor :-) gönül istiyor ki türkçeside düzgün çalışsın umarım xiaomi bu sorunu çözer

@serserim09 sağolun hocam, miui 12 geçişinde 4 binden fazla satır değişti, 40 civarı apk'da değişiklikler oldu ve 3 tane repo var. On binlerce satırla uğraştım. İllâ ki arada gözden kaçan şeyler olacaktır, zamanla bizde eksiklerimizi tamamlarız. İleride çok daha iyi olacaktır.

Suat üstad global beta tester seçilmişim şimdi global betaya geçsem senin işine yarar mı ?

@mahmutuslu evet hocam, global beta da sorun olup olmadığını öğrenirsek ne yapmamız gerektiği konusunda daha iyi bir fikir sahibi oluruz.

Tamamdır üstad çorbada benimde bir tuzum olsun muhtemelen etkinlikten sonra dağıtılır diye tahmin ediyorum ben şimdi fastboot Roma geçeyim geldiğinde yada gelirse yazarım sana

@mahmutuslu tamamdır hocam kolay gelsin

@suatsari etkinlik yarım saat sürdü ve hiç health uygulamasından bahsedilmedi haftaya dağıtılacakmış valla çözümsüz kalacak sanırım bu iş

authors: altiner mahmutuslu onurekici serserim09 suatsari


text:
fix: move changesets back to main

What is the purpose of this pull request?

What problem is this solving?

Types of changes

[ ] Feat: (new functionality)
[ ] Bug fix: ([#ref number] non-breaking change which fixes an issue)
[ ] Chore: (improvements that will not reflect in production behaviour)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires change to documentation, which has been updated accordingly.

#66  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @keeganpotgieter and the rest of your teammates on  Graphite

repo: subifinancial/subi-connect


text:
🛑 Cubari (imgbox) is down

In 0ff8056, Cubari (imgbox) (https://cubari.moe/read/imgbox/cUGEkRbdZZ/?cache_buster=$GITHUB_RUN_NUMBER) was down:

HTTP code: 500
Response time: 8340 ms

Resolved: Cubari (imgbox) is back up in 6b7004a after 1 hour, 8 minutes.

repo: subject-f/cubari-status-page


text:
🛑 Guya.moe Proxied is down

In 73cce7d, Guya.moe Proxied (https://ice.guya.moe/) was down:

HTTP code: 521
Response time: 124 ms

Resolved: Guya.moe Proxied is back up in bdaabe4 after 56 minutes.

repo: subject-f/guya-status-page


text:
passing extra user parameters to render_autoindex(...)

hi,
as i saw in the code 'render_autoindex' calls 'render_template' and passes its own context-dict
, so if a user want to make his own template and pass his own parameters two template it crashes.

return autoindex.render_autoindex(path='/', endpoint = '.app_root', template='myui.html', form=form)
the paramter 'form' throws an exception because it cannot be added to the 'render_autoindex'

my fault did not see template_context parameter

repo: sublee/flask-autoindex


text:
Lime-79, Issue 46: Fix unused vars

Description
Stacked pull request on #158
Compiler detects unused variables, function parameters and a function that can be restricted to pure. I'll enumerate them here:
SavingsAccount.sol L209 —> _receivedToken is unused
SavingsAccount.sol L246 —> _receivedToken is unused
NoYield.sol L152 —> function parameter address _asset is unused
NoYield.sol L162 —> function parameter address _asset is unused
NoYield.sol L53 —> liquidityToken function visibility can be restricted to pure
Integrations Checklist

[x]  Have any function signatures changed? If yes, outline below.
[ ]  Have any features changed or been added? If yes, outline below.
[ ]  Have any events changed or been added? If yes, outline below.
[ ]  Has all documentation been updated?

Changelog

SavingsAccount.sol L209 —> _receivedToken is unused (Removed)
SavingsAccount.sol L246 —> _receivedToken is unused (Removed)
NoYield.sol L152 —> function parameter address _asset is unused (skipped: https://linear.app/sublime-finance/issue/LIME-79#comment-06824ec6)
NoYield.sol L162 —> function parameter address _asset is unused (skipped: https://linear.app/sublime-finance/issue/LIME-79#comment-06824ec6)
NoYield.sol L53 —> liquidityToken function visibility can be restricted to pure (Changed)

Event Signature Changes
Function Signature Changes

function liquidityToken(address _asset) external *pure* override returns (address _tokenAddress)

Features
Events

Codecov Report

Merging #159 (5b58e20) into lime-71 (a979565) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           lime-71     #159   +/-   ##
========================================
  Coverage    85.01%   85.01%
========================================
  Files           16       16
  Lines         1735     1735
  Branches       321      321
========================================
  Hits          1475     1475
  Misses         260      260

Impacted Files
Coverage Δ

contracts/SavingsAccount/SavingsAccount.sol
91.04% <100.00%> (ø)

contracts/yield/NoYield.sol
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

authors: KalpitaMandal codecov-commenter


text:
Simplify docusign logic

The length(filter(x)) == 0 is the same thing as not any(x). If we also require that file_type is not null, then we can go a step further: all(not x)
All these optimizations happen under the hood anyway, so the rule is still logically identical. This seems simpler to me though, and I think it's more readable (although this might be triggering for anyone with some all trauma). We can add a length check if we'd like but it's already combined with the any so it's redundant

😓 anxiety building.... In theory we can do the same thing with this rule
I'll kick off some hunt comparisons just so I can sleep at night.

Maybe it's that null case?
and length(filter(attachments, .file_type not in~ ('png', 'jpeg', 'jpg', 'bmp'))) == 0 will ignore null .file_type but my change won't run if there are any null .file_type. I'll go to not any then

This hurts my 🧠

authors: morriscode rw-access

repo: sublime-security/sublime-rules


text:
Add a metrics proxy script

This encapsulates nc-specific details.
See #1046.

@skitt I wanted to only approve but I accidentally merged this. Is it ok, or did you want to wait with this one until 0.16.0-rc0?

@skitt I wanted to only approve but I accidentally merged this. Is it ok, or did you want to wait with this one until 0.16.0-rc0?

It’s fine, thanks! I wanted to get this in as soon as possible, the dependency from rc0 was intended as a hard deadline.

authors: nyechiel skitt

repo: submariner-io/shipyard


text:
The Submariner Automated Upgrade command is updating only one component

ISSUE:
We have used the Automated Upgrade command to upgrade the submariner from v0.15.2 to v0.16.2, in the documentation, it is mentioned that all the components will be upgraded, here we see that only one component of the submariner is upgraded.
Document Referenced:
https://submariner.io/operations/upgrading/#automated-upgrade
Outputs:
From Site2, did subctl upgrade on site2
sh-4.4$ /tmp/new_subctl/bin/subctl upgrade --to-version v0.16.0 --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
 ✓ Checking if the Broker is installed
 ✓ Checking if the Operator is installed
 ✓ Upgrading the Operator to v0.16.0
 ✓ Created operator namespace: submariner-operator
 ✓ Upgrading the Connectivity component to v0.16.0
 ✓ Upgrading Service Discovery to v0.16.0

sh-4.4$ /root/.local/bin/subctl version
subctl version: v0.15.2
sh-4.4$ /root/.local/bin/subctl show all --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
 ✓ Detecting broker(s)
 ✓ No brokers found

 ✓ Showing Connections
GATEWAY                          CLUSTER   REMOTE IP       NAT   CABLE DRIVER   SUBNETS                        STATUS      RTT avg.
control-1-ru2.rackae1.mydomain   site1     172.20.200.25   no    libreswan      172.30.0.0/16, 10.128.0.0/14   connected   324.836µs

 ✓ Showing Endpoints
CLUSTER   ENDPOINT IP     PUBLIC IP     CABLE DRIVER   TYPE
site2     172.20.102.26   129.41.87.3   libreswan      local
site2     172.20.102.27   129.41.87.3   libreswan      local
site1     172.20.200.25   129.41.87.2   libreswan      remote

 ✓ Showing Gateways
NODE                             HA STATUS   SUMMARY
control-1-ru3.rackae2.mydomain   passive     There are no connections
control-1-ru4.rackae2.mydomain   active      All connections (1) are established

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  OVNKubernetes
        Service CIDRs:   [172.31.0.0/16]
        Cluster CIDRs:   [10.132.0.0/14]

 ✓ Showing versions
COMPONENT                         REPOSITORY           VERSION
submariner-gateway                quay.io/submariner   0.15.2
submariner-routeagent             quay.io/submariner   0.15.2
submariner-metrics-proxy          quay.io/submariner   0.15.2
submariner-operator               quay.io/submariner   v0.16.0
submariner-lighthouse-agent       quay.io/submariner   0.15.2
submariner-lighthouse-coredns     quay.io/submariner   0.15.2
submariner-networkplugin-syncer   quay.io/submariner   0.15.2

sh-4.4$ /root/.local/bin/subctl show all --kubeconfig /connection/kube-config/71a5f5abfc/kubeconfig
Cluster "default-cluster"
 ✓ Detecting broker(s)
NAMESPACE               NAME                COMPONENTS                        GLOBALNET   GLOBALNET CIDR   DEFAULT GLOBALNET SIZE   DEFAULT DOMAINS
submariner-k8s-broker   submariner-broker   service-discovery, connectivity   no          242.0.0.0/8      65536

 ✓ Showing Connections
GATEWAY                          CLUSTER   REMOTE IP       NAT   CABLE DRIVER   SUBNETS                        STATUS      RTT avg.
control-1-ru4.rackae2.mydomain   site2     172.20.102.27   no    libreswan      172.31.0.0/16, 10.132.0.0/14   connected   369.425µs

 ✓ Showing Endpoints
CLUSTER   ENDPOINT IP     PUBLIC IP     CABLE DRIVER   TYPE
site1     172.20.200.25   129.41.87.2   libreswan      local
site2     172.20.102.27   129.41.87.3   libreswan      remote
site1     172.20.200.26   129.41.87.2   libreswan      local
site1     172.20.200.27   129.41.87.2   libreswan      local

 ✓ Showing Gateways
NODE                             HA STATUS   SUMMARY
control-1-ru2.rackae1.mydomain   active      All connections (1) are established
control-1-ru3.rackae1.mydomain   passive     There are no connections
control-1-ru4.rackae1.mydomain   passive     There are no connections

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  OVNKubernetes
        Service CIDRs:   [172.30.0.0/16]
        Cluster CIDRs:   [10.128.0.0/14]

 ✓ Showing versions
COMPONENT                         REPOSITORY           VERSION
submariner-gateway                quay.io/submariner   0.15.2
submariner-routeagent             quay.io/submariner   0.15.2
submariner-metrics-proxy          quay.io/submariner   0.15.2
submariner-operator               quay.io/submariner   0.15.2
submariner-lighthouse-agent       quay.io/submariner   0.15.2
submariner-lighthouse-coredns     quay.io/submariner   0.15.2
submariner-networkplugin-syncer   quay.io/submariner   0.15.2

From Site2, did subctl upgrade on site1
sh-4.4$ /tmp/new_subctl/bin/subctl upgrade --to-version v0.16.0 --kubeconfig /connection/kube-config/71a5f5abfc/kubeconfig
Cluster "default-cluster"
 ✓ Checking if the Broker is installed
 ✓ Upgrading the Broker to v0.16.0
 ✓ Setting up broker RBAC
 ✓ Deploying the Submariner operator
 ✓ Created operator namespace: submariner-operator
 ✓ Deploying the broker
 ✓ Upgrading the Connectivity component to v0.16.0
 ✓ Upgrading Service Discovery to v0.16.0

sh-4.4$ /root/.local/bin/subctl show all --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
 ✓ Detecting broker(s)
 ✓ No brokers found

 ✓ Showing Connections
GATEWAY                          CLUSTER   REMOTE IP       NAT   CABLE DRIVER   SUBNETS                        STATUS      RTT avg.
control-1-ru2.rackae1.mydomain   site1     172.20.200.25   no    libreswan      172.30.0.0/16, 10.128.0.0/14   connected   274.04µs

 ✓ Showing Endpoints
CLUSTER   ENDPOINT IP     PUBLIC IP     CABLE DRIVER   TYPE
site2     172.20.102.26   129.41.87.3   libreswan      local
site2     172.20.102.27   129.41.87.3   libreswan      local
site1     172.20.200.25   129.41.87.2   libreswan      remote

 ✓ Showing Gateways
NODE                             HA STATUS   SUMMARY
control-1-ru3.rackae2.mydomain   passive     There are no connections
control-1-ru4.rackae2.mydomain   active      All connections (1) are established

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  OVNKubernetes
        Service CIDRs:   [172.31.0.0/16]
        Cluster CIDRs:   [10.132.0.0/14]

 ✓ Showing versions
COMPONENT                         REPOSITORY           VERSION
submariner-gateway                quay.io/submariner   0.15.2
submariner-routeagent             quay.io/submariner   0.15.2
submariner-metrics-proxy          quay.io/submariner   0.15.2
submariner-operator               quay.io/submariner   v0.16.0
submariner-lighthouse-agent       quay.io/submariner   0.15.2
submariner-lighthouse-coredns     quay.io/submariner   0.15.2
submariner-networkplugin-syncer   quay.io/submariner   0.15.2

sh-4.4$ /root/.local/bin/subctl show all --kubeconfig /connection/kube-config/71a5f5abfc/kubeconfig
Cluster "default-cluster"
 ✓ Detecting broker(s)
NAMESPACE               NAME                COMPONENTS                        GLOBALNET   GLOBALNET CIDR   DEFAULT GLOBALNET SIZE   DEFAULT DOMAINS
submariner-k8s-broker   submariner-broker   service-discovery, connectivity   no          242.0.0.0/8      65536

 ✓ Showing Connections
GATEWAY                          CLUSTER   REMOTE IP       NAT   CABLE DRIVER   SUBNETS                        STATUS      RTT avg.
control-1-ru4.rackae2.mydomain   site2     172.20.102.27   no    libreswan      172.31.0.0/16, 10.132.0.0/14   connected   368.614µs

 ✓ Showing Endpoints
CLUSTER   ENDPOINT IP     PUBLIC IP     CABLE DRIVER   TYPE
site1     172.20.200.25   129.41.87.2   libreswan      local
site2     172.20.102.27   129.41.87.3   libreswan      remote
site1     172.20.200.26   129.41.87.2   libreswan      local
site1     172.20.200.27   129.41.87.2   libreswan      local

 ✓ Showing Gateways
NODE                             HA STATUS   SUMMARY
control-1-ru2.rackae1.mydomain   active      All connections (1) are established
control-1-ru3.rackae1.mydomain   passive     There are no connections
control-1-ru4.rackae1.mydomain   passive     There are no connections

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  OVNKubernetes
        Service CIDRs:   [172.30.0.0/16]
        Cluster CIDRs:   [10.128.0.0/14]

 ✓ Showing versions
COMPONENT                         REPOSITORY           VERSION
submariner-gateway                quay.io/submariner   0.15.2
submariner-routeagent             quay.io/submariner   0.15.2
submariner-metrics-proxy          quay.io/submariner   0.15.2
submariner-operator               quay.io/submariner   v0.16.0
submariner-lighthouse-agent       quay.io/submariner   0.15.2
submariner-lighthouse-coredns     quay.io/submariner   0.15.2
submariner-networkplugin-syncer   quay.io/submariner   0.15.2

We couldn't do subctl gather due to the issue that we have here
https://github.com/submariner-io/submariner/issues/2857
Questions:
Till now the process that we followed for upgradation is to uninstall the older version and install the newer version. This process takes about 10 mins, during this, there will be downtime.

As this is a frequent process, such a long downtime would be detrimental to the product, is there any alternate way to address this issue?

We discovered that there is an automated upgrade command.
subctl upgrade --to-version v0.16.0 --kubeconfig <kubeconfig_path>

Is this the right way to follow for the upgrade of the submariner?
Is it expected that only one component of the submariner will be upgraded, while the command is run?
If so is there any workaround to be followed to make other components of the submariner to be upgraded?

The recommended way to deploy Submariner on OpenShift is to use Advanced Cluster Management; this takes care of upgrades for you.
In this particular instance, we need some more information; to start with, can you show the output of
/tmp/new_subctl/bin/subctl show all --kubeconfig /tmp/local-kubeconfig

(The new version of subctl shows more information than version 0.15.2.)

Hi @skitt
We have uninstalled the submariner and installed the new version of it manually due to urgent requirements.
However, we have tried the upgrade command on other clusters, it's the same result.
Outputs for upgrade commands:
sh-4.4$ /tmp/new_subctl/bin/subctl upgrade --to-version v0.16.0 --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
 ✓ Checking if the Broker is installed
 ✓ Checking if the Operator is installed
 ✓ Upgrading the Operator to v0.16.0
 ✓ Created operator namespace: submariner-operator
 ✓ Upgrading the Connectivity component to v0.16.0
 ✓ Upgrading Service Discovery to v0.16.0

sh-4.4$ /tmp/new_subctl/bin/subctl upgrade --to-version v0.16.0 --kubeconfig /connection/kube-config/c0672c4c63/kubeconfig
Cluster "default-cluster"
 ✓ Checking if the Broker is installed
 ✓ Upgrading the Broker to v0.16.0
 ✓ Setting up broker RBAC
 ✓ Deploying the Submariner operator
 ✓ Created operator namespace: submariner-operator
 ✓ Deploying the broker
 ✓ Upgrading the Connectivity component to v0.16.0
 ✓ Upgrading Service Discovery to v0.16.0

Outputs for commands show all, diagnose all, and subctl gather
For SITE 2
sh-4.4$ /tmp/new_subctl/bin/subctl show all --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
 ✓ Detecting broker(s)
 ✓ No brokers found

 ✓ Showing Connections
GATEWAY                          CLUSTER   REMOTE IP      NAT   CABLE DRIVER   SUBNETS                        STATUS      RTT avg.
control-1-ru4.isf-racki.rtp.ra   site1     9.42.107.216   no    libreswan      172.30.0.0/16, 10.128.0.0/14   connected   267.558µs

 ✓ Showing Endpoints
CLUSTER   ENDPOINT IP    PUBLIC IP     CABLE DRIVER   TYPE
site2     9.42.107.234   129.41.87.2   libreswan      local
site1     9.42.107.216   129.41.87.0   libreswan      remote
site2     9.42.107.235   129.41.87.3   libreswan      local
site2     9.42.107.236   129.41.87.4   libreswan      local

 ✓ Showing Gateways
NODE                             HA STATUS   SUMMARY
control-1-ru2.isf-rackk.rtp.ra   active      All connections (1) are established
control-1-ru3.isf-rackk.rtp.ra   passive     There are no connections
control-1-ru4.isf-rackk.rtp.ra   passive     There are no connections

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  OVNKubernetes
        Service CIDRs:   [172.31.0.0/16]
        Cluster CIDRs:   [10.132.0.0/14]

 ✓ Showing versions
COMPONENT                       REPOSITORY           CONFIGURED   RUNNING
submariner-gateway              quay.io/submariner   0.15.2       Unavailable
submariner-routeagent           quay.io/submariner   0.15.2       Unavailable
submariner-metrics-proxy        quay.io/submariner   0.15.2       Unavailable
submariner-operator             quay.io/submariner   v0.16.0      Unavailable
submariner-lighthouse-agent     quay.io/submariner   0.15.2       Unavailable
submariner-lighthouse-coredns   quay.io/submariner   0.15.2       Unavailable

sh-4.4$ /tmp/new_subctl/bin/subctl diagnose all --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
 ✓ Checking Submariner support for the Kubernetes version
 ✓ Kubernetes version "v1.25.14+bcb9a60" is supported

 ✓ Non-Globalnet deployment detected - checking that cluster CIDRs do not overlap
 ✓ Checking DaemonSet "submariner-gateway"
 ✓ Checking DaemonSet "submariner-routeagent"
 ✓ Checking DaemonSet "submariner-metrics-proxy"
 ✓ Checking Deployment "submariner-lighthouse-agent"
 ✓ Checking Deployment "submariner-lighthouse-coredns"
 ✗ Checking the status of all Submariner pods
 ✗ Pod "submariner-operator-5b7c6958b6-l2kfd" is not running. (current state is Pending)

 ✓ Checking Submariner support for the CNI network plugin
 ✓ The detected CNI network plugin ("OVNKubernetes") is supported
 ✓ Checking OVN version
 ✓ The ovn-nb database version 7.0.0 is supported
 ✓ Checking gateway connections
 ✓ Checking Submariner support for the kube-proxy mode
 ✓ Cluster is running with "OVNKubernetes" CNI which internally implements kube-proxy functionality
 ✓ Checking that firewall configuration allows intra-cluster VXLAN traffic

 ✓ Checking that services have been exported properly

Skipping inter-cluster firewall check as it requires two kubeconfigs. Please run "subctl diagnose firewall inter-cluster" command manually.

subctl version: v0.16.0

sh-4.4$ /tmp/new_subctl/bin/subctl subctl gather --kubeconfig /tmp/local-kubeconfig
Error: unknown command "subctl" for "subctl"
Run 'subctl --help' for usage.
unknown command "subctl" for "subctl"
sh-4.4$ cd /tmp
sh-4.4$ /tmp/new_subctl/bin/subctl gather --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
Gathering information from cluster "local-config"
 ✓ Gathering connectivity logs
 ✓ Found 3 pods matching label selector "app=submariner-gateway"
 ✓ Found 6 pods matching label selector "app=submariner-routeagent"
 ✓ Found 3 pods matching label selector "app=submariner-metrics-proxy"
 ✓ Found 0 pods matching label selector "app=submariner-globalnet"
 ✓ Found 0 pods matching label selector "app=submariner-addon"
 ✗ Gathering connectivity resources
 ✓ Gathering CNI data from 6 pods matching label selector "app=submariner-routeagent"
 ✓ Gathering CNI data from 3 pods matching label selector "app=submariner-gateway"
 ✓ Gathering cable driver data from 3 pods matching label selector "app=submariner-gateway"
 ✓ Gathering OVN data from OVN kube pod "ovnkube-master-jkbwb"
 ✗ Failed to gather gatewayroutes: error listing "gatewayroutes": the server could not find the requested resource
 ✗ Failed to gather nongatewayroutes: error listing "nongatewayroutes": the server could not find the requested resource
 ✓ Found 2 endpoints in namespace "submariner-operator"
 ✓ Found 2 clusters in namespace "submariner-operator"
 ✓ Found 3 gateways in namespace "submariner-operator"
 ✓ Found 0 clusterglobalegressips in namespace ""
 ✓ Found 0 globalegressips in namespace ""
 ✓ Found 0 globalingressips in namespace ""
 ✓ Gathering service-discovery logs
 ✓ Found 3 pods matching label selector "component=submariner-lighthouse"
 ✓ Found 6 pods matching label selector "dns.operator.openshift.io/daemonset-dns=default"
 ✓ Gathering service-discovery resources
 ✓ Found 0 serviceexports in namespace ""
 ✓ Found 0 serviceimports in namespace ""
 ✓ Found 0 endpointslices by label selector "endpointslice.kubernetes.io/managed-by=lighthouse-agent.submariner.io" in namespace ""
 ✓ Found 1 configmaps by label selector "component=submariner-lighthouse" in namespace "submariner-operator"
 ✓ Found 1 configmaps by field selector "metadata.name=dns-default" in namespace "openshift-dns"
 ✓ Found 0 services by label selector "submariner.io/exportedServiceRef" in namespace ""
 ✓ Gathering broker logs
 ✓ Gathering broker resources
 ✓ Found 2 endpoints in namespace "submariner-k8s-broker"
 ✓ Found 2 clusters in namespace "submariner-k8s-broker"
 ✓ Found 0 endpointslices by label selector "endpointslice.kubernetes.io/managed-by=lighthouse-agent.submariner.io" in namespace "submariner-k8s-broker"
 ✓ Found 0 serviceimports in namespace "submariner-k8s-broker"
 ✗ Gathering operator logs
 ✓ Found 2 pods matching label selector "name=submariner-operator"
 ✗ Error outputting current log for pod "submariner-operator-5b7c6958b6-l2kfd": error opening log stream: container "submariner-operator" in pod "submariner-operator-5b7c6958b6-l2kfd" is waiting to start: trying and failing to pull image
 ✓ Gathering operator resources
 ✓ Found 1 submariners in namespace "submariner-operator"
 ✓ Found 1 servicediscoveries in namespace "submariner-operator"
 ✓ Found 1 deployments by field selector "metadata.name=submariner-operator" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-gateway" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-metrics-proxy" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-routeagent" in namespace "submariner-operator"
 ✓ Found 0 daemonsets by label selector "app=submariner-globalnet" in namespace "submariner-operator"
 ✓ Found 1 deployments by label selector "app=submariner-lighthouse-agent" in namespace "submariner-operator"
 ✓ Found 1 deployments by label selector "app=submariner-lighthouse-coredns" in namespace "submariner-operator"
Files are stored under directory "submariner-20240105173047/local-config"

For SITE 1
sh-4.4$ /tmp/new_subctl/bin/subctl show all --kubeconfig /connection/kube-config/c0672c4c63/kubeconfig
Cluster "default-cluster"
 ✓ Detecting broker(s)
NAMESPACE               NAME                COMPONENTS                        GLOBALNET   GLOBALNET CIDR   DEFAULT GLOBALNET SIZE   DEFAULT DOMAINS
submariner-k8s-broker   submariner-broker   service-discovery, connectivity   no          242.0.0.0/8      65536

 ✓ Showing Connections
GATEWAY                          CLUSTER   REMOTE IP      NAT   CABLE DRIVER   SUBNETS                        STATUS      RTT avg.
control-1-ru2.isf-rackk.rtp.ra   site2     9.42.107.234   no    libreswan      172.31.0.0/16, 10.132.0.0/14   connected   324.011µs

 ✓ Showing Endpoints
CLUSTER   ENDPOINT IP    PUBLIC IP     CABLE DRIVER   TYPE
site1     9.42.107.214   129.41.87.6   libreswan      local
site1     9.42.107.215   129.41.87.7   libreswan      local
site1     9.42.107.216   129.41.87.0   libreswan      local
site2     9.42.107.234   129.41.87.2   libreswan      remote

 ✓ Showing Gateways
NODE                             HA STATUS   SUMMARY
control-1-ru2.isf-racki.rtp.ra   passive     There are no connections
control-1-ru3.isf-racki.rtp.ra   passive     There are no connections
control-1-ru4.isf-racki.rtp.ra   active      All connections (1) are established

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  OVNKubernetes
        Service CIDRs:   [172.30.0.0/16]
        Cluster CIDRs:   [10.128.0.0/14]

 ✓ Showing versions
COMPONENT                       REPOSITORY           CONFIGURED   RUNNING
submariner-gateway              quay.io/submariner   0.15.2       Unavailable
submariner-routeagent           quay.io/submariner   0.15.2       Unavailable
submariner-metrics-proxy        quay.io/submariner   0.15.2       Unavailable
submariner-operator             quay.io/submariner   v0.16.0      Unavailable
submariner-lighthouse-agent     quay.io/submariner   0.15.2       Unavailable
submariner-lighthouse-coredns   quay.io/submariner   0.15.2       Unavailable

sh-4.4$ /tmp/new_subctl/bin/subctl diagnose all --kubeconfig /connection/kube-config/c0672c4c63/kubeconfig
Cluster "default-cluster"
 ✓ Checking Submariner support for the Kubernetes version
 ✓ Kubernetes version "v1.25.14+bcb9a60" is supported

 ✓ Non-Globalnet deployment detected - checking that cluster CIDRs do not overlap
 ✓ Checking DaemonSet "submariner-gateway"
 ✓ Checking DaemonSet "submariner-routeagent"
 ✓ Checking DaemonSet "submariner-metrics-proxy"
 ✓ Checking Deployment "submariner-lighthouse-agent"
 ✓ Checking Deployment "submariner-lighthouse-coredns"
 ✗ Checking the status of all Submariner pods
 ✗ Pod "submariner-operator-7bfcdc5d48-6jv62" is not running. (current state is Pending)

 ✓ Checking Submariner support for the CNI network plugin
 ✓ The detected CNI network plugin ("OVNKubernetes") is supported
 ✓ Checking OVN version
 ✓ The ovn-nb database version 7.0.0 is supported
 ✓ Checking gateway connections
 ✓ Checking Submariner support for the kube-proxy mode
 ✓ Cluster is running with "OVNKubernetes" CNI which internally implements kube-proxy functionality
 ✓ Checking that firewall configuration allows intra-cluster VXLAN traffic

 ✓ Checking that services have been exported properly

Skipping inter-cluster firewall check as it requires two kubeconfigs. Please run "subctl diagnose firewall inter-cluster" command manually.

subctl version: v0.16.0

sh-4.4$ /tmp/new_subctl/bin/subctl gather --kubeconfig /connection/kube-config/c0672c4c63/kubeconfig
Cluster "default-cluster"
Gathering information from cluster "default-cluster"
 ✓ Gathering broker logs
 ✓ Gathering broker resources
 ✓ Found 2 endpoints in namespace "submariner-k8s-broker"
 ✓ Found 2 clusters in namespace "submariner-k8s-broker"
 ✓ Found 0 endpointslices by label selector "endpointslice.kubernetes.io/managed-by=lighthouse-agent.submariner.io" in namespace "submariner-k8s-broker"
 ✓ Found 0 serviceimports in namespace "submariner-k8s-broker"
 ✗ Gathering operator logs
 ✓ Found 2 pods matching label selector "name=submariner-operator"
 ✗ Error outputting current log for pod "submariner-operator-7bfcdc5d48-6jv62": error opening log stream: container "submariner-operator" in pod "submariner-operator-7bfcdc5d48-6jv62" is waiting to start: trying and failing to pull image
 ✓ Gathering operator resources
 ✓ Found 1 submariners in namespace "submariner-operator"
 ✓ Found 1 servicediscoveries in namespace "submariner-operator"
 ✓ Found 1 deployments by field selector "metadata.name=submariner-operator" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-gateway" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-metrics-proxy" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-routeagent" in namespace "submariner-operator"
 ✓ Found 0 daemonsets by label selector "app=submariner-globalnet" in namespace "submariner-operator"
 ✓ Found 1 deployments by label selector "app=submariner-lighthouse-agent" in namespace "submariner-operator"
 ✓ Found 1 deployments by label selector "app=submariner-lighthouse-coredns" in namespace "submariner-operator"
 ✓ Gathering connectivity logs
 ✓ Found 3 pods matching label selector "app=submariner-gateway"
 ✓ Found 6 pods matching label selector "app=submariner-routeagent"
 ✓ Found 3 pods matching label selector "app=submariner-metrics-proxy"
 ✓ Found 0 pods matching label selector "app=submariner-globalnet"
 ✓ Found 0 pods matching label selector "app=submariner-addon"
 ✓ Gathering connectivity resources
 ✓ Gathering CNI data from 6 pods matching label selector "app=submariner-routeagent"
 ✓ Gathering CNI data from 3 pods matching label selector "app=submariner-gateway"
 ✓ Gathering cable driver data from 3 pods matching label selector "app=submariner-gateway"
 ✓ Gathering OVN data from OVN kube pod "ovnkube-master-lttjt"
 ✓ Found 0 gatewayroutes in namespace ""
 ✓ Found 0 nongatewayroutes in namespace ""
 ✓ Found 2 endpoints in namespace "submariner-operator"
 ✓ Found 2 clusters in namespace "submariner-operator"
 ✓ Found 3 gateways in namespace "submariner-operator"
 ✓ Found 0 clusterglobalegressips in namespace ""
 ✓ Found 0 globalegressips in namespace ""
 ✓ Found 0 globalingressips in namespace ""
 ✓ Gathering service-discovery logs
 ✓ Found 3 pods matching label selector "component=submariner-lighthouse"
 ✓ Found 6 pods matching label selector "dns.operator.openshift.io/daemonset-dns=default"
 ✓ Gathering service-discovery resources
 ✓ Found 0 serviceexports in namespace ""
 ✓ Found 0 serviceimports in namespace ""
 ✓ Found 0 endpointslices by label selector "endpointslice.kubernetes.io/managed-by=lighthouse-agent.submariner.io" in namespace ""
 ✓ Found 1 configmaps by label selector "component=submariner-lighthouse" in namespace "submariner-operator"
 ✓ Found 1 configmaps by field selector "metadata.name=dns-default" in namespace "openshift-dns"
 ✓ Found 0 services by label selector "submariner.io/exportedServiceRef" in namespace ""
Files are stored under directory "submariner-20240105173120/default-cluster"

Subctl Gather Files :
submariner-site1-gather.zip
submariner-site2-gather.zip

Hi @dfarrell07
We can upgrade to 0.16.2 if it is compatible with OCP 4.12.x, 4.13.x and 4.14.x
Yesterday we tried to use the automated upgrade command using the subctl version v0.16.2
But, this is also doing the same(upgrading only one component of the submariner)
Before using upgrade command
sh-4.4$ /tmp/new_subctl/bin/subctl show all --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
 ✓ Detecting broker(s)
 ✓ No brokers found

 ✓ Showing Connections
GATEWAY                          CLUSTER   REMOTE IP      NAT   CABLE DRIVER   SUBNETS                        STATUS      RTT avg.
control-1-ru4.isf-racki.rtp.ra   site1     9.42.107.216   no    libreswan      172.30.0.0/16, 10.128.0.0/14   connected   329.319µs

 ✓ Showing Endpoints
CLUSTER   ENDPOINT IP    PUBLIC IP     CABLE DRIVER   TYPE
site2     9.42.107.234   129.41.87.2   libreswan      local
site2     9.42.107.235   129.41.87.3   libreswan      local
site1     9.42.107.216   129.41.87.0   libreswan      remote
site2     9.42.107.236   129.41.87.4   libreswan      local

 ✓ Showing Gateways
NODE                             HA STATUS   SUMMARY
control-1-ru2.isf-rackk.rtp.ra   passive     There are no connections
control-1-ru3.isf-rackk.rtp.ra   active      All connections (1) are established
control-1-ru4.isf-rackk.rtp.ra   passive     There are no connections

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  OVNKubernetes
        Service CIDRs:   [172.31.0.0/16]
        Cluster CIDRs:   [10.132.0.0/14]

 ✓ Showing versions
COMPONENT                       REPOSITORY           CONFIGURED   RUNNING       ARCH
submariner-gateway              quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-routeagent           quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-metrics-proxy        quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-operator             quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-lighthouse-agent     quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-lighthouse-coredns   quay.io/submariner   0.15.2       Unavailable   Unavailable

Upgrade command for site 2
sh-4.4$ /tmp/new_subctl/bin/subctl upgrade --to-version v0.16.2 --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
 ✓ Checking if the Broker is installed
 ✓ Checking if the Operator is installed
 ✓ Upgrading the Operator to v0.16.2
 ✓ Created operator namespace: submariner-operator
 ✓ Upgrading the Connectivity component to v0.16.2
 ✓ Upgrading Service Discovery to v0.16.2

Upgrade command for site 1
sh-4.4$ /tmp/new_subctl/bin/subctl upgrade --to-version v0.16.2 --kubeconfig /connection/kube-config/c0672c4c63/kubeconfig
Cluster "default-cluster"
 ✓ Checking if the Broker is installed
 ✓ Upgrading the Broker to v0.16.2
 ✓ Setting up broker RBAC
 ✓ Deploying the Submariner operator
 ✓ Created operator namespace: submariner-operator
 ✓ Deploying the broker
 ✓ Upgrading the Connectivity component to v0.16.2
 ✓ Upgrading Service Discovery to v0.16.2

Show all command for Site 2
sh-4.4$ /tmp/new_subctl/bin/subctl show all --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
 ✓ Detecting broker(s)
 ✓ No brokers found

 ✓ Showing Connections
GATEWAY                          CLUSTER   REMOTE IP      NAT   CABLE DRIVER   SUBNETS                        STATUS      RTT avg.
control-1-ru4.isf-racki.rtp.ra   site1     9.42.107.216   no    libreswan      172.30.0.0/16, 10.128.0.0/14   connected   0s

 ✓ Showing Endpoints
CLUSTER   ENDPOINT IP    PUBLIC IP     CABLE DRIVER   TYPE
site2     9.42.107.234   129.41.87.2   libreswan      local
site2     9.42.107.235   129.41.87.3   libreswan      local
site1     9.42.107.216   129.41.87.0   libreswan      remote
site2     9.42.107.236   129.41.87.4   libreswan      local

 ✓ Showing Gateways
NODE                             HA STATUS   SUMMARY
control-1-ru2.isf-rackk.rtp.ra   passive     There are no connections
control-1-ru3.isf-rackk.rtp.ra   active      All connections (1) are established
control-1-ru4.isf-rackk.rtp.ra   passive     There are no connections

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  OVNKubernetes
        Service CIDRs:   [172.31.0.0/16]
        Cluster CIDRs:   [10.132.0.0/14]

 ✓ Showing versions
COMPONENT                       REPOSITORY           CONFIGURED   RUNNING       ARCH
submariner-gateway              quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-routeagent           quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-metrics-proxy        quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-operator             quay.io/submariner   v0.16.2      Unavailable   Unavailable
submariner-lighthouse-agent     quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-lighthouse-coredns   quay.io/submariner   0.15.2       Unavailable   Unavailable

Show all command for site 1
sh-4.4$ /tmp/new_subctl/bin/subctl show all --kubeconfig /connection/kube-config/c0672c4c63/kubeconfig
Cluster "default-cluster"
 ✓ Detecting broker(s)
NAMESPACE               NAME                COMPONENTS                        GLOBALNET   GLOBALNET CIDR   DEFAULT GLOBALNET SIZE   DEFAULT DOMAINS
submariner-k8s-broker   submariner-broker   service-discovery, connectivity   no          242.0.0.0/8      65536

 ✓ Showing Connections
GATEWAY                          CLUSTER   REMOTE IP      NAT   CABLE DRIVER   SUBNETS                        STATUS      RTT avg.
control-1-ru3.isf-rackk.rtp.ra   site2     9.42.107.235   no    libreswan      172.31.0.0/16, 10.132.0.0/14   connected   372.694µs

 ✓ Showing Endpoints
CLUSTER   ENDPOINT IP    PUBLIC IP     CABLE DRIVER   TYPE
site1     9.42.107.214   129.41.87.6   libreswan      local
site1     9.42.107.215   129.41.87.7   libreswan      local
site1     9.42.107.216   129.41.87.0   libreswan      local
site2     9.42.107.235   129.41.87.3   libreswan      remote

 ✓ Showing Gateways
NODE                             HA STATUS   SUMMARY
control-1-ru2.isf-racki.rtp.ra   passive     There are no connections
control-1-ru3.isf-racki.rtp.ra   passive     There are no connections
control-1-ru4.isf-racki.rtp.ra   active      All connections (1) are established

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  OVNKubernetes
        Service CIDRs:   [172.30.0.0/16]
        Cluster CIDRs:   [10.128.0.0/14]

 ✓ Showing versions
COMPONENT                       REPOSITORY           CONFIGURED   RUNNING       ARCH
submariner-gateway              quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-routeagent           quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-metrics-proxy        quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-operator             quay.io/submariner   v0.16.2      Unavailable   Unavailable
submariner-lighthouse-agent     quay.io/submariner   0.15.2       Unavailable   Unavailable
submariner-lighthouse-coredns   quay.io/submariner   0.15.2       Unavailable   Unavailable

Diagnose all for site 2
sh-4.4$ /tmp/new_subctl/bin/subctl diagnose all --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
 ✓ Checking Submariner support for the Kubernetes version
 ✓ Kubernetes version "v1.26.11+7dfc52e" is supported

 ✓ Non-Globalnet deployment detected - checking that cluster CIDRs do not overlap
 ✓ Checking DaemonSet "submariner-gateway"
 ✓ Checking DaemonSet "submariner-routeagent"
 ✓ Checking DaemonSet "submariner-metrics-proxy"
 ✓ Checking Deployment "submariner-lighthouse-agent"
 ✓ Checking Deployment "submariner-lighthouse-coredns"
 ✗ Checking the status of all Submariner pods
 ✗ Pod "submariner-operator-578485964d-nkvlj" is not running. (current state is Pending)

 ✓ Checking Submariner support for the CNI network plugin
 ✓ The detected CNI network plugin ("OVNKubernetes") is supported
 ✓ Checking OVN version
 ✓ The ovn-nb database version 7.0.4 is supported
 ✓ Checking gateway connections
 ✓ Checking Submariner support for the kube-proxy mode
 ✓ Cluster is running with "OVNKubernetes" CNI which internally implements kube-proxy functionality
 ✓ Checking that firewall configuration allows intra-cluster VXLAN traffic

 ✓ Checking that services have been exported properly

Skipping inter-cluster firewall check as it requires two kubeconfigs. Please run "subctl diagnose firewall inter-cluster" command manually.

subctl version: v0.16.2

sh-4.4$ /tmp/new_subctl/bin/subctl diagnose all --kubeconfig /connection/kube-config/c0672c4c63/kubeconfig
Cluster "default-cluster"
 ✓ Checking Submariner support for the Kubernetes version
 ✓ Kubernetes version "v1.26.11+7dfc52e" is supported

 ✓ Non-Globalnet deployment detected - checking that cluster CIDRs do not overlap
 ✓ Checking DaemonSet "submariner-gateway"
 ✓ Checking DaemonSet "submariner-routeagent"
 ✓ Checking DaemonSet "submariner-metrics-proxy"
 ✓ Checking Deployment "submariner-lighthouse-agent"
 ✓ Checking Deployment "submariner-lighthouse-coredns"
 ✗ Checking the status of all Submariner pods
 ✗ Pod "submariner-operator-578555d5bb-mb7jn" is not running. (current state is Pending)

 ✓ Checking Submariner support for the CNI network plugin
 ✓ The detected CNI network plugin ("OVNKubernetes") is supported
 ✓ Checking OVN version
 ✓ The ovn-nb database version 7.0.4 is supported
 ✓ Checking gateway connections
 ✓ Checking Submariner support for the kube-proxy mode
 ✓ Cluster is running with "OVNKubernetes" CNI which internally implements kube-proxy functionality
 ✓ Checking that firewall configuration allows intra-cluster VXLAN traffic

 ✓ Checking that services have been exported properly

Skipping inter-cluster firewall check as it requires two kubeconfigs. Please run "subctl diagnose firewall inter-cluster" command manually.

subctl version: v0.16.2

Outputs for subctl gather
For Site 2
sh-4.4$ /tmp/new_subctl/bin/subctl gather --kubeconfig /tmp/local-kubeconfig
Cluster "local-config"
Gathering information from cluster "local-config"
 ✓ Gathering broker logs
 ✓ Gathering broker resources
 ✓ Found 2 endpoints in namespace "submariner-k8s-broker"
 ✓ Found 2 clusters in namespace "submariner-k8s-broker"
 ✓ Found 0 endpointslices by label selector "endpointslice.kubernetes.io/managed-by=lighthouse-agent.submariner.io" in namespace "submariner-k8s-broker"
 ✓ Found 0 serviceimports in namespace "submariner-k8s-broker"
 ✗ Gathering operator logs
 ✓ Found 2 pods matching label selector "name=submariner-operator"
 ✗ Error outputting current log for pod "submariner-operator-578485964d-nkvlj": error opening log stream: container "submariner-operator" in pod "submariner-operator-578485964d-nkvlj" is waiting to start: trying and failing to pull image
 ✓ Gathering operator resources
 ✓ Found 1 submariners in namespace "submariner-operator"
 ✓ Found 1 servicediscoveries in namespace "submariner-operator"
 ✓ Found 1 deployments by field selector "metadata.name=submariner-operator" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-gateway" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-metrics-proxy" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-routeagent" in namespace "submariner-operator"
 ✓ Found 0 daemonsets by label selector "app=submariner-globalnet" in namespace "submariner-operator"
 ✓ Found 1 deployments by label selector "app=submariner-lighthouse-agent" in namespace "submariner-operator"
 ✓ Found 1 deployments by label selector "app=submariner-lighthouse-coredns" in namespace "submariner-operator"
 ✓ Gathering connectivity logs
 ✓ Found 3 pods matching label selector "app=submariner-gateway"
 ✓ Found 6 pods matching label selector "app=submariner-routeagent"
 ✓ Found 3 pods matching label selector "app=submariner-metrics-proxy"
 ✓ Found 0 pods matching label selector "app=submariner-globalnet"
 ✓ Found 0 pods matching label selector "app=submariner-addon"
 ✓ Gathering connectivity resources
 ✓ Gathering CNI data from 6 pods matching label selector "app=submariner-routeagent"
 ✓ Gathering CNI data from 3 pods matching label selector "app=submariner-gateway"
 ✓ Gathering cable driver data from 3 pods matching label selector "app=submariner-gateway"
 ✓ Gathering OVN data from OVN kube pod "ovnkube-master-7xrzp"
 ✓ Found 0 gatewayroutes in namespace ""
 ✓ Found 0 nongatewayroutes in namespace ""
 ✓ Found 2 endpoints in namespace "submariner-operator"
 ✓ Found 2 clusters in namespace "submariner-operator"
 ✓ Found 3 gateways in namespace "submariner-operator"
 ✓ Found 0 clusterglobalegressips in namespace ""
 ✓ Found 0 globalegressips in namespace ""
 ✓ Found 0 globalingressips in namespace ""
 ✓ Gathering service-discovery logs
 ✓ Found 3 pods matching label selector "component=submariner-lighthouse"
 ✓ Found 6 pods matching label selector "dns.operator.openshift.io/daemonset-dns=default"
 ✓ Gathering service-discovery resources
 ✓ Found 0 serviceexports in namespace ""
 ✓ Found 0 serviceimports in namespace ""
 ✓ Found 0 endpointslices by label selector "endpointslice.kubernetes.io/managed-by=lighthouse-agent.submariner.io" in namespace ""
 ✓ Found 1 configmaps by label selector "component=submariner-lighthouse" in namespace "submariner-operator"
 ✓ Found 1 configmaps by field selector "metadata.name=dns-default" in namespace "openshift-dns"
 ✓ Found 0 services by label selector "submariner.io/exportedServiceRef" in namespace ""
Files are stored under directory "submariner-20240110101256/local-config"

For site 1
sh-4.4$ /tmp/new_subctl/bin/subctl gather --kubeconfig /connection/kube-config/c0672c4c63/kubeconfig
Cluster "default-cluster"
Gathering information from cluster "default-cluster"
 ✓ Gathering connectivity logs
 ✓ Found 3 pods matching label selector "app=submariner-gateway"
 ✓ Found 6 pods matching label selector "app=submariner-routeagent"
 ✓ Found 3 pods matching label selector "app=submariner-metrics-proxy"
 ✓ Found 0 pods matching label selector "app=submariner-globalnet"
 ✓ Found 0 pods matching label selector "app=submariner-addon"
 ✓ Gathering connectivity resources
 ✓ Gathering CNI data from 6 pods matching label selector "app=submariner-routeagent"
 ✓ Gathering CNI data from 3 pods matching label selector "app=submariner-gateway"
 ✓ Gathering cable driver data from 3 pods matching label selector "app=submariner-gateway"
 ✓ Gathering OVN data from OVN kube pod "ovnkube-master-r8sbp"
 ✓ Found 1 gatewayroutes in namespace ""
 ✓ Found 0 nongatewayroutes in namespace ""
 ✓ Found 2 endpoints in namespace "submariner-operator"
 ✓ Found 2 clusters in namespace "submariner-operator"
 ✓ Found 3 gateways in namespace "submariner-operator"
 ✓ Found 0 clusterglobalegressips in namespace ""
 ✓ Found 0 globalegressips in namespace ""
 ✓ Found 0 globalingressips in namespace ""
 ✓ Gathering service-discovery logs
 ✓ Found 3 pods matching label selector "component=submariner-lighthouse"
 ✓ Found 6 pods matching label selector "dns.operator.openshift.io/daemonset-dns=default"
 ✓ Gathering service-discovery resources
 ✓ Found 0 serviceexports in namespace ""
 ✓ Found 0 serviceimports in namespace ""
 ✓ Found 0 endpointslices by label selector "endpointslice.kubernetes.io/managed-by=lighthouse-agent.submariner.io" in namespace ""
 ✓ Found 1 configmaps by label selector "component=submariner-lighthouse" in namespace "submariner-operator"
 ✓ Found 1 configmaps by field selector "metadata.name=dns-default" in namespace "openshift-dns"
 ✓ Found 0 services by label selector "submariner.io/exportedServiceRef" in namespace ""
 ✓ Gathering broker logs
 ✓ Gathering broker resources
 ✓ Found 2 endpoints in namespace "submariner-k8s-broker"
 ✓ Found 2 clusters in namespace "submariner-k8s-broker"
 ✓ Found 0 endpointslices by label selector "endpointslice.kubernetes.io/managed-by=lighthouse-agent.submariner.io" in namespace "submariner-k8s-broker"
 ✓ Found 0 serviceimports in namespace "submariner-k8s-broker"
 ✗ Gathering operator logs
 ✓ Found 2 pods matching label selector "name=submariner-operator"
 ✗ Error outputting current log for pod "submariner-operator-578555d5bb-mb7jn": error opening log stream: container "submariner-operator" in pod "submariner-operator-578555d5bb-mb7jn" is waiting to start: trying and failing to pull image
 ✓ Gathering operator resources
 ✓ Found 1 submariners in namespace "submariner-operator"
 ✓ Found 1 servicediscoveries in namespace "submariner-operator"
 ✓ Found 1 deployments by field selector "metadata.name=submariner-operator" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-gateway" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-metrics-proxy" in namespace "submariner-operator"
 ✓ Found 1 daemonsets by label selector "app=submariner-routeagent" in namespace "submariner-operator"
 ✓ Found 0 daemonsets by label selector "app=submariner-globalnet" in namespace "submariner-operator"
 ✓ Found 1 deployments by label selector "app=submariner-lighthouse-agent" in namespace "submariner-operator"
 ✓ Found 1 deployments by label selector "app=submariner-lighthouse-coredns" in namespace "submariner-operator"
Files are stored under directory "submariner-20240110101322/default-cluster"

Gather logs
site1_gather_logs.zip
site2_gather_logs.zip

@dfarrell07
Alongside can you provide the Submariner versions compatibility with the OCP versions?
This matrix will be really helpful for us to easily decide on the required submariner version with the OCP versions that we upgrade to.

@dfarrell07
Any update on the above queries?

authors: BhavaniYalamanchili skitt

repo: submariner-io/submariner


text:
Directive variable conflicts with imported package name

Here:

package: https://github.com/suborbital/subo/blob/main/builder/context/buildcontext.go#L11
variable: https://github.com/suborbital/subo/blob/main/builder/context/buildcontext.go#L72

They shouldn't have the same name. It's down to shadowing rules to figure out what you mean by directive, which can be confusing, and can lead to unexpected bugs.

Hey @javorszky, I would like to know if there are other links for this because these are not opening, can you confirm, Thank you.

repo: suborbital/subo


text:
This should be tested in 0.10-6.x

Currently, both versions this is tested on in Travis (0.6 and 0.8) are unsupported, even in maintenance mode. Could this be instead tested in 0.10, 0.12, 4, 5, and 6 (all the currently supported versions)?
@substack I believe this might unmask many of the errors people are experiencing with this project.

Fixed in 1f7aa376bcf5d1a5a9580fdf0c4925d505938ff1

authors: isiahmeadows ljharb

repo: substack/node-resolve


text:
Do not intercept exceptions

It's weird that tape is intercepting exceptions and will report them as TAP error.
Exceptions are actually bugs in the test code and should not output TAP failures but just crash the test program instead.
This also makes it easier to test and debug tests themself as you can just use standard tools, like any standard uncaught exception tooling or any standard debugging thrown exception tooling.

For users trying to report uncaught exceptions as failed tests, I've created a library that does just that. More information here.

authors: Raynos ehmicky

repo: substack/tape


text:
Beta 6 Kaikoura fixes

A bunch of fixes stabilising Beta 6.

Cherry picked real fixes into beta-6-fixes. Continuing on branch 'kaikoura'

authors: michael oliver----

repo: substance/substance