Change HTTP Gateway for ChainAPI test calls

We need to do change HTTP Gateway to make it usable for ChainAPI test API call purposes. The user enters values for each endpoint parameters. e.g. a currency conversion endpoint expects: from, to and amount. The enter these, click execute and the Airnode gateway gets called with these request parameters
The response gets returned to the end user. They can then play with the reserved parameters (if they are user defined) and see the encoded value change in real time. No Airnode/backend calls involved at this point.
The use case:

Let the user provide the values for the user-defined endpoint parameters
Call the gateway with these to get the JSON API response
Let the user provide the values for the reserved parameters and apply them to the JSON at the ChainAPI side to let the user figure things out by trial and error, without requiring additional API calls

Changes to be made:

Currently the gateway errors if it is called with parameters that would have made a successful API call, but not process it successfully (for example it's missing _type, which is absolutely required to be defined in all requests). For the above to be possible, the gateway needs to respond with the API response JSON and error partially while trying to encode the response.
The second change is making the reserved parameters inaccessible in pre/post processing to make sure that we can simulate how the reserved parameters will be applied consistently.

Change of the gateway discussion here
Designs on ChainAPI side here

I have an endpoint with the following reserved parameters
"reservedParameters": [
            {
              "name": "_type",
              "fixed": "int256"
            },
            {
              "name": "_path",
              "fixed": "market_data.current_price.usd"
            },
            {
              "name": "_times",
              "fixed": "1000000"
            }
          ]

When I call http-data/ with {"parameters": {"coinId": "bitcoin"}}, I get
{
    "rawValue": {
        "id": "bitcoin",
        "symbol": "btc",
        "name": "Bitcoin,
        ...
    },
    "encodedValue": "0x00000000000000000000000000000000000000000000000000000006d1c2ac40",
    "values": [
        "29289000000"
    ]
}

I update the reserved parameters as below
"reservedParameters": [
            {
              "name": "_type"
            }
          ]

When I call http-data/ with {"parameters": {"coinId": "bitcoin"}}, I get
{
    "id": "bitcoin",
    "symbol": "btc",
    "name": "Bitcoin",
    ...
}

I would have expected
{
    "rawValue": {
        "id": "bitcoin",
        "symbol": "btc",
        "name": "Bitcoin,
        ...
    }
}

I created an endpoint with a user-defined _type. I added console.log(input, endpointParameters) to its pre and post processing. Made http-data, http-signed-data, rrp requests to this endpoint where I specify the _type value in parameters. The node didn't print _type in any of these. I retried the same with Airnode v0.11 and confirmed that the older printed _type.
So other than the response schema issue here, this can be considered to be tested.
provided the _type value in the parameters of the request, and added console.log(input, endpointParameters) to pre and post processing of http-data, http-signed-data, rrp requests

@andreogle for visibility

Well yes this is expected, _type is a reserved parameter and:

We want both pre-processing and post-processing to not have access to the reserved parameters (this seems to only do it for post-processing)

from https://github.com/api3dao/airnode/pull/1831#discussion_r1266899998

No problems with that, I'm referring to this
The JSON API response is at the root of the response body or in rawValue, depending on if encoding fails. The problem is the user can't tell if the encoding will fail at runtime. This means that while ChainAPI is using http-data/ to get the raw API response, it will first need to look for a rawValue in the response body, and if it doesn't exist, fall back to using the entire body. This is ugly and becomes a more significant issue when the API response has a rawValue field at the root level.

I'm a bit confused by this. My understanding was that this change was essentially to make expose this http-data endpoint as a proxy between ChainAPI and the end API. I would expect this to respond exactly as the end API would respond - after any kind of filtering/transformations are applied. Wrapping everything in a single top level rawValue key doesn't make much sense to me.
i.e. I would expect to see this from your example above.
{
    "id": "bitcoin",
    "symbol": "btc",
    "name": "Bitcoin"
}

I'm not following why encodedValue and values are being returned. They are irrelevant for endpoint testing in ChainAPI

The only use case for encodedValue and values for the non-signed gateway is allowing someone like @metobom or a third-party service to test integrations (for example data feed templates wouldn't have any missing reserved parameters) without giving access to any signatures.

Closing this, the remainder will be tracked by https://github.com/api3dao/airnode/issues/1845


Users aren't alerted to Notification failures

OneFuzz has both webhook events and notifications. When notifications are configured, but fail to send, the failure is logged internally to an instance, but is otherwise silent. For example, the associated task is not failed. This can happen if a user has a custom analysis task that generates a structured file (like a crash report), or if they have an ADO Notification template that is malformed.
Make it so that a failed notification is observable to end users in a way that does not depend on task or user-generated data. For example, we could add webhook events for notification failures specifically, which an external service could consume and use to send emails. This could be generalized to other backend failures.
AB#39956411

@nharper285 please be sure to reference this issue in your PR using "closes".


cannot send attachments above 64KB

for example if you use ".addAttachData("picture.jpg", "image/jpg", (uint8_t *)buf,len);" with the len going over 64K, then the attachment gets truncated.
the parameters all over the library uses uint16_t
it is the case if ::addAttachData() and ::add() and for std::vector<uint16_t>, etc. etc.

Thanks for informing the issue.
Now it fixed already, please update.


Test ldc on Windows

Just a reminder that we should include ldc in our appveyor setup.

#116 fixes this :)


Publish gimme_readme as a package in the npm registry

This pertains to packaging up this tool and publishing it on the npm registry so that other users can install it via npm install and run it on their respective devices.

This will be done shortly after Release 0.1, where I have a short demo of this cli tool

gimme_readme has been published to the npm registry! You can now install this program globally via npm i -g gimme_readme.


update commands

Could you please also fill in the "Minimum Agent Version" for having documented with which version the new command is available / old deprecated.

Well it's not the agent here, it's the server that renders uploaded data in UI. So, though the command works ( it uploads the data ), after next sprint deployment the data won't be shown in UI.

The problem is that if you write custom tasks you'll have no clue which commands are available on VSTS or a certain On-Prem version (and I assume this documentation is for writing custom tasks). For you it's clear that this will change with next sprint, but from an outside point of view it's even hard to find out when a certain sprint was deployed. Even if it is not dependent on the agent, agent version is the easiest way to find out deployed sprint. I already discussed this problem with @bryanmacfarlane on other issues.

@pascalberger This particular command allows adding summary markdown to completed build. This is not about writing custom tasks. I agree that it's unclear on sprint deployments ( atleast as far as I know ). Problem with using agent version here is that, agent versions before that minimum doesn't work since it's dependent on TFS server. So it's better not to include agent version in this particular case since, whatever the agent version is, it's the server that renders the UI.


Feature Request: Allow onSelect handler to reject selection

I have another modification for you.  I need to be able to disable the selection of certain days.  It seemed to me that the easiest way to do that is to simply not select days where the onSelect handler returns false.
The following:
https://github.com/ygt-mikekchar/react-calendar-pane/compare/day-classes...ygt-mikekchar:disabled_days
Implements to reject selection.  It works like:
let onSelect = function(date) {
    if (some_test_on(date)) {
        // We don't want to select this date
        return false;
    }
    handle_the_good_selection();
}

return (
    <Calendar onSelect={onSelect} dayClasses={dayClasses}/>
);

I've updated the demo to reject selection for days in other dates.
Note: Because I'm merging my branches into my fork, the diff is against two of my own branches.  It's just there to give you an idea of the code.  I'm happy to submit pull requests if you prefer.

This issue is resolved by https://github.com/tomkp/react-calendar-pane/pull/5


API hanging when making rapid requests

It seems that the client hangs for me when I make rapid requests from the API. For example, I am trying to save every player ID to a file, but my code hangs after ~100 requests or so. About 10 minutes later it can request another 100, etc.
I figure this is an upstream issue, but was wondering if anyone had a workaround or had experienced something similar.

Sorry for getting back so late. @ryant030408 your idea of putting the time.sleep call worked great.
The code for this project is on a university repo, but if anyone wants it just shoot me an email. I'm going to go ahead and close the issue.


Why Tags are int ?

Hi,
i think in wordpress are Tags normaly "strings" why i should put a slice of ints to the tags when i create a post?
Tags          []int          json:"tags,omitempty"
How does it work?
I want to tag my post with "apple, banana, test" and so on.

I believe it's because the tags in this case are integer primary keys.

@robbiet480 do you have an idea how i can achive this?
// create non existent tags or take existent and put id to int slice
func SetOrCreateTags(tags []strings) *[]int {}

@n0v3xx I'm sorry, i'm not in a position to help as I no longer use this library, let alone WordPress.


Rules on universal selector (*) and combinors prevent using the 'lobotomised owl' selector (:scope > * + *)

I love the concept of CSS Blocks and would love to use it in my team's design system. However, it expressly forbids the use of a selector like :scope > * + * (known to some people as the lobotomised owl selector). I want to present our use-case to you and see what you think! Maybe this is a convincing argument for CSS Blocks to support the owl selector, or maybe there's an equivalent alternative way of doing the same thing in CSS Blocks that solves the same problem.
Use case: layout components
In a design system, you want components to be self contained and not have to worry about how they're laid out. We have a rule in our design system called 'No outer margins'. It should be possible to use a component anywhere without having to worry about where it will be used. If the component has a margin on the outside, it may have a gap around it where you haven't intended it.
So how do you set gaps and margins between components? In our design system, that's a the parent component's responsibility to compose them together. We call the components that have this responsibility 'layout components'.
For example, a layout component called Grid would use CSS Grid to lay out its children. And the gap property would set the gap between components. I wouldn't need to go outside of the scope of the Grid component to set the gap between child components because of the way CSS Grid works; that can be done from the parent.
/* Grid */
:scope {
  display: grid;
  gap: 1rem;
}

However, if I don't need to use a grid layout - if I just want a stack of paragraphs and images in an article to be laid out one-below-the-other - I just need the default CSS flow layout. So I need to use a margin to set a space/gap between components. That's where the owl selector comes in. I can create a layout component called Stack and it will set a gap between its children; I don't need to worry about what components those children are. (The Book 'Every Layout' makes a great case for the owl selector when explaining the Stack layout.)
<Stack>

CSS is awesome

Foo

Foo

Foo

</Stack>

/* Stack */
:scope {
  display: block;
}

:scope > * + * {
  margin-top: 1rem;
}

It's a similar problem if you're using CSS Flex to create a layout, and you need to add the flex property to the children to set varying flex amounts.

Would it be possible to use :scope > *:not(:last-child) instead?

Would it be possible to use :scope > *:not(:last-child) instead?

Yeah that would do the same thing. However, wouldn't that be against the rules of the system as well? The universal selector is forbidden. Wouldn't the :not pseudo-class have to be associated with a particular class (:scope > .foo:not(:last-child))? When creating layout components, I don't know what the class of the children will be. It's meant to be very versatile. 🙂


Store goal/constraint/condition jars in database

Rework the constraint, goal, and scheduling condition tables to accept jars.

Discussed this with @Mythicaeda @JoelCourtney @skovati and @mattdailis this morning - thanks all! We agreed on some driving requirements as well as a proposed implementation in terms of DB changes:
Requirements
Generally, we need to support procedural scheduling, which will allow users to add a new type of goal - a procedural goal with an uploaded JAR file.

Once these procedural (JAR) goals are created, users should be able to add them to their model/plan goal specs in the same way they do (or will) for EDSL goals.
It should be possible to have both EDSL goals and JAR goals in a spec, and even "interleave" them in terms of priority.
Procedural goals should use the same versioning mechanism that was built for the shared EDSL goals, and it should be possible to create a new version of an existing procedural goal with a newly-uploaded JAR file.
Procedural goals will allow arguments/parameters to be passed to them, so the DB (and UI) will need to be updated to persist and show them. This is a new feature not currently supported by EDSL goals.
Goal specs should be allowed to have the same goal multiple times, with different sets of arguments. Specs should be thought of as a list of goal instances or invocations with their own IDs, as opposed to the current design where a spec refers to goal IDs.
Existing scheduling analysis features should support analysis of procedural goals & their parameters.
The scheduling analysis table should not depend on the spec or any goal invocations within it, and should always reflect the state of goals at the time goals were run, even if they have changed since then. This is different from the current implementation, where if you remove a goal, it is also removed from analysis.

Proposed DB Changes
These are the proposed changes we agreed on in the meeting, @Mythicaeda please feel free to edit this list if I missed anything or if more changes are needed to satisfy the requirements above.

New upload endpoint, specifically for uploading a procedural goal definition/JAR
New addition to goal spec table(s): arguments field (JSONB type), representing parameters passed to the goal
New primary key on goal spec table for representing goal invocations - either a synthetic key or a new column
Changes to goal definition table:

Add new field: language which can be either "EDSL" or "JAR", to represent which type it is. (naming open to discussion)
Existing definition field may now either represent the EDSL source code, OR a pointer to a JAR, depending on value of language column

Changes to goal analysis tables:

new fields: arguments (JSONB) and priority (integer)
PK on these tables needs to change - either synthetic key of 4 columns, or new ID field
there are three goal analysis tables that all need this change

The current plan is to have @Mythicaeda work on this after the DB refactor/merge (in progress), but we can discuss if it makes sense to have someone else help with this.

Goal specs should be allowed to have the same goal multiple times, with different sets of arguments. Specs should be thought of as a list of goal instances or invocations with their own IDs, as opposed to the current design where a spec refers to goal IDs.

In our first cut - we added arguments, without relaxing the uniqueness constraint on goal id.
Work to go: design for how to allow for multiple invocations of the same goal in the same spec

Hooked up DB changes to scheduler-worker flow.


Failed to load baseapp in Docker

I tried to launch baseapp docker container, but the application was not loaded. Following the docker container logs:
2017-03-15T14:58:56.615849Z mysqld_safe Logging to syslog. 2017-03-15T14:58:56.642123Z mysqld_safe Logging to '/var/log/mysql/error.log'. 2017-03-15T14:58:56.679873Z mysqld_safe Logging to '/var/log/mysql/error.log'. 2017-03-15T14:58:56.687592Z mysqld_safe Directory '/var/run/mysqld' for UNIX socket file don't exists. mysql root password: zae7raiJohph mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! mysqladmin: [Warning] Using a password on the command line interface can be insecure. mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! mysqladmin: [Warning] Using a password on the command line interface can be insecure. mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)' Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! mysqld: no process found /usr/local/lib/python2.7/dist-packages/supervisor-3.3.1-py2.7.egg/supervisor/options.py:298: UserWarning: Supervisord is  running as root and it is searching for its configuration file in default locations (including its current working dire ctory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved se curity.   'Supervisord is running as root and it is searching ' 2017-03-15 14:59:17,602 CRIT Supervisor running as root (no user in config file) 2017-03-15 14:59:17,634 INFO RPC interface 'supervisor' initialized 2017-03-15 14:59:17,634 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2017-03-15 14:59:17,634 INFO supervisord started with pid 337 2017-03-15 14:59:18,639 INFO spawned: 'stdout' with pid 340 2017-03-15 14:59:18,655 INFO spawned: 'nginx' with pid 341 2017-03-15 14:59:18,665 INFO spawned: 'baseapp' with pid 342 2017-03-15 14:59:18,668 INFO spawned: 'mysqld' with pid 343 2017-03-15 14:59:19,769 INFO success: stdout entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:19,770 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs ) 2017-03-15 14:59:19,770 INFO success: baseapp entered RUNNING state, process has stayed up for > than 1 seconds (startse cs) 2017-03-15 14:59:19,770 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) baseapp stdout | ~ ~ revel! http://revel.github.io ~  baseapp stderr | 2017/03/15 14:59:19 revel.go:336: Failed to load module.  Import of github.com/revel/revel/modules/job s failed: cannot find package "github.com/revel/revel/modules/jobs" in any of:         /usr/lib/go-1.6/src/github.com/revel/revel/modules/jobs (from $GOROOT)         /go/src/github.com/revel/revel/modules/jobs (from $GOPATH) 2017-03-15 14:59:19,980 INFO exited: baseapp (exit status 1; not expected) 2017-03-15 14:59:19,984 INFO spawned: 'baseapp' with pid 348 baseapp stdout | ~ ~ revel! http://revel.github.io ~  baseapp stderr | 2017/03/15 14:59:19 revel.go:336: Failed to load module.  Import of github.com/revel/revel/modules/sta tic failed: cannot find package "github.com/revel/revel/modules/static" in any of:         /usr/lib/go-1.6/src/github.com/revel/revel/modules/static (from $GOROOT)         /go/src/github.com/revel/revel/modules/static (from $GOPATH) 2017-03-15 14:59:20,012 INFO exited: baseapp (exit status 1; not expected) 2017-03-15 14:59:21,276 INFO spawned: 'baseapp' with pid 377 baseapp stdout | ~ ~ revel! http://revel.github.io ~  baseapp stderr | 2017/03/15 14:59:21 revel.go:336: Failed to load module.  Import of github.com/revel/revel/modules/job s failed: cannot find package "github.com/revel/revel/modules/jobs" in any of:         /usr/lib/go-1.6/src/github.com/revel/revel/modules/jobs (from $GOROOT)         /go/src/github.com/revel/revel/modules/jobs (from $GOPATH) 2017-03-15 14:59:21,300 INFO exited: baseapp (exit status 1; not expected) 2017-03-15 14:59:22,583 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:23,587 INFO spawned: 'baseapp' with pid 381 2017-03-15 14:59:23,601 INFO spawned: 'mysqld' with pid 382 baseapp stdout | ~ ~ revel! http://revel.github.io ~  baseapp stderr | 2017/03/15 14:59:23 revel.go:336: Failed to load module.  Import of github.com/revel/revel/modules/sta tic failed: cannot find package "github.com/revel/revel/modules/static" in any of:         /usr/lib/go-1.6/src/github.com/revel/revel/modules/static (from $GOROOT)         /go/src/github.com/revel/revel/modules/static (from $GOPATH) 2017-03-15 14:59:23,621 INFO exited: baseapp (exit status 1; not expected) 2017-03-15 14:59:24,783 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:25,557 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:26,563 INFO spawned: 'mysqld' with pid 411 2017-03-15 14:59:26,743 INFO spawned: 'baseapp' with pid 413 baseapp stdout | ~ ~ revel! http://revel.github.io ~  baseapp stderr | 2017/03/15 14:59:26 revel.go:336: Failed to load module.  Import of github.com/revel/revel/modules/sta tic failed: cannot find package "github.com/revel/revel/modules/static" in any of:         /usr/lib/go-1.6/src/github.com/revel/revel/modules/static (from $GOROOT)         /go/src/github.com/revel/revel/modules/static (from $GOPATH) 2017-03-15 14:59:26,754 INFO exited: baseapp (exit status 1; not expected) 2017-03-15 14:59:27,754 INFO gave up: baseapp entered FATAL state, too many start retries too quickly 2017-03-15 14:59:27,758 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:28,524 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:29,530 INFO spawned: 'mysqld' with pid 440 2017-03-15 14:59:30,722 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:31,493 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:32,499 INFO spawned: 'mysqld' with pid 466 2017-03-15 14:59:33,684 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:34,474 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:35,479 INFO spawned: 'mysqld' with pid 492 2017-03-15 14:59:36,673 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:37,493 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:38,496 INFO spawned: 'mysqld' with pid 518 2017-03-15 14:59:39,664 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:40,432 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:41,439 INFO spawned: 'mysqld' with pid 544 2017-03-15 14:59:42,624 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:43,395 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:44,401 INFO spawned: 'mysqld' with pid 570 2017-03-15 14:59:45,583 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:46,356 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:47,364 INFO spawned: 'mysqld' with pid 596 2017-03-15 14:59:48,553 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:49,344 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:50,351 INFO spawned: 'mysqld' with pid 622 2017-03-15 14:59:51,532 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:52,325 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:53,333 INFO spawned: 'mysqld' with pid 648 2017-03-15 14:59:54,523 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:55,365 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:56,371 INFO spawned: 'mysqld' with pid 674 2017-03-15 14:59:57,553 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 14:59:58,325 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 14:59:59,331 INFO spawned: 'mysqld' with pid 700 2017-03-15 15:00:00,523 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:01,617 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:02,624 INFO spawned: 'mysqld' with pid 726 2017-03-15 15:00:03,815 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:04,626 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:05,634 INFO spawned: 'mysqld' with pid 752 2017-03-15 15:00:06,825 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:07,605 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:08,612 INFO spawned: 'mysqld' with pid 778 2017-03-15 15:00:09,794 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:10,647 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:11,654 INFO spawned: 'mysqld' with pid 804 2017-03-15 15:00:12,854 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:13,636 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:14,641 INFO spawned: 'mysqld' with pid 830 2017-03-15 15:00:15,815 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:16,605 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:17,611 INFO spawned: 'mysqld' with pid 856 2017-03-15 15:00:18,794 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:19,634 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:20,641 INFO spawned: 'mysqld' with pid 882 2017-03-15 15:00:21,825 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:22,596 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:23,603 INFO spawned: 'mysqld' with pid 908 2017-03-15 15:00:24,784 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:25,565 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:26,572 INFO spawned: 'mysqld' with pid 934 2017-03-15 15:00:27,755 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:28,536 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:29,544 INFO spawned: 'mysqld' with pid 960 2017-03-15 15:00:30,734 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:31,515 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:32,521 INFO spawned: 'mysqld' with pid 986 2017-03-15 15:00:33,694 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:34,474 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:35,482 INFO spawned: 'mysqld' with pid 1012 2017-03-15 15:00:36,664 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:37,455 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:38,462 INFO spawned: 'mysqld' with pid 1038 2017-03-15 15:00:39,655 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:40,634 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:41,637 INFO spawned: 'mysqld' with pid 1064 2017-03-15 15:00:42,804 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:43,504 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:44,507 INFO spawned: 'mysqld' with pid 1090 2017-03-15 15:00:45,674 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:46,444 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:47,451 INFO spawned: 'mysqld' with pid 1116 2017-03-15 15:00:48,634 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:49,497 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:50,504 INFO spawned: 'mysqld' with pid 1142 2017-03-15 15:00:51,684 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:52,476 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:53,483 INFO spawned: 'mysqld' with pid 1168 2017-03-15 15:00:54,682 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:55,456 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:56,459 INFO spawned: 'mysqld' with pid 1194 2017-03-15 15:00:57,625 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:00:58,476 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:00:59,481 INFO spawned: 'mysqld' with pid 1220 2017-03-15 15:01:00,654 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:01,424 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:02,431 INFO spawned: 'mysqld' with pid 1246 2017-03-15 15:01:03,614 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:04,466 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:05,471 INFO spawned: 'mysqld' with pid 1272 2017-03-15 15:01:06,644 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:07,485 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:08,488 INFO spawned: 'mysqld' with pid 1298 2017-03-15 15:01:09,665 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:10,465 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:11,468 INFO spawned: 'mysqld' with pid 1324 2017-03-15 15:01:12,634 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:13,414 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:14,418 INFO spawned: 'mysqld' with pid 1350 2017-03-15 15:01:15,584 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:16,354 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:17,360 INFO spawned: 'mysqld' with pid 1376 2017-03-15 15:01:18,554 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:19,344 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:20,350 INFO spawned: 'mysqld' with pid 1402 2017-03-15 15:01:21,534 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:22,314 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:23,320 INFO spawned: 'mysqld' with pid 1428 2017-03-15 15:01:24,514 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:25,236 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:26,243 INFO spawned: 'mysqld' with pid 1454 2017-03-15 15:01:27,425 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:28,254 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:29,260 INFO spawned: 'mysqld' with pid 1480 2017-03-15 15:01:30,444 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:31,254 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:32,260 INFO spawned: 'mysqld' with pid 1506 2017-03-15 15:01:33,443 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:34,224 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:35,230 INFO spawned: 'mysqld' with pid 1532 2017-03-15 15:01:36,424 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:37,436 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:38,443 INFO spawned: 'mysqld' with pid 1558 2017-03-15 15:01:39,634 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:40,425 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:41,431 INFO spawned: 'mysqld' with pid 1584 2017-03-15 15:01:42,625 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:43,426 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:44,432 INFO spawned: 'mysqld' with pid 1610 2017-03-15 15:01:45,655 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:46,435 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:47,441 INFO spawned: 'mysqld' with pid 1636 2017-03-15 15:01:48,624 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:49,405 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:50,411 INFO spawned: 'mysqld' with pid 1662 2017-03-15 15:01:51,594 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:52,357 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:53,364 INFO spawned: 'mysqld' with pid 1688 2017-03-15 15:01:54,555 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:55,384 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:56,391 INFO spawned: 'mysqld' with pid 1714 2017-03-15 15:01:57,583 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:01:58,356 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:01:59,364 INFO spawned: 'mysqld' with pid 1740 2017-03-15 15:02:00,555 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:01,374 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:02,382 INFO spawned: 'mysqld' with pid 1766 2017-03-15 15:02:03,574 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:04,345 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:05,352 INFO spawned: 'mysqld' with pid 1792 2017-03-15 15:02:06,545 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:07,346 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:08,355 INFO spawned: 'mysqld' with pid 1818 2017-03-15 15:02:09,544 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:10,377 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:11,384 INFO spawned: 'mysqld' with pid 1844 2017-03-15 15:02:12,574 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:13,557 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:14,561 INFO spawned: 'mysqld' with pid 1870 2017-03-15 15:02:15,724 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:16,557 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:17,564 INFO spawned: 'mysqld' with pid 1896 2017-03-15 15:02:18,754 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:19,545 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:20,552 INFO spawned: 'mysqld' with pid 1922 2017-03-15 15:02:21,735 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:22,596 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:23,604 INFO spawned: 'mysqld' with pid 1948 2017-03-15 15:02:24,783 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:25,576 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:26,584 INFO spawned: 'mysqld' with pid 1974 2017-03-15 15:02:27,775 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:28,547 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:29,555 INFO spawned: 'mysqld' with pid 2000 2017-03-15 15:02:30,744 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:31,544 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:32,548 INFO spawned: 'mysqld' with pid 2026 2017-03-15 15:02:33,724 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:34,494 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:35,500 INFO spawned: 'mysqld' with pid 2052 2017-03-15 15:02:36,684 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:37,464 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:38,468 INFO spawned: 'mysqld' with pid 2078 2017-03-15 15:02:39,644 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:40,414 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:41,419 INFO spawned: 'mysqld' with pid 2104 2017-03-15 15:02:42,594 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:43,385 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:44,393 INFO spawned: 'mysqld' with pid 2130 2017-03-15 15:02:45,574 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:46,344 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:47,349 INFO spawned: 'mysqld' with pid 2156 2017-03-15 15:02:48,534 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:49,327 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:50,334 INFO spawned: 'mysqld' with pid 2182 2017-03-15 15:02:51,524 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:52,296 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:53,304 INFO spawned: 'mysqld' with pid 2208 2017-03-15 15:02:54,493 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:55,296 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:56,303 INFO spawned: 'mysqld' with pid 2234 2017-03-15 15:02:57,499 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:02:58,306 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:02:59,313 INFO spawned: 'mysqld' with pid 2260 2017-03-15 15:03:00,504 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:01,345 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:02,348 INFO spawned: 'mysqld' with pid 2286 2017-03-15 15:03:03,514 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:04,354 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:05,361 INFO spawned: 'mysqld' with pid 2312 2017-03-15 15:03:06,554 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:07,326 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:08,332 INFO spawned: 'mysqld' with pid 2338 2017-03-15 15:03:09,504 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:10,264 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:11,271 INFO spawned: 'mysqld' with pid 2364 2017-03-15 15:03:12,464 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:13,257 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:14,265 INFO spawned: 'mysqld' with pid 2390 2017-03-15 15:03:15,464 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:16,324 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:17,330 INFO spawned: 'mysqld' with pid 2416 2017-03-15 15:03:18,517 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:19,497 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:20,503 INFO spawned: 'mysqld' with pid 2442 2017-03-15 15:03:21,674 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:22,446 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:23,453 INFO spawned: 'mysqld' with pid 2468 2017-03-15 15:03:24,634 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:25,414 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:26,420 INFO spawned: 'mysqld' with pid 2494 2017-03-15 15:03:27,604 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:28,424 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:29,432 INFO spawned: 'mysqld' with pid 2520 2017-03-15 15:03:30,614 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:31,406 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:32,414 INFO spawned: 'mysqld' with pid 2546 2017-03-15 15:03:33,604 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:34,434 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:35,438 INFO spawned: 'mysqld' with pid 2572 2017-03-15 15:03:36,615 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:37,406 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:38,414 INFO spawned: 'mysqld' with pid 2598 2017-03-15 15:03:39,605 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:40,467 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:41,474 INFO spawned: 'mysqld' with pid 2624 2017-03-15 15:03:42,664 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:43,574 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:44,580 INFO spawned: 'mysqld' with pid 2650 2017-03-15 15:03:45,764 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:46,546 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:47,554 INFO spawned: 'mysqld' with pid 2676 2017-03-15 15:03:48,744 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:49,615 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:50,618 INFO spawned: 'mysqld' with pid 2702 2017-03-15 15:03:51,784 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:52,545 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:53,550 INFO spawned: 'mysqld' with pid 2728 2017-03-15 15:03:54,726 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:55,714 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:56,718 INFO spawned: 'mysqld' with pid 2754 2017-03-15 15:03:57,894 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:03:58,674 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:03:59,681 INFO spawned: 'mysqld' with pid 2780 2017-03-15 15:04:00,865 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:04:01,637 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:04:02,643 INFO spawned: 'mysqld' with pid 2806 2017-03-15 15:04:03,824 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:04:04,667 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:04:05,675 INFO spawned: 'mysqld' with pid 2832 2017-03-15 15:04:06,854 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:04:07,636 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:04:08,642 INFO spawned: 'mysqld' with pid 2858 2017-03-15 15:04:09,834 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:04:10,706 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:04:11,713 INFO spawned: 'mysqld' with pid 2884 2017-03-15 15:04:12,894 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:04:13,686 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:04:14,693 INFO spawned: 'mysqld' with pid 2910 2017-03-15 15:04:15,884 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:04:16,664 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:04:17,671 INFO spawned: 'mysqld' with pid 2936 2017-03-15 15:04:18,855 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:04:19,707 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:04:20,714 INFO spawned: 'mysqld' with pid 2962 2017-03-15 15:04:21,904 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s) 2017-03-15 15:04:22,675 INFO exited: mysqld (exit status 1; not expected) 2017-03-15 15:04:23,681 INFO spawned: 'mysqld' with pid 2988 2017-03-15 15:04:24,875 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsec s)

In https://github.com/richtr/baseapp/commit/c2b7c4457b4246a9284b31c162aed03112d6c554 I have greatly simplified and minimized the Dockerfile contents. mysql is no longer bundled in the Dockerfile.
The idea here is that MySQL (or PostgreSQL) should be run in a separate docker container. Then the app.conf file should be modified and injected in to the baseapp container to point to this external mysql file.
Coordination of multiple containers can be done with docker-compose.
NOTE: please make sure you change your mysql passwords as I think you accidentally copy/pasted them above ;)

Thanks for the fix, but now I have the following error if  I try to build by docker-compose
ERROR: Service 'baseapp' failed to build: The command '/bin/sh -c apk add --no-cache gcc g++ git pwgen bash &&
cd $BASEAPP_PATH &&             go get -v ./... github.com/revel/revel github.com/revel/cmd/revel github.com/go-sql-driv
er/mysql &&             chmod 755 /start.sh' returned a non-zero code: 1

I have now extensively refactored the included docker-compose file + docker bootstrap files.
I have also introduced vendoring in to the project via godeps.
Please pull the latest version and let me know if it works for you.

Thanks Richtr.
I successfully build the docker compose, but when I returned a 502 Bad Gateway when I try to access via browser.In the logs I can see only
nginx_1    | 2017/04/28 08:36:18 [error] 7#7: *43 connect() failed (111: Connection refused) while connecting to upstrea
m, client: <IP_ADDRESS>, server: , request: "GET / HTTP/1.1", upstream: "http://<IP_ADDRESS>:9000/", host: "<IP_ADDRESS>
"
nginx_1    | <IP_ADDRESS> - - [28/Apr/2017:08:36:18 +0000] "GET / HTTP/1.1" 502 575 "-" "Mozilla/5.0 (Windows NT 6.1; WO
W64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36" "-"
nginx_1    | 2017/04/28 08:36:18 [error] 7#7: *43 connect() failed (111: Connection refused) while connecting to upstrea
m, client: <IP_ADDRESS>, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://<IP_ADDRESS>:9000/favicon.ico",
 host: "<IP_ADDRESS>", referrer: "http://<IP_ADDRESS>/"

