Supervised model

We need to create interface for the text classification.
The draft API will looks like the following:
import fasttext

# Train new classifier
classifier = fasttext.supervised(input, output, params)

# List of labels
classifier.labels

# Test classifier
classifier.test(test_file)

# Predict label of some sentence
classifier.predict(sentence)

Initial plan for fasttext.supervised was we will be able to use file and Numpy array as an input.

implemented in #21


No issue - looking for advice...

Hi there,
Could you elaborate on the process of sniffing for the right packets to get the additional information to integrate locally?
I didn't see a discussion active on this Github page so thought to reach out via an issue.
Thanks in advance.

Closing ticket as I see a very similar close issue raised.

Discussed in #2.


The behavior of Canvas.skew does not match the documentation

The documentation for Canvas.skew states that the units for the sx and sy parameters are in radians. However, that is incorrect, they are actually in raw "rise over run" ratio units. To see this, try a vertical skew of π/4 radians (45°). This should turn a horizontal line into a 45° diagonal line. You will see that it doesn't. However, if you instead try a vertical skew of tan(π/4), then you see the desired result.

This is unfortunate.  I believe the goal here was to consistently do things in terms of radians, but it's probably too late now to change the behavior.  We'll have to update the docs.

/cc @hixie in case I'm missing something here about how Skew is supposed to work.


Consider a postMessage plugin as an alternative to BroadcastChannel

Welcome! Please use this template for reporting bugs or requesting features. For questions about using Workbox, the best place to ask is Stack Overflow, tagged with [workbox]: https://stackoverflow.com/questions/ask?tags=workbox
Library Affected:
workbox-sw, workbox-build, etc.
workbox-build, workbox-sw
Browser & Platform:
E.g. Google Chrome v51.0.1 for Android, or "all browsers".
Any besides Chrome, FF
Issue or Feature Request Description:
Your request here.
Hi!
Workbox has been fantastic.  I have been working on an Edge-specific project using the MS Edge Windows Insiders builds.  These builds do not support the BroadcastChannel API that FF and Chrome use.
Instead, one can communicate with the Host page via postMessage.  Also, @angular/service-worker uses postMessage as a built-in.  We decided against @angular/service-worker for the configurability of workbox, but bumped into this in our transition.
It'd be great to have workbox have a default plugin that enables various postMessage communications by default.  That way, we can have Cache update (via 'staleWhileRevalidate') notifications go to host page, without having to write our own plugin.
Others may benefit from this as well.
Thanks!
When reporting bugs, please include relevant JavaScript Console logs and links to public URLs at which the issue could be reproduced.

We can consider it. In the meantime, if you want equivalent functionality, you can add your own cacheDidUpdate plugin to your handler:
const postMessagePlugin = {
  cacheDidUpdate: async ({cacheName, url, oldResponse, newResponse}) => {
    // Use whatever logic you want to determine whether the responses differ.
    if (oldResponse && (oldResponse.headers.get('etag') !== newResponse.headers.get('etag'))) {
      const clients = await self.clients.matchAll();
      for (const client of clients) {
        // Use whatever message body makes the most sense.
        // Note that `Response` objects can't be serialized.
        client.postMessage({url, cacheName});
      }
    }
  },
};

Great! Thank you!!

Jeff it would be good to add this to WebFundamentals somewhere. Maybe under "advanced recipes" or we could create a  "custom plugins" page. What do you think?

I'm going to close this now that we have the recipe merged in our docs.
If there's strong demand to update the "official" workbox-broadcast-cache-update plugin to add support for postMessage(), then we can reconsider.


Add support for time_series_dimension flag in _elastic/{index}/_field_caps API method

Opensearch Dashboards calling _field_caps to build an index pattern. To use quickwit natively as an external data source for it dashboards need to determine a timestamp field to render histogram, such fields listed on index pattern settings page. For that it relies on a time_series_dimension flag in <field>.<type>.time_series_dimension.
Link to the doc.
Describe the solution you'd like
Filed chosen as timestamp_field in index should be marked as time_series_dimension in _field_caps output.
Describe alternatives you've considered
I've made a little proxy to query /api/v1/indexes?index_id_patterns= and patch response of _field_caps method.
Additional context
I'm working on integrating quickwit as an Opensearch Dashboards backend to replace existing setup which is using regular Opensearch.

@kuzaxak have you started experimenting with adding opendashboard support by any chance? I'd love to exchange if you have more info on other missing pieces.

