Switch Header/Source for clangd

This snippet may be useful for users of clangd
-- in lsp-ext.lua
M = {}

M.switch_header_source = function()
    vim.lsp.buf_request(
        0,
        "textDocument/switchSourceHeader",
        vim.lsp.util.make_text_document_params(),
        function(err, _, result, _, _)
            if err then
                print(err)
            else
                vim.cmd('e '..vim.uri_to_fname(result))
            end
        end
    )
end

return M

-- in your lua config
vim.cmd [[
    command! SwitchHeaderSource lua require "lsp-ext".switch_header_source()
]]

Is something like this in the scope of nvim-lsp? Maybe we could put this in the documentation in the README.

Ooops: someone was faster: #263


New package: CopositiveAnalyticCenter v0.1.0

Registering package: CopositiveAnalyticCenter
Repository: https://github.com/rileybadenbroek/CopositiveAnalyticCenter.jl
Created by: @rileybadenbroek
Version: v0.1.0
Commit: 6e00083f9fada51561e73be2fcfb9f57d79a311b
Git reference: master

Will try to fix these errors

Fails because automerge cannot find a Gurobi installation, which makes sense.


bump dependencies

Description
Changes proposed in this pull request:
it is too cumbersome to handle all the dependabot PRs by hand. here is an all-in-one PR.
Related issue(s)

/retest

/retest


Feature: Add Explorable Explanations interactive mode.

Description
This PR aims to introduce an interactive mode where user can move the user icon with mouse and upon clicking on a circle depending on the index either auction or joinAdInterestGroup is triggered.
Relevant Technical Choices

Testing Instructions

Clone this branch.
Go to terminal and run cd ee && npm i && npm start.
Now in the browser, move the user icon to the circles and check the auction flows.

Additional Information:

Screenshot/Screencast
https://github.com/user-attachments/assets/46cd5c5a-d989-45c9-ad1a-f849b689d23f

Checklist

[x] I have thoroughly tested this code to the best of my abilities.
[x] I have reviewed the code myself before requesting a review.
[x] This code is covered by unit tests to verify that it works as intended.
[x] The QA of this PR is done by a member of the QA team (to be checked by QA).

@amovar18 We have to handle the case when the user clicks on one node and while the animation is in progress, they click on another node. I see the flow mess up and eventually throws error.

