Strip scheme from host parameter if provided when creating QdrantClient instance

Details are in #88
This just adds a helper function to the QdrantClient class that strips the scheme from the hostname prior to self assigning the attribute and generating the rest_uri.

Hi @nleroy917, thanks for the PR!
Would it be possible to try to avoid mixing of URL and Host concepts, as it could lead to misinterpretations?
For example, https://localhost parsed as URL should mean that we are intended to use 443 port and https protocol for communication. But code in the PR will discard this information without any warnings.
Would it be possible to make additional optional argument  url, which will be fully parsed into correct client configuration?

Sure. Do you mean sort of the paradigm that database connection libraries use? Where you can provide a connection string (postgres://user:password@localhost:5432) or the individual params (host=localhost, password=..., etc).

Sure. Do you mean sort of the paradigm that database connection libraries use? Where you can provide a connection string (postgres://user:password@localhost:5432) or the individual params (host=localhost, password=..., etc).

Exactly! We could have additional optional parameter url, it it is provided, we can parse it into schema, port and host

Do you intend this to be in init or in the new helper function on the class?

I think extending __init__ will be reasonable

I'll work on this in the coming days. In the meantime, wondering if this flow seems reasonable for establishing the connection:
graph LR
  A[<code>__init__</code>] --> B{<code> url == None? </code>}
  B -- No --> C[Parse url into host and port]
  B -- Yes --> D[use provided host and port]

I also saw #92 I don't know if it's reasonable to add that functionality. But the diagram could be updated to look more like:
graph LR
  A[__init__] --> B{env vars?}
  B -- Yes --> C[connect with env vars]
  B -- No --> D{<code> url == None ? </code>}
  D -- No --> E[Parse url into host and port]
  D -- Yes --> F[use provided host and port]

I'm personally opposed to initiating from env variables, but thats just my opinion 😅

I also don't think ENV should be parsed internally

Hi @nleroy917, we intercepted your PR a bit https://github.com/qdrant/qdrant_client/pull/99, hope it solves the issue for you!
Please feel free to suggest any other improvements.

@generall no worries! I was moving too slowly. I'll let you know if I run into other issues...


Insert then an undo then a redo does not correctly invoke tx.checkPermission

The following sequence of tx transactions does not work, if you use a custom tx.checkPermission that expects a non-null doc argument for an insert action:

Transaction that inserts a doc into a collection
tx.undo()
tx.redo()

The tx.redo() fails because the tx.checkPermission call fails.
I am about to upload a github repo that reproduces the problem

Here is the repo, please read the README for full details of my investigation and proposed fix:
https://github.com/rjsmith/meteor-transactions-bug-repo

Richard, thank you so much for the time you've put into chasing down this bug and finding a fix.  I really appreciate it.  You're quite right about the cause of the bug.
I'll certainly look into removing the Meteor.isClient from the onTransactionExpired call.  You make a good point about what happens when the tx.undo and tx.redo methods are called from the server.
I'm putting this on high priority and hope to get a new release out within 24 hours.

No problem  - thanks for creating this package.
re: undo & redo, maybe allow a standard - pattern function(err, res) callback to be passed as a 2nd parameter?

Yes, I'll see what I can do.  I really should have had this pattern in place from the beginning.

@rjsmith I can't thank you enough for your attention to detail in tracking this error down and suggesting a fix.
Moreover, the repo with the jasmine test was just the gentle prod I needed to get my house in order (i.e. start writing a proper test suite).  A package like this should really not exist without decent test coverage, but I've been putting it off due to my inexperience with testing.  Now that you've shown me a blueprint of how it can be done, I am without excuse. :-)
It's contributions like this that motivate me to implement things like this sooner rather than later.
If you're ever in Beijing, dinner's on me!

Forgot to mention: in 0.6.16, the function (err, res) { ... } can be passed as the second (or first) parameter of the tx.undo() and tx.redo() functions.  The default behaviour of firing tx.onTransactionExpired (on the client only) is unchanged (for backwards compatibility), but can be switched off in favour of using callbacks with tx.onTransactionExpired = null;.

Cool, thanks.
re: testing .. agreed, especially for a package like this where it really is important it does the right thing, or at least refuses to do the right thing if anything might go wrong!
You might want to consider creating a separate test app repo, which adds meteor-transaction package, so that you can use the full set of velocity - enabled test frameworks, especially sanjo:jasmine, and perhaps xolvio:cucumber for GUi testing of the undo / redo widgets. You could then write any mix of client/server unit/integration tests you think is useful.  You could use my bug repo as a starting point if that helped.
I have recently been involved with the Velocity core team, as I contributed a Velocity wrapper for the python - based robotframework end-to-end framework. They are a very helpful group, and very willing to help out. So, good luck !

Thanks again, Richard.  I'll definitely be using your bug repo as a starting point for moving forward with testing.
You're absolutely right that the package should refuse to do anything if there's a potential problem.  If I get that mongo 2-phase commit going properly, it will be a big step in the right direction, but having a decent test suite is non-negotiable if this package is going to end up in production apps.


The model predicts the relationship of all entities as "N", that is, no relationship.

Because the data labeling strategy according to the multi-head selection model, most of the relationship labels are "N", which leads to the model biasing the prediction of "N". How to solve such a problem?

Well this is not an issue in any of our examined datasets. We have examined four datasets in our work. I guess you use your own dataset. You can try to weight the examples to solve your imbalanced problem. Another solution might be to remove the N label completely from the model (i.e., you have to change the model for that). Basically, you get probabilities for each of the labels and when for every of the examined labels, you get a threshold below 0.5, you can infer that there is no relation. This is just an idea and I am not sure whether it will work in practice.

uaho1


Moving Windows security info to new page

Moving Windows security information to a new page
Part of #31428
/label refactor
/sig windows

/sig security

/assign @brasmith-ms

Preview: https://deploy-preview-31851--kubernetes-io-vnext-staging.netlify.app/docs/concepts/security/windows-security/

@sftim I incorporated your feedback and rebased.

todo: link to https://kubernetes.io/docs/concepts/security/pod-security-standards/#what-profiles-should-i-apply-to-my-windows-pods

todo: update https://kubernetes.io/docs/tasks/configure-pod-container/create-hostprocess-pod/   to reference  https://kubernetes.io/docs/concepts/security/pod-security-standards/#what-profiles-should-i-apply-to-my-windows-pod

Let's get the balls rolling. Approving based the feedback/revision history.
/lgtm
/approve

@tengqm Thanks for merging this.
I discussed these PRs and the parent issue during one of the sig-docs community meetings in March.
The we all discussed was to stage all of the PRs that split up intro-windows-in-kubernetes.md in the dev-1.24 branch but hold them until after the initial dev-1.24->main and then do another merge shortly after.
The intentions here was sig-docs leads weren't sure they would have enough bandwidth to adequately review the Windows PRs due to all the dockershim removal work. @sftim, @nate-double-u, and a few others were there as well.
My apologies for not adding a hold here.
Would you all like me to revert this PR or is it OK to keep in dev-1.24?
I'm OK either way.
I'm going to focus on the rest of the items listed in https://github.com/kubernetes/website/issues/31428 after 1.24 code freeze.

At this point a revert won't achieve what we'd want (reduced workload for the release docs team). I guess these are OK to live with, and the changes are beneficial.

What I had in mind when kicking this in was: 1. a refactoring work is nontrivial, we will need to achieve the goal in a step by step way; 2. the Windows docs are well maintained so far and people are actively improving them, we are supposed to encourage that; 3.  having a PR not moving on for 20+ days (as you both mentioned, no WIP sign) worries me, from the review history of this one, I can only see some non-blocking nits.
I'm sorry for not checking the meeting notes for these.

SIG Docs discussed, in a meeting yesterday, that once there are a bunch of PRs that are ready to merge into the main branch, SIG Docs can help get those merged.
In my view, there great part of the effort is lining up PRs that are good to merge, and actually merging them is more restricted (needs an approver's time) but less effort.
We also agreed in that meeting that those involved favor continuing to work towards doing that merge after the v1.24 release.


Add maven-publish plugin

Add's the maven publish plugin with only a mechanism for locally installing, this will need to be extended to publish to maven central (but it seems odd to publish this plugin without signing it with sigstore?) So lets see how that goes -- maybe we could do it with a non-gradle tool for now and just include it in the publication.
Signed-off-by: Appu Goundan<EMAIL_ADDRESS>

gonna have to cosign it


RFC 001: Cancelable operations and use of Context

This PR adds an RFC about how we should use Context in Genji.
It is opened for comments and suggestions.

Codecov Report

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

@@            Coverage Diff             @@
##           master     #249      +/-   ##
==========================================
- Coverage   61.61%   60.81%   -0.80%
==========================================
  Files          67       68       +1
  Lines        6273     6579     +306
==========================================
+ Hits         3865     4001     +136
- Misses       1895     2058     +163
- Partials      513      520       +7

Impacted Files
Coverage Δ

sql/parser/options.go
100.00% <0.00%> (ø)

sql/query/expr/function.go
6.55% <0.00%> (+0.82%)
:arrow_up:

sql/parser/expr.go
80.95% <0.00%> (+2.67%)
:arrow_up:

sql/parser/parser.go
87.68% <0.00%> (+4.70%)
: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 d7ed9d8...087bbb4. Read the comment docs.

I think parser.ParseQuery shouldn’t accept context (it does so now). Parsing statements shouldn’t be an expensive operation.

@tie @yaziine Do you see any blocker for this RFC?


SNlM0e has disappeared

It's still in the browser, but calling with GET and current cookie setup produces a response without it
Also, calling the stream API (which also has a new body format) with a manually extracted SNlM0e and __Secure-1PSID doesn't work. It's like there is something detecting that the call is not originating from the browser UI

guess we had a good run


Add support for Connect Aktor

Hi,
it would be great if support for the connect aktor could be added.
Without this support, the shutter level is displayed in the temperature state with an odd scaling.
See https://forum.iobroker.net/topic/25227/homepilot-fehler-bei-connect-aktor-kein-level for details.
Thanks!

Hi,
initially I developed this adapter for Rademacher shutter belt actors. From time to time other user contributed data and time to add more actors. As I still only use shutter belt actors I can not really develop further versions. But if you have pull requests I'd really appreciate it.

Hi,
after some search I have found the problem (I think). At the beginning I did not understand why my Aktor with the code 49 behaves differently than the Connect Aktor with the code 4B.
After some checking I realized, that the following code in main.js has a bug:
parseInt(duoferncode.substring(0,2)) < 20 is true for the input '4B' as in that case, parseInt results in '4' as partInt expects a decimal value as parameter.
As the code is in hexadecimal I expect that all lines containing that code have to be changes as following:
parseInt(duoferncode.substring(0,2), 16) < 26
26 instead of 20 as 0x19 is 25.
I know the solution but I don't know how to build that adapter.
Could you please create a new adapter version and I can test it with my configuration?
Thanks
Christof

Hi,
finally I realized that I can simply change the code in my local installation and try it out.
This was successfull, so that I created a pull request with my changes.
I hope those are acceptable.
Thanks for the great adapter!
Bye
Christof


[Spike] BTC <> DEGEN frame

https://shapeshift.notion.site/F-Multichain-trade-Frame-8cf92831c8024680863dd6f19e2aa68b

Updated the spec to reflect a more possible GTM:

Blocked on router upgrades from TC.
Go to market with just L1 swaps upgrading gomes first app into an MVP with better styling.

Closing this spike for now as complete.


Adding title to contenful-tables

Hey, first of all thanks, cool extension. Is there any possibility to add a title to table content object? right now they are all saved as undefined with no option to change somehow.

Ok never mind.
Add new text field to custom table content model
Set as Entry title
Sorry new with contentful so this was not obvious to me


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/117770

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/119171


Add From conversions for HeaderValue(s) to Raw

This improves ergonomics, and more importantly, could save the next developer some time grappling with the types and conversions involved.  See the new doctest in src/header/mod.rs for the best summary.
Conflicting trait (coherence?) rules prevented implementing some generic From over IntoIterator<Item=HeaderValue> or Iterator to Raw, so I've implemented the same directly using the concrete GetAll struct as returned by HeaderMap::get_all.
This likely warrants bumping to 0.14.0.

#8 is a alternative to this, which is nicer to use and faster, but a more significant breaking change.

Closing in preference to #8.


[Feature] Show disclaimer if report from manifest

PR checklist

[x] Ensure you have added or ran the appropriate tests for your PR.
[x] DCO signed

What type of PR is this?
feature
What this PR does / why we need it:

need disclaimer to hint user when reports are generated from manifest file

Which issue(s) this PR fixes:
sc-32348
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

LGTM


Zoom to fit: request

Could you give me an example of how (with a perspective camera) I can zoom to fill the screen on a 3D object or set of 3D objects?

hello
I've attatched screen fit example for your request #36
this code like as below.
using System;
using System.Collections.Generic;
using System.Text;
using THREE;
using THREEExample.Learning.Utils;
namespace THREEExample
{
    [Example("LightHint", ExampleCategory.ThreeJs, "loader")]
    public class LightHintExample :Example
    {
        Vector3 _cameraEye;
        Vector3 _center;
        Vector3 _up;
        float _fov;
        AmbientLight ambientLight;
        DirectionalLight directionalLight;
        public LightHintExample() : base()
        {
            _cameraEye = new Vector3(-1.5f,-3.0f,2.0f);
            _center = new Vector3(0,0,0);
            _up = new Vector3(0,0,1);
            _fov = 45f;
        }
        public override void InitLighting()
        {
            ambientLight = new AmbientLight(THREE.Color.Hex(0x888888));
            directionalLight = new DirectionalLight() { Color = THREE.Color.Hex(0x888888) };

            scene.Add(ambientLight);
            scene.Add(directionalLight);
        }
        private Vector3 Offset(Vector3 source,Vector3 direction,float distance)
        {
            var normal = direction.Clone().Normalize();
            source.X += normal.X * distance;
            source.Y += normal.Y * distance;
            source.Z += normal.Z * distance;
            return source;
        }
        private void AdjustClippingPlanesToSphere(Sphere boundingSphere)
        {
            if(boundingSphere.Radius <=0.0000f)
            {
                return;
            }
            if(boundingSphere.Radius <= 10.0f)
            {
                camera.Near = 0.01f;
                camera.Far = 100;
            }
            else if (boundingSphere.Radius <= 100.0f)
            {
                camera.Near = 0.1f;
                camera.Far = 1000f;
            }
            else if(boundingSphere.Radius <= 1000.0f)
            {
                camera.Near = 10.0f;
                camera.Far = 10000f;
            }
            else
            {
                camera.Near = 100.0f;
                camera.Far = 1000000f;
            }
        }
        private void FitToSphere(Vector3 center,float radius)
        {
            var offsetToOrigin = _center - center;
            _cameraEye = _cameraEye - offsetToOrigin;
            _center = center.Clone();
            var centerEyeDirection = (_cameraEye - _center).Normalize();
            var fieldOfView = _fov / 2.0f;
            if (this.glControl.Width < this.glControl.Height)
            {
                fieldOfView = fieldOfView * glControl.Width / glControl.Height;
            }
            var distance = radius / (float)System.Math.Sin(fieldOfView * MathUtils.DEG2RAD);
            var centerCloned = _center.Clone();
            centerCloned = Offset(centerCloned,centerEyeDirection,distance);
            _cameraEye = centerCloned;
        }

        private void FitSphereToWindow(Sphere boundingSphere)
        {
            Vector3 center = boundingSphere.Center.Clone();
            float radius = boundingSphere.Radius;
            FitToSphere(center, radius);
        }

        public void FitModelToWindow(Object3D model)
        {
            Box3 boundingBox = new Box3();
            boundingBox = boundingBox.SetFromObject(model);
            Sphere boundingSphere = new Sphere();
            boundingSphere = boundingBox.GetBoundingSphere(boundingSphere);
            AdjustClippingPlanesToSphere(boundingSphere);
            FitSphereToWindow(boundingSphere);

            camera.Position = _cameraEye;
            camera.Up = _up;
            camera.LookAt(_center.X, _center.Y, _center.Z);
            camera.Aspect = glControl.AspectRatio;
            camera.Fov = _fov;
            camera.UpdateProjectionMatrix();

            var lightDir = _cameraEye - _center;
            directionalLight.Position.Set(lightDir.X,lightDir.Y,lightDir.Z);
        }
        public virtual void BuildScene()
        {

            OBJLoader loader = new OBJLoader();
            var mesh = loader.Parse(@"../../../../assets/models/obj/80038032{18}.obj");
            var childMesh = mesh.Children[0];

            mesh.CastShadow = true;

            scene.Add(mesh);

            // FitModelToWindow(mesh);
            FitModelToWindow(childMesh); //-->  you can set this target object
        }
        public override void Init()
        {
            base.Init();
            BuildScene();
        }
    }

}

@hjoykim thank you. That example code is that I'm currently using.
My mistake was setting a camera.zoom value at startup...
Now i set camera.zoom=1

but if I use "FitModelToWindow" with small objects then I get clipped...
https://github.com/user-attachments/assets/14b6e56b-9199-4852-90ce-97ca2ff197ca

I think that zooming change camera position according to eye position. but TrackballController didn't work this job your zooming after FitModelToWindow
so, you must redefine your camera controller

I'm sorry but I can't undestand.
My trackballcontrol has ha camera reference, what Do I have to redefine ?

I mean that redefine --> create your own Camera controller to change camera settings.
this problem is caused that camera near and far factor value is set to small,
so you should make to fix that this value is not changed by zooming for your target object.
below code would help you
public void FitModelToWindow(Object3D model, bool nearFarChange)
{
    Box3 boundingBox = new Box3();
    boundingBox = boundingBox.SetFromObject(model);
    Sphere boundingSphere = new Sphere();
    boundingSphere = boundingBox.GetBoundingSphere(boundingSphere);
    if(nearFarChange)
    {
        AdjustClippingPlanesToSphere(boundingSphere);
    }
    FitSphereToWindow(boundingSphere);

    camera.Position = _cameraEye;
    camera.Up = _up;
    camera.LookAt(_center.X, _center.Y, _center.Z);
    camera.Aspect = glControl.AspectRatio;
    camera.Fov = _fov;
    camera.UpdateProjectionMatrix();

    var lightDir = _cameraEye - _center;
    directionalLight.Position.Set(lightDir.X,lightDir.Y,lightDir.Z);
}

...
if object is loaded at first,
FitModelToWindow(childMesh,true);

and you want to fit model to window
FitModelToWindow(childMesh,false);


Pausing filter chain on http request body doesn't work for dynamic forward proxy. It works when envoy is reverse-proxy.

I have a HTTP WASM filter where I make a http callout in the request body callback. After the callout, I return FilterDataStatus::StopIterationAndBuffer(which is 1) for this callback and want envoy to pause and wait for the callout reply to decide to stop or continue.
This works when envoy is reverse-proxy. However, when envoy is dynamic-forward-proxy, the pause didn't happen for the request body and the filter chain continued for the request body.
Looking at the log, for dynamic forward proxy, it's possible that after DNS is resolved asynchronously(which was triggered by http request headers), when it tried to continue the filter chain, it didn't check for the filter chain's current status and continued even when a previous filter returned FilterDataStatus::StopIterationAndBuffer.
[2021-07-23 01:24:03.141][558823][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_request_body return: 1
[2021-07-23 01:24:03.141][558823][trace][http] [source/common/http/filter_manager.cc:676] [C0][S12846879879184174189] decode data called: filter=0x47c1bd46cf50 status=1
[2021-07-23 01:24:03.141][558823][trace][http] [source/common/http/http1/codec_impl.cc:613] [C0] parsed 223 bytes
[2021-07-23 01:24:03.141][558823][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1250] membership update for TLS cluster dynamic_forward_proxy_cluster added 1 removed 0
[2021-07-23 01:24:03.141][558823][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1257] re-creating local LB for TLS cluster dynamic_forward_proxy_cluster
[2021-07-23 01:24:03.142][558823][debug][forward_proxy] [source/extensions/filters/http/dynamic_forward_proxy/proxy_filter.cc:142] [C0][S12846879879184174189] load DNS cache complete, continuing
[2021-07-23 01:24:03.142][558823][trace][http] [source/common/http/filter_manager.cc:70] [C0][S12846879879184174189] continuing filter chain: filter=0x47c1bd46d030
[2021-07-23 01:24:03.142][558823][debug][router] [source/common/router/router.cc:448] [C0][S12846879879184174189] cluster 'dynamic_forward_proxy_cluster' match for URL '/'
[2021-07-23 01:24:03.142][558823][debug][router] [source/common/router/router.cc:634] [C0][S12846879879184174189] router decoding headers:

In the above log, when "load DNS cache complete, continuing", looks like it didn't check the fact that a filter previously returned 1(FilterDataStatus::StopIterationAndBuffer) for the request body. Can someone confirm if this is a bug? I can provide the repro code if needed.

Just to get a bit more detail on this, it looks like you tried to stop iteration on the request body but your logs show that after DNS succeeded the router continued processing request headers.
If you tell Envoy to stop iteration on the body it doesn't stop processing headers, but it should hold back the body until you're done processing that.  Are you seeing the body processed as well or was there a misunderstanding on what you're trying to pause?

Thank you for looking into this, @alyssawilk. Yes, your description matches my intention. In other words, I want to sanitize request body before it's sent to upstream. It's ok if the request headers are continued and sent to upstream.
For "Are you seeing the body processed as well", I think so. The whole request body were sent to upstream without waiting for the callout reply.  This problem only happens when envoy is running as dynamic forward proxy. With the same filter code,  if I run envoy as reverse-proxy, the request body was held until I do resume_http_request() in the callout reply. That's why I suspect it's a bug in dynamic forward proxy when DNS is completed and filters are continued.

hm, the logs pasted only show forwarding the headers. any chance you have a more complete trace of this happening?

Yes. Here is the complete trace:
[2021-08-03 07:41:41.584][594068][debug][conn_handler] [source/server/active_tcp_listener.cc:332] [C0] new connection from <IP_ADDRESS>:49960
[2021-08-03 07:41:41.584][594068][trace][connection] [source/common/network/connection_impl.cc:552] [C0] socket event: 3
[2021-08-03 07:41:41.584][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C0] write ready
[2021-08-03 07:41:41.584][594068][trace][connection] [source/common/network/connection_impl.cc:590] [C0] read ready. dispatch_buffered_data=false
[2021-08-03 07:41:41.584][594068][trace][connection] [source/common/network/raw_buffer_socket.cc:24] [C0] read returns: 227
[2021-08-03 07:41:41.584][594068][trace][connection] [source/common/network/raw_buffer_socket.cc:38] [C0] read error: Resource temporarily unavailable
[2021-08-03 07:41:41.585][594068][trace][http] [source/common/http/http1/codec_impl.cc:564] [C0] parsing 227 bytes
[2021-08-03 07:41:41.585][594068][trace][http] [source/common/http/http1/codec_impl.cc:843] [C0] message begin
[2021-08-03 07:41:41.585][594068][debug][http] [source/common/http/conn_manager_impl.cc:274] [C0] new stream
[2021-08-03 07:41:41.585][594068][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x444afcea0850 for 300000ms, min is 300000ms
[2021-08-03 07:41:41.586][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C0] completed header: key=Host value=myserver.com:9100
[2021-08-03 07:41:41.586][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C0] completed header: key=User-Agent value=curl/7.68.0
[2021-08-03 07:41:41.586][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C0] completed header: key=Accept value=*/*
[2021-08-03 07:41:41.586][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C0] completed header: key=Proxy-Connection value=Keep-Alive
[2021-08-03 07:41:41.586][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C0] completed header: key=Content-Type value=application/json
[2021-08-03 07:41:41.586][594068][trace][http] [source/common/http/http1/codec_impl.cc:694] [C0] onHeadersCompleteBase
[2021-08-03 07:41:41.586][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C0] completed header: key=Content-Length value=32
[2021-08-03 07:41:41.586][594068][trace][http] [source/common/http/http1/codec_impl.cc:1041] [C0] Server: onHeadersComplete size=6
[2021-08-03 07:41:41.586][594068][debug][http] [source/common/http/conn_manager_impl.cc:872] [C0][S12839156143591365990] request headers complete (end_stream=false):
':authority', 'myserver.com:9100'
':scheme', 'http'
':path', '/predict'
':method', 'POST'
'user-agent', 'curl/7.68.0'
'accept', '*/*'
'proxy-connection', 'Keep-Alive'
'content-type', 'application/json'
'content-length', '32'

[2021-08-03 07:41:41.586][594068][trace][http] [source/common/http/filter_manager.cc:527] [C0][S12839156143591365990] decodeHeaders loop filter=0x444afcea08c0
[2021-08-03 07:41:41.586][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] proxy_on_context_create(2, 1)
[2021-08-03 07:41:41.587][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_context_create return: void
[2021-08-03 07:41:41.587][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] proxy_on_request_headers(2, 10)
[2021-08-03 07:41:41.589][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm->host] env.proxy_get_header_map_pairs(0, 1048448, 1048452)
[2021-08-03 07:41:41.589][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] malloc(309)
[2021-08-03 07:41:41.591][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] malloc return: 1114248
[2021-08-03 07:41:41.591][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm<-host] env.proxy_get_header_map_pairs return: 0
[2021-08-03 07:41:41.591][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm->host] env.proxy_log(1, 1115488, 330)
[2021-08-03 07:41:41.591][594068][debug][wasm] [source/extensions/common/wasm/context.cc:1215] wasm log test test: on_http_request_headers: [(":authority", "myserver.com:9100"), (":scheme", "http"), (":path", "/predict"), (":method", "POST"), ("user-agent", "curl/7.68.0"), ("accept", "*/*"), ("content-type", "application/json"), ("content-length", "32"), ("x-forwarded-proto", "http"), ("x-request-id", "55097614-592a-49b9-bc04-0adf64ddfb4d")]
[2021-08-03 07:41:41.591][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm<-host] env.proxy_log return: 0
[2021-08-03 07:41:41.592][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_request_headers return: 0
[2021-08-03 07:41:41.592][594068][trace][http] [source/common/http/filter_manager.cc:546] [C0][S12839156143591365990] decode headers called: filter=0x444afcea08c0 status=0
[2021-08-03 07:41:41.592][594068][trace][http] [source/common/http/filter_manager.cc:527] [C0][S12839156143591365990] decodeHeaders loop filter=0x444afcea09a0
[2021-08-03 07:41:41.592][594068][debug][forward_proxy] [source/extensions/common/dynamic_forward_proxy/dns_cache_impl.cc:101] thread local lookup for host 'myserver.com:9100'
[2021-08-03 07:41:41.592][594068][debug][forward_proxy] [source/extensions/common/dynamic_forward_proxy/dns_cache_impl.cc:122] cache miss for host 'myserver.com:9100', posting to main thread
[2021-08-03 07:41:41.592][594068][debug][forward_proxy] [source/extensions/filters/http/dynamic_forward_proxy/proxy_filter.cc:128] [C0][S12839156143591365990] waiting to load DNS cache entry
[2021-08-03 07:41:41.592][594068][trace][http] [source/common/http/filter_manager.cc:546] [C0][S12839156143591365990] decode headers called: filter=0x444afcea09a0 status=4
[2021-08-03 07:41:41.592][594068][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x444afcea0850 for 300000ms, min is 300000ms
[2021-08-03 07:41:41.592][594068][trace][http] [source/common/http/http1/codec_impl.cc:821] [C0] message complete
[2021-08-03 07:41:41.592][594068][trace][http] [source/common/http/http1/codec_impl.cc:1132] [C0] body size=32
[2021-08-03 07:41:41.592][594044][debug][forward_proxy] [source/extensions/common/dynamic_forward_proxy/dns_cache_impl.cc:269] starting main thread resolve for host='myserver.com:9100' dns='myserver.com' port='9100'
[2021-08-03 07:41:41.592][594068][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x444afcea0850 for 300000ms, min is 300000ms
[2021-08-03 07:41:41.592][594068][trace][http] [source/common/http/filter_manager.cc:620] [C0][S12839156143591365990] decodeData loop filter=0x444afcea08c0
[2021-08-03 07:41:41.592][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] proxy_on_request_body(2, 32, 0)
[2021-08-03 07:41:41.592][594044][trace][upstream] [source/common/network/dns_impl.cc:219] Setting DNS resolution timer for 5000 milliseconds
[2021-08-03 07:41:41.593][594044][debug][forward_proxy] [source/extensions/common/dynamic_forward_proxy/dns_cache_impl.cc:287] main thread resolve complete for host 'myserver.com:9100'. 1 results
[2021-08-03 07:41:41.593][594044][debug][forward_proxy] [source/extensions/common/dynamic_forward_proxy/dns_cache_impl.cc:326] host 'myserver.com:9100' address has changed
[2021-08-03 07:41:41.593][594044][debug][upstream] [source/extensions/clusters/dynamic_forward_proxy/cluster.cc:104] Adding host info for myserver.com:9100
[2021-08-03 07:41:41.593][594044][debug][upstream] [source/extensions/clusters/dynamic_forward_proxy/cluster.cc:83] adding new dfproxy cluster host 'myserver.com:9100'
[2021-08-03 07:41:41.593][594044][debug][upstream] [source/common/upstream/upstream_impl.cc:257] transport socket match, socket default selected for host with address <IP_ADDRESS>:9100
[2021-08-03 07:41:41.593][594044][trace][upstream] [source/common/upstream/upstream_impl.cc:1358] Local locality:
[2021-08-03 07:41:41.593][594044][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1250] membership update for TLS cluster dynamic_forward_proxy_cluster added 1 removed 0
[2021-08-03 07:41:41.593][594044][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1257] re-creating local LB for TLS cluster dynamic_forward_proxy_cluster
[2021-08-03 07:41:41.593][594067][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1250] membership update for TLS cluster dynamic_forward_proxy_cluster added 1 removed 0
[2021-08-03 07:41:41.593][594044][debug][forward_proxy] [source/extensions/common/dynamic_forward_proxy/dns_cache_impl.cc:345] DNS refresh rate reset for host 'myserver.com:9100', refresh rate 60000 ms
[2021-08-03 07:41:41.593][594067][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1257] re-creating local LB for TLS cluster dynamic_forward_proxy_cluster
[2021-08-03 07:41:41.594][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm->host] env.proxy_log(1, 1114248, 54)
[2021-08-03 07:41:41.594][594068][debug][wasm] [source/extensions/common/wasm/context.cc:1215] wasm log test test: on_http_request_body: body_size 32 end_of_stream false
[2021-08-03 07:41:41.594][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm<-host] env.proxy_log return: 0
[2021-08-03 07:41:41.595][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_request_body return: 1
[2021-08-03 07:41:41.595][594068][trace][http] [source/common/http/filter_manager.cc:683] [C0][S12839156143591365990] decode data called: filter=0x444afcea08c0 status=1
[2021-08-03 07:41:41.595][594068][trace][http] [source/common/http/filter_manager.cc:208] return false 2
[2021-08-03 07:41:41.595][594068][trace][http] [source/common/http/filter_manager.cc:698] [C0][S12839156143591365990] filter=0x444afcea08c0 status=1, return here.
[2021-08-03 07:41:41.595][594068][trace][connection] [source/common/network/connection_impl.cc:354] [C0] readDisable: disable=true disable_count=0 state=0 buffer_length=227
[2021-08-03 07:41:41.595][594068][debug][http] [source/common/http/filter_manager.cc:817] [C0][S12839156143591365990] request end stream
[2021-08-03 07:41:41.595][594068][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x444afcea0850 for 300000ms, min is 300000ms
[2021-08-03 07:41:41.595][594068][trace][http] [source/common/http/filter_manager.cc:620] [C0][S12839156143591365990] decodeData loop filter=0x444afcea08c0
[2021-08-03 07:41:41.595][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] proxy_on_request_body(2, 32, 1)
[2021-08-03 07:41:41.595][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm->host] env.proxy_log(1, 1114248, 53)
[2021-08-03 07:41:41.595][594068][debug][wasm] [source/extensions/common/wasm/context.cc:1215] wasm log test test: on_http_request_body: body_size 32 end_of_stream true
[2021-08-03 07:41:41.595][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm<-host] env.proxy_log return: 0
[2021-08-03 07:41:41.595][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm->host] env.proxy_http_call(1050536, 7, 1114304, 78, 0, 0, 1114248, 4, 5000, 1048452)
[2021-08-03 07:41:41.595][594068][debug][router] [source/common/router/router.cc:448] [C0][S1704033592469637009] cluster 'httpbin' match for URL '/bytes/1'
[2021-08-03 07:41:41.595][594068][debug][router] [source/common/router/router.cc:634] [C0][S1704033592469637009] router decoding headers:
':method', 'GET'
':path', '/bytes/1'
':authority', 'httpbin.org'
':scheme', 'http'
'x-envoy-internal', 'true'
'x-forwarded-for', '<IP_ADDRESS>'
'x-envoy-expected-rq-timeout-ms', '5000'

[2021-08-03 07:41:41.595][594068][debug][pool] [source/common/http/conn_pool_base.cc:74] queueing stream due to no available connections
[2021-08-03 07:41:41.595][594068][debug][pool] [source/common/conn_pool/conn_pool_base.cc:241] trying to create new connection
[2021-08-03 07:41:41.595][594068][trace][pool] [source/common/conn_pool/conn_pool_base.cc:242] ConnPoolImplBase 0x444afd938160, ready_clients_.size(): 0, busy_clients_.size(): 0, connecting_clients_.size(): 0, connecting_stream_capacity_: 0, num_active_streams_: 0, pending_streams_.size(): 1 per upstream preconnect ratio: 1
[2021-08-03 07:41:41.595][594068][debug][pool] [source/common/conn_pool/conn_pool_base.cc:139] creating a new connection
[2021-08-03 07:41:41.596][594068][debug][client] [source/common/http/codec_client.cc:60] [C1] connecting
[2021-08-03 07:41:41.596][594068][debug][connection] [source/common/network/connection_impl.cc:866] [C1] connecting to <IP_ADDRESS>:80
[2021-08-03 07:41:41.596][594068][debug][connection] [source/common/network/connection_impl.cc:884] [C1] connection in progress
[2021-08-03 07:41:41.596][594068][trace][pool] [source/common/conn_pool/conn_pool_base.cc:125] not creating a new connection, shouldCreateNewConnection returned false.
[2021-08-03 07:41:41.596][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm<-host] env.proxy_http_call return: 0
[2021-08-03 07:41:41.596][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm->host] env.proxy_log(0, 1114248, 18)
[2021-08-03 07:41:41.596][594068][trace][wasm] [source/extensions/common/wasm/context.cc:1212] wasm log test test: pause request body
[2021-08-03 07:41:41.596][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [vm<-host] env.proxy_log return: 0
[2021-08-03 07:41:41.596][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_request_body return: 1
[2021-08-03 07:41:41.596][594068][trace][http] [source/common/http/filter_manager.cc:683] [C0][S12839156143591365990] decode data called: filter=0x444afcea08c0 status=1
[2021-08-03 07:41:41.596][594068][trace][http] [source/common/http/filter_manager.cc:208] return false 2
[2021-08-03 07:41:41.596][594068][trace][http] [source/common/http/filter_manager.cc:698] [C0][S12839156143591365990] filter=0x444afcea08c0 status=1, return here.
[2021-08-03 07:41:41.596][594068][trace][http] [source/common/http/http1/codec_impl.cc:613] [C0] parsed 227 bytes
[2021-08-03 07:41:41.596][594068][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1250] membership update for TLS cluster dynamic_forward_proxy_cluster added 1 removed 0
[2021-08-03 07:41:41.596][594068][debug][upstream] [source/common/upstream/cluster_manager_impl.cc:1257] re-creating local LB for TLS cluster dynamic_forward_proxy_cluster
[2021-08-03 07:41:41.596][594068][debug][forward_proxy] [source/extensions/filters/http/dynamic_forward_proxy/proxy_filter.cc:142] [C0][S12839156143591365990] load DNS cache complete, continuing
[2021-08-03 07:41:41.596][594068][trace][http] [source/common/http/filter_manager.cc:70] [C0][S12839156143591365990] continuing filter chain: filter=0x444afcea09a0
[2021-08-03 07:41:41.596][594068][trace][http] [source/common/http/filter_manager.cc:527] [C0][S12839156143591365990] decodeHeaders loop filter=0x444afcea0a10
[2021-08-03 07:41:41.596][594068][debug][router] [source/common/router/router.cc:448] [C0][S12839156143591365990] cluster 'dynamic_forward_proxy_cluster' match for URL '/predict'
[2021-08-03 07:41:41.597][594068][debug][router] [source/common/router/router.cc:634] [C0][S12839156143591365990] router decoding headers:
':authority', 'myserver.com:9100'
':scheme', 'http'
':path', '/predict'
':method', 'POST'
'user-agent', 'curl/7.68.0'
'accept', '*/*'
'content-type', 'application/json'
'content-length', '32'
'x-forwarded-proto', 'http'
'x-request-id', '55097614-592a-49b9-bc04-0adf64ddfb4d'
'x-envoy-expected-rq-timeout-ms', '15000'

[2021-08-03 07:41:41.597][594068][debug][pool] [source/common/http/conn_pool_base.cc:74] queueing stream due to no available connections
[2021-08-03 07:41:41.597][594068][debug][pool] [source/common/conn_pool/conn_pool_base.cc:241] trying to create new connection
[2021-08-03 07:41:41.597][594068][trace][pool] [source/common/conn_pool/conn_pool_base.cc:242] ConnPoolImplBase 0x444afd938000, ready_clients_.size(): 0, busy_clients_.size(): 0, connecting_clients_.size(): 0, connecting_stream_capacity_: 0, num_active_streams_: 0, pending_streams_.size(): 1 per upstream preconnect ratio: 1
[2021-08-03 07:41:41.597][594068][debug][pool] [source/common/conn_pool/conn_pool_base.cc:139] creating a new connection
[2021-08-03 07:41:41.597][594068][debug][client] [source/common/http/codec_client.cc:60] [C2] connecting
[2021-08-03 07:41:41.597][594068][debug][connection] [source/common/network/connection_impl.cc:866] [C2] connecting to <IP_ADDRESS>:9100
[2021-08-03 07:41:41.598][594068][debug][connection] [source/common/network/connection_impl.cc:884] [C2] connection in progress
[2021-08-03 07:41:41.598][594068][trace][pool] [source/common/conn_pool/conn_pool_base.cc:125] not creating a new connection, shouldCreateNewConnection returned false.
[2021-08-03 07:41:41.598][594068][trace][http] [source/common/http/filter_manager.cc:546] [C0][S12839156143591365990] decode headers called: filter=0x444afcea0a10 status=1
[2021-08-03 07:41:41.598][594068][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x444afcea0850 for 300000ms, min is 300000ms
[2021-08-03 07:41:41.598][594068][trace][http] [source/common/http/filter_manager.cc:620] [C0][S12839156143591365990] decodeData loop filter=0x444afcea09a0
[2021-08-03 07:41:41.598][594068][trace][http] [source/common/http/filter_manager.cc:683] [C0][S12839156143591365990] decode data called: filter=0x444afcea09a0 status=0
[2021-08-03 07:41:41.598][594068][trace][http] [source/common/http/filter_manager.cc:212] return true
[2021-08-03 07:41:41.598][594068][trace][http] [source/common/http/filter_manager.cc:620] [C0][S12839156143591365990] decodeData loop filter=0x444afcea0a10
[2021-08-03 07:41:41.598][594068][trace][router] [source/common/router/upstream_request.cc:235] [C0][S12839156143591365990] buffering 32 bytes
[2021-08-03 07:41:41.598][594068][trace][http] [source/common/http/filter_manager.cc:683] [C0][S12839156143591365990] decode data called: filter=0x444afcea0a10 status=3
[2021-08-03 07:41:41.598][594068][trace][http] [source/common/http/filter_manager.cc:208] return false 2
[2021-08-03 07:41:41.598][594068][trace][connection] [source/common/network/connection_impl.cc:552] [C0] socket event: 2
[2021-08-03 07:41:41.598][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C0] write ready
[2021-08-03 07:41:41.599][594068][trace][connection] [source/common/network/connection_impl.cc:552] [C2] socket event: 2
[2021-08-03 07:41:41.599][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C2] write ready
[2021-08-03 07:41:41.599][594068][debug][connection] [source/common/network/connection_impl.cc:670] [C2] connected
[2021-08-03 07:41:41.599][594068][trace][connection] [source/common/network/connection_impl.cc:415] [C2] raising connection event 2
[2021-08-03 07:41:41.599][594068][debug][client] [source/common/http/codec_client.cc:88] [C2] connected
[2021-08-03 07:41:41.599][594068][debug][pool] [source/common/conn_pool/conn_pool_base.cc:285] [C2] attaching to next stream
[2021-08-03 07:41:41.599][594068][debug][pool] [source/common/conn_pool/conn_pool_base.cc:171] [C2] creating stream
[2021-08-03 07:41:41.599][594068][debug][router] [source/common/router/upstream_request.cc:386] [C0][S12839156143591365990] pool ready
[2021-08-03 07:41:41.599][594068][trace][connection] [source/common/network/connection_impl.cc:475] [C2] writing 257 bytes, end_stream false
[2021-08-03 07:41:41.599][594068][trace][connection] [source/common/network/connection_impl.cc:475] [C2] writing 32 bytes, end_stream false
[2021-08-03 07:41:41.599][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C2] write ready
[2021-08-03 07:41:41.599][594068][trace][connection] [source/common/network/raw_buffer_socket.cc:67] [C2] write returns: 289
[2021-08-03 07:41:41.599][594068][trace][connection] [source/common/network/connection_impl.cc:552] [C2] socket event: 2
[2021-08-03 07:41:41.599][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C2] write ready
[2021-08-03 07:41:41.618][594068][trace][connection] [source/common/network/connection_impl.cc:552] [C2] socket event: 3
[2021-08-03 07:41:41.618][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C2] write ready
[2021-08-03 07:41:41.618][594068][trace][connection] [source/common/network/connection_impl.cc:590] [C2] read ready. dispatch_buffered_data=false
[2021-08-03 07:41:41.618][594068][trace][connection] [source/common/network/raw_buffer_socket.cc:24] [C2] read returns: 137
[2021-08-03 07:41:41.618][594068][trace][connection] [source/common/network/raw_buffer_socket.cc:38] [C2] read error: Resource temporarily unavailable
[2021-08-03 07:41:41.618][594068][trace][http] [source/common/http/http1/codec_impl.cc:564] [C2] parsing 137 bytes
[2021-08-03 07:41:41.618][594068][trace][http] [source/common/http/http1/codec_impl.cc:843] [C2] message begin
[2021-08-03 07:41:41.619][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C2] completed header: key=Date value=Tue, 03 Aug 2021 07:41:41 GMT
[2021-08-03 07:41:41.619][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C2] completed header: key=Content-Length value=20
[2021-08-03 07:41:41.619][594068][trace][http] [source/common/http/http1/codec_impl.cc:694] [C2] onHeadersCompleteBase
[2021-08-03 07:41:41.619][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C2] completed header: key=Content-Type value=text/plain; charset=utf-8
[2021-08-03 07:41:41.619][594068][trace][http] [source/common/http/http1/codec_impl.cc:1268] [C2] status_code 200
[2021-08-03 07:41:41.619][594068][trace][http] [source/common/http/http1/codec_impl.cc:1278] [C2] Client: onHeadersComplete size=3
[2021-08-03 07:41:41.619][594068][debug][router] [source/common/router/router.cc:1234] [C0][S12839156143591365990] upstream headers complete: end_stream=false
[2021-08-03 07:41:41.621][594068][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x444afcea0850 for 300000ms, min is 300000ms
[2021-08-03 07:41:41.621][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] proxy_on_response_headers(2, 5)
[2021-08-03 07:41:41.623][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_response_headers return: 0
[2021-08-03 07:41:41.623][594068][trace][http] [source/common/http/filter_manager.cc:1077] [C0][S12839156143591365990] encode headers called: filter=0x444afcea0930 status=0
[2021-08-03 07:41:41.623][594068][debug][http] [source/common/http/conn_manager_impl.cc:1471] [C0][S12839156143591365990] encoding headers via codec (end_stream=false):
':status', '200'
'date', 'Tue, 03 Aug 2021 07:41:41 GMT'
'content-length', '20'
'content-type', 'text/plain; charset=utf-8'
'x-envoy-upstream-service-time', '21'
'server', 'envoy'

[2021-08-03 07:41:41.623][594068][trace][connection] [source/common/network/connection_impl.cc:475] [C0] writing 167 bytes, end_stream false
[2021-08-03 07:41:41.623][594068][trace][http] [source/common/http/http1/codec_impl.cc:821] [C2] message complete
[2021-08-03 07:41:41.623][594068][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x444afcea0850 for 300000ms, min is 300000ms
[2021-08-03 07:41:41.623][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] proxy_on_response_body(2, 20, 0)
[2021-08-03 07:41:41.626][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_response_body return: 0
[2021-08-03 07:41:41.626][594068][trace][http] [source/common/http/filter_manager.cc:1240] [C0][S12839156143591365990] encode data called: filter=0x444afcea0930 status=0
[2021-08-03 07:41:41.626][594068][trace][http] [source/common/http/filter_manager.cc:212] return true
[2021-08-03 07:41:41.626][594068][trace][http] [source/common/http/conn_manager_impl.cc:1480] [C0][S12839156143591365990] encoding data via codec (size=20 end_stream=false)
[2021-08-03 07:41:41.626][594068][trace][connection] [source/common/network/connection_impl.cc:475] [C0] writing 20 bytes, end_stream false
[2021-08-03 07:41:41.626][594068][trace][http] [source/common/http/http1/codec_impl.cc:1350] [C2] message complete
[2021-08-03 07:41:41.626][594068][debug][client] [source/common/http/codec_client.cc:130] [C2] response complete
[2021-08-03 07:41:41.626][594068][trace][main] [source/common/event/dispatcher_impl.cc:251] item added to deferred deletion list (size=1)
[2021-08-03 07:41:41.627][594068][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x444afcea0850 for 300000ms, min is 300000ms
[2021-08-03 07:41:41.627][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] proxy_on_response_body(2, 0, 1)
[2021-08-03 07:41:41.627][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_response_body return: 0
[2021-08-03 07:41:41.627][594068][trace][http] [source/common/http/filter_manager.cc:1240] [C0][S12839156143591365990] encode data called: filter=0x444afcea0930 status=0
[2021-08-03 07:41:41.627][594068][trace][http] [source/common/http/filter_manager.cc:212] return true
[2021-08-03 07:41:41.627][594068][trace][http] [source/common/http/conn_manager_impl.cc:1480] [C0][S12839156143591365990] encoding data via codec (size=0 end_stream=true)
[2021-08-03 07:41:41.627][594068][trace][connection] [source/common/network/connection_impl.cc:354] [C0] readDisable: disable=false disable_count=1 state=0 buffer_length=0
[2021-08-03 07:41:41.628][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] proxy_on_log(2)
[2021-08-03 07:41:41.629][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_log return: void
[2021-08-03 07:41:41.630][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] proxy_on_done(2)
[2021-08-03 07:41:41.631][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_done return: 1
[2021-08-03 07:41:41.631][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] proxy_on_delete(2)
[2021-08-03 07:41:41.632][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_delete return: void
[2021-08-03 07:41:41.632][594068][trace][main] [source/common/event/dispatcher_impl.cc:251] item added to deferred deletion list (size=2)
[2021-08-03 07:41:41.632][594068][trace][misc] [source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x444afcea0770 for 3600000ms, min is 3600000ms
[2021-08-03 07:41:41.632][594068][debug][pool] [source/common/http/http1/conn_pool.cc:53] [C2] response complete
[2021-08-03 07:41:41.632][594068][debug][pool] [source/common/conn_pool/conn_pool_base.cc:200] [C2] destroying stream: 0 remaining
[2021-08-03 07:41:41.632][594068][trace][http] [source/common/http/http1/codec_impl.cc:613] [C2] parsed 137 bytes
[2021-08-03 07:41:41.632][594068][trace][main] [source/common/event/dispatcher_impl.cc:115] clearing deferred deletion list (size=2)
[2021-08-03 07:41:41.632][594068][trace][connection] [source/common/network/connection_impl.cc:552] [C0] socket event: 2
[2021-08-03 07:41:41.632][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C0] write ready
[2021-08-03 07:41:41.632][594068][trace][connection] [source/common/network/raw_buffer_socket.cc:67] [C0] write returns: 187
[2021-08-03 07:41:41.632][594068][trace][connection] [source/common/network/connection_impl.cc:552] [C0] socket event: 3
[2021-08-03 07:41:41.632][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C0] write ready
[2021-08-03 07:41:41.632][594068][trace][connection] [source/common/network/connection_impl.cc:590] [C0] read ready. dispatch_buffered_data=false
[2021-08-03 07:41:41.633][594068][trace][connection] [source/common/network/raw_buffer_socket.cc:24] [C0] read returns: 0
[2021-08-03 07:41:41.633][594068][debug][connection] [source/common/network/connection_impl.cc:638] [C0] remote close
[2021-08-03 07:41:41.633][594068][debug][connection] [source/common/network/connection_impl.cc:248] [C0] closing socket: 0
[2021-08-03 07:41:41.633][594068][trace][connection] [source/common/network/connection_impl.cc:415] [C0] raising connection event 0
[2021-08-03 07:41:41.633][594068][debug][conn_handler] [source/server/active_tcp_listener.cc:76] [C0] adding to cleanup list
[2021-08-03 07:41:41.633][594068][trace][main] [source/common/event/dispatcher_impl.cc:251] item added to deferred deletion list (size=1)
[2021-08-03 07:41:41.633][594068][trace][main] [source/common/event/dispatcher_impl.cc:251] item added to deferred deletion list (size=2)
[2021-08-03 07:41:41.633][594068][trace][main] [source/common/event/dispatcher_impl.cc:115] clearing deferred deletion list (size=2)
[2021-08-03 07:41:41.670][594068][trace][connection] [source/common/network/connection_impl.cc:552] [C1] socket event: 2
[2021-08-03 07:41:41.670][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C1] write ready
[2021-08-03 07:41:41.670][594068][debug][connection] [source/common/network/connection_impl.cc:670] [C1] connected
[2021-08-03 07:41:41.670][594068][trace][connection] [source/common/network/connection_impl.cc:415] [C1] raising connection event 2
[2021-08-03 07:41:41.670][594068][debug][client] [source/common/http/codec_client.cc:88] [C1] connected
[2021-08-03 07:41:41.671][594068][debug][pool] [source/common/conn_pool/conn_pool_base.cc:285] [C1] attaching to next stream
[2021-08-03 07:41:41.671][594068][debug][pool] [source/common/conn_pool/conn_pool_base.cc:171] [C1] creating stream
[2021-08-03 07:41:41.671][594068][debug][router] [source/common/router/upstream_request.cc:386] [C0][S1704033592469637009] pool ready
[2021-08-03 07:41:41.671][594068][trace][connection] [source/common/network/connection_impl.cc:475] [C1] writing 136 bytes, end_stream false
[2021-08-03 07:41:41.671][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C1] write ready
[2021-08-03 07:41:41.671][594068][trace][connection] [source/common/network/raw_buffer_socket.cc:67] [C1] write returns: 136
[2021-08-03 07:41:41.671][594068][trace][connection] [source/common/network/connection_impl.cc:552] [C1] socket event: 2
[2021-08-03 07:41:41.671][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C1] write ready
[2021-08-03 07:41:41.751][594068][trace][connection] [source/common/network/connection_impl.cc:552] [C1] socket event: 3
[2021-08-03 07:41:41.751][594068][trace][connection] [source/common/network/connection_impl.cc:661] [C1] write ready
[2021-08-03 07:41:41.751][594068][trace][connection] [source/common/network/connection_impl.cc:590] [C1] read ready. dispatch_buffered_data=false
[2021-08-03 07:41:41.751][594068][trace][connection] [source/common/network/raw_buffer_socket.cc:24] [C1] read returns: 237
[2021-08-03 07:41:41.751][594068][trace][connection] [source/common/network/raw_buffer_socket.cc:38] [C1] read error: Resource temporarily unavailable
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:564] [C1] parsing 237 bytes
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:843] [C1] message begin
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C1] completed header: key=Date value=Tue, 03 Aug 2021 07:41:41 GMT
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C1] completed header: key=Content-Type value=application/octet-stream
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C1] completed header: key=Content-Length value=1
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C1] completed header: key=Connection value=keep-alive
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C1] completed header: key=Server value=gunicorn/19.9.0
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C1] completed header: key=Access-Control-Allow-Origin value=*
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:694] [C1] onHeadersCompleteBase
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:484] [C1] completed header: key=Access-Control-Allow-Credentials value=true
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:1268] [C1] status_code 200
[2021-08-03 07:41:41.751][594068][trace][http] [source/common/http/http1/codec_impl.cc:1278] [C1] Client: onHeadersComplete size=7
[2021-08-03 07:41:41.751][594068][debug][router] [source/common/router/router.cc:1234] [C0][S1704033592469637009] upstream headers complete: end_stream=false
[2021-08-03 07:41:41.753][594068][debug][http] [source/common/http/async_client_impl.cc:104] async http request response headers (end_stream=false):
':status', '200'
'date', 'Tue, 03 Aug 2021 07:41:41 GMT'
'content-type', 'application/octet-stream'
'content-length', '1'
'connection', 'keep-alive'
'server', 'gunicorn/19.9.0'
'access-control-allow-origin', '*'
'access-control-allow-credentials', 'true'
'x-envoy-upstream-service-time', '155'

[2021-08-03 07:41:41.753][594068][trace][http] [source/common/http/http1/codec_impl.cc:821] [C1] message complete
[2021-08-03 07:41:41.753][594068][trace][http] [source/common/http/async_client_impl.cc:121] async http request response data (length=1 end_stream=false)
[2021-08-03 07:41:41.753][594068][trace][http] [source/common/http/http1/codec_impl.cc:1350] [C1] message complete
[2021-08-03 07:41:41.753][594068][debug][client] [source/common/http/codec_client.cc:130] [C1] response complete
[2021-08-03 07:41:41.753][594068][trace][main] [source/common/event/dispatcher_impl.cc:251] item added to deferred deletion list (size=1)
[2021-08-03 07:41:41.754][594068][trace][http] [source/common/http/async_client_impl.cc:121] async http request response data (length=0 end_stream=true)
[2021-08-03 07:41:41.754][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host->vm] proxy_on_http_call_response(1, 1, 9, 1, 0)
[2021-08-03 07:41:41.757][594068][trace][wasm] [source/extensions/common/wasm/wasm_vm.cc:39] [host<-vm] proxy_on_http_call_response return: void
[2021-08-03 07:41:41.757][594068][trace][main] [source/common/event/dispatcher_impl.cc:251] item added to deferred deletion list (size=2)
[2021-08-03 07:41:41.757][594068][debug][pool] [source/common/http/http1/conn_pool.cc:53] [C1] response complete
[2021-08-03 07:41:41.757][594068][debug][pool] [source/common/conn_pool/conn_pool_base.cc:200] [C1] destroying stream: 0 remaining
[2021-08-03 07:41:41.757][594068][trace][http] [source/common/http/http1/codec_impl.cc:613] [C1] parsed 237 bytes
[2021-08-03 07:41:41.757][594068][trace][main] [source/common/event/dispatcher_impl.cc:115] clearing deferred deletion list (size=2)
[2021-08-03 07:41:45.944][594044][debug][main] [source/server/server.cc:215] flushing stats
[2021-08-03 07:41:50.947][594044][debug][main] [source/server/server.cc:215] flushing stats
[2021-08-03 07:41:55.955][594044][debug][main] [source/server/server.cc:215] flushing stats
[2021-08-03 07:42:00.938][594044][debug][upstream] [source/common/upstream/logical_dns_cluster.cc:107] starting async DNS resolution for httpbin.org
[2021-08-03 07:42:00.939][594044][trace][upstream] [source/common/network/dns_impl.cc:219] Setting DNS resolution timer for 5000 milliseconds
[2021-08-03 07:42:00.954][594044][debug][upstream] [source/common/upstream/logical_dns_cluster.cc:115] async DNS resolution complete for httpbin.org
[2021-08-03 07:42:00.954][594044][debug][upstream] [source/common/upstream/logical_dns_cluster.cc:161] DNS refresh rate reset for httpbin.org, refresh rate 30000 ms
[2021-08-03 07:42:00.959][594044][debug][main] [source/server/server.cc:215] flushing stats
[2021-08-03 07:42:05.963][594044][debug][main] [source/server/server.cc:215] flushing stats

And below is my filter code in rust, which is based on https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/master/examples/http_auth_random.rs
use log::*;
use proxy_wasm::traits::*;
use proxy_wasm::types::*;
use std::time::Duration;

#[no_mangle]
pub fn _start() {
    proxy_wasm::set_log_level(LogLevel::Trace);
    proxy_wasm::set_http_context(|_, _| -> Box<dyn HttpContext> { Box::new(HttpAuthRandom) });
}

struct HttpAuthRandom;

impl HttpContext for HttpAuthRandom {
    fn on_http_request_headers(&mut self, _: usize) -> Action {
        debug!(
            "on_http_request_headers: {:?}",
            self.get_http_request_headers()
        );
        Action::Continue
    }

    fn on_http_request_body(&mut self, body_size: usize, end_of_stream: bool) -> Action {
        debug!(
            "on_http_request_body: body_size {} end_of_stream {}",
            body_size, end_of_stream
        );
        if !end_of_stream {
            // Wait -- we'll be called again when the complete body is buffered
            // at the host side.
            return Action::Pause;
        }
        self.dispatch_http_call(
            "httpbin",
            vec![
                (":method", "GET"),
                (":path", "/bytes/1"),
                (":authority", "httpbin.org"),
            ],
            None,
            vec![],
            Duration::from_secs(5),
        )
        .unwrap();
        trace!("pause request body");
        Action::Pause
    }
}

impl Context for HttpAuthRandom {
    fn on_http_call_response(&mut self, _: u32, _: usize, _body_size: usize, _: usize) {
        trace!("on_http_call_response. block it");
        self.send_http_response(403, vec![], Some(b"Access forbidden.\n"));
    }
}

I'm no wasm expert but I think the DFP is doing the correct thing here, so maybe @mathetake or @PiotrSikora can take a look at the rust?
From a C++ perspective, DFP does call commonContinue() when it gets the DNS resolution, but commonContinue should detect that the wasm filter returned StopIterationAndSomething and continue to not forward data.  I believe https://github.com/envoyproxy/envoy/pull/17580 regression tests that DFP is working as expected.

From a C++ perspective, DFP does call commonContinue() when it gets the DNS resolution, but commonContinue should detect that the wasm filter returned StopIterationAndSomething and continue to not forward data. I believe #17580 regression tests that DFP is working as expected.

DFP calls decoder_callbacks_->continueDecoding(), which is the same call that Wasm is using to resume processing.
I'm not sure how DFP could continue, but not forward data?

@dandlake do you have DFP configured after or before Wasm? I think it should work if you put DFP before Wasm, since then DFP will pause and resume before passing request to the next filter, so it won't interfere with the Wasm code.
Basically, I think (but I didn't verify) that with HTTP filters Wasm -> DFP -> router, the flow is:

HTTP request headers -> Wasm (forward) -> DFP (pause on headers).
HTTP request body -> Wasm (pause on body).
DNS resolved -> continue.
HTTP request headers -> DFP (continued from 3.),
HTTP request body -> Wasm (continued from 3.).

But with HTTP filters DFP -> Wasm -> router, the flow would be:

HTTP request headers -> DFP (pause on headers),
DNS resolved -> continue,
HTTP request headers -> DFP (continued from 2.) -> Wasm (forward) -> router (forward).
HTTP request body -> DFP (forward, no-op) -> Wasm (pause on body).

Yes, reversing the wasm and DFP filters works. Thank you for the suggestion, @PiotrSikora!
While this works, do you see any downside of putting Wasm after DFP? I tested a few cases on my side and it seems fine, but want to see if you foresee any potential issue.
On the other hand, do you think step 5 above can be fixed so that request headers are continued(in step 4) but request body remains paused(since an earlier filter paused it)? Not sure if this question is for @alyssawilk or @PiotrSikora. Any other non-wasm filter can potentially return StopIterationAndSomething for request body. Do you want to support this case? or do you require other filters stay after DFP?

@dandlake yeah, it's definitely a bug (so please leave this open) and the reverse order should be supported, I just wanted to unblock you, since I imagine that putting DFP first should work for 95% of use cases.

continueDecoding is a complicated function.  It's a per filter call* so should undo the pause of that specific filter.
In this case if WASM paused the body and DFP paused headers and DFP resumed headers, it shouldn't result in body heading past WASM.  Again I think my regression test verifies that all that logic works as intended so I'm fairly confused what's causing the issue you're experiencing.  cc @mattklein123 @snowp
*hhttps://github.com/envoyproxy/envoy/blob/main/source/common/http/filter_manager.cc#L69

@alyssawilk right, but the "per filter" doHeaders, doData, doTrailers all call functions on the parent object:
https://github.com/envoyproxy/envoy/blob/79ade4aebd02cf15bd934d6d58e90aa03ef6909e/source/common/http/filter_manager.cc#L321-L332

@alyssawilk, @PiotrSikora Should I keep this issue open or should I leave it and let github close it?

Definitely leave it open, but I'm not sure if @alyssawilk or anybody else is actively working on it.

yeah it's backburner for me so left it unassigned but I'll tag no-stalebot.


Update the game over message.

Update the game over message so people know how to play again!

Looks fine but you need to make some changes


Weirdness upon switching from Core to Full

Have an abstract page open with core=always. I also set my internet speed to slow 3G for testing.
In another tab, set core=never
In the original abstract page tab, click on a link - the page hydrates but takes me back to the home page and doesn't leave me on the hydrated abstract, or, ideally, drop me on the link I'd just clicked.

This does not happen when we click on links that exist in core such as metrics, graphics or export. It only happens when we click on links such as citations, references, co-reads, similar, volume because those links just trigger a search (they are not a view in the abstract in core). Given that the cookie is set to never, the request is managed by BBB and not ADS Core (that's why a loading screen appears). But we still have problems with BBB and parameter queries (i.e., parameters sent after the ?) and that's why it goes to the main search form instead of showing the query.
This is something to be fixed in BBB and the way it is deployed, so I'll close it here.


[WIP] OCPBUGS-22216: version subcmd displays lvms version

The LVMS version isn't easy to obtain from microshift itself, and usually requires inspecting the container topolvm contain image.  This is complicated by the fact that microshift lumps the lvms images in with core openshift images and discards the lvms version.
The changes here do a couple things:

UX: changes the output of microshift version to append the lvms version. For example:

❯ _output/bin/microshift version
MicroShift Version: 4.16.0-0.nightly-2023-12-15-211129-20231220224009-6684e03d9-dirty
Base OCP Version: 4.16.0-0.nightly-2023-12-15-211129
Base LVMS Version: v4.14.1-4

LVMS versions are tracked only by the image tag and not by specific git commit.

Isolate lvms pull-specs and version data in a separate release file.
Inject lvms pull-spects into the release-images data struct to keep internal release-image handling as is
Update the lvms rebase logic to handle version and pull-spect parsing and storing

TODO:

Remove old lvms rebase logic

If we make the version command show the LVMS version we have to keep doing that and that will make it hard to decouple the CSI later.
We should be able to get the version from the input to the rebase command, can't we?
Can we save the version to a new config map in the same namespace as the controller? That should meet the requirements without adding another point of tight coupling. Later, from the command line, someone could look at the rpm version.

Closing as this has crept out of scope


Problem for installing MargGo

Hello,
I have been following the installation instructions in here https://margo.sh/b/migrate/ but I can't get margo to work. I have cloned the repo in /Application/Sublime Text 3/Contents/MacOS/Packages and restarted
Sublime text 3 but it still did not work. The command cmd+.+x does not work after restarting.
Thanks in advance!

@nicolasdilley the correct Packages directory is something like ~/Library/...Sublime Text 3.../Packages. You can find it via menu Preferences > Browse Packages....

Works like a charm thanks !


Fix loadRule when one of the tiers had no available servers

When one of the tiers have no servers, LoadRule should ignore that tier
and continue to load/drop segments in other available tiers.
the bug causes wierd behavior with LoadRule when some tier has no servers where the segment balancer keeps on moving segments to other nodes in existing tiers but the extra segment copies are never dropped eventually leading to all the tiers getting full .

Minor questions from my side, ok as is if they are rejected by author :+1:

:-1:


Add .swiftpm and Package.resolved to gitignore

We shouldn't be tracking these for SwiftPM unless really need to.

@swift-ci smoke test


feat: add volta as node-version-file

Description:
Updates node-version-file to accept input volta. This can be important to repositories that use Volta as Node.js version management. Unlike other version managers, Volta places its versioning within package.json. Feel free to look at the format within the test package.json.
Check list:

[x] Mark if documentation changes are required.
[x] Mark if tests were added or updated to cover the changes.

Hello @jef. Thank you for your pull request. Could you please run the npm run format command ? Besides, do we need to declare package.json as possible input ?

Besides, do we need to declare package.json as possible input

great question. i also wasn't sure about this. i'm not sure if other projects use package.json for storing node.js versions. if so, then perhaps this could be more extendable.

Thank you for reply @jef. I think we can remove package.json from this pull request because we have pull requests with adding support for package.json engine.

pull requests with adding support for package.json engine.

ah, yes. i see that in #485. in this case, i believe there need some logic update into include volta.
should i wait until #485 is merged and then i proceed with mine?

Hi @jef, could you please update your branch from main and resolve conflicts?

Sure thing. I'll be back from vacation next week.

Should be all good now @vsafonkin. Thanks!

I've realized that the documentation for package.json is missing. Should I add it in here?

Hello @jef. Thank you for your suggestion. We would appreciate if you add this to the documentation, but if you want, we will do it on our side. Thank you!

Alright, I've added in the documentation! Everything seems good from my end. Let me know if you need anything extra.

Hi @jef, you need to resolve conflicts according #553 Thank you in advance!

Hi @jef, you need to resolve conflicts according #553 Thank you in advance!

Not a problem! Should be all sorted. I removed the try/catch on the latter half of parseNodeVersionFile only because it was throwing an error locally. Seemed better this way. I can revert if necessary.
Thanks!

@vsafonkin, anything else you need before getting this in? Thanks!

Hello @jef. Sorry for the late response. Could you please e2e tests for volta ?

Hi @jef!
Just a gentle ping - we would like to know if you are planning to implement e2e tests here.
Thank you in advance!

Sorry about that. Yes, I can implement some e2e tests. Is that going to be outside of the __tests__/installer.test.ts file?

Hello @jef!
Thanks for the quick response!
According to our contributor's guide, end-to-end tests are in the workflows folder, particularly in the versions.yml file.

Hi @e-korolevskii, I believe I implemented something that should work. I can also combine it with the previous step if that makes more sense.
Thanks!

Hi @jef!
Now it looks good and I think we are ready to merge it.
I just wanted to thank you again for your contribution!

Thanks for walking me through @e-korolevskii 😊


heatseeker: fix finding stty

Otherwise this crashes at runtime.
I've opened https://github.com/rschmitt/heatseeker/issues/42 upstream.
@bhipple this is the fix from https://github.com/NixOS/nixpkgs/pull/80539 that's still needed.

Motivation for this change
Things done

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

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

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

Rats, I pulled out this patch from another commit and missed a bit, sorry!

Fixed!

Gentle ping.

ping @bhipple

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/141

Clean improvement, well-executed with a reference to an upstream issue :+1:
Sorry you had to wait so long.


[Task] Add drag resolution to task resize

Add drag resolution to task resize in both ways

Not to be implemented right now, to allow manual resize and adjust.


pointing option for messages (other than labels)

this is an FR to support "pointing" left/right for a Message as well.
The use case would be chat messages.

I'm afraid semantic doesn't have floating helpers, you'll have to write the css yourself.

I did. In fact, I used http://www.cssarrowplease.com/  to generate the following code and applied to a message div but it didn't work.
.arrow_box_left {
	position: relative;
	background: #FFF8DB;
	border: 1px solid #B58105;
}
.arrow_box_left:after, .arrow_box_left:before {
	right: 100%;
	top: 50%;
	border: solid transparent;
	content: " ";
	height: 0;
	width: 0;
	position: absolute;
	pointer-events: none;
}

.arrow_box_left:after {
	border-color: rgba(255, 248, 219, 0);
	border-right-color: #FFF8DB;
	border-width: 30px;
	margin-top: -30px;
}
.arrow_box_left:before {
	border-color: rgba(181, 129, 5, 0);
	border-right-color: #B58105;
	border-width: 31px;
	margin-top: -31px;
}


Authenticated Flickr bridge support

It would be nice to have an authenticated Flickr bridge to be able to see private account photos and mature photos which Flickr doesn't propose yet.

In general being able to access authenticated contents is a good idea, but there is a very high chance for hosts of RSS-Bridge to collect your authentication information without you knowing it. This is why bridges don't support authentication and we don't accept PRs for that.
That being said, we already have a small corner in the Wiki with a few bridges specifically build to access contents via proprietary APIs which do require authentication. That way, if you host your own private server, you can put them in the bridges folder to utilize their features.
This doesn't solve your issue right now, as there is no Flickr bridge supporting authentication yet. I might look into it if I have more time to space, but no promises to when that might happen. If anyone is interested in picking this up, please feel free to do so. Just be aware that it won't get merged into master.


init() got multiple values for argument 'and percentage'

when I use
clr_triangular = OneCycleLR(NUM_SAMPLES, NUM_EPOCHS, BATCH_SIZE, MAX_LR, end_percentage=0.2, scale_percentage=0.2)
in your plot_clr.py
I got the following errors:
init() got multiple values for argument 'and percentage'
But if I use
clr_triangular = OneCycleLR(max_lr=0.02, maximum_momentum=0.9, verbose=True)
it works well.

seems the README is a little outdated. @titu1994


Fix handling of JS keyword for imported functions, types and statics, and when causing invalid code gen

Fixes #4317
Fixes #4328
As I said in #4317, keyword handling was kind of a mess. Keywords are now handled correctly for both imports and exports AFAICT.
Changes:

Stricter parsing for js_namespace. Now, the first identifier cannot be a JS keyword and empty lists are no longer allowed. This is not a breaking change, because keyword identifiers resulted in invalid JS code gen, and empty lists crashed the CLI.
Keywords are now generally allowed for imported functions, types, and statics. However, they will cause an error if the resulting JS code gen would be invalid.
Keywords are now always correctly escaped when used as function parameters.
Exported classes and enums named after keywords now result in an error instead of invalid code gen. Since all JS keywords are lower-case, I don't export anyone to have used keywords for them anyway.
I fixed the keyword list. Whoever decided that we don't need to check Rust keywords forgot that raw identifiers and js_name exist. The list now includes all JS keywords.

About the keyword list update: I also add keywords that are only keywords in strict mode. JavaScript has 2 execution modes: strict mode and sloppy mode. Sloppy mode is the legacy mode and shouldn't be used anymore. The key takeaway here is that we should only generate code that works in strict mode, so we must not allow identifiers that are keywords in strict mode. This is important, because all JS files that use ESM (import/export) implicitly use strict mode. I don't want WBG to be in the situation where it only generates valid JS for some CLI targets.
Lastly, await. await is a keyword ONLY is async functions in JS. So it can generally be used as an identifier, but this can cause problems. If a class is named await, then this class cannot be used inside async functions. It's a weird edge case, and I'm not sure whether we should consider await a reserved keyword too. Right now, I just allowed it.

Done. Thanks for the suggestions!

Thanks for the prompt fix - much appreciated!


[feat] setting window

Describe the problem
Need a pref window with tabbed ui
It just finish the expierience.
Hard to replicate in react which i did it still feels not native enough
Describe the solution you'd like
Build a custom window like
https://github.com/sindresorhus/Settings
If possible at all
Alternatives considered
Using react for the content in the window mimic the ui
Not good enough
Additional context
Would like to onow of this is possible at all

This is outside the scope of tauri, and better suited to be a community project.


Desync, Timestamp for this request was 1000ms ahead of the server's time

Java version :
C:\Program Files\Java\jdk1.8.0_152\bin>java.exe -version
java version "1.8.0_152"
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)
Quite a common error, here is the snippet of code I am using to compare the time between my computer and binance API :
package laby.java;

import com.binance.api.client.BinanceApiClientFactory;
import com.binance.api.client.BinanceApiRestClient;

public class Main {

    private static final String APIKEY = "key";
    private static final String APISECRET = "secret";

    public static void main(String[] args) {

        BinanceApiClientFactory factory = BinanceApiClientFactory.newInstance(APIKEY, APISECRET);
        BinanceApiRestClient client = factory.newRestClient();

        while (true) {
            // Checking time between
            Long clientTime = java.lang.System.currentTimeMillis();
            Long serverTimerTime = client.getServerTime();
            System.out.println("Times : client[" + clientTime + "] server[" + serverTimerTime + "] diff[" + (serverTimerTime - clientTime) + "]");
        }
    }

}

Results:
Times : client[1514132675503] server[1514132675624] diff[121]
Times : client[1514132677246] server[1514132676946] diff[-300]
Times : client[1514132678541] server[1514132677226] diff[-1315]
Times : client[1514132678820] server[1514132677505] diff[-1315]
Times : client[1514132679098] server[1514132677788] diff[-1310]
Times : client[1514132679420] server[1514132678111] diff[-1309]
Times : client[1514132679729] server[1514132678414] diff[-1315]
Times : client[1514132680007] server[1514132678698] diff[-1309]
Times : client[1514132680293] server[1514132678983] diff[-1310]
Times : client[1514132680579] server[1514132679265] diff[-1314]
Times : client[1514132680858] server[1514132679544] diff[-1314]
Times : client[1514132681137] server[1514132679823] diff[-1314]
Times : client[1514132681417] server[1514132680107] diff[-1310]

Process finished with exit code 1

Registry setting is set to update time each ten minutes, it doesn't change anything:

For your information, I updated the clock time before each attempt :

I am loosing around 1.2 seconds somewhere, and I don't know where

I put a PR up for this #11. Its been working for a couple days so I think its safe. Not sure if its the best implementation though. Check it out if you want.

@JamesBarnes88 many thanks for your PR, I'll review it in the upcoming days. The idea looks good, and it does solve the "problem", although I'm afraid it also hides away the fact that the client time is not ntp synchronised, as it should. This can have some consequences when reading out times returned by the API.

The thing is, even after manually synchronizing with a NTP server, the error is still there. And it's always around 1200 ms :<

@joaopsilva Hey thanks for some clarification around the problem. Didn't know about NTP and SNTP before this. My question is if we use an NTPClient or SNTPClient implementation should this set my system time to sync with binance's server? Reading their api document it doesn't say that they use a specific ntp server. So the time may be managed by them.
So what if I also needed to sync with a different exchange's server while running both apps simultaneously? Maybe I misunderstood how that part of NTP works. Sorry for all the questions.

I just solve this problem using getServerTime() and gap time
for example
before
@Override
public Account getAccount() {
    return getAccount(BinanceApiConstants.DEFAULT_RECEIVING_WINDOW, System.currentTimeMillis());
}

after
  @Override
  public Account getAccount() {
	  long start = System.currentTimeMillis();
	  long serverTime = this.getServerTime();
	  long end = System.currentTimeMillis();
	  long gap = start - end;
	  return getAccount(BinanceApiConstants.DEFAULT_RECEIVING_WINDOW, serverTime + gap);
  }

Closing as this issue is only related to local machines with an unsynchronized clock. In any case, there's a workaround, as mentioned by @SungMinHong .


Ghost text completion suggestions push cursor to end of suggestion

Using copilot completions in the latest VS Code insiders, I see the cursor being pushed to after the suggested text. This makes it very difficult to work with the text while passive completions are suggested.

@hediet is it possible to differentiate between an inline completion and inlay hint in the editor? maybe we could have different behavior in different cases?


Deploying in prod with svg-sprite-loader

I use svg-sprite-loader (last version) in a react app with extrac: true option.
The process build generates the files excactly where I want it. Similar like this: https://github.com/doug2k1/react-svg-icon
My problem is that altough in dev more, the  full svg is included by the default in the body of the app, when used in prod the svg is not there, so usting svg tags referencing each id would not work.
Question: is there a way that the loader will add js script to insert the svg in the body, or should I do it by my self?

Not sure that I understand you problem, I've launched your demo like so NODE_ENV=production webpack-dev-server -p and all icons are rendered correctly.

True. in dev mode it works great: it shows up in my dom. My problem is when I build for prod it and extracted as a file, there is no reference in dom about it. Do i have to put it myself?

I see that you use prebuilt svg sprite - icons.svg. This loader was made to generate sprites dynamically from single SVG import (e.g. import './img.svg'). I don't know why it works in your case, but it shouldn't :)

I saw that, but it was also good for injecting into the dom the svg :)

Damn, that post pushed me in the wrong direction.
Just to confirm: https://www.webdevdrops.com/build-an-svg-icon-component-with-react-de9db211ebd6/
This is not how you are supposed to use svg-sprite loader right?


Change background

Hi, thanks for module! It will be nice if there in config will be some UI configs such as background Image , color, something like that

Hi @Saulenco, thanks, this is a great idea. Lately, I have not had much time to work on it, I hope I can add this new feature soon.

Hi @Saulenco, finally customization is available https://github.com/oijusti/react-native-firebaseui-auth#ui-customization

Hi @oijusti i see that only the android has the support for background and logo, it is possible to add for iOS also ?

hi @Saulenco, right now for iOS the only way to do it is editing the FUICustomAuthPickerViewController.xib file directly from XCode. You can change the background and add the logo using the tools that XCode provide.


Feature/issue 244 automatically add recommended tasks

Regarding your UX comment: I agree that there should be a way to see recommended tasks, but I think that falls outside of what this dialog is responsible for, so it should be addressed in a later PR. What do you think of these thoughts here https://github.com/pg-irc/pathways-frontend/issues/267 "?

I'm not sure I feel the need for the overhaul (#267). My main concern is the count shows x amount of tasks recommended but many of those you'll never be able to add to your list if you willingly or accidentally clicked "No" on the dialog. You're right, currently it falls out of this dialog's responsibility but maybe things should be rejigged ...

We discussed this in sprint planning and decided seeing as recommended tasks are still kicking around we're going to keep this as is.

I'll be taking a look at the styling issues.


Replace old debug-code with log messages

Remove already inactive "print()" code and replace with log messages when usefull.

done


[BUG] Stage 2 works but Stage 3 reports the error while loss backward

Describe the bug
A clear and concise description of what the bug is.
The training runs smoothly with the setting zero stage 2. However, when I attempted to configure it with zero stage  = 3, an error was encountered during the execution of the loss backward propagation process:
model.backward(divided_loss_laion)
  File "/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/deepspeed/utils/nvtx.py", line 15, in wrapped_fn
        self.loss_scaler.backward(loss.float(), retain_graph=retain_graph)ret_val = func(*args, **kwargs)

  File "/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/deepspeed/runtime/fp16/loss_scaler.py", line 63, in backward
  File "/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/deepspeed/runtime/engine.py", line 1923, in backward
    scaled_loss.backward(retain_graph=retain_graph)
  File "/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/torch/_tensor.py", line 487, in backward
    torch.autograd.backward(
  File "/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/torch/autograd/__init__.py", line 200, in backward
    Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
RuntimeError: The size of tensor a (0) must match the size of tensor b (8192) at non-singleton dimension 1
    self.optimizer.backward(loss, retain_graph=retain_graph)
  File "/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/deepspeed/utils/nvtx.py", line 15, in wrapped_fn
    ret_val = func(*args, **kwargs)
  File "/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/deepspeed/runtime/zero/stage3.py", line 2080, in backward
    self.loss_scaler.backward(loss.float(), retain_graph=retain_graph)
  File "/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/deepspeed/runtime/fp16/loss_scaler.py", line 63, in backward
    scaled_loss.backward(retain_graph=retain_graph)
  File "/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/torch/_tensor.py", line 487, in backward
    torch.autograd.backward(
  File "/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/torch/autograd/__init__.py", line 200, in backward
    Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
RuntimeError: The size of tensor a (0) must match the size of tensor b (8192) at non-singleton dimension 1

The error is very strange: 1) Stage 2 works, but stage 3 reports the error; 2) The error occurred while executing loss backward, but the backward process rarely reports errors.
ds_report output
23-10-02 22:37:29,462] [INFO] [real_accelerator.py:158:get_accelerator] Setting ds_accelerator to cuda (auto detect)
--------------------------------------------------
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
 [WARNING]  async_io: please install the libaio-dev package with apt
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
async_io ............... [NO] ....... [NO]
fused_adam ............. [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
 [WARNING]  sparse_attn requires a torch version >= 1.5 and < 2.0 but detected 2.0
 [WARNING]  using untested triton version (2.0.0), only 1.0.0 is known to be compatible
sparse_attn ............ [NO] ....... [NO]
spatial_inference ...... [NO] ....... [OKAY]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ............... ['/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/torch']
torch version .................... 2.0.1
deepspeed install path ........... ['/home/yongqi/miniconda3/envs/openflamingo/lib/python3.9/site-packages/deepspeed']
deepspeed info ................... 0.10.3, unknown, unknown
torch cuda version ............... 11.7
torch hip version ................ None
nvcc version ..................... 11.3
deepspeed wheel compiled w. ...... torch 2.0, cuda 11.7
shared memory (/dev/shm) size .... 251.76 GB

Additional context
Add any other context about the problem here.

@liyongqi67 Can you provide a small script to reproduce the error?

Closing due to lack of response.


Add basic-commands folder as markdown format

Overview
Description
Some documentation for FAWE from the basic-commands folder
Submitter Checklist

[X] Make sure you are opening from a topic branch (/feature/fix/docs/ branch (right side)) and not your main branch.
[X] Ensure that the pull request title represents the desired changelog entry.
[X] New public fields and methods are annotated with @since TODO.
[X] I read and followed the contribution guidelines.

Hey @TheMeinerLP,
any chance you can take a look at my feedback?

Yeah ofc

Hey @TheMeinerLP,
any chance you can take a look at my feedback?

Hope this is now okay and useful for you