Heroku can't convert String into Integer on migrate
I'm trying to migrate some database changes to my Heroku app. I'm getting an error message, but it's not really eluding to the issue that's cause it to not migrate.
When running heroku run rake db:migrate --appname
I get this error
can't convert String into Integer
.heroku/client/lib/heroku/jsplugin.rb:70:in `'
.heroku/client/lib/heroku/jsplugin.rb:70:in `commands'
.heroku/client/lib/heroku/jsplugin.rb:272:in `find_command'
.heroku/client/lib/heroku/jsplugin.rb:23:in `try_takeover'
.heroku/client/lib/heroku/cli.rb:28:in `start'
/usr/local/bin/heroku:24:in `<main>'
! Heroku client internal error.
! Search for help at: https://help.heroku.com
! Or report a bug at: https://github.com/heroku/heroku/issues/new
Error: can't convert String into Integer (TypeError)
Command: heroku run rake db:migrate --appname
Version: heroku-toolbelt/3.43.12 (x86_64-darwin10.8.0) ruby/1.9.3
I though it may be because i'm using PG and I changed a decimal column to an integer. So i removed the column in question and still having the same issue. I removed all data from the database too, but still no luck.
ruby-on-rails heroku ruby-on-rails-5
asked Nov 22 '18 at 23:27
DollarChillsDollarChills
4551620
add a comment |
I'm trying to migrate some database changes to my Heroku app. I'm getting an error message, but it's not really eluding to the issue that's cause it to not migrate.
When running heroku run rake db:migrate --appname
I get this error
can't convert String into Integer
.heroku/client/lib/heroku/jsplugin.rb:70:in `'
.heroku/client/lib/heroku/jsplugin.rb:70:in `commands'
.heroku/client/lib/heroku/jsplugin.rb:272:in `find_command'
.heroku/client/lib/heroku/jsplugin.rb:23:in `try_takeover'
.heroku/client/lib/heroku/cli.rb:28:in `start'
/usr/local/bin/heroku:24:in `<main>'
! Heroku client internal error.
! Search for help at: https://help.heroku.com
! Or report a bug at: https://github.com/heroku/heroku/issues/new
Error: can't convert String into Integer (TypeError)
Command: heroku run rake db:migrate --appname
Version: heroku-toolbelt/3.43.12 (x86_64-darwin10.8.0) ruby/1.9.3
I though it may be because i'm using PG and I changed a decimal column to an integer. So i removed the column in question and still having the same issue. I removed all data from the database too, but still no luck.
ruby-on-rails heroku ruby-on-rails-5
asked Nov 22 '18 at 23:27
DollarChillsDollarChills
4551620
You tried $ heroku restart, $ heroku pg:reset DATABASE, $ heroku run rake db:migrate ?
– Clyde T
Nov 22 '18 at 23:42
Each of those commands give me the same error.
– DollarChills
Nov 22 '18 at 23:45
Looks like the problem is somewhere in the Heroku client itself. Do you have the latest Heroku tools installed? Do you have a more up-to-date Ruby than 1.9.3 available?
– mu is too short
Nov 23 '18 at 0:07
1
I have ruby 2.4.1p111. I just did a heroku --version command and got the same error. So may need updating.
– DollarChills
Nov 23 '18 at 0:14
It was the issue. As soon as i updated to the latest version of Heroku tools it worked. @mu would you like to create an answer and I'll accept?
– DollarChills
Nov 23 '18 at 0:18
add a comment |
I'm trying to migrate some database changes to my Heroku app. I'm getting an error message, but it's not really eluding to the issue that's cause it to not migrate.
When running heroku run rake db:migrate --appname
I get this error
can't convert String into Integer
.heroku/client/lib/heroku/jsplugin.rb:70:in `'
.heroku/client/lib/heroku/jsplugin.rb:70:in `commands'
.heroku/client/lib/heroku/jsplugin.rb:272:in `find_command'
.heroku/client/lib/heroku/jsplugin.rb:23:in `try_takeover'
.heroku/client/lib/heroku/cli.rb:28:in `start'
/usr/local/bin/heroku:24:in `<main>'
! Heroku client internal error.
! Search for help at: https://help.heroku.com
! Or report a bug at: https://github.com/heroku/heroku/issues/new
Error: can't convert String into Integer (TypeError)
Command: heroku run rake db:migrate --appname
Version: heroku-toolbelt/3.43.12 (x86_64-darwin10.8.0) ruby/1.9.3
I though it may be because i'm using PG and I changed a decimal column to an integer. So i removed the column in question and still having the same issue. I removed all data from the database too, but still no luck.
ruby-on-rails heroku ruby-on-rails-5
asked Nov 22 '18 at 23:27
DollarChillsDollarChills
4551620
I'm trying to migrate some database changes to my Heroku app. I'm getting an error message, but it's not really eluding to the issue that's cause it to not migrate.
When running heroku run rake db:migrate --appname
I get this error
can't convert String into Integer
.heroku/client/lib/heroku/jsplugin.rb:70:in `'
.heroku/client/lib/heroku/jsplugin.rb:70:in `commands'
.heroku/client/lib/heroku/jsplugin.rb:272:in `find_command'
.heroku/client/lib/heroku/jsplugin.rb:23:in `try_takeover'
.heroku/client/lib/heroku/cli.rb:28:in `start'
/usr/local/bin/heroku:24:in `<main>'
! Heroku client internal error.
! Search for help at: https://help.heroku.com
! Or report a bug at: https://github.com/heroku/heroku/issues/new
Error: can't convert String into Integer (TypeError)
Command: heroku run rake db:migrate --appname
Version: heroku-toolbelt/3.43.12 (x86_64-darwin10.8.0) ruby/1.9.3
I though it may be because i'm using PG and I changed a decimal column to an integer. So i removed the column in question and still having the same issue. I removed all data from the database too, but still no luck.
ruby-on-rails heroku ruby-on-rails-5
ruby-on-rails heroku ruby-on-rails-5
asked Nov 22 '18 at 23:27
DollarChillsDollarChills
4551620
asked Nov 22 '18 at 23:27
DollarChillsDollarChills
4551620
asked Nov 22 '18 at 23:27
DollarChillsDollarChills
4551620
asked Nov 22 '18 at 23:27
DollarChillsDollarChills
4551620
asked Nov 22 '18 at 23:27
DollarChillsDollarChills
4551620
4551620
You tried $ heroku restart, $ heroku pg:reset DATABASE, $ heroku run rake db:migrate ?
– Clyde T
Nov 22 '18 at 23:42
Each of those commands give me the same error.
– DollarChills
Nov 22 '18 at 23:45
Looks like the problem is somewhere in the Heroku client itself. Do you have the latest Heroku tools installed? Do you have a more up-to-date Ruby than 1.9.3 available?
– mu is too short
Nov 23 '18 at 0:07
1
I have ruby 2.4.1p111. I just did a heroku --version command and got the same error. So may need updating.
– DollarChills
Nov 23 '18 at 0:14
It was the issue. As soon as i updated to the latest version of Heroku tools it worked. @mu would you like to create an answer and I'll accept?
– DollarChills
Nov 23 '18 at 0:18
add a comment |
You tried $ heroku restart, $ heroku pg:reset DATABASE, $ heroku run rake db:migrate ?
– Clyde T
Nov 22 '18 at 23:42
Each of those commands give me the same error.
– DollarChills
Nov 22 '18 at 23:45
Looks like the problem is somewhere in the Heroku client itself. Do you have the latest Heroku tools installed? Do you have a more up-to-date Ruby than 1.9.3 available?
– mu is too short
Nov 23 '18 at 0:07
1
I have ruby 2.4.1p111. I just did a heroku --version command and got the same error. So may need updating.
– DollarChills
Nov 23 '18 at 0:14
It was the issue. As soon as i updated to the latest version of Heroku tools it worked. @mu would you like to create an answer and I'll accept?
– DollarChills
Nov 23 '18 at 0:18
You tried $ heroku restart, $ heroku pg:reset DATABASE, $ heroku run rake db:migrate ?
– Clyde T
Nov 22 '18 at 23:42
You tried $ heroku restart, $ heroku pg:reset DATABASE, $ heroku run rake db:migrate ?
– Clyde T
Nov 22 '18 at 23:42
Each of those commands give me the same error.
– DollarChills
Nov 22 '18 at 23:45
Each of those commands give me the same error.
– DollarChills
Nov 22 '18 at 23:45
Looks like the problem is somewhere in the Heroku client itself. Do you have the latest Heroku tools installed? Do you have a more up-to-date Ruby than 1.9.3 available?
– mu is too short
Nov 23 '18 at 0:07
Looks like the problem is somewhere in the Heroku client itself. Do you have the latest Heroku tools installed? Do you have a more up-to-date Ruby than 1.9.3 available?
– mu is too short
Nov 23 '18 at 0:07
1
1
I have ruby 2.4.1p111. I just did a heroku --version command and got the same error. So may need updating.
– DollarChills
Nov 23 '18 at 0:14
I have ruby 2.4.1p111. I just did a heroku --version command and got the same error. So may need updating.
– DollarChills
Nov 23 '18 at 0:14
It was the issue. As soon as i updated to the latest version of Heroku tools it worked. @mu would you like to create an answer and I'll accept?
– DollarChills
Nov 23 '18 at 0:18
It was the issue. As soon as i updated to the latest version of Heroku tools it worked. @mu would you like to create an answer and I'll accept?
– DollarChills
Nov 23 '18 at 0:18
add a comment |
1 Answer
1
active
oldest
votes
Looks to me like you have an old version of the Heroku client (from heroku-toolbelt 3.43.12) and an old version of Ruby (1.9.3). AFAIK heroku-toolbelt isn't even used anymore, that's been superseded by a new Heroku client. Ruby 1.9.3 is no longer supported so shouldn't be used.
Perhaps your version of the toolbelt and your version of Ruby are incompatible with each other, perhaps they're incompatible with Heroku's current API. In any case, upgrading to new versions of both would be a good starting point.
answered Nov 23 '18 at 0:43
mu is too shortmu is too short
351k58688667
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53439058%2fheroku-cant-convert-string-into-integer-on-migrate%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Looks to me like you have an old version of the Heroku client (from heroku-toolbelt 3.43.12) and an old version of Ruby (1.9.3). AFAIK heroku-toolbelt isn't even used anymore, that's been superseded by a new Heroku client. Ruby 1.9.3 is no longer supported so shouldn't be used.
Perhaps your version of the toolbelt and your version of Ruby are incompatible with each other, perhaps they're incompatible with Heroku's current API. In any case, upgrading to new versions of both would be a good starting point.
answered Nov 23 '18 at 0:43
mu is too shortmu is too short
351k58688667
add a comment |
Looks to me like you have an old version of the Heroku client (from heroku-toolbelt 3.43.12) and an old version of Ruby (1.9.3). AFAIK heroku-toolbelt isn't even used anymore, that's been superseded by a new Heroku client. Ruby 1.9.3 is no longer supported so shouldn't be used.
Perhaps your version of the toolbelt and your version of Ruby are incompatible with each other, perhaps they're incompatible with Heroku's current API. In any case, upgrading to new versions of both would be a good starting point.
answered Nov 23 '18 at 0:43
mu is too shortmu is too short
351k58688667
add a comment |
Looks to me like you have an old version of the Heroku client (from heroku-toolbelt 3.43.12) and an old version of Ruby (1.9.3). AFAIK heroku-toolbelt isn't even used anymore, that's been superseded by a new Heroku client. Ruby 1.9.3 is no longer supported so shouldn't be used.
Perhaps your version of the toolbelt and your version of Ruby are incompatible with each other, perhaps they're incompatible with Heroku's current API. In any case, upgrading to new versions of both would be a good starting point.
answered Nov 23 '18 at 0:43
mu is too shortmu is too short
351k58688667
Looks to me like you have an old version of the Heroku client (from heroku-toolbelt 3.43.12) and an old version of Ruby (1.9.3). AFAIK heroku-toolbelt isn't even used anymore, that's been superseded by a new Heroku client. Ruby 1.9.3 is no longer supported so shouldn't be used.
Perhaps your version of the toolbelt and your version of Ruby are incompatible with each other, perhaps they're incompatible with Heroku's current API. In any case, upgrading to new versions of both would be a good starting point.
answered Nov 23 '18 at 0:43
mu is too shortmu is too short
351k58688667
answered Nov 23 '18 at 0:43
mu is too shortmu is too short
351k58688667
answered Nov 23 '18 at 0:43
mu is too shortmu is too short
351k58688667
answered Nov 23 '18 at 0:43
mu is too shortmu is too short
351k58688667
351k58688667
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53439058%2fheroku-cant-convert-string-into-integer-on-migrate%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You tried $ heroku restart, $ heroku pg:reset DATABASE, $ heroku run rake db:migrate ?
– Clyde T
Nov 22 '18 at 23:42
Each of those commands give me the same error.
– DollarChills
Nov 22 '18 at 23:45
Looks like the problem is somewhere in the Heroku client itself. Do you have the latest Heroku tools installed? Do you have a more up-to-date Ruby than 1.9.3 available?
– mu is too short
Nov 23 '18 at 0:07
1
I have ruby 2.4.1p111. I just did a heroku --version command and got the same error. So may need updating.
– DollarChills
Nov 23 '18 at 0:14
It was the issue. As soon as i updated to the latest version of Heroku tools it worked. @mu would you like to create an answer and I'll accept?
– DollarChills
Nov 23 '18 at 0:18