<commit_before>---
swagger: "2.0"
info:
  title: Oshinko REST Server
  description: |-
    The REST API server for the Oshinko suite of applications
  version: "0.0.0"
consumes:
  - application/json
produces:
  - application/json
definitions:
  ClusterModel:
    allOf:
      - $ref: "#/definitions/NewCluster"
      - properties:
          status:
            description: |-
              Current status for the cluster
            type: string
        # INFO(elmiko) should we add a nodes member or something here?
        # i envision this might give links to each pod, or container in the
        # cluster. maybe helpful for introspecting the nodes.
        required:
          - status
  ErrorModel:
    properties:
      status:
        description: |-
          HTTP status code
        type: integer
        format: int32
      title:
        description: |-
          A brief summary of the error, this should remain consistent
          between errors of the same class
        type: string
      details:
        description: |-
          An explanation of the specific error that has occurred
        type: string
    required:
      - status
      - title
      - details
  ErrorResponse:
    properties:
      errors:<commit_msg>add more to the comments about the cluster model<commit_after>---
swagger: "2.0"
info:
  title: Oshinko REST Server
  description: |-
    The REST API server for the Oshinko suite of applications
  version: "0.0.0"
consumes:
  - application/json
produces:
  - application/json
definitions:
  ClusterModel:
    allOf:
      - $ref: "#/definitions/NewCluster"
      - properties:
          status:
            description: |-
              Current status for the cluster
            type: string
        # INFO(elmiko) should we add a nodes member or something here?
        # i envision this might give links to each pod, or container in the
        # cluster. maybe helpful for introspecting the nodes.
        # INFO(elmiko) i think at the least we will need to somehow easily
        # acquire the hostname/ip/whatever for the master spark nodes. the
        # outstanding question is, should this be a list of "services" within
        # the cluster, or should it be a list of "pods", or perhaps another
        # abstraction here.
        required:
          - status
  ErrorModel:
    properties:
      status:
        description: |-
          HTTP status code
        type: integer
        format: int32
      title:
        description: |-
          A brief summary of the error, this should remain consistent
          between errors of the same class
        type: string
      details:
        description: |-
          An explanation of the specific error that has occurred
        type: string
    required:
      - status
      - title
      - details
  ErrorResponse:
    properties:
      errors:
{'fraction_non_alphanumeric': 0.06300315015750788, 'fraction_numerical': 0.004900245012250612, 'mean_word_length': 1.9074262461851474, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6134634', 'n_tokens_mistral': 746, 'n_tokens_neox': 732, 'n_words': 300}