Crash with Advanced Rocketry

The Server crashes when a player tries to build a rocket.
Advanced Rocketry version: 2.0.0-10
Forge: 36.1.13
Chocolate Version: 1.3.0-1.16.4
Stacktrace: https://gist.github.com/Seniorendi/184038f7f0150858a43feed517b7cfe3
In the log is a text with "Please Report this to Chocolate!" this is the reason why I'm here.

Right. So I know exactly what's going on here.
Chocolate makes an assumption - that BiomeContainer should always be given a Registry<Biome>, in order to properly encode biome IDs using the runtime dynamic registry. Vanilla always does this, but does not require this. This exception is indicative that Advanced Rocketry is breaking that assumption. In particular, (for example) here:
https://github.com/Advanced-Rocketry/AdvancedRocketry/blob/b13546cf86fac60c43a8fe431b5d3a3c0eb8cd8f/src/main/java/zmaster587/advancedRocketry/util/StorageChunk.java#L134
Now, generally, I would hope that Advanced Rocketry would be able to pass in the actual biome registry - however taking a brief look I have some concerns in the way that might be handled. Ideally, by passing in:
ServerLifecycleHooks.getCurrentServer().registryAccess().registryOrThrow(Registry.BIOME_REGISTRY)

Now, assuming that they don't fix this in said form, that leaves two options. One, is that I would need to very carefully special case biome containers constructed with weird registries. This would be a massive pain.
The other option, which I would assume you are more interested in, would just be to remove chocolate. The reason being, you are using a Forge version (36.1.13) which has actually (finally) fixed the primary bug Chocolate was created for. So unless you really need MC-197616 fixed, you very likely won't be seeing any issues just by removing Chocolate.

The other option, which I would assume you are more interested in, would just be to remove chocolate. The reason being, you are using a Forge version (36.1.13) which has actually (finally) fixed the primary bug Chocolate was created for. So unless you really need MC-197616 fixed, you very likely won't be seeing any issues just by removing Chocolate.

Oh, thank you for your advice!


[Component name] [description of the issue]

the bug
I'll be honest this may not be a bug, but a lack of knowledge from my part.
According to the Documentation
I should be able to pass data attributes to a datepicker like this:
<div
  class="relative"
  id="{{id}}"
  data-te-datepicker-init
  data-te-input-wrapper-init
  data-te-title="Selecione a Data"
  data-te-ok-btn-text="OK"
  data-te-clear-btn-text="Limpar"
  data-te-months-full="['Janeiro','Fevereiro','Março','Abril','Maio','Junho','Julho','Agosto','Setembro','Outubro','Novembro','Dezembro']"
  data-te-cancel-btn-text="cancelar">
... more code after this

However I'm getting the following error:
ERROR Error: DATEPICKER: Option "monthsFull" provided type "string" but expected type "array".
    at tw-elements.es.min.js:80:13
    at Array.forEach (<anonymous>)
    at N (tw-elements.es.min.js:77:18)
    at Gg._getConfig (tw-elements.es.min.js:5398:8)
    at new Gg (tw-elements.es.min.js:5330:94)
    at tw-elements.es.min.js:10524:15
    at Array.forEach (<anonymous>)
    at Jm (tw-elements.es.min.js:10522:43)
    at tw-elements.es.min.js:10527:20
    at Array.forEach (<anonymous>)

Is the component not able to convert the array or I'm the one passing data the wrong way?
To Reproduce
Steps to reproduce the behavior:

Try to create an datepicker, the simple example will suffice
Try to pass options that are array via HTML5 data attributes
See error

Expected behavior
The months names should be translated, as seen in the array
Actual behavior
The data-te-months-full, when passing an array says it's a string
Desktop (please complete the following information):

OS: Ubuntu 20.04
Browser Chrome

Hi, try passing the array with use of javascript like in this example:
https://tailwind-elements.com/docs/standard/forms/datepicker/#section-translations

I have updated the snippet for datepicker with translations but I am not sure that it will solve your issue. The problem is that I cannot recreate the silent failing that you are experiencing.
Could you describe what do you mean by that? Does it only happen when you are adding the translations?

I didn't see that earlier but the issue may be that you are initing the datepicker with data attributes and js at the same time. You have data-te-datepicker-init that will init the datepicker automaticaly after calling the initTE method. Then the second time with JS and adding the translations. Try removieng the data-te-datepicker-init and see whether the issue still occurs.


generator crashes - can't figure out why

I'm running a command line script but I get the same thing happening if I run it from within Scribus. The output is:
`$ ~/GenOfficers.sh Committees
14:41:07 - ScribusGenerator - INFO: ScribusGenerator initialized
14:41:07 - ScribusGenerator - INFO: Generating all files for Committees.sla in directory /home/garydale/mnt/archives/2021/Lions Club/District/Directory/
14:41:07 - ScribusGenerator - INFO: parsing scribus SLA file /home/garydale/.scribus/templates/Lions Club/Committees.sla
14:41:07 - ScribusGenerator - INFO: source document consumes 1 data record(s) from 104.
14:41:07 - ScribusGenerator - INFO: variables from data files: ['Position', 'Lion', 'E-Mail', 'Phone', 'Home-Club']
14:41:08 - ScribusGenerator - ERROR:
error: Traceback (most recent call last):
  File "/home/garydale/.scribus/scripts/ScribusGenerator-python3/ScribusGeneratorCLI.py", line 171, in <module>
    generator.run()
  File "/home/garydale/.scribus/scripts/ScribusGenerator-python3/ScribusGeneratorBackend.py", line 227, in run
    tmpElt = ET.fromstring(outContent).find('DOCUMENT')
  File "/usr/lib/python3.9/xml/etree/ElementTree.py", line 1347, in XML
    parser.feed(text)
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 1, column 34947
`

I've used the script to successfully generate a different file, and, as per above, it happens without the script too. I've loaded the .csv file into Calc and re-saved it, so I'm sure that it's valid CSV. I even replaced some square brackets with () in case that was an issue - it wasn't.
I've triple checked my variables and they seem to be OK. The only thing I'm doing different in this template is I'm using %SG_NEXT-RECORD%, but I still get an error if I remove it.
I'm hoping someone can tell me what the problem might be.
Here's a sample of the .csv file:
"Position","Lion","E-Mail","Phone","Home-Club"
"District Governor [DG]","Person Dg","person1@gmail.com","999 999-9999","Toronto Centennial"
"Immediate Past District Governor [IPDG]","Person Ipdg","person2@gmail.com","888 888-8888","Thistletown"
The template lists the information with multiple records per page but also adds PDF annotations - a dummy to later be used to link to a biography page, and mailto: and tel: web links.
After further digging - by removing various elements and retrying, I've narrowed it down to a text element shown in the attachment. I can't see why it should cause a problem but maybe you can....

I eventually just deleted the text boxes and recreated them, It worked. I can't see any difference between the original and the recreated one. However, when I went back and duplicated the entire section (text box and overlaying PDF annotations) in bulk to fill an entire page the problem returned.
I created the initial page as a test with only 5 text boxes on it (and 4 %SG_NEXT-RECORD% boxes) plus the PDF annotations. When I removed the 5 text boxes then created a new one that I copied & pasted 4 times, the generator worked. When I then took the bottom 4 boxes + NEXT-RECORDs, etc., and copied and pasted them as a block, the problem returned.
It appears that there is something in the bulk copy & paste to duplicate sections that the generator doesn't handle.
In my next test, I removed just the (new - I left the 5 that were working [see two paragraphs above]) text boxes then selected just the 5 text boxes, copied and pasted them back. That worked. Unfortunately, the SG_NEXT-RECORD boxes weren't being acted upon.
In an attempt to fix this, I removed the boxes and added the SG_NEXT-RECORD to the end of each text box. Unfortunately that got me back to the error when I copied the text box. Removing the copied items, I tried again - with just one text box on the page. It worked, but the SG_NEXT-RECORD was executed before the pdf annotations.... so those links contained information from the next record (because there is an SG_NEXT-RECORD, the first page contained the information from the first record while the annotations had information from the second, while the second page showed the information from the third record...).
All subsequent efforts to resolve this, including starting with a fresh document, have simply led to generator crashing. I tried rebooting but that didn't solve things. I tracked it down to the presence of %VAR_Position% anywhere in the text box. It doesn't seem to be the fact that it's the first column - inserting a dummy column didn't help - or the name of the column. Nor can I see anything in the contents to cause a problem.
I also don't get why it's happening now and not earlier. I haven't touched the generator install nor the CSV file contents except to change the column headings (as above). I've started with a fresh .sla file to use as the template...
After multiple more tries, I finally got the thing to work. I can't see any significant difference in the template that worked versus the various ones that didn't. I started with the VAR_Position omitted and got a few records per page with the SG_NEXT-RECORD at the start of the second and subsequent text boxes. After that worked, I was able to add VAR_Position back in without it complaining.
I was also able to bulk copy & paste without generator throwing error messages. The only thing that went wrong was on the first generated page, each text box showed up twice with the same data in the same position but different levels. This didn't happen on the second and subsequent pages.

Seems to be a problem with the text you want to insert rather than the variable names and/or position etc - I had a similar issue once, and it sounds a lot like what I encountered back then .. for me, it was a "middot" (or interpunct, see wikipedia) character causing trouble.

Hello Gary.
Sorry for not answering this issue earlier, I just was not very active in GitHub and may have missed the notification.
The initial problem may have been with a non printable character in the template (quite likely from the error log you report), or indeed with the multiple copies mechanism, that might not be failproof.
Could you please share a version of the template that breaks? I cannot seem to reproduce the issue.
Thanks, and sorry again for the delay.

This seems connected to #138

I'll freeze this issue since cannot reproduce. Hoping it was indeed just an issue with a non-printable character that you solved by removing the faulty paragraph and creating it anew.
Please re-open attaching the problematic template if the issue still arises with the updated ScribusGenerator script !


[API breaking change] add prefix change indicator

closes #4068
documentation will be added as part of #4070
I'm open to better suggestions for a name to indicate prefix change

@itaiad200 - please, no more colors in the diff screen. The UI shows a folder icon, indicating that this is a prefix and not a single object. I would argue that this enough.

@itaiad200

Currently, The UI shows the same color for prefix as for change. I don't think we should add another color for it, maybe add text with "changes under this prefix" but I'm not sure it's necessary because it has a change color and folder icon.
Done
There isn't an explanation on the docs about the current diff behavior, on #4070 I'm adding a diff section on the docs that we can explain there in detail. unless you have an idea where to document it for now.


[cURL] ...

