Emtpy kw only dataclass has incorrect type hint for init signature

Environment data

Language Server version: 2023.2.10
OS and version: OSX 13.1
Python version (& distribution if applicable, e.g. Anaconda): miniconda python 3.10.8

Code Snippet
from dataclasses import dataclass
@dataclass(kw_only=True)
class A:
    pass
A() # shows (*args:Any,**kwargs:Any)

Screenshot

Repro Steps

Enter code above and show the type hint

Expected behavior
Typehint shows no args or kwargs, empty signature.
Actual behavior
Type hint shows any args or kwargs accepted.
Logs
Collected in empty vscode instance, by turning on trace, clearing, restarting, pasting code into unnamed file, and hovering over last line.
[Info  - 10:56:22] (13001) Pylance language server 2023.2.10 (pyright 01758105) starting
[Info  - 10:56:22] (13001) Server root directory: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist
[Info  - 10:56:22] (13001) Starting service instance "<default>"
[Info  - 10:56:22] (13001) No pyproject.toml file found.
[Info  - 10:56:22] (13001) Setting pythonPath for service "<default>": "$CONDA_PREFIX/bin/python"
[Warn  - 10:56:22] (13001) stubPath typings is not a valid directory.
[Info  - 10:56:22] (13001) Assuming Python version 3.10
[Info  - 10:56:22] (13001) Assuming Python platform Darwin
[Info  - 10:56:22] (13001) Search paths for <default>
[Info  - 10:56:22] (13001)   $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib
[Info  - 10:56:22] (13001)   .
[Info  - 10:56:22] (13001)   typings
[Info  - 10:56:22] (13001)   $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stubs/...
[Info  - 10:56:22] (13001)   $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/bundled/stubs
[Info  - 10:56:22] (13001)   $CONDA_PREFIX/lib/python3.10
[Info  - 10:56:22] (13001)   $CONDA_PREFIX/lib/python3.10/lib-dynload
[Info  - 10:56:22] (13001)   $HOME/.local/lib/python3.10/site-packages
[Info  - 10:56:22] (13001)   $CONDA_PREFIX/lib/python3.10/site-packages
[Info  - 10:56:22] (13001) Searching for source files
[Info  - 10:56:22] (13001) No source files found.
(13001) [IDX(FG)] index libraries  (index) ...
(13001) [IDX(FG)]   read stdlib indices (16ms)
(13001) [IDX(FG)] index libraries  (index) [succeed] (17ms)
[Info  - 10:56:22] (13001) No pyproject.toml file found.
[Info  - 10:56:22] (13001) Setting pythonPath for service "<default>": "$CONDA_PREFIX/bin/python"
[Warn  - 10:56:22] (13001) stubPath typings is not a valid directory.
[Info  - 10:56:22] (13001) Assuming Python version 3.10
[Info  - 10:56:22] (13001) Assuming Python platform Darwin
[Info  - 10:56:22] (13001) Search paths for <default>
[Info  - 10:56:22] (13001)   $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib
[Info  - 10:56:22] (13001)   .
[Info  - 10:56:22] (13001)   typings
[Info  - 10:56:22] (13001)   $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stubs/...
[Info  - 10:56:22] (13001)   $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/bundled/stubs
[Info  - 10:56:22] (13001)   $CONDA_PREFIX/lib/python3.10
[Info  - 10:56:22] (13001)   $CONDA_PREFIX/lib/python3.10/lib-dynload
[Info  - 10:56:22] (13001)   $HOME/.local/lib/python3.10/site-packages
[Info  - 10:56:22] (13001)   $CONDA_PREFIX/lib/python3.10/site-packages
[Info  - 10:56:22] (13001) Searching for source files
[Info  - 10:56:22] (13001) No source files found.
(13001) [IDX(FG)] index libraries  (index) ...
(13001) [IDX(FG)]   read stdlib indices (0ms)
(13001) [IDX(FG)] index libraries  (index) [succeed] (1ms)
[Info  - 10:56:22] (13001) Background analysis(1) root directory: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist
[Info  - 10:56:22] (13001) Background analysis(1) started
(13001) Background analysis message: setConfigOptions
(13001) Background analysis message: setImportResolver
(13001) Background analysis message: ensurePartialStubPackages
(13001) [FG] parsing: Untitled-1 (16ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (83ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/builtins.pyi (15ms)
(13001) [FG] binding: Untitled-1 (0ms)
(13001) Background analysis message: setTrackedFiles
(13001) Background analysis message: markAllFilesDirty
(13001) Background analysis message: setFileOpened
(13001) Background analysis message: setConfigOptions
(13001) Background analysis message: setImportResolver
(13001) Background analysis message: ensurePartialStubPackages
(13001) Background analysis message: setTrackedFiles
(13001) Background analysis message: markAllFilesDirty
(13001) Background analysis message: getSemanticTokens full
(13001) [BG(1)] getSemanticTokens full at Untitled-1 ...
(13001) [BG(1)]   parsing: Untitled-1 (17ms)
(13001) [BG(1)]   parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (84ms)
(13001) [BG(1)]   binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/builtins.pyi (17ms)
(13001) [BG(1)]   binding: Untitled-1 (0ms)
(13001) [BG(1)] getSemanticTokens full at Untitled-1 (120ms)
(13001) Background analysis message: analyze
(13001) [BG(1)] analyzing: Untitled-1 ...
(13001) [BG(1)]   checking: Untitled-1 (3ms)
(13001) [BG(1)] analyzing: Untitled-1 (3ms)
(13001) Background analysis message: resumeAnalysis
(13001) Background analysis message: setFileOpened
(13001) Background analysis message: markFilesDirty
(13001) [FG] parsing: Untitled-1 (10ms)
(13001) [FG] binding: Untitled-1 (0ms)
(13001) Background analysis message: analyze
(13001) [BG(1)] analyzing: Untitled-1 ...
(13001) [BG(1)]   parsing: Untitled-1 (9ms)
(13001) [BG(1)]   binding: Untitled-1 (0ms)
(13001) [BG(1)]   checking: Untitled-1 ...
(13001) [BG(1)]     parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing.pyi [fs read 2ms] (39ms)
(13001) [BG(1)]     binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing.pyi (3ms)
(13001) [BG(1)]     parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 0ms] (3ms)
(13001) [BG(1)]     binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing_extensions.pyi (1ms)
(13001) [BG(1)]     parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (24ms)
(13001) [BG(1)]     binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
(13001) [BG(1)]     parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/types.pyi [fs read 1ms] (10ms)
(13001) [BG(1)]     binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/types.pyi (1ms)
(13001) [BG(1)]     parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/abc.pyi [fs read 1ms] (1ms)
(13001) [BG(1)]     binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/abc.pyi (1ms)
(13001) [BG(1)]     parsing: $CONDA_PREFIX/lib/python3.10/dataclasses.py [fs read 1ms] (34ms)
(13001) [BG(1)]     binding: $CONDA_PREFIX/lib/python3.10/dataclasses.py (4ms)
(13001) [BG(1)]     parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/dataclasses.pyi [fs read 0ms] (6ms)
(13001) [BG(1)]     binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/dataclasses.pyi (1ms)
(13001) [BG(1)]     parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi [fs read 0ms] (0ms)
(13001) [BG(1)]     binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi ...
(13001) [BG(1)]       parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_collections_abc.pyi [fs read 0ms] (1ms)
(13001) [BG(1)]       binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_collections_abc.pyi (0ms)
(13001) [BG(1)]     binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi (1ms)
(13001) [BG(1)]   checking: Untitled-1 (160ms)
(13001) [BG(1)] analyzing: Untitled-1 (169ms)
(13001) Background analysis message: getDiagnosticsForRange
(13001) Background analysis message: getSemanticTokens delta
(13001) [BG(1)] getSemanticTokens delta previousResultId:1675763782447 at Untitled-1 (1ms)
(13001) Background analysis message: resumeAnalysis
(13001) Background analysis message: getDiagnosticsForRange
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing.pyi [fs read 1ms] (43ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing.pyi (3ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 1ms] (3ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/typing_extensions.pyi (2ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 0ms] (25ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/types.pyi [fs read 0ms] (8ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/types.pyi (2ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/abc.pyi [fs read 1ms] (1ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/abc.pyi (0ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/dataclasses.pyi [fs read 0ms] (5ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/dataclasses.pyi (1ms)
(13001) [FG] parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi [fs read 0ms] (0ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi ...
(13001) [FG]   parsing: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_collections_abc.pyi [fs read 0ms] (0ms)
(13001) [FG]   binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/_collections_abc.pyi (0ms)
(13001) [FG] binding: $HOME/.vscode/extensions/ms-python.vscode-pylance-2023.2.10/dist/typeshed-fallback/stdlib/collections/abc.pyi (1ms)

Thanks for the bug report. This will be fixed in an upcoming version.

This issue has been fixed in prerelease version 2023.2.21, which we've just released. You can find the changelog here: CHANGELOG.md


vimPlugins.sniprun: 1.3.9 -> 1.3.10

Description of changes
Changelog: https://github.com/michaelb/sniprun/releases/tag/v1.3.10

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 277726 run on x86_64-linux 1

1 package built:

vimPlugins.sniprun


Axis translate in local coords is broken

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Godot 0c9d20104453483fcace18bd22007c87378bd853
Issue description:

The axis translate is does not work in local coord, @n-pigeon maybe a regression of a6ff2819665b7fd1536753490f9e3f69bce8d563
Steps to reproduce:
Link to minimal example project:

Yup I know about it. It's not regression tho, it just needs to be implemented. :)
It's on my list and is next PR on my list so will fix soon. Didn't had time for coding lately.

@n-pigeon it was working some time ago, so i think its a regression.

Weird, there is no physical way I could break it. This code is well separated from each other. Each Gizmo handles math separately :B Oh welp I will fix it. How it got borked is non issue for me :)

@n-pigeon thats the attitude

@n-pigeon any news on this?

@reduz
First on my list. I will fix it this or next week. :)

Basically fixed, will submit PR soon. First I want refactor this block of code a bit so it will be more consistent.


Remove unnecessary "introduction" field from step-by-step links

Looking at a page with a step-by-step displaying, I think the title
and all the steps are used, but the introduction is not.
Unfortunately the introduction is very small, so removing it isn't a
significant saving.

Trello card

This looks to be working.  Almost all of the content on staging has been represented now, I've confirmed the introduction has been taken out of the links for check-uk-visa, and the page is still rendering fine.  No new errors in sentry, and no relevant errors in the 4xx/5xx dashboard.


Modify error handling in email otp

Modified a few private methods with context details to be used in the handleAuthErrorScenario

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Hasanthi Dissanayake seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


FRQ Practice from CollegeBoard

Blog: Link
Did digit counter for methods and control structures FRQ
Did AdditionPattern Class for Classes FRQ
Did add/remove members for ArrayList FRQ
Did zero row FRQ for 2D Arrays

Peer Review of Aarav (using AP scoring guidelines)
Methods and Control Structures FRQ: 9/9

Completes all guidelines, good job implementing the helper methods

Class FRQ: 8/9

You used public static void for the next method but it should be public void
Everything else looks good, make sure not to make this mistake and review the difference between static vs non static methods

ArrayList FRQ: 9/9

Both parts are properly done and are very similar to the scoring guidelines

2D Arrays FRQ: 9/9

Good implementation, similar to the CollegeBoard solution

Overall, your FRQs are completely done. I know that adding some of the helper methods on the last two FRQs are difficult but the testing looks good for the first two FRQs. Make sure to review the different types of methods so you don't make mistakes and don't forget to put the type when defining a variable in a for or while loop.


KAFKA-2369: Add REST API for Copycat.

@gwenshap I need to fill out some unit tests for the new functionality in the Herders, but figured you might want start taking a look at this. System test included. Note that currently it'll fail rat checks because trunk has a file missing a copyright, you can merge w/ #377 to fix that.

@gwenshap Ready for re-review. Note that the system test has uncovered a few issues which I fixed in the last couple of commits -- they are unrelated except for the fact that the REST API system test revealed them.
The only comment I don't think I directly addressed was the PUT vs POST. I can see arguments both ways, so I'm not tied to either in particular. Let me know if you'd prefer the PUT version, it should only be a couple of lines change.
I'm also aware of one other issue that can cause system test failures -- because sink tasks join their consumer group during their start(), and that start() currently occurs in the DistributedHerder's worker thread, it can cause that thread to block for long enough to miss heartbeats, then have to rejoin (which can also take awhile as other members need to heartbeat). As far as I can tell, nothing fundamentally breaks and we could probably resolve it just by increasing timeouts in the test (the failure is that some data doesn't appear downstream as quickly as we would like, but it should get there eventually once all the membership issues are worked out). However, I'd also just like to figure out how to get that work out of the DistributedHerder's thread -- invoking any 3rd party code in that thread is potentially risky. I don't think we want to roll that into this patch though.

Agree that we should prevent running 3rd party code in the DistributedHerder's worker thread. Do you want to open a JIRA so we won't lose that todo?

Yup, filed https://issues.apache.org/jira/browse/KAFKA-2713 to track it.

LGTM.
Lets leave POST / PUT as is for now, it makes sense.


Minify parity

I'll create a grunt task to concatenate and minify all the js so it's a single file, and remove the loading screen completely.

Addressed by #34


MaximumDrawdownPercentPerSecurity Looks to be MaximumUnrealizedProfitPercentPerSecurity

I was just looking at the code for
https://github.com/QuantConnect/Lean/blob/master/Algorithm.Framework/Risk/MaximumDrawdownPercentPerSecurity.py
and I may be mistaken but I think that should be renamed MinimumUnrealizedProfitPercentPerSecurity, as it doesn't seem to use drawdown. For drawdown, i think you would need to keep track of min UnrealizedLossPercent as done here:
https://github.com/IlshatGaripov/Lean/blob/c12868fa3f3c8145a752c86ebd05932adf983359/Algorithm.Framework/Risk/TrailingStopRiskManagementModel.py
Not sure if the proper correction is to rename it or implement drawdown.

Closing as doesn't seem like a bug. Implementing the drawdown percent. Happy to reopen if can explain further the issue.

Hi @jaredbroad
The main functionality is:
maximumDrawdownPercent = 0.05
pnl = security.Holdings.UnrealizedProfitPercent
            if pnl < self.maximumDrawdownPercent:
                 # liquidate
                targets.append(PortfolioTarget(security.Symbol, 0))

This script uses unrealized profit, which has as its base the purchase price. Drawdown has as its base the highest unrealized profit. This script does not keep track of nor use the the highest unrealized profit. Hopefully that clarifies.


Fix markdown crash and relative path issue

fix CodeBlock lines contain "[]" might cause crash
Add RootUrl property and convert relative Url (such as image url or link url) to absolute Url
.
And is there any need to add Two property
such as "ResurceRootUrl" and "LinkRootUrl"?
Because image's root url( https://raw.githubusercontent.com ) is not the same as link url (https://github.com)

Thanks for the contribution, I've improved on this to cover more cases + be tested in the referencing PR.


Async versions of OrderedMerge and GroupAdjacent

I really like the GroupAdjacent and OrderedMerge, as in combination they can do an ordered full join on sequences that have already been sorted by the same key, powerful for processing/updating/comparing large sorted data sets.
Great to see an async version of Merge - any interest in async versions of GroupAdjacent and OrderedMerge?

@danielearwicker, these operators exist in SuperLinq.Async, as ConcurrentMerge, GroupAdjacent, and SortedMerge. SuperLinq.Async also has most of the other operators in async version as well.

@danielearwicker OrderedMerge is implemented & maintained by @i3arnon as part of MoreAsyncLINQ. Unfortunately, looks like GroupAdjacent has been added yet (perhaps you may want to contribute there?). You could use SuperLinq that offers both, but that's a complete separate fork.

Cool, thanks for the pointers


Enable SBOM strace for jdk21u x64Linux, ppc64leLinux and aarch64Linux

Enable creating SBOM strace dependencies for Temurin builds in jdk21u x64Linux, ppc64leLinux and aarch64Linux
aarch64 needs to be throttled to 40jobs on the Adoptium 160core nodes due to resource shortage causing:
https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk22/job/jdk22-linux-aarch64-temurin/18/console
15:51:23  javacserver server process failed to initialize: No port file values materialized. Giving up after 60165 ms

run tests jdk21u


ALSA output

I see this thing is hard coded for pcm.default for the ALSA output. It would be great to have a command line option for the ALSA output. A cmd line option for the listen port would also be great. I have a few 7.1 ch sound cards in my server and have an elaborate ALSA config that busts them up into several outputs and then I run several instances of shairport-sync and each one is on it's own port and set to output to different ALSA outputs. I would love to be able to do this with AirPlay 2.

You are not the first to have a different Alsa configuration, I will add a parameter to change the default value  (pcm.default)

I'm actually not getting any output at all on a freshly loaded test machine running Debian.
This works perfect though:
speaker-test -D pcm.default -c 2 -f 44100 -F S16_LE

Do you have any error while starting the program ? I use my program on a Raspberry 1 with Raspbian. Any logs ?

I uncommented setLog() so it would output to a file but there are no errors in there. I also changed pcm.default to gibberish and it still doesn't produce any errors.

there should be some logs at startup :
goplay2 -i en0
2021/07/07 20:55:08 Device Pi: be3a23ed-3159-4336-8282-1c543ff13fc9, guid: a41f6742-7fbb-4c42-b983-6094836b5a12, Psi: 94865c70-52b3-4b05-ad72-f26d10184f57
If you do not have a similar line, there is an error in the build. If PCM.default ist not found, an error should be logged. On ArchLinux i've got an error anyway

You need to pair (iPhone in my case) and try to play to music to have the error like this one :
2021/07/07 20:06:33 request received : SETUP rtsp://<IP_ADDRESS>/6934733998229897469 body 271 at<PHONE_NUMBER>713274
2021/07/07 20:06:33 response sent : body 145 at<PHONE_NUMBER>107943
2021/07/07 20:06:33 request received : POST /audioMode body 64 at<PHONE_NUMBER>437105
2021/07/07 20:06:33 map[audioMode:default]
2021/07/07 20:06:33 response sent : body 0 at<PHONE_NUMBER>656907
ALSA lib pcm.c:2565:(snd_pcm_open_noupdate) Unknown PCM gibberish
2021/07/07 20:06:33 Audio Stream init error: could not open ALSA device gibberish

I did a ```git reset --hard`` and then rebuilt and now I am getting errors:
2021/07/07 15:10:10 Device Pi: bebf7835-08cc-43d6-bc12-bd1af42abd21, guid: 4078901e-103f-4123-9548-7b41aba8878a, Psi: 3e20f0da-c9de-484b-aafa-3410b19e8af0
2021/07/07 15:10:21 conn opened
2021/07/07 15:10:21 request received : GET /info body 70 at<PHONE_NUMBER>8
2021/07/07 15:10:21 response sent : body 415 at<PHONE_NUMBER>7
2021/07/07 15:10:21 request received : POST /pair-setup body 6 at<PHONE_NUMBER>1
2021/07/07 15:10:21 response sent : body 409 at<PHONE_NUMBER>8
2021/07/07 15:10:21 request received : POST /pair-setup body 457 at<PHONE_NUMBER>5
2021/07/07 15:10:21 response sent : body 69 at<PHONE_NUMBER>5
2021/07/07 15:10:21 request received : POST /pair-setup body 159 at<PHONE_NUMBER>2
2021/07/07 15:10:21 response sent : body 143 at<PHONE_NUMBER>7
2021/07/07 15:10:21 request received : POST /pair-verify body 37 at<PHONE_NUMBER>2
2021/07/07 15:10:21 response sent : body 140 at<PHONE_NUMBER>4
2021/07/07 15:10:21 request received : POST /pair-verify body 125 at<PHONE_NUMBER>5
2021/07/07 15:10:21 response sent : body 3 at<PHONE_NUMBER>9
2021/07/07 15:10:21 request received : POST /fp-setup body 16 at<PHONE_NUMBER>0
2021/07/07 15:10:21 response sent : body 142 at<PHONE_NUMBER>3
2021/07/07 15:10:21 request received : POST /fp-setup body 164 at<PHONE_NUMBER>8
2021/07/07 15:10:21 response sent : body 32 at<PHONE_NUMBER>8
2021/07/07 15:10:21 request received : SETUP rtsp://<IP_ADDRESS>/6148076841563931421 body 893 at<PHONE_NUMBER>0
2021/07/07 15:10:21 response sent : body 76 at<PHONE_NUMBER>3
2021/07/07 15:10:21 request received : GET /info body 0 at<PHONE_NUMBER>6
2021/07/07 15:10:21 response sent : body 415 at<PHONE_NUMBER>0
2021/07/07 15:10:21 request received : GET_PARAMETER rtsp://<IP_ADDRESS>/6148076841563931421 body 8 at<PHONE_NUMBER>4
2021/07/07 15:10:21 response sent : body 14 at<PHONE_NUMBER>4
2021/07/07 15:10:21 request received : RECORD rtsp://<IP_ADDRESS>/6148076841563931421 body 0 at<PHONE_NUMBER>9
2021/07/07 15:10:21 response sent : body 0 at<PHONE_NUMBER>4
2021/07/07 15:10:21 request received : SETPEERS rtsp://<IP_ADDRESS>/6148076841563931421 body 84 at<PHONE_NUMBER>3
2021/07/07 15:10:21 response sent : body 0 at<PHONE_NUMBER>9
2021/07/07 15:10:21 request received : POST /command body 7074 at<PHONE_NUMBER>2
2021/07/07 15:10:21 response sent : body 0 at<PHONE_NUMBER>3
2021/07/07 15:10:21 request received : SET_PARAMETER rtsp://<IP_ADDRESS>/6148076841563931421 body 20 at<PHONE_NUMBER>94551
2021/07/07 15:10:21 response sent : body 0 at<PHONE_NUMBER>38439
2021/07/07 15:10:23 request received : POST /feedback body 0 at<PHONE_NUMBER>62274
2021/07/07 15:10:23 response sent : body 0 at<PHONE_NUMBER>00201
2021/07/07 15:10:23 request received : SETUP rtsp://<IP_ADDRESS>/6148076841563931421 body 271 at<PHONE_NUMBER>92454
2021/07/07 15:10:23 response sent : body 145 at<PHONE_NUMBER>94689
2021/07/07 15:10:23 request received : POST /audioMode body 64 at<PHONE_NUMBER>49047
2021/07/07 15:10:23 map[audioMode:default]
2021/07/07 15:10:23 response sent : body 0 at<PHONE_NUMBER>42942
2021/07/07 15:10:23 Audio Stream init error: could not get periods: Invalid argument

It also terminates after the "could not get periods" error.

BTW, I am not using an RPi.. this is a full sized Intel powered machine I had laying around.

I need to look at what "could not get periods" error from alsa perspective

Nice, thanks for that cmd line arg! As for the periods error. When I searched the code I see that message is hardcoded in the goalsa package. It's not an error coming directly from ALSA so searching on that error isn't getting me very far.

I found this documentation:
https://www.alsa-project.org/alsa-doc/alsa-lib/group___p_c_m___h_w___params.html#ga7242d7045ae23a9ae736c191030c25e8
It says it returns a negative value if the configuration space does not contain a single value. So I think something is just messed up with this default alsa.conf that Debian 10 created. If I run goplay with --alsa pcm.front I get audio although it's breaking up I've made progress. I wouldn't spend anymore time on this. I will test tonight on my server at the house with a working alsa config.

From my research it seems indeed that this is a missing configuration. However, I am pretty sure goplay2 does not need this parameters anyway. I am just building goplay on a debian VM to check the issues...

Part of my confusion was that this project only supports BUFFERED and not REALTIME. I was initially testing with Spotify which is why it wasn't giving me any audio but also not returning any errors in stdout.
Thanks for your help and sorry to waste your time.

Realtime will have some issue on RTP/UDP part. This is not supported for now. I use apple music on my side.
I might try to implement REALTIME one day but for now I focus on Buffered + Apple Music.

I have reproduce the issue on debian 10

I can confirm it's working now! Thanks again!


[6.0] Fix NSDecimal interpreter test

Cherry-pick of https://github.com/swiftlang/swift/pull/75886 to release/6.0
We fixed the behavior of Decimal.ulp with https://github.com/apple/swift-foundation/pull/741. We should remove this test with wrong expectations since we already test it in SwiftFoundation
resolves: rdar://137332735

@swift-ci test


fix: Reduce padding to 5px for bounded text

fixes https://github.com/excalidraw/excalidraw/issues/4498


feat: PrivateHiddenKey

What I did

[x] _get PrivateHiddenKey
[x] _put PrivateHiddenKey (String)
[x] _delete PrivateHiddenKey

What's not done:

getBinary PrivateHiddenKey
put (byte[]) PrivateHiddenKey

closes #48

LGTM but can you explain in the PR (1) what a private hidden key is and (2) how this implementation matches the implementation in the Dart client

Ah my fault, now that I am looking at the Dart client, PrivateKeys in the Dart client are prefixed with privatekey:... my code makes the keys prefixed with _ because I thought privatekeys were the same as internal hidden keys..

Should I just close this or refactor everything to InternalKey ?
Also I've tried to create my own privatekey in my secondary manually and it would not work @gkc any idea why?
@smoothalligator@ update:privatekey:test@smoothalligator fascin
org.atsign.common.AtException: error:AT0016-Invalid key : Key privatekey:test@smoothalligator is invalid
        at org.atsign.client.api.impl.secondaries.RemoteSecondary.executeCommand(RemoteSecondary.java:102)
        at org.atsign.client.api.impl.clients.AtClientImpl.executeCommand(AtClientImpl.java:385)
        at org.atsign.client.cli.REPL.repl(REPL.java:183)
        at org.atsign.client.cli.REPL.main(REPL.java:53)
Calling System.exit

Is it because I am only allowed to read private keys and/or modify pre-existing private keys?

Please set up some time to discuss this with @murali-shris ... it's important we retain consistency on the core concepts across SDKs
at_commons has classes & methods to determine what sort of key type a key is. That is canonical, Java SDK should be exactly aligned

Start by looking at AtKey.getKeyType in at_commons

Thank you @gkc I will close for now because I do not think I did the correct approach.


Fix broken links - 2023.05

How to categorize this PR?

/area documentation
/kind enhancement
What this PR does / why we need it:
This PR fixes broken links in the documentation.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

/test pull-gardener-integration

/milestone v1.71


[exception] fn must be a function

This doesn't happen when I use 1.2.0, but 1.3.0 does, any ideas?

@9mm sorry I didn't have any time to investigate this. Does it still not work for you?

It appears to work now :+1:

@9mm How did you solved that issue ?

I honestly dont remember :( I might have just upgraded it. I believe it was a bug in the dependency and when they fixed it it just started working (bluebird)

Going to put this here for the next poor sod that runs into this issue.
The fix for me was:

Remove<EMAIL_ADDRESS>from package.json
Remove node_modules and clean npm cache

rm -rf node_modules
npm cache clean

npm i

Install react-native-fs separately (without caret)

npm i -S<EMAIL_ADDRESS>
Hope that helps 🙂


Set contents of __mod_init_func and __mod_term_func as function pointers

What is the feature you'd like to have?
To improve analyzing Mach-O's that have C++ classes, it would be great to have the function pointers typed in the  __DATA/__mod_init_func and __DATA/__mod_term_func like shown.  For mod_init_func's they are typed as void (*)(int, char **, char **, char **) in dyld and it seems like mod_term_func's have no parameters/return in dyld.

Is your feature request related to a problem?
Today this section is parsed and displayed as standard data, which isn't wrong but types could be a better default.

Are any alternative solutions acceptable?
Leaving this as is? 🤷♂
Additional Information:
Discussion in slack on this.

Duplicate of #3334


Teku crashes (json.lock already in use)

I'm running Besu/Teku in execution, consensus, and validator mode
Teku seems to crash pretty immediately.
I've tried running ./ethd terminate, then re-configuring and starting again (same result).
bash
Attaching to eth-docker_consensus_1
consensus_1       | 2022-01-24 02:18:36,387 main INFO Setting logging level to INFO
consensus_1       | 2022-01-24 02:18:37,330 main INFO Configuring logging for destination: console
consensus_1       | 2022-01-24 02:18:37,330 main INFO Logging includes events: true
consensus_1       | 2022-01-24 02:18:37,331 main INFO Logging includes validator duties: true
consensus_1       | 2022-01-24 02:18:37,337 main INFO Logging includes color: true
consensus_1       | 2022-01-24 02:18:37,363 main INFO Include P2P warnings set to: false
consensus_1       | 2022-01-24 02:18:37.365 INFO  - Teku version: teku/v22.1.0/linux-x86_64/-eclipseadoptium-openjdk64bitservervm-java-17
consensus_1       | 2022-01-24 02:18:37.376 INFO  - This software is licensed under the Apache License, Version 2.0 (the "License"); you may not use this software except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
consensus_1       | 2022-01-24 02:18:37.841 INFO  - validator-api-enabled is false, not starting rest api.
consensus_1       | 2022-01-24 02:18:37.927 INFO  - Using default implementation for ThreadExecutor
consensus_1       | 2022-01-24 02:18:37.930 INFO  - Job execution threads will use class loader of thread: main
consensus_1       | 2022-01-24 02:18:37.989 INFO  - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
consensus_1       | 2022-01-24 02:18:37.991 INFO  - Quartz Scheduler v.2.3.2 created.
consensus_1       | 2022-01-24 02:18:37.992 INFO  - RAMJobStore initialized.
consensus_1       | 2022-01-24 02:18:37.993 INFO  - Scheduler meta-data: Quartz Scheduler (v2.3.2) 'DefaultQuartzScheduler' with instanceId 'NON_CLUSTERED'
consensus_1       |   Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
consensus_1       |   NOT STARTED.
consensus_1       |   Currently in standby mode.
consensus_1       |   Number of jobs executed: 0
consensus_1       |   Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
consensus_1       |   Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
consensus_1       |
consensus_1       | 2022-01-24 02:18:37.993 INFO  - Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
consensus_1       | 2022-01-24 02:18:37.993 INFO  - Quartz scheduler version: 2.3.2
consensus_1       | 2022-01-24 02:18:38.158 INFO  - Storing beacon chain data in: /var/lib/teku/beacon
consensus_1       | 2022-01-24 02:18:38.169 INFO  - Using optimized BLST library
consensus_1       | 2022-01-24 02:18:38.182 INFO  - Starting metrics http service on <IP_ADDRESS>:8008
consensus_1       | 2022-01-24 02:18:38.190 INFO  - BLS: loaded BLST library
consensus_1       | 2022-01-24 02:18:38.202 INFO  - Loading 1 validator keys...
consensus_1       | 2022-01-24 02:18:38.510 INFO  - Beacon data directory set to: /var/lib/teku/beacon
consensus_1       | 2022-01-24 02:18:38.520 INFO  - Metrics service started and listening on 8008:8008
consensus_1       | 2022-01-24 02:18:38.626 INFO  - Created leveldb_tree Hot and Finalized database (leveldb-tree) at /var/lib/teku/beacon/db
consensus_1       | 2022-01-24 02:18:38.706 INFO  - Using execution engine at http://execution:8545
consensus_1       | 2022-01-24 02:18:38.756 INFO  - Initializing storage
consensus_1       | 2022-01-24 02:18:38.760 INFO  - Storage initialization complete
consensus_1       | 2022-01-24 02:18:38.761 INFO  - Loading initial state from https://github.com/eth-clients/merge-testnets/raw/3d07b2914747c4a8bd847a27c272e048cb2d29d8/kintsugi/genesis.ssz
consensus_1       | 2022-01-24 02:18:42.835 INFO  - Loaded initial state at epoch 0 (state root = 0x01e136a24f58dfa0c8735afdc1ccada58d286ae4e15cb26327d97f040fd8f36b, block root = 0x3bed1de741643a0c616440e7a999fc3dfbe74ba6d5c55a622dc19278e02cc771, block slot = 0).
consensus_1       | 2022-01-24 02:18:42.902 INFO  - Genesis Event ***
consensus_1       | Genesis state root: 0x01e136a24f58dfa0c8735afdc1ccada58d286ae4e15cb26327d97f040fd8f36b
consensus_1       | Genesis block root: 0x3bed1de741643a0c616440e7a999fc3dfbe74ba6d5c55a622dc19278e02cc771
consensus_1       | Genesis time: 2021-12-16 13:05:00 GMT
consensus_1       | 2022-01-24 02:18:44.609 INFO  - Generated new p2p private key and storing in: generated-node-key
consensus_1       | 2022-01-24 02:18:45.096 INFO  - PreGenesis Local ENR: enr:-KG4QL4WQJ8olI2EQQp0TBD6KW9XQePAX0Hr1G7yMI-XSpitKUQ2tBoivX1ASlTveUxoOXlsXpj7fKWDJ6GsZ-2x1xYChGV0aDKQmCTRN2AAAGn__________4JpZIJ2NIJpcIQUbaj6iXNlY3AyNTZrMaECfG9Kq9me_TPIBTBMUBtN1lV-Snh7YpSs-Tcbedik6aaDdGNwgiMog3VkcIIjKA
consensus_1       | 2022-01-24 02:18:45.112 INFO  - Using multipeer sync
consensus_1       | 2022-01-24 02:18:45.315 WARN  - JDK15 and Kotlin 1.5 break reflection in different ways - the OpenAPI plugin will not work properly. Please visit https://github.com/tipsy/javalin/issues/1193 if you want to help fix this issue.
consensus_1       | 2022-01-24 02:18:45.352 INFO  - Logging initialized @11173ms to org.eclipse.jetty.util.log.Slf4jLog
consensus_1       | 2022-01-24 02:18:45.642 INFO  - The latest finalized checkpoint at epoch 0 fell outside of the weak subjectivity period after epoch 1157, which is prior to the current epoch 8674.
consensus_1       | 2022-01-24 02:18:45.643 INFO  - The latest finalized checkpoint at epoch 0 is outside of the weak subjectivity period.  Please supply a recent weak subjectivity checkpoint using --ws-checkpoint=<BLOCK_ROOT>:<EPOCH>.
consensus_1       | 2022-01-24 02:18:45.692 INFO  - Starting libp2p network...
consensus_1       | 2022-01-24 02:18:45.709 INFO  - Starting discovery server on UDP port 9000
consensus_1       | 2022-01-24 02:18:45.711 INFO  - Listening for connections on: /ip4/<IP_ADDRESS>/tcp/9000/p2p/16Uiu2HAm3oQxiapCdorTp8C6ceWoHM9SnPzzCmuRcGgb2muMSmUq
consensus_1       | 2022-01-24 02:18:45.727 INFO  - Monitor has started. Waiting MERGE fork activation. Polling every PT14S
consensus_1       | 2022-01-24 02:18:45.728 INFO  - Starting Javalin ...
consensus_1       | 2022-01-24 02:18:45.753 INFO  - UDP discovery client started
consensus_1       | 2022-01-24 02:18:45.782 INFO  - You are running Javalin 4.1.1 (released October 10, 2021. Your Javalin version is 105 days old. Consider upgrading!).
consensus_1       | 2022-01-24 02:18:45.886 INFO  - jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 17.0.1+12
consensus_1       | 2022-01-24 02:18:45.954 INFO  - Local ENR: enr:-KG4QC1RKecSbmiAwVRdodf4rR744WhLTHcvN1jXupWYQz77SjW9_Aw115xncP4uvl3tpGUCEwFYG_hm3b0RJyZz2MkDhGV0aDKQ7nHpc2IAAHH__________4JpZIJ2NIJpcIQUbaj6iXNlY3AyNTZrMaECfG9Kq9me_TPIBTBMUBtN1lV-Snh7YpSs-Tcbedik6aaDdGNwgiMog3VkcIIjKA
consensus_1       | 2022-01-24 02:18:46.105 INFO  - Started<EMAIL_ADDRESS>(http/1.1)}{<IP_ADDRESS>:5052}
consensus_1       | 2022-01-24 02:18:46.105 INFO  - Started @11928ms
consensus_1       | 2022-01-24 02:18:46.106 INFO  - Listening on http://localhost:5052/
consensus_1       | 2022-01-24 02:18:46.106 INFO  - Javalin started in 378ms \o/
consensus_1       | 2022-01-24 02:18:46.110 FATAL - Keystore file /keys/0x8aedb6edd6a724878e164fa56236d2269e1842de3e0fbad0aa572901eaf9dc9cc37ca35222edb4ed3b00ff65ade407e2.json.lock already in use.
consensus_1       | tech.pegasys.teku.infrastructure.exceptions.InvalidConfigurationException: Keystore file /keys/0x8aedb6edd6a724878e164fa56236d2269e1842de3e0fbad0aa572901eaf9dc9cc37ca35222edb4ed3b00ff65ade407e2.json.lock already in use.
consensus_1       | at tech.pegasys.teku.validator.client.loader.KeystoreLocker.keystoreInUseException(KeystoreLocker.java:85) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.KeystoreLocker.attemptReplaceStaleLockFile(KeystoreLocker.java:68) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.KeystoreLocker.lockKeystore(KeystoreLocker.java:43) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.LocalValidatorSource$LocalValidatorProvider.loadBLSPrivateKey(LocalValidatorSource.java:267) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.LocalValidatorSource$LocalValidatorProvider.createSigner(LocalValidatorSource.java:254) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.SlashingProtectedValidatorSource$SlashingProtectedValidatorProvider.createSigner(SlashingProtectedValidatorSource.java:92) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.MultithreadedValidatorLoader.lambda$loadValidators$0(MultithreadedValidatorLoader.java:64) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:?]
consensus_1       | at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
consensus_1       | at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
consensus_1       | at java.lang.Thread.run(Unknown Source) ~[?:?]
consensus_1       | Keystore file /keys/0x8aedb6edd6a724878e164fa56236d2269e1842de3e0fbad0aa572901eaf9dc9cc37ca35222edb4ed3b00ff65ade407e2.json.lock already in use.
consensus_1       |
consensus_1       | To display full help:
consensus_1       | teku [COMMAND] --help
consensus_1       | 2022-01-24 02:18:51,478 main INFO Setting logging level to INFO
consensus_1       | 2022-01-24 02:18:52,631 main INFO Configuring logging for destination: console
consensus_1       | 2022-01-24 02:18:52,636 main INFO Logging includes events: true
consensus_1       | 2022-01-24 02:18:52,636 main INFO Logging includes validator duties: true
consensus_1       | 2022-01-24 02:18:52,636 main INFO Logging includes color: true
consensus_1       | 2022-01-24 02:18:52,668 main INFO Include P2P warnings set to: false
consensus_1       | 2022-01-24 02:18:52.670 INFO  - Teku version: teku/v22.1.0/linux-x86_64/-eclipseadoptium-openjdk64bitservervm-java-17
consensus_1       | 2022-01-24 02:18:52.674 INFO  - This software is licensed under the Apache License, Version 2.0 (the "License"); you may not use this software except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
consensus_1       | 2022-01-24 02:18:53.246 INFO  - validator-api-enabled is false, not starting rest api.
consensus_1       | 2022-01-24 02:18:53.362 INFO  - Using default implementation for ThreadExecutor
consensus_1       | 2022-01-24 02:18:53.369 INFO  - Job execution threads will use class loader of thread: main
consensus_1       | 2022-01-24 02:18:53.453 INFO  - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
consensus_1       | 2022-01-24 02:18:53.453 INFO  - Quartz Scheduler v.2.3.2 created.
consensus_1       | 2022-01-24 02:18:53.454 INFO  - RAMJobStore initialized.
consensus_1       | 2022-01-24 02:18:53.454 INFO  - Scheduler meta-data: Quartz Scheduler (v2.3.2) 'DefaultQuartzScheduler' with instanceId 'NON_CLUSTERED'
consensus_1       |   Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
consensus_1       |   NOT STARTED.
consensus_1       |   Currently in standby mode.
consensus_1       |   Number of jobs executed: 0
consensus_1       |   Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
consensus_1       |   Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
consensus_1       |
consensus_1       | 2022-01-24 02:18:53.455 INFO  - Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
consensus_1       | 2022-01-24 02:18:53.455 INFO  - Quartz scheduler version: 2.3.2
consensus_1       | 2022-01-24 02:18:53.565 INFO  - Using optimized BLST library
consensus_1       | 2022-01-24 02:18:53.574 INFO  - BLS: loaded BLST library
consensus_1       | 2022-01-24 02:18:53.594 INFO  - Storing beacon chain data in: /var/lib/teku/beacon
consensus_1       | 2022-01-24 02:18:53.594 INFO  - Starting metrics http service on <IP_ADDRESS>:8008
consensus_1       | 2022-01-24 02:18:53.596 INFO  - Loading 1 validator keys...
consensus_1       | 2022-01-24 02:18:53.892 INFO  - Metrics service started and listening on 8008:8008
consensus_1       | 2022-01-24 02:18:53.895 INFO  - Beacon data directory set to: /var/lib/teku/beacon
consensus_1       | 2022-01-24 02:18:53.966 INFO  - Created leveldb_tree Hot and Finalized database (leveldb-tree) at /var/lib/teku/beacon/db
consensus_1       | 2022-01-24 02:18:54.037 INFO  - Using execution engine at http://execution:8545
consensus_1       | 2022-01-24 02:18:54.087 INFO  - Initializing storage
consensus_1       | 2022-01-24 02:18:56.621 INFO  - Storage initialization complete
consensus_1       | 2022-01-24 02:18:57.692 INFO  - Loading generated p2p private key from: generated-node-key
consensus_1       | 2022-01-24 02:18:58.285 INFO  - PreGenesis Local ENR: enr:-KG4QM6ovWK403UhV216YhgmcluN9NqIgdtkBMByJ-mFJkPLc1Rvs79NSjClGx74HZQzv0e_uAjjjJQIcFoh4adU228FhGV0aDKQmCTRN2AAAGn__________4JpZIJ2NIJpcIQUbaj6iXNlY3AyNTZrMaECfG9Kq9me_TPIBTBMUBtN1lV-Snh7YpSs-Tcbedik6aaDdGNwgiMog3VkcIIjKA
consensus_1       | 2022-01-24 02:18:58.291 INFO  - Using multipeer sync
consensus_1       | 2022-01-24 02:18:58.432 WARN  - JDK15 and Kotlin 1.5 break reflection in different ways - the OpenAPI plugin will not work properly. Please visit https://github.com/tipsy/javalin/issues/1193 if you want to help fix this issue.
consensus_1       | 2022-01-24 02:18:58.476 INFO  - Logging initialized @10279ms to org.eclipse.jetty.util.log.Slf4jLog
consensus_1       | 2022-01-24 02:18:58.665 INFO  - The latest finalized checkpoint at epoch 0 fell outside of the weak subjectivity period after epoch 1157, which is prior to the current epoch 8674.
consensus_1       | 2022-01-24 02:18:58.665 INFO  - The latest finalized checkpoint at epoch 0 is outside of the weak subjectivity period.  Please supply a recent weak subjectivity checkpoint using --ws-checkpoint=<BLOCK_ROOT>:<EPOCH>.
consensus_1       | 2022-01-24 02:18:58.713 INFO  - Starting libp2p network...
consensus_1       | 2022-01-24 02:18:58.724 INFO  - Listening for connections on: /ip4/<IP_ADDRESS>/tcp/9000/p2p/16Uiu2HAm3oQxiapCdorTp8C6ceWoHM9SnPzzCmuRcGgb2muMSmUq
consensus_1       | 2022-01-24 02:18:58.729 INFO  - Starting discovery server on UDP port 9000
consensus_1       | 2022-01-24 02:18:58.750 INFO  - Monitor has started. Waiting MERGE fork activation. Polling every PT14S
consensus_1       | 2022-01-24 02:18:58.763 INFO  - UDP discovery client started
consensus_1       | 2022-01-24 02:18:58.764 INFO  - Starting Javalin ...
consensus_1       | 2022-01-24 02:18:58.797 INFO  - You are running Javalin 4.1.1 (released October 10, 2021. Your Javalin version is 105 days old. Consider upgrading!).
consensus_1       | 2022-01-24 02:18:58.890 INFO  - jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 17.0.1+12
consensus_1       | 2022-01-24 02:18:58.925 INFO  - Local ENR: enr:-KG4QG5QP0c22khwuP5l527rdA7k4F8DOTmEvBkU7vKEZbPcYVCHQ_KSUzvzBeg3kgG0IBsfsxXQEWmUI9uLzpekNqQGhGV0aDKQ7nHpc2IAAHH__________4JpZIJ2NIJpcIQUbaj6iXNlY3AyNTZrMaECfG9Kq9me_TPIBTBMUBtN1lV-Snh7YpSs-Tcbedik6aaDdGNwgiMog3VkcIIjKA
consensus_1       | 2022-01-24 02:18:59.245 INFO  - Started<EMAIL_ADDRESS>(http/1.1)}{<IP_ADDRESS>:5052}
consensus_1       | 2022-01-24 02:18:59.245 INFO  - Started @11054ms
consensus_1       | 2022-01-24 02:18:59.246 INFO  - Listening on http://localhost:5052/
consensus_1       | 2022-01-24 02:18:59.246 INFO  - Javalin started in 482ms \o/
consensus_1       | 2022-01-24 02:18:59.254 FATAL - Keystore file /keys/0x8aedb6edd6a724878e164fa56236d2269e1842de3e0fbad0aa572901eaf9dc9cc37ca35222edb4ed3b00ff65ade407e2.json.lock already in use.
consensus_1       | tech.pegasys.teku.infrastructure.exceptions.InvalidConfigurationException: Keystore file /keys/0x8aedb6edd6a724878e164fa56236d2269e1842de3e0fbad0aa572901eaf9dc9cc37ca35222edb4ed3b00ff65ade407e2.json.lock already in use.
consensus_1       | at tech.pegasys.teku.validator.client.loader.KeystoreLocker.keystoreInUseException(KeystoreLocker.java:85) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.KeystoreLocker.attemptReplaceStaleLockFile(KeystoreLocker.java:68) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.KeystoreLocker.lockKeystore(KeystoreLocker.java:43) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.LocalValidatorSource$LocalValidatorProvider.loadBLSPrivateKey(LocalValidatorSource.java:267) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.LocalValidatorSource$LocalValidatorProvider.createSigner(LocalValidatorSource.java:254) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.SlashingProtectedValidatorSource$SlashingProtectedValidatorProvider.createSigner(SlashingProtectedValidatorSource.java:92) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.MultithreadedValidatorLoader.lambda$loadValidators$0(MultithreadedValidatorLoader.java:64) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:?]
consensus_1       | at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
consensus_1       | at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
consensus_1       | at java.lang.Thread.run(Unknown Source) ~[?:?]
consensus_1       | Keystore file /keys/0x8aedb6edd6a724878e164fa56236d2269e1842de3e0fbad0aa572901eaf9dc9cc37ca35222edb4ed3b00ff65ade407e2.json.lock already in use.
consensus_1       |
consensus_1       | To display full help:
consensus_1       | teku [COMMAND] --help
consensus_1       | 2022-01-24 02:19:05,199 main INFO Setting logging level to INFO
consensus_1       | 2022-01-24 02:19:06,185 main INFO Configuring logging for destination: console
consensus_1       | 2022-01-24 02:19:06,186 main INFO Logging includes events: true
consensus_1       | 2022-01-24 02:19:06,186 main INFO Logging includes validator duties: true
consensus_1       | 2022-01-24 02:19:06,186 main INFO Logging includes color: true
consensus_1       | 2022-01-24 02:19:06,213 main INFO Include P2P warnings set to: false
consensus_1       | 2022-01-24 02:19:06.216 INFO  - Teku version: teku/v22.1.0/linux-x86_64/-eclipseadoptium-openjdk64bitservervm-java-17
consensus_1       | 2022-01-24 02:19:06.223 INFO  - This software is licensed under the Apache License, Version 2.0 (the "License"); you may not use this software except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
consensus_1       | 2022-01-24 02:19:06.676 INFO  - validator-api-enabled is false, not starting rest api.
consensus_1       | 2022-01-24 02:19:06.785 INFO  - Using default implementation for ThreadExecutor
consensus_1       | 2022-01-24 02:19:06.786 INFO  - Job execution threads will use class loader of thread: main
consensus_1       | 2022-01-24 02:19:06.833 INFO  - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
consensus_1       | 2022-01-24 02:19:06.833 INFO  - Quartz Scheduler v.2.3.2 created.
consensus_1       | 2022-01-24 02:19:06.834 INFO  - RAMJobStore initialized.
consensus_1       | 2022-01-24 02:19:06.843 INFO  - Scheduler meta-data: Quartz Scheduler (v2.3.2) 'DefaultQuartzScheduler' with instanceId 'NON_CLUSTERED'
consensus_1       |   Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
consensus_1       |   NOT STARTED.
consensus_1       |   Currently in standby mode.
consensus_1       |   Number of jobs executed: 0
consensus_1       |   Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
consensus_1       |   Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
consensus_1       |
consensus_1       | 2022-01-24 02:19:06.843 INFO  - Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
consensus_1       | 2022-01-24 02:19:06.843 INFO  - Quartz scheduler version: 2.3.2
consensus_1       | 2022-01-24 02:19:06.986 INFO  - Using optimized BLST library
consensus_1       | 2022-01-24 02:19:06.989 INFO  - Storing beacon chain data in: /var/lib/teku/beacon
consensus_1       | 2022-01-24 02:19:07.011 INFO  - Starting metrics http service on <IP_ADDRESS>:8008
consensus_1       | 2022-01-24 02:19:07.024 INFO  - BLS: loaded BLST library
consensus_1       | 2022-01-24 02:19:07.027 INFO  - Loading 1 validator keys...
consensus_1       | 2022-01-24 02:19:07.312 INFO  - Metrics service started and listening on 8008:8008
consensus_1       | 2022-01-24 02:19:07.315 INFO  - Beacon data directory set to: /var/lib/teku/beacon
consensus_1       | 2022-01-24 02:19:07.399 INFO  - Created leveldb_tree Hot and Finalized database (leveldb-tree) at /var/lib/teku/beacon/db
consensus_1       | 2022-01-24 02:19:07.477 INFO  - Using execution engine at http://execution:8545
consensus_1       | 2022-01-24 02:19:07.544 INFO  - Initializing storage
consensus_1       | 2022-01-24 02:19:10.744 INFO  - Storage initialization complete
consensus_1       | 2022-01-24 02:19:11.789 INFO  - Loading generated p2p private key from: generated-node-key
consensus_1       | 2022-01-24 02:19:12.316 INFO  - PreGenesis Local ENR: enr:-KG4QNevwhBk_piRfa_eF95p12LOvZ9H7Sf3I7iP_i05M5MEPBsv0eb37kAYTKdUQXs5mG3WEfnV-MYZT5Z75FUQvsgIhGV0aDKQmCTRN2AAAGn__________4JpZIJ2NIJpcIQUbaj6iXNlY3AyNTZrMaECfG9Kq9me_TPIBTBMUBtN1lV-Snh7YpSs-Tcbedik6aaDdGNwgiMog3VkcIIjKA
consensus_1       | 2022-01-24 02:19:12.323 INFO  - Using multipeer sync
consensus_1       | 2022-01-24 02:19:12.489 WARN  - JDK15 and Kotlin 1.5 break reflection in different ways - the OpenAPI plugin will not work properly. Please visit https://github.com/tipsy/javalin/issues/1193 if you want to help fix this issue.
consensus_1       | 2022-01-24 02:19:12.539 INFO  - Logging initialized @10531ms to org.eclipse.jetty.util.log.Slf4jLog
consensus_1       | 2022-01-24 02:19:12.761 INFO  - The latest finalized checkpoint at epoch 0 fell outside of the weak subjectivity period after epoch 1157, which is prior to the current epoch 8674.
consensus_1       | 2022-01-24 02:19:12.763 INFO  - The latest finalized checkpoint at epoch 0 is outside of the weak subjectivity period.  Please supply a recent weak subjectivity checkpoint using --ws-checkpoint=<BLOCK_ROOT>:<EPOCH>.
consensus_1       | 2022-01-24 02:19:12.816 INFO  - Starting libp2p network...
consensus_1       | 2022-01-24 02:19:12.831 INFO  - Listening for connections on: /ip4/<IP_ADDRESS>/tcp/9000/p2p/16Uiu2HAm3oQxiapCdorTp8C6ceWoHM9SnPzzCmuRcGgb2muMSmUq
consensus_1       | 2022-01-24 02:19:12.836 INFO  - Starting discovery server on UDP port 9000
consensus_1       | 2022-01-24 02:19:12.854 INFO  - Monitor has started. Waiting MERGE fork activation. Polling every PT14S
consensus_1       | 2022-01-24 02:19:12.856 INFO  - Starting Javalin ...
consensus_1       | 2022-01-24 02:19:12.872 INFO  - UDP discovery client started
consensus_1       | 2022-01-24 02:19:12.907 INFO  - You are running Javalin 4.1.1 (released October 10, 2021. Your Javalin version is 105 days old. Consider upgrading!).
consensus_1       | 2022-01-24 02:19:12.990 INFO  - jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 17.0.1+12
consensus_1       | 2022-01-24 02:19:13.038 INFO  - Local ENR: enr:-KG4QOuwLq2mn0TUCgnnzUzRiW8J3XvYwTyseZwdwRPW6bJAVNM9tBJK5Xs6KUcBuaraQ7Q6ppqmuxM4_-78Rl5HAfEJhGV0aDKQ7nHpc2IAAHH__________4JpZIJ2NIJpcIQUbaj6iXNlY3AyNTZrMaECfG9Kq9me_TPIBTBMUBtN1lV-Snh7YpSs-Tcbedik6aaDdGNwgiMog3VkcIIjKA
consensus_1       | 2022-01-24 02:19:13.375 INFO  - Started<EMAIL_ADDRESS>(http/1.1)}{<IP_ADDRESS>:5052}
consensus_1       | 2022-01-24 02:19:13.375 INFO  - Started @11368ms
consensus_1       | 2022-01-24 02:19:13.376 INFO  - Listening on http://localhost:5052/
consensus_1       | 2022-01-24 02:19:13.376 INFO  - Javalin started in 520ms \o/
consensus_1       | 2022-01-24 02:19:13.379 FATAL - Keystore file /keys/0x8aedb6edd6a724878e164fa56236d2269e1842de3e0fbad0aa572901eaf9dc9cc37ca35222edb4ed3b00ff65ade407e2.json.lock already in use.
consensus_1       | tech.pegasys.teku.infrastructure.exceptions.InvalidConfigurationException: Keystore file /keys/0x8aedb6edd6a724878e164fa56236d2269e1842de3e0fbad0aa572901eaf9dc9cc37ca35222edb4ed3b00ff65ade407e2.json.lock already in use.
consensus_1       | at tech.pegasys.teku.validator.client.loader.KeystoreLocker.keystoreInUseException(KeystoreLocker.java:85) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.KeystoreLocker.attemptReplaceStaleLockFile(KeystoreLocker.java:68) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.KeystoreLocker.lockKeystore(KeystoreLocker.java:43) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.LocalValidatorSource$LocalValidatorProvider.loadBLSPrivateKey(LocalValidatorSource.java:267) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.LocalValidatorSource$LocalValidatorProvider.createSigner(LocalValidatorSource.java:254) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.SlashingProtectedValidatorSource$SlashingProtectedValidatorProvider.createSigner(SlashingProtectedValidatorSource.java:92) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at tech.pegasys.teku.validator.client.loader.MultithreadedValidatorLoader.lambda$loadValidators$0(MultithreadedValidatorLoader.java:64) ~[teku-validator-client-22.1.0.jar:22.1.0]
consensus_1       | at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:?]
consensus_1       | at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
consensus_1       | at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
consensus_1       | at java.lang.Thread.run(Unknown Source) ~[?:?]
consensus_1       | Keystore file /keys/0x8aedb6edd6a724878e164fa56236d2269e1842de3e0fbad0aa572901eaf9dc9cc37ca35222edb4ed3b00ff65ade407e2.json.lock already in use.
consensus_1       |
consensus_1       | To display full help:
consensus_1       | teku [COMMAND] --help
luis@kintsugi-vm:~/eth-docker$

Interesting. Say more please. What environment is this running in? What's the OS? Is there any NFS/EFS storage behind the docker volumes, or is it all local-attached?

That might do it, docker isn’t friendly to symlinks. Try removing docker volumes - you’ll have to reimport keys - remove the symlinks and tell docker that its root is now on the new drive. That’s in a config file and can be googled. From there you are hopefully golden.


Update xip.io to sslip.io

With xip.io no longer available, we'll start using sslip.io.
Note: There will be no migration for anyone using xip.io.

On rancher 2.6.0-rc3 UI - "Automatically generate a .sslip.io hostname" is seen when creating an ingress.


Does not seem to work with react-router

When following the set up instructions provided in the README this tool breaks the application if the app has react-router-dom. Currently using react-router-dom v5.1.2.
I see this error when attempting to include in my project.

Seems like acorn is choking on something in router... I am unsure if acorn was pulled in as a dependency of reactime or another one of the packages i have in my project... regardless, when i comment out the router code reactime works, when i have it in the code it breaks.

Thank you for reporting this, since this was missed in our original testing, to clarify, did your React router crash on runtime or only after clicking on your Components?

I also hit this error, the app crashes immediately before any user interaction.

Hi @josiahgallen, @mikestaub
We just released Reactime 3.0 which supports React Router. Update both the npm package and Chrome extension and let me know if it works for you.


Few minor changes.

Updated a spelling issue and added an additional line to the description.

Thanks for correcting typos.


nodeSelector configurable over virt-operator

Signed-off-by: Marcin Franczyk<EMAIL_ADDRESS>
What this PR does / why we need it:
It allows to set nodeSelector field for VMIs over virt-operator by setting a NODE_SELECTOR env, as example:
NODE_SELECTOR="system-os_release.ID=centos"
or
NODE_SELECTOR="system-os_release.ID=centos,system-os_release.MAJOR_VERSION=7"
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Special notes for  your reviewer:
Next things to do:

[x] add tests

Release note:

Limit VMIs to specific nodes

@rmohr, @slintes this PR is still in progress (missing tests), however, I would like you to check if this implementation makes sense. Thanks.

Ok, fine with me, it means virt-controller during render will take nodeSelector from kubevirt-config configMap and there is no need to change virt-operator.

@davidvossel done, node selectors read from configMap, if selector is invalid VMI will not start.


remove mantid from dependency

fixes #86

Coverage remained the same at 87.791% when pulling 7f771af48c04c03afed5107fd984c00fc09b9343 on 86-rm-mantid-dep into 61dd792aa3695281240abf51e9151a308e86163c on master.

Coverage remained the same at 87.791% when pulling 7f771af48c04c03afed5107fd984c00fc09b9343 on 86-rm-mantid-dep into 61dd792aa3695281240abf51e9151a308e86163c on master.

Coverage remained the same at 87.791% when pulling 7f771af48c04c03afed5107fd984c00fc09b9343 on 86-rm-mantid-dep into 61dd792aa3695281240abf51e9151a308e86163c on master.


Include 'inject: false,' configuration flag

Your example should include and highlight that you need to add the inject:false, configuration option.
If you don't asset references are added twice to the resulting html file.
Once based on the template, and an additional time because they are injected.

Added to README.  Closing.


Fix segfault in case of adding resources dynamically

Resource(s) Added Events (see
https://github.com/AMWA-TV/nmos-discovery-registration/blob/v1.2/docs/4.2. Behaviour - Querying.md)
only have a post field but no pre field. Hence, the condition for creation was erroneous and
the segfault occurred when we accessed the pre field without checking for existence.

Many thanks for the clear report and patch. I would like to add a few additional comments to the patched code and will then merge.

Sure!


Move compile on save to ide key

TL;DR: Provide a way to disable the build part of atom-typescript but retain the IDE features (auto-complete, syntax highlighting, etc.)
I have a project that leverages a number of technologies that require a build step.  I am using gulp as my build system.  I would like to be able to use atom-typescript, but I do not want it to be building things for me, I just want it for the IDE features.
From what I can tell, there isn't a way that I can disable the build-system features of atom-typescript while retaining the rest of the features.  gulp-typescript uses tsconfig.json, so as long as atom-typescript continues to use tsconfig.json for its configuration then everything should stay in sync.
The reason auto-compilation is a problem is because my build system does more than a default TypeScript compile.  After the typescript files are built, they need to be processed and put in the correct location.  atom-typescript is currently creating intermediate files that should not exist for longer than it takes to run a build.
Also, atom-typescript doesn't support rootDir yet, though I imagine this is a temporary problem.

I just found out about: https://github.com/TypeStrong/atom-typescript/blob/master/docs/faq.md#i-dont-want-atom-typescript-compiling-my-js
This is a workaround for now, however I may have other tools that I do want to compile-on-save.  In general, I think it is a bad idea to combine atom-typescript configuration with general typescript configuration.  The same goes for filesGlob, this should go in an atom-typescript file or nested inside an atom-typescript object in the tsconfig.json.  In the case of the latter, there should be a standard way of extending tsconfig.json that various IDEs can leverage when they want to add their own IDE-specific (non-standard) options such that they don't collide with other tools.

that various IDEs can leverage when they want to add their own IDE-specific (non-standard) options such that they don't collide with other tools.

Agreed. We should move compileOnSave under an ide key.

Is there be a situation where you would not want Visual Studio or IntelliJ to compile on save but you would want atom to compile on save?
If the answer to the above question is yes, then I believe this should be put into an atom or atom-typescript key.  If no one can come up with a reason why you wouldn't want the rule to apply across IDEs then I think ide is a good key name.
If it is going to end up in a general ide key, it may be a good idea to get feedback from the community (outside of atom-typescript) on this to better coordinate with other IDEs on the matter, to avoid having to change again if Visual Studio or IntelliJ decide to do something similar but under a different key.

If it is going to end up in a general ide key, it may be a good idea to get feedback from the community (outside of atom-typescript) on this to better coordinate with other IDEs on the matter

We did discuss it : https://github.com/Microsoft/TypeScript/issues/2326 I just left another comment https://github.com/Microsoft/TypeScript/issues/2326#issuecomment-98620293


Latest Everycompat crash

Mod Name
Everycompat
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/every-compat
Minecraft version
1.20.1
Describe the bug
Crash with latest Everycompat update
Steps to reproduce

...
Logs
https://mclo.gs/X54rJwM
Additional context
No response

I've downloaded everycompat and it runs fine on its own. You log mentions you have a lot of other mods installed, so it's hard to determine the real cause of the crash.
Please read the issue template more carefully. For modpack related issues, use the support channel on our discord server.

Before reporting, please ensure that:

You've installed a minimal set of mods required to reproduce the issue.
Issues with modpacks and excessive amount of mods will not be accepted, as they take a long time to diagnose.
Knowing which mods are causing problems allows us to focus on fixing the issue as soon as possible.
If you're unsure which mods might be at fault, try using binary search - removing half of installed mods
repeatedly until the faulty mod is found.


CO-1884 Delete nesting when Group is deleted

Change is on line 44.

@boshrin I re-committed this without the whitespace changes.  Thanks!


Come up with a draft ordering of the exercises in xJava

I'm gonna share my ongoing thoughts, here, as I continue through the track.

(as I've said in another ticket) Gigasecond seems trivial in the Java track.

binary and roman-numeral are very similar kinds of problems.  In fact, I feel like roman-numeral is a fun revisit of binary with some twists.

@jtigger did you see the comment I made on this?  It seems to be gone...?

@matthewmorgan I saw it.  That was on a separate issue: #143

I'm losing it!  thanks :)

...wait... you had it? ;)

@exercism/java: the track is about to pick-up this work in earnest.
I've found that taking the time to understand why we're doing a work yields higher quality outcomes.
Please take a moment to consider and share your thoughts: why does the Java track of Exercism exist?  What purpose does it serve?  Whom does it serve?

@exercism/java I've created a spreadsheet for us to collect our assessments https://docs.google.com/spreadsheets/d/15UbVn4cBUxI7tekKmNNls9dXsT1rDhtG7Z8lp1nmjlM/edit
Please fill-out the sheet according to your assessment:

share your thoughts in the Notes tab;
name the topics invoked by the exercise in the Topics tab;
estimate the difficulty of the exercise in Difficulty tab.

You might find #134 inspiring.
Thanks!

Will take a crack at this over the holidays :)

FWIW, I've started to settle on an "intrinsic complexity" measure.  I see two primary sources of complexity:

that arising from required interfaces (i.e. methods and data structures)
that arising from required behavior (i.e. operations)

I'm capturing this in another tab in the spreadsheet.  If you're interested, take a look. I figure behavior complexity has more of an impact than interface complexity on how hard the problem is, so I put a coefficient in front of them.  I'll sort by that complexity rating and see what I get!
Very interested in how others are tackling this problem (of identifying order of exercises).

Please signal here when you've add your input.

I've added difficulty rankings based on manual inspection of the problem descriptions and test suites. They align fairly well with @jtigger's rankings! I probably won't have time to get to the topics list any time soon - busy times ahead.

Yeah, thankfully we're not worlds apart! :)  I've tossed some stats over the current rankings.  For those who haven't voted, you might want to prioritize your votes for the exercises that have a standard deviation of 1 or greater (marked in red).

Great idea!

Yeah, and "topics" seem like a whole 'nother thing... I'm aware of the general idea of how it can be valuable, but I am not clear one or more use-cases that motivate the use of that data.  Also, if a particular exercise aims for a specific topic, shouldn't it be attributed to that exercise (i.e. in x-common)?  So, what's the additional topics that are language-specific?
many questions. :)
For that reason, I'm personally interested in just the difficulty, first.

For sure; it's also not clear to me how we handle topics that may or may not touched on by an exercise depending on implementation choices...
Also, I only just realized that we will need to manually decide on an exercise order - the order is not absolutely controlled by difficulty. The difficulty ranking should be a great starting point for that sort, however!

@FridaTveit, I've created a column for you on the spreadsheet should you want to jump in on this.

Thanks! :)

At this time, the task at hand is to close the gap on the exercises which have a standard deviation > 1 (in appears with red background in spreadsheet).
I can think of some resolution paths:

John and Stuart can share their rationale for their scoring, possibly convincing one or the other to change their rating.
Emit, Frida, or Matt could add their vote on these exercises.  Presumably, this would close the gap.
Ignore the difference and go with the average.  To @stkent's point, difficulty does not have to be the only variable in ranking.
...

added matrix, twelve-days, and rectangles to the spreadsheet.

I think getting some sensible order in place is a reasonably high priority; currently, track newcomers are hit with ETL as the second exercise which is probably not a very friendly welcome. I'd support using the existing scores to seed the preliminary ordering, with the understanding that issues/PRs proposing sequencing changes (with reasoning) are both welcomed and encouraged. That iterative philosophy also fits better with the mutation of exercises that will occur as the canonical test suites change.
This assumes that exercism fetch is robust as exercise order changes, i.e. that it fetches "the earliest exercise not yet completed" rather than "the exercise following your most recently-completed exercise in the track sequence"...?

Well put, @stkent; I wholeheartedly agree.
I'm fairly certain that the CLI works that way.  I'll double-check.

Awesome; once you confirm, I'll open up a PR based on the shared spreadsheet!

Okay... I've confirmed.  The next fetched exercise is determined by taking the entire track, subtracting all problems for which the user has submitted and grabbing the top of that list:
https://github.com/exercism/x-api/blob/7919a00f0d266652ad14d22044892b5e13acd51f/api/v1/routes/exercises.rb#L45
This makes re-ordering the track a very safe operation.

Current difficulty profile:

Sorted by average score:

Major change, here!  Super excited!

That second graph is so purdy! Thanks for checking out the CLI behavior, John - glad that behaves as expected. I'll reply to your question on the difficulty ranking spreadsheet now, and once that's resolved, open up the reordering PR.

We've applied this first round of ordering... there's a flight of stories around improving the overall experience... weeeeeeeee!
Considering this first move as done.


Do not enforce a max-height on opened site menu.

PRODUCTION:

DEVELOPMENT

 Hamburger menu problem on mobile devices


[Travis] Remove special frozen string literal build

That build entry is redundant  -- we test frozen string literals in all of the 2.3.0 builds now.

@homu r+

:pushpin: Commit c0bad96 has been approved by segiddins

:hourglass: Testing commit c0bad96 with merge 5a38f3c...

:broken_heart: Test failed - status

@homu retry

:hourglass: Testing commit c0bad96 with merge 9451c1d...

:broken_heart: Test failed - status

@homu retry

:hourglass: Testing commit c0bad96 with merge b698900...

:sunny: Test successful - status


Bug fixes and more quality assurance

Hey guys, Santa 🎅 dropped by at my apartment tonight and left some commits in my socks, yay!

Upgraded TypeScript to the latest version.
Added visual regression tests and file update tests to improve quality assurance of the test suite.
Added a pre-release script to automatically update static fallback specs data before each release.
Added a new CI workflow to check if the crawler script health which is used to generate static fallback specs data.
Dropped tslib dependency as node engine is targeted over v8 after recent pptr upgrade.
Refactored file service to utilize node's native util promisify - only possible when node engine is targeted over v8.
Bug fixes and documentation improvements.

fixes #77
fixes #75
fixes #73
fixes #72
fixes #70
fixes #69
fixes #35
fixes #8

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Create new presets for shop=wholesale and shop=health_food

shop=wholesale (https://wiki.openstreetmap.org/wiki/Tag:shop%3Dwholesale)

Name: Wholesale shop/store
Terms: warehouse club, cash and carry
Additional field: wholesale=* (https://wiki.openstreetmap.org/wiki/Key:wholesale)

shop=health_food (https://wiki.openstreetmap.org/wiki/Tag:shop%3Dhealth_food)

Name: Health food shop
Terms: wholefood, vitamins, vegetarian, vegan

This was done in #4773


infer_schema! panicked using sqlite db on master

I ran into this when using diesel master in anticipation of a stable release:
infer_schema!("dotenv:DATABASE_URL");

And in .env:
DATABASE_URL=test.sqlite

My schema:
CREATE TABLE rooms (
    id INTEGER PRIMARY KEY NOT NULL,
    name TEXT NOT NULL,
    udp_port INTEGER NOT NULL,
    tcp_port INTEGER NOT NULL
)

And my struct:
#[derive(Serialize, Deserialize, Clone, Insertable, Queryable)]
#[table_name = "rooms"]
pub struct Room {
    pub id: i32,
    pub name: String,
    pub udp_port: i32,
    pub tcp_port: i32,
}

I'm using sqlite with features = ["sqlite"] defined in my Cargo.toml. Let me know if there's any more info you need to determine whether this is an issue with my code or diesel. It works fine (on nightly) when using the latest published crate, so this is either a regression in diesel or my misunderstanding of how to define DATABASE_URL for sqlite.
If I get time today I'll test against Postgres, though I prefer to prototype with sqlite since there's less hassle setting up/upgrading the db.

Can you provide the error message you received? Was the file actually present at the path you pointed to?

Not sure if this is related, but I'm also having issues w/ infer_schema! while trying to follow along with Getting Started, however I was using PostgreSQL instead of SQLite.
The error I receive:
$ cargo build
   Compiling aqua v0.1.0
error: macro undefined: 'options!'
 --> src/schema.rs:1:1
  |
1 | infer_schema!("dotenv:DATABASE_URL");
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate

error: aborting due to previous error

error: Could not compile `aqua`.

This is the database connection string
$ cat .env
<EMAIL_ADDRESS>

Let me know if there's any other debug information I could gather for you.

error: macro undefined: 'options!'

Sound like we missed something in #565?

Same error here:

macro undefined 'options!'
(Linux/PostgreSQL/Rust nightly 1.16/Diesel 0.9.1)

nightly-2017-01-25 is busted. Update to a more recent nightly, or point at diesel master.

Oh.
The example (or at least the first steps) do compile and work after removing

#![feature(proc_macro)]

(as suggested).
Maybe this should be added to the tutorial until the issue is fixed.

The tutorial will be updated soon when the new version is released (it
doesn't track master).
fivethousand<EMAIL_ADDRESS>schrieb am Do. 2. Feb. 2017 um
18:17:

Oh.
The example (or at least the first steps) do compile and work after
removing
#![feature(proc_macro)]
(as suggested).
Maybe this should be added to the tutorial until the issue is fixed.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/diesel-rs/diesel/issues/605#issuecomment-277021101,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABOX8-cvTew_qeyF-eC_p-oTg_xF-pFks5rYg-MgaJpZM4L1TB3
.

I'll try again on the beta compiler. I was using the latest nightly (from Tuesday I think).

I get the same problem on the nightly you listed using diesel_codegen master:
     Running `rustc --crate-name kingdoms src/lib.rs --crate-type lib --emit=dep-info,link -C debuginfo=2 -C metadata=8803b6454b81cb08 -C extra-filename=-8803b6454b81cb08 --out-dir /home/otto/src/kingdoms/target/debug/deps -L dependency=/home/otto/src/kingdoms/target/debug/deps --extern futures=/home/otto/src/kingdoms/target/debug/deps/libfutures-e55d45cfd50e0707.rlib --extern tokio_core=/home/otto/src/kingdoms/target/debug/deps/libtokio_core-70b906545a29c574.rlib --extern diesel=/home/otto/src/kingdoms/target/debug/deps/libdiesel-bf8106fecd2b1076.rlib --extern router=/home/otto/src/kingdoms/target/debug/deps/librouter-2997412ffea4968d.rlib --extern iron=/home/otto/src/kingdoms/target/debug/deps/libiron-72125e3b31590887.rlib --extern dotenv=/home/otto/src/kingdoms/target/debug/deps/libdotenv-75d8ce5725f9d0e8.rlib --extern serde=/home/otto/src/kingdoms/target/debug/deps/libserde-3b541f18042a189e.rlib --extern serde_json=/home/otto/src/kingdoms/target/debug/deps/libserde_json-85c7805edd047502.rlib --extern hyper=/home/otto/src/kingdoms/target/debug/deps/libhyper-f076905ec4b248f0.rlib --extern clap=/home/otto/src/kingdoms/target/debug/deps/libclap-f2820a3ff71ece60.rlib --extern diesel_codegen=/home/otto/src/kingdoms/target/debug/deps/libdiesel_codegen-4fec4c5b49099acd.so --extern serde_derive=/home/otto/src/kingdoms/target/debug/deps/libserde_derive-bb0d6dc974011064.so -L native=/usr/lib -L native=/usr/lib`
error: custom derive attribute panicked
 --> src/schema.rs:1:1
  |
1 | infer_schema!("dotenv:DATABASE_URL");
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = help: message: This is a bug. Please open a Github issue with your invocation of `infer_schema!
  = note: this error originates in a macro outside of the current crate

error: Could not compile `kingdoms`.

Caused by:
  process didn't exit successfully: `rustc --crate-name kingdoms src/lib.rs --crate-type lib --emit=dep-info,link -C debuginfo=2 -C metadata=8803b6454b81cb08 -C extra-filename=-8803b6454b81cb08 --out-dir /home/otto/src/kingdoms/target/debug/deps -L dependency=/home/otto/src/kingdoms/target/debug/deps --extern futures=/home/otto/src/kingdoms/target/debug/deps/libfutures-e55d45cfd50e0707.rlib --extern tokio_core=/home/otto/src/kingdoms/target/debug/deps/libtokio_core-70b906545a29c574.rlib --extern diesel=/home/otto/src/kingdoms/target/debug/deps/libdiesel-bf8106fecd2b1076.rlib --extern router=/home/otto/src/kingdoms/target/debug/deps/librouter-2997412ffea4968d.rlib --extern iron=/home/otto/src/kingdoms/target/debug/deps/libiron-72125e3b31590887.rlib --extern dotenv=/home/otto/src/kingdoms/target/debug/deps/libdotenv-75d8ce5725f9d0e8.rlib --extern serde=/home/otto/src/kingdoms/target/debug/deps/libserde-3b541f18042a189e.rlib --extern serde_json=/home/otto/src/kingdoms/target/debug/deps/libserde_json-85c7805edd047502.rlib --extern hyper=/home/otto/src/kingdoms/target/debug/deps/libhyper-f076905ec4b248f0.rlib --extern clap=/home/otto/src/kingdoms/target/debug/deps/libclap-f2820a3ff71ece60.rlib --extern diesel_codegen=/home/otto/src/kingdoms/target/debug/deps/libdiesel_codegen-4fec4c5b49099acd.so --extern serde_derive=/home/otto/src/kingdoms/target/debug/deps/libserde_derive-bb0d6dc974011064.so -L native=/usr/lib -L native=/usr/lib` (exit code: 101)

To be clear, I can use the published crate on nightly, but using master breaks on all rustc that I've tried.

Nvm, it seems to fail regardless of what I try... in any case, I'm not blocked by this issue, I just wanted to make sure it was addressed before a new crate was published targeting the new rust 1.15.

Ok, it looks like it's potentially partially my fault. I was messing with the URL in .env to try to get it to work on the beta release, and I then got errors from that. I'm working through the errors on the nightly mentioned earlier in this chain.

Ok, I figured it out. I was using diesel_codegen from master, but diesel from crates.io and I had to set the "sqlite" feature when I updated to diesel master (I guess it was default on in diesel but not diesel_codegen before?). I rebuilt using the latest beta (1.16) and it worked.
So, TL;DR: update both diesel and diesel_codegen to the latest master and it compiles on the latest beta.

Can you give an example of the .env file that was failing so I can make sure we give an error message than handles that case? Was the .env file itself invalid?

Yes, the .env file was invalid in my test. I threw a sqlite:// in front of the filename (to make it look more like postgres) thinking maybe it was just a poor error message, but it was failing before even getting to that point. As I mentioned above, it was a mismatch between diesel_codegen 0.10 and diesel 0.9, which was resolved by setting both to pull from master. The error message I got once it got past whatever it was panicking on was helpful:

= help: message: called Result::unwrap() on an Err value: StringError("Failed to establish a database connection at sqlite://test.sqlite. Error: BadConnection("Unable to open the database file")")
= note: this error originates in a macro outside of the current crate

The crate you just published works OOTB with my previously working .env entry, so this is now resolved and works with the stable compiler.


Digest loop problem

Hi, I'm using the app to bootstrap ng1 ng2 at work. However, every single event is firing the digest loop. To make matters worst, when the package angular material is added even the mouse move triggers the digest loop.
I'm using this to watch the digest loop
        $scope.$watch( function () {
            console.log("digested ...", event)
        })

In the friends controller.

Hm.. Yeah I am noticing that a digest is triggered when clicking on the view.
Not sure what is causing that. Wonder if it's a zone thing...

I refactor my app. It took almost the same amount of time that I spent making ng1 ng2 work together.


US580238: Updating commons version

https://internal.almoctane.com/ui/entity-navigation?p=131002/6001&entityType=work_item&id=580238

A developer build has not yet been created for this branch. Click here to go ahead and create the build...

CI Build Link:
http://sou-jenkins2.swinfra.net:8080/job/CAFapi/job/CAFapi~opensuse-tomcat-jre11-image~US580238~CI


Support cats show (or something better than .toString)?

Hi,
It's hard to decrypt what's wrong in a case class printed with .toString because it doesn't contain the keys but only it's values.
Cats show + Kitten has been saving my life for this: https://github.com/typelevel/kittens#derive-show
Would be cool to either support cats Show typeclass or maybe we can think of verify typeclass and a separate dependency that bring conversions for cats Show?
Thanks

Major goal of verify is to minimize dependencies on other libraries, so Cats show probably won't happen. Do you have specific cases where toString doesn't work well, like Array?

Proposal
I understand that adding a dependency to cats is out of the question.
Maybe having verify's own typeclass with a default instance that uses .toString?
I'm refering to an implementation like described in Dotty's doc.
Basically this would enable users of verify to customize how to show objects and we could in a separate lib have cats derived instances for that verify typeclass.
The usecase
Given this simple case class:
case class Foo(a: String, b: String, c: String, d: String, e: String, f: String, g: String)

And an assertion failure:
Foo("yo", "yo", "yo", "yo", "ya", "yo", "yo") == Foo("yo", "yo", "yo", "yo", "yo", "yo", "yo")

I need to count with my finger on the screen to know were the assertion failed.
Thanks


Add stream control to Neuralynx

A fix desired for @TheChymera's data conversion - he has some multi-stream Neuralynx files and needs to be able to specify the stream to be written as the main vs. processed recording
Will need some tests to merge this, which will require investigating the GIN examples to see if any of those are multi-stream

The following are multi-stream:
/home/heberto/neuroconv_testing_data/ephy_testing_data/neuralynx/Cheetah_v5.6.3/original_data
NeuralynxRecordingExtractor: 2 channels - 2 segments - 2.0kHz - 1196.800s
/home/heberto/neuroconv_testing_data/ephy_testing_data/neuralynx/Cheetah_v5.7.4/original_data
NeuralynxRecordingExtractor: 5 channels - 4 segments - 32.0kHz - 43.595s
/home/heberto/neuroconv_testing_data/ephy_testing_data/neuralynx/Cheetah_v5.5.1/original_data
NeuralynxRecordingExtractor: 2 channels - 2 segments - 32.0kHz - 53.312s
/home/heberto/neuroconv_testing_data/ephy_testing_data/neuralynx/Cheetah_v6.3.2/incomplete_blocks
NeuralynxRecordingExtractor: 1 channels - 3 segments - 32.0kHz - 107.010s
/home/heberto/neuroconv_testing_data/ephy_testing_data/neuralynx/Cheetah_v5.4.0
/home/heberto/neuroconv_testing_data/ephy_testing_data/neuralynx/BML_unfilledsplit/original_data
NeuralynxRecordingExtractor: 1 channels - 2 segments - 29.4kHz - 0.045s

@thechymera Did this change end up working for you?

@TheChymera managed to find some testing data for it, finally added some tests for the capability
@h-mayorquin Could you give this a quick look when you get a chance? Just propagating stream control to SI

@h-mayorquin OK copied docstring and helper class method from https://github.com/catalystneuro/neuroconv/blob/add_stream_control_neuralynx/src/neuroconv/datainterfaces/ecephys/openephys/openephysbinarydatainterface.py#L55-L68
We can eventually talk about how to make a common interface to reduce the duplication there, but this is just a patch fix here


Convert PSCustomObject to Hashtable

Convert the CustomObject that ConvertFrom-Json produces to a hashtable. This implementation does not use newtonsoft.json but rather haphazardly converts the PSCustomObject to a hashtable.
The alternative approach is to take on another dependency to newtonsoft.json and then do ConvertFrom-JsonNewtonsoft -String (Get-Content -Path $Path -Encoding $Encoding -Raw) | ConvertTo-Datum -DatumHandlers $DatumHandlers

I don't really get why we need this and why we don't use ConvertFrom-Yaml for the JSON...
I only had a look on my phone for a sec...

I was unaware that a YAML module would convert JSON. Sounds like a simple fix then.


Remove .fr_text if section breaks contain no description text

@ajb: this will fix the gratuitous padding for section breaks.

I already did this: https://github.com/dobtco/formrenderer-base/commit/fd61b2790f2ced4a1adc51a23979348839f93dac
What's missing?


Could not import Flash Attention enabled models: No module named 'vllm_cache_ops'

System Info
Full command: CUDA_VISIBLE_DEVICES=0,1 text-generation-launcher --model-id meta-llama/Llama-2-7b-chat-hf --port 8080 --trust-remote-code --env --num-shard 2
OS: Ubuntu 20
Target: x86_64-unknown-linux-gnu
Cargo version: 1.70.0
Commit sha: 0e8b47811e711b46fe80e6b*****4186f83744d6
Docker label: N/A
nvidia-smi:
Thu Aug 10 07:46:13 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 515.57       Driver Version: 515.57       CUDA Version: 11.7     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA A100-SXM...  Off  | 00000000:01:00.0 Off |                    0 |
| N/A   29C    P0    58W / 400W |  36526MiB / 40960MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+
|   1  NVIDIA A100-SXM...  Off  | 00000000:41:00.0 Off |                    0 |
| N/A   29C    P0    55W / 400W |      3MiB / 40960MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+
|   2  NVIDIA A100-SXM...  Off  | 00000000:81:00.0 Off |                    0 |
| N/A   26C    P0    52W / 400W |      3MiB / 40960MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+
|   3  NVIDIA A100-SXM...  Off  | 00000000:C1:00.0 Off |                    0 |
| N/A   25C    P0    53W / 400W |      3MiB / 40960MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
+-----------------------------------------------------------------------------+
The current version: latest v1.0 (install locally from text-generation-inference github
Information

[ ] Docker
[X] The CLI directly text-generation-launcher --model-id meta-llama/Llama-2-7b-chat-hf --port 8080 --trust-remote-code --env

Tasks

[ ] An officially supported command
[x] My own modifications

Reproduction
Install locally according to the instruction in README.md, then run
CUDA_VISIBLE_DEVICES=0,1 text-generation-launcher --model-id meta-llama/Llama-2-7b-chat-hf --port 8080 --trust-remote-code --env --num-shard 2
Expected behavior
Expect the llama models to shard and run correctly as it does when sharding on all 4 GPUs with the following command:
'text-generation-launcher --model-id meta-llama/Llama-2-7b-chat-hf --port 8080 --trust-remote-code --env'

It was just due to incorrect installation from source. Some how the "BUILD_EXTENSIONS=True make install" command did not excecute all the installation. Fixed the issues by manually install vllm, flash attention according to Makefile in server/Makefile

It was just due to incorrect installation from source. Some how the "BUILD_EXTENSIONS=True make install" command did not excecute all the installation. Fixed the issues by manually install vllm, flash attention according to Makefile in server/Makefile

anyone just wanting to run a model and not neccesarily requiring FlashAttention, you can bypass this issue by using --quantize bitsandbytes , you will still see the warning but the model will load. I'm aware that this is not the intention of the HF devs, since they are going to gradualy deprecate this, but I find more than often people struggle to get things running at all, before running compute optimal.

This has nothing to do with bitsandbytes. We're not going to deprecate bitsandbytes.

my bad - I thought bitsandbytes would def. route to CausalLm by default


PromQL error

What type of bug is this?
Unexpected error
What subsystems are affected?
Frontend, Datanode
What happened?
I tried some PromQL expressions of node-exporter dashboard, but failed to query expected results for some expressions.

[ ] avg(node_load5) / count(count(node_cpu_seconds_total) by (cpu))

Error: No field named cpu. Valid fields are node_load5.greptime_timestamp, "AVG(node_load5.greptime_value)".

[ ] node_memory_SwapTotal_bytes - node_memory_SwapFree_bytes

No field named node_memory_swapfree_bytes.instance. Valid fields are "node_memory_SwapTotal_bytes".instance, "node_memory_SwapTotal_bytes".job, "node_memory_SwapTotal_bytes".greptime_timestamp, "node_memory_SwapTotal_bytes".greptime_value, "node_memory_SwapFree_bytes".instance, "node_memory_SwapFree_bytes".job, "node_memory_SwapFree_bytes".greptime_timestamp, "node_memory_SwapFree_bytes".greptime_value.

What operating system did you use?
Linux beelink 6.4.7-arch1-2 #1 SMP PREEMPT_DYNAMIC Mon, 31 Jul 2023 11:41:04 +0000 x86_64 GNU/Linux
Relevant log output and stack trace
No response
How can we reproduce the bug?

use GreptimeCloud preview, and exec docker run --rm -e GREPTIME_URL='' -e GREPTIME_USERNAME='' -e GREPTIME_PASSWORD='' --name greptime-node-exporter greptime/node-exporter from quick start without prometheus
directly exec the expressions above

I've verified this is fixed on the current latest HEAD, the corresponding PR should be https://github.com/GreptimeTeam/greptimedb/pull/2297