cli: support visualizing any group

Allows to create any ERD based on the Compas spec without enabling generated queries for these types

Probably not going to support this for a bit, need to leak to much internal code-gen checks to the cli to consistently generate this.
The sql checks always operate on query enabled objects only, so to add this we loose a lot of assumptions or need to restructure quite a bit
A work around would be:
import { uuid, spawn } from "@compas/stdlib";

const app = new App();

app.add(...);

const tmpDirectory = `/tmp/${uuid()}`
app.generate({
  dumpStructure: true,
  enabledGroups: ["group"],
  enabledGenerators: ["type"],
  outputDirectory: tempDirectory
});

const { exitCode } = await spawn("yarn", [
  "compas",
  "visualise",
  "sql",
  `${tempDirectory}/common/structure.js`,
  "--format",
  "png",
  "--output",
  "./docs/group-erd.png",
]);

/cc @tjonger


Redesign notification settings

Problem Description
Similar to the settings screen the notification screen is quite unstructured and cluttered.
Changes
This PR introduces sections for preference entries in the form of cards and replaces checkboxes with switches to stay consistent with the design of the settings.
This PR closes #183.
Screenshots

I just noticed that it is currently possible to go to the Notification settings screen when the user is logged out, I assume this is not intended. Would you mind fixing this as part of this PR? @julian-wls
I think it should be as easy as moving the NotificationSection into the accountData?.let statement in SettingsScreen :D


[BUG] Field exists query broken for GeoShape fields after upgrade (from 2.8.0 to 2.11.1)

Describe the bug
"Field exists" query does not work properly on fields GeoShape for existing indexes after the upgrade from 2.8.0 version to 2.11.1
I suspect it is related to #10958 somehow
Related component
Search:Query Capabilities
To Reproduce

Start an OpenSearch server in version 2.8.0
Create an index with a geo_shape field

PUT old_index
{
    "mappings": {
        "properties": {
            "name": { "type": "text" },
            "my_geometry": { "type": "geo_shape" }
        }
    }
}

Add some documents to it

POST old_index/_doc/1
{
  "name" : "Without geometry"
}

POST old_index/_doc/2
{
  "name" : "With geometry",
  "my_geometry":  {
    "type": "Point",
    "coordinates": [1,1]
  }
}

Check that the "Field exists" filter works on this version

GET old_index/_search
{
  "query": {
      "bool": { "must_not": { "exists": { "field": "my_geometry" }}}
  }
}

Upgrade the OpenSearch server to version 2.11.1

Do the same search as before

GET old_index/_search
{
  "query": {
      "bool": { "must_not": { "exists": { "field": "my_geometry" }}}
  }
}

Expected behavior
The current result is the following failure :
FieldExistsQuery requires that the field indexes doc values, norms or vectors, but field 'my_geometry' exists and indexes neither of these data structures

The expected result is that the filter works properly and only returns the following document :
{
  "name" : "Without geometry"
}

If we re-create a fresh new index on this 2.11.1 version following the same steps as before, then the filter works fine.
Additional Details
Host/Environment :
Initially had the issue with :

Index initially created on version 1.3.5
OpenSearch version before upgrade 2.8.0
OpenSearch version after upgrade 2.11.1
=> result: I did not have any error message with this setup, but the responses were wrong, and the filter was not applying (ignored?)

Reproduced locally (dockerized) with :

Index Initially created on version 2.8.0
OpenSearch version before upgrade 2.8.0
OpenSearch version after upgrade 2.11.1
=> result: a 500 error, with the message above

If you have time, try to turn this into a (failing) YAML test?


Service Unavailable | unable to connect to https://quay.io/v2/ inside private network

I'm inside my company network which I go through a proxy to access external sites.
When building my container inside y spring boot application, I'm receiving a Caused by: com.github.dockerjava.api.exception.InternalServerErrorException: {"message":"Get https://quay.io/v2/: Service Unavailable"}
When I access the link, I'm able to connect via chrome
I have tried using a docker compose file (which i am able to run with no issues using docker-compose up) and my container starts up with no issues.
I tried two different methods: one starting up using the docker image name and another with the docker compose file passed in, both fail.
@Testcontainers
public class ElasticSearchServiceTest {

  @Container
  public static DockerComposeContainer compose =
      new DockerComposeContainer(
          new File("src/test/resources/docker-compose.yml"))
          .withExposedService("elasticsearch", 9200);

I also tried creating it with the docker image name:
@Testcontainers
public class ElasticSearchServiceTest {