Extension – cURL
The ability to specify headers other than those suggested by the extension.
Describe the feature and the current behavior/state.
There are some custom headers/non standard headers for an internal API I would like to be able to set however I can only seem to select from the list of headers provided by the extension rather than being able to type in any manually.
Who will benefit with this feature?
I would imagine most people would benefit from being able to specify headers other than those provided by the extension.
Any Other info.

I would also really appreciate this feature


Scrape GSOC Project information

Describe the feature
Going through GSOC projects can be overwhelming because of large number of organizations and the specific technology requirements. By scraping GSOC website, the following information can be used:

Name of the organization
The tech stack specification
Topics regarding the project
Past project information

Add ScreenShots
Following information can be generated about the organization:

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC 23 contributor
[X] I want to work on this issue

Hey, it is an event-specific idea. We are looking for more generalization.


[TASK] Fix all-time threshold history table

Overview
The current Network Thresholds History filtered on all-time's horizontal axis reads 'Month' when it should read 'Sessions'. We should also include all sessions.

Task Checklist

[ ] Update to fix horizontal axis

Closed in #813


Clarify setup when cloneing repo in readme

The setup guide currently doesn't mention cloning at all, I think someone tempted to clone the repo might forget to install the dependencies. I don't even remember how to do that anymore.

Should be fixed with 332919b

I've changed the structure a bit in #51


Add graphical tool for KDE

Hello There!
I just tried this for fun on my Lenovo Thinkpad X1 Yoga and it worked really well, thanks!.
I have an idea on how to improve this project: How about adding a KCM (KDE configuration module). This  could be in a sub directory so that users can install it, but don't have to.
This way the users can configure the config file graphically with the native tools.
Edit: It is almost finsihed, see https://github.com/alex1701c/linux_detect_tablet_mode/tree/master/kde.

Hi. This project was meant for a minimalistic setup with a window manager, not as something for consumption by KDE or Gnome. That's why it's just a simple ruby script. Also, I'm not a C++/Qt developer, so I don't think there's a reason to have it in this repository, as I won't be able to maintain it. But I don't see why your project couldn't coexist with mine as two separate projects.


IF search bad Name

One-line fix (plus a test) of a bug in the Nomenclature "IF web searcjh url. See #1925
Fixes #1925

Deployed  deploy-2024-02-22-23-56 -> deploy-2024-02-22-23-56


Hacktober Feature Request: Rename Learn .NET page and link

Describe the feature

Rename Learn .NET page to Learn
Rename Learn .NET link to Learn

Advantages

Means we can add resources for learning Azure as well as .NET in this page

Acceptance Criteria
Functional and non-functional criteria that should be met by this work

[ ] Both link in navigation bar and page are called "Learn"

@wordshaker Can I do this ?

Thank you for your contribution @Augilar


Fix issue #48

Fixed digits:int goes scientific at 13 digits

Coverage decreased (-0.003%) to 89.369% when pulling 40859288c879140cedf8b077b15de278da2eb53a on fix/digits-gt-13 into 69b7cbf535c869e51b5f1e2f1fda429926ebe5eb on master.

Coverage decreased (-0.003%) to 89.369% when pulling 40859288c879140cedf8b077b15de278da2eb53a on fix/digits-gt-13 into 69b7cbf535c869e51b5f1e2f1fda429926ebe5eb on master.

Coverage decreased (-0.003%) to 89.369% when pulling 40859288c879140cedf8b077b15de278da2eb53a on fix/digits-gt-13 into 69b7cbf535c869e51b5f1e2f1fda429926ebe5eb on master.


Tr

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing


OSError: libtorch_cpu.so: cannot open shared object file: No such file or directory

❓ Questions & Help
When I run import Data, it shows the errors 'OSError: libtorch_cpu.so: cannot open shared object file: No such file or directory'
my code is following:
`import torch
from torch_geometric.data import Data
edge_index = torch.tensor([[0, 1, 1, 2],
[1, 0, 2, 1]], dtype=torch.long)
x = torch.tensor([[-1], [0], [1]], dtype=torch.float)
data = Data(x=x, edge_index=edge_index)

Data(edge_index=[2, 4], x=[3, 1])`

How to fix?

This is caused by the PyTorch version is no match.

What pytorch version should it be? Mine is 1.4.0 and cuda 10.1:
python -c "import torch; print(torch.__version__)"
> 1.4.0
python -c "import torch; print(torch.version.cuda)"
> 10.1


change: cross-spawn-async to cross-spawn

Can you explain why you want to see this PR merged?

I guess we can merge it since cross-spawn-async is deprecated now. They've removed the sync stuff that prevented us from using it before.

I guess we can merge it since cross-spawn-async is deprecated now. They've removed the sync stuff that prevented us from using it before.

exactly


Add a new node with the ansible configuration

I've a running cluster that I setup so easily with the Ansible playbook (thank you very much!), but now the cluster is growing and I need to add new nodes.
If I just add it in the [nodes] list of the inventory file, then it'll reinstall the whole cluster (tried it, on a staging cluster thankfully). Is there a way to just add a new node?
Thanks you very much.

I guess you can try to run ansible-playbooks manually and add "--limit" parameter to the command. Something like this:
ansible-playbook -i inventory cluster.yml --tags=nodes --limit=NEW_NODE

Please let us know what does/doesn't work....    I'm a little concerned we do some per node generation of access tokens in the kubernetes role and I have no idea how the working with --tags and --limit...

But re-running against the entire cluster, should work. It should not break, harm, or destroy anything else. If it does, that's a bug.

Without the --limit option, all the custom Kubernetes & Docker configurations were replaced (ie in the systemd services definition). Maybe the ideal would be to actually updates these configuration in the Ansible playbook.

You mean that you updated docker/kube outside of ansible and then re-ran ansible which undid your custom changes? Running this playbook a second time should leave the cluster unchanged.

Exactly what I did and it revert everything :smiley:

Might I suggest doing those docker customization in ansible (but yes, sorry about that, how did --limit work?)

Yes I'll probably do the updates on a fork of this repository, that might be better :)
And actually didn't try the --limit because my cluster was already broken and don't really want to do that again for now.
I'm leaving this issue opened in case somebody else can add details if they experiment the same problem.

@zaa, @eparis: after trying the --limit option, it looks like it's not working because the token is not generated on the master node:
TASK [node : Get the node token values] ****************************************
failed: [new-node -> master] => (item=system:kubelet) => {"failed": true, "item": "system:kubelet", "msg": "file not found: /etc/kubernetes/tokens/system:kubelet-new-node.token"}

I agree with the original comment, yes, the Ansible installer is very nice.  I am wondering about the status of adding a node.
I have not tried yet but I wondered about how it was handled by the OpenShift/Origin Ansible installer.  They respect a "new_nodes" section addition to the inventory file:
[new_nodes]
node3.example.com openshift_node_labels="{'region': 'primary', 'zone': 'west'}"
Then once complete the line is moved to [nodes].


[release-2.5] Manual cherry-pick of #119

Manual cherry-pick of:

#119

No issue was created. Test automation related -- no QE required.


Add OpenBSD support to libmachine/crashreport

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "crashreport-openbsd" git@github.com:nogoegst/machine.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

LGTM


Form and button style error

As I can see all the form and many elements inside have style error. Could you please take a look?
https://jekyller.github.io/jasper2/a-full-and-comprehensive-style-test

@quyleanh  They look good for me, but let me know if this is still an issue for you!

Actually I don't know if this is OK. Could you please take a look? Thank you.

@quyleanh Ohh I see what you mean now. The placement of the boxes and labels is weird indeed... this was copied as it was based on the Casper theme by the Ghost folks. They are now running version 4 of the theme but it still looks like that 😄
See https://demo.ghost.io/style-test/

Thank you for your kind reply.
I think the default one has no custom CSS. Understand now.


Server codegen could provide From Trait for operations' error types

Each operation gets a dedicated error enum generated making error handling quite verbose with the current lack of From trait implementations.
Example when using the following smithy model:
@httpError(500) @error("server")
structure InternalServerException { message: String }

operation Op1 {
    input: Input,
    output: Output,
    errors: [
        InternalServerException,
    ],
}

The generated code will have in errors.rs:
#[non_exhaustive]
#[derive(std::clone::Clone, std::cmp::PartialEq)]
pub struct InternalServerError {
    pub message: std::option::Option<std::string::String>,
}

#[derive(std::fmt::Debug)]
pub enum Op1Error {
    InternalServerError(crate::error::InternalServerError),
}

Having the From<InternalServerError> trait there would be nice (and should always be possible since the Enum is created from a list of error types in smithy):
impl From<InternalServerError> for Op1Error {
  fn from(e : InternalServerError) -> Self { Self::InternalServerError(e) }
}

This is something we are already discussing and this issue description sums it up perfectly. I am not 100% sure about the implementation yet, but this is definitely something we will be working on in the short term. Thanks for reporting this.


Group WebJobs functions by containing job

This is a request for a usability improvement for the interface to WebJobs functions at https://mysite.scm.azurewebsites.net/azurejobs/#/functions
I currently have 6 continuous WebJobs executables deployed on a single App Service. Each executable has between 1 and 20 different exposed functions. Browsing through the list of functions via the web UI at the above URL is painfully slow and the functions aren't organized in any useful manner.
To improve the user experience, please group the functions by executable. Allowing me to pick an executable/job and then listing the functions would help tremendously. Alternatively, if the paging speed could be improved, that would be great first step, if nothing else could be done. Right now I often have to wait an entire minute for the next page of functions after clicking the Next button.
Thanks

This actually pertains to the WebJobs SDK which is quite separate from Kudu. Can you open on https://github.com/Azure/azure-webjobs-sdk/issues instead? Thanks!

Done. Thanks for pointing me in the right direction.


Is there a way to pass a generic Type at runtime?

I'm using AlamofireObjectMapper to deserialize json responses from APIs, but I am struggling to write a generic function where I can pass an object at runtime.
If I have 3 objects A, B, C, right now I have to create 3 functions to deserialize in A, B, C.
I would like to only have 1 function that accept as a parameter the object type and pass it to the object mapper.
I've tried with Mirroring, and using the generic T, but I always get the error "is not a type".
some examples:
 func test<T>(cls: T.Type){

        let x = Mirror(reflecting: cls)
        Alamofire.request(.POST, endpoint).responseObject { (response:  Response<x, NSError>) in

            guard response.result.error == nil
                else {
                    return
            }
        }
    }

 func test<T>(cls: T.Type){

        Alamofire.request(.POST, endpoint).responseObject { (response:  Response<cls, NSError>) in

            guard response.result.error == nil
                else {
                    return
            }
        }
    }

