mythrnr

Thanks your message. Yes, I can fix xrefs manually. But this process is in an automation, and this kind of PDF is uploaded by users in rare cases. In debugging,...

Please excuse the delay in replying. I'm guessing that the viewer ignores or doesn't handle xref sections as strictly as it should, since they open fine in the viewer. I...

Thank you so much for fixing that! PDFs with broken xrefs like this are probably really rare cases, so I can't allege that you should spend the effort to parse...

Same error occurred in docker container (golang:1.10.2-alpine3.7). Of course I use the command `rizla main.go`, I think `rizla run main.go` is simply mistake. :)

I got same issue. This is probably an issue with tracing-attributes `0.1.29`. Adding `tracing-attributes = "=0.1.28"` to Cargo.toml to lock the version should solve it.

This was not fixed in `tracing-attributes 0.1.30`, so I fixed it. https://github.com/async-graphql/async-graphql/pull/1728

I'm also waiting for this PR to be reviewed. @sunli829 , what do you think about this PR?

@loverustfs Sorry for the late response. I’ve signed the CLA. I’ve also fixed the JSON key you pointed out, so could you please take another look?

@yohanleb I missed your reply. If you're using `rustfs/rustfs:latest` (digest: `sha256:8e467b32af3ff83e70c70dddb0c36b5e611f46e89a3075db8770aea4f30b2fe3`), bucket notifications don’t work — at least in my environment. It seems you’ll need to wait for the next...