[cherry-pick release/3.2.x] add back debug symbol and related test to release/3.2.x

Summary

This cherry-picks the following PRs:
https://github.com/Kong/kong/pull/10568
https://github.com/Kong/kong/pull/10579
Please rebase merge to keep the commits accordingly.
Checklist

[ ] The Pull Request has tests
[ ] There's an entry in the CHANGELOG
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

[Implement ...]

Issue reference
FTI-4918
KAG-1036

Test result: https://github.com/Kong/kong/actions/runs/4686832728


RC2 servers' extracted pack name is inappropriate

Description:
Once user extracted the wso2sp-4.1.0-RC2.zip archive, user will get pack as wso2sp-4.1-2.0. this is inappropriate.
Affected Product Version:
wso2sp-4.1.0-RC2

Fixed


Archive CityCamp NC 2015 items

I've got sponsors/press moved to a sub -page

Still need to do:
http://citycampnc.org/venue/
http://citycampnc.org/speakers/
http://citycampnc.org/hackathon/

So sorry to miss tonight. I'm sharing my car with my teen daughter this
week and the schedule just didn't work out tonight. I'm worried that we are
getting into crunch time for some of our marketing efforts. I'll do my best
to catch up this week.
Best regards,
Suzanne
On Monday, June 20, 2016, Jason Hibbets<EMAIL_ADDRESS>wrote:

Closed #59 https://github.com/codeforraleigh/CityCampNC/issues/59.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/CityCampNC/issues/59#event-698379317,
or mute the thread
https://github.com/notifications/unsubscribe/ARrpxp973z45O6vbYG0ku0vqLGs_ibkJks5qNyZigaJpZM4INz5u
.


Warning: Each child in a list should have a unique "key" prop.  Check the render method of BlocksField.

Link to reproduction
Not for now
To Reproduce
Not sure how to reproduce, I guess it occurs for any blocks field
Describe the Bug

Payload Version
1.10.5

@Stupidism I was able to recreate this when using initialData, is that true for you as well? I am unable to reproduce it when just using blocks/array rows.


Sparse array in Cpp

Information about Algorithm

(Type here)
Sparse array using linked list
Have you read the Contributing.md and Code of conduct

[x] Yes
[ ] No

Other context

(Type here)

assign this issue to me


Unflattening does not create an instance of the property

Describe the bug
When unflattening the entire source into a property of target, that property is not initialized before setting the values resulting in a runtime NullReferenceException
To Reproduce
Steps to reproduce the behavior:

Declare a mapper as an interface
Add a wrapper around CarDto
Add a mapping method CarWrapper CarToWrapper(Car car);
Execute mapper

Expected behavior
target object and inner property created and initialized
Code snippets
public record Car
{
    public string Make { get; set; } = null!;
}

public record CarDto
{
    public string Make { get; set; } = null!;
}

public record CarWrapper
{
    public CarDto Dto { get; set; } = null!;
}

[Mapper]
public partial class CarMapper
{
    [MapProperty(source: "Make", target: "Dto.Make")]
    public partial CarWrapper CarToWrapper(Car car);
}

var mapper = new CarMapper();
var car = new Car { Make = "CoolCar" };
var wrapper = mapper.CarToWrapper(car);
wrapper.Dto.Should().NotBeNull();
wrapper.Dto.Make.Should().Be("CoolCar");

Environment (please complete the following information):

Mapperly Version: 2.5.0
.NET Version: .NET 6.0.102
Target Framework: .net6.0
OS: windows / docker mcr.microsoft.com/dotnet/aspnet:6.0-alpine

Additional context
Add any other context about the problem here.

This is because you marked your properties as non-nullable, but still assigned null to them. Mapperly does not create and assign new instances to non-nullable properties, as they should already contain a value (given that they are non-nullable).
Either mark your properties as nullable or assign a value to them, then it will work as expected.


[SPARK-4286] Integrate external shuffle service to coarse grained Mesos mode

Test build #24976 has finished for   PR 3861 at commit 392486e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      "cd %s*; %s ./bin/spark-class ".format(basename, prefixEnv)

Test build #24976 has finished for   PR 3861 at commit 392486e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      "cd %s*; %s ./bin/spark-class ".format(basename, prefixEnv)

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/24976/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/24976/
Test FAILed.

I don't think the test failure is related, and the test passes locally too.

I don't think the test failure is related, and the test passes locally too.

@ash211 Thanks for the review, updated the PR.

Test build #25002 has started for   PR 3861 at commit a8d036c.

This patch merges cleanly.

Test build #25002 has finished for   PR 3861 at commit a8d036c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      "cd %s*; %s ./bin/spark-class ".format(basename, prefixEnv)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25002/
Test PASSed.

@aarondav

Test build #25082 has started for   PR 3861 at commit ae1d91a.

This patch merges cleanly.

Test build #25083 has started for   PR 3861 at commit c601c3f.

This patch merges cleanly.

Test build #25082 has finished for   PR 3861 at commit ae1d91a.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      "cd %s*; %s ./bin/spark-class ".format(basename, prefixEnv)
   implicit class StringToAttributeConversionHelper(val sc: StringContext)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25082/
Test PASSed.

Test build #25083 has finished for   PR 3861 at commit c601c3f.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      "cd %s*; %s ./bin/spark-class ".format(basename, prefixEnv)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25083/
Test PASSed.

Test build #25119 has finished for   PR 3861 at commit c954dc7.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      "cd %s*; %s ./bin/spark-class ".format(basename, prefixEnv)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25119/
Test PASSed.

Hi @tnachen thanks for your work. I will do a closer review within the next few days. First I have a high level question. IIUC, the changes in this PR basically enable the dynamic allocation feature to be used with Mesos coarse-grained mode. However, in Mesos I believe we express the amount of resources an application wants in terms of cores, not the number of executors. Is the concern raised in SPARK-4751 for standalone mode relevant here?

Test build #25206 has started for   PR 3861 at commit c18760f.

This patch merges cleanly.

Hi @andrewor14, yes the concerns are identical. Basically in coarse grain mode, I don't over allocate executors even if you request more than the available slaves.
So really dynamic allocation in coarse grain mode simply provides a way to scale down the executors, and when more is needed to scale back maximumly to the available slave nodes and also still within spark.cores.max.
This could change ofcourse as there are discussions to allow coarse grain mode to launch multiple executors, but that's a seperate discussion.

Test build #25209 has started for   PR 3861 at commit f39cdd2.

This patch merges cleanly.

Test build #25206 has finished for   PR 3861 at commit c18760f.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SlaveStatus(var executorRunning: Boolean, var taskRunning: Boolean)
      "cd %s*; %s ./bin/spark-class ".format(basename, prefixEnv)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25206/
Test PASSed.

Test build #25209 has finished for   PR 3861 at commit f39cdd2.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SlaveStatus(var executorRunning: Boolean, var taskRunning: Boolean)
      "cd %s*; %s ./bin/spark-class ".format(basename, prefixEnv)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25209/
Test PASSed.

Test build #25245 has started for   PR 3861 at commit 99cc898.

This patch merges cleanly.

Test build #25248 has started for   PR 3861 at commit 95ff246.

This patch merges cleanly.

@andrewor14 I updated the PR with your feedback, and also after testing on a 4 node cluster I fixed an issue I found where it the offer has enough resources just for the task but scheduler is looking for shuffle and task resources.

Test build #25249 has started for   PR 3861 at commit 93e5fbc.

This patch merges cleanly.

Test build #25245 has finished for   PR 3861 at commit 99cc898.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SlaveStatus(var executorRunning: Boolean, var taskRunning: Boolean)
      "cd %s*; %s ./bin/spark-class ".format(basename, prefixEnv)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25245/
Test PASSed.

Test build #25248 has finished for   PR 3861 at commit 95ff246.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SlaveStatus(var executorRunning: Boolean, var taskRunning: Boolean)
      "cd %s*; %s ./bin/spark-class ".format(basename, prefixEnv)

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25248/
Test FAILed.

Test build #25249 has finished for   PR 3861 at commit 93e5fbc.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25249/
Test FAILed.

@andrewor14 I wonder if you have time to review this?

Test build #25581 has started for   PR 3861 at commit 99415c3.

This patch merges cleanly.

Test build #25581 has finished for   PR 3861 at commit 99415c3.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SlaveStatus(var executorRunning: Boolean, var taskRunning: Boolean)
      "cd %s*; %s ./bin/spark-class ".format(basename, prefixEnv)

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25581/
Test PASSed.

Adding you folks for review: @dragos @deanw @huitseeker @skyluc

Hey @tnachen sorry again for slipping on this. I think this would be a good feature to add in 1.4. I'll be sure to review this at the beginning of the release cycle. Thanks for pinging me on this.

@tnachen Thanks for working on this. Before I dive deeper into the implementation there's a main open question that I'd like to address. The external shuffle service is intended to live across the executor lifetime and so launched independently of any Spark application. The service enables dynamic allocation of resources because it can continue to serve an executor's shuffle files after the executor has been killed. However, in this patch the service seems to be started inside the executor backend itself and its fate necessarily tied with the application.
If I understand correctly, the Mesos slave is equivalent to the standalone Worker in that it is long running and lives beyond the lifetime of a particular application. If this is the case, the appropriate place to start the shuffle service would be there instead.
Another issue is that this patch in its current state seems to conflate two issues (1) dynamic allocation and (2) external shuffle service. (1) is what you refer to as auto-scaling on the JIRA, and depends on (2) to work. However, since we already check whether shuffle service is enabled in ExecutorAllocationManager, we shouldn't check it again when launching the Mesos executor. More specifically, I don't understand why we launch the executor two different ways depending on whether (2) is enabled. I believe a better solution is to separate these two concerns and launch the executor the same way we already do today.

