maxagin/p-key

Pirate Key VSCode color theme

_{℗Key or Pirate Key is a color theme
for testing DVC Extension for Visual Studio Code multiple theme compatibility.}

 

℗Key

For pirates of Visual Studio Code.

"tab.activeBackground": "#f3361f", "panel.border": "#4a1d1c", "foreground": "#4a1d1c", //"disabledForeground": "#4a1d1c", "button.background": "#dd2108", "dropdown.background": "#4a1d1c", //"widget.shadow": "#000000", //"descriptionForeground": "#fff", "sash.hoverBorder": "#fff", "editor.background": "#f3361f", "editor.foreground": "#4a1d1c", "editorLineNumber.foreground": "#4a1d1c", "sideBar.background": "#f3361f", "sideBar.border": "#4a1d1c", "activityBar.activeBackground": "#f3361f", "activityBar.activeBorder": "#f3361f", "statusBar.background": "#dd2108", //"statusBar.border": "#4a1d1c", "activityBar.background": "#dd2108", //"activityBar.border": "#4a1d1c", "editorGroupHeader.tabsBackground": "#25252d", "terminal.background": "#f3361f", "quickInput.background": "#f3361f", "editorCursor.foreground": "#ffff00", "terminalCursor.foreground": "#ffff00", "focusBorder": "#4a1d1c", // "settings.rowHoverBackground": "#fff", "scrollbarSlider.background": "#4a1d1c", "notifications.background": "#f79c18",

 

Minimalistic

 

In order to track the data files and directories added with dvc add, dvc repro, etc. DVC moves all these files to the project's cache.

However, the versions of the tracked files that match the current code are also needed in the workspace, so a subset of the cached files can be kept in the working directory (using dvc checkout). Does this mean that some files will be duplicated between the workspace and the cache?

That would not be efficient! Especially with large files (several Gigabytes or larger).

In order to have the files present in both directories without duplication, DVC can automatically create file links to the cached data in the workspace. In fact, by default it will attempt to use reflinks* if supported by the file system. File link types for the DVC cache File links are lightweight entries in the file system that don't hold the file contents, but work as shortcuts to where the original data is actually stored.

They're more common in file systems used with UNIX-like operating systems, and come in different kinds that differ in how they connect file names to inodes in the system. Inodes are metadata file records to locate and store permissions to the actual file contents.

See Linking files in this doc for technical details (Linux). Use ls -i to list inodes on Linux.

There are pros and cons to the 3 supported link types: Hard links, Soft or Symbolic links, and Reflinks in more recent systems. While reflinks bring all the benefits and none of the worries, they're not commonly supported in most platforms yet. Hard/soft links optimize speed and space in the file system, but may break your workflow since updating hard/sym-linked files tracked by DVC in the workspace would cause cache corruption.

To protect against this, DVC protects hardlinks and symlinks by making them read-only, requiring using dvc unprotect to be able to modify them safely.

p-key's Issues

Fix text line-height in the README.md

The text under For pirates of Visual Studio Code. needs to be fixed.

It actually looks very cool, the only problem that at VSCode and Marketplace it's looks different.

Also looks good. Hmmm... Probably just to modify the textual content.