This repository has been archived by the owner on May 1, 2023. It is now read-only.
Releases: facebookarchive/profilo
Releases · facebookarchive/profilo
release-8e1e759c: Catch Java unwinder compatibility check errors
Reviewed By: simpleton Differential Revision: D37568744 fbshipit-source-id: e667bb9b4523b51349d89fcb6bc9b8885a10059e
release-8c4701b6: Bump numpy from 1.21.0 to 1.22.0 in /python (#113)
Summary: Bumps [numpy](https://github.com/numpy/numpy) from 1.21.0 to 1.22.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/numpy/numpy/releases">numpy's releases</a>.</em></p> <blockquote> <h2>v1.22.0</h2> <h1>NumPy 1.22.0 Release Notes</h1> <p>NumPy 1.22.0 is a big release featuring the work of 153 contributors spread over 609 pull requests. There have been many improvements, highlights are:</p> <ul> <li>Annotations of the main namespace are essentially complete. Upstream is a moving target, so there will likely be further improvements, but the major work is done. This is probably the most user visible enhancement in this release.</li> <li>A preliminary version of the proposed Array-API is provided. This is a step in creating a standard collection of functions that can be used across application such as CuPy and JAX.</li> <li>NumPy now has a DLPack backend. DLPack provides a common interchange format for array (tensor) data.</li> <li>New methods for <code>quantile</code>, <code>percentile</code>, and related functions. The new methods provide a complete set of the methods commonly found in the literature.</li> <li>A new configurable allocator for use by downstream projects.</li> </ul> <p>These are in addition to the ongoing work to provide SIMD support for commonly used functions, improvements to F2PY, and better documentation.</p> <p>The Python versions supported in this release are 3.8-3.10, Python 3.7 has been dropped. Note that 32 bit wheels are only provided for Python 3.8 and 3.9 on Windows, all other wheels are 64 bits on account of Ubuntu, Fedora, and other Linux distributions dropping 32 bit support. All 64 bit wheels are also linked with 64 bit integer OpenBLAS, which should fix the occasional problems encountered by folks using truly huge arrays.</p> <h2>Expired deprecations</h2> <h3>Deprecated numeric style dtype strings have been removed</h3> <p>Using the strings <code>"Bytes0"</code>, <code>"Datetime64"</code>, <code>"Str0"</code>, <code>"Uint32"</code>, and <code>"Uint64"</code> as a dtype will now raise a <code>TypeError</code>.</p> <p>(<a href="https://github-redirect.dependabot.com/numpy/numpy/pull/19539">gh-19539</a>)</p> <h3>Expired deprecations for <code>loads</code>, <code>ndfromtxt</code>, and <code>mafromtxt</code> in npyio</h3> <p><code>numpy.loads</code> was deprecated in v1.15, with the recommendation that users use <code>pickle.loads</code> instead. <code>ndfromtxt</code> and <code>mafromtxt</code> were both deprecated in v1.17 - users should use <code>numpy.genfromtxt</code> instead with the appropriate value for the <code>usemask</code> parameter.</p> <p>(<a href="https://github-redirect.dependabot.com/numpy/numpy/pull/19615">gh-19615</a>)</p> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/numpy/numpy/commit/4adc87dff15a247e417d50f10cc4def8e1c17a03"><code>4adc87d</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/numpy/numpy/issues/20685">#20685</a> from charris/prepare-for-1.22.0-release</li> <li><a href="https://github.com/numpy/numpy/commit/fd66547557f57c430d41be2fc0764f74a62e8ccf"><code>fd66547</code></a> REL: Prepare for the NumPy 1.22.0 release.</li> <li><a href="https://github.com/numpy/numpy/commit/125304b035effcd82e366e601b102e7347eaa9ba"><code>125304b</code></a> wip</li> <li><a href="https://github.com/numpy/numpy/commit/c283859128b1a4b57014581570a23ed7950a24ea"><code>c283859</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/numpy/numpy/issues/20682">#20682</a> from charris/backport-20416</li> <li><a href="https://github.com/numpy/numpy/commit/5399c03d4a069fe81a1616be0184c9749d7271ee"><code>5399c03</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/numpy/numpy/issues/20681">#20681</a> from charris/backport-20954</li> <li><a href="https://github.com/numpy/numpy/commit/f9c45f8ebf31340b1a5a0371bfca25afcfc4794e"><code>f9c45f8</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/numpy/numpy/issues/20680">#20680</a> from charris/backport-20663</li> <li><a href="https://github.com/numpy/numpy/commit/794b36f7e1bf2a8c42774ab0db86a74bd32f674b"><code>794b36f</code></a> Update armccompiler.py</li> <li><a href="https://github.com/numpy/numpy/commit/d93b14e3d7abaa1d837825e51671f817788e120f"><code>d93b14e</code></a> Update test_public_api.py</li> <li><a href="https://github.com/numpy/numpy/commit/7662c0789cc6a70d5ad4d950ee2e95f3afef7df6"><code>7662c07</code></a> Update <strong>init</strong>.py</li> <li><a href="https://github.com/numpy/numpy/commit/311ab52488a7d096ac3bc4c2de0fdae17ecd13ef"><code>311ab52</code></a> Update armccompiler.py</li> <li>Additional commits viewable in <a href="https://github.com/numpy/numpy/compare/v1.21.0...v1.22.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `dependabot rebase` will rebase this PR - `dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `dependabot merge` will merge this PR after your CI passes on it - `dependabot squash and merge` will squash and merge this PR after your CI passes on it - `dependabot cancel merge` will cancel a previously requested merge and block automerging - `dependabot reopen` will reopen this PR if it is closed - `dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/facebookincubator/profilo/network/alerts). </details> Pull Request resolved: https://github.com/facebookincubator/profilo/pull/113 Reviewed By: simpleton Differential Revision: D37343506 Pulled By: yukonfb fbshipit-source-id: 676240d96e2b6a429efc121626b7620ba96e2032
release-f559bf41: Folder cleanup on trace completion
Summary: When a trace folder contains only a single trace file (most cases), that folder won't be deleted upon processing for the successful case. This change ensures proper trace folder deletion for all cases. Reviewed By: simpleton Differential Revision: D37470334 fbshipit-source-id: 07c37792198e3432a6e12e2ebebbc840802e8c22
release-5d3bc457: Back out "Temporarily disable stack traces for libc++ arm64"
Summary: As with all temporary solutions, this turned out to be a lot less temporary than I was hoping for :D I was never able to figure out the original issue, but I tried again after switching unwinders from libgcc to libunwind. Unfortunately that ran into new crashes so I had to revert it again. I fixed the underlying issue in LLVM's libunwind in https://reviews.llvm.org/D126343, so let's try this again and see what happens. Reviewed By: simpleton Differential Revision: D37181295 fbshipit-source-id: bb4ca5c8e525e8deab3fa43b8be78120b477ffed
release-909e42df: Backport a fix to C++20 partial specialization issue
Summary: Backport a fix to https://github.com/fmtlib/fmt/issues/2769. Reviewed By: aandreyeu Differential Revision: D37077479 fbshipit-source-id: 6f9d716c47784717c4aa36eba89498639eb3503a
release-485398db: Trigger config Id migration support
Reviewed By: yukonfb Differential Revision: D36331575 fbshipit-source-id: a2b18fe44449ef27a9c94ee746b478b8189181f7
release-67c41c47: Reversible Trace ID sanitization
Summary: # Problem Description Loom uses base64 encoding for the string representation of Trace IDs. The base64 alphabet uses `+` and `/` characters in addition to alphanumeric characters. Trace file names contain Trace IDs, and in order it to be valid filenames, Trace IDs are sanitized to replace unsupported characters. The current approach is replacing both `+` and `/` with an underscore (`_`). This transformation makes it impossible to reconstruct the actual Trace ID from the filename, which could be useful in situations where we need to access the Trace ID without parsing the trace file contents (on either client or server). # Change Description With this change, the sanitization function becomes reversible, by having it replace `+` with `_p_` and `/` with `_s_`. Reviewed By: aandreyeu Differential Revision: D36764316 fbshipit-source-id: 744ac37fe6c190436a2445170fac6d1003b3b2f1
release-cc50c61a: Assign the right oncall to profilo tests
Summary: We try to remove the use test_ownership_2020 oncall, which was created to enforce oncall field in test module. This diff stack tries its best to guess who the right oncall is for these "unowned" tests. If you don't think this belongs to you, please 1. Either re-assign to another team to your best knowledge 2. Or delete the test Every test should have an owner! (Note: this ignores all push blocking failures!) Reviewed By: jiawei-lyu Differential Revision: D36434525 fbshipit-source-id: c2eed95531670b7e5026c233b8a045d37a122aa6
release-256981b1: Delete all files under managed paths on cleanup
Reviewed By: yukonfb Differential Revision: D36265084 fbshipit-source-id: 0f026c0adab6e250bc25e6acc62e502251c1da75
release-d55c0c7d: apply import merging for . (1 of 1)
Summary: Applies new import merging and sorting from µsort v1.0. When merging imports, µsort will make a best-effort to move associated comments to match merged elements, but there are known limitations due to the diynamic nature of Python and developer tooling. These changes should not produce any dangerous runtime changes, but may require touch-ups to satisfy linters and other tooling. Note that µsort uses case-insensitive, lexicographical sorting, which results in a different ordering compared to isort. This provides a more consistent sorting order, matching the case-insensitive order used when sorting import statements by module name, and ensures that "frog", "FROG", and "Frog" always sort next to each other. For details on µsort's sorting and merging semantics, see the user guide: https://usort.readthedocs.io/en/stable/guide.html#sorting Reviewed By: lisroach Differential Revision: D36402269 fbshipit-source-id: fa77bafb09e935a0a21065dbc23d66c325b271c2