Hi all -- As you're aware from recent working group calls we need to develop a mechanism whereby the service configurations can be easily overridden to use Redis for the upcoming Edinburgh release. In

Hi all -- During today's Core Working Group call as we were discussing various ways for export-distro / app-functions-sdk to notify core-data that an event had been successfully handled, I believe Eri

Just to update everyone on the thread, I just talked with Tony and we’re on the same page. We will be taking the reflection-based approach with the IsValidated() check for complex types. Trevor

We’re talking in circles now. If you want to have a call, let me know but I have to start working on this. Trevor

Hi Tony – An issue with the sample code in your branch is that Addressable must make a call to a.Validate() on line 179 instead of returning nil. This is because there are other endpoints that take an

Thanks for providing that summary Tony. I've been working on incorporating the "is validated" discussion from this morning into the feature branches below. There's a problem in that we have types that

Another update on this – This week in the #core channel on Slack Ian Johnson asked me why the approach below didn’t involve creating a Validator interface and using reflection to go through the member

Hi all -- I wanted to follow up on this discussion we've been having in the Core Working Group about validating our contract models and where that responsibility lies. This past week we talked about t

Well, we kind of have a method like that already. https://github.com/edgexfoundry/go-mod-core-contracts/blob/4425df9b51ed055c673fdafb1a97590b6cd0f324/models/operatingstate.go#L53 Again, the problem is

I think my hunch on #1 is correct. If I alter the request JSON to include an empty OperatingState, I can step into the unmarshalling of the type now and receive the error I’m looking for. {"_class":"o

Lenny – Yes, it does appear that is the mechanism preventing the UnmarshalJSON from being called. But I have two follow ups: Why does it work when calling Marshal()? I suspect it’s because there isn’t

We may be moving towards a better solution with Ian’s suggestion. I have created a follow up branch here: https://github.com/tsconn23/go-mod-core-contracts/tree/marshal_bug_ian Only the contracts requ

Hi Ian – See below in blue Trevor From: Ian Johnson <ian.johnson@canonical.com> Sent: Thursday, March 7, 2019 5:04 PM To: Conn, Trevor Cc: edgex-tsc-core@lists.edgexfoundry.org; EdgeX-GoLang@lists.edg

Whoops – It’s always good to commit one’s changes, not simply add them. They’re there now. Thanks for the catch, Lenny. Trevor

Hi all – I’m sending this email out as a follow up to today’s Core WG call. The recording of the call can be found on the wiki page and discussion pertinent to this topic starts at about the 30 minute

Hi all -- I'm going to piggy back on the thread below and loop in the Go email distro for more discussion about modules. I've attached a V2 of the previous document that was sent. It includes two more

Dell Customer Communication “In short, it is long past time to add versions to the working vocabulary of both Go developers and our tools, and this proposal describes a way to do that.” https://github

OK, I see. I will try this for the next feature I take on. Thanks. Trevor Conn Senior Principal Software Engineer Dell Technologies | IoT DellTech Trevor_Conn@Dell.com Round Rock, TX USA _____________

Dell Customer Communication There’s been a lot of talk recently around how we manage commits and commit messages in GitHub to make the history more clean. While in Portland earlier this week, I descri

Dell Customer Communication Taking the Docker/Moby tree as an example, if you look in "pkg" you'll find packages used throughout the application that don't contain any of the primary functionality of