It can take quite a while (up to a couple of minutes) for BaseApp to compile in the docker container.
Keep docker-compose up running until you see Listening on :9000... in the console!


[🐛] Calling [node<EMAIL_ADDRESS>config] finished with an exception. Error message: groovy.json.JsonException: Unable to determine the current character, it is not a string, number, array, or object

ng "react-native config" command and contact the package maintainers about this.
info Fetching system and libraries information...
System:
OS: Linux 5.19 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-12400
Memory: 839.79 MB / 15.39 GB
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 14.21.3 - /usr/bin/node
Yarn: Not Found
npm: 6.14.18 - /usr/bin/npm
Watchman: Not Found
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java: 11.0.19 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: ^18.2.0 => 18.2.0
react-native: ^0.70.5 => 0.70.12
npmGlobalPackages:
react-native: Not Found

Same error ,any solution?

I ran the npx --quiet react-native config command and encountered the following error:
"No package name found. Found errors in ../projectname/node_modules/react-native-image-picker/android/src/main/AndroidManifest.xml."
Upon investigation, I discovered that the package="com.imagepicker" attribute is missing in the AndroidManifest.xml file.

any updates on this problem? I need some help with React Native 0.70.5

@jeffinhk install 5.4.2 version for react-native-image-picker it worked. for me.


Why comes with useless style?

That's probably from having seen a 404 page, and the styles leaked. We've addressed this in master already.


[mod]use 'decisionHandler(WKNavigationActionPolicyCancel)' to replace…

Here is my reason.
https://github.com/marcuswestin/WebViewJavascriptBridge/issues/163

@lokimeyburg please review and merge or close.

I spent the day doing a bunch of changes - I'll take on this and the other PRs :)
Great explanation in #163 @lbj96347, thanks!

@lbj96347 I really appreciate that sort of thoroughness. I'm giving you repo access. Use responsibly please :)

@marcuswestin Don’t mention it. :-) We also thank you for your project.Our app "留白·WHITE" uses WebViewJavascriptBridge.It could be a quite important part in our app.


Large modal won't mouse scroll on small page

I'm using a modal to show a list that is often bigger than the screen so you need to scroll. However mouse scrolling often doesn't work (using arrow keys still works though).
I found out that this happens when the page behind the modal is smaller than the screen (so it has no scrollbar).
So basically when the page is too small to scroll any modal that you open on it can't be scrolled either even if the modal is too big for the screen.
I already tried this css to always force the scrollbar:
body {
overflow-y: scroll !important;
}
This doesn't fix the problem, only 'solution' so far is this css:
html {
height:101%;
}
Which I 'improved' to doing this when the modal opens (coffeescript):
$('html').css('height', '101%')
@timeout ->
$('html').css('height', '100%')
, 300
I haven't tried the new $uibModal yet.
Any else encountered this issue?

@Janneman84, please do not use the issues forum for support related requests.  Rather, please follow the instructions here.  The issues forum is reserved for bugs.
If you think you've found a bug, please follow these instructions.
Unfortunately, if you think you have found a bug and do not follow the above instructions within a reasonable amount of time, we will close the issue due to lack of activity.

It is up to the user to control the CSS - my recommendation would be to use max-height on the modal to control the viewport for smaller screens.
Closing as a usage issue.

