base_commit & patch how to use?

Describe the issue
The definition of base_commit & patch is vague. I git apply the patch content to checkout to base_commit, but found that the apply failed. What does this design mean? Then I manually set up env and found that this dataset types-pkg-resources does not exist. How can I use and test the patch with this dataset?
{'repo': 'sqlfluff/sqlfluff',
 'instance_id': 'sqlfluff__sqlfluff-4764',
 'base_commit': 'a820c139ccbe6d1865d73c4a459945cd69899f8f',
 'patch': 'diff --git a/src/sqlfluff/cli/commands.py b/src/sqlfluff/cli/commands.py\n--- a/src/sqlfluff/cli/commands.py\n+++ b/src/sqlfluff/cli/commands.py\n@@ -44,6 +44,7 @@\n     dialect_selector,\n     dialect_readout,\n )\n+from sqlfluff.core.linter import LintingResult\n from sqlfluff.core.config import progress_bar_configuration\n \n from sqlfluff.core.enums import FormatType, Color\n@@ -691,12 +692,16 @@ def lint(\n         sys.exit(EXIT_SUCCESS)\n \n \n-def do_fixes(lnt, result, formatter=None, **kwargs):\n+def do_fixes(\n+    result: LintingResult, formatter: Optional[OutputStreamFormatter] = None, **kwargs\n+):\n     """Actually do the fixes."""\n-    click.echo("Persisting Changes...")\n+    if formatter and formatter.verbosity >= 0:\n+        click.echo("Persisting Changes...")\n     res = result.persist_changes(formatter=formatter, **kwargs)\n     if all(res.values()):\n-        click.echo("Done. Please check your files to confirm.")\n+        if formatter and formatter.verbosity >= 0:\n+            click.echo("Done. Please check your files to confirm.")\n         return True\n     # If some failed then return false\n     click.echo(\n@@ -708,7 +713,7 @@ def do_fixes(lnt, result, formatter=None, **kwargs):\n     return False  # pragma: no cover\n \n \n-def _stdin_fix(linter, formatter, fix_even_unparsable):\n+def _stdin_fix(linter: Linter, formatter, fix_even_unparsable):\n     """Handle fixing from stdin."""\n     exit_code = EXIT_SUCCESS\n     stdin = sys.stdin.read()\n@@ -751,7 +756,7 @@ def _stdin_fix(linter, formatter, fix_even_unparsable):\n \n \n def _paths_fix(\n-    linter,\n+    linter: Linter,\n     formatter,\n     paths,\n     processes,\n@@ -765,11 +770,12 @@ def _paths_fix(\n ):\n     """Handle fixing from paths."""\n     # Lint the paths (not with the fix argument at this stage), outputting as we go.\n-    click.echo("==== finding fixable violations ====")\n+    if formatter.verbosity >= 0:\n+        click.echo("==== finding fixable violations ====")\n     exit_code = EXIT_SUCCESS\n \n     with PathAndUserErrorHandler(formatter):\n-        result = linter.lint_paths(\n+        result: LintingResult = linter.lint_paths(\n             paths,\n             fix=True,\n             ignore_non_existent_files=False,\n@@ -781,20 +787,18 @@ def _paths_fix(\n \n     # NB: We filter to linting violations here, because they\'re\n     # the only ones which can be potentially fixed.\n-    if result.num_violations(types=SQLLintError, fixable=True) > 0:\n-        click.echo("==== fixing violations ====")\n-        click.echo(\n-            f"{result.num_violations(types=SQLLintError, fixable=True)} fixable "\n-            "linting violations found"\n-        )\n+    num_fixable = result.num_violations(types=SQLLintError, fixable=True)\n+    if num_fixable > 0:\n+        if formatter.verbosity >= 0:\n+            click.echo("==== fixing violations ====")\n+        click.echo(f"{num_fixable} " "fixable linting violations found")\n         if force:\n-            if warn_force:\n+            if warn_force and formatter.verbosity >= 0:\n                 click.echo(\n                     f"{formatter.colorize(\'FORCE MODE\', Color.red)}: "\n                     "Attempting fixes..."\n                 )\n             success = do_fixes(\n-                linter,\n                 result,\n                 formatter,\n                 types=SQLLintError,\n@@ -809,9 +813,9 @@ def _paths_fix(\n             c = click.getchar().lower()\n             click.echo("...")\n             if c in ("y", "\\r", "\\n"):\n-                click.echo("Attempting fixes...")\n+                if formatter.verbosity >= 0:\n+                    click.echo("Attempting fixes...")\n                 success = do_fixes(\n-                    linter,\n                     result,\n                     formatter,\n                     types=SQLLintError,\n@@ -829,8 +833,9 @@ def _paths_fix(\n                 click.echo("Aborting...")\n                 exit_code = EXIT_FAIL\n     else:\n-        click.echo("==== no fixable linting violations found ====")\n-        formatter.completion_message()\n+        if formatter.verbosity >= 0:\n+            click.echo("==== no fixable linting violations found ====")\n+            formatter.completion_message()\n \n     error_types = [\n         (\n@@ -841,7 +846,7 @@ def _paths_fix(\n     ]\n     for num_violations_kwargs, message_format, error_level in error_types:\n         num_violations = result.num_violations(**num_violations_kwargs)\n-        if num_violations > 0:\n+        if num_violations > 0 and formatter.verbosity >= 0:\n             click.echo(message_format.format(num_violations))\n             exit_code = max(exit_code, error_level)\n \n@@ -880,10 +885,20 @@ def _paths_fix(\n     "--force",\n     is_flag=True,\n     help=(\n-        "skip the confirmation prompt and go straight to applying "\n+        "Skip the confirmation prompt and go straight to applying "\n         "fixes. **Use this with caution.**"\n     ),\n )\n+@click.option(\n+    "-q",\n+    "--quiet",\n+    is_flag=True,\n+    help=(\n+        "Reduces the amount of output to stdout to a minimal level. "\n+        "This is effectively the opposite of -v. NOTE: It will only "\n+        "take effect if -f/--force is also set."\n+    ),\n+)\n @click.option(\n     "-x",\n     "--fixed-suffix",\n@@ -913,6 +928,7 @@ def fix(\n     force: bool,\n     paths: Tuple[str],\n     bench: bool = False,\n+    quiet: bool = False,\n     fixed_suffix: str = "",\n     logger: Optional[logging.Logger] = None,\n     processes: Optional[int] = None,\n@@ -932,6 +948,13 @@ def fix(\n     """\n     # some quick checks\n     fixing_stdin = ("-",) == paths\n+    if quiet:\n+        if kwargs["verbose"]:\n+            click.echo(\n+                "ERROR: The --quiet flag can only be used if --verbose is not set.",\n+            )\n+            sys.exit(EXIT_ERROR)\n+        kwargs["verbose"] = -1\n \n     config = get_config(\n         extra_config_path, ignore_local_config, require_dialect=False, **kwargs\ndiff --git a/src/sqlfluff/cli/formatters.py b/src/sqlfluff/cli/formatters.py\n--- a/src/sqlfluff/cli/formatters.py\n+++ b/src/sqlfluff/cli/formatters.py\n@@ -94,7 +94,7 @@ def __init__(\n     ):\n         self._output_stream = output_stream\n         self.plain_output = self.should_produce_plain_output(nocolor)\n-        self._verbosity = verbosity\n+        self.verbosity = verbosity\n         self._filter_empty = filter_empty\n         self.output_line_length = output_line_length\n \n@@ -116,13 +116,13 @@ def _format_config(self, linter: Linter) -> str:\n         """Format the config of a `Linter`."""\n         text_buffer = StringIO()\n         # Only show version information if verbosity is high enough\n-        if self._verbosity > 0:\n+        if self.verbosity > 0:\n             text_buffer.write("==== sqlfluff ====\\n")\n             config_content = [\n                 ("sqlfluff", get_package_version()),\n                 ("python", get_python_version()),\n                 ("implementation", get_python_implementation()),\n-                ("verbosity", self._verbosity),\n+                ("verbosity", self.verbosity),\n             ]\n             if linter.dialect:\n                 config_content.append(("dialect", linter.dialect.name))\n@@ -138,7 +138,7 @@ def _format_config(self, linter: Linter) -> str:\n                         col_width=41,\n                     )\n                 )\n-            if self._verbosity > 1:\n+            if self.verbosity > 1:\n                 text_buffer.write("\\n== Raw Config:\\n")\n                 text_buffer.write(self.format_config_vals(linter.config.iter_vals()))\n         return text_buffer.getvalue()\n@@ -150,7 +150,7 @@ def dispatch_config(self, linter: Linter) -> None:\n     def dispatch_persist_filename(self, filename, result):\n         """Dispatch filenames during a persist operation."""\n         # Only show the skip records at higher levels of verbosity\n-        if self._verbosity >= 2 or result != "SKIP":\n+        if self.verbosity >= 2 or result != "SKIP":\n             self._dispatch(self.format_filename(filename=filename, success=result))\n \n     def _format_path(self, path: str) -> str:\n@@ -159,14 +159,14 @@ def _format_path(self, path: str) -> str:\n \n     def dispatch_path(self, path: str) -> None:\n         """Dispatch paths for display."""\n-        if self._verbosity > 0:\n+        if self.verbosity > 0:\n             self._dispatch(self._format_path(path))\n \n     def dispatch_template_header(\n         self, fname: str, linter_config: FluffConfig, file_config: FluffConfig\n     ) -> None:\n         """Dispatch the header displayed before templating."""\n-        if self._verbosity > 1:\n+        if self.verbosity > 1:\n             self._dispatch(self.format_filename(filename=fname, success="TEMPLATING"))\n             # This is where we output config diffs if they exist.\n             if file_config:\n@@ -182,12 +182,12 @@ def dispatch_template_header(\n \n     def dispatch_parse_header(self, fname: str) -> None:\n         """Dispatch the header displayed before parsing."""\n-        if self._verbosity > 1:\n+        if self.verbosity > 1:\n             self._dispatch(self.format_filename(filename=fname, success="PARSING"))\n \n     def dispatch_lint_header(self, fname: str, rules: List[str]) -> None:\n         """Dispatch the header displayed before linting."""\n-        if self._verbosity > 1:\n+        if self.verbosity > 1:\n             self._dispatch(\n                 self.format_filename(\n                     filename=fname, success=f"LINTING ({\', \'.join(rules)})"\n@@ -202,7 +202,7 @@ def dispatch_compilation_header(self, templater, message):\n \n     def dispatch_processing_header(self, processes: int) -> None:\n         """Dispatch the header displayed before linting."""\n-        if self._verbosity > 0:\n+        if self.verbosity > 0:\n             self._dispatch(  # pragma: no cover\n                 f"{self.colorize(\'effective configured processes: \', Color.lightgrey)} "\n                 f"{processes}"\n@@ -228,7 +228,7 @@ def _format_file_violations(\n         show = fails + warns > 0\n \n         # Only print the filename if it\'s either a failure or verbosity > 1\n-        if self._verbosity > 0 or show:\n+        if self.verbosity > 0 or show:\n             text_buffer.write(self.format_filename(fname, success=fails == 0))\n             text_buffer.write("\\n")\n \n@@ -253,6 +253,8 @@ def dispatch_file_violations(\n         self, fname: str, linted_file: LintedFile, only_fixable: bool\n     ) -> None:\n         """Dispatch any violations found in a file."""\n+        if self.verbosity < 0:\n+            return\n         s = self._format_file_violations(\n             fname,\n             linted_file.get_violations(\n@@ -392,10 +394,13 @@ def format_filename(\n         if isinstance(success, str):\n             status_string = success\n         else:\n-            status_string = self.colorize(\n-                success_text if success else "FAIL",\n-                Color.green if success else Color.red,\n-            )\n+            status_string = success_text if success else "FAIL"\n+\n+        if status_string in ("PASS", "FIXED", success_text):\n+            status_string = self.colorize(status_string, Color.green)\n+        elif status_string in ("FAIL", "ERROR"):\n+            status_string = self.colorize(status_string, Color.red)\n+\n         return f"== [{self.colorize(filename, Color.lightgrey)}] {status_string}"\n \n     def format_violation(\ndiff --git a/src/sqlfluff/core/linter/linted_dir.py b/src/sqlfluff/core/linter/linted_dir.py\n--- a/src/sqlfluff/core/linter/linted_dir.py\n+++ b/src/sqlfluff/core/linter/linted_dir.py\n@@ -117,7 +117,11 @@ def persist_changes(\n         for file in self.files:\n             if file.num_violations(fixable=True, **kwargs) > 0:\n                 buffer[file.path] = file.persist_tree(suffix=fixed_file_suffix)\n-                result = buffer[file.path]\n+                result: Union[bool, str]\n+                if buffer[file.path] is True:\n+                    result = "FIXED"\n+                else:  # pragma: no cover\n+                    result = buffer[file.path]\n             else:  # pragma: no cover TODO?\n                 buffer[file.path] = True\n                 result = "SKIP"\n',
 'test_patch': 'diff --git a/test/cli/commands_test.py b/test/cli/commands_test.py\n--- a/test/cli/commands_test.py\n+++ b/test/cli/commands_test.py\n@@ -557,6 +557,18 @@ def test__cli__command_lint_parse(command):\n             ),\n             1,\n         ),\n+        # Test that setting --quiet with --verbose raises an error.\n+        (\n+            (\n+                fix,\n+                [\n+                    "--quiet",\n+                    "--verbose",\n+                    "test/fixtures/cli/fail_many.sql",\n+                ],\n+            ),\n+            2,\n+        ),\n     ],\n )\n def test__cli__command_lint_parse_with_retcode(command, ret_code):\n@@ -1891,7 +1903,7 @@ def test_cli_fix_disabled_progress_bar_deprecated_option(\n \n \n def test__cli__fix_multiple_errors_no_show_errors():\n-    """Basic checking of lint functionality."""\n+    """Test the fix output."""\n     result = invoke_assert_code(\n         ret_code=1,\n         args=[\n@@ -1910,8 +1922,57 @@ def test__cli__fix_multiple_errors_no_show_errors():\n     assert result.output.replace("\\\\", "/").startswith(multiple_expected_output)\n \n \n+def test__cli__fix_multiple_errors_quiet_force():\n+    """Test the fix --quiet option with --force."""\n+    result = invoke_assert_code(\n+        ret_code=0,\n+        args=[\n+            fix,\n+            [\n+                "--disable-progress-bar",\n+                "test/fixtures/linter/multiple_sql_errors.sql",\n+                "--force",\n+                "--quiet",\n+                "-x",\n+                "_fix",\n+            ],\n+        ],\n+    )\n+    normalised_output = result.output.replace("\\\\", "/")\n+    assert normalised_output.startswith(\n+        """1 fixable linting violations found\n+== [test/fixtures/linter/multiple_sql_errors.sql] FIXED"""\n+    )\n+\n+\n+def test__cli__fix_multiple_errors_quiet_no_force():\n+    """Test the fix --quiet option without --force."""\n+    result = invoke_assert_code(\n+        ret_code=0,\n+        args=[\n+            fix,\n+            [\n+                "--disable-progress-bar",\n+                "test/fixtures/linter/multiple_sql_errors.sql",\n+                "--quiet",\n+                "-x",\n+                "_fix",\n+            ],\n+            # Test with the confirmation step.\n+            "y",\n+        ],\n+    )\n+    normalised_output = result.output.replace("\\\\", "/")\n+    assert normalised_output.startswith(\n+        """1 fixable linting violations found\n+Are you sure you wish to attempt to fix these? [Y/n] ...\n+== [test/fixtures/linter/multiple_sql_errors.sql] FIXED\n+All Finished"""\n+    )\n+\n+\n def test__cli__fix_multiple_errors_show_errors():\n-    """Basic checking of lint functionality."""\n+    """Test the fix --show-lint-violations option."""\n     result = invoke_assert_code(\n         ret_code=1,\n         args=[\n',
 'problem_statement': 'Enable quiet mode/no-verbose in CLI for use in pre-commit hook\nThere seems to be only an option to increase the level of verbosity when using SQLFluff [CLI](https://docs.sqlfluff.com/en/stable/cli.html), not to limit it further.\r\n\r\nIt would be great to have an option to further limit the amount of prints when running `sqlfluff fix`, especially in combination with deployment using a pre-commit hook. For example, only print the return status and the number of fixes applied, similar to how it is when using `black` in a pre-commit hook:\r\n![image](https://user-images.githubusercontent.com/10177212/140480676-dc98d00b-4383-44f2-bb90-3301a6eedec2.png)\r\n\r\nThis hides the potentially long list of fixes that are being applied to the SQL files, which can get quite verbose.\n',
 'hints_text': '',
 'created_at': '2023-04-16T14:24:42Z',
 'version': '1.4',
 'FAIL_TO_PASS': '["test/cli/commands_test.py::test__cli__fix_multiple_errors_quiet_force", "test/cli/commands_test.py::test__cli__fix_multiple_errors_quiet_no_force"]',
 'PASS_TO_PASS': '["test/cli/commands_test.py::test__cli__command_directed", "test/cli/commands_test.py::test__cli__command_dialect", "test/cli/commands_test.py::test__cli__command_no_dialect", "test/cli/commands_test.py::test__cli__command_parse_error_dialect_explicit_warning", "test/cli/commands_test.py::test__cli__command_parse_error_dialect_implicit_warning", "test/cli/commands_test.py::test__cli__command_dialect_legacy", "test/cli/commands_test.py::test__cli__command_extra_config_fail", "test/cli/commands_test.py::test__cli__command_lint_stdin[command0]", "test/cli/commands_test.py::test__cli__command_lint_stdin[command1]", "test/cli/commands_test.py::test__cli__command_lint_stdin[command2]", "test/cli/commands_test.py::test__cli__command_lint_stdin[command3]", "test/cli/commands_test.py::test__cli__command_render_stdin", "test/cli/commands_test.py::test__cli__command_lint_parse[command0]", "test/cli/commands_test.py::test__cli__command_lint_parse[command1]", "test/cli/commands_test.py::test__cli__command_lint_parse[command2]", "test/cli/commands_test.py::test__cli__command_lint_parse[command3]", "test/cli/commands_test.py::test__cli__command_lint_parse[command4]", "test/cli/commands_test.py::test__cli__command_lint_parse[command5]", "test/cli/commands_test.py::test__cli__command_lint_parse[command6]", "test/cli/commands_test.py::test__cli__command_lint_parse[command7]", "test/cli/commands_test.py::test__cli__command_lint_parse[command8]", "test/cli/commands_test.py::test__cli__command_lint_parse[command9]", "test/cli/commands_test.py::test__cli__command_lint_parse[command10]", "test/cli/commands_test.py::test__cli__command_lint_parse[command11]", "test/cli/commands_test.py::test__cli__command_lint_parse[command12]", "test/cli/commands_test.py::test__cli__command_lint_parse[command13]", "test/cli/commands_test.py::test__cli__command_lint_parse[command14]", "test/cli/commands_test.py::test__cli__command_lint_parse[command15]", "test/cli/commands_test.py::test__cli__command_lint_parse[command16]", "test/cli/commands_test.py::test__cli__command_lint_parse[command17]", "test/cli/commands_test.py::test__cli__command_lint_parse[command18]", "test/cli/commands_test.py::test__cli__command_lint_parse[command19]", "test/cli/commands_test.py::test__cli__command_lint_parse[command20]", "test/cli/commands_test.py::test__cli__command_lint_parse[command21]", "test/cli/commands_test.py::test__cli__command_lint_parse[command22]", "test/cli/commands_test.py::test__cli__command_lint_parse[command23]", "test/cli/commands_test.py::test__cli__command_lint_parse[command24]", "test/cli/commands_test.py::test__cli__command_lint_parse[command25]", "test/cli/commands_test.py::test__cli__command_lint_parse[command26]", "test/cli/commands_test.py::test__cli__command_lint_parse_with_retcode[command0-1]", "test/cli/commands_test.py::test__cli__command_lint_parse_with_retcode[command1-1]", "test/cli/commands_test.py::test__cli__command_lint_parse_with_retcode[command2-1]", "test/cli/commands_test.py::test__cli__command_lint_parse_with_retcode[command3-0]", "test/cli/commands_test.py::test__cli__command_lint_parse_with_retcode[command4-0]", "test/cli/commands_test.py::test__cli__command_lint_parse_with_retcode[command5-2]", "test/cli/commands_test.py::test__cli__command_lint_parse_with_retcode[command6-1]", "test/cli/commands_test.py::test__cli__command_lint_parse_with_retcode[command7-1]", "test/cli/commands_test.py::test__cli__command_lint_parse_with_retcode[command8-1]", "test/cli/commands_test.py::test__cli__command_lint_parse_with_retcode[command9-2]", "test/cli/commands_test.py::test__cli__command_lint_warning_explicit_file_ignored", "test/cli/commands_test.py::test__cli__command_lint_skip_ignore_files", "test/cli/commands_test.py::test__cli__command_lint_ignore_local_config", "test/cli/commands_test.py::test__cli__command_lint_warning", "test/cli/commands_test.py::test__cli__command_versioning", "test/cli/commands_test.py::test__cli__command_version", "test/cli/commands_test.py::test__cli__command_rules", "test/cli/commands_test.py::test__cli__command_dialects", "test/cli/commands_test.py::test__cli__command__fix[LT01-test/fixtures/linter/indentation_errors.sql0]", "test/cli/commands_test.py::test__cli__command__fix[LT01-test/fixtures/linter/whitespace_errors.sql]", "test/cli/commands_test.py::test__cli__command__fix[LT01-test/fixtures/linter/indentation_errors.sql1]", "test/cli/commands_test.py::test__cli__command__fix[LT02-test/fixtures/linter/indentation_error_hard.sql]", "test/cli/commands_test.py::test__cli__fix_error_handling_behavior[1_lint_error_1_unsuppressed_parse_error]", "test/cli/commands_test.py::test__cli__fix_error_handling_behavior[1_lint_error_1_unsuppressed_templating_error]", "test/cli/commands_test.py::test__cli__fix_error_handling_behavior[1_lint_error_1_suppressed_parse_error]", "test/cli/commands_test.py::test__cli__fix_error_handling_behavior[0_lint_errors_1_unsuppressed_parse_error]", "test/cli/commands_test.py::test__cli__fix_error_handling_behavior[0_lint_errors_1_suppressed_parse_error]", "test/cli/commands_test.py::test__cli__fix_error_handling_behavior[1_lint_error_1_unsuppressed_parse_error_FIX_EVEN_UNPARSABLE]", "test/cli/commands_test.py::test__cli__fix_error_handling_behavior[2_files_with_lint_errors_1_unsuppressed_parse_error]", "test/cli/commands_test.py::test_cli_fix_even_unparsable[command-line-False]", "test/cli/commands_test.py::test_cli_fix_even_unparsable[command-line-True]", "test/cli/commands_test.py::test_cli_fix_even_unparsable[config-file-False]", "test/cli/commands_test.py::test_cli_fix_even_unparsable[config-file-True]", "test/cli/commands_test.py::test__cli__fix_loop_limit_behavior[--", "test/cli/commands_test.py::test__cli__command_fix_stdin[select", "test/cli/commands_test.py::test__cli__command_fix_stdin[", "test/cli/commands_test.py::test__cli__command_format_stdin[select", "test/cli/commands_test.py::test__cli__command_format_stdin[", "test/cli/commands_test.py::test__cli__command_fix_stdin_logging_to_stderr", "test/cli/commands_test.py::test__cli__command_fix_stdin_safety", "test/cli/commands_test.py::test__cli__command_fix_stdin_error_exit_code[create", "test/cli/commands_test.py::test__cli__command_fix_stdin_error_exit_code[select", "test/cli/commands_test.py::test__cli__command__fix_no_force[LT01-test/fixtures/linter/indentation_errors.sql-y-0-0]", "test/cli/commands_test.py::test__cli__command__fix_no_force[LT01-test/fixtures/linter/indentation_errors.sql-n-1-1]", "test/cli/commands_test.py::test__cli__command_parse_serialize_from_stdin[None-yaml]", "test/cli/commands_test.py::test__cli__command_parse_serialize_from_stdin[None-json]", "test/cli/commands_test.py::test__cli__command_parse_serialize_from_stdin[outfile-yaml]", "test/cli/commands_test.py::test__cli__command_parse_serialize_from_stdin[outfile-json]", "test/cli/commands_test.py::test__cli__command_lint_serialize_from_stdin[select", "test/cli/commands_test.py::test__cli__command_lint_serialize_from_stdin[SElect", "test/cli/commands_test.py::test__cli__command_fail_nice_not_found[command0]", "test/cli/commands_test.py::test__cli__command_fail_nice_not_found[command1]", "test/cli/commands_test.py::test__cli__command_lint_nocolor", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[None-human]", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[None-yaml]", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[None-json]", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[None-github-annotation]", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[None-github-annotation-native]", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[None-none]", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[outfile-human]", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[outfile-yaml]", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[outfile-json]", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[outfile-github-annotation]", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[outfile-github-annotation-native]", "test/cli/commands_test.py::test__cli__command_lint_serialize_multiple_files[outfile-none]", "test/cli/commands_test.py::test__cli__command_lint_serialize_github_annotation", "test/cli/commands_test.py::test__cli__command_lint_serialize_github_annotation_native", "test/cli/commands_test.py::test__cli__command_lint_serialize_annotation_level_error_failure_equivalent[github-annotation]", "test/cli/commands_test.py::test__cli__command_lint_serialize_annotation_level_error_failure_equivalent[github-annotation-native]", "test/cli/commands_test.py::test___main___help", "test/cli/commands_test.py::test_encoding[utf-8-ascii]", "test/cli/commands_test.py::test_encoding[utf-8-sig-UTF-8-SIG]", "test/cli/commands_test.py::test_encoding[utf-32-UTF-32]", "test/cli/commands_test.py::test_cli_encoding[utf-8-command-line-False]", "test/cli/commands_test.py::test_cli_encoding[utf-8-SIG-command-line-True]", "test/cli/commands_test.py::test_cli_encoding[utf-8-config-file-False]", "test/cli/commands_test.py::test_cli_encoding[utf-8-SIG-config-file-True]", "test/cli/commands_test.py::test_cli_no_disable_noqa_flag", "test/cli/commands_test.py::test_cli_disable_noqa_flag", "test/cli/commands_test.py::test_cli_get_default_config", "test/cli/commands_test.py::TestProgressBars::test_cli_lint_disabled_progress_bar", "test/cli/commands_test.py::TestProgressBars::test_cli_lint_disabled_progress_bar_deprecated_option", "test/cli/commands_test.py::TestProgressBars::test_cli_lint_enabled_progress_bar", "test/cli/commands_test.py::TestProgressBars::test_cli_lint_enabled_progress_bar_multiple_paths", "test/cli/commands_test.py::TestProgressBars::test_cli_lint_enabled_progress_bar_multiple_files", "test/cli/commands_test.py::TestProgressBars::test_cli_fix_disabled_progress_bar", "test/cli/commands_test.py::TestProgressBars::test_cli_fix_disabled_progress_bar_deprecated_option", "test/cli/commands_test.py::test__cli__fix_multiple_errors_no_show_errors", "test/cli/commands_test.py::test__cli__fix_multiple_errors_show_errors", "test/cli/commands_test.py::test__cli__multiple_files__fix_multiple_errors_show_errors", "test/cli/commands_test.py::test__cli__render_fail", "test/cli/commands_test.py::test__cli__render_pass"]',
 'environment_setup_commit': 'd19de0ecd16d298f9e3bfb91da122734c40c01e5'}

Suggest an improvement to documentation
No response

Then I checkout to this base_commit, run FAIL_TO_PASS, is not fail, run PASS_TO_PASS is not pass, why?

Why i can not found tests/test_fields.py in this base_commit ?
Is there something wrong with my usage or with the data?
In [11]: json.loads(dev[55]['FAIL_TO_PASS'])
Out[11]:
['tests/test_fields.py::TestListNested::test_list_nested_only_exclude_dump_only_load_only_propagated_to_nested[only]',
 'tests/test_fields.py::TestListNested::test_list_nested_only_exclude_dump_only_load_only_propagated_to_nested[exclude]',
 'tests/test_fields.py::TestListNested::test_list_nested_only_and_exclude_merged_with_nested[only-expected0]',
 'tests/test_fields.py::TestListNested::test_list_nested_only_and_exclude_merged_with_nested[exclude-expected1]',
 'tests/test_fields.py::TestDictNested::test_dict_nested_only_exclude_dump_only_load_only_propagated_to_nested[only]',
 'tests/test_fields.py::TestDictNested::test_dict_nested_only_exclude_dump_only_load_only_propagated_to_nested[exclude]',
 'tests/test_fields.py::TestDictNested::test_dict_nested_only_and_exclude_merged_with_nested[only-expected0]',
 'tests/test_fields.py::TestDictNested::test_dict_nested_only_and_exclude_merged_with_nested[exclude-expected1]']

