Repository navigation
CoreScope 0.12.0
Added
- Databases › watch changes: a window per database that lists, while you use the app, rows
created (all values), updated (before/after, changed columns) and deleted, per table and
moment; ignore noisy tables (defaults from.corescope.yml, togglable in the window), clear,
snapshot and compare. No triggers or binlog: kept rows compared when the server says a table
was written (MySQL/MariaDB information_schema, PostgreSQL pg_stat). MCPdb_watch_*. .corescope.ymldatabases:— per database:server,ignore_changes,skip_data,
before_restore/after_restorecommands (any stack).- Restore a dump, safer: other sessions on a replaced database are closed (or waited for
30 s),before_restore/after_restorerun around it, the tables without data default to
the project's list and the last choice, a marker table flags an incomplete restore (incomplete
on the card), progress is read from the server, and each server has a restore history. - Databases › restore a dump: a mysqldump / mariadb-dump / pg_dump (plain) dump,
.sqlor
.sql.gz, into an existing database (replaced after a snapshot) or a new one. It is analysed first
— tables with exact row counts and sizes, views, triggers, routines, definers; truncated,
multi-database or cross-database dumps are refused — and you choose which tables come without
data (or No data above N rows), and whether to leave out triggers / owners. Streamed into the
server's client inside the container with its credentials, in batched transactions; the dump's
USE / CREATE DATABASE / \connect, SET GLOBAL and grants are left out, missing DEFINER accounts
become CURRENT_USER, max_allowed_packet is raised when needed. Progress, cancel and a log that
names the dump line of an error. CLIdb analyze/db import; MCPanalyze_dump,
restore_dump,restore_status,cancel_restore. - Environment › recent runs: every mode start/stop and action keeps its last 5 logs (with the
exit code appended). The environment card lists them, Show output next to a status error opens
the latest one, and logs open in a window that follows the run, marks errors and finds with ⌘F.
Action logs are on the Logs page too. MCPenvironment_runs. - Reorder by dragging the ≡ handle (or Move up / Move down): projects on the Projects page
(saved inprojects.json, so the floating panel and menu bar follow; MCPreorder_projects)
and project sections on the Profiles page (MCPset_setting profiles_order).
Changed
- Profiles page, more compact: each project section folds to one line that says what is in
use, and an app's actions are chips grouped by kind instead of one row each — the chip is the
button (▶ and the name), with the last result as a dot and output, artifact, cancel and the
command in its context menu. Action and run rows highlight end to end under the pointer.
Commits since v0.11.0
- feat(environment): keep recent run logs and show them in the app (c934496)
- feat(profiles,projects): compact environment actions and drag to reorder (f3dad28)
- feat(databases): restore a dump into a new or existing database (f14cf72)
- feat(databases): watch changes, safer dump restores, databases in .corescope.yml (a14952b)
- chore(release): 0.12.0 (625a62c)
Full diff: v0.11.0...v0.12.0
Install
- Download CoreScope-0.12.0-macos-universal.dmg below (universal: Apple Silicon and Intel, macOS 14+).
- Open the DMG and drag CoreScope to Applications.
- The app is open source and signed ad hoc, not notarized by Apple, so macOS blocks it the first time. Open it once, then go to System Settings → Privacy & Security and click Open Anyway. Alternatively, in Terminal:
xattr -dr com.apple.quarantine /Applications/CoreScope.app
The Intel slice is built and checked on every release but has not yet been run on an Intel Mac; reports are welcome.
Checksums (SHA-256)
8ba011e51ea5ea8acec4af0a138d32b71c921e082fc9971fdff07b3a0bc50b0a CoreScope-0.12.0-macos-universal.dmg
6755a7dfff73ba2f3bbdc120133e5109730baebb4c9daae5984f6a84d6ab6a8a CoreScope-0.12.0-macos-universal.zip
Verify with shasum -a 256 -c SHA256SUMS.txt in the download folder.