Companion Conversations Still Eventually Break

Related to #1159. Two conversations between Barrett and Sarah are broken in a way that either causes the scene between them to never start, or causes the quest to never end after the conversation happens. This will end up breaking all other conversations, once again.

Details
SCEN records 002E892A and 002BAAE1 lack these flags: Begin on Quest Start, Stop on Quest End
Preventing this bug from happening is as easy as adding these flags. Fixing it retroactively is another question. I'm open to any suggestions on how this could be done best.
Game Version
1.14.70
Language
English (EN)
New Game
Yes
Reproduction Steps
Get Barrett and Sarah together in one room for long enough. Eventually they will stop talking to each other, and the awkward tension will be so severe that nobody else in Constellation will ever break the silence.

:D love the repro steps part


The parameter names are not updated to meet the new parameter names in Karpenter 0.23.0

The parameter names are not updated to meet the new parameter names in Karpenter 0.23.0 which causes an issue with the parameters not propagating properly to the Karpenter helm chart because addons still uses the old parameter names.
https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/a9181ae2ddfafc03af70b1eab667eac7dd17bf1a/modules/kubernetes-addons/karpenter/locals.tf#L46-L52

Hi nalshamaajc!
As we spoke, in order enable the configuration of the parameters in the first image:

You'll need to add another configuration block, together with the one that you highlighted:
https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/a9181ae2ddfafc03af70b1eab667eac7dd17bf1a/modules/kubernetes-addons/karpenter/locals.tf#L46-L52
  argocd_gitops_config = {
    enable                 = true
    serviceAccount         = {
      name   = local.service_account
      create = false
    }
    settings = {
      aws = {
        clusterName            = var.addon_context.eks_cluster_id
        clusterEndpoint        = var.addon_context.aws_eks_cluster_endpoint
        defaultInstanceProfile = var.node_iam_instance_profile
        interruptionQueueName  = try(data.aws_arn.queue[0].resource, "")
      }
    }
  }

Thanks @rodrigobersa!
We also needed to pass the defaultInstanceProfile through the TF outputs which made it work eventually.

I reopened the issue since it is still cause problems when pulling from upstream the values are still different from the ones in the helm chart
https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/v4.27.0/modules/kubernetes-addons/karpenter/locals.tf#L46-L52

@nalshamaajc does https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/pull/115 not fix this issue?  Maybe I'm not understanding which parameter is incorrect.
It looks like where this is defined is correct:
https://github.com/aws-ia/terraform-aws-eks-blueprints-addons/pull/115/files#diff-dc46acf24afd63ef8c556b77c126ccc6e578bc87e3aa09a931f33d9bf2532fbbR1946
https://github.com/aws/karpenter/tree/main/charts/karpenter#installing-the-chart
settings.aws.defaultInstanceProfile

@nalshamaajc would you mind providing a reproduction so we can take a look at the issue you are facing? thanks!

closing this for now - please feel free to respond if there is additional details and we can take a look


Update for latest node version

Fixes #1
Needed to change the formatting of elm files to conform to the new elm-format version (0.8) since the older version of elm-format does not work with node 12.

There is not much change here actually. Just the change to package.json. All other changes are programmatic yarn upgrade and elm-format.


Rename: inflorescence branch meristem (PO:0009105) >> higher order inflorescence axis apical meristem

Based on the revisions to 'higher order inflorescence axis' (was: inflorescence branch) (PO:0009081), we will need to revise this term.
See notes on
March 14th, 2017 Planteome Ontology Meeting
inflorescence branch meristem (PO:0009105)
Current def: An inflorescence meristem (PO:0009108) that gives rise to an inflorescence branch (PO:0009081).
See also history of this term on #437

inflorescence axillary meristem  (PO:0009105)
Renaming of: inflorescence branch meristem (PO:0009105)
Current def'n: An inflorescence meristem (PO:0009108) that gives rise to an inflorescence branch (PO:0009081).
Revised def’n: An inflorescence meristem (PO:0009108) that gives rise to a higher order inflorescence axis (PO:0009081).
Current comment: None.
Revised comment: No revisions.
Current synonyms: meristema lateral de la inflorescencia (Spanish, exact), 花序側部（側方）分裂組織 (Japanese, exact)
Revised synonyms: meristema lateral de la inflorescencia (Spanish, exact), 花序側部（側方）分裂組織 (Japanese, related)

Completed, closing


Missing two icons of cards

@harikrishnan-annappilly
konnichiwa bug solver,
Help me find the issue in #6 My Services section.
In the bootstrap card two icons were not showing smh.
pull the code from main  or deepak branch and do something ffs.

nvm, fixed myself nbd


Installing clarification

Please can you clarify that you need Python 2 when installing Anaconda in your instructions for Linux users?
As I only half understand python I had a few issues following the instructions at (https://diamondlightsource.github.io/SuRVoS/docs/installation/).
The link to Anaconda offers two version of Python (currently 3.4 and 2.7).  It wasn't clear from the instructions on your site that you'd coded in Python 2.  Seeing as how the bigger number is better in my mind I spent quite a lot of time trying to force your code to work with python 3.4.  It was only after I found a few print errors (expecting parentheses) that I realised that the Python version affected the syntax of quite a few commands.
I think I have it working now (don't mention the problems I had getting Cuda running on Centos).
I'd have emailed this as its not really a coding error, but there are no links in your instructions (unless<EMAIL_ADDRESS>is a real person https://diamondlightsource.github.io/SuRVoS/about/)
Hope this is helpful.
Toby S

Hi @tstarborg,
Thanks for the comments. It is indeed python 2.7 the one used in SuRVoS (although it will be compatible with both in the future). Sorry for missing that comment in the installation instructions. It is already fixed, along with an email for the contact page.
Thank you for your interest,
Imanol


ImportError: No module named flask_restful

threat_note/libs/API.py wants to import "from flask_restful import Api"
I'll look into making sure my pip install of requirements.txt went well but I did not see an update to that here.

will need to follow requirements-dev.txt.  Going to close for now.

@eopdyke Yeah... after a lot of consideration I'm just going to merge the two. People can survive a few extra vendored libraries.


Add Support for Enums in Config Beans.

For details on the problem description, please refer to issue#397.

Hi @karthicks,
Thank you for your contribution! We really value the time you've taken to put this together.
Before we proceed with reviewing this pull request, please sign the Typesafe Contributors License Agreement:
http://www.lightbend.com/contribute/cla

Thanks, this seems like a very useful feature!

Thanks Havoc for your comments! Like you suggested, I pushed the Enum-parsing logic inside the Config interface, and added checks around invalid values.

@viktorklang  @2m any comments on this one?

Need to resolve conflicts here; also you could squash the "just to restart the build" commit maybe so it isn't sitting around in commit history forever. :-) You'd have to push -f. I think I can manually restart the build if required in the future.
I'll merge this once conflicts are resolved, if nobody has more comments by then.

Sorry about that. I resolved the conflict, and, squashed all the commits into one.

Cool, thanks! Appreciate the contributions.


Custom Partner Invitation Message is not working.  Fix it

Summary
The custom partner invitation message is not working.  Fix it.
Why
Having the system match reasonable bank expectations
Details
Seeing the problem
Set up the message:
sign in as<EMAIL_ADDRESS>Click "My Organization" in the left hand menu,  then "Edit" in that page.
Find the field "Custom Partner Invitation Message".  Put some text in there that you'll recognizae.   Save.
Then,
Click "Partner Agencies",  "All Partners".  Find a partner with "Resend Invite".  Click "Resend Invite".  Click "OK" in the confirmation window.
Wait a couple of minutes for the email to appear in your browser.
The text you entered should appear after "You've been invited to become a partner with Pawnee Diaper Bank!".
Note:
It's possible that this has been broken since the databases were combined.
Criteria for completion

[ ] The text appears as described above
[ ] Tests to support that.

Hey, I woud like to take this


⚠ Bofrost.be has degraded performance

In c520a81, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 978 ms

Resolved: Bofrost.be performance has improved in ad09098 after 6 minutes.


rdpwrap 1682,termsrv 1741?

Please help, not wrk rdp with update july 2022, in screen is 1682 version, but in folder c: windows termsrv.dll - 1741.
ok, i put rdpwrap.ini in folder program files, when 1741 correct.
Users come in, all ok. But in programm rdpwrap is 1682 full supported! Where i do correct a mistake?

all work! but this mistake is not right...

and i restart termsrv service too)))) whats happened?

Please, disable Autoupdate.bat (if you using this script). Them execute sfc /scannow and reboot.
Please, send RDPConf screenshot after this.

i do it, but not happened

1741 is correct version (issue https://github.com/stascorp/rdpwrap/issues/1881)
If RDPConf shows a version other than the one in System32, then something is wrong with your system.
If you want to sort out your problem, it's better to write to Telegram chat https://t.me/rdpwrap (there's more chance of getting an answer).
Since most likely the problem is not with the RDP Wrapper, but with your system, this issue will be closed.


[hk] Disallow parameter creation in apply when params is None

Previously, this would create new parameters:
rng = jax.random.PRNGKey(0)
module = hk.transform(lambda x: hk.Linear(10)(x), apply_rng=True)
print(module.apply(None, rng, jnp.ones((3, 2))))
Because internally it would alias to the init path.
This PR disallows this behavior for both params and state.

The types on the apply functions don't indicate that Optional[T] are accepted, should we update that too?

Both done.

This got merged, but weird stuff happened and GitHub doesn't recognize the copybara merge.
Closing.


[Feature Request]: Dockerize the Application

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I want to add Dockerfile to the root of the project. A Dockerfile is a text file of instructions which are used to automate installation and configuration of a Docker image .
Adding Dockerfile to the root of the project will encourage image formation of the application using Docker and running the image in one's local environment without installing the dependencies.
Use Case
Dockerfile leads to easy development and deployment process.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC-EXT contributor
[X] I'm a HACKTOBERFEST contributor
[X] I have starred the repository

