IRC log for #wowace on 20161118

00:01.02StanzillaZeldo: so does the packager not build on tags then?
00:03.14Ressysnickers
00:03.24Ressynice one Stanzilla
00:03.33Stanzilla:)
00:05.20nevcairielznf: for svn repos you can just click on the url you think it should be and check if it contains the things you want :p
00:05.29nevcairielspeaking of that, repos seems randomly ratehr slow Zeldo
00:05.35znfgood point
00:06.45znfthere Gnarfoz, fixed broker_lootspec
00:10.35Gnarfozwoah, totally forgot that Grand Tour is available already :D
00:10.48nevcairieli thought tomorrow
00:10.52nevcairielwell it is tomorrow i guess
00:11.30Gnarfozyep
00:12.02nevcairielprobably watch tomorrow though
00:12.03nevcairielits late
00:12.27ZeldoStanzilla: Ticket in to fix that on the packager, in the mean time if you make a small commit with the tag it will package
00:12.39ZeldoIt does build tags but it thought it was the same content so it skipped it
00:12.50StanzillaZeldo: it did not though
00:13.08nevcairielyou need to push the small commit together with the tag, is what Zeldo means
00:13.18Stanzillasigh
00:13.24ZeldoYes, if it builds an alpha currently it won’t build the release
00:13.33nevcairielsee, i was right
00:13.35nevcairielyou can scream now
00:13.40Stanzillafucking bullshit
00:13.46ZeldoOptionally you cna rename the current alpha and covert it to release
00:13.52Stanzillatime to test force push
00:13.55ZeldoIt’s being fixed, but if you want a file out now that is the option
00:14.10ZeldoOr I can fix the file for you if you give me the name you want
00:14.22Zeldo2.2.2.2?
00:14.54ZeldoStanzilla: ^
00:15.02Stanzillalet me test something first
00:15.05Zeldokk
00:16.40znfoh, so now you have to push both, not like in the past where you had to push the content then the tag?
00:16.47znfor am I being wrong about the past? :P
00:17.02nevcairielyou are wrong about the past
00:17.27nevcairieli often pushed both at the same time and it worked fine
00:17.33znfok, that never worked for me :-/
00:17.41znfI did something wrong, no idea what
00:18.01nevcairielit did get kinda screwy if you pushed only the tag and not the master branch
00:18.02ZeldoThe packager will be changed to be able to commit, then push a tag
00:18.12nevcairielbut if you pushed both it was fine
00:18.17ZeldoAs Stanzilla expected it to work
00:18.23ZeldoHowever that is not current implemented
00:18.31Stanzillaremote: Internal server error. (auth)
00:18.31Stanzillafatal: unable to access 'https://repos.wowace.com/wow/weakauras-2/': The requested URL returned error: 500
00:19.15ZeldoJesus
00:19.21Stanzillaworked now
00:19.26znfyou broke it
00:19.35StanzillaZeldo: https://www.wowace.com/projects/weakauras-2/files/2345989
00:19.35Stanzillathere
00:19.40Stanzillapushed  the tag with the commit
00:19.43Stanzillastill made an alpha zip
00:20.08nevcairieli hear a lot of curseing from curse hq :p
00:21.19*** join/#wowace jlam (~yaaic@454a3e82.cst.lightpath.net)
00:21.29ZeldoWhat did you do to 500 it?
00:21.36Zeldoand yes, I am cussing atm -.-
00:22.30Stanzillaif I had to guess it would be the force push
00:22.32Stanzillabut I dont know!
00:22.53nevcairielthe auth likely happened before the remote even figured out what it was receiving
00:27.24ZeldoI am going to fix this file Stanzilla, if you push another release try doing it without a force
00:27.26Zeldoand see if it works
00:30.52*** join/#wowace Xuerian__ (~Xuerian@199.91.179.30)
00:34.18Kesava" contains root level files or root directories with empty or missing toc.xml files"
00:34.23Kesavais this some new thing i need to make
00:35.14nevcairielit probably complains about Kui_Media which is not an active addon directory
00:37.36ZeldoNo Kesava
00:37.39ZeldoWhat is your addon name?
00:37.49KesavaKuiNameplates
00:38.16znfso how do I push both the master branch and the tag in a single push? TortoiseGit's UI is not intuitive in this regard
00:38.19nevcairielhe has a toplevel directory with art assets with no toc, since it would be weird to have one, that would likely crash such a check
00:38.32nevcairielgit push origin master --tags
00:38.37nevcairielno clue about tortoise
00:38.41ZeldoKesava: Missclicked, the packager was packing non .pkgmeta addons incorrectly
00:38.49Kesavaah
00:38.58znfoh, that's new http://i.imgur.com/sY75SmH.png
00:39.00ZeldoIt’s being worked on
00:40.07nevcairielsounds like your git build is rather fubar znf :p
00:40.45nevcairielblame Stanzilla for cmder problems
00:40.46nevcairielnodnod
00:41.07znfyes
00:41.10znfblames Stanzilla
00:42.08Kesavaoh. yeah, the root directory name has been changed so the folders aren't being moved out
00:42.09Kesavaetc
00:43.28Kesavayay it worked.
00:45.10*** join/#wowace stolenlegacy (~stolenleg@213-47-49-27.cable.dynamic.surfer.at)
00:45.10*** join/#wowace stolenlegacy (~stolenleg@unaffiliated/stolenlegacy)
00:46.24nevcairielhehe its still complaining in the review queue
00:46.25nevcairielNote: Archive is missing Kui_Media/Kui_Media.toc (name is case sensitive and must not be empty)
00:47.01Kesava:<
00:47.10nevcairielbut i can just tell it to shove off!
00:47.14TorhalThat just means we have to know about it.
00:47.24TorhalSomeone who isn't familiar with your project might reject it.
00:47.57nevcairielshould totally have internal review notes that come up when you review a file for a rpoject
00:48.46Kesavacould i perhaps just put an empty toc file there. so as to not bother the reviewers
00:49.04znfI pushed. Nothing happens to broker_microclock
00:49.52znfor, rather, to all of Timmeh's broker_* packages
00:51.41nevcairielsmells like they have alpha packaging off, t here is not a single alpha in the file list from ever
00:52.01znfI pushed the tag, too
00:53.39znfIt's also set to "package all commits"
00:53.50nevcairielstill doesnt have a single alpha from ever :D
00:54.02nevcairielmicroclock that is
00:54.37znfI pushed to broker_lootspec, broker_microclock
00:54.38znf:-|
00:55.31znfTorhal broke it :(
00:56.11quiescens/blame torhal
00:56.49TorhalI'm starting to wonder if using /ignore would be worth my time to type out.
00:56.50Torhal>.>
00:58.05quiescens):
01:00.28znfbut we love you
01:00.30znfyou and your cats
01:00.33znfwell, mostly your cats
01:02.08TorhalKesava, Ressy, znf - added you to the whitelist.
01:02.14Ressyty :)
01:02.30TorhalNow, less QQ, more pew-pew.
01:02.33RessyI guess now isn't the time to make a joke about doing bad stuff with ARL/Collectinator? :p
01:02.47TorhalGo ahead. IDGAF anymore
01:02.48Torhal>.>
01:02.52Ressyo.O
01:02.58RessyI'm working on them tonight btw
01:03.03Ressyso ty for the whitelist. :)
01:03.21TorhalI'm thanking me for the whitelist because I'm the one on queue duty.
01:03.23Torhal<.<
01:03.23*** join/#wowace Ketho (~Ketho@ip565063bd.direct-adsl.nl)
01:03.29Kesavaty :D
01:04.12znfwell, crap, now I don't have a reason to bug you anymore :(
01:05.04znfSo... any ideas why my commits don't appear?
01:05.10znfIs it because I'm an Author and not the owner?
01:05.14znfhas something to do with permissions?
01:05.49TorhalDunno. They're doing some work right now that may fix it.
01:07.26Ressysnickers
01:07.40znfmars
01:07.42znftwix
01:08.11znfbounty? milky way?
01:21.42*** join/#wowace jlam (~yaaic@2600:380:bd3c:b444:f558:ad28:58ad:6bd5)
01:25.25Zeldoznf> So... any ideas why my commits don't appear?
01:25.27ZeldoWhat do you mean?
01:26.15znfZeldo, I pushed to broker_microclock and broker_lootspec
01:26.29znftaged and everything
01:26.32znfnothing's happening
01:28.04*** join/#wowace jilong (~yaaic@pool-98-109-225-39.nwrknj.fios.verizon.net)
01:30.10ZeldoOkay let me look
01:30.56ZeldoThey both “failed"
01:30.58*** join/#wowace jlam (~yaaic@pool-98-109-225-39.nwrknj.fios.verizon.net)
01:30.58ZeldoLet me ask
01:40.44Zeldoznf: Apparently one of your deps is accessing /trunk on a git repoi
01:40.46ZeldoNot sure which
01:40.51znfall
01:41.07ZeldoThere is no trust on them
01:41.11Zeldotrunk*
01:41.26znfOh...
01:41.30Zeldoalso you did not need to update your URLs
01:41.35Zeldothe packager will convert for you
01:41.36znfso what about https://repos.wowace.com/wow/ace3/trunk/AceLocale-3.0 ?
01:41.51znfI need to remove trunk from everywhere?
01:42.05ZeldoIf its a git repo yes
01:42.08Torhalznf: No LibPubSub is Git
01:42.09ZeldoAce3 for example is SVN
01:42.16TorhalYou're referencing /trunk in the .pkgmeta
01:42.24TorhalGit repos have no trunk
01:42.30Zeldo^
01:42.36znffuck this
01:42.40znfreverting .pkgmeta
01:42.46ZeldoThat works as well
01:42.50TorhalJust remove /trunk from that single line
01:42.54znfI can't figure out now which are svn and which are git
01:42.56Funkeh`if only you used .git extensions
01:43.03TorhalThey're all SVN except for the one I named
01:47.09znfsomehow my tortoisegit credentials don't propagate to CLI git
01:47.10TorhalFunkeh`: You get the information the same way you would have on the old site: You go to the project, look at the repo settings. Yes, it used to have .git in the URL but now it specifically says "The project's source code is available using Git." instead.
01:47.31znfand I have to enter the U/P every time
01:47.42Funkeh`what if I don't want to look at the project page
01:47.48znfok, I pushed
01:47.49znfnow what
01:48.00znfthere's still nothing on broker_microclock
01:48.18Funkeh`I mean I wonder what type of repo this could be? https://github.com/BigWigsMods/BigWigs.git
01:48.20TorhalFunkeh`: How did you get the repo URLs on the old sites? You looked at the project page.
01:48.22znfit shows up on broker_lootspec
01:48.26znfbut not the tag
01:48.50znfonly alpha
01:48.51Funkeh`Torhal, no, you can, you know, PM people, on any client on the internet
01:49.00znfand apparently I'm still under review
01:49.14Funkeh`not to mention other packager scripts now need to scrape files to detect what type of repo it is
01:49.48znfso, I pushed broker_lootspec together with a tag (1.5.6)
01:49.48Funkeh`now if someone links me a repo I need to go to the project page to see what client I need to pull it
01:49.52znfyet it only packaged it as alpha
01:49.52Torhalznf: The file processors are running on your file. That's why it says "Under Review"
01:50.09ZeldoThey ran
01:50.16ZeldoHis file is alpha, that is the problem
01:50.20znfTorhal, how about "packaging"? :P
01:50.30Torhalznf: It packaged or the file wouldn't exist
01:50.49znfok, how about broker_microclock?
01:50.55znfnothing's going on there
01:52.28Funkeh`hey Torhal check out my cool new project you can get it here https://repos.wowace.com/wow/awesomeproject/
01:55.54Zeldoznf investigating
01:57.45Funkeh`Zeldo, is someone looking into fixing bigwigs?
01:58.49ZeldoYes, there seems to be an issue with the syncer
01:58.53ZeldoIt’s being looked at
01:59.08ZeldoThe issue only happens on a handful of projects
02:01.24Funkeh`yeah, others were fine
02:02.35ZeldoThey are actually trying to figure out the solution as we speak.
02:03.29Funkeh`crack the whip
02:09.37*** join/#wowace Megalon (~wig0r@213-157-157-61.adsl.highway.telekom.at)
02:12.18Zeldoznf: Can you push any commit at all to micro clock?
02:12.28ZeldoJust to kick the packager, looking at an interesting issue
02:18.20znfZeldo, done
02:33.03ZeldoThanks, they are working on the packager to fix the issue
02:36.34TorhalZeldo: Timmeh just pushed a version that packaged.
02:36.55ZeldoYes I know, but it was still stuck as an alpha
02:37.03TorhalAh
02:37.56znfwth Timmeh!
02:38.41Torhalznf: I was wrong - it was just uploaded as him
02:39.02znfoh
02:44.09ZeldoIts fine :P
02:46.59*** join/#wowace AmiYuy (~AmiYuy@cpe-104-172-205-250.socal.res.rr.com)
02:48.33legowxelab2z8How can I check the packager status of my project?  my pkgmeta needed to be updated with an explicit package-as since that seems to have been lost in the migration. I pushed a new commit along with a tag but I don't see anything new under files. my project is https://www.wowace.com/projects/adibags-legion-filters
02:54.52Torhallegowxelab2z8: Looking at it.
02:55.45TorhalZeldo: ^
02:55.53TorhalSays Completed.
02:59.00Zeldokk, will have him look
03:19.39znfoh god
03:19.48znfit took forever to do trial of valor on LFR
03:28.55Zeldoznf, we pushed a new packager, can you push a new tag with a change of some sort? This one should package as a release so please tag appropriatly for your project :)
03:29.04ZeldoStanzilla: You still around?
03:29.55znfLet's see if I can do this from bed via teamviewer
03:31.10Zeldo:P
03:33.02znfOh new tag
03:33.04znfDamn it
03:35.12Zeldolegowxelab2z8: Your repo is pushed to /dev
03:35.16ZeldoPlease push it to /master
03:35.22Zeldoznf :P
03:37.42znfI did it
03:37.53znfI think
03:38.20ZeldoYou didn’t tag :P
03:38.22ZeldoAgain
03:47.20*** join/#wowace Kesava_ (~kesava@static-84-9-181-33.vodafonexdsl.co.uk)
03:47.20*** join/#wowace Kesava_ (~kesava@unaffiliated/sliker)
03:53.25znfPretty sure I did
03:54.00TorhalI don't see a tag.
03:54.15znfhttps://usercontent.irccloud-cdn.com/file/kG7Clm3M/Screenshot_2016-11-18-05-53-57.png
03:54.17TorhalYou might have made one, but it wasn't pushed.
03:54.30Torhalo.O
03:54.57TorhalI only see 1.10.2 in my copy of the repo.
03:55.09TorhalAnd three commits after
03:55.54znfhttps://usercontent.irccloud-cdn.com/file/y54mwgPm/Screenshot_2016-11-18-05-55-32.png
03:57.49legowxelab2z8A few hours ago I pushed and tagged a v1.3.2-beta (bugfix for a beta version) to my /dev branch and it made a file that needed review. That file got rejected by torhal since the .toc didnt match the folder name.  I was using the wowace package as under the repository settings which seems to be removed now. I change my .pkgmeta to include a package as: option. I tagged that commit as v1.3.2-beta2. I can't tell if my new .pgkmeta
03:58.04znfHow the hell do I tag from cli
04:00.09legowxelab2z8No file was created after pushing the v1.3.2-beta2 tag
04:01.11znfSee Torhal
04:01.12znfhttps://usercontent.irccloud-cdn.com/file/ZAtwJqrs/Screenshot_2016-11-18-06-00-55.png
04:01.53znfTeamViewer is hard
04:03.04Zeldo@Torhal please help legowxelab2z8
04:03.14TorhalZeldo: I'm looking at it right now
04:05.35ZeldoStanzilla: Packaging and then tagging is fixed
04:05.44ZeldoYou can push an alpha then tag it and it will build now
04:06.48Torhallegowxelab2z8: I don't know why your initial push packaged, since we only package off of master, but if you could merge dev into master and then push, you should get a file. If not, please let me know.
04:10.08legowxelab2z8So I need to merge dev into master every time I want it to make a beta package? I'm working on a new feature that still needs testing which is why I have been pushing to dev instead of master. I have been using the master branch for stable releases.
04:11.06TorhalOne sec
04:12.18TorhalOk, yes - confirmed: We only build from the master branch.
04:12.41znfWhy did I open this fashion app. Now I'm tempted to buy shoes again damn it
04:13.48znfI definitely have a shoe problem
04:15.45legowxelab2z8I'm new to git and how braches are typically done, but what is the point of having different branches if you always need to merge back into master to package? Should I just be doing everything under master and only tag for releases? it seems like that would be difficult to track feature changes. Any links for how I should do braching would help if you don't want to explain how to use git since that is out of scope.
04:16.07znfSo what is my package doing?
04:18.22AmiYuylegowxelab2z8: This might help- https://guides.github.com/introduction/flow/
04:18.45Torhallegowxelab2z8: I've always internally tested feature branches until I'm satisfied that they're up to snuff, and then merged into master and released. Afterward, if there are issues, people report them.
04:19.49TorhalIf the branch isn't ready, and there are issues in "stable" I make the fixes in master then merge those into the feature branch.
04:22.04Torhalznf: 1.10.4 is on the site
04:23.24Torhallegowxelab2z8: You can still push other branches, but those will only be available to collaborators.
04:23.41TorhalThey can pull them, make changes, push those, and your users will not see them.
04:29.33quiescenswhat did znf break this time?
04:29.58*** part/#wowace Seerah (~RyanNL@104-180-66-29.lightspeed.mmphtn.sbcglobal.net)
04:31.33TorhalAll The Things™, quiescens.
04:33.31znfsomeone explain me this http://i.imgur.com/GLmCoux.png
04:33.40znfwhy is $EMAG only last line? O.o
04:35.27Torhallegowxelab2z8: After merging into master, you can also just tag betas or not tag at all to produce alphas if you'd rather have people do intensive testing before you make a release tag.
04:35.52TorhalMost people have their app set to download only Release files, and those that don't are used to things being broken.
04:37.16*** join/#wowace jlam (~jlam@pool-98-109-225-39.nwrknj.fios.verizon.net)
04:39.53*** part/#wowace jlam (~jlam@pool-98-109-225-39.nwrknj.fios.verizon.net)
05:06.39*** join/#wowace Aiue (~aiue@h-4-145-174.a163.priv.bahnhof.se)
05:34.30*** join/#wowace stolenlegacy (~stolenleg@unaffiliated/stolenlegacy)
05:52.57*** join/#wowace ShadniX (dagger@p5DDFE1EC.dip0.t-ipconnect.de)
06:00.07*** join/#wowace Bribri (~Brybry@unaffiliated/brybry)
06:37.39*** join/#wowace Kesava_ (~kesava@static-84-9-181-33.vodafonexdsl.co.uk)
06:37.39*** join/#wowace Kesava_ (~kesava@unaffiliated/sliker)
07:02.02*** join/#wowace Elmoe_ (~Elmoe@24.18.131.251)
07:16.42*** join/#wowace devnull84 (~devnull84@196.15.203.251)
07:33.36*** join/#wowace Elmoe (~Elmoe@24.18.131.251)
07:44.03*** join/#wowace devnull84 (~devnull84@196.15.203.251)
07:55.02*** join/#wowace devnull84 (~devnull84@196.15.203.251)
08:27.43Timmehznf: whut?
08:27.47Timmehznf: you pung?
08:28.01TimmehTorhal: you pung too?
08:28.24TorhalTimmeh: Yeah, never mind though - was a system eccentricity.
08:28.29Timmehokay
08:28.49Timmehwas it about Broker: TimeToExecute, the thing znf fixed the other week?
08:28.57TorhalMicroClock IIRC
08:29.10Timmehah ok
08:29.20Timmehwas there fixing needed on that one as well?
08:29.27TorhalThe new system currently attributes any packager builds to the project owner instead of the person who initiated the build, so I mistakenly thought you did what he could not.
08:29.33Timmehah I see
08:29.45Timmeh"new system" oooo
08:29.47Timmehhow fancy
08:29.50TorhalHeh
08:30.38TimmehI don't see any changes in the git repos, though
08:30.41Timmehso not sure why things were built
08:31.17TorhalTimmeh: Migration obsoleted the old repos - there are new URLs.
08:31.23Timmehooo
08:31.40Timmehmust've happened in the last 2 weeks then
08:31.43Timmehvery new system then :-P
08:31.48TorhalYesterday actually :)
08:32.01Timmehwell, grats on getting it out and live :-)
08:32.11Torhal:D
08:32.16TorhalTimmeh: https://www.curseforge.com/docs/repomigration
08:32.45Timmehthanks
08:33.07Timmehwaow wowace looks fancy
08:33.38*** join/#wowace Elmoe (~Elmoe@24.18.131.251)
08:36.30*** join/#wowace Megalon (~wig0r@213-157-157-61.adsl.highway.telekom.at)
08:38.11Timmehall cloning now happens thorugh https?
08:38.35Timmehoh nvm, found it in the doc you just linked
08:55.09nevcairielTorhal: re earlier discussion, imho the packager should just package all tags, irregardless of which branch they are on, this will enable betas for upcoming expansions or other major API changes that are not ready to go mainline, ie. at a time when you do want to run two in parallel
08:56.27TorhalI'll submit that as a suggestion. It's definitely something that would be nice to have.
09:18.05*** join/#wowace devnull84 (~devnull84@196.15.203.251)
09:32.40nevcairielTorhal: why does the maintainer role not get repository access? that seems backwards
09:33.01Torhalnevcairiel: That's a damn good question. Fixing.
09:34.36TorhalOk, fixed on wow.curseforge and wowace
10:36.08TimmehTorhal: is there no repo anymore, telling us what changed when? :-(
10:36.22Timmehor is he in his own little channel now, or something?
10:36.51Timmehmisses Repo.
10:36.56TimmehRepo: how are you today?
10:36.58nevcairielrepo is on vacation
10:37.20TimmehI guess he still needs to be hooked up or something
10:40.20Timmehznf: I'll quickly retag all repos, so their actual builds show up in files o.o
10:40.53Timmehznf: broker_timetoexecute shows 1.1.2 as latest version, even though you tagged a 1.1.3
10:41.25Timmehznf: broker_lootspec shows an alpha file instead of 1.5.6 (what actually happened to 1.5.{2,3,45}? o.o)
10:41.46Timmehznf: and broker_microclock, wth did you do the commit history? xD
10:45.34Timmehand now it built 1.5.6 as well for broker_lootspec, even though it did already exist :-P
10:45.45Timmehoh well, it built all files now
10:45.47Timmehso all is good
10:46.43Timmehnice, even syntax highlighting in descriptions now
10:46.49Timmeh(as long as it's code blocks, at least)
10:49.44Timmehnevcairiel / Torhal: is .docmeta still being processed, or is it still in the works for the new environment (or just gone)?
10:50.14nevcairielafaik the documenter doesnt exist yet on the new platform, but maybe in the future, or so Kaelten tells me
10:52.01Timmehalright
11:05.52TorhalTimmeh: It's listed in our internal tracker
11:06.05Timmehalrighty
11:06.25Timmehall this work you guys do, you guys actually work for Curse, right? this isn't voluntary stuff?
11:06.30Timmehjust checking
11:06.38Timmehif it's voluntary stuff, I'm happy to help out on things if I can
11:06.47Timmehif you get paid, I'll just complain :-D
11:07.32TimmehTorhal: another thing for your internal tracker: syntax highlighting language detection of the new Description stuff is pissing me off :-D
11:07.55TorhalI blame Stanzilla.
11:08.03TorhalI'm an employee.
11:09.07Timmehalrighty
11:09.24Timmehsince you put it that way, are there also people working on it that aren't, then?
11:09.47TorhalNot on the site, no.
11:09.52nevcairielonly in a moderator capacity like myself and Stanzilla
11:09.57TimmehIC
11:09.59Timmehalrighty
11:10.01TorhalVolunteer moderators for projects and files, the forums, stuff like that
11:10.07nevcairielback in the good old days we actually had the ability to fiddle with some of the code
11:10.09nevcairiellike the documenter
11:10.22nevcairielthey had a curseforge project for curseforge!
11:10.22nevcairiel:D
11:10.45Timmehhah alright
11:10.51nevcairieli fixed some of the documenter behavior back then myself
11:10.55*** join/#wowace devnull84 (~devnull84@196.15.203.251)
11:10.57nevcairieli'm sure that code was still in use until last week
11:10.58nevcairiel:p
11:11.11Timmeh:-D
11:12.15Timmehany idea what markdown extensions are used for the description thing?
11:12.25Timmehit'd be nice to be able to force the language of the syntax highlighting
11:13.30TorhalNo idea :/
11:13.35Timmehor otherwise, maybe force it to lua on a project (or site?) basis, or something :-P
11:13.37*** join/#wowace devnull84 (~devnull84@196.15.203.251)
11:13.49TorhalTry '''lua perhaps?
11:13.52Timmehthe github flavours don't work, at least (the thing that adds ```lua)
11:13.54Timmehyea
11:13.56TimmehI tried that :-P
11:14.03Torhal``` lua maybe?
11:15.00Timmehnah, it just stops syntax highlighting alltogether with ``` around
11:15.19Timmehit appears to add <code> tags for ```
11:15.32Timmehand the syntax highlighter probably only picks up <pre> tags (which is logical, and I guess it should)
11:15.43Timmehand it just adds "lua" or " lua" as part of the <code> content
11:15.52TorhalSee what you can find out at https://www.curseforge.com/paste
11:16.41Timmehas in, what it detects?
11:17.08Timmehit actually appears to detect differently there (however still wrong)
11:17.10Timmeh:-D
11:17.18TimmehI mean, it's not a huge issue
11:17.22nevcairielmaybe your Lua just isnt very .. Lua!
11:17.22nevcairiel:D
11:17.26Timmehobviously the focus is not documentation
11:17.28TorhalPyLua!
11:18.12TimmehI can understand why it miss-detects anyway :-P
11:18.15Timmehbut still annoying :-D
11:18.41Timmehhttps://www.wowace.com/projects/libpubsub-1-0 - 6 code snippets, detected as: ruby - ruby - lua - css - css - css
11:19.54nevcairielits funny how all of it looks different
11:20.10TorhalOk, enabled pastes on wow.cf and wowace
11:20.35nevcairielbeing able to specify the language would be neat
11:20.48TorhalYeah, I actually thought that was a thing
11:20.50nevcairielbut purely cosmetical of course
11:21.23Timmehmost markdown libraries support multiple markdown extensions / addons to be added (or even just enabled)
11:21.54Timmehand since that generally just adds class names
11:22.00Timmehmost syntax highlighting libs pick that up
11:22.25Timmehby "that" I mean the specific extensions for language of code blocks
11:25.23TorhalI'm going to go eat and watch some shows. Have fun :)
11:25.26nevcairieldoes it only support the indent code blocks, not any explicit markers?
11:25.40Timmehit appears that way
11:26.06Timmehwhat language do you guys use for the platform?
11:26.08Timmeh:-D
11:26.18nevcairielhttps://www.wowace.com/projects/libbuttonglow-1-0
11:26.21nevcairielno idea what language it picked
11:26.25nevcairielbut it looks broken :p
11:26.42Timmehyou can see from the class name on the code block :-P
11:26.44Timmehit's css
11:27.50TorhalGoogle tells me this: https://highlightjs.org/usage/
11:28.05TorhalSo maybe using the WYSIWYG you can do something?
11:28.11Timmehbut but
11:28.13Timmehmarkdown
11:28.15Timmeh:-(
11:28.23Timmehif the platform happens to be built in Python, and happens to use the Markdown lib from pypi (which seems logical in that case), just enabling the "extra" or "fenced_code" extensions should do the trick :-D
11:28.23TorhalI know :/
11:28.30Timmehhttps://pythonhosted.org/Markdown/extensions/fenced_code_blocks.html
11:28.31TorhalC#
11:28.33Timmehah k
11:28.53Timmehwhat markdown lib? :-D
11:28.59TimmehI can try and check it out
11:29.07Timmeheither way, enjoy your eating and watching of shows
11:29.25TorhalNo idea which lib, I only found what I linked via Googling "hljs" :)
11:29.30Timmehalright :-)
11:29.34Timmehthanks anyway
11:30.06Timmehtechnically one could embed HTML in markdown >_>
11:30.13nevcairieli tried that, didnt work
11:30.54Timmehah
11:31.20nevcairielit quotes the <>
11:31.25nevcairielso it shows up as-is
11:31.28Timmehright
11:31.43Timmehmakes sense from a security point of view
11:32.11Timmehmaybe we can find a bug in the parser to abuse :-P
11:32.12nevcairielnot particularly since the WYSIWYG is just html
11:32.16Timmehoh
11:32.19Timmehyea, ok
11:35.00nevcairielyou can even edit the raw html in that mode
11:35.07nevcairielbut it doesnt like the code block with custom language
11:37.57nevcairielZeldo: https://www.wowace.com/projects/libbuttonglow-1-0/relations/dependents just error'ed out for me
11:38.42nevcairielin other topics, where is my grocery delivery, it was supposed to be here between 10 and 12
11:38.46nevcairieland its 12:40!
11:40.08Timmeh:-(
11:47.44nevcairieljust had to complain a bit and it arrived, its funny how that works sometimes
12:05.06*** join/#wowace ven (ven@unaffiliated/ven)
12:05.47*** part/#wowace ven (ven@unaffiliated/ven)
12:10.33*** join/#wowace devnull84 (~devnull84@196.15.203.251)
12:48.36znfTimmeh, the packager was broken for that project, that's why I pushed so many times
12:48.41znfwas being useful
12:52.27Timmehyup yup, it's fine :-)
12:52.36Timmehthanks for the effort again, really
12:53.03Timmehznf: ^
12:53.31Timmehthe history just looked a bit awkward :-P
12:53.39Timmehbut it's fine, it works
12:53.44Timmeh(or at least, I think it does)
12:55.04*** join/#wowace devnull84 (~devnull84@196.15.203.251)
13:16.25nevcairielZeldo: Torhal: localizations are broken and not put into files
13:16.37Timmeh:-(
13:16.45nevcairielhttps://www.wowace.com/projects/routes/files see 1.5.5 tagged a few hours ago, its severly smaller and all locale files are empty
13:17.28nevcairielhttps://www.wowace.com/projects/routes/files/2346150 the broken one, i archived it now to avoid people downloading it
13:17.56Timmehconfirmed
13:18.49TimmehI just checked my plugins, they actually show in the files:
13:18.51Timmeh--@localization(locale="enUS", format="lua_additive_table", handle-unlocalized="english", escape-non-ascii=true, same-key-is-true=true)@
13:18.59nevcairielyeah that stuff is supposed to be replaced
13:19.03Timmehyup
13:19.21Timmehthe "--@do-not-package@" stuff is removed, but does leave the "--@end-do-not-package@"
13:19.24Timmehwhich is also kinda awkward :-P
13:19.27Timmehbut less of a problem
13:21.12*** join/#wowace jlam (~yaaic@pool-98-109-225-39.nwrknj.fios.verizon.net)
13:21.23nevcairiela bug nontheless
13:21.50Timmehnevcairiel: if only we could fiddle with the code ourselves, amirite? :-P
13:22.29nevcairielindeed
13:36.04*** join/#wowace stolenlegacy (~stolenleg@unaffiliated/stolenlegacy)
13:36.04TorhalWTF?
13:36.08TimmehWTF!
13:36.11TorhalThat shit was working.
13:36.46Timmeh:-(
13:36.48TimmehI blame Stanzilla.
13:39.58TorhalI think he and nebula worked together.
14:26.06*** join/#wowace Ressy (~Ressy@WoWUIDev/WoWAce/ARL/Ressy)
14:39.53StanzillaTorhal Zeldo can confirm, WA was packaged without locales, too
14:39.58Stanzillahad to delete the release
14:41.34*** join/#wowace jlam (~yaaic@2600:380:bd3c:b444:f558:ad28:58ad:6bd5)
14:41.38Funkeh`scrubs]
15:03.57*** join/#wowace Megalon (~wig0r@213-157-157-61.adsl.highway.telekom.at)
15:08.01TimmehI pushed versions of my broker-addons with localisations manually added
15:08.27Timmehcan someone please ping and/or poke me when it's fixed at some point? :-)
15:38.38quiescenso.o
15:38.55quiescenswhat did you break timmeh
15:43.35Funkeh`life
15:51.09ZeldoWhattttt we even tested it with WA
15:51.17ZeldoFucking fuck
15:55.39Funkeh`bad
16:02.16Stanzilla¯_(ツ)_/¯
16:16.38*** join/#wowace Aiue (~aiue@h-4-145-174.a163.priv.bahnhof.se)
16:19.04ZeldoStanzilla: Can you push please?
16:19.23ZeldoShould be fixed on WoWAce but I want to double check before I fix it on WoW
16:22.57Stanzilladone
16:23.54Zeldotyty
16:23.58StanzillaZeldo: not fixed
16:24.28Stanzilladeleted the file
16:24.55ZeldoIt was still running
16:24.56Zeldo93c31ac-alphaWeakAuras 2Non-existent localization namespace "WeakAuras / Options" for locale "deDE." Failed lookup at " Options."SystemHighRejectedProcessor ActionNo<1 min ago
16:26.10*** join/#wowace Phixion (phixion@epsilon.phixion.org)
16:27.05nebulawa is weird and has spaces in it's namespaces in the files, should try fixing that
16:28.23ZeldoHrm, yea
16:28.35ZeldoWe can’t even trim those on our side because you can have spaces in your namespace
16:28.44Zeldo“Bob The Builder” is a valid namespace name
16:29.39nebulai used wa as a test for my packager, had to add some hacky shit to make it work, should have just yelled at Stanzilla
16:31.11Stanzilla:E
16:31.27nebulaalso, you can easily trim them on your side after splitting
16:31.40ZeldoWe don’t split
16:31.47nebulalookup at " Options."
16:31.49ZeldoWe have them on our side already mashed
16:32.07ZeldoSo its looking for WeakAuras/Options as the namespace “name"
16:32.19ZeldoNot Options thats part of WeakAuras
16:33.15nebulawell no shit, but it was checking vs " Options", so it's obviously splitting the string from the file then doing the check
16:36.39nebulaalso, i'm pretty sure spaces weren't valid in namespace entries, "Bob The Builder" would have errored if you tried to use it on the old system
16:37.25*** join/#wowace darkValorous (uid90505@gateway/web/irccloud.com/x-sarygqkogsuxwlxi)
16:38.13*** join/#wowace jlam (~jlam@216.194.53.60)
16:40.52nevcairielRoutes failed before as well, tha tdoesnt even use namespaces at all
16:42.57ZeldoBefore yes, it should be fixed now
16:43.03ZeldoThat’s how I got that error ^
16:43.11ZeldoIf you push it again now it should localize it
16:45.49Funkeh`are we having fun yet
16:47.18FiskerI'm gonna hug Stanzilla one day
16:48.00Funkeh`woah
16:48.04Funkeh`getting crazy now
17:12.27*** join/#wowace jaxdahl (jaxdahl@ypsilon.residential.okstate.edu)
17:27.27*** join/#wowace SniperFodder (~SniperFod@www.silicateillusion.org)
17:29.17nevcairielZeldo: looks good, although its slightly confusing it briefly shows a file without locale which then gets replaced .p
17:32.28ZeldoYea, it should happen befor ethe file is approved
17:32.53ZeldoIt’s just because of the way the file processors work and the fact that inserting localization isn’t insant
18:07.53*** join/#wowace Yoshimo (~anything@unaffiliated/yoshimo)
18:19.49*** join/#wowace Seerah (~RyanNL@104-180-66-29.lightspeed.mmphtn.sbcglobal.net)
18:20.25Stanzilla.
18:20.47KaeltenFisker that's just uncalled for man...
18:22.22FiskerHuh?
18:24.56nevcairielcant threaten to a hug a man
18:30.44*** join/#wowace jlam (~yaaic@mobile-166-172-063-144.mycingular.net)
18:44.15StanzillaZeldo: why are files in CC always "modified"?
18:44.19Stanzillabigwigs in this case
18:44.23Stanzillahave to click it on every update
18:44.33Funkeh`literally just noticed that
18:44.40Funkeh`it updates fine
18:44.43Stanzillayes
18:44.43Funkeh`then you click refresh
18:44.51Stanzillajust goes back to modified
18:44.52Funkeh`and it says the old version, but it's actually the new version
18:45.31Funkeh`at least it's showing up now though \o/
18:50.06*** join/#wowace jlam (~yaaic@mobile-166-172-063-144.mycingular.net)
18:54.20*** join/#wowace Phixion (phixion@epsilon.phixion.org)
18:56.31ZeldoStanzilla: Can you report that in the client?
18:56.37ZeldoThe client team will have to take a look at that
18:56.40Stanzillayeah
18:56.54ZeldoMight be over cautious so that we dont overwrite a modified copy
18:57.06*** join/#wowace jlam (~jlam@216.194.53.60)
18:57.14ZeldoCan you zip the current install of the addon and send it to me as well?
18:58.03StanzillaZeldo: https://dl.dropboxusercontent.com/s/x4pc42vdqb21nxd/BW.zip
18:58.05Elmoeis there a known bug where the curse client shows all add-ons as 'modified' now when an update is pushed?  I'm assuming this is related to the curseforge migration somehow
18:58.10Zeldoty Stan
18:58.18StanzillaElmoe: that is literally what we are talking about
18:58.21Funkeh`I would say it's most likely some kind of cache issue
18:58.24ElmoeStanzilla: oh hah
18:58.35Funkeh`because it's thinking it's the pre-transition version Zeldo
18:58.38Elmoereminds me to read the backlog first heh
19:00.34Elmoeok I filed a bug report inside the curse client for that
19:00.42ZeldoTyty
19:00.44Elmoehas there been any new ETA on the ticket system being back up?
19:01.01ZeldoEarly next week at this time
19:01.40ZeldoIt’s not Funkeh` I was able to replicate
19:01.50ZeldoI manually installed an alpha and its still “Modified"
19:02.01ZeldoI think its a fingerprinting issue
19:03.36jlamIs source code available for the CC?
19:04.05ZeldoNope :\
19:32.09*** join/#wowace Cairenn (~Owner@MMOI/Administratrix/Cairenn)
19:32.09*** mode/#wowace [+o Cairenn] by ChanServ
19:50.08*** join/#wowace EthanCentaurai (~EthanCent@79-76-215-146.dynamic.dsl.as9105.com)
20:00.20*** join/#wowace EthanCentaurai (~EthanCent@79-76-215-146.dynamic.dsl.as9105.com)
20:00.42TorhalElmoe Issues are back.
20:01.33ZeldoDashboard is back as well
20:01.37ZeldoWith packager status for your projects
20:04.25Elmoehuzzah!
20:04.26Elmoeawesome
20:18.46*** join/#wowace Kesava_ (~kesava@static-84-9-181-33.vodafonexdsl.co.uk)
20:18.46*** join/#wowace Kesava_ (~kesava@unaffiliated/sliker)
20:26.23*** join/#wowace LexSfX (LexSfX@216-71-194-85.dyn.novuscom.net)
20:41.40*** join/#wowace Kultzi (~ironi@85-76-67-7-nat.elisa-mobile.fi)
21:25.07*** join/#wowace Elmoe_ (~Elmoe@24.18.131.251)
21:47.15*** join/#wowace Elmoe (~Elmoe@24.18.131.251)
21:50.52Elmoehmm is there no easy way to tell which issues have new comments since you last read them?
21:52.21Elmoealso for some reason all the old closed tickets are set to open after the migration
21:52.44Elmoeit seems like the old closed reasons have been converted to tags
21:52.47Elmoebut the status is now open again
21:53.03Elmoeeg. a ticket that was 'marked as invalid' is now tagged with 'invalid' but status is open rather than closed
21:56.41Elmoehmm don't seem to be receiving email notification wrt issues now either
21:56.53Elmoeis there a wowace issue tracker somewhere where we should be filing all the bugs we find?
21:57.39Stanzillanope
22:01.42Elmoealso interesting some tickets are not showing recent comments prior to the migration
22:02.08Elmoewhats odd is this is inconsistent
22:02.27Elmoelike I see tickets that were filed just before the migration occurred and then other tickets older than that are missing comments
22:10.51TorhalElmoe: Go to your preferences, notifications, and turn off daily digest.
22:13.54Fiskerhugs Stanzilla just to watch him get squeezed
22:14.04FiskerI'll do what I want
22:15.06TorhalDon't make him throw you on the ground.
22:16.01ElmoeTorhal: got it thanks
22:16.17ElmoeTorhal: any thoughts on the other issues?
22:16.39TorhalI think Zeldo should make tickets.
22:16.40Torhal>.>
22:16.42Torhalhides.
22:16.43Elmoeagreed
22:16.53ElmoeI am happy to file tickets for issues I find to help better track things just don't know how
22:17.38TorhalThey're internal, so you need to tell one of us. Since I'm about to pass out hardcore mode, that'd be Zeldo at the moment.
22:18.27Elmoeok will try to ping Zelda when he comes back around
22:18.30Elmoego get some sleep dude
22:20.33TorhalActually, screw it. I'll copy/paste it into an email then go to sleep.
22:20.48ZeldoI’ve got it
22:21.03ElmoeZeldo: basically two issues I've found thus far
22:21.12ZeldoYea, I am trying to think of solutions
22:21.13ElmoeZeldo: 1.) tickets that were marked as closed are now open after migration
22:21.33ElmoeZeldo: 2.) data migration seems incomplete.  some tickets are missing recent comments
22:21.58ZeldoDo you have an example of #2?
22:22.09Elmoefor issue one since the tags are correct, you could just bulk mark as close tickets that have tags like 'invalid' 'fixed' etc.
22:22.15Elmoefor #2 let me get you a ticket
22:22.30Elmoevuhdo seemed fine but then I checked a ticket I had commented in on another author's addon and it was missing my comments
22:23.04Elmoehttps://wow.curseforge.com/projects/gnosis/issues/87
22:23.14Elmoethe last comment is from nov 6th
22:23.19Elmoebut there were 2-3 comments past that before migration
22:44.38ZeldoElmoe: I am going to file a ticket to fix issues
22:44.44ZeldoBut there are a few more pressing things infront of that
22:44.51ZeldoAs for the missing comments I will have them take a look :)
22:44.55Elmoek
22:45.24ZeldoBut I waslooking at the project you listed and it shows the proper ones closed
22:45.32ZeldoDo you have examples of unclosed ones that should be?
22:45.49Elmoehttps://wow.curseforge.com/projects/vuhdo/issues/735
22:45.54Elmoehttps://wow.curseforge.com/projects/vuhdo/issues/740
22:46.09Zeldotyty
22:46.12Elmoethey have a tag which reflects the old 'marked as' closure reason but the ticket status is still open
22:46.29ZeldoYea, I think a few tags were not marked as closed
22:46.31ZeldoBut most work
22:48.07Elmoealso in general the old issue tracker had much richer filter/search capabilities than the new one
22:48.21Elmoenot high priority but it would be nice to eventually get feature parity with the old tracker in that regard
22:48.53Elmoeeven simple stuff like the number of ticket that match the current filter criteria are missing
22:49.10Timmehohai
22:49.43Timmehjust wondering whether the localizations thing has been fixed
22:50.16Timmeh(not to be pushy - other than `git push`y)
22:51.40nevcairiellocale are fixed
22:52.12TimmehTorhal: Zeldo: ^\o/
22:52.15Timmehwait
22:52.19Timmeh\o/*
22:52.28TimmehI apparently had already typed a pinging message
22:52.33Timmehnow I still pung them
22:52.35Timmeh<_<
22:52.47nevcairielhow evil of you
22:52.58TimmehI know right
22:55.13ZeldoYea they were fixed shortly after you left :x
22:55.22Timmehtypical :-P
22:56.02Timmehit's like nevcairiel's complaining about groceries not arriving
22:56.30nevcairielcomplaining helps things go faster
22:56.34nevcairieleven if noone hears the complaints
22:56.35nevcairielxD
23:01.36*** join/#wowace Megalon (~wig0r@212-60-168-24.adsl.highway.telekom.at)
23:07.32znfhow is Stanzilla not hyped about this? https://www.w3.org/TR/2016/REC-html51-20161101/changes.html#changes
23:08.49znfTimmeh, did you delete all my pushes? O.o
23:08.59Timmehno
23:09.04znf:o
23:09.08Timmehare you connecting with the old repo?
23:09.18Timmeh(that was my problem earlier today)
23:09.23znfomg, you archived my thingies! :P
23:09.32znfnah, I was looking at the file list
23:09.35nevcairielthey were broken
23:09.52ZeldoLocalization was borking znf
23:09.57ZeldoTis fixed now
23:10.00znfOh
23:10.05znfman, this Torhal guy... breaks everything
23:10.08Timmeh:-P
23:10.10Timmehoh yea
23:10.12Timmehyou mean those
23:10.14Timmehyea, I archived those
23:10.21Timmehso people wouldn't accidentally get stuff with broken localizations
23:10.52Timmehso I only archived the ones from today
23:11.00Timmehnot from before today
23:11.34znfwas the first time I changed stuff :P
23:11.45Timmehnot on Broker_TimeToExecute :-P
23:11.48znfI remember Gnarfoz complaining about _lootspec
23:11.52znfyes, not that one
23:12.02Timmeh*foz always complains :-D
23:12.38znfanyway, GOOD
23:12.43znfI've no idea about localization stuff
23:12.47znfdoesn't ever localize his addons
23:13.04Timmehyea well, sorry about the archiving, but I wanted to make sure people wouldn't end up with stupid errors
23:13.17znfit's ok
23:13.25znfI wasn't aware it was broken
23:13.30Timmehnor was I
23:13.39znfI don't think Zeldo was, either :D
23:13.49ZeldoHad I know I would have fixed it sooner :P
23:14.21TimmehI miss Repo though :-(
23:14.25Timmehsomeone should make Repo talk to us again
23:14.28TimmehREEEPPOOOO
23:14.36znfYes, that's what I said last night!
23:14.39znfWe want Repo!
23:14.49znfI never know if I commit properly unless Repo shows me!
23:15.43TimmehI know!
23:16.08Timmehznf: I just reverted the temporary locale fixes
23:16.10Timmehpushing them nao
23:16.26znfyour project!
23:16.48Timmehmaybe I should've only done one first
23:16.55Timmehto see if it's actually fixed :-P
23:18.19Timmehis there still a packager status page like there used to be?
23:19.40TimmehRIP https://www.wowace.com/packager
23:20.21znfhey Stanzilla https://clickclickclick.click/
23:21.10nevcairielTimmeh: you get one for your own projects here https://www.wowace.com/dashboard/builds
23:21.56Timmehoh fanceh
23:22.31Timmehexcept it says completed, but file doesn't show yet :-P I'll give it a minute
23:24.09*** join/#wowace AmiYuy (~AmiYuy@cpe-104-172-205-250.socal.res.rr.com)
23:26.40Timmehwait
23:27.44Timmehthat dashboard is actually pretty cool
23:27.51TimmehI like what you guys have done with it
23:28.16Timmehquiescens: you should give Zeldo a cookie
23:28.47nevcairieli wish https://www.wowace.com/dashboard/projects would have some filtering though, so that irrelevant projects could be hidden without having to go to individual status entries
23:29.05nevcairiel(so, smarter filtering, it does have some basic filters)
23:29.13*** join/#wowace Ressy (~Ressy@WoWUIDev/WoWAce/ARL/Ressy)
23:29.16nevcairielwhat do i care about projects I didnt even remember existed
23:29.20nevcairielsicne they are from the dawn of time
23:30.59AmiYuyThere are two "Enhancement" tags - One is spelled wrong (Enhancment) and that's the one automatically applied to all my tickets...
23:31.22Timmehmaybe a default order by latest change
23:31.23Timmehor something
23:31.25Timmehnevcairiel: ^
23:31.39nevcairielAmiYuy: funny enough i have a few tickets that have both tags xD
23:31.48AmiYuyOh my XD
23:32.23AmiYuyLooks like i have one of those
23:33.33nevcairieli'll probably use that chance to close a bunch of old ones and re-tag the existing ones properly
23:33.48AmiYuyThis is going to take some time to clean up, especially since you can't edit tags, I wish Status were still separate
23:34.33AmiYuyI hope it doesn't email the ticket creators each time I add/remove/change tags...
23:35.32TimmehZeldo: there is a small issue with "@do-not-package", it appears to leave in the "--@end-do-not-package@" at the end of it
23:36.14TimmehZeldo: at least in my situation, where there's a line with only "--@end-do-not-package@"
23:36.49ZeldoYup there is a ticket in for that timmeh
23:36.55Timmehalright
23:37.05Timmehare those tickets public?
23:37.13Timmeh(just so I know I don't report shit that's already in there)
23:37.20nevcairielthey are not
23:37.23Timmehalright
23:51.37Megalonanyone here have a survival hunter?

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.