text:
Pool connections status

Is there a way to get status (readyState) of connections inside a SimplePool? Thanks

I used a "dirty" workaround for this, accessing the _conn property of the SimplePool instance directly. It works, but maybe we should add a getter for Connection state. I'll open a PR

I think using the dirty workaround should be fine.

I think using the dirty workaround should be fine.

I disagree. _conn is a private field that will not even be shown by the LSP. Also accessing it directly is unsafe. A overwrite will render the pool instance useless. Also _conn holds many other private fields of the Relay Instance that are not of interest to the end user of the API.
I am working on a PR that adds a getter method to the class that will return a safe copy of only the connection state and exclude the other methods.

this pr with listConnectionStatus() didn't solve this issue? allow you to see whole network status
https://github.com/nbd-wtf/nostr-tools/pull/419/files

authors: Egge7 antonioconselheiro fiatjaf misovan

repo: nbd-wtf/nostr-tools

license: Unlicense


text:
🛑 Site is down

In 2e753f9, Site (https://fyle.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Site is back up in 3a30847 after 18 minutes.

source: gharchive/issue

repo: nbitzz/status

license: MIT

license_type: permissive

license_source: github-api


text:
In the case where AMD is used, Expose store to the global window object ...

...so extensions (like store.overlfow.js) can extend it :)

Looks like you are changing the behavior in a way past AMD users disagree with. While we consider the merits, your pull request should at least update the tests so they don't fail.

Thanks for the the response, I'll update the tests shortly.

P.s jQuery uses a similar approach to make it easily extensible. :)

Well, if jQuery does it... :)

source: gharchive/pull-request

authors: nbubna raikoroje

repo: nbubna/store

license: mit

license_source: bigquery


text:
error building FSharp.Core

on Windows, I get the following error when building using build.cmd:
Time Elapsed 00:00:01.79
  Restoring packages for D:\Projects\dotnet-js\src\FSharp.Core\FSharp.Core.fsproj...
  Generating MSBuild file D:\Projects\dotnet-js\src\FSharp.Core\obj\FSharp.Core.fsproj.nuget.g.props.
  Generating MSBuild file D:\Projects\dotnet-js\src\FSharp.Core\obj\FSharp.Core.fsproj.nuget.g.targets.
  Writing lock file to disk. Path: D:\Projects\dotnet-js\src\FSharp.Core\obj\project.assets.json
  Restore completed in 485.64 ms for D:\Projects\dotnet-js\src\FSharp.Core\FSharp.Core.fsproj.

  NuGet Config files used:
      C:\Users\Wael\AppData\Roaming\NuGet\NuGet.Config
      C:\Program Files (x86)\NuGet\Config\Microsoft.VisualStudio.Offline.config

  Feeds used:
      https://api.nuget.org/v3/index.json
      C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\
Microsoft (R) Build Engine version 15.1.1012.6693
Copyright (C) Microsoft Corporation. All rights reserved.

C:\Program Files\dotnet\sdk\1.0.4\Sdks\Microsoft.NET.Sdk\build\Microsoft.NET.Sdk.DefaultItems.targets(165,5): error : Duplicate 'Compile' items were included. The .NET SDK includes 'Compile' items from your project directory by default. You can either remove these items from your project file, or set the 'EnableDefaultCompileItems' property to 'false' if you want to explicitly include them in your project file. For more information, see https://aka.ms/sdkimplicititems. The duplicate items were: 'array.fs'; 'array.fsi'; 'array2.fs'; 'array2.fsi'; 'array3.fs'; 'array3.fsi'; 'collections.fs'; 'collections.fsi'; 'event.fs'; 'event.fsi'; 'fslib-extra-pervasives.fs'; 'fslib-extra-pervasives.fsi'; 'Linq.fs'; 'Linq.fsi'; 'list.fs'; 'list.fsi'; 'local.fs'; 'local.fsi'; 'map.fs'; 'map.fsi'; 'MutableTuple.fs'; 'nativeptr.fs'; 'nativeptr.fsi'; 'option.fs'; 'option.fsi'; prim-types-prelude.fs'; 'prim-types-prelude.fsi'; 'prim-types.fs'; 'prim-types.fsi'; 'printf.fs'; 'printf.fsi'; 'QueryExtensions.fs'; 'quotations.fs'; 'quotations.fsi'; 'reflect.fs'; 'reflect.fsi'; 'result.fs'; 'result.fsi'; 'seq.fs'; seq.fsi'; 'seqcore.fs'; 'seqcore.fsi'; 'set.fs'; 'set.fsi'; 'SI.fs'; 'string.fs'; 'string.fsi' [D:\Projects\dotnet-js\srcFSharp.Core\FSharp.Core.fsproj]

Build FAILED.

C:\Program Files\dotnet\sdk\1.0.4\Sdks\Microsoft.NET.Sdk\build\Microsoft.NET.Sdk.DefaultItems.targets(165,5): error : Duplicate 'Compile' items were included. The .NET SDK includes 'Compile' items from your project directory by default. You can either remove these items from your project file, or set the 'EnableDefaultCompileItems' property to 'false' if you want to explicitly include them in your project file. For more information, see https://aka.ms/sdkimplicititems. The du
plicate items were: 'array.fs'; 'array.fsi'; 'array2.fs'; 'array2.fsi'; 'array3.fs'; 'array3.fsi'; 'collections.fs'; 'collections.fsi'; 'event.fs'; 'event.fsi'; 'fslib-extra-pervasives.fs'; 'fslib-extra-pervasives.fsi'; 'Linq.fs'; 'Linq.fsi'; 'list.fs'; 'list.fsi'; 'local.fs'; 'local.fsi'; 'map.fs'; 'map.fsi'; 'MutableTuple.fs'; 'nativeptr.fs'; 'nativeptr.fsi'; 'option.fs'; 'option.fsi'; 'prim-types-prelude.fs'; 'prim-types-prelude.fsi'; 'prim-types.fs'; 'prim-types.fsi'; 'printf.fs'; 'printf.fsi'; 'QueryExtensions.fs'; 'quotations.fs'; 'quotations.fsi'; 'reflect.fs'; 'reflect.fsi'; 'result.fs'; 'result.fsi';'seq.fs'; 'seq.fsi'; 'seqcore.fs'; 'seqcore.fsi'; 'set.fs'; 'set.fsi'; 'SI.fs'; 'string.fs'; 'string.fsi' [D:\Projects\dotnet-js\src\FSharp.Core\FSharp.Core.fsproj]
    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.25
