profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/lucasderraugh/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Lucas Derraugh lucasderraugh New Hampshire derraugh.com Always looking for a challenge

git-up/GitUp 9841

The Git interface you've been missing all your life has finally arrived.

lucasderraugh/AppleProg-Cocoa-Tutorials 136

Cocoa tutorials from YouTube

lucasderraugh/AppleProg-ObjC-Tutorials 30

Objective-C tutorials from YouTube

lucasderraugh/AppleProg-Debugging-Tutorials 13

Apple Debugging tutorials from YouTube

lucasderraugh/AppleProg-C-Tutorials 11

C tutorials from YouTube

lucasderraugh/AppleProg-CocoaConcurrency-Tutorials 11

Cocoa Concurrency tutorials from YouTube (Swift+Obj-C)

lucasderraugh/AppleProg-CoreAnimation-Tutorials 11

Core Animation tutorials from YouTube

cs3410/logisim-evolution 7

Digital logic designer and simulator

lucasderraugh/AppleProg-BuildIt 7

AppleProgramming Built It series

lucasderraugh/LADSlider 5

A simple custom slider for Mac OS 10.10+

pull request commentgit-up/GitUp

[Feature] Image Diff Preview

Hey @lucasderraugh! Is there anything else I should be doing to help this PR along? With the UTI identification in place (c4f52a4 / bae1fc2) and the thumbnails being generated (991f889) only the separation of image loading and size calculation would be left, but as mentioned in #748 (comment) I'm not sure how to go about that 🤔

Perhaps this StackOverflow post would answer this for you: https://stackoverflow.com/questions/1551300/get-size-of-image-without-loading-in-to-memory

I wish we didn't require size calculation up front, but that's a bigger API transition that is a bit beyond scope for this PR at least. If you can test with committing 30 or so large different images and see what the performance is like that would be great. I'll gladly test it out when the size logic is in.

Stengo

comment created time in 6 days

pull request commentgit-up/GitUp

GitUp. libgit2 main branch after v1.1.1

@lucasderraugh

libgit2 v1.2.0 is released

https://github.com/libgit2/libgit2/releases/tag/v1.2.0

Do you need me to update the GitUp libgit repository branch? I'm unfortunately out of town without a laptop, but I can update the branch when I return.

lolgear

comment created time in 21 days

push eventlucasderraugh/lucasderraugh.github.io

Lucas Derraugh

commit sha 6288b8df6f06c2266dda2f37b729ed7b0a5221e8

Update current job

view details

push time in 25 days

push eventlucasderraugh/AppleProg-Standalone

Lucas Derraugh

commit sha 47c56b35c9303b3772cd6e97d2ee4c1283c2ad63

CommandMe Part 2

view details

push time in a month

push eventlucasderraugh/AppleProg-Standalone

Lucas Derraugh

commit sha 55e9d33fe820e7feee2fec331269b1437fd85122

CommandMe Part 1

view details

push time in a month

issue commentgit-up/GitUp

Failed connecting to "origin" remote: SSH could not execute request: Timed out waiting on socket

Hi, I'm having the same issue

@ruslankmlv @BabaSalley Are you both using SSH keys to login? Very odd considering we haven't made any changes in quite some time.

BabaSalley

comment created time in a month

pull request commentgit-up/GitUp

GitUp. libgit2 main branch after v1.1.1

@lolgear I can't make these "hacks" part of the workflow. I should be able to pull a branch and run the project.

lolgear

comment created time in a month

Pull request review commentgit-up/GitUp

