Gateway properties are now 'Negotiate client certificate' under the Custom Domains blade

This needs updating as the documentation still states 'Request client certificates'.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 51769134-4b97-0a48-3031-cbcea10ca714
Version Independent ID: dc70bd8c-54be-1592-2137-aed9cae0094b
Content: Secure APIs using client certificate authentication in API Management - Azure API Management
Content Source: articles/api-management/api-management-howto-mutual-certificates-for-clients.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

@DrReedo The setting mentioned at the top of the page is only for the consumption tier which is correct.

@DrReedo Just following up here... Hope my previous comment clears things up.

@DrReedo Hope my previous comment clears things up.
Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Hi Pramod,
Can the documentation also include details of what’s required in the other tiers?
thank you
Claire Reed | Senior Engineer (MS Dynamics) | Corporate Systems Team
IT Services, University of the West of England, Coldharbour Lane, Bristol BS16 1QY
Tel: 0117 32 81058
My working days are: Monday, Tuesday, Wednesday and Thursday (8.15am-2pm)
This email and any attachments are confidential to the intended recipient. If you are not the intended recipient please delete it from your system and notify the sender.
From: Pramod Valavala<EMAIL_ADDRESS>Sent: 23 September 2019 07:32
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Claire Reed<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Gateway properties are now 'Negotiate client certificate' under the Custom Domains blade (#39105)
Closed #39105https://github.com/MicrosoftDocs/azure-docs/issues/39105.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/39105?email_source=notifications&email_token=AEJFZVNZVA7EDGEJPTA7NRTQLBPHRA5CNFSM4IX4TFQKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOTYTLV3Q#event-2653338350, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEJFZVJME6RQNXA53W3DR7TQLBPHRANCNFSM4IX4TFQA.


Create Data Model

Do all work for this issue in a branch named issue-5.
Course collection/schema, default courses.

branch issue-5 published; added course and gateway collections/schema; created CourseItem.jsx (one row of the transcript table)
^haven't updated any of the /pages/ yet so no visible changes to the application


x/tools/cmd/guru: give an option to exclude test code from the search

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.10.2 linux/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/vimal/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/vimal/gowork"
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build593363879=/tmp/go-build -gno-record-gcc-switches"

What did you do?
used guru to list callers of a function.
What did you expect to see?
the callers of the function
What did you see instead?
guru returns all the callers of the function, including test code.
Is it possible to give an option to exclude test code while doing the search?
an option to exclude test code from search will not only reduce the time taken to complete the search, but also give lesser results to the editors to work with.

guru was deleted in https://github.com/golang/go/issues/65880; closing as obsolete. Incidentally, gopls gets this right.


restart the docker container ,web page not restart

The issue will be closed without any reasons if it does not satisfy any of following requirements:

Please speak English, we have forum in Chinese.
Please post questions or config/deploy problems on our forum: https://discuss.gogs.io, here are bugs and feature requests only.
Please take a moment to search that an issue doesn't already exist.
Please give all relevant information below for bug reports; incomplete details considered invalid report.

You MUST delete above content including this line before posting; too lazy to take this action considered invalid report.

Gogs version (or commit ref):
Git version:
Operating system:
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist (usually found in log/gogs.log):

Description
the docker-compose.yml is here
version: "2"
services:
        gogs:
          image: gogs/gogs
          volumes:
              - ./data:/data
          ports:
              - "10022:22"
              - "10080:3000"

the first time . i do docker-compose up gogs . and fellow the document . ervery was fine .
but . some days  later.  i restart the gogs service . git is ok, my friends can git push normal .
but i can't enter  the manger web page http://localhost:10080.   so i try to enter the container and curl.
docker-compose exec gogs sh
then curl http://localhost:3000.  not work. so i belief the web not restart .
...

finally i found the workround.
if you change the port when setup. you must change the mapping port too.
so，change the port in the config。
ports:
- "10022:22"
- "10080:10080"


UI/UX issues

Epic to collect all UI/UX issues on the chat integration:
Starting with: https://github.com/liteflow-labs/marketplace-template/pull/31#issuecomment-1303154546

[ ] Before typing a wallet address, the cursor is very small
[ ] When creating a new chat an typing an address, if the address isn't found and the chat drawer is not opened, the error message appears below viewport and the back arrows moves down
[ ] The border is a bit dark, maybe something like a lighter gray with a drop shadow would look better.

Another one, on full screen the demo app is not aligned, might be related to https://github.com/liteflow-labs/chat/pull/22


sql server

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

creacionismos de sql server

This is a Windows Container image only - Please see the documentation for this image and the requirements.
To learn more about Windows Containers, please see this post:
https://blog.docker.com/2016/09/build-your-first-docker-windows-server-container/
Additionally, if you're running Docker for Windows, you can switch to using linux/windows containers:
https://docs.docker.com/docker-for-windows/#switch-between-windows-and-linux-containers


⚠ Samsung has degraded performance

In be5268d, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2258 ms

Resolved: Samsung performance has improved in f169d29.


Code explanation help

Hello again and thanks for the great repo,
I have some questions about the code which will be happy if you could help me with.
first is, what is the use of class 'FrameCallback'? since it is extending the 'Choreographer.FrameCallback' I can geuss that it is a helper class for updating animation, am I right?
Since I am going to just put one model without animation on the screen, is this class still needed? or I can just use the 'update' method in ARCore for that, for just updating the model per frame?(I am guessing the update method in ArCore class is doing the job of the override method 'onDrawFrame' right? )
Thank you!

FrameCallback is provides added functionality to android.view.Choreographer. Choreographer runs a callback when it's time to render a frame. FrameCallback has a frame limiter and supports skipping frames. In our app I will turn on frame skipping when the device starts to throttle due to high temperature warnings. You can remove some of the added functionality but at the very least I would still use Choreographer to callback when it's time to render a frame.

If all you want to do is update the model I would remove these lines
val frameCallback =
    FrameCallback(
        arCore,
        doFrame = { frame ->
            //if (frame.getUpdatedTrackables(Plane::class.java)
           //         .any { it.trackingState == TrackingState.TRACKING }
            //) {
            //    arTrackingEvents.tryEmit(Unit)
            //}

            lightRenderer.doFrame(frame)
            //planeRenderer.doFrame(frame)
            modelRenderer.doFrame(frame)
        },
    )

Thank you.
I was going through the code and I see there are classes like 'BaseGestureRecognizer' for drag, scale and pinch.
What I want to do is a simple click on screen and loading the glb file, do you have any hint how to handle it in this code without gestures? I can't completely spot the line just for loading. in model renderer I saw you have two update and move. but I think in my case just an update is applied.
Since I move to filament because I cannot load obj files in just ARCore I think using filament is the only way loading gab files.

Filament is the only open source library I have found that can render GLB/GLTF models. Loading models directly with OpenGL is possible but requires a lot of work. Which is why Google has a team of developers a cross platform library for loading GLB/GLTF files and rendering them using physically based rendering techniques.
This project is just a starting point to get ARCore working with Filament which can be modified for your use case. It's not attempting to be a framework or game engine. Just a simple sample to get started. Sceneform was trying to be a framework/game engine that has more features but is more complex and difficult to modify if it doesn't mean your needs.
arCore.frame.hitTest is used to get the location for the model. I just render the model at the coordinates from the HitResult. ARCore will update sometimes update the position of tracked surfaces. If you want to make sure that the model position is updated when the tracked surface position changes, call .createAnchor() on HitResult to get an Anchor. That's what Google's documentation recommends.


fix(erc721): display custom ERC721 token on wallet portfolio

Issues

Cannot add/remove ERC721

~Currently fetching owned tokens by rpc call getPastLogs to read block and filter by Transfer events~
~But getPastLogs or getPastEvents only allows 2048 block in maximum, it will cause exception if too long without running the scan action. And waiting repeatedly fetching will also result in bad user experience~
because of immutable state to update

somehow the states became frozen under mutations with such encountering cases

state.ercNftTokensCustom.push(...)
state.ercNftTokenIds.push(...)
Vue.set(state.walletBalance, ...)
state.ercNftTokenIds[index] = c
state.ercNftTokensCustom.splice(...)

Cannot display ERC721 image and metadata

getTokenURI has missing / to concat the IPFS ID hash
ERCNftView

getter img depends on metadata but didn't watch it
img didn't handle IPFS uri properly

Solutions

Workaround in the encountering cases, not really know why the states under mutations became frozen,

Use concat instead of push to mutate array
Destruct the object and reassignment instead of Vue.set
Slicing array to remove the target item instead of arr.splice

Ex: [...slice(0, index), ...slice(index + 1)]

Use either CDN or manual uri to rewrite the ipfs:// scheme

Extract the constant CF_IPFS_BASE to constants.ts file
Add @Watch('metadata') on getter img and add function checkIPFSUri to parse image url before rendering

~Refactor to fetch tokens from contract directly by extending the ERC721Enumerable from EIP standard, which allows to read tokens by address from contract directly. This is also current Avalanche implementation~

~What modified~

~Removed old scanNewNfts action~
~Removed ercNftTokenIds in ERCNftModuleState because tokenIds will store in ERCNftToken instance~
~Modify canSupport flag: both EIP ERC721Metadata and ERC721Enumerable should be extended~
~Fetching owned tokens by combo of balanceOf and tokenOfOwnerByIndex directly from smart contract~

Tested Cases
2 ERC721 contracts deployed @Kopernikus
- 0xE54cEa4233C28b526e2f7f53D56C4E4B90F8e1Fd
- 0x1bF615d88B3cd4a15bdF79956d11d279Edff9AEb

New wallet access (no related info stored in localStorage)

Add two collectibles to check if minted ERC721 tokens display image and metadata properly
Remove 1 added contract from Add Collectible modal to check if the view update properly
Re-add the removed contract to check if the minted tokens display properly

Existing wallet access (reload the page and use the previous wallet to check recovering from localStorage works)

Reload page and re-login to check if previously added ERC721 tokens display properly
Remove 1 contract from Add Collectible modal to check if the view update properly
Add an ERC721 contract to check if the minted tokens display properly

Update
Fix issue TECH-835
Root cause
Currently getPastLogs only find the Transfer event about to address, e.g.,

address A sent token 1 to address B, only address B will collect the Transfer event

How fixes

invoking additional getPastLogs to find Transfer event about from address
combine both to events and from events and sort events by blockNumber
according to the parsed log, append tokenId if the address is in to field, and remove it if is in from field


pip install -e .

i got error
Obtaining file:///E:/FROM-FOLDER-D/github/nunchaku
Preparing metadata (setup.py) ... done
Installing collected packages: nunchaku
Attempting uninstall: nunchaku
Found existing installation: nunchaku 0.15.1
Uninstalling nunchaku-0.15.1:
Successfully uninstalled nunchaku-0.15.1
DEPRECATION: Legacy editable install of nunchaku==0.0.0b0 from file:///E:/FROM-FOLDER-D/github/nunchaku (setup.py develop) is deprecated. pip 25.0 will enforce this behaviour change. A possible replacement is to add a pyproject.toml or enable --use-pep517, and use setuptools >= 64. If the resulting installation is not behaving as expected, try using --config-settings editable_mode=compat. Please consult the setuptools documentation for more information. Discussion can be found at https://github.com/pypa/pip/issues/11457
Running setup.py develop for nunchaku
error: subprocess-exited-with-error
× python setup.py develop did not run successfully.
│ exit code: 1
╰─> [106 lines of output]
    C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\dist.py:337: InformationOnly: Normalizing '0.0.0beta0' to '0.0.0b0'
      self.metadata.version = self._normalize_version(self.metadata.version)
    running develop
    C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\command\develop.py:41: EasyInstallDeprecationWarning: easy_install command is deprecated.
    !!

            ********************************************************************************
            Please avoid running ``setup.py`` and ``easy_install``.
            Instead, use pypa/build, pypa/installer or other
            standards-based tools.

            See https://github.com/pypa/setuptools/issues/917 for details.
            ********************************************************************************

    !!
      easy_install.initialize_options(self)
    C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
    !!

            ********************************************************************************
            Please avoid running ``setup.py`` directly.
            Instead, use pypa/build, pypa/installer or other
            standards-based tools.

            See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
            ********************************************************************************

    !!
      self.initialize_options()
    running egg_info
    writing nunchaku.egg-info\PKG-INFO
    writing dependency_links to nunchaku.egg-info\dependency_links.txt
    writing top-level names to nunchaku.egg-info\top_level.txt
    reading manifest file 'nunchaku.egg-info\SOURCES.txt'
    adding license file 'LICENCE.txt'
    writing manifest file 'nunchaku.egg-info\SOURCES.txt'
    running build_ext
    C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py:380: UserWarning: Error checking compiler version for cl: [WinError 2] The system cannot find the file specified
      warnings.warn(f'Error checking compiler version for {compiler}: {error}')
    building 'nunchaku._C' extension
    Emitting ninja build file E:\FROM-FOLDER-D\github\nunchaku\build\temp.win-amd64-cpython-311\Release\build.ninja...
    Compiling objects...
    Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
    ninja: error: FindFirstFileExA(E:/FROM-FOLDER-D/github/nunchaku/src/kernels/flash_attn): The directory name is invalid.

    Traceback (most recent call last):
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py", line 2105, in _run_ninja_build
        subprocess.run(
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\subprocess.py", line 571, in run
        raise CalledProcessError(retcode, process.args,
    subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

    The above exception was the direct cause of the following exception:

    Traceback (most recent call last):
      File "<string>", line 2, in <module>
      File "<pip-setuptools-caller>", line 34, in <module>
      File "E:\FROM-FOLDER-D\github\nunchaku\setup.py", line 94, in <module>
        setuptools.setup(
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\__init__.py", line 117, in setup
        return distutils.core.setup(**attrs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\core.py", line 183, in setup
        return run_commands(dist)
               ^^^^^^^^^^^^^^^^^^
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\core.py", line 199, in run_commands
        dist.run_commands()
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\dist.py", line 954, in run_commands
        self.run_command(cmd)
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\dist.py", line 999, in run_command
        super().run_command(command)
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\dist.py", line 973, in run_command
        cmd_obj.run()
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\command\develop.py", line 35, in run
        self.install_for_development()
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\command\develop.py", line 112, in install_for_development
        self.run_command('build_ext')
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\cmd.py", line 316, in run_command
        self.distribution.run_command(command)
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\dist.py", line 999, in run_command
        super().run_command(command)
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\dist.py", line 973, in run_command
        cmd_obj.run()
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\command\build_ext.py", line 98, in run
        _build_ext.run(self)
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 359, in run
        self.build_extensions()
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py", line 866, in build_extensions
        build_ext.build_extensions(self)
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 476, in build_extensions
        self._build_extensions_serial()
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 502, in _build_extensions_serial
        self.build_extension(ext)
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\command\build_ext.py", line 263, in build_extension
        _build_ext.build_extension(self, ext)
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 557, in build_extension
        objects = self.compiler.compile(
                  ^^^^^^^^^^^^^^^^^^^^^^
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py", line 838, in win_wrap_ninja_compile
        _write_ninja_file_and_compile_objects(
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py", line 1785, in _write_ninja_file_and_compile_objects
        _run_ninja_build(
      File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py", line 2121, in _run_ninja_build
        raise RuntimeError(message) from e
    RuntimeError: Error compiling objects for extension
    [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.

Rolling back uninstall of nunchaku
Moving to c:\users\lior0\miniconda3\envs\nunchaku\lib\site-packages\nunchaku-0.15.1.dist-info
from C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages~unchaku-0.15.1.dist-info
Moving to c:\users\lior0\miniconda3\envs\nunchaku\lib\site-packages\nunchaku
from C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages~unchaku
error: subprocess-exited-with-error
× python setup.py develop did not run successfully.
│ exit code: 1
╰─> [106 lines of output]
C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\dist.py:337: InformationOnly: Normalizing '0.0.0beta0' to '0.0.0b0'
self.metadata.version = self._normalize_version(self.metadata.version)
running develop
C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\command\develop.py:41: EasyInstallDeprecationWarning: easy_install command is deprecated.
!!
        ********************************************************************************
        Please avoid running ``setup.py`` and ``easy_install``.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.

        See https://github.com/pypa/setuptools/issues/917 for details.
        ********************************************************************************

!!
  easy_install.initialize_options(self)
C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!

        ********************************************************************************
        Please avoid running ``setup.py`` directly.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.

        See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
        ********************************************************************************

!!
  self.initialize_options()
running egg_info
writing nunchaku.egg-info\PKG-INFO
writing dependency_links to nunchaku.egg-info\dependency_links.txt
writing top-level names to nunchaku.egg-info\top_level.txt
reading manifest file 'nunchaku.egg-info\SOURCES.txt'
adding license file 'LICENCE.txt'
writing manifest file 'nunchaku.egg-info\SOURCES.txt'
running build_ext
C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py:380: UserWarning: Error checking compiler version for cl: [WinError 2] The system cannot find the file specified
  warnings.warn(f'Error checking compiler version for {compiler}: {error}')
building 'nunchaku._C' extension
Emitting ninja build file E:\FROM-FOLDER-D\github\nunchaku\build\temp.win-amd64-cpython-311\Release\build.ninja...
Compiling objects...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
ninja: error: FindFirstFileExA(E:/FROM-FOLDER-D/github/nunchaku/src/kernels/flash_attn): The directory name is invalid.

Traceback (most recent call last):
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py", line 2105, in _run_ninja_build
    subprocess.run(
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\subprocess.py", line 571, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<string>", line 2, in <module>
  File "<pip-setuptools-caller>", line 34, in <module>
  File "E:\FROM-FOLDER-D\github\nunchaku\setup.py", line 94, in <module>
    setuptools.setup(
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\__init__.py", line 117, in setup
    return distutils.core.setup(**attrs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\core.py", line 183, in setup
    return run_commands(dist)
           ^^^^^^^^^^^^^^^^^^
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\core.py", line 199, in run_commands
    dist.run_commands()
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\dist.py", line 954, in run_commands
    self.run_command(cmd)
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\dist.py", line 999, in run_command
    super().run_command(command)
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\dist.py", line 973, in run_command
    cmd_obj.run()
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\command\develop.py", line 35, in run
    self.install_for_development()
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\command\develop.py", line 112, in install_for_development
    self.run_command('build_ext')
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\cmd.py", line 316, in run_command
    self.distribution.run_command(command)
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\dist.py", line 999, in run_command
    super().run_command(command)
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\dist.py", line 973, in run_command
    cmd_obj.run()
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\command\build_ext.py", line 98, in run
    _build_ext.run(self)
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 359, in run
    self.build_extensions()
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py", line 866, in build_extensions
    build_ext.build_extensions(self)
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 476, in build_extensions
    self._build_extensions_serial()
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 502, in _build_extensions_serial
    self.build_extension(ext)
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\command\build_ext.py", line 263, in build_extension
    _build_ext.build_extension(self, ext)
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 557, in build_extension
    objects = self.compiler.compile(
              ^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py", line 838, in win_wrap_ninja_compile
    _write_ninja_file_and_compile_objects(
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py", line 1785, in _write_ninja_file_and_compile_objects
    _run_ninja_build(
  File "C:\Users\LIOR0\miniconda3\envs\nunchaku\Lib\site-packages\torch\utils\cpp_extension.py", line 2121, in _run_ninja_build
    raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.

Hi, we are looking into the compatibility issue on Windows.
Before that, I would recommend trying nunchaku on WSL2 for Windows users. Guide (make sure to select wsl 2 instead of wsl 1).

Getting the same error :(

(nunchaku) C:\ai\nunchaku>pip install -e .
Looking in indexes: https://pypi.org/simple/, https://pypi.ngc.nvidia.com
Obtaining file:///C:/ai/nunchaku
  Preparing metadata (setup.py) ... done
Installing collected packages: nunchaku
  DEPRECATION: Legacy editable install of nunchaku==0.0.0b0 from file:///C:/ai/nunchaku (setup.py develop) is deprecated. pip 25.0 will enforce this behaviour change. A possible replacement is to add a pyproject.toml or enable --use-pep517, and use setuptools >= 64. If the resulting installation is not behaving as expected, try using --config-settings editable_mode=compat. Please consult the setuptools documentation for more information. Discussion can be found at https://github.com/pypa/pip/issues/11457
  Running setup.py develop for nunchaku
    error: subprocess-exited-with-error

    × python setup.py develop did not run successfully.
    │ exit code: 1
    ╰─> [115 lines of output]
        C:\Users\nitin\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\dist.py:294: InformationOnly: Normalizing '0.0.0beta0' to '0.0.0b0'
          self.metadata.version = self._normalize_version(self.metadata.version)
        running develop
        C:\Users\nitin\miniconda3\envs\nunchaku\Lib\site-packages\setuptools\command\develop.py:41: EasyInstallDeprecationWarning: easy_install command is deprecated.
        !!

                ********************************************************************************
                Please avoid running ``setup.py`` and ``easy_install``.
                Instead, use pypa/build, pypa/installer or other
                standards-based tools.

                See https://github.com/pypa/setuptools/issues/917 for details.

Hi, we are looking into the compatibility issue on Windows. Before that, I would recommend trying nunchaku on WSL2 for Windows users. Guide (make sure to select wsl 2 instead of wsl 1).

how to insttal with wsl?
wsl --install  -e .?

Hi, we are looking into the compatibility issue on Windows. Before that, I would recommend trying nunchaku on WSL2 for Windows users. Guide (make sure to select wsl 2 instead of wsl 1).

how to insttal with wsl? wsl --install -e .?

You need to first install WSL by using wsl --install in Windows. After that, you could use wsl to enter WSL, which is basically a virtual machine of Ubuntu.


Fail to run on first start, missing jobs.json

On first run, the app fails to start with an UnhandledPromiseRejection telling me that ./jobs.json doesn't exist.
Reproduction

git clone
npm install
npm run build
npm start

Expected
The app starts
Actual
╰─ npm start

><EMAIL_ADDRESS>start /Users/Martin/Workspace/applican
> node lib/index.js

(node:29284) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/Users/Martin/Workspace/applican/jobs.json'
(Use `node --trace-warnings ...` to show where the warning was created)
(node:29284) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:29284) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Adding a jobs.json file containing an empty object prints the title, then fails with Cannot read property 'forEach' of undefined:
╰─ npm start

><EMAIL_ADDRESS>start /Users/Martin/Workspace/applican
> node lib/index.js
                      ╭──────────────────────────────────────────────────────────────────────────────────╮
                      │        __      __       ___                ___            __  _                  │
                      │       / /___  / /_     /   |  ____  ____  / (_)________ _/ /_(_)___  ____  _____ │
                      │  __  / / __ \/ __ \   / /| | / __ \/ __ \/ / / ___/ __ `/ __/ / __ \/ __ \/ ___/ │
                      │ / /_/ / /_/ / /_/ /  / ___ |/ /_/ / /_/ / / / /__/ /_/ / /_/ / /_/ / / / (__  )  │
                      │ \____/\____/_.___/  /_/  |_/ .___/ .___/_/_/\___/\__,_/\__/_/\____/_/ /_/____/   │
                      │                           /_/   /_/                                              │
                      ╰──────────────────────────────────────────────────────────────────────────────────╯
(node:29399) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'forEach' of undefined
    at /Users/Martin/Workspace/applican/lib/util.js:80:18
    at new Promise (<anonymous>)
    at Object.exports.createTable (/Users/Martin/Workspace/applican/lib/util.js:75:12)
    at /Users/Martin/Workspace/applican/lib/util.js:108:50
    at step (/Users/Martin/Workspace/applican/lib/util.js:33:23)
    at Object.next (/Users/Martin/Workspace/applican/lib/util.js:14:53)
    at /Users/Martin/Workspace/applican/lib/util.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/Users/Martin/Workspace/applican/lib/util.js:4:12)
    at /Users/Martin/Workspace/applican/lib/util.js:102:60
(Use `node --trace-warnings ...` to show where the warning was created)
(node:29399) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:29399) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I forgot that I had an uncommitted template file named jobs.json on my local machine. I'll fix this today. Standby for fix.
Thanks @MartinRosenberg 👍

Hey @MartinRosenberg, please try the following steps:

Either just start over by re-cloning / re-forking this repo in a new directory OR copy just the jobs.json that exists in this repo now.
npm install
npm run build
npm start

This should get you to the main screen of Applican now.
Please let me know if you have any trouble. I'm closing this issue for now, but can reopen it if it's not working for you.
Thanks again!


docs(devs-infra): correct a few things in documentation

Summary

Correct ts-jest description to clear up confusion
Correct a small mistake in README

Test plan

Green CI
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
N.A.

Pull Request Test Coverage Report for Build 694848412

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

Totals

Change from base Build 692215961:
0.0%

Covered Lines:
964

Relevant Lines:
994

💛  - Coveralls

@kulshekhar would you please also adjust project description in project settings to A Jest transformer with source map support that lets you use Jest to test projects written in TypeScript.?

Done!


How can we receive messages

Hey, Netfile can you please help me ?
I'm able to send all types of messages but i cannot receive messages please help.

Hi,
You have to create a webkook: https://developers.facebook.com/docs/whatsapp/cloud-api/guides/set-up-webhooks

Hi,
You have to create a webkook: https://developers.facebook.com/docs/whatsapp/cloud-api/guides/set-up-webhooks

I have already created a webhook.
but unable to understand that how can i receive and save received messages into database in php.


Allow to keep default values in serialized JSON

We use Protobuf to define API endpoints and spotted surprising behavior - items with default values are absent in the serialized JSON. It is uncommon for PHP REST APIs to have parameters disappearing from response when returned value is default one. This PR solves this problem without braking default behavior.
I would like to hear your feedback on proposed solution. Thanks.

Could you send this PR to protobuf’s main repo?
On Tue, Mar 17, 2020 at 6:20 AM Alexander Shiltcev<EMAIL_ADDRESS>wrote:

We use Protobuf to define API endpoints and spotted surprising behavior -
items with default values are absent in the serialized JSON. It is uncommon
for PHP REST APIs to have parameters disappearing from response when
returned value is default one. This PR solves this problem without braking
default behavior.
I would like to hear your feedback on proposed solution. Thanks.
You can view, comment on, or merge this pull request online at:
https://github.com/protocolbuffers/protobuf-php/pull/6
Commit Summary

Allow to keep default values in serialized JSON

File Changes

M README.md
https://github.com/protocolbuffers/protobuf-php/pull/6/files#diff-04c6e90faac2675aa89e2176d2eec7d8
(7)
M src/Google/Protobuf/Internal/GPBWire.php
https://github.com/protocolbuffers/protobuf-php/pull/6/files#diff-6d4f2e77838aaccbe4cc7a7a1370ad87
(10)
M src/Google/Protobuf/Internal/Message.php
https://github.com/protocolbuffers/protobuf-php/pull/6/files#diff-e2ee323e57d24611a2b3e21edf4fd598
(116)

Patch Links:

https://github.com/protocolbuffers/protobuf-php/pull/6.patch
https://github.com/protocolbuffers/protobuf-php/pull/6.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/protocolbuffers/protobuf-php/pull/6, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHUPZO3YQURT3ONSAGGHP3RH52LVANCNFSM4LNNOPLQ
.

:closed_book: MEV SW OD Build #27839 result: FAILURE

Manifest Name
Build Status
Jenkins Link
Artifacts
Unsuccessful Stages
Description

mev-ts-trunk
FAILURE
59604
 Artifacts
IPU SDK Build

mev-trunk
FAILURE
56680
 Artifacts
Simics_C0_ACC

mev-release
NOT AFFECTED

mev-ts-release
NOT AFFECTED

mev-ts-release-1.6.1
NOT AFFECTED

mev-ts-release-bitbake
NOT AFFECTED

mev-ts-release-external
NOT AFFECTED

mev-ts-trunk-bitbake
NOT AFFECTED

mev-ts-trunk-bitbake-c1
NOT AFFECTED

mev-ts-trunk-external
NOT AFFECTED

mev-upstream-idpf
NOT AFFECTED

:closed_book: MEV SW OD Build #27894 result: FAILURE

Manifest Name
Build Status
Jenkins Link
Artifacts
Unsuccessful Stages
Description

mev-trunk
FAILURE
56702
 Artifacts
IPU_IMC_6_6_4

mev-ts-trunk
SUCCESS
59633
 Artifacts

mev-release
NOT AFFECTED

mev-ts-release
NOT AFFECTED

mev-ts-release-1.6.1
NOT AFFECTED

mev-ts-release-bitbake
NOT AFFECTED

mev-ts-release-external
NOT AFFECTED

mev-ts-trunk-bitbake
NOT AFFECTED

mev-ts-trunk-bitbake-c1
NOT AFFECTED

mev-ts-trunk-external
NOT AFFECTED

mev-upstream-idpf
NOT AFFECTED


add github actions to dependabot config

Dependabot is pretty reasonable if it notes your using v1.1.1 and it will update to v1.2.0
I haven't tried commit sha but technically that is also mutable since you can use force push to remove that commit sha.


ISPN-11845 SingleFileStore location validation should be skipped when global state is disabled

https://issues.redhat.com/browse/ISPN-11845
Please cherry-pick into 10.1.x.

Makes sense.  I'll update the PR.

There are lots of related failures due to the change of behaviour.

Closing in favour of https://github.com/infinispan/infinispan/pull/8361


Social preview for topic pages

For example this is how the US Child Tax Credit topic page shows up on Twitter

https://manifold.markets/browse?topic=us-child-tax-credit
https://twitter.com/MaxGhenis/status/1749489952272855074

good idea! i'll keep this in mind for the topic page redesign


4.pub-sub Node Subscriber doesn't receive request body

Expected Behavior
When running the pubsub sample in Kubernetes and manufacturing messages with the react front-end, the node subscriber receives messages, but no message body.
Actual Behavior
The node subscriber prints the topic name with an empty body:
A: {}

Steps to Reproduce the Problem
Run the sample in kubernetes and log the node-subscriber's output.
Culprit
The source of the problem seems to be the json type that the express bodyParser is using: application/*+json. When changed to application/json, the sample works as expected. Apparently, however, this causes issues in standalone mode: #79, which @youngbupark noted in #85.

@abhirockzz FYI

@ryanvolum @abhirockzz this issue must be fixed. I tested in standalone and k8s envs.

@youngbupark did you test it with the react front-end? I wonder if maybe the issue is the way that it's posting messages.
I'm definitely not seeing the content of topics of type A. I'll check again to be sure.

@ryanvolum yeah I tested with react front-end.

@ryanvolum please look at this conversation. - https://gitter.im/Dapr/samples?at=5db71ad714d55a378590324e
It was working in minikube.

Upon updating to the latest Dapr version, this no longer appears to be an issue.


Maxsteps not update after addtags on formless feature

Hello,
We tried formless feature and we noticed that the maxsteps variable is not updated after addtags method. So if we start the conversation with 1 tag the submit callback function is fired after we add a tag on step callback and the conversion stop.
We have found a trick, we set the maxsteps to 1000 just after the startconversation but it's not very clean.
Regards

@MediacraftFR thanks for the report, i've pushed a fix to master


[MRG] Global threshold for feature computation

This PR allows the selection of a globally optimum threshold for object detection in input images, instead of computing a different threshold for each image. This is enabled by the global illumination correction from a previous PR.

@starcalibre I'm currently struggling with a design choice. When do we treat images as single-channel, multi-channel, or either?
If you look at features.intensity_object_features, the input is assumed to be single-channel, but upstream functions (default_feature_map, or myores.feature_vector_from_rgb) are assumed to take 3-channel input. Now that I'm fiddling with the threshold, this difference is getting a bit frustrating.
At some point, we might want to allow 3D input, or input with more than three channels, or input with just one channel, so I'm wary of hardcoding 2D or 3 channels everywhere...
Do you have any ideas for the best tack to take here?

Is the difficulty with features that depend upon information from more than channel? These types of features should be treated as being screen specific, so these should either be specified before feature extraction or generated conditionally depending on presence of particular channels.. however that's something that's much easier said than done, and would go against the goal of creating something that's easily applicable to any screen..
Couldn't default_feature_map generalise to any number of channels? It's just a concatenation of the feature vectors produced by features.intensity_object_features?

Hey,
No, features that use more than one channel are not the problem and are not currently used, although I was actually thinking about doing something like a correlation coefficient for every pair of channels. (thoughts?)
But the difficulty is that every feature vector we use (myores, cellomics) uses "intensity_object_features", which is only aware of a single channel. So I was finding myself adding manual threshold logic to both of those functions separately, because each channel has its own threshold. Instead, perhaps I want to push the multi-channel logic all the way down to "intensity_object_features", so that it can take a multi-channel threshold and then operate on the objects on each channel.
Ugh. I'm quite muddled in my thinking of this and I think it shows. =P Are you going in tomorrow?

Coverage increased (+0.58%) to 71.44% when pulling 00ee3329cfc9e007bcc30a5ab4ff9a8bdee705b8 on jni:global-threshold into 078c801e9c7bb6d2b6f211f75bb74e70e19f6a7a on microscopium:master.

@starcalibre this is ready to review now!

@jni Thanks for adding the comment! This looks good to me.. did you want to add anything else before I merge it?

@starcalibre ACTUALLY, I was playing around with a different lot of images yesterday and found that threshold_isodata gave terrible results! I might go back to Otsu!

Fiddlesticks..! Could you post a couple of examples here?

Cervically! =P

and

Shocking, isn't it????
(For many examples, isodata gave similar results to Otsu. But I didn't see any where Otsu failed dramatically and isodata didn't. I just kinda liked isodata because it seemed intuitive while making fewer assumptions about the data distribution. Turns out Otsu's nice theoretical grounding is nice. =P)

@starcalibre ok, now this is ready. Exciting! =)

Coverage increased (+0.7%) to 71.56% when pulling cb493b6985d27f33d8944299d3c989e1df18b6cb on jni:global-threshold into 078c801e9c7bb6d2b6f211f75bb74e70e19f6a7a on microscopium:master.


[Starfinder Simple] Addition of operative Disciple Mysticism skill for Trick Attack skill.

Addition of missing debilitating tricks from Trick attack macro.
Changes / Comments
Starfinder Simple sheet additions for new Disciple trick attack that came out in a new book.  It also adds the missing debilitating tricks available for the Trick attack macro that exists for operative trick attacks and the appropriate conditions to apply.  No options were removed from the Trick attack option list and no conditions were removed from the conditions list so no current sheet players should be affected.
If the conditions are not immediately present players can turn off and turn on the trick attack macro selection to get the new debilitating trick macro to apply to attacks.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[X] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[X] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


Request

Please consider my API to add in your list
https://github.com/vedicscriptures/bhagavad-gita-api

read this: https://github.com/public-apis/public-apis/blob/b7d950cee2f39d664d9aff781cbb9988dc2a37ac/.github/CONTRIBUTING.md
and then submit a peer review

read this: https://github.com/public-apis/public-apis/blob/b7d950cee2f39d664d9aff781cbb9988dc2a37ac/.github/CONTRIBUTING.md
and then submit a peer review


Editor's viewport doesn't redraw on Node2D deletion leaving icons, helpers, the selection rectangle,...

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Godot 3.0 master https://github.com/godotengine/godot/commit/1f4685375f2d2e36a2e19e67ac9f614b8c99ea28
Issue description:

Steps to reproduce:

Add a Node2D
Select it
(optional) toggle the lock or the grouping modes
Delete it
Icons, helpers, selection rectangle,... are still in the editor viewport

Link to minimal example project:

As @YeldhamDev mentionned, the problem il also here for lock icons and helpers.
The viewport probably need are redraw on delete.

@groud (or anyone else) check SceneTreeDock and, worst case, just force redraw to CanvasItemEditorPlugin from there. I may have added similar code for other circumsatances there.

Well I wanted to finish reworking the gui inputs in the canvas item editor but it might take a while. I'll probably fix this sooner to avoid other issues to be opened.


ANMS_EXP_DAP_005 (ARIs) Sorting and Information

It was noted when sort is executed on a column without data is selected, the table was still sorted.  It is not clear what column is used.
It was also noted the ARIs panel lacks an 'information' icon informing the user of the purpose of the panel.

test step instruction


Avoid using maps for labels to reduce memory

Codecov Report

Merging #416 (f814d9b) into main (1607714) will decrease coverage by 0.17%.
The diff coverage is 77.77%.

@@            Coverage Diff             @@
##             main     #416      +/-   ##
==========================================
- Coverage   94.52%   94.35%   -0.18%
==========================================
  Files          75       75
  Lines        6471     6514      +43
==========================================
+ Hits         6117     6146      +29
- Misses        269      279      +10
- Partials       85       89       +4

Impacted Files
Coverage Δ

internal/promapi/range_normalize.go
88.42% <75.00%> (-11.58%)
:arrow_down:

internal/checks/promql_series.go
98.90% <100.00%> (ø)

internal/promapi/range.go
94.73% <100.00%> (+0.02%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


StuxRip doesn't recognize 64bit Avisynth+ installation

Well,
title says everything. After indexing a movie StuxRip keeps on telling me that Avisynth+ is not installed, even after selecting the dll file manually.
OS: Win10 Education x64
StuxRip: <IP_ADDRESS> beta
Avisynth+: MT-r1825
Best regards

Experienced the same problems are resolved:
1, uninstall Avisynth
2, install Avisynth+
3, and staxrip can automatically recognize.

By now I found out that there is a much easier way. As I said, I have installed the MT version of Avisynth+. So all I had to do is to change the version numer in StuxRip into "r1825 MT x64". It is exactly the same with StuxRip <IP_ADDRESS>pre release.
Now, the issue is solved by workaround :-).
HAND

Yes it detects different versions and says that you can use it by editing the date with F12.

Can i download Avisynth+ manuel without steup ?


Unable to intercept deployment with taints

Bug Description
I got a deployment with taints
      tolerations:
      - key: reserved-staging
        operator: Equal
        value: "true"
        effect: NoSchedule
      - key: reserved-staging
        operator: Equal
        value: "true"
        effect: NoExecute

And I think because of these taints the intercept is failing, because I got this on event manager:
Name: mirrord-agent-e5o0euru5e-67mmr.177076c2c38a37ef
Namespace: staging
Labels: <none>
Annotations: <none>
API Version: v1
Count: 1
Event Time: <nil>
First Timestamp: 2023-07-10T09:13:59Z
Involved Object:
  Kind: Pod
  Name: mirrord-agent-e5o0euru5e-67mmr
  Namespace: staging
Kind: Event
Last Timestamp: 2023-07-10T09:13:59Z
Message: Marking for deletion Pod staging/mirrord-agent-e5o0euru5e-67mm
Metadata:
  Creation Timestamp: 2023-07-10T09:13:59Z
  Managed Fields:
    API Version: v1
    Fields Type: FieldsV1
    fieldsV1:
      f:count:
      f:firstTimestamp:
      f:involvedObject:
      f:lastTimestamp:
      f:message:
      f:reason:
      f:source:
        f:component:
      f:type:
    Manager: kube-controller-manager
    Operation: Update
    Time: 2023-07-10T09:13:59Z
  Resource Version: 4075336
  UID: 0ebca40e-9b70-4936-9adb-243d360de9d3
Reason: TaintManagerEviction

It seems the taint manager kill the intercept pod and since it is a pod nothing its started on its place.
Steps to Reproduce

Deploy a deployment with taints
Try to intercept it

Backtrace
When targeting multi-pod deployments, mirrord impersonates the first pod in the deployment.
 Support for multi-pod impersonation requires the mirrord operator, which is part of mirrord for Teams.
 To try it out, join the waitlist with `mirrord waitlist <email address>`, or at this link: https://metalbear.co/#waitlist-form
⠦ mirrord cli starting...
  x exec
    x preparing to launch process
    ✓ layer extracted
    ✓ no operator detected
    ✓ agent pod created
    x waiting for pod to be ready...
Error:   × Agent wasn't ready in time
  help:
            Please check the status of the agent pod, using `kubectl get pods` in the relevant namespace.
            Make sure it is able to fetch the agent image, it didn't fail due to lack of resources, etc.

Relevant Logs
No response
Your operating system and version
Fedora 38
Local process
Tried several programs, always same result
Local process version
No response
Additional Info
No response

Thanks for reporting this. This will be released in 3.50.2 :)


feature: Typescript Kernel

As the title suggests. A TypeScript kernel using ts-lab would be an amazing addition.

I would love to try and implement this myself but am not sure if this is realistic with my level of nix experience. Let me know if you think this is possible?

Hello! Creating a kernel is not very difficult -- it consists on packaging that gives the kernel executable (or finding it on Nixpkgs), and writing a kernel file. Each one of the subfolder in the kernels folder is an example of package. If you want to try, I recommend choosing one of the smallest definitions, and to try replication it for ts-lab.

@nazzacode
There is a PR #259 to add a Typescript kernel. I believe it works. Give it a try if you have a chance.


400 error when I try to store base64 string

I want to store base64 string in solid pod. But when I try to execute I get the following error.
As I understood it has to do with the length of the string.  Or is it still a problem?

It's wasn't a problem, sorry)


Integration tests

Pull Request Test Coverage Report for Build 327778902

0 of 4 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 80.378%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/api/server/server.go
0
4
0.0%

Totals

Change from base Build 327349000:
-0.3%

Covered Lines:
893

Relevant Lines:
1111

💛  - Coveralls


Change maximum media request size

We have some (exactly 6 actually) audio_events that are longer than the maximum limit for media downloads (media maximum = 120s, longest audio event = 161s). When these events are shown in the library, they can't be shown.
Proposed: change the maximum allowed media duration to 180s.

e.g.
GET /audio_recordings/138285/media.png?audio_event_id=10586&end_offset=228&start_offset=98
{
"audio_event_id"=>"10586",
"end_offset"=>"228",
"start_offset"=>"98",
"format"=>"png",
"controller"=>"media",
"action"=>"show",
 "audio_recording_id"=>"138285"
}

A BawAudioTools::Exceptions::SegmentRequestTooLong occurred in media#show:

  Requested duration 130.0 (98.0 to 228.0) is greater than maximum (120.0).
  lib/modules/api/media_metadata.rb:182:in `check_duration_defaults'

Old:

cached_audio_defaults.max_duration_seconds = 300.0 (5 minuntes)
cached_spectrogram_defaults.max_duration_seconds =  120.0 (2 minuntes)

New:

cached_audio_defaults.max_duration_seconds = 300.0 (5 minuntes)
cached_spectrogram_defaults.max_duration_seconds =  180 (3 minuntes)


Johannsen-Psaltis metric fits

This PR is draft as this is initially a WIP.
A couple of issues at the moment:

JPLineProfile seems to igore the line energy parameter.

The fitting runs into an automatic differentiation problem (but this could simply be that one of my packages is out of date).

The last commit should perhaps be on a separate branch but I didn't want to mess things up at the last minute.

The Johannsen-Psaltis disc fits are now included. Other modifications to the presentation included.


flutter build web -> The compiler crashed when compiling this element

When I run flutter web in browser all works fine.
But when running the flutter build web command it throws this error below.
@override
  Stream<LoginState> mapEventToState(LoginEvent event) async* {
    if (event is GetLoginEvent) {
      yield LoginLoadingState();
      final failureOrModel = getLoginUseCase(event.aid);
      await for (var value in failureOrModel) {
        yield* _eitherLoadedOrErrorState(value);
      }
    }
  }

Target dart2js failed: Exception: lib/features/login/presentation/bloc/login_bloc.dart:25:22:
Internal Error: The compiler crashed when compiling this element.
  Stream<LoginState> mapEventToState(LoginEvent event) async* {
                     ^

The compiler is broken.

When compiling the above element, the compiler crashed. It is not
possible to tell if this is caused by a problem in your program or
not. Regardless, the compiler should not crash.

The Dart team would greatly appreciate if you would take a moment to
report this problem at http://dartbug.com/new.

Please include the following information:

* the name and version of your operating system:(Mac OS),

* the Dart SDK build number (2.9.0-edge.2b917f5b6a0e1524516f214c6d0df49f4abfd378), and

* the entire message you see here (including the full stack trace
  below as well as the source location above).

The compiler crashed: NoSuchMethodError: The getter 'classNode' was called on null.

Hi @lukehassel
Can you please provide your flutter doctor -v,
your flutter build web --verbose,
your pubspec.yaml
and a minimal complete reproducible code sample.
Thank you

Without additional information we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


In field button

Description
Graduating the pre-release snapshot release of the in-field button.
Tokens added (19):

in-field-button-edge-to-disclosure-icon-stacked-extra-large
in-field-button-edge-to-disclosure-icon-stacked-large
in-field-button-edge-to-disclosure-icon-stacked-medium
in-field-button-edge-to-disclosure-icon-stacked-small
in-field-button-edge-to-fill
in-field-button-fill-stacked-inner-border-rounding
in-field-button-inner-edge-to-disclosure-icon-stacked-extra-large
in-field-button-inner-edge-to-disclosure-icon-stacked-large
in-field-button-inner-edge-to-disclosure-icon-stacked-medium
in-field-button-inner-edge-to-disclosure-icon-stacked-small
in-field-button-outer-edge-to-disclosure-icon-stacked-extra-large
in-field-button-outer-edge-to-disclosure-icon-stacked-large
in-field-button-outer-edge-to-disclosure-icon-stacked-medium
in-field-button-outer-edge-to-disclosure-icon-stacked-small
in-field-button-stacked-inner-edge-to-fill
in-field-button-width-stacked-extra-large
in-field-button-width-stacked-large
in-field-button-width-stacked-medium
in-field-button-width-stacked-small

Related Issue
DNA-1288
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Run report for 03289852
Total time: 46.4s | Comparison time: 44.3s | Estimated loss: 2.1s (4.4% slower)

Action
Time
Status
Info

🟩
SetupNodeTool(18.13.0)
3.7s
Passed

🟩
InstallNodeDeps(18.13.0)
17.3s
Passed

🟩
SyncNodeProject(tokens)
0.6ms
Passed

🟩
RunTarget(tokens:build)
20.9s
Passed

🟩
SyncWorkspace
0ms
Passed

🟩
RunTarget(tokens:buildManifest)
186.2ms
Passed

🟩
RunTarget(tokens:test)
2.1s
Passed

🟩
RunTarget(tokens:generateDiffResult)
4.3s
Passed

Touched files
.changeset/swift-gifts-dress.md
package.json
packages/tokens/src/layout-component.json
packages/tokens/tasks/diff.js
packages/tokens/tasks/lib/augmentExpressTokens.js
packages/tokens/test/drover.test.js
pnpm-lock.yaml


Parallel support for Once/Before/After/Lastly

Hi,
We've been using Canopy to build our E2E tests for a couple of months now, and really like the ease with which we can create them.
I'm trying to convert some tests that ran in sequence into something that can run in parallel. I'm going with instanced tests, so I've added instances to various contexts, open prunner etc. Unfortunately, it seems to be missing support for the context setup and teardown steps. Is this the case or am I missing something?
Thanks very much,
Mike

I've found the answer to my own question here - http://lefthandedgoat.github.io/canopy/upgrade1to2.html - no it doesn't, I'll try using nunit like it suggests!
Cheers,
Mike


update only packages with changes

what

update only packages with changes
update all packages if apk, tasks or codefresh folders updated
upgrade of variant

why

avoid rebuilding all packages if only some was updated

Fix merge conflict

rename codefresh.yaml to something more descriptive like docker.yaml or what it does

If timestamps are not working for dependency tracking,  consider this approach to track file contents via hashes.

Closing this in favor of a using different Makefile centric strategy:

Use a codefresh shared volume to persist state
create a target in each Makefile like

$(PACKAGE_NAME)-$(PACKAGE_VERSION)-r$(PACkAGE_RELEASE).apk: apk/prepare apk/checksum apk/build apk/clean`

apk: $(PACKAGE_NAME)-$(PACKAGE_VERSION)-r$(PACkAGE_RELEASE).apk

If we do this, then we don't need to muck around with the greping and awking to figure out what changed. We only build packages which don't yet exist. This is all derived automatically by make, because make will only call  $(PACKAGE_NAME)-$(PACKAGE_VERSION)-r$(PACkAGE_RELEASE).apk if the file does not exist.


Add link to Idea 1 micro-tasks

I've added the link to the corresponding issue. I created the issue in GrimoireLab project as the idea is related to it, but I can move it to another project if you think it would be more appropriate.

Awesome. This is great. Thank you.


All issues seem to be missing

Avoid duplicates

[X] I have searched the issues tracker for a bug report similar to mine, in vain

Steps to reproduce
I distinctly remember reporting issues in the last few days, and upon checking on their status, they all seem to be gone :(
Debug link
Doesn't apply
Screenshots
No response
Additional information
No response

Yeah, seems like the backtrack on the "If you don't pay you don't actually deserve to have issues" idiocy only applies as long as the team reads the bug report and not meant for "community engagement" aka "this app isn't flawless and you need workarounds".

I'm not really sure what that means. It sounds like it's referencing some drama, but without context I'm not even sure if it's pro or con 🤷

Right, sorry. It's sadly drama that went down a few months ago.
The dev team seemingly went through some fundamental shifts that caused multiple old and important members to leave. After which the "new" team disabled all Issues on this repo claiming "It's for the users' security as they kept sharing personal info." and made it only accessible to donating members.
A few weeks later they stepped back on this decision and opened up Issues again, but as you can see they systematically purge them. Either so no one can see how many problems the app still has or to try and push people to donate to SEE potential fixes mentioned by other users.
It's a very unfortunate situation when this app has introduced so many improvements Franz's base code which has actually just recently started up development again with some big updates. 👍

Right, sorry. It's sadly drama that went down a few months ago.
The dev team seemingly went through some fundamental shifts that caused multiple old and important members to leave. After which the "new" team disabled all Issues on this repo claiming "It's for the users' security as they kept sharing personal info." and made it only accessible to donating members.
A few weeks later they stepped back on this decision and opened up Issues again, but as you can see they systematically purge them. Either so no one can see how many problems the app still has or to try and push people to donate to SEE potential fixes mentioned by other users.
It's a very unfortunate situation when this app has introduced so many improvements Franz's base code which has actually just recently started up development again with some big updates. 👍

It seems that the portable version at least is instabile I would not be surprised that minorannoyances have been introduced to promote subscription to issue tracker.


Fix poll interval in abacus-client

Signed-off-by: Stoyan Gradev<EMAIL_ADDRESS>

Coverage decreased (-0.02%) to 90.897% when pulling fcb1c87143ebb9972a09eca7ebe5a29de4e035c6 on SAP:poll-interval into efd23532d3d2cc435fa64fd5c5a9c59e993d1760 on cloudfoundry-incubator:master.


Add setup.py

Hi @aluttik, this is a setup.py file to make it a little easier for other people to install your library.

Thanks @PatOConnor43, much appreciated 👍


Leak

Hey idk why you did that but it will be taken down

seethe + cope

?

i like the decompiler notices

Thx, I was too  lazy to deobf and decompile myself as I'm working on other projects atm and someone asked me for SRC so they could skid

That's why some of it is still obf xd

You exposed yourself that you dont have a professional knowledge because the code isnt obfuscated btw

but if smth is unobfuscated you also dont have any agreement to upload the code and to put another license on it

That's why some of it is still obf xd

idk why you do that but many people do that because they get a feeling of a wanna be superiority. Idk why do you think there is a obfuscation xd

What license was used in the client
Since when did I say I was a "professional"?

Also if u read the license u would see that it allows anyone to do anything with it since idrc, also I did it because I was really bored

Also yes it was retarded of me to say its obf because I didn't even check all of SRC and assumed it was still semi obf, but after checking its not, thanks for making me to use my brain!

btw we work currently on a dmca claim i just wanted to inform you about our steps
Its licensed after german laws we have the copyright on our code


Remove references to CockroachDB

Summary

We need to remove references to CockroachDB from the documentation.
Why do we need this ?

In https://github.com/TheThingsNetwork/lorawan-stack/pull/4813 we removed CockroachDB from the development tooling of The Things Stack. With that change, we no longer test The Things Stack on CockroachDB, and even though it will probably still work fine, I think it's better to use the same database (PostgreSQL) everywhere.
How do you propose to document this?

Take a look at the current docker-compose file in lorawan-stack and make the necessary changes to the examples in this repository.
Test the examples to make sure they still work.
Remove other references to CockroachDB.

@nejraselimovic im swamped with conference work so assigning you here. if you need any help ping me.


Fix various error handling issues in DRBG code [1.1.1]

Back-port of #7517 to 1.1.1

Merged to 1.1.1 as c40c1ef.  Thanks!


Prevent double initalization when using multiple app domains

Mstest, IIS might use multiple AppDomains which trigger multiple loads
of the library and thus multiple static constructor executions. This
means that v8 was initialized multiple times.
Since v8 lives independently of AppDomains this would lead to errors when
creating a second AppDomain.

I think you are right.  Not sure what I was thinking.

Oh, now I know (though I have already merged - please address the problem): if two threads enter your code simultaneously then one will skip initialisation of v8.  However it may continue and use v8 before the other thread has finished its initialisation calls.  Any threads need to be held up until initialisation has completed.

No, not urgent.  Thanks.
On Tue, Aug 28, 2018 at 7:24 PM, Erik Schilling<EMAIL_ADDRESS>wrote:

Ah... Indeed... I did not think about that... Unfortunately I won't be
able to submit a PR until Thursday...
But since the problem is not worse than before I guess it is not that
urgent? Otherwise you might want to revert it.
Sorry!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/JavascriptNet/Javascript.Net/pull/53#issuecomment-416513997,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACqgcZJ-vQlkRWsG5Q4nkP6DRupk7JfVks5uVQxDgaJpZM4WNcpv
.


Unhandled exception when depth size is not correctly set

When the depth is not correctly set and we try to access a linked_item the gem raise a unhandled exception.
undefined method '[]' for nil:NilClass

that occurs in lib/delivery/resolvers/linked_item_resolver.rb at
def resolve_item(codename)
  item = @modular_content.values.find { |i| i['system']['codename'] == codename }
  ContentItem.new JSON.parse(JSON.generate(item)), @content_link_url_resolver, @inline_content_item_resolver, self
end

The codename is not inside the modular_content so the find method return nil
It's easily fix by increasing the depth size of the request but that would be better to raise a custom exception.
Test environment

Ruby 2.7
kontent-delivery-sdk-ruby 2.0.22

Hey @BenjaminDigeon!
Thanks for the bug report 👍 I'm currently having some permission issue with the repo (embarrassing) so I couldn't push the changes here, but I did just package up 2.0.24 of the gem and push it live. Now, if the depth is insufficient (e.g. 0), calling get_links('my_element') will return an empty array.


Getting Exception: StackExchange.Redis.RedisConnectionException

I am getting this error - Exception: StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(S); to create a disconnected multiplexer, disable AbortOnConnectFail. SocketFailure on PING.
Please suggest me what I am doing wrong.
Thanks,
Viren

I pushed the change. Can you check please?

Same error again..
Exception: StackExchange.Redis.RedisConnectionException: It was not possible to connect to the redis server(S); to create a disconnected multiplexer, disable AbortOnConnectFail. SocketFailure on PING

Did you pull the latest from git? I just commented the RedisStore injection. Can you check in Program.cs whether InMemoryStore is being used or not?

Yes, I have taken latest Program.cs
`var builder = new ContainerBuilder();
        #region Redis

        //RedisStoreOptions redisOptions = new RedisStoreOptions()
        //{
        //    Configuration = "localhost"
        //};

        //builder.Register(c => new RedisStore(redisOptions))
        //   .As<RedisStore>()
        //   .SingleInstance();

        //builder.Register(c => new CachingBotDataStore(c.Resolve<RedisStore>(),
        //                                              CachingBotDataStoreConsistencyPolicy.ETagBasedConsistency))
        //    .As<IBotDataStore<BotData>>()
        //    .AsSelf()
        //    .InstancePerLifetimeScope();
        #endregion

        #region InMemory
        builder.RegisterType<InMemoryDataStore>()
            .AsSelf()
            .SingleInstance();

        builder.Register(c => new CachingBotDataStore(c.Resolve<InMemoryDataStore>(),
                                                      CachingBotDataStoreConsistencyPolicy.ETagBasedConsistency))
            .As<IBotDataStore<BotData>>()
            .AsSelf()
            .InstancePerLifetimeScope();

        #endregion

        List<string> managerList = GetManagerList();

        builder.Register(c => new ManagerScorable(c.Resolve<IBotToUser>(), managerList))
            .Keyed<ManagerScorable>(FiberModule.Key_DoNotSerialize)
            .As<IScorable<IActivity, double>>()
            .InstancePerLifetimeScope();

        builder.Update(Conversation.Container);`

I had commented RedisStore and used InMemoryStore. In no other place is Redis used. It may be due to old dll's. Can you try clearing bin and obj folder and build again.

Thank you so much, now it's working fine.  I have few more doubts, will share details in next message.
Thanks,
Viren

Great. The reason was that since the bot will not be talking to Microsoft Bot Connector in any way, we would need to store bot's context somewhere our-self. I had used locally running instance of Redis. Now I have commented out RedisStore and used InMemoryStore. To use RedisStore uncomment the 'region' in Program.cs and comment InMemory 'region'.


Look into new command pod install

When igniting a new app, if the user chooses to install dependencies we run the following:
   // #region Install CocoaPods
    // install pods
    if (shouldFreshInstallDeps) {
      startSpinner("Baking CocoaPods")
      await spawnProgress(`npx<EMAIL_ADDRESS>{
        onProgress: log,
      })
      stopSpinner("Baking CocoaPods", "☕")
    }
    // #endregion

Is it possible this action is then duplicated via our ./boilerplate/bin/postInstall script during yarn install? This script also goes through the necessary MacOS and ios folder checks to then run pod install.

Or maybe let's just run npx pod-install from the postInstall script and remove our home rolled version?

Interesting in my testing, if the Podfile.lock versions were mismatched, (see https://github.com/infinitered/ignite/pull/2278), our typical cd ios && pod install in ./boilerplate/bin/postInstall does fail:
./bin/postInstall failed on command:
  if [ -d "ios" ] && [ -z "$IGNITE_SKIP_POD_INSTALL" ]; then cd ios && pod install && touch ran_pods && cd -; fi
error Command failed with exit code 1.

    at ChildProcess.exithandler (node:child_process:399:12)
    at ChildProcess.emit (node:events:526:28)
    at ChildProcess.emit (node:domain:475:12)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  killed: false,
  code: 1,
  signal: null,
  cmd: 'yarn install',
  stdout: 'yarn install v1.22.19\n' +

However, if that command is skipped and npx pod-install runs shortly after, that will complete successfully catching the error and running the appropriate command:
⠙ Baking CocoaPods [!] CocoaPods could not find compatible versions for pod "hermes-engine":
  In snapshot (Podfile.lock):
    hermes-engine (from `../node_modules/react-native/sdks/hermes/hermes-engine.podspec`)

  In Podfile:
    hermes-engine (from `../node_modules/react-native/sdks/hermes/hermes-engine.podspec`)

It seems like you've changed the version of the dependency `hermes-engine` and it differs from the version stored in `Pods/Local Podspecs`.
You should run `pod update hermes-engine --no-repo-update` to apply changes made locally.

 > pod update hermes-engine --no-repo-update

    ⠙ Baking CocoaPods Using Expo modules

Perhaps we should use that Expo script all the time?

:tada: This issue has been resolved in version 8.3.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Enhancement Request: XCreds app cant update ds

following on from https://macadmins.slack.com/archives/C03GBF2DE7P/p1713850151357849:
XCreds uses ds to store the kerberos and ad username/login, if one does not use xcreds login, these fields are not populated, and thus one cannot obtain a kerberos ticket, and the OIDC username is blank,
(easy fix via adding these attributes)
dscl . -create /Users/"${loggedInUser}" 'dsAttrTypeNative:_xcreds_oidc_username' "${loggedInUser}"
dscl . -create /Users/"${loggedInUser}" 'dsAttrTypeNative:_xcreds_activedirectory_kerberosPrincipal' "${loggedInUser}"@DOMAIN

suggested fix:

xcreds should save that value in prefs and use that if it isn't in DS, but currently doesn't

added code to copy and update the same values in DS. You can read them with :
defaults read ~/Library/Preferences/com.twocanoes.xcreds.plist
and are all prefixed with xcreds


initial sparql mapping commit

Adds sparql construct based mapping.

Still being tested -  PR in draft

Don't merge yet, found a regression in the single-graph-consumer logic

ok should be fixed now


Will onxxruntime backend support INT8 on cpu ?

Hi,
we are trying to quantise  our onnx models to int8 to run on cpu using : https://onnxruntime.ai/docs/performance/model-optimizations/quantization.html#quantization-on-gpu
we are using dynamic quantisation , and banking on AVX2 and AVX512 extensions , when we tested our models using onnx runtime we see an improvement so cross checking if this backend supports them by directly defining backend  in config.pbtxt ?

yes, onxxruntime backend support INT8 on cpu


evcc gets stuck connecting to mqtt on startup

Describe the bug
evcc gets stuck connecting to mqtt on startup
connecting to the mosquitto broker with mosquitto_sub is possible without delay
Steps to reproduce

sudo systemctl restart evcc
journalctl -f -u evcc

Configuration details
---
network:
  schema: "http"
  host: "<IP_ADDRESS>"
  port: 7070
interval: "2s"
sponsortoken: "..."
log: "info"
meters:
- name: "Test SmartPi"
  type: "custom"
  power:
    source: "mqtt"
    topic: "wa-pi/grid"
- name: "Senec Michael"
  type: "template"
  template: "senec-home"
  usage: "battery"
  host: "helios.ddnss.de:443"
- name: "Fronius Simulator"
  type: "template"
  template: "fronius-solarapi-v1"
  usage: "pv"
  host: "<IP_ADDRESS>:8083"
- name: "2nd Fronius for Evcc"
  type: "template"
  template: "fronius-solarapi-v1"
  usage: "pv"
  host: "<IP_ADDRESS>:8083"
chargers:
- name: "OCPP-1"
  type: "template"
  template: "ocpp"
  host: "<IP_ADDRESS>"
  id: 1
site:
  title: "Wien"
  meters:
    grid: "Test SmartPi"
    pvs:
    - "Fronius Simulator"
    - "2nd Fronius for Evcc"
    batteries:
    - "Senec Michael"
loadpoints:
- title: "OCPP-1"
  charger: "OCPP-1"
  phases: 3
  mode: "minpv"
mqtt:
  broker: "<IP_ADDRESS>"
  topic: "evcc"
  user: "..."
  password: "..."

Log details
Jan 19 20:13:13 smartpi systemd[1]: Started evcc.
Jan 19 20:13:18 smartpi evcc[22594]: [main  ] INFO 2023/01/19 20:13:18 evcc 0.111.1
Jan 19 20:13:18 smartpi evcc[22594]: [main  ] INFO 2023/01/19 20:13:18 using config file: /etc/evcc.yaml
Jan 19 20:13:18 smartpi evcc[22594]: [main  ] INFO 2023/01/19 20:13:18 starting ui and api at :7070
Jan 19 20:13:21 smartpi evcc[22594]: [db    ] INFO 2023/01/19 20:13:21 using sqlite database: /root/.evcc/evcc.db
Jan 19 20:13:21 smartpi evcc[22594]: [mqtt  ] INFO 2023/01/19 20:13:21 connecting evcc-409459007 at tcp://<IP_ADDRESS>:1883

What type of operating system are you running?
Linux
Version
evcc version 0.111.1

Please check trace log for whats really going on

Jan 19 21:07:27 smartpi systemd[1]: Started evcc.
 Should timeout after 5 minutes.


STYLE : Updated manual to correctly describe checkout of 5.0.0 branch

The current manual instructs the user to use git checkout v5.0.0 to get the latest release. The tags for this repository do not include the v prefix. The correct commmand should be git checkout 5.0.0.

thank you!


[Task]: Rename register proposal to add proposal

Task description
Register proposal might confuse the users, so let's change the wording to add proposal.
Requirements
TBD
Creation checklist

[ ] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

Maybe we call it "upload" proposal? Dont know, Add is also fine, definitely better than "register"

Included in #5546


rlang & dplyr/tidyr incompatibility issues

I ran into the error as reported at https://github.com/tidyverse/dplyr/issues/3941.
I tried to update rlang via conda install 'r-rlang>=3.1', but this resulted in the following:

    package                    |            build
    ---------------------------|-----------------
    r-bindr-0.1.1              |r351h6115d3f_1001          20 KB  conda-forge
    r-bindrcpp-0.2.2           |r351h29659fb_1001          93 KB  conda-forge
    r-ggplot2-2.2.1            |   r351h6115d3f_1         3.1 MB  conda-forge
    ------------------------------------------------------------
                                           Total:         3.2 MB

The following NEW packages will be INSTALLED:

  binutils_impl_lin~ pkgs/main/linux-64::binutils_impl_linux-64-2.31.1-h6176602_1
  binutils_linux-64  pkgs/main/linux-64::binutils_linux-64-2.31.1-h6176602_3
  bwidget            pkgs/main/linux-64::bwidget-1.9.11-1
  gcc_impl_linux-64  conda-forge/linux-64::gcc_impl_linux-64-7.3.0-habb00fd_1
  gcc_linux-64       conda-forge/linux-64::gcc_linux-64-7.3.0-h553295d_3
  gfortran_impl_lin~ pkgs/main/linux-64::gfortran_impl_linux-64-7.3.0-hdf63c60_1
  gfortran_linux-64  pkgs/main/linux-64::gfortran_linux-64-7.3.0-h553295d_3
  gxx_impl_linux-64  conda-forge/linux-64::gxx_impl_linux-64-7.3.0-hdf63c60_1
  gxx_linux-64       conda-forge/linux-64::gxx_linux-64-7.3.0-h553295d_3
  libgfortran-ng     pkgs/main/linux-64::libgfortran-ng-7.3.0-hdf63c60_0
  make               conda-forge/linux-64::make-4.2.1-h14c3975_2004
  tktable            pkgs/main/linux-64::tktable-2.10-h14c3975_0

The following packages will be REMOVED:

  r-ape-5.0-r3.4.1_0
  r-dplyr-0.7.4-r3.4.1_0
  r-tidyr-0.7.1-r3.4.1_0

The following packages will be UPDATED:

  cairo                                  1.14.12-he6fea26_5 --> 1.14.12-h80bd089_1005
  glib                                    2.55.0-h464dc38_2 --> 2.56.2-had28632_1001
  harfbuzz                                 1.9.0-h08d66d9_0 --> 1.9.0-he243708_1001
  libpng                                  1.6.34-ha92aebf_2 --> 1.6.37-hed695b0_0
  pcre                                               8.39-0 --> 8.41-hf484d3e_1003
  r-assertthat       conda-forge/linux-64::r-assertthat-0.~ --> conda-forge/noarch::r-assertthat-0.2.1-r351h6115d3f_0
  r-base                                            3.4.1-4 --> 3.5.1-he45234b_1005
  r-bh               conda-forge/linux-64::r-bh-1.66.0_1-r~ --> conda-forge/noarch::r-bh-1.69.0_1-r351h6115d3f_0
  r-bindr            conda-forge/linux-64::r-bindr-0.1.1-r~ --> conda-forge/noarch::r-bindr-0.1.1-r351h6115d3f_1001
  r-bindrcpp                           0.2.2-r341h9d2a408_1 --> 0.2.2-r351h29659fb_1001
  r-cli              conda-forge/linux-64::r-cli-1.0.0-r34~ --> conda-forge/noarch::r-cli-1.1.0-r351h6115d3f_0
  r-colorspace                         1.3_2-r341hc070d10_2 --> 1.4_1-r351hcdcec82_0
  r-crayon           conda-forge/linux-64::r-crayon-1.3.4-~ --> conda-forge/noarch::r-crayon-1.3.4-r351h6115d3f_1001
  r-digest                            0.6.18-r341hc070d10_0 --> 0.6.18-r351h96ca727_1000
  r-fansi                              0.3.0-r341hc070d10_0 --> 0.4.0-r351h96ca727_1000
  r-glue                               1.3.0-r341h470a237_2 --> 1.3.1-r351hcdcec82_0
  r-gtable           conda-forge/linux-64::r-gtable-0.2.0-~ --> conda-forge/noarch::r-gtable-0.3.0-r351h6115d3f_0
  r-labeling         conda-forge/linux-64::r-labeling-0.3-~ --> conda-forge/noarch::r-labeling-0.3-r351h6115d3f_1001
  r-lattice                          0.20_35-r341hc070d10_0 --> 0.20_38-r351h96ca727_1000
  r-lazyeval                           0.2.1-r341hc070d10_2 --> 0.2.2-r351hcdcec82_0
  r-magrittr         conda-forge/linux-64::r-magrittr-1.5-~ --> conda-forge/noarch::r-magrittr-1.5-r351h6115d3f_1001
  r-mass                              7.3_50-r341hc070d10_2 --> 7.3_51.3-r351hcdcec82_0
  r-munsell          conda-forge/linux-64::r-munsell-0.5.0~ --> conda-forge/noarch::r-munsell-0.5.0-r351h6115d3f_1001
  r-nlme                             3.1_137-r341h364d78e_0 --> 3.1_139-r351h9bbef5b_0
  r-pillar           conda-forge/linux-64::r-pillar-1.3.0-~ --> conda-forge/noarch::r-pillar-1.3.1-r351h6115d3f_1000
  r-pkgconfig        conda-forge/linux-64::r-pkgconfig-2.0~ --> conda-forge/noarch::r-pkgconfig-2.0.2-r351h6115d3f_1001
  r-plogr            conda-forge/linux-64::r-plogr-0.2.0-r~ --> conda-forge/noarch::r-plogr-0.2.0-r351h6115d3f_1001
  r-plyr                               1.8.4-r341h9d2a408_2 --> 1.8.4-r351h29659fb_1002
  r-purrr                              0.2.5-r341hc070d10_1 --> 0.3.2-r351hcdcec82_0
  r-r6               conda-forge/linux-64::r-r6-2.2.2-r341~ --> conda-forge/noarch::r-r6-2.4.0-r351h6115d3f_0
  r-rcolorbrewer     conda-forge/linux-64::r-rcolorbrewer-~ --> conda-forge/noarch::r-rcolorbrewer-1.1_2-r351h6115d3f_1001
  r-rcpp                               1.0.0-r341h9d2a408_0 --> 1.0.1-r351h0357c0b_0
  r-reshape2                           1.4.3-r341h9d2a408_2 --> 1.4.3-r351h29659fb_1003
  r-rlang                            <IP_ADDRESS>-r341h470a237_0 --> 0.3.4-r351hcdcec82_0
  r-scales                             1.0.0-r341h9d2a408_1 --> 1.0.0-r351h29659fb_1001
  r-stringi                            1.2.4-r341h9d2a408_1 --> 1.4.3-r351h0357c0b_0
  r-stringr          conda-forge/linux-64::r-stringr-1.3.1~ --> conda-forge/noarch::r-stringr-1.4.0-r351h6115d3f_0
  r-tibble                             1.4.2-r341hc070d10_2 --> 2.1.1-r351hcdcec82_0
  r-tidyselect                         0.2.4-r341h9d2a408_2 --> 0.2.5-r351h29659fb_1000
  r-utf8                               1.1.4-r341hc070d10_0 --> 1.1.4-r351h96ca727_1000
  r-viridislite      conda-forge/linux-64::r-viridislite-0~ --> conda-forge/noarch::r-viridislite-0.3.0-r351h6115d3f_1001

The following packages will be DOWNGRADED:

  r-ggplot2                            2.2.1-r341h6115d3f_1 --> 2.2.1-r351h6115d3f_1

It appears that there's some compatibility issues with r-rlang and r-dplyr, r-tidyr, & r-ape.
conda info:
     active environment : /ebio/abt3_projects/software/dev/llga/.snakemake/conda/a69c2539
    active env location : /ebio/abt3_projects/software/dev/llga/.snakemake/conda/a69c2539
            shell level : 2
       user config file : /ebio/abt3/nyoungblut/.condarc
 populated config files : /ebio/abt3_projects/software/dev/miniconda3_dev/.condarc
                          /ebio/abt3/nyoungblut/.condarc
          conda version : 4.6.13
    conda-build version : 3.11.0
         python version : 3.6.7.final.0
       base environment : /ebio/abt3_projects/software/dev/miniconda3_dev  (writable)
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://conda.anaconda.org/bioconda/linux-64
                          https://conda.anaconda.org/bioconda/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/free/linux-64
                          https://repo.anaconda.com/pkgs/free/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://conda.anaconda.org/leylabmpi/linux-64
                          https://conda.anaconda.org/leylabmpi/noarch
                          https://conda.anaconda.org/r/linux-64
                          https://conda.anaconda.org/r/noarch
                          https://conda.anaconda.org/qiime2/linux-64
                          https://conda.anaconda.org/qiime2/noarch
          package cache : /ebio/abt3_projects/software/dev/miniconda3_dev/pkgs
                          /ebio/abt3/nyoungblut/.conda/pkgs
       envs directories : /ebio/abt3_projects/software/dev/miniconda3_dev/envs
                          /ebio/abt3/nyoungblut/.conda/envs
               platform : linux-64
             user-agent : conda/4.6.13 requests/2.18.4 CPython/3.6.7 Linux/4.9.127 ubuntu/18.04.1 glibc/2.27
                UID:GID : 6354:350
             netrc file : None
           offline mode : False

I assume you're interpreting conda removing those packages as indicating an incompatibility. More likely conda thought you didn't need them for some reason (presumably they were pulled in by another package before). The following installs the most recent versions of the packages you indicated without issue:
conda create -n blahblah r-rlang r-ape r-dplyr r-tidyr

@nick-youngblut This seems to be a R 3.4.1 environment, where you try to install r-rlang >0.3.1. The newest r-rlang version for R 3.4.1 in conda-forge is r-rlang-<IP_ADDRESS>, see https://anaconda.org/conda-forge/r-rlang/files
I would do the same as @dpryan79 suggested, using conda create or conda env create -n blahblah -f environment.yaml to create an entire new R environment with newest package versions instead of upgrading an old R environment.

@dbast the issue seems to be the fact that I had the bioconda channel as higher priority than conda-forge. Changing channel priorities seems to have fixed the problem.


Support Amazon ECS

Add http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ECS_agent.html so that RancherOS supports ECS

RancherOS is easy to use as ECS Container Instances. Start RancherOS EC2 instances with the following user-data:
#cloud-config
rancher:
  environment:
    ECS_CLUSTER: your-ecs-cluster-name
  services_include:
    amazon-ecs-agent: true

Don't forget to choose the ECS Instance Role (e.g. ecsInstanceRole) in the IAM Role dropdown in the instance creation form.

@imikushin - can you put this in the README? Or is it documented somewhere else? Seems like an important feature to mention.

When v0.4.0 is officially announced, we'll be updating the docs to have this information included.


Add [XAU CL] #issuer GBCB4WO6J4ET55RWK2SVX76LUQ4PQ7TCDHG2YFILQML7D6XR3HACLXAU

Recently, my token was flagged as #unsafe. Please guide me on best practices to avoid these kinds of issues. Most of the issued tokens are backed by liquidity pools.

The new information has been modifieid.
Please stop changing the information to it "anchored" and sounding like it is connected to real gold. If it happens again the flagging will be permanent since this will be looked at a intentional and repeated deception.


phone verification, no phone

What is your username and discriminator?
uliwillcode
Why did you join Discord Linux?
i've switched Linux as my main OS, that's why i wanted to learn it more.
Where did you hear about Discord Linux?
On Programing discord server.
What is the passphrase that was assigned to you by the bot?
Info
Username: uliwillcode#0512
ID:<PHONE_NUMBER>48815104
Created: 2019/01/24 08:39:12

From Ethan Weegee#9302 :
The passphrase you have entered is not correct.  Please check the message that mentions you in the welcome channel to find your passphrase.

Closing as it's been more than 24 hours.


Move Fan Control Cluster to spec

I only updated to 1.2 spec (not 1.3 which has slightly newer revision);
Changes

Enum for sequence had High instead of On in the name
Made FanModeSequence attribute READ ONLY (and removed the test that attempted to prove it is writable)

Fixes #29406

Made FanModeSequence attribute READ ONLY

This part is pretty frustrating.  It used to be R[W], and then people changed the spec and didn't bother to file SDK issues or anything....


modified boxy2mne function

made some changes to the boxy2mne function:
-outputs the info struct along with the channels distances
-adds the wavelengths to each channel label and to the 'locs' array (which contains the coordinates)
-converts the coordinate units in the .tol file from millimeters to meters (seems to be the units mne wants)
-also added a few more comments to explain what each section is doing

great jon, I got this feedback from the MNE developers on our plan: https://github.com/mne-tools/mne-python/issues/7057#issuecomment-616030565


[Removal]:

Hotspot Name
Howling Mint Duck
Hotspot b58 Address
11st8GizYxfT9KmccnTNGex3yw7sZAjPPKjYbkDMin9tX96S9xm
Discord Handle
FuFu68 the Pharmacist 🧪#8124
Hotspot Manufacturer
bobcat
Removal Reason
for a few weeks I have grouped my hotspots in the same room because I am changing country on September 30th. It was temporary until this date, I imagine that the proximity of my various HS make that they were reported. precision I live well in marseille in france, and my HS are well located in france
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information
I never imagined having such a problem before leaving to live in Thailand. I enclose my identity documents, my plane ticket, and photos of the current installation. Since this installation is not deemed adequate, I request that you please remove it from the denylist. I will transfer my hotspots to my friend in Marseille, the same city as me, he is a professional in radio waves and will do a very clean installation. I enclose my bank account too, thank you for being understanding given the purchase of my very expensive machines.

@damiano68
Strongly suggest you remove your passport photos from all the issues you have added - this is not necessary for any denylist removals and is information you should keep private


Add files via upload for Yoobee college

@ranjurave Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@ranjurave You might miss my previous comment. Please react.

Thank you for the response. Here are the details

Domian - https://www.yoobee.ac.nz/
Address - Level 4, 3 City Road, Grafton, Auckland, New Zealand
Course - https://www.yoobee.ac.nz/courses/technology/bachelor-of-software-engineering
Email
<EMAIL_ADDRESS>(my email)

Hope I was able to provide what is required
Thank you
Ranju

@ranjurave  Thank you for the clarifications. Pull request merged. Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


flutter 2.2.2 release mode crash

detail https://github.com/flutter/flutter/issues/92162
when  I use 2.5.3 ,it's work,  not crash
but I hope fix this bug in 2.2.2, Who can help me?

dart::Thread::EnterIsolate(dart::Isolate*, bool) | thread.cc | 284 |   |
-- | -- | -- | -- | --
1 | Flutter | Dart_EnterIsolate | dart_api_impl.cc | 1546
2 | Flutter | Dart_EnterIsolate | dart_api_impl.cc | 1546
3 | Flutter | tonic::DartIsolateScope::DartIsolateScope(_Dart_Isolate*) | dart_isolate_scope.cc | 17
4 | Flutter | std::__1::__function::__func<tonic::DartMessageHandler::OnMessage(tonic::DartState*)::$_0, std::__1::allocatortonic::DartMessageHandler::OnMessage(tonic::DartState*)::$_0, void ()>::operator()() | functional | 1707
5 | Flutter | fml::MessageLoopImpl::FlushTasks(fml::FlushType) | message_loop_impl.cc | 132
6 | Flutter | fml::MessageLoopDarwin::OnTimerFire(__CFRunLoopTimer*, fml::MessageLoopDarwin*) | message_loop_darwin.mm | 76
7 | CoreFoundation | CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION | - | -
8 | CoreFoundation | __CFRunLoopDoTimer | - | -
9 | CoreFoundation | __CFRunLoopDoTimers | - | -
10 | CoreFoundation | __CFRunLoopRun | - | -
11 | CoreFoundation | CFRunLoopRunSpecific | - | -
12 | Flutter | fml::MessageLoopDarwin::Run() | message_loop_darwin.mm | 47
13 | Flutter | void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_deletestd::__1::__thread_struct >, fml::Thread::Thread(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&)::$_0> >(void*) | thread | 351
14 | libsystem_pthread.dylib | _pthread_start |   |

Hi @AKZHW,

when I use 2.5.3 ,it's work, not crash

Since you are no longer able to reproduce the issue on 2.5.3 so this is likely fixed, You will need to upgrade to stable 2.5.3, The new fixes are always released with a newer version so it always advisable to use the latest stable release to stay upto date with the latest fixes.
You can read more about How the release process works here https://github.com/flutter/flutter/wiki/Flutter-build-release-channels
Closing as fixed on the latest stable.

If we upgrade to 2.5.3, we will face a lot of adaptation costs，We just want to use 2.2.2

@AKZHW, It isn't feasible to add specific fixes to each stable release,

we will face a lot of adaptation costs
I am not sure what costs you are talking about, but upgrading shouldn't be an issue in my opinion.

Alternatively, If you decide not to upgrade then you might want to dig a bit into the stable 2.5.3 release notes and cherry-pick the fix to your stable 2.2.2  SDK.


Allow spreading of both attributes and event handlers

The {..foo} block parsing in a view! now supports everything impl IntoIterator<Item = B>, where B: Into<Binding> with Binding being either an attribute of type { name: &'static str, value: Attribute } or  an EventHandlerFn (typed, boxed Fn).
The old Vec<(&'static str, Attribute)> can still be used as {..foo}, as shown by the added spread example, to only spread attributes.
Vec<EventHandlerFn> can be used as {..foo}, to only spread event handlers.
Vec<Binding> can be used as {..foo}, to possibly spread both attributes and event handlers.
Multiple ({..foo} {..bar}) spreads can be performed on one element (possibly keeping attributes and handlers separate).
Closes: https://github.com/leptos-rs/leptos/issues/2431

Okay, this looks good to me, now, having looked into that last comment and discovered the enum is probably the way to go! Thanks so much.