Any hint? Thanks

I think all you're missing is that T must implement Mappable. Something like this should work:
func test<T: Mappable>(obj: T.Type){
        Alamofire.request(.POST, endpoint).responseObject { (response: Response<[T], NSError>) in

        }
    }

True, that was easy, I should have investigated more. Thanks a lot.

I think all you're missing is that T must implement Mappable. Something like this should work:
func test<T: Mappable>(obj: T.Type){
        Alamofire.request(.POST, endpoint).responseObject { (response: Response<[T], NSError>) in

        }
    }

How to implement this generic with Alamofire 4 ?
 {

        Alamofire.request(urlStr, method: method, parameters: params, encoding: encoding, headers: header).responseJSON { (response: DataResponse<T>) in

        }
    }

The error :

Cannot convert value of type '(DataResponse) -> ()' to
expected argument type '(DataResponse) -> Void'

Please advise.

@nizzam  I am dealing with the same issue.Did you find a way to do it with Alamofire 4. thanks.

Here what I'm doing.
/// For `API-Result`
enum APIResult<T> {
    case Success(T)
    case ErrorCallback(ErrorResponse)
    case FailureCallback(ErrorFailure)
}

func handleResponse<T: Codable>(result: Result<Response, MoyaError>,
                                entity: T.Type,
                                completion: @escaping(APIResult<T>)->Void) {

    switch result {
    case let .success(response):
        do {
            if response.statusCode == 200 {
                let decodedData = try response.map(T.self)
                print("*****************************************************")
                print("Success :", decodedData)
                completion(.Success(decodedData))

            } else {
                print("*****************************************************")
                print("Status Code : ", response.statusCode)
                print("Response : ", String(data: response.data, encoding: .utf8) ?? "Failed to read response data")
                completion(.ErrorCallback(handleError(response: response)))
            }

        } catch {
            completion(.ErrorCallback(handleError(response: response)))
        }

    case let .failure(error):
        completion(.FailureCallback(error))
    }
}


Fix incorrect arrays validations in Dry::Struct attributes when used in schemas

This PR fix problem with array validation inside Dry::Struct #395

This extension was removed so this is no longer applicable.


New version: WGPUCore v0.1.4

Registering package: WGPUCore
Repository: https://github.com/dvijaha/WGPUCore.jl
Created by: @arhik
Version: v0.1.4
Commit: d4391ba0f4003b92300e6ec77e67e9000e7b3436
Reviewed by: @arhik
Reference: https://github.com/dvijaha/WGPUCore.jl/commit/d4391ba0f4003b92300e6ec77e67e9000e7b3436#commitcomment-87299186
Description: julia wgpu-native core abstraction library

followed sequential versioning and merged. This is void request.


Customize header text/Remove menu (only leave Toolbar)

Hi guys thank you for the component
How do we archive the following:

Remove the menu bar and only leave Toolbar (with same functions as on the menu bar)?
Remove or customize the header text ("Here the editor")

Thank you.

Hi @zabronm,
What version are you using? The 'Here...' thing shouldn't be in the official package.
To remove the menu bar you can set the menubar property to false in the wrapper.  Here you can find a list of the default menu options: Basic Setup
Let me know if this helps


fix(publish): adds back evaluation of current associations in publish.go

This fixes a regression introduced by #412 to the ability to prune in disk
to mirror workflows
Signed-off-by: Jennifer Power<EMAIL_ADDRESS>Description
^^
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?

[X] Manually verified in the mirror to mirror and disk to mirror workflows
[X] Add to e2e tests, need pruning image checks

Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

/retest


Typescript?

Can I (gradually) convert everything to Typescript? :)
It seems to me that TS have "won" and everyone converts their projects to it eventually (unless they pick something like ReasonML or Elm).
The costs for converting to TS are proportional to the amount of code, so it might be better to start this early.
I think even with "noImplicitAny": false (e.g., most of JS code is a valid TS code) it still might be beneficial for safer refactorings and adopting types gradually.

@OAGr, any thoughts? My guess is that this would be fine in itself but might take too much time.

I like Typescript, happy for things to gradually move in that direction.

I added some basic & very forgiving (allowJs=true, strict=false) TypeScript setup in #8.


!play should play embeded files

It would be cool, if the bot could download audiofiles that are sent to the discordchat and play them afterwards, wouldn't it?

If you can't wait for this to be implemented, here's how you can do it yourself:

Open the bot.py file inside the musicbot subfolder with a text editor like Atom  or Notepad++
Scroll down to the line 845 and change the line to this:

    async def cmd_play(self, player, channel, message, author, permissions, leftover_args, song_url = ""):

Add the following lines right after the line 854:

        if len(leftover_args) < 1:
            attachments = message.attachments
            if len(attachments) < 1:
                return Response("You need to provide a song url or attach a file!")
            song_url = attachments[0]["url"]

This is how it should look:


-d option inconsistency

there is insonsistency in the "-d" param within /opt/pivpn/makeOVPN.sh and /usr/local/bin/pivpn
by default, expiration time is interactively queried instead so -d option is mandatory when using pivpn in scripted mode
/opt/pivpn/makeOVPN.sh
helpFunc() {
echo "::: Create a client ovpn profile, optional nopass"
echo ":::"
echo "::: Usage: pivpn <-a|add> [-n|--name ] [-p|--password ]|[nopass] [-d|--days ] [-h|--help]"
echo ":::"
echo "::: Commands:"
echo ":::  [none]               Interactive mode"
echo ":::  nopass               Create a client without a password"
echo ":::  -d,--days            Expire the certificate after specified number of days (default: 1080)"
echo ":::  -n,--name            Name for the Client (default: '"$(hostname)"')"
echo ":::  -p,--password        Password for the Client (no default)"
echo ":::  -h,--help            Show this help dialog"
}
/usr/local/bin/pivpn
pivpn -h
::: Control all PiVPN specific functions!
:::
::: Usage: pivpn  [option]
:::
::: Commands:
:::  -a, add [nopass]     Create a client ovpn profile, optional nopass
:::  -c, clients          List any connected clients to the server
:::  -d, debug            Start a debugging session if having trouble
:::  -l, list             List all valid and revoked certificates
:::  -r, revoke           Revoke a client ovpn profile
:::  -h, help             Show this help dialog
:::  -u, uninstall        Uninstall PiVPN from your system!
function helpFunc {
echo "::: Control all PiVPN specific functions!"
echo ":::"
echo "::: Usage: pivpn  [option]"
echo ":::"
echo "::: Commands:"
echo ":::  -a, add [nopass]     Create a client ovpn profile, optional nopass"
echo ":::  -c, clients          List any connected clients to the server"
echo ":::  -d, debug            Start a debugging session if having trouble"
echo ":::  -l, list             List all valid and revoked certificates"
echo ":::  -r, revoke           Revoke a client ovpn profile"
echo ":::  -h, help             Show this help dialog"
echo ":::  -u, uninstall        Uninstall PiVPN from your system!"
exit 1
}

Probably you want the script to just use the default number of days when creating non interactively, however I made the script ask the expiration date bey default to make the user aware that the feature is there.

yes, but pivpn is also telling wrong meaning of -d , as there is "-d debug" and "-d days" - so everybody needs to guess how it's being used non-interactively

Good point but to use -d as days you need to prepend -a

and how do i get to that information if "pivpn -h" does not tell it ?

and how do i get to that information if "pivpn -h" does not tell it ?

pivpn -a -h

closing this thread as both flags are used in different scripts with different objectives ...
pivpn -d  its for debug
pivpn -a -d its for days and not related.


Incorporate cargo-deny into build

Incorporate cargo-deny into our build to

Verify dependency licenses.
Check for vulnerable dependencies.

i want to pick this up and not sure where the builds happens , or if the cd system is external . However , its currently failing on some licencese. Do you want to use the default deny.toml , or do you have bespoke criteria ?
Here is the current output of cargo-deny check

where the builds happens

We use GitHub Actions as our CI platform. Right now, we are finishing the implementation of first devnet version of the node and the work takes place in proto branch.

Do you want to use the default deny.toml , or do you have bespoke criteria ?

We do have following criterias:

Our code is dual-licensed with MIT and Apache 2, therefore all our dependencies must be compatible with this.
Vulnerability checks must be strict.

Due to nature of these topics, this configuration is very critical to be correct and as I'm responsible for this, I need to fully understand the configuration myself. I don't have time to go through all the cargo-deny documentation right now and therefore I will not merge any external PRs related to this, but if you want to help nonetheless, you can submit preliminary version of the configuration and I'll go through it later when possible.


aws_iam_role service_role resources are not being tagged

The following resource block is missing a tagging attribute. Tagging is so used to organize infrastructure and implement policy checks based on tags.
https://github.com/terraform-aws-modules/terraform-aws-appsync/blob/master/iam.tf#L78
The other aws_iam_role resources include the tag attribute, I would request that this resource also includes tagging. In this case be a new pass-in attribute for something like service_role_tags or default to the tags module-level attribute.

Adding a tagging attribute to the resource block mentioned above would be very useful for some work I plan on doing in the near future. Wondering if the maintainers of this repo agree with the proposed changes?

Absolutely agree. PR is welcome :)


missing noun

"While multiple queues across projects can use the same agent pool, multiple queues within a project cannot use the agent pool."
I think this should say
While multiple queues across projects can use the same agent pool, multiple queues within a project cannot use the same agent pool.
I would fork and push but unable to on my work computer
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4f6f63ad-e95d-0105-c73a-de6e904edc09
Version Independent ID: c97bfa1a-5aca-80a9-d9aa-8cca9987ad82
Content: Agents pools - Azure Pipelines
Content Source: docs/pipelines/agents/pools-queues.md
Product: devops
Technology: devops-cicd-agents
GitHub Login: @steved0x
Microsoft Alias: sdanie

@JohnCOsborne Thank you for the feedback, please consider becoming a contributor.
The documentation has been updated and is pending review.


Use 'name-format' option in rendering parameter names as well

Work for this issue will begin begin on branch work-liquid-labs/dmd-readme-api/37.


[Feature Request] Client to Group based on active registered domains

Based on this suggestions, we're going to create an action hook to move customers to groups based on the number of active domains in their accounts.

The hook is ready for use.

Great hook!
I suggest to add into a log-write function, to record the change ("user id# 1234 has been automatically assigned to price slab 2", or something like that...
It's not trivial such as add a localApi call to LogActivity, but I guess it require also a full rewrite to the query that does the job (that currently check and rewrite the grouped for every single user, even if there's no change... to do it, it's also necessary to retrieve from db current groupid, and rewrite it only if it's changed...)

