Skip to content

v2.60.0: debug, pin, summarise

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Oct 17:26
v2.60.0
091b02f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v2.60.0 — new since v2.59.1

Debug from your editor, pin where vsp may work, read less to know more.
v2.59.x continues as an LTS line on release/2.59 (fixes only).

New: vsp dap, a Debug Adapter Protocol server. It lets you debug ABAP from VS Code, nvim-dap or JetBrains on a real system, with no Z code. See Debug from your editor (DAP).

New: read summary. SAP(action="read", ..., params={"summary": true})
(vsp source read ... --summary) returns the lines, bytes and sha256 of
the source instead of the source. params={"if_none_match": "<sha256>"}
(--if-none-match) answers "unchanged: source sha256 …" while the source
still has that digest. Only the object's own source is compared, not the
dependency context. A read with include_hash now carries the same sha256. The digest is over the exact text, not normalised. See
Read Summary.

Fixed:

  • vsp dap releases everything it took. Every exit path (disconnect,
    end of stream, a signal, a failed step or attach) clears the breakpoints,
    releases the debuggee and stops the listener. A disconnect during a listen
    no longer waits behind it: measured on a real system, 58 s → 0.1 s (#346).
  • A failed BADI_IMPL leaves no empty ENHO (#349, ported from #336). The
    shared cleanup after a failed create now also releases the lock it took,
    and a container whose transport request can't be established is kept, with
    the manual step named, rather than deleted past --allowed-transports.
  • The leak scan can't be blinded. Control bytes in a commit message, a
    file name or a foreign message encoding no longer hide a value from it, and
    it never prints a scanned path or value in its own log (#347).

Moved out: the ABAP transpilers (vsp compile) now live in ABAPiti.

New: --expect SID[.CLIENT][/USER] (or SAP_EXPECT, or "expect" on a
.vsp.json system) pins where vsp may work, e.g. --expect A4H.001/DEVELOPER.
A configured user that differs is refused at startup, before any logon. On
the first request, vsp asks the system for its SID, client and user and
refuses everything when they differ. SAP() shows pinned: A4H.001/DEVELOPER ✓.
Without a pin, nothing changes and no extra request is sent. The server's
startup log and vsp config show now say where the logon came from.

Platforms: six binaries: linux-amd64, linux-arm64, darwin-amd64,
darwin-arm64, windows-amd64 and windows-arm64. vsp-linux-386,
vsp-linux-arm and vsp-windows-386 are no longer built. On those platforms,
install from source instead:
go install github.com/oisee/vibing-steampunk/cmd/vsp@latest
(vsp update from v2.59.x only reports that the release has no asset for
the platform and leaves the installed binary alone; from v2.60.0 on it says
why and gives this command).

Downloads

Platform Architecture File
Linux x64 vsp-linux-amd64
Linux ARM64 vsp-linux-arm64
macOS x64 vsp-darwin-amd64
macOS Apple Silicon vsp-darwin-arm64
Windows x64 vsp-windows-amd64.exe
Windows ARM64 vsp-windows-arm64.exe

Checksums: checksums.txt. Or run vsp update from an older version on one of these platforms; elsewhere: go install github.com/oisee/vibing-steampunk/cmd/vsp@latest.
LICENSE and NOTICE travel with the binaries (Apache-2.0 components are embedded).

Changelog: https://github.com/oisee/vibing-steampunk/blob/v2.60.0/CHANGELOG.md

Assets 11
Loading