Tapping Deny on WC / Dapp Connection Screen on Fresh Install Shows Invalid Homescreen

Current behavior
For users who freshly install Valora and attempt to connect to a Dapp, without first setting up their account, if they deny the Dapp connection prompt they arrive at an empty homescreen.
Desired behavior
The user if the account is not setup we don't try to open the deeplink or connect with WalletConnect ws url with Valora.
Steps to Reproduce
Perquisites  On a fresh install or reset account that has not completed onboarding.

Navigate to a service using WC or a deeplink e.g. PoolTogether or Sushi
Connect to Valora
Deny the Connection in Prompt

Video
https://user-images.githubusercontent.com/26950305/141374361-6d8a49d6-0fe1-41b2-a964-934c7baa51ad.mov
Workaround

Closing and reopening the app takes the user back to the first step of onboarding.

Versions
v1.21.0

Hey @MuckT, We have verified this issue using Latest Android Play store build V1.21.0, App store build V1.21.0 & observed the issue is reproducible.
Observation:

When user clicks on "Allow" button from wallet connect prompt it loads continuously, Cancel button, allow button is not clickable & on clicking cancel "X" button connecting screen appears. Attachment

Devices: One plus 7T(11.0), Redmi Note 8 (10.0), iPhone 12(15.0)
Thanks..!!

Hey @MuckT, We have verified this issue using Latest Android Internal Release build V1.24.1, iOS TestFlight Release build V1.24.1 and observed that issue is faced for "https://mento-fi-q5d61619k-celotools.vercel.app/" too
Observation:
-When user clicks on "Allow" button from wallet connect prompt , loader is seen continuously
-Cancel button, allow button both are not clickable after loader is seen
-Clicking on "X" button in top left navigates user to connecting screen.
Attachment: (mentoissue1.mp4)[]
Devices: Google Pixel 2XL(11.0), iPhone 12(14.7.1)
Thanks..!!

Hey @MuckT, We have verified this issue using Latest Android Internal Release build V1.24.1, iOS TestFlight Release build V1.24.1 and observed that issue is faced for "https://mento-fi-q5d61619k-celotools.vercel.app/" too
Observation:

When user clicks on "Allow" button from wallet connect prompt , loader is seen continuously
Cancel button, allow button both are not clickable after loader is seen
Clicking on "X" button in top left navigates user to connecting screen and then redirets user to home page where account address is not seen

Attachment: (mentoissue1.mp4)[https://drive.google.com/file/d/1HL5GkqORJotBQFCI-_RRH77u5tKXebQE/view?usp=sharing]
Devices: Google Pixel 2XL(11.0), iPhone 12(14.7.1)
Thanks..!!

This issue is no longer valid with the use of the Dapp Bottom Sheet.
https://user-images.githubusercontent.com/26950305/193930083-10c24fdf-687f-4423-8a9f-2f14c0ef5bf1.mov


Cannot conda install typhon for Python 3.8

Bug report
Bug summary
Using conda, I cannot install typhon for Python 3.8.  In fact, conda throws an exception.  Probably a bug in conda, but possibly triggered by something in typhon as it's not happening with Python 3.7 and I've not seen this bug with any other package installed via conda.  The failure appears similar to https://github.com/conda/conda/issues/8811 except that it's supposed to be fixed in conda 4.8.2.
Code for reproduction
conda create -n test -c rttools -c conda-forge --strict-channel-priority python=3.8 typhon

Actual outcome
Collecting package metadata (current_repodata.json): ...working... done
Solving environment: ...working... failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working...
Building graph of deps:   0%|          | 0/4 [00:00<?, ?it/s]
Examining @/linux-64::__glibc==2.26=0:   0%|          | 0/4 [00:00<?, ?it/s]
Examining typhon:  25%|██▌       | 1/4 [00:00<00:00, 7724.32it/s]
Examining python=3.8:  50%|█████     | 2/4 [00:02<00:02,  1.40s/it]
Examining python=3.8:  75%|███████▌  | 3/4 [00:02<00:00,  1.07it/s]
Examining @/linux-64::__cuda==10.0=0:  75%|███████▌  | 3/4 [00:02<00:00,  1.07it/s]

Determining conflicts:   0%|          | 0/4 [00:00<?, ?it/s]
Examining conflict for typhon python:   0%|          | 0/4 [00:00<?, ?it/s]
Examining conflict for __cuda:  25%|██▌       | 1/4 [00:00<00:02,  1.17it/s]
Examining conflict for __cuda:  50%|█████     | 2/4 [00:00<00:00,  2.34it/s]

Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed

# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<

    Traceback (most recent call last):
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/exceptions.py", line 1079, in __call__
        return func(*args, **kwargs)
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/cli/main.py", line 84, in _main
        exit_code = do_call(args, p)
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/cli/conda_argparse.py", line 82, in do_call
        return getattr(module, func_name)(args, parser)
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/cli/main_create.py", line 37, in execute
        install(args, parser, 'create')
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/cli/install.py", line 261, in install
        unlink_link_transaction = solver.solve_for_transaction(
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/core/solve.py", line 114, in solve_for_transaction
        unlink_precs, link_precs = self.solve_for_diff(update_modifier, deps_modifier,
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/core/solve.py", line 157, in solve_for_diff
        final_precs = self.solve_final_state(update_modifier, deps_modifier, prune, ignore_pinned,
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/core/solve.py", line 281, in solve_final_state
        ssc = self._run_sat(ssc)
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/common/io.py", line 88, in decorated
        return f(*args, **kwds)
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/core/solve.py", line 805, in _run_sat
        ssc.solution_precs = ssc.r.solve(tuple(final_environment_specs),
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/common/io.py", line 88, in decorated
        return f(*args, **kwds)
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/resolve.py", line 1318, in solve
        self.find_conflicts(specs, specs_to_add, history_specs)
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/resolve.py", line 347, in find_conflicts
        bad_deps = self.build_conflict_map(specs, specs_to_add, history_specs)
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/resolve.py", line 506, in build_conflict_map
        c = self.breadth_first_search_for_dep_graph(
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/resolve.py", line 369, in breadth_first_search_for_dep_graph
        last_spec = MatchSpec.union((path[-1], target_paths[-1][-1]))[0]
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/models/match_spec.py", line 481, in union
        return cls.merge(match_specs, union=True)
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/models/match_spec.py", line 475, in merge
        reduce(lambda x, y: x._merge(y, union), group) if len(group) > 1 else group[0]
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/models/match_spec.py", line 475, in <lambda>
        reduce(lambda x, y: x._merge(y, union), group) if len(group) > 1 else group[0]
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/models/match_spec.py", line 502, in _merge
        final = this_component.union(that_component)
      File "/data/gholl/miniconda3/lib/python3.8/site-packages/conda/models/match_spec.py", line 764, in union
        return '|'.join(options)
    TypeError: sequence item 0: expected str instance, Channel found

`$ /data/gholl/miniconda3/bin/conda create -n test -c rttools -c conda-forge --strict-channel-priority python=3.8 typhon`

  environment variables:
         ALSA_CONFIG_PATH=/etc/alsa-pulse.conf
                 CIO_TEST=<not set>
        CONDA_DEFAULT_ENV=/media/nas/x21324/miniconda3
                CONDA_EXE=/data/gholl/miniconda3/bin/conda
             CONDA_PREFIX=/media/nas/x21324/miniconda3
    CONDA_PROMPT_MODIFIER=(/media/nas/x21324/miniconda3)
         CONDA_PYTHON_EXE=/data/gholl/miniconda3/bin/python
               CONDA_ROOT=/data/gholl/miniconda3
              CONDA_SHLVL=1
                  MANPATH=/media/nas/x21308/inst/texlive/2019/texmf-
                          dist/doc/man:/media/nas/x21308/inst/texlive/2019/texmf-
                          dist/doc/man:/media/nas/x21308/inst/texlive/2019/texmf-
                          dist/doc/man:/usr/local/man:/usr/share/man
                 NO_PROXY=<set>
                     PATH=/media/nas/x21308/inst/texlive/2019/bin/x86_64-linux:/media/nas/x21308
                          /inst/texlive/2019/bin/x86_64-linux:/media/nas/x21308/inst/texlive/201
                          9/bin/x86_64-linux:/media/nas/x21324/miniconda3/bin:/media/nas/x21324/
                          miniconda3/condabin:/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/loc
                          al/bin:/usr/bin:/bin:/opt/bin:/usr/lib/mit/sbin:/opt/perforce/bin:/opt
                          /hdf-java/bin:/usr/lib/mit/sbin:/opt/perforce/bin
            PYTHONSTARTUP=/home/gholl/.pythonrc.py
       REQUESTS_CA_BUNDLE=<not set>
              SOCKS_PROXY=<set>
            SSL_CERT_FILE=<not set>
               WINDOWPATH=7
                 XNLSPATH=/usr/share/X11/nls
                ftp_proxy=<set>
             gopher_proxy=<set>
               http_proxy=<set>
              https_proxy=<set>
                 no_proxy=<set>
              socks_proxy=<set>

     active environment : /media/nas/x21324/miniconda3
    active env location : /media/nas/x21324/miniconda3
            shell level : 1
       user config file : /home/gholl/.condarc
 populated config files : /home/gholl/.condarc
          conda version : 4.8.2
    conda-build version : not installed
         python version : 3.8.1.final.0
       virtual packages : __cuda=10.0
                          __glibc=2.26
       base environment : /data/gholl/miniconda3  (writable)
           channel URLs : https://conda.anaconda.org/rttools/linux-64
                          https://conda.anaconda.org/rttools/noarch
                          https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /data/gholl/miniconda3/pkgs
                          /home/gholl/.conda/pkgs
       envs directories : /data/gholl/miniconda3/envs
                          /home/gholl/.conda/envs
               platform : linux-64
             user-agent : conda/4.8.2 requests/2.22.0 CPython/3.8.1 Linux/4.12.14-lp150.12.82-default opensuse-leap/15.0 glibc/2.26
                UID:GID : 16209:16217
             netrc file : None
           offline mode : False

An unexpected error has occurred. Conda has prepared the above report.

If submitted, this report will be used by core maintainers to improve
future releases of conda.
Would you like conda to send this report to the core maintainers?

[y/N]:
Timeout reached. No report sent.

Expected outcome
I expected a working conda environment with the latest released typhon and Python 3.8.1.
Version information

Operating System: openSUSE 15.0
Typhon Version: latest on conda (attempted)
Python Version: 3.8.1 (attempted)
Conda Version: 4.8.2

Sometimes conda doesn't throw an exception, but instead outputs:
Collecting package metadata (current_repodata.json): ...working... done
Solving environment: ...working... failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working...
Building graph of deps:   0%|          | 0/4 [00:00<?, ?it/s]
Examining @/linux-64::__cuda==10.0=0:   0%|          | 0/4 [00:00<?, ?it/s]
Examining typhon:  25%|██▌       | 1/4 [00:00<00:00, 4315.13it/s]
Examining python=3.8:  50%|█████     | 2/4 [00:02<00:02,  1.36s/it]
Examining python=3.8:  75%|███████▌  | 3/4 [00:02<00:00,  1.10it/s]
Examining @/linux-64::__glibc==2.26=0:  75%|███████▌  | 3/4 [00:02<00:00,  1.10it/s]

Determining conflicts:   0%|          | 0/4 [00:00<?, ?it/s]
Examining conflict for __cuda:   0%|          | 0/4 [00:00<?, ?it/s]
Examining conflict for typhon python:  25%|██▌       | 1/4 [00:00<00:00, 10699.76it/s]

Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed

UnsatisfiableError: The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions

Package python conflicts for:
typhon -> python[version='3.5.*|3.6.*|>=3.5,<3.6.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0']
typhon -> docutils -> python[version='2.7.*|>=2.7,<2.8.0a0|>=3.8,<3.9.0a0|3.4.*|>=3.6|>=3.5.3|>=3.5|>=3.8.0a,<3.9.0a0']
python=3.8The following specifications were found to be incompatible with your CUDA driver:

  - feature:/linux-64::__cuda==10.0=0

Your installed CUDA driver is: 10.0

Note that strict channel priority may have removed packages required for satisfiability.

Also reported at https://github.com/conda/conda/issues/9681

If I install it into an existing environment I get:
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: /
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.
failed

UnsatisfiableError: The following specifications were found
to be incompatible with the existing python installation in your environment:

Specifications:

  - typhon -> python[version='3.5.*|3.6.*|>=3.5,<3.6.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0']

Your python: python=3.8

If python is on the left-most side of the chain, that's the version you've asked for.
When python appears to the right, that indicates that the thing on the left is somehow
not available for the python version you are constrained to. Note that conda will not
change your python version to a different minor version unless you explicitly specify
that.

The following specifications were found to be incompatible with your CUDA driver:

  - feature:/linux-64::__cuda==10.0=0

Your installed CUDA driver is: 10.0

Note that strict channel priority may have removed packages required for satisfiability.

We don't provide any Python 3.8 Anaconda packages, since there is no stable Anaconda Distribution with Python 3.8 available yet.
When you're trying to install the current py37 package in a Python 3.8 environment, it most likely triggers a downgrade to Python 3.7 and everything goes haywire in Anaconda's dependency resolution. This is an upstream issue.

Why do you need a stable anaconda distribution to provide packages when there is a python-3.8 package on conda-forge, which most people use? Typhon appears quite alone in this decision, there are python 3.8 packages for scipy, numpy, pandas, numba, xarray, numexpr, satpy, matplotlib, scikit-learn, imageio, bokeh, and many others.  I'm not aware of other packages that wait for the full Anaconda Distribution before providing builds for 3.8.  What is the rationale here?

We agreed upon that typhon only depends on anaconda main and not on conda-forge. Currently it is not possible to build a python 3.8 package without using conda-forge because netcdf4-py38 is still missing in main:
conda create -n test python=3.8 python
[snip]

conda install netcdf4
[snip]
UnsatisfiableError: The following specifications were found
[snip]
  - netcdf4 -> python[version='>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.7,<3.8.0a0|>=3.5,<3.6.0a0']

Your python: python=3.8

As soon as this dependency is satisfied by anaconda/main, I'll happily add a 3.8 package to our builds.

There's still a difference between not requiring conda-forge and not supporting conda-forge — adding a 3.8 package would not affect people trying to install typhon for python 3.7 without using conda-forge.  But it's not important, I can easily install typhon in my python 3.8 environment with pip.


Driver refuses to load

I've compiled both projects and signed the driver:
"C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x64\signtool.exe" sign /v /f D:\Experimental\ReClass.NET-KernelPlugin\bin\MySPC.pfx /t http://timestamp.verisign.com/scripts/timstamp.dll /p my_passowrd
I've also built a loader to load the library (running as admin):
#undef UNICODE
#include <windows.h>
#include <iostream>
int main()
{
	HINSTANCE hGetProcIDDLL = LoadLibrary("D:\\Experimental\\ReClass.NET-KernelPlugin\\bin\\x64\\KernelCore.dll");

	if (hGetProcIDDLL == NULL) {
		std::cout << "cannot locate the .dll file" << std::endl;
	}
	else {
		std::cout << "it has been called" << std::endl;
		return -1;
	}
}

It seems to fail on this line:
Driver.cpp:55
if (!NT_SUCCESS(status = NtLoadDriver(&m_registry_entry))) {
instead of going to return false.. the function immediately exits. With status = -1073740760
My issue here is how to debug drivers I think. Any tips on how to debug or fix this issue?
Thanks

Stupid question... copy into system32 and use from there.. fixed. DependencyWalker reading the file from where it was built would show that.

I have a feeling this has to do with using the windows 10 sdk.. I'll try 8.1.

that error code is STATUS_INVALID_IMAGE_HASH, is the driver malformed? also make sure the dll and the driver are in the same directory.
Also, the dll tries to load the driver based on the current directory, which is based on the reclass.net app, as seen here
std::wstring driver_path = fs::current_path().wstring() + L"\\Plugins\\ReClassKernel64.sys";

Yup, I made sure the path was correct, set a breakpoint checked the path exactly. I rebuilt Reclass.net, ended up getting that going but it just fails to load the plugin.
I think my issue is I migrated to Visual Studio 2019, I'm going to try 2015. I'm trying this because I seem to get a failure on other driver loading projects trying to load it in. Maybe something to do with the SDK / DDK / VS 2019.
This for example has changed in the project:

There is no configuration type Driver and no Platform Toolset 8.1 that works

I was thinking there is a platform toolset for WindowsKernelModeDriver10. I appreciate the help Timboy, this plugin I'm hoping will help me immensely with learning Reclass.net (on handles that block traditional memory reading calls).

Followed this:
https://github.com/DarthTon/Blackbone/issues/218#event-1385719174

Add cert as Trusted Root CA
bcdedit.exe /set testsigning on
reboot

Seems to load the driver now, trying with Reclass.net

this sounds like your code signing certificate is not working properly, if it works for test signing but not for ur cert, its because you didnt buy an actual code signing certificate, and are using a self-made or test (WDKTestCert) one

That sounds about right. I ended up using another project and using it to load in my driver (I think intel driver it used?). It seemed to work no problem, would need a bit of rework to make it work with Reclass.net Plugins.
But I decided to go in another direction and work from Linux with KVM (where there is no Reclass unfortunately, unless I load it into the windows system).

You can run ReClass.NET in Linux. Just use Mono to run it.
https://www.youtube.com/watch?v=GkB0dCcAQVw&list=PLO246BmtoITanq3ygMCL8_w0eov4D8hjk&index=6&t=0s

You're absolutely right, someone let me know about this early and i'm working on it hopefully.

Just a follow up: I ended up having some success loading drivers without test signing on with EfiGuard - https://github.com/Mattiwatti/EfiGuard. You can turn off driver signing verification, load the driver, turn driver signing verification back on. Closing this now.


Added an open source css template

Added a template css file and linked it to base.njk.

👷 Deploy Preview for benevolent-sprinkles-4567d6 processing.

Name
Link

🔨 Latest commit
68b344fc9904cfd186ce7d0ad2ba5d875fa26f0e

🔍 Latest deploy log
https://app.netlify.com/sites/benevolent-sprinkles-4567d6/deploys/65bb97cde92170000826310a


son-gtkkpi

Integration between kpi module, gtkapi and monitoring system

https://github.com/sonata-nfv/son-tests/tree/master/int-gtkkpi-prometheus


Support TypeScript 5.2.2

Context
TypeScript 5.2.2 comes with a breaking change that requires all @typescript-eslint/* dependencies to move to >= v6: https://github.com/typescript-eslint/typescript-eslint/issues/7155#issuecomment-1692384149.
In this repository that specifically means moving from
"@typescript-eslint/experimental-utils": "^5.3.0"

to
"@typescript-eslint/utils": "^6.0.0"

Changes
Add tests
To give more confidence that behaviour was preserved before and after making changes tests have been added.
This was done using the recommendations from https://typescript-eslint.io/developers/custom-rules#testing - use @typescript-eslint/rule-tester paired with vitest.
These tests can be reverted if they are not desired.
Update to @typescript-eslint/utils and<EMAIL_ADDRESS>This is the main change, allowing this really helpful plugin to continue to be used with newer typescript.

This is a breaking change as well for this package I guess, might need to bump the major version~

I'm thinking should I merge your PR and release a major version first before bumping @typescript-eslint/utils to v8 in another PR. This way people stuck with v6 of @typescript-eslint/utils could make use of your changes in this PR.
@dominicfraser What do you think?

Hi @shian15810 ☺
I tested updating to v8, and pushed a commit showing what that would look like: https://github.com/shian15810/eslint-plugin-typescript-enum/pull/338/commits/34496c58dd7c75bf6243333122da57784961b0fc.
I've then reset it back to v6.
I think your plan of merging with the v6 changes, doing a release, and then updating to v8 and doing another release is a good plan. It gives flexibility to people to be able to update in stages if they need to 👍


refactor(cli): misc config improvements

Context

Description

Dependencies: #360
This PR introduces various improves to the handling of accounts:

Renaming Owned and Alias accounts to User and Deployment accounts
Introducing a AddressOrAlias type for the CLI arguments
Removing some old CLI flags (self-address, referer) + renaming current flags to more sensible / consistent names
Config::load() will now always be at the start of the entry-points of commands, instead of main
Use register_*_apis functions from jstz_proto with default / config values

Manually testing the PR

This is a very large PR that should ideally be split into 3 smaller ones. In the interest of time I am not going to ask for it, but please do so next time for other similar PRs.

I concur, writing bits of the configure is a bit messy. Thanks for not requiring it (since this would delay merging this PR) 🙏

I see that it has no manual testing section, so before merging please ensure that it was tested. Overall the changes seem reasonable, but I can't test them all so I believe we should have 1-2 day long internal ecosystem dogfooding session to properly test everything before wider dogfooding release as a lot of changes are being introduced quickly.

We can add this to the sprint planning today, I think it is an excellent idea to do a day or 2 of QA


Unable to find string literal

I tried to build this and ran into some issues:
Building "alarm.so" for ZNC 1.6.5... alarm.cpp:75:30: warning: ‘get_start_time’ function uses ‘auto’ type specifier without trailing return type [enabled by default]
     auto get_start_time  ( ) const
                              ^
alarm.cpp:79:27: warning: ‘get_end_time’ function uses ‘auto’ type specifier without trailing return type [enabled by default]
     auto get_end_time ( ) const
                           ^
alarm.cpp:87:24: warning: ‘get_timer’ function uses ‘auto’ type specifier without trailing return type [enabled by default]
     auto get_timer ( ) const
                        ^
alarm.cpp:91:21: warning: ‘get_id’ function uses ‘auto’ type specifier without trailing return type [enabled by default]
     auto get_id ( ) const
                     ^
alarm.cpp:103:22: error: unable to find string literal operator ‘operator"" s’
     string reason_ = "Default"s;

The error I changed to:
 string reason_ = "Default";

(the warnings I left because didn't know what to do)
The module was able to build after removing the s off the end, and I could load it with /znc loadmod alarm, although upon trying /znc *alarm add or /znc *alarm list it completely crashed znc.

 Then again, I'll probably update it within the next days to be less of a catastrophe.
Regarding your compile issues:
I just tried if it compiles and it does so on znc 1.6.3 with the "-std=c++14" flag set in znc-buildmod.
Can you please post your CXXFLAGS from /usr/bin/znc-buildmod?
Regarding the crash issue upon issuing "list":
I just tried it and on my znc version and it doesn't crash. Which version are you using?

heheh, yes — I like your idea, and thanks for responding.
current znc-buildmod CXXFLAGS:
CXXFLAGS="  -DOPENSSL_NO_COMP=1 -std=c++11 -D_FORTIFY_SOURCE=2 -O2 -Wall -W -Wno-unused-parameter -Woverloaded-virtual -Wshadow -pthread   -fvisibility=hidden -fPIC -include znc/zncconfig.h -I/usr/local/include $CXXFLAGS"
MODLINK="-shared $MODLINK"
VERSION="1.6.5"

ZNC Version 1.65
GCC Version gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-11)
I used the -std=c++1y and I still get the error:
Building "alarm.so" for ZNC 1.6.5... alarm.cpp:105:22: error: unable to find string literal operator ‘operator"" s’
     string reason_ = "Default"s;

Once I change that it compiles with no errors or warnings.
/znc *alarm list seems to work:
*alarm There are no timers running at the moment.

However, /znc *alarm add completely crashes znc to the ground.
'm not sure where logs for znc stores it logs for such events, but I'm happy to provide whatever info you might need to get this working, thanks!

It seems that your compiler (c++ lib implementation) is too old to support string literals.
I still wonder why it crashes as I don't have that issue on my odroid (arm based) and on my development machine (amd64). I'll try to obtain your exact compiler version + znc version and see if I can figure something out.
I'll now try to get your compiler and znc version to see if I can reproduce the behavior somehow.
I'll report back and sorry for the delay in my answer.

That is strange; I can only imagine that thread is off forking somewhere else. 😜

Closed because I just tried it on my odroid after using the newest image and it seems to work there now, too. Please feel free to tell me if the issue still persists.


the valset of rad

Hello, I recently read the MMQ paper and code, there is a question, that is, the RAD dataset does not have a validation set, then I want to ask, what do we rely on to find the best accuracy model, and then use the test set to test the final accuracy? Thank you very much for your answer.

Hello, we also encountered the same problem, that is, after training 40 epochs, how do we choose the best model to test the accuracy on the test set? Is it to load all the generated weight models of 40 epochs in order to test the accuracy in the test set? Then choose the highest precision as the best result?

Thank you very much for your reply


--imports option for outputting # from xxx.yyy import function_name

This will make it even easier to pipe -s output to llm and get back working code examples.
symbex -d symbex --imports

Should output:
# File: symbex/lib.py Line: 12
# from symbex.lib import find_symbol_nodes
def find_symbol_nodes(code: str, filename: str, symbols: Iterable[str]) -> List[Tuple[(AST, Optional[str])]]

# File: symbex/lib.py Line: 36
# from symbex.lib import code_for_node
def code_for_node(code: str, node: AST, class_name: str, signatures: bool, docstrings: bool) -> Tuple[(str, int)]

Also a --no-file option to suppress output of the # File:  lines.
Those can have shortcuts of -i for --imports and -n for --no-code - so if you want to apply both (and just get the imports) you can then do this:
symbex -d symbex -in

The interesting challenge here is how to figure out that import string, since it depends on the location of the function relative to the Python path.
I think the following heuristics should work:

If the file in question lives in any of the directories currently on sys.path, figure it out relative to that
Otherwise, try to figure it out relative to one of the -d directory paths (including . if symbex was run without arguments)
For -f path/to/file.py files which are outside of anything in sys.path just go with from .module import function_name

Tried those heuristics and found a problem - when using the -d option you often want to do things like -d ../datasette/tests - but that gives incorrect import statements.
Might be that it needs a --imports-relative ... option too.

That --imports-relative option could be called --sys-path and could add new folders to the simulated sys.path when calculating relative imports.
Part of the reason I'm having trouble here is that -d ../datasette is also pulling in files from datasette/.eggs. Two things that would help here:

.gitignore support, which is really tricky, see conversation here: https://github.com/simonw/symbex/issues/15#issuecomment-1597456924
The ability to exclude directories, using maybe -x/--exclude ../datasette/.eggs.

This initial implementation doesn't yet do anything fancy with sys.path but it's enough to start experimenting.

This does not do the right thing with class methods, *.*:
symbex '*.*' -in

# from tests.example_symbols import __init__
    def __init__(self, a)

# from tests.example_symbols import method_types
    def method_types(self, b: int) -> bool

For class methods attempting to display a from x import y line doesn't make sense at all.
What would make sense? I guess showing the name of the class, which the # File line does already:
symbex '*.*' --imports

# File: tests/example_symbols.py Class: ClassWithMethods Line: 79
# from tests.example_symbols import __init__
    def __init__(self, a)

# File: tests/example_symbols.py Class: ClassWithMethods Line: 82
# from tests.example_symbols import method_types
    def method_types(self, b: int) -> bool

So what should -in do here? Maybe it should remove the File: line but add in a new Class: XXX line, perhaps like this:
# Class tests.ClassWithMethods
    def __init__(self, a)

A thing that worries me about this feature is that it's genuinely making promises it can't keep.
If an LLM is fed an incorrect import path it will generate incorrect example code.
If a user is browsing function documentation using this and reads an incorrect import path they'll get confused too.


Reducer<FormState, AnyAction>' is not assignable to type 'Reducer<FormState | undefined, AnyAction>

Description
After removing example app and generating a container PLOP.
Project fails to compile Typescript.
Steps to reproduce
npx create-react-app --template cra-template-rb my-app
cd my-app
npm run cleanExampleApp
npm run generate
[PLOP] Please choose a generator. container - Add a container component

What should it be called? Form
Do you want to wrap your component in React.memo? No
Do you want headers? No
Do you want a redux slice(actions/selectors/reducer) for this container? Yes
Do you want sagas for asynchronous flows? (e.g. fetching data) Yes
Do you want to use styled-components? Yes
Do you want i18n translations (i.e. will this component use text)? No
Do you want to load the component asynchronously? No
Do you want to have tests? No

npm start
Failed to compile.
/src/app/containers/Form/index.tsx(19,37):
Type 'Reducer<FormState, AnyAction>' is not assignable to type 'Reducer<FormState | undefined, AnyAction>'.
  Type 'FormState | undefined' is not assignable to type 'FormState'.
    Type 'undefined' is not assignable to type 'FormState'.  TS2322

    17 |
    18 | export function Form(props: Props) {
  > 19 |   useInjectReducer({ key: sliceKey, reducer: reducer });
       |                                     ^
    20 |   useInjectSaga({ key: sliceKey, saga: formSaga });
    21 |
    22 |   // eslint-disable-next-line @typescript-eslint/no-unused-vars

Expected behavior
PLOP for new container does not fail to compile Typescript.
Versions

react-boilerplate-cra-template: v0.1.0
Node/NPM: v12.16.1
Browser: Chrome v81.0.4044.122

Starting template was the problem actually sorry. I fixed it. You can also fix it by changing the src/utils/types/injector-typings.ts file to
import { RootState } from 'types';
import { Reducer, AnyAction } from 'redux';
import { Saga } from 'redux-saga';
import { SagaInjectionModes } from 'redux-injectors';

type RequiredRootState = Required<RootState>;

export type RootStateKeyType = keyof RootState;

export type InjectedReducersType = {
  [P in RootStateKeyType]?: Reducer<RequiredRootState[P], AnyAction>;
};
export interface InjectReducerParams<Key extends RootStateKeyType> {
  key: Key;
  reducer: Reducer<RequiredRootState[Key], AnyAction>;
}

export interface InjectSagaParams {
  key: RootStateKeyType | string;
  saga: Saga;
  mode?: SagaInjectionModes;
}

The changes you can see in the commit I just made

Thank You!


fix for codepress js lib use GPL Licensing in 4.4.x Carbon.Ui #1562

https://github.com/wso2/carbon-kernel/issues/1562
Remove codepress from carbon ui for solving this issue.


Support for Sony Bravia TV

Description:
The braviatv platform allows you to control a Sony Bravia TV.
To add a Sony Bravia TV to your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entry
media_player:
  platform: braviatv
  host: <IP_ADDRESS>
  name: Living Room TV

Configuration variables:

host (Required): The IP of the Sony Bravia TV, eg. <IP_ADDRESS>
name (Optional): The name you would like to give to the Sony Bravia TV.

You will need to configure your TV to allow the Home Assistant for remote usage. To do that, ensure that your TV is turned on. Open the configuration popup on Home Assistant and enter whatever PIN (for example, 0000). After that, the TV will show you a PIN and the Home Assistant will allow you to re-enter a new PIN. Enter the PIN shown on your TV and your Home Assistant will be allowed for remote usage on your Sony Bravia TV.
Supported almost all Sony Bravia TV 2013 and newer at http://info.tvsideview.sony.net/en_ww/home_device.html#bravia
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#
Example entry for configuration.yaml (if applicable):
# Example configuration.yaml entry
media_player:
  platform: braviatv
  host: <IP_ADDRESS>
  name: Living Room TV

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If code communicates with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

This platform contains a lot of logic for communicating with the TV. It would be best to split this out into a separate library and add that library as a dependency.
Nice use of the configurator component, though. 👍  That one definitely goes under-appreciated.

Thank you regarding the configurator usage. I think that the configurator is a great piece for this kind of use cases. You should work on improving it to support more scenarios.
Regarding your comment, I don't see lot of logic within my component, just the necessary to communicate with bravia TV taking into account current HA capabilities. I have performed a big clean-up before merging this guy into your branch and I think we could save a dependency in that sense.
We could think about moving out to a library if we have to support more devices using the same protocol.
The component work like a charm, I have it connected to my Amazon ECHO via HA and after going back from work I have just to tell it: "Alexa, tell home assistant to turn on the TV" :)

Yeah.
We don't want any protocol parsing etc in this repo. That way other people that do not use HA will not be able to leverage your work and we will have to maintain protocol upgrades.

Ok, the code has been updated according to your suggestions.
Thank you!

It looks good. Please rebase on the latest dev branch to resolve your merge conflicts.

Ok, done!

You didn't rebase but merged the branch. Now it shows 23 files changed and I can no longer verify which changes this PR brings. Please fix it 👍

Ops, sorry! fixed!

Ok, done! Please review it again to check if everything looks cool now!

Hi Aparraga,
Many thanks for building this component! It's (almost) working great! I copied the code to my custom sensor folder for now.
I have a Sony Bravia KDL myself, connected to my WIFI network. When my TV is turned on, everything works great, however, when it's turned off the below error message is logged. This is obviously caused by the braviarc submitting a request while the host is not available.
I started to fiddle around a bit myself to see whether i can first ping the host before submitting the request but haven't been able to solve it so far.
You help would be appreciated.
Jun 23 19:48:09 raspberrypi hass[5165]: ERROR:braviarc.braviarc:[W] Exception: HTTPConnectionPool(host='<IP_ADDRESS>', port=80): Max retries exceeded with url: /sony/accessControl (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x76426d70>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=10)'))

Thank you Dennuuz,
Problem with the ping is that Bravia responds to pings even if it's turned off.
So, component can't guarantee Bravia status based on ping. I think that checking the status of the TV by calling rest service is a good choice. Maybe component should catch this exception to avoid log the error.
Does it make sense?


touching up graphics

cleaned up a few image mistakes that Jason pointed out.

closing in favor of #765


Feature:Add Graceful Shutdown

What this PR does:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

remove test to samples

samples:   https://github.com/dubbo-go-pixiu/samples/pull/22

Codecov Report

Merging #474 (524b940) into develop (47d95f2) will decrease coverage by 0.25%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop     #474      +/-   ##
===========================================
- Coverage    37.20%   36.95%   -0.26%
===========================================
  Files           56       56
  Lines         3811     3837      +26
===========================================
  Hits          1418     1418
- Misses        2230     2256      +26
  Partials       163      163

Impacted Files
Coverage Δ

pkg/server/listener_manager.go
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

go fmt

samples: dubbo-go-pixiu/samples#22

The new PR https://github.com/apache/dubbo-go-pixiu-samples/pull/1


updates are not sent to the widget deterministically / refresh button not always working

need to log events to file and try to find some pattern


CI: Release pipeline/docs

[x] Finish up CI by setting up a release pipeline on Azure
[ ] Document our release process (On a wiki - perhaps the meta repo)

Release docs can be found in our wiki, here https://github.com/python-discord/django-simple-bulma/wiki/Release-to-PyPI


Use GitHub-flavored markdown code blocks with language specified

This might not help with actual rendering on the site, so feel free to reject

Keep them in same way will be helpful for others, thanks for your work~


Symbol "long dash" (–) is broke after saving.

Hello colleagues, I have an issue related to encoding in my application. Or even with symbol long dash (–).
After saving(POST/PUT/PATCH) some entity with text field in frontend the symbol long dash (–) was saved in database like â.
Our tech stack and flow: SAPUI5 - AppRouter - nodeJS odata-v2-adapter (converting metadata to odataV2) - CAP (on odataV4) - Hana Cloud Db.
Frontend SAPUI5 and backend CAP was configured with UTF-8, but it did not help.
If do a save request via Postman to backend - everything is ok. But frontend also do not have a problem before requesting to backend, json file is ok.
If put a breakpoint in ODataProcessor.java (CAP) - we can see already broken data (in input stream).
I'm not sure where exactly this problem is.
Maybe some framework does not have some symbol support or the issue related to charset.

Hello @Kir-4K,
I have just checked with our internal test apps doing a PATCH (OData V4) resp MERGE (OData V2) in a "pure" scenario against a SAP Gateway backend and checked the http traffic plus the contents of the changed field after refresh: everything is okay.
I am not aware of any logic doing encoding for the V2 Adapter, did may check the payload of the http request, i.e. is this already wrong? Or does it fail on the server side before reaching ODataProcessor.java?
As the OData V4 model's V2 Adapter only supports read scenarios (and is only tested for those), see https://sapui5.hana.ondemand.com/#/topic/365bdbd737034334a38a6fef07345196
... The OData V4 model can consume an OData V2 service for read scenarios only. ...
I am closing this.
Regards,
Patric


2024-10-22/25: 👥ISPRS Technical Commission IV Symposium 2024

https://www.isprs.org/tc4-symposium2024/index.html
See also
#348

I am now included in the keynote speaker list.
https://www.isprs.org/tc4-symposium2024/speakers.html

As in #594, successfully completed!


auto_recrawl not stopped

on latest version pyspider it worked...
on this version is working:
http://demo.pyspider.org/task/recrawl:6ab016b2dad7ba49a992ba0213a91cf8
git clone https://github.com/binux/pyspider.git and run this code, then task always recrawl, age not working.

How do you stop a auto_recrawl task? What do you mean by age not working?
'on this version is working' - you mean the demo version?

yes, in the demo version demo.pyspider.org is working, on the latest version do not working.
age=50*60 or 1000 not difference.
Now I rewrote on exetime

The interval of auto_recrawl is set when the task created, if you changed the age afterward, it will not work. You have to force_update the same task to modify the age. If you want to stop it, use cancel


Docker Environment

Added a complete docker environment and added a Github Workflow which triggers a build using Github Actions for every commit.
Docker for dummies: https://youtu.be/_dfLOzuIg2o
How to install docker on macOS: https://www.docker.com/products/docker-desktop/
To build a image you can simply change directory into the git repo and run the command bash build_container.sh
The script will now build a image (some binary) of the full installation based on the rules described in Dockerfile.
Now, to activate and access a container based on the image you can simply run the command bash run_container.sh.  You will also be able to build code inside the container. In fact, I made a alias for this as well.

Sweet, takk!


[express-apollo-prisma] Stopping the script start causes an error

Reproduction
Stack
OS: MacOS 13.1
Shell: zsh
Node: 16.17.0
Steps

Run pnpm install
Ensure there is a valid configuration (for example, by copying .env.example to .env)
Run pnpm infrastructure:start
Run pnpm run start
Press [ctrl] + [c]

Expected behaviour
All services started by the command should gracefully stop again. No errors should be shown in the terminal output, and the exit code should be 0.
Actual behaviour
The command stops with the message:
ELIFECYCLE Command failed.

With exit code 130

We decided not to do graceful shutdowns.


For Accessibility Demo Only - Do Not Merge

A spike for the accessibility demo to show how axe-core integrates into the ci/cd pipeline. Do not merge but please review positively.
Changes

work in progress code changes
axe-core in cypress

Notes

Do not merge

Good demo!


Install/Upgrade to Nuitka 8.0/8.1 fails - zip_safe missing

Attempted to upgrade to latest Nuitka and I got the  following error.

Deleted Nutika and attempted to reinstall and got the same error.

Other python libraries do not have this issue

OS: Debian 11 bullseye
Python 3.10.4
pip install -U Nuitka==0.8.1
Collecting Nuitka==0.8.1
Using cached Nuitka-0.8.1.tar.gz (3.8 MB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [10 lines of output]
/home/david/Dev/python/dev_venv3.10.4/lib/python3.10/site-packages/setuptools/_distutils/dist.py:275: UserWarning: Unknown distribution option: 'zip_safe'
warnings.warn(msg)
/home/david/Dev/python/dev_venv3.10.4/lib/python3.10/site-packages/setuptools/_distutils/dist.py:275: UserWarning: Unknown distribution option: 'entry_points'
warnings.warn(msg)
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
  error: invalid command 'egg_info'
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Whoops forgot this bit:
python -m pip freeze
appdirs==1.4.4
astroid==2.11.5
black==22.3.0
boto3-stubs==1.23.5
botocore-stubs==1.26.5
BTrees==4.10.0
certifi==2<IP_ADDRESS>
cffi==1.15.0
charset-normalizer==2.0.12
click==8.1.3
colorama==0.4.4
commonmark==0.9.1
ConfigUpdater==3.1
crypto==1.4.1
dill==<IP_ADDRESS>
dlib==19.24.99
fs==2.4.16
idna==3.3
isort==5.10.1
Jinja2==3.1.2
lazy-object-proxy==1.7.1
MarkupSafe==2.1.1
mccabe==0.7.0
memray==1.1.0
mypy==0.950
mypy-boto3-ec2==1.23.0.post1
mypy-boto3-s3==1.23.0.post1
mypy-extensions==0.4.3
Naked==0.1.31
netifaces==0.11.0
numpy==1.22.4
pathspec==0.9.0
pathvalidate==2.5.0
perfmetrics==3.2.0.post0
persistent==4.9.0
platformdirs==2.5.2
psutil==5.9.1
pycparser==2.21
pycryptodome==3.14.1
Pygments==2.12.0
pylint==2.13.9
PySide6==6.3.0
PySide6-Addons==6.3.0
PySide6-Essentials==6.3.0
pysqlite3==0.4.7
python-dateutil==2.8.2
pytz==2022.1
PyYAML==6.0
RelStorage==3.4.5
requests==2.27.1
rich==12.4.2
shellescape==3.8.1
shiboken6==6.3.0
simplejson==3.17.6
six==1.16.0
toml==0.10.2
tomli==2.0.1
transaction==3.0.1
types-backports==0.1.3
types-python-dateutil==2.8.16
types-pytz==2021.3.8
types-setuptools==57.4.15
types-simplejson==3.17.6
types-six==1.16.15
typing_extensions==4.2.0
urllib3==1.26.9
wrapt==1.14.1
xmltodict==0.13.0
zc.lockfile==2.0
ZConfig==3.6.0
ZODB==5.7.0
zodbpickle==2.3
zope.dottedname==4.3
zope.interface==5.4.0

Seems something funny has been done with setuptools to not have these option entry_points anymore. I don't think you will be able to install any version of Nuitka with it now?

The setuptools version is hidden from freeze output unfortunately, Please provide this commands output
python -c "import setuptools; print(setuptools.__version__)"

Hi Kay, as requested:
python -c "import setuptools; print(setuptools.version)"
62.3.2
I will try and install an earlier Nuitka version and let you know

And I cannot install Nuitka 7 either - which I have previously done so...so setuptools is broke I guess

In which way did you create the virtualenv there?

I don't know why the venv bit is not part of the original report.
 A  hayen@anna: ~/test$ python3 -m venv install_test
 A  hayen@anna: ~/test$ cd install_test
 A  hayen@anna: ~/test/install_test$ ls -l
total 20
drwxr-xr-x 2 hayen hayen 4096 May 25 16:03 bin
drwxr-xr-x 2 hayen hayen 4096 May 25 16:03 include
drwxr-xr-x 3 hayen hayen 4096 May 25 16:03 lib
lrwxrwxrwx 1 hayen hayen    3 May 25 16:03 lib64 -> lib
-rw-r--r-- 1 hayen hayen   69 May 25 16:03 pyvenv.cfg
drwxr-xr-x 3 hayen hayen 4096 May 25 16:03 share
 A  hayen@anna: ~/test/install_test$ . bin/activate
(install_test)  A  hayen@anna: ~/test/install_test$ python -m pip install nuitka
Collecting nuitka
  Downloading Nuitka-0.8.1.tar.gz (3.8 MB)
     |████████████████████████████████| 3.8 MB 5.3 MB/s
Using legacy 'setup.py install' for nuitka, since package 'wheel' is not installed.
Installing collected packages: nuitka
    Running setup.py install for nuitka ... done
Successfully installed nuitka-0.8.1
(install_test)  A  hayen@anna: ~/test/install_test$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

It's working just fine for me. So question becomes if anything you did install before in that venv changed setuptools for the worse.

Sorry about the venv bit Kay - kind of the background of life and I forget about it as it just works.
I downgraded setuptools to 62.3.0 and Nuitka install worked!
I upgraded to seetuptools 62.3.2 and Nuitka install failed
So I have a work around but something has changed with setuptools

And I just tried installing geonames and same behavior:
setuptools 62.3.0 works
setuptools 62.3.2 fails
The finger is really pointing at a setuptools change being root cause

It seems that setuptools-62.3.2 works fine for me. Maybe a strange case of corruption on your side.

Definitely an odd one...I will put this on the shelf until the next python release and then I will make a new venv and see if it works....

Just to close this off..I rebuilt my dev environment and the problem went away.


Fix examples of typings npm script

To pass arguments to an npm script, a -- separator is necessary.
This is resulting in incorrect bug reports on the typings project: https://github.com/typings/typings/issues/220

I've signed the CLA.

Actually, it appears that the examples were actually correct. I'd propose using the more consistent style in this PR to avoid confusion, however. Namely always putting -- after npm run typings.

Accepting this PR would not have prevented the original error that spawned the typings issue; see my comments there. The errant command would still have failed.
There is a limit to how much we can teach the community tools such as npm. That said, I think we could do better by drawing attention to the significance of the -- argument and linking to the npm guidance.
That may be how I address the problem rather than substituting one mysterious command for another.
I do appreciate the heads up, though!

@wardbell I realize that you have to balance a lot of different concerns in the Angular docs. (Great job on them, BTW.)
I do think that drawing attention to the -- and consistently using it as a separator between the npm script and all subsequent arguments would make it easier for beginners to internalize, as @blakeembrey mentioned in the typings thread.

I agree and will do

Ok ... I've thought about it more and incorporated all of these suggestions in a new PR #849.
I also incorporated it in PR #838 which is my preferred version of the QuickStart.
These typings changes will arrive in one or the other PR.
We don't need THREE PRs on this subject so I'm closing this one.  Thanks for the help.

Awesome. Thanks @wardbell!


Able to add JComponent as accordion title instead of just text.

I thought it would be nice to be able to have something more than just text as the title (a little bit like with JTabbedPane).
I also cleaned up code and formatting, added @Override annotations and such...

thanks! I will review it in the next couple of days
On 5 January 2016 at 16:06, Matthieu Labas<EMAIL_ADDRESS>wrote:

I thought it would be nice to be able to have something more than just
text as the title (a little bit like with JTabbedPane).
I also cleaned up code and formatting, added @Override
https://github.com/Override annotations and such...
You can view, comment on, or merge this pull request online at:
https://github.com/oliverwatkins/swing_library/pull/1
Commit Summary

Able to add JComponent as accordion title instead of just text.

File Changes

M src/main/java/com/gg/slider/Animation.java
https://github.com/oliverwatkins/swing_library/pull/1/files#diff-0
(33)
M src/main/java/com/gg/slider/ArrowPanel.java
https://github.com/oliverwatkins/swing_library/pull/1/files#diff-1
(24)
M src/main/java/com/gg/slider/ArrowPanel2.java
https://github.com/oliverwatkins/swing_library/pull/1/files#diff-2
(16)
M src/main/java/com/gg/slider/SideBar.java
https://github.com/oliverwatkins/swing_library/pull/1/files#diff-3
(7)
M src/main/java/com/gg/slider/SidebarAnimation.java
https://github.com/oliverwatkins/swing_library/pull/1/files#diff-4
(19)
M src/main/java/com/gg/slider/SidebarSection.java
https://github.com/oliverwatkins/swing_library/pull/1/files#diff-5
(80)
M src/main/java/com/gg/slider/SliderTester.java
https://github.com/oliverwatkins/swing_library/pull/1/files#diff-6
(21)

Patch Links:

https://github.com/oliverwatkins/swing_library/pull/1.patch
https://github.com/oliverwatkins/swing_library/pull/1.diff

—
Reply to this email directly or view it on GitHub
https://github.com/oliverwatkins/swing_library/pull/1.


Reusing faup_handler_t instance is unsafe

Reusing an instance of faup_handler_t will occasionally cause a segfault.  Specifically, using an instance faup_handler_t to parse two URLs, one after another (not simultaneously).  In my tests, this happens as frequently as once every 100 URLs parsed or as infrequently as once every 100K URLs parsed.  But it always happens eventually.
The segfault always occurs in the TLD code.  Here are two example backtraces from gdb, showing just the stack frames within libfaup:
#0  faup_tld_tree_tld_exists (Tree=, tld=, tld_len=)
at /home/jdiner/projectx/src/libfaup/src/lib/tld-tree.c:295
#1  faup_tld_tree_extract (fh=, tld_tree=)
at /home/jdiner/projectx/src/libfaup/src/lib/tld-tree.c:406
#2  0x000000000065c9cf in faup_decode (fh=0x7fb7e4070250, url=0x7fb7e4070f98 "jonbird.a4f96b687afedf2cc04075f58c4b31b93.profile.msp50.cloudfront.net",
url_len=) at /home/jdiner/projectx/src/libfaup/src/lib/decode.c:228
...
#0  faup_tld_tree_tld_exists (Tree=, tld=, tld_len=)
at /home/jdiner/projectx/src/libfaup/src/lib/tld-tree.c:295
#1  faup_tld_tree_extract (fh=, tld_tree=)
at /home/jdiner/projectx/src/libfaup/src/lib/tld-tree.c:406
#2  0x000000000065c9cf in faup_decode (fh=0x7ff800033eb0,
url=0x7ff800033f88 "jonbird.0067-0-ams3095387e7bb06d27e2c6e6134b6482f6ddf4f5cda8.beacon.rum.dynapis.info", url_len=)
at /home/jdiner/projectx/src/libfaup/src/lib/decode.c:228
...
My guess is that there is some lingering state in the faup_handler_t instance that can occasionally cause parsing of a second URL to crash.  I've worked around this by always allocating a new instance of faup_handler_t for each URL to be parsed.  But this workaround is inefficient.

Good catch! Will work on this, and provide a strong test to make sure we are good there.


[Request] Delugia Code

This is an up-to-date, better and more supported version of Cascadia Code than ryanoasis's. The repo is here https://github.com/adam7/delugia-code and downloads are here https://github.com/adam7/delugia-code/releases
For reference, Scoop already has Delugia Code.

@rashil2000 I started working on this.  I am creating each zip in the release as their own Chocolatey packages.  As new releases are published, new chocolatey packages will be pushed automatically.  Let me know if this is an acceptable approach or if you feel all of the delugia zips should be packaged as a single installable font package.

Hey, thanks for the update!
I personally prefer each zip as it's own package (offers more flexibility), but I'm not aware of how most people use it.
Feel free to publish them as you prefer 😅

@rashil2000 Wasn't sure if you saw, but all 5 Delugia fonts have been packaged and released to Chocolatey.org.

Awesome!
I have updated the upstream issue with this news :)


Alternative to dockershim in our test framework

dockershim goes away in k8s v1.24
our tests currently rely heavily on Docker and we need our testing framework to be supported to k8s v1.24 and beyond.
https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-removal-affects-you/
https://kubernetes.slack.com/archives/CCK68P2Q2/p1678375295577289

I deployed a 1.24 EKS cluster.
$ aws eks describe-cluster --name TestInfraCluster | grep version
        "version": "1.24",

I then copied the manifest for an existing prowjob from the current, production Prow cluster (running on an EKS 1.23 cluster):
wget "https://prow.ack.aws.dev/rerun?mode=original&prowjob=18c517f7-e363-11ed-9b2d-da0dd0a101b7" -O prowjob-dynamodb-e2e.yaml
Then
kubectl -n prow apply -f prowjob-dynamodb-e2e.yaml
The tests seem to have run just fine.

Yay! :) Closing...


Saving two checkpoints instead of one (+ worse BLEU)

T2T had switched from schedule train_and_evaluate to continuous_train_and_eval and since some version (I think it was v1.4.0) it saves by default two checkpoints instead of one after each 2000 steps. So by default the checkpoints are saved at steps 1, 2000, 2001, 4000, 4001, 6000, 6001 etc.
This has been reported as one of the problems in #495, but now I found even more strange observation. When evaluating each checkpoint (with t2t-bleu, i.e. independently on the internal approx_bleu evaluation), I found that the *001 checkpoints are much worse than the *000 checkpoints (except for 2000 and 2001):

I ran two experiments (with optimizer=Adafactor, warmup=8k, T2T v1.4.2, eight GPUs) which differ only in the --schedule parameter: train (gray) vs. continuous_train_and_eval (green)

Both experiments are evaluated with t2t-bleu.
For the train (gray) experiment there is a checkpoint each hour.
For the continuous_train_and_eval (green) there are two checkpoints each 2000 steps (each 45 minutes).
The train experiment does no internal evaluation, thus it is a bit faster (14560 steps in 4 hours, versus 12000 steps in 4 hours for the continuous_train_and_eval), but this is not my point now (and I choose steps instead of time for the x-axis, so the graph is not influenced by this).
Obviously, my point that the continuous_train_and_eval curve is much worse even if we ignore the sudden drop to almost zero BLEU at 6k and 8k steps.
I believe this may be related to the drops and double checkpoins reported in my previous post. I was not able to test the train_and_evaluate schedule because it fails on OOM error (which is expected, I think it needs to store two models in the memory at one time).

Wow, very odd.
My hypothesis is that it has something to do with how it goes through the data. With continuous_train_and_eval it recalls the input_fn for training each time it switches back to it. It won't see the data as evenly as schedule=train.

Now I am reading more carefully the continuous_train_and_eval documentation, which says

THIS FUNCTION IS EXPERIMENTAL.

I had thought this warning is outdated (as it is the default in T2T now)... before creating this issue.

First, the resources (e.g., memory) used by training will be released before evaluation (train_and_evaluate takes double resources).

This is great, we save memory.

Second, more checkpoints will be saved as a checkpoint is generated at the end of each training iteration.

This explains the double checkpoints are to be expected. I know when stopping the training (with whatever schedule) e.g. at step 1000 and resuming from this checkpoint, the first thing T2T does is saving checkpoint 1001. I am not sure if it actually does the one step (training one minibatch) before saving the checkpoint, or not and increasing the step count is just done to prevent overwriting the old checkpoint.

As the estimator.train starts from scratch (new graph, new states for input, etc) at each iteration, it is recommended to have the train_steps_per_iteration larger. It is also recommended to shuffle your input.

Does it mean that after each internal evaluation the training starts really from scratch, i.e. from the first minibatch? Thus effectively training only on the first 2000 minibatches all the time? I can't believe it. But if not, why they suggest to shuffle the input (after each internal evaluation)?
@rsepassi: When I resume training from a checkpoint, does the training starts from the very first training example, or does it compute the position in the data (based on global_step and batch_size and number of GPUs) where it had ended last time and continues from there?

There is no logic to keep track of where training was the last time it stopped. The input function is called from scratch again. However, I don't think it's as bad as starting from the exact same first minibatch because we do shuffle the filenames and the data as we read it.

And my guess is that 1 minibatch of training is done for step 1001. And because that minibatch may have already been seen (or at least it's not as uncorrelated as we'd like it to be) it slightly degrades performance.

I don't think it's as bad as starting from the exact same first minibatch because we do shuffle the filenames

By default there are just 100 data shards (filenames), so shuffling the filenames only would mean training on 100 * 2000 minibatches...

and the data as we read it.

... but I guess this means that it starts from a random position in the file, am I right? (I saw the code, but thought the shuffling is there only to prevent bottleneck disk access/deadlocks in distributed training.)
I guess this shuffling is influenced by the random seed and I hope the seed is not reset after each evaluation.
It is reset/fixed only when starting t2t-trainer. Thus if I kill t2t-trainer always after it saves the first checkpoint (after 2000 steps of training) and resume, I will get the problem of training on the same 2000 minibatches. Am I right?
(I just want to understand how it works. I don't say this is a bug - hopefully nobody needs to kill&resume the training so often. Personally, I use --schedule=train, so I don't care about this issue at all, I just wanted to report because most users use the default schedule.)

The error is still there in T2T 1.5.2.

I don't think it's as bad as starting from the exact same first minibatch because we do shuffle the filenames

By default there are just 100 data shards (filenames), so shuffling the filenames only would mean training on 100 * 2000 minibatches...

and the data as we read it.

... but I guess this means that it starts from a random position in the file, am I right? (I saw the code, but thought the shuffling is there only to prevent bottleneck disk access/deadlocks in distributed training.)
I guess this shuffling is influenced by the random seed and I hope the seed is not reset after each evaluation.
It is reset/fixed only when starting t2t-trainer. Thus if I kill t2t-trainer always after it saves the first checkpoint (after 2000 steps of training) and resume, I will get the problem of training on the same 2000 minibatches. Am I right?
(I just want to understand how it works. I don't say this is a bug - hopefully nobody needs to kill&resume the training so often. Personally, I use --schedule=train, so I don't care about this issue at all, I just wanted to report because most users use the default schedule.)

Hi, @martinpopel , your information is very valuable for me. As to your question here, namely does the training see only a part of whole data (of course in --schedule=continuous_train_and_eval)?
I'm also wondering it, do you have an answer now?


Missed token in codespell

https://github.com/sharkdp/bat/issues/2344#issuecomment-1264714981

Thank you for reporting this!
Can you please include a paste of the entire help message? And the version of codespell you're using? I'll probably add it as a test file.
Aside from that, this one seems pretty easy to fix. I'm trying to attract contributors during Hacktoberfest so I'm going to leave it up for a first time contributor.
I'll fix it myself if it's not done by the end of the month. Cool?

❯ codespell --version
2.2.1
❯ codespell --help
usage: codespell [-h] [--version] [-d] [-c] [-w] [-D DICTIONARY]
                 [--builtin BUILTIN-LIST] [--ignore-regex IGNORE_REGEX]
                 [-I FILE] [-L WORDS] [--uri-ignore-words-list WORDS]
                 [-r REGEX] [--uri-regex URI_REGEX] [-s] [--count] [-S SKIP]
                 [-x FILE] [-i INTERACTIVE] [-q QUIET_LEVEL] [-e] [-f] [-H]
                 [-A LINES] [-B LINES] [-C LINES] [--config CONFIG]
                 [files ...]

positional arguments:
  files                 files or directories to check

options:
  -h, --help            show this help message and exit
  --version             show program's version number and exit
  -d, --disable-colors  disable colors, even when printing to terminal (always
                        set for Windows)
  -c, --enable-colors   enable colors, even when not printing to terminal
  -w, --write-changes   write changes in place if possible
  -D DICTIONARY, --dictionary DICTIONARY
                        custom dictionary file that contains spelling
                        corrections. If this flag is not specified or equals
                        "-" then the default dictionary is used. This option
                        can be specified multiple times.
  --builtin BUILTIN-LIST
                        comma-separated list of builtin dictionaries to
                        include (when "-D -" or no "-D" is passed). Current
                        options are:
                        - 'clear' for unambiguous errors
                        - 'rare' for rare (but valid) words that are likely to
                          be errors
                        - 'informal' for making informal words more formal
                        - 'usage' for replacing phrasing with recommended
                          terms
                        - 'code' for words from code and/or mathematics that
                          are likely to be typos in other contexts (such as
                          uint)
                        - 'names' for valid proper names that might be typos
                        - 'en-GB_to_en-US' for corrections from en-GB to en-US
                        The default is 'clear,rare'.
  --ignore-regex IGNORE_REGEX
                        regular expression that is used to find patterns to
                        ignore by treating as whitespace. When writing regular
                        expressions, consider ensuring there are boundary non-
                        word chars, e.g., "\bmatch\b". Defaults to
                        empty/disabled.
  -I FILE, --ignore-words FILE
                        file that contains words that will be ignored by
                        codespell. File must contain 1 word per line. Words
                        are case sensitive based on how they are written in
                        the dictionary file
  -L WORDS, --ignore-words-list WORDS
                        comma separated list of words to be ignored by
                        codespell. Words are case sensitive based on how they
                        are written in the dictionary file
  --uri-ignore-words-list WORDS
                        comma separated list of words to be ignored by
                        codespell in URIs and emails only. Words are case
                        sensitive based on how they are written in the
                        dictionary file. If set to "*", all misspelling in
                        URIs and emails will be ignored.
  -r REGEX, --regex REGEX
                        regular expression that is used to find words. By
                        default any alphanumeric character, the underscore,
                        the hyphen, and the apostrophe is used to build words.
                        This option cannot be specified together with --write-
                        changes.
  --uri-regex URI_REGEX
                        regular expression that is used to find URIs and
                        emails. A default expression is provided.
  -s, --summary         print summary of fixes
  --count               print the number of errors as the last line of stderr
  -S SKIP, --skip SKIP  comma-separated list of files to skip. It accepts
                        globs as well. E.g.: if you want codespell to skip
                        .eps and .txt files, you'd give "*.eps,*.txt" to this
                        option.
  -x FILE, --exclude-file FILE
                        ignore whole lines that match those in the file FILE.
                        The lines in FILE should match the to-be-excluded
                        lines exactly
  -i INTERACTIVE, --interactive INTERACTIVE
                        set interactive mode when writing changes:
                        - 0: no interactivity.
                        - 1: ask for confirmation.
                        - 2: ask user to choose one fix when more than one is
                          available.
                        - 3: both 1 and 2
  -q QUIET_LEVEL, --quiet-level QUIET_LEVEL
                        bitmask that allows suppressing messages:
                        - 0: print all messages.
                        - 1: disable warnings about wrong encoding.
                        - 2: disable warnings about binary files.
                        - 4: omit warnings about automatic fixes that were
                          disabled in the dictionary.
                        - 8: don't print anything for non-automatic fixes.
                        - 16: don't print the list of fixed files.
                        As usual with bitmasks, these levels can be combined;
                        e.g. use 3 for levels 1+2, 7 for 1+2+4, 23 for
                        1+2+4+16, etc. The default mask is 2.
  -e, --hard-encoding-detection
                        use chardet to detect the encoding of each file. This
                        can slow down codespell, but is more reliable in
                        detecting encodings other than utf-8, iso8859-1, and
                        ascii.
  -f, --check-filenames
                        check file names as well
  -H, --check-hidden    check hidden files and directories (those starting
                        with ".") as well.
  -A LINES, --after-context LINES
                        print LINES of trailing context
  -B LINES, --before-context LINES
                        print LINES of leading context
  -C LINES, --context LINES
                        print LINES of surrounding context
  --config CONFIG       path to config file.

And adb --help

I think tcpip PORT, reconnect device, etc should be highlighted.

And adb --help

You're right. Although these look harder to get right.
I have an inkling on how to do this. But I can only fix this if it doesn't break other parts of the syntax (in particular: highlighting normal text, false positives).
That said, could you open a new issue for these? Same asks apply (version + full help message). The screenshot helps a lot too!
And thank you for reporting! :purple_heart: Don't hesitate to bring these issues up!


Bad path for purge CSS

I had problems with production css, probably because bad purge css path in config. I added themeDir variable and now it works.
content: [themeDir + 'layouts/**/*.html'],

Hi, could you be more specific on the system, settings and commands you used while encountering this error?

Hugo version
use of the theme starter within a theme package or directly within a hugo project
exact command to build the site
expected css and actual build css (include code snippet)

This would help to investigate this error and fix the starter theme for all use cases. Thanks

Found it. Thank you.


Refactor mesh-layers model matrix

Coverage increased (+0.3%) to 57.094% when pulling f517b24adb72d571537862f5aa6a50a3f65375ae on refact-model-matrix into 02d899511922d154783213f01e4647e07f7bc9fb on master.


[zh-cn] Sync configure-cgroup-driver.md

Sync content/zh-cn/docs/tasks/administer-cluster/kubeadm/configure-cgroup-driver.md with en page.

The weight is different too.

The weight is different too.

Thanks a lot , I have changed that weight.

/lgtm
/approve


Prometheus parse problems

I cant acess metrics from appmetrics in prometheus.
Can it be parsing error?
level=warn ts=2017-11-22T14:23:50.458732892Z caller=scrape.go:675 component="target manager" scrape_pool=appmetrics target=http://*********/metrics-text msg="append failed" err="no token found"

I seem to have the same issue. The output of the endpoint is the following (just some values replaced).
Metrics endpoint output:
`# HELP application_httprequests_apdex
TYPE application_httprequests_apdex GAUGE
application_httprequests_apdex{server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} 1
HELP application_httprequests_one_minute_error_percentage_rate
TYPE application_httprequests_one_minute_error_percentage_rate GAUGE
application_httprequests_one_minute_error_percentage_rate{server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} 100
HELP application_httprequests_one_minute_error_percentage_rate_per_endpoint
TYPE application_httprequests_one_minute_error_percentage_rate_per_endpoint GAUGE
application_httprequests_one_minute_error_percentage_rate_per_endpoint{route="GET",server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} NaN
HELP application_httprequests_active
TYPE application_httprequests_active GAUGE
application_httprequests_active{server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} 0
HELP application_httprequests_errors
TYPE application_httprequests_errors GAUGE
application_httprequests_errors{http_status_code="404",server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} 9
HELP application_httprequests_error_rate_total
TYPE application_httprequests_error_rate_total COUNTER
application_httprequests_error_rate_total{server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} 9
HELP application_httprequests_error_rate_per_endpoint_and_status_code_total
TYPE application_httprequests_error_rate_per_endpoint_and_status_code_total COUNTER
application_httprequests_error_rate_per_endpoint_and_status_code_total{route="GET",http_status_code="404",server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} 9
HELP application_httprequests_error_rate_per_endpoint_total
TYPE application_httprequests_error_rate_per_endpoint_total COUNTER
application_httprequests_error_rate_per_endpoint_total{route="GET",server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} 9
HELP application_httprequests_transactions
TYPE application_httprequests_transactions SUMMARY
application_httprequests_transactions_sum{server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} 0.17912697
application_httprequests_transactions_count{server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} 9
application_httprequests_transactions{server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild",quantile="0.5"} 0.0143838473851932
application_httprequests_transactions{server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild",quantile="0.75"} 0.012762055
application_httprequests_transactions{server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild",quantile="0.95"} 0.101100645
application_httprequests_transactions{server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild",quantile="0.99"} 0.101100645
HELP application_httprequests_transactions_per_endpoint
TYPE application_httprequests_transactions_per_endpoint SUMMARY
application_httprequests_transactions_per_endpoint_sum{route="GET",server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} 0
application_httprequests_transactions_per_endpoint_count{route="GET",server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild"} 0
application_httprequests_transactions_per_endpoint{route="GET",server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild",quantile="0.5"} 0
application_httprequests_transactions_per_endpoint{route="GET",server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild",quantile="0.75"} 0
application_httprequests_transactions_per_endpoint{route="GET",server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild",quantile="0.95"} 0
application_httprequests_transactions_per_endpoint{route="GET",server="SOME-PC",app="Some.App",env="development",HostingEnvironment="Development",ApplicationName="Some.Application",ApplicationBuild="SomeApplicationBuild",quantile="0.99"} 0`
Output of prometheus --version:
prometheus, version 2.0.0 (branch: HEAD, revision: 0a74f98628a0463dddc90528220c94de5032d1a0)
Prometheus error:
level=warn ts=2017-11-23T12:01:01.6617151Z caller=scrape.go:673 component="target manager" scrape_pool=bla target=http://localhost/metrics-text msg="append failed" err="no token found"

Should be fixed by https://github.com/AppMetrics/Prometheus/issues/20 haven't yet pushed to nuget.

Getting the same issue, is a nuget version planned soon?

@talarari Not until early in the new year unfortunately, you can reference the latest packages from myget

I already solved it in my local machine, the problem is that prometheus can't parse UpperCases so types should be change to
TYPE application_httprequests_transactions SUMMARY -> # TYPE application_httprequests_transactions summary

Seems like it is still undecided? https://github.com/prometheus/prometheus/issues/2788

I am having a similar issue when my TYPE starts with a numeric value such as "5V_PG" or "01_System_LED".  Is this expected?
Version 2.2.1
Builddate:<PHONE_NUMBER>4:15:45

@martinjt we are experiencing the same issue with our .net core app; you and @marcinbudny mention having a workaround using text formatting - can you provide more details?
We are trying to aggregate metrics in DataDog (prometheus format), setting up our output formatter this way in Startup.cs:
IMetricsRoot metricsRoot = null;
services.AddMetrics(metricsBuilder =>
{
metricsRoot = metricsBuilder.OutputMetrics.AsPrometheusPlainText().Build();
});
services.AddMetricsEndpoints(options =>
{
options.MetricsEndpointOutputFormatter = metricsRoot.OutputMetricsFormatters
.GetType();
});

I should be able to look into this one sometime over the next few days unless someone gets to it before me.
It did appear to be working for me against the latest version of prometheous with this configuration https://github.com/AppMetrics/Prometheus/blob/2.0.0/sandbox/MetricsPrometheusSandboxMvc/Host.cs#L29

What is the status of this being fixed? We are trying to use AppMetrics and Prometheus together at my job and have been waiting on this issue to be resolved to proceed.

Getting the same, and it seems to be caused by AppMetrics upper-casing the metric types.

@trondhindenes Same issue here. as of prometheus 2.4.0 uppercase metric types are no longer supported. @alhardy Can you please push the fix to nuget?


IndexedDB not working

It works with any type but IndexedDB. For instance it doesn't store anything locally.
I'm using:

OS: Ubuntu Gnome
Google Chrome: Version 49.0.2623.87 (64-bit).

It's a bit late over here, I'll take a look tomorrow to fix it.

May be I've jumped too quickly to conclusions. I've checked the indexedDB availability writing in my Chrome console with the following code:
var idbSupported = false;
document.addEventListener("DOMContentLoaded", function(){
if("indexedDB" in window) {
    idbSupported = true;
}

},false);
I attach the screenshot.
And the result is false. It seems it's not supported by my browser event though it should. That's why it's not working when I forcing through storage(readyCallback ,'IndexedDB')


make docker related targets now failing on a Mac

Bug Description
 make docker
./tools/docker
./tools/docker: line 34: out/darwin_amd64/docker-builder: cannot execute binary file: Exec format error

This was working for me last week.
Version
master branch

Additional Information
No response

Broken by https://github.com/istio/istio/pull/35965


Error log : v1720

while trying to disable / enable one click downloads
Meldii Errors make Arkii sad.txt

Huh this is an odd one, does it crash every time?

nope seems to be an initial problem.  although I can't seem to download any
add-on at all. download page opens but nothing seem to download.
unfortunately I don't get any error message.

And you are downloading with the one click buttons?
They downlaod silently in the background but you should see the addon pop up in the list if you have Meldii open or it will show up the next time you launch Meldii.
If that is not the case could you check "%localappdata%/meldii" and "%localappdata%/melder" and see if the addons zip is in there?

first i checked if "one click download" works by disable it.
if disabled, i get error message in firefox " The address wasn't understood "
if enabled i get the download page " Your addon should be downloading now :>  "
but nothing happens, addon wont be added to the list in meldii. and no zips in
"%localappdata%/meldii" or "%localappdata%/melder"
in meldii i set both paths:
D:\Steam\steamapps\common\Firefall
and
C:\Users\abc123\Documents\Firefall\Addons\
when i try with melder v1.02 i get an error#07 message
" Server failed to provide file Information "
i can download the .zip files manual and put it into the library folder and meldii will see it after restart.

The addon library folder isn't meant to be the same as the games addon folder.
Its where Meldii will store downloaded addons.
Can you try setting it back to "C:\User\abc123\AppData\Local\Melder\addons" and see if that has any effect?

it isnt the same path.

What I mean is that "C:\User\abc123\AppData\Local\Melder\addons" is the path where Firefall loads its addons from, Meldii will store the addon zips in its "Addon Libary" and copy them to that folder when you want to install them.

no changes..


Exception in CentralFreeList::RemoveRange->FetchFromSpans()

Application is link to libtcmalloc.so.4.1.0 on linux machine and compiled with gcc4.7.2
Issue has been observed only once and not reproducible.
Please let me know in case you need to debug this issue further.
Program terminated with signal 11, Segmentation fault.
#0  tcmalloc::CentralFreeList::FetchFromSpans (this=0x7f33ab381e60) at src/central_freelist.cc:298
298       span->objects = *(reinterpret_cast<void**>(result));
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.149.el6.x86_64 libgcc-4.4.7-11.el6.x86_64 nss-softokn-freebl-3.14.3-18.el6_6.x86_64
(gdb) bt
#0  tcmalloc::CentralFreeList::FetchFromSpans (this=0x7f33ab381e60) at src/central_freelist.cc:298
#1  0x00007f33ab1632f7 in tcmalloc::CentralFreeList::RemoveRange (this=0x7f33ab381e60, start=0x7f33a88b6af0, end=0x7f33a88b6af8, N=32) at src/central_freelist.cc:269
#2  0x00007f33ab166332 in tcmalloc::ThreadCache::FetchFromCentralCache (this=0x2321d40, cl=Unhandled dwarf expression opcode 0xf3) at src/thread_cache.cc:162
#3  0x00007f33ab16f255 in Allocate (old_ptr=0x9410500, new_size=104) at src/thread_cache.h:341
#4  do_malloc (old_ptr=0x9410500, new_size=104) at src/tcmalloc.cc:1068
#5  do_malloc_or_cpp_alloc (old_ptr=0x9410500, new_size=104) at src/tcmalloc.cc:1005
#6  do_realloc_with_callback (old_ptr=0x9410500, new_size=104) at src/tcmalloc.cc:1205
#7  do_realloc (old_ptr=0x9410500, new_size=104) at src/tcmalloc.cc:1228
#8  tc_realloc (old_ptr=0x9410500, new_size=104) at src/tcmalloc.cc:1526

0x19a55670:     0x000069fd
(gdb) p *span
$22 = {start = 27133, length = 1, next = 0xaf03980, prev = 0x7f33ab381ea0, objects = 0x6417e500000000, refcount = 67,
  sizeclass = 8, location = 0, sample = 0}
(gdb) p nonempty_
$23 = {start = 0, length = 0, next = 0x19a55670, prev = 0xaef91e0, objects = 0x0, refcount = 0, sizeclass = 0, location = 0,
  sample = 0}

I have used --enable-frame-pointers flag during configuration, and will not be able to provide any test program to reproduce the issue as it is a propitiatory software.

Hi. It seems inlikely that there is bug in this place of tcmalloc. Since it's code path that is hit pretty often.
I believe it is likely that something in your program has written either past allocated memory or maybe touched freed memory and thus corrupted malloc data structures. I would like to debug this more. I.e. to see if I'm right. But without far details on this issues (like test program) I don't think I can.
Consider building and running your program under address sanitizer and/or valgrind since it will help you finding any issues like that in your program.
Closing bug. But feel free to reopen if you have more data to add.


feat(RingTheory/Radical): Radical of an element in a unique factorization normalization monoid

For a unique factorization normalization monoid, define a radical of an element as a product of normalized prime factors (without duplication). This is part of our project to port Mason-Stothers Theorem in mathlib @jcpaik. You can find more theorems that will be added in future PRs here.

@jcommelin Could you check the updates? Thanks!

@jcommelin @erdOne Let me know if any updates are needed!

@seewoo5 Could you please create a follow-up PR implementing the comments by @YaelDillies ?


All services : Add support for mysql migrations in all services

Is your feature request related to a problem? Please describe.
Right now we only provide postgres migrations and it is difficult for people opting for mysql
as they have to create their own scripts to execute.
Describe the solution you'd like
A separate set of migrations for mysql database.

Services Impacted

Notification - Done
Chat - WIP
Audit
Authentication
Feature Toggle
Payment
Search
Survey
Task
User tenant
Video conferencing
Scheduler
BPMN
OIDC
In-Mail
Reporting


What is possible with AlexaPi ?

I have AlexaPi up and running, asking questions and getting a result works fine.
But what now ?
Is there anything I can connect to AlexaPi ?
Example :

a calendar to get better answers about specific dates ?
voice control commands to control Alexa enabled devices ?

you can add skills to your Alexa and use it as you want.
Let's say you have a Philips HUE; you can add the PhilipsHue skill to Alexa and when you say Alexa/ Turn lights off it will turn off the lights for you

@fourleggedostrich no
AlexaPi is using Alexa API v1 that is very limited so a lot of skills can never work on it.
I leave this issue openned to list skills that are working or not


Proof of concept - Replacing Xinput with SDL2

This pull request replaces the xinput functions with generic SDL2 ones, with the objective of allowing any controller (including xbox) to be translated to DirectInput, can be useful with Nintendo Switch/PS4/PS5 controllers.
Tested on FlatOut 2 with a DualSense PS5 controller.
Can be used with devreorder as well to hide existing directinput controllers, so only the xidi ones exist.
TODO: find a way to handle controllers connecting and disconnecting

Thanks for sharing this proof of concept! I'm glad to see that Xidi's physical controller back-end is modular (and readable) enough that it was possible to go in and change XInput to another back-end, and I'm also glad to hear that it worked.
Long term, I don't think switching from XInput to SDL2 is the right solution. I recognize that people want to use PS4/PS5/Nintendo Switch (and possibly other) controllers with Xidi, and SDL2 certainly shows some implementation techniques for how to achieve that. What I have been considering is a Xidi-specific modular back-end whose implementation can be inspired by SDL2 but does not use it directly. That makes Xidi code easier to maintain and also fully under the control of this project. I'm also wondering about the comment "TODO: find a way to handle controllers connecting and disconnecting" and, in particular, whether or not it means that the current implementation of the SDL2 breaks an existing Xidi feature that works with XInput.
Until Xidi properly supports these additional controllers, it is possible to use a project like x360ce to make non-XInput controllers available via XInput. I've used this project in the past (version 3 I believe, the one that uses custom XInput DLLs) so that my old DirectInput-only Logitech controllers would work with XInput-only games. I haven't tested this with Xidi, but in theory this should allow non-XInput controllers like Nintendo Switch and PS4/PS5 controllers to become available via XInput and thus able to be used with Xidi. (And if that doesn't currently work, I don't foresee it being too hard to fix.)
The key reason that comes to mind for not wanting to switch to SDL2 directly is that there is a maintenance burden to doing so, which is introduced because we would need to modify SDL2 code itself so that it integrates correctly with Xidi.
SDL2 itself makes calls to DirectInput, in particular by using the exact interface that the HookModule form of Xidi intercepts. So what would happen in a situation in which the HookModule form is being used is the game calls Xidi, Xidi calls its own integrated SDL2 library, the SDL2 library calls the hooked interface, that hooked interface redirects to Xidi, Xidi calls the SDL2 again, and... we get a circular dependency problem. We can't just not hook that interface because then the games wouldn't work with Xidi at all. To fix this we would need to make changes to the SDL2 code itself, and the moment we start making changes to third-party code we introduce a maintenance burden. The more invasive, low-level, and/or complex the change, the greater the burden.
Some good examples of applications and games for which this would actually be an issue are any that require the HookModule for of Xidi, and this includes emulators and other games that themselves use SDL2 for controller support.
I had the same circular dependency problem with the HookModule form of Xidi when it intercepts WinMM functions. However, in this case there is no third-party maintenance burden because the circular dependency is between the HookModule and WinMM forms of Xidi (in other words, it is between two DLLs that are both part of Xidi). To give an idea of the complexity of the fix, I ended up creating an entire API to allow the HookModule and WinMM modules to communicate so that the WinMM module would be able to access the unhooked system functions directly, even if the HookModule form had intercepted them. Some parts of the implementation are here and here.

Thanks for the feedback! I understand your concerns regarding maintenance and your reasons to not make such a switch.
I had no idea HookModule had such an impact in the aspects you've mentioned to the point of modifying the core SDL2 code to solve potential issues, SDL is a whole other beast entirely and it's probably for the best we don't mess with it.
I like the idea of a modular backend too and I'm actually working on something similiar with Xidi as well. Scripting.
I've managed to get LuaJIT working inside of Xidi but unlike this PR where it changes how the physical controller is read, instead I'm feeding the virtual DirectInput controller directly from a single .lua script (I've actually used SDL2 from lua too just for testing purposes, but it can be literally anything else instead, ex: data coming from a server...things like that)
Apologies for opening an entire PR just for this, but I've found no other way to communicate this better other than just showing the entire thing (and maybe the messy code, but then again I'm not a C/C++ developer, but hey it's just a proof of concept right? 😉).
I hope your idea of a modular backend goes forward since Xidi is the only method that works on both Windows/Linux/Wine/Proton, there are alternatives like vJoy but that is a windows system driver so that's probably not happening in other operating systems. Don't know if x360ce works though, might have to test it aswell.
A way of futureproofing Xidi whould be very appreciated because who knows what kind of crazy new controller comes out next year (but one thing's for sure SDL probably is going to support it)


Adapt servicegraph task description to istio

installation, as it already contains servicegraph by default.
Also the file install/kubernetes/addons/servicegraph.yml no longer
exists.
Co-authored-by: Holger Oehm<EMAIL_ADDRESS>

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

Needs approval from an approver in each of these files:

OWNERS

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

Hi @holgero. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Deploy preview for istio failed.
Built with commit 787eb2ed5d3761f6ef18cdfe27f16a753e2674cf
https://app.netlify.com/sites/istio/deploys/5b212104e39e7c70116ba727

Deploy preview for preliminary-istio failed.
Built with commit 787eb2ed5d3761f6ef18cdfe27f16a753e2674cf
https://app.netlify.com/sites/preliminary-istio/deploys/5b212104e39e7c70116ba725

/ok-to-test

/assign @geeknoid

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: douglas-reid, holgero
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
Assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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

Hi, I did some refactoring and the file you edited has moved in the repo. Please rebase and push again. Sorry for the inconvenience.

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: douglas-reid, holgero
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
Assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


Add profiling example for Minio to Kafka Sink

We have done them: minio-kafka and minio-kafka-exchange-pooling