@kuzaxak have you started experimenting with adding opendashboard support by any chance? I'd love to exchange if you have more info on other missing pieces.

Yes, I was able to migrate our Open search dashboard completely to quickwit backend. But I'm using a proxy to monkey patch some responses of quickwit.
I can share a proxy code, it is a simple python flask app.

@fulmicoton here you can find a proxy server code.
I'm using quickwit as an external source not to deal with auth, dashboards storage, etc.

Enable this feature for OSD:

data_source.enabled: true

Add proxy as an additional datasource:

Add Index pattern using external source:

This way I'm using security features and SAML from OSD and logs storage and querying from Quickwit.

@kuzaxak That's absolutely awesome, thank you for sharing the script, the approach and the screenshot, The hack is really cool!


Allow the spread operator for arguments

There are multiple parts to this issue: allow spread operator on arguments and allow spreaded arguments in function and super() calls.
function foo(...args) {
    [...args]; // works
    [...arguments]; // Type 'IArguments' is not an array type.
}

If I'm not mistaken, although arguments is not technically an array in JS, it can be treated like one for all practical purposes, but I may be missing an edge case here.
Secondly, allow this to be used in function and super calls:
function foo (data: string) {}

function bar(data: string) {
    foo(...arguments);
}

class Parent {
    constructor(foo: string, bar: number) {
    }
}

class Child extends Parent {
    constructor(foo: string, bar: number) {
        super(...arguments);
    }
}

These changes would enable common patterns with re-passing parameters for higher-order functions and (I think) it's pretty common for subclasses to have the same construction signatures as their parents.

While I haven't read the ES spec, that isn't valid ES6.  Firefox complains SyntaxError: 'arguments' object may not be used in conjunction with a rest parameter.

Thanks @kitsonk. I did some reading and testing this morning and here is what I found. Using FF as a reference implementation:
> (function(...args) { return [...args] })(1, 2)
  Array [ 1, 2 ]
> (function(...args) { return [...arguments] })(1, 2)
  SyntaxError: 'arguments' object may not be used in conjunction with a rest parameter
> (function() { return [...arguments] })(1, 2)
  TypeError: arguments[Symbol.iterator] is not a function
> (function() { return [...Array.from(arguments)] })(1, 2)
  Array [ 1, 2 ]

Based on this and my reading of the spec, you can't use the spread operator on arguments. There are workarounds, namely:
// to do this
function bar(data) {
    foo(...arguments);
}

// you can either do this
function bar(...args) {
    [ data ] = args;
    foo(...args);
}

// or this
function bar(data) {
    foo(...Array.from(arguments))
}

Unfortunately using ...args breaks any sort of static checking on concrete arguments (assuming you wanted some) and it would likely be very hard for TypeScript to somehow model this:
function foo (data: string) {}

function bar(data: string) {
    foo(...Array.from(arguments));
}

So based on that I'm going to close this. Sorry for the noise.

@jbrantly
Not sure why you have data: string in your signature. This works:
function bar() {
    foo(...Array.from(arguments));
}

At any rate, not sure why this ticket is closed.
Why is this not valid ES6:
function bar() {
    foo( ...arguments );
}

or just this:
function bar() {
    foo(arguments );
}

Why reconstruct and deconstruct arguments?

I think FF has corrected this issue, the examples you provided actually work now @jbrantly
Also I think the spec actually reads that the arguments object is an iterableObject which means it can be spread.
http://www.ecma-international.org/ecma-262/6.0/#sec-functiondeclarationinstantiation
This issue was raised on SO and the relevant part of the spec:

If argumentsObjectNeeded is true, then
If strict is true or if simpleParameterList is false, then
Let ao be CreateUnmappedArgumentsObject(argumentsList).
Else,
NOTE mapped argument object is only provided for non-strict functions that don’t have a rest parameter, any parameter default value initializers, or any destructured parameters .
Let ao be CreateMappedArgumentsObject(func, formals, argumentsList, env).

Can this issue be re-opened?

This should be working as intended using --downlevelIteration.


Update aws-java-sdk-cloudwatch to 1.11.944

Updates com.amazonaws:aws-java-sdk-cloudwatch from 1.11.915 to 1.11.944.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-cloudwatch" } ]

labels: library-update, semver-patch

Superseded by #187.


Add skip parameter to base plugin configuration

can use system property -Djib.skip=true to skip if part of
lifecycle
still requires "required parameters" on jib to be configured
even if skipping, since maven doesn't provide a api for actual
goal skipping

