Add batch-writable PLANNED_ASSET_MATERIALIZATION_FAILURE and PLANNED_ASSET_MATERIALIZATION_SKIPPED events

js_modules/dagster-ui/packages/ui-core/src/runs/LogsRowStructuredContent.tsx

@@ -152,6 +152,8 @@ export const LogsRowStructuredContent = ({node, metadata}: IStructuredContentPro
         />
       );
     case 'AssetMaterializationPlannedEvent':
+    case 'PlannedAssetMaterializationFailureEvent':
+    case 'PlannedAssetMaterializationSkippedEvent':
       return <DefaultContent eventType={eventType} message={node.message} />;
     case 'ObjectStoreOperationEvent':
       return (

js_modules/dagster-ui/packages/ui-core/src/runs/filterLogs.tsx

@@ -6,11 +6,13 @@ import {weakmapMemoize} from '../app/Util';
 
 export function filterLogs(logs: LogsProviderLogs, filter: LogFilter, filterStepKeys: string[]) {
   const filteredNodes = logs.allNodes.filter((node) => {
-    // These events are used to determine which assets a run will materialize and are not intended
+    // These events are used for internal bookkeeping and are not intended
     // to be displayed in the Dagster UI. Pagination is offset based, so we remove these logs client-side.
     if (
       node.__typename === 'AssetMaterializationPlannedEvent' ||
-      node.__typename === 'AssetCheckEvaluationPlannedEvent'
+      node.__typename === 'AssetCheckEvaluationPlannedEvent' ||
+      node.__typename === 'PlannedAssetMaterializationFailureEvent' ||
+      node.__typename === 'PlannedAssetMaterializationSkippedEvent'
     ) {
       return false;
     }