The Wayback Machine - https://web.archive.org/web/20220504052812/https://github.com/topics/job-scheduler
Skip to content
#

job-scheduler

Here are 383 public repositories matching this topic...

odin
tmkontra
tmkontra 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
bug good first issue
zhaoyuguang
zhaoyuguang commented Feb 21, 2019

请在提交问题之前回答这些问题。

  • 你为什么提交这个问题?
  • 问题或讨论
  • Bug
  • 需求
  • 功能或性能改进

要求或改进

  • 我们目前还没有部署手册,如果有人愿意编写欢迎 PR
  • @crystalChen 如果有时间开始编写 请将assign只想你 并关闭 help wanted
help wanted good first issue document
cohix
cohix commented Oct 26, 2021

Another idea, the tests could be condensed quite a bit, for example:

func TestDefaultRules(t *testing.T) {
	rules := defaultHTTPRules()

	tests := []struct {
		name string
		url  string
	}{
		{"http allowed", "http://example.com"},
		{"https allowed", "https://example.com"},
		{"IP allowed", "http://100.11.12.13"},
	}

	for _, test := range tests {
		t.Run(test.name, func(t 
enhancement good first issue

Improve this page

Add a description, image, and links to the job-scheduler 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 job-scheduler topic, visit your repo's landing page and select "manage topics."

Learn more