Jasper n00b here...
We've got some reports that run weekly. They both save a copy of the report to a specified folder in the repository, as well as email a copy of the report to specified users.
We're finding that at times, there are discrepancies between these two reports. Obviously, there should not be. Same report. Same input params. Same scheduled job.
Not something that I can easily reproduce, as it's intermittent (as with all fun troubleshooting tasks). And lacking familiarity with Jasper in general, not even sure where to begin looking.
I apologize in advance for the vague/general question, but if anybody has any insights into where I might even begin to start looking, it'd be greatly appreciated.
EDIT TO ADD: We've had a couple of occasions now where the emailed version of the report is blank, but the saved version in the repository is fine. Thoughts??
Related
A year ago I have started an issue on github repository of a popular open source project. There wasn't enough data to fix it because bug was caused only by one closed source program. Recently I have stumbled upon other program that causes the bug and this one is open source. This should make it possible to fix the issue.
I have added new comment in issue providing new information, but it got no response for 10 days.
https://github.com/linuxmint/Cinnamon/issues/6253
I wonder if maintainers see comments on old issues in their notifications?
If they do did they discard it by accident or perhaps because in their experience most comments on old issues are useless?
Should I just edit last comment there slightly?
Will they see that?
Or what to do?
The good news is the project is not dead. Issues have been closed recently and PRs have been merged. Someone is watching the queue. The bad news is the project has over 800 open issues at this time which means they're probably swamped.
Open Source projects are typically run by volunteers, and that looks like a low priority issue. If you want it solved, do everything you can do reduce the work necessary to fix the problem. You've already given clear instructions on how to reproduce the problem, that's a very good start.
The single best thing you can do is submit a PR with a complete patch including tests. Be sure to conform to their developer guidelines. That project does not leave PRs open long. If you can't do a complete patch, take a stab at it and submit the PR asking for help. If you don't know where to start patching, make a comment on the issue asking for help with where to start.
Basically, do the work. If you can't do the work, show a willingness to do the work.
There seems to be some consternation about two file types that, in my case, TFS checks in when a new solution or project are created: .vssscc and .vspscc files.
I found a page that describes that these files are for, and yet another that recommends checking them in. I'm perfectly fine with this, but I have heard some grumblings in the internet that these files can cause issues with collaboration between projects, such as merge conflicts and project load errors.
I do recall having some issues in my own organization where the .vspscc file caused some issues, where a developer had caused some edits to it and didn't check it in with the rest of his changes. We were able to repair easily, however.
My question is: what issues should I be aware of, and in the case that issues exist, what precautions can I recommend to my organization to avoid any trouble?
The only issue I've ever come across is a minor annoyance- the .vssscc is included as a change with many checkins even though the .vssscc contents have not changed. I'm guessing the last modified date is being updated.
Apparently Microsoft was looking into fixing this in 2010.
It seems unlikely that these files contain anything of importance to the source code. As far as I can tell it's just cached data about the current code.
I opened an issue at https://github.com/dotnet/project-system/issues/1801, so go there and let them know how this affects you.
I have created a total of 9 sample pages for my project. I tagged three of them as templates to speed the design process. I successfully exported all nine files but upon returning to my account discovered that all nine files had some how revered to the same source code.
In other words, instead of 9 distinctly different pages I have 9 copies of the same page. How could this happen and how can I fix this? I need to continue my work but with no way to correct this problem or upload my correct files form my previous export I feel as if I need to either start over or do all of my editing in an HTML editor manually going forward.
Any guidance would be much appreciated!
Do backup next time. I don't think you would be able to retrieve your "OLD files" if you didn't back them up and without UPLOADING your previous files.
Please get in touch with support if you lost any data and we'll work with you to get it restored right away. Bugs like these are always high priority and we want to make sure your data is never lost.
In the new version of Divshot saving is now manual and with version history you now have the option to revert back to a previous version of a file at any time. All data is backed up on Amazon S3 with versioning.
After upgrading let me know if you continue to experience issues with cloning pages or using templates. We'll be happy to help!
I've been working with a lot of my files on the go recently, and in the process often times accumulated several copies of files in different stages of completion/revision. I'm working on any number of projects at a given time, so it's not always easy to remember or figure out quickly which version I should continue working on.
What type of options would you recommend that allow me to track changes locally and if possible with files I work on while at a remote location? I've never worked with file versioning or tracking systems, so not sure what direction I should be looking in. I work mostly with HTML, CSS, and PHP.
Any help is awesomely appreciated! Thanks.
PS. Don't know if I should have this in a separate question but what options are available for the same type of thing, change tracking/logging for files on server? Preferably something that not only vaguely notes a file has been changed, but that tracks specific changes that have occurred in files.
It's seems to me that github is prefect choice for your requirement. You can create repository for maintain the history, it's easy to use and it is free
https://github.com/
Eric suggests that you read your team's diffs every morning. Can I get TFS to automate this in some way? Ideally I'd like an email with all of the differences in, but I'd settle for a link to each of the commits.
As someone who works for Eric and who has the behaviour of checking the diffs each morning let me explain what I do. I'd like to think that I was one of the people he was thinking about when he wrote the post, but I know for a fact that he didn't know I did the diff checking each morning :-)
In Eclipse I use the Team, Synchronize... functionality to compare my local workspace with the latest on the server. As I do a get latest frequently, this tells me what has happened since I last did this (i.e. what changed while I wasn't looking).
In Visual Studio, I can do a similar thing by right clicking on the root folder of the area that interests me and selecting Compare... and then doing a compare of the Workspace version with the latest version.
Alternatively, you can just do a "History..." on the folder that is of interest and a brief scan down the history view will show you what has been happening and you can go look at what is interesting. It also encourages you to leave good check-in comments, and to encourage your developers to do the same :-)
I used to have email alerts configured for each check-in (Team, Project Alerts...), but I just ended up ignoring them most of the time. I even have a robotic rabbit configured to talk to me when someone does a check-in or runs a build - but this is only useful during the day, not checking what has happened the previous day while I was asleep (I live in a different time-zone to the rest of my colleagues so they do a lot of work while I sleep and vice-versa, making the practise of diff-checking even more useful)
In theory it would be possible to write a program that did generate you a diff each day between the latest version and your workspace version, however I've never bothered myself. This is partly because as I find the most value of the practise comes in exploring the changes that were made each day rather than just reading about them. I also admit that I wasn't aware that anyone else in the world was doing this daily diff routine - I figured I was alone in my code voyerisum, but obviously not!
UPDATE Feb 12, 2009: The following blog post just came to my attention.
http://blogs.msdn.com/abhinaba/archive/2008/07/07/auto-generating-code-review-email-for-tfs.aspx
It talks about (and provides source for) a tool called CRMail that will generate an email from a shelveset that will contain links back to Team System Web Access to show the diffs for each change in the changeset. It would be possible to modify this source to get it to show you diffs between changesets if you wanted to. Then you would just need to hook it up to run either as a nightly scheduled task or on every check-in by subscribing to the check-in event from TFS.
Have you explored setting up a report on the project portal that would show diffs based on date? I haven't done this (and I'm at home now so I can't investigate it), but I know that there is a lot of information you can get out of the portal. Whether you can get code diffs, I don't know.
The other alternative would be automating something with tfsadmin or the power tools. Again, not at work so I can't look at it, though the power tools seem like they may make it possible to do what you want from the docs.
A quick solution would be to configure project alerts to send you one email per changeset.
Filter these into a separate folder in your email client, and review them at your leisure.