Skip to content
#

scheduling

Here are 689 public repositories matching this topic...

odin
ttymck
ttymck commented Aug 2, 2020

Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).

To Reproduce

  1. odin deploy -f test.job.yaml
  2. odin log -i {job_id}
vagrant@vagrant:~/odin$ odin log -i dea194794589
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x79c764]

goroutine
pretalx
oxinabox
oxinabox commented Jun 14, 2020

Problem you are facing

I wish to know what type a submission was proposed by the author,
vs what type of submission the program committee accepted the program item as.

Possible Solution

Introduce this idea of a a "Accepted-As" submission type, that is set by the program committee, as a distinct field from the submission type as set by the submitter.

Context

We have 3 main type

Improve this page

Add a description, image, and links to the scheduling topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the scheduling topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.