search

quavedev / meteor-packages

8 stars 2 forks source link

There is already a collection named "cronHistory" error #1

Closed kolyasya closed 1 month ago

kolyasya commented 6 months ago

Hey, I replaced the package with

meteor remove littledata:synced-cron && meteor add quave:synced-cron

And now I get such error:

image

I tried to drop the collection, but after restart I still get the same result.

Rolling back to littledata:synced-cron fixes the issue.

Also I tried to disable all the custom SyncedCron code I have (SyncedCron.config, SyncedCron.start and etc.) It didn't help.

I'm testing it with Meteor 2.x. Is that an issue?

filipenevola commented 1 month ago

@joaovictornsv I think you got a similar error, right?

And yes, it could be related with Meteor 2.

I'll take a look in the next 2 weeks.

joaovictornsv commented 1 month ago

@joaovictornsv I think you got a similar error, right?

And yes, it could be related with Meteor 2.

I'll take a look in the next 2 weeks.

Yes, I got a similar error.

In my case, I needed to change the collection name to be able to work with quave:synced-cron.

filipenevola commented 1 month ago

In my case, I needed to changed the collection name to be able to work with quave:synced-cron.

That shouldn't be necessary, I'll check soon.

filipenevola commented 1 month ago

@kolyasya I'm not getting this error.

There was a version where MongoDB threw a different user error, but that's fixed in our current versions.

Are you running an older MongoDB version?

Please reopen the issue if you're still experiencing this problem.

BTW, we just released a new version with new features. Check them out here: https://github.com/quavedev/meteor-packages/blob/main/synced-cron/CHANGELOG.md#209-2024-10-07