Skip to content

"Hover Context Menu: Hover over any of your messages to reveal a ... … #35

"Hover Context Menu: Hover over any of your messages to reveal a ... …

"Hover Context Menu: Hover over any of your messages to reveal a ... … #35

Triggered via push June 1, 2026 00:42
Status Failure
Total duration 24s
Artifacts
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 11 warnings
build
Process completed with exit code 1.
build: InnoTrack.Application/Services/ChatService.cs#L218
'IGenericRepository<ChatMessageReaction>' does not contain a definition for 'DeleteAsync' and no accessible extension method 'DeleteAsync' accepting a first argument of type 'IGenericRepository<ChatMessageReaction>' could be found (are you missing a using directive or an assembly reference?)
build: InnoTrack.Application/Services/ChatService.cs#L207
'IGenericRepository<ChatMessage>' does not contain a definition for 'UpdateAsync' and no accessible extension method 'UpdateAsync' accepting a first argument of type 'IGenericRepository<ChatMessage>' could be found (are you missing a using directive or an assembly reference?)
build: InnoTrack.Application/Services/ChatService.cs#L185
'IGenericRepository<ChatMessage>' does not contain a definition for 'UpdateAsync' and no accessible extension method 'UpdateAsync' accepting a first argument of type 'IGenericRepository<ChatMessage>' could be found (are you missing a using directive or an assembly reference?)
build: InnoTrack.Application/Services/ChatService.cs#L171
'IGenericRepository<ChatMessage>' does not contain a definition for 'UpdateAsync' and no accessible extension method 'UpdateAsync' accepting a first argument of type 'IGenericRepository<ChatMessage>' could be found (are you missing a using directive or an assembly reference?)
build: InnoTrack.Application/Services/ChatService.cs#L218
'IGenericRepository<ChatMessageReaction>' does not contain a definition for 'DeleteAsync' and no accessible extension method 'DeleteAsync' accepting a first argument of type 'IGenericRepository<ChatMessageReaction>' could be found (are you missing a using directive or an assembly reference?)
build: InnoTrack.Application/Services/ChatService.cs#L207
'IGenericRepository<ChatMessage>' does not contain a definition for 'UpdateAsync' and no accessible extension method 'UpdateAsync' accepting a first argument of type 'IGenericRepository<ChatMessage>' could be found (are you missing a using directive or an assembly reference?)
build: InnoTrack.Application/Services/ChatService.cs#L185
'IGenericRepository<ChatMessage>' does not contain a definition for 'UpdateAsync' and no accessible extension method 'UpdateAsync' accepting a first argument of type 'IGenericRepository<ChatMessage>' could be found (are you missing a using directive or an assembly reference?)
build: InnoTrack.Application/Services/ChatService.cs#L171
'IGenericRepository<ChatMessage>' does not contain a definition for 'UpdateAsync' and no accessible extension method 'UpdateAsync' accepting a first argument of type 'IGenericRepository<ChatMessage>' could be found (are you missing a using directive or an assembly reference?)
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build: InnoTrack.Domain/Entities/AuditLog.cs#L7
Non-nullable property 'Action' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build: InnoTrack.Domain/Entities/Team.cs#L13
Non-nullable property 'JoinCode' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build: InnoTrack.Domain/Entities/Team.cs#L10
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build: InnoTrack.Domain/Entities/TeamMember.cs#L16
Non-nullable property 'Student' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build: InnoTrack.Domain/Entities/TeamMember.cs#L12
Non-nullable property 'Team' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build: InnoTrack.Domain/Entities/Technology.cs#L10
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build: InnoTrack.Domain/Entities/User.cs#L19
Non-nullable property 'LastName' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build: InnoTrack.Domain/Entities/User.cs#L17
Non-nullable property 'FirstName' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build: InnoTrack.Domain/Entities/User.cs#L14
Non-nullable property 'PasswordHash' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
build: InnoTrack.Domain/Entities/User.cs#L11
Non-nullable property 'Email' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.