-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Checking mergeability…
Don’t worry, you can still create the pull request.
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: Alamofire/Alamofire
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: lowlevel-studios/Alamofire
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 7 commits
- 175 files changed
- 2 contributors
Commits on Nov 5, 2018
-
If string creation with a specific encoding fails, fallback to ASCII …
…encoding before returning error.
Configuration menu - View commit details
-
Copy full SHA for 74b3f53 - Browse repository at this point
Copy the full SHA 74b3f53View commit details
Commits on Jan 15, 2019
-
[Issue #2677] Fixed reachability listener issue in airplane mode
Prior to this change, the reachability listener was notified at launch if the device was not in airplane mode. When in airplane mode, the reachability flags were 0, which is what we were defaulting the previous flags to. Because of this, the notifyListener function would early out since the flags had not changed. The core issue here was that the default value of previousFlags was poorly chosen. It should instead default to a value that represents and unknown status. One way to do this would be to make previousFlags an optional. However, this change would not be backwards compatible, so it was abandoned. The best backwards compatible way to make this change was to set previousFlags to a rawValue that is not currently used. That way, we can guarantee that the originally computed flags will be different than the default previous flags. This change results in the listener being called at launch even when in airplane mode. Please refer to issue #2677 for more details.
Configuration menu - View commit details
-
Copy full SHA for 4711de7 - Browse repository at this point
Copy the full SHA 4711de7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4b14a97 - Browse repository at this point
Copy the full SHA 4b14a97View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8219072 - Browse repository at this point
Copy the full SHA 8219072View commit details -
Configuration menu - View commit details
-
Copy full SHA for 13b3e10 - Browse repository at this point
Copy the full SHA 13b3e10View commit details -
Configuration menu - View commit details
-
Copy full SHA for d82c794 - Browse repository at this point
Copy the full SHA d82c794View commit details
Commits on Mar 13, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 88182e9 - Browse repository at this point
Copy the full SHA 88182e9View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...master