@dustinb3403 said in What Are You Doing Right Now:
@quixoticjeremy said in What Are You Doing Right Now:
Waiting for my IT to wake up so that I can get logs
Why don't you have access to the logs (without the need of IT) ?
Just the way that we have it set up currently. Will change eventually but we haven't gotten around to it.
Waiting for my IT to wake up so that I can get logs
@stacksofplates Likely no, our checkins are done via our own scheduling. Would not think that altering that would effect us.
@danp Haha I'm sure there will be new features today but nope not yet. Data collection took priority this morning. I did get some things cleaned up but I haven't created a release yet.
@danp They were mainly backend changes in conjunction with the architecture changes to make sure we don't run into more checkin issues.
@dustinb3403 said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
Waiting for the coffee to be ready.
So late in the day to have coffee.
I have coffee up until I leave work #1....
@gjacobse said in Sodium: Device Check in:
@scottalanmiller
And it's been nearly 45 minutes since I posted this...
Looks like you're good now.
@gjacobse said in Sodium: Device Check in:
Just about ever device we have connected has not checked in since 9:20
Waiting on a response from IT so that I can get logs and look into what is going on.
@gjacobse said in Sodium: Custom Ticket Views:
@danp said in Sodium: Custom Ticket Views:
@quixoticjeremy said in Sodium: Custom Ticket Views:
that being said it's being worked on from the standpoint of logins should timeout ....overnight.... so you should have to login in the morning anyways.
Has this change been pushed out? FWIW, I didn't get auto-logged out overnight.
I dont' get auto-logged out either.
No one does yet.
@danp said in Sodium: Custom Ticket Views:
@quixoticjeremy said in Sodium: Custom Ticket Views:
that being said it's being worked on from the standpoint of logins should timeout ....overnight.... so you should have to login in the morning anyways.
Has this change been pushed out? FWIW, I didn't get auto-logged out overnight.
No it has not been pushed out yet, it's currently in development.
Just checked in Chrome and I get this --
Exception in template helper: TypeError: Cannot read property 'company' of undefined at Object.unitGroups (https://sodium.waxquixotic.com/app.js?hash=9a69b28b89efe0a1f976612c19bd1154b5baa7e4:1656:35) at https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:185:18 at https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:112:41 at https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:191:182 at Function.Template._withTemplateInstanceFunc (https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:714:12) at https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:191:74 at Object.Spacebars.call (https://sodium.waxquixotic.com/packages/spacebars.js?hash=ebf9381e7fc625d41acb0df14995b7614360858a:14:14) at https://sodium.waxquixotic.com/app.js?hash=9a69b28b89efe0a1f976612c19bd1154b5baa7e4:1:31142 at Blaze.View.<anonymous> (https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:172:181) at https://sodium.waxquixotic.com/packages/blaze.js?hash=f33d3dfed63a491d24e3aa07ad66c24b5fe8c761:120:252
That's just initial load. Won't effect anything. the client side threw that error before it read from the server side subscription. I just don't have a catch wrapped around it yet. Not a big deal.
@gjacobse FF 54
At the moment there are quite a few screens that are going to show errors/messages due to the fact that a few days ago I implemented an extra level of security that is throwing these messages for the tiniest thing. It is being fine tuned.
@gjacobse said in Sodium: Custom Ticket Views:
@quixoticjeremy said in Sodium: Custom Ticket Views:
@gjacobse said in Sodium: Custom Ticket Views:
@quixoticjeremy said in Sodium: Custom Ticket Views:
@gjacobse said in Sodium: Custom Ticket Views:
Created a Ticket View last night for Open/Closed and it was missing this morning.
Created it again, and did not save.
Can you log out and log back in for me please.
Done - and you're right. that worked.
Now, I have extra filters,.. did we decide we can delete those?
Believe that this was answered in a different thread that we added that to the list of work.
Coolness - I can wait. It's evolving.. so things are coming along... and rather nicely at that.
Haha thanks for being patient. Doing my best to get to everything I can as quickly as I can :).
@gjacobse said in Sodium: Custom Ticket Views:
@quixoticjeremy said in Sodium: Custom Ticket Views:
@gjacobse said in Sodium: Custom Ticket Views:
Created a Ticket View last night for Open/Closed and it was missing this morning.
Created it again, and did not save.
Can you log out and log back in for me please.
Done - and you're right. that worked.
Now, I have extra filters,.. did we decide we can delete those?
Believe that this was answered in a different thread that we added that to the list of work.
@danp said in Sodium: Custom Ticket Views:
@gjacobse I've seen similar behavior. This morning I could only see the default "No Open Tickets" one. Had to log out and back in to see my custom one.
This is a known issue that I'm currently working on.
edit: that being said it's being worked on from the standpoint of logins should timeout ....overnight.... so you should have to login in the morning anyways.
@gjacobse said in Sodium: Custom Ticket Views:
Created a Ticket View last night for Open/Closed and it was missing this morning.
Created it again, and did not save.
Can you log out and log back in for me please.
@gjacobse they shouldn't have been in the list after having them be applied, obviously there is a bug. I'm going to have to look into this first thing tomorrow. As for updates that need a restart obviously at the time I did not want to auto restart any servers or anything like that. I will implement an option for us to restart the server for you if you confirm that you want that but at the point that these updates were at I was not implementing any restart functionality yet simply because this was early on work. (avoiding doing anything that isn't prompted by the user); You shouldn't see those in the list though after them having completed updating so I have work to look into. Until said point I may briefly take updates offline. Potentially.
@danp said in Sodium: Closed ticket in error:
@quixoticjeremy Great! FWIW, it was working correctly for me in Chrome.
Great! And good catch btw 
Feeling like crud, fever yesterday and today
