Function Node Editor Bg gone to White (again)

Current Behavior
After update 3.0 the Function Node Editor background is White (not dark)

Expected Behavior
No response
Steps To Reproduce
No response
Example flow
paste your flow here

Environment

Node-RED version: 3.0
Node.js version: v16.15.0
npm version:
Platform/OS: Home Assistant OS 8.2
Browser: Chrome 103.0.5060.114

Please fill our the whole template and include details of which theme you are using.

I'm pretty sure this is due to the theme you are using not been updated to set the Monaco theme.
Have you checked to see if there is an update to your current theme?
You can also manually set the Monaco theme in the settings.js file of you wish.

Please fill our the whole template and include details of which theme you are using.

I've tried to add all the info I could find. My NR is an add-on in Home Assistant.
If you need anything else, please let me know what and where/how to find it. :)

@Steve-Mcl
Thanks for the reply... I've looked around and did notice that info too - Something about themes being managed by another rep.
Sadly, the instructions for updating didn't point me to anything I could use/understand - I'm not a Unix guy and my NR is an add-on in Home Assistant.
I tried some of the commands I found, in what I think was Terminal, but got some errors about destination paths, etc.

Hi, we don't use HA so not certain we can help other than offer some pointers. You may need to ask for help on the HA forum.

I know that the excellent theme pack by @bonanitech has been updated for v3 & pretty sure the themes set an appropriate code editor theme
If you know how to (or can find out how to) edit your settings.js file , you can choose from any of the built in Monaco themes - take a look at this post on the forum: https://discourse.nodered.org/t/editor-text-size/53944/4

Also, I forgot the add, if this theme is provided/created by the HA team, It would probably be a good thing to let them know (via an issue on their repository) that the theme in question does not set an appropriate Monaco theme.

@3ative, it looks like you have theme: "vs" enabled in your settings.js.
Just comment out that line and then restart Node-RED.

Thanks for all the replies ppl.
Like I said I'm in no way a linux guy 😁 but here's what I could find:
In the config tab of Node-Red (HA Add-on Page) I have set the theme;

And everything in the NR interface is the same colours as before, etc apart from the BG of the Function Node Editor- as seen in the OP.

So [most] of the theme is being used.

As for the settings.js, there is no [theme:] so, I'm guessing the above setting is covering that bit. :)
    // The following property can be used to order the categories in the editor
    // palette. If a node's category is not in the list, the category will get
    // added to the end of the palette.
    // If not set, the following default order is used:
    paletteCategories: [
        'home_assistant',
        'subflows',
        'input',
        'output',
        'function',
        'social',
        'mobile',
        'storage',
        'analysis',
        'advanced'
    ],

    // Configure the logging output
    logging: {
        // Only console logging is currently supported
        console: {
            // Whether or not to include metric events in the log output
            metrics: false,
            // Whether or not to include audit events in the log output
            audit: false
        }
    },

    // Customising the editor
    editorTheme: {
        projects: {
            // To enable the Projects feature, set this value to true
            enabled: false
        }
    }
}

From what I can gather, this "midnight-red" theme IS still being used, it's just the Function Node Editor BG part of the theme itself that hasn't been updated.

Also, while looking at the docs and other web page about updating themes... it talks about npm install to place a theme in a "theme" folder... which there isn't one in /config/node-red.

I'll work with the add-on developer to find a fix for this.

@3ative the core node-red project doesn't maintain any custom themes for the editor. They are mostly all provided by the excellent work done by @bonanitech.
The problem you are having will not lead to any code changes or fixes in Node-RED itself (which is what this issue list is for tracking) - this is what 'upstream' means in this context.

@3ative the core node-red project doesn't maintain any custom themes for the editor. They are mostly all provided by the excellent work done by @bonanitech.
The problem you are having will not lead to any code changes or fixes in Node-RED itself (which is what this issue list is for tracking) - this is what 'upstream' means in this context.

I understand now it's not a NR issue and is something in addition to... Thanks for the clarification too. 👍

It looks like the problem is that they don't have codeEditor in their settings.

@knolleary, shouldn't it work anyway?

@bonanitech can you explain a bit more? Is this not related to the theme then? Do you have a way to recreate this?

If there is no codeEditor object in settings.js, it will not load the customizations made in the theme.

I'll take a look
@knolleary is there time before 3.0.1 for me to see if I can resolve this?

@Steve-Mcl we need to get 3.0.1 released today. I would rather not being doing that late in the evening. If there's a fix that is forthcoming, then yes. Otherwise it'll have to wait until 3.0.2.

5 mins I will push modification - i believe is straight forward and non invasive.
If it makes the cut, great. If not, then 3.0.2

@knolleary  PR done (tests running)

Thanks, guys!

🥰 Great work guys... but,Alas it didn't make 3.0.1

Looking forward to 3.0.2 😀

@3ative 3.0.1 has not been published yet. Other things got in the way. We'll get it released tomorrow.

@3ative 3.0.1 has not been published yet. Other things got in the way. We'll get it released tomorrow.

LOL Yeah, I saw this in my Home Assistant and got excited. 🤣

I can confirm that with the latest Home Assistant Add-on update for NR... Now is all good.
Thanks go to everyone involved. 💖


the actual place of an error in async actualizer is unknown

Problem
Now, in current architecture
error during async actualizer execution -> something like the following message in the log:
*****: [projectors.(*asyncActualizer).Run:73]: air.FillDashboard [4] value of one of RecordID fields is 0: not found

Problem (warm): the place the error is occured at is unknown

Describe the solution you'd like

log the place the error is returned from using skip stack frames?
wrap the error into something that can contain the place?

@host6


It's not possible to get chat by string (username, groupname or channelname)

Official API supports sending strings to getChat:
https://core.telegram.org/bots/api#getchat
But ToChatRef doesn't accept strings. This means I can't operate on any chat given only @reference.

Very useful API, hope to support as soon as possible

let chat:Chat=api.send( telegram_bot::GetChat::new(telegram_bot_raw::types::refs::ChatRef::ChannelUsername(name))).await?;
println!("{:?}", chat);

runs correctly
let chat:Chat=api.send( telegram_bot::GetChat::new(telegram_bot::types::refs::ChatRef::ChannelUsername(name))).await?;
println!("{:?}", chat);

runs correctly
···
let chat:Chat=api.send( telegram_bot::GetChat::new(telegram_bot::types::refs::ChatRef::ChannelUsername("@username"))).await?;
println!("{:?}", chat);
···

Hey thank you! Sorry for being noob...


Update Rest API for websocket

Description
Update the REST Api file for the Websocket app
Fixes #393
Type of change

[x] Documentation update

Checklist:

[x] I did follow the contribution guidelines
[x] New Unit tests added - Not needed
[x] Unit tests pass locally with my changes

Tested manually

Started websocket grid node using the following command

python websocket_app.py --start_local_db --id=anne --port=3001
python websocket_app.py --start_local_db --id=james --port=3002

Upload 1 simple model (only a Linear layer) with 2 names

import torch as th
import syft as sy
import grid as gr
import torch.nn.functional as F

hook = sy.TorchHook(th)

# Connect to the grid nodes
bob = gr.WebsocketGridClient(hook, "http://localhost:3000", id="bob")
anne = gr.WebsocketGridClient(hook, "http://localhost:3001", id="anne")
james = gr.WebsocketGridClient(hook, "http://localhost:3002", id="james")

# Upload downloadable and not downloadable models to worker anne
model = th.nn.Linear(1, 1)
traced_model = th.jit.trace(model, th.Tensor([1.0]))

anne.serve_model(traced_model, "trace_model5", allow_download=False)
anne.serve_model(traced_model, "trace_model3", allow_download=True)

#### THIS PART DID NOT WORK
# Define a new model - it needs to have the encrypt attribute - it's the one from the skin cancer tutorial
def make_model(
    num_classes: int = 2, is_plan=False, model_id="skin-cancer-model-encrypted"
):
    super_class = sy.Plan if is_plan else th.nn.Module

    class Net(super_class):
        """Similar to LeNet5 but without pooling."""

        def __init__(self):
            if is_plan:
                super(Net, self).__init__(id=model_id)
            else:
                super(Net, self).__init__()
            self.conv1 = th.nn.Conv2d(3, 6, 5, 1)
            self.conv2 = th.nn.Conv2d(6, 16, 5, 1)
            self.fc1 = th.nn.Linear(9216, 120)
            self.fc2 = th.nn.Linear(120, 84)
            self.fc3 = th.nn.Linear(84, num_classes)

            if is_plan:
                self.add_to_state(["conv1", "conv2", "fc1", "fc2", "fc3"])

        def forward(self, x):
            x = F.relu(self.conv1(x))
            x = F.relu(self.conv2(x))
            x = x.view(-1, 9216)
            x = F.relu(self.fc1(x))
            x = F.relu(self.fc2(x))
            x = self.fc3(x)
            return x

    return Net()

# Upload encrypted model to worker anne and bob using james as the crypto provider
model.encrypt([bob, anne], crypto_provider=james)
bob.serve_model("skin-cancer", model, allow_download=True, allow_remote_inference=False)

#####

# Split dataset and tag them - used the Spam Notebook

Anne Index after tag and model send
Bob index after tag
Anne - Models
Bob - Models
Anne - Model Copy Allowed
Anne - Model Copy Not Allowed
Anne - Model Copy - Model Not Found
Anne - Get Model - Not Allowed
Anne - Get Model - Not Found
Anne - Get Model - Success
Anne - Search Enc Model - Model Not Found
Anne - Search Enc Model - Payload not correct
Anne - Search Dataset Tag - Success/Fail

Still working on this one, will finish it this week, sorry for the looong delay.

No problem! You're doing a great work :)

Is this project still active?

I have something done for this but it is not finished :( @

I think it can be closed. @IonesioJunior ^^?

Yep! We still need the API documentation, but at this moment a lot of things will change. So, we can close this PR and open a new one in the future.


small fix

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3355f4d). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #99   +/-   ##
=========================================
  Coverage          ?   92.32%
=========================================
  Files             ?       23
  Lines             ?     1016
  Branches          ?        0
=========================================
  Hits              ?      938
  Misses            ?       78
  Partials          ?        0

Continue to review full report at Codecov.

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


Question: Experience with Code Editors + Ignored Files?

Hello, I just stumbled across Meta for the first and am trying it out as I'm in that typical mono-vs-multi repo situation.  I like the idea of meta, however upon trying it out I ran into an issue pretty quickly.  I use Atom, and like other code editors it supports the .gitignore file... so any directories or files that are ignored get grayed-out.  This is a big issue for me in that I now lost my indicators that colorize new (green) and modified (orange) files and the like.
I'm curious if others have worked around this somehow with Atom or similar code editors?  How do you use meta, but still maintain full git support being that the project folders are listed in the top level .gitignore file?
Thanks for the insight, I appreciate any feedback.

Haven't run into this problem, as I use VSCode. Perhaps there are some settings, to control the behavior. Don't know if Atom allows for extensions, but a meta extension could potentially make those not greyed out.

@mateodelnorte thank you for the feedback. I switched over to VSCode, and though I sware without a doubt it initial did work... I am once again in the same spot I was with Atom.  Because the sub-project directories listed in .gitignore I lose all of my git colorization for modifications.
Would really appreciate anyone elses feedback here or is this just me?  Perhaps the workaround will be to add the sub-folders separately to the workspace. :/
FWIW, the pros outway the cons... and I've used it on two projects now.  So thank you for the work you are doing on this, it solves a real problem with a simple clean solution.

yea vscode workspaces - tbh I usually just open multiple vscodes cause I like having the full window integrated debugger for each that I'm working on

@patrickleet I actually tried that. I had a workspace for the meta repo, and a separate that just included the sub-directory projects...  VSCode must be sourcing .gitignore all the way up the parent directory stack becasue if in that case it was still treating the subdirectories as ignored.  I'm at a loss here.
VSCODE: 1.34.0
macOS: Mojave 10.14.4


Proposal: Rationalizing Sequence end-operation names

This proposal suggests renaming or redesigning many APIs which operate on the beginning or end of a Sequence or Collection, with the goal of producing coherently-named method families. In summary:

c.drop… becomes c.removing…
c.…First/Last(n) become c.…Prefix/Suffix(n)
c.starts(with: prefix…) becomes c.hasPrefix(prefix…)
c.index(of: elem/where: isCond) becomes c.firstIndex(of: elem/where: isCond)
c.prefix(upTo: i), c.prefix(through: i), and c.suffix(from: i) become c[..<i], c[...i], and c[i..<]

To support that last change, this proposal includes new IncompleteRange and IncompleteClosedRange types and operators to construct them; it is otherwise not additive.
(@dabrahams suggested reducing the number of subscript overloads using a RangeExpression protocol, but when writing a prototype I realized this would require generic subscripts. Next year!)

Hi Brent,
Thanks for putting this together.  I'm sorry I wasn't able to respond
earlier to this work; we've been swamped!
on Tue Jul 19 2016, Brent Royal-Gordon <notifications-AT-github.com> wrote:

This proposal suggests renaming or redesigning many APIs which operate
on the beginning or end of a Sequence or Collection, with the goal of
producing coherently-named method families. In summary:

c.drop… becomes c.removing…
c.…First/Last(n) become c.…Prefix/Suffix(n)
c.starts(with: prefix…) becomes c.hasPrefix(prefix…)
c.index(of: elem/where: isCond) becomes c.firstIndex(of: elem/where: isCond)
c.prefix(upTo: i), c.prefix(through: i), and c.suffix(from: i) become c[..<i], c[...i], and c[i..<]

To support that last change, this proposal includes new IncompleteRange and IncompleteClosedRange types and operators to construct them; it is otherwise not additive.
(@dabrahams suggested reducing the number of subscript overloads using
a RangeExpression protocol, but when writing a prototype I realized
this would require generic subscripts.

It wouldn't, actually.  You'd just need to write out all the subscript
overloads, as today.  Other APIs could take advantage of it.  The main
reason I want this protocol is that I expect to see more models of
RangeExpression, such as e.g. c[$+256..<] (drop the first 256
elements).

Next year!)  You can view, comment on, or merge this pull request
online at:
https://github.com/apple/swift-evolution/pull/447
-- Commit Summary --

Proposal: Rationalizing Sequence end-operation names

-- File Changes --
A proposals/NNNN-sequence-end-ops.md (766)

-- Patch Links --
https://github.com/apple/swift-evolution/pull/447.patch
https://github.com/apple/swift-evolution/pull/447.diff

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/apple/swift-evolution/pull/447

--
Dave

Okay, I can try to work that into the prototype and proposal tonight. (Question: Should Range conform to RangeExpression? The rule favoring non-generics ought to prefer the Range overload, so it wouldn't actually be ambiguous or recursive.)
Is there anything else that should be done to this proposal?

I notice that AnyRangeExpression<Bound> could be a trivial closure-based type erasing wrapper. Would it be worth including?

@brentdax Please send me a direct email when this is ready to merge, thanks.

Sorry to do tech support on a Github issue, but I'm stuck on a compiler error. This code:
public protocol RangeExpression {
    associatedtype Bound : Comparable
    func relative<C: Indexable>(to collection: C) -> Range<Bound> where C.Index == Bound
}
extension CountableRange: RangeExpression {
    public func relative<C: Indexable>(to collection: C) -> Range<Bound> where C.Index == Bound {
        return Range(self)
    }
}

Gives me: <unknown>:0: error: same-type constraint type 'τ_0_0' does not conform to required protocol 'Comparable'. Despite the less-than-helpful symbol, I suspect this is trying to say that, in the implementation of relative(to:), the compiler thinks C.Index isn't constrained to be Comparable. Except...well, it is. Even IndexableBase.Index is constrained to Comparable.
Is this a bug? Any idea how I can work around it?

on Wed Jul 20 2016, Brent Royal-Gordon <notifications-AT-github.com> wrote:

I notice that AnyRangeExpression<Bound> could be a trivial
closure-based type erasing wrapper. Would it be worth including?

Probably not.  Is there a use-case for this?  Type-erasure is not
usually a win for simple abstractions behind which there is very little
complexity.

on Thu Jul 21 2016, Brent Royal-Gordon <notifications-AT-github.com> wrote:

Is this a bug? Any idea how I can work around it?

Maybe.  If you provide instructions for reproducing it (or even tell us
what line the error appears on), we might be able to diagnose it.
It's almost certainly a bug that you're seeing any message with a “τ” in
it, FWIW.
--
Dave

Reproduction is as indicated: copy those two declarations and paste them into a REPL or playground. (Or put them in the standard library, of course, but it reproduces without that.)

Definitely a bug.  I’m looking for workarounds, but not optimistic.  @rudkx @DougGregor is this something that can be easily fixed?

As a workaround, I would try dropping the relative(to:) interface and put the interface for completing ranges on Collection.

I we might be getting confused over the generic parameter Bound from CountableRange vs. the associatedtype Bound from RangeExpression.

@rudkx Changing Bound to Bound_ in the snippet doesn’t appear to change anything about the result.

Ugly workaround that preserves the general structure of RangeExpressible:
public protocol RangeExpression {
    associatedtype Bound : Comparable
    func relativeTo<BoundDistance: SignedInteger>(start startIndex: Bound, end endIndex: Bound, offset: (Bound, BoundDistance) -> Bound) -> Range<Bound>
}

extension CountableRange: RangeExpression {
    public func relativeTo<BoundDistance: SignedInteger>(start startIndex: Bound, end endIndex: Bound, offset: (Bound, BoundDistance) -> Bound) -> Range<Bound> {
        return Range(self)
    }
}

Hey, whatever it takes, man!  Congratulations on finding it!

Okay, I'm making forward progress again.
There's a comment in some relevant code that references a radar I can't read:
% for Self in 'Indexable', 'MutableIndexable':
[snip]
// WORKAROUND rdar://25214066 - should be on Collection
extension ${Self} {

Can someone take a look at that and distill it for me? Currently I'm putting the equivalents of these subscripts on Collection, and I'm wondering if that's going to be a problem.

on Fri Jul 22 2016, Brent Royal-Gordon <notifications-AT-github.com> wrote:

There's a comment in some relevant
code
that references a radar I can't read:
% for Self in 'Indexable', 'MutableIndexable':
[snip]
// WORKAROUND rdar://25214066 - should be on Collection
extension ${Self} {

Can someone take a look at that and distill it for me?

It means I ran into a compiler bug and this was the workaround.  I have
no idea whether the bug is still alive.  I suggest that if you run into
trouble you follow the pattern already in the standard library.
--
Dave

If I'm not mistaken, the same-type constraint error in your original snippet is due to CountableRange's 'Bound' parameter not currently being required to conform to Comparable.
Either way, the diagnostic here is not useful/actionable, so a new bug at bugs.swift.org would be appreciated.

Scratch that, I now see a 'where' clause that requires Bound to be Comparable:
where
// WORKAROUND rdar://25214598 - should be just Bound : Strideable
Bound : _Strideable & Comparable,
Bound.Stride : SignedInteger {

The prototype with RangeExpression is now operational (and seems to pass all relevant tests), and I've updated the proposal to match. I'd like opinions on a couple points:

I've added @dabrahams as a coauthor since RangeExpression is his design. I'll take you back off if you don't want to be there (or just take yourself off).

With further work, the RangeExpression workaround method actually ended up with a fairly elegant design:
range.relative(to: startIndex ..< endIndex, offsettingBy: index(_:offsetBy:))
func relative<BoundDistance: SignedInteger>(to bounds: Range<Bound>, offsettingBy offset: (Bound, BoundDistance) -> Bound) -> Range<Bound>

The proposal calls this temporary and suggests the documentation call it out as likely to change, but should we instead go with this as the intended design?

Now that we're touching removeSubrange(i ... j) and replaceSubrange(i ... j, with: [x, y]), I'm wondering if they should be renamed as well, perhaps to one of these:

remove(i ... j) and replace(i ... j, with: [x, y])
remove(at: i ... j) and replace(at: i ... j, with: [x, y])
remove(in: i ... j) and replace(in: i ... j, with: [x, y])

Other than these points, I think this is ready to go.

on Sun Jul 24 2016, Brent Royal-Gordon <notifications-AT-github.com> wrote:

The prototype with RangeExpression is now operational (and seems to
pass all relevant tests),

Nice!  IMO you should submit a PR (with a do not merge until proposal is
accepted note) and reference that from the proposal.

and I've updated the proposal to match. I'd like opinions on a couple
points:

I've added @dabrahams as a coauthor since RangeExpression is his
design. I'll take you back off if you don't want to be there (or just
take yourself off).

Thanks, that's fine.

With further work, the RangeExpression workaround method actually ended up with a fairly elegant design:range.relative(to: startIndex ..< endIndex, offsettingBy: index(_:offsetBy:))
func relative<BoundDistance: SignedInteger>(to bounds: Range<Bound>,

offsettingBy offset: (Bound, BoundDistance) -> Bound) -> Range
The proposal calls this temporary and suggests the documentation
call it out as likely to change, but should we instead go with this as
the intended design?

I'm really glad you found a workaround, but I don't think it's where we
should end up.  Do you disagree?

Now that we're touching removeSubrange(i ... j) and
replaceSubrange(i ... j, with: [x, y]), I'm wondering if they should
be renamed as well, perhaps to one of these:

remove(i ... j) and replace(i ... j, with: [x, y])
remove(at: i ... j) and replace(at: i ... j, with: [x, y])
remove(in: i ... j) and replace(in: i ... j, with: [x, y])

Other than these points, I think this is ready to go.

Those names were very carefully chosen, and I guess I'd rather not
consider changing them as part of this proposal, which is mostly
orthogonal.

FYI I created a test case that doesn't rely on the stdlib as it exists today, and opened a JIRA bug for it: https://bugs.swift.org/browse/SR-2158

I'm really glad you found a workaround, but I don't think it's where we should end up.  Do you disagree?

I think you said you preferred the name RangeExpression over something involving "subrange" because you wanted it to be more broadly applicable than that. On the other hand, the mere fact that this API is more broadly applicable than one that uses Collection doesn't necessarily mean this is the more-broadly-applicable API we want, so it's probably best to keep our options open for now.
With this last batch of minor tweaks, I think this is ready to go. @dabrahams, @lattner, it's your show.
@rudkx Thank you! I meant to fully reduce it once we got this thing merged, but you've saved me the effort. I've updated the comments in the prototype to point to that bug.

Is there any concern that prefix operator ... might conflict with the syntax for some future parameter-pack-ish feature?

@jtbandes That's an interesting point, and one I hadn't considered.
I've chosen to propose the full set of operators that would make sense for this feature and allow the reviewers and core team to whittle them down if they want something narrower. I won't be upset if some of them are removed.
(For what it's worth, postfix ... is the most expendable operator—it's included for completeness, but it's not actually useful for subscripting. The infix forms provide access to all of this proposal's functionality, at the cost of having to write—and more importantly, to read and interpret—array[i..<nil] instead of array[i..<].)


Fix rescaleWithRoundUp

@zhouyuan Verified on Gluten CI https://github.com/oap-project/gluten/pull/3560.

Included in https://github.com/oap-project/velox/pull/454 for branch-1.1
the changes will be merged in later rebase work


Set true to Sys.interactive

Issue: #78
Sys.interactive controls loading ocamltoplevel.cma inside OCaml top level at toplevel/toploop.ml.
ocamltoplevel.cma causes Unbound value error on REPL:

This PR rejects loading ocamltoplevel.cma like:

I hide the ocamltoplevel.cma error:


Fix language descriptor

Fixes #40255

Internal previews

📄 File
🔗 Preview link

docs/csharp/linq/standard-query-operators/set-operations.md
Set operations (C#)

Hi while your at it in the same MD doc there are two other plcaes where the same issue is https://github.com/search?q=repo%3Adotnet%2Fdocs language%3D"csharp%3B"&type=code


Show the commands that are executed.

I would love to see an advanced or dev mode that shows the commands that are going to be run for any selected option. Perhaps this would be more useful to daily Linux users who want to know what happens behind the scenes.
Also, this tool is amazing. ❤

Each script is completely separate, so this would be quite involved. The linutil TUI has very little control over the scripts it launches.

I would love to see an advanced or dev mode that shows the commands that are going to be run for any selected option. Perhaps this would be more useful to daily Linux users who want to know what happens behind the scenes.
Also, this tool is amazing. ❤

You can press P on any selected option and it will show you the commands that will be executed for the selected option

You can press P on any selected option and it will show you the commands that will be executed for the selected option

Ah! this is similar to what I needed. Looking at the script can figure out what is going to run. Perhaps an indication to P could be added somewhere.

I am working on this will be added soon

As jeevi said above this has been implemented and is in the current release.

/close


Remove Release Notification Listener

Tell us about your request
E2E tests are currently using the Release Notification Listener to monitor an SQS queue and pull off messages from the queue to run Tekton pipelines. This works as a streamlined approach for both running tests [in periodics] and based off a github /karpenter snapshot message.
Rather than having the overhead of running the listener on the E2E test cluster and maintaining an SQS queue, we should investigate if we can auth directly from GHA into the K8s cluster to deploy the the PipelineRun directly into the cluster. This way we don't have to maintain this SQS queue and the periodic cronJob can directly apply the PipelineRun into the cluster rather than reaching outside to the SQS queue like it's doing now.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
N/A
Are you currently working around this issue?
Pushing messages into the SQS queue that is being pulled from by the Release Notification Listener to perform PipelineRun applies
Additional Context
No response
Attachments
No response
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

On top of this, release notification listener doesn't have a good GitOps pipeline to get deployed to the cluster, which means that the deployment that sits on the cluster has the potential to be removed without an audit trail

Closed with #4179


Offer conditions: References with details

This is an alternative to #546 which asks providers to give details of the number and type of referees required.
This has the advantage that it is more flexible depending on the requirements of the provider, and would allow us to remove all the guidance we show to candidates about the types of reference required (for example, an academic reference if graduating within the past 5 years).
Trello card: https://trello.com/c/zcZy7o9e/212-new-reference-prototypes-for-manage
Screenshot

 New reference prototypes for Manage


Maximum rectangular area in Histogram

I would like to add the problem of Maximum rectangular area in Histogram under LGM SOC'21.
Language: C++
Please assign this issue to me.

I want to add the solution for Maximum Histogram area in c
@Ayush7614  @Amit366  could you please assign this issue to me


eid-mw: 4.4.1 -> 4.4.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/eid-mw/versions.
These checks were done:

built on NixOS
Warning: no invocation of /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/bin/eid-viewer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/bin/.eid-viewer-wrapped had a zero exit code or showed the expected version
/nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/bin/beid-update-nssdb passed the binary check.
/nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/bin/eid-nssdb passed the binary check.
2 of 4 passed binary check by having a zero exit code.
0 of 4 passed binary check by having the new version present in output.
found 4.4.2 with grep in /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2
directory tree listing: https://gist.github.com/9bc7e47978cdc6d1c57b60a0cdf06ffc
du listing: https://gist.github.com/8f3d2be711226cec456c9d62c6e114d6

meta.description for eid-mw is: '"Belgian electronic identity card (eID) middleware"'.
cc @bfortz for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout daecb043eedd0427971228662cbd8aa2c9c4ecac && nix-shell --pure -I nixpkgs=. -p eid-mw

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: eid-mw
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: eid-mw
Partial log (click to expand)
shrinking /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/libexec/beid-askaccess
shrinking /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/libexec/beid-spr-askpin
shrinking /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/libexec/beid-spr-changepin
shrinking /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/bin/.eid-viewer-wrapped
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/lib  /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/libexec  /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/bin
patching script interpreter paths in /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2
/nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/bin/beid-update-nssdb: interpreter directive changed from "/bin/bash" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/bash"
/nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2/bin/eid-nssdb: interpreter directive changed from "/bin/sh" to "/nix/store/qckzjk3406va7h6s40cy9s75z2w715rq-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/fb82i287dxzdi7iymk84yyvrx5ph4x41-eid-mw-4.4.2...

Works OK. @xeji could you also backport to 18.03? Thanks!

backported in f4fdffd1ea31c924e2372eaa91d113fc0259461e


Hardware Buttons management

Short description of the problem:
I strongly believe that Ionic 2 should have a default minimum hardware Buttons management feature, which should implement following behaviours:
What behavior are you expecting?
Hardware back button

If user is on homepage, pressing hardware back button should:

exit application     =>OK
optionnally require confirmation from user (alert)     => To be implemented

If sidemenu is opened, pressing hardware back button should:

close sidemenu     => To be implemented

if an alert is opened, pressing hardware back button should:

act as if user clicked on one of the buttons (optionnaly configured) => To be implemented

if a popover is opened, pressing hardware back button should:

close popover     => ok

If we are in a tabbed view, pressing hardware back button should:

pop the tabbed views, including tabbed container     => sometimes work, sometimes go back to previous tabbed view, depending on device (android versions: 4.1.2 and 5.1)

if not in above cases: pressing hardware back button should:

pop to previous view     => OK

Hardware Menu button
When user press hardware menu button:

if a sidemenu exists: toggle sidemenu
if no sidemenu but a contextual menu exist: toggle contextual menu
if no menu: do nothing
Currently, harware menu button is not managed.

My opinion is that these cases should be managed by default, and that developers should only have to manage cases specific to their app/project.
This is non sense that each developer has to implement these features by himself: time lost!
Please feel free to add any other case I have not listed here.
Which Ionic Version? 2.0 RC0

Hello, thanks for opening an issue with us! I am going to close this issue as a duplicate of https://github.com/driftyco/ionic/issues/7611.


[doc] Fix getNews example

The Http.expectJson has this signature : expectString : (Result Error String -> msg) -> Expect msg.
The getNews example from the doc does not comply with it, hence this PR to clarify :)
Note that I may be totally wrong with this PR, still it may lead to a clearer example :woman_shrugging:
PSS. thanks for this package  :heart:

closing in favor of https://github.com/dillonkearns/remotedata/pull/2/files/199cccfa0f9a943e38c8d72010c96dd7c97534be..9c5f33871a2f948897cdff2635a706784990d7cf


AttributeError: 'Namespace' object has no attribute 'norm_dets'. When using format_dets with value txt.

Describe the bug
Thank you for this awesome tool. There seems to be a bug in cli when specifying --format_dets txt. A simple fix may be renaming norm_in_dets found here to norm_dets (or vise versa) if I understood the code correctly.
To Reproduce
Steps to reproduce the behavior:

Specify --format_dets txt --norm_dets rel detection options when using globox cli tool.

Expected behavior
No error happens and I can use both --format_dets txt and --norm_dets rel.
Environment (please complete the following information):

Ubuntu 22.04 (WSL).
Globox version 2.4.3.
Python 3.10.12.

Additional context
Error traceback:
Traceback (most recent call last):
  File "/home/user/.local/bin/globox", line 8, in <module>
    sys.exit(main())
  File "/home/user/.local/lib/python3.10/site-packages/globox/cli.py", line 384, in main
    predictions = parse_dets_annotations(args, coco_gts=coco_gts)
  File "/home/user/.local/lib/python3.10/site-packages/globox/cli.py", line 268, in parse_dets_annotations
    relative: bool = args.norm_dets == "rel"
AttributeError: 'Namespace' object has no attribute 'norm_dets'. Did you mean: 'format_dets'?

Thanks for reporting this bug and for the details.
I fixed this issue in the last version 2.4.4.

Sorry to bump this closed issue, but as far as I can tell, the problem still persist. What did the trick for me, was changing line 268 from relative: bool = args.norm_dets == "rel" to relative: bool = args.norm_in_dets == "rel".
Please correct me if I am wrong, but it is parse_dets_annotations function that had to to be modified in this situation, not the parse_annotations, as was done in your fix. That is because we are dealing with detection format arguments.
@laclouis5

@mziai Whoops, I did it too fast and updated the wrong line without testing. Could you check if PR #46 solves the issue please ? This reverts the last fix and updates line 268 instead.


fix indent_style

https://github.com/sindresorhus/atom-editorconfig/issues/36

also there should be 3. states for indent_styles
-tab (use tabs)
-space (use spaces)
-undefined (use editors default config)

What's the editors default?

the config at Preferences => Soft Tabs

Then I guess it's spaces so we can safely use the isTab variable anyway.

No, it's not o.0

It it's soft tabs it's spaces?

Yeah, but if it's turned off then it should use tabs (unless specified by editorconfig).

// @bobrocke @ezekg @ismay

:+1:


FEATURE REQUEST:  show docker swarm stack just as service tab

Description
Show docker swarm stack as service tab. Show stack information just like docker stack [command]

If you're talking about docker stack support, it'll be implemented via #257.
Feel free to re-open if needed.

@deviantony sorry for duplicated requests..


Crashes when using magit's time-machine-transient-state

Environment

Elixir & Erlang versions (elixir --version): 1.8.1
Operating system: MacOS
Client (editor or IDE): Emacs 26.3

Crash report template
Delete this section if not reporting a crash

If using a client other than VS Code, please try VS Code's ElixirLS extension. Does it reproduce your failure?
It doesn't have magit
Create a new Mix project with mix new empty, then open that project with VS Code and open an Elixir file. Is your issue reproducible on the empty project? If not, please publish a repo on Github that does reproduce it.
Yes
Check the output log by opening View > Output and selecting "ElixirLS" in the dropdown. Please include any output that looks relevant. (If ElixirLS isn't in the dropdown, the server failed to launch.)
Not in VSCode
Check the developer console by opening Help > Toggle Developer Tools and include any errors that look relevant.
Not in VSCode

Steps to reproduce

Create a new project
Create at least two git commits
Use time-machine-transient-state to display the state of the file under a previous commit

@x-ji Please provide logs if you want this fixed. Otherwise we are unable to support every Emacs plugin out there


Always check read_len's remaining length in structs

Fixes #171

While this fixes #171 we still have the issue in #175 remaining. It is only an issue when you have overlapping variants AND they are inlined. When they're merely overlapping (e.g. shelley vs alonzo tx outs) this PR fixes the issue. When they were never overlapping (regardless of if inlined) then there was never an issue in the first place.


online javascript --> offline javascript

Wouldnt it better if we have the js and css files loaded over from the cdn provider to reduce the load on our server.

Well, this is also a good point. But we should definitely look into
something which can load the website faster

Sri Harsha Gajavalli
B.Tech - 3rd Year
Computer Science and Engineering
IIIT Chittoor
Sri City-517588
(+91)-91007 53548
On Mon, Apr 16, 2018 at 10:21 PM, David Christie<EMAIL_ADDRESS>wrote:

Wouldnt it better if we have the js and css files loaded over from the cdn
provider to reduce the load on our server.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AIDeveloperCommunity/aidevelopercommunity.github.io/issues/11#issuecomment-381672685,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATrjCcu7tphOW1tYvUD8AlfBHI_BJJAhks5tpMwggaJpZM4TBVb1
.

The new template doesnt seem to have the loading issues.
Close this issue?


Add UnionPay brand

reference: https://en.wikipedia.org/wiki/Payment_card_number#Issuer_identification_number_(IIN)

@heynext Please rebase this PR from master

@heynext Please rebase this PR from master

@faiyaz-shaikh  done


[Helix] HttpClientFactory DisposesLiveHandler is flaky on OSX/Linux queues

This tests fails roughly half the time on helix runs of 2.1, OSX/ubuntu queues specifically, seems reliable on Win10
@rynowak github blame says this bad boy might be yours?  Any ideas why this test might be misbehaving?
For example: https://mc.dot.net/#/user/dotnet-github-anon-kaonashi-bot/pr~2Faspnet~2Fextensions/ci/20181211.10/workItem/Microsoft.Extensions.Http.Tests~2Fnetcoreapp2.0/wilogs
[xUnit.net 00:00:02.57]     Microsoft.Extensions.Http.DefaultHttpClientFactoryTest.Factory_CleanupCycle_DisposesLiveHandler [FAIL]
Failed   Microsoft.Extensions.Http.DefaultHttpClientFactoryTest.Factory_CleanupCycle_DisposesLiveHandler
Error Message:
 Cleanup entry disposable
Expected: True
Actual:   False
Stack Trace:
   at Microsoft.Extensions.Http.DefaultHttpClientFactoryTest.Factory_CleanupCycle_DisposesLiveHandler() in /_/src/HttpClientFactory/Http/test/DefaultHttpClientFactoryTest.cs:line 409

This is a super fun test. I made some improvements to this in 2.2, and I think I finally did fix the flakiness.

Ah, actually that was master, not 2.2. Are we fixing flaki-wakies on 2.1?

Can you backport the fixes to 2.1?  That's where we are starting with the helix runs

Sure

Should be fixed by https://github.com/aspnet/Extensions/pull/635#event-2022475211


e_sqlite3 not found on net462

I'm trying to add a .NET Framework target to the tests for an existing project. The test project references a .NET Standard wrapper library that PackageReferences a SQLitePCL.raw bundle:
Library csproj: https://github.com/zmj/sqlite-fast/blob/master/Sqlite.Fast/Sqlite.Fast.csproj
Test csproj: https://github.com/zmj/sqlite-fast/blob/master/Sqlite.Fast.Tests/Sqlite.Fast.Tests.csproj
Batteries.Init call: https://github.com/zmj/sqlite-fast/blob/master/Sqlite.Fast/Connection.cs#L15
On Mono / M1 Mac, the tests fail on the Batteries.Init call. They also fail on Windows 11 x64 with a similar error. I'll add that output in a comment.
dotnet test output:
  Error Message:
   System.TypeInitializationException : The type initializer for 'Sqlite.Fast.Connection' threw an exception.
---- System.Exception : Library e_sqlite3 not found
plat: dlopen
suffix: DYLIB
possibilities (2):
    1) /private/var/folders/jp/s3w4bhcs0lx1kjp_7rgm10jr0000gn/T/6a8ac9fc-ea25-4701-9a77-c5f5cf22da04/6a8ac9fc-ea25-4701-9a77-c5f5cf22da04/assembly/shadow/9253aac8/ac26431d_3e75e9d5_00000002/runtimes/osx-x64/native/libe_sqlite3.dylib
    2) /private/var/folders/jp/s3w4bhcs0lx1kjp_7rgm10jr0000gn/T/6a8ac9fc-ea25-4701-9a77-c5f5cf22da04/6a8ac9fc-ea25-4701-9a77-c5f5cf22da04/assembly/shadow/9253aac8/ac26431d_3e75e9d5_00000002/libe_sqlite3.dylib
dlopen TryLoad: /private/var/folders/jp/s3w4bhcs0lx1kjp_7rgm10jr0000gn/T/6a8ac9fc-ea25-4701-9a77-c5f5cf22da04/6a8ac9fc-ea25-4701-9a77-c5f5cf22da04/assembly/shadow/9253aac8/ac26431d_3e75e9d5_00000002/runtimes/osx-x64/native/libe_sqlite3.dylib
dlopen gave: 0
dlopen TryLoad: /private/var/folders/jp/s3w4bhcs0lx1kjp_7rgm10jr0000gn/T/6a8ac9fc-ea25-4701-9a77-c5f5cf22da04/6a8ac9fc-ea25-4701-9a77-c5f5cf22da04/assembly/shadow/9253aac8/ac26431d_3e75e9d5_00000002/libe_sqlite3.dylib
dlopen gave: 0
NOT FOUND

  Stack Trace:
    at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_generic_class_init(intptr)
  at Sqlite.Fast.Tests.TestTable..ctor (System.String createTableSql) [0x00008] in <776f3b1ba5e2418f8366f895574427ec>:0
  at Sqlite.Fast.Tests.ConverterTests.Scalar_FromInt () [0x00009] in <776f3b1ba5e2418f8366f895574427ec>:0
  at (wrapper managed-to-native) System.Reflection.RuntimeMethodInfo.InternalInvoke(System.Reflection.RuntimeMethodInfo,object,object[],System.Exception&)
  at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0006a] in <b27839cc2dba4804baacf2f5cce6de32>:0
----- Inner Stack Trace -----
  at SQLitePCL.NativeLibrary.Load (System.String libraryName, System.Reflection.Assembly assy, System.Int32 flags) [0x00058] in <8a9cf65dcc6542b59d3abc28e58f9815>:0
  at SQLitePCL.Batteries_V2.MakeDynamic (System.String name, System.Int32 flags) [0x00010] in <8a9cf65dcc6542b59d3abc28e58f9815>:0
  at SQLitePCL.Batteries_V2.DoDynamic_cdecl (System.String name, System.Int32 flags) [0x00000] in <8a9cf65dcc6542b59d3abc28e58f9815>:0
  at SQLitePCL.Batteries_V2.Init () [0x00000] in <8a9cf65dcc6542b59d3abc28e58f9815>:0
  at Sqlite.Fast.Connection..cctor () [0x00000] in <b25266bf021944fbb119c28d8aecb6d8>:0

Looking at the existing open issues, I see some workarounds supplying explicit RuntimeIdentifiers. Is that something I should be doing?
Template info:

What version of SQLitePCLRaw are you using?

2.1.2. Also tried 2.0.7, same error.

If you are using one of the SQLitePCLRaw bundle packages, which one?

Tried green and e_sqlite3.

What platform are you running on?  What operating system?  Which version?  What CPU?

OSX Ventura, M1 Pro.
WIndows 11 x64.

What target framework are you building for?

net462. Also tried net48, same error.

Are you on .NET Framework or the newer stuff (.NET Core, .NET 5+, etc)?

Framework.

Are you using the command line, or an IDE?  Which IDE?  Which version of that IDE?

Command line. On Windows, the error message is the same in Visual Studio 2022.

Is this problem something that just started happening?  For example, were things working well for you and then you updated something and then the problem showed up?  What changed?

No. I'm trying to add a net framework target to tests that were previously netcore only.

What is the exact error message you are seeing when the problem happens?

See above.

Are you using PackageReference or packages.config?

PackageReference

If you are using mobile platforms, are you on classic/legacy Xamarin or on .NET 6 and higher?

N/A

Sometimes other packages using SQLitePCLRaw cause problems when they are mixed together.  What other packages are you including in your project?

Minimal. See csproj links above.

How can we reproduce the problem you are seeing?  Your issue will get attention much faster if you attach a minimal reproduction sample project.

Clone the repository (links above) and run the tests.

On Windows:
  Error Message:
   System.TypeInitializationException : The type initializer for 'Sqlite.Fast.Connection' threw an exception.
---- System.Exception : Library e_sqlite3 not found
plat: win
suffix: DLL
possibilities (2):
    1) C:\Users\zmj\AppData\Local\Temp\d5e5718b-ca74-4b1d-8c7d-e3b7f63a95fa\d5e5718b-ca74-4b1d-8c7d-e3b7f63a95fa\assembly\dl3\bbda9fce\004c6898_94cbd801\runtimes\win-x86\native\e_sqlite3.dll
    2) C:\Users\zmj\AppData\Local\Temp\d5e5718b-ca74-4b1d-8c7d-e3b7f63a95fa\d5e5718b-ca74-4b1d-8c7d-e3b7f63a95fa\assembly\dl3\bbda9fce\004c6898_94cbd801\e_sqlite3.dll
win TryLoad: C:\Users\zmj\AppData\Local\Temp\d5e5718b-ca74-4b1d-8c7d-e3b7f63a95fa\d5e5718b-ca74-4b1d-8c7d-e3b7f63a95fa\assembly\dl3\bbda9fce\004c6898_94cbd801\runtimes\win-x86\native\e_sqlite3.dll
thrown: System.ComponentModel.Win32Exception (0x80004005): The specified module could not be found
   at SQLitePCL.NativeLibrary.TryLoad(String name, Loader plat, Action`1 log, IntPtr& h)
win TryLoad: C:\Users\zmj\AppData\Local\Temp\d5e5718b-ca74-4b1d-8c7d-e3b7f63a95fa\d5e5718b-ca74-4b1d-8c7d-e3b7f63a95fa\assembly\dl3\bbda9fce\004c6898_94cbd801\e_sqlite3.dll
thrown: System.ComponentModel.Win32Exception (0x80004005): The specified module could not be found
   at SQLitePCL.NativeLibrary.TryLoad(String name, Loader plat, Action`1 log, IntPtr& h)
NOT FOUND

  Stack Trace:
     at Sqlite.Fast.Connection..ctor()
   at Sqlite.Fast.Tests.TestTable..ctor(String createTableSql) in D:\sqlite-fast\Sqlite.Fast.Tests\TestTable.cs:line 13
   at Sqlite.Fast.Tests.ConverterTests.Custom_ToBlob() in D:\sqlite-fast\Sqlite.Fast.Tests\ConverterTests.cs:line 226