@andrewor14 Mesos slave doesn't have the concept of Auxilary service as YARN, that launches a service as part of the Slave. It requires a task to be running to launch anything.
Therefore to have a long running service that lives longer than the task lifetime, I went the route to create a custom Mesos executor that launches the Coarse grained spark executor, and continue to run when the spark executor finishes. The custom executor also launches the external shuffle service.
I agree I didn't really like the diverging path, but I felt like the original method is much simpler as it directly launches the coarse grain executor, and don't want to increase the complexity by making it also have to launch this custom executor.

We spoke a bit offline about this, but my feeling was that the best thing here might be to add a way to launch the shuffle service as a standalone application (initially, not one managed by Mesos) so that it can be shared across Spark applications. That would involve writing some simple launching scripts for it in a similar way to existing daemons we launch, and you'd ask users to launch the shuffle service similar to other storage systems like HDFS. That's very simple and would avoid diverging a lot between Mesos and the other modes. And longer term we could actually have a single shared shuffle service that is scheduled by mesos.

Agree and it's currently being worked on. We can close this PR too.

I'd like to take a shot at making the external shuffle service a "daemon". Just to make sure I understand the requirements:

the shuffle service is launched manually on cluster machines
it does not care about spark.shuffle.service.enabled, if it's started -- it just starts
it should not depend on Spark or Scala -- this is the part I'd like to get confirmation. If that's the case, it means we can't use helper scripts like spark-submit or spark-class that would simplify loading configuration files

/cc @tnachen


Match charm messages

In a separate function for now

It turns out that Event IDs are not as globally unique as I thought they were, so some messages were being mismatched with others. I fixed this, but it will still possibly cause issues if messages with the same event ID were to overlap in time. I don't know if it is possible for them to overlap or how projections accounts for this (if it does and if it even needs to). For now, though, it seems that basically all messages are being properly matched.
Another thing I don't really understand: it appears that some entry methods are split into portions (each a separate enter event) by "dummy_thread_ep" in the ping-pong projections trace. Each of those portions are matched to the same message send in projections, even though it's not multi- or broad-cast. Matching here still works with my implementation, it's just that the matching event in the send event's columns will have the index/timestamp of the last of these portions.

One other thing that needs to be addressed: right now, the messages being matched from Instant send events to Enter events that mark the beginning of an entry method.
The problem is, in the enter events this would overwrite the matching enters/leaves from _match_events (or from the reader in the new implementation). I'm guessing this warrants a new column.


Selected threads - only 2 highlighted

Hi guys,
I noticed that when using the 2 panel layout, when selecting multiple threads, only the first 2 selections are highlighted.
The right-panel (that originally shows the message content) shows the correct number of selected conversations, but as said, only 2 itens in the messages list stay highlighted.
But It turns highlighted if you change the threads list width.
I'm using:

OSX 10.11.6
Nylas Version 1.0.21 (1.0.21)
Tested with all default themes.
Appearance layout: 2 panel

There are two different ways to reproduce:
1) Selecting messages one by one

set the appearance layout to TWO PANEL;

access any folder in any account (all mail, inbox, sent...)

select one threads (it will highlight), then, with cmd key pressed, select any other threads (it will highlight too). Still with cmd key pressed, and select other threads (it will not highlight, but the right panel will count this threads in the total)

If you change the threads list width (the sufficient to change its appearance - image 1), the unhighlighted messages will be highlighted (image 2)
Image 1:

Image 2:

2) Selecting messages whit shift key

set the appearance layout to TWO PANEL;

access any folder in any account (all mail, inbox, sent...)

