Skip to content
This repository was archived by the owner on Mar 13, 2025. It is now read-only.

[$50] Failing to pay ticket #245

Closed
jmgasper opened this issue Nov 23, 2019 · 15 comments
Closed

[$50] Failing to pay ticket #245

jmgasper opened this issue Nov 23, 2019 · 15 comments

Comments

@jmgasper
Copy link
Collaborator

@afrisalyp - Another one that's failing is a ticket in a private repo.

The DB has this repo ID, challenge ID, number, and provider, but it seems to be failing to find the ticket:

debug: Enter ensureChallengeExists to scan an issue record
debug: Enter ensureChallengeExists. Number: 39
debug: Enter ensureChallengeExists. provider: github
debug: Enter ensureChallengeExists. repositoryId: 221569487
debug: Enter scanOne.
debug: scanOne. Error. TypeError: Cannot read property 'map' of undefined
debug: scanOne. Result.
debug:
error: Error happened in system
TypeError: Cannot read property 'count' of undefined
    at model.scan.exec (/topcoder-x-processor/utils/db-helper.js:67:29)
    at /topcoder-x-processor/node_modules/q/q.js:2059:17
    at runSingle (/topcoder-x-processor/node_modules/q/q.js:137:13)
    at flush (/topcoder-x-processor/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:132:7)
    at process._tickDomainCallback (internal/process/next_tick.js:219:9)
error: Error happened in process
TypeError: Cannot read property 'id' of undefined
    at handleIssueClose (/topcoder-x-processor/services/IssueService.js:482:51)
    at <anonymous>
    at runMicrotasksCallback (internal/process/next_tick.js:122:5)
    at _combinedTickCallback (internal/process/next_tick.js:132:7)
    at Immediate._tickDomainCallback (internal/process/next_tick.js:219:9)
    at runCallback (timers.js:810:20)
    at tryOnImmediate (timers.js:768:5)
    at processImmediate [as _immediateCallback] (timers.js:745:5)
error:  message=Cannot read property 'id' of undefined, stack=TypeError: Cannot read property 'id' of undefined
    at handleIssueClose (/topcoder-x-processor/services/IssueService.js:482:51)
    at <anonymous>
    at runMicrotasksCallback (internal/process/next_tick.js:122:5)
    at _combinedTickCallback (internal/process/next_tick.js:132:7)
    at Immediate._tickDomainCallback (internal/process/next_tick.js:219:9)
    at runCallback (timers.js:810:20)
    at tryOnImmediate (timers.js:768:5)
    at processImmediate [as _immediateCallback] (timers.js:745:5), logged=true
debug:
error: Error happened in system
@jmgasper
Copy link
Collaborator Author

Contest https://www.topcoder.com/challenges/30107828 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

@jmgasper
Copy link
Collaborator Author

Contest https://www.topcoder.com/challenges/30107828 has been updated - it has been assigned to afrisalyp.

This is an automated message for ghostar via Topcoder X

@afrisalyp
Copy link
Collaborator

Accidentally close this. Sorry. :D

@jmgasper
Copy link
Collaborator Author

Payment failed: [400]: Failed to update challenge. Detail: javax.ejb.EJBTransactionRolledbackException

This is an automated message for ghostar via Topcoder X

@afrisalyp
Copy link
Collaborator

I can't reproduce this issue.
But upgrading dynamoose is a possible solution.
dynamoose/dynamoose#248

Also, there are some missed return in reject code.

@afrisalyp
Copy link
Collaborator

afrisalyp commented Nov 23, 2019

package.json is updated.
So please clean the node-module and package-lock.json then npm install again when deploying it to prod.
Thanks.

@jmgasper
Copy link
Collaborator Author

Payment failed: [400]: Failed to update challenge. Detail: javax.ejb.EJBTransactionRolledbackException

This is an automated message for ghostar via Topcoder X

@jmgasper
Copy link
Collaborator Author

@afrisalyp - The cleaning of node modules is done on every deploy.

@jmgasper
Copy link
Collaborator Author

@afrisalyp - Testing this out, and the response data isn't getting properly logged:

error: Response Data: [object Object]

@afrisalyp
Copy link
Collaborator

@jmgasper - log fixed.

@jmgasper
Copy link
Collaborator Author

@afrisalyp - That's great, thanks! I've been able to capture what's happening and I've reported it to the team that handles the challenge API. Something's weird and it's only in prod, for some reason. It's throwing an odd SQLException in the challenge API. Hopefully they can fix it ASAP.

@afrisalyp
Copy link
Collaborator

Sounds good. Hope it'll be fixed soon.
Thanks.

@jmgasper
Copy link
Collaborator Author

Contest https://www.topcoder.com/challenges/30108384 has been created for this ticket.

This is an automated message for ghostar via Topcoder X

@jmgasper
Copy link
Collaborator Author

Contest https://www.topcoder.com/challenges/30108384 has been updated - it has been assigned to afrisalyp.

This is an automated message for ghostar via Topcoder X

@jmgasper
Copy link
Collaborator Author

Payment task has been updated: https://software.topcoder-dev.com/review/actions/ViewProjectDetails?pid=30108384

This is an automated message for ghostar via Topcoder X

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants