Unknown error
See original GitHub issueIm getting an “UNKNOWN” errorno -4094 Code:
figlet("Test", function(err, data) {
if (err) {
console.log(err);
return;
}
message.channel.send('```' + data + '```')
})```
Error:
`{ [Error: UNKNOWN: unknown error, open '//../fonts/Standard.flf']
errno: -4094,
code: 'UNKNOWN',
syscall: 'open',
path: '//../fonts/Standard.flf' }
`
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (6 by maintainers)
Top Results From Across the Web
iOS update and restore errors - Apple Support (SA)
If your device couldn't be restored and you get a message that "an unknown error occurred [error number]," use these steps.
Read more >Unknown error - WebDriver - MDN Web Docs
The unknown element error is a WebDriver error that occurs when an unspecified error occurs in the driver whilst processing a command.
Read more >Unknown Error. Code : -2145116137 - ManageEngine Pitstop
Hello, I'm having the exact same error on two patches. Any update on this issue could help me as well. Error: Unknown Error....
Read more >Unknown error - how to solve related issues - Opster
How to troubleshoot Elasticsearch/OpenSearch log "Unknown error" a detailed guide including background on ES concepts: bootstrap.
Read more >#UNKNOWN! error - Microsoft Support
The #UNKNOWN! error indicates a unknown data type that is not currently supported in this version of Excel. If you need to work...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Wait, is this being transpiled? If so, it probably is a Webpack config error of some sort, or at least a problem how the code is being transpiled. __dirname should resolve to “your-app/node_modules/figlet/lib/”, and it’s joined with “…/fonts”, which gives the directory to the fonts folder.
Another option may be to use the new “importable-fonts” that I added to the project. I haven’t yet tested these, which is why it’s not advertised. However, I’m adding them for use in front-end apps that get transpiled. The fonts are actually there, and I envision them being used like this:
Though again, I haven’t tested these yet due to some computer issues I’m having.
@cyberbobjr I have a hacky fix for it, Just delete all the fonts and importable-fonts you don’t use and it should fix the indexing. https://github.com/REAZN/figlet.js