#1970 ✓worksforme
Chris Webb

Getting "!! Warning: could not load core command file" when deploying to Heroku

Reported by Chris Webb | August 16th, 2015 @ 11:18 PM | in 1.3.2 (closed)

When moving from Play version 1.3.x-1.3.1-17-gf193e1a to 1.3.x-1.3.1-47-gce4e56f I get warnings when pushing the application to Heroku as follows:

uk-m-cwebb:PTAsocial-MVP chriswebb$ git push staging trello#4080-send-conversation-post-async:master
Counting objects: 4, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 406 bytes | 0 bytes/s, done.
Total 4 (delta 3), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote: 
remote: -----> Fetching custom git buildpack... done
remote: -----> Play! app detected
remote: -----> Installing OpenJDK 1.8... done
remote: -----> Updating Play! version. Previous version was 1.3.x-1.3.1-17-gf193e1a. Updating to 1.3.x-1.3.1-47-gce4e56f...
remote: -----> Installing Play! 1.3.x-1.3.1-47-gce4e56f.....
remote: -----> done
remote: -----> Building Play! application...
remote: ~
remote: ~ !! Warning: could not load core command file .___init__.py
remote: ~
remote: ~
remote: ~ !! Warning: could not load core command file ._autotest.py
remote: ~
remote: ~
remote: ~ !! Warning: could not load core command file ._deps.py
remote: ~
remote: ~
remote: ~ !! Warning: could not load core command file ._javadoc.py
remote: ~
remote:        ~        _            _ 
remote:        ~  _ __ | | __ _ _  _| |
remote:        ~ | '_ \| |/ _' | || |_|
remote:        ~ |  __/|_|\____|\__ (_)
remote:        ~ |_|            |__/   
remote:        ~
remote:        ~ play! 1.3.x-1.3.1-47-gce4e56f, https://www.playframework.com
remote:        ~
remote:        1.3.x-1.3.1-47-gce4e56f
remote:        Building Play! application at directory ./
remote:        Resolving dependencies: .play/play dependencies ./ --forProd --forceCopy --silent -Duser.home=/tmp/build_2d3aa963b9cd1204d2855bdca329b9b6 2>&1
remote:        ~
remote:        ~ !! Warning: could not load core command file .___init__.py
remote:        ~
remote:        ~
remote:        ~ !! Warning: could not load core command file ._autotest.py
remote:        ~
remote:        ~
remote:        ~ !! Warning: could not load core command file ._deps.py
remote:        ~
remote:        ~
remote:        ~ !! Warning: could not load core command file ._javadoc.py
remote:        ~
remote:        Picked up JAVA_TOOL_OPTIONS: -Djava.net.preferIPv4Stack=true
remote:        :: loading settings :: file = /tmp/build_2d3aa963b9cd1204d2855bdca329b9b6/.ivy2/ivysettings.xml
remote:        ~ Resolving dependencies using /tmp/build_2d3aa963b9cd1204d2855bdca329b9b6/conf/dependencies.yml,

If I roll back the Play version to 1.3.x-1.3.1-17-gf193e1a the warning messages go away. I did a diff between the two framework release packages and there was nothing obvious that could be causing the problem. Looking back through the commits there was only one commit that touched on the Python commands but it was to do with Selenium testing.

The build seems to complete successfully and the application launches but it's disconcerting and I'd feel better if the warnings weren't there. I've attached the two packages.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Pages