fixes #865

If anyone has any decent testing strategies for this, let me know. It's kind of hard to do since maven doesn't actually define "skipping" a goal like gradle does.

You could run something like the BuildImageMojoIntegrationTest and use the Verifier#verifyTextInLog() that your log string appeared.

@briandealwis I was hoping to ensure that the return was called, maybe I can ensure the log has no more writes after that?


How can I get the  "cause" of ProxyToServerConnection failure?

I need to expose the "cause" (exceptions) of the HTTPS connection failure (not by checking the log). Expose the certificate exception will be valuable to get to know the cause of the SSL handshake failure to the monitor Web Application, so that these kind of failures can be noticed and resolved quickly. I guess the easiest way is to pass the (Throwable cause) to proxyToServerConnectionFailed method. Can we do this enhancement? Or there is other way to get this that I'm not aware of? Please kindly let me know. Thanks.

It's true, there's no way to access the cause of the connection failure currently. As part of the upcoming ConnectionFlow rewrite, I'd like to expose this.

Perfect. Thanks Jason. Any outlook for the next milestone to include this?


Give option to create a default profile at install time

This option will simplify writing action sets for the users. The controller can default to the location and credentials provided in this profile if the users do not override them in their action sets.

The main drawback with this approach is that for every change in the schema of the profile CRD we will have to send a PR upstream which will take a long time to get approved. The alternative is to add a profile helm chart under kanister.

Upstream PR has been sent.


Add license to package.json

Hi.
Your project doesn't include a license in package.json. eslint has a dependency on your project and requires all deps declare their license.

Duplicates #24

Can you publish a new version of your package, so it can be depended upon?


put back the config to write logs to the file instead of only stdout logs

Reason for Change:

This PR is to put back thye config to write to the file instead of only stdout logs
Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] relevant PR labels added

Notes:

@paulyufan2 make sure you run the Azure Container Networking PR - submodules pipeline. It is getting skipped as the criteria to trigger the pipeline didn't match.( Will change that in separate PR)

@paulyufan2 make sure you run the Azure Container Networking PR - submodules pipeline. It is getting skipped as the criteria to trigger the pipeline didn't match.( Will change that in separate PR: #2108 )

This is the submodule pipeline log:


[doc] improve basic-summary.md

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[x] No Need

Has document been added or modified:

[x] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

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

please modify the pr title to the format as 'xxx description' !


ModalWrapper does not close after submit when using shouldCloseAfterSubmit

Detailed description
ModalWrapper does not close after submit. i am using the prop shouldCloseAfterSubmit. handleSubmit is running, because my function this.onHandleMultiSubmit is getting triggered. Looks like in the source code it is just a simple boolean change of state to close it:
  handleClose = () => {
    this.setState({
      isOpen: false,
    });
  };

  handleOnRequestSubmit = () => {
    const { handleSubmit, shouldCloseAfterSubmit } = this.props;

    if (handleSubmit()) {
      if (shouldCloseAfterSubmit) {
        this.handleClose();
      }
    }
  };

Any ideas why this would not be working? Or am i using ModalWrapper wrong? Or is there an easy hack which would let me close this that someone else has used? Anything will do :)
Version:     "carbon-components-react": "5.32.0",
Browser: Chrome
I have posted my code for reference below.
Code
          <ModalWrapper
            // modalProps={{ onBlur: { onBlur() }, onClick: { onClick() }, onFocus: { onFocus() }, …}}
            id='input-modal'
            buttonTriggerText='Import Whitelist'
            modalLabel=''
            modalHeading='Import Whitelist'
            handleSubmit={this.onHandleMultiSubmit}
            primaryButtonText='Send To Blockchain'
            shouldCloseAfterSubmit
          >

              Add multiple addresses to the whitelist by uploading a comma seperated CSV file. The format should be as follows:

Column 1 - Ethereum Address

Column 2 - Sell Restriction (mm/dd/yyyy)

Column 2 - Buy Restriction (mm/dd/yyyy)

            <FileUploader
              buttonLabel='IMPORT WHITELIST'
              filenameStatus='edit'
              accept={[".csv"]}
              onChange={this.props.handleUpload}
              multiple
            />

            {this.props.modalShowing ?

                  Below is the data you will be sending to the blockchain, please confirm it is correct, and then click the Send button to continue.

                {this.props.addresses.map((user, i) => (

Address: {this.props.addresses[i]}

Sell Expiry Time: {this.props.sell[i]}

Buy Expiry Time: {this.props.buy[i]}

                ))}

              : null}
          </ModalWrapper>