I'm having this problem too, though only on Windows and on Chrome (not tested in IE). On Firefox in Windows it's fine, and on Mac there is no problem either (both Chrome / Firefox). Both solutions proposed work (either setting an height in the modal, or making the body height at 101%) but these solutions are more workarounds than a solution and making such a workaround for just 1 browser for 1 platform (affecting everything else) is a bit awkward.
I understand it's a CSS issue, but the uibModal is much about CSS ... :)
A plunkr: http://plnkr.co/edit/qkgRpZlVGy5hSfygMwNz?p=preview
You need to "Launch the preview in a separate window" in Windows/Chrome for seeing the issue. In the embedded Window, it scrolls well.


Unable to specify the Stage when subscribing to all Pipelines in a project

When  subscribing to a project, the Stage dropdown does not present the available Environments or Stages [Any] is the only stage choice and I need to select a specific stage

@shannonlharris -- Shannon, thank you for your feedback.  Are you following a particular docs.microsoft.com article?  Meanwhile, please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow


After the last update 1.7.2 nog working

Hello,
After the last update the plug-in is not startend anymore.

I have not changed Any thing in the config

Please take a look at the v1.7.0 release.
NOTE: The mqtt broker port is now a string. Just quote your port like this port: "1883"


Need for Planned Deposit/Withdraw Outage Times

Description
For the sake of appearing reliable, there is need to be able to pre-plan outage times for Token/Network Deposits and Withdrawals. A common example would be when Axelar undergoes an upgrade, and all bridging attempts from Osmosis, if permitted by the frontend, would fail for a few hours. These upgrades are at predicable times and block heights, with sufficient warning, so there is npo reason why can't plan for them.
We've historically had two methods to deal with this: either,

mark all the tokens associated with that network as isUnstable: true, and hope that the PR gets created, validated, and approved in time for the upgrade, and also make sure someone is around to merge precisely when the upgrade begins, and repeat for the completion of the upgrade, which is sometime not known ahead of time; or,
do nothing, and allow users experience unexplained degraded performance, sullying their impression of Osmosis, Osmosis frontend, and/or Axelar.

Requested Functionality
In the future, it would be ideal if we could pre-plan an outage, automatically disabling deposits/withdrawal for all tokens associated with the network at exactly when the upgrade is scheduled to begin, and automatically restoring deposits/withdrawls when the generous outage time-frame is complete, or when the outage is manually updated as 'finished', (or when an API/endpoints returns a certain value??,) whichever comes first.
In addition, it would be best to have an additional generic deposit/withdrawal disablement message beyond 'instability', due to potential negative implications. Something more like, 'temporarily disabled due to network upgrade' would give a better indication to the user that the network isn't actually unstable/broken/built poorly/etc., but rather that it's just going through an upgrade; as well, that deposits and withdrawals will be restored soon.
Potential Solution
Add an additional outage message, and have it activate at a certain block height. Assuming that a network with reach a specific block height when scheduled to upgrade and not advance to a new block until the block height is complete, a simple endpoint status query should be able to indicate to the client whether the upgrade is still ongoing.
Please discuss other ideas below.

Closing for now until that convo is arrived at.


Deveoper's Website Spreading Viruses

Just what the title says!

Can confirm. This needs to be changed ASAP!


ISPN-6740 Client topologies not updated with persistent state

Backport of https://github.com/infinispan/infinispan/pull/4391 for 8.2.x
https://issues.jboss.org/browse/ISPN-6740
The HotRod client starts with topology id 0, so we initialize the
cache with topology id 1 to force a topology update on the first ping.

integrated! thanks @danberindei !


Huge Log

This is more of a question than a problem (I hope) but is an AdaptiveRoads.log file of around 500 MB (532,459 KB to be exact) normal or to be expected?  That's how big mine is, with a total of 5,101,328 lines (mostly [Debug] it looks like, but also [Info]) with a cumulative (??) time of 6,076,267ms, or about 101 minutes if I'm reading that correctly.
It starts with:
[Info]   21,236ms | Log file at C:/Program Files (x86)/Steam/steamapps/common/Cities_Skylines/Cities_Data\Logs\AdaptiveRoads.log now=7/30/2022 4:38:10 AM
[Info]   21,237ms | AdaptiveRoads Version:<IP_ADDRESS>20 Commit:7604473 CommitDate:2022-07-03T21:38:09+03:00
[Debug]  21,237ms | Testing StackTrace:
at AdaptiveRoads.LifeCycle.LifeCycle.Enable()
at AdaptiveRoads.LifeCycle.UserMod.OnEnabled()
at System.Reflection.MonoMethod.InternalInvoke(System.Object , System.Object[] , System.Exception ByRef )
at System.Reflection.MonoMethod.Invoke(System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture)
at System.Reflection.MethodBase.Invoke(System.Object obj, System.Object[] parameters)
at ColossalFramework.Plugins.PluginManager.AddPlugins(System.Collections.Generic.Dictionary`2 plugins)
at ColossalFramework.Plugins.PluginManager.LoadPlugins()
at Starter.Awake()
[Info]   21,238ms | Found plug-in:Adaptive Networks 3.8
[Info]   21,239ms | Initializing Log.FlushTread
[Info]   21,241ms | LifeCycle.HotReload3rdparty() called.
...
[Info]   22,134ms | LifeCycle.HotReload3rdparty() called.
[Info]   31,026ms | option Verbose log is False
[Info]   31,027ms | option Buffered log is True
[Info]   85,435ms | LifeCycle.HotReload3rdparty() called.
[Info]   87,115ms | option Verbose log is False
[Info]   87,116ms | option Buffered log is True
[Info]   274,321ms | LifeCycle.Preload() called
Then lists my mods.  AdaptiveRoads.Patches seem to be applied, then Harmony.  AssetDataExtension.OnAssetLoadedImpl is called for all kinds of things.  Net Metadata is restored for a number of things.  As an example:
AssetDataExtension.OnAssetLoadedImpl(): extracted data for AdvancedRoadEditor_NetInfoExt
[Info]   304,267ms | AssetData.Load(AdaptiveRoads.Manager.AssetData,<PHONE_NUMBER>.Double Steel Barrier - raisable_Data (NetInfo)) called.
[Info]   304,268ms | NetInfoExtionsion.EnsureExtended(1889660581.Double Steel Barrier - raisable_Data (NetInfo), False) called.
[Debug]  304,269ms | EnsureExtended(1889660581.Double Steel Barrier - raisable_Data (NetInfo)): successful
[Info]   304,269ms | Net.Recalculate(1889660581.Double Steel Barrier - raisable_Data (NetInfo)) called.
[Info]   304,269ms | Net.RefreshLevelOfDetail() called.
[Info]   304,269ms | Net.RecalculateConnectGroups() called.
[Info]   304,269ms | Net.OptimizeUserData() called.
[Info]   304,269ms | Segment.OptimizeUserData() called.
[Debug]  304,269ms | Net Metadata restored.
The vast majority of entries are similar to these:
[Debug]  780,088ms | mark node:162 info:Pedestrian Gravel (NetInfo) update-level=-1 from segment:0
[Debug]  780,089ms | mark segment:22878 info:Pedestrian Gravel (NetInfo) update-level=0 from node:162
[Debug]  780,089ms | mark node:16628 info:Pedestrian Gravel (NetInfo) update-level=1 from segment:22878
[Debug]  780,089ms | mark node:16628 info:Pedestrian Gravel (NetInfo) update-level=-1 from segment:0
There doesn't appear to be any real errors or problems, and as I had just started a new game I can see an initial index or something being created right from the start which can be very long.
  Thanks!  (Log file can be provided if needed.)

If i See it correct, you are subscribed to the Alpha version, or? If so: yes expected as we need a Lot of information in Life If  we implement new features. The stable Version should Not do debug logging.

I can confirm the OPs issue. I have here a small city with ~30k Sims, the log is "only" 41MB.
But counting the [Debug] lines gives 410832 Debug lines (out of 417108 total lines)
$ grep -c "[Debug]" AdaptiveRoads.log
410832
$ grep -c "[Info]" AdaptiveRoads.log
3397
$ grep -c "[Warning]" AdaptiveRoads.log
2768
$ wc -l AdaptiveRoads.log
417108 AdaptiveRoads.log
I'm subscribed to stable version (see last line below)

[Info]   0ms | Log file at /hdisks/data2/SteamLibrary/steamapps/common/Cities_Skylines/Cities_Data/Logs/AdaptiveRoads.log now=08/10/2022 13:58:24
[Info]   0ms | AdaptiveRoads Version:<IP_ADDRESS>20 Commit:7604473 CommitDate:2022-07-03T21:38:09+03:00
[Debug]  0ms | Testing StackTrace:
at AdaptiveRoads.LifeCycle.LifeCycle.Enable()
at AdaptiveRoads.LifeCycle.UserMod.OnEnabled()
at System.Reflection.MonoMethod.InternalInvoke(System.Object , System.Object[] , System.Exception ByRef )
at System.Reflection.MonoMethod.Invoke(System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture)
at System.Reflection.MethodBase.Invoke(System.Object obj, System.Object[] parameters)
at ColossalFramework.Plugins.PluginManager.AddPlugins(System.Collections.Generic.Dictionary`2 plugins)
at ColossalFramework.Plugins.PluginManager.LoadPlugins()
at Starter.Awake()
[Info]   8ms | Found plug-in:Adaptive Networks 3.8
[Info]   8ms | Initializing Log.FlushTread
[Info]   9ms | LifeCycle.HotReload3rdparty() called.
[Info]   9,733ms | option Verbose log is False
[Info]   9,733ms | option Buffered log is True
[Info]   116,467ms | LifeCycle.Preload() called
[Info]   116,469ms | Installed mods are:
...
...
*<PHONE_NUMBER> Adaptive Networks 3.8
...
...

