Core 1826 add/update harperdb studio topic and subtopics#2
Merged
Conversation
terraHDB
requested review from
DavidCockerill,
deliciousmonster,
kriszyp and
kylebernhardy
September 26, 2022 17:32
terraHDB
changed the title
Member
|
I noticed this PR has the install changes from 1825 in it? did you branch off that branch for this? |
kriszyp
reviewed
Oct 10, 2022
| 1) Click the plus icon (Browse Add Button) at the top right of the table browser. | ||
| 2) The Studio will pre-populate existing table attributes in JSON format. | ||
|
|
||
| *The hash_attribute is not included, but you can add it in and set it to your desired value. Auto-maintained fields are not included and cannot be manually set. You may enter a JSON array to insert multiple records in a single transaction.* |
DavidCockerill
approved these changes
Oct 17, 2022
kriszyp
reviewed
Oct 28, 2022
# Conflicts: # docs/install-harperdb/mac.md # docs/install-harperdb/node-ver-requirement.md # docs/install-harperdb/offline.md # docs/install-harperdb/windows.md
DavidCockerill
pushed a commit
that referenced
this pull request
Nov 15, 2022
* doc migration epic branch * 3/4 progress of security * finished configuration.md, began users and roles * users and roles migrated; still needs updates * updated user and roles operations * corrections to security docs * CORE-1825 Add/Update "install harpedb" subtopics (#1) * added mac, added/updated windows, added/updated node version requirements, and added offline docs * go requirements * docs adjustments * testing variable usage * testing variable usage * Update other.md Update installation for other operating systems. * added link to download * node version * exact replica download button * functional download link * deleted old link * node version Co-authored-by: Kris Zyp <kriszyp@gmail.com> * Core 1826 add/update harperdb studio topic and subtopics (#2) * added mac, added/updated windows, added/updated node version requirements, and added offline docs * 1/3 through studio subtopics * 2/3 through studio subtopics * 3/3 through studio subtopics * corrected harperdb operations api * removed icon descriptions and fixed typos * removed icon descriptions * primary key vs hash_attribute change * primary key vs hash attribute qualifier * minor change to example function Co-authored-by: Kris Zyp <kriszyp@gmail.com>
DavidCockerill
pushed a commit
that referenced
this pull request
Nov 29, 2022
* testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * testing variable syntax * reverted changes from variable testing * added diagrams and clustering docs * more formatting * formatted the rest of clustering docs * Core 1828 Docs Migration- Security: Topic and Subtopics (#4) * doc migration epic branch * 3/4 progress of security * finished configuration.md, began users and roles * users and roles migrated; still needs updates * updated user and roles operations * corrections to security docs * CORE-1825 Add/Update "install harpedb" subtopics (#1) * added mac, added/updated windows, added/updated node version requirements, and added offline docs * go requirements * docs adjustments * testing variable usage * testing variable usage * Update other.md Update installation for other operating systems. * added link to download * node version * exact replica download button * functional download link * deleted old link * node version Co-authored-by: Kris Zyp <kriszyp@gmail.com> * Core 1826 add/update harperdb studio topic and subtopics (#2) * added mac, added/updated windows, added/updated node version requirements, and added offline docs * 1/3 through studio subtopics * 2/3 through studio subtopics * 3/3 through studio subtopics * corrected harperdb operations api * removed icon descriptions and fixed typos * removed icon descriptions * primary key vs hash_attribute change * primary key vs hash attribute qualifier * minor change to example function Co-authored-by: Kris Zyp <kriszyp@gmail.com> * added more context to clustering intro page; adjusted subscription behavior description Co-authored-by: Kris Zyp <kriszyp@gmail.com>
kylebernhardy
pushed a commit
that referenced
this pull request
Jul 14, 2026
kriszyp review (docs#576 #2): the prose credited *export* for 'wins on reload', but the hardened example deliberately does not export (it registers via server.resources.set with all transports off). The quota hook actually resolves the resource by name from the live registry each call (checkDurableQuota -> getResources().get(path)), and server.resources.set() populates that same registry, so registration — not export — is what makes it resolvable, and the currently-registered class wins on reload. Prose now says 'registered' and names both registration paths. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0188G62J9fZQg4J9rVuqLzjy
kylebernhardy
added a commit
that referenced
this pull request
Jul 22, 2026
* Gate the quota-hook example's table off the MCP surface
The example exported the counter table, which surfaces update_/delete_
verb tools and REST — letting a permitted client reset its own quota.
Found by a blind agent evaluation of the harper-mcp skill (skills#69).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Use the real registration mechanism to gate the quota class
static exportTypes is never read off exported classes (kriszyp) — the
wired mechanism is server.resources.set(name, Class, exportTypes), and
rest: false is needed for the REST side independently. Runtime-verified
on main: McpQuota absent from tools/list, REST 404, quota hook still
resolves and denies past the limit.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Close all six transports in the quota-gating example
The example set { mcp: false, rest: false }, closing only two of the six
transports exportTypes gates. Since McpQuota extends QuotaCounter (standard
Table CRUD) and unset means exposed, the 'reset your own counter' path the
example prevents was still reachable via SSE/WS/GraphQL/MQTT. Set all six
(mcp, rest, sse, ws, graphql, mqtt) and reword the comment so it doesn't read
as fully closed when it wasn't. Addresses kriszyp's review on #576 (incl. the
sse surface his suggestion omitted).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0188G62J9fZQg4J9rVuqLzjy
* Reconcile quota.resource prose with the non-exporting example
kriszyp review (docs#576 #2): the prose credited *export* for 'wins on reload',
but the hardened example deliberately does not export (it registers via
server.resources.set with all transports off). The quota hook actually resolves
the resource by name from the live registry each call (checkDurableQuota ->
getResources().get(path)), and server.resources.set() populates that same
registry, so registration — not export — is what makes it resolvable, and the
currently-registered class wins on reload. Prose now says 'registered' and names
both registration paths.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0188G62J9fZQg4J9rVuqLzjy
* Document the durable quota as server.setMcpQuotaHandler, not config
Companion to harper#1821, which replaces the mcp.<profile>.quota.resource/method
config (a Resource reference, public-by-default) with a registration function.
Rewrite the quota section: drop the removed config keys, and show a registered
function backed by an INTERNAL (non-@export) counter table plus a separate
exported tool — so nothing exposes update_/delete_ CRUD a client could use to
reset its own counter. Resolves Kris's review that the fix belongs in the API.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0188G62J9fZQg4J9rVuqLzjy
---------
Co-authored-by: Kyle Bernhardy <kyle.bernhardy@gmail.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migrating docs, "HarperDB Studio", to gitbook.
Current state of HarperDB Studio docs: https://harperdb.io/docs/harperdb-studio/