Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 227 for encloses (0.2 sec)

  1. okhttp-sse/src/test/java/okhttp3/sse/internal/EventSourceRecorder.kt

        data: String,
      ) {
        get().log("[ES] onEvent", Platform.INFO, null)
        events.add(Event(id, type, data))
        drainCancelQueue(eventSource)
      }
    
      override fun onClosed(eventSource: EventSource) {
        get().log("[ES] onClosed", Platform.INFO, null)
        events.add(Closed)
        drainCancelQueue(eventSource)
      }
    
      override fun onFailure(
        eventSource: EventSource,
        t: Throwable?,
    Plain Text
    - Registered: Fri May 03 11:42:14 GMT 2024
    - Last Modified: Mon Jan 08 01:13:22 GMT 2024
    - 3.1K bytes
    - Viewed (0)
  2. LICENSES/vendor/go.opencensus.io/LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
    Plain Text
    - Registered: Fri Apr 05 09:05:09 GMT 2024
    - Last Modified: Wed Jul 01 20:12:36 GMT 2020
    - 11.2K bytes
    - Viewed (0)
  3. LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
    Plain Text
    - Registered: Fri May 03 12:43:13 GMT 2024
    - Last Modified: Wed Feb 22 18:59:39 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  4. LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
    Plain Text
    - Registered: Wed May 08 00:11:12 GMT 2024
    - Last Modified: Thu Feb 20 19:53:57 GMT 2020
    - 11.1K bytes
    - Viewed (0)
  5. licenses/cloud.google.com/go/logging/LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Feb 23 21:41:04 GMT 2021
    - 11.1K bytes
    - Viewed (0)
  6. licenses/cel.dev/expr/LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 08 17:05:56 GMT 2024
    - 11.1K bytes
    - Viewed (0)
  7. licenses/github.com/envoyproxy/protoc-gen-validate/LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sat Oct 26 02:47:39 GMT 2019
    - 11.1K bytes
    - Viewed (0)
  8. licenses/github.com/Masterminds/goutils/LICENSE.txt

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 30 20:56:04 GMT 2020
    - 11.1K bytes
    - Viewed (0)
  9. licenses/github.com/golang/groupcache/LICENSE

    APPENDIX: How to apply the Apache License to your work
    
    To apply the Apache License to your work, attach the following boilerplate
    notice, with the fields enclosed by brackets "[]" replaced with your own
    identifying information. (Don't include the brackets!) The text should be
    enclosed in the appropriate comment syntax for the file format. We also
    recommend that a file or class name and description of purpose be included on
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sat Oct 26 02:47:39 GMT 2019
    - 10K bytes
    - Viewed (0)
  10. licenses/github.com/grpc-ecosystem/go-grpc-prometheus/LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sat Oct 26 02:47:39 GMT 2019
    - 11.1K bytes
    - Viewed (0)
Back to top