ERROR
Cannot destructure property 'color' of '_app__WEBPACK_IMPORTED_MODULE_2__.default.bubbles.positions[i]' as it is undefined.
TypeError: Cannot destructure property 'color' of '_app__WEBPACK_IMPORTED_MODULE_2__.default.bubbles.positions[i]' as it is undefined.
    at __webpack_modules__../src/modules/bubbles.js.bubbles.reverseBarrageAnimation (http://localhost:8080/protected-audience.js:1701:14)
    at __webpack_modules__../src/modules/join-interest-group.js.joinInterestGroup.draw (http://localhost:8080/protected-audience.js:2189:58)
    at async __webpack_modules__../src/protectedAudience.js._app_js__WEBPACK_IMPORTED_MODULE_2__.default.drawFlows (http://localhost:8080/protected-audience.js:2586:3)
    at async _app__WEBPACK_IMPORTED_MODULE_1__.default.p.mouseClicked (http://localhost:8080/protected-audience.js:2280:9)

Also if I click multiple times on the same node.

Please add an "Interactive Mode" checkbox and the flow should go into the interactive mode only when the checkbox is checked.

@amovar18 Some more improvements:

[ ] The bubble container of IGs should reset when interactive mode is checked.
[ ] Interest groups container is not clickable when interactive mode is on.
[ ] When the user clicks on another node which the previous one was in progress, reset the previous animation and start this new one.
[ ] Remove user icon from the cursor, if the user hovers over action items other than the nodes.


GH-41134: [GLib] Support building arrow-glib with MSVC

Rationale for this change
Allow Windows users to more easily build the GLib libraries.
What changes are included in this PR?

Minor fixes to allow building with MSVC:

Changes some uses of variable length arrays to std::vector, because MSVC doesn't support variable length arrays
Moves some function definitions that use C++ types outside of G_BEGIN_DECLS/G_END_DECLS blocks (which expand to extern C { }), because this caused MSVC to error

Fix libraries not having any exported symbols with MSVC, which defaults to hiding symbols

Add visibility.h which defines a new GARROW_EXTERN macro that adds dllimport or dllexport attributes when using MSVC.
Include the GARROW_EXTERN macro in the definitions of the GARROW_AVAILABLE_IN_* macros.

Add a new CI job that builds the GLib libraries with MSVC on Windows, using vcpkg to install pkgconfig and glib.
For now only arrow-glib is built, I can follow up with the other libraries after this PR. That will require introducing new per-library version macros.

Are these changes tested?
The build will be tested in CI but I've only done some quick manual tests that the built library works correctly, I haven't got the ruby tests running against the build yet.
Are there any user-facing changes?
No? Eventually some documentation should be updated when all the GLib libraries can be built with MSVC though

GitHub Issue: #41134

@github-actions crossbow submit -g release

@github-actions crossbow submit -g nightly-release

I've rebased on top of the changes from #41721 to add per-library version headers, and added per-library visibility headers too. I've had to keep the Gandiva build disabled due to #36958 and also disabled the Flight libraries due to a missing zlib dependency, but I'm hoping that should be fixed by switching to vcpkg dependencies for the C++ library build.


New version: 7S2P.Effie version 3.11.7

Created by 🥟 Dumplings in workflow run #6943.

Log
Updated: 3.11.5 → 3.11.7
Submitting WinGet manifests
Found existing pull requests:
New version: 7S2P.Effie.CN version 3.11.7 - https://github.com/microsoft/winget-pkgs/pull/165062
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run


Block comment behave wierd

I pressed gcap on that block for  2 times.

This seems to be due to how neovim detects the paragraphs:
local function a()
    print("hello")
    print("hello")
    print("hello")
    print("hello")
    print("hello")
end

When you press gcap on this two times, it works as you would probably want.
local function a()

    print("hello")
    print("hello")
    print("hello")
    print("hello")
    print("hello")
end

When you have a blank line there, neovim will detect the bottom part as the paragraph. It seems that in this case the region will start on the blank line, so that's where the comment starts. Now, since the block looks like this:
local function a()
--[[
    print("hello")
    print("hello")
    print("hello")
    print("hello")
    print("hello")
end ]]

there isn't a blank line starting a new paragraph anymore, so neovim will detect the whole thing as a paragraph.
In general, I would advise against using the paragraph text object, since something treesitter based is much more accurate. I'm not sure in which capacity it supports lua, but have a look at this plugin in case you want a function text object.

Why not just add a newline above the first comment line?

Because that's not normally the expected behaviour.

Alright, thank you. But I'm sure there is situation you want manually partition into paragraphs, because the semantic unit itself is not enough in some cases.
Workaround: I've found gcip instead of gcap perfectly fit my need.


Add __errno_location on Redox, DragonFlyBSD, Haiku

Currently libstd and the getrandom crate have to use external declarations in order to implement errno_location across all UNIX platforms. This change adds bindings for the remaining UNIX platforms, allowing everyone to just use normal libc bindings.
This also removes the need for a seperate errno-dragonfly crate.
Links to the relevant header files:

Redox: relibc's bits/errno.h uses __errno_location
Haiku: posix/errno.h uses _errnop
DragonFlyBSD: sys/errno.h uses __error just like FreeBSD (which makes sense)

Note that the __error function is inlined. I don't think this causes a problem.

r? @gnzlbg
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+
Thanks!

:pushpin: Commit 4fc38ca9d9d68c8781dbc413fc968dab2a800e57 has been approved by gnzlbg

:hourglass: Testing commit 4fc38ca9d9d68c8781dbc413fc968dab2a800e57 with merge acd8db569336a2f7bc871e4f65a39dd1ce392247...

@bors: r-
The paths need fixing.

:broken_heart: Test failed - checks-travis

The paths need fixing.

Copy paste bites again, should be fixed now.

Thanks! @bors: r+

:pushpin: Commit e9c1ade3dc2af1bd79dcd1df159198b97313270f has been approved by gnzlbg

:hourglass: Testing commit e9c1ade3dc2af1bd79dcd1df159198b97313270f with merge d829520a33703fbdfc728670127a9f9bb6964f55...

:broken_heart: Test failed - status-appveyor

Note that both std and errno-dragonfly seem to implement this differently than what's in this PR for Dragonfly. Was that intentional?

cc @strangelittlemonkey

cc @sikmir could you review this for haiku?
cc @jackpot51 could you review this for redox ?

Note that both std and errno-dragonfly seem to implement this differently than what's in this PR for Dragonfly. Was that intentional?

This was intentional. I looks like implementing it with #[thread_local] would be slightly more efficient (as you don't have a function call). However, that's not possible on stable Rust, so using the function instead seems like the best bet.

Interesting. The errno-dragonfly crate actually uses custom C code to return errno and then links to that. Is that just an oversight on their part?
N.B. I am speaking from ignorance here. I'm only asking these questions because I'm curious. :-)

I think Rust can handle such a function OK

The __error function is static (TU-private) and inline, so it probably isn't part of the generated binary, and we can't link against that. That is, we would need to implement it in this crate.
DragonflyBSD defines errno here as :
extern __thread int	errno;
static __inline int* __error() { return &errno; }

This:
extern __thread int	errno;
int* foo() { return &errno; }

emits:
define dso_local i32* @foo() #0 {
  ret i32* @errno
}

Notice the dso_local in there.

I think that in Rust we would need: extern "C" { #[thread_local] static errno: i32; } (using feature(thread_local)), but I don't know whether this currently works when used on extern statics. Right now we don't emit dso_local, and I don't know how important that is. cc @eddyb @rkruppe

Also cc @joshtriplett: there is no stable Rust way to link against extern #[thread_local] statics, that should probably be added to the list of missing features for C FFI.

@BurntSushi

Is that just an oversight on their part?

I don't think so. They can't crate a pointer to the static __thread int errno from Rust, so they have to do that from C. See above.

dso_local is a function attribute and likely the static on foo.
You need to compare the declarations of the @errno global to check if the #[thread_local] works (it should, since we lower it pretty straightforwardly).

@eddyb so we lower the extern "C" { #[thread_local] static errno: i32; } to
@errno = external thread_local global i32

clang lowers this to:
@errno = external thread_local global i32, align 4

So I think #[thread_local] should work.

@josephlr we do have a cargo feature feature = "unstable" that you could use to only provide the #[thread_local]s for nightly users that enable that feature via a #[cfg()].
I don't think there is a pure Rust solution available for stable Rust users. Linking to a C snippet that returns a pointer to the thread local like the errno-dragonfly crate does feels like the simplest solution to this problem.

Could that platform's errno be gated by #[cfg(feature = "unstable")] to land this, and have an issue for stable support?

@eddyb sure, and libstd enables the "unstable" feature, so it can make use of this to simplify the implementation. The getrandom crate would need to wait a bit.

LGTM

@josephlr we do have a cargo feature feature = "unstable" that you could use to only provide the #[thread_local]s for nightly users that enable that feature via a #[cfg()].

@gnzlbg that works, I’ll make the change to add __error and errno behind this guard. For getrandom, we might just be OK requiring nightly for DragonFlyBSD.

Also, I don't know how good will ctest be with verifying the ABI of thread-locals. If there are any issues, feel free to just use cfg.skip_static in libc-test/build.rs to skip the tests, and fill an issue in ctest upstream. We can solve those later.

@gnzlbg this crate doesn't seem to have an unstable feature in Cargo.toml. Would you want me to add it, or am I missing something?

Yes, please add it. I think we might have removed it when we started enabling features depending on the Rust-versions.

Yes, please add it. I think we might have removed it when we started enabling features depending on the Rust-versions.

Would you want it to be called nightly or unstable? Using nightly seems slightly more common among crates.

So, call the cargo feature unstable, and in the libc/build.rs, if that feature or rustc_dep_of_std are enabled, pass a --cfg libc_thread_local when building the library. Inside libc/src, use #[cfg_attr(libc_thread_local, feature(thread_local))] to enable the feature(thread_local) and #[cfg(libc_thread_local)] to gate its uses.

The reason I prefer not to use nightly, is that a lot of people compile libc with nightly, but don't want to use unstable features when they do so. So whether a nightly toolchain is used is orthogonal to whether unstable features are used.

DragonFly BSD has no ability at present to build nightly so if you move this to requiring nightly then there’s no point in making any rules in the setup that account for DragonFly.

On Jul 10, 2019, at 11:55 AM, gnzlbg<EMAIL_ADDRESS>wrote:
The reason I prefer not to use nightly, is that a lot of people compile libc with nightly, but don't want to use unstable features when they do so. So whether a nightly toolchain is used is orthogonal to whether unstable features are used.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

So, call the cargo feature unstable, and in the libc/build.rs, if that feature or rustc_dep_of_std are enabled, pass a --cfg libc_thread_local when building the library. Inside libc/src, use #[cfg_attr(libc_thread_local, feature(thread_local))] to enable the feature(thread_local) and #[cfg(libc_thread_local)] to gate its uses.

@gnzlbg this is done. I had to use cfg_if and a sub-module to add the errno stuff, otherwise the style checker yelled at me. Also, there seem to be a bunch of CI failures related to serde_derive, any idea why those are happening?

DragonFly BSD has no ability at present to build nightly so if you move this to requiring nightly then there’s no point in making any rules in the setup that account for DragonFly.

@strangelittlemonkey I'm not sure what you mean here. Nightly is required to build libstd and we have Dragonfly related code in libstd.

It turns out the CI is failing due to a transitive serde_derive dependency, which is breaking because of https://github.com/rust-lang/rust/issues/62562
All the errors (as far as I can tell) are related to this bug, so the breakage is not caused by this PR.

You’re fine to write DragonFly code for something needing nightly but it’s dead code because we have no nightly build and I’m not sure we’ll ever have nightly support or a nightly build even. If you’re requiring nightly you should take DragonFly off the support list for the crate or any other like that because it would just be misleading.

On Jul 10, 2019, at 9:06 PM, Joseph Richey<EMAIL_ADDRESS>wrote:
It turns out the CI is failing due to a transitive serde_derive dependency, which is breaking because of rust-lang/rust#62562
All the errors (as far as I can tell) are related to this bug, so the breakage is not caused by this PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@strangelittlemonkey "nightly" is misleading - what's important here is "unstable", which is allowed for any dependency of std/rustc.
Even if users of libc from crates.io might not use the unstable feature on DragonFlyBSD, to build even stable/beta, std needs errno from libc, for which it can enable some "unstable" flag to provide errno.

@strangelittlemonkey or in other words, when the compiler is compiling itself, which is something that has to be done to build a compiler for DragonflyBSD, it can use unstable features that are generally only available on nightly.

I’m just saying requiring nightly to build it at all would make DragonFly a moot point, but allowing extra features if building with nightly would be different and fine, but still dead code if it applied to DragonFly specifically.

On Jul 11, 2019, at 9:24 AM, gnzlbg<EMAIL_ADDRESS>wrote:
@strangelittlemonkey or in other words, when the compiler is compiling itself, which is something that has to be done to build a compiler for DragonflyBSD, it can use unstable features that are generally only available on nightly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I’m just saying requiring nightly to build it at all would make DragonFly a moot point, but allowing extra features if building with nightly would be different and fine

It's the latter, we're talking about an opt-in way to enable errno on DragonFly that requires unstable. This is either for nightly or building Rust itself.
Like I said before, that opt-in would be enabled by std, which depends on this crate for its FFI to implement std::io, std::fs and other such functionality.
So when you build any future release of Rust (including stable ones) for DragonFlyBSD, the errno added here would be used, even if a use of that build of Rust wouldn't have that errno available.
So, yes, it's dead code for normal users of this crate, but would still be needed and used for the standard library (which does its OS FFI through this very same crate).

@gnzlbg https://github.com/rust-lang/rust/issues/62562 has been fixed, so the CI is passing again
@strangelittlemonkey Nightly build issues aside, the code added in this PR is required to build libstd for DragonFlyBSD (not necessarily building on DragonFlyBSD). Will this code work for DragonFlyBSD? and if not, what should we do instead?
I updated the docs to point out why we need unstable at all

Just to triple check, is there any crate that wants to use this from crates.io ?
If not, then we don't need the unstable feature, and can just feature gate this using the "dep-of-std" feature.

Just to triple check, is there any crate that wants to use this from crates.io ?

Initially the thought was to also use this for getrandom, but due to https://github.com/rust-lang/cargo/issues/4866 we can't reasonably turn on the unstable feature for only one target, so I don't know of any crates that currently want it.

If not, then we don't need the unstable feature, and can just feature gate this using the "dep-of-std" feature.

Sounds good, I'll make the change unless anyone else want's to use this.

@josephlr you can chime in in the thread_local tracking issue in rust-lang/rust, and mention that getrandom wants to use it. I don't know if anybody has needed to use extern thread-locals before, but that's something required for being able to FFI with C..

Just to triple check, is there any crate that wants to use this from crates.io ?

Yes. walkdir will eventually want this. I'm currently using the same hack as the errno-dragonfly crate in my branch: https://github.com/BurntSushi/walkdir/blob/ag/sys/src/os/unix/errno.rs

Just to triple check, is there any crate that wants to use this from crates.io ?

Yes. walkdir will eventually want this. I'm currently using the same hack as the errno-dragonfly crate in my branch: https://github.com/BurntSushi/walkdir/blob/ag/sys/src/os/unix/errno.rs (Which I'll have to continue using if errno on DragonFly is only available with nightly Rust.)

OK, as walkdir and getrandom can’t use this until it’s on stable, we don’t need the unstable feature. I’ll mention this on the main Rust tracking issue.

Looking at the tracking issue, and the thread_local! discussions, it appears that 1) thread_local! solves the problem for most people, and 2) the main uncertainty is that #[thread_local] isn't portable.
Maybe we could reduce the scope of an initial version of #[thread_local] to extern static declarations. If the target does not support #[thread_local], well then the extern static declaration is incorrect since there cannot be a definition anywhere, and using it would already be UB. We could add on top of this a "best effort" compilation error, e.g., if the compiler knows that the target doesn't support it.

@gnzlbg I removed the unstable feature, and commented on the appropriate thread_local tracking issue.

Thanks!
@bors: r+

:pushpin: Commit df34d17bd9c3427731a000d6356e7d04d0255c8d has been approved by gnzlbg

:hourglass: Testing commit df34d17bd9c3427731a000d6356e7d04d0255c8d with merge 47535e6d20c90404d9da710dbccb1fedbb0e6424...

:sunny: Test successful - checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-travis, status-appveyor
Approved by: gnzlbg
Pushing 47535e6d20c90404d9da710dbccb1fedbb0e6424 to master...

libc 0.2.60 has been published with this - I'll update libc on rust-lang/rust


New address for ECE

New email address for ece.fr to edu.ecetech.fr
(http://www.ecetech.fr/) is a French IT university.
The edu extension is only for email addresses.
(Maybe my path is wrong ? I want @edu.ecetech.fr)

@xukyo Yes, for edu.ecetech.fr the path has to be lib/domains/fr/ecetech/edu.txt
Please correct. Thank you.

@philipto I have corrected it

@xukyo Pull request merged. Thank you!


Feature Request: Roku Support

Probably for the icebox but Roku would be a great additional media player to support (in the same vein as Chromecasts, etc..)
Here is some information on Roku/Python and discovery of Rokus.
http://paulmouzas.github.io/python/http/sockets/2015/03/29/roku-remote.html
Additional Roku/Python/Pip - https://github.com/alexsacr/pyroku
Control of the Roku would be useful in scenes but I am still searching to see if anyone has created an example of tracking the state of the Roku (i.e. what channel/screen is currently being displayed, etc..)  That state information would be very useful as triggers for additional lighting, presence and other automations.
Just leaving this here for someone smarter than I. :)

The Roku API allows remote control, but does nothing towards providing the status of the box. There is absolutely no way to track the state of the Roku short of hacking into the Roku. It is very unfortunate, and also the only reason I do not own a Roku myself.
It is quite a shame that no off-the-shelf set top boxes have a decent API. The Chromecast is far and above the best in terms of data reporting, but still isn't quite as nice as solutions like Plex and Kodi.
Despite all of this, Roku support could be added for basic control features like Play/Pause, Next/Previous, and Power. We can leave this issue open for someone with a Roku looking for inspiration.

Closing this issue as feature requests should be posted in the forum.


while i ctrl+s to save the code

this will apppear  in 3s
after 3s ,it auto disappear,
how can i solve it

while i open vscode ,and  ctrl the file   ,it will appear

it really annoy me so much

i need to reinstall nodejs&&vscode???


ART-3395 Accept release job enhancements

https://issues.redhat.com/browse/ART-3395
Summary:

Use release_tool.py script instead of our hack script
Allow rejecting a release

This should give our serviceaccount the needed roles https://github.com/openshift/release/pull/36192
Hack run: https://saml.buildvm.openshift.eng.bos.redhat.com:8888/job/hack/job/sidsharm-aos-cd-jobs/job/build%252Faccept-release/34/console
TODO: Figure out how to fetch/store script (and requirements.txt) - leaning towards a dumb solution of keeping local copy, comparing to remote and error out if outdated. We don't expect the files to be updated, should be once / twice in a quarter or less.

Would be nice to have a test run. Maybe we can trigger a nightly for an old version (e.g. 4.7) and reject it.
Is the accept functionality going to work on nightlies too, or just on named releases like before?

This basically LGTM. Would be nice if there is a test run but I am ok with merging this and test in production.

/lgtm


What do I do with the updated file.ini

Hello everyone, first of all thank you very much for this RDP that has solved so many "problems" for some Windows users, what happens is that I have windows 8.1 with 6.3 9600 and the RDP does not work, it shows me as "Not Supported", then I read a bit, and it says to update the rdpwrap.ini with some new parameters, then download the files and I did, now, what should I do with these files? You have to pack them? How to do it? with what software does that, I'm sorry I'm not very expert in this, I would greatly appreciate your help.

This is bug tracker, not forum for discussions.

where i can find the forum for this question?


[Linter] Proposal: prefer_wildcard_variables lint rule

Proposal for New Dart Lint Rule
TLDR
Add a lint rule to prefer wildcard variables (_) over multiple underscores (_, __, ___) in unused parameters.
Motivation
The upcoming Dart 3.7.0 release introduces support for wildcard variables (_) that can be reused for multiple unused parameters. Previously, developers commonly relied on distinct variables like _, __, ___ to indicate unused parameters. This practice is now redundant with the introduction of _, which improves clarity and reduces visual noise in the codebase.
Reference

https://github.com/dart-lang/sdk/blob/main/CHANGELOG.md#wildcard-variables

Lint Rule Implementation
Rule Name: prefer_wildcard_variables
Description: Warns when distinct variable names such as __, ___, etc. are used for unused parameters, recommending the use of _ instead.
Severity Level: WARNING (as it’s a stylistic improvement and non-breaking).
Code Examples
Bad
ListView.builder(
  itemCount: 10,
  itemBuilder: (_, __) {
    return ListTile(
      title: Text('Item'),
    );
  },
);

Good
ListView.builder(
  itemCount: 10,
  itemBuilder: (_, _) {
    return ListTile(
      title: Text('Item'),
    );
  },
);

Behavior

Triggers a warning: When multiple distinct unused variable names (__, ___) are declared.
Does not trigger: For valid wildcard use cases, such as (_, _, _).

Benefits

Improved Code Readability: Reduces unnecessary differentiation in unused parameter names.
Consistent Dart Style: Encourages developers to adopt features introduced in newer Dart versions.
Simpler Refactoring: Avoids subtle issues where _, __, and ___ might accidentally be referenced or misinterpreted.

CC @pq @kallentu sounds like a win to me!

Ah yes, we've agreed upon making a lint that's exactly this. We may call it unnecessary_underscores or something more specific than prefer_wildcard_variables though.
For more context: https://github.com/dart-lang/sdk/issues/56595

I like that name. too_many_underscores. why_so_many_underscores. 😁


slim 4 + slim-http 0.5 decorators

Hello!
Now i'm using slim4 and slim psr7 implementation.. Today you have upgraded slim-http to decorators, very good update, thanks!

After upgrade i got errors in slim4 App.. If i understood right, now slim psr7 moved to slim/psr7, but composer couldn't find it..
Some modules of my system (stand-alone) using Guzzle implementation. Is it will be better, to move the entire system to Guzzle too, using new decorators?
How to do it right?)
Thanks in advance

