Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

500 error when notifying subscribers #205

Open
btaitelb opened this issue May 24, 2016 · 3 comments
Open

500 error when notifying subscribers #205

btaitelb opened this issue May 24, 2016 · 3 comments

Comments

@btaitelb
Copy link
Member

This was for https://www.railsschool.org/l/contributing-to-an-open-source-rails-project and the tweet message was Learn how to contribute to open source projects @railsschool #cville {{url}}

Error from heroku logs:

2016-05-24T18:54:26.328518+00:00 app[web.1]: ActiveRecord::StatementInvalid (PG::StringDataRightTruncation: ERROR: value too long for type character varying(140)
2016-05-24T18:54:26.309961+00:00 app[web.1]: Completed 500 Internal Server Error in 641ms (ActiveRecord: 14.2ms)

The tweet and emails both went out, so this is just a db issue. I suggest increasing the column limits here.

@gkop gkop mentioned this issue May 24, 2016
@btaitelb
Copy link
Member Author

Closing this, as it looks like it was already fixed, we just needed to run rake db:migrate.

@btaitelb
Copy link
Member Author

I'm still getting this issue when I try to notify attendees.

@btaitelb btaitelb reopened this Jun 15, 2016
@levans248
Copy link
Contributor

levans248 commented Jun 15, 2016

Looks like master was never pushed up to heroku after the fix for this was merged. I pushed master up and ran the migration and length limit of 140 has now been removed so I do not think that anything else needs to be done. @btaitelb I think that this can be closed again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants