Item frame error.

i was not sure if i needed to open a new error so i did sorry to bother you.
https://youtu.be/gnGsrnFId5M Here is a link to me on my server showing the error. hope this helps :)
-Pocketmine 3.2.0
-Php 7.2
-banknotedev-7.phar

TinyPixel.us.to (server)

oh! now i get it ok sorry i will see what i can do to fix it

Finally fixed. Banknote collection won't work on these blocks:
(so you don't accidently collect it while eg. opening a chest)

Item Frame
Anvil
Crafting Table
Furnace
Chest
Brewing Stand
Cake
Wooden Door
Wooden Button
Stone Button
Enchanting Table
Ender Chest
Fence Gate
Iron Door
Stonecutter
Trapped Chest
Wooden Trapdoor
Bed

Thank you for posting the issue and don't worry it didn't bother me

the fix, together with some additions has been submitted, but a newer version is already in the works.

Thanks love this plugin!

No problem!


typo

Describe the bug
There is a typo on guild . see attached

Steps to reproduce
Steps to reproduce here.
Spam policy

[X] I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

twitter API is not working I guess

We are not responsible for the Guild codebase.

We are not responsible for the Guild codebase.

i though it would be good to let you guys know and whilst you are not responsible this definitely looks bad because taiko is involved in this in an indirect way. If its  all good for you , then fine by me


T04a.01 activity_child.xml removed

Removed activity_child.xml because it should be created by the student in the TODO steps 1-5.
It's the solution to these steps except the ChildActivity.java is missing.

Same as #29 but for student branch

Thanks for the flags! Unfortunately pull requests don't really work in this repository, but I addressed the lesson 5 issue in https://github.com/udacity/ud851-Exercises/commit/91f6bc975a72211134b975e062eec5907524ab49 and the lesson 4 issue in https://github.com/udacity/ud851-Exercises/commit/e3d664612a50d5e7a074c59732ec397fc1ce2dad


cblrepo does not add install option to PKGBUILD

I am working in archhaskell/habs, trying to add a few packages.
Rebuilding every package in the docker container, I repeatedly runs into the following sort of issue:
:: Proceed with installation? [Y/n]
:: Retrieving packages...
 haskell-extensible-excepti...    31.2 KiB  0.00B/s 00:00 [###############################] 100%
[...]
:: Processing package changes...
(1/2) installing haskell-extensible-exceptions            [###############################] 100%
[...]
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading alsa-core-<IP_ADDRESS>.tar.gz...
[...]
  -> Found original.cabal
==> Validating source files with sha256sums...
    alsa-core-<IP_ADDRESS>.tar.gz ... Passed
    original.cabal ... Passed
==> Extracting sources...
  -> Extracting alsa-core-<IP_ADDRESS>.tar.gz with bsdtar
bsdtar: Failed to set default locale
==> Starting prepare()...
==> Starting build()...
Configuring alsa-core-<IP_ADDRESS>...
Setup: Encountered missing dependencies:
extensible-exceptions >=0.1.1 && <0.2
==> ERROR: A failure occurred in build().
    Aborting...
*** ERROR: Trapped ERR, something went very wrong.

In this example, despite extensible-exceptions having been installed from a freshly built package, the next package build can't find it. I can work around the issue by restarting the container and manually running the register.sh script for that package, after which the build for that package succeeds, only to fail on the next similar issue.
$ docker start blissful_mcnulty
$ docker exec -it blissful_mcnulty sudo bash -x /usr/share/haskell/haskell-extensible-exceptions/register.sh
$ docker attach blissful_mcnulty
==> Finished making: haskell-alsa-core <IP_ADDRESS>.x0-252 (Sat Feb 17 04:44:01 UTC 2018)
==> Extracting database to a temporary location...
bsdtar: Failed to set default locale
==> Extracting database to a temporary location...
bsdtar: Failed to set default locale
==> Adding package 'haskell-alsa-core-<IP_ADDRESS>.x0-252-x86_64.pkg.tar.xz'

Digging down, I can see that haskell-extensible-exceptions (created with cblrepo pkgbuild extensible-exceptions) has a haskell-extensible-exceptions.install which should call the register.sh script properly in the post_install hook. However, the PKGBUILD for this module never mentions the install script, which is therefore ignored.
This seems to be an issue with cblrepo, which fails to add this install section to the PKGBUILD.

Ah... I was using cblrepo from the standard repos (cblrepo 0.24.0-62), replacing it with  cblrepo-0.24.0.x0-11-x86_64 and recreating the PKGBUILDs fixed the issue.
I'm curious why, though, as it seems to be a similar version 🤔 .

I don't know why that would ever happen, it is indeed very strange!
However, since it isn't our package that is broken I'll close this issue :)


Cannot Import 3D City Model using Unreal SDK 2.2.1

Sorry for using English, I can't write in Japanese well.
I am unable to load a mesh using the Unreal SDK. I have tried both local import and server import and they both cause the editor to crash.
OS: MacOS 14.5 ARM
Unreal: Unreal 5.3.2
Plateau: PLATEAU SDK for Unreal v2.2.1
Steps to reproduce:
Started with blank project
Then followed the steps in https://project-plateau.github.io/PLATEAU-SDK-for-Unreal/manual/ImportCityModels.html to load from server.
Selected one mesh code area (Shibuya: 53393596)
Plugin starts importing, then the editor crashes with the following output.
LoginId:d55a41640d47eafb12bb25840894d795
EpicAccountId:b66069337c5a4873b98097153cbafd8a
Caught signal
Unknown() Address = 0x1810b2a60 (filename not found) [in libsystem_kernel.dylib]
Unknown() Address = 0x180ff7a30 (filename not found) [in libsystem_c.dylib]
Unknown() Address = 0x1810a1d08 (filename not found) [in libc++abi.dylib]
Unknown() Address = 0x181091fc0 (filename not found) [in libc++abi.dylib]
Unknown() Address = 0x180d301e0 (filename not found) [in libobjc.A.dylib]
Unknown() Address = 0x1810a10cc (filename not found) [in libc++abi.dylib]
Unknown() Address = 0x1810a4348 (filename not found) [in libc++abi.dylib]
Unknown() Address = 0x1810a428c (filename not found) [in libc++abi.dylib]
xercesc_4_0::DefaultHandler::fatalError(xercesc_4_0::SAXParseException const&) Address = 0x40e501fd4 (filename not found) [in UnrealEditor-PLATEAURuntime.dylib]
xercesc_4_0::SAX2XMLReaderImpl::error(unsigned int, char16_t const*, xercesc_4_0::XMLErrorReporter::ErrTypes, char16_t const*, char16_t const*, char16_t const*, unsigned long long, unsigned long long) Address = 0x40e6b3848 (filename not found) [in UnrealEditor-PLATEAURuntime.dylib]
xercesc_4_0::XMLScanner::emitError(xercesc_4_0::XMLErrs::Codes) Address = 0x40e686644 (filename not found) [in UnrealEditor-PLATEAURuntime.dylib]
xercesc_4_0::XMLScanner::scanProlog() Address = 0x40e6864c8 (filename not found) [in UnrealEditor-PLATEAURuntime.dylib]
xercesc_4_0::IGXMLScanner::scanDocument(xercesc_4_0::InputSource const&) Address = 0x40e65076c (filename not found) [in UnrealEditor-PLATEAURuntime.dylib]
xercesc_4_0::SAX2XMLReaderImpl::parse(xercesc_4_0::InputSource const&) Address = 0x40e6b0630 (filename not found) [in UnrealEditor-PLATEAURuntime.dylib]
citygml::parse(xercesc_4_0::InputSource&, citygml::ParserParams const&, std::__1::shared_ptrcitygml::CityGMLLogger, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator>) Address = 0x40e50017c (filename not found) [in UnrealEditor-PLATEAURuntime.dylib]
citygml::load(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&, citygml::ParserParams const&, std::__1::shared_ptrcitygml::CityGMLLogger) Address = 0x40e500708 (filename not found) [in UnrealEditor-PLATEAURuntime.dylib]
FCityModelLoaderImpl::ParseCityGml(FString const&) Address = 0x40f0e950c [/Users/saji/Repo/Plateau/Plugins/PLATEAU-SDK-for-Unreal/Source/PLATEAURuntime/Private/PLATEAUCityModelLoader.cpp, line 137] [in UnrealEditor-PLATEAURuntime.dylib]
UE::Core::Private::Function::TFunctionRefCaller<APLATEAUCityModelLoader::LoadAsync(bool)::$_6::operator()()::'lambda7'(), bool ()>::Call(void*) Address = 0x40f0e85e4 [/Users/Shared/Epic Games/UE_5.3/Engine/Source/Runtime/Core/Public/Templates/Function.h, line 470] [in UnrealEditor-PLATEAURuntime.dylib]
TAsyncRunnable::Run() Address = 0x40f0eb1a0 [/Users/Shared/Epic Games/UE_5.3/Engine/Source/Runtime/Core/Public/Async/Async.h, line 457] [in UnrealEditor-PLATEAURuntime.dylib]
FRunnableThreadPThread::Run() Address = 0x10824ce4c (filename not found) [in UnrealEditor-Core.dylib]
FRunnableThreadPThread::_ThreadProc(void*) Address = 0x1081ade50 (filename not found) [in UnrealEditor-Core.dylib]
Unknown() Address = 0x1810eaf94 (filename not found) [in libsystem_pthread.dylib]
Unknown() Address = 0x1810e5d34 (filename not found) [in libsystem_pthread.dylib]

We apologize for the inconvenience regarding PLATEAU SDK for Unreal.
Currently, there is a bug that causes Unreal Engine to crash when importing 地下街(underground structures). We are currently working on addressing this issue. As a workaround, you can import other city types by unchecking the "インポートする"(Import) option for 地下街(underground structures).


Addition of the code freeze automation

An example of the code freeze PR created on my fork can be found here: https://github.com/frouioui/vitess/pull/125

After commit 628b74a, here is the latest example: https://github.com/frouioui/vitess/pull/127


[#132082633] Use version 0.0.5 of paas-haproxy-release

What
#132082633 - Router HAProxy restarts rsyslog without reason
We want to reduce the number of unnecessary restarts of rsyslog, as the amount of time it takes to restart has been known to cause deployment failures.
This pull request changes our version of the HAProxy release to 0.0.5. This version changes the start script so it only restarts rsyslog if the configuration changes.
How to review

Deploy from this branch.
Check tests pass

Who can review
Anyone but me

Everything good :+1:


a  bug report

Microsoft PowerToys version
0.65.0
Installation method
PowerToys auto-update
Running as admin
None
Area(s) with issue?
Mouse Utilities
Steps to reproduce
首先，打开“鼠标荧光笔”，然后，按下鼠标左键，不要松开。接着，按下触摸板的左键（同时鼠标左键不能松开），此时移动鼠标会发现屏幕上多了一个荧光点，松开鼠标和触摸板（顺序随意），会发现屏幕上多出的荧光点不会消失。
把鼠标和触摸板按下的顺序倒转，也会出现这样的问题。
把鼠标和触摸板按下的键改为右键，也会出现这样的问题。
✔ Expected Behavior
如果已经按下鼠标，那么触摸板的按下不应该再次呈现在屏幕上
❌ Actual Behavior
按下鼠标的情况下按下触摸板上同样的键，会有两个荧光点出现在屏幕上
Other Software
No response

Hi @x-c-o
Thank you for reporting this!
Google translate:

First, turn on the "Mouse Highlighter", then, press the left mouse button and do not release it. Then, press the left button of the touchpad (at the same time, the left button of the mouse cannot be released), at this time, move the mouse and you will find a fluorescent point on the screen. The fluorescent spots will not disappear.
Reversing the order in which the mouse and touchpad are pressed down also causes the same problem.
Change the key pressed by the mouse and touchpad to the right button, and this problem will also occur.

Closing this as a duplicate.
/dup #21099


Is there any way to disable previous dates?

The props disabledDates is not working and I got that the disabledDates works for specific dates, is that correct?

minDate is probably what you are looking for.


fixed bug where basicauth gets used even when not set

Coverage remained the same at 81.25% when pulling 8c95d615a071574d264d508b1769bc8739978a0b on bug/basicauth into c62df51a773c5024bf7d6b799eb737b2108ff5c4 on master.


Update which test script to run

I came across this example through the blog around eager fetches[0] and the readme was wrong. Doesn't hurt to update things.
0 - https://blog.aspect.dev/avoid-eager-fetches

Type of change

Bug fix (change which fixes an issue)
New feature or functionality (change which adds functionality)
Style (white-space, formatting, etc...)
Refactor (a code change that neither fixes a bug or adds a new feature)
Performance (a code change that improves performance)
Documentation (updates to documentation or READMEs)
Chore (any other change that doesn't affect source or test files, such as configuration)

For changes visible to end-users

Breaking change (this change will force users to change their own code or config)
Relevant documentation has been updated
Suggested release notes are provided below:

Test plan

Covered by existing test cases
New test cases added
Manual testing; please provide instructions so we can reproduce:

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


python311Packages.ml-collections: 0.1.1 -> 1.0.0

ZHF: https://github.com/NixOS/nixpkgs/issues/352882
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] 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/)
25.05 Release Notes (or backporting 24.11 and 25.05 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.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 359265

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.ml-collections
python311Packages.ml-collections.dist
python312Packages.ml-collections
python312Packages.ml-collections.dist


disable 2FA wallet option

2FA wallet cannot be supported by CB. Please disable the option from the wallet creation page.

Also disabled multisig for the time being.


Change the order of URIs in zts-svccert

@havetisyan

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner

thank you @havetisyan


Remove unit test that was system-dependent

Fixes issue #50. The test in question assumed
that a JKS key store would return its entries
in a deterministic order when an alias was not
specified, but this may not be true. Removing
the test entirely since there is already a test
that verifies that the functionality is correct
when an alias is explicitly specified.

@akroy , this should fix the issue (it removes the test entirely).

@uschi2000 or @markelliot , can you merge this change once it verifies?
As explained in the comment, the test I'm removing shouldn't be necessary -- I already have a test for the positive case. Although I would like it if I could test for the negative case, if the order in which a key is returned is non-deterministic (or not well-defined), then any test I write for it will always have a chance of failure (since there's always a chance that the correct key will be returned first, which would cause the test to fail)


Trailing space in comment breaks brackets-jscs

If there is a trailing space in a comment an "Unexpected token"-error is created in brackets-jscs.
This is not a problem when running JSCS in commandline.
// This line has a trailing space
function a() {
    return;
}

And here is by the way the .jscs.json-config that was used if that helps
{
    "excludeFiles": ["frontend/app/bower_components", "frontend/node_modules", "frontend/instrument",
                     "frontend/dist", "frontend/.tmp", "frontend/coverage",
                     "backend/node_modules", "backend/coverage"],
    "disallowKeywords": ["with"],
    "disallowKeywordsInComments": ["TODO"],
    "disallowKeywordsOnNewLine": ["else"],
    "disallowMixedSpacesAndTabs": true,
    "disallowMultipleLineStrings": true,
    "disallowNewlineBeforeBlockStatements": true,
    "disallowSpaceAfterPrefixUnaryOperators": ["++", "--", "+", "-", "~", "!"],
    "disallowSpaceBeforePostfixUnaryOperators": ["++", "--"],
    "disallowSpacesInCallExpression": true,
    "disallowSpacesInsideParentheses": true,
    "maximumLineLength": 120,
    "requireBlocksOnNewline": true,
    "requireCapitalizedConstructors": true,
    "requireCommaBeforeLineBreak": true,
    "requireDotNotation": "except_snake_case",
    "requireLineBreakAfterVariableAssignment": true,
    "requireOperatorBeforeLineBreak": true,
    "requireParenthesesAroundIIFE": true,
    "requireSpaceBeforeBlockStatements": true,
    "requireSpaceBeforeKeywords": ["else", "while", "catch"],
    "requireSpaceBeforeObjectValues": true,
    "requireSpaceBetweenArguments": true,
    "requireSpacesInConditionalExpression": true,
    "requireSpacesInForStatement": true,
    "validateLineBreaks": "LF",
    "validateParameterSeparator": ", ",
    "validateQuoteMarks": "'"
}

I have now found that the problem is in

I have now found that the error is in handleJSXJSCS (Probably in JSXTransformer.transform(text, {harmony: true}).code;)
I added some console output to confirm this
console.log('text', text);
console.log('JSXCode', JSXCode);
return handleJSCS(JSXCode, fullPath, config);

Which gives the output:
text // This line has a trailing space
function a() {
    return;
}
JSXCode // This line has a trailing spacefunction a() {
    return;
}

My workaround until it is fixed is to change line 189 in main.js to (since I do not use harmony I hope guess that JSXTransformer.transform is not necessary for me):
return handleJSCS(text, fullPath, config);

Looks like an issue with the JSXTransformer. I have opened a new bug with the Facebook team: https://github.com/facebook/react/issues/3378

I think it is not JSXTransformer, but this line in handleJSXJSCS:
// Trim trailing whitespace
JSXCode = JSXCode.replace(/( +)\n/g, '');

If I remove it it works better.
Also Node-shebangs ( #!/usr/bin/env node\n ) are not handled correctly. It should be ignored if it is in the beginning of a file. I suggest the following in the beginning of the handleJSXJSCS-function:
text = text.replace(/^#!.+\n/m, '');

A fix has been pushed for this. Please try v0.2.2 of the extension.

The first problem is fixed now. But the other one is still a problem, I will create separate issue for that and a pull request.

Now you have a new problem. The rule:
{"disallowTrailingWhitespace": true}

does not work anymore. I will create a new issue for that.


Percentage formate

C3 version 3.5.0
D3 version 3.5.17
Browser Chrome
OS Windows
I have a graph with currency line, with some lines with number format and I want to add a line with percentage format, but I want it to show percents of maximum value. How can I do that?

Some code would be better.

[                 ['data1', 250000, 200000, 160000, 140000, 210000],                 ['data2', 105360, 40000, 100000, 50000, 45000],                 ['data3', 115360, 54000, 145000, 34000, 69000],                 ['data4', 10%, 13%, 16%, 25%, 30%]             ]
I want data4 to display not as 10 + % after it, but as a percentage value from Y (for example, as 100 of 1000, and I want to display points as a percentage of the axis Y).

I believe that's what you looking for? - https://jsfiddle.net/mcd6ucge/346/

@Youfka I believe you can do this something like this, in some generic way, that does not depend on how much elements percent array has
https://jsfiddle.net/aleksey_korotkevich/xv3bL1fm

thank you! It works now (I tried amitozdeol's solution)


make instant

changed to eventlistener on #input
no more button
changed some querySelector's to getElementById
Fixes #7

Awesome.
But I think we should also trigger converting when:

changing the language
change mode (decode/encode)

What do you think?

Ah yeah good idea
I wouldn't make it run when you change the mode, because you might wanna copy the text you just translated and then decrypt it, so if it'd run then you'd get nothing and lose your original string
the language changed is a good idea though

I've updated it

:shipit:


python311Packages.appthreat-vulnerability-db: 5.5.0 -> 5.5.1

Diff: https://github.com/AppThreat/vulnerability-db/compare/refs/tags/v5.5.0...v5.5.1
Changelog: https://github.com/AppThreat/vulnerability-db/releases/tag/v5.5.1
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

6 packages built:

appthreat-depscan
appthreat-depscan.dist
python310Packages.appthreat-vulnerability-db
python310Packages.appthreat-vulnerability-db.dist
python311Packages.appthreat-vulnerability-db
python311Packages.appthreat-vulnerability-db.dist


libinput 1.26.1, Add accel config for pointer acceleration

I was wanting to play with pointer acceleration added in 1.23. I gen'd the latest version 1.26.1.
Add AccelProfile::Custom
Add AccelType
Add AccelConfig
The example I have been testing with:
use std::{
    fs::{File, OpenOptions},
    os::fd::OwnedFd,
    path::Path,
};

use input::{AccelProfile, Libinput, LibinputInterface};

struct Interface;

impl LibinputInterface for Interface {
    fn open_restricted(&mut self, path: &Path, flags: i32) -> Result<OwnedFd, i32> {
        OpenOptions::new()
            .read(true)
            .write(true)
            .open(path)
            .map(|file| file.into())
            .map_err(|err| err.raw_os_error().unwrap())
    }
    fn close_restricted(&mut self, fd: OwnedFd) {
        let _file = File::from(fd);
    }
}

fn main() {
    let device = "/dev/input/event7";
    let mut input = Libinput::new_from_path(Interface);
    let mut device = input.path_add_device(device).expect("to get the device");

    dbg!(&device.name());

    if device.config_accel_is_available() {
        device
            .config_accel_set_profile(AccelProfile::Custom)
            .expect("to set profile to custom");

        let config = input::accel_config::AccelConfig::new(AccelProfile::Custom);

        config
            .set_points(
                input::accel_config::AccelType::Motion,
                0.5,
                4,
                vec![3., 4., 5., 6.],
            )
            .expect("to set points");

        dbg!(device.config_accel_profile().unwrap());

        device.config_accel_apply(config).expect("to apply config");
    }
}

Willing to make some updates of what may be better.
Thanks

Context

https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/775

Thanks for taking the time to review this code. I will make the marked improvements. I minimally made these changes and wasn't sure if they would be accepted.  I can now work to make this acceptable for merging.
Thanks.


There appear to be more DNS names required now

While putting API Management behind Azure Firewall (forced tunnel), we were able to discover additional DNS required via the Azure Firewall logs, including one that would block deployment until it was allowed:
Required (my provisioning failed unless allowed):

azurewatsonanalysis-prod.core.windows.net

Additional Azure Monitor DNS:

shared.regionname.prod.warm.ingestion.monitoring.azure.com (where regionname is the location of APIM)
gcs.prod.warm.ingestion.monitoring.azure.com
global.metrics.nsatc.net

Additional Questions

Also, do we really need to open outbound port 1886 to the AzureCloud service tag? Azure Firewall logs revealed these are https calls to the same DNS as the Diagnostic DNS, can we just limit that to the DNS on the list as well?
Do we need to open certain ports for the "Send to Log Analytics" and "Send to Stream Analytics" diagnostic settings?

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

ID: 8d854b3c-f9f9-7f6a-f889-e19acac2961c
Version Independent ID: ed544e54-d24b-2f37-05b6-8b60eacd2026
Content: How to use Azure API Management with virtual networks
Content Source: articles/api-management/api-management-using-with-vnet.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

@milope
Thanks for your Question! We are currently investigating and will get back on this.

@milope Thanks for bringing this up!
@vladvino @mikebudzynski @miaojiang Could you please confirm the details shared in the OP?

@milope We have assigned this issue to the content author to review and update accordingly.

@solankisamir please review and comment.

Wanted to add, we also just found this one:
prod3-black.prod.microsoftmetrics.com for port 1886.

Wanted to add, we also just found this one:

prod3-black.prod.microsoftmetrics.com for port 1886.

This endpoint is already there in the docs, but it needs to be fixed. Will fix it.
prod3-black.prod3.metrics.microsoftmetrics.com(new)
prod3-black.prod3.metrics.nsatc.net(to be deprecated)
prod3-red.prod3.metrics.microsoftmetrics.com(new)
prod3-red.prod3.metrics.nsatc.net(to be deprecated)

shared.regionname.prod.warm.ingestion.monitoring.azure.com (where regionname is the location of APIM)
gcs.prod.warm.ingestion.monitoring.azure.com
global.metrics.nsatc.net

We have started monitoring this endpoint,

But yes, it needs to be updated in docs.

Required (my provisioning failed unless allowed):
azurewatsonanalysis-prod.core.windows.net

I doubt Azure Watson is a required dependency, if that is the case, we would prefer to disable this hard dependency. Can you follow up with an ICM and data where the deployment failed?

Also, do we really need to open outbound port 1886 to the AzureCloud service tag? Azure Firewall logs revealed these are https calls to the same DNS as the Diagnostic DNS, can we just limit that to the DNS on the list as well?

No, the data for resource Health will not flow if the port 1886 is blocked

Do we need to open certain ports for the "Send to Log Analytics" and "Send to Stream Analytics" diagnostic settings?

I will ask @promoisha on that.

I can try and file that ICM for the watson one. Regarding the port 1886, I guess the question was more centered around if the Service Tag for 1886 really needs to be AzureCloud and not something more narrow like AzureMonitor or the Azure Monitor FQDNs?

@milope we have fixed the documentation. Please close the issue if satisfied.

I will close the incident. Thank you for the update!


[stable/datadog] DD_TAGS is generated with [] surrounding the values

Describe the bug
DD_TAGS is expected to be of the format value: "key:value key2:value2", instead it is value: "[key:value key2:value2]".
Version of Helm and Kubernetes:
version.BuildInfo{Version:"v3.1.2", GitCommit:"d878d4d45863e42fd5cff6743294a11d28a9abce", GitTreeState:"clean", GoVersion:"go1.13.8"}
Which chart:
stable/datadog

Hi @nesl247
Thank you for reporting this issue. We have included a fix in the pull request #22006.
Cedric


support completition of csharp files

Hey, thanks for the PR, but I'm in the middle of some conflicting changes to RoslynHost. Plus I'd rather this be a per document, not the entire host.


Can the current kafka eagle work with kafka2.3.0 and zookeeper 3.5.5 through SSL

HI
we setup the zookeeper 3.5.5 and kafka2.3.0,
and the zookeeper is based on SSL,
can the newest kafka eagle(2019.9.29) support this case.
if support,can you tell me how to configure it.
if not support, is this in plan?

Fixed by kafka-eagle-v1.4.0


server mode for OBS

I'd love to be able to give to 2+ people a URL to use, that'll stream into my OBS as a source (multiple person panel stream)... person A/B/C all connect with a different stream key to the pxy (server mode) endpoint.
then I just add an SRT/RTSP/RTMP source to my OBS scene with the same streamkey they came in with. Browser -> pxy <- OBS
Obviously latency/quality of service is important... so you'd need to benchmark which protocol from pxy to OBS is best... but if the pxy is hosted on the same box/LAN as OBS. figure it shouldn't matter much
open question: Getting the audio between those people which is a challenge, I'd want everybody to hear each other in sync (could use humble or something)

Sorry. quick research would show SRT has listener mode natively out of the box.. if you can support it

Hello @shleeable , the goal of this project (for now) is to serve as a reference implementation for live streams that are proxied between a WebSocket input and an RTMP output. As such, pxy would not support SRT. Perhaps this is something that could be explored more in the future, thank you for your suggestion regardless!


snapcraft: init at 8.0.5

Description of changes
Adds snapcraft, starting at version 8.0.5, which is the latest stable version.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] 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

[x] 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.

Ah, spotted the aarch64 CI failure. I'll take a look soon.

Thank you @drupol 😎


Propagate error instead of panic for take_bytes

Which issue does this PR close?

Closes #.
Rationale for this change

take_bytes can propagate error instead of panic.
What changes are included in this PR?

Changing take_bytes to propagate error.
Are there any user-facing changes?

Thanks @tustvold


Users can't delete triggers once created.

There should be an intuitive way for users to remove a rule once it has been created.

This will be resolved when the support for multiple rules is added. I will have a UI with all existing rules and I will have a delete icon on them.


[ruby] New parser Gem Parser Implementation

Due to the performance and stability issues with a 2-phase LLK parser approach with ANTLR, this branch, developed over the past two weeks, introduces the usage of a parser based approach wrapped in ruby_ast_gen. This Gem is used by many popular Ruby linters and static analysis tools, and is compatible with Ruby versions across 1-3.
We bundle ruby_ast_gen with the frontend under resources, and execute the Ruby code using JRuby to maximize portability. This has a bit of an overhead for short-lived processes, so we have a disabled-by-default --try-local-ruby frontend arg that will attempt to detect and use a compatible native Ruby binary. This is enabled for tests to have them run faster. If the resource is detected to be in a JAR, ruby_ast_gen is written to a temporary directory, from where it is then executed.
Both JRuby and native Ruby runs of ruby_ast_gen far outperform the old ANTLR version, which would often have worst-case performance for some set of language constructs encountered.
Files worth reviewing if needed:

joern-cli/frontends/rubysrc2cpg/src/main/scala/io/joern/rubysrc2cpg/parser/*
joern-cli/frontends/rubysrc2cpg/src/main/scala/io/joern/rubysrc2cpg/RubySrc2Cpg.scala
joern-cli/frontends/rubysrc2cpg/build.sbt

Changes include:

Remove ANTLR implementation
Execute ruby_ast_gen and parse JSON output
Map the JSON output to the same intermediate AST nodes that ANTLR used to avoid changing AstCreation logic
Rename the method name for executable strings (%x{}-style strings) to <operator>.backticks instead of exec as exec technically has different semantics
Trim .code properties to 60 characters to avoid large .code properties. (this is done by ruby_ast_gen)
Added db/migration to default ignored directories

Tests are largely kept the same, and ruby:test is green on codescience after some small .code and .lineNumber tweaks. See dave/ruby/prep-for-ruby-parse-gem.
Co-authored by @AndreiDreyer

I'd prefer if we handled the astgen like we do it in the other frontends, i.e. do not add those 17M binaries to the repo, and instead download them on demand by invoking the astGenDlTask. Most frontends invoke it before compile:
Compile / compile := ((Compile / compile) dependsOn astGenDlTask).value

Bundling this in the resources directory was part of a discussion with Markus, as it would be easier to distribute, and running it with JRuby allows us to be platform independent (so no need to select specific binaries). However, is what you mean that we can still bundle it, but exclude it from Git and download this on compile time?

Putting undiffable binaries in the repo will get us locked again on traffic until Fabs pulls out his credit card. We had this issue already.

However, is what you mean that we can still bundle it, but exclude it from Git and download this on compile time?

By 'bundle' you probably refer something like Universal/packageBin or stage, right? You simply want to make it part of the result, rather than giving the user instructions to download and link it.
So yes, you'll get all of that by just downloading it on demand, there's no need to add those files to the repo afaics.

However, is what you mean that we can still bundle it, but exclude it from Git and download this on compile time?

By 'bundle' you probably refer something like Universal/packageBin or stage, right? You simply want to make it part of the result, rather than giving the user instructions to download and link it. So yes, you'll get all of that by just downloading it on demand, there's no need to add those files to the repo afaics.

Rather, I mean under src/main/resources, none of ruby_ast_gen or its vendored dependencies are binaries.

Right, sorry, yes those are not binaries. But still they take up 17M and it's really not necessary to have them as part of this repo since we merely download them from a third party. So unless there's a benefit to having them as part of this repo I'd like to use the same pattern as for the other astgens and download them on compiler, rather than on git clone.

Ok I've moved to not checking them in, I agree it is a lot of strain on the git history and object in general.
For now, it's still going into resources, so the end-user doesn't need to expect additional downloads. It is about 14MB uncompressed (1.7 MB zip compressed) in resources, which may be a plausible argument to simply have it as the rest of the astGen programs instead of in the JAR.

Thanks! One point I forgot to mention: it would have been 17M for each new version of the astgen, being preserved unnecessarily in the git history forever.
Looks good from my POV and I can approve it. Not sure if anyone else can/should have a review of the frontend code itself. Given that you worked together with @AndreiDreyer it might already be "reviewed-enough".

there's a couple of tests still marked as ignore, is that intended?

I think I'm going to double-check that they are not "newly" ignored - i.e., there were ignored ones from the last parser. Andrei and I are also meeting with Markus tomorrow to check if he is happy, so an approval won't necessarily mean a merge.
Also we are looking into the failing Window tests, seems to be our blocker right now.

We're seeing regressions in our integration tests due to changes around implicit field accesses. Until now, something like params would just be turned into a field access self.params. Now it's turned into a dynamic call params with receiver self.params and argument 0  params. This might be more correct on some level, but it's Kryptonite for Qwiet's dataflow engine.

@maltek I'm seeing it too on ruby:test, there was initially some logic to "guess" what certain identifiers were on the AstCreator side as everything coming from ANTLR was an identifier, however the new parser applies the Ruby logic to automatically determine if something is a call or identifier, and has taken the "right to guess" away from AstCreator.
I think it's best to put off this merge a bit longer until we see green on Qwiet's dataflow engine, I'll have a look at how we can get the old behavior back.

@maltek I've figured out how to get this old behaviour back, and my local ruby:test is green again (had to update a few flow paths back to how they used to be). Of course, will wait for build bot to be green before going ahead, which may be something to look into next week.

@DavidBakerEffendi thank you! That fixed all those regressions, and our results are the same again as before for our test projects. (Depth-first order of a few source/sink nodes has changed, and we'll need to adjust the expected values of - but that's totally fine.)

@maltek In that case, I'll merge here, so we can get the backlog of stability and speed fixes that this brings in sooner rather than later.

Looking good, the schema violation is gone (https://github.com/joernio/joern/issues/5037)
Just a small expectation bump and we'll be green again: https://github.com/ShiftLeftSecurity/codescience/pull/8035


"terminate called after throwing an instance of 'std::runtime_error'   what():  VIDIOC_DQBUF error 19, No such device Aborted (core dumped)"

Required Info

Camera Model
SR300

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 14.04.05 LTS

Kernel Version (Linux Only)
4.4.0-36-generic

Build System
Makefile

./c-tutorial-2-streams
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
    Serial number:<PHONE_NUMBER>87
    Firmware version: <IP_ADDRESS>
terminate called after throwing an instance of 'std::runtime_error'
  what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

Device 0 - Intel RealSense SR300:
 Serial number:<PHONE_NUMBER>87
 Firmware version: <IP_ADDRESS>
 USB Port ID: 2-1
 Supported options:
    COLOR_BACKLIGHT_COMPENSATION : 0 .. 4, 1
    COLOR_BRIGHTNESS : -64 .. 64, 1
    COLOR_CONTRAST : 0 .. 100, 1
    COLOR_EXPOSURE : 0 .. 0, 1
    COLOR_GAIN : 0 .. 128, 1
    COLOR_GAMMA : 100 .. 500, 1
    COLOR_HUE : -180 .. 180, 1
    COLOR_SATURATION : 0 .. 100, 1
    COLOR_SHARPNESS : 0 .. 100, 1
    COLOR_WHITE_BALANCE : 2800 .. 6500, 1
    COLOR_ENABLE_AUTO_EXPOSURE : 0 .. 0, 1
    COLOR_ENABLE_AUTO_WHITE_BALANCE : 0 .. 1, 1
    F200_LASER_POWER : 0 .. 16, 1
    F200_ACCURACY : 1 .. 3, 1
    F200_MOTION_RANGE : 0 .. 100, 1
    F200_FILTER_OPTION : 0 .. 7, 1
    F200_CONFIDENCE_THRESHOLD : 0 .. 15, 1
    SR300_DYNAMIC_FPS : 0 .. 0, 0
    SR300_AUTO_RANGE_ENABLE_MOTION_VERSUS_RANGE : 0 .. 2, 1
    SR300_AUTO_RANGE_ENABLE_LASER : 0 .. 1, 1
    SR300_AUTO_RANGE_MIN_MOTION_VERSUS_RANGE : -32768 .. 32767, 1
    SR300_AUTO_RANGE_MAX_MOTION_VERSUS_RANGE : -32768 .. 32767, 1
    SR300_AUTO_RANGE_START_MOTION_VERSUS_RANGE : -32768 .. 32767, 1
    SR300_AUTO_RANGE_MIN_LASER : -32768 .. 32767, 1
    SR300_AUTO_RANGE_MAX_LASER : -32768 .. 32767, 1
    SR300_AUTO_RANGE_START_LASER : -32768 .. 32767, 1
    SR300_AUTO_RANGE_UPPER_THRESHOLD : 0 .. 65535, 1
    SR300_AUTO_RANGE_LOWER_THRESHOLD : 0 .. 65535, 1
 Stream DEPTH - 9 modes:
  640   x 480   @ 60Hz  Z16 67.9 x 53.6 degrees
  640   x 480   @ 30Hz  Z16 67.9 x 53.6 degrees
  640   x 480   @ 15Hz  Z16 67.9 x 53.6 degrees
  640   x 480   @ 5Hz   Z16 67.9 x 53.6 degrees
  640   x 240   @ 110Hz Z16 67.9 x 53.6 degrees
  640   x 240   @ 60Hz  Z16 67.9 x 53.6 degrees
  640   x 240   @ 30Hz  Z16 67.9 x 53.6 degrees
  640   x 240   @ 15Hz  Z16 67.9 x 53.6 degrees
  640   x 240   @ 5Hz   Z16 67.9 x 53.6 degrees
 Stream COLOR - 245 modes:
  1920  x 1080  @ 30Hz  YUYV    69.4 x 42.6 degrees
  1920  x 1080  @ 30Hz  RGB8    69.4 x 42.6 degrees
  1920  x 1080  @ 30Hz  BGR8    69.4 x 42.6 degrees
  1920  x 1080  @ 30Hz  RGBA8   69.4 x 42.6 degrees
  1920  x 1080  @ 30Hz  BGRA8   69.4 x 42.6 degrees
  1920  x 1080  @ 30Hz  Y8  69.4 x 42.6 degrees
  1920  x 1080  @ 30Hz  Y16 69.4 x 42.6 degrees
  1920  x 1080  @ 15Hz  YUYV    69.4 x 42.6 degrees
  1920  x 1080  @ 15Hz  RGB8    69.4 x 42.6 degrees
  1920  x 1080  @ 15Hz  BGR8    69.4 x 42.6 degrees
  1920  x 1080  @ 15Hz  RGBA8   69.4 x 42.6 degrees
  1920  x 1080  @ 15Hz  BGRA8   69.4 x 42.6 degrees
  1920  x 1080  @ 15Hz  Y8  69.4 x 42.6 degrees
  1920  x 1080  @ 15Hz  Y16 69.4 x 42.6 degrees
  1920  x 1080  @ 5Hz   YUYV    69.4 x 42.6 degrees
  1920  x 1080  @ 5Hz   RGB8    69.4 x 42.6 degrees
  1920  x 1080  @ 5Hz   BGR8    69.4 x 42.6 degrees
  1920  x 1080  @ 5Hz   RGBA8   69.4 x 42.6 degrees
  1920  x 1080  @ 5Hz   BGRA8   69.4 x 42.6 degrees
  1920  x 1080  @ 5Hz   Y8  69.4 x 42.6 degrees
  1920  x 1080  @ 5Hz   Y16 69.4 x 42.6 degrees
  1280  x 720   @ 60Hz  YUYV    69.4 x 42.6 degrees
  1280  x 720   @ 60Hz  RGB8    69.4 x 42.6 degrees
  1280  x 720   @ 60Hz  BGR8    69.4 x 42.6 degrees
  1280  x 720   @ 60Hz  RGBA8   69.4 x 42.6 degrees
  1280  x 720   @ 60Hz  BGRA8   69.4 x 42.6 degrees
  1280  x 720   @ 60Hz  Y8  69.4 x 42.6 degrees
  1280  x 720   @ 60Hz  Y16 69.4 x 42.6 degrees
  1280  x 720   @ 30Hz  YUYV    69.4 x 42.6 degrees
  1280  x 720   @ 30Hz  RGB8    69.4 x 42.6 degrees
  1280  x 720   @ 30Hz  BGR8    69.4 x 42.6 degrees
  1280  x 720   @ 30Hz  RGBA8   69.4 x 42.6 degrees
  1280  x 720   @ 30Hz  BGRA8   69.4 x 42.6 degrees
  1280  x 720   @ 30Hz  Y8  69.4 x 42.6 degrees
  1280  x 720   @ 30Hz  Y16 69.4 x 42.6 degrees
  1280  x 720   @ 15Hz  YUYV    69.4 x 42.6 degrees
  1280  x 720   @ 15Hz  RGB8    69.4 x 42.6 degrees
  1280  x 720   @ 15Hz  BGR8    69.4 x 42.6 degrees
  1280  x 720   @ 15Hz  RGBA8   69.4 x 42.6 degrees
  1280  x 720   @ 15Hz  BGRA8   69.4 x 42.6 degrees
  1280  x 720   @ 15Hz  Y8  69.4 x 42.6 degrees
  1280  x 720   @ 15Hz  Y16 69.4 x 42.6 degrees
  1280  x 720   @ 5Hz   YUYV    69.4 x 42.6 degrees
  1280  x 720   @ 5Hz   RGB8    69.4 x 42.6 degrees
  1280  x 720   @ 5Hz   BGR8    69.4 x 42.6 degrees
  1280  x 720   @ 5Hz   RGBA8   69.4 x 42.6 degrees
  1280  x 720   @ 5Hz   BGRA8   69.4 x 42.6 degrees
  1280  x 720   @ 5Hz   Y8  69.4 x 42.6 degrees
  1280  x 720   @ 5Hz   Y16 69.4 x 42.6 degrees
  960   x 540   @ 60Hz  YUYV    69.4 x 42.6 degrees
  960   x 540   @ 60Hz  RGB8    69.4 x 42.6 degrees
  960   x 540   @ 60Hz  BGR8    69.4 x 42.6 degrees
  960   x 540   @ 60Hz  RGBA8   69.4 x 42.6 degrees
  960   x 540   @ 60Hz  BGRA8   69.4 x 42.6 degrees
  960   x 540   @ 60Hz  Y8  69.4 x 42.6 degrees
  960   x 540   @ 60Hz  Y16 69.4 x 42.6 degrees
  960   x 540   @ 30Hz  YUYV    69.4 x 42.6 degrees
  960   x 540   @ 30Hz  RGB8    69.4 x 42.6 degrees
  960   x 540   @ 30Hz  BGR8    69.4 x 42.6 degrees
  960   x 540   @ 30Hz  RGBA8   69.4 x 42.6 degrees
  960   x 540   @ 30Hz  BGRA8   69.4 x 42.6 degrees
  960   x 540   @ 30Hz  Y8  69.4 x 42.6 degrees
  960   x 540   @ 30Hz  Y16 69.4 x 42.6 degrees
  960   x 540   @ 15Hz  YUYV    69.4 x 42.6 degrees
  960   x 540   @ 15Hz  RGB8    69.4 x 42.6 degrees
  960   x 540   @ 15Hz  BGR8    69.4 x 42.6 degrees
  960   x 540   @ 15Hz  RGBA8   69.4 x 42.6 degrees
  960   x 540   @ 15Hz  BGRA8   69.4 x 42.6 degrees
  960   x 540   @ 15Hz  Y8  69.4 x 42.6 degrees
  960   x 540   @ 15Hz  Y16 69.4 x 42.6 degrees
  960   x 540   @ 5Hz   YUYV    69.4 x 42.6 degrees
  960   x 540   @ 5Hz   RGB8    69.4 x 42.6 degrees
  960   x 540   @ 5Hz   BGR8    69.4 x 42.6 degrees
  960   x 540   @ 5Hz   RGBA8   69.4 x 42.6 degrees
  960   x 540   @ 5Hz   BGRA8   69.4 x 42.6 degrees
  960   x 540   @ 5Hz   Y8  69.4 x 42.6 degrees
  960   x 540   @ 5Hz   Y16 69.4 x 42.6 degrees
  848   x 480   @ 60Hz  YUYV    69.4 x 42.6 degrees
  848   x 480   @ 60Hz  RGB8    69.4 x 42.6 degrees
  848   x 480   @ 60Hz  BGR8    69.4 x 42.6 degrees
  848   x 480   @ 60Hz  RGBA8   69.4 x 42.6 degrees
  848   x 480   @ 60Hz  BGRA8   69.4 x 42.6 degrees
  848   x 480   @ 60Hz  Y8  69.4 x 42.6 degrees
  848   x 480   @ 60Hz  Y16 69.4 x 42.6 degrees
  848   x 480   @ 30Hz  YUYV    69.4 x 42.6 degrees
  848   x 480   @ 30Hz  RGB8    69.4 x 42.6 degrees
  848   x 480   @ 30Hz  BGR8    69.4 x 42.6 degrees
  848   x 480   @ 30Hz  RGBA8   69.4 x 42.6 degrees
  848   x 480   @ 30Hz  BGRA8   69.4 x 42.6 degrees
  848   x 480   @ 30Hz  Y8  69.4 x 42.6 degrees
  848   x 480   @ 30Hz  Y16 69.4 x 42.6 degrees
  848   x 480   @ 15Hz  YUYV    69.4 x 42.6 degrees
  848   x 480   @ 15Hz  RGB8    69.4 x 42.6 degrees
  848   x 480   @ 15Hz  BGR8    69.4 x 42.6 degrees
  848   x 480   @ 15Hz  RGBA8   69.4 x 42.6 degrees
  848   x 480   @ 15Hz  BGRA8   69.4 x 42.6 degrees
  848   x 480   @ 15Hz  Y8  69.4 x 42.6 degrees
  848   x 480   @ 15Hz  Y16 69.4 x 42.6 degrees
  848   x 480   @ 5Hz   YUYV    69.4 x 42.6 degrees
  848   x 480   @ 5Hz   RGB8    69.4 x 42.6 degrees
  848   x 480   @ 5Hz   BGR8    69.4 x 42.6 degrees
  848   x 480   @ 5Hz   RGBA8   69.4 x 42.6 degrees
  848   x 480   @ 5Hz   BGRA8   69.4 x 42.6 degrees
  848   x 480   @ 5Hz   Y8  69.4 x 42.6 degrees
  848   x 480   @ 5Hz   Y16 69.4 x 42.6 degrees
  640   x 480   @ 60Hz  YUYV    54.9 x 42.6 degrees
  640   x 480   @ 60Hz  RGB8    54.9 x 42.6 degrees
  640   x 480   @ 60Hz  BGR8    54.9 x 42.6 degrees
  640   x 480   @ 60Hz  RGBA8   54.9 x 42.6 degrees
  640   x 480   @ 60Hz  BGRA8   54.9 x 42.6 degrees
  640   x 480   @ 60Hz  Y8  54.9 x 42.6 degrees
  640   x 480   @ 60Hz  Y16 54.9 x 42.6 degrees
  640   x 480   @ 30Hz  YUYV    54.9 x 42.6 degrees
  640   x 480   @ 30Hz  RGB8    54.9 x 42.6 degrees
  640   x 480   @ 30Hz  BGR8    54.9 x 42.6 degrees
  640   x 480   @ 30Hz  RGBA8   54.9 x 42.6 degrees
  640   x 480   @ 30Hz  BGRA8   54.9 x 42.6 degrees
  640   x 480   @ 30Hz  Y8  54.9 x 42.6 degrees
  640   x 480   @ 30Hz  Y16 54.9 x 42.6 degrees
  640   x 480   @ 15Hz  YUYV    54.9 x 42.6 degrees
  640   x 480   @ 15Hz  RGB8    54.9 x 42.6 degrees
  640   x 480   @ 15Hz  BGR8    54.9 x 42.6 degrees
  640   x 480   @ 15Hz  RGBA8   54.9 x 42.6 degrees
  640   x 480   @ 15Hz  BGRA8   54.9 x 42.6 degrees
  640   x 480   @ 15Hz  Y8  54.9 x 42.6 degrees
  640   x 480   @ 15Hz  Y16 54.9 x 42.6 degrees
  640   x 480   @ 5Hz   YUYV    54.9 x 42.6 degrees
  640   x 480   @ 5Hz   RGB8    54.9 x 42.6 degrees
  640   x 480   @ 5Hz   BGR8    54.9 x 42.6 degrees
  640   x 480   @ 5Hz   RGBA8   54.9 x 42.6 degrees
  640   x 480   @ 5Hz   BGRA8   54.9 x 42.6 degrees
  640   x 480   @ 5Hz   Y8  54.9 x 42.6 degrees
  640   x 480   @ 5Hz   Y16 54.9 x 42.6 degrees
  640   x 360   @ 60Hz  YUYV    69.4 x 42.6 degrees
  640   x 360   @ 60Hz  RGB8    69.4 x 42.6 degrees
  640   x 360   @ 60Hz  BGR8    69.4 x 42.6 degrees
  640   x 360   @ 60Hz  RGBA8   69.4 x 42.6 degrees
  640   x 360   @ 60Hz  BGRA8   69.4 x 42.6 degrees
  640   x 360   @ 60Hz  Y8  69.4 x 42.6 degrees
  640   x 360   @ 60Hz  Y16 69.4 x 42.6 degrees
  640   x 360   @ 30Hz  YUYV    69.4 x 42.6 degrees
  640   x 360   @ 30Hz  RGB8    69.4 x 42.6 degrees
  640   x 360   @ 30Hz  BGR8    69.4 x 42.6 degrees
  640   x 360   @ 30Hz  RGBA8   69.4 x 42.6 degrees
  640   x 360   @ 30Hz  BGRA8   69.4 x 42.6 degrees
  640   x 360   @ 30Hz  Y8  69.4 x 42.6 degrees
  640   x 360   @ 30Hz  Y16 69.4 x 42.6 degrees
  640   x 360   @ 15Hz  YUYV    69.4 x 42.6 degrees
  640   x 360   @ 15Hz  RGB8    69.4 x 42.6 degrees
  640   x 360   @ 15Hz  BGR8    69.4 x 42.6 degrees
  640   x 360   @ 15Hz  RGBA8   69.4 x 42.6 degrees
  640   x 360   @ 15Hz  BGRA8   69.4 x 42.6 degrees
  640   x 360   @ 15Hz  Y8  69.4 x 42.6 degrees
  640   x 360   @ 15Hz  Y16 69.4 x 42.6 degrees
  640   x 360   @ 5Hz   YUYV    69.4 x 42.6 degrees
  640   x 360   @ 5Hz   RGB8    69.4 x 42.6 degrees
  640   x 360   @ 5Hz   BGR8    69.4 x 42.6 degrees
  640   x 360   @ 5Hz   RGBA8   69.4 x 42.6 degrees
  640   x 360   @ 5Hz   BGRA8   69.4 x 42.6 degrees
  640   x 360   @ 5Hz   Y8  69.4 x 42.6 degrees
  640   x 360   @ 5Hz   Y16 69.4 x 42.6 degrees
  424   x 240   @ 60Hz  YUYV    69.4 x 42.6 degrees
  424   x 240   @ 60Hz  RGB8    69.4 x 42.6 degrees
  424   x 240   @ 60Hz  BGR8    69.4 x 42.6 degrees
  424   x 240   @ 60Hz  RGBA8   69.4 x 42.6 degrees
  424   x 240   @ 60Hz  BGRA8   69.4 x 42.6 degrees
  424   x 240   @ 60Hz  Y8  69.4 x 42.6 degrees
  424   x 240   @ 60Hz  Y16 69.4 x 42.6 degrees
  424   x 240   @ 30Hz  YUYV    69.4 x 42.6 degrees
  424   x 240   @ 30Hz  RGB8    69.4 x 42.6 degrees
  424   x 240   @ 30Hz  BGR8    69.4 x 42.6 degrees
  424   x 240   @ 30Hz  RGBA8   69.4 x 42.6 degrees
  424   x 240   @ 30Hz  BGRA8   69.4 x 42.6 degrees
  424   x 240   @ 30Hz  Y8  69.4 x 42.6 degrees
  424   x 240   @ 30Hz  Y16 69.4 x 42.6 degrees
  424   x 240   @ 15Hz  YUYV    69.4 x 42.6 degrees
  424   x 240   @ 15Hz  RGB8    69.4 x 42.6 degrees
  424   x 240   @ 15Hz  BGR8    69.4 x 42.6 degrees
  424   x 240   @ 15Hz  RGBA8   69.4 x 42.6 degrees
  424   x 240   @ 15Hz  BGRA8   69.4 x 42.6 degrees
  424   x 240   @ 15Hz  Y8  69.4 x 42.6 degrees
  424   x 240   @ 15Hz  Y16 69.4 x 42.6 degrees
  424   x 240   @ 5Hz   YUYV    69.4 x 42.6 degrees
  424   x 240   @ 5Hz   RGB8    69.4 x 42.6 degrees
  424   x 240   @ 5Hz   BGR8    69.4 x 42.6 degrees
  424   x 240   @ 5Hz   RGBA8   69.4 x 42.6 degrees
  424   x 240   @ 5Hz   BGRA8   69.4 x 42.6 degrees
  424   x 240   @ 5Hz   Y8  69.4 x 42.6 degrees
  424   x 240   @ 5Hz   Y16 69.4 x 42.6 degrees
  320   x 240   @ 60Hz  YUYV    54.9 x 42.6 degrees
  320   x 240   @ 60Hz  RGB8    54.9 x 42.6 degrees
  320   x 240   @ 60Hz  BGR8    54.9 x 42.6 degrees
  320   x 240   @ 60Hz  RGBA8   54.9 x 42.6 degrees
  320   x 240   @ 60Hz  BGRA8   54.9 x 42.6 degrees
  320   x 240   @ 60Hz  Y8  54.9 x 42.6 degrees
  320   x 240   @ 60Hz  Y16 54.9 x 42.6 degrees
  320   x 240   @ 30Hz  YUYV    54.9 x 42.6 degrees
  320   x 240   @ 30Hz  RGB8    54.9 x 42.6 degrees
  320   x 240   @ 30Hz  BGR8    54.9 x 42.6 degrees
  320   x 240   @ 30Hz  RGBA8   54.9 x 42.6 degrees
  320   x 240   @ 30Hz  BGRA8   54.9 x 42.6 degrees
  320   x 240   @ 30Hz  Y8  54.9 x 42.6 degrees
  320   x 240   @ 30Hz  Y16 54.9 x 42.6 degrees
  320   x 240   @ 15Hz  YUYV    54.9 x 42.6 degrees
  320   x 240   @ 15Hz  RGB8    54.9 x 42.6 degrees
  320   x 240   @ 15Hz  BGR8    54.9 x 42.6 degrees
  320   x 240   @ 15Hz  RGBA8   54.9 x 42.6 degrees
  320   x 240   @ 15Hz  BGRA8   54.9 x 42.6 degrees
  320   x 240   @ 15Hz  Y8  54.9 x 42.6 degrees
  320   x 240   @ 15Hz  Y16 54.9 x 42.6 degrees
  320   x 240   @ 5Hz   YUYV    54.9 x 42.6 degrees
  320   x 240   @ 5Hz   RGB8    54.9 x 42.6 degrees
  320   x 240   @ 5Hz   BGR8    54.9 x 42.6 degrees
  320   x 240   @ 5Hz   RGBA8   54.9 x 42.6 degrees
  320   x 240   @ 5Hz   BGRA8   54.9 x 42.6 degrees
  320   x 240   @ 5Hz   Y8  54.9 x 42.6 degrees
  320   x 240   @ 5Hz   Y16 54.9 x 42.6 degrees
  320   x 180   @ 60Hz  YUYV    69.4 x 42.6 degrees
  320   x 180   @ 60Hz  RGB8    69.4 x 42.6 degrees
  320   x 180   @ 60Hz  BGR8    69.4 x 42.6 degrees
  320   x 180   @ 60Hz  RGBA8   69.4 x 42.6 degrees
  320   x 180   @ 60Hz  BGRA8   69.4 x 42.6 degrees
  320   x 180   @ 60Hz  Y8  69.4 x 42.6 degrees
  320   x 180   @ 60Hz  Y16 69.4 x 42.6 degrees
  320   x 180   @ 30Hz  YUYV    69.4 x 42.6 degrees
  320   x 180   @ 30Hz  RGB8    69.4 x 42.6 degrees
  320   x 180   @ 30Hz  BGR8    69.4 x 42.6 degrees
  320   x 180   @ 30Hz  RGBA8   69.4 x 42.6 degrees
  320   x 180   @ 30Hz  BGRA8   69.4 x 42.6 degrees
  320   x 180   @ 30Hz  Y8  69.4 x 42.6 degrees
  320   x 180   @ 30Hz  Y16 69.4 x 42.6 degrees
  320   x 180   @ 15Hz  YUYV    69.4 x 42.6 degrees
  320   x 180   @ 15Hz  RGB8    69.4 x 42.6 degrees
  320   x 180   @ 15Hz  BGR8    69.4 x 42.6 degrees
  320   x 180   @ 15Hz  RGBA8   69.4 x 42.6 degrees
  320   x 180   @ 15Hz  BGRA8   69.4 x 42.6 degrees
  320   x 180   @ 15Hz  Y8  69.4 x 42.6 degrees
  320   x 180   @ 15Hz  Y16 69.4 x 42.6 degrees
  320   x 180   @ 5Hz   YUYV    69.4 x 42.6 degrees
  320   x 180   @ 5Hz   RGB8    69.4 x 42.6 degrees
  320   x 180   @ 5Hz   BGR8    69.4 x 42.6 degrees
  320   x 180   @ 5Hz   RGBA8   69.4 x 42.6 degrees
  320   x 180   @ 5Hz   BGRA8   69.4 x 42.6 degrees
  320   x 180   @ 5Hz   Y8  69.4 x 42.6 degrees
  320   x 180   @ 5Hz   Y16 69.4 x 42.6 degrees
 Stream INFRARED - 22 modes:
  640   x 480   @ 200Hz Y8  67.9 x 53.6 degrees
  640   x 480   @ 200Hz Y16 67.9 x 53.6 degrees
  640   x 480   @ 120Hz Y8  67.9 x 53.6 degrees
  640   x 480   @ 120Hz Y16 67.9 x 53.6 degrees
  640   x 480   @ 60Hz  Y8  67.9 x 53.6 degrees
  640   x 480   @ 60Hz  Y16 67.9 x 53.6 degrees
  640   x 480   @ 30Hz  Y8  67.9 x 53.6 degrees
  640   x 480   @ 30Hz  Y16 67.9 x 53.6 degrees
  640   x 480   @ 15Hz  Y8  67.9 x 53.6 degrees
  640   x 480   @ 15Hz  Y16 67.9 x 53.6 degrees
  640   x 480   @ 5Hz   Y8  67.9 x 53.6 degrees
  640   x 480   @ 5Hz   Y16 67.9 x 53.6 degrees
  640   x 240   @ 110Hz Y8  67.9 x 53.6 degrees
  640   x 240   @ 110Hz Y16 67.9 x 53.6 degrees
  640   x 240   @ 60Hz  Y8  67.9 x 53.6 degrees
  640   x 240   @ 60Hz  Y16 67.9 x 53.6 degrees
  640   x 240   @ 30Hz  Y8  67.9 x 53.6 degrees
  640   x 240   @ 30Hz  Y16 67.9 x 53.6 degrees
  640   x 240   @ 15Hz  Y8  67.9 x 53.6 degrees
  640   x 240   @ 15Hz  Y16 67.9 x 53.6 degrees
  640   x 240   @ 5Hz   Y8  67.9 x 53.6 degrees
  640   x 240   @ 5Hz   Y16 67.9 x 53.6 degrees

 ./cpp-pointcloud
terminate called after throwing an instance of 'std::runtime_error'
  what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-tutorial-2-streams
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
    Serial number:<PHONE_NUMBER>87
    Firmware version: <IP_ADDRESS>
Device does not provide infrared2 stream.
terminate called after throwing an instance of 'std::runtime_error'
  what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./c-tutorial-2-streams
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
    Serial number:<PHONE_NUMBER>87
    Firmware version: <IP_ADDRESS>
terminate called after throwing an instance of 'std::runtime_error'
  what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./c-tutorial-2-streams
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
    Serial number:<PHONE_NUMBER>87
    Firmware version: <IP_ADDRESS>
terminate called after throwing an instance of 'std::runtime_error'
  what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-capture
Capturing DEPTH at 640 x 480, fov = 67.9 x 53.6, distortion = INVERSE_BROWN_CONRADY
Capturing COLOR at 640 x 480, fov = 54.9 x 42.6, distortion = NONE
Capturing INFRARED at 640 x 480, fov = 67.9 x 53.6, distortion = INVERSE_BROWN_CONRADY
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-headless
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
Serial number:<PHONE_NUMBER>87
Firmware version: <IP_ADDRESS>
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-restart
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-tutorial-3-pointcloud
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
Serial number:<PHONE_NUMBER>87
Firmware version: <IP_ADDRESS>
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./c-tutorial-3-pointcloud
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
Serial number:<PHONE_NUMBER>87
Firmware version: <IP_ADDRESS>
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-capture
Capturing DEPTH at 640 x 480, fov = 67.9 x 53.6, distortion = INVERSE_BROWN_CONRADY
Capturing COLOR at 640 x 480, fov = 54.9 x 42.6, distortion = NONE
Capturing INFRARED at 640 x 480, fov = 67.9 x 53.6, distortion = INVERSE_BROWN_CONRADY
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-headless
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
Serial number:<PHONE_NUMBER>87
Firmware version: <IP_ADDRESS>
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

**{THIS IS THE ONLY ONE THAT ALLOWS A RGB STREAM}**

./cpp-restart
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-tutorial-3-pointcloud
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
Serial number:<PHONE_NUMBER>87
Firmware version: <IP_ADDRESS>
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./c-tutorial-3-pointcloud
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
Serial number:<PHONE_NUMBER>87
Firmware version: <IP_ADDRESS>
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-capture
Capturing DEPTH at 640 x 480, fov = 67.9 x 53.6, distortion = INVERSE_BROWN_CONRADY
Capturing COLOR at 640 x 480, fov = 54.9 x 42.6, distortion = NONE
Capturing INFRARED at 640 x 480, fov = 67.9 x 53.6, distortion = INVERSE_BROWN_CONRADY
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-config-ui {stream of each camera doesen't initiate}
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-multicam
Starting Intel RealSense SR300... done.
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./cpp-tutorial-1-depth
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
Serial number:<PHONE_NUMBER>87
Firmware version: <IP_ADDRESS>
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

./c-tutorial-1-depth
There are 1 connected RealSense devices.
Using device 0, an Intel RealSense SR300
Serial number:<PHONE_NUMBER>87
Firmware version: <IP_ADDRESS>
terminate called after throwing an instance of 'std::runtime_error'
what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

Hi, we have not encountered this issue, but a prime suspect is the USB controller. In particular if you are using an USB-hub the camera might be drawing too much power on start causing a reset. If you have several USB3 ports try switching between them. If you need a hub, consider using powered one. Another theory can be that one of the video interfaces is not enumerated. Please check that you see video0 and video1 under /dev/ and in /sys/class/video4linux

The computer is branded new and the USB ports are both usb 3.1, so I wouldn't suspect a power issue.
Already tried with both available USB, reinstalling Ubuntu and upgrading to 16.04 LTS but I'm having the same problem.
I'm just able to stream with cpp-config-ui few seconds of RGB and then the script closes itself
~/src/librealsense/bin$ ./cpp-config-ui
terminate called after throwing an instance of 'std::runtime_error'
  what():  VIDIOC_DQBUF error 19, No such device
Aborted (core dumped)

By the way video0 and video1 are both existing, and under /dev/ > /sys/class/video4linux, video4linux is existing as well.

The attached documents represents the complete output of dmesg
Dmesg.tar.gz

your dmesg error log looks almost exactly like mine (#343)..
Any luck getting this to work?

I get this error when I try to run multiple cameras in parallel with callbacks.
When I run the cameras in a while loop (polling frames devices after device), then this does not happen. But in this way, if I want to, for example, save every new frame to a file .jpg file, then the FPS for all cameras drop to 20 FPS (from 30 FPS originally). The hardware/software is very delicate very delicate.

Ubuntu 14.04, SR300 camera and Alienware R5 labtop, I got same error. Then I plugin the camera into the powered USB3.0 HUB, then it works.

Environment Info
.

Camera Model
SR300

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 16.04.1 LTS

Kernel Version (Linux Only)
4.8.0-58-generic

Computer
Alienware 17

Single camera works fine when directly connected via USB 3.0. This issue arises using the same camera on an Amazon Basics USB 3.0 hub powered by a 48W(12V/3A) adapter. No other USB devices are connected.

Duplicate to #418

root@block:~/bdsm/src# ./BDSM-FETISHd
terminate called after throwing an instance of 'std::runtime_error'
what():  locale::facet::_S_create_c_locale name not valid
Aborted (core dumped)

"VIDIOC_DQBUF error 19" -  camera disconnection from host event, in most cases occurs due to the insufficient power provided by host.
There are several ways to mitigate the issue, or at least to its minimize its re-occurrence:

Connect the depth camera via a self-powered USB3 hub.
Do not connect additional USB devices (including Keyboard and Mouse) to the same USB hub/port
Avoid using long (3m+) USB3 cables.
On laptops - prefer working with the AC plugged-in.

Additional info can be found in threads, #418, #264,#558, 487 and more (apply "error 19" filter on the "Issues" tab).

I recommend using an Industrial USB 3.0 hub. That solved my problem.


chore: don't use Task::on_shutdown for Task::make_shutdown_rx

It makes it easy to leak memory.
Instead, use tokio::sync::watch to update tasks that might be waiting for shutdown signal.

Tests are more flaky than normal?


Tonic Validate Evaluators

Description
This PR adds a Tonic Validate integration into LLamaIndex. Specifically, this PR adds three things

An evaluator in llama_index.evaluation corresponding to each Tonic Validate RAG metric.
An evaluator, TonicValidateEvaluator, that calculates all of the Tonic Validate metrics at once.
An example notebook, docs/examples/evaluation/TonicValidateEvaluators.ipynb that shows how to use the new evaluators.

The new evaluator classes are subclasses of BaseEvaluator.
These changes require the new dependency
tonic_validate>=2.1.0
for the new evaluators to work. Note that no changes have been made to the pyproject.toml file to reflect this dependency.
Type of Change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[x] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

this has nothing to do with the PR but congrats on hitting PR 10000!

Congrats #10000 !

@nerdai thanks for the review! I added a couple more change to address your comments.

@nerdai thanks for the review! I added a couple more changes to address your comments.

The notebook looks much improved now with an evaluation example with more than one observation! Thanks again for your modifications and the answers to my questions.
Merging this now 🚀


find/replace not triggering didChange

VSCode Version: 1.7.2
OS Version: OS X 10.11.6

Steps to Reproduce:

open 3 files with the same string in it.
Search + replace for that string.
Language server protocol only fires a change event for one of the changed files.

Same thing happens for a rename request.
https://github.com/Microsoft/language-server-protocol/blob/master/protocol.md#rename-request
What I expected:
a textDocument/didChange for every file that was changed.

This will be fixed in the next version (3.x) of the Language Server protocol implementation for node (already fix in master here: https://github.com/Microsoft/vscode-languageserver-node)

@dbaeumer thanks for the answer

@dbaeumer
we tried the same steps with version 3.0.1-alpha.3 (the newest one available five days ago and the newest one working without changing the protocol on our end) and we still had the same issues.

@nicolasg-da actually there is still a problem. Was able to reproduce. Will address for the next LSP release.

Fixed in<EMAIL_ADDRESS>

@dbaeumer thanks! :)


Silent Login interval is too short

Reportedly, the Auth0 iframe for running the silent login is injected too often (every 35 to 40 seconds) ignoring the TTL of the JWT.

Fixed in commit bc59de7


add git diff check

Changes

order the manifest contents outputs of devtools/scripts/update_manifest.py by filename for consistent manifest generation
add a git diff check in pytest_asdf.yml workflow against the output of devtools/scripts/update_manifest.py (if this fails, try running devtools/scripts/update_manifest.py locally and commit changes)

This should make it easier to find bugs in the asdf manifest and Converter setups
If the action fails at the git diff step run the update_manifest.py script (must be executed in the devtools/scripts folder) to fix


Fix web worker build with parcel

This fixed the issue #28 for me with Parcel. I believe the module is needed to instruct the bundler that it's an esmodule and should be bundled.
https://stackoverflow.com/questions/48045569/whats-the-difference-between-a-classic-and-module-web-worker

I was getting this error with parcel:
🚨 Build failed.
[Error: ENOENT: no such file or directory, open '/Users/jdlm/stripe/pay-server/frontend/graphy/node_modules/.pnpm/@memgraph+orb<EMAIL_ADDRESS>{
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/jdlm/stripe/pay-server/frontend/graphy/node_modules/.pnpm/@memgraph+orb<EMAIL_ADDRESS>}

And this got it working.
I know this PR isn't quite up to contributing standards, but I figured I'd throw something up real quick so ya'll could take a look and tweak if you want it.

Thanks a bunch for contributing!
Looking at this browser compatibility list, it seems that ES worker modules aren't supported by Firefox. I tried your branch and it seems to work fine for me. Could you please test your setup in Firefox to confirm that it works?

It works with Firefox (v107.0) on my Mac via Parcel. I believe that compatibility table doesn't apply in the Parcel case because the { type: 'module' } acts has a hint for Parcel to bundle away the ES modules before sending it to the browser. Here's a snippet of what gets shipped to Firefox for process.worker:
// modules are defined as an array
// [ module function, map of requires ]
//
// map of requires is short require name -> numeric require
//
// anything defined in a previous bundle is accessed via the
// orig method which is the require for previous bundles

(function (modules, entry, mainEntry, parcelRequireName, globalName) {
  /* eslint-disable no-undef */
  var globalObject =
    typeof globalThis !== 'undefined'
      ? globalThis
      : typeof self !== 'undefined'
      ? self
      : typeof window !== 'undefined'
      ? window
      : typeof global !== 'undefined'
      ? global
      : {};
  /* eslint-enable no-undef */

  // Save the require from previous bundle to this closure if any
  var previousRequire =
    typeof globalObject[parcelRequireName] === 'function' &&
    globalObject[parcelRequireName];

...<snip>...


Revisit the switching event processor

The switching event processor feels like we're pushing back against fundamental design choices encouraged by Axon. We should revisit it and consider only keeping the replay functionality.
What benefit do we get from using tracking event processors for replays given that they only work when assigned to the default group?

I've tested the reworked saga example and found that a long running saga interrupted by application shut down or crash:

will not recover when we're using subscribing event processors
will automatically continue processing the saga when the application restarts when using the tracking event processor

My vote is to remove the switching one.


Feat: Allow transitional separators to be set on component basis

This separates the transitional separators from section . And allows them to be uses on component scope.
Also the statusline function is refractored to simplify it .
Example :

Merged in https://github.com/shadmansaleh/lualine.nvim

Part of #311