gugldiy.blogg.se - Hopper disassembler reference strings

#Hopper disassembler reference strings full
#Hopper disassembler reference strings code

Googling around turned up some initially promising results, such as a jamf blog post: “ Verifying that a Package is Signed”. pkgs are validly signed by Developer ID Installer: Digita Security, LLC. When pushing back to GitHub, we got a bunch of errors about references that couldn’t be deleted - these turned out to be references created by GitHub to manage PRs, and the fact they remain actually means that our PR history is maintained despite rewriting the whole history.Our goal was (conceptually) simple: verify that downloaded update.

#Hopper disassembler reference strings full

We could have potentially scraped together the list of commits and passed it in, but instead we decided to accept the loss of history (with the caveat that we’ve kept a copy of the full repo). We’d hoped to keep the last 6 months worth of commits intact, just in case. Each protected commit needs to be specified (defaulting to HEAD). It’s not possible to safeguard files from commits after a certain date. To work around this, we kept the blob size threshold relatively high (4MB), but also specified file types to delete from the history (images, videos, ML models, storyboards).

#Hopper disassembler reference strings code

This caused us issues as ideally we wanted to delete even quite small files but preserve certain file formats (including all code and Xcode project files). It’s not possible to safeguard specific file types - ideally we’d want to say every file above X size but not matching a certain file type. We settled on the specific configuration for the command after we discovered there were things we couldn’t do with BFG Repo Cleaner (and initially thought we could): To mitigate these risks, we backed up the repository before modifying it, so if we do need to go back then we can (with a little more effort). We might lose some old assets we’d want to recover later.However, because of the way the toolchain is built into Xcode, it often doesn’t anyway (at least not without a lot of work). Since then, the team has had to check out a fresh clone of the repository but has been able to otherwise continue working without issues. We did it when most of the team was on holiday and after merging opened PRs to reduce disruption. This removes any blobs bigger than 4MB and deletes all files with one of the file types specified. Java -jar bfg.jar - strip-blobs-bigger-than 4M - delete-files ‘*.’ Memrise-iOS.git

We used the BFG Repo Cleaner, following the instructions there. We did this by rewriting the iOS git repository’s history in order to shrink its size. It also solved our inability to push from our CI. We immediately saved about 3 minutes per CI job, even when checking out the code each time rather than caching it.

We’d been having issues pushing to the repo from our CI and a bit of googling revealed an oversized repository might be the cause.Īt the start of the year, we reduced the size of the iOS git repository from 3.2GB to 398MB.

It slowed down our CI - even though we actually cached the repo rather than fetching it, we spent over 4 mins per build just restoring and saving the cache.

This became a problem we needed to address because: Our iOS Git repository had grown over the years to reach over 3.2GB, due to a history of image and video assets, machine learning models, and third-party libraries.