OpenRefine / OpenRefine/OpenRefine

Display clearer error messages when Wikibase instance is unreachable

Open
#3,138 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

error handling Type: Bug wikibase
Dominant language
Java
Stars
12k
Forks
2.2k
Avg merge
1d 14h
Merged PRs (30d)
27

Description

Currently running OpenRefine directly from the master branch and reconciling with an independent Wikibase instance doesn't fully work on Chrome on MacOS Catalina.

To Reproduce

Steps to reproduce the behavior:

  1. First, run OR in terminal from cloned master branch
  2. Then, add reconcilitation service and corresponding manifest
  3. Finally, try adding some data and building a schema to prepare to upload the data to Wikibase
Current Results

Once you get to the statement level for a new item – it is not possible to add values to the statement, the value field does not appear.

Expected Behavior

A value box should appear, once a property is selected. At the moment I can select a property, but then nothing happens.

Screenshots

Screenshot 2020-08-25 at 23 59 47

Versions
  • Operating System: MacOS Catalina 10.15.6
  • Browser Version: Google Chrome Version 84.0.4147.135 (Official Build) (64-bit)
  • JRE or JDK Version: JRE 1.8.0_261
  • OpenRefine: OpenRefine master branch as of 28.08.2020

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

No files, tests, or entry points are named. Reproduce the Wikibase reconciliation flow from the cloned master branch in Chrome on macOS, then trace what happens after selecting a property when the instance is unreachable. Done means the failure produces a clear error message and the expected value box behavior is addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.