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

Issue in Commit 1246bf70 - Cannot succeed in ./bin/startup #21443

Open
yousefmarey12 opened this issue Dec 30, 2024 · 1 comment
Open

Issue in Commit 1246bf70 - Cannot succeed in ./bin/startup #21443

yousefmarey12 opened this issue Dec 30, 2024 · 1 comment
Labels
bug always open for contribution

Comments

@yousefmarey12
Copy link
Contributor

Recently, my terminal could not succeed in ./bin/startup. It worked perfectly around 15 days ago. After a through investigation, it had to do with the recent subforem commits as it stated:

PG::UndefinedColumn: ERROR: column site_configs.subforem_id does not exist (ActiveRecord::StatementInvalid)

I was going crazy until I played around with the previous commits, and realized that on 1246bf7 this issue persisted. I could not do ./bin/setup nor could I do ./bin/startup as it would provide me the above error.

The problem looks like we are accessing site_configs[:subforem_id], but it doesn't really exist.

image

To Reproduce

  1. git reset --hard 1246bf7011a5339ca3cb8de6a95b1b7f6f3ac8aa This will go to where the problem first begins. Try to do ./bin/setup or ./bin/startup.
  2. Notice that you won't succeed due to the specified error above.
  3. Go to the commit before it (provided here for your convience) git reset --hard e51317f66b27bd720a406e6c3d99481f1068ba51 and you will realize that ./bin/startup and ./bin/setup work perfectly.

Expected behavior

./bin/startup and ./bin/setup should work for all commits

Screenshots

Desktop (please complete the following information):

  • OS, version: Ubuntu 22.04.3 LTS
  • Browser, version: Not applicable
@yousefmarey12 yousefmarey12 added the bug always open for contribution label Dec 30, 2024
Copy link
Contributor

Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you.

To our amazing contributors: issues labeled bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.

If this is a feature request from an external contributor (not core team at Forem), please close the issue and re-post via GitHub Discussions.

To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem-team. The OSS Community Manager or the engineers on OSS rotation will follow up.

For full info on how to contribute, please check out our contributors guide.

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

No branches or pull requests

1 participant