default Admin view lists wrong # of active collectors

[libbyh]

Most of these projects has at least one active collector, and it shows as active on the project's individual page.

[pratik27shah]

Hi,The backend part to fix the issue has been completed with the database on the server,now i need to make changes in the code to make this functionality dynamic

[libbyh]

Can you explain what all you had to change?

On Wed, Mar 22, 2017 at 6:18 PM, Pratik Shah notifications@github.com wrote:

Hi,The backend part to fix the issue has been completed with the database on the server,now i need to make changes in the code to make this functionality dynamic

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/casmlab/stack/issues/1#issuecomment-288569499, or mute the thread https://github.com/notifications/unsubscribe-auth/AALIzqpVyvdACWqWxzTVY6yIlTVZlWiNks5roaxagaJpZM4LxwD1 .

[pratik27shah]

on the backend their is a Db named config which consist of list of active collectors,but by default all of them were set to 0 ,so for now,,before the entire functionality is complete I changed active to 1 for all active collectors...

[libbyh]

Do you know where in the code those values get set? We should fix the underlying problem if they're being set wrong.

On Thu, Mar 23, 2017 at 11:21 PM Pratik Shah notifications@github.com wrote:

on the backend their is a Db named config which consist of list of active collectors,but by default all of them were set to 0 ,so for now,,before the entire functionality is complete I changed active to 1 for all active collectors...

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/casmlab/stack/issues/1#issuecomment-288929913, or mute the thread https://github.com/notifications/unsubscribe-auth/AALIzqj0Q8dDL_cMdDIWRpwtMqC6q_-Sks5ro0TSgaJpZM4LxwD1 .

-- Messages by Libby. Typos by iPhone.

[pratik27shah]

Yes currently I am working on it...but please take the git update to and restart the server,so that the other fixed issues can be pushed to production...

[libbyh]

Done. Waiting to close the issue until the underlying problem is solved.

[pratik27shah]

the issue has been fixed works fine on local,,need to test on the production,,please take git update and restart server

[pratik27shah]

command to update in db db.config.update({"collectors.name":"wnipd"},{$set:{"collectors.0.active":1}},{upsert:true})

[libbyh]

That collector isn't actually active as far as I can tell. How can we write the update to reflect only those that are running and really collecting data?

On Sun, Mar 26, 2017 at 1:52 AM, Pratik Shah notifications@github.com wrote:

command to update in db db.config.update({"collectors.name ":"wnipd"},{$set:{"collectors.0.active":1}},{upsert:true})

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/casmlab/stack/issues/1#issuecomment-289262390, or mute the thread https://github.com/notifications/unsubscribe-auth/AALIzpI04e4GM-cvcvekU0aCGuNjMijiks5rpgtGgaJpZM4LxwD1 .

[pratik27shah]

this is only an example to update the db manually...directly through mongo..without using the code...if required in future..this is the syntax of the command.The code changes have been made to update the active collector value only when the collector has been started

[libbyh]

These values are wrong again. Not sure what happened here.

Collectors for potus45, queer-fans, and mil2 are all running.

[pratik27shah]

needs discussion.

[libbyh]

Let's just delete the column - users can find out what's active by clicking on the collector to view its details.

[pratik27shah]

the UI has been changed..but it is not very pleasing,I suggest you have a look at it once,before closing the issue

[libbyh]

It looks ok. I can worry about the third column later.