aboutsummaryrefslogtreecommitdiff
path: root/modules/core/virtual-fs.js
Commit message (Collapse)AuthorAgeFilesLines
* fix(newos4): the virtual /sys entry leaked into listings, trees and counts ↵Agando2026-10-231-6/+17
| | | | | | | | | | | | | | | | (v4.6.88-90) One phantom entry, three symptoms: - ls() injected 'sys' whenever it was called without a path, so 'cd _agents; ls' advertised a sys directory that does not exist, and list_files('_agents/sys') answered 'Directory not found' — the reported false negative. Injection is now gated on dir === root. - tree() pushed the same virtual name into the walk and dereferenced it, throwing mid-output on every root listing. Guarded. - _gatherFileInfo() walked into /sys and counted a synthetic subtree: 146 files / 114 dirs for a 44-file / 15-dir store. Virtual entries are skipped. Verified: root still lists sys; _agents and skills do not; tree('') completes; world model total (44) equals an independent walk of fs.root (44), agree: true.
* fix(newos4): an invalid grep pattern returns a message, not an exception ↵Agando2026-10-231-2/+8
| | | | | | | | | | | | | | | | | (v4.6.64) Packet 8. `new RegExp(pattern)` sat unguarded in the terminal grep handler and in VFS find()/grep(), so a bad pattern threw out of the command handler into the error ledger -- the same ledger packet 2 had to stop trusting. - module-fs.js grep: compile in try/catch, print "grep: invalid pattern: <pattern> (<engine message>)" as a warning and return - virtual-fs.js find()/grep(): same guard, return [] and stash the message on _lastPatternError instead of throwing into the module error wrapper Verified live on v4.6.64 with the packet's own repro: `grep "/\bug_id\" file` prints the message, the error counter stays 0 (was: one ledger entry per call), a valid pattern still matches, and fs.grep('[') returns [] instead of throwing.
* fix(newos4): define VirtualFS.emptyTrash() — empty-trash threw since ↵Agando2026-10-231-0/+27
| | | | | | | | 2026-10-18 Report RPT-20261018-164646-89352963 ("this.fs.emptyTrash is not a function") was filed by the auto-filer and never fixed: terminal.js:1777 called a method VirtualFS never defined, so 'empty-trash --confirm' threw instead of emptying. Added emptyTrash() returning true only when it removed something. Verified live on v4.6.54: put -> rm -> empty-trash --confirm => 'Trash emptied.'; second run => 'Trash is already empty.'; .trash entries 0.
* newOS4 v4.6.40: review fixes (bug diagnostics, trash tree, dir paste, stale ↵Agando2026-10-181-14/+7
| | | | capture, preview)
* auto: 2026-07-09_06:00 changesAgando2026-07-091-4/+8
|
* auto: 2026-06-19_18:01 changesAgando2026-06-191-2/+55
|
* auto: 2026-06-17_06:01 changesAgando2026-06-171-4/+35
|
* auto: 2026-06-10_06:00 changesAgando2026-06-101-9/+345
|
* auto: 2026-06-09_06:00 changesAgando2026-06-091-0/+7
|
* auto: 2026-06-08_18:00 changesAgando2026-06-081-94/+15
|
* auto: 2026-06-08_06:00 changesAgando2026-06-081-1/+4
|
* auto: 2026-06-07_18:00 changesAgando2026-06-071-0/+16
|
* auto: 2026-06-06_06:00 changesAgando2026-06-061-1/+31
|
* auto: 2026-06-04_06:00 changesAgando2026-06-041-0/+52
|
* auto: 2026-05-27_06:00 changesAgando2026-05-271-121/+319
|
* auto: 2026-05-26_06:00 changesAgando2026-05-261-5/+16
|
* auto: 2026-05-25_18:02 changesAgando2026-05-251-0/+320