client can not connect the server
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
Research direction
Start with neuron_explainer/activation_server/main.py and compare the server command's port 8000 with the error's current URL at port 8002 and the client environment setting. Run the supplied server and client commands, then verify that the client can look up model information successfully.
Written by the indexing model from the issue text.
Description
Error: Unable to look up model info. Are you sure you're running an activation server for this dataset? Current URL: http://localhost:8002
server and client are deployed on the same machine,
server start as the command:
python neuron_explainer/activation_server/main.py --run_model False --port 8000
client start as the command:
NEURON_VIEWER_ACTIVATION_SERVER_URL=http://localhost:8000 npm start
Is the OPENAI_API_KEY neccssary?
- Dominant language
- Python
- Stars
- 4.1k
- Forks
- 242
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/transformer-debugger
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
openai/transformer-debugger#19 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
openai/transformer-debugger#18 · 1 comment · 3 reactions ·
All issues in openai/transformer-debugger
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
MISP/misp-workbench#496 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
fossasia/visdom-dev#69 ·
Maintainers usually reply within 3 days
-
[Bug] Parameters named like a property break to_xcal()Possibly taken @atharvasalunke1267 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
collective/icalendar#2018 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day