imagej / imagej/imagej-server

HTTP 409 Conflict error

Open
#35 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
40
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Hi, I am testing ImageJ-server with the pyimagej client, but I constantly get this HTTP 409 Conflict with this line: ij.show(img_in, format='jpg'). And if I change the format to 'png' or 'tif' then no error.

If I use the browser to visit the url:

  1. http://localhost:8080/objects/object:jyrqyqekjp1oh1yz/ gives me {"id":"object:jyrqyqekjp1oh1yz","created_at":"Wed Jul 31 23:13:14 CEST 2019","created_by":"uploadFile:filename=2D_1_MMStack_1-Pos_000_000.ome-0001.tif","last_used":"Wed Jul 31 23:13:15 CEST 2019","class":"net.imagej.DefaultDataset"}

  2. http://localhost:8080/objects/object:jyrqyqekjp1oh1yz/jpg causes error:
    {"code":409,"message":"HTTP 409 Conflict"}

  3. http://localhost:8080/objects/object:jyrqyqekjp1oh1yz/png opens a png image.

I am using ImageJ 1.52p with Java 1.8.0 on MacOS 10.14.5.

Contributor guide

No contributing guide indexed for this repository

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

Reproduce the failure with pyimagej using ij.show(img_in, format='jpg'), then compare requests to /objects/object:jyrqyqekjp1oh1yz/jpg, /png, and /tif. Trace why the ImageJ server returns HTTP 409 for JPEG while PNG succeeds; done means JPEG display or retrieval works without the conflict response.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, python
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.