---
Build failed

After upgrading to .net core 2.0, I no longer have this issue. closing it...

repo: ncave/dotnet-js


text:
ConfigRouter undefined

Currently "make test" fails as ConfigRouter is undefined at config_server_helper_test.go:39.
$ make test
...
api/rest/config_server_helper_test.go:39:3: undefined: ConfigRouter
...

Naively grepping suggests that maybe it should be "RestRouter"

I need to update that test. ConfigRouter was removed in 613c9c45f011bde507053c07b0adcddc5f2147b3. Maybe the test doesn't need to be there anymore, actually.

Fixed with daace77c08603633017db7b2ee44d0fb25321a11

authors: danielthatcher jacobheath

repo: nccgroup/tracy


text:
Add Depends On Component Biospecimen

https://github.com/ncihtan/data-models/blob/741f4a7ca6a3bae13534f144be83a5f8e9ff8a15/HTAN.model.csv#L95

Fixed in #163

repo: ncihtan/data-models


text:
Home Assistant MQTT support

Resolves #24
This PR adds Home Assistant MQTT support so that energy-monitor measurements can be stored and used with electricity grid integration.

Won't merge (for now), see https://github.com/ncolomer/energy-monitor/issues/24#issuecomment-1637189435

repo: ncolomer/energy-monitor


text:
whatis parse for rclone(1) failed

