-
Notifications
You must be signed in to change notification settings - Fork 0
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
default Admin view lists wrong # of active collectors #1
Comments
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 |
Can you explain what all you had to change?
…On Wed, Mar 22, 2017 at 6:18 PM, Pratik Shah ***@***.***> 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
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AALIzqpVyvdACWqWxzTVY6yIlTVZlWiNks5roaxagaJpZM4LxwD1>
.
|
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... |
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 ***@***.***> 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
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AALIzqj0Q8dDL_cMdDIWRpwtMqC6q_-Sks5ro0TSgaJpZM4LxwD1>
.
--
Messages by Libby. Typos by iPhone.
|
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... |
Done. Waiting to close the issue until the underlying problem is solved. |
the issue has been fixed works fine on local,,need to test on the production,,please take git update and restart server |
command to update in db db.config.update({"collectors.name":"wnipd"},{$set:{"collectors.0.active":1}},{upsert:true}) |
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 ***@***.***> 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
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AALIzpI04e4GM-cvcvekU0aCGuNjMijiks5rpgtGgaJpZM4LxwD1>
.
|
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 |
needs discussion. |
Let's just delete the column - users can find out what's active by clicking on the collector to view its details. |
the UI has been changed..but it is not very pleasing,I suggest you have a look at it once,before closing the issue |
It looks ok. I can worry about the third column later. |
Most of these projects has at least one active collector, and it shows as active on the project's individual page.
The text was updated successfully, but these errors were encountered: