ubq-testing / bot-ai

0 stars 1 forks source link

feat: ui upgrade #4

Closed Keyrxng closed 1 year ago

Keyrxng commented 1 year ago

Resolves #3

I went ahead and used NextJs routing to implement things.

The displays are aligned so that the data is on the left, chat displayed in the middle and docs on the right all in parallel.

Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago
! Error: This model's maximum context length is 16385 tokens. However, your messages resulted in 85424 tokens. Please reduce the length of the messages.
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Have achieved specification

The changes in the PR align with the specification provided. Here is a summary of the changes made:

Please review the implementation in more detail to ensure it meets all requirements and functions as expected.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.

====================================
gptResponse {
  answer: 'Based on the PR diff, it appears that the specification has been met. \n' +
    '\n' +
    '- The PR includes the creation of a `navbar.tsx` component that implements a horizontal navbar with 3 sections: Chat, Data, and Docs.\n' +     
    '- The PR also includes the creation of a `dialogue.tsx` component that can be used to display dialogue boxes.\n' +
    '- The PR adds the necessary imports and components to the `layout.tsx` file to display the navbar and render the children components.\n' +     
    '- The PR adds the necessary components and content to the `@data/page.tsx` and `@docs/page.tsx` files to display the data and docs pages alongside the chat page.\n' +
    '- The PR also includes the necessary dependencies in the `package.json` file.\n' +
    '\n' +
    "Overall, the changes in the PR align with the specification provided. However, it's important to review the implementation in more detail to ensure that it meets all the requirements and functions as expected.",
  tokenUsage: { output: 192, input: 2886, total: 3078 }
}
====================================
====================================
validated {
  answer: '### Have achieved specification\n' +
    'The changes in the PR align with the specification provided. Here is a summary of the changes made:\n' +
    '\n' +
    '- Creation of `navbar.tsx` component with 3 sections: Chat, Data, and Docs.\n' +
    '- Creation of `dialogue.tsx` component for displaying dialogue boxes.\n' +
    '- Addition of necessary imports and components to `layout.tsx` file for displaying the navbar and rendering children components.\n' +
    '- Addition of necessary components and content to `@data/page.tsx` and `@docs/page.tsx` files for displaying data and docs pages alongside the chat page.\n' +
    '- Addition of necessary dependencies in `package.json` file.\n' +
    '\n' +
    'Please review the implementation in more detail to ensure it meets all requirements and functions as expected.',
  tokenUsage: { output: 149, input: 506, total: 655 }
}
====================================
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Have achieved specification

The changes in the PR align with the specification provided. Here is a summary of the changes made:

Please review the implementation in more detail to ensure it meets all requirements and functions as expected.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Haven't achieved specification

The answer provided contains unnecessary information and is not formatted correctly.

Here's how you can fix it:

  1. Remove the unnecessary summary of changes and focus on providing a concise and clear answer.
  2. Format the answer using GitHub Flavored Markdown, including tables, lists, and code blocks for clear and organized answers.
  3. Follow the template provided in the instructions, including the relevant information.

Example of a corrected answer:

### Have achieved specification
{username}, you have achieved the spec and now the reviewers will let you know if there are any other changes needed.

Please make these changes and resubmit your answer.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Haven't achieved specification

The answer provided contains unnecessary information and is not formatted correctly.

Here's how you can fix it:

  1. Follow the template provided in the validation standards section. Use the exact wording and formatting specified.

  2. Remove any unnecessary information or summaries of the changes made. Stick to the concise and organized format of the template.

  3. Use tables, lists, and code blocks where appropriate to clearly present the information.

Here's an example of how the answer should be formatted:

### Have achieved specification
{username}, you have achieved the spec and now the reviewers will let you know if there are any other changes needed.

Please make these changes and resubmit your answer.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Haven't achieved specification

The answer provided contains unnecessary information and is not formatted correctly.