Hi,
following the Linux install guide, http://rclone.org/install/, I encountered this error while doing performing the last command, sudo mandb (these are the latest records):
Processing manual pages under /usr/local/share/man...
Updating index cache for path `/usr/local/share/man/man1'. Wait...mandb: warning: /usr/local/share/man/man1/rclone.1: whatis parse for rclone(1) failed
done.
Checking for stray cats under /usr/local/share/man...
Checking for stray cats under /var/cache/man/local...
1 man subdirectory contained newer manual pages.
1 manual page was added.
0 stray cats were added.
0 old database entries were purged.

I'm trying to install/use rclone v1.29 (rclone-v1.29-linux-amd64) on Ubuntu 14.04 LTS.
Even when trying to grab the rclone version is printing a failed error:
root@mysrv:~/rclone-v1.29-linux-amd64# rclone -V
2016/04/28 13:13:41 Failed to load config file "/root/.rclone.conf" - using defaults: open /root/.rclone.conf: no such file or directory
rclone v1.29

Is rclone not compatible with Ubuntu 14.04 LTS?

I don't think the whatis parse for rclone(1) failed is a problem - it is only a warning.  It probably means rclone won't appear in the whatis database.
As for Failed to load config file "/root/.rclone.conf" - using defaults: open /root/.rclone.conf: no such file or directory - then next step is to run rclone config to make the configuration for the remote fs.
So yes rclone should work fine with ubuntu 14.04 (I develop it on ubuntu!).

Yes, forgot to update. Seem to work properly. Thanks @ncw .

authors: ncw oviliz

repo: ncw/rclone


text:
The host website for the World Bank's LSMS-ISA data is not accessible.

When attempting to access the World Bank's LSMS-ISA data through your link, an error message comes up as follows:

Would you like to check if the site is accessible or has been updated to a new location?
Thanks and Kind Regards,
Haocheng

hi Haocheng! unfortunately I haven't been keeping up with this for several years and can't really point you in the right direction. hope you're able to find where they're hosting the data now or a similar data source that you can use!

repo: nealjean/predicting-poverty


text:
Fungible Token Support

Overview
Fungible token (FT) support in the wallet is required by several of our app developers (Flux, Stardust, Upshot, etc), and is necessary for proper ETH Bridge support (handling wrapped ETH and ERC20 tokens).
At a minimum, we need to display the balances of a subset of tokens that meet the FT standard.
FT Standard NEP
FT Implementation
Stories
As a user, I want to view the token balances of my account, so I can understand my current asset position.
As a user, I want to directly view and confirm transactions that involve my tokens, so I can prevent misuse.
As a user, I want to send and receive tokens from the Wallet, so I can pay for items with tokens.

Closing as issue is outdated

repo: near/near-wallet


text:
Replacing Segment to RudderStack on transfer wizard metrics

This PR contains changes from replacing Segment to Rudderstack.
Currently these metrics are only active within wallet transfer functionality.

@roshaans thank you for thoughtful review!

I have rebased master. This PR needs to be reviewed & merged prior to releasing transfer wizard, so would be appreciated if I can get more reviews


text:
Add Chakra CoC to root of project

Right now our CoC link is dead. This needs to be updated.

As like vidi

closed by #112

authors: ckiss mcdonnelldean

repo: nearform/concorda


text:
Support non standard JWKS paths

Hi,
is it possible to update plugins options to allow passing a custom path to the remote JWKS keys? Currently it always points to .well-known/jwks.json which does not work for every project.
Will be glad to help with the PR.
Thanks for this cool library.

@alex-rieger I transfered the issue to the get-jwks repo

@alex-rieger is this something you'd be interested in sending a PR for?

authors: alex-rieger simoneb

repo: nearform/get-jwks


text:
Add a postmaster page

Discussed in https://github.com/neatnik/omg.lol/discussions/256

This has been added! Thanks.


text:
After clicking "Deploy App" in the frame the iframe goes blank

Context

Refused to frame 'https://nebari/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'none'".

Value and/or benefit
NA
Anything else?
No response

When I use the headless form outside of an iframe it redirects me to a spawn page like https://nebari/hub/spawn-pending/mike/tes-1771544

I think we need to either:

intercept the final redirection and instead show a confirmation that the app was deployed (:tada:) and allow user to click a button to launch it in a new tab (outside of the iframe)
allow the app to be launched in the iframe by relaxing frame-ancestors to self (this is easier short-term)

intercept the final redirection and instead show a confirmation that the app was deployed (:tada:) and allow user to click a button to launch it in a new tab (outside of the iframe)

It seems like events like beforeUnload etc are only triggered after the CSP violation i.e. the header is checked first before the javascript can be executed. At least, this is my current understanding.
I’m currently unable to think of a way to indirectly intercept/prevent the navigate request.
I guess an alternative is for me to open another PR in jhub-apps (unless you can think of another workaround)? e.g. if we are in headless mode (see this variable) then we have no navigation. What do you think?

I’m currently unable to think of a way to indirectly intercept/prevent the navigate request.

As per https://developer.mozilla.org/en-US/docs/Web/API/Location/assign#exceptions the assign should throw SecurityError exception so maybe it should be fixed on jhub-apps by catching this exception and in that case showing a confirmation screen and a button allowing to open that URL in a new browser tab?

if we are in headless mode (see this variable) then we have no navigation.

That would work too. Still, need to show a confirmation and have a way to open it in new window.

@krassowski If you are agreed that this issue is probably best resolved in jhub-apps (perhaps with some downstream tweaks afterwards here if required), then I will open an issue in jhub-apps now.

I believe that this has now been closed by https://github.com/nebari-dev/jhub-apps/pull/509.

authors: krassowski nenb

repo: nebari-dev/jupyterlab-jhub-apps


text:
Merge develop into main for 2024.3.3 release

Reference Issues or PRs

What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[x] Release
[ ] Other (please describe):

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

Any other comments?

This is now only required to keep main up to date.

repo: nebari-dev/nebari


text:
Input text not visible in cases due to color:inherit

The color:inherit will obviously cause problems if font color is set to something close to white in any section of html.  (Say a header section, etc with a dark background).  Since the font-color becomes inherited, but the background remains default in input elements, it won't look correct or make any sense.  It should NOT be assumed that the user's text in a section of html will not be white or a color close to what happens to be background color of input elements.
button,
input,
optgroup,
select,
textarea {
color: inherit; /* 1 /
font: inherit; / 2 /
margin: 0; / 3 */
}

color: inherit; /* 1 */ should be removed.

Absolutely, I dont know who decided this value for color. If that color need to be inherited, then background-color cant stay static as #FFF in original or changed one by developer

@clottes @CemDemirkartal agree that inherit should be removed - https://github.com/necolas/normalize.css/blob/master/normalize.css#L256 /cc @necolas will PR be accepted?

This was fixed by #502.

Thanks, @cvrebert, for spotting this!

authors: CemDemirkartal clottes cvrebert jonathantneal voronianski


text:
[chore] folder/file naming conventions

we should pick a naming convention and update the entire repo to use that naming convention
currently for files we have a weird combination of Pascal-and-Spinal-Case
for the languages that have separated the neetcode 150 and the blind 75, we don't have a consistent convention for directory naming.
i'd propose moving to spinal-case across the board, but don't feel strongly about it. curious if anyone has strong opinions.
when we do the refactor, we should do it in chunks (maybe folder by folder) to make the PR reviews easier.
@neetcode-gh any preferences?

Hi, I would like to contribute to your work and was wondering if snake_case(words separated by underscores) will be a good fit for the issue, since you don't have a good feeling about spinal-case?

I'd be cool with snake case. Let's wait for @neetcode-gh to drop their two pennies before we start the refactor, though!

Hi. Are there any updates? Should I proceed with the work

Neet's probably been getting a ton of pings on this repo, it's blown up a bit since the video about the website update. It could be a while before there's a decision, I'd recommend finding other places to contribute in the meantime!

Thanks for looking into this! Yeah im fine with having a standard naming convention, but updating the file names will break the links on the site. The links will mostly have to be updated manually, along with the file names so I'm wondering if it's worth it. If there are any PRs that change file names, please cc me on them so I know to update the links, thanks!

I think for Java solutions, we should adhere to the standard of using lower CamelCase.

one other thought to add to this. in some languages we're using a directory structure that maps to the categories on neetcode.io (e.g. neetcode_150/backtracking/).
we should likely decide on a single convention? In my opinion, it's easier to search w/ CMD + F if all the solutions are in one top level directory for that language (not everyone is familiar with the t shortcut on github.com). I'm not sure I see a benefit of using the nested dirs structure?

I'm not sure I see a benefit of using the nested dirs structure?

In my Opinion the nested directory structure is quite compact and easy to use it really gives a brief knowledge about the domains of  DSA in a glance.

I also find it easier to CTRL/CMD + F the repo to find solutions. The website already does a good job of showcasing the problems sorted into their respective domains.

I think a nested directory structure is more organized and less cluttered. If we need to find which directory it belongs to, we could always add a list in the Readme to indicate which category each question is under.

Yep! Nested Directory Structure looks well organized and much easier to navigate around

Hello ! Could I contribute to this?

thanks for all of the thoughts and input, everyone!
i'm on board with snake_case and the same nested directory structure as the website (this seems like the general consensus/preference).
@Ahmad-A0 would these types of changes break the fancy new "Missing Solutions" feature in the readme (renaming files?)?
i think people are free to start work on this refactor, with these requirements:

tag @neetcode-gh as the reviewer on your PR. it can't merge until he's taken the time to update the website accordingly, and for that reason he should be the only person merging these PRs
also tag @Ahmad-A0 as a reviewer on the PR, so he can update the "Missing Solutions" script accordingly (this depends on whether or not these changes would actually break that feature, ahmad should be able to answer that for us)
please only change one language + problem set (blind 75 or neetcode 150) per PR. for example, you might decide to make one PR for java/blind_75. (if PRs get too large it's hard to ensure to quality of review can stay high. this will also help neet and ahmad's updates be reasonably scoped)
ensure your changes are all of the snake case form, including the appropriate subdirectory and preceding zeros, if any. e.g. java/1-Two-Sum.java would become java/neetcode_150/01_arrays_&_hashing/0001_two_sum.java

we should also update the https://github.com/neetcode-gh/leetcode/blob/main/CONTRIBUTING.md#contributing-guidelines to make sure they reflect the decided convention.

@mitchellirvin So long as the files are prefixed with the problem-number the table will continue to function.

@Ahmad-A0 understood, thank you!
do you mind if we add preceding zeros where applicable (e.g. 0001_two_sum.java)? i think it'd be really nice to make the github file sorting add some navigability (this way problems would actually be ordered by number ascending)

Since the script uses the <problem-number> prefix it should be able to continue working after a quick fix to read nested directories, which I will likely push tomorrow.
However I wanted to suggest using the name leetcode assigns in URLs to avoid any confusion or discrepancies across solutions eg. 0242-valid-anagram.<extension> for https://leetcode.com/problems/valid-anagram/. This change could be incorporated with the nested directory structure, or we could maintain the flat directory structure and add a README component to organise the problems into problem type.
@mitchellirvin and others, thoughts?

@Ahmad-A0 understood, thank you!
do you mind if we add preceding zeros where applicable (e.g. 0001_two_sum.java)? i think it'd be really nice to make the github file sorting add some navigability (this way problems would actually be ordered by number ascending)

Yep this is fine, preceding zeroes won't affect the script.

does the name in leetcode's URLs ever differ from the name in the title of the problem? I'm not sure I understand the impact of that change. what would the before/after look like?

The name in the URLs always matches the name of the problem, you can view the full list in the table script on the .github for.
const URLS = {
     'NeetCode 150': [
         'https://leetcode.com/problems/contains-duplicate/',
         'https://leetcode.com/problems/valid-anagram/',
         'https://leetcode.com/problems/two-sum/',
         'https://leetcode.com/problems/group-anagrams/',
         'https://leetcode.com/problems/top-k-frequent-elements/',
         'https://leetcode.com/problems/product-of-array-except-self/',
         'https://leetcode.com/problems/valid-sudoku/',
         'https://leetcode.com/problems/encode-and-decode-strings/',
         'https://leetcode.com/problems/longest-consecutive-sequence/',
         'https://leetcode.com/problems/valid-palindrome/',
         'https://leetcode.com/problems/two-sum-ii-input-array-is-sorted/',
         'https://leetcode.com/problems/3sum/',
         'https://leetcode.com/problems/container-with-most-water/',
         'https://leetcode.com/problems/trapping-rain-water/',
         'https://leetcode.com/problems/best-time-to-buy-and-sell-stock/',
         'https://leetcode.com/problems/longest-substring-without-repeating-characters/',
         'https://leetcode.com/problems/longest-repeating-character-replacement/',
         'https://leetcode.com/problems/permutation-in-string/',
         'https://leetcode.com/problems/minimum-window-substring/',
         'https://leetcode.com/problems/sliding-window-maximum/',
         'https://leetcode.com/problems/valid-parentheses/',
         'https://leetcode.com/problems/min-stack/',
         'https://leetcode.com/problems/evaluate-reverse-polish-notation/',
         'https://leetcode.com/problems/generate-parentheses/',
         'https://leetcode.com/problems/daily-temperatures/',
         'https://leetcode.com/problems/car-fleet/',
         'https://leetcode.com/problems/largest-rectangle-in-histogram/',
         'https://leetcode.com/problems/binary-search/',

that's a good idea.
i'd prefer to keep snake case for consistency (as opposed to spinal case), though. e.g. 0242_valid_anagram.<extension> just so we're not mixing and matching naming conventions

Yep, that sounds great. I can write a script to rename the files although I don't know how practical that is until something like #763 gets done.

I'm wondering if the nested directory structure is still necessary with the changes made to the README to reflect problem category, having a different folder for the <problem-set>  could especially be problematic as some problems would now appear three times in the NeetCode 150, Blind 75 and NeetCode All lists.

This is long overdue, but I'll have some time over the next week to implement dynamic URLs from #763, so I'm happy to review and merge any PRs related to renaming/organizing. I'll time it to merge the PRs the same time I push my changes.
The main thing I would need is to be able to know if a solution exists for a given language (e.g. LC 1 has a solution in Java). But the readme table that @Ahmad-A0 implemented pretty much solves that, but I would just need to convert it to JSON. Btw is there a script you're using for that? At first glance i couldnt find it.

@neetcode-gh
I'm currently using the updateCompletionTable.js script hidden away in ./.github/workflows, it just grabs the problem number for each leetcode question, which I have stored in this JSON file, and sees if the language folder e.g c, cpp, python, etc. has any solutions that start with that number.
Depending on how you want to implement this on your side it might be helpful for me to add another JSON file to this repo that keeps track of which problems are completed alongside the table.

Thanks, I'm almost done with the site changes required. Do you know if there's already some open PRs for doing the renaming? If not, i can do them.

There are no open PRs! Unrelated but, can I also ask how files are found on the site's end so I don't break things in the future. @neetcode-gh

@Ahmad-A0 Just opened #1607 - the PR has a file (.problemSiteData.json) which is the file that contains code links for the site. Lmk if you have any questions, and thank you!

repo: neetcode-gh/leetcode


text:
Create: 199-Binary Tree Right Side View -- SWIFT

File(s) Modified: 199-Binary-Tree-Right-Side-View.swift
Language(s) Used: Swift
Submission URL: https://leetcode.com/submissions/detail/787672275/

Thanks, @nprepaci!


text:
Add optional error flag for controller methods window_by_location and window_by_title.

I'd like to add an error flag to these two methods to error out if the search fails, similar to the is_location api method for the controller.

https://github.com/neetjn/py-component-controller/pull/56

repo: neetjn/py-component-controller


text:
JS version of :empty selector

Would love to see a JS version of how to select all empty elements in JS, as this works: https://api.jquery.com/empty-selector/

:empty is just a css selector, so you should be able to just do this document.querySelectorAll('*:empty') to get a list of all empty elements.

Oh cool! Didn't know that! Thanks.

authors: drewbaker zdivozzo

repo: nefe/You-Dont-Need-jQuery


text:
Possible IOS 9 audio fix for slow audio

Possible fix for ios 9 slow / distorted audio.

Curious, why offlineAudioContext ?

Well, it was the only way I could set the rate to 44100, other attempts
didn't set the buffer correctly.
On Tue, Feb 9, 2016 at 8:35 PM, Zhen Wang notifications@github.com wrote:

Curious, why offlineAudioContext ?
—
Reply to this email directly or view it on GitHub
https://github.com/nehz/ngWebAudio/pull/8#issuecomment-182172686.

--
Christopher Schaub
http://chris.schaub.com

The number was set, but you have to set it "before" decodeAudioData is run,
it seems to prime the pump.
On Tue, Feb 9, 2016 at 8:50 PM, Christopher Schaub chris@schaub.com wrote:

Well, it was the only way I could set the rate to 44100, other attempts
didn't set the buffer correctly.
On Tue, Feb 9, 2016 at 8:35 PM, Zhen Wang notifications@github.com
wrote:

Curious, why offlineAudioContext ?
—
Reply to this email directly or view it on GitHub
https://github.com/nehz/ngWebAudio/pull/8#issuecomment-182172686.

--
Christopher Schaub
http://chris.schaub.com

--
Christopher Schaub
http://chris.schaub.com

Right. That's weird ... not sure how Apple is messing it up as the offline buffer isn't even rendered yet (https://developer.mozilla.org/en-US/docs/Web/API/OfflineAudioContext), but somehow just initializing an offline buffer fixes the audio context?

Also was there a reason for choosing 2 audio channels for the offline buffer? (Trying to reverse engineer why it works)

I'm actually testing touchend with this
https://github.com/Jam3/ios-safe-audio-context/blob/master/index.js
instead. More soon.
On Tue, Feb 9, 2016 at 9:42 PM, Zhen Wang notifications@github.com wrote:

Also was there a reason for choosing 2 audio channels for the offline
buffer? (Trying to reverse engineer why it works)
—
Reply to this email directly or view it on GitHub
https://github.com/nehz/ngWebAudio/pull/8#issuecomment-182184206.

--
Christopher Schaub
http://chris.schaub.com

What's the easiest way to disable webaudio and just fall back to html5
audio? I can't duplicate the issue on iphone 6s, just iphone 6. Apple needs
to fix this.
On Tue, Feb 9, 2016 at 9:43 PM, Christopher Schaub chris@schaub.com wrote:

I'm actually testing touchend with this
https://github.com/Jam3/ios-safe-audio-context/blob/master/index.js
instead. More soon.
On Tue, Feb 9, 2016 at 9:42 PM, Zhen Wang notifications@github.com
wrote:

Also was there a reason for choosing 2 audio channels for the offline
buffer? (Trying to reverse engineer why it works)
—
Reply to this email directly or view it on GitHub
https://github.com/nehz/ngWebAudio/pull/8#issuecomment-182184206.

--
Christopher Schaub
http://chris.schaub.com

--
Christopher Schaub
http://chris.schaub.com

Yeah I agree, can't duplicate issue on my actual iPad either.
You can null out AudioContext before angular is loaded:
window.AudioContext = null; window.webkitAudioContext = null;
But I'll probably push an update that allows this via a flag

Added flag to options to use HTML5 Audio.
Also I added the safe-audio-context code to context init in case it helps some people (fingers crossed)

authors: chrisschaub nehz

repo: nehz/ngWebAudio


text:
🛑 Helen Oy is down

In 539bb8e, Helen Oy (https://www.helen.fi/en) was down:

HTTP code: 503
Response time: 418 ms

Resolved: Helen Oy is back up in a1dd925 after 10 minutes.

repo: neighbourhood-cyber/espoo-watchtower


text:
Made a fork

Hi everyone. I don't know if there is still someone interested in this plugin, since this repository seems dead, but I like it, so I fixed some issues and added some features.
My changes are here. The plugin can be only installed manually for now.
What I changed:

relative path for fetched images is no longer a problem (#36)
updated the overall appearance and layout of the card, it now uses Obsidian's css variables
now text wraps and truncates properly (#29)
added a nice button to copy the URL from preview and live-preview mode (#25)
there is now the possibility to turn off (form settings) the fetching of some non-required fields (description, favicon, host, thumbnail)
it is now possible to (optionally) store all images locally (#28 more or less)

@nekoshita I really like your work on this plugin. Let me know if you are willing to integrate my changes in here.

Hello, I like this plugin very much so i'm looking for ways to make this plugin call to local images. Knowing that you had fixed those problems and added some features, but it seems the lins is unused. Wondering if there was a chance to experience the plugins you made. Thank you very much for reading my letter and thank you very much for trying to solve these problems.

Hi!
What I did was adding an option to download each image to to the plugin directory. This doesn't speed up loading very much (maybe it does on slow networks though) and there is already some sort of caching done by Electron probably.
Using local images in the yaml code block is not possible as of now because Obsidian uses ad hoc links.

Support for this could be possible through DataAdapter.getResourcePath().
I see if I can get something working.

I'm glad you got back to me so quickly. I may not be able to help you at my current level, but thank you very much for your answer and for your willingness to keep trying. I'll wait for your good news. Good luck!!!

authors: ormai xhuajin

repo: nekoshita/obsidian-auto-card-link


text:
format string: don't require a separator between tags

Trying this code:
const std = @import("std");
const time = @import("time");

pub fn main() anyerror!void {
    var now = time.DateTime.now();
    std.log.info("{YYYYMM}", .{ now });
}

It fails with this compilation error: 'M' is not a valid format sequence
Since you're referring to moment in the code, here's how it handles the same format string:
> moment().format('YYYYMM')
< '202205'

try passing that string to DateTime.format directly. std.fmt.format parses the zig-time formatter incorrectly

That doesn't work either.
.\.zigmod\deps\git\github.com\nektro\zig-time\time.zig:328:34: error: 'M' is not a valid format sequence
            if (i < fmt.len - 1) @compileError(comptime std.fmt.comptimePrint("'{s}' is not a valid format sequence", .{fmt[s..e]}));
                                 ^
.\src\main.zig:25:33: note: called from here
        try time.DateTime.format(now, "YYYYMM", .{}, stdout);
                                ^

thanks, will look into this, sorry for troubles

authors: nektro sigod

repo: nektro/zig-time


text:
Invalid routine for account rate calculation

Fixed, measure rate on all cpu cores simultaneously
Fixes # or describe the changes introduced by this PR.

[ x] I have read the CONTRIBUTING.md and make ci passes on my machine.
[ x] I have updated the documentation accordingly.
[ x] I have added tests to cover my changes.

Codecov Report

Merging #102 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #102   +/-   ##
=======================================
  Coverage   19.04%   19.04%
=======================================
  Files           3        3
  Lines         147      147
=======================================
  Hits           28       28
  Misses        117      117
  Partials        2        2

Impacted Files
Coverage Δ

pkg/vanity/probability.go
0% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

repo: nem-toolchain/nem-toolchain


text:
Add vote commands

Close #559

add vote commands
update protocol.json

Maybe you can check https://github.com/neo-project/neo-node/pull/575 and serialize the result according to the expected type?

OK, I can complete it in a new PR.

authors: ProDog shargon

repo: neo-project/neo-node


text:
Add support for temporal functions

Support for the following temporal functions supported by Neo4j:

date()
datetime()
localdatetime()
localtime()
time()

Reference: https://neo4j.com/docs/cypher-manual/current/functions/temporal/

Thanks @RamonLM See #92. Would that work for your usecase? Cheers, Michael.

Thank you, this is great.

authors: RamonLM michael-simons


text:
Update "Graphing our way through the ICIJ offshore jurisdiction data"

uses neo4j-version: 2.2
make sure the graphgist uses Neo4j 2.2 features, esp. Labels
try to adhere to the Cypher style guide (capitalized labels, all-caps rel-types, camel-case properties, if possible consistent keyword casing e.g. all-caps)
the relationship-types should be meaningful enough
sensible data model size 20-150 nodes
good idea
great prose, well written and enough that it makes a good read but not a novel, also prose explaining the use-cases
good domain picture, if possible other illustrating pictures
meta-information available: author, topics
good use of graphgist tools (//graph_result, //table, //setup, //hide, //output)
at least one //graph_result per gist
make sure that long setup queries are hidden
put console at the end

Thanks a lot @whatSocks
We should use Neo4j 2.3 instead.

This one and Neo4j and the Offshore Leaks: the Case of Azerbaijan are both about the ICIJ dataset

authors: jexp whatSocks


text:
Benchmark fails with SEGFAULT

Following the readme, running the benchmark python -m neo4j.bench "MATCH (a:Person {name:'Alice'}) RETURN a"
results in a segmentation fault.
Output:
Neo4j Benchmarking Tool for Python
Copyright (c) 2002-2015 "Neo Technology,"
Network Engine for Objects in Lund AB [http://neotechnology.com]
Report bugs to nigel@neotechnology.com

Python 3.5.0 |Continuum Analytics, Inc.| (default, Sep 13 2015, 10:34:39)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)]

This machine has 4 processors (linux)

Latency measurements:

         INIT     <---SEND--->     <---RECV--->     DONE
overall  <--------------------------------------------->
network           <--------------------------->
wait                          <--->

INIT - start of overall request
SEND - period of time over which data is sent
RECV - period of time over which data is received
DONE - end of overall request

Using graph database at bolt://localhost
Warming up... done

------------------------------------------------------
 MATCH (a:Person {name:'Alice'}) RETURN a
   × 10,000 runs × 1 client = 2,472.9 tx/s
    (10,000 requests in 4.0s)
------------------------------------------------------
 percentile |   overall   |   network   |     wait
------------|-------------|-------------|-------------
       0.0% |     327.9µs |     121.0µs |      55.2µs
      10.0% |     357.2µs |     139.6µs |      66.6µs
      20.0% |     358.6µs |     140.4µs |      67.2µs
      30.0% |     360.0µs |     141.3µs |      67.8µs
      40.0% |     361.8µs |     142.5µs |      68.6µs
      50.0% |     364.7µs |     144.4µs |      70.0µs
      60.0% |     370.1µs |     149.5µs |      73.7µs
      70.0% |     381.4µs |     165.6µs |      92.1µs
      80.0% |     402.8µs |     187.8µs |     107.8µs
      90.0% |     430.1µs |     204.8µs |     120.5µs
      95.0% |     538.1µs |     246.5µs |     135.5µs
      98.0% |     649.8µs |     283.0µs |     154.9µs
      99.0% |     684.8µs |     301.0µs |     186.2µs
      99.5% |     789.2µs |     361.4µs |     231.4µs
      99.9% |   2,547.2µs |   2,003.0µs |   1,896.4µs
     100.0% |   9,253.8µs |   8,843.1µs |   8,723.5µs

------------------------------------------------------
 MATCH (a:Person {name:'Alice'}) RETURN a
[1]    17428 segmentation fault (core dumped)  python -m neo4j.bench "MATCH (a:Person {name:'Alice'}) RETURN a"

The same is true even with -p 1 (and also -x 1)

This code was part of the early driver and no longer exists so cannot fix.

authors: nigelsmall spacecowboy


text:
feat(Beaker): Add distro tag from provisioning conf

Add feature which enables adding distro tags specified
in the provisioning config in beaker section like:
beaker:
    distro_tags:
        FEDORA-34%:
            - NIGHTLY-TESTED

This allows us to specify distros with custom tags.
Signed-off-by: Tibor Dudlák tdudlak@redhat.com

@netoarmando  yes i meant exactly like this, low level per distro which needs it.

repo: neoave/mrack


text:
Versioning on the website is broken

Cache issue, will probably resolve itself.

I mean, it's also broken in private mode 🤔

If you disable cache and reload it works again: (bottom right checkbox)

🤔

Yeah, that works. Also nice to know that exists.

I've purged the cache via the Cloudflare dashboard. It seems to work now, even in a Firefox private window.

repo: neoforged/websites


text:
Send LSN range in getpage request

Problem
There are three kinds of get_page :

Master compute: get the latest page not older than specified LSN (horizon=Lsn::MAX)

RO replica: get the latest page not newer than current WAL position replica already applied (horizon=GetXLogReplayRecPtr(NULL))

Snapshot: get latest page not new than specified LSN (horizon=request_lsn)

The problem itself is more detailed explained in Slack:
https://neondb.slack.com/archives/C036U0GRMRB/p1705932864991419
So I assume that two cases are clear:
Normal RW node: it always request latest version of there page because nobody except it can update pages.
Static RO node (snapshot): it always request version of the page not greater than snapshot LSN
In both cases we do no need range and just "latest" flag.
Most difficult is hot-standby replica. It accepts and apply WAL concurrently with PS. Replica can be ahead of PS or visa versa. This is why replica can not request latest version of the page, because if PS is ahead of replica, it will get "future" version of the page. But we also can not request version of the page with LSN not greater than specified (as in case of static replica). Because we are using "last written LSN" cache to estimate when page was last updated. If page was not updated for a long time, then requesting page worth this LSN may cause PS to retrieve version of the page which was already collected by GC.
So to handle case 3 we need top pas range of LSN: low boundary specifies estimated LSN of last page update (so that we do make PS to wait for applying most recent updates) and higher boundary specifies current apply position of replica, to prevent PS from sending too young pages.
With such range determining start LSN position for lookup in layer map becomes even simpler than now with "latest" flag - it is just max(low_bloundary, min(last_record_lsn, upper_boundary))
Summary of changes
Replace latest flag in get page request with horizon
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

I've added Christian as a reviewer: please can you add someone from the storage team as a review for PRs that change the pageserver.
I haven't reviewed the code, but I notice that there aren't any tests in this PR

I've added Christian as a reviewer: please can you add someone from the storage team as a review for PRs that change the pageserver.
I haven't reviewed the code, but I notice that there aren't any tests in this PR

It is protocol change affecting get_page_at_lsn - the main PS API. So this PR is affecting all tests and so all tests are checking it. But certainly this protocol change was done to address  "Key already removed by GC issue" in PR  #6357.
And there is test_replication_lag.py in this PR. @hlinnaka ask to separate protocol changes in separate PR. Here it is. Unfortunately this PR itself is not enough to solve the access beyond GC cutoff issue.  This PR is necessary but not sufficient. We need also prevent GC from deleting LSN beyond replicas apply position. And here we need changes in #6357 which propagate standby feedback through safekeeper and broker to PS.

Please add a test case that demonstrates the problem / regress-tests your solution.
Also, you are making a breaking change to the protocol.
Please provide a plan to orchestrate the rollout. A Slack channel (e..g, #proj-page_service-lsn-range-requests ) is probably most appropriate, as this touches multiple components.

I just wrote in the previous comment.
Problem is described in #6211
It was expected to be fixed by #6357 and it contains test reproducing the problem.
This PR is separated from #6357.
It is not enough to fix the problem - only in conjunction with changes #6357 the problem will be fixed.
So I do not see much sense in moving test from @6357 to this PR.
Concerning rollout: changes in protocol are backward compatible - new server ids able to serve old clients.
So we can deploy server and then sometimes later upgrade computes.

Discussion: add tests, also cover different protocols in tests
At the very least, describe how you tested it.

I have added more comments explaining how backward compatibility of protocol is provided.
Also I have added neon.protocol_version GUC. It isn't sent now to page server, so ro provide backward compatibility is is necessary not to change format of existed commands. New protocol version should just add new commands.
neon.protocol_version  may be used at compute side to use specific protocol version.
It is currently used in test_protocol_version.py test  which tests backward compatibility. It can be also used if for some reasons we need new client to work with old page server.

Conflicts are resolved.
@problame @petuhovskiy Can you please have a look? Thanks.

Please add a test case that demonstrates the problem / regress-tests your solution.
Also, you are making a breaking change to the protocol.
Please provide a plan to orchestrate the rollout. A Slack channel (e..g, #proj-page_service-lsn-range-requests ) is probably most appropriate, as this touches multiple components.

New page server is able to server old and new commands. So backward compatibility is supported.
For compute I have added neon.protocol_version GUC which can be used to make neon extension to choose old or new format. We can first deploy compute with neon.protocol_version=1.
In this case client will send old commands.
We can rollback deploy of PS and still running clients will be able to work with old server.
Then at next deploy, we can switch protocol version to 2.
Right now default value for neon.protocol_version GUC is 2. I can change it to 1 or we can explicitly specify it in compute spec provided by control plane. What is better?

I wonder how easy would be to have a test specifically for the horizon & standby issue, exposing errors on standby when page which hadn't changes for a long time is requested. https://github.com/neondatabase/neon/pull/7368 has test_replication_lag which covers this, but it needs both...

In principle we have get_raw_page_at_lsn in neon_test_utils extension to request page at there particular LSN.
But still to reproduce error we need PS to advance gc_cutoff beyond this point. So I do not see any principle difference here from what  test_replication_lag.py does

superseded by
https://github.com/neondatabase/neon/pull/7377

authors: andreasscherbaum arssher jcsp knizhnik

repo: neondatabase/neon


text:
UI Attach runs into error

I'm trying to make an UI attachment in a plugin, but it doesn't seem to work and runs into errors.
I tried various different variations of the code below:
Neovim.logger << 'test!'

Neovim.plugin do |plug|
  plug.ui_attach(999, 999, {}) do |*a|
    Neovim.logger << a.inspect
  end
end

With and without block argument, with value in the hashmap and entirely without a third argument, but I'm always getting the same error, so I suspect that it's a plugin issue. Otherwise any hints are welcome.
The error appears once I call :UpdateRemotePlugins (I'm using https://github.com/junegunn/vim-plug).
Versions
macOS 14.1.1 Sonoma
Ruby: 3.2.2 (rbenv 1.2.0)
Gem: 3.4.12
Neovim-Ruby: 0.9.1
Neovim: 0.9.4
Neovim error message
function remote#host#UpdateRemotePlugins[6]..<SNR>61_RegistrationCommands[15]..remote#
host#Require[10]..provider#ruby#Require[8]..provider#Poll, line 7
Vim(if):Error invoking 'poll' on channel 5:^@Invalid channel: 5
function remote#host#UpdateRemotePlugins[6]..<SNR>61_RegistrationCommands[15]..remote#
host#Require[10]..provider#ruby#Require[8]..provider#Poll, line 17
Failed to load ruby host. You can try to see what happened by starting nvim with $NVIM
_RUBY_LOG_FILE set and opening the generated log file. Also, the host stderr is available in messages.
remote/host: generated rplugin manifest: /Users/huluk/.local/share/nvim/rplugin.vim

Error logs
# Logfile created on 2023-11-25 17:07:28 +0100 by logger.rb/v1.5.3
{"_level":"DEBUG","_time":"2023-11-25T17:07:28.708601","_class":"Neovim::EventLoop","_method":"run","exception":"EOFError","message":"end of file reached"}
{"_level":"DEBUG","_time":"2023-11-25T17:07:28.720948","_class":"Neovim::EventLoop","_method":"run","exception":"EOFError","message":"end of file reached","backtrace":["/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/lib/neovim/connection.rb:47:in `readpartial'","/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/lib/neovim/connection.rb:47:in `read'","/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/lib/neovim/connection.rb:47:in `read'","/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/lib/neovim/event_loop.rb:109:in `read'","/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/lib/neovim/event_loop.rb:80:in `block in run'","/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/lib/neovim/event_loop.rb:75:in `loop'","/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/lib/neovim/event_loop.rb:75:in `run'","/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/lib/neovim/session.rb:35:in `run'","/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/lib/neovim/host.rb:29:in `run'","/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/lib/neovim/host.rb:17:in `run'","/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/lib/neovim/host/cli.rb:33:in `run'","/usr/local/var/rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/neovim-0.9.1/exe/neovim-ruby-host:5:in `<top (required)>'","/usr/local/var/rbenv/versions/3.2.2/bin/neovim-ruby-host:25:in `load'","/usr/local/var/rbenv/versions/3.2.2/bin/neovim-ruby-host:25:in `<main>'"]}
test!

I think there are a couple things causing this... first of all it seems like writing to Neovim.logger from a remote plugin breaks the rpc connection. Try removing those lines that write to the logger.
The next thing you're going to run into though, is that you're calling ui_attach on the remote plugin DSL object, not a neovim client. I think this closer to what you want, although I'm not sure if this works either:
Neovim.plugin do |plug|
  plug.command(:StartMyUI) do |client|
    client.ui_attach(999, 999, {})
  end
end

That said, I'm not sure if you want to spawn a UI within a remote plugin like this... I'm pretty unfamiliar with writing UI clients but my understanding was that the UI process should be responsible for starting an embedded nvim process, which it sends the nvim_ui_attach rpc when it's ready to draw (see docs: https://neovim.io/doc/user/ui.html). Maybe @justinmk could point to better resources/examples? Sorry I'm not super helpful here.

Thank you for the hints, and the quick reply!
With your code snippet, at least it doesn't crash any more. Not sure yet if it's working, I'll do some more experiments later.
I think I'm fine with my plugin attaching to the UI. I don't want to embed vim somewhere, I want to produce output on an additional channel for an existing vim instance. (To be concrete, I want to pipe command output into a text to speech engine, in addition to the output which shows on the screen).
I guess after my client calls ui_attach with {ext_cmdline: true, ext_messages: true}, I now want to add a listener to msg_show somehow.
Once I have a working example, I might make a pull request with documentation updates – I must admit I'm really struggling to get started here. Trying to look at other projects either using neovim-ruby or other language interfaces, but it's really hard to find the right info. Not a complaint, I know how much work it is :D

