Bug: Incorrect formatting when using \left\{ and \right. causing unexpected tabbing issues

It appears that tex-fmt has an issue when handling the combination of \left\{ and \right.. When these are used together in a math environment, the formatter fails to correctly recognize the environment closure. This results in unexpected additional tabs in subsequent lines of the document.
This issue is particularly problematic in documents with multiple occurrences of this pattern, as the incorrect tabbing propagates, making the document increasingly misaligned and harder to read.
Using the following minimal working example (MWE), the issue can be reproduced:
\[
    f(x) =
    \left\{
        \begin{aligned}
            & g(x), & & \text{if } x \geq 0, \\
            & h(x), & & \text{otherwise.}
        \end{aligned}
    \right.
\]
xyz abc xyz ...

After formatting this code with tex-fmt, the last two lines inside the aligned environment are incorrectly indented. Furthermore, all subsequent content in the document is shifted to the right by an additional tab.
\[
    f(x) =
    \left\{
        \begin{aligned}
            & g(x), & & \text{if } x \geq 0, \\
            & h(x), & & \text{otherwise.}
        \end{aligned}
        \right.
    \]
    xyz abc xyz ...

Changing \right. to \right\} resolves the tabbing issue, confirming that the problem lies in the formatter's failure to recognize the closure of \left when paired with \right.. The formatter should properly interpret \left\{ and \right. as a valid delimiter pair, which is a legitimate LaTeX syntax, ensuring that the subsequent lines are not misaligned.
This bug is particularly disruptive in documents with multiple instances of \left\{ ... \right., as the issue compounds with each occurrence, requiring extensive manual intervention to fix. Thank you for investigating this issue and improving the usability of tex-fmt!

Hi @cdesaintguilhem,
Thank you for taking the time to respond and for considering looking into this unintended behavior. I really appreciate your efforts in maintaining tex-fmt.
You are absolutely correct that the cases environment would be a more natural way to format the example I provided. However, the purpose of my example was not to recommend the use of \left\{ and \right. in such simple cases, but rather to demonstrate an edge case where tex-fmt fails to properly handle valid LaTeX delimiter pairs. In more complex mathematical scenarios, the use of \left\{ and \right. (or other similar delimiter pairs) is quite common, especially when combined with nested or invisible delimiters.  The issue here is not about promoting a specific style but showcasing a limitation in tex-fmt's current parsing logic, which could cause significant formatting issues in such cases. I believe addressing this could improve the robustness of tex-fmt when dealing with valid LaTeX syntax, even in edge cases.
Thank you again for considering this, and please let me know if I can provide further examples or clarify anything further.

Thanks for this discussion; this is an interesting case. I see the argument for expecting \right. to match its preceding \left\{, for example, but is this definitely what we want? I can also envision scenarios in which the current behaviour is actually preferable. For example, consider
\left\{
\right.
\left.
\right\}

Here it might be clearer to have the \left\{ match to \right\} rather than to the internal "delimiters".

Here it might be clearer to have the \left\{ match to \right\} rather than to the internal "delimiters".

Well, maybe it makes no difference to match { } or { . + . }? I think the following is still acceptable.
\left\{
  …
\right.
\left.
  …
\right\}

Besides, LaTeX Workshop in VS Code just matches { . + . }.
https://github.com/James-Yu/LaTeX-Workshop/pull/2503


Nifticlib 2023 03 29

This updates nifti to the current upstream master.

@hjmjohnson @dzenanz this gets various fixes from upstream nifti.


Rewriting Hashes in replaceDependency should prefer to run locally.

Currently when distributed builds enabled each derivation is uploaded to the remote server to have their hashes rewritten.
Within pkgs/build-support/replace-dependency.nix the 'replaceHashes; derivation should be marked in such a way so that the replacement is done locally for those people who have enabled distributed builds.  I believe there is a simple way to do this, but I need to look up how it is done.
@shlevy I've assigned myself this issue, but you might also be interested in fixing it.

preferLocalBuild = true, I suppose.

(triage) @roconnor , any update on this ? Have you fixed it ?

Are there any updates to this issue, please?

https://github.com/NixOS/nixpkgs/pull/218984


implement ancestry hash

change hash of a prepare/commit to a fixed ancestry hash paired with each epoch.
made a description picture here: https://github.com/NIC619/documents/blob/master/PoS/Capser Contract/Prepare_Commit/example_ancestry_hash.jpg
this builds on previous PR of fixing tester and implementing event log

Old PR still referencing prepare/commit.
Should be closed.
@karlfloersch @ChihChengLiang

Closing!


Install fails with memory error

Trying to install anywhere on fresh octoprint .14 on rpi zero wireless

Another user has reported a similar problem. He found out that the problem seems to be caused by pip version 9.0.1.
If you have upgraded pip to 9.0.1, you can downgrade it to 8.1.1 by the command pip install pip==8.1.1. Then you can try to install OctoPrint Anywhere again. Let me know if it solves your problem @theisgroup

here is what i get after i downgrade to pip 8.1.1
Error!
Could not parse output from pip, see plugin_pluginmanager_console.log for generated output

i ssh into the pi and ran the install and it looks like that worked. i will check it once this print is complete.

Great. Meanwhile I will try to reproduce the problem on my Pi zero to see if I can come up with a permanent solution.

@theisgroup I released a new version yesterday so that the installation would succeed even under pip 9.0.1.

i just flashed a second pi zero w with octoprint 0.14 and the plugin installed from plugin manager.


Request Tab"Code" file sort by date modified

Description
Request Tab"Code" file sort by date modified

Example URLs
https://github.com/refined-github/refined-github/

The issue is where to put yet another button/dropdown.
If you just want a quick run, this sorts from newest from oldest:
files = document.querySelector('[aria-labelledby="folders-and-files"] tbody')
children = [...files.children]
files.replaceChildren(
    children[0],
    ...[...files.querySelectorAll('[aria-labelledby="folders-and-files"] .react-directory-row')].sort((a, b) =>
        new Date(a.querySelector('relative-time').datetime) < new Date(b.querySelector('relative-time').datetime) ? 1 : -1
    ),
    children.at(-1),
)

The issue is where to put yet another button/dropdown.
If you just want a quick run, this sorts from newest from oldest:
files = document.querySelector('[aria-labelledby="folders-and-files"] tbody')
children = [...files.children]
files.replaceChildren(
    children[0],
    ...[...files.querySelectorAll('.react-directory-row')].sort((a, b) =>
        new Date(a.querySelector('relative-time').datetime) < new Date(b.querySelector('relative-time').datetime) ? 1 : -1
    ),
    children.at(-1),
)

Wow Thanks...
run it in Chrome(safari) console? how to do it ?

Yep, paste the code in DevTools console and run.

Yep, paste the code in DevTools console and run.

not work

You probably need to enable the "New Repository Overview" feature preview (in your profile menu), old DOM could be different (and I don't have interest in that).
Anyway this is going a little off-topic. Personally I would like some sort of sorting, it's just... too big of a feature.

You probably need to enable the "New Repository Overview" feature preview (in your profile menu), old DOM could be different (and I don't have interest in that).
Anyway this is going a little off-topic. Personally I would like some sort of sorting, it's just... too big of a feature.

Thanks，work！hope to add this feature to refined-github

The issue is where to put yet another button/dropdown in a already crowded space.
If you just want a quick run, this sorts from newest from oldest:
files = document.querySelector('[aria-labelledby="folders-and-files"] tbody')
children = [...files.children]
files.replaceChildren(
    children[0],
    ...[...files.querySelectorAll('.react-directory-row')].sort((a, b) =>
        new Date(a.querySelector('relative-time').datetime) < new Date(b.querySelector('relative-time').datetime) ? 1 : -1
    ),
    children.at(-1),
)

please add the  feature to the project.thanks

This can be its own feature: sort by date, commit, name, etc. not in Refined GitHub.
Refined GitHub does already highlight recent files so if you want to see recent changes you already can

This can be its own feature: sort by date, commit, name, etc. not in Refined GitHub.
Refined GitHub does already highlight recent files so if you want to see recent changes you already can

Thanks


feat: fuzzy matching completions

Closes #601
What are the key elements of this solution?

I am implementing fuzzy matching for auto completions. The two main cases that I focused on were typos and partial matches.

Typos: Since right now a substring prefix is required, any typo prevents suggestions from being displayed ("slect" will not suggest "select"), this PR adds support for that.
Partial matches: Since right now startswith is used, if I have a column named "team_sales", typing "sales" is not a match, since it does not share a prefix. This adds support for it.

Why did you design your solution this way? Did you assess any alternatives? Are there tradeoffs?

Some discussion here: https://github.com/tconbeer/harlequin/issues/601#issuecomment-2342392559
I also tested various alternatives using a harnessed snippet with the completions for a local database, where I modified the number of possible characters and 2 was a good tradeoff between the worst case scenario performance and real world use.
Time to generate a completion in my laptop+database is still in the microsecond range but it does seem to be 3/4 times slower in the worst case scenarios.

Does this PR require a change to Harlequin's docs?

[x] No.
[ ] Yes, and I have opened a PR at tconbeer/harlequin-web.
[ ] Yes; I haven't opened a PR, but the gist of the change is: ...

Did you add or update tests for this change?

[ ] Yes.
[x] No, I believe tests aren't necessary.

NOTE: Since the current implementation of the matching is not tested I didn't add it. Let me know if you think its needed and I would be happy to write it.

[ ] No, I need help with testing this change.

Please complete the following checklist:

[x] I have added an entry to CHANGELOG.md, under the [Unreleased] section heading. That entry references the issue closed by this PR.
[x] I acknowledge Harlequin's MIT license. I do not own my contribution.

Hummm oddly enough the tests hang forever after merging main. I was able to run them before the update.

Well in despite the tests being broken for me RN ...

I think to address that, fuzzy matches should be ordered better -- right now they are listed alphabetically; would be good to order fuzzy matches by edit distance, or order all matches by:
exact matches first
startswith matches
fuzzy matches last (ordered ideally by edit distance or some heuristic or maybe just alphabetically)
A final optimization related to the ordering -- it might make sense to only compute fuzzy > matches if the length of the list of exact and startswith matches is below some threshold. i.e., no reason to fuzzy match on a single character input that already returns dozens of results.

I implemented this idea with some minor variations ... I is Exact > starswith > fuzzy and I am sorting the fuzzy matches by length. This results in "more fuzzy" matches generally going last (which I feel is a good approximation). I am also skipping the fuzzy matching if there are already more than 20 direct matches.
Also took the freedom to add an unit test for it. I bundled the completions from a dummy database with just the 'iris' dataset added to it and stored the HarlequinCompletions as json, my only reservation on that is that it is a large-ish file and re-generating it entails some source code hooking/monkeypatching which I have not included in the PR.
LMK what you think and if you have any ideas on how to fix the testing issue.
Full traceback after killing a pytest session python -m pytest --full-trace tests/functional_tests/test_app.py (sorry, my python async is not great so I am having a hard time debugging this one ...)

=================================== test session starts ===================================
platform darwin -- Python 3.12.6, pytest-8.3.2, pluggy-1.5.0
rootdir: /Users/myuser/git/harlequin
configfile: pyproject.toml
plugins: syrupy-4.6.1, asyncio-0.21.2, textual-snapshot-0.4.0
asyncio: mode=Mode.STRICT
collected 49 items

tests/functional_tests/test_app.py ^C

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

        Only accepts keyword arguments, which should match the hook
        specification.

        Returns the result(s) of calling all registered plugins, see
        :ref:`calling`.
        """
        assert (
            not self.is_historic()
        ), "Cannot directly call a historic hook - use call_historic instead."

        Only accepts keyword arguments, which should match the hook
        specification.

        Returns the result(s) of calling all registered plugins, see
        :ref:`calling`.
        """
        assert (
            not self.is_historic()
        ), "Cannot directly call a historic hook - use call_historic instead."

        The rewrite module will use util._reprcompare if it exists to use custom
        reporting via the pytest_assertrepr_compare hook.  This sets up this custom
        comparison for the test.
        """
        ihook = item.ihook

        def callbinrepr(op, left: object, right: object) -> str | None:
            """Call the pytest_assertrepr_compare hook and prepare the result.

            This uses the first result from the hook and then ensures the
            following:
            * Overly verbose explanations are truncated unless configured otherwise
              (eg. if running in verbose mode).
            * Embedded newlines are escaped to help util.format_explanation()
              later.
            * If the rewrite mode is used embedded %-characters are replaced
              to protect later % formatting.

        Only accepts keyword arguments, which should match the hook
        specification.

        Returns the result(s) of calling all registered plugins, see
        :ref:`calling`.
        """
        assert (
            not self.is_historic()
        ), "Cannot directly call a historic hook - use call_historic instead."

        Only accepts keyword arguments, which should match the hook
        specification.

        Returns the result(s) of calling all registered plugins, see
        :ref:`calling`.
        """
        assert (
            not self.is_historic()
        ), "Cannot directly call a historic hook - use call_historic instead."
         "
                    "Please remove asyncio marker. "
                    "If the test is not marked explicitly, "
                    "check for global markers applied via 'pytestmark'."

        If the argument is a coroutine, it is wrapped in a Task.

        WARNING: It would be disastrous to call run_until_complete()
        with the same coroutine twice -- it would wrap it in two
        different Tasks and that can't be good.

         For consistent
        # behavior with the other selector classes, we prevent that here
        # (using max). See https://bugs.python.org/issue29255
        max_ev = self._max_events or 1
        ready = []
        try:
>           kev_list = self._selector.control(None, max_ev, timeout)
E           KeyboardInterrupt

<EMAIL_ADDRESS>n3.12/selectors.py:566: KeyboardInterrupt
================================= no tests ran in 29.92s ==================================

After nuking the env it works fine again!
571ad25 Adds the review suggestions and updates the .ambr files.
Trimmed the json ... left ~100 completions and pretty printed it.
Also noticed it now shows a "Tx: Auto" in several of the snapshots. Which I don't believe are related with my PR.

Thanks a lot for the feedback!

The Tx: Auto is added when using python 3.12+ with SQLite. For developing and testing I use 3.8 (soon 3.9)

the last few failures are from snapshots that aren't running on macs; I can help clean up those final snapshots in the next few days

Wohoo! Thank you very much for helping throughout the process (and for the amazing project)! It has been an absolute pleasure @tconbeer


vue-class-component didnt worked

Here is my vue component,
// src/components/Tabs.vue
<template>
  <nav class="tab-wrapper">
    <span
      v-for="(item, index) in options"
      :class="['tab-item', {'active' : active === index}]"
      :key="index"
      @click="changeIndex(index)"
    >{{item.title}}</span>
  </nav>
</template>
<script lang="ts">
import Vue from 'vue';
import Component from 'vue-class-component';

@Component({
  props: {
    options: Array,
    active: Number
  }
})
export default class Tabs extends Vue {
  options!: Array<{ title: string }>;
  active!: number;
  changeIndex(index: number) {
    this.$emit('onChangeIndex', index);
  }
}
</script>
<style lang="scss" scoped>
.tab-wrapper {
  font-size: 28px;
  display: flex;
  height: 99px;
  color: #aaaaaa;
  border-bottom: 1px solid rgba(0, 0, 0, 0.08);
  background: #ffffff;
  align-items: center;
  .tab-item {
    margin-right: 40px;
    &.active {
      position: relative;
      color: #323333;
    }
  }
}
</style>

I have installed 'storybook', and followed the guide
while I execute npm run storybook, terminal reported below text
ERROR in ./src/components/Tabs.vue?vue&type=script&lang=ts& (./node_modules/vue-loader/lib??vue-loader-options!./src/components/Tabs.vue?vue&type=script&lang=ts&) 15:0
Module parse failed: Unexpected character '@' (15:0)
You may need an appropriate loader to handle this file type.
| import Component from 'vue-class-component';
|
> @Component({
|   props: {
|     options: Array,
 @ ./src/components/Tabs.vue?vue&type=script&lang=ts& 1:0-119 1:135-138 1:140-256 1:140-256
 @ ./src/components/Tabs.vue
 @ ./stories/tabs.stories.js
 @ ./stories sync .stories.js$
 @ ./.storybook/config.js
 @ multi<EMAIL_ADDRESS><EMAIL_ADDRESS>./.storybook/config.js ./node_modules/webpack-hot-middleware/client.js?reload=true

ERROR in ./src/components/Tabs.vue?vue&type=style&index=0&id=bdda1ea4&lang=scss&scoped=true& (./node_modules/vue-loader/lib??vue-loader-options!./src/components/Tabs.vue?vue&type=style&index=0&id=bdda1ea4&lang=scss&scoped=true&) 32:0
Module parse failed: Unexpected token (32:0)
You may need an appropriate loader to handle this file type.
|
|
> .tab-wrapper {
|   font-size: 28px;
|
 @ ./src/components/Tabs.vue?vue&type=style&index=0&id=bdda1ea4&lang=scss&scoped=true& 1:0-152 1:168-171 1:173-322 1:173-322
 @ ./src/components/Tabs.vue
 @ ./stories/tabs.stories.js
 @ ./stories sync .stories.js$
 @ ./.storybook/config.js
 @ multi<EMAIL_ADDRESS><EMAIL_ADDRESS>./.storybook/config.js ./node_modules/webpack-hot-middleware/client.js?reload=true

My project use these dependencied
"vue": "^2.6.6",
 "vue-class-component": "^7.0.1",
 "vue-property-decorator": "^8.0.0",

I want to learn how to config to success,tks

@swust-xiaoj Did you figure out what's going on?
I'm running into the same problem after an upgrade, and it looks like it's specifically the Vue SFC <styles> section that is build system is getting hung up on.
Upgrade details
 @storybook/addon-a11y         ^5.0.0  →  ^5.0.5
 @storybook/addon-actions      ^5.0.0  →  ^5.0.5
 @storybook/addon-knobs        ^5.0.0  →  ^5.0.5
 @storybook/addon-links        ^5.0.0  →  ^5.0.5
 @storybook/addon-storysource  ^5.0.0  →  ^5.0.5
 @storybook/addons             ^5.0.0  →  ^5.0.5
 @storybook/vue                ^5.0.0  →  ^5.0.5
 storybook-readme              ^4.0.5  →  ^5.0.1

Error
ERROR in ./src/components/SbButton.vue?vue&type=style&index=0&lang=css& (./node_modules/vue-loader/lib??vue-loader-options!./src/components/SbButton.vue?vue&type=style&index=0&lang=css&) 52:0
Module parse failed: Unexpected token (52:0)
You may need an appropriate loader to handle this file type.
|
|
> .sb_button {
|   padding: 5px;
|   cursor: pointer;
 @ ./src/components/SbButton.vue?vue&type=style&index=0&lang=css& 1:0-131 1:147-150 1:152-280 1:152-280
 @ ./src/components/SbButton.vue
 @ ./stories/03_Components/SbButton.stories.js
 @ ./stories sync .stories.js$
 @ ./.storybook/config.js
 @ multi<EMAIL_ADDRESS><EMAIL_ADDRESS>./.storybook/config.js ./node_modules/webpack-hot-middleware/client.js?reload=true

I'm going to start working through individual updates to see if I can find change that caused this problem.  Unfortunately, I don't have a lot of time to dig into it, so if push comes to shove, I'll just have to downgrade us. 🙁 Hopefully I can at least narrow down the root problem. 🤞

seems like your webpack setup isnt quite right, i recommend using vue cli and vue-cli-plugin-storybook

@backbone87 - I won't garuntee that my webpack setup is correct (configs in general, and webpcak in particular, are my achille's heal) however  mine was working; it was a change during the upgrade process that broke it.
At this point, if i revert to my previous working version, then run the following upgrades:
yarn upgrade-interactive v1.13.0
info Color legend :
 "<red>"    : Major Update backward-incompatible updates
 "<yellow>" : Minor Update backward-compatible features
 "<green>"  : Patch Update backward-compatible bug fixes
? Choose which packages to update.
 devDependencies
   name                          range    from       to      url
 ◉ @babel/core                   ^7.3.4   7.3.4   ❯  7.4.0   https://babeljs.io/
 ◯ @storybook/addon-a11y         ^5.0.0   5.0.1   ❯  5.0.5   https://github.com/storybooks/storybook#readme
 ◯ @storybook/addon-actions      ^5.0.0   5.0.1   ❯  5.0.5   https://github.com/storybooks/storybook/tree/master/addons/actio
ns
 ◯ @storybook/addon-knobs        ^5.0.0   5.0.1   ❯  5.0.5   https://github.com/storybooks/storybook/tree/master/addons/knobs

 ◯ @storybook/addon-links        ^5.0.0   5.0.1   ❯  5.0.5   https://github.com/storybooks/storybook/tree/master/addons/links

 ◯ @storybook/addon-storysource  ^5.0.0   5.0.1   ❯  5.0.5   https://github.com/storybooks/storybook/tree/master/addons/story
source
 ◯ @storybook/addons             ^5.0.0   5.0.1   ❯  5.0.5   https://github.com/storybooks/storybook/tree/master/lib/addons
 ◯ @storybook/vue                ^5.0.0   5.0.1   ❯  5.0.5   https://github.com/storybooks/storybook/tree/master/app/vue
 ◉ @vue/cli-plugin-babel         ^3.4.0   3.5.0   ❯  3.5.1   https://github.com/vuejs/vue-cli/tree/dev/packages/@vue/cli-plug
in-babel#readme
 ◉ @vue/cli-plugin-e2e-cypress   ^3.4.0   3.5.0   ❯  3.5.1   https://github.com/vuejs/vue-cli/tree/dev/packages/@vue/cli-plug
in-e2e-cypress#readme
 ◉ @vue/cli-plugin-eslint        ^3.4.0   3.5.0   ❯  3.5.1   https://github.com/vuejs/vue-cli/tree/dev/packages/@vue/cli-plug
in-eslint#readme
 ◉ @vue/cli-plugin-unit-jest     ^3.4.0   3.5.0   ❯  3.5.1   https://github.com/vuejs/vue-cli/tree/dev/packages/@vue/cli-plug
in-unit-jest#readme
 ◉ @vue/cli-service              ^3.4.0   3.5.0   ❯  3.5.1   https://cli.vuejs.org/
 ◉ eslint                        ^5.8.0   5.15.1  ❯  5.15.3  https://eslint.org
 ◉ vue-template-compiler         ^2.5.21  2.6.8   ❯  2.6.10  https://github.com/vuejs/vue/tree/dev/packages/vue-template-comp
iler#readme

 dependencies
   name                          range    from       to      url
 ◉ @vue/cli                      ^3.4.1   3.5.0   ❯  3.5.1   https://cli.vuejs.org/
❯◉ vue                           ^2.6.6   2.6.8   ❯  2.6.10  https://github.com/vuejs/vue#readme

Everything continues to work just fine.
However, when I run the @storybook/vue upgrade:
@storybook/vue                ^5.0.0   5.0.1   ❯  5.0.5   https://github.com/storybooks/storybook/tree/master/app/vue

I get the error.
So, now I'm starting to dig into that ...

BREAKING changes were committed with "@storybook/vue": "5.0.2"
Apparently Storybook's own kitchen sink webpack examples for v5.0.0 & v5.0.1 were marked as deprecated but were still very much working and the demonstrated approach is still listed as an option in the custom-webpack-config Extend Mode documentation.
However, as of v5.0.2 the extend-mode/object syntax listed in https://storybook.js.org/docs/configurations/custom-webpack-config no longer works for at least some Vue configurations and the kitchen sink examples have been updated to the new function approach.
It appears that they should still be working and there is actually a console message notifying us of the deprecation.  However, the build broke for me and the console message was thoroughly buried under successful building step messages and then by the broken build messages, that I totally missed it.
FWIW: I based my own webpack.config.js off of that working vue-kitchen-sink example when I started my brand new project with v5.0.0!

that is really annoying, i recommend using full control mode only (since this is what will be the only option in the future, if i understood that correctly) or use the vue-cli-plugin-storybook

Yes, there was a bug in 5.0.0 which caused many peoples' webpack config to break migrating from 4.x. I fixed the bug in 5.0.2 and it caused some problems for anybody who used "extend mode" configuration in the 12 days between the 5.0.0 release and the 5.0.2 bugfix. To keep this from happening I deprecated extend-mode and will be removing it in a future version of Storybook. I also added a --debug-webpack flag so you can debug your custom configuration more easily.

is this actionable?

is this actionable?

I tried to update documentation to decrease the probability that someone else could run into this - https://github.com/storybooks/storybook/pull/6318
Based on @shilman's last comment, I'm not sure that there's much else that is actionable. 🤷♂

ok, so i gonna close it


Use dns_name instead of name for resource attribute

The name resource attribute overrides the original name given to the resource. There is a special name_attribute which should be used for this instead (and is used in this PR).
See: https://github.com/sethvargo/chefspec/issues/356#issuecomment-36004241

Due to lack of activity here I'm going to close this pull request. You are welcome to re-open it with a rebased branch to propose this merge again. Thank you once again for your submission @JeanMertz :heart:


Build Script

Should mention that it relies on svn to get apache sources on the readme

Yes, svn, findutils, grep and sed have to be available. Will push into readme.

i hate that i have to install svn just to contribute or use this lib. But its fine.

Well like half of repositories are available on ASF GIT ( https://git.apache.org/ ), but not all.
I have used the most official code source to be very clear about it.
You can still download the repositories as ZIPs for example and set env UPDATE_UPSTREAM to something else than 1 to not use SVN at all.

Well first release is out, see https://repo1.maven.org/maven2/cz/msebera/android/httpclient/4.3.3/
Gradle dependency tag is cz.msebera.android:httpclient:4.3.3


great addon but

i would love if you could add a toggle to completely disable the overlay

I put an option to turn the overlay off in v1.1.


[AIRFLOW-746] Connection refactoring

Add connection_types to handle plugin style connection adding
Dear Airflow Maintainers,
Please accept this PR that addresses the following issues:

https://issues.apache.org/jira/browse/AIRFLOW-746

Testing Done:

Unit tests are coming shortly, this is just a placeholder for better understanding what we are talking about as of now.

We all really need this! Is it going to be merged?

I am not following up on it as I am not working on airflow anymore.
You can fork my work and rebase it on the latest code if you need it.


Multi-label classification ?

Can I implement Multi-Label classification by using mxnet's LogisticRegressionOutput as loss function ?
I mean, in other words, does LogisticRegressionOutput support probability vector as input rather than a singular ?

Yes it does.
Checkout https://github.com/dmlc/mxnet/blob/master/example/kaggle-ndsb2/Train.py

@piiswrong ok, Thank you very much !

i think this is a multi-class regression example? in multi-label regression, there is no softmax constrain across label dimensions.

There is an example of multi-label image classification: https://github.com/miraclewkf/multilabel-MXNet, which use sigmoid instead of LogisticRegressionOutput and needn't recompile mxnet.


user permission

When you assign station permission to user it does not work at all and no access to manage and control station nor autodj for station

@athensguy I'm not seeing this error on my end...can you explain in more detail please?
If you're the station administrator, you should be able to log in as the other user and verify their permissions work correctly. I am happy to look into any specific pages or permissions that aren't working as expected.

That's what I am doing:

Using main administrator account, I can create TestStation as Shoutcast2 station
Using Users > permissions, I managed to add new permission as below

Role Name: StationManager
System-Wide Permissions: blank (No actions)
TestStation: assigned everything (All actions available)

Using Users > User accounts, I added new user and set his role StationManager

When I login with user that has StationManager role, he can view stats and modify his account, choose theme for AzuraCast while no manage button for station. When attempt to access manage station url directly, I got alert reporting access is denied.

@athensguy Thank you very much for the detailed reproduction...I see exactly what the problem is, will be pushing a fix up ASAP for it.


Once Human

There are some major rendering issues in this game. Its been like this for months. It used to play pretty ok on proton-ge 7.55, with a few graphical errors. Then the game got an anti cheat, and we could not use it anymore. It did never work on newer protons. I believe that the proton team has also look at this issue for months now, without a solution.
So some places are rendering pretty good, like the torturial etc. After you get into the open world, every npc, player house, animals starts to stutter heavy. It gets so bad, you get motion sick. Moving and driving is pretty bad in general.
From the look of things, it looks like the whole community has turned upside down on this game, to make it work.
Computer Information:
Manufacturer: ASUSTeK COMPUTER INC.
Model: ROG STRIX X670E-E GAMING WIFI
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 7 7800X3D 8-Core Processor
CPU Family: 0x19
CPU Model: 0x61
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 5050 MHz
8 logical processors
8 physical processors
Hyper-threading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Supported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Supported
AVX512VNNI: Supported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
BMI1: Supported
BMI2: Supported
F16C: Supported
FMA: Supported
Operating System Version:
"CachyOS" (64 bit)
Kernel Name: Linux
Kernel Version: 6.12.1-2-cachyos
X Server Vendor: The X.Org Foundation
X Server Release: 12401004
X Window Manager: KWin
Steam Runtime Version:
Client Information:
Version:<PHONE_NUMBER>
Browser GPU Acceleration Status: Disabled
Browser Canvas: Unavailable
Browser Canvas out-of-process rasterization: Disabled
Browser Direct Rendering Display Compositor: Disabled
Browser Compositing: Disabled
Browser Multiple Raster Threads: Enabled
Browser OpenGL: Disabled
Browser Rasterization: Disabled
Browser Raw Draw: Disabled
Browser Skia Graphite: Disabled
Browser Video Decode: Disabled
Browser Video Encode: Disabled
Browser Vulkan: Disabled
Browser WebGL: Unavailable
Browser WebGL2: Unavailable
Browser WebGPU: Disabled
Browser WebNN: Disabled
Video Card:
Driver: NVIDIA Corporation NVIDIA GeForce RTX 4090/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 565.57.01
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 137 Hz
VendorID: 0x10de
DeviceID: 0x2684
Revision Not Detected
Number of Monitors: 2
Number of Logical Video Cards: 1
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 6400 x 2160
Primary Display Size: 36.22" x 20.35" (41.54" diag), 92.0cm x 51.7cm (105.5cm diag)
Primary VRAM: 24564 MB
Sound card:
Audio device: Nvidia GPU a3 HDMI/DP
Memory:
RAM: 31722 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_GB.UTF-8
Total Hard Disk Space Available: 1181942 MB
Largest Free Hard Disk Block: 941491 MB
Storage:
Number of SSDs: 5
SSD sizes: 4000G,4000G,3840G,250G,0B
Number of HDDs: 0
Number of removable drives: 0
https://filebin.net/owph8spy8wppn5pd)
https://www.protondb.com/app/2139460

Hi there.
Does the game doesn't work on Linux at all right now because of anti cheat? If so then it is likely pretty hard to look in to. Even if when taking a look at windows anti cheats often don't allow the kind of tools used to debug visual issues (with good reason).

Because of the visual issues right? Not anti cheat.
I will try to take a look here later.

The game is free on steam, it made by NetEase with the NeoX engine. Its fully working on linux. just not playable due to stutter and bad performance in game. You can look at the ProtonDB to look at all the issues.
I run the game on a 4090, on very low settings, just then its pretty much not playable.

Looking at your log it seems to be hinting that the game uses d3d12 to render and not d3d11.  That would make it more appropriate to make a issue at https://github.com/HansKristian-Work/vkd3d-proton
But a bell is ringing for this game now. Could you try to installed the native version of d3dcompiler_47 with protontricks and see how it behaves then?

Looking at your log it seems to be hinting that the game uses d3d12 to render and not d3d11. That would make it more appropriate to make a issue at https://github.com/HansKristian-Work/vkd3d-proton
But a bell is ringing for this game now. Could you try to install the native version of d3dcompiler_47 with protontricks and see how it behaves then?

It has both. d3d11 does not work at all right now. If you go into that, all textures break

Could you check if either d3d11 or d3d12 mode gets fixed with a native d3dcompiler_47?

I did copy this post over at Hans Kristian as well. Both are broken of the versions.

So i have reproduced the visual glitches in dx11 mode out of the box yes, but after i start using the Windows d3dcompiler_47 it appears normal without glitches. This is tested with Experimental Bleeding Edge.

Im aware of that. But it still dont fix the performance issues.  So im not sure how to solve it. Or where to go with this problem.

I think i need to start over to properly understand what this issue is about.
The performance/stutter issue you are talking about is that both in dx11 and dx12 mode?

I think i need to start over to properly understand what this issue is about. Most of the opening post seem to write about the visual issue. The performance/stutter issue you are talking about is that both in dx11 and dx12 mode?

Yes the stutter is on both. To be honest, im not even sure anymore what is causing it. Other that objects, npc, and building causes major stutter. To me it seems to be a render issue of some sort. Been turning upside down on this for months. Then I tried to compare what was the difference from the proton 7 to the once we have now. Proton 7, was the only ok working proton for this. Any newer or older was not running good at all. Then a few months ago, the game got an anti cheat. Meaning we could not use proton 7. Due to its not compatibel with anti cheat. I dont think the anti cheat it self has anything to do with it. It ran close to flawless on the proton-ge 7-55. So nobody understands why.


Normalize java.io.tmpdir in TAPI tests.

We found that in TAPI tests, java.io.tmpdir sometimes are different, resulting in incompatible daemons. This PR fixes by always using same -Djava.io.tmpdir in TAPIs, no matter they're TAPI, or GradleExecuter, or CLI invocation.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.

We found that in TAPI tests, java.io.tmpdir sometimes are different

I don't understand what problem we are fixing here for test distribution. Can you clarify what the issues is? So between different test classes on the same test distribution agent the tmp dirs are different? Or on different agents on the same machine the tmp dirs are different?
Does test distribution set the java.io.tmpdir and that is what causes the test failures?

The previous passed java.io.tmpdir was different between local executors and remote executors (on TD agents). I think it was caused by different TMPDIR environment variable picked up by JVM.
@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Content will lost if a inline html tag in table

Describe the bug
In markdown mode, insert a table, then write some html in table cell like a2, then change mode, the content after the cell(content is HTML Tag) will lost
and
if paste a article with a table like mentioned above, all the content will lost
To Reproduce
Steps to reproduce the behavior:

Go to 'https://ui.toast.com/tui-editor'
Switch to markdown mode
Add a table, write a html tag to cell
Switch to wysiwyg mode
Content lost

Expected behavior
The content should not be lost, keep the html tag as is.
Screenshots

Desktop (please complete the following information):

OS: Windows 11
Browser Chrome 99.0.4844.74
Version V3.1.3

Additional context
I tried to debug the code, finally I found the content lost in ToWwConvertorState.convert

FYI: not only tag SUP, I tried many tag, only tag STRONG will work well

Thank you for the issue. We'll check it.


Added code for Peak Index In A Mountain Array Problem

@Sukshan001 kindly put the file in the correct folder.


teams-for-linux: 1.0.45 -> 1.0.53

Description of changes
The biggest changes are having macOS support and having a multi-account command-line flag. Other release notes at https://github.com/ismaelmartinez/teams-for-linux/releases
I added myself as maintainer and am letting OfBorg test to see if it builds on macOS or not (and I'll mark it broken if not)
Versions in-between these were waiting on #214062 but this version works without it again (so some of the drive-by changes were originally related to getting it to work with that)
I also tossed in a fix for notification sounds
Fixes #215593
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I'm just marking darwin broken for now unless someone else figures something out or I get access to the Darwin community builder (winterqt/darwin-build-box#12) and can debug

Fixes a known bug (two people verified on the issue thread) and has an approval already, merging


rolling_update: fix active mds host value

The active mds host should be based on the inventory hostname and not on
the ansible hostname.
The value returns under the mdsmap structure is based on the OS hostname
so we need to find the right node in the inventory with this value when
doing operation on inventory nodes.
Othewise we could see error like:
The task includes an option with an undefined variable. The error was:
"hostvars[foobar]" is undefined

Signed-off-by: Dimitri Savineau<EMAIL_ADDRESS>

jenkins test centos-container-purge

jenkins test centos-non_container-all_daemons

No we still need [0] because mds_active_host is a list

let's talk about this @dsavineau


ImportError: libtorch_cpu.so: cannot open shared object file: No such file or directory

when I run "python tools/test.py configs/faster_rcnn_r50_fpn_1x.py     checkpoints/faster_rcnn_r50_fpn_1x_20181010-3d1b3351.pth" there are some errors
Traceback (most recent call last):
File "tools/test.py", line 8, in
from tools.fuse_conv_bn import fuse_module
File "/mnt/WXRG0349/zhuoli/mmdetection/tools/fuse_conv_bn.py", line 7, in
from mmdet.apis import init_detector
File "/mnt/WXRG0349/zhuoli/mmdetection/mmdet/apis/init.py", line 1, in
from .inference import (async_inference_detector, inference_detector,
File "/mnt/WXRG0349/zhuoli/mmdetection/mmdet/apis/inference.py", line 11, in
from mmdet.core import get_classes
File "/mnt/WXRG0349/zhuoli/mmdetection/mmdet/core/init.py", line 7, in
from .post_processing import *  # noqa: F401, F403
File "/mnt/WXRG0349/zhuoli/mmdetection/mmdet/core/post_processing/init.py", line 1, in
from .bbox_nms import multiclass_nms
File "/mnt/WXRG0349/zhuoli/mmdetection/mmdet/core/post_processing/bbox_nms.py", line 3, in
from mmdet.ops.nms import nms_wrapper
File "/mnt/WXRG0349/zhuoli/mmdetection/mmdet/ops/init.py", line 19, in
from .utils import get_compiler_version, get_compiling_cuda_version
File "/mnt/WXRG0349/zhuoli/mmdetection/mmdet/ops/utils/init.py", line 2, in
from .compiling_info import get_compiler_version, get_compiling_cuda_version
ImportError: libtorch_cpu.so: cannot open shared object file: No such file or directory
Environment
pytorch1.4.0+python3.7.0
use "pip" install the pytorch

I meet same error here, how did you solve it?

I meet same error here, how did you solve it?

I haven't solve this problem.

Did you install CUDA correctly?

Did you install CUDA correctly?

yes. when I run torch.cuda.is_available() it returns True

Traceback (most recent call last):
File "../mmdetection/tools/test.py", line 9, in
from tools.fuse_conv_bn import fuse_module
File "/home/pansiyuan/mmdetection/tools/fuse_conv_bn.py", line 7, in
from mmdet.apis import init_detector
File "/home/pansiyuan/mmdetection/mmdet/apis/init.py", line 1, in
from .inference import (async_inference_detector, inference_detector,
File "/home/pansiyuan/mmdetection/mmdet/apis/inference.py", line 9, in
from mmdet.core import get_classes
File "/home/pansiyuan/mmdetection/mmdet/core/init.py", line 5, in
from .mask import *  # noqa: F401, F403
File "/home/pansiyuan/mmdetection/mmdet/core/mask/init.py", line 2, in
from .structures import BitmapMasks, PolygonMasks
File "/home/pansiyuan/mmdetection/mmdet/core/mask/structures.py", line 8, in
from mmdet.ops.roi_align import roi_align
File "/home/pansiyuan/mmdetection/mmdet/ops/init.py", line 3, in
from .dcn import (DeformConv, DeformConvPack, DeformRoIPooling,
File "/home/pansiyuan/mmdetection/mmdet/ops/dcn/init.py", line 1, in
from .deform_conv import (DeformConv, DeformConvPack, ModulatedDeformConv,
File "/home/pansiyuan/mmdetection/mmdet/ops/dcn/deform_conv.py", line 12, in
from . import deform_conv_ext
ImportError: libtorch_cpu.so: cannot open shared object file: No such file or directory

also seeing this issue when importing init_detector with a valid CUDA environment

Hi @grayson-hilliard, @pansiyuan123 , @interestingzhuo ,
Can you first try to import torch and do some operation to see whether your PyTorch is installed correctly and works well? Meanwhile, you can also try to use conda to install PyTorch and see whether the bug still exists.

Hi @grayson-hilliard, @pansiyuan123 , @interestingzhuo ,
Can you first try to import torch and do some operation to see whether your PyTorch is installed correctly and works well? Meanwhile, you can also try to use conda to install PyTorch and see whether the bug still exists.

there's still the same problem

Could you try to run https://github.com/open-mmlab/mmdetection/blob/master/mmdet/utils/collect_env.py and post your results in this issue?

I also meet the problem. I use pytorch 1.4.0+cuda 10.0

I also meet the problem. I use pytorch 1.4.0+cuda 10.0

well i've solved this problem by recompile mmdetection。Maybe you could try
pytorch1.4 and cuda 10.0

I also meet the problem. I use pytorch 1.4.0+cuda 10.0

well i've solved this problem by recompile mmdetection。Maybe you could try。
i use pytorch1.4 and cuda 10.0

Hi !  What does ''recompile mmdetection'' mean? Do that in install.md again? Thank you!
(My cuda is  the image: nvidia/cuda         10.0-cudnn7-devel)

Could you try to run https://github.com/open-mmlab/mmdetection/blob/master/mmdet/utils/collect_env.py and post your results in this issue?

I'm using mdmet==v1.0rc1 and these are the results of the "backported" collect_env.py script:
> python ./mmdet/utils/collect_env.py
Traceback (most recent call last):
  File "./mmdet/utils/collect_env.py", line 62, in <module>
    for name, val in collect_env().items():
  File "./mmdet/utils/collect_env.py", line 55, in collect_env
    from mmdet.ops import get_compiler_version, get_compiling_cuda_version
  File "./mmdet/ops/__init__.py", line 7, in <module>
    from .nms import nms, soft_nms
  File "./mmdet/ops/nms/__init__.py", line 1, in <module>
    from .nms_wrapper import nms, soft_nms
  File "./mmdet/ops/nms/nms_wrapper.py", line 4, in <module>
    from . import nms_cpu, nms_cuda
ImportError: libtorch_cpu.so: cannot open shared object file: No such file or directory

I commented out the mmdet import + subsequent calls and re-ran, here are the results:
> python ./mmdet/utils/collect_env.py
sys.platform: linux
Python: 3.7.7 (default, May  7 2020, 21:25:33) [GCC 7.3.0]
CUDA available: True
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 10.0, V10.0.130
GPU 0: GeForce RTX 2080
GCC: gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
PyTorch: 1.4.0
PyTorch compiling details: PyTorch built with:
  - GCC 7.3
  - Intel(R) Math Kernel Library Version 2020.0.1 Product Build 20200208 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v0.21.1 (Git Hash 7d2fd500bc78936d1d648ca713b901012f470dbc)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - NNPACK is enabled
  - CUDA Runtime 10.0
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_37,code=compute_37
  - CuDNN 7.6.3
  - Magma 2.5.1
  - Build settings: BLAS=MKL, BUILD_NAMEDTENSOR=OFF, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -fopenmp -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -O2 -fPIC -Wno-narrowing -Wall -Wextra -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Wno-stringop-overflow, DISABLE_NUMA=1, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_STATIC_DISPATCH=OFF,

TorchVision: 0.5.0
OpenCV: 4.2.0

Hi @grayson-hilliard ,
If you use MMDet 1.x and meet the similar problem, then yes, it is very likely the environment problem caused by recent PyTorch, we will further check it.

It seems that they recently refactored their libraries yes: https://github.com/pytorch/pytorch/issues/29235 , so if you build against pytorch 1.5.0 and then try and run on an older pytorch it will have an issue.

So should we go through INSTALL.md and redo the steps?

I solve this problem by using pytorch1.5 and the new version. Maybe you can use the new version.

I solve this problem by using pytorch1.5 and the new version. Maybe you can use the new version.

new version of?

I solve this problem by using pytorch1.5 and the new version. Maybe you can use the new version.

new version of?

The latest code.

I solve this problem by using pytorch1.5 and the new version. Maybe you can use the new version.

new version of?

The latest code.

I  built the environment from scratch, and it started working, thank you. But when i run for multiple GPUs using the following command:
./tools/dist_train.sh configs/ms_rcnn/ms_rcnn_x101_32x4d_fpn_1x_coco.py 4
I'm having 4 GPUs on a single machine. So i have mentioned 4 above.
I'm getting SubProcessError:
subprocess.CalledProcessError: Command '['/home/dksingh/anaconda3/envs/open-mmlab/bin/python', '-u', './tools/train.py', '--local_rank=3', 'configs/ms_rcnn/ms_rcnn_x101_32x4d_fpn_1x_coco.py', '--launcher', 'pytorch', '--work-dir', '/ssd_scratch/cvit/dksingh/msrcnn_logs/']' died with <Signals.SIGKILL: 9>.

I encountered this issue when I downgraded from pytorch from 1.5.0 to 1.4.0. I did the following command twice then the issue disappeared.
rm -r build
python setup.py develop

I encountered this issue when I downgraded from pytorch from 1.5.0 to 1.4.0. I did the following command twice then the issue disappeared.
rm -r build
python setup.py develop

Initially i was running using 1.4+, it was raising other errors, once i built the environment, it started running for single gpu machine, but when i run for multiple gpu as I have mentioned above, it's raising that issue.
I noticed other similar issues regarding it and they have mentioned that it maybe due to batch size or memory, Do you have any idea under which dictionary i should mention batch size?
Also, do we have to mention the CUDA_VISIBLE_DEVICES for multiple_gpu run on a single machine.
Thank you

I encountered this issue when I downgraded from pytorch from 1.5.0 to 1.4.0. I did the following command twice then the issue disappeared.
rm -r build
python setup.py develop

This also fixed it for me. I got another error with PyTorch 1.5 and CUDA 10.1 so I downgraded to PyTorch 1.4. The exact error was #2635
Also better to change to rm -rf build to remove the flood of prompts

I encountered this issue when I downgraded from pytorch from 1.5.0 to 1.4.0. I did the following command twice then the issue disappeared.
rm -r build
python setup.py develop

This also fixed it for me. I got another error with PyTorch 1.5 and CUDA 10.1 so I downgraded to PyTorch 1.4. The exact error was #2635
Also better to change to rm -rf build to remove the flood of prompts

I can also confirm, this was the solution. I'm successfully running inference w/ mmdet=1.0 and cuda=10.0 :tada:
I feel silly for not having realized I needed to delete the build folder. Could we update the docs to include this (seemingly obvious but very critical and time-consuming to triage) information?

Hi @deepakksingh
You may set samples_per_gpu in data dict.
CUDA_VISIBLE_DEVICES may not be necessary.
You could raise a new issue with error template if you encounter other errors.

Thank you. I will do that.

I encountered this issue when I downgraded from pytorch from 1.5.0 to 1.4.0. I did the following command twice then the issue disappeared.
rm -r build
python setup.py develop

It not work for me ,I finnaly found the reason is that cuda version of compiling torch and extension is not match.  Adding extentsion cuda in PATH works for me
export LD_LIBRARY_PATH="usr/local/cuda-10.2/lib64:$LD_LIBRARY_PATH"

For me, the problem occurred when I use pip install --upgrade torch-geometric to update Pytorch Geometric from 1.4 to 1.5.
Then I used conda install pytorch torchvision cudatoolkit=10.1 -c pytorch to update torch and the problem got solved.

someone may need to delete all generated so files under mmdet
find . -name "*.so" -type f -delete

I encountered this issue when I downgraded from pytorch from 1.5.0 to 1.4.0. I did the following command twice then the issue disappeared.
rm -r build
python setup.py develop

I'm also encountering this issue.. I'm also downgrading pytorch from 1.5 to 1.4.
I'm using CUDA10.0, mmdet==2.3.0rc0+b90441e.
After I ran the first round of
rm -r build python setup.py develop
the build folder doesn't appear anymore.
Only one round of this command seems couldn't solve this issue.
Could you please give some idea. I also added CUDA library path to LD_LIBRARY_PATH. But still got this issue.

@ShidiDaisy
you should delete all the shared library (*.so) under mmdet, not only the build folder.

@ShidiDaisy
you should delete all the shared libraries (*.so) under mmdet, not only the build folder.

I have run
find . -name "*.so" -type f -delete
python setup.py develop
twice, but still got this issue.

I encountered this issue when I downgraded from pytorch from 1.5.0 to 1.4.0. I did the following command twice then the issue disappeared.
rm -r build
python setup.py develop

It not work for me ,I finnaly found the reason is that cuda version of compiling torch and extension is not match. Adding extentsion cuda in PATH works for me
export LD_LIBRARY_PATH="usr/local/cuda-10.2/lib64:$LD_LIBRARY_PATH"

thx,this work for me~

Hi, I have the same problem. after I uninstall the mmdet and delete build, then when I run pip install -v -e . again, there 's no build file in mmdetection anymore which means it doesn't build successfully.

I met the same problem, and waste days to find the solution. Last I found that I am such a fool, I just copy this
pip install mmcv-full==latest+torch1.5.0+cu101 -f https://openmmlab.oss-accelerate.aliyuncs.com/mmcv/dist/index.html
to install mmcv, and I did not saw this command include version code, so I change it to
pip install mmcv-full==latest+torch1.4.0+cu100 -f https://openmmlab.oss-accelerate.aliyuncs.com/mmcv/dist/index.html
with pytorch=1.4 and cuda=10.0 , finally is worked, now I am struggling in another problem.

When I run the command from mmdet.models import build_detector I got the error below:
File "/usr/src/app/mmdetection/mmdet/models/__init__.py", line 3, in <module>
    from .bbox_heads import *  # noqa: F401,F403
  File "/usr/src/app/mmdetection/mmdet/models/bbox_heads/__init__.py", line 3, in <module>
    from .double_bbox_head import DoubleConvFCBBoxHead
  File "/usr/src/app/mmdetection/mmdet/models/bbox_heads/double_bbox_head.py", line 2, in <module>
    from mmcv.cnn.weight_init import normal_init, xavier_init
ModuleNotFoundError: No module named 'mmcv.cnn.weight_init'

This is what I have from the command python mmdetection/mmdet/utils/collect_env.py:
sys.platform: linux
Python: 3.6.9 |Anaconda, Inc.| (default, Jul 30 2019, 19:07:31) [GCC 7.3.0]
CUDA available: True
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 10.1, V10.1.243
GPU 0: GeForce RTX 2070 SUPER
GCC: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609
PyTorch: 1.3.0
PyTorch compiling details: PyTorch built with:
  - GCC 7.3
  - Intel(R) Math Kernel Library Version 2019.0.4 Product Build 20190411 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v0.20.5 (Git Hash 0125f28c61c1f822fd48570b4c1066f96fcb9b2e)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - NNPACK is enabled
  - CUDA Runtime 10.1
  - NVCC architecture flags: -gencode;arch=compute_35,code=sm_35;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_50,code=compute_50
  - CuDNN 7.6.3
  - Magma 2.5.1
  - Build settings: BLAS=MKL, BUILD_NAMEDTENSOR=OFF, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -fopenmp -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -O2 -fPIC -Wno-narrowing -Wall -Wextra -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Wno-stringop-overflow, DISABLE_NUMA=1, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=True, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_STATIC_DISPATCH=OFF,

TorchVision: 0.4.1a0+d94043a
OpenCV: 4.2.0
MMCV: 1.0.5
MMDetection: 1.2.0+unknown
MMDetection Compiler: GCC 5.4
MMDetection CUDA Compiler: 10.1

The project is in a docker container with the image
FROM pytorch/pytorch:1.3-cuda10.1-cudnn7-devel

How did you solve it? Please help.

I encountered this issue when I downgraded from pytorch from 1.5.0 to 1.4.0. I did the following command twice then the issue disappeared.
rm -r build
python setup.py develop

It work well，thanks

i have solved this problem by reinstalling mmcv.
pip uninstall mmcv
pip install mmcv-full  -i https://pypi.tuna.tsinghua.edu.cn/simple  (not pip install mmcv-full==latest+torch1.5.0+cu101 -f https://download.openmmlab.com/mmcv/dist/index.html)
it may be helpful for you

I encountered this issue when I downgraded from pytorch from 1.5.0 to 1.4.0. I did the following command twice then the issue disappeared.
rm -r build
python setup.py develop

In what directory do I run these commands?

I met the same problem, and waste days to find the solution. Last I found that I am such a fool, I just copy this
pip install mmcv-full==latest+torch1.5.0+cu101 -f https://openmmlab.oss-accelerate.aliyuncs.com/mmcv/dist/index.html
to install mmcv, and I did not saw this command include version code, so I change it to
pip install mmcv-full==latest+torch1.4.0+cu100 -f https://openmmlab.oss-accelerate.aliyuncs.com/mmcv/dist/index.html
with pytorch=1.4 and cuda=10.0 , finally is worked, now I am struggling in another problem.

This solved my problem.

I met the same problem, and waste days to find the solution. Last I found that I am such a fool, I just copy this
pip install mmcv-full==latest+torch1.5.0+cu101 -f https://openmmlab.oss-accelerate.aliyuncs.com/mmcv/dist/index.html
to install mmcv, and I did not saw this command include version code, so I change it to
pip install mmcv-full==latest+torch1.4.0+cu100 -f https://openmmlab.oss-accelerate.aliyuncs.com/mmcv/dist/index.html
with pytorch=1.4 and cuda=10.0 , finally is worked, now I am struggling in another problem.

This solved my problem.

Also solved my problem.

i solve the problem by reinstall the mmcv-full by "pip install mmcv-full==1.1.4 -i https://pypi.tuna.tsinghua.edu.cn/simple"

i solve the problem by reinstall the mmcv-full by "pip install mmcv-full==1.1.4 -i https://pypi.tuna.tsinghua.edu.cn/simple"

Thanks a lot. It works for me.

I encountered this issue when I downgraded from pytorch from 1.5.0 to 1.4.0. I did the following command twice then the issue disappeared.
rm -r build
python setup.py develop

could you please tell me which build shuold be remove or while is the build file ? I can not find it.

I encountered this issue when I downgraded from pytorch from 1.5.0 to 1.4.0. I did the following command twice then the issue disappeared.
rm -r build
python setup.py develop

could you please tell me which build shuold be remove or while is the build file ? I can not find it.

you can try it  reinstall the mmcv-full by "pip install mmcv-full==1.1.4 -i https://pypi.tuna.tsinghua.edu.cn/simple", i solve the problem by this

Honestly speaking, I have tried all possible solutions above mentioned, but I still can't import .so shared files in pycharm(like nms_cpu.cpython-37m-x86_64-linux-gnu.so, etc.) and then raise the error like title: ImportError: libtorch_cpu.so: cannot open shared object file: No such file or directory,

my mmdetection version is 1.0.rc0+6e48d28 that used in another repo so that I can't change version lest incompatible problems
my env is:
sys.platform: linux
Python: 3.7.10 (default, Feb 26 2021, 18:47:35) [GCC 7.3.0]
CUDA available: True
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 10.1, V10.1.243
GPU 0,1: GeForce RTX 2080 Ti
GCC: gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
PyTorch: 1.4.0
PyTorch compiling details: PyTorch built with:
  - GCC 7.3
  - Intel(R) Math Kernel Library Version 2019.0.4 Product Build 20190411 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v0.21.1 (Git Hash 7d2fd500bc78936d1d648ca713b901012f470dbc)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - NNPACK is enabled
  - CUDA Runtime 10.1
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_37,code=compute_37
  - CuDNN 7.6.3
  - Magma 2.5.1
  - Build settings: BLAS=MKL, BUILD_NAMEDTENSOR=OFF, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -fopenmp -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -O2 -fPIC -Wno-narrowing -Wall -Wextra -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Wno-stringop-overflow, DISABLE_NUMA=1, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_STATIC_DISPATCH=OFF,

TorchVision: 0.5.0
OpenCV: 4.5.2
MMCV: 0.5.3
MMDetection: 1.1.0+unknown
MMDetection Compiler: GCC 7.5
MMDetection CUDA Compiler: 10.1

rm -r build
python setup.py develop

works.


Routing - path param not matching

Trying to do some very simple REST calls, but decorators don't seem to be working :(
GET http://localhost:3000/api/cart (Works)
GET http://localhost:3000/api/cart/123 (Caught by findManyHandler instead of findOneHandler)
POST  http://localhost:3000/api/cart (Works)
PATCH http://localhost:3000/api/cart/123 (404 - Not Found)
DELETE http://localhost:3000/api/cart/123 (404 - Not Found)
Next version : 12.3.4,
File name: /api/cart/[[...params].ts
File contents
class CartAPI {
  @Get()
  public async findManyHandler(@Request() req: IReq, @Query() query: Record<string, any> = {}) {
    console.log("get many >>>", query); /* outputs { params: [ '123' ] } */
    return [];
  }

  @Get("/:id")
  public async findOneHandler(@Request() req: IReq, @Param("id") id: number) {
    console.log("get one >>>", id);
    return [{ test: 1 }];
  }

  @Post()
  @HttpCode(201)
  public async createHandler(@Request() req: IReq, @Body() body: Record<string, any> = {}) {
    console.log("create >>>", body);
  }

  @Patch("/:id")
  @HttpCode(204)
  public async updateHandler(@Request() req: IReq, @Param("id") id: string, @Body() body: Record<string, any> = {}) {
    console.log("update >>>", id, body);
  }

  @Delete("/:id")
  @HttpCode(204)
  protected async deleteHandler(@Request() req: IReq, @Param("id") id: string) {
    console.log("delete >>>", id);
  }
}

export default createHandler(CartAPI);

Got latest and installed these packages, seemed to have fixed the issue for me
pnpm i path-to-regexp reflect-metadata class-validator class-transformer


Angular 11 compatibility

Hey, I'm unable to run it on an Angular 11 app, getting error:
Value at position 10 in the NgModule.declarations of MyAppModule is not a reference. Value could not be determined statically.(-991010)
Is there something I'm doing wrong?
Thx

Hey @shaya-tabit  , as you can see in the description of the project this repository only compatible with angular 4.x versions, not maintianed this project for long time, PRs are welcome to ingratiate to the new versions of angular, but I have no time to do these works for now
in other words, you need to pick another libs


Listening to CMI events (LMSFinish, LMSCommit)

Hi @NemoStein,
How are we able to listen to the SCORM CMI events (LMSFinish, LMSCommit) so we can talk to our backend systems (Saving scorm data) ?

This package is a client-side implementation of SCORM standard that interfaces with the LMS.
The implementation of the server-side API is left to the LMS to handle.
How are you using this package (could you provide a use-case)?


Fix authorization config paths

Thanks for the fix.
The CI fail is unrelated to your changes. I'll fix it in a separate PR first, though.


android: acceptAllCerts doesn't call callbacks

As per API/doc, acceptAllCerts should call one of its success/failure callback but it's not doing so. At least on android, the CordovaHttpPlugin's execute method is not calling  success()/error() on callbackContext for the "acceptAllCerts" as it is doing for the "enableSSLPinning" case.

You're right, it didn't on Android. It will now invoke the success handler once it's done.

awesome, thanks!


nix-shell with development dependencies from package.json

I've run nixfromnpm -f package.json -o ~/Projects/nix-node-packages --dev-depth 1 -r http://mylocalregistry from ~/Projects/mynodeproject/ and it creates a default.nix and project.nix, along with adding expressions to ~/Projects/nix-node-packages.
Incorrect src path
Running nix-shell and nix-build work. The nix expressions for my project in ~/Projects/nix-node-packages/ have src = ./.;, which is obviously incorrect, and results in nix-build ~/Projects/nix-node-packages/default.nix -A nodePackages.mynodeproject failing like so:
return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open './package.json'
    at Error (native)
    at Object.fs.openSync (fs.js:549:18)
    at Object.fs.readFileSync (fs.js:397:15)

Nix-shell with development dependencies
nix-shell ~/Projects/nix-node-packages/default.nix -A nodePackages.mynodeproject works, but nix-shell ~/Projects/nix-node-packages/default.nix -A nodePackages.mynodeproject.env doesn't work as expected. I expected it to build a node_modules with all my dependences and devDependencies, but it only includes normal dependencies, behaving just like the command without .env.
I tried nix-shell default.nix -A env, I'm not sure that is the correct command, but I was expecting it would give me dev dependencies, but it doesn't either, it behaves the same as nix-shell default.nix.
What is going on, and how do I get an environment with dev dependencies?
Output path trailing slash
Additionally, the -o outputpath option doesn't work if you use a trailing slash, it'll add the trailing slash to the path in your default.nix.
Getting npm to use nix-shell result
Can I get nix-shell to symlink in the /run/user/1000/xxxxxxxxxxx-packagename-0.1.0/node_modules to ./node_modules or somehow pass the location to npm?
Would appreciate any help!

Could you maybe paste what the default.nix and project.nix look like, and what the directory structure is? I haven't worked on the shell stuff for a little while except for modifying the libraries that in the nix-node-packages repo. It might just be a matter of bringing the changes I've made back into nixfromnpm.

{ nodejs ? pkgs.nodejs-4_x, npm3 ? false, pkgs ? import <nixpkgs> {} }:
let
    lib = import /home/ollie/Projects/nix-node-packages {
      inherit pkgs npm3 nodejs;
    };
    in lib.callPackage ./project.nix {}

{ buildNodePackage, nodePackages, pkgs }:
buildNodePackage {
    name = "mynodeproject";
    version = "0.1.0";
    src = ./.;
    deps = with nodePackages; [
      dependency_1-1-0
      otherdependency_1-2-3
      anotherdependency_0-4-5
    ];
    devDependencies = with nodePackages; [
      devdependency_6-7-0
      anotherdevdependency_8-9-0
    ];
    meta = {
      description = "Description of my node module";
    };
  }

I have the latest checked out version of nix-node-packages, and the only files that generating my packages has changed is packages in nodePackages/, and upped the version in .nixfromnpm-version from 0.10.0 to 0.10.2, all the nodeLibs/ are the same as in master.

@adnelson Any ideas on this, particularly to do with nix-shell with development dependencies?

Hey Ollie sorry it's taken me a little while to look at this. I'll take a
crack at it this morning.
On Tuesday, August 2, 2016, Ollie Hunt<EMAIL_ADDRESS>wrote:

@adnelson https://github.com/adnelson Any ideas on this, particularly
to do with nix-shell with development dependencies?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/adnelson/nixfromnpm/issues/64#issuecomment-236919574,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2wt4whEiFhoSqEcPoaW2tDGQfk5pzxks5qb1KDgaJpZM4JSpvy
.

--
-- Allen

@ollieh
Let me know if this doesn't work out for you. The .env attribute was effectively a no-op since I had removed that functionality by accident. I restored it and it should grab the dev dependencies when it constructs the local environment.
The way that node knows how to find the packages is via an environment variable $NODE_PATH. The shell constructs a temporary directory which contains symlinks to all of the dependencies, as well as the package itself, and puts that tempdir's path in the $NODE_PATH variable. It would also be possible to create a symlink to that folder in the package directory, but I didn't do this because it has externally visible effects. All that would need to be done is to execute
[nix-shell]$ ln -s $NODE_MODULES node_modules

in the shell.

.env is working as expected now, thanks a lot! However, I'm getting circular dependencies, and they appear to be in your nix-node-packages repo. Is there a way to resolve them?
https://github.com/adnelson/nix-node-packages/issues/26


Is this a silly spawn bug?

Hello,
Just starting with the language. Can anyone please tell me why this runs ok:
i = 0
spawn do
  loop do
    i += 1
    puts "#{i}!"
  end
end
sleep 1.second
puts "\nDone."

Output:
343585!
343586!
343587!
343588!

Done.

... while this won't stop (infinite loop)?
i = 0
spawn do
  loop do
    i += 1
    #puts "#{i}!"
  end
end
sleep 1.second
puts "\nDone."```

? It doesn't seem to make any sense for me...

Thanks,
Howe

In the second example, the code in the second fiber runs in a tight loop. The main fiber will never be reached and thus can't reach the "Done" line and exit the program.
puts "#{i}!" allows switching fibers when the main fiber is supposed to be resumed.

Hey @straight-shoota,
Is that by design? That's the the first language I ever saw with such a behavior. I found that very confusing.
Thanks.
Howe

Go works like that, or so it seems: https://github.com/golang/go/issues/10958
(though I thought at this point it was fully preemptive)

In the future we'll probably have to think about how to add more preemption points  to programs but for now this is expected behaviour.


Synthesis failed for Manufacturers

Hello! Autosynth couldn't regenerate Manufacturers. :broken_heart:
Here's the output from running synth.py:
2020-05-09 05:16:02 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-05-09 05:16:02,125 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
Switched to branch 'autosynth-manufacturers'
2020-05-09 05:16:03 [INFO] Running synthtool
2020-05-09 05:16:03,946 autosynth > Running synthtool
2020-05-09 05:16:03 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--']
2020-05-09 05:16:03,946 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--']
2020-05-09 05:16:04,154 synthtool > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-manufacturers
nothing to commit, working tree clean
2020-05-09 05:16:04,407 synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
2020-05-09 05:16:04,881 synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Manufacturers
2020-05-09 05:16:09,049 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 180, in __exit__
    write(self.metadata_file_path)
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
    with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/manufacturers/synth.metadata'
2020-05-09 05:16:09 [ERROR] Synthesis failed
2020-05-09 05:16:09,078 autosynth > Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 599, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--', 'Manufacturers']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating Manufacturers. :sob:
Here's the output from running synth.py:
2020-05-11 05:14:23 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-05-11 05:14:23,494 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
Switched to branch 'autosynth-manufacturers'
2020-05-11 05:14:25 [INFO] Running synthtool
2020-05-11 05:14:25,210 autosynth > Running synthtool
2020-05-11 05:14:25 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--']
2020-05-11 05:14:25,210 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--']
2020-05-11 05:14:25,393 synthtool > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-manufacturers
nothing to commit, working tree clean
2020-05-11 05:14:25,728 synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
2020-05-11 05:14:26,206 synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Manufacturers
2020-05-11 05:14:30,979 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 180, in __exit__
    write(self.metadata_file_path)
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
    with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/manufacturers/synth.metadata'
2020-05-11 05:14:31 [ERROR] Synthesis failed
2020-05-11 05:14:31,004 autosynth > Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 599, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--', 'Manufacturers']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating Manufacturers. :sob:
Here's the output from running synth.py:
2020-05-11 15:17:10 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-05-11 15:17:10,537 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
Switched to branch 'autosynth-manufacturers'
2020-05-11 15:17:12 [INFO] Running synthtool
2020-05-11 15:17:12,343 autosynth > Running synthtool
2020-05-11 15:17:12 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--']
2020-05-11 15:17:12,344 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--']
2020-05-11 15:17:12,568 synthtool > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-manufacturers
nothing to commit, working tree clean
2020-05-11 15:17:12,653 synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
2020-05-11 15:17:13,173 synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Manufacturers
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.0
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
A new Hex version is available (0.20.1 < 0.20.5), please update with `mix local.hex`
All dependencies are up to date
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.

22:17:15.711 [info]  FETCHING: https://manufacturers.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

22:17:16.153 [info]  FETCHING: https://manufacturers.googleapis.com/$discovery/rest?version=v1

22:17:16.477 [info]  FOUND: https://manufacturers.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200428, new=20200505, generating=true
Creating leading directories
Writing Attributes to clients/manufacturers/lib/google_api/manufacturers/v1/model/attributes.ex.
Writing Capacity to clients/manufacturers/lib/google_api/manufacturers/v1/model/capacity.ex.
Writing Count to clients/manufacturers/lib/google_api/manufacturers/v1/model/count.ex.
Writing DestinationStatus to clients/manufacturers/lib/google_api/manufacturers/v1/model/destination_status.ex.
Writing Empty to clients/manufacturers/lib/google_api/manufacturers/v1/model/empty.ex.
Writing FeatureDescription to clients/manufacturers/lib/google_api/manufacturers/v1/model/feature_description.ex.
Writing Image to clients/manufacturers/lib/google_api/manufacturers/v1/model/image.ex.
Writing Issue to clients/manufacturers/lib/google_api/manufacturers/v1/model/issue.ex.
Writing ListProductsResponse to clients/manufacturers/lib/google_api/manufacturers/v1/model/list_products_response.ex.
Writing Price to clients/manufacturers/lib/google_api/manufacturers/v1/model/price.ex.
Writing Product to clients/manufacturers/lib/google_api/manufacturers/v1/model/product.ex.
Writing ProductDetail to clients/manufacturers/lib/google_api/manufacturers/v1/model/product_detail.ex.
Writing Accounts to clients/manufacturers/lib/google_api/manufacturers/v1/api/accounts.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.

22:17:17.713 [info]  Bumping patch
fixing file permissions
2020-05-11 15:17:18,480 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 180, in __exit__
    write(self.metadata_file_path)
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
    with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/manufacturers/synth.metadata'
2020-05-11 15:17:18 [ERROR] Synthesis failed
2020-05-11 15:17:18,511 autosynth > Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 599, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--', 'Manufacturers']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating Manufacturers. :sob:
Here's the output from running synth.py:
2020-05-12 05:16:42 [INFO] logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-05-12 05:16:42,012 autosynth > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
Switched to branch 'autosynth-manufacturers'
2020-05-12 05:16:43 [INFO] Running synthtool
2020-05-12 05:16:43,494 autosynth > Running synthtool
2020-05-12 05:16:43 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--']
2020-05-12 05:16:43,494 autosynth > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--']
2020-05-12 05:16:43,705 synthtool > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-manufacturers
nothing to commit, working tree clean
2020-05-12 05:16:43,863 synthtool > Cloning https://github.com/googleapis/elixir-google-api.git.
2020-05-12 05:16:44,572 synthtool > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/elixir-google-api:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh Manufacturers
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.0
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
A new Hex version is available (0.20.1 < 0.20.5), please update with `mix local.hex`
All dependencies are up to date
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.

12:16:47.069 [info]  FETCHING: https://manufacturers.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

12:16:47.511 [info]  FETCHING: https://manufacturers.googleapis.com/$discovery/rest?version=v1

12:16:47.833 [info]  FOUND: https://manufacturers.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200428, new=20200505, generating=true
Creating leading directories
Writing Attributes to clients/manufacturers/lib/google_api/manufacturers/v1/model/attributes.ex.
Writing Capacity to clients/manufacturers/lib/google_api/manufacturers/v1/model/capacity.ex.
Writing Count to clients/manufacturers/lib/google_api/manufacturers/v1/model/count.ex.
Writing DestinationStatus to clients/manufacturers/lib/google_api/manufacturers/v1/model/destination_status.ex.
Writing Empty to clients/manufacturers/lib/google_api/manufacturers/v1/model/empty.ex.
Writing FeatureDescription to clients/manufacturers/lib/google_api/manufacturers/v1/model/feature_description.ex.
Writing Image to clients/manufacturers/lib/google_api/manufacturers/v1/model/image.ex.
Writing Issue to clients/manufacturers/lib/google_api/manufacturers/v1/model/issue.ex.
Writing ListProductsResponse to clients/manufacturers/lib/google_api/manufacturers/v1/model/list_products_response.ex.
Writing Price to clients/manufacturers/lib/google_api/manufacturers/v1/model/price.ex.
Writing Product to clients/manufacturers/lib/google_api/manufacturers/v1/model/product.ex.
Writing ProductDetail to clients/manufacturers/lib/google_api/manufacturers/v1/model/product_detail.ex.
Writing Accounts to clients/manufacturers/lib/google_api/manufacturers/v1/api/accounts.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.

12:16:49.043 [info]  Bumping patch
fixing file permissions
2020-05-12 05:16:49,777 synthtool > No files in sources /home/kbuilder/.cache/synthtool/elixir-google-api/clients were copied. Does the source contain files?
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 180, in __exit__
    write(self.metadata_file_path)
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 112, in write
    with open(outfile, "w") as fh:
FileNotFoundError: [Errno 2] No such file or directory: 'clients/manufacturers/synth.metadata'
2020-05-12 05:16:49 [ERROR] Synthesis failed
2020-05-12 05:16:49,808 autosynth > Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 599, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 471, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 549, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 118, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/manufacturers/synth.metadata', 'synth.py', '--', 'Manufacturers']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


feat: move homing, light, open lid and modules into Protocol Engine

Have the protocol engine http handlers also handle homing, light, open lid and modules. Further, define, along with UX and Apps&UI, the behavior when the robot is engaged in various activities and it's asked via http to engage in another activity.
Acceptance criteria

[ ] homing, light, open lid and modules are now handled by PE endpoints
[ ] a grid is constructed w/ robot activities (run, calibrate, open lid, etc) along both axis and the grid is populated with what the robot should respond with if it's doing the thing on the left, and it's asked to do the thing on the top
[ ] a new ticket to implement the behaviors defined in the grid

Superseded by #9617


CUDA error in fused_multihead_attention_v2.h

I am compiling in local machine without a docker. The compilation is done but I encountered following issue:
CUDA Error: (null) /home/ec2-user/SageMaker/FasterTransformer/3rdparty/trt_fused_multihead_attention/fused_multihead_attention_v2.h 688

and the error is huge:
FT Mean diff: 0.18701171875
FT Max diff:  3.546875
FT Min diff:  0.0
EFF-FT Mean diff: 0.1739501953125
EFF-FT Max diff:  3.30078125
EFF-FT Min diff:  0.0

Here is the command I am running:
python ../examples/pytorch/encoder/encoder_example.py 8 4 128 8 64 --remove_padding --fp16

If I remove the --fp16 then it is normal:
FT Mean diff: 1.5242422932715272e-06
FT Max diff:  0.00024694204330444336
FT Min diff:  0.0
EFF-FT Mean diff: 2.849347765732091e-06
EFF-FT Max diff:  0.00020140409469604492
EFF-FT Min diff:  0.0

@xuanqing94 how did you manage to solve this? I encountered the same issue on A100 FP16. After removing --fp16 flag, errors are gone.
The error seems related to TensorRT fused MHA implementation, which is in cubin format.
CUDA Error: (null) FasterTransformer/3rdparty/trt_fused_multihead_attention/fused_multihead_attention_v2.h 686

@donglinz sorry but I didn't solve this issue.