-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PuneMetroLog #1879
Open
shubhamPatil-paycraft
wants to merge
2
commits into
ONDC-Official:main
Choose a base branch
from
shubhamPatil-paycraft:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
PuneMetroLog #1879
shubhamPatil-paycraft
wants to merge
2
commits into
ONDC-Official:main
from
shubhamPatil-paycraft:main
+9,091
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FLOW-1 (Ticket Booking)on_search1:
search2: "Payload is missing" on_search2:
select:
on_select:
init:
on_init:
confirm:
on_confirm:
status:
on_status:
FLOW-2 (Cancel Flow)on_search1:
search2:
on_search2:
select:
on_select:
init:
on_init:
confirm:
on_confirm:
soft_cancel:
confirm_cancel:
soft_on_cancel:
confirm_on_cancel:
NOTE
|
***@***.*** ***@***.***>@ajay ***@***.***>
…________________________________
From: sharique827 ***@***.***>
Sent: 08 January 2025 15:19
To: ONDC-Official/verification-logs ***@***.***>
Cc: Shubham Patil ***@***.***>; Mention ***@***.***>
Subject: Re: [ONDC-Official/verification-logs] PuneMetroLog (PR #1879)
FLOW-1 (Ticket Booking)
on_search1:
* schemaErr0: "/message/catalog/providers/0/time/range/start must match format "date-time""
* schemaErr1: "/message/catalog/providers/0/time/range/end must match format "date-time""
* timestamp_err: "Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format"
* message_id: "Message Id for /search and /on_search api should be same."
* code: "descriptor.code should be one of TICKET,PASS"
* provider_0_fulfillment_0type: "Fulfillment type should be 'ROUTE' in provider."
* Fulfillment 0:
* stops_1.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_9.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* provider_0_fulfillment_1type: "Fulfillment type should be 'ROUTE' in provider."
* Fulfillment 1:
* stops_2.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_4.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_7.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_8.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* stops_10.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* stops_12.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* provider_0_fulfillment_2type: "Fulfillment type should be 'ROUTE' in provider."
* fulfimment[2].stops: "stops are missing or empty at fulfillment[2]"
* provider_0_fulfillment_3type: "Fulfillment type should be 'ROUTE' in provider."
* fulfimment[3].stops: "stops are missing or empty at fulfillment[3]"
* provider_0_fulfillment_4type: "Fulfillment type should be 'ROUTE' in provider."
* fulfimment[4].stops: "stops are missing or empty at fulfillment[4]"
* provider_0_fulfillment_5type: "Fulfillment type should be 'ROUTE' in provider."
* fulfimment[5].stops: "stops are missing or empty at fulfillment[5]"
* provider_0_fulfillment_6type: "Fulfillment type should be 'ROUTE' in provider."
* fulfimment[6].stops: "stops are missing or empty at fulfillment[6]"
* provider_0_fulfillment_7type: "Fulfillment type should be 'ROUTE' in provider."
* fulfimment[7].stops: "stops are missing or empty at fulfillment[7]"
* provider_0_fulfillment_8type: "Fulfillment type should be 'ROUTE' in provider."
* fulfimment[8].stops: "stops are missing or empty at fulfillment[8]"
* provider_0_fulfillment_9type: "Fulfillment type should be 'ROUTE' in provider."
* fulfimment[9].stops: "stops are missing or empty at fulfillment[9]"
* provider_0_fulfillment_10type: "Fulfillment type should be 'ROUTE' in provider."
* fulfimment[10].stops: "stops are missing or empty at fulfillment[10]"
* provider_0_fulfillment_11type: "Fulfillment type should be 'ROUTE' in provider."
* fulfimment[11].stops: "stops are missing or empty at fulfillment[11]"
search2: "Payload is missing"
on_search2:
* on_search2: "Payload is missing"
select:
* tmpstmp: "Timestamp for /on_search api cannot be greater than or equal to /select api"
* item[0].item_id: "/message/order/items/id in item: I333-AND-DDI should be one of the /item/id mapped in previous call"
on_select:
* schemaErr0: "/message/order/provider/time/range/start must match format "date-time""
* schemaErr1: "/message/order/provider/time/range/end must match format "date-time""
* timestamp_err: "Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format"
* message_id: "Message Id for /select and /on_select api should be same."
* Fulfillment 0:
* stops_1.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_9.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* Fulfillment 1:
* stops_2.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_4.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_7.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_8.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* stops_10.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* stops_12.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* fulfimment[2].stops: "stops are missing or empty at fulfillment[2]"
* fulfimment[3].stops: "stops are missing or empty at fulfillment[3]"
* fulfimment[4].stops: "stops are missing or empty at fulfillment[4]"
* fulfimment[5].stops: "stops are missing or empty at fulfillment[5]"
* fulfimment[6].stops: "stops are missing or empty at fulfillment[6]"
* fulfimment[7].stops: "stops are missing or empty at fulfillment[7]"
* fulfimment[8].stops: "stops are missing or empty at fulfillment[8]"
* fulfimment[9].stops: "stops are missing or empty at fulfillment[9]"
* fulfimment[10].stops: "stops are missing or empty at fulfillment[10]"
* fulfimment[11].stops: "stops are missing or empty at fulfillment[11]"
* item[0].item_id: "/message/order/items/id in item: I333-AND-DDI should be one of the /item/id mapped in select"
init:
* tmpstmp: "Timestamp for /on_search api cannot be greater than or equal to /init api"
* item[0].item_id: "/message/order/items/id in item: I333-AND-DDI should be one of the /item/id mapped in previous call"
on_init:
* schemaErr0: "/message/order/provider/time/range/start must match format "date-time""
* schemaErr1: "/message/order/provider/time/range/end must match format "date-time""
* timestamp_err: "Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format"
* message_id: "Message Id for /init and /on_init api should be same."
* prvdrStartFormat: "Range.start Time Format is Invalid in /on_init"
* prvdrEndFormat: "Range.end Time Format is Invalid in /on_init"
* Fulfillment 0:
* stops_1.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_9.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* Fulfillment 1:
* stops_2.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_4.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_7.gps: "GPS coordinates must be precise upto six decimal places only in longitude."
* stops_8.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* stops_10.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* stops_12.gps: "GPS coordinates must be precise upto six decimal places only in latitude."
* fulfimment[2].stops: "stops are missing or empty at fulfillment[2]"
* fulfimment[3].stops: "stops are missing or empty at fulfillment[3]"
* fulfimment[4].stops: "stops are missing or empty at fulfillment[4]"
* fulfimment[5].stops: "stops are missing or empty at fulfillment[5]"
* fulfimment[6].stops: "stops are missing or empty at fulfillment[6]"
* fulfimment[7].stops: "stops are missing or empty at fulfillment[7]"
* fulfimment[8].stops: "stops are missing or empty at fulfillment[8]"
* fulfimment[9].stops: "stops are missing or empty at fulfillment[9]"
* fulfimment[10].stops: "stops are missing or empty at fulfillment[10]"
* fulfimment[11].stops: "stops are missing or empty at fulfillment[11]"
* payment_params: "params object must be present and non-empty in /on_init"
confirm:
* tmpstmp: Timestamp for /on_search api cannot be greater than or equal to /confirm api
* item[0].item_id: /message/order/items/id in item: I333-AND-DDI should be one of the /item/id mapped in previous call
* payments[0]_id: payments.id must be present in confirm
* payment_params_bank_code: params.bank_code must be present in /confirm
* payment_params_bank_account_number: params.bank_account_number must be present in /confirm
* payment_params_virtual_payment_address: params.virtual_payment_address must be present in /confirm
________________________________
on_confirm:
* schemaErr0: /message/order/provider/time/range/start must match format "date-time"
* schemaErr1: /message/order/provider/time/range/end must match format "date-time"
* timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
* message_id: Message Id for /confirm and /on_confirm api should be same.
* Fulfillment 0:
* stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* Fulfillment 1:
* stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* fulfimment[2].stops: stops are missing or empty at fulfillment[2]
* fulfimment[3].stops: stops are missing or empty at fulfillment[3]
* fulfimment[4].stops: stops are missing or empty at fulfillment[4]
* fulfimment[5].stops: stops are missing or empty at fulfillment[5]
* fulfimment[6].stops: stops are missing or empty at fulfillment[6]
* fulfimment[7].stops: stops are missing or empty at fulfillment[7]
* fulfimment[8].stops: stops are missing or empty at fulfillment[8]
* fulfimment[9].stops: stops are missing or empty at fulfillment[9]
* fulfimment[10].stops: stops are missing or empty at fulfillment[10]
* fulfimment[11].stops: stops are missing or empty at fulfillment[11]
* item[0].item_id: /message/order/items/id in item: I333 should be one of the /item/id mapped in /on_init
* payments[0]_id: payments.id must be present in on_confirm
* payment_params_bank_code: params.bank_code must be present in /on_confirm
* payment_params_bank_account_number: params.bank_account_number must be present in /on_confirm
* payment_params_virtual_payment_address: params.virtual_payment_address must be present in /on_confirm
* created_at: created_at must match with context.timestamp in /on_confirm
* updated_at: updated_at must match with context.timestamp in /on_confirm
________________________________
status:
* tmpstmp: Timestamp for /on_init api cannot be greater than or equal to /status api
________________________________
on_status:
* schemaErr0: /message/order/provider/time/range/start must match format "date-time"
* schemaErr1: /message/order/provider/time/range/end must match format "date-time"
* timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
* message_id: Message Id for /status and /on_status api should be same.
* item[0].item_id: /message/order/items/id in item: I333 should be one of the /item/id mapped in /on_status
* payment_params_bank_code: params.bank_code must be present in /on_status
* payment_params_bank_account_number: params.bank_account_number must be present in /on_status
* payment_params_virtual_payment_address: params.virtual_payment_address must be present in /on_status
FLOW-2 (Cancel Flow)
on_search1:
* schemaErr0: /message/catalog/providers/0/time/range/start must match format "date-time"
* schemaErr1: /message/catalog/providers/0/time/range/end must match format "date-time"
* timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
* message_id: Message Id for /search and /on_search api should be same.
* code: descriptor.code should be one of TICKET,PASS
* provider_0_fulfillment_0type: Fulfillment type should be 'ROUTE' in provider.
* Fulfillment 0:
* stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* provider_0_fulfillment_1type: Fulfillment type should be 'ROUTE' in provider.
* Fulfillment 1:
* stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* provider_0_fulfillment_2type: Fulfillment type should be 'ROUTE' in provider.
* fulfimment[2].stops: stops are missing or empty at fulfillment[2]
* provider_0_fulfillment_3type: Fulfillment type should be 'ROUTE' in provider.
* fulfimment[3].stops: stops are missing or empty at fulfillment[3]
* provider_0_fulfillment_4type: Fulfillment type should be 'ROUTE' in provider.
* fulfimment[4].stops: stops are missing or empty at fulfillment[4]
* provider_0_fulfillment_5type: Fulfillment type should be 'ROUTE' in provider.
* fulfimment[5].stops: stops are missing or empty at fulfillment[5]
* provider_0_fulfillment_6type: Fulfillment type should be 'ROUTE' in provider.
* fulfimment[6].stops: stops are missing or empty at fulfillment[6]
* provider_0_fulfillment_7type: Fulfillment type should be 'ROUTE' in provider.
* fulfimment[7].stops: stops are missing or empty at fulfillment[7]
* provider_0_fulfillment_8type: Fulfillment type should be 'ROUTE' in provider.
* fulfimment[8].stops: stops are missing or empty at fulfillment[8]
* provider_0_fulfillment_9type: Fulfillment type should be 'ROUTE' in provider.
* fulfimment[9].stops: stops are missing or empty at fulfillment[9]
* provider_0_fulfillment_10type: Fulfillment type should be 'ROUTE' in provider.
* fulfimment[10].stops: stops are missing or empty at fulfillment[10]
* provider_0_fulfillment_11type: Fulfillment type should be 'ROUTE' in provider.
* fulfimment[11].stops: stops are missing or empty at fulfillment[11]
________________________________
search2:
* search2: Payload is missing
________________________________
on_search2:
* on_search2: Payload is missing
________________________________
select:
* tmpstmp: Timestamp for /on_search api cannot be greater than or equal to /select api
* item[0].item_id: /message/order/items/id in item: I333-AND-BPI should be one of the /item/id mapped in previous call
________________________________
on_select:
* schemaErr0: /message/order/provider/time/range/start must match format "date-time"
* schemaErr1: /message/order/provider/time/range/end must match format "date-time"
* timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
* message_id: Message Id for /select and /on_select api should be same.
* Fulfillment 0:
* stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* Fulfillment 1:
* stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* fulfimment[2].stops: stops are missing or empty at fulfillment[2]
* fulfimment[3].stops: stops are missing or empty at fulfillment[3]
* fulfimment[4].stops: stops are missing or empty at fulfillment[4]
* fulfimment[5].stops: stops are missing or empty at fulfillment[5]
* fulfimment[6].stops: stops are missing or empty at fulfillment[6]
* fulfimment[7].stops: stops are missing or empty at fulfillment[7]
* fulfimment[8].stops: stops are missing or empty at fulfillment[8]
* fulfimment[9].stops: stops are missing or empty at fulfillment[9]
* fulfimment[10].stops: stops are missing or empty at fulfillment[10]
* fulfimment[11].stops: stops are missing or empty at fulfillment[11]
* item[0].item_id: /message/order/items/id in item: I333-AND-BPI should be one of the /item/id mapped in select
________________________________
init:
* tmpstmp: Timestamp for /on_search api cannot be greater than or equal to /init api
* item[0].item_id: /message/order/items/id in item: I333-AND-BPI should be one of the /item/id mapped in previous call
________________________________
on_init:
* schemaErr0: /message/order/provider/time/range/start must match format "date-time"
* schemaErr1: /message/order/provider/time/range/end must match format "date-time"
* timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
* message_id: Message Id for /init and /on_init api should be same.
* prvdrStartFormat: Range.start Time Format is Invalid in /on_init
* prvdrEndFormat: Range.end Time Format is Invalid in /on_init
* Fulfillment 0:
* stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* Fulfillment 1:
* stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* fulfimment[2].stops: stops are missing or empty at fulfillment[2]
* fulfimment[3].stops: stops are missing or empty at fulfillment[3]
* fulfimment[4].stops: stops are missing or empty at fulfillment[4]
* fulfimment[5].stops: stops are missing or empty at fulfillment[5]
* fulfimment[6].stops: stops are missing or empty at fulfillment[6]
* fulfimment[7].stops: stops are missing or empty at fulfillment[7]
* fulfimment[8].stops: stops are missing or empty at fulfillment[8]
* fulfimment[9].stops: stops are missing or empty at fulfillment[9]
* fulfimment[10].stops: stops are missing or empty at fulfillment[10]
* fulfimment[11].stops: stops are missing or empty at fulfillment[11]
* payment_params: params object must be present and non-empty in /on_init
confirm:
* tmpstmp: Timestamp for /on_search api cannot be greater than or equal to /confirm api
* item[0].item_id: /message/order/items/id in item: I333-AND-BPI should be one of the /item/id mapped in previous call
* payments[0]_id: payments.id must be present in confirm
* payment_params_bank_code: params.bank_code must be present in /confirm
* payment_params_bank_account_number: params.bank_account_number must be present in /confirm
* payment_params_virtual_payment_address: params.virtual_payment_address must be present in /confirm
on_confirm:
* schemaErr0: /message/order/provider/time/range/start must match format "date-time"
* schemaErr1: /message/order/provider/time/range/end must match format "date-time"
* timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
* message_id: Message Id for /confirm and /on_confirm api should be same.
* Fulfillment 0:
* stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* Fulfillment 1:
* stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* fulfimment[2].stops: stops are missing or empty at fulfillment[2]
* fulfimment[3].stops: stops are missing or empty at fulfillment[3]
* fulfimment[4].stops: stops are missing or empty at fulfillment[4]
* fulfimment[5].stops: stops are missing or empty at fulfillment[5]
* fulfimment[6].stops: stops are missing or empty at fulfillment[6]
* fulfimment[7].stops: stops are missing or empty at fulfillment[7]
* fulfimment[8].stops: stops are missing or empty at fulfillment[8]
* fulfimment[9].stops: stops are missing or empty at fulfillment[9]
* fulfimment[10].stops: stops are missing or empty at fulfillment[10]
* fulfimment[11].stops: stops are missing or empty at fulfillment[11]
* item[0].item_id: /message/order/items/id in item: I333 should be one of the /item/id mapped in /on_init
* payments[0]_id: payments.id must be present in on_confirm
* payment_params_bank_code: params.bank_code must be present in /on_confirm
* payment_params_bank_account_number: params.bank_account_number must be present in /on_confirm
* payment_params_virtual_payment_address: params.virtual_payment_address must be present in /on_confirm
* created_at: created_at must match with context.timestamp in /on_confirm
* updated_at: updated_at must match with context.timestamp in /on_confirm
soft_cancel:
* tmpstmp: Timestamp for /on_confirm api cannot be greater than or equal to /soft_cancel api
confirm_cancel:
* cancel: Payload is missing
soft_on_cancel:
* schemaErr0: /message/order/provider/time/range/start must match format "date-time"
* schemaErr1: /message/order/provider/time/range/end must match format "date-time"
* timestamp_err: Timestamp not in RFC 3339 (YYYY-MM-DDTHH:MN:SS.MSSZ) Format
* message_id: Message Id for /soft_cancel and /soft_on_cancel api should be same.
* order_id: order_id should be same as in /on_confirm
* Fulfillment 0:
* stops_1.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_9.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* Fulfillment 1:
* stops_2.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_4.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_7.gps: GPS coordinates must be precise upto six decimal places only in longitude.
* stops_8.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_10.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* stops_12.gps: GPS coordinates must be precise upto six decimal places only in latitude.
* fulfimment[2].stops: stops are missing or empty at fulfillment[2]
* fulfimment[3].stops: stops are missing or empty at fulfillment[3]
* fulfimment[4].stops: stops are missing or empty at fulfillment[4]
* fulfimment[5].stops: stops are missing or empty at fulfillment[5]
* fulfimment[6].stops: stops are missing or empty at fulfillment[6]
* fulfimment[7].stops: stops are missing or empty at fulfillment[7]
* fulfimment[8].stops: stops are missing or empty at fulfillment[8]
* fulfimment[9].stops: stops are missing or empty at fulfillment[9]
* fulfimment[10].stops: stops are missing or empty at fulfillment[10]
* fulfimment[11].stops: stops are missing or empty at fulfillment[11]
* item[0].item_id: /message/order/items/id in item: I333 should be one of the /item/id mapped in /on_cancel
* breakup: quote.breakup is missing
* price: price.value is missing in quote
* cancellation: cancellation is missing in /on_cancel
confirm_on_cancel:
* on_cancel: Payload is missing
NOTE
* Please use the correct format of json.
* Please remove signature from the paylaod.
@shubhamPatil-paycraft<https://github.com/shubhamPatil-paycraft>
—
Reply to this email directly, view it on GitHub<#1879 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BFWPBT2SLORZ7IMNI3Q443T2JTYENAVCNFSM6AAAAABUXFURF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZXGI2DGNRVGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
DISCLAIMER:-This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Paycraft Solutions Private Limited. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Note that Finally, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email.
|
@shubhamPatil-paycraft, it's a gentle reminder to provide updated logs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.