Hi @davekaj! 👋 Thanks so much for taking the time to make this issue 😄
Most likely, this is due to this.onHandleMultiSubmit not returning a truth-y value such that this block would get triggered:
    if (handleSubmit()) {
      if (shouldCloseAfterSubmit) {
        this.handleClose();
      }
    }

Let me know if this isn't the case and I can try and help debug further!


Pull Request: Merging 'rename_organise' into 'master' branch

Hello Geekcomputers team,
I hope this message finds you well. I am Nitkarsh Chourasia, and I am thrilled to submit this pull request to merge the 'rename_organise' branch into the 'master' branch of the Python repository under the Geekcomputers organization.
In this pull request, I have made a significant improvement to the project by adding a new program named "snake_case_renamer_depth_one.py" to the 'rename_organise' branch. Allow me to provide a detailed explanation of what I did and why:
What I did:
I implemented a Python script that recursively scans through the repository's top-level directories and subdirectories on depth one. The script converts filenames and folder names to adhere to the snake_case naming convention. This convention requires using all lowercase letters and replacing spaces with underscores in the names. By adopting snake_case, we ensure a consistent and standardized approach to file and folder naming across the project.
Why I did this:

Following Python's Best Practice:
Python, as a language, strongly advocates the use of snake_case for various entities, including variables, functions, and filenames. This convention enhances the code's readability and maintainability, making it easier for developers to understand and work collaboratively.

Codebase Organization:
Maintaining a uniform naming convention improves codebase organization. Developers can quickly identify the purpose and content of files, leading to efficient collaboration and code maintenance.

Compatibility:
By using snake_case, we align with the wider Python community's best practices, making it easier for contributors from diverse backgrounds to participate and contribute effectively.

Automated Conversion:
My Python script automates the conversion process, saving valuable developer time. It also ensures that filenames are converted accurately, leaving no room for manual errors.

I kindly request the repository admins to review this pull request and consider merging it into the 'master' branch. I believe that this improvement will elevate the quality and consistency of the Python repository.
Thank you for your attention to this request. I look forward to your feedback and the opportunity to contribute further to this fantastic project.
Best regards,
Nitkarsh Chourasia

Dear Sir,
I hope this message finds you well. I am writing to request your kind assistance in transforming our repository, geekcomputers/Python, into a standardized and organized form. My goal is to improve the overall quality of the codebase, while ensuring that no existing programs are adversely affected during the process.
To achieve this, I have meticulously designed a program, "snake_case_renamer_depth_one.py," which will facilitate the transformation. This program intelligently renames files and folders within the repository to adhere to the snake_case naming convention, making the codebase more consistent and readable.
I want to emphasize that I have taken utmost care to avoid any disruptions to our existing programs. The renaming process has been limited to the first level of depth, which means that only files and folders at the top level will be affected, leaving project files untouched.
By implementing this transformation, I aim to create a solid foundation for future improvements. My plan is to gradually revise and enhance each program, while also introducing new, high-quality programs to the repository. This organizational overhaul will ensure that our repository remains efficient and easy to navigate, even as it grows in size and complexity.
Your approval and support for this endeavor are crucial, as it will pave the way for a more robust and thriving repository. I assure you that I will be meticulous in my approach, adhering to best practices and standards of Python programming throughout the entire process.
Thank you for considering my request. I eagerly await your valuable guidance and look forward to making this repository a source of pride for our community.
Sincerely,
Nitkarsh Chourasia
GitHub Username: NitkarshChourasia

Sir, please look into it and do it.
This will transform the whole repository in to a standardized form using the best practices till date.
I took special care so it doesn't break any program.
How?
I have done the renaming to the depth of level one only.
No inside of any projects files have been renamed.
I want to transform this repository.
Day by day, I will revise and improve every line of code in every program possible.
Also, add new better programs to it.
For that I need the repository to be extremely organized.
Or it will whole be a mess as of now.
I will try to sort the repository based on various parameters.
As I have worked on projects way bigger then these.

I will be scaling this repository, so need a very organized form of this repository.
I will be using the best practices of Programming and Software project management to do so.
So, please have a sincere look into this, as it is of very importance.
With the help of each other, I want to make this repository the best on the internet.

