594211 - library list doesn't include core library

Status: RESOLVED FIXED

(Mozilla Labs Graveyard :: FlightDeck, defect)

Description

[Myk Melez [:myk] [@mykmelez]]

In the editor on the installation of FlightDeck on the staging server, the list of libraries on which an addon depends doesn't include the core library.  It does include other libraries on which an addon depends, however, and the number of libraries in the "Libraries" header contains the correct number.

For example, I created an addon whose editor page is at this URL:

https://lm-app-flightdeck-stage01.mozillalabs.com/addon/edit/1001972/latest/

I haven't made any changes to it, however.  Its number of libraries is one (1), but when I click the Libraries header to open the list of libraries, I see no libraries in the list.

And here's the View Source link for another one of my addons:

https://lm-app-flightdeck-stage01.mozillalabs.com/addon/1000190/latest/

It depends on two libraries: the core library, and a library called org.mozilla.myk.  But only the latter library shows up in the list.

I mentioned this problem to Piotr a few hours ago, and he thought it was the result of a bug he had fixed on the release branch.  So Zandr restaged the release, including recloning the production database to the staging database and reloading the 0.6 and 0.7 SDKs into the database.  But that hasn't solved the problem.

Marking this as a 1.0a5 blocker, as we clearly can't ship with this major problem in one of the release's key new features.

Piotr: do you have any thoughts on what the problem might be?

Comment 1

[Piotr Zalewa [:zalun]]

I can't replicate the problem. It's working on flightdeck.zalewa.info when on release-1.0a5 branch, the same with local version.
Without read access to the staging server (at least to database) I can't really say what's going on.

Comment 2

[Zandr Milewski [:zandr]]

Piotr- I just emailed you a database dump.

Comment 3

[Myk Melez [:myk] [@mykmelez]]

Piotr: can you use the database dump Zandr sent you to try to reproduce the problem?

As an aside, in order for us to graduate this application to "product" status (hosting it on product-grade infrastructure, giving it a product-grade domain name like builder.addons.mozilla.org, having the AMO team take on the responsibility for designing, developing, and managing it, etc.), it absolutely has to be possible for the application to be staged and deployed by IT staff without manual intervention by developers.

It's not clear what the issue is here (a bug in the code, an issue with the documentation on installing and configuring the application, a difference in the setup of the dev versus staging servers, etc.).  But whatever it is, we need to work these things out and establish the code development and deployment practices and processes that make it possible for us to hand the code to IT for them to deploy.

Comment 4

[Piotr Zalewa [:zalun]]

Zandr, thanks for the database.
It is running on my local machine with this database on release-1.0a5 branch.
Could this depend on database setup?

Comment 5

[Piotr Zalewa [:zalun]]

It could also be the environment.
Here is my full output of "yolk -l"

BeautifulSoup   - 3.1.0.1      - active 
Django          - 1.2.1        - active 
Markdown        - 2.0.3        - active 
MySQL-python    - 1.2.3        - active 
PIL             - 1.1.7        - active 
Python          - 2.6.5        - active development (/usr/lib/python2.6/lib-dynload)
South           - 0.7.1        - active 
django-debug-toolbar - 0.8.3        - active 
django-extensions - 0.5          - active 
django-haystack - 1.1.0-alpha  - active development (/home/zalun/Projects/FlightDeck/flightdeckenv/src/django-haystack)
docutils        - 0.7          - active 
elementtree     - 1.2.7-20070827-preview - active 
mechanize       - 0.2.2        - active 
pip             - 0.7.2        - active 
setuptools      - 0.6c11       - active 
simplejson      - 2.1.1        - active 
wsgiref         - 0.1.2        - active development (/usr/lib/python2.6)
yolk            - 0.4.1        - active

Comment 6

[Myk Melez [:myk] [@mykmelez]]

Zandr found and fixed an issue on the staging server that was causing this problem, so it has now been resolved.