Skip to content

fix association query #24586

fix association query

fix association query #24586

Triggered via push May 13, 2024 11:08
Status Failure
Total duration 13m 7s
Artifacts 1

e2e.yml

on: push
Matrix: e2e
Fit to window
Zoom out
Zoom in

Annotations

1 error, 62 warnings, and 5 notices
e2e (1*.js)
Process completed with exit code 1.
Type 'ExpectedFundsFilter' was added: server/graphql/schemaV2.graphql#L3531
Type 'ExpectedFundsFilter' was added
Field 'paymentProcessorUrl' was added to object type 'Order': server/graphql/schemaV2.graphql#L1176
Field 'paymentProcessorUrl' was added to object type 'Order'
Field 'paymentProcessorUrl' was added to interface 'Transaction': server/graphql/schemaV2.graphql#L1374
Field 'paymentProcessorUrl' was added to interface 'Transaction'
Field 'paymentProcessorUrl' was added to object type 'Credit': server/graphql/schemaV2.graphql#L8743
Field 'paymentProcessorUrl' was added to object type 'Credit'
Field 'paymentProcessorUrl' was added to object type 'Debit': server/graphql/schemaV2.graphql#L8888
Field 'paymentProcessorUrl' was added to object type 'Debit'
Argument 'expectedDateFrom: DateTime' added to field 'Account.orders': server/graphql/schemaV2.graphql#L560
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateTo: DateTime' added to field 'Account.orders': server/graphql/schemaV2.graphql#L565
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Enum value 'ORDER_REVIEW_OPENED' was added to enum 'ActivityAndClassesType': server/graphql/schemaV2.graphql#L14996
Adding an enum value may break existing clients that were not programming defensively against an added case when querying an enum.
Argument 'onlyExpectedFunds: Boolean' added to field 'Account.orders': server/graphql/schemaV2.graphql#L586
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Enum value 'ORDER_REVIEW_CLOSED' was added to enum 'ActivityAndClassesType': server/graphql/schemaV2.graphql#L14997
Adding an enum value may break existing clients that were not programming defensively against an added case when querying an enum.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'Account.orders': server/graphql/schemaV2.graphql#L587
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Enum value 'ORDER_DISPUTE_CREATED' was added to enum 'ActivityAndClassesType': server/graphql/schemaV2.graphql#L14998
Adding an enum value may break existing clients that were not programming defensively against an added case when querying an enum.
Enum value 'ORDER_DISPUTE_CLOSED' was added to enum 'ActivityAndClassesType': server/graphql/schemaV2.graphql#L14999
Adding an enum value may break existing clients that were not programming defensively against an added case when querying an enum.
Argument 'expectedDateFrom: DateTime' added to field 'Host.orders': server/graphql/schemaV2.graphql#L2234
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Enum value 'ORDER_PENDING_EXPIRED' was added to enum 'ActivityAndClassesType': server/graphql/schemaV2.graphql#L15008
Adding an enum value may break existing clients that were not programming defensively against an added case when querying an enum.
Argument 'expectedDateTo: DateTime' added to field 'Host.orders': server/graphql/schemaV2.graphql#L2239
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateFrom: DateTime' added to field 'Fund.orders': server/graphql/schemaV2.graphql#L15498
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'onlyExpectedFunds: Boolean' added to field 'Host.orders': server/graphql/schemaV2.graphql#L2260
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateTo: DateTime' added to field 'Fund.orders': server/graphql/schemaV2.graphql#L15503
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'Host.orders': server/graphql/schemaV2.graphql#L2261
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'onlyExpectedFunds: Boolean' added to field 'Fund.orders': server/graphql/schemaV2.graphql#L15524
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateFrom: DateTime' added to field 'PaymentMethod.orders': server/graphql/schemaV2.graphql#L4547
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'Fund.orders': server/graphql/schemaV2.graphql#L15525
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateTo: DateTime' added to field 'PaymentMethod.orders': server/graphql/schemaV2.graphql#L4552
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateFrom: DateTime' added to field 'Project.orders': server/graphql/schemaV2.graphql#L16367
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'onlyExpectedFunds: Boolean' added to field 'PaymentMethod.orders': server/graphql/schemaV2.graphql#L4573
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'PaymentMethod.orders': server/graphql/schemaV2.graphql#L4574
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateTo: DateTime' added to field 'Project.orders': server/graphql/schemaV2.graphql#L16372
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Enum value 'ORDER_REVIEW_OPENED' was added to enum 'ActivityType': server/graphql/schemaV2.graphql#L5747
Adding an enum value may break existing clients that were not programming defensively against an added case when querying an enum.
Argument 'onlyExpectedFunds: Boolean' added to field 'Project.orders': server/graphql/schemaV2.graphql#L16393
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Enum value 'ORDER_REVIEW_CLOSED' was added to enum 'ActivityType': server/graphql/schemaV2.graphql#L5748
Adding an enum value may break existing clients that were not programming defensively against an added case when querying an enum.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'Project.orders': server/graphql/schemaV2.graphql#L16394
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Enum value 'ORDER_DISPUTE_CREATED' was added to enum 'ActivityType': server/graphql/schemaV2.graphql#L5749
Adding an enum value may break existing clients that were not programming defensively against an added case when querying an enum.
Enum value 'ORDER_DISPUTE_CLOSED' was added to enum 'ActivityType': server/graphql/schemaV2.graphql#L5750
Adding an enum value may break existing clients that were not programming defensively against an added case when querying an enum.
Enum value 'ORDER_PENDING_EXPIRED' was added to enum 'ActivityType': server/graphql/schemaV2.graphql#L5759
Adding an enum value may break existing clients that were not programming defensively against an added case when querying an enum.
Argument 'expectedDateFrom: DateTime' added to field 'Bot.orders': server/graphql/schemaV2.graphql#L7395
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateTo: DateTime' added to field 'Bot.orders': server/graphql/schemaV2.graphql#L7400
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'onlyExpectedFunds: Boolean' added to field 'Bot.orders': server/graphql/schemaV2.graphql#L7421
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'Bot.orders': server/graphql/schemaV2.graphql#L7422
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateFrom: DateTime' added to field 'Collective.orders': server/graphql/schemaV2.graphql#L8151
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateTo: DateTime' added to field 'Collective.orders': server/graphql/schemaV2.graphql#L8156
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'onlyExpectedFunds: Boolean' added to field 'Collective.orders': server/graphql/schemaV2.graphql#L8177
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'Collective.orders': server/graphql/schemaV2.graphql#L8178
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateFrom: DateTime' added to field 'Event.orders': server/graphql/schemaV2.graphql#L9360
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateTo: DateTime' added to field 'Event.orders': server/graphql/schemaV2.graphql#L9365
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'onlyExpectedFunds: Boolean' added to field 'Event.orders': server/graphql/schemaV2.graphql#L9386
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'Event.orders': server/graphql/schemaV2.graphql#L9387
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateFrom: DateTime' added to field 'Individual.orders': server/graphql/schemaV2.graphql#L10351
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateTo: DateTime' added to field 'Individual.orders': server/graphql/schemaV2.graphql#L10356
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'onlyExpectedFunds: Boolean' added to field 'Individual.orders': server/graphql/schemaV2.graphql#L10377
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'Individual.orders': server/graphql/schemaV2.graphql#L10378
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateFrom: DateTime' added to field 'Organization.orders': server/graphql/schemaV2.graphql#L11313
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateTo: DateTime' added to field 'Organization.orders': server/graphql/schemaV2.graphql#L11318
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'onlyExpectedFunds: Boolean' added to field 'Organization.orders': server/graphql/schemaV2.graphql#L11339
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'Organization.orders': server/graphql/schemaV2.graphql#L11340
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateFrom: DateTime' added to field 'Vendor.orders': server/graphql/schemaV2.graphql#L12169
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateTo: DateTime' added to field 'Vendor.orders': server/graphql/schemaV2.graphql#L12174
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'onlyExpectedFunds: Boolean' added to field 'Vendor.orders': server/graphql/schemaV2.graphql#L12195
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'Vendor.orders': server/graphql/schemaV2.graphql#L12196
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateFrom: DateTime' added to field 'Query.orders': server/graphql/schemaV2.graphql#L13257
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedDateTo: DateTime' added to field 'Query.orders': server/graphql/schemaV2.graphql#L13262
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'onlyExpectedFunds: Boolean' added to field 'Query.orders': server/graphql/schemaV2.graphql#L13283
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
Argument 'expectedFundsFilter: ExpectedFundsFilter' added to field 'Query.orders': server/graphql/schemaV2.graphql#L13284
Adding a new argument to an existing field may involve a change in resolve function logic that potentially may cause some side effects.
e2e (3*.js)
Unexpected input(s) 'owner', 'repo', 'ref', valid inputs are ['route', 'mediaType']
e2e (0*.js)
Unexpected input(s) 'owner', 'repo', 'ref', valid inputs are ['route', 'mediaType']
e2e (2*.js)
Unexpected input(s) 'owner', 'repo', 'ref', valid inputs are ['route', 'mediaType']
e2e (1*.js)
Unexpected input(s) 'owner', 'repo', 'ref', valid inputs are ['route', 'mediaType']

Artifacts

Produced during runtime
Name Size
screenshots
682 KB