vimPlugins.elixir-tools-nvim: init at 2023-04-20

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

you have to run the update script afterwards, for instance pkgs/applications/editors/vim/plugins/update.py --proc 5 --github-token $GITHUB_TOKEN

I've run the update script, the behavior was seemingly change.


Update Stackdriver Logging documentation

Update obsolete Stackdriver Logging documentation: it's now possible to enable/disable Stackdriver Logging in a running GKE cluster

This change is

/cc @piosz

/lgtm


[CARBONDATA-2532][Integration] Carbon to support spark 2.3 version

## What changes were proposed in this pull request?
In this PR inorder to hide the compatibility issues of columnar vector API's from the existing common classes, i introduced an interface of the proxy vector readers, this
proxy vector readers will take care the compatibility issues with respect to spark different versions.
Column vector and Columnar Batch interface compatibility issues has been addressed in this PR, The changes were related to below modifications done in spark interface.

Highlights:
a) This is a refactoring of ColumnVector hierarchy and related classes.
b) make ColumnVector read-only
c) introduce WritableColumnVector with write interface
d) remove ReadOnlyColumnVector
e) Fixed spark-carbon integration API compatibility issues - By sandeep katta
f) Corrected the testcases based on spark 2.3.0 behaviour change  - By sandeep katta
g)  Excluded following dependency from pom.xml files <groupId>net.jpountz</groupId><artifactId>lz4</artifactId> as spark 2.3.0 changed
      it to org.lz4, so removed from the test class path of spark2,spark-common-test,spark2-examples
 - By sandeep katta
## How was this patch tested?
Manual testing, and existing test-case execution

Please review and let us know for any suggestions.
While squashing please squash the commits independently of mine and sandeep as both of us has commits related to this upgrade activity.

@gvramana

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6285/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5248/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5249/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6286/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5124/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6330/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5282/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5236/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6402/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5347/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5245/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6411/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5351/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6442/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6447/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5278/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6581/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5420/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6614/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5602/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5605/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5591/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6769/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6797/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6808/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6876/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5664/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5665/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6901/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5683/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5690/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6948/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5731/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6960/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5749/

LGTM

Merged to "carbonstore" branch.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7270/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5897/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6039/

New PR has been raised
https://github.com/apache/carbondata/pull/2524


test: added tests for import, export and fork application

Description
This PR contains tests for importing, exporting and forking an application and validating data binding for all apps.
Fixes #10203

if no issue exists, please create an issue and ask the maintainers about this first

How Has This Been Tested?
locally
Checklist:

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

/ok-to-test sha=1006ea6

/ok-to-test sha=918b6b7


Add missing css imports

Added missing css imports in some PresentationInstanceFilterBuilder related components. Missing imports resulted in components being rendered without styling in cases when css classes used in those components where nor loaded globally.
Also updated beachball config. Looks like message property from config is used for both publish and change commands. This resulted in pnpm change script generating change files with same message.

This PR should be undone. Manually importing unlayered CSS from @itwin/itwinui-css causes styling issues downstream. And as of<EMAIL_ADDRESS>the entire iTwinUI stylesheet is automatically injected by default anyway, negating the need for such imports. More details.
To tackle the root cause, instead of using classes from @itwin/itwinui-css, it is recommended to directly use components (<Select>, <Input>, <Tag>, etc) from @itwin/itwinui-react. If you find that some components do not fully meet your needs, you can open an issue in the iTwinUI repo.

This PR should be undone. Manually importing unlayered CSS from @itwin/itwinui-css causes styling issues downstream. And as of<EMAIL_ADDRESS>the entire iTwinUI stylesheet is automatically injected by default anyway, negating the need for such imports. More details.
To tackle the root cause, instead of using classes from @itwin/itwinui-css, it is recommended to directly use components (<Select>, <Input>, <Tag>, etc) from @itwin/itwinui-react. If you find that some components do not fully meet your needs, you can open an issue in the iTwinUI repo.

Created an issue for this https://github.com/iTwin/presentation/issues/287. I will switch to itwinui-react components where possible.


Add Product UI to show products that are unlocked/researched

Suggestion
Request setting to show only unlocked products in the Add Product UI

I thought about this in the past, and it's not a bad idea, but it's kinda hard to implement I feel. I'll give it a go at some point though. Thanks for the suggestion.

This is still something I am considering to do at some point, as part of a bigger system.


Per User TimeZone settings

It would be good to be able to setup timezone preferences on a user/account level rather than Huginn-wide (though obviously that can still control the default)
Running a 6pm on a server configured for a different timezone becomes a bit of a mindbend.

Rather than per user, why not storing everything in UTC and using the browser client time zone to set the times to the user?

I set up docker image and got timezone problem, so this would have been nice feature to have.


Superficial downstream Typescript support

You can fake support of Typescript for parsers without actually meaningfully supporting it, but still provide some value to downstream users
All that it takes in practice is adding a string for the output type
This could be supported as an argument in the options tuple, with basically no other changes
The end result of such a thing is that output from the parser would be easy to integrate into a typescript project, and would receive non-trivial (though still incomplete) typechecking
If I provided a PR that did this, and it was short and not awful, would it be considered?

This was previously https://github.com/pegjs/pegjs/issues/562

Yes, I'm interested in this.

(assuming backward-compat, opt-in, and clean enough syntax for its use that doesn't conflict with anything else that's on the table) :)

Everything I do will expect backward compatability and either opt-in or safe default.  I am an absolutist about backcompat.
I will try my best to not conflict with other things, but I would appreciate help in that regard.


Allow excluding inlined enum from type generation

Description
Consider this schema:
{
  "components": {
    "schemas": {
      "SegmentFeature": {
        "required": ["type"],
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "enum": ["Feature"]
          }
        }
      }
    }
  }
}

Which Generates this code intypes.gen.ts:
export type type = 'Feature';

export const type = {
  FEATURE: 'Feature',
} as const;

export type SegmentFeature = {
  type: 'Feature';
};

While the name type is problematic (see #1281), I would also like disable generation of the first two types of such inline enums (enums, which are not themself schema).
It is currently not possible to exclude this generation. input.include isn't even called on the inline enum by itself.
So either have some configuration for such inline enums or this could be also part of a generalized approach?
Preferred output in this case would be to have the two first type declarations removed:
- export type type = 'Feature';

- export const type = {
-   FEATURE: 'Feature',
- } as const;

export type SegmentFeature = {
  type: 'Feature';
};

Will add – suggestions for config naming are welcome!

TBH naming this is is quite hard... I guess it should live within @hey-api/types? One option could be to extends enums to an object?
{
  name: '@hey-api/types';
  enums: {
    emit: 'javascript' | ‘typescript';
    include: 'ref' | 'inline' | 'all';
  },
}

But I actually don't see a use case for include: 'inline'. Other options would be:
{
  name: '@hey-api/types';
  enums: {
    emit: 'javascript' | ‘typescript';
    includeInline: boolean;
  },
}

or
{
  name: '@hey-api/types';
  enums: 'javascript' | ‘typescript';
  includeInlineEnums: boolean;
}

Awesome improvement, thank you so much! 🚀


Error while Running a Multi-Feature topeka Instant App

Error:A problem was found with the configuration of task ':topekaapk:dataBindingExportBuildInfoDebug'.

Directory 'F:\downloads\topeka\topekaapk\build\intermediates\data-binding-info\debug' specified for property 'xmlOutFolder' does not exist.

I am unable to reproduce this issue. Did you try cleaning your build first? If you are still seeing this issue try repeating the codelab from scratch.


Fix $GITHUB_SHA in coverage upload

Hi! I think there is a problem with values returned by GITHUB_SHA for pull_request events. I have to update the documentation, but here's a setup that should work for you. I will also update the uploader script to produce more useful output on errors!
https://github.community/t/github-sha-not-the-same-as-the-triggering-commit/18286/2

Here's a PR to my fork where the check is failing as expected: https://github.com/grodowski/undercoverci_demo_ruby/pull/1

@grodowski thanks!


Update on usage (data-animate-scroll)

Instead of
Go to Element

We might as well make use of data-animate-scroll in which the library listen for on-click events on elements having the data attribute? For example,

I thought of using the data api earlier but due to lack of time I wasn't able to add, anyways I will be adding support for them soon.
If you're comfortable with javascript, you can even contribute by sending a pull request.


Added java solution to remove kth node from end of linkedlist

Hey
@akgmage I just added java solution to remove kth node from end of linkedlist.
Please merge my PR , so that other able to see my changes.

ok


Create existing_payment/_stripe.html.erb

As described in https://github.com/solidusio/solidus_gateway/issues/48, Solidus 2.2 created the need for views in the existing_payment folder, but no such views exist in solidus_gateway. This created issues where customers could not checkout using solidus_gateway methods (in our case, Stripe).
This PR creates a primitive _stripe view which just renders the default gateway view. Nothing special, but it should fix this issue.
This may also fix https://github.com/solidusio/solidus_gateway/issues/30 as well, depending on what exactly was the root cause of that.

I'm having this issue as well. Thanks for making a pull! Not sure why they haven't merged it yet.

This definitely should be merged in for all stores using Stripe and @wallet_payment_sources

Sorry, that this took so long.


[AutoPR recoveryservicessiterecovery/resource-manager] typo: recoveryservicessiterecovery/resource-manager/Microsoft.RecoveryServices

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4749

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/690


[BUG] window.appInsights.properties is marked private

Description/Screenshot
README.md says that window.appInsights.properties.context.telemetryTrace.traceID is the way to get/set the trace ID, however the properties field is marked private in the types so I can't access it in my code. Either it's wrongly marked private, or I need a different way to get trace ID.
Thanks for your help! Use case is to show the trace ID in the error message that we show the user after a service call failure.

My ugly workaround:
// Pull the W3C trace context ID from AI and add it to the error message.
// See https://github.com/microsoft/ApplicationInsights-JS/issues/1232 for why the any cast is needed.
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const w3cTraceId = (window.appInsights as any).properties.context.telemetryTrace.traceID;

Hi,
After investigating this issue you don't need your ugly workaround, instead you will find that the appInsights object already has a public 'context' value which is a reference to the .properties.context instance.
So the issue is basically a documentation one (after calling loadAppInsights), so I'm going to update the README to read (as below) and ensure that the context value is assigned during the construction of the instance as opposed to only during the loadAppInsights() method as it is today.
window.appInsights.context.telemetryTrace.traceID

Thanks! window.appInsights.context is always undefined for me when using "Snippet Setup", so if your code change makes that work then that's exactly what I need :)

There was an issue with the way this value was propagated to the snippet, which I've fixed with the #1236 PR, this will be included in the next release

Fixed deployed as NPM and next CDN channels

Now also fully deployed to primary CDN


Manage promotions with Expeditor

The second phase of release automation for this repository is to allow promotion to occur within Expeditor. This will require adding a chef account as a contributor and storing the key in vault.

@tas50 is this the relevant info for the promotion process?
https://code.visualstudio.com/api/working-with-extensions/publishing-extension


POST, PUT, and PATCH requests with NULL body should be allowed

The resolution to issue #1131 was that certain request types (POST, PUT, PATCH) are no longer allowed to have no body. However, this is not in line with the HTTP specifications.
Nowhere in the HTTP spec is mentioned that a body is required for POST requests: https://www.rfc-editor.org/rfc/rfc7231#section-4.3.3
An earlier version of the spec explicitly defined that a request payload  is optional for all request types: https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-p3-payload-11#section-3
In this thread you can find responses from HTTP working group members that indicates POST requests without a body should be valid: https://lists.w3.org/Archives/Public/ietf-http-wg/2010JulSep/0272.html

Can you describe what you are trying to achieve? Is there some API that takes advantage/requires this?
I expect it would take a strong justification for us to change this.  The email thread is from 4 years before the current spec, so I'm not sure how to read that exactly.
We often look at other clients and standards, so evidence that this is a common implementation choice would help.  Looking at docs like Mozilla Docs they agree with the current implementation
https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST - Request Body  - Yes
https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/DELETE - Request Body - May

We have a transaction approval system that allows users to signal they approve a transaction by making a POST request to and endpoint that looks like https://api.service.com/approvals/<approval-id>/ok. This system has been in use and functioning for years on our web platform.
We have Android and iOS applications that expose web functionality through webviews, allowing us to reuse our web platform to service mobile customers. Here we intercept all API requests made in the webview, and route them through the mobile app security framework.
On every other platform (web, iOS) everything is working as expected, but the transaction approval system is broken on Android because this library won't forward the POST requests without a body.
We now have to implement workarounds (by attaching emptystring bodies to requests without a body) specifically to keep systems that use this library from failing. Since this library is the only HTTP request tool across all platforms we use that is breaking on these requests, I would consider its behaviour outside the norm, specifically because the HTTP standard does not disallow these types of request.
It looks to me like the Mozilla documentation is also incorrect on this topic. Thanks for bringing it to my attention, I will create an issue there as well.

I'll wait for others to weigh in on this, it's comforting to know that you have a workaround for this (empty body), so you are not currently blocked.

As an evidence that other clients commonly support sending POST requests without body, I propose looking at the behaviour of web browsers.
You can try this by going to httpbin.org in your browser of choice and running this code:
const http = new XMLHttpRequest();
http.open('POST', "http://httpbin.org/anything");
http.onreadystatechange = () => console.log(http.responseText);
http.send();

As far as I know all (major) browsers will happily send an HTTP POST request with no body.

@ruphin is the a meaningful difference between an empty body and no body at all?

I think yes. For one, this library will send a request with empty body but refuse to send one with no body ;)
Over the wire the difference is expressed by the presence of "Content-Length" header. According to the spec, a message with a body MUST have a "Content-Length" (or "Transfer-Encoding") header. The content length MUST be 0 or higher. Thus, a message with empty body should have a Content-Length header with value 0, and a message with no body should have no Content-Length header.
Semantically I think there is also a difference. Imagine a (badly designed) message service that allows you to post chat messages by putting your message in the body of a POST request. A POST request with empty body (Content-Length 0) should post an empty message, but a POST request with no body is not semantically valid in this context and should be ignored (by the server).

Regardless of the answer to the question, I think this API throwing error on no body is a bug. Consider the options:

If there is a meaningful difference, the API should allow me to POST with "" and null because they are different.
If there is no meaningful difference, then the API is wrong to allow one and disallow the other, because they are the same.

Is this a feature request to support hypothetical badly designed APIs that have different behavior for null vs. empty?
Do browsers support this distinction? Does HTTP/2?

I think that because absent vs. empty is ambiguous in HTTP/2 we shouldn't offer a mechanism to make them different in OkHttp.

A request or response that includes a payload body can include a content-length header field. A request or response is also malformed if the value of a content-length header field does not equal the sum of the DATA frame payload lengths that form the body.

https://httpwg.org/specs/rfc7540.html#malformed

Yeah also the HTTP/1 docs don't suggest a difference between absent and empty for methods that enclose a body.
   A user agent SHOULD send a Content-Length in a request message when
   no Transfer-Encoding is sent and the request method defines a meaning
   for an enclosed payload body.  For example, a Content-Length header
   field is normally sent in a POST request even when the value is 0
   (indicating an empty payload body).  A user agent SHOULD NOT send a
   Content-Length header field when the request message does not contain
   a payload body and the method semantics do not anticipate such a
   body.

The feature request is not to support hypothetical badly designed APIs. It was just a hypothetical example that you could use as an argument to claim they are different. I don't have a position in this, if you want to interpret these two requests as different or the same, that's up to you, as the spec is indeed ambiguous about this.
If you think making an HTTP request with no body and one with an empty body is the same, then my point is that it's odd that your library specifically forbids one but allows the other. For example, browsers accept both emptystring and undefined body, and will send an HTTP POST with Content-Length 0 over the wire in both cases, which is a strong argument to interpret these two as the same.
Aside from how you feel about ambiguity in the HTTP spec, the core issue I have is that this type of request is working in every other HTTP client that we use, except for this library, so we need to write workarounds just for this library because it has different behaviour.

We insist on an non-null body for HTTP methods like POST where a possibly-empty HTTP body must always be sent to comply with the spec.
We insist on a null body for HTTP methods like GET where no HTTP body may be sent to comply with the spec.
My model of it is:

If there's a body there's a content-length header (or transfer-encoding for streaming bodies!)
If there's no body there's no content-length header (and no transfer-encoding header either)

In particular HTTP GET is different here because it doesn't permit any body, not even an empty body. So there is a distinction. It's just that GET never has a body and POST always has one.
We could unambiguously convert null request bodies to empty request bodies for POST requests. We don't do that because it's simple for you to create an empty body instead.
JavaScript famously converts arbitrary values between types as a user convenience. The typical user response is not delight but WAT. We shy away from such conveniences in this library.

Looking back at decisions we've made in this category.  We have often taken positions in grey areas to focus on either a) following important industry standards (where features are implemented by browsers and actively used that way), or b) encouraging good practices, making it hard to make accidental bad requests (meticulous, opinionated, ergonomic, ...).
But also we've avoided changing existing behaviour often when there is a reasonable workaround. Even if it isn't pretty but keeps the standard cases cleaner. I think that also applies in this case.

To put some perspective on how this issue can impact users; we had a production incident impacting one of our services on our Android platform, because this library throws on some inputs. My team works on platform infrastructure that is responsible for forwarding and handling all HTTP traffic created by product/application teams, and we don't know what kinds of requests are created by our teams, we just have to forward them using the appropriate methods. One such team had a service that has been running without issues on our web platform for years, and recently enabled this service on our mobile Android and iOS platforms, which caused failures specifically on Android because we use this library as our general purpose HTTP client on our Android platform.
I agree that their HTTP request structure is questionable, but consider this from the product team's perspective. Their request scheme has been working for several years across many different browsers/ HTTP clients, and HTTP/proxy/application server backends. Without having an engineer on their team who is familiar with all details of the HTTP spec, I think it is reasonable that they reach the conclusion that their implementation is valid.
I can name off the top of my head over 10 HTTP client/server implementations that allow undefined/no body in POST requests:

XMLHTTPRequest API (IE11, Edge Legacy, Chromium, Firefox, Safari, probably every other browser)
Fetch API (Chromium, Firefox, Safari, Deno, fetch polyfill from whatwg)
Nginx
Apache

I don't know a of a single one that will throw or fail on such requests.
As you mentioned yourself in earlier posts, you like to be aligned with other HTTP client implementations. Given this, I still consider the current behaviour of this library a bug. At least from our perspective, if we cannot trust the httpok implementation to be aligned with other HTTP clients and it can randomly refuse to send certain HTTP requests because you consider the request to be invalid according to your interpretation of the spec, it is not usable for us as a general purpose HTTP client.

I appreciate your frustration. I'm doing my best to make OkHttp predicable and don't want to be unreasonable.
But I'm also confused. What happened that caused your Android app to send a POST request with a null body? Our typical users might encounter that NullPointerException in development, then switch to an empty request body instead.

Our developers build "application" logic for the web platform. Our Android applications use webviews to wrap existing applications, and intercept/forward all HTTP requests through our Android security library for authentication purposes.
The Android app is trying to send a POST request with a null body because it intercepted such a request from a web application in a webview and is trying to forward it. The web application in question has been running in production on other platforms for years, and the original developers never encountered any exceptions back when it was in development. The exception is only happening now that their application/functionality is exposed in one of our Android applications.
The team that handles the Android request interception/forwarding must rely on an HTTP library to forward any request that we intercept from existing web applications.

Thanks for the context, that helps!


Updated host in endpoint URL

The old host is always giving timeouts. The new one is also used at their website.

Hm, new URL does not work for me at all...

It takes very long for the data to load.


Test accelerate

https://travis-ci.org/reasonerjt/harbor/builds/209231170
it takes 8min25sec :)

Coverage remained the same at 54.319% when pulling da05c899c87ef861576f029e981aa96a9f2b591b on reasonerjt:test-accelerate into 46e953fd5ed69ad1d726efe3adfa206b7e046387 on vmware:dev.

Coverage decreased (-0.05%) to 54.272% when pulling da05c899c87ef861576f029e981aa96a9f2b591b on reasonerjt:test-accelerate into 46e953fd5ed69ad1d726efe3adfa206b7e046387 on vmware:dev.


[#noissue] Hide sidebar on no agent

Codecov Report

Merging #6308 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6308      +/-   ##
==========================================
- Coverage   39.59%   39.59%   -0.01%
==========================================
  Files        3065     3065
  Lines       91397    91397
  Branches    11836    11836
==========================================
- Hits        36189    36188       -1
- Misses      52223    52224       +1
  Partials     2985     2985

Impacted Files
Coverage Δ

...vercorp/pinpoint/rpc/packet/ClientClosePacket.java
55.55% <0%> (-11.12%)
:arrow_down:

...p/pinpoint/rpc/stream/StreamChannelRepository.java
75% <0%> (-10%)
:arrow_down:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
66.66% <0%> (-6.67%)
:arrow_down:

...navercorp/pinpoint/rpc/common/SocketStateCode.java
82.92% <0%> (-2.44%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
79.22% <0%> (-1.06%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
72.4% <0%> (+1.62%)
:arrow_up:

...java/com/navercorp/pinpoint/rpc/DefaultFuture.java
74.16% <0%> (+1.66%)
:arrow_up:

...om/navercorp/pinpoint/rpc/codec/PacketDecoder.java
59.57% <0%> (+2.12%)
:arrow_up:

...tor/metric/datasource/DefaultDataSourceMetric.java
78.12% <0%> (+3.12%)
:arrow_up:

...pc/server/LoggingServerMessageListenerFactory.java
100% <0%> (+10%)
:arrow_up:

Continue to review full report at Codecov.

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


[VL] Complex type does not release memory util shuffle writer destructor

Backend
VL (Velox)
Bug description
In a test case, we encountered a memory issue  that executor was killed by yarn due to running out of physical memory, instead of  throwing "offheap not enough" exception. It means that some memory is not monitored by Spark, and the actual physical memory overrun and killed by yarn.
Spark version
None
Spark configurations
No response
System information
No response
Relevant logs
No response

jemalloc profile attached:


Hue version on docker image

What version of Hue is on docker image (gethue/hue:latest from docker hub) ? Is it 3.9 ?
Thanks!

It pulls directly from the github, so the very latest on master

Thanks!

Hi,
Hue image is reported as pushed 5 months ago ; so I don't think it pulls directly from github and it does not seem to be an automated build too.
I tried to build it from scratch and it fails when compiling some botoo dependencies. Trying to build a 3.9 release instead of master in the meantime as it worked some months ago.
Nicolas

The plan is to re-update this one in 1 month when Hue 3.10 is out! @enricoberti


Fix clx images

Since there are a lot of automatically generated changes in this PR, it's probably easiest to review by commit.
This PR includes the following changes:

Removes the clx symlink and ci folder from core images since the core images don't have clx installed and the ci directory is not relevant to our images. This change prevents these folders from showing up in the JupyterLab directory in the browser.
Removes WORKDIR step from clx images so that they start in the same directory as the core images
Updates clx images to use existing partial for conda clean commands
Adds a step to the clx images to re-symlink the clx repo in the notebooks directory which was removed in the core images.
Inlines and deletes the clone_and_build_clx partial since it's only used in one spot.

The generated_files GH check is expected to fail on this PR.

I will test these changes locally in the morning before merging.

Tested locally. Merging.


Using Image.asset in a package throws Unable to load asset

Steps to Reproduce
My company has several packages that include assets and we have widget tests
in those packages that test trees that include assets. While upgrading to 3.3.0, if
we include the package: parameter in Image.asset the tests will throw. If we
exclude the package name, the image will not load in an app (expected) but the
tests pass. This is new behavior with 3.3.0. Tests pass and our apps run as
expected under 3.0.5.

Run an app and execute tests on the code sample

Expected results:
Assets load in app code and under widget tests
Actual results:
Assets load in one or the other... not both

Code sample

(full example project)
/// example widget tree in package
class PngTest extends StatelessWidget {
  const PngTest({super.key});

  @override
  Widget build(BuildContext context) {
    return Column(children: [
      /// Works when running the app
      /// Doesn't work under test
      Image.asset(
        'assets/pngs/ethernet_connected.png',
        package: 'png_test',
      ),

      /// Doesn't work when running in an app
      /// Work under test
      Image.asset(
        'assets/pngs/ethernet_disconnected.png',
        // package: 'png_test',
      ),
    ]);
  }
}

/// example widget test in package
void main() {
  testWidgets('Image.asset', (tester) async {
    TestWidgetsFlutterBinding.ensureInitialized();

    tester.pumpWidget(
      const MaterialApp(home: PngTest()),
    );
  });
}

/// example app usage
void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatelessWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: const [PngTest()],
        ),
      ),
    );
  }
}

# pubspec.yaml of package
name: png_test
description: A new Flutter package project.
version: 0.0.1
publish_to: none

environment:
  sdk: ">=2.18.0 <3.0.0"
  flutter: ">=3.3.0"

dependencies:
  flutter:
    sdk: flutter

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_lints: ^2.0.0

flutter:
  assets:
    - assets/pngs/

Logs

# flutter test in package

00:00 +0: loading /Users/nicholasspencer/Development/png_test/test/png_test_test.dart
00:01 +0: loading /Users/nicholasspencer/Development/png_test/test/png_test_test.dart
00:02 +0: loading /Users/nicholasspencer/Development/png_test/test/png_test_test.dart
00:02 +0: Image.asset
00:02 +0: Image.asset
══╡ EXCEPTION CAUGHT BY IMAGE RESOURCE SERVICE ╞════════════════════════════════════════════════════
The following assertion was thrown resolving an image codec:
Unable to load asset: packages/png_test/assets/pngs/ethernet_connected.png.

When the exception was thrown, this was the stack:
#0      PlatformAssetBundle.loadBuffer (package:flutter/src/services/asset_bundle.dart:272:7)
#1      AssetBundleImageProvider._loadAsync (package:flutter/src/painting/image_provider.dart:731:35)
#2      AssetBundleImageProvider.loadBuffer (package:flutter/src/painting/image_provider.dart:695:14)
#3      ImageProvider.resolveStreamForKey.<anonymous closure> (package:flutter/src/painting/image_provider.dart:513:13)
#4      ImageCache.putIfAbsent (package:flutter/src/painting/image_cache.dart:384:22)
#5      ImageProvider.resolveStreamForKey (package:flutter/src/painting/image_provider.dart:511:81)
#6      ScrollAwareImageProvider.resolveStreamForKey (package:flutter/src/widgets/scroll_aware_image_provider.dart:106:19)
#7      ImageProvider.resolve.<anonymous closure> (package:flutter/src/painting/image_provider.dart:358:9)
#8      ImageProvider._createErrorHandlerAndKey.<anonymous closure> (package:flutter/src/painting/image_provider.dart:473:24)
<asynchronous suspension>
(elided 5 frames from dart:async and package:stack_trace)

Image provider: AssetImage(bundle: null, name:
  "packages/png_test/assets/pngs/ethernet_connected.png")
Image key: AssetBundleImageKey(bundle: PlatformAssetBundle#013b2(), name:
  "packages/png_test/assets/pngs/ethernet_connected.png", scale: 1.0)
════════════════════════════════════════════════════════════════════════════════════════════════════

00:02 +0 -1: Image.asset [E]
  Test failed. See exception logs above.
  The test description was: Image.asset

To run this test again: /Users/nicholasspencer/fvm/versions/stable/bin/cache/dart-sdk/bin/dart test /Users/nicholasspencer/Development/png_test/test/png_test_test.dart -p vm --plain-name 'Image.asset'

00:02 +0 -1: Some tests failed.

# flutter run -v in app
[   +1 ms] Syncing files to device iPhone 13 Pro Max... (completed in 98ms)
[        ] Synced 0.0MB.
[   +1 ms] <- accept
[   +3 ms] Connected to _flutterView/0x7ff5b6014620.
[   +4 ms] Flutter run key commands.
[   +2 ms] r Hot reload. 🔥🔥🔥
[        ] R Hot restart.
[        ] h List all available interactive commands.
[        ] d Detach (terminate "flutter run" but leave application running).
[        ] c Clear the screen
[        ] q Quit (terminate the application on the device).
[        ] 💪 Running with sound null safety 💪
[        ] An Observatory debugger and profiler on iPhone 13 Pro Max is available at: http://<IP_ADDRESS>:49882/dT0CepEf17w=/
[ +104 ms]
           ══╡ EXCEPTION CAUGHT BY IMAGE RESOURCE SERVICE ╞════════════════════════════════════════════════════
           The following assertion was thrown resolving an image codec:
           Unable to load asset: assets/pngs/ethernet_disconnected.png.

           When the exception was thrown, this was the stack:
           #0      PlatformAssetBundle.loadBuffer (package:flutter/src/services/asset_bundle.dart:272:7)
           #1      AssetBundleImageProvider._loadAsync (package:flutter/src/painting/image_provider.dart:731:35)
           #2      AssetBundleImageProvider.loadBuffer (package:flutter/src/painting/image_provider.dart:695:14)
           #3      ImageProvider.resolveStreamForKey.<anonymous closure> (package:flutter/src/painting/image_provider.dart:513:13)
           #4      ImageCache.putIfAbsent (package:flutter/src/painting/image_cache.dart:384:22)
           #5      ImageProvider.resolveStreamForKey (package:flutter/src/painting/image_provider.dart:511:81)
           #6      ScrollAwareImageProvider.resolveStreamForKey (package:flutter/src/widgets/scroll_aware_image_provider.dart:106:19)
           #7      ImageProvider.resolve.<anonymous closure> (package:flutter/src/painting/image_provider.dart:358:9)
           #8      ImageProvider._createErrorHandlerAndKey.<anonymous closure> (package:flutter/src/painting/image_provider.dart:473:24)
           <asynchronous suspension>

           Image provider: AssetImage(bundle: null, name: "assets/pngs/ethernet_disconnected.png")
           Image key: AssetBundleImageKey(bundle: PlatformAssetBundle#fd9c7(), name:
             "assets/pngs/ethernet_disconnected.png", scale: 1.0)
           ════════════════════════════════════════════════════════════════════════════════════════════════════
[ +246 ms] The Flutter DevTools debugger and profiler on iPhone 13 Pro Max is available at: http://<IP_ADDRESS>:9101?uri=http://<IP_ADDRESS>:49882/dT0CepEf17w=/
[+134838 ms] Application finished.

Analyzing example...
No issues found! (ran in 2.9s)

[✓] Flutter (Channel stable, 3.3.0, on macOS 12.5 21G72 darwin-x64, locale en-US)
    • Flutter version 3.3.0 on channel stable at /Users/nicholasspencer/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ffccd96b62 (2 days ago), 2022-08-29 17:28:57 -0700
    • Engine revision 5e9e0e0aa8
    • Dart version 2.18.0
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc1)
    • Android SDK at /Users/nicholasspencer/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0-rc1
    • ANDROID_SDK_ROOT = /Users/nicholasspencer/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13F100
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] VS Code (version 1.70.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.46.0

[✓] Connected device (3 available)
    • iPhone 13 Pro Max (mobile) • 7C156174-5C99-408B-8899-FD1F8C627ABC • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-5 (simulator)
    • macOS (desktop)            • macos                                • darwin-x64     • macOS 12.5 21G72 darwin-x64
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 104.0.5112.101

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

I'm also encountering this issue in my UI tests.
Flutter 3.3.0 -> UI tests fails (unable to load asset).
Downgrade to 3.0.5 -> Everything runs fine.

Hello @nicholasspencer. This is occurring because you are running the app from an example app (therefore you need the package param) and the test from the package (therefore you don't need it). If you move the test from test/png_test_test.dart to example/test/png_test_test.dart and run flutter test from the example folder, you will see the same result as running the app.
I am closing this issue as everything is working as expected. Thank you.

What's the reason for this change in 3.3.0? Tests for a package should be in the package repository, not the app using it. This breaks tests that are in the package itself.

Hello @nicholasspencer. This is occurring because you are running the app from an example app (therefore you need the package param) and the test from the package (therefore you don't need it). If you move the test from test/png_test_test.dart to example/test/png_test_test.dart and run flutter test from the example folder, you will see the same result as running the app.
I am closing this issue as everything is working as expected. Thank you.

@exaby73 Thanks for the reply. Unfortunately I think there is a misunderstanding...
The tests are supposed to be in the package. We are testing widgets that are exposed from the package. My company has several apps that depend on core packages that reuse widgets and assets. These widgets in these core packages are tested. Hence, this is a bug.

@nicholasspencer
@exaby73 will probably reopen this, add the regression label and ask for team insights when he will be online. Thank you for your patience.

Hi @exaby73 - Multiple customers (myself included) are reporting this as a regression as it was working 3.0.5, and is not working in 3.3.
This is either an unintentional regression in 3.3, or an intentional breaking change. It seems to me that this is an unintentional regression. If this was an intentional breaking change, can you explain why support for loading assets within widgets tests from a package was dropped in 3.3?

@Jordan-Nelson @nicholasspencer @remcoanker I'll reopen this issue as I misunderstood it. Tested on previous versions, and I see the regression you are describing. Labelling for more insights from the team

cc @eliasyishak & @andrewkolos

cc @jonahwilliams

So this was likely cause by a change I made that replaced the bespoke unit test asset loader with the same asset loader used by the framework. As a result, this broke the behavior that package/<current-package>/<asset-name> would load assets and instead the same strategy used by the code under lib would need to be used instead.
Its unclear to me if this is actually desirable behavior, or if instead package/<current-package>/<asset-name> should work regardless of whether or not you are running the app or running the unit test. The divergence of behavior seems like it has the potential to be confusing.
@nicholasspencer what is the fix you'd like to see here. Do you actually want the old behavior / are you able to update to the new behavior?

Do you actually want the old behavior / are you able to update to the new behavior?

@jonahwilliams What would updating to the new behavior look like? I want to say that the old behavior made sense based on API documentation and the Assets and images documentation.
With the current API for AssetImage and Image.asset, I would assume that if the package parameter is not null, any kind of "<current-package>" logic would be disregarded and the package name would be explicitly used. I should note that this appears to not be affecting the loading other types of assets.
If we were to try and use this new behavior, would we have to introduce a DefaultAssetBundle in our package's tests that resolve differently? I guess I'm kind of stumped on this. Or maybe it's as easy as fully realizing the asset path in the key parameter instead of using the package parameter (🤔 I should try that.) My specific situation, and I assume others, is that we have shared image assets in packages. Some of these assets as loaded by trees internally, some are just Image.asset wrappers so that we can constantly defined the images and avoid strings all over the place. These widgets explicitly set the package name in Image.asset because, although the assets and code exist in the package together, the widget is expected to be used (and the asset loaded) in code that depends on the package. I would expect package tests to test packages as if they're being used by something that depends on it.

Any ETA on this? This issue keeps me on 3.0.5.
If a fix is not in the near future, what are some work arounds I can do? I've tried quite a few things to be able to load image assets during UI tests, but it still fails

@jonahwilliams What is a workaround for this bug? When will it be fixed or documentated?

The tests are supposed to be in the package. We are testing widgets that are exposed from the package. My company has several apps that depend on core packages that reuse widgets and assets. These widgets in these core packages are tested. Hence, this is a bug.

We experience the same problem here. We have a core package to reuse widgets in multiple projects.

I'm also encountering this issue in my UI tests. Flutter 3.3.0 -> UI tests fails (unable to load asset). Downgrade to 3.0.5 -> Everything runs fine.

As mentioned here, we have the same problem keeping us in Version 3.0.5.

@nicholasspencer what is the fix you'd like to see here. Do you actually want the old behavior / are you able to update to the new behavior?

I would definitely expect that the framework should find the given asset as it worked before. Especially if the package is given while loading the asset.

@jonahwilliams What is the workaround for this?

Deduplicating into https://github.com/flutter/flutter/issues/111285
In general the workaround would be to load assets in tests the same way you load them in the applicaiton. This seems too breaking for now so I'll put together a cherry pick

@jonahwilliams - is this being tracked in #111285 now? I wasn't sure from the previous comment if that is what you meant.
I might suggest keeping this one open over #111285 as it has been open longer and has more people following it.

Pretty sure this is the issue I had one of my packages as well. Saw it in beta 3.3.x before 3.3.0 stable release. It worked OK in 3.0.5, but failed on beta 3.3, did not have time to figure out why so I temporarily disabled the test until I could get back to it. Have not done so yet, but seems like now is a good idea to do so and see if this fixes it.

@jonahwilliams - is this being tracked in #111285 now? I wasn't sure from the previous comment if that is what you meant.
I might suggest keeping this one open over #111285 as it has been open longer and has more people following it.

right, wouldn't the other one be a duplicate? :suspect:

@jonahwilliams Thans for the information and the work!
Is my assumption correct that the cherry pick will be available in the next hotfix / fix version?

Works now in v3.3.2


'undefined reference to symbol' error during linking RSMI on linux

Hi! I'm having trouble linking the repo on my linux environment. I'm getting the following error:
/usr/bin/ld: Exp.o: undefined reference to symbol '_ZTTN5torch2nn10LinearImplE'
/usr/bin/ld: //storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/lib/libtorch_cpu.so: error adding symbols: DSO missing from command line

I am working on Debian 4.19.194 with the most recent LibTorch (CPU) ver. 1.10.0 - I tried both Pre-cxx11 ABI and cxx11 ABI variants (both producing the same error), gcc version 8.3.0 and boost version 1.60.
I followed the instructions in README, replacing the libtoch path with my own, without changing anything else.
I also tried older libtorch versions, the linking error can be traced back to 1.5.0, in which case the missing reference symbol is '_ZTVN5torch5optim11AdamOptionsE'. Versions <1.5.0 fail even earlier in the compilation.
The entire compilation output:
(BUSTER)tslaninakova@skirit:/storage/brno6/home/tslaninakova/playground/RSMI$ make -f Makefile
g++ -O3 -std=c++14 -o Exp.o -c Exp.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o utils/FileReader.o -c utils/FileReader.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o utils/ExpRecorder.o -c utils/ExpRecorder.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o utils/Constants.o -c utils/Constants.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o utils/FileWriter.o -c utils/FileWriter.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o entities/Mbr.o -c entities/Mbr.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o entities/NonLeafNode.o -c entities/NonLeafNode.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o entities/LeafNode.o -c entities/LeafNode.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o entities/NodeExtend.o -c entities/NodeExtend.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o entities/Point.o -c entities/Point.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o entities/Node.o -c entities/Node.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o curves/hilbert.o -c curves/hilbert.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o curves/z.o -c curves/z.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o curves/hilbert4.o -c curves/hilbert4.cpp -g -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include
g++ -O3 -std=c++14 -o Exp Exp.o utils/FileReader.o utils/ExpRecorder.o utils/Constants.o utils/FileWriter.o entities/Mbr.o entities/NonLeafNode.o entities/LeafNode.o entities/NodeExtend.o entities/Point.o entities/Node.o curves/hilbert.o curves/z.o curves/hilbert4.o -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include -I/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/include/torch/csrc/api/include -L/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/lib -ltorch -lc10 -lpthread -Wl,-rpath=/storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/lib
/usr/bin/ld: Exp.o: undefined reference to symbol '_ZTTN5torch2nn10LinearImplE'
/usr/bin/ld: //storage/brno6/home/tslaninakova/playground/RSMI/libtorch-abi/lib/libtorch_cpu.so: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make: *** [Makefile:35: Exp] Error 1

Any suggestions are greatly appreciated.

The problem disappeared once I put the ltorch_cpu flag in the Makefile, so:
#for linux
...
LIB +=-L/opt/libtorch/lib -ltorch -ltorch_cpu -lc10 -lpthread

similar problem and also fixed by the same way


Hsearch 2581

Duplicate of #1343 : just want to have Jenkins test with a slightly different configuration.

Closing, since I added your commit to #1343


400 Client Error: Missing Object ID

Describe the bug
Following Microsoft/PowerPlatformConnectors/AzureKeyVault Recipe
Created new AppRegistration as per step-by-step guide in docs.microsoft.com referenced on the github article, added the permissions
Downloaded the two JSON files, the api definitions and the api properties, modified the data inside to match the clicks I made on my side.
As per the recipe I run this command to create:
paconn create --api-def apiDefinition.swagger.json --api-prop apiProperties.json --secret "Foo********Bar"
and I get this error.
Please select an environment:
[1] Default Environment
Environment selected: Default Environment
{
"error": {
"code": "MissingObjectId",
"message": "The provided object identifier was null or missing."
}
}
400 Client Error: Bad Request for url: https://api.powerapps.com/providers/Microsoft.PowerApps/objectIds/validateApiSwagger?api-version=2016-11-01
The same error happens when I try and validate with the command below
paconn validate --api-def apiDefinition.swagger.json
Line 3 of teh apidefinition.swagger.json file looked suspicious considering i'm getting an object message.
{
  "basePath": "/",
  "consumes": [],

&& to triple check I pasted the file in an online json formatter and it confirmed it was a valid format.. so it's not a typo...
I read over the docs to make sure I didn't miss a click in portal.azure; and my user eyes say followed each step and started over a few times.
Frustrating to be hung up on the equivalent to Hello World -> your help and time is greatly appreciated!!!!
Cheers,
~C

Sounds like you don't have access to the default environment for connector creation. Please try another environment or let us know if you do have access to the environment. You can specify the environment with -e [GUID] in the command line as well.

Response was provided. In the future, please submit connector development questions to the forum: https://powerusers.microsoft.com/t5/Connector-Development/bd-p/ConnectorDevelopment


Issues with latest patch

Since LoLEnhancementSuite has moved to a different version detection schema (it retrieves versions it's compatible with from the internet), there is the possibility that it may have some compatibility issues that have turned up. I do my best to check for any issues but if any extra issues are created with the current League of Legends patch then please report them in this issue (instead of creating a new issue).
Current known issues with the latest League of Legends patch:

Join Multiple Queues is currently broken and needs to be re-implemented for each patch. This modification has not been updated since 5.11

Thanks,
Snowl.

I'll eventually fix join multiple queues when I have the time. The current implementation is hard to work with, so it probably needs to be reworked.


(Api/ClientCtrl) Build method: Launch prod script if body.prod

POST materia/client/build: Allow running client production script by passing { prod: true } as request body

For the moment it run prod script : if {prod: true} is passed in request body and client.scripts.prod exists. Don't you think it is better to return an error if build or prod script doesn't exists ?


Protein-Prep: Support prep direct from RCSB

Running our protein-prep CLI on a supported target but using a PDB structure file directly from RCSB results in a failure see the following example:
wget https://files.rcsb.org/download/5SQ1.pdb
asap-prep --target "SARS-CoV-2-Mac1"  --pdb-file 5SQ1.pdb --output-dir mac1

DPI: 0.02, RFree: 0.17, Resolution: 1.05
Processing BU # 1 with title: NON-STRUCTURAL PROTEIN 3_, chains A
Found unresolved N-terminal with 2 residues before VAL 3   A 0  , with sequence SM
Warning: There was a problem building some missing pieces, built as much as was possible
Processing BU # 2 with title: NON-STRUCTURAL PROTEIN 3_, chains B
Warning: No ligand or sites detected, please revise inputs and/or options

In this case the prep workflow can not find the ligand, however changing the residue name to LIG fixes the issue.
cc @hmacdope  @JenkeScheen

solution would be to expose a flag to pass the ligand entry in the PDB file. Annoying that OE doesn't catch the ligand automatically.


UNINITIALIZED_VALUE - false positive C

In the following minimal example, the var variable is initialized into a while(true), however, Infer reports an UNINITIALIZED_VALUE. I checked this case with if (true), for ( ; ; ) and while(1) and Infer returns the same error.
int main(){
	int var;
	while(true){
		var = 0;
		if(var==0) break;
	}
	printf("Var:%d\n",var);
	return 0;
}

This is the Infer's report:
Found 1 issue

while_true.c:12: error: UNINITIALIZED_VALUE
  The value read from var was never initialized.
  10.   		if(var==0) break;
  11.   	}
  12. > 	printf("Var:%d\n",var);
  13.   	return 0;
  14.   }

Summary of the reports

  UNINITIALIZED_VALUE: 1

You're right, this checker doesn't track the value of the loop condition so doesn't realise it's always true. Would it be an option to hoist var = 0 out of the loop ?

Thanks for the suggestion, yes in that case Infer would not report an error.
This problem was encountered during the analysis of the SQLite code, Infer reports this false positive in several situations, on the other hand the Clang Static Analyzer realizes that the condition of the loop is always true and therefore does not report any error.


HSEARCH-3752 Implicit nested predicates

https://hibernate.atlassian.net/browse/HSEARCH-3752
Preview: only match predicate and ElasticSearch backend are done.
If you don't want to have an early look, please ignore this pull request until it isn't a preview anymore.
now is ready for review

Thank you @yrodiere.
Comments addressed.
Is there anything else I can do here?

I ran a built for all support environments: https://ci.hibernate.org/job/hibernate-search/view/change-requests/job/PR-2229/10/

@yrodiere I think I've done the changes.
I spent some time adding some extra test for complex cases.
If there is something else to improve, I'll be happy to do that.

Started a full build: https://ci.hibernate.org/job/hibernate-search/view/change-requests/job/PR-2229/12/

Done. Let's wait for the CI than I'll merge it. Thanks @yrodiere


added more communities and OSS project

Added 4 more Communities' names with their respective discord link to the list.

Added an OSS project to the list and arranged them all in alphabetical order.

closes #146

@chirag0002 can you please also resolve the merge conflict
__
  Summary: :hammer_and_wrench: This code needs a fix

Ohk, looking for it.

Resolved the conflict errors, and removed extra lines. You can review it again @kaiwalyakoparkar.
__
  Summary: :hammer_and_wrench: This code needs a fix

Very glad to know that my PR got merged...Thank You :)


Resolve gcc compiler warnings

What
Add some constructors more explicitly and initialize memory of some unions.
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested demo.rerun.io (if applicable)
[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

I guess touching uninitialized memory - even writing to it - is UB somehow

It boils down to the places that we implement some form of swap. Essentially we end up swapping initialized memory with uninitialized memory. Even though the recipient of the uninitialized memory is self consistent in a way that prevents it from touching that uninitialized memory, the checks in swap end up seeing it as a read and complaining.
I suspect if we were really worried about the initialization overhead we could use the union-variant to only swap the initialized portion of memory based on the union arm or something comparably gross.


Stop throwing some exceptions in JedisClusterCommand

In JedisClusterCommand, stop throwing custom exceptions when key is null or keys array is null or empty. This is not what is practised in other Jedis classes.

@HeartSaVioR @marcosnils

@smadasu by applying this change, this will cause a NullPointerException everytime you set a key to null from here: https://github.com/xetorthio/jedis/blob/master/src/main/java/redis/clients/jedis/util/JedisClusterHashTagUtil.java?utf8=✓#L27
In other Jedis classes ,we also check this at a different level:
https://github.com/xetorthio/jedis/blob/master/src/main/java/redis/clients/jedis/util/SafeEncoder.java?utf8=✓#L28
I think it's OK to leave it like this.

@marcosnils Please check #1774. It is opposite approach of this PR.

@sazzad16  @marcosnils  this PR is similar with #1774 which has more better implement. so can we close this one and keep #1774 as 3.0.0's milestone?  it is small improvement instead of key feature.
WDTY?

@jiafu1115 If you think the implementation of #1774 is good, you can LGTM that :)

@sazzad16 yes. this PR loss some implement which is in #1774 . so suggest close this PR and continue #1774 , BTW, can you help to review one tiny change PR #1814 , Thanks

Shall we close this in favor of #1774 ?


Project upgrade not triggered - azure-sdk-for-python project

Load azure.sln from https://github.com/azure/azure-sdk-for-python
On VS 2017 latest RC.
It prompts to install python support.

I deleted the solution file and tried to just load azure.pyproj, and that upgraded fine.


fix: add v-bind="$attrs" to DatePicker in Calendar

Adding v-bind="$attrs" to DatePicker allows fine-grained control over the underlying v-calendar component's API.

Attribute Inheritance is true by default
With your change attributes will apply to these two lines 👇  instead of only <DatePicker> component

https://github.com/olemarius/shadcn-vue/blob/calendar-attrs/apps/www/src/lib/registry/default/ui/calendar/Calendar.vue#L55
https://github.com/olemarius/shadcn-vue/blob/calendar-attrs/apps/www/src/lib/registry/default/ui/calendar/Calendar.vue#L65

IMO, let's wait for Infer attrs (Vue 3.4) cause v-calendar does not provide any types to set it easily in the defineProps section

@sadeghbarati thanks for pointing that out! Also agree it's better to wait for Infer attrs, wasn't aware of that rfc.
So for now, the workaround is to modify your own local copy of the Calendar.vue component with
defineOptions({
  inheritAttrs: false
})

and
<DatePicker
  v-bind="$attrs"
  ...
/>


Input with type "button", "submit", "reset" and "search" should be styled like buttons

Only search needs to be implemented, the others are done.


Rabarber initialiser

Hi, I've started playing about with this gem and might be a silly question but what do we put here?
Rabarber.configure do |config|
...
  config.when_actions_missing = -> (missing_actions, context) { ... }
  config.when_roles_missing = -> (missing_roles, context) { ... }
  config.when_unauthorized = -> (controller) { ... }
end

Here is what I have:
 Rabarber.configure do |config|
  config.cache_enabled = true
  config.current_user_method = :current_user
  config.must_have_roles = false

  config.when_actions_missing = -> (missing_actions, context) do
    raise ActionController::RoutingError.new('Not Found')
  end

  config.when_roles_missing = -> (missing_roles, context) do
    redirect_to root_path, alert: 'You do not have sufficient permissions'
  end

  config.when_unauthorized = -> (controller) do
    redirect_to root_path, alert: 'You are not authorized to access this page'
  end
end

But I'm getting
undefined local variable or method `root_path' for main:Object

Any help here would be great.

Hi there,
I'd like to address a couple of points regarding the issue you raised:

As stated in our contributing guidelines, issues are meant for reporting bugs. If you have questions or need assistance with using the gem, we encourage you to use the Discussions section.
The README file provides comprehensive guidance on how to configure and use the gem. However, if you find any areas lacking clarity or have suggestions for improvements, we welcome your contributions through pull requests.
Regarding the error with the root_path method, there is no such method in the specific context of that lambda. Only the controller instance (controller argument) is available within the lambda, so you have to derive everything you need from it. You're also welcome to take a look the implementation of the default logic; you can find it here. Probably, it will help you understand what you can possibly have inside your lambdas.

I hope this clarifies the situation for you. I'm closing the issue as it is more suited for discussions.


Runs first password fails even when correct, then: Error: Message: Cannot Connect to the Service Geckodriver

Finally found a compatible configuration of dependencies for the script and got it to run. However, it only passes the first password in my list, and returns failed, regardless of whether its correct. Then, on the second run, the script returns "Error: Message: Can not connect to the Service geckodriver"
`Starting tor daemon...done.
[ ok ] Checking Account Existence

Bruteforce starting ( Delay = 1 sec ) -
Password: pa88w0rd    | Failed        | IP : b'<IP_ADDRESS>'

Error : Message: Can not connect to the Service geckodriver`
I have the localhost in /etc/hosts. I removed the following:
socks.setdefaultproxy(socks.PROXY_TYPE_SOCKS5, "<IP_ADDRESS>", 9050, True)                                                 socket.socket = socks.socksocket
This put me past the first password issue, even though it still failed the correct password, but ultimately blocked me out after 12 tries given that the proxy stopped rotating the IP. Anyone have a solution?

Got the script to run by replacing
socks.setdefaultproxy(socks.PROXY_TYPE_SOCKS5, "<IP_ADDRESS>", 9050, True) socket.socket = socks.socksocket
with
fp = webdriver.FirefoxProfile()                 fp.set_preference("network.proxy.socks","<IP_ADDRESS>")                 fp.set_preference("network.proxy.socks_port",int(9050))
Still not rotating IPs, however, and blocked me after 6 tries. First password, although correct, still failed as well.


Line comment highlights the rest of the code as a string when ' is used

You can reproduce the issue here: https://opensource.respawn.pro/FlowMVI/sample/ (Decompose integration item)
What's interesting, it seems that if the comment is not indented, then the bug does not occur. This started happening after the update from 0.8 to 0.9

Okay this looks serious, I think we will have this fixed in next versions

@Nek-12 I checked the fragment of yours code  inn the sample of 1.0.0 version.
Input
class PagesComponent(
        context: ComponentContext,
        container: () -> PagesContainer, // inject using DI or create
) : ComponentContext by context,
    PagesStore by context.retainedStore(factory = container) {

private val navigator = PagesNavigation<PageConfig>()

val pages = childPages(
    source = navigator,
    serializer = PageConfig.serializer,
    initialPages = { Pages(items = List(5) { PageConfig(it) }) },
    childFactory = ::PageComponent,
)

init {
// subscribe to the store following the component's lifecycle
subscribe {
    actions.collect { action ->
        when (action) {
            is SelectPage -> navigator.select(action.index)
        }
    }
}

Output
After analysis there has been found:
marks = ( ( ( ( ( ( ( ( ( ( ) ) ) ) ) ) ) ) ) ) - - - > > > > = = = = = = = = { { { { { { { < } } } } }
punctuations = : : : : : , , , , , , , . . . . .
keywords = class by by private val val when is
strings =
literals = 5
comments = // inject using DI or create  // subscribe to the store following the component's lifecycle
multilineComments =
annotations =
kotlin.Unit

Probably the problem belongs to KodeView so please recheck that

Interesting. We are using a fork of code view that processes the annotations async on a different thread, so I will try to fork it again from a more fresh commit to see if anything changes

This is what I see on the latest version. I tried updating the KodeView but that didn't help, however you can see the behavior is different now. I am pretty sure the problem is in the ' symbol which tells the library that a string has started.

Everything until the end of line should be considered a comment when // is used

@Nek-12 Thanks for precise reproduction. Indeed that was a small gap in logic. This should be fixed in published 0.9.3


Add giovp to feedstock maintainers

@giovp please take a look

also, v.1.1.0 didn't go through due to https://github.com/conda-forge/status/issues/181

:+1: @giovp @LucaMarconato added and rebased

Fantastic thank you!

Thanks @thewtex!

also, v.1.1.0 didn't go through due to conda-forge/status#181

I will ask the admin to rerun the bot for the recently closed PR.

Hi @thewtex, could you please merge this? Also, could @giovp and I be added as maintainer to https://github.com/conda-forge/multiscale-spatial-image-feedstock? Thanks!

I don't have merge permissions :-(

Ah! @goanpeca can you merge please?


Create Biopython slides

Having a stack of slides on Biopython would be useful.  Proposed subjects:

sequences: reading/writing, computing properties, slicing,...
sequence annotations
sequence alignment
phylogenetic trees
searching online databases

Done, commit #20767491645cd247a4b4753917c221c33b5294db added this.


EnlistTransaction does not exist in EF 2.0

https://github.com/aspnet/EntityFramework.Docs/blob/master/samples/core/Saving/Saving/Transactions/CommitableTransaction/Sample.cs#L37
context.Database.EnlistTransaction(transaction);

EnlistTransaction  was added in 2.1 https://github.com/aspnet/EntityFrameworkCore/issues/5595
So this stops the samples from compiling for me. any ideas why it doesnt break other people?

EF Core 2.0 and lower are out-of-support, so closing docs issues specific to these releases.

This wasnt about v2. It was about not being able to build the current version of docs

@SimonCropp My mistake. Duplicate of #1074

Cool. Thanks for the forward


Add sk-java-hello-world

Motivation and Context

Add basic Hello world for Java Semantic Kernel.
Description

Contribution Checklist

[ ] The code builds clean without any errors or warnings
[ ] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel-starters/blob/main/CONTRIBUTING.md)
[ ] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
[ ] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

@matthewbolanos could you have a look at this pr?


ConvertFrom-Json : Invalid JSON primitive: .

Modpack Version

Describe your issue.
I setup settings.ps1 matching my pack options.
I skip all parts except actual uploading on CF.
When i lunch modpack-uploader.ps1 i see this:

Seems like something wrong with CF output.
Error:
ConvertFrom-Json : Недопустимый примитив JSON: .
D:\mc_client\Instances\Enigmatica2Expert - Extended\modpackUploader\modpack-uploader.ps1:245 знак:30
+             --progress-bar | ConvertFrom-Json
+                              ~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [ConvertFrom-Json], ArgumentException
    + FullyQualifiedErrorId : System.ArgumentException,Microsoft.PowerShell.Commands.ConvertFromJsonCommand

Failed to upload client files:
Failed to upload client files:
D:\mc_client\Instances\Enigmatica2Expert - Extended\modpackUploader\modpack-uploader.ps1:252 знак:13
+             throw "Failed to upload client files: $response"
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Failed to upload client files: :String) [], RuntimeException
    + FullyQualifiedErrorId : Failed to upload client files:

I tried to redirect output of curl.exe in file:
- --progress-bar | ConvertFrom-Json
+ > out.html

Opening out.html i see this:

Why this happen? How to fix that?
Crash Report
No response
Latest Log
No response
Have you modified the modpack?
No
User Modifications
No response
Did the issue happen in singleplayer or on a server?
Both

Thanks for the report. Could you please provide your settings.ps1 file?

I am also getting the same error, API token is added. my setttings.ps1 is here: https://gist.github.com/MetaverseRPN/de37892b5eefcc4981cda3f229c58cfc

Any chance you have a the returned error in english? 😅

I do. Here it is:
Failed to upload client files: @{errorCode=1002; errorMessage=Error in field metadata: Invalid JSON.} Failed to upload client files: @{errorCode=1002; errorMessage=Error in field metadata`:
Invalid JSON.}
At C:\Users\nicho\curseforge\minecraft\Instances\Protocol Beta test\modpack-uploader.ps1:250 char:13

        throw "Failed to upload client files: $response"

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : OperationStopped: (Failed to uploa...
Invalid JSON.}:String) [], RuntimeException
FullyQualifiedErrorId : Failed to upload client files: @{errorCode=1002; errorMessage=Error in field metadata:

Invalid JSON.}`

Thank you kindly. Do you also have the output just prior to this? I'm looking for something like this:
Client Metadata:

{
            changelog: 'The Changelog is currently being written, it should be done soon.',
            changelogType: 'markdown',
            displayName: 'Enigmatica 6 1.2.1',
            gameVersions: [8203],
            releaseType: 'alpha'
        }

Client Metadata:

{
            changelog: 'You aren't supposed to be here... There is nothing for you to see here...',
            changelogType: 'markdown',
            displayName: 'PhoenixRising 0.0.1',
            gameVersions: [6756],
            releaseType: 'beta'
        }

Is this what you are looking for?

It is indeed. Odd, that looks perfectly valid.
I'm guessing they're finally patching the odd json format they used to expect. Could you perhaps re-try a couple of times, see if you reach one of their API servers that haven't updated yet? 😄 I was able to use this a few minutes ago.

Im trying for the 3rd time but it seems I am getting this error every time I try

Yes, i tried different time a day and same error.

Hmm alright. Could you please try replacing the setting of the $CLIENT_METADATA parameter like below?
Change this:
$CLIENT_METADATA =
        "{
            changelog: `'$CLIENT_CHANGELOG`',
            changelogType: `'$CLIENT_CHANGELOG_TYPE`',
            displayName: `'$CLIENT_FILE_DISPLAY_NAME`',
            gameVersions: [$GAME_VERSIONS],
            releaseType: `'$CLIENT_RELEASE_TYPE`'
        }"
        ```
to this:
```ps1
$CLIENT_METADATA = @{
    changelog     = $CLIENT_CHANGELOG
    changelogType = $CLIENT_CHANGELOG_TYPE
    displayName   = $CLIENT_FILE_DISPLAY_NAME
    gameVersions  = $GAME_VERSIONS
    releaseType   = $CLIENT_RELEASE_TYPE
} | ConvertTo-Json

