Mypy plugins complains if a field is named "kwargs"

Checks

[x] I added a descriptive title to this issue
[x] I have searched (google, github) for similar issues and couldn't find anything
[x] I have read and followed the docs and still think this is a bug

Bug
Exactly what it says on the tin: when using the mypy plugin, mypy complains that the name "kwargs" is already defined.
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.8.2
            pydantic compiled: True
                 install path: ~/.cache/pypoetry/virtualenvs/a-2bdB6j1N-py3.9/lib/python3.9/site-packages/pydantic
               python version: 3.9.6 (default, Jun 30 2021, 10:22:16)  [GCC 11.1.0]
                     platform: Linux-5.11.6-arch1-1-x86_64-with-glibc2.33
     optional deps. installed: ['typing-extensions']

import pydantic

class Test(pydantic.BaseModel): # Name "kwargs" already defined (possibly by an import)
	kwargs: int

This does not happen if Config.extra = "forbid".

We’re no longer actively developing Pydantic V1 (although it will continue to receive security fixes for the next year or so), so we’re closing issues solely related to V1. If you really think this shouldn’t be closed, please comment or create a new issue 🚀.

I think this is still an issue in V2.

I confirm I reproduce with Pydantic 2 (2.9.2), with the plugin mypy.pydantic enabled.


Add documentation for existing best practice rules

This seems to be the only place in the documentation on best practice rules. I suggest to add another page/section that details the existing best practice rules with information on when or how they can/should be suppressed. Basically an update for D365 of the existing documentation for AX 2012: https://docs.microsoft.com/en-us/dynamicsax-2012/developer/best-practices-for-microsoft-dynamics-ax-development
See for example the following discussion that shows that some guidance for BPUpgradeCodeLateBoundCall is needed:
https://www.yammer.com/dynamicsaxfeedbackprograms/threads/99300423933952
https://www.yammer.com/dynamicsaxfeedbackprograms/threads/876654722

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

ID: 15d3cf22-c316-5df9-4203-88a0add25e2d
Version Independent ID: c4844080-547b-90f7-0780-eb843294d6b4
Content: Write best practice rules - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/dev-tools/author-best-practice-rules.md
Service: dynamics-ax-platform
GitHub Login: @pvillads
Microsoft Alias: pvillads

@FH-Inway, thanks for feedback and for providing examples.
@pvillads, please review and update the content accordingly.

Bug 340055 has been logged to track this issue.

There are several efforts ongoing to review BP rules, improve them and potentially remove irrelevant ones. I don't expect we will provide any documentation until that exercise has completed. There are also other efforts like AppChecker which will get more information publicized as they become available.


Add looping functionality - iOS Only

Adds the ability to loop a fixed amount (or indefinitely) any audio file played through the SoundPlayer.

lgtm :+1:


fix: relase clean up code

Description

merge and remove constants and timeouts that are  not necessary as constants.
delete constants pointing to constants

Issue ticket number and link
https://issues.redhat.com/browse/RHTAPREL-660
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

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

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/assigin @redhat-appstudio/release-team

/retest

/lgtm

Can you please update the Description and the name ("Relase") of the PR?

/approve


Extracting grid features with smaller image size

Thanks for sharing the code!
I have a question when extracting the grid features: If I want to extract a fewer number of grid features (using a smaller image size like 448*448 which is mentioned in Table.4 of the paper), can I still use the provided pre-trained model or should I train a new model with smaller image sizes to ensure consistency?

Thanks for your interest in our work. For the numbers reported in Table 4 of the paper, we trained separate models on Visual Genome using different image sizes.

Thanks for the reply
Just another question, will the number of grid features (196 vs 608) influence the used hyper-parameters (e.g., learning rate) to train the model?

We used the same hyper-parameters for all grid features. But it's possible that optimal hyper-parameters may differ for different number of grid features.


Inability to get List Executions from Unscheduled Cycle

request to https://prod-api.zephyr4jiracloud.com/connect/public/rest/api/1.0/executions/search/cycle/{cycleId}?projectId={projectId}&sversionId=-1
Actual result:
code 400
{"errorType":"ERROR","clientMessage":"versionId field value is null or -1 is not valid.","errorCode":131}
What is reason of such behavior?
Even in samples we can see versionId = -1 as an example.

the version id which u specified it invalid it won't be -1 please check your release version id and replace it with proper version id.

the version id which u specified it invalid it won't be -1 please check your release version id and replace it with proper version id.

you replied almost word-for-word what the error already told him. You've done nothing to bring OP closer to a solution.  Please make a more genuine attempt at being helpful
When you look at a return response from zapi, there is clearly a "-1" key for something.  I see it all the time.  If you know what the -1 means please explain it.  If you have no knowledge of what he is describing, please refrain from commenting non-solutions like you did here.

@IZaiarnyi I think the problem is the request argument name. You have "sversionId", looks like it is a typo, try "versionId".


cmd.exe  Not found

Atom 1.401 on Windows 64-bit: I had to change atom.sh in its last five lines to explicitly refer to cmd.exe when running atom from the git bash. Previously this used to work. Note the second line of this listing.
if [ "$(uname -o)" == "Msys" ]; then
  "C:\\WINDOWS\\system32\\cmd.exe" //C "$ATOMCMD" "$@" # Msys thinks /C is a Windows path...
else
  cmd.exe /C "$ATOMCMD" "$@" # Cygwin does not
fi

I am not sure if this is an issue of Atom configuration, or perhaps rather the git bash.

I think at this point that my system got somehow misconfigured: no basic programs are in the path (cmd, powershell). Can that is most likely the source of this error.


New Rule0075: Record Get Procedure Arguments

Discussion: https://github.com/StefanMaron/BusinessCentral.LinterCop/discussions/85
Thank you @rvanbekkum for providing the test cases!
I could use some feedback on this new rule, as my intention is to have set the default severity as a warning for this new rule, where I want to prevent possible false positives.
Some remarks on this PR:
Implicit conversation
procedure GetSalesOrder(DocumentNo: Code[20])
var
    SalesOrder: Record "Sales Header";
begin
    SalesOrder.Get(1, DocumentNo);
end;

Not the best example, but I want to allow this in this rule (and maybe have LC0003 report on this).
For now I have these implicit conversation in place, where I don't have a lot of examples where the parameter type is different then the field type on the table. Could use some input on this if I need to add or remove some conversions here.

Parameter in .Get()
Table field type

Integer
Option

Integer
BigInteger

Integer
Enum

BigInteger
Duration

Code
Text

Text
Code

String(literal)
Text

String(literal)
Code

String(literal) can be a hard coded value directly in code or for example a Label value.
Enums
Currently I expect the provided Enum to be exactly the same as the Enum declaration of the field. Are there exceptions on this I need to take into account?
Setup Table
For a setup table, where I expect the Singleton Pattern, a .Get() call without any values should be sufficiënt. I've now created the check that when a table has one a single primary key of type Code, the rule will handle this as a setup table. Potentially this could raise a false positive on a table with a single primary key of another type, like for example Text?
Length of Code/Text field
Currently the rule will not raise on a Code[20] argument on a Code[10] field, which can possibly create a overflow. I'm looking into handling this with the LC0051 rule.

Thank you very much for doing this. I'm sorry, I wasn't able to bring our changes over in a timely manner, but I'm still trying my best to resolve the internal issues, so I can get back to contributing.
As for this rule, here's a few of my views.
Enum:
I like requiring that it's the same enum. I would even avoid the implicit Integer -> Enum conversion. If someone wants to execute a Get(Int), where PK is an Enum, they can do the Get(Enum.FromInt(Int)). I also don't like the Int -> Option, but okay, there I don't really see a choice if you got the argument passed as an integer parameter...
Setup tables:
Our approach was to simply exit out of the rule if the Get invocation has 0 arguments. Realistically, the chance of accidentally creating Get(), when the table is not a setup table, is pretty low.
Length
We do check that the argument length needs to be shorter than the key field length. I think it's important. I'm not against LC0051 covering it, but the benefit of this rule covering it is that the error message would be more "in line" with what I'd expect.
I couldn't contribute this one directly, but while it's public, you can still have a look at our implementation of this rule here:
https://github.com/Companial/CompanialCop/blob/main/CompanialCopAnalyzer/Design/Rule0028AnalyzeGetInvocations.cs

@tinestaric, Thank you for taking the time to review this rule, very much appreciated!
I somehow didn't realize that this rule was already created in the CompanialCop 😳 where I now created this rule from scratch (sorry).
You're remark on the Enum is valid. I forgot you can easily cast an Int to the proper Enum value with the FromInt(), so I'm going to take out allowing this impliciet conversation directly.
I'll leave the check for the setup table in place for now. If this raises false positives, or any other unwanted side-effects, I'll probably take the same approach as you suggested to skip analyzing the .Get() method when zero arguments are provided.
On the length, I think I can cover more exotic scenario with the logic in the LC0051 rule. For those creative minds out there, like the example below. I don't think this code below is a good idea, but I'm also withhold on raise an warning on this.
procedure MyProcedure()
var
    SalesHeader: Record "Sales Header";
    Prefix: Code[5];
    DocumentNo: Code[15];
begin
    SalesHeader.Get("Sales Document Type"::Order, StrSubstNo(Prefix, DocumentNo));
end;


Add support for links with icons

As used by the new membership components.
But this PR proposes a generic link + icon HTML pattern for any other use case:
<a class="coop-t-link" href="#">
  More about offers

  <!-- Icon with colour fill -->
  <svg class="coop-t-link__icon">
    <path class="coop-u-brand-fill"/>
  </svg>
</a>

As the icon is decorative, we'll also add to the SVG:
<svg aria-hidden="true" focusable="false"></svg>

Sizing is done in em rather than rem so it scales with the link font size.

Looks fine to me 👍


cphate color picker - bubble up events on neuron selection

include flat list of neurons in colorpicker for the cphate
when a single neuron color is changed reflect that in all the sphere/clusters in the cphate

to be estimated

Tasks

transform cphate structure to get distinct list of all neurons
color picker modification to list neurons that are not real instances in the Canvas (have to generalize the component)
change color -> get spheres instances that contain neuron & change their color


Hover state added for active

.nav-list .active > a:hover {
background-color: #000;
}

Just resolved this (will push shortly) by making the hover state the same as the active. Thanks!

Cool. I threw the #000 in there only for attention. Thanks!
/
Van
646-831-9219
(Sent from an Apple device that is mostly awesome, but sometimes inserts its own words into email..leading to awkward misunderstandings)
On Feb 1, 2012, at 8:54 PM, Mark<EMAIL_ADDRESS>wrote:

Just resolved this (will push shortly) by making the hover state the same as the active. Thanks!

Reply to this email directly or view it on GitHub:
https://github.com/twitter/bootstrap/issues/1528#issuecomment-3771256


Absorbable implementations that utilize to_bytes may not match their AbsorbableGadget counterpart

There may be 0 padding in some implementations of native to_bytes, making it differ from the constraints equivalent. It may be worthwhile to consistently take a subset of the bytes (based on the number of bits in the field) to make the outputs consistent between native and constraints to_bytes.

Fixed in a commit to the nonnnative library


Multisig UX improves; all multisg users are delighted with the tool.

closing this issue since it's a bit vague, will track issues/enhancements via the Github project https://github.com/orgs/informalsystems/projects/29/views/11


Binary for Yosemite needed

"You can't  use this version of the application "Bitmarkets" with this version of OS X.
You have OS X 10.10.5. The application requires OS X 10.11 or later."

Thanks for the feedback. Is there a reason you can't do the free upgrade to 10.11?

I'd just prefer to wait until the bugs get fixed
On Thu, Nov 19, 2015 at 5:10 AM, Steve Dekorte<EMAIL_ADDRESS>wrote:

Thanks for the feedback. Is there a reason you can't do the free upgrade
to 10.11?
—
Reply to this email directly or view it on GitHub
https://github.com/Voluntarynet/Bitmarkets/issues/31#issuecomment-157864229
.


Manage signers: Alignment issue.

Check the alignment of Icon.

Verified this issue on keeper app v 1.1.11(295)


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 550

Questions ?
Please refer to the Backport tool documentation


Try to link against an older glibc for releases

The release build for Linux is a reproducible and bootstrappable one using Guix (see https://github.com/wizardsardine/liana/pull/140 and the documentation at contrib/reproducible/).
The glibc this build links against is Guix's gcc-toolchain which ships Glibc 2.33. Unfortunately, it's quite recent (February 2021) and some operating systems still only provide older glibc. See https://sourceware.org/glibc/wiki/Release for a table of glibc version per distribution version. I'd like to at least get Ubuntu Focal (Glibc 2.31) and Debian 10 (Glibc 2.28).
Unfortunately building against an older Glibc within the Guix container is non-trivial (to me). Another approach could be to link against musl (see https://github.com/wizardsardine/liana/issues/255).
The quickest solution for anyone running into an issue of the type:
./liana-gui: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./liana-gui)

Is to compile the project from source. There are instruction at doc/BUILD.md on how to do this reasonably. But you can also just use the simple (not really decent) way of installing the Rust toolchain from their website and build Liana like so (example for v1):
git clone https://github.com/wizardsardine/liana
cd liana/
git checkout v1.0
cd gui/
cargo run

Removing from the 1.0 project. I've had another look at it and it is really non-trivial (to me) to build against an older glibc within the Guix container.

As commented in this Merged PR, I will try to get hands on it by next week. It doesn't see that trivial to fix.
I you fix it I will try to keep track on this PR.
Thanks!

I've added details about this issue to the OP. Since it's been hit (as expected..) by a couple users already i've added troubleshooting instructions (basically you have to build from source).

I will try to get hands on it by next week

Good to hear. A PR for this would be very welcome. But note i do not want to compromise on reproducible and bootstrappable builds, so it has to happen within the Guix toolchain.

Hi, actually building from source doesn't work either, I have Ubuntu 20.04 with glib 2.31 and I can build from source, but somehow the gui crash at startup with the following error:
$cargo run --release
/.../
     Running `target/release/liana-gui`
  2023-06-08T14:46:38.541243Z  INFO winit::platform_impl::platform::x11::window:147: Guessed window scale factor: 1.75

2023-06-08T14:46:38.541277Z  INFO winit::platform_impl::platform::x11::window: Guessed window scale factor: 1.75
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
liana-gui: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)

I could reproduce the issue on another machine that runs same system.
It seems that the problem appears when I first build lianad and liana-cli, then build the gui, and that if my target dir is clean it works fine.
Best I could track so far is that it was an issue with winit that was supposedly fixed by https://github.com/rust-windowing/winit/pull/554, but was reported again later by other project. Not sure what to do about it.

Hi, actually building from source doesn't always work either, I have Ubuntu 20.04 with glib 2.31 and I can build from source, but somehow the gui crash at startup with the following error:
$cargo run --release
/.../
     Running `target/release/liana-gui`
  2023-06-08T14:46:38.541243Z  INFO winit::platform_impl::platform::x11::window:147: Guessed window scale factor: 1.75

2023-06-08T14:46:38.541277Z  INFO winit::platform_impl::platform::x11::window: Guessed window scale factor: 1.75
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
liana-gui: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)

I could reproduce the issue on another machine that runs the same system.
It seems that the problem appears when I first build lianad and liana-cli, then build the gui. If I already built the daemon I need to cargo clean it first before building the gui.
Best I could track so far is that it was an issue with winit that was supposedly fixed by rust-windowing/winit#554, but was reported again later by other projects. Not sure what to do about it. [[EDIT1]] minor edits for clarity

look like #523

Discussed this with someone much more knowledgeable about Guix and it is indeed non-trivial, for what it's worth.

any way to link against a static glibc?

When I helped Rana to have binaries I tried also on that time to build Liana. CLI worked fine, but not GUI. For some reason it needed libc for a rust package as far I remember...
I had on mind, that I wrote this before when I tried it and seems I completely forgot.
Please, take a look what I did just in case you want to try (Is not using Guix as needed here) but is an approach to create the binaries.
https://github.com/grunch/rana/pull/44#issuecomment-1659670984
https://github.com/grunch/rana/pull/44#issuecomment-1662681163
Hope this help some how to push this a bit forward. Regards


'FluidFlowSettings" object has no attribute 'name'

Describe the bug
When i try to export this fluid simulation  ing glb file format , i get a python error.
To Reproduce
Steps to reproduce the behavior:
Download the file and play the animation
Expected behavior
To export into a glb file without a problem stating FluidFlowSettings object has no attribute 'name'
Screenshots

.blend file/ .gltf (mandatory)
LASTTTT - Copy.zip
Version

OS: [windows]
Blender Version [4.2.1]

Description:
i created a fluid flow water like simulation and baked it to keyframes without addding a name anywherre.Now finally when i got it working it starting to bug saying i can't export it.

Confirmed.
On the Sphere Object, the "use Flow" is animated, but this can not be exported in glTF.
There is a bug in the way we are retrieving the channel data_path.
Workaround to export your data:
Remove the animation on the boolean field:

Thank you very much!


SIL.rst: Add documentation for async function representation.

Unlike our existing coroutines, async functions run independently within an async coroutine context, and don't
directly yield values back and forth. They therefore mostly behave like normal functions with only an @async annotation
to indicate the presence of async suspend points. The withUnsafeContinuation primitive requires some instructions
to represent the operation that prepares the continuation to be resumed, which will be represented by
begin_async_continuation...await_async_continuation regions.

Thanks for writing these docs. At the SIL level, explaining async coroutines in terms of @async functions confuses me. Calling an @async function will require generating a coroutine, but the SIL design actually hides that. (I think most people reading this will initially assume that these instructions are used to create a coroutine for calling @async functions, which is backward).
Instead, here we're talking about any function that may suspend execution in some way that does not involve calling an @async function. It may be worth pointing out that calling an @async function implicitly generates a coroutine in a way that's hidden from SIL, while these instructions are for other kinds of suspension points that aren't naturally handled by an @async function call, namely withUnsafeContinuation. As a footnote, we can say that they are currently limited to @async function bodies for implementation reasons that are totally unrelated to SIL design.
In SIL, there's no reason that a synchronous function can't suspend. I think that will be important to support at the language-level when we can statically determine the executor. There will be some type annotation on such functions and additional type restrictions on its interface similar to the restrictions on async coroutines. So, if we needed some SIL function attribute to guard the use of these instructions, I would call it @maysuspend instead, but that doesn't seem useful.

Regarding the implications for SIL passes, a lot seems to be hidden in this statement:
It is possible for a continuation to be resumed before ``await_async_continuation``.
 In this case, the resume operation returns immediately, and
 ``await_async_continuation`` immediately transfers control to its ``resume``
 or ``error`` successor block, with the resume or error value that the
 continuation was resumed with.

We won't be able to allow side-effect free code motion across the await, which is something we've never had to content with. Do we need to add a constraint that values defined within the suspend region can't be used outside the suspend region?
We also, obviously can't reason about side effects across the await. The basically means that the await appears to write to the entire memory space, meaning we can't optimize anything across suspends.

Thanks for writing these docs. At the SIL level, explaining async coroutines in terms of @async functions confuses me. Calling an @async function will require generating a coroutine, but the SIL design actually hides that. (I think most people reading this will initially assume that these instructions are used to create a coroutine for calling @async functions, which is backward).

Maybe this is a matter of different perspective, whether you consider the "coroutine" to be the notional execution context that persists across async calls, or to be the mechanical LLVM coroutine lowering goop. I guess I'm speaking more in terms of the former than the latter—as I see it, the LLVM coroutine splitting is an implementation detail, whereas the Task that async functions run in is part of the programming model. An async function doesn't represent a whole Task/coroutine unto itself, but a piece of work that can run on that Task.

Instead, here we're talking about any function that may suspend execution in some way that does not involve calling an @async function. It may be worth pointing out that calling an @async function implicitly generates a coroutine in a way that's hidden from SIL, while these instructions are for other kinds of suspension points that aren't naturally handled by an @async function call, namely withUnsafeContinuation. As a footnote, we can say that they are currently limited to @async function bodies for implementation reasons that are totally unrelated to SIL design.

I guess it isn't clear, but the intent of these instructions was to give something for withUnsafeContinuation specifically to lower to, as John described in this forum post. I can add a more explicit example of how withUnsafeContinuation lowers to these SIL instructions. The hope is that withUnsafeContinuation's operation block can be inlined into the caller in most situations.

In SIL, there's no reason that a synchronous function can't suspend. I think that will be important to support at the language-level when we can statically determine the executor.

Could you give me an example of what you have in mind. As I understand it, anything associated with an executor that might suspend ought to be async in the language design. What differences would there be between @async and @maysuspend?

Regarding the implications for SIL passes, a lot seems to be hidden in this statement:

It is possible for a continuation to be resumed before await_async_continuation.
In this case, the resume operation returns immediately, and
await_async_continuation immediately transfers control to its resume
or error successor block, with the resume or error value that the
continuation was resumed with.
We won't be able to allow side-effect free code motion across the await, which is something we've never had to content with. Do we need to add a constraint that values defined within the suspend region can't be used outside the suspend region?