See PR #2529 for where we're going. We're in flux at the moment on this branch.

It really doesn't matter and is up to you. There is no "right" here. Personally, I'd use Nyholm's PSR-7 implementation for my Slim app as I like it and then use Guzzle as an HTTP client within my actions.


docs(Ideal/QuotientOperations): remove an extra-star denoting a ring homomorphism

Correct the doc of Ideal.quotientEquiv removing a spurious star.

Thanks!
bors merge


Packaging subdirectory [brew-staging: directory-change]

Blocked on: #1231
This PR applies several cleanups to the K repo structure.

Creates package subdirectory where packaging scripts are moved (currently except Homebrew scripts).
Moves Dockerfile.* into the appropriate packaging subdirectory, and has just one generic Dockerfile at the top level for normal CI steps.
Ensures that the hub release is attached to the correct commit (not just to origin/master) to make it possible to try releases on non-master branches (for testing).

Needs kframework/homebrew-k#3 merged before this is merged.

@dwightguth it really does not make sense to me that the K Platform Independent Binary is still failing on this PR. I'm not changing the Dockerfile it uses, or anything about any of the tests it's running. Everything that is changed has to do with the other packages, and the only thing changed is that scripts are moved to the package subdirectory to organize the repo a bit.
Any ideas what's going on?

Evidence that this is working: https://office.runtimeverification.com/jenkins/blue/organizations/jenkins/k/detail/PR-1227/29/pipeline/

@dwightguth for some reason, when the Arch build was running before the Platform Independent K Binary build in the same directory, it was causing test18 to fail with a unicode error. fed0f80 runs the arch build in a subdirectory, which seems to fix the problem. This is ready for review.


Incomplete PRAGMA support

I have noticed some inconsistencies in the handling for SQLite pragmas.

There is a setter for busy_timeout= but no getter.  Likewise for ignore_check_constraints=.
No accessors for analysis_limit hard_heap_limit trusted_schema
No method for optimize
No methods for function_list module_list pragma_list
No methods for table_list table_xinfo

For the last, SQLite supports 3 pragmas for index and table:

thing_list
thing_info
thing_xinfo

The gem I have installed, version 2.0.4, has methods for all three index pragmas but only the table_info method.
Some of these may not make sense to support, but these are my findings.  Separately, I have some ideas about how to reorganize lib/sqlite3/pragmas.rb.

I might take a stab.  Here's what I'm doing in the meantime: https://gist.github.com/rickhull/464c6fdf5fdea217894f67618b4a2b0c

Please take a look at the Nostrb::SQLite::Pragma class: https://github.com/rickhull/nostrb/blob/master/lib/nostrb/sqlite.rb#L6
I want to basically import this wholesale, or something like it, as our pragma backend.  We can then patch or rewrite the current API using this backend.  I think it will be relatively easy to delete nearly of the current pragma impl with this more programmatic approach.
Even if not, I may still look at extending the current approach.

@rickhull I'm not opposed to doing something like what you're describing, but maybe we can get there iteratively instead of big-bang copying code and then trying to adapt to it.
For example, I really like how that class defines the pragma setters and getters dynamically. Maybe we could start by introducing that technique into this gem (and adding some tests for those pragmas)? I think that really cleans things up and addresses almost all of the initial issues you raised above. WDYT?

Totally agreed on not necessarily big-bang-adapt.  If I can land a suitable patch here, then I can delete most of my stuff.  Let me come up with something more concrete in the next few days.

How do we feel about these pragma I've ignored?
      #      debug: parser_trace schema_version stats vdbe_* writable_schema
      #     legacy: legacy_alter_table legacy_file_format
      # deprecated: case_sensitive_like count_changes data_store_directory
      #             default_cache_size empty_result_callbacks full_column_names
      #             short_column_names temp_store_directory

@rickhull I don't mind if some pragmas end up unimplemented, but I do want to make sure we don't remove existing pragmas. I didn't do a complete check, but for example default_cache_size is currently supported by this gem. Does that make sense?

Sounds good! I'm pretty slammed for the next couple weeks but I'm 90% of the way to a PR.  It may take a lil while to get there.

I haven't forgotten about this and am willing to support and guide if someone else wants to drive.  Otherwise I'm 90% of the way to a plan for a PR, but need to carve out the time to crank it out.  Probably not for 2024 though.  It's still on the back burner though.


Update overview.md

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 8d583cc562705b44888c9a1702e2f07a2d47b31e
https://deploy-preview-8495--docsdocker.netlify.com

Writing guidelines issue.


chore(deps): updated project dependencies

Codecov Report

Merging #4 (e9b9c2c) into main (3350b0e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #4   +/-   ##
=======================================
  Coverage   71.05%   71.05%
=======================================
  Files           2        2
  Lines          38       38
  Branches        6        6
=======================================
  Hits           27       27
  Misses          5        5
  Partials        6        6

Flag
Coverage Δ

unittests
71.05% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 3350b0e...e9b9c2c. Read the comment docs.


Fix non-existing directory error when writing files

Given /base/path/ dir exists and /base/path/sub/ doesn't, then the following fails:
(new Writer('/base/path')).write('sub/foo.html', 'foo')
//=> Error: ENOENT: no such file or directory, open '/base/path/sub/foo.html'

This happens, e.g., when there's an foo in the HTML.
This fix uses the mkdirp package to create missing parent directories before writing the file.

Great, thanks!


Bug: Backplates will be displayed when hovering in High Contrast

Description
As the title

Steps To Reproduce

Make Windows HC
Open Files
Hover something that have TextBlock.

Requirements

Remove backplates

Files Version
2.5.20
Windows Version
10.0.22000
Log File
None

Is this only on the sidebar and details layout?

Is this only on the sidebar and details layout?

This is what UIElement.HighContrastAdjustment  will handle
https://learn.microsoft.com/en-us/uwp/api/windows.ui.xaml.uielement.highcontrastadjustment?view=winrt-22621

So all controls using UIElement have this issue.

Is this really an issue? Why isn't that property the default behavior?

@0x5bfa

@0x5bfa

By default they want to prioritise the readability of text.  But because it is not visually appealing, they allow you to set the High Contrast Adjustment - to remove this behaviour | as long as the app developer has ensured the text contrast is readable.
If you want to remove the backplate, check every element to ensure text is always readable

What's the expected design for this?

So is the expected design to have black text without a backplate?

So is the expected design to have black text without a backplate?

Anything highlighted, needs the correct text colour.

There appears to be an issue where setting the property in app.xaml doesn't work. We can work around by setting it on the individual page, but we'd prefer to avoid doing this.

There appears to be an issue where setting the property in app.xaml doesn't work. We can work around by setting it on the individual page, but we'd prefer to avoid doing this.

I should work though, when I tried last time I worked well. But Dialog class and MenuFlyout class doesn't respect this setting in App.xaml so need to set indivisually or we can find another way if any.

@0x5bfa it's not too bad if it's just dialogs and menu flyouts. Let's do this 👍

Alright!

This should be resolved in main.


Add pruneicebergscancolumn rule

related with #1030
This pr will prune unnecessary column during scanning. Which will make query consume less memory.
before
PLAN FRAGMENT 24
 OUTPUT EXPRS:
  PARTITION: RANDOM

  STREAM DATA SINK
    EXCHANGE ID: 06
    UNPARTITIONED

  5:Project
  |  <slot 52> : 52: ca_address_sk
  |  <slot 59> : 59: ca_county
  |
  4:IcebergScanNode
     TABLE: customer_address
     cardinality=250000
     avgRowSize=19.8634
     numNodes=0

after
PLAN FRAGMENT 24
 OUTPUT EXPRS:
  PARTITION: RANDOM

  STREAM DATA SINK
    EXCHANGE ID: 03
    UNPARTITIONED

  2:IcebergScanNode
     TABLE: customer_address
     cardinality=250000
     avgRowSize=5.48192
     numNodes=0

