Add generation status for each file in report

sweep-ai[bot] commented 1 year ago

PR Feedback (click)

[ ] 👍 Sweep Did Well
[ ] 👎 Sweep Needs Improvement
Description

This PR adds the generation status for each file in the report generated by the jekyll-seo-ai-action project. The generation status provides information about whether the description was generated, skipped, or encountered an error during processing.

Summary of Changes

Added a new enum GenerationStatus in src/generator.js to represent the different generation statuses.
Modified the DescriptionResult class in src/generator.js to include a status property of type GenerationStatus.
Updated the generateDescription function in src/generator.js to return a DescriptionResult object with the appropriate status based on the processing conditions.
Modified the generateDescriptions function in src/generator.js to handle the new DescriptionResult object and include the status in the report.
Updated the generateReport function in src/report.js to include the status in the report generated for each file.

These changes provide users with detailed information about the generation status of each file, making it easier to understand what happened during the processing of the files.

Fixes #5.

🎉 Latest improvements to Sweep:

Getting Sweep to run linters before committing! Check out Sweep Sandbox Configs to set it up.
Added support for self-hosting! Check out Self-hosting Sweep to get started.
[Self Hosting] Multiple options to compute vector embeddings, configure your .env file using VECTOR_EMBEDDING_SOURCE

💡 To get Sweep to edit this pull request, you can:

Leave a comment below to get Sweep to edit the entire PR
Leave a comment in the code will only modify the file
Edit the original issue to get Sweep to recreate the PR from scratch

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is npm test. Here are the relevant lines from the logs:

console.error
Error generating description for non-existent-file.md: Error: File not found

console.error
Error generating description for test/fixtures/empty.md: Error: File not found

console.error
Error generating description for test/fixtures/with-description.md: Error: File not found

console.warn
No front matter found for test/fixtures/without-front-matter.md -- is it really a blog post?

console.warn
No front matter found for test/fixtures/without-date.md -- is it really a blog post?

console.info
Front matter already contains a description for test/fixtures/with-description.md -- skipping

● generateDescriptions › should return an empty array when given an array of non-existent files

● generateDescriptions › should return an empty array when given an array of files that don't contain front matter

● generateDescriptions › should return an empty array when given an array of files that already contain a description

● generateDescriptions › should return an empty array when the files do not have front matters

● generateDescriptions › should return an empty array when the files do not have a date in the front matter

● generateDescriptions › should return an empty array when the files already have descriptions in the front matter

Please note that the logs are truncated and may not include all the relevant information.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is npm test. Here are the relevant lines from the logs:

console.error
Error generating description for non-existent-file.md: Error: File not found

console.error
Error generating description for test/fixtures/empty.md: Error: File not found

console.error
Error generating description for test/fixtures/with-description.md: Error: File not found

console.warn
No front matter found for test/fixtures/without-front-matter.md -- is it really a blog post?

console.warn
No front matter found for test/fixtures/without-date.md -- is it really a blog post?

console.info
Front matter already contains a description for test/fixtures/with-description.md -- skipping

These lines indicate that there were errors generating descriptions for certain files due to them not being found. Additionally, there were warnings for files that did not have front matter, and an info message indicating that a file already had a description and was skipped.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is npm test. Here are the relevant lines from the logs:

console.error
Error generating description for non-existent-file.md: Error: File not found

console.error
Error generating description for test/fixtures/empty.md: Error: File not found

console.error
Error generating description for test/fixtures/with-description.md: Error: File not found

console.warn
No front matter found for test/fixtures/without-front-matter.md -- is it really a blog post?

console.warn
No front matter found for test/fixtures/without-date.md -- is it really a blog post?

console.info
Front matter already contains a description for test/fixtures/with-description.md -- skipping

These lines indicate that there were errors generating descriptions for certain files due to them not being found. Additionally, there were warnings for files that did not have front matter, and an info message indicating that a file already had a description and was skipped.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is npm test. Here are the relevant lines from the logs:

console.error
Error generating description for non-existent-file.md: Error: File not found

console.error
Error generating description for test/fixtures/empty.md: Error: File not found

console.error
Error generating description for test/fixtures/with-description.md: Error: File not found

console.warn
No front matter found for test/fixtures/without-front-matter.md -- is it really a blog post?

console.warn
No front matter found for test/fixtures/without-date.md -- is it really a blog post?

console.info
Front matter already contains a description for test/fixtures/with-description.md -- skipping

