| Age | Commit message (Collapse) | Author |
|
- Rename `vault_admin_list` to `vault_host_list` in config and actions
- Add `#[serde(rename)]` attributes to all data structures for shorter
JSON keys
- Update field renames in LocalConfig, LatestFileData, LatestInfo,
LocalSheetData, Member, SheetData, Share, and VirtualFileMeta
|
|
This adds a reverse mapping from virtual file IDs to their actual paths
in reference sheets, which is needed for proper file resolution during
operations that reference files by ID.
|
|
- Return host mode status from auth_member to determine admin privileges
- Add reference sheet detection to get_current_sheet_name with allow_ref
parameter
- Prevent modifications to reference sheets unless in host mode
- Use VAULT_HOST_NAME as sheet holder for host mode operations
- Add share/merge share action registrations
|
|
Add `try_get_local_output` helper to retrieve output channel from
context and `local_println!` macro for sending formatted strings. Use
these in track actions to send progress messages to CLI instead of
stdout.
Also reduce log level for connection events from info to debug.
|
|
|
|
|
|
|
|
When tracking files, modified files are now skipped instead of
automatically synced if the new `allow_overwrite_modified` flag is
false. The action result includes a new `skipped` field listing these
files.
|
|
|
|
- Add check for non-existent files in track_file_action - Include
VirtualFileId in SyncVersionInfo type - Handle first download case in
proc_sync_tasks_local by creating new mapping - Ensure parent
directories exist before writing downloaded files
|
|
|
|
The action now accepts a boolean flag to control whether success
information should be printed to stdout. When enabled, held files are
prefixed with "+" and thrown files with "-".
The logic for hold/throw operations was also corrected to match the
intended behavior.
|
|
|
|
|
|
|
|
- Add sync task processing for both local and remote operations - Use
temp files for secure download operations - Update file metadata after
successful synchronization - Add proper error handling and cleanup for
sync operations - Display sync progress with appropriate status symbols
|
|
The version information is now sent regardless of whether files have
member holders, simplifying the update protocol.
|
|
|
|
When updating to latest info with no sync needed, ensure the workspace
is properly marked as unmodified when running local procedures.
|
|
- Record vault state changes in sheet operations - Track modifications
when creating, dropping, or updating sheets - Mark vault as unmodified
after syncing with upstream - Add vault_modified module with check and
sign functions
|
|
|
|
Add file_update_info parameter to track versions and descriptions, add print_infos flag for user feedback.
|
|
Implement complete update task processing for both local and remote operations, add version validation and conflict detection.
|
|
Add comprehensive file update verification with detailed failure reasons including version mismatch, file not held, and missing descriptions.
|
|
The change from HashSet to Vec for task collections maintains the order
of file operations, which is important for consistent processing
behavior. This affects created_task, update_task, and sync_task
variables throughout the code.
|
|
|
|
- Implement SHA1 hash calculation module with async support
- Add file status analysis for tracking moves, creates, and modifications
- Enhance local file management with relative path handling
- Update virtual file actions with improved tracking capabilities
|
|
- Create virtual file actions module
- Add basic structure for virtual file operations
- NOTE: Still under development
|
|
- Refine action service connection handling
- Extend client registry functionality
- Enhance server registry capabilities
|
|
- Add cached sheet data synchronization
- Implement bidirectional sheet version checking
- Enhance update_to_latest_info_action with sheet sync
- Add support for SheetData and CachedSheet integration
|
|
- Add write_and_return macro for common result handling pattern - Extend
make_sheet_action to restore sheets with no holder - Implement
drop_sheet_action for releasing sheet ownership - Register new
drop_sheet_action in client and server registries
|
|
- Add redirect functionality for already stained workspaces
- Implement SameUpstream and Redirected result types
- Improve vault address update logic
|
|
- Update local actions implementation
- Improve latest info handling
- Enhance vault sheets management
|
|
- Update client and server registry logic
- Improve TCP connection instance handling
|
|
- Implement make_sheet_action for creating sheets
- Add sheet-related constants
- Update sheet data structures
|
|
This action synchronizes the latest vault information including sheets,
reference sheet content, and member data between local and remote
instances.
|
|
The authentication function now returns the authenticated member's ID
instead of just () when successful. This provides callers with access to
the authenticated member's identity for subsequent operations.
|
|
- Use dereferenced UUID instead of cloning - Simplify error message
formatting
|
|
Initialize and insert Arc-wrapped LocalWorkspace and UserDirectory
instances into the ActionContext for client environment actions. This
provides workspace and user directory data to actions running in client
mode.
The LocalWorkspace is initialized from the current directory's local
config, while UserDirectory uses the current document directory. Both
are wrapped in Arc for efficient sharing across the action execution.
|
|
The server_entry function now accepts an optional port_override
parameter that allows specifying a custom port instead of using the
configured port from vault configuration. When port_override is greater
than 0, it takes precedence over the configured port.
|
|
|
|
|
|
`with_arc_data` 2. Add new `insert_data` and `insert_arc_data` methods
that take &mut self
|
|
|
|
Include current connection count in connection open/close log messages
for better monitoring of server load
|
|
Lock the vault before starting the server and unlock it during shutdown.
|
|
|
|
parameters during `on_proc_begin`
|
|
`is_remote_action`
|
|
|