await_async_continuation shouldn't be any more opaque to optimization than a try_apply. Code outside of the task can't manipulate the function's local state, but can have arbitrary global side effects, like a synchronous call.
Reading this back, I see it sounds like it's implying that resuming a continuation before await_async_continuation immediately transfers control to the await_async_continuation successor, which isn't what I meant to say—the resume operation returns immediately to its caller after priming the await, and then later, when the await_async_continuation executes, it immediately goes to the resume/error successor using the value it was primed with. I'll reword it to clarify.
Thanks for taking a look and giving me your feedback, Andy!

I revised the text a bit; this time I stop trying to discuss async functions as a kind of coroutine, and clarify the semantics of await_async_continuation when the continuation is resumed before it's awaited.

Thanks for writing these docs. At the SIL level, explaining async coroutines in terms of @async functions confuses me. Calling an @async function will require generating a coroutine, but the SIL design actually hides that. (I think most people reading this will initially assume that these instructions are used to create a coroutine for calling @async functions, which is backward).

Maybe this is a matter of different perspective, whether you consider the "coroutine" to be the notional execution context that persists across async calls, or to be the mechanical LLVM coroutine lowering goop. I guess I'm speaking more in terms of the former than the latter—as I see it, the LLVM coroutine splitting is an implementation detail, whereas the Task that async functions run in is part of the programming model. An async function doesn't represent a whole Task/coroutine unto itself, but a piece of work that can run on that Task.

It's a natural assumption when reading this introduction is that the new async_continuation instructions are necessary for implementaing @async functions, which is quite misleading. We can say that the instructions only occur in @async functions, but from the point-of-view of SIL, that's an arbitrary restriction.

Instead, here we're talking about any function that may suspend execution in some way that does not involve calling an @async function. It may be worth pointing out that calling an @async function implicitly generates a coroutine in a way that's hidden from SIL, while these instructions are for other kinds of suspension points that aren't naturally handled by an @async function call, namely withUnsafeContinuation. As a footnote, we can say that they are currently limited to @async function bodies for implementation reasons that are totally unrelated to SIL design.

I guess it isn't clear, but the intent of these instructions was to give something for withUnsafeContinuation specifically to lower to, as John described in this forum post. I can add a more explicit example of how withUnsafeContinuation lowers to these SIL instructions. The hope is that withUnsafeContinuation's operation block can be inlined into the caller in most situations.

That's totally clear to me, I just don't think it was clear in the docs.

In SIL, there's no reason that a synchronous function can't suspend. I think that will be important to support at the language-level when we can statically determine the executor.

Could you give me an example of what you have in mind? As I understand it, anything associated with an executor that might suspend ought to be async in the language design. What differences would there be between @async and @maysuspend?

What about an @asyncHandler function?
Or, purely hypothetical:
// Must not return anything...
func spawnTask() -> () {
  Builtin.beginAsyncTask(on: globalExecutor)
  // Synchronous return after setting up a continuation
  let request = await asyncRequest()
  // Asynchronous continuation
  _ = request
}

Regarding the implications for SIL passes, a lot seems to be hidden in this statement:

It is possible for a continuation to be resumed before await_async_continuation.
In this case, the resume operation returns immediately, and
await_async_continuation immediately transfers control to its resume
or error successor block, with the resume or error value that the
continuation was resumed with.
We won't be able to allow side-effect free code motion across the await, which is something we've never had to content with. Do we need to add a constraint that values defined within the suspend region can't be used outside the suspend region?

await_async_continuation shouldn't be any more opaque to optimization than a try_apply. Code outside of the task can't manipulate the function's local state, but can have arbitrary global side effects, like a synchronous call.
Reading this back, I see it sounds like it's implying that resuming a continuation before await_async_continuation immediately transfers control to the await_async_continuation successor, which isn't what I meant to say—the resume operation returns immediately to its caller after priming the await, and then later, when the await_async_continuation executes, it immediately goes to the resume/error successor using the value it was primed with. I'll reword it to clarify.

Oh, phew, I completely misread that statement. What I really need to know is  that the region of code inside begin/await_async_continuation must run synchronously with the continuation's resume block. I'd need to think hard about how that's implemented. My mental model is that the body of the continuation is actually the resume block. So, once that continuation is added to a dispatch queue, there's nothing preventing it from running before execution within the begin/await region reaches the await. I must not be clear on how it's implemented in IRGen yet.

I revised the text a bit; this time I stop trying to discuss async functions as a kind of coroutine, and clarify the semantics of await_async_continuation when the continuation is resumed before it's awaited.

I like the new text, thanks!
I wonder if begin_async_continuation is misleading as an instruction name — like Andy says, the region described by the instructions isn't actually the continuation, it's an operation that works with the continuation.  Maybe get_async_continuation for the opener?  The risk is that someone reading that might not understand that it's a region, but I think that's okay.
I really like await_async_continuation for the closing instruction, it captures the sense of what's happening from the function's perspective perfectly.

get_async_continuation seems reasonable. Hopefully the verifier can enforce the constraints well enough to help people understand what's going on if it isn't evident from the instruction names themselves

@swift-ci Please smoke test

Alright, I revised begin to get_async_continuation, and clarified the ownership of the bbargs. Any other concerns?


Analysis Server doesn't report usages from Dart code injected in HTML

Related to #24403.
com.google.dart.server.AnalysisServerListenerAdapter#computedSearchResults doesn't include usages from Dart code in HTML files.

It appears that we are not indexing HTML


Add a new change that can replace a note

Description
From https://github.com/apple/swift-syntax/pull/2286#discussion_r1359927684

Hmm, it’s not easily possible in the current design where we assume all nodes for the Fix-It to already be present in the syntax tree so that we just need to flip the token presence.

I would say that it’s good enough for now but adding support for these kinds of Fix-Its might be useful in general. What we need for that is, IMO, a new Fixit.Change that takes a syntax node, a key path within that node and a replacement node, i.e. something like case replace<NodeType, ChildType>(node: NodeType, path: KeyPath<NodeType, ChildType>, child: ChildType) – and yes I see the irony of declaring a generic enum case here, you would need to come up with some design that actually compiles, I haven’t thought about it too much yet.

I think this kind of Fix-It change might also be useful for macro authors. IIRC it came up once or twice but was never super important.

Tracked in Apple’s issue tracker as rdar://117082263

Close in favour of https://github.com/apple/swift-syntax/issues/2205


Add getters to AnthropicCreateMessageRequest and change scope of attributes

This should have been done in #834

Thank you @langchain4j ! Do you know when you are planning another release that would include this?

Hi @edeandrea, sorry for the delay, I plan to do one on 15th April.

No worries at all I'm sure you're busy! Thank you for the update!


chore(bindings/nodejs): Append license header automatically

After upgrading @napi-rs/cli, patches can be removed.
cc @Xuanwo for the script.

😳, when will we add the header if we have those patch removed?

😳, when will we add the header if we have those patch removed?

Actually, when you fixed the CI issue some hours ago and bumped @napi-rs/cli, the patch was already invalidated.

got it.

I'm looking forward to this https://github.com/apache/incubator-opendal/pull/1711#issuecomment-1477403208 🤣
Just do it when you have free time.


[Bug]: ob433 query select array_contains([1,2,3], 2), download result set, report null pointer

ODC version
ODC432
OB version
oceanbase433
What happened?

What did you expect to happen?
。
How can we reproduce it (as minimally and precisely as possible)?
select array_contains([1,2,3], 2);

export result set
Anything else we need to know?
No response

sqlparser does not support this type of syntax

test pass


OmniSharp server crashes on startup

From @ignusin on June 12, 2018 16:54
Hello OmniSharp/VSCode team.
IntelliSense doesn't work in my AspNetCore 2.0 project.
OmniSharp fails with following exception copied from OmniSharp Log in VSCode.
Could you please take a look?

Extension Name: csharp
Extension Version: 1.15.2
OS Version: Windows_NT x64 10.0.17134
VSCode version: 1.24.0

System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
at Microsoft.VisualStudio.Setup.Configuration.ISetupInstance2.GetState()
at OmniSharp.MSBuild.Discovery.Providers.VisualStudioInstanceProvider.GetInstances()
at OmniSharp.MSBuild.Discovery.MSBuildLocator.GetInstances()
at OmniSharp.CompositionHostBuilder.RegisterMSBuildInstance(IMSBuildLocator msbuildLocator, ILogger logger)
at OmniSharp.CompositionHostBuilder.Build()
at OmniSharp.Stdio.Host..ctor(TextReader input, ISharedTextWriter writer, IOmniSharpEnvironment environment, IConfiguration configuration, IServiceProvider serviceProvider, CompositionHostBuilder compositionHostBuilder, ILoggerFactory loggerFactory, CancellationTokenSource cancellationTokenSource)
at OmniSharp.Stdio.Driver.Program.<>c__DisplayClass0_1.b__1()
at Microsoft.Extensions.CommandLineUtils.CommandLineApplication.Execute(String[] args)
at OmniSharp.HostHelpers.Start(Func`1 action)
Copied from original issue: OmniSharp/omnisharp-vscode#2379

Sorry guys, this is 100% my local issue.
I upgraded Visual Studio 2017 to 15.7.3 and everything started to work like a charm!

Thanks for letting us know. Glad to hear it's solved!


Modify ORM to Mongoose

Change the backend ORM from Mongoskin to Mongoose
Also create a collection for every queue name to increase performance

Don't need to overhead mongoskin works fine


Update based on issue #75633

Updated code snippet, the answer to the issue  is that should point to the External URL and path to the API, as mentioned in included link https://docs.microsoft.com/en-us/azure/active-directory/app-proxy/application-proxy-configure-native-client-application
In the code snippet  is replaced with todoListBaseAddress + "/api/values/4"
Added more specific instructions.
Updated links.

@timpeteren : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Forgot to mention that this linked to item # 1611113
#ATCP

@timpeteren : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

@timpeteren - thank you for the work in this area and the PR. I have been working with the product team to get this merged. Would you please email me? My email is the same as my github and at microsoft.com.

@timpeteren : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@timpeteren : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@timpeteren : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@kenwith and @timpeteren - any update on this?

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@kenwith where are we with this one?

@BarbaraSelden this will likely be merged now. There has been a (off and on) conversation going on between Ken, Arpad Gulyas and myself, but I believe we have reached our destination now 🤞
@kenwith some more details in a separate email on these final changes.
Thanks everyone!

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@kenwith I added two commits to format the two latter sections as numbered procedure steps. I'll merge now. Thanks, all.


table.index() not adding SPATIAL index for geometry column

Environment
Knex version: 0.14.4
Database + version: MariaDB 10.2
Issue
At creating geospatial columns, when creating the indexes, it does not create the SPATIAL index, plus getting Error: BLOB/TEXT column 'locations' used in key specification without a key length, and as far as I know, you can't set MULTIPOINT columns with a length
table.specificType('locations', 'MULTIPOINT').notNullable()
table.index(['locations'], null, ['SPATIAL'])

table.specificType('location', 'POINT').notNullable()
table.index(['location'], null, 'SPATIAL')

Error:
[ { sql: 'create table `merchants` (`id` int unsigned not null auto_increment primary key, `category_id` int unsigned not null, `user_id` int unsigned not null, `locations` MULTIPOINT not null, `created_at` datetime, `updated_at` datetime)',
    bindings: [] },
  { sql: 'alter table `merchants` add constraint `merchants_category_id_foreign` foreign key (`category_id`) references `categories` (`id`) on delete CASCADE',
    bindings: [] },
  { sql: 'alter table `merchants` add constraint `merchants_user_id_foreign` foreign key (`user_id`) references `users` (`id`) on delete CASCADE',
    bindings: [] },
  { sql: 'alter table `merchants` add index `merchants_locations_index`(`locations`)',
    bindings: [] } ]
[ { sql: 'drop table if exists `adonis_schema_lock`',
    bindings: [] } ]
{ Error: BLOB/TEXT column 'locations' used in key specification without a key length ... }
]

Which would be expected queries in this case? I suppose this one is not what you were expecting:
alter table `merchants` add index `merchants_locations_index`(`locations`)

Uh, forgot it, my bad:
ALTER TABLE merchants ADD SPATIAL INDEX merchants_locations_index (locations) (probably with)

Looks like a bug then 👍 Need to check out if that is broken in all dialects.

I was giving it a try, and found out this bug has nothing to do with SPATIAL indexes, It's actually a limitation of the knex api.
As you can see here https://github.com/tgriesser/knex/issues/203#issuecomment-214650706 (another issue that needs attention for this)
table.index(['location'], null, 'ANYTHING') is not using the index type in the query.

Any updates on this?

@Frondor I'm sure you would have known if you have done anything about this :) I highly doubt that anyone else is going to fix it.


[Bug] Georeplication from not partitioned topic cluster to enforced partition cluster

Search before asking

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

Version
2.10.5
Minimal reproduce step
On a local cluster, create a non-partitioned topic on a cluster with systems topics enabled.
Then, on the remote cluster force all topics to be partitioned.
Then enable georeplication from local to remote clusters.
What did you expect to see?
Correct replication.
What did you see instead?
Weird topics were created on the local cluster such as tenant/namespace/__change_events-partition-0.
Anything else?
I also suspect it from duplicating all existing topics to partitioned ones if they weren't.
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

local cluster create a non-partitioned topic , "topicA";
remote cluster   set config  allowAutoTopicCreation=true   allowAutoTopicCreationType=partitioned;
when local cluster replicate "topicA" to remote cluster, topic "topicA-partition-0" will be created in remote cluster , and then remote cluster replicate  the topic "topicA-partition-0",finally the local cluster will create the topic ,named "topicA-partition-0"
when  new a GeoPersistentReplicator , it will create a producer for the topic to the remote cluster.
    public GeoPersistentReplicator(PersistentTopic topic, ManagedCursor cursor, String localCluster,                                    String remoteCluster, BrokerService brokerService,                                    PulsarClientImpl replicationClient)             throws PulsarServerException {         super(localCluster, topic, cursor, remoteCluster, topic.getName(), brokerService, replicationClient);     }
remoteTopicName is topic.getName()
this.producerBuilder = replicationClient.newProducer(Schema.AUTO_PRODUCE_BYTES()) //                 .topic(remoteTopicName)                 .messageRoutingMode(MessageRoutingMode.SinglePartition)                 .enableBatching(false)                 .sendTimeout(0, TimeUnit.SECONDS) //                 .maxPendingMessages(producerQueueSize) //                 .producerName(getProducerName());
Only the topic name is set when the producer is created, and whether it is a partitioned or non-partitioned topic can only be created based on the default configuration of the remote cluster
Maybe we can create the topic to remote cluster  first before creating the replicationProducer to solve it


npm Vue (node module) does not work in the standardized way

Version
2.5.16
Reproduction link
https://jsfiddle.net/chrisvfritz/50wL7mdz/
Steps to reproduce

{{ message }}

  const Vue = require("vue");

  const app = new Vue({
    el: "#app",
    data: {
      message: "Hello Vue!"
    }
  });

What is expected?
The native npm  or node module should work in a Browser-side JavaScript code such as in Electron environment.
What is actually happening?
..myProject/node_modules/vue/dist/vue.runtime.common.js:589 [Vue warn]:
You are using the runtime-only build of Vue where the template compiler is not available. Either pre-compile the templates into render functions, or use the compiler-included build.
(found in )
warn @ /home/ken/p/markdown-editor/node_modules/vue/dist/vue.runtime.common.js:589
and the "Hello Vue!" does not work.

The reason of this issue is obviously,  npm module  package.json is as follows:
//...
 "main": "dist/vue.runtime.common.js",
//...

The workaround is to change the client-js code to:
  const Vue = require("./node_modules/vue/dist/vue.js");
`
  const app = new Vue({
    el: "#app",
    data: {
      message: "Hello Vue!"
    }
  });

I unserstand this is due to
https://vuejs.org/v2/guide/installation.html#Explanation-of-Different-Builds

CommonJS: CommonJS builds are intended for use with older bundlers like browserify or webpack 1. The default file for these bundlers (pkg.main) is the Runtime only CommonJS build (vue.runtime.common.js).

However, I think the standarized behavior of npm package is to run without browserify or webpack, and it's strange that
"dist/vue.runtime.common.js" is the default module of the npm package.
It's should be
"dist/vue.js".

Yes, if you want the template compilation, you need to use that version. If you want the template compiler for node, you have a dedicated package for it.
In any case, this would be a breaking change

@posva How can one require() or import Vue?
In my client-side script (which is compiled with Babel), I'll have something like this:
import Vue from 'vue';

This works on the surface, but with no way to specify a build, the "runtime-only" build is used, as @kenokabe said.  This (at least to me) doesn't make much sense.  Usually the module exported is a full build.  If someone wanted a scaled back build, they can get it out of dist/.
Is there any useful workaround?  Requiring out of node_modules/ is not appropriate in my opinion... that directory can change.


Query About Low-grade Instance Suppressive Function

Hey,
Thanks for the repo. In section 4.3 of the paper, you introduced LIS function. Can you point me out the location where this function is implemented in the code? I am basically curious about how to get the value of T, k and W in the logistic function.

Hi @ASMIftekhar
We use different NIS parameters for V-COCO and HICO dataset.
For HICO, it's in HICO-DET_benchmark/Generate_HICO_detection_nis.py (line38-40 & 72)
For V-COCO, it's in tools/Vcoco_lis_nis.py (line 304)

Thanks a lot.


Fazle/vote timeline chart

PR-Codex overview
This PR adds new SVG icons, updates components with proposalVotes, and refactors chart data handling.
Detailed summary

Added chevronSelectorVertical and check SVG icons
Updated ProposalDescription components with proposalVotes
Refactored chart data handling in VotingTimelineChart

The following files were skipped due to too many changes: src/components/Proposals/ProposalPage/VotingTimelineChart/VotingTimelineChart.tsx, src/components/Proposals/ProposalPage/OPProposalPage/ProposalVotesSummaryDetails/ProposalVotesSummaryDetails.tsx, yarn.lock

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Please investigate why the chart does not show up on proposals for the ENS tenant.
To test this locally, just set the .env NEXT_PUBLIC_AGORA_INSTANCE_NAME=ens


feat: better database errors

In light of problems I faced when error handling a back-end agnostic code, I've came up with an interface that lets the user figure out what kind of error the database returned, which fixes #2102.
The new DatabaseError::kind(&self) function tries to match the error code with a known kind, taking into account the back-end specific ways it might be returned. Four error kinds are supported for now: unique, foreign key, not null, and check violations.
SQLite and Postgres are pretty straight forward, MySQL has multiple codes for each kind of violation, but MSSQL has a funny way of reporting checks and foreign key violations, it uses the same error code and differentiates the two in the message.
I've performed tests and all four kinds are supported for all back-ends currently supported, including check and foreign key for MSSQL.

This looks brilliant to me.
Any idea on if this will be merged soon @abonander ?

@saiintbrisson current development is on the 0.7-dev branch which just had some major refactors merged. Do you mind rebasing?

@abonander seems like we are good to go. I've deleted the MSSQL error implementation, but I'm wondering where I should put it, will the "pro" crate be available soon?

You can just delete the MSSQL stuff, we'll be redoing that from scratch anyway.
x.py I honestly never touch as I don't understand how to use it :rofl:, it was written by @mehcode ages ago. I prefer to run tests directly in CLion so I can attach a debugger if I want to, and let Github Actions deal with running the full suite.

Right! Dropped the MSSQL commit @abonander.
x.py is indeed confusing, there's probably a better way to write a test suite. And as to the remaining MSSQL tests, should I follow up with a PR deleting them?
By the way, the PR is ready to be reviewed!

I'll delete them, they're just dead code.
x.py is supposed to be a runner for common build/test commands, there's a similar script in rust-lang/rust that inspired it. If people are actually using it I'm fine keeping it but I don't see much value in it myself.

@saiintbrisson sadly Transaction cannot implement Executor anymore due to coherence issues: https://github.com/launchbadge/sqlx/actions/runs/4088645789/jobs/7050682422#step:7:665
You should be able to just insert a dereference, e.g. .execute(&mut *tx)

@abonander Makes sense, I was expecting this to happen, and it did with sqlite, but x.py really does not work correctly hahaha

@abonander MySQL has this weird functionality where CHECK constraints didn't exist before version 8.0, and the 5.7 server just "ignored it", we can't run tests for this version or any MariaDB. I'm not sure how to proceed, as the test isn't aware of the server version it's connecting to, any ideas?
SQLite also requires a PRAGMA foreign_keys = ON on every connection that wants to ensure foreign key consistency.

I believe we do send PRAGMA foreign_keys = ON by default for SQLite, cause having it off is kinda pointless for new applications.
As for MySQL, we've used #[cfg] flags to only enable tests when running against newer database versions in CI, you can duplicate what we did for Postgres to MySQL:

https://github.com/launchbadge/sqlx/blob/0.7-dev/tests/postgres/types.rs#L552
https://github.com/launchbadge/sqlx/blob/0.7-dev/.github/workflows/sqlx.yml#L233

It looks like 5.7 is slowly getting EOL'd as it's not supported on newer operating systems: https://www.mysql.com/support/supportedplatforms/database.html
I'll be glad when we can drop it entirely cause it's kinda been a pain.

@abonander I've re-ran all the tests locally and they seem to be working fine


[LMS-251] Remove StartDate and EndDate from Section Association

Wow, there was quite a bit to this.


Docs Update BE http documents

Proposed changes
Issue Number: close #15658
Problem summary
Update BE http documents
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

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...

run buildall

run p0


Cannot push/pull on insomnia git sync

Expected Behavior
Creates a snapshot and pull t to insomnia sync
Actual Behavior
I created the snapshot.
And click on create and push:

Reproduction Steps
No response
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
Version: Insomnia 2022.7.0 Build date: 15/12/2022 OS: Linux x64 5.15.0-56-generic Electron: 22.0.0 Node: 16.17.1 V8: <IP_ADDRESS>-electron.0 Architecture: x64
What operating system are you using?
Other Linux
Operating System Version
mint
Installation method
download
Last Known Working Insomnia version
No response

Hi @gdoumenc any chance you can provide some more details of which git provider/server are you using (and if it is self-hosted)?
Also are you still able to reproduce this one past 2022.7.2?

Hi @gdoumenc any chance you can provide some more details of which git provider/server are you using (and if it is self-hosted)?
Also are you still able to reproduce this one past 2022.7.2?

Always git push failed to gitlab Version: Insomnia 2022.7.5.

Same for me. When I click Git commit, insomnia shows this message:

The issue happened for half of a year already. Just checked with latest version (Insomnia 2023.2.2), running on Windows 10 64 bit and it still crashes.
I using GitHub as remote repository, I already logged in successfully:


[binance] Add tickers

Added getting of tickers (2 requests needed: bids/size + price)
Added mapping symbol -> currency pair (got from exchange info)
Moved exchangeInfo-methods to MarketDataService
Updated integration tests
Added requests for idea http client
Simplified dto's

Hi.
Two requests for tickers:
api/v3/ticker/price - Latest price for a symbol or symbols.
api/v3/ticker/bookTicker - Best price/qty on the order book for a symbol or symbols.
But there is no volume and quoteVolume and ticker time is only last moment.
If I understand correctly, we should get a 24 hour ticker.
this api is fit:
https://binance-docs.github.io/apidocs/spot/en/#24hr-ticker-price-change-statistics

Hi. Two requests for tickers: api/v3/ticker/price - Latest price for a symbol or symbols. api/v3/ticker/bookTicker - Best price/qty on the order book for a symbol or symbols. But there is no volume and quoteVolume and ticker time is only last moment.
If I understand correctly, we should get a 24 hour ticker. this api is fit: https://binance-docs.github.io/apidocs/spot/en/#24hr-ticker-price-change-statistics

Hi. Yep, good idea :+1:
will change the implementation

done
#4868

@timmolter
I propose to review and merge the https://github.com/knowm/XChange/pull/4868 first. Then I can integrate the changes to my branch

merged 4868

merged 4868

done, feel free to review

@timmolter ping


Using all vCPU available on the only server NO cluster

Hello,
I have a server with 4 vCPU and some 7.5 GB RAM i wonder how can i make use of all virtual CPU on my server so the meteor runs faster with no lags.
is there a way to add ssl in the mup config ?
Thanks you

Use the meteorhacks:cluster package.
Although beware that people (including me) have had issues with cluster multicore support.


feat(linter): eslint/no-unexpected-multiline

Implement ESLint's no-unexpected-multiline rule.
To get started, run
just new-rule no-unexpected-multiline

I just started looking at this repository and I tried to start with this issue, then I did some research and I realized that it is hard for me to implement this rule in a simple way.
Imitating eslint's implementation, I need to find the corresponding Statement from AstNode in Program, and since AstNode doesn't have an index stored link to the Statement, I do this step by doing a binary search .
Then I can find the previous Statement of the current Statement to determine if they are on the same line, but i can't find the line number of the Statement, so I can only locate the line number by traversing the line breaks in the source code.
Both of these binary search and traversing the source code are slower operations, and if the performance drop is unacceptable, to implement this rule I may have to store more information such as the line number, AstNode to Statement Index.

This is a style rule which can be fixed by a formatter, let's remove this from our list.


Maintenance Todos

The original repo by dawsonjon has not been updated in few years.
After forking,  these is the things I would to do in the next few days.

[x]  Upgrade to Python 3
[ ]  publish package to pypi (under different name)
[ ]  adapter to axi stream for input output
[x]  test examples with Python 3

Build wheels using GitHub Action:  3fc5d791173a7f38b96b58b2cc1590c36b63b0cd

publish to pypi in the same GitHub actions workflow,  https://pypi.org/project/Chips-python/
Tested with tag v2.2.2
b5f467e7f088f86a4e2e026b8640cc7b4ceda0ac


sync_hash fails if encrypted on disk = true, but wallet not encrypted (is_encrypted shows true in wallet status also)

There are some scenarios where the encrypted on disk value is incorrect(one is: if sync apply with a blank password was used on an encrypted wallet) and in this case, sync hash fails when run. But after the app runs sync apply to get a new hash, then sync hash works again.
Error: 'NoneType' object has no attribute 'encode'
It should not fail and should try to run the hash knowing that the wallet is not encrypted and the encrypted on disk value is
incorrect.
This prevents startup on Android and causes issues on desktop/lbry.tv as well.
is_encrypted in wallet status should also be false.  encrypted on disk setting should be reset in wallet.

bump


Too many undefined variable on compiled CSS

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
I found too many undefined problem on compiled css,
There are too many variable on compiled css, that not have value:
check the lines of compiled css:
2809
3522
3636
3810
4184
4189
4190
4191
4198
4499
5207
5273
5287
5565
6110
all of this line, has variable without value.
Reduced test cases
I remove all undefined variables, but its need to remove property that use this variables.
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
No response
What version of Bootstrap are you using?
5.2

Duplicate of #36595

I found too many variables that not used. I think have to change the compiler to create a correct css compiled files.

The CSS compiled file is correct. Empty CSS variables can exist, it is valid.
However, we're going to try remove them when unused in order to lighten the file a little bit.


Revise KIC plugin and auth guides for GWAPI

Summary
Continuing the addition of Gateway API content and reusable includes for common tasks from https://github.com/Kong/docs.konghq.com/pull/4766 onward, into the plugin and authentication guides, and then some more popular guides.
Add a blurb about KongIngress support for HTTPRoute.
Updates all the KIC guide Kong versions in responses to 3.1.1, since edits over time have made these get out of sync within guides.
Reason
Part of https://github.com/Kong/kubernetes-ingress-controller/issues/2878 and https://github.com/Kong/kubernetes-ingress-controller/issues/2966
Testing
Full testing still TBD. Some initial spot testing of command correctness.

When this is ready please feel free to remove the draft status so we can approve it.

@Guaris this depends on https://github.com/Kong/docs.konghq.com/pull/4766; it needs to be merged, and this needs to be rebased, before this can proceed.
If it works better for ya'll I could make this the only PR, containing the commits and changes from both. I'd kept them separate since they're both fairly large on their own already.

Still needs an E2E command validation pass from me, but going ahead and marking ready for review of the copy and templating.

Vale is unhappy for reasons I cannot entirely determine. It's apparently detecting terminology issues on a bunch of content I didn't edit. Didn't find any app/_src/ku in the log, so it looks like the content here is fine :shrug:


Fix CI

I notice CI has been red on master for some time; this PR should fix that. Marking it as a draft until CI is green.

LGTM.

Well, @raxod502 the CI for auto assigning the author fails. I think this GitHub action is bugged and we need to switch to another one.

@wizard-28 I copied the GitHub Actions configuration from this repo to https://github.com/raxod502/assign-pr-author-as-assignee-test and created an example pull request to test the functionality. In my test, the assignment worked correctly, so I suspect the problem may be on the end of the repository configuration, which I don't have access to---I may need your help to correct the problem.

Does the permissions error only occur when receiving a pull request from a contributor who does not have push access to the repository? I will test.

Yes, I was able to reproduce the error on my repository: https://github.com/raxod502/assign-pr-author-as-assignee-test/runs/5731145848
I will investigate when I have time. To help me understand how best to fix the problem, would you mind providing some more context about how you use pull request assignment in this repository? I.e., what function does automatically self-assigning submitted PRs fulfill?

To help me understand how best to fix the problem, would you mind providing some more context about how you use pull request assignment in this repository? i.e., what function does automatically self-assigning submitted PRs fulfill?

It doesn't server a major function, it just enables us to see whose working on that particular PR. Generally the PR author is working on it so it makes sense to assign the PR to them automatically.

I updated the configuration in https://github.com/pacstall/pacstall-programs/pull/894/commits/704f1ed7e93ab125648a9e6bda497965651b4054. Per this test pull request, the new configuration should work correctly even for pull requests submitted by third-party contributors.
The install-package status check is configured as a required check, but it is also configured to be skipped if a PR does not change any Pacscripts. This means that PRs not touching Pacscripts are not mergeable. To fix the issue, I pushed https://github.com/pacstall/pacstall-programs/pull/894/commits/15250e617599074ecd0799676b3aa803f84d3b0d and https://github.com/pacstall/pacstall-programs/pull/894/commits/45168d289071d2d49d978d28459b625594700614, which removes the conditional configuration. If there is concern over the increased CI load, I would recommend that we implement a quick script that will check whether the PR touches Pacscripts, and run that at the beginning of the workflow. Let me know if that is needed before we can merge this PR.

If there is concern over the increased CI load, I would recommend that we implement a quick script that will check whether the PR touches Pacscripts, and run that at the beginning of the workflow. Let me know if that is needed before we can merge this PR.

Yeah, that would be better.

@raxod502 any updates on this?

I'll be able to implement the suggested change in the next week or two

Pacscript tests are not being run on this PR, and Pacstall is not being installed, because there are no Pacscript changes. In https://github.com/pacstall/pacstall-programs/pull/1002, I introduced a Pacscript change, and noted that the tests for that Pacscript are being run, and Pacstall is being installed.
With that, I think this feature is working correctly, and we are ready for another review. @wizard-28


Use SPDX identifier in license field of META.info

Use the standardized identifier for the license field.
For more details see https://design.perl6.org/S22.html#license

Closing as this clashes with the meta rename from #1


Powertoys ADMX Download

Provide a description of requested docs changes
I am unable to find where to download the ADMX files for Powertoys.  I see them referenced here https://learn.microsoft.com/en-us/windows/powertoys/grouppolicy#how-to-install

https://github.com/Microsoft/PowerToys/releases/latest und the assets list.

@crutkas
For future releases we should fix the name of the zip file to "Administrative Templates for PowerToys v0.xx.x".

cc: @jaimecbernardo

Need to tweak https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml last bit

Need to tweak https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml last bit

@crutkas
But where to find the file name mask? 🤔 It isn't there.
(Can tweak this in sync with the docs update/rework in #.)

Rename designation folder appropriately would be the easy first step

Rename designation folder appropriately would be the easy first step

@crutkas
What we can do is renaming /src/gpo/assets to /src/PolicyDefinitions. This is the same naming as in Windows (C:\Windows\PolicyDefinitions).

Need to tweak https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml last bit

@crutkas
I am wondering about two things:

Where are the names of the output folder and release assets defined?
Why does the file ends with three dots?

Need to tweak https://github.com/microsoft/PowerToys/blob/main/.pipelines/release.yml last bit

@crutkas I am wondering about two things:

Where are the names of the output folder and release assets defined?
Why does the file ends with three dots?

I think with the latest update to CI draft, these are no longer being assigned as assets in the way that they receive a name. At least I had to manually do those renames this latest release.

@crutkas
I have added detailed download instructions to the docs page. Should we keep this issue open for maybe rename the zip file in the future (or automate generation)?


Delete unnecessary spaces

When copying from the web page, there is an unnecessary space after the code.

@changeworld : Thanks for your contribution! The author, @mikejo5000, has been notified to review your proposed change.

Verified whitespace deletion.
@changeworld Thanks!


similarity score

The code is working properly.
How can I get the similarity score between two samples?

The project cannot provide a similarity score between two samples.


This module are doing incorrect.

Using software ipcal:
willian_pires@wpsXPS:~/Programas/python3/IPS_FROM_REGION$: ipcalc <IP_ADDRESS>/21
Address:   <IP_ADDRESS>         00011111.10000111.11110<PHONE_NUMBER>0
Netmask:   <IP_ADDRESS> = 21   11111111.11111111.11111<PHONE_NUMBER>0
Wildcard:  <IP_ADDRESS>            00000000.00000000.00000<PHONE_NUMBER>1
=>
Network:   <IP_ADDRESS>/21      00011111.10000111.11110<PHONE_NUMBER>0
HostMin:   <IP_ADDRESS>         00011111.10000111.11110<PHONE_NUMBER>1
HostMax:   <IP_ADDRESS>       00011111.10000111.11110<PHONE_NUMBER>0
Broadcast: <IP_ADDRESS>       00011111.10000111.11110<PHONE_NUMBER>1
Hosts/Net: 2046                  Class A
This is network address: <IP_ADDRESS>/21 and this is BroadCast Address: <IP_ADDRESS>
When i run this code:
import ipcalc
address = '<IP_ADDRESS>/21'
c = ipcalc.Network(address)
print(c.broadcast,c.network)
it produce:
<bound method Network.broadcast of Network('<IP_ADDRESS>/21')>
<bound method Network.network of Network('<IP_ADDRESS>/21')>
Look at Network address is not <IP_ADDRESS>/21

Im stuped sorry.


Fix flaky split test

SSIA

Oops, I incorrectly assumed this branch got merged to the main and messed things up.


[Update Request]: GPXSee 13.20

What type of update are you requesting?
A new version of an existing package
Current Package Identifier
tumic0.GPXSee
Package Version
13.20
Please describe the changes you would like to see
GPXSee 13.20 available.
GPXSee 13.16 removed.

Hello, @tumic0 👋🏼
Since you're the publisher & author of this package, would you please consider automatically generate new manifest of this package with WinGet Releaser once a new version release?


"Unsupported drive" with HPE HH LTO-9 on 2.4-stable on CentOS 7.9

Describe the bug
I'm trying to mount a tape (previously formatted) on an HPE LTO-9 drive, but I'm getting "Unsupported drive". I've just built LTFS from source from 2.4-stable.
I have a CentOS system with two LTO drives on it, a Quantum LTO-7 and a new HPE LTO-9. Since the manufacturer-provided RPM packages of LTFS only support their respective hardware, I decided to install 2.4-stable from source. This works fine with the Quantum LTO-7 drive, but when I try to mount a tape from the HPE LTO-9 drive, it tells me the device is unspported. The drive also does not show up when doing ltfs -o device_list
Screenshots
[code]
[root@shinjuku test]# /usr/local/bin/ltfs /mnt/ltfs2 -o devname=/dev/sg74,sync_type=time@20
b3a LTFS14000I LTFS starting, LTFS version <IP_ADDRESS> (Prelim), log level 2.
b3a LTFS14058I LTFS Format Specification version 2.4.0.
b3a LTFS14104I Launched by "/usr/local/bin/ltfs /mnt/ltfs2 -o devname=/dev/sg74,sync_type=time@20".
b3a LTFS14105I This binary is built for Linux (x86_64).
b3a LTFS14106I GCC version is 4.8.5 20150623 (Red Hat 4.8.5-44).
b3a LTFS17087I Kernel version: Linux version 3.10.0-1160.92.1.el7.x86_64<EMAIL_ADDRESS>(gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Tue Jun 20 11:48:01 UTC 2023 i386.
b3a LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core).
b3a LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core).
b3a LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core).
b3a LTFS17089I Distribution: NAME="CentOS Linux".
b3a LTFS14063I Sync type is "time", Sync time is 1200 sec.
b3a LTFS17085I Plugin: Loading "sg" tape backend.
b3a LTFS17085I Plugin: Loading "unified" iosched backend.
b3a LTFS14095I Set the tape device write-anywhere mode to avoid cartridge ejection.
b3a LTFS30209I Opening a device through sg-ibmtape driver (/dev/sg74).
b3a LTFS30213I Unsupported Drive 'HPE     ' / 'Ultrium 9-SCSI  '.
b3a LTFS12012E Cannot open device: failed backend open call.
b3a LTFS10004E Cannot open device '/dev/sg74'
[/code]
Desktop (please complete the following information):

OS: CentOS 7.9
Kernel: 3.10.0-1160.92.1.el7.x86_64

Investigating a bit further, it seems that although README.md for 2.4-stable lists HP LTO-9 drives as supported, the actual hp_supported_drives list in ltfs/src/tape_drivers/hp_tape.c only lists up to LTO-8 as supported. Now the question becomes, is the README file wrong, or is the source code wrong? Is it safe to add LTO-9 to the list and recompile?

Hi, Sorry for our confusable description.
README.md is wrong. Please add the line into hp_tape.c and try. It might work correctly.
TAPEDRIVE( HPE_VENDOR_ID, "Ultrium 9-SCSI",  VENDOR_HP, DRIVE_LTO9,    "[Ultrium 9-SCSI]" ),  /* HPE Ultrium Gen 9 */

@piste-jp-ibm Thank you, but should that VENDOR_HP field be there? The entry for LTO-8 in that list look like this, and all the entries have 4 fields:
TAPEDRIVE( HPE_VENDOR_ID, "Ultrium 8-SCSI",  DRIVE_LTO8,    "[Ultrium 8-SCSI]" ),  /* HPE Ultrium Gen 8 */

Oops, it's for the master branch.
You are right, the line below is good for the v2.4-stable branch.
TAPEDRIVE( HPE_VENDOR_ID, "Ultrium 9-SCSI",  DRIVE_LTO9,    "[Ultrium 9-SCSI]" ),  /* HPE Ultrium Gen 9 */