Trying it now

um.... Ok this is a new one.....
curl: (6) Could not resolve host: aren\u0027t

curl: (6) Could not resolve host: supposed

curl: (6) Could not resolve host: to

curl: (6) Could not resolve host: be

curl: (6) Could not resolve host: here...

curl: (6) Could not resolve host: There

curl: (6) Could not resolve host: is

curl: (6) Could not resolve host: nothing

curl: (6) Could not resolve host: for

curl: (6) Could not resolve host: you

curl: (6) Could not resolve host: to

curl: (6) Could not resolve host: see

curl: (3) bad range specification in URL position 31:
here...,
    gameVersions:  [
                         6756
                     ],
    changelogType:  markdown,
    releaseType:  beta,
    displayName:  PhoenixRising

Yikes. CurseForge still dislikes normal JSON I guess :P
Please revert that change, and make this change instead:
Change:
-F metadata=$CLIENT_METADATA

to
-F metadata=([System.Text.Encoding]::UTF8.GetBytes($CLIENT_METADATA ))

Oh woops, I think it should've been [System.Text.Encoding]::UTF8.GetString
-F metadata=([System.Text.Encoding]::UTF8.GetString($CLIENT_METADATA))

The argument "bytes" cannot be converted, with the value: "{
            changelog: 'The Changelog is currently being written, please ignore.',
            changelogType: 'markdown',
            displayName: 'E2E-Extended v0.56.0',
            gameVersions: [6756],
            releaseType: 'beta'
        }", for "GetString" into type "System.Byte[]": "Cannot convert value "{
            changelog: 'The Changelog is currently being written, please ignore.',
            changelogType: 'markdown',
            displayName: 'E2E-Extended v0.56.0',
            gameVersions: [6756],
            releaseType: 'beta'
        }" в тип "System.Byte[]". Error: "Cannot convert value "{
            changelog: 'The Changelog is currently being written, please ignore.',
            changelogType: 'markdown',
            displayName: 'E2E-Extended v0.56.0',
            gameVersions: [6756],
            releaseType: 'beta'
        }" в тип "System.Byte". Ошибка: "The input string was in the wrong format."""
D:\mc_client\Instances\Enigmatica2Expert - Extended\modpackUploader\modpack-uploader.ps1:238 знак:9
+         $response = curl.exe `
+         ~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodException
    + FullyQualifiedErrorId : MethodArgumentConversionInvalidCastArgument

Failed to upload client files:
Failed to upload client files:
D:\mc_client\Instances\Enigmatica2Expert - Extended\modpackUploader\modpack-uploader.ps1:252 знак:13
+             throw "Failed to upload client files: $response"
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Failed to upload client files: :String) [], RuntimeException
    + FullyQualifiedErrorId : Failed to upload client files:

-F metadata=([System.Text.Encoding]::UTF8.GetBytes($CLIENT_METADATA ))

I tried this. After uploading progress bar, slowly got similar messages curl: (6) Could not resolve host: 32 again and again:
######################################################################## 100,0%

curl: (6) Could not resolve host: 123

curl: (6) Could not resolve host: 13

curl: (6) Could not resolve host: 10

curl: (6) Could not resolve host: 32

curl: (6) Could not resolve host: 32

curl: (6) Could not resolve host: 32

curl: (6) Could not resolve host: 32

curl: (6) Could not resolve host: 32

Did you try this fix as well? https://github.com/EnigmaticaModpacks/ModpackUploader/issues/16#issuecomment-1120272019

Did you try this fix as well? https://github.com/EnigmaticaModpacks/ModpackUploader/issues/16#issuecomment-1120272019

Yes, same error as in https://github.com/EnigmaticaModpacks/ModpackUploader/issues/16#issuecomment-1122761431

Damn, I'll think on it some more then, and try to reproduce it some more.

Client Metadata:

{
            changelog: 'You aren't supposed to be here... There is nothing for you to see here...',
            changelogType: 'markdown',
            displayName: 'PhoenixRising 0.0.1',
            gameVersions: [6756],
            releaseType: 'beta'
        }

Is this what you are looking for?

Actually, try removing the ' from aren't

removing the ' fixed it for me, but now I have a completely different issue I'm running into. The manifest that the modpackuploader.ps1 is generating is referencing two mods that are most certainly not in my pack, causing a invalid manifest error: https://cflookup.com/462460?fileId=3253803 https://cflookup.com/446346?fileId=3202390
I will open a new issue for that one as this is a completely different issue now


[Fix]: RHP is not scrollable if click on "Next" without filling ID in Custom Segments/record

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/50065
PROPOSAL: https://github.com/Expensify/App/issues/50065#issuecomment-2395011270
Tests

Open App
Log in with a new Gmail account
Click on FAB - New workspace
Enable "Accounting" in the "More features" page.
Navigate to "Accounting"
Connect to NetSuite and upgrade the workspace to Control when asked
Wait for the sync to finish
Navigate to Accounting - Import - Custom Segments/records
Click on the "Add custom segments/record
Choose segment or record and click on the "Next" button
Type in any custom record name and click on the "Next" button
Click on the "Next" button without filling the ID

Verify that: RHP is scrollable, "Next" button is visible

[x] Verify that no errors appear in the JS console

Offline tests

Cannot test offline
QA Steps

Same as tests

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/cc2e15a5-b08b-44cd-9920-3f69b198e332

Android: mWeb Chrome
https://github.com/user-attachments/assets/947b2e6b-9b61-4f49-8810-59e257b747b5

iOS: Native
https://github.com/user-attachments/assets/f08c555b-dccc-4c3d-bdfc-0b33afd47a0e

iOS: mWeb Safari
https://github.com/user-attachments/assets/83761d66-1af4-4280-9882-dd4c1e24224e

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/c335ef17-dce4-4ec0-80ef-05cea2bea3bd

MacOS: Desktop
https://github.com/user-attachments/assets/9f727143-938a-4ae1-95e0-b4730f242847

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Title: Tiers library

There doesn't seem to be a way to change the title on the view controller and "Tier library" is hard coded. Also, the text color and background colors are not exposed publicly. It would be nice to have control over these as properties on OpenSourceController.

Hello !
I just tried in another project to set "Tiers library" = "Blabla"; in my Localizable.string file and it work fine !
Did you override NSLocalizedString in your project ?
For the customization I'll make it asap, probably this afternoon for the next version, thank you !

Just pushed v1.0.5 on cocoapods.
See the https://github.com/terflogag/OpenSourceController#customisation section :-)

Wow! You are awesome! Thanks so much for sharing this in the first place, and also for so quickly adding the configuration features. Very nice!


In Dataset.to_zarr cannot specify to not write empty chunks when appending to existing store

What happened?
I'm trying to append to a very sparse zarr store. When initially creating (or overwriting) the store, I can specify {'write_empty_chunks': False} for the data variables in the dataset and it will avoid writing an excessive amount of empty chunks. When I try to append (mode='a', append_dim set), I cannot specify {'write_empty_chunks': False} and it uses the default value True and will write empty chunks.
Example from MCVE:
>>> ds.to_zarr('demo_append.zarr', encoding={'test': {'write_empty_chunks': False}})
<xarray.backends.zarr.ZarrStore object at 0x11cb1a6c0>
>>>
>>> import os
>>> os.system('ls demo_append.zarr/test')
0.1.0
0
>>>
>>> ds.to_zarr('demo_append.zarr', mode='a', append_dim='Z', encoding={'test': {'write_empty_chunks': False}})
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/rileykk/opt/anaconda3/envs/oco-test/lib/python3.11/site-packages/xarray/core/dataset.py", line 2236, in to_zarr
    return to_zarr(  # type: ignore[call-overload,misc]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rileykk/opt/anaconda3/envs/oco-test/lib/python3.11/site-packages/xarray/backends/api.py", line 1673, in to_zarr
    raise ValueError(
ValueError: variable 'test' already exists, but encoding was provided
>>> ds.to_zarr('demo_append.zarr', mode='a', append_dim='Z')
<xarray.backends.zarr.ZarrStore object at 0x11d53d0e0>
>>> os.system('ls demo_append.zarr/test')
0.1.0	1.0.0	1.0.1	1.1.0	1.1.1
0

What did you expect to happen?
I would expect the write_empty_chunks encodings to either be configurable or preserved when appending.
Minimal Complete Verifiable Example
import xarray as xr
import numpy as np
import os

d = np.array([np.nan, np.nan, 1.0, np.nan]).reshape((1, 2,2))
ds = xr.Dataset(data_vars={'test': (('Z', 'Y', 'X'), d)})

ds['test'] = ds['test'].chunk((1,1,1))

# 3 chunks in 'test' var fully empty so they should not be written
ds.to_zarr('demo_append.zarr', mode='w', encoding={'test': {'write_empty_chunks': False}})

# Verify only one chunk written
os.system('ls demo_append.zarr/test')

# Error here; cannot specify that we don't want to write empty chunks
ds.to_zarr('demo_append.zarr', mode='a', append_dim='Z', encoding={'test': {'write_empty_chunks': False}})

# Append without specifying encoding
ds.to_zarr('demo_append.zarr', mode='a', append_dim='Z')

# But now we have appended 4 new chunks (5 total) instead of just 1
os.system('ls demo_append.zarr/test')

# Show the chunk shape + that the appended data has 3 empty chunks
xr.open_zarr('demo_append.zarr')
xr.open_zarr('demo_append.zarr').test.to_numpy()

MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output
No response
Anything else we need to know?
No response
Environment

INSTALLED VERSIONS
commit: None
python: 3.11.4 | packaged by conda-forge | (main, Jun 10 2023, 18:10:28) [Clang 15.0.7 ]
python-bits: 64
OS: Darwin
OS-release: 22.5.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: ('en_US', 'UTF-8')
libhdf5: 1.14.0
libnetcdf: 4.9.2
xarray: 2023.7.0
pandas: 2.0.2
numpy: 1.25.1
scipy: 1.11.1
netCDF4: 1.6.4
pydap: None
h5netcdf: 1.2.0
h5py: 3.9.0
Nio: None
zarr: 2.15.0
cftime: 1.6.2
nc_time_axis: None
PseudoNetCDF: None
iris: None
bottleneck: 1.3.7
dask: 2023.4.0
distributed: 2023.4.0
matplotlib: 3.7.2
cartopy: None
seaborn: None
numbagg: None
fsspec: 0.8.3
cupy: None
pint: None
sparse: None
flox: None
numpy_groupies: None
setuptools: 67.7.2
pip: 23.1.2
conda: None
pytest: None
mypy: None
IPython: 8.12.0
sphinx: None

Looks like this will require zarr>=2.11 to have an effect; otherwise it will issue a warning of unrecognized kwarg on to_zarr. This seems to be what is causing the min_all_deps check to fail (+ the fact that the new test cases expect it to work when it shouldn't with that version of zarr). Is this something that would be better resolved by a check or bumping the minimum required zarr version?


Evict transactions based on transaction accounts by sender

Describe the feature
currently
https://github.com/paradigmxyz/reth/blob/849a47efb86e995ca4be22041581371f50156024/crates/transaction-pool/src/pool/txpool.rs#L587-L591
simply discards the worst transactions
instead, this should also take the number of transactions from unique senders so that spammers are more affected
Additional context
No response

@mattsse I'd like to look into this :)

I can take this.


"Iecea Mare" is listed in the drop-down menu

Description:
"Iecea Mare" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Iecea Mare" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Iecea Mare, TIMIȘ (Iecea Mare)" and "Comuna Iecea Mare, TIMIȘ".


Webhook text

Allow for predefined text to be sent with each webhook from config.ini
Requested by Kozzy#1340

Would inherently allow for the tagging of discord roles and users via discord developer ID, for example:
<@121343381069627392>
would tag me (Jartan#7450).

Would inherently allow for the tagging of discord roles and users via discord developer ID, for example:
<@121343381069627392>
would tag me (Jartan#7450).