Here's how you can fix it:

  1. Follow the template provided in the validation standards section.
  2. Remove any unnecessary information and focus on providing a concise and clear answer.
  3. Format the answer using GitHub Flavored Markdown, including tables, lists, and code blocks for clear and organized answers.

Example of a corrected answer:

### Have achieved specification
{username}, you have achieved the spec and now the reviewers will let you know if there are any other changes needed.

Please make the necessary changes and resubmit your answer.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Have achieved specification

Based on the PR diff, it appears that the specification has been met.

Overall, the changes in the PR align with the specification provided.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Have achieved specification

The changes in the PR align with the specification provided.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.

====================================
spec [
  {
    role: 'system',
    content: 'This pull request context: \n' +
      `[{"login":"Keyrxng","body":"Keyrxng's pull request description:\\nResolves #3 \\r\\n\\r\\nI went ahead and used NextJs routing to implement things.\\r\\n\\r\\nThe displays are aligned so that the data is on the left, chat displayed in the middle and docs on the right all in parallel."},{"login":"assistant","body":"#3 Specification: \\nCreate a structured layout\\r\\n\\r\\nImplement a horizontal navbar with 3 sections: Chat, Data, Docs\\r\\n\\r\\nCreate a docs page that is displayed alongside the chat page.\\r\\n\\r\\nCreate a data page that is displayed alongside the chat page.\\r\\n\\r\\nDocs and data should share the same layout, chat on left docs/data on right with same nav across all.\\r\\n\\r\\nDocs Page: \\r\\n\\r\\nThere will be md files that need rendered alongside the chat so they are indexable and readable, for now we just need them rendered.\\r\\n\\r\\nData Page:\\r\\n\\r\\nData will eventually display mid-process AI dialogue as to demonstrate how got the end result, for now we just need a display similar to chat that will display text alongside the chat interface."}]`
  }
]
====================================
====================================
gptResponse {
  answer: 'Based on the PR diff, it appears that the specification has been met. \n' +
    '\n' +
    '- The PR includes the creation of a `navbar.tsx` component that implements a horizontal navbar with 3 sections: Chat, Data, and Docs.\n' +     
    '- The PR also includes the creation of a `dialogue.tsx` component that can be used to display dialogue boxes.\n' +
    '- The `layout.tsx` file has been modified to include the `NavBar` component.\n' +
    '- The `page.tsx` file has been renamed to `Dual.tsx` and includes the necessary code for the chat functionality.\n' +
    '- Two new pages, `@data/page.tsx` and `@docs/page.tsx`, have been created to display the Data and Docs pages respectively.\n' +
    '- The `layout.tsx` file has been created to define the layout for the Data and Docs pages.\n' +
    '\n' +
    'Overall, the changes in the PR align with the specification provided.',
  tokenUsage: { output: 185, input: 2886, total: 3071 }
}
====================================
====================================
validated {
  answer: '### Have achieved specification\n' +
    'The changes in the PR align with the specification provided.',
  tokenUsage: { output: 16, input: 514, total: 530 }
}
====================================
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Have achieved specification

Based on the PR diff, it appears that the specification has been met.

Overall, the PR implements the required layout and components for the Chat, Data, and Docs pages.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.

