linkedin / linkedin/oncall

ImportError: No module named parse

Open
#242 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.3k
Forks
245
PR merge metrics
No merged PRs in 30d

Description

I'm getting the following error:
```
Fri Mar 15 18:22:55 2019 - [uwsgi-daemons] respawning "/home/oncall/env/bin/oncall-scheduler /home/oncall/config/config.yaml" (uid: 1000 gid: 1000)
Traceback (most recent call last):
File "/home/oncall/env/bin/oncall-scheduler", line 6, in
from oncall.bin.scheduler import main
File "/home/oncall/env/local/lib/python2.7/site-packages/oncall/bin/scheduler.py", line 13, in
from oncall.api.v0.schedules import get_schedules
File "/home/oncall/env/local/lib/python2.7/site-packages/oncall/api/v0/schedules.py", line 4, in
from urllib.parse import unquote
ImportError: No module named parse

```
I think I'm using the latest version of oncall git id `a4829c0e93ec40cf1886f583ded2bd9c59752f5b`

Docker version 18.09.3
Packer version v1.3.5

I've been trying to follow the get started on https://oncall.tools/docs/admin_guide.html (except for typo about oncall.json path?).

I'm new to docker and python so sorry if I'm missing something obvious.

Cheers

Sam

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the traceback and inspect oncall/api/v0/schedules.py, then check the Python runtime used by the scheduler entry point oncall/bin/scheduler.py. Reproduce the startup failure in the documented environment; done means the scheduler starts without this ImportError.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.