select one threads (it will highlight), then, with shift key pressed, select any number of threads below (or above) the initial selection (it will highlight too, doesn't matter if you select a group of 2 or 15 threads). Still with shift key pressed (or you can change it, pressing the cmd key), and select other threads (it will not highlight, but the right panel will count this threads in the total)

If you change the threads list width (the sufficient to change its appearance), the unhighlighted messages will be highlighted

this should be fixed on 1.0.26 which was released today! Thanks for your patience!


Default nominal entries

Coverage increased (+0.0003%) to 98.765% when pulling ced977858e04935ad76416ff98af2e5bb4f1d97f on default-nominal-entries into daa8151e67914013538078c9735c59dcc6445984 on master.


User is not able to set security groups for EKS cluster

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Add catalog - https://github.com/rmweir/system-charts
Branch - add-eks-controller; commit id: c6651c4
Deploy rancher-eks-controller from this catalog.
Deploy an eks cluster using kubectl apply -f cluster.yaml where is something like cluster.yaml

apiVersion: ke.cattle.io/v1
kind: EKSClusterConfig
metadata:
  name: sowmya-2
spec:
  kubernetesVersion: "1.14"
  privateAccess: true
  publicAccess: true
  cloudCredential: ""
  displayName: "sowmya-2"
  region: "us-east-2"
  loggingTypes: []
  tags:
    "test" : "one"
  securityGroups: [<sg-1>]
  nodeGroups:
  - nodegroupName: "sowmya-2-ng"
    instanceType: "t3.medium"
    desiredSize: 1
    maxSize: 1
    minSize: 1

Cluster is created.
The security group set - sg-1  is NOT seen set on the cluster

Actual Result:
User should be able to set security groups  for EKS cluster
Expected Result:
Security group set is NOT reflected on the cluster
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head - master-3244-head
Installation option (single install/HA): HA

Verified on master-head - commit id: 6aef36313

Login as a standard user
Create a hosted EKS cluster
Give in the subnet and security group.
Cluster comes up successfully
Security group set on Rancher reflects as Additional security groups in EKS
Subnets set on rancher reflect under Subnets in EKS console.


catalog page 'There are no compatible templates.'

after upgrading to rancher  v1.1.10 the catalog page turned out empty with the message:
There are no compatible templates.

Useful
Info

Versions
Rancher rancher/server Cattle: v0.165.7 UI: v1.1.10

Access
github admin

Orchestration
Cattle

Route
catalog-tab.index

@joostliketoast Can you check your settings and make sure Rancher Certified and Community Contributed options are set to enabled.
If they already are, can you disable, click save then enable and click save again.  See if that brings them back up.

I have the same issue.
I am testing the Rancher Catalog with this: https://gitlab.com/averri/ocb-catalog.git

Useful
Info

Versions
Rancher v1.1.1 Cattle: v0.165.7 UI: v1.1.12

Access
localauth admin

Orchestration
Cattle

Route
catalog-tab.index

@averri: compose v2 syntax is not supported yet.

Thanks @vincent99, so I converted the docker-compose to v1, still no success.

I think the top level folder should just be templates and you need another folder nested in that folder that will be named ocb-services.

@deniseschannon, tried that too using: https://gitlab.com/averri/templates.git
And still getting the same message.

@averri That's a repository named templates, not a folder named templates inside the repository.

Hi @vincent99, thanks for informing that. I have added the folder  templates, as bellow:

Added the catalog to Rancher:

But it still says:

Did you give it 5 min for automatic refresh or click the refresh button in the upper-right corner after changing?  They're not updated instantaneously
Unfortunately GitLab is down right now so I can't show a picture of it in the UI, but it was loading in the API now with your last change so it will work in the UI:

Tried in version 1.1.1 and I'm seeing your catalog after adding https://gitlab.com/averri/templates in catalog.

@joostliketoast never heard back from you about your catalog issue.  Was your issue resolved?

Thanks @tfiduccia, but I still have no luck. I reinstalled Rancher Server, and the problem persists. There are some error messages in the Rancher Server:
time="2016-07-21T18:05:08Z" level=info msg="Starting Rancher Catalog service"
time="2016-07-21T18:05:08Z" level=info msg="Using catalog library=https://github.com/rancher/rancher-catalog.git"
time="2016-07-21T18:05:08Z" level=info msg="Using catalog community=https://github.com/rancher/community-catalog.git"
time="2016-07-21T18:05:08Z" level=info msg="Using catalog OCB=https://gitlab.com/averri/templates.git"
time="2016-07-21T18:05:08Z" level=error msg="Failed to pull the catalog from git repo https://github.com/rancher/community-catalog.git, error: exit status 1"
time="2016-07-21T18:05:08Z" level=error msg="Git pull for Catalog community failing with error: exit status 1 "
time="2016-07-21T18:05:08Z" level=info msg="Cloning the catalog from git URL https://gitlab.com/averri/templates.git"
Cloning into './DATA/OCB'...
fatal: unable to access 'https://gitlab.com/averri/templates.git/': Failed to connect to apache port 1080: Connection refused
time="2016-07-21T18:05:08Z" level=error msg="Failed to clone the catalog from git err: exit status 128"
time="2016-07-21T18:05:08Z" level=error msg="Failed to pull the catalog from git repo https://github.com/rancher/rancher-catalog.git, error: exit status 1"
time="2016-07-21T18:05:08Z" level=error msg="Git pull for Catalog library failing with error: exit status 1 "

It seems you need/have configured a proxy for git that doesn't work?  Nothing is going to show up if it can't clone the repos.

Hi @vincent99, it is possible to clone any git repo from the host, but not from inside the Rancher container:
From Docker host (ok):
[root@vmi77191 ~]# git clone https://gitlab.com/averri/templates.git
Cloning into 'templates'...
remote: Counting objects: 35, done.
remote: Compressing objects: 100% (28/28), done.
remote: Total 35 (delta 5), reused 0 (delta 0)
Unpacking objects: 100% (35/35), done.

From Rancher container (fails):
root@fbc4f63eecf4:/# git clone https://gitlab.com/averri/templates.git
Cloning into 'templates'...
fatal: unable to access 'https://gitlab.com/averri/templates.git/': Failed to connect to apache port 1080: Connection refused

I have the container environment variables HTTP_PROXY and HTTPS_PROXY set, and this causes the problem with git inside the Rancher Server container.

@averri Were you able to resolve this?

@joostliketoast @averri Please reopen if you still have issues.

I'm getting same issue in rancher v1.4.1.
ive added following catalog url in settings.. https://github.com/alfredfrancis/rancher-catalogs
when i refresh im getting following log only..
time="2017-03-01T14:39:27Z" level=info msg="Using catalog pdd=https://github.com/alfredfrancis/rancher-catalogs.git"

getting the same with rancher 1.6.24 and internet access is completely opened


add navbar enhancements

add customizable search placeholder/button text and label color
feat
Fixes #131
Changes proposed in this pull request:

Added custom search placeholder/button text
Added custom label color
Restyle naming conventions onSearchButtonClick style to a scoped onClickButton style
Propose new format for documentation
(Separate brand and search properties which are class instances into individual doc files of Navbar folder for better structure, organization and navigation.

I had a wrong email configured on my git so I'm having trouble signing this license again. I will try to create it again with the correct configuration.


MAX_CONTENT_LENGTH is not respected

When I send a large payload to the service, the flask config is not respecting the config and let the program continue to run.
This line is not hit ever: https://github.com/pallets/werkzeug/blob/6df9e5bdb9d216fcf2989ce051cd11b763cef4a0/werkzeug/formparser.py#L194

Expected Behavior
I am expecting to get 413 error in response.
from flask import Flask, request, jsonify, abort

app = Flask(__name__)
app.config['MAX_CONTENT_LENGTH'] = 100

...

@app.route('/myendpoint', methods=['POST'])

...

if __name__ == "__main__":
    app.run(host="<IP_ADDRESS>", port=12345, debug=True)

Actual Behavior
Tell us what happens instead.
Paste the full traceback if there was an exception.

Environment

Python version:  Both python 2.7 and 3.6
Flask version: 0.12.2
Werkzeug version: 0.14.1

I can't reproduce your issue. You must actually attempt to access the data to trigger form parsing and see the error. The content length only applies to form data, not arbitrary post bodies.
It appears that you're using the development server in production (binding to <IP_ADDRESS>). Do not use the development server in production. All production WSGI and HTTP servers have more robust configuration for request limits that you should use.

Addressed by https://github.com/pallets/werkzeug/pull/2620, although my previous comment still stands.


Pass argument's index to equalityCheck function

will allow to conditionally apply different checks on different arguments, i.e. defaultEqualityCheck for everything, but _.isEqual in case of non-immutable argument

Coverage remained the same at 100.0% when pulling 31c5f648cd28a39a31041935470b409e3c103fe7 on bsideup:patch-1 into e5d78d28fe5bf68d4600c8911bb9da39d180b78f on reactjs:master.

Current coverage is 100% (diff: 100%)

Merging #158 into master will not change coverage

@@           master   #158   diff @@
====================================
  Files           1      1
  Lines          12     12
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits           12     12
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update e5d78d2...31c5f64

Hey @bsideup, thanks for the PR! I don't see any reason why we shouldn't merge this, but I'm going to leave it open for the moment and aim to make it part of the v3 release.

Hi, I can't see this PR merged in master branch. Is there any problem?
Thank you


cleos set contract -h spelling errors

Two main issues:

Flag options such as -c/--clear has incorrect spelling of "Rmove" rather than "Remove"
Inconsistent capitalization of first letter of sentences, about 1/2 each way.

`$ cleos set contract -h
Create or update the contract on an account
Usage: cleos set contract [OPTIONS] account [contract-dir] [wasm-file] [abi-file]
Positionals:
account TEXT                The account to publish a contract for (required)
contract-dir TEXT           The path containing the .wasm and .abi
wasm-file TEXT              The file containing the contract WASM relative to contract-dir
abi-file TEXT               The ABI for the contract relative to contract-dir
Options:
-h,--help                   Print this help message and exit
-a,--abi TEXT               The ABI for the contract relative to contract-dir
-c,--clear                  Rmove contract on an account
--suppress-duplicate-check  Don't check for duplicate
-x,--expiration             set the time in seconds before a transaction expires, defaults to 30s
-f,--force-unique           force the transaction to be unique. this will consume extra bandwidth and remove any protections against accidently issuing the same transaction multiple times
-s,--skip-sign              Specify if unlocked wallet keys should be used to sign transaction
-j,--json                   print result as json
-d,--dont-broadcast         don't broadcast transaction to the network (just print to stdout)
--return-packed             used in conjunction with --dont-broadcast to get the packed transaction
-r,--ref-block TEXT         set the reference block num or block id used for TAPOS (Transaction as Proof-of-Stake)
-p,--permission TEXT ...    An account and permission level to authorize, as in 'account@permission' (defaults to 'account@active')
--max-cpu-usage-ms UINT     set an upper limit on the milliseconds of cpu usage budget, for the execution of the transaction (defaults to 0 which means no limit)
--max-net-usage UINT        set an upper limit on the net usage budget, in bytes, for the transaction (defaults to 0 which means no limit)
--delay-sec UINT            set the delay_sec seconds, defaults to 0s`

I did some analysis of cleos/main.cpp and found that 78 message begin with an upper-case character and 354 begin with lower.
grep localized main.cpp | awk -F 'localized' '{print $2 FS "."}' | cut -c3 | awk 'BEGIN{ FPAT="[a-zA-Z]"; l=u=0 } { for (i=1; i<=NF; i++) ($i~/[a-z]/)? l++ : u++; printf "upper: %d, lower: %d\n", l, u }'
Although I believe these should all be upper-case, the preponderance are lower-case.

If you want to submit a PR, I think lowercase for all would be best.

I created a PR for point #1 (#8130 )
I wasn't sure 'all' of the localizations should just be switched case. so left that part alone.

I create a PR for all of this after talking with Jonathan and digging a bit further, it turns out that the majority of flag descriptions are in fact in upper-case. As such, it makes the most sense to fix it by upper-casing the 30 or so descriptions that were not.

Fixed by #8130 & #8131


Remove minify to make the code debuggable

I just got an error somewhere deeply inside of this library and cannot
figure out what's going on because the code here is minified and chrome
is not able to apply formatter.
Would be good to publish the new patch soon so I could find the problem
in my code.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@TrySound We don't minify before we publish. We do transpile the code though. We offer three different distributions with varying degrees of transpilation.

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
The es6 distribution would be the best for debugging, the es5 distribution is intended for old browsers.
The dists have entry points listed in package.json, but the es6 key is not recognized directly by bundlers and must be selected manually. In webpack that can be done via the resolve.mainFields setting, not sure about rollup etc.
Hope that helps a little.

Here's esm pretty printed (by chrome) code. And it's not debuggable.

You are right. I had removed babel-minify from the major frameworks but apparently still present here in the smaller frameworks.
Always experimenting with ways to reduce the bundle size...

Would be good to publish a patch release with this change

@TrySound Just published 5.3.0-alpha.2, let me know how it goes


format: add statistics for tables, columns, queries, etc.

More research is needed on what systems typically support.
This would make ADBC more useful in situations where it supplies data to other systems, since then those systems could query statistics using a standard interface and integrate them into query planning. (Interestingly, Spark at least doesn't seem to have this in DataSourceV2 - I suppose the smarts are directly in their JDBC support.)
Examples:

Estimated result set size for queries (basically, a semi-standardized EXPLAIN (ANALYZE))
Parquet-style min/max/null % statistics per column

Possibly: add ConnectionGetStatistics whose result set schema is something like
- catalog
- db_schema
- table_name
- statistic_type: min, max, null percentage, row count, ndv
- column_name
- value (union of int64, double, uint64, string, binary?)

so for a table, you would have a row per column per statistic type, and a row per statistic type (for table-wide statistics: row count, ndv)
(do we want to/how would we account for partitions, in the sense of Flight SQL, etc.?)

JDBC
getIndexInfo

Oriented around database indices
Provides row count and ndv
Also provides page count and ordering
Differentiates between exact/approximate; this can affect performance of the call

=> We may want a statistic for "abstract size"? (But the values wouldn't be comparable between drivers.)
=> Is ordering useful?
=> Exact/approximate may also be useful to indicate
ODBC
SQLStatistics

Effectively the same as JDBC

PostgreSQL
https://www.postgresql.org/docs/current/planner-stats.html and https://www.postgresql.org/docs/current/view-pg-stats.html

Row count (may be out of date), page count
null percentage
a very odd ndv estimate
histograms, most common elements, etc.
average column width (~= average size of a row in a column; i.e. an estimate of string length, etc?)

=> How should we define ndv?
=> Do we want to be able to map through "most common elements" etc. or should we leave that alone? (Probably leave it alone)
=> We may want to define a column width statistic

So proposal is for:
AdbcConnectionGetStatistics(struct AdbcConnection*, const char* catalog, const char* db_schema, const char* table_name, bool approximate, struct ArrowArrayStream* out);

- Parameters allow filtering down to an individual table, or you can request data for multiple tables at once
- "approximate" is an enum allowing you to request exact statistics, or just get approximate/best-effort/out of date statistics

The result set has schema:
- catalog: str
- db_schema: str
- table_name: str
- statistic_type: str (one of null percentage, row count, ndv, byte_width or a database-specific value)
- column_name: str (null if table-wide statistics)
- value: double
- is_approximate: bool

column_name is null if the statistic applies to the whole table
null_percentage is a value in [0, 1] representing the % of rows in the column that are null
ndv is the number of distinct values in the column (I'm tempted to take the PostgreSQL definition: positive means a fixed number of distinct values, negative means a percentage of distinct values)
row count is a value in [0, inf)
byte_width is a value in [0, inf) representing the average size in bytes of a row in the column (e.g. for a string column, this would be the average string size)

unknown values should be null, or the whole row should simply be omitted
Questions:

Do we care about min, max, etc.? IMO no, this complicates the encoding of the 'value' in the result, and utility is questionable. (But maybe we do want value to be at least union[double, string] to perhaps allow for this?)
Do we encode the statistic names as strings, or requiring dictionary encoding, or specifying an enumeration? (I would prefer dictionary encoding, but this complicates implementation a bit. The benefit is that if we specify some fixed dictionary values, we can save space on the common values and avoid lots of string comparisons while still allowing self-describing extensibility by vendors)

Other potential statistics:

Calcite defines these: https://calcite.apache.org/javadocAggregate/org/apache/calcite/rel/metadata/BuiltInMetadata.html
If we were to provide a direct equivalent of getIndexInfo, we could possibly also map ColumnUniqueness, Collation. It may work to allow column_name to be list<str>.

In addition to Calcite, Hive contains a fairly decent statistics set, especially since it has column statistics as well as table statistics.

Ah, thanks for the pointer. It seems Hive also stores min/max N values, histograms, percentiles, and average/sum of numeric columns.
This overlaps somewhat with PostgreSQL, so maybe we should try to support them. That said, encoding polymorphic types (if we want min/max of say a string column) and list types is a bit of a pain in Arrow (for min/max N, histograms, etc.) but it's doable via a union.

The proposal was updated to include min/max value and max byte width as standardized statistics. Digging into the Hive code, histograms are implemented but top/bottom K never were. The proposal allows for backends to return custom statistics so Hive/Postgres could still encode histograms (the encoding with Arrow gets very messy, however, given the lack of an 'any' type; they would have to pack the histogram values into a binary column).

Looking at JDBC drivers:

PostgreSQL basically just gives you row count of columns with indices on them (including primary key). The debugger shows it executes this query internally:
SELECT
  tmp.TABLE_CAT,
  tmp.TABLE_SCHEM,
  tmp.TABLE_NAME,
  tmp.NON_UNIQUE,
  tmp.INDEX_QUALIFIER,
  tmp.INDEX_NAME,
  tmp.TYPE,
  tmp.ORDINAL_POSITION,
  trim(
    both '"'
    from
      pg_catalog.pg_get_indexdef(
        tmp.CI_OID, tmp.ORDINAL_POSITION,
        false
      )
  ) AS COLUMN_NAME,
  CASE tmp.AM_NAME WHEN 'btree' THEN CASE tmp.I_INDOPTION[tmp.ORDINAL_POSITION - 1] & 1 :: smallint WHEN 1 THEN 'D' ELSE 'A' END ELSE NULL END AS ASC_OR_DESC,
  tmp.CARDINALITY,
  tmp.PAGES,
  tmp.FILTER_CONDITION
FROM
  (
    SELECT
      NULL AS TABLE_CAT,
      n.nspname AS TABLE_SCHEM,
      ct.relname AS TABLE_NAME,
      NOT i.indisunique AS NON_UNIQUE,
      NULL AS INDEX_QUALIFIER,
      ci.relname AS INDEX_NAME,
      CASE i.indisclustered WHEN true THEN 1 ELSE CASE am.amname WHEN 'hash' THEN 2 ELSE 3 END END AS TYPE,
      (
        information_schema._pg_expandarray(i.indkey)
      ).n AS ORDINAL_POSITION,
      ci.reltuples AS CARDINALITY,
      ci.relpages AS PAGES,
      pg_catalog.pg_get_expr(i.indpred, i.indrelid) AS FILTER_CONDITION,
      ci.oid AS CI_OID,
      i.indoption AS I_INDOPTION,
      am.amname AS AM_NAME
    FROM
      pg_catalog.pg_class ct
      JOIN pg_catalog.pg_namespace n ON (ct.relnamespace = n.oid)
      JOIN pg_catalog.pg_index i ON (ct.oid = i.indrelid)
      JOIN pg_catalog.pg_class ci ON (ci.oid = i.indexrelid)
      JOIN pg_catalog.pg_am am ON (ci.relam = am.oid)
    WHERE
      true
      AND ct.relname = 'mytable'
  ) AS tmp
ORDER BY
  NON_UNIQUE,
  TYPE,
  INDEX_NAME,
  ORDINAL_POSITION

SQL Server gives you the row count for the table, and tells you about columns with a UNIQUE constraint, but doesn't give you much else. Internally it runs EXEC sp_statistics_100 ?,?,?,?,?, ?

It seems we shouldn't expect much here from JDBC (and to be fair, getIndexInfo was meant to get info about indices, not really get us detailed statistics), so if we want detailed statistics we'll have to do it per database.


Use default TAG=dev to prevent accidental push on main by quay admins

Yesterday I accidentally pushed the "main" image on quay (I rollbacked minutes later).
This change should avoid such a situation

/approve


Cocoapods support

Description

Added AutoLayoutHelperSwift podspec
Updated documentation

Notes

Will add to trunk once this PR is merged and v1.0.0 is created

Status

[x] Review

Current coverage is 99.20% (diff: 100%)

Merging #23 into master will not change coverage

@@             master        #23   diff @@
==========================================
  Files             4          4
  Lines           503        503
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            499        499
  Misses            4          4
  Partials          0          0

Powered by Codecov. Last update 4767367...2af52ba


docs: add mkdocstrings for api reference

Issue #, if available: #346 #481
Description of changes:

Pre-work required before revamping Event Source Data Classes and Parser documentation. This PR auto-generate and embed API reference docs.
As part of this work, we need to reformat our docstrings since mkdocstrings doesn't support Numpy format we've been using.
Checklist

[x] Meet tenets criteria
[x] Update docs
[x] PR title follows conventional commit semantics

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #517 (0bd4142) into develop (f61b02f) will decrease coverage by 0.28%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #517      +/-   ##
===========================================
- Coverage    99.90%   99.62%   -0.29%
===========================================
  Files          107      107
  Lines         4266     4258       -8
  Branches       208      212       +4
===========================================
- Hits          4262     4242      -20
- Misses           1        8       +7
- Partials         3        8       +5

Impacted Files
Coverage Δ

aws_lambda_powertools/tracing/tracer.py
100.00% <100.00%> (ø)

aws_lambda_powertools/utilities/parser/types.py
71.42% <0.00%> (-28.58%)
:arrow_down:

...wertools/utilities/idempotency/persistence/base.py
92.99% <0.00%> (-6.37%)
:arrow_down:

...lambda_powertools/utilities/parser/models/apigw.py
97.36% <0.00%> (-0.04%)
:arrow_down:

aws_lambda_powertools/logging/logger.py
100.00% <0.00%> (ø)

aws_lambda_powertools/metrics/metrics.py
100.00% <0.00%> (ø)

aws_lambda_powertools/shared/constants.py
100.00% <0.00%> (ø)

aws_lambda_powertools/logging/formatter.py
100.00% <0.00%> (ø)

aws_lambda_powertools/utilities/batch/base.py
100.00% <0.00%> (ø)

... and 7 more

Continue to review full report at Codecov.

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

Pausing this work to prioritize #563

Closing as a lot has changed since then in mkdocstrings, and I'll make one PR for each utility instead to split the work.


Add Stories to Windows Terminal

Add a “Stories” Feature to Windows Terminal
Stories are the new hotness. Snapchat invented Stories but the paradigm of ephemeral updates has since been adopted by Instagram, WhatsApp, Facebook, LinkedIn, Twitter, and most recently, Spotify. There is even a VS Code extension that adds this feature.
Why should LinkedIn get all the fun?! Windows Terminal might be a singular experience (but with user profiles, is it really), but that doesn’t mean we shouldn’t create an ephemeral social layer into it.
Windows Terminal “Stories” could be in gist form (a la GitHub) or scripts in your favorite shell language (PWSH or BASH or ZSH, in da clurb we all fam), they could also be print screens of your current terminal session. Because who doesn’t want to show off their latest Neofetch/winfetch ASCII art!
As a longterm goal, there could even be a way to share a gist/link to your config file to share your specific terminal preferences and font/color information.
Proposed technical implementation details (optional)
In order to see Stories from others (assuming we don’t want to focus just on local users), we would need to run some sort of web server that ties into some type of social network for followers/displays. GitHub would probably be ideal for that.
Having said all this, as good of a feature as I believe Stories would be, it would probably require a lot of resources and overhead, not to mention possible performance concerns. Perhaps this is a better request for Hyper, since it is Electron and basically running a web browser anyway. (No shade to Hyper — Hyper is great and beautiful and I’m just teasing out of love!)
In fact, the more I write about this. Maybe it’s a bad idea.

You got my support on this @filmgirl. +1

rooting for you @filmgirl 🎉

11/10, want to see this happen! 💜

Knowing that this is possible my life will not be the same without it

We need this.

I thought the Terminal was for productivity. Am I wrong?

I guess probably something could be hacked together with Cowsay and Fortune. This would get closer to feature parity with a real Linux machine. 😏

I can't believe it hasn't already been implemented, this is a must have feature.

This needs a kickstarter campaign

Can this be integrated with #469?

most recently, Twitter

I think Spotify was more recent

most recently, Twitter

I think Spotify was more recent

Right you are!

I haven't seen any feature request in this repo having this much reactions (and upvotes) in such short amount of time. 🤯

This has my full support \o/

I would love to see this happen.

How have I been using Terminal without this feature for so long? I'm using plain old terminal until we have it!

Wondering if Terminal users are mentally prepared to such amount of social activity in their lives.. switching from 0 social life to this directly might be... overwhelming 😄

Wondering if Terminal users are mentally prepared to such amount of social activity in their lives.. switching from 0 social life to this directly might be... overwhelming 😄

@Don-Vito Are you talking about me? 😄

Wondering if Terminal users are mentally prepared to such amount of social activity in their lives.. switching from 0 social life to this directly might be... overwhelming 😄

@Don-Vito Are you talking about me? 😄

About myself actually 😄

Doesn't it look cool?   https://twitter.com/kose__suat/status/1329514405818732545

Well this thread was a good hilarious read to start my week. Thanks for that 🤣
I know that this is 90% a meme post from twitter, but this is also our actual work tracker, so I've gotta be at least 5% serious here:
I don't believe the Terminal is the place to implement most of this.

We've already got a commandline ecosystem problem of users just executing random scripts that they download with curl - if we're letting users install scripts that they saw on someone's story, then i can guarantee you there'll be scripts like "Run Graphical Applications in WSL!!!" that actually just rm -rf /mnt/c. I don't want to be held responsible for contributing to that problem.
I think GitHub gists are already better suited for a lot of this - they've already got syntax highlighting for different languages, they've already got accounts set up, and authentication, and hey, they've already got a web-scale website that can host all this, and frankly I'm not prepared, nor is anyone on the team, to build that ourselves.
We've also already got #469 on the backlog for recording Terminal output to the asciinema format, for sharing on https://asciinema.org. Again, that's another site that's probably better suited for hosting recordings of terminal sessions, rather than us standing this up on our own.

So those are reasons why I would reject this feature request. However, this thread is definitely @cinnamon-msft's responsibility, so I'll let them handle it.

As far as the following is concerned:

there could even be a way to share a gist/link to your config file to share your specific terminal preferences and font/color information.

I believe there's been discussion about that in the past, and that I'm on board with. "Stories", not so much.

+1 this is a vital feature. pls ship @cinnamon-msft 🙏🏻

This definitely was a fun read, but I agree with @zadjii-msft that this doesn't really make sense for Terminal. Kudos to @filmgirl for writing such an entertaining feature request, however I will have to close this issue since we aren't planning to implement it. 😄

On the other hand a native support for twitter could prevent us from missing the meme post:

@Darth4212 but is it really ?

@Darth4212 You use the terminal for coding?

@Supesu Terminal? Coding? You must be insane, that is impossible!

@Supesu Terminal? Coding? You must be insane, that is impossible! The terminal exists only for cmatrix

@Finermeerkat137 - you should try it. I recently switched to Terminal from VS 2019 and am really happy since then: same level of code completion and refactoring with almost twice less memory!

Could you maybe engage who ever is doing the visual studio code stories: https://marketplace.visualstudio.com/items?itemName=bar9.stories
Having something that is uniform across Microsoft development platforms will have a far better chance of being more than just a gimmick and have a solid base to grow.

:shipit:

Btw can we call this Stories for Terminal E5 X?

I think someone could implement this as an extension

I seriously hope this is just a joke post

@Supesu I use Terminal to access Vim on WSL as my main editor

It's a fun-take and I wanted to upvote it for the fun part, but then I thought it may send the wrong message so I had to downvote it, just to not confuse newcomers. ;)
Many people want super-simple stories - the terminal story. They want a terminal, that's the story! But if people want pink ribbon hipster dancing marquee tags in the terminal, well, the terminal can always be as customizable as possible. Perhaps make the themes epic as much as possible. But for me personally? Simplicity. (It's ok to have more options). And the simplest story is to keep it so simple that stories are not necessary. USING the terminal is already the best story. ;)
(Admittedly I am actually more likely to use e. g. KDE Konsole + WSL on windows these days than windows Terminal BUT this is not always possible, and in these cases, then, Windows Terminal is so much nicer than oldschool cmd.exe ...)

It's a fun-take and I wanted to upvote it for the fun part, but then I thought it may send the wrong message so I had to downvote it, just to not confuse newcomers. ;)
Many people want super-simple stories - the terminal story. They want a terminal, that's the story! But if people want pink ribbon hipster dancing marquee tags in the terminal, well, the terminal can always be as customizable as possible. Perhaps make the themes epic as much as possible. But for me personally? Simplicity. (It's ok to have more options). And the simplest story is to keep it so simple that stories are not necessary. USING the terminal is already the best story. ;)
(Admittedly I am actually more likely to use e. g. KDE Konsole + WSL on windows these days than windows Terminal BUT this is not always possible, and in these cases, then, Windows Terminal is so much nicer than oldschool cmd.exe ...)

Could you maybe engage who ever is doing the visual studio code stories: https://marketplace.visualstudio.com/items?itemName=bar9.stories
Having something that is uniform across Microsoft development platforms will have a far better chance of being more than just a gimmick and have a solid base to grow.

@thenexus00 I thought you were kidding, but 11,819 installs...

This explains a lot and why microsoft made ton of bad decisions recently, maybe the people at the top are delusional?
now question, how she got the job?

Even the Windows Kernel says NO!

no

no thanks

nsg 650

+1

Please don't fill the issue tracker with jokes.

@zadjii-msft or @DHowett Please lock this thread

Alright yea, I thought we could all play along and enjoy a nice, lighthearted joke thread, but I guess I was wrong. I'm not gonna take lightly to comments disparaging any of our colleagues. Perhaps having a sense of humor is a desirable trait in an employee, something some participants in this thread are clearly lacking.
Obviously, we're not adding Stories to the Terminal. Anyone can read the thread and figure that out, if that's not asking too much.

This explains a lot and why microsoft made ton of bad decisions recently, maybe the people at the top are delusional?
now question, how she got the job?

get out of here with your misogynist shit, @russhy


VisitAKSCluster fails to get vnetSubnetID property when kubenet network plugin is used

Description of the issue
When running Export-AzRuleData on a RG with my AKS cluster that is using kubenet instead of Azure CNI, the following error happens:
VisitAKSCluster: C:\Users\armcleod\Documents\github-repos\PSRule.Rules.Azure\out\modules\PSRule.Rules.Azure\PSRule.Rules.Azure.psm1:1140:60
Line |
1140 |  … ainerService/managedClusters' { VisitAKSCluster @PSBoundParameters; }
     |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | The property 'vnetSubnetID' cannot be found on this object. Verify that the property exists.

To Reproduce
Steps to reproduce the issue:
Export-AzRuleData -Subscription '<subID>' -Tenant '<tenantID>' -ResourceGroupName '<rgName>'

Expected behaviour
Not error out for invalid vnetSubnetID property.
I think this should check if properties.networkProfile.networkPlugin is not set to kubenet before adding this property. Could also just check if it set to azure.
https://docs.microsoft.com/en-us/azure/templates/microsoft.containerservice/managedclusters?tabs=json#containerservicenetworkprofile-object
Let me know if I'm not running something properly here 😄 .

@ArmaanMcleod Thanks. Makes sense to me. I'll review the PR.


Release 0.16.0?

I wonder if it would be possible to make a 0.16.0 release; there appears to be nothing open on the milestone (other than issue once I open it).
I'm mostly interested in #527, but there are a few other bug fixes from a while ago that would be good to get out there.

Thanks for the pings @QuLogic. Yes we should - I'm horribly behind on PR reviews (the "last mile effect" from numpy 2.0 is taking its toll), and I think we'd like to get some of those in - gh-594 in particular.
Let me try and get that done over the next few days. It'd be good to set a goal of getting a release out this week. WDYT @dnicolodi?

It would be nice to get a release out. There are a few PR pending. It would be nice to get these in, but I don't see any reason why we cannot have a release without those. The release process is relatively lightweight, thus we can follow up with another release soon after.

Release is up on PyPI now: https://pypi.org/project/meson-python/0.16.0/ - thanks for the help & patience!

Thanks for taking care of the release!

Something went wrong with publishing the documentation. I'm having a look


RFC: sockops: fix missing /usr/include/asm symlink

cilium fails to compile bpf_sockops.o because /usr/include/asm doesn't
exist on the docker image
error:
level=error msg="Failed to compile bpf_sockops.o: exit status 1" compiler-pid=228 linker-pid=229 subsys=datapath-loader
level=warning msg="In file included from /var/lib/cilium/bpf/sockops/bpf_sockops.c:29:" subsys=datapath-loader
level=warning msg="In file included from /usr/include/sys/socket.h:33:" subsys=datapath-loader
level=warning msg="/usr/include/bits/socket.h:390:10: fatal error: 'asm/socket.h' file not found" subsys=datapath-loader
level=warning msg="#include <asm/socket.h>" subsys=datapath-loader
level=warning msg="         ^" subsys=datapath-loader
level=warning msg="1 error generated." subsys=datapath-loader
level=error msg="failed compile sockops/bpf_sockops.c: Failed to compile bpf_sockops.o: exit status 1" subsys=sockops
level=error msg="Failed to compile bpf_redir.o: exit status 1" compiler-pid=231 linker-pid=232 subsys=datapath-loader
level=warning msg="In file included from /var/lib/cilium/bpf/sockops/bpf_redir.c:29:" subsys=datapath-loader
level=warning msg="In file included from /usr/include/sys/socket.h:33:" subsys=datapath-loader
level=warning msg="/usr/include/bits/socket.h:390:10: fatal error: 'asm/socket.h' file not found" subsys=datapath-loader
level=warning msg="#include <asm/socket.h>" subsys=datapath-loader
level=warning msg="         ^" subsys=datapath-loader
level=warning msg="1 error generated." subsys=datapath-loader
level=error msg="failed compile sockops/bpf_redir.c: Failed to compile bpf_redir.o: exit status 1" subsys=sockops
Signed-off-by: Nirmoy Das<EMAIL_ADDRESS>

This change is

I couldn't test it on my machine as make docker-image failed to fetch builder image from local repo.

seems the soft link exist :/
nirmoy@c176:~> sudo docker run --rm cilium/cilium-builder:2018-11-09 ls -l /usr/include/asm
lrwxrwxrwx 1 root root 20 Sep 17 07:07 /usr/include/asm -> x86_64-linux-gnu/asm
nirmoy@c176:~> sudo docker run --rm docker.io/cilium/cilium-builder:2018-11-09 ls -l /usr/include/asm
lrwxrwxrwx 1 root root 20 Sep 17 07:07 /usr/include/asm -> x86_64-linux-gnu/asm

I think we can just #define AF_INET and AF_INET6 in bpf_sockops.h its the only thing we care about here and then we avoid pulling in another pkg.

I'll write the patch in just a few moments. Thanks @nirmoy for finding and tracking this down. Let me know if you have any objections to doing the above instead.

@nirmoy Here is what I was thinking. Also happy to add your Signed-off if your OK with the patch I borrowed your patch description. Thanks!
https://github.com/cilium/cilium/pull/6216

Sounds good to me, Thanks @jrfastab


saveHar ignores directory path

Description
Using     "@neuralegion/cypress-har-generator": "^5.14.0",
Try to save the file in a path that is determined at run time.
Here harPath is admin/blockScheduling/officerSetup/ & harFIleName is 'User-needs-to-set-up-an-officer-and-assign-them-to-a-specific-group-dev-chrome.har'
The full path was created before the saveHar

File saved to root ignoring path

Debugger showing harPath

   cy.saveHar({
          fileName: `/${harPath}/${harFileName}`
        });

The env is setup
env: {
  "hars_folders": "cypress/hars"
}

Steps to reproduce

try to save a file to a sub directory below the hars_folders

Expected behavior
HAR file created in subdirectory
Actual behavior
HAR file created in hars_folder ignoring the subdirectory path
Screenshots
See above

@bartonhammond thanks for the report 👍🏾 fileName is the name of the file in the pathname (for details please refer to basename), the directory will be ignored by design. If you want to change the destination folder programmatically, you can use the outDir option as follows:
cy.saveHar({ outDir: harPath, fileName: harFileName })

@derevnjuk  Thanks for the help.
The file isn't written out at all now.  Stopping in the debugger I see the values are set correctly but the outDir directory is empty.

Needed the entire path
let harsFolder = Cypress.env("hars_folders");
let harPath = "admin/blockScheduling/officerSetup/";
let harFileName = `${scenarioName}-${env}-${browser}.har`

 cy.saveHar({
    outDir: `${harsFolder}/${harPath}`,
    fileName: harFileName,
  });


file 'launch_sim.launch.py' was not found

What happened?
file 'launch_sim.launch.py' was not found in the share directory of package 'robolaunch_cloudy_simulator' which is at '/home/yanlulu/cloudy_ws/install/robolaunch_cloudy_simulator/share/robolaunch_cloudy_simulator'
What did you expect to happen?
I cannot find the file "launch_sim.launch.py" in folder "robolaunch_cloudy_sim/launch "
How can we reproduce it (as minimally and precisely as possible)?
Launch the simulation
ros2 launch robolaunch_cloudy_simulator launch_sim.launch.py

Looks like the README is out of date. Have you tried launching gazebo.launch.py?

Looks like the README is out of date. Have you tried launching gazebo.launch.py?

[gzserver-2] Error [Converter.cc:113] Unable to convert from SDF version 1.9 to 1.7
and nothing is displayed in Gazebo window

Looks like the README is out of date. Have you tried launching gazebo.launch.py?

I have replaced the world file, and it is functioning properly. Thank you.

Glad you handled it. Converted the issue to docs issue.


<EMAIL_ADDRESS>wrong info

hi, i found that you app don't work correct on<EMAIL_ADDRESS>package thus it has at least 1 high vulnerability by snyk and 1 critical and 2 high by deps.dev:
https://security.snyk.io/package/npm/loader-utils/2.0.1
https://deps.dev/npm/loader-utils/2.0.1

Hi @ultramaxim, thanks for reporting!
Currently, we're not supporting package versions, which means you will always get the insights for the latest version.


Fixes for defaults in SCSS and correct fluid column calcs

Hi,
I apologize if my pull request is not being done correctly. This is my first ever git-hub pull request.
The way the grid.scss works currently, doesn't work right if you are using sub-columns (inside a row) when in fluid mode. I've made some tweaks to hopefully fix that.
Also, I added some !default declarations to your defaults.
Thanks for putting this framework together! I really like how small and efficient it is!
I hope my changes are helpful.

Hi Phil, thanks for your work. Your solution to the gridsystem-width worked, but @daffydowden had the idea of using a function instead, which is what I ended up implementing. Thanks again.

Thanks Tyler.
Actually, ultimately I found that the whole notion of percentage based
columns was flawed for what I was doing since different browsers
handle rounding differently, and I could never get complex columns to
line up right, or reliably fill the whole space.
I ended up building my own solution, using flexbox, that falls back to
pixel based columns for IE. I hope to publish it soon.
I was very much inspired by your system, and a number of others. Thank
you for all your hard work!
-Phil
On Wed, Jan 11, 2012 at 5:31 AM, Tyler Tate
<EMAIL_ADDRESS>wrote:

Hi Phil, thanks for your work. Your solution to the gridsystem-width worked, but @daffydowden had the idea of using a function instead, which is what I ended up implementing. Thanks again.

Reply to this email directly or view it on GitHub:
https://github.com/twigkit/semantic.gs/pull/26#issuecomment-3446462

--
Phil Quinn, President, Quinn Interactive, Inc.
<EMAIL_ADDRESS>(415) 296-9000


Login (or auth) service

Main functionality implemented,
docs is WIP

@chriku Couldn't answer to your comment on the top of your first review. But refactored logging in eb89d8c


Components and patterns that need a guidance change to meet WCAG 2.1

What
We need to change our examples or add improved content to our guidance pages in order to resolve issues from the DAC Audit May 2023.
WCAG criteria

Step-by-step navigation, Step-by-step navigation 'or' headings must be nested under their parent step headings alphagov/govuk-frontend#2794 and usability criteria Step-by-step navigation does not convey all of the information for screen reader users when viewing them as forms alphagov/govuk-design-system#3021
Password (show/hide), Pages with 2+ password fields must use different programmatic labels for 'show' and 'hide' buttons on those password fields alphagov/govuk-frontend#2795
Tabs, Tab components should show visible headings for all sections on mobile screen sizes alphagov/govuk-frontend#2797
Links, Links to Welsh versions of content should be understandable even when out of context alphagov/govuk-frontend-docs#207

Usability criteria

Error message, Error summary, Error messages should use the same label text as the input when referring to an input alphagov/govuk-frontend#2801
Pagination, Pagination for smaller numbers of pages does not show current page number alphagov/govuk-frontend#3682
Character count, Character count is hidden until you approach a character threshold alphagov/govuk-frontend#3689

Further documentation
DAC audit 2023 results spreadsheet.
This work is a continuation from the previous DAC audit cards, alphagov/govuk-frontend#3814, alphagov/govuk-frontend#3592 and alphagov/govuk-frontend#3329.
Why
This work supports our efforts towards the Epic: Update styles, components and patterns to WCAG 2.2 AA alphagov/govuk-frontend#3040.
As we approach the publishing date for WCAG 2.2, we want to ensure our existing govuk-frontend elements are meeting all WCAG 2.1 AA criteria. The only way to pass WCAG 2.2 AA is to also meet all criteria in WCAG 2.1 AA (with one exception, where a criterion is being removed).
We're doing other work to assess where updates are needed to align elements with the 9 new WCAG 2.2 criteria, but we likely don't have capacity to run an internal audit across all of the existing 78 WCAG criteria.
### Tasks
- [ ] https://github.com/alphagov/govuk-design-system/issues/2794
- [ ] https://github.com/alphagov/govuk-design-system/issues/3021
- [ ] https://github.com/alphagov/govuk-design-system/issues/2795
- [ ] https://github.com/alphagov/govuk-design-system/issues/2797
- [ ] https://github.com/alphagov/govuk-design-system/issues/2796
- [ ] https://github.com/alphagov/govuk-design-system/issues/2801
- [ ] https://github.com/alphagov/govuk-frontend/issues/3682
- [ ] https://github.com/alphagov/govuk-frontend/issues/3689
- [ ] https://github.com/alphagov/govuk-design-system/issues/2799
- [ ] https://github.com/alphagov/govuk-design-system/issues/3097
- [ ] https://github.com/alphagov/govuk-design-system/issues/3105

I think unless anyone can suggest otherwise that this has now been completed 🎉. I'll close the issue and move to Done 🏁


Mesos UI does not require authentication to view

This may have to be pushed back to a later release. Still doing research on this.
https://issues.apache.org/jira/browse/MESOS-1923
https://issues.apache.org/jira/browse/MESOS-809

With pull #135, closing this issue.

Great! Thx Steve


Color transition

First of all, this library is awesome. It saved me a lot of time and it looks awesome. Now, my question is about a color transition. I made 4 custom slides and the slider works, but there is no that smooth color transition between slides like you have in your README file. Do you know maybe why is that?

Hi @ilovrencic! Can you please add some code that is not working?


Assoc conversion causes unintended value change

This is  a bug.

Prerequisites
yes
Description

The change in readTemplate introduced in https://github.com/laravel-enso/FormBuilder/commit/3726fa139a180b9914755b4eea1f5dbec8a09228#diff-2e39d0f5a27f1453796dcb9b88bc1e21R182 to convert everything to an assoc array instead of using stdClasses is causing an unintended conversion from (default) value {} to [].
This is causing issues for custom elements being saved under a json (array) property (lost data).
Was there a good reason to change this to use assoc? Or just didn't realize the limitations this could introduce?
Steps to Reproduce

Have a (custom) form element with default value {} defined in the .json template
When trying to add a (tested with) numeric key to it, it creates an array of length x instead

Expected behavior

{} in the json template to remain {} in the json returned to frontend
Actual behavior

{} being converted to [] because of the change introduced in https://github.com/laravel-enso/FormBuilder/commit/3726fa139a180b9914755b4eea1f5dbec8a09228#diff-2e39d0f5a27f1453796dcb9b88bc1e21R182

Workaround
Define the value in the form create() function, f.e.: $this->form->value('customField', new \stdClass());

Note that the workaround only works for create, if the db-stored value is {} it still converts it to an array

You shoud be able to do the same in edit, value('custom', $model->custom).
Could you give me more details about the context where you would need that? Maybe I can find a solution.

You should be able to do the same in edit

Realized that after commenting, however this still looks like unexpected behaviour (and is connected to the change to use assoc combined with the obj helper)
context: storing some metadata about a model directly on the model (using json) the way the model is defined & used requires it to be an assoc array (i.e. object, in js terms)... on the front-end which the parse-assoc in the BE is preventing in case of an empty object (as an empty object & array look exactly the same in php after an assoc parse)

I need to look thoroughly in forms / tables and other places where we use the Obj container and see what it takes to replace it with Laravel's collection. It seems that there are too many side effects.

@jlsjonas could you test now and see if the problem is still present?

I'll be upgrading our stack this week & let you know

reopen if still exists


Zarf connect command doesn't work in Vagrant

Zarf binds to <IP_ADDRESS> when doing the zarf connect which conflicts with the networking of the Vagrant box making the traffic not actually accessible outside of the Vagrant vm.
zarf connect is essentially just a wrapper around kubectl port-forward. One solution is to run kubectl port-forward --address <IP_ADDRESS> {EVERYTHING_ELSE}.
This issue is mainly here to acknowledge the issue and give us a place to determine if we want to:

Add a flag to zarf connect to set the address location
Not worry about this since the multi-distro-support PR means we can eventually migrate our examples to docker w/ KIND leading to even simpler example deployments.

Only minor note is it's not actually a wrapper, it's a native go implementation of that same kubectl function.  That matters because it means zarf doesn't require kubectl exist for this to work.

IMO, assuming it doesn't break anything, I'd like to see zarf connect just internally do the equivalent to --address <IP_ADDRESS> without needing a flag. That's assuming nothing breaks somewhere else if that is the case. If other things do break then yeah we'd need a flag added to zarf connect

I think the issue is it's actually a  security risk.   And this currently is an edge case so probably shouldn't be the default behavior, we should always aim to reduce exposure as much as possible.  I think the real compromise is if you need something exposed on <IP_ADDRESS>, then you probably should add an ingress or at least nodeport as those are better suited to hosting external traffic. Alternatively we could add a flag along the lines of "--insecure-public-bind" or something to bind to <IP_ADDRESS>.

Gotcha, yeah I wasn't sure whether there were any security implications.
In that case, maybe just stick with having an --address flag to mimic the established convention from kubectl port-forward?

Yeah that's fair too, I just worry some of zarfs target users would never run such a command or know what to do so might not appreciate the security implications. Either way definitely worth talking about some more.

@thejohnny do you have any good Vagrant POCs on the Hashicorp side?

I think we'd be better off just removing vagrant at this point as all the local distros test Zarf just fine without a VM

The docs no longer refer to Vagrant so this should no longer be a major concern.


What would it take to expose your test helpers?

Since the tests directory isn't empty, I think it would be great to expose your suite of test helpers for developers to use to test drag-and-drop in their own apps.
What would it take to make your test helpers shareable?
Would documenting how they're used be a good start?

Yeah, it would be great to have a way to test my app's drag and drop capability -- or at least, to test that the right action is called.

I agree this would be helpful. I do a similar thing for ember-cli-pagination. Will try and make time to expose them.
Thanks for taking the time to make an issue!

This seems like it should be possible when I read the docs, but I'm having trouble importing the drag helper.
https://github.com/mharris717/ember-drag-drop#test-helpers


"The path to log could not be detected"

Hi, community, I have been trying to convert my EU4 savegame to Victoria 2 off youtube, following the procedure to have this be done. However, I have a serious issue that tells me the following "The path to log could not be detected, and need to be set manually here in the frontend. Was expecting to exist at C:Users\Zach\Videos\EU4toVic2converter\EU4ToVic2\log.txt" I know this is pretty specific but I have no idea how to fix this.

Note "EU4toVic2converter" is the file I made for this mod.

What Idhrendur said.  Also, what video is this?  There are instructions linked in the first page of the forum, every forum post with a release, every Reddit post with a release and I believe on Steam, so a video shouldn't be needed (it shouldn't be a very complicated process)

I downloaded the newest update "EU4ToV2-1.0Ha.zip," went to winrar and extracted the files into the folder I made in the videos document. If you see something wrong in these files, please do point them out.

Thanks for what you've shown us so far. Can you screenshot the rest of the screens from the frontend as it runs, as you keep clicking next?

I reinstalled winrar making sure it is 64 bit, I made sure that I extracted all from the download into the mod file I created, and am still met with these errors and I'm stumped on how to fix this.
The save I attempted to use was not ironman and had no mods enabled, I also did not rename my saves.

I'm not sure about the log file error, but for the actual error causing you problems, just save your game in EU4 as uncompressed.

Wow that's all I had to do, thank you.

That problem is likely the bookmarks file problem described on the release thread on the paradox forums. I forget the details, but essentially you need to edit the bookmarks file in your mod to swap the order of the 1821 and 1836 bookmarks.


(BOLT-241) Load config from file

This commit adds the ability to load config options from a file. This
required a small refactor to seperate config-like options from
command-options. Config like options are all flags and are passed around
with config but may not be read from the config file. The Command
options are those that are not prefaced with flags and are only exposed
to the execute function of the CLI not passed around with the config.
There is a further distinction between global config options and those
that are transport specific. Transport specific options are specified
for each transport in the config file but only map to a single flag for
all transports as command line flags. Most of these flags only work with
the ssh transport now.

CLA signed by all contributors.


Make Emoji keyboard be more like IOS system Emoji keyboard

Through my effort, I have made it.
And I have tested it, it works.
BTW, ios development is one of my hobbies, so maybe some codes seem ugly.
Maybe, you can regard them as a reference.

Wow, great job! I will merge it into a separate branch and give it a run.
I could merge it if it works well and doesn't change too many general parts of the library. However, since UIKit support is being removed in v 4.0, perhaps we should discuss how to make it live beyond that.

Wow, great job! I will merge it into a separate branch and give it a run.
I could merge it if it works well and doesn't change too many general parts of the library. However, since UIKit support is being removed in v 4.0, perhaps we should discuss how to make it live beyond that.

Wow, great job! I will merge it into a separate branch and give it a run.
I could merge it if it works well and doesn't change too many general parts of the library. However, since UIKit support is being removed in v 4.0, perhaps we should discuss how to make it live beyond that.

You are right. Because some older IOS devices need to be supported, I prefer UIKit to SwiftUI.

Wow, great job! I will merge it into a separate branch and give it a run.
I could merge it if it works well and doesn't change too many general parts of the library. However, since UIKit support is being removed in v 4.0, perhaps we should discuss how to make it live beyond that.

You are right. Because some older IOS devices need to be supported, I prefer UIKit to SwiftUI.

Yeah, it's still going to be possible to build UIKit keyboards with SwiftUI. I just won't include those parts in the library.

Yeah, it's still going to be possible to build UIKit keyboards with SwiftUI. I just won't include those parts in the library.

I have made some improvements to make it more flexible and configurable.

I have made some improvements to make it more flexible and configurable.

Ok, prefect! 👍
I'm working on an emoji keyboard now, but will check it out later! Until then, it would help a lot of you could squash the commits into one and give the commit a text in the imperative form (for instance "Make emoji keyboard behave like more like the system one".

Ok, prefect! 👍
I'm working on an emoji keyboard now, but will check it out later! Until then, it would help a lot of you could squash the commits into one and give the commit a text in the imperative form (for instance "Make emoji keyboard behave like more like the system one".

Ok, prefect! 👍
I'm working on an emoji keyboard now, but will check it out later! Until then, it would help a lot of you could squash the commits into one and give the commit a text in the imperative form (for instance "Make emoji keyboard behave like more like the system one".

Done. I create a new PR. See #178

Ok, prefect! 👍
I'm working on an emoji keyboard now, but will check it out later! Until then, it would help a lot of you could squash the commits into one and give the commit a text in the imperative form (for instance "Make emoji keyboard behave like more like the system one".

Done. I create a new PR. See #178