@Sami3160 For now, are we required to Dockerize this application?

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I want to add Dockerfile to the root of the project. A Dockerfile is a text file of instructions which are used to automate installation and configuration of a Docker image .
Adding Dockerfile to the root of the project will encourage image formation of the application using Docker and running the image in one's local environment without installing the dependencies.
Use Case
Dockerfile leads to easy development and deployment process.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC-EXT contributor
[X] I'm a HACKTOBERFEST contributor
[X] I have starred the repository

Tell in details how adding docker will affect our project, how we need to run the project and how will be the installation process...
And how we maintain the docker container, also explain how it is scalable for our project
I'm really interested in integrating docker, but don't know how it would affect our project,

hey @Sami3160  and @jeevan10017  adding docker to a project is never early as it has always that thing to make the development process easier, It keeps away the dependencies that one needs to manually install to their system to get started with the project , instead it takes care all of that , it needs a single command to make a image of the application inside the docker container and another command will run the application on the specified ports.
Docker offers consistent, lightweight containers that simplify app deployment across environments, ensuring portability and isolation. It also enables easy scaling by allowing rapid container replication and resource allocation based on demand.

hey @Sami3160  and @jeevan10017  adding docker to a project is never early as it has always that thing to make the development process easier, It keeps away the dependencies that one needs to manually install to their system to get started with the project , instead it takes care all of that , it needs a single command to make a image of the application inside the docker container and another command will run the application on the specified ports.
Docker offers consistent, lightweight containers that simplify app deployment across environments, ensuring portability and isolation. It also enables easy scaling by allowing rapid container replication and resource allocation based on demand.

Okay you can use docker but you need to update readme.md,
Have some detailed readme about how to run container and create images add dependency and every thing such that even a beginner can run our app and contribute to it without any problem

Yeah sure I will update the Readme.md in the way that is understandable by everyone.


Save token when app is running in background

Hi, I have some questions.
If device token is refreshed when app is running in background, how can I save this new token properly?

I believe this is solved using the onTokenRefresh method


Use of deprecated xlink:href in examples

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
For example, the example of Footers use <svg class="bi" width="30" height="24"><use xlink:href="#bootstrap"/></svg> to display the Bootstrap Logo. xlink:type is deprecated and should not be used acording to Mozilla.
Reduced test cases
https://getbootstrap.com/docs/5.1/examples/footers/
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
v5.1.0

Looks like Safari 12.2 added support for href, but we support Safari 12.0 and up so I don't think we can switch yet. https://caniuse.com/mdn-svg_elements_use_href
Tagging for v6.


[incubator/aws-alb-ingress-controller] bump aws alb ingress controller

Signed-off-by: Rauny Brandão<EMAIL_ADDRESS>Special notes for your reviewer:
https://github.com/kubernetes-sigs/aws-alb-ingress-controller/releases/tag/v1.1.3
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @bigkraig

@M00nF1sh and @bigkraig

/assign @M00nF1sh


Kiwix and ZIM managment

Currently we have to use the --library parameter in the start-up script in order to read different ZIM file.
--library call a library.xml file which contain a list of ZIM file in an XML format. This file has to be built with a binary that does not exist for ARM proc. This is not flexible at all and we have to find a new way of using Kiwix and ZIM file.
For instance, we can call directly a ZIM file with kiwix-serve but in this case we have as much kiwix-server proc as we call ZIM file which is not really optimised

All the stuff to build the library.xml file is here http://download.kiwix.org/bin/kiwix-server-arm.tar.bz2.


Reply to a conversation thread in teams using Teams bot

I have a bot that is created by using Microsoft botframework sdk, I'm trying to find a way to reply to a conversation thread in a teams Channel conversation without being prompted first by a user. So for example given a certain condition (eg. triggered by some event such as time of day, a pull request, etc.) it posts a message in a channel to a particular thread. I have read the documentation on the proactive messaging in teams. I gather that in order to send a message to a teams channel, the bot needs to know the "conversationId" of the user. This information is stored in the conversationreference object, and it gets this from the current conversation. However, in my case I don't have a 'current conservation', because I don't want to just respond to a user, I want to post a reply to a thread proactively. How can I achieve this ?
Also, I followed a document where the bot can read any messages without being mentioned using @ by following. So I thought we will be getting the user's conversation id in the context object whenever there is a new message in the channel RSC permissions, but it doesn't seems to be working out for me, I'm not sure if I'm missing out on anything

Same issue is being tracked here https://stackoverflow.com/questions/78618577/reply-to-a-conversation-thread-in-teams-using-teams-bot. Please follow above thread for further updates. Thank you.

@Meghana-MSFT  I'm the author for the same thread you shared above... I didn't get any response yet..


metadata version 2016-07-29

Lowercase service/stack/container name only in the 2016-07-29/latest versions

Also dropped hostId in 2016-07-29 HostMetadata

https://github.com/rancher/rancher/issues/6226


[Spark-12260][wip][Streaming]Graceful Shutdown with In-Memory State

View Detail Design DOC
Motivation:
Users often stop and restart their streaming jobs for tasks such as maintenance, software upgrades or even application logic updates. When a job re-starts it should pick up where it left off i.e. any state information that existed when the job stopped should be used as the initial state when the job restarts.
Proposal:
I  create an abstract class called DumpableDStream which extends DStream, and make stateful DStreams entend it, for instance, MapWithStateDStream, StateDStream. So that these stateful DSteams will have common ancestor.
DumpFormat is also an abstract class, looks like following:
abstract class DSteamDumpFormat[K, S] extends Serializable{
     val identity : String
     private[streaming] def dump(rdd : RDD[(K, S)], path: String): Unit
     def load(sc: SparkContext, path: String): RDD[(K, S)]
}

User can customize his own DumpFormat by extending this abstract class. There are three interfaces in it. “identity” is used to recognize dumped RDD during loading it back, it have to be provided for every DumpableDStream instance. “dump” method is designed to dump inputted DRR to given path, this method will be called by DumpableDStream.dump method. “load” method is designed to load RDD back from given path, user need to call it expilicatly.
When an application performs graceful shutdown via invoking StreamingContext.stop(…), it invoke a method ssc.graph.dump that will traverse current DStreamGraph to find all DumpableDStream and perform DumpableDStream.dump()
Usage:
From user perspective, first he/she need to create a new DumpFormat instance:
val df = new CheckpointDumpFormat[String, Int]("WordCount")

Then set this DumpFormat instance into stateDStream reference”. That’s all.
	val stateDstream = wordDstream.updateStateByKey[Int](newUpdateFunc,
    new HashPartitioner(ssc.sparkContext.defaultParallelism), true, initialRDD)
  	stateDstream.setDumpFormat(df)

Once StreamingContext.stop() is invoked with stopGracefully = true, the state of WordCount will be automatically saved into HDFS and user can easily load it back when restarting the process by following code:
	val initialRDD = df.load(ssc.sc , checkpointDir+"/WordCount")

For advance usage, user can create his own DumpFormat type to specify serializer or save in-memory state into Datadase, etc.

@tdas Could you help to review this PR? As we discussed before, some users have requirements to dump in-memory states when process shutdown, at the same time, they want to recover states back during restarting. This is the initial implementation to meet such requirement. And I have marked this PR with [wip].  Let me know how you think about it. Thank you.

Test build #47499 has started for PR 10252 at commit 6e0fcfc.

Test build #47499 has finished for PR 10252 at commit 6e0fcfc.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * abstract class DSteamDumpFormat[K, S] extends Serializable\n  * class CheckpointDumpFormat[K: ClassTag, S: ClassTag](val identity: String)\n  * abstract class DumpableDStream[K: ClassTag, S: ClassTag](ssc: StreamingContext)\n

Merged build finished. Test FAILed.

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

Test build #47576 has started for PR 10252 at commit 163d362.

Test build #47576 has finished for PR 10252 at commit 163d362.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * abstract class DSteamDumpFormat[K, S] extends Serializable \n  * class CheckpointDumpFormat[K: ClassTag, S: ClassTag](val identity: String)\n  * abstract class DumpableDStream[K: ClassTag, S: ClassTag](ssc: StreamingContext)\n

Merged build finished. Test FAILed.

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

Before reviewing this further, let's return to the JIRA. I do not see that this implements something that you a) can't do with updateStateByKey or trackStateByKey, or b) that Spark should be managing anyway.

After talk with @mwws offline, we probably need to serialize the accumulator variables as well.
I personally agree with @srowen, we need to think provide better API, otherwise, app developers can implement the logic themselves.

@mwws can you close this PR?

Sorry @srowen for the confusing, I was talking about this is a partial done PR, I think @mwws will update the code change soon.

That's fine too; it needs a rebase. I'm personally skeptical this can be solved in the general case, or should be, but getting more specific about the API is probably the only way forward.

Hi, @mwws , @chenghao-intel , is there any progress on this pr?
When we use spark streaming, it will lose some stateful data when we upgrade code, i think this pr may  resolve our problem. Is there plan to continue on this pr?

@zzcclp can you please describe how do you recover from the streaming? We are actually will spit this into 2 separated ones, but still thinking what the API users want.

@chenghao-intel @mwws , sorry for my late reply.
Currently, we just record the kafka offset and accumulators to third-party storage system after per batch, and then restore  them from the window‘s earliest start time. For stateful data, we have no good way to recover by now, so it will lose some statistical data.
Next, one of our business system must ensure data integrity after software upgrade or even application logic update, so we urgently hope that spark can native support this feature.

@zzcclp we have another PR for this fixing, #11101, please check if it can fix your problem.

@mwws please close this PR


Refactor tts function

Current implement will try to return an int when it gets invalid phrase like "H1"

In the current implementation we do not raise unless the original value is not int. (Let int() do the raise if needed)
We do not support 1.5H, if the user want 1.5H the user should send 90m

Done
Updated with just making it more strict towards the input
PR description is updated

/verified

/verified

/verified

/retest sonarqube

/retest sonarqube

You need to return int(ts) here.

If we will keep the regex 'strictness' and the exception handling in the same way as before,
I'm closing since i'm not seeing added value in my changes.


What does a protoDescriptor look like for a schema with nested types?

