Enter the query into the form above.
API method:
GET /api/symbols?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel search send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
Return the protocol version of STORE as an integer.
Collect garbage from the store at SERVER. If MIN-FREED is non-zero, then collect at least MIN-FREED bytes. Return the paths that were collected, and the number of bytes freed.
Return the list of valid "derivers" of PATH---i.e., all the .drv present in the store that have PATH among their outputs.
Return #t if PATH is a store path, and not a sub-directory of a store path. This predicate is sometimes needed because files *under* a store path are not valid inputs.
Return the list of store items for which a build failure is cached.
The result is always the empty list unless the daemon was started with '--cache-failures'.
Return true if PATH is syntactically a valid store path. Unlike 'store-path?', this can be used to validate untrusted input.
This must not be confused with 'valid-path?'.
Set STORE's CACHE to VALUE.
This is a mutating version that should be avoided. Prefer the functional 'set-store-connection-cache' instead, together with using %STORE-MONAD.
Make PATH a temporary root for the duration of the current session. Return #t.
Run MVAL, a monadic value in the store monad, in STORE, an open store connection, and return the result.
Return the hash part of PATH as a base32 string, or #f if PATH is not a syntactically valid store path.
Return #t if PATH is a derivation path.
Like 'references', but cache results.
Add a garbage collector root pointing to TARGET, an element of the store, preventing TARGET from even being collected. This can also be used if TARGET does not exist yet.
Raise an error if the caller does not have write access to the GC root directory.
Verify the integrity of the store and return false if errors remain, and true otherwise. When REPAIR? is true, repair any missing or altered store items by substituting them (this typically requires root privileges because it is not an atomic operation.) When CHECK-CONTENTS? is true, check the contents of store items; this can take a lot of time.