A routine gem update ended up creating $73k worth of subscriptions
1–10 of 336 posts
Re: A routine gem update ended up creating $73k worth of subscriptions
#2This sort of behavior change in a dependency would make me blacklist the dependency.
Re: A routine gem update ended up creating $73k worth of subscriptions
#3This sort of behavior change in a dependency would make me blacklist the dependency.
I shun everything MongoDB because of how immature its engineering culture is.
Re: A routine gem update ended up creating $73k worth of subscriptions
#4Re: A routine gem update ended up creating $73k worth of subscriptions
#5This sort of behavior change in a dependency would make me blacklist the dependency.
They fixed the issue, reversed everything, wrote a detailed explanation of what happened and apologized to their users. I don't think you can expect much better than this to be honest?
Re: A routine gem update ended up creating $73k worth of subscriptions
#6Mongoid docs[1] seem to be pretty cool about this change:
"As of Mongoid 7.1, logical operators (and, or, nor and not) have been changed to have the the same semantics as those of ActiveRecord. To obtain the semantics of or as it behaved in Mongoid 7.0 and earlier, use any_of which is described below."
Is it just me or is this one of the most terrible breaking changes in a popular, official library ever?
[1] https://docs.mongodb.com/mongoid/current/tutorials/mongoid-q...
Re: A routine gem update ended up creating $73k worth of subscriptions
#7Mongoid docs[1] seem to be pretty cool about this change: "As of Mongoid 7.1, logical operators (and, or, nor and not) have been changed to have the the same semantics as those of ActiveRecord. To obtain the semantics of or as it behaved in Mongoid 7.0 and earlier, use any_of which is described below." Is it just me or is this one of the most terrible breaking changes in a popular, official library ever? [1] https://…
The SerpAPI blog author seems cool about it, too.
After such a problem, I would roll back and never ever update this dependency again.
Re: A routine gem update ended up creating $73k worth of subscriptions
#8That sounds like a major, incredibly dangerous update to the DB driver. Their 7.1, 7.2, 7.3 versions seem to all have breaking changes [1].
Yet they are in obvious violation of SemVer expectations, which they declare to follow [2]:
> Mongoid follows versioning guidelines as outlined by the Semantic Versioning Specification, so you can expect only backwards incompatible changes in major versions [sic]
[1] https://docs.mongodb.com/mongoid/current/tutorials/mongoid-u...
[2] https://mongoid.github.io/old/en/mongoid/docs/upgrading.html
Re: A routine gem update ended up creating $73k worth of subscriptions
#9This sort of behavior change in a dependency would make me blacklist the dependency.
They fixed the issue, reversed everything, wrote a detailed explanation of what happened and apologized to their users. I don't think you can expect much better than this to be honest?
I’m not blaming them: I’m saying that if I was in this position, I’d ban the Mongo library used.
Re: A routine gem update ended up creating $73k worth of subscriptions
#10This sort of behavior change in a dependency would make me blacklist the dependency.
They fixed the issue, reversed everything, wrote a detailed explanation of what happened and apologized to their users. I don't think you can expect much better than this to be honest?
I believe the dependency OP is referring to is mongoid. I think serpapi did all the right things here.