Allow schema.Reference to validate as normal field

Solves issue #57 by allowing schema.Reference to be validated as a normal field. See commit messages for more details!

One of my big question with this design idea, is weather there will be more objects that various FielValidator's Compile methods needs access to in the future... If no, then this design might be OK.

TL;DR: I will complete this design to facilitate discussion. It's either this or passing context.Context to the Validate method (where the context would contain the same wrapped resource.Index that in effect implements ResourceLookup).
Design discussion: I had been hoping from some comments by now, but I suppose my code was not complete enough to facilitate a full understanding of the intended design here; especially as I have not implemented the part that must wrap resource.Index into an implementation of the ResourceLookup interface before passing that in to the Schema.Compile() method. Anyway, I have done some thinking myself below that I will outline below.
I have one thing that talks in favor of this desing atm., and that is that it makes sense to validate that the linked Reference resource exist at compile time. It can even help users avoid some bugs from reaching production.
I mentioned on #57 that I have considered replacing the ResourceLookup passed to the Compiler method with a context.Context that can optionally contain a ResourceLookup. That however feels really iffy, as the main purpose of context.Context is not to pass arbitrary data to (deeply nested) functions, but to facilitate deadlines and cancelation. And that is something the Compiler functions should not need!
The Validate function however, could serve well as a method where context.Context could be passed in -- as it could actually make sense to allow for deadline management there -- especially if having to do a DB call to finish the validation, as would be the case for Reference.
I will complete the current design to facilitate discussion, but it's probably a viable alternative to consider going for a Valdiate(ctx context.Context) interface.

I am not to far away from pushing and update... almost got there in the weekend, just need to update some remaining tests...

Sorry if I'm not very responsive. I'll wrap my head around the subject when you send the PR.

No problem @rs, I have been very busy as well, hench the long delay in pushing any more code.

@rs, There is still some tests that needs updating, but now at least the tests within the schema package pass.
At least tests within the schema/encoding and resource  packages needs updating.

UPDATE: jsonschema tests fixed, although I will add better support for JSON Schema encoding of Reference later now that we can actually access the reference after Compile is called.
rest package tests are still failing though, with the following:
2017/05/08 07:59:08 Server error: No Storage Defined
--- FAIL: TestHandlerPostListWithReferenceNoRouter (0.00s)
        Error Trace:    method_post_test.go:229
	Error:  	Not equal: 500 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:232
	Error:  	Not equal: 500 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:233
	Error:  	Not equal: "Router not available in context" (expected)
			        != "Document contains error(s)" (actual)

--- FAIL: TestHandlerPostListWithInvalidReference (0.00s)
        Error Trace:    method_post_test.go:255
	Error:  	Not equal: 500 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:258
	Error:  	Not equal: 500 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:259
	Error:  	Not equal: "Invalid resource reference for field `foo': invalid" (expected)
			        != "Document contains error(s)" (actual)

.... more failures like this.

I am not quite sure why, but presumably it's somehow related to issues with index.Compile() ?

@rs, thanks for the review, and sorry for my slow update time on this. Pushing a minor update to resolve identified issues, but there is still one major bug in the resource package that needs some debugging. Reproduce by running tests.
If someone with some time on their hans want to try and debug it, feel welcome. Otherwise I will get to it eventually.

Sorry for the the delay in looking into this.
I think most of the errors looks pretty reasonable, since the code generating the error texts / status codes we test against here, is part of what has been removed.

Right, so the 201 issues are solved by adding an explicit Compile to index. Normaly, index is compiled by rest.NewHandler(index), but that method is not called in these tests. Previously, this tests worked because a schema compilation was not specifically needed for schema.Reference fields, or any of the other fields in this specific schemas.
This leaves the remaining ssues with unexpected status codes / error messages when POSTing documents due to changed semantics. These errors also lacks an explicit call to index.Compile(). When correcting the tests, I think we can wrote them to be go 1.7 sub-tests, so that there is less code duplication.
@rs, what's your opinion on changing the semantics for "invalid reference" to all return a 422 (Unprocessable Entity), rather than different type of errors based on what's wrong with the Reference field. The reason that the status code is changing, is that invalid Reference fields now follow the same code pattern as other validation issues.
--- FAIL: TestHandlerPostListWithReferenceNoRouter (0.00s)
        Error Trace:    method_post_test.go:229
	Error:  	Not equal: 500 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:232
	Error:  	Not equal: 500 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:233
	Error:  	Not equal: "Router not available in context" (expected)
			        != "Document contains error(s)" (actual)

--- FAIL: TestHandlerPostListWithInvalidReference (0.00s)
        Error Trace:    method_post_test.go:255
	Error:  	Not equal: 500 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:258
	Error:  	Not equal: 500 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:259
	Error:  	Not equal: "Invalid resource reference for field `foo': invalid" (expected)
			        != "Document contains error(s)" (actual)

--- FAIL: TestHandlerPostListWithReferenceOtherError (0.00s)
        Error Trace:    method_post_test.go:282
	Error:  	Not equal: 500 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:285
	Error:  	Not equal: 500 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:286
	Error:  	Not equal: "Error fetching resource reference for field `foo': No Storage Defined" (expected)
			        != "Document contains error(s)" (actual)

--- FAIL: TestHandlerPostListWithReferenceNotFound (0.00s)
        Error Trace:    method_post_test.go:309
	Error:  	Not equal: 404 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:312
	Error:  	Not equal: 404 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:313
	Error:  	Not equal: "Resource reference not found for field `foo'" (expected)
			        != "Document contains error(s)" (actual)

--- FAIL: TestHandlerPostListWithSubSchemaReferenceNotFound (0.00s)
        Error Trace:    method_post_test.go:407
	Error:  	Not equal: 404 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:410
	Error:  	Not equal: 404 (expected)
			        != 422 (actual)

        Error Trace:    method_post_test.go:411
	Error:  	Not equal: "Resource reference not found for field `foo'" (expected)
			        != "Document contains error(s)" (actual)

Yes I think it make sense. And for Go 1.7 sub-test, I'm all for it.

I have set the sub-tests to run in Parallel. This appears to uncover a data race within github.com/rs/rest-layer/rest.DefaultResponseFormatter.FormatError(), but I don't think it's related to this change.
The bug goes away if I remove the parallel execution of the sub-tests. I think the bug was just masked before because we didn't do to many parallel tests...

It's these lines:
func (f DefaultResponseFormatter) FormatError(ctx context.Context, headers http.Header, err error, skipBody bool) (context.Context, interface{}) {
        oldLogger := resource.Logger
        resource.Logger = nil
        defer func() { resource.Logger = oldLogger }()

It think this is pretty ugly:-/ If we really need to do this, we need to use a mutex. What's the benfit of silencing the logger? Do you want to fix it in a separate commit?
This PR should be otherwise good to go in now :-)

I did that in some tests to remove error output while testing error cases? Did I do that in actual code??

Did I do that in actual code??
Well, I didn't run a git blame on it yet, but someone did... if it's by mistake I can add a separate commit to remove it in this PR so that the tests pass.

And we can of course silence the loggers in test code (or re-route it to write to testung.T).

The Git-blame btw:

https://github.com/rs/rest-layer/commit/4d8102671d3b82ac56d174b1ab1d0600cca0662f

I will rebase one more time to put the bug-fixes in front of the feature, leaving all three commits with passing tests.

@rs, ready for final review. The two commits before the feature are (unrelated) bugfixes that where needed for the (updated) tests to pass, hench I recommend a rebase and merge so that they end up as separate commits on master :-)

Note tha the commit ordering on GitHub is a bit weird... Ir's the one with the green tick that's last. The git log on this is correct on the branch.

@rs, I have pushed rename schema.ReferenceCompiler -> Compiler as a new commit for easier review only.
When you are happy, I would like to do a manual rebase to fold this, as well as any other requested changes into the previous commit :-)

rebased

\o/


Merge #5133

Add missing permission name
Fix  #5133

Coverage decreased (-0.2%) to 90.985% when pulling 628072b6e246436bd65d2f31ba360137879e92a0 on yakky:merge/5133 into 0eb535fafc548275f1b3c796c0cf420b26f777d1 on divio:support/3.1.x.


