Indeterminacy of the `mime` Package in Go: Trust But Verify
Posted originally in my blog: https://lazy.bearblog.dev/go-mime-wtf/
Background
One weekend, I decided to write a Telegram bot for myself to automate to-do or shopping lists.
The idea is simple. I send the bot a list of items to buy, and it creates a webpage with checkboxes that I can tick off while holding my phone in one hand and a shopping basket in the other.
The bot was written pretty quickly, but then I wanted to experiment with OpenAI's Whisper model. So, I decided to add speech recognition to my application.
Now, the program works as follows:
- I send the bot a voice message like this: "buy a kilogram of potatoes, a bunch of dill, a head of cabbage, a couple of beers, oh, don't need the cabbage, we have it"
- The bot recognizes the speech and creates a page with checkboxes:
[ ] potatoes - 1 kg [ ] dill - 1 bunch [ ] beer - 2 bottles
Now, about the article. In go-openai, you can send audio using the openai.AudioRequest structure, which allows you to specify an audio data stream in the Reader field or a file path in the FilePath field. Well, I thought these fields were mutually exclusive, but it turns out you need to specify FilePath even when using an audio stream. The API probably uses this to determine the stream type.
On the Telegram side, we receive a tgbotapi.Voice structure, which has a MimeType field. For voice messages, it is audio/ogg, but it could easily change in the future.
So, we have the MIME type of the audio stream, and we need to determine the file extension from it, creating a file name to ensure the OpenAI API doesn't complain about an unknown file type.
What Could Be Simpler?
The code seems trivial:
extensions, err := mime.ExtensionsByType(mimeType) if err != nil { return err } if len(extensions) == 0 { return fmt.Errorf("unsupported mime type: %s", mimeType) } ext := extensions[0] log.Printf("Assumed extension: %s", ext) fakeFileName := fmt.Sprintf("voice_message.%s", ext)
Testing locally - it works:
2024/07/28 17:49:06 Assumed extension: oga
Deploying to the cloud - it doesn't work:
2024/07/28 17:55:32 unsupported mime type: audio/ogg
Checking the Go versions, locally and in the CI/CD used for building - they are the same.
Let's Cut to the Chase
It turns out the behavior of the mime package is not deterministic and depends at runtime on whether there is a /etc/mime.types file in the operating system and its contents.
That's where the mime package reads the runtime table of MIME type to file extension mappings.
I'm dead serious: you compile a binary, run all the tests, everything seems great, but this binary will determine the assumed file extensions for the same MIME type differently in different environments.
How to Fix It
Let's take known MIME types of audio files and their extensions, and manually add them in the init function using mime.AddExtensionType.
var mimetypes = [][]string{ {"audio/amr", "amr"}, {"audio/amr-wb", "awb"}, {"audio/annodex", "axa"}, {"audio/basic", "au", "snd"}, {"audio/csound", "csd", "orc", "sco"}, {"audio/flac", "flac"}, {"audio/midi", "mid", "midi", "kar"}, {"audio/mpeg", "mpga", "mpega", "mp2", "mp3", "m4a"}, {"audio/mpegurl", "m3u"}, {"audio/ogg", "oga", "ogg", "opus", "spx"}, {"audio/prs.sid", "sid"}, {"audio/x-aiff", "aif", "aiff", "aifc"}, {"audio/x-gsm", "gsm"}, {"audio/x-mpegurl", "m3u"}, {"audio/x-ms-wma", "wma"}, {"audio/x-ms-wax", "wax"}, {"audio/x-pn-realaudio", "ra", "rm", "ram"}, {"audio/x-realaudio", "ra"}, {"audio/x-scpls", "pls"}, {"audio/x-sd2", "sd2"}, {"audio/x-wav", "wav"}, } func init() { log.Println("init mimetypes") for _, v := range mimetypes { typ := v[0] extensions := v[1:] for _, ext := range extensions { err := mime.AddExtensionType("."+ext, typ) if err != nil { log.Fatalf("mime: %s", err.Error()) } } } }
This will make the behavior of our application deterministic regarding the domain it will work with (in my case, audio files).
Conclusion
This experience showed that things in Go are not always deterministic. If something seems odd, don't hesitate to dive into the library's source code and see how it's implemented. This can save you a lot of time and trouble in the long run.
The above is the detailed content of Indeterminacy of the `mime` Package in Go: Trust But Verify. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











Golang is better than Python in terms of performance and scalability. 1) Golang's compilation-type characteristics and efficient concurrency model make it perform well in high concurrency scenarios. 2) Python, as an interpreted language, executes slowly, but can optimize performance through tools such as Cython.

Golang is better than C in concurrency, while C is better than Golang in raw speed. 1) Golang achieves efficient concurrency through goroutine and channel, which is suitable for handling a large number of concurrent tasks. 2)C Through compiler optimization and standard library, it provides high performance close to hardware, suitable for applications that require extreme optimization.

Goisidealforbeginnersandsuitableforcloudandnetworkservicesduetoitssimplicity,efficiency,andconcurrencyfeatures.1)InstallGofromtheofficialwebsiteandverifywith'goversion'.2)Createandrunyourfirstprogramwith'gorunhello.go'.3)Exploreconcurrencyusinggorout

Golang is suitable for rapid development and concurrent scenarios, and C is suitable for scenarios where extreme performance and low-level control are required. 1) Golang improves performance through garbage collection and concurrency mechanisms, and is suitable for high-concurrency Web service development. 2) C achieves the ultimate performance through manual memory management and compiler optimization, and is suitable for embedded system development.

Golang and Python each have their own advantages: Golang is suitable for high performance and concurrent programming, while Python is suitable for data science and web development. Golang is known for its concurrency model and efficient performance, while Python is known for its concise syntax and rich library ecosystem.

The performance differences between Golang and C are mainly reflected in memory management, compilation optimization and runtime efficiency. 1) Golang's garbage collection mechanism is convenient but may affect performance, 2) C's manual memory management and compiler optimization are more efficient in recursive computing.

Golang and C each have their own advantages in performance competitions: 1) Golang is suitable for high concurrency and rapid development, and 2) C provides higher performance and fine-grained control. The selection should be based on project requirements and team technology stack.

Golangisidealforbuildingscalablesystemsduetoitsefficiencyandconcurrency,whilePythonexcelsinquickscriptinganddataanalysisduetoitssimplicityandvastecosystem.Golang'sdesignencouragesclean,readablecodeanditsgoroutinesenableefficientconcurrentoperations,t