  @Container
  public static ElasticsearchContainer compose =
      new ElasticsearchContainer(
          "hub.docker.prod.<company_name>.com/library/elasticsearch:7.0.0")
          .withExposedPorts(8080);

since i am able to hit the the site with no issues via chrome and I am able to start the container via docker-compose up I am not sure what the issue may be.
I get the exact same error for both.
The dependencies i'm using are:
  <dependency>
      <groupId>org.testcontainers</groupId>
      <artifactId>junit-jupiter</artifactId>
      <version>1.12.2</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.testcontainers</groupId>
      <artifactId>elasticsearch</artifactId>
      <version>1.12.2</version>
      <scope>test</scope>
    </dependency>

What can i do to work around it? Can someone provide examples?

We have the same problem in our company network.


v0.10.0 causes runtime error when building with Create React App

I'm using websocket-as-promised in an ejected version of "create-react-app". When testing using the dev server, everything works fine. But when I build the project and then run it, I get an error "Uncaught TypeError: Super expression must either be null or a function, not undefined" and the websocket code fails to run.
Downgrading to version 0.9.0 fixes the problem.
I have not had a chance to try much debugging. I tried to change the Terser minification plugin option in my app to keep_fnames: true, going on advice from various Stack Overflow posts. This did not resolve the issue. I also tried disabled the Terser plugin in my app, and that resolved the issue.

hi @pangolingo !
Could you show a stack trace to localize the problem?

Unfortunately the stack trace is almost useless because I didn't have time to fight with Webpack to include the package sourcemaps. The root error comes from line 1065 in dist/index.js:  if ("function" != typeof t && null !== t) throw new TypeError("Super expression must either be null or a
(anonymous) (index.js:1065)
function");
(anonymous) (index.js:1064)
(anonymous) (index.js:1058)
(anonymous) (index.js:711)
n (index.js:15)
(anonymous) (index.js:454)
n (index.js:15)
(anonymous) (index.js:51)
226 (index.js:5)
f (index.html:1)
486 (index.jsx:15)
f (index.html:1)
229 (index.js:1924)
f (index.html:1)
t (index.html:1)
r (index.html:1)
(anonymous) (index.chunk.js:1)

The error happens when I instantiate the library:
import WebSocketAsPromised from 'websocket-as-promised';

const client = new WebSocketAsPromised(`ws://localhost:${port}`, {
      packMessage: (data: any) => JSON.stringify(data),
      unpackMessage: (data: any) => data,
      // add a unique ID to the request so we know when we receive a response
      attachRequestId: (data: any, requestId: string | number): void => {
        console.log('attaching id', requestId, 'to', data);
        if (
          typeof data === 'object' &&
          'rc' in data &&
          typeof data.rc === 'object'
        ) {
          const newData = { ...data };
          newData.rc.id = requestId;
          console.log('attached', newData);
          return newData;
        }
        console.log('could not attach');
        return data;
      },
      extractRequestId: (data: any) => {
        if (
          typeof data === 'object' &&
          'rc' in data &&
          typeof data.rc === 'object'
        ) {
          return data.rc.id;
        }
        return null;
      }
    });

I just confirmed this failure occurs with a fresh create-react-app installation using CRA v3.0.1.
Steps to reproduce:
> create-react-app
> cd websocket-as-promised-error-poc

Add the following to the top of App.js:
import WebSocketAsPromised from 'websocket-as-promised';
new WebSocketAsPromised('ws://localhost:8080');

Build and run the app (I'm using http-server to run it.)
> yarn build
> http-server ./build

Thanks for details!
I've disabled own minification and released 0.10.1.
In my tests with CRA it now works.
Could you please reinstall fresh websocket-as-promised and re-check?

@vitalets I've confirmed that the bug is fixed in 0.10.1. Thank you! 🙇♂

You are welcome! )


Fix case where decision task is followed by a terminate task

The execution of the TERMINATE task deviated from that of other tasks such that -

The task execution would modify the enclosing workflow but expect the orchestrator/state machine to persist the workflow changes
In order to accomodate this behavior, the state machine evaluation had to be hacked for detection and early termination of the workflow, leading to incomplete workflow evalutions. (The most obvious side-effect of this being the TERMINATE task would be added to the workflow with a seq of 0).
The incomplete state evaluation further led to the corner case such that when a DECISION task is followed by a TERMINATE task in one of its branches, the DECISION task would not be persisted by the state machine as part of the workflow data.

This PR aims to resolve the above discrepancies by

Making the TERMINATE task execution consistent with that of other tasks and relying on state machine to modify and update any workflow level changes.
Fixing the DAG evaluation in the state machine such that it exits early when a TERMINATE task node is met in the graph.
Removing the hacks during task execution and replacing it with DAG evaluation combined with workflow evaluation for early termination of workflows using the TERMINATE task.

A behavior change for the TERMINATE task that has been introduced in this PR is that other non-terminal tasks will be marked as CANCELED keeping it consistent to the behavior if the workflow were to be TERMINATED manually (or using the API). The old behavior here was to mark such tasks as SKIPPED.

@rickfish This might be of interest to you as well based on #1773 . I am currently making this change in 3.0 branch but once approved, will back-port this to 2.x as well. Please review and provide thoughts.

@rickfish This might be of interest to you as well based on #1773 . I am currently making this change in 3.0 branch but once approved, will back-port this to 2.x as well. Please review and provide thoughts.

@apanicker-nflx Thanks for letting me know. There are so many scenarios...I will have to run my test case once the changes are in the 2.x release to see if it does indeed cancel all the tasks in all of the subworkflows and the subworkflows themselves. I am assuming that you already tested that and feel confident that the changes you made maintain the fix and also fixes other side effects.

@apanicker-nflx Thanks for letting me know. There are so many scenarios...I will have to run my test case once the changes are in the 2.x release to see if it does indeed cancel all the tasks in all of the subworkflows and the subworkflows themselves. I am assuming that you already tested that and feel confident that the changes you made maintain the fix and also fixes other side effects.


Mix project variant?

Currently, the template is supporting the Phoenix project (API and web variants), how about supporting the Mix project (for creating another Elixir lib) 🤔
mix nimble.phx.gen.template --mix

We could consider changing the task name to nimble.gen.template so that doesn't contain the phx to make it clear
mix nimble.gen.template --mix

That would be a great addition as even for umbrella apps, we might not always need a Phoenix application. So I am in favour or renaming the task name to mix nimble.gen.template.

That would be a great addition as even for umbrella apps, we might not always need a Phoenix application. So I am in favour or renaming the task name to mix nimble.gen.template.


iOS image overlay does not work

Hi all
Currently, working on app that use tapioca for video overlay creation, on android everything works like a charm, but on ios image overlays are not working. Even when i build an example with pink color overlay, text and image, - first two TapioaBalls works, but no image on result video.
I am ready to be a contributor, cause i need this functionality asap. Can you send me a tutorial how to build ?
iOS 15.3 (Iphone 11)
P.S. Same result for iOS emulator, no image overlay
Thank you!

All right.
First , clone the repository.
git clone https://github.com/anharu2394/tapioca

Second, open an iOS emulator.
Third, using Android Studio, press a run button. Then, it will build the app and run it. So, you can debug it.
iOS original source code:
https://github.com/anharu2394/tapioca/tree/master/ios%2FClasses
Flutter source code:
https://github.com/anharu2394/tapioca/tree/master/lib
If you edit iOS original source, iOS behavior of Tapioca will be improved!!

Same issue.. Image overlay not working on iOS real device.
Any solution to that issue???

@hbrhbr
The solution for ios - to switch x and y coordinates, becaue on ios the coordinate grid is different
so yo need something like this
if (ios){
show(y, x)
else  {
show(x, y)
}

@dmayboroda I am having trouble with this also. I can see the overlay when generated from Android, but not iOS. What coordinates do you need to put in for iOS? I don't really care where the image goes yet, I just want to see if on the video.

Do we have any solution for this?

same problem here. cannot see any image even with many different coordinates


Small typo in docs

The best partition is calculated twice.

See only now that it is a duplicate of issue #79


Improve method delegation support

Remove hard-coded method delegation using inheritance and the Forwardable module.

Thanks for the contribution!


Fix k8s secret resolution logic

Apparently there's an issue with the current code. If concourse only has access to "$SECRET" secret and not "$PIPELINE.$SECRET", then apiserver will return a 403 which fails fast, not allowing concourse to try the second option.
This PR makes sure that concourse will try both options before failing, also improves logging.

@farcaller How do you set up rbac so that the client only has access to one secret in the namespace and not the other?

@william-tran
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: Role
metadata:
  name: concourse
rules:
  - apiGroups: ['']
    resourceNames:
      - containers.mysecret # only needed as a workaround for this bug
      - mysecret # actual secret
    resources: [secrets]
    verbs: [get]

@farcaller I assumed the typical use case would be a ClusterRoleBinding that allows all secrets in the team specific namespace to be read by concourse, where the namespace is set up for the sole purpose of providing secret values to all pipelines in a particular team. See my comment here: https://github.com/concourse/atc/pull/189#issuecomment-341502356. You can control what secrets concourse has access to by just adding and removing secrets in that namespace. One downside to this approach is either the duplication of secret values used outside concourse, or needing to provide specific bindings to each non-concourse secret usage.
I think the situation you're solving for is one where:

You have an existing namespace that contains secrets
Your team name and namespace prefix are set up to map to this namespace
Not all secrets in this namespace should be made available to concourse.

Are we on the same page here?

This feels related to https://github.com/concourse/atc/pull/254?

Sorry but I'm gonna close this for now since I'm not sure it's going anywhere. There are other PRs open related to k8s secrets and I'd like to minimize the mental gymnastics of correlating them.
Thanks for kicking this off though!


IRP unload

is it possible add a IRP unload for drivers ?
To unload an IRP, the driver typically needs to complete the processing of the IRP and release any resources that were allocated for it. This is typically done by calling the IoCompleteRequest function, which signals the operating system that the IRP has been completed and can be freed.

Oh Y can  use Unload Driver Function ----It will call the Target Driver unload function( == Send UNLOAD IRP)

thank you im talking about this one

OK I get it, The next version  will show IRP unload  address.   Before 5.5

hey there still no unload IRP in new version

yes but i was wondering if its possible to  add unload routine in refresh view all only show danger properties find target in explroer export to to text

#12


[FEATURE] Introduce the general remote fs access layer

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the feature
Currently, we use the Hadoop filesystem interface to be interactive with S3/OBS/HDFS/COS, maybe this will make uniffle
bound to Hadoop ecosystem.
In my opinion, when deploying uniffle into the K8s and directly use the s3 as the backend storage, there is not necessary to use the Hadoop api to visit S3.
So we should introduce the general fs access layer to unify all fs visit, including HDFS/S3, like flink does.
Motivation
No response
Describe the solution
No response
Additional context
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

I have some concern about some low performance operations about object storage such as Append operation and List operation. Maybe we need extra optimization.

This issue may be related with the support of object store. Let's track this in https://github.com/apache/incubator-uniffle/issues/391


clock module error "Timezone database not found at"...

[2020-01-28 16:51:44.183] [warning] module clock: Disabling module "clock", Timezone database not found at "/home/lann/Downloads/tzdata"

I get the same issue. Workaround works!

@mjec Any idea why this happens ?

It looks like this only happens if the date library is configured not to use system tzdb; see https://github.com/HowardHinnant/date/blob/master/src/tz.cpp#L3387-L3497.
By default Waybar should be using the system tzdb: https://github.com/Alexays/Waybar/blob/master/meson.build#L85.
@varac / @lann, what distribution are you running, and what steps did you take to compile or install Waybar?

Looks like that option was set to false in my checkout for some reason (based on strings in the libtz object file). Deleting build and re-running meson fixed it.

@varac / @lann, what distribution are you running, and what steps did you take to compile or install Waybar?

I'm using ubuntu 19.10, sway version 1.4-f681d529 (Jan 22 2020, branch 'heads/1.4'), and compile waybar with
 meson --reconfigure build && ninja -C build && sudo ninja -C build install

@varac I'm on 19.10 too. I suspect the issue is caused by some bit of build state that might not get reset by --reconfigure. I fixed it with the nuclear option (deleting build/).

@varac I'm on 19.10 too. I suspect the issue is caused by some bit of build state that might not get reset by --reconfigure. I fixed it with the nuclear option (deleting build/).

Thx @ianhattendorf I removed the build folder for now, will report back once I hit this again.


Subnets

HI,
I am pretty new to this. I am using your module but it seems each time I run terraform the IP changes forcing VPC to rebuild because subnets changes and then forces EKS to rebuild is there a way to stop the IP changing in the subnets ?
Sorry if am asking a very obvious question. I am just pretty new to this.
Thanks

https://github.com/terraform-aws-modules/terraform-aws-vpc/issues/114 . same issue but am using /24
name = "puppy-vpc"
cidr = "<IP_ADDRESS>/16"
azs             = ["eu-west-2a", "eu-west-2b", "eu-west-2c"]
public_subnets  = ["<IP_ADDRESS>/24", "<IP_ADDRESS>/24", "<IP_ADDRESS>/24"]
private_subnets = ["<IP_ADDRESS>/19", "<IP_ADDRESS>/19", "<IP_ADDRESS>/19"]

Hi,
The problem is not the /24 public subnets but your /19 private subnets.
AWS calculates the "correct" network address based on the input CIDR values, which may differ from the values set in Terraform. You need to update your private_subnets to also use these correct values: "<IP_ADDRESS>/19", "<IP_ADDRESS>/19", "<IP_ADDRESS>/19"
Maybe file a bug against the AWS provider so that the vpc and subnet resources also do this translation.

Hey
I have spent 2 days trying to resolve this problem. Thanks so much you have made my day :)  Just 1 quick question. How do you know what subnet ranges I can use ? I have 2 more environments with same problem.

Easiest way is to use an ip calculator. There are plenty of options out there. An example is http://jodies.de/ipcalc . Put in an address in your range and the CIDR value, hit calculate and take the Network result.

Thanks for your help on that. Really helpful.
I have another question. I am not able to connect to the Nodes. I am guessing its the VPC ACL that isn't letting connection to the nodes. What would be the best way to allow access to the nodes

You mentioned EKS so I guess you're talking about kubernetes nodes?
Depends on how you want to access nodes. Do you mean command line access?
If you want to use SSH then you will have to create a key pair resource and pass it to the node launch template/configuration.
Remember that by default AWS security groups do not allow ingress from anywhere.
Do the nodes have public IPs? If so, you need to edit the security group and allow access from your IP.
If not, you need to create a bastion server in the public subnet, allow SSH access from your IP and grant it SSH access to the nodes.
Alternatively, you can use AWS Systems Manager Session Manager to gain access without SSH or ingress security rules. You will need to install an agent in the nodes (e.g. via user data or creating an AMI), add the necessary IAM permissions and then use the AWS console.
https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html

HI
I have managed to get ssh key working, I have also opened the port 22, I also enabled Public IP and public DNS for nodes. I am still not able to connect to the nodes. I am not sure if there is something in the VPC blocking me from connecting to the nodes directly.

Closing this issue, as it is not related to the module.


fix: update to eye v3.4.5

fix: update to eye v3.4.5

:tada: This PR is included in version 4.4.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v4.4.2

Your semantic-release bot :package::rocket:


Prefers empty array to undefined in UI span conversion; backfills ipv6

When writing json to the wire, we guard on creating empty arrays for
annotations and binaryAnnotations. However, in process, this just makes
life more difficult ex (annotations || []).map... This simplifies
things, cleaning up some code. It also backfills the missing ipv6.

cc @Logic-32 @zeagord


[BUG] type-safe-api.parse-openapi-spec command not found

Describe the bug
During the build of a typesafe api project when running the following command:
npx --yes -p @aws/pdk@$AWS_PDK_VERSION type-safe-api.parse-openapi-spec
The following error is output:
sh: type-safe-api.parse-openapi-spec: command not found
Expected Behavior
It was expected that the spec is read
Current Behavior
sh: type-safe-api.parse-openapi-spec: command not found
Task "build » compile » generate" failed when executing "npx --yes -p @aws/pdk@$AWS_PDK_VERSION type-safe-api.parse-openapi-spec
Reproduction Steps
Running the build with typesafeapi using pdk version 0.23.55
Possible Solution
No response
Additional Information/Context
No response
PDK version used
0.23.55
What languages are you seeing this issue on?
Typescript
Environment details (OS name and version, etc.)
macOSX Ventura 13.6.9 npm 9.8.1 node 18.18.2

Hi! That script has now been moved to a subcommand of the type-safe-api command (see here). Please can you try re-synthesising your project files (eg npx projen)? That should update your projects to point to the new script.

Closing this as re-synthesizing will adjust the command that's run from type-safe-api.parse-openapi-spec to type-safe-api parse-openapi-spec. Feel free to comment and reopen if you're still having issues! :)


Help

lib Update Request

Configuration Check

My compilation target is ES2015 and my lib is the default.
Missing / Incorrect Definition

Sample Code

Documentation Link

Hi @jamesbanged! If you need help with something, check out the TS discord. If you're trying to file an issue with TS itself, you'll need to fill out the issue templates.


x-pack branch - password changes

docker-compose.yml
version: '2'

services:
  elasticsearch:
    build:
      context: elasticsearch/
    volumes:
      - ./elasticsearch/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml
      - ./elasticsearch/data/:/usr/share/elasticsearch/data
    ports:
      - "9200:9200"
      - "9300:9300"
    environment:
      ES_JAVA_OPTS: "-Xmx256m -Xms256m"
      ELASTIC_PASSWORD: "NewPassword"
    networks:
      - elk