Fix bug "new folder error persists through multiple 'create folder' attempts" [#OSF-5707]

Purpose

Fixes bug where any error message shown when creating a folder persists through multiple create folder attempts and certain error messages sometimes take a while to display or may even never display at all
Changes
Fixes code to clear helpText whenever the dismiss toolbar button is hit and also whenever a create folder attempt is made
Also makes sure error messages appear using m.redraw() after helpText is filled with the error

Side effects
None

Ticket

https://openscience.atlassian.net/browse/OSF-5707

LGTM, and I see that this passed a product demo. Moving this ahead ⏩


Preserve typing on Task extensions

I've made a couple of extension methods trying to simplify the extremely verbose syntax when using Task. I'm left mapping in case of a failure to preserve unexpected errors.
class AppFailure {}

extension TaskEitherExtensions<T extends Either<Object, U>, U> on Task<T> {
  Task<Either<AppFailure, U>> mapLeftToFailure() {
    return map<Either<AppFailure, U>>(
      (either) => either.leftMap<AppFailure>((error) {
        if (error is AppFailure) return error;
        throw error;
      }),
    );
  }
}

extension TaskExtensions<T, U> on Task<T> {
  Future<Either<AppFailure, U>> execute<U>() =>
      attempt().mapLeftToFailure().run();
}

And I wanna call it like:
Future<Either<AppFailure, Unit>> someMethod() {
        return Task(someFutureReturningVoid).execute<Unit>();
  }

However, I get type 'Future<Either<AppFailure, dynamic>>' is not a subtype of type 'Future<Either<AppFailure, Unit>>'
I might be missing something here but is there a way of preserving type safety with my approach?

Hi, @RollyPeres .
Your problem seems to be related to type inferentece and, thus, not related to dartz itself.
Please, refer to #33 and #38, they are similar issues.
The problem probably will be solved simply by typecasting in the right place.
As I don't have the time to test your specific code right now, I may be wrong, so please feel free to tell me if this is not the case.

Hi @mateusfccp , thanks for suggestions. It clearly has something to do with type inference but couldn't find a solution. Also attempt is not generic as suggested in #33 ...I'm using dartz: ^0.9.0-dev.5.

Can you provide a minimal reproducible example?

@mateusfccp There you go: https://gist.github.com/RollyPeres/72c3d80e39bf032209c5b2aaea7b42e7

Well, your case is a little more complex. It seems Dart can't handle the "complex" case of T extends Either<Object, U> and can't infer U.
Let me ask: why have T to extend Either,<Object, U>? In the MRE you provided, you are not using any extension of Either, but Either itself.
I managed to run your example by replacing every occurrence of T with it's meaning:
extension TaskEitherExtensions<U> on Task<Either<Object, U>> {
  Task<Either<AppFailure, U>> mapLeftToFailure() {
    return map<Either<AppFailure, U>>(
      (Either<Object, U> either) => either.leftMap<AppFailure>((error) {
        if (error is AppFailure) return error;
        // simplified code for brevity...
        return AppFailure();
      }),
    );
  }
}

Of course, this will cause another problem. You are returning a Future<String> on something when doSomething expects Either<AppFailure, Unit>. Changing Unit to String will solve this:
Future<Either<AppFailure, String>> doSomething() {
  return Task(something).attempt().mapLeftToFailure().run();
}

Is this the expected behavior or am I missing something?

That was the problem. I've experimented with a couple of approaches, so apparently I ended up not paying attention to basic stuff :)
My end goal was to have:
extension TaskExtensions<T> on Task<T> {
  Future<Either<AppFailure, T>> execute() => attempt().mapLeftToFailure().run();
}

This will greatly simplify all the boiler plate.
Thanks @mateusfccp for having a fresh look at this!


jinja2 inheritance is working?

On the README you said that jinja2 is supported but there is so (none) example of how effectively use this, like: template inheritance?

It works just like regular Jinja2, it merely alters how the syntax looks like. I've updated the README with an example in e59cb7c

cool. many thanks :3


Flutter in an existing project

I have integrated a flutter module into an existing native project (iOS / Android).
I want to attach the debugger or the console log to the flutter module when running the native project.
I don't know how or even if it is possible.
To replace this inconvenience so far I have used the hot reload feature and made some additional workarounds for it (I have a text widget to display my prints).

on Android flutter/dart "print" statements do show up.. on iOS I don't find them easily..

print statements from flutter appear in the console of xcode as well as android studio but you cannot attach flutter to existing process.
I would be a nice to have in the future.


milvus: always set self._collection

Description
fix based on discussion from https://github.com/run-llama/llama_index/pull/16165#discussion_r1781582473
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[ ] Yes
[x] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[ ] Yes
[x] No

Type of Change
Please delete options that are not relevant.

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

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

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I ran make format; make lint to appease the lint gods

@andrew-augment can you run make lint and also bump the version of the integration?


Support overriding spot allocation strategy

My understanding is Karpenter only supports price-capacity-optimized.
I would like to be able to override this to capacity-optimized.
I can't see documentation on how to do this?

Closing due to duplication: https://github.com/aws/karpenter/issues/1240


[ChatGPT] Error message by using without selected text

Extension
https://www.raycast.com/abielzulio/chatgpt
Description
I get an error message when I open the “Ask Question” command without selected text. But it doesn't impact command functionality in any way. I have the setting for autoload text on, and it works correctly when I select text in an application.

Steps To Reproduce

Open Raycast.
Search for "Ask Question".
Open command.
You see the error massage.

Current Behaviour
No response
Expected Behaviour
No response

Are you still facing this issue on a daily basis? @wra1w0

Are you still facing this issue on a daily basis? @wra1w0

Don't use the extension anymore, because of Raycast AI. But I just reinstalled it and tested again, and I still got an error.
I think this is the function you use.
 useEffect(() => {
    (async () => {
      if (isAutoLoad && !disableAutoLoad) {
        setLoading(true);
        try {
          const selectedText = await getSelectedText();
          if (selectedText.length > 1) {
            setData(selectedText.trim());
            await showToast({
              style: Toast.Style.Success,
              title: "Selected text loaded!",
            });
          }
        } catch (error) {
          await showToast({
            style: Toast.Style.Failure,
            title: "Selected text couldn't load",
            message: String(error),
          });
        }
        setLoading(false);
      }
    })();
  }, []);

When no text is selected, you throw the error message. But from a UX perspective, it's not so nice. Because if someone intentionally doesn't select some text, it shouldn't be an error.
In my opinion, the better way may be to throw a success toast with text like "No text selected" etc. or an error toast without "Error"-word in the description.


Bug:staticConstructor of @Value Invalid when @Builder exist

version:1.18.2

the staticConstructor  not in result.
I think this is a bug.
Why builder can't exist with staticConstructor?

Because it can't. What's the point? You already have a builder, use that.


Codeunit 87 Blanket Sales Order to Order - ResetQuantityFields

We require an additional publisher in function ResetQuantityFields so we can reset our own field. We would like to propose the following change. A simular change for CU87 has been requested as issue #3005.
LOCAL PROCEDURE ResetQuantityFields@1(VAR TempSalesLine@1000 : Record 37);
BEGIN
  TempSalesLine.Quantity := 0;
  TempSalesLine."Quantity (Base)" := 0;
  TempSalesLine."Qty. Shipped Not Invoiced" := 0;
  TempSalesLine."Quantity Shipped" := 0;
  TempSalesLine."Quantity Invoiced" := 0;
  TempSalesLine."Qty. Shipped Not Invd. (Base)" := 0;
  TempSalesLine."Qty. Shipped (Base)" := 0;
  TempSalesLine."Qty. Invoiced (Base)" := 0;
  TempSalesLine."Outstanding Quantity" := 0;
  TempSalesLine."Outstanding Qty. (Base)" := 0;
  ///// START
  OnAfterResetQuantityFields(TempSalesLine);
  ///// END
END;

And the signature of the publisher:
[Integration]
LOCAL PROCEDURE OnAfterResetQuantityFields@11095586(VAR TempSalesLine@11095585 : Record 37);
BEGIN
END;

Many thanks.

Was introduced in BC14, missing in BC16. Will issue a new request.


Partial Invoicing

Currently, you can only create an invoice for the entire purchase order.
There are business cases for which a partial invoice is necessary.
interface InvoiceGeneratorInterface
{
    public function generateForOrder(OrderInterface $order, \DateTimeInterface $date): InvoiceInterface;

    /**
     * @param array $orderItemData [['orderItem' => $orderItem1, 'quantity' => 1],['orderItem' => $orderItem2, 'quantity' => 1]]
     * @param int $shippingAmount Shipping amount for this invoivce
     * @param \DateTimeInterface $date
     * @return InvoiceInterface
     */
    public function generateForOrderItems(array $orderItemData, int $shippingAmount, \DateTimeInterface $date): InvoiceInterface;
}

It's also may be dependant on multiple partial payment https://github.com/Sylius/InvoicingPlugin/issues/142


Port eclipselink-maven-plugin to a Gradle plugin

Can we get an equivalent of this plugin for Gradle?

Thanks for your interest in this plugin! This would be quite an undertaking and probably better off as a project of its own. I do not have the resources to do this at this time.

Thanks @ethlo, can you give me guidance (kind of a checklist to get me started). I will undertake this project myself.


arch/arm: change up_saveusercontext to assembly code

Summary
gdb will backtrace failure when use C code to save user context, because the stack push operation in C code can disrupt the stack information.
Impact
debug
Testing
tools/checkpatch.sh

@masayuki2009 Any feedback?


feat(APIM-81): Add get deal investor endpoint

Introduction
Add the GET /deals/{dealIdentifier}/investors endpoint
Resolution
For new Deals endpoint will return 1 investor. One more investor needs to be created using POST /deals/{dealIdentifier}/investors endpoint.

Response example (it matches Mulesoft response):

[
    {
        "dealIdentifier": "0030597686",
        "portfolioIdentifier": "E1",
        "lenderType": {
            "LenderTypeCode": "100"
        },
        "effectiveDate": "2023-03-20",
        "expiryDate": "9999-12-31",
        "isExpiryDateMaximum": false,
        "maximumLiability": 500012.25
    },
    {
        "dealIdentifier": "0030597686",
        "portfolioIdentifier": "E1",
        "lenderType": {
            "LenderTypeCode": "500"
        },
        "effectiveDate": "2023-03-20",
        "expiryDate": null,
        "isExpiryDateMaximum": true,
        "maximumLiability": 500012.25
    }
]

Endpoint logic is minimal:
a. it transforms ACBS response and adds 2 fields from request

do we need portfolioIdentifier and dealIdentifier fields? left them as it matches Mulesoft implementation.
b.  removes time from date fields
c. one datetime field in ACBS response can be null.

Responses:
a. 200 - All good
b. 404 - ACBS can return 200 null for non-existing Deals.

Mulesoft in this case sends status 200 but 404 in the body
In NodeJs implementation we return 404 in header and body
c. 500 - for any other errors or ACBS responses

Misc

Content type for UKEF ID. It is 10 digits string. Typescript "Template Literal Types" helps to define format a little bit, but can't ensure length check.
1 or 2 TODO items.

LGTM


Headless service (in multi primary mode) is not resolvable across clusters in Istio 1.9.2.

Bug description
I have multi-primary-cluster set up on the same network based on these instructions. Cross cluster connectivity is working as expected as mentioned in these verification docs. But exposing a headless (clusterIp: None) service in cluster1 is not getting resolved from cluster2 in Istio version 1.9.2. Note: this works in version 1.9.1.
[x] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
The headless service deployed in cluster1 is getting resolved in cluster1
Steps to reproduce the bug
i. Follow the multi primary installation docs to install istio in multi-cluster setup.
ii. Verify the setup is working as per this verification docs.
iii. Create a headless service backed by a statefulset in cluster 1. Note the service object targets a pod to use service FQDN.
apiVersion: v1
kind: Service
metadata:
  name: helloworld-0
  namespace: test
  labels:
    app: helloworld
    service: helloworld
spec:
  clusterIP: None
  ports:
  - port: 5000
    name: http
  selector:
    statefulset.kubernetes.io/pod-name: helloworld-0
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: helloworld
  namespace: test
spec:
  serviceName: "helloworld"
  replicas: 1
  selector:
    matchLabels:
      app: helloworld
  template:
    metadata:
      labels:
        app: helloworld
    spec:
      containers:
      - name: helloworld
        image: docker.io/istio/examples-helloworld-v2
        resources:
          requests:
            cpu: "100m"
        imagePullPolicy: IfNotPresent #Always
        ports:
        - containerPort: 5000

vi. exec into a pod in cluster2(in test namespace) and run curl helloworld-0.test.svc.cluster.local:5000/hello -- this would return Could not resolve host: helloworld-0.test.svc.cluster.local (using service FQDN).
Note: this however works in Istio version 1.9.1
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
client version: 1.9.2
control plane version: 1.9.7
data plane version: 1.9.7 (1 proxies)

How was Istio installed?
https://istio.io/latest/docs/setup/install/multicluster/multi-primary/
Environment where the bug was observed (cloud vendor, OS, etc)
Deployed on AWS using KOPS.

https://github.com/istio/istio/pull/32515
1.11 will have support for this, but it won't be back-ported to 1.9 unfortunately.

We originally had https://github.com/istio/istio/issues/27342 which I think is the same issue.

thanks for the quick response @stevenctl


Update free-programming-books-es.md

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s)
For resources
Description
An HTML and CSS course in spanish
Why is this valuable (or not)?
It's a very complete course
How do we know it's really free?
It's made by a spanish blog author and yes, it's free because I have taked it.
For book lists, is it a book? For course lists, is it a course? etc.
It's a course
Checklist:

[x] Not a duplicate
[ ] Included author(s) if appropriate
[x] Lists are in alphabetical order
[x] Needed indications added (PDF, access notes, under construction)

It looks like the build failed because there is an incorrect number of blank lines between the end of the HTML/CSS section and the JAVA section title.
Add in one more blank line, so that there are two blank lines between the last link and the new section
For more information on the formatting and guidelines, check the contribution guide (CONTRIBUTING.md). Or, you can also look at the failed check in Travis CI to see the details of where linting has failed.

As you say, this is a course, not a book, and should be added to the courses list.


Bugs inside the DTag transferring process

Bug description
During the completion of the Desmos Primer Phase 6 challenge that required them to perform a DTag transferring, the Discord user MikeSnowman75 told me they ran into a strange behavior that did not allow him to exchange the DTag properly.
Steps to reproduce
Reporting his words, here is what he did with an additional analyses from me.
He tried to transfer the dtag first in these 2 transactions:

First
Second

As we can already see, there are two problems here:

The first transaction has an empty dtag_to_trade.
This might say that the sending profile did not exist, or it didn't have the DTag set. This is a bug I've already reported inside #292.

The second message fails with error profile of desmos1k7q92w7ku72ycutz6xqrx67v92yycff3emz88s doesn't exist.
This should not have happened. If a user wants a DTag of another user without having created a profile first, then a new profile for the receiving user should be created and the DTag transferring should continue properly.

After this, he tried with other two transactions:

First

Second

From them, we can see that:

The first transaction was successful.
The second transaction failed with error the owner's DTag is different from the one to be exchanged.
Apparently, something here messed up because this one should not have failed here.

Also, they said that they tried performing another transaction. As you can see, this failed with error:
the transfer request from desmos1rpurg200edtv6rgvfjuf7j6s8mghnsljkzvurg to desmos1k7q92w7ku72ycutz6xqrx67v92yycff3emz88s has already been made

To be honest, I don't think this error should ever verify. If an Alice -> Bob transfer was made successfully, then once it concluded it should be removed allowing Alice to send Bob another DTag if she wants. I've reported this bug inside #295.
Expected behavior
The first transferring should have completed properly, as well as the second one.

I think I've understood why this txs error occurred.
Since in v0.12.3 we have the empty DTag transfer bug, when we make a request to an address without a profile, the system saves the request with an empty dTag into the store. Later, that address create a profile with a dTag which will be different from the empty one and if he accept the transfer request the error will show up.

@bragaz So, this should be fixed with #303 as well?

@RiccardoM I will add some more integration tests to a new PR that should solve this and #295


Allow passing scopes as parameter

