Implement Headers.prototypeg.getSetCookie

Per https://github.com/bytecodealliance/StarlingMonkey/pull/108.

This was implemented in https://github.com/bytecodealliance/StarlingMonkey/pull/108.


Update prompt docs for promptSecretUint

Following https://github.com/foundry-rs/foundry/pull/8082, this PR adds documentation for the promptSecretUint cheatcode.

@all-contributors please add @DhairyaSethi for code


Update email instructions to match google doc

I made a few edits to the email instructions.

Instructions updated and should be deployed soon.
Note that the instructions to "close your browser" has been added, but I think it is questionable. First, the "logout" mechanism should be in place shortly, so that after the issue is complete, you are logged out of the session.  That should eliminate the problem entirely. Second, not sure, but I think the token is preserved across browser restarts, so I'm not sure that the restart even helps.
Regardless - please monitor and we'll see if we can eliminate the problem with the forced logout after issuance.
Please close once the email content has been confirmed.


Remove resrc.it urls from interests component

We no longer use resrc.it and this is handled in the backend via ImageFormatter.

:+1:


PSR2.Classes.PropertyDeclaration.ReadonlyBeforeVisibility doesn't support constructor property promotion

Describe the bug
PSR2.Classes.PropertyDeclaration.ReadonlyBeforeVisibility doesn't apply when constructor property promotion is used
Code sample
<?php

class Test
{
    private readonly int $three;
    readonly private int $four; // <--  Correctly errors (PSR2.Classes.PropertyDeclaration.ReadonlyBeforeVisibility)

    public function __construct(
        private readonly int $one,
        readonly private int $two // <-- Does not error
    )
    {
    }
}

To reproduce
Steps to reproduce the behavior:

Create a file called test.php with the code sample above...
Run phpcs test.php ...
See error message displayed

FILE: /Users/earthiverse/Code/Test.php
-------------------------------------------------------------------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
-------------------------------------------------------------------------------------------------------------------------------------------------
 8 | ERROR | [x] The readonly declaration must come after the visibility declaration (PSR2.Classes.PropertyDeclaration.ReadonlyBeforeVisibility)
-------------------------------------------------------------------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
-------------------------------------------------------------------------------------------------------------------------------------------------

Time: 37ms; Memory: 8MB

Expected behavior
The line with readonly private int $two should also have an error.
Versions

Operating System
MacOS 14.4.1

PHP version
8.3.4

PHP_CodeSniffer version
3.9.1

Standard
PSR2, PSR12

Install type
Composer

Please confirm:

[X] I have searched the issue list and am not opening a duplicate issue.
[X] I confirm that this bug is a bug in PHP_CodeSniffer and not in one of the external standards.
[X] I have verified the issue still exists in the master branch of PHP_CodeSniffer.

@earthiverse Thank you for reporting this. I've changed the type from "bug" to "feature request" (enhancement) as the  PSR2.Classes.PropertyDeclaration sniff does not support constructor property promotion at all - and neither PSR2 nor PSR12  would expect it to, as both predate constructor property promotion, let alone readonly properties.
As things are, what with the sniff being based on the AbstractVariableSniff, adding support for examining properties declared via constructor property promotion to the sniff would likely warrant a complete rewrite of the sniff.


feat: export metadata object in stage 2

Functionally, this PR adds a metadata object to the exports of the stage 2 file. Right now, this object contains just a url property containing the file path of each function, like so:
// Existing export
export const functions = {
  func1: [Function],
  func2: [Function]
}

// New export
export const metadata = {
  func1: {
    url: "file:///some/path/to/func1.ts",
  },
  func2: {
    url: "file:///some/path/to/func2.ts",
  }
}

This will allow the bootstrap code to match log locations to function names.
Also, it includes some housekeeping:

Node tests were moved from test/ to test/node/
Deno tests added to test/deno/
CI updated to run Deno tests
Added stage 2 test

I saw the change of moving tests into more organised folders. I do really like structuring all of this a little bit. I remember looking into the code there are files in the src folder that are organised in folders, and some that are not. Maybe it might be interesting in the future to organise the src folder in general. Because it might give a little bit more context to both the code and the tests. Right now I'd almost say it might be clearer for the deno tests to just be a part of the deno folder because it'll clearly show the existing tests, and might lead to an incentive to write more when changing something there or adding something there.
Also: total nitpicking here, no prioritisation at all :)

I saw the change of moving tests into more organised folders. I do really like structuring all of this a little bit. I remember looking into the code there are files in the src folder that are organised in folders, and some that are not. Maybe it might be interesting in the future to organise the src folder in general. Because it might give a little bit more context to both the code and the tests. (for example, we have bundle.ts that is just an export of an interface, while there are other files that export functions).
Right now I'd almost say it might be clearer for the deno tests to just be a part of the deno folder because it'll clearly show the existing tests, and might lead to an incentive to write more when changing something there or adding something there.
Also: total nitpicking here, no prioritisation at all :)

Good thoughts! Let's iterate on this.


use appropiate key while publishing message to kafka

Why? Kafka caches partition number when key = null and is not round robin

publish without key fairly sends to all partitions! does not look  like we were using any key! Am i missing something?

@amarjeetsingh12 nope
When key is null this code is used
 /**
   * Retrieves the partition id and throws an UnknownTopicOrPartitionException if
   * the value of partition is not between 0 and numPartitions-1
   * @param topic The topic
   * @param key the partition key
   * @param topicPartitionList the list of available partitions
   * @return the partition id
   */
  private def getPartition(topic: String, key: Any, topicPartitionList: Seq[PartitionAndLeader]): Int = {
    val numPartitions = topicPartitionList.size
    if(numPartitions <= 0)
      throw new UnknownTopicOrPartitionException("Topic " + topic + " doesn't exist")
    val partition =
      if(key == null) {
        // If the key is null, we don't really need a partitioner
        // So we look up in the send partition cache for the topic to decide the target partition
        val id = sendPartitionPerTopicCache.get(topic)
        id match {
          case Some(partitionId) =>
            // directly return the partitionId without checking availability of the leader,
            // since we want to postpone the failure until the send operation anyways
            partitionId
          case None =>
            val availablePartitions = topicPartitionList.filter(_.leaderBrokerIdOpt.isDefined)
            if (availablePartitions.isEmpty)
              throw new LeaderNotAvailableException("No leader for any partition in topic " + topic)
            val index = Utils.abs(Random.nextInt) % availablePartitions.size
            val partitionId = availablePartitions(index).partitionId
            sendPartitionPerTopicCache.put(topic, partitionId)
            partitionId
        }
      } else
        partitioner.partition(key, numPartitions)
    if(partition < 0 || partition >= numPartitions)
      throw new UnknownTopicOrPartitionException("Invalid partition id: " + partition + " for topic " + topic +
        "; Valid values are in the inclusive range of [0, " + (numPartitions-1) + "]")
    trace("Assigning message of topic %s and key %s to a selected partition %d".format(topic, if (key == null) "[none]" else key.toString, partition))
    partition
  }

it caches partition id and uses the same till it expires (600s). This causes the accumulation since our sends are bursts, causing all to go in the same queue.

verified on sandbox.


Programmatically navigation in new router

What's the "official" programmatic equivalent of ng-link to execute from within your controller?  Whether with the basic router or the ui-router, and now with the new router, we rarely declare links directly in the markup.  More typically, we click something, do something, then programmatically navigate.

same issue.
Any solution?

I also would like to know how this works.

It's router.navigate() or router.navigateByUrl() depending on what you have available to route to a component.
Also keep in mind that this repo here is on hold and that all the development is happening over at http://github.com/angular/angular.

ok and thanks a lot :)


TbEditable check if we have registered js already

useful in combination with TbEditableColumn and large datasets

Thank you!


Delay loading of AliasAnalysis data

Pull Request Description
Continuation of #10729 to actually speed things up by 10% by delaying loading of AliasAnalysis data.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] All code follows the
Scala,
Java,
[x] Unit tests continue to pass.

Running stdlibs benchmarks to verify impact on startup.

Running stdlibs benchmarks to verify impact on startup. There is 10% speedup of the most relevant benchmark!

Another stdlibs benchmarks run to verify the state even after recent changes.


update issue & feature request template

Is your feature request related to a problem? Please describe.
Update the issue & feature request template as in the main repo
Describe the solution you'd like

keep all the options as in the main repo template
In both bug & feature form add a  field for the user to verify if the user faced the issue with / requesting the feature for the vue simulator. (mandatory field)
In only bug form add a field to ask the user if the user used simulator with or without backend. (optional field)
In only bug form  add a filed to ensure if the bug is only in dev server or build or in both. (optional field)

Describe alternatives you've considered
N/A
Additional context
feel free to discuss if you have any other additional fields that can be included which would make the process smoother for devs.
Are you working on this? (No)

Sure

@Arnabdaz  please review this PR.

@Arnabdaz shall I update the readme file by adding

Community section
Code of conduct
folder structure
contributors section

Hey @Arnabdaz  you can review this updated Pr https://github.com/CircuitVerse/cv-frontend-vue/pull/255


Add IDocumentProvider service and its implementation

#1626
does not "provide an api to generate multiple / all documents"; could be layered on this work

otherwise, meets requirements listed in #1626

assumes the following answers to open questions in #1626 (generally means everything is opt-in)

without an AddSwagger() call, IDocumentProvider service will not exist
registered document name / identifier is new SwaggerSettings<>.DocumentName property

document is not registered unless DocumentName is non-null i.e. IDocumentProvider won't know about it
SwaggerSettings<>.MiddlewareBasePath and SwaggerRoute are independent of DocumentName

middleware does not depend on the IDocumentProvider or registrar services; duplicating some code

many thanks to @rynowak for writing this proposal

:up::date:d to address your comments @RSuter. I look forward to any alternative suggestions or further thoughts you have.

@dougbu is this now ready to be merged?

is this now ready to be merged?

It won't harm anything to merge this (though squashing the 10 commits might help 😃.
But, based on our offline thread about the Startup.Configure(...) method, we might go with a different design -- especially w.r.t. the document registry. Suggest holding off until you choose an option.

@dougbu I made a PR against the branch in this PR, https://github.com/dougbu/NSwag/pull/1
I think this should cover scenario 3 (change middleware api). Is this ok and will work with your other code?

@RSuter well, I was just testing the changes I'd made. I'll push to my remote branch so that you can compare and contrast…

I'm now trying to merge all my work but it's now a big mess. But there are thee main problems:

