Not signed in (Sign In)

Auctioneer::Technical: Lexical element too long? after a AC Scan Completes

Bottom of Page

1 to 9 of 9

  1.  
    • CommentAuthoralderion
    • CommentTimeApr 10th 2008
     
    Been Getting this error occasionally after a succesful scan.

    Everything still seems to work but not sure what is causing it?

    Date: 2008-04-10 19:43:07
    ID: 51
    Error occured in: Global
    Count: 1
    Message: WTF\Account\...\SavedVariables\Auc-ScanData.lua line 142:
    lexical element too long
    Debug:
    [C]: ?
    [C]: resume()
    Auc-Advanced\CoreScan.lua:804:
    Auc-Advanced\CoreScan.lua:803
    Auc-Advanced\CoreScan.lua:1121: StorePage()
    Auc-Advanced\CoreScan.lua:1161:
    Auc-Advanced\CoreScan.lua:1147
    [C]: ?
    [C]: pcall()
    Stubby\Stubby.lua:340:
    Stubby\Stubby.lua:324
    (tail call): ?
    Auctioneer\AucQueryManager.lua:552:
    Auctioneer\AucQueryManager.lua:537
    Auctioneer\AucQueryManager.lua:217: AucQueryManager_OnUpdate()
    [string "*:OnUpdate"]:2:
    [string "*:OnUpdate"]:1
    AddOns:
    ArcHUD2, v2.2
    ArkInventory, v2.27
    AtlasLoot, vAtlasLoot Enhanced v4.04.01
    AucAdvanced, v5.0.PRE.2995
    AucFilterBasic, v5.0.PRE.2995 (BillyGoat)
    AucScanData, v5.0.PRE.2995 (BillyGoat)
    AucStatClassic, v5.0.PRE.2995 (BillyGoat)
    AucStatPurchased, v5.0.PRE.2995 (BillyGoat)
    AucStatSimple, v5.0.PRE.2995 (BillyGoat)
    AucStatStdDev, v5.0.PRE.2995 (BillyGoat)
    AucUtilBigPicture, v<%version%> (<%codename%>)
    Auctioneer, v5.0.PRE.2995
    AutoTurnin, v3.0.6
    BagSync, vr28876
    Bartender3, v3.1.2 r68497
    BeanCounter, v5.0.PRE.2995 (BillyGoat)
    BtmScan, v5.0.PRE.2995
    Cartographer, vr68749
    CartographerData, v1.0
    CartographerTrainers, v1.0
    CartographerVendors, v1.0
    CartographerQuestObjectives, v0.9b
    CartographerQuests, v0.2
    CartographerRoutes, v1.0
    ClosetGnomeTooltip, v1.0
    ClosetGnome, v1.0.68289
    ElkBuffBars, v2.1
    Enchantrix, v5.0.PRE.2995
    EnchantrixBarker, v5.0.PRE.2995 (BillyGoat)
    EnhTooltip, v5.0.PRE.2995
    EquipCompare, v2.9.8b
    FeatureFrame
    FuBarAmmoFu, v2.0
    FuBarDurabilityFu, v2.0
    FuBarHitChanceFu
    FuBarPerformanceFu, v2.0
    FuBarPetInfoFu, v2.4.1 $Revision: 68548 $
    FuBarToFu, v2.0
    FuBar2
    FuBar, v52783
    Informant, v5.0.PRE.2995
    ItemPriceTooltip, v2
    ChatThrottleLib, v19
    nQuestLog, v1.0 r68363
    Omen, vOmen r68561 / Threat-2.0 r68794
    OmniCC, v2.0.8
    PitBull, v3.0r68199
    Postal, v2.1 r68567
    Prat, v2.0 68549
    simpleMinimap, v20100-6
    SpamSentry, v20080405
    Stubby, v52
    Swatter, v5.0.PRE.2995
    ChatBox, v1.3
    • CommentAuthorKinesia
    • CommentTimeApr 10th 2008
     
    Wow, I just got that an hour ago myself...
    I believe it's because our Auc-ScanData.lua files are corrupt. I had a look at mine and it had some really long lines in the wrong format...
    I'm going to reboot and run scandisk soon...
    • CommentAuthorzumi
    • CommentTimeMay 30th 2008
     
    My problem seems to be the same kind, so I'm posting it in this topic.

    I'm using the Advanced version of Auctioneer (details in the buglog).

    I get this regularly after some scan, and my Auc-ScanData.lua gets purged.
    (it says: "Warning, Overwriting AucScanData with AucAdvancedScanSimpleData", I guess because AucScanData comes back empty after this error.)

    I don't think that makes a difference from the point of the addon, but I'm using it on a private server.

    Any help would be most appreciated.

    I can send the lua file in question if it's needed.

    ---

    my Auc-ScanData.lua file from line 90 until EOF:

    ["image"] = "return {{\"|cffa335ee|Hitem:32229:0: [...it is the single longest line of the ~10 megabyte file...] 0,47878,7069,0,0,0,0,},}",
    ["time"] = 1212151635,
    ["LastFullScan"] = 0,
    },
    EOF

    ---

    Date: 2008-05-30 21:35:16
    ID: 3
    Error occured in: Global
    Count: 1
    Message: WTF\Account\ZUMI002\SavedVariables\Auc-ScanData.lua line 90:
    lexical element too long
    Debug:
    [C]: ?
    [C]: LoadAddOn()
    Auc-Advanced\CoreScan.lua:64: LoadAuctionImage()
    Auc-Advanced\CoreScan.lua:101: GetImage()
    ...Auc-Advanced\Modules\Auc-Util-Appraiser\AprFrame.lua:2541:
    ...Auc-Advanced\Modules\Auc-Util-Appraiser\AprFrame.lua:2525
    [C]: ?
    [C]: pcall()
    Stubby\Stubby.lua:340:
    Stubby\Stubby.lua:324
    (tail call): ?
    [string "*:OnClick"]:1:
    [string "*:OnClick"]:1
    AddOns:
    AucAdvanced, v5.0.PRE.3117
    AucFilterBasic, v5.0.PRE.3117 (BillyGoat)
    AucScanData, v5.0.PRE.3117 (BillyGoat)
    AucStatClassic, v5.0.PRE.3117 (BillyGoat)
    AucStatPurchased, v5.0.PRE.3117 (BillyGoat)
    AucStatSimple, v5.0.PRE.3117 (BillyGoat)
    AucStatStdDev, v5.0.PRE.3117 (BillyGoat)
    BeanCounter, v5.0.PRE.3117 (BillyGoat)
    BtmScan, v5.0.PRE.3117
    EnhTooltip, v5.0.PRE.3117
    Informant, v5.0.PRE.3117
    QuestHelper, v0.47.8-43d2a7e
    Stubby, v52
    Swatter, v5.0.PRE.3117
    •  
      CommentAuthordinesh
    • CommentTimeMay 30th 2008
     
    Sorry, we don't provide any support for private servers.

    Search the forums for the warning message you got, though, i think there is some discussion about what it means.
    • CommentAuthorzumi
    • CommentTimeMay 30th 2008
     
    There are two other people with very similar problem in this thread. While I can understand that it's hard to support gibberish private servers, I tought that the two other posts before mine indicates a real problem, which surfaces sometimes.

    I can imagine two possibility with my almost zero lua knowledge:
    1) there are some lenghty names/IDs in the image which lua itself can't handle. (and maybe private servers are using long varibles, and normal servers don't)
    2) there's a bug in your data parsing code which only comes up with some funny item names/IDs (or the data file writer function makes the error)

    Either way, I think it would benefit the program to know the source of the problem.

    I'm willing to help with debugging if there's help on the other side.
    •  
      CommentAuthordinesh
    • CommentTimeMay 31st 2008
     
    as kinesia mentioned, the lexical element too big error is likely caused by a corrupt data file. there's a chance it's caused by bad code somewhere, but it seems unlikely since your file EOFs in the middle of an object. more likely you either had a random piece of data corruption, or you forced the wow process closed in the middle of exiting wow.

    either way, i regret to tell you that we do not support private servers here. i get that you're saying that it's a similar problem to others, and i agree, but it is simply our policy not to provide any support for users running on private servers. there's just too much that these servers can do differently that can cause problems which we'll spend lots of time trying (to no avail) to track down.
    • CommentAuthorzumi
    • CommentTimeMay 31st 2008
     
    Thanks for your suggestions.

    Just for the record:
    I haven't pasted the last line before EOF by mistake, so there's the ending "}" that you pointed out missing. My bad.

    The data corruption part can be ruled out because this symptom appeared on two independent, otherwise working computer, multiple times, closing the client regularly, however with the same server. So it's something to do with the latter.

    I understand your problem with private servers, so I stop asking for help. I only write here more if I will be able to find some real problems with the code of the Auctioneer regarding this error.
    Thanks for your time.
    • CommentAuthorRockSlice
    • CommentTimeMay 31st 2008
     
    Posted By: zumiI understand your problem with private servers, so I stop asking for help. I only write here more if I will be able to find some real problems with the code of the Auctioneer regarding this error.

    Perhaps you misunderstand. We will only help if you get problems while running on Blizz's servers. If you are having issues caused by real problems in the code, you will either have to log onto a Blizz server and give us the error from within there, or wait until somebody running on a Blizz server reports the problem.

    This is not to be mean, but as Dinesh said, to make sure we are talking about the exact same API. It is also to support the company that has worked hard to provide us with a very solid, very capable API, not to mention such an in-depth gaming environment.
    • CommentAuthorzumi
    • CommentTimeMay 31st 2008
     
    I understand the problems with private servers, and I'm not complaining. :) I'm not using the Blizz servers any more, so that's not an option for me.

    As I was thinking about how can my file get corrupted, I think I found out the source of the problem. It is not rare on my server that it crashes and then it throws me back to the title screen. This way I guess the addon scripts are terminated, and if the scanning parts is running at this time, it can ruin the database of items. So, I keep a backup and write it back when it happens.

    Thanks for your time again, at least I figured out what's wrong, and it's not the addon that causes it.

1 to 9 of 9

  1.  
World of Warcraft™ and Blizzard Entertainment™ are trademarks or registered trademarks of Blizzard Entertainment, Inc. in the U.S. and/or other countries.