closing because Stable has less log.


Defaults in README.md don't match values.yml

The default JVM options documented in README.md don't match the ones in values.yml.
I assume the README.md needs updating because we reviewed and discussed values.yml in PR #82.

fixed


Pass the user to the callback

The user is currently not being passed to the callback in case of a verification failure (INVALID_CREDENTIALS). So currently this:
<?php
Verifi::verify(request(), function ($user) {
  //verification logic
});

will result in

(1/1) FatalThrowableError
Type error: Too few arguments to function App\Http\Controllers\Auth\VerifyController::App\Http\Controllers\Auth{closure}(), 0 passed and exactly 1 expected

and the developer would have to make the user param optional, like below
<?php
Verifi::verify(request(), function ($user = null) {
   //verification logic
});

@SelimSalihovic Thanks 👍


Popup doesn't show

Integration version: 1.5.0.
Device: Pixel 6a
App version: 2023.10.2-full.
Same dashboard on Galaxy S21 Ultra is shown without any troubles, with all popups.
The difference, except the phone, is that troublesome user is not admin.
Any advice? Don't want to move to Browser mod, but WAF is dropping.

Sorry, looks like false alarm. I cleaned the cache and app data, re-logged in, and it wasn't working - but after some time it started to, weirdly.


Find Widget doesn't trap focus

The latest updates mention the Find Widget's tab order is improved and I agree! Thanks!
However, unlike full Visual Studio, tabbing within the widget doesn't confine the focus; eventually I end up back in my document and the only way to get back is Ctrl+F or Ctrl+H. I'm not sure if this is intentional (with all your other a11y changes) but I generally prefer the way Visual Studio does it.
Bug? Setting?

This is for accessibility purposes. In our environment the only way to go to the next focusable element is via Tab and for that reason we should not trap focus -- otherwise folks who cannot use a mouse will not be able to escape the find widget.

I'm sorry, but that makes no sense. Every other IDE I've used traps focus in the find widget/panel.
I just tested with what I have installed:

Sublime Text - Esc key escapes the find panels. Tab toggles between "Find What:" and "Replace With:"
Visual Studio 2015 - Esc key escapes the find and replace panel. Tab toggles between all the fields.
Atom - Esc key escapes both the Find in current buffer and Find in project panels. Tab toggles between the text fields.
I could go on...

The Esc key should escape focus and restore focus to whatever was found.


Service Worker always offline on new Chrome 86

What I'm trying to achieve
My chrome got an update on mac - and since then, the webshop stays offline!! The same issue for the hosted saleor version. In the network dev tools, I see 200 Ok from GraphQL, but still offline :/ don't know, what they changed.
Steps to reproduce the problem

What I expected to happen
…
Screenshots

System information
Operating system:
Browser:

@JannikZed Hey! Do you still have this error?

actually no - don't know what happened there.


Local E2E tests fail with crosschain_swap failed: btc transaction not signed

Describe the Bug
The Bitcoin local e2e Crosschain Swap sometimes fails with the error
bitcoin tests failed: crosschain_swap failed: btc transaction not signed, stack trace goroutine 119 [running]:

This used to happen sometimes but appears to occur more and more frequently, we should therefore consider fixing it once for all
To Reproduce
Happens sometime in E2E tests execution like: https://github.com/zeta-chain/node/actions/runs/8877450563/job/24371074194?pr=2060
It appears to never happens locallly on my side
Screenshots

https://github.com/zeta-chain/node/actions/runs/8972215322/job/24639719251?pr=2119

https://github.com/zeta-chain/node/runs/24807859621

https://github.com/zeta-chain/node/actions/runs/9169683804/job/25210551669


⚠ PrivateHD has degraded performance

In 5ffae40, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1232 ms

Resolved: PrivateHD performance has improved in 0148350.


Events on creation

Added assignee_changed and status_changed events for the initial values of the issue when it was created
Updated tests
Using matchers from rchampourlier/golib

Fixes #27
TODO

[ ] Update README

Pull Request Test Coverage Report for Build 48

2 of 41 (4.88%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-6.4%) to 52.731%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

jira/sync.go
2
6
33.33%

store/mockstore.go
0
15
0.0%

store/store.go
0
20
0.0%

Files with Coverage Reduction
New Missed Lines
%

store/mockstore.go
1
0.0%

Totals

Change from base Build 46:
-6.4%

Covered Lines:
280

Relevant Lines:
531

💛  - Coveralls


Userdata String - Userdata unrecognized userdata format

What happened?
$ metal server update -i $ID -u "#cloud-config"
Error: Could not update Device: PUT https://api.equinix.com/metal/v1/devices/4a001dfc-3aa1-4cfb-b8fd-30e5448e416e?include=facility: 422 Userdata unrecognized userdata format

I am trying to figure out how to pass the "string" to userdata. I need to pass in the external ip of the host into the userdata.
How can we reproduce it?
$ metal server update -i $ID -u "#cloud-config"

CLI version 0.12.0

The userdata for #cloud-config or any shebang lines must include a newline.

Is there an example I can follow?

So I pulled the userdata from an existing server and tried to push it back in and it failed.
clempro:clemenko Desktop ( <IP_ADDRESS>:6443 ) $ ID=17df8ec8-9202-4344-934b-0bc63eda14c4

clempro:clemenko Desktop ( <IP_ADDRESS>:6443 ) $ metal server get -o json -i $ID | jq '.userdata'
"#cloud-config\n\nscheme_version: 1\ntoken: ilikechicken\nos:\n  ssh_authorized_keys:\n  - ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA26evmemRbhTtjV9szD9SwcFW9VOD38jDuJmyYYdqoqIltDkpUqDa/V1jxLSyrizhOHrlJtUOj790cxrvInaBNP7nHIO+GwC9VH8wFi4KG/TFj3K8SfNZ24QoUY12rLiHR6hRxcT4aUGnqFHGv2WTqsW2sxz03z+W1qeMqWYJOUfkqKKs2jiz42U+0Kp9BxsFBlai/WAXrQsYC8CcpQSRKdggOMQf04CqqhXzt5Q4Cmago+Fr7HcvEnPDAaNcVtfS5DYLERcX2OVgWT3RBWhDIjD8vYCMBBCy2QUrc4ZhKZfkF9aemjnKLfLcbdpMfb+r7NwJsVQSPKcjYAJOckE8RQ==<EMAIL_ADDRESS>password: Pa22word\n  ntp_servers:\n  - 0.suse.pool.ntp.org\n  - 1.suse.pool.ntp.org\ninstall:\n  mode: create\n  device: /dev/sda\n  iso_url: https://equinixphilip.s3.amazonaws.com/harvester-v1.1.1-amd64.iso\n  tty: ttyS1,115200n8\n  vip: <server_public_ip>\n  vip_mode: static"

clempro:clemenko Desktop ( <IP_ADDRESS>:6443 ) $ metal server create -P c3.small.x86 -m ny -H test -O rocky_9 -u "#cloud-config\n\nscheme_version: 1\ntoken: ilikechicken\nos:\n  ssh_authorized_keys:\n  - ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA26evmemRbhTtjV9szD9SwcFW9VOD38jDuJmyYYdqoqIltDkpUqDa/V1jxLSyrizhOHrlJtUOj790cxrvInaBNP7nHIO+GwC9VH8wFi4KG/TFj3K8SfNZ24QoUY12rLiHR6hRxcT4aUGnqFHGv2WTqsW2sxz03z+W1qeMqWYJOUfkqKKs2jiz42U+0Kp9BxsFBlai/WAXrQsYC8CcpQSRKdggOMQf04CqqhXzt5Q4Cmago+Fr7HcvEnPDAaNcVtfS5DYLERcX2OVgWT3RBWhDIjD8vYCMBBCy2QUrc4ZhKZfkF9aemjnKLfLcbdpMfb+r7NwJsVQSPKcjYAJOckE8RQ==<EMAIL_ADDRESS>password: Pa22word\n  ntp_servers:\n  - 0.suse.pool.ntp.org\n  - 1.suse.pool.ntp.org\ninstall:\n  mode: create\n  device: /dev/sda\n  iso_url: https://equinixphilip.s3.amazonaws.com/harvester-v1.1.1-amd64.iso\n  tty: ttyS1,115200n8\n  vip: <server_public_ip>\n  vip_mode: static"
Error: Could not create Device: POST https://api.equinix.com/metal/v1/projects/1acc31b0-760a-47b9-abac-0f1d381137a5/devices: 422 Userdata unrecognized userdata format

Is there anyway to pass a "string" to
We need a working example for this.