With your approach, we cannot add a default document because we cannot detect when the user didnt provide one (i.e. AddOpenApi() is not able to detect that AddDocument is not called
AddOpenApi and AddDocument can add a document ATM which doesnt make sense from an API perspective, see

            services
                .AddOpenApi(settings => settings.DocumentName = "v1") // Why the settings here?
                .AddDocument(settings =>
                {
                    settings.DocumentName = "v2";
                    settings.GeneratorSettings.SchemaType = SchemaType.OpenApi3;
                });

If we break all users, I want to split the swagger.json and swagger UI middlewares into separate Use* functions to reduce the number of methods and not do two things with one method...

Will update my PR against your PR soon.

With your approach, we cannot add a default document because we cannot detect when the user didn't provide one (i.e. AddOpenApi() is not able to detect that AddDocument is not called

AddOpenApi() adds the first document. AddDocument(...) is only for additional documents.

// Why the settings here?

Because users may want to configure the first, possibly only, document.

separate Use* functions to reduce the number of methods and not do two things with one method.

I tried that approach but found it falls down because the UI middleware needs to know where the generator middleware is hosted. But, this will be much simpler to do once I move to an IOptions<T> approach.

I think documentName should not be part of the options/settings as it must be clear that it's only used to connect AddSwagger with UseSwagger (which IMO is not really nice, but there is not a better solution with how ASP.NET Core is designed)

:ok: though I'm not quite sure I understand the concern.
All middleware in my approach handles all the documents. Well, except the Redoc UI one. Names are primarily important for routing and the IDocumentProvider calls.

keep the name Swagger

Sure.

AddOpenApi() adds the first document. AddDocument(...) is only for additional documents.

I think this API is really confusing because AddOpenApi() and AddDocument() are doing the same but have a different name... That's why I'd like to have this nested configuration, i.e. AddOpenApi() adds the required services and AddDocument (as in AddOpenApi(options => options.AddDocument()) actually adds a document - if none is specified a default one is regeistered by AddOpenApi.

🆗 though I'm not quite sure I understand the concern.

I think it should be like this in a common scenario (simplest case):
AddSwagger() // registers services
UseSwagger() // register swagger.json middleware
UseSwaggerUi3() // register swagger.json consuming UI
This way each call has its own defined responsibility...

But, this will be much simpler to do once I move to an IOptions approach.

How should this solve this structural problem? Can you give an example?

And let's not use OpenApi in the method and stick with Swagger for now... otherwise it gets really confusing because OpenApi does not enforce OpenAPI v3.0 and v2.0 is still supported so we have two methods which should do the same but internally dont (one registers the services the other doesnt).

AddOpenApi() and AddDocument() are doing the same but have a different name

Not quite. AddOpenApi(...) does the whole shebang and AddDocument(...) just extends the available documents. Note AddDocument(...) isn't an extension method on the IServiceCollection.

I think it should be like this in a common scenario (simplest case)

That will work fine using my approach as well. The AddSwagger() call registers the default document, UseSwagger() uses the default IOptions<SwaggerMiddlewareOptions> and UseSwaggerUi3() uses the default IOptions<SwaggerUi3Options> and also the SwaggerRoute set in IOptions<SwaggerMiddlewareOptions>.
Users will be able to mess themselves up by calling UseSwaggerUi3() without UseSwagger() or by passing SwaggerMiddlewareOptions into UseSwagger() that doesn't have the same route as the default. But, both cases are avoidable e.g. by having the middleware flip a bit in SwaggerMiddlewareOptions to indicate they're actually in use.

How should this solve this structural problem?

Users would be able to stick with the usual ASP.NET Core configuration patterns. (MVC and EF get a bit more complicated because they aren't themselves exposed as middleware.)
For example, ConfigureServices(...) might contain
services.AddSwagger();
services.Configure<SwaggerMiddlewareOptions>(o => o.SwaggerRoute = "/openApi/{documentName}/swagger.json");
services.Configure<SwaggerUi3Options>(o => o.SwaggerUiRoute = "/myUi");

then the Use*() methods in Configure(...) stitch everything together.

services.AddSwagger();
services.Configure<SwaggerMiddlewareOptions>(o => o.SwaggerRoute = "/openApi/{documentName}/swagger.json");
services.Configure<SwaggerUi3Options>(o => o.SwaggerUiRoute = "/myUi");

This is really bad as you can have only one SwaggerMiddlewareOptions or SwaggerUi3Options option...
What if I need two Swagger UIs?
E.g one with the category a, one with category b and one with both (dropdown). See sample in my updated PR: https://github.com/dougbu/NSwag/pull/1

… also SwaggerMiddlewareOptions has a PostProcess (Action(request, document)) which cannot be specified per document this way...

Users will be able to mess themselves up by calling UseSwaggerUi3() without UseSwagger() or by passing SwaggerMiddlewareOptions into UseSwagger() that doesn't have the same route as the default. But, both cases are avoidable e.g. by having the middleware flip a bit in SwaggerMiddlewareOptions to indicate they're actually in use.

Yes, but Swashbuckle does it the same way - and I'd rather trade this problem for more flexibility. If you don't change the routes it just works - otherwise you have to be aware that you can misconfigure the thing...
For me these (AddSwagger, UseSwagger and UseSwaggerUi) are 3 different services... you can use UseSwaggerUi without the other two (e.g. with an external spec)

Not true because the UseSwagger(...) and UseSwaggerUi3(...) methods have overloads accepting unique options.

Ah yes, makes sense - so either you configure it for all in ConfigureServices() or individually in Configure(), right?

This is why I put the PostProcess property in the document settings.

Adding PostProcess to the generator settings was a mistake in the first place so I want to fix this... PostProcess should be only a middleware level feature to transform a document based on the current HttpContext (e.g. set correct hosts, etc.) and thus only be available in SwaggerMiddlewareOptions or SwaggerUi3Options  (and not in the generator settings itself - use a document processor for that instead).
Can't we just merge my PR and add your IOptions support to that (applies for all and {documentName} is replaced)?

Ah yes, makes sense - so either you configure it for all in ConfigureServices() or individually in Configure(), right?

Exactly 😃

PostProcess should be only a middleware level feature

That's fine though it seems better for PostProcess to operate on multiple documents rather than users having to configure the individual documents as well as a middleware per document to host it.

Latest commit means I can't apply IOptions<T> and related work I spent the day doing. Can that be backed out @RSuter?

Ok.

:up::date: only remaining WIP bits are a couple of names and a few empty doc comments.
From my perspective, this PR has the following advantages:

uses IOptions<T> for UseSwagger(...) and UseSwaggerUi4(...) scenarios
changes fewer files
reduces the middleware depth when multiple documents are registered (by default)
supports post-processing in IDocumentProvider scenarios
places extensions and the ISwaggerBuilder interface in appropriate namespaces
does not nest lambdas when using AddSwagger(...) or AddOpenApi(...)

note MVC uses nested lambdas only for changing MvcOptions, which would be relevant if SwaggerDocumentProvider took options

leaves SwaggerDocumentRegistry with a single purpose
leaves existing code unchanged except for a few nits

@RSuter please note the "Reviewers" comments in a few files

@RSuter I should have mentioned: If you choose this PR over #1678 and want me to, I'll squash the commits, perform any renaming, and fill in the blank doc comments. LMK

I hope this is ok for you?

@RSuter yes, this is fine. Much better than fine: You've now got an IDocumentProvider implementation and have moved NSwag.AspNetCore to be more familiar to ASP.NET Core developers with plans to do more in v12!
I was somewhat sorry to see the middleware pipeline still contains multiple SwaggerMiddleware instances and that users don't immediately get IOptions<T> goodness. But, these are your decisions about your code. And, I agree this took more of both of our time than we'd hoped.
One more real concern, echoing my earlier "supports post-processing in IDocumentProvider scenarios" point: This lack in NSwag.AspNetCore may mean the Microsoft document tool will get a different document than the SwaggerMiddleware would provide. That is, users may do more than adjust to the request host and schemes in their SwaggerMiddlewareSettings.PostProcess actions. Can / should SwaggerGeneratorSettings.DocumentProcessors and OperationProcessors be used for that purpose?

This lack in NSwag.AspNetCore may mean the Microsoft document tool will get a different document than the SwaggerMiddleware would provide. That is, users may do more than adjust to the request host and schemes in their SwaggerMiddlewareSettings.PostProcess actions.

You are right, this also bothers me. The following code is actually not executed when running via command line:
https://github.com/RSuter/NSwag/blob/master/src/NSwag.AspNetCore/Middlewares/SwaggerMiddleware.cs#L87-L91
The idea is that the PostProcess here should only be used to change BasePath, Schemes and Host based on the request, but of course it cannot be enforced. How would you proceed?

Remove these lines completely (breaking change for some, host and schemes may be wrong),
remove just PostProcess (but then you cannot change host, schemes, etc.) or
keep as is and add documentation that PostProcess should only be used to change host, schemes etc?

Can / should SwaggerGeneratorSettings.DocumentProcessors and OperationProcessors be used for that purpose?

Yes, exactly - you should use a custom document processor for that - but you don't have access to a request there (because a spec is independent of an actual HTTP request).

keep as is and add documentation that PostProcess should only be used to change host, schemes etc?

If it were me, this is the route I'd go because adjusting these values to match the request is so useful. Suggest also mentioning the processing order of OperationProcessors, DocumentProcessors and PostProcess.
Separately, including all schemes, hosts and PathBase values may be done using the IServerAddressesFeature in IWebHost.ServerFeatures.

you should use a custom document processor for that

Reasonable.
In retrospect, the main thing my trial addition of a PostProcess action to SwaggerDocumentSettings improved was ease of use for simple cases. Implementing IDocumentProcessor is slightly more involved but covers more cases because the DocumentProcessorContext provides more context.

In retrospect, the main thing my trial addition of a PostProcess action to SwaggerDocumentSettings improved was ease of use for simple cases. Implementing IDocumentProcessor is slightly more involved but covers more cases because the DocumentProcessorContext provides more context.

Yes, but I don't like having two concepts for the same scenario... we could just provide a generic GenericDocumentProcessor(Action<Context> action) so that it's very easy to add a lambda/inline based document processor - this way you dont need a new class...

If it were me, this is the route I'd go because adjusting these values to match the request is so useful. Suggest also mentioning the processing order of OperationProcessors, DocumentProcessors and PostProcess.

Ok, then we'll do that. But in the case of using the command line you need to define these properties via config anyway so why not force it also for the hosted scenario?

Separately, including all schemes, hosts and PathBase values may be done using the IServerAddressesFeature in IWebHost.ServerFeatures.

Good point.

so why not force it also for the hosted scenario?

I'm missing something. Force what?
If you mean forcing use of config, aren't IDocumentProcessors and PostProcess already added through config?

I mean force the user to use the config to get the host etc so that it works in the host scenario and cli scenario.. but this might upset users :-)

I agree setting the document properties statically would be a regression.
After talking more internally, I'm sorry to say the IServerAddressesFeature isn't going to be helpful until after the production server is started, possibly after the first request. Even then, for the middleware case, you'll be able to detect that HTTP is enabled in addition to HTTPs but that won't be 100% reliable. (E.g. for an HTTP request -- the service may be deployed behind a TLS gateway and not itself support HTTPS. Or the service may support both schemes but be behind a reverse proxy that supports just one.) And, IServerAddressesFeature won't improve IDocumentProvider scenarios.


Can't connect to prosody 0.10 with latest mod_websocket

I cloned this repo and put it into https://webchat.dateknoten.me/ my websocket is under https://webchat.datenknoten.me/ws, when I try to connect I'm directly taken to the login page again.
In the prosody logs I can only find this:
May 17 11:47:46 http.server     debug   Firing event: GET boese-ban.de/xmpp-websocket
May 17 11:47:46 c2s43a9760      info    Client connected
May 17 11:47:46 c2s43a9760      info    Client disconnected: connection closed
May 17 11:47:46 c2s43a9760      debug   Destroying session for (unknown) ((unknown)@(unknown))

Link Mauve in the prosody chat suggested that this might be related that not the latest version of the xmpp-websocket spec is used.

+1. Cannot connect to any server from otalk.im site.


Unable to use asynchronous argument with FAISS.load_local

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
import boto3
from langchain.text_splitter import RecursiveCharacterTextSplitter
from langchain_community.vectorstores import FAISS
from langchain_community.embeddings import BedrockEmbeddings

class Document():
    def __init__(self, content, source):
        self.page_content = content
        self.metadata = { 'source': source }

def data_ingestion():
    documents = [
        Document('Contents1', 'Doc1'),
        Document('Contents2', 'Doc2')
    ]

    text_splitter = RecursiveCharacterTextSplitter(
        chunk_size=10000,
        chunk_overlap=1000
    )

    return text_splitter.split_documents(documents)

def store_vectors(embeddings, documents, directory):
    vectorstore_faiss = FAISS.from_documents(
        documents,
        embeddings
    )

    vectorstore_faiss.save_local(directory)

INDEX_DIR = 'test_index'
bedrock = boto3.client(service_name='bedrock-runtime', region_name='us-west-2')
bedrock_embeddings = BedrockEmbeddings(model_id='amazon.titan-embed-text-v2:0', client=bedrock)

# Store documents
docs = data_ingestion()
store_vectors(bedrock_embeddings, docs, INDEX_DIR)

# Load documents
vector_store = FAISS.load_local(
    INDEX_DIR,
    bedrock_embeddings,
    allow_dangerous_deserialization=True,
    asynchronous=True
)

Error Message and Stack Trace (if applicable)
Traceback (most recent call last):
  File "/root/aws-doc-sdk-examples/python/example_code/bedrock-runtime/models/mistral_ai/example_code.py", line 41, in <module>
    vector_store = FAISS.load_local(
  File "/root/aws-doc-sdk-examples/python/example_code/bedrock-runtime/rag/lib/python3.10/site-packages/langchain_community/vectorstores/faiss.py", line 1098, in load_local
    return cls(embeddings, index, docstore, index_to_docstore_id, **kwargs)
TypeError: FAISS.__init__() got an unexpected keyword argument 'asynchronous'

Description
In the documentation here: https://api.python.langchain.com/en/latest/vectorstores/langchain_community.vectorstores.faiss.FAISS.html#langchain_community.vectorstores.faiss.FAISS.load_local
It says that I can use the asynchronous argument to use the async version. However, when I try it, I get the stack trace such that FAISS.init() got an unexpected keyword argument 'asynchronous'.
It is possible I am misunderstanding the usage of this feature. In the example code, I am simply trying to call load_local with this argument.
System Info
"pip freeze | grep langchain"
langchain==0.2.1
langchain-aws==0.1.4
langchain-community==0.2.0
langchain-core==0.2.0
langchain-text-splitters==0.2.0
langchainhub==0.1.15
Platform: Ubuntu 20.04.6 LTS
Python Version: 3.10.14

After reading the code in faiss.py, I suspect that the documentation about the parameter "asynchronous: whether to use async version or not" is an error and should be removed.
the functions "save_local" and "load_local" themselves do not have an async version, but once you get an instance of the FAISS object, you can do most of the things using "await vector_store." like
await vector_store.aadd_texts(<arguments>)


Changed the footer of event page

I have deleted the history folder which got added without my knowledge. I have edited the footer of the event page. Let me know if any changes needed

Thanks


omit_local_variable_type quick fix should be smarter

It just drops the local variable type; but sometimes the information needs moving to preserve it:
List<int> x = []; --> var x = [] loses information
It should be fixed to: var x = <int>[];
(I just verified w/this exact example).
Thanks!

https://dart-review.googlesource.com/c/sdk/+/247968


Document approach to service accounts in Snowflake

In collaboration with @Thea-S-Man, document our approach to provisioning and managing service accounts:

How they are provisioned
How to create key pairs
How to assign appropriate roles
Where to store credentials
Any rotation policies
Documenting TLS usage

Next steps: @melanie-logan will contact Thea to confirm the right format.

Meeting with @Thea-S-Man scheduled 1/3/2024.


unavailable

There's no print in the log. I was deployed by helm

Hi @puleiC  i believe this is the issue with BRMS not running in secure context (https). Some browser apis that we use require secure connection / with certificate to be able to run properly.
I believe for testing you can run a chrome in unsecure mode. We will see how to solve this so that brms can run on non https connectections.

@ivanmiletic Thank you for your reply. The problem has been solved. It is the http problem that causes the unavailability. I suggest that you add deployment tips related to https

We will try to update documentation, please bear with us. - we have a few big features coming over next couple of months together with team scaling and also working with our enterprise customers.


Binary/Text mode readers and writers in IO

This is needed for binary formats and shouldn't be the users concern.

Fixed in #963.


Check for Magic SDK Extension version compatibility at runtime

✅ Prerequisites

[x] Did you perform a cursory search of open issues? Is this feature already requested elsewhere?
[x] Are you reporting to the correct repository (magic-sdk)?

✨ Feature Request
Because we need to support magic-sdk and @magic-sdk/react-native as separate entries, we cannot make use of the peerDependencies field of package.json without adding noisy (and perhaps alarming) warnings to every developer's install process. I've explored the use of optionalDependencies as well, but this does not produce the desired behavior (acts like dependencies instead of peerDependencies and does not hoist in the node_modules structure).
Another option is to check the compatible SDK version at runtime. We can do this by introducing a static supported member on the BaseExtension class, then use semver to perform the check. An incompatible version should produce a SDK warning (not an exception).

Related to #39

:rocket: Issue was released in<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


Fix bug in Show creation when summary is not available

_remove_tags cannot operate on None values, it needs a string.

Merged into dev, might be pushing some more changes tomorrow so I'm going to wait to merge to master.  Thanks for this!


adding Le Petit Prince to public repo

Mods (relative to the version on private cognitive_protocols repo):

some reorganisation
added English translations for instructions and attention questions
compiled scattered readmes into one README.md
removed participant_answers sub-dir

TODO:

upload audio files for runs 1-9 from scanner PC (?) add OpenNeuro link to audio files when available
localizer does not run in the first attempt from the bash script - requires running the python script separately first

I just wanted to confirm if we are okay with uploading the audio files to this repo.
As of now, they are only available on the 3T stimulation PC.

You should ask Christophe whether this is legal.
Best,

OK, will do. Thanks!

Hey! Bringing this discussion back.
The discussion is whether upload the audio files to this repo or just point to Christophe's OpenNeuro site where all the files already are. @bthirion @man-shu


NPM For Discord RPC is Down !

NPM For Discord RPC is Down !
When you try to install DiscordRPC from NPM it refers to an unfound repository....
PS C:\Users\Afi\Desktop\RPC> npm install discord-rpc
info: please complete authentication in your browser...-session b8d56d1fc3f9bc96
npm ERR! Error while executing:
npm ERR! F:\App\Git\Git\cmd\git.EXE ls-remote -h -t https://github.com/djs/discord-rpc.git
npm ERR!
npm ERR! remote: Repository not found.
**npm ERR! fatal: repository 'https://github.com/djs/discord-rpc.git/' not found**
npm ERR!
npm ERR! exited with error code: 128

npm ERR!      C:\Users\Afi\AppData\Roaming\npm-cache\_logs\2021-02-08T22_22_58_712Z-debug.log

This repo is for the official discord-rpc C++ library, the JS library on npm is separate, try its Discord server or GitHub repo

Ok thanks


Describe the wallet instance lifecycle, the interaction between the wallet instance and the wallet provider

@rohe 's
In the description of the wallet instance lifecycle the interaction between the wallet instance and the wallet provider is omitted. Shouldn't it be part of the initialization process ? This is in https://github.com/italia/eudi-wallet-it-docs/blob/versione-corrente/docs/en/wallet-solution.rst

The interaction between the wallet instance and the wallet provider is described in the Wallet Instance Attestation paragraph along with a sequence diagram as well.


SagaTestFixture extend APIs for publishing historic events with metadata

This change allows the usage of metadata in the saga test fixture when using the givenAPublished GivenState. To do this currently, there is only the workaround to do sth. like:
fixture.givenAggregate("id")
.published()
.andThenAPublished(orderCreatedEvent, MetaData.emptyInstance())

fixes #3197

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Praegla, Alexander seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fixed numpy pin

This PR fixes the numpy pin under host - the trick is to just use numpy in host spec, which should build with 1.9.x, see https://conda-forge.org/docs/meta.html#building-against-numpy.

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

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


Replace build workflow with plugin_test

This PR is part of asdf-community/.github/issues/2

Replaced build workflow with plugin_test workflow
updated checkout action

@all-contributors please add @Naturalclar for infra


Remove unsafe transmute

Missed this in my last PR, sorry for the noise.

Side note: I don't know if you have a reason to not enable issues on this repo, but it would be nice, especially for the random stack overflow I just got while trying to run bindgen on bullet physics.

Just flipped the switch on issues. It was just defaulted to off after forking.

Cool, thanks!


Fix gdal binaries

Adding separate gdal jar files for each platform, because they are apparently different
The Gdal2tiles build.gradle file has changed to detect the platform and load the appropriate gdal jar
Had to comment-out some tests for CLI that were linux-only

This change is

Coverage remained the same at 53.656% when pulling 2b3802c17b73cd2c7dd1f84448d7ce3b53b4a65e on fix-gdal-binaries into 1a3a978b0873e972c4fef89304d21c0687583fc9 on master.


The problem with events.

If depending on conditions the element is replaced by another and oldTag.name === newTag.name, then old events saved.
Bug example: http://jsfiddle.net/zrmu855c/1/

@RubaXa Confirmed! Great catch, I will have a fix in for this tonight. There is a @todo in the code directly related to this:
https://github.com/developit/preact/blob/master/src/preact.js#L925
Thanks for giving me a simple way to reproduce it!

@RubaXa This fix has landed in the 3.0 beta branch. Please test via npm i preact@beta if possible, thanks!

:ok_hand:

Thanks for your demo fiddle, that helped immensely. Here's the same code running on preact 3.0 (preact@beta), and it now works as intended:
http://jsfiddle.net/developit/zrmu855c/2/


BoF OSCON 2016 @Austin

We're holding a Birds of a Feather session on May 18th 7pm in Meeting Room 5.
If anyone from the community is headed to Austin for OSCON and wishes to stop by, please let us know!
Feel free to post any questions you want so we can come prepared.

pinpoint_OSCON_BoF.pdf

Done!


Support LoadBalance mode

Support load balance according to what proposed in https://github.com/Azure/AppConfiguration/issues/868

It's supported in version 2.1.0

@linglingye001 please update the document
https://learn.microsoft.com/en-us/azure/azure-app-configuration/howto-geo-replication?tabs=kubernetes#load-balance-with-replicas


[Doc]: Text field documentation consistency

Documentation Location
https://orange-opensource.github.io/ods-ios/components/textSelection_docs
Current issue
the side bar navigation and page title are not consistant
Expected Correction
the "Text field" wording should be used everywhere
Additional context
the file name should also be changed, but we need to update the DSM when this is pushed to production.

As we reviewed the text inputs (text fields and text editor), and remove the text selection. This issue can be ignored.


Correcting links in dns-overview.md

Links in the 'Next steps' section were incorrect. This commit updates them to be accurate.

#sign-off


Hexxen-1733-Ulisses-Spiele(Official) - New Feature (new role: parazoologist)

Submission Checklist
Required

[ x ] The pull request title clearly contains the name of the sheet I am editing.
[ x ] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[ x ] The pull request makes changes to files in only one sub-folder.
[ x ] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ x ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ x ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: https://www.f-shop.de/hexxen-1733/regel-und-quellenbaende/3130/hexxen-1733-handbuch-der-parazoologie
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description
I added the recently published role of parazoologist (translations only in german).

Character Sheet Info Roll20 Internal Use only.

@Gorthian @CodenameSupreme @coolguyinlove are you folks food with this pull request?

@Gorthian @CodenameSupreme @coolguyinlove Checking in one more time, we're gonna go ahead and merge this if there're no objections.

No objections from me, but I'm not in charge on this sheet.

I've asked our publisher relations team to reach out to Ulisses Spiele to get clarity on this given that nobody seems to know who authorizes on this sheet.

Got confirmation from Ulisses and they've authorized the change.

Not part of our team but the added role does exist and the change can be merged.

Internal reference: C7PJZKX1U


Build of tensorrt-cu12 fails with "No module named pip"

uv: 0.2.33
python: 3.9.19
I have the following in my requirements.txt:
# Minimal pip requirement list for AMPL with CUDA-enabled GPUs. This includes only the packages directly imported by AMPL code, plus a few others commonly used during development. It requires CUDA-enable GPUs and nvidia packages to be installed first.
-i https://download.pytorch.org/whl/cu118
--extra-index-url https://pypi.python.org/simple
# **Note**: for LC developers, comment out line 3 pypi install and use/uncommenting line 5:
#--extra-index-url https://wci-repo.llnl.gov/repository/pypi-group/simple
-f https://storage.googleapis.com/jax-releases/jax_cuda_releases.html
-f https://data.dgl.ai/wheels/cu118/repo.html

absl-py==2.1.0
aiohttp==3.9.5
aiosignal==1.3.1
arrow==1.3.0
asttokens==2.4.1
astunparse==1.6.3
async-timeout==4.0.3
attrs==23.2.0
bokeh==3.4.1
bravado==11.0.3
bravado-core==6.1.1
cachetools==5.3.3
certifi==2024.2.2
charset-normalizer==3.3.2
cloudpickle==3.0.0
cmake==3.29.3
coloredlogs==15.0.1
comm==0.2.2
contourpy==1.2.1
cycler==0.12.1
debugpy==1.8.1
decorator==5.1.1
deepchem==2.7.1
dgl==1.1.2+cu118
dgllife==0.3.2
dill==0.3.8
exceptiongroup==1.2.1
executing==2.0.1
filelock==3.14.0
flatbuffers==24.3.25
fonttools==4.52.4
fqdn==1.5.1
frozenlist==1.4.1
fsspec==2024.5.0
future==1.0.0
gast==0.5.4
google-auth==2.29.0
google-auth-oauthlib==1.0.0
google-pasta==0.2.0
grpcio==1.64.0
h5py==3.11.0
humanfriendly==10.0
hyperopt==0.2.7
idna==3.7
importlib_metadata==7.1.0
importlib_resources==6.4.0
ipykernel==6.29.4
ipython==8.18.1
isoduration==20.11.0
jax==0.4.16
jaxlib
jedi==0.19.1
Jinja2==3.1.4
joblib==1.4.2
jsonpointer==2.4
jsonref==1.1.0
jsonschema==4.22.0
jsonschema-specifications==2023.12.1
jupyter_client==8.6.2
jupyter_core==5.7.2
keras==2.14.0
kiwisolver==1.4.5
libclang==18.1.1
lightning==2.2.5
lightning-utilities==0.11.2
lit==18.1.6
llvmlite==0.42.0
maestrowf==1.1.10
Markdown==3.6
markdown-it-py==3.0.0
MarkupSafe==2.1.5
matplotlib==3.9.0
matplotlib-inline==0.1.7
matplotlib-venn==0.11.10
mdurl==0.1.2
ml-dtypes==0.2.0
MolVS==0.1.1
monotonic==1.6
mordred==1.2.0
mpmath==1.3.0
msgpack==1.0.8
multidict==6.0.5
nest-asyncio==1.6.0
networkx==2.8.8
numba==0.59.1
numpy==1.24.4
nvidia-cublas-cu11
nvidia-cuda-cupti-cu11==11.8.87
nvidia-cuda-nvcc-cu11==11.8.89
nvidia-cuda-runtime-cu11==11.8.89
nvidia-cudnn-cu11==<IP_ADDRESS>
nvidia-cufft-cu11==<IP_ADDRESS>
nvidia-cusolver-cu11==<IP_ADDRESS>
nvidia-cusparse-cu11==<IP_ADDRESS>
oauthlib==3.2.2
opt-einsum==3.3.0
packaging==24.0
pandas==2.2.2
parso==0.8.4
pexpect==4.9.0
pillow==10.3.0
platformdirs==4.2.2
prompt_toolkit==3.0.45
protobuf==4.25.3
psutil==5.9.8
ptyprocess==0.7.0
pure-eval==0.2.2
py4j==<IP_ADDRESS>
pyarrow==16.1.0
pyasn1==0.6.0
pyasn1_modules==0.4.0
Pygments==2.18.0
pynndescent==0.5.12
pyparsing==3.1.2
python-dateutil==2.9.0.post0
pytorch-lightning==2.2.5
pytz==2024.1
PyYAML==5.4.1
pyzmq==26.0.3
rdkit==2023.9.6
referencing==0.35.1
requests==2.32.3
requests-oauthlib==2.0.0
rfc3339-validator==0.1.4
rfc3986-validator==0.1.1
rich==13.7.1
rpds-py==0.18.1
rsa==4.9
scikit-learn==1.2.2
scipy==1.8.1
seaborn==0.13.2
simplejson==3.19.2
six==1.16.0
stack-data==0.6.3
swagger-spec-validator==3.0.3
sympy==1.12.1
tabulate==0.9.0
tensorboard==2.14.1
tensorboard-data-server==0.7.2
tensorflow==2.14.0
tensorflow-estimator==2.14.0
tensorflow-io-gcs-filesystem==0.37.0
tensorrt==10.0.1
tensorrt-cu12==10.0.1
termcolor==2.4.0
threadpoolctl==3.5.0
torch==2.*
torch_geometric==2.5.3
torchmetrics==1.4.0.post0
tornado==6.4
tqdm==4.66.4
traitlets==5.14.3
triton==2.*
types-python-dateutil==<IP_ADDRESS>40316
typing_extensions==4.12.0
tzdata==2024.1
umap-learn==0.5.6
uri-template==1.3.0
urllib3==2.2.1
wcwidth==0.2.13
webcolors==1.13
Werkzeug==3.0.3
wrapt==1.14.1
xgboost==2.0.3
xyzservices==2024.4.0
yarl==1.9.4
zipp==3.19.0

running uv pip install leads to the following:
DEBUG Calling `setuptools.build_meta:__legacy__.build_wheel("/home/herman/.cache/uv/built-wheels-v3/index/dcd4cb247a731f5c/tensorrt-cu12/10.0.1/jOoT6AHZgjt1wIPlJCiVw/.tmpOG6WPI", {}, None)`
error: Failed to prepare distributions
  Caused by: Failed to fetch wheel: tensorrt-cu12==10.0.1
  Caused by: Failed to build: `tensorrt-cu12==10.0.1`
  Caused by: Build backend failed to build wheel through `build_wheel()` with exit status: 1
--- stdout:
running bdist_wheel
running build
running build_py
copying tensorrt/__init__.py -> build/lib/tensorrt
running egg_info
writing tensorrt_cu12.egg-info/PKG-INFO
writing dependency_links to tensorrt_cu12.egg-info/dependency_links.txt
writing requirements to tensorrt_cu12.egg-info/requires.txt
writing top-level names to tensorrt_cu12.egg-info/top_level.txt
reading manifest file 'tensorrt_cu12.egg-info/SOURCES.txt'
adding license file 'LICENSE.txt'
writing manifest file 'tensorrt_cu12.egg-info/SOURCES.txt'
installing to build/bdist.linux-x86_64/wheel
running install
--- stderr:
/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/bin/python: No module named pip
/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/bin/python: No module named pip
Traceback (most recent call last):
  File "<string>", line 11, in <module>
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/build_meta.py", line 420, in build_wheel
    return self._build_with_temp_dir(
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/build_meta.py", line 402, in _build_with_temp_dir
    self.run_setup()
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/build_meta.py", line 502, in run_setup
    super().run_setup(setup_script=setup_script)
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/build_meta.py", line 318, in run_setup
    exec(code, locals())
  File "<string>", line 121, in <module>
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/__init__.py", line 111, in setup
    return distutils.core.setup(**attrs)
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 184, in setup
    return run_commands(dist)
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 200, in run_commands
    dist.run_commands()
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 964, in run_commands
    self.run_command(cmd)
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/dist.py", line 948, in run_command
    super().run_command(command)
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 983, in run_command
    cmd_obj.run()
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/command/bdist_wheel.py", line 419, in run
    self.run_command("install")
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
    self.distribution.run_command(command)
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/dist.py", line 948, in run_command
    super().run_command(command)
  File "/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 983, in run_command
    cmd_obj.run()
  File "<string>", line 73, in run
  File "<string>", line 42, in run_pip_command
  File "/usr/local/lib/python3.9/subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/home/herman/.cache/uv/builds-v0/.tmpg2iSa0/bin/python', '-m', 'pip', 'install', '--extra-index-url', 'https://pypi.nvidia.com', 'tensorrt-cu12_libs==10.0.1', 'tensorrt-cu12_bindings==10.0.1']' returned non-zero exit status 1.

Here's the full log: log.txt
However, this seems to work fine and install without uv
Let me know if you need any more info

Looks like tensorrt-cu12 has a build requirement on pip that it does not declare. You'll need to use --no-build-isolation and install all of the build dependencies manually. This would probably fail to install via pip with PEP 517 enabled (`--use-pep517). See #2252.

wow thanks for the quick response!

No problem! Let me know if you have any more questions.


Nick: Watch documentaryhomes.com

Nick requests the watch of the watch_keyword documentaryhomes\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

documentaryhomes\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Use a working license instead of UNLICENSE

[I posted this in your Reddit thread, but it should be an actual issue.]
Please don't use UNLICENSE for your license. It doesn't actually work. All uses of UNLICENSE can be replaced with uses of the Apache 2 license (which actually works); you get the same "do whatever you want with it" support without causing your users pain because your license makes no legal sense.
Apache 2 really is what you want; unlike the MIT license, it covers the following as well:

Any patches you receive are also licensed under Apache 2. MIT says nothing on this and thus leaves any project using it in a weird state after merging in external contributions.
It gives a patent license as well.
Other minor useful tidbits.

I've made the mistake of using UNLICENSE myself before; learn from my experience.

Hi, Andrew.  If you are willing to consider an alternative, Rob Landley created for the toybox project the '0BSD' license (Zero-Clause BSD License) by removing a requirements clause from 2-clause BSD, and resulting in text running about ten lines.  Moreover, it's already an OSI Certified licence, albeit OSI hasn't yet cleared up some lingering name confusion.
Several years on, my (referenced) damning legal critique of Unlicense on the license-review mailing list still looks to me, IMO, fully merited, but I absolutely applaud your wish to use a copyfree licence.  Maybe 0BSD will be your cuppa.  (copyfree.org lists it as 'Toybox License'.  As I said, there's a lingering name issue being cleared up:  Rob is working on getting everyone to standardise on 0BSD as the short name, and Zero-Clause BSD License as the full name.)
-- Rick Moen
<EMAIL_ADDRESS>

Hi, Andrew. If you are willing to consider an alternative, Rob Landley created
for the toybox project the '0BSD' license (Zero-Clause BSD License) by removing
a requirements clause from 2-clause BSD, and resulting in text running about
ten lines. Moreover, it's already an OSI Certified licence, albeit OSI hasn't
yet cleared up some lingering name confusion.
Several years on, my (referenced) damning legal critique of Unlicense on the
license-review mailing list still looks to me, IMO, fully merited, but I
absolutely applaud your wish to use a copyfree licence. Maybe 0BSD will be
your cuppa. (copyfree.org lists it as 'Toybox License'. As I said, there's a
lingering name issue being cleared up: Rob is working on getting everyone to
standardise on 0BSD as the short name, and Zero-Clause BSD License as the full
name.)
-- Rick Moen
<EMAIL_ADDRESS>
@rickmoen Thanks for responding, but based on your mailing list posts from 2012, and assuming your perspective hasn't changed, then it's clear to me that we're coming at this from very different angles. The fundamental crux at which we disagree is captured fairly succinctly in this part of your correspondence:

And that's the pity of it:  Using a very simple standard permissive
licence such as MIT/X11 License or even a peculiar and cramped but
somewhat standard 3-line licence like Fair Licence achieves everything
Bendiken and others want (and actually escape warranty liability)
except for the ideological point about getting 'out of the copyright
game'.
And because of that ideological hobbyhorse, everyone's time gets wasted.

Given that, and given the clear condescension expressed towards the type of perspective I hold here, I'm not sure it's particularly productive to discuss this further.
Moreover, about 3 years ago, I dual licensed this project under the MIT and the UNLICENSE, which should assuage the practical concerns others have made. I did the same for most of my other projects, and since then, plenty of folks---including large corporations with huge legal infrastructure devoted to figuring out which software licenses are acceptable for them to use---have had no problem using my code.
I've elaborated a bit on my licensing choice in a different project of mine here: https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#license

Andrew, I'm glad to clarify (and repeat) that I have nothing but respect for your and others' desire to achieve maximally permissive & terse software licensing.  I'm totally sincere about that, and have consistently so said in public and private.
My sharp criticism (call it condescension if you wish) has been restricted to ignominious failures to address that need, that fail for lack of attention to legal basics, such as WTFPL and Unlicense.  Those licences' structural defects are both gravely fatal and pretty much not disputed by anyone familiar with basics of software licensing and copyright law -- which, like death and taxes, don't go away merely because one dislikes them.
MIT License is excellent, of course -- and about 13 lines of standard ASCII text.  Hypothetically switching to 0BSD would shrink that to about 10 lines, FWIW.

Andrew, I'm glad to clarify (and repeat) that I have nothing but respect for your and others' desire to achieve maximally permissive & terse software licensing. I'm totally sincere about that, and have consistently so said in public and private.

I get that. But I hope it's also clear that I use the Unlicense for at least partially ideological reasons. It is specifically intended as a protest against monopoly copyright interest. Neither the 0BSD nor the MIT achieve that. To you, this is a waste of time. That's a fair position to take; I don't even disagree with it 100%. I'm not that big on activism. But this is one position I've found I can take without actually giving up much, specifically because of the dual licensing with a widely recognized license (MIT).
The point of me using MIT is to hedge against situations where the Unlicense isn't acceptable for one reason or another (perhaps because some legal professional declared it to be unsuitable). To that end, I don't think there is any better choice, including the 0BSD, simply on grounds of broad appeal alone.

which, like death and taxes, don't go away merely because one dislikes them.

For what it's worth, this is the kind of condescension that I find really unappealing. Presumably you're hear to convince me of something.  Whether that's your intent or not, that's how you come across to me. In particular, I'm well aware that the practice of law has absolutely nothing to do with whether I disagree with it or not. However, sometimes laws (or norms) should change, and the only way for that to happen is for someone to act against the status quo. Therefore, your descriptive argument is completely barking up the wrong tree, because I'm making a prescriptive argument.
Now, maybe there exists a better way to stake my ideological ground. Maybe there should be an Unlicense2 that addresses your concerns. So long as the goal is to disclaim monopoly copyright interest, I'd be happy to support that. But I don't know of any such effort, and I certainly do not want to add yet another license to the fray myself. :-)

For what it's worth, this is the kind of condescension that I find really unappealing.

I'm typically Scandinavian-American in the sense of habitually telling perceived truths bluntly.  If you want a salesman or flattery, that's somebody else.
And no, I'm not trying to convince you of anything.  There's nothing in that for me.  I'm just stating my views because it's on a topic of longtime interest to me, because you kindly permit it, and so others will probably find what I'm saying.
Your ideological position is all very well, and I don't differ with it in any way.  I wish the global copyright regime would get out of our way, too.  But meanwhile, if writing software and not wishing to create nasty future legal pitfalls for downstream users and redistributors, it's IMO wise to use competent licensing for the same reason one sticks to competently assembled and maintained cars when driving rather than driving an incompetently built one as a protest for ideological reasons.
Or, at least, if you do, someone's likely to have a bad day.

it's IMO wise to use competent licensing for the same reason one sticks to competently assembled and maintained cars when driving rather than driving an incompetently built one as a protest for ideological reasons.

That's why I dual license and it's also why I drive a Camry.

I'm typically Scandinavian-American in the sense of habitually telling perceived truths bluntly. If you want a salesman or flattery, that's somebody else.

If your "perceived truth" is that I think the practice of law depends on whether I dislike it or not, then you very clearly must think of me as a blubbering idiot.
Here's my perceived truth: the absence of condescension is not the same as the presence of salesmanship or flattery.

Thanks for explaining that in more detail. I'm generally happy to see copyfree licenses get more press.
With that said, we'll have to agree to disagree on how we perceive the world. You see naiveté, but I see rebellion. Rebellion comes in many shapes and sizes, and for it to succeed, you generally need to sacrifice something. Maybe that comes in the form of real world software using sub-optimal software licenses. I am a terrible activist though; which is why I ultimately caved and dual licensed.
 You have an opportunity to educate folks on license choices, but instead you lace it with invective. It's completely distracting. Be blunt. Be honest. Don't sugar coat it. But don't snub your nose at the people you're trying to educate.

  On a fairly lengthly search, I can't find examples.
Nor, actually, would that make any sense in light of what I've been saying:  There's nothing of stupidity implied by choosing unsuitable tools for a task, when one is far outside one's field, but hasn't realised why leveraging the work of domain-knowledge experts is crucial.
The only people I come somewhat close to derogating are Mr. Sam Hocevar, author of WTFPL v.2, whose effort produced a hapless failure for lack of attention to basic detail, and Mr. Joe Brockmeier, who meant well and missed the target but less badly than Sam did.  Even them, I certainly wouldn't call stupid, just tragically inept in a way likely to cause much bigger problems for others than for themselves.
Along those lines, as to what software stakeholders sacrifice in choosing legally flawed licensing in hopes of making a point, I respect that choice right up to the point where they negligently leave legal pitfalls for downstream code reusers, which IMO is morally suspect.  YMMV.

That's enough. I've done my best to express my distaste for how you're choosing to continue this conversation, but it's not working. You keep continuing to spew invective and proffer unsolicited opinions on not only entire social groups, but now you're targeting specific individuals. This goes way beyond spreading the word about copyfree licenses, which I'm totally happy to indulge. From my perspective, your social commentary is inflammatory and a waste of my time to read. Please do not bother me with it again.


Haiku Patches

This PR is an attempt to update the previous PR to the latest Vim version. This version builds fine on bare install with ./configure [args] && make install, but there are still a few quirks:

GUI does not build
vimrc & plugins do not work.

For plugins and vimrc, previous haikuports recipe uses a workaround on line 150, but I was not able to successfully apply that to this version yet. I'm not sure how the code in misc1.c applies to this.
For the GUI, the previous version on Haikuports build fine, but I am still not sure what is wrong with the bare version. I've made a couple of additions to the code to make sure Haiku-specific files are counted, alas no luck. Any guidance on this would be appreciated!
To build on Haiku, just follow the instructions in runtime/doc/os_haiku.txt.
To try Haiku itself, feel free to download and install the latest nightly images from here!
I hope to improve the documentation once above two issues have been resolved.
Thank you!

Codecov Report

Merging #5605 into master will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5605      +/-   ##
==========================================
- Coverage   83.17%    83.1%   -0.07%
==========================================
  Files         137      137
  Lines      152067   152024      -43
==========================================
- Hits       126476   126337     -139
- Misses      25591    25687      +96

Impacted Files
Coverage Δ

src/mbyte.c
66.53% <ø> (-0.2%)
:arrow_down:

src/menu.c
73.41% <ø> (ø)
:arrow_up:

src/os_unix.c
63.36% <ø> (-0.27%)
:arrow_down:

src/fileio.c
82.05% <ø> (ø)
:arrow_up:

src/screen.c
84.59% <ø> (-0.04%)
:arrow_down:

src/evalfunc.c
91.69% <ø> (-0.1%)
:arrow_down:

src/mouse.c
76.67% <ø> (-0.12%)
:arrow_down:

src/version.c
92.1% <ø> (ø)
:arrow_up:

src/term.c
80.74% <ø> (-0.82%)
:arrow_down:

src/misc1.c
83.42% <ø> (ø)
:arrow_up:

... and 37 more

Continue to review full report at Codecov.

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

BSD make doesn't like it: make[1]: "/tmp/cirrus-ci-build/src/Makefile" line 1395: Missing dependency operator
I guess you can't use +=

BSD make doesn't like it: make[1]: "/tmp/cirrus-ci-build/src/Makefile" line 1395: Missing dependency operator
I guess you can't use +=

I guess my fix did not work. :\
In the meantime, plugins and vimrc files work now, only major thing left is the GUI.

What is the proper way of auto-generating configure in Vim context? I was able to start building with GUI (failing though, output below) after an autoconf, but it overwrites the file in src/, instead of src/auto. Also the diff is quite different than the current file, it's not just the additions. See diff attached.
configure_diff.txt
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_HAIKU    -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1        -o objects/beval.o beval.c
In file included from structs.h:110,
                from vim.h:1847,
                from beval.c:11:
beval.c: In function 'get_beval_info':
beval.c:154:21: error: 'BalloonEval' {aka 'struct BalloonEvalStruct'} has no member named 'y'
 row = Y_2_ROW(beval->y);
                    ^~
gui.h:117:24: note: in definition of macro 'Y_2_ROW'
# define Y_2_ROW(y) (((y) - gui.border_offset) / gui.char_height)
                       ^
beval.c:155:21: error: 'BalloonEval' {aka 'struct BalloonEvalStruct'} has no member named 'x'
 col = X_2_COL(beval->x);
                    ^~
gui.h:113:24: note: in definition of macro 'X_2_COL'
# define X_2_COL(x) (((x) - gui.border_offset) / gui.char_width)
                       ^
Makefile:3218: recipe for target 'objects/beval.o' failed
make: *** [objects/beval.o] Error 1

What is the proper way of auto-generating configure in Vim context?

Try make autoconf.

What is the proper way of auto-generating configure in Vim context?

Try make autoconf.

This worked thanks, but the diff is the same though. It changes more than it (probably) should. GUI build fails with the same error above, CLI build completes fine.

It changes more than it (probably) should.

It may depend on version of autoconf.

@brammool, thanks for including. I will open an issue to track the GUI build failure issue.


Mat::image_encode is leaking

Hi! Thank you very much for the bindings!
I'm trying to save frames from a video stream as JPEG files, however, as soon as I uncomment the line
let bytes = mat.image_encode(".jpg", vec![])?; the app starts consuming more and more memory until it gets OOM-killed.
extern crate cv;
use cv::*;
use cv::highgui::{Show, WindowFlag};
use cv::imgcodecs::ImageWriteMode;
use std::fs::File;
use std::io::prelude::*;
use std::error::Error;

const WINDOW_NAME: &'static str = "smile";

fn main() -> Result<(), Box<Error>> {
    let capture = videoio::VideoCapture::new(0);
    let window = cv::highgui::highgui_named_window(WINDOW_NAME, WindowFlag::Opengl);

    while capture.is_open() {
        let mat = capture.read();
        if let Some(mat) = mat {
            mat.show(WINDOW_NAME, 50);
//            let bytes = mat.image_encode(".jpg", vec![])?;
//            File::create("img.jpg")?.write_all(bytes.as_slice())?;
        } else {
            break
        }
    }
    Ok(())
}

Could you please explain to me what I'm doing wrong or confirm if it is a bug?
Using OpenCV 3.4.1 with GStreamer on rust 1.28.0-nightly.

Hey there!
Can you please share CMake flags you used to build the opencv so I could reproduce?

I'm using the opencv-gstreamer package from AUR: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=opencv-gstreamer

Yep, it seems that the problem is with ImencodeResult which has C-allocated memory which gets copied into Rust one:
https://github.com/nebgnahz/cv-rs/blob/master/src/imgcodecs.rs#L143
but never gets freed.

Well, there is actually a comment 😄
https://github.com/nebgnahz/cv-rs/blob/master/native/imcodecs.cc#L18

Is there anything I could help with?

@vstepchik well, there is a branch where the fix is located: https://github.com/nebgnahz/cv-rs/tree/feature/leak_fix
Unfortunately, it's currently fails with segfault while I cannot debug it on windows for several reasons. So you have to wait until I get home and up my ubuntu VM or you can try to locate it yourself.

@nebgnahz any idea why CI fails?
+ cd /home/travis/build/nebgnahz/cv-rs/opencv-3.4.1/build
++ pwd
+ echo 'Configuring at /home/travis/build/nebgnahz/cv-rs/opencv-3.4.1/build'
Configuring at /home/travis/build/nebgnahz/cv-rs/opencv-3.4.1/build
+ cmake -D WITH_CUDA=ON -D BUILD_EXAMPLES=OFF -D BUILD_TESTS=OFF -D BUILD_PERF_TESTS=OFF -D BUILD_opencv_java=OFF -D BUILD_opencv_python=OFF -D BUILD_opencv_python2=OFF -D BUILD_opencv_python3=OFF -D OPENCV_EXTRA_MODULES_PATH=/home/travis/build/nebgnahz/cv-rs/opencv_contrib-3.4.1/modules -D CMAKE_INSTALL_PREFIX=/home/travis/usr -D CMAKE_BUILD_TYPE=Release -D CUDA_ARCH_BIN=5.2 -D CUDA_ARCH_PTX= ..
CMake Error: The source directory "/home/travis/build/nebgnahz/cv-rs/opencv-3.4.1" does not appear to contain CMakeLists.txt.

I don't see why it says that source directory is /home/travis/build/nebgnahz/cv-rs/opencv-3.4.1 when pwd is clearly /home/travis/build/nebgnahz/cv-rs/opencv-3.4.1/build

@Pzixel the fix works, it doesn't leak anymore, thank you!

@vstepchik ok, then I create a PR for it. Thank you for a report!

any idea why CI fails?

Fixing the CI now. There is nothing in /home/travis/build/nebgnahz/cv-rs/opencv-3.4.1 after we use git submodules instead of downloading the zip.

Let's keep discussion in PR.


Fix KL27Z4 target name and remove unsupported KV31 board

The boards table incorrectly listed the FRDM-KL27Z target as "kl27z" instead of "kl27z4". This is a fix to #306.
Also removed the FRDM-KV31Z board that isn't (yet) supported.

/morph test

Can one of the admins verify this patch?


[BUG] 30_max_analyzed_offset failing

What is the bug?
FAILED test_opensearchpy/test_server/test_rest_api_spec.py::test_rest_api_spec[OpenSearch-main/rest-api-spec/src/main/resources/rest-api-spec/test/search/highlight/30_max_analyzed_offset[5]]

How can one reproduce the bug?
Latest builds are failing in this REST spec.

The failing test link is here.

This failure is related to this issue.

The fix is present in opensearch 2.x, but it is unreleased. Ideally, the fix may be included in version 2.13.0 when it is released.

I believe the skip version in this test should be set to " - 2.12.99". @Xtansia, what do you think? Did I miss anything?

Additional info:

I debugged the opensearch-net client to check if this test is executed and noticed that it is skipped for all currently released opensearch versions. It is only running for the unreleased version, where it is working fine.

Regarding opensearch-rs, all yaml tests are skipped for released opensearch versions and are only running for unreleased versions.

How is the opensearch-net client correctly interpreting the skip version as " - 2.12.99" even though it is currently specified as " - 2.1.99"

Got it @Xtansia! In opensearch-net's YAML test runner, tests against each opensearch version are taken from the corresponding opensearch version, such as 2.x branch when tests are run against 2.x.
On the other hand, opensearch-py uses only yaml tests from the main branch to test all opensearch versions.
Thomas, what do you think is the correct way to test? I'm inclined towards testing all opensearch versions against the opensearch main branch yaml tests. This should be the place where we'll have all the tests correctly, including skip tests that determine whether the test should be run on a particular branch or not.

If I understand correctly OpenSearch/main and 2.x are eventually consistent and should be identical? So it shouldn't matter where we take them from. However, I think it's best if we standardized on one way of doing it.

Another thought. If OpenSearch 3.x (main) removes an API, would it be deleted from main? In that case we want to take tests from 2.x.

Listing other failing tests against the unreleased OpenSearch main branch. Working on fixing them.

FAILED test_opensearchpy/test_server/test_rest_api_spec.py::test_rest_api_spec[OpenSearch-main/rest-api-spec/src/main/resources/rest-api-spec/test/indices/forcemerge/10_basic[2]]
FAILED test_opensearchpy/test_server/test_rest_api_spec.py::test_rest_api_spec[OpenSearch-main/rest-api-spec/src/main/resources/rest-api-spec/test/search/highlight/30_max_analyzed_offset[5]]
FAILED test_opensearchpy/test_server/test_rest_api_spec.py::test_rest_api_spec[OpenSearch-main/rest-api-spec/src/main/resources/rest-api-spec/test/search/350_matched_queries[1]]

@dblock @saimedhi For both .NET & Rust this behaviour of picking the tests from the matching branch/revision of the OS cluster was inherited in the fork from Elastic. Even if main is eventually consistent, it seems evident that taking the tests intended for a given version will be more reliable.

Fixed in https://github.com/opensearch-project/opensearch-py/pull/696.


Importance of selecting a comprehensive reference

Dear scarches developers,
I was wondering that how important to select a good and comprehensive dataset as a reference to build the model upon?
If the reference missed some celltypes that exist in the latter dataset, can the model still capture the heterogeneous?
Thanks,

HI @Lesdormis
sorry for the late reply :)
I would say the reference building is really important and one has to pay attention to multiple things:

The reference should include multiple batches in order for the model to understand the notion of batch effect (have at least 2-3 studies in there)

the integration and the model that you integrate the reference is also important, try scvi first.
If the reference missed some celltypes that exist in the latter dataset, can the model still capture the heterogeneous?

yeah this possible for sure for unseen states such as disease

Thanks for the reply!


feat: add Zh Blogs

Fixes: #623
Changes:
made changes  for #470  according to https://www.docusaurus.cn/docs/api/plugins/@docusaurus/plugin-content-blog#i18n
Please review when you are available @juzhiyuan @liuxiran  @bzp2010 @Baoyuantop

Does it seem that no matter if I change Chinese or English, the blog is always displayed in English？

Does it seem that no matter if I change Chinese or English, the blog is always displayed in English？

Yes. just rechecked this https://www.docusaurus.cn/docs/api/plugins/@docusaurus/plugin-content-blog#i18n .
Please let me know if there is any change to be done.

In #623, the Expected Behaviour is:
When the current environment is in English, only English blogs are displayed, and in the Chinese environment, only Chinese blogs are displayed.

In #623, the Expected Behaviour is:
When the current environment is in English, only English blogs are displayed, and in the Chinese environment, only Chinese blogs are displayed.

yes For this behavior I followed this guide https://www.docusaurus.cn/docs/api/plugins/@docusaurus/plugin-content-blog#i18n

Does it seem that no matter if I change Chinese or English, the blog is always displayed in English？

Yes ;(

cc @guoqqqi

Hi @Baoyuantop , I have submitted another PR for this task.

Hi @KishaniKandasamy, thanks for your continuous contrition! I have translated all necessary blogs in #681 #682 #679 #678 from Chinese to English, so I will close this PR and #550 :)


ocamlPackages.labltk: init at 8.06

LablTk is an OCaml interface to the Tcl/Tk GUI framework.
homepage: http://labltk.forge.ocamlcore.org/
Motivation for this change
https://github.com/NixOS/nixpkgs/issues/43512#issuecomment-405051777
cc/ @ghasshee
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval


[BUG] Array bound warning observed in iot_test_tcp.c

Description:
Observing the array bound warning in iot_test_tcp.c (libraries/abstractions/secure_sockets/test)
Please find the attached screenshot for the warning observed.

The warning is being observed in the below line of code from iot_test_tcp.c
Line number -2509   cFakeAddress[ sizeof( clientcredentialMQTT_BROKER_ENDPOINT ) - 3 ]++;

What is the value of clientcredentialMQTT_BROKER_ENDPOINT? Assuming that you are compiling a test project, you are supposed to define it here -  https://github.com/aws/amazon-freertos/blob/main/tests/include/aws_clientcredential.h#L37

Closing for no activity, please reopen if anything new comes up


Declarations - const enum to enums

When preserving const enums (to be available in js) the exported code is identical to a standard export ofr an enum. However, typescript still fails compilation when trying to iterate over it though it will work correctly when used directly in js.
This reverts const enums to enums in our UMD declarations, which will allow any playground using enum iteration in typescript to work.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15235/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15235/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15235/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15235/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15235/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15235/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15235/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15235/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15235/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15235/merge/testResults/webgpuplaywright/index.html


Cross-Reference to the API Documentation

...wouldn't that be nice? Now I just have to figure out how I can link to specific parts of the sphinx-autoapi-generated documentation.
Related:

https://github.com/readthedocs/sphinx-autoapi/issues/442
https://github.com/orgs/executablebooks/discussions/1169

{py:obj}`bw2data.project.ProjectManager.copy_project`

does the trick. Documented here in the Sphinx pages and here in the MyST pages.


Style/RedundantLineContinuation false positive

I'm seeing a number of false positives reported by RedundantLineContinuation in 1.50.0 - eg
expect {
  worker.perform
}.to change(ClipImport, :count).by(3).and \
  not_change(AudioClip, :count)

XPath.descendant(:"trix-editor").where \
  XPath.attr(:id).equals(locator)

Expected behavior
Style/RedundantLineContinuation doesn't warn on the above code.
Actual behavior
Style/RedundantLineContinuation warns on the above code, and autocorrect tries to fix it by removing the \.
For /Users/jon/Developer/web: configuration from /Users/jon/Developer/web/.rubocop.yml
configuration from /Users/jon/Developer/web/vendor/bundle/nix-bundle/ruby/3.1.0/gems/rubocop-capybara-2.17.1/config/default.yml
Default configuration from /Users/jon/Developer/web/vendor/bundle/nix-bundle/ruby/3.1.0/gems/rubocop-1.50.0/config/default.yml
configuration from /Users/jon/Developer/web/vendor/bundle/nix-bundle/ruby/3.1.0/gems/rubocop-capybara-2.17.1/lib/../config/default.yml
configuration from /Users/jon/Developer/web/vendor/bundle/nix-bundle/ruby/3.1.0/gems/rubocop-performance-1.17.1/config/default.yml
configuration from /Users/jon/Developer/web/vendor/bundle/nix-bundle/ruby/3.1.0/gems/rubocop-performance-1.17.1/config/default.yml
configuration from /Users/jon/Developer/web/vendor/bundle/nix-bundle/ruby/3.1.0/gems/rubocop-rails-2.19.0/config/default.yml
configuration from /Users/jon/Developer/web/vendor/bundle/nix-bundle/ruby/3.1.0/gems/rubocop-rails-2.19.0/config/default.yml
configuration from /Users/jon/Developer/web/vendor/bundle/nix-bundle/ruby/3.1.0/gems/rubocop-rake-0.6.0/config/default.yml
configuration from /Users/jon/Developer/web/vendor/bundle/nix-bundle/ruby/3.1.0/gems/rubocop-rake-0.6.0/config/default.yml
configuration from /Users/jon/Developer/web/vendor/bundle/nix-bundle/ruby/3.1.0/gems/rubocop-rspec-2.19.0/config/default.yml
configuration from /Users/jon/Developer/web/vendor/bundle/nix-bundle/ruby/3.1.0/gems/rubocop-rspec-2.19.0/config/default.yml
Inheriting configuration from /Users/jon/Developer/web/.rubocop_todo.yml
Inspecting 1 file
Scanning /Users/jon/Developer/web/foo.rb
Loading cache from /Users/jon/.cache/rubocop_cache/02b1ead9d63b796a28453205933c8584967ef383/6fe223d0911b45d6ba12dfe334f169f487534acf/fe777f0a0bdd6777443f6052088d110afed2026a
C

Offenses:

foo.rb:1:1: C: [Correctable] Style/FrozenStringLiteralComment: Missing frozen string literal comment.
expect {
^
foo.rb:3:43: C: [Correctable] Style/RedundantLineContinuation: Redundant line continuation.
}.to change(ClipImport, :count).by(3).and \ ...
                                          ^
foo.rb:6:40: C: [Correctable] Style/RedundantLineContinuation: Redundant line continuation.
XPath.descendant(:"trix-editor").where \ ...
                                       ^

1 file inspected, 3 offenses detected, 3 offenses autocorrectable
Finished in 0.41214599926024675 seconds

Steps to reproduce the problem
End a line with a method name and a backslash, then arguments to that method on the next line.
RuboCop version
$ bundle exec rubocop -V
1.50.0 (using Parser <IP_ADDRESS>, rubocop-ast 1.28.0, running on ruby 3.1.2) [arm64-darwin22]
  - rubocop-capybara 2.17.1
  - rubocop-performance 1.17.1
  - rubocop-rails 2.19.0
  - rubocop-rake 0.6.0
  - rubocop-rspec 2.19.0

Looks to me like #11752.

Given foo.rb :
require "xpath"

xpath = XPath.descendant(:"trix-editor").where \
  XPath.attr(:id).equals("foo")

pp xpath

rubocop will autocorrect it to:
require "xpath"

xpath = XPath.descendant(:"trix-editor").where
XPath.attr(:id).equals("foo")

pp xpath

The former is equivalent to:
require "xpath"

xpath = XPath.descendant(:"trix-editor").where(XPath.attr(:id).equals("foo"))

pp xpath

the latter is:
require "xpath"

xpath = XPath.descendant(:"trix-editor").where()
XPath.attr(:id).equals("foo"))

pp xpath

which would raise on trying to call where() - xpath/dsl.rb:45:in where': wrong number of arguments (given 0, expected 1)`

I see. This is an unexpected behavior and I opened https://github.com/rubocop/rubocop/pull/11784 to fix it. Thank you.


Menu options for message/comment cells in ContentListingViewController

Actually this is not done in the Android app, closing. If anyone has suggestions for something that could be in a menu feel free to open this back up!


[docs] Format and examples to specify a tenant/namespace for a topic.

Added topic's name format and examples to specify a tenant and namespace of the topic.
Previously not a single mention of "namespaces" and how to specify one.
Motivation & context
Make docs easier.
I'm learning Apache Pulsar and had a confusion by the fact word "namespace" not mentioned even once in the nodejs part of the documentation. So it was impossible to know how to specify a namespace and/or tenant during topic manipulation (subscribing or connecting with a producer).
Modifications
To address this problem, I added the topic name format (based on Pulsar console output) and examples to the documentation.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation
This is modification to the documentation itself (and only).

@tuteng could you please help review this PR from the technical perspective? Thanks

@vsly-ru any progress of this PR? Thanks

@vsly-ru any progress of this PR? Thanks

Sorry, I'm not familiar how to apply this PR to a multiple branches, can you give me a hint? Thanks.

@vsly-ru any progress of this PR? Thanks

Sorry, I'm not familiar how to apply this PR to a multiple branches, can you give me a hint? Thanks.

@vsly-ru If your update applies to other versions, you can update them accordingly in different versions here.
Here is an example: https://github.com/apache/pulsar/pull/10317/files

Hi @vsly-ru any progress for the code and doc? Thanks.

Hi @vsly-ru can you take a look at our comments and make changes? Thanks

Hi @vsly-ru can you take a look at our comments and make changes? Thanks

Sorry, I have encountered a lot of unexpected problems with Pulsar, e.g. [pulsar-error] [<IP_ADDRESS>:52152 -> pulsar_ip:6650] Read failed: End of file after the app relaunch randomly (and this error isn't even mentioned anywhere), calling PulsarClient.close() crashes the app with no reason and I couldn't even close the connection properly.
So I'm busy with gradually replacing Pulsar in some critical areas of the app I'm working on.
Sorry, I don't feel like participating with such a huge problems and time lost caused by Pulsar.

@Anonymitaet Shall I create a new pr after @vsly-ru replies to this message? Thank you.

@sijia-w I've confirmed w/ eng, could you please help open another PR and update all versioned docs (from 2.2.0 to master) based on our comments? Thanks


Failed to initialize NVML: Unknown Error

It may not be linked to the docker file, but more to my docker installation, but I follow exactly the steps in your readme, and when I launch :
docker run --rm --gpus all matthewfeickert/cuda-tf-torch:cuda10.1-cudnn7-runtime-ubuntu18.04 nvidia-smi
I have :
Failed to initialize NVML: Unknown Error
Anyone already had this issue?
Thanks!

See :
https://forums.developer.nvidia.com/t/nvida-container-toolkit-failed-to-initialize-nvml-unknown-error/286219/2


Download grid:UI changes.

Remove first option : "Download with Encryption"
Second option should be only : "Download"

Resolved,

Verified this issue on Tribe app v 2.2.2(592)


TP/T0: Tenant should not be allowed to be a parent to itself & also not allow a child of a parent to be a parent of the its parent

I'm submitting a ...

[X] bug report
[ ] new feature / enhancement request
[ ] improvement request (usability, performance, tech debt, etc.)
[ ] other

Traffic Control components affected ...

[ ] CDN in a Box
[ ] Documentation
[ ] Grove
[ ] Traffic Control Client
[ ] Traffic Monitor
[X] Traffic Ops
[ ] Traffic Ops ORT
[X] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] unknown

Current behavior:

I was able edit tenant and update the tenant to be a parent to itself.
Also I was able to edit tenant to update the tenant's parent to be is child.
got 500 Internal server error
Expected / new behavior:

Should not allow/list the self to be in the parent in to/tp
not allow a child of a parent to be a parent of the its parent
An appropriate message should be displayed with Not allowed
500 Internal server error should not be displayed.
Minimal reproduction of the problem with instructions:

Anything else:

example

root
tenant 1
-- tenant 1.1

assigning tenant 1.1 as parent to tenant 1 - should not be allowed
assigning root as parent to root - should not be allowed

Did the assignment succeed? I doubt it, given the error.
Error could should be 409 Conflict in this case, imo.

through TP

TP is just passing in the info got from TO. so the underlying change is required in the TO API as well

Of course. This has two parts:
• TO shouldn't allow invalid tenancy parenting assignments (best implemented as a db constraint IMO)
• TP shouldn't show invalid options when selecting a tenant parent.

A server-side check (TO) now first checks the children of the tenant before allowing the update, will prevent the update from happening, and return an error. Fixed in #5474. However, TP still shows all tenants as a possibility.


build.sh gradle Error

I followed README's instruction but error happen.
$ ./build.sh gradle

> Task :core:compileJava FAILED
[Fatal Error] slf4j-parent-1.7.25.pom:427:6: "[xX][mM][lL]"과 일치하는 처리 명령 대상은 허용되지 않습니다.
/Users/mac0314/Desktop/Github/ship/core/src/main/java/ship/util/AergoPool.java:26: error: constructor NettyConnectStrategy in class NettyConnectStrategy cannot be applied to given types;
    final NettyConnectStrategy nettyConnectStrategy = new NettyConnectStrategy();
                                                      ^
  required: HostnameAndPort
  found: no arguments
  reason: actual and formal argument lists differ in length
/Users/mac0314/Desktop/Github/ship/core/src/main/java/ship/util/AergoPool.java:29: error: cannot find symbol
    nettyConnectStrategy.setConfiguration(configuration);
                        ^
  symbol:   method setConfiguration(Configuration)
  location: variable nettyConnectStrategy of type NettyConnectStrategy
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
2 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':core:compileJava'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/4.10/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 1s
5 actionable tasks: 4 executed, 1 up-to-date

I thought it's gradle incompatible error so that I append code "--warning-mode all" to build.sh.
function execute-gradle() {
  $PROJECT_HOME/gradlew clean build test alljacoco --warning-mode all
}

But error still happen.
This is the log.
$ ./build.sh gradle

> Configure project :
As part of making the publishing plugins stable, the 'deferred configurable' behavior of the 'publishing {}' block is now deprecated. has been deprecated. In Gradle 5.0 the 'enableFeaturePreview('STABLE_PUBLISHING')' flag will be removed and the new behavior will become the default. Please add 'enableFeaturePreview('STABLE_PUBLISHING')' to your settings file and do a test run by publishing to a local repository. If all artifacts are published as expected, there is nothing else to do. If the published artifacts change unexpectedly, please see the migration guide for more details: https://docs.gradle.org/4.10/userguide/publishing_maven.html#publishing_maven:deferred_configuration.
        at build_en353ssb0ak1x71osv4fg3ojx$_run_closure3.doCall(/Users/mac0314/Desktop/Github/ship/build.gradle:48)
        (Run with --stacktrace to get the full stack trace of this deprecation warning.)
Gradle now uses separate output directories for each JVM language, but this build assumes a single directory for all classes from a source set. This behaviour has been deprecated and is scheduled to be removed in Gradle 5.0.
        at build_en353ssb0ak1x71osv4fg3ojx$_run_closure3$_closure21.doCall(/Users/mac0314/Desktop/Github/ship/build.gradle:181)
        (Run with --stacktrace to get the full stack trace of this deprecation warning.)

> Task :core:compileJava FAILED
[Fatal Error] slf4j-parent-1.7.25.pom:427:6: "[xX][mM][lL]"과 일치하는 처리 명령 대상은 허용되지 않습니다.
Detecting annotation processors on the compile classpath has been deprecated. Gradle 5.0 will ignore annotation processors on the compile classpath. The following annotation processors were detected on the compile classpath: 'lombok.launch.AnnotationProcessorHider$AnnotationProcessor'.  Please add them to the annotation processor path instead. If you did not intend to use annotation processors, you can use the '-proc:none' compiler argument to ignore them.
/Users/mac0314/Desktop/Github/ship/core/src/main/java/ship/util/AergoPool.java:26: error: constructor NettyConnectStrategy in class NettyConnectStrategy cannot be applied to given types;
    final NettyConnectStrategy nettyConnectStrategy = new NettyConnectStrategy();
                                                      ^
  required: HostnameAndPort
  found: no arguments
  reason: actual and formal argument lists differ in length
/Users/mac0314/Desktop/Github/ship/core/src/main/java/ship/util/AergoPool.java:29: error: cannot find symbol
    nettyConnectStrategy.setConfiguration(configuration);
                        ^
  symbol:   method setConfiguration(Configuration)
  location: variable nettyConnectStrategy of type NettyConnectStrategy
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
2 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':core:compileJava'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s
5 actionable tasks: 4 executed, 1 up-to-date

My gradle version
------------------------------------------------------------
Gradle 4.8.1
------------------------------------------------------------

Build time:   2018-06-21 07:53:06 UTC
Revision:     0abdea078047b12df42e7750ccba34d69b516a22

Groovy:       2.4.12
Ant:          Apache Ant(TM) version 1.9.11 compiled on March 23 2018
JVM:          1.8.0_171 (Oracle Corporation 25.171-b11)
OS:           Mac OS X 10.13.6 x86_64

Thank you for your reporting.
Your analysis is wrong.
It just fail to build becase ship and heraj's version are not matched. Ship always follows up heraj's update as soon as possible.
The build was broken during short term and it had been fixxed.
The "--warning-mode all" option is showing every warnings. It makes no effect to build result.
This kinds of broken will be disappeared after versioning. We are ready for v0.8 in end of Nov.

Thank you for your kind reply!
On Mon, Oct 22, 2018 at 8:15 PM bonyong lee<EMAIL_ADDRESS>wrote:

Thank you for your reporting.
Your analysis is wrong.
It just fail to build becase ship and heraj's version are not matched.
Ship always follows up heraj's update as soon as possible.
The build was broken during short term and it had been fixxed.
The "--warning-mode all" option is showing every warnings. It makes no
effect to build result.
This kinds of broken will be disappeared after versioning. We are ready
for v0.8 in end of Nov.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aergoio/ship/issues/1#issuecomment-431800415, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AO-VMfwQcOTr_S8QY8wMk3AsxvQM5R3Rks5unajsgaJpZM4Xdcsy
.


Why shouldnt we use a password with nanopool?

Why shouldnt we use a password with nanopool?
Title says it all
Thank you!

Do you mean a password in the 'Extra data' field (technically the email) to change the minimum payout or do you mean a password as in the 'Password' field? If the latter then it's because Nanopool doesn't use the password field for anything nor do they support having anything in it.

The extra data field for changing minimum payout

You can do that but usually it's recommended to mine with a password on your own computer until you can change the minimum payout and then spread a miner without the password since otherwise anyone who checks the connection of the miner can see the password and change the minimum payout.

got it, so if i mine to 10 rating with t-rex miner with a password, I will be able to change my minimum payout, then spread without any extra data?

Yes exactly.

Thank you so much for the fast replies!

Im not able to add a password while someone else is mining correct? Also for the advanced parameters when i want to add --report-hashrate should i remove  --response-timeout=30 --farm-retries=30 ?

Yeah if someone is already mining with a worker name then that will block you from changing the minimum payout if that worker name has another or no password. For the --report-hashrate you can just add it after the two already existing ones.

Thanks!

Sorry I keep reopening this, But I have a worker that has a high rating and no email, and its offline, but I am trying to add a password right now using my worker hehe and eddy But it keeps saying incorrect password, is it probable that CDESKTOP41 is preventing me from doing this?
https://eth.nanopool.org/account/0x77a3343dd18b63c957f22e14f3c50fa014fc498b

hehe is online at the time of writing this*

Yes, even offline workers will prevent it since they don't have the same password. To change the minimum payout all workers in the list have to have the same password. Workers are removed from the list if they are offline for more than 2 days.

Thank you!


pkg/endpoint: wait for security identity on restore

If the KVStore connectivity is not reliable during the endpoint restore
process Cilium can end up with an endpoint in a 'restoring' state in
case the ep's security identity resolution fails.
Adding a controller will make sure Cilium will retry to get an identity
for that endpoint until the endpoint is removed or the connectivity
with the allocator is successful.
Signed-off-by: André Martins<EMAIL_ADDRESS>avoid having endpoints in 'restoring' state in case the connectivity with the KVStore is not reliable

test-me-please

test-me-please

Dropping the needs-backport/1.6 label due the lack of the 'context' field in the endpoint structure (introduced in Cilium >=1.7)

@tgraf https://github.com/cilium/cilium/pull/12307#issuecomment-652044193

@aanm We still need to find a way to fix this in 1.6