GitUp. libgit2 main branch after v1.1.1

 				DBBEE6BF256B0B1C00F96DAF /* PBXTargetDependency */, 			); 			name = Tool;+			packageProductDependencies = (+				0A4881DB26C7B98D00289CF9 /* Libgit2Origin */,

Maybe this is a dumb question, but where does Libgit2Origin come from?

lolgear

comment created time in a month

PullRequestReviewEvent

pull request commentgit-up/libgit2

[GitUp] libgit2 main after v1.1.1

Your base branch is wrong, should be gitup_libgit2_v1.1 @lolgear

lolgear

comment created time in a month

pull request commentgit-up/GitUp

GitUp. libgit2 main branch after v1.1.1

@lolgear That's the main libgit2 repo, I think you made the PR in the wrong place.

lolgear

comment created time in a month

pull request commentlibgit2/libgit2

[Gitup] libgit2 main after v1.1.1

@lolgear I think you opened this against the main repo, when you meant the gitup repo.

lolgear

comment created time in a month

pull request commentgit-up/GitUp

GitUp. libgit2 main branch after v1.1.1

I understand. I've moved the gitup/libgit2 gitup_libgit2_v1.1 branch to the latest libgit2/libgit2 main branch. This won't be what we merge into GitUp as we'll want to wait for a stable release, but can we use the gitup/libgit2 branch that has all the latest commits as our testing for this?

As for GitUp PRs, let's keep this to a single PR with either this #757 one this one (#764).

lolgear

comment created time in a month

pull request commentgit-up/GitUp

GitUp. libgit2 main branch after v1.1.1

@lolgear I'm confused, wasn't the change merged into libgit2 on main? https://github.com/libgit2/libgit2/commit/e65229ee972c113413eeca77853213352129bd47

lolgear

comment created time in a month

pull request commentgit-up/GitUp

Draft: Support GPG signing

I don't have tons of time to review the details of PRs these days. But I'm still willing to help move the project forward.

I honestly don't care what the initial UI looks like (UI can easily be iterated on in future releases), but here is the 1 thing I do care about:

Adding in support for GPG signing CANNOT regress the performance for people not using this feature.

I'm not sure if @OdNairy is willing to keep working on these changes, I personally don't have a good understanding of gpg signing so I'm deferring to those that do to understand a good approach here. I will absolutely test out the final result before merging in anything, but that's where I stand here.

OdNairy

comment created time in a month

pull request commentgit-up/GitUp

[Libgit2] v1.1.0 update.

Can we close this out now @lolgear. I'll help you get the libgit2 changes across the finish line (and I appreciate you're endless patience dealing with me). Let's keep 1 PR in "draft" that will be the final libgit2 changes you'd like to have going.

lolgear

comment created time in a month

pull request commentgit-up/GitUp

GitUp. libgit2 main branch after v1.1.1

Can we close this out @lolgear since I've updated the gitup/libgit2 branch you requested?

lolgear

comment created time in a month

pull request commentgit-up/libgit2

[GitUp] libgit v1.1.0

@lolgear I've updated it to libgit2's main branch. I want to be clear though that we cannot point to a non-release version of libgit2 for release. So ultimately before anything would go in to a release version of GitUp I'd have to wait until 1.1.2 (or whatever the next version is).

That said, you can use this to demonstrate your changes against with that commit you listed above, but we'll have to wait before GitUp will get this change.

lolgear

comment created time in a month

push eventgit-up/libgit2

Ian Hattendorf

commit sha 5b2cd75587826148c2c2d189371fe49847f06ec9

winhttp: support optional client cert

view details

Ian Hattendorf

commit sha 1697e90f90162a41e2c98cb7354fc69b0b7ec630

winhttp: variable and switch case scoping

view details

Ian Hattendorf

commit sha 6a10b80201fe26288b60bf7dda568408e75ffb88

winhttp: clarify invalid cert case

view details

lhchavez

commit sha 896b1db493245f5ecbbb328b4d1485e44d4a1e27

Add a ThreadSanitizer build This change adds a ThreadSanitizer CI build rule. It's informative for now because there are still known places where there are races. Part of: #5592

view details

Edward Thomson

commit sha d79bb1595ce3678b925da02542bc97f789697d97

ntlm: update ntlm dependency for htonll Update ntlm to include an htonll that is not dependent on system libraries.

view details

Edward Thomson

commit sha fe12423a91015e6116773340a8936fece3251339

init: move thread init to git_global_threads_init Instead of treating win32 thread initialization specially in the win32 git_libgit2_init function, add a git_global_threads_init function.

view details

Edward Thomson

commit sha 521aa8c1c04c25a57b82e1279a4e91d8a07436aa

win32: teach the allocator to deal with crtdbg Move the MSVC C runtime debugging bits into the allocator's global init function.

view details

Edward Thomson

commit sha 6554b40e42df831d7fc9c623d34b2738227dd8a2

settings: localize global data Move the settings global data teardown into its own separate function, instead of intermingled with the global state.

view details

Edward Thomson

commit sha 8aa69f887afaced1389d1ae965d5f313b10da66b

mwindow: localize mutex Move the mwindow mutex into the mwindow code itself, initializing it in the mwindow global initialization function instead of in the global initializer.

view details

Edward Thomson

commit sha bc3919abc716088cf7c33bc08d48ee2bc434c398

global init: check error message buffer allocation Ensure that we can allocate the error message buffer. In keeping with our typical policiess, we allow (small) memory leaks in the case where we're out of memory.

view details

Edward Thomson

commit sha 4853d94ca47a6f1ecaa7c24b9034ededcb7e5bff

global: separate global state from thread-local state Our "global initialization" has accumulated some debris over the years. It was previously responsible for both running the various global initializers (that set up various subsystems) _and_ setting up the "global state", which is actually the thread-local state for things like error reporting. Separate the thread local state out into "threadstate". Use the normal subsystem initialization functions that we already have to set it up. This makes both the global initialization system and the threadstate system simpler to reason about.

