[ 
https://issues.apache.org/jira/browse/BEAM-7154?focusedWorklogId=236473&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-236473
 ]

ASF GitHub Bot logged work on BEAM-7154:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/May/19 18:25
            Start Date: 02/May/19 18:25
    Worklog Time Spent: 10m 
      Work Description: lostluck commented on issue #8462: [BEAM-7154] Updating 
Go SDK errors (Part 2)
URL: https://github.com/apache/beam/pull/8462#issuecomment-488779759
 
 
   That's almost certainly the case, given the whole GoGradle, Versioning, Etc. 
situation the SDK is in. I do not recommend testing with the gradle commands 
locally under the vast majority of cases.
   
   `go test ./...` should cover everything, but otherwise `go build ./...` 
would certainly catch it.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 236473)
    Time Spent: 1h  (was: 50m)

> Switch internal Go SDK error code to use new package
> ----------------------------------------------------
>
>                 Key: BEAM-7154
>                 URL: https://issues.apache.org/jira/browse/BEAM-7154
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-go
>            Reporter: Daniel Oliveira
>            Assignee: Daniel Oliveira
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> I added a new package for errors in the Go SDK: 
> [https://github.com/apache/beam/pull/8369]
> This issue tracks progress on modifying existing error code, which mostly 
> uses fmt.Errorf, to use this new package.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to