Skip to content

downstream found possible bug #208

@fallbackerik

Description

@fallbackerik

See chubin/wttr.in#1075

To me the wttr.in codebase looks like it is basically parsing a web request into the corresponding terminal command for wego, and then processes the wego output to send it back to the curl command making the request. Therefore, I assume if there's a bug, it's actually here. Could someone have a look? Learning more about your code base would be nice as well, even though I'm not as experienced reading golang.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions