« first day (8 days earlier)      last day (205 days later) » 
00:00 - 15:0015:00 - 00:00

00:02
RELOAD!
[Cardshifter/Cardshifter] 12 commits. 10 opened issues. 2 issue comments.
[Cardshifter/cardshifter.github.io] 2 opened issues. 1 issue comment.
[retailcoder/Rubberduck] 6 commits. 2 opened issues. 1 closed issue. 12 issue comments.
[ShearOfDoom/Cactus] 31 commits. 26 opened issues. 16 closed issues. 39 issue comments.
[Vannevelj/VSDiagnostics] 1 opened issue.
[Zomis/Duga] 5 issue comments.
@EthanBierlein No
doesn't conform to PEP 8
Or just get a good text editor and it'll handle it all for your
http://atom.io
Oh, okay then. Can you change that to using spaces rather than tabs.
I'm just going to say that it should be implied by the style guide
We can watch any PRs for the wrong kind (plus, Python will not accept mixed in a single file, so they should at least be testing their code before committing)
But seriously, get a great text editor. Are you using Notepad still?
(I would cry if you did :P)
@Ethan is it okay that I am creating so many issues? If you don't want one, you should let me know. I just want to make the project better
And if someone doesn't know what to do, they can look at an open issue
Most of the stuff I'm doing now is bugfixes and stability improvements (I doubt that you would object to those :P), but let me know if you don't want a feature or something.
00:17
[ShearOfDoom/Cactus] ShearOfDoom pushed commit a324e943 to master: Added index reference validation.
[ShearOfDoom/Cactus] ShearOfDoom pushed commit f951d697 to master: Added index reference checking.
@AnnonomusPenguin Hmm. Let's keep the maximum open issues to 15. Just to keep in manageable.
@EthanBierlein why would we do that?
You have a good idea that we should add, you do a feature request
Hmm. Let me rephrase that. We should only have 15 open issues that are feature requests, or idea discussions. Bugs can be unlimited.
I'm going to define bug as anything that might lead to instability problems
Like the validator isn't a bug, but not having it might lead to instability problems
00:20
@Ethan I was more talking about the content. What do you think of that?
We shouldn't have too many open "suggestions" or "content". It becomes to hard to manage when we're trying to implement, like, 40 ideas at once.
Figure of speech, but yeah.
[ShearOfDoom/Cactus] ShearOfDoom pushed commit 32c9ac51 to master: Fixed issue with modified files.
00:58
@QPaysTaxes no hard limit though
It might be small changes
@Ethan don't work on issues that have already been assigned.
Which issue in particualr?
I already had local commits that I was going to push for that issue
Oh, sorry. At least it was a small one. :/
@EthanBierlein yeah, just make sure not to do it for a big issue
:D
K.
What would define "big issue" though? > 25 code lines?
01:03
Don't do it at all, unless it's a critical bug
Even then, a person shouldn't be assigned a critical bug if they can't fix it
So: Never
An asignee is basically saying "I'll do that." Don't waste other people's time
Soundses likeses a plans. Gollums and preciouses agrees.
01:09
@Ethan did you, by any chance, use the command git push --force [bad]?
@AnnonomusPenguin Erm, no... Why?
> It, by default, goes to the location called start. They should be able to change that to the great hall or whatever.
@EthanBierlein something's screwed up in the history and I can't tell why
A commit of yours removed some of my content, and the next one added it
Hmm. Can you show me the relevant history?
Was there a conflict?
01:12
There was some merge issue when I ran git pull, and the test.py file had a bunch of the wierd characters in it that github inserted. So I edited those characters out.
Did it accidentally destroy anything?
@EthanBierlein it somehow came back
Hmm...
Can you screenshot it?
What, the, heck....
01:16
> Yes, the website. Docs are often done in GitHub pages because it can render Markdown. It's looks nicer vs. doesn't require a pull request to edit. Personally, I like pages better, but I don't know what we want.

Wikis are older
That's really odd. I never touched those parts.
It has to be related to the conflict
But I'm worried that we lost more code there
So, do you remember the exact order that the conflict happened? Like push, then conflict, pull, then edit... etc.?
I think it went push, push fail, pull, edit, push.
Let me figure this out
So a total of two pushes?
Or three?
Those are events in the order they happened. I pushed twice.
Oh, and btw, I just ran git pull, (no updates needed to local repo), and the code still appears to work.
01:21
@EthanBierlein why are there three commits?
And did you stage every single file?
What do you mean "stage"?
git add "filename"
I staged all the ones that were important parts of the project that were not part of a commit, and had changed.
Wait.
How did I do a pull request from a branch to the same one?
Oh god. I, honestly don't know what's happening here. The code still seems to be the same, and works fine. (As far as I can tell)
Ummm
Ring ring, GitHub support
Shh, it looks cool, shh...
What the
I don't even know anymore
anymoe
lol
01:31
This seems like a hash collision but that shouldn't happen
> However, you should be aware of how ridiculously unlikely this scenario is. The SHA-1 digest is 20 bytes or 160 bits. The number of randomly hashed objects needed to ensure a 50% probability of a single collision is about 2^80 (the formula for determining collision probability is p = (n(n-1)/2) * (1/2^160)). 2^80 is 1.2 x 10^24 or 1 million billion billion. That’s 1,200 times the number of grains of sand on the earth.
> Here’s an example to give you an idea of what it would take to get a SHA-1 collision. If all 6.5 billion humans on Earth were programming, and every second, each one was producing code that was the equivalent of the entire Linux kernel history (1 million Git objects) and pushing it into one enormous Git repository, it would take 5 years until that repository contained enough objects to have a 50% probability of a single SHA-1 object collision.
> A higher probability exists that every member of your programming team will be attacked and killed by wolves in unrelated incidents on the same night.
2
Hash collision? OH GOD THE RAPTURE IS COMING
I don't think that's it, but it'd be cool
20
Q: Github Repo Corruption - Sha1 Collision

saalonYesterday one of my team's checkins corrupted our github repo. On github, they were showing this error: $ git fsck error: sha1 mismatch 87859f196ec9266badac7b2b03e3397e398cdb18 error: 87859f196ec9266badac7b2b03e3397e398cdb18: object corrupt or missing missing blob 87859f196ec9266badac7b2b03e33...

That's what happens ^^^ :P
@Ethan I'm just going to say let this one slip since this seems like a bug. A very weird one, for sure.
Did you use rebase? A special flag? Anything?
Nope. Just git push
rebase... hmm
No.
Just be careful out there. It's a dangerous world out there with Git :P
That's why I prefer Github for windows over the command line.
WE JUST HIT 20 UNIQUE VISITORS
A birthday attack is a type of cryptographic attack that exploits the mathematics behind the birthday problem in probability theory. This attack can be used to abuse communication between two or more parties. The attack depends on the higher likelihood of collisions found between random attack attempts and a fixed degree of permutations (pigeonholes). == Understanding the problem == As an example, consider the scenario in which a teacher with a class of 30 students asks for everybody's birthday, to determine whether any two students have the same birthday (corresponding to a hash collision as...
Lol ^^
01:39
@EthanBierlein call the news agencies!!!
We shall report this to the reporters 2nd Monitor.
> Hello all. We'd love support for Cactus. We just hit 20 unique visitors, and we're working really hard on it. We have a website, subreddit, and a chat room. Thank you for the support!
That's what I posted in TSM ^^
Hey, I've made the subreddit un-private, so that users can post in it now.
COMMUNITY PROMOTION
@EthanBierlein wut?
01:51
Hello @nhgrif!
Hello nhgrif (late, sorry) q:
> I can migrate everything if we want docs. Leave the technical stuff up to me; just tell me what you want.
> Okay, so the current pages on our repo's wiki, let's migrate them to the website, and then any other wiki pages I add, we can just migrate.
> Don't add any more there. I'll work on documentation now.

