« first day (733 days earlier)      last day (2447 days later) » 

00:02
Also sort when the grouping is changed.
Well, sorting when the grouping is being changed isn't cutting it. BBL.
00:20
@Mat'sMug Ready.
> Time flies. 6 whole weeks, 353 commits, 142* pull requests from 8 contributors, 143* closed issues, 60* new ones, 129,835 additions and 113,388 deletions in 788* files later, we go beta.

*From the GitHub "Pulse" page between May 7 and June 7, 2016.
okay
@Mat'sMug Hang on just a sec.
I'm running a couple tests, then I'll make a PR if it works.
We can get 1618 in the release then too.
updating TeamViewer
ok
I'm drafting the RD News post
Works.
@Hosch250 - Where should I be looking for a worker thread that spawns new worker threads?
00:25
@Comintern No idea.
We don't do any manual threading--we just use the dispatcher and the TPL.
@Comintern AFAIK the only place that happens would be in the parser
and ^^^ that
There you go, @Mat'sMug.
@Duga is down.
oh, awesome :/
Hmmm. Parser was my first thought too, but it seems to exit just fine. There are 3 threads open - the main one (expected), the GC finalizer (expected), one mystery thread that never exits. Outside of that, there are anywhere from 1 to 4 other threads that pop in and out of existence.
the inspections spawns a task
00:28
@Comintern The TPL will create threads based on the amount of work we give it.
In other words, more components to parse will create more threads.
I can't find anywhere where we're giving it work... Everything COM related is basically gone at that point.
@Hosch250 PR is out-of-date, care to sync?
@Mat'sMug Does it matter?
If there aren't conflicts, it shouldn't matter...
Except for the squash thing, maybe...
I'd like a green dot, this close to switching to release mode...
It will get a green dot anyway.
Only, now it will get two green dots because AppVeyor isn't smart enough to cancel the old build.
00:32
lol, that's allright, the good part is that we don't get @Duga screaming at us for it this time :)
See, we got our green dot on the first build.
Second build started.
allright screw this
00:35
Anyone want to sword fight while we wait?
4
[rubberduck-vba/Rubberduck] Hosch250 pushed commit 7d049a48 to next: Close #1618
[rubberduck-vba/Rubberduck] Hosch250 pushed commit 8955eb70 to next: Merge branch 'next' into Issue1618
Merge pull request #1730 from Hosch250/Issue1618

Correctly sort inspection results
[rubberduck-vba/Rubberduck] build for commit 8955eb70 on next: AppVeyor build cancelled
[retailcoder/Rubberduck] retailcoder pushed 22 commits to next (only showing some of them below)
[retailcoder/Rubberduck] Hosch250 pushed commit 7a2e04c9 to next: Close #1868
Umm, @Duga woke up just then?
Merge pull request #1726 from Hosch250/Issue1686

Adjust CE node icon position
I guess
00:37
She's been down for several hours.
[retailcoder/Rubberduck] Hosch250 pushed commit 3e5bc553 to next: Fix Use Meaningful Name selection and Remove Identifier Not Used--Variable quick fix
[retailcoder/Rubberduck] Hosch250 pushed commit 6f1bc8f2 to next: Fix broken tests
Note to self. You can't kill a process with an active external debugger attached. Facepalm
[retailcoder/Rubberduck] Hosch250 pushed commit e089115e to next: Merge branch 'next' of github.com/rubberduck-vba/Rubberduck into InspectionBugs
Merge pull request #1728 from Hosch250/InspectionBugs

Fix Use Meaningful Name selection and Remove Identifier Not Used--Var…
[retailcoder/Rubberduck] Hosch250 pushed commit 7d049a48 to next: Close #1618
[retailcoder/Rubberduck] Hosch250 pushed commit 8955eb70 to next: Merge branch 'next' into Issue1618
Merge pull request #1730 from Hosch250/Issue1618

Correctly sort inspection results
OK, @Mat'sMug, m18-787-059
Merge pull request #121 from rubberduck-vba/next

sync with main repo
00:38
huzzah!
wow, lag
Hang on a sec--going to create a clean branch for this.
Ready.
Merge pull request #1730 from Hosch250/Issue1618

Correctly sort inspection results
ok so you got the release config down. good
you know what sucks? I left my work laptop at the office, so I can't test the release build on another machine
[rubberduck-vba/Rubberduck] build for commit 4a32cae0 on next: AppVeyor build succeeded
@Hosch250 tag is v2.0b
@Hosch250 nah, drop the "preview" ;-)
00:43
What's listening to the TimerHook?
off the top of my head.......... that one was deactivated... is it?
@Hosch250 drop the cheesy part at the bottom ;-)
nice
OK, now to build the thing and stuff it in the installer.
you have the Inno Setup Compiler?
yup, last stable release will do
00:46
Stable release here? jrsoftware.org/isdl.php
Unicode?
uh
nah
gosh
I'm running 5.5.9 (a)
lol, are you really reading this?
More/less.
I skim it.
Well, a little more than skim.
OK, point out what to do.
First, build the release?
ok, now you're looking for the Installer Build Script.iss file in your repo
it needs to be updated
@Hosch250 it won't be in the solution
review the file/assembly version for all assemblies
Set everything to 2.0?
What about the indenter?
yeah, might as well
00:53
OK.
takes a deep breath
Visio, AutoCad?
@Hosch250 I wouldn't bother with those - they're there to discover the bitness of the Office install
huh, what happened to the script?
00:57
Closed it.
lol, reopen :)
..was in the recent files list
ok, Build
yup
takes another deep breath
#define OutputDirectory SourcePath + "\Installers"
Where?
That's it?
rename it to Rubberduck.Setup.2.0b.exe
you..
just messed up your COM registration I think :)
I know.
Just doing some testing to make sure things still work.
cool. I edited the draft
that looks weird...
uh-oh
01:04
...
...
First a resolver error, then SC crashes Excel when I try to merge...
got logging enabled?
I hope.
lol
I think we should disable the event sinks when importing/exporting stuff for SC
that Parsing...Resolving...Parsing...Resolving...Parsing...Resolving thing is utterly annoying
Me toooo.
Said in an Emo Philips voice
I got it to commit to remote :)
I'm curious about these exceptions though
01:12
> Source control crashed when I tried to merge to a remote branch. I have a feeling we should only be allowed to merge to local branches (then push to remote separately).
@Hosch250 wait a sec.. do we have everyone we should have in the about box?
> What constitutes "empty"?

White space? Option statements?
We don't have @Comintern in.
any other last-minute changes?
> I had a workbook that had previously hosted a Calendar Control. The control is long gone, but the reference remains. Would be nice to have an inspection that tells me it's safe to remove.
01:19
that's annoying too
oh crap
that's a serious one
What happened to the test explorer???
> Might need to consider whether a @Folder annotation is meaningful, if all other content is meaningless.

Might also need to determine if non-standard VB Attributes are set.
it's not resolved
It had been.
I force-reparsed it to try to make it work.
@Hosch250 I think making test discovery depend on parse results might have been a mistake. it's way too slow.
01:22
Everything is really slow.
ugh
@Hosch250 refresh the page
Hey guys, not to take things off-topic, but I did drop in to let you know. I've been working on some code to inspect type libraries. I've nearly gotten it to the point where I'm happy to publish it. I'll let you know when I have.
You might be interested in using it, I'll be OSS-ing it.
ouch
it still says "Error" @Hosch250
01:28
you're going too fast
Yeah...
I forgot whether I'd clicked Cancel.
we really need a taller settings dialog
I'll do another release in about a week.
> If it's empty-empty, then `OptionExplicitInspection` is already triggered.

I don't think we need an inspection for this. The code explorer would already display the module without anything under it...

That's the rationale?
[rubberduck-vba/Rubberduck] build for commit 4a32cae0 on next: AppVeyor build succeeded
01:32
@Hosch250 you need to uninstall, and then redo the initial setup steps. and don't forget to switch back to debug config :)
OK.
Got to work 15 more minutes.
I'll get the inspection settings working again.
And add @Comintern to the About.
too late, done already
[retailcoder/Rubberduck] retailcoder pushed commit 518bb154 to next: adding @Comintern to the about box - thanks mate!
Oh, OK.
Well, the beta has lots of bugs.
no shit
01:35
But, it is much better than the alpha.
Stick my head in a debugger and my pinger goes nuts.
Thanks!
01:39
[rubberduck-vba/Rubberduck] build for commit 518bb154 on next: AppVeyor build cancelled
[rubberduck-vba/Rubberduck] build for commit e99f44e3 on next: AppVeyor build cancelled
[rubberduck-vba/Rubberduck] retailcoder pushed 59 commits to next (only showing some of them below)
[rubberduck-vba/Rubberduck] retailcoder pushed commit 7286b610 to next: Merge branch 'next' into next
[rubberduck-vba/Rubberduck] retailcoder pushed commit 96626f7d to next: fixed FunctionReturnValueNotUsed firing on Sub procedures
[rubberduck-vba/Rubberduck] retailcoder pushed commit b9953664 to next: Merge branch 'next' into next
Merge pull request #119 from rubberduck-vba/next

sync with main repo
Merge pull request #120 from rubberduck-vba/next

sync with main repo
gosh how the F is that 59 commits
Merge pull request #121 from rubberduck-vba/next

sync with main repo
[rubberduck-vba/Rubberduck] retailcoder pushed commit 518bb154 to next: adding @Comintern to the about box - thanks mate!
[rubberduck-vba/Rubberduck] retailcoder pushed commit e99f44e3 to next: adding @Gareth to the about box - thanks mate!
Merge pull request #1734 from retailcoder/next

adding missing contributors to the about box
[rubberduck-vba/Rubberduck] Hosch250 pushed commit ddc01509 to next: Update the build script and the build versions
Merge pull request #1735 from Hosch250/release

Update the build script and the build versions
[rubberduck-vba/Rubberduck] build for commit ddc01509 on next: AppVeyor build failed
BUILD FAILURE!
@Hosch250 not to undo anything you've done, but I'm going to make another release build right now and update the package with these changes.
[retailcoder/Rubberduck] Hosch250 pushed commit ddc01509 to next: Update the build script and the build versions
Merge pull request #1734 from retailcoder/next

adding missing contributors to the about box
Merge pull request #1735 from Hosch250/release

Update the build script and the build versions
Merge pull request #122 from rubberduck-vba/next

sync with main repo
[rubberduck-vba/Rubberduck] build for commit 5394fdb8 on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 53540142 on next: AppVeyor build succeeded
[retailcoder/Rubberduck] retailcoder pushed commit b0329a92 to next: resized settings window, made it sizeable, and added a gridsplitter to the indenter settings
Merge pull request #122 from rubberduck-vba/next

sync with main repo
[rubberduck-vba/Rubberduck] retailcoder pushed commit b0329a92 to next: resized settings window, made it sizeable, and added a gridsplitter to the indenter settings
Merge pull request #1736 from retailcoder/next

