Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just pulled from svn and... nice! Top plays support = fabulous.
I'm able to see today's schedule, it's yesterday's (4/22) that I have problems with. It says "There was a parser problem with the listings page." Previous days work fine, though.
Thanks for all the great work on this!!
Ah, that's what I get for waking up early. ;-) It was the "if before 9am, show yesterday's listings". So that makes more sense. Perhaps whoever added the top plays last night forgot a comma somewhere.
Well, that's good news that you all can get today's games. Maybe when they figure out their error, you can view yesterday's top plays.
Just wanted to let you know that I figured out the cause of yesterday's hiccup (their unwonted use of a double quote in a play description) and I'll have a fix up quite soon.
Hmmm. Just pulled the latest svn. Getting a "there was a parser error with the listings page" followed by "No listings available for today". Tried going back a day and jumping to another day. No difference. Direct link to mlb listings as given earlier on the thread and I get something back. Putting it into debug mode didnt make any difference.
Thoughts?
*edit* This is on a laptop. I'll try it on my usual PC later.
Hmmm. Just pulled the latest svn. Getting a "there was a parser error with the listings page" followed by "No listings available for today". Tried going back a day and jumping to another day. No difference. Direct link to mlb listings as given earlier on the thread and I get something back. Putting it into debug mode didnt make any difference.
Thoughts?
Don't know what to tell you. All days work here -- strange. Did you make some local changes (the hours bugfix, maybe?) so the update isn't overwriting?
Try doing a fresh pull into another directory:
Code:
svn co https://mlbviewer.svn.sourceforge.net/svnroot/mlbviewer/trunk mlbviewer-test
Hmmm. Just pulled the latest svn. Getting a "there was a parser error with the listings page" followed by "No listings available for today". Tried going back a day and jumping to another day. No difference. Direct link to mlb listings as given earlier on the thread and I get something back. Putting it into debug mode didnt make any difference.
Thoughts?
*edit* This is on a laptop. I'll try it on my usual PC later.
I'm guessing just based on the time difference between this post and jkr's that you just missed his check-in. Try checking it out again.
I'll see if I can re-raise the Exception when debug is enabled just in case we're masking something else. Debug is intended to let most errors drop through like a lead ball so we can find the "unknown" errors.
I'm guessing just based on the time difference between this post and jkr's that you just missed his check-in. Try checking it out again.
I'll see if I can re-raise the Exception when debug is enabled just in case we're masking something else. Debug is intended to let most errors drop through like a lead ball so we can find the "unknown" errors.
Well, this particular error definitely came from the double quote. I ran the steps one at a time, and it gave me the particular place in the JSP that it barfed on (i.e., the character where the parsing got confused). There might be other errors masked there, but the one that was biting people yesterday came from that issue.
Well, this particular error definitely came from the double quote. I ran the steps one at a time, and it gave me the particular place in the JSP that it barfed on (i.e., the character where the parsing got confused). There might be other errors masked there, but the one that was biting people yesterday came from that issue.
No doubt.
If we get future Json errors, the commit I'm making will spit out the character information if debugging is enabled.
Code:
matthew@tango:~/mlbtv/svn/mlbviewer$ ./mlbviewer.py
Traceback (most recent call last):
File "./mlbviewer.py", line 619, in ?
curses.wrapper(mainloop, mycfg.data)
File "curses/wrapper.py", line 44, in wrapper
File "./mlbviewer.py", line 448, in mainloop
raise Exception,detail
MLBviewer.mlbtv.MLBJsonError: Expecting , delimiter: line 1 column 66499 (char 66499)
This way if there are any other json error conditions we're missing, e.g. the "There was an error in parsing" message comes back, we can track it down easily by enabling debug.
EDIT: Verified with Debug enabled that parser error isn't raised so your fix is golden. Thanks a million!
I don't know if I am pulling the newest svn off correctly...I am not getting anything when I press J for jumping to a day....I am still getting traceback errors. How do I know whether I am picking up the latest version?
____________________________________________________________________
Newbie error....Got it situated!
I don't know if I am pulling the newest svn off correctly...I am not getting anything when I press J for jumping to a day....I am still getting traceback errors. How do I know whether I am picking up the latest version?
You should see something like this:
Code:
matthew@tango:~$ svn co https://mlbviewer.svn.sourceforge.net/svnroot/mlbviewer/trunk mlbviewer-test
A mlbviewer-test/test
A mlbviewer-test/test/mlbgameid.py
A mlbviewer-test/LICENSE.txt
A mlbviewer-test/mlbviewer.py
A mlbviewer-test/INSTALL
A mlbviewer-test/setup.py
A mlbviewer-test/MLBviewer
A mlbviewer-test/MLBviewer/LIRC.py
A mlbviewer-test/MLBviewer/__init__.py
A mlbviewer-test/MLBviewer/mlbtv.py
A mlbviewer-test/MLBviewer/config.py
A mlbviewer-test/README
Checked out revision 60.
matthew@tango:~$
jkr
Did you create a new branch (or tag)? What's with the "mlbviewer-test"?
How do you know if you have the latest?
Code:
matthew@tango:~$ cd mlbviewer-test/
matthew@tango:~/mlbviewer-test$ ls
INSTALL LICENSE.txt MLBviewer mlbviewer.py README setup.py test
matthew@tango:~/mlbviewer-test$ svn up
At revision 60.
matthew@tango:~/mlbviewer-test$
From within the directory,
svn up updates your copy if there are newer revisions in the repository
svn diff to see the changes between what's in the repository and any local changes you might have made
svn log to see the commit notes
And finally, you can always browse the repository online at:
Each file/directory has its own Rev. so you look for the highest Rev and the Age to see how recent the revision is. Browsing the repository online also lets you see the commit log and visual diff's which are easier to read than svn diff.
If you installed the package globally, (e.g. you ran setup.py install), you'll probably need to re-install the package you just checked out (or updated.)
I don't know if I am pulling the newest svn off correctly...I am not getting anything when I press J for jumping to a day....I am still getting traceback errors. How do I know whether I am picking up the latest version?
____________________________________________________________________
Newbie error....Got it situated!
Glad to hear it.
I don't mind typing out the howto answers like I just did. It helps me later when someone asks the same question.
You have to have a manual first before you can tell someone to read the fine manual.
Daftcat-
Thanks! I didn't realize it was being put into a new folder, I have been looking at .mlb from the original origin. The svn put it in a mlbviewer-test folder within my home directory...I am sure you already know this, but I didn't and that was my problem... Everything works great, I love the options!
Did you create a new branch (or tag)? What's with the "mlbviewer-test"?
Nope. You can call the target directory anything you want -- I just wanted to indicate putting it somewhere other than the directory he was probably running out of right now. Sometimes if somethig got screwy with my edit, I just pull down to a different folder with an arbitrary name (mlbviewer-i-fd-up) and run it out of there to compare.
Great writeup. One slight addition:
Quote:
Originally Posted by daftcat
svn diff to see the changes between what you checked out and what's in the repository.
This actually shows the difference between what you last checked out (what was on the server) and the local changes you made to it. It doesn't show what changes have appeared on the server.
Advanced usage note: 'svn log' shows you all the changes. But you can actually pull down from any point -- svn keeps a complete history. So if any of you are real bug-hunting junkies, and you think a recent change might have screwed something up, you can just run 'svn -r #' up, where '#' is a change in the log, to roll back to here. Only for the curious, but the latest version will still always be there waiting for you if you screw up
And just to add on to what daftcat said about system installation. If that's how you run it, you can just run setup.py again. Each change will overwrite the old files.
Copied from the MLB Mosaic Forum (and in turn, copied from an email correspondence with one of the members of that forum):
Quote:
Thank you very much for your note to Mark Newman regarding your inability to get the Condensed Games. We apologize for the delay in providing you this content, but the product is not gone forever. Its launch this year was slightly delayed due to the several unforeseen factors around Opening Day. That being said, we fully expect the product to be available in May. In the interim, I would recommend you use our new video search page and watch the Rewind Recaps. We have them for every game, every day. Thanks for your patience and we look forward to providing you with the Condensed Games as soon as possible.
Best regards,
Matthew Gould
VP, Corporate Communications
MLB Advanced Media
When Condensed Games return, I'll be sure to add that to mlbviewer. For now, I support Rewind Recaps already.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
