Release 0.3.1

Co-authored-by: Michał Bartoszkiewicz <[email protected]>
Co-authored-by: Jan Chorowski <[email protected]>
Co-authored-by: Xavier Gendre <[email protected]>
Co-authored-by: Adrian Kosowski <[email protected]>
Co-authored-by: Jakub Kowalski <[email protected]>
Co-authored-by: Sergey Kulik <[email protected]>
Co-authored-by: Mateusz Lewandowski <[email protected]>
Co-authored-by: Mohamed Malhou <[email protected]>
Co-authored-by: Krzysztof Nowicki <[email protected]>
Co-authored-by: Richard Pelgrim <[email protected]>
Co-authored-by: Kamil Piechowiak <[email protected]>
Co-authored-by: Paweł Podhajski <[email protected]>
Co-authored-by: Olivier Ruas <[email protected]>
Co-authored-by: Przemysław Uznański <[email protected]>
Co-authored-by: Sebastian Włudzik <[email protected]>
GitOrigin-RevId: 4d326333cbb4815d6005d766898afb41b07b3c9d

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,66 @@
+name: Bug Report
+description: File a bug report
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: Steps to reproduce
+      description: What happened and how to reproduce it?
+      placeholder: Tell us what you see! 
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      placeholder: Tell us what you see! It would be nice if you could leave us the logs.
+      render: text
+    validations:
+      required: true
+  - type: textarea
+    id: what-did-you-expect
+    attributes:
+      label: What did you expect to happen?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Describe your expectations.
+    validations:
+      required: true
+  - type: input
+    id: pathway_version
+    attributes:
+      label: Version
+      description: On which version of Pathway are you working?
+    validations:
+      required: true
+  - type: input
+    id: docker_version
+    attributes:
+      label: Docker Versions (if used)
+      description: On which Docker version are you working?
+    validations:
+      required: false
+  - type: dropdown
+    id: os_version
+    attributes:
+      label: OS
+      description: On which OS did you run Pathway?
+      options:
+        - Linux
+        - MacOS
+    validations:
+      required: true
+  - type: dropdown
+    id: cpu_architecture
+    attributes:
+      label: On which CPU architecture did you run Pathway?
+      multiple: false
+      options:
+        - x86-64
+        - ARM64 (AArch64, Apple silicon)

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: New feature? Tell us about it on GitHub Discussions
+    url: https://github.com/pathwaycom/pathway/discussions
+    about: We are using Discussions as a place to connect with other members of the Pathway community.
+  - name: Discord
+    url: https://discord.com/invite/pathway
+    about: Ask questions you are wondering about.

.github/pull_request_template.md

@@ -0,0 +1,27 @@
+### Introduction
+To contribute code to the Pathway project, start by discussing your proposed changes on Discord or by filing an issue. 
+Once approved, follow the fork + pull request model against the main branch, ensuring you've signed the contributor license agreement.
+
+### Context
+<!--- Why is this change required? What problem does it solve? -->
+
+### How has this been tested?
+<!--- Please describe in detail how you tested your changes. -->
+
+### Types of changes
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature or improvement (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+
+### Related issue(s):
+1. 
+2.
+3.
+
+### Checklist:
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] My code follows the code style of this project,
+- [ ] My change requires a change to the documentation,
+- [ ] I described the modification in the CHANGELOG.md file.

CHANGELOG.md

@@ -7,6 +7,23 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.3.1] - 2023-08-29
+
+### Added
+
+- `tuple` reducer, that returns a tuple with values.
+- `ndarray` reducer, that returns an array with values.
+
+### Changed
+- `numpy` arrays of `int32`, `uint32` and `float32` are now converted to their 64-bit variants instead of tuples.
+- KNNIndex interface to take columns as inputs.
+- Reducers now check types of their arguments.
+
+### Fixed
+
+- Fixed delayed reporting of output connector errors.
+- Python objects are now freed more often, reducing peak memory usage.
+
 ## [0.3.0] - 2023-08-07
 
 ### Added

CODE_OF_CONDUCT.md