In [12]: dev[55]['base_commit']
Out[12]: '456bacbbead4fa30a1a82892c9446ac9efb8055b'

In [13]:

https://github.com/pydicom/pydicom

(pydicom-new) pydicom-new  49a3da4a3 @ git branch
* (HEAD detached at 49a3da4a3)
  main
(pydicom-new)  pydicom-new  49a3da4a3 @ find . -name test_fields.py
(pydicom-new)  pydicom-new  49a3da4a3 @

Regarding types-pkg-resources: See #199

This FAIL_TO_PASS ["test/cli/commands_test.py::test__cli__fix_multiple_errors_quiet_force", "test/cli/commands_test.py::test__cli__fix_multiple_errors_quiet_no_force"] in the git checkout to base_commit 'a820c139ccbe6d1865d73c4a459945cd69899f8f' will fail ?  @klieret

Hi. Not sure if you already answered the question yourself, because you closed it. But some of the tests are added by the gold patch and so are meant to fail before the gold patch is applied (i.e., on the base patch). This is explained in detail in the swe-B paper.


AWS Auth v4 Part 1: Authorization header auth without payload sha256 verification

This PR is the first part to implement AWS version 4 authentication scheme. [1]
Subsequent tasks are #1059 #1058 #1060 .
This PR includes:

