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

ns doesn't exist. #39

Closed
Siba94 opened this issue Jan 16, 2018 · 19 comments
Closed

ns doesn't exist. #39

Siba94 opened this issue Jan 16, 2018 · 19 comments

Comments

@Siba94
Copy link

Siba94 commented Jan 16, 2018

I am using 4.0 version of this bundle and whenever I run console command dtc:queue:count, it gives me a exception -> ns doesn't exist.

@mmucklo
Copy link
Owner

mmucklo commented Jan 17, 2018

I'll take a look

@mmucklo
Copy link
Owner

mmucklo commented Jan 17, 2018

May have fixed it in the PR, but I'll have to check it later...signing off for now.

mmucklo added a commit that referenced this issue Jan 17, 2018
…talled button (#40)

* Attempt to fix bin/console dtc:queue:count for all job types (issue #39), plus add a Prune Stalled button on the Running Jobs page

* make method protected

* update CHANGELOG for 4.1.0 release

* a few bug fixes for issues found in testing

* cs-fixes

* fix wording
@mmucklo
Copy link
Owner

mmucklo commented Jan 17, 2018

Please check if the issue is fixed in 4.1.0

@mmucklo
Copy link
Owner

mmucklo commented Jan 18, 2018

@Siba94 did the fix I did work?

@Siba94
Copy link
Author

Siba94 commented Jan 18, 2018

checking it right now. i'll let you know about it.

@Siba94
Copy link
Author

Siba94 commented Jan 18, 2018

No, still have the same issue.
I am following the documentation as mentioned for symfony3
Steps are :
1- Composer require.
2- Register the bundle in AppKernel.
3- Set up config.yml for MongoDB ODM
4- Set up routes in routing.yml
5- Set up security.yml to allow admins.
and then while doing dtc:queue:count it gives exception ns doesn't exist.

@mmucklo
Copy link
Owner

mmucklo commented Jan 18, 2018

@Siba94 - Oh I know what's going on - the database and collection don't exist yet in Mongo.

If you create then run a job, it should fix that, however I should see if there's a way to catch that before executing the count command.

@Siba94
Copy link
Author

Siba94 commented Jan 18, 2018

Thanks a lot. @mmucklo

mmucklo pushed a commit that referenced this issue Jan 20, 2018
mmucklo added a commit that referenced this issue Jan 21, 2018
* Should fix issue #39

* update .travis.yml

* fix for travis build with redis on 7.2

* php-cs-fixes
@mmucklo
Copy link
Owner

mmucklo commented Jan 21, 2018

@Siba94 could you verify now against release 4.2.0?

@Siba94
Copy link
Author

Siba94 commented Jan 21, 2018

@mmucklo Let me check. I will update you.

@mmucklo
Copy link
Owner

mmucklo commented Jan 22, 2018

@Siba94 Ok, thanks, let me know...

mmucklo added a commit that referenced this issue Jan 22, 2018
* Should fix issue #39

* work in progress on issue #42

* Store and show full redis counts per issue #42

* Add more unit tests, fix PhpRedis version

* try to fix flakey test, refactoring

* fix a bug in tests

* refactoring to hopefully help scrutinizer score
@Siba94
Copy link
Author

Siba94 commented Jan 22, 2018

@mmucklo still have the same issue. I had a job collection also as mentioned by you before running the count command create job first but when I run the count command it still generates the same exception.
I can see the jobs in waiting queue by following /dtc_queue/jobs route.
selection_018
selection_019
Here is the Exception details that i get in /dtc_queue route.
selection_025
selection_024
After running the run command, count command works perfectly..

@mmucklo
Copy link
Owner

mmucklo commented Jan 23, 2018

Ok, let me check it out.

@mmucklo
Copy link
Owner

mmucklo commented Jan 23, 2018

@Siba94,

I think I got it this time in 4.3.1 - yours is responding "ns doesn't exist" whereas mine was responding "namespace does not exist".

The code should now catch both.

Let me know,

--Matt

@mmucklo
Copy link
Owner

mmucklo commented Jan 24, 2018

@Siba94 - did 4.3.1 fix the issue for you?

@Siba94
Copy link
Author

Siba94 commented Jan 25, 2018

@mmucklo let me check it

@mmucklo
Copy link
Owner

mmucklo commented Jan 25, 2018

@Siba94 - ok thanks once again...

@Siba94
Copy link
Author

Siba94 commented Jan 26, 2018

Thanks a lot @mmucklo it's working perfectly.

@mmucklo
Copy link
Owner

mmucklo commented Jan 26, 2018

@Siba94 - good news thanks. Closing the issue.

@mmucklo mmucklo closed this as completed Jan 26, 2018
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