I experimented a bit and found that passing a string to userdata works with a literal newline, but not with an escape sequence:
# This command with escape sequence fails
% metal device update -i <some_device_id> -u "#cloud-config\n"
Error: Could not update Device: PUT https://api.equinix.com/metal/v1/devices/<some_device_id>?include=facility: 422 Userdata unrecognized userdata format
# This command with literal newline succeeds
% metal device update -i <some_device_id> -u "#cloud-config
"
+--------------------------------------+-----------------+------------------+--------+
|                  ID                  |    HOSTNAME     |        OS        | STATE  |
+--------------------------------------+-----------------+------------------+--------+
| <some_device_id>                     | t3-small-x86-01 | Ubuntu 22.04 LTS | active |
+--------------------------------------+-----------------+------------------+--------+

This behavior may be coming from packngo: https://github.com/packethost/packngo/issues/161#issuecomment-557205101

Glad you see the problem. At this point it is not reasonable to pass full carrier returns to the command. Frankly the API supports it.

API for the win until this can be fixed.

The shell is interpolating the \n and it arrives as \\n in metal-cli.  To avoid this, either:

enter the actual newline
PACKNGO_DEBUG=1 metal device update -i $ID -u "$(echo -e "#cloud-config\ntest: true\n")"
send the literal \n
PACKNGO_DEBUG=1 metal device update -i $ID -u '#cloud-config'$'\n''test: true'

I found a good explanation here: https://stackoverflow.com/questions/16904064/end-of-line-new-line-escapes-in-bash

Can you give me a working example?

The examples above should work (format-wise, that cloud-config would be ignored).  You can also format the userdata like this:
metal device create -u $'#!/bin/sh\necho hello world\n'


Bug: 'start' value (sometimes) broken in pagination

First off, thanks for the this cool demo/example! :-)
I came across the following bug (steps to reproduce):

Create user: python create_fake_users.py 10000. (Better: use attached database file. ;-) GitHub does not support uploading sqlite files, that's why its zipped.)
Search for "David" and directly go to the last page (press the "32" button in the lower right).
Quickly search for "Anna" now. Seems like doing this "quickly" isn't even really necessary.
The result page will contain no results (empty table) although there are results and Gridjs confirms this by summarizing "Showing 1 to 10 of 157 results". See the following screenshot.

Adding the debug code (to the data() function):
    if start != -1 and length != -1:
        print(f"Offsetting: {start}, {length}")
        query = query.offset(start).limit(length)

reveals that the start value is still containing the previous start value (Offsetting: 310, 10) of the last page when showing previous search results (for "David", in this case). To easier reproduce it, I've attached by generated SQLite database file.
Can you fix this or explain how it can be fixed?
Thank you so much!

I honestly do not think this is a bug, but in any case, this is a behavior of grid.js, so if this is a bug, it is not a bug in this project, which just demonstrates how to integrate grid.js with Flask.
In any case, you are on page 32, and you change the search parameters such that the new search results have less than 32 pages. The table is empty because you are still on page 32, which is past the end of the new result set. If you click on any of the pages shown in the bottom right you will go to the correct page for the new search.

Thanks for you quick response.
I agree with your explanation of why the table is (considered) empty.
But how can this be "the behavior of grid.js" if you provide wrong parameters in the python code to the pagination?
Anyway, do think this is fixable from Python? Testing whether the start is "out-of-scope" seems like a bad idea. I would say, the current page needs to be reset when a new search term is entered. What do your think?

Alight, guess I fixed it that way (testing whether the search string has changed). Thanks anyay!

But how can this be "the behavior of grid.js" if you provide wrong parameters in the python code to the pagination?

Simple. Try the simple_table.py example, which downloads the entire list of people to the client and then does the pagination entirely there.
You may be able to detect this in the server as you indicated, but I'm not sure that will produce a state difference between the server (which is now maybe on page 1) and the client (which still things it's on page 32).


[deploy] Improve bundle zip file name to include project name

Jreleaser creates a bundle zip file for maven central named as namespace + version + "-bundle.zip". It would be nice to include the project name as well.
Without the project name, it is hard to see which archive belongs to which project in sonatype deployments overview
The fix should add  "-" + context.getModel().getProject().getResolvedName() + in MavenCentralMavenDeployer.java, I think

🎉 This issue has been resolved in v1.13.0 (Release Notes)


Add application tests to GitHub CI

Restore the test(s) we did in Jenkins.

