(11-20-2018, 01:27 PM)Backo Wrote: It's been another week and still no official statement from either admins or devs that take care of the tracker. This is quite demotivating and I would be very disappointed if it ends up with a green message in 3 months that we are denied officialdom because there isn't a working tracker to judge our activity. A simple "we are working on it" would be quite assuring, I don't demand that you fix this here and now, I just want an official statement to know if this is going to get fixed or not. While the journey is more important than the destination I'd be quite disappointed to lose another 500 mil in vain.
(11-20-2018, 01:27 PM)Backo Wrote: It's been another week and still no official statement from either admins or devs that take care of the tracker. This is quite demotivating and I would be very disappointed if it ends up with a green message in 3 months that we are denied officialdom because there isn't a working tracker to judge our activity. A simple "we are working on it" would be quite assuring, I don't demand that you fix this here and now, I just want an official statement to know if this is going to get fixed or not. While the journey is more important than the destination I'd be quite disappointed to lose another 500 mil in vain.
I gave you an answer Last Wednesday at 2:43 PM
I just want it officially stated here. So the future of the faction can be known publicly. That's all.
(11-20-2018, 01:27 PM)Backo Wrote: It's been another week and still no official statement from either admins or devs that take care of the tracker. This is quite demotivating and I would be very disappointed if it ends up with a green message in 3 months that we are denied officialdom because there isn't a working tracker to judge our activity. A simple "we are working on it" would be quite assuring, I don't demand that you fix this here and now, I just want an official statement to know if this is going to get fixed or not. While the journey is more important than the destination I'd be quite disappointed to lose another 500 mil in vain.
I gave you an answer Last Wednesday at 2:43 PM
I just want it officially stated here. So the future of the faction can be known publicly. That's all.
official then: change your tag to drop the backslash if you don't to wait for someone to secure time to figure this out. otherwise wait?
So I've made this activity tracker that tracks L\- from the individual player activity pages: http://flactivity.cfapps.io/
It takes each page from the player activity list and then filters only for L\- characters that show up there. The downside is that it only tracks this and last month, because player_activity only provides such data.
I'll get to add a total time once I get more time/motivation to tinker with it. EDIT: That's in now.
I'd still very much like to get the actual tracker fixed, but I can't do anything without at least some assistance from the people responsible for it. I know the activity tracker dev(s?) want to rewrite the whole thing but without any estimation on when that'll happen, I'd much rather have that 1 line that fixes the issue rather than wait indefinitely.
Also actual feedback regarding the faction is also welcome, don't feel threatened by my constant bickering with the devs regarding the backslash faction activity tracker issue, I'm a very nice person, really.
Posts: 3,798
Threads: 144
Joined: Aug 2009
Staff roles: Server Manager Coding Dev Moderator
I've spent some hours looking into the faction activity tracker issue and wanted to give an update, so far it seems the issue is not with Discovery code but with a backslash escaping issue upstream (probably in Microsoft Entity Framework Core or the Pomelo.EntityFrameworkCore.MySql connector we use for it). They generate some unnecessarily bad SQL code and, just to make things more difficult to debug, make it difficult to extract the query they generate. Unfortunately another upstream problem prevents us from simply working around this issue in our code by doing the escaping ourselves. I'm going to see if I track down the root of the issue and get it fixed. Even if I manage to do that, I'm not sure how easy it will be to integrate the fixed version into Discovery's codebase.
![[Image: kallistesilver.gif]](https://sig.grumpybumpers.com/host/kallistesilver.gif)
![[Image: dI8iG0a.png]](https://i.imgur.com/dI8iG0a.png)