aviwarner opened a new issue, #8208:
URL: https://github.com/apache/incubator-devlake/issues/8208

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   Data too long for column 'component' error while collecting/processing data. 
I have seen some similar issues, but in this case, the data type doesn't seem 
to be a 
   
   I checked the db and in the `_tool_jira_issues` table found a `components` 
field where the data type is `text` (doesn't appear to be a character limited 
field). Not exactly sure how I might track down the offending jira issue for 
further troubleshooting. 
   
   Interestingly, my first collection ran fine. Only subsequent ones have had 
this error.
   
   Attempted to upgrade to latest version, also deleted and recreated the 
project and connection without change.
   
   ```
   attached stack trace -- stack trace: | 
github.com/apache/incubator-devlake/server/services.runPipeline | 
/app/server/services/pipeline_runner.go:79 | [...repeated from below...] Wraps: 
(2) Error running pipeline 18. Wraps: (3) attached stack trace -- stack trace: 
| github.com/apache/incubator-devlake/server/services.RunTasksStandalone | 
/app/server/services/task.go:217 | 
github.com/apache/incubator-devlake/server/services.(*pipelineRunner).runPipelineStandalone.func1
 | /app/server/services/pipeline_runner.go:42 | 
github.com/apache/incubator-devlake/core/runner.runPipelineTasks | 
/app/core/runner/run_pipeline.go:90 | 
github.com/apache/incubator-devlake/core/runner.RunPipeline | 
/app/core/runner/run_pipeline.go:54 | 
github.com/apache/incubator-devlake/server/services.(*pipelineRunner).runPipelineStandalone
 | /app/server/services/pipeline_runner.go:38 | 
github.com/apache/incubator-devlake/server/services.runPipeline | 
/app/server/services/pipeline_runner.go:76 | github.com/apache/inc
 ubator-devlake/server/services.RunPipelineInQueue.func1 | 
/app/server/services/pipeline.go:349 | runtime.goexit | 
/usr/local/go/src/runtime/asm_arm64.s:1172 Wraps: (4) attached stack trace | -- 
stack trace: | | 
github.com/apache/incubator-devlake/server/services.RunTasksStandalone.func1 | 
| /app/server/services/task.go:189 | Wraps: (2) Error running task 223. | 
Wraps: (3) attached stack trace | -- stack trace: | | 
github.com/apache/incubator-devlake/core/runner.RunPluginSubTasks | | 
/app/core/runner/run_task.go:333 | | 
github.com/apache/incubator-devlake/core/runner.RunPluginTask | | 
/app/core/runner/run_task.go:165 | | 
github.com/apache/incubator-devlake/core/runner.RunTask | | 
/app/core/runner/run_task.go:139 | | 
github.com/apache/incubator-devlake/server/services.runTaskStandalone | | 
/app/server/services/task_runner.go:114 | | 
github.com/apache/incubator-devlake/server/services.RunTasksStandalone.func1 | 
| /app/server/services/task.go:187 | Wraps: (4) subtask convertIssues ended
  unexpectedly | Wraps: (5) attached stack trace | -- stack trace: | | 
github.com/apache/incubator-devlake/helpers/pluginhelper/api.(*StatefulDataConverter[...]).Execute
 | | /app/helpers/pluginhelper/api/data_convertor_stateful.go:184 | | 
[...repeated from below...] | Wraps: (6) error adding result to batch (500) | 
Wraps: (7) attached stack trace | -- stack trace: | | 
github.com/apache/incubator-devlake/impls/dalgorm.(*Dalgorm).convertGormError | 
| /app/impls/dalgorm/dalgorm.go:547 | | 
github.com/apache/incubator-devlake/impls/dalgorm.(*Dalgorm).CreateOrUpdate | | 
/app/impls/dalgorm/dalgorm.go:265 | | 
github.com/apache/incubator-devlake/helpers/pluginhelper/api.(*BatchSave).flushWithoutLocking
 | | /app/helpers/pluginhelper/api/batch_save.go:131 | | 
github.com/apache/incubator-devlake/helpers/pluginhelper/api.(*BatchSave).Add | 
| /app/helpers/pluginhelper/api/batch_save.go:109 | | 
github.com/apache/incubator-devlake/helpers/pluginhelper/api.(*StatefulDataConverter[...]).Execute
 | | /a
 pp/helpers/pluginhelper/api/data_convertor_stateful.go:182 | | 
github.com/apache/incubator-devlake/plugins/jira/tasks.ConvertIssues | | 
/app/plugins/jira/tasks/issue_convertor.go:164 | | 
github.com/apache/incubator-devlake/core/runner.runSubtask | | 
/app/core/runner/run_task.go:425 | | 
github.com/apache/incubator-devlake/core/runner.RunPluginSubTasks | | 
/app/core/runner/run_task.go:330 | | 
github.com/apache/incubator-devlake/core/runner.RunPluginTask | | 
/app/core/runner/run_task.go:165 | | 
github.com/apache/incubator-devlake/core/runner.RunTask | | 
/app/core/runner/run_task.go:139 | | 
github.com/apache/incubator-devlake/server/services.runTaskStandalone | | 
/app/server/services/task_runner.go:114 | | 
github.com/apache/incubator-devlake/server/services.RunTasksStandalone.func1 | 
| /app/server/services/task.go:187 | | runtime.goexit | | 
/usr/local/go/src/runtime/asm_arm64.s:1172 | Wraps: (8) Error 1406 (22001): 
Data too long for column 'component' at row 174 (500) | Wraps: (9) Error
  1406 (22001): Data too long for column 'component' at row 174 | Error types: 
(1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) 
*errutil.withPrefix (5) *withstack.withStack (6) *errutil.withPrefix (7) 
*withstack.withStack (8) *errutil.withPrefix (9) *mysql.MySQLError Error types: 
(1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) 
*errutil.leafError
   ```
   
   ### What do you expect to happen
   
   For the collection to run appropriately without error. 
   
   ### How to reproduce
   
   Create a Jira connection with, I assume, very long component names 
associated with some issues. 
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   v1.0.2-beta5
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to