Skip to content
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

"Oops. We could not send the error report." #1649

Closed
janpio opened this issue Feb 19, 2020 · 3 comments
Closed

"Oops. We could not send the error report." #1649

janpio opened this issue Feb 19, 2020 · 3 comments
Assignees
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug. topic: error
Milestone

Comments

@janpio
Copy link
Member

janpio commented Feb 19, 2020

When reproducing #1648 you can not submit an error report:

...
    at processTicksAndRejections (internal/process/task_queues.js:85:5)
[src\libcore\option.rs:1188:5] to
Oops. We could not send the error report.

Thanks a lot for your help! �🙏

More information with DEBUG=*:

...
  IntrospectionEngine:stdin     at Generator.next (<anonymous>)
  IntrospectionEngine:stdin     at fulfilled (C:\ProgramData\nvm\v12.6.0\node_modules\prisma2\build\index.js:2:877318)
  IntrospectionEngine:stdin     at processTicksAndRejections (internal/process/task_queues.js:85:5) +0ms
 ERROR  Oops, an unexpected error occured!
[src\libcore\option.rs:1188:5] to
Please help us improve Prisma 2 by submitting an error report.
Error reports never contain personal or other sensitive information.
Learn more: https://pris.ly/d/telemetry

┌─ Submit error report ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐  
│                                                                                                                                                                                                                                                                  │  
│ ⠋ Submitting error report                                                                                                                                                                                                                                        │  
│   No             Don't send error report                                                                                                                                                                                                                         │  
│                                                                                                                                                                                                                                                                  │  
└──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘  
  getos { platform: 'win32', libssl: undefined } +1m
  IntrospectionEngine:rpc starting introspection engine with binary: C:\ProgramData\nvm\v12.6.0\node_modules\prisma2\introspection-engine-windows.exe +1m
  IntrospectionEngine:rpc SENDING RPC CALL {"id":3,"jsonrpc":"2.0","method":"getDatabaseDescription","params":[{"schema":{}}]} +27ms
  IntrospectionEngine:rpc {
  IntrospectionEngine:rpc   jsonrpc: '2.0',
  IntrospectionEngine:rpc   error: {
  IntrospectionEngine:rpc     code: -32602,
  IntrospectionEngine:rpc     message: 'Invalid params: invalid type: map, expected a string.'
  IntrospectionEngine:rpc   },
  IntrospectionEngine:rpc   id: 3
  IntrospectionEngine:rpc } +14ms
  sendPanic Error: Error in RPC
  sendPanic  Request: {
  sendPanic   "id": 3,
  sendPanic   "jsonrpc": "2.0",
  sendPanic   "method": "getDatabaseDescription",
  sendPanic   "params": [
  sendPanic     {
  sendPanic       "schema": {}
  sendPanic     }
  sendPanic   ]
  sendPanic }
  sendPanic Response: {
  sendPanic   "jsonrpc": "2.0",
  sendPanic   "error": {
  sendPanic     "code": -32602,
  sendPanic     "message": "Invalid params: invalid type: map, expected a string."
  sendPanic   },
  sendPanic   "id": 3
  sendPanic }
  sendPanic Invalid params: invalid type: map, expected a string.
  sendPanic 
  sendPanic Wrote failed-getDatabaseDescription-20200219112925.md with debugging information.
  sendPanic Please put that file into a gist and post it in Slack.
  sendPanic 1. cat failed-getDatabaseDescription-20200219112925.md | pbcopy
  sendPanic 2. Create a gist https://gist.github.com/new
  sendPanic 
  sendPanic     at IntrospectionEngine.<anonymous> (C:\ProgramData\nvm\v12.6.0\node_modules\prisma2\build\index.js:2:883980)
  sendPanic     at Generator.next (<anonymous>)
  sendPanic     at C:\ProgramData\nvm\v12.6.0\node_modules\prisma2\build\index.js:2:877503
  sendPanic     at new Promise (<anonymous>)
[src\libcore\option.rs:1188:5] to
Oops. We could not send the error report.

Thanks a lot for your help! �🙏

C:\Users\Jan\Documents\throwaway\1093>

(preview 22)

@janpio
Copy link
Member Author

janpio commented Mar 19, 2020

Possibly related: #1869

@Jolg42
Copy link
Member

Jolg42 commented Mar 24, 2020

Fixed
See #1869 (comment)

Current error
Screen Shot 2020-03-24 at 16 37 01

@Jolg42 Jolg42 closed this as completed Mar 24, 2020
@janpio
Copy link
Member Author

janpio commented Mar 24, 2020

Close, but not perfect on Windows:

But as this is just a cosmetic thing, and the error was sent - I will create a new issue about this: #1923

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug. topic: error
Projects
None yet
Development

No branches or pull requests

4 participants