@@ -0,0 +1,80 @@
+# Pathway Code of Conduct
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and our
+community a harassment-free experience for everyone, regardless of age, body
+size, disability, health condition, ethnicity, gender identity and expression, level of
+experience, nationality, country of origin, personal appearance, race, religion, or sexual identity
+and orientation, and any other criteria falling under discriminatory practices under the Law of France.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+*   Using welcoming and inclusive language.
+*   Being respectful of differing viewpoints and experiences.
+*   Gracefully accepting constructive criticism.
+*   Focusing on what is best for the community.
+*   Showing empathy towards other community members.
+
+Examples of unacceptable behavior by participants include:
+
+*   The use of sexualized language or imagery and unwelcome sexual attention or
+    advances.
+*   Trolling, insulting/derogatory comments, and personal or political attacks.
+*   Public or private harassment.
+*   Publishing others' private information, such as a physical or electronic
+    address, without explicit permission.
+*   Conduct which could reasonably be considered inappropriate for the forum in
+    which it occurs.
+
+All Pathway forums and spaces are meant for professional interactions, and any behavior which could reasonably be considered inappropriate in a professional setting is unacceptable.
+
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+
+## Scope
+
+This Code of Conduct applies to all content on pathway.com, Pathway’s GitHub organization, or any other official Pathway web presence allowing for community interactions, as well as at all official Pathway events, whether offline or online.
+
+The Code of Conduct also applies within project spaces and in public spaces whenever an individual is representing Pathwayor its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed or de facto representative at an online or offline event. 
+
+
+## Conflict Resolution
+
+Conflicts in an open source project can take many forms, from someone having a bad day and using harsh and hurtful language in the issue queue, to more serious instances such as sexist/racist statements or threats of violence, and everything in between.
+
+If the behavior is threatening or harassing, or for other reasons requires immediate escalation, please see below.
+
+However, for the vast majority of issues, we aim to empower individuals to first resolve conflicts themselves, asking for help when needed, and only after that fails to escalate further. This approach gives people more control over the outcome of their dispute. 
+
+If you are experiencing or witnessing conflict, we ask you to use the following escalation strategy to address the conflict:
+
+1.  If you so wish and if you do not feel threatened or at risk of any form of personal abuse, address the perceived conflict directly with those involved, preferably in a real-time medium.
+2.  If this fails, get a third party (e.g. a mutual friend, and/or someone with
+    background on the issue, but not involved in the conflict) to intercede.
+3.  If you are still unable to resolve the conflict, and you believe it rises to
+    harassment or another code of conduct violation, report it.
+
+Please note that if you are experiencing or witnessing a discriminatory practice that would be susceptible to be condemned by law, we ask you to directly escalate to 3. 
+
+## Reporting Violations
+
+Violations of the Code of Conduct can be reported to Pathway via email to [email protected]. Project maintainers will determine whether the Code of Conduct was violated, and will issue an appropriate sanction, possibly including a written warning or expulsion from the project, project sponsored spaces, or project forums. We ask that you make a good-faith effort to resolve your conflict via the conflict resolution policy before submitting a report.
+
+Violations of the Code of Conduct can occur in any setting, even those unrelated to the project. We will only consider complaints about conduct that has occurred within one year of the report.
+
+
+## Enforcement
+
+If the Project maintainers receive a report alleging a violation of the Code of Conduct, the Project maintainers will notify the accused of the report, and provide them an opportunity to discuss the report before a sanction is issued. The Project maintainers will do their utmost to keep the reporter anonymous. If the act is ongoing (such as someone engaging in harassment), or involves a threat to anyone's safety (e.g. threats of violence), the Project maintainers may issue sanctions without notice.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Tensorflow Code of Conduct, and based on Contributor Covenant, version 1.4, available at https://contributor-covenant.org/version/1/4, and includes some aspects of the Geek Feminism Code of Conduct and the Drupal Code of Conduct.

CONTRIBUTING.md

@@ -0,0 +1,32 @@
+# Contributing to Pathway
+
+Welcome! This guide is intended to help developers that are new to the community
+to make contributions to the Pathway project. Please be sure to also read our [code of conduct](CODE_OF_CONDUCT.md). We work hard to make this a welcoming community for all, and we're excited to have you on board!
+
+## The basics:
+
+* Use the [Issue Tracker](https://github.com/pathwaycom/pathway/issues) to
+  report bugs, crashes, performance issues, etc... Please include as much detail
+  as possible.
+
+* [Discussions](https://github.com/pathwaycom/pathway/discussions) is a great
+  venue to ask questions, start a design discussion, or post an RFC.
+
+* [Discord](https://discord.com/invite/pathway) is our main gathering place - jump in and ask us anything!
+
+## Contributing Code
+
+We are eager to build Pathway together with the community and are excited to have you here!
+
+Important: Before you contribute any changes to our repositories (make a Pull Request) please get in touch with us and explain what you want to work on. You can do so by filing an issue, or asking us on Discord. That way you can get coding advice and speedier reviews. If you start to work on an issue before hearing back from a Pathway core team engineer there is a chance that we will not be able to accept your changes - something we all want to avoid!
+
+We use a standard GitHub fork + pull request model for merging and reviewing
+changes. New pull requests should be made against the main upstream branch.
+After a pull request is opened it will be reviewed, and merged after
+passing continuous integration tests and being accepted by a project or
+sub-system maintainer.
+
+We ask that developers sign our [contributor license
+agreement](https://cla-assistant.io/pathwaycom/pathway). The
+process of signing the CLA is automated, and you'll be prompted with instructions
+the first time you submit a pull request to the project.