{
"name": "frames",
"type": "RECORD",
"mode": "REPEATED",
"fields": [
{
"name": "first_processed_at",
"type": "TIMESTAMP",
}
]
}
how would a Struct column like this get described?
in the  const protoDescriptor = {};
protoDescriptor.name = 'SampleData';
protoDescriptor.field = ...

I dug into the source, seems the proto descriptors are defined in the protobuf library.
The following is how you define the descriptor. I've tested it as well and it works properly with the default stream. If you serialize a proto with this format, it should go through properly. I suppose if you need triple nested types, you can redefine nestedType and reference it using typeName in the sub-descriptor.
Hopes this helps someone. The documentation should definitely be updated to include a nested example.
const protoDescriptor = {
  name: "Record",
  field: [
    {
      name: "timestamp",
      number: 1,
      type: FieldDescriptorProto.Type.TYPE_INT64,
    },
    {
      name: "nested",
      number: 1,
      label: FieldDescriptorProto.Label.LABEL_REPEATED,
      type: FieldDescriptorProto.Type.TYPE_MESSAGE,
      typeName: "Record.Nested",
    }
  ],
  nestedType: [
    {
      name: "Nested",
      field: [
        {
          name: "type",
          number: 1,
          type: FieldDescriptorProto.Type.TYPE_STRING,
        },
        {
          name: "values",
          number: 2,
          label: FieldDescriptorProto.Label.LABEL_REPEATED,
          type: FieldDescriptorProto.Type.TYPE_INT64,
        },
      ],
    },
  ],
};

Closing this out, the repo now has more extensive samples related to nested messages.  See https://github.com/googleapis/nodejs-bigquery-storage/blob/main/samples/append_rows_proto2.js for an example.


Why is the update check cache so long? (60 days)

Hi there!
I never noticed the cache validity period, why was it set to a value of 60 days?
Wouldn't a value of 12/24 h be sufficient? Is there a restriction that doesn't allow this?
$item->expiresAfter(3600 * 60 * 24); Defined here
Can we introduce a default task like check-update?
For example, currently, if I update castor to the latest version on my workstation and send it to PR, my colleagues will encounter compatibility problems. And I'd need to notify everyone that something needed to be updated manually via message or meeting.
To solve this problem, I thought of introducing a function like min_version_check('0.10.0'); which, even before running a command, checks whether the minimum version required is installed on the workstation. And if it doesn't, we could run the check-update command
What do you think of this?

$item->expiresAfter(3600 * 60 * 24); Defined here

IMHO, there is a typo. It should have be 60 * 60 * 24 🙃

Can we introduce a default task like check-update?

We already discuss that, and We don't think this is useful. We have (almost?) never seen such check in other CLI software. Either you update it, or you get an alert when an update is available. I think people won't use it.

To solve this problem, I thought of introducing a function like min_version_check('0.10.0');

YES! We discussed that a lot of time, and this is something we want. However, we did not though about the DX.
But I like your proposal. I would instead call it guard_min_version('0.10.0')

Can we introduce a default task like check-update?

We already discuss that, and We don't think this is useful. We have (almost?) never seen such check in other CLI software. Either you update it, or you get an alert when an update is available. I think people won't use it.

To solve this problem, I thought of introducing a function like min_version_check('0.10.0');

YES! We discussed that a lot of time, and this is something we want. However, we did not though about the DX.
But I like your proposal. I would instead call it guard_min_version('0.10.0')

Ok cool! I see :) Here's a first draft if it suits https://github.com/TheoD02/castor/commit/752874b948da8dbe969c3b8d026087832527c620
For the DX, possibly the solutions that I see and that I have quoted so already in the draft :
To have an impact on all tasks:

Call this method at the top of castor.php so that it is an impact no matter what task call.
Or use the event system with the AfterApplicationInitializationEvent.

For example, if you want to scope, so that only specific tasks check this version, then :

Either check at the start of the task before doing any process.
Or once again with the Event Listener which could allow you to scoop on a regex pattern, a namespace etc... and execute only under certain conditions or all the time.

Do you have any other possibilities in mind ?

You can open the PR, it's okay for me, I'll comment there.


Add wrapper for utils package from sriov-device-plugin

This is a pre requisite to cover code in host pkg with unit tests.
cc @adrianchiris @SchSeba @zeeke

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-151 of 158 (4.43%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 24.097%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/host/manager.go
0
3
0.0%

pkg/host/internal/network/network.go
0
7
0.0%

pkg/host/internal/sriov/sriov.go
2
16
12.5%

pkg/host/internal/lib/dputils/dputils.go
0
30
0.0%

pkg/host/internal/lib/dputils/mock/mock_dputils.go
5
102
4.9%

Files with Coverage Reduction
New Missed Lines
%

pkg/host/internal/network/network.go
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
2708

Relevant Lines:
11238

💛  - Coveralls

@zeeke can we merge this one ?


DataDog agent restarting all the time

During normal operation, DataAgent is restarting itself all of the time, at regular intervales. I suspect Docker monitor to be the source of the issue, although it was working a couple of hours ago:
Getting the status from the agent.

==============
Agent (v6.0.3)
==============

  Status date: 2018-03-22 01:18:59.487465 UTC
  Pid: 5363
  Python Version: 2.7.14+
  Logs: Log Level: info

  Paths
  =====
    Config File: /etc/datadog-agent/datadog.yaml
    conf.d: /etc/datadog-agent/conf.d
    checks.d: /etc/datadog-agent/checks.d

  Clocks
  ======
    System UTC time: 2018-03-22 01:18:59.487465 UTC

  Host Info
  =========
    bootTime: 2018-03-14 18:31:25.000000 UTC
    kernelVersion: 4.15.0-1-amd64
    os: linux
    platform: debian
    platformFamily: debian
    platformVersion: buster/sid
    procs: 404
    uptime: 629254
    virtualizationRole: host
    virtualizationSystem: kvm

  Hostnames
  =========
    hostname: wasp
    socket-fqdn: wasp.radical.zone.
    socket-hostname: wasp

=========
Collector
=========

  Running Checks
  ==============
    No checks have run yet

========
JMXFetch
========

  Initialized checks
  ==================
    no checks

  Failed checks
  =============
    no checks

=========
Forwarder
=========

  RetryQueueSize: 0
  Success: 0

==========
Logs Agent
==========

  Logs Agent is not running

=========
DogStatsD
=========

  Event: 1

Mar 22 01:19:30 wasp trace-agent[5846]: 2018-03-22 01:19:30 INFO (main.go:108) - pid '5846' written to pid file '/opt/datadog-agent/run/trace-agent.pid'
Mar 22 01:19:30 wasp agent[5844]: 2018-03-22 01:19:30 CET | INFO | (start.go:156 in StartAgent) | Starting Datadog Agent v6.0.3
Mar 22 01:19:30 wasp agent[5844]: 2018-03-22 01:19:30 CET | INFO | (start.go:167 in StartAgent) | pid '5844' written to pid file '/opt/datadog-agent/run/agent.pid'
Mar 22 01:19:31 wasp process-agent[5845]: 2018-03-22 01:19:31 INFO (main_common.go:84) - pid '5845' written to pid file '/opt/datadog-agent/run/process-agent.pid'
Mar 22 01:19:31 wasp process-agent[5845]: 2018-03-22 01:19:31 INFO (tagger.go:77) - starting the tagging system
Mar 22 01:19:31 wasp process-agent[5845]: 2018-03-22 01:19:31 INFO (tagger.go:148) - docker tag collector successfully started
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (start.go:174 in StartAgent) | Hostname is: wasp
Mar 22 01:19:31 wasp trace-agent[5846]: 2018-03-22 01:19:31 INFO (main.go:174) - trace-agent not enabled.
Mar 22 01:19:31 wasp trace-agent[5846]: Set env var DD_APM_ENABLED=true or add
Mar 22 01:19:31 wasp trace-agent[5846]: apm_enabled: true
Mar 22 01:19:31 wasp trace-agent[5846]: to your datadog.conf file.
Mar 22 01:19:31 wasp trace-agent[5846]: Exiting.
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (start.go:191 in StartAgent) | GUI server port -1 specified: not starting the GUI.
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (forwarder.go:232 in Start) | DefaultForwarder started (1 workers), sending to 1 endpoint(s): "https://6-0-3-app.agent.datadoghq.com" (1 api key(s))
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (start.go:231 in StartAgent) | logs-agent disabled
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (tagger.go:77 in Init) | starting the tagging system
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (udp.go:63 in Listen) | dogstatsd-udp: starting to listen on <IP_ADDRESS>:8125
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (tagger.go:151 in tryCollectors) | docker tag collector successfully started
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (runner.go:92 in NewRunner) | Runner started with 1 workers.
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (collector.go:51 in NewCollector) | Embedding Python 2.7.14 (default, Mar  9 2018, 12:15:24) [GCC 4.7.2]
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (file.go:68 in Collect) | File Configuration Provider: searching for configuration files at: /etc/datadog-agent/conf.d
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (file.go:68 in Collect) | File Configuration Provider: searching for configuration files at: /opt/datadog-agent/bin/agent/dist/conf.d
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (file.go:72 in Collect) | Skipping, open /opt/datadog-agent/bin/agent/dist/conf.d: no such file or directory
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:243 in Configure) | could not get a check instance with the new api: __init__() takes at least 4 arguments (4 given)
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:244 in Configure) | trying to instantiate the check with the old api, passing agentConfig to the constructor
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:269 in Configure) | passing `agentConfig` to the constructor is deprecated, please use the `get_config` function from the 'datadog_agent' package (disk).
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:243 in Configure) | could not get a check instance with the new api: __init__() takes at least 4 arguments (4 given)
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:244 in Configure) | trying to instantiate the check with the old api, passing agentConfig to the constructor
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:269 in Configure) | passing `agentConfig` to the constructor is deprecated, please use the `get_config` function from the 'datadog_agent' package (mysql).
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:243 in Configure) | could not get a check instance with the new api: __init__() takes at least 4 arguments (4 given)
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:244 in Configure) | trying to instantiate the check with the old api, passing agentConfig to the constructor
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:269 in Configure) | passing `agentConfig` to the constructor is deprecated, please use the `get_config` function from the 'datadog_agent' package (postgres).
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:243 in Configure) | could not get a check instance with the new api: __init__() takes at least 4 arguments (4 given)
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:244 in Configure) | trying to instantiate the check with the old api, passing agentConfig to the constructor
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:269 in Configure) | passing `agentConfig` to the constructor is deprecated, please use the `get_config` function from the 'datadog_agent' package (postgres).
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:243 in Configure) | could not get a check instance with the new api: __init__() takes at least 4 arguments (4 given)
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:244 in Configure) | trying to instantiate the check with the old api, passing agentConfig to the constructor
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:269 in Configure) | passing `agentConfig` to the constructor is deprecated, please use the `get_config` function from the 'datadog_agent' package (redisdb).
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:243 in Configure) | could not get a check instance with the new api: __init__() takes at least 4 arguments (4 given)
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:244 in Configure) | trying to instantiate the check with the old api, passing agentConfig to the constructor
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | WARN | (check.go:269 in Configure) | passing `agentConfig` to the constructor is deprecated, please use the `get_config` function from the 'datadog_agent' package (network).
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check disk
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check disk with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check docker
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check docker with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check mysql
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check mysql with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check nginx
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check nginx with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check postfix
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check postfix with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check postgres
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check postgres with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check postgres
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check postgres with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check redisdb
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check redisdb with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check cpu
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check cpu with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check file_handle
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check file_handle with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check io
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check io with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check load
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check load with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check memory
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check memory with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check network
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check network with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check ntp
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check ntp with an interval of 15s
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (autoconfig.go:267 in schedule) | Scheduling check uptime
Mar 22 01:19:31 wasp agent[5844]: 2018-03-22 01:19:31 CET | INFO | (scheduler.go:72 in Enter) | Scheduling check uptime with an interval of 15s
Mar 22 01:19:33 wasp agent[5844]: 2018-03-22 01:19:33 CET | INFO | (process_info.go:52 in GetProcesses) | Error fetching info for pid 2793: user: unknown userid 1030
Mar 22 01:19:33 wasp agent[5844]: 2018-03-22 01:19:33 CET | INFO | (process_info.go:52 in GetProcesses) | Error fetching info for pid 2827: user: unknown userid 1030
Mar 22 01:19:33 wasp agent[5844]: 2018-03-22 01:19:33 CET | INFO | (serializer.go:180 in SendMetadata) | Sent host metadata payload, size: 3573 bytes.
Mar 22 01:19:33 wasp agent[5844]: 2018-03-22 01:19:33 CET | INFO | (transaction.go:133 in Process) | Successfully posted payload to "https://6-0-3-app.agent.datadoghq.com/intake/?api_key=*************************c5ba8", the agent will only log transaction success every 20 transactions
Mar 22 01:19:46 wasp agent[5844]: 2018-03-22 01:19:46 CET | INFO | (runner.go:246 in work) | Running check disk
Mar 22 01:19:46 wasp agent[5844]: 2018-03-22 01:19:46 CET | WARN | (datadog_agent.go:135 in LogMessage) | (__init__.py:189) | DEPRECATION NOTICE: `device_name` is deprecated, please use a `device:` tag in the `tags` list instead
Mar 22 01:19:46 wasp agent[5844]: 2018-03-22 01:19:46 CET | INFO | (runner.go:302 in work) | Done running check disk
Mar 22 01:19:46 wasp agent[5844]: 2018-03-22 01:19:46 CET | INFO | (runner.go:246 in work) | Running check docker
Mar 22 01:19:47 wasp agent[5844]: panic: runtime error: index out of range
Mar 22 01:19:47 wasp agent[5844]: goroutine 122 [running]:
Mar 22 01:19:47 wasp agent[5844]: github.com/DataDog/datadog-agent/pkg/collector/corechecks/containers.(*DockerCheck).countAndWeightImages(0xc420159570, 0x302b720, 0xc420868090, 0xc4200e20c0, 0x0, 0x0)
Mar 22 01:19:47 wasp agent[5844]: #011/builds/datadog/datadog-agent/.omnibus/src/datadog-agent/src/github.com/DataDog/datadog-agent/pkg/collector/corechecks/containers/docker.go:127 +0x7cc
Mar 22 01:19:47 wasp agent[5844]: github.com/DataDog/datadog-agent/pkg/collector/corechecks/containers.(*DockerCheck).Run(0xc420159570, 0x3cc95a6e0, 0x3088d60)
Mar 22 01:19:47 wasp agent[5844]: #011/builds/datadog/datadog-agent/.omnibus/src/datadog-agent/src/github.com/DataDog/datadog-agent/pkg/collector/corechecks/containers/docker.go:238 +0x1e4b
Mar 22 01:19:47 wasp agent[5844]: github.com/DataDog/datadog-agent/pkg/collector/runner.(*Runner).work(0xc4201dac60)
Mar 22 01:19:47 wasp agent[5844]: #011/builds/datadog/datadog-agent/.omnibus/src/datadog-agent/src/github.com/DataDog/datadog-agent/pkg/collector/runner/runner.go:255 +0x4a1
Mar 22 01:19:47 wasp agent[5844]: created by github.com/DataDog/datadog-agent/pkg/collector/runner.(*Runner).AddWorker
Mar 22 01:19:47 wasp agent[5844]: #011/builds/datadog/datadog-agent/.omnibus/src/datadog-agent/src/github.com/DataDog/datadog-agent/pkg/collector/runner/runner.go:100 +0x8a
Mar 22 01:19:47 wasp systemd[1]: datadog-agent.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 22 01:19:47 wasp systemd[1]: datadog-agent.service: Failed with result 'exit-code'.

