Include gate and udp instantiations in non-elaborated tree

@alaindargelas Need a little help in finishing this. Intent to have the gate and udp instantiations in the non-elaborated tree. I have managed to get most of it working. The issue I have is with setting udp::Udp_defn. Attached are the logs for the test that are impacted by this change.
Build#846.zip

Should the value for udp::Udp_defn be valid in the non-elaborated model?
For the elaborated model, should the value be set during elaboration using one of the bindXXX functions? I tried this but looks like the ElaboratorListener isn't tracking udp definitions. Also, should the definition itself be cloned for the elaborated model?

Appreciate some pointers to take this to finish line.

@hs-apotell, this is not coherent with the rest of the non-elaborated model. In the non-elaborated model, there are no instances of modules in modules. Why do you want instances of gates/udps? It is already present in the elaborated model (where it should be).
. Should the value for udp::Udp_defn be valid in the non-elaborated model?
The non-elaborated model has many incorrect bindings (Because elaboration is typically required to do correct binding). But this one is one that can be done correctly without elaboration as udps don't have parameters.
The binding needs to happen in Surelog::UhdmWriter. Not in ElaboratorListener for the non-elaborated model.
. For the elaborated model, should the value be set during elaboration using one of the bindXXX functions? I tried this but looks like the ElaboratorListener isn't tracking udp definitions. Also, should the definition itself be cloned for the elaborated model?
This is already done (in Surelog, not in ElaboratorListener):
Udp.log:
....
  |vpiPrimitive:
  \_udp: work@udp_body (work@udp_body_tb.udp), file:dut.sv, line:89:1, endln:89:22
    |vpiParent:
    \_module: work@udp_body_tb (work@udp_body_tb), file:dut.sv, line:84:1, endln:106:10
    |vpiDefName:work@udp_body
    |vpiName:udp
<EMAIL_ADDRESS>    |vpiUdpDefn:
    \_udp_defn: work@udp_body, line:1:1, endln:18:13

Elaboration is not an option for language server usage. User is working with just one file from a potentially larger design. Elaboration won't succeed for these use case. There are three options -

Use the non-elaborated model
Fall back to the AST, or
Use the antlr walker directly.

The non-elaborated model approach is little more useful in terms of functionality like go-to reference or declaration and definition. In my opinion, the non-elaborated model needs to be more complete with information on instances, comments, and macros (all of which is currently missing).

@hs-apotell, you can go ahead and implement in the non-elaborated model for all the items you mention.

@hs-apotell, you can go ahead and implement in the non-elaborated model for all the items you mention.

That's exactly what I am attempting. I might come back to you with specific questions along the way.


bug: reconcile on collection changes

Currently, we do not reconcile workloads when its parent collection changes.
Idea:

Add a watch to the collection resource

Depends on #67

@scottd018 is this actually dependent on #67 or can this be done in parallel?

@JefeDavis I believe they can be done in parallel. I think the better term would have been “affects” rather than “depends upon”. I just threw that issue out there before I forgot and didn't put much thought into it…ha

This will be highly dependent upon the implementation of #107 .  We will have to find a way to determine which component we are reconciling for which collection and/or find a way to tell the component to reconcile only when a specific collection changes.  These 2 tasks should likely be linked together as one.
The different scenarios that we came up with to link a component to a collection are:

GVK
Labels
Annotations
Namespace/Name