Implement authorization header / non- aws-chunked case.
Payload sha256 verification is out of scope (see #1059 )
Test v4 Authorization header cases by boto_test
Keep boto tests of v2 auth along with v4
Kill switch of v4 auth and disabled by default

[1] Authenticating Requests (AWS Signature Version 4) - Amazon Simple Storage Service
http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html

testing, testing...
[posted via JIRA by Shunichi Shinohara]

I would recommend squashing several fix to make it comprehensive and bisectable.

Did some interactive rebase and force pushed :fire:

I will add some eqc check at next sprint.

TODO: we have to add expiration and timestamp validation at string_to_sign_v4/3 like v2.

Replaced by #1064.


feat(ui): Improve the banner component

Improve the banner component by supporting long texts. Also: parts are defined as Widget rather than a String or a specific widget such as FlexImage for more flexibility.

Also in this PR:

More controls on the widgetbook page
Widgetbook pages re-organized
Additional banner example in the playground
Deploying instructions for the playground web app

The playground has been deployed with those changes


Using Nylas Kotlin v3 SDK, create a code sample to delete a user grant

Using Nylas Kotlin v3 SDK, create a code sample to delete a user grant

@relaxedtomato can you assign it to me?

@relaxedtomato PR submitted

Closed by PR #107


[Service Bus] Remove test reference in src

/azp run js - servicebus - tests

Looks okay. I do wish we could just establish that the value of the error is undefined and just not keep handling it

undefined instanceOf MessagingError would result in false. So, it's fine.

(there are two spots in there where we properly handle it but it's not obvious).

What two spots, @richardpark-msft ?

4 tests failed in the browser

The uncaught TypeError is from heat.
I was able to repro the issue in the browser even in track 1 (Since it didn't have #RunInBrowser tag, the test did not execute in track 1).

/cc - @chradek


Using accordion class instead of card

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
✔

Fixed issues
https://v5.getbootstrap.com/docs/5.0/components/accordion/

accordion-footer is not a thing, so removed.

I'm not happy yet. The btn class should not be there anymore/

OK. Please ping us when you're ready for review. There's a special button for that btw.:

I was looking for that option, after I saw you do that! Thanks :)

Ready for review!

👍


Update index.html

Please note this should likely qualify for invalid label to not get counted towards the hacktoberfest goal: https://hacktoberfest.digitalocean.com/details/#spam
The user has registered with GitHub only some hours ago and spammed other projects with such useless PRs as well.


Inject a tag to builds to determine where they came from

For example, we can have an "AppImage" tag, or an "installer" or "standalone" tag for Windows. We can then send that to Mixpanel.

We should probably break down "installer" into "downloaded from the Etcher website" and "installed by chocolately"? Or is that level of distinction not possible? Does "standalone" mean the "portable" version?
Similarly on Linux, it might be nice if we could tell if the user had installed the .deb file by downloading it from S3, or if they'd installed it from bintray.


bump actions CI to jdk16 and include dragonwell

@gdams @karianna @M-Davies This really needs a doc change alongside the one in https://github.com/AdoptOpenJDK/openjdk-build/pull/2403

@gdams @karianna @M-Davies This really needs a doc change alongside the one in https://github.com/AdoptOpenJDK/openjdk-build/pull/2403


chore: remove unnecessary final modifiers

Remove all final modifiers on the io.github.kennedykori.utils.ObjectUtils class static methods. This is because the class is final.

:tada: This PR is included in version 2.0.0-dev.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

v2.0.0
GitHub release

Your semantic-release bot :package::rocket:


The offset of mcontext_t inside the libc::ucontext_t struct is incorrect

Cpp code:
DEBUG("off: 0x%x\n", (size_t)(&((ucontext_t *) data)->uc_mcontext) - (size_t)data);
output:
off: 0xB0
Rust code:
let ucontext = data as *const libc::ucontext_t;
let start = ucontext as usize;
let uc_mcontext_ref = &(*ucontext).uc_mcontext;
let uc_mcontext_ptr = uc_mcontext_ref as *const _;
let end = uc_mcontext_ptr as usize;
log::info!("off:0x{:x}",end -star);
output:
off:0x30
build for target aarch64-linux-android

would you be able to produce a PR ?


bluetooth-hci-socket can't find my bluetooth device

i wrote some program using ble, but it only not working in my new laptop.
i wonder that this library can't connect to BLE 4.1 device?
enviromnet

Dell XPS13 9350
ble driver : Dell Wireless 1820A Bluetooth 4.1 LE

error log
\node_modules\bluetooth-hci-socket\lib\usb.js:50
throw new Error('No compatible USB Bluetooth 4.0 device found!');
^
Error: No compatible USB Bluetooth 4.0 device found!
at BluetoothHciSocket.bindUser (C:\Users\Nacer\Documents\1.nBand\BandLogger-master\BandLogger-master\node_modules\bluetooth-hci-socket\lib\usb.js:50:11)
at BluetoothHciSocket.bindRaw (C:\Users\Nacer\Documents\1.nBand\BandLogger-master\BandLogger-master\node_modules\bluetooth-hci-socket\lib\usb.js:28:8)
at Hci.init (C:\Users\Nacer\Documents\1.nBand\BandLogger-master\BandLogger-master\node_modules\noble\lib\hci-socket\hci.js:89:16)
at NobleBindings.init (C:\Users\Nacer\Documents\1.nBand\BandLogger-master\BandLogger-master\node_modules\noble\lib\hci-socket\bindings.js:83:13)
at new Noble (C:\Users\Nacer\Documents\1.nBand\BandLogger-master\BandLogger-master\node_modules\noble\lib\noble.js:67:18)
at Object. (C:\Users\Nacer\Documents\1.nBand\BandLogger-master\BandLogger-master\node_modules\noble\index.js:3:18)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)

@Galch only the following adapters are whitelisted now:
https://github.com/sandeepmistry/node-bluetooth-hci-socket#compatible-bluetooth-40-usb-adapters
You can try adding the USB id's of yours here: https://github.com/sandeepmistry/node-bluetooth-hci-socket/blob/master/lib/usb.js#L66, if it works please submit a pull request so it can be added to the whitelist.

I'm closing this for now, due to lack of discussion.

Same issue here - as far as I can tell the Atheros QCA6174 that does BLE (and Wifi) isn't a USB device. And even if I add a BLE USB device that I know works, Windows won't enable it because it knows there i already an active BLE adaptor!


JsonWriter mis-handles control characters

When using JObject.FromObject(), or a custom converter which has:
public override void WriteJson(JsonWriter writer, object value, JsonSerializer serializer)
{
if (value == null)
return;

string s = String.Join("\r\n", (string[]) value); // the writer messes up \r\n strings
writer.WriteValue(s);
}

the resulting piece of text withing the JSON string will be:
String1\\r\\nString2\\r\\nString3
It appears that the JsonWrite is 'escaping' the \
rather than treating the \r as a single control character.

That JSON is correct. Line breaks are supposed to be escaped.
http://json.org/

James,
My point is that they are double-escaped.
Any normal line break is shown as \n or \r.
It appears that the \ is being escaped, resulting in a sequence of \n
Dave
Sent from my iPhone

On 28 Dec 2018, at 20:20, James Newton-King<EMAIL_ADDRESS>wrote:
Closed #1942.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


potentially misleading error message

I frequently have seen the below error message and have become desensitized to it, and assume it's harmless, but have been all the while curious if it's something that shouldn't bubble up to the user:
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 3.147s, Critical Path: 1.83s
INFO: 0 processes.
FAILED: Build did NOT complete successfully
ERROR: Build failed. Not running target
FAILED: Build did NOT complete successfully
iBazel [6:48PM]: Error starting process: fork/exec /var/folders/5g/4ssx2_117rv3fty7pqqv9wpc0000gp/T/bazel_script_path351664668: permission denied

It frequently follows errors that explain why it happened, so it makes sense in context, but the fact that it says "Not running target", but then seems to proceed to run the target is suspicious. Is this something that is better caught and swallowed?

Could you provide a little more context on what you're doing to invoke this? I don't see this on a regular basis. Is this a build or run what kind of target are you messing with? Is this happening exclusively in one kind of repo? What version of ibazel/bazel are you on?

I have a repo where I usually reproduce things. I can make a branch there and provide it here.


Can Oriented Rcnn run without requiring nvidia gpu

Can Oriented Rcnn run without requiring nvidia gpu or exported to onnx format. If not, is it easy to implement these features?

This repo can be built on the CPU, but the onnx format is not supported yet.


feat(auth): Enable default values for params

This PR hopes to allow the ability for consumers to add default values for parameters that will be sent up alongside the oauth2 authorizationCode request. Currently, you can add parameters that must be filled out by the user input when setting up a profile, this change allows us to define default values as a way to encode query params such as audience client_id params without needing the user to configure it themselves.

@mgagliardo91 also consider checking out https://rest.sh/ (https://github.com/danielgtaylor/restish) I've been thinking of suggesting an OpenAPI extension to auto-configure parts of the auth there. If you don't explicitly need code generation it might be a good option.


Adding the rest of Morphir methods

I didn't mention it on each instance but it would be great to implement eraseAttributes in terms of mapAttributes instead of just returning an empty instance as that is incorrect.


Should we allow privileged containers? docker inside docker?

A security issue.
To make things simpler to some applications, the user can have privileged containers and docker inside docker.
Should this be allowed despite the risk?
Docker inside docker is really useful to package databases and code in a single image.
It can be done by calling the host's docker (right way) or by installing docker inside the image (wrong way).

I think for now we should not allow or promote the use of docker inside
docker. We have to think also in people trying to run these images inside
clusters and larger infrastructures. If we allow something with a certain
degree of risk, certainly, sysadmins will not allow the use of it on their
systems.
On Tue, Aug 25, 2015 at 10:08 AM Saulo<EMAIL_ADDRESS>wrote:

A security issue.
To make things simpler to some applications, the user can have privileged
containers and docker inside docker.
Should this be allowed despite the risk?
Docker inside docker is really useful to package databases and code in a
single image.
It can be done by calling the host's docker (right way) or by installing
docker inside the image (wrong way).
—
Reply to this email directly or view it on GitHub
https://github.com/BioDocker/biodocker/issues/24.

perfect. my idea exactly.
That said, running docker is never "safe". anyone who can run docker can use -v/:/data and change any settings of the host computer. :D

Can we close @sauloal? and perhaps include an sentence in the specification about it?

@ypriverol , I think we could close it but I like to leave the questions open for at least one week so that other members can have the chance of voicing their opinion.
I'm aware that I'm using "issues" as a replacement for a forum :D


InstrumentedHandler is incompatible with Jetty version in 2.0.0-rc13

Asynchronous responses raises an exception from com.codahale.metrics.jetty9.InstrumentedHandler because DISPATCHED is not a member of enum type org.eclipse.jetty.server.HttpChannelState.State (org.eclipse.jetty:jetty-server:9.4.23.v20191118)

WARN  o.e.jetty.server.HttpChannelState - java.lang.NoSuchFieldError: DISPATCHED while invoking onComplete listener com.codahale.metrics.jetty9.InstrumentedHandler$7@66d27937

See also https://github.com/eclipse/jetty.project/issues/4169

@skradel Thanks for reporting this!
Could you please check if the problem still exists with Dropwizard 2.0.0-rc14?

This appears quieted in metrics-jetty9:4.1.2 although one can't help noticing the conspicuous presence of:

private HttpChannelState.State DISPATCHED_HACK;


Git command never exits in terminal window

Type: Bug
Run some git commands such as 'git diff'
Observe the command prompt never returns.
'q' / ctrl+c / break all have no effect.
Open git.exe in debugger - see it is blocked/waiting indefinitely.
I don't have these issues in a normal (standalone) terminal window.
 It looks like you may be using an old version of VS Code, the latest stable release is 1.77.3. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I can't reproduce and I haven't seen other reports like this. Can you share your settings.json? Maybe something in there is impacting things.
You could also try disable shell integration and see if that helps.

Thanks! I went to repro, but after reproducing reliable for several weeks, something has apparently changed and it's now no-repro here also. For future reference, it triggered most often for commands with pagination.

OK, I can repro again:

start a terminal (it starts with about a dozen rows of space)
run a command which uses a pager e.g. git log
Maximize the terminal pane
Page down (space) a few pages
Terminal goes unresponsive (even to ctrl+c etc)
Kill 'less.exe' via task manager and all returns to normal

Interestingly, this does reproduce for me in windows terminal. So perhaps not vscode specific after all.
One vscode specific difference - ctrl+break interrupts & gets back to working state in windows terminal.
In vscode, ctrl+break seems to do nothing & task manager kill is necessary.
vscode 1.78.2
git version 2.39.2.windows.1

Interestingly, this does reproduce for me in windows terminal. So perhaps not vscode specific after all.

Sounds like a conpty problem then. Here's my standard reply for this type of upstream issue 🙂

This issue seems to originate from an upstream component and is not something VSCode can fix by making a change to our code. As such, I will go ahead and close it. Please try to reproduce in Windows Terminal and report to microsoft/terminal with repro steps.
If you cannot reproduce in Windows Terminal, chances are it's fixed in a later version of Windows. You can read more about how we consume conpty here. Thanks for understanding.
/label upstream terminal-conpty windows

Thanks Tryiar, will do. https://github.com/microsoft/terminal/issues/15386
It still seems like there may be an issue in forwarding 'break' signals. But perhaps that's with terminal component also :)


Windows target (mingw) with forceGtk build fails to find GTK entry point.

While building for a windows target works fine, using -d:forceGtk results in an error:
The procedure entry point at atk_hyperlink_impl_get_type could not be located in the dynamic link library...

I confirmed that the mentioned DLL does exist in the path given in the error message.

I have no idea, what tries to call the procedure atk_hyperlink_impl_get_type. NiGui's Gtk binding does not include this procedure. Do other Gtk 3 programs work on your machine?

They do.

this problem is related to the nim compiler.
i examined this dll in a simple way and encountered the same error!
("libgtk-3-0.dll" exists in the directory)

in general, the nim compiler does not have the ability to read any dll file.
for example, i made dll file with flat assembler and used it in fasm & cpp but this dll file didn't load in nim

apparently no longer relevant, please re-open if still reproducible


OpsWorks apps.json

Hi @atmos in order to set the opsworks feature, how can I pass the
"aws_access_key_id": "",
"aws_secret_access_key" : ""
are these grabbed from the environment where hubot is installed?
Thank you very much!
JL

It'd look something like this. We could look at merging these in or something from an env var. In my testing I used separate IAM keys per application environment.
"camo": {
  "provider": "aws_opsworks",
  "repository": "atmos/camo",
  "environments": ["production", "staging"],

  "opsworks": {
    "production": {
      "app_id": "<app_id>",
      "stack_id": "<stack_id>",
      "aws_access_key_id": "",
      "aws_secret_access_key" : ""
    }
  }
}

Yes nice, we'd do the same, thanks!

Strange, I got "Bad credentials" but I can deploy with those credentials and my token has "repo_deployment, user"

Can you curl the repo in question with something like curl https://api.github.com/repos/me/project/deployments?access_token=<yourtoken>?

{
"message": "Not Found",
"documentation_url": "https://developer.github.com/v3"
}

It looks like whatever token you're using doesn't have access to that repo.
If you curl -vv https://api.github.com/user does it return the same user
you intend and have the appropriate scopes in the response headers?
On Thu, Apr 9, 2015 at 10:53 AM, JoseLuis Torres<EMAIL_ADDRESS>wrote:

{
"message": "Not Found",
"documentation_url": "https://developer.github.com/v3"
}
—
Reply to this email directly or view it on GitHub
https://github.com/atmos/hubot-deploy/issues/40#issuecomment-91309418.

[
  {
    "url": "https://api.github.com/repos/praxik/roisite/deployments/527613",
    "id": 527613,
    "sha": "cbe5563fb40a9e95c1800c52a1a3a5e03cc4aaff",
    "ref": "development",
    "task": "deploy",
    "payload": {
      "name": "pzm",
      "hosts": "",
      "notify": {
        "room": "Shell",
        "user": "Shell",
        "adapter": "shell",
        "message_thread": "unknown"
      },
      "config": {
        "provider": "aws_opsworks",
        "repository": "redacted/redacted",
        "environments": [
          "web_development"
        ],
        "opsworks": {
          "web_development": {
            "app_id": "redacted",
            "stack_id": "redacted",
            "aws_access_key_id": "redacted",
            "aws_secret_access_key": "redacted"
          }
        }
      }
    },
    "environment": "web_development",
    "description": "Deploying from hubot-deploy-v0.6.51",
    "creator": {
      "login": "joseluistorres",
      "id": 216166,
      "avatar_url": "https://avatars.githubusercontent.com/u/216166?v=3",
      "gravatar_id": "",
      "url": "https://api.github.com/users/joseluistorres",
      "html_url": "https://github.com/joseluistorres",
      "followers_url": "https://api.github.com/users/joseluistorres/followers",
      "following_url": "https://api.github.com/users/joseluistorres/following{/other_user}",
      "gists_url": "https://api.github.com/users/joseluistorres/gists{/gist_id}",
      "starred_url": "https://api.github.com/users/joseluistorres/starred{/owner}{/repo}",
      "subscriptions_url": "https://api.github.com/users/joseluistorres/subscriptions",
      "organizations_url": "https://api.github.com/users/joseluistorres/orgs",
      "repos_url": "https://api.github.com/users/joseluistorres/repos",
      "events_url": "https://api.github.com/users/joseluistorres/events{/privacy}",
      "received_events_url": "https://api.github.com/users/joseluistorres/received_events",
      "type": "User",
      "site_admin": false
    },
    "created_at": "2015-04-09T13:36:29Z",
    "updated_at": "2015-04-09T13:36:29Z",
    "statuses_url": "https://api.github.com/repos/redacted/redacted/deployments/527613/statuses",
    "repository_url": "https://api.github.com/repos/redacted/redacted"
  },
  {
    "url": "https://api.github.com/repos/redacted/redacted/deployments/522676",
    "id": 522676,
    "sha": "b9203969b5a906b1c2aac2d7124543c10613dbdd",
    "ref": "development",
    "task": "deploy",
    "payload": {
      "name": "pzm",
      "hosts": "",
      "notify": {
        "room": "joseluistorres",
        "user": "joseluistorres",
        "adapter": "slack",
        "message_thread": "unknown"
      },
      "config": {
        "provider": "aws_opsworks",
        "repository": "praxik/roisite",
        "environments": [
          "web_development"
        ],
        "opsworks": {
          "web_development": {
            "app_id": "redacted",
            "stack_id": "redacted"
          }
        }
      }
    },

So is it creating them properly now?

Yes it is, ha, perhaps I'm misunderstanding this, can this events trigger opswork to generate the real "deployment" there?
:blush:

Yeah, in the past I configured the opsworks github-service integration in my repository settings.
The chat stuff triggers a deployment event, and the github-service picks up that deployment event and does the actual deployment to opsworks.

Oh ok, I see, I didn't know that, let me ask for that integration, thanks again!


Bench nomad exec

Exec task driver and standalone Nomad Server and Clients (no -dev mode)

Local/testing environment

Bye bye -dev mode, now both Nomad Servers and Clients are started independently

Can automate as many Nomad Clients as needed (wb backend pass nomad server|client start|stop NAME)

Optional stateful Nomad Agents instead of starting and stopping on every run

Only when using the Nomad exec Task Driver Clients are run as root

Create symlinks to every Task's stdout and stderr file for easier/live monitoring and debugging

Cloud deployments

Add a new mode called nomadexec that uses SRE's patched version of Nomad

As part of the switch-over to directly-executable derivations, the Nomad Job specification file is self contained. Every script and config file is included as a template stanza only leaving outside the genesis folder.

Created an ad-hoc "container-specs.json" file with GitHub references (towards being able to benchmark any cardano-node commit from any workbench version).

The workbench checks that the commit being tested is publicly available on GitHub

Fetch all Nomad (some dynamically) generated start.sh and config.json files for log and debugging purposes

Both local and cloud

Control and monitoring of Nomad Jobs was refactored in line with the important role it has

Removal of all locality assumptions

Removal of all 1-1 allocation ID-task name relation assumptions

Others

Fixed how wb backend calls backend specific subcommands

bors merge

bors merge

bors merge


oci: Make OCI config file and bundle directory paths public.

The OCI configuration file path and the OCI bundle directory need to be
public to allow them to be used by runtime implementations.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

Coverage remained the same at 67.404% when pulling 0604e92364b3bb8adb4c3bcc633421e70d976098 on jodh-intel:make-oci-annotation-keys-public into d274a91fe3026edc72590c816e5f46e97e0a3e0b on containers:master.

These variables stutter now oci.OCIFooBar. Would be nicer without it.

@dlespiau - agreed. Branch updated.

lgtm

Coverage remained the same at 67.404% when pulling 2d8cecc2a0f3a31134f10813268d758fd6e319a9 on jodh-intel:make-oci-annotation-keys-public into d274a91fe3026edc72590c816e5f46e97e0a3e0b on containers:master.

LGTM


Update zio, zio-streams, zio-test, ... to 2.0.19

About this PR
📦 Updates

dev.zio:zio
dev.zio:zio-streams
dev.zio:zio-test
dev.zio:zio-test-sbt

from 2.0.15 to 2.0.19
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #555.


 This is not an easy fix, I naively thought that I don't need to worry about older versions of m^2 and that the loaders' module resolution would handle multiple versions of the same jar as if it were a mod. But it looks like that's not the case and I'll need to handle it myself. If you want to launch and keep more culling you'll need to remove Elytra Trims unfortunately, apologies.

alright! so as a temp fix i will need to temp remove elytra trims?

I have made about 30 prs to different repos providing a fix. The issue will persist until mods update but at least the cause has been dealt with.

elytra trims just got updated to 3.5.4 , did the issue with mixinsquared get fixed? iirc i had to  remove this mod for this issue

f you want to launch and keep more culling you'll need to remove Elytra Trims unfortunately, apologies.


chore: bdd-gh-1584528340 to 0.0.1

chore: Promote bdd-gh-1584528340 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


pretrained VMamba weights cannot be downloaded

The download link doesn't work.

Hi, I've uploaded the weight here

Thanks!

1325473360
@.***

------------------ 原始邮件 ------------------
发件人: "Zifu @.>;
发送时间: 2024年6月18日(星期二) 晚上7:51
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [zifuwan/Sigma] pretrained VMamba weights cannot be downloaded (Issue #17)
Hi, I've uploaded the weight here
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


[Suggestion] Adding wheight to creategroup-command

Adding a second argument for directly set a groupwheight on /lp creategroup
Like: /lp creategroup <new group> <wheight>

What's the benefit?
Seems a bit unnecessary to add an extra argument, just for the sake of saving one extra command execution.
It seems logical that the creategroup command should do just that, and nothing more.


Geting Nan Inf errors for the TangentSpace(metric='riemann') transform

Sorry to bother you, I have one question which I don't know the answer.
First I would like to say it is great to see you apply Information Geometry to some real world problems and get amazing results, I am also using Information Geometry in my research, but applied to the field of entropy.
I am trying a simple example of pyRiemann, first I pass the data through covariance
cov_data_ = pyRiemannCovariances(epochs_data_)

then calculate tangent space
ts = pyRiemannTangentSpace(metric='riemann')
data_ = ts.fit_transform(cov_data_)

however, it give me a ValueError, saying array must not contain infs or NaNs.
I checked the matrix of cov_data_ and epochs_data_, there is no Inf or Nan.
I am wondering what are the conditions for my data in order for this to work?
Does this mean one or more of the covariance matrix have zero det, but what is
wrong with the original data so it have zero det.In other word, what is the condition
for my data so that the covariance matrix have zero det?
For example, if my data is
array([[[1, 4],
        [2, 5],
        [3, 6]],

       [[3, 4],
        [1, 2],
        [3, 6]]])

it will give me the same infs or NaNs error.
Thanks in advance.

Hi,
This happen when your covariance matrices are not positive definite.
This is a very common problem that occurs when 2 channels are colinear, or when you have less time sample than channels.
Riemannian geometry imply you have definite positive covariance matrices. If it not the case, you should use regularization. you can add regularization in the covariance estimator, like this :
cov_data_ = pyRiemann.Covariances(estimator='lwf').fit_transform(epochs_data_)
it should works fine with any data, but be aware that regularization can degrade perf by modifying the covariance structure.

Hi Alex,
Thanks for the reply :)
I add estimator='lwf' to the origninal data, it works!
However, the small 235 random data example still does not work
epoch_data_ = np.array([[[ 1,  4,  7, 10,  4],
        [ 2,  5,  8,  8,  8],
        [ 3,  6,  9,  2,  2]],

       [[ 1,  2,  3,  6,  2],
        [ 4,  5,  8,  8,  1],
        [ 3,  5,  5,  2,  6]]])

cov_data_ = Covariances(estimator='lwf').fit_transform(epochs_data_) still give me error
I can't figure what's wrong with this fake data, is it possible to regularize this data to make the covariance matrix positive definite?
Bests,
Yunshu

Can you share some data or code. ledoit-wolf estimator is supposed to always give SPD matrices.

When I try to run the same code for the small example this morning, it actually worked. I must have using epochs_data_ instead of epoch_data_ when I do it yesterday, it is my mistake.
The original data is from grasp-n-lift competition in kaggle.
I actually post a question on the forum regarding your "Beat the Benchmark. 0.708" script, but I guess you have not visit the forum today. My question is why EEG are epoched using a window of 2 second before and after the event? I though we are not allowed to use any future data, or I misunderstood the meaning of future data?

Yep, the grasp-n-lift dataset need regularization.
I will answer your question on the forum :)

Hi!
I'm getting the same problem with CospCovariances.
Is there a way to regularize them?
I'm using MEG resting state data, so some of the channels are definitely highly correlated.

Hi.
CospCovariance has a higher risk of non SPD matrix (which is the reason you get nan) because covariance are estimated in the frequency domain using a sliding window.
Try to increased overlap as much as possible.
If it does not work, you Can manualy force the matrices to be SPD with shrinkage.

Ok, I'll try that. Thanks a lot!


Show IPFS hash in WNS table

Display the IPFS (for apps and bots) in the WNS table.
Ideally as a hyperlink to the IPFS console so that the file can be inspected.
Extend the client Registry API @wirelineio/registry-client to support fetching attributes also.
The Registry class should also expose an endpoint property.

Updated registry-client has endpoint property now.


Update to Lit2.0, TS support, issue templates, component registration extension

Is your feature request related to a problem? Please describe.
The badge element is built using Lit1.0 and related dependencies. The element does not support typescript users.  Issue templates and github settings in this repo are outdated. The current badge element is well behind recent versions of core support functions.
This repo does not support TS users.
This repo's issue templates are out of date.
This repo does not support component extension.
Describe the solution you'd like
Update to Lit2.0
Using a Node 18 environment, update all other dependencies. This may include deleting and rebuilding the package-lock.json file and node_modules/ directory then running npm run i to recreate all resources.
Update component registration
Update the following core features of the badge element

Remove the element definition from the element .js file and place into index.js file
Update rollup dependencies and configs to support the new import model

Update typescript support
Update the repo to support typescript. The solution is to use the typescript npm package, add a types npm build script and create a tsconfig.json file.
tsconfig.json example
{
  "include": ["src/**/*.js"], // process the generated JS files from the src js files
  "exclude": [],
  "compilerOptions": {
    // Tells TypeScript to read JS files, as
    // normally they are ignored as source files
    "allowJs": true,
    // Generate d.ts files
    "declaration": true,
    // This compiler run should
    // only output d.ts files
    "emitDeclarationOnly": true,
    "outDir": "dist",
    // go to js file when using IDE functions like
    // "Go to Definition" in VSCode
    "declarationMap": true
  }
}

Update the repo's ISSUE TEMPLATES

update:   .github/ISSUE_TEMPLATE/bug_report.md
update:   .github/ISSUE_TEMPLATE/feature_request.md
update:   .github/ISSUE_TEMPLATE/general-support.md
update:   .github/settings.yml
delete:    .github/ISSUE_TEMPLATE/develop-design-story.md
delete:    .github/ISSUE_TEMPLATE/audit.md
delete:    .github/ISSUE_TEMPLATE/new_wc.md
delete:    .github/ISSUE_TEMPLATE/parent-design-story.md
delete:    .github/ISSUE_TEMPLATE/review-design-story.md
delete:    .github/ISSUE_TEMPLATE/symbol-design-story.md
delete:    .github/ISSUE_TEMPLATE/user-story.md

When reviewing code from the previous issue commit, be sure to include this commit as well.
https://github.com/AlaskaAirlines/auro-badge/commit/fdaddcc8d314decfa891a1930ba90d31293943f2
Exit criteria
This issue will be considered closed once the repo is updated to Lit2.0 and all features and tests operate as expected with all other dependencies updated as well.
This issue can be closed once a .d.ts file is created with the build.
This issue can be closed once the issue templates match the content from the generator repo.
This issue will not be considered complete once the listed core features are updated along with all associated dependencies and all features work as previously expected with node 18 installed.

This issue was copied from #66 by @blackfalcon.

https://github.com/AlaskaAirlines/auro-header/pull/84/commits/a08f2326060c61f9ee7f99b2efb338e4927a2328
https://github.com/AlaskaAirlines/auro-header/pull/84/commits/f4d91f6e8a1a51d56456733dc96c3734e28eaf94
https://github.com/AlaskaAirlines/auro-header/pull/59/files

/duplicate

@fajar-apri-alaska please pay attention to this commit for all the things expected to be addressed with this issue.

https://github.com/AlaskaAirlines/auro-button/pull/210/commits/d8b1dab7b313dbbcad20ad3f21f116fa0e43f105

/duplicate

/duplicate

/duplicate

/duplicate

/duplicate

/duplicate

/duplicate


squash root in BaseModel json encoding

Fixes #911.
This corrects the specific problem described by @peku33, where the response is received by the client as {"__root__": foo}. This change simply converts to foo during json encoding.
Note that these __root__ structures may still exist internally, e.g. {"foo": {"__root__": foo}}. That is a pydantic bug (https://github.com/samuelcolvin/pydantic/issues/1414) with an open PR.

Nice, thank you! :bug: :fire: :tada:


Base class should be stateless

Hi @Power-Maverick,
Took a look at your base class - I think it might fall foul of not being stateless:
https://docs.microsoft.com/en-us/power-apps/developer/data-platform/best-practices/business-logic/develop-iplugin-implementations-stateless
Particularly:
https://github.com/Power-Maverick/Power-Tips/blob/aa9e2de4c698cfc6611d9013c05a09c27916d2ad/Ep-04/PowerTips.Plugins/PowerTips.Plugins.Training/PluginBase.cs#L35
If two instances of the plugin execute at once they'll share the same object, and the context could get overwritten/trashed indeterminately.
Thank you for publishing - there's always stuff in there that I learn.  Please accept this as constructive criticism :)

Thanks for bringing this to my attention. I will work on the fix for the Plugin Base but I am ok with accepting a PR if you already have one ready.


Attempt to read property "name" on null

laravel 11, livewire 3,4 breeze starter kit
create new module and open, get error: Attempt to read property "name" on null from "layout.navigation"

Not sure. Could be related to https://github.com/InterNACHI/modular/pull/63.
To make fixing easier would you mind sharing a repo which reproduces your issue?

Discovered the same thing just about now, dd(auth()->user()); returns null. Currently investigating the cause of this.


feat(huawei CCE): Support huawei CCE kev2

Summary
Fixes # https://github.com/cnrancher/pandaria/issues/2563

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

提交至新分支


fix: absolutely resolve configPath in builder setup to fix HMR in nx/storybook

Closes #1025
📝 Description
A one line fix to solve config dep resolution in nx/storybook:
https://github.com/chakra-ui/panda/blob/fae0d35a225379d66e2d3bb02d01ac5f06802ce0/packages/node/src/builder.ts#L95
This PR also includes an nx sandbox. I thought an nx example might be helpful to others (I've seen a few issues/discussions about it). If not - so fine - happy to remove it. That +6400 diff is enough to give anyone the heeby jeebies 😂

HMR still isn't working in an nx/storybook combination despite https://github.com/chakra-ui/panda/pull/1026 and https://github.com/chakra-ui/panda/pull/1029 (though it did solve it for regular storybook ✅). With a postcss.config.cjs file that looks like this (required to get it running with nx serve my-app AND nx storybook my-app):
module.exports = {
  plugins:
    process.env.NX_TASK_TARGET_TARGET === 'storybook'
      ? [require('@pandacss/dev/postcss')({configPath: './libs/theme/panda.config.ts'})]
      : {'@pandacss/dev/postcss': { configPath: '../../libs/theme/panda.config.ts' }},
};

resolveWithExtension in @pandacss/config/get-mod-deps.ts was trying to find the config in {cwd}{filePath}, resulting in it looking in the wrong places like this:
/Users/harley/oss/panda/sandbox/nx-monorepo/libs/theme/libs/theme/panda.config.ts

Note the double libs/theme/libs/theme.
⛳ Current behavior (updates)
The correct config path is resolved absolutely from setup, and HMR works as expected in nx storybook.
🚀 New behavior
None
💣 Is this a breaking change (Yes/No):
No
📝 Additional Information

Oh man 😂 I was so stoked to finally figure out the issue I didn't even think of that. Can confirm this works:
const path = require('path');

module.exports = {
  plugins: {
    '@pandacss/dev/postcss': {
      configPath:
        process.env.NX_TASK_TARGET_TARGET === 'storybook'
          ? path.resolve('./libs/styled-system/panda.config.ts')
          : '../../libs/styled-system/panda.config.ts',
    },
  },
};


Make CCIG Cobrand / Whitelabel

[x] referrer code = ccig
[x] Logo to come
[x] If a user goes through from this referrer link, skip optional sign-up question.
[x] Add landing page like JeffCo >> Make sure Get Started off landing page, keeps URL params.
[x] Results Page: Add additional language (use Let's Get Set model) Something to the effect of Thanks for filling out MyFriendBen. You've completed you're CCIG registration. Review programs that you might be eligible for. . . something. . . @sydney-devine will sharpen this up later.

@sydney-devine do we want an icon to go with the message? We currently have this for lgs.

@CalebPena let's axe the icon and just keep the background and bold text.

@CalebPena logos - Vertical one is for the landing page

Copy: Thank you for completing your application to join the Colorado Community Insight Group by filling out MyFriendBen. Your application will be processed within 2 - 4 days. In the meantime, we encourage you to explore the benefits and resources that may be available to your family listed below. If you have any questions in the meantime, please feel free to email us at<EMAIL_ADDRESS>

@sydney-devine do we want to add CCIG to the referrer source drop down?

Yes please. Colorado Community Insight Group

Add like 1.5 rem padding between logo and paragraphs.
Unbold the copy.

Ugh Let's double the padding between the logo and header? Sorry, being a little nitpicky now. It just seems smooshed right now.

Looks great ty


Update tutorial with renamed smart contract language

eopsin has been renamed to opshin. This change updates the docs to reflect this change.

Codecov Report

Merging #183 (6fa18b1) into main (8f29313) will decrease coverage by 0.45%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #183      +/-   ##
==========================================
- Coverage   86.23%   85.78%   -0.45%
==========================================
  Files          26       26
  Lines        2767     2814      +47
  Branches      655      672      +17
==========================================
+ Hits         2386     2414      +28
- Misses        287      296       +9
- Partials       94      104      +10

see 8 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


⚠ Slack has degraded performance

In fd8178f, Slack (https://status.slack.com/api/v2.0.0/current) experienced degraded performance:

HTTP code: 200
Response time: 56 ms

Resolved: Slack performance has improved in 81e4b10.


Upgrade to Rebar 3.20

This issue is to track upgrading from Rebar 3.18 to 3.20. This will mean Riak no longer supports OTP-22
This will require:

[ ] https://github.com/vernemq/rebar3_cuttlefish/pull/47
[ ] Potentially resolving diverging basho/cuttlefish with https://github.com/Kyorai/cuttlefish.
[ ] Something along the lines of https://github.com/basho/riak/pull/1107. This current PR will not properly escape JSON (e.g. when creating buckets). I have an updated version but will need to figure out how to integrate with latest Riak as pull/1107 is is out of date. fmt in lib.sh may do this already but it fails on JSON.
[ ] Related to the above: https://github.com/basho/riak_kv/pull/1822/
[ ] Resolving diverging Relx with https://github.com/erlware/relx/issues/918

I imagine some other changes that I'll continue to track.

A note on OTP support.  Riak 3.0.15+ is currently OTP 22 only.  The intention has been for Riak 3.2.1 to be OTP 22 and OTP 25+ (OTP 25 is proven, there's been some initial work on OTP 26).
I have vague memories of past discussions on Slack about whether there should always be an option when upgrading Riak versions to do so without needing an OTP uplift - which I think was the motivation in ensuring backwards compatibility to OTP 22 in 3.2.n.  However, I think we need to be pragmatic.  There are real benefits of aligning Riak with the community, as well as  people willing to help to achieve this.  rebar3 has a clear policy that would at the very least constrain supporting both OTP 22 and OTP 26.  There is also an ongoing release tax with testing Riak across multiple OTP versions.
So I think just as support was (accidentally) dropped for OTP 20 in 3.0.10, it should be OK to drop support for OTP 22 in Riak 3.2.1 or 3.2.2.   So, for example, 3.0.10+ would be OTP 22 only, 3.2.1 would be OTP 25 only and 3.2.2 may be OTP 26 only.
@nsaadouni @hmmr - does this seem OK with you?  I think we have been through this loop before, and I may be guilty of forgetting some potential issues.


Viewer options

Does this viewer have the same options like the web viewer from pdfjs, i.e. print, download, navigation etc.?

This component is mainly for rendering pages as needed by the app's case of use. It isn't a viewer itself but you can find some examples in the docs that you can check also you can use pdf.js api to implement as many option as you need :)


Rework mem opt m2m virtual

Rebased with master

@TeroJaasko didnt you already rebase memory_optimizatons branch with master? Will this PR now duplicate git commit history again ?

Yes, this branch needs cleanup. Or was this PR was supposed to be against master? If so, just press the edit-button and select the target branch to be master, not memory_optimizations.

Maybe I should do it this change directly to master branch.

Now unit tests pass rate is 15/18 with memory_optimizations branch of mbed-client-c.
Failing test cases are:
m2mresource
m2mresourceinstance
m2mbase

Thsi went in via master, closing PR.


Bump go-aserto to fix CVE-2024-21664

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 63.532%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2385

Relevant Lines:
3754

💛  - Coveralls


EXTRUDERS 2

(output status 1
Pasting "DIO" and "-" does not provide a valid preprocessing token)
Located in the configuration.h file
#define EXTRUDERS 1 i
When I want to do EXTRUDERS 2 I get the following error.
I get the same error. I wonder why.
There is a compilation error.
What should I do. Please help me.

I got the same issue.
Do you got a solution for this?


Set current working dir properly for debug adaptor

Fixes an issue with debug adaptor where it fails to startup in some unix envs.
Fixes https://github.com/ballerina-platform/ballerina-lang/issues/18978

Codecov Report

Merging #18977 into next-release will decrease coverage by 0.01%.
The diff coverage is 0%.

@@               Coverage Diff                @@
##           next-release   #18977      +/-   ##
================================================
- Coverage         15.81%    15.8%   -0.02%
================================================
  Files                47       47
  Lines              1258     1259       +1
  Branches            196      196
================================================
  Hits                199      199
- Misses             1046     1047       +1
  Partials             13       13

Impacted Files
Coverage Δ

...ool-plugins/vscode/src/debugger/config-provider.ts
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 69c8572...ca88c35. Read the comment docs.


Feature/copy json

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: IgnaciodeNuevo sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Closed because I did a mistake trying to PR to our repository but instead I did it in Microsoft's one.

@IgnaciodeNuevo can you help your friend @IsmaelNavarro with this? He's done the same, and more than once. It hurts our efforts by deviating the team and community focus.

@IgnaciodeNuevo thanks for working on this. I took a quick look at your changes and I will have a bunch of comments. Not sure when I can get to doing a full review though, so please bear with me.

Never mind, didn't notice the PR was closed :)

FYI, I had the tree view code pending on my machine, with just a couple things to iron out. I finished it and have a PR open here: https://github.com/Microsoft/AdaptiveCards/pull/1613/


⚠ ClamAV has degraded performance

In 1bb8351, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 69 ms

Resolved: ClamAV performance has improved in b4a7043 after 5 minutes.


SLA miss duplicate notification

PagerDuty can create pages via email or API call.
We have Notifiers defined that work as sla_miss_callback and are called when an SLA misses, they call PagerDuty pages with the API.
Airflow also sends emails when the SLA is missed, to all the emails defined in the DAG, so when PagerDuty gets that email, it creates a new Page, so we end up with 2 pages for the same DAG SLA miss.
The solution to this is quite simple. If there is a callback defined in sla_miss_callback, then we won't send the email to the @lyft.pagerduty.com emails.
simple unit test of the change applied:
test_emails =<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>emails = {email for email in test_emails if not email.endswith('@lyft.pagerduty.com')}
assert(emails ==<EMAIL_ADDRESS><EMAIL_ADDRESS>

/ptal @eschachar


Authz/authn additions

hey! thanks for taking a look and giving me some suggestions. Some notes to test :

you'll need to test with google chrome, and enable the webauthn virtual authentication environment to create a test webauthn credential
theres a set of commands in auth-service/src/main/setup-fga.sh that need to be run manually individually before dev services is started (for now) because of an Open issue in the FGA client
to test, I've been doing ./mvnw quarkus:dev -Dquarkus.profile=no-microcks in the frontend,rest-fights,rest-heroes,rest-villains services and ./mvnw quarkus:dev in the auth-service.

Some general notes:

The javascript code will eventually look a lot better when this get's fixed and I don't need to manually copy the WebAuthn javascript that Quarkus provides. I was fetching the script dynamically at first but without the flag it didn't work
My idea was to use WebAuthn for AuthN, and then OpenFGA for AuthZ. I have 3 "plans" (full, referee, viewer) and each can access different resources. full can access both fights and narration services, referee can only trigger a fight, and viewer can see fighters get loaded, but when they try to trigger a fight they get a "please upgrade your plan" type message

Any suggestions are much appreciated!

Maybe it would be more intuitive to make the UI "smarter"? For instance, why have a "perform fight" button if the user isn't able to perform a fight? Sure you need to do checking on the backend to prevent hacking/bypassing the UI, but generally from a user experience perspective, don't give the user the option to do something they can't do in the first place.

I guess this is a good point if this were to be considered for this main repo. For a demo, I wanted to purposefully make it a bit "annoying" so that the two fighters get loaded for any user, but when they actually try to do something they get the "Consider upgrading!" message.

Maybe I don't understand the general flow, but it seems the only place authentication is happening is within rest-fights? There isn't any kind of auth happening within any of the other services? So as a user, if I knew the URLs for the other services (heroes/villains/locations/narration), I could still interact directly with them?

At the moment yes, I didn't want to over complicate it for now and haven't gotten that far yet. That's one of the reasons I mentioned wanting to consider mTLS between the services for authenticating eachother (or putting them behind a mesh) so that I wouldn't have to authenticate a user in each individual service and a frontend user wouldn't be able to access services within that mesh. But I'm open to ideas.

I also almost feel like there is a mix of concerns? You're putting the fight service in charge of doing all the auth (it has the auth client and a whole jax-rs resource class for handling auth requests from the UI). Wouldn't it be better/more appropriate for that stuff to live in the ui-super-heroes application (on the backend)?

To be honest, I don't really understand the "back-end" portion of ui-super-heroes. The way I visualize and understand the architecture diagram is that the backend for ui-super-heroes IS the rest-fights service and rest-fights is supposed to query all the other services so I was following that flow. I also don't really know how to fit the authentication flow into the ui-super-heroes stuff directly (unless you meant like modifying the initial registration/login to hit the auth-service directly which would just be adding something here, but then that would break from the patterns i've noticed where UI superheroes only hits one endpoint). Since rest-fights is the only service really exposed to the UI, I placed auth flow there for this example but since we've shown the pattern of delegating a separate service to make the actual decisions the auth-service methods can be used anywhere. So i'm not sure what best way to handle it is lol!

There's no resilience at all when using the auth rest client. What happens if the auth client (i.e. checkFeatureAccess) fails for some reason (auth service not reachable, etc). There should be some circuit breaking/fallbacks/retries/timeouts in place. We have this in place when communicating with the other services.
Agreed, I wanted to make sure things were working first but will work on adding this

And I agree on all your other notes as well! Thanks so much for the feedback

Maybe it would be more intuitive to make the UI "smarter"? For instance, why have a "perform fight" button if the user isn't able to perform a fight? Sure you need to do checking on the backend to prevent hacking/bypassing the UI, but generally from a user experience perspective, don't give the user the option to do something they can't do in the first place.

I guess this is a good point if this were to be considered for this main repo. For a demo, I wanted to purposefully make it a bit "annoying" so that the two fighters get loaded for any user, but when they actually try to do something they get the "Consider upgrading!" message.

Makes sense!

Maybe I don't understand the general flow, but it seems the only place authentication is happening is within rest-fights? There isn't any kind of auth happening within any of the other services? So as a user, if I knew the URLs for the other services (heroes/villains/locations/narration), I could still interact directly with them?

At the moment yes, I didn't want to over complicate it for now and haven't gotten that far yet. That's one of the reasons I mentioned wanting to consider mTLS between the services for authenticating eachother (or putting them behind a mesh) so that I wouldn't have to authenticate a user in each individual service and a frontend user wouldn't be able to access services within that mesh. But I'm open to ideas.

I think introducing mTLS between the apps, while a good idea in the "real world", would probably make a mess of trying to run things locally and/or with docker compose, so I'm not sure its something we want to do.
Plus when deploying to OpenShift, that would certainly mess with the routes.
I'm not as familiar with WebAuthN as I am with OIDC (OpenID Connect). If we were talking about OIDC then this would be how I would set it up:

The UI would use auth code flow to obtain a token
The UI would pass the token to rest-fights
rest-fights would use client credentials flow to authenticate itself to grpc-locations, rest-narration, rest-villains, and rest-heroes
One of the roles/grants in the original user token would need to be passed from rest-fights to the other services, but the other backend services wouldn't necessarily know the identity of the end user

Maybe @sberyozkin can chime in with his thoughts here?

I also almost feel like there is a mix of concerns? You're putting the fight service in charge of doing all the auth (it has the auth client and a whole jax-rs resource class for handling auth requests from the UI). Wouldn't it be better/more appropriate for that stuff to live in the ui-super-heroes application (on the backend)?

To be honest, I don't really understand the "back-end" portion of ui-super-heroes. The way I visualize and understand the architecture diagram is that the backend for ui-super-heroes IS the rest-fights service and rest-fights is supposed to query all the other services so I was following that flow. I also don't really know how to fit the authentication flow into the ui-super-heroes stuff directly (unless you meant like modifying the initial registration/login to hit the auth-service directly which would just be adding something here, but then that would break from the patterns i've noticed where UI superheroes only hits one endpoint). Since rest-fights is the only service really exposed to the UI, I placed auth flow there for this example but since we've shown the pattern of delegating a separate service to make the actual decisions the auth-service methods can be used anywhere. So i'm not sure what best way to handle it is lol!

So the ui-super-heroes is mostly a front-end/react app. It uses Quarkus Quinoa to package the react app inside a Quarkus app. The react app gets its configuration by first making a GET to /env.js, which is handled by https://github.com/quarkusio/quarkus-super-heroes/blob/main/ui-super-heroes/src/main/java/io/quarkus/sample/superheroes/ui/EnvResource.java (a JAX-RS resource within the ui-super-heroes backend app).
My thought was that this auth stuff could exist there as well, that way the rest-fights isn't responsible for handling login/logout. It would be the ui app's responsibility. That way, rest-fights would stay within the "fight" domain. Sure you'll probably have to add authorization like you are, and it probably still needs to "talk" to the auth service to decide whether or not certain functions can be performed by the current user, but it would not be responsible for handling login/logout.

There's no resilience at all when using the auth rest client. What happens if the auth client (i.e. checkFeatureAccess) fails for some reason (auth service not reachable, etc). There should be some circuit breaking/fallbacks/retries/timeouts in place. We have this in place when communicating with the other services.
Agreed, I wanted to make sure things were working first but will work on adding this

And I agree on all your other notes as well! Thanks so much for the feedback

You're welcome!


Sign an ES256 or RS256 JWT within Postgres

I want to build an auth system that directly connects to Postgres, but currently we can only sign keys with pgjwt that aren't compatible with JWKS. Is there any way to add a method for signing JWT's at the postgres level that can be used with RLS.

Hi, thanks for the issue. Currently pg_session_jwt only handles the verification of ES256 JWTs. We don't have any intention to support signing at this time.
Usually for an authentication platform you need to be doing some kind of oauth2 flow or password verification, and I would recommend signing JWTs at that place, not within Postgres.

The thinking is a future where there no longer needs to be an authentication API, and instead have a function within Postgres that an anonymous user can use, for example...
SELECT from users where email = '$email' and password = '$hashedPassword'
If found, sign and return JWT to be passed along in subsequent requests. The whole purpose being to totally remove the need for a separate API for handling authentication. Or is the only API-less future going to require using third party OAuth providers and their JWKS?


Tab at the top of the browser says MakeCode Skill Map - not "Skillmap"

Describe the bug

Can we pull this text from the skillmap md file?  MakeCode + the name of the map?

Still true. We should make sure it's "Skillmap" everywhere.


Upgrade wgpu 0.15

published a new version with this for ease of use! 0.11 is live now

Thank you!


About training

This is a great job!!! I want to know if this training code will be made public?

In the demo of the video reconstruction, the ground truth of the high-speed camera had to be used, which was confusing. How can we use the model without high-speed camera data？For example, I only have the images of low-speed cameras and the data of event cameras, and the timestamps of each frame.

Thank you for your interest. We are continuing to work on the task, and the training code will be released when after the new work is done. The detailed training process are provided in our paper.
As mentioned in our paper, we use the GT video skipped 199 frames as input for quantitative VFI evaluation. This is due to the fact that the brightness intensity of GT video frames is different from that of DAVIS video frames (DAVIS video frames are darker). If we use the low-speed DAVIS video frames as input, the output VFI results will have the save brightness as the DAVIS video frames, and are different from GT video frames. This is unfair for flow-based methods and flow-based module in Time Lens. If you only need qualitative VFI results or use it in real-world applications, you could just use low-speed video frames and the corresponding event stream between frames as input (spatiotemporal aligned frames and events), e.g. frames and events captured by DAVIS event camera (naturally aligned).

THANKS!!!!


swiper 4 error on chrome  version 67

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: EXACT RELEASE VERSION OR COMMIT HASH, HERE.

Live Link or JSFiddle/Codepen or website with isssue: PREFERABLY (IF YOU WANT YOUR ISSUE TO BE RESOLVED ASAP).

What you did
swiper error in new version chrome

Expected Behavior
I googling found out it's chrome problem .
Actual Behavior
EXPLAIN WHAT IS ACTUALLY HAPPENING, HERE.
P.S. Remember, an issue is not the place to ask questions. You can use Stack Overflow
for that.
Before you open an issue, please check if a similar issue already exists or has been closed before.

Your issue is closed because it is not filled correctly. Before you open an issue please review the contributing guideline.
Please fill the issue template correctly and:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with isssue

It will save a lot of time for other contributors to check your issue and fix it.


[128] improvement: Add a integration test case for Spark with MiniYarnCluster —— in test state

What changes were proposed in this pull request?
Add a integration test case for Spark with MiniYarnCluster
Why are the changes needed?
Fix: https://github.com/apache/incubator-uniffle/issues/138
Does this PR introduce any user-facing change?
No.
How was this patch tested?
It self is test case

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ecbf2e7) 53.22% compared to head (3360f5d) 53.47%.
Report is 13 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1395      +/-   ##
============================================
+ Coverage     53.22%   53.47%   +0.25%
+ Complexity     2715     2191     -524
============================================
  Files           418      342      -76
  Lines         23932    15417    -8515
  Branches       2043     1427     -616
============================================
- Hits          12738     8245    -4493
+ Misses        10408     6708    -3700
+ Partials        786      464     -322

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

The PR title should obey the rule like that  [#128] improvement(tests): Add a integration test case for Spark with MiniYarnCluster
And If this is on progress, you can mark this PR as draft that could be finished by this button,


Bleak updated :(

Run new container has result:
ble2mqtt_1     | 2022-08-25 19:35:42 INFO: Connected to 02:F6:21:7E:10:96
ble2mqtt_1     | 2022-08-25 19:35:43 WARNING: Error while connecting to Blind_AM43_02f6217e1096, 'BleakClientBlueZDBus' object has no attribute '_properties' AttributeError("'BleakClientBlueZDBus' object has no attribute '_properties'"), failure_count=1
Old version works fine.

I fixed this in the branch, can you please try it out?
pip3 install -U https://github.com/devbis/ble2mqtt/archive/refs/heads/main.zip --no-cache-dir --force-reinstall

yes, fix works. Thank you

Fixed in version 0.1.3