There's a guide on the subreddit wiki on how to format code for display on reddit. When in doubt, you can also use GitHub Gist or Hastebin, though. Source: over 4 years ago

In future, use code formatting or put your code into hastebin.com and then post a link here. It will make it easier to read. Source: over 4 years ago

If you want to post a log, you'll have to generate one first (go to settings > logging and set both logging verbosities to 0-debug and 'log to file' to ON, then do whatever you need to do to create the offending behavior; that should make the log. Then, open the resulting log in a text editor and copy/paste the contents somewhere like hastebin.com and post a link to it here). Source: over 4 years ago

Close RetroArch, then navigate to your 'logs' folder in your RetroArch user directory (if you can't find it, open RetroArch and go to settings > directory and see where your 'logs' directory is located). You should see a text file there. Copy/paste its contents somewhere like hastebin.com and then post a link to it here and I/we can take a look. Source: almost 5 years ago

Can you give me the entire command history that got you to where you are now? If you can do that, make sure there is not personal information in the history, especially passwords. Look at the output of history. If it's large, try hastebin.com . Source: almost 5 years ago

Anecdotal, but I have built from scratch a fairly large OpenAPI-compliant service using the Goa dsl (https://goa.design) and a coding agent and I've suspected for a while that the reason I've been as productive as I have with few blind alleys is that Goa kept the mistake surface pretty constrained. I also like not having the model generate boilerplate, as Goa's tooling does all that so much more cheaply. YMMV. - Source: Hacker News / 4 days ago

My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / about 2 years ago

See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: over 2 years ago

If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: about 3 years ago

Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / about 3 years ago