ui_attach seems to work – the plugin shows up for :echo nvim_list_uis(). I'm now trying to actually listen to events. For my experiments, I picked "option_set", since that is part of the always-on global set and I should be able to trigger it with :set showtabline=0. But how do I actually register a callback for this? client.subscribe does not take any block arguments.
The following code doesn't work, but also I'd be very surprised if I'm even going in the correct direction:
Neovim.plugin do |plug|

  p = plug.instance_variable_get(:@plugin)
  # initialize(source, type, name, sync, options, block)
  option_set_handler = Neovim::Plugin::Handler.new(
    nil,
    :event,
    'option_set',
    false,
    {},
    Proc.new { |*args| system 'say', 'this is a test!' + args.inspect }
  )
  p.handlers.push(option_set_handler)

  plug.command(:Start) do |client|
    client.subscribe(:option_set)
    client.ui_attach(999, 999, {ext_cmdline: true, ext_messages: true})
    client.subscribe(:option_set)
  end
end

But how do I actually register a callback for this? client.subscribe does not take any block arguments.

subscribe() is kinda useless. After you ui_attach, all UI events will be sent to the channel as redraw events. :help ui-events explains more and shows an example.

authors: Huluk alexgenco justinmk

repo: neovim/neovim-ruby


text:
rust_analyzer get_root_dir fails assert

