Merge branch 'main' into feature/formatter

Signed-off-by: worksofliam <mrliamallan@live.co.uk>

Author: worksofliam

.eslintrc.json

@@ -14,7 +14,7 @@ jobs:
           node-version: '20'
       - uses: actions/checkout@v2
 
-      - run: npm install
+      - run: npm ci
 
       - run: npm install -g vsce ovsx
 

.github/workflows/release.yaml

@@ -1,10 +1,6 @@
 name: NodeJS with Webpack
 
-on:
-  push:
-    branches: [ "main" ]
-  pull_request:
-    branches: [ "main" ]
+on: pull_request
 
 jobs:
   build:
@@ -22,9 +18,14 @@ jobs:
       with:
         node-version: ${{ matrix.node-version }}
 
+    - name: Install dependencies
+      run: npm ci
+
+    - name: Type check
+      run: npm run typings
+
     - name: Build and package
       run: |
-        npm install
         npx webpack
         npm install -g vsce
         vsce package
@@ -35,18 +36,41 @@ jobs:
         cat $GITHUB_ENV
 
     - name: Upload dist artifacts
-      uses: actions/upload-artifact@v3
+      uses: actions/upload-artifact@v4
       with:
         name: test_vsix
         path: ${{env.vsix_name}}
 
+    - name: Find Comment
+      uses: peter-evans/find-comment@v1
+      id: fc
+      with:
+        issue-number: ${{ github.event.pull_request.number }}
+        comment-author: 'github-actions[bot]'
+        body-includes: new build is available
+
     - name: Post comment
+      continue-on-error: true
+      if: steps.fc.outputs.comment-id == ''
       uses: actions/github-script@v5
       with:
         script: |
           github.rest.issues.createComment({
             issue_number: context.issue.number,
             owner: context.repo.owner,
             repo: context.repo.repo,
-            body: '👋  A new build is available for this PR based on ${{ github.event.pull_request.head.sha }}.\n * [Download here.](https://github.com/halcyon-tech/vscode-db2i/actions/runs/${{ github.run_id }})\n'
+            body: '👋 A new build is available for this PR based on ${{ github.event.pull_request.head.sha }}.\n * [Download here.](https://github.com/codefori/vscode-db2i/actions/runs/${{ github.run_id }})\n* [Read more about how to test](https://github.com/codefori/vscode-db2i/blob/master/.github/pr_testing_template.md)'
           })
+
+    - name: Update comment
+      continue-on-error: true
+      if: steps.fc.outputs.comment-id != ''
+      uses: peter-evans/create-or-update-comment@v1
+      with:
+        edit-mode: replace
+        comment-id: ${{ steps.fc.outputs.comment-id }}
+        body: |
+          👋 A new build is available for this PR based on ${{ github.event.pull_request.head.sha }}.
+
+          * [Download here.](https://github.com/codefori/vscode-db2i/actions/runs/${{ github.run_id }})
+          * [Read more about how to test](https://github.com/codefori/vscode-db2i/blob/master/.github/pr_testing_template.md)

.github/workflows/webpack_ci.yaml

@@ -2,5 +2,4 @@ node_modules
 .vscode-test/
 *.vsix
 .DS_Store
-dist
-types
+dist

.gitignore

@@ -0,0 +1,20 @@
+temperature: 0.3
+description: Analyze and identify patterns in SELF errors on IBM i
+---
+<system>
+You are a highly experienced SQL error logging specialist with deep expertise in the SQL Error Logging Facility (SELF) on IBM i. Your knowledge extends across the entire SQLSTATE code set, SQL diagnostic logs, error resolution techniques, and performance optimization in Db2 for i. Your primary goal is to guide users through identifying the root causes of SQL errors and warnings, helping them enhance their system's stability and performance.
+
+When responding to user queries:
+- Offer detailed, structured explanations of error causes and potential resolutions.
+- Provide examples of similar issues and proven best practices.
+- Use your expertise to suggest preventive measures for future error mitigation.
+- Highlight any trends or patterns in the errors and suggest long-term improvements to error-handling strategies and system configuration.
+- Include references to specific IBM i documentation where applicable.
+
+Keep in mind the need for both short-term fixes and strategies for long-term stability and performance.
+</system>
+
+{{{ db2i "*SELF"}}}
+{{{ input }}}
+
+As a database administrator, perform a thorough analysis of the SELF errors logged on the IBM i system. Look for recurring error patterns, identify root causes, and provide actionable recommendations for resolving these issues and improving future error handling.

.prompts/self-analyst.prompt

@@ -0,0 +1,34 @@
+temperature: 0.3
+description: Generate a report on SELF error
+---
+<system>
+You are an expert in the SQL Error Logging Facility (SELF) on IBM i, a specialized tool designed for capturing, logging, and analyzing SQL errors and warnings in Db2 for i environments. Your expertise includes in-depth knowledge of SQLSTATE codes, SQL error handling, diagnostic logs, and optimizing error reporting for performance. Your goal is to offer precise, actionable guidance on configuring, using, and troubleshooting SELF, ensuring users can identify root causes, improve error handling strategies, and maintain optimal performance.
+
+When responding to user queries:
+- Provide clear, step-by-step explanations and direct references to relevant documentation.
+- Identify potential edge cases, focusing on how to prevent, detect, and resolve errors efficiently.
+- Address both short-term fixes and long-term best practices for robust error logging and system reliability.
+</system>
+
+{{{ input }}}
+
+Please analyze the provided SELF error using the following guidelines:
+
+1. **Error Analysis**:
+   - Examine the error message, SQLSTATE code, and relevant diagnostic information.
+   - Identify the root cause and potential contributing factors.
+   
+2. **SQL Context**:
+   - Provide the SQL statement or context that likely triggered the error.
+   - Explain any relevant patterns or operations in the SQL code that could lead to similar issues.
+
+3. **Resolution Guidance**:
+   - Offer specific recommendations for resolving the error.
+   - Suggest ways to prevent similar errors in future queries or operations.
+
+4. **Diagnostic Insights**:
+   - Analyze the diagnostic logs, explaining their significance and how they relate to the identified issue.
+
+5. **Performance Considerations**:
+   - Discuss any performance implications related to the error and error-handling process.
+   - Provide tips for optimizing SELF configurations to minimize performance impact during error logging.

.prompts/self-report.prompt

@@ -31,7 +31,24 @@
 			"preLaunchTask": "${defaultBuildTask}",
 			"sourceMaps": true,
 			"env": {
-				"testing": "true"
+				"db2_testing": "true"
+			}
+		},
+		{
+			"name": "Launch Tests (Specific)",
+			"type": "extensionHost",
+			"request": "launch",
+			"args": [
+				"--extensionDevelopmentPath=${workspaceFolder}"
+			],
+			"outFiles": [
+				"${workspaceFolder}/dist/**/*.js"
+			],
+			"preLaunchTask": "${defaultBuildTask}",
+			"sourceMaps": true,
+			"env": {
+				"db2_testing": "true",
+				"db2_specific": "true"
 			}
 		},
 	]

.vscode/launch.json

@@ -7,12 +7,14 @@
 			"type": "npm",
 			"script": "webpack-dev",
 			"problemMatcher": "$ts-webpack-watch",
+			"isBackground": false,
+			
 			"presentation": {
 				"reveal": "never"
 			},
 			"group": {
 				"kind": "build",
-				"isDefault": true
+				"isDefault": true,
 			}
 		}
 	]

.vscode/tasks.json

@@ -10,6 +10,5 @@ vsc-extension-quickstart.md
 media/main.png
 node_modules
 src
-types
 .github
 src/dsc.ts