Merge pull request #347 from zowe/v2.x/staging

merge staging into rc

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,45 @@
+---
+name: Bug report
+about: Create a report to help us improve.
+title: ''
+labels: bug, new
+---
+
+<!-- Before opening a bug ticket, check if it can be solved by the website troubleshooting https://docs.zowe.org/stable/troubleshoot/troubleshooting or by using its search bar -->
+
+**Describe the bug**
+
+**Steps to Reproduce**
+
+1.
+2.
+
+**Expected behavior**
+
+**Screenshots (if needed)**
+
+**Logs**
+<!-- If applicable, add server logs collected at the time of your problem. -->
+<!-- Logs can contain some system information like hostnames, usernames, and IP/port info. -->
+<!-- Please sanitize your logs or reach out to the TSC or ZAC if you need to provide your logs with discretion -->
+<!-- Note you can increase log verbosity if desired. -->
+<!-- zwe command tracing: Use --trace on a zwe command -->
+<!-- zwe startup tracing: Set zowe.launchScript.logLevel to trace (https://github.com/zowe/zowe-install-packaging/blob/677a607686e6ee7ecb349dc5925a6f58dd9e61da/example-zowe.yaml#L356) -->
+<!-- app-server tracing: You can set any of the log levels here https://github.com/zowe/zlux-app-server/blob/d1b10b39bd0ba530784144430c33c19a5fb8f935/schemas/app-server-config.json#L378 using the guide here https://docs.zowe.org/stable/user-guide/mvd-configuration#logging-configuration -->
+<!-- zss tracing: Similar to app-server tracing, but with these loggers https://github.com/zowe/zss/blob/0bc9c812a5cd5a72768125d13826430e3a5bf1fb/schemas/zss-config.json#L216 -->
+
+
+**Describe your environment**
+<!-- Some items below may not apply to your use case, but answer as best as you can -->
+
+- Zowe version number (Check the Desktop login screen, or manifest.json in the Zowe install folder): 
+- Install method (pax, smpe, kubernetes, github clone):
+- Operating system (z/OS, kubernetes, etc) and OS version:
+- Node.js version number (Shown in logs, or via `node --version`):
+- Java version number (Shown in logs, or via `java -version`):
+- z/OSMF version:
+- What is the output of log message ZWES1014I:
+- Environment variables in use:
+
+
+**Additional context**

.github/ISSUE_TEMPLATE/bug_report_high.md

@@ -0,0 +1,45 @@
+---
+name: High-severity bug report
+about: Create a report on a high-severity bug. High severity is when there is an issue that has a major impact on usage of Zowe.
+title: ''
+labels: bug, new, severity-high
+---
+
+<!-- Before opening a bug ticket, check if it can be solved by the website troubleshooting https://docs.zowe.org/stable/troubleshoot/troubleshooting or by using its search bar -->
+
+**Describe the bug**
+
+**Steps to Reproduce**
+
+1.
+2.
+
+**Expected behavior**
+
+**Screenshots (if needed)**
+
+**Logs**
+<!-- If applicable, add server logs collected at the time of your problem. -->
+<!-- Logs can contain some system information like hostnames, usernames, and IP/port info. -->
+<!-- Please sanitize your logs or reach out to the TSC or ZAC if you need to provide your logs with discretion -->
+<!-- Note you can increase log verbosity if desired. -->
+<!-- zwe command tracing: Use --trace on a zwe command -->
+<!-- zwe startup tracing: Set zowe.launchScript.logLevel to trace (https://github.com/zowe/zowe-install-packaging/blob/677a607686e6ee7ecb349dc5925a6f58dd9e61da/example-zowe.yaml#L356) -->
+<!-- app-server tracing: You can set any of the log levels here https://github.com/zowe/zlux-app-server/blob/d1b10b39bd0ba530784144430c33c19a5fb8f935/schemas/app-server-config.json#L378 using the guide here https://docs.zowe.org/stable/user-guide/mvd-configuration#logging-configuration -->
+<!-- zss tracing: Similar to app-server tracing, but with these loggers https://github.com/zowe/zss/blob/0bc9c812a5cd5a72768125d13826430e3a5bf1fb/schemas/zss-config.json#L216 -->
+
+
+**Describe your environment**
+<!-- Some items below may not apply to your use case, but answer as best as you can -->
+
+- Zowe version number (Check the Desktop login screen, or manifest.json in the Zowe install folder): 
+- Install method (pax, smpe, kubernetes, github clone):
+- Operating system (z/OS, kubernetes, etc) and OS version:
+- Node.js version number (Shown in logs, or via `node --version`):
+- Java version number (Shown in logs, or via `java -version`):
+- z/OSMF version:
+- What is the output of log message ZWES1014I:
+- Environment variables in use:
+
+
+**Additional context**

.github/ISSUE_TEMPLATE/bug_report_low.md

@@ -0,0 +1,45 @@
+---
+name: Low-severity bug report
+about: Create a report on a low-severity bug. Low severity is when there is an issue that is inconvenient but doesn't impact key use cases.
+title: ''
+labels: bug, new, severity-low
+---
+
+<!-- Before opening a bug ticket, check if it can be solved by the website troubleshooting https://docs.zowe.org/stable/troubleshoot/troubleshooting or by using its search bar -->
+
+**Describe the bug**
+
+**Steps to Reproduce**
+
+1.
+2.
+
+**Expected behavior**
+
+**Screenshots (if needed)**
+
+**Logs**
+<!-- If applicable, add server logs collected at the time of your problem. -->
+<!-- Logs can contain some system information like hostnames, usernames, and IP/port info. -->
+<!-- Please sanitize your logs or reach out to the TSC or ZAC if you need to provide your logs with discretion -->
+<!-- Note you can increase log verbosity if desired. -->
+<!-- zwe command tracing: Use --trace on a zwe command -->
+<!-- zwe startup tracing: Set zowe.launchScript.logLevel to trace (https://github.com/zowe/zowe-install-packaging/blob/677a607686e6ee7ecb349dc5925a6f58dd9e61da/example-zowe.yaml#L356) -->
+<!-- app-server tracing: You can set any of the log levels here https://github.com/zowe/zlux-app-server/blob/d1b10b39bd0ba530784144430c33c19a5fb8f935/schemas/app-server-config.json#L378 using the guide here https://docs.zowe.org/stable/user-guide/mvd-configuration#logging-configuration -->
+<!-- zss tracing: Similar to app-server tracing, but with these loggers https://github.com/zowe/zss/blob/0bc9c812a5cd5a72768125d13826430e3a5bf1fb/schemas/zss-config.json#L216 -->
+
+
+**Describe your environment**
+<!-- Some items below may not apply to your use case, but answer as best as you can -->
+
+- Zowe version number (Check the Desktop login screen, or manifest.json in the Zowe install folder): 
+- Install method (pax, smpe, kubernetes, github clone):
+- Operating system (z/OS, kubernetes, etc) and OS version:
+- Node.js version number (Shown in logs, or via `node --version`):
+- Java version number (Shown in logs, or via `java -version`):
+- z/OSMF version:
+- What is the output of log message ZWES1014I:
+- Environment variables in use:
+
+
+**Additional context**

.github/ISSUE_TEMPLATE/bug_report_medium.md

@@ -0,0 +1,45 @@
+---
+name: Medium-severity bug report
+about: Create a report on a medium-severity bug. Medium severity is when there is an issue that makes the use of Zowe difficult, but has a workaround or doesn't prevent the use of Zowe.
+title: ''
+labels: bug, new, severity-medium
+---
+
+<!-- Before opening a bug ticket, check if it can be solved by the website troubleshooting https://docs.zowe.org/stable/troubleshoot/troubleshooting or by using its search bar -->
+
+**Describe the bug**
+
+**Steps to Reproduce**
+
+1.
+2.
+
+**Expected behavior**
+
+**Screenshots (if needed)**
+
+**Logs**
+<!-- If applicable, add server logs collected at the time of your problem. -->
+<!-- Logs can contain some system information like hostnames, usernames, and IP/port info. -->
+<!-- Please sanitize your logs or reach out to the TSC or ZAC if you need to provide your logs with discretion -->
+<!-- Note you can increase log verbosity if desired. -->
+<!-- zwe command tracing: Use --trace on a zwe command -->
+<!-- zwe startup tracing: Set zowe.launchScript.logLevel to trace (https://github.com/zowe/zowe-install-packaging/blob/677a607686e6ee7ecb349dc5925a6f58dd9e61da/example-zowe.yaml#L356) -->
+<!-- app-server tracing: You can set any of the log levels here https://github.com/zowe/zlux-app-server/blob/d1b10b39bd0ba530784144430c33c19a5fb8f935/schemas/app-server-config.json#L378 using the guide here https://docs.zowe.org/stable/user-guide/mvd-configuration#logging-configuration -->
+<!-- zss tracing: Similar to app-server tracing, but with these loggers https://github.com/zowe/zss/blob/0bc9c812a5cd5a72768125d13826430e3a5bf1fb/schemas/zss-config.json#L216 -->
+
+
+**Describe your environment**
+<!-- Some items below may not apply to your use case, but answer as best as you can -->
+
+- Zowe version number (Check the Desktop login screen, or manifest.json in the Zowe install folder): 
+- Install method (pax, smpe, kubernetes, github clone):
+- Operating system (z/OS, kubernetes, etc) and OS version:
+- Node.js version number (Shown in logs, or via `node --version`):
+- Java version number (Shown in logs, or via `java -version`):
+- z/OSMF version:
+- What is the output of log message ZWES1014I:
+- Environment variables in use:
+
+
+**Additional context**

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: Suggest an idea for ZSS
+labels: enhancement, new
+---
+
+<!-- Thanks for deciding to open an issue. Before submitting, please complete the following information. -->
+
+**Is your feature or enhancement request related to a problem or limitation? Please describe**
+
+<!-- A clear and concise description of the problem or limitation. Example: I'm frustrated when [...] happens, or I wish I was able to [...] with Zowe -->
+
+**Describe your enhancement idea**
+
+<!-- A clear and concise description of what you want to happen, such as the task you are trying to complete. -->
+<!-- Please attach images or references if it helps you describe what you'd like -->
+
+**Describe alternatives you've considered**
+
+<!-- A clear and concise description of any alternative solutions or workarounds you've used to overcome the problem or limitation. -->
+
+**Provide any additional context**
+
+<!-- Add any other context (code snippets, error messages, sample outputs, screenshots) about the request here. -->
+

.github/pull_request_template.md

@@ -0,0 +1,35 @@
+<!-- Thank you for submitting a PR to Zowe! To help us understand, test, and give feedback on your code, please fill in the details below. -->
+
+## Proposed changes
+<!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue. -->
+
+This PR addresses Issue: [*Link to Github issue within https://github.com/zowe/zowe-common-c/issues* if any]
+
+This PR depends upon the following PRs:
+
+## Type of change
+Please delete options that are not relevant.
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Change in a documentation
+- [ ] Refactor the code 
+- [ ] Chore, repository cleanup, updates the dependencies.
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+
+## PR Checklist
+Please delete options that are not relevant.
+- [ ] If the changes in this PR are meant for the next release / mainline, this PR targets the "staging" branch.
+- [ ] My code follows the style guidelines of this project (see: [Contributing guideline](https://github.com/zowe/zss/blob/v2.x/master/CONTRIBUTING.md))
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] video or image is included if visual changes are made
+- [ ] Relevant update to CHANGELOG.md
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works, or describe a test method below
+
+## Testing
+<!-- Describe how this code should be tested. I've you've added an automated or unit test, then describe how to run it. Otherwise, describe how you have tested it and how others should test it. -->
+
+## Further comments
+<!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, or if there are follow-up tasks and TODOs etc... -->

.github/workflows/stale.yml

@@ -0,0 +1,30 @@
+name: 'Close stale issues and PRs'
+on:
+  schedule:
+    - cron: '0 */6 * * *'
+
+permissions:
+  issues: write
+  pull-requests: write
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v5
+        with:
+          close-issue-message: >
+            This issue has been automatically closed due to lack of activity.
+            If this issue is still valid and important to you, it can be reopened.
+          days-before-close: 90
+          days-before-stale: 180
+          exempt-all-assignees: true
+          exempt-all-milestones: true
+          exempt-issue-labels: "community-upvoted, dependency, for-review, keep, security, high-severity, critical-severity, help-wanted, good-first-issue"
+          stale-issue-label: "stale-reopen-if-needed"
+          stale-issue-message: >
+            This issue has been automatically marked as stale because it has not had
+            recent activity. It will be closed if no further activity occurs,
+            but can be reopened if needed. Thank you for your contributions.
+          stale-pr-label: "stale-reopen-if-needed"
+          start-date: "2022-05-30T00:00:00Z"

CHANGELOG.md

@@ -1,5 +1,10 @@
 # Zowe Common C Changelog
 
+## `2.5.0`
+
+- Added embeddedjs command "xplatform.appendFileUTF8" for appending to files rather than writing whole files.
+- Bugfix that the configmgr binary would always return rc=0. Now, it has various return codes for the various internal errors or config invalid responses.
+
 ## `2.3.0`
 
 - Bugfix for lht functions of collections.c to avoid memory issues on negative keys

build/configmgr.proj.env

@@ -1,5 +1,5 @@
 PROJECT="configmgr"
-VERSION=0.4.0
+VERSION=0.4.1
 DEPS="QUICKJS LIBYAML"
 
 QUICKJS="quickjs"