Also, can we get a styleguide for Markdown? I have one that I like and the output always looks good. I'll put it online for you to peek at.
> Alright, you can use your md style.
@AnnonomusPenguin If your MD style is better than mine, then please use it.
@EthanBierlein that's subjective, but I like it better
Less cluttered and better flowing (IMHO, at least)
If it's less cluttered and better flowing, than it's better than mine.
01:56
haha
> I want to add other examples
> Sounds good to me.
[ShearOfDoom/Cactus] ShearOfDoom pushed commit b7c83932 to gh-pages: Added entire README.md to site front page.
> I'm going to assign myself to this. That sound good?
> Sure. Can you please run the PR past me to make sure that all of the binding code isn't broken by this? It's easier just for me to check than for me to explain
> I don't have a commit yet, but I'll put up the PR as soon as I have it.
[ShearOfDoom/Cactus] Annonomus-Penguin pushed commit fb8f0b94 to gh-pages: Delete LICENSE.txt
Ahm, @AnnonomusPenguin, try converting the MD on the front page to HTML.
@EthanBierlein it should since it's Jerkyll
It's, not, Jerkyll. It's just normal GH-pages.
Yes it is
For sure
02:49
I used some Jerkyll there
Like includes that were Jerkyll
{{% include header.html %}}
Are you sure, because it's still not rendering.
I know, I think it's a HTML and MD issue
[ShearOfDoom/Cactus] Annonomus-Penguin pushed commit a910cddb to gh-pages: Let's try this?
[ShearOfDoom/Cactus] Annonomus-Penguin pushed commit 433a1176 to gh-pages: Fixed conflict
Better. One more thing
Is it still not supposed to be rendering?
03:00
@EthanBierlein there were a few other issues
[ShearOfDoom/Cactus] Annonomus-Penguin pushed commit 863fb3f1 to gh-pages: Test if this will render the markdown
Nope. Still not working.
Ack. I think I figured it out.
It might take 20 minutes to do; feel free to revert to old commit if you want
Nah. I got time you can work your magic.
Good thing that I learned not to test in production on a small scale here :P
03:15
lol
YAY. Except links don't render.
What?
If it's the first link I'd laugh
@EthanBierlein Look at the URL
None of them render.
03:24
Refresh? All of them work for me
Dang it, this theme is too small to be readable in docs
Hmm. May just be an issue with this cough old cough laptop.
Could we have a different design for docs?
What do you think about the size of the page?
Page should be slightly wider. What theme are you thinking?
@EthanBierlein anything that is wider? :P
I'm just looking at this and the header is mostly image-generated so we can't (easily) resize it
Wait... let me try something
Okay, the links are an issue with my laptop. They render fine on my phone.
03:35
@Ethan what are you thinking as far as the theme? I can't seem to fix it
Lets keep the current theme. I like the way it looks.
WE JUST HIT 1,000 VIEWS
I'm not sure how to handle this. Docs should be separate but should look similar
We could have the docs linked on the main page.
But as a separate page on the site.
03:43
I'm not talking about that. This site design doesn't seem like docs though.
I don't know. I think it's the theme
Everything seems cramped
I like the colors but not the layout
Hmm. Okay. We can use a new theme if you want.
@EthanBierlein what do you think?
What do you like about the current theme yourself?
I don't really care. Whatever looks good.
And about the current theme, not much, it just looks, game-ish.
03:49
Hmm...
There's a command line-ish one that might seem fitting
Not great. Let me show you one other thing
Hmm. okay
I would have to tweak the colors, but I edited the gradient
We could make it look like a dessert
Change the heading text to be console-ish, but everything else would look smooth
I like it. CHANGE ALL THE THEMES
03:55
@EthanBierlein You do?
#score!
It's also responsive
This is a level 1 meme-free zone. Please do not use memes.
XD
This is a level-10 meme contamination emergency, please redirect all content to safe file on secure server.
alarms blaring
PROTECT YOUR CHILDREN
RUUUUUNNNNN
HIDE UR WIFE, HIDE UR KIDS, HIDE UR FAMILY
04:00
alashaslfjds;afjasdf;sad;fjk;sdf
Why are licenses so annoying?
Because it's legal crap. That
's why
All I wanted was a responsive website
None of this CCSA 4.0 intl.
Can we just delete the gh-pages branch and start over?
You'll have to do that
@EthanBierlein It's the Cayman theme. Tell me when you're done
04:06
[ShearOfDoom/Cactus] ShearOfDoom deleted branch gh-pages
Done
Also, for the website, if you want to re-write the first part of the readme, you can. I feel like it's kinda wierdly written.
@EthanBierlein the README and the main page will be different
The readme will be more code focused and the website will be more intro
alrighty
04:07
It's not up
There isn't even a gh-pages branch
@EthanBierlein can you create it?
yup
should it use jerkyll
?
@EthanBierlein just create a normal site. I'll do the rest
[ShearOfDoom/Cactus] ShearOfDoom pushed commit 6f0fa51e to gh-pages: Create gh-pages branch via GitHub
[ShearOfDoom/Cactus] ShearOfDoom pushed commit 9ff9756c to gh-pages: Centered logo.
I created the branch, btw
04:30
Aarg. I'm checking out for the night. Me and my gf are going to go watch a movie. I'll be on-off in here for another hour or so.
> Maybe just set the location at index 0 is the start?
Ok
I'm going to push here soon :)
K. I may just stay in here. (She wants to watch a horror movie)
[ShearOfDoom/Cactus] Annonomus-Penguin pushed commit 0f0b6d12 to gh-pages: Style and Layout Design
@EthanBierlein lol stay
Does the movie involve memes?
And... errr.... nope!
04:33
No. She wants to watch insidious. Brrr.
Lol
Look at the page now
How did that destroy the theme?
I think the paths got messed up
But no 404s
Ahm. I'm assuming the missing theme is not intentional.
The entire head element disappeared ???
I don't think this is normal
But it's Jerkyll, so never know
Oh, forgot to set theme
Right.
[ShearOfDoom/Cactus] Annonomus-Penguin pushed commit f423a6f1 to gh-pages: Helps if you set the theme right
Heh. Lol
04:36
There we go!
Hmm. Maybe my iPhone doesn't render it correctly...
@EthanBierlein screenshot?
There we fo
*go
Hey, can you put <center> around the logo at the top.
@EthanBierlein Why?
I'm going to move the logo into the header
04:39
So it displays it right by "Cactus" in the orange area
K
Oh god. She's starting the horror movie....
05:05
[ShearOfDoom/Cactus] Annonomus-Penguin pushed commit e0a56aab to gh-pages: Moved logo; added framework for docs and tutorials
[ShearOfDoom/Cactus] Annonomus-Penguin pushed commit 9d4f35bb to gh-pages: Added page stubs for docs and tutorials
@EthanBierlein New changes! Now I have the site divided into different areas. Will work on in AM.
Night everyone! yawn
05:29
We need a change log
Hmm. We just have an initial version. When we release the next one we'll have a changelog.
that'll help us keep the docs up to date
And we should have the change log edited with each commit so we don't forget anything (unless we want to go back later)
Okay. We can create a changelog.txt file. Anyways, I'm going to bed.
 
8 hours later…
13:54
Hello!
14:46
Morning
14:57
The site's looking really nice! :)
00:00 - 15:0015:00 - 00:00

« first day (8 days earlier)      last day (205 days later) »