[Bug][Bitbucket] Extract Pull Requests fails on microsecond timestamp parsing

[oguzgu]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

After upgrading to v1.0.3-beta9, Bitbucket PR sync fails during the Extract Pull Requests subtask with a time.ParseError.

The issue started occurring after merging PR:

#8668

It seems related to timestamp parsing changes introduced in that PR.

What do you expect to happen

Bitbucket timestamps with microseconds should be parsed correctly.

How to reproduce

Use DevLake v1.0.3-beta9

Configure a Bitbucket datasource (cloud)

Add a Bitbucket repository to a project

From the Dashboard, trigger Sync (or run the pipeline manually)

Anything else

No response

Version

v1.0.3-beta9

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[dosubot]

The Bitbucket PR extraction failure is caused by Go's default time.Time parsing, which doesn't handle microsecond precision timestamps returned by Bitbucket Cloud (e.g., 2025-12-01T12:34:56.123456Z). The extractor currently unmarshals the created_on and updated_on fields directly into time.Time, leading to time.ParseError when microseconds are present.

To fix this, update the BitbucketApiPullRequest struct to use the existing common.Iso8601Time type for these fields instead of time.Time. The Iso8601Time helper provides flexible ISO8601 parsing and can be easily extended to support microseconds by adding a matcher/format for six-digit fractional seconds (or by falling back to time.RFC3339Nano) source.

In summary: replace

BitbucketCreatedAt time.Time `json:"created_on"`
BitbucketUpdatedAt time.Time `json:"updated_on"`

with

BitbucketCreatedAt *common.Iso8601Time `json:"created_on"`
BitbucketUpdatedAt *common.Iso8601Time `json:"updated_on"`

and update downstream usage to call .ToNullableTime() or .ToTime() as needed. This will make the extractor robust to all ISO8601 timestamp variants Bitbucket emits, including those with microseconds source.

If you encounter any timestamp formats not currently handled, you can add a new regex/format pair to the DateTimeFormats list in iso8601time.go for full coverage.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[EmyysJanaK]

@oguzgu Hi, I would like to take this