darmiel / yaxc Goto Github PK

CLI

• gpg signature check (#28)
• survey (-m)

GLOBAL FLAGS:

• anywhere
• key (whitelist key) (#24)

---

🚀 push

merge paste into push

FLAGS:

• anywhere*>
• secret>
• ttl
• base64
• hash
• gpg-sign (#28)

OTHER:

• from pipe
• from stdin
• from file (#25)
• from web (proxy?) (#29)

---

👈 pull

merge get into pull

FLAGS:

• anywhere*>
• secret>
• `base64
• gpg-sign (#28)

OTHER:

• to stdout
• to file (#25)

---

👀 watch

• compare last updated
  • store DateTime (#30)

FLAGS:

• anywhere*>
• secret>
• check-delay
• base64
• gpg-sign (#28)
• no-pull
• no-push

Server

• whitelist-key database (#24)

PARAMETERS:

• base64 (#26)

FLAGS:

• enable-whitelist-key (#24)

Hi,

in response to your StackOverflow question and Data Race in Cache #8, see majodev/yaxc for a minimal reproduction test and fix.

TL;DR:
Go fiber zero allocation. The byte slice buffer that holds your strings path and hash which you got from ctx is only valid within the handler. The key/values stored inside your cache map will change as these strings are still based on this buffer that gets reused in each handler.

Either:

• Create a new Buffer from the read values inside the handler and copy its contents over
• or use the utils.ImmutableString util (same as above)
• or use the Immutable config flag (perf penalty, no longer zero allocated context).