Tasks List for first run of monoloth prototype

[saurabhpujar]

Tasks for creation of monolith prototype and it's first run:

• Determine target projects
  • Open GitHub issue in Varangian Repo [Saurabh]
  • Issue 6 assigned to Ale, Christoph. PR: 4
  • Examine some target projects [Yunhui]
  • document requirements of model, what do we need, how much of it? #16
  • Generate auto-labeler data for #15 @zyh1121
    • Grep
    • Crun
    • Fuse-overlayfs
    • https://github.com/containers/buildah/issues ?
• Training data split
  • Temporal slicing of commits into training, dev splits [Burn/Saurabh]
• Manual Verification of model output
• ML
  • Feature Engineering:
    • Incorporate Yunchungs features in Feature Extractor [Burn]
    • Check if new features improve performance [Saurabh]
    • Add new features to feature extractor [Saurabh]
  • Separate training and inference [Burn]
  • Separate Voting from training [Burn]
• C-BERT:
  • Create new train file for prototype [Luca]
  • Create tokenization script [Saurabh]
  • Inference mode tokenization[Luca/Saurabh]
  • Write script for artifacts package creation [Luca]
  • Run experiments to pick the right C-BERT model for prototype [Luca/Saurabh]
• Engineering
  • Prepare system diagram [Saurabh]
  • Formalize output across components [Saurabh/Burn/Luca]
  • Create Infer output code extractor [Burn]
  • Write Python code for first run
  • Integration run
  • Model selector after training [Saurabh]
  • Inference output selector [Saurabh]
  • Get metrics at bug level
• Bot #13
  • Provide libtiff data to Kevin [Saurabh/Burn]
  • Bot Development @KPostOffice

[zyh1121]

• https://github.com/containers/buildah/issues?
  Not an ideal project for now due to the static analyzer support. It's mainly in Go and Shell (Go 68.9%, Shell 28.7%)

• In addition, the following two are the same thing, as the main efforts will be changes based on the released auto-labeler and dataset generator to support new heuristics.

  • Generate auto-labeler data for Generate auto-labeler data for #15 @zyh1121
  • Static Analyzer/Auto-labeler

• Since we are going to plan for multiple demos, is Generate auto-labeler data for #15 still priority/critical-urgent

[saurabhpujar]

@zyh1121

• Noted.
• Deleted duplicate task.
• We can discuss in the meeting today.

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[saurabhpujar]

/remove-lifecycle stale

[saurabhpujar]

/remove-lifecycle stale

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.