search

heroku / legacy-cli

Heroku CLI
https://cli.heroku.com
MIT License
1.36k stars 381 forks source link

heroku local malfunctions versus heroku cloud deployed App #2066

Closed pbmorton closed 6 years ago

pbmorton commented 6 years ago

I have a java webapp on heroku. It runs perfectly on the cloud. But when run locally it appears to use a stale resource. My jar is called nymmbl1-1.0.jar. I have 100% verified the resource is correct in target\nymmbl1-1.0.jar and ~.m2\repository\com\nymmbl\nymmbl1\1.0\nymmbl1-1.0.jar. When run locally the resource is old. It's as though heroku local is using some cached version.

Has anyone ever seen anything like this?

The out-of-date resource is a local read-only SQlite database. When running "heroku local" the database is accessed but the content returned is different than the actual database content in the current jar. The content returned is from an older version of the SQLite DB that is not in the current JAR.

As I said, this problem is not observed when run on the cloud.

My guess is that "heroku local" is doing something I don't expect. Can you suggest what may be the problem or how to debug this?

pbmorton commented 6 years ago

This issue was opened in the wrong place. I'm closing it here and reopening it at https://github.com/heroku/heroku-apps/issues/202