Skip to content

gem activerecord-sqlserver-adapter latest plugin not working to log message in database #942

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

Closed
vishwasFullStack opened this issue Sep 8, 2021 · 8 comments · Fixed by #943

Comments

@vishwasFullStack
Copy link

Issue

To store log in the database we are using td-aget 4.1.1 with the gem activerecord-sqlserver-adapter with version '6.1.0.0' but yesterday when we reinstall gem activerecord-sqlserver-adapter installed with the latest version 6.1.2.0.

This version is throwing "Uninitialized Constant Rails" Error .

image

We are trying to install the previous version, but it was also not available.

@harsh288
Copy link

harsh288 commented Sep 8, 2021

I'm getting the same error with fluentd configuration, it was working with the package "fluent-plugin-sql" but now getting errors like uninitialized constant Rails, can someone guide as early as possible, we are stuck.

@wpolicarpo
Copy link
Member

This was a regression coming from #941.

Sorry about that. I'll fix it and release a new version soon.

@harsh288
Copy link

harsh288 commented Sep 8, 2021

Sure @wpolicarpo, I'm waiting for the new version, just curious how can this be avoided in future since the previous version is gone, this will surely impact the production if the latest version is taken.

wpolicarpo added a commit that referenced this issue Sep 8, 2021
The adapter can be used outside a Rails context so TinyTDS appname config should
be able to be resolved if a Rails application was not detected.

Fix #942.
@wpolicarpo
Copy link
Member

@harsh288 not sure what you mean with previous version is gone. I'm not yanking 6.1.2.0 for now (but maybe I should).

wpolicarpo added a commit that referenced this issue Sep 8, 2021
The adapter can be used outside a Rails context so TinyTDS appname config should
be able to be resolved if a Rails application was not detected.

Fix #942.
@harsh288
Copy link

harsh288 commented Sep 8, 2021

@wpolicarpo I mean the version 6.1.1.0 & 6.1.0.0 (https://github.com/rails-sqlserver/activerecord-sqlserver-adapter/commit/6276e1b0f72561d1bec385d7aa712ffac5128458#diff-7b60b8e351cbb80c47459ffe2c79f1a26404871f49294780fe47ad0e58c09350

I believe the previous version is overridden, but if there is a way where I can still download the old version of the package like "gem install activerecord-sqlserver-adapter 6.1.0" then it would be safe since this has been tested.

@wpolicarpo
Copy link
Member

@harsh288 No, previous versions are not removed, they are available in RubyGems unless they are yanked.

You can either pin it down to 6.1.1.0 for now or wait a few minutes until I release a new version.

wpolicarpo added a commit that referenced this issue Sep 8, 2021
The adapter can be used outside a Rails context so TinyTDS appname config should
be able to be resolved if a Rails application was not detected.

Fix #942.
wpolicarpo added a commit that referenced this issue Sep 8, 2021
The adapter can be used outside a Rails context so TinyTDS appname config should
be able to be resolved if a Rails application was not detected.

Fix #942.
@wpolicarpo
Copy link
Member

Version 6.1.2.1 was released and contains a fix for that.

Can you please update your deps and let me know if you find any issues?

@harsh288
Copy link

harsh288 commented Sep 8, 2021

@wpolicarpo Thanks a lot for fixing this on priority.

lavika pushed a commit to lavika/activerecord-sqlserver-adapter that referenced this issue Sep 26, 2023
The adapter can be used outside a Rails context so TinyTDS appname config should
be able to be resolved if a Rails application was not detected.

Fix rails-sqlserver#942.
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

Successfully merging a pull request may close this issue.

3 participants