Sizeable settings window
01:56
it won't maximize, but it will resize.
[rubberduck-vba/Rubberduck] build for commit b0329a92 on next: AppVeyor build cancelled
BUILD FAILURE!
@Duga yeah yeah
ugh, this is wrong.
the tag is [supposedly] 60-some commits behind the installer package it's for
[rubberduck-vba/Rubberduck] build for commit 249de2d5 on next: AppVeyor build succeeded
wtf
it still says it's behind 64 commits
Probably the squash
02:06
> There isn’t anything to compare.
rubberduck-vba:next is up to date with all commits from retailcoder:next. Try switching the base for your comparison.
I don't get it
well crap, I deleted the tag for no reason then
@Mat'sMug I fixed the settings.
Can I PR real quick and have this fix in too?
at this point...
[Hosch250/Rubberduck] Hosch250 pushed commit 160c1ff6 to release: Make code inspection settings save updated severities
But... After this, the settings work 100% as far as I know.
02:08
be sure to bring in my changes before you ...pr
I'd already PR'ed :(
[Hosch250/Rubberduck] Hosch250 pushed 64 commits to release (only showing some of them below)
Merge pull request #120 from rubberduck-vba/next

sync with main repo
I just updated it though.
Merge pull request #121 from rubberduck-vba/next

sync with main repo
[Hosch250/Rubberduck] retailcoder pushed commit 518bb154 to release: adding @Comintern to the about box - thanks mate!
02:08
good
[Hosch250/Rubberduck] retailcoder pushed commit e99f44e3 to release: adding @Gareth to the about box - thanks mate!
Merge pull request #1734 from retailcoder/next

adding missing contributors to the about box
Merge pull request #1735 from Hosch250/release

Update the build script and the build versions
Merge pull request #122 from rubberduck-vba/next

sync with main repo
[Hosch250/Rubberduck] retailcoder pushed commit b0329a92 to release: resized settings window, made it sizeable, and added a gridsplitter to the indenter settings
Merge pull request #1736 from retailcoder/next

Sizeable settings window
[Hosch250/Rubberduck] Hosch250 pushed commit 1159b964 to release: Merge branch 'next' into release
The first one is building.
eh, I'm still working on the announcement :)
Did you update the release yet?
meanwhile 38 watchers got 2 emails for a now-deleted beta tag lol
02:12
I had.. wtf was that
First build passed.
@Mat'sMug You deleted the entire release.
3
[rubberduck-vba/Rubberduck] build for commit 160c1ff6 on unknown branch: AppVeyor build succeeded
Shoot.
Just re-synced from VS...
If you merge that, I'll redo the release.
You'll just need to make any edits to the release notes you'd made again.
Yeah, got em in notepad
02:15
Limited time offer--almost have to go.
@Mat'sMug OK, you create the release, then I'll just add the exe.
No, the stack traces will point to your build folder, I'd like the tag to have the same author
OK. Created the tag.
updated
gosh
scrap that
the merge wasn't in
I deleted the draft
make a new one now off next - it should say 0 commits to next since tag creation
wait
wait wait wait
02:21
I accidentally published it :/
#ReleaseIsHectic
lol, isn't it
it's not listed
wait
I deleted it already.
ok
create it off master now
I think duga is down again
OK, add the text.
02:24
@Mat'sMug Uhn uh.
The user forms and class events work.
what's up?
you sure??
Remember, I hard-coded the class ones, and the user forms work.
Yeah, I spent most of yesterday working on the inspections getting them to work.
ok, remove the part about user forms
class events aren't mentioned
OK, have fun, beta!
woot!
02:27
@Zak Come and get it!
Before we throw it to the coyotes.
I'll finish the announcement and then 2.0b is as public as it gets
#Rubberduck 2.0 beta release out. Come and get it before we throw it to the coyotes.
You can close #1292 too.
02:30
ah thanks!
[rubberduck-vba/Rubberduck] build for commit d7262017 on next: AppVeyor build succeeded
@Mat'sMug Well, there is a wee bit of a problem with the settings.
It works, but after one is changed, it drops to the bottom of the group.
Didn't realize that until just now.
I'll get that fixed tomorrow and it can go out in a release on Friday/Monday with the first bug patches.
IIWY, I wouldn't bother contacting Norton &c. until we get the stable release out.
yet it costs nothing to dump the installer into Microsoft Security center
02:41
[rubberduck-vba/Rubberduck] build for commit 2a08d2fb on next: AppVeyor build succeeded
Now that we got the biggest bugs smashed, we can probably do a release every week.
That way, people who can't build and check things out can still provide regular feedback too.
yep
> Stay tuned, things are going to snowball from this point on – we’ll be releasing much more often than we have been.
When are you going to ping that Japanese guy who said he'd do the translations?
Hi, @maksil666.
Dishes time, BBL.
Put in 9 hours today and yesterday.
Have I done enough work for 237 hours?
lol
aaand it's out
2.0 Beta is here! https://rubberduckvba.wordpress.com/2016/06/08/2-0-beta-is-here
> Stack trace (mainly so I don't have to catch and dump it again):

ole32.dll!CDestObjectWrapper::GetMarshalSizeMax(const _GUID & riid, void * pv, unsigned long dwDestCtx, void * pvDestObjectWrapper, unsigned long mshlflags, unsigned long * pSize) Line 493 C++
ole32.dll!CoGetMarshalSizeMax(unsigned long * pulSize, const _GUID & riid, IUnknown * pUnk, unsigned long dwDestCtx, void * pvDestCtx, unsigned long mshlflags) Line 722 C++
ole32.dll!CRemoteUnknown::DoCallback(tagXAptCallback * p
02:58
woah
If you ever have to touch VBA install this plugin. Trust me. https://twitter.com/rubberduckvba/status/740375092945813504
> Rubberduck.Setup.2.0b.exe (5.27MB) - Downloaded 0 times.
Last updated on 2016-06-08
btw @Hosch250, we did it
> Rubberduck.Setup.2.0.1a-pre.exe (5.25MB) - Downloaded 194 times.
Last updated on 2016-04-25
inb4 200 downloads of the alpha version :)
03:55
@Mat'sMug Do you know why the debug build is about 10 times as fast as the release build?

« first day (733 days earlier)      last day (2447 days later) »