Cosmos / ReadItemAsync -> much longer response time than it should

I'm not 100% sure if the problem is the code, some missing configuration, or whatever.
I have a very simple query:
SELECT * FROM c where c.id = 'Profile:123'
which processing in data explorer, has the following performance parameters:
Index lookup time 0.17 ms
Document load time 0.030000000000000002 ms
Query engine execution time 0.02 ms
System function execution time 0 ms
User defined function execution time 0 ms
Document write time 0 ms

but the response time of my api is very slow (it is far from this data explorer performance). I'm using azure functions, and I did several tests to try to find the source of the problem. the problem I found is precisely the cosmos api:
the structure of my repository:
public Container Container { get; private set; }
public CosmosRepository(IConfiguration config)
{
    var connString = config.GetValue<string>("RepositoryOptions_CosmosConnectionString");
    var databaseId = config.GetValue<string>("RepositoryOptions_DatabaseId");
    var containerId = config.GetValue<string>("RepositoryOptions_ContainerId");

    var _client = new CosmosClient(connString, new CosmosClientOptions()
    {
        SerializerOptions = new CosmosSerializationOptions()
        {
            PropertyNamingPolicy = CosmosPropertyNamingPolicy.CamelCase
        }
    });

    Container = _client.GetContainer(databaseId, containerId);
}

my get method:
public async Task<T> Get<T>(string id, string partitionKeyValue, CancellationToken cancellationToken) where T : CosmosBase
{
    try
    {
        Stopwatch sw = Stopwatch.StartNew();
        var response = await Container.ReadItemAsync<T>(id, new PartitionKey(partitionKeyValue), null, cancellationToken);
        throw new Exception(sw.Elapsed.ToString());

        //return response.Resource;
    }
    catch (CosmosException ex) when (ex.StatusCode == System.Net.HttpStatusCode.NotFound)
    {
        return null;
    }
}

it is taking an average of 1.5 seconds to execute this code. even with several in sequence, not just the first.
is there something wrong with this cosmos api project? am i doing something wrong? is there any configuration i should be doing?

Please follow the public guides for slow requests: https://docs.microsoft.com/en-us/azure/cosmos-db/troubleshoot-dot-net-sdk-slow-request
You need to collect and evaluate the Diagnostics.

@drma-dev Based on the article, when looking at latency, how are you measuring it? Are you measuring 1 operation or the P99 (99 percentile) over an hour?
Troubleshooting 1 operation is not worth it, as the service has a P99 latency guarantee, not 100%. How many operations in an hour have high latency versus how many have acceptable latency? If the volume is high, we can help if you share some diagnostics here (assuming you already verified all the conditions in the article under "Application Design").

@ealsur
I'm still developing, that is, only I'm accessing it. there is no way to reach any limit.
It's not a structure problem either. I made a project from scratch, just to call this method exclusively.

Can you clarify then what is the scope of this Issue? If you are running code from your machine to a database that is in the cloud, the latency will never be ideal, that is completely expected.
The metrics you are showing from the Portal are related to a Query and that is the time the Query took executing on the database (service), the time you are measuring in your code is the time that operation took from your machine, sending the request over the network, waiting for it to be processed, and then receiving the response. Because of the natural geographical distance and different networks, that latency will never be good.
Also, there is the cold-start factor, all connections need to be opened, so if you are simply doing 1 operation, the latency of that operation is not meaningful, that does not represent a live system or production application. Normally you would perform performance/latency analysis over a production application that is already deployed and follows all the requirements (Application Design section) for latency to be optimal.
If you are developing an application from scratch, https://docs.microsoft.com/en-us/azure/cosmos-db/sql/conceptual-resilient-sdk-applications is also a good read to keep in mind.

so I'm comparing it with data explorer. if it were for "being cold", it would be slow in both cases. I also know that they give an acceptable delay because I'm accessing an external api. but something that runs within 100 milliseconds would not take 2 seconds to respond. something is wrong.

I created an account without being serverless, just to test. that's not it. it took the same thing: 1.8 seconds.

{
"children":
    [
        {
        "children":
            [
                {
                "duration in milliseconds": 6960131.0,
                "id": "3e507fb2-f033-4b3c-9a0c-166c946e0cd7",
                "name": "Waiting for Initialization of client to complete",
                "start time": "04:04:44:275"
                },
                {
                "children":
                    [
                        {
                        "children":
                            [
                                {
                                "children":
                                    [
                                        {
                                        "children":
                                            [
                                                {
                                                "data":
                                                    {
                                                    "Client Side Request Stats":
                                                        {
                                                        "AddressResolutionStatistics":
                                                            [
                                                                {
                                                                "EndTimeUTC": "2022-09-27T16:04:45.8117581Z",
                                                                "StartTimeUTC": "2022-09-27T16:04:45.7394518Z",
                                                                "TargetEndpoint": "https://cosmos-teste-dhiogo-brazilsouth.documents.azure.com//addresses/?$resolveFor=dbs%2fO6pCAA%3d%3d%2fcolls%2fO6pCALz8-4k%3d%2fdocs&$filter=protocol eq rntbd&$partitionKeyRangeIds=0"
                                                                }
                                                            ],
                                                        "ContactedReplicas":
                                                            [
                                                                {
                                                                "Count": 1,
                                                                "Uri": "rntbd://cdb-ms-prod-brazilsouth1-be12.documents.azure.com:14304/apps/a79a6295-573f-440a-ae6e-cba1cf309657/services/8ffc7fc0-b3cd-4a14-bfb3-329112193c48/partitions/f68904f7-7130-4776-9039-45b73bec0e5f/replicas/133087611347997962s/"
                                                                }
                                                            ],
                                                        "FailedReplicas":
                                                            [
                                                            ],
                                                        "HttpResponseStats":
                                                            [
                                                                {
                                                                "ActivityId": "e2b3d7af-74aa-4dd6-9754-f34063aa1b26",
                                                                "DurationInMs": 5010322.0,
                                                                "HttpMethod": "GET",
                                                                "RequestUri": "https://cosmos-teste-dhiogo-brazilsouth.documents.azure.com/dbs/database/colls/container",
                                                                "ResourceType": "Collection",
                                                                "StartTimeUTC": "2022-09-27T16:04:45.0231613Z",
                                                                "StatusCode": "OK"
                                                                },
                                                                {
                                                                "ActivityId": "44494f65-6906-4085-a11b-f63c2562ae88",
                                                                "DurationInMs": 807373.0,
                                                                "HttpMethod": "GET",
                                                                "RequestUri": "https://cosmos-teste-dhiogo-brazilsouth.documents.azure.com/dbs/O6pCAA==/colls/O6pCALz8-4k=/pkranges",
                                                                "ResourceType": "PartitionKeyRange",
                                                                "StartTimeUTC": "2022-09-27T16:04:45.5588426Z",
                                                                "StatusCode": "OK"
                                                                },
                                                                {
                                                                "ActivityId": "9e9b9b4c-6f7e-4f26-963c-186d9f222fa6",
                                                                "DurationInMs": 720994.0,
                                                                "HttpMethod": "GET",
                                                                "ReasonPhrase": "Not Modified",
                                                                "RequestUri": "https://cosmos-teste-dhiogo-brazilsouth.documents.azure.com/dbs/O6pCAA==/colls/O6pCALz8-4k=/pkranges",
                                                                "ResourceType": "PartitionKeyRange",
                                                                "StartTimeUTC": "2022-09-27T16:04:45.6489707Z",
                                                                "StatusCode": "NotModified"
                                                                },
                                                                {
                                                                "ActivityId": "b9b32609-4003-4ad4-86eb-221994c70ebc",
                                                                "DurationInMs": 698931.0,
                                                                "HttpMethod": "GET",
                                                                "RequestUri": "https://cosmos-teste-dhiogo-brazilsouth.documents.azure.com//addresses/?$resolveFor=dbs%2fO6pCAA%3d%3d%2fcolls%2fO6pCALz8-4k%3d%2fdocs&$filter=protocol eq rntbd&$partitionKeyRangeIds=0",
                                                                "ResourceType": "Document",
                                                                "StartTimeUTC": "2022-09-27T16:04:45.7409410Z",
                                                                "StatusCode": "OK"
                                                                }
                                                            ],
                                                        "Id": "AggregatedClientSideRequestStatistics",
                                                        "RegionsContacted":
                                                            [
                                                            ],
                                                        "StoreResponseStatistics":
                                                            [
                                                                {
                                                                "LocationEndpoint": "https://cosmos-teste-dhiogo-brazilsouth.documents.azure.com/",
                                                                "OperationType": "Read",
                                                                "ResourceType": "Document",
                                                                "ResponseTimeUTC": "2022-09-27T16:04:46.4907384Z",
                                                                "StoreResult":
                                                                    {
                                                                    "ActivityId": "b9b32609-4003-4ad4-86eb-221994c70ebc",
                                                                    "BELatencyInMs": "0.233",
                                                                    "CurrentReplicaSetSize": -1,
                                                                    "CurrentWriteQuorum": -1,
                                                                    "GlobalCommittedLSN": 3,
                                                                    "IsValid": true,
                                                                    "ItemLSN": 3,
                                                                    "LSN": 3,
                                                                    "NumberOfReadRegions": 0,
                                                                    "PartitionKeyRangeId": "0",
                                                                    "QuorumAckedLSN": -1,
                                                                    "RequestCharge": 105.0,
                                                                    "RetryAfterInMs": null,
                                                                    "SessionToken": "-1#3",
                                                                    "StatusCode": "Ok",
                                                                    "StorePhysicalAddress": "rntbd://cdb-ms-prod-brazilsouth1-be12.documents.azure.com:14304/apps/a79a6295-573f-440a-ae6e-cba1cf309657/services/8ffc7fc0-b3cd-4a14-bfb3-329112193c48/partitions/f68904f7-7130-4776-9039-45b73bec0e5f/replicas/133087611347997962s/",
                                                                    "SubStatusCode": "Unknown",
                                                                    "TransportException": null,
                                                                    "transportRequestTimeline":
                                                                        {
                                                                        "connectionStats":
                                                                            {
                                                                            "callsPendingReceive": 0,
                                                                            "lastReceive": "2022-09-27T16:04:46.3854358Z",
                                                                            "lastSend": "2022-09-27T16:04:46.3062044Z",
                                                                            "lastSendAttempt": "2022-09-27T16:04:46.3057703Z",
                                                                            "waitforConnectionInit": "True"
                                                                            },
                                                                        "requestSizeInBytes": 491,
                                                                        "requestTimeline":
                                                                            [
                                                                                {
                                                                                "durationInMs": 39646.0,
                                                                                "event": "Created",
                                                                                "startTimeUtc": "2022-09-27T16:04:45.8350017Z"
                                                                                },
                                                                                {
                                                                                "durationInMs": 5512382.0,
                                                                                "event": "ChannelAcquisitionStarted",
                                                                                "startTimeUtc": "2022-09-27T16:04:45.8389663Z"
                                                                                },
                                                                                {
                                                                                "durationInMs": 136458.0,
                                                                                "event": "Pipelined",
                                                                                "startTimeUtc": "2022-09-27T16:04:46.3902045Z"
                                                                                },
                                                                                {
                                                                                "durationInMs": 822283.0,
                                                                                "event": "Transit Time",
                                                                                "startTimeUtc": "2022-09-27T16:04:46.4038503Z"
                                                                                },
                                                                                {
                                                                                "durationInMs": 304.0,
                                                                                "event": "Received",
                                                                                "startTimeUtc": "2022-09-27T16:04:46.4860786Z"
                                                                                },
                                                                                {
                                                                                "durationInMs": 0,
                                                                                "event": "Completed",
                                                                                "startTimeUtc": "2022-09-27T16:04:46.4891186Z"
                                                                                }
                                                                            ],
                                                                        "responseBodySizeInBytes": 1716,
                                                                        "responseMetadataSizeInBytes": 416,
                                                                        "serviceEndpointStats":
                                                                            {
                                                                            "inflightRequests": 1,
                                                                            "openConnections": 1
                                                                            }
                                                                        },
                                                                    "UsingLocalLSN": true
                                                                    }
                                                                }
                                                            ]
                                                        }
                                                    },
                                                "duration in milliseconds": 15232321.0,
                                                "id": "88188bd5-3fc5-4736-a229-be666f522b5c",
                                                "name": "Microsoft.Azure.Documents.ServerStoreModel Transport Request",
                                                "start time": "04:04:44:983"
                                                }
                                            ],
                                        "duration in milliseconds": 1530618.0,
                                        "id": "ffaf65cb-1dc0-443c-9520-991b5b571f97",
                                        "name": "Microsoft.Azure.Cosmos.Handlers.TransportHandler",
                                        "start time": "04:04:44:976"
                                        }
                                    ],
                                "duration in milliseconds": 15312392.0,
                                "id": "75ada5f6-c7b6-45d3-9d1e-a13c4bc7b074",
                                "name": "Microsoft.Azure.Cosmos.Handlers.RouterHandler",
                                "start time": "04:04:44:976"
                                }
                            ],
                        "duration in milliseconds": 15348012.0,
                        "id": "4eb626e8-164a-4c97-af83-bda2fe5769bb",
                        "name": "Microsoft.Azure.Cosmos.Handlers.RetryHandler",
                        "start time": "04:04:44:973"
                        }
                    ],
                "data":
                    {
                    "System Info":
                        {
                        "systemHistory":
                            [
                                {
                                "cpu": 1328.0,
                                "dateUtc": "2022-09-27T16:04:44.8919849Z",
                                "memory":<PHONE_NUMBER>.0,
                                "numberOfOpenTcpConnection": 0,
                                "threadInfo":
                                    {
                                    "availableThreads": 32766,
                                    "isThreadStarving": "no info",
                                    "maxThreads": 32767,
                                    "minThreads": 16
                                    }
                                }
                            ]
                        }
                    },
                "duration in milliseconds": 15355656.0,
                "id": "8b953126-1e5c-411a-be83-7581c64d7b10",
                "name": "Microsoft.Azure.Cosmos.Handlers.DiagnosticsHandler",
                "start time": "04:04:44:972"
                }
            ],
        "duration in milliseconds": 22829562.0,
        "id": "552a9445-9f13-4529-8269-fe0252a0eed3",
        "name": "Microsoft.Azure.Cosmos.Handlers.RequestInvokerHandler",
        "start time": "04:04:44:225"
        },
        {
        "duration in milliseconds": 583441.0,
        "id": "26fc2d34-7a41-4d6f-bb48-3a03939eecc5",
        "name": "Response Serialization",
        "start time": "04:04:46:509"
        }
    ],
"data":
    {
    "Synchronization Context": "Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext"
    },
"duration in milliseconds": 23475393.0,
"id": "68e8f90a-bf61-4b6c-af76-a9effacd53f4",
"name": "ReadItemAsync",
"start time": "04:04:44:220",
"Summary":
    {
    "DirectCalls":
        {
        "(200, 0)": 1
        },
    "GatewayCalls":
        {
        "(200, 0)": 3,
        "(304, 0)": 1
        }
    }
}

that solved it for me.
that solved it for me.