view details

Edward Thomson

commit sha c40d2dc5ff2058bf04d816423507dec42e7dd0cc

thread: restore the git_thread_exit tests We were never properly testing git_thread_exit. Do so.

view details

Edward Thomson

commit sha 8970acb750ecf4b86883d9ea1a8cb280517e6c86

thread: don't use the global tlsdata for thread exit We want to store a pointer to emulate `pthread_exit` on Windows. Do this within the threading infrastructure so that it could potentially be re-used outside of the context of libgit2 itself.

view details

Edward Thomson

commit sha e316b0d3d64eb8f65f4109c1565d929b29e1d33a

runtime: move init/shutdown into the "runtime" Provide a mechanism for system components to register for initialization and shutdown of the libgit2 runtime.

view details

Edward Thomson

commit sha 1ec4702a51b1074fb7109a841dc95a192feb8525

Rename global.c to libgit2.c Now that we've identified that our global settings really aren't global at all, and refactored the library to match that, change global.c to libgit2.c, which is especially nice since the prefix of the functions matches the filename.

view details

Edward Thomson

commit sha 634c285a0eb016a2d144b35298dabc350d2e7576

Move libgit2 settings into libgit2.c

view details

lhchavez

commit sha 4a0dceebe4038b2b14460956105100d159c2e628

Make the Windows leak detection more robust This change: * Increases MY_ROW_LIMIT to 2M, since it has been failing in #5595's tests since it's _super_ close to the limit. * Calls `git_repository_free()` on a `git_repository` that was being leaked only in Windows. * Marks the global `git_repository` on `tests/repo/init.c` as `NULL` after being freed to make any accidental access more noisy. * Uses `cl_assert_equal_i()` in `test_trace_windows_stacktrace__leaks` to make the test failures more actionable. * Renames the globals in `tests/repo/init.c` so that they don't start with an underscore.

view details

lhchavez

commit sha fa3daa8259df6c09a7e075b0b959eabc791f92f9

Define `git___load` when building with `-DTHREADSAFE=OFF` This should allow folks that build in non-thread-safe environments to still be able to build the library. Fixes: #5663

view details

Edward Thomson

commit sha a027efbb8dcd01da7eaffc42f9c653a3887ac54c

Merge pull request #5658 from libgit2/ethomson/ntlm_htonll ntlm: update ntlm dependency for htonll

view details

Edward Thomson

commit sha c964f73d3f5a6529bba87c0ad1e484e2a5db87ee

Merge pull request #5664 from lhchavez/define-non-threadsafe-git-load Define `git___load` when building with `-DTHREADSAFE=OFF`

view details

push time in a month

pull request commentgit-up/libgit2

[GitUp] libgit v1.1.0

@lolgear By "update main branch" you just mean merge into gitup_libgit_v1.1 branch?

lolgear

comment created time in a month

pull request commentgit-up/libgit2

[GitUp] libgit v1.1.0

I don't see how a Package.swift is going to help us. We aren't using Swift in the main project and won't be for the foreseeable future. We should use the same approach as the Objective-git project: https://github.com/libgit2/objective-git.

Whatever we'd do I don't want to introduce Swift Package Manager or CocoaPods. We should stick with the submodule approach we're using today. @lolgear

lolgear

comment created time in a month

issue closedgit-up/GitUp

Using 2FA on Github

I have 2FA on Github. When I try to do a push from Gitup to my repository on Github, I get asked for username/password. I enter my username and the token from Authy - The request gets rejected. I enter my username and password - the request gets rejected.

I have to revert to Github desktop in order to do the push.

Is there something I'm missing on doing the authentication from Gitup?

closed time in a month

sjemmett

issue commentgit-up/GitUp

Using 2FA on Github

Going to close this out as we have answers to how this works. SSH or PAT as password should work in 2FA approaches.

sjemmett

comment created time in a month

delete branch lucasderraugh/AppleProg-Standalone

delete branch : main

delete time in 2 months

create barnchlucasderraugh/AppleProg-Standalone

branch : master

created branch time in 2 months

push eventlucasderraugh/AppleProg-Standalone

push time in 2 months

create barnchlucasderraugh/AppleProg-Standalone

branch : main

created branch time in 2 months

created repositorylucasderraugh/AppleProg-Standalone

Standalone tutorials from AppleProgramming YouTube channel

created time in 2 months

startedessentialdevelopercom/essential-feed-case-study

started time in 2 months

issue commentgit-up/GitUp

How to install Kaleidoscope as a merge tool? [Question]

Closing this out as it sounds like there are solutions.

NikKovIos

comment created time in 2 months