WowAce

What steps will reproduce the problem?
1. Updated to 4.2, started playing my L60 Blood DK
2. Got attacked while playing archeologist
3. Started fighting an Owlbeast at Owl WingThicket in Winterspring
4. Quartz go boom!

What version of the product are you using?
Quartz, v3.0.6

Do you have an error log of what happened?

Date: 2011-06-28 19:29:47
ID: 1
Error occured in: Global
Count: 2
Message: ..\AddOns\Quartz\modules\Swing.lua line 183:
   bad argument #1 to 'bit_band' (number expected, got string)
Debug:
   (tail call): ?
   [C]: ?
   Quartz\modules\Swing.lua:183: ?()
   ...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147:
      ...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
   [string "safecall Dispatcher[13]"]:4:
      [string "safecall Dispatcher[13]"]:4
   [C]: ?
   [string "safecall Dispatcher[13]"]:13: ?()
   ...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()
   ...ace\AddOns\TomTom\libs\AceEvent-3.0\AceEvent-3.0.lua:120:
      ...ace\AddOns\TomTom\libs\AceEvent-3.0\AceEvent-3.0.lua:119
AddOns:
  Swatter, v5.11.5146 (DangerousDingo)
  WowheadLooter, v40017
  Archy, v1.8.3
  Atlas, v1.20.0
  AtlasBattlegrounds, v1.20.0
  AtlasDungeonLocs, v1.20.0
  AtlasOutdoorRaids, v1.20.0
  AtlasTransportation, v1.20.0
  AucAdvanced, v5.11.5146 (DangerousDingo)
  AucFilterBasic, v5.11.5146 (DangerousDingo)
  AucFilterOutlier, v5.11.5146.2531
  AucMatchUndercut, v5.11.5146.2531
  AucScanData, v5.11.5146 (DangerousDingo)
  AucStatHistogram, v5.11.5146 (DangerousDingo)
  AucStatiLevel, v5.11.5146 (DangerousDingo)
  AucStatPurchased, v5.11.5146 (DangerousDingo)
  AucStatSales, v5.11.5146.2842
  AucStatSimple, v5.11.5146 (DangerousDingo)
  AucStatStdDev, v5.11.5146 (DangerousDingo)
  AucStatWOWEcon, v5.11.5146.2530
  AucUtilAHWindowControl, v5.11.5146.3311
  AucUtilAppraiser, v5.11.5146.2530
  AucUtilAskPrice, v5.11.5146.3175
  AucUtilAutoMagic, v5.11.5146.3142
  AucUtilCompactUI, v5.11.5146.2530
  AucUtilEasyBuyout, v5.11.5146.3583
  AucUtilFixAH, v5.11.5146 (DangerousDingo)
  AucUtilGlypher, v5.11.5146.5061
  AucUtilGlypherPost, v5.11.5146.5069
  AucUtilItemSuggest, v5.11.5146.3108
  AucUtilPriceLevel, v5.11.5146.2545
  AucUtilScanButton, v5.11.5146.2530
  AucUtilScanFinish, v5.11.5146.2530
  AucUtilScanProgress, v5.11.5146.2530
  AucUtilScanStart, v5.11.5146.4784
  AucUtilSearchUI, v5.11.5146.3655
  AucUtilSimpleAuction, v5.11.5146.4546
  AucUtilVendMarkup, v5.11.5146.2530
  Auctionator, v2.9.7
  Babylonian, v5.1.DEV.130
  Bartender4, v4.4.18
  BeanCounter, v5.11.5146 (DangerousDingo)
  Configator, v5.1.DEV.282
  DebugLib, v5.1.DEV.275
  Grail, v
  GuildLaunchProfiler, v01.03.00
  Identity, v40000
  Informant, v5.11.5146 (DangerousDingo)
  LuaBrowser, v10.11.10
  Omen, v3.1.2
  Overachiever, v0.63
  Quartz, v3.0.6
  Rubbish, vv40100-0.9
  Skada, vr323
  SkadaAbsorbs, v1.0
  SkadaCC, v1.0
  SkadaDamage, v1.0
  SkadaDamageTaken, v1.0
  SkadaDeaths, v1.0
  SkadaDebuffs, v1.0
  SkadaDispels, v1.0
  SkadaEnemies, v1.0
  SkadaFailbot, v1.0
  SkadaHealing, v1.0
  SkadaPower, v1.0
  SkadaThreat, v1.0
  SlideBar, v5.11.5146 (DangerousDingo)
  Stubby, v5.11.5146 (DangerousDingo)
  TextureBrowser, v10.11.10
  TomTom, vv40100-1.4.0
  WowLua, vv40000-1.0.1
  WoWPro, v2.1.17
  WoWProDailies, v2.1.17
  WoWProLeveling, v2.1.17
  BlizRuntimeLib_enUS v4.2.0.40200 <us>
  (ck=8ed)

Please provide any additional information below.

My reports looks related to http://www.wowace.com/addons/quartz/tickets/154-enemy-casts-module-error/, except that I never got this error in the past 2 months playing this toon and now it seems to happen every other time I kill something.

The switch to 4.2 seems suspicious.

Perhaps this might help:
http://eu.battle.net/wow/en/forum/topic/2057506348 aka 4.2 COMBAT_LOG_EVENT_UNFILTERED changed.

It seems there are two new arguments stuck in there.

Changing line 173 to:

function Swing:COMBAT_LOG_EVENT_UNFILTERED(event, timestamp, combatevent, hideCaster, srcGUID, srcName, srcFlags, sourceRaidFlags, dstName, dstGUID, dstFlags, destRaidFlags, spellID, spellName)

seems to fix the problem. Combat log showed the bug popped when I missed a swing and I killed a dozen Owlbeasts in a row and missed more than once with this fix.