Subject: Request for Assistance in Organizing and Scaling the Repository
Dear geekcomputers,
I hope this message finds you well. I am writing to seek your valuable support and guidance in an important endeavor. As an active contributor to the geekcomputers/Python repository, I have ambitious plans to scale and transform it into a highly organized and exemplary codebase.
Given the repository's potential and the growing community around it, I believe it is essential to elevate it to the next level of excellence. To achieve this, I am committed to implementing the best practices of programming and software project management. My intention is to ensure the repository's structure and content adhere to rigorous standards, enabling seamless scalability and long-term sustainability.
I understand the significance of this task, and I sincerely request your assistance in reviewing and approving the proposed changes. With our collective efforts, I firmly believe we can establish this repository as one of the finest on the internet. By fostering collaboration, knowledge-sharing, and continuous improvement, we can set new benchmarks for Python enthusiasts worldwide.
Your experienced insights and constructive feedback are invaluable to me in this endeavor. I am eager to work closely with you to address any concerns, make necessary adjustments, and ensure that the transformation proceeds smoothly.
Thank you for considering my request. Together, we can unlock the full potential of this repository and contribute significantly to the Python programming community.
Looking forward to your positive response.
Sincerely,
Nitkarsh Chourasia
GitHub Username: NitkarshChourasia

Unstoppable @NitkarshChourasia


"Template-ize" index.html.in files

In order to integrate with the FaceBase website, we use deployment-specific index.html.in files. It works well for search/index.html.in because the main code of that page is included in a template (%TEMPLATES%), which the FaceBase version uses. Then whenever that template is updated, it gets sucked into the FaceBase file.
This is not set up for records/index.html.in and I have to notice if the chaise version is changed and then manually update it - things get out of sync very easily.
So in general, index.html.in files should put the bulk of the code in a template block. I specifically need this for records/index.html.in but think it would be a good idea for others like viewer/index.html.in

Can you tell me the block of html in the record/index.html.in that should be templatized? Should it be this entire block:
https://github.com/informatics-isi-edu/chaise/blob/master/record/index.html.in#L9-L262

lines 22 through 261 should do it (from <!-- SPINNER --> to the last closing <div> tag)

I've updated the facebase-www version so we'll see how it looks on dev after the next update

@crisaless can you please assign this to someone that can review the issue?

i checked dev.facebase.org. details pages look fine.


Corrected the required fields in the constructors.

Errors were showing in VS Code because the constructor argument for the list of colors was marked with 'required' instead of '@required'
Description
Simply changed 'required' to '@required' in the constructors.
Related Issues
Issue #63908

@googlebot I signed it!

required without the @ is the new syntax with dart's new nullsaftey feature: https://dart.dev/null-safety/understanding-null-safety#required-named-parameters
If you're using the latest Dart SDK shipped with Flutter in VS Code you shouldn't see any warnings about this.


Not running on commonMain of Kotlin Multiplatform Project

Rewrite is not running over commonMain sourceSet of a KMP. Example PR: https://github.com/nomisRev/rewrite-arrow/pull/32.
Running ./gradlew build :sample:rewriteRun shows that the sources in sample/src/commonMain/kotlin/org/example/example.kt are not being rewritten or updated.

Duplicate of https://github.com/openrewrite/rewrite-gradle-plugin/issues/172


feat(haproxy): update to 3.0 LTS

Update HAProxy to 3.0 LTS
Fix various Linting issues in the Role
Fix role for Debian that was not working
Add repo for Rocky and RHEL to be able to install v3 (taken from official docs)

Fixes #95
Fixes https://github.com/sighupio/product-management/issues/542
Tested with:

Ubuntu 20.04
Ubuntu 22.04
Rocky 9 ARM I could not test e2e because the repo does not provide packages for ARM, but I'm 99% confident it works. (I'd like a double check with an x86_64 machine if possible @stefanoghinelli).
Debian 12
Using our usual configuration for KFD (control plane + ingresses)

I did some tests with:

OS: Rocky Linux 8 and Rocky Linux 9
Architecture: x86_64
Target HAProxy version: 3.0.6

Package installation fails due to missing GPG signatures in the Zenetys repository.
Example error on Rocky Linux 8: msg: 'Failed to validate GPG signature for haproxy30z-3.0.6-1.el8.zenetys.x86_64: Package haproxy30z-3.0.6-1.el8.zenetys.x86_64.rpm is not signed'

Thanks for the test Ste, I've pushed a fix disabling gpg check for the Zenetys repo, could you please try again please?
Thanks