Please, do ask for specific information - happy to provide any info required.
Afters disabling docker:
Getting the status from the agent.

==============
Agent (v6.0.3)
==============

  Status date: 2018-03-22 01:22:58.027211 UTC
  Pid: 8045
  Python Version: 2.7.14+
  Logs:
  Check Runners: 1
  Log Level: info

  Paths
  =====
    Config File: /etc/datadog-agent/datadog.yaml
    conf.d: /etc/datadog-agent/conf.d
    checks.d: /etc/datadog-agent/checks.d

  Clocks
  ======
    NTP offset: -0.000728418 s
    System UTC time: 2018-03-22 01:22:58.027211 UTC

  Host Info
  =========
    bootTime: 2018-03-14 18:31:25.000000 UTC
    kernelVersion: 4.15.0-1-amd64
    os: linux
    platform: debian
    platformFamily: debian
    platformVersion: buster/sid
    procs: 413
    uptime: 629450
    virtualizationRole: host
    virtualizationSystem: kvm

  Hostnames
  =========
    hostname: wasp
    socket-fqdn: wasp.radical.zone.
    socket-hostname: wasp

=========
Collector
=========

  Running Checks
  ==============
    cpu
    ---
      Total Runs: 2
      Metrics: 6, Total Metrics: 6
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    disk
    ----
      Total Runs: 2
      Metrics: 108, Total Metrics: 216
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    file_handle
    -----------
      Total Runs: 2
      Metrics: 1, Total Metrics: 2
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    io
    --
      Total Runs: 2
      Metrics: 286, Total Metrics: 374
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    load
    ----
      Total Runs: 2
      Metrics: 6, Total Metrics: 12
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    memory
    ------
      Total Runs: 2
      Metrics: 14, Total Metrics: 28
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    mysql
    -----
      Total Runs: 2
      Metrics: 164, Total Metrics: 327
      Events: 0, Total Events: 0
      Service Checks: 1, Total Service Checks: 2

    network
    -------
      Total Runs: 2
      Metrics: 56, Total Metrics: 112
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    nginx
    -----
      Total Runs: 2
      Metrics: 7, Total Metrics: 14
      Events: 0, Total Events: 0
      Service Checks: 1, Total Service Checks: 2

    ntp
    ---
      Total Runs: 2
      Metrics: 1, Total Metrics: 2
      Events: 0, Total Events: 0
      Service Checks: 1, Total Service Checks: 2

    postfix
    -------
      Total Runs: 2
      Metrics: 3, Total Metrics: 6
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

    postgres
    --------
      Total Runs: 2
      Metrics: 0, Total Metrics: 0
      Events: 0, Total Events: 0
      Service Checks: 1, Total Service Checks: 2Error: ('FATAL', '28P01', 'password authentication failed for user "datadog"')
      Traceback (most recent call last):
        File "/opt/datadog-agent/bin/agent/dist/checks/__init__.py", line 332, in run
          self.check(copy.deepcopy(self.instances[0]))
        File "/opt/datadog-agent/embedded/lib/python2.7/site-packages/datadog_checks/postgres/postgres.py", line 791, in check
          db = self.get_connection(key, host, port, user, password, dbname, ssl, connect_fct, tags)
        File "/opt/datadog-agent/embedded/lib/python2.7/site-packages/datadog_checks/postgres/postgres.py", line 690, in get_connection
          password=password, database=dbname, ssl=ssl)
        File "/opt/datadog-agent/embedded/lib/python2.7/site-packages/pg8000/__init__.py", line 328, in connect
          user, host, unix_sock, port, database, password, ssl)
        File "/opt/datadog-agent/embedded/lib/python2.7/site-packages/pg8000/core.py", line 1263, in __init__
          raise self.error
      ProgrammingError: ('FATAL', '28P01', 'password authentication failed for user "datadog"')

    postgres
    --------
      Total Runs: 2
      Metrics: 85, Total Metrics: 170
      Events: 0, Total Events: 0
      Service Checks: 1, Total Service Checks: 2

    redisdb
    -------
      Total Runs: 2
      Metrics: 38, Total Metrics: 76
      Events: 0, Total Events: 0
      Service Checks: 1, Total Service Checks: 2

    uptime
    ------
      Total Runs: 2
      Metrics: 1, Total Metrics: 2
      Events: 0, Total Events: 0
      Service Checks: 0, Total Service Checks: 0