I updated the script to log changes to clients group. You can find a preview at the very end of this section.


openOnSessionStart not working with internalConsole

Issue Type: Bug
Omni version: 1.15.2
I made a new project with dotnet new console
When I press f5 to debug, or use the green arrow, the intergrated console has focus with the build info, instead of the debug console.
launch.json:
{
    // Use IntelliSense to find out which attributes exist for C# debugging
    // Use hover for the description of the existing attributes
    // For further information visit https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger-launchjson.md
    "version": "0.2.0",
    "configurations": [
        {
            "name": ".NET Core Launch (console)",
            "type": "coreclr",
            "request": "launch",
            "preLaunchTask": "build",
            // If you have changed target frameworks, make sure to update the program path.
            "program": "${workspaceFolder}/bin/Debug/netcoreapp2.0/DockerLogTest.dll",
            "args": [],
            "cwd": "${workspaceFolder}",
            // For more information about the 'console' field, see https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger-launchjson.md#console-terminal-window
            "console": "internalConsole",
            "stopAtEntry": false,
            "internalConsoleOptions": "openOnSessionStart",
            "logging": {
                "moduleLoad": false,
            }
        },
        {
            "name": ".NET Core Attach",
            "type": "coreclr",
            "request": "attach",
            "processId": "${command:pickProcess}"
        },
    ]
}

VS Code version: Code 1.25.1 (1dfc5e557209371715f655691b1235b6b26a06be, 2018-07-11T15:43:53.668Z)
OS version: Windows_NT x64 10.0.14393

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz (4 x 2295)

GPU Status
2d_canvas: unavailable_softwareflash_3d: unavailable_softwareflash_stage3d: unavailable_softwareflash_stage3d_baseline: unavailable_softwaregpu_compositing: unavailable_softwaremultiple_raster_threads: unavailable_offnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: unavailable_softwarevideo_encode: unavailable_softwarevpx_decode: unavailable_softwarewebgl: unavailable_offwebgl2: unavailable_off

