search

LuckySherry / TwitterClient_0.2

COMP3111_Phase1_Team202
0 stars 0 forks source link

Crash: # Entity #27

Open monosite opened 11 years ago

monosite commented 11 years ago

How:

  1. Tweet the follow:

    GoGo&GO #GoGo*GO

What: Application Crashed

bingo92 commented 11 years ago

what a morning shock! > < Well , after some testings , I think the API went wrong somehow, which are related to the hash tag entity and user mention entity, I suggest you test these two tweets in your version to see whether it will go wrong as well. ÔÚ 2013-4-18 AM4:26£¬"monosite" notifications@github.comдµÀ£º

How:

  1. Tweet the follow:

    GoGo&GO #GoGo*GO

What: Application Crashed

¡ª Reply to this email directly or view it on GitHubhttps://github.com/LuckySherry/TwitterClient_0.2/issues/27 .

monosite commented 11 years ago

We face the same problem in another way that we cannot recognizing these correctly and display them correctly. I am also currently working on fixing these Entity Recognizing issues for our application.

bingo92 commented 11 years ago

Yes, you are right. Our version of twitterclient crashed just because of the wrong return value of API functions offered which is to locate the beginning and ending point of hash tag entity as well as user mention entity. So did some other group. Maybe we can ask TA for help ~

2013/4/18 monosite notifications@github.com

We face the same problem in another way that we cannot recognizing these correctly and display them correctly. I am also currently working on fixing these Entity Recognizing issues for our application.

— Reply to this email directly or view it on GitHubhttps://github.com/LuckySherry/TwitterClient_0.2/issues/27#issuecomment-16570469 .

monosite commented 11 years ago

I think I have solved this problem.

bingo92 commented 11 years ago

Wow~ how you did it? Just now, I have located where the bus appeared and it has something to do with RawJSON since some special characters like "&" and " * ". Now I am still struggling with how to get the rawjson in an easy way~

monosite commented 11 years ago

I just find where is wrong with the API and fix that problem.

monosite commented 11 years ago

And I don't think getting the rawJson is a good way as It will definitely slow down the whole application in a huge degree.

bingo92 commented 11 years ago

yeah, you are right. Also, I have to periodically clear the json map to release memory if I do it that way.... can you offer me some hints to fix the bug ? now I just feel quite struggled ~~ > <

monosite commented 11 years ago

Actually, I modified the source code of twitter4j-core-3.0.3 and generate a corrected new twitter4j-core-3.0.3 library. Hope it helps, or you might wait for twitter4j 3.04 which a I think maybe this bug will be fixed or maybe not.

bingo92 commented 11 years ago

Well, thanks a lot for suggestion, I will take a try~~ ÔÚ 2013-4-20 AM12:07£¬"monosite" notifications@github.comдµÀ£º

Actually, I modified the source code of twitter4j-core-3.0.3 and generate a corrected new twitter4j-core-3.0.3 library. Hope it helps, or you might wait for twitter4j 3.04 which a I think maybe this bug will be fixed or maybe not.

¡ª Reply to this email directly or view it on GitHubhttps://github.com/LuckySherry/TwitterClient_0.2/issues/27#issuecomment-16662177 .

waitingcheung commented 11 years ago

Confirmed.

Ken