is this will run on windows ?

I want to run this in windows environment, can this db-sync run on it ?

yes


.Net:  .Net: Added AstraDB memory store connector

Motivation and Context
We are going to add Astra as a memory store.
DataStax Astra DB is a serverless vector database that’s perfect for managing mission-critical AI workloads. It’s built on Apache Cassandra®, making Astra DB a highly scalable, reliable database technology. It’s a powerful all-in-one data storage solution, ideal for Generative AI projects.
Description

Add AstraDB connector for dotnet memory connectors.
Add integration tests for that AstraDB memory connector

Contribution Checklist

[x] The code builds clean without any errors or warnings
[ ] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[ ] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

@hakeemsyd We are in the process of updating our memory connector design, the Memory ADR is here: https://github.com/microsoft/semantic-kernel/issues/5887. Here is an example PR which migrates an existing connector to the new design: https://github.com/microsoft/semantic-kernel/pull/8065.
The old design is going to be made obsolete and eventually removed.
Here's how I propose we proceed with this PR:

We will create a feature branch for the new connector
Change this PR to target the feature branch
Create a new PR which adds the implementation of the new design (again targeting the new feature branch)
Merge to main once all of the implementation and tests have been completed

Would you be interested in contributing an implementation using the new design?

@hakeemsyd we have recently announced a new Microsoft.Extensions.VectorData.Abstractions package which we have developed in partnership with the .NET team. We have also started migrating our memory connectors to use these new abstractions and plan to obsolete the old implementations. So we are not taking any new changes to the older memory connectors. If you are interested in contributing am AstraDB memory connector using the new memory abstractions we would consider adding this to the Semantic Kernel.


