You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changed — may break callers
A failed bot command's run names the Cloud API call that failed.runs show and runs list give its error.http the method and endpoint_template beside the status — { "method": "POST", "endpoint_template": "/v23.0/:id/messages", "status": 400 } — where before they had only the status. Every id in the path is written :id, so the phone number id, the business account id and a media id never reach a run or a trace. Bot requests in --trace and in a recorded run carry the same two fields, and a pretty trace line shows them after the operation's name. A script that parses --trace text sees that extra column.
Added
store reset --dry-run lists what a reset would empty and deletes nothing (cli-core 0.429.0): the store's files and bytes, every data table with its rows, whether a backup comes first, and whether a serve or another process has the file open.
search messages --discover also finds messages close in meaning once e5-small is downloaded and conversations rebuild has given messages their own vectors (cli-core 0.432.0). Each hit's discovery.found_by says which search found it. Until then discovery searches by words as before and says why. Nothing is downloaded and no text leaves the computer.
Fixed
A bare --version answers before the program loads: the bin starts through @wirecat/cli-core/cli/start (cli-core 0.429.0).