Showing 2 open source projects for "error"

View related business solutions
  • Enterprise-grade ITSM, for every business Icon
    Enterprise-grade ITSM, for every business

    Give your IT, operations, and business teams the ability to deliver exceptional services—without the complexity.

    Freshservice is an intuitive, AI-powered platform that helps IT, operations, and business teams deliver exceptional service without the usual complexity. Automate repetitive tasks, resolve issues faster, and provide seamless support across the organization. From managing incidents and assets to driving smarter decisions, Freshservice makes it easy to stay efficient and scale with confidence.
    Try it Free
  • Try Google Cloud Risk-Free With $300 in Credit Icon
    Try Google Cloud Risk-Free With $300 in Credit

    No hidden charges. No surprise bills. Cancel anytime.

    Use your credit across every product. Compute, storage, AI, analytics. When it runs out, 20+ products stay free. You only pay when you choose to.
    Start Free
  • 1
    LeakCanary

    LeakCanary

    A memory leak detection library for Android

    ...It effectively detects leaks and narrows down the cause of each leak through its in-depth knowledge of the internals of the Android Framework. This helps developers avoid and dramatically reduce OutOfMemoryError (OOM) crashes. A memory leak is a programming error that can cause an OutOfMemoryError crash. It’s often caused by bugs related to the lifecycle of objects, and can occur fairly often in Android applications. LeakCanary helps to find and fix those leaks during development so you never have to experience another OOM crash.
    Downloads: 5 This Week
    Last Update:
    See Project
  • 2
    EitherNet

    EitherNet

    A pluggable sealed API result type for modeling Retrofit responses

    ...This library leverages Kotlin sealed types to better model these responses with a type-safe single point of return and no exception handling needed. ApiResult has two sealed subtypes: Success and Failure. Success is typed to T with no error type and Failure is typed to E with no success type. Failure in turn is represented by four sealed subtypes of its own: Failure.NetworkFailure, Failure.ApiFailure, Failure.HttpFailure, and Failure.UnknownFailure. This allows for simple handling of results through a consistent, non-exceptional flow via sealed when branches.
    Downloads: 2 This Week
    Last Update:
    See Project
  • Previous
  • You're on page 1
  • Next
MongoDB Logo MongoDB