ueberdb2 1.4.16

package/.github/workflows/npmpublish.yml

@@ -0,0 +1,103 @@
+name: Node.js Package
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+      - master
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    services:
+      couchdb:
+        image: couchdb
+        ports:
+          - 5984:5984
+        env:
+          COUCHDB_USER: ueberdb
+          COUCHDB_PASSWORD: ueberdb
+      mongo:
+        image: mongo
+        ports:
+          - 27017:27017
+      mysql:
+        # The default authentication used in MySQL 8.0 isn't supported by the
+        # mysql npm package: https://github.com/mysqljs/mysql/issues/2002
+        image: mariadb
+        ports:
+          - 3306:3306
+        env:
+          MYSQL_ROOT_PASSWORD: password
+          MYSQL_USER: ueberdb
+          MYSQL_PASSWORD: ueberdb
+          MYSQL_DATABASE: ueberdb
+      postgres:
+        image: postgres
+        ports:
+          - 5432:5432
+        env:
+          POSTGRES_USER: ueberdb
+          POSTGRES_PASSWORD: ueberdb
+          POSTGRES_DB: ueberdb
+        options: >-
+          --health-cmd="pg_isready -d postgresql://ueberdb:ueberdb@127.0.0.1/ueberdb"
+          --health-interval=10s
+          --health-timeout=5s
+          --health-retries=5
+      redis:
+        image: redis
+        ports:
+          - 6379:6379
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 12
+      - run: npm ci
+      # Optional dependencies must be installed manually.
+      - run: npm i sqlite3
+
+      # Verify databases are reachable.
+      - name: MySQL client and server check
+        run: |
+          mysql --version &&
+          mysql -h 127.0.0.1 -u ueberdb -pueberdb -e "SHOW TABLES;" ueberdb
+      - name: PostgreSQL client and server check
+        run: |
+          psql --version &&
+          psql -d postgresql://ueberdb:ueberdb@127.0.0.1/ueberdb -c '\dt'
+
+      - run: npm test
+      - run: npm run lint
+
+  publish-npm:
+    if: github.event_name == 'push'
+    needs: test
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v1
+        with:
+          node-version: 12
+          registry-url: https://registry.npmjs.org/
+      - run: git config user.name 'github-actions[bot]'
+      - run: git config user.email '41898282+github-actions[bot]@users.noreply.github.com'
+      - run: npm ci
+      - run: npm version patch
+      - run: git push --follow-tags
+      # `npm publish` must come after `git push` otherwise there is a race
+      # condition: If two PRs are merged back-to-back then master/main will be
+      # updated with the commits from the second PR before the first PR's
+      # workflow has a chance to push the commit generated by `npm version
+      # patch`. This causes the first PR's `git push` step to fail after the
+      # package has already been published, which in turn will cause all future
+      # workflow runs to fail because they will all attempt to use the same
+      # already-used version number. By running `npm publish` after `git push`,
+      # back-to-back merges will cause the first merge's workflow to fail but
+      # the second's will succeed.
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}

package/.travis.yml

@@ -0,0 +1,46 @@
+language: node_js
+
+node_js:
+  - 14
+
+services:
+  - docker
+  - mysql
+  - postgresql
+  - couchdb
+  - sqlite3
+  - redis
+  - cassandra
+  - elasticsearch
+  - mongodb
+  - rethinkdb
+
+before_install:
+  - mysql -e 'CREATE DATABASE ueberdb;'
+  - mysql -e 'CREATE USER "ueberdb"@"localhost" identified by "ueberdb";'
+  - mysql -e "ALTER DATABASE ueberdb CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;"
+  - mysql -e "grant CREATE,ALTER,SELECT,INSERT,UPDATE,DELETE on ueberdb.* to 'ueberdb'@'localhost';"
+  - mysql -e "CREATE TABLE \`store\` (\`key\` varchar(100) COLLATE utf8mb4_bin NOT NULL DEFAULT '',\`value\` longtext COLLATE utf8mb4_bin NOT NULL,PRIMARY KEY (\`key\`)) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin;" ueberdb
+#  - cp /etc/rethinkdb/default.conf.sample /etc/rethinkdb/instances.d/instance1.conf
+
+#addons:
+#  rethinkdb: '2.3.4'
+
+# Brings in procedure required for creating large data set
+  - mysql ueberdb < test/lib/mysql.sql
+  - mysql ueberdb -e 'CALL generate_data();';
+  - psql -c 'create database ueberdb;' -U postgres
+#  - psql -c "grant CREATE,ALTER,SELECT,INSERT,UPDATE,DELETE on ueberdb.* to 'ueberdb'@'localhost';" -U postgres
+
+install:
+  - "export GIT_HASH=$(git rev-parse --verify --short HEAD)"
+
+jobs:
+  include:
+    - name: "Run the Backend tests"
+      install:
+        - "npm install"
+
+notifications:
+  email:
+    - john@mclear.co.uk

package/CHANGELOG.md

@@ -0,0 +1,167 @@
+# Notable Changes
+
+## v1.4.16
+
+* `postgres`: You can now provide a connection string instead of a settings
+  object. For example:
+  ```javascript
+  const db = new ueberdb.Database('postgres', 'postgres://user:password@host/dbname');
+  ```
+
+## v1.4.15
+
+* `postgres`, `postgrespool`: The `postgrespool` database driver was renamed to
+  `postgres`, replacing the old `postgres` driver. The old `postgrespool` name
+  is still usable, but is deprecated. For users of the old `postgres` driver,
+  this change increases the number of concurrent database connections. You may
+  need to increase your configured connection limit.
+* `sqlite`: Updated `sqlite3` to 5.0.2.
+
+## v1.4.14
+
+Updated dependencies:
+* `cassandra`: Updated `cassandra-driver` to 4.6.3.
+* `couch`: Updated `nano` to 9.0.3.
+* `dirty`: Updated `dirty` to 1.1.3.
+* `dirty_git`: Updated `simple-git` to 2.45.0.
+* `mongodb`: Updated `mongodb` to 3.6.11.
+* `mssql`: Updated `mssql` to 7.2.1.
+* `postgres`, `postgrespool`: Updated `pg` to 8.7.1.
+
+## v1.4.13
+
+* `mongodb`: The `dbName` setting has been renamed to `database` for consistency
+  with other database drivers. The `dbName` setting will continue to work (for
+  backwards compatibility), but it is deprecated and is ignored if `database` is
+  set.
+* `mongodb`: The `database` (formerly `dbName`) setting is now optional. If it
+  is not specified, the database name embedded in the `url` setting is used.
+
+## v1.4.8
+
+* `redis`: Updated `redis` dependency to 3.1.2.
+
+## v1.4.7
+
+* Each write operation in a bulk write batch is now retried if the bulk write
+  fails.
+* Fixed write metrics for `setSub()` read failures.
+
+## v1.4.6
+
+* `mysql`: Use a connection pool to improve performance and simplify the code.
+
+## v1.4.5
+
+* `mysql`: Reconnect on fatal error.
+* `mysql`: Log MySQL errors.
+
+## v1.4.4
+
+* New experimental setting to limit the number of operations written at a time
+  when flushing outstanding writes.
+* `mysql`: Bulk writes are limited to 100 changes at a time to avoid query
+  timeouts.
+* `mysql`: Raised default cache size from 500 entries to 10000.
+
+## v1.4.2
+
+* Refined the experimental read and write metrics.
+
+## v1.4.1
+
+* The two callback arguments in `remove()`, `set()`, and `setSub()` have
+  changed: Instead of a callback that is called after the write is buffered and
+  another callback that is called after the write is committed, both callbacks
+  are now called after the write is committed. Futhermore, the second callback
+  argument is now deprecated.
+* Modernized record locking.
+* Experimental metrics for reads, writes, and locking.
+
+## v1.3.2
+
+* `dirty`: Updated `dirty` dependency.
+
+## v1.3.1
+
+* `redis`: The database config object is now passed directly to the `redis`
+  package. For details, see
+  https://www.npmjs.com/package/redis/v/3.0.2#options-object-properties.
+  Old-style settings objects (where the `redis` options are in the
+  `client_options` property) are still supported but deprecated.
+
+## v1.2.9
+
+* `dirty`: Workaround for a bug in the upstream `dirty` driver.
+
+## v1.2.7
+
+* `redis`: Experimental support for passing the settings object directly to the
+  `redis` package.
+
+## v1.2.6
+
+* `redis`: Fixed "Callback was already called" exception during init.
+
+## v1.2.5
+
+* All: Fixed a major bug introduced in v1.1.10 that caused `setSub()` to
+  silently discard changes.
+* All: Fixed a bug that prevented cache entries from being marked as most
+  recently used.
+
+## v1.2.4
+
+* `mssql`: Updated `mssql` dependency.
+* `dirty_git`: Updated `simple-git` dependency.
+* `sqlite`: Updated `sqlite3` dependency.
+
+## v1.2.3
+
+* `mssql`: Updated `mssql` dependency.
+
+## v1.2.2
+
+* All: Fixed minor `setSub()` corner cases.
+
+## v1.2.1
+
+* New `flush()` method.
+* The `doShutdown()` method is deprecated. Use `flush()` instead.
+* The `close()` method now flushes unwritten entries before closing the database
+  connection.
+* Bug fix: `null`/`undefined` is no longer cached if there is an error reading
+  from the database.
+
+## v1.1.10
+
+* Major performance improvement: The caching logic was rewritten with much more
+  efficient algorithms. Also: Scans for entries to evict is performed less
+  often. Depending on your workload you might observe a slight memory usage
+  increase.
+
+## v1.1.7
+
+* `mysql` dependency bumped to 7.0.0-alpha4 to avoid a security vulnerability in
+  one of its indirect dependencies.
+
+## v1.1.6
+
+* Bug fix: When write buffering is disabled, reads of keys with values that were
+  changed but not yet written to the underlying database used to return the
+  previous value. Now the updated value is returned.
+* Minor performance improvement: Setting a key to the same value no longer
+  triggers a database write.
+
+## v1.1.5
+
+* Minor performance improvement: Debug log message strings are no longer
+  generated if debug logging is not enabled.
+
+## v1.1.1
+
+* The `database()` constructor is deprecated; use `Database()` instead.
+
+## Older
+
+See the Git history.

package/CONTRIBUTING.md

@@ -0,0 +1,103 @@
+# Contributor Guidelines
+(Please talk to people on the mailing list before you change this page, see our section on [how to get in touch](https://github.com/ether/etherpad-lite#get-in-touch))
+
+## Pull requests
+
+* the commit series in the PR should be _linear_ (it **should not contain merge commits**). This is necessary because we want to be able to [bisect](https://en.wikipedia.org/wiki/Bisection_(software_engineering)) bugs easily. Rewrite history/perform a rebase if necessary
+* PRs should be issued against the **develop** branch: we never pull directly into **master**
+* PRs **should not have conflicts** with develop. If there are, please resolve them rebasing and force-pushing
+* when preparing your PR, please make sure that you have included the relevant **changes to the documentation** (preferably with usage examples)
+* contain meaningful and detailed **commit messages** in the form:
+  ```
+  submodule: description
+
+  longer description of the change you have made, eventually mentioning the
+  number of the issue that is being fixed, in the form: Fixes #someIssueNumber
+  ```
+* if the PR is a **bug fix**:
+  * the first commit in the series must be a test that shows the failure
+  * subsequent commits will fix the bug and make the test pass
+  * the final commit message should include the text `Fixes: #xxx` to link it to its bug report
+* think about stability: code has to be backwards compatible as much as possible. Always **assume your code will be run with an older version of the DB/config file**
+* if you want to remove a feature, **deprecate it instead**:
+  * write an issue with your deprecation plan
+  * output a `WARN` in the log informing that the feature is going to be removed
+  * remove the feature in the next version
+* if you want to add a new feature, put it under a **feature flag**:
+  * once the new feature has reached a minimal level of stability, do a PR for it, so it can be integrated early
+  * expose a mechanism for enabling/disabling the feature
+  * the new feature should be **disabled** by default. With the feature disabled, the code path should be exactly the same as before your contribution. This is a __necessary condition__ for early integration
+* think of the PR not as something that __you wrote__, but as something that __someone else is going to read__. The commit series in the PR should tell a novice developer the story of your thoughts when developing it
+
+## How to write a bug report
+
+* Please be polite, we all are humans and problems can occur.
+* Please add as much information as possible, for example
+  * client os(s) and version(s)
+    * browser(s) and version(s), is the problem reproducible on different clients
+    * special environments like firewalls or antivirus
+  * host os and version
+    * npm and nodejs version
+    * Logfiles if available
+  * steps to reproduce
+  * what you expected to happen
+  * what actually happened
+* Please format logfiles and code examples with markdown see github Markdown help below the issue textarea for more information.
+
+## General goals of UeberDB
+To make sure everybody is going in the same direction:
+* easy to install for admins and easy to use for people
+* easy to integrate into other apps, but also usable as standalone
+* lightweight and scalable
+* extensible, as much functionality should be extendable with plugins so changes don't have to be done in core.
+
+## How to work with git?
+* Don't work in your master branch.
+* Make a new branch for every feature you're working on. (This ensures that you can work you can do lots of small, independent pull requests instead of one big one with complete different features)
+* Don't use the online edit function of github (this only creates ugly and not working commits!)
+* Try to make clean commits that are easy readable (including descriptive commit messages!)
+* Test before you push. Sounds easy, it isn't!
+* Don't check in stuff that gets generated during build or runtime
+* Make small pull requests that are easy to review but make sure they do add value by themselves / individually
+
+## Coding style
+* Do write comments. (You don't have to comment every line, but if you come up with something that's a bit complex/weird, just leave a comment. Bear in mind that you will probably leave the project at some point and that other people will read your code. Undocumented huge amounts of code are worthless!)
+* Never ever use tabs
+* Indentation: JS/CSS: 2 spaces; HTML: 4 spaces
+* Don't overengineer. Don't try to solve any possible problem in one step, but try to solve problems as easy as possible and improve the solution over time!
+* Do generalize sooner or later! (if an old solution, quickly hacked together, poses more problems than it solves today, refactor it!)
+* Keep it compatible. Do not introduce changes to the public API, db schema or configurations too lightly. Don't make incompatible changes without good reasons!
+* If you do make changes, document them! (see below)
+* Use protocol independent urls "//"
+
+## Branching model / git workflow
+see git flow http://nvie.com/posts/a-successful-git-branching-model/
+
+### `master` branch
+* the stable
+* This is the branch everyone should use for production stuff
+
+### feature branches (in your own repos)
+* these are the branches where you develop your features in
+* If it's ready to go out, it will be merged into develop
+
+Over the time we pull features from feature branches into the develop branch. Every month we pull from develop into master. Bugs in master get fixed in hotfix branches. These branches will get merged into master AND develop. There should never be commits in master that aren't in develop
+
+## Testing
+Front-end tests are found in the `tests/frontend/` folder in the repository. Run them by pointing your browser to `<yourdomainhere>/tests/frontend`.
+
+Back-end tests can be run via `npm test`.
+
+## Things you can help with
+The Etherpad Foundation is much more than software.  So if you aren't a developer then worry not, there is still a LOT you can do!  A big part of what we do is community engagement.  You can help in the following ways
+ * Triage bugs (applying labels) and confirming their existence
+ * Testing fixes (simply applying them and seeing if it fixes your issue or not) - Some git experience required
+ * Notifying large site admins of new releases
+ * Writing Changelogs for releases
+ * Creating Windows packages
+ * Creating releases
+ * Bumping dependencies periodically and checking they don't break anything
+ * Write proposals for grants
+ * Co-Author and Publish CVEs
+ * Work with SFC to maintain legal side of project
+

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2020 The Etherpad Foundation
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.