Twitter changes of May 12 and new changeset breaks my code

May 12, 2011 at 11:29 PM
Edited May 12, 2011 at 11:30 PM

I've been using LinqToTwitter successfully, with PinAuthorizer and the streamming api, both sitestream and userstream.

I loaded the new version, with the corrected paths, but I have some problems:

- When I use "Track", I get a "403 Error - Request entity too large", that seems to be related with the Get in the headers

var streaming = (from strm in ctx.UserStream
                                 where strm.Type == UserStreamType.Site
                                 && strm.Track == "xxx,yyy"
                                 && strm.With == "User"
                                 select strm)

- When I use "Follow", I get a "400 Error - Bad request"

 var streaming = (from strm in ctz.UserStream
                                 where strm.Type == UserStreamType.Site
                                 && strm.Follow == "111,222"                                 
			      && strm.With == "User"
                                 select strm)

 

Any idea about what had break the code?

 We are using this in production, so it's very urgent to repair the program.  Thanks a lot for your help.

Marcos

 

 

Coordinator
May 12, 2011 at 11:33 PM

Hi Marcos,

Do you have a stack trace for each error?

Joe

May 12, 2011 at 11:40 PM

Hi Joe,

Thanks a lot for your help.

The first error is

{"The remote server returned an error: (413) Request Entity Too Large."}

with the following stack trace

"   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)\r\n   at LinqToTwitter.TwitterExecute.<>c__DisplayClasse.<ExecuteTwitterStream>b__c(IAsyncResult ar) in C:\\$Twittaly\\LinqToTwitter\\linqtotwitter-88593\\LinqToTwitterAg\\LinqToTwitter\\TwitterExecute.cs:line 445"

Marcos

May 12, 2011 at 11:46 PM

Joe,

Just for info I commented the following lines in UserStreamRequestProcessor

       private string BuildSiteUrl(Dictionary<stringstring> parameters)
        {
            //if (!parameters.ContainsKey("Follow"))
            //{
            //    throw new ArgumentNullException("Follow", "Follow is required.");
            //}

as in my previous version, because I could use site or user streams just with "Track", works ok without "Follow"

Marcos


Coordinator
May 13, 2011 at 12:26 AM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Coordinator
May 13, 2011 at 12:27 AM

Thanks, I moved it to a work item and will check it out.

Joe

May 13, 2011 at 12:32 AM

Thanks a lot Joe, please do your best.

The program was in production and I'm in a very unconfortable position.

Marcos

Coordinator
May 13, 2011 at 4:26 AM

Marcos,

I wasn't able to reproduce this on my system.  What version are you looking at?  I'm currently working with the latest changeset:

http://linqtotwitter.codeplex.com/SourceControl/changeset/changes/88593

This hasn't been formally released, but it's downloadable and you can build and use it.  Is this the same version you're using?

Joe

May 13, 2011 at 8:41 AM

Yes, I donwloaded and use the latest changeset.

Can I send you a very small code?  But it must be privately, due to the use of real authorization codes.

Please, contact me at mtabaj@bap-systems.com

Thanks a lot

Marcos

Jun 8, 2011 at 2:34 PM

Hello

I have the same problem.

Any solutions?

Thanks!

Coordinator
Jun 8, 2011 at 2:47 PM

There are a couple different issues with the latest changeset that are currently in-process.  No ETA, but they are being worked on.

Joe

Jun 16, 2011 at 6:37 AM

Hi, same issue for me too. It would be cool if you'll fix asap.

txs in advance.

-Vince

Coordinator
Jun 16, 2011 at 2:33 PM

Thanks for the feedback - in progress.

Joe

Jun 28, 2011 at 10:05 AM

Hi Joe,

Sorry to say that with changeset 90545 I still have the same error using Sitestream:

 (413) Request Entity Too Large

By the way, you can change SiteStreamUrl from

 "http://betastream.twitter.com/2b/"

to
 "http://sitestream.twitter.com/2b/"
it's the correct now.
Hope you can fix the problem soon.
Regards,
Marcos
Coordinator
Jun 28, 2011 at 9:13 PM

Marco,

Thanks for letting me know.  Funny, my samples worked with the old URL and I assumed it was fixed.  I do remember some scenarios you gave me that were causing problems and will look at those too.

Joe

Coordinator
Jun 28, 2011 at 9:15 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Coordinator
Jun 28, 2011 at 9:15 PM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.