Yanlong Wang

Same issue here Version: 2.4.0

I thought this project was long deprecated. Even jinad is deprecated. @nan-wang Should we set this repo deprecated?

之前的评论我搬运过来。。 TypeScript 是有多重身份的， 作为js类型系统的TS； 作为ESNext的TS； 作为微软内部效率工具的TS； 还有作为已经被遗忘的，Angular的姊妹项目，ATScript 的TS。 很少有人理解刚才所说的最后一种身份。 如果没有ATScript和TypeScript的合并，TS拿不到今天的地位。 谷歌方面给TS加进来的就是这一个东西，AT，@，装饰器。 没有装饰器的TypeScript是没有灵魂的。 TypeScript真正有价值的地方其实在于装饰器和它背后，将类型信息由设计时带入运行时的Reflect.metadata. 尤雨溪显然就没有理解这点，所有Vue同温层的人，esbuild作者，不写分号的那一波人都有这个问题，没有运行时类型信息和装饰器的TypeScript，不是完整的TypesScript.

It turned out running `ffmpeg.exit()` during execution is not required to reproduce this issue. Just `ffmpeg.exit()` and reuse the same instance.

Moving the `Core.exit(1);` to last line may solve this issue while retaining its bizarre throwing behavior. But I think we need `ffmpeg.exit()` not throw any error And related behavior be...

If the current behavior that the ffmpeg instance after `exit` would not be useable again is expected, then it should be renamed to `destroy`

@sandfox Thanks.

I presume you are accessing from China. Perhaps it's the network connection? The `r.jina.ai` is deployed in Google Cloud, more specifically in the `us-central1` region.

@brendandburns @drubin @lchrennew Could you please release this fix(#882) on npm?

See https://github.com/jina-ai/reader/issues/14 Use the API for now.