My preference would be 4, as that is how the controller is currently deciding how to reconcile against its resources today (see https://github.com/vmware-tanzu-labs/operator-builder/blob/main/internal/plugins/workload/v1/scaffolds/templates/controller/controller.go#L116 req.NamespacedName).

I had previously envisioned a component having a collectionRef section added to it's spec.  Something like this:
apiVersion: ingress.acme.com/v1alpha1
kind: Contour
metadata:
  name: contour-sample
spec:
  namespace: "ingress-system"
  envoyImage: "nginx:1.17"
  collectionRef:
    apiVersion: platforms.acme.com/v1alpha1
    kind: CloudNativePlatform
    name: cnp-sample
    namespace: cnp-system  # no namespace if cluster-scoped

However, maybe we can just solve this by making the collection the owner of the components.  The ownerReference takes care of all that for us.  And I think we want the behavior that comes with it anyway.


When i try to sign pdf

raceback (most recent call last):
File "pdfSigner.py", line 35, in
main()
File "pdfSigner.py", line 28, in main
'sha512'
File "/Users/nikhil.p/.local/share/virtualenvs/pdfSigner-bDNO_miT/lib/python3.7/site-packages/endesive/pdf/cms.py", line 320, in sign
return cls.sign(datau, udct, key, cert, othercerts, algomd, hsm)
File "/Users/nikhil.p/.local/share/virtualenvs/pdfSigner-bDNO_miT/lib/python3.7/site-packages/endesive/pdf/cms.py", line 311, in sign
contents = signer.sign(None, key, cert, othercerts, algomd, True, md, hsm)
File "/Users/nikhil.p/.local/share/virtualenvs/pdfSigner-bDNO_miT/lib/python3.7/site-packages/endesive/signer.py", line 66, in sign
'values': (cms.Time({'utc_time': core.UTCTime(signed_time)}),)
File "/Users/nikhil.p/.local/share/virtualenvs/pdfSigner-bDNO_miT/lib/python3.7/site-packages/asn1crypto/core.py", line 1677, in init
raise e
File "/Users/nikhil.p/.local/share/virtualenvs/pdfSigner-bDNO_miT/lib/python3.7/site-packages/asn1crypto/core.py", line 1669, in init
self.set(value)
File "/Users/nikhil.p/.local/share/virtualenvs/pdfSigner-bDNO_miT/lib/python3.7/site-packages/asn1crypto/core.py", line 4986, in set
raise ValueError('Must be timezone aware')
ValueError: Must be timezone aware
while constructing asn1crypto.core.UTCTime

The pypi version is old, try the git version

new version 1.2.1 uploaded


Doesnt work

All are invalid so dont try

Hello @Astracheatsdev, I don't own the website or anything I just made a client for it and you can check in closed issues. I think the website is pretty bad now considering it gives invalid accounts.


Improved documentation, Added a Contribute.md file

This is a reference to the issue #12
In this PR we:

Improved README.md
Added a Contribute.md file which contains the guildlines for making contibutions.

Relevant Screenshots

Team BigUhOh ( RGSoC'20)

Please remove "Project Admin" and "Mentor" sections. Also, try to squash your commits into one. I know we can do it from here but it is a great stuff to learn about git :)

Sure, I also made a new file "Guide.md" which mentions the guidelines to setup the project on local web server easily.

I've made a separate pr.


[Serverless] add isError flag to channelMessage

What does this PR do?
This PR adds IsError field to the ChannelMessage structure.
Before all message were set with status info but in some case, we want to tag message as error right away, for instance if we know that these are coming from stderr

Motivation
Set the correct level in message
Describe how to test/QA your changes
Unit test
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

Would it make sense to instead expose the full status field, so that any of the available levels can be set?

Would it make sense to instead expose the full status field, so that any of the available levels can be set?

Sure! I can do the modification, the only downside of that we could pass invalid status such as 'blablabla'
WDTY?

Good point! If there is no foreseeable need for more status options, what you have now in the PR might be better.


related repositories

This work is largely in support of Susan Celniker's work on IARPA Felix

turbomam/synbio-alignments

fork of https://github.com/beckyjackson/synbio-alignments
aligns sequences from Postgres against reference genome and assembly from merlot /data/iarpa/TE filesystem

turbomam/synbio-schema

for of https://github.com/cmungall/synbio-schema

turbomam/synbio-sheets
turbomam/synbio_bottomup


Resolvers are not being updated in AppSync (using Aurora)

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm install amplify
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
5.1.0
What operating system are you using?
Mac
Amplify Categories
api
Amplify Commands
push
Describe the bug
The resolvers are not being updated to the appsync when they are changed manually in Amplify directory under resolvers, both for new queries and existing queries.
Expected behavior
The resolvers all should be updated to the app sync
Reproduction steps

I have created the db using amplify api add-graphql-datasource
I then create a new query (or update an existing one) under schema.graphql
type Query {
listPortfoliosByFirm(firm: String!): [portfolio]
}
I add the 2 files of req and res in the resolvers
I update the StacksCustomResolvers
I amplify push --yes

Result: the query is added the datasource but the resolver is not updated - instead it shows the "Pets" example
GraphQL schema(s)
type Query {
  listPortfoliosByFirm(firm: String!): [portfolio]
}

input CreatePortfolioInput {
  firm: String!
  name: String!
  symbol: String!
  weight: Float
  customerID: Int
}

type portfolio {
  id: Int
  firm: String!
  name: String!
  symbol: String!
  weight: Float
  customerID: Int
}

input UpdatePortfolioInput {
  id: Int!
  firm: String
  name: String
  symbol: String
  weight: Float
  customerID: Int
}

type Mutation {
  deletePortfolio(id: Int!): portfolio
  createPortfolio(createPortfolioInput: CreatePortfolioInput!): portfolio
  updatePortfolio(updatePortfolioInput: UpdatePortfolioInput!): portfolio
}

type Subscription {
  onCreatePortfolio: portfolio @aws_subscribe(mutations: ["createPortfolio"])
}

schema {
  query: Query
  mutation: Mutation
  subscription: Subscription
}

Log output

# Put your logs below this line

Additional information
No response

I have encountered the similar problem.
In my case, I changed ~/amplifyapp/amplify/backend/api/amplifyapp/schema.graphql from
type Todo @model(
    mutations: {create: "create3", delete: "deleteTodo", update: null}
    timestamps: null
    subscriptions: null) {
  id: ID!
  name: String!
  description: String
}

to
type Todo @model(
    mutations: {create: "create4", delete: "deleteTodo", update: null}
    timestamps: null
    subscriptions: null) {
  id: ID!
  name: String!
  description: String
}

, then I tried both amplify codegen and amplify api gql-compile.
And both of them resulted into an unchanged ~/amplifyapp/src/graphql/mutations.ts
/* tslint:disable */
/* eslint-disable */
// this is an auto generated file. This will be overwritten

export const create3 = /* GraphQL */ `
  mutation Create3(
    $input: CreateTodoInput!
    $condition: ModelTodoConditionInput
  ) {
    create3(input: $input, condition: $condition) {
      id
      name
      description
    }
  }
`;
export const deleteTodo = /* GraphQL */ `
  mutation DeleteTodo(
    $input: DeleteTodoInput!
    $condition: ModelTodoConditionInput
  ) {
    deleteTodo(input: $input, condition: $condition) {
      id
      name
      description
    }
  }
`;

I found amplify mock api do the correct update which overwrote the mutations.ts, but I'm not sure if this is the correct behavior.


Resolve new linting errors

There's possibly been an update to the linting libraries that is causing errors. See #579 for an example.

I saw this in two PRs, thanks for fixing it!!


Change New Item/List Button Location

Instead of a separate button, consider adding an element to the list that says "Add [Item | List]".

This is not necessary because the CollectionMenu componen more elegantly allows for displaying reusable menus.


chore(master): release 0.2.0

:robot: I have created a release beep boop
0.2.0 (2023-01-20)
Features

derive clone and copy where possible (#5) (e95395e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/uggo-lol/ddragon/releases/tag/v0.2.0 :sunflower:


updates to include ray shutdown pass in atm_interp

Add in similar shutdown bypass for the second ISOFIT call in apply_oe if empirical_line or analytical_line is to be called.

Thanks! Integrated changes faithfully via #3


Fail to build on NixOS due to gnome-bluetooth

When i try to build, i get the following error:
evaluation aborted with the following error message: 'lib.customisation.callPackageWith: Function called without required argument "gnome-bluetooth" at /nix/store/3p6803sfb55m8xcdcsx2alayfqf6nphs-source/nix/default.nix:24'

this panel drives me nuts more and more but now i can't even rebuild my system without pinning the frickin flake

this panel drives me nuts more and more but now i can't even rebuild my system without pinning the frickin flake

What's your nix version?

What's your nix version?

NixOS 24.05

What's your nix version?

NixOS 24.05, Lix 2.91.0

Did you add a nixpkgs.follow in the hyprpanel flake call?

Did you add a nixpkgs.follow in the hyprpanel flake call?

Not the one you asked the question to, but yes I have this in my flake.nix, and still get the error:
    hyprpanel = {
      url = "github:Jas-SinghFSU/HyprPanel";
      inputs.nixpkgs.follows = "nixpkgs";
    };

Did you add a nixpkgs.follow in the hyprpanel flake call?

Not the one you asked the question to, but yes I have this in my flake.nix, and still get the error:

    hyprpanel = {

      url = "github:Jas-SinghFSU/HyprPanel";

      inputs.nixpkgs.follows = "nixpkgs";

    };

Try to remove it and rebuild

Try to remove it and rebuild

Doesnt make any difference :/ Still the same error

i'll try to fix this today fellow nerds

that should fix the issue. if it doesn't, please mention me again, preferably on discord

@orxngc I'm still experiencing this error. This issue should be reopened.

i will look into this again tomorrow then

it really should be fixed now

The error is still present on my end after 83d2aa6 :/

@orxngc Still there. Doesn't work either if I use the follows line or not

New user, I just installed and got the same issue, I guess it's not fixed yet.

@M0NsTeRRR please tell me if running nix run in the folder works

I've created a PR that worked for my config (I don't have anymore the error linked above)

Can some of you test my PR and see if it fixes for you (just use my repo instead)

Can some of you test my PR and see if it fixes for you (just use my repo instead)

Fixed

Yeah okay so the actual flake only work for unstable and not for stable. As I'm not a nix expert I don't know how to manage it :/

the Question is: can aylurs-gtk-shell build without the gnome-bluetooth dependency, because that's a hard no for me, due to the systemd dependency. Investigating.

Just to dot some I's and cross some T's. Everyone here who has removed inputs.nixpkgs.follows = "nixpkgs" from their hyprpanel input has also then updated their flake.lock and run a rebuild without cache and the --refresh flag (if just using nix build)

Hi everyone! I have just updated the documentation and tested it. Could you guys tell me if the error is still present if you follow the instructions in the docs? 💖

First of all, the mere inclusion of the nixpkgs overlay, makes it unable to build on 24.05, due to
error: evaluation aborted with the following error message: 'lib.customisation.callPackageWith: Function called without required argument "gnome-bluetooth" at /nix/store/zknqfdygdbl1fa6swpv9qnknfxgqkn2a-source/nix/default.nix:24'

(My flake here, private git server)
Second of all, I personally think we should wait until 24.11 drops. I have estimated for 24.11 to release in about a month due to the fact, that, previously, 23.11 has released at the end of November. Anyways, this is all up to the maintainers, if fix or wait, of course.


Use the ModifyFeature on Labels (DrawText) disappears the text

Hi all,
I'm new on working with OpenLayers and the ole-editor. I think I find a mistake in the ole-editor.
If I set a label with the DrawText-Function on the map and after that use the ModifyFeature to change that text, the text disappears and instead of the text it appears only a point.
I think there would be two possible solutions. The first one ist to disallow the modifying of text. I could delete the "wrong" text and draw a new one. The second solution could be the possible to really modifiy the text by using the drawtext-function.
I'm sorry, but by now I don't understand this software enough to do it on my own.
It would be great, if someone can help me.
Thanks a lot!
Michael

This appears to be a drawing issue, if you use the modify tool you can only modify the geometry. The text disappears. If you click the select tool and click the text "point" again, the text will redraw.

Closing since this project is not maintained any longer.
Please visit https://github.com/geops/ole2


MODBULKOPS-11 - BulkOperationController

MODBULKOPS-11 - BulkOperationController
Purpose
BulkOperationController should utilize capabilities of the BulkOperationService. Controller should provide the following endpoints: ControllerImplementationDetails.
Approach

Implemented controller logic
Created unit tests

Pre-Merge Checklist:
Before merging this PR, please go through the following list and take appropriate actions.

Does this PR meet or exceed the expected quality standards?

[ ] Code coverage on new code is 80% or greater
[ ] Duplications on new code is 3% or less
[ ] There are no major code smells or security issues

Does this introduce breaking changes?

[ ] Were any API paths or methods changed, added or removed?
[ ] Were there any schema changes?
[ ] Did any of the interface versions change?
[ ] Were permissions changed, added, or removed?
[ ] Are there new interface dependencies?
[x] There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

What other modules will these changes impact?
Do JIRAs exist to update the impacted modules?

[ ] If not, please create them
[ ] Do they contain the appropriate level of detail?  Which endpoints/schemas changed, etc.
[ ] Do they have all they appropriate links to blocked/related issues?

Are the JIRAs under active development?

[ ] If not, contact the project's PO and make sure they're aware of the urgency.

Do PRs exist for these changes?

[ ] If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment.  Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

INFO: api-lint: Using api-lint version: 1.1.4
INFO: api-lint: https://dev.folio.org/guides/api-lint/
INFO: api-lint: Assessing API description files: OAS
INFO: api-lint: Processing OAS 3.0 file: src/main/resources/swagger.api/bulk-operations.yaml
ERROR: api-lint:
---- Summary:
parsingResult.conforms: false
parsingResult.results.length: 1
Violation: Unresolved reference '#components/schemas/BulkOperationDto'
--------
validationResult.conforms: true
validationResult.results.length: 20
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
should have required property 'bulkOperations'
should have required property 'totalRecords'

Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should be boolean
Warning: should NOT have additional properties
Warning: should NOT have additional properties
--------

---- parsingResult:
Model: file://./src/main/resources/swagger.api/bulk-operations.yaml
Conforms: false
Number of results: 1

Level: Violation

- Constraint: http://a.ml/vocabularies/amf/core#unresolved-reference
  Message: Unresolved reference '#components/schemas/BulkOperationDto'
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/201/payload/application%2Fjson/unresolved
  Property:
  Range: [(40,16)-(41,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

---- validationResult:
ModelId: file://./src/main/resources/swagger.api/bulk-operations.yaml
Profile: OAS 3.0
Conforms: true
Number of results: 20

Level: Warning

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should be boolean
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Range: [(17,17)-(17,23)]
  Location: file://./src/main/resources/swagger.api/schemas/cell.json

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(46,0)-(47,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(54,0)-(55,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(82,0)-(83,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(90,0)-(91,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(98,0)-(99,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(130,0)-(131,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(138,0)-(139,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(146,0)-(147,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(173,0)-(174,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(181,0)-(182,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(189,0)-(190,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fstart/supportedOperation/post/startBulkOperation/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fstart/supportedOperation/post/startBulkOperation/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(215,0)-(216,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fstart/supportedOperation/post/startBulkOperation/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fstart/supportedOperation/post/startBulkOperation/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(230,0)-(231,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors/supportedOperation/get/getErrorsPreviewByOperationId/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors/supportedOperation/get/getErrorsPreviewByOperationId/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Range: [(256,0)-(257,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(297,0)-(298,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(305,0)-(306,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(313,0)-(314,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
should have required property 'bulkOperations'
should have required property 'totalRecords'

  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations/supportedOperation/get/getBulkOperationCollection/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations/supportedOperation/get/getBulkOperationCollection/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Range: [(333,0)-(334,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D/supportedOperation/get/getBulkOperationById/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D/supportedOperation/get/getBulkOperationById/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(366,0)-(367,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

ERROR: api-lint: There were processing errors. See list above.

Note: When those ERRORs are fixed, then any INFO and WARNING messages will be gone too. See Jenkins "Artifacts" tab for ApiLintReport.

INFO: api-lint: Using api-lint version: 1.1.4
INFO: api-lint: https://dev.folio.org/guides/api-lint/
INFO: api-lint: Assessing API description files: OAS
INFO: api-lint: Processing OAS 3.0 file: src/main/resources/swagger.api/bulk-operations.yaml
ERROR: api-lint:
---- Summary:
parsingResult.conforms: false
parsingResult.results.length: 1
Violation: Unresolved reference '#components/schemas/BulkOperationDto'
--------
validationResult.conforms: true
validationResult.results.length: 20
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
should have required property 'bulkOperations'
should have required property 'totalRecords'

Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should NOT have additional properties
Warning: should be boolean
Warning: should NOT have additional properties
Warning: should NOT have additional properties
--------

---- parsingResult:
Model: file://./src/main/resources/swagger.api/bulk-operations.yaml
Conforms: false
Number of results: 1

Level: Violation

- Constraint: http://a.ml/vocabularies/amf/core#unresolved-reference
  Message: Unresolved reference '#components/schemas/BulkOperationDto'
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/201/payload/application%2Fjson/unresolved
  Property:
  Range: [(40,16)-(41,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

---- validationResult:
ModelId: file://./src/main/resources/swagger.api/bulk-operations.yaml
Profile: OAS 3.0
Conforms: true
Number of results: 20

Level: Warning

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should be boolean
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Range: [(17,17)-(17,23)]
  Location: file://./src/main/resources/swagger.api/schemas/cell.json

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(46,0)-(47,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(54,0)-(55,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(82,0)-(83,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(90,0)-(91,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fcontent-update/supportedOperation/post/postContentUpdates/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(98,0)-(99,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(130,0)-(131,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(138,0)-(139,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview/supportedOperation/get/getPreviewByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(146,0)-(147,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(173,0)-(174,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(181,0)-(182,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fpreview%2Fdownload/supportedOperation/get/downloadPreviewByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(189,0)-(190,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fstart/supportedOperation/post/startBulkOperation/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fstart/supportedOperation/post/startBulkOperation/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(215,0)-(216,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fstart/supportedOperation/post/startBulkOperation/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Fstart/supportedOperation/post/startBulkOperation/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(230,0)-(231,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors/supportedOperation/get/getErrorsPreviewByOperationId/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors/supportedOperation/get/getErrorsPreviewByOperationId/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Range: [(256,0)-(257,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/400/payload/application%2Fjson/examples/example/default-example
  Range: [(297,0)-(298,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(305,0)-(306,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D%2Ferrors%2Fdownload/supportedOperation/get/downloadErrorsByOperationId/returns/resp/500/payload/application%2Fjson/examples/example/default-example
  Range: [(313,0)-(314,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
should have required property 'bulkOperations'
should have required property 'totalRecords'

  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations/supportedOperation/get/getBulkOperationCollection/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations/supportedOperation/get/getBulkOperationCollection/returns/resp/200/payload/application%2Fjson/examples/example/default-example
  Range: [(333,0)-(334,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should NOT have additional properties
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D/supportedOperation/get/getBulkOperationById/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2F%7BoperationId%7D/supportedOperation/get/getBulkOperationById/returns/resp/404/payload/application%2Fjson/examples/example/default-example
  Range: [(366,0)-(367,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

ERROR: api-lint: There were processing errors. See list above.

Note: When those ERRORs are fixed, then any INFO and WARNING messages will be gone too. See Jenkins "Artifacts" tab for ApiLintReport.

INFO: api-lint: Using api-lint version: 1.1.4
INFO: api-lint: https://dev.folio.org/guides/api-lint/
INFO: api-lint: Assessing API description files: OAS
INFO: api-lint: Processing OAS 3.0 file: src/main/resources/swagger.api/bulk-operations.yaml
ERROR: api-lint:
---- Summary:
parsingResult.conforms: false
parsingResult.results.length: 1
Violation: Unresolved reference '#components/schemas/BulkOperationDto'
--------
validationResult.conforms: true
validationResult.results.length: 1
Warning: should be boolean
--------

---- parsingResult:
Model: file://./src/main/resources/swagger.api/bulk-operations.yaml
Conforms: false
Number of results: 1

Level: Violation

- Constraint: http://a.ml/vocabularies/amf/core#unresolved-reference
  Message: Unresolved reference '#components/schemas/BulkOperationDto'
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/201/payload/application%2Fjson/unresolved
  Property:
  Range: [(40,16)-(41,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

---- validationResult:
ModelId: file://./src/main/resources/swagger.api/bulk-operations.yaml
Profile: OAS 3.0
Conforms: true
Number of results: 1

Level: Warning

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should be boolean
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Range: [(17,17)-(17,23)]
  Location: file://./src/main/resources/swagger.api/schemas/cell.json

ERROR: api-lint: There were processing errors. See list above.

Note: When those ERRORs are fixed, then any INFO and WARNING messages will be gone too. See Jenkins "Artifacts" tab for ApiLintReport.

INFO: api-lint: Using api-lint version: 1.1.4
INFO: api-lint: https://dev.folio.org/guides/api-lint/
INFO: api-lint: Assessing API description files: OAS
INFO: api-lint: Processing OAS 3.0 file: src/main/resources/swagger.api/bulk-operations.yaml
ERROR: api-lint:
---- Summary:
parsingResult.conforms: false
parsingResult.results.length: 1
Violation: Unresolved reference '#components/schemas/BulkOperationDto'
--------
validationResult.conforms: true
validationResult.results.length: 1
Warning: should be boolean
--------

---- parsingResult:
Model: file://./src/main/resources/swagger.api/bulk-operations.yaml
Conforms: false
Number of results: 1

Level: Violation

- Constraint: http://a.ml/vocabularies/amf/core#unresolved-reference
  Message: Unresolved reference '#components/schemas/BulkOperationDto'
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/201/payload/application%2Fjson/unresolved
  Property:
  Range: [(40,16)-(41,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

---- validationResult:
ModelId: file://./src/main/resources/swagger.api/bulk-operations.yaml
Profile: OAS 3.0
Conforms: true
Number of results: 1

Level: Warning

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should be boolean
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Range: [(17,17)-(17,23)]
  Location: file://./src/main/resources/swagger.api/schemas/cell.json

ERROR: api-lint: There were processing errors. See list above.

Note: When those ERRORs are fixed, then any INFO and WARNING messages will be gone too. See Jenkins "Artifacts" tab for ApiLintReport.

INFO: api-lint: Using api-lint version: 1.1.4
INFO: api-lint: https://dev.folio.org/guides/api-lint/
INFO: api-lint: Assessing API description files: OAS
INFO: api-lint: Processing OAS 3.0 file: src/main/resources/swagger.api/bulk-operations.yaml
ERROR: api-lint:
---- Summary:
parsingResult.conforms: false
parsingResult.results.length: 1
Violation: Unresolved reference '#components/schemas/bulkOperationDto'
--------
validationResult.conforms: true
validationResult.results.length: 1
Warning: should be boolean
--------

---- parsingResult:
Model: file://./src/main/resources/swagger.api/bulk-operations.yaml
Conforms: false
Number of results: 1

Level: Violation

- Constraint: http://a.ml/vocabularies/amf/core#unresolved-reference
  Message: Unresolved reference '#components/schemas/bulkOperationDto'
  Severity: Violation
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/web-api/endpoint/%2Fbulk-operations%2Fupload/supportedOperation/post/uploadCsvFile/returns/resp/201/payload/application%2Fjson/unresolved
  Property:
  Range: [(40,16)-(41,0)]
  Location: file://./src/main/resources/swagger.api/bulk-operations.yaml

---- validationResult:
ModelId: file://./src/main/resources/swagger.api/bulk-operations.yaml
Profile: OAS 3.0
Conforms: true
Number of results: 1

Level: Warning

- Constraint: http://a.ml/vocabularies/amf/validation#example-validation-error
  Message: should be boolean
  Severity: Warning
  Target: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Property: file://./src/main/resources/swagger.api/bulk-operations.yaml#/references/3/shape/schema/property/property/header/array/header/shape/schema/property/property/visible/scalar/visible/scalar_1
  Range: [(17,17)-(17,23)]
  Location: file://./src/main/resources/swagger.api/schemas/cell.json

ERROR: api-lint: There were processing errors. See list above.

Note: When those ERRORs are fixed, then any INFO and WARNING messages will be gone too. See Jenkins "Artifacts" tab for ApiLintReport.


Wrap Text [supplied] / Remove Hard Returns

Ref: Conversation #1588 / Tim

Ref: Conversation #3725 / Orebee

Ref: Conversation #4727 / Brian

Ref: Conversation #5053 / Stephen M.

https://twitter.com/LeanderrJ/status/800449714395041792

Ref: Conversation #4228 / Malcolm

Ref: Conversation #5489 / Engin

Ref: Conversation #5727 / Jonathan


pgscan: The operation has timed out

Hi,
we have updated our pgscan version from 1.2.0 to 1.3.1.
We did this mainly to use the functionality to send multiple dependents in one request (we did not update to the new ProGet 2022 yet).
Unfortunately, our pgscan calls are now running into timeouts.
We have projects which have up to 1500 npm dependencies. The default timeout of 100 seconds is not enough to handle this amount of dependents. Before the update, pgscan took 2-3 minutes to handle this amount of dependents.
Maybe you have already encountered this limitation?
I guess there could be two possible solutions:

Increase the timeout before the request gets send (but who knows what value would please anybody?)
Use appsettings where the request can be modified individually.

Please let me know what you think about this issue.

Hello,
Are the time-outs happening on the pgscan side, or is ProGet timing out (and then causing pgscan to fail)?
100 seconds does seem like a really long time, but there may be some performance issues with really large data sets due to some missing indexes.
With ProGet 2022, this should not be an issue as these indexes were added.... but especially if you witch to the pgscan identify command, which uses the new API. That works with signficantly larger datasets no problem.
Cheers,
Alana

Hi Alana,
the timeouts are on the pgscan side. Pgscan uses a WebRequest which has a default timeout of 100 seconds.
I tried the pgscan publish command on our test setup of ProGet 2022 and it is responding a lot faster than our live ProGet 6.0.11.
Unfortunately, we did not have time to have a detailed look at the new ProGet 2022 and therefore, we can not update ProGet for now.
Should we just continue to use an older version of pgscan in combination with the older ProGet version?

Thanks; the alternative is to increase the timeout in the pgscan code, but like you said, we don't know what it should be... In 2022, it will never never be that slow.
The other option is to add indexes to your PackageDependants table in production ProGet 6.0, but then you'll want to delete them before upgrading to ProGet 2022.

Thank you for your quick feedback.
We will try to update to ProGet 2022 as soon as possible.
Until then we will just use the older version of pgscan.

We upgradet to ProGet 2022.8 and are no longer encountering this problem.


Consumer Instance Owner error.

I find Consumer Instance Owner metrics in consumers never update.
For example,if i change the consumer,ConsumerGroupCommand.main(new String[]{"--bootstrap-server","xxxx","--group","consumer3","--describe"}); can update real time,but kafka-manager never update.

same problem +1


Version 3 Momentum PR #2

Because development has slowed down considerably, all v3 changes will be on this branch/PR. This means less waiting for PRs to go through and less worrying about potential merge conflicts. This is the second mass PR of what might be 3 to 5.
Review as needed, check often and commit as needed. Individual commits will be reported in the Vyxal chat room by the bot.
Merge conditions:

[X] JLine PR merged (merge conflicts can be handled if needed)
[x] Elements up to ẋ implemented

[x] Ŀ = Logarithm / scan fixedpoint [apply until a previous value is repeated, collecting intermediate results] / len(lhs) == rhs
[x] Ṁ = Modular; return every y th element of x. If y is zero, mirror: prepend x to its reverse. <lst/str, num>
[x]     / Matrix multiply <lst, lst> / regex fullmatch? <str, str>
[x] Ṅ = Join on nothing / integer partitions / first truthy integer where function
[x] Ȯ = Over
[x] Ṗ = Permutations
[x] Ṙ = Rotate left
[x] Ṡ = Vectorised sums / num to str / is numeric?
[x] Ṫ = a[:-1]
[x] Ẇ = Wrap a list in chunks of a certain length / <str, str> / first n truthy integers where function
[x] Ẋ = Carteisan product
[x] ι = range [0, length(lhs))
[x] κ = range [1, length(lhs)]
[x] ȧ = absolute difference / apply to neighbours [applies to windows of length 2] /
[x] ḃ = a % 2 / second half of string
[x] ċ = n choose k / <num, str> / set of chars in lhs == set of chars in rhs
[x] ḋ = dot product / convert a to bijective base b
[x] ė = reciprocal / remove whitespace
[x] ḟ = prime factors / remove non-alphabet characters
[x] ġ = group by consecutive items
[x] ḣ = a[0], a[1:]
[x] ŀ = transliterate / call b on c until a(c) is falsy
[x] ṁ = mirror
[x] ṅ = "\n".join(lhs) / pad with 0s to nearest positive multiple of 8 / if 1, push context variable n
[x] ȯ = Boolify
[x] ṗ = list partitions
[x] ṙ = rotate right
[x] ṡ = chunk by list of numbers / sort list by function
[x] ṫ = a[:-1], a[-1]
[x] ẋ = cartesian power /

[x] Some more modifiers implemented

[x] ᵃ = Reduce each overlap of size 2 by an element / number of truthy items by element
[x] ᵇ = Apply element without popping / remove duplicates by element
[x] ᶜ = reduce columns / map over suffixes
[x] ᵈ = Next element as a dyadic function
[x] ᵉ = Next two elements as a dyadic function
[x] ᶠ = Next three elements as a dyadic function
[x] ᶢ = Next four elements as a dyadic function
[x] ᴴ = Apply element only to the head of list
[x] ᶤ = find the index for the first element such that function evaluates as truthy
[x] ᶨ = Loop an element. Repeat until the results are no longer unique. Record intermediate results.
[x] ᵏ = Key. Map an element over the groups formed by identical items.
[x] ᶪ = Loop an element. Repeat until the results are no longer unique.
[x] ᵐ = maximum by element
[x] ⁿ = mimimum by element
[x] ᵒ = Outer Product / Table
[x] ᵖ = map over prefixes

[X] 2 byte number compression implemented (#887) (met)

Well done!


How would you like configurable UX settings to be implemented?

There are a series of UX changes that we have in mind for our Hypha instance; I could simply make the changes in the templates, but would like to avoid diverging too far from origin.  This means I'd rather implement this as configurable elements.
Just as an example: we don't want the "Apply" button to appear at the bottom of the home page.  There will also soon be a desire to change which sections appear in the application review.
I could see this done in a few ways:

Adding settings to base.py (so it can be configured via local.py or environment variable)
Adding settings to the wagtail admin (so it can be configured by an admin)

What do you all think, and is this kind of configuration something you would like to see added to the project?

Settings that it is likely staff need to change from time to time we normally put in Wagtail admin.
If the settings are something you set once, if they have important side effects etc. we put them in the settings file.
I think many UX changes that are more cosmetic could be good to have in Wagtail admin.
P.S. Better to post issue to main Hypha repo at https://github.com/HyphaApp/hypha/issues

Oh whoops -- I'm sorry for posting this here that was a misfire!
Thanks for the answer; I'll close the issue!


MatPaper Component Created

MatBlazor current uses the "elevation" css class that mdc provides, but I always thought  it could be a component, but creating a component only to wrap a css class didn't sound that good. But now I added new parameters and created the MatPaper component.
This component is based on the Paper component  of Material-UI because I couldn't find any documentation about such component in the Material Design Docs (I think it doesn't exits).
The parameters for the component are:

Elevation => 0 to 24 int values and default to 1 (Uses the "elevation" css class)
Rounded => Enable rounded surface
Outlined => Enable outlined surface

Which exits in the Paper component , and it is used everywhere in the Material Design Docs, even though it isn't documented the guide lines.
The styles for Outlined are the same in the Material Design Docs and in the Material-UI, so I think this parameter will be following the guide lines.
But the styles for Rounded is a little different, but I couldn't extract a good example of a rounded elevated component in the Material Design Docs, so I used the Material-UI style, which is border-radius:  4px;.
Observations:

This PR won't bring any breaking changes, but I changed the name of the "Elevation" page to "Paper".
I used the StyleMapper class and added var(--mdc-theme-surface, #ffffff); to the background-color of the component. I'm not sure if this is correct, so please let me know if this will cause any problems.

I hope this component makes a good difference and add new improvements to MatBlazor.  Thanks for the awesome library!

@lindespang  @SamProf  what are your thoughts on this PR? Looks like @EduVencovsky  created a convincing argument for the component and his code looks well done. I might suggest we need to do something about marking elevation as deprecated?

Hi I like this as well! As long as elevation page is gone I don’t see any need to explain  deprecation - maybe in bold within release notes perhaps? Good enough?
As mentioned there are no breaking changes for people that prev used the elevation css classes.
Well done @EduVencovsky and thanks for reaching out @enkodellc

Wow. that's great. I will make release this weekend.


yarn cache not found when using yarn workspaces

Description:
i'm trying to cache dependencies according to the instructions here. i always get yarn cache not found at the start of the run, no matter what.
my project is a monorepo using yarn workspaces. i have different workspaces under /packages/**, each of which has a package.json, as well as one at the top level.
there is also a single yarn.lock file, only at the top level.
Action version:
latest
Platform:

[ ] Ubuntu
[x] macOS
[ ] Windows

Runner type:

[x] Hosted
[ ] Self-hosted

Tools version:
github action running node 16 and whatever the version of yarn that comes with that is.
Repro steps:
here's my action config:
name: On PR to main

on:
  pull_request:
    branches:
      - main

jobs:
  ci:
    name: CI
    runs-on: ubuntu-latest
    steps:
      - name: 🛍 Checkout code
        uses: actions/checkout@v2

      - name: 💽 Setup Nodejs
        uses: actions/setup-node@v2
        with:
          node-version: 16
          cache: "yarn"

      - name: 🧩 Install dependencies
        run: yarn

      - name: 🧪 Run unit tests
        run: yarn unit-test

Expected behavior:
after the first run on a branch, subsequent runs should restore the yarn cache.
Actual behavior:
yarn cache not found

Hello @jhackett1. Thank you for your report. Could you please provide a public repository to reproduce the issue. Besides, could you please try to install dependencies via this yarn install --frozen-lockfile command.

Hello @jhackett1, just a gentle ping.


Better testing of GUI code

It's currently hard to write tests for GUI code, and as a consequence a lot of our Qt code is not covered by tests, which has resulted in quite a few issues in the past. It would be good to develop a framework and/or documentation for how to write good GUI tests, and then start requiring good GUI coverage in pull requests.

See also #5864


Build failure: uim

Steps To Reproduce
Steps to reproduce the behavior:

build uim

Build log
qtPreHook
Error: wrapQtAppsHook is not used, and dontWrapQtApps is not set.

Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.128, NixOS, 23.11 (Tapir), 23.11pre520855.3e52e76b70d5`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

https://github.com/NixOS/nixpkgs/pull/255091 seems to fix this problem.


[Bug] Cannot build kuberay with Go 1.16

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ray-operator
What happened + What you expected to happen
My environment: Mac Pro (Intel i5), go1.16.2 darwin/amd64
make build

This is very similar to https://github.com/kubernetes-sigs/controller-tools/issues/643. Hence, I doubt whether kuberay supports go 1.16 or not. If we cannot, I will update DEVELOPMENT.md.
My Solution: Update to 1.17.6
go install golang.org/dl/go1.17.6@latest
go1.17.6 download
export GOROOT=$(go1.17.6 env GOROOT)
export PATH="$GOROOT/bin:$PATH"
make build

Reproduction script
See above.
Anything else
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

cc @DmitriGekhtman

Let's just go the easy route here and assert in Development.MD that KubeRay requires Go 1.17.


Contributing docs and refactor dev packages

[x] Place dev and test packages inside setup python file.
[x] Provide contributing docs for pip and conda developers.

@jkimbo @Cito ready for review


fix issue #1747

Codecov Report

Merging #1749 (9ff5f39) into develop (ee29b28) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop    #1749      +/-   ##
===========================================
- Coverage    71.26%   71.25%   -0.01%
===========================================
  Files          457      457
  Lines        43448    43450       +2
===========================================
- Hits         30964    30962       -2
- Misses       10501    10504       +3
- Partials      1983     1984       +1

Flag
Coverage Δ

go-1.15
71.25% <100.00%> (+0.01%)
:arrow_up:

go-1.16
?

go-1.17
71.24% <100.00%> (+0.02%)
:arrow_up:

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

Impacted Files
Coverage Δ

encoding/gjson/gjson_implements.go
100.00% <100.00%> (ø)

net/gtcp/gtcp_pool.go
34.09% <0.00%> (-4.55%)
:arrow_down:

os/gspath/gspath_cache.go
84.21% <0.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 ee29b28...9ff5f39. Read the comment docs.


KubeNow CLI

Change content and motivation
This PR adds a kn command that wraps around a Docker container to make the installation of ansible and terraform easier for the user (and to solve tedious versioning problems with ansible and terraform). Nothing but kn is now needed to provision.
GitHub cross-links

Fixes:

Docs:

KubeNow CLI ready to fly 🙂 !!! I'd like @andersla to test and review, since this is a big change. To test:
bin/kn init my-deployment
cd my-deployment
# fill a template
../bin/kn ansible-playbook playbook/import-<gce|openstack>-image.yml
../bin/kn terraform get <host_cloud>
../bin/kn terraform apply <host_cloud>
../bin/kn ansible-playbook playbook/install-code.yml
# enjoy k8s!
../bin/kn terraform destroy <host_cloud>

@andersla good it's now live 🙂


Modify StreamingDataset to support passing process_group as construct…

…or arg
Description of changes:
Modify StreamingDataset to support passing process_group as a constructor argument. Currently, StreamingDataset assumes it should use the default process group; however, for certain use cases (e.g., Pipeline Distributed Parallel training), users may want to specify a different process group. This change accommodates this flexibility.
Issue #, if available:
N/A
Merge Checklist:
Put an x without space in the boxes that apply. If you are unsure about any checklist, please don't hesitate to ask. We are here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[X] I have read the contributor guidelines
[ ] This is a documentation change or typo fix. If so, skip the rest of this checklist.
[X] I certify that the changes I am introducing will be backward compatible, and I have discussed concerns about this, if any, with the MosaicML team.
[ ] I have updated any necessary documentation, including README and API docs (if appropriate).

Tests

[X] I ran pre-commit on my change. (check out the pre-commit section of prerequisites)
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate).
[X] I ran the tests locally to make sure it pass. (check out testing)
[ ] I have added unit and/or integration tests as appropriate to ensure backward compatibility of the changes.

Hey @jasonkrone, thanks for submitting this PR! So two things:

we're trying to reduce our dependency on torch.distributed because it can, at times, cause some messy issues with more complex parallelism schemes at scale
we are definitely looking to support other parallelism schemes, including pipeline parallelism
We recently added the replication arg, which duplicates samples across groups of consecutive GPUs. For your pipelining case, does that work for you? If it doesn't, is there a way to do this which doesn't involve sending in a ProcessGroup object? For example, you may be able to pass in a World object or add some functionality that enables pipelining.

Ah I see @knighton already discussed much of this with you on the community slack.

@jasonkrone is this PR still needed? Or was there a resolution from that community slack thread?

We can cancel this one! I didn't get a resolution, but i think that this is not likely to be a common issue for the community and therefore doesn't warrant the change.


#7: add proposal: allow cancellation peeking

or what's in a name...
in function of conversations of issue #7

Closing this PR as a won't do. Turns out we do not have a real use case any longer. See the discussion in #7 for more information and context.


Workspace Importer does not import execution mode

Bug description 🐞
We have a lot of workspaces that are using local execution mode in Terraform Cloud (i.e. where we're just using it for state management), however I've noticed that regardless of what the value is set to in Terraform Cloud, when the workspace gets imported it always gets imported as execution mode of remote.
Steps to reproduce

Create a workspace in Terraform Cloud with an execution mode set to Local
Use the Terrakube Workspace Importer to import the workspace using CLI-driven workflow
Check the execution mode in Terrakube and note it's set to remote

Expected behavior
Execution mode in Terrakube should reflect that from the workspace in Terraform Cloud.
Example repository
No response
Anything else?
No response

You are right we are not importing it, I will check which is the field in the api result and will include it


Add limitation to image upload in FAQ section.

We have a bug when uploading images with long names. The preview doesn't load, and the image cannot be uploaded to RTE. This is a backend limitation, and cannot be fixed in RTE.
Link to bug https://dynamicscrm.visualstudio.com/OneCRM/_workitems/edit/3000073/

Closing this PR because updates are being handled in the private repo.


does SHACL playground or shacl-js support jsonld 1.1?

JSON-LD is a serialization. SHACL-JS is an API that assumes that RDF graphs have already been loaded (in whatever format, using a 3rd party JavaScript API). So I don't see the connection.

the SHACL playground has an option to write the graphs as json-ld too. It gives an error when version 1.1 json-ld is used. However, it works when written in turtle format.

If you inspect the code on SHACL playground, you can see that we use a copy of rdflib.js. You could check if that library has been updated for JSON-LD 1.1 and then use your own variation of the code.


SIMSBIOHUB-542 Project Regions

Links to Jira Tickets
SIMSBIOHUB-542 Fix project region list column
SIMSBIOHUB-582 Error on survey study area save
Description of Changes

Updated the project list to display regions based on the survey study areas
Modified some bcgw / region / survey services to correctly map a selected map feature to the equivalent NRM region
Maps the NRM region by the geometry name to the survey_region table

Testing Notes

Should be able to select one or more survey study areas on the survey page
Project list should render a list of NRM regions (intersecting NRM regions for the survey study areas)
On survey save, the survey_regions will all be deleted and re-populated
Note: A project renders a list of NRM regions for ALL the surveys. If you only have one survey in a project the project region will be an exhaustive list

@MacQSL Pushed up a commit to fix that transition group error. The double stack was the solution, I just had the closing stack tag in the wrong spot.
It was:
<stack component={transitionGroup}>
    <...list>
    <add button>
<stack>

Its now:
<stack>
    <stack component={transitionGroup}>
       <...list>
    <stack>
    <add button>
<stack>

Probably the button is not a transition-able component, and so it was angry.


Persona 3: Dancing in Moonlight [PCSE01274]

Game summary

Game name: Persona 3: Dancing in Moonlight
Game serial: PCSE01274
Game version: 01.00

Vita3K summary

Version: v0.1
Build number: 1316
Commit hash: https://github.com/vita3k/vita3k/commit/d5378b8

Test environment summary

Tested by: IllusionMan1212
OS: Windows 10 Pro
CPU: AMD Ryzen 5 1600
GPU: NVIDIA GTX 1050Ti
RAM: 8 GB

Issues
Softlocks after sceFiber calls
Screenshots
None at the moment
Log
vita3k.log

The game is ingame+ now, only issues are halfnotes (the notes go halfspeed what causes that you can't complete a song without leaving half of the notes unplayed) + audio issues. 0 graphical glitches encountered

The game is ingame+ now, only issues are halfnotes (the notes go halfspeed what causes that you can't complete a song without leaving half of the notes unplayed) + audio issues. 0 graphical glitches encountered

kinda random, but do you have that captured build in particular, i was in the mood to test it, but it just crashes on the current one, and yours like isn't that new, maybe it's just me, i went to discord, but it's to be resolved yet

The game is playable now. No issues except for crackling audio were encountered.

For some reason I cant play the DLC song and even i do it just do a endless loop of loading screen when you select the DLC song

For some reason I cant play the DLC song and even i do it just do a endless loop of loading screen when you select the DLC song

That's weird, I have completed the game now, with 100% achievments and every music played (I didn't get the achievement for all trohies, but that's normal ). Maybe it is because of your PC

I encountered the same issue when I tried to play DLC songs. They show up just find, being added and preview normally but when you try and play it everything just stops.

@ZeroXTran @JoeysMemeTeam have you tried uninstalling DLCs and the game, and installing them again all at once as one zip package?
The feature of Persona 3: Dancing in Moonlight and Persona 5: Dancing in Starlight is that they have cross-DLCs (DLCs are the same for both games and can be played in both games respectively). It could be possible that Vita3K cannot read these DLCs correctly due to this feature in some cases.
DLC songs are working perfectly for me, but I've been installing both P3D and P5D as .zip packages containing not only game but also all DLCs (so I installed these DLCs twice, first time with P5D zip package, second time with P3D).

I dont know how to it been a long time.

I eventually figured it out with enough messing around and I believe I know how to re-create it. I believe it has to do with how inserted the DLC into the game through the direct DLC folder in the emulator directory rather than installing it within the emulator that caused this to happen. It also only worked as intended when I installed every piece of DLC individually for some reason. I only tried to configure the DLC through the directory way because I was not too sure what I was doing tbh, but I get it now. Not sure if @ZeroXTran was doing it the same way that caused this to happen for them too. But now that I'm playing the game I've only add some weird texture glitching at seemingly random points and a small frame drops in the room sections. Besides that, and the previous known audio glitches, the game is working perfectly well as intended for me.

This is not playable, audio issues are major for a dancing game

https://github.com/Vita3K/Vita3K/pull/2668 fixed audio issues

Chart doesn't restart properly when pressing retry in the middle of a song, otherwise runs perfectly after shaders are compiled
https://www.youtube.com/watch?v=VaEnNM94PDE
Tested by Me on Steam Deck, SteamOS 3.4.8, Vita 3K 3258, P3D PCSE01274 v1.0.0 + All DLC

Chart doesn't restart properly when pressing retry in the middle of a song, otherwise runs perfectly after shaders are compiled https://www.youtube.com/watch?v=VaEnNM94PDE Tested by Me on Steam Deck, SteamOS 3.4.8, Vita 3K 3258, P3D PCSE01274 v1.0.0 + All DLC

Can confirm, same happens to me on Steam Deck as well. Workaround: end the song and then start it again instead of restarting right away.

On top of https://github.com/Vita3K/Vita3K/issues/2705, I've had a couple of instances were audio broke and went super garbled, forcing a restart. This is pretty rare and seems to happen at random.
I've also had a couple of instances of textures going garbled, which also persists until a restart. This is also pretty rare and random, but always seems to start in the "SOCIAL" menu.
I've been using OpenGL because Vita3k Vulkan is busted on Linux/RADV. This can happen regardless of whether "Disable surface sync" is enabled.

On top of Vita3K/Vita3K#2705, I've had a couple of instances were audio broke and went super garbled, forcing a restart. This is pretty rare and seems to happen at random.
I've also had a couple of instances of textures going garbled, which also persists until a restart. This is also pretty rare and random, but always seems to start in the "SOCIAL" menu.
I've been using OpenGL because Vita3k Vulkan is busted on Linux/RADV. This can happen regardless of whether "Disable surface sync" is enabled.

Can confirm as well. I've encountered this issue on Desktop and Steam Deck too. Texture garble is actually not persistent and may go away by itself on the next song start. Audio, on the other hand, does not.

i know im late to this but my issue isnt the audio breaking or stuff getting garbled the song just completely stops even though the dancing continues but i get no notes no scrachs fever time etc cuz the song itself just freezes but the talking from the characters and the dancing continues its happend on both mass destruction and wiping all out idk whats going on but i figured id put this here

As of Vita3k version 3529 the game seems to be entirely broken. I'm on Linux (SteamOS 3.5.7). Game used to work mostly fine barring a couple of issues which were reported in my earlier comment. Now under Vulkan, the game crashes SteamOS after the title screen. Under OpenGL, the game just becomes a slideshow instead (1fps or less), which is slightly better, but still unplayable. None of the other settings seem to make a difference. Tomorrow I'll get some logs and try to find when the regression happened.

Can confirm that it is still happening on Vulkan, on 3571 , but OpenGL is playable just fine for me on Steam Deck, albeit occasional first time shader stutters

Working on 3578 on OpenGL so far, when running on Vulkan I was getting a crash after the title screen.

EPILEPSY WARNING FOR ANYONE SEEING THIS
idk how much other tracks this happens on, but i got the game to run just fine, but for battle hymn of the soul there is a LOT of graphical errors and flashing. this is on opengl, idk how it acts with vulkan or with tweaking the graphics settings (this is only a small portion of it and i had to scale it down to 480p cuz github is poopyhead and i cant upload more than 10 mb)
https://github.com/Vita3K/compatibility/assets/163798443/8253a701-c870-4c63-ae06-26f3901e5497

Hey, so there's a problem with Mali drivers, for some reason the game just looks like this

game fails to boot and emulator stops responding
when i try to open the game what i described above happens, specifically on vulkan, when on opengl the emulator doesn't stop responding but the game still does not boot.
i've even tried multiple vita3k builds (risked getting a virus trying to find old builds XDD) and the same happens

vita3k log
vulkan: vita3k.log
opengl: vita3k.log

vita3k version
0.2.0 3629-3f62275b

system specs
OS: Windows 11
CPU:11th Gen Intel(R) Core(TM) i5-1135G7
RAM: 24gb
GPU(Integrated): Intel(R) Iris(R) Xe Graphics (driver version: <IP_ADDRESS>71)

screenshots

emulator not responding


Decode of the Toggle command doesn't look right

I checked the decode function and it seems that it will put both Level and ToggleCount from the same part of the string, and also the check for ToggleRate seems wrong. I don't have a way to actually test it, but I was porting it to C# and it looked inconsistent.

You found a bug alright. Thank you.
I order to make the decode function, I copied & pasted the generate function and reverse engineered it. I never quite fixed that if statement it seems. I'll fix it as soon as possible.

I also never made a way to distinguish between level and toggleCount. My bad.

Actually, now that I look back at the UPB PDF, toggle cannot accept a level setting at all. Patches have been released patches for upb and upb-cli. Thank you again for spotting this.

BTW, you can test it with upb-cli. Simply generate a command and then decode it. It should have the same output to the input. If you need help working with that please post an issue there.

Nice, thank you! Btw, do you have a link to that UPB PDF?

At the bottom of the README there is  a link called "Tech Specs." That has the UPB protocol PDF, the PIM PDF, and the command wizard.
Also, when you are done with the C# implementation and if decide the to open source it, it would be nice if you could drop a link to it here. I would like to watch it, as your bugs and UPB protocol inconsistencies (like the one you brought up) could apply to my code too.
Also note that your work will be a derivative of mine. I am using the Apache license, which has a few minor rules about attribution and changes. See the redistribution section from here: http://www.apache.org/licenses/LICENSE-2.0
Good luck! It's nice to know that someone is using my work.

On Jan 13, 2015, at 10:46 PM, "Hakan Lindestaf"<EMAIL_ADDRESS>wrote:
Nice, thank you! Btw, do you have a link to that UPB PDF?
—
Reply to this email directly or view it on GitHub.

Ah, thanks..
That's fine, but I haven't copied your code, I was just looking at it to learn how you interpreted different parts of the protocol (like the variable toggle parameters). I guess I misspoke about "porting it", I meant I'm writing a C# port for the UPB protocol.

FYI here's my implementation of the UPB protocol in C#: https://github.com/iostorm/iostorm/blob/master/CorePlugins/UpbPim.cs

Cool! You should remove line 95. That was the error uncovered in this issue. Level cannot be used with the toggle command.

Thanks for the feedback, I left that part as-is in my code because I wanted to see if I had misinterpreted the specification compared to your implementation. A recommendation on your code, you have byte1-4 and then "fullbytes". The byte 1-4 are actually "half bytes", called nibbles. You may want to update your code to make it more clear. I also recommend bit-wise operations instead of the large if-statements in your decode function, makes for more robust code.


Two-color warning icon

Describe the desired behavior
Would love to see an icon like this that takes theme.palette.warning.main as its background color, and theme.palette.warning.dark as its foreground color, by default under both light and dark themes.

Describe the current behavior
Not offered by default. The default yellow gives a light yellow that is inaccessible (contrast less than 2)

Is this request related to a current issue?
Part of the A11y initiative
Additional Context

Only this icon is in urgent need as it is used extensively across Eaton to convey the idea of "warning". But I can see in the future how we might want to support additional icons like this outlined format

The icon shape come directly from Material Design's warning icon.

@huayunh All of our icons share a contrast colors, we haven't added any specific contrast color override for a single icon.

I don't understand. This is a feature request to write a new component.


Use granules closer to the middle of the disk

A feature of Disk Extended Color Basic (DECB) is that it prefers to use granules that are closer to the file allocation table and directory entries (track 17) before using granules that are closer to the outer edges of the disk. This makes sense, since it means stepping the read/write head less frequently after reading the file system data. Currently, the assembler will do a search for free granules starting at granule 0 (the first track). While this isn't an issue when using virtual files, on real media, there may be a noticeable delay when loading data from disk, since the read/write head needs to step a lot in order to read the granule data. The purpose of this feature request is to enable the same behavior in the assembler for populating granules that is seen when using DECB.

Looking at the Disk Basic Unravelled series, it looks like Disk Basic alternates sides between track 17 (FAT + directory entry track) when allocating granules. It starts at track 16, which are granules 32 and 33 (remember each track stores 2 granules, each granule is a half track long). So when granules 32 and 33 are filled, it moves to track 18 and checks to see if granules 34 and 35 are empty. Then it moves to granule 30 and 31, then 36 and 37, moving back and forth until it hits the outermost granules on the disk. So the granule allocation strategy merely needs to start close and move outwards.
Looking at granule allocation used by the virtual file system so far, it looks like the simplest way to implement this is to create a list of granule numbers that represent the order in which to fill granules on disk. So for the above method, the list would look like this:
granule_fill_order = [32, 33, 34, 35, 30, 31, 36, 37, ...]

It may be a good idea to be able to toggle this strategy on and off.


ratelimit adaptations

Created on_request_hook for vManageSession and vManageAuth which allows to attach custom user function which will be executed right before request is sent to vmanage.
Hooks can be assigned at class level (will attach to every new instance) or can be assigned at instance level.
Added ratelimit utility module which demonstrates how global ratelimiting using on_request_hook can be implemented:
from vmngclient.utils.ratelimit import ratelimit, on_request_throttle
ratelimit(100)
vManageSession.on_request_hook = on_request_throttle
vManageAuth.on_request_hook = on_request_throttle

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/140


feat: Adds more convenient methods for notifications and its options

Success, Danger, Info, Warning
Exposes dismissable and dismissDelay options

Codecov Report

Merging #12 into master will increase coverage by 1.20%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
+ Coverage   72.00%   73.21%   +1.20%
==========================================
  Files          53       53
  Lines         768      769       +1
  Branches      119      119
==========================================
+ Hits          553      563      +10
+ Misses        215      206       -9

Impacted Files
Coverage Δ

...insights-common-typescript/src/utils/AlertUtils.ts
100.00% <100.00%> (+21.42%)
:arrow_up:

...ages/insights-common-typescript/src/store/index.ts
92.30% <0.00%> (+46.15%)
:arrow_up:

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 7ecd19e...95bde30. Read the comment docs.


Add ability to record availability for games

Data model:

Id (unique Id for record)
TeamId (the team of the game/player)
GameId (the game the player is available for)
UserId (the user saying available)
PlayerId (the player)
Available (available or not)

API routes:

POST /api/Available/{teamId}/{gameId}/{playerId}
PATCH /api/Available/{id}
DELETE /api/Available/{id}
GET /api/Available/{teamId}/{gameId}


Use Flemish Region instead of Flanders

Is official name for that ISO code: https://en.wikipedia.org/wiki/ISO_3166-2:BE#Regions Made this edit on github.com, haven't rerun anything.

I verified these changes, these were successfully integrated in the new description.csv