  logstash:
    build:
      context: logstash/
    volumes:
      - ./logstash/pipeline:/usr/share/logstash/pipeline
      - ./logstash/config/logstash.yml:/usr/share/logstash/config/logstash.yml
    ports:
      - "5000:5000"
      - "5044:5044"
    environment:
      LS_JAVA_OPTS: "-Xmx256m -Xms256m"
      xpack.monitoring.elasticsearch.password: "NewPassword"
    networks:
      - elk
    depends_on:
      - elasticsearch

  kibana:
    build:
      context: kibana/
    ports:
      - "5601:5601"
    networks:
      - elk
    depends_on:
      - elasticsearch
    volumes:
      - ./kibana/config/kibana.yml:/usr/share/kibana/config/kibana.yml

networks:
  elk:
    driver: bridge

Kibana.yml
server.name: kibana
server.host: "0"
elasticsearch.url: http://elasticsearch:9200
elasticsearch.password: NewPassword

Logstash.yml
http.host: <IP_ADDRESS>
path.config: /usr/share/logstash/pipeline
xpack.monitoring.elasticsearch.password: NewPassword

I've tried an assortment of different things to get this working. One approach that had the setup working was to change the elasticsearch.username in the Logstash.yml file to 'elastic' which overides the 'logstash_system' user. The problem with this was when a password is entered incorrectly the whole system locks out.
I've tried using the bin/x-pack/setup-passwords interactive command and configuring the passwords this way too, this also failed.
The branch is also missing default logstash / kibana yaml files, is this standard? I copied the default layouts from the Master branch.
Error
logstash_1       | [2017-12-12T16:50:00,769][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://logstash_system:xxxxxx@localhost:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://logstash_system:xxxxxx@localhost:9200/][Manticore::SocketException] Connection refused (Connection refused)"}

Adding the links I referenced in another issue for reference:
X-Pack for the Elastic Stack [6.0] » Securing Elasticsearch and Kibana »

Getting Started with Security
Setting Up User Authentication

@antoineco
I've been through that approach and configured the passwords with x-pack along with updating the passwords in the yaml files (see above). Still no joy.

Here's what I did:

Generate new passwords for built-in users

# docker-compose exec elasticsearch bin/x-pack/setup-passwords auto

Initiating the setup of reserved user elastic,kibana,logstash_system passwords.
The passwords will be randomly generated and printed to the console.
Please confirm that you would like to continue [y/N]y

Changed password for user kibana
PASSWORD kibana = $fREKVMGQyG19oX%~fs@

Changed password for user logstash_system
PASSWORD logstash_system = rjUK$+&kEC?#0L8mY%np

Changed password for user elastic
PASSWORD elastic = mc~?DPIUhj-!kUMr+~dd

Create/Update configs (see README)

logstash.yml / kibana.yml
eg.
# config/logstash.yml
xpack.monitoring.elasticsearch.username: logstash_system
xpack.monitoring.elasticsearch.password: 'rjUK$+&kEC?#0L8mY%np'

# config/kibana.yml
elasticsearch.username: kibana
elasticsearch.password: '$fREKVMGQyG19oX%~fs@'

# pipeline/logstash.conf
...
		user => elastic
		password => 'mc~?DPIUhj-!kUMr+~dd'

Restart the stack

# docker-compose restart

So far so good, I can login to Kibana and ship logs via Logstash.
Can you try on your side?

Following your instructions exactly this is the error I'm receiving...
[2017-12-12T18:33:03,302][ERROR][logstash.agent           ] Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"LogStash::ConfigurationError", :message=>"Expected one of #, {, } at line 13, column 31 (byte 202) after output {\n\telasticsearch {\n\t\thosts => \"elasticsearch:9200\"\n\t\tuser => elastic\n\t\tpassword => Q9S6XJ2sDWikZatw", :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:42:in `compile_ast'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:50:in `compile_imperative'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:54:in `compile_graph'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:12:in `block in compile_sources'", "org/jruby/RubyArray.java:2486:in `map'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:11:in `compile_sources'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:107:in `compile_lir'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:49:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:215:in `initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:35:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:335:in `block in converge_state'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:141:in `with_pipelines'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:332:in `block in converge_state'", "org/jruby/RubyArray.java:1734:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:319:in `converge_state'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:166:in `block in converge_state_and_update'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:141:in `with_pipelines'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:164:in `converge_state_and_update'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:90:in `execute'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:362:in `block in execute'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/stud-0.0.23/lib/stud/task.rb:24:in `block in initialize'"]}
[2017-12-12T18:33:03,371][INFO ][logstash.inputs.metrics  ] Monitoring License OK
[2017-12-12T18:33:04,230][INFO ][logstash.pipeline        ] Pipeline terminated {"pipeline.id"=>".monitoring-logstash"}

You have a typo in your Logstash pipeline config, make sure you use single quotes around passwords.
I also committed default config files to the x-pack branch so you don't have to pull them yourself.

Correct, double quotes seemed to be causing the issue. Sorry, the error message is actually quite clear now that I'm looking at it with fresh eyes. Thanks for your input, seems to be working fine. I'll continue testing.

Awesome, feel free to comment back or close the issue then :)

Ok sweet, I've got it running with a configuration suited to our needs. Issues closed.


Update to latest pulumi-service

Add initial support for the deploy-target option.

@seanyeh This is ready for review now.


feat!: initial generation of client library

initial generation of library.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@182128b). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   98.87%
=========================================
  Files             ?       11
  Lines             ?    18114
  Branches          ?      525
=========================================
  Hits              ?    17910
  Misses            ?      197
  Partials          ?        7

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 182128b...83a1edb. Read the comment docs.


message hub shows offline - but it is online

There is a problem with this part of the message hub page:
https://www.evernote.com/l/AICZcYK5rbJKtJkPrB7IHxZ1Dv41KZo3ZS8
The problem is that this message hub is ONLINE. If you refresh the page, you can see it changes quickly from ONLINE to OFFLINE.
The reason for this is because some of the message hubs are offline. You can see this here:
https://www.evernote.com/l/AIBJRMjN7fRGS5UV_EKQzmUdGAOT_AswC8U
But since my main message hub is zoe.koto.at, it should show ONLINE. not OFFLINE.
So only check MY message hub, and report status of THAT one only.

@dimakrsna we are going to let @Cardoso-topdev try and solve this problem. Good luck @Cardoso-topdev .


No popup

Tried disabling all plugings except TS and nabla.
I've tried multiple maps, aswel as just writing ":lua require("nabla").popup()" in command mode.
Latex parser is installed.
Canot get any feedback at all.
NVIM 0.7.2

😅 thanks, guess it was obvious

Well, not really. Previously, it had a warning message, but we forgot to put it again with the new treesitter implementation. So thanks for pointing this out! It will probably save a few people's time.

Any way to copy the content to the clipboard without using the mouse?

Currently no. Why would you need this?
It's always possible to use the underlying lua API to extract the ASCII content from a Latex formula.

Well, I was checking the plugin to have plaintext shareable equations. So, most of the time I open the popup is to paste it into the file.

You could try with :lua require"nabla".popup({focusable=true}) then use some command to jump into the window (I don't remenber currently). I personally always use the mouse (:set mouse=a) and click into the floating window to focus it. That's the best solution I came up with now.

@jbyuki I wouldn't add a warning
imo it's obvious already
perhaps add a notice to the readme if you think it isn't
but this could be annoying if e.g. someone just uses a CursorHold autocommand

Fair point, I'll add this into the README instead. Thanks @max397574 .


Remove service worker from app and add disable caching

What is the context of this PR?
This PR removes the service worker from the application.
The service worker allows progressive web applications to provide a better experience when working offline.
You can learn more about service workers here.
We are not currently using the service worker to it's full potential and it is causing old versions of the application to be displayed when deployed in our CloudFoundry and ECS environments.
For now, the team has decided that the best thing to do would be to remove the service worker and thus prevent it from being registered in the browser.
I have also added some caching configuration to the index.html page as instructed here.
How to review
All tests and checks should pass.
Delete the service worker and start using the application. A new service worker should not be registered.

 Remove Service Worker


#870: ensureIndexes() throws unhandleable "Index with name: xyz_1" already exists

added a new parameter to IndexOptions for controlling the recreation of the outdated index

No chance... the gradle output doesn't show the failing tests in the log from Travis build...

I ran the Gradle build locally and I found the following tests failing:
org.mongodb.morphia.aggregation.AggregationTest > testDateToString FAILED
org.junit.ComparisonFailure at AggregationTest.java:86

org.mongodb.morphia.indexes.TestIndexOptionAsDropOutdated > testDropOutdatedIndexWhenOptionsHaveChangedWithClassIndex FAILED
java.lang.AssertionError at TestIndexOptionAsDropOutdated.java:53

org.mongodb.morphia.indexes.TestIndexOptionAsDropOutdated > testDropOutdatedIndexWhenOptionsHaveChangedWithUnnamedIndex FAILED
java.lang.AssertionError at TestIndexOptionAsDropOutdated.java:53

@trishagee Thank you very much. Can you tell me, which version of MongoDB you are using? I use 3.2.6, but I think, that there is a change in the error message, which I parse in order to get the 'failing' index-name, which must be dropped. In these two testcases, the index is not named via annotation.
If I know the MongoDB version, I try to setup another server with exactly this version in order to reproduce the problem...
The test with "testDateToString" has something to do, at what time you start the test (I ran into failing sometimes, but if I start it later than 2 am in the morning, then it worked)... nevertheless, this is not connected with the PR, because my changes does not touch the Aggregation.

Ok, found out, that before MongoDB 2.6, the an index, which exists but with different options was not created, but there was no error. Since 2.6, there is an error.

The amount of work you've put into this pull request is clear - you have test coverage, have followed the conventions and worked hard to get the build passing.
However, in MongoDB libraries like Morphia we have generally tried to avoid implementing strategies for automatically dealing with failure (retries on error, for example) because of the added performance cost that is not always visible to those using the library.  It's generally better practice to highlight the failure to the application using the library (e.g. through specific Exceptions) so developers can deal with the problem in a way that is appropriate for their case.
Ultimately the decision to merge pull requests is @evanchooly's, but I wanted to take the time to explain why code that you've clearly spent time and effort on may not be merged immediately and requires careful consideration from the maintainers.

Hi Trisha,
thanks for your explanation.
The problem here is, that if we did not provide such "option" to automatically delete and re-create the index when there is an index with that name but with other options, the user has no real option to deal with this situation correctly. The only information the user has at the moment is a simple text-message, where an index-name is provides. But the user does not know, on which collection this index is, because this information is not given. So the only way to handle this is to iterate over all collections, get the index names and throw away this index, which can result in a much unneccessary dropped indexes. And this is not really possible in production systems, where there are huge collections, which need time to recreate.
I think, to have this "dropOutdated"-option is not other then the "dropDubs"-option. And the "automatic failure-code" only come into play, when there is an error situation, so there is no real performance hit.
Nevertheless, relying on messages or something is always not ideal. Better would be, when Mongo-Java-Driver throws some "IndexAlreadyExistsWithOtherOption"-exception and provide a reliable data structure with index-name and collection-name, so Morphia or the user have exact informations to deal with.

In point of fact, dropDups is a server-side option that's been removed for many of the same reasons this option makes me terribly nervous.  Trisha has it right that correctly identifying this case is tricky.  If the problem is that the message doesn't contain the collection, that can be easily fixed.  I'm still unsure about this PR.  It needs a bit of discussion still, I think.

@evanchooly
< If the problem is that the message doesn't contain the collection>
Ok, but if I get it right, we need to update MongoServer, because the error message is generated by Mongo directly.
But then, it would be better, if the response contains a dedicated error structure, otherwise the user has to deal with string-parsing to identify collection- and index-name.

Indexing has been significantly refactored so this PR can not be merged as is.  In addition, consensus among the team is that is isn't something that should be in Morphia itself.  As such, I'm going to close out this PR.  Issue #1036 would be an interesting one to tackle if you're looking to contribute.  It'd be very similar to the document validation work.

Does the MongoDB-Java-Driver now provides the collection name in addition to the index name in the exception? Then I would make the "workaround" in the business-application.


IncrementCount -> IncrementAmount inside onclick

In the example where Pages/Counter.razor is modified to have IncrementCount parameter, onclick still calls IncrementCount. This gives build error, as it should be replaced with IncrementAmount.

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

ID: c07e57dc-526f-9479-4695-de7d8f06eb9a
Version Independent ID: 8226ed72-69b2-3c93-a931-218bd11cf9c8
Content: Get started with ASP.NET Core Blazor
Content Source: aspnetcore/blazor/get-started.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Thanks @smilyte ... I'll get that patched up.

No, @smilyte ... actually, that's correct. The method is IncrementCount there.

Check your spellings in your code. I've seen a spelling mistake cause that sort of error.

Wow, it's been a long day for me. I managed to copy-type this incorrectly :D Sorry, and thanks for quick look!


Refresh post

Congratulation for this amazing project !!
I have a cache problem I think because my posts don't update on my site as soon as I post one except when I force dynamic reloading...

@axelverglas I've adjusted the revalidate route to bust all cache in this commit https://github.com/gregrickaby/nextjs-wordpress/commit/bddd6bbefa555c9401ab0967c14162ad03519b88
On other projects I run, I've found the best way to revalidate is to revalidate all paths.


docs: reference formula assertions for tests

[x] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

This might make people more likely to use pipe_output

Looks good, thanks again @SMillerDev! Merge conflict that needs addressed unfortunately (probably my bad, sorry).

Thanks @SMillerDev!


java.lang.ClassNotFoundException  androidx.activity.OnBackPressedDispatcherOwner at io.flutter.plugin.platform.PlatformPlugin.popSystemNavigator(Unknown Source:13)

Root cause:
[+5050 ms] E/AndroidRuntime( 3772): FATAL EXCEPTION: main
[   +2 ms] E/AndroidRuntime( 3772): Process: com.jelly.medianoter, PID: 3772
[   +1 ms] E/AndroidRuntime( 3772): java.lang.NoClassDefFoundError: Failed resolution of:
Landroidx/activity/OnBackPressedDispatcherOwner;
[   +3 ms] E/AndroidRuntime( 3772):     at
io.flutter.plugin.platform.PlatformPlugin.popSystemNavigator(PlatformPlugin.java:318)
[   +1 ms] E/AndroidRuntime( 3772):     at io.flutter.plugin.platform.PlatformPlugin.access$600(PlatformPlugin.java:28)
[   +3 ms] E/AndroidRuntime( 3772):     at
io.flutter.plugin.platform.PlatformPlugin$1.popSystemNavigator(PlatformPlugin.java:101)
[   +1 ms] E/AndroidRuntime( 3772):     at
io.flutter.embedding.engine.systemchannels.PlatformChannel$1.onMethodCall(PlatformChannel.java:123)
[   +2 ms] E/AndroidRuntime( 3772):     at
io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:233)
[   +1 ms] E/AndroidRuntime( 3772):     at
io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:85)
[   +5 ms] E/AndroidRuntime( 3772):     at
io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:818)
[   +4 ms] E/AndroidRuntime( 3772):     at android.os.MessageQueue.nativePollOnce(Native Method)
[   +1 ms] E/AndroidRuntime( 3772):     at android.os.MessageQueue.next(MessageQueue.java:363)
[   +2 ms] E/AndroidRuntime( 3772):     at android.os.Looper.loop(Looper.java:176)
[   +2 ms] E/AndroidRuntime( 3772):     at android.app.ActivityThread.main(ActivityThread.java:8387)
[   +2 ms] E/AndroidRuntime( 3772):     at java.lang.reflect.Method.invoke(Native Method)
[   +1 ms] E/AndroidRuntime( 3772):     at
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:513)
[   +1 ms] E/AndroidRuntime( 3772):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1055)
[   +1 ms] E/AndroidRuntime( 3772): Caused by: java.lang.ClassNotFoundException: Didn't find class
"androidx.activity.OnBackPressedDispatcherOwner" on path: DexPathList[[zip file
"/data/app/com.jelly.medianoter-pP8csWG7GHq2NAkix0gG5g==/base.apk"],nativeLibraryDirectories=[/data/app/com.jelly.median
oter-pP8csWG7GHq2NAkix0gG5g==/lib/arm64,
/data/app/com.jelly.medianoter-pP8csWG7GHq2NAkix0gG5g==/base.apk!/lib/arm64-v8a, /system/lib64, /hw_product/lib64,
/system/product/lib64]]

I was not able to reproduce this on emulator with Android 11. @sinojelly are you able to reproduce this issue on Emulator?
It would help if you are able to provide a minimal code that reproduces this issue.
Thank you
Originally posted by @pedromassangocode in https://github.com/flutter/flutter/issues/76183#issuecomment-780580869

I also met this problem.
finally I solve this problem add implementation in build.gradle
implementation 'androidx.activity:activity:1.0.0'
but I don't know why did this problem only appear recently?

Closing as solved based on the above response, Incase you disagree feel free to write in the comments and we will reopen it.
Thank you.


[Feature Request] : Improve Homepage UI

I would like to propose an enhancement to the homepage UI to make it more modern, user-friendly, and visually appealing. This will include:

Redesigning the layout for better user navigation
Improving the colour scheme and typography for readability
Enhancing the responsiveness for a better mobile experience
Simplifying the header and footer for cleaner design
This improvement will help provide a better user experience, making the project more attractive to new users.

This improvement will help provide a better user experience, making the project more attractive to new users.
Please add the following labels to this issue:
"gssoc-ext"
"hacktoberfest-accepted"
Please assign this issue to me so I can start working on it.

i would like to work on this issue .please this to me under gssoc ext and hacktoberfest

@iarmaanx, @Sahoobarsharani, are you familiar with Figma? Could you show me your design and what it looks like after the code is executed?

If anyone is familiar with Figma and UX/UI design, please join this Figma link to create your design and collaborate with other designers.
https://www.figma.com/design/Gpp9lztaz36xu9nuGt7FBE/Frontend-Mentor?node-id=222-2&t=5ORsoPuj9AQSklia-1
For further discussion join the discord server here:
https://discord.gg/cWDQjdhd


Add a fix for the intermitten failure in the OIDCIdentityFederationTestCase.

$subject.
Related to https://github.com/wso2/product-is/issues/11018.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/499078094

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/499078094

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/499078094
Status: success

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/499078094
Status: success


Problem with installation

Just removed node-red-contrib-discord and tried downloading it and im getting this error

Sorry, I totally missed this issue. Do you still have the same error or did you fix it already?

Hello,
I stopped working on the bot for a while, I’ll check and see if it still doesn’t work.

On Oct 1, 2021, at 9:01 AM, Markoudstaal @.***> wrote:

Sorry, I totally missed this issue. Do you still have the same error or did you fix it already?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


[Snyk] Security upgrade node-sass from 6.0.1 to 7.0.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

test/fixtures/global-scss-asset-resolution/package.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

661/1000  Why? Recently disclosed, Has a fix available, CVSS 7.5
Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Herşey benim bilgim ve gönül rizak dışında gerçekleşiyor ve ben çok acı çekiyorum bu dünyadaki herşeyimi kaybettim bu gözlerime takılan lensleri benim haberim olmadan takmışlar ben bunu yıllar sonra öğrendim ve inanın çok kötü durumdayim lütfen yardım edin yıllarca bu lensler yuzunden hep hakaret gördüm takip edildim haksızlığa uğradım neler beler


Drop python 3.9 support

Following the PyAnsys Python version support policy, drop support for 3.9.
Update pre-commit hooks using pre-commit autoupdate.

Holding off on this since I want to merge and release #562 first.


Vibration won't work without 'VIBRATE' permission for Android device

Need to add below code into AndroidManifest.xml to make vibrating work.
<uses-permission android:name="android.permission.VIBRATE" />
And I think it's better to write this down in Readme file

Thank you @paulbao for your input. @Nagle's merged pull request implements your suggestion. Therfor I close this issue.

Vibration isn't working for me on iOS either, is there a permission to add there?

No, this lib only supports Android.

Oh! Thanks so much @paulbao  for your fast reply. I thougt I was posting on the official react native github. I was using this module - https://facebook.github.io/react-native/docs/vibration.html
Are you familiar with that?

Can you paste your code here to see if there's something wrong?

Thank you so much for your offer sir!!
My code is this:
import React, { Component } from 'react'
import { Vibration, View, Text, Animated } from 'react-native'

crash = () => {
const { gameover, gameover_anim } = this.state;
if (gameover) return;
this.setState(()=>({gameover:true}));
this.hole.stop();
Animated.timing(gameover_anim, { toValue:1, duration:700, useNativeDriver:true }).start();
console.log('you lose');
Vibration.vibrate();
}

The vibrate is happening on the last line. It works perfect on Android.

Maybe try to add the pattern for it like:
const pattern = [0, 1000, 2000, 3000];
Vibration.vibrate(pattern, true);

Thanks very much for that @paulbao ! I tried it but it didn't work. :( It might be a bug on their side huh?

Which RN version are you working with?

Excuse the delay please @paulbao I am using 0.44.2
Thanks again so much!

Interesting, I just did the same test and it works for me. I'm running RN 0.44.

Oh wow my sincerest thanks for putting in that much effort @paulbao -
I am on a iPad - maybe the vibrations are deactivated, I will check it out. If that is the case I am totally embarassed.

You are welcome. That must be the case...I don't think iPad supports vibration.


python3.9 CVE fixes and aim removal to pass FIPS tolerance

Description of the change

Removing the AIM component for now so FIPS tolerance works.
Moving the dnf update to the end as I noticed it missed at least one package that was later installed.
Removing the old python3.9 items (and dnf) as we're using python3.11 and the legacy python3.9 is causing CVE violations.  Attempts at upgrading python3.9 was causing many conflicts.

Related issue number
Closes issue https://github.ibm.com/ai-foundation/watson-fm-stack-tracker/issues/828

How to verify the PR
I'm testing this on my Fyre FIPS OpenShift Cluster using the steps outlined in the wiki here:
https://github.com/foundation-model-stack/fms-hf-tuning/wiki/Installing-and-Testing-OpenShift-fms‐hf‐tuning-Stack

Was the PR tested
TBD, in process now.

[ ] I have added >=1 unit test(s) for every new method I have added.
[ ] I have ensured all unit tests pass

OK - off the main branch, we have:
cve | link | hasFix | status | packageType | packageName | packageVersion | packageLicense | packageBinaryPkgs | packagePath
-- | -- | -- | -- | -- | -- | -- | -- | -- | --
CVE-2024-3651 | https://nvd.nist.gov/vuln/detail/CVE-2024-3651 | Y | fixed in 3.7 | python | idna | 2.1 | BSD-like |   | /usr/lib/python3.9/site-packages/idna-2.10-py3.9.egg-info
CVE-2023-43804 | https://nvd.nist.gov/vuln/detail/CVE-2023-43804 | Y | fixed in 2.0.6, 1.26.17 | python | urllib3 | 1.26.5 | MIT |   | /usr/lib/python3.9/site-packages/urllib3-1.26.5-py3.9.egg-info
CVE-2023-45803 | https://nvd.nist.gov/vuln/detail/CVE-2023-45803 | Y | fixed in 2.0.7, 1.26.18 | python | urllib3 | 1.26.5 | MIT |   | /usr/lib/python3.9/site-packages/urllib3-1.26.5-py3.9.egg-info
CVE-2023-32681 | https://nvd.nist.gov/vuln/detail/CVE-2023-32681 | Y | fixed in 2.31.0 | python | requests | 2.25.1 | Apache 2.0 |   | /usr/lib/python3.9/site-packages/requests-2.25.1.dist-info
CVE-2022-40897 | https://nvd.nist.gov/vuln/detail/CVE-2022-40897 | Y | fixed in 65.5.1 | python | setuptools | 53.0.0 | UNKNOWN |   | /usr/lib/python3.9/site-packages/setuptools-53.0.0.dist-info

and with this PR we result in no python3.9 CVEs:
cve | link | hasFix | status | packageType | packageName | packageVersion | packageLicense | packageBinaryPkgs | packagePath
-- | -- | -- | -- | -- | -- | -- | -- | -- | --

Geeze, what a mess...  going to close PR and re-do clean...


Introduce Distributed Queue

Introduce Distributed Queue
Lint
Update HPO
Module distribute updates

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1305
#1304  👈
#1280
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @dongreenberg and the rest of your teammates on  Graphite

Merge activity

Nov 12, 11:52 PM EST: A user started a stack merge that includes this pull request via Graphite.


update in translation

can you update your translations for Portuguese. I've added comments in english xml where translations are needed ( end of xml file ). Thank you.


Global Optimizer C++ API question, Using as an "ask and tell"

I'm a beginner to C++ so struggling a bit getting the information I need by just reading the source code.
I want to use your MaxLIPO+TR algorithm as a part of my hyperparameter optimization strategy, however I would like to use it in a way that I can not find documentation for....
What I want to do:
I am optimizing a single objective function, I would like to pass in the historical results of running those objective functions (which I will already have), along with the parameters that gave those results, and then I would like to receive a suggestion for the next parameters I should try.
I am aware of the "initial_function_evaluations" part of the API, and I believe I can probably figure out how to pass in the historical results (although I am a little confused by the "function_spec" objects taking in matrix<double,0,1>, which seems to indicate to me that maybe what I'm calling a "parameter" in my objective function is being called a "function" in the source code?).
The problem is that the UX doesn't seem to offer an easy way to get a suggestion for the next params to try, only provide the best params from the already evaluated results.
I believe the function I am looking for is this one: https://github.com/davisking/dlib/blob/c9a25fda0a984fa9ba754a5c918df03da8a42d38/dlib/global_optimization/global_function_search.cpp#L700
But I'm still trying to figure it out.
I'm sure I will figure this out soon enough, and if I do I will post my answer here for future user-reference, but if anyone already knows how to do this and could post some quick example code that would be extremely helpful. Thank you!

When it says "function" it's talking about the objective function.  Did you read the docs for this tool?  It goes on at some length about what you are asking about: http://dlib.net/dlib/global_optimization/global_function_search_abstract.h.html#global_function_search (get to that from http://dlib.net/optimization.html#global_function_search)

Thank you, yes I had already read the documentation, but I see after rereading it that I must not quite understand the type definition for the Matrix inputs to "function_spec". I took "Matrix<double,0,1>" to mean 0 rows, 1 column, which I assumed would just be a single value and not allow a function with multiple inputs. But obviously I should have read the entire docs for "Matrix" as well. So in conclusion looks like yes, I will be using the get_next_x function after passing in the initial_function_evaluations. I will post my actual code here once I've got it all working.

Alright for future reference if anyone else is trying to do the same thing here is an example:
          // the objective function I want to evaluate(just one in this case)
            std::function<double(double, double)> exampleFunction = [](double a, double b) {
                double result = std::pow(a, 2.0) + std::pow(b, 2.0);//known minimum at 0, 0
                //make negative because we are looking for a minimum, but global_function_search searches for a maximum
                return -1.0 * result;
            };
            //setting up the function_spec
            dlib::matrix<double, 0, 1> paramsLowerBounds({ 0,0 });
            dlib::matrix<double, 0, 1> paramsUpperBounds({ 1000000.0,1000000.0 });
            std::vector<bool> paramsAreIntegers({ false,false });
            std::vector<dlib::function_spec> functionSpecs({
                dlib::function_spec(paramsLowerBounds,paramsUpperBounds,paramsAreIntegers)
                });

            //generating some historical results to feed to the optimizer/searcher
            std::vector<dlib::function_evaluation> initialFunctionEvalsSingleFunction;
            for (double i = 2.0; i < 10.0; i++) {
                initialFunctionEvalsSingleFunction.push_back(dlib::function_evaluation(dlib::matrix<double, 0, 1>({ i,i }), exampleFunction(i,i)));
            }
            //creating the searcher
            dlib::global_function_search searcher(
                functionSpecs, std::vector<std::vector<dlib::function_evaluation>>({ initialFunctionEvalsSingleFunction })
            );
            //actual search and evaluation loop
            int numberOfFunctionCallsToTry = 100;
            for (int i = 0; i < numberOfFunctionCallsToTry; i++) {
                auto funcRequest = searcher.get_next_x();
                auto functionToEvaluateIndex = funcRequest.function_idx();// unused in this case
                dlib::matrix<double, 0, 1> paramsToEvaluateInOrder = funcRequest.x();
                double result = exampleFunction(paramsToEvaluateInOrder(0), paramsToEvaluateInOrder(1));
                funcRequest.set(result);
            }
            //get best result
            dlib::matrix<double, 0, 1> bestX;
            double bestY;
            size_t bestFunctionIndex;
            searcher.get_best_function_eval(bestX, bestY, bestFunctionIndex);//mutates the input params
            std::cout << "Best function result = " << bestY << ", best params = " << bestX << std::endl;

Additional note to future readers, log-scaling of variables can be extremely important for the performance of the algorithm, the code above does NOT include log scaling, you will have to take care of that yourself (refer to the source code of "find_max_global.h" for a good example of how to do it, but keep in mind you will ALSO have to apply log scaling to the x values of your initial function evaluations).


feat: add ability to skip OG image generation during builds

Add SKIP_OG_IMAGES env flag to optionally bypass dynamic OG image generation
Load static fallback image to use when skipping generation
Add proper caching headers for fallback image response
Significantly speeds up builds during emergency patches by avoiding resource-intensive image generation

Build time from 15 minutes to 5 minutes by setting the SKIP_OG_IMAGES=true in the environment variables.


Move timeline tool and statvar menu code to separate folders

This is to help for further refactor. No functional change in this PR.

will you be refactoring this to be more of a standalone component?

will you be refactoring this to be more of a standalone component?

Yep. The statvar menu (or svg menu) will be a standalone component. I plan to take that out from current browser code.

thanks for the refactor. it'll also be nice to eventually drop the middle "s" in "statsvar" to "statvar"

sg


If Expression support

    [<Test>]
    let ``Produces if-then expression`` () =
        AnonymousModule() {
            IfThen("x", "=", "12") {
                Value("x", "4")
                Unit()
            }
        }
        |> produces
            """

if x = 12 then
    let x = 4
    ()
"""

I can't say I'm a fan of the "x", "=", "12" part.
This is again way too specific and I think it would be better to accept any Expr instead.
You can later expand on a boolean DSL perhaps but for now, I would keep things general.

@TimLariviere Trying to accept Value and Unit breaks the Namespace, Module and Yield Collection builder extensions. So for mow, I changed to the support list of Expr for both the if and then expressions


Refactor RecurrenceGoal conflict production and solving

Tickets addressed: Resolves #1135
Review: By commit
Merge strategy: Merge (no squash)

Description

See the ticket for the original issue. The cause for this issue is that

RecurrenceGoal produces all the conflicts at once
each conflict has no relationship with the other.

Because of this independence between conflicts, we had to find a way to specify temporal constraints for each conflict. What is done is that if the recurrence interval is 1 hour, each conflict is being given a 1-hour period to insert an activity. But you can see how this can result in 2 contiguous activities being separated by more than 1 hour (the first is scheduled at the start of its interval and the other at the end of its interval (because of a mutex possibly)).
I tried 2 approaches:

going back to an iterative conflict production that was ditched less than a year ago (I'd say) in which for each goal we call getConflicts not only before but also after solving to see if new conflicts are discovered. I combined this with a change to RecurrenceGoal so that it produces only one conflict at a time. Because conflicts would be produced one at a time, it would take into account the last activity insertion. Unfortunately, it required adding a specific block for RecurrenceGoal in the solving loop and I had to update the definition of RecurrenceGoal at each iteration so it would not stay stuck in case one of the activity insertion fails. All of this just looked like a workaround for a bigger issue.
creating a new type of conflict that takes relationships between subsequent activities into account. Instead of multiple 1-activity template conflicts, we have one big MissingNetwork conflict that contains a list of activities and their temporal constraints encoded as an STN. To solve this conflict, we go through each activity in the list, build a MissingActivityTemplateConflict with the most up-to-date STN temporal constraints and give that to the regular solver for that type of conflict. Then, we update the STN bounds with the start/end times of the inserted activity, we propagate and we find the bounds for the next activity. And so on and so on.

I ended up with 2 as this is more elegant and also will be useful to instantiate task networks in #1073 #870.
I am also updating how the API of this goal to include an explicit temporal flexibility definition. Instead of just the every(Duration), I am adding separatedByNoMoreThan(Duration) and separatedByNoLessThan(Duration). The first is the one leading to conflict production. Which means that there is no penalty by having smaller separations in existing plans but... when we create new activities we use the second operator to determine the minimum space between activities.
I have refactored the satisfyGoalGeneral method of PrioritySolver to put the business logic of solving each type of conflict in its own method. It's just easier to read. And I needed to use one for this new work.
I have also refactored the satisfaction concept in the scheduler so it's not just a ill-defined number.
Verification

[x] fix the failing tests (in most of them, one too many activity is added to the plan)
[x] add at least one test reproducing the original issue

Documentation

[x] update the documentation for the new behavior/operators

Future work

None.

I faced some bugs that made me reconsider the semantics of the goal. @srschaffJPL helped me reflect on this subject, here is a summary.
Alternative (easier) way of solving this issue
When the user writes .every(1hour), we don't only allow activities to start at 0, 1, 2, 3 timepoints but we allow a default/implicit flexibility (to account for mutex/state constraints) of 1 hour. In other words we allow the first activity to start in [0, 1[, the second in [1, 2[ and so on. Which can cause activities to be separated by more than 1 hour.
We could be explicit about this flexibility with additional operators which would have the user write something like
.every(1 hour)
.plus(30 minutes)
.minus(10 minutes)

We would not have to depart from the current approach of independent conflict and activities could still be separated by more than 1 hour but it would be the user's problem, not ours. Note that the scheduler now schedules activities at their earliest start time.
Important point: in Clipper recurrence goals are mostly concerned by enforcing that 2 activities are not separated by more than some duration. So the strictness is important which would go against this alternative way of solving the issue.
Making MissingNetwork conflicts
Now let's come back to the MissingNetwork solution. One issue I was struggling with were the difference between activity and absolute timepoint boundaries.
There is one basic use case that is recurrence(activity1, activity2) that arises when there is too much time passing between the starts of activity1 and activity2. In this case, we can put constraints between missing template activities in the STN and existing activities. In other words we can bound the space between all activities. This is the easiest case.
The other basic use case that I’ll note recurrence(timepoint1, timepoint2) is the one when the plan is empty and the timepoints correspond to the start and end of the planning horizon. In this case,

what is the constraint between timepoint1 and the first template activity ? Should we consider that there exists a satisfying activity before timepoint1 (before the planning horizon start sometimes) ?
what is the constraint between the last template activity and timepoint2 ?  and so on.

What got out of the conversation is that we should let the users tell us where the activity (it’s fake though, there is no activity) before timepoint1 is, which would say when to actually start the serie. It would look like that
.separatedByNoLessThan(1)
.separatedByNoMoreThan(3)
.lastActOccurred(1)

The default value for this parameter could be the negated value of separatedByNoMoreThan, here -3 then. This would allow to conserve the usual behavior that have activities start at timepoint1 (0 if planning horizon start).
As for the timepoint2, we would not put a specific distance constraint but more of a separation constraint between the last template activity and this absolute boundary. The reason for that is that we care about what happened before the plan but not about what happens after.
What happens when one of the template in a MissingNetwork cannot be scheduled ?
Sometimes, a constraint or the mission model will make it impossible to schedule one of the activities in the “chain”, let’s say it’s activity i. That is a problem because the start bounds of activities i+1…k depend on the actual start times of activity i (they are being refined with propagation). So it seems we have to fix the STN to continue solving if we do not want to have a degraded solution. Note that this does not happen currently because each activity template is independent from others (which contributes to create the issue we are trying to solve…).
Some ways of fixing it :

transitive closures: we get the windows in which the activity has been scheduled.  We act like activity has been scheduled at its earliest start time, propagate and log that it has failed for later report
relax constraint for activity i and try again
insert absolute timepoints and reconnect following activities in the graph

From the point of view of the user, what is the best behavior is something fails in the middle ?

fit an activity somehow even with looser constraints ?
drop the activity ?

Discussed this with @adrienmaillard and @mattdailis earlier this week - looking good except it needs a rebase & potential conflict resolution.
Also @adrienmaillard when you get a chance - please write a couple sentences for the Upgrade Guide when this is released, to advise users on the impact of the change. Thanks!

I have made the changes you mentioned.

Is there any check to make sure separatedByAtLeast > separatedByAtMost?

I have just added a check in RecurrenceGoal.

Upgrade note for @dandelany
RecurrenceGoal changes
The behavior of the goal has been changed when setting its interval parameter
When setting the interval parameter to 1 hour, the old behavior would create 1-hour bins for the duration of the horizon (or the more restrictive applyWhen period) and place 1 activity in each of these bins, whenever it is possible considering global scheduling conditions.
With the new behavior, the interval parameter means a strict 1-hour distance between consecutive activities.
New parameters have been introduced to give more control over the behavior of the goal and how it is solved:

A user can now give lower (separatedByAtLeast) and upper bounds (separatedByAtMost)  on the separation between activities. Only the upper bound will lead to conflicts being created. In other words, having activities separated by less than separatedByAtLeastwill not create a conflict. But, when a conflict exists, separatedByAtLeast will be used for solving.
As said above, the old interval parameter has been left but setting it to X is equivalent to setting both separatedByAtMost and separatedByAtLeast to X.
The user can either use the interval parameter or the 2 new bounds parameters.
Another new parameter previousActivityStartedAt allows the user to specify when the “last” activity happened. It can potentially be a negative duration if it is before the start of the planning horizon. If not set, this parameter is set to -separatedByAtMost.

The solver will now try several combinations to solve this goal, starting with the least number of activities possible (separated by a greater distance), and increase the number of activities until either all the temporal constraints are satisfied or it reaches a dead-end.


there is no clipping info for given tab

Version
2.4.4
Reproduction link
https://jsfiddle.net/chrisvfritz/50wL7mdz/
Steps to reproduce
some compute(Win7 chrome 65.0.3325.181 or Ubuntu 16.04 chrome 64) will throw this question if they use<EMAIL_ADDRESS>above!
this error show this:
commons.js:1 Channel: Error in handleResponse {errorMessage: "There is no clipping info for given tab"}
log @ commons.js:1
What is expected?
why show errorMessage: "There is no clipping info for given tab"
commons.js:1 Channel: Error in handleResponse {errorMessage: "There is no clipping info for given tab"}
log @ commons.js:1
loggers.forEach.n @ commons.js:1
invokeLoggers @ commons.js:1
error @ commons.js:1
_handleResponsePromise @ commons.js:1
_handleDispatchResponse @ commons.js:1
handleMessage @ commons.js:1
listener @ commons.js:1
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
messageListener @ VM1631 extensions::messaging:240
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
dispatchOnMessage @ VM1631 extensions::messaging:392
commons.js:1 Channel: Error in handleResponse {errorMessage: "There is no clipping info for given tab"}
log @ commons.js:1
loggers.forEach.n @ commons.js:1
invokeLoggers @ commons.js:1
error @ commons.js:1
_handleResponsePromise @ commons.js:1
_handleDispatchResponse @ commons.js:1
handleMessage @ commons.js:1
listener @ commons.js:1
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
messageListener @ VM1631 extensions::messaging:240
EventImpl.dispatchToListener @ extensions::event_bindings:403
publicClassPrototype.(anonymous function) @ extensions::utils:138
EventImpl.dispatch @ extensions::event_bindings:387
EventImpl.dispatch @ extensions::event_bindings:409
publicClassPrototype.(anonymous function) @ extensions::utils:138
dispatchOnMessage @ VM1631 extensions::messaging:392
2commons.js:1 Uncaught (in promise) Error: There is no clipping info for given tab
at E._handleResponsePromise (commons.js:1)
at E._handleDispatchResponse (commons.js:1)
at E._handleMessage (commons.js:1)
at listener (commons.js:1)
at EventImpl.dispatchToListener (VM1471 extensions::event_bindings:403)
at Event.publicClassPrototype.(/anonymous function) [as dispatchToListener] (extensions::utils:138:26)
at EventImpl.dispatch (VM1471 extensions::event_bindings:387)
at EventImpl.dispatch (VM1471 extensions::event_bindings:409)
at Event.publicClassPrototype.(/anonymous function) [as dispatch] (extensions::utils:138:26)
at messageListener (VM1478 extensions::messaging:240)
What is actually happening?
how to prevent this error?

Please, follow the issue reporting guidelines
You can ask questions on the forum, the Discord server, gitter or StackOverflow.

It's raised by Evernote Web Clipper, disable this extension will make chrome get rid of this error.


Requested 'AlexaClientSDK = 1.21.0' but version of AlexaClientSDK is 1.22.0

Hello ,
I'm new to the alexa thing.
Until December 9th I had no problem to configure cmake. But today the following error appears:
`pi@AlexaRPi:~/sdk_folder/ss-build $ cmake -DCMAKE_PREFIX_PATH=$HOME/sdk_folder/sdk-install \

-DCMAKE_PREFIX_PATH=$HOME/sdk_folder/sdk-install
-DSENSORY_KEY_WORD_DETECTOR=ON
-DSENSORY_KEY_WORD_DETECTOR_LIB_PATH=/home/pi/sdk_folder/third-party/alexa-rpi/lib/libsnsr.a
-DSENSORY_KEY_WORD_DETECTOR_INCLUDE_DIR=/home/pi/sdk_folder/third-party/alexa-rpi/include
-DWEBSOCKETPP_INCLUDE_DIR=$HOME/sdk_folder/third-party/websocketpp-0.8.1
-DDISABLE_WEBSOCKET_SSL=ON
-DGSTREAMER_MEDIA_PLAYER=ON
-DCMAKE_BUILD_TYPE=DEBUG
-DPORTAUDIO=ON -DPORTAUDIO_LIB_PATH=$HOME/sdk_folder/third-party/portaudio/lib/.libs/libportaudio.a
-DPORTAUDIO_INCLUDE_DIR=$HOME/sdk_folder/third-party/portaudio/include/
-DAPL_CORE=ON
-DAPLCORE_INCLUDE_DIR=$HOME/sdk_folder/apl-core-library/aplcore/include
-DAPLCORE_LIB_DIR=$HOME/sdk_folder/apl-core-library/build/aplcore
-DAPLCORE_RAPIDJSON_INCLUDE_DIR=$HOME/sdk_folder/apl-core-library/build/rapidjson-prefix/src/rapidjson/include
-DYOGA_INCLUDE_DIR=$HOME/sdk_folder/apl-core-library/build/yoga-prefix/src/yoga
-DYOGA_LIB_DIR=$HOME/sdk_folder/apl-core-library/build/lib
-DBLUETOOTH_BLUEZ_PULSEAUDIO_OVERRIDE_ENDPOINTS=ON -DBLUETOOTH_BLUEZ=ON
../alexa-smart-screen-sdk
-- Checking for module 'AlexaClientSDK=1.21.0'
--   Requested 'AlexaClientSDK = 1.21.0' but version of AlexaClientSDK is 1.22.0
CMake Error at /usr/share/cmake-3.13/Modules/FindPkgConfig.cmake:452 (message):
A required package was not found
Call Stack (most recent call first):
/usr/share/cmake-3.13/Modules/FindPkgConfig.cmake:622 (_pkg_check_modules_internal)
modules/Alexa/CMakeLists.txt:7 (pkg_check_modules)

-- Configuring incomplete, errors occurred!
See also "/home/pi/sdk_folder/ss-build/CMakeFiles/CMakeOutput.log".`
What can I do to solve this issue?
I use a Raspberry Pi 4 with the latest Raspbian.
Sorry for my english, it's not my native language.
Thanks in advance.

@tigger-gg,
Thanks a lot for reaching out to Alexa team. It seems that you are on incorrect version of avs-device-sdk (1.22.0) that was released 5 days ago.
Here is the error:
-- Requested 'AlexaClientSDK = 1.21.0' but version of AlexaClientSDK is 1.22.0
Go to avs-device-sdk and checkout version 1.21.0 and rebuild. You will need to do a make install for the new binaries.


chore: update eslint rule no floating promises

fix: bump date-fns-tz from 3.0.0 to 3.0.1

Bumps date-fns-tz from 3.0.0 to 3.0.1.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: date-fns-tz
dependency-type: direct:production
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
fix: bump @commitlint/prompt from 19.2.0 to 19.2.2

Bumps @commitlint/prompt from 19.2.0 to 19.2.2.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: "@commitlint/prompt"
dependency-type: direct:development
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
fix: bump @commitlint/cli from 19.2.1 to 19.2.2

Bumps @commitlint/cli from 19.2.1 to 19.2.2.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: "@commitlint/cli"
dependency-type: direct:development
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
fix: bump typescript from 5.4.4 to 5.4.5

Bumps typescript from 5.4.4 to 5.4.5.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: typescript
dependency-type: direct:development
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
fix: bump semantic-release from 23.0.7 to 23.0.8

Bumps semantic-release from 23.0.7 to 23.0.8.

Release notes
Commits

updated-dependencies:

dependency-name: semantic-release
dependency-type: direct:development
update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>Co-authored-by: dependabot[bot]<EMAIL_ADDRESS>

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


Fix to FieldError fields name for duplicate param names

Fixes #2192
Changes
Changes field name from spec.inputs.params to spec.params.name to be consistent with other validation checks.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

I think the unit test needs to be fixed as well!

so embarrassed .... yes

Oopps, I got too confident, too quickly :joy_cat:

/lgtm


Recognize entities difference on versions

When calling endpoint /entities/recognition/general with the text: Bill Gates | Microsoft | salesperson | Microsoft Surface laptop | Coding
Before:
entities = 5
categories: "Person, Organization, PersonType, Product, and Skill" respectively

Now:
entities = 0

FYI @assafi


Set up Keycloak and integrate with API

Merging blocked on #575 and #627 because this contains commits from those PRs.
To use, (re)build containers:
docker-compose down
rm build/{api,keycloak,keycloak-db,local-api-data-watcher-pusher}
make build/api
make build/keycloak
make build/keycloak-db
make build/local-api-data-watcher-pusher

TODO:

[x] Fork keycloak-admin-client to https://github.com/amazeeio/keycloak-admin-client
[x] Fix security warnings
[x] Merge create group upstream into fork. Done: amazeeio/keycloak-admin-client#1
[x] Add keycloak-admin-client dependency to API
[x] Switch to keycloak-admin instead of using our fork
[x] Wait on Keycloak startup (~20 seconds) before accepting API requests
[x] addProject mutation creates Keycloak group
[x] updateProject with a new name renames Keycloak group
[x] updateProject with a new customer deletes Keycloak users with customer-only project access from the Keycloak group
[x] updateProject with a new customer adds Keycloak users with customer-only project access to the Keycloak group
[x] deleteProject deletes Keycloak group
[x] deleteAllProjects deletes all corresponding Keycloak groups
[x] addUser mutation creates Keycloak user
[x] addUserToProject adds a Keycloak user to a group
[x] removeUserFromProject deletes a Keycloak user from a group
[x] removeAllUsersFromAllProjects deletes all Keycloak users from all groups
[x] addUserToCustomer adds a Keycloak user to the groups corresponding to the customer's projects
[x] removeUserFromCustomer deletes a Keycloak user from the groups corresponding to the customer's projects
[x] removeAllUsersFromAllCustomers deletes all Keycloak users from the groups corresponding to all customers' projects
[x] Update of users
[x] Delete of users
[x] Move truncation code to each DAO file and add Keycloak deletion commands
[x] Make user.email column unique
[x] Require email to be passed to user creation command
[x] Adapt addUser mutations in api-data.gql to also specify email
[x] Configure the environment variables
[x] Pull request to override config after auth Canner/keycloak-admin#3
[x] Resolve any issues with short 60s token timeout (maybe this isn't a problem? or if it is, we can use the refresh_token)
[x] Fix bug with user email updating causing loss of group membership
[x] If User has been created from GitLab Sync system, add provided Gitlab UserID and Username as Identity Provider Links in Keycloak for the gitlab identity provider
[x] Fix Flow types in all API -> DAO files
[ ] Migrate to better folder structure for resolvers, SQL files, Keycloak files

Maybe:

Fix broken tests in keycloak-admin-client, open PR Using the keycloak-admin module instead
Change the config path back to the default $HOME/.keycloak/kcadm.config (see 3080d6cd27d99a6372b1253b0ef3f15efbb6f11a)
[ ] Improve token refresh (currently setInterval) to use refresh token to get new token
[ ] Move API authentication to Keycloak
[ ] Move rest of Users implementation to Keycloak

Nope:

deleteCustomer deletes all Keycloak groups corresponding to customer projects Don't need to do this because deleteCustomer only deletes customers without any projects assigned to them

Closes #620

Get a 60 second admin token
$ curl -X POST \
    -H 'Content-Type: application/x-www-form-urlencoded' \
    -d 'username=admin&password=admin&client_id=admin-cli&grant_type=password' \
    http://localhost:8088/auth/realms/master/protocol/openid-connect/token
{"access_token":"<access token>","expires_in":60,"refresh_expires_in":1800,"refresh_token":"<refresh token>","token_type":"bearer","not-before-policy":0,"session_state":"c22cd523-4467-4068-8524-88f7a23261c9","scope":"profile email"}

GET users
$ curl -v -X GET \
    -H 'Authorization: Bearer <access token>' http://localhost:8088/auth/admin/realms/lagoon/users
Note: Unnecessary use of -X or --request, GET is already inferred.
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 8088 (#0)
> GET /auth/admin/realms/lagoon/users HTTP/1.1
> Host: localhost:8088
> User-Agent: curl/7.54.0
> Accept: */*
> Authorization: Bearer <access token>
>
< HTTP/1.1 200 OK
< Connection: keep-alive
< Cache-Control: no-cache
< Content-Type: application/json
< Content-Length: 326
< Date: Wed, 19 Sep 2018 15:01:53 GMT
<
* Connection #0 to host localhost left intact
[{"id":"2c6cf0a8-c07d-42af-bce6-ec4ebdd4aa59","createdTimestamp":1537365502713,"username":"user","enabled":true,"totp":false,"emailVerified":false,"disableableCredentialTypes":["password"],"requiredActions":[],"notBefore":0,"access":{"manageGroupMembership":true,"view":true,"mapRoles":true,"impersonate":true,"manage":true}}]%

Ref: https://stackoverflow.com/questions/48507224/cant-access-keycloak-rest-api-methods-404

Hm, using this keycloak-admin-client library doesn't feel great:

The description describes the client as "Extremely Experimental" (it was originally conceived in this 2016 RFC)
Last commit October 2017
Lots of pull requests and issues, many without any feedback, some about broken tests or nsp security updates
It looks like creating a group is still in pull request: keycloak/keycloak-admin-client#65

I've renewed the call for an active maintainer here:
https://github.com/keycloak/keycloak-admin-client/issues/81#issuecomment-423490792
I've create an @amazeeio fork to include new features that we need, and will open pull requests for anything that makes sense.
cc @Schnitzel

Merged into #675 to collaborate better with rest of team. Will continue from there.


Syntax error in solr .install file on macOS with Ubuntu 16.04.01

Issue Type

Bug Report / Support Request

Your Environment
Vagrant 1.8.6
VirtualBox 5.1.10r112026
ansible <IP_ADDRESS>

Your OS

macOS Sierra (10.12.1 (16B2555))

Full console output
Tried to reinstall the latest DrupalVM. Destroyed the old VM, ran a cleanup then ran composer install && vagrant up. The error output is below, with the full console output in the Gist above.
https://gist.github.com/jamiehollern/530f80dc092d11ebae5fa4046f27e3f1
Summary
ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.

The error appears to have been in '/Users/jamie.hollern/Projects/elife/journal/test-cms-fork/vendor/geerlingguy/drupal-vm/provisioning/roles/geerlingguy.solr/tasks/install.yml': line 27, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- name: Run systemd daemon_reload (RHEL 7 workaround).
  ^ here

The error appears to have been in '/Users/jamie.hollern/Projects/elife/journal/test-cms-fork/vendor/geerlingguy/drupal-vm/provisioning/roles/geerlingguy.solr/tasks/install.yml': line 27, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- name: Run systemd daemon_reload (RHEL 7 workaround).
  ^ here

Ansible failed to complete successfully. Any error out

Please see my comment on https://github.com/geerlingguy/drupal-vm/issues/1065

@geerlingguy Many thanks for your prompt response, but unfortunately I'm already running that latest version of Ansible (<IP_ADDRESS>).

Hmm... so you are.
Can you verify that running which ansible shows the path to Ansible, and ansible --version definitely gives 2.2.0?
This warning occurs when Ansible can't find the module that's used in that task. In this case, it's the systemd module, which was only included in 2.2.0+: https://github.com/geerlingguy/ansible-role-solr/blob/master/tasks/install.yml#L31

Also, it is definitely using system Ansible according to the gist you posted... so this is perplexing, because 2.2.0 definitely includes the systemd module :/

@geerlingguy Figured it out. Whilst my version of Ansible was correct, the command being run was using ansible-playbook which was at version <IP_ADDRESS>. I symlinked that location to the normal ansible binary and it works perfectly now.

Great! Glad you could get that working. Also, if you're not using pip or brew to manage your Ansible installation, it might be best to switch to one of those package managers—helps to make sure all the ansible-* commands are correct :)


[SPARK-10272][Pyspark][MLLib] Added @since tags to pyspark.mllib.evaluation

Duplicated the @since decorator from pyspark.sql into pyspark (also tweaked to handle functions without docstrings).
Added @since to public methods + "versionadded::" to classes (derived from the git file history in pyspark).
Note - I added also the tags to MultilabelMetrics even though it isn't declared as public in the all statement... if that's incorrect - I'll remove.

Can one of the admins verify this patch?

add to whitelist

Merged build triggered.

Merged build started.

Test build #42467 has started for   PR 8628 at commit 9f06d04.

Test build #42467 has finished for   PR 8628 at commit 9f06d04.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

test this please

@yu-iskw Could you help review this PR? Thanks!

Merged build triggered.

Merged build started.

Test build #42643 has started for   PR 8628 at commit 9f06d04.

Test build #42643 has finished for   PR 8628 at commit 9f06d04.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

/bump @yu-iskw @mengxr

LGTM

Merged into master. Thanks!


Question: Consumer only on one broker

Hello together
We have deployed the operator on k8s and have deployed two brokers. Then we connected our application via the svc: artemis-borker-hdls-svc
But we only see the consumers for one broker and they are not visible in the Management Console under "Consumer". If we call up the metrics via curl directly on the broker, we also only see the consumers for one broker. We would have expected to see the consumers of all brokers in the Management Console.
Our goal was to set up an HA (master & slave) so that if one broker fails, the other broker takes over. Apparently this is not possible with the operator. How do we ensure HA with an operator? How can we display all consumers in the Management Console? Do we understand something wrong?
Thx!

The ArtemisCloud Operator deploys a cluster of primary brokers and each broker only show its clients. You could use the Prometheus Operator to aggregate metrics from multiple broker instances.
You can find an example of JDBC HA at https://github.com/artemiscloud/activemq-artemis-operator/blob/1.2.4/controllers/activemqartemis_jdbc_ha_test.go


MIT License?

Perhaps this repo could get a MIT License?
That would be cool for open use :)

Done! Let me know if you do anything cool with it?


Renaming Dashboard: Do not reload if renaming is exited

If I click the 'X' on the window, the dashboard is reloaded. Should not be.

@nireeshT Please see if you can resolve this one.

Closed.


Missing functions

Hi Jacob,
I came across your library and I couldn’t find a couple of functions in the library.
dposv
dpotrs
dorgqr
dgeqrf
Are you still interested in developing this library? I would be happy to fund the functions I need.
Regards,
Isaac
P.S. BTW, the library is really awesome!

Hi @neuhausi
Sorry for the late reply
I am super happy you like the blasjs library and find it very usefull.
The functions dposv,dpotrs,dorgqr,dgeqrf  are from LAPACK library, this repo is the BLAS numerical library. I Was considering developing LAPACK, it has close to 2000 kernel functions (BLAS has 100 orso subroutines)
I have reached out to you (your website https://www.canvasxpress.org/)
Best Regards
Jacob Bogers


doc: Provide detailed installation outline that works for fresh Ubuntu

Also reorganizes the documentation to prune the README to
a reasonable size.
Note that in order to get reliable installation instructions,
it was necessary to modify the recording of requirements and
add a script to install the requirements in a well-defined order,
in addition to just adding documentation.
Supersedes #49.
Resolves #73.

on it, will update per this feedback shortly.

OK, I made every change suggested (in one form or another) so I am not responding to any of the individual review comments above. But the PR is ready for re-review.

Great. So I think all this needs now to be merged is for someone to replicate the process. @liammulh please let us know if you will in the end be having time to do this. If not, we completely understand and will find another way to verify this so Kate can merge it.

Sorry, @gwhitney, @katestange, I've had a busier week than I anticipated. I am taking my car to the mechanic tomorrow morning, and I'll have (I think) a few hours before work to review/test.

I did not configure Postgres, but I don't think that was giving us any trouble. I can check Postgres later this evening if you feel it's necessary, @gwhitney. Thanks!

Confused; how did you complete the installation to a server that would respond to API requests without configuring postgres? We would definitely want the installation to go through to that point. If you don't have time to do a test that goes through to that point, just let us know and we will handle some other way. Thanks for the above feedback, I will respond to it all ASAP.

Is there an easy way to test an API request?

Sure. Have two open shells on the same Ubuntu box (either by ssh'ing in twice or by using some sort of multiplexer on a single ssh connection) and in one shell, run the server as you did above, and while it is running, in the other shell execute a curl command on a reasonable api endpoint.
I will remove the offending newline shortly. ;-)

Thanks, @gwhitney. I guess you could say I wasn't thinking outside the box. I started to use screen, but I thought "there has to be a better way."
Anyway, I SSH'd to my droplet this morning and I curl'd /api/get_oeis_values/A035513/50, which was successful. I then checked to see if there was anything in the DB using psql -U scope -d scope -F , --no-align -c "SELECT * FROM sequences WHERE id='A035513';", and that was also successful. I think that's a reasonable end-to-end test, right?

That's a reasonable end-to-end test, right?

Yup, I agree. And as I see no unresolved feedback in this PR, it'd be lovely if one of y'all approved and merged this :)


Develop add codecov

Please do not create a Pull Request without creating an issue first.
What is the purpose of the change
XXXXX
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[ ] Run mvn -B clean package apache-rat:check findbugs:findbugs -Dmaven.test.skip=true to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@a1c7715). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop       #1   +/-   ##
==========================================
  Coverage           ?   41.37%
  Complexity         ?     4375
==========================================
  Files              ?      871
  Lines              ?    31787
  Branches           ?     3704
==========================================
  Hits               ?    13151
  Misses             ?    17325
  Partials           ?     1311

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 a1c7715...3691b5d. Read the comment docs.