cc @DorianZheng @dirtysalt @stephen-shelby

Does PruneIcebergScanColumnRule share a lot code with PruneHiveScanColumnRule? Could we extract a common class to handle both? It's very hard to maintain both hive and iceberg rules.

Does PruneIcebergScanColumnRule share a lot code with PruneHiveScanColumnRule? Could we extract a common class to handle both? It's very hard to maintain both hive and iceberg rules.

i will change later @dirtysalt

Does PruneIcebergScanColumnRule share a lot code with PruneHiveScanColumnRule? Could we extract a common class to handle both? It's very hard to maintain both hive and iceberg rules.

I will refactor these codes later @dirtysalt

I refactored this code
PTAL thanks!

@Seaven PTAL

@caneGuy You should add UT for the your change.


Multplile sprity() calls will create the same sprite

In a project, I have to create multiple sprites for different image size (like 1 for 16x16, 1 for 32x32 and so on)
In the same gulpfile i have multiple tasks to generate those sprites.
When i call a task which require the subtasks with
gulp.task('sprites', ['sprites_16', 'sprites_32', 'sprites_64', 'sprites_500'], function() {});

Every png is the same, and contains every image.

try gulp-sequence
https://www.npmjs.com/package/gulp-sequence

@stephanedemotte It works, but also doing parallels tasks the resut is very mixed.
I think someone should check for work isolation.

@ZxBud I also have such a problem, So I can only run tasks one by one to solve.

+1

Should be resolved with #40.


[FR] Add schemas for Origins' "Miscellaneous" types (eg. advancements)

I didn't see it suggested before, but it would be cool to have that in this beauty of a vs plugin.
From what I saw and read, this plugin currently does not support schemas for the types listed on Origins Docs in the "MISCELLANEOUS" tab on the left.
So that would be:

Advancement triggers
Item Modifiers (also in loot tables' functions)
Items (so just origins:orb_of_origin)
Predicates (also in loot tables' conditions)

I don't think adding support for commands would be nessesary, as there is no support for other commands in "execute_command" action type anyway

If you wanted to add it, I also hope that It could be compatible with the Data-pack Helper Plus plugin I'm using for writing datapack, for example advancements, because it currenlt marks it as an error and I wouldn't want its schemas overwritten

I didn't see any alternatives that would have that kind of schemas, so I hope you would be interested in my request

Vanilla files are out of scope for this plugin.
DPH 4.0 is in development and adds updated and improved schemas for these files. You can follow it's development here: https://discord.gg/EbdseuS.
They're pretty close to releasing v4.0.


workflow.py:2080 ERROR    'favorites'

I tried the workflow and couldn't make it work. I couldn't say whether it is because of a bug of because I missed a configuration step.
I imported the workflow added the APP_ID variable before running the workflow, didn't add any currency to the favorites list as I couldn't. I didn't work.
Apparently there is a problem with the favorites as I got this error.
[23:58:14.285] Productivity Coon[Script Filter] Queuing argument '(null)'
[23:58:18.468] Productivity Coon[Script Filter] Script with argv '(null)' finished
[23:58:18.474] STDERR: Productivity Coon[Script Filter] .
23:58:17 workflow.py:2061 DEBUG    ---------- Productivity Coon (1.0.0) ----------
23:58:17 workflow.py:1468 DEBUG    reading settings from /Users/Username/Library/Application Support/Alfred/Workflow Data/tech.tomy.coon/settings.json
23:58:17 workflow.py:2338 INFO     checking for update ...
23:58:17 background.py:233 DEBUG    [__workflow_update_check] command cached: /Users/Username/Library/Caches/com.runningwithcrayons.Alfred/Workflow Data/tech.tomy.coon/__workflow_update_check.argcache
23:58:17 background.py:237 DEBUG    [__workflow_update_check] passing job to background runner: [u'/usr/bin/python', '/Users/Username/Dropbox/Applications_Backups/Alfred_Backups/Backup_Alfred/Alfred.alfredpreferences/workflows/user.workflow.08009832-5D2F-4E5A-BE10-9B257CBB7595/currency/workflow/background.pyc', u'__workflow_update_check']
.
23:58:17 workflow.py:2061 DEBUG    ---------- Productivity Coon (1.0.0) ----------
23:58:17 background.py:243 DEBUG    [__workflow_update_check] background job started
.
23:58:17 workflow.py:2061 DEBUG    ---------- Productivity Coon (1.0.0) ----------
23:58:17 workflow.py:2338 INFO     checking for update ...
23:58:17 background.py:225 INFO     [__workflow_update_check] job already running
23:58:18 query.py:72 INFO     Run Pattern 0
23:58:18 workflow.py:2080 ERROR    'favorites'
Traceback (most recent call last):
  File "/Users/Username/Dropbox/Applications_Backups/Alfred_Backups/Backup_Alfred/Alfred.alfredpreferences/workflows/user.workflow.08009832-5D2F-4E5A-BE10-9B257CBB7595/currency/workflow/workflow.py", line 2073, in run
    func(self)
  File "/Users/Username/Dropbox/Applications_Backups/Alfred_Backups/Backup_Alfred/Alfred.alfredpreferences/workflows/user.workflow.08009832-5D2F-4E5A-BE10-9B257CBB7595/currency/__init__.py", line 66, in convert
    query.run_pattern(workflow, rates)
  File "/Users/Username/Dropbox/Applications_Backups/Alfred_Backups/Backup_Alfred/Alfred.alfredpreferences/workflows/user.workflow.08009832-5D2F-4E5A-BE10-9B257CBB7595/currency/query.py", line 74, in run_pattern
    func(workflow, rates)
  File "/Users/```
[23:58:14.285] Productivity Coon[Script Filter] Queuing argument '(null)'
[23:58:18.468] Productivity Coon[Script Filter] Script with argv '(null)' finished
[23:58:18.474] STDERR: Productivity Coon[Script Filter] .
23:58:17 workflow.py:2061 DEBUG    ---------- Productivity Coon (1.0.0) ----------
23:58:17 workflow.py:1468 DEBUG    reading settings from /Users/Username/Library/Application Support/Alfred/Workflow Data/tech.tomy.coon/settings.json
23:58:17 workflow.py:2338 INFO     checking for update ...
23:58:17 background.py:233 DEBUG    [__workflow_update_check] command cached: /Users/Username/Library/Caches/com.runningwithcrayons.Alfred/Workflow Data/tech.tomy.coon/__workflow_update_check.argcache
23:58:17 background.py:237 DEBUG    [__workflow_update_check] passing job to background runner: [u'/usr/bin/python', '/Users/Username/Dropbox/Applications_Backups/Alfred_Backups/Backup_Alfred/Alfred.alfredpreferences/workflows/user.workflow.08009832-5D2F-4E5A-BE10-9B257CBB7595/currency/workflow/background.pyc', u'__workflow_update_check']
.
23:58:17 workflow.py:2061 DEBUG    ---------- Productivity Coon (1.0.0) ----------
23:58:17 background.py:243 DEBUG    [__workflow_update_check] background job started
.
23:58:17 workflow.py:2061 DEBUG    ---------- Productivity Coon (1.0.0) ----------
23:58:17 workflow.py:2338 INFO     checking for update ...
23:58:17 background.py:225 INFO     [__workflow_update_check] job already running
23:58:18 query.py:72 INFO     Run Pattern 0
23:58:18 workflow.py:2080 ERROR    'favorites'
Traceback (most recent call last):
  File "/Users/Username/Dropbox/Applications_Backups/Alfred_Backups/Backup_Alfred/Alfred.alfredpreferences/workflows/user.workflow.08009832-5D2F-4E5A-BE10-9B257CBB7595/currency/workflow/workflow.py", line 2073, in run
    func(self)
  File "/Users/Username/Dropbox/Applications_Backups/Alfred_Backups/Backup_Alfred/Alfred.alfredpreferences/workflows/user.workflow.08009832-5D2F-4E5A-BE10-9B257CBB7595/currency/__init__.py", line 66, in convert
    query.run_pattern(workflow, rates)
  File "/Users/Username/Dropbox/Applications_Backups/Alfred_Backups/Backup_Alfred/Alfred.alfredpreferences/workflows/user.workflow.08009832-5D2F-4E5A-BE10-9B257CBB7595/currency/query.py", line 74, in run_pattern
    func(workflow, rates)
  File "/Users/Username/Dropbox/Applications_Backups/Alfred_Backups/Backup_Alfred/Alfred.alfredpreferences/workflows/user.workflow.08009832-5D2F-4E5A-BE10-9B257CBB7595/currency/query.py", line 82, in pattern_0
    for currency in settings["favorites"]:
KeyError: 'favorites'
23:58:18 workflow.py:2082 INFO     for assistance, see: https://git.io/fjD6M
23:58:18 workflow.py:2103 DEBUG    ---------- finished in 0.840s ----------
23:58:18 workflow.py:2254 DEBUG    set last run version: 1.0.0
23:58:18 workflow.py:2103 DEBUG    ---------- finished in 1.464s ----------
[23:58:18.495] Productivity Coon[Script Filter] {"items": [{"valid": false, "subtitle": "'favorites'", "icon": {"path": "/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/AlertStopIcon.icns"}, "title": "Error in workflow 'Productivity Coon'"}]}

```/Dropbox/Applications_Backups/Alfred_Backups/Backup_Alfred/Alfred.alfredpreferences/workflows/user.workflow.08009832-5D2F-4E5A-BE10-9B257CBB7595/currency/query.py", line 82, in pattern_0
    for currency in settings["favorites"]:
KeyError: 'favorites'
23:58:18 workflow.py:2082 INFO     for assistance, see: https://git.io/fjD6M
23:58:18 workflow.py:2103 DEBUG    ---------- finished in 0.840s ----------
23:58:18 workflow.py:2254 DEBUG    set last run version: 1.0.0
23:58:18 workflow.py:2103 DEBUG    ---------- finished in 1.464s ----------
[23:58:18.495] Productivity Coon[Script Filter] {"items": [{"valid": false, "subtitle": "'favorites'", "icon": {"path": "/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/AlertStopIcon.icns"}, "title": "Error in workflow 'Productivity Coon'"}]}

Sorry, that was my bad.
This issue occurred when new install doesn't have an settings,
which I just patched in v1.0.1.
Please try installing the newest release,
and let me know if there's any other problem.
Thanks. 😛

Installed the newest version. Working.


windows_eventlog requires old version of puppetlabs-registry and blocks its upgrade

Affected Puppet, Ruby, OS and module versions/distributions

Puppet: 6.15.0
Ruby: built-in
Distribution: RHEL
Module version: 3.0.0

How to reproduce (e.g Puppet code you use)
attempt to update puppetlabs-registry
What are you seeing
'puppet-windows_eventlog' (v3.0.0) requires 'puppetlabs-registry' (>= 1.1.1 < 3.0.0)
What behaviour did you expect instead
Output log
Any additional information you'd like to impart
Current version of puppetlabs-registry is 3.1.0. Can you please support it in this module? Thank you

Closing as this functionality has been added in #68


Remove defaultProps from FlatList

Summary
Issue #31602. Remove defaultProps from FlatList.
Changelog
[JavaScript] [Changed] - Remove defaultProps from FlatList
Test Plan
All test for FlatList pass.
https://user-images.githubusercontent.com/57131123/124164691-4066c980-daa1-11eb-8653-5c51640fe63e.mov

@lunaleaps Could you review the pull request? I would be very grateful 😊

Looks good, thank you so much for working on this! Small comments about adding more documentation in the props about defaults. Let me know if you want to add those or I can add them on land. @joxw1 Let me know your call and I'll import :)

One thing that came up to my mind while reviewing my changes: Should I introduce a constant for all the {numColumns = 1 } assignments? Something like {numColumns = DEFAULT_NUM_COLUMNS} ? What is your opinion on that @lunaleaps ? And thank you very much for your review! 🚀

One thing that came up to my mind while reviewing my changes: Should I introduce a constant for all the {numColumns = 1 } assignments? Something like {numColumns = DEFAULT_NUM_COLUMNS} ? What is your opinion on that @lunaleaps ? And thank you very much for your review! 🚀

That's a good idea! I think the concern is that someone introduces a new read of the prop and doesn't set a default value. I think using a constant like that could help make it clearer if they miss it. In other work I've also created a dedicated accessor function like getNumColumnsOrDefault which serves a similar purpose.

One thing that came up to my mind while reviewing my changes: Should I introduce a constant for all the {numColumns = 1 } assignments? Something like {numColumns = DEFAULT_NUM_COLUMNS} ? What is your opinion on that @lunaleaps ? And thank you very much for your review! 🚀

That's a good idea! I think the concern is that someone introduces a new read of the prop and doesn't set a default value. I think using a constant like that could help make it clearer if they miss it. In other work I've also created a dedicated accessor function like getNumColumnsOrDefault which serves a similar purpose.

Done! For the naming of the accessor functions I followed the VirtualizedList class, where the accessor functions have the variable name as prefix (e.g. horizontalOrDefault(...)). Thank you very much for the nice suggestion 😊

@lunaleaps Any updates on this?


Added Kaluga branch of Bauman Moscow State Technical University domain

@aleffnull Pull request merged. Thank you.


How to set appropriate values in .yaml file to avoid low GPU-uti but high GPU Memory-usage?

I used torch==1.9.0 and cuda=11.1, with two A40 GPUs. The code could work if "fill_value" is removed from the inputs to scatter_max function in Line 78 in mapnet.py .
The fps is nearly 30.
What confuses me is that the "GPU-util" is extremely low (<10%) and the "GPU Memory-usage" is high (nearly 50%) when training a model (e.g., the "ans-depth" model).  The GPU-util of the GPU for SIMULATOR and MAPPER is nearly 0. Is this normal or is there something wrong due to the change of installation environments?
What should I do to improve the GPU-util? Is it possible to improve the GPU-util by setting the config values in .yaml file? What's the relationship between RL.ANS.MAPPER.replay_size and map_batch_size and NUM_PROCESSES? I have no idea on how to setting appropriate values for "replay_size" and "map_batch_size". It will be of great help is some explanations could be provided.

I would like to close this issue sicen I got the appropriate values after trying several times.

Hi @AgentEXPL. Thank you for bringing up this issue. I've only trained this model with 8 GPUs and 16/32GB memory per GPU. So I don't have a good answer to this. But this is something valuable to know for others in the community. Can you send a pull request to the README on how you resolved this?

Hi @srama2512 . Actually, I am not sure whether my answer is the right answer. I only test two models: ans_depth model and occant_depth model. From my experience, the GPU for SIMULATOR would occupy relatively high GPU-memory with low GPU-util when the NUM_PROCESSES is relatively high. The NUM_PROCESSES can be set according to the total memory of the GPU, where each process would occupy nearly 2~3G memory.  As for the GPU-util resource, it is mainly occupied by the MAPPER if occupancy anticipation model is used when ans_depth and occant_depth is compared, the occant_depth is able to achieve high GPU-util.
The following is one of my settings. I would like to set the GPU be used for both mapper and simulator if I do not have enough GPUs.
Setting 1:
two A40 GPUs, each of which has 48 memory.
BASE_TASK_CONFIG_PATH: "configs/exploration/gibson_train.yaml"
TRAINER_NAME: "occant_exp"
ENV_NAME: "ExpRLEnv"
SIMULATOR_GPU_ID: 4
SIMULATOR_GPU_IDS: [4,5]
TORCH_GPU_ID: 4
VIDEO_OPTION: ["disk", "tensorboard"]
TENSORBOARD_DIR: "tb"
VIDEO_DIR: "video_dir"
EVAL_CKPT_PATH_DIR: "data/new_checkpoints"
NUM_PROCESSES: 18
SENSORS: ["RGB_SENSOR", "DEPTH_SENSOR"]
CHECKPOINT_FOLDER: "data/new_checkpoints"
NUM_EPISODES: 10000
T_EXP: 1000
RL:
PPO:
# ppo params
ppo_epoch: 4
num_mini_batch: 4
ANS:
# Uncomment this for anticipation reward
# reward_type: "map_accuracy"
image_scale_hw: [128, 128]
MAPPER:
map_size: 65
registration_type: "moving_average"
label_id: "ego_map_gt_anticipated"
ignore_pose_estimator: False
map_batch_size: 120
use_data_parallel: True
replay_size: 100000
gpu_ids: [4,5]
OCCUPANCY_ANTICIPATOR:
type: "occant_depth"


make-process--with-editor-process-filter: Wrong type argument: stringp, 2000

I encountered the above error. I can use the gpy.py in the elpa folder but not calling it from my emacs 28.1 with gpt.el.

solved with
(setq gpt-openai-max-tokens "2000")
(setq gpt-openai-temperature "0")


JSONEachRow parsing: null values

JSONEachRow format for KafkaEngine seems not to be able to parse null values such as:
... ,"voucher":null, ...

2018.08.02 16:49:47.798295 [ 21 ] <Error> executeQuery: Code: 26, e.displayText() = DB::Exception: Cannot parse JSON string: expected opening quote: (while read the value of key voucher): (at row 1)

I understand this is a limitation of the JSON Parser.
However, how to feed null values into a table? I've read in docs that NULLs are not supported for default values at least, but some other issues seem to give support to them.

try to omit null attributes, JSONEachRow treat {} the same as {"voucher":null}

NULLs are supported. This is documentation issue.
You can insert NULLs from JSONEachRow if you have Nullable data type in your table: by writing them as null or by omitting the key and value pair. The latter is treated as inserting default value.

Documentation is ready.


Update data-protection-kubernetes-astra-azure-netapp-files-content.md

Textual updates to include Trident and backup functionality
Before selecting the "Create pull request" button:

Enter a meaningful title above^, using a prefix if necessary and keywords "New" or "Update" indicating the nature of changes.

Describe the summary, scope, and intent of this PR:
Astra Control Service (ACS) adds value to AKS with persistent volume management and backup integration.

Insert links(s) to any related work item(s) or supporting detail:
[DELETE-OR-REPLACE-THIS-TEXT]

AFTER YOUR PR HAS BEEN CREATED, expand this section for tips and additional instructions.
These are common guidelines for contributions across the repos managed by the Cloud Architecture Content Team (CACT). Some repositories may have additional specific requirements that are not listed here.
Guidance for all contributors

Topic
Guidance

Draft PR
If your PR will be a work-in-progress for more than a day or two, select the Convert to draft link in the upper right of the page (under Reviewers) to change it to a draft. For future reference, you can also do this using the Create pull request button drop-down during PR creation.

ms.date metadata
Don't update an article's "ms.date" metadata property unless you've done a full freshness review of the content. A full freshness review includes changes required to correct or improve the full technical accuracy of the article.Don't update "ms.date" if you're doing targeted changes to improve non-technical aspects of the article, such as editorial quality, art improvements, article template alignment, etc.If you've changed any "ms.date" properties for work that wasn't part of full review for freshness, please reset them to their previous value.

Placement and linking
If you're creating a new article or articles, include updates to the related TOC.yml file to propose where the article(s) should be placed. Also consider other places within the document set where it would be beneficial to cross-reference and link to your new article(s).

PR build
After you open your PR, and for each successive commit that you push to your branch, the publishing platform will run validation on the files in your pull request. A summary of the build results for each file will be inserted inline into your pull request, which includes any build suggestions/warnings/errors. PRs cannot be merged until all build errors and most warnings are resolved.

Publishing
Following a successful merge, most repos publish to the live site at least once per (business) day, usually around 10am Pacific.

Additional resources
Learn.Microsoft.Com contributor guide

Additional guidance for private repos and internal contributors

Topic
Guidance

PR size
If your PR is more than ~5 lines of changes, or you'd like for the changes to go through editorial or larger review, open a contribution request at https://aka.ms/Contribution and include a link to the PR in response #8. Once it's processed, you'll be notified of the next steps.

PR title prefix
Select the Edit button to the right of the PR title if you need to revise it. The following prefixes are reserved for specific contribution types:[Quality Check] - maintenance work related to content quality (edit passes, art improvements, template alignment)[LinkFix] - recurring/adhoc PRs to correct link URLs[Pipeline] - new/updated contributor success pipeline content[WIP] - a work-in-progress draft requiring several days/weeks

PR preview
Following successful build of your PR, publishable files will also include Preview URL links to staged previews of your new/updated articles. Be sure to review these for verification of your intended contributions, or to send to other internal contributors for review.

PR sign-off (public repo)
If an article you own is updated in a public repo PR, you are responsible for sign-off. You will be automatically notified via email. The PR will not be merged until you've had a chance to review and sign-off.

PR sign-off (private repo)
After you've completed your proposed changes, addressed build warnings, and completed all review work, you can begin the sign-off process for review and merge:If your PR is in draft mode, remove "[WIP]" from the title and select Ready for review button at the bottom of the PR.Enter "#sign-off" in a new comment. This comment indicates that you're confident the work meets or exceeds Microsoft's standards for publication, and will trigger the review process.Your PR may be selected for initial review by the CACT. Following CACT review, you may receive questions or requests for additional changes. You should have initial feedback from CACT review within a few business days. If you have an urgent request or need to contact the team, please mention @MicrosoftDocs/cloud-architecture-content-team-pr-reviewers in your PR and someone will get back to you. After CACT review is complete, a CACT #sign-off will be added.Final review/merge is done by the PR review team. The PR team may also respond with feedback, categorized as "Blocking" (requires action from you), or "Non-blocking" (to be addressed in a future PR).

Additional resources
Learn.Microsoft.Com internal contributor guideAuthoring templates: architecture-center-pr, well-architected-prTo contact the CACT use e-mail, or @mention our GitHub team in your PR comments using: @MicrosoftDocs/cloud-architecture-content-team-pr-reviewers

Hi @arntdg,
Did you intend to open this PR in the private repo, architecture-center-pr, instead of the public one?

Hi Courtney,
The purpose of the PR is to update the existing article.
I was notified of the article expiry toward the end of January 2024.
I hope this helps.
With kind regards/Met vriendelijke groeten,
@.***
Arnt de Gier
Azure NetApp Files Technical Marketing Engineer
Mobile: +31613384557 – Email<EMAIL_ADDRESS>|<EMAIL_ADDRESS>https://azure.microsoft.com/services/netapp/https://azure.microsoft.com/en-us/services/netapp/
Azure NetApp Files documentation found herehttps://docs.microsoft.com/azure/azure-netapp-files/
From: Courtney Wales @.>
Sent: dinsdag 2 januari 2024 17:53
To: MicrosoftDocs/architecture-center @.>
Cc: de Gier, Arnt @.>; Mention @.>
Subject: Re: [MicrosoftDocs/architecture-center] Update data-protection-kubernetes-astra-azure-netapp-files-content.md (PR #4348)
EXTERNAL EMAIL - USE CAUTION when clicking links or attachments
Hi @arntdghttps://github.com/arntdg,
Did you intend to open this PR in the private repo, architecture-center-pr, instead of the public one?
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/architecture-center/pull/4348#issuecomment-1874282434, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUSZSYIDCWKHBKSS2T3MLEDYMQ3OXAVCNFSM6AAAAABBKI2QF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZUGI4DENBTGQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


caching support

When using docker we often setup a cache for things to download(eg cargo metadata & packages) and sometimes things that are compiled eg rust libs etc since rust can incrementally rebuild based on only what needs to be rebuilt. An example would be'
RUN --mount=type=cache,target=/usr/local/cargo/registry \
    --mount=type=cache,target=/app/target \
    cargo build --release

This allows for large projects to be build in minutes, especially when cross compiling for non-native archs(eg aarch64 on amd64) normally due having to clean build from scratch this cause build times to be almost half a day on medium/large size rust projects when cross compiling.

It seems reasonable to have, but some care will have to be put into how the caches get maintained.  I'm inclined to leave that as a concern outside melange itself, as different users will have different usecases.
There is already --cache-dir, which could be extended for this purpose.  What do you think, @imjasonh?

I'm for it.
In theory folks can already do this today at head, but it's a bit of a hack, and we could make it more sturdy and flexible.
The current implementation added in https://github.com/chainguard-dev/melange/pull/143 just makes the directory /var/cache/melange accessible to the build environment, so if one build writes to /var/cache/melange/hello then a subsequent build can read it. This is used by fetch to avoid wgets if possible. If we decide to recommend this for broader usage we should document or require checksum checking to avoid cache poisoning.


filesystem.gd returns paths with two forward slashes between directory and file name

Description
When filesystem._list is called, the paths that it returns are like res://path/to//filename.gd. This caused a few problems when I tried to load the templates to copy them.
Possible Fix
In filesystem.gd at line 27 -
var absolute_path: String = "%s/%s" % [path, name]

here, the / between the two %s could be removed, but when I tried that, WAT.tscn kept causing the editor to crash and the error message indicated cyclic reference.
The crashes happened if the addon was enabled, if the scene was opened or if the scene was run (in this case, only the preview window crashed).

Is this causing any issues at the moment or only when you were first trying to do it?

There aren't any noticeable problems right now. It just causes a hiccup when you try to add/modify anything that uses it. In the case of script templates, I couldn't use i.path and instead had to use script_templates_dir + "/" + i.name.

This is odd. It seems to show up with one slash when printing the absolute path from line 27 for me.

The extra slash might be coming from somewhere else.

(Also to be clear res/user is supposed to be a double slash).

The extra slash you added when you were saving the WATTemplate was redundant since the script_templates directory ends with a forward slash.

Okay. This is actually weird as hell. It shows differently from the print and the slash.

Okay found the issue. You had placed a leading underscore at the wat_templates_dir string. So when you passed that directory to the filesystem.list method, then filesystem was adding an additional slash on top of the one you gave.

Ah ok. That sort of explains the crash, the scene was looking for a path that didn't exist? I'm not entirely sure.

Yeah the crash was the scene trying to look for testdirectorytestscript rather than testdirectory/testscript


Implement reactions

It would be really fun to be able to write (text) reactions to some submissions

Very fun idea!


API to get cluster logs

Currently there is no REST API available to get cluster logs -- stdout, stderr, log4j-active.log, executor logs.
We can only download it via UI. (or use a custom log delivery and pick it from there).
Can you please add a API that allows us to get these logs via REST API ?

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

ID: 25b5fd38-af0a-12e9-e8f8-3e57bcbc273f
Version Independent ID: f3a0cfcb-99eb-77c4-c888-4045d5d93947
Content: REST API 2.0 - Azure Databricks
Content Source: databricks/dev-tools/api/latest/index.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@vijayrajah  Thanks for the feedback. Currently, we don't have any API to get the cluster logs.
We appreciate it. We will share and elevate your feedback with the Azure Azure Databricks product team.
REST API available for enabling logs: This feature is also available in the REST API. See Clusters API and Cluster log delivery examples.

@vijayrajah  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Antivirus block

I have been upgraded my Avast yet. Then I have try to download latest Git release for Windows x32  (v2.9.3). But Avast have blocked downloading with message:
object:
https://github-cloud.s3.amazonaws.com/releases/23216272/148...
.
Win32:Shiz [Spy]
Process:
C:\Program Files\Google\Chrome\Applications\chrome.exe

Also I don't know how to avoid anti-virus blocking. How can I do this?
And why Avast think that git downloading is dangerous?

Also it is the same problem when using Internet Explorer

Hey, this is the issue tracker for the git-scm.com website, not Git itself. If you still want to discuss this issue, you should reach out to the community.


added helper property to easily access clear control scale

Added helper property to easily access Clear Control dataset scale.
This property could be part of the abstract database class. It isn't ergonomic to manually query the scale from the metadata every time.
I don't know why but linting did some changes again.

Minor comment: can also add a simple test for this.

@JoOkuma I'm working on related stuff in #122.

It's ready for review.

@ziw-liu , CI error is not related to the changes.


[regression] update test framework and fix cases

Proposed changes
Issue Number: close #xxx
Problem Summary:
modify regression test framework in order to support cases from ssb_sf1 tpcds_sf1 tpch_sf1, which I will do in next pr.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Have you tested that how long it takes to run? with 16c 64g single node BE?

this pr meets the bug https://github.com/apache/doris/issues/10766 too, maybe need to rebase master when the bug fixed

regression test exclude suite test_create_table_with_bloom_filter temporarily


[BEAM-13799] Create an Interactive Beam Dataproc package for users to manage clusters with

Adds code to automatically create a Dataproc cluster configured with Docker and Flink if a user instantiates an InteractiveRunner using underlying_runner='FlinkRunner'
By default, the created Dataproc cluster will be called 'interactive-beam-cluster' and will persist even after the kernel is interrupted
Users additionally will have the ability to:

specify a name of their choosing for the created cluster, a warning is raised to notify the user that they will have to delete the cluster on their own
toggle an automatic deletion of the cluster with the default name, 'interactive-beam-cluster' when the kernel is interrupted
delete the cluster with the default name, 'interactive-beam-cluster'

BEAM-13799

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @KevinGG
R: @rohdesamuel


Having PYTHONWARNINGS=default crashes pytest discovery

Type: Bug

Behaviour
Expected vs. Actual
When opening vscode with PYTHONWARNINGS=default and a warning is given it will fail discovering and error out. I would assume it could handle the warning.
Steps to reproduce:

Set export PYTHONWARNINGS=default
Open code from terminal with code .
Have a module with a warning in it (for me it is playwright-pytest).

I have used the following environment:

mamba create -n tmp python=3.10 pytest
mamba install playwright -c microsoft -y
pip install pytest-playwright

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.10.7
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
Value of the python.languageServer setting: Pylance

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

> conda run -n tmp --no-capture-output python ~/.vscode/extensions/ms-python.python-2022.18.2/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.18.2/pythonFiles/printEnvVariables.py
> conda run -n tmp --no-capture-output python ~/.vscode/extensions/ms-python.python-2022.18.2/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.18.2/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . -s --cache-clear .
cwd: .
[ERROR 2022-10-21 21:58:29.261]: Error discovering pytest tests:
 [n [Error]: <frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
<frozen importlib._bootstrap>:914: ImportWarning: _SixMetaPathImporter.find_spec() not found; falling back to find_module()
/home/shh/miniconda3/envs/tmp/lib/python3.10/tempfile.py:860: ResourceWarning: Implicitly cleaning up <TemporaryDirectory '/tmp/playwright-pytest-bus6_mv3'>
  _warnings.warn(warn_message, ResourceWarning)

	at ChildProcess.<anonymous> (/home/shh/.vscode/extensions/ms-python.python-2022.18.2/out/client/extension.js:2:242843)
	at Object.onceWrapper (node:events:646:26)
	at ChildProcess.emit (node:events:526:28)
	at maybeClose (node:internal/child_process:1092:16)
	at ChildProcess._handle.onexit (node:internal/child_process:302:5)]

User Settings

languageServer: "Pylance"

linting
• flake8Args: "<placeholder>"
• flake8Enabled: true
• mypyArgs: "<placeholder>"
• mypyEnabled: true

formatting
• provider: "black"

testing
• pytestArgs: "<placeholder>"
• pytestEnabled: true

Extension version: 2022.18.2
VS Code version: Code 1.73.1<PHONE_NUMBER>f055b99068d3688932416f2346dd3b, 2022-11-09T03:54:53.913Z)
OS version: Linux x64 6.0.6-76060006-generic
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 9 5900X 12-Core Processor (24 x 4171)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 1

Memory (System)
125.72GB (116.09GB free)

Process Argv
/home/shh/bin

Screen Reader
no

VM
0%

DESKTOP_SESSION
pop

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
pop

XDG_SESSION_TYPE
x11

This is due to us parsing the output from pytest at the moment. We are working on rewriting our pytest support so that our integration is via a pytest plug-in, but that work is still ongoing.

Hello! We have just finished our testing rewrite and are beginning the roll out to users. I have tested this issue with the re-write and I am no longer reproducing the bug! If you would like to try it yourself, you need to add this setting to your users settings.json "python.experiments.optInto": ["pythonTestAdapter"]. Let me know if it doesn’t work for you and we can re-open this issue. Thanks!

I'm still seeing problems with the new test adapter. I think it can't handle skipping tests:
2023-07-18 20:05:08.167 [info] Experiment 'pythonTestAdapter' is active
2023-07-18 20:05:08.167 [info] Test server listening.
2023-07-18 20:05:08.167 [info] Python interpreter path: ~/miniconda3/envs/holoviz/bin/python
...
2023-07-18 20:05:21.099 [error] pytest test discovery error
 unittest.case.SkipTest: Could not import cuDF, skipping cuDFInterface tests.
 Check Python Test Logs for more details.

Emitted here: https://github.com/holoviz/holoviews/blob/003be4133a13949bf9bf081729e8fd2014cb511b/holoviews/tests/core/data/test_cudfinterface.py#L10
Do you want me to open a new issue?

Do you want me to open a new issue?

@Hoxbro  Yes please! Instructions can be found at https://aka.ms/pvsc-bug .


added support for dark theme in fire dialog

Task/Issue URL: https://app.asana.com/0/1157893581871903/1173834809155121
Description:
The Fire Dialog was shown in white even thought the user had selected dark theme. This PR fixes that
Steps to test this PR:

Open the app
Tap on the Fire Icon

Screenshots:
API 21:

Light Theme
Dark theme

API 29:

Light Theme
Dark theme

Internal references:
Software Engineering Expectations
Technical Design Template

As per our discussion, I'll be closing this until the Product Review is created and accepted


Update dependencies to cocoapods 0.39.0

Hey slather team,
I have updated slather's dependencies to use cocoa pods 0.39.0
Cheers
tarbrain

Thanks for looking into this @tarbrain ! Would you mind squashing the commits down using git rebase -i? Would love to get this all in with one commit, as not to muck up the git history. Once it's squashed, it should be good to merge!

Ok, I did a new PR: https://github.com/venmo/slather/pull/106


Single quoutes in gstreamer wrapper prevent evaluation of profile plugins path search

Description: what the title says.

cat "$(nix-store -r "$(nix-instantiate '<nixpkgs>' -A gst_all_1.gstreamer.dev)")"/bin/gst-launch-1.0

#! /nix/store/...-bash-4.4-p23/bin/bash -e
export GST_PLUGIN_SYSTEM_PATH=$GST_PLUGIN_SYSTEM_PATH${GST_PLUGIN_SYSTEM_PATH:+':'}'$(unset _tmp; for profile in $NIX_PROFILES; do _tmp=$profile/lib/gstreamer-1.0${_tmp:+:}$_tmp; done; printf $_tmp)'
exec -a "$0" "/nix/store/...-gstreamer-1.14.4-dev/bin/.gst-launch-1.0-wrapped"  "${extraFlagsArray[@]}" "$@"

There are single quotes around the plugin search in NIX_PROFILES, preventing it from evaluation on runtime. (i.e. '$(unset _tmp; ... printf $_tmp)', instead of "$(unset _tmp; ... printf $_tmp)")
Steps to reproduce

nix-env -iA nixos.gst_all_1.gstreamer
nix-env -iA nixos.gst_all_1.gst-plugins-good
gst-launch-1.0 pulsesrc ! fakesink

ERROR: pipeline could not be constructed: no element "pulsesrc".

(Same behavior can be achieved by placing gst_all_1.gstreamer and gst_all_1.gst-plugins-good in your configuration.nix)
Expected behavior

cat "$(nix-store -r "$(nix-instantiate '<nixpkgs>' -A gst_all_1.gstreamer.dev)")"/bin/gst-launch-1.0

#! /nix/store/...-bash-4.4-p23/bin/bash -e
export GST_PLUGIN_SYSTEM_PATH=$GST_PLUGIN_SYSTEM_PATH${GST_PLUGIN_SYSTEM_PATH:+':'}"$(unset _tmp; for profile in $NIX_PROFILES; do _tmp=$profile/lib/gstreamer-1.0${_tmp:+:}$_tmp; done; printf $_tmp)"
exec -a "$0" "/nix/store/...-gstreamer-1.14.4-dev/bin/.gst-launch-1.0-wrapped"  "${extraFlagsArray[@]}" "$@"

nix-env -iA nixos.gst_all_1.gstreamer
nix-env -iA nixos.gst_all_1.gst-plugins-good
gst-launch-1.0 pulsesrc ! fakesink

Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstPulseSrcClock
Redistribute latency...
...

Additional context
Evaluation trace:
gst-launch-1.0: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/gstreamer/core/default.nix#L63
wrapProgram: https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/setup-hooks/make-wrapper.sh#L139
makeWrapper: https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/setup-hooks/make-wrapper.sh#L33
Workaround: Steal another derivation's (constructed with wrapGappsHook) environment via mkShell.inputsFrom. e.g.

nix-shell =(echo "with (import <nixpkgs> {}).pkgs; mkShell { inputsFrom = [mopidy]; }") --run "gst-launch-1.0 pulsesrc ! fakesink"

Maintainer information:
attribute: gst_all_1.gstreamer.dev

The quote issue was fixed in 9b7742eefc70b94c85c5942f2e4dc52a5b5f5cef
However gst_all_1 sets GST_PLUGIN_SYSTEM_PATH instead of GST_PLUGIN_SYSTEM_PATH_1_0 which makes the setup ineffective. Using the correct variable I'm able to find the pulseaudio plugin.

Thanks, closing the issue.
/close


Allow support for Node.JS <= v0.12.9

A lot of companies still use older versions of Node.JS for a variety of reasons.
That being said the optional dependancy on jsdom (^6.1.0) requires us to be using Node.JS v4 or greater.
My recommendation is to use jsdom (~3.1.2) which is allow support for a greater number of previous versions of Node.JS.
I have ran through the source code and also check the tests whilst using this version of the jsdom dependency and everything looks OK.
I'll submit a PR and link to this ticket for your consideration. (https://github.com/airbnb/enzyme/pull/95)

Looks like this can be closed as the PR is merged.

Closed via #95.


ci: update ci

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Which docs this PR relation:
Ref #
Which toolchain this PR adaption:
No Breaking Change
Special notes for your reviewer:
CI Switch
ci-runs-only: [Code Format, Unit Tests]

/run-ci

/run-ci

/ci

/ci

/ci

/ci

/ci


Auto Complete Not Contextually Correct

Tested versions
Reproducible in 4.2.2 Stable
System information
Godot v4.2.2.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1650 Ti (NVIDIA; <IP_ADDRESS>33) - AMD Ryzen 5 4600H with Radeon Graphics (12 Threads)
Issue description
Autocomplete suddenly isn't Guessing correctly given the context and I don't know why.

look at the screenshot example
Steps to reproduce
Create a var from a node
Minimal reproduction project (MRP)
.

Please show the way you declared animated_sprite is it statically typed as its type?

Closing due to lack of response, if you provide the requested information this can be reopened


Channel not found

Hello I am using the latest version of keycloak-event-listener and I get the following error.
keycloak-to-rabbitmq ERROR sending message: KK.EVENT.ADMIN.demoscope.SUCCESS.CLIENT.UPDATE
keycloak_1   | 09:01:52,367 ERROR [stderr] (default task-16) com.rabbitmq.client.AlreadyClosedException: channel is already closed due to channel error; protocol method: #method<channel.close>(reply-code=404, reply-text=NOT_FOUND - no exchange 'registrations' in vhost '/', class-id=60, method-id=40)

Is there any way to create the channel when starting the process with docker-compose. I tried to find a way to create the channel with the rabbitmq image but with no luck.
Thanks in advance.

That looks like your configuration of Keycloak is trying to send messages to exchange: registrations but that does not exist on your Rabbit. Could you check that, and maybe share your current plugin configuration?

@aznamier Yeap this is actually my problem. I want to create the channel when starting keycloak. I tried to find a way to create it from rabbitmq configuration and I had no luck with it.


Only reuse generated templates. This closes #34

Merged. Thank you!

I was thinking we can actually make it even smarter and reuse any generated template that matches the field definition. No need to limit to last sibling. No harm in doing that. Right? One or two lines of code and a few tests :) if you agree I will do tonight while it's still "hot".
Sent from my iPhone

On May 6, 2015, at 6:17 PM, sergeyshushlyapin<EMAIL_ADDRESS>wrote:
Merged. Thank you!
—
Reply to this email directly or view it on GitHub.

Yep. Sounds reasonable.

Will do
Sent from my iPhone

On May 6, 2015, at 7:01 PM, sergeyshushlyapin<EMAIL_ADDRESS>wrote:
Yep. Sounds reasonable.
—
Reply to this email directly or view it on GitHub.


Protected branch for main?

Do we want to make main a protected branch? This means that  force-pushing to and deleting the branch is disallowed for everyone (unless we specifically allow it). We also have these options available to us:

Require a number of reviews
Require a review from a codeowner
Require that one or more of the PR status checks pass (by default admins can override as needed)

The last one is one I'm interested in, not as a gate-keeping exercise, but it allows us to use "auto-merge". With that we can mark a PR to merge as soon as all of the required checks pass.

+1 for auto-merging, especially for bot-generated maintenance PRs.
I think we're probably ready to implement the "require a review from a codeowner" rule now that we have a sensible team-based codeowner system in place, so that it's very unlikely we'll be stuck waiting on any one individual who might be away/unavailable to review.


Refactor ReDoc to take Cow<'static, str> instead of borrowed str

Same thing as #867, except I modified ReDoc this time.
Breaking changes
Just like #867: I think the removal of the two lifetime parameters on ReDoc can break some code (e.g. when implementing custom traits for ReDoc). As far as the method parameters are concerned, I don't think there are any breaking changes due to the Into<Cow<'static, str> generic.

Just like https://github.com/juhaku/utoipa/pull/867: I think the removal of the two lifetime parameters on ReDoc can break some code (e.g. when implementing custom traits for ReDoc). As far as the method parameters are concerned, I don't think there are any breaking changes due to the Into<Cow<'static, str> generic.

That is true, but the changes are low, but sure when the release is done this is going to be a major release. :slightly_smiling_face:  Just to be explisit about possibility of stuff breaking.


Show WG widget timestamps in system timezone

This change shows each latest handshake time in the WireGuard widget in the timezone of the system, rather than UTC as currently. The change is intended to implement this forum request: https://forum.opnsense.org/index.php?topic=20530.msg95463#msg95463.
As a disclaimer, I am by no means a PHP programmer, but this commit is based on my research. It works when I tested it.

Merged, thanks!

Merged, thanks!

Pleasure. It is nice to be able to make a contribution, however tiny!

Pleasure. It is nice to be able to make a contribution, however tiny!


hvplot histogram: weights, density, cumulative=-1

Is your feature request related to a problem? Please describe.
I was using pandas and matplotlib to make histograms, and they support

density: so I can plot histogram into y range (0, 1), to see things compared w/ the overall counts
weights: normally histogram is ploted as 'user distributions', let's say each user also has some money; how do we plot their account balance histogram? weights can solve this problem.
cumulative=-1: sometimes the data is used in reverse order, and we need to reverse the cdf, so we need to use cumulative in different order; as in https://stackoverflow.com/questions/28889845/tricks-to-get-reverse-order-cumulative-histogram-in-matplotlib

When I want to switch to hvplot, they are not supported, I want to know what am I supposed to do?
Should I calculate the result myself, or should hvplot implement these features?
Thanks?

hvPlot already accepts normed and cumulative, which are then passed to the histogram HoloViews operation.

[ ] Expose weight_dimension
[ ] Document usage of these options

Note that since numpy 1.6.0 the normed parameter of the numpy.histogram function is deprecated in favor of density and that matplotlib.pyplot.hist uses density too. So let's add:

[ ] Expose density rather than normed at the hvPlot level


Vector<>::_ptr is now typed and points to the beginning of the array rather than refcounting block

Godot-s codebase is a breeze to work with. There is one thing, however that drives me crazy: every time I debug something and want to check content of a String I need to do a pointer arithmetic and a cast in watch window.
Therefore I propose to change _ptr to point to the actual array and be typed, and assume that reference count and size is stored before it. I hope that makes sense.

sounds like a good idea, have you tested everything and does this work
properly?
On Fri, Dec 4, 2015 at 1:53 AM, koalefant<EMAIL_ADDRESS>wrote:

Godot-s codebase is a breeze to work with. There is one thing, however
that drives me crazy: every time I debug something and want to check
content of a String I need to do a pointer arithmetic and a cast in watch
window.
Therefore I propose to change _ptr to point to the actual array and be
typed, and assume that reference count and size is stored before it. I hope
that makes sense.
You can view, comment on, or merge this pull request online at:
https://github.com/godotengine/godot/pull/2983
Commit Summary

Vector<>::_ptr is now typed and points to the beginning of array
rather than reference count block

File Changes

M core/vector.h
https://github.com/godotengine/godot/pull/2983/files#diff-0 (42)

Patch Links:

https://github.com/godotengine/godot/pull/2983.patch
https://github.com/godotengine/godot/pull/2983.diff

—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/pull/2983.

My little project works (with and without editor) and I went through the most of the demos - looks good.


add perflab file as a demo

Things To Remember:

Be sure to merge into the right branch. The choices are:

master if your PR runs on the current version of Tableau.
dev-2021.2

You should update at least one of the following:

The changelog of the project you modified.
The root README.md if the PR is a release of the SDK, Connector Packager, or TDVT.
=====

Hi, @lukewrites! Thanks for opening this PR!

In the file tdvt/tdvt/perflab.py:

Line 37:2: W292 no newline at end of file
Line 36:5: F821 undefined name 'case'
Line 31:5: F821 undefined name 'passed'
Line 27:5: F821 undefined name 'perf_iteration'
Line 24:5: F821 undefined name 'tds_name'
Line 23:5: F821 undefined name 'test_name'
Line 22:5: F821 undefined name 'test_set_name'
Line 21:5: F821 undefined name 'suite'

For reference: Error Code Reference, PEP8, Python code style


CosmosDataSource requires Context now?

Can you update the sample code to explain where the ApolloContext is from (package) and how it is created?
export class UserDataSource extends CosmosDataSource<UserDoc, ApolloContext> {}

I'm updating from 0.0.14 where it wasn't required to 0.1.0 where it seems to be required.

Ok, here is what I did to get past the Type Error but honestly not sure why the ApolloContext is listed in the docs and then why I don't really need it.
Changed
export class GameDataSource
  extends CosmosDataSource<GameModel, ApolloContext>
  implements IGameDataSource
{

to
export class GameDataSource
  extends CosmosDataSource<GameModel, any>
  implements IGameDataSource
{

sorry missed the notifications and got behind here.
The context is a type parameter so you can use an enriched type for ApolloContext. I'll add something to the docs on this.


[Bug] Pulsar shutdowns Sink connector on exception

Search before asking

[X] I searched in the issues and found nothing similar.

Version

Pulsar 2.7.3 onwards

Minimal reproduce step

Change any sink implementation for test and call record.fail() from the write method. The processing guarantee for the sink should be set to EFFECTIVELY_ONCE and auto ack should be false.

What did you expect to see?
For the sinks having EFFECTIVE_ONCE guarantee, prior to pulsar v2.7.3 , if there was any exception in record processing, the CompletableFuture callback was swallowing the RuntimeException. From v2.7.3, it is not processed in the callback hence caught by the run method of JavaInstanceRunnable which shutdowns the sink. Is this expected behavior? In this case, on failure, no further processing will happen as the sink is shutdown. Shouldn't this exception be handled and the record be retried and allow other future message processing as well? At least, there should be a config option that would decide to shutdown the sink or keep it running.
What did you see instead?
Pulsar shutdowns the sink service hence that particular record and any further records are not processed by the sink.
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

@sijie @lhotari @eolivelli would be great if you guys can clarify. I can see that this behavior has changed from PR #10618

Runtime exceptions are totally out of control, like Out of memory errors and they can leave the JVM in a unstable status

The behavior you want makes sense when auto acknowledge is turned on, in that case the Sink should acknowledge the message in case of success and nack the message otherwise.

@dlg99 @nicoloboschi @cbornet may be interested in taking a look

Runtime exceptions are totally out of control, like Out of memory errors and they can leave the JVM in a unstable status

@eolivelliWouldn't it be fine to catch all other throwables which aren't java.lang.Errors?

For the sinks having EFFECTIVE_ONCE guarantee, prior to pulsar v2.7.3 , if there was any exception in record processing, the CompletableFuture callback was swallowing the RuntimeException. From v2.7.3, it is not processed in the callback hence caught by the run method of JavaInstanceRunnable which shutdowns the sink. Is this expected behavior? In this case, on failure, no further processing will happen as the sink is shutdown.

@abhilashmandaliya Yes, it seems surprising if the sink is shutdown. Is the sink left in the shutdown state or does it restart automatically?

Shouldn't this exception be handled and the record be retried and allow other future message processing as well? At least, there should be a config option that would decide to shutdown the sink or keep it running.

seems reasonable
@abhilashmandaliya

For the sinks having EFFECTIVE_ONCE guarantee, prior to pulsar v2.7.3 , if there was any exception in record processing, the CompletableFuture callback was swallowing the RuntimeException. From v2.7.3, it is not processed in the callback hence caught by the run method of JavaInstanceRunnable which shutdowns the sink. Is this expected behavior? In this case, on failure, no further processing will happen as the sink is shutdown.

@abhilashmandaliya Yes, it seems surprising if the sink is shutdown. Is the sink left in the shutdown state or does it restart automatically?

@lhotari it gets stuck into shutdown/restart loop as Pulsar will retry the same message again and again.

The behavior you want makes sense when auto acknowledge is turned on, in that case the Sink should acknowledge the message in case of success and nack the message otherwise.

@eolivelli In my case, autoack is set to false.

it gets stuck into shutdown/restart loop as Pulsar will retry the same message again and again.

@abhilashmandaliya Would this problem of being stuck on a "poison message" get resolved if the Sink connector didn't get shutdown?

It seems good behavior to me that a poison pill is handled and not silently ignored. The previous behavior of neither acking nor nacking and just forget about it until there's a restart (consuming some broker and client resources for the message reference) doesn't seem right.
We could catch the exception and nack. The advantage is that you can configure retries and DLQ if the use-case allows it.
Now in some situations such as OOME, it's probably better to let the connector crash and be restarted.
Note that crash loops can have some bad consequences such as spurious bandwidth consumption in k8s/cloud environments (downloading the NAR from BK at each restart).

Thanks for the update @cbornet.

We could catch the exception and nack. The advantage is that you can configure retries and DLQ if the use-case allows it.

I think this will not work directly in the current code. If we nack by calling the fail method on the record, the failure handler will again throw a RuntimeException which will be caught by the JavaInstanceRunnable and this loop will continue. It needs some more changes or please correct me if I am wrong.

while this PR https://github.com/apache/pulsar/pull/14589 was not merged (cherry-picks w/protocol changes), it outlines why we want the sink to crash on unhandled exceptions.

while this PR #14589 was not merged (cherry-picks w/protocol changes), it outlines why we want the sink to crash on unhandled exceptions.

Thanks for the reply @dlg99. I went through PR #14589 and got your point for k8s use case. But let's consider a case where some sink parses some field of the received record and that field is malformed and the sink can't parse it and wants to throw an exception. In this case, it will never come out of a poison message. Shouldn't a config option exist to ignore exception, log it and send an ack to the broker? If we send a nack, this malformed message will never succeed and it will never come out of a poison message.

Thanks for all your review and feedback @eolivelli @lhotari @cbornet @dlg99
What should be the steps further? I am ready to contribute a fix given some guidance :)


Deployment fails with "Login profile size exceeds 32 KiB"

The latest PR merge errored with:
INVALID_ARGUMENT: Login profile size exceeds 32 KiB. Delete profile values to make additional space

This is probably because every time time the deployment GHA runs, we do a login. This is turn generates a ssh key pair.
We should probably do what the error instructs(Delete profile values to make additional space) to make it work again.

solved by https://github.com/2i2c-org/pilot-hubs/pull/216 :tada:

Unfortunately I had to revert the revert in #217, so this isn't solved.

This means we have to do https://github.com/2i2c-org/pilot-hubs/issues/83#issuecomment-716643591 for each new hub again, for now.


Add Hook Mobile provider info

To be consistent, please make your logo 32x32(right now it's 32x18). You can add transparent pixels to empty areas.

I've changed the icon size. Should be 32x32 now.

@ell20 can you provide a bit more description on what your service does? I see there's PINHook  product, but I don't see much documentation on your site beyond 1 paragraph.

Do we want to merge this?

Without more info I don't feel comfortable merging this. Seems like an incomplete product.


Plugin does not function in multiplayer.

The plugin doesn't appear to work in multiplayer, works as expected in single player.
I also tried throwing the plugin on the server as well just in case it needed to be present server-side to function, however that didn't change anything.
Plugin version: v0.3
Game version: v0.4.5 (76ca840)
Platform: Windows
Server Platform: Linux (Unraid Docker)

Hey Steven, thank you for your report. You are indeed correct; unfortunately this plugin currently does not support multiplayer. Since this plugin is not used as often as my other plugins, I'm afraid I won't have the time to add support for multiplayer anytime soon. I will leave the issue open though until I can, or someone else wants to, add the multiplayer support. :)

Ahh, thank you for clarifying.
I just wasn't sure as it had not been mentioned anywhere in the README.md


Alert - Custom field

That will be good if inside the mail sent over alerting system we could include an content like an URL which could contain procedure.
By this way we could a mail template having:

metrics impacted by the alert
current threshold exceed
URL procedure linked to this alert

Just an idea when it's an support team receiving alert. By this way they will know which metrics impacted and whichaction required following the URL procedire included into the alert for resolve the problem ;-)
Thanks for your feedback.
Julien.

Duplicate of #75