Add OperatorPlusMinusCC

Add an Operation OperatorPlusMinusCC(operand, sign=+1) that signifies an operator plus (or minus) its complex conjugate. This is primarily to make the structure of an expression clear. Like in #44, the operation should only be created or expanded "on demand".

This was closed by 8f8fe9069d2a8b60fa5f0df43b7db18024a876b6


Azure Pipeline public - yml

Azure Pipeline
Could you please share the Azure Pipeline ?
Evidence or User Insights
This will be nice to add to reproduce fully  the build
Proposal
Add an azure pipeline .yaml
Goals
Perform builds ourselves.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

The YAML for the pipelines is here and the build logs and artifacts for our active CI pipeline are publicly visible, too.

Closing, since this question appears to have been answered, but feel free to reactivate if you don't think part of your question still hasn't been addressed.


🐞 [BUG] - Unable to load shared library 'rust_ffi'

Describe the Bug
Trying to run ProjectOrigin.Electricity.Example from MAC returns an error 'Unable to load shared library 'rust_ffi''.
Unhandled exception. System.DllNotFoundException: Unable to load shared library 'rust_ffi' or one of its dependencies. In order to help diagnose loading problems, consider setting the DYLD_PRINT_LIBRARIES environment variable:
dlopen(/Users/guyheylens/Documents/Coding/registry/src/ProjectOrigin.Electricity.Example/bin/Debug/net7.0/runtimes/osx-arm64/native/rust_ffi.dylib, 0x0001):

To Reproduce
1. Clone GIT repo to local machine (MacOS)
2. Open repository in Jetbrains Rider
3. Run Electricity.Example app
...

Expected Behavior
Example app works as expected.
Screenshots
No response
Desktop

OS: macOS
Version Version 13.4.1

Additional Context
Ex

Fixed in latest release in other repo


Flaky smoke test: Task Quick Pick

VSCode Smoke Tests (Electron)
Task
Task Quick Pick
Tasks: Run Task
icon - icon & color:
Error: Timeout: get text content ' .monaco-editor[data-uri$="tasks.json"] .view-lines' after 20 seconds.
at Code.poll (/Users/runner/work/1/s/test/automation/out/code.js:204:23)
at async Code.waitForTextContent (/Users/runner/work/1/s/test/automation/out/code.js:151:16)
at async Editor.waitForTypeInEditor (/Users/runner/work/1/s/test/automation/out/editor.js:79:9)
at async Task.configureTask (/Users/runner/work/1/s/test/automation/out/task.js:68:13)
at async Context. (out/areas/task/task-quick-pick.test.js:52:17)

/duplicate #216564


docs: update README.md

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Regenerator of regenerators

A lot of fixes have been going into the job regenerators recently and I keep having to update them one by one which gets a little time consuming and annoying after a while (there's not a way I know of to "import" configs from other jobs). Similarly to the build-pipeline-generator and pipeline_jobs_generator_jdkxx jobs, it would be nice to have a job in utils/ that will refresh these jobs on a commit push to master.

Let's be mindful of making sure this doesn't get too complicated and impacts the ability for others to get involved in the project.


Fix libc mess

Unfortunately things are still inconsistency :unamused:
I found this interesting article that may help (Enthough goes in the direction as defaults).

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


Add tracking stats to witnesses

Depends on https://github.com/akitasoftware/akita-ir/pull/8.

Closing. The IR size increase turned out to be too much, and is not currently relevant.


Loading Pretrained Models

Hi, I'm interested in helping implement the loading of the pretrained models.
I want to know if you can point in the right direction of what you think needs to be and I can take a look.
I see that openai has code at https://github.com/openai/image-gpt that isn't being maintained and is written in TF.
What do you think. Should we try and take those models and convert them to onnx and go from there?

Hi, any update? @JohnnyC08


feat/grafana-risingwave-dashboard

What's changed and what's your intention?
Building out k8-focused Grafana Dashboard
In relation to #163

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

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

@Larrystamford seems some of the commits are signed with a non-recognized GitHub account 😃 would u mind rewriting them?

Gonna close this in favor of #179


Bug: prometheus does not display 'real' values

I see on EKG:
real:complex.message.Error.timed.mean | 3.5568424622399645e15
but nowhere in Prometheus output.

In example-complex.

Reals are stored as Labels in EKG as it cannot store real numbers and ekg-prometheus-adapter ignores any Label inside ekg store.

I can see 2 possible solutions:

We can change the function from ekg-prometheus-adapter
We can create an independent prometheus store and forward the items that arrive in EKG to prometheus.

I think it only needs some proper conversion. I see in prometheus:
ns:complex_message_Debug_timed_max  1.561453432464649e18

which looks like a real value.
so any value starting with "real:" can be tried to be converted to a Double and then output to Prometheus. (and, "ns:", others ?)

I think it only needs some proper conversion. I see in prometheus:
ns:complex_message_Debug_timed_max  1.561453432464649e18

which looks like a real value.
so any value starting with "real:" can be tried to be converted to a Double and then output to Prometheus. (and, "ns:", others ?)

This is Nanoseconds which is translated for ekg in Gauge (integer-valued gauges) and then all the Gauges from ekg are translated to prometheus' Gauge which is a double-valued gauge.
Labels of ekg are ignored by the ekg-prometheus-adapter.
https://github.com/adinapoli/ekg-prometheus-adapter/blob/bb482c9918cde40a5ac475fef4c67c8b5436ac09/src/System/Remote/Monitoring/Prometheus.hs#L88