----- Inner Stack Trace -----
   at SQLitePCL.NativeLibrary.Load(String libraryName, Assembly assy, Int32 flags)
   at SQLitePCL.Batteries_V2.MakeDynamic(String name, Int32 flags)
   at SQLitePCL.Batteries_V2.DoDynamic_cdecl(String name, Int32 flags)
   at SQLitePCL.Batteries_V2.Init()
   at Sqlite.Fast.Connection..cctor() in D:\sqlite-fast\Sqlite.Fast\Connection.cs:line 15

I cloned your repo and reproduced the problem.
Then I added a file called xunit.runner.json into Sqlite.Fast.Tests, containing:
{
   "shadowCopy": false
}

Then I added this snippet to Sqlite.Fast.Tests.csproj:
  <ItemGroup>
    <None Include="xunit.runner.json" CopyToOutputDirectory="PreserveNewest" />
  </ItemGroup>

After that dotnet test works.
This is a common problem when using xunit with .NET Framework.

Thank you! That fixed things.


MSID: 88256 Version: 2 DOI: 10.1101/2<IP_ADDRESS>6370

MSID: 88256
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>6370
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=88256
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>6370

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/88256v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>6370
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/88256/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

warn: [article-email-corresp-author-count-equivalence] The number of corresponding authors (1: Kumaravel Somasundaram) is not equal to the number of distinct email addresses (2<EMAIL_ADDRESS>ksomasundaram1@gmail.com). Is this correct?

Above is fine as is. Fixing bold terms throughout


Add example for entrypoint on one ip address

What does this PR do?
Show by example how to bind an entrypoint to a single ip address. Similar as earlyer by #1194.