========
JMXFetch
========

  Initialized checks
  ==================
    no checks

  Failed checks
  =============
    no checks

=========
Forwarder
=========

  CheckRunsV1: 2
  IntakeV1: 2
  RetryQueueSize: 0
  Success: 6
  TimeseriesV1: 2

  API Keys status
  ===============
    https://6-0-3-app.agent.datadoghq.com,*************************c5ba8: API Key valid

==========
Logs Agent
==========

  Logs Agent is not running

=========
DogStatsD
=========

  Checks Metric Sample: 1406
  Event: 1
  Events Flushed: 1
  Number Of Flushes: 2
  Series Flushed: 198
  Service Check: 42
  Service Checks Flushed: 23
  Dogstatsd Metric Sample: 6

docker.yaml:
init_config:

instances:
  - ## The agent honors the DOCKER_HOST, DOCKER_CERT_PATH and DOCKER_TLS_VERIFY
    ## environment variables to setup the connection to the server.
    ## See https://docs.docker.com/engine/reference/commandline/cli/#environment-variables
    url: 'unix://var/run/docker.sock'
    new_tag_names: true

    ## Data collection
    ##

    # Create events whenever a container status change.
    # Defaults to true.
    #
    # collect_events: false

    # By default we do not collect events with a status ['top', 'exec_start', 'exec_create'].
    # Here can be added additional statuses to be filtered.
    # List of available statuses can be found here https://docs.docker.com/engine/reference/commandline/events/#object-types
    # filtered_event_types:
    #    - 'top'
    #    - 'exec_start'
    #    - 'exec_create'

    # Collect disk usage per container with docker.container.size_rw and
    # docker.container.size_rootfs metrics.
    # Warning: This might take time for Docker daemon to generate,
    # ensure that `docker ps -a -q` run fast before enabling it.
    # Defaults to false.
    #
    collect_container_size: true

    # Collect images stats
    # Number of available active images and intermediate images as gauges.
    # Defaults to false.
    #
    collect_images_stats: true

    # Collect disk usage per image with docker.image.size and docker.image.virtual_size metrics.
    # The check gets this size with the `docker images` command.
    # Requires collect_images_stats to be enabled.
    # Defaults to false.
    #
    collect_image_size: true

    # Collect disk metrics (total, used, free) through the docker info command for data and metadata.
    # This is useful when these values can't be obtained by the disk check.
    # Example: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html
    # Note that it only works when the storage driver is devicemapper.
    # Explanation of these metrics can be found here:
    # https://github.com/docker/docker/blob/v1.11.1/daemon/graphdriver/devmapper/README.md
    # Defaults to false.
    #
    collect_disk_stats: true

    # Monitor exiting containers and send service checks based on exit code value
    # (OK if 0, CRITICAL otherwise)
    # Defaults to false.
    #
    # collect_exit_codes: true

    # Allows ad-hoc spike filtering if the system reports incorrect metrics.
    # This will drop points if the computed rate is higher than the cap value
    # capped_metrics:
    #   docker.cpu.user: 1000
    #   docker.cpu.system: 1000

    ## Tagging
    ##

    # You can add extra tags to your Docker metrics with the tags list option.
    # Example: ["extra_tag", "env:testing"]
    #
    # tags: []

@uded thanks for the detailled report we were able to spot the issue rapidly, it will occur when collecting sizes on a docker image with no repository tags.
In the meanwhile to mitigate the issue you can either try to remove the guilty image or disable the collect_image_size setting temporarily.

OK, which image is that? I am uncertain what was deployed that caused it...

@uded docker image ls --format "{{.ID}}: {{.Repository}}" | grep none should help you find the troublesome image, you can confirm it by using docker image inspect <id> and see "RepoTags": []

Tried what you sent me, @mfpierre. And this is what I got:
⚡ root@wasp  /home/uded  docker image ls --format "{{.ID}}: {{.Repository}}" | grep none
 ✘ ⚡ root@wasp  /home/uded 

None, zero. Nothing. And no one changed anything with Docker installation for last 4-5 days...

@uded you should have more chance withdocker image ls --format "{{.ID}}" | xargs -t -I '{}' docker image inspect '{}' | grep "\"RepoTags\": \[\]"

OK, that gave me some results. I will look into it.
 ⚡ root@wasp  /home/uded  docker image ls --format "{{.ID}}" | xargs -t -I '{}' docker image inspect '{}' | grep "\"RepoTags\": \[\]"
docker image inspect 9797e3c0293f
docker image inspect 9797e3c0293f
docker image inspect 4189e5cacc1b
docker image inspect 27263afa0818
docker image inspect 6a1a828c53f1
docker image inspect b7112fd25f97
        "RepoTags": [],
docker image inspect c6b513da2ff3
docker image inspect b216bc18aa6f
docker image inspect f623213473f3
docker image inspect 873fbdc4536c
        "RepoTags": [],
docker image inspect 9b9a5552926f
docker image inspect b786c2be8466
docker image inspect 7775ababc3c6
docker image inspect 0ea6a041f928
docker image inspect 3925ef3919cc
docker image inspect 7bf66eeb1ed6

OK, our management software, after automatically upgrading the image to the newly released latest tag, is abandoning the previously used image (which was latest till that point) tagless. It kinda makes sense, but it's not ideal. Anyway, hope your fix was or will be released soon as it will happen again for sure ;-)


Android apt plugin is incompatible with the Android Gradle plugin.

My project Gradle version
4.1
My project Android Gradle plugin version
3.0.1
after I add below line to root project buildscript  dependencies block
classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'
Gradle give me following error message:
Error:android-apt plugin is incompatible with the Android Gradle plugin.  Please use 'annotationProcessor' configuration instead.

This issue is not related at all with Mockery.
https://stackoverflow.com/questions/42574803/incompatible-plugins-for-android-apt-after-upgrading-to-android-studio-2-3

Sorry, apt plugin 'com.neenbedankt.gradle.plugins:android-apt:1.8' is not incompatible with the gradle android plugin v3.0 but the v2.3.


Allow global setting

The plugin is very useful. The only thing that's nagging me is, that I have to enable it in every job. Given I have > 100 Jobs, this gets quite cumbersome ;)
What do you think about a global switch for enabling it per default?

It's a good idea. When I was coding this I couldn't find how to do it. Pull requests welcome!

I would like to help but don't know either. Sorry.

I use a wrapper in Jenkins Job builder to ensure that the plugin is enabled for all my jobs:
http://docs.openstack.org/infra/jenkins-job-builder/wrappers.html

@tpot It would be great to document this in README somehow, please contribute!

Try this script:
def jobs = hudson.model.Hudson.instance.items
jobs.each { job ->
def has_color_wrapper = false
job.buildWrappersList.each { wrapper ->
  if (wrapper instanceof hudson.plugins.ansicolor.AnsiColorBuildWrapper) {
    has_color_wrapper = true
    println("$job.name is already configured.")
  }
}
if (!has_color_wrapper) {
  	println("Adding AnsiColor to $job.name")
  	job.buildWrappersList.add(new hudson.plugins.ansicolor.AnsiColorBuildWrapper());
	job.save()
}

}

+1, especially in the context of Jenkins 2.x Pipeline builds a global setting would be super useful. Enabling colored output is a cross-cutting concern that you may not want to repeat in each and every Jenkinsfile.
Will give @dsaita 's workaround a try...

Another approach I was thinking about was redefining the sh step from within a global library, but

my groovy foo is a bit outdated and first experiments not successful
I don't know if redefining pipeline DSL steps would work at all or is guarded against somewhere

If we can't have a truly global setting - can we have a one liner for pipeline jobs that doesn't use a block? I'm new to pipeline but having all these wrapper blocks seems a bit ridiculous.

@subos2008 were you able to find a solution?

@ericfrancis not yet. Perhaps the declarative style makes it easier, but our pipelines aren't simple enough to use declarative style at the moment.

@subos2008 I was able to wrap all with:
#!groovy
pipeline {
  agent any

  options {
    buildDiscarder logRotator(daysToKeepStr: '5')
    timeout(time: 10, unit: 'MINUTES')
    ansiColor('xterm')
  }

@ericfrancis Yep, that's the new declarative style for pipelines.  Vastly improves this kind of thing. However, the declarative style is (currently) much more limited. A solution for the traditional groovy script would be much appreciated - which is what this thread is about. (aiui)

Any progress on this issue?

An equivalent global config was added to the timestamper plugin here:
https://github.com/jenkinsci/timestamper-plugin/commit/1afb7d4b4077c7aa7660794d75e018def8ba08c0
It would be great to see a global config option for ansicolor

Please contribute!

Thank you @kcboschert :+1:

Hi, would you consider cutting a new release so we can use this great feature? Thanks!

Hi, would you consider cutting a new release so we can use this great feature? Thanks!

https://github.com/jenkinsci/ansicolor-plugin/issues/166


fix volume_server.proto conflict

What problem are we solving?
fix volume_server.proto conflict after https://github.com/seaweedfs/seaweedfs/pull/3841 and https://github.com/seaweedfs/seaweedfs/commit/dcd0743a35912dfa559ae912e5208f15dd186386
How are we solving the problem?
How is the PR tested?
Checks

[ ] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

Do not release without merge this PR (ReadNeedleBlobRequest broken)


Can't click buttons in status bar during tooltip transition.

Keyword is during.
When attempting to click a button, such as New Terminal, Close All or switching to a different open terminal. I must first wait until the fade in transition on the tooltip has finished, meaning if the mouse release event occurs before this the button is not clicked.
The buttons work fine when I disable the transition from Developer Tools.

Well damn, I think it might be from atom-material-ui by silvestreh.

I've been experiencing the same issue with atom-material-ui. How did you disable the transition from devtools?

Came here with the same issue, thanks!

Please retest again with platformio-atom-ide-terminal 2.9.0 is using node-pty-prebuilt instead unmaintained and outdated pty.js

Please retest again with platformio-atom-ide-terminal 2.9.0 which since f64888d is using node-pty-prebuilt instead unmaintained and outdated pty.js. This is good news for stability and compatibility.
if issues persist, please open a new ticket with requested information.
Thx =)