Memory (System)
16.00GB (5.82GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (18)

Extension
Author (truncated)
Version

spellright
ban
2.5.24

markdown-mermaid
bie
1.0.0

path-intellisense
chr
1.4.2

gitignore
cod
0.5.0

bracket-pair-colorizer
Coe
1.0.59

githistory
don
0.4.2

tslint
eg2
1.0.34

auto-rename-tag
for
0.0.15

python
ms-
2018.7.1

azurecli
ms-
0.4.2

csharp
ms-
1.15.2

PowerShell
ms-
1.8.2

vsliveshare
ms-
0.3.504

team
ms-
1.136.0

debugger-for-chrome
msj
4.8.2

code-settings-sync
Sha
3.0.0

vscode-wakatime
Wak
1.2.3

markdown-all-in-one
yzh
1.6.0

@gregg-miskelly Does this sound like a debugging bug, or a bug with VS Code itself?

I filed it against VSCode initially who closed it. https://github.com/Microsoft/vscode/issues/55940#issuecomment-411026965

@CoenraadS I am not sure I understand your issue.
Because you have "internalConsoleOptions": "openOnSessionStart" and "console": "internalConsole" set you should see that your program's stdout/err goes to the 'DEBUG CONSOLE' window and that the 'DEBUG CONSOLE' tab is brought to the foreground when debugging starts (see screen capture). Is this what you are seeing?

@gregg-miskelly
The terminal is in the foreground for me and I must always switch to debug console manually.
I can provide a screenshot tomorrow (~10 hours from now), but its basically just the terminal saying build complete or something

@CoenraadS Thanks, is that case this issue really belongs with VS Code. I will ping back their issue and see if they can reactivate it.


Update documentation to use new calicoctl commands

[ ]  Update all of the docs to use the latest commands
[ ]  Remove docs about non-docker networking docker containers
[ ]  Update our vagrant demos
[ ]  Move all documentation into the docs repo.

@gunjan:  Do you think you could take this on to do the following:

Get the golang branch building cleanly
Make sure the resource definitions are accurate

@robbrockbank let me know if you want me to take over some of the commands docs work tomorrow.

Closing issue and opening separate issues in calico repo


Fix ContentRootDirectory path on Linux

The current value (@"..\..\..\Content") causes this runtime exception on Linux:

Unhandled exception. System.InvalidOperationException: The generated content file is missing. Make sure to build in DEBUG mode or copy the file generated in DEBUG mode to the RELEASE output.
at DevilDaggersInfo.Tools.Engine.Content.DecompiledContentFile.Create(String contentRootDirectory, String contentFilePath) in ~/ddinfo-tools/src/DevilDaggersInfo.Tools.Engine.Content/DecompiledContentFile.cs:line 23
at DevilDaggersInfo.Tools.InternalResources.Create() in ~/ddinfo-tools/src/DevilDaggersInfo.Tools/InternalResources.cs:line 42
at DevilDaggersInfo.Tools.Application..ctor(ImGuiController imGuiController) in ~/ddinfo-tools/src/DevilDaggersInfo.Tools/Application.cs:line 30
at Program.$(String[] args) in ~/ddinfo-tools/src/DevilDaggersInfo.Tools/Program.cs:line 52

Thanks! Feel free to open an issue in case there are more problems with Linux builds. I don't test them regularly, especially debug ones.


Replace auto-updating-hash on docs site with anchor links

This suggestion came out of the performance investigation on the docs site in #6.
It's still unclear what perf impact the updating hash functionality has, but regardless of that, @ericdrobinson brought up a good point in #6 that updating the hash as you scroll through the page 100% messes up browsing history. As soon as you scroll on the docs site, the back button stops working.
@ericdrobinson's suggestion was to replace that functionality with anchor links that are copyable - like how headings in READMEs on GitHub are linked, can be copied, and render a little anchor icon to give users a hint that you may want to link/share to this. I like that suggestion.

Gonna familiarize myself with how the docs are generated and give a shot at a pull request for this. I'm also thinking of splitting up the docs page so that we have one-component-per-page - I think that may address some of the performance problems identified in #6.

It will. Involved in all of this is figuring out how to keep data persistent between the pages for the theme and scaling selection. Ben was working on it as a single page and loading in the components and using the history api

I don’t know where he left his work

I'm gonna guess @benjamind's fork 😄 https://github.com/benjamind/spectrum-css/tree/docs-site-spa

Benjamin's branch seems to work pretty well! I made some tweaks on my own branch (to hook in some gulp bits like watching and added a couple of null checks to fix some JS errors), and compared scrolling through the various alert component variants on the old docs page (all components on one page) vs. doing the same on this branch based on Ben's work. The perf graph is way less busy on the one-component-per-page setup.
Old docs site perf graph:

Out of 7.25 seconds scrolling through alert variants, ~3 seconds were spent rendering.
New docs site perf graph:

Out of 8 seconds scrolling through alert variants, 50ms was spent rendering.
You can also see that the FPS while scrolling is way higher on the new docs page: the number of green bars in the "Frames" row is much higher during the scroll events compared to the old docs site.

Cool, thanks for this!


problem with unicorn graceful restart

Hello,
we have an application that runs with Unicorn/Sinatra/Ruby3.
We'd like to use rack-timeout to have visibility on what the app was doing when the timeout occured (with Unicorn timeout seems that is not possible).
So, in the config.ru file we added the line
use Rack::Timeout, service_timeout: 45
When we deploy the application, we send a USR2 signal to unicorn master process, in order to gracefully restart the application, but unicorn processes are not restarted and in the unicorn logs we found these lines:
I, [2022-10-07T16:38:22.206164 #99971]  INFO -- : executing ["/home/user/.rvm/gems/ruby-3.0.2/bin/unicorn", "-D", "-c", "/home/user/project/unicorn.conf.rb", {8=>#<Kgio::UNIXServer:/tmp/unicorn.sock>, 12=>#<Unicorn::TCPSrv:fd 12, AF_INET, <IP_ADDRESS>, 8080>}] (in /home/user/project)
I, [2022-10-07T16:38:22.206678 #99971]  INFO -- : forked child re-executing...
I, [2022-10-07T16:38:24.302962 #99971]  INFO -- : inherited addr=/tmp/unicorn.sock fd=8
I, [2022-10-07T16:38:24.303171 #99971]  INFO -- : inherited addr=<IP_ADDRESS>:8080 fd=12
I, [2022-10-07T16:38:24.303571 #99971]  INFO -- : Refreshing Gem list
E, [2022-10-07T16:38:24.607024 #86513] ERROR -- : reaped #<Process::Status: pid 99971 exit 1> exec()-ed
I, [2022-10-07T16:38:25.273111 #86516]  INFO -- : source=rack-timeout id=a419d97f-5356-4476-938b-c53786e384c1 timeout=45000ms state=ready
I, [2022-10-07T16:38:25.280949 #86516]  INFO -- : source=rack-timeout id=e0a7c39b-d1d4-4957-b698-70a033a8deb9 timeout=45000ms state=ready
...
I, [2022-10-07T16:38:25.645790 #86516]  INFO -- : source=rack-timeout id=c3cba1c7-1d3f-4572-ab74-f2773b1ae94e timeout=45000ms state=ready
I, [2022-10-07T16:38:25.721126 #86516]  INFO -- : source=rack-timeout id=8efaa8a1-17b0-4e3a-9ce0-a7aaa3da68fd timeout=45000ms state=ready

Insted, when we remove the line in the config.ru, everything works as expected, and in the unicorn logs we see these lines:
I, [2022-10-07T16:41:27.915059 #100577]  INFO -- : executing ["/home/user/.rvm/gems/ruby-3.0.2/bin/unicorn", "-D", "-c", "/home/user/project/unicorn.conf.rb", {8=>#<Kgio::UNIXServer:/tmp/unicorn.sock>, 12=>#<Unicorn::TCPSrv:fd 12, AF_INET, <IP_ADDRESS>, 8080>}] (in /home/user/project)
I, [2022-10-07T16:41:27.915554 #100577]  INFO -- : forked child re-executing...

Thanks in advance!

I'm afraid there's not information here to conclude what is happening / what to fix, and I'm also not familiar with unicorn enough to comment. Most likely it has something to do with how unicorn is managing its forks/children. It's possible that this has now been fixed by #212 but I'm not sure it's related or not.

Please try 0.7.0 and let us know if the behavior has [not] changed.

The problem doesn't seem to occur anymore with version 0.7. Thanks!


🐞 [BUG] -Code not visible in dark mode in The content Display Page GSSoc'24.

Issue Verification

[X] I have verified that this is a new bug report.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Describe the bug
in the content display page the code or links are not visible in dark mode whereas it is visible in light mode.

Expected behavior
after making changes to code the code should be visible in dark mode as well.

Steps to reproduce
1.Environment Setup- after forking the project  on the system
2. Opening each file an checking the code by opening it with "live server"
3. In the content-display page the code is not visible in dark mode -finding the issue in code
4. coorecting the issue in code.
Additional Context
i can fix this please assign this to me under GSSoc'24.

please assign this o me under GSSoc'24.


Kafka stream benchmarks

Added some kafka benchmarks for measuring DH Kafka consume speed.  Tests that use TableType.append() are no-op tests that measure topic consumption into a table.  Tests that use TableType.blink() use count_by() to determine when the test is finished.
Highlights:

Kafka tests with varying heap
Kafka tests with varying table width
Kafka tests with varying types
Added a JSON producer for generating messages to Kafka
Tests use both JSON and Avro producers
Some cleanup of the experimental test package (not automated)

2023-05-25_kafka_processing_rates.csv

This pull request received no feedback for 2 weeks. In that time multiple breaking changes occurred in DHC. It was easier to pull the relevant parts from this PR and make separate PRs to deal with the breaking changes.
https://github.com/deephaven/benchmark/pull/116


Create Dockerfile

docker build -t pilbox .
docker run pilbox

Coverage remained the same at 95.848% when pulling bcd27b2b2280284302cc76ac5ff640b2a2646c78 on mhunesi:patch-1 into d05d1c0366fba2de92c261c81ca49307370f4699 on agschwender:master.


Change marks to xp and add xp virtual field to Submission

Fixes #90

Pull Request Test Coverage Report for Build 679

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.995%

Totals

Change from base Build 672:
0.0%

Covered Lines:
355

Relevant Lines:
366

💛  - Coveralls


Can't get oauth_verifier

Hi
I download rMLST scheme with confindr_database_setup , and also provide consumer key and consumer secret.
2023-11-14 09:06:32  Removing old databases...
  2023-11-14 09:06:32  Downloading cgMLST-derived data for Escherichia, Salmonella, and Listeria...
  2023-11-14 09:06:43  Since this is the first time you are using this database, it needs to be indexed by KMA. This might take a while
  2023-11-14 09:06:53  Since this is the first time you are using this database, it needs to be indexed by KMA. This might take a while
  2023-11-14 09:06:54  Since this is the first time you are using this database, it needs to be indexed by KMA. This might take a while
Visit this URL in your browser: http://pubmlst.org/cgi-bin/bigsdb/bigsdb.pl?db=pubmlst_rmlst_seqdef&page=authorizeClient&oauth_token=
Enter oauth_verifier from browser:

When I visit the URL, it show below

I can't get the oauth_verifier for download rMLST scheme
Do you have any idea?

Hi @chen1i6c04,
What is the full command that you're using with confindr_database_setup? And, does your secret file follow the format mentioned here?
i.e. Where the first line is the consumer key and the second line is the consumer secret:
efKXmqp2D0EBlMBkZaGC2lPf
F$M+fQ2AFFB2YBDfF9fpHF^qSWJdmmN%L4Fxf5Gur3

Hi @pcrxn
I solved the issue, the reason is my system time is incorrect, so pubMLST reject the request.
It can work after I adjusted system time.

Ok, thank you for letting us know!


Merge prTesting_201909190352 branch to master branch

Docs Build status updates of commit 2a7cadd:
:warning: Validation status: warnings

File
Status
Preview URL
Details

split/updateTestRef.md
:warning:Warning

Details

split/updateTestRef.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


How to get master,child,subChild,etc(child of child) pattern in datagrid with expandable rows?

https://clarity.design/documentation/datagrid/expandable-rows
I have a requirement to display expandable row which itself need to be expanded till the last child with lazy loading for each level of the child.

This sounds like a question for StackOverflow instead of an issue with Clarity. Please post how to questions there in the future.
I’m also not clear what you are asking about, but expandable rows can project a component that lazy loads data into the detail row, just like you would do with any component onInit.
Closing as not an issue, but please post on StackOverflow with better details about your use case if you need.


PUB-823 add secrets

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PUB-823
Change description
Add secrets to pipeline
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ X ] No

closing as left open to long


Insufficient contrast between filter fields and background

Describe the bug
Reported by a colleague: "My immediate reaction is that the contrast between the input fields and the background colour needs to be increase. On my secondary monitor (which is older and doesn’t have a great contrast ratio) I can barely see where the fields are, the whole screen looks like it is white, which makes it quite hard to use. "
Expected behavior
The fields should contrast clearly from the background to be easier to locate. This will be especially important for users in lower resource settings or with visual disabilities.
Screenshots

Sorry but that sounds a little bit like a "fix the user" answer. Some people won't know to adjust contrast, or will have old monitors (or phones) - are we going to tell them tough luck, if you can't afford a new monitor you deserve a sub-optimal experience on the Query Builder?
Is there a technical reason to NOT increase contrast?

Am I looking at the right bit here?
https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html
The minimum requirement is presented here:

On the query builder, the right hand vertical line in those inputs (shown below) is #828894, which (just about) meets the minimum contrast requirement of 3:1.

Would you consider maybe adding a border, or even just a bottom border as per the example cited in the accessibility guidelines?


Prune phi instructions by absract-interpreting LHS

please squash

squash plz

Don't merge yet.
Just recalled this has some bugs, which are fixed in a different branch.
Will have to port the fixes.

there's gotta be a test case you can add here

Yes! :)
On Thu, Mar 28, 2019, 9:41 PM John Regehr<EMAIL_ADDRESS>wrote:

there's gotta be a test case you can add here
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/souper/pull/525#issuecomment-477855401, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABLavzhK4oCy8CbdK1gPNx_rKWUyjV0Oks5vbYt2gaJpZM4cGW-t
.


Extend repo,mirror add snapshot

Hi,
a few words about these changes:

init: config_file:
We required to use a custom path for Aptly configuration in the past. Meanwhile we use default paths too, but I wonder if it might still be helpful?

adding snapshot.pp
We use additional scripts to automate updating any of the mirrors Puppet creates. In this regards it was easier to provide snapshots already from beginning when we need to took care of failure handling in those scripts. It's probably not useful to most users but hopefully useful enough to keep it included?

adding attributes to repo.pp
Our internal Apt structure required to define the default distribution of the repository. Other parameters were added as we evaluated Aptly. They seem reasonable enough to keep them.

adding attributes to mirror.pp
Quite similar to last paragraph we included additional arguments while evaluating Aptly. 'with_sources' is important for our build-hosts while 'with_udebs' must be included to setup proper mirrors for serving installation packages (i.e. PXE installations from local mirror). Restricting the list of architectures helps us to control the disk space needed for our mirrors.

Let me know if you have any doubts to merge these changes!
Cheers!
Mathias

Thanks for the contribution. Hopefully one of us will get round to looking at it soon. At a cursory glance it looks fine though.

Hi,
This pull request contain a similar thing than the #31. So I think we can close the #31 and take this one.
But there will be a conflit with the #29.
Thomas

@dw-thomast : Thanks for mentioning! I've merged #29 into this pull request.

Now, according to me, this branch is perfect.
We just have to wait for the project owner to merge it :)

@mklette @dw-thomast Thanks for your commits to this pull request. Looks good to me; have merged!


Naming a few boost related variables

For more clarity about gTankActiveBurnerCount: Each of the following actions increments the value if they are happening during the frame: Player is boosting, player is braking, player is using the left jet (holding Z), player is using the right jet (holding R).
This value is used to determine how fast the boost meter should be drained.

How can I tell if a variable is static rather than global? I'm more used to C++ than C, so I'm kind of learning a lot still

How can I tell if a variable is static rather than global? I'm more used to C++ than C, so I'm kind of learning a lot still
If it's used in only one file, that's an indication of a variable being static. We don't use the static keyword here however, because IDO removes them from the mapfile, and they're good to have for usage of various tools.


Implement versionize for arrays via const generics

Signed-off-by: Patrick Roy<EMAIL_ADDRESS>Reason for This PR
resolves a TODO. const generics have been stablized since 1.51
Description of Changes
Remove the macro generated impls up to array size 32 with a completely generic version based on const generics
License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.
PR Checklist
[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]

[x] All commits in this PR are signed (git commit -s).
[x] The reason for this PR is clearly provided (issue no. or explanation).
[x] The description of changes is clear and encompassing.
[x] Any required documentation changes (code and docs) are included in this PR.
[x] Any newly added unsafe code is properly documented.
[ ] Any user-facing changes are mentioned in CHANGELOG.md.

I'd absolutely love to get rid of the Default + Copy bound as well by using MaybeUninit (this is the stereotypical usecase for it according to the rust docs), but sadly that doesn't seem to be supported with generic T :( https://github.com/rust-lang/rust/issues/61956


vitualservice tcp match destinationSubnets useless

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
vitualservice tcp match destinationSubnets useless
[ ] Docs
[ ] Installation
[ x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
Steps to reproduce the bug
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: tcp-echo
spec:
  hosts:
  - "*"
  gateways:
  - tcp-echo-gateway
  tcp:
  - match:
    - destinationSubnets:
      - <IP_ADDRESS>/24
    route:
    - destination:
        host: tcp-echo
        port:
          number: 9000
        subset: v2

Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
[root@master01 tcp]# istioctl version
client version: 1.10.0-rc.1
control plane version: 1.10.0-rc.1
data plane version: 1.10.0-rc.1 (11 proxies)
How was Istio installed?
Environment where the bug was observed (cloud vendor, OS, etc)
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

It's used for mesh traffic

thanks


[BUG] InputDateRange displayed value disappears after form value change

🐞 Bug report
Description
I noticed that after programmatically changing InputDateRange control value its display value disappears. It happens when you call reset, patchValue or setValue.
Reproduction
In demo just press reset button:
https://stackblitz.com/edit/taiga-date-range-reset?file=src/app/app.component.ts
Expected behavior
After changing control value, display value should be updated accordingly.
Versions

OS: Win 10
Browser Chrome 92.0.4515.159
Angular 12.1.4
Package<EMAIL_ADDRESS>

It looks like problems with ngZone, because if I wrap this.form.reset(value) into setTimeout - everything works fine.

Hi, @uberpwner !
You are using
<button type="reset">

it triggers native reset event.
This native event resets range calendar value to default native value after you explicitly change value by this.form.reset .
See your modified sandbox (take attention to console.logs' order):
https://stackblitz.com/edit/reset-event-native?file=src/app/app.component.ts
So, if you want replace native reset event with your custom one => try event.preventDefault()

@nsbarsukov You are right, thank you!
That's my final solution: (reset.prevent)="onReset()".


Instance input list object should not have backslashes

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened: Instance listing has backslashes in "input" field
[
{
"created_at": "Mon, 03 Jun 2019 12:04:46 GMT",
"description": null,
"id": "5cf50e20ebe06301f3faa4e4",
"input": "{"ip_addr": "<IP_ADDRESS>", "description": "Migration_test_orchestration", "srcBucketName": "aws-orchestrate", "auth_token": "gAAAAABc9Q3qklyGA3wnFHBo27z93rUSSDYU-S6X4SGQhTI4hhozKwsqxFvQ2KY-0wVJfIJ6wDQjwiRyFw6-8ALSFAtcZOSNCf8N5xQCisZJHN-Iw6oDWO6xe7jrs0sLWRjlqtlOyDX-Q7eDhBgXxD66BSDYo1sEcJBfOtrLxk25LWZ4HeIUya159aqyh6FrpC08161gw97T", "userId": "558057c4256545bd8a307c37464003c9", "remainSource": true, "destBucketName": "hw-orchestrate", "tenant_id": "94b280022d0c4401bcf3b0ea85870519", "destBackend": "hw-backend", "port": "8089", "name": "testmigration"}",
"name": "migration-bucket",
"output": null,
"service_id": "eecd76dd-f46b-4113-a7ab-9108107a2f3e",
"status": null,
"updated_at": "Mon, 03 Jun 2019 12:04:46 GMT",
"workflow_definition_id": "417de5d9-a8d3-4499-9148-ed56cca15d3b",
"workflow_source": "opensds.migration-bucket"
},
What you expected to happen: It should be sanitized
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Orchestration(release/branch) version:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

/assign \assign @himanshuvar

PR is raised for it.

closing


Severe slicing bug when slicing a cube with a boolean ndarray

🐛 Bug Report
Hi folks, buggy-bug here, please see the following:
MRE
import netCDF4
import iris
import dask
print(dask.__version__)
import numpy as np

fil = "tos_Omon_CESM2_historical_r1i1p1f1_gn_185001-201412.nc"

def do_lazy_iris(c):
    bo = np.zeros(c.core_data().shape[0], dtype=bool)
    bo[1560:1860] = True
    d = c[bo, ...]
    print("Lazy Iris")
    print(d[100, 30, 50].data)
    print(d[56, 30, 50].data)
    print(d[144, 30, 50].data)

def do_realized_iris(c):
    bo = np.zeros(c.data.shape[0], dtype=bool)
    bo[1560:1860] = True
    d = c[bo, ...]
    print("Realized Iris")
    print(d[100, 30, 50].data)
    print(d[56, 30, 50].data)
    print(d[144, 30, 50].data)

def do_netCDF4():
    ds = netCDF4.Dataset(fil)
    print(ds["tos"][1660, 30, 50])
    print(ds["tos"][1616, 30, 50])
    print(ds["tos"][1704, 30, 50])

cub = iris.load_cube(fil)
do_lazy_iris(cub)
print("\n")
do_realized_iris(cub)
print("\n")
do_netCDF4()

file can be downloaded directly from https://esgf.ceda.ac.uk/thredds/catalog/esg_cmip6/CMIP6/CMIP/NCAR/CESM2/historical/r1i1p1f1/Omon/tos/gn/v20190308/catalog.html?dataset=esg_cmip6/CMIP6/CMIP/NCAR/CESM2/historical/r1i1p1f1/Omon/tos/gn/v20190308/tos_Omon_CESM2_historical_r1i1p1f1_gn_185001-201412.nc
Environment
Things that matter:

iris==3.11.0
dask: 2024.8 or 2024.11
netCDF4 (latest version, doesn't matter)
all else should be the same

Results
Run the above Python code for the two versions of Dask (2024.8 and 2024.11) and you'll see the differences :grin:
Fixing the issue
Hints:

There is some very deterministic rotation of the data from lazy vs realized, the data is the same but there is an offset of indices of exactly 44 (in this case), so the data, albeit having the same data points values, is symmetrically shifted, I'm sure that if you look at the code you will find this extra indexing that's not needed :smiley:
no such issues when slicing with int ndarrays, gotta be boolean
it's be good to have a test that checks against netCDF4 values, like in my MRE

Good luck :beer:

Whoops forgot to tag poor @schlunma who worked heaps on isolating the behaviour out of the stack 🍺

Just as an extra clue: moving the slice forward in time, and asking for elements equally shifted in time, results in consitent results lazy-realized-netCDF4:
import netCDF4
import iris
import dask
print(dask.__version__)
import numpy as np

fil = "tos_Omon_CESM2_historical_r1i1p1f1_gn_185001-201412.nc"

def do_lazy_iris(c):
    bo = np.zeros(c.core_data().shape[0], dtype=bool)
    bo[1460:1860] = True
    d = c[bo, ...]
    print("Lazy Iris")
    print(d[100, 30, 50].data)
    print(d[56, 30, 50].data)
    print(d[144, 30, 50].data)

def do_realized_iris(c):
    bo = np.zeros(c.data.shape[0], dtype=bool)
    bo[1460:1860] = True
    d = c[bo, ...]
    print("Realized Iris")
    print(d[100, 30, 50].data)
    print(d[56, 30, 50].data)
    print(d[144, 30, 50].data)

def do_netCDF4():
    ds = netCDF4.Dataset(fil)
    print(ds["tos"][1560, 30, 50])
    print(ds["tos"][1516, 30, 50])
    print(ds["tos"][1604, 30, 50])

cub = iris.load_cube(fil)
do_lazy_iris(cub)
print("\n")
do_realized_iris(cub)
print("\n")
do_netCDF4()

and in the same vein, trying to retrieve the data elements frm the example above (the MRE), with a slice shifted in time, results in consistent results too:
import netCDF4
import iris
import dask
print(dask.__version__)
import numpy as np

fil = "tos_Omon_CESM2_historical_r1i1p1f1_gn_185001-201412.nc"

def do_lazy_iris(c):
    bo = np.zeros(c.core_data().shape[0], dtype=bool)
    bo[1460:1860] = True
    d = c[bo, ...]
    print("Lazy Iris")
    print(d[200, 30, 50].data)
    print(d[156, 30, 50].data)
    print(d[244, 30, 50].data)

def do_realized_iris(c):
    bo = np.zeros(c.data.shape[0], dtype=bool)
    bo[1460:1860] = True
    d = c[bo, ...]
    print("Realized Iris")
    print(d[200, 30, 50].data)
    print(d[156, 30, 50].data)
    print(d[244, 30, 50].data)

def do_netCDF4():
    ds = netCDF4.Dataset(fil)
    print(ds["tos"][1660, 30, 50])
    print(ds["tos"][1616, 30, 50])
    print(ds["tos"][1704, 30, 50])

cub = iris.load_cube(fil)
do_lazy_iris(cub)
print("\n")
do_realized_iris(cub)
print("\n")
do_netCDF4()

so there is something very odd when starting the slice at time index 1560 out of 1980 index length

...and shifting the slice forward in time, results in consistent results:
import netCDF4
import iris
import dask
print(dask.__version__)
import numpy as np

fil = "tos_Omon_CESM2_historical_r1i1p1f1_gn_185001-201412.nc"

def do_lazy_iris(c):
    bo = np.zeros(c.core_data().shape[0], dtype=bool)
    bo[1660:1860] = True
    d = c[bo, ...]
    print("Lazy Iris")
    print(d[100, 30, 50].data)
    print(d[56, 30, 50].data)
    print(d[144, 30, 50].data)

def do_realized_iris(c):
    bo = np.zeros(c.data.shape[0], dtype=bool)
    bo[1660:1860] = True
    d = c[bo, ...]
    print("Realized Iris")
    print(d[100, 30, 50].data)
    print(d[56, 30, 50].data)
    print(d[144, 30, 50].data)

def do_netCDF4():
    ds = netCDF4.Dataset(fil)
    print(ds["tos"][1760, 30, 50])
    print(ds["tos"][1716, 30, 50])
    print(ds["tos"][1804, 30, 50])

cub = iris.load_cube(fil)
do_lazy_iris(cub)
print("\n")
do_realized_iris(cub)
print("\n")
do_netCDF4()

anything special about 1560 out of 1980? Apart from 1650 / 1980 = 0.78787878... which is a beautiful number :grin:

@valeriupredoi To clarify if a bug was solved or introduced: which of the two versions of Dask produces the correct numbers?

ah a good point @bouweandela :beer: :

dask <=2024.8.2: no difference between any sliced cube ie lazy slice == realized slice == netCDF4-python data
dask >2024.8.2: lazy slice has data rotated (given the above slice only, starting at index 1560) but realized slice == netCDF4-python data

Thanks, that is very useful information. Have you been able to reproduce this using only Dask arrays? Or does the issue only show up when the data is loaded through Iris?

let me try get it to go through netCDF4+Dask only, can't really load the data in a safe way in any other way (so that I preserve some iris-like structure)

OK, netCDF4-python+Dask with MRE:
def do_netCDF4_Dask(c):
    ds = netCDF4.Dataset(fil)
    bo = np.zeros(c.data.shape[0], dtype=bool)
    bo[1560:1860] = True
    dat = da.array(ds["tos"])[bo, ...]
    print(dat[100, 30, 50].compute())
    print(dat[56, 30, 50].compute())
    print(dat[144, 30, 50].compute())

gives correct ie unrotated results for both dask 2024.11 (12 too) and 2024.8
Here's another clue: I switched to iris==3.9, and this buggy behaviour disappears! Let me try go to 3.10 too

Curiously, I can't seem to replicate this behaviour directly from the `NetCDFDataProxy object.
from iris.fileformats.netcdf import NetCDFDataProxy

def do_netcdfproxy(c):
    bo = np.zeros(c.data.shape[0], dtype=bool)
    bo[1560:1860] = True
    print("NetCDF Proxy")
    proxy = NetCDFDataProxy(shape=(1980, 384, 320), dtype=np.float32(), path=fil, variable_name="tos", fill_value=999)

    dask_proxy = da.from_array(proxy, chunks=(300, 384, 320))
    dask_slice = dask_proxy[bo, ...]

    print(dask_slice[100, 30, 50].compute())
    print(dask_slice[56, 30, 50].compute())
    print(dask_slice[144, 30, 50].compute())

This seems like a pretty tricky one to debug. I think for the time being a dask pin is probably sensible.

It's also worth noting that this problem doesn't seem to be due to iris specific indexing since the core data dask array also has this problem.

def do_lazy_iris_core(c):
    bo = np.zeros(c.core_data().shape[0], dtype=bool)
    bo[1560:1860] = True
    print("Lazy Iris core data")
    dc = c.core_data()[bo, ...]
    print(dc[100, 30, 50].compute())
    print(dc[56, 30, 50].compute())
    print(dc[144, 30, 50].compute())

A pin on Dask is really unwelcome, since that version we'd pin on is already 4+ months old. An alternative, that I would propose to my colleagues, would be to use the int indexed ndarray, literally converting the boolean slice to an int dtype-d array. Let me know if you need me to run any more fixes.

@valeriupredoi we've discussed this at length, and we think there's a significant risk of others also encountering this problem, and potentially in ways where a workaround is not possible. We don't know how long it will take to develop a full understanding of the problem, and also how long it might take to fix, especially with the Christmas period coming up. So avoid leaving our users exposed to this problem, a pin is unfortunately necessary.
We're going to implement the pin in a bugfix release, which should capture most 'naive' users, including those on PyPI. If the pin is a problem for you then you can specify a different Iris version in your requirements.

It is indeed solved upstream in Dask, see the issue  https://github.com/dask/dask/issues/11614 but I suggest keeping the issue open until both Dask release the version with the fix, and iris unpins Dask, I'd also pin Dask to that version in your next release 🍺🎄

well, it's up to you guys to decide how to handle an issue, my take is keep it open as long as the bug is still out there, the workaround the bug (ie pin Iris) is done, but the actual bug is still lurking (in Dask, as we've seen, until Dask release a new version, after the Xmas hols). At any rate, you folks have a good break and happy Xmas! :christmas_tree:


[SUPPORT] When using the HoodieDeltaStreamer, is there a corresponding parameter that can control the number of cycles? For example, if I cycle 5 times, I stop accessing data

Tips before filing an issue

Have you gone through our FAQs?

Join the mailing list to engage in conversations and get faster support at<EMAIL_ADDRESS>

If you have triaged this as a bug, then file an issue directly.

Describe the problem you faced
When I use the HoodieDeltaStreamer, the "-- continuous" parameter: "Delta Streamer runs in continuous mode running source match ->Transform ->Hudi Write in loop". So I would like to ask if there are any corresponding parameters that can control the number of cycles, such as stopping accessing data when I cycle 5 times.
To Reproduce
Steps to reproduce the behavior:

Prepare Kafka's topic and continuously produce data
Utilize hudi utilities bundle_ 2.12-0.13.0.jar and the "-- continuous" parameter continuously receive data from Kafka and synchronize it to hive

Expected behavior
Are there any corresponding parameters that can control the number of cycles? For example, when I cycle 5 times, I stop accessing data.
Environment Description
Hudi version : 2.12-0.13.0
Spark version : 3.2.3
Hive version : 3.1.3
Hadoop version : 3.3.4
Storage (HDFS/S3/GCS..) : hdfs
Running on Docker? (yes/no) : no
Additional context
I would like to ask if there is a parameter for controlling the number of times, or if it will be supported in the future
Stacktrace
Add the stacktrace of the error.

I found a configuration: "-- post write termination strategy class". I tried using the 'org.apache.hudi.utilities.deltastreamer.NoNewDataTerminationStrategy' to stop the task, but it didn't seem to meet my expectations. I think that after it stops ExecutorService, the subsequent SparkContext will also stop, but now SparkContext will always be started and no subsequent logs will be visible.

@ad1happy2go  Should we stop SparkContext?

I have looked at the code and it will wait for the thread to complete the task. It will stop after a maximum of 24 hours.

@LiJie20190102 Do you need any other support on this ? Feel free to close it if not.

@LiJie20190102 Closing out this issue. Feel free to open if you need any other support on this.


Autocomplete not working properly?

Hi there,
first of all, thanks for this extension. I like Code very much and was happy to see an extension for Elixir for it.
Unfortunately I have some trouble to use it. I'm not sure if it's just me, or something is not working properly. But if I begin to type a word and Intellisense shows up (example def/2) and I press the Tab or Enter all I get is really the def/2 in the editor. Is it on purpose? I've used Atom for Elixir before and it also shows def/2, but after Tab I always got my clean:
def Name do
end
What do I wrong?
Best

I think this is an old bug (#22) but this should be fixed in 0.1.1. Are running the latest version?
I currently can't reproduce this on master, I will push out a new build once we have transitioned the rights to publish to me.

I also have this bug in version 0.1.1.

$ elixir -v
Erlang/OTP 19 [erts-8.2.2] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false] [dtrace]
Elixir 1.4.2

Thanks for the detailed report @philipgiuliani
Appearently the fix for #22 wasn't yet published in 0.1.1
I will publish the update once @mat-mcloughlin and I figure out how to transfer ownership

@philipgiuliani @DarthIwan I pushed a new update, can you confirm that this issue is fixed now?

Just updated and works great! :)
Thank you very much!

Thanks for your feedback :-)


Corrupted binary parts

Currently the \n char gets replaced with \r\n in binary parts:
My current workaround is:
module Mail
  class Message
    # Avoids calling {String#to_crlf} on binary parts.
    def raw_source=(value)
      if value.include?("Content-Transfer-Encoding: binary")
        @raw_source = value
      else
        @raw_source = value.to_crlf
      end
    end
  end
end

You can reproduce this with a PDF:
--uuid:f2520735-6098-4586-93f3-019733fc1404+id=4
Content-ID: <http://tempuri.org/1/634746078367623835>
Content-Transfer-Encoding: binary
Content-Type: application/octet-stream

%PDF-1.3
....

Fixed by #1113


updating to integrate with cucumber.js 0.9.x

cucumber.js 0.9 brought in some breaking changes.
This PR should bring parallel-cucumber-js up to date with cucumber.js and resolve issue #16
changes:

duplicate step definitions will cause an ambiguity error:
https://github.com/cucumber/cucumber-js/commit/0e284313c2c75aebd53f74ea966e8c14d8946800

AstTreeWalker now takes an options parameter:
https://github.com/cucumber/cucumber-js/commit/d8b0ae7fb476ed3d2009ad2cf93264d7a1b6b940

Cli.Configuration now takes an options object and an array of feature paths:
https://github.com/cucumber/cucumber-js/commit/c37d1ce98d43c43635d9898a90d9b72fe95189a4

World function doesn't take a callback:
https://github.com/cucumber/cucumber-js/commit/50c5eb6311edfd1a8cb1ddabff77d3cc20c65f99

listeners is now an Array:
https://github.com/cucumber/cucumber-js/commit/022e790ec27ffef117df6722e9b4a80260a3826d

Hi @dyanarose.  Latest release now supports Cucumber 1.0.x


Fix the number of net_connections_currently_open_stat error increase

when connectUp success, connectUp function will increase net_connections_currently_open_stat, so it is no need in function TSVconnFdCreate.

[approve ci]


Use class_map on inference workflow

🚀 Feature
Currently there is no default way to set ClassMap in the inference workflow. Specially because we end up creating the inference dataset like so:
infer_ds = Dataset.from_images([img], infer_tfms)

There is no place to pass the class_map here. It's not so easy as to add a parameter class_map to this function because we don't know the task is should be set on (in the majority of cases it will be under .detection but we cannot be sure).

add class_map like this：
infer_ds = Dataset.from_images([img], infer_tfms, class_map=class_map)
version0.8.0 works fine。

Resolved.


Added New Free Course Portal in Integration Platform Space

New Category added.
New course portal added under that.

@avinash201199 conflict resolved.


Hive-Cote implementation

Hi,
Can you provide an example of how to implement HIVE-COTE using sktime ?
Thanks

hi, so the final way of building hive-cote is still in development, because we want to release it with a contract time. tbh we never build it as one classifier. It is much better to build each component and post process the final classifier. I'm just debugging components to make sure the output is not significantly different to the java version, tsml. Working document is here, which I will update this week.

Thank you very much,
Looking forward for the release.

Hm, but isn't there already the option to build it in a modular way already?
It just might not be optimized.
This example has RISE
https://github.com/alan-turing-institute/sktime/blob/master/examples/univariate_time_series_classification.ipynb
and surely HIVE-COTE is just a matter of putting the right building blocks together in the right sequence?

(re-opening because I'm also interested in the answer to the question, in the variation I've just posted)

@TonyBagnall : post-processing = compilation, i.m.o. - very interested in this topic, it might be worth discussing in a separate thread as it seems like a major feature to me

its a bit more complex than putting them in a pipeline, since you need a weight estimate of the accuracy from the training data, and there are bespoke ways of doing that, and a voting scheme. However, this is very simple and we have it in place, just need to test and push it.

if I may attempt to translate: this means in-principle you could build it as a pipeline, but in terms of components we are currently missing one, namely the ensembler/compositor that is used in HIVE-COTE?

yes you could, although I tend to think of it hierarchically rather than linearly, in that HIVE-COTE sits on top of the others. Top level also needs to handle the time contract, determining method of accuracy estimation, and threading each component if configured thus. Jason has a version and when he comes up for air from teaching this week he will I hope sort it out I'm currently running some experiments related to this issue in tsml (java version), and will aim to port over best practice to sktime. Happy to discuss tomorrow

alright, maybe let's ask then the easier variant of the question: can we build all the components classifiers of HIVE-COTE, considered as top-level ensemble, that is, HIVE-COTE minus the top layer? We have RISE (above).
Yes, let's chat tmrw.


[Request] EndeavourOS

The icon I want is:

Name: EndeavourOS
URL: https://endeavouros.com/
Link to icon: https://raw.githubusercontent.com/endeavouros-team/endeavouros-theming/master/EndeavourOS-logo.png

Vector version of the logo: https://upload.wikimedia.org/wikipedia/commons/4/4b/EndeavourOS_Logo.svg
Official style guide or brand guide: https://github.com/endeavouros-team/endeavouros-theming

I'd like to take this up!


kubefirst terraform command should throw error when not able to connect to Vault

Which version of kubefirst are you using?
2.6.1
Which cloud provider?
None specific
Which DNS?
None specific
Which installation type?
None specific
Which distributed Git provider?
None specific
Did you use a fork of gitops-template?
No
Which Operating System?
None specific
What is the issue?
If the command kubefirst terraform set-env isn't able to connect to Vault (example, someone pasted the --vault-token with a % at the end which isn't valid (not sure if happen only in this case on in all bad token cases), the command run without any error, but obviously won't work, and generate the .env file it is supposed to do. The command should return an error in that case.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@konstructcarrie FYI, the issue you had last week.


Track @imports that include extension

This fixes the issue that if someone includes a file extension in their @import (e.g. @import 'foo.scss'), then the plugin doesn't property track changes to that file, even though sass does import such a file (extension is merely optional).
sass's behaviour can be tested with this command:
mkdir /tmp/css;
cd /tmp/css;
echo "@import 'foo.scss'" > main.scss;
echo "body { color: #fff }" > foo.scss;
sass main.scss:main.css;
cat main.css;

Output:
body {
  color: #fff; }

/*# sourceMappingURL=main.css.map */

Thanks for your contribution! Wanna join the project? :smiley:


bug: Error message every time I start writing the command :lua

Did you check docs and existing issues?

[X] I have read all the noice.nvim docs
[X] I have searched the existing issues of noice.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.9
Operating system/version
MacOS 13.6
Describe the bug
Every time I begin to write :lua , for each subsequent character I get the error message " query: invalid structure at position X for language lua" (X standing for any number). Therefore, I end up getting a lot of error messages, one for each character.

Steps To Reproduce

Open nvim
Enter : lua
Start writing any subsequent command, like require(...)

Expected Behavior
Error messages not to appear when writing correct lua commands.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/noice.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

this looks like a query and parser out of sync problem to me

So how would I solve the problem?

:TSUpdate. If that doesn't work, check the nvim-treesitter docs/wiki

Thanks for the suggestion, I actually found the solution here: https://github.com/nvim-treesitter/nvim-treesitter/issues/3092


Snapshot serializer in CLI tests doesn't replace time durations >= 1s with a placeholder

Snapshot serializer in CLI tests doesn't replace time durations greater than or equal to 1s with a placeholder.
Failed pipeline: https://github.com/prisma/prisma/runs/4657927865?check_suite_focus=true#step:15:662
  ● --schema from parent directory › --schema absolute path: should work

    expect(received).toMatchInlineSnapshot(snapshot)

    Snapshot name: `--schema from parent directory --schema absolute path: should work 1`

    - Snapshot  - 1
    + Received  + 1

      ↵
    - ✔ Generated Prisma Client (0.0.0 | TEST_ENGINE_TYPE) to ./subdirectory/@prisma/client in XXms
    + ✔ Generated Prisma Client (0.0.0 | TEST_ENGINE_TYPE) to ./subdirectory/@prisma/client in 3.34s
      You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client

Relevant code: https://github.com/prisma/prisma/blob/c1fdadf96c27509accf4e8d5c0c3ab91ff68afd4/packages/cli/src/tests/helpers/snapshotSerializer.ts#L37-L39

It does now so I'll close
https://github.com/prisma/prisma/blob/main/packages/sdk/src/utils/jestSnapshotSerializer.js#L74

Thanks!

Thanks! added in https://github.com/prisma/prisma/pull/11123


Closeing Popup while prerenderTemplate is still active throws Window Closed error

I render a zoid component as a popup.
When I try to close the popup while the prerenderTemplate is still active (the spinner).
I got this error.
Uncaught Error: Window closed
    at index.js:550
    at _loop (promise.js:161)
    at ZalgoPromise._proto.dispatch (promise.js:152)
    at ZalgoPromise._proto.resolve (promise.js:96)
    at _loop (promise.js:212)
    at ZalgoPromise._proto.dispatch (promise.js:152)
    at ZalgoPromise._proto.resolve (promise.js:96)
    at promise.js:353
    at _loop (promise.js:161)
    at ZalgoPromise._proto.dispatch (promise.js:152)

This is thrown by this function in the ParentComponent:
    close() : ZalgoPromise<void> {
        return ZalgoPromise.try(() => {
            this.component.log(`close`);
            return this.event.trigger(EVENT.CLOSE);

        }).then(() => {
            if (this.child) {
                this.child.close.fireAndForget().catch(noop);
            }

            return this.destroy(new Error(`Window closed`), false);
        });
    }

I wonder is there any way to gracefully close the popup while prerenderTemplate is still active without causing this error?

The difficulty here is that closing the window prior to it being loaded rejects the render() promise since it's a failure during the render process. And if that render promise rejection isn't handled, it'll result in an uncaught error.
So in theory, you can render().catch(() => { ... }) to handle/suppress that error.


Funnel Report Using Event Properties

Hi,
To maintain a clean events definition, I currently have only a few event_name values, each with specific properties as shown in the code below. However, I would like to generate a funnel report that not only tracks the event names (like click or view) but also leverages the event properties. For example, my click event could occur on different pages or steps of the onboarding process on my platform, and I'd like to track this granularity in the funnel.
Is it already possible to do this? If not, I would appreciate any guidance on how to achieve this functionality.
export declare global {
    interface Window {
        umami?: {
            track: <T extends EventName>(
                eventName: T,
                eventData: EventDataMap[T]
            ) => void;
        };
    }
}

type Page = 'x' | 'y' | 'z';
type Action = 'a' | 'b' | 'c' | 'd';

// Define allowed event names
type EventName = 'c' | 'v';

// Map event names to specific properties
interface EventDataMap {
    click: {
        page: Page;
        type: Action;
        component_name: string;
    };
    view: {
        page: Page;
        step: 'global' | 'checkout_success' | 'checkout_cancel';
        component_type?: 'banner' | 'modal';
    };
}

We definitely plan to include event data into all the reports.


Do a better job of formatting error messages as json

Right now when cargo-vet spits out an error (in this case some first-party packages match published crates.io versions), it doesn't format it as json even if --output-format=json is specified. This can cause opaque errors from infrastructure that's expecting json.
Here's another example, which stems from a toml parse error: https://treeherder.mozilla.org/jobs?repo=try&revision=8a3a904d1fc5eedc4fc349af5fcc18767b35144d
CC @glandium

This will probably be much easier to do once @Gankra's work on unifying our error reporting infrastructure is done.

With #218 landed, all Errors (as in Result::Err) are written to stderr, while "output" (as in everything controlled by --output-format=json) goes to stdout. In the case that there is an Err, we should end up writing literally nothing to "output". In this way we now behave very similarly to minidump-stackwalk: either we produce valid json, or literally nothing.
That said arguably some of the cases we write to "output" for vet are "errors", so we're still a bit inconsistent about this "approach".

WE might want to always emit all errors to the output as json if we're in JSON mode

@glandium Generally speaking, do you think it's better for cargo-vet to package up errors and print them as part of json output, or to have the harnesses properly handle stderr and stdout as separate streams?

A thing I thought of last night: now that all our errors feed into a single reporting mechanism, we can theoretically write a generalized "error jsonifier" by setting a different ReportHandler when output=json: https://docs.rs/miette/latest/miette/trait.ReportHandler.html
See https://docs.rs/miette/latest/src/miette/handlers/graphical.rs.html#126-151 for the human reporter's impl. It's all just recursively asking error (Diagnostic) trait-objects if they have certain pieces of information, which is more elbow grease than difficult.

It would be simpler if errors were packed in the json output.

This is only parti


[Question] Is there a way to change the axis line (either x or y axis) into a "dashed" line in Victory Chart?

Bugs and Questions
Checklist

[x] This is a victory-native specific issue. (Issues that also appear in victory should be opened here)

[x] I have read through the FAQ and Guides before asking a question

[x] I am using the latest version of victory-native

[x] I have checked to make sure that my versions of react-native and react-native-svg are compatible with this version of victory-native. Read about version requirements

[x] I've searched open issues to make sure I'm not opening a duplicate issue

The Problem
First, Thanks FormidableLabs for the work. Much appreciated ^^
I have a question about the Axis for react-native, is it possible to change the axis line (not the graph line) into a dashed line? If it's a beginner/noob question, sorry for the inconvenience (I've checked the docs, StackOverflow, and other forums, and still have no clue).

Yes! You'll want to use the strokeDasharray attribute in your styles like so:
<VictoryAxis
  style={{
    axis: {stroke: "black", strokeDasharray: "0, 5"}
  }}
/>


Data Science with Python : Noise Removal for Image Processing

Description
Welcome to the 'DSWP' Team, good to see you here
With this issue, readers will get introduced to core information to the Noise Removal model for digital image processing along with sample code completely in an effective way.
To get assigned to this issue, add your serial numbers mentioned in the spreadsheet of "Data Science with Python", the approach one would follow and the choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on.
If you had referred any resources, add them up in "DS Resources". Similarly, if you had used datasets, include them in "DS Datasets".
Domain: Computer Vision
Mentors Assigned: Dhruv Bajaj / Aishani Singh
Points to Note :
The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include the issue number along with it.
Changes should be made inside the Datascience_With_Python/ directory & Datascience_With_Python branch.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'GWOC' contributors of the 'DSWP' domain.
All the best. Enjoy your open source journey ahead. 😎
Domain
Datascience with Python
Type of Contribution
Audio, Video, Documentation
Code of Conduct

[ ] I follow Contributing Guidelines & Code of conduct of this project.

I would like to take this issue.
Name- Aryan Ahuja
Serial No. 117
Type- Documentation
Approach- Removing noise from image using Opencv. I'll be using cv2.fastNlMeansDenoisingColored() function which is the implementation of Non-local Means Denoising algorithm

I would like to work on this issue.
Serial No: 721
Name: Prishita Singh
Type - Documentation
Approach - Intro, using OpenCV removing noise from an image

Issue assigned to @theshredbox for documentation


[5.7] Delete unneeded return statement

looks like we had some mistake, since assertSessionHasNoErrors have 2 returns one by one

assertSessionMissing is returning $this;
https://github.com/laravel/framework/blob/bf452ce7155b4676c0370bd373bf4aad7324a5cc/src/Illuminate/Foundation/Testing/TestResponse.php#L945-L959
So this could be one liner method:
public function assertSessionHasNoErrors()
{
    return $this->assertSessionMissing('errors');
}

@antonkomarev changed


[Improvement] Misleading IT suffix in test class

What would you like to be improved?
Some test class has the IT suffix, e.g. XXXTableOperationsIT,  TestMysqlDatabaseOperations, TestPostgreSqlSchemaOperations. But integration test means end-to-end testing.
Should we remove the misleading suffix?
How should we improve?
Maybe we can revisit all the test classes in test folder to see which of them are end to end testing and remove the suffix from all other classes.

I think you are right.
Can you help to review whether this issue is reasonable? @yuqi1129

@zivali
Some tests like TestMysqlDatabaseOperations are not integration tests actually, it's just a unit test that depends on the docker environment. An integration test is an end-to-end test that starts from the user's side, mainly the user API, and then progresses through the Gravitino server and the underlying catalog implementation.
To answer your questions, I think it makes sense to differentiate between UT and IT. If you have time, go ahead. Thank you.