# prodigy.json setting causes web app error **URL:** \ **Category:** Uncategorized\ **Tags:** done, front-end, solved\ **Created:** [June 9, 2018, 8:13pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595 "2018-06-09T20:13:34Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![djpremier](https://avatars.discourse-cdn.com/v4/letter/d/9d8465/32.png) [@djpremier](https://support.prodi.gy/u/djpremier)\ **Post date:** [June 9, 2018, 8:13pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/1 "2018-06-09T20:13:34Z")
Good afternoon people, I’m trying to use the system, but regardless of the command line (be it ner.manual, ner.teach, or others), I always get this error, even using your examples as: prodigy ner.teach my\_set en\_core\_web\_sm news\_headlines.jsonl What can it be? I wait, thanks. ![Screenshot_20180609_171053](https://us1.discourse-cdn.com/flex020/uploads/prodigy/original/1X/9d3a2bfe6f89a7c45a4fdfc7f2d0454e5a3bbd48.png) And the console is experiencing this error: bundle.js:1 Error: Minified React error #62; visit [http://facebook.github.io/react/docs/error-decoder.html?invariant=62&args[]=](http://facebook.github.io/react/docs/error-decoder.html?invariant=62&args%5B%5D=) for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at d (bundle.js:1) at \_o (bundle.js:1) at No (bundle.js:1) at finalizeInitialChildren (bundle.js:1) at completeWork (bundle.js:1) at n (bundle.js:1) at r (bundle.js:1) at i (bundle.js:1) at a (bundle.js:1) at S (bundle.js:1) u @ bundle.js:1 The rating, accept or reject, is working, but the text does not appear, just the error message ---
**Author:** ![djpremier](https://avatars.discourse-cdn.com/v4/letter/d/9d8465/32.png) [@djpremier](https://support.prodi.gy/u/djpremier)\ **Post date:** [June 9, 2018, 8:59pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/2 "2018-06-09T20:59:24Z")
Resolved, for those who go through the same situation, my solution in the case was to leave the ‘prodigy.json’, that is, not creating the file. ---
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [June 10, 2018, 8:32am UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/3 "2018-06-10T08:32:03Z")
@djpremier Could you share what was in your `prodigy.json` before? Of course, I’m glad it works now, but removing your settings shouldn’t be a solution. I suspect there’s a problem with one setting and the front-end doesn’t handle this properly – for example, the setting might have an unexpected type. So I’d love to investigate that! 🙂 Now that we have the JSON schemas implemented that validate the stream, I’ll also add validation for the `prodigy.json`. This means that if something in the settings doesn’t look as expected, Prodigy won’t even start the server and instead, output a message with details on what’s wrong. ---
**Author:** ![Ralf](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ralf/32/4176_2.png) [@Ralf](https://support.prodi.gy/u/Ralf)\ **Post date:** [June 13, 2018, 11:16am UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/4 "2018-06-13T11:16:14Z")
oo, that was to fast;) Opening the webapp I got “Oops, something went wrong ☹ You might have come across a bug in Prodigy’s web app – sorry about that. We’d love to fix this, so feel free to open an issue on the Prodigy Support Forum and include the steps that led to this message.” and in the console “Error: Minified React error #62” What to do here? ---
**Author:** ![Ralf](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ralf/32/4176_2.png) [@Ralf](https://support.prodi.gy/u/Ralf)\ **Post date:** [June 13, 2018, 11:21am UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/5 "2018-06-13T11:21:46Z")
the react side told me: "The full text of the error you just encountered is: The `style` prop expects a mapping from style properties to values, not a string. For example, style={{marginRight: spacing + ‘em’}} when using JSX." ---
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [June 13, 2018, 11:22am UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/6 "2018-06-13T11:22:39Z")
Thanks for looking into this! And hmm, this is strange. Do you have any special customisations in your `prodigy.json`? Like, a `card_css` or something similar? ---
**Author:** ![Ralf](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ralf/32/4176_2.png) [@Ralf](https://support.prodi.gy/u/Ralf)\ **Post date:** [June 13, 2018, 11:25am UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/7 "2018-06-13T11:25:25Z")
no, it’s just empty. { } ---
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [June 13, 2018, 11:43am UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/8 "2018-06-13T11:43:32Z")
Hmm, this is very mysterious and I can’t reproduce this error yet, especially not with the fairly simple text classification setup and interface. I really can’t see where this would be coming from 🤔 Could you post the exact command you ran? And if you run the command with the environment variable `PRODIGY_LOGGING=verbose`, is there anything in the config that looks suspicious? (The output after “CONTROLLER: Initialising from recipe”.) ---
**Author:** ![mayurbhangale](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/mayurbhangale/32/155_2.png) [@mayurbhangale](https://support.prodi.gy/u/mayurbhangale)\ **Post date:** [June 13, 2018, 12:17pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/9 "2018-06-13T12:17:42Z")
@ines same issue. I’m running this command: prodigy my\_recipe org\_relations ‘/path/to/model’ data.jsonl -F my\_recipe.py [Here is the log](https://gist.github.com/mayurbhangale/13ed39a85f94dcd7631e8683869e4702). There seems to be no trace of error. It is running on Mac but not on Ubuntu 16.04 ---
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [June 13, 2018, 12:34pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/10 "2018-06-13T12:34:49Z")
Thanks for the report – this is really bizarre. Trying my best to reproduce it. Prodigy practically never sets `style` manually, except for user settings like the `card_css` and in some of the image interfaces… Does this only happen in the `classification` interface or everywhere? ---
**Author:** ![mayurbhangale](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/mayurbhangale/32/155_2.png) [@mayurbhangale](https://support.prodi.gy/u/mayurbhangale)\ **Post date:** [June 13, 2018, 12:37pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/11 "2018-06-13T12:37:21Z")
Tried with ner, same issue. Though on mac all interfaces seem to be working. ---
**Author:** ![Ralf](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ralf/32/4176_2.png) [@Ralf](https://support.prodi.gy/u/Ralf)\ **Post date:** [June 13, 2018, 12:41pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/12 "2018-06-13T12:41:52Z")
hier is my log: "python -m prodigy ner.teach ensi\_set de\_core\_news\_sm “G:/OneDrive - Bircomp GmbH/Bircomp/Projekte/Entwicklung/AI/Tools/Wortindex/ENSI-Texte/ensi\_de\_utf8.txt” 14:39:57 - RECIPE: Calling recipe ‘ner.teach’ 14:39:57 - RECIPE: Starting recipe ner.teach {‘spacy\_model’: ‘de\_core\_news\_sm’, ‘loader’: None, ‘patterns’: None, ‘exclude’: None, ‘api’: None, ‘source’: ‘G:/OneDrive - Bircomp GmbH/Bircomp/Projekte/Entwicklung/AI/Tools/Wortindex/ENSI-Texte/ensi\_de\_utf8.txt’, ‘unsegmented’: False, ‘label’: None, ‘dataset’: ‘ensi\_set’} 14:39:57 - LOADER: Using file extension ‘txt’ to find loader G:/OneDrive - Bircomp GmbH/Bircomp/Projekte/Entwicklung/AI/Tools/Wortindex/ENSI-Texte/ensi\_de\_utf8.txt 14:39:57 - LOADER: Loading stream from txt 14:39:57 - LOADER: Rehashing stream 14:39:58 - RECIPE: Creating EntityRecognizer using model de\_core\_news\_sm 14:39:59 - MODEL: Added sentence boundary detector to model pipeline [‘sbd’, ‘tagger’, ‘parser’, ‘ner’] 14:39:59 - SORTER: Resort stream to prefer uncertain scores (bias 0.0) 14:39:59 - CONTROLLER: Initialising from recipe {‘stream’: \, ‘dataset’: ‘ensi\_set’, ‘on\_load’: None, ‘self’: \, ‘exclude’: None, ‘get\_session\_id’: None, ‘on\_exit’: None, ‘progress’: \, ‘config’: {‘dataset’: ‘ensi\_set’, ‘port’: 8080, ‘auto\_create’: True, ‘show\_bounding\_box\_center’: False, ‘host’: ‘localhost’, ‘choice\_style’: ‘single’, ‘ner\_manual\_require\_click’: False, ‘diff\_style’: ‘words’, ‘theme’: ‘basic’, ‘ner\_manual\_label\_style’: ‘list’, ‘split\_sents\_threshold’: False, ‘writing\_dir’: ‘ltr’, ‘batch\_size’: 10, ‘preview\_bounding\_boxes’: False, ‘show\_stats’: False, ‘custom\_theme’: {}, ‘choice\_auto\_accept’: False, ‘api\_keys’: {}, ‘show\_flag’: False, ‘label’: ‘all’, ‘instructions’: False, ‘db\_settings’: {}, ‘swipe’: False, ‘hide\_meta’: False, ‘shade\_bounding\_boxes’: False, ‘html\_template’: False, ‘darken\_image’: 0, ‘card\_css’: False, ‘cors’: True, ‘db’: ‘sqlite’, ‘lang’: ‘de’}, ‘update’: \\>, ‘view\_id’: ‘ner’, ‘db’: True} 14:39:59 - VALIDATE: Creating validator for view ID ‘ner’ 14:39:59 - DB: Initialising database SQLite 14:39:59 - DB: Connecting to database SQLite 14:39:59 - DB: Loading dataset ‘ensi\_set’ (0 examples) 14:39:59 - DB: Creating dataset ‘2018-06-13\_14-39-59’ {‘created’: datetime.datetime(2018, 6, 13, 11, 45, 19), ‘description’: ‘ENSI-2017’, ‘author’: ‘RalfBendzko’} 14:39:59 - CONTROLLER: Validating the first batch 14:39:59 - CONTROLLER: Iterating over stream 14:39:59 - PREPROCESS: Splitting sentences {‘stream’: \, ‘min\_length’: None, ‘batch\_size’: 32, ‘nlp’: \, ‘text\_key’: ‘text’} 14:39:59 - FILTER: Filtering duplicates from stream {‘by\_input’: True, ‘stream’: \, ‘by\_task’: True} 14:39:59 - FILTER: Filtering out empty examples for key ‘text’ 14:39:59 - FILTER: Skipping invalid ‘text’ task {‘text’: ‘’, ‘\_task\_hash’: 1839039364, ‘\_input\_hash’: 616230852} 14:40:00 - MODEL: Predicting spans for batch (batch size 64) 14:40:00 - MODEL: Sorting batch by entity type (batch size 32) ? Starting the web server at [http://localhost:8080](http://localhost:8080) … Open the app in your browser and start annotating!" ---
**Author:** ![Ralf](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ralf/32/4176_2.png) [@Ralf](https://support.prodi.gy/u/Ralf)\ **Post date:** [June 13, 2018, 12:44pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/13 "2018-06-13T12:44:15Z")
interestingly, the buttons on the web-GUI do work. But the error message does not disappear and fills the whole screen. ---
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [June 13, 2018, 1:04pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/14 "2018-06-13T13:04:56Z")
@mayurbhangale I just had a look at your log and it lists the version as `'version': '1.5.0'`. So maybe something didn't upgrade correctly? This might also explain the platform differences (because in general, it's pretty mysterious why the web app would work on one system and not on the other – usually, this would always indicate a deeper problem with the back-end serving the front-end.) > [@Buffer and memoryview are not contiguous in the same dimension.](https://support.prodi.gy/t/buffer-and-memoryview-are-not-contiguous-in-the-same-dimension/609/13): > > the buttons on the web-GUI do work. Yeah, if possible, the Prodigy app always tries to localise the error and will only fail on the part that's causing it, so you never get a full crash. As a quick sanity check, the log for `GET: /get_questions` (after the server started) correctly shows `1.5.1` as the version? And if you run `prodigy stats`, the version is also correct? ---
**Author:** ![mayurbhangale](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/mayurbhangale/32/155_2.png) [@mayurbhangale](https://support.prodi.gy/u/mayurbhangale)\ **Post date:** [June 13, 2018, 1:20pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/15 "2018-06-13T13:20:33Z")
@ines Clean Installed in multiple environments. Same error. It does seem to respond to buttons and save annotations. ---
**Author:** ![Ralf](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ralf/32/4176_2.png) [@Ralf](https://support.prodi.gy/u/Ralf)\ **Post date:** [June 13, 2018, 1:29pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/16 "2018-06-13T13:29:22Z")
version: (spacy\_e) C:\WINDOWS\system32\>python -m prodigy stats 15:28:55 - DB: Initialising database SQLite 15:28:55 - DB: Connecting to database SQLite ? Prodigy stats Location C:\Anaconda3\envs\spacy\_e\lib\site-packages\prodigy Version 1.5.1 Total Datasets 2 Database Name SQLite Prodigy Home G:\OneDrive - Bircomp GmbH\ralf\Documents.prodigy Platform Windows-10-10.0.17134-SP0 Database Id sqlite Total Sessions 10 Python Version 3.5.4 ---
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [June 13, 2018, 1:57pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/17 "2018-06-13T13:57:00Z")
@mayurbhangale I was just asking because your log shows version `1.5.0` and this usually means that at least the `about.py` of the package is the one shipped with the previous version (since this is where the version identifier is taken from). @Ralf Thanks for your patience! I’ve been pulling my hair out over this for the past hour or so 🤯 But I think I might have the solution: in your `prodigy.json`, try setting the following explicitly: ```json "card_css": {} ``` You can also remove the entry from your `prodigy.json` – based on your log, it looks like you likely have a `prodigy.json` file _somewhere_ (usually in your home directory in `.prodigy`) that’s populated with some default values, including `"card_css": false`. This was the default suggested in the docs – but under certain circumstances, it would actually cause this error. I’ve already adjusted the documentation accordingly. It’s especially frustrating because we actually planned on shipping JSON schema-based `prodigy.json` validation in `v1.5.1` that would have output a warning for exactly that – but we decided against it because we wanted to give it more thorough testing 😩 ---
**Author:** ![Ralf](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ralf/32/4176_2.png) [@Ralf](https://support.prodi.gy/u/Ralf)\ **Post date:** [June 13, 2018, 4:41pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/18 "2018-06-13T16:41:41Z")
Thank you very much!!! 1. you have been right, I had a second prodigy.json with the entry “card\_css”: false. 2. altering the entry to “card\_css”: {}, did the trick. ---
**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\ **Post date:** [June 13, 2018, 4:54pm UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/19 "2018-06-13T16:54:17Z")
Ahhhh, I’m so glad it worked 🎉 Sorry again! I’ve already added the fix to prevent this sort of stuff in the next version. I also moved the posts over to this thread, which turned out to be related to the same problem. ---
**Author:** ![baeumer](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/baeumer/32/260_2.png) [@baeumer](https://support.prodi.gy/u/baeumer)\ **Post date:** [June 21, 2018, 7:46am UTC](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595/20 "2018-06-21T07:46:52Z")
Thank you so much for this thread. I was going crazy this morning after updating to 1.5.1. But the trick with the css value solved the issue. But serious: In my case there was no error message at all. Just this meaningless Oops-Error in the Frontend. Not helpful to find the error by my own! [Next page](https://support.prodi.gy/t/prodigy-json-setting-causes-web-app-error/595.md?page=2)