Thank you, that seems to work, the drive shows up in the list of valid devices, and I can mount the tape. However, when mounting, I do get a couple of messages I haven't seen before, here's the output:
[root@shinjuku ~]# /usr/local/bin/ltfs /mnt/ltfs2 -o devname=/dev/sg74,sync_type=time@20 f7b LTFS14000I LTFS starting, LTFS version <IP_ADDRESS> (Prelim), log level 2. f7b LTFS14058I LTFS Format Specification version 2.4.0. f7b LTFS14104I Launched by "/usr/local/bin/ltfs /mnt/ltfs2 -o devname=/dev/sg74,sync_type=time@20". f7b LTFS14105I This binary is built for Linux (x86_64). f7b LTFS14106I GCC version is 4.8.5 20150623 (Red Hat 4.8.5-44). f7b LTFS17087I Kernel version: Linux version 3.10.0-1160.92.1.el7.x86_64<EMAIL_ADDRESS>(gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Tue Jun 20 11:48:01 UTC 2023 i386. f7b LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core). f7b LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core). f7b LTFS17089I Distribution: CentOS Linux release 7.9.2009 (Core). f7b LTFS17089I Distribution: NAME="CentOS Linux". f7b LTFS14063I Sync type is "time", Sync time is 1200 sec. f7b LTFS17085I Plugin: Loading "sg" tape backend. f7b LTFS17085I Plugin: Loading "unified" iosched backend. f7b LTFS14095I Set the tape device write-anywhere mode to avoid cartridge ejection. f7b LTFS30209I Opening a device through sg-ibmtape driver (/dev/sg74). f7b LTFS30250I Opened the SCSI tape device <IP_ADDRESS> (/dev/sg74). f7b LTFS30207I Vendor ID is HPE     . f7b LTFS30208I Product ID is Ultrium 9-SCSI  . f7b LTFS30214I Firmware revision is Q3F9. f7b LTFS30215I Drive serial is HUJ312FK2J. f7b LTFS30285I The reserved buffer size of /dev/sg74 is 524288. f7b LTFS30205I RSOC (0xa3) returns -20601. f7b LTFS30263I RSOC returns Not Ready to Ready Transition, Medium May Have Changed (-20601) /dev/sg74. f7b LTFS30294I Setting up timeout values from vendor and device. f7b LTFS17160I Maximum device block size is 1048576. f7b LTFS11330I Loading cartridge. f7b LTFS11332I Load successful. f7b LTFS17157I Changing the drive setting to write-anywhere mode. f7b LTFS11005I Mounting the volume. f7b LTFS30205I READ_ATTR (0x8c) returns -20501. f7b LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/sg74. f7b LTFS30205I READ_ATTR (0x8c) returns -20501. f7b LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/sg74. f7b LTFS30205I READ_ATTR (0x8c) returns -20501. f7b LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/sg74. f7b LTFS30233I Cannot read attribute (-20501). f7b LTFS17227I Tape attribute: Vendor = HPE     . f7b LTFS17227I Tape attribute: Application Name = LTFS                            . f7b LTFS17227I Tape attribute: Application Version = 3.5.0   . f7b LTFS17227I Tape attribute: Medium Label = veranda_004. f7b LTFS17228I Tape attribute: Text Localization ID = 0x00. f7b LTFS17227I Tape attribute: Barcode = . f7b LTFS17227I Tape attribute: Application Format Version = 2.4.0           . f7b LTFS17228I Tape attribute: Volume Lock Status = 0x00. f7b LTFS17227I Tape attribute: Media Pool name = . f7b LTFS11031I Volume mounted successfully. NO_BARCODE : Gen = 25 / (a, 5) -> (b, 15859029) / HUJ312FK2J. f7b LTFS14111I Initial setup completed successfully. f7b LTFS14112I Invoke 'mount' command to check the result of final setup. f7b LTFS14113I Specified mount point is listed if succeeded.
The two sections I haven't seen before are:
f7b LTFS30205I RSOC (0xa3) returns -20601. f7b LTFS30263I RSOC returns Not Ready to Ready Transition, Medium May Have Changed (-20601) /dev/sg74.
f7b LTFS30205I READ_ATTR (0x8c) returns -20501. f7b LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/sg74. f7b LTFS30205I READ_ATTR (0x8c) returns -20501. f7b LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/sg74. f7b LTFS30205I READ_ATTR (0x8c) returns -20501. f7b LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/sg74. f7b LTFS30233I Cannot read attribute (-20501).
Are any of these anything to worry about? I'm trying to be as sure as possible that this works before I start using this.