These lines indicate that there were errors generating descriptions for certain files due to them not being found. Additionally, there were warnings for files that did not have front matter, and an info message indicating that a file already had a description and was skipped.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is Run ./. Here are the relevant lines from the logs:

RequestError [HttpError]: Invalid tree info
at /home/runner/work/jekyll-seo-ai-action/jekyll-seo-ai-action/dist/index.js:6059:25
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async createCommit (/home/runner/work/jekyll-seo-ai-action/jekyll-seo-ai-action/dist/index.js:22318:16)
at async run (/home/runner/work/jekyll-seo-ai-action/jekyll-seo-ai-action/dist/index.js:25101:5) {
status: 422,
response: {
url: 'https://api.github.com/repos/AlphaGit/jekyll-seo-ai-action/git/trees',
status: 422,
headers: {
'access-control-allow-origin': '*',
'access-control-expose-headers': 'ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset',
connection: 'close',
'content-length': '106',
'content-security-policy': "default-src 'none'",
'content-type': 'application/json; charset=utf-8',
date: 'Sun, 24 Sep 2023 18:55:38 GMT',
'referrer-policy': 'origin-when-cross-origin, strict-origin-when-cross-origin',
server: 'GitHub.com',
'strict-transport-security': 'max-age=31536000; includeSubdomains; preload',
vary: 'Accept-Encoding, Accept, X-Requested-With',
'x-accepted-github-permissions': 'contents=write',
'x-content-type-options': 'nosniff',
'x-frame-options': 'deny',
'x-github-api-version-selected': '2022-11-28',
'x-github-media-type': 'github.v3; format=json',
'x-github-request-id': '600B:5CB0:27E638F:51FDA6C:6510862A',
'x-ratelimit-limit': '1000',
'x-ratelimit-remaining': '945',
'x-ratelimit-reset': '1695583445',
'x-ratelimit-resource': 'core',
'x-ratelimit-used': '55',
'x-xss-protection': '0'
},
data: {
message: 'Invalid tree info',
documentation_url: 'https://docs.github.com/rest/git/trees#create-a-tree'
}
},
request: {
method: 'POST',
url: 'https://api.github.com/repos/AlphaGit/jekyll-seo-ai-action/git/trees',
headers: {
accept: 'application/vnd.github.v3+json',
'user-agent': 'octokit-core.js/3.6.0 Node.js/16.20.1 (linux; x64)',
authorization: 'token [REDACTED]',
'content-type': 'application/json; charset=utf-8'
},
body: '{"base_tree":"64c679907b410bc438c274a6fec66d480ad9f90b","tree":[]}',
request: {
agent: Agent {
_events: [Object: null prototype] {
free: [Function (anonymous)],
newListener: [Function: maybeEnableKeylog]
},
_eventsCount: 2,
_maxListeners: undefined,
defaultPort: 443,
protocol: 'https:',
options: [Object: null prototype] { path: null },
requests: [Object: null prototype] {},
sockets: [Object: null prototype] {
'api.github.com:443:::::::::::::::::::::': [ [TLSSocket] ]
},
freeSockets: [Object: null prototype] {},
keepAliveMsecs: 1000,
keepAlive: false,
maxSockets: Infinity,
maxFreeSockets: 256,
scheduling: 'lifo',
maxTotalSockets: Infinity,
totalSocketCount: 1,
maxCachedSessions: 100,
_sessionCache: {
map: {
'api.github.com:443:::::::::::::::::::::': [Buffer [Uint8Array]]
},
list: [ 'api.github.com:443:::::::::::::::::::::' ]
},
[Symbol(kCapture)]: false
},
hook: [Function: bound bound register]
}
}
}
##[error]Invalid tree info

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is npm test. Here are the relevant lines from the logs:

console.error
Error generating description for non-existent-file.md: Error: File not found

console.error
Error generating description for test/fixtures/empty.md: Error: File not found

console.error
Error generating description for test/fixtures/with-description.md: Error: File not found

console.warn
No front matter found for test/fixtures/without-front-matter.md -- is it really a blog post?

console.warn
No front matter found for test/fixtures/without-date.md -- is it really a blog post?

console.info
Front matter already contains a description for test/fixtures/with-description.md -- skipping

These lines indicate that there were errors generating descriptions for certain files due to them not being found. Additionally, there were warnings for files that did not have front matter, and an info message indicating that a file already had a description and was skipped.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is npm test. Here are the relevant lines from the logs:

console.error
Error generating description for non-existent-file.md: Error: File not found