Added Changa (#2892). Was planning to add NAMD as well, but getting compilation errors (LB related?):
g++ -m64 -std=c++0x -I/home/mdiener/Work/charm/netlrts-linux-x86_64/include -DCMK_OPTIMIZE=1 -Isrc -Iinc    -Iplugins/include -Icolvars/src -DSTATIC_PLUGIN -I/Projects/namd2/tcl/tcl8.5.9-linux-x86_64-threaded/include -DNAMD_TCL  -I/Projects/namd2/fftw/linux-x86_64/include -DNAMD_FFTW     -DNAMD_VERSION=\"3.0alpha\" -DNAMD_PLATFORM=\"Linux-x86_64-netlrts\"  -DREMOVE_PROXYRESULTMSG_EXTRACOPY -DNODEAWARE_PROXY_SPANNINGTREE -DUSE_NODEPATCHMGR -DBONDED_CUDA -DUSE_HOMETUPLES    -DUSE_CKLOOP=1 -O3 -fexpensive-optimizations -ffast-math  -o obj/mainfunc.o -c src/mainfunc.C
In file included from src/BroadcastObject.h:18,
                 from src/Broadcasts.h:12,
                 from src/mainfunc.C:12:
src/LdbCoordinator.h:43:9: error: ‘LDObjid’ does not name a type; did you mean ‘LDOMid’?
   43 | typedef LDObjid LdbId;
      |         ^~~~~~~
      |         LDOMid

@minitu @rbuch Is this a known issue?

Added Changa (#2892). Was planning to add NAMD as well, but getting compilation errors (LB related?):
g++ -m64 -std=c++0x -I/home/mdiener/Work/charm/netlrts-linux-x86_64/include -DCMK_OPTIMIZE=1 -Isrc -Iinc    -Iplugins/include -Icolvars/src -DSTATIC_PLUGIN -I/Projects/namd2/tcl/tcl8.5.9-linux-x86_64-threaded/include -DNAMD_TCL  -I/Projects/namd2/fftw/linux-x86_64/include -DNAMD_FFTW     -DNAMD_VERSION=\"3.0alpha\" -DNAMD_PLATFORM=\"Linux-x86_64-netlrts\"  -DREMOVE_PROXYRESULTMSG_EXTRACOPY -DNODEAWARE_PROXY_SPANNINGTREE -DUSE_NODEPATCHMGR -DBONDED_CUDA -DUSE_HOMETUPLES    -DUSE_CKLOOP=1 -O3 -fexpensive-optimizations -ffast-math  -o obj/mainfunc.o -c src/mainfunc.C
In file included from src/BroadcastObject.h:18,
                 from src/Broadcasts.h:12,
                 from src/mainfunc.C:12:
src/LdbCoordinator.h:43:9: error: ‘LDObjid’ does not name a type; did you mean ‘LDOMid’?
   43 | typedef LDObjid LdbId;
      |         ^~~~~~~
      |         LDOMid

@minitu @rbuch Is this a known issue?

Yeah, I ran into this last week, it's nothing to do with the new LB stuff, it's because the CMake build doesn't do the same configure checks as the old build. In the old build, the variable that controls this (CMK_LBID_64BIT) is set in configure.ac and the variable is then defined in conv-autoconfig.h. Is there a place in the CMake build where this should go instead?

Yeah, I ran into this last week, it's nothing to do with the new LB stuff, it's because the CMake build doesn't do the same configure checks as the old build. In the old build, the variable that controls this (CMK_LBID_64BIT) is set in configure.ac and the variable is then defined in conv-autoconfig.h. Is there a place in the CMake build where this should go instead?

Right, #2893 should fix this.

NAMD and ChaNGa have been added to Github CI. Closing this bug, but feel free to reopen in case we want to add additional tests.


Crash traces

I got a crash dump:

and then when I clicked "You can find SyncTrayzor's log file here" I got another one:
Version: <IP_ADDRESS>; Variant: Installed; Arch: Amd64
Path: C:\Program Files\SyncTrayzor\SyncTrayzor.exe
System.ArgumentNullException: Value cannot be null.
Parameter name: path1
   at System.IO.Path.Combine(String path1, String path2)
   at SyncTrayzor.Pages.UnhandledExceptionViewModel.OpenLogFilePath() in C:\projects\synctrayzor\src\SyncTrayzor\Pages\UnhandledExceptionViewModel.cs:line 54
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Stylet.Xaml.ActionBase.InvokeTargetMethod(Object[] parameters) in c:\projects\stylet\Stylet\Xaml\ActionBase.cs:line 201
   at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
   at System.Windows.Documents.Hyperlink.OnClick()
   at System.Windows.Documents.Hyperlink.DoUserInitiatedNavigation(Object sender)
   at System.Windows.Documents.Hyperlink.OnMouseLeftButtonUp(Object sender, MouseButtonEventArgs e)
   at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
   at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
   at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at System.Windows.ContentElement.RaiseTrustedEvent(RoutedEventArgs args)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
   at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
   at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Clicking "Close" in the second window caused a system crash, which is why I was only able to get a screenshot of the first window.

Thanks for reporting! I'll take a look at this next week

Turns out this is the same as #354, so closing in favour of that one.


Add conda environment file

Resolve #19

@joannabrozek - These files should probably be under each of the directories?


Markdown doc visual improvements

Hyperlink support throughout, for example [Node] this from xml doc should be converted to markdown text hyperlinked to Node class
Same [method_ready] of XML should correspond to hyperlink to ready method of that class doc
If scrolled down in a doc and say we click on a hyperlink to other doc then it will still be scrolled down. Vertical scrolling must reset for every time a new doc is opened.
Spacing improvements, right now everything is very condensed compared to original godot doc

Addressed all the issues, except scroll problem. Created an issue regarding that in vs code repository https://github.com/microsoft/vscode/issues/78465


added follow us section

@MitulSonagara
I have added follow us section successfully
kindly check it out

@MitulSonagara could you please review and merge it

@AswaniBolisetti
Please resolve this error

@MitulSonagara
could you please more details like when did you get this error

@AswaniBolisetti
When i check the deployment of the website...

@MitulSonagara
kindly close this issue, I found my mistake, I'll raise this issue again and create another pull request by considering all these issues

@AswaniBolisetti
Okay no problem...


Consolidate databases into a single one and introduce account index

This work is based on PR #160 and it's still work-in-progress.
A few identified issues that need to be addressed:

[ ] The network protocol is being affected, especially block/transaction codec;
[ ] Validation of block certificate (committee signatures) for unknown account index;
[ ] More tests are required.

This was supposed to be a PR...


Fix C++ compilation

With ESP-IDF 5.2, some headers do not tolerate being included from an extern "C" block. To avoid any similar issue, all includes are moved outside of these blocks, thus fixing compilation of C++ code including our headers.
These changes are made under both the "Apache 2.0" and the "GNU Lesser General
Public License 2.1 or later" license terms (dual license).
SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later

Makes sense, let's target release-0.6

Makes sense, let's target release-0.6

ets headers also need the same change, I'll create another PR for it on main branch.


Marketo Cloud Configuration root missing

I am trying to integrate Marketo forms with AEM but following the steps from [1] when I get to step 2 I don't have any configuration there, the page is blank and I can't move forward.

I managed to create our own configuration as a workaround but I think that the path where the cloud configuration is created it's not in the site’s Conf root so when I add an embed component and select Marketo, instead of getting a list with all the available forms, it displays "Unable to load forms from Marketo".

I contacted also the Adobe support which directed me here, and they suggested that I should be able to select on the page properties the cloud configuration for the organisation, which is also not available. Even though I don't see this step in your documentation.

How can this be fixed?
[1] https://adobe-consulting-services.github.io/acs-aem-commons/features/marketo-form/index.html

Hi @andreeastoiuu sorry for the delay on this one. Could you take a look at this branch: https://github.com/Adobe-Consulting-Services/acs-aem-commons/tree/defect/marketo-form/cloud-config-root-missing
OR just remove the exclude property from the resource:
/apps/acs-commons/content/cloudservice/create/target/field/datasource

Hi @klcodanr, removing the exclude property from /apps/acs-commons/content/cloudservice/create/target/field/datasource worked for me. But how can I commit this code for higher environments as this path is getting installed via build.

@davidjgonzalez, we are using an older version of the Adobe ACS commons dependency 5.0.1. I updated the all/pom.xml file with the newer versions and completed a new AEM CS pipeline. Unfortunately. I still see the older version of the ACS Zip file.
When updating a version other than the all/pom.xml version updates, are there additional steps to be performed for AEM CS?

@klcodanr I am encountering the same issue with v5.3.4 on a new site with MSM enabled.
This is showing in the logs:
POST /apps/acs-commons/content/cloudservice/console/_jcr_content/content/items/cloudconfiglist HTTP/1.1] com.adobe.granite.metrics.knownerrors.impl.ErrorLoggingComponentFilter Exception in component: category=CUSTOMER_CODE, resourceType=acs-commons/components/utilities/cloudconfig/cloudconfiglist, exceptionType=java.io.IOException, errorId=CUSTOMER, resource=/apps/acs-commons/content/cloudservice/console/jcr:content/content/items/cloudconfiglist, exceptionMessage = Parameter template must not be blank

Note: I am able to get to the Marketo cloud configs if I use a fresh author instance and fresh site built from the archetype (and a title/name without any spaces). Otherwise, existing sites have the issue reported here.
What could be causing this?


Force Recurring Events by Priority

Based on Priority,  Yearly, Monthly , Weekly, Daily

The following three events have the highest priority;
New Year’s Day, CLOSED ALL DAY
Thanksgiving Day, CLOSED AT 2:00 pm
Christmas Day, CLOSED ALL DAY
Master Record 48485 has two conflicts on the calendar; T-giving & X-mas. [AGC Range Badge Processing, M-F, all year long]

What about non recurring events?  I'm trying to think of a priority order.

Same level will not overwrite each other,
Lower number has priority,

Yearly,
Monthly,
Weekly,
Daily,
Non recurring.

I think I disagree. Theoretically, if we could get the database corrected for all existing recurring events, then an existing non-recurring event would have a higher priority against any new recurring event trying to be created. If we took 2020 as the standard for recurring events, then those events would have to deal with the priority you defined. But, new recurring events would only be created if they did not cause a conflict with existing non-recurring and recurring events.
Corrected list;

Holiday Closing
Yearly,
Monthly
Weekly
Daily

You know there is no recurring time frame of Holiday right?   You left off Non-recurring events priority?  Maybe a new field that means "No Override"?


Massive pr

Lots of files being edited here. This is a long-lived branch with lots of different stuff. Though most of it is removal of obsolete files and fixing specs.
Ready:

Fixed most of the specs so that they are building and passing
Removed some obsolete specs
Marked some specs as [Ignored] as they need some more effort
Removes *.Management and TimeSeries projects
Dolittle.Applications => Dolittle.ApplicationModel
Use new Contracts. Without the 'external alias' thing
Remove 'Cause'
Remove 'RetryProcessingState' from IEventProcessor
Remove 'ProcessorFailureType'
Add new Process-method to IEventProcessor with 'failureReason' and 'retryCount' that is used only for stream processors that are catching up
Move PublicFilter to Events.Processing
Separate StreamProcessor registration from the starting of a StreamProcessor. The one that registers the StreamProcessor is responsible for the lifecycle of it. Starting it and Disposing it when it is supposed to be disposed.
The EventHandlers and Filters services will attempt to register all StreamProcessors before starting them. If the registration of a StreamProcessor is failed for any of the tenants then the service will write a failed response and close the connection
Removed FilterRegistry as it is not needed. There is no point in keeping an in memory registry of the filter definitions. The filter processors are StreamProcessors which are registered.
Removed Bindings for 'ICanValidateFilter'. The filter validators are discovered and registered in the IFilterValidators
Create 'FilterValidationResult' which is returned by the FilterValidator.Validate
Get rid of 'ICanRemovePersistedFilterDefinition'
Add 'IFilterDefinitionRepository' which can persist and retrieve 'IPersistableFilter' filters
'StreamProcessor's Unregister themselves from the 'StreamProcessors' registry when cancellation is requested. It is also defined as an IDisposable now. Unregistering a stream processor multiple times should not throw any exception or do anything unexpected.
'StreamProcessors' returns a 'StreamProcessorRegistrationResult' that, among other things, says whether the stream processor has already been registered or not. So the caller can for itself decide what to do.
Have a general filter definition repository in Mongo event store
Remove IDisposable interface from IEventStore
'CommittedEvent's has ExecutionContext as a property
Events.Store.MongoDB ExecutionContext: Added Version, Environment.
Adhere to changes in Fundamentals

Half-way:

Start on using the new formated log functions
Start on formalizing FailureId's for known errors on services.
Maybe find some common functionality that can be shared between the *Service classes.
When a 'StreamProcessor' starts, the task is stored and returned en future calls to Start(). The method Start does not necessarily reflect this. We need to decide what we want the semantics to be. Either consecutive calls on Start throws an exception or it needs to do something else, for example returning the original task as I do already.
Removed unused Exceptions
Removed most of the code in Heads. More of it may also be obsolete

Not ready:

EventHorizonEvent's ExecutionContext is not set right. The Tenant is set to be the consumer tenant, it should be the producer tenant.
Need to implement the PublicFilterValidator validate function
The IFilter, IEventHandlers stuff may perhaps not be necessary as they don't really do that much. They only register the stream processors and returns a result.
The filter validators are still not "correct"
Use BsonClassMaps and Serializers in Events.Store.MongoDB

┆Issue is synchronized with this Asana task

Pulling this abomination in, in agreement with @jakhog


Grid doesnt render - shows large blue arrow instead

I'm trying to use React DataGrid, but it doesnt render correctly... Why?
Here's what I see when I run my simple app:

Turns out this was simply me not fully reading the Readme.md. It says you need to include the css file, like so:
require('react-datagrid/index.css');

which I did. But that required that I install the npm module "css-loader", which I did using the following:
npm install css-loader --save-dev
npm install file-loader --save-dev
npm install url-loader --save-dev
npm install style-loader --save-dev

Then it worked!

This is with webpack of course