Netflix/metaflow

Improve visibility of Metaflow Code object

Open

#1,009 opened on Apr 13, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Python (695 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (7,202 stars)
PR merge metrics
 (Avg merge 31d 18h) (23 merged PRs in 30d)

Description

The code tarball saved by Metaflow is accessible with the client but it is not very easy to work with. We may want to make it more visible possibly even in the Metaflow UI.

Another idea would be to link it to the source control that the Metaflow code is in (if there is one). In particular, we could store the branch/commit information as well as a "dirty" patch file if needed. We can keep the same tarball to work internally but also linking it to the user's development environment may make it easier to work with.

Contributor guide

Research direction
Investigate how the code tarball is currently stored and accessed in Metaflow client and UI. Explore ways to extract branch/commit information from the environment and link it to the source control. Consider storing a dirty patch file alongside the tarball. Evaluate UI modifications to display this information.
Tech stack
python
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonMetaflow
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60