console.error
Error generating description for test/fixtures/empty.md: Error: File not found

console.error
Error generating description for test/fixtures/with-description.md: Error: File not found

console.warn
No front matter found for test/fixtures/without-front-matter.md -- is it really a blog post?

console.warn
No front matter found for test/fixtures/without-date.md -- is it really a blog post?

console.info
Front matter already contains a description for test/fixtures/with-description.md -- skipping

These lines indicate that there were errors generating descriptions for certain files due to them not being found. Additionally, there were warnings for files that did not have front matter, and an info message indicating that a file already had a description and was skipped.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is npm test. Here are the relevant lines from the logs:

console.error
Error generating description for non-existent-file.md: Error: File not found

console.error
Error generating description for test/fixtures/empty.md: Error: File not found

console.error
Error generating description for test/fixtures/with-description.md: Error: File not found

console.warn
No front matter found for test/fixtures/without-front-matter.md -- is it really a blog post?

console.warn
No front matter found for test/fixtures/without-date.md -- is it really a blog post?

console.info
Front matter already contains a description for test/fixtures/with-description.md -- skipping

These lines indicate that there were errors generating descriptions for certain files due to them not being found. Additionally, there were warnings for files that did not have front matter, and an info message indicating that a file already had a description and was skipped.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is npm test. Here are the relevant lines from the logs:

console.error
Error generating description for non-existent-file.md: Error: File not found

console.error
Error generating description for test/fixtures/empty.md: Error: File not found

console.error
Error generating description for test/fixtures/with-description.md: Error: File not found

console.warn
No front matter found for test/fixtures/without-front-matter.md -- is it really a blog post?

console.warn
No front matter found for test/fixtures/without-date.md -- is it really a blog post?

console.info
Front matter already contains a description for test/fixtures/with-description.md -- skipping

These lines indicate that there were errors generating descriptions for certain files due to them not being found. Additionally, there were warnings for files that did not have front matter, and an info message indicating that a file already had a description and was skipped.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is npm test. Here are the relevant lines from the logs:

console.error
Error generating description for non-existent-file.md: Error: File not found

console.error
Error generating description for test/fixtures/empty.md: Error: File not found

console.error
Error generating description for test/fixtures/with-description.md: Error: File not found

console.warn
No front matter found for test/fixtures/without-front-matter.md -- is it really a blog post?

console.warn
No front matter found for test/fixtures/without-date.md -- is it really a blog post?

console.info
Front matter already contains a description for test/fixtures/with-description.md -- skipping

These lines indicate that there were errors generating descriptions for certain files due to them not being found. Additionally, there were warnings for files that did not have front matter, and an info message indicating that a file already had a description and was skipped.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is npm test. Here are the relevant lines from the logs:

console.error
Error generating description for non-existent-file.md: Error: File not found

console.error
Error generating description for test/fixtures/empty.md: Error: File not found

console.error
Error generating description for test/fixtures/with-description.md: Error: File not found

console.warn
No front matter found for test/fixtures/without-front-matter.md -- is it really a blog post?

console.warn
No front matter found for test/fixtures/without-date.md -- is it really a blog post?

console.info
Front matter already contains a description for test/fixtures/with-description.md -- skipping

These lines indicate that there were errors generating descriptions for certain files due to them not being found. Additionally, there were warnings for files that did not have front matter, and an info message indicating that a file already had a description and was skipped.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

sweep-ai[bot] commented 1 year ago

GitHub actions yielded the following error.

The command that failed is npm test. Here are the relevant lines from the logs:

console.error
Error generating description for non-existent-file.md: Error: File not found

console.error
Error generating description for test/fixtures/empty.md: Error: File not found

console.error
Error generating description for test/fixtures/with-description.md: Error: File not found

console.warn
No front matter found for test/fixtures/without-front-matter.md -- is it really a blog post?

console.warn
No front matter found for test/fixtures/without-date.md -- is it really a blog post?

console.info
Front matter already contains a description for test/fixtures/with-description.md -- skipping

These lines indicate that there were errors generating descriptions for certain files due to them not being found. Additionally, there were warnings for files that did not have front matter, and an info message indicating that a file already had a description and was skipped.

There are a lot of errors. This is likely due to a small parsing issue or a missing import with the files changed in the PR.

This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests.

I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR.

AlphaGit / jekyll-seo-ai-action

Add generation status for each file in report #10

PR Feedback (click)

Description

Summary of Changes