docs: RTD build failing due to jupyter_client.kernelspec.NoSuchKernel

Describe the bug
ReadtheDocs build is failing due to error jupyter_client.kernelspec.NoSuchKernel: No such kernel named mesa_geo

Full Error
Running Sphinx v8.0.2
loading translations [en]... done
making output directory... done
WARNING: html_static_path entry '_static' does not exist
Converting `source_suffix = ['.rst', '.md']` to `source_suffix = {'.rst': 'restructuredtext', '.md': 'restructuredtext'}`.
loading intersphinx inventory 'python' from https://docs.python.org/3/objects.inv ...
myst v4.0.0: MdParserConfig(commonmark_only=False, gfm_only=False, enable_extensions=set(), disable_syntax=[], all_links_external=False, links_external_new_tab=False, url_schemes=('http', 'https', 'mailto', 'ftp'), ref_domains=None, fence_as_directive=set(), number_code_blocks=[], title_to_header=False, heading_anchors=0, heading_slug_func=None, html_meta={}, footnote_sort=True, footnote_transition=True, words_per_minute=200, substitutions={}, linkify_fuzzy_links=True, dmath_allow_labels=True, dmath_allow_space=True, dmath_allow_digits=True, dmath_double_inline=False, update_mathjax=True, mathjax_classes='tex2jax_process|mathjax_process|math|output_area', enable_checkboxes=False, suppress_warnings=[], highlight_code_blocks=True)
myst-nb v1.1.1: NbParserConfig(custom_formats={}, metadata_key='mystnb', cell_metadata_key='mystnb', kernel_rgx_aliases={}, eval_name_regex='^[a-zA-Z_][a-zA-Z0-9_]*$', execution_mode='cache', execution_cache_path='', execution_excludepatterns=(), execution_timeout=60, execution_in_temp=False, execution_allow_errors=False, execution_raise_on_error=False, execution_show_tb=False, merge_streams=False, render_plugin='default', remove_code_source=False, remove_code_outputs=False, code_prompt_show='Show code cell {type}', code_prompt_hide='Hide code cell {type}', number_source_lines=False, output_stderr='show', render_text_lexer='myst-ansi', render_error_lexer='ipythontb', render_image_options={}, render_figure_options={}, render_markdown_format='commonmark', output_folder='build', append_css=True, metadata_to_fm=False)
Using jupyter-cache at: /home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/checkouts/main/_readthedocs/.jupyter_cache
building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 17 source files that are out of date
updating environment: [new config] 17 added, 0 changed, 0 removed
reading sources... [  6%] README
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/read.py:71: RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
  if path.endswith(suffix):
reading sources... [ 12%] apis/api_main
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/read.py:71: RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
  if path.endswith(suffix):
reading sources... [ 18%] apis/geo_base
reading sources... [ 24%] apis/geoagent
reading sources... [ 29%] apis/geospace
reading sources... [ 35%] apis/raster_layers
reading sources... [ 41%] apis/tile_layers
reading sources... [ 47%] apis/visualization
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/solara/validate_hooks.py:122: UserWarning: /home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/mesa/experimental/jupyter_viz.py:163: JupyterViz: `use_state` found within a nested function created on line 155
To suppress this check, replace the line with:
        grid_layout, set_grid_layout = solara.use_state(grid_layout_initial)  # noqa: SH104

Make sure you understand the consequences of this, by reading about the rules of hooks at:
    https://solara.dev/documentation/advanced/understanding/rules-of-hooks

  warnings.warn(str(e))
reading sources... [ 53%] examples/geo_schelling
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/read.py:71: RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
  if path.endswith(suffix):
reading sources... [ 59%] examples/geo_schelling_points
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/read.py:71: RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
  if path.endswith(suffix):
reading sources... [ 65%] examples/geo_sir
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/read.py:71: RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
  if path.endswith(suffix):
reading sources... [ 71%] examples/overview
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/read.py:71: RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
  if path.endswith(suffix):
reading sources... [ 76%] examples/population
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/read.py:71: RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
  if path.endswith(suffix):
reading sources... [ 82%] examples/rainfall
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/read.py:71: RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
  if path.endswith(suffix):
reading sources... [ 88%] examples/urban_growth
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/read.py:71: RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
  if path.endswith(suffix):
reading sources... [ 94%] index
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/read.py:71: RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
  if path.endswith(suffix):
reading sources... [100%] tutorials/intro_tutorial
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/read.py:71: RemovedInSphinx90Warning: Sphinx 9 will drop support for representing paths as strings. Use "pathlib.Path" or "os.fspath" instead.
  if path.endswith(suffix):
/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/checkouts/main/docs/tutorials/intro_tutorial.ipynb: Executing notebook using local CWD [mystnb]
WARNING: autodoc: failed to import module 'modules.__init__' from module 'visualization'; the following exception was raised:
No module named 'visualization.modules' [autodoc.import_object]
WARNING: autodoc: failed to import module 'modules.MapVisualization' from module 'visualization'; the following exception was raised:
No module named 'visualization.modules' [autodoc.import_object]

Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/sphinx/cmd/build.py", line 337, in build_main
    app.build(args.force_all, args.filenames)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/sphinx/application.py", line 378, in build
    self.builder.build_update()
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/sphinx/builders/__init__.py", line 296, in build_update
    self.build(to_build,
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/sphinx/builders/__init__.py", line 317, in build
    updated_docnames = set(self.read())
                           ^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/sphinx/builders/__init__.py", line 424, in read
    self._read_serial(docnames)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/sphinx/builders/__init__.py", line 476, in _read_serial
    self.read_doc(docname)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/sphinx/builders/__init__.py", line 535, in read_doc
    publisher.publish()
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/docutils/core.py", line 234, in publish
    self.document = self.reader.read(self.source, self.parser,
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/sphinx/io.py", line 106, in read
    self.parse()
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/docutils/readers/__init__.py", line 76, in parse
    self.parser.parse(self.input, document)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/sphinx_.py", line 152, in parse
    with create_client(
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/execute/base.py", line 79, in __enter__
    self.start_client()
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/myst_nb/core/execute/cache.py", line 72, in start_client
    result = single_nb_execution(
             ^^^^^^^^^^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/jupyter_cache/executors/utils.py", line 58, in single_nb_execution
    executenb(
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/nbclient/client.py", line 1314, in execute
    return NotebookClient(nb=nb, resources=resources, km=km, **kwargs).execute()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/jupyter_core/utils/__init__.py", line 165, in wrapped
    return loop.run_until_complete(inner)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/docs/.asdf/installs/python/3.12.3/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/nbclient/client.py", line 693, in async_execute
    async with self.async_setup_kernel(**kwargs):
  File "/home/docs/.asdf/installs/python/3.12.3/lib/python3.12/contextlib.py", line 210, in __aenter__
    return await anext(self.gen)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/nbclient/client.py", line 648, in async_setup_kernel
    await self.async_start_new_kernel(**kwargs)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/nbclient/client.py", line 550, in async_start_new_kernel
    await ensure_async(self.km.start_kernel(extra_arguments=self.extra_arguments, **kwargs))
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/jupyter_core/utils/__init__.py", line 198, in ensure_async
    result = await obj
             ^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/jupyter_client/manager.py", line 96, in wrapper
    raise e
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/jupyter_client/manager.py", line 87, in wrapper
    out = await method(self, *args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/jupyter_client/manager.py", line 435, in _async_start_kernel
    kernel_cmd, kw = await self._async_pre_start_kernel(**kw)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/jupyter_client/manager.py", line 397, in _async_pre_start_kernel
    self.kernel_spec,
    ^^^^^^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/jupyter_client/manager.py", line 195, in kernel_spec
    self._kernel_spec = self.kernel_spec_manager.get_kernel_spec(self.kernel_name)
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/jupyter_client/kernelspec.py", line 285, in get_kernel_spec
    raise NoSuchKernel(kernel_name)
jupyter_client.kernelspec.NoSuchKernel: No such kernel named mesa_geo

Exception occurred:
  File "/home/docs/checkouts/readthedocs.org/user_builds/mesa-geo/envs/main/lib/python3.12/site-packages/jupyter_client/kernelspec.py", line 285, in get_kernel_spec
    raise NoSuchKernel(kernel_name)
jupyter_client.kernelspec.NoSuchKernel: No such kernel named mesa_geo
The full traceback has been saved in /tmp/sphinx-err-ycc8zhmq.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!

Expected behavior
ReadtheDocs should build successfully.
To Reproduce
In the visual environment, install docs dependency:
pip install -e ".[dev]"

Then in the docs folder, run:
python -m sphinx -T -b html -d _build/doctrees -D language=en . html

Additional context
This is likely caused by https://github.com/projectmesa/mesa-geo/blob/5b05dcd29dd1c3d8f9ed893abfb816f0dd53b591/docs/tutorials/intro_tutorial.ipynb#L1112-L1117
I'm not sure whether removing these will have any side effects.

(may not be useful) npsphinx has a nbsphinx_kernel_name parameter that can change kernel name: https://github.com/spatialaudio/nbsphinx/blob/ae3c9d9bbf56b6afe5f102f62cd14dfb44e76011/doc/configuring-kernels.ipynb#Kernel-Name

Fixed by https://github.com/projectmesa/mesa-geo/pull/229. Closing.


Fix typo in SASS mode that was introduced by PR #3013

Typo was in commit 9e56052a

Btw, the token types used in SASS are really inconsistent with the set used by the CSS/LESS/SCSS modes.

CSS/LESS/SCSS
SASS

Tag name selector
tag
atom

Class selector
qualifier
atom

Id selector
builtin
atom

Property name
property
property

Numeric value
number (including any unit suffix)
number (but unit suffix is unit)

Enumerated value
atom
attribute

Would there be any objections to changing SASS to match the others more closely?  And maybe porting the unit thing into the others, since that seems like a nice enhancement...  (CC @ankitstarski since you seem to have worked on the SASS code most recently)

I've merged your patch as dad7abf . I'd be okay with changing the styles output by the SASS mode to match the CSS dialects more closely, and also with copying the trick of giving units a separate style -- though I'd prefer to use one of the standard styles, rather than unit, which is not covered by any of the themes.


include terminal emulator

Is it possible to include terminal emulator support to prevent the need of a multiplexer?

Good idea! :)
Actually, some time ago I made a multiplexer in Python: https://github.com/jonathanslenders/pymux
So, it shouldn't be too hard to give pyvim terminal emulation as well. Do you know how neovim is doing it? It would be good to support the same set of commands.
Having this would be also be the start of a real Python IDE with integrated debugger and option to run scripts.

Hi @jonathanslenders
NeoVim uses libvterm.
http://www.leonerd.org.uk/code/libvterm/


"Fix three KePub fullScreenReading bugs" Better Patch

FindReplaceString:
Find:    "img { display: block; margin-left: auto !important; margin-right: auto !important; width: auto !important; height: auto !important; }"
Replace: "body{margin:0!important;padding:0!important;}body>div{margin-right:0.2em !important; margin-bottom:0.25em !important;               }"

The default 3 patches still have text cut off in Japanese(Vertical), English under difference circumstances.
This one is bruteforce but enables Japanese, Eng/Chinese aligned properly without being cut off.
Any better adjustment will be welcomed.
Plz merge this.

I think change 0.Xem to XXpx could be better in compatibility.
Because fonts differs in weight & sizes, I tested many works, few(very few) like MI LANTING still cut off Japanese with this patch. BUT default fonts all works fine.

This patch should not be necessary since 4.11.11911, as Kobo now officially supports disabling headers and footers.


No entries found

I'm facing a problem wheee i enter the Nhentai app and show nothing hut a message no entries found i try to refresh it but still the same. I turn on the Nhent.ai but still the same result.

@kidman9520 Make sure you can access both nhentai.net and nhent.ai in your browser. If you cant that means you might need an VPN. Also FYI nhent.ai is down and cant be accessed right now


Add prefix to SVG id/class attributes (#16997)

backport #16997
Currently the svg minifier (make svg) rewrites all id and class attributes in svg files. Every file gets the ids a, b, .... If multiple svgs with ids are used on a page these ids are conflicting and the results are broken images.

minified ids
unique ids

This PR adds a prefix (the filename) to every id/class.
Follow up problem: Because we embed svg images there are duplicated ids if one svg image is used multiple times on a page. As those ids refer to the same content it may be no real problem because browser handle that fine.

make lgtm work


HandTrackingExample.py

length, info, img = detector.findDistance(lmList1[8], lmList2[8], img)  # with draw
has an error below
ValueError: too many values to unpack (expected 2)
  def findDistance(self, p1, p2, img=None):
      x1, y1 = p1
      x2, y2 = p2
      cx, cy = (x1 + x2) // 2, (y1 + y2) // 2
      length = math.hypot(x2 - x1, y2 - y1)
      info = (x1, y1, x2, y2, cx, cy)
      if img is not None:
          cv2.circle(img, (x1, y1), 15, (255, 0, 255), cv2.FILLED)
          cv2.circle(img, (x2, y2), 15, (255, 0, 255), cv2.FILLED)
          cv2.line(img, (x1, y1), (x2, y2), (255, 0, 255), 3)
          cv2.circle(img, (cx, cy), 15, (255, 0, 255), cv2.FILLED)
          return length, info, img
      else:
          return length, info

I think the problem is that the lmList2 and lmList1 have 3 element, respectively.

Hello
yes, I think mediapipe has change the return value in august.
Now I fix the error, Please install the lastest version.


feat(popup): Added arrow centering, size and width properties

Before submitting a pull request, please make sure you have at least performed the following:

[x] read and followed the CONTRIBUTING.md guide.
[x] linted, built and tested the changes locally.
[x] added/updated any applicable API documentation.
[x] added/updated any applicable demos.

Added ability for popup to align the center of the arrow when it would be reasonable. (Feature same as in SUI v2.3.0)
Also the size and width properties were added.

Thank you for this PR, I'm sorry it's taken so long to get merged. I'm cutting an @next release tomorrow, will be releasing a new version in due course.


How did you find the direction of the coverage to reduce the number of turns?

Hi @gustavoavellar , I am unable understand how you determine the direction of the sweeping in your code.  I am working with a rectangle search area. But unable to make it cover to reduce number of turns. If you could give some explanation, that would be tremendous.

The best sweep direction is one which yields longer lines and less turns outside coverage area. Therefore, you are searching for a sweep direction that is perpendicular to the smallest projection of your polygon.

In my code, I search for this direction by rotating the polygon and looking for the smallest distance between maximum and minimum x coordinate. You can find this in findStrips.m


Uncaught Error: Class 'AutopilotManager' not found

Hey guys
Looks like the AutopilotManager class isn't being loaded.
Installed your PHP library via Composer, did the old "include_once('./vendor/autoload.php')" which didn't throw any errors.
Then it falls over as soon as I call the class with:
$manager = new AutopilotManager($api_key);
PHP Fatal error:  Uncaught Error: Class 'AutopilotManager' not found in...

I resolved the issue with namespaces.
It should be:
$autopilot = new Autopilot\AutopilotManager($api_key);


Bug 1755623: storagecluster: Do not set ownerRefs for StorageClasses

The StorageClass resources are non-namespaced resources, and had their
ownerRefs set to the StorageCluster resource which is a namespaced
resource in the openshift-storage namespace. Having this sort of
cross-namespace ownerRefs, could cause the other children of the
StorageCluster to be inadverdently deleted by the GC. Ref 1.
Removing the ownerRefs on the StorageClass objects avoids this.
Backport of #314.

/test ocs-operator-e2e-aws
The OCP deployment failed in the previous run. Retriggering.

/test ocs-operator-e2e-aws
Triggering again. Another CI infra failure.

/test ocs-operator-e2e-aws


Add Round Timer to Encounter

Closes #2296

What's this?

I think that issue was created before automatic effect expiration was added.


One-stop shop for creating physical plans

Code that creates physical plans exists already in different places in the code base, and there will be more in the future (e.g., when we add the rewriting rules). Often, this code includes also the creation of the physical operators and perhaps even the logical operators wrapped by the physical ones. To simplify the code base and to avoid repetition of code we should add a factory/helper class to make it more convenient to create physical plans, which can be similar to the factory class to be created according to #89.
/cc @chengsijin0817 I will take care of this.

Done. Now, the main way to create physical plans is via PhysicalPlanFactory.
@chengsijin0817 don't bother using this in your current PR #70 at the moment. We can take care of that later.


Fixes 3611: ML API procedures handle null values being passed in better

Fixes https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues/3611

vertexai and openai embeddings return null rows with null list values

embeddings, chat completion, completion and image procedures return null if the input parameter is null

not implemented null check in apoc.ml..custom procedures, since we can potentially pass a null parameter (e.g. to call this RestAPI)

TODO: open Trello Card for the following note?

Additional notes
Would be great to handle errors like these, but we cannot implement it since is part of APOC Core:
CALL apoc.ml.openai.chat([ {role:"user", content:null}], $apiKey, $conf)
We should do something like this:
        @Override
        public InputStream getInputStream() throws IOException {
            if (con instanceof HttpURLConnection httpConn && httpConn.getResponseCode() >= 400)
            {
                // return ErrorStream as a RuntimeException
                String errMsg = new String(httpConn.getErrorStream().readAllBytes());
                throw new RuntimeException("Error during HTTP call:\n" + errMsg);
            }

            return toLimitedIStream(con.getInputStream(), getLength());
        }

LGTM


[BUG] integration map_test:test_map_scalars_supported_key_types failures

Describe the bug
[2023-08-03T13:18:49.080Z] FAILED ../../src/main/python/map_test.py::test_map_scalars_supported_key_types[Byte(not_null)][INJECT_OOM]

[2023-08-03T13:18:49.080Z] FAILED ../../src/main/python/map_test.py::test_map_scalars_supported_key_types[Short(not_null)]

[2023-08-03T13:18:49.080Z] FAILED ../../src/main/python/map_test.py::test_map_scalars_supported_key_types[Integer(not_null)]

[2023-08-03T13:18:49.080Z] FAILED ../../src/main/python/map_test.py::test_map_scalars_supported_key_types[Long(not_null)]

[2023-08-03T13:18:49.080Z] FAILED ../../src/main/python/map_test.py::test_map_scalars_supported_key_types[Date(not_null)][INJECT_OOM]

[2023-08-03T13:18:49.080Z] FAILED ../../src/main/python/map_test.py::test_map_scalars_supported_key_types[Timestamp(not_null)][INJECT_OOM]

AssertionError: GPU and CPU are not both null at [0, 'scalarsubquery()[key]']

The same tests failed in the MT shuffle job

This was fixed with https://github.com/NVIDIA/spark-rapids/pull/8971


Restarting Home Assistant while Risco active causes sensors and switches to have 'unknown' state.

Describe the bug
If risco-mqtt-local is running and Home Assistant is restarted, sensors and switches have 'unknown' state
Configuration

Environment: Docker
Version: v0.4.1
Mode: direct
Command line (if not running as HA Addon):
Risco Panel model: Lightsys
Risco Panel firmware version:

I’ll have a go.  Might take a while, though!

On 11 Apr 2022, at 20:52, Johann Vanackere @.***> wrote:
Yes I agree. That's exactly what I suggested in #32 https://github.com/vanackej/risco-mqtt-local/pull/32.
@markxroberts https://github.com/markxroberts do you think you could try do do it ?
—
Reply to this email directly, view it on GitHub https://github.com/vanackej/risco-mqtt-local/issues/31#issuecomment-1095499026, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF2J4VZ6QZKIZKYWLKWCQS3VER7GHANCNFSM5SM4SVPA.
You are receiving this because you were mentioned.

I've had a go at fixing this.

Available in 0.4.2, thx


Bit extract

The only commit in this PR is this:
correct wgsl code gen

The only change of this PR is this commit:
correct wgsl code gen

In the latest change, I update the function signature to use uint as the type for the offset and bit parameters.
Update the test correspondingly. Now we can get rid of most of the special handling of wgsl backend.


gatsby-plugin-netlify broken with Webpack 5

Stuck with this issue: https://github.com/gatsbyjs/gatsby/issues/29974

Tried adding
"resolutions": {
  "webpack-assets-manifest": "5.0.1"
}

to package.json and using yarn install as per https://github.com/gatsbyjs/gatsby/issues/29974. Did not help unfortunately


made aesthetic changes

added padding to image and made it responsive and changed the size of time and cw

Its UI kinda got messed up I gave that image size because when a user comes on this site he should see the typing board at first. Trying adjusting the image

It should look like this when a user comes everything should be visible

ok...I'll fix that up

I restored the width and corrected the alignment of image and text , and added a margin .

I will close this PR cause If I merge this PR it will go to spam and try improving the UI and then PR.


Implement close() for BlockStore interface

Leaving RocksBlockStore unclosed, will block creating further stores at the same path. This prevents running fail-over scenarios in single process tests with ROCKS meta-store. This PR makes necessary plumbing to make sure RocksBlockStore is closed during master shutdown.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4088/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4096/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4119/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4121/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4123/
Test PASSed.

@LuQQiu @calvinjia
PTAL. Thanks!

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4167/
Test PASSed.

alluxio-bot, merge this please.

alluxio-bot, cherry-pick this to branch-2.0 please.


Adding New Profile (Ahasas Jain)

I added my profile please review it.

close issue #43

to fix the conflicts, try adding your profile in between instead of top and bottom

resolved all conflicts please review.


Diag freq

What changes does this PR introduce?
(Bug fix, feature, docs update, ...)
First band-aid to diagnostics frequency errors discussed in #426. Just an implementation of the idea I mentioned in #411, so far.
What is the current behaviour?
(You can also link to an open issue here)
#426
What is the new behaviour
(if this is a feature change)?

diagnostics resets any frequency where |frequency| < deltaTclock to be deltaTclock
warning to the user (maybe not necessary)

Does this PR introduce a breaking change?
(What changes might users need to make in their application due to this PR?)
Other information:
Suggested addition to tag-index
(To avoid unnecessary merge conflicts, please don't update tag-index. One of the admins will do that when merging your pull request.)

reset diagnostics frequency when set to less than deltaTclock

@jm-c will act as fortran expert here and take a look

I've checked (and fixed a problem in diagnostics_out.F) and this seems to works fine when timeRec/freq(listId) is larger
than any integer*4 (checked with g77 and pgf77). In my tests, I did not include the changes in diagnostics_readparms.F so I think
we can just left this one un-changed. Also, there are 2 minor issues with modified version of diagnostics_readparms.F (PRINT_ERROR should not be used to report a warning but only an error ; and the behavior for the case frequency(l) = 0. is not
preserved) that I did not fixe, but should be if we decide to keep this feature ( |freq| >= deltaTClock).

Following up from today I can confirm the following based on the verification experiment global_ocean.cs32x15/input.seaice, which uses mdsio and diagnostics:

the master branch fails when setting diagnostics frequency to 1
with this PR, the run no longer fails when diagnostics frequency is set to 1
with diagnostics_out from this PR and the master branch version of diagnostics_readparms, the only difference to the previous case is a warning to the user that the frequency was reset

Given potential troubles with frequency = 0, I am in favor of removing the changes to diagnostics_readparms. I can push this if you like, let me know.

@timothyas Thanks for checking this. I am also in favor of keeping diagnostics_readparams.F unchanged but if you can take care of this it would be great.

No problem @jm-c, done

Ok, I think this one is ready to merged in. Will do this tomorrow unless some one disagree.


Default options change not working

Changing breakpoints in nuxt.config.js has no effect. To change default options you have to edit plugin.js file in node-modules folder.

I will investigate this in weekend and refactor some code, thanks for your patience.

+1


On (some) mobile phones, Ketcher window stays empty

The SMILES str displayed correctly but the structure is not loaded in the Ketcher window

We have to consult with ketcher app developers

In the Safari console:
"TypeError: undefined is not an object (evaluating 'ketcher.setMolecule')

I have filed an issue here.

The issue is solved with a modification of the loadMol function. It now checks whether or not the Ketcher window is loaded before trying to load a molecule. If it is not loaded, it waits 100ms and calls itself again.


the year of CopyRight

Which cheat sheet? Describe the issue
We found only "2021" in the footnote. Is it better to update to include recent year?

Relevant codes ..?
https://github.com/Azure/azureml-cheatsheets/blob/1c472e26ed5e5e4d0232958eff49173be2159938/website/docusaurus.config.js#L81
https://github.com/Azure/azureml-cheatsheets/blob/1c472e26ed5e5e4d0232958eff49173be2159938/website/i18n/ja/docusaurus-theme-classic/footer.json#L43

Hi @kyoro1, I'm not sure if the code works in this json file. Created a simple fix:
https://github.com/Azure/azureml-cheatsheets/pull/90


Adds bogan accent to customize menu

About the PR
adds the bogan accent to traits
Why / Balance
some guy in bounties wanted it
Changelog
:cl: Syndie

tweak: You can now get the Bogan accent in character customization.

Looks like I need to work on my accent improvement PR now then :despair:


Cannot Connect to Parse Server via Android

I'm currently running Parse-Server 2.1.4 (same problem persists on 2.1.3) and my configuration is:
var parse_api = new ParseServer({
  databaseURI: process.env.MONGOLAB_URI || 'xxxxxxx',
  cloud: './cloud/main.js',
  appId: 'xxxxxxx',
  fileKey: 'xxxxxxx',
  masterKey: 'xxxxxxx',
  serverURL: process.env.PARSE_SERVER_URL || 'http://www.xxxxx.com/parse'
});

app.use('/parse', parse_api);

I'm unable to connect to this parse-server via my android client (I'm using parse-android:1.13.0). My configuration is:

        Parse.initialize(new Parse.Configuration.Builder(this)
                .applicationId(xxxxxx)
                .clientKey("unused")
                .server("http://www.xxxxx.com/parse/")
                .enableLocalDataStore()

                .build()
        );

Oddly enough, my iOS client (parse SDK 1.12.0) connects just fine to the same parse-server via the below configuration:
        Parse.initializeWithConfiguration(ParseClientConfiguration(block: {(configuration: ParseMutableClientConfiguration) -> Void in
            configuration.applicationId = "xxxxxx"
            configuration.clientKey = "unused"
            configuration.server = "http://www.xxxxxx.com/parse"
            configuration.localDatastoreEnabled = true
        }))

Any idea why I am able to connect  via iOS but not Android? From what I've seen, my Android client is implementing the standard configurations.

UP! Same error here.
It seems to be a url request replacement error. I analyzed the network interceptor and its replacing:
 http://server.com:1337/parse  to http://server.com:1337/
Is removing the "parse" path while placing the requests and the response is 404.

@ronaldo-getreveel is correct, as a workaround I've modified the configuration.server address, adding another /parse to the path and it worked:
Parse.initialize(new Parse.Configuration.Builder(this)
                .applicationId("APP_ID")
                .clientKey("CLIENT_ID")
                .server("http://MY_PARSE_SERVER.com/parse/parse")
                        .build()
        );

Interesting... cc @richardjrossiii or @grantland, any ideas?

For Android simply add an extra slash in the server's url and it will works.
http://MY_PARSE_SERVER.com/parse**/**

I didn't catch the trailing slash was missing...Yeah, it is required and this is known.

Did you guys get it to work with by adding parse/ ? I'm having a hard time getting this to work on android.


Fix Rust.gitignore rules for build artifacts

Reasons for making this change:
The changes made in #3436 are incorrect and should be reversed. Cargo, the de facto build tool for Rust, always outputs build / compilation artifacts to target/ in the root of the crate (project), by default (see the relevant portion of the Cargo book). We should target Cargo's defaults and allow other users to override them if they have customized the configuration of their builds.
The correct gitignore rule for excluding the target directory is
/target

since we want to ignore the top-level directory (only), as well as all of its children. Since the debug directory is itself always a child of target under the default Cargo configuration, excluding only target is sufficient for also excluding the debug directory that the previous committer added to the rules. Several other commenters in #3436 also pointed this out, but after the changes were already merged.
Importantly, the rules used in #3436 are incorrect, because they can exclude directories/files in src, e.g.:

src/target/some_file.rs or
src/components/debug/

which are actual source files for the project. Scoping the exclusion specifically to the top-level target directory generated by Cargo is a safer default.

tl;dr: We always know (absent custom configuration) that the target directory at the project root will contain all of Cargo's build and compilation artifacts, and that /target in the .gitignore is the sole safe default that will exclude them from git tracking correctly and safely; the same cannot be said for the current .gitignore rules, which could very well ignore actual source code in a project (and in a way that could be easy to miss / very unexpected).
Aside: the above rules will always be adequate for a "vanilla" Cargo project without custom config and should be considered the community defaults. Changes for customization or third-party tooling probably shouldn't be added here.

Links to documentation supporting these rule changes:
https://doc.rust-lang.org/cargo/guide/build-cache.html

@shiftkey I don't seem to be able to add a reviewer, could you have a look at this when you've time?

@shiftkey I don't seem to be able to add a reviewer, could you have a look at this when you've time?

@shiftkey ?

Thanks, @gracehop !

Ready to merge.

P.S. just a note to project maintainers:
I was unable to

Tag anyone for review on this PR
Merge the PR after approval

Perhaps this is because I opened the PR from a fork of the repo, rather than cloning the repo directly and branching within it?

P.S. just a note to project maintainers:
I was unable to

Tag anyone for review on this PR
Merge the PR after approval

Perhaps this is because I opened the PR from a fork of the repo, rather than cloning the repo directly and branching within it? Or perhaps it was desirable to have such restrictive settings on the repo, I'm not sure.
In any case, this could be merged, anytime, by anyone who has the ability to do so!

Anyone can modify a public repo is absolutely a bad idea.


Docs codeowners

What does this PR do?
Update CODEOWNERS so Baklava is notified about docs changes for container integrations
Motivation
Baklava was not auto-added when I did a PR for ECS Fargate
Additional Notes
N/A
Review checklist (to be filled by reviewers)

[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] Feature or bugfix must have tests
[ ] Git history must be clean
[ ] If PR adds a configuration option, it must be added to the configuration file.

Does this not suffice?
https://github.com/DataDog/integrations-core/blob/51981f5c3d56672c7ea00fe75a4f4b05fc22e6d0/.github/CODEOWNERS#L10-L11

It doesn't work. I made a PR on the ECS Fargate folder and Baklava wasn't added. According to GitHub, the later matches take precedence:
https://help.github.com/en/articles/about-code-owners


The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.

I have the following configuration while attempting to use AWS Rest API to invoke a lambda.
import http from "k6/http";
import {check, group, sleep} from "k6";
import {randomIntBetween} from "https://jslib.k6.io/k6-utils/1.4.0/index.js"
import {AWSConfig, SignatureV4} from "https://jslib.k6.io/aws/0.9.0/aws.js"

const awsConfig = new AWSConfig({
    region: "eu-west-1",
    accessKeyId: __ENV.AWS_ACCESS_KEY_ID,
    secretAccessKey: __ENV.AWS_SECRET_ACCESS_KEY,
    sessionToken: __ENV.AWS_SESSION_TOKEN,
})

const lambdaInvoke = () => {
    const signer = new SignatureV4({
        service: 'lambda',
        region: awsConfig.region,
        credentials: {
            accessKeyId: awsConfig.accessKeyId,
            secretAccessKey: awsConfig.secretAccessKey,
            sessionToken: awsConfig.sessionToken,
        }
    })

    const signedRequest = signer.sign({
        method: 'POST',
        protocol: 'https',
        hostname: 'lambda.eu-west-1.amazonaws.com',
        path: '/2015-03-31/functions/FUNCTION-NAME/invocations',
        headers: {
            'content-type': 'application/json'
        },
        applyChecksum: true,
        uriEscapePath: true
    })
    const data = {
        "hi": 'K6'
    }
    return http.post(signedRequest.url, data, {headers: signedRequest.headers});
};

export default () => {
    group("Spike Test Set", () => {
        const startDataRes = lambdaInvoke();
        console.log(startDataRes)
        sleep(randomIntBetween(0, 1));

        check([startDataRes], {
            "status is 200": (r) => r.every((res) => res.status === 200),
        });
    });
};

It is failing with generating the proper signature. The provided access keys and session tokens are valid. Is there some missing
configuration the I have missed?

Hello! Any news about it? I'm facing the exact same error. Here is my code, if it helps in the investigations:
import { AWSConfig, SignatureV4 } from 'https://jslib.k6.io/aws/0.9.0/aws.js'
import { getExprs } from './data/get_data.js'
import http from 'k6/http'

export const options = {
    discardResponseBodies: true,
    scenarios: {
      constant_scenario: {
        executor: 'constant-vus',
        exec: 'sigv4',
        vus: 1,
        duration: '1s',
      },
    },
  }

const awsConfig = new AWSConfig({
  region: __ENV.AWS_REGION,
  accessKeyId: __ENV.AWS_ACCESS_KEY_ID,
  secretAccessKey: __ENV.AWS_SECRET_ACCESS_KEY,
  sessionToken: __ENV.AWS_SESSION_TOKEN,
})

export function sigv4() {
  const signer = new SignatureV4({
    service: 'aps',
    region: awsConfig.region,
    credentials: {
      accessKeyId: awsConfig.accessKeyId,
      secretAccessKey: awsConfig.secretAccessKey,
      sessionToken: awsConfig.sessionToken,
    },
  })

    const exprs = getExprs()
    const now = new Date();
    now.setHours(now.getHours() - 1);
    const start = Math.floor(now.getTime() / 1000)
    const end = Math.floor(Date.now() / 1000)

    for (const expr of exprs) {
      const signedRequest = signer.sign(
        {
          method: 'GET',
          protocol: 'https',
          hostname: 'aps-workspaces.us-east-1.amazonaws.com',
          path: `/workspaces/<my-workspace>/api/v1/query_range?query=${encodeURIComponent(expr)}&start=${start}&end=${end}&step=1m`,
          headers: { "Host": 'aps-workspaces.us-east-1.amazonaws.com' },
          uriEscapePath: false,
          applyChecksum: false,
        },
        {
            signingDate: new Date(),
            signingService: 'aps',
            signingRegion: 'us-east-1',
        }
      )

      const result = http.get(signedRequest.url, { headers: signedRequest.headers })

    }
}

Hey folks 👋🏻 sorry for the delay in my reply, holidays happened 🙇🏻
I'm currently looking into it more thoroughly, but the first thing that strikes me in both your examples is that the uriEscapePath and applyChecksum parameters should be used in the SignatureV4 constructor rather than as an argument to the sign method. I'm not 100% convinced this is it, but that's a good first candidate.
It appears to be a mistake in our documentation website too, which will be addressed as soon as possible.
Does moving those values to the constructor address the issue for you?
  const signer = new SignatureV4({
    service: 'aps',
    region: awsConfig.region,
    credentials: {
      accessKeyId: awsConfig.accessKeyId,
      secretAccessKey: awsConfig.secretAccessKey,
      sessionToken: awsConfig.sessionToken,
    },
    uriEscapePath: false,
    applyChecksum: false,
  })

@mickey101 👋🏻
I've investigated your issue a little bit more, and I think I found the root cause. The Lambda API expects a payload, and when such a payload is present, the sign method needs to know about it. You can set it with the optional body field of the request parameter.
The reason for that is that as part of the AWS signature v4 signing process, the request body is included and used to generate the signature sent to AWS for comparison.
Also, as the body is JSON in your case, we should encode it to a string (this might change in the future, but this is how it's done right now).
Here's an example based on yours that I got to work:
import http from 'k6/http'

import {AWSConfig, SignatureV4} from "https://jslib.k6.io/aws/0.9.0/aws.js"

const awsConfig = new AWSConfig({
    region: __ENV.AWS_REGION,
    accessKeyId: __ENV.AWS_ACCESS_KEY_ID,
    secretAccessKey: __ENV.AWS_SECRET_ACCESS_KEY,
    sessionToken: __ENV.AWS_SESSION_TOKEN,
})

export default function () {
    const data = JSON.stringify({
        key1: 'value1',
        key2: 'value2',
        key3: 'value3',
    })

    /**
     * In order to be able to sign an HTTP request's,
     * we need to instantiate a SignatureV4 object.
     */
    const signer = new SignatureV4({
        service: 'lambda',
        region: awsConfig.region,
        credentials: {
            accessKeyId: awsConfig.accessKeyId,
            secretAccessKey: awsConfig.secretAccessKey,
            sessionToken: awsConfig.sessionToken,
        },
    })

    /**
     * The sign operation will return a new HTTP request with the
     * AWS signature v4 protocol headers added. It returns an Object
     * implementing the SignedHTTPRequest interface, holding a `url` and a `headers`
     * properties, ready to use in the context of k6's http call.
     */
    const signedRequest = signer.sign(
        /**
         * HTTP request description
         */
        {
            /**
             * The HTTP method we will use in the request.
             */
            method: 'POST',

            /**
             * The network protocol we will use to make the request.
             */
            protocol: 'https',

            /**
             * The hostname of the service we will be making the request to.
             */
            hostname: 'lambda.us-east-1.amazonaws.com',

            /**
             * The path of the request.
             */
            path: '/2015-03-31/functions/myFunctionName/invocations',

            /**
             * The headers we will be sending in the request.
             */
            headers: {},

            body: data,
        },
        /**
         * (optional) Signature operation options.
         */
        {
            /**
             * The date and time to be used as signature metadata. This value should be
             * a Date object, a unix (epoch) timestamp, or a string that can be
             * understood by the JavaScript `Date` constructor.If not supplied, the
             * value returned by `new Date()` will be used.
             */
            signingDate: new Date(),

            /**
             * The service signing name. It will override the service name of the signer
             * in current invocation
             */
            signingService: 'lambda',

            /**
             * The region name to sign the request. It will override the signing region of the
             * signer in current invocation
             */
            signingRegion: 'us-east-1',
        }
    )

    const res = http.post(signedRequest.url, data, { headers: signedRequest.headers })
    console.log(JSON.stringify(res, null, 2))
}

@mariana-mendes I haven't double-checked your specific use-case, but could you also verify and try and let me know if that solved the issue on your side? Thank you 🙇🏻

@oleiade Thanks for the answer!!
I've tried to use uriEscapePath: false and  applyChecksum: false in the constructor, removed them, and also tried combinations of the values. But I am still getting 403 :(

Fair enough 😇
The next thing I notice about your specific example is that you include the query parameters directly in the path parameter of the sign method: path: /workspaces/<my-workspace>/api/v1/query_range?query=${encodeURIComponent(expr)}&start=${start}&end=${end}&step=1m.
I believe this is very likely to lead a signature problem indeed, and the reason is that the signature process encodes and signs query parameters separately following a dedicated process.
Could you try passing the query parameters through the dedicated query parameter of the sign method, and see if that helps? I expect something along the lines of:
      const signedRequest = signer.sign(
        {
          method: 'GET',
          protocol: 'https',
          hostname: 'aps-workspaces.us-east-1.amazonaws.com',
          path: `/workspaces/<my-workspace>/api/v1/query_range`,
          headers: { "Host": 'aps-workspaces.us-east-1.amazonaws.com' },
          query: {  // query params arg
            query: encodeURIComponent(expr),  // your actual prometheus query
            start: start,
            end: end,
            step: '1m',
        },
        {
            signingDate: new Date(),
            signingService: 'aps',
            signingRegion: 'us-east-1',
        }
      )

The resulting signed URL should have the query parameters correctly added, and the signature should correctly account for those too. Let me know if that was helpful 🤝

Hi!!, it's working now. My code is something like this:
      const signedRequest = signer.sign(
        {
          method: 'GET',
          protocol: 'https',
          hostname: 'aps-workspaces.us-east-1.amazonaws.com',
          path: '/workspaces/<my-workspace>/api/v1/query_range',
          headers: {"host":'aps-workspaces.us-east-1.amazonaws.com'},
          query: {  // query params arg
            query: expr,
            start: startTime.toString(),
            end: end.toString(),
            step: '1m'

        },
        }
      )

I figured out here: In this case, you don't need to encode the query, and the timestamps need to be strings.
I  was following this tutorial . The tip of the `query`` parameter is already in some documentation? I couldn't find it.
Thank you so much for your help!!! 🚀

Hey @oleiade!
Thanks Including the request body as a string in the signer.sign  body parameter solved the signature issue.
I am happy to close this issue

I'm glad we killed two birds with one stone 🤝
I will look into improving the documentation for it accordingly 🙇🏻


Mentor-Info : Update MENTORS.md

Mentor-Info : Update MENTORS.md

@Aryamanz29 hey, if you have any projects please send the pr or dm me i will add it.


How to move Y axis to left hand side of chart?

By default, when using the series graphs, the Y axis is rendered on the right hand side of the chart, is there a simple way of getting this to be on the left hand side?

Yes, set AxisType to chart.YAxisSecondary (as defined in axis.go). For example:
YAxis: chart.YAxis{
        Name: "Elevation",
        AxisType: chart.YAxisSecondary,
		Style: chart.Style{
			Show: true,
		},
	},

@ssorc  did you get a chance to look at the values being cropped when switching the axis to left side?

YAxis: chart.YAxis{ 		AxisType: chart.YAxisSecondary,  },

YAxis: chart.YAxis{
AxisType: chart.YAxisSecondary,
}, - not work in version 1, and version 2 ; YAxis just gone


Predefined environment variables for credentials

Hi,
I would like to know if there are any predefined environment variables that we can use to configure credentials.
For example, aws sdk for java has AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_SESSION_TOKEN.
Thanks.

@billwert could you help @dhatri308 with their question?

Hello @dhatri308! You can find our reference for environment variables here. These are useful when using the EnvironmentCredential. That credential is part of the credential chain in DefaultAzureCredential which may also be useful to you.
Please let me know if you have other questions.


Ability to set play option defaults

New optional Boolean config options default_random, default_repeat, default_consume and default_single introduced.
If these option are set to true or false then corresponding playback options are set on Mopidy startup. This allows (geeky) users enable those options automatically on every Mopidy startup.

This feature belongs in Mopidy and is tracked at https://github.com/mopidy/mopidy/issues/310.

I believe I will just work on my Mopidy-MusicBox-Webclient fork independently (because you don't seem to be open to virtually any pull requests).
Looks like we have very different opinions on features and quality.

The project mandate is a simple and easy to use client. Configurable
options generally go against this so we want to make sure they are
necessary. We also only want them if they will be useful for the majority
of people. All contributions are appreciated but some are just not aligned
with the project aims.
However, in this particular case, the feature belongs in Mopidy core and
not here. Please don't take it personally and please do send any bug fixes
back upstream to us here.
On 12 Jul 2015 17:40, "Dāvis Mošenkovs"<EMAIL_ADDRESS>wrote:

I believe I will just work on my Mopidy-MusicBox-Webclient fork
independently (because you don't seem to be open to virtually any pull
requests).
Looks like we have very different opinions on features and quality.
—
Reply to this email directly or view it on GitHub
https://github.com/woutervanwijk/Mopidy-MusicBox-Webclient/pull/118#issuecomment-120739405
.

The Mopidy issue 310 is about preserving the state (this is a bit different feature). Does this feature belong here or in core is a good question, but I believe I wouldn't be the only user benefiting from this feature.
I am not taking anything personally (I hope you don't either), but I am respecting my (and your) time and I don't see that my attempts to contribute are productive here.
The worst (but not the only one) example is here: https://github.com/woutervanwijk/mopidy-websettings/pull/12 At first I was told that changes in startup script are required, but when they were completed (+ some testing done) I was informed that the feature is not welcome. Sorry to say, but this was really demotivating for me. Regarding importance of that feature I can agree that it is not the most important one, but I expect the feature not welcome as the very first comment, not as the last one (when the feature is code complete and tested). Afterwards the discussion shifted to globally writable /boot where it ended with my comment about possible solutions (left without response). So on both of these topics I have wasted several hours with no ROI (no changes in Pi MusicBox). Please correct me if I am wrong!
P.S. This is not the only one open-source project to which I have contributed, but, sad to say, contribution/collaboration productivity here was the worst.

I agree it's a useful feature for Mopidy core and the activity on 310 is proof enough that it's popular but I really do think it belongs there rather than a random client.
Regarding https://github.com/woutervanwijk/mopidy-websettings/pull/12, I am sorry that your initial work won't be included, I can see that it's frustrating.  Perhaps if I had looked more closely at it sooner than that wasted effort could have been avoided. I thought that some really good ideas come off the back of it and I intend to make use of what was discussed - hence the PR is still open and still relevant. I've been bogged down with various other things lately and not made the progress I wanted on the next Musicbox release which annoyingly gates a lot of the more interesting stuff.


Can't Generate from Pretrained Story Models

I ran the following command from the examples stories tutorial using the pretrained checkpoints and couldn't get it to work. What is the correct command to generate from the pretrained story model? I saw https://github.com/pytorch/fairseq/issues/285 had a similar question, but I wasn't sure if it was resolved and if so what the correct command was.
python generate.py data-bin/writingPrompts --path data-bin/models/fusion_checkpoint.pt --batch-size 32 --beam 1 --sampling --sampling-topk 10 --sampling-temperature 0.8 --nbest 1 --model-overrides "{'pretrained_checkpoint':'data-bin/models/pretrained_checkpoint.pt'}"

My error is pasted below.
| [wp_target] dictionary: 104960 types
| data-bin/writingPrompts test 15138 examples
| ['data-bin/writingPrompts'] test 15138 examples
| loading model(s) from data-bin/models/fusion_checkpoint.pt
| loading pretrained model
  0%|                                         | 0/474 [00:00<?, ?it/s]Traceback (most recent call last):
  File "generate.py", line 171, in <module>
    main(args)
  File "generate.py", line 104, in main
    for sample_id, src_tokens, target_tokens, hypos in translations:
  File "/juicier/scr121/scr/hughz/fairseq/fairseq/sequence_generator.py", line 95, in generate_batched_itr
    prefix_tokens=s['target'][:, :prefix_size] if prefix_size > 0 else None,
  File "/juicier/scr121/scr/hughz/fairseq/fairseq/sequence_generator.py", line 117, in generate
    return self._generate(encoder_input, beam_size, maxlen, prefix_tokens)
  File "/juicier/scr121/scr/hughz/fairseq/fairseq/sequence_generator.py", line 143, in _generate
    encoder_out = model.encoder.reorder_encoder_out(encoder_out, new_order)
  File "/juicier/scr121/scr/hughz/fairseq/fairseq/models/composite_encoder.py", line 48, in reorder_encoder_out
    encoder_out[key] = self.encoders[key].reorder_encoder_out(encoder_out[key], new_order)
  File "/juicier/scr121/scr/hughz/fairseq/fairseq/models/fconv_self_att.py", line 231, in reorder_encoder_out
    eo.index_select(0, new_order) for eo in encoder_out['encoder_out']
  File "/juicier/scr121/scr/hughz/fairseq/fairseq/models/fconv_self_att.py", line 231, in <genexpr>
    eo.index_select(0, new_order) for eo in encoder_out['encoder_out']
RuntimeError: Expected object of type torch.cuda.LongTensor but found type torch.cuda.FloatTensor for argument #3 'index'```

Sorry, I have not seen this issue before.

Just saw this issue: https://github.com/pytorch/fairseq/issues/348
might be related? It seems resolved in this issue, could you take a look? Thank you!

Ah I pulled to the most recent version and now it works. Thanks a bunch!
On Sun, Nov 25, 2018 at 5:20 AM Huihui Fan<EMAIL_ADDRESS>wrote:

Just saw this issue: #348 https://github.com/pytorch/fairseq/issues/348
might be related? It seems resolved in this issue, could you take a look?
Thank you!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pytorch/fairseq/issues/383#issuecomment-441440042,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEwWmt3Uot4c4B9Z8MUiBUy1gU2muiK5ks5uypkQgaJpZM4YxjxC
.

I still have this problem, even after pulling latest version

Using the latest code, and executing the following command:
 CUDA_VISIBLE_DEVICES=1 python train.py data-bin/iwslt14.tokenized.de-en  --lr 0.25 --clip-norm 0.1 \ --dropout 0.2 --max-tokens 4000  --arch trarmer_iwslt_de_en \ --save-dir checkpoints/transformer --log-interval 200 --no-progress-bar --save-interval-updates 600
when restoring from an unfinished checkpoint (that is, checkpints beside the epoch checkpoints determined by the --save-interval-updates option), it would expect the following error:
 File "/home/frank/fairseq-py/fairseq/trainer.py", line 250, in train_step     self.meters['gnorm'].update(grad_norm)   File "/home/frank/fairseq-py/fairseq/meters.py", line 24, in update     self.sum += val * n RuntimeError: Expected object of type torch.FloatTensor but found type torch.cuda.FloatTensor for argument #4 'other'
It runs fine if restoring fromthe epoch checkpoint file.
And when executing the generate.py file, with code
CUDA_VISIBLE_DEVICES=1 python generate.py data-bin/iwslt14.tokenized.en-de --path checkpoints/transformer/checkpoint_best.pt  --beam 5 --batch-size 128  --quiet
I can see the following error as in previous posts.
  File "/home/frank/fairseq-py/fairseq/models/transformer.py", line 342, in reorder_encoder_out     encoder_out['encoder_out'].index_select(1, new_order) RuntimeError: Expected object of type torch.cuda.LongTensor but found type torch.cuda.FloatTensor for argument #3 'index'

upgrading to pytorch 0.4.1 solved the above problem.


Question regarding class instantiation

Andy,
I've noticed a few places where a class is instantiated, then following it, there's initialization code.
I'm wondering why there's no overloading with optional parameters being used for some of these.
An example is ProjectLoadIssues.  Standard instantiation :
ProjectLoadIssues dlg = new ProjectLoadIssues();
dlg.CanCancel           = false;
dlg.Messages            = messages;
By adding the overload:
    public ProjectLoadIssues(string messages, bool cancel = true, bool cont = true)
    {
        InitializeComponent();
        Messages = messages;
        CanCancel = cancel;
        CanContinue = cont;
    }

the instantiation can be either the original (unless you make Messages, CanCancel and CanContinue private) or the following:
            ProjectLoadIssues dlg = new ProjectLoadIssues(messages, false);

or
ProjectLoadIssues dlg = new ProjectLoadIssues(messages, false, false);
Just curious..
Andy

There's a haphazard mix of constructor arguments and post-construction property setting, without much rhyme or reason to it.  I wouldn't read too much intent into anything. :-)  I was trying to figure out how best to write WinForms/C# code while writing WinForms/C# code, and it's probably obvious that my understanding evolved over time.
The ProjectLoadIssue class should take an enum with three possible states (CanCancel, CanContinue, CanCancelOrContinue) so that it's obvious at the call site what's happening -- it's kind of annoying to run into DoSomething(false, false, true, false, 42) and have to figure out which boolean means what -- and also to present an API that doesn't allow invalid states (disabling both buttons doesn't make sense).  The enum and the (mandatory!) Messages string should be constructor arguments, and there should be no public properties.

I feel the learining curve.  Went through it myself.  Then again when they went to .NET framework, and I still see changes, some make sense, some, not so much.
As far as the Method(false, false, true, false, 42), VS makes that easy..  As you're writing a call, you get the parameter and it's type as soon as you hit the (.  If you want to see it later, just hover over the method name and it'll show you everything.  Would be nice if it showed the info in the documentation block right before the method declaration, but we can't have anything.
Another thing I do when coding forms.  When I have radio buttons, I always create a property with a getter that returns a value for which RB is selected, and sets the proper RB depending on what's sent to it.  Sometimes I'll set up an Enum for it as well, but not usually for the simpler ones.  That way I don't have long buttonName.Checked in if statements.  I use a switch instead.  Makes for easier reading.
Something to maybe consider in the future.

The radio button property sounds like a good idea.  I miss DDX_Radio() from MFC.  (That's probably the only thing I miss from MFC.)  Some people have tried to do this with custom group boxes, but that doesn't seem like a good fit for this.

Moved various form properties into constructor args.  Cleaned up some stuff nearby while I was at it.  Haven't played with radio-button-properties yet.


Vocabulary: action vs intent

Hi
Reading the README and others examples I was surprised at the use of "Action" when describing the intents.
Indeed, it introduces a new term whereas we speak of MVI, aka Model View Intent, where the term action is completely out of the picture.
Furthermore, what's called actions here are some intents: it's not because the user "asks for it" that it'll happen. Some business logic might contradict the user's will here. For example the chosen login might be already given to someone else.
So, why not call these actions intents?
The model would then get a stream of Intent, which is way more in sync with MVI, and all would be simpler.
I suspect I'm missing something but I don't see what so...
++

Hi :)
I'd recommend checking our official docs on MVI, in particular this part: https://cycle.js.org/model-view-intent.html#model-view-intent-summarized

intent() function
Purpose: interpret DOM events as user’s intended actions
Input: DOM source
Output: Action Streams


Ansible action plugin to post messages to ntfy.sh

I thought this might interest people: I've created a small Ansible action plugin which can post messages to ntfy.sh. (I'm aware the uri module can do this as well but think this is a bit simpler to use.)
- name: "Notify ntfy that we're done"
  ntfy:
        msg: "deployment on {{ inventory_hostname }} is complete. 🐄"
        attrs:
           tags: [ heavy_check_mark ]
           priority: 1

Feedback and suggestions / improvements are welcome at https://github.com/jpmens/ansible-ntfy

That's awesome. Thank you for sharing. Added to the docs: https://github.com/binwiederhier/ntfy/commit/62cd51722316039355638bd6169fd868b053ced3

If you like, you could add a concrete example to the examples page too, in addition to what's already there: https://github.com/binwiederhier/ntfy/blob/main/docs/examples.md#ansible-salt-and-puppet


Switch to a professional Workflow

Since our project could increase a lot, I think we have to figure out an appropriate Workflow.
We cannot run the risk of breaking the official release through unwanted changes from a contributor which can push directly to the master.
What do you think about the Gitflow https://www.atlassian.com/git/tutorials/comparing-workflows#gitflow-workflow
In a nutshell, its aim is to separate the official release (which lives into the master branch) from an
an integration branch (tipically called the develop branch).
Here it's explain even more better: https://leanpub.com/git-flow/read

I'm a big fan of this

Yea, this seems great.  It's my understanding that this is how it's done in professional settings and it would be good for us to start working as the professionals do.

We can keep working the same way until the release  and then freeze master and create the develop branch

We are already using workflow so I'm closing this


⚠ Bofrost.lu has degraded performance

In 2db3318, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1285 ms

Resolved: Bofrost.lu performance has improved in 82183b5 after 7 minutes.


Specify compression algorithm in writer

Is there any way to specify which compression algorithm you want to use when writing Avro?

Yes, the codec parameter in the writer: https://github.com/tebeka/fastavro/blob/master/fastavro/writer.py#L443-L444

Thank you


Update prod Vector Tiles with Mapzen API keys

Preview: https://precog.mapzen.com/mapzen/mapzen-docs-generator/vector-v0.10.5-doc1/documentation/vector-tiles/api-keys-and-rate-limits/

Must also land with: https://github.com/mapzen/mapzen-docs-generator/pull/198

Verified on precog, and 198 has just been merged.

Thanks @nvkelso! All seems to be updated here and in overview for the anchor link.
fixes #197


Update package.json

https://nodesecurity.io/advisories/54

Looks good to me. @mlmorg Can we land this?
Proposed CHANGELOG message and release command:
1.5.1 - Upgraded to<EMAIL_ADDRESS>to resolve security advisory via @jacobp100 in #38

./release 1.5.1

Sweet, thanks for the quick merge @mlmorg =)

No problem!


Missing functionality for OAuth2 Password Flow

If you use OAuth2 PAssword Flow you dont get a Button for "Get Token"

Yes, password-flow exchange-token is not supported
we need to clear some legal/internal dependency for that which I do not see being resolved soon.
Most likely it will not be supported.
Even though it is a supported type in OpenAPI, RapiDoc will limit it to documentation only and not provide the functionality to get a token.
It is not a recommended way anymore
https://tools.ietf.org/html/draft-ietf-oauth-security-topics-13#section-3.4
https://oauth.net/2/grant-types/password/


added preview image

What does it do ?
Added a preview for the image
Before

After

😍 Nice!

This doesn't seem to work if the image is set to use a media source other than the site root.

Works great now, thanks.


Fix cached/indexed artifacts from disabled repositories are still reachable

@jdcasey seems this pr encountered a metrics error for ftest in 1.2.x branch. Waiting for fix from @bxf12315 on 1.2.x branch.

Seems funny that the CI env can pass without error but I encountered the zabix metrics error local. Not sure why but seems the code itself does not have any problem

Oops, I removed the 1.2.x branch so we can simplify to master + 1.1.x for now, until we're ready to release 1.2.0. We're not focusing on anything beyond 1.2 for now, so master should be good enough for that work. I'll apply your commits to master and open a new PR.


feat: add bq link to preview query view

Here’s a well-formatted version of your GitHub pull request description:

Add Feature to View a Preview Query Job in the BigQuery Console
This PR introduces a feature that allows users to view a preview query job directly in the BigQuery console.

What’s New

Clicking the link takes the user to the corresponding query job in BigQuery.
This eliminates the need to manually copy the compiled query for ad-hoc testing in BigQuery.

Need Help Testing

I’d appreciate help verifying that the method I use to parse the bigQueryJobId into a functional link works for others, as it currently works for me.

The user needs to have BQ Job List permission in GCP to be able to use the link.
There might be a better way to fetch the job ID, as we currently use two similar variables inside of the window event listener (jobId and bigQueryJobId). This could potentially lead to confusion.

Hi @HampB, definitely a good feature to have. looks good to me, ill test it and let you know if I encounter any issue

Hi @HampB ,  I tested it locally it works as expected. Regarding the inconsistent variable names, you are right. I have sent an MR to address the issue.

Thanks for the changes @ashish10alex , variable usage makes more sense now.
I've tested the changes and it seems to work as intended.


fs watching

When docs change, generate 'em!
http://search.npmjs.org/#/tree-watcher perhaps?

This can easily be done with grunt-groc and grunt-contrib-watch.


perf(audiorender): improve preformace in iOS audio render

not use atempo filter on AudioQueue render
use filter to convert planer audio instead of in copyPCMData

Signed-off-by: pingkai<EMAIL_ADDRESS>

Codecov Report

Merging #459 into develop will decrease coverage by 4.10%.
The diff coverage is 85.71%.

@@             Coverage Diff             @@
##           develop     #459      +/-   ##
===========================================
- Coverage    68.73%   64.62%   -4.11%
===========================================
  Files          216      217       +1
  Lines        11760    11772      +12
===========================================
- Hits          8083     7608     -475
- Misses        3677     4164     +487

Impacted Files
Coverage Δ

framework/filter/IAudioFilter.h
100.00% <ø> (ø)

framework/render/audio/filterAudioRender.h
50.00% <ø> (ø)

framework/render/audio/filterAudioRender.cpp
87.28% <83.33%> (+1.13%)
:arrow_up:

framework/filter/ffmpegAudioFilter.cpp
81.46% <87.50%> (+0.36%)
:arrow_up:

framework/render/audio/CheaterAudioRender.h
100.00% <100.00%> (ø)

framework/tests/dataSource/ipList.h
0.00% <0.00%> (-100.00%)
:arrow_down:

framework/tests/demuxer/demuxerUnitTest.cpp
0.00% <0.00%> (-100.00%)
:arrow_down:

framework/tests/dataSource/dataSourceUnitTest.cpp
0.00% <0.00%> (-93.85%)
:arrow_down:

framework/tests/decoder/decoderUnitTest.cpp
0.00% <0.00%> (-93.62%)
:arrow_down:

framework/tests/demuxer/demuxerUtils.cpp
0.00% <0.00%> (-76.00%)
:arrow_down:

... and 18 more

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 60e65ba...314b2db. Read the comment docs.


expose application on port 8443 does not work as expected

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
port 8443 does not populate correctly in ingress-gateway. I have a basic scenario with SSL PASSTHROUGH.  in my container inside mesh I have both Apache (SSL termination at 8443) and Nginx (SSL termination at 443).following is my config:
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: myapp-gw
namespace: myapp-istio
spec:
selector:
istio: ingressgateway
servers:
- port:
number: 443
name: https
protocol: HTTPS
tls:
mode: PASSTHROUGH
hosts:
- "myapp.istio.local"
- hosts:
- "myapp.istio.local"
port:
name: https-web
number: 8443
protocol: HTTP
tls:
mode: PASSTHROUGH
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: myapp-vs
namespace: myapp-istio
spec:
hosts:
- myappistio.local
gateways:
- myapp-gw
tls:
- match:
- port: 443
sniHosts:
- myapp.istio.local
route:
- destination:
host: sfs
subset: v1
port:
number: 443
- match:
- port: 8443
sniHosts:
- myapp.istio.local
route:
- destination:
host: myapp
subset: v1
port:
number: 8443

apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
name: myapp-dr
namespace: sfs-istio
spec:
host: myapp
trafficPolicy:
tls:
mode: ISTIO_MUTUAL
subsets:
- labels:
version: v1
app: myapp
name: v1
apiVersion: security.istio.io/v1beta1
kind: PeerAuthentication
metadata:
name: myapp-pa
namespace: sfs-istio
spec:
selector:
matchLabels:
app: myapp
mtls:
mode: STRICT
output from istioctl listener ingress-gatewaypo is
<IP_ADDRESS> 8443  SNI: myapp.istio.local Cluster: outbound|443|v1|myapp.myapp-istio.svc.cluster.local
I expect that both 8443 and 443 exist in output. because 8443 does not exist so traffic does not reach to apache web-server and the error is HTTP/1.1 404 Not Found
if I remove 443 from GW and VS, I can see 8443 and apache webserver works
<IP_ADDRESS> 8443  SNI: myapp.istio.local Cluster: outbound|8443|v1|myapp.myapp-istio.svc.cluster.local
FYI: I test with/without  8443 in the ingress-gateway service manifest. default ports are 443/8443  and 80/8080
[ ] Docs
[ ] Installation
[x ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
expect port 8443 expose same as other ports
1-my cluster is rancher k3s
2- istio 1.9.6
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
istioctl version
client version: 1.9.4
control plane version: 1.9.6
data plane version: 1.9.6 (4 proxies)
kubectl version
ubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:59:11Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.11+k3s1", GitCommit:"39552458bc2acc8dc06926ff622d23c0754ddeae", GitTreeState:"clean", BuildDate:"2021-05-20T00:50:19Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}
How was Istio installed?
Rancher-istio
Environment where the bug was observed (cloud vendor, OS, etc)
on prem cluster. k3s on centos 7.9
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

it is hard to read your yaml file. you can use "```yaml" to reformat it.
and just like you said, 8443(target port) is mapped to 443(port) in istio-ingressgateway svc. so which port you want to map to 8443 in svc? has the targetPort identified in istio-ingressgateway containerPort?
FYI: I test with/without 8443 in the ingress-gateway service manifest. default ports are 443/8443 and 80/8080

kind: Gateway
metadata:
name: myapp-gw
namespace: myapp-istio
spec:
selector:
istio: ingressgateway
servers:
- port:
number: 443
name: https
protocol: HTTPS
tls:
mode: PASSTHROUGH
hosts:
- "myapp.istio.local"
- hosts:
- "myapp.istio.local"
port:
name: https-web
number: 8443
protocol: HTTP
tls:
mode: PASSTHROUGH```

@hobbytp I have apache server inside mesh on port 8443 (SSL enabled) and want to PASSTHROUGH traffic to that server. I update yaml file


fix: Process Network Data Handler

Download network data in the handler.
Otherwise, we are downloading the network datafile every time we run a command (Also if that datafile goes down, it would block us running commands!)

:tada: This PR is included in version 6.14.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Is there a predictor?

Do you have a simple predictor somewhere? Looking for something that takes in a simple image and then predicts the program using your model.

Not yet, I don't expect this codebase to be actually useful for turning images into programs because the DSLs are very small and narrow. If you still want to try it you can look at scripts/td_search_eval.py
The codebase is meant mostly for academic use on the technique and reproducibility + transparency of evaluation numbers in the paper.
I am working on making it easier to use it on a custom image! I just don't expect it to work on arbitrary images very well, because the DSLs just can't express them.

Turns out we have a problem so "simple", what you have might be sufficient.

Here is an example of an image I want to fit. Should it be able to fit this one? It seems to get sort of close, but doesn't seem to be able to solve it.

Here is an example of an image I want to fit. Should it be able to fit this one? It seems to get sort of close, but doesn't seem to be able to solve it. It's hard to see here, but it's just a rectangle inside a 128x128 image.

You might be able to solve a problem like that using a simple genetic algorithm to be honest.

Yeah, we already solve it a different, very simple way, but the algorithm in this paper could lead to something better for more complicated situations.

I'm working on making this repository actually useful for new images! Stay tuned. I sadly fell sick right after release so it's been a bit slow.

@revalo Please get well. Your paper is very promising. Definitely a step in the right direction. Making the repo code to work well would be awesome to do reasearch into code diffusion.


Add hmd.cpp to amalgamated.cpp

The file hmd.cpp is missing in amalgamated.cpp, causing unresolved references at link time when compiling using a custom build-system.

Fixed: https://github.com/bkaradzic/bgfx/commit/33057ea86c8c5e0126dda480c2c2aadca6a35b3d


[?bug] BaseHtml line 1938 - v<IP_ADDRESS> - Object of class "..." could not be converted to int - proposed workaround

Hello,
I'm getting the next error after updating from 2.0.44 to <IP_ADDRESS>: Object of class "..." could not be converted to int
Please check BaseHtml:1938
https://github.com/yiisoft/yii2/blob/73902f0730454f499d1a8bb49382e5021943656e/framework/helpers/BaseHtml.php#L1938C44-L1938C44
var_dump($selection)
/project/vendor/yiisoft/yii2/helpers/BaseHtml.php:1938:
object("...")[315]
  protected 'value' => int 0
  protected string 'label' => string 'First' (length=7)

var_dump($key)
/project/vendor/yiisoft/yii2/helpers/BaseHtml.php:1939:int 0

Workaround:
$selected = is_object($selection) ?
                                $selection->value == $key : $selection == $key;

Should i keep this workaround or im getting the error due of my Enum:
/**
 * @method static self first()
 * @method static self second()
 * @method static self third()
 */
class BookSubject extends Enum
{
    /**
     * @codeCoverageIgnore
     */
    protected static function values(): array
    {
        return [
            'first' => 0,
            'second' => 1,
            'third' => 2
        ];
    }

    /**
     * @codeCoverageIgnore
     */
    protected static function labels(): array
    {
        return [
            'first' => \Yii::t('app', 'first'),
            'second' => \Yii::t('app', 'second'),
            'third' => \Yii::t('app', 'third')
        ];
    }
}

Enums are not supported yet but we will be happy to provide it. Do you have a time to prepare the PR maybe?

Sure, i have just created the PR: https://github.com/yiisoft/yii2/pull/19928
Could i use this fix for <IP_ADDRESS> or do i have to wait for the next release? Thanks


Add CM to CMO's locker

Discussed and having 1 on station is fine.
If sci really want one it needs to be nerfed to shit.

no this just means theyll give it to paramed roundstart

wrong again
what will happen is following:

cmo will not give paramed their monitor
cmo will not look at monitor for the entire round with 10 ghosts booing medical

colonial marines in CMO's locker let's go


gradient checkpointing needs static graph

RuntimeError: Expected to mark a variable ready only once. This error is caused by one of the following reasons: 1) Use of a module parameter outside the forward function. Please make sure model parameters are not shared across multiple concurrent forward-backward passes. or try to use _set_static_graph() as a workaround if this module graph does not change during training loop.2) Reused parameters in multiple reentrant backward passes. For example, if you use multiple checkpoint functions to wrap the same part of your model, it would result in the same set of parameters been used by different reentrant backward passes multiple times, and hence marking a variable ready multiple times. DDP does not support such use cases in default. You can try to use _set_static_graph() as a workaround if your module graph does not change over iterations.
Parameter at index 753 has been marked as ready twice. This means that multiple autograd engine  hooks have fired for this particular parameter during this iteration. You can set the environment variable TORCH_DISTRIBUTED_DEBUG to either INFO or DETAIL to print parameter names for further debugging.
https://discuss.pytorch.org/t/ddp-and-gradient-checkpointing/132244/3
https://github.com/mlfoundations/open_clip/blob/c933765dc557d88e15be968e78d7580d95f86af8/src/training/main.py#L156
trying to figure out how to do this with accelerate

https://github.com/huggingface/accelerate/pull/637 here's the fix

adding an option here, will PR later

https://github.com/lucidrains/DALLE2-pytorch/pull/226

fyi 2x ram saving using grad checkpointing once this is fixed

@rom1504 nice! thanks for figuring this one out!

Hi @rom1504, is there a fix using the pytorchlightning and hydra library as well? I'm using the hydra library to initialise my model which is of type pytorchLightning. Facing similar issue, any workaround possible?


jstree.min.js:3 Uncaught TypeError: Cannot read property 'scrollLeft' of null     at a.jstree.plugins.types.get_state (jstree.min.js:3)     at a.jstree.plugins.types.save_state (jstree.min.js:5)     at a.jstree.plugins.types. (jstree.min.js:5)     at e (jquery.1.11.min.js:2)

Hi,
I am trying to do the select_node but it's giving me the above error ..
I have created node using create_node and get the created information throgh get_node it's giving me the correct information but when i try to select the same node through select_node it's giving me the follwoing error .
jstree.min.js:3 Uncaught TypeError: Cannot read property 'scrollLeft' of null
at a.jstree.plugins.types.get_state (jstree.min.js:3)
at a.jstree.plugins.types.save_state (jstree.min.js:5)
at a.jstree.plugins.types. (jstree.min.js:5)
at e (jquery.1.11.min.js:2)

That can only mean there is no tree parent available - maybe you discarded the DOM node somehow (perhaps removed it). If that is not the case - please provide a demo (jsFiddle would be great), so that I can help you, I am closing this until further information is provided.


Allow specifying control plane service for actors and/or reminders

Description
This PR lets users configure their solution/ControlPlaneService for actors/reminders.
If nothing is given, traditional placement and inbuilt reminders will be used.
Issue reference

Please reference the issue this PR links with: #7203
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/test-version-skew

@DeepanshuA see conflicts

@DeepanshuA see conflicts

Resolved

/test-version-skew

/ok-to-test

/ok-to-test

/test-version-skew


[BUG]:  llama2 training on multi-node slurm, report error: errno: 98 - Address already in use

🐛 Describe the bug
RuntimeError: The server socket has failed to listen on any local network address. The server socket has failed to bind to [::]:29601 (errno: 98 - Address already in use). The server socket has failed to bind to <IP_ADDRESS>:29601 (errno: 98 - Address already in use).
srun: error: HOST-10-140-60-1: tasks 0-5,7: Exited with exit code 1
Error: failed to run torchrun --nproc_per_node=8 --nnodes=1 --node_rank=0 --master_addr=<IP_ADDRESS> --master_port=29601 pretrain.py --config 70b --grad_checkpoint --batch_size 4 --num_epochs 30 --max_length 4096 --lr 3e-4 --weigth_decay 0.1 --warmup_steps 2000 --mixed_precision fp16 --save_interval 5000 --save_dir 70B_pretrain_ckpt on <IP_ADDRESS>, is localhost: True, exception: Encountered a bad command exit code!

The start command as above, it reported an error when running multi-node model training on the cluster.
I am sure the port was not been used.
What can I do to trouble-shoot the problem ?
How can I run the training on a cluster ?
Environment
torch  1.13.1+cu117
cuda-11.7
Python 3.10.0

ps -ef | grep
then kill -9 the demon which bind to the port

ps -ef | grep
then kill -9 the demon which bind to the port

I have done this before, however it doesn't work. And I'm sure the master address and port are available.
Still thank you very much.

Finally , I solve the problem as below :
First, using python xx.py instead of colossalai run --nproc_per_node 8 xx.py works well.
So the start command is srun -p replacement -N 4 -n 32 --ntasks-per-node=8 --gpus-per-task=1 python benchmark.py -c 70b -g -x -b 2 --max_length 4096  --tp 1 --pp 1 > train_70B_benchmark.log 2>&1 &
Second, there are some code modifications：
In benchmark.py  line 79,
colossalai.launch_from_slurm(config={}, host=get_master_node(), port=12346) , instead of colossalai.launch_from_torch({})
And function get_master_node is :
`def get_master_node():
import subprocess, os
if os.getenv("SLURM_JOB_ID") is None:
    raise RuntimeError("get_master_node can only used in Slurm launch!")
result = subprocess.check_output('scontrol show hostnames "$SLURM_JOB_NODELIST" | head -n 1', shell=True)
result = result.decode("utf8").strip()
return result

`


Clearer, more granular configuration needed

I found this project as a possible replacement for FlareDNS, which recently seems to have stopped updating my Windows machines properly. It seemed like it would be a pretty simple drop-in, configure, and go, but that hasn't been my experience.
The documentation doesn't really say what putting in "your details" will do, but from reading the code it looks like the app updates every single A record in the zone you give it to the current machine's public IP. Thankfully I didn't configure it correctly, or most of my websites would have been knocked offline until I put the right IPs back in.
Am I missing a way to specify the zone (e.g. mydomain.name) and then specify only a single subdomain (e.g. windows1.mydomain.name) to be updated?
I hate to misuse the issue tracker like this, but since finding @birkett on Twitter didn't work out I needed to just get in touch however I could.

Filtering and selecting individual domains is a planned feature. I plan on working on this further, soon.

Any progress?  I would really like a Windows client to update CloudFlare, without having to install perl or php on my Windows server, but only need to update 5 hosts in a zone with about 20 other records.

zfanta kindly committed a small patch to add checkboxes. This was merged in yesterday, and allows you to select specific hosts to update. That should get you up and running.
There's more work happening on this, which will be merged soon.

That's great!  Do you have a build?  I only see the source and the initial release.

To clarify further - filling in the "Domain" box in the settings will correctly limit the update process to only that root domain. "example.com" in the Domain box will fetch and update A records for "*.example.com", all other domains on the account will be ignored.
With zfanta's commit yesterday, there are now additional checkboxes in the host list. Only checked hosts will be updated.
The process is a little bugged right now, as the checked items are not saved, and will revert to unchecked after every update. I'm working to fix this right now, and will push some new binaries tonight.

Awesome. Thanks for your work on this.

Binaries added to the releases tab.
I will keep this issue open for now. I still need to create the proper documentation, and possibly revisit the code for this. It could be cleaner. (possibly use an OnChanged callback on the checkboxes).

Closing this now that the README has been updated, and filtering / service support is working as intended.
The contents of README will eventually be split into Wiki pages.


[MRESOLVER-33] New class 'DefaultDependencyManager' managing dependen…

…cies on all levels supporting transitive dependency management.

ITs running...

@slachiewicz have a look


Screen for edit signature fails with checked 'Edit RAW HTML'

Hi
I don't see any issue for this problem.
MacOs Sierra 10.12.4
Versión 2.0.15 (2.0.15)
Bug?
Not pluginx
Using SMTP/IMAP account
When I try to edit my signature, error for "edit box" when click on Edit RAW HTML

Same here, with Windows 10 Pro. The frame containing the HTML text can't be resized, making it hard to edit the text directly. As a workaround, I just select all, copy to a text editor, make the adjustments there and paste it back. Not very friendly.

Same results with multiple custom and default themes as well.


release 4.0.1

@katspaugh can you merge/tag/release this?

Coverage remained the same at 80.512% when pulling f153e1fbec38688a678e3aaa00ea2da84ba99639 on release-401 into 4e2375e20a84ab1ca15b74dc25cfddb769d03e40 on master.

Done, thanks! ✅


Adding an extra header disturbs the allignment of other headers

Describe the bug (required)

Sandbox link :
https://codesandbox.io/s/confident-fermi-hlum3?file=/src/App.js
Steps to reproduce the behavior:
Create columns as mentioned in sandbox
As you observe , column header : FirstName & LastName should be parallel to Info. But with react table they are parallel to : Age,Visits,Status, ProfileProgress.
Is there a way cells on top of FirstName and LastName be removed ?
Expected behavior (Recommended)

You can fiddle with the rowSpan of these headers if you like, but this is currently beyond the scope of React-Table since it's a headless utility, not a component.


python310Packages.bibtexparser: 1.1.0 -> 1.2.0

Motivation for this change
Fix build (https://hydra.nixos.org/build/163504135, https://hydra.nixos.org/build/163523665, https://hydra.nixos.org/build/164496223)
Preparation to fix papis.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build python310Packages.bibtexparser python310Packages.papis


Remove Zookeeper, Logstash from Docker in control node image in README

As of #1130 and #873, this image is outdated. Zookeeper should be outside of Docker, and logstash should be removed. We might also want to include mantlui and Vault.

Looking at the history of the image, it looks like maybe @ryane would be in charge of these images?

the originals are in a Keynote file in docs/_static/diagrams.key


Just fixing the verb typo

Release Playbook

[ ] Rebase against master
[ ] Code review
[ ] Merge into master
[ ] Verify changes at http://site-staging.convox.com
[ ] Promote release on site-production in the convox/production Rack

Thanks!


Efficiently handle 3-bytes pixel formats

Signed-off-by: ahcorde<EMAIL_ADDRESS>Related to this commit in RVIZ1 https://github.com/rhaschke/rviz/commit/2b31dc4be241e3ebd3a92c0f94d56fdb71391d51

Linux
Linux-aarch64
macOS
Windows

Windows


homeassistant-core and wyoming container docs update, custom wake word

Hi,

Final changes to homeassistant-core and wyoming container docs
Add example custom wake word model for wyoming-openwakeword

@ms1design wyoming-openwakeword is now failing to build on JP5 / L4T R35.4.1 because of tflite-runtime-nightly dependency - do you know what changed?
+ echo 'wyoming-openwakeword: 1.10.0'
+ pip3 install --no-cache-dir --extra-index-url https://www.piwheels.org/simple 'wyoming-openwakeword @ https://github.com/rhasspy/wyoming-openwakeword/archive/refs/tags/v1.10.0.tar.gz'
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting wyoming-openwakeword@ https://github.com/rhasspy/wyoming-openwakeword/archive/refs/tags/v1.10.0.tar.gz
  Downloading https://github.com/rhasspy/wyoming-openwakeword/archive/refs/tags/v1.10.0.tar.gz
     | 5.3 MB 22.7 MB/s 0:00:00
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
INFO: pip is looking at multiple versions of wyoming-openwakeword to determine which version is compatible with other requirements. This could take a while.
ERROR: Could not find a version that satisfies the requirement tflite-runtime-nightly (from wyoming-openwakeword) (from versions: none)
ERROR: No matching distribution found for tflite-runtime-nightly

@dusty-nv I have not builded it on JP5 / L4T R35.4.1 unfortunately. Need to do the bday present unboxing 🫣 to try on that with JP5, but really didn’t had much free time for that last days.

Oh yea, don't worry about setting up for JP5/ect - I will handle that (you might just wanna wait to flash that unit for JP6 GA to come out any day now...) - I was just wondering if you knew why it now needs TFLite and if that's possible to resolve or disable on Ubuntu 18.04

Oh yes that too, I'm not with a hassle with unboxing also because I'm waiting for JP6 GA 👍 wyoming-openwakeword doesn't use cuda yet 🙈 I have that on my todo list in docs. I think we just need to build it against onnxruntime, but I did not have much time to check if it requires any patching in the openwakeword codebase.

wyoming-openwakeword built on JP5 before (https://hub.docker.com/r/dustynv/wyoming-openwakeword/tags) and I didn't see any changes to the dockerfile in this PR related to TFLite - maybe the change came from upstream?

Regardless, merged this and the docs updates into master awhile.  All ready for tomorrow :grinning:

Nevermind about JP5, other of the wyoming containers are failing too, and overall its probably unsustainable to support both JP5/JP6 (for Wyoming at least), so let's just focus on JP6 support for Wyoming :+1:

I will investigate that later 👍


Add code.

I think it would be nice to do so 🤗

What a coincidence, I too think it would be nice.


[SR-2895] Audit and resolve the Optional-as-Any warnings in Foundation

Previous ID
SR-2895

Radar
None

Original Reporter
@belkadan

Type
Bug

Additional Detail from JIRA

Votes
0

Component/s
Foundation

Labels
Bug

Assignee
None

Priority
Medium

md5: 770b9f93f7f3d50495b3f19fbac47a8f

Issue Description:
Both swift-corelibs-foundation and the Apple Foundation overlay (swift/stdlib/public/SDK/Foundation) have quite a few warnings for implicit conversion of Optional to Any; it is likely that at least some of these are true issues (particularly the ones in string interpolations). Every one of these warnings should be addressed in some way.

This is done, and #5000 also addresses all outstanding warnings.


Usable with blue board?

I could flash the FW for the blue board from the other repo (H8mini_blue_board), but this doesn't seem to work. Is there a dual mode version which works with a blue one?

the blue firmware is dual mode only, there is an option to make it acro only, but it's dual by default
It also starts in level mode, gestures are used to toggle between modes

good to know, thank you!


Airplane Mode Icon

Icon Request

Icon name: Airplane
Use case: Airplane Mode Icon for mobile

@mayurrawte: We actually already have an airplane icon: https://lucide.dev/icon/plane?search=plane
It was under the name "plane" and missing the tag airplane, so thanks for bringing that to our attention, I've added the tag so that people will find it easier in the future. :)