@piste-jp-ibm Just as a status update, I umounted the tape, remounted it as read only, and did some test reads off of the filesystem, all in all about half a terabyte, in different files from different directories, and that all seems to work fine. So reading is ok.
I've now mounted as read/write, and I'm going to do some more testing. For what it's worth, I keep getting these lines when I mount:
1603 LTFS30205I READ_ATTR (0x8c) returns -20501.
1603 LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/sg74.
1603 LTFS30205I READ_ATTR (0x8c) returns -20501.
1603 LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/sg74.
1603 LTFS30205I READ_ATTR (0x8c) returns -20501.
1603 LTFS30263I READ_ATTR returns Invalid Field in CDB (-20501) /dev/sg74.
1603 LTFS30233I Cannot read attribute (-20501).

But the other lines about RSOC have not appeared again. Will report back after more testing.

Are any of these anything to worry about? I'm trying to be as sure as possible that this works before I start using this.

I don't need to worried about the messages severity I, last character shows the severity.
First of all, you need to understand file system (LTFS) is not working with only successful SCSI commands. Almost all commands are successfully done, but a few commands might be failed as expected.
On the other hand, the lowest level SCSI handling code doesn't know an error is not expected or unexpected in that level. So it prints the I level log and upper level code shows W or E level log if it is unexpected. (It is important and useful when we investigate a problem from user. Because we always want to know which SCSI command faild.)
In this case, you didn't have any W and E logs. Don't worry to much.

For RSOC errors (actually not error at all..), I guess you launched ltfs just after load a tape by hand.
The drive state might change from loading to ready between starting ltfs and issueing RSOC command. ltfs upper layer detected it is not-ready-to-ready notification and recover correctly.

@piste-jp-ibm Thank you for all your help. Just as a final report, I've now copied about 6TB to a tape, and then copied various parts of that data back off of the tape and verified it, and it all looks fine, so unless there could be some very strange corner cases, I think I can say that this works fine.

Close, because no activities from 9/22.


Issue with docs.zowe.org/stable/user-guide/install-nodejs-zos

Description

The Links to the IBM node.js are broken.  No longer available.
Pages to Update

Screenshots

Expected behavior

Additional context

Assigned to @samanthasusu


[Event Request] Codeunit 74 Purch.-Get Receipt - function CreateInvLines

Dear,
I request for below Integration

Definition of Integration as below

thanks & regards
Ashwini Tripathi

We already have this event here
procedure GetItemChargeAssgnt(var PurchRcptLine: Record "Purch. Rcpt. Line"; QtyToInvoice: Decimal)
var
    PurchOrderLine: Record "Purchase Line";
    ItemChargeAssgntPurch: Record "Item Charge Assignment (Purch)";
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeGetItemChargeAssgnt(PurchRcptLine, QtyToInvoice, IsHandled);
    if IsHandled then
        exit;


⚠ Cioos National CKAN Sitemap has degraded performance

In b6570f1, Cioos National CKAN Sitemap (https://catalogue.cioos.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 5263 ms

Resolved: Cioos National CKAN Sitemap performance has improved in 6bc55df after 5 minutes.


jQuery Object Lost when clear the global dom scope

When you use
 $('body').html require('views/some-template')

then you change to the controller by using event-trigger instead of re-instantiating the controller(usually recall constructor function)
// projectsController.coffee
@navigate '/projects'
// index.coffee
@routes
    "": ->
	@html require('views/index')
    "/login": ->
	@loginController = new Login(el: $('body'))
    "/projects": ->
	@projectController.active()

the @el will not pointer to the dom even if the dom existed
I will fix it later in the refreshElements of Spine.coffee
by re-finding the DOM using the old id or classes

so, this only is a problem if replacing the element that the spine app is initially set up to work from or one higher in the DOM tree?

I was thinking a similar thing. "don't do that"

Think I will close this. As @adambiggs mentioned if you want to replace controllers nested inside of other controllers you should manage that explicitly. There is just to much to go wrong for Spine to try to handle that for you

@adambiggs Thx U for the help.
I may not understand the philosophy of the Spine architecture very well. And I admit my solution is less efficient but I still feel uncomfortable while handling such problem so that i couldn't substitute the whole body dom free.
I haven't encountered such problem in EmberJS because of another fully different view handle solution. So I wonder if the design of the Spine View Module is not so reasonable.


fix typo in dropRepeatsWith's documentation

It seems that it is a typo, but I am not sure :-)

Actually, I don't think this is a typo.
I'm not sure we've got a great syntax for this yet (see #1554) but the predicate supplied here is never going to be treated as a curried function, even if you supply one that happens to be curried.  It will always be called with two parameters.

if it's not a typo, it's still not correct:
@sig (a, a -> Boolean) -> [a] -> [a]
should be
@sig ((a, a) -> Boolean) -> [a] -> [a]

That's why I brought up #1554.  There is some debate about how we should represent pairs/tuples in these signatures.  But certainly we need something to group them, or there's no way to distinguish between ((a, a) -> Boolean) and (a, (a -> Boolean)).

But agreed we should fix this, and probably to the version @buzzdecafe suggests.

a * a is used to represent tuple in F#.
https://en.wikipedia.org/wiki/Product_type

a * a is used to represent tuple in F#.

right, that traces its ancestry to ML. Unfortunately, I don't think it fits in this case, because we are just trying to indicate that the function takes two arguments, but may or may not be curried. And it does not really take a tuple for an argument.


Windows

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

It would be preferable to build from source. However, I understand Windows is sometimes a mess to get working. Just as long as this is an issue on your radar.


V3 file generation

Adds support to generate the 3.0 spec early_vote_site.txt file, and generate the custom days_times_open with 0 to many schedules.
Pivotal Card

Re-opening it to be based off the auth0-upgrade branch.


url is not defined

When trying to run the step, the step is failing for the following reason.
let host_name = url.parse(gatewayUrl).hostname;
                ^
ReferenceError: url is not defined
    at Object.<anonymous> (/tmp/bitrise982183872/step_src/upload.js:21:17)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
    at internal/main/run_main_module.js:17:47

Thanks.

This is fixed by adding the required nodejs library.


Vulnerability roundup 92: kotlin-1.3.61: 1 advisory [8.8]

search, files

[ ] CVE-2020-15824 CVSSv3=8.8 (nixos-20.03)

Scanned versions: nixos-20.03: 925ae0dee63.
Cc @nequissimus

20.03 is frozen and EOL.
Closing.


webui is not responsive

Hi there,
When I make the window smaller, the webui is not acting right and it's not responsive. I mean it doesn't collapse the sidebar

I'd class this under "papercut" issues, annoying but not enough to an immediate problem. PRs are always welcome for alleviating papercuts.


FadeIn & FadeOut functions

I added the fadeIn and fadeOut functions and also added the welcome text. Furthermore I created an onChange listener which saves the input to localStorage. Can you, @Chris-Mugumwa, please take a look and review my changes?

@Chris-Mugumwa also we need to change the text Color in the input to make it more readable.
Also we need some functions for when we press Enter or press the button to go to the next page. I will create 2 tasks for this


Update Package Lock to Latest Version

Description
package-lock.json updated to the latest version of node_modules to resolve the following issues ...

Resolves #1
Resolves #2
Resolves #3
Resolves #4
Resolves #5
Resolves #6
Resolves #7
Resolves #8

package-lock.json also updated as part of WhiteSource configuration change #12


GitHub Action to lint Python code

Ruff supports over 500 lint rules and can be used to replace Flake8 (plus dozens of plugins), isort, pydocstyle, yesqa, eradicate, pyupgrade, and autoflake, all while executing (in Rust) tens or hundreds of times faster than any individual tool.
The ruff Action uses minimal steps to run in ~5 seconds, rapidly providing intuitive GitHub Annotations to contributors.

I'm so glad to see pythonista being worked towards. Thank you guys. I'd love to collaborate as much as I can. Be it consulting, reviewing, or even editing. Any way possible. It all may end tomorrow, but I'll go down swingin at it.

Test output: https://github.com/cclauss/flixy/actions


Explicitly recommend content digest information

The spec mandated only the verification of digests in the response headers, not the requested digests. That allowed conformant clients not to validate content at all, leaving the users of these clients exposed to accidental or malicious bad content.
This commit adds a "SHOULD verify" clause to the blob and manifest pull sections. It's not a MUST to keep it somewhat backwards compatible with requirements of 1.1 and prior, but it's not a MAY to convey that "the full implications should be understood and the case carefully weighed" (description in RFC 2119) for a client not to verify digests.
Fixes: #549
cc @sudo-bmitch

Thanks for the suggestions, @sudo-bmitch, and sorry for the delay. I'm happy with the change now, wdyt?

Thanks for the suggestions, @sudo-bmitch, and sorry for the delay. I'm happy with the change now, wdyt?

The changes LGTM. Please squash the commits and I'll kick off the CI. @burgerdev


Lazyload efects still working ? effect: 'fadeIn'

Lazyload efects still working ? effect: 'fadeIn'
For older versions (1.9.x) I used:
lazyload({
effect: 'fadeIn',
threshold: 20,
failure_limit: 16
});

Now seems to not working

Curious about this as well. Really liked the fade-in effect!


TypeError: exceptions must derive from BaseException

when i use kanta to process my video , it send this erro.could you tell me how to solve it?
https://user-images.githubusercontent.com/38372764/110197043-bf494e00-7e83-11eb-982d-5ddb8dc9bbcc.mp4

i used:
imgs = vd.extract_video_keyframes(no_of_frames = no_of_frames_to_return,
file_path= video_file_path)
i aimed to extract keyframe

Thank you for the data. We are able to replicate the issue.

it's trouble for you. If you can solve it ,please tell me. Thanks.

There seems to be an issue with the video encoding. You can fix the video by using handbrake https://handbrake.fr/. We are looking at exception handling in code separately

Issue is fixed in new release v0.8.1, Please reinstall Katna for updated version.


Use DeleteCollection to delete pods on the Node at once

What type of PR is this?
/kind feature

What this PR does / why we need it:
Use DeleteCollection to delete pods on the Node at once for better performance.
Which issue(s) this PR fixes:

Fixes #79
Special notes for your reviewer:
/label tide/merge-method-squash

/ok-to-test

/assign

@donaldtang2019
Thanks for your first contribution, welcome to our project.
Your changes require changing the unit tests. So, please fix them. You can run tests with make test in your machine.


Merge main into develop

Automatically syncing these 2 branches failed by the CI server. Merge this pull request manually instead.

:tada: This PR is included in version 1.1.0-alpha.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

Pull request title looks good 👍. If this pull request gets merged, it will not cause a new release of the software.
Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.0.
To merge this pull request, add the label Ready to merge to this pull request and I'll merge it for you.

:tada: This PR is included in version 2.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


DDT-114: Finishing of ReceiveNotifications

This looks good to me. We have to remember that this runs on port 9092 ;-)