You cannot compare with Data Explorer. How are you measuring the latency of your browser? The numbers you are seeing in Data Explorer are just the Backend Latency, not end to end (the time your browser took to start the request and get the response).
Your diagnostics show a cold client, we can see the client is initializing (https://learn.microsoft.com/en-us/azure/cosmos-db/sql/sql-sdk-connection-modes#routing):
"name": "Waiting for Initialization of client to complete",
....
....

"HttpResponseStats":
                                                            [
                                                                {
                                                                "ActivityId": "e2b3d7af-74aa-4dd6-9754-f34063aa1b26",
                                                                "DurationInMs": 5010322.0,
                                                                "HttpMethod": "GET",
                                                                "RequestUri": "https://cosmos-teste-dhiogo-brazilsouth.documents.azure.com/dbs/database/colls/container",
                                                                "ResourceType": "Collection",
                                                                "StartTimeUTC": "2022-09-27T16:04:45.0231613Z",
                                                                "StatusCode": "OK"
                                                                },
                                                                {
                                                                "ActivityId": "44494f65-6906-4085-a11b-f63c2562ae88",
                                                                "DurationInMs": 807373.0,
                                                                "HttpMethod": "GET",
                                                                "RequestUri": "https://cosmos-teste-dhiogo-brazilsouth.documents.azure.com/dbs/O6pCAA==/colls/O6pCALz8-4k=/pkranges",
                                                                "ResourceType": "PartitionKeyRange",
                                                                "StartTimeUTC": "2022-09-27T16:04:45.5588426Z",
                                                                "StatusCode": "OK"
                                                                },
                                                                {
                                                                "ActivityId": "9e9b9b4c-6f7e-4f26-963c-186d9f222fa6",
                                                                "DurationInMs": 720994.0,
                                                                "HttpMethod": "GET",
                                                                "ReasonPhrase": "Not Modified",
                                                                "RequestUri": "https://cosmos-teste-dhiogo-brazilsouth.documents.azure.com/dbs/O6pCAA==/colls/O6pCALz8-4k=/pkranges",
                                                                "ResourceType": "PartitionKeyRange",
                                                                "StartTimeUTC": "2022-09-27T16:04:45.6489707Z",
                                                                "StatusCode": "NotModified"
                                                                },
                                                                {
                                                                "ActivityId": "b9b32609-4003-4ad4-86eb-221994c70ebc",
                                                                "DurationInMs": 698931.0,
                                                                "HttpMethod": "GET",
                                                                "RequestUri": "https://cosmos-teste-dhiogo-brazilsouth.documents.azure.com//addresses/?$resolveFor=dbs%2fO6pCAA%3d%3d%2fcolls%2fO6pCALz8-4k%3d%2fdocs&$filter=protocol eq rntbd&$partitionKeyRangeIds=0",
                                                                "ResourceType": "Document",
                                                                "StartTimeUTC": "2022-09-27T16:04:45.7409410Z",
                                                                "StatusCode": "OK"
                                                                }
                                                            ],

This is expected, as I said, you need to measure performance across P99, this is a single request after the client instance is created.
 But again, when you are measuring performance and latency, you need to look at P99, not 1 request.
If you look closely to your diagnostics:
{
                                                                                "durationInMs": 822283.0,
                                                                                "event": "Transit Time",
                                                                                "startTimeUtc": "2022-09-27T16:04:46.4038503Z"
                                                                                },

You see a very high transit time (https://docs.microsoft.com/en-us/azure/cosmos-db/sql/troubleshoot-dot-net-sdk-slow-request?tabs=cpu-new#rntbdRequestStats) which means, your problem is the network. If you are doing this request from your local machine, this does not represent a real production scenario, this latency is huge, that is a networking issue you need to look into.

ok, I understand that it's only a problem with the first query (I'm almost sure it's for any query. I'll see if it's a problem with my architecture).
anyway, this instance initializer uses await, which I can't use in the class's constructor.

note: as I use azure functions, I don't think the instance stays active, so I'll have to force initialization. or am i wrong?

Depends on the Azure Function plan, they have plans that keep the instance running.
If you are on Consumption Plan, then yes, you will pay the initialization cost for the first request always, that is by design. Any database client needs to establish connections at some point.
If you are on Consumption Plan also, using CreateAndInitializeAsync won't make much difference either, because anyway you are creating the client instance the moment the instance comes up, which is the moment you need to use it. CreateAndInitializeAsync makes a difference when the initialization of the application happens when the instance starts up and you are warming up the machine (you have other initialization logic too).
For a complete serverless scenario, Azure Functions on Consumption Plan, then yes, you will always end up paying the initialization cost, there is no way around it. Make sure you are reducing all possible reasons to have even more latency (Singleton client, running on the same region, regional preference correctly set on the client, etc), but you cannot remove the initialization cost (whatever that may be) because you are always creating a new client if the AF instance gets shuts down, there is simply no instance that can maintain those connections established.

so I use the static web app, which has the azure functios built in (yes, I believe it's the one that initializes every time it's called).
So, there's nothing that can solve my life? do i have to use some sort of cache?

found out.
azure functions keep instances for at least 20 minutes, even if they are serveless.
So, I thought: so the problem is really with me.
services.AddScoped<IRepository>(func =>
{
    return new CosmosRepository(config);
});

the instance of my repository was as scoped, there it was forcing to initialize every time. I switched to singleton.

Correct, we recommend in those articles I linked that the client should be Singleton. Glad you found the root cause.


fix: use file data register i18n file to provider

What this PR does / why we need it:
fix: use file data register i18n file to provider
Which issue(s) this PR fixes:
Fixes #
Specified Reviewers:
/assign @your-reviewer

/approve


Actions Not Successfully Stored

@eltoroit, I have found an issue with storable actions not working correctly due to some logic in the ETLC_ApexBridgeHelper.js file. Because of the order in the logic, the action does not get successfully marked as a storable action. I can add that and create a "pull request". Just wanted to check and see if that is how you normally handle changes to the project. Thank you!

Please create a pull request, I would like to see what are the changes you are proposing.

@eltoroit Thank you. Would you prefer that I push changes to my forked jr. branch and then create pull request to merge forked jr. into master?


API v1 discussion

Here's a central issues to discuss the API changes that need to happen before we publish API v1.

Background: right now all API calls are handled by calls from api.ldjam.com/vx/. /vx/ is the experimental API, which means you shouldn't expect API changes to be consistent. That said, after 2 events, folks have started using our API, so we need to start promising some consistency.
So that means promoting some of the API work to API v1.
Before we do that though, there are things that are lingering, things that I want to do (and things that have been recommended to me). So this issue is about discussing what those things are. Deciding what's left before we crises API v1.

Some rough thoughts on API changes:

node and note love requests should be POST (They have side effects)
I think it might make sense to fragment off love/star and other kinds of markers into a separate endpoint, something like /mark/star/add/node/, /mark/love/remove/note/
I want to be able to fetch a feed that mixes nodes and notes (e.g. get my recent posts and comments)
Need better querying for individual comments, get user comments, stuff like this.
We talked some about unifying feed into a new endpoint with common code to deal with feed options, and then minimal providers to generate feeds for different object types.

General
I would like to see code like this
		$Node.Get(node.parent)
		.then(r => {
			if ( r.node && r.node.length ) {
				this.setState({'parent': r.node[0]});

				return $Grade.GetMy(node.id);
			}
			return Promise.resolve({});
		})

specifically this part:
			if ( r.node && r.node.length ) {

streamlined a bit.
What I mean: the raw responses from the API are being passed to the requests. The code could be changed to:
			if ( r && r.length ) {

or
			if ( r && !r.error ) {

Many API requests are allowed to fail (no items in feed), and it needs to be decided where true errors (catch) should be used.
Plus, we have very-basic async/await support now in the compiler, so this main block of code above could potentially be simplified.
Feeds
Feeds return arrays of nodes that should be displayed in an order. Such as blog feeds, game lists, results, etc.

Feeds are complex. They should definitely become their own file

Walk
Walk is used to decypher a URL request by stepping through each element of the path, to find the actual node. The remaining nodes are passed to the node type as extra arguments.

Walk needs to return a timestamp, so it too can request reloading of data upon change (like feeds)
Walk could include node data as an optimization, since a walk always returns 1 node

On the general, it sounds like me that if (r.valid) would be even nicer, but I'm also wondering here, if the preprocessing shouldn't repackage the response so that you could have:
$Node.Get(node.parent)
  .then(
    r => {
      this.setState({'parent': r.node[0]});
      return $Grade.GetMy(node.id);
    },
    r => {
      //Handle all sorts of issues if this is how the promises look like
    });

That is preprocessing should reject all things that could be issues and you should not have to test validity in the successful part of then.
I never really understood how walk works. Still don't. Which should be an indication of that it would be nice if the mechanism could be simplified or clarified somehow.
I do agree (if I understand you correctly) that feeds are quite distinct from common nodes and would be better treated as entirely separate entities.

There are cases where returning an empty array is valid, and I suspect the same goes for an empty response, but I don't yet know. At the moment error handling tends to get collapsed in to the success case. It begs the question where errors should be raised.
Raising errors to the user should probably be revisited too. There was some hackery in place for errors related to signups, but there should be a more standard way to inform of errors.
I'm also more leaning towards .catch(...) instead of the 2nd argument to .then(...), just because it's more clear that it's an error because of the word catch.

Any APIs that have side effects should really be POST rather than GET (I found a bunch more in grading, theme voting) - While this isn't a huge functional issue because over HTTPS it's unlikely for a caching proxy to rely on the meaning of GET vs POST semantics, there may still be situations where this causes hiccups.

I'm not expecting any hiccups, but I'm with you for the consistency.

I'm probably using $Node.Get the wrong way, but if I have an array of nodes I want to get, I manually join their id on '+'. Most if not all of these individual nodes actually exists in the cache, but since I haven't done the exact same request before, I don't use the cache. Or I think this is happening. This seems like a waste.

You should be able to pass the array directly to $Node.Get. Get should support both standard array-of-ids format, and array-of-ids-with-changes format.

Yeah that was it, Sets were not allowed, which is a bit of a pitty because they are nice things for making sure you don't ask for the same node more than once.

Note support for Set is a bit of a minefield in IE (only partial support), so we may need to add more compat shims. Not sure if you have tested in IE :)

No I didn't but I assumed our ES6 compiler would take care of these as well. (An my general feeling about ppl using IE is that they don't deserve support, they should at least have switched to Edge).

The compiler more handles syntax than features. That said we do have polyfills in place to add support for features not found in older browsers, but I'm not familiar enough with the problem with sets to know if we have that covered or not.
As far as legacy browser compatibility goes, I want the site to work on IE11 (i.e. Windows 7), but that's it. Windows 7 users don't have the luxury to install Edge.

Consider changing all API's that specify an ID as part of the path to include the $.
eg.
https://api.ldjam.com/vx/feed/$1/parent
This is the syntax used by other URL decoders to differentiate IDs from slugs. It may as well be standard.

What's the state of this issue? What still needs to be done to publish stable API v1?

 Maybe some initial-batch APIs too. Then do a once-over of everything to make sure everything is being done properly (POST instead of GET in the cases that @sgstair pointed out).


ucf101 video dataset seems to be gone

The ucf101 activity recognition dataset seems to have been completely removed. There's a link here https://www.tensorflow.org/datasets/catalog/ucf101 and when you go further both the landing page and the .zip file results in 404 errors.
To be honest I am a little surprised that Google wasn't hosting these datasets. You could link it up in Colaboratory so you didn't even have to download anything when using them from there. Just an idea.

This issue is more suitable on https://github.com/tensorflow/datasets/issues platform.
For quicker turnaround time you may try raising it on datasets repo.
Thanks!

Thanks for the issue. The correct weblink should point to https://www.crcv.ucf.edu/datasets/human-actions/ucf101/UCF101.rar

Thank you so much! And I'm so sorry for putting it here rather than in /datasets - I was  a bit confused I think =)

Thank you for reporting

To be honest I am a little surprised that Google wasn't hosting these datasets.

Google does not own the original data, so we are not legally allowed to re-host the dataset ourself (even if we would love to as it would greatly benefit the open source community).
Closing this as we've updated the link internally.


DSVT Voxel Performance using 100% waymo dataset

Hi,
I trained a DSVT model using the Waymo dataset with batch_size = 3 and 3 3090 GPUs(with torch.utils.checkpoints). The performance of mAP/H is about 1% below your benchmark.
Especially in the Ped. is particularly severe, but on the contrary, there are some improvements in the L2 of Vehicle.
my log

The reported performance is obtained with a batch_size of 3 and 8 GPUs.


Dexsearch: fix maxgen parameter

So that searching for gen1 mons doesn't give the rest of the gens too.

Actually I should probably document this somewhere


Fix iter_lines boundary bug when CRLF straddles two chunks

In Response.iter_lines, if a \r\n sequence (the only multi-character line boundary) straddles two chunks, the \r and \n are treated as two separate boundaries. Consequently, iter_lines will yield one extra blank line, as an empty string.
This addresses the issue by checking if a chunk ends with \r, and when appropriate, leaving the trailing line in pending until the next chunk or EOF arrives.

Hi @nanotone, thanks for putting this together! This has actually already been addressed and is patched for Requests-3.0 (#3984). We won't be able to merge this into the current master branch because it's a breaking change for some users which isn't backwards compatible.


Contact OPG

Samuel deez nuts is working on it

@SamueldSun Pls give update

Mike Gilbert from OPG never responded. They also don't do asset management/maintenance


input group for input type select doesn't prepend (input-group)

Input type select doesn't render well as opposed to other input types the edges remain curved  when placed in the input group
Bug report:

Tested using mac OS X 10.14.6
with Google Chrome 80
link to Codepen live preview codepenLink

actual output Preview

expected output preview

Bug reports must include a live reduced test case via CodePen/JS Bin or Stackblitz. And report specific browser and OS details.
This is an automated reply

alright let me  do that Asap

Input groups include support for custom selects and custom file inputs. Browser default versions of these are not supported.

Please see https://getbootstrap.com/docs/4.4/components/input-group/#custom-forms


Add dd component.

Issue https://github.com/basemate/matestack-ui-core/issues/182: Addition of Dd Component.
Changes

[x] Add dd component.
[x] Add dd documentation.
[x] Add dd spec.

Sure @pascalwengerter . I was thinking the same to pick issue https://github.com/basemate/matestack-ui-core/issues/186.


fix: node-please-upgrade usage

Before: undefined requires at least version 8.6.0 of Node, please upgrade
After: lint-staged requires at least version 8.6.0 of Node, please upgrade

Hmm could you please check why is CI failing now?

I think it's because I pushed too quickly and GitHub/Travis mixed things up a bit, because the tests passed: https://travis-ci.org/okonet/lint-staged/pull_requests


sys/linux: improved the descriptions for cgroup

fix: hugetlb..limit_in_bytes can be set.
hugetlb..usage_in_bytes is for reading.
added descriptions for the following resource controllers:
net_cls, net_prio, devices, freezer.
Update #533 , #1115
@dvyukov @xairy

The last force-push is a rebase on the master branch for merging without conflicts.


Dragonrage: Watch graphixwala.com

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

graphixwala\.com has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by rene in Charcoal HQ


Add Other Performance Metrics

Hi! I would like to use the following performance metrics to validate the hyperparameter optimization algorithms with kurobako.

The number of budgets to reach the X% point of the best performance. I want to give X as a float or a list of floats. I want to know the mean and variance.
The performance of the final parameter that was found to perform best. I want to know the mean and variance.

Thank you for the feature request!
As both seem useful, I'd like to support them. I'll consider the details of them when I have time.
For now, let me leave random thoughts about them.

The number of budgets to reach the X% point of the best performance. I want to give X as a float or a list of floats. I want to know the mean and variance.

I think that the most difficult point is how to specify an appropriate X%  to each problem. For example, considering to optimize the validation accuracy of ML tasks of which the best performance is 1.0, some tasks may easily achieve 0.9 accuracies while other tasks may not be able to reach 0.8 accuracies even if it's allowed to run infinity trials. It seems not an easy task to specify X% because it requires some insight about the target problem.
The following approach that uses random search might be a possible solution:

Run a benchmark that uses random search as the solver with a huge budget and save the result.
Let users specify a percentile point of the random search result instead of the X% point of the best performance of the problem.

I don't think that this is the best approach but at least, this ensures that users always specify a feasible point.

The performance of the final parameter that was found to perform best. I want to know the mean and variance.

It seems not difficult this feature, but currently kurobako doesn't provide built-in problems that have noise in the evaluation. So it might be worth considering adding such a problem too when we implement this feature.

If you have any comments, please let me know. > @HideakiImamura


Fix goroutine leaks due to use of non-buffered channels

Due to a channel not being buffered, and not having a guaranteed read occur, it's likely that one of the proxy copy goroutines blocks indefinitely writing to a non buffered channel. This is fixed by making the channel buffered. We see something similar in the console code as well.
Here's an example showing what i'm referring to. With the code below, we'll never see the sent error print statement
package main

import (
	"fmt"
	"time"
)

func main() {

	errChan := make(chan error)
	go func() {

		fmt.Println("sending error")
		errChan <- fmt.Errorf("err")
		fmt.Println("sent error")
	}()

	fmt.Println("sleeping")
	time.Sleep(100 * time.Second)
}

But with this code we will see the print statement.
package main

import (
	"fmt"
	"time"
)

func main() {

	errChan := make(chan error, 1)
	go func() {

		fmt.Println("sending error")
		errChan <- fmt.Errorf("err")
		fmt.Println("sent error")
	}()

	fmt.Println("sleeping")
	time.Sleep(100 * time.Second)
}

the difference is the use of a buffered channel.
NONE

/cc @kwiesmueller

/lgtm
/approve

/retest

This is also a good candidate for backports.

Looks good. I look forward to see that fix.
/approve

/lgtm
/approve


chore: use GitHub app token

So release-please PRs trigger GitHub workflows.

I'm not using https://github.com/tibdex/github-app-token since it's very hard to know what's the action is doing since the code is complied from TypeScript. I feel it's safer to pin to a commit hash of navikt/github-app-token-generator

Forgot to add the repo to the list of repos that have access to the secrets and also to install it for the repo.
Should work now.


[L7J7] Pipeline reproduction (SPM - deriv)

Softwares
SPM12
Input data
derivatives (fMRIprep)
Additional context
List of tasks
Please tick the boxes below once the corresponding task is finished. :+1:

[ ] :ok_hand: A maintainer of the project approved the issue, by assigning a :checkered_flag:status: ready for dev label to it.
[ ] :deciduous_tree: Create a branch on your fork to start the reproduction.
[ ] :sunrise: Create a file team_{team_id}.py inside the narps_open/pipelines/ directory. You can use a file inside narps_open/pipelines/templates as a template if needed.
[ ] :inbox_tray: Create a pull request as soon as you completed the previous task.
[ ] :brain: Write the code for the pipeline, using Nipype and the file architecture described in docs/pipelines.md.
[ ] :blue_book: Make sure your code is documented enough.
[ ] :snake: Make sure your code is explicit and conforms with PEP8.
[ ] :microscope: Create tests for your pipeline. You can use files in tests/pipelines/test_team_* as examples.
[ ] :microscope: Make sure your code passes all the tests you created (see docs/testing.md).

@icorouge: I am adding you as assignee on this issue (just for the time of the hackathon) so that we can more easily see which pipelines are open for new contributions in https://github.com/orgs/Inria-Empenn/projects/1/views/1

Correlation results with 108 subjects : [0.93, 0.94, 0.93, 0.94, 0.94, 0.93, 0.94, 0.93, 0.95] with commit ba2b3dd


Containerd 1.3.9 unable to use nvidia-container-runtime

Hi there, I'm upgrading containerd from 1.2.6 to 1.3.9, and I cannot find the right way to config to use nvidia-container-runtime.
For 1.2.6, I just change [plugins.linux] "runtime" from "runc" to "nvidia-container-runtime", and it all works. For 1.3.9, I tried to follow the doc but still can't find the right way to config, following is my config for 1.3.9, can someone help with that?
version = 2
root = "/var/lib/containerd"
state = "/run/containerd"
plugin_dir = ""
disabled_plugins = []
required_plugins = []
oom_score = 0

[grpc]
  address = "/run/containerd/containerd.sock"
  tcp_address = ""
  tcp_tls_cert = ""
  tcp_tls_key = ""
  uid = 0
  gid = 0
  max_recv_message_size = 16777216
  max_send_message_size = 16777216

[ttrpc]
  address = ""
  uid = 0
  gid = 0

[debug]
  address = ""
  uid = 0
  gid = 0
  level = ""

[metrics]
  address = ""
  grpc_histogram = false

[cgroup]
  path = ""

[timeouts]
  "io.containerd.timeout.shim.cleanup" = "5s"
  "io.containerd.timeout.shim.load" = "5s"
  "io.containerd.timeout.shim.shutdown" = "3s"
  "io.containerd.timeout.task.state" = "2s"

[plugins]
  [plugins."io.containerd.gc.v1.scheduler"]
    pause_threshold = 0.02
    deletion_threshold = 0
    mutation_threshold = 100
    schedule_delay = "0s"
    startup_delay = "100ms"
  [plugins."io.containerd.grpc.v1.cri"]
    disable_tcp_service = true
    stream_server_address = "<IP_ADDRESS>"
    stream_server_port = "0"
    stream_idle_timeout = "4h0m0s"
    enable_selinux = false
    sandbox_image = "k8s.gcr.io/pause:3.1"
    stats_collect_period = 10
    systemd_cgroup = false
    enable_tls_streaming = false
    max_container_log_line_size = 16384
    disable_cgroup = false
    disable_apparmor = false
    restrict_oom_score_adj = false
    max_concurrent_downloads = 3
    disable_proc_mount = false
    [plugins."io.containerd.grpc.v1.cri".containerd]
      snapshotter = "overlayfs"
      default_runtime_name = "runc"
      no_pivot = false
      [plugins."io.containerd.grpc.v1.cri".containerd.default_runtime]
        runtime_type = "io.containerd.runtime.v1.linux"                     // changed from "io.containerd.runc.v1"
        runtime_engine = ""
        runtime_root = ""
        privileged_without_host_devices = false
      [plugins."io.containerd.grpc.v1.cri".containerd.untrusted_workload_runtime]
        runtime_type = ""
        runtime_engine = ""
        runtime_root = ""
        privileged_without_host_devices = false
      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]
        [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
          runtime_type = "io.containerd.runtime.v1.linux"                  // changed from "io.containerd.runc.v1"
          runtime_engine = ""
          runtime_root = ""
          privileged_without_host_devices = false
    [plugins."io.containerd.grpc.v1.cri".cni]
      bin_dir = "/opt/cni/bin"
      conf_dir = "/etc/cni/net.d"
      max_conf_num = 1
      conf_template = ""
    [plugins."io.containerd.grpc.v1.cri".registry]
      [plugins."io.containerd.grpc.v1.cri".registry.mirrors]
        [plugins."io.containerd.grpc.v1.cri".registry.mirrors."docker.io"]
          endpoint = ["https://registry-1.docker.io"]
    [plugins."io.containerd.grpc.v1.cri".x509_key_pair_streaming]
      tls_cert_file = ""
      tls_key_file = ""
  [plugins."io.containerd.internal.v1.opt"]
    path = "/opt/containerd"
  [plugins."io.containerd.internal.v1.restart"]
    interval = "10s"
  [plugins."io.containerd.metadata.v1.bolt"]
    content_sharing_policy = "shared"
  [plugins."io.containerd.monitor.v1.cgroups"]
    no_prometheus = false
  [plugins."io.containerd.runtime.v1.linux"]
    shim = "containerd-shim"
    runtime = "nvidia-container-runtime"              // changed from "runc"
    runtime_root = ""
    no_shim = false
    shim_debug = false
  [plugins."io.containerd.runtime.v2.task"]
    platforms = ["linux/amd64"]
  [plugins."io.containerd.service.v1.diff-service"]
    default = ["walking"]
  [plugins."io.containerd.snapshotter.v1.devmapper"]
    root_path = ""
    pool_name = ""
    base_image_size = ""

Are you still using the v1 shim?
That's the only one you have configured but I think the default in 1.3 is io.containerd.runc.v1 (And 1.4 io.container.runc.v2).

hi~ @diyi0926
Could you show the way running a container on your machine, like ctr run ... or crictl create ... or kubectl ...


Fix use of ` in formatting in README

Current coverage is 48.97%

Merging #8 into master will not affect coverage as of 328d646

@@            master      #8   diff @@
======================================
  Files            9       9
  Stmts          196     196
  Branches         0       0
  Methods          0       0
======================================
  Hit             96      96
  Partial          0       0
  Missed         100     100

Review entire Coverage Diff as of 328d646

Powered by Codecov. Updated on successful CI builds.

Thanks. :)

Oh, haha, this is wrong too. It's rst, not markdown. I'll fix.

Oh my haha.
Sorry about that! It looks funny in GitHub :wink:

Fixed it for good with https://github.com/getsentry/sentry-auth-github/commit/2047d3833bbeedb8720b59de551daa61691f6c93


binary message

Hi,
I follow your Put example however within mq web console the messages are shown as 'binary messages'. Interesting, within MQ Explorer they are shown as text.
Thanks Tom.

Hi @T0X1CCAT
Could you please share some images to see the difference between mq web console and MQ Explorer?
Thank you.

I have the same issue, this my config and result

I have the same issue like that, now it is resolved this way,
https://github.com/JoseLuisSR/mqmeter/pull/7/commits/5fec56cc4442df56610feaa0df60db446baeb62e

Hi there.
In web console, it looks like this (first two messages are from jmeter, the third one is from external application):

In the mq explorer, it looks like this:


Invalid float values parsed from .toml file on Linux

Environment
toml++ version and/or commit hash:  GIT_TAG v3.2.0
Compiler:   g++ (Debian 10.2.1-6) 10.2.1 20210110
C++ standard mode: C++17
Target arch:  x64
Library configuration overrides:  TOML_HEADER_ONLY
Relevant compilation flags:  No.
compile_commands.json.log
Describe the bug
Float variables have wrong value after parsing from .toml file
formatted_data.toml.txt (Changed extension to .txt to upload to Github).
Values retrieved using ostringstream << operator on toml::table.
LastTest.log
Retrieved values:
positiveFloat1 = 0.84821299999999999
positiveFloat2 = 6.9341999999999997
negativeFloat = -995.92139999999995
(all float values are wrong).
Moreover, positiveFloat1 is listed twice!
Steps to reproduce (or a small repro code sample)
fs::path pathTested = GetParam();

fwsign::TomlReader tomlReader;
std::optional<toml::table> result = tomlReader.tomlFileRead(pathTested);

if(!fs::exists(pathTested) && !fs::exists(fixture.fwsignConfigDir / pathTested))
{
    ASSERT_FALSE(result.has_value());
    return;
}

if(!fs::is_regular_file(pathTested) && !fs::is_regular_file(fixture.fwsignConfigDir / pathTested))
{
    ASSERT_FALSE(result.has_value());
    return;
}

if(pathTested.extension() != ".toml")
{
    ASSERT_FALSE(result.has_value());
    return;
}

std::ostringstream temp;
temp << result.value();
std::string stringResult = temp.str();

// toml content after parsing is unordered - check for substrings
for(auto& entry : fixture.tomlTypesData.matchingFormatText)
{
    ASSERT_TRUE(stringResult.find(entry) != std::string::npos) <<
        "Did not find:\n" << entry << "\nin:\n" << stringResult << std::endl;
}

Additional information
Same code, bug is not reproduced on Windows 11 (compiled with MSVC 19.34.31933.0).
See: https://github.com/Andrey-Borisovich-Quality-Technologies/fw-sign/pull/14
Checks: https://github.com/Andrey-Borisovich-Quality-Technologies/fw-sign/actions/runs/3555112328/jobs/5971618751
And passing Windows build: https://github.com/Andrey-Borisovich-Quality-Technologies/fw-sign/actions/runs/3555112328/jobs/5971622441

This isn't a bug in toml++ but in the underlying float parsing implementation used by the version of the standard library you're compiling against. The reason it works correctly on windows is because the MSVC STL has std::from_chars for floating-points, whereas libstdc++ and libc++ either lack floating-point std::from_chars or it's broken, so there I fall back to a stringstream-based implementation.
You can try to force use of std::from_chars using #define TOML_FLOAT_CHARCONV 1, but your mileage may vary.

Moreover, positiveFloat1 is listed twice!

What? I tested your sample toml and there's no duplication. This isn't correct, or there's something wrong with your tests.

I just tried your TOML on x64 linux (ubuntu) both locally here on my machine, and remotely on the github actions, and it parses correctly and round-trips the values exactly. I'm going to close this as 'not a bug' since it seems the issue lies somewhere in your standard library locally.

Thanks for info, I'll look into it.

Might be something as simple as floating-point optimization, or similar. Worth noting that the values aren't really 'wrong'; they're floating-point and are out by like 0.000000000001, so I think you ought to even reconsider if this is an actual problem. Expecting exactness from floating-point is always a mistake.

Also perhaps try the most recent build, instead of v3.2.0? I can't think of anything in particular that might be impacting this, but I have fixed a few small bugs, so who knows?

Resolved the issue.
Turned out that TOML does not parse decimal floating points but only binary matching IEEE-754 specification.
However, this is not the problem. The problem is that this TomlPlusPlus library happily parses decimal floating point values without any error and then displays different values after parsing. This feature seems questionable in my opinion, especially that end user may not expect an exact result.
This subject was already mentioned in the https://github.com/toml-lang/toml/issues/572 .
I've used converted https://www.h-schmidt.net/FloatConverter/IEEE754.html to check the actual values.
I think TomlPlusPlus parser should throw parsing errors when the floating point value is not IEEE-754 compliant.
You can do that by using https://en.cppreference.com/w/cpp/types/numeric_limits/is_iec559 function.
Please consider this feature, current implementation of the library forces end-users to write their own validation of floating point values.


install through CocoaPods -> Use of unresolved identifier 'TransitionOptions'

Just installed it through CocoaPods. Set my UIViewController to conform to MenuContainerViewController. And this XCode error appears: Use of unresolved identifier 'TransitionOptions'. And i couldn't find implementation for this in InteractiveSideMenu Pod classes. transitionOptions property is missing too. I compared the class MenuContainerViewController from Pod and from example from GitHub and they seem different! Could you please help me what am doing wrong?

Hi @epitonium,
Please, take a look into this issue. Maybe, it'll help you.
If no, we'll get into the details of your question a little bit later.
Thanks for using library and asking question.

Thank you very much! This issue was already open and i missed it. Solved my problem!

Glad to hear! You're welcome.


impl(generator): handle http path with multiple substitutions

part of the work for #10980
When dealing with protos generated from discovery documents, we can encounter http paths with multiple substitutions, i.e. multiple pairs of {}. We need to parse this and then reassemble it with the string literals pieces and appropriate request accessor calls.

This change is

When using std::pair<> it will discard any additional splits it finds. So it's an implicit limit of 2.

A limit usually means that a=b=c split by = returns a and b=c... Do you really want just a and b?
-- sent from my phone.


ci: update matrix to include multiple Julia versions

checks for both ubuntu (x64) and macos (arm64)
Julia versions  ['1.9', '1.10', '~1.11.0-0']

Just a question: does something fail on Ubuntu Arm64? I guess people will be moving more and more to ARM for all OSes, and it'd be interesting to know whether this can be compatible.

I
See the failed jobs at github.com/WilhelmusLab/IceFloeTracker.jl/actions/runs/11057508568/job/30721473127. Had to remove the (ubuntu, arm64) combinations.

Just a question: does something fail on Ubuntu Arm64? I guess people will be moving more and more to ARM for all OSes, and it'd be interesting to know whether this can be compatible.

See the failed jobs from this ci runthis ci run . Had to remove the (ubuntu, arm64) combinations.

Just a question: does something fail on Ubuntu Arm64? I guess people will be moving more and more to ARM for all OSes, and it'd be interesting to know whether this can be compatible.

See the failed jobs from this ci run . Had to remove the (ubuntu, arm64) combinations.


Force leading zero?

Just like the title says.
I have a script to remove these after compiling but I think it reads better while writing. Just my personal preference and I'd like to keep everything consistent.
Setting leading-zero: 0 just removes the rule instead of forcing a leading zero.

See https://github.com/sasstools/sass-lint/blob/develop/docs/rules/leading-zero.md
Rule configuration is explained here: https://github.com/sasstools/sass-lint#rules
You need to set include: true in the rule options, like this:
leading-zero:
  - 2
  -
    include: true

That does it thanks.


could not create slug image: unexpected HTTP status: 500 Internal Server Error

git push has suddenly stopped working properly and it will either hang during the deploy and never complete or I'll get this error.

remote: 2017/04/20 17:03:34 ERROR: could not create slug image: unexpected HTTP status: 500 Internal Server Error
remote: ERROR: Build failed: exec: job exited with status 1

I've done all the usual things such as checking disk space and fix-hosts but that all seems ok.
I've emailed you the logs.

@dottodot I can see some errors in the blobstore log like:
XAmzContentSHA256Mismatch: The provided 'x-amz-content-sha256' header does not match what was computed.

It seems to only be happening in job cluster4-d1c12fbe-7f86-42c4-93a8-3230038f10c6 and for large uploads.
I suggest restarting that job with:
$ flynn -a blobstore kill cluster4-d1c12fbe-7f86-42c4-93a8-3230038f10c6

OK the first attempt to push has worked, but probably won't know for sure until I've done a few so will report back if there are any more issues.


Load carrers' link is not working.

Hi @joao-abrantes, this link https://consultancy.load.digital/carreiras is no longer working.
Do you have a new one?
Thanks.

Hi Rafael. What do you mean? Current one works - you mean https?

On 27 Sep 2020, at 02:34, Rafael Marmelo<EMAIL_ADDRESS>wrote:
Hi @joao-abrantes https://github.com/joao-abrantes, do you have a new link?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/marmelo/tech-companies-in-portugal/issues/196, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGYER57R5ILHNNRI6KYGKK3SH2JBFANCNFSM4R3HYWZQ.

Hi @joao-abrantes,
I cannot open the following link:
https://consultancy.load.digital/carreiras
The DNS cannot resolve the IP for the consultancy.load.digital domain.
Can you please check it that is the correct link?
Thanks.

Right… :)
Fixed and pushed new info to the server.
Thanks.
Joao

On 28 Sep 2020, at 16:09, Rafael Marmelo<EMAIL_ADDRESS>wrote:
Hi @joao-abrantes https://github.com/joao-abrantes,
I cannot open the following link:
https://consultancy.load.digital/carreiras https://consultancy.load.digital/carreiras
The DNS cannot resolve the IP for the consultancy.load.digital domain.
Can you please check it that is the correct link?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/marmelo/tech-companies-in-portugal/issues/196#issuecomment-700068273, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGYER5ZIL44WCIYKTGDSSYTSICRI7ANCNFSM4R3HYWZQ.

Hi @joao-abrantes,
I believe you forgot to create the pull request.
Can you please check?
Thanks.

Hi!
done.
regards,
Joao

On 5 Oct 2020, at 20:11, Rafael Marmelo<EMAIL_ADDRESS>wrote:
Hi @joao-abrantes https://github.com/joao-abrantes,
I believe you forgot to create the pull request.
Can you please check?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/marmelo/tech-companies-in-portugal/issues/196#issuecomment-703832411, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGYER5ZMDZES5WNH2URRRMTSJIK6VANCNFSM4R3HYWZQ.

thank you

On 4 Feb 2021, at 11:41, Afonso Jorge Ramos<EMAIL_ADDRESS>wrote:
Closed #196 https://github.com/marmelo/tech-companies-in-portugal/issues/196.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/marmelo/tech-companies-in-portugal/issues/196#event-4290415860, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGYER56VI4Q5SPR5GYUU3M3S5KBYPANCNFSM4R3HYWZQ.

João Abrantes
www.load.digital
www.blockbastards.io
www.qudo.io


Not being able to render jade blocks

Hi guys,
I'm using jade as the template engine and blocks are not rendering from the layout file.
I have the following file structure:
src/post.md - the file that is going to be built, which contains:
    ---
    layout: post.jade
    title: The title goes here
    ---
    # Hello World!

layouts/homepage.jade - this contains various main, footer and head blocks
layouts/post.jade - this is the main post template that contains
layouts/head.jade - the head block
extends homepage

block main
  #content!= contents

and partials/footer.jade with:
extends homepage

block footer
  #footer
    p footer content here

My build.js file looks like this:
var Metalsmith = require('metalsmith'),
  markdown = require('metalsmith-markdown'),
  layouts = require('metalsmith-layouts'),
  inPlace = require('metalsmith-in-place');

Metalsmith(__dirname)
  .use(markdown())
  .use(layouts({
    engine: 'jade',
    directory: 'layouts',
    partials: 'partials'
  }))
  .build(function(err) {
    if (err) throw err;
  });

If, on my post.md file I set the layout to homepage.jade NONE of the blocks are rendering.
While using post.jade as layout ONLY the main block is rendering inside of the homepage layout (extends seem to work).
If I use block main in any other jade file, that will not render either.
Could you please give me some feedback on this issue. It was previously working with metalsmith-templates ...
Cheers!

No problem, can you create a reduced test case that demonstrates the problem (and push it to a github repo)? That'll make it easier for me to take a look at it.

Hi @ismay
Thanks for your reply.
I've created a github repo to showcase the issue, and added the details in the readme file.
https://github.com/v3rt1go/metalsmith-layout-jade
Thanks for your help!

np :+1:


Fixing reader to display full path to image

Fixing image reader so that path in schema would contain the full path to image (or file) instead of just the zip file and added a test to validate

@imatiach-msft: Merging this with a comment pointing at the original code.

@imatiach-msft: the build fails with
##[error]Executor: Exception in task 5.0 in stage 22.0 (TID 81)
java.lang.ClassCastException: org.apache.hadoop.io.BytesWritable cannot be cast to [B
  at org.apache.spark.sql.catalyst.expressions.BaseGenericInternalRow$class.getBinary(rows.scala:47)
  ...


turtlebot3_node colcon build error ros2 rolling

Which TurtleBot3 platform do you use?

[x] Burger
[ ] Waffle
[ ] Waffle Pi

Which ROS is working with TurtleBot3?

[ ] ROS 1 Kinetic Kame
[ ] ROS 1 Melodic Morenia
[ ] ROS 1 Noetic Ninjemys
[ ] ROS 2 Dashing Diademata
[ ] ROS 2 Eloquent Elusor
[ ] ROS 2 Foxy Fitzroy
[x] ROS 2 Rolling (built from source)

Which SBC(Single Board Computer) is working on TurtleBot3?

[ ] Intel Joule 570x
[ ] Raspberry Pi 3B+
[x] Raspberry Pi 4
[ ] etc (Please specify your SBC here)

Which OS you installed on SBC?

[ ] Raspbian distributed by ROBOTIS
[ ] Ubuntu MATE (16.04/18.04/20.04)
[x] Ubuntu preinstalled server (18.04/20.04)
[ ] etc (Please specify your OS here)

Which OS you installed on Remote PC?

[ ] Ubuntu 16.04 LTS (Xenial Xerus)
[ ] Ubuntu 18.04 LTS (Bionic Beaver)
[x] Ubuntu 20.04 LTS (Focal Fossa)
[ ] Windows 10
[ ] MAC OS X (Specify version)
[ ] etc (Please specify your OS here)

Specify the software and firmware version(Can be found from Bringup messages)

Software version: [x.x.x]
Firmware version: [x.x.x]

Specify the commands or instructions to reproduce the issue.

mkdir -p ~/tb3_rolling/src && cd tb3_rolling/src
wget https://raw.githubusercontent.com/ROBOTIS-GIT/turtlebot3/ros2/turtlebot3.repos
vcs import src < turtlebot3.repos
rosdep install -y -r -q --from-paths src --ignore-src --rosdistro rolling
colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release

Copy and Paste the error messages on terminal.

/home/moritz/ros2_rolling/install/rclcpp/include/rclcpp/node_impl.hpp: In instantiation of ‘auto rclcpp::Node::declare_parameter(const string&, const ParameterDescriptor&, bool) [with ParameterT = unsigned int; std::string = std::__cxx11::basic_string<char>; rcl_interfaces::msg::ParameterDescriptor = rcl_interfaces::msg::ParameterDescriptor_<std::allocator<void> >]’:
/home/moritz/tb3_rolling/src/turtlebot3/turtlebot3/turtlebot3_node/src/turtlebot3.cpp:57:55:   required from here
/home/moritz/ros2_rolling/install/rclcpp/include/rclcpp/node_impl.hpp:223:26: error: call of overloaded ‘ParameterValue(<brace-enclosed initializer list>)’ is ambiguous
  223 |   rclcpp::ParameterValue value{ParameterT{}};

Please describe the issue in detail.

I'm currently trying to setup the turtlebot3 packages on my host pc in combination with ros2 rolling. Whilst building the turtlebot3 packages as stated above I get the mentioned error message. I checked that only rolling is sourced for both ros2 and navigation2.

@MoritzWillmann
Thank you for reporting the issue. I'm currently working on to release rolling packages, and for turtlebot3 package, you may use the galactic-devel branch for now as I'm going to create the rolling branch very soon.
Thanks!

Had the same problem.
Making the changes in turtlebot3_node/src/turtlebot3.cpp that @m2-farzan did seems to have resolved it and the build proceeded to completion (with a couple of warnings). But then at the end there's 1 package had stderr output: turtlebot3_node.
Strange because there were no errors and there's Finished <<< turtlebot3_node [1min 30s] alright

'stderr' output is caused by errors and/or warnings. In your case it's probably just the warnings.

@MoritzWillmann Apologies for the delayed response. We have assembled a TF team to address TurtleBot3 issues and are actively working on resolutions. Please note that we do not support EOL (End-of-Life) ROS versions; our support currently extends to Noetic and Humble versions. We kindly ask that you try again with the latest version. If the same issue arises, please feel free to resubmit it, and we will address it promptly.


Incorrect name resolution for JSDoc template tag constraints in typedef

Bug Report
🔎 Search Terms
jsdoc name resolve lookup symbol template constraint typedef
🕗 Version & Regression Information

This has been an issue since we added support for @template in JSDoc

⏯ Playground Link
Playground link with relevant code
💻 Code
/**
 * @template T
 * @template {keyof T} K
 * @typedef Foo
 */

🙁 Actual behavior
Reports Cannot find name `T`.
🙂 Expected behavior
Does not report an error.
Notes
Name resolution does not look at the symbol table of the @typedef tag, so when looking for T in the code below, we end up looking at T for the function declaration further down in this example:
/**
 * @template T
 * @template {keyof T} K
 * @typedef Foo
 */

/**
 * @template T
 * @param {T} a
 */
function bar(a) {
}

A "go-to-definition" on the T in keyof T jumps to the T declared for bar, not the T in the typedef for Foo.

Duplicate of https://github.com/microsoft/TypeScript/issues/43403


control_toolbox: 2.1.0-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository control_toolbox to 2.1.0-1:

upstream repository: https://github.com/ros-controls/control_toolbox.git
release repository: https://github.com/ros2-gbp/control_toolbox-release.git
distro file: rolling/distribution.yaml
bloom version: 0.10.7
previous version for package: 2.0.2-2

control_toolbox
* Fix parameter loading log levels
* Support pass in a precomputed derivative error
* Add getParametersCallbackHandle function
* Add topic_prefix_ to declareParam & setParameter
* Update include/control_toolbox/dither.hpp
* Correct contributing and license files for ament_copyright.
* Added license text file and contributing guidelines, corrected license short identifier.
* Remove build of downstream workspace.
* Update CI config and add pre-commit-config.
* Contributors: Bence Magyar, ChenJun, Denis Štogl, Timon Engelke

Holding for Rolling sync.


no check if need causal mask in flash_attn path

Hi Phil,
Looks like you forgot to check if actually need to apply causal mask to attn_bias when using flash attention path:
https://github.com/lucidrains/soundstorm-pytorch/blob/d4830b43355a314a55afe6dc2cf9b3ba4fc9bcc5/soundstorm_pytorch/attend.py#L98

@inspirit :man_facepalming: yes, thank you

@inspirit have you seen https://github.com/lucidrains/e2-tts-pytorch ? think i can revisit soundstorm and add the E2 type conditioning here as well (and cleanup a bunch of old torch code along the way)

yeah that one is of particular interest for me as well :) i was planning on giving it a try soon. I tried another implementation of e2-tts (rfwave) and it worked quite well for me but requires a lot of training, so i will come back to e2-tts a bit later.
i'm currently trying to apply maskgit generator to RQVAE from different domain so needs more adjusting here and there

yes that's a good combo


fix errors in 9. Modern Recurrent Neural Networks

Job d2l-zh/PR-775/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-775/


Lasso select tool (feature request)

Freely-drawn selection boundaries are a pretty commonly-expected tool. This would involve point-in-polygon (PIP) detection, which if I understand correctly is not implemented in SVG across all browsers. But, there are already JS implementations of common PIP methods (e.g. this one; not specifically advocating for this one, it was just the first one I found).

Related: #17 mentions this; #87 is about intersection algorithms in general. So perhaps this and #87 should be done together, to make sure we use a library (or algorithm set) that supports both lasso and rectangle solution (though I guess the latter is a special case; it can probably be done faster).
By the way, I don't think I know any web-based whiteboards that support lasso selection. But I agree that it's common among non-web-based tools.

By the way, I don't think I know any web-based whiteboards that support lasso selection

Google's Jamboard has Lasso select, and otherwise a pretty decent UI interface, but lacks infinite scroll and arbitrary zoom. I've been using Jamboard for student meetings but am going to switch to cocreate.

Google's Jamboard has Lasso select, [...]

Hmm, how do you do lasso select in Jamboard? I must be missing something...

I wrongly assumed the web interface was the same as the (Android) app, which has a Lasso tool. Mea culpa. I was used to using the app.


Flow will never be presented if the view controller has no navigation controller

Starting the flow from a view controller that is not in a UINavigationController does not work because the check to see if the view controller is visible fails.
This line:
https://github.com/Autodesk/ADAppRater-iOS/blob/master/ADAppRater/ADAppRater.m#L836
should check that viewController.navigationController is not nil before comparing to viewController.

found the same issue today and wrote the same check, +1 to merge this PR

Pushed now to version 1.0.5.
Thnx


SC: Smart Contract Framework implementation

We need to create a Smart Contract Framework Implementation for neo-sharp

The VM is usable now, so we can invoke Smart Contracts


Paket v4 fails update cmd (infinite dependency loop ?)

Description
I have a solution where paket (4.3.0 at this time) fails the update command, it never ends
whereas with paket 3.36, it finished in 4s
Repro steps
Not ATM, reproduced with a private repo, I will try to provide something if I can pinpoint the issue
Expected behavior
Paket update should finish in a reasonable amount time
Actual behavior
I stopped the update after 30 min
I attached a filtered verbose output for both v3 & v4 paket.exe
v4_res.txt
v3_res.txt
You can see that v4 seems lost in the dependency graph, not sure if caused by a circular dependency but the thing is it was working fine with v3
Known workarounds
Stick with v3 for this solution 😢

Yes please provide a repro. We are very interested in fixing this
Am 10.04.2017 12:11 nachm. schrieb "MrLuje"<EMAIL_ADDRESS>Description
I have a solution where paket (4.3.0 at this time) fails the update
command, it never ends
whereas with paket 3.36, it finished in 4s
Repro steps
Not ATM, reproduced with a private repo, I will try to provide something if
I can pinpoint the issue
Expected behavior
Paket update should finish in a reasonable amount time
Actual behavior
I stopped the update after 30 min
I attached a filtered verbose output for both v3 & v4 paket.exe
v4_res.txt https://github.com/fsprojects/Paket/files/909697/v4_res.txt
v3_res.txt https://github.com/fsprojects/Paket/files/909698/v3_res.txt
You can see that v4 seems lost in the dependency graph, not sure if caused
by a circular dependency but the thing is it was working fine with v3
Known workarounds
Stick with v3 for this solution 😢
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/2225, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNPgFIQwr2ITjzQS_2Hh8qxyK-_qMks5rugBogaJpZM4M4lCI
.

You can check https://github.com/MrLuje/Paket-v4-update-issue
I was not able to properly reproduce it so I integrated the same dependency graph we currently have on our private repo (as a local repository in the sln)
We found the cause : MassTransit & StackExchange.Redis have some incompatible versions (we can see this in verbose output) but it should be able to stop crawling the packages 😄

/cc @cloudRoutine. I think we should debug this one

In the end, duplicate of #2289 and also fixed by PR #2299
Great job, can't wait to see this officially released !


FieldValue does not accept bigint

type Schema = {
    id: bigint,
}

const [form, {Form, Field, FieldArray}] = createForm<Schema>()
/**
 * Type 'Schema' does not satisfy the constraint 'FieldValues'.
 * Property 'id' is incompatible with index signature.
 * Type 'bigint' is not assignable to type 'FieldValues | FieldValue | (FieldValues | FieldValue)[]'
 */
const formStore = createFormStore<Schema>()
/**
 * Type 'Schema' does not satisfy the constraint 'FieldValues'.
 */

bigint is not supported by any native HTML element. That's why it is not supported by Modular Forms.


*-CS cmdlets not recognized

After upgrading to Windows 11 and installing the latest MicrosoftTeams module (also tried preview) none of the CS cmdlets are recognized.
Get-CsMeetingRoom
Get-CsMeetingRoom : The term 'Get-CsMeetingRoom' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1

Get-CsMeetingRoom

  + CategoryInfo          : ObjectNotFound: (Get-CsMeetingRoom:String) [Get-CsMeetingRoom], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

I've tried connecting using Connect-MicrosoftTeams -UseDeviceAuthentication to no avail. According to Get-Command they are available:
Function        Get-CsIPPhonePolicy                                2.6.1      MicrosoftTeams
Function        Get-CsMeetingConfiguration                         2.6.1      MicrosoftTeams
Function        Get-CsMeetingMigrationStatus                       2.6.1      MicrosoftTeams
Function        Get-CsMeetingRoom                                  2.6.1      MicrosoftTeams
Function        Get-CsMobilityPolicy                               2.6.1      MicrosoftTeams

Hi @wagenveld, thank you for your feedback.
I have Windows 11 on my machine and I can use version 2.6.0 with the CS cmdlets.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome, let me know if it can be called out in the docs.
Please follow this link to contact support for business products: https://docs.microsoft.com/office365/admin/contact-support-for-business-products.
Please keep us posted here on the resolution to feed whatever information you discover into the content.

@dariomws  Thank you very much for the contribution and sharing this explanation. @wagenveld
Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed to close it as here we are limited to documentation fixes and improvements only.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Pushlists

be better on screen about why pushlistgithub doesn't process for those with version=local

merged


Descripe purpose of TimeEvolver in ReadMe

Add short summary of features to the ReadMe and describe what TimeEvolver does.

Done with fac1fe2


Block size documentation

I can find no documentation on the "Block size (MB)" property available in Azure Blob Storage sink of Copy Data. The documentation refers to various pages where properties can be found, and the link from the tool links here; but the term Block size is not available on the page. Where can I get this info?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: df7b56de-6c44-a6a7-7cb1-2d77025f17f5
Version Independent ID: fa99fc00-8d68-a1de-558e-0ef651548f34
Content: Copy and transform data in Azure Blob storage - Azure Data Factory
Content Source: articles/data-factory/connector-azure-blob-storage.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

Thanks for the feedback. Doc is updated. Please refer to the description of blockSizeInMB in this section https://docs.microsoft.com/en-us/azure/data-factory/connector-azure-blob-storage#blob-storage-as-a-sink-type.
#please-close

@linda33wj  Awesome!


How can I extract the features using 2000 classes (1600 objects +400 attributes) ?

In your code, we find N_CLASSES = 1601, does it mean 1600 objects + 1 background?
And how can I extract the features using 2000 classes (1600 objects +400 attributes)? Modity the N_CLASSES = 1601 to N_CLASSES = 2001 directly?
Thanks a lot and wait for your reply!

N_CLASSES = 1601 is 1600 object classes + 'no object' class. It can't be directly extended to 2000 classes, because in the original model attributes are handled by additional output layer which I don't use.

Thanks for your reply!
Assume that index0, index1, ..., index1600 represent the N_CLASSES = 1,601 categories, does the index0 mean the "no object" class or the index1600? And the rest of 1600 categories correspond to object classes in order?

index0 is 'no object', the rest are in the same order as in the file.

Ok, thanks for your kind help!


How-To: Kubernetes base YAML guide

Thank you for helping make the Radius documentation better!
Please follow this checklist before submitting:

[ ] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description

Auto-generated description

🤖 Generated by Copilot at 87aec43
Summary
📝🧱🗂

This pull request adds a new how-to guide on using Radius to incrementally onboard from existing Kubernetes resources. It also adds the code snippets for the guide, such as the basemanifest.bicep and basemanifest.yaml files, which demonstrate how to define a Radius application and a container resource that loads a Kubernetes base manifest file.

Radius guides grow
Adding YAML and bicep
Docs bloom in springtime

Walkthrough

Add a new how-to guide on incrementally onboarding from existing Kubernetes resources using Radius (link)

Reference the code snippets for the Radius application and the Kubernetes base manifest file (link, link)

Add a new bicep file for the Radius application that loads the Kubernetes base manifest file (link)
Add a new YAML file for the Kubernetes base manifest file that defines various Kubernetes resources (link)

Issue reference
#705

had a chat with @AaronCrawfis about which resource configs "win out" if both are specified in the base yaml and the radius bicep.
@jasonviviano - can you test the outcome of the following behaviors note how these work so that we may update our documentation accordingly?

If different values for namespace is specified in both the Bicep and YAML definitions
If different container images are specified in both the Bicep and YAML definitions

closing this in favor of https://github.com/radius-project/docs/pull/1024


sqlparser-rs can not parse pgvector SQL

I want to use pg_later to create pgvector index as an async job. But it looks like sqlparser-rs can not parse the SQL.
postgres=# select pglater.exec('CREATE INDEX ON items USING hnsw (embedding vector_l2_ops)') as job_id;
ERROR:  Query parsing failed, please submit a valid query: ParserError("Expected ), found: vector_l2_ops at Line: 1, Column 45")

$ cargo run
   Compiling sql_parse_test v0.1.0 (/Users/xieyuandong/Workspace/rust/sql_parse_test)
    Finished dev [unoptimized + debuginfo] target(s) in 1.32s
     Running `target/debug/sql_parse_test`
thread 'main' panicked at src/main.rs:8:48:
called `Result::unwrap()` on an `Err` value: ParserError("Expected ), found: vector_l2_ops at Line: 1, Column 45")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

(base)
~/Workspace/rust/sql_parse_test on  main! ⌚ 15:20:19
$ cat src/main.rs
use sqlparser::dialect::GenericDialect;
use sqlparser::parser::Parser;

fn main() {
    let sql="CREATE INDEX ON items USING hnsw (embedding vector_l2_ops);";
    let dialect = GenericDialect {}; // or AnsiDialect, or your own dialect ...

    let ast = Parser::parse_sql(&dialect, sql).unwrap();

    println!("AST: {:?}", ast);
}

@ChuckHend I found you leverage sqlparser-rs for query parsing in this pr https://github.com/tembo-io/pg_later/pull/48/files.

I see what you mean. Thats not intended / definitely a bug.

I see what you mean. Thats not intended / definitely a bug.

Thank you for your reply, will we fix this bug?

Currently, I am using version 0.0.14 and have skipped the validate process.
However, I encountered a problem. After completing the task, I am unable to obtain the results.
postgres=# select pglater.init();
NOTICE:  relation "q_pg_later_jobs" already exists, skipping
NOTICE:  relation "a_pg_later_jobs" already exists, skipping
NOTICE:  relation "q_pg_later_jobs_vt_idx" already exists, skipping
NOTICE:  relation "archived_at_idx_pg_later_jobs" already exists, skipping
NOTICE:  relation "q_pg_later_results" already exists, skipping
NOTICE:  relation "a_pg_later_results" already exists, skipping
NOTICE:  relation "q_pg_later_results_vt_idx" already exists, skipping
NOTICE:  relation "archived_at_idx_pg_later_results" already exists, skipping
 init
------
 t
(1 row)

postgres=# select pglater.exec(                                                                                'select * from pg_available_extensions order by name limit 2'                                                                                ) as job_id;
 job_id
--------
      5
(1 row)

postgres=# select pglater.fetch_results(5);
 fetch_results
---------------

(1 row)

postgres=# select * from pgmq.q_pg_later_jobs;
postgres=# select * from pgmq.q_pg_later_jobs where msg_id=5;
 msg_id | read_ct |          enqueued_at          |              vt               |                                 message
--------+---------+-------------------------------+-------------------------------+--------------------------------------------------------------------------
      5 |       0 | 2024-12-12 03:46:15.867772+00 | 2024-12-12 03:46:15.868156+00 | {"query": "select * from pg_available_extensions order by name limit 2"}
(1 row)

Why the query is not executed?

I solve it, I use the latest pgmq.

, will we fix this bug?

Yes. I think we want to keep the SQL parser, or find an alternative to it, because it is a great way to reject invalid queries before they are executed. I could use some help finding a solution. Or I can look at it sometime in the next couple weeks.


Error while using debugger

Hi,
I have installed the debugger, but when I do basic command like list it throws following error -
Welcome to the OpenWhisk Debugger
(wskdb) list
Available actions:
Error: entity does not exist while in this operation:  fetching actions
Unhandled rejection TypeError: Cannot read property 'filter' of undefined
at print (/usr/local/lib/node_modules/openwhisk-debugger/lib/commands/list.js:45:6)
at /usr/local/lib/node_modules/openwhisk-debugger/lib/repl-messages.js:49:6
at tryCatcher (/usr/local/lib/node_modules/openwhisk-debugger/node_modules/bluebird/js/main/util.js:26:23)
at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/openwhisk-debugger/node_modules/bluebird/js/main/promise.js:510:31)
at Promise._settlePromiseAt (/usr/local/lib/node_modules/openwhisk-debugger/node_modules/bluebird/js/main/promise.js:584:18)
at Promise._settlePromises (/usr/local/lib/node_modules/openwhisk-debugger/node_modules/bluebird/js/main/promise.js:700:14)
at Async._drainQueue (/usr/local/lib/node_modules/openwhisk-debugger/node_modules/bluebird/js/main/async.js:123:16)
at Async._drainQueues (/usr/local/lib/node_modules/openwhisk-debugger/node_modules/bluebird/js/main/async.js:133:10)
at Immediate.Async.drainQueues (/usr/local/lib/node_modules/openwhisk-debugger/node_modules/bluebird/js/main/async.js:15:14)
at runCallback (timers.js:637:20)
at tryOnImmediate (timers.js:610:5)
at processImmediate [as _immediateCallback] (timers.js:582:5)

Hi Sandeep,
According to the author of the debugger, Nick Mitchell, the debugger currently requires node 6 to 6.2, i believe. anything higher than 6.3 won't work.
Not sure what Node version you have tried.
Kind regards,
Matt

hi @sandeep-paliwal sorry for the delay in responding to you. we've been working on an update to this functionality. check it out here: https://openwhisk.ng.bluemix.net/api/v1/web/nickm_wskng_demos/public/index.html
the OpenWhisk Shell includes the debugger functionality. in the Shell, the debugger works with all versions of node 6 (whereas this github project only works with up to NodeJS 6.2). Also, with the Shell, you can download a platform release, avoiding the need for any local builds. let us know what you think!