React My Personal Apps Update - Improve responsive Grid Tiles

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

What's in this Pull Request?
Improve responsive behaviour  grid Tiles

@joaojmendes thanks for making an awesome sample even more awesome.
I'd still like you to present on the May 21st SPFx community call. Would you be interested?

Hi  Hugo,
Sorry for the later answer , I’m sorry but I can not confirm right now… let me check if I’m free on that day and I inform you.
Thank you!
From: Hugo Bernier<EMAIL_ADDRESS>Reply to: SharePoint/sp-dev-fx-webparts<EMAIL_ADDRESS>Date: Saturday, 11 April 2020 at 18:11
To: SharePoint/sp-dev-fx-webparts<EMAIL_ADDRESS>Cc: João Mendes<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [SharePoint/sp-dev-fx-webparts] React My Personal Apps Update - Improve responsive Grid Tiles (#1207)
@joaojmendeshttps://github.com/joaojmendes thanks for making an awesome sample even more awesome.
I'd still like you to present on the May 21st SPFx community call. Would you be interested?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/SharePoint/sp-dev-fx-webparts/pull/1207#issuecomment-612467696, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC7YHVID6OS3KGBV35A7M5TRMCQDRANCNFSM4MF7DDOA.


Custom dataset issue

I have used my own custom dataset as per the instructions provided in the README file. But yet facing issue. Model is stuck here as shown for infinity.

I updated some codes to process custom datasets.
Please check 'tagruler/server/datasets/data_process_example' folder.


Copy fea-rs VariationStoreBuilder to write-fonts

and make it pub so that fontc can use it to build stuff like HVAR or COLR
Fixes https://github.com/googlefonts/fontations/issues/633
fea-rs var_store.rs module was copied from this commit:
https://github.com/cmyr/fea-rs/blob/497f51c66530f0b685646fae1db192502cdab1fe/fea-rs/src/compile/tables/var_store.rs

based on the assumption you moved it w/o significant changes

first commit literally copied from https://github.com/cmyr/fea-rs/blob/497f51c66530f0b685646fae1db192502cdab1fe/fea-rs/src/compile/tables/var_store.rs
following commits simply adjust the import paths and make it pub


Create new motion gets JS error "this.getVersion(...) is undefined"

To reproduce:
Create new motion (enter title only). Save. JS console shows error in motion getTitle method. This line in core/base.js is also reference in following error: DS.inject(data.collection, data.data);
The error is also shown on all other clients after auto update.
@ostcar Any idea?
Error: this.getVersion(...) is undefined
.methods.getTitle@http://localhost:8000/static/js/motions/base.js:138:28
anonymous/fn@http://localhost:8000/static/js/openslides-libs.js line 8 > Function:2:244
o/<@http://localhost:8000/static/js/openslides-libs.js:7:6561
bn/this.$get</p.prototype.$digest@http://localhost:8000/static/js/openslides-libs.js:7:15082
bn/this.$get</p.prototype.$apply@http://localhost:8000/static/js/openslides-libs.js:7:16731
e/p/u[e]@http://localhost:8000/static/js/openslides-libs.js:66:5311
@http://localhost:8000/static/js/core/base.js:185:17
newConnect/socket.onmessage/<@http://localhost:8000/static/js/core/base.js:72:21
rt@http://localhost:8000/static/js/openslides-libs.js:1:3732
An/<@http://localhost:8000/static/js/openslides-libs.js:1:14598
newConnect/socket.onmessage@http://localhost:8000/static/js/core/base.js:71:17
SockJS</r.prototype.dispatchEvent@http://localhost:8000/static/js/openslides-libs.js:21:12911
SockJS</S.prototype._dispatchMessage@http://localhost:8000/static/js/openslides-libs.js:21:26002
SockJS</S.prototype._didMessage@http://localhost:8000/static/js/openslides-libs.js:21:26892
SockJS</S.websocket/i.ws.onmessage@http://localhost:8000/static/js/openslides-libs.js:21:28838

I found the bug, but I don't know how to fix it.
On the client side a motion is only valid if it has at least one version. Without a version a motion can not have text, title or reason. So when the server sends a motion with {version: []} then problems like this one happens.
On the server side, a new motion has to be saved before any version can be added. We first have to save the motion and only then can save the versions in a second step. So for a short moment there is a motion without versions on the server. In theory this is no problem, because this could happen in a transaction. But...
When we save the motion to the database, an autoupdate is triggered. So each client gets the motion without the versions (which are not saved at this moment).
This issue is connected to #2007. We need to find a way to only trigger the autoupdate after an transaction. Maybe this django 1.9 feature can help https://docs.djangoproject.com/en/1.9/topics/db/transactions/#django.db.transaction.on_commit @normanjaeckel any idea?


Convoy can change status when assets is active. Expand tests

Coverage decreased (-0.1%) to 49.74% when pulling 6d7d06eaf221fe99bb261bd561f0b91f7d724517 on oleksiyVeretiuk:505088183523951_change_asset_status into 4114a4cfb0317d48682ce3ce34fd45989d564303 on openprocurement:master.


fix: handle select errors

Fixes https://github.com/tannerlinsley/react-query/issues/1540

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Kubernetes Documentation Examples Port Configuration

Do you want to request a feature or report a bug?
Documentation Update
What needs updating?
The kubernetes examples (https://docs.traefik.io/user-guide/kubernetes/) and (https://github.com/containous/traefik/tree/master/examples/k8s/traefik-ds.yaml) Have a nodeport service fronting a daemonset with hostports. This creates duplicate methods for accessing traefik, and is not clear for new users.
We should clean up the examples to keep the deployment/daemonset examples as close to each other as possible, and update the port configurations to be the same.
We should also make a note about hostports, and how they are not supported in production, and possibly a link to the k8s documentation.

Closed by #3368.


Velocity / Delta Position Controller

Type of Issue
Select the type of issue:

[ ] Bug report (to report a bug)
[ X] Feature request (to request an additional feature)
[ ] Tracker (I am just using this as a tracker)
[ ] Refactor request
[ ] Documentation Ask

Description
Given that a lot of robot research uses delta position control or velocity control, could you add an example policy for one of these? I know these can be built with a light wrapper around the existing policies, but it could be nice to standardize. This way, if I want to use a dataset collected with a Polymetis velocity controller, it is straightforward.
Current Behavior
There is no velocity or delta position controller.
Expected Behavior
env.step([1,0,0]) moves robot forward by some standard unit of measurement.
Links to any relevant pastes or documents
Please post links to any relevant documents that might contain any extra information.
Checklist
Use this checklist if you are using this issue as a tracker:

[ ] Task 1
[ ] Task 2
[ ] Task 3 ...

Added to our list of planned features, although I cannot promise a delivery date.
In the meanwhile feel free to let me know if you have any issues creating a custom velocity controller.

Just an update, just adding a delta=True option to the update_desired_ee_pose(...) function would be sufficient :)

Update on this issue: We are implementing a joint velocity controller in the low-level controller space in #1222. A Cartesian controller might come later but that is also low priority for us.
Adding a delta argument to the impedance methods doesn't seem to do much because the user can already easily increment the desired pose themselves.

@AlexanderKhazatsky please reopen this issue if the current workarounds don't suffice. Thanks!


[Android] Support Action.isEnabled

Related Issue
Fixes #5719
Description

Re-SWIG'd shared model changes.
Elements with selectAction with isEnabled: false are rendered as if there is no selectAction provided.
Elements with inlineAction with isEnabled: false are not clickable.
Top-level actions and ActionSet actions with isEnabled: false` are not clickable and get platform's default disabled styling.
Custom actions are expected to determine how to support isEnabled (the SDK doesn't impose any enabling/disabling)

Sample Card
Updated v1.5\Elements\Action.isEnabled sample to include RichTextBlock
How Verified

Microsoft Reviewers: Open in CodeFlow

have you gotten VSCode set up with the editorconfig extension?
also, something something emacs

Yes! Yet, it thinks this file should have tabs (bottom info bar).

have you gotten VSCode set up with the editorconfig extension?

Yes! Yet, it thinks this file should have tabs (bottom info bar).

Actually,
https://github.com/microsoft/AdaptiveCards/blob/a05ba759ac15ce08c503650ef3edea8fa9e4a24d/.editorconfig#L10-L11

also, something something emacs

I'd sooner use vim :)

you can do that in emacs!


Filter that leaves a single dimension value / reduce on a single value

I'm currently trying to convert proof of concept use case 3 to the new processes.
I'm wondering whether I need to actually run a no-op reducer after executing filter_bands with a single band name passed?
As far as I can see datacube = b.process("filter_bands", {data: datacube, bands: ["B8"]); would only remove all bands except B8, but the spectral dimension is still there. So if I'd really want to get rid of the spectral dimension, I'd need to call reduce and basically pass a no-op callback (or any process that doesn't alter the data as sum or so). That sounds really cumbersome:
datacube = b.process("filter_bands", {data: datacube, bands: ["B8"]});
datacube = b.process("reduce", {
	data: datacube,
	dimension: "spectral",
// Using sum solely as a no-op process here as only a single value is passed  :-(
	reducer: (builder, params) => builder.process("sum", {data: params.data})
});

If we just want to throw another process on it, it would probably be something like reduce_bands(data: datacube, band: "B8"), I guess? But I could also think of other dimensions that need to be filtered/reduced to a single value simply by its dimension value. So maybe we need something more general.
An alternative would be to specify that dimensions get removed once a filter leaves only a single dimension value, but that sounds dirty and loosens the definition of a filter (number of dimensions stays the same).
Maybe related to #43 and the ideas about adding a band selector.

What speaks against keeping the dimension with a single entry? If we want to get rid of the dimension, I would rename the process to band_selector as suggested and either vary the bands argument (if it is a string, "reduce" the dimension. If it is an array/list, keep the dimension) or add another boolean argument (e.g. reduce).

@claxn Nothing in general, but in the proof of concept use case 3 I need to get rid of the remaining dimensions except the one I want to group by to get the zonal statistics as time series. Otherwise the process doesn't know how to handle the remaining data. A quote from aggregate_polygon:

The data cube must have been reduced to only contain two raster dimensions and a third dimension the values are aggregated from, for example a single band. Otherwise this process fails with the TooManyDimensions error.

It seems like in the older versions we implied that if we filter for a single band the dimension is reduced automatically.

Ak okay, thanks for the clarification, I was not aware of that. I would also agree with your approach within the reduce process.

Introduced my proposal to the reduce process, please review it: https://github.com/Open-EO/openeo-processes/commit/fbae1eb3ddf09123dad1bb0eb062e3d9b71094f3


Add a -f/--format option to change the format of the badges

I see several alternatives

by default 'auto' format: display the number of tests only if 100% success, otherwise display xxx/yyy
alternate format 1: display the success percentage

For the coverage badge is could be a format string for the coverage float, such as '%.2f' ?

Hi! I would also find it useful to be able to modify the title of the badge.
Something along the lines of genbadge [flake8|coverage|tests] --title "Alternative Title".


[QUESTION] Are running workflows affected by workflow-definition updates?

Does a running workflow overtake die updated definition ?

@JohnHaze If you're using the version parameter in Workflow definition when updating, then it shouldn't be a problem. Eg: if a workflow is running version:5, and you update metadata to version:6, the running workflows won't be affected, and new workflows could use version:6

@kishorebanala Thank you so much for your reply.
What happens in the case of an update of the same version of the workflow?


Text wrapping on top of itself in messageview

Not easily replicable.
Text seems to wrap on top of itself at times for some reason.
Could have something to do with multiple paragraphs?

Properly picture documented in #30. Seems to be a problem with newlines in some way.


Check that logs are rotating in loki

I think promtail from loki-stack had some option to delete old logs, but not sure if it's configured properly in loki-stack helm chart
Need to check how it's working and maybe add some configuration to values.yaml for loki-stack

Found ServiceMonitor for prometheus operator, but not sure if it works with installed lite version
Maybe i could just write a script to get information i want? Not like i need to constantly monitor it anyway


How to change the default primary key  data type when  creating a table ? I want to set it to 'bigint'

setType

https://book.cakephp.org/phinx/0/en/migrations.html#creating-a-table
Set 'id' => false and create bigint column with addColumn
$table = $this->table('mytable', ['id' => false, 'primary_key' => ['id']])
    ->addColumn('id', 'bigint')


bug(lazygit): pressing Escape quickly twice puts it in normal mode.

Did you check docs and existing issues?

[X] I have read all the snacks.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of snacks.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.2
Operating system/version
archlinux
Describe the bug
minor bug though as user can just avoid pressing Esc twice quickly and pressing i or a after this brings it back.  also tried this on kdheepak/lazygit.nvim and this bug doesnt happen.
Steps To Reproduce

Open Snacks.lazygit
Press Esc quickly twice

Expected Behavior
shouldn't go into normal mode
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "folke/snacks.nvim", opts = { lazygit = { enabled = true}} },
  },
})

That's not a bug. That's on purpose. Check the docs to disable the keymap in the style if you don't want that.


Unable to use Middleware as substitute to table.hook('reading')

I'm trying to transform the response object of a query using the new Middleware API. However, it doesn't appear possible to re-assign the value of the DbCoreCursor:
            // ....middleware implementation...
            openCursor: (
              req: DBCoreOpenCursorRequest
            ): Promise<DBCoreCursor | null> => {
              return nextTable.openCursor(req).then(result => {
                result.value = {...} // <--- can't set to a new value since value is readonly
                return result;
              });
            }

You can return an object that inherit from result but overrides value. You also need to check for null before returning your alternate cursor. Use Object.create(result, {value: {get(){ return yourValue;}}})

Thanks, @dfahlander. Unfortunately, that solution doesn't seem to work for me. Can you check out this simplified working example I put together that replicates the issue I am seeing in my project:
https://stackblitz.com/edit/dexie-middleware-example?file=package.json
Thanks!

@dfahlander do you have any other recommendations or guidance since the code you proposed (Object.create(result, {value: {get(){ return yourValue;}}})) throws an exception (Illegal invocation)?
Thanks for the help!

You need to check result for null before calling Object.create(). If result is null, you must also return null rather than object.create.


adding env-var aware site detection for drush and wp commands

Closes #437

+1

@joshkoenig Do you have permissions to deploy this? You're clear to launch.

Thanks! I can merge now.
I think with 0.8.0 imminent we can wait on that to roll this out to everybody -
https://github.com/pantheon-systems/cli/milestones/0.8.0


A suggestion about product design

First of all, thank you very much for developing such a good tool with rich functions.
I have an idea for a product design.

A client only needs to configure the connection address of the server, and the client will be registered in the server.
On the server side, the registered client can be tagged.
On the server side, multiple file synchronization policies can be created.
On the server side, file synchronization policies can be associated with one or more tagged clients.
On the client side,The client will receive the file synchronization policy from the server and execute the actions of this policy

A client only needs to configure the connection address of the server, and the client will be registered in the server.
On the server side, the registered client can be tagged.

Thanks for your suggestion and that sounds great. @myselfghost
At present, there is a simple client registration implementation, see the online field in the Report API.
In order to achieve policy delivery, we need to further enhance security, stability, and reliability.

On the server side, multiple file synchronization policies can be created.
On the server side, file synchronization policies can be associated with one or more tagged clients.
On the client side,The client will receive the file synchronization policy from the server and execute the actions of this policy

Which scenarios require support for policy delivery: pulling files from the server, pushing files to the server, or both?
What policies do we need to support? All existing flags, or some other policies?
Do you have any user cases for specific scenarios involving multiple policies, and how to resolve or detect policy conflicts?

One of the scenarios is: building a backup center，

Machine A, path /data/p1, backed up once a day
Machine B, path /data/p2, backed up once a week
Machine C, path /data/p3, backed up once a week
Machine C, path /data/p4, backed up once a month

maybe need so many policy ,It would be better for us to manage these policies uniformly on the server side.

So, how to assign the policy 1 to machine A, and the policy 2 to machine B?
Do we need a back-end management platform to assign the policies by administrator?

So, how to assign the policy 1 to machine A, and the policy 2 to machine B? Do we need a back-end management platform to assign the policies by administrator?

Looks like a web backend is needed.

It is indeed a lot of work to develop into a mature product, and there is no rush. We can think carefully about the actual usage scenarios, slowly design the product architecture, and then develop it.

Let me add one more thought. The client receives a policy from the server, and the actions performed by this policy should have multiple possibilities. for example:

Pull files from server
Push files to the server;
Pull files from other addresses such as minio or sftp;
Push files to other addresses such as minio or sftp;

Should the client support multiple tasks at the same time?

Should the client support multiple tasks at the same time? We need an isolated context to handle multiple tasks.
maybe  the client should support multiple tasks

One of the scenarios:
Machine C, path /data/p3, backed up once a week, push files to server
Machine C, path /data/p4, backed up once a month,push files to minio

+----------+                           +----------+                           +----------+                           +----------+                          +----------+
|          |                           |          |<---(C)---connect&auth ----|  Client  |                           |          |                          |          |
|  Server  |                           |  Server  |                           |  Manager |  (process or goroutine)   |  Client  |                          |  Client  |
|  Disk    |                           |          |----(D)--deliver policy--->|          |----(E)-- start worker --->|  Worker  |                          |  Disk    |
|          |                           |          |                           +----------+                           |          |                          |          |
|          |                           |          |<-----------------(H)--- connect&auth ----------------------------|          |                          |          |
|          |<---(J)--- read file   ----|          |<-----------------(I)--- pull file -------------------------------|          |                          |          |
|          |                           |          |                                                                  |          |                          |          |
|          |----(K)--- return file --->|          |------------------(L)--- send file ------------------------------>|          |----(M)--- write file --->|          |
|          |                           |          |                                                                  |          |                          |          |
|          |                           |          |<-----------------(O)--- report result ---------------------------|          |<---(N)-- write result----|          |
+----------+                           +----------+                                                                  +----------+                          +----------+
                                          ^    ^                                                                        |    ^
                        (A) create policy |    |                                                  (F) add to task queue |    |
                                          |    |                                                                        |    |
                                          |    | (B) assign policy                                                      v    | (G) execute task
                                       +--+-—--|--+                                                                  +-------|--+
                                       |          |                                                                  |          |
                                       |  Admin   |                                                                  |  Task    |
                                       |          |                                                                  |  Queue   |
                                       |          |                                                                  |          |
                                       |          |                                                                  |          |
                                       |          |                                                                  |          |
                                       +----------+                                                                  +----------+

For better isolation, consider creating a process for each task, something like the Daemon Mode.


AuthenticationTokenSchema after Login

AuthenticationTokenSchema
In Swagger the example response for a successful login in the AdminAPI has the following AuthenticationTokenSchema:
object string
authentication_token string
user_id string
user UserSchema
account_id string
account AccountSchema

But when I do an actual login it also returns the key master_admin bool. Is there a reason for this or is it missing from the example?
Your environment
Commit 169bf5c

Also in the MintedTokenSchema it says subunit_to_unit boolean but I think this should be subunit_to_unit integer.

master_admin is very recent (last week I think). Sorry for missing that from the schema.
Basically it's a boolean flag that tells whether the user holding that token is an admin on the master account or not.
And the "master account" is the name we're using for the top-level account. Only one master account exists in a given ewallet system. Because it's the top-level account, we're also granting the admin on master account to manage system-wide settings such as create minted tokens, etc. Note: we're still adding permissions to cover all actions.

If you'd like to work on this please let us know. Otherwise I'll put this into our queue. Thanks again!

Yea sure I'll pick it up


[GURPS] 2.10.8

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

Changes / Description

ENHANCEMENT: Ranged attack table. If you enter a ROF greater than 1, the attack roll will ask for the number of shots fired and the roll results will show the number of hits based on recoil. If there's no recoil entered, it will assume the recoil is 1.

ACTIONS: The ranged attack table should automatically update the new shots fired macro when the sheet loads, but it's possible it doesn't. In that case, just change the ROF for a ranged attack and the macro should get updated.

DISPLAY BUGFIX: Fixed the order of fields for the Modifier Tool Summary box. Reported by Demented Avenger.
ENHANCEMENT: Hit Location Table, each hit location has a toggle notes button, in addition there are two links to open and close all notes. Requested by Tommi.

Character Sheet Info Roll20 Internal Use only.


How to work with submenus? Still missing order

Hello again,
maybe there is something new or I'm missing something in doc, but how do you sort submenu pages in main menu? Now i can generate all subpages for page in main menu, but how to set order for this pages?

Wagtailmenus respects the 'natural ordering' of pages, which is determined by the path value. You can see / modify this order from the explorer by clicking the little 'reorder' icon at the top of the first column:
http://docs.wagtail.io/en/stable/editor_manual/finding_your_way_around/the_explorer_page.html#reordering-pages

Am closing this issue

Thanks, my fault.


Rsync process with 160%

After install rsync version I have this scenario on my machine:

I put here the link to the conversation (in pt-BR) to contextualize:
https://gitter.im/azukiapp/azk/pt?at=5567a7cfbeed96397ea737be


day of week not correct when use yearOffset

use yearOffset: 543 for buddhist year but day of week not correct.
eg. mon 19 changed to thu 19

Ref: https://github.com/xdan/datetimepicker/issues/490


Update DrillingReport.csv

Changed date format to YYYY-MM-DD

@lolettac Is this PR still needed? or can I close it?

Thanks Bryan, would you please close it?
From: Bryan Vestey<EMAIL_ADDRESS>Reply-To: maana-io/q-tutorials<EMAIL_ADDRESS>Date: Monday, February 18, 2019 at 10:56 AM
To: maana-io/q-tutorials<EMAIL_ADDRESS>Cc: Loletta Chiu<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [maana-io/q-tutorials] Update DrillingReport.csv (#3)
@lolettachttps://github.com/lolettac Is this PR still needed? or can I close it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/maana-io/q-tutorials/pull/3#issuecomment-464843165, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlWkFic58qf0W0STpDFBH880nzgL84jKks5vOvdTgaJpZM4Ug6zi.

This is no longer needed, so closing it.


Include example of EdgeNavigation

If possible this would highlight how to override the default behaviours. Such as:

Disabling swiping to toggle the menu
Disabling dragging of menu panel when its active
Applying alternative triggers

These questions come up a lot on Slack so thought I would post the request here.

Thanks! I'll look into it


Tutorial Classical Shadows

Before submitting
Please complete the following checklist when submitting a PR:

[ ] Ensure that your tutorial executes correctly, and conforms to the
guidelines specified in the README.

[ ] Add a thumbnail link to your tutorial in beginner.rst, or if a
QML implementation, in implementations.rst.

[ ] All QML tutorials conform to
PEP8 standards.
To auto format files, simply pip install black, and then
run black -l 100 path/to/file.py.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

Title:
Summary:
Relevant references:
Possible Drawbacks:
Related GitHub Issues:

Great choice @bdoolittle!

@trbromley The classical shadows tutorial is ready for code review. Please take a look when you get a chance. Thanks!

Thanks for all the comments, I think we've been able to address all the feedback.

I think we're ready for merging. @trbromley, could you take a final look?


Return Result instead of Option for encoding/decoding

Coverage decreased (-0.5%) to 89.32% when pulling 2d6edfcfa08af254285704e283f88b8059bb5268 on coding-use-result into 0c07a9b6d23353b2dba1d1406396d39733f35d9e on master.

Coverage decreased (-0.5%) to 89.32% when pulling 2d6edfcfa08af254285704e283f88b8059bb5268 on coding-use-result into 0c07a9b6d23353b2dba1d1406396d39733f35d9e on master.


httpx: 1.3.2 -> 1.3.3

Diff: https://github.com/projectdiscovery/httpx/compare/refs/tags/v1.3.2...v1.3.3
Changelog: https://github.com/projectdiscovery/httpx/releases/tag/v1.3.3
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 239019 run on x86_64-linux 1

1 package built:

httpx


Grafana dashboard

Hello,
Thanks for your exporter it works well !
I haven't seen any dashboard for your exporter so i've created one, if you would like to add it I can create a pull request :)
https://grafana.com/grafana/dashboards/12688

Awesome, I will add it to the README in the next few days, as I'm a bit short on time right now.

Sure, your welcome


Fuzzing matching of DateTime

Hello.
Please consider the following test example:
Wrapper = Struct.new(:date)
w = Wrapper.new(DateTime.new(2017, 9, 22, 20, 0, 30))

expect(w).not_to have_attributes(date: DateTime.new(2017, 9, 22, 15, 30, 15))

Unfortunately, this test will fail because have_attributes matcher internally uses FuzzyMatcher for comparing two dates which in turn uses Date#===. Since DateTime inherits from Date it uses this method which returns true for dates if they are the same day what is exactly we have in our example.
From the example shown above it was not obvious the datetimes would be compared as dates and this situation could potentially be dangerous for those who don't know about it.

I don't understand your example.  have_attributes accepts a hash of key/value pairs, for what the attributes names and values are.  You've passed a DateTime that doesn't make any sense to me...

This is the docs for have_attributes method from rspec-expectations method:
    # Passes if actual's attribute values match the expected attributes hash.
    # This works no matter how you define your attribute readers.
    #
    # @example
    #   Person = Struct.new(:name, :age)
    #   person = Person.new("Bob", 32)
    #
    #   expect(person).to have_attributes(:name => "Bob", :age => 32)
    #   expect(person).to have_attributes(:name => a_string_starting_with("B"), :age => (a_value > 30) )
    #
    # @note It will fail if actual doesn't respond to any of the expected attributes.
    #
    # @example
    #   expect(person).to have_attributes(:color => "red")
    def have_attributes(expected)
      BuiltIn::HaveAttributes.new(expected)
    end
    alias_matcher :an_object_having_attributes, :have_attributes
    alias_matcher :having_attributes,           :have_attributes

It works both for hashes and objects.

Sorry, you're right I fixed my example but it still won't pass.

To support composable matchers, all our higher-order matchers (e.g. matchers which can accept other matchers, regexes, etc as arguments) use the === protocol for matching against the arguments.  This provides a lot of additional flexibility that many users rely on and it's not something we can consider changing at this point.  It's unfortunate that Ruby defines DateTime#=== to only match on the date part of it.  IMO, that's very surprising behavior, to the point where it feels like a bug to me, although I suspect it was intentional.  If you agree, consider opening a bug with the ruby core team to see if they'll change it.
In the mean time, you can work around this by changing your expectation like so:
expect(w).not_to have_attributes(date: an_object_eq_to(DateTime.new(2017, 9, 22, 15, 30, 15)))

By wrapping it in an_object_eq_to (an alias of the eq matcher, which matches using ==), your ensuring it only matches if the date times are exactly equal using ==, rather than using the more lenient === method.

Thank you, @myronmarston. I agree, this behaviour was really unexpected of DateTime but Ruby documentation specifically mentions the comparison of DateTime using ===. Meanwhile I think I'll gonna use your workaround.


unable to login, using chromium on linux

When trying to view the website using Chromium, on Linux, I only see the throbber.

This is on Chromium version 58.0.3029.96 Built on Ubuntu , running on Ubuntu 16.04 (64-bit).
On this same machine, using Firefox, the website works fine.

Hey @govvin, are you seeing any errors in the browser console?

@ajithranka  Please see attached.
By the way, now I couldn't log-in with Firefox and Chromium
osmlab.github.io-1495532192568.log.txt

This should be fixed after to-fix-backed/issues/96.
@govvin Let me know if you are able to login now.

Yes, that's confirmed.  I noticed that earlier today. Thank you!
However, I couldn't get iD to launch for editing.


Add option to change the repo link image

Right now there is an option to link a git repository by setting the $docsify.repo setting entry, and the link is displayed on a github-corner symbol, but not all repositories are using GitHub - please add an option to specify an image, or select from a pre-defined set of images (github, gitlab, bitbucket, plain git etc.).

You can write CSS as you need.


Needs to show the generic docker-machine icon when there's no specific one.  Users can add arbitrary other drivers, we can't have icons for all of them.

The Generic image is good.  But can we please use the name of the driver instead of Generic for the text.  It's confusing if you have more than 1.

Version - 2.0 master 3/21
Verified fixed


Should ignore backslash escaping character when extracting from string

The following template, in French, contains a backslash that should be ignored during the extraction:
[title]=" 'C\'est ok' | translate"

Actual extraction:
msgid "C\\'est ok"

Expected:
msgid "C'est ok"

As a french, I really need this too!

The problem comes from the replace method which only replaces the first occurrence of matched string.
This code:
while (matches = regExp.exec(template)) {
	collection = collection.add(matches[2].replace('\\\'', '\''));
}

Should be replaced by this code:
while (matches = regExp.exec(template)) {
	collection = collection.add(matches[2].split('\\\'').join('\''));
}

Can someone fix this (@biesbjerg)?

@BenDevelopment Since I don't have much time at the moment, a PR with a passing test would be most welcome!

@BenDevelopment You correctly identified a problem where only the escaped quote was being replace. I will fix this.
As for @Toub, I can't reproduce your issue. When using your example in a template and running extract, I get the correct output:
Command
ngx-translate-extract -i ./src -o test.po --format pot
test.component.ts
@Component({
	template: `<span [title]=" 'C\'est ok' | translate"</span>`
})
export class TestComponent {
	public constructor(protected _translateService: TranslateService) { }
}

test.po
msgid ""
msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"

msgid "C'est ok"
msgstr ""

Going to close this until more information is provided by @Toub.
@BenDevelopment Your fix has been committed here: https://github.com/biesbjerg/ngx-translate-extract/commit/b2ae17697dc9ebfccbd549ca95bdc0469017ee63