I’m currently trying to use
django-storage-swift as a filestore in Sentry and almost have it working, but have identified one problem doing so. Right now, it looks like Sentry reads through the file in order to generate the checksum/blob identifiers, but does not
.seek(0) or rewind the file before passing it off to the storage. As a result, the storage client hangs because it’s at the end of the file. If I edit the storage client to do that, everything works beautifully.
Since I’m not familiar with this platform at all (never work in python/django basically), I’m unsure who’s responsibility this is; should Sentry be rewinding the file prior to passing it off to any storage mechanisms, or should the storage mechanism be rewinding the file prior to processing it?