Description
When trying to get the root dir of the current Rust project it fails with the error:
E5108: Error executing lua ...ig/lua/lspconfig/server_configurations/rust_analyzer.lua:14: assertion failed!
stack traceback:
        [C]: in function 'assert'
        ...ig/lua/lspconfig/server_configurations/rust_analyzer.lua:14: in function 'get_workspace_dir'
        ...ig/lua/lspconfig/server_configurations/rust_analyzer.lua:63: in function 'get_root_dir'
        [string ":lua"]:1: in main chunk

Example command: :lua print(require('lspconfig')["rust_analyzer"].get_root_dir(vim.fn.getcwd()))
Neovim version
NVIM v0.9.0
Build type: Release
LuaJIT 2.1.0-beta3
Nvim-lspconfig version
No response
Operating system and version
Arch Linux (6.3.2)
Affected language servers
rust_analyzer
Steps to reproduce

Create a random project cargo new test-error
cd test-error
nvim src/main.rs
Run :lua print(require('lspconfig')["rust_analyzer"].get_root_dir(vim.fn.getcwd()))

Actual behavior
Crash
Expected behavior
Not a crash, get the root dir printed.
Minimal config
???

LSP log

you can't run it in cmdline it's async must run in a coroutine

repo: neovim/nvim-lspconfig