This way, it can be used for managed identity authentication during development.
(And we don't need to install Azure Cli in the dev container when doing C# development)

Oh the file name. Yeah, sure I'll make that change and update the pull request.

Thanks, looks good. If you can update the README also with details on how to call the new helper that would be great!

Published. Thanks @shocklateboy92, very excited to see this extension being used in new ways 👍


Refactor modified PodSpec to PodSpecMod

The Kubernetes specs which we modify or add shortcuts to, are
in the format of Mod struct, example ServicePortMod,
IngressSpecMod, etc. This was not done for PodSpec in the App
struct till now.
This commit refactors the modified PodSpec out of the App struct
into PodSpecMod struct, and refactors tests.
Fixes #112

Cool LGTM


Update createTestCases.js

To ensure the script works with relative paths for module creation and file handling, all file system operations should use relative paths anchored at __dirname

What kind of change does this PR introduce?

Did you add tests for your changes?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

Sorry but we don't need these changes, thanks anyway


fixed typos

@eric-haibin-lin If you can reivew it, I would be very grateful

Thanks @anancds !

Thanks @anancds !


Community: Adding ChatPredictionGuard Integration

*[x] PR title: "community: adding ChatPredictionGuard integration to allow for chat using the Prediction Guard API in Langchain."

*[x] PR message:

Description: This PR introduces the ChatPredictionGuard class. This enables users to chat with LLMs through the Prediction Guard ecosystem.
Issue: None
Dependencies: None
Twitter handle: @predictionguard

*[x] Add tests and docs: Notebooks and integration tests are added and working for the new integration feature.

*[x] Lint and test: Linting tests are all passing.

Closing after move to partner package


Language translation files are cached after upgrade

Post upgrading packages, the translation files such as en.json are cached in the browser. Somehow hard refresh doesn't work on them. If the UI can find a clever way to call them or ensure that they arne't cached by the browser.
ISSUE TYPE

Bug Report

COMPONENT NAME

UI

@rohityadavcloud , according to internet (stackoverflow) you need to up the version in package.json to automatically load the new files. I think we can do that (allign it a bit with the cloudstack release for instance.

Ah, thanks @DaanHoogland I suppose we can use the UI version same as ACS version - cc @weizhouapache ?

Raised a PR - https://github.com/apache/cloudstack/pull/7894 @DaanHoogland cc all - but that needs manual (upgrade) testing

@rohityadavcloud what is the side effect of this - do you mean that since the translation files are getting cached, on changing the language, it doesn't reflect in the UI?

@Pearl1594 say you upgrade from 4.17 -> 4.18; any new feature that introduced say a UI translation key such as message.action.xyz.abc will show up as-is, since the translation file (en.json say) is cached in browser for 4.17. Only if somebody clears cache or open UI in incognito etc will be able to see the string for message.action.xyz.abc which got added in 4.18 (not in 4.17).

fixed by #7894


General fixes

Fixes some issues, crashes and warnings

Nice work! These fixes looks very good to me!


dead keys on MacOS

I'm having problems trying to use the terminal with us-international layout (Mac OS), specifically using " or ' and `  this chars have dead keys so, to type a quote ", you have to press the quote key followed by the SPACE key. Is this behaviour supported?

Devel branch use event.key if supported by the browser here is browser support it seems that it's not supported by Safari.

Finally was able to install MacOSX on virtualBox and fixed the issue

the fix will be in version 1.0.7


cmd/go: Go 1.5beta2 updating GOPATH and unstaged Git repositories

I use go get -v -d -u -f .../ to update all my GOPATH.
With Go 1.4.2, there was no problem.

Please commit or stash them.

I need to manually reset/clean the repositories.
These messages appear randomly.
I can't reproduce this problem reliably.
Go version: 1.4.2 & 1.5beta1/2
Git version: 2.4.6
Linux version: 4.1.2-2-ARCH #1 SMP PREEMPT Wed Jul 15 08:30:32 UTC 2015 x86_64 GNU/Linux

Huuu sorry.
Actually, I think my IDE is running goimports on modified files during GOPATH update.


[Question] How to parse / transform traversal & blocks

First of all, great work on this crate @martinohmann!
Second, I am trying to parse a particular file into a shape that i want to transform it for, and I am wondering if you have a guide or an example in mind for it.
The hcl file
I am currently parsing routes/listeners etc and I want to be able to traverse/resolve blocks, e.g.:

listener "http" {
  bind = "<IP_ADDRESS>"
  port = 80
}

upstream "service" {
  ip = "<IP_ADDRESS>"
  port = 3000
}

route "domain.com" {
  listener = listener.http
  upstreams = [upstream.service]
}

route "anotherroute {
  listener = listener.http
  upstreams = [upstream.service]
}

What I am having issues with, is the shape at the end, like below.
The shape I want at the end
// Example

struct MyStruct {
  listeners: Vec<Listener>,
  routes: Vec<Route>
}

struct Listener {
   bind: String,
   port: usize
}

struct Upstream {
  ip: String,
  port: usize
}

struct Route {
 upstreams: Vec<Upstream>
}

From the way I understand it, I can't simply parse and I'd need some transformation in place, but I am not able to find the right direction so far.
Any pointers/suggestions that you have?
Thanks in advance!

Hi there!
A config like this requires a two-step approach: first parse the config into some helper structs, and then resolve the references like upstream.service to get the structure you want.
You could do something like this:
use hcl::{
    eval::{Context, Evaluate},
    expr::Traversal,
    Map, Result,
};
use serde::{Deserialize, Serialize};

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let input = r#"
        listener "http" {
          bind = "<IP_ADDRESS>"
          port = 80
        }

        upstream "service" {
          ip = "<IP_ADDRESS>"
          port = 3000
        }

        route "domain.com" {
          listener = listener.http
          upstreams = [upstream.service]
        }

        route "anotherroute" {
          listener = listener.http
          upstreams = [upstream.service]
        }
        "#;

    let raw_config: RawConfig = hcl::from_str(input)?;

    let config = raw_config.resolve()?;

    serde_json::to_writer_pretty(std::io::stdout(), &config)?;
    Ok(())
}

#[derive(Serialize, Deserialize)]
struct RawConfig {
    #[serde(rename = "listener")]
    listeners: Map<String, Listener>,
    #[serde(rename = "upstream")]
    upstreams: Map<String, Upstream>,
    #[serde(rename = "route")]
    raw_routes: Map<String, RawRoute>,
}

impl RawConfig {
    fn resolve(&self) -> Result<Config> {
        let mut ctx = Context::new();
        ctx.declare_var("upstream", hcl::to_value(&self.upstreams)?);

        let mut routes = Vec::with_capacity(self.raw_routes.len());

        for raw_route in self.raw_routes.values() {
            let route = raw_route.resolve(&ctx)?;
            routes.push(route);
        }

        let listeners = self.listeners.values().cloned().collect();

        Ok(Config { listeners, routes })
    }
}

#[derive(Serialize, Deserialize)]
struct RawRoute {
    listener: Traversal,
    upstreams: Vec<Traversal>,
}

impl RawRoute {
    fn resolve(&self, ctx: &Context) -> Result<Route> {
        let mut upstreams = Vec::with_capacity(self.upstreams.len());

        for traversal in &self.upstreams {
            let value = traversal.evaluate(&ctx)?;
            let upstream = hcl::from_value(value)?;
            upstreams.push(upstream);
        }

        Ok(Route { upstreams })
    }
}

#[derive(Serialize, Deserialize, Clone, Debug)]
struct Config {
    listeners: Vec<Listener>,
    routes: Vec<Route>,
}

#[derive(Serialize, Deserialize, Clone, Debug)]
struct Route {
    upstreams: Vec<Upstream>,
}

#[derive(Serialize, Deserialize, Clone, Debug)]
struct Listener {
    bind: String,
    port: usize,
}

#[derive(Serialize, Deserialize, Clone, Debug)]
struct Upstream {
    ip: String,
    port: usize,
}

Output:
{
  "listeners": [
    {
      "bind": "<IP_ADDRESS>",
      "port": 80
    }
  ],
  "routes": [
    {
      "upstreams": [
        {
          "ip": "<IP_ADDRESS>",
          "port": 3000
        }
      ]
    },
    {
      "upstreams": [
        {
          "ip": "<IP_ADDRESS>",
          "port": 3000
        }
      ]
    }
  ]
}

Let me know if this helps with your use case.


move tests to corresponding structures?

After #197 is merged we will have implementations of structures:

Identity
Maybe
Array
Compose

This might grove after adding more algebras in future.
Possibly solution is to completely remove test from FL, but in this case fantasy-id, fantasy-maybe ... should be always up to date and if we have a PR to add some spec to FL, before we land it, PRs for fantasy-* should be opened, to ensure PR in FL is correct, then PR in FL could be merged and version bumped. After which PRs in fantasy-* could update FL and be merged as well.
Related discussion

Now that is an awesome idea

We could also make fantasy-* dev dependencies of fantasy-land, right? Sounds much easier than alternative with multiple PRs for each change.

If some Foo spec is added to FL with foo method and the method should be implemented in fantasy-* what shell we do? also fantasy-* have there own tests too.

Sorry I've deleted my comment after realising that it's invalid :)
Anyway I still don't understand completely how this would work even with multiple PRs to multiple repos. We would add unmerged branches as dependencies and such?
Sounds very complicated.

For example someone opens PR to adds Foo spec to FL and adds laws/foo.js
once it looks good and is ready to merge, then the author will also open PR for fl-id or fl-maybe and depend on her development branch of the FL PR temporarily, add tests, and after it's passing then PR in FL could be merged and version bumped, after which the PR in fl-id or fl-maybe could be updated to use published version of FL and be merged. (we just need at least Id Maybe to be up to date with correct FL)
Yeah it's sort of complicated but the way we are doing it is not any better.

I don't. Duplication is an evil in itself. I can't fathom why we constantly have to duplicate libraries containers over and over again. The point of the spec included the libraries around it, they're a standard for the spec and because people have decided to implement their own (and have worse implementations!!!), they're neglected because of this. I went to rectify this...
Fantasyland has standard libraries with the spec and should have been promoted from the start (which I regret not doing!) and we should strive to do this...

people have decided to implement their own (and have worse implementations!!!)

Could you elaborate on this point, @SimonRichardson?

Invalid functors is a very common one, also checking types on maybes which
leads to all sorts of issues.
If I come across some I'll try to take a note so that we can help the
author to understand the mistakes they've made, but not gotten anything to
hand right now unfortunately.
On Sun, 30 Oct 2016, 21:41 David Chambers<EMAIL_ADDRESS>wrote:

people have decided to implement their own (and have worse
implementations!!!)
Could you elaborate on this point, @SimonRichardson
https://github.com/SimonRichardson?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fantasyland/fantasy-land/issues/200#issuecomment-257181440,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACcaGN-Zl5g5s3oPbWbi0YAbwdyA3VTbks5q5Q8KgaJpZM4KkfXo
.

Invalid functors is a very common one, also checking types on maybes which leads to all sorts of issues.

Ah, yes. I've seen this sort of thing several times. Thanks for the clarification.

@SimonRichardson maybe we should provide standard library for basic data structure? Maybe, Either are basic data structure i think. Haskell provide this on Prelude and Purescript community only used one implementation. But on Fantasy Land, many library provides their own implementations, which make difficult to integrate them (hence the need for spec).
Maybe we should introspec, our implementations on Fantasy-Land repo doesn't have good documentation, and even it doesn't transpile it (it will create problem on browser, as we don't have it). Then we can make other library authors to depend our implementations.


basic progress indicator during sample import

Shows a very basic count down of bytes remaining to be imported during sample file import into flash.
Fixes: #147

I'm seeing occasional crashes which I can't reliably reproduce in test, but I need to check if this is due to the outstanding clock bug, a failing sdcard or actual issue with this PR.

I'll test this later, but I'm tempted to think that the fact that this works is actually a problem and we should fix that, or really understand why this works to ensure it doesn't cause any issues.
My concern is that there should be no reads from flash while writing into it, so nothing should happen until we finish writing.

I'll test this later, but I'm tempted to think that the fact that this works is actually a problem and we should fix that, or really understand why this works to ensure it doesn't cause any issues.
My concern is that there should be no reads from flash while writing into it, so nothing should happen until we finish writing.

I mentioned this in #151 as well, but this doesnt mean that there are any reads from flash while writing it. What my code displays is actually the part of the import process where the sample is copied from samplelib location to the projectdir and that seems to be the longer part of the process whereas loading the sample data from the projectdir into flash, likely due to the way the current code writes to the sdcard in small chunks which is quite slow on sdcards.
So I guess this is more accurately at the moment only showing the copy process progress, but I'll improve it to show more messages just before flash load starts but the it won't be able to show progress as you mention unless perhaps we did a better way of managing flash writes by not disabling interrupts during that process on both cores.

obsolete


Figure out which operations need a progress bar and async treatment

At the moment, most Rust commands are "normal" synchronous functions. Hence even if JS is using them through an asynchronous interface, they can still block the UI because the main thread ends up stuck in Rust. This seems to be fix-able by making these Rust commands async, but then we need som way to lock the UI to ensure that the user does not trigger too many actions while waiting on one computation.

Resolved by #15.


fix: Using netty dependency from server for MySQL

Local development fails because of the dependency being loaded by both server and plugin class loaders. This fix makes mysql use the server loaded class.

/ok-to-test sha=7c62999


convert_script() converts ALL commands to ansys.run()

pyansys 0.39.10 with ANSYS V19.0,
convert_script() converts ALL commands to ansys.run(...) rather than equivalent pyansys commands (when possible).
I think this can be fixed by following edit on line 197 of convert.py
change from:
command = items[0].capitalize().strip()
to:
command = items[0].lower().strip()

Fixed in cfa3ee1a54eb35451b005a5c6ccc2d9036deddfc


vni conflict in vxlan connecitons

Expected Behavior
vni should be unique for each connection between two clusters
Current Behavior
Two remote connections can have the same vni value
Failure Information (for bugs)
Current vni selector script does not guarantee that there is no vni conflict in connections between two clusters
https://github.com/networkservicemesh/networkservicemesh/blob/54548ed42f1d0c3de6071c873412b58e68eaf690/controlplane/pkg/vni/vni.go#L39-L52
Steps to Reproduce
Disabled TestInterdomainVPNFirewallRemote integration test in pr #1298 has almost 100% chance to reproduce issue on clouds
Failure Logs
log.txt

I don't like the way we reference VNI in the middle fo the control plane. NSMgr should be pretty much remote mechanism agnostic and have an abstract pool of connection IDs where the local forwarding planes translate them to the specific IDs that the selected tunnelling protocol uses. So imagine we want to enable MPLS now, we have to map the VNIs to labels.

@nickolaev I don't quite follow... could you say more?

One of the NSM building blocks is the point-to-point connection between the workloads. When we want to connect remote workloads we rely on a unique identifier to establish that point-top-point connectivity without interfering with the other workloads sharing the same physical infrastructure.
In the current code, the unique ID, that is supposed to distinguish the tunnel is called VNI, which more or less suggests VxLAN. I prefer if we move away from that wording, and be more generic here - TunnelID or similar might be better named. Then we also need to find a suitable size of that id. VNIs are 24-bit which is plenty but maybe we want to go with 32 or even 64 bit IDs. We can even do UUIDs if we find that better. Then these abstract IDs can be passed to the forwarding plane alongside the cross-connect request (as done today) and let the forwarding plane figure out how the 64-bit ID (for example) maps to the 24-bit VNI.
As I proposed in my previous comment - these IDs can be generated out of the domain/host names, or maybe split the whole 64-bit(range) into chunks and distribute them to the NSMgrs etc.

@nickolaev VNIs are bound to the particular mechanism choice (in this case VXLAN)... different mechanism types will have different kinds of parameters (example: SRv6 and SID lists)... so I think this is more an issue of proper binding of parameters to mechanisms, rather than trying to build a one size fits all parameters.
All of that said, I think the issue that @artem-belov is raising here is about how we assign the VNI.
Currently, the last NSMgr in the chain assigns the VNI as part of accepting the connection, and it does it by comparing its IP address to the SRC_IP for the tunnel.  Depending on the outcome of that comparison it will choose to assign either odd or even VNIs when it receives a Request from this particular peer.  The reason it does this is to avoid a central ID issuing authority.  Since given two peers (NSMgr1, NSMgr2) you can have:
NSMgr1 Requests of NSMgr2 (and therefore NSMgr2 picks the VNI) or
NSMgr2 Requests of NSMgr1 (and therefore NSMgr1 picks the VNI)
and since in the case of VXLAN, its (src_ip, dst_ip, vni) that uniquely determine the tunnel, this approach let us avoid complex coordination.
What @artem-belov is pointing out is that due to NAT-like behaviors in inter-domain, we may have situations where NSMgr1 Requests via a pNSMgr to NSMgr2 ... and the pNSMgr may be munging tunnel IPs to deal with Public/Private IP situations.
So NSMgr1 thinks its dealing with the pair (private_src_ip, public_dst_ip) and NSMgr2 sees (public_src_ip,private_dst_ip).  This can cause them to arrive at situations via IP address comparison where NSMgr1 believes it should select from the odd VNIs when NSMgr2 requests of it... and NSMgr2 believes it should also select from the odd VNIs when NSMgr1 requests of it.

I get what are the reasons behind this code, but my argument here is that this code does (parsin IPs and figuring out ~VNIs) does not belong to NSMgr, but to the concrete forwarding plane implementation. From your explanation it sounds like we'll have to add networkservicemesh/controlplane/pkg/sni/sni.go once we want to add SR. and then choose at runtime which ID allocation mechanism to call depdning on the remote mechanism chosen. And I think this logic does not belong in NMgr. It's forawrding plane's job to figure out remote mechanism details- IMO.

@nickolaev Ah... got it.  So I think we have two issues here:

Where this sort of logic should live.  I get your point about putting it in the NSM Forwarder.  To do so, we will need to make some alterations to the NSM Forwarder API, but they are arguably overdue.  I would suggest we open a new issue for that
Fixing the selection algorithm for VNIs in this sort of case.

Does that sounds like a fair split of the issue to you?

@edwarnicke yes, this is a good split. Thanks.

@artem-belov Do you have suggestions for ways to handle the VNI problem here?

Guys, correct me, probable I'm wrong, but in this example it probable will also fail:

@haiodo I don't think so... in this example the VXLAN/VNI1 is for the vWire between Dataplane1 and Dataplane2 ... Vxlan/VNI2 is for the vWire between Dataplane2 and Dataplane3... so it should work (if I understand your example correctly).

In this example it should also fail:

@edwarnicke , I’ve found error in my drawing so updated :slightly_smiling_face:
Question is when we need vxlan from dataplane3 to dataplane1

@haiodo I'd been thinking about it as Dataplane2 being responsible to crossconnect there.
So Dataplane1 crossconnects Client to VXlan/VNI1, Datplane2 crossconnects VXlan/VN1 to VXLAN/VNI2, and Dataplane3 cross connects from VXLAN/VNI2 to the Endpoint.
I'm not sure what to make of your VXLAN/VNI3 directly from the Endpoint... ;)

@haiodo @edwarnicke @nickolaev  I think we can make kind of a handshake of NSMs on first request. For example, NSMgr1 doesn't find NSMgr2 address in the VNIs map, so it makes a request to split up VNI range.
Another way - we can wind some unique property to compare NSMs and choose range (Like we are doing now with ip address)

@edwarnicke After @onobrod will prepare interdomain as plugin, it will keep both  Internal and External IPs information. So we can compare public IPs (local IPs if public are missing or equal) to generate vni. It should resolve problem

@artem-belov Please say more... I don't quite follow what you are proposing.

@edwarnicke
Current vni generation depends on comparing ip addresses:
src-ip > dst-ip - even vni
dst-ip < src-ip - odd vni
In Interdomain we have to configure VXLAN next way:
src vxlan side: src-internal-ip -> dst-external-ip (vni x)
dst vxlan side: dst-internal-ip -> src-external-ip (vni x)
The cause of current vni conflict is comparing internal ip with external ip which is gives simmetric result sometimes.
src-internal-ip > dst-external-ip - event vni
dst-internal-ip > src-external-ip - even vni
So we want to keep both internal and external IPs in mechanism preferences to make correct comparing for vni generation. We will compare public IPs for interdomain and local IPs for connection within one cluster

Closing, since merged.


Triton ONNX runtime backend slower than onnxruntime python client on CPU

Description
When deploying an ONNX model using the Triton Inference Server's ONNX runtime backend, the inference performance on the CPU is noticeably slower compared to running the same model using the ONNXRuntime Python client directly. This performance discrepancy is observed under identical conditions, including the same hardware, model, and input data.
Triton Information
TRITON_VERSION <= 24.09
To Reproduce
model used:
wget -O model.onnx https://github.com/onnx/models/raw/refs/heads/main/validated/vision/classification/densenet-121/model/densenet-12.onnx

Triton server (ONNX runtime)
config.pbtxt
name: "test_densenet"
platform: "onnxruntime_onnx"

Python clients
Triton client
import numpy as np
import tritonclient.grpc as grpcclient
import tritonclient.grpc._infer_input as infer_input

grpcclient = grpcclient.InferenceServerClient(url='localhost:9178')

i = infer_input.InferInput('data_0', [1, 3, 224, 224], 'FP32')
i.set_data_from_numpy(np.zeros((1, 3, 224, 224), dtype=np.float32))

%%timeit
res = grpcclient.infer(model_name="test_densenet", inputs=[i])

results: 473 ms ± 87.9 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
ONNX Runtime
import onnxruntime as ort

ort_sess = ort.InferenceSession('model.onnx')
test_inputs = {"data_0": np.zeros((1, 3, 224, 224), dtype=np.float32)}

%%timeit
ort_sess.run(["fc6_1"], test_inputs)

results: 159 ms ± 23.9 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)

@fpetrini15 ?? it's a black box

@Mitix-EPI  Can you add  get_inference_statistics  function call after infer and share the numbers?
It would help us in identifying the bottleneck.  Does the latency remain the same or it reduces with repetition? This would help us identifying if this is a warmup issue.

Hi @Mitix-EPI,
I set up a simple test suite on my local machine with minor modifications (mostly altering the code to work outside of Jupytr) and could not replicate your results. While the result you report in your ONNX Runtime section is consistent with what I am observing in my testing, Triton is consistently clocking between 178-185ms of execution time when deploying an instance to the CPU.
AVG Execution time: 10.60993140405044 ms per inference
TOTAL Execution time:<PHONE_NUMBER>405044 seconds ms inference

You can make explicitly sure that your model is being deployed to the CPU by adding the following to your config:
instance_group [
    {
        count: 1
        kind: KIND_CPU
     }
]

Hi @Mitix-EPI,
I set up a simple test suite on my local machine with minor modifications (mostly altering the code to work outside of Jupytr) and could not replicate your results. While the result you report in your ONNX Runtime section is consistent with what I am observing in my testing, Triton is consistently clocking between 178-185ms of execution time when deploying an instance to the CPU.
AVG Execution time: 10.60993140405044 ms per inference
TOTAL Execution time:<PHONE_NUMBER>405044 seconds ms inference

You can make explicitly sure that your model is being deployed to the CPU by adding the following to your config:
instance_group [
    {
        count: 1
        kind: KIND_CPU
     }
]

Thanks ++ for your interest on my issue !
Nothing about GPU, the device I use does not have GPU.
I1007 09:04:52.000928 1 onnxruntime.cc:2986] "TRITONBACKEND_ModelInitialize: test_densenet (version 1)"
I1007 09:04:52.134176 1 onnxruntime.cc:3051] "TRITONBACKEND_ModelInstanceInitialize: test_densenet_0 (CPU device 0)"
I1007 09:04:52.134301 1 onnxruntime.cc:3051] "TRITONBACKEND_ModelInstanceInitialize: test_densenet_1 (CPU device 0)"
I1007 09:04:52.398852 1 model_lifecycle.cc:839] "successfully loaded 'test_densenet'"

I just tested on another computer with another cpu and it ⚠ DOES NOT ⚠ reproduce the slow triton onnx inference... maybe cpu compatibility issue ?
>lscpu
Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         46 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  12
  On-line CPU(s) list:   0-11
Vendor ID:               GenuineIntel
  Model name:            13th Gen Intel(R) Core(TM) i5-1345U
    CPU family:          6
    Model:               186
    Thread(s) per core:  2
    Core(s) per socket:  10
    Socket(s):           1
    Stepping:            3
    CPU max MHz:         4700,0000
    CPU min MHz:         400,0000
    BogoMIPS:            4992.00
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr
                         sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good
                          nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vm
                         x smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_ti
                         mer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs i
                         bpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2
                          smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xs
                         aves avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi umip p
                         ku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdiri movdir64b fsrm md_clear serialize pconfig
                         arch_lbr ibt flush_l1d arch_capabilities
Virtualization features:
  Virtualization:        VT-x
Caches (sum of all):
  L1d:                   352 KiB (10 instances)
  L1i:                   576 KiB (10 instances)
  L2:                    6,5 MiB (4 instances)
  L3:                    12 MiB (1 instance)
NUMA:
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-11
Vulnerabilities:
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Not affected
  Retbleed:              Not affected
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
  Srbds:                 Not affected
  Tsx async abort:       Not affected

I don't actually know how to deal with it ...

@Mitix-EPI You can try Model Warmup feature to issue two requests to the model during the load time.

I just tried to add model warmup but it does not affect the time inference.
config.pbtxt
name: "test_densenet"
platform: "onnxruntime_onnx"

input [
  {
    name: "data_0"
    data_type: TYPE_FP32
    dims: [ 1, 3, 224, 224 ]
  }
]
output [
  {
    name: "fc6_1"
    data_type: TYPE_FP32
    dims: [ 1, 1000, 1, 1 ]
  }
]

instance_group [{ kind: KIND_CPU }]
model_warmup [
{
    name : "zero sample"
    batch_size: 1
    inputs {
        key: "data_0"
        value: {
            data_type: TYPE_FP32
            dims: [ 1, 3, 224, 224 ]
            zero_data: true
        }
    }
    count: 100 <----------- A lot of warmup, just to see that in runtime it takes time and the warmup exists
}]

results of test_triton_inference.py
Time: 33.84 ms
Time: 98.95 ms
Time: 89.65 ms
...
Time: 70.02 ms
Time: 87.91 ms
Time: 77.67 ms
Mean: 74.03 ms
Median: 72.99 ms
Std: 13.33 ms
Inference statistics:
model_stats {
  name: "test_densenet"
  version: "1"
  last_inference:<PHONE_NUMBER>536
  inference_count: 300
  execution_count: 300
  inference_stats {
    success {
      count: 300
      ns:<PHONE_NUMBER>0
    }
    fail {
    }
    queue {
      count: 300
      ns: 2986235
    }
    compute_input {
      count: 300
      ns: 4255835
    }
    compute_infer {
      count: 300
      ns:<PHONE_NUMBER>2
    }
    compute_output {
      count: 300
      ns: 6082487
    }
    cache_hit {
    }
    cache_miss {
    }
  }
  batch_stats {
    batch_size: 1
    compute_input {
      count: 300
      ns: 4255835
    }
    compute_infer {
      count: 300
      ns:<PHONE_NUMBER>2
    }
    compute_output {
      count: 300
      ns: 6082487
    }
  }
}


server bundle compile error

/vuejs/test/node_modules/vue-slide/vue-slide.vue:1
(function (exports, require, module, __filename, __dirname) { <style>
SyntaxError: Unexpected token <

It look like vue-slide.vue compile error on the server?

I am facing the same issue.
Steps to reproduce:

Clone the repo.
npm install --save vue-pdf
Include it in any component.
Directly navigate to the route.

Throws an error

@billwing were you able to solve the issue?

@chawlaaditya8 I think that vue-pdf does not support vue-ssr as vue-slide.

@billwing were you able to solve the issue?

Solve this issue for nuxt.js
👇
#148 (comment)


fix: Year method in the time feature

Description
The year method returns a value lesser than the default min year value of 1701.
Steps To Reproduce

Make use of the year method without passing any max value.

Expected Behavior
The return year value should not be lesser than 1701
Screenshots

Additional Context
Add any other context about the problem here.

Alright.... I will check it out... @developerjamiu just if you are also available to look at this.


Jb/rule tweaks for better boosting

Changes which enable working with hs-backend-booster:

mark all rules for #range as concrete (otherwise we get the wrong semantics)
mark a few functions and rules as definedness-preserving
remove matching _List_(.List, TAIL) and _List_(INIT, .List) and unnecessary #let expressions

Hmmmm, I don't like that we have to manually put preserves-definedness on some rules, would be better to either strengthen the analysis, or refactor the semantics. Issue created: https://github.com/runtimeverification/evm-semantics/issues/1857


Look at what link_with does with respect to the targets

I've never used this in any of my podfiles so it's a bit of a mystery.

link_with is gone as of this morning!

:D


qTip2 v2.2.1. bower dist doesn't contain full css and js version

github.com/qTip2/bower.git
This repo contains only basic version of qTip2.
Could you please update it?

It also contains the full build, in the main jquery.qtip.js and similar files. Closing

The bower repo still only contains the 2.2.1 version and the bower main is missing the CSS.


Create "valued members file" to further clean up the top level readme

As discussed in the 13 April TAG CS meeting. Moving Bootstrap TAG members
& Emeritus Leads to their own file with a referance paragraph in the readme.

@carolynvs @jberkus can you please review?


Enable codecov.io

Current coverage is 97.50% (diff: 100%)

No coverage report found for master at 0c63316.

Powered by Codecov. Last update 0c63316...7fea7c3


headscale: 0.7.1 -> 0.8.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/juanfont/headscale/releases.
meta.description for headscale is: "An implementation of the Tailscale coordination server"
meta.homepage for headscale is: "https://github.com/juanfont/headscale"
meta.changelog for headscale is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/smzf94q24hc4bmnvb379q1863mz3l7sj-headscale-0.8.1/bin/headscale passed the binary check.

1 of 1 passed binary check by having a zero exit code.

0 of 1 passed binary check by having the new version present in output.

found 0.8.1 with grep in /nix/store/smzf94q24hc4bmnvb379q1863mz3l7sj-headscale-0.8.1

found 0.8.1 in filename of file in /nix/store/smzf94q24hc4bmnvb379q1863mz3l7sj-headscale-0.8.1

directory tree listing: https://gist.github.com/51b0d2a12144f100bdda79b32f44e1e6

du listing: https://gist.github.com/91978442d88bcea90164ad53257a8c6d

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
headscale

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/smzf94q24hc4bmnvb379q1863mz3l7sj-headscale-0.8.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A headscale https://github.com/r-ryantm/nixpkgs/archive/e386c79730ea736a6ef51cee6f5b1c0c25345608.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/smzf94q24hc4bmnvb379q1863mz3l7sj-headscale-0.8.1
ls -la /nix/store/smzf94q24hc4bmnvb379q1863mz3l7sj-headscale-0.8.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

headscale

Maintainer pings
cc @NKJe @kalbasit for testing.

Result of nixpkgs-review pr 139030 run on x86_64-darwin 1

1 package built:

headscale


Wiki needs information detailing the Backstory and overall Gameplay of Technodungeon

We need something for the writer to go off of for when he/she creates the opening scroll for the game. So we'll need some backstory written up as well as some information detailing the overall gameplay.
It would also be a good idea to talk about the structure of how the game is played so that everyone is on the same page with the future of Technodungeon

Finished most of this now, detailing the Environment, two main players and backstory.
It would be nice to get more info up there on items, equipment, obstacles (traps, turrets, tripwires, etc) and the other NPC characters like the Drone and etc.
I would like to get some pictures on the Wiki once we develop some of this stuff that shows the basic game mechanic in action.. there are too many words up there nobody is going to read it right now.


take screenshots during the next cm in berlin

...to showcase the app in the repo and to have new screenshots for the play store

Yea - and let's meet there - really hope there will be no rain or snow ;-)
On 14.10.2015 18:37, stephan lindauer wrote:

...to showcase the app in the repo and to have new screenshots for the
play store
—
Reply to this email directly or view it on GitHub
https://github.com/criticalmaps/criticalmaps-android/issues/83.

--
best regards,
ligi
http://ligi.de

:+1:

:+1:

added new screenshots to the google play store


Fix annotation for default storage class

The current annotation that is set is prefixed with storageclass.beta.kubernetes.io https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/storage-class/aws/default.yaml

/cc @msau42

LGTM. Can you squash the commits please? Thanks!

Sure, all squashed now.
I also opened to change the annotation in the storage classes in k8s: https://github.com/kubernetes/kubernetes/pull/68345

alright, i am closing this then. The PR for the default annotation for the storage addons in the main repo is on its way.


Replace torch.allclose from tests

Description
We want to be framework agnostic (even if currently we are highly coupled with torch).
For this we should remove all torch specific functions from the files where there should be "generic"-like code.
One of those functions is allclose from torch.
This issue is to reove the allclose function from the test files.
Are you interested in working on this improvement yourself?

Yes, I am.

Additional Context
Check if pytest has an allclose function or check what other libraries (more general than torch) are doing this.

Hi, I could do this. It seems other instances use np.allclose, is this sufficient or would you also want to use the pytest api for those cases too? If so, there is the approx function from pytest: https://docs.pytest.org/en/latest/reference/reference.html?highlight=approx#pytest.approx

I think the approx would be great!


use declared prefixes in SPARQL construct results (or declare SOA prefixes in LPWC)

Continuing https://github.com/davidlamprecht/linkedpaperswithcode/issues/7, I tried this query at http://<IP_ADDRESS>:10216/sparql (will become https://linkedpaperswithcode.org/sparql shortly):
PREFIX dct: <http://purl.org/dc/terms/>
PREFIX org: <http://www.w3.org/ns/org#>
PREFIX soa: <https://semopenalex.org/ontology/>
PREFIX dct: <http://purl.org/dc/terms/>
construct {?org ?p ?o} where {
  {select ?x {[] dct:creator ?x} limit 1}
  {service <https://semopenalex.org/sparql> {
      ?x org:memberOf ?org.
      ?org ?p ?o
  }}
}

Unlike YasGUI that returns a table, this returns turtle, which is better:
@prefix schema: <https://schema.org/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix sp: <http://spinrdf.org/sp#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix org: <http://www.w3.org/ns/org#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .

<https://semopenalex.org/institution/I57206974> a <https://semopenalex.org/ontology/Institution>;
  owl:sameAs <https://makg.org/entity/57206974>, <https://www.wikidata.org/wiki/Q49210>;
  <http://purl.org/dc/terms/created> "2016-06-24"^^xsd:date;
  <http://purl.org/dc/terms/modified> "2024-05-30"^^xsd:date;
  rdfs:seeAlso <https://en.wikipedia.org/wiki/New%20York%20University>;
  <https://semopenalex.org/ontology/citedByCount> 8616587;
  <https://semopenalex.org/ontology/worksCount> 229236;
  <https://semopenalex.org/ontology/countsByYear> <https://semopenalex.org/countsByYear/I57206974Y2012>,
    <https://semopenalex.org/countsByYear/I57206974Y2013>, <https://semopenalex.org/countsByYear/I57206974Y2014>,
    <https://semopenalex.org/countsByYear/I57206974Y2015>, <https://semopenalex.org/countsByYear/I57206974Y2016>,
    <https://semopenalex.org/countsByYear/I57206974Y2017>, <https://semopenalex.org/countsByYear/I57206974Y2018>,
    <https://semopenalex.org/countsByYear/I57206974Y2019>, <https://semopenalex.org/countsByYear/I57206974Y2020>,
    <https://semopenalex.org/countsByYear/I57206974Y2021>, <https://semopenalex.org/countsByYear/I57206974Y2022>,
    <https://semopenalex.org/countsByYear/I57206974Y2023>, <https://semopenalex.org/countsByYear/I57206974Y2024>;
  <https://semopenalex.org/ontology/magId> 57206974;
  <https://dbpedia.org/property/countryCode> "US";
  foaf:name "New York University";
  <https://semopenalex.org/ontology/ror> "https://ror.org/0190ak572";
  <https://dbpedia.org/ontology/alternativeName> "Universidad de Nueva York", "Université de New York";
  foaf:depiction "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/Nyu%20short%20color.svg";
  foaf:homepage "http://www.nyu.edu/";
  <https://dbpedia.org/ontology/location> <https://semopenalex.org/geo/I57206974>;
  <https://dbpedia.org/property/acronym> "NYU";
  <https://semopenalex.org/ontology/grid> "grid.137628.9";
  <https://semopenalex.org/ontology/imageThumbnail> "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/Nyu%20short%20color.svg&width=300";
  <https://semopenalex.org/ontology/rorType> "education";
  <https://semopenalex.org/ontology/hasChildInstitution> <https://semopenalex.org/institution/I258800397>,
    <https://semopenalex.org/institution/I120250893>, <https://semopenalex.org/institution/I36672615>,
    <https://semopenalex.org/institution/I2799442855>, <https://semopenalex.org/institution/I4210123063>,
    <https://semopenalex.org/institution/I4210165353>;
  <https://semopenalex.org/ontology/hasAssociatedInstitution> <https://semopenalex.org/institution/I4210086933>,
    <https://semopenalex.org/institution/I2802707398>, <https://semopenalex.org/institution/I2800015068>,
    <https://semopenalex.org/institution/I4210108985>, <https://semopenalex.org/institution/I4210163050>,
    <https://semopenalex.org/institution/I4210160702>, <https://semopenalex.org/institution/I42102869> .

<https://semopenalex.org/institution/I27837315> a <https://semopenalex.org/ontology/Institution>;
  owl:sameAs <https://makg.org/entity/27837315>, <https://www.wikidata.org/wiki/Q230492>;
  <http://purl.org/dc/terms/created> "2016-06-24"^^xsd:date;
  <http://purl.org/dc/terms/modified> "2024-05-29"^^xsd:date;
  rdfs:seeAlso <https://en.wikipedia.org/wiki/University%20of%20Michigan>;
  <https://semopenalex.org/ontology/citedByCount> 17535410;
  <https://semopenalex.org/ontology/worksCount> 885687;
  <https://semopenalex.org/ontology/countsByYear> <https://semopenalex.org/countsByYear/I27837315Y2012>,
    <https://semopenalex.org/countsByYear/I27837315Y2013>, <https://semopenalex.org/countsByYear/I27837315Y2014>,
    <https://semopenalex.org/countsByYear/I27837315Y2015>, <https://semopenalex.org/countsByYear/I27837315Y2016>,
    <https://semopenalex.org/countsByYear/I27837315Y2017>, <https://semopenalex.org/countsByYear/I27837315Y2018>,
    <https://semopenalex.org/countsByYear/I27837315Y2019>, <https://semopenalex.org/countsByYear/I27837315Y2020>,
    <https://semopenalex.org/countsByYear/I27837315Y2021>, <https://semopenalex.org/countsByYear/I27837315Y2022>,
    <https://semopenalex.org/countsByYear/I27837315Y2023>, <https://semopenalex.org/countsByYear/I27837315Y2024>;
  <https://semopenalex.org/ontology/magId> 27837315;
  <https://dbpedia.org/property/countryCode> "US";
  foaf:name "University of Michigan–Ann Arbor";
  <https://semopenalex.org/ontology/ror> "https://ror.org/00jmfr291";
  <https://dbpedia.org/ontology/alternativeName> "University of Michigan", "UMich",
    "Université du Michigan";
  foaf:depiction "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/University%20of%20Michigan%20logo.svg";
  foaf:homepage "https://www.umich.edu";
  <https://dbpedia.org/ontology/location> <https://semopenalex.org/geo/I27837315>;
  <https://dbpedia.org/property/acronym> "UM";
  <https://semopenalex.org/ontology/grid> "grid.214458.e";
  <https://semopenalex.org/ontology/imageThumbnail> "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/University%20of%20Michigan%20logo.svg&width=300";
  <https://semopenalex.org/ontology/rorType> "education";
  <https://semopenalex.org/ontology/hasChildInstitution> <https://semopenalex.org/institution/I4210163254>,
    <https://semopenalex.org/institution/I4210104572>, <https://semopenalex.org/institution/I4210130704>,
    <https://semopenalex.org/institution/I4210092198>;
  <https://semopenalex.org/ontology/hasAssociatedInstitution> <https://semopenalex.org/institution/I2801799315>,
    <https://semopenalex.org/institution/I4210114445> .

<https://semopenalex.org/institution/I36672615> a <https://semopenalex.org/ontology/Institution>;
  owl:sameAs <https://makg.org/entity/36672615>, <https://www.wikidata.org/wiki/Q946028>;
  <http://purl.org/dc/terms/created> "2016-06-24"^^xsd:date;
  <http://purl.org/dc/terms/modified> "2024-05-30"^^xsd:date;
  rdfs:seeAlso <https://en.wikipedia.org/wiki/Courant%20Institute%20of%20Mathematical%20Sciences>;
  <https://semopenalex.org/ontology/citedByCount> 723289;
  <https://semopenalex.org/ontology/worksCount> 14169;
  <https://semopenalex.org/ontology/countsByYear> <https://semopenalex.org/countsByYear/I36672615Y2012>,
    <https://semopenalex.org/countsByYear/I36672615Y2013>, <https://semopenalex.org/countsByYear/I36672615Y2014>,
    <https://semopenalex.org/countsByYear/I36672615Y2015>, <https://semopenalex.org/countsByYear/I36672615Y2016>,
    <https://semopenalex.org/countsByYear/I36672615Y2017>, <https://semopenalex.org/countsByYear/I36672615Y2018>,
    <https://semopenalex.org/countsByYear/I36672615Y2019>, <https://semopenalex.org/countsByYear/I36672615Y2020>,
    <https://semopenalex.org/countsByYear/I36672615Y2021>, <https://semopenalex.org/countsByYear/I36672615Y2022>,
    <https://semopenalex.org/countsByYear/I36672615Y2023>, <https://semopenalex.org/countsByYear/I36672615Y2024>;
  <https://semopenalex.org/ontology/magId> 36672615;
  <https://dbpedia.org/property/countryCode> "US";
  foaf:name "Courant Institute of Mathematical Sciences";
  <https://semopenalex.org/ontology/ror> "https://ror.org/037tm7f56";
  foaf:depiction "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/WarrenWeaverHall.JPG";
  foaf:homepage "http://www.cims.nyu.edu/";
  <https://dbpedia.org/ontology/location> <https://semopenalex.org/geo/I36672615>;
  <https://dbpedia.org/property/acronym> "CIMS";
  <https://semopenalex.org/ontology/grid> "grid.482020.c";
  <https://semopenalex.org/ontology/imageThumbnail> "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/WarrenWeaverHall.JPG&width=300";
  <https://semopenalex.org/ontology/rorType> "education";
  <https://semopenalex.org/ontology/hasParentInstitution> <https://semopenalex.org/institution/I57206974> .

However, it doesn't use prefixed declared in the query.
I suspect it only uses namespaces existing in the LPWC repo.
If that is the case, then please define all SOA prefixes in the LPWC repo.

Hi @VladimirAlexiev ,
I have added all namespaces from the semopenalex.org metaphactory to the linkedpaperswithcode.com metaphactory.
Let me know if any namespaces are still missing. Then I will define them too.
Your provided Query now returns the following result when being executed against https://linkedpaperswithcode.com/sparql:

@prefix schema: <https://schema.org/> .
@prefix soa: <https://semopenalex.org/ontology/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix sp: <http://spinrdf.org/sp#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix dbprop: <https://dbpedia.org/property/> .
@prefix jsfn: <http://www.ontotext.com/js#> .
@prefix wgs: <http://www.w3.org/2003/01/geo/wgs84_pos#> .
@prefix dbpedia-owl: <https://dbpedia.org/ontology/> .
@prefix org: <http://www.w3.org/ns/org#> .
@prefix fabio: <http://purl.org/spar/fabio/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .

<https://semopenalex.org/institution/I57206974> a soa:Institution;
  owl:sameAs <https://makg.org/entity/57206974>, <https://www.wikidata.org/wiki/Q49210>;
  dct:created "2016-06-24"^^xsd:date;
  dct:modified "2024-05-30"^^xsd:date;
  rdfs:seeAlso <https://en.wikipedia.org/wiki/New%20York%20University>;
  soa:citedByCount 8616587;
  soa:worksCount 229236;
  soa:countsByYear <https://semopenalex.org/countsByYear/I57206974Y2012>, <https://semopenalex.org/countsByYear/I57206974Y2013>,
    <https://semopenalex.org/countsByYear/I57206974Y2014>, <https://semopenalex.org/countsByYear/I57206974Y2015>,
    <https://semopenalex.org/countsByYear/I57206974Y2016>, <https://semopenalex.org/countsByYear/I57206974Y2017>,
    <https://semopenalex.org/countsByYear/I57206974Y2018>, <https://semopenalex.org/countsByYear/I57206974Y2019>,
    <https://semopenalex.org/countsByYear/I57206974Y2020>, <https://semopenalex.org/countsByYear/I57206974Y2021>,
    <https://semopenalex.org/countsByYear/I57206974Y2022>, <https://semopenalex.org/countsByYear/I57206974Y2023>,
    <https://semopenalex.org/countsByYear/I57206974Y2024>;
  soa:magId 57206974;
  dbprop:countryCode "US";
  foaf:name "New York University";
  soa:ror "https://ror.org/0190ak572";
  dbpedia-owl:alternativeName "Universidad de Nueva York", "Université de New York";
  foaf:depiction "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/Nyu%20short%20color.svg";
  foaf:homepage "http://www.nyu.edu/";
  dbpedia-owl:location <https://semopenalex.org/geo/I57206974>;
  dbprop:acronym "NYU";
  soa:grid "grid.137628.9";
  soa:imageThumbnail "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/Nyu%20short%20color.svg&width=300";
  soa:rorType "education";
  soa:hasChildInstitution <https://semopenalex.org/institution/I258800397>, <https://semopenalex.org/institution/I120250893>,
    <https://semopenalex.org/institution/I36672615>, <https://semopenalex.org/institution/I2799442855>,
    <https://semopenalex.org/institution/I4210123063>, <https://semopenalex.org/institution/I4210165353>;
  soa:hasAssociatedInstitution <https://semopenalex.org/institution/I4210086933>, <https://semopenalex.org/institution/I2802707398>,
    <https://semopenalex.org/institution/I2800015068>, <https://semopenalex.org/institution/I4210108985>,
    <https://semopenalex.org/institution/I4210163050>, <https://semopenalex.org/institution/I4210160702>,
    <https://semopenalex.org/institution/I42102869> .

<https://semopenalex.org/institution/I27837315> a soa:Institution;
  owl:sameAs <https://makg.org/entity/27837315>, <https://www.wikidata.org/wiki/Q230492>;
  dct:created "2016-06-24"^^xsd:date;
  dct:modified "2024-05-29"^^xsd:date;
  rdfs:seeAlso <https://en.wikipedia.org/wiki/University%20of%20Michigan>;
  soa:citedByCount 17535410;
  soa:worksCount 885687;
  soa:countsByYear <https://semopenalex.org/countsByYear/I27837315Y2012>, <https://semopenalex.org/countsByYear/I27837315Y2013>,
    <https://semopenalex.org/countsByYear/I27837315Y2014>, <https://semopenalex.org/countsByYear/I27837315Y2015>,
    <https://semopenalex.org/countsByYear/I27837315Y2016>, <https://semopenalex.org/countsByYear/I27837315Y2017>,
    <https://semopenalex.org/countsByYear/I27837315Y2018>, <https://semopenalex.org/countsByYear/I27837315Y2019>,
    <https://semopenalex.org/countsByYear/I27837315Y2020>, <https://semopenalex.org/countsByYear/I27837315Y2021>,
    <https://semopenalex.org/countsByYear/I27837315Y2022>, <https://semopenalex.org/countsByYear/I27837315Y2023>,
    <https://semopenalex.org/countsByYear/I27837315Y2024>;
  soa:magId 27837315;
  dbprop:countryCode "US";
  foaf:name "University of Michigan–Ann Arbor";
  soa:ror "https://ror.org/00jmfr291";
  dbpedia-owl:alternativeName "University of Michigan", "UMich", "Université du Michigan";
  foaf:depiction "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/University%20of%20Michigan%20logo.svg";
  foaf:homepage "https://www.umich.edu";
  dbpedia-owl:location <https://semopenalex.org/geo/I27837315>;
  dbprop:acronym "UM";
  soa:grid "grid.214458.e";
  soa:imageThumbnail "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/University%20of%20Michigan%20logo.svg&width=300";
  soa:rorType "education";
  soa:hasChildInstitution <https://semopenalex.org/institution/I4210163254>, <https://semopenalex.org/institution/I4210104572>,
    <https://semopenalex.org/institution/I4210130704>, <https://semopenalex.org/institution/I4210092198>;
  soa:hasAssociatedInstitution <https://semopenalex.org/institution/I2801799315>, <https://semopenalex.org/institution/I4210114445> .

<https://semopenalex.org/institution/I36672615> a soa:Institution;
  owl:sameAs <https://makg.org/entity/36672615>, <https://www.wikidata.org/wiki/Q946028>;
  dct:created "2016-06-24"^^xsd:date;
  dct:modified "2024-05-30"^^xsd:date;
  rdfs:seeAlso <https://en.wikipedia.org/wiki/Courant%20Institute%20of%20Mathematical%20Sciences>;
  soa:citedByCount 723289;
  soa:worksCount 14169;
  soa:countsByYear <https://semopenalex.org/countsByYear/I36672615Y2012>, <https://semopenalex.org/countsByYear/I36672615Y2013>,
    <https://semopenalex.org/countsByYear/I36672615Y2014>, <https://semopenalex.org/countsByYear/I36672615Y2015>,
    <https://semopenalex.org/countsByYear/I36672615Y2016>, <https://semopenalex.org/countsByYear/I36672615Y2017>,
    <https://semopenalex.org/countsByYear/I36672615Y2018>, <https://semopenalex.org/countsByYear/I36672615Y2019>,
    <https://semopenalex.org/countsByYear/I36672615Y2020>, <https://semopenalex.org/countsByYear/I36672615Y2021>,
    <https://semopenalex.org/countsByYear/I36672615Y2022>, <https://semopenalex.org/countsByYear/I36672615Y2023>,
    <https://semopenalex.org/countsByYear/I36672615Y2024>;
  soa:magId 36672615;
  dbprop:countryCode "US";
  foaf:name "Courant Institute of Mathematical Sciences";
  soa:ror "https://ror.org/037tm7f56";
  foaf:depiction "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/WarrenWeaverHall.JPG";
  foaf:homepage "http://www.cims.nyu.edu/";
  dbpedia-owl:location <https://semopenalex.org/geo/I36672615>;
  dbprop:acronym "CIMS";
  soa:grid "grid.482020.c";
  soa:imageThumbnail "https://commons.wikimedia.org/w/index.php?title=Special:Redirect/file/WarrenWeaverHall.JPG&width=300";
  soa:rorType "education";
  soa:hasParentInstitution <https://semopenalex.org/institution/I57206974> .

@davidlamprecht Thanks!! But I noticed a mistake about dbpedia:

DBpedia terms use http, you've used https: will need a data migration :-(
please replace these with shorter and more popular variants (as per prefix.cc):
dbpedia-owl -> dbo
dbprop -> dbp

@VladimirAlexiev thanks for the feedback.
I have updated:
dbpedia-owl -> dbo
dbprop -> dbp
The correct use of http to DBpedia is already tracked in Issue 3:
https://github.com/davidlamprecht/linkedpaperswithcode/issues/3 we will update our mappings for the next LPWC Version.

@VladimirAlexiev I have updated all DBpedia terms in the current data and Ontology from https to http.

@davidlamprecht
Please register these prefixes as well (the shoemaker goes barefoot :-)
PREFIX lpwcc: <https://linkedpaperswithcode.com/class/>
PREFIX lpwc: <https://linkedpaperswithcode.com/property/>

I've added them to prefix.cc


Update update-version-scripts to change test matrix

https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/core/supported-version-matrix.json
Originally posted by @lmolkova in https://github.com/Azure/azure-sdk-for-java/pull/24312#pullrequestreview-763303384

Closing as what this was referencing no longer exists, but I believe this was a request to update the version validation test matrix used to validate a set of Reactor, Reactor Netty, and Jackson versions which is kept up to date.


Modify print help message & Add Tox Configuration

Description
Modify print help message
Add Tox Configuration
Type of change
Please insert 'x' one of the type of change.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[x] Refactoring, Maintenance
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Please commit with sign-off.

I'll Pull Request again


Update maintainers according to contribution

There is actually a point to that listing that has little to do with contributors.
One of the rules that come along with being in the JS Foundation, your lib owners need to be clearly visible the community so they know who the responsible parties are.
That said, the way we approach it with a lib that has a / multiple lead maintainers they are listed first & the blanks are filled in by the webpack-contrib owners. i.e. myself, Juho, Sean.


Add initial CODEOWNERS file

Codecov Report
Base: 34.12% // Head: 34.12% // No change to project coverage :thumbsup:

Coverage data is based on head (32357bc) compared to base (691f6b7).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #69   +/-   ##
=======================================
  Coverage   34.12%   34.12%
=======================================
  Files          42       42
  Lines        8036     8036
=======================================
  Hits         2742     2742
  Misses       5077     5077
  Partials      217      217

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

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


ArgoCD Operator 0.6 does not process ApplicationSet manifests

Checklist:

[x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
[x] I've included steps to reproduce the bug.
[x] I've pasted the output of argocd version.

Describe the bug
We are using operatorhub.io to install and manage ArgoCd. Our ApplicationSets do not create applications anymore. (It was working before)
To Reproduce
chart
apiVersion: v2
name: argocd-operator
description: Deploys the OLM resources to start an ArgoCD operator
type: application
version: 0.1.0
appVersion: "v0.3.0"

applicationset manifest
# Source: team-ns/templates/argocd/argocd-applicationset.yaml
apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: team-admin-nodejs-helloworld
  namespace: argocd # ApplicationSets must always be in the argocd namespace
spec:
  generators:
  - git:
      repoURL: https://gitea.<IP_ADDRESS>.nip.io/otomi/values.git
      revision: HEAD
      files:
      - path: "env/teams/workloads/admin/nodejs-helloworld.yaml"
  template:
    metadata:
      name: 'team-admin-nodejs-helloworld'
    spec:
      project: 'team-admin' # project is restricted
      source:
        repoURL: 'https://github.com/redkubes/nodejs-helloworld.git'
        targetRevision: 'HEAD'
        path: 'chart/hello-world'
        chart: ''
        helm:
          # The argocd template the values parameter is taken from the git generator path
          values: '{{values}}'
          releaseName: 'nodejs-helloworld'
      syncPolicy:
        automated:
          allowEmpty: false
          prune: false
          selfHeal: true
        retry:
          backoff:
            duration: 10s
            factor: 3
          limit: 3
        syncOptions: []
      destination:
        server: 'https://kubernetes.default.svc'
        namespace: 'team-admin'
        # helm-specific config
---

Expected behavior
Application should popup within argocd console.

Version
ArgoCD Version: v2.6.3+e05298b

Logs
olm/olm-operator
time="2023-04-30T23:44:28Zlevel=debug msg="failed to get the owner subscription csv=packageserver
time="2023-04-30T23:44:28Zlevel=debug msg="no env var to inject into csvcsv=packageserver
time="2023-04-30T23:44:28Zlevel=debug msg="skipping copy for OwnNamespace operatorgroupcsv=packageserver id=9RZ/t namespace=olm phase=Succeeded
time="2023-04-30T23:44:28Zlevel=debug msg="skipping copy for OwnNamespace operatorgroupcsv=argocd-operator.v0.6.0 id=F+Ztq namespace=argocd phase=Succ
time="2023-04-30T23:44:43Zlevel=debug msg="Processing olmConfig
time="2023-04-30T23:46:20Zlevel=debug msg="syncing CSVcsv=packageserver id=Abhp+ namespace=olm phase=Succeeded
time="2023-04-30T23:46:20Zlevel=debug msg="syncing CSVcsv=argocd-operator.v0.6.0 id=hzRJ5 namespace=argocd phase=Succeeded
time="2023-04-30T23:46:20Zlevel=debug msg="annotations correctannotationTargets=olm opgroupTargets=olm
time="2023-04-30T23:46:20Zlevel=debug msg="annotations correctannotationTargets=argocd opgroupTargets=argocd
time="2023-04-30T23:46:20Zlevel=debug msg="csv in operatorgroupcsv=packageserver id=yWlNd namespace=olm opgroup=olm-operators phase=Succeeded
time="2023-04-30T23:46:20Zlevel=debug msg="csv in operatorgroupcsv=argocd-operator.v0.6.0 id=UQ4/M namespace=argocd opgroup=argocd-operator phase=Succ
time="2023-04-30T23:46:20Zlevel=debug msg="no intersecting operatorgroups provide the same apisapis=PackageManifest.v1.packages.operators.coreos.com c
time="2023-04-30T23:46:20Zlevel=debug msg="no intersecting operatorgroups provide the same apisapis="AppProject.v1alpha1.argoproj.io,Application.v1alp
time="2023-04-30T23:46:20Zlevel=debug msg="checking packageserver
time="2023-04-30T23:46:20Zlevel=debug msg="checking if csv is replacing an older version
time="2023-04-30T23:46:20Zlevel=debug msg="checking argocd-operator.v0.6.0
time="2023-04-30T23:46:20Zlevel=debug msg="checking if csv is replacing an older version
time="2023-04-30T23:46:20Zlevel=debug msg="unable to get previous csverror="clusterserviceversions.operators.coreos.com \"argocd-operator.v0.5.0\not
time="2023-04-30T23:46:20Zlevel=debug msg="perm.ServiceAccountName: olm-operator-serviceaccount
time="2023-04-30T23:46:20Zlevel=debug msg="perm.ServiceAccountName: argocd-operator-controller-manager
time="2023-04-30T23:46:20Zlevel=debug msg="failed to get the owner subscription csv=packageserver
time="2023-04-30T23:46:20Zlevel=debug msg="no env var to inject into csvcsv=packageserver
time="2023-04-30T23:46:20Zlevel=debug msg="perm.ServiceAccountName: argocd-operator-controller-manager
time="2023-04-30T23:46:20Zlevel=debug msg="skipping copy for OwnNamespace operatorgroupcsv=argocd-operator.v0.6.0 id=hzRJ5 namespace=argocd phase=Succ
time="2023-04-30T23:46:20Zlevel=debug msg="skipping copy for OwnNamespace operatorgroupcsv=packageserver id=Abhp+ namespace=olm phase=Succeeded

Hi @leiarenee , which helm chart are you using to deploy this operator ? Can you please provide more steps and information ? To me, it looks like an invalid issue for this repo.

Hi @iam-veeramalla You can see it in our open source repo here
https://github.com/redkubes/otomi-core/tree/main/charts/argocd-operator
My colleague fixed it by explicitly defining version as 0.5 which prevents auto updates.

Hi @leiarenee , we are not the maintianers of that opensource project that helps you install the Argo CD operator. Please use the instructions in the repo to install the operator or you can also install from operatorhub.io

Hi there,
There is similar issue with operator in version 0.7.0.
I am using OLM to deploy the operator
In below snippet there is a very basic config for the applicationSet controller.
The operator seems to ignore it. I can't see any logs. The rest of the argocd deployments are created and configured as expected. In the status property you can also see the status applicationSetController: Unknown
I am a bit puzzled here as the same configuration was working with operator v0.5.0.


new point release

          if we do a point release soon (which I think we were planning to do), then lets include a note about this (and maybe warning when run under Python 3.8 or 3.9). then as soon as that's released, bump the minimum python version to 3.10 and start using those language features.

thoughts?
Originally posted by @williballenthin in https://github.com/mandiant/capa/issues/1966#issuecomment-2385957492

+1 for a point release, we've recently merged some bug fixes for the dynamic backends that would be good to push to our users.