Motivation
There is not mentioned anywhere in the doc that an IP address can be set for an entry point. (Except in #1193) Write it in full examplw, since I searched it there.

More

[ ] Added/updated tests
[x] Added/updated documentation

Additional Notes
A short separate section with explication would better. There could be more examples as requested in #5059 (ipv6, multiple addresses?, network mask?, ...)

Hello,
It will be better to add a dedicated example instead of changing an existing one.

I can write a short section within some days. Found the syntax for ipv6 on https://golang.org/pkg/net/#Listen and https://golang.org/pkg/net/#Dial
But I still have no idea what ip address to choose for which provider (docker container, docker swarm, ...)

Just add a simple example in the entry point page: https://docs.traefik.io/v2.1/routing/entrypoints/#configuration-examples

I rebased and did force push because it was on the wrong branch.

ready for another review


Update to Uniform documentation standards

Let's make sure we have all functions documented properly and in the same manner

One needs to go through and make sure all functions appear in the doc. Style seems to be propagated.


[ENH] histogram distribution

For distribution estimation, an important distribution type is the histogram distribution.
This will be parameterized by bins and bin densities.

Just needed some clarification, the bins would be the upper bound for the interval it will be an array or if its a single value then it will be divided equally and the bin_density will have an array of same size with values for all the bins ranging from [0,1] interval as we want it to be a probability distribution. Or do we want to store the frequency in the bin_density and then divide by total frequency to bring it down to [0,1].
Do I understand the requirement correctly?

Do I understand the requirement correctly?

The exact specification has not been set out, so it would be great if you could make a few suggestions!
The suggestion on specifying by number of bins, or bin boundaries both make sense - in fact these are both so common that popular interfaces like pandas.cut allow for both, via a polymorphic interface: http://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.cut.html

@fkiraly There were some merge conflicts in the init.py in distributions and distributions.rst that were troubling a little so I decided to make a new PR #382 instead, so there are no conflicts.
All the discussion regarding the Histogram discussion has been discussed in the PR #335.

Reopening to keep a reminder of "summarizing outcomes" (vectorization) from https://github.com/sktime/skpro/pull/382 in a new issue.

Reopening to keep a reminder of "summarizing outcomes" (vectorization) from #382 in a new issue.

I have opened https://github.com/sktime/skpro/issues/405  summarizing the outcomes of vectorization.


Standardise files with files in sous-chefs/repo-management

Signed-off-by: Dan Webb<EMAIL_ADDRESS>

Released as: 4.4.1


does not load beyond 1 epoch

my video card is not detected, but it was not a problem. last time I calmly trained a working model in a couple of hours.
now when I try to run, doing everything the same as yesterday, nothing works. do not load further than the first epoch
C:\RVC>runtime\python.exe infer-web.py --pycmd runtime\python.exe --port 7897 --dml
No supported Nvidia GPU found
use DirectML instead
Use Language: en_US
Running on local URL:  http://<IP_ADDRESS>:7897
runtime\python.exe trainset_preprocess_pipeline_print.py "C:\RVC\sampl\mayni-model\sample.mp3" 40000 3 "C:\RVC/logs/mayni123" False
['trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model\sample.mp3', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
start preprocess
['trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model\sample.mp3', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
Fail. Traceback (most recent call last):
File "C:\RVC\trainset_preprocess_pipeline_print.py", line 111, in pipeline_mp_inp_dir
for idx, name in enumerate(sorted(list(os.listdir(inp_root))))
NotADirectoryError: [WinError 267] Неверно задано имя папки: 'C:\RVC\sampl\mayni-model\sample.mp3'
end preprocess
start preprocess
['trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model\sample.mp3', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
Fail. Traceback (most recent call last):
File "C:\RVC\trainset_preprocess_pipeline_print.py", line 111, in pipeline_mp_inp_dir
for idx, name in enumerate(sorted(list(os.listdir(inp_root))))
NotADirectoryError: [WinError 267] Неверно задано имя папки: 'C:\RVC\sampl\mayni-model\sample.mp3'
end preprocess
runtime\python.exe trainset_preprocess_pipeline_print.py "C:\RVC\sampl\mayni-model" 40000 3 "C:\RVC/logs/mayni123" False
['trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
start preprocess
['trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
['C:\RVC\trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
['C:\RVC\trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
['C:\RVC\trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
C:\RVC\sampl\mayni-model/sample.mp3->Suc.
end preprocess
start preprocess
['trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
C:\RVC\sampl\mayni-model/sample.mp3->Suc.
end preprocess
runtime\python.exe extract_f0_rmvpe_dml.py "C:\RVC/logs/mayni123"
['extract_f0_rmvpe_dml.py', 'C:\RVC/logs/mayni123']
todo-f0-78
f0ing,now-0,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_0.wav
loading rmvpe model
2023-08-25 17:02:07.0276152 [W:onnxruntime:, session_state.cc:1169 onnxruntime::VerifyEachNodeIsAssignedToAnEp] Some nodes were not assigned to the preferred execution providers which may or may not have an negative impact on performance. e.g. ORT explicitly assigns shape related ops to CPU to improve perf.
2023-08-25 17:02:07.0382099 [W:onnxruntime:, session_state.cc:1171 onnxruntime::VerifyEachNodeIsAssignedToAnEp] Rerunning with verbose output on a non-minimal build will show node assignments.
C:\RVC\lib\rmvpe.py:120: UserWarning: The operator 'aten::reflection_pad3d.out' is not currently supported on the DML backend and will fall back to run on the CPU. This may have performance implications. (Triggered internally at D:\a_work\1\s\pytorch-directml-plugin\torch_directml\csrc\dml\dml_cpu_fallback.cpp:17.)
input_data = F.pad(input_data.unsqueeze(1),(self.pad_amount, self.pad_amount, 0, 0,0,0),mode='reflect').squeeze(1)
f0ing,now-15,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_24.wav
f0ing,now-30,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_38.wav
f0ing,now-45,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_51.wav
f0ing,now-60,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_66.wav
f0ing,now-75,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_80.wav
['extract_f0_rmvpe_dml.py', 'C:\RVC/logs/mayni123']
todo-f0-78
f0ing,now-0,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_0.wav
f0ing,now-15,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_24.wav
f0ing,now-30,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_38.wav
f0ing,now-45,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_51.wav
f0ing,now-60,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_66.wav
f0ing,now-75,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_80.wav
runtime\python.exe extract_feature_print.py privateuseone:0 1 0  "C:\RVC/logs/mayni123" v2
['extract_feature_print.py', 'privateuseone:0', '1', '0', 'C:\RVC/logs/mayni123', 'v2']
C:\RVC/logs/mayni123
load model(s) from hubert_base.pt
move model to privateuseone:0
all-feature-78
now-78,all-0,0_0.wav,(149, 768)
now-78,all-7,0_15.wav,(149, 768)
now-78,all-14,0_22.wav,(149, 768)
now-78,all-21,0_3.wav,(149, 768)
now-78,all-28,0_36.wav,(149, 768)
now-78,all-35,0_42.wav,(149, 768)
now-78,all-42,0_49.wav,(149, 768)
now-78,all-49,0_55.wav,(149, 768)
now-78,all-56,0_61.wav,(149, 768)
now-78,all-63,0_69.wav,(149, 768)
now-78,all-70,0_76.wav,(149, 768)
now-78,all-77,0_9.wav,(149, 768)
all-feature-done
['extract_f0_rmvpe_dml.py', 'C:\RVC/logs/mayni123']
todo-f0-78
f0ing,now-0,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_0.wav
f0ing,now-15,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_24.wav
f0ing,now-30,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_38.wav
f0ing,now-45,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_51.wav
f0ing,now-60,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_66.wav
f0ing,now-75,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_80.wav
['extract_feature_print.py', 'privateuseone:0', '1', '0', 'C:\RVC/logs/mayni123', 'v2']
C:\RVC/logs/mayni123
load model(s) from hubert_base.pt
move model to privateuseone:0
all-feature-78
now-78,all-0,0_0.wav,(149, 768)
now-78,all-7,0_15.wav,(149, 768)
now-78,all-14,0_22.wav,(149, 768)
now-78,all-21,0_3.wav,(149, 768)
now-78,all-28,0_36.wav,(149, 768)
now-78,all-35,0_42.wav,(149, 768)
now-78,all-42,0_49.wav,(149, 768)
now-78,all-49,0_55.wav,(149, 768)
now-78,all-56,0_61.wav,(149, 768)
now-78,all-63,0_69.wav,(149, 768)
now-78,all-70,0_76.wav,(149, 768)
now-78,all-77,0_9.wav,(149, 768)
all-feature-done
['trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
start preprocess
['trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
['C:\RVC\trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
['C:\RVC\trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
['C:\RVC\trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
C:\RVC\sampl\mayni-model/sample.mp3->Suc.
end preprocess
start preprocess
['trainset_preprocess_pipeline_print.py', 'C:\RVC\sampl\mayni-model', '40000', '3', 'C:\RVC/logs/mayni123', 'False']
C:\RVC\sampl\mayni-model/sample.mp3->Suc.
end preprocess
['extract_f0_rmvpe_dml.py', 'C:\RVC/logs/mayni123']
todo-f0-78
f0ing,now-0,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_0.wav
f0ing,now-15,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_24.wav
f0ing,now-30,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_38.wav
f0ing,now-45,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_51.wav
f0ing,now-60,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_66.wav
f0ing,now-75,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_80.wav
['extract_f0_rmvpe_dml.py', 'C:\RVC/logs/mayni123']
todo-f0-78
f0ing,now-0,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_0.wav
f0ing,now-15,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_24.wav
f0ing,now-30,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_38.wav
f0ing,now-45,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_51.wav
f0ing,now-60,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_66.wav
f0ing,now-75,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_80.wav
['extract_feature_print.py', 'privateuseone:0', '1', '0', 'C:\RVC/logs/mayni123', 'v2']
C:\RVC/logs/mayni123
load model(s) from hubert_base.pt
move model to privateuseone:0
all-feature-78
all-feature-done
['extract_f0_rmvpe_dml.py', 'C:\RVC/logs/mayni123']
todo-f0-78
f0ing,now-0,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_0.wav
f0ing,now-15,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_24.wav
f0ing,now-30,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_38.wav
f0ing,now-45,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_51.wav
f0ing,now-60,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_66.wav
f0ing,now-75,all-78,-C:\RVC/logs/mayni123/1_16k_wavs/0_80.wav
['extract_feature_print.py', 'privateuseone:0', '1', '0', 'C:\RVC/logs/mayni123', 'v2']
C:\RVC/logs/mayni123
load model(s) from hubert_base.pt
move model to privateuseone:0
all-feature-78
all-feature-done
NO GPU DETECTED: falling back to CPU - this may take a while
INFO:mayni123:{'train': {'log_interval': 200, 'seed': 1234, 'epochs': 20000, 'learning_rate': 0.0001, 'betas': [0.8, 0.99], 'eps': 1e-09, 'batch_size': 3, 'fp16_run': False, 'lr_decay': 0.999875, 'segment_size': 12800, 'init_lr_ratio': 1, 'warmup_epochs': 0, 'c_mel': 45, 'c_kl': 1.0}, 'data': {'max_wav_value': 32768.0, 'sampling_rate': 40000, 'filter_length': 2048, 'hop_length': 400, 'win_length': 2048, 'n_mel_channels': 125, 'mel_fmin': 0.0, 'mel_fmax': None, 'training_files': './logs\mayni123/filelist.txt'}, 'model': {'inter_channels': 192, 'hidden_channels': 192, 'filter_channels': 768, 'n_heads': 2, 'n_layers': 6, 'kernel_size': 3, 'p_dropout': 0, 'resblock': '1', 'resblock_kernel_sizes': [3, 7, 11], 'resblock_dilation_sizes': [[1, 3, 5], [1, 3, 5], [1, 3, 5]], 'upsample_rates': [10, 10, 2, 2], 'upsample_initial_channel': 512, 'upsample_kernel_sizes': [16, 16, 4, 4], 'use_spectral_norm': False, 'gin_channels': 256, 'spk_embed_dim': 109}, 'model_dir': './logs\mayni123', 'experiment_dir': './logs\mayni123', 'save_every_epoch': 5, 'name': 'mayni123', 'total_epoch': 100, 'pretrainG': 'pretrained_v2/f0G40k.pth', 'pretrainD': 'pretrained_v2/f0D40k.pth', 'version': 'v2', 'gpus': '0', 'sample_rate': '40k', 'if_f0': 1, 'if_latest': 1, 'save_every_weights': '1', 'if_cache_data_in_gpu': 0}
INFO:torch.distributed.distributed_c10d:Added key: store_based_barrier_key:1 to store for rank: 0
INFO:torch.distributed.distributed_c10d:Rank 0: Completed store-based barrier for key:store_based_barrier_key:1 with 1 nodes.
gin_channels: 256 self.spk_embed_dim: 109
INFO:mayni123:loaded pretrained pretrained_v2/f0G40k.pth

INFO:mayni123:loaded pretrained pretrained_v2/f0D40k.pth

C:\RVC\runtime\lib\site-packages\torch\functional.py:641: UserWarning: stft with return_complex=False is deprecated. In a future pytorch release, stft will return complex tensors for all inputs, and return_complex=False will raise an error.
Note: you can still call torch.view_as_real on the complex output to recover the old return format. (Triggered internally at C:\actions-runner_work\pytorch\pytorch\builder\windows\pytorch\aten\src\ATen\native\SpectralOps.cpp:867.)
return _VF.stft(input, n_fft, hop_length, win_length, window,  # type: ignore[attr-defined]
C:\RVC\runtime\lib\site-packages\torch\functional.py:641: UserWarning: stft with return_complex=False is deprecated. In a future pytorch release, stft will return complex tensors for all inputs, and return_complex=False will raise an error.
Note: you can still call torch.view_as_real on the complex output to recover the old return format. (Triggered internally at C:\actions-runner_work\pytorch\pytorch\builder\windows\pytorch\aten\src\ATen\native\SpectralOps.cpp:867.)
return _VF.stft(input, n_fft, hop_length, win_length, window,  # type: ignore[attr-defined]
C:\RVC\runtime\lib\site-packages\torch\functional.py:641: UserWarning: stft with return_complex=False is deprecated. In a future pytorch release, stft will return complex tensors for all inputs, and return_complex=False will raise an error.
Note: you can still call torch.view_as_real on the complex output to recover the old return format. (Triggered internally at C:\actions-runner_work\pytorch\pytorch\builder\windows\pytorch\aten\src\ATen\native\SpectralOps.cpp:867.)
return _VF.stft(input, n_fft, hop_length, win_length, window,  # type: ignore[attr-defined]
C:\RVC\runtime\lib\site-packages\torch\functional.py:641: UserWarning: stft with return_complex=False is deprecated. In a future pytorch release, stft will return complex tensors for all inputs, and return_complex=False will raise an error.
Note: you can still call torch.view_as_real on the complex output to recover the old return format. (Triggered internally at C:\actions-runner_work\pytorch\pytorch\builder\windows\pytorch\aten\src\ATen\native\SpectralOps.cpp:867.)
return _VF.stft(input, n_fft, hop_length, win_length, window,  # type: ignore[attr-defined]
C:\RVC\runtime\lib\site-packages\torch\functional.py:641: UserWarning: stft with return_complex=False is deprecated. In a future pytorch release, stft will return complex tensors for all inputs, and return_complex=False will raise an error.
Note: you can still call torch.view_as_real on the complex output to recover the old return format. (Triggered internally at C:\actions-runner_work\pytorch\pytorch\builder\windows\pytorch\aten\src\ATen\native\SpectralOps.cpp:867.)
return VF.stft(input, n_fft, hop_length, win_length, window,  # type: ignore[attr-defined]
INFO:torch.nn.parallel.distributed:Reducer buckets have been rebuilt in this iteration.
C:\RVC\runtime\lib\site-packages\torch\autograd_init.py:200: UserWarning: Grad strides do not match bucket view strides. This may indicate grad was not created according to the gradient layout contract, or that the param's strides changed since DDP was constructed.  This is not an error, but may impair performance.
grad.sizes() = [64, 1, 4], strides() = [4, 1, 1]
bucket_view.sizes() = [64, 1, 4], strides() = [4, 4, 1] (Triggered internally at C:\actions-runner_work\pytorch\pytorch\builder\windows\pytorch\torch\csrc\distributed\c10d\reducer.cpp:337.)
Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
INFO:mayni123:Train Epoch: 1 [0%]
INFO:mayni123:[0, 0.0001]
INFO:mayni123:loss_disc=3.761, loss_gen=5.026, loss_fm=13.513,loss_mel=22.202, loss_kl=6.184
DEBUG:matplotlib:matplotlib data path: C:\RVC\runtime\lib\site-packages\matplotlib\mpl-data
DEBUG:matplotlib:CONFIGDIR=C:\Users\admin.matplotlib
DEBUG:matplotlib:interactive is False
DEBUG:matplotlib:platform is win32
INFO:torch.nn.parallel.distributed:Reducer buckets have been rebuilt in this iteration.

You should use dataset dir instead of dataset audio name.


Add type hints, testing suite and documentation

What is this?
This pull request represents a significant overhaul of the Typesense Python client library. The motivation behind these changes is to modernize the codebase by  adding type hints, improve type safety, enhance readability, and align the library with current Python best practices.
The expected outcome is a cleaner, more consistent API that leverages Python's type hinting capabilities, making it easier for developers to use the library correctly and catch potential errors early in the development process. Additionally, the refactored code should be more extensible, allowing for easier additions of new features in the future.
Changes
Added Features:

Type Hinting:

Comprehensive type annotations have been added throughout the codebase, improving IDE support and catching potential type-related errors at compile-time.

Testing Suite:

Full testing suite covering the whole codebase, by using both unit tests combined with actual integration tests with a Typesense server instance to ensure proper functionality throughout the library.

Pipenv Dependency Management:

Add pipenv to properly manage development dependencies and maintain compatibility with requirements.txt, by generating them from pipenv itself.

Code Changes:

In api_call.py:

Refactored ApiCall class to use type-safe methods and improved error handling.
Introduced _execute_request method for centralized request execution logic.
Introdoces RequestHandler and NodeManager classes to properly break down request logic into submodules.

In client.py:

Updated Client class to use type hints and added typed_collection method for improved type safety when working with collections, in order to infer the underlying type for the document.

In collection.py and collections.py:

Refactored to use generic types, allowing for better type inference when working with different document schemas.

In documents.py:

Overhauled Documents class to use generic types and added type-safe methods for various document operations.
Overhaul import_ method to provide easier testing, improve maintainability and adhere to SRP.

In preprocess.py:

Introduced type-safe utility functions for parameter processing.

In request_handler.py:

Created a new RequestHandler class to encapsulate HTTP request handling logic.

In node_manager.py:

Introduced a new NodeManager class for managing Typesense nodes and health checks.

Documentation Updates:

Docstrings:

Added or updated docstrings for all classes and methods, providing clear explanations of their purpose and usage.

Type Annotations:

Comprehensive type annotations added throughout the codebase, serving as both documentation and type checking.

Module-level Documentation:

Added module-level docstrings explaining the purpose and contents of each module.

Examples:

Updated and added code examples in docstrings to demonstrate proper usage of the library.

These changes collectively represent a significant update in the library's structure, type safety, and documentation.
PR Checklist

[x] I have read and signed the Contributor License Agreement.

This is awesome and much needed - thank you! I've been patching the library literally inside the virtualenv just to not have to look at type errors.


Get the referral link

We need to get the referral link for the user, so he or she can share it with friends.

I think the referral code makes sense to be stored in the user object, and so returned with the rest of the user data.
The rest of the URL should be constructed on the front-end, because it is the front end which defines what the full URL should be.
Concretely for this example, user contains:
{
  ...
  referral_code: user12,
  ...
}

And I think the front end can get the current url from this.$route, which should then look something like https://venue.volentix.io/signup?referer=<code>

I confirm that I've added referral_code to the api/retrieve/user/ endpoint.
About the signup endpoint, I'm sending an email with a URL like  /signup?code=<referral_code>.

@alexdashkov Yes you're right, I see it in that call. Thanks for the info.
@Lyncis The retrieve/user call is done as part of the load user data. So you should find it in the Nuxt store at this.$store.state.user.referral_code.

ok, looks good. Going to try it

Everything is working, thank you


MBH will spell out capitalized letters when two or more begin a word.

Instead of pronouncing BOtzerker as botzerker, MBH will pronounce it as B O tzerker.

You know this may be better handled by investigating SSML or Speech Synthesis Markup Language.  I don't know if IRC will let all of that markup through.  But it would cool to try.

Well MBH is already doing this. I was looking at it as a bug. I thought MBH should pronounce BOTzerker as botzerker and NOT as B O T zerker.


Query Loading .pcd files for Dataset

Hi,
I am quite new to this field (undergrad).  From what I can tell, the result of all the four ScanNet files that are needed are loading xyz, rgb, labels and instance.
I would like to make my own dataset using Hitatchi Automotive Labs editor, which produces labelled .pcd files (which are basically an array of x, y, z, r, g, b, label, instance) - seems perfect to go into PointGroup.  However, I'm a bit lost in the whole code structure.
Would appreciate if anyone could tell me where/how I could do away with the ScanNet format and load .pcd files instead?
Thank you for your response.

managed to create my own loader.


chore(deps): update terraform terraform-ibm-modules/key-protect-all-inclusive/ibm to v4.6.0

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/key-protect-all-inclusive/ibm (source)
module
minor
4.4.2 -> 4.6.0

Release Notes

terraform-ibm-modules/terraform-ibm-kms-all-inclusive (terraform-ibm-modules/key-protect-all-inclusive/ibm)
v4.6.0
Compare Source
Features

added kp_private_endpoint and kp_public_endpoint outputs  (#404) (258bda5)
updated Key Protect module to version v2.5.1. This version will cause an expected update in place on the Key Protect instance if you have one provisioned. See v2.5.1 release notes for details. (#404) (258bda5)

v4.5.0
Compare Source
Features (#400) (0148340)

The following variables have been removed force_delete, force_delete_key_ring, existing_key_map, as its now possible to pass them as part of a new input variable list called keys. This has replaced the old variables key_map and existing_key_map as it supports creating key in existing and new key rings using a boolean. See updated usage on how to consume module.
Current infrastructure will not be impacted when updating to this version if migration to new usage is done correctly. For example:
In previous versions:
key_map = {
  "key-ring-name-1" = ["key-1", "key-2"]
}

existing_key_map = {
  "key-ring-name-2" = ["key-3", "key-4"]
}

In this version:
keys = [
  {
    key_ring_name = "key-ring-name-1"
    keys = [
      {
        key_name = "key-1"
      },
      {
        key_name = "key-2"
      }
    ]
  },
  {
    key_ring_name = "key-ring-name-2"
    existing_key_ring = true
    keys = [
      {
        key_name = "key-3"
      },
      {
        key_name = "key-4"
      }
    ]
  }
]

In addition, the output of the module has changed to now only have one "keys" output. below is an example of how the output has changed:
Older versions:
module.kms_all_inclusive.keys["key-ring-name-1.key-1"]
module.kms_all_inclusive.keys["key-ring-name-1.key-2"]
module.kms_all_inclusive.existing_key_ring_keys["existing-key-ring.key-3"]
module.kms_all_inclusive.existing_key_ring_keys["existing-key-ring.key-4"]

This version:
module.kms_all_inclusive.keys["key-ring-name-1.key-1"]
module.kms_all_inclusive.keys["key-ring-name-1.key-2"]
module.kms_all_inclusive.keys["existing-key-ring.key-3"]
module.kms_all_inclusive.keys["existing-key-ring.key-4"]

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

An update in place happens (as expected and documented with the key-protect-all-inclusive release notes)
TestRunAdvancedExampleUpgrade 2024-02-04T21:54:39Z command.go:185:   # module.key_protect_all_inclusive.module.key_protect[0].ibm_resource_instance.key_protect_instance will be updated in-place
TestRunAdvancedExampleUpgrade 2024-02-04T21:54:39Z command.go:185:   ~ resource "ibm_resource_instance" "key_protect_instance" {
TestRunAdvancedExampleUpgrade 2024-02-04T21:54:39Z command.go:185:         id                      = "crn:v1:bluemix:public:kms:eu-de:a/abac0df06b644a9cabc6e44f55b3880e:e52286fe-d39d-4f58-a329-317e43514f1e::"
TestRunAdvancedExampleUpgrade 2024-02-04T21:54:39Z command.go:185:         name                    = "redis-advanced-upg-smzgnw-kp"
TestRunAdvancedExampleUpgrade 2024-02-04T21:54:39Z command.go:185:       + parameters              = {
TestRunAdvancedExampleUpgrade 2024-02-04T21:54:39Z command.go:185:           + "allowed_network" = "public-and-private"
TestRunAdvancedExampleUpgrade 2024-02-04T21:54:39Z command.go:185:         }
TestRunAdvancedExampleUpgrade 2024-02-04T21:54:39Z command.go:185:         tags                    = []
TestRunAdvancedExampleUpgrade 2024-02-04T21:54:39Z command.go:185:         # (33 unchanged attributes hidden)
TestRunAdvancedExampleUpgrade 2024-02-04T21:54:39Z command.go:185:     }

This has nothing to do with this module, and no other errors are reported with the upgrade, so a SKIP UPGRADE TEST commit will be created.

/run pipeline

:tada: This PR is included in version 1.4.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fixup Liferay URL generation;JSON decoding

Hello @ivan-c! Thanks for submitting the PR.

In the file portal/views/portal.py, following are the PEP8 issues :

Line 1104:80: E501 line too long (83 > 79 characters)
Line 1107:23: E231 missing whitespace after ':'
Line 1125:80: E501 line too long (83 > 79 characters)
Line 1145:80: E501 line too long (83 > 79 characters)


Wave XI ship icons

Wave XI is announced; we'll need ship icons for

Auzituck Gunship
TIE Aggressor
Scurrg H-6 Bomber

Also for the C-ROC:

C-ROC Cruiser
Container Token (normal and inverted)

I don't think the available images (only "card fans") are good enough to use at the moment. I will get to work when we have revealed ship cards for each ship type.

Scratch the Container Token, looks like it's gonna be a gameplay-placed obstacle like the Debris token. The Jabba card does confirm an Illicit token though so we'll need that and an inverted version.

Is this adequate?

You'll probably want these too...

Are those images good enough or do you need them flatbed scanned so there is no perspective skewing?

If it isn't, here's a scan:

I think all the necessary icons are available now, but I don't have time to fix them at the time being. Others are welcome to do so, otherwise I will try to get them done when I get time.

Here are a few higher resolution scans of the ship shapes if they help.    I'd be happy to create the vector outlines, what app should I use?  email me at<EMAIL_ADDRESS>and I'll give it a go.

I just took my first go using FontForge.  I put the CROC in C, the Auzituck in @  the Aggressor in the tilde ` and the H-6 Scurrg in H.   No clue if they will help or not.. feel free to delete or clean up the vector work.
x-wing-ships-sk.ttf.zip

Awesome job, this'll do great for me while waiting on the existing font. I can fix sizing per ship in the app I use them in. :D

Yeah.  I think I made them too big.   My first time using FontForge.

OK.. I found the TRANSFORM feature to scale the glyph.   Here is how they look and an uploaded copy.

x-wing-ships-SK2.ttf.zip

Unfortunately there is still a problem with the four new icons. All older icons are rectangular (3x4), but the new ones are square. Could it be fixed?

Spending more time with the app.. I see how you started the ships below the baseline.. I moved the ships down and to the left to hopefully be more consistent with all the other..   And, now that I look at it, the C-ROC at R doesn't make as much sense as having it at 5   The 5th huge ship.
Attached is a tweaked font.
x-wing-ships-SK4.ttf.zip

So just to clarify: C-ROC is "5" ?

Think so.  On the update I just uploaded.   Croc should be 5 and I resized and reset the baseline on them all.

Here's an example of your new glyphs with the originals. Works great!


RDF research

-Has no view for people
-can easily shape the graphs
-is used instead of a distributed database
-easier information structure
-can insert RDFA into HTML and then convert to any RDF like json, xml
# RDF - Examples of Use
Describing properties for shopping items, such as price and availability
Describing time schedules for web events
Describing information about web pages (content, author, created and modified date)
Describing content and rating for web pictures
Describing electronic libraries


HAWQ-210. Improve data locality by calculating the insert host.

Currently, data locality is based on a heuristic greedy algotirhm.
First consider continue blocks for a vseg and then non continue blocks and finally non local blocks.
But when a file contains several continue blocks but each vseg could only process one blocks due to avg size. In this case continue blocks are assigned to different vsegs one by one, and they are to be treated as non continue blocks.
In this improvement, we try to add continue infomation to help choosing the right vseg in non continue blocks allocation stages. The main idea is to go through the blocks in a file, and find the host which include the max number of blocks in this file. We call this host as INSERT HOST. When assigning non continue blocks, we prefer INSERT HOST to other hosts when they are all local read.

looks good

Looks good


GH-2463: Provide smart contract access to associated keys that signed a deploy

Closes #2463
This PR adds list_authorization_keys to the contract_api / wasm ffi, allowing smart contracts access to the set of associated AccountHashes that signed a deploy.
This is necessary for certain types of more advanced smart contracts that utilize multi signature accounts and need to impose some form of role based security in their app logic. For instance, a smart contract that has defined a "clerk", a "supervisor", and "registrar" roles and contains certain entrypoints or operations that are only allowed if one or more signatories of specific role(s) have signed a deploy.

good start, quick turn around, but see notes

My comment (https://github.com/casper-network/casper-node/pull/2468#discussion_r769119376) still stands. Why are we not exposing keys instead? They're more valuable to the smart contracts than hashes (one can always go key -> hash but not the other way around).

My comment (#2468 (comment)) still stands. Why are we not exposing keys instead? They're more valuable to the smart contracts than hashes (one can always go key -> hash but not the other way around).

Consistency with other associated keys APIs with _key suffix. There was also an idea to expose Key::Accounts (as the function has _keys suffix) but it's the same issue

My comment (#2468 (comment)) still stands. Why are we not exposing keys instead? They're more valuable to the smart contracts than hashes (one can always go key -> hash but not the other way around).

Consistency with other associated keys APIs with _key suffix. There was also an idea to expose Key::Accounts (as the function has _keys suffix) but it's the same issue

If exposing keys is superior functionality we shouldn't disregard it b/c we've exposed hashes until now.

My comment (#2468 (comment)) still stands. Why are we not exposing keys instead? They're more valuable to the smart contracts than hashes (one can always go key -> hash but not the other way around).

Consistency with other associated keys APIs with _key suffix. There was also an idea to expose Key::Accounts (as the function has _keys suffix) but it's the same issue

If exposing keys is superior functionality we shouldn't disregard it b/c we've exposed hashes until now.

Can we address this is in separate work perhaps? I have some concerns with exposing casper_types::PublicKey in current shape to Wasm

I agree with @goral09 here: https://github.com/casper-network/casper-node/pull/2468#issuecomment-998931886
@mpapierski @piotr-dziubecki can we create a ticket and plan for this?

@mpapierski any actions you need to take before merging the PR?

bors r+

@mpapierski, any actions you need to take before merging the PR?

I just notified Piotr about exposing PublicKeys in future work (2.0.0 perhaps). Merging now


update 1.0.5

☆ Snowflake-ml-python 1.0.5 Update ☆
Jira Ticket
Upstream
Dependencies
Changes

Updated version number and sha256
Updated pinnings on dependencies

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:22: patch_unnecessary: patch should not be in build when source/patches is not set
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:21: patch_unnecessary: patch should not be in build when source/patches is not set
Errors were found

This seems like a Snowflake package. @Arishamays1 could you please follow these guidelines? They are still under review but almost complete. Please ping me if you encounter any errors or unclear steps.

Note: this is NOT a Snowflake package, and it goes to defaults.

Linter check found the following problems:
The following problems have been found:
ERROR: clone/recipe/meta.yaml:22: patch_unnecessary: patch should not be in build when source/patches is not set
Errors were found


Word-based pointer APIs

The following APIs circumnavigate uninitialized NBKDoubleWidth pointee access (#67).
New UnsafePointer APIs
public func load <H>(_ word: UInt.Type, at index: Int) -> UInt where Pointee == NBKDoubleWidth<H>

New UnsafeMutablePointer APIs
public func store<H>(_ word: UInt,      at index: Int)         where Pointee == NBKDoubleWidth<H>
public func load <H>(_ type: UInt.Type, at index: Int) -> UInt where Pointee == NBKDoubleWidth<H>

Hm. I do wonder, however, if the following is allowed. In that case, these may not be required:
let value = Int256.uninitialized { pointer in
    for index in  Int256.indices {
        pointer.pointee[index] = UInt.zero
    }
}

Hm. I suppose the following might count as a pointee read:
set {
    let byteOffset = BitPattern.endiannessSensitiveByteOffset(unchecked: index)
    Swift.withUnsafeMutablePointer(to: &self) { pointer in // ⚠ inout pointee
        UnsafeMutableRawPointer(pointer).storeBytes(of: newValue, toByteOffset: byteOffset, as: T.self)
    }
}

These APIs are (or would be) made obsolete by (#71).


SkyDock / containers unable to resolve under Centos 7.1 Docker 1.7.1

That issue similar to that https://github.com/crosbymichael/skydock/issues/53.
I followed setup part from README.md and the test via
docker run -t -i crosbymichael/redis-cli -h redis1.redis.dev.docker

is not working.
Unfortunately I could not fix it via suggested command
iptables -A INPUT -s <IP_ADDRESS> -d <IP_ADDRESS> -p udp -m udp --dport 53 -j ACCEPT
Any suggestions?

I fixed it by  flushing all rules and chains in iptables. As it was suggested in #53.
To my surprise Centos 7 with "minimal install" setup adds something to iptables... Any way.


EDDI Reports Most (All) Planets as Not Suitable For Landing When They Are

I am finding that EDDI (latest) reports planets that are suitable for landing as not-suitable.

duplicate of https://github.com/EDCD/EDDI/issues/107

for issues with EDDI 2.3.1 and beyond, please post issues to https://github.com/EDCD/EDDI. thanks!


Data Race - Subscriptions not concurrent safe

Error happens in
https://github.com/functionalfoundry/graphqlws/blob/master/subscriptions.go#L157
Seems like the subscription manager map is not concurrent safe.

I fixed that by converting the map to sync.Map.  It's a map of interface{} which you have to dynamically check outside compile time if they're the right type. You can find the solution here
https://github.com/exapsy/graphqlws/blob/master/subscriptions.go
It actually solved a data-race problem of mine which crashed the entire frontend which was supported by the golang graphql server, which is nice.
But I think it's an ugly solution to serve to the public so I wont make a PR unless someone thinks it's alright. From what I see this repository's maintainers are inactive anyways so a PR probably wouldn't serve anyone :P
But whoever wants to utilize this solution into their code they're free to do so. :)