Feature: Llava executor #609
Merged
Annotations
11 warnings
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Build:
LLama/Common/PolymorphicJSONConverter.cs#L51
Dereference of a possibly null reference.
|
|
Build:
LLama/ChatSession.cs#L777
Possible null reference argument for parameter 'executorState' in 'SessionState.SessionState(State? contextState, ExecutorBaseState executorState, ChatHistory history, List<ITextTransform> inputTransformPipeline, ITextStreamTransform outputTransform, IHistoryTransform historyTransform)'.
|
|
Build:
LLama/LLamaInstructExecutor.cs#L109
Possible null reference argument for parameter 'data' in 'Task InstructExecutor.LoadState(ExecutorBaseState data)'.
|
|
Build:
LLama/LLamaExecutorBase.cs#L416
Non-nullable property 'Embeds' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build:
LLama/LLamaExecutorBase.cs#L419
Non-nullable property 'EmbedInps' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build:
LLama/LLamaExecutorBase.cs#L422
Non-nullable property 'SessionTokens' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build:
LLama/LLamaExecutorBase.cs#L425
Non-nullable property 'LastTokens' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build:
LLama/LLamaInteractExecutor.cs#L103
Possible null reference argument for parameter 'data' in 'Task InteractiveExecutor.LoadState(ExecutorBaseState data)'.
|
|
Build:
LLama/LLamaInstructExecutor.cs#L154
'IReadOnlyListExtensions.TokensEndsWithAnyString<TTokens>(TTokens, IList<string>?, SafeLlamaModelHandle, Encoding)' is obsolete: 'Use an Antiprompt processor instead'
|
|
Build:
LLama/LLamaInstructExecutor.cs#L150
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Loading