Keploy - The Keploy server for golang

api-server

docker biuildx build --platform linux/amd64,linux/arm64 -t slayerjain/keploy-api-server:$(date +%s) -t slayerjain/keploy-api-server --push .
Comments
  • [docs]: Add missing file name and package in the Readme

    [docs]: Add missing file name and package in the Readme

    What do you want to add to the docs? (please state reasons if any)

    The section Integration with native Go test framework is missing 2 things:

    1. It is not mentioned in which file we have to add the given code.
    2. No package is added at the beginning which will give an error.

    Where is this stated?

    Under the Integration with native Go test framework section in README.md* file

  • docs: use dynamic contributors list

    docs: use dynamic contributors list

    Related Issue

    See https://github.com/keploy/keploy/pull/101#issuecomment-1086548839.

    Describe the changes you've made

    Used contrib.rocks to dynamically generate the list of contributors.

    Type of change

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    Describe if there is any unusual behaviour of your code(Write NA if there isn't)

    NA

    Checklist:

    • [ ] My code follows the style guidelines of this project.
    • [ ] I have performed a self-review of my own code.
    • [ ] I have commented my code, particularly in hard-to-understand areas.
    • [ ] I have made corresponding changes to the documentation.
    • [ ] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] New and existing unit tests pass locally with my changes.

    Screenshots (if any)

    | Original | Updated | |:-----------------------:|:--------------------------:| | original screenshot | updated screenshot |

  • Documentation redirect should open new tab

    Documentation redirect should open new tab

  • [feature]: enable version command for the keploy binary

    [feature]: enable version command for the keploy binary

    Is there an existing feature request for this?

    • [X] I have searched the existing issues

    Summary

    Keploy needs to provide a version flag (eg: keploy version which outputs the binary version. The version needs to be consistent with the git tag which was used to build that version. This might require passing git tag (which is the version) as a build argument during the build process and outputting that via the version subcommand within keploy.

    Why should this be worked on?

    This would help users check for their version of keploy, which is particularly helpful during debugging.

  • feat: mock data compress-decompress

    feat: mock data compress-decompress

    Related Issue

    • Closes: #184 Compressed the data on Encode wiriting mocks into yaml and decompressed on Decode

    Type of change

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    Checklist:

    • [ ] My code follows the style guidelines of this project.
    • [ ] I have performed a self-review of my own code.
    • [ ] I have commented my code, particularly in hard-to-understand areas.
    • [ ] I have made corresponding changes to the documentation.
    • [ ] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] New and existing unit tests pass locally with my changes.

    Screenshots (if any)

    Screenshot from 2022-10-17 11-33-45

  • keploy command

    keploy command

    Closes: #204

    Describe the changes you've made

    keploy is now available as a binary. It also now supports overriding the default keploy port.

    Type of change

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [x] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    Test Run Logs

    keploy on cmd-keploy [!] via 🐹 v1.18.4 on 🐳 v20.10.17 at ☸️  microk8s  took 6s
    ➜ git diff
    diff --git a/Dockerfile b/Dockerfile
    index a3a805f..75b5e6f 100644
    --- a/Dockerfile
    +++ b/Dockerfile
    @@ -44,5 +44,5 @@ COPY --from=alpine /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/
     COPY --from=go-builder /app/keploy /app/
     COPY --from=go-builder /go/bin/dlv /
    
    -EXPOSE 6789
    -ENTRYPOINT ["/app/keploy"]
    \ No newline at end of file
    +EXPOSE 8000
    +ENTRYPOINT ["/app/keploy", "-p", "8000"]
    diff --git a/docker-compose-dev.yaml b/docker-compose-dev.yaml
    index 4ff8cf0..bf7bba3 100644
    --- a/docker-compose-dev.yaml
    +++ b/docker-compose-dev.yaml
    @@ -3,7 +3,7 @@ services:
       keploy:
         build: .
         ports:
    -      - "6789:6789"
    +      - "6789:8000"
         environment:
           KEPLOY_MODE: "off"
           KEPLOY_MONGO_URI: "mongodb://mongo:27017"
    @@ -13,4 +13,4 @@ services:
       mongo:
         image: "mongo"
         ports:
    -      - "27017:27017"
    \ No newline at end of file
    +      - "27017:27017"
    
    
    keploy on cmd-keploy [!] via 🐹 v1.18.4 on 🐳 v20.10.17 at ☸️  microk8s
    ➜ docker-compose  -f docker-compose-dev.yaml up -d --build
    [+] Building 14.7s (27/27) FINISHED
     => [internal] load build definition from Dockerfile                                            0.0s
     => => transferring dockerfile: 32B                                                             0.0s
     => [internal] load .dockerignore                                                               0.0s
     => => transferring context: 2B                                                                 0.0s
     => [internal] load metadata for docker.io/library/golang:alpine                                1.1s
     => [internal] load metadata for docker.io/library/node:14-bullseye                             1.0s
     => [internal] load metadata for docker.io/library/alpine:latest                                0.0s
     => [internal] load build context                                                               0.0s
     => => transferring context: 23.31kB                                                            0.0s
     => [go-builder  1/10] FROM docker.io/library/golang:alpine@sha256:f3e683657ddf73726b5717c2ff8  0.0s
     => [ui-builder 1/6] FROM docker.io/library/node:14-bullseye@sha256:43d260e563bf51cfc813311e80  0.0s
     => FROM docker.io/library/alpine:latest                                                        0.0s
     => CACHED [ui-builder 2/6] RUN npm install -g gatsby-cli                                       0.0s
     => CACHED [ui-builder 3/6] RUN git clone https://github.com/keploy/ui                          0.0s
     => CACHED [ui-builder 4/6] WORKDIR /ui                                                         0.0s
     => CACHED [ui-builder 5/6] RUN npm install                                                     0.0s
     => CACHED [ui-builder 6/6] RUN gatsby build                                                    0.0s
     => CACHED [go-builder  2/10] RUN apk add -U --no-cache ca-certificates && apk add build-base   0.0s
     => CACHED [go-builder  3/10] RUN go install github.com/go-delve/delve/cmd/dlv@latest           0.0s
     => CACHED [go-builder  4/10] WORKDIR /app                                                      0.0s
     => CACHED [go-builder  5/10] COPY go.mod .                                                     0.0s
     => CACHED [go-builder  6/10] COPY go.sum .                                                     0.0s
     => CACHED [go-builder  7/10] RUN go mod download                                               0.0s
     => [go-builder  8/10] COPY . .                                                                 0.1s
     => [go-builder  9/10] COPY --from=ui-builder /ui/public /app/web/public                        0.1s
     => [go-builder 10/10] RUN CGO_ENABLED=0 GOOS=linux go build -o keploy cmd/keploy-cli/main.go  13.2s
     => CACHED [stage-2 2/4] COPY --from=alpine /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/  0.0s
     => CACHED [stage-2 3/4] COPY --from=go-builder /app/keploy /app/                               0.0s
     => CACHED [stage-2 4/4] COPY --from=go-builder /go/bin/dlv /                                   0.0s
     => exporting to image                                                                          0.0s
     => => exporting layers                                                                         0.0s
     => => writing image sha256:9d3260a64331b3b968de616b3972edb2af3e8e66c11d89d4b28a6b2b583e9c6c    0.0s
     => => naming to docker.io/library/keploy-keploy                                                0.0s
    
    Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
    [+] Running 3/3
     ⠿ Network keploy_default     Created                                                           0.0s
     ⠿ Container keploy-mongo-1   Started                                                           0.4s
     ⠿ Container keploy-keploy-1  Started                                                           0.7s
    
    
    keploy on cmd-keploy [!] via 🐹 v1.18.4 on 🐳 v20.10.17 at ☸️  microk8s  took 16s
    ➜ docker-compose logs keploy
    keploy-keploy-1  | 2022/10/08 13:57:59 👍 connect to http://localhost:8000 for GraphQL playground
    keploy-keploy-1  |
    
  • [docs]: Update keploy logo in the dashboard

    [docs]: Update keploy logo in the dashboard

    What do you want to add to the docs? (please state reasons if any)

    The Keploy logo is updated now, but the Keploy console still has old logo.
    Screenshot 2022-08-10 at 12 57 18 AM

    Where is this stated?

    https://avatars.githubusercontent.com/u/92252339?s=200&v=4

  • chore: rename the container in docker-compose

    chore: rename the container in docker-compose

    Related Issue

    Closes: #102

    Describe the changes you've made

    Renamed the web_1 container to keploy

    Type of change

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [x] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    Please let us know if any test cases are added

    NA

    Describe if there is any unusual behaviour of your code(Write NA if there isn't)

    NA

    Checklist:

    • [x] My code follows the style guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [ ] I have commented my code, particularly in hard-to-understand areas.
    • [ ] I have made corresponding changes to the documentation.
    • [x] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [x] New and existing unit tests pass locally with my changes.

    Screenshots (if any)

    Original | Updated :--------------------: |:--------------------: original screenshot | updated screenshot |

  • [docs]: Add details for 3 different Keploy SDK Modes

    [docs]: Add details for 3 different Keploy SDK Modes

    Is there an existing feature request for this?

    • [X] I have searched the existing issues

    Summary

    Add 3 different modes of Keploy SDK in the readme.

    Record: Sets to record mode. Test: Sets to test mode. Off: Turns off all the functionality provided by the API

    Note: KEPLOY_MODE value is case sensitive.

    Take inspiration from https://github.com/keploy/go-sdk#configure

    Why should this be worked on?

    Users will have better undedstanding about different modes and what exactly needs to be set in the env variable since it's currently case sensitive

  • added instructions after dependency wrapping

    added instructions after dependency wrapping

    Related Issue

    • Info about Issue or bug

    Closes: #[issue number that will be closed through this PR]

    Describe the changes you've made

    A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
    added the instructions after dependency wrapping .

    Type of change Documentation

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [x] This change requires a documentation update

    Please let us know if any test cases are added

    Please describe the tests(if any). Provide instructions how its affecting the coverage.

    Describe if there is any unusual behaviour of your code(Write NA if there isn't)

    A clear and concise description of it.

    Checklist:

    • [x] My code follows the style guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [x] I have commented my code, particularly in hard-to-understand areas.
    • [x] I have made corresponding changes to the documentation.
    • [x] My changes generate no new warnings.
    • [x] I have added tests that prove my fix is effective or that my feature works.
    • [x] New and existing unit tests pass locally with my changes.

    Screenshots (if any)

    | Original | Updated | |:-----------------------:|:--------------------------:| | original screenshot | updated screenshot |

  • change log level to error instead of fatal

    change log level to error instead of fatal

    Related Issue

    (https://github.com/keploy/keploy/issues/150) Closes: https://github.com/keploy/keploy/issues/150

    Describe the changes you've made

    Changed log level to Error from Fatal so that keploy doesn't exit in case of no internet

    Type of change

    • [x ] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    Describe if there is any unusual behaviour of your code(Write NA if there isn't)

    NA

  • changed the name of the mock files

    changed the name of the mock files

    Closes: #247

    Describe the changes you've made

    Updated the names of the mock files.

    Type of change

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    Please let us know if any test cases are added

    Please describe the tests(if any). Provide instructions how its affecting the coverage.

    Describe if there is any unusual behaviour of your code(Write NA if there isn't)

    A clear and concise description of it.

    Checklist:

    • [ ] My code follows the style guidelines of this project.
    • [ ] I have performed a self-review of my own code.
    • [ ] I have commented my code, particularly in hard-to-understand areas.
    • [ ] I have made corresponding changes to the documentation.
    • [ ] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.
    • [ ] New and existing unit tests pass locally with my changes.

    Screenshots (if any)

    | Original | Updated | |:-----------------------:|:--------------------------:| | original screenshot | updated screenshot |

  • The server version printed during runtime should reflect the actual server version

    The server version printed during runtime should reflect the actual server version

    https://github.com/keploy/keploy/blob/2b1d6a0536d73370f9c59b983f5fd9a94861b95f/cmd/server/main.go#L9

    This is currently hardcoded as v0.1.0-dev

    ~ server-v0.7.8 run
    
           ▓██▓▄
        ▓▓▓▓██▓█▓▄
         ████████▓▒
              ▀▓▓███▄      ▄▄   ▄               ▌
             ▄▌▌▓▓████▄    ██ ▓█▀  ▄▌▀▄  ▓▓▌▄   ▓█  ▄▌▓▓▌▄ ▌▌   ▓
           ▓█████████▌▓▓   ██▓█▄  ▓█▄▓▓ ▐█▌  ██ ▓█  █▌  ██  █▌ █▓
          ▓▓▓▓▀▀▀▀▓▓▓▓▓▓▌  ██  █▓  ▓▌▄▄ ▐█▓▄▓█▀ █▓█ ▀█▄▄█▀   █▓█
           ▓▌                           ▐█▌                   █▌
            ▓
    
    keploy 0.1.0-dev
    
    .2023-01-02T17:31:24.480+0100	INFO	server/server.go:215	keploy started at port 6789
    

    This should ideally print v0.7.8 when running with v0.7.8.

  • Windows Installation ReadMe Update

    Windows Installation ReadMe Update

    Related Issue

    ReadMe Update - Added the Steps for Keploy Installation on Windows.

    Type of change

    • [x] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Code style update (formatting, local variables)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [x] This change requires a documentation update

    Please describe the tests(if any). Provide instructions how its affecting the coverage.

    Describe if there is any unusual behaviour of your code(Write NA if there isn't)

    A clear and concise description of it.

    Checklist:

    • [x] My code follows the style guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [x] I have commented my code, particularly in hard-to-understand areas.
    • [x] I have made corresponding changes to the documentation.
    • [x] My changes generate no new warnings.
    • [x] I have added tests that prove my fix is effective or that my feature works.
    • [x] New and existing unit tests pass locally with my changes.
  • build(deps): bump github.com/go-chi/render from 1.0.1 to 1.0.2

    build(deps): bump github.com/go-chi/render from 1.0.1 to 1.0.2

    Bumps github.com/go-chi/render from 1.0.1 to 1.0.2.

    Commits
    • 996350f Merge pull request #4 from syntaqx/master
    • d098851 adding nolint errcheck until a config can be added
    • 56c7eb9 removing minor.patch specificity of actions/cache
    • 6a082d9 swapping travis for github actions
    • 126d5e7 Merge branch 'master' of github.com:go-chi/render
    • 99dff9a modernizing DecodeForm changeset
    • af1759a removing boilerplate toml
    • bf4aca9 ignoring vendor folder from vcs
    • a54e4ac removing vendor folder
    • 9fd658c really fixing merge conflicts
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • build(deps): bump github.com/99designs/gqlgen from 0.15.1 to 0.17.22

    build(deps): bump github.com/99designs/gqlgen from 0.15.1 to 0.17.22

    Bumps github.com/99designs/gqlgen from 0.15.1 to 0.17.22.

    Release notes

    Sourced from github.com/99designs/gqlgen's releases.

    v0.17.22

    What's Changed

    New Contributors

    Full Changelog: https://github.com/99designs/gqlgen/compare/v0.17.21...v0.17.22

    v0.17.21

    What's Changed

    New Contributors

    Full Changelog: https://github.com/99designs/gqlgen/compare/v0.17.20...v0.17.21

    v0.17.20

    What's Changed

    New Contributors

    ... (truncated)

    Changelog

    Sourced from github.com/99designs/gqlgen's changelog.

    v0.17.22 - 2022-12-08

    • d6579466 release v0.17.22

    • 9a292299 graphql.Error is not deprecated anymore (#2455)

    • Remove DO NOT EDIT

    Sometimes vscode warn about this while editing resolvers code. Finally the resolver's code is editable and generated at the same time.

    • Ability to return multiple errors from resolver.

    • Multiple errors return example

    • Fix missing import

    • reformat

    • gofmt

    • go generate ./...

    • go generate ./...

    • Regenerate

    • remove trailing period

    • Prevent entity resolver generation for stub types. In Federation 2 key fields are implicitly external

    • Add more comments to "isResolvable"

    • Check that no resolvers are set for stub "Hello"

    • Run generate with go 1.16

    • Simplify implicit external check

    • Add stricter federation version check. Update comment on expected behavior of the resolvable argument. Add comment to documentation about external directive.

    ... (truncated)

    Commits
    • d657946 release v0.17.22
    • 9a29229 graphql.Error is not deprecated anymore (#2455)
    • a44685b Ability to return multiple errors from resolvers raise than add it to stack. ...
    • db1e3b8 Implicit external check (#2449)
    • 5065163 Re-generate and update release checklist to regenerate for new version
    • 5cfc22d Add v0.17.21 Release notes
    • 5d39046 v0.17.21 postrelease bump
    • 9deb838 release v0.17.21
    • 5c083c7 use goField directive for getters generation (#2447)
    • 463d213 fix: safe http error response (#2438)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • build(deps): bump go.mongodb.org/mongo-driver from 1.8.3 to 1.11.1

    build(deps): bump go.mongodb.org/mongo-driver from 1.8.3 to 1.11.1

    Bumps go.mongodb.org/mongo-driver from 1.8.3 to 1.11.1.

    Release notes

    Sourced from go.mongodb.org/mongo-driver's releases.

    MongoDB Go Driver 1.11.1

    The MongoDB Go Driver Team is pleased to release version 1.11.1 of the official Go driver.

    Release Notes

    This release contains a bug fix for heartbeat buildup with streaming protocol when the Go driver process is paused in an FAAS environment (e.g. AWS Lambda). This release also includes a bug fix for handling sequential "NoWritesPerformed" labeled operation errors, in that they should still return the "previous indefinite error".

    P.S. We want to hear about how Go developers use MongoDB and the MongoDB Go Driver! If you haven't already, please take the 2022 MongoDB Go Developer Survey.


    For a full list of tickets included in this release, please see the links below:

    Documentation for the Go driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. Questions and inquiries can be asked on the MongoDB Developer Community. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the Go driver is greatly appreciated!

    MongoDB Go Driver 1.11.0

    The MongoDB Go Driver Team is pleased to release version 1.11.0 of the official Go driver.

    Release Notes

    This release improves the Timeout API and behavior, reduces memory allocations when running most operations, and fixes several bugs. It also removes support for some legacy versions of MongoDB and Go. See below for more details.

    Improve Timeout API and Behavior

    Setting Timeout on a mongo.Client to enable a client-level default operation timeout is a feature added in version 1.10.0 of the driver. Various improvements have been made to this API. In particular:

    • If Timeout is set, the driver will now retry as many times as possible before the context's deadline instead of just once. This should improve application resiliency when using Timeout.
    • The mongo.IsTimeout error helper has been extended to catch more timeout errors.
    • New GridFS methods have been added that take contexts instead of using SetReadDeadline and SetWriteDeadline.

    This feature will remain a provisional API while we gather feedback on its design and solidify our specification.

    Reduce Memory Allocations

    Reduce memory allocations in several critical paths in operation execution.

    Fix SRV Polling

    Fix a severe bug in SRV polling which may prevent changes in SRV records from updating the servers that the Go driver attempts to connect to when the MongoDB connection string includes a username and password.

    Remove Support for Legacy MongoDB Versions

    As of this release, the Go driver now requires MongoDB 3.6 or newer.

    Remove Support for Legacy Go Versions

    ... (truncated)

    Commits
    • 88c138b Update version to v1.11.1
    • 1f525ec Merge branch 'release/1.11' of github.com:mongodb/mongo-go-driver into releas...
    • fc7ebbb Revert "Release/1.11 (#1146)"
    • bf833d5 Release/1.11 (#1146)
    • cd79115 resolve merge conflicts
    • ed484be GODRIVER-2577 Retry heartbeat on timeout to prevent pool cleanup in FAAS paus...
    • 30805e4 GODRIVER-2333 Assert that Ping op succeeds initial DNS spec tests (#1124)
    • 19f3fb9 GODRIVER-2651 Break NoWritesPerformed-Only Error Sequence (#1135)
    • 4803b59 Update version to v1.11.1-prerelease
    • ea2a55c Update version to v1.11.0
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Related tags
Pape-server - A small server written in golang to serve a random wallpaper.

pape-server I like to inject custom CSS themes into a lot of websites and electron apps, however browsers don't let websites access local disk through

Dec 31, 2021
A Language Server Protocol (LSP) server for Jsonnet

Jsonnet Language Server Warning: This project is in active development and is likely very buggy. A Language Server Protocol (LSP) server for Jsonnet.

Nov 22, 2022
The server-pubsub is the main backend of DATAVOC project that manages all the other web-server modules of the same project such as the processor

server-pubsub The server-pubsub is the main backend of DATAVOC project that manages all the other web-server modules of the same project such as the p

Dec 3, 2021
Server and client implementation of the grpc go libraries to perform unary, client streaming, server streaming and full duplex RPCs from gRPC go introduction

Description This is an implementation of a gRPC client and server that provides route guidance from gRPC Basics: Go tutorial. It demonstrates how to u

Nov 24, 2021
Cert bound sts server - Certificate Bound Tokens using Security Token Exchange Server (STS)
Cert bound sts server - Certificate Bound Tokens using Security Token Exchange Server (STS)

Certificate Bound Tokens using Security Token Exchange Server (STS) Sample demonstration of Certificate Bound Tokens acquired from a Security Token Ex

Jan 2, 2022
Echo-server - An HTTP echo server designed for testing applications and proxies

echo-server An HTTP echo server designed for testing applications and proxies. R

Dec 20, 2022
Broadcast-server - A simple Go server that broadcasts any data/stream

broadcast A simple Go server that broadcasts any data/stream usage data You can

Oct 21, 2022
Videos2gether-server - Server for the Realtime video streaming app Videos2Gether

Videos Together server Server source code for the https://videos2gether.com Arch

Jan 9, 2022
JPRQ Customizer is a customizer that helps to use the JPRQ server code and make it compatible with your own server with custom subdomain and domain
JPRQ Customizer is a customizer that helps to use the JPRQ server code and make it compatible with your own server with custom subdomain and domain

JPRQ Customizer is a customizer that helps to use the JPRQ server code and make it compatible with your own server with custom subdomain and domain.You can upload the generated directory to your web server and expose user localhost to public internet. You can use this to make your local machine a command center for your ethical hacking purpose ;)

Jan 19, 2022
Envoy-eds-server - Envoy EDS server is a working Envoy Discovery Service implementation

envoy-eds-server Intro Envoy EDS server is a working Envoy Discovery Service imp

Apr 2, 2022
Http-server - A HTTP server and can be accessed via TLS and non-TLS mode

Application server.go runs a HTTP/HTTPS server on the port 9090. It gives you 4

Feb 3, 2022
Server - Dupman server written in Go

server dupman server written in Go Requirements Go (>=1.17) Installation Usage C

Feb 22, 2022
“Dear Port80” is a zero-config TCP proxy server that hides SSH connection behind a HTTP server!

Dear Port80 About The Project: “Dear Port80” is a zero-config TCP proxy server that hides SSH connection behind a HTTP server! +---------------------

Jun 29, 2022
Simple mDNS client/server library in Golang

mdns Simple mDNS client/server library in Golang. mDNS or Multicast DNS can be used to discover services on the local network without the use of an au

Jan 4, 2023
golang tcp server

TCPServer Package tcp_server created to help build TCP servers faster. Install package go get -u github.com/firstrow/tcp_server Usage: NOTICE: OnNewMe

Dec 28, 2022
A LWM2M Client and Server implementation (For Go/Golang)

Betwixt - A LWM2M Client and Server in Go Betwixt is a Lightweight M2M implementation written in Go OMA Lightweight M2M is a protocol from the Open Mo

Dec 23, 2022
High-performance PHP application server, load-balancer and process manager written in Golang
High-performance PHP application server, load-balancer and process manager written in Golang

RoadRunner is an open-source (MIT licensed) high-performance PHP application server, load balancer, and process manager. It supports running as a serv

Jan 1, 2023
golang NFSv3 server

Golang Network File Server NFSv3 protocol implementation in pure Golang. Current Status: Minimally tested Mounts, read-only and read-write support Usa

Dec 27, 2022