Developing my first Extension: MineMeld Server now reports ERROR RETRIEVING EXTENSIONS LIST

L2 Linker

Developing my first Extension: MineMeld Server now reports ERROR RETRIEVING EXTENSIONS LIST

I worked on my first extension today (based on the structure and files of youtube-miner).

 

As soon as I imported it into MineMeld I got the ERROR RETRIEVING EXTENSIONS LIST: INTERNAL SERVER ERROR red box of shame.   

 

What log should I be looking in for clues?  I've searched a bit and I know this was the path of the local folder.   I removed it but that hasn't helped.

 

/opt/minemeld/local/library/3238b8cf-ecb2-4d32-b5e8-afa8d0f68b91/

 

 

I found this in minemeld-web.log, 

 

[2018-12-23 23:21:18 EST] [29663] [ERROR] Exception on /extensions [GET]
Traceback (most recent call last):
  File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/flask/app.py", line 1982, in wsgi_app
    response = self.full_dispatch_request()
  File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/flask/app.py", line 1614, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/flask/app.py", line 1517, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/flask/app.py", line 1612, in full_dispatch_request
    rv = self.dispatch_request()
  File "/opt/minemeld/engine/current/local/lib/python2.7/site-packages/flask/app.py", line 1598, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/opt/minemeld/engine/core/minemeld/flask/aaa.py", line 125, in decorated_view
    return f(*args, **kwargs)
  File "/opt/minemeld/engine/core/minemeld/flask/aaa.py", line 135, in decorated_view
    return f(*args, **kwargs)
  File "/opt/minemeld/engine/core/minemeld/flask/extensionsapi.py", line 168, in list_extensions
    extensions = _get_extensions()
  File "/opt/minemeld/engine/core/minemeld/flask/extensionsapi.py", line 54, in _get_extensions
    return minemeld.extensions.extensions(library_directory)
  File "/opt/minemeld/engine/core/minemeld/extensions/manager.py", line 284, in extensions
    _installed = installed_extensions(installation_dir)
  File "/opt/minemeld/engine/core/minemeld/extensions/manager.py", line 265, in installed_extensions
    installed_extension = _load_metadata_from_dir(epath)
  File "/opt/minemeld/engine/core/minemeld/extensions/manager.py", line 206, in _load_metadata_from_dir
    metadata = json.load(f)
  File "/usr/lib/python2.7/json/__init__.py", line 291, in load
    **kw)
  File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.7/json/decoder.py", line 380, in raw_decode
    obj, end = self.scan_once(s, idx)
ValueError: Expecting property name: line 11 column 9 (char 425)
127.0.0.1 - - [23/Dec/2018:23:21:18 -0500] "GET /extensions?_=1545625278 HTTP/1.0" 500 291 "https://localhost/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0"
[2018-12-23 23:21:37 EST] [29663] [DEBUG] redis session connection pool: in use: 0 available: 1
L2 Linker

Re: Developing my first Extension: MineMeld Server now reports ERROR RETRIEVING EXTENSIONS LIST

Two additional learnings:   

 

- The file being referred to here was minemeld.json (I had a dangling comma )

 

ValueError: Expecting property name: line 11 column 9 (char 425)

 

- I hadn't actually removed the library folder (though I thought I had).  Once I deleted that (with the bad file), I was able to clear the error and reimport the Git project.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!