====================================
gptResponse {
  answer: 'Based on the PR diff, it appears that the specification has been met. \n' +
    '\n' +
    '- The PR includes the creation of a `navbar.tsx` component that implements a horizontal navbar with 3 sections: Chat, Data, and Docs.\n' +     
    '- The PR also includes the creation of a `dialogue.tsx` component that can be used to display dialogue boxes.\n' +
    '- The `layout.tsx` file has been modified to include the `NavBar` component.\n' +
    '- The `page.tsx` file has been renamed to `Dual.tsx` and includes the necessary code for the chat functionality.\n' +
    '- Two new pages, `@data/page.tsx` and `@docs/page.tsx`, have been created to display the Data and Docs pages respectively.\n' +
    '- The `layout.tsx` file has been created to define the layout for the Data and Docs pages.\n' +
    '\n' +
    'Overall, the PR implements the required layout and components for the Chat, Data, and Docs pages.',
  tokenUsage: { output: 192, input: 2886, total: 3078 }
}
====================================
INFO (http): POST / 202 - 9004ms
INFO (server): POST http://localhost:3000/ - 202
====================================
validated {
  answer: '### Have achieved specification\n' +
    'Based on the PR diff, it appears that the specification has been met. \n' +
    '\n' +
    '- The PR includes the creation of a `navbar.tsx` component that implements a horizontal navbar with 3 sections: Chat, Data, and Docs.\n' +     
    '- The PR also includes the creation of a `dialogue.tsx` component that can be used to display dialogue boxes.\n' +
    '- The `layout.tsx` file has been modified to include the `NavBar` component.\n' +
    '- The `page.tsx` file has been renamed to `Dual.tsx` and includes the necessary code for the chat functionality.\n' +
    '- Two new pages, `@data/page.tsx` and `@docs/page.tsx`, have been created to display the Data and Docs pages respectively.\n' +
    '- The `layout.tsx` file has been created to define the layout for the Data and Docs pages.\n' +
    '\n' +
    'Overall, the PR implements the required layout and components for the Chat, Data, and Docs pages.',
  tokenUsage: { output: 197, input: 516, total: 713 }
}
====================================
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Have achieved specification

Based on the PR diff, it appears that the specification has been met.

Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Have achieved specification

Based on the PR diff, it appears that the specification has been met.

Overall, the PR implements the required layout and components for the Chat, Data, and Docs pages.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Spec Achieved:

Based on the PR diff, it appears that the specification has been met.

Overall, the PR implements the required layout and components for the Chat, Data, and Docs pages.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Spec Achieved:

Have achieved specification

{username}, you have achieved the spec and now the reviewers will let you know if there are any other changes needed.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.

====================================
gptResponse {
  answer: 'Based on the PR diff, it appears that the specification has been met. \n' +
    '\n' +
    '- The PR includes the creation of a `navbar.tsx` component that implements a horizontal navbar with 3 sections: Chat, Data, and Docs.\n' +     
    '- The PR also includes the creation of a `dialogue.tsx` component that can be used to display dialogue boxes.\n' +
    '- The `layout.tsx` file has been modified to include the `NavBar` component.\n' +
    '- The `page.tsx` file has been renamed to `Dual.tsx` and includes the necessary code for the chat functionality.\n' +
    '- Two new files, `@data/page.tsx` and `@docs/page.tsx`, have been added to implement the Data and Docs pages respectively.\n' +
    '- The `layout.tsx` file in the `tri-display` folder has been created to implement the layout for the Data and Docs pages.\n' +
    '- The `page.tsx` file in the `tri-display` folder has been renamed to `Dual.tsx` and includes the necessary code for the chat functionality.\n' +
    '\n' +
    'Overall, the changes in the PR align with the specification provided.',
  tokenUsage: { output: 226, input: 2886, total: 3112 }
}
====================================
====================================
validated {
  answer: 'Spec Achieved: \n' +
    '\n' +
    '### Have achieved specification\n' +
    '{username}, you have achieved the spec and now the reviewers will let you know if there are any other changes needed.',
  tokenUsage: { output: 34, input: 451, total: 485 }
}
====================================
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Spec Achieved:

Have achieved specification

Based on the PR diff, it appears that the specification has been met.

Overall, the PR implements the required layout and components for the Chat, Data, and Docs pages.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Spec Achieved:

Have achieved specification

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Spec achieved

You have achieved the spec and now the reviewers will let you know if there are any other changes needed.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.

====================================
gptResponse {
  answer: 'Based on the PR diff, it appears that the specification has been met. \n' +
    '\n' +
    '- The PR includes the creation of a `navbar.tsx` component that implements a horizontal navbar with 3 sections: Chat, Data, and Docs.\n' +     
    '- The PR also includes the creation of a `dialogue.tsx` component that can be used to display dialogue boxes.\n' +
    '- The `layout.tsx` file has been modified to include the `NavBar` component.\n' +
    '- The `page.tsx` file has been renamed to `Dual.tsx` and includes the necessary code for the chat functionality.\n' +
    '- Two new pages, `@data/page.tsx` and `@docs/page.tsx`, have been created to display the Data and Docs pages respectively.\n' +
    '- The `layout.tsx` file has been created to define the layout for the Data and Docs pages.\n' +
    '\n' +
    'Overall, the PR implements the required layout and components for the Chat, Data, and Docs pages.',
  tokenUsage: { output: 192, input: 2886, total: 3078 }
}
====================================
INFO (http): POST / 202 - 9003ms
INFO (server): POST http://localhost:3000/ - 202
====================================
validated {
  answer: '### Spec achieved\n' +
    'You have achieved the spec and now the reviewers will let you know if there are any other changes needed.',
  tokenUsage: { output: 25, input: 468, total: 493 }
}
====================================
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Spec achieved

Keyrxng, you have achieved the spec and now the reviewers will let you know if there are any other changes needed.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.

====================================
gptResponse {
  answer: 'Based on the PR diff, it appears that the specification has been met. \n' +
    '\n' +
    '- The PR includes the creation of a `navbar.tsx` component that implements a horizontal navbar with 3 sections: Chat, Data, and Docs.\n' +     
    '- The PR also includes the creation of a `dialogue.tsx` component that can be used to display dialogue boxes.\n' +
    '- The PR adds the necessary imports and components to the `layout.tsx` file to display the navbar and render the children components.\n' +     
    '- The PR adds the necessary components and content to the `@data/page.tsx` and `@docs/page.tsx` files to display the data and docs pages alongside the chat page.\n' +
    '- The PR also includes the necessary dependencies in the `package.json` file.\n' +
    '\n' +
    "Overall, the changes in the PR align with the specification provided. However, it's important to review the implementation in more detail to ensure that it meets all the requirements and functions as expected.",
  tokenUsage: { output: 192, input: 2886, total: 3078 }
}
====================================
====================================
validated {
  answer: '### Spec achieved\n' +
    'Keyrxng, you have achieved the spec and now the reviewers will let you know if there are any other changes needed.',
  tokenUsage: { output: 29, input: 473, total: 502 }
}
====================================
Keyrxng commented 1 year ago

/review

ubqbot[bot] commented 1 year ago

Spec achieved

Keyrxng, you have achieved the spec and now the reviewers will let you know if there are any other changes needed.

Ensure the pull request requirements are in the linked issue's first comment and update it if the scope evolves.

====================================
gptResponse {
  answer: 'Based on the PR diff, it appears that the specification has been met. \n' +
    '\n' +
    '- The PR includes the creation of a `navbar.tsx` component that implements a horizontal navbar with 3 sections: Chat, Data, and Docs.\n' +     
    '- The PR also includes the creation of a `dialogue.tsx` component that can be used to display dialogue boxes.\n' +
    '- The PR adds the necessary imports and components to the `layout.tsx` file to display the navbar and render the children components.\n' +     
    '- The PR adds the necessary components and content to the `@data/page.tsx` and `@docs/page.tsx` files to display the data and docs pages alongside the chat page.\n' +
    '- The PR also includes the necessary dependencies in the `package.json` file.\n' +
    '\n' +
    "Overall, the changes in the PR align with the specification provided. However, it's important to review the implementation in more detail to ensure that it meets all the requirements and functions as expected.",
  tokenUsage: { output: 192, input: 2886, total: 3078 }
}
====================================
====================================
validated {
  answer: '### Spec achieved\n' +
    'Keyrxng, you have achieved the spec and now the reviewers will let you know if there are any other changes needed.',
  tokenUsage: { output: 29, input: 473, total: 502 }
}
====================================