alexander-e-andrews opened a new issue, #21382:
URL: https://github.com/apache/superset/issues/21382
A clear and concise description of what the bug is.
Followed along with example deployment. Successfully passing in the first
token.
Afterwards it attempts to do getGuestTokenRefreshTiming and fails as
Buffer.from is not found
#### How to reproduce the bug
1. Follow along with example
2. Navigate to the webpage
### Expected results
Function runs without issue
### Actual results
`guestTokenRefresh.js:41 Uncaught (in promise) ReferenceError: Buffer is not
defined.
at getGuestTokenRefreshTiming (guestTokenRefresh.js:41:1)
at _callee3$ (index.js:137:1)
at tryCatch (runtime.js:63:1)
at Generator.invoke [as _invoke] (runtime.js:293:1)
at Generator.next (runtime.js:118:1)
at asyncGeneratorStep (asyncToGenerator.js:3:1)
at _next (asyncToGenerator.js:25:1)`
### Environment
- browser type and version: chrome 105.0.5195.102
- superset version: 2.0.0
- node.js version: v16.17.0
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [x] I have checked the superset logs for python stacktraces and included
it here as text if there are any.
- [x] I have reproduced the issue with at least the latest released version
of superset.
- [x] I have checked the issue tracker for the same issue and I haven't
found one similar.
### Additional context
Adding a buffer replacement to guestTokenRefresh.js like
npmjs.com/package/buffer removes the error
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