GET /callsets/nonexistent-ID returns skeleton CallSet

GET /callsets/some-ID-not-naming-a-real-callset returns a CallSet object with all of its fields set to default values.  Per @jeromekelleher, this is the wrong behavior:

This is wrong all right; any GET /objects/id-that-doesn't-exist should return a 404.

(Incidentally, I found this issue using the new compliance test kit.)

Verfied fixed in #569


Prevent OoM in a tight retry loop

on a machine with very limited resources.
When the number of push threads is low and there are a lot of items in the retry queue; when a  new batch is also forced to be queued, the retry loop is very likely to immediately acquire back the just released lock, not giving the push thread a chance to write to the queue - and this could last for several minutes, quickly eating up heap memory as points are accumulating in a push thread's buffers.

@panghy: Switched from waiting for 50ms to using a less crude approach by using a ReentrantLock in "fair" mode. It also solves the thread starvation issue:
Before:

After:

Thanks for looking into this

@panghy Done!


add option enableOnBoot for virtualisation.libvirtd (like virtualisation.docker)

Issue description
I would like to have libvirtd, but as socket, not as service. I use it, but not on regularly basis. So I would prefer that it only starts when I first connect to the libvirt daemon.
Technical details

system: "x86_64-linux"
host os: Linux 4.14.74, NixOS, 18.09.892.c06f5302f63 (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.1.1
channels(root): "nixos-18.09.892.c06f5302f63"
channels(wucke13): "nixos-unstable-small-19.03pre156243.9772ea03140, nixpkgs-unstable-19.03pre155614.ac7bf94f6df, nixos-unstable-18.09pre150708.083220867c7"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

could possibly be called startWhenNeeded like sshd - https://github.com/NixOS/nixpkgs/blob/0bf2d63366cab1b006366831e581d52f5579090d/nixos/modules/services/networking/ssh/sshd.nix#L76-L84

I do still care about it


chore(pagination): use en dash instead of hyphen

replaces hyphen (-) with en dash(–)
closes https://github.com/IBM/carbon-components/pull/2231 (carbon components)

just pushed a commit which updates the test content with en dashes, hopefully that passes and this PR will be done!


TCPServer and TCPSocket are leaking file descriptors (Linux)

I noticed that prax is leaking file descriptors, and narrowed it down to TCPSocket.new(host, port) opening 2 descriptors, of which only one will actually be closed.

I identified the problem: libevent's evdns_getaddrinfo creates a UDP socket to resolve the host (it always creates the socket, even for "localhost" which is found it in /etc/hosts) but evutil_freeaddrinfo only frees the allocated memory but never closes the UDP socket.
Running strace against the following code will outline this (fd #13 is used to resolve google.fr is never closed), a new socket will be created on each loop and never closed:
require "socket"

loop do
  TCPSocket.new("google.fr", 80).close
  sleep 5
end

open("/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 13
fstat(13, {st_mode=S_IFREG|0644, st_size=172, ...}) = 0
read(13, "# Dynamic resolv.conf(5) file fo"..., 172) = 172
close(13)                               = 0
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 13
fcntl(13, F_GETFD)                      = 0
fcntl(13, F_SETFD, FD_CLOEXEC)          = 0
fcntl(13, F_GETFL)                      = 0x2 (flags O_RDWR)
fcntl(13, F_SETFL, O_RDWR|O_NONBLOCK)   = 0
epoll_ctl(3, EPOLL_CTL_ADD, 13, {EPOLLIN, {u32=13, u64=13}}) = 0
uname({sys="Linux", node="xps", ...})   = 0
sendto(13, "w,\1\0\0\1\0\0\0\0\0\0\6goOgle\2FR\0\0\1\0\1", 27, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("<IP_ADDRESS>")}, 16) = 27
sendto(13, ">>\1\0\0\1\0\0\0\0\0\0\6gOOGle\2Fr\0\0\34\0\1", 27, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("<IP_ADDRESS>")}, 16) = 27
rt_sigprocmask(SIG_SETMASK, [], [], 8)  = 0
epoll_wait(3, {{EPOLLIN, {u32=13, u64=13}}}, 32, 4625) = 1
recvfrom(13, "w,\201\200\0\1\0\1\0\0\0\0\6goOgle\2FR\0\0\1\0\1\300\f\0\1\0"..., 1500, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("<IP_ADDRESS>")}, [16]) = 43
recvfrom(13, 0x7f5d845ac740, 1500, 0, 0x7f5d845acd20, 0x7f5d845acd1c) = -1 EAGAIN (Resource temporarily unavailable)
epoll_wait(3, {{EPOLLIN, {u32=13, u64=13}}}, 32, 3000) = 1
recvfrom(13, ">>\201\200\0\1\0\1\0\0\0\0\6gOOGle\2Fr\0\0\34\0\1\300\f\0\34\0"..., 1500, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("<IP_ADDRESS>")}, [16]) = 55
recvfrom(13, 0x7f5d845ac740, 1500, 0, 0x7f5d845acd20, 0x7f5d845acd1c) = -1 EAGAIN (Resource temporarily unavailable)
rt_sigprocmask(SIG_SETMASK, [], [], 8)  = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 14
fcntl(14, F_GETFL)                      = 0x2 (flags O_RDWR)
fcntl(14, F_SETFL, O_RDWR|O_NONBLOCK)   = 0
connect(14, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("<IP_ADDRESS>")}, 16) = -1 EINPROGRESS (Operation now in progress)
epoll_ctl(3, EPOLL_CTL_ADD, 14, {EPOLLOUT, {u32=14, u64=14}}) = 0
rt_sigprocmask(SIG_SETMASK, [], [], 8)  = 0
epoll_wait(3, {{EPOLLOUT, {u32=14, u64=14}}}, 32, 4585) = 1
epoll_ctl(3, EPOLL_CTL_DEL, 14, {EPOLLOUT, {u32=14, u64=14}}) = 0
rt_sigprocmask(SIG_SETMASK, [], [], 8)  = 0
connect(14, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("<IP_ADDRESS>")}, 16) = 0
close(14)                               = 0

I identified the problem: the evdns_base_new is always called, even thought it should be memoized :(

It's not memoized because Event::Base is a struct, and @base ||= ... updates a copy of the original Scheduler.event_base. I'm not sure how to fix this. Either we always initialize the DNS base or we change Event::Base to be a class, but it may have a performance hit.

Really good catch!! I don't think @dns_base has to be inside Event::Base at all. I'm not sure where yet, but we need to move it somewhere else.

I learnt a lot about debugging stuck processes on the way :smile:


Feature/fs3 592 : Unit test + codecov + code refacto + adding scheduler to campaign

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@61ee114). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage        ?   44.20%
=======================================
  Files           ?       66
  Lines           ?     1070
  Branches        ?        0
=======================================
  Hits            ?      473
  Misses          ?      531
  Partials        ?       66

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


getBTCBalance returns NULL for addresses that have not been seen on the Blockchain

Running the query for an address which has never been seen by the blockchain returns "[]".
It seems there are ~5 possible conditions at play:

address has never been seen.
address found in the mempool with funding.
address found in the mempool, but has been spent (is this possible?)
address found in a block with funding
address found in a block, but has been spent (balance is 0)
Do I understand this correctly?

How can this be handled so as to report back to the calling program the current status of the address?

I just ran a test using an address never seen before and it didn’t return null. It returned 0.00000000 as expected, since if the query returns no UTXOs it doesn’t iterate over anything, but still returns 0 because it’s returning balance variable which has been set to 0.
Can you provide an example of a test run you’ve done showing when null is returned?

My mistake...it was when I ran the query from the command line that it produced the [].
I guess it only matters that the amount of 0 is returned in the long run.


Move initial job health check to infrastructure plugins.

In lifecycle/lifecycle/monitor/monitors.py Racetrack calls the infrastructure targets own monitoring. For the K8s plugin, that is src/monitor.py. A big part of KubernetesMonitor is calling check_until_job_is_operational, which is imported from lifecycle/lifecycle/monitor/health.py.
I propose moving the bulk of the initial monitoring from lifecycle/lifecycle/monitor/health.py to the infrastructure targets themselves. This would allows the K8s infrastructure target to check for K8s specific errors, while still querying the /live and /ready endpoints.
In general, this allows more flexibility for the infrastructure targets to terminate deployments early if something goes wrong, thereby speeding up development for Racetrack users, but it also puts the onus on the infrastructure targets to check /live and /ready, which would lead to a bit of code duplication across plugins.
@iszulcdeepsense
@JosefAssad - who's the new architect so I can ping them?

It makes sense. I'd move this issue to https://github.com/TheRacetrack/plugin-kubernetes-infrastructure if you don't mind since it's plugins responsibility to stop calling the generic health checker from Racetrack core.
I think it may even work fine to work with infrastructure plugins like that:
By default, you can call the health checker from Racetrack to keep the plugin simple. But if you want something more specific, copy it and adjust the code for your needs.

who's the new architect so I can ping them?

Ah, no idea... Sorry.

Moved to https://github.com/TheRacetrack/plugin-kubernetes-infrastructure/issues/26