- Site: https://graphite.dev
- Docs: https://docs.graphite.dev/
- Stacked PRs allow you to easily work like so:
- Work on branch
ACQ-000-part-A(which is based on master) - Work on branch
ACQ-000-part-B(which is based on part-A)
- Work on branch
| #!/bin/zsh | |
| function get_devices() { | |
| all_devices=$(command adb devices) | |
| # Drop the title | |
| all_devices=${all_devices#"List of devices attached"} | |
| # Drop any unauthorised devices (i.e. USB debugging disabled or authorisations revoked) | |
| valid_devices=$(echo $all_devices | grep -v "([[:alnum:]-]+[[:space:]]+unauthorized$)" | grep -oE "([[:alnum:]-]+[[:space:]]+device$)") |
ACQ-000-part-A (which is based on master)ACQ-000-part-B (which is based on part-A)Did you ever have android build failed issue because of dependency resolution?
… or you were curious where all these old rxjava dependencies come from?
You can pretty easy track the module causing issues via following gradle command.
gradlew :root-module:dependencyInsight \
--configuration debugRuntimeClasspath \ // or debugCompileClasspath
--dependency io.reactivex:rxjava:1.1.0 > dependencies.txt // saves result to 'dependencies.txt' file
| <?xml version="1.0" encoding="utf-8"?> | |
| <android.support.design.widget.CoordinatorLayout xmlns:android="http://schemas.android.com/apk/res/android" | |
| xmlns:app="http://schemas.android.com/apk/res-auto" | |
| xmlns:tools="http://schemas.android.com/tools" | |
| android:layout_width="match_parent" | |
| android:layout_height="match_parent" | |
| tools:context="com.vacuum.app.cinema.MainActivity"> | |
| <!--SOME CODE FOR MY AppBarLayout--> | |
| <!--SOME CODE FOR MY ToolBar--> |
| Hi All! | |
| I've recently launched a tool that wraps many of the commands here with a user interface. This desktop application is currently available for macOS. There's a roadmap outlining planned features for the near future. | |
| Feel free to request any features you'd like to see, and I'll prioritize them accordingly. | |
| One of the most important aspects of this application is that every command executed behind the scenes is displayed in a special log section. This allows you to see exactly what’s happening and learn from it. | |
| Here's the link to the repository: https://github.com/Pulimet/ADBugger | |
| App Description: | |
| ADBugger is a desktop tool designed for debugging and QA of Android devices and emulators. It simplifies testing, debugging, and performance analysis by offering device management, automated testing, log analysis, and remote control capabilities. This ensures smooth app performance across various setups. |
| package be.brol | |
| import android.os.Binder | |
| import android.os.Bundle | |
| import android.support.v4.app.BundleCompat | |
| import android.support.v4.app.Fragment | |
| /** | |
| * Eases the Fragment.newInstance ceremony by marking the fragment's args with this delegate | |
| * Just write the property in newInstance and read it like any other property after the fragment has been created |
| import rx.Observable; | |
| import rx.subjects.PublishSubject; | |
| import rx.subjects.SerializedSubject; | |
| import rx.subjects.Subject; | |
| /** | |
| * Simple pass-thru event bus with error handling and reconnect. | |
| */ | |
| public class EventBus { |
| /** | |
| * A custom DialogFragment that is positioned above given "source" component. | |
| * | |
| * @author Jonik, http://stackoverflow.com/a/20419231/56285 | |
| */ | |
| public class ConfirmBox extends DialogFragment { | |
| private View source; | |
| public ConfirmBox() { | |
| } |
| function Add-Path() { | |
| [Cmdletbinding()] | |
| param([parameter(Mandatory=$True,ValueFromPipeline=$True,Position=0)][String[]]$AddedFolder) | |
| # Get the current search path from the environment keys in the registry. | |
| $OldPath=(Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment' -Name PATH).Path | |
| # See if a new folder has been supplied. | |
| if (!$AddedFolder) { | |
| Return 'No Folder Supplied. $ENV:PATH Unchanged' | |
| } | |
| # See if the new folder exists on the file system. |