url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://docs.aws.amazon.com/fr_fr/lambda/latest/dg/durable-getting-started.html | Création de fonctions Lambda durables - AWS Lambda Création de fonctions Lambda durables - AWS Lambda Documentation AWS Lambda Guide du développeur Conditions préalables Créez une fonction durable Invoquez la fonction durable Nettoyage Étapes suivantes Les traductions sont fournies par des outils de traduction automatique. En cas de conflit entre le contenu d'une traduction et celui de la version originale en anglais, la version anglaise prévaudra. Création de fonctions Lambda durables Pour commencer à utiliser les fonctions durables Lambda, utilisez la console Lambda pour créer une fonction durable. En quelques minutes, vous pouvez créer et déployer une fonction durable qui utilise des étapes et des temps d'attente pour démontrer une exécution basée sur des points de contrôle. Au cours de ce didacticiel, vous découvrirez les concepts fondamentaux des fonctions durables, tels que la façon d'utiliser l' DurableContext objet, de créer des points de contrôle avec des étapes et de suspendre l'exécution avec des temps d'attente. Vous découvrirez également comment fonctionne le replay lorsque votre fonction reprend après une attente. Pour simplifier les choses, vous devez créer votre fonction à l'aide de l'exécution Python ou Node.js. Avec ces langages interprétés, vous pouvez modifier le code de fonction directement dans l'éditeur de code intégré à la console. Astuce Pour apprendre à créer des solutions sans serveur , consultez le Guide du développeur sans serveur . Conditions préalables Si vous n'en avez pas Compte AWS, procédez comme suit pour en créer un. Pour vous inscrire à un Compte AWS Ouvrez l' https://portal.aws.amazon.com/billing/inscription. Suivez les instructions en ligne. Dans le cadre de la procédure d’inscription, vous recevrez un appel téléphonique ou un SMS et vous saisirez un code de vérification en utilisant le clavier numérique du téléphone. Lorsque vous vous inscrivez à un Compte AWS, un Utilisateur racine d'un compte AWS est créé. Par défaut, seul l’utilisateur racine a accès à l’ensemble des Services AWS et des ressources de ce compte. La meilleure pratique de sécurité consiste à attribuer un accès administratif à un utilisateur, et à utiliser uniquement l’utilisateur racine pour effectuer les tâches nécessitant un accès utilisateur racine . AWS vous envoie un e-mail de confirmation une fois le processus d'inscription terminé. À tout moment, vous pouvez consulter l'activité actuelle de votre compte et gérer votre compte en accédant à https://aws.amazon.com/ et en choisissant Mon compte . Après vous être inscrit à un Compte AWS, sécurisez Utilisateur racine d'un compte AWS AWS IAM Identity Center, activez et créez un utilisateur administratif afin de ne pas utiliser l'utilisateur root pour les tâches quotidiennes. Sécurisez votre Utilisateur racine d'un compte AWS Connectez-vous en AWS Management Console tant que propriétaire du compte en choisissant Utilisateur root et en saisissant votre adresse Compte AWS e-mail. Sur la page suivante, saisissez votre mot de passe. Pour obtenir de l’aide pour vous connecter en utilisant l’utilisateur racine, consultez Connexion en tant qu’utilisateur racine dans le Guide de l’utilisateur Connexion à AWS . Activez l’authentification multifactorielle (MFA) pour votre utilisateur racine. Pour obtenir des instructions, voir Activer un périphérique MFA virtuel pour votre utilisateur Compte AWS root (console) dans le guide de l'utilisateur IAM . Création d’un utilisateur doté d’un accès administratif Activez IAM Identity Center. Pour obtenir des instructions, consultez Activation d’ AWS IAM Identity Center dans le Guide de l’utilisateur AWS IAM Identity Center . Dans IAM Identity Center, octroyez un accès administratif à un utilisateur. Pour un didacticiel sur l'utilisation du Répertoire IAM Identity Center comme source d'identité, voir Configurer l'accès utilisateur par défaut Répertoire IAM Identity Center dans le Guide de AWS IAM Identity Center l'utilisateur . Connexion en tant qu’utilisateur doté d’un accès administratif Pour vous connecter avec votre utilisateur IAM Identity Center, utilisez l’URL de connexion qui a été envoyée à votre adresse e-mail lorsque vous avez créé l’utilisateur IAM Identity Center. Pour obtenir de l'aide pour vous connecter en utilisant un utilisateur d'IAM Identity Center, consultez la section Connexion au portail AWS d'accès dans le guide de l'Connexion à AWS utilisateur . Attribution d’un accès à d’autres utilisateurs Dans IAM Identity Center, créez un ensemble d’autorisations qui respecte la bonne pratique consistant à appliquer les autorisations de moindre privilège. Pour obtenir des instructions, consultez Création d’un ensemble d’autorisations dans le Guide de l’utilisateur AWS IAM Identity Center . Attribuez des utilisateurs à un groupe, puis attribuez un accès par authentification unique au groupe. Pour obtenir des instructions, consultez Ajout de groupes dans le Guide de l’utilisateur AWS IAM Identity Center . Créez une fonction Lambda durable avec la console Dans cet exemple, votre fonction durable traite une commande en plusieurs étapes avec un point de contrôle automatique. La fonction prend un objet JSON contenant un numéro de commande, valide la commande, traite le paiement et confirme la commande. Chaque étape est automatiquement contrôlée. Ainsi, si la fonction est interrompue, elle reprend à partir de la dernière étape terminée. Votre fonction illustre également une opération d'attente, interrompant l'exécution pendant une courte période pour simuler l'attente d'une confirmation externe. Pour créer une fonction durable avec la console Ouvrez la page Functions (Fonctions) de la console Lambda. Choisissez Créer une fonction . Sélectionnez Créer à partir de zéro . Dans le volet Informations de base , pour Nom de la fonction , saisissez myDurableFunction . Pour Runtime , choisissez Node.js 24 ou Python 3.14 . Sélectionnez Activer l'exécution durable . Lambda crée votre fonction durable avec un rôle d'exécution qui inclut des autorisations pour les opérations de point de contrôle ( lambda:CheckpointDurableExecutions et). lambda:GetDurableExecutionState Note Les environnements d'exécution Lambda incluent le SDK Durable Execution, qui vous permet de tester des fonctions durables sans créer de dépendances. Toutefois, nous vous recommandons d'inclure le SDK dans votre package de déploiement pour la production. Cela garantit la cohérence des versions et évite les mises à jour d'exécution potentielles susceptibles d'affecter votre fonction. Utilisez l'éditeur de code intégré à la console pour ajouter votre code de fonction durable. Node.js Pour modifier le code dans la console Cliquez sur l’onglet Code . Dans l'éditeur de code intégré de la console, vous devriez voir le code de fonction créé par Lambda. Si vous ne voyez pas l'onglet index.mjs dans l'éditeur de code, sélectionnez index.mjs dans l'explorateur de fichiers, comme le montre le schéma suivant. Collez le code suivant dans l'onglet index.mjs , en remplaçant le code créé par Lambda. import { DurableContext, withDurableExecution, } from "@aws/durable-execution-sdk-js"; export const handler = withDurableExecution( async (event, context) => { const orderId = event.orderId; // Step 1: Validate order const validationResult = await context.step(async (stepContext) => { stepContext.logger.info(`Validating order $ { orderId}`); return { orderId, status: "validated" }; }); // Step 2: Process payment const paymentResult = await context.step(async (stepContext) => { stepContext.logger.info(`Processing payment for order $ { orderId}`); return { orderId, status: "paid", amount: 99.99 }; }); // Wait for 10 seconds to simulate external confirmation await context.wait( { seconds: 10 }); // Step 3: Confirm order const confirmationResult = await context.step(async (stepContext) => { stepContext.logger.info(`Confirming order $ { orderId}`); return { orderId, status: "confirmed" }; }); return { orderId: orderId, status: "completed", steps: [validationResult, paymentResult, confirmationResult] }; } ); Dans la section DÉPLOYER , choisissez Déployer pour mettre à jour le code de votre fonction : Comprendre votre code de fonction durable Avant de passer à l'étape suivante, examinons le code de la fonction et comprenons les principaux concepts relatifs aux fonctions durables. L' withDurableExecution emballage : Votre fonction durable est emballée avec withDurableExecution . Ce wrapper permet une exécution durable en fournissant l' DurableContext objet et en gérant les opérations des points de contrôle. L' DurableContext objet : Au lieu du contexte Lambda standard, votre fonction reçoit un. DurableContext Cet objet fournit des méthodes pour des opérations durables telles wait() que step() et qui créent des points de contrôle. Étapes et points de contrôle : Chaque context.step() appel crée un point de contrôle avant et après l'exécution. Si votre fonction est interrompue, elle reprend à partir du dernier point de contrôle terminé. La fonction ne réexécute pas les étapes terminées. Il utilise plutôt leurs résultats enregistrés. Opérations d'attente : L' context.wait() appel interrompt l'exécution sans consommer de ressources informatiques. Une fois l'attente terminée, Lambda appelle à nouveau votre fonction et rejoue le journal des points de contrôle, en substituant des valeurs stockées aux étapes terminées. Mécanisme de rediffusion : Lorsque votre fonction reprend après une attente ou une interruption, Lambda exécute votre code depuis le début. Toutefois, les étapes terminées ne sont pas réexécutées. Lambda rejoue leurs résultats à partir du journal des points de contrôle. C'est pourquoi votre code doit être déterministe. Python Pour modifier le code dans la console Cliquez sur l’onglet Code . Dans l'éditeur de code intégré de la console, vous devriez voir le code de fonction créé par Lambda. Si vous ne voyez pas l'onglet lambda_function.py dans l'éditeur de code, sélectionnez lambda_function.py dans l'explorateur de fichiers, comme le montre le schéma suivant. Collez le code suivant dans l'onglet lambda_function.py , en remplaçant le code créé par Lambda. from aws_durable_execution_sdk_python import ( DurableContext, durable_execution, durable_step, ) from aws_durable_execution_sdk_python.config import Duration @durable_step def validate_order(step_context, order_id): step_context.logger.info(f"Validating order { order_id}") return { "orderId": order_id, "status": "validated"} @durable_step def process_payment(step_context, order_id): step_context.logger.info(f"Processing payment for order { order_id}") return { "orderId": order_id, "status": "paid", "amount": 99.99} @durable_step def confirm_order(step_context, order_id): step_context.logger.info(f"Confirming order { order_id}") return { "orderId": order_id, "status": "confirmed"} @durable_execution def lambda_handler(event, context: DurableContext): order_id = event['orderId'] # Step 1: Validate order validation_result = context.step(validate_order(order_id)) # Step 2: Process payment payment_result = context.step(process_payment(order_id)) # Wait for 10 seconds to simulate external confirmation context.wait(Duration.from_seconds(10)) # Step 3: Confirm order confirmation_result = context.step(confirm_order(order_id)) return { "orderId": order_id, "status": "completed", "steps": [validation_result, payment_result, confirmation_result] } Dans la section DÉPLOYER , choisissez Déployer pour mettre à jour le code de votre fonction : Comprendre votre code de fonction durable Avant de passer à l'étape suivante, examinons le code de la fonction et comprenons les principaux concepts relatifs aux fonctions durables. Le @durable_execution décorateur : Votre fonction de gestion est décorée avec @durable_execution . Ce décorateur permet une exécution durable en fournissant l' DurableContext objet et en gérant les opérations aux points de contrôle. Le @durable_step décorateur : Chaque fonction de marche est décorée avec @durable_step . Ce décorateur définit la fonction comme une étape durable qui crée des points de contrôle. L' DurableContext objet : Au lieu du contexte Lambda standard, votre fonction reçoit un. DurableContext Cet objet fournit des méthodes pour des opérations durables telles wait() que step() et qui créent des points de contrôle. Étapes et points de contrôle : Chaque context.step() appel crée un point de contrôle avant et après l'exécution. Si votre fonction est interrompue, elle reprend à partir du dernier point de contrôle terminé. La fonction ne réexécute pas les étapes terminées. Il utilise plutôt leurs résultats enregistrés. Opérations d'attente : L' context.wait() appel interrompt l'exécution sans consommer de ressources informatiques. Une fois l'attente terminée, Lambda appelle à nouveau votre fonction et rejoue le journal des points de contrôle, en substituant des valeurs stockées aux étapes terminées. Le SDK Python est synchrone : Notez que le SDK Python n'utilise await pas. Toutes les opérations durables sont des appels de méthode synchrones. Invoquez la fonction durable à l'aide de l'éditeur de code de la console Les fonctions durables nécessitent un ARN qualifié pour l'invocation. Avant de pouvoir invoquer votre fonction durable, publiez une version. Pour publier une version de votre fonction Choisissez l'onglet Versions . Choisissez Publish new version (Publier une nouvelle version) . Dans le champ Description de la version , entrez Initial version (facultatif). Choisissez Publier . Lambda crée la version 1 de votre fonction. Notez que la fonction ARN inclut désormais :1 à la fin, ce qui indique qu'il s'agit de la version 1. Créez maintenant un événement de test à envoyer à votre fonction. L'événement est un document au format JSON contenant un numéro de commande. Pour créer l'événement de test Dans la section ÉVÉNEMENTS DE TEST de l’éditeur de code de console, choisissez Créer un événement de test . Dans Event Name (Nom de l'événement) , saisissez myTestEvent . Dans la section JSON d’événement , remplacez le JSON par défaut par ce qui suit : { "orderId": "order-12345" } Choisissez Enregistrer . Pour tester votre fonctionnalité durable et en voir l'exécution Dans la section ÉVÉNEMENTS DE TEST de l’éditeur de code de la console, cliquez sur l’icône d’exécution à côté de votre événement de test : Votre fonction durable commence à s'exécuter. Comme il inclut une attente de 10 secondes, l'appel initial se termine rapidement et la fonction reprend après la période d'attente. Vous pouvez consulter la progression de l'exécution dans l'onglet Exécutions durables . Pour visualiser l'exécution durable de vos fonctions Choisissez l'onglet Exécutions durables . Trouvez votre exécution dans la liste. L'exécution indique l'état actuel (en cours, réussi ou échec). Choisissez l'ID d'exécution pour afficher les détails, notamment : Chronologie d'exécution indiquant la date à laquelle chaque étape est terminée Historique des points de contrôle Périodes d'attente Résultats des étapes Vous pouvez également consulter les journaux de votre fonction dans CloudWatch Logs pour voir le résultat de chaque étape de la console. Pour consulter les enregistrements d'invocation de votre fonction dans Logs CloudWatch Ouvrez la page Groupes de journaux de la CloudWatch console. Choisissez le groupe de journaux de votre fonction ( /aws/lambda/myDurableFunction ). Faites défiler la page vers le bas et choisissez le flux de journaux pour les invocations de fonctions que vous souhaitez consulter. Vous devriez voir des entrées de journal pour chaque appel de votre fonction, y compris l'exécution initiale et la rediffusion après l'attente. Nettoyage Lorsque vous avez fini d'utiliser l'exemple de fonction durable, supprimez-le. Vous pouvez également supprimer le groupe de journaux qui stocke les journaux de la fonction, et le rôle d'exécution créé par la console. Pour supprimer la fonction Lambda Ouvrez la page Functions (Fonctions) de la console Lambda. Sélectionnez la fonction que vous avez créée. Sélectionnez Actions , Supprimer . Saisissez confirm dans la zone de saisie de texte et choisissez Delete (Supprimer). Pour supprimer le groupe de journaux Ouvrez la page Log groups (Groupes de journaux) de la console CloudWatch. Sélectionnez le groupe de journaux de la fonction ( /aws/lambda/myDurableFunction ). Sélectionnez Actions , Delete log group(s) (Supprimer le ou les groupes de journaux) . Dans la boîte de dialogue Delete log group(s) (Supprimer le ou les groupes de journaux) , sélectionnez Delete (Supprimer) . Pour supprimer le rôle d'exécution Ouvrez la page Rôles de la console Gestion des identités et des accès AWS (IAM). Sélectionnez le rôle d'exécution de la fonction (par exemple, myDurableFunction-role- 31exxmpl ). Sélectionnez Delete (Supprimer) . Dans la fenêtre de dialogue Supprimer le rôle , saisissez le nom du rôle, puis sélectionnez Supprimer . Ressources supplémentaires et prochaines étapes Maintenant que vous avez créé et testé une fonction simple et durable à l'aide de la console, procédez comme suit : Découvrez les cas d'utilisation courants des fonctions durables, notamment les transactions distribuées, le traitement des commandes et les flux de travail de révision humaine. Voir les exemples . Découvrez comment surveiller les exécutions de fonctions durables à l'aide de CloudWatch métriques et d'un historique d'exécution. Consultez la section Surveillance et débogage . Découvrez comment invoquer des fonctions durables de manière synchrone et asynchrone, et comment gérer les exécutions de longue durée. Voir Invocation de fonctions durables. Suivez les meilleures pratiques en matière de rédaction de code déterministe, de gestion de la taille des points de contrôle et d'optimisation des coûts. Consultez la section Bonnes pratiques . Découvrez comment tester des fonctions durables localement et dans le cloud. Voir Tester des fonctions durables . JavaScript est désactivé ou n'est pas disponible dans votre navigateur. Pour que vous puissiez utiliser la documentation AWS, Javascript doit être activé. Vous trouverez des instructions sur les pages d'aide de votre navigateur. Conventions de rédaction Concepts de base En utilisant AWS CLI Cette page vous a-t-elle été utile ? - Oui Merci de nous avoir fait part de votre satisfaction. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer ce qui vous a plu afin que nous puissions nous améliorer davantage. Cette page vous a-t-elle été utile ? - Non Merci de nous avoir avertis que cette page avait besoin d'être retravaillée. Nous sommes désolés de ne pas avoir répondu à vos attentes. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer comment nous pourrions améliorer cette documentation. | 2026-01-13T09:29:29 |
https://docs.aws.amazon.com/zh_tw/lambda/latest/dg/durable-getting-started.html | 建立 Lambda 耐用函數 - AWS Lambda 建立 Lambda 耐用函數 - AWS Lambda 文件 AWS Lambda 開發人員指南 先決條件 建立耐用的 函數 叫用耐用的 函數 清除 後續步驟 本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。 建立 Lambda 耐用函數 若要開始使用 Lambda 耐用函數，請使用 Lambda 主控台建立耐用函數。在幾分鐘內，您可以建立和部署耐久的 函數，該函數使用步驟 並等待示範檢查點型執行。 執行教學課程時，您將學習基本的耐用函數概念，例如如何使用 DurableContext 物件、使用步驟建立檢查點，以及使用等待暫停執行。您也將了解當您的函數在等待後繼續時，重播的運作方式。 為了簡化，您可以使用 Python 或 Node.js 執行期建立函數。您可以使用這些轉譯語言，直接在主控台的內建程式碼編輯器中編輯函數程式碼。 提示 若要了解如何建置 無伺服器解決方案 ，請參閱 無伺服器開發人員指南 。 先決條件 如果您沒有 AWS 帳戶，請完成下列步驟來建立一個。 註冊 AWS 帳戶 開啟 https://portal.aws.amazon.com/billing/signup 。 請遵循線上指示進行。 部分註冊程序需接收來電或簡訊，並在電話鍵盤輸入驗證碼。 當您註冊 時 AWS 帳戶， AWS 帳戶根使用者 會建立 。根使用者有權存取該帳戶中的所有 AWS 服務 和資源。作為安全最佳實務，請將管理存取權指派給使用者，並且僅使用根使用者來執行 需要根使用者存取權的任務 。 AWS 會在註冊程序完成後傳送確認電子郵件給您。您可以隨時登錄 https://aws.amazon.com/ 並選擇 我的帳戶 ，以檢視您目前的帳戶活動並管理帳戶。 註冊 後 AWS 帳戶，請保護 AWS 帳戶根使用者、啟用 AWS IAM Identity Center和建立管理使用者，以免將根使用者用於日常任務。 保護您的 AWS 帳戶根使用者 選擇 根使用者 並輸入 AWS 帳戶 您的電子郵件地址，以帳戶擁有者 AWS 管理主控台 身分登入 。在下一頁中，輸入您的密碼。 如需使用根使用者登入的說明，請參閱 AWS 登入 使用者指南 中的 以根使用者身分登入 。 若要在您的根使用者帳戶上啟用多重要素驗證 (MFA)。 如需說明，請參閱《 IAM 使用者指南 》中的 為您的 AWS 帳戶 根使用者 （主控台） 啟用虛擬 MFA 裝置 。 建立具有管理存取權的使用者 啟用 IAM Identity Center。 如需指示，請參閱《AWS IAM Identity Center 使用者指南》 中的 啟用 AWS IAM Identity Center 。 在 IAM Identity Center 中，將管理存取權授予使用者。 如需使用 IAM Identity Center 目錄 做為身分來源的教學課程，請參閱 AWS IAM Identity Center 《 使用者指南 》中的 使用預設值設定使用者存取權 IAM Identity Center 目錄 。 以具有管理存取權的使用者身分登入 若要使用您的 IAM Identity Center 使用者簽署，請使用建立 IAM Identity Center 使用者時傳送至您電子郵件地址的簽署 URL。 如需使用 IAM Identity Center 使用者登入的說明，請參閱 AWS 登入 《 使用者指南 》中的 登入 AWS 存取入口網站 。 指派存取權給其他使用者 在 IAM Identity Center 中，建立一個許可集來遵循套用最低權限的最佳實務。 如需指示，請參閱《AWS IAM Identity Center 使用者指南》 中的 建立許可集 。 將使用者指派至群組，然後對該群組指派單一登入存取權。 如需指示，請參閱《AWS IAM Identity Center 使用者指南》 中的 新增群組 。 使用主控台建立 Lambda 耐用函數 在此範例中，您的耐用函數會使用自動檢查點處理多個步驟的訂單。函數會取得包含訂單 ID 的 JSON 物件、驗證訂單、處理付款，以及確認訂單。每個步驟都會自動檢查點，因此如果函數中斷，則會從上次完成的步驟繼續執行。 您的函數也會示範等待操作，暫停執行一小段時間以模擬等待外部確認。 使用主控台建立耐用的函數 開啟 Lambda 主控台中的 函數頁面 。 選擇 建立函數 。 選取 從頭開始撰寫 。 在 基本資訊 窗格中，為 函數名稱 輸入 myDurableFunction 。 針對 執行期 ，選擇 Node.js 24 或 Python 3.14。 選取 啟用持久性執行 。 Lambda 會使用包含檢查點操作 ( lambda:CheckpointDurableExecutions 和 ) 許可的 執行角色 來建立您的耐用函數 lambda:GetDurableExecutionState 。 注意 Lambda 執行時間包含耐用的執行 SDK，因此您可以測試耐用的函數，無需封裝相依性。不過，我們建議在部署套件中包含 開發套件以供生產使用。這可確保版本一致性，並避免可能影響函數的潛在執行時間更新。 使用主控台的內建程式碼編輯器來新增您的耐用函數程式碼。 Node.js 若要在主控台中修改程式碼 選擇 程式碼 標籤。 在主控台的內建程式碼編輯器中，您應該會看到 Lambda 建立的函數程式碼。如果您在程式碼編輯器中沒看到 index.mjs 標籤，請在檔案總管中選取 index.mjs ，如下圖所示。 將以下程式碼貼到 index.mjs 標籤中，替換 Lambda 建立的程式碼。 import { DurableContext, withDurableExecution, } from "@aws/durable-execution-sdk-js"; export const handler = withDurableExecution( async (event, context) => { const orderId = event.orderId; // Step 1: Validate order const validationResult = await context.step(async (stepContext) => { stepContext.logger.info(`Validating order $ { orderId}`); return { orderId, status: "validated" }; }); // Step 2: Process payment const paymentResult = await context.step(async (stepContext) => { stepContext.logger.info(`Processing payment for order $ { orderId}`); return { orderId, status: "paid", amount: 99.99 }; }); // Wait for 10 seconds to simulate external confirmation await context.wait( { seconds: 10 }); // Step 3: Confirm order const confirmationResult = await context.step(async (stepContext) => { stepContext.logger.info(`Confirming order $ { orderId}`); return { orderId, status: "confirmed" }; }); return { orderId: orderId, status: "completed", steps: [validationResult, paymentResult, confirmationResult] }; } ); 在 DEPLOY 區段中，選擇 部署 以更新函數的程式碼： 了解您的耐用函數程式碼 在進行下一個步驟之前，讓我們先查看函數程式碼，並了解關鍵的耐久函數概念。 withDurableExecution 包裝函式： 您的耐用函數以 包裝 withDurableExecution 。此包裝函式提供 DurableContext 物件和管理檢查點操作，以啟用持久的執行。 DurableContext 物件： 您的函數會收到 ，而不是標準 Lambda 內容 DurableContext 。此物件提供持久性操作的方法 wait() ，例如建立檢查點的 step() 和 。 步驟和檢查點： 每個 context.step() 呼叫都會在執行前後建立檢查點。如果您的函數中斷，則會從上次完成的檢查點繼續執行。函數不會重新執行完成的步驟。它會改用其儲存的結果。 等待操作： context.wait() 呼叫會暫停執行，而不會耗用運算資源。當等待完成時，Lambda 會再次叫用您的函數，並重播檢查點日誌，以儲存的值取代已完成的步驟。 重播機制： 當您的函數在等待或中斷後繼續時，Lambda 會從頭開始執行您的程式碼。不過，已完成的步驟不會重新執行。Lambda 會從檢查點日誌重播其結果。這就是您的程式碼必須具有決定性的原因。 Python 若要在主控台中修改程式碼 選擇 程式碼 標籤。 在主控台的內建程式碼編輯器中，您應該會看到 Lambda 建立的函數程式碼。如果您在程式碼編輯器中沒看到 lambda_function.py ，請在檔案總管中選取 lambda_function.py ，如下圖所示。 將以下程式碼貼到 lambda_function.py 標籤中，替換 Lambda 建立的程式碼。 from aws_durable_execution_sdk_python import ( DurableContext, durable_execution, durable_step, ) from aws_durable_execution_sdk_python.config import Duration @durable_step def validate_order(step_context, order_id): step_context.logger.info(f"Validating order { order_id}") return { "orderId": order_id, "status": "validated"} @durable_step def process_payment(step_context, order_id): step_context.logger.info(f"Processing payment for order { order_id}") return { "orderId": order_id, "status": "paid", "amount": 99.99} @durable_step def confirm_order(step_context, order_id): step_context.logger.info(f"Confirming order { order_id}") return { "orderId": order_id, "status": "confirmed"} @durable_execution def lambda_handler(event, context: DurableContext): order_id = event['orderId'] # Step 1: Validate order validation_result = context.step(validate_order(order_id)) # Step 2: Process payment payment_result = context.step(process_payment(order_id)) # Wait for 10 seconds to simulate external confirmation context.wait(Duration.from_seconds(10)) # Step 3: Confirm order confirmation_result = context.step(confirm_order(order_id)) return { "orderId": order_id, "status": "completed", "steps": [validation_result, payment_result, confirmation_result] } 在 DEPLOY 區段中，選擇 部署 以更新函數的程式碼： 了解您的耐用函數程式碼 在進行下一個步驟之前，讓我們先查看函數程式碼，並了解關鍵的耐久函數概念。 @durable_execution 裝飾項目： 您的處理常式函數以 裝飾 @durable_execution 。此裝飾項目透過提供 DurableContext 物件和管理檢查點操作來實現持久的執行。 @durable_step 裝飾項目： 每個步驟函數都以 裝飾 @durable_step 。此裝飾項目會將函數標記為建立檢查點的耐久步驟。 DurableContext 物件： 您的函數會收到 ，而不是標準 Lambda 內容 DurableContext 。此物件提供持久性操作的方法 wait() ，例如建立檢查點的 step() 和 。 步驟和檢查點： 每個 context.step() 呼叫都會在執行前後建立檢查點。如果您的函數中斷，則會從上次完成的檢查點繼續執行。函數不會重新執行完成的步驟。它會改用其儲存的結果。 等待操作： context.wait() 呼叫會暫停執行，而不會耗用運算資源。當等待完成時，Lambda 會再次叫用您的函數，並重播檢查點日誌，以儲存的值取代已完成的步驟。 Python SDK 是同步的： 請注意，Python SDK 不使用 await 。所有耐用的操作都是同步方法呼叫。 使用主控台程式碼編輯器叫用耐用函數 耐用的函數需要合格的 ARN 才能叫用。在您可以叫用耐久函數之前，請先發佈版本。 發佈 函數的版本 選擇 版本 索引標籤。 選擇 Publish new version (發佈新版本) 。 針對 版本描述 ，輸入 Initial version （選用）。 選擇 發布 。 Lambda 會建立函數的第 1 版。請注意，函數 ARN 現在 :1 會在結尾包含 ，表示這是第 1 版。 現在建立測試事件以傳送至您的 函數。事件是包含訂單 ID 的 JSON 格式文件。 若要建立測試事件 在主控台程式碼編輯器的 TEST EVENTS 區段中，選擇 建立測試事件 。 Event Name (事件名稱) 輸入 myTestEvent 。 在 事件 JSON 區段中，將預設 JSON 取代為下列項目： { "orderId": "order-12345" } 選擇 儲存 。 測試您的耐用函數並檢視執行 在主控台程式碼編輯器的 TEST EVENTS 區段中，選擇測試事件旁邊的執行圖示： 您的耐用函數會開始執行。因為它包含 10 秒的等待時間，初始調用會快速完成，而且函數會在等待期間之後繼續。您可以在 持久性執行索引標籤中檢視執行 進度。 檢視您的耐久函數執行 選擇 持久性執行 索引標籤。 在清單中尋找您的執行。執行會顯示目前狀態 （執行中、成功或失敗）。 選擇執行 ID 以檢視詳細資訊，包括： 顯示每個步驟完成時間的執行時間表 檢查點歷史記錄 等待期間 步驟結果 您也可以在 CloudWatch Logs 中檢視函數的日誌，以查看每個步驟的主控台輸出。 若要在 CloudWatch Logs 中檢視函數的調用記錄 開啟 CloudWatch 主控台的 日誌群組 頁面。 為函數 ( /aws/lambda/myDurableFunction ) 選擇日誌群組名稱。 向下捲動並選擇要查看的函數調用 日誌串流 。 您應該會看到每次叫用函數的日誌項目，包括初始執行和等待後的重播。 清除 當您完成使用範例耐用函數時，請將其刪除。您還可以刪除存放函數日誌的日誌群組，以及主控台建立的 執行角色 。 若要刪除 Lambda 函數 開啟 Lambda 主控台中的 函數頁面 。 選擇您建立的函數。 選擇 Actions (動作)、 Delete (刪除)。 在文字輸入欄位中輸入 confirm ，然後選擇 刪除 。 刪除日誌群組 開啟 CloudWatch 主控台的 日誌群組 頁面。 選取函數的日誌群組 ( /aws/lambda/myDurableFunction )。 選擇 動作 、 刪除日誌群組 。 在 刪除日誌群組 對話方塊中，選擇 刪除 。 刪除執行角色 開啟 AWS Identity and Access Management (IAM) 主控台的角色 頁面 。 選取函數的執行角色，(例如 myDurableFunction-role- 31exxmpl )。 選擇 刪除 。 在 刪除角色 對話方塊中輸入角色名稱，然後選擇 刪除 。 其他資源和後續步驟 現在您已使用 主控台建立並測試簡單的耐用函數，請採取下列後續步驟： 了解耐用函數的常見使用案例，包括分散式交易、訂單處理和人工審核工作流程。請參閱 範例 。 了解如何使用 CloudWatch 指標和執行歷史記錄監控持久的函數執行。請參閱 監控和偵錯 。 了解如何同步和非同步叫用耐久函數，以及管理長時間執行的執行。請參閱 叫用耐用函數 。 遵循撰寫確定性程式碼、管理檢查點大小和最佳化成本的最佳實務。請參閱 最佳實務 。 了解如何在本機和雲端測試耐用的函數。請參閱 測試耐用函數 。 您的瀏覽器已停用或無法使用 Javascript。 您必須啟用 Javascript，才能使用 AWS 文件。請參閱您的瀏覽器說明頁以取得說明。 文件慣用形式 基本概念 使用 AWS CLI 此頁面是否有幫助？ - 是 感謝您，讓我們知道我們做得很好！ 若您有空，歡迎您告知我們值得讚許的地方，這樣才能保持良好服務。 此頁面是否有幫助？ - 否 感謝讓我們知道此頁面仍須改善。很抱歉，讓您失望。 若您有空，歡迎您提供改善文件的方式。 | 2026-01-13T09:29:29 |
https://democoding.in/codepen-ideas/page/3 | Amazing CodePen Ideas Page no 3 | Demo Coding DemoCoding * Home Series Premium Animation Blogs Codepen Ideas Home /codepen-ideas / Page 3 « 1 ... 2 3 4 ... 7 » Mind Blowing CSS Only Animation in 2023 © 2023 DemoCoding Home Privacy Policy Contact Us | 2026-01-13T09:29:29 |
https://docs.aws.amazon.com/zh_tw/lambda/latest/dg/durable-best-practices.html | Lambda 耐用函數的最佳實務 - AWS Lambda Lambda 耐用函數的最佳實務 - AWS Lambda 文件 AWS Lambda 開發人員指南 寫入確定性程式碼 等冪性的設計 有效率地管理狀態 設計有效的步驟 有效率地使用等待操作 其他考量 其他資源 本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。 Lambda 耐用函數的最佳實務 耐用函數使用重播型執行模型，需要與傳統 Lambda 函數不同的模式。遵循這些最佳實務來建置可靠且符合成本效益的工作流程。 寫入確定性程式碼 在重播期間，您的函數會從頭開始執行，並且必須遵循與原始執行相同的執行路徑。持久性操作之外的程式碼必須具有決定性，在相同的輸入下產生相同的結果。 以步驟包裝非確定性操作： 隨機數產生和 UUIDs 目前時間或時間戳記 外部 API 呼叫和資料庫查詢 檔案系統操作 TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; import { randomUUID } from 'crypto'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Generate transaction ID inside a step const transactionId = await context.step('generate-transaction-id', async () => { return randomUUID(); }); // Use the same ID throughout execution, even during replay const payment = await context.step('process-payment', async () => { return processPayment(event.amount, transactionId); }); return { statusCode: 200, transactionId, payment }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext import uuid @durable_execution def handler(event, context: DurableContext): # Generate transaction ID inside a step transaction_id = context.step( lambda _: str(uuid.uuid4()), name='generate-transaction-id' ) # Use the same ID throughout execution, even during replay payment = context.step( lambda _: process_payment(event['amount'], transaction_id), name='process-payment' ) return { 'statusCode': 200, 'transactionId': transaction_id, 'payment': payment} Important (重要) 請勿使用全域變數或關閉在步驟之間共用狀態。透過傳回值傳遞資料。重播期間全域狀態中斷，因為步驟會傳回快取的結果，但全域變數會重設。 避免關閉變動： 在關閉中擷取的變數可能會在重播期間遺失變動。步驟會傳回快取的結果，但步驟外的變數更新不會重播。 TypeScript // ❌ WRONG: Mutations lost on replay export const handler = withDurableExecution(async (event, context) => { let total = 0; for (const item of items) { await context.step(async () => { total += item.price; // ⚠️ Mutation lost on replay! return saveItem(item); }); } return { total }; // Inconsistent value! }); // ✅ CORRECT: Accumulate with return values export const handler = withDurableExecution(async (event, context) => { let total = 0; for (const item of items) { total = await context.step(async () => { const newTotal = total + item.price; await saveItem(item); return newTotal; // Return updated value }); } return { total }; // Consistent! }); // ✅ EVEN BETTER: Use map for parallel processing export const handler = withDurableExecution(async (event, context) => { const results = await context.map( items, async (ctx, item) => { await ctx.step(async () => saveItem(item)); return item.price; } ); const total = results.getResults().reduce((sum, price) => sum + price, 0); return { total }; }); Python # ❌ WRONG: Mutations lost on replay @durable_execution def handler(event, context: DurableContext): total = 0 for item in items: context.step( lambda _: save_item_and_mutate(item, total), # ⚠️ Mutation lost on replay! name=f'save-item- { item["id"]}' ) return { 'total': total} # Inconsistent value! # ✅ CORRECT: Accumulate with return values @durable_execution def handler(event, context: DurableContext): total = 0 for item in items: total = context.step( lambda _: save_item_and_return_total(item, total), name=f'save-item- { item["id"]}' ) return { 'total': total} # Consistent! # ✅ EVEN BETTER: Use map for parallel processing @durable_execution def handler(event, context: DurableContext): def process_item(ctx, item): ctx.step(lambda _: save_item(item)) return item['price'] results = context.map(items, process_item) total = sum(results.get_results()) return { 'total': total} 等冪性的設計 由於重試或重播，操作可能會執行多次。非等冪性操作會導致重複的副作用，例如向客戶收費兩次或傳送多封電子郵件。 使用等冪符記：在步驟中 產生符記，並將其包含在外部 API 呼叫中，以防止重複操作。 TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Generate idempotency token once const idempotencyToken = await context.step('generate-idempotency-token', async () => { return crypto.randomUUID(); }); // Use token to prevent duplicate charges const charge = await context.step('charge-payment', async () => { return paymentService.charge( { amount: event.amount, cardToken: event.cardToken, idempotencyKey: idempotencyToken }); }); return { statusCode: 200, charge }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext import uuid @durable_execution def handler(event, context: DurableContext): # Generate idempotency token once idempotency_token = context.step( lambda _: str(uuid.uuid4()), name='generate-idempotency-token' ) # Use token to prevent duplicate charges def charge_payment(_): return payment_service.charge( amount=event['amount'], card_token=event['cardToken'], idempotency_key=idempotency_token ) charge = context.step(charge_payment, name='charge-payment') return { 'statusCode': 200, 'charge': charge} 使用at-most-once語意： 對於絕不能重複的關鍵操作 （金融交易、庫存扣除），請設定at-most-once的執行模式。 TypeScript // Critical operation that must not duplicate await context.step('deduct-inventory', async () => { return inventoryService.deduct(event.productId, event.quantity); }, { executionMode: 'AT_MOST_ONCE_PER_RETRY' }); Python # Critical operation that must not duplicate context.step( lambda _: inventory_service.deduct(event['productId'], event['quantity']), name='deduct-inventory', config=StepConfig(execution_mode='AT_MOST_ONCE_PER_RETRY') ) 資料庫冪等性： 使用check-before-write模式、條件更新或 upsert 操作，以防止重複記錄。 有效率地管理狀態 每個檢查點都會將狀態儲存為持久性儲存。大型狀態物件會增加成本、緩慢檢查點和影響效能。僅儲存必要的工作流程協調資料。 保持最小狀態： 存放 IDs和參考，而非完整物件 視需要在步驟內擷取詳細資訊 針對大型資料使用 Amazon S3 或 DynamoDB，以 狀態傳遞參考 避免在步驟之間傳遞大型承載 TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Store only the order ID, not the full order object const orderId = event.orderId; // Fetch data within each step as needed await context.step('validate-order', async () => { const order = await orderService.getOrder(orderId); return validateOrder(order); }); await context.step('process-payment', async () => { const order = await orderService.getOrder(orderId); return processPayment(order); }); return { statusCode: 200, orderId }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext @durable_execution def handler(event, context: DurableContext): # Store only the order ID, not the full order object order_id = event['orderId'] # Fetch data within each step as needed context.step( lambda _: validate_order(order_service.get_order(order_id)), name='validate-order' ) context.step( lambda _: process_payment(order_service.get_order(order_id)), name='process-payment' ) return { 'statusCode': 200, 'orderId': order_id} 設計有效的步驟 步驟是耐用函數中的基本工作單位。精心設計的步驟可讓工作流程更易於理解、偵錯和維護。 步驟設計原則： 使用描述性名稱 - 類似 的名稱， validate-order 而不是 step1 讓日誌和錯誤更容易理解 將 名稱保持靜態 - 請勿將動態名稱與時間戳記或隨機值搭配使用。步驟名稱必須具有決定性才能重播 平衡精細程度 - 將複雜的操作分解為重點步驟，但避免增加檢查點負荷的過小步驟 群組相關操作 - 應該一起成功或失敗的操作屬於同一步驟 有效率地使用等待操作 等待操作會暫停執行，而不會耗用資源或產生成本。使用它們，而不是讓 Lambda 保持執行狀態。 以 時間為基礎的等待： 使用 context.wait() 處理延遲，而非 setTimeout 或 sleep 。 外部回呼： 等待外部系統 context.waitForCallback() 時使用 。一律設定逾時以防止無限期等待。 輪詢： 使用 context.waitForCondition() 搭配指數退避來輪詢外部服務，而不會讓它們過多。 TypeScript // Wait 24 hours without cost await context.wait( { seconds: 86400 }); // Wait for external callback with timeout const result = await context.waitForCallback( 'external-job', async (callbackId) => { await externalService.submitJob( { data: event.data, webhookUrl: `https://api.example.com/callbacks/$ { callbackId}` }); }, { timeout: { seconds: 3600 } } ); Python # Wait 24 hours without cost context.wait(86400) # Wait for external callback with timeout result = context.wait_for_callback( lambda callback_id: external_service.submit_job( data=event['data'], webhook_url=f'https://api.example.com/callbacks/ { callback_id}' ), name='external-job', config=WaitForCallbackConfig(timeout_seconds=3600) ) 其他考量 錯誤處理： 重試暫時性故障，例如網路逾時和速率限制。請勿重試永久失敗，例如無效的輸入或身分驗證錯誤。使用適當的最大嘗試次數和退避率來設定重試策略。如需詳細範例，請參閱 錯誤處理和重試 。 效能： 透過儲存參考而非完整承載，將檢查點大小降至最低。使用 context.parallel() 和 context.map() 同時執行獨立操作。批次相關操作，以減少檢查點額外負荷。 版本控制： 使用版本編號或別名叫用函數，將執行釘選到特定的程式碼版本。確保新的程式碼版本可以處理較舊版本的狀態。請勿重新命名步驟或以中斷重播的方式變更其行為。 序列化： 將 JSON 相容類型用於操作輸入和結果。將日期轉換為 ISO 字串，並將自訂物件轉換為純物件，然後再將其傳遞至持久的操作。 監控： 啟用具有執行 IDs結構化記錄。針對錯誤率和執行持續時間設定 CloudWatch 警示。使用追蹤來識別瓶頸。如需詳細指引，請參閱 監控和偵錯 。 測試： 測試快樂路徑、錯誤處理和重播行為。回呼和等待的測試逾時案例。使用本機測試來縮短反覆運算時間。如需詳細指引，請參閱 測試耐用函數 。 要避免的常見錯誤： 不要巢狀 context.step() 化呼叫，請改用子內容。在步驟中包裝非確定性操作。一律設定回呼的逾時。平衡步驟精細程度與檢查點額外負荷。儲存參考，而不是處於 狀態的大型物件。 其他資源 Python SDK 文件 - 完整的 API 參考、測試模式和進階範例 TypeScript SDK 文件 - 完整的 API 參考、測試模式和進階範例 您的瀏覽器已停用或無法使用 Javascript。 您必須啟用 Javascript，才能使用 AWS 文件。請參閱您的瀏覽器說明頁以取得說明。 文件慣用形式 監控耐用的 函數 Lambda 受管執行個體 此頁面是否有幫助？ - 是 感謝您，讓我們知道我們做得很好！ 若您有空，歡迎您告知我們值得讚許的地方，這樣才能保持良好服務。 此頁面是否有幫助？ - 否 感謝讓我們知道此頁面仍須改善。很抱歉，讓您失望。 若您有空，歡迎您提供改善文件的方式。 | 2026-01-13T09:29:29 |
https://docs.aws.amazon.com/id_id/lambda/latest/dg/workflow-event-management.html | Mengelola alur kerja dan acara Lambda - AWS Lambda Mengelola alur kerja dan acara Lambda - AWS Lambda Dokumentasi AWS Lambda Panduan Developerr Orkestrasi kode pertama dengan fungsi tahan lama Mengatur alur kerja dengan Step Functions Mengelola acara dengan EventBridge dan EventBridge Scheduler Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Mengelola alur kerja dan acara Lambda Saat membuat aplikasi tanpa server dengan Lambda, Anda sering membutuhkan cara untuk mengatur eksekusi fungsi dan menangani peristiwa. AWS menyediakan beberapa pendekatan untuk mengoordinasikan fungsi Lambda: Fungsi Lambda yang tahan lama untuk orkestrasi alur kerja kode pertama dalam Lambda AWS Step Functions untuk orkestrasi alur kerja visual di beberapa layanan Amazon EventBridge Scheduler dan Amazon EventBridge untuk arsitektur dan penjadwalan yang digerakkan oleh acara Anda juga dapat mengintegrasikan pendekatan ini bersama-sama. Misalnya, Anda dapat menggunakan EventBridge Scheduler untuk memicu fungsi tahan lama atau alur kerja Step Functions saat peristiwa tertentu terjadi, atau mengonfigurasi alur kerja untuk mempublikasikan peristiwa ke EventBridge Scheduler pada titik eksekusi yang ditentukan. Topik berikut di bagian ini memberikan informasi lebih lanjut tentang bagaimana Anda dapat menggunakan opsi orkestrasi ini. Orkestrasi kode pertama dengan fungsi tahan lama Fungsi tahan lama Lambda menyediakan pendekatan kode-pertama untuk orkestrasi alur kerja, memungkinkan Anda untuk membangun alur kerja stateful dan berjalan lama secara langsung dalam fungsi Lambda Anda. Tidak seperti layanan orkestrasi eksternal, fungsi tahan lama menjaga logika alur kerja Anda dalam kode, membuatnya lebih mudah untuk versi, pengujian, dan pemeliharaan bersama logika bisnis Anda. Fungsi tahan lama sangat ideal saat Anda membutuhkan: Definisi alur kerja kode-pertama: Tentukan alur kerja menggunakan bahasa pemrograman yang sudah dikenal daripada JSON atau desainer visual Proses yang berjalan lama: Jalankan alur kerja yang dapat berjalan hingga satu tahun, jauh melampaui batas 15 menit fungsi Lambda standar Pengembangan yang disederhanakan: Simpan logika alur kerja dan logika bisnis dalam basis kode yang sama untuk pemeliharaan dan pengujian yang lebih mudah Penantian hemat biaya: Jeda eksekusi selama status tunggu tanpa menghabiskan sumber daya komputasi Manajemen status bawaan: Pos pemeriksaan otomatis dan persistensi status tanpa konfigurasi penyimpanan eksternal Memilih antara fungsi tahan lama dan Step Functions Fungsi tahan lama dan Step Functions menyediakan kemampuan orkestrasi alur kerja, tetapi mereka melayani kasus penggunaan yang berbeda: Pertimbangan Fungsi Tahan Lama Step Functions Definisi alur kerja Kode-pertama (, JavaScript Python, Java) Bahasa Amazon States atau desainer visual yang berbasis di JSON Pendekatan pengembangan Basis kode tunggal dengan logika bisnis Pisahkan definisi alur kerja dan kode fungsi Integrasi layanan Melalui kode fungsi Lambda dan AWS SDKs Integrasi asli dengan banyak layanan AWS Durasi eksekusi Hingga 1 tahun Hingga 1 tahun (Standar), 5 menit (Ekspres) Pemrosesan paralel Promise.all () dan pola berbasis kode Status paralel dan Peta Terdistribusi Penanganan kesalahan Blok coba-tangkap dan logika coba ulang khusus Status coba ulang dan catch bawaan Pemantauan visual CloudWatch log dan dasbor khusus Grafik eksekusi visual dan riwayat terperinci Terbaik untuk Alur kerja yang berpusat pada pengembang, logika bisnis yang kompleks, pembuatan prototipe cepat Orkestrasi multi-layanan, alur kerja visual, tata kelola perusahaan Gunakan fungsi yang tahan lama saat: Tim Anda lebih memilih pendekatan pengembangan kode-pertama Logika alur kerja digabungkan erat dengan logika bisnis Anda membutuhkan pembuatan prototipe dan iterasi yang cepat Alur kerja Anda terutama melibatkan fungsi Lambda dan panggilan layanan sederhana Gunakan Step Functions saat: Anda memerlukan desain dan pemantauan alur kerja visual Alur kerja Anda mengatur beberapa layanan secara ekstensif AWS Anda memerlukan fitur tata kelola perusahaan dan kepatuhan Pemangku kepentingan non-teknis perlu memahami logika alur kerja Untuk informasi selengkapnya tentang fungsi tahan lama, lihat Fungsi tahan lama untuk Lambda . Mengatur alur kerja dengan Step Functions AWS Step Functions adalah layanan orkestrasi alur kerja yang membantu Anda mengoordinasikan beberapa fungsi Lambda dan layanan lainnya ke dalam alur kerja terstruktur. AWS Alur kerja ini dapat mempertahankan status, menangani kesalahan dengan mekanisme coba ulang yang canggih, dan memproses data dalam skala besar. Step Functions menawarkan dua jenis alur kerja untuk memenuhi kebutuhan orkestrasi yang berbeda: Alur kerja standar Ideal untuk alur kerja yang berjalan lama dan dapat diaudit yang memerlukan semantik eksekusi tepat sekali. Alur kerja standar dapat berjalan hingga satu tahun, memberikan riwayat eksekusi terperinci, dan mendukung debugging visual. Mereka cocok untuk proses seperti pemenuhan pesanan, pipa pemrosesan data, atau pekerjaan analitik multi-langkah. Alur kerja ekspres Dirancang untuk high-event-rate, beban kerja berdurasi pendek dengan semantik at-least-once eksekusi. Alur kerja ekspres dapat berjalan hingga lima menit dan ideal untuk pemrosesan peristiwa volume tinggi, transformasi data streaming, atau skenario konsumsi data IoT. Mereka menawarkan throughput yang lebih tinggi dan biaya yang berpotensi lebih rendah dibandingkan dengan alur kerja Standar. catatan Untuk informasi selengkapnya tentang jenis alur kerja Step Functions, lihat Memilih jenis alur kerja di Step Functions. Dalam alur kerja ini, Step Functions menyediakan dua jenis status Peta untuk pemrosesan paralel: Peta Inline Memproses item dari array JSON dalam riwayat eksekusi alur kerja induk. Peta Inline mendukung hingga 40 iterasi bersamaan dan cocok untuk kumpulan data yang lebih kecil atau ketika Anda perlu menyimpan semua pemrosesan dalam satu eksekusi. Untuk informasi selengkapnya, lihat Menggunakan status Peta dalam mode Inline . Peta Terdistribusi Memungkinkan pemrosesan beban kerja paralel skala besar dengan mengulangi kumpulan data yang melebihi 256 KiB atau memerlukan lebih dari 40 iterasi bersamaan. Dengan dukungan hingga 10.000 eksekusi alur kerja anak paralel, Peta Terdistribusi unggul dalam memproses data semi-terstruktur yang disimpan di Amazon S3, seperti file JSON atau CSV, sehingga ideal untuk pemrosesan batch dan operasi ETL. Untuk informasi selengkapnya, lihat Menggunakan status Peta dalam mode Terdistribusi . Dengan menggabungkan jenis alur kerja dan status Peta ini, Step Functions menyediakan perangkat yang fleksibel dan kuat untuk mengatur aplikasi tanpa server yang kompleks, mulai dari operasi skala kecil hingga jaringan pemrosesan data skala besar. Untuk memulai menggunakan Lambda dengan Step Functions, lihat Mengatur fungsi Lambda dengan Step Functions. Mengelola acara dengan EventBridge dan EventBridge Scheduler Amazon EventBridge adalah layanan bus acara yang membantu Anda membangun arsitektur berbasis acara. Ini merutekan peristiwa antara AWS layanan, aplikasi terintegrasi, dan aplikasi perangkat lunak sebagai layanan (SaaS). EventBridge Scheduler adalah penjadwal tanpa server yang memungkinkan Anda membuat, menjalankan, dan mengelola tugas dari satu layanan pusat, memungkinkan Anda untuk memanggil fungsi Lambda pada jadwal menggunakan ekspresi cron dan rate, atau mengonfigurasi pemanggilan satu kali. Amazon EventBridge dan EventBridge Scheduler membantu Anda membangun arsitektur berbasis peristiwa dengan Lambda. EventBridge merutekan peristiwa antara AWS layanan, aplikasi terintegrasi, dan aplikasi SaaS, sementara EventBridge Scheduler menyediakan kemampuan penjadwalan khusus untuk menjalankan fungsi Lambda secara berulang atau satu kali. Layanan ini menyediakan beberapa kemampuan utama untuk bekerja dengan fungsi Lambda: Buat aturan yang cocok dan rute acara ke fungsi Lambda menggunakan EventBridge Siapkan pemanggilan fungsi berulang menggunakan ekspresi cron dan rate dengan Scheduler EventBridge Konfigurasikan pemanggilan fungsi satu kali pada tanggal dan waktu tertentu Tentukan jendela waktu yang fleksibel dan coba lagi kebijakan untuk pemanggilan terjadwal Lihat informasi yang lebih lengkap di Memanggil fungsi Lambda sesuai jadwal . Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Powertools untuk AWS Lambda Lambda fungsi tahan lama Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:29:29 |
https://reports.jenkins.io/jelly-taglib-ref.html#project | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:29 |
https://docs.aws.amazon.com/fr_fr/lambda/latest/dg/durable-execution-sdk.html | SDK d'exécution durable - AWS Lambda SDK d'exécution durable - AWS Lambda Documentation AWS Lambda Guide du développeur DurableContext Ce que fait le SDK Comment fonctionne le point de contrôle Comportement de rediffusion Opérations durables disponibles Comment mesure-t-on la durabilité des opérations Les traductions sont fournies par des outils de traduction automatique. En cas de conflit entre le contenu d'une traduction et celui de la version originale en anglais, la version anglaise prévaudra. SDK d'exécution durable Le SDK d'exécution durable est la base de la création de fonctions durables. Il fournit les primitives dont vous avez besoin pour contrôler la progression, gérer les nouvelles tentatives et gérer le flux d'exécution. Le SDK élimine la complexité de la gestion et de la rediffusion des points de contrôle, en vous permettant d'écrire du code séquentiel qui devient automatiquement tolérant aux pannes. Le SDK est disponible pour JavaScript, TypeScript, et Python. Pour obtenir une documentation complète sur l'API et des exemples, consultez le TypeScript SDKJavaScript/ et le SDK Python sur. GitHub DurableContext Le SDK fournit à votre fonction un DurableContext objet qui expose toutes les opérations durables. Ce contexte remplace le contexte Lambda standard et fournit des méthodes pour créer des points de contrôle, gérer le flux d'exécution et coordonner avec des systèmes externes. Pour utiliser le SDK, enveloppez votre gestionnaire Lambda avec le wrapper d'exécution durable : TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Your function receives DurableContext instead of Lambda context // Use context.step(), context.wait(), etc. return result; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext @durable_execution def handler(event: dict, context: DurableContext): # Your function receives DurableContext # Use context.step(), context.wait(), etc. return result Le wrapper intercepte l'invocation de votre fonction, charge tout journal de points de contrôle existant et fournit le journal DurableContext qui gère les rediffusions et les points de contrôle. Ce que fait le SDK Le SDK assume trois responsabilités essentielles qui permettent une exécution durable : Gestion des points de contrôle : le SDK crée automatiquement des points de contrôle lorsque votre fonction exécute des opérations durables. Chaque point de contrôle enregistre le type d'opération, les entrées et les résultats. Lorsque votre fonction termine une étape, le SDK maintient le point de contrôle avant de continuer. Cela garantit que votre fonction peut reprendre après toute opération terminée en cas d'interruption. Coordination des rediffusions : lorsque votre fonction reprend après une pause ou une interruption, le SDK effectue une rediffusion. Il exécute votre code depuis le début mais ignore les opérations terminées, en utilisant les résultats des points de contrôle stockés au lieu de les réexécuter. Le SDK garantit que la rediffusion est déterministe : avec les mêmes entrées et le même journal de points de contrôle, votre fonction produit les mêmes résultats. Isolation des états : le SDK conserve l'état d'exécution séparément de votre logique métier. Chaque exécution durable possède son propre journal de points de contrôle auquel les autres exécutions ne peuvent pas accéder. Le SDK chiffre les données des points de contrôle au repos et garantit la cohérence de l'état entre les rediffusions. Comment fonctionne le point de contrôle Lorsque vous appelez une opération durable, le SDK suit cette séquence : Vérifier l'existence d'un point de contrôle : le SDK vérifie si cette opération a déjà été effectuée lors d'un appel précédent. S'il existe un point de contrôle, le SDK renvoie le résultat enregistré sans réexécuter l'opération. Exécuter l'opération : s'il n'existe aucun point de contrôle, le SDK exécute votre code d'opération. Pour les étapes, cela signifie appeler votre fonction. Pour les temps d'attente, cela signifie planifier la reprise. Créer un point de contrôle : une fois l'opération terminée, le SDK sérialise le résultat et crée un point de contrôle. Le point de contrôle inclut le type d'opération, le nom, les entrées, le résultat et l'horodatage. Point de contrôle persistant : le SDK appelle l'API du point de contrôle Lambda pour conserver le point de contrôle. Cela garantit la durabilité du point de contrôle avant de poursuivre l'exécution. Renvoyer le résultat : le SDK renvoie le résultat de l'opération à votre code, qui passe à l'opération suivante. Cette séquence garantit qu'une fois l'opération terminée, son résultat est stocké en toute sécurité. Si votre fonction est interrompue à tout moment, le SDK peut être rejoué jusqu'au dernier point de contrôle terminé. Comportement de rediffusion Lorsque votre fonction reprend après une pause ou une interruption, le SDK effectue une rediffusion : Charger le journal des points de contrôle : le SDK extrait le journal des points de contrôle pour cette exécution à partir de Lambda. Exécuter depuis le début : le SDK appelle votre fonction de gestionnaire dès le début, et non depuis l'endroit où elle s'est interrompue. Ignorer les opérations durables terminées : lorsque votre code appelle des opérations durables, le SDK compare chacune d'entre elles au journal des points de contrôle. Pour les opérations durables terminées, le SDK renvoie le résultat stocké sans exécuter le code d'opération. Note Si le résultat d'un contexte enfant est supérieur à la taille maximale du point de contrôle (256 Ko), le code du contexte est à nouveau exécuté pendant la rediffusion. Cela vous permet de générer des résultats volumineux à partir des opérations durables exécutées dans le contexte, qui seront consultés dans le journal des points de contrôle. Il est donc impératif de n'exécuter le code déterministe que dans le contexte lui-même. Lorsque vous utilisez des contextes enfants avec des résultats importants, il est recommandé d'effectuer un travail de longue durée ou non déterministe à l'intérieur des étapes et de n'effectuer que des tâches de courte durée qui combinent les résultats dans le contexte lui-même. Reprise au point d'interruption : lorsque le SDK atteint une opération sans point de contrôle, il s'exécute normalement et crée de nouveaux points de contrôle au fur et à mesure que les opérations durables sont terminées. Ce mécanisme de rediffusion nécessite que votre code soit déterministe. Avec les mêmes entrées et le même journal de points de contrôle, votre fonction doit effectuer la même séquence d'appels d'opérations durables. Le SDK applique cela en validant que les noms et types d'opérations correspondent au journal des points de contrôle lors de la rediffusion. Opérations durables disponibles DurableContext Il fournit des opérations pour différents modèles de coordination. Chaque opération durable crée automatiquement des points de contrôle, garantissant ainsi que votre fonction peut reprendre à tout moment. Étapes Exécute la logique métier avec pointage automatique des points de contrôle et réessais. Utilisez des étapes pour les opérations qui appellent des services externes, effectuent des calculs ou exécutent toute logique qui doit être vérifiée. Le SDK crée un point de contrôle avant et après l'étape, stockant le résultat pour le rejouer. TypeScript const result = await context.step('process-payment', async () => { return await paymentService.charge(amount); }); Python result = context.step( lambda _: payment_service.charge(amount), name='process-payment' ) Les étapes prennent en charge les stratégies de nouvelle tentative configurables, la sémantique d'exécution (at-most-once ou at-least-once) et la sérialisation personnalisée. Éléments d’attente Suspend l'exécution pendant une durée spécifiée sans consommer de ressources informatiques. Le SDK crée un point de contrôle, met fin à l'invocation de la fonction et planifie la reprise. Lorsque l'attente est terminée, Lambda invoque à nouveau votre fonction et le SDK rejoue jusqu'au point d'attente avant de continuer. TypeScript // Wait 1 hour without charges await context.wait( { seconds: 3600 }); Python # Wait 1 hour without charges context.wait(3600) Rappels Les rappels permettent à votre fonction de faire une pause et d'attendre que des systèmes externes fournissent une entrée. Lorsque vous créez un rappel, le SDK génère un identifiant de rappel unique et crée un point de contrôle. Votre fonction est ensuite suspendue (met fin à l'invocation) sans frais de calcul. Les systèmes externes soumettent les résultats de rappel à l'aide du SendDurableExecutionCallbackSuccess ou SendDurableExecutionCallbackFailure Lambda APIs. Lorsqu'un rappel est soumis, Lambda invoque à nouveau votre fonction, le SDK rejoue jusqu'au point de rappel et votre fonction continue avec le résultat du rappel. Le SDK propose deux méthodes pour utiliser les rappels : CreateCallback : crée un rappel et renvoie à la fois une promesse et un identifiant de rappel. Vous envoyez l'ID de rappel à un système externe, qui soumet le résultat à l'aide de l'API Lambda. TypeScript const [promise, callbackId] = await context.createCallback('approval', { timeout: { hours: 24 } }); await sendApprovalRequest(callbackId, requestData); const approval = await promise; Python callback = context.create_callback( name='approval', config=CallbackConfig(timeout_seconds=86400) ) context.step( lambda _: send_approval_request(callback.callback_id), name='send_request' ) approval = callback.result() waitForCallback: simplifie la gestion des rappels en combinant la création et la soumission des rappels en une seule opération. Le SDK crée le rappel, exécute votre fonction de soumission avec l'ID de rappel et attend le résultat. TypeScript const result = await context.waitForCallback( 'external-api', async (callbackId, ctx) => { await submitToExternalAPI(callbackId, requestData); }, { timeout: { minutes: 30 } } ); Python result = context.wait_for_callback( lambda callback_id: submit_to_external_api(callback_id, request_data), name='external-api', config=WaitForCallbackConfig(timeout_seconds=1800) ) Configurez les délais d'attente pour empêcher les fonctions d'attendre indéfiniment. Si un rappel expire, le SDK renvoie un CallbackError et votre fonction peut gérer le cas de délai d'expiration. Utilisez les délais d'expiration du rythme cardiaque pour les rappels de longue durée afin de détecter les cas où les systèmes externes cessent de répondre. Utilisez des rappels pour les human-in-the-loop flux de travail, l'intégration de systèmes externes, les réponses Webhook ou tout autre scénario dans lequel l'exécution doit être interrompue pour une entrée externe. Exécution en parallèle Exécute plusieurs opérations simultanément avec un contrôle de simultanéité optionnel. Le SDK gère l'exécution parallèle, crée des points de contrôle pour chaque opération et gère les défaillances conformément à votre politique d'achèvement. TypeScript const results = await context.parallel([ async (ctx) => ctx.step('task1', async () => processTask1()), async (ctx) => ctx.step('task2', async () => processTask2()), async (ctx) => ctx.step('task3', async () => processTask3()) ]); Python results = context.parallel( lambda ctx: ctx.step(lambda _: process_task1(), name='task1'), lambda ctx: ctx.step(lambda _: process_task2(), name='task2'), lambda ctx: ctx.step(lambda _: process_task3(), name='task3') ) parallel À utiliser pour exécuter simultanément des opérations indépendantes. Map Exécutez simultanément une opération sur chaque élément d'un tableau avec un contrôle de simultanéité optionnel. Le SDK gère les exécutions simultanées, crée des points de contrôle pour chaque opération et gère les défaillances conformément à votre politique d'achèvement. TypeScript const results = await context.map(itemArray, async (ctx, item, index) => ctx.step('task', async () => processItem(item, index)) ); Python results = context.map( item_array, lambda ctx, item, index: ctx.step( lambda _: process_item(item, index), name='task' ) ) map À utiliser pour traiter des tableaux avec contrôle de simultanéité. Contextes relatifs aux enfants Crée un contexte d'exécution isolé pour les opérations de regroupement. Les contextes enfants possèdent leur propre journal des points de contrôle et peuvent contenir plusieurs étapes, temps d'attente et autres opérations. Le SDK traite l'ensemble du contexte de l'enfant comme une unité unique pour les nouvelles tentatives et la restauration. Utilisez des contextes enfants pour organiser des flux de travail complexes, implémenter des sous-flux de travail ou isoler les opérations qui doivent être réessayées ensemble. TypeScript const result = await context.runInChildContext( 'batch-processing', async (childCtx) => { return await processBatch(childCtx, items); } ); Python result = context.run_in_child_context( lambda child_ctx: process_batch(child_ctx, items), name='batch-processing' ) Le mécanisme de rediffusion exige que les opérations durables soient effectuées dans un ordre déterministe. En utilisant plusieurs contextes enfants, plusieurs flux de travail peuvent être exécutés simultanément, et le déterminisme s'applique séparément dans chaque contexte. Cela vous permet de créer des fonctions hautes performances qui utilisent efficacement plusieurs cœurs de processeur. Par exemple, imaginons que nous démarrions deux contextes enfants, A et B. Lors de l'invocation initiale, les étapes des contextes étaient exécutées dans cet ordre, les étapes « A » s'exécutant simultanément avec les étapes « B » : A1, B1, B2, A2, A3. Lors de la rediffusion, le chronométrage est beaucoup plus rapide car les résultats sont extraits du journal des points de contrôle et les étapes sont parcourues dans un ordre différent : B1, A1, A2, B2, A3. Comme les étapes « A » ont été rencontrées dans le bon ordre (A1, A2, A3) et que les étapes « B » ont été rencontrées dans le bon ordre (B1, B2), le besoin de déterminisme a été correctement satisfait. Attentes conditionnelles Recherche une condition avec pointage automatique entre les tentatives. Le SDK exécute votre fonction de vérification, crée un point de contrôle avec le résultat, attend selon votre stratégie et répète jusqu'à ce que la condition soit remplie. TypeScript const result = await context.waitForCondition( async (state, ctx) => { const status = await checkJobStatus(state.jobId); return { ...state, status }; }, { initialState: { jobId: 'job-123', status: 'pending' }, waitStrategy: (state) => state.status === 'completed' ? { shouldContinue: false } : { shouldContinue: true, delay: { seconds: 30 } } } ); Python result = context.wait_for_condition( lambda state, ctx: check_job_status(state['jobId']), config=WaitForConditionConfig( initial_state= { 'jobId': 'job-123', 'status': 'pending'}, wait_strategy=lambda state, attempt: { 'should_continue': False} if state['status'] == 'completed' else { 'should_continue': True, 'delay': 30} ) ) waitForCondition À utiliser pour interroger des systèmes externes, attendre que les ressources soient prêtes ou implémenter une nouvelle tentative avec interruption. Invocation de fonctions Invoque une autre fonction Lambda et attend son résultat. Le SDK crée un point de contrôle, invoque la fonction cible et reprend votre fonction une fois l'invocation terminée. Cela permet la composition des fonctions et la décomposition du flux de travail. TypeScript const result = await context.invoke( 'invoke-processor', 'arn:aws:lambda:us-east-1:123456789012:function:processor', { data: inputData } ); Python result = context.invoke( 'arn:aws:lambda:us-east-1:123456789012:function:processor', { 'data': input_data}, name='invoke-processor' ) Comment mesure-t-on la durabilité des opérations Chaque opération durable que vous effectuez DurableContext crée des points de contrôle pour suivre la progression de l'exécution et stocker les données d'état. Ces opérations sont facturées en fonction de leur utilisation, et les points de contrôle peuvent contenir des données qui contribuent à vos coûts d'écriture et de conservation des données. Les données stockées incluent les données relatives aux événements d'invocation, les charges utiles renvoyées par les étapes et les données transmises lors de l'exécution des rappels. Comprendre comment la durabilité des opérations est mesurée vous permet d'estimer les coûts d'exécution et d'optimiser vos flux de travail. Pour plus de détails sur la tarification, consultez la page de tarification de Lambda . La taille de la charge utile fait référence à la taille des données sérialisées qu'une opération durable persiste. Les données sont mesurées en octets et leur taille peut varier en fonction du sérialiseur utilisé par l'opération. La charge utile d'une opération peut être le résultat lui-même en cas d'achèvement réussi, ou l'objet d'erreur sérialisé en cas d'échec de l'opération. Opérations de base Les opérations de base sont les éléments fondamentaux des fonctions durables : Opération Chronométrage des points de contrôle Nombre d'opérations Les données ont persisté Exécution Démarré(e) 1 Taille de la charge utile d'entrée Exécution Terminé (Succeeded/Failed/Stopped) 0 Taille de la charge utile de sortie Step (Étape) Retry/Succeeded/Failed 10 + Aucune nouvelle tentative Taille de la charge utile renvoyée à chaque tentative Attente Démarré(e) 1 N/A WaitForCondition Chaque tentative de sondage + 1 x N sondages Taille de la charge utile renvoyée à chaque tentative de sondage Nouvelle tentative au niveau de l'invocation Démarré(e) 1 Charge utile pour l'objet d'erreur Opérations de rappel Les opérations de rappel permettent à votre fonction de faire une pause et d'attendre que des systèmes externes fournissent une entrée. Ces opérations créent des points de contrôle lorsque le rappel est créé et lorsqu'il est terminé : Opération Chronométrage des points de contrôle Nombre d'opérations Les données ont persisté CreateCallback Démarré(e) 1 N/A Exécution du rappel via un appel d'API Terminé 0 Charge utile de rappel WaitForCallback Démarré(e) 3 + N tentatives (contexte + rappel + étape) Charges utiles renvoyées par les tentatives d'étape de l'expéditeur, plus deux copies de la charge utile de rappel Opérations composées Les opérations composées combinent plusieurs opérations durables pour gérer des modèles de coordination complexes tels que l'exécution parallèle, le traitement de tableaux et les contextes imbriqués : Opération Chronométrage des points de contrôle Nombre d'opérations Les données ont persisté Parallèle Démarré(e) 1 + N branches (1 contexte parent + N contextes enfants) Jusqu'à deux copies de la taille de charge utile renvoyée par chaque branche, plus les statuts de chaque branche Map Démarré(e) 1 + N branches (1 contexte parent + N contextes enfants) Jusqu'à deux copies de la taille de charge utile renvoyée par itération, plus les statuts de chaque itération Des aides à la promesse Terminé 1 Taille de la charge utile renvoyée par la promesse RunInChildContext Succès/Echec 1 Taille de la charge utile renvoyée par le contexte enfant Pour les contextes, tels que ceux issus runInChildContext ou utilisés en interne par des opérations composées, les résultats inférieurs à 256 Ko sont directement contrôlés. Les résultats les plus importants ne sont pas stockés ; ils sont reconstruits lors de la rediffusion en retraitant les opérations du contexte. JavaScript est désactivé ou n'est pas disponible dans votre navigateur. Pour que vous puissiez utiliser la documentation AWS, Javascript doit être activé. Vous trouverez des instructions sur les pages d'aide de votre navigateur. Conventions de rédaction Sécurité et autorisations Environnements d'exécution pris en charge Cette page vous a-t-elle été utile ? - Oui Merci de nous avoir fait part de votre satisfaction. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer ce qui vous a plu afin que nous puissions nous améliorer davantage. Cette page vous a-t-elle été utile ? - Non Merci de nous avoir avertis que cette page avait besoin d'être retravaillée. Nous sommes désolés de ne pas avoir répondu à vos attentes. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer comment nous pourrions améliorer cette documentation. | 2026-01-13T09:29:29 |
https://reports.jenkins.io/jelly-taglib-ref.html#layout | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:29 |
https://docs.aws.amazon.com/id_id/lambda/latest/dg/durable-functions.html#durable-functions-benefits | Lambda fungsi tahan lama - AWS Lambda Lambda fungsi tahan lama - AWS Lambda Dokumentasi AWS Lambda Panduan Developerr Manfaat utama Cara kerjanya Kapan menggunakan fungsi yang tahan lama Langkah selanjutnya Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Lambda fungsi tahan lama Fungsi Lambda yang tahan lama memungkinkan Anda membangun aplikasi multi-langkah yang tangguh dan alur kerja AI yang dapat dijalankan hingga satu tahun sambil mempertahankan kemajuan yang andal meskipun ada gangguan. Ketika fungsi tahan lama berjalan, siklus hidup lengkap ini disebut eksekusi tahan lama, yang menggunakan pos pemeriksaan untuk melacak kemajuan dan secara otomatis pulih dari kegagalan melalui pemutaran ulang, mengeksekusi ulang dari awal sambil melewatkan pekerjaan yang telah selesai. Dalam setiap fungsi, Anda menggunakan operasi yang tahan lama sebagai blok bangunan mendasar. Langkah-langkah mengeksekusi logika bisnis dengan percobaan ulang dan pelacakan kemajuan bawaan, sementara menunggu menangguhkan eksekusi tanpa menimbulkan biaya komputasi, menjadikannya ideal untuk proses yang berjalan lama seperti alur kerja atau polling dependensi eksternal. human-in-the-loop Baik Anda memproses pesanan, mengoordinasikan layanan mikro, atau mengatur aplikasi AI agen, fungsi tahan lama mempertahankan status secara otomatis dan pulih dari kegagalan saat Anda menulis kode dalam bahasa pemrograman yang sudah dikenal. Manfaat utama Tulis kode tangguh secara alami: Dengan konstruksi pemrograman yang sudah dikenal, Anda menulis kode yang menangani kegagalan secara otomatis. Pemeriksaan bawaan, percobaan ulang transparan, dan pemulihan otomatis berarti logika bisnis Anda tetap bersih dan fokus. Bayar hanya untuk apa yang Anda gunakan: Selama operasi tunggu, fungsi Anda ditangguhkan tanpa menimbulkan biaya komputasi. Untuk alur kerja yang berjalan lama yang menunggu berjam-jam atau berhari-hari, Anda hanya membayar untuk waktu pemrosesan aktual, bukan menunggu idle. Kesederhanaan operasional: Dengan model tanpa server Lambda, Anda mendapatkan penskalaan otomatis, termasuk scale-to-zero, tanpa mengelola infrastruktur. Fungsi tahan lama menangani manajemen status, coba kembali logika, dan pemulihan kegagalan secara otomatis, mengurangi overhead operasional. Cara kerjanya Di bawah kap, fungsi tahan lama adalah fungsi Lambda biasa menggunakan checkpoint/replay mekanisme untuk melacak kemajuan dan mendukung operasi yang berjalan lama melalui titik suspensi yang ditentukan pengguna, yang biasa disebut sebagai eksekusi tahan lama. Ketika fungsi yang tahan lama dilanjutkan dari titik tunggu atau gangguan seperti percobaan ulang, sistem melakukan pemutaran ulang. Selama pemutaran ulang, kode Anda berjalan dari awal tetapi melompati pos pemeriksaan yang telah selesai, menggunakan hasil yang disimpan alih-alih mengeksekusi ulang operasi yang telah selesai. Mekanisme pemutaran ulang ini memastikan konsistensi sekaligus memungkinkan eksekusi yang berjalan lama. Setelah fungsi Anda dilanjutkan dari jeda atau gangguan, sistem melakukan pemutaran ulang. Selama pemutaran ulang, kode Anda berjalan dari awal tetapi melompati pos pemeriksaan yang telah selesai, menggunakan hasil yang disimpan alih-alih mengeksekusi ulang operasi yang telah selesai. Mekanisme pemutaran ulang ini memastikan konsistensi sekaligus memungkinkan eksekusi yang berjalan lama. Untuk memanfaatkan checkpoint-and-replay mekanisme ini dalam aplikasi Anda, Lambda menyediakan SDK eksekusi yang tahan lama. SDK mengabstraksi kompleksitas pengelolaan pos pemeriksaan dan pemutaran ulang, memperlihatkan primitif sederhana yang disebut operasi tahan lama yang Anda gunakan dalam kode Anda. SDK tersedia untuk JavaScript,, dan Python TypeScript, terintegrasi secara mulus dengan alur kerja pengembangan Lambda Anda yang ada. Dengan SDK, Anda membungkus event handler Lambda Anda, yang kemudian menyediakan DurableContext di samping acara Anda. Konteks ini memberi Anda akses ke operasi yang tahan lama seperti langkah dan menunggu. Anda menulis logika fungsi Anda sebagai kode sekuensial normal, tetapi alih-alih memanggil layanan secara langsung, Anda membungkus panggilan tersebut dalam langkah-langkah untuk pemeriksaan otomatis dan percobaan ulang. Ketika Anda perlu menjeda eksekusi, Anda menambahkan menunggu yang menangguhkan fungsi Anda tanpa menimbulkan biaya. SDK menangani semua kompleksitas manajemen status dan pemutaran ulang di belakang layar, sehingga kode Anda tetap bersih dan mudah dibaca. Kapan menggunakan fungsi yang tahan lama Koordinasi jangka pendek: Mengkoordinasikan pembayaran, inventaris, dan pengiriman di berbagai layanan dengan pengembalian otomatis pada kegagalan. Memproses pesanan melalui validasi, otorisasi pembayaran, alokasi inventaris, dan pemenuhan dengan jaminan penyelesaian. Memproses pembayaran dengan percaya diri: Membangun arus pembayaran tangguh yang mempertahankan status transaksi melalui kegagalan dan menangani percobaan ulang secara otomatis. Mengkoordinasikan otorisasi multi-langkah, pemeriksaan penipuan, dan penyelesaian di seluruh penyedia pembayaran dengan auditabilitas penuh di seluruh langkah. Bangun alur kerja AI yang andal: Buat alur kerja AI multi-langkah yang memanggil model rantai, menggabungkan umpan balik manusia, dan menangani tugas yang berjalan lama secara deterministik selama kegagalan. Secara otomatis melanjutkan setelah penangguhan, dan hanya membayar untuk waktu eksekusi aktif. Mengatur pemenuhan pesanan yang kompleks: Mengkoordinasikan pemrosesan pesanan di seluruh inventaris, pembayaran, pengiriman, dan sistem notifikasi dengan ketahanan bawaan. Secara otomatis menangani kegagalan sebagian, mempertahankan status pesanan meskipun ada gangguan, dan secara efisien menunggu peristiwa eksternal tanpa menghabiskan sumber daya komputasi. Otomatiskan alur kerja bisnis multi-langkah: Bangun alur kerja yang andal untuk orientasi karyawan, persetujuan pinjaman, dan proses kepatuhan yang berlangsung berhari-hari atau berminggu-minggu. Pertahankan status alur kerja di seluruh persetujuan manusia, integrasi sistem, dan tugas terjadwal sambil memberikan visibilitas penuh ke dalam status dan riwayat proses. Langkah selanjutnya Memulai dengan fungsi yang tahan lama Jelajahi SDK eksekusi yang tahan lama Memantau dan men-debug fungsi yang tahan lama Tinjau keamanan dan izin Ikuti praktik terbaik Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Alur kerja dan acara Konsep dasar Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:29:30 |
https://wordpress.com/zh-cn/google/ | 将您的 WordPress.com 网站与 Google 工具相集成 产品 特色 资源 套餐与定价 登录 从这里开始 菜单 WordPress主机 WordPress for Agencies 成为联盟成员 域名 AI 网站生成器 网站构建器 创建一个博客 电子报 专业电子邮件 网站设计服务 电商版 WordPress Studio 企业级 WordPress 概述 WordPress主题 WordPress 插件 WordPress 样板 Google App 支持中心 WordPress新闻 企业名称生成器 徽标制作工具 发现新文章 热门标签 博客搜索 关闭导航菜单 从这里开始 注册 登录 关于 套餐与定价 产品 WordPress主机 WordPress for Agencies 成为联盟成员 域名 AI 网站生成器 网站构建器 创建一个博客 电子报 专业电子邮件 网站设计服务 电商版 WordPress Studio 企业级 WordPress 特色 概述 WordPress主题 WordPress 插件 WordPress 样板 Google App 资源 支持中心 WordPress新闻 企业名称生成器 徽标制作工具 发现新文章 热门标签 博客搜索 Jetpack 应用程序 了解更多 WordPress.com + Google 了解在 WordPress 网站上使用 Google 工具和服务最简单的方法。无需选择和 取舍。在 WordPress.com 打造最优秀的网站。 Google Analytics（分析） 在 Google 的支持下，利用深入详尽的数据作出明智的业务决策 将 Google Analytics（分析）添加到您的 WordPress.com 商务版 站点中以跟踪性能。 及时获得以下方面的详细统计数据：访客来自何处、他们如何与您的站点互动以及他们是否响应您的营销行动。 了解 Google Analytics（分析） Google Workspace 动动手指就能畅快使用最热门的 Google 产品 向您的 WordPress.com 帐户添加自定义品牌的 Gmail 电子邮件地址、Google 云端硬盘、Google 文件、Google Meet 和 Google 聊天。 我们集成了 Google Workspace，让您不需要借助任何软件也能改进工作流程。 了解 Google Workspace Search Console 借助 Search Console，让人们更轻松地找到您的站点 集成 Google Search Console 后，您可以像使用搜索引擎那样查看自己的站点。还可以获得详细的报告，了解访客如何搜索到您的站点、他们点击了什么内容以及谁关联了您的站点等信息。优化您的站点可提高浏览量和曝光度。 Google Docs 让您能协同编辑 WordPress 网站内容 利用 WordPress.com for Google Docs，您可以在 Google Docs 中撰写和编辑文档并与他人协作，然后在任意 WordPress.com 站点上将其保存为博文。图片和大部分格式也会从 Google Docs 传递到 WordPress 中，让您无需再费力地进行复制并粘贴。 了解 Google 文件 Google Photos Google Photos for WordPress 助您简化工作流程 一次上传，随处分享。利用 Google Photos for WordPress，您可以在 Web 存储空间中轻松管理和保存媒体内容。您可以浏览和搜索 Google 帐户中的照片，然后将照片直接复制到 WordPress.com 博文和页面中，而无需二次上传照片。 了解 Google 相册 在 WordPress.com 上利用 Google 的强大功能为您的商务站点带来优越性能 商务版 套餐无需安装软件就能添加 Google 工具和服务，助您轻松打造自己的站点。 开始 WordPress.com 产品 WordPress主机 WordPress for Agencies 成为联盟成员 域名 AI 网站生成器 网站构建器 创建一个博客 专业电子邮件 网站设计服务 WordPress Studio 企业级 WordPress 特色 概述 WordPress主题 WordPress 插件 WordPress 样板 Google App 资源 WordPress.com 博客 企业名称生成器 徽标制作工具 WordPress.com 阅读器 可访问性 删除订阅 帮助 支持中心 使用指南 课程 论坛 联系 开发者资源 公司 关于 新闻 服务条款 隐私政策 请勿出售或分享我的个人信息 面向加州用户的隐私声明 Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English 移动应用程序 在以下位置下载 应用中心 在以下位置获取 Google Play 社交媒体 Facebook 上的 WordPress.com X (Twitter) 上的 WordPress.com Instagram 上的 WordPress.com YouTube 上的 WordPress.com Automattic Automattic 与我们合作 | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/zh_tw/lambda/latest/dg/durable-security.html | Lambda 耐用函數的安全性和許可 - AWS Lambda Lambda 耐用函數的安全性和許可 - AWS Lambda 文件 AWS Lambda 開發人員指南 執行角色許可 狀態加密 CloudTrail 日誌記錄 跨帳戶考量事項 繼承的 Lambda 安全功能 本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。 Lambda 耐用函數的安全性和許可 Lambda 耐用函數需要特定的 IAM 許可才能管理檢查點操作。僅授予函數所需的許可，以遵循最低權限原則。 執行角色許可 您耐用函數的執行角色需要建立檢查點和擷取執行狀態的許可。下列政策顯示最低必要許可： { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "lambda:CheckpointDurableExecution", "lambda:GetDurableExecutionState" ], "Resource": "arn:aws:lambda:region:account-id:function:function-name:*" } ] } 當您使用主控台建立耐用的函數時，Lambda 會自動將這些許可新增至執行角色。如果您使用 AWS CLI 或 建立函數 AWS CloudFormation，請將這些許可新增至執行角色。 最低權限原則 將 Resource 元素範圍限定為特定函數 ARNs，而不是使用萬用字元。這只會將執行角色限制為需要它們的函數的檢查點操作。 範例：多個函數的範圍許可 { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "lambda:CheckpointDurableExecution", "lambda:GetDurableExecutionState" ], "Resource": [ "arn:aws:lambda:us-east-1:123456789012:function:orderProcessor:*", "arn:aws:lambda:us-east-1:123456789012:function:paymentHandler:*" ] } ] } 或者，您可以使用 AWS 受管政策 AWSLambdaBasicDurableExecutionRolePolicy ，其中包含必要的持久執行許可，以及 Amazon CloudWatch Logs 的基本 Lambda 執行許可。 狀態加密 Lambda 耐用函數使用 AWS 擁有的金鑰自動啟用靜態加密，無需付費。每個函數執行都會維持其他執行無法存取的隔離狀態。不支援客戶受管金鑰 (CMK)。 檢查點資料包括： 步驟結果和傳回值 執行進度和時間軸 等待狀態資訊 當 Lambda 讀取或寫入檢查點資料時，所有資料都會使用 TLS 在傳輸中加密。 使用自訂序列化程式和還原序列化程式進行自訂加密 對於關鍵安全需求，您可以使用自訂序列化程式和使用耐用 SDK 的還原序列化程式 (SerDer) 來實作自己的加密和解密機制。此方法可讓您完全控制用來保護檢查點資料的加密金鑰和演算法。 重要 當您使用自訂加密時，您會失去 Lambda 主控台和 API 回應中操作結果的可見性。檢查點資料會在執行歷史記錄中顯示加密，且無法在未解密的情況下進行檢查。 函數的執行角色對自訂 SerDer 實作中使用的 AWS KMS 金鑰的需求 kms:Encrypt 和 kms:Decrypt 許可。 CloudTrail 日誌記錄 Lambda 會將檢查點操作記錄為其中的資料事件 AWS CloudTrail。您可以使用 CloudTrail 來稽核檢查點的建立時間、追蹤執行狀態變更，以及監控對持久執行資料的存取。 檢查點操作會顯示在具有下列事件名稱的 CloudTrail 日誌中： CheckpointDurableExecution - 步驟完成並建立檢查點時記錄 GetDurableExecutionState - 當 Lambda 在重播期間擷取執行狀態時記錄 若要啟用耐用函數的資料事件記錄，請設定 CloudTrail 追蹤來記錄 Lambda 資料事件。如需詳細資訊，請參閱《CloudTrail 使用者指南》中的 記錄資料事件 。 範例：檢查點操作的 CloudTrail 日誌項目 { "eventVersion": "1.08", "eventTime": "2024-11-16T10:30:45Z", "eventName": "CheckpointDurableExecution", "eventSource": "lambda.amazonaws.com", "requestParameters": { "functionName": "myDurableFunction", "executionId": "exec-abc123", "stepId": "step-1" }, "responseElements": null, "eventType": "AwsApiCall" } 跨帳戶考量事項 如果您跨 AWS 帳戶叫用耐久的函數，呼叫帳戶需要 lambda:InvokeFunction 許可，但檢查點操作一律使用函數帳戶中的執行角色。呼叫帳戶無法直接存取檢查點資料或執行狀態。 此隔離可確保檢查點資料在函數的帳戶內保持安全，即使從外部帳戶調用也一樣。 繼承的 Lambda 安全功能 耐用的函數繼承 Lambda 的所有安全、控管和合規功能，包括 VPC 連線、環境變數加密、無效字母佇列、預留並行、函數 URLs、程式碼簽署和合規認證 (SOC、PCI DSS、HIPAA 等）。 如需 Lambda 安全性功能的詳細資訊，請參閱《Lambda 開發人員指南》中的 中的安全性 AWS Lambda 。持久功能的唯一額外安全考量是本指南中記錄的檢查點許可。 您的瀏覽器已停用或無法使用 Javascript。 您必須啟用 Javascript，才能使用 AWS 文件。請參閱您的瀏覽器說明頁以取得說明。 文件慣用形式 範例 耐用的執行 SDK 此頁面是否有幫助？ - 是 感謝您，讓我們知道我們做得很好！ 若您有空，歡迎您告知我們值得讚許的地方，這樣才能保持良好服務。 此頁面是否有幫助？ - 否 感謝讓我們知道此頁面仍須改善。很抱歉，讓您失望。 若您有空，歡迎您提供改善文件的方式。 | 2026-01-13T09:29:30 |
https://id.atlassian.com/signup?application=community--entry-auth&continue=https%3A%2F%2Fcommunity.atlassian.com%2Flearning%2Fhub%2Fadoption-and-change-management | Log in with Atlassian account Atlassian JavaScript is disabled You should enable JavaScript to work with this page. Atlassian JavaScript load error We tried to load scripts but something went wrong. Please make sure that your network settings allow you to download scripts from the following domain: https://id-frontend.prod-east.frontend.public.atl-paas.net | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/fr_fr/lambda/latest/dg/durable-security.html | Sécurité et autorisations pour les fonctions durables de Lambda - AWS Lambda Sécurité et autorisations pour les fonctions durables de Lambda - AWS Lambda Documentation AWS Lambda Guide du développeur Autorisations du rôle d’exécution Chiffrement d'état CloudTrail journalisation Considérations relatives à l’accès intercompte Fonctionnalités de sécurité Lambda héritées Les traductions sont fournies par des outils de traduction automatique. En cas de conflit entre le contenu d'une traduction et celui de la version originale en anglais, la version anglaise prévaudra. Sécurité et autorisations pour les fonctions durables de Lambda Les fonctions durables de Lambda nécessitent des autorisations IAM spécifiques pour gérer les opérations des points de contrôle. Respectez le principe du moindre privilège en n'accordant que les autorisations dont votre fonction a besoin. Autorisations du rôle d’exécution Le rôle d'exécution de votre fonction durable nécessite des autorisations pour créer des points de contrôle et récupérer l'état d'exécution. La politique suivante indique les autorisations minimales requises : { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "lambda:CheckpointDurableExecution", "lambda:GetDurableExecutionState" ], "Resource": "arn:aws:lambda:region:account-id:function:function-name:*" } ] } Lorsque vous créez une fonction durable à l'aide de la console, Lambda ajoute automatiquement ces autorisations au rôle d'exécution. Si vous créez la fonction à l'aide du AWS CLI ou AWS CloudFormation, ajoutez ces autorisations à votre rôle d'exécution. Principe du moindre privilège Délimitez l' Resource élément à une fonction spécifique ARNs au lieu d'utiliser des caractères génériques. Cela limite le rôle d'exécution aux opérations de point de contrôle uniquement pour les fonctions qui en ont besoin. Exemple : autorisations étendues pour plusieurs fonctions { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "lambda:CheckpointDurableExecution", "lambda:GetDurableExecutionState" ], "Resource": [ "arn:aws:lambda:us-east-1:123456789012:function:orderProcessor:*", "arn:aws:lambda:us-east-1:123456789012:function:paymentHandler:*" ] } ] } Vous pouvez également utiliser la politique AWS gérée AWSLambdaBasicDurableExecutionRolePolicy qui inclut les autorisations d'exécution durables requises ainsi que les autorisations d'exécution Lambda de base pour Amazon CloudWatch Logs. Chiffrement d'état Les fonctions Lambda Durable activent automatiquement le chiffrement au repos à l'aide de clés AWS détenues gratuitement. Chaque exécution de fonction conserve un état isolé auquel les autres exécutions ne peuvent pas accéder. Les clés gérées par le client (CMK) ne sont pas prises en charge. Les données des points de contrôle incluent : Résultats des étapes et valeurs renvoyées Progrès et calendrier de l'exécution Informations sur l'état d'attente Toutes les données sont cryptées en transit à l'aide du protocole TLS lorsque Lambda lit ou écrit des données de point de contrôle. Chiffrement personnalisé avec sérialiseurs et désérialiseurs personnalisés Pour les exigences de sécurité critiques, vous pouvez implémenter votre propre mécanisme de chiffrement et de déchiffrement à l'aide de sérialiseurs et de désérialiseurs personnalisés () à l'aide d'un SDK durable. SerDer Cette approche vous donne un contrôle total sur les clés de chiffrement et les algorithmes utilisés pour protéger les données des points de contrôle. Important Lorsque vous utilisez un chiffrement personnalisé, vous perdez la visibilité des résultats des opérations dans la console Lambda et les réponses de l'API. Les données des points de contrôle apparaissent cryptées dans l'historique des exécutions et ne peuvent pas être inspectées sans déchiffrement. Le rôle d'exécution de votre fonction kms:Decrypt nécessite kms:Encrypt et autorise la AWS KMS clé utilisée dans l' SerDer implémentation personnalisée. CloudTrail journalisation Lambda enregistre les opérations des points de contrôle sous forme d'événements de données dans. AWS CloudTrail Vous pouvez l'utiliser CloudTrail pour auditer le moment où les points de contrôle sont créés, suivre les changements d'état d'exécution et surveiller l'accès aux données d'exécution durables. Les opérations de point de contrôle apparaissent dans CloudTrail les journaux sous les noms d'événements suivants : CheckpointDurableExecution - Enregistré lorsqu'une étape se termine et crée un point de contrôle GetDurableExecutionState - Enregistré lorsque Lambda récupère l'état d'exécution pendant la rediffusion Pour activer la journalisation des événements de données pour des fonctions durables, configurez un journal CloudTrail pour enregistrer les événements de données Lambda. Pour plus d'informations, consultez la section Journalisation des événements liés aux données dans le Guide de CloudTrail l'utilisateur. Exemple : entrée de CloudTrail journal pour le fonctionnement du point de contrôle { "eventVersion": "1.08", "eventTime": "2024-11-16T10:30:45Z", "eventName": "CheckpointDurableExecution", "eventSource": "lambda.amazonaws.com", "requestParameters": { "functionName": "myDurableFunction", "executionId": "exec-abc123", "stepId": "step-1" }, "responseElements": null, "eventType": "AwsApiCall" } Considérations relatives à l’accès intercompte Si vous invoquez des fonctions durables sur plusieurs AWS comptes, le compte appelant a besoin d'une lambda:InvokeFunction autorisation, mais les opérations de point de contrôle utilisent toujours le rôle d'exécution dans le compte de la fonction. Le compte appelant ne peut pas accéder directement aux données du point de contrôle ou à l'état d'exécution. Cette isolation garantit que les données des points de contrôle restent sécurisées dans le compte de la fonction, même lorsqu'elles sont invoquées depuis des comptes externes. Fonctionnalités de sécurité Lambda héritées Les fonctions durables héritent de toutes les fonctionnalités de sécurité, de gouvernance et de conformité de Lambda, notamment la connectivité VPC, le chiffrement des variables d'environnement, les files d'attente lettre morte, la simultanéité réservée, les URLs fonctions, la signature de code et les certifications de conformité (SOC, PCI DSS, HIPAA, etc.). Pour des informations détaillées sur les fonctionnalités de sécurité Lambda, consultez la section Sécurité AWS Lambda dans le guide du développeur Lambda. Les seules considérations de sécurité supplémentaires pour les fonctions durables sont les autorisations de point de contrôle décrites dans ce guide. JavaScript est désactivé ou n'est pas disponible dans votre navigateur. Pour que vous puissiez utiliser la documentation AWS, Javascript doit être activé. Vous trouverez des instructions sur les pages d'aide de votre navigateur. Conventions de rédaction Exemples SDK d'exécution durable Cette page vous a-t-elle été utile ? - Oui Merci de nous avoir fait part de votre satisfaction. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer ce qui vous a plu afin que nous puissions nous améliorer davantage. Cette page vous a-t-elle été utile ? - Non Merci de nous avoir avertis que cette page avait besoin d'être retravaillée. Nous sommes désolés de ne pas avoir répondu à vos attentes. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer comment nous pourrions améliorer cette documentation. | 2026-01-13T09:29:30 |
https://id.atlassian.com/login?application=community--entry-auth&continue=https%3A%2F%2Fcommunity.atlassian.com%2Fforums%2Fs%2Fplugins%2Fcommon%2Ffeature%2Foauth2sso_v2%2Fsso_login_redirect%3Freferer%3Dhttps%3A%2F%2Fcommunity.atlassian.com%2Flearning%2Fhub%2Fadoption-and-change-management | Log in with Atlassian account Atlassian JavaScript is disabled You should enable JavaScript to work with this page. Atlassian JavaScript load error We tried to load scripts but something went wrong. Please make sure that your network settings allow you to download scripts from the following domain: https://id-frontend.prod-east.frontend.public.atl-paas.net | 2026-01-13T09:29:30 |
https://meeksfamily.uk/~michael/blog/2023/Mar/index.html | Stuff Michael Meeks is doing Stuff Michael Meeks is doing This is my (in)activity log. You might like to visit Collabora Productivity a subsidiary of Collabora focusing on LibreOffice support and services for whom I work. Also if you have the time to read this sort of stuff you could enlighten yourself by going to Unraveling Wittgenstein's net or if you are feeling objectionable perhaps here . Failing that, there are all manner of interesting things to read on the LibreOffice Planet news feed . Older items: 2023 : ( J F M A M J ), 2022 : ( J F M A M J J A S O N D ), 2021 , 2019 , 2018 , 2017 , 2016 , 2015 , 2014 , 2013 , 2012 , 2011 , 2010 , 2009 , 2009 , 2008 , 2007 , 2006 , 2005 , 2004 , 2003 , 2002 , 2001 , 2000 , 1999 , legacy html Fri, 31 Mar 2023 --> 2023-03-31 Friday Mail & admin backlog catchup - not as bad as expected; if much of the team is travelling - they're not mailing me it seems. Poked at BinaryDataContainer code that holds compressed images in memory (or swap). Thu, 30 Mar 2023 --> 2023-03-30 Thursday Up early, breakfast with the COOL-kids, packed and set off for an all-day mgmt meeting in the office. That sped by, then bid 'bye to all and sundry - ferried people to stations & Claire College, and home. Wed, 29 Mar 2023 --> 2023-03-29 Wednesday Breakfast, partner day: informal opening chat with Simon around various open-source topics, great talk from Robert. Product Management workshop - lots of interesting and sometimes unexpected input around what partners want: excitin & useful for our planning. Updates from Eloy & Naomi. Some of us went out punting in the rain - a very British experience - before a formal candle-lit dinner at Ridley. Bid a fond goodbye to people in waves until rather late at night having gone from pub to pub. Tue, 28 Mar 2023 --> 2023-03-28 Tuesday Up early, cooked breakfast; Kendy kindly compered the talks, Naomi's sorted out a great venue, fine food, lots of good company - packed a huge number of 5 minute talks in; thanks to all who spoke. Gave a thanks / summary / wrap-up of COOL days' technical track with some random prognostication: Out around town in a team with Robert, Cor & Tor for a ClueGo game/race thing - fun. Back for dinner at the college. Mon, 27 Mar 2023 --> 2023-03-27 Monday Mail chew, misc. admin & slideware bits. Packed, off to Claire College via the office to pick up some conference goodies. Met up with Naomi & welcomed people variously. Dinner at Millworks - good to see lots of people from the wider team & community - encouragingly COOL momentum. Sun, 26 Mar 2023 --> 2023-03-26 Sunday All Saints in the morning; H. played, pulled stops for the organ variously. Italo and Tiziana over for lunch - lovely to see them & spend some time together; dropped them back to the Fitz. Sat, 25 Mar 2023 --> 2023-03-25 Saturday Worked much of the day writing slides & preparing talks for COOL-days next week. J. cut the grass. Fri, 24 Mar 2023 --> 2023-03-24 Friday Mail chew, interview & offered a job. B&A over for lunch, partner meeting. Bit of code reading - knocked up a performance fix for our staging server. Setup various bitwarden bits to point at our vaultwarden server. Played with UCS somewhat with Mazin. Thu, 23 Mar 2023 --> 2023-03-23 Thursday Caught up with Miklos, COOL community call, more mail chew. Partner call, sync with Andras, catch up with Naomi and Eloy on COOL-days. Wed, 22 Mar 2023 --> 2023-03-22 Wednesday Up early, various trains, plane to Luton - some peace in the air to work on task backlog. Encouraging sales call, various other calls, caught up with admin. All Saints band practice, and out to collect M. and H. from Hills Road. J. and N. returned from Loughborough design engineering open day. Tue, 21 Mar 2023 --> 2023-03-21 Tuesday Up early; breakfast with Simon; got some E-mail chewed - call with Andras, and off to the venue. Caught up with people variously. Enjoyed presenting the work from the team included in Nextcloud Hub 4 alongside Nextcloud - some great progress & incisive analysis to enjoy. Out for dinner with remaining team; back to meet Simon's charming lady - Frieda; slept. Mon, 20 Mar 2023 --> 2023-03-20 Monday Up at 3am-ish, drove to Luton, flight to Berlin. Met up with the Nextclouders to practice for their big Nextcloud Hub 4 announcement tomorrow. Lovely to see them. Kindly hosted by Simon Tennant in the evening - really lovely to catch up with him properly after so long. Sun, 19 Mar 2023 --> 2023-03-19 Sunday All Saints in the morning - great to have Sam's son (Mary's great-grandson dedicated). Home for a pizza lunch, and presents for J. on Mothering Sunday. Caught up with babes, read stories, bed early. Sat, 18 Mar 2023 --> 2023-03-18 Saturday Up; J. at counselling training all day - out shopping for Mothering Sunday; replaced dripping mixer tap in downstairs toilet; had to use a dremel to angle-grind the (already rusted) steel screw-threads off, all for want of a little chromium in the steel. Got it sorted, and the plywood / tile facing cut to size. Out for a short walk with J. - then David over for pulled pork & a chance to catch up. Watched Chaos Walking in the evening. Fri, 17 Mar 2023 --> 2023-03-17 Friday Mail chew, dropped babes into school, woke up N. and encouraged her to print & submit her project. Admin, various calls. Celebrated N's project hand-in, read stories to babies. Thu, 16 Mar 2023 --> 2023-03-16 Thursday New bed arrived on a palette; chat with Miklos. COOL community call - couldn't run perf report on the server - out of memory; discovered perf archive - nice! but no good docs on how to effectively use it with perf report or hotspot . Client support call during lunch, chat with a customer. Catch up with Paris, and Andras. Lots of bed assembly and movement in the evening before house-group, and more bed work. Wed, 15 Mar 2023 --> 2023-03-15 Wednesday Encouraging sales call. Interview, admin, calls through the day, bit of profiling & code reading. Helped E. with her math homework. Tue, 14 Mar 2023 --> 2023-03-14 Tuesday Up early, run in the rain with J. mail, 1:1 with Kendy, catch up with Pedro, lunch, partner call, sync. on COOL-days schedule with Eloy & Naomi. Customer call, supplier call. Mon, 13 Mar 2023 --> 2023-03-13 Monday Up early, planning call, lunch, catch up with Paris. Out to Mike Tippet's funeral at All Saints - great talk, H. played organ, back. Calls variously, dinner, out to PCC re-ordering meeting. Sun, 12 Mar 2023 --> 2023-03-12 Sunday All Saints in the morning, guitar to fill-in for Beckie. Home, quick lunch, picked M. up from StAG youth house-party - a winner of the assassins game. Pizza dinner, relaxing variously. Sat, 11 Mar 2023 --> 2023-03-11 Saturday Up lateish, J. to AllSaints, provided on-hand debugging advice for N. much of the day. Tried to get memory trimming patch pushed; fell over amusing CI fails due to day-of-week dependent code in unit test at the weekend issue up-stream. Makes a pleasant change from random breakage introduced by me . Always bad when you have no recollection of writing the code , but the style shows it must have been you. Fri, 10 Mar 2023 --> 2023-03-10 Friday 8am sales call, partner & customer calls through the day, calmed down a runaway logging problem in a corner-case. Implemented a memory / cache trimming feature for inactive documents. Thu, 09 Mar 2023 --> 2023-03-09 Thursday Up early; E. off to have her toe looked at. Mail chew, chat to Miklos & Quikee, some digging into memory management, lunch, sync with Paris, customer call until late. Wed, 08 Mar 2023 --> 2023-03-08 Wednesday Up too early, mail chew, breakfast with Eloy & met some happy users in passing. Checked out, off to CS3, tried to catch up with some work, talked more to people. Enjoyed lunch with an enthusiastic Biochemist interested in visiting rather than sharing data. Off to the airport - Ryan Air ! - three plus hour wait for delayed flight; what a terrible service. Eventually got on a plane home. Tue, 07 Mar 2023 --> 2023-03-07 Tuesday Up later; breakfast with Eloy, worked on slides somewhat, off to the conference. More talks with people variously. Gave mine at the end of the day: Dinner with Eloy, sleep. Mon, 06 Mar 2023 --> 2023-03-06 Monday Up remarkably early, drove to Stansted, flight to Barcelona for CS3; plugged away at tasks on the plane. Arrived, lunch with Eloy. Listened to talks, met up and chatted with a number of great partners & customers for the afternoon. Out for Tapas in the evening with Frank, Bjoern & Eloy. Sun, 05 Mar 2023 --> 2023-03-05 Sunday All Saints in the morning, played with H. Robert spoke well on a letter to a church from Revelation. Home quickly to see M&D dropping by from Robert's. Lunch together, relaxed, out to help David S. install the first of several veluxen in his roof conversion; surprisingly heavy. Home, chatted with the parents until late. Sat, 04 Mar 2023 --> 2023-03-04 Saturday Up earlyish, off to R&A's for L's birthday party, good to see lots of the extended family over there and play balloon fights - with three-to-four small boys concurrently. Did some relaxing hackery in the evening having driven back; amazing what you find when you profile. Fri, 03 Mar 2023 --> 2023-03-03 Friday Out for a run with J.; a day of many calls, worked on CS3 slides & admin in gaps. Tried an on-line / video violin lesson for E. Thu, 02 Mar 2023 --> 2023-03-02 Thursday Mail chew, thrilled to see our work with Nextcloud and Deutsche Telekom around their great MagentaCLOUD announced . This brings Collabora Online (and LibreOffice technology ) to another large group of users, and lets us continue to invest to improve both COOL and the underlying LibreOffice technology for everyone; more in Steven's article . Also really pleased (something of a news roundup today) to see the EDPS piloting Collabora Online too with Nextcloud. FLOSS solutions that give you back your Digital Sovereignty: full control over your data, software, and IT stack are here. Catch-up with Miklos, COOL community call, lunch, catch up with William & Paris, then Lars & Andras, ESC call. Early tea with the family, up late. Wed, 01 Mar 2023 --> 2023-03-01 Wednesday Chat with Stelios, sales planning call; caught up with William, lunch. Partner call, introducing Anna, more calling action with William. My content in this blog and associated images / data under images/ and data/ directories are (usually) created by me and (unless obviously labelled otherwise) are licensed under the public domain, and/or if that doesn't float your boat a CC0 license. I encourage linking back (of course) to help people decide for themselves, in context, in the battle for ideas, and I love fixes / improvements / corrections by private mail. In case it's not painfully obvious: the reflections reflected here are my own; mine, all mine ! and don't reflect the views of Collabora, SUSE, Novell, The Document Foundation, Spaghetti Hurlers (International), or anyone else. It's also important to realise that I'm not in on the Swedish Conspiracy . Occasionally people ask for formal photos for conferences or fun . Michael Meeks ( michael.meeks@collabora.com ) | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/zh_tw/lambda/latest/dg/workflow-event-management.html | 管理 Lambda 工作流程與事件 - AWS Lambda 管理 Lambda 工作流程與事件 - AWS Lambda 文件 AWS Lambda 開發人員指南 具有耐用函數的程式碼優先協同運作 使用 Step Functions 協同運作工作流程 使用 EventBridge 與 EventBridge 排程器管理事件 本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。 管理 Lambda 工作流程與事件 使用 Lambda 建置無伺服器應用程式時，您通常需要協調函數執行和處理事件的方法。 AWS 提供數種方法來協調 Lambda 函數： Lambda 中用於程式碼優先工作流程協同運作的 Lambda 耐用函數 AWS Step Functions 用於跨多個 服務的視覺化工作流程協同運作 適用於事件驅動型架構和排程的 Amazon EventBridge 排程器和 Amazon EventBridge 您也可以將這些方法整合在一起。例如，您可以使用 EventBridge 排程器在特定事件發生時觸發持久函數或 Step Functions 工作流程，或設定工作流程在定義的執行點將事件發佈至 EventBridge 排程器。本節中的下列主題提供如何使用這些協同運作選項的詳細資訊。 具有耐用函數的程式碼優先協同運作 Lambda 耐用函數提供工作流程協同運作的程式碼優先方法，可讓您直接在 Lambda 函數內建置具狀態且長時間執行的工作流程。與外部協同運作服務不同，耐用的函數會將工作流程邏輯保留在程式碼中，讓您更輕鬆地搭配業務邏輯進行版本化、測試和維護。 當您需要時，耐用的函數是理想的選擇： 程式碼優先工作流程定義： 使用熟悉的程式設計語言定義工作流程，而不是使用 JSON 或視覺化設計工具 長時間執行的程序： 執行工作流程，最多可執行一年，遠超過標準 Lambda 函數的 15 分鐘限制 簡化開發： 將工作流程邏輯和商業邏輯保留在相同的程式碼庫中，以便於維護和測試 經濟實惠的等待： 在等待狀態期間暫停執行，而不耗用運算資源 內建狀態管理： 自動檢查點和狀態持續性，無需外部儲存組態 在耐久函數和 Step Functions 之間進行選擇 耐用函數和 Step Functions 都提供工作流程協同運作功能，但它們提供不同的使用案例： 考量事項 耐用的 函數 步驟函數 工作流程定義 Code-first (JavaScript、Python、Java) 以 JSON 為基礎的 Amazon States 語言或視覺化設計工具 開發方法 具有商業邏輯的單一程式碼庫 單獨的工作流程定義和函數程式碼 服務整合 透過 Lambda 函數程式碼和 AWS SDKs 與許多 AWS 服務的原生整合 執行持續時間 最長 1 年 最長 1 年 （標準）、5 分鐘 （快速） 平行處理 Promise.all() 和程式碼型模式 平行狀態和分散式映射 錯誤處理 Try-catch 區塊和自訂重試邏輯 內建重試和擷取狀態 視覺化監控 CloudWatch 日誌和自訂儀表板 視覺化執行圖表和詳細歷史記錄 最適合 以開發人員為中心的工作流程、複雜的商業邏輯、快速原型設計 多服務協同運作、視覺化工作流程、企業控管 在以下情況下使用耐用的函數： 您的團隊偏好程式碼優先開發方法 工作流程邏輯與業務邏輯緊密結合 您需要快速原型設計和反覆運算 您的工作流程主要涉及 Lambda 函數和簡單的服務呼叫 在下列情況下使用 Step Functions： 您需要視覺化工作流程設計和監控 您的工作流程會廣泛協調多個 AWS 服務 您需要企業控管和合規功能 非技術利益相關者需要了解工作流程邏輯 如需耐用函數的詳細資訊，請參閱 Lambda 的耐用函數 。 使用 Step Functions 協同運作工作流程 AWS Step Functions 是一種工作流程協同運作服務，可協助您將多個 Lambda 函數和其他 AWS 服務協調為結構化工作流程。這些工作流程可以維護狀態、使用複雜的重試機制處理錯誤，以及大規模處理資料。 Step Functions 提供兩種類型的工作流程，可滿足不同的協同運作需求： 標準工作流程 適用於需具備「恰好一次」執行語義、執行時間較長且可稽核的工作流程。標準工作流程最長可以執行一年，提供詳細的執行歷史記錄，並支援視覺化偵錯功能。此類型適用於訂單履行、資料處理管道或多步驟分析任務等流程。 快速工作流程 專為具備「至少一次」執行語義、高事件量且執行時間短的工作負載而設計。快速工作流程最長可執行五分鐘，非常適合大量事件處理、串流資料轉換或 IoT 資料擷取案例。相較於標準工作流程，此類型提供的輸送量更高，成本可能更低。 注意 如需有關 Step Functions 工作流程類型的詳細資訊，請參閱 Choosing workflow type in Step Functions 。 在此類工作流程中，Step Functions 提供兩種類型的映射狀態，用於實現平行處理： 內嵌映射 在父工作流程的執行歷史記錄中處理來自 JSON 陣列的項目。內嵌映射最多支援 40 個並行迭代，適用於較小的資料集或需要將所有處理保持在單次執行內的情況。如需詳細資訊，請參閱 Using Map state in Inline mode 。 分散式映射 透過迭代處理超過 256 KiB 或需要超過 40 個並行迭代的資料集，實現對大規模平行工作負載的處理。分散式映射可支援最多 10,000 個平行子工作流程執行，擅長處理儲存在 Amazon S3 中的半結構化資料 (例如 JSON 或 CSV 檔案)，因此非常適合批次處理與 ETL 操作。如需詳細資訊，請參閱 Using Map state in Distributed mode 。 透過結合這些工作流程類型與映射狀態，Step Functions 提供了靈活且強大的工具集，能夠從小型操作到大型資料處理管道，全面協同運作複雜的無伺服器應用程式。 若要開始將 Lambda 與 Step Functions 搭配使用，請參閱 使用 Step Functions 協同運作 Lambda 函式 。 使用 EventBridge 與 EventBridge 排程器管理事件 Amazon EventBridge 是一項事件匯流排服務，可協助建置事件驅動型架構。它會路由 AWS 服務、整合應用程式和軟體即服務 (SaaS) 應用程式之間的事件。EventBridge 排程器是一種無伺服器排程器，可讓您從一個中央服務建立、執行並管理任務，允許您使用 Cron 和 Rate 表達式依排程調用 Lambda 函式，或設定一次性調用函式。 Amazon EventBridge 和 EventBridge 排程器可協助使用 Lambda 建置事件驅動型架構。EventBridge 會路由 AWS 服務、整合應用程式和 SaaS 應用程式之間的事件，而 EventBridge 排程器則提供特定排程功能，以定期或一次性叫用 Lambda 函數。 這些服務為使用 Lambda 函式提供數種關鍵功能： 使用 EventBridge 建立規則來比對事件，並將其路由至 Lambda 函式 使用 EventBridge 排程器設定以 Cron 與 Rate 表達式驅動的週期性函式調用 在特定日期和時間設定一次性函式調用 為排程調用定義彈性時段與重試政策 如需詳細資訊，請參閱 依排程調用 Lambda 函數 。 您的瀏覽器已停用或無法使用 Javascript。 您必須啟用 Javascript，才能使用 AWS 文件。請參閱您的瀏覽器說明頁以取得說明。 文件慣用形式 Powertools for AWS Lambda Lambda 耐用函數 此頁面是否有幫助？ - 是 感謝您，讓我們知道我們做得很好！ 若您有空，歡迎您告知我們值得讚許的地方，這樣才能保持良好服務。 此頁面是否有幫助？ - 否 感謝讓我們知道此頁面仍須改善。很抱歉，讓您失望。 若您有空，歡迎您提供改善文件的方式。 | 2026-01-13T09:29:30 |
https://reports.jenkins.io/jelly-taglib-ref.html#hudson.3AbuildCaption | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/id_id/lambda/latest/dg/durable-best-practices.html | Praktik terbaik untuk fungsi tahan lama Lambda - AWS Lambda Praktik terbaik untuk fungsi tahan lama Lambda - AWS Lambda Dokumentasi AWS Lambda Panduan Developerr Tulis kode deterministik Desain untuk idempotensi Kelola negara secara efisien Rancang langkah-langkah efektif Gunakan operasi tunggu secara efisien Pertimbangan tambahan Sumber daya tambahan Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Praktik terbaik untuk fungsi tahan lama Lambda Fungsi tahan lama menggunakan model eksekusi berbasis replay yang membutuhkan pola berbeda dari fungsi Lambda tradisional. Ikuti praktik terbaik ini untuk membangun alur kerja yang andal dan hemat biaya. Tulis kode deterministik Selama pemutaran ulang, fungsi Anda berjalan dari awal dan harus mengikuti jalur eksekusi yang sama dengan proses aslinya. Kode di luar operasi tahan lama harus deterministik, menghasilkan hasil yang sama dengan input yang sama. Bungkus operasi non-deterministik dalam langkah-langkah: Pembuatan angka acak dan UUIDs Waktu atau stempel waktu saat ini Panggilan API eksternal dan kueri database Operasi sistem file TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; import { randomUUID } from 'crypto'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Generate transaction ID inside a step const transactionId = await context.step('generate-transaction-id', async () => { return randomUUID(); }); // Use the same ID throughout execution, even during replay const payment = await context.step('process-payment', async () => { return processPayment(event.amount, transactionId); }); return { statusCode: 200, transactionId, payment }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext import uuid @durable_execution def handler(event, context: DurableContext): # Generate transaction ID inside a step transaction_id = context.step( lambda _: str(uuid.uuid4()), name='generate-transaction-id' ) # Use the same ID throughout execution, even during replay payment = context.step( lambda _: process_payment(event['amount'], transaction_id), name='process-payment' ) return { 'statusCode': 200, 'transactionId': transaction_id, 'payment': payment} Penting Jangan gunakan variabel global atau penutupan untuk berbagi status antar langkah. Lewati data melalui nilai pengembalian. Status global rusak selama pemutaran ulang karena langkah-langkah mengembalikan hasil yang di-cache tetapi variabel global diatur ulang. Hindari mutasi penutupan: Variabel yang ditangkap dalam penutupan dapat kehilangan mutasi selama pemutaran ulang. Langkah-langkah mengembalikan hasil cache, tetapi pembaruan variabel di luar langkah tidak diputar ulang. TypeScript // ❌ WRONG: Mutations lost on replay export const handler = withDurableExecution(async (event, context) => { let total = 0; for (const item of items) { await context.step(async () => { total += item.price; // ⚠️ Mutation lost on replay! return saveItem(item); }); } return { total }; // Inconsistent value! }); // ✅ CORRECT: Accumulate with return values export const handler = withDurableExecution(async (event, context) => { let total = 0; for (const item of items) { total = await context.step(async () => { const newTotal = total + item.price; await saveItem(item); return newTotal; // Return updated value }); } return { total }; // Consistent! }); // ✅ EVEN BETTER: Use map for parallel processing export const handler = withDurableExecution(async (event, context) => { const results = await context.map( items, async (ctx, item) => { await ctx.step(async () => saveItem(item)); return item.price; } ); const total = results.getResults().reduce((sum, price) => sum + price, 0); return { total }; }); Python # ❌ WRONG: Mutations lost on replay @durable_execution def handler(event, context: DurableContext): total = 0 for item in items: context.step( lambda _: save_item_and_mutate(item, total), # ⚠️ Mutation lost on replay! name=f'save-item- { item["id"]}' ) return { 'total': total} # Inconsistent value! # ✅ CORRECT: Accumulate with return values @durable_execution def handler(event, context: DurableContext): total = 0 for item in items: total = context.step( lambda _: save_item_and_return_total(item, total), name=f'save-item- { item["id"]}' ) return { 'total': total} # Consistent! # ✅ EVEN BETTER: Use map for parallel processing @durable_execution def handler(event, context: DurableContext): def process_item(ctx, item): ctx.step(lambda _: save_item(item)) return item['price'] results = context.map(items, process_item) total = sum(results.get_results()) return { 'total': total} Desain untuk idempotensi Operasi dapat dijalankan beberapa kali karena mencoba ulang atau memutar ulang. Operasi non-idempoten menyebabkan efek samping duplikat seperti menagih pelanggan dua kali atau mengirim beberapa email. Gunakan token idempotensi: Hasilkan token di dalam langkah-langkah dan sertakan dengan panggilan API eksternal untuk mencegah operasi duplikat. TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Generate idempotency token once const idempotencyToken = await context.step('generate-idempotency-token', async () => { return crypto.randomUUID(); }); // Use token to prevent duplicate charges const charge = await context.step('charge-payment', async () => { return paymentService.charge( { amount: event.amount, cardToken: event.cardToken, idempotencyKey: idempotencyToken }); }); return { statusCode: 200, charge }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext import uuid @durable_execution def handler(event, context: DurableContext): # Generate idempotency token once idempotency_token = context.step( lambda _: str(uuid.uuid4()), name='generate-idempotency-token' ) # Use token to prevent duplicate charges def charge_payment(_): return payment_service.charge( amount=event['amount'], card_token=event['cardToken'], idempotency_key=idempotency_token ) charge = context.step(charge_payment, name='charge-payment') return { 'statusCode': 200, 'charge': charge} Gunakan at-most-once semantik: Untuk operasi kritis yang tidak boleh diduplikasi (transaksi keuangan, pengurangan inventaris), konfigurasikan mode eksekusi. at-most-once TypeScript // Critical operation that must not duplicate await context.step('deduct-inventory', async () => { return inventoryService.deduct(event.productId, event.quantity); }, { executionMode: 'AT_MOST_ONCE_PER_RETRY' }); Python # Critical operation that must not duplicate context.step( lambda _: inventory_service.deduct(event['productId'], event['quantity']), name='deduct-inventory', config=StepConfig(execution_mode='AT_MOST_ONCE_PER_RETRY') ) Idempotensi basis data: Gunakan check-before-write pola, pembaruan bersyarat, atau operasi upsert untuk mencegah duplikat catatan. Kelola negara secara efisien Setiap pos pemeriksaan menyimpan status ke penyimpanan persisten. Objek status besar meningkatkan biaya, pos pemeriksaan lambat, dan kinerja dampak. Simpan hanya data koordinasi alur kerja yang penting. Pertahankan status minimal: Simpan IDs dan referensi, bukan objek penuh Ambil data terperinci dalam langkah-langkah sesuai kebutuhan Gunakan Amazon S3 atau DynamoDB untuk data besar, teruskan referensi dalam status Hindari melewatkan muatan besar di antara langkah-langkah TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Store only the order ID, not the full order object const orderId = event.orderId; // Fetch data within each step as needed await context.step('validate-order', async () => { const order = await orderService.getOrder(orderId); return validateOrder(order); }); await context.step('process-payment', async () => { const order = await orderService.getOrder(orderId); return processPayment(order); }); return { statusCode: 200, orderId }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext @durable_execution def handler(event, context: DurableContext): # Store only the order ID, not the full order object order_id = event['orderId'] # Fetch data within each step as needed context.step( lambda _: validate_order(order_service.get_order(order_id)), name='validate-order' ) context.step( lambda _: process_payment(order_service.get_order(order_id)), name='process-payment' ) return { 'statusCode': 200, 'orderId': order_id} Rancang langkah-langkah efektif Langkah-langkah adalah unit dasar kerja dalam fungsi yang tahan lama. Langkah-langkah yang dirancang dengan baik membuat alur kerja lebih mudah dipahami, di-debug, dan dipelihara. Prinsip desain langkah: Gunakan nama deskriptif - Nama seperti validate-order alih-alih step1 membuat log dan kesalahan lebih mudah dipahami Pertahankan nama statis - Jangan gunakan nama dinamis dengan cap waktu atau nilai acak. Nama langkah harus deterministik untuk diputar ulang Granularitas keseimbangan - Pecahkan operasi kompleks menjadi langkah-langkah yang terfokus, tetapi hindari langkah-langkah kecil yang berlebihan yang meningkatkan overhead pos pemeriksaan Operasi terkait kelompok - Operasi yang harus berhasil atau gagal bersama termasuk dalam langkah yang sama Gunakan operasi tunggu secara efisien Tunggu operasi menangguhkan eksekusi tanpa menghabiskan sumber daya atau menimbulkan biaya. Gunakan mereka alih-alih menjaga Lambda tetap berjalan. Penantian berbasis waktu: Gunakan context.wait() untuk penundaan, bukan atau. setTimeout sleep Callback eksternal: Gunakan context.waitForCallback() saat menunggu sistem eksternal. Selalu atur batas waktu untuk mencegah penantian yang tidak terbatas. Polling: Gunakan context.waitForCondition() dengan backoff eksponensial untuk melakukan polling layanan eksternal tanpa membebani mereka. TypeScript // Wait 24 hours without cost await context.wait( { seconds: 86400 }); // Wait for external callback with timeout const result = await context.waitForCallback( 'external-job', async (callbackId) => { await externalService.submitJob( { data: event.data, webhookUrl: `https://api.example.com/callbacks/$ { callbackId}` }); }, { timeout: { seconds: 3600 } } ); Python # Wait 24 hours without cost context.wait(86400) # Wait for external callback with timeout result = context.wait_for_callback( lambda callback_id: external_service.submit_job( data=event['data'], webhook_url=f'https://api.example.com/callbacks/ { callback_id}' ), name='external-job', config=WaitForCallbackConfig(timeout_seconds=3600) ) Pertimbangan tambahan Penanganan kesalahan: Coba lagi kegagalan sementara seperti batas waktu jaringan dan batas tarif. Jangan mencoba lagi kegagalan permanen seperti kesalahan input atau otentikasi yang tidak valid. Konfigurasikan strategi coba lagi dengan upaya maksimal dan tingkat backoff yang sesuai. Untuk contoh rinci, lihat Penanganan kesalahan dan percobaan ulang . Kinerja: Minimalkan ukuran pos pemeriksaan dengan menyimpan referensi alih-alih muatan penuh. Gunakan context.parallel() dan context.map() untuk menjalankan operasi independen secara bersamaan. Operasi terkait batch untuk mengurangi overhead pos pemeriksaan. Versioning: Memanggil fungsi dengan nomor versi atau alias untuk menyematkan eksekusi ke versi kode tertentu. Pastikan versi kode baru dapat menangani status dari versi yang lebih lama. Jangan mengganti nama langkah atau mengubah perilaku mereka dengan cara yang merusak pemutaran ulang. Serialisasi: Gunakan tipe yang kompatibel dengan JSON untuk input dan hasil operasi. Konversikan tanggal ke string ISO dan objek kustom menjadi objek biasa sebelum meneruskannya ke operasi yang tahan lama. Pemantauan: Aktifkan pencatatan terstruktur dengan nama eksekusi IDs dan langkah. Siapkan CloudWatch alarm untuk tingkat kesalahan dan durasi eksekusi. Gunakan penelusuran untuk mengidentifikasi kemacetan. Untuk panduan terperinci, lihat Monitoring dan debugging . Pengujian: Uji jalur bahagia, penanganan kesalahan, dan perilaku pemutaran ulang. Uji skenario batas waktu untuk panggilan balik dan menunggu. Gunakan pengujian lokal untuk mengurangi waktu iterasi. Untuk panduan terperinci, lihat Menguji fungsi tahan lama . Kesalahan umum yang harus dihindari: Jangan membuat context.step() panggilan sarang, gunakan konteks anak sebagai gantinya. Bungkus operasi non-deterministik dalam langkah-langkah. Selalu atur batas waktu untuk callback. Seimbangkan granularitas langkah dengan overhead pos pemeriksaan. Simpan referensi alih-alih objek besar dalam keadaan. Sumber daya tambahan Dokumentasi Python SDK - Referensi API lengkap, pola pengujian, dan contoh lanjutan TypeScript Dokumentasi SDK - Referensi API lengkap, pola pengujian, dan contoh lanjutan Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Memantau fungsi tahan lama Instans Terkelola Lambda Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/zh_tw/lambda/latest/dg/durable-functions.html#durable-functions-how-it-works | Lambda 耐用函數 - AWS Lambda Lambda 耐用函數 - AWS Lambda 文件 AWS Lambda 開發人員指南 主要優點 運作方式 何時使用耐用函數 後續步驟 本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。 Lambda 耐用函數 Lambda 耐用函數可讓您建置彈性的多步驟應用程式和 AI 工作流程，可執行長達一年，同時在中斷的情況下保持可靠的進度。當持久性函數執行時，這個完整的生命週期稱為持久性執行，它使用檢查點來追蹤進度，並透過重新執行自動從失敗中復原，從頭開始重新執行，同時略過完成的工作。 在每個函數中，您會使用耐用的操作做為基本的建置區塊。步驟會使用內建重試和進度追蹤來執行商業邏輯，同時等待暫停執行而不會產生運算費用，因此非常適合長時間執行的程序human-in-the-loop工作流程或輪詢外部相依性。無論您是在處理訂單、協調微服務或協調代理式 AI 應用程式，當您使用熟悉的程式設計語言編寫程式碼時，耐用的函數會自動維持狀態並從失敗中復原。 主要優點 自然撰寫彈性程式碼： 使用熟悉的程式設計建構，您可以撰寫自動處理失敗的程式碼。內建檢查點、透明重試和自動復原意味著您的商業邏輯保持乾淨且專注。 僅為您使用的項目付費： 在等待操作期間，您的函數會暫停，而不會產生運算費用。對於等待數小時或數天的長時間執行工作流程，您只需支付實際處理時間，而非閒置等待。 操作簡單： 使用 Lambda 的無伺服器模型，您可以自動擴展，包括scale-to-zero，而無需管理基礎設施。耐用的函數會自動處理狀態管理、重試邏輯和故障復原，從而降低營運開銷。 運作方式 在幕後，耐用的函數是一般的 Lambda 函數，使用檢查點/重播機制來追蹤進度，並透過使用者定義的暫停點支援長時間執行的操作，通常稱為耐用執行。當持久的函數從等待點繼續，或像重試一樣中斷時，系統會執行重播。在重播期間，您的程式碼會從頭開始執行，但會略過已完成的檢查點，使用儲存的結果，而不是重新執行已完成的操作。此重播機制可確保一致性，同時啟用長時間執行的執行。 函數從暫停或中斷恢復後，系統會執行重播。在重播期間，您的程式碼會從頭開始執行，但會略過已完成的檢查點，使用儲存的結果，而不是重新執行已完成的操作。此重播機制可確保一致性，同時啟用長時間執行的執行。 為了在您的應用程式中利用此checkpoint-and-replay機制，Lambda 提供耐用的執行 SDK。開發套件可消除管理檢查點和重播的複雜性，公開您在程式碼中使用的稱為耐久操作的簡單基本概念。開發套件適用於 JavaScript、TypeScript 和 Python，可與您現有的 Lambda 開發工作流程無縫整合。 使用 SDK，您可以包裝 Lambda 事件處理常式，然後提供 DurableContext 與您的事件並行。此內容可讓您存取耐用的操作，例如步驟和等待。您可以將函數邏輯寫入為一般循序程式碼，但不會直接呼叫 服務，而是將這些呼叫包裝為自動檢查點和重試的步驟。當您需要暫停執行時，您可以新增暫停函數的等待，而不會產生費用。開發套件可處理所有複雜的狀態管理和在幕後重播，讓您的程式碼保持乾淨且可讀取。 何時使用耐用函數 短期協調： 透過自動轉返失敗，協調跨多項服務的付款、庫存和運送。透過驗證、付款授權、庫存分配和履行來處理訂單，並保證完成。 安心處理付款： 建立彈性付款流程，透過失敗維持交易狀態，並自動處理重試。協調跨付款供應商的多步驟授權、詐騙檢查和和解，並跨步驟進行完整稽核。 建置可靠的 AI 工作流程： 建立多步驟 AI 工作流程，以鏈結模型呼叫、整合人工意見回饋，並在失敗期間果斷地處理長時間執行的任務。停用後自動繼續，且只需支付作用中的執行時間。 協調複雜的訂單履行： 使用內建彈性協調跨庫存、付款、運送和通知系統的訂單處理。自動處理部分故障、保留中斷時的順序狀態，並有效率地等待外部事件，而不會耗用運算資源。 自動化多步驟業務工作流程： 為員工加入、貸款核准和跨越數天或數週的合規程序建立可靠的工作流程。維護跨人工核准、系統整合和排程任務的工作流程狀態，同時提供程序狀態和歷史記錄的完整可見性。 後續步驟 開始使用耐用的 函數 探索耐用的執行 SDK 監控和偵錯耐用函數 檢閱安全性和許可 遵循最佳實務 您的瀏覽器已停用或無法使用 Javascript。 您必須啟用 Javascript，才能使用 AWS 文件。請參閱您的瀏覽器說明頁以取得說明。 文件慣用形式 工作流程與事件 基本概念 此頁面是否有幫助？ - 是 感謝您，讓我們知道我們做得很好！ 若您有空，歡迎您告知我們值得讚許的地方，這樣才能保持良好服務。 此頁面是否有幫助？ - 否 感謝讓我們知道此頁面仍須改善。很抱歉，讓您失望。 若您有空，歡迎您提供改善文件的方式。 | 2026-01-13T09:29:30 |
https://www.linkedin.com/jobs/view/account-executive-ps-ms-at-pivotree-4301096332?position=2&pageNum=0&refId=%2BXRAFRizTpYP%2FZZY412ABA%3D%3D&trackingId=M08sCmHwIXC1S0PNuwBqQw%3D%3D | Pivotree hiring Account Executive (PS/MS) in Greater Chicago Area | LinkedIn Skip to main content LinkedIn Account Executive (PS/MS) in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Sign in Create an account Account Executive (PS/MS) Pivotree Greater Chicago Area Apply Account Executive (PS/MS) Pivotree Greater Chicago Area 8 hours ago Over 200 applicants See who Pivotree has hired for this role Apply Save Report this job Direct message the job poster from Pivotree Brad McLaughlin Brad McLaughlin Senior Technical Recruiter at Pivotree Position Summary As an Account Executive with a specialized focus on acquiring new logos, your primary responsibility is to drive revenue growth by identifying, prospecting, and closing new business opportunities. You will leverage your strong sales acumen and strategic thinking to engage with prospective clients, understand their unique needs and challenges, and effectively articulate how our products or services can address those needs and deliver value. Roles & Responsibilities: ● Prospect and develop direct new client relationships, convert leads into opportunities and close new logos and revenue ● Conduct research to understand target market, competitive landscape and potential client’s business objectives and pain points. ● Build and identify a robust sales pipeline by consistently identifying and pursuing new opportunities, managing the entire sales process from lead generation to contract negotiations and closure. ● Collaborate closely with cross functional teams, including marketing, product development, to ensure alignment and support through the deal cycle. ● Leverage effective sales strategies, including consultative selling, value based selling and solution selling to articulate the unique value proposition of our offering and differentiate us from competitors. ● Provide accurate sales forecasts and regular updates to sales pipeline, activities and progress against targets to management ● Continuously strive to overachieve sales targets and KPIs, while maintaining high levels of customer satisfaction. Key Skills and Competencies: ● 8+ years of high performance sales with consultative solutions into large enterprises. ● 3+ years as a large account manager for digital, e-commerce, management consulting or complex systems integration solutions ● Data-driven selling experience: Has successfully used sales processes, analytics and methodologies to obtain predictable revenue ● Performance-driven: Has a bias for action and results — an energetic, highly motivated person who relishes challenges and tirelessly pursues objectives. Proven track record in previous positions ● Curiosity: ability to understand through effective questioning and listening ● Desired domain experience: e-commerce, digital marketing, product content management (PIM / PCM / MDM), search, web analytics, web content management, user experience (UX) ● Strong written, verbal and presentation skills; able to adapt to a wide variety of audiences ● Entrepreneurial, high energy, self-motivated, assertive; consummate professional ● Ability to react quickly, assess, and resolve problems ● Well versed with CRM tools to manage sales and accounts (salesforce.com) ● Bachelor's Degree Pivotree is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive and accessible workplace. Show more Show less Seniority level Mid-Senior level Employment type Full-time Job function Sales, Consulting, and Business Development Industries IT Services and IT Consulting, IT System Custom Software Development, and Software Development Referrals increase your chances of interviewing at Pivotree by 2x See who you know Get notified when a new job is posted. Set alert Sign in to set job alerts for “Account Executive” roles. Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Similar jobs Account Executive Account Executive REVOLUTION BEAUTY Chicago, IL 2 weeks ago Remote SMB AE - $175-$200k OTE (Cybersecurity) Remote SMB AE - $175-$200k OTE (Cybersecurity) CyberCoders Chicago, IL $175,000.00 - $200,000.00 2 weeks ago Mid-Market Account Executive - PubSec Mid-Market Account Executive - PubSec Samsara Chicago, IL $136,240.00 - $170,300.00 1 week ago Account Executive, Commercial Account Executive, Commercial Level Access Greater Chicago Area 5 days ago Retail Vertical Account Executive Retail Vertical Account Executive enosix Chicago, IL 6 months ago Account Executive, SMB Account Executive, SMB Karbon Chicago, IL $60,000.00 - $130,000.00 1 week ago Account Executive - SMB Sales Account Executive - SMB Sales WorkWave Chicago, IL $70,000.00 - $118,000.00 1 month ago Account Executive Account Executive Rise25 Chicago, IL 2 years ago Account Executive - North Central Account Executive - North Central Jitterbit Chicago, IL 2 days ago Account Executive in Chicago Account Executive in Chicago PRACTICE Chicago, IL $70,000.00 - $300,000.00 3 weeks ago Account Manager - SMB Sales Account Manager - SMB Sales WorkWave Chicago, IL $65,000.00 - $105,000.00 2 months ago Sales Account Executive Sales Account Executive Yang Ming Marine Transport Corp. Chicago, IL 6 days ago Sr. Amazon Account Manager Sr. Amazon Account Manager Envision Horizons Chicago, IL $90,000.00 - $140,000.00 1 month ago Account Executive | Remote | AI SaaS Sales Role Account Executive | Remote | AI SaaS Sales Role Process Street Chicago, IL 5 months ago Strategic Account Executive Strategic Account Executive D-ID Chicago, IL $200,000.00 - $300,000.00 1 month ago Salesforce Account Executive Salesforce Account Executive Madison Ave Consulting Chicago, IL $100,000.00 - $110,000.00 6 days ago Account Executive Account Executive Orca Security Greater Chicago Area 1 week ago Account Executive Account Executive NCD Chicago, IL 2 months ago Enterprise Account Executive, Federal Public Sector Enterprise Account Executive, Federal Public Sector Asana Chicago, IL $145,000.00 - $165,000.00 2 weeks ago National Account Manager National Account Manager Daniels Health Chicago, IL $140,073.00 - $180,179.00 6 days ago Account Executive Account Executive JumpSeat Chicago, IL 1 month ago Sr. Account Director, Enterprise - 11047 Sr. Account Director, Enterprise - 11047 Coupa Chicago, IL 4 days ago Manufacturing Vertical Account Executive Manufacturing Vertical Account Executive enosix Chicago, IL 6 months ago Sales Account Manager Sales Account Manager The HRT Club Greater Chicago Area $80,000.00 - $85,000.00 3 weeks ago Copier Account Executive Copier Account Executive ECLARO Chicago, IL $75,000.00 - $90,000.00 5 days ago National/Regional Account Executive National/Regional Account Executive Korn Ferry Chicago, IL $200,000.00 - $300,000.00 2 weeks ago Account Executive Account Executive Miter Chicago, IL $200,000.00 - $210,000.00 2 months ago Show more jobs like this Show fewer jobs like this People also viewed Technical Account Manager - Commerce / Partner Success (100% Remote - USA) Technical Account Manager - Commerce / Partner Success (100% Remote - USA) Hopper Chicago, IL $160,000.00 - $250,000.00 1 week ago Account Executive, Mid-Market - 11043 Account Executive, Mid-Market - 11043 Coupa Chicago, IL 6 days ago Founding Account Executive | Legal Tech (Full-Cycle Hunter) Founding Account Executive | Legal Tech (Full-Cycle Hunter) Wamy Chicago, IL $150,000.00 - $200,000.00 1 month ago Mid-Market Account Executive, SaaS Sales -- North Central Mid-Market Account Executive, SaaS Sales -- North Central DeleteMe Chicago, IL $140,000.00 - $180,000.00 1 month ago Global Account Director - New Business Global Account Director - New Business QAD Chicago, IL $130,000.00 - $150,000.00 1 week ago Account Executive Account Executive MES Solutions Glen Ellyn, IL 1 week ago Account Executive Account Executive BusPlanner Chicago, IL 3 months ago Key Account Director Key Account Director Caresyntax Chicago, IL 1 month ago Account Executive Account Executive Hawthorne Executive Search Greater Chicago Area 11 hours ago Key Account Director - Chicago based Key Account Director - Chicago based Cullerton Group Greater Chicago Area 2 days ago Similar Searches Enterprise Account Executive jobs 44,389 open jobs Commercial Account Executive jobs 35,633 open jobs Clinical Sales Consultant jobs 947 open jobs Account Executive Recruiter jobs 148 open jobs Account Manager jobs 121,519 open jobs Federal Account Executive jobs 2,380 open jobs Sales Account Executive jobs 85,131 open jobs Junior Account Executive jobs 60,161 open jobs Strategic Account Executive jobs 37,453 open jobs Trainee Account Executive jobs 25 open jobs Finance Executive jobs 55,259 open jobs Sales Executive jobs 122,628 open jobs Public Relations Account Executive jobs 27,160 open jobs Healthcare Account Executive jobs 28,204 open jobs Media Account Executive jobs 28,250 open jobs Wholesale Account Executive jobs 3,456 open jobs Logistics Account Executive jobs 88,964 open jobs Senior Account Executive jobs 62,248 open jobs Marketing Account Executive jobs 34,745 open jobs New Business Account Executive jobs 23,413 open jobs Advertising Sales Account Executive jobs 3,696 open jobs Technical Account Executive jobs 5,560 open jobs Inside Account Executive jobs 29,552 open jobs Associate Account Executive jobs 27,981 open jobs International Account Executive jobs 30,392 open jobs Show more Show less Explore collaborative articles We’re unlocking community knowledge in a new way. Experts add insights directly into each article, started with the help of AI. Explore More More searches More searches Kenaitze Indian Tribe jobs Advantage Technologies jobs Enterprise Account Executive jobs kite jobs Commercial Account Executive jobs Rock Island Auction Company jobs Clinical Sales Consultant jobs RateGenius jobs Thomas Printworks jobs Union jobs Account Executive Recruiter jobs Account Manager jobs Federal Account Executive jobs Sales Account Executive jobs Junior Account Executive jobs Strategic Account Executive jobs Sterling-Hoffman Life Sciences jobs Trainee Account Executive jobs Finance Executive jobs Sales Executive jobs CUSD jobs Public Relations Account Executive jobs Healthcare Account Executive jobs Media Account Executive jobs Senior Living Management jobs Wholesale Account Executive jobs Logistics Account Executive jobs Senior Account Executive jobs Marketing Account Executive jobs New Business Account Executive jobs Advertising Sales Account Executive jobs Technical Account Executive jobs Inside Account Executive jobs Associate Account Executive jobs International Account Executive jobs Senior Business Development Representative jobs Corporate Account Executive jobs Business Account Executive jobs Advertising Account Executive jobs Digital Account Executive jobs Account Executive Intern jobs Named Account Executive jobs Account Manager Financial Services jobs Business Development Representative jobs Channel Account Executive jobs Executive Account Manager jobs Territory Account Executive jobs Public Sector Account Executive jobs CleanPower jobs Major Account Executive jobs Inside Sales Account Executive jobs Regional Account Executive jobs Enterprise Account Manager jobs OnCall jobs American Public Works Association jobs Services Account Executive jobs International Financial Advisor jobs Software Account Executive jobs Outside Sales Account Executive jobs Customer Account Executive jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at Pivotree Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T09:29:30 |
https://meeksfamily.uk/~michael/blog/2022/Mar/index.html | Stuff Michael Meeks is doing Stuff Michael Meeks is doing This is my (in)activity log. You might like to visit Collabora Productivity a subsidiary of Collabora focusing on LibreOffice support and services for whom I work. Also if you have the time to read this sort of stuff you could enlighten yourself by going to Unraveling Wittgenstein's net or if you are feeling objectionable perhaps here . Failing that, there are all manner of interesting things to read on the LibreOffice Planet news feed . Older items: 2023 : ( J F M A M J ), 2022 : ( J F M A M J J A S O N D ), 2021 , 2019 , 2018 , 2017 , 2016 , 2015 , 2014 , 2013 , 2012 , 2011 , 2010 , 2009 , 2009 , 2008 , 2007 , 2006 , 2005 , 2004 , 2003 , 2002 , 2001 , 2000 , 1999 , legacy html Thu, 31 Mar 2022 --> 2022-03-31 Thursday Slept poorly; un-screwed leaking drain with H's help. Wow; full of solids nearly to the brim, after some investigation discovered the hole filled with a metre cubed bulk sand bag and some rocks: which had been acting as a solid filter presumably since construction by Pete Mathews Home Improvements Ltd. not great. Set too trowling the volume down with H's help. Interupted by a pleasant call with Simon & Nick at Linux Format and lunch. Worked on delta cache pieces until J. returned. Finally solved the plumbing issue by the evening; grim. You don't realize how wonderful modern sanitation is until it doesn't work. Wed, 30 Mar 2022 --> 2022-03-30 Wednesday Shut the bathrooms draining into the dodgy manhole; still have some free capacity luckiy. Waited for drain people to arrive. Sales call, some marketing bits; more delta debugging. No-one arrived to charge us some hundreds of pounds to unblock the drains by the late evening - hey ho. Tue, 29 Mar 2022 --> 2022-03-29 Tuesday Managed to reproduce an annoying Online crash; Aron got a nice reproducer good to get that fixed. Discovered the drains not draining - things from upstairs coming out downstairs: not cool. Called emergency drain un-blockers - picked the one that gave a quote in pounds for tomorrow. Mon, 28 Mar 2022 --> 2022-03-28 Monday Pleased to find SSL issue fixed & released. Planning calls; came to do tax & annual accounting to discover a failed bank-pin RSA dongle - why is the battery not user-serviceable ? odd. Sun, 27 Mar 2022 --> 2022-03-27 Sunday All Saints, J. ran Kids For Christ (KFC). Relaxed. Sat, 26 Mar 2022 --> 2022-03-26 Saturday Building in the garage with David; got more of the next wall insulated, plaster-boarded and so on. Up very late working with Ash on a rather surprising SSL related regression. Fri, 25 Mar 2022 --> 2022-03-25 Friday Some hacking time at last - lots of progress on improving delta + keyframe compression and storage - nice. Catch-up call with Gerald. Relaxed and caught up with H. who helped with the garage building work somewhere here. Thu, 24 Mar 2022 --> 2022-03-24 Thursday N. got a positive COVID test - and started self-isolating, M. to the dentist, H. home - really lovely to see her after so long. COOL community call, admin etc. Wed, 23 Mar 2022 --> 2022-03-23 Wednesday Sales calls, band practice. Tue, 22 Mar 2022 --> 2022-03-22 Tuesday 1:1's variously. Mon, 21 Mar 2022 --> 2022-03-21 Monday Took babes to school; planning calls; mail chew, marketing catch-up. Sun, 20 Mar 2022 --> 2022-03-20 Sunday All Saints; fine lunch, slugging. Sat, 19 Mar 2022 --> 2022-03-19 Saturday David over; got much more stud-work with ply screwed to the garage ceiling, floor, fibre-glass into sections and plasterboard onto the back wall. Fri, 18 Mar 2022 --> 2022-03-18 Friday Mail & admin catch-up, sync with Gokay. Got some cable pulls sorted out in the garage. Thu, 17 Mar 2022 --> 2022-03-17 Thursday 1:1's, COOL community call, catch-up with Julian Seward - its been too long - really missing in-persons like FOSDEM. Debugged delta pieces, monotonic timestamps and so on. Wed, 16 Mar 2022 --> 2022-03-16 Wednesday Sales meeting; Productivity monthly all-hands meeting, band practice. Tue, 15 Mar 2022 --> 2022-03-15 Tuesday 1:1's, slides, monthly mgmt meeting. Mon, 14 Mar 2022 --> 2022-03-14 Monday Planning calls, catch-up with Olivier Paroz; All Saints PCC meeting in the evening. Sun, 13 Mar 2022 --> 2022-03-13 Sunday All Saints, Kelsey over for lunch - lovely to get to know her a bit better. Sat, 12 Mar 2022 --> 2022-03-12 Saturday David over; dunged out the garage, built beautiful timber frames overlayed with ply-wood and perfectly square. Fitted them into place to discover the concrete floor and/or ceiling is far from level; time for expanding-foam and packers. Fri, 11 Mar 2022 --> 2022-03-11 Friday Catch-up call with Rash, worked on slides variously. Thu, 10 Mar 2022 --> 2022-03-10 Thursday COOL Community call, various 1:1s, bits of hacking, catch-up with Peter G. Wed, 09 Mar 2022 --> 2022-03-09 Wednesday E-mail catch-up, sales call, band practice, finished solding up the Geiger Counter - getting around ~1 scintilation each second or two on average: not very sensitive I suspect - hopefully sees more than passing muons. Tue, 08 Mar 2022 --> 2022-03-08 Tuesday Breakfast & meetings in the morning, train, plane home again - good to be back. Mon, 07 Mar 2022 --> 2022-03-07 Monday Up earlyish, day of meetings - interesting people lots of good things going on. Dinner in the evening together. Sun, 06 Mar 2022 --> 2022-03-06 Sunday All Saint in the morning, B&A, S&C & boys over for a lovely lunch; got a train to Heathrow - first time back on the road after endless lock-downs. Arrived in Hamburg, got to the Hotel, sleep. Sat, 05 Mar 2022 --> 2022-03-05 Saturday Set too soldering components, David over too - E. turns out to be the only person who can fit through a tiny gap - at least one of the family can. Fri, 04 Mar 2022 --> 2022-03-04 Friday Worked with Ash on a Secure View talk; call with Florian, catch-up with Gokay. Men of Faith pot-luck dinner at AllSaints in the evening. Thu, 03 Mar 2022 --> 2022-03-03 Thursday Catch up with Miklos, COOL community call, call with Andras; got some hacking done on deltas. DIY Geiger Counter PCB and components showed up: available on github Wed, 02 Mar 2022 --> 2022-03-02 Wednesday Sales call, competitor chat, customer call, catch up with Gokay - life seems to be mostly calls these days. Band practice. Tue, 01 Mar 2022 --> 2022-03-01 Tuesday Team 1:1's variously, Nextcloud catch-up, sales call. My content in this blog and associated images / data under images/ and data/ directories are (usually) created by me and (unless obviously labelled otherwise) are licensed under the public domain, and/or if that doesn't float your boat a CC0 license. I encourage linking back (of course) to help people decide for themselves, in context, in the battle for ideas, and I love fixes / improvements / corrections by private mail. In case it's not painfully obvious: the reflections reflected here are my own; mine, all mine ! and don't reflect the views of Collabora, SUSE, Novell, The Document Foundation, Spaghetti Hurlers (International), or anyone else. It's also important to realise that I'm not in on the Swedish Conspiracy . Occasionally people ask for formal photos for conferences or fun . Michael Meeks ( michael.meeks@collabora.com ) | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/lambda/latest/dg/durable-best-practices.html | Best practices for Lambda durable functions - AWS Lambda Best practices for Lambda durable functions - AWS Lambda Documentation AWS Lambda Developer Guide Write deterministic code Design for idempotency Manage state efficiently Design effective steps Use wait operations efficiently Additional considerations Additional resources Best practices for Lambda durable functions Durable functions use a replay-based execution model that requires different patterns than traditional Lambda functions. Follow these best practices to build reliable, cost-effective workflows. Write deterministic code During replay, your function runs from the beginning and must follow the same execution path as the original run. Code outside durable operations must be deterministic, producing the same results given the same inputs. Wrap non-deterministic operations in steps: Random number generation and UUIDs Current time or timestamps External API calls and database queries File system operations TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; import { randomUUID } from 'crypto'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Generate transaction ID inside a step const transactionId = await context.step('generate-transaction-id', async () => { return randomUUID(); }); // Use the same ID throughout execution, even during replay const payment = await context.step('process-payment', async () => { return processPayment(event.amount, transactionId); }); return { statusCode: 200, transactionId, payment }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext import uuid @durable_execution def handler(event, context: DurableContext): # Generate transaction ID inside a step transaction_id = context.step( lambda _: str(uuid.uuid4()), name='generate-transaction-id' ) # Use the same ID throughout execution, even during replay payment = context.step( lambda _: process_payment(event['amount'], transaction_id), name='process-payment' ) return { 'statusCode': 200, 'transactionId': transaction_id, 'payment': payment} Important Don't use global variables or closures to share state between steps. Pass data through return values. Global state breaks during replay because steps return cached results but global variables reset. Avoid closure mutations: Variables captured in closures can lose mutations during replay. Steps return cached results, but variable updates outside the step aren't replayed. TypeScript // ❌ WRONG: Mutations lost on replay export const handler = withDurableExecution(async (event, context) => { let total = 0; for (const item of items) { await context.step(async () => { total += item.price; // ⚠️ Mutation lost on replay! return saveItem(item); }); } return { total }; // Inconsistent value! }); // ✅ CORRECT: Accumulate with return values export const handler = withDurableExecution(async (event, context) => { let total = 0; for (const item of items) { total = await context.step(async () => { const newTotal = total + item.price; await saveItem(item); return newTotal; // Return updated value }); } return { total }; // Consistent! }); // ✅ EVEN BETTER: Use map for parallel processing export const handler = withDurableExecution(async (event, context) => { const results = await context.map( items, async (ctx, item) => { await ctx.step(async () => saveItem(item)); return item.price; } ); const total = results.getResults().reduce((sum, price) => sum + price, 0); return { total }; }); Python # ❌ WRONG: Mutations lost on replay @durable_execution def handler(event, context: DurableContext): total = 0 for item in items: context.step( lambda _: save_item_and_mutate(item, total), # ⚠️ Mutation lost on replay! name=f'save-item- { item["id"]}' ) return { 'total': total} # Inconsistent value! # ✅ CORRECT: Accumulate with return values @durable_execution def handler(event, context: DurableContext): total = 0 for item in items: total = context.step( lambda _: save_item_and_return_total(item, total), name=f'save-item- { item["id"]}' ) return { 'total': total} # Consistent! # ✅ EVEN BETTER: Use map for parallel processing @durable_execution def handler(event, context: DurableContext): def process_item(ctx, item): ctx.step(lambda _: save_item(item)) return item['price'] results = context.map(items, process_item) total = sum(results.get_results()) return { 'total': total} Design for idempotency Operations may execute multiple times due to retries or replay. Non-idempotent operations cause duplicate side effects like charging customers twice or sending multiple emails. Use idempotency tokens: Generate tokens inside steps and include them with external API calls to prevent duplicate operations. TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Generate idempotency token once const idempotencyToken = await context.step('generate-idempotency-token', async () => { return crypto.randomUUID(); }); // Use token to prevent duplicate charges const charge = await context.step('charge-payment', async () => { return paymentService.charge( { amount: event.amount, cardToken: event.cardToken, idempotencyKey: idempotencyToken }); }); return { statusCode: 200, charge }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext import uuid @durable_execution def handler(event, context: DurableContext): # Generate idempotency token once idempotency_token = context.step( lambda _: str(uuid.uuid4()), name='generate-idempotency-token' ) # Use token to prevent duplicate charges def charge_payment(_): return payment_service.charge( amount=event['amount'], card_token=event['cardToken'], idempotency_key=idempotency_token ) charge = context.step(charge_payment, name='charge-payment') return { 'statusCode': 200, 'charge': charge} Use at-most-once semantics: For critical operations that must never duplicate (financial transactions, inventory deductions), configure at-most-once execution mode. TypeScript // Critical operation that must not duplicate await context.step('deduct-inventory', async () => { return inventoryService.deduct(event.productId, event.quantity); }, { executionMode: 'AT_MOST_ONCE_PER_RETRY' }); Python # Critical operation that must not duplicate context.step( lambda _: inventory_service.deduct(event['productId'], event['quantity']), name='deduct-inventory', config=StepConfig(execution_mode='AT_MOST_ONCE_PER_RETRY') ) Database idempotency: Use check-before-write patterns, conditional updates, or upsert operations to prevent duplicate records. Manage state efficiently Every checkpoint saves state to persistent storage. Large state objects increase costs, slow checkpointing, and impact performance. Store only essential workflow coordination data. Keep state minimal: Store IDs and references, not full objects Fetch detailed data within steps as needed Use Amazon S3 or DynamoDB for large data, pass references in state Avoid passing large payloads between steps TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Store only the order ID, not the full order object const orderId = event.orderId; // Fetch data within each step as needed await context.step('validate-order', async () => { const order = await orderService.getOrder(orderId); return validateOrder(order); }); await context.step('process-payment', async () => { const order = await orderService.getOrder(orderId); return processPayment(order); }); return { statusCode: 200, orderId }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext @durable_execution def handler(event, context: DurableContext): # Store only the order ID, not the full order object order_id = event['orderId'] # Fetch data within each step as needed context.step( lambda _: validate_order(order_service.get_order(order_id)), name='validate-order' ) context.step( lambda _: process_payment(order_service.get_order(order_id)), name='process-payment' ) return { 'statusCode': 200, 'orderId': order_id} Design effective steps Steps are the fundamental unit of work in durable functions. Well-designed steps make workflows easier to understand, debug, and maintain. Step design principles: Use descriptive names - Names like validate-order instead of step1 make logs and errors easier to understand Keep names static - Don't use dynamic names with timestamps or random values. Step names must be deterministic for replay Balance granularity - Break complex operations into focused steps, but avoid excessive tiny steps that increase checkpoint overhead Group related operations - Operations that should succeed or fail together belong in the same step Use wait operations efficiently Wait operations suspend execution without consuming resources or incurring costs. Use them instead of keeping Lambda running. Time-based waits: Use context.wait() for delays instead of setTimeout or sleep . External callbacks: Use context.waitForCallback() when waiting for external systems. Always set timeouts to prevent indefinite waits. Polling: Use context.waitForCondition() with exponential backoff to poll external services without overwhelming them. TypeScript // Wait 24 hours without cost await context.wait( { seconds: 86400 }); // Wait for external callback with timeout const result = await context.waitForCallback( 'external-job', async (callbackId) => { await externalService.submitJob( { data: event.data, webhookUrl: `https://api.example.com/callbacks/$ { callbackId}` }); }, { timeout: { seconds: 3600 } } ); Python # Wait 24 hours without cost context.wait(86400) # Wait for external callback with timeout result = context.wait_for_callback( lambda callback_id: external_service.submit_job( data=event['data'], webhook_url=f'https://api.example.com/callbacks/ { callback_id}' ), name='external-job', config=WaitForCallbackConfig(timeout_seconds=3600) ) Additional considerations Error handling: Retry transient failures like network timeouts and rate limits. Don't retry permanent failures like invalid input or authentication errors. Configure retry strategies with appropriate max attempts and backoff rates. For detailed examples, see Error handling and retries . Performance: Minimize checkpoint size by storing references instead of full payloads. Use context.parallel() and context.map() to execute independent operations concurrently. Batch related operations to reduce checkpoint overhead. Versioning: Invoke functions with version numbers or aliases to pin executions to specific code versions. Ensure new code versions can handle state from older versions. Don't rename steps or change their behavior in ways that break replay. Serialization: Use JSON-compatible types for operation inputs and results. Convert dates to ISO strings and custom objects to plain objects before passing them to durable operations. Monitoring: Enable structured logging with execution IDs and step names. Set up CloudWatch alarms for error rates and execution duration. Use tracing to identify bottlenecks. For detailed guidance, see Monitoring and debugging . Testing: Test happy path, error handling, and replay behavior. Test timeout scenarios for callbacks and waits. Use local testing to reduce iteration time. For detailed guidance, see Testing durable functions . Common mistakes to avoid: Don't nest context.step() calls, use child contexts instead. Wrap non-deterministic operations in steps. Always set timeouts for callbacks. Balance step granularity with checkpoint overhead. Store references instead of large objects in state. Additional resources Python SDK documentation - Complete API reference, testing patterns, and advanced examples TypeScript SDK documentation - Complete API reference, testing patterns, and advanced examples Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Monitoring durable functions Lambda Managed Instances Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/zh_tw/lambda/latest/dg/durable-basic-concepts.html | 基本概念 - AWS Lambda 基本概念 - AWS Lambda 文件 AWS Lambda 開發人員指南 持久性執行 DurableContext 步驟 等待狀態 叫用其他 函數 耐用的函數組態 本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。 基本概念 Lambda 提供適用於 JavaScript、TypeScript 和 Python SDKs。這些 SDKs是建置耐用函數的基礎，提供您檢查點進度、處理重試和管理執行流程所需的基本概念。如需完整的 SDK 文件和範例，請參閱 GitHub 上的 JavaScript/TypeScript SDK 和 Python SDK 。 持久性執行 持久性執行 代表 Lambda 持久性函數的完整生命週期，使用檢查點和重播機制來追蹤業務邏輯進度、暫停執行並從失敗中復原。當函數在暫停或中斷後恢復時，會重新播放先前完成的檢查點，且函數會繼續執行。 生命週期可能包含 Lambda 函數的多次調用以完成執行，特別是在暫停或故障復原之後。此方法可讓您的函數長時間執行 （長達一年），同時在中斷的情況下維持可靠的進度。 重播的運作方式 Lambda 會在函數執行時保留所有耐久操作 （步驟、等待和其他操作） 的執行中日誌。當您的函數需要暫停或遇到中斷時，Lambda 會儲存此檢查點日誌並停止執行。當需要繼續時，Lambda 會從頭再次叫用您的函數，並重播檢查點日誌，取代已完成操作的預存值。這表示您的程式碼會再次執行，但先前完成的步驟不會重新執行。而是改用其儲存的結果。 此重播機制對於了解耐用函數至關重要。您的程式碼在重播期間必須具有決定性，這表示它在相同的輸入下會產生相同的結果。避免在步驟之外出現副作用的操作 （例如產生隨機數字或取得目前時間），因為這些操作可能會在重播期間產生不同的值，並導致非確定性的行為。 DurableContext DurableContext 是您耐用函數接收的內容物件。它提供持久性操作的方法，例如建立檢查點和管理執行流程的步驟和等待。 您的耐用函數會收到 DurableContext 而非預設 Lambda 內容： TypeScript import { DurableContext, withDurableExecution, } from "@aws/durable-execution-sdk-js"; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { const result = await context.step(async () => { return "step completed"; }); return result; }, ); Python from aws_durable_execution_sdk_python import ( DurableContext, durable_execution, durable_step, ) @durable_step def my_step(step_context, data): # Your business logic return result @durable_execution def handler(event, context: DurableContext): result = context.step(my_step(event["data"])) return result 適用於耐用函數的 Python SDK 使用同步方法，不支援 await 。TypeScript SDK 使用 async/await 。 步驟 步驟 會使用內建重試和自動檢查點來執行商業邏輯。每個步驟都會儲存其結果，確保您的函數可以在中斷後從任何完成的步驟恢復。 TypeScript // Each step is automatically checkpointed const order = await context.step(async () => processOrder(event)); const payment = await context.step(async () => processPayment(order)); const result = await context.step(async () => completeOrder(payment)); Python # Each step is automatically checkpointed order = context.step(lambda: process_order(event)) payment = context.step(lambda: process_payment(order)) result = context.step(lambda: complete_order(payment)) 等待狀態 等待狀態 是您的函數停止執行 （並停止充電） 的計劃暫停，直到繼續為止。使用它們來等待期間、外部回呼或特定條件。 TypeScript // Wait for 1 hour without consuming resources await context.wait( { seconds:3600 }); // Wait for external callback const approval = await context.waitForCallback( async (callbackId) => sendApprovalRequest(callbackId) ); Python # Wait for 1 hour without consuming resources context.wait(3600) # Wait for external callback approval = context.wait_for_callback( lambda callback_id: send_approval_request(callback_id) ) 當您的函數遇到等待或需要暫停時，Lambda 會儲存檢查點日誌並停止執行。恢復時，Lambda 會再次叫用您的函數，並重播檢查點日誌，以儲存的值取代已完成的操作。 對於更複雜的工作流程，耐用的 Lambda 函數也隨附進階操作，例如 parallel() 用於並行執行、 map() 用於處理陣列、 runInChildContext() 用於巢狀操作，以及 waitForCondition() 用於輪詢。如需何時使用每個操作的詳細範例和指引，請參閱 範例 。 叫用其他 函數 調用 允許耐用的函數呼叫其他 Lambda 函數，並等待其結果。呼叫函數會在調用函數執行時暫停，建立保留結果的檢查點。這可讓您建置模組化工作流程，讓專門的 函數處理特定任務。 使用 從耐用函數內 context.invoke() 呼叫其他函數。調用是檢查點的，因此如果您的函數在調用函數完成後中斷，它會繼續以儲存的結果繼續，而不會重新調用函數。 TypeScript // Invoke another function and wait for result const customerData = await context.invoke( 'validate-customer', 'arn:aws:lambda:us-east-1:123456789012:function:customer-service:1', { customerId: event.customerId } ); // Use the result in subsequent steps const order = await context.step(async () => { return processOrder(customerData); }); Python # Invoke another function and wait for result customer_data = context.invoke( 'arn:aws:lambda:us-east-1:123456789012:function:customer-service:1', { 'customerId': event['customerId']}, name='validate-customer' ) # Use the result in subsequent steps order = context.step( lambda: process_order(customer_data), name='process-order' ) 調用函數可以是耐用或標準 Lambda 函數。如果您叫用持久性函數，呼叫函數會等待完全持久性執行完成。此模式在微服務架構中很常見，其中每個函數都會處理特定網域，讓您從專業、可重複使用的函數編寫複雜的工作流程。 注意 不支援跨帳戶調用。調用函數必須與呼叫函數位於相同的 AWS 帳戶中。 耐用的函數組態 耐用函數具有特定的組態設定，可控制執行行為和資料保留。這些設定與標準 Lambda 函數組態分開，並套用至整個耐久執行生命週期。 DurableConfig 物件會定義耐用函數的組態： { "ExecutionTimeout": Integer, "RetentionPeriodInDays": Integer } Execution timeout (執行逾時) 執行逾時 可控制持久性執行從開始到完成的執行時間。這與 Lambda 函數逾時不同，它控制單一函數調用可以執行的時間長度。 當 Lambda 函數通過檢查點、等待和重播時，耐久執行可以跨越多個 Lambda 函數叫用。執行逾時適用於持久性執行的總經過時間，不適用於個別函數叫用。 了解差異 Lambda 函數逾時 （最多 15 分鐘） 會限制函數的每個個別調用。持久性執行逾時 （最長 1 年） 會限制從執行開始到完成、失敗或逾時的總時間。在此期間，您的函數可能會在處理步驟、等待並從失敗中復原時被叫用多次。 例如，如果您將持久執行逾時設定為 24 小時，Lambda 函數逾時設定為 5 分鐘： 每個函數調用必須在 5 分鐘內完成 整個耐久執行最多可執行 24 小時 在這 24 小時內，您的函數可以被叫用多次 等待操作不會計入 Lambda 函數逾時，但會計入執行逾時 您可以使用 Lambda 主控台或 建立耐用函數時 AWS CLI，設定執行逾時 AWS SAM。在 Lambda 主控台中，選擇您的函數，然後選擇組態、持久性執行。以秒為單位設定執行逾時值 （預設值：86400 秒 / 24 小時，最小值：60 秒，最大值：31536000 秒 / 1 年）。 注意 執行逾時和 Lambda 函數逾時的設定不同。Lambda 函數逾時控制每個個別調用可以執行的時間長度 （最長 15 分鐘）。執行逾時可控制整個持久性執行的總經過時間 （最長 1 年）。 保留期間 保留期間 控制 Lambda 在持久性執行完成後保留執行歷史記錄和檢查點資料的時間長度。此資料包含步驟結果、執行狀態和完整的檢查點日誌。 保留期間到期後，Lambda 會刪除執行歷史記錄和檢查點資料。您無法再擷取執行詳細資訊或重播執行。保留期會在執行達到結束狀態 (SUCCEEDED、FAILED、STOPPED 或 TIMED_OUT) 時開始。 您可以使用 Lambda 主控台 AWS CLI或 來設定建立耐用函數時的保留期間 AWS SAM。在 Lambda 主控台中，選擇您的函數，然後選擇組態、持久性執行。以天為單位設定保留期間值 （預設值：14 天，下限：1 天，上限：90 天）。 根據您的合規要求、除錯需求和成本考量，選擇保留期。較長的保留期提供更多偵錯和稽核的時間，但會增加儲存成本。 您的瀏覽器已停用或無法使用 Javascript。 您必須啟用 Javascript，才能使用 AWS 文件。請參閱您的瀏覽器說明頁以取得說明。 文件慣用形式 Lambda 耐用函數 建立耐用的函數 此頁面是否有幫助？ - 是 感謝您，讓我們知道我們做得很好！ 若您有空，歡迎您告知我們值得讚許的地方，這樣才能保持良好服務。 此頁面是否有幫助？ - 否 感謝讓我們知道此頁面仍須改善。很抱歉，讓您失望。 若您有空，歡迎您提供改善文件的方式。 | 2026-01-13T09:29:30 |
https://mastodon.social/share?text=Windows+Docker+Agent+Images%3A+General+Availability+https%3A%2F%2Fwww.jenkins.io%2Fblog%2F2020%2F05%2F11%2Fdocker-windows-agents%2F | Log in - Mastodon Login to mastodon.social Login with your mastodon.social credentials. If your account is hosted on a different server, you will not be able to log in here. E-mail address * Password Log in Sign up Forgot your password? Didn't receive a confirmation link? | 2026-01-13T09:29:30 |
https://meeksfamily.uk/~michael/blog/2022/Apr/index.html | Stuff Michael Meeks is doing Stuff Michael Meeks is doing This is my (in)activity log. You might like to visit Collabora Productivity a subsidiary of Collabora focusing on LibreOffice support and services for whom I work. Also if you have the time to read this sort of stuff you could enlighten yourself by going to Unraveling Wittgenstein's net or if you are feeling objectionable perhaps here . Failing that, there are all manner of interesting things to read on the LibreOffice Planet news feed . Older items: 2023 : ( J F M A M J ), 2022 : ( J F M A M J J A S O N D ), 2021 , 2019 , 2018 , 2017 , 2016 , 2015 , 2014 , 2013 , 2012 , 2011 , 2010 , 2009 , 2009 , 2008 , 2007 , 2006 , 2005 , 2004 , 2003 , 2002 , 2001 , 2000 , 1999 , legacy html Sat, 30 Apr 2022 --> 2022-04-30 Saturday Plugged away at some building / concreting work with E. now a rather skilled pad-stone manoeverer (with jack) - fun. Lunch. Fri, 29 Apr 2022 --> 2022-04-29 Friday Catch up with Gokay, Pedro & Szymon, chat with Jos. Helped H. with some engineering revision on Jitsi. Men of Faith fish & chip dinner at All Saints. Thu, 28 Apr 2022 --> 2022-04-28 Thursday Catch-up with Miklos, COOL community call, quarterly C'bra mgmt meeting until late. Tried to get wxPython setup on a Mac for a customer; somewhat nightmarish, sometimes I despair of the Linux Desktop - and then I see a Windows machine where an update has irreparably broken screen brightness or somesuch and marvel. Wed, 27 Apr 2022 --> 2022-04-27 Wednesday Sales catch-up, quarterly C'bra mgmt meeting much of the day until late. Tue, 26 Apr 2022 --> 2022-04-26 Tuesday Up late - blackout blinds; sync with Kendy (who also is a Colin Furze watcher; sync with Simon, worked on some marketing together. Catch up with Eloy, contract work, marketing bits. Mon, 25 Apr 2022 --> 2022-04-25 Monday Planning call; lunch, partner call, poked at planning and LinkedIn, catch-up with Philippe. Out for a run with J. Put up Bloc-blinds in the bedroom Sun, 24 Apr 2022 --> 2022-04-24 Sunday All Saints in the morning, just me and (2 metre) Peter - without having practiced: survived for the most part. Home for a Pizza lunch. Slugged, J. took babes to StAG, watched The Hunt for Red October with E. Rested. Sat, 23 Apr 2022 --> 2022-04-23 Saturday Played with E. in the morning, made some mortar together and started improving the drive. Lunch, David over - chatted, fixed up some wiring for roses, removed an ivy root, sealed the garage door a bit better. Lynn and Esther over in the evening, watched Silent Witness with J. Fri, 22 Apr 2022 --> 2022-04-22 Friday Catch up with Eloy, admin, lunch, call with Cor, more E-mail, poked at projections, reviewed Ash' save patches. Watched Get Smart in the evening with E. it could use a sequal. Thu, 21 Apr 2022 --> 2022-04-21 Thursday Starting to feel somewhat better - good. Parents car not charged enough in the morning: vampire drains over-taking the trickle-charger? Took babes to school, made some jump-leads from scrap cabling off-cuts - and jump started their car with some help from M&D. Helped to get H. sorted out and off to University - so lovely to have her around, sad to see her go. 1:1 with Miklos, COOL community call, lunch, 1:1 with Andras, chats with Jos & Simon. Booked flights for Univention Summit, dinner. Back to E-mail and the backlog. Leo over in the evening for home-group, lovely to catch-up with him. Wed, 20 Apr 2022 --> 2022-04-20 Wednesday Wedding Anniversary - twenty blissful years. Lots of nice cards - lovely. To work, a bit of E-mail, poked at slides, CP monthly all-hands. Out for a lovely walk with the parents in the afternoon at Lynford Arboretum - some fine trees, and a potter around together - must be getting old. Chinese take-out treat in the evening, thanks to M&D. Tue, 19 Apr 2022 --> 2022-04-19 Tuesday Catch up with Mike & Kendy, Lunch, quarterly mgmt call, more E-mail backlog beat-back. Discovered parents' Prius battery discharged due to leaving the light on: odd to de-couple the 12V systems from the (charged) motive battery. Left it trickle-charging overnight. Mon, 18 Apr 2022 --> 2022-04-18 Monday Up lateish; cooked breakfast with the family. Out to St Albans together to meet up with S&C & boys - played in the park together in the sun - still feeling throaty. Bid 'bye to R&A and boys. Home, did some work with H. before she went out for the evening. Sun, 17 Apr 2022 --> 2022-04-17 Sunday All off to church, celebrated variously - easter-egg hunt in the graveyard afterwards with the babes - walked home in the sun. J. stayed for Leo's baptism, snacked and chatted in the garden together - J. back - big lamb roast lunch. Played with the babes; talked until late at night with R. . Sat, 16 Apr 2022 --> 2022-04-16 Saturday Bit of wiring in the garage with Father; helped H. with some project research. Lunch together, R&A and boys arrived late - lovely to see them, up late. Fri, 15 Apr 2022 --> 2022-04-15 Friday Up late, rested somewhat, out for a walk with M&D, M&E along the dyke nearby, shade-sail up in the garden & lunch outside - a lovely hot day. David over, got insulated plasterboard stabilized by injecting foam behind it, set too getting the floor fitted with David's help - and some success; managed to (somehow) almost level the floor with packing pieces. Dinner, dunged out the U-bend in a parlous state in N&M's bathroom. Thu, 14 Apr 2022 --> 2022-04-14 Thursday Still feeling poor; out to Ridgeons to get supplies; set-too cutting out & re-siliconing the top bathroom shower seal. Interrupted by a friendly fencer - caught up with Sue & Russel. Parents arrived in the evening, watched some Colin Furze with Father and rested. Wed, 13 Apr 2022 --> 2022-04-13 Wednesday Still feeling poor. Helped J. with the shopping - it's amazing what she does to feed us all. Triaged E-mail to try to keep it down. Tue, 12 Apr 2022 --> 2022-04-12 Tuesday Up late, caught up my blog since Jan 27th in a block. Still in something of a haze. Mon, 11 Apr 2022 --> 2022-04-11 Monday Feeling awful; planning calls. B&A over - stayed away from them while trying to catch up - slept through the afternoon exhaustedly. Late night work with Eloy (on vacation). Sun, 10 Apr 2022 --> 2022-04-10 Sunday All-Saints, precautionary mask wearing despite another clear COVID test. Put up Trampoline again after the winds, and clipped it to the house. Managed to give a bike to Cedric - slowly empting the garage of unused stuff. Sat, 09 Apr 2022 --> 2022-04-09 Saturday David over, managed to get the tricky insulated plasterboard pieces above and around the door together having stuck some timber into the RSJ above it - 100mm phosphate screws are the bees knees. Ran out of foam. Ham, eggs &. chips for tea - nice. Fri, 08 Apr 2022 --> 2022-04-08 Friday Feeling pretty awful; took much of the day off; modulo FOSS Asia presentation - great to be back there. Cut the grass: walking slowly up & down is about my limit. Thu, 07 Apr 2022 --> 2022-04-07 Thursday Feeling pretty awful - not COVID it seems though; worked on & off. Wed, 06 Apr 2022 --> 2022-04-06 Wednesday Joint COOL presentation with our partner Redpill Linpro; weekly sales call, monthly Productivity developers show-and-tell. Worked on slides for FOSS-Asia talk tomorrow. Tue, 05 Apr 2022 --> 2022-04-05 Tuesday Discovered my blog is down - apparently I had missed the notification : bother; kindly provided with a backup of the last ~20 years of random up-loads/backups/slides & blog bits from there: 1.8Gb. Fond memories of when such things were stored at unam.mx in the very early days of GNOME. Been wondering what to do about my blog anyway - some people complain(ed) about the personal content - it's not technical-enough and presumably ragged around the edges. They want a tag so they can ignore the personal pieces - and can instead get pure engineering updates - as if from some corporate entity. I'm not impressed by such requests for several reasons: Hacker communities are made of people - not corporate clones: people are wonderfully different & have real lives, and interests. Its important to remember that communities are not this homogeneous professional blob - they are made of diverse experiences, viewpoints and interests. Reminding people that their software is created and maintained by a fun but motley crew of random co-beligerents can stop them getting the idea that they get a polished, professional product for free - which is quite helpful for the ecosystem who sell that. My blog is run from some legacy pybloxsm software from emacs and I have little-to-no time to adapt it to make it easier for people to read only the worker-bee part of it. They are more than welcome to read none of it. My technical content is increasingly less substantial these days I fear - primarily I do a lot of sales and management which - while interesting & encouraging doesn't lend itself to early publication. Have spent some holiday to catch up, and will try to get some new hosting. Mon, 04 Apr 2022 --> 2022-04-04 Monday Planning calls, early Sales & Marketing call - trying to make some calendar space for a holiday. Sun, 03 Apr 2022 --> 2022-04-03 Sunday All Saints; Mike Geach over for a pizza lunch, lovely to catch up with him again; rested variously. Sat, 02 Apr 2022 --> 2022-04-02 Saturday J. took E. to The Ark at Isleham for a YFC all-day event: climbing, laser-quest and all sorts of useful teaching. Managed to get roller-door removed, and new window frames fitted - glazing sealed in properly this time, and surrounds added. Hung doors, foam & frame sealant all around, and - bingo - something approaching a room starts to appear. Fri, 01 Apr 2022 --> 2022-04-01 Friday More delta work, good to have Henry helping out too, merged some of his changes to my branch. My content in this blog and associated images / data under images/ and data/ directories are (usually) created by me and (unless obviously labelled otherwise) are licensed under the public domain, and/or if that doesn't float your boat a CC0 license. I encourage linking back (of course) to help people decide for themselves, in context, in the battle for ideas, and I love fixes / improvements / corrections by private mail. In case it's not painfully obvious: the reflections reflected here are my own; mine, all mine ! and don't reflect the views of Collabora, SUSE, Novell, The Document Foundation, Spaghetti Hurlers (International), or anyone else. It's also important to realise that I'm not in on the Swedish Conspiracy . Occasionally people ask for formal photos for conferences or fun . Michael Meeks ( michael.meeks@collabora.com ) | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/lambda/latest/dg/workflow-event-management.html | Managing Lambda workflows and events - AWS Lambda Managing Lambda workflows and events - AWS Lambda Documentation AWS Lambda Developer Guide Code-first orchestration with durable functions Orchestrating workflows with Step Functions Managing events with EventBridge and EventBridge Scheduler Managing Lambda workflows and events When building serverless applications with Lambda, you often need ways to orchestrate function execution and handle events. AWS provides several approaches for coordinating Lambda functions: Lambda durable functions for code-first workflow orchestration within Lambda AWS Step Functions for visual workflow orchestration across multiple services Amazon EventBridge Scheduler and Amazon EventBridge for event-driven architectures and scheduling You can also integrate these approaches together. For example, you might use EventBridge Scheduler to trigger durable functions or Step Functions workflows when specific events occur, or configure workflows to publish events to EventBridge Scheduler at defined execution points. The following topics in this section provide more information on how you can use these orchestration options. Code-first orchestration with durable functions Lambda durable functions provide a code-first approach to workflow orchestration, allowing you to build stateful, long-running workflows directly within your Lambda functions. Unlike external orchestration services, durable functions keep your workflow logic in code, making it easier to version, test, and maintain alongside your business logic. Durable functions are ideal when you need: Code-first workflow definition: Define workflows using familiar programming languages rather than JSON or visual designers Long-running processes: Execute workflows that can run for up to one year, far beyond the 15-minute limit of standard Lambda functions Simplified development: Keep workflow logic and business logic in the same codebase for easier maintenance and testing Cost-effective waiting: Pause execution during wait states without consuming compute resources Built-in state management: Automatic checkpointing and state persistence without external storage configuration Choosing between durable functions and Step Functions Both durable functions and Step Functions provide workflow orchestration capabilities, but they serve different use cases: Consideration Durable Functions Step Functions Workflow definition Code-first (JavaScript, Python, Java) JSON-based Amazon States Language or visual designer Development approach Single codebase with business logic Separate workflow definition and function code Service integration Through Lambda function code and AWS SDKs Native integrations with many AWS services Execution duration Up to 1 year Up to 1 year (Standard), 5 minutes (Express) Parallel processing Promise.all() and code-based patterns Parallel state and Distributed Map Error handling Try-catch blocks and custom retry logic Built-in retry and catch states Visual monitoring CloudWatch logs and custom dashboards Visual execution graph and detailed history Best for Developer-centric workflows, complex business logic, rapid prototyping Multi-service orchestration, visual workflows, enterprise governance Use durable functions when: Your team prefers code-first development approaches Workflow logic is tightly coupled with business logic You need rapid prototyping and iteration Your workflows primarily involve Lambda functions and simple service calls Use Step Functions when: You need visual workflow design and monitoring Your workflows orchestrate multiple AWS services extensively You require enterprise governance and compliance features Non-technical stakeholders need to understand workflow logic For more information on durable functions, see Durable functions for Lambda . Orchestrating workflows with Step Functions AWS Step Functions is a workflow orchestration service that helps you coordinate multiple Lambda functions and other AWS services into structured workflows. These workflows can maintain state, handle errors with sophisticated retry mechanisms, and process data at scale. Step Functions offers two types of workflows to meet different orchestration needs: Standard workflows Ideal for long-running, auditable workflows that require exactly-once execution semantics. Standard workflows can run for up to one year, provide detailed execution history, and support visual debugging. They are suitable for processes like order fulfillment, data processing pipelines, or multi-step analytics jobs. Express workflows Designed for high-event-rate, short-duration workloads with at-least-once execution semantics. Express workflows can run for up to five minutes and are ideal for high-volume event processing, streaming data transformations, or IoT data ingestion scenarios. They offer higher throughput and potentially lower cost compared to Standard workflows. Note For more information on Step Functions workflow types, see Choosing workflow type in Step Functions . Within these workflows, Step Functions provides two types of Map states for parallel processing: Inline Map Processes items from a JSON array within the execution history of the parent workflow. Inline Map supports up to 40 concurrent iterations and is suitable for smaller datasets or when you need to keep all processing within a single execution. For more information, see Using Map state in Inline mode . Distributed Map Enables processing of large-scale parallel workloads by iterating over datasets that exceed 256 KiB or require more than 40 concurrent iterations. With support for up to 10,000 parallel child workflow executions, Distributed Map excels at processing semi-structured data stored in Amazon S3, such as JSON or CSV files, making it ideal for batch processing and ETL operations. For more information, see Using Map state in Distributed mode . By combining these workflow types and Map states, Step Functions provides a flexible and powerful toolset for orchestrating complex serverless applications, from small-scale operations to large-scale data processing pipelines. To get started with using Lambda with Step Functions, see Orchestrating Lambda functions with Step Functions . Managing events with EventBridge and EventBridge Scheduler Amazon EventBridge is an event bus service that helps you build event-driven architectures. It routes events between AWS services, integrated applications, and software as a service (SaaS) applications. EventBridge Scheduler is a serverless scheduler that enables you to create, run, and manage tasks from one central service, allowing you to invoke Lambda functions on a schedule using cron and rate expressions, or configure one-time invocations. Amazon EventBridge and EventBridge Scheduler help you build event-driven architectures with Lambda. EventBridge routes events between AWS services, integrated applications, and SaaS applications, while EventBridge Scheduler provides specific scheduling capabilities for invoking Lambda functions on a recurring or one-time basis. These services provide several key capabilities for working with Lambda functions: Create rules that match and route events to Lambda functions using EventBridge Set up recurring function invocations using cron and rate expressions with EventBridge Scheduler Configure one-time function invocations at specific dates and times Define flexible time windows and retry policies for scheduled invocations For more information, see Invoke a Lambda function on a schedule . Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Powertools for AWS Lambda Lambda durable functions Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/zh_tw/lambda/latest/dg/durable-functions.html#durable-functions-next-steps | Lambda 耐用函數 - AWS Lambda Lambda 耐用函數 - AWS Lambda 文件 AWS Lambda 開發人員指南 主要優點 運作方式 何時使用耐用函數 後續步驟 本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。 Lambda 耐用函數 Lambda 耐用函數可讓您建置彈性的多步驟應用程式和 AI 工作流程，可執行長達一年，同時在中斷的情況下保持可靠的進度。當持久性函數執行時，這個完整的生命週期稱為持久性執行，它使用檢查點來追蹤進度，並透過重新執行自動從失敗中復原，從頭開始重新執行，同時略過完成的工作。 在每個函數中，您會使用耐用的操作做為基本的建置區塊。步驟會使用內建重試和進度追蹤來執行商業邏輯，同時等待暫停執行而不會產生運算費用，因此非常適合長時間執行的程序human-in-the-loop工作流程或輪詢外部相依性。無論您是在處理訂單、協調微服務或協調代理式 AI 應用程式，當您使用熟悉的程式設計語言編寫程式碼時，耐用的函數會自動維持狀態並從失敗中復原。 主要優點 自然撰寫彈性程式碼： 使用熟悉的程式設計建構，您可以撰寫自動處理失敗的程式碼。內建檢查點、透明重試和自動復原意味著您的商業邏輯保持乾淨且專注。 僅為您使用的項目付費： 在等待操作期間，您的函數會暫停，而不會產生運算費用。對於等待數小時或數天的長時間執行工作流程，您只需支付實際處理時間，而非閒置等待。 操作簡單： 使用 Lambda 的無伺服器模型，您可以自動擴展，包括scale-to-zero，而無需管理基礎設施。耐用的函數會自動處理狀態管理、重試邏輯和故障復原，從而降低營運開銷。 運作方式 在幕後，耐用的函數是一般的 Lambda 函數，使用檢查點/重播機制來追蹤進度，並透過使用者定義的暫停點支援長時間執行的操作，通常稱為耐用執行。當持久的函數從等待點繼續，或像重試一樣中斷時，系統會執行重播。在重播期間，您的程式碼會從頭開始執行，但會略過已完成的檢查點，使用儲存的結果，而不是重新執行已完成的操作。此重播機制可確保一致性，同時啟用長時間執行的執行。 函數從暫停或中斷恢復後，系統會執行重播。在重播期間，您的程式碼會從頭開始執行，但會略過已完成的檢查點，使用儲存的結果，而不是重新執行已完成的操作。此重播機制可確保一致性，同時啟用長時間執行的執行。 為了在您的應用程式中利用此checkpoint-and-replay機制，Lambda 提供耐用的執行 SDK。開發套件可消除管理檢查點和重播的複雜性，公開您在程式碼中使用的稱為耐久操作的簡單基本概念。開發套件適用於 JavaScript、TypeScript 和 Python，可與您現有的 Lambda 開發工作流程無縫整合。 使用 SDK，您可以包裝 Lambda 事件處理常式，然後提供 DurableContext 與您的事件並行。此內容可讓您存取耐用的操作，例如步驟和等待。您可以將函數邏輯寫入為一般循序程式碼，但不會直接呼叫 服務，而是將這些呼叫包裝為自動檢查點和重試的步驟。當您需要暫停執行時，您可以新增暫停函數的等待，而不會產生費用。開發套件可處理所有複雜的狀態管理和在幕後重播，讓您的程式碼保持乾淨且可讀取。 何時使用耐用函數 短期協調： 透過自動轉返失敗，協調跨多項服務的付款、庫存和運送。透過驗證、付款授權、庫存分配和履行來處理訂單，並保證完成。 安心處理付款： 建立彈性付款流程，透過失敗維持交易狀態，並自動處理重試。協調跨付款供應商的多步驟授權、詐騙檢查和和解，並跨步驟進行完整稽核。 建置可靠的 AI 工作流程： 建立多步驟 AI 工作流程，以鏈結模型呼叫、整合人工意見回饋，並在失敗期間果斷地處理長時間執行的任務。停用後自動繼續，且只需支付作用中的執行時間。 協調複雜的訂單履行： 使用內建彈性協調跨庫存、付款、運送和通知系統的訂單處理。自動處理部分故障、保留中斷時的順序狀態，並有效率地等待外部事件，而不會耗用運算資源。 自動化多步驟業務工作流程： 為員工加入、貸款核准和跨越數天或數週的合規程序建立可靠的工作流程。維護跨人工核准、系統整合和排程任務的工作流程狀態，同時提供程序狀態和歷史記錄的完整可見性。 後續步驟 開始使用耐用的 函數 探索耐用的執行 SDK 監控和偵錯耐用函數 檢閱安全性和許可 遵循最佳實務 您的瀏覽器已停用或無法使用 Javascript。 您必須啟用 Javascript，才能使用 AWS 文件。請參閱您的瀏覽器說明頁以取得說明。 文件慣用形式 工作流程與事件 基本概念 此頁面是否有幫助？ - 是 感謝您，讓我們知道我們做得很好！ 若您有空，歡迎您告知我們值得讚許的地方，這樣才能保持良好服務。 此頁面是否有幫助？ - 否 感謝讓我們知道此頁面仍須改善。很抱歉，讓您失望。 若您有空，歡迎您提供改善文件的方式。 | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/lambda/latest/dg/durable-best-practices.html | Best practices for Lambda durable functions - AWS Lambda Best practices for Lambda durable functions - AWS Lambda Documentation AWS Lambda Developer Guide Write deterministic code Design for idempotency Manage state efficiently Design effective steps Use wait operations efficiently Additional considerations Additional resources Best practices for Lambda durable functions Durable functions use a replay-based execution model that requires different patterns than traditional Lambda functions. Follow these best practices to build reliable, cost-effective workflows. Write deterministic code During replay, your function runs from the beginning and must follow the same execution path as the original run. Code outside durable operations must be deterministic, producing the same results given the same inputs. Wrap non-deterministic operations in steps: Random number generation and UUIDs Current time or timestamps External API calls and database queries File system operations TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; import { randomUUID } from 'crypto'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Generate transaction ID inside a step const transactionId = await context.step('generate-transaction-id', async () => { return randomUUID(); }); // Use the same ID throughout execution, even during replay const payment = await context.step('process-payment', async () => { return processPayment(event.amount, transactionId); }); return { statusCode: 200, transactionId, payment }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext import uuid @durable_execution def handler(event, context: DurableContext): # Generate transaction ID inside a step transaction_id = context.step( lambda _: str(uuid.uuid4()), name='generate-transaction-id' ) # Use the same ID throughout execution, even during replay payment = context.step( lambda _: process_payment(event['amount'], transaction_id), name='process-payment' ) return { 'statusCode': 200, 'transactionId': transaction_id, 'payment': payment} Important Don't use global variables or closures to share state between steps. Pass data through return values. Global state breaks during replay because steps return cached results but global variables reset. Avoid closure mutations: Variables captured in closures can lose mutations during replay. Steps return cached results, but variable updates outside the step aren't replayed. TypeScript // ❌ WRONG: Mutations lost on replay export const handler = withDurableExecution(async (event, context) => { let total = 0; for (const item of items) { await context.step(async () => { total += item.price; // ⚠️ Mutation lost on replay! return saveItem(item); }); } return { total }; // Inconsistent value! }); // ✅ CORRECT: Accumulate with return values export const handler = withDurableExecution(async (event, context) => { let total = 0; for (const item of items) { total = await context.step(async () => { const newTotal = total + item.price; await saveItem(item); return newTotal; // Return updated value }); } return { total }; // Consistent! }); // ✅ EVEN BETTER: Use map for parallel processing export const handler = withDurableExecution(async (event, context) => { const results = await context.map( items, async (ctx, item) => { await ctx.step(async () => saveItem(item)); return item.price; } ); const total = results.getResults().reduce((sum, price) => sum + price, 0); return { total }; }); Python # ❌ WRONG: Mutations lost on replay @durable_execution def handler(event, context: DurableContext): total = 0 for item in items: context.step( lambda _: save_item_and_mutate(item, total), # ⚠️ Mutation lost on replay! name=f'save-item- { item["id"]}' ) return { 'total': total} # Inconsistent value! # ✅ CORRECT: Accumulate with return values @durable_execution def handler(event, context: DurableContext): total = 0 for item in items: total = context.step( lambda _: save_item_and_return_total(item, total), name=f'save-item- { item["id"]}' ) return { 'total': total} # Consistent! # ✅ EVEN BETTER: Use map for parallel processing @durable_execution def handler(event, context: DurableContext): def process_item(ctx, item): ctx.step(lambda _: save_item(item)) return item['price'] results = context.map(items, process_item) total = sum(results.get_results()) return { 'total': total} Design for idempotency Operations may execute multiple times due to retries or replay. Non-idempotent operations cause duplicate side effects like charging customers twice or sending multiple emails. Use idempotency tokens: Generate tokens inside steps and include them with external API calls to prevent duplicate operations. TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Generate idempotency token once const idempotencyToken = await context.step('generate-idempotency-token', async () => { return crypto.randomUUID(); }); // Use token to prevent duplicate charges const charge = await context.step('charge-payment', async () => { return paymentService.charge( { amount: event.amount, cardToken: event.cardToken, idempotencyKey: idempotencyToken }); }); return { statusCode: 200, charge }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext import uuid @durable_execution def handler(event, context: DurableContext): # Generate idempotency token once idempotency_token = context.step( lambda _: str(uuid.uuid4()), name='generate-idempotency-token' ) # Use token to prevent duplicate charges def charge_payment(_): return payment_service.charge( amount=event['amount'], card_token=event['cardToken'], idempotency_key=idempotency_token ) charge = context.step(charge_payment, name='charge-payment') return { 'statusCode': 200, 'charge': charge} Use at-most-once semantics: For critical operations that must never duplicate (financial transactions, inventory deductions), configure at-most-once execution mode. TypeScript // Critical operation that must not duplicate await context.step('deduct-inventory', async () => { return inventoryService.deduct(event.productId, event.quantity); }, { executionMode: 'AT_MOST_ONCE_PER_RETRY' }); Python # Critical operation that must not duplicate context.step( lambda _: inventory_service.deduct(event['productId'], event['quantity']), name='deduct-inventory', config=StepConfig(execution_mode='AT_MOST_ONCE_PER_RETRY') ) Database idempotency: Use check-before-write patterns, conditional updates, or upsert operations to prevent duplicate records. Manage state efficiently Every checkpoint saves state to persistent storage. Large state objects increase costs, slow checkpointing, and impact performance. Store only essential workflow coordination data. Keep state minimal: Store IDs and references, not full objects Fetch detailed data within steps as needed Use Amazon S3 or DynamoDB for large data, pass references in state Avoid passing large payloads between steps TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Store only the order ID, not the full order object const orderId = event.orderId; // Fetch data within each step as needed await context.step('validate-order', async () => { const order = await orderService.getOrder(orderId); return validateOrder(order); }); await context.step('process-payment', async () => { const order = await orderService.getOrder(orderId); return processPayment(order); }); return { statusCode: 200, orderId }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext @durable_execution def handler(event, context: DurableContext): # Store only the order ID, not the full order object order_id = event['orderId'] # Fetch data within each step as needed context.step( lambda _: validate_order(order_service.get_order(order_id)), name='validate-order' ) context.step( lambda _: process_payment(order_service.get_order(order_id)), name='process-payment' ) return { 'statusCode': 200, 'orderId': order_id} Design effective steps Steps are the fundamental unit of work in durable functions. Well-designed steps make workflows easier to understand, debug, and maintain. Step design principles: Use descriptive names - Names like validate-order instead of step1 make logs and errors easier to understand Keep names static - Don't use dynamic names with timestamps or random values. Step names must be deterministic for replay Balance granularity - Break complex operations into focused steps, but avoid excessive tiny steps that increase checkpoint overhead Group related operations - Operations that should succeed or fail together belong in the same step Use wait operations efficiently Wait operations suspend execution without consuming resources or incurring costs. Use them instead of keeping Lambda running. Time-based waits: Use context.wait() for delays instead of setTimeout or sleep . External callbacks: Use context.waitForCallback() when waiting for external systems. Always set timeouts to prevent indefinite waits. Polling: Use context.waitForCondition() with exponential backoff to poll external services without overwhelming them. TypeScript // Wait 24 hours without cost await context.wait( { seconds: 86400 }); // Wait for external callback with timeout const result = await context.waitForCallback( 'external-job', async (callbackId) => { await externalService.submitJob( { data: event.data, webhookUrl: `https://api.example.com/callbacks/$ { callbackId}` }); }, { timeout: { seconds: 3600 } } ); Python # Wait 24 hours without cost context.wait(86400) # Wait for external callback with timeout result = context.wait_for_callback( lambda callback_id: external_service.submit_job( data=event['data'], webhook_url=f'https://api.example.com/callbacks/ { callback_id}' ), name='external-job', config=WaitForCallbackConfig(timeout_seconds=3600) ) Additional considerations Error handling: Retry transient failures like network timeouts and rate limits. Don't retry permanent failures like invalid input or authentication errors. Configure retry strategies with appropriate max attempts and backoff rates. For detailed examples, see Error handling and retries . Performance: Minimize checkpoint size by storing references instead of full payloads. Use context.parallel() and context.map() to execute independent operations concurrently. Batch related operations to reduce checkpoint overhead. Versioning: Invoke functions with version numbers or aliases to pin executions to specific code versions. Ensure new code versions can handle state from older versions. Don't rename steps or change their behavior in ways that break replay. Serialization: Use JSON-compatible types for operation inputs and results. Convert dates to ISO strings and custom objects to plain objects before passing them to durable operations. Monitoring: Enable structured logging with execution IDs and step names. Set up CloudWatch alarms for error rates and execution duration. Use tracing to identify bottlenecks. For detailed guidance, see Monitoring and debugging . Testing: Test happy path, error handling, and replay behavior. Test timeout scenarios for callbacks and waits. Use local testing to reduce iteration time. For detailed guidance, see Testing durable functions . Common mistakes to avoid: Don't nest context.step() calls, use child contexts instead. Wrap non-deterministic operations in steps. Always set timeouts for callbacks. Balance step granularity with checkpoint overhead. Store references instead of large objects in state. Additional resources Python SDK documentation - Complete API reference, testing patterns, and advanced examples TypeScript SDK documentation - Complete API reference, testing patterns, and advanced examples Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Monitoring durable functions Lambda Managed Instances Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:30 |
https://meeksfamily.uk/~michael/blog/2023/Jun/index.html | Stuff Michael Meeks is doing Stuff Michael Meeks is doing This is my (in)activity log. You might like to visit Collabora Productivity a subsidiary of Collabora focusing on LibreOffice support and services for whom I work. Also if you have the time to read this sort of stuff you could enlighten yourself by going to Unraveling Wittgenstein's net or if you are feeling objectionable perhaps here . Failing that, there are all manner of interesting things to read on the LibreOffice Planet news feed . Older items: 2023 : ( J F M A M J ), 2022 : ( J F M A M J J A S O N D ), 2021 , 2019 , 2018 , 2017 , 2016 , 2015 , 2014 , 2013 , 2012 , 2011 , 2010 , 2009 , 2009 , 2008 , 2007 , 2006 , 2005 , 2004 , 2003 , 2002 , 2001 , 2000 , 1999 , legacy html Fri, 30 Jun 2023 --> 2023-06-30 Friday Mail chew; partner call, lunch, interview, partner call. Amused to read more about the supposed panacea that is distro-less containers . Also read RedHat Open Source commitment . I have a number of thoughts: First what we do: Collabora Online source code is open - our releases are tags in a public git repo, which we also link from help->about - that helps us support people better, and makes everything super transparent. But - I have huge sympathy with this sentiment; emphasis mine: "The generally accepted position that these free rebuilds are just funnels churning out RHEL experts and turning into sales just isn't reality . I wish we lived in that world, but it's not how it actually plays out" . One of the troubling things about being in business is having to live in the real world which can get extremely and painfully real . It is particularly annoying at such times to be told - that making it ever easier for people not to pay is the only true solution. The risks of people taking your hard-work, slapping their brand on it, and not contributing significantly are ones we all have long and disappointing experience with too. Of course the FLOSS licenses allow it - but to feel entitled to have this made extra easy for you is unfortunate. My take is a simple and perhaps radical one: Making it easy for everyone not to pay to support development is profoundly counter-productive . Put another way: someone needs to pay for something scarce . We can try to work out who that someone should be eg. "very large IT organizations" are a traditional favourite, and what is scarce (traditionally signed enterprise binaries), but some degree of compromise is inevitable - I have a long write up on various different compromises in the space here: Sustained Freedom from slide sixteen. I have even more sympathy with the rationale, because RedHat is a pure-play FLOSS company. If you are part of the Proprietary periphary mob (also known as OpenCore) - then you have your own proprietary stuff that allows you to make it arbitrarily hard for people not to pay to support development. As such - ironically - as a community it seems we're once again focusing our criticism on those who differ least from FOSS orthodoxy, and who are doing the best job of up-stream contribution. However - this rationale as presented: "Simply rebuilding code, without adding value or changing it in any way, represents a real threat to open source companies everywhere. This is a real threat to open source, and one that has the potential to revert open source back into a hobbyist- and hackers-only activity." simultaneously seems contrived. Surely that is what Linux Distros do: they dis-intermediate FLOSS projects - but it is perhaps also an opportunity, let me explain: One of the significant concerns around commercially funded FLOSS projects is that of being dis-intermediated: having their latest code bundled into a Linux distro where it is simultaneously extremely hard to get leads (which drive sales) from downloaders -and- long-term support guarentees are met by that distributor; often without any feature contribution back. The same dis-intermediation threat is there around cloud provision of pure-play FLOSS products. Sometimes creator companies are simply acquired to get the support team in-house; while fair - that seems far from optimal. I see a potentially lucrative opportunity for the first enterprise distro that can build a wider partner ecosystem of contributing open-source companies by - including them into their enterprise products via some transparent business and support co-development model. We have lots of excellent, standard FLOSS licenses for code, but few successful open-agreements for go-to-market FLOSS collaboration - building a more diverse and widespread Open Source business community. Can you imagine the power of the possibilities of RedHat/IBM's scale and experience helping to bring their extraordinary reach into enterprises to a snowballing set of businesses built around the RedHat platform with some turbo-charged mutual partnership model? The volume of FLOSS that could be written & improved, and the niches we could fill and sustain? Either way, it will be interesting to see where this goes long term. For those with very long memories I believe that Cygnus tree used to be distributed only to their customers - in the 1990s. Thu, 29 Jun 2023 --> 2023-06-29 Thursday Early morning accessibility call - good stuff, sales call. Interviews with PM candidates, partner call; mail chew. Interviews into cell group + dinner combination until late. Wed, 28 Jun 2023 --> 2023-06-28 Wednesday Partner call, weekly sales call, admin, PM interviews, catch-up calls, admin. Pushed some tile management wins. Nissan Leaf not charging, silly messages on the car console - expect its down to the well known low-charging problems of the 12V battery; annoying. Bought another, and replaced the battery: lead & acid still: amazing. Still no joy, re-booted pod-point: perhaps the problem is there, charged on a 13A socket instead. Tue, 27 Jun 2023 --> 2023-06-27 Tuesday Catch up with Andras, lengthy partner call, lunch. Sync with Pedro, more admin, got to a bit of hacking in the evening - fun; then couldn't sleep. Mon, 26 Jun 2023 --> 2023-06-26 Monday Mail chew; planning call, chat with Elisa; lunch. Helped Nick with an unusual macro problem and an upgrade. OpenChain training, more admin. Sun, 25 Jun 2023 --> 2023-06-25 Sunday All Saints, helped Peter with the organ, noticed how a mid-week practice is rather a benefit by its absence. Back for pizza lunch. Rested variously into the evening; watched Ad-Astra with J.: curiously dissatisfying. Chatted with the babes on their return from church. Sat, 24 Jun 2023 --> 2023-06-24 Saturday Up lateish, off to open-Church; back for BBQ lunch with David; attacked the hedge together on a super hot day: great progress. Off to Bob & Dee's leaving do in Beck Row. Fri, 23 Jun 2023 --> 2023-06-23 Friday Up early, out for a run with J. partner call, interview, lunch, interview, partner call, admin. Booked travel to LibreOffice Conference 2023 which should be fun. Thu, 22 Jun 2023 --> 2023-06-22 Thursday Technical planning call, COOL community call, sales call, interview, offer, customer call. Up extremely late hacking on tile caching. Wed, 21 Jun 2023 --> 2023-06-21 Wednesday Mail chew; early partner call, sales call; admin; Lunch. CP all-hands, sync with Miklos. Managed to re-activate bank account dongle after some HSBC oddity. Tue, 20 Jun 2023 --> 2023-06-20 Tuesday Up early, out for a run with J. chat with Kendy, product call, admin, slides. Lunch, monthly mgmt meeting, more calls. Mon, 19 Jun 2023 --> 2023-06-19 Monday Caught up the blog; mail chew, status report. Planning call, chat with Shehr and Pedro. Lunch. Customer call, sync with Andras. PCC meeting in the evening, wrote minutes. Sun, 18 Jun 2023 --> 2023-06-18 Sunday All Saints in the morning with H. Sue spoke - caught up with the wider church family; home for a pizza lunch with B&A visiting - lovely, baked Alaska as birthday treat desert. Slept in the afternoon, watched The Ballad of Buster Scruggs - amused by the Cohen Brothers. Sat, 17 Jun 2023 --> 2023-06-17 Saturday Up earlyish, babes sleeping - out with J. to Lavenham for a walk through the beautiful countryside nearby in the sunshine; pit stop at a pub. Home for BBQ in the evening with the family. Worked on slides until late. Fri, 16 Jun 2023 --> 2023-06-16 Friday Out for a run with J. in the morning. Partner & customer calls, worked on project slides. Catch up with Luigi, sync with Andras. Thu, 15 Jun 2023 --> 2023-06-15 Thursday Catch up of E-mail backlog; technical planning call, COOL community call, catch up with Sarper, 1:1 with Miklos, chat with Caolan; more admin. Picked up E. from Soham, bible study group with Cyrille & Jan. Wed, 14 Jun 2023 --> 2023-06-14 Wednesday Up earlyish, trains to the airport, flight home - hacked on cleaning up a re-work of tile management in our javascript for more performance - fun. Trains home variously. E's birthday dinner in the evening, so lovely to see the daughters grow up. Tue, 13 Jun 2023 --> 2023-06-13 Tuesday Up early, found the venue, talked to lots of customers, partners and listened to some great presentations; talked about CODE 23.05 - out today and some of the great new features there, as well as the great integration work Julius & team have done at Nextcloud with the SmartPicker and other bits around COOL. Interesting lunch with some customers. Back to more talks, partner event slides; talked with lots of partner and sales people until late; out to dinner in town again, bed late. Mon, 12 Jun 2023 --> 2023-06-12 Monday Up early, train with H. and M. to Cambrige, set off to Munich. Discovered another joy of TravelPerk: it allows business travellers to book back-packer style tickets without making it clear - where you have no guarenteed seat. Eventually arrived, texted a few people to meet up - I should really organize my life further in advance. Headed to the hotel, met up with Marc, Niels kindly took us to the beer-hall for dinner with the Nextcloud team. Great evening, home late. Sun, 11 Jun 2023 --> 2023-06-11 Sunday All Saints, played with H. Bridge Violin starting to have a buzz & also flaking audio wise; a stray cable inside? may have to go back to a louder wooden violin & a pick; perhaps carbon fibre is best only for bows. Home, pizza lunch with the babes, hot day - slept exhaustedly in the garden for much of the afternoon. Sat, 10 Jun 2023 --> 2023-06-10 Saturday Up earlyish, worked on tile code on and off much of the day, rather rapid interview. Helped E. with her statistics after BBQ dinner; worked until late at night & slept badly. Fri, 09 Jun 2023 --> 2023-06-09 Friday Poked at 23.05 testing, marketing, and dug into a tile management issue with large presentations. Came up with an entirely better way of doing this and hacked on it between partner meetings. Thu, 08 Jun 2023 --> 2023-06-08 Thursday Another CODE 23.05 release standup; chasing some interesting performance regressions interactively. Making some good progress, exciting times. COOL community call, partner call, catch up with Andras, more marketing review. Cell group in the evening. Wed, 07 Jun 2023 --> 2023-06-07 Wednesday Day full of meetings; stand-up for 23.05 release. Accessibiltiy call, catch up with Sarper, two interviews, marketing call. All Saints band practice with H. Tue, 06 Jun 2023 --> 2023-06-06 Tuesday App early, off to the Drivery to record some Hub 5 announcement segments with the team - lots of interesting kit there. Out for a rapid burger, airport, RyanAir - flight delayed by an hour on the tarmac baking the occupants for a mechanical fault. Home late. Mon, 05 Jun 2023 --> 2023-06-05 Monday Checked in late at night for flight; apparently TravelPerk/RyanAir think it is clever to give users a much worse experience than booking direct when using a booking agent: had to re-validate passports pay Eur 0.6 and similarly bogus stuff: annoying. Much easier to book directly. Planning call with the team; lots of good things happening. Drove to STN, flight to Berlin, BBQ at Frank's (nice!) pad, and talked with the team until late. Found and managed to check-into room rather late. Sun, 04 Jun 2023 --> 2023-06-04 Sunday All Saints, lunch; slugged tiredly much of the day. Watched a Potter, fantastic beasts - well made it seems; still with a repetitive junior/outsider motif. Sat, 03 Jun 2023 --> 2023-06-03 Saturday Dropped jacket to the dry cleaners, and went shopping with J. at Aldi - watched a shop-lifter get caught red handed there; interesting. Got some work backlog done, candidate application triage. Plugged away at a lathe tool for copying things, and a shelf for J. David & Allison over for a BBQ in the evening interupted by J. doing lots of ferrying of small girls; lovely to catch up. Fri, 02 Jun 2023 --> 2023-06-02 Friday Mail chew, partner call, sales meeting, tested collaborative editing in a call; lunch, partner call. More mail chew, syncing etc. partner call. Continued combing through CVs for various new roles at Collabora. Good to see LibreOffice in the Flatpak app-store announced as the future on RHEL; and for those that missed it glad to have Caolán still on the team. Thu, 01 Jun 2023 --> 2023-06-01 Thursday Up, had some meetings. Technical planning call, COOL community call, catch up with Kendy, 1:1 with Miklos. Encouraging marketing call. My content in this blog and associated images / data under images/ and data/ directories are (usually) created by me and (unless obviously labelled otherwise) are licensed under the public domain, and/or if that doesn't float your boat a CC0 license. I encourage linking back (of course) to help people decide for themselves, in context, in the battle for ideas, and I love fixes / improvements / corrections by private mail. In case it's not painfully obvious: the reflections reflected here are my own; mine, all mine ! and don't reflect the views of Collabora, SUSE, Novell, The Document Foundation, Spaghetti Hurlers (International), or anyone else. It's also important to realise that I'm not in on the Swedish Conspiracy . Occasionally people ask for formal photos for conferences or fun . Michael Meeks ( michael.meeks@collabora.com ) | 2026-01-13T09:29:30 |
https://meeksfamily.uk/~michael/blog/2022/Jan/index.html | Stuff Michael Meeks is doing Stuff Michael Meeks is doing This is my (in)activity log. You might like to visit Collabora Productivity a subsidiary of Collabora focusing on LibreOffice support and services for whom I work. Also if you have the time to read this sort of stuff you could enlighten yourself by going to Unraveling Wittgenstein's net or if you are feeling objectionable perhaps here . Failing that, there are all manner of interesting things to read on the LibreOffice Planet news feed . Older items: 2023 : ( J F M A M J ), 2022 : ( J F M A M J J A S O N D ), 2021 , 2019 , 2018 , 2017 , 2016 , 2015 , 2014 , 2013 , 2012 , 2011 , 2010 , 2009 , 2009 , 2008 , 2007 , 2006 , 2005 , 2004 , 2003 , 2002 , 2001 , 2000 , 1999 , legacy html Mon, 31 Jan 2022 --> 2022-01-31 Monday Planning call much of the morning; tried to air the formaldehyde smell from out-gassing book-shelves from the room somehow without letting the cold in. Sun, 30 Jan 2022 --> 2022-01-30 Sunday All Saints, David came over, slugged variously. Sat, 29 Jan 2022 --> 2022-01-29 Saturday Visited Bruce & Anne, lovely to see them. Fri, 28 Jan 2022 --> 2022-01-28 Friday Shelves arrived from IKEA (finally), TDF employees call, encouraging customer/partner call, mail, encouraging meet up with Arawa's great team; catch up with Eloy, Gokay, and an interestig west-coast start-up. Admin, mail, minutes, catch-up. Thu, 27 Jan 2022 --> 2022-01-27 Thursday Catch up with Miklos & Andras; COOL community call. Sorted out purple. C'bra quarterly mgmt call much of the afternoon and evening; caught up with frenzy of detailed task backlog in parallel. Finally got to TDF budget ranking; tweaked my ssh-config for gerrit thanks to mst & erAck. PubkeyAcceptedKeyTypes ssh-rsa did it for gerrit. Transferred H. money for university food & shelter. Wed, 26 Jan 2022 --> 2022-01-26 Wednesday Took babes to school, CS3 interspersed with sales call with Eloy; catch-up with Gokay. C'bra quarterly mgmt call much of the afternoon - caught up with admin in parallel. Tue, 25 Jan 2022 --> 2022-01-25 Tuesday Planning call, TDF marketing call; worked on CS3 slides until late, called Pad. Mon, 24 Jan 2022 --> 2022-01-24 Monday Planning call, TDF marketing call; worked on CS3 slides until late. Sun, 23 Jan 2022 --> 2022-01-23 Sunday All Saints, 2m Peter played the Organ well; sang with Mary. Bob spoke, home for roast lunch. Slugged vigorously; picked up babes from StAG in the evening. Sat, 22 Jan 2022 --> 2022-01-22 Saturday Up lateish, breakfast with the crowd; got the garage tidied up again. Worked on J's counselling room facade - routed up the door sill, managed to take ~all the teeth off the circular saw removing the top 1cm of the frame: which made it substantially harder to cut with. Eventually cut it down to size. Fri, 21 Jan 2022 --> 2022-01-21 Friday FOSDEM slides, recorded & up-loaded video - looking forward to it; set to work on CS3 slides, talk with Simon, catch up with Gokay. Helped N. tidy the house, picked up Charlie, and got to work making the garage habitable for boys: amazingly there is a concrete floor under the dust. Lots of N's friends turned up for 17th birthday party & sleepover; good to see them, tried to teach several lads to play 'go'. Left them to it, 2:30am the singing stopped, 3:30 - boys out to the garage to sleep. Thu, 20 Jan 2022 --> 2022-01-20 Thursday 1:1's, COOL community call; discussion of the color purple: fun. Wonderful to see the team release COOL 21.11 today - with all the goodness of CODE, and some new RTL functionality for our Arabic, Hebrew and other Indic users online. Wed, 19 Jan 2022 --> 2022-01-19 Wednesday Catch up with Dennis, sales call, monthly all-hands call. Release material review, TDF Advisory Board call. All Saints, practice singing. Tue, 18 Jan 2022 --> 2022-01-18 Tuesday Press pre-briefing on COOL 21.11, catch up with Simon, monthly mgmt call, mail chew. Mon, 17 Jan 2022 --> 2022-01-17 Monday New-approach to planning calls, mail, catch up with Philippe. Sun, 16 Jan 2022 --> 2022-01-16 Sunday Up early sawed a barrel in half to grow potatoes in for Father, re-arranged the garage contents a bit; lunch. Drove home, sermon in the car, dinner with the babes; relaxed variously. Sat, 15 Jan 2022 --> 2022-01-15 Saturday Up earlyish, breakfast. Got support prepared by Dad screwed into the attic, wire through, ceiling switch mounted and wired. Out to visit a friend of Mum's who kindly lent H. a lovely full-size Viola. Home - back onto wiring with Father; a fine lunch. Drove H. to Durham, and managed to get her bits back to her study with E's help. Wandered through the Cathedral, and out for a coffee with her friend - lovely. Bid a fond farewell. Drove home, dinner, watched Cinderella & had snacks with the parents. Fri, 14 Jan 2022 --> 2022-01-14 Friday Sync with Gokay, TDF board calls, catch up with Frank, go/no-go decision call with Ash, Gokay, patch review etc. Packed left N. and M. at home, and drove to M&D's. Thu, 13 Jan 2022 --> 2022-01-13 Thursday Chat with Miklos, partner call, COOL community call. Lunch with H, sync with Eloy, partner call. Provider check-in, caught end of the ESC, customer call. Wed, 12 Jan 2022 --> 2022-01-12 Wednesday Sales call, catch up with Eloy, Andras, Gokay. Tue, 11 Jan 2022 --> 2022-01-11 Tuesday Catch-up with Mike K, Kendy, Simon L, mail chew. Into town with J. and H. to meet up with N. for a birthday celebration at Nandos together. Mon, 10 Jan 2022 --> 2022-01-10 Monday Monster planning-call 2.5hrs - the joys of approaching release time? Intro call for Italo, Mike & Simon L. Partner discussion. Sun, 09 Jan 2022 --> 2022-01-09 Sunday All Saints; band. Pizza lunch, relaxed variously with the family in the afternoon.. Sat, 08 Jan 2022 --> 2022-01-08 Saturday Chewed at mail & some hackery in the morning. David over in the afternoon, present opening; played with arranging Spot-It cards into a 7x7 grid with some vanishing points ineffectually for a while before cheating. Got timber joinery sorted, and glued together, dinner, relaxed together. Fri, 07 Jan 2022 --> 2022-01-07 Friday Mail chew, prioritization, patch review, some hacking. Durham switched to online teaching for two weeks for H. so she could stay home for a bit longer: fun; re-arranged the weekend with M&D. Thu, 06 Jan 2022 --> 2022-01-06 Thursday Various 1:1's, COOL community call, catch up with Gokay, poked at tickets & bugs, caught some of the ESC call. Susan around for house-group, chatted with her and J. happily. Wed, 05 Jan 2022 --> 2022-01-05 Wednesday Weekly sales call, team dev show & tell - lots of encouraging goodness being created. Call with Gokay. Started adjusting window frame for the garage, cut a suitable mortice in the nice mahogony. Tue, 04 Jan 2022 --> 2022-01-04 Tuesday Various 1:1's, catch-up with Ezinne, poked at delta generation, and customer pieces. Mon, 03 Jan 2022 --> 2022-01-03 Monday Mail chew, planning call, J. got the decorations down, caught up with Simon L, plugged at admin, continued reading back through E-mail; out for a run with J. Sun, 02 Jan 2022 --> 2022-01-02 Sunday All Saints with H. in the morning; dropped H. at the train, home for a Pizza lunch with Hannah, Nick & Joni played games with them; lovely to catch-up. Sat, 01 Jan 2022 --> 2022-01-01 Saturday Out for a walk with J. H. M. E. - passed the somewhat extraordinary Suffolk Hedgehog Hospital: (Hedge-hogs, why can't they share?) - and had a nice walk around Ousden and admired what looks like a bunker on Back Street. Spent some considerable time adding a lock to our en-suite toilet door; can finally put router & jigs away after their long service - good. Hacking until midnight - ooh it's addictive; got compressed deltas almost working with zlib - lots of bandwidth and CPU savings left & right I hope. My content in this blog and associated images / data under images/ and data/ directories are (usually) created by me and (unless obviously labelled otherwise) are licensed under the public domain, and/or if that doesn't float your boat a CC0 license. I encourage linking back (of course) to help people decide for themselves, in context, in the battle for ideas, and I love fixes / improvements / corrections by private mail. In case it's not painfully obvious: the reflections reflected here are my own; mine, all mine ! and don't reflect the views of Collabora, SUSE, Novell, The Document Foundation, Spaghetti Hurlers (International), or anyone else. It's also important to realise that I'm not in on the Swedish Conspiracy . Occasionally people ask for formal photos for conferences or fun . Michael Meeks ( michael.meeks@collabora.com ) | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/zh_tw/lambda/latest/dg/durable-monitoring.html | 監控耐用的 函數 - AWS Lambda 監控耐用的 函數 - AWS Lambda 文件 AWS Lambda 開發人員指南 CloudWatch 指標 EventBridge 事件 AWS X-Ray 追蹤 本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。 監控耐用的 函數 您可以使用 CloudWatch 指標、CloudWatch Logs 和追蹤來監控耐用的函數。由於耐用的函數可以長時間執行並跨越多個函數叫用，因此監控它們需要了解其獨特的執行模式，包括檢查點、狀態轉換和重播行為。 CloudWatch 指標 Lambda 會自動將指標發佈至 CloudWatch，無需額外費用。耐用函數提供超出標準 Lambda 指標的額外指標，協助您監控長時間執行的工作流程、狀態管理和資源使用率。 耐用的執行指標 Lambda 會針對持久性執行發出下列指標： 指標 Description ApproximateRunningDurableExecutions 處於 RUNNING 狀態的耐久執行數目 ApproximateRunningDurableExecutionsUtilization 您帳戶目前正在使用的最大執行中耐久執行配額百分比 DurableExecutionDuration 持久執行保持為 RUNNING 狀態的經過時間，以毫秒為單位 DurableExecutionStarted 啟動的持久性執行數量 DurableExecutionStopped 使用 StopDurableExecution API 停止的耐久執行數目 DurableExecutionSucceeded 成功完成的持久性執行數量 DurableExecutionFailed 因失敗而完成的耐久執行數量 DurableExecutionTimedOut 超過其設定執行逾時的持久執行數量 DurableExecutionOperations 在持久性執行內執行的累計操作數 （上限：3，000) DurableExecutionStorageWrittenBytes 持久性執行所保留以位元組為單位的累積資料量 （上限：100 MB) CloudWatch 指標 Lambda 會發出耐用函數的標準調用、效能和並行指標。由於耐久的執行可能會在通過檢查點和重播時跨越多個函數叫用，因此這些指標的行為與標準函數不同： 調用： 計算每個函數調用，包括重播。單一耐久執行可以產生多個調用資料點。 持續時間： 分別測量每個函數叫用。 DurableExecutionDuration 用於單一持久性執行所花費的總時間。 錯誤： 追蹤函數叫用失敗。 DurableExecutionFailed 用於執行層級失敗。 如需標準 Lambda 指標的完整清單，請參閱 Lambda 函數的指標類型 。 建立 CloudWatch 警示 建立 CloudWatch 警示，以在指標超過閾值時通知您。常見警示包括： ApproximateRunningDurableExecutionsUtilization 超過配額的 80% DurableExecutionFailed 增加超過閾值 DurableExecutionTimedOut 表示執行逾時 DurableExecutionStorageWrittenBytes 接近儲存限制 如需詳細資訊， 請參閱使用 CloudWatch 警示。 . EventBridge 事件 Lambda 會將持久的執行狀態變更事件發佈至 EventBridge。您可以使用這些事件來觸發工作流程、傳送通知，或追蹤耐久函數的執行生命週期變更。 持久性執行狀態變更事件 每當持久性執行變更狀態時，Lambda 都會向 EventBridge 發出事件。這些事件具有下列特性： 來源 ： aws.lambda 詳細資訊類型： Durable Execution Status Change 狀態變更事件會針對下列執行狀態發佈： RUNNING - 執行已開始 SUCCEEDED - 執行成功完成 STOPPED - 使用 StopDurableExecution API 停止執行 FAILED - 執行失敗並發生錯誤 TIMED_OUT - 執行超過設定的逾時 下列範例顯示持久的執行狀態變更事件： { "version": "0", "id": "d019b03c-a8a3-9d58-85de-241e96206538", "detail-type": "Durable Execution Status Change", "source": "aws.lambda", "account": "123456789012", "time": "2025-11-20T13:08:22Z", "region": "us-east-1", "resources": [], "detail": { "durableExecutionArn": "arn:aws:lambda:us-east-1:123456789012:function:my-function:$LATEST/durable-execution/090c4189-b18b-4296-9d0c-cfd01dc3a122/9f7d84c9-ea3d-3ffc-b3e5-5ec51c34ffc9", "durableExecutionName": "order-123", "functionArn": "arn:aws:lambda:us-east-1:123456789012:function:my-function:2", "status": "RUNNING", "startTimestamp": "2025-11-20T13:08:22.345Z" } } 對於終端機狀態 ( SUCCEEDED 、 STOPPED 、 FAILED 、 TIMED_OUT )，事件包含指出執行完成時間 endTimestamp 的欄位。 建立 EventBridge 規則 建立規則，將持久的執行狀態變更事件路由到 Amazon Simple Notification Service、Amazon Simple Queue Service 或其他 Lambda 函數等目標。 下列範例會建立符合所有持久執行狀態變更的規則： { "source": ["aws.lambda"], "detail-type": ["Durable Execution Status Change"] } 下列範例會建立僅符合失敗執行的規則： { "source": ["aws.lambda"], "detail-type": ["Durable Execution Status Change"], "detail": { "status": ["FAILED"] } } 下列範例會建立符合特定函數狀態變更的規則： { "source": ["aws.lambda"], "detail-type": ["Durable Execution Status Change"], "detail": { "functionArn": [ { "prefix": "arn:aws:lambda:us-east-1:123456789012:function:my-function" }] } } 如需建立規則的詳細資訊，請參閱《 EventBridge 使用者指南》中的 Amazon EventBridge 教學 課程。 EventBridge AWS X-Ray 追蹤 您可以在耐用的函數上啟用 X-Ray 追蹤。Lambda 會將 X-Ray 追蹤標頭傳遞至持久性執行，讓您追蹤整個工作流程的請求。 若要使用 Lambda 主控台啟用 X-Ray； 追蹤，請選擇您的函數，然後選擇組態、監控和操作工具，然後在 X-Ray 下開啟主動追蹤。 若要使用 啟用 X-Ray 追蹤 AWS CLI： aws lambda update-function-configuration \ --function-name my-durable-function \ --tracing-config Mode=Active 若要使用 啟用 AWS X-Ray 追蹤 AWS SAM： Resources: MyDurableFunction: Type: AWS::Serverless::Function Properties: Tracing: Active DurableConfig: ExecutionTimeout: 3600 如需 X-Ray 的詳細資訊， 請參閱 AWS X-Ray 開發人員指南。 您的瀏覽器已停用或無法使用 Javascript。 您必須啟用 Javascript，才能使用 AWS 文件。請參閱您的瀏覽器說明頁以取得說明。 文件慣用形式 測試耐用函數 最佳實務 此頁面是否有幫助？ - 是 感謝您，讓我們知道我們做得很好！ 若您有空，歡迎您告知我們值得讚許的地方，這樣才能保持良好服務。 此頁面是否有幫助？ - 否 感謝讓我們知道此頁面仍須改善。很抱歉，讓您失望。 若您有空，歡迎您提供改善文件的方式。 | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/lambda/latest/dg/durable-monitoring.html | Monitoring durable functions - AWS Lambda Monitoring durable functions - AWS Lambda Documentation AWS Lambda Developer Guide CloudWatch metrics EventBridge events AWS X-Ray tracing Monitoring durable functions You can monitor your durable functions using CloudWatch metrics, CloudWatch Logs, and tracing. Because durable functions can run for extended periods and span multiple function invocations, monitoring them requires understanding their unique execution patterns, including checkpoints, state transitions, and replay behavior. CloudWatch metrics Lambda automatically publishes metrics to CloudWatch at no additional charge. Durable functions provide additional metrics beyond standard Lambda metrics to help you monitor long-running workflows, state management, and resource utilization. Durable execution metrics Lambda emits the following metrics for durable executions: Metric Description ApproximateRunningDurableExecutions Number of durable executions in the RUNNING state ApproximateRunningDurableExecutionsUtilization Percentage of your account's maximum running durable executions quota currently in use DurableExecutionDuration Elapsed wall-clock time in milliseconds that a durable execution remained in the RUNNING state DurableExecutionStarted Number of durable executions that started DurableExecutionStopped Number of durable executions stopped using the StopDurableExecution API DurableExecutionSucceeded Number of durable executions that completed successfully DurableExecutionFailed Number of durable executions that completed with a failure DurableExecutionTimedOut Number of durable executions that exceeded their configured execution timeout DurableExecutionOperations Cumulative number of operations performed within a durable execution (max: 3,000) DurableExecutionStorageWrittenBytes Cumulative amount of data in bytes persisted by a durable execution (max: 100 MB) CloudWatch metrics Lambda emits standard invocation, performance, and concurrency metrics for durable functions. Because a durable execution can span multiple function invocations as it progresses through checkpoints and replays, these metrics behave differently than for standard functions: Invocations: Counts each function invocation, including replays. A single durable execution can generate multiple invocation data points. Duration: Measures each function invocation separately. Use DurableExecutionDuration for total time taken by a single durable execution. Errors: Tracks function invocation failures. Use DurableExecutionFailed for execution-level failures. For a complete list of standard Lambda metrics, see Types of metrics for Lambda functions . Creating CloudWatch alarms Create CloudWatch alarms to notify you when metrics exceed thresholds. Common alarms include: ApproximateRunningDurableExecutionsUtilization exceeds 80% of your quota DurableExecutionFailed increases above a threshold DurableExecutionTimedOut indicates executions are timing out DurableExecutionStorageWrittenBytes approaches storage limits For more information, see Using CloudWatch alarms. . EventBridge events Lambda publishes durable execution status change events to EventBridge. You can use these events to trigger workflows, send notifications, or track execution lifecycle changes across your durable functions. Durable execution status change events Lambda emits an event to EventBridge whenever a durable execution changes status. These events have the following characteristics: Source: aws.lambda Detail type: Durable Execution Status Change Status change events are published for the following execution states: RUNNING - Execution started SUCCEEDED - Execution completed successfully STOPPED - Execution stopped using the StopDurableExecution API FAILED - Execution failed with an error TIMED_OUT - Execution exceeded the configured timeout The following example shows a durable execution status change event: { "version": "0", "id": "d019b03c-a8a3-9d58-85de-241e96206538", "detail-type": "Durable Execution Status Change", "source": "aws.lambda", "account": "123456789012", "time": "2025-11-20T13:08:22Z", "region": "us-east-1", "resources": [], "detail": { "durableExecutionArn": "arn:aws:lambda:us-east-1:123456789012:function:my-function:$LATEST/durable-execution/090c4189-b18b-4296-9d0c-cfd01dc3a122/9f7d84c9-ea3d-3ffc-b3e5-5ec51c34ffc9", "durableExecutionName": "order-123", "functionArn": "arn:aws:lambda:us-east-1:123456789012:function:my-function:2", "status": "RUNNING", "startTimestamp": "2025-11-20T13:08:22.345Z" } } For terminal states ( SUCCEEDED , STOPPED , FAILED , TIMED_OUT ), the event includes an endTimestamp field indicating when the execution completed. Creating EventBridge rules Create rules to route durable execution status change events to targets like Amazon Simple Notification Service, Amazon Simple Queue Service, or other Lambda functions. The following example creates a rule that matches all durable execution status changes: { "source": ["aws.lambda"], "detail-type": ["Durable Execution Status Change"] } The following example creates a rule that matches only failed executions: { "source": ["aws.lambda"], "detail-type": ["Durable Execution Status Change"], "detail": { "status": ["FAILED"] } } The following example creates a rule that matches status changes for a specific function: { "source": ["aws.lambda"], "detail-type": ["Durable Execution Status Change"], "detail": { "functionArn": [ { "prefix": "arn:aws:lambda:us-east-1:123456789012:function:my-function" }] } } For more information about creating rules, see Amazon EventBridge tutorials in the EventBridge User Guide. AWS X-Ray tracing You can enable X-Ray tracing on your durable functions. Lambda passes the X-Ray trace header to the durable execution, allowing you to trace requests across your workflow. To enable X-Ray; tracing using the Lambda console, choose your function, then choose Configuration, Monitoring and operations tools, and turn on Active tracing under X-Ray. To enable X-Ray tracing using the AWS CLI: aws lambda update-function-configuration \ --function-name my-durable-function \ --tracing-config Mode=Active To enable AWS X-Ray tracing using AWS SAM: Resources: MyDurableFunction: Type: AWS::Serverless::Function Properties: Tracing: Active DurableConfig: ExecutionTimeout: 3600 For more information about X-Ray, see the AWS X-Ray Developer Guide. Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Testing durable functions Best practices Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/id_id/lambda/latest/dg/durable-security.html | Keamanan dan izin untuk fungsi Lambda yang tahan lama - AWS Lambda Keamanan dan izin untuk fungsi Lambda yang tahan lama - AWS Lambda Dokumentasi AWS Lambda Panduan Developerr Izin peran eksekusi Enkripsi negara CloudTrail penebangan Pertimbangan lintas akun Fitur keamanan Lambda yang diwarisi Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Keamanan dan izin untuk fungsi Lambda yang tahan lama Fungsi tahan lama Lambda memerlukan izin IAM khusus untuk mengelola operasi pos pemeriksaan. Ikuti prinsip hak istimewa paling sedikit dengan hanya memberikan izin yang dibutuhkan fungsi Anda. Izin peran eksekusi Peran eksekusi fungsi tahan lama Anda memerlukan izin untuk membuat pos pemeriksaan dan mengambil status eksekusi. Kebijakan berikut menunjukkan izin minimum yang diperlukan: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "lambda:CheckpointDurableExecution", "lambda:GetDurableExecutionState" ], "Resource": "arn:aws:lambda:region:account-id:function:function-name:*" } ] } Saat Anda membuat fungsi tahan lama menggunakan konsol, Lambda secara otomatis menambahkan izin ini ke peran eksekusi. Jika Anda membuat fungsi menggunakan AWS CLI or AWS CloudFormation, tambahkan izin ini ke peran eksekusi Anda. Prinsip hak istimewa paling sedikit Cakupan Resource elemen ke fungsi tertentu ARNs alih-alih menggunakan wildcard. Ini membatasi peran eksekusi ke operasi pos pemeriksaan hanya untuk fungsi yang membutuhkannya. Contoh: Izin tercakup untuk beberapa fungsi { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "lambda:CheckpointDurableExecution", "lambda:GetDurableExecutionState" ], "Resource": [ "arn:aws:lambda:us-east-1:123456789012:function:orderProcessor:*", "arn:aws:lambda:us-east-1:123456789012:function:paymentHandler:*" ] } ] } Atau, Anda dapat menggunakan kebijakan AWS terkelola AWSLambdaBasicDurableExecutionRolePolicy yang menyertakan izin eksekusi tahan lama yang diperlukan bersama dengan izin eksekusi Lambda dasar untuk CloudWatch Log Amazon. Enkripsi negara Fungsi tahan lama Lambda secara otomatis mengaktifkan enkripsi saat istirahat menggunakan kunci AWS yang dimiliki tanpa biaya. Setiap eksekusi fungsi mempertahankan status terisolasi yang tidak dapat diakses oleh eksekusi lain. Kunci terkelola pelanggan (CMK) tidak didukung. Data pos pemeriksaan meliputi: Hasil langkah dan nilai kembalikan Kemajuan eksekusi dan timeline Tunggu informasi status Semua data dienkripsi dalam perjalanan menggunakan TLS ketika Lambda membaca atau menulis data pos pemeriksaan. Enkripsi khusus dengan serializer dan deserializer khusus Untuk persyaratan keamanan kritis, Anda dapat menerapkan mekanisme enkripsi dan dekripsi Anda sendiri menggunakan serializer kustom dan deserializer () menggunakan SDK yang tahan lama. SerDer Pendekatan ini memberi Anda kontrol penuh atas kunci enkripsi dan algoritma yang digunakan untuk melindungi data pos pemeriksaan. penting Saat Anda menggunakan enkripsi khusus, Anda kehilangan visibilitas hasil operasi di konsol Lambda dan respons API. Data pos pemeriksaan muncul dienkripsi dalam riwayat eksekusi dan tidak dapat diperiksa tanpa dekripsi. Peran eksekusi fungsi Anda membutuhkan kms:Encrypt dan kms:Decrypt izin untuk AWS KMS kunci yang digunakan dalam SerDer implementasi kustom. CloudTrail penebangan Lambda mencatat operasi pos pemeriksaan sebagai peristiwa data di. AWS CloudTrail Anda dapat menggunakan CloudTrail untuk mengaudit saat pos pemeriksaan dibuat, melacak perubahan status eksekusi, dan memantau akses ke data eksekusi yang tahan lama. Operasi pos pemeriksaan muncul di CloudTrail log dengan nama acara berikut: CheckpointDurableExecution - Log ketika langkah selesai dan membuat pos pemeriksaan GetDurableExecutionState - Tercatat saat Lambda mengambil status eksekusi selama pemutaran ulang Untuk mengaktifkan pencatatan peristiwa data untuk fungsi tahan lama, konfigurasikan CloudTrail jejak untuk mencatat peristiwa data Lambda. Untuk informasi selengkapnya, lihat Mencatat peristiwa data di Panduan CloudTrail Pengguna. Contoh: entri CloudTrail log untuk operasi pos pemeriksaan { "eventVersion": "1.08", "eventTime": "2024-11-16T10:30:45Z", "eventName": "CheckpointDurableExecution", "eventSource": "lambda.amazonaws.com", "requestParameters": { "functionName": "myDurableFunction", "executionId": "exec-abc123", "stepId": "step-1" }, "responseElements": null, "eventType": "AwsApiCall" } Pertimbangan lintas akun Jika Anda menjalankan fungsi tahan lama di seluruh AWS akun, akun panggilan memerlukan lambda:InvokeFunction izin, tetapi operasi pos pemeriksaan selalu menggunakan peran eksekusi di akun fungsi. Akun panggilan tidak dapat mengakses data pos pemeriksaan atau status eksekusi secara langsung. Isolasi ini memastikan bahwa data pos pemeriksaan tetap aman di dalam akun fungsi, bahkan ketika dipanggil dari akun eksternal. Fitur keamanan Lambda yang diwarisi Fungsi tahan lama mewarisi semua fitur keamanan, tata kelola, dan kepatuhan dari Lambda, termasuk konektivitas VPC, enkripsi variabel lingkungan, antrian surat mati, konkurensi cadangan, fungsi, penandatanganan kode, dan sertifikasi kepatuhan (SOC URLs, PCI DSS, HIPAA, dll.). Untuk informasi terperinci tentang fitur keamanan Lambda, lihat Keamanan AWS Lambda di Panduan Pengembang Lambda. Satu-satunya pertimbangan keamanan tambahan untuk fungsi tahan lama adalah izin pos pemeriksaan yang didokumentasikan dalam panduan ini. Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Contoh Eksekusi SDK yang tahan lama Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:29:30 |
https://mastodon.social/share?text=Sending+Notifications+in+Pipeline+https%3A%2F%2Fwww.jenkins.io%2Fblog%2F2016%2F07%2F18%2Fpipeline-notifications%2F#logo-symbol-wordmark | Log in - Mastodon Login to mastodon.social Login with your mastodon.social credentials. If your account is hosted on a different server, you will not be able to log in here. E-mail address * Password Log in Sign up Forgot your password? Didn't receive a confirmation link? | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/fr_fr/lambda/latest/dg/durable-best-practices.html | Meilleures pratiques pour les fonctions durables de Lambda - AWS Lambda Meilleures pratiques pour les fonctions durables de Lambda - AWS Lambda Documentation AWS Lambda Guide du développeur Écrire du code déterministe Conception axée sur l'idempuissance Gérez efficacement l'état Concevez des étapes efficaces Utilisez efficacement les opérations d'attente Considérations supplémentaires Ressources supplémentaires Les traductions sont fournies par des outils de traduction automatique. En cas de conflit entre le contenu d'une traduction et celui de la version originale en anglais, la version anglaise prévaudra. Meilleures pratiques pour les fonctions durables de Lambda Les fonctions durables utilisent un modèle d'exécution basé sur le replay qui nécessite des modèles différents de ceux des fonctions Lambda traditionnelles. Suivez ces meilleures pratiques pour créer des flux de travail fiables et rentables. Écrire du code déterministe Pendant la réexécution, votre fonction s'exécute depuis le début et doit suivre le même chemin d'exécution que l'exécution initiale. Le code en dehors des opérations durables doit être déterministe et produire les mêmes résultats avec les mêmes entrées. Répartissez les opérations non déterministes par étapes : Génération de nombres aléatoires et UUIDs Heure actuelle ou horodatage Appels d'API externes et requêtes de base de données Opérations du système de fichiers TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; import { randomUUID } from 'crypto'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Generate transaction ID inside a step const transactionId = await context.step('generate-transaction-id', async () => { return randomUUID(); }); // Use the same ID throughout execution, even during replay const payment = await context.step('process-payment', async () => { return processPayment(event.amount, transactionId); }); return { statusCode: 200, transactionId, payment }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext import uuid @durable_execution def handler(event, context: DurableContext): # Generate transaction ID inside a step transaction_id = context.step( lambda _: str(uuid.uuid4()), name='generate-transaction-id' ) # Use the same ID throughout execution, even during replay payment = context.step( lambda _: process_payment(event['amount'], transaction_id), name='process-payment' ) return { 'statusCode': 200, 'transactionId': transaction_id, 'payment': payment} Important N'utilisez pas de variables globales ou de fermetures pour partager l'état entre les étapes. Transmettez les données via les valeurs de retour. L'état global se brise pendant la rediffusion car les étapes renvoient les résultats mis en cache mais les variables globales sont réinitialisées. Évitez les mutations de fermeture : les variables capturées lors des fermetures peuvent perdre des mutations pendant la rediffusion. Les étapes renvoient les résultats mis en cache, mais les mises à jour des variables en dehors de l'étape ne sont pas reproduites. TypeScript // ❌ WRONG: Mutations lost on replay export const handler = withDurableExecution(async (event, context) => { let total = 0; for (const item of items) { await context.step(async () => { total += item.price; // ⚠️ Mutation lost on replay! return saveItem(item); }); } return { total }; // Inconsistent value! }); // ✅ CORRECT: Accumulate with return values export const handler = withDurableExecution(async (event, context) => { let total = 0; for (const item of items) { total = await context.step(async () => { const newTotal = total + item.price; await saveItem(item); return newTotal; // Return updated value }); } return { total }; // Consistent! }); // ✅ EVEN BETTER: Use map for parallel processing export const handler = withDurableExecution(async (event, context) => { const results = await context.map( items, async (ctx, item) => { await ctx.step(async () => saveItem(item)); return item.price; } ); const total = results.getResults().reduce((sum, price) => sum + price, 0); return { total }; }); Python # ❌ WRONG: Mutations lost on replay @durable_execution def handler(event, context: DurableContext): total = 0 for item in items: context.step( lambda _: save_item_and_mutate(item, total), # ⚠️ Mutation lost on replay! name=f'save-item- { item["id"]}' ) return { 'total': total} # Inconsistent value! # ✅ CORRECT: Accumulate with return values @durable_execution def handler(event, context: DurableContext): total = 0 for item in items: total = context.step( lambda _: save_item_and_return_total(item, total), name=f'save-item- { item["id"]}' ) return { 'total': total} # Consistent! # ✅ EVEN BETTER: Use map for parallel processing @durable_execution def handler(event, context: DurableContext): def process_item(ctx, item): ctx.step(lambda _: save_item(item)) return item['price'] results = context.map(items, process_item) total = sum(results.get_results()) return { 'total': total} Conception axée sur l'idempuissance Les opérations peuvent être exécutées plusieurs fois en raison de nouvelles tentatives ou de rediffusions. Les opérations non idempotentes entraînent des effets secondaires dupliqués, comme le fait de facturer deux fois les clients ou d'envoyer plusieurs e-mails. Utilisez des jetons d'idempuissance : générez des jetons en quelques étapes et incluez-les dans les appels d'API externes pour éviter les opérations dupliquées. TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Generate idempotency token once const idempotencyToken = await context.step('generate-idempotency-token', async () => { return crypto.randomUUID(); }); // Use token to prevent duplicate charges const charge = await context.step('charge-payment', async () => { return paymentService.charge( { amount: event.amount, cardToken: event.cardToken, idempotencyKey: idempotencyToken }); }); return { statusCode: 200, charge }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext import uuid @durable_execution def handler(event, context: DurableContext): # Generate idempotency token once idempotency_token = context.step( lambda _: str(uuid.uuid4()), name='generate-idempotency-token' ) # Use token to prevent duplicate charges def charge_payment(_): return payment_service.charge( amount=event['amount'], card_token=event['cardToken'], idempotency_key=idempotency_token ) charge = context.step(charge_payment, name='charge-payment') return { 'statusCode': 200, 'charge': charge} Utilisez la at-most-once sémantique : pour les opérations critiques qui ne doivent jamais être dupliquées (transactions financières, déductions d'inventaire), configurez at-most-once le mode d'exécution. TypeScript // Critical operation that must not duplicate await context.step('deduct-inventory', async () => { return inventoryService.deduct(event.productId, event.quantity); }, { executionMode: 'AT_MOST_ONCE_PER_RETRY' }); Python # Critical operation that must not duplicate context.step( lambda _: inventory_service.deduct(event['productId'], event['quantity']), name='deduct-inventory', config=StepConfig(execution_mode='AT_MOST_ONCE_PER_RETRY') ) Identité de la base de données : utilisez check-before-write des modèles, des mises à jour conditionnelles ou des opérations de modification pour éviter les doublons d'enregistrements. Gérez efficacement l'état Chaque point de contrôle enregistre l'état dans un stockage permanent. Les objets d'état volumineux augmentent les coûts, ralentissent le pointage des points de contrôle et ont un impact sur les performances. Stockez uniquement les données essentielles de coordination du flux de travail. Maintenez l'état au minimum : Magasin IDs et références, pas des objets complets Récupérez des données détaillées en quelques étapes, selon les besoins Utilisez Amazon S3 ou DynamoDB pour les données volumineuses, transmettez les références dans l'état Évitez de transmettre de grosses charges utiles entre les étapes TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Store only the order ID, not the full order object const orderId = event.orderId; // Fetch data within each step as needed await context.step('validate-order', async () => { const order = await orderService.getOrder(orderId); return validateOrder(order); }); await context.step('process-payment', async () => { const order = await orderService.getOrder(orderId); return processPayment(order); }); return { statusCode: 200, orderId }; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext @durable_execution def handler(event, context: DurableContext): # Store only the order ID, not the full order object order_id = event['orderId'] # Fetch data within each step as needed context.step( lambda _: validate_order(order_service.get_order(order_id)), name='validate-order' ) context.step( lambda _: process_payment(order_service.get_order(order_id)), name='process-payment' ) return { 'statusCode': 200, 'orderId': order_id} Concevez des étapes efficaces Les étapes sont l'unité de travail fondamentale des fonctions durables. Des étapes bien conçues facilitent la compréhension, le débogage et la maintenance des flux de travail. Principes de conception des étapes : Utilisez des noms descriptifs : les noms tels que validate-order « step1 instead » facilitent la compréhension des journaux et des erreurs Conservez les noms statiques : n'utilisez pas de noms dynamiques avec des horodatages ou des valeurs aléatoires. Les noms des étapes doivent être déterministes pour la rediffusion Équilibrez la granularité : divisez les opérations complexes en étapes ciblées, mais évitez les petites étapes excessives qui augmentent la charge des points de contrôle Opérations liées au groupe - Les opérations qui devraient réussir ou échouer ensemble appartiennent à la même étape Utilisez efficacement les opérations d'attente Les opérations d'attente suspendent l'exécution sans consommer de ressources ni entraîner de coûts. Utilisez-les au lieu de faire fonctionner Lambda. Attentes basées sur le temps : à utiliser context.wait() pour les retards au lieu de setTimeout ou. sleep Rappels externes : à utiliser context.waitForCallback() lorsque vous attendez des systèmes externes. Définissez toujours des délais d'attente pour éviter les temps d'attente indéfinis. Sondage : context.waitForCondition() à utiliser avec un recul exponentiel pour interroger les services externes sans les surcharger. TypeScript // Wait 24 hours without cost await context.wait( { seconds: 86400 }); // Wait for external callback with timeout const result = await context.waitForCallback( 'external-job', async (callbackId) => { await externalService.submitJob( { data: event.data, webhookUrl: `https://api.example.com/callbacks/$ { callbackId}` }); }, { timeout: { seconds: 3600 } } ); Python # Wait 24 hours without cost context.wait(86400) # Wait for external callback with timeout result = context.wait_for_callback( lambda callback_id: external_service.submit_job( data=event['data'], webhook_url=f'https://api.example.com/callbacks/ { callback_id}' ), name='external-job', config=WaitForCallbackConfig(timeout_seconds=3600) ) Considérations supplémentaires Gestion des erreurs : réessayez les échecs transitoires tels que les délais d'expiration du réseau et les limites de débit. Ne réessayez pas en cas d'échec permanent, comme une saisie non valide ou une erreur d'authentification. Configurez des stratégies de nouvelles tentatives avec des taux de tentatives et d'interruption maximaux appropriés. Pour des exemples détaillés, voir Gestion des erreurs et nouvelles tentatives . Performances : minimisez la taille des points de contrôle en stockant des références plutôt que des charges utiles complètes. Utilisez context.parallel() et context.map() pour exécuter simultanément des opérations indépendantes. Opérations liées au batch pour réduire la surcharge des points de contrôle. Gestion des versions : invoquez des fonctions avec des numéros de version ou des alias pour attribuer les exécutions à des versions de code spécifiques. Assurez-vous que les nouvelles versions du code peuvent gérer l'état des anciennes versions. Ne renommez pas les étapes et ne modifiez pas leur comportement de manière à interrompre la rediffusion. Sérialisation : utilisez des types compatibles JSON pour les entrées et les résultats des opérations. Convertissez les dates en chaînes ISO et les objets personnalisés en objets simples avant de les transmettre à des opérations durables. Surveillance : activez la journalisation structurée avec les noms d'exécution IDs et d'étape. Configurez CloudWatch des alarmes pour les taux d'erreur et la durée d'exécution. Utilisez le traçage pour identifier les goulots d'étranglement. Pour obtenir des instructions détaillées, consultez la section Surveillance et débogage . Tests : testez le chemin heureux, la gestion des erreurs et le comportement des rediffusions. Testez des scénarios de temporisation pour les rappels et les temps d'attente. Utilisez des tests locaux pour réduire le temps d'itération. Pour obtenir des instructions détaillées, voir Tester des fonctions durables . Erreurs courantes à éviter : n'imbriquez pas les context.step() appels, utilisez plutôt des contextes enfantins. Enveloppez les opérations non déterministes par étapes. Définissez toujours des délais d'expiration pour les rappels. Équilibrez la granularité des étapes avec la surcharge des points de contrôle. Stockez les références plutôt que les objets volumineux dans l'état. Ressources supplémentaires Documentation du SDK Python - Référence complète des API, modèles de test et exemples avancés TypeScript Documentation du SDK : référence complète des API, modèles de test et exemples avancés JavaScript est désactivé ou n'est pas disponible dans votre navigateur. Pour que vous puissiez utiliser la documentation AWS, Javascript doit être activé. Vous trouverez des instructions sur les pages d'aide de votre navigateur. Conventions de rédaction Surveillance des fonctions durables Instances gérées Lambda Cette page vous a-t-elle été utile ? - Oui Merci de nous avoir fait part de votre satisfaction. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer ce qui vous a plu afin que nous puissions nous améliorer davantage. Cette page vous a-t-elle été utile ? - Non Merci de nous avoir avertis que cette page avait besoin d'être retravaillée. Nous sommes désolés de ne pas avoir répondu à vos attentes. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer comment nous pourrions améliorer cette documentation. | 2026-01-13T09:29:30 |
http://www.christian-thinktank.com/objedex.html | Index of Objections Over-dex of Objections [Minor edits Sept/2023...I hope to keep filling this out over time] Reasons some people give for not approaching Jesus Christ for: -- a vivifying personal relationship; -- spiritual/emotional help and recovery; -- and confidence that their experience of the afterlife will be characterized by peace, warmth, and safety ......................................................................... The God of the Bible is not worthy of my respect: The God who created 'red in tooth and claw' nature is cruel. [ predator.html ] God commanded and supported genocide against the Amorites/Canaanites [ qamorite.html ], and even endorsed the anti-Semitic writings in the New Testament--especially of the apostle John [ ajews.html ], and the apostle Paul in 1st Thess 2. [ moantijew.html ] God is hypocritical in His orders (e.g. child-sacrifice) [ qkilisak.html ], and in His ethics about honesty. [ godlies.html ] The God who created all things must therefore have created evil [ qmakevil.html ], and He actually states that explicitly [ iamwrong1.html ]. This means that He must be evil itself. [ evilgod.html ] God is apparently insensitive to all the suffering in the world [ vincent1.html ], even all the natural evil we experience -- some of which is horrific, like hot viruses. [ natevl.html ] God is either malevolent, impotent, or just hypocritical--He expects us to intervene in crime situations but He doesn't! [ 2stds.html ] God must be cruel or insane to set us up for failure from the beginning. [ gutripper.html ] God forces people to disobey Him, so He can punish them--both His friends, like King David [ hcensus.html and gutripper.html#census ], and His enemies like Pharaoh. [ hharden.html ] God unfairly condemns people who haven't even heard of Him. [ hnohear.html ] And He even unfairly places people in specific cultures which will determine that they have a low chance of becoming a Christian. [ culturegod.html ] God condones slavery [ qnoslave.html ], and devalues women. [ femalex.html ] God must not be all that loving, because He executes justice when He could just as easily forgive sins. [ whyjust.html ] Plus, He punishes people eternally for non-eternal sins. [ way2long.html ] And then His 'solution' to it (punishing an innocent Jesus instead of us guilty parties) is both immoral and illegal! [ inmyplace.html ] God is even called "jealous", "vengeful", and "wrathful" by Himself (and by others) in the bible! [ madgod.html ] His servants (like Elisha) are cruel and easily provoked to violence even against children [ QNU_meanElisha.html ]. His servants do His bidding, even to Saul's butchering innocent Amalekite women and children [ rbutcher1.html ], Moses' butchering of Midianite women and boys [ midian.html ], and -- of course -- the nationwide execution of firstborn offspring at the Exodus. [ killheir.html ] God is obviously a self-centered and insecure glory-hog, since He created an entire universe just to sit around and worship Him. [ Letter_1997_08_30_gloryhog.html ] God knew -- with perfect knowledge -- that all this suffering and hell would befall us, but He was heartless/sadistic enough to go ahead with creation and history ANYWAY. [ gr5part1.html ] And He then offers me the "free choice" of "love me, or be tortured in hell for ever ... [ meorburn.html ] Or so I THOUGHT it was a choice--but instead He predestined me to choose hell ANYWAY� according to St. Paul in Romans 9?! [ stealtime.html#romans9 and sh3morals.html )] And, this predestination was totally arbitrary , as if decided by a random set of dice or a lottery BEFORE I WAS EVEN BORN or CONCEIVED� and with nothing about my character or actions having ANY bearing on it... [ nowhim.html ] Besides, God just created us just to meet His own, personal EGO needs--He obviously is not 'healthy' enough without us! [ needygod.html ] Actually, it might even be that He needs us to feed him in some way(?), since He gets hungry! [ gastricgod.html ] And, if the biblical story is true, and if that 'god' exists, then the Old Testament god YHWH is probably SATAN himself! [ Was_YHWH_Satan.html ] ......................................................................... Actually, the very concepts of "god" and "souls" are useless: Humanity probably invented the concept. [ hinvent.html ] Science has shown us that humans don't have "souls" anyway. [ hmosoul.html ] The concept of God is riddled with incoherence anyway. [ hgodrock.html ] Even if He/she/it/they DID exist, our finite language is inadequate to talk about God. [ finlang.html ] And God (if he/she/it/they did exist) is so far beyond our knowledge, we could never know God in a personal way. [ noknow.html ] ......................................................................... The OT/Tanach that tells us about the God is not trustworthy It makes false claims: it claims to be written by Moses, but it wasn't [ qmoses1.html ], and Daniel 'pretends' that its telling the future! [ qwhendan3x.html ] It is filled with historical errors, like human longevity before the Flood of Noah [ sumerq.html ], or Abraham having camels before they were domesticated. [ qnocamel.html ] Archaeology has disproved the biblical story, especially about Joshua's Conquest narratives. [ noai.html ] It is filled with contradictions, like God's approval-disapproval of Jehu's actions [ qjehu.html ], or Terah being 70 or 130 years old when Abraham was born. [ abebirth.html ] There is no extra-biblical data to support its wild claims--like the parting of the sea by Moses, the stopping of the sun by Joshua, the reversal of the sun's course by Isaiah, the miraculous feeding of the 5,000-plus people by Jesus, or the post-crucifixion resurrections in Jerusalem. [ 5felled.html ]. And the extra-biblical data that does exist shows that it is merely a rip-off of earlier ANE literature! [ gilgymess.html ] It was corrupted in transmission to us. [ qmomoz.html ] And, what is even WORSE, the god "YHWH" in it, claiming to be the source of the OT was actually SATAN, presenting himself as Israel's God YHWH! [ Was_YHWH_satan_in_OT.html ] ......................................................................... I have no affirmative reason to believe such a God exists God should give us concrete proof--but He doesn't [ adam01.html ], and the Christian interpretation of the "evidence" has no compelling support for it. [ sh1college.html ] We don't have any evidence of God's existence. [ tqwhygod.html ] We don�t have any reasons to believe in spirits or a 'supernatural dimension' anyway. [Rewrite planned] Christianity cannot be true, since it needs so much defending? And God doesn't make it very clear or obvious to everyone? [ 2many1.html ] The complexity in the universe doesn't need a 'God' to explain it--complexity arises from simplicity all the time� [ notuphill.html ] The supernatural elements in the gospels are not 'evidence' (LOL), since the ancient world was teeming with fraudulent claims, aimed for the credulous masses. [ mqfx.html ] ......................................................................... Jesus didn't actually exist himself: There are no extra-biblical records of Jesus. [ jesusref.html ] He was probably just an amalgam of other savior myths. [ copycat.html ] He (and the bible itself) was probably concocted for power reasons, to control the populace. [ controlm.html ] ......................................................................... The Jesus of the New Testament is not worthy of my respect (much less, worship or trust): He was a hate-monger [ hhate.html ], and even anti-family. [ hfamval.html ] He was dishonest--telling lies and deceiving people often -- and was even sacrilegious in using the flesh-eating and blood-drinking imagery. [ hnoblood2.html ] He used mean and insulting language to his opponents, his audiences, and even his students [ ralphtrail.html#badlist and ralphtrail.html#badvss ], -- but why even to humble supplicants like the Canaanite woman? [ qcrude.html ] He prayed to the pagan god EL on the Cross (and not YHWH?) [ elwho.html ] He was mistaken about His return [ qaim.html ], and the Church had to re-spin Him into something else! [ spinmequick1.html ] Even His death contradicted the Law of God about human sacrifice. [ sacra.html ] And He even tried to do away with (annul) the eternal, unchangeable Mosaic law! [ finaltorah.html ] ......................................................................... The New Testament that tells us about this Jesus is not trustworthy: The whole story about "Jesus the Messiah" cannot be true, because the Jews were not expecting a Messiah at all. [ messiah.html ] Instead, the early Christians twisted the OT into saying something it didn't, (even the Psalm 22 thing! [ ps22cheat.html ]) and they 'read Jesus back into' the OT. [ baduseot.html ] But even then, Jesus didn't fulfill those messianic prophecies [ fabprof0.html ], he was a failure as a messiah to His people [ qjesus1.html ], and he didn't even fulfill the prophecies he was supposed to (so we would KNOW he was the messiah). [ falsechrist.html ] The NT itself was probably a hoax [ hnoblood2.html ], written by people biased to the point of untruthfulness [ nuhbias.html ], perhaps victims of a group hallucination [ hallucn.html ]. And we know that some of the letters of the NT were frauds--written by someone 'borrowing' the name of a famous person to win their case [ pseudox.html ] ...especially the so-called letters of Peter. [ ynotpeter1.html ] These NT authors somehow felt it was okay to invent places like Nazareth [ NoNazareth.html ], and invent events like the raising of Lazarus from the dead [ qlazirun.html ], inflate numbers like Matthew did [ diplopia.html ], make up speeches/settings for Jesus to make Jesus look like 'Moses on the Mountain' [ qnomount.html ], or plagiarizing ancient Essene prayers [ qdssmnt.html ]. They probably just ripped-off stories from the Hebrew bible and ascribed them to Jesus, [ qotripoff.html ], and even borrowed freely from pagan religions! [ copycat2.html ] With all the problems associated with memory and memory recall [ loftus.html ], it is no wonder that, after the long, slow, hodge-podge collection, by warring factions within the early church, of oral traditions about Jesus [ stilltoc.html ], we find the NT accounts filled with contradictions about major events, including: The Resurrection [ ordorise.html ]; Infancy events [ infancyoff.html ]; and the Ascension. [ qascend.html and q150v500.html ] And not just contradictions on the MAJOR events, but countless other small details as well: Two people or One? [ 2or1.html ]; On the third day or AFTER 3 days? [ q3rdday.html and q3daze.html ]; Take a staff or not? [ nostaff.html ] Even the best historian in the NT (Luke) makes major, glaring historical errors -- like the stories of Theudas [ qtheudy.html ], and of Quirinius' census. [ qr1.html ] So, why should I trust the other writers, like the peasant John [ qjohngrk.html ] who was anti-Semitic [ ajews.html ], or Paul who completely mutates Jesus' religion into something totally different! [ muslix.html ] The evangelists/disciples even invented the miracles stories of Jesus, to "sell Him" to others, didn't they? [ mqx.html ] This whole myth construction was done so rapidly, and gained power so quickly, that those that knew the truth did not have time to speak up in time [ qiwitnes.html and qiwitne2.html ], and the Christians somehow simply outlived those that knew the truth. [ qconspr.html ] Thanks to the old Jesus Seminar and the earliest gospel (the Gospel of Thomas) [ gthomas.html ], we know that the message of Jesus was 'embellished' by the early Christian communities [ stilltoc.html ], and the 'official version' of the NT we have today (and the doctrines of the Church) were not the original ones of the true original Christians--the Nazarenes and Ebionites. [ qnazonly.html ] The early church was so fragmented that they could not tell between 'authentic' books and 'inauthentic' books [ dumbdad2.html ], and the process they used for deciding on what were 'official books' was corrupt and politically motivated. [ canonout.html ] And, by the time we get to Rome making Christianity the "state religion", it totally distorted the NT documents for political purposes [ rome.html ], increasing the number of textual errors (further undermining our confidence in the NT). [ texterrs.html ] And we even have reason to believe that the earliest church suppressed the truth and deceived people for reasons of power. [ qbadmark.html ] ......................................................................... And even if it were all true: How could I decide between all the competing world religions, all claiming to be true? [ decide0.html ] How would I know whether I had the right kind of faith or not? [ qisfaith.html ] How would I know how to deal with "faith vs. knowledge" issues? [ hnoblood1.html ] ...................... [objedex.html] The Christian ThinkTank... [https://www.Christian-thinktank.com] (Reference Abbreviations) | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/ja_jp/lambda/latest/dg/extensions-configuration.html#invocation-extensions-images | Lambda 拡張機能の設定 - AWS Lambda Lambda 拡張機能の設定 - AWS Lambda ドキュメント AWS Lambda デベロッパーガイド 拡張子の設定 (.zip ファイルアーカイブ) コンテナイメージでの拡張機能の使用 次のステップ Lambda 拡張機能の設定 拡張子の設定 (.zip ファイルアーカイブ) 関数に、 Lambda レイヤー として拡張機能を追加できます。レイヤーを使用すれば、組織全体または Lambda デベロッパーのコミュニティ全体で拡張機能を共有できます。1 つ以上の拡張機能をレイヤーに追加できます。1 つの関数に最大 10 個の拡張機能を登録できます。 レイヤーの場合と同じメソッドを使用して、関数に拡張機能を追加します。詳細については、「 レイヤーによる Lambda 依存関係の管理 」を参照してください。 関数に拡張機能を追加する (コンソール) Lambda コンソールの [関数ページ] を開きます。 関数を選択します。 選択されていない場合は、[ Code (コード) ] タブを選択します。 [ レイヤー ] で、[ Edit (編集) ] を選択します。 [ Choose a layer ] の [ Specify an ARN ] を選択します。 [ Specify an ARN ] に、拡張機能レイヤーの Amazon リソースネーム (ARN) を入力します。 [追加] を選択します。 コンテナイメージでの拡張機能の使用 コンテナイメージ に拡張機能を追加できます 。ENTRYPOINT コンテナイメージ設定では、関数のメインプロセスを指定します。Dockerfile で ENTRYPOINT 設定を行うか、関数設定のオーバーライドとして設定します。 コンテナ内で複数のプロセスを実行できます。Lambda は、メインプロセスと任意の追加プロセスのライフサイクルを管理します。Lambda は、 拡張機能 API を使用して、拡張機能のライフサイクルを管理します。 外部拡張機能の追加の例 外部拡張機能は、Lambda 関数とは別のプロセスで実行されます。Lambda は、 /opt/extensions/ ディレクトリで各拡張モジュールのプロセスを開始します。Lambda は、拡張機能 API を使用して、拡張機能のライフサイクルを管理します。関数が実行され完了すると、Lambda はそれぞれの外部拡張機能に Shutdown イベントを送信します。 例 Python ベースイメージに外部拡張機能を追加する FROM public.ecr.aws/lambda/python:3.11 # Copy and install the app COPY /app /app WORKDIR /app RUN pip install -r requirements.txt # Add an extension from the local directory into /opt/extensions ADD my-extension.zip /opt/extensions CMD python ./my-function.py 次のステップ 拡張機能の詳細を参照するには、次のリソースをお勧めします。 基本的な使用例については、AWS Lambda コンピューティングブログの Building Extensions for AWS を参照してください。 AWS Lambda パートナーが提供する拡張機能の詳細については、AWS Lambda コンピューティングブログの AWS 拡張機能の紹介 を参照してください。 利用可能な拡張機能とラッパースクリプトの例については、AWS Lambda サンプル GitHub リポジトリの「 AWS Extensions 」を参照してください。 ブラウザで JavaScript が無効になっているか、使用できません。 AWS ドキュメントを使用するには、JavaScript を有効にする必要があります。手順については、使用するブラウザのヘルプページを参照してください。 ドキュメントの表記規則 Lambda 拡張機能 拡張機能パートナー このページは役に立ちましたか? - はい ページが役に立ったことをお知らせいただき、ありがとうございます。 お時間がある場合は、何が良かったかお知らせください。今後の参考にさせていただきます。 このページは役に立ちましたか? - いいえ このページは修正が必要なことをお知らせいただき、ありがとうございます。ご期待に沿うことができず申し訳ありません。 お時間がある場合は、ドキュメントを改善する方法についてお知らせください。 | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/zh_tw/lambda/latest/dg/durable-execution-sdk.html | 耐用的執行 SDK - AWS Lambda 耐用的執行 SDK - AWS Lambda 文件 AWS Lambda 開發人員指南 DurableContext 開發套件的功能 檢查點的運作方式 重播行為 可用的耐用操作 如何計量耐久性操作 本文為英文版的機器翻譯版本，如內容有任何歧義或不一致之處，概以英文版為準。 耐用的執行 SDK 耐用執行 SDK 是建置耐用函數的基礎。它提供檢查點進度、處理重試和管理執行流程所需的基本概念。SDK 可抽象化檢查點管理和重播的複雜性，讓您撰寫可自動容錯的循序程式碼。 開發套件適用於 JavaScript、TypeScript 和 Python。如需完整的 API 文件和範例，請參閱 GitHub 上的 JavaScript/TypeScript SDK 和 Python SDK 。 DurableContext 開發套件為您的函數提供公開所有耐久操作的 DurableContext 物件。此內容會取代標準 Lambda 內容，並提供建立檢查點、管理執行流程以及與外部系統協調的方法。 若要使用 SDK，請使用耐用的執行包裝函式來包裝 Lambda 處理常式： TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Your function receives DurableContext instead of Lambda context // Use context.step(), context.wait(), etc. return result; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext @durable_execution def handler(event: dict, context: DurableContext): # Your function receives DurableContext # Use context.step(), context.wait(), etc. return result 包裝函式會攔截函數叫用、載入任何現有的檢查點日誌，並提供 DurableContext 管理重播和檢查點的 。 開發套件的功能 開發套件會處理三個關鍵責任，以實現持久的執行： 檢查點管理： 軟體開發套件會在函數執行耐久操作時自動建立檢查點。每個檢查點都會記錄操作類型、輸入和結果。當您的函數完成步驟時，SDK 會保留檢查點再繼續。這可確保您的函數可以在中斷時從任何已完成的操作恢復。 重播協調： 當函數在暫停或中斷後恢復時，軟體開發套件會執行重播。它會從頭開始執行程式碼，但會略過已完成的操作，使用儲存的檢查點結果，而不是重新執行它們。SDK 可確保重播是確定性的，因為提供相同的輸入和檢查點日誌，您的函數會產生相同的結果。 狀態隔離： SDK 會與您的業務邏輯分開維護執行狀態。每個耐久執行都有自己的檢查點日誌，其他執行無法存取。開發套件會加密靜態檢查點資料，並確保狀態在重播之間保持一致。 檢查點的運作方式 當您呼叫持久性操作時，軟體開發套件會遵循以下順序： 檢查現有檢查點： SDK 會檢查此操作是否已在先前的調用中完成。如果檢查點存在，軟體開發套件會傳回儲存的結果，而不會重新執行操作。 執行操作： 如果沒有檢查點，則 SDK 會執行您的操作程式碼。對於步驟，這表示呼叫您的 函數。對於等待，這表示排程恢復。 建立檢查點： 操作完成後，軟體開發套件會序列化結果並建立檢查點。檢查點包含操作類型、名稱、輸入、結果和時間戳記。 持久性檢查點： SDK 會呼叫 Lambda 檢查點 API 來持久性檢查點。這可確保檢查點在繼續執行之前是耐用的。 傳回結果： 軟體開發套件會將操作結果傳回至您的程式碼，繼續執行下一個操作。 此序列可確保一旦操作完成，就會安全地存放其結果。如果您的函數在任何時間點中斷，開發套件可以重新執行到最後完成的檢查點。 重播行為 當您的函數在暫停或中斷後繼續時，軟體開發套件會執行重播： 載入檢查點日誌： 開發套件會從 Lambda 擷取此執行的檢查點日誌。 從頭開始執行： 軟體開發套件會從頭調用您的處理常式函數，而不是從暫停的位置調用。 略過已完成的持久性操作： 當程式碼呼叫持久性操作時，軟體開發套件會根據檢查點日誌檢查每個操作。對於已完成的持久性操作，軟體開發套件會傳回預存結果，而不執行操作程式碼。 注意 如果子內容的結果大於檢查點大小上限 (256 KB)，則會在重播期間再次執行內容的程式碼。這可讓您建構在內容中執行之耐久操作的大型結果，這些結果將從檢查點日誌中查詢。因此，只能在內容本身中執行確定性程式碼。使用具有大型結果的子內容時，最佳實務是在步驟內執行長時間執行或非確定性工作，並且只執行將結果合併到內容本身的短期執行任務。 在中斷點繼續： 當開發套件在沒有檢查點的情況下達到 操作時，它會正常執行，並在耐久操作完成時建立新的檢查點。 此重播機制需要您的程式碼具有決定性。假設輸入和檢查點日誌相同，您的函數必須進行相同序列的耐久操作呼叫。SDK 透過驗證操作名稱和類型在重播期間符合檢查點日誌來強制執行此操作。 可用的耐用操作 DurableContext 提供不同協調模式的操作。每個耐用的操作都會自動建立檢查點，確保您的函數可以隨時恢復。 步驟 使用自動檢查點和重試來執行商業邏輯。對呼叫外部服務、執行計算或執行任何應檢查點的邏輯的操作使用步驟。開發套件會在步驟前後建立檢查點，存放結果以進行重播。 TypeScript const result = await context.step('process-payment', async () => { return await paymentService.charge(amount); }); Python result = context.step( lambda _: payment_service.charge(amount), name='process-payment' ) 步驟支援可設定的重試策略、執行語意 (at-most-once或at-least-once和自訂序列化。 等待 在指定的持續時間內暫停執行，而不耗用運算資源。SDK 會建立檢查點、終止函數叫用，以及排程恢復。當等待完成時，Lambda 會再次叫用您的函數，而 SDK 會在繼續之前重播至等待點。 TypeScript // Wait 1 hour without charges await context.wait( { seconds: 3600 }); Python # Wait 1 hour without charges context.wait(3600) 回呼 回呼可讓函數暫停並等待外部系統提供輸入。當您建立回呼時，開發套件會產生唯一的回呼 ID 並建立檢查點。然後，您的函數會暫停 （終止調用），而不會產生運算費用。外部系統使用 SendDurableExecutionCallbackSuccess 或 SendDurableExecutionCallbackFailure Lambda APIs提交回呼結果。提交回呼時，Lambda 會再次叫用您的函數，開發套件會重播至回呼點，而函數會繼續回呼結果。 開發套件提供兩種使用回呼的方法： createCallback： 建立回呼，並同時傳回 promise 和回呼 ID。您可以將回呼 ID 傳送至外部系統，該系統會使用 Lambda API 提交結果。 TypeScript const [promise, callbackId] = await context.createCallback('approval', { timeout: { hours: 24 } }); await sendApprovalRequest(callbackId, requestData); const approval = await promise; Python callback = context.create_callback( name='approval', config=CallbackConfig(timeout_seconds=86400) ) context.step( lambda _: send_approval_request(callback.callback_id), name='send_request' ) approval = callback.result() waitForCallback： 將回呼建立和提交結合在一個操作中，簡化回呼處理。開發套件會建立回呼、使用回呼 ID 執行您的提交者函數，並等待結果。 TypeScript const result = await context.waitForCallback( 'external-api', async (callbackId, ctx) => { await submitToExternalAPI(callbackId, requestData); }, { timeout: { minutes: 30 } } ); Python result = context.wait_for_callback( lambda callback_id: submit_to_external_api(callback_id, request_data), name='external-api', config=WaitForCallbackConfig(timeout_seconds=1800) ) 設定逾時以防止函數無限期等待。如果回呼逾時，開發套件會擲回 CallbackError ，而您的函數可以處理逾時案例。針對長時間執行的回呼使用活動訊號逾時，以偵測外部系統何時停止回應。 將回呼用於human-in-the-loop工作流程、外部系統整合、Webhook 回應或任何執行必須針對外部輸入暫停的情況。 平行執行 與選用並行控制同時執行多個操作。SDK 會管理平行執行、為每個操作建立檢查點，以及根據您的完成政策處理失敗。 TypeScript const results = await context.parallel([ async (ctx) => ctx.step('task1', async () => processTask1()), async (ctx) => ctx.step('task2', async () => processTask2()), async (ctx) => ctx.step('task3', async () => processTask3()) ]); Python results = context.parallel( lambda ctx: ctx.step(lambda _: process_task1(), name='task1'), lambda ctx: ctx.step(lambda _: process_task2(), name='task2'), lambda ctx: ctx.step(lambda _: process_task3(), name='task3') ) 使用 parallel 可同時執行獨立操作。 Map 使用選用並行控制，同時對陣列中的每個項目執行 操作。SDK 會管理並行執行、為每個操作建立檢查點，以及根據您的完成政策處理失敗。 TypeScript const results = await context.map(itemArray, async (ctx, item, index) => ctx.step('task', async () => processItem(item, index)) ); Python results = context.map( item_array, lambda ctx, item, index: ctx.step( lambda _: process_item(item, index), name='task' ) ) 使用 map 處理具有並行控制的陣列。 子內容 建立用於分組操作的隔離執行內容。子內容有自己的檢查點日誌，可包含多個步驟、等待和其他操作。SDK 會將整個子內容視為單一單位，以供重試和復原。 使用子內容來組織複雜的工作流程、實作子工作流程，或隔離應同時重試的操作。 TypeScript const result = await context.runInChildContext( 'batch-processing', async (childCtx) => { return await processBatch(childCtx, items); } ); Python result = context.run_in_child_context( lambda child_ctx: process_batch(child_ctx, items), name='batch-processing' ) 重播機制要求以決定性順序進行持久性操作。使用多個子內容，您可以同時執行多個工作串流，而且決定性會分別套用在每個內容中。這可讓您建置高效能函數，以有效率地利用多個 CPU 核心。 例如，假設我們啟動兩個子內容 A 和 B。在初始調用時，內容中的步驟會依此順序執行，而 'A' 步驟會與 'B' 步驟同時執行：A1, B1, B2, A2, A3。重新執行時，從檢查點日誌擷取結果時，時間會快得多，而步驟的發生順序也不同：B1, A1, A2, B2, A3。由於「A」步驟的順序正確 (A1、A2, A3)，且「B」步驟的順序正確 (B1、B2)，因此正確滿足確定性的需求。 條件式等待 輪詢在嘗試之間具有自動檢查點的條件。SDK 會執行您的檢查函數、建立具有結果的檢查點、根據您的策略等待，並重複直到滿足條件為止。 TypeScript const result = await context.waitForCondition( async (state, ctx) => { const status = await checkJobStatus(state.jobId); return { ...state, status }; }, { initialState: { jobId: 'job-123', status: 'pending' }, waitStrategy: (state) => state.status === 'completed' ? { shouldContinue: false } : { shouldContinue: true, delay: { seconds: 30 } } } ); Python result = context.wait_for_condition( lambda state, ctx: check_job_status(state['jobId']), config=WaitForConditionConfig( initial_state= { 'jobId': 'job-123', 'status': 'pending'}, wait_strategy=lambda state, attempt: { 'should_continue': False} if state['status'] == 'completed' else { 'should_continue': True, 'delay': 30} ) ) 使用 waitForCondition 輪詢外部系統、等待資源就緒，或使用退避實作重試。 函數調用 叫用另一個 Lambda 函數並等待其結果。SDK 會建立檢查點、叫用目標函數，並在叫用完成時繼續您的函數。這可啟用函數合成和工作流程分解。 TypeScript const result = await context.invoke( 'invoke-processor', 'arn:aws:lambda:us-east-1:123456789012:function:processor', { data: inputData } ); Python result = context.invoke( 'arn:aws:lambda:us-east-1:123456789012:function:processor', { 'data': input_data}, name='invoke-processor' ) 如何計量耐久性操作 您透過 呼叫的每個耐用操作都會 DurableContext 建立檢查點，以追蹤執行進度並存放狀態資料。這些操作會根據其用量產生費用，而檢查點可能包含對您的資料寫入和保留成本有所貢獻的資料。儲存的資料包括調用事件資料、步驟傳回的承載，以及完成回呼時傳遞的資料。了解耐用操作的計量方式，可協助您預估執行成本並最佳化工作流程。如需定價的詳細資訊，請參閱 Lambda 定價頁面 。 承載大小是指持久性操作持續的序列化資料大小。資料是以位元組為單位測量，大小可能會因 操作使用的序列化程式而有所不同。操作的承載可能是成功完成的結果本身，如果操作失敗，可能是序列化錯誤物件。 基本操作 基本操作是耐用函數的基本建置區塊： 作業 檢查點計時 操作數量 資料持續存在 執行 已開始 1 輸入承載大小 執行 已完成 Succeeded/Failed/Stopped) 0 輸出承載大小 Step (步驟) Retry/Succeeded/Failed 1 + N 次重試 每次嘗試傳回的承載大小 等候 已開始 1 N/A WaitForCondition 每次輪詢嘗試 1 + N 輪詢 每次輪詢嘗試傳回的承載大小 調用層級重試 已開始 1 錯誤物件的承載 回呼操作 回呼操作可讓您的函數暫停並等待外部系統提供輸入。這些操作會在建立回呼和完成時建立檢查點： 作業 檢查點計時 操作數量 資料持續存在 CreateCallback 已開始 1 N/A 透過 API 呼叫完成回呼 已完成 0 回呼承載 WaitForCallback 已開始 3 + N 次重試 （內容 + 回呼 + 步驟） 提交者步驟嘗試傳回的承載，加上兩個回呼承載副本 複合操作 複合操作結合多個耐久操作，以處理複雜的協調模式，例如平行執行、陣列處理和巢狀內容： 作業 檢查點計時 操作數量 資料持續存在 平行 已開始 1 + N 個分支 (1 個父內容 + N 個子內容） 從每個分支傳回的承載大小最多兩個複本，以及每個分支的狀態 Map 已開始 1 + N 個分支 (1 個父內容 + N 個子內容） 每次反覆運算傳回的承載大小最多兩個副本，加上每次反覆運算的狀態 Promise 協助程式 已完成 1 從 promise 傳回的承載大小 RunInChildContext 成功/失敗 1 從子內容傳回的承載大小 對於內容，例如來自 runInChildContext 或由複合操作內部使用，小於 256 KB 的結果會直接檢查點。不會儲存較大的結果，而是透過重新處理內容的操作，在重播期間重建結果。 您的瀏覽器已停用或無法使用 Javascript。 您必須啟用 Javascript，才能使用 AWS 文件。請參閱您的瀏覽器說明頁以取得說明。 文件慣用形式 安全與許可 支援的執行時期 此頁面是否有幫助？ - 是 感謝您，讓我們知道我們做得很好！ 若您有空，歡迎您告知我們值得讚許的地方，這樣才能保持良好服務。 此頁面是否有幫助？ - 否 感謝讓我們知道此頁面仍須改善。很抱歉，讓您失望。 若您有空，歡迎您提供改善文件的方式。 | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/id_id/lambda/latest/dg/durable-basic-concepts.html | Konsep Basic - AWS Lambda Konsep Basic - AWS Lambda Dokumentasi AWS Lambda Panduan Developerr Eksekusi tahan lama DurableContext Langkah-langkah Tunggu Negara Memanggil fungsi lainnya Konfigurasi fungsi yang tahan lama Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Konsep Basic Lambda menyediakan eksekusi yang tahan lama SDKs untuk JavaScript, TypeScript, dan Python. Ini SDKs adalah fondasi untuk membangun fungsi yang tahan lama, menyediakan primitif yang Anda butuhkan untuk memeriksa kemajuan, menangani percobaan ulang, dan mengelola alur eksekusi. Untuk dokumentasi dan contoh SDK lengkap, lihat SDK JavaScript/TypeScript SDK dan Python aktif. GitHub Eksekusi tahan lama Eksekusi yang tahan lama mewakili siklus hidup lengkap fungsi tahan lama Lambda, menggunakan mekanisme pos pemeriksaan dan pemutaran ulang untuk melacak kemajuan logika bisnis, menangguhkan eksekusi, dan memulihkan dari kegagalan. Ketika fungsi dilanjutkan setelah penangguhan atau interupsi, pos pemeriksaan yang telah selesai sebelumnya diputar ulang dan fungsi melanjutkan eksekusi. Siklus hidup dapat mencakup beberapa pemanggilan fungsi Lambda untuk menyelesaikan eksekusi, terutama setelah penangguhan atau pemulihan kegagalan. Pendekatan ini memungkinkan fungsi Anda berjalan untuk waktu yang lama (hingga satu tahun) sambil mempertahankan kemajuan yang dapat diandalkan meskipun ada gangguan. Cara kerja replay Lambda menyimpan log berjalan dari semua operasi tahan lama (langkah, menunggu, dan operasi lainnya) saat fungsi Anda dijalankan. Ketika fungsi Anda perlu menjeda atau mengalami gangguan, Lambda menyimpan log pos pemeriksaan ini dan menghentikan eksekusi. Ketika tiba waktunya untuk melanjutkan, Lambda memanggil fungsi Anda lagi dari awal dan memutar ulang log pos pemeriksaan, menggantikan nilai yang disimpan untuk operasi yang telah selesai. Ini berarti kode Anda berjalan lagi, tetapi langkah yang telah diselesaikan sebelumnya tidak dijalankan kembali. Hasil tersimpan mereka digunakan sebagai gantinya. Mekanisme replay ini sangat penting untuk memahami fungsi yang tahan lama. Kode Anda harus deterministik selama pemutaran ulang, artinya menghasilkan hasil yang sama dengan input yang sama. Hindari operasi dengan efek samping (seperti menghasilkan angka acak atau mendapatkan waktu saat ini) di luar langkah, karena ini dapat menghasilkan nilai yang berbeda selama pemutaran ulang dan menyebabkan perilaku non-deterministik. DurableContext DurableContext adalah objek konteks yang diterima fungsi tahan lama Anda. Ini menyediakan metode untuk operasi tahan lama seperti langkah-langkah dan menunggu yang membuat pos pemeriksaan dan mengelola alur eksekusi. Fungsi tahan lama Anda menerima DurableContext bukan konteks Lambda default: TypeScript import { DurableContext, withDurableExecution, } from "@aws/durable-execution-sdk-js"; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { const result = await context.step(async () => { return "step completed"; }); return result; }, ); Python from aws_durable_execution_sdk_python import ( DurableContext, durable_execution, durable_step, ) @durable_step def my_step(step_context, data): # Your business logic return result @durable_execution def handler(event, context: DurableContext): result = context.step(my_step(event["data"])) return result Python SDK untuk fungsi tahan lama menggunakan metode sinkron dan tidak mendukung. await TypeScript SDK menggunakan async/await . Langkah-langkah Langkah-langkah menjalankan logika bisnis dengan percobaan ulang bawaan dan pos pemeriksaan otomatis. Setiap langkah menyimpan hasilnya, memastikan fungsi Anda dapat dilanjutkan dari langkah yang diselesaikan setelah interupsi. TypeScript // Each step is automatically checkpointed const order = await context.step(async () => processOrder(event)); const payment = await context.step(async () => processPayment(order)); const result = await context.step(async () => completeOrder(payment)); Python # Each step is automatically checkpointed order = context.step(lambda: process_order(event)) payment = context.step(lambda: process_payment(order)) result = context.step(lambda: complete_order(payment)) Tunggu Negara Status tunggu adalah jeda yang direncanakan di mana fungsi Anda berhenti berjalan (dan berhenti mengisi daya) hingga waktunya untuk melanjutkan. Gunakan mereka untuk menunggu periode waktu, panggilan balik eksternal, atau kondisi tertentu. TypeScript // Wait for 1 hour without consuming resources await context.wait( { seconds:3600 }); // Wait for external callback const approval = await context.waitForCallback( async (callbackId) => sendApprovalRequest(callbackId) ); Python # Wait for 1 hour without consuming resources context.wait(3600) # Wait for external callback approval = context.wait_for_callback( lambda callback_id: send_approval_request(callback_id) ) Saat fungsi Anda mengalami penantian atau perlu dijeda, Lambda menyimpan log pos pemeriksaan dan menghentikan eksekusi. Ketika tiba waktunya untuk melanjutkan, Lambda memanggil fungsi Anda lagi dan memutar ulang log pos pemeriksaan, menggantikan nilai yang disimpan untuk operasi yang telah selesai. Untuk alur kerja yang lebih kompleks, fungsi Lambda yang tahan lama juga dilengkapi dengan operasi lanjutan parallel() seperti untuk eksekusi bersamaan, untuk memproses array map() , untuk operasi bersarang runInChildContext() , dan untuk polling. waitForCondition() Lihat Contoh untuk contoh terperinci dan panduan tentang kapan harus menggunakan setiap operasi. Memanggil fungsi lainnya Invoke memungkinkan fungsi yang tahan lama untuk memanggil fungsi Lambda lainnya dan menunggu hasilnya. Fungsi pemanggilan ditangguhkan saat fungsi yang dipanggil dijalankan, menciptakan pos pemeriksaan yang mempertahankan hasilnya. Hal ini memungkinkan Anda untuk membangun alur kerja modular di mana fungsi khusus menangani tugas-tugas tertentu. Gunakan context.invoke() untuk memanggil fungsi lain dari dalam fungsi tahan lama Anda. Pemanggilan diperiksa, jadi jika fungsi Anda terputus setelah fungsi yang dipanggil selesai, ia dilanjutkan dengan hasil yang disimpan tanpa memanggil kembali fungsi tersebut. TypeScript // Invoke another function and wait for result const customerData = await context.invoke( 'validate-customer', 'arn:aws:lambda:us-east-1:123456789012:function:customer-service:1', { customerId: event.customerId } ); // Use the result in subsequent steps const order = await context.step(async () => { return processOrder(customerData); }); Python # Invoke another function and wait for result customer_data = context.invoke( 'arn:aws:lambda:us-east-1:123456789012:function:customer-service:1', { 'customerId': event['customerId']}, name='validate-customer' ) # Use the result in subsequent steps order = context.step( lambda: process_order(customer_data), name='process-order' ) Fungsi yang dipanggil dapat berupa fungsi Lambda yang tahan lama atau standar. Jika Anda menjalankan fungsi yang tahan lama, fungsi pemanggilan menunggu eksekusi yang tahan lama selesai. Pola ini umum dalam arsitektur layanan mikro di mana setiap fungsi menangani domain tertentu, memungkinkan Anda menyusun alur kerja yang kompleks dari fungsi khusus yang dapat digunakan kembali. catatan Pemanggilan lintas akun tidak didukung. Fungsi yang dipanggil harus berada di AWS akun yang sama dengan fungsi pemanggilan. Konfigurasi fungsi yang tahan lama Fungsi tahan lama memiliki pengaturan konfigurasi khusus yang mengontrol perilaku eksekusi dan retensi data. Pengaturan ini terpisah dari konfigurasi fungsi Lambda standar dan berlaku untuk seluruh siklus hidup eksekusi yang tahan lama. DurableConfig Objek mendefinisikan konfigurasi untuk fungsi tahan lama: { "ExecutionTimeout": Integer, "RetentionPeriodInDays": Integer } Batas waktu eksekusi Batas waktu eksekusi mengontrol berapa lama eksekusi yang tahan lama dapat berjalan dari awal hingga selesai. Ini berbeda dengan batas waktu fungsi Lambda, yang mengontrol berapa lama pemanggilan fungsi tunggal dapat berjalan. Eksekusi yang tahan lama dapat mencakup beberapa pemanggilan fungsi Lambda saat berlangsung melalui pos pemeriksaan, menunggu, dan memutar ulang. Batas waktu eksekusi berlaku untuk total waktu yang telah berlalu dari eksekusi tahan lama, bukan untuk pemanggilan fungsi individual. Memahami perbedaannya Batas waktu fungsi Lambda (maksimum 15 menit) membatasi setiap pemanggilan individu dari fungsi Anda. Batas waktu eksekusi yang tahan lama (maksimum 1 tahun) membatasi total waktu dari saat eksekusi dimulai hingga selesai, gagal, atau habis waktu. Selama periode ini, fungsi Anda mungkin dipanggil beberapa kali saat memproses langkah, menunggu, dan pulih dari kegagalan. Misalnya, jika Anda menetapkan batas waktu eksekusi tahan lama 24 jam dan batas waktu fungsi Lambda 5 menit: Setiap pemanggilan fungsi harus selesai dalam waktu 5 menit Seluruh eksekusi yang tahan lama dapat berjalan hingga 24 jam Fungsi Anda dapat dipanggil berkali-kali selama 24 jam tersebut Operasi tunggu tidak dihitung terhadap batas waktu fungsi Lambda tetapi dihitung terhadap batas waktu eksekusi Anda dapat mengonfigurasi batas waktu eksekusi saat membuat fungsi tahan lama menggunakan konsol Lambda AWS CLI,, atau. AWS SAM Di konsol Lambda, pilih fungsi Anda, lalu Konfigurasi, Eksekusi tahan lama. Atur nilai batas waktu eksekusi dalam hitungan detik (default: 86400 detik/ 24 jam, minimum: 60 detik, maksimum: 31536000 detik/ 1 tahun). catatan Batas waktu eksekusi dan batas waktu fungsi Lambda adalah pengaturan yang berbeda. Batas waktu fungsi Lambda mengontrol berapa lama setiap pemanggilan individu dapat berjalan (maksimum 15 menit). Batas waktu eksekusi mengontrol total waktu yang telah berlalu untuk seluruh eksekusi tahan lama (maksimum 1 tahun). Periode retensi Periode retensi mengontrol berapa lama Lambda mempertahankan riwayat eksekusi dan data pos pemeriksaan setelah eksekusi yang tahan lama selesai. Data ini mencakup hasil langkah, status eksekusi, dan log pos pemeriksaan lengkap. Setelah periode retensi berakhir, Lambda menghapus riwayat eksekusi dan data pos pemeriksaan. Anda tidak dapat lagi mengambil detail eksekusi atau memutar ulang eksekusi. Periode retensi dimulai ketika eksekusi mencapai status terminal (BERHASIL, GAGAL, BERHENTI, atau TIMED_OUT). Anda dapat mengonfigurasi periode retensi saat membuat fungsi tahan lama menggunakan konsol Lambda, AWS CLI, atau. AWS SAM Di konsol Lambda, pilih fungsi Anda, lalu Konfigurasi, Eksekusi tahan lama. Tetapkan nilai periode Retensi dalam beberapa hari (default: 14 hari, minimum: 1 hari, maksimum: 90 hari). Pilih periode retensi berdasarkan persyaratan kepatuhan Anda, kebutuhan debugging, dan pertimbangan biaya. Periode retensi yang lebih lama memberikan lebih banyak waktu untuk debugging dan audit tetapi meningkatkan biaya penyimpanan. Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Lambda fungsi tahan lama Menciptakan fungsi yang tahan lama Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/lambda/latest/dg/durable-execution-sdk.html | Durable execution SDK - AWS Lambda Durable execution SDK - AWS Lambda Documentation AWS Lambda Developer Guide DurableContext What the SDK does How checkpointing works Replay behavior Available durable operations How durable operations are metered Durable execution SDK The durable execution SDK is the foundation for building durable functions. It provides the primitives you need to checkpoint progress, handle retries, and manage execution flow. The SDK abstracts the complexity of checkpoint management and replay, letting you write sequential code that automatically becomes fault-tolerant. The SDK is available for JavaScript, TypeScript, and Python. For complete API documentation and examples, see the JavaScript/TypeScript SDK and Python SDK on GitHub. DurableContext The SDK provides your function with a DurableContext object that exposes all durable operations. This context replaces the standard Lambda context and provides methods for creating checkpoints, managing execution flow, and coordinating with external systems. To use the SDK, wrap your Lambda handler with the durable execution wrapper: TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Your function receives DurableContext instead of Lambda context // Use context.step(), context.wait(), etc. return result; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext @durable_execution def handler(event: dict, context: DurableContext): # Your function receives DurableContext # Use context.step(), context.wait(), etc. return result The wrapper intercepts your function invocation, loads any existing checkpoint log, and provides the DurableContext that manages replay and checkpointing. What the SDK does The SDK handles three critical responsibilities that enable durable execution: Checkpoint management: The SDK automatically creates checkpoints as your function executes durable operations. Each checkpoint records the operation type, inputs, and results. When your function completes a step, the SDK persists the checkpoint before continuing. This ensures your function can resume from any completed operation if interrupted. Replay coordination: When your function resumes after a pause or interruption, the SDK performs replay. It runs your code from the beginning but skips completed operations, using stored checkpoint results instead of re-executing them. The SDK ensures replay is deterministic—given the same inputs and checkpoint log, your function produces the same results. State isolation: The SDK maintains execution state separately from your business logic. Each durable execution has its own checkpoint log that other executions cannot access. The SDK encrypts checkpoint data at rest and ensures state remains consistent across replays. How checkpointing works When you call a durable operation, the SDK follows this sequence: Check for existing checkpoint: The SDK checks if this operation already completed in a previous invocation. If a checkpoint exists, the SDK returns the stored result without re-executing the operation. Execute the operation: If no checkpoint exists, the SDK executes your operation code. For steps, this means calling your function. For waits, this means scheduling resumption. Create checkpoint: After the operation completes, the SDK serializes the result and creates a checkpoint. The checkpoint includes the operation type, name, inputs, result, and timestamp. Persist checkpoint: The SDK calls the Lambda checkpoint API to persist the checkpoint. This ensures the checkpoint is durable before continuing execution. Return result: The SDK returns the operation result to your code, which continues to the next operation. This sequence ensures that once an operation completes, its result is safely stored. If your function is interrupted at any point, the SDK can replay up to the last completed checkpoint. Replay behavior When your function resumes after a pause or interruption, the SDK performs replay: Load checkpoint log: The SDK retrieves the checkpoint log for this execution from Lambda. Run from beginning: The SDK invokes your handler function from the start, not from where it paused. Skip completed durable operations: As your code calls durable operations, the SDK checks each against the checkpoint log. For completed durable operations, the SDK returns the stored result without executing the operation code. Note If a child context's result was larger than the maximum checkpoint size (256 KB), the context's code is executed again during replay. This allows you to construct large results from the durable operations that ran inside the context, which will be looked up from the checkpoint log. Therefore it is imperative to only run deterministic code in the context itself. When using child contexts with large results, it is a best practice to perform long-running or non-deterministic work inside of steps and only perform short-running tasks which combine the results in the context itself. Resume at interruption point: When the SDK reaches an operation without a checkpoint, it executes normally and creates new checkpoints as durable operations complete. This replay mechanism requires your code to be deterministic. Given the same inputs and checkpoint log, your function must make the same sequence of durable operation calls. The SDK enforces this by validating that operation names and types match the checkpoint log during replay. Available durable operations The DurableContext provides operations for different coordination patterns. Each durable operation creates checkpoints automatically, ensuring your function can resume from any point. Steps Executes business logic with automatic checkpointing and retry. Use steps for operations that call external services, perform calculations, or execute any logic that should be checkpointed. The SDK creates a checkpoint before and after the step, storing the result for replay. TypeScript const result = await context.step('process-payment', async () => { return await paymentService.charge(amount); }); Python result = context.step( lambda _: payment_service.charge(amount), name='process-payment' ) Steps support configurable retry strategies, execution semantics (at-most-once or at-least-once), and custom serialization. Waits Pauses execution for a specified duration without consuming compute resources. The SDK creates a checkpoint, terminates the function invocation, and schedules resumption. When the wait completes, Lambda invokes your function again and the SDK replays to the wait point before continuing. TypeScript // Wait 1 hour without charges await context.wait( { seconds: 3600 }); Python # Wait 1 hour without charges context.wait(3600) Callbacks Callbacks enable your function to pause and wait for external systems to provide input. When you create a callback, the SDK generates a unique callback ID and creates a checkpoint. Your function then suspends (terminates the invocation) without incurring compute charges. External systems submit callback results using the SendDurableExecutionCallbackSuccess or SendDurableExecutionCallbackFailure Lambda APIs. When a callback is submitted, Lambda invokes your function again, the SDK replays to the callback point, and your function continues with the callback result. The SDK provides two methods for working with callbacks: createCallback: Creates a callback and returns both a promise and a callback ID. You send the callback ID to an external system, which submits the result using the Lambda API. TypeScript const [promise, callbackId] = await context.createCallback('approval', { timeout: { hours: 24 } }); await sendApprovalRequest(callbackId, requestData); const approval = await promise; Python callback = context.create_callback( name='approval', config=CallbackConfig(timeout_seconds=86400) ) context.step( lambda _: send_approval_request(callback.callback_id), name='send_request' ) approval = callback.result() waitForCallback: Simplifies callback handling by combining callback creation and submission in one operation. The SDK creates the callback, executes your submitter function with the callback ID, and waits for the result. TypeScript const result = await context.waitForCallback( 'external-api', async (callbackId, ctx) => { await submitToExternalAPI(callbackId, requestData); }, { timeout: { minutes: 30 } } ); Python result = context.wait_for_callback( lambda callback_id: submit_to_external_api(callback_id, request_data), name='external-api', config=WaitForCallbackConfig(timeout_seconds=1800) ) Configure timeouts to prevent functions from waiting indefinitely. If a callback times out, the SDK throws a CallbackError and your function can handle the timeout case. Use heartbeat timeouts for long-running callbacks to detect when external systems stop responding. Use callbacks for human-in-the-loop workflows, external system integration, webhook responses, or any scenario where execution must pause for external input. Parallel execution Executes multiple operations concurrently with optional concurrency control. The SDK manages parallel execution, creates checkpoints for each operation, and handles failures according to your completion policy. TypeScript const results = await context.parallel([ async (ctx) => ctx.step('task1', async () => processTask1()), async (ctx) => ctx.step('task2', async () => processTask2()), async (ctx) => ctx.step('task3', async () => processTask3()) ]); Python results = context.parallel( lambda ctx: ctx.step(lambda _: process_task1(), name='task1'), lambda ctx: ctx.step(lambda _: process_task2(), name='task2'), lambda ctx: ctx.step(lambda _: process_task3(), name='task3') ) Use parallel to execute independent operations concurrently. Map Concurrently execute an operation on each item in an array with optional concurrency control. The SDK manages concurrent execution, creates checkpoints for each operation, and handles failures according to your completion policy. TypeScript const results = await context.map(itemArray, async (ctx, item, index) => ctx.step('task', async () => processItem(item, index)) ); Python results = context.map( item_array, lambda ctx, item, index: ctx.step( lambda _: process_item(item, index), name='task' ) ) Use map to process arrays with concurrency control. Child contexts Creates an isolated execution context for grouping operations. Child contexts have their own checkpoint log and can contain multiple steps, waits, and other operations. The SDK treats the entire child context as a single unit for retry and recovery. Use child contexts to organize complex workflows, implement sub-workflows, or isolate operations that should retry together. TypeScript const result = await context.runInChildContext( 'batch-processing', async (childCtx) => { return await processBatch(childCtx, items); } ); Python result = context.run_in_child_context( lambda child_ctx: process_batch(child_ctx, items), name='batch-processing' ) The replay mechanism demands that durable operations happen in a deterministic order. Using multiple child contexts you can have multiple streams of work execute concurrently, and the determinism applies separately within each context. This allows you to build high-performance functions which efficiently utilize multiple CPU cores. For example, imagine we start two child contexts, A and B. On the initial invocation, the steps within the contexts were run in this order, with the 'A' steps running concurrently with the 'B' steps: A1, B1, B2, A2, A3. Upon replay, the timing is much faster as results are retrieved from checkpoint log, and the steps happen to be encountered in a different order: B1, A1, A2, B2, A3. Because the 'A' steps were encountered in the correct order (A1, A2, A3) and the 'B' steps were encountered in the correct order (B1, B2), the need for determinism was satisfied correctly. Conditional waits Polls for a condition with automatic checkpointing between attempts. The SDK executes your check function, creates a checkpoint with the result, waits according to your strategy, and repeats until the condition is met. TypeScript const result = await context.waitForCondition( async (state, ctx) => { const status = await checkJobStatus(state.jobId); return { ...state, status }; }, { initialState: { jobId: 'job-123', status: 'pending' }, waitStrategy: (state) => state.status === 'completed' ? { shouldContinue: false } : { shouldContinue: true, delay: { seconds: 30 } } } ); Python result = context.wait_for_condition( lambda state, ctx: check_job_status(state['jobId']), config=WaitForConditionConfig( initial_state= { 'jobId': 'job-123', 'status': 'pending'}, wait_strategy=lambda state, attempt: { 'should_continue': False} if state['status'] == 'completed' else { 'should_continue': True, 'delay': 30} ) ) Use waitForCondition for polling external systems, waiting for resources to be ready, or implementing retry with backoff. Function invocation Invokes another Lambda function and waits for its result. The SDK creates a checkpoint, invokes the target function, and resumes your function when the invocation completes. This enables function composition and workflow decomposition. TypeScript const result = await context.invoke( 'invoke-processor', 'arn:aws:lambda:us-east-1:123456789012:function:processor', { data: inputData } ); Python result = context.invoke( 'arn:aws:lambda:us-east-1:123456789012:function:processor', { 'data': input_data}, name='invoke-processor' ) How durable operations are metered Each durable operation you call through DurableContext creates checkpoints to track execution progress and store state data. These operations incur charges based on their usage, and the checkpoints may contain data that contributes to your data write and retention costs. Stored data includes invocation event data, payloads returned from steps, and data passed when completing callbacks. Understanding how durable operations are metered helps you estimate execution costs and optimize your workflows. For details on pricing, see the Lambda pricing page . Payload size refers to the size of the serialized data that a durable operation persists. The data is measured in bytes and the size can vary depending on the serializer used by the operation. The payload of an operation could be the result itself for successful completions, or the serialized error object if the operation failed. Basic operations Basic operations are the fundamental building blocks for durable functions: Operation Checkpoint timing Number of operations Data persisted Execution Started 1 Input payload size Execution Completed (Succeeded/Failed/Stopped) 0 Output payload size Step Retry/Succeeded/Failed 1 + N retries Returned payload size from each attempt Wait Started 1 N/A WaitForCondition Each poll attempt 1 + N polls Returned payload size from each poll attempt Invocation-level Retry Started 1 Payload for error object Callback operations Callback operations enable your function to pause and wait for external systems to provide input. These operations create checkpoints when the callback is created and when it's completed: Operation Checkpoint timing Number of operations Data persisted CreateCallback Started 1 N/A Callback completion via API call Completed 0 Callback payload WaitForCallback Started 3 + N retries (context + callback + step) Payloads returned by submitter step attempts, plus two copies of the callback payload Compound operations Compound operations combine multiple durable operations to handle complex coordination patterns like parallel execution, array processing, and nested contexts: Operation Checkpoint timing Number of operations Data persisted Parallel Started 1 + N branches (1 parent context + N child contexts) Up to two copies of the returned payload size from each branch, plus the statuses of each branch Map Started 1 + N branches (1 parent context + N child contexts) Up to two copies of the returned payload size from each iteration, plus the statuses of each iteration Promise helpers Completed 1 Returned payload size from the promise RunInChildContext Succeeded/Failed 1 Returned payload size from the child context For contexts, such as from runInChildContext or used internally by compound operations, results smaller than 256 KB are checkpointed directly. Larger results aren't stored—instead, they're reconstructed during replay by re-processing the context's operations. Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Security and permissions Supported runtimes Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:30 |
https://www.facebook.com/recover/initiate/?privacy_mutation_token=eyJ0eXBlIjo1LCJjcmVhdGlvbl90aW1lIjoxNzY4Mjk2MTE3fQ%3D%3D&ars=facebook_login&next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0EMbkUGtFhdHj6l1z8H2uKlhWTs2quQSiCv8K0cSF16NogXCojvN6TgLnu9qKqKchnyBFIotVdQS7I3eKZQ2h8gXOqhTlhy1cDSsNfFEZzbVaMjDifGvETKJHqB3aW8g5KStYkt-dHb3rZ | Facebook 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/lambda/latest/dg/durable-getting-started.html | Creating Lambda durable functions - AWS Lambda Creating Lambda durable functions - AWS Lambda Documentation AWS Lambda Developer Guide Prerequisites Create the durable function Invoke the durable function Clean up Next steps Creating Lambda durable functions To get started with Lambda durable functions, use the Lambda console to create a durable function. In a few minutes, you can create and deploy a durable function that uses steps and waits to demonstrate checkpoint-based execution. As you carry out the tutorial, you'll learn fundamental durable function concepts, like how to use the DurableContext object, create checkpoints with steps, and pause execution with waits. You'll also learn how replay works when your function resumes after a wait. To keep things simple, you create your function using either the Python or Node.js runtime. With these interpreted languages, you can edit function code directly in the console's built-in code editor. Tip To learn how to build serverless solutions , check out the Serverless Developer Guide . Prerequisites If you do not have an AWS account, complete the following steps to create one. To sign up for an AWS account Open https://portal.aws.amazon.com/billing/signup . Follow the online instructions. Part of the sign-up procedure involves receiving a phone call or text message and entering a verification code on the phone keypad. When you sign up for an AWS account, an AWS account root user is created. The root user has access to all AWS services and resources in the account. As a security best practice, assign administrative access to a user, and use only the root user to perform tasks that require root user access . AWS sends you a confirmation email after the sign-up process is complete. At any time, you can view your current account activity and manage your account by going to https://aws.amazon.com/ and choosing My Account . After you sign up for an AWS account, secure your AWS account root user, enable AWS IAM Identity Center, and create an administrative user so that you don't use the root user for everyday tasks. Secure your AWS account root user Sign in to the AWS Management Console as the account owner by choosing Root user and entering your AWS account email address. On the next page, enter your password. For help signing in by using root user, see Signing in as the root user in the AWS Sign-In User Guide . Turn on multi-factor authentication (MFA) for your root user. For instructions, see Enable a virtual MFA device for your AWS account root user (console) in the IAM User Guide . Create a user with administrative access Enable IAM Identity Center. For instructions, see Enabling AWS IAM Identity Center in the AWS IAM Identity Center User Guide . In IAM Identity Center, grant administrative access to a user. For a tutorial about using the IAM Identity Center directory as your identity source, see Configure user access with the default IAM Identity Center directory in the AWS IAM Identity Center User Guide . Sign in as the user with administrative access To sign in with your IAM Identity Center user, use the sign-in URL that was sent to your email address when you created the IAM Identity Center user. For help signing in using an IAM Identity Center user, see Signing in to the AWS access portal in the AWS Sign-In User Guide . Assign access to additional users In IAM Identity Center, create a permission set that follows the best practice of applying least-privilege permissions. For instructions, see Create a permission set in the AWS IAM Identity Center User Guide . Assign users to a group, and then assign single sign-on access to the group. For instructions, see Add groups in the AWS IAM Identity Center User Guide . Create a Lambda durable function with the console In this example, your durable function processes an order through multiple steps with automatic checkpointing. The function takes a JSON object containing an order ID, validates the order, processes payment, and confirms the order. Each step is automatically checkpointed, so if the function is interrupted, it resumes from the last completed step. Your function also demonstrates a wait operation, pausing execution for a short period to simulate waiting for external confirmation. To create a durable function with the console Open the Functions page of the Lambda console. Choose Create function . Select Author from scratch . In the Basic information pane, for Function name , enter myDurableFunction . For Runtime , choose either Node.js 24 or Python 3.14 . Select Enable durable execution . Lambda creates your durable function with an execution role that includes permissions for checkpoint operations ( lambda:CheckpointDurableExecutions and lambda:GetDurableExecutionState ). Note Lambda runtimes include the Durable Execution SDK, so you can test durable functions without packaging dependencies. However, we recommend including the SDK in your deployment package for production. This ensures version consistency and avoids potential runtime updates that might affect your function. Use the console's built-in code editor to add your durable function code. Node.js To modify the code in the console Choose the Code tab. In the console's built-in code editor, you should see the function code that Lambda created. If you don't see the index.mjs tab in the code editor, select index.mjs in the file explorer as shown on the following diagram. Paste the following code into the index.mjs tab, replacing the code that Lambda created. import { DurableContext, withDurableExecution, } from "@aws/durable-execution-sdk-js"; export const handler = withDurableExecution( async (event, context) => { const orderId = event.orderId; // Step 1: Validate order const validationResult = await context.step(async (stepContext) => { stepContext.logger.info(`Validating order $ { orderId}`); return { orderId, status: "validated" }; }); // Step 2: Process payment const paymentResult = await context.step(async (stepContext) => { stepContext.logger.info(`Processing payment for order $ { orderId}`); return { orderId, status: "paid", amount: 99.99 }; }); // Wait for 10 seconds to simulate external confirmation await context.wait( { seconds: 10 }); // Step 3: Confirm order const confirmationResult = await context.step(async (stepContext) => { stepContext.logger.info(`Confirming order $ { orderId}`); return { orderId, status: "confirmed" }; }); return { orderId: orderId, status: "completed", steps: [validationResult, paymentResult, confirmationResult] }; } ); In the DEPLOY section, choose Deploy to update your function's code: Understanding your durable function code Before you move to the next step, let's look at the function code and understand key durable function concepts. The withDurableExecution wrapper: Your durable function is wrapped with withDurableExecution . This wrapper enables durable execution by providing the DurableContext object and managing checkpoint operations. The DurableContext object: Instead of the standard Lambda context, your function receives a DurableContext . This object provides methods for durable operations like step() and wait() that create checkpoints. Steps and checkpoints: Each context.step() call creates a checkpoint before and after execution. If your function is interrupted, it resumes from the last completed checkpoint. The function doesn't re-execute completed steps. It uses their stored results instead. Wait operations: The context.wait() call pauses execution without consuming compute resources. When the wait completes, Lambda invokes your function again and replays the checkpoint log, substituting stored values for completed steps. Replay mechanism: When your function resumes after a wait or interruption, Lambda runs your code from the beginning. However, completed steps don't re-execute. Lambda replays their results from the checkpoint log. This is why your code must be deterministic. Python To modify the code in the console Choose the Code tab. In the console's built-in code editor, you should see the function code that Lambda created. If you don't see the lambda_function.py tab in the code editor, select lambda_function.py in the file explorer as shown on the following diagram. Paste the following code into the lambda_function.py tab, replacing the code that Lambda created. from aws_durable_execution_sdk_python import ( DurableContext, durable_execution, durable_step, ) from aws_durable_execution_sdk_python.config import Duration @durable_step def validate_order(step_context, order_id): step_context.logger.info(f"Validating order { order_id}") return { "orderId": order_id, "status": "validated"} @durable_step def process_payment(step_context, order_id): step_context.logger.info(f"Processing payment for order { order_id}") return { "orderId": order_id, "status": "paid", "amount": 99.99} @durable_step def confirm_order(step_context, order_id): step_context.logger.info(f"Confirming order { order_id}") return { "orderId": order_id, "status": "confirmed"} @durable_execution def lambda_handler(event, context: DurableContext): order_id = event['orderId'] # Step 1: Validate order validation_result = context.step(validate_order(order_id)) # Step 2: Process payment payment_result = context.step(process_payment(order_id)) # Wait for 10 seconds to simulate external confirmation context.wait(Duration.from_seconds(10)) # Step 3: Confirm order confirmation_result = context.step(confirm_order(order_id)) return { "orderId": order_id, "status": "completed", "steps": [validation_result, payment_result, confirmation_result] } In the DEPLOY section, choose Deploy to update your function's code: Understanding your durable function code Before you move to the next step, let's look at the function code and understand key durable function concepts. The @durable_execution decorator: Your handler function is decorated with @durable_execution . This decorator enables durable execution by providing the DurableContext object and managing checkpoint operations. The @durable_step decorator: Each step function is decorated with @durable_step . This decorator marks the function as a durable step that creates checkpoints. The DurableContext object: Instead of the standard Lambda context, your function receives a DurableContext . This object provides methods for durable operations like step() and wait() that create checkpoints. Steps and checkpoints: Each context.step() call creates a checkpoint before and after execution. If your function is interrupted, it resumes from the last completed checkpoint. The function doesn't re-execute completed steps. It uses their stored results instead. Wait operations: The context.wait() call pauses execution without consuming compute resources. When the wait completes, Lambda invokes your function again and replays the checkpoint log, substituting stored values for completed steps. Python SDK is synchronous: Note that the Python SDK doesn't use await . All durable operations are synchronous method calls. Invoke the durable function using the console code editor Durable functions require a qualified ARN for invocation. Before you can invoke your durable function, publish a version. To publish a version of your function Choose the Versions tab. Choose Publish new version . For Version description , enter Initial version (optional). Choose Publish . Lambda creates version 1 of your function. Note that the function ARN now includes :1 at the end, indicating this is version 1. Now create a test event to send to your function. The event is a JSON formatted document containing an order ID. To create the test event In the TEST EVENTS section of the console code editor, choose Create test event . For Event Name , enter myTestEvent . In the Event JSON section, replace the default JSON with the following: { "orderId": "order-12345" } Choose Save . To test your durable function and view execution In the TEST EVENTS section of the console code editor, choose the run icon next to your test event: Your durable function starts executing. Because it includes a 10-second wait, the initial invocation completes quickly, and the function resumes after the wait period. You can view the execution progress in the Durable executions tab. To view your durable function execution Choose the Durable executions tab. Find your execution in the list. The execution shows the current status (Running, Succeeded, or Failed). Choose the execution ID to view details, including: Execution timeline showing when each step completed Checkpoint history Wait periods Step results You can also view your function's logs in CloudWatch Logs to see the console output from each step. To view your function's invocation records in CloudWatch Logs Open the Log groups page of the CloudWatch console. Choose the log group for your function ( /aws/lambda/myDurableFunction ). Scroll down and choose the Log stream for the function invocations you want to look at. You should see log entries for each invocation of your function, including the initial execution and the replay after the wait. Clean up When you're finished working with the example durable function, delete it. You can also delete the log group that stores the function's logs, and the execution role that the console created. To delete the Lambda function Open the Functions page of the Lambda console. Select the function that you created. Choose Actions , Delete . Type confirm in the text input field and choose Delete . To delete the log group Open the Log groups page of the CloudWatch console. Select the function's log group ( /aws/lambda/myDurableFunction ). Choose Actions , Delete log group(s) . In the Delete log group(s) dialog box, choose Delete . To delete the execution role Open the Roles page of the AWS Identity and Access Management (IAM) console. Select the function's execution role (for example, myDurableFunction-role- 31exxmpl ). Choose Delete . In the Delete role dialog box, enter the role name, and then choose Delete . Additional resources and next steps Now that you've created and tested a simple durable function using the console, take these next steps: Learn about common use cases for durable functions, including distributed transactions, order processing, and human review workflows. See Examples . Understand how to monitor durable function executions with CloudWatch metrics and execution history. See Monitoring and debugging . Learn about invoking durable functions synchronously and asynchronously, and managing long-running executions. See Invoking durable functions . Follow best practices for writing deterministic code, managing checkpoint sizes, and optimizing costs. See Best practices . Learn how to test durable functions locally and in the cloud. See Testing durable functions . Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Basic concepts Using AWS CLI Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/lambda/latest/dg/durable-execution-sdk.html | Durable execution SDK - AWS Lambda Durable execution SDK - AWS Lambda Documentation AWS Lambda Developer Guide DurableContext What the SDK does How checkpointing works Replay behavior Available durable operations How durable operations are metered Durable execution SDK The durable execution SDK is the foundation for building durable functions. It provides the primitives you need to checkpoint progress, handle retries, and manage execution flow. The SDK abstracts the complexity of checkpoint management and replay, letting you write sequential code that automatically becomes fault-tolerant. The SDK is available for JavaScript, TypeScript, and Python. For complete API documentation and examples, see the JavaScript/TypeScript SDK and Python SDK on GitHub. DurableContext The SDK provides your function with a DurableContext object that exposes all durable operations. This context replaces the standard Lambda context and provides methods for creating checkpoints, managing execution flow, and coordinating with external systems. To use the SDK, wrap your Lambda handler with the durable execution wrapper: TypeScript import { withDurableExecution, DurableContext } from '@aws/durable-execution-sdk-js'; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { // Your function receives DurableContext instead of Lambda context // Use context.step(), context.wait(), etc. return result; } ); Python from aws_durable_execution_sdk_python import durable_execution, DurableContext @durable_execution def handler(event: dict, context: DurableContext): # Your function receives DurableContext # Use context.step(), context.wait(), etc. return result The wrapper intercepts your function invocation, loads any existing checkpoint log, and provides the DurableContext that manages replay and checkpointing. What the SDK does The SDK handles three critical responsibilities that enable durable execution: Checkpoint management: The SDK automatically creates checkpoints as your function executes durable operations. Each checkpoint records the operation type, inputs, and results. When your function completes a step, the SDK persists the checkpoint before continuing. This ensures your function can resume from any completed operation if interrupted. Replay coordination: When your function resumes after a pause or interruption, the SDK performs replay. It runs your code from the beginning but skips completed operations, using stored checkpoint results instead of re-executing them. The SDK ensures replay is deterministic—given the same inputs and checkpoint log, your function produces the same results. State isolation: The SDK maintains execution state separately from your business logic. Each durable execution has its own checkpoint log that other executions cannot access. The SDK encrypts checkpoint data at rest and ensures state remains consistent across replays. How checkpointing works When you call a durable operation, the SDK follows this sequence: Check for existing checkpoint: The SDK checks if this operation already completed in a previous invocation. If a checkpoint exists, the SDK returns the stored result without re-executing the operation. Execute the operation: If no checkpoint exists, the SDK executes your operation code. For steps, this means calling your function. For waits, this means scheduling resumption. Create checkpoint: After the operation completes, the SDK serializes the result and creates a checkpoint. The checkpoint includes the operation type, name, inputs, result, and timestamp. Persist checkpoint: The SDK calls the Lambda checkpoint API to persist the checkpoint. This ensures the checkpoint is durable before continuing execution. Return result: The SDK returns the operation result to your code, which continues to the next operation. This sequence ensures that once an operation completes, its result is safely stored. If your function is interrupted at any point, the SDK can replay up to the last completed checkpoint. Replay behavior When your function resumes after a pause or interruption, the SDK performs replay: Load checkpoint log: The SDK retrieves the checkpoint log for this execution from Lambda. Run from beginning: The SDK invokes your handler function from the start, not from where it paused. Skip completed durable operations: As your code calls durable operations, the SDK checks each against the checkpoint log. For completed durable operations, the SDK returns the stored result without executing the operation code. Note If a child context's result was larger than the maximum checkpoint size (256 KB), the context's code is executed again during replay. This allows you to construct large results from the durable operations that ran inside the context, which will be looked up from the checkpoint log. Therefore it is imperative to only run deterministic code in the context itself. When using child contexts with large results, it is a best practice to perform long-running or non-deterministic work inside of steps and only perform short-running tasks which combine the results in the context itself. Resume at interruption point: When the SDK reaches an operation without a checkpoint, it executes normally and creates new checkpoints as durable operations complete. This replay mechanism requires your code to be deterministic. Given the same inputs and checkpoint log, your function must make the same sequence of durable operation calls. The SDK enforces this by validating that operation names and types match the checkpoint log during replay. Available durable operations The DurableContext provides operations for different coordination patterns. Each durable operation creates checkpoints automatically, ensuring your function can resume from any point. Steps Executes business logic with automatic checkpointing and retry. Use steps for operations that call external services, perform calculations, or execute any logic that should be checkpointed. The SDK creates a checkpoint before and after the step, storing the result for replay. TypeScript const result = await context.step('process-payment', async () => { return await paymentService.charge(amount); }); Python result = context.step( lambda _: payment_service.charge(amount), name='process-payment' ) Steps support configurable retry strategies, execution semantics (at-most-once or at-least-once), and custom serialization. Waits Pauses execution for a specified duration without consuming compute resources. The SDK creates a checkpoint, terminates the function invocation, and schedules resumption. When the wait completes, Lambda invokes your function again and the SDK replays to the wait point before continuing. TypeScript // Wait 1 hour without charges await context.wait( { seconds: 3600 }); Python # Wait 1 hour without charges context.wait(3600) Callbacks Callbacks enable your function to pause and wait for external systems to provide input. When you create a callback, the SDK generates a unique callback ID and creates a checkpoint. Your function then suspends (terminates the invocation) without incurring compute charges. External systems submit callback results using the SendDurableExecutionCallbackSuccess or SendDurableExecutionCallbackFailure Lambda APIs. When a callback is submitted, Lambda invokes your function again, the SDK replays to the callback point, and your function continues with the callback result. The SDK provides two methods for working with callbacks: createCallback: Creates a callback and returns both a promise and a callback ID. You send the callback ID to an external system, which submits the result using the Lambda API. TypeScript const [promise, callbackId] = await context.createCallback('approval', { timeout: { hours: 24 } }); await sendApprovalRequest(callbackId, requestData); const approval = await promise; Python callback = context.create_callback( name='approval', config=CallbackConfig(timeout_seconds=86400) ) context.step( lambda _: send_approval_request(callback.callback_id), name='send_request' ) approval = callback.result() waitForCallback: Simplifies callback handling by combining callback creation and submission in one operation. The SDK creates the callback, executes your submitter function with the callback ID, and waits for the result. TypeScript const result = await context.waitForCallback( 'external-api', async (callbackId, ctx) => { await submitToExternalAPI(callbackId, requestData); }, { timeout: { minutes: 30 } } ); Python result = context.wait_for_callback( lambda callback_id: submit_to_external_api(callback_id, request_data), name='external-api', config=WaitForCallbackConfig(timeout_seconds=1800) ) Configure timeouts to prevent functions from waiting indefinitely. If a callback times out, the SDK throws a CallbackError and your function can handle the timeout case. Use heartbeat timeouts for long-running callbacks to detect when external systems stop responding. Use callbacks for human-in-the-loop workflows, external system integration, webhook responses, or any scenario where execution must pause for external input. Parallel execution Executes multiple operations concurrently with optional concurrency control. The SDK manages parallel execution, creates checkpoints for each operation, and handles failures according to your completion policy. TypeScript const results = await context.parallel([ async (ctx) => ctx.step('task1', async () => processTask1()), async (ctx) => ctx.step('task2', async () => processTask2()), async (ctx) => ctx.step('task3', async () => processTask3()) ]); Python results = context.parallel( lambda ctx: ctx.step(lambda _: process_task1(), name='task1'), lambda ctx: ctx.step(lambda _: process_task2(), name='task2'), lambda ctx: ctx.step(lambda _: process_task3(), name='task3') ) Use parallel to execute independent operations concurrently. Map Concurrently execute an operation on each item in an array with optional concurrency control. The SDK manages concurrent execution, creates checkpoints for each operation, and handles failures according to your completion policy. TypeScript const results = await context.map(itemArray, async (ctx, item, index) => ctx.step('task', async () => processItem(item, index)) ); Python results = context.map( item_array, lambda ctx, item, index: ctx.step( lambda _: process_item(item, index), name='task' ) ) Use map to process arrays with concurrency control. Child contexts Creates an isolated execution context for grouping operations. Child contexts have their own checkpoint log and can contain multiple steps, waits, and other operations. The SDK treats the entire child context as a single unit for retry and recovery. Use child contexts to organize complex workflows, implement sub-workflows, or isolate operations that should retry together. TypeScript const result = await context.runInChildContext( 'batch-processing', async (childCtx) => { return await processBatch(childCtx, items); } ); Python result = context.run_in_child_context( lambda child_ctx: process_batch(child_ctx, items), name='batch-processing' ) The replay mechanism demands that durable operations happen in a deterministic order. Using multiple child contexts you can have multiple streams of work execute concurrently, and the determinism applies separately within each context. This allows you to build high-performance functions which efficiently utilize multiple CPU cores. For example, imagine we start two child contexts, A and B. On the initial invocation, the steps within the contexts were run in this order, with the 'A' steps running concurrently with the 'B' steps: A1, B1, B2, A2, A3. Upon replay, the timing is much faster as results are retrieved from checkpoint log, and the steps happen to be encountered in a different order: B1, A1, A2, B2, A3. Because the 'A' steps were encountered in the correct order (A1, A2, A3) and the 'B' steps were encountered in the correct order (B1, B2), the need for determinism was satisfied correctly. Conditional waits Polls for a condition with automatic checkpointing between attempts. The SDK executes your check function, creates a checkpoint with the result, waits according to your strategy, and repeats until the condition is met. TypeScript const result = await context.waitForCondition( async (state, ctx) => { const status = await checkJobStatus(state.jobId); return { ...state, status }; }, { initialState: { jobId: 'job-123', status: 'pending' }, waitStrategy: (state) => state.status === 'completed' ? { shouldContinue: false } : { shouldContinue: true, delay: { seconds: 30 } } } ); Python result = context.wait_for_condition( lambda state, ctx: check_job_status(state['jobId']), config=WaitForConditionConfig( initial_state= { 'jobId': 'job-123', 'status': 'pending'}, wait_strategy=lambda state, attempt: { 'should_continue': False} if state['status'] == 'completed' else { 'should_continue': True, 'delay': 30} ) ) Use waitForCondition for polling external systems, waiting for resources to be ready, or implementing retry with backoff. Function invocation Invokes another Lambda function and waits for its result. The SDK creates a checkpoint, invokes the target function, and resumes your function when the invocation completes. This enables function composition and workflow decomposition. TypeScript const result = await context.invoke( 'invoke-processor', 'arn:aws:lambda:us-east-1:123456789012:function:processor', { data: inputData } ); Python result = context.invoke( 'arn:aws:lambda:us-east-1:123456789012:function:processor', { 'data': input_data}, name='invoke-processor' ) How durable operations are metered Each durable operation you call through DurableContext creates checkpoints to track execution progress and store state data. These operations incur charges based on their usage, and the checkpoints may contain data that contributes to your data write and retention costs. Stored data includes invocation event data, payloads returned from steps, and data passed when completing callbacks. Understanding how durable operations are metered helps you estimate execution costs and optimize your workflows. For details on pricing, see the Lambda pricing page . Payload size refers to the size of the serialized data that a durable operation persists. The data is measured in bytes and the size can vary depending on the serializer used by the operation. The payload of an operation could be the result itself for successful completions, or the serialized error object if the operation failed. Basic operations Basic operations are the fundamental building blocks for durable functions: Operation Checkpoint timing Number of operations Data persisted Execution Started 1 Input payload size Execution Completed (Succeeded/Failed/Stopped) 0 Output payload size Step Retry/Succeeded/Failed 1 + N retries Returned payload size from each attempt Wait Started 1 N/A WaitForCondition Each poll attempt 1 + N polls Returned payload size from each poll attempt Invocation-level Retry Started 1 Payload for error object Callback operations Callback operations enable your function to pause and wait for external systems to provide input. These operations create checkpoints when the callback is created and when it's completed: Operation Checkpoint timing Number of operations Data persisted CreateCallback Started 1 N/A Callback completion via API call Completed 0 Callback payload WaitForCallback Started 3 + N retries (context + callback + step) Payloads returned by submitter step attempts, plus two copies of the callback payload Compound operations Compound operations combine multiple durable operations to handle complex coordination patterns like parallel execution, array processing, and nested contexts: Operation Checkpoint timing Number of operations Data persisted Parallel Started 1 + N branches (1 parent context + N child contexts) Up to two copies of the returned payload size from each branch, plus the statuses of each branch Map Started 1 + N branches (1 parent context + N child contexts) Up to two copies of the returned payload size from each iteration, plus the statuses of each iteration Promise helpers Completed 1 Returned payload size from the promise RunInChildContext Succeeded/Failed 1 Returned payload size from the child context For contexts, such as from runInChildContext or used internally by compound operations, results smaller than 256 KB are checkpointed directly. Larger results aren't stored—instead, they're reconstructed during replay by re-processing the context's operations. Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Security and permissions Supported runtimes Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:30 |
https://issues.jenkins.io/issues/?jql=labels%20%3D%20newbie-friendly%20AND%20status%20not%20in%20(Closed%2C%20Done%2C%20Resolved%2C%20%22Fixed%20but%20Unreleased%22)%20AND%20component%20%3D%20docker%20AND%20project%20%3D%20JENKINS | Loading... Log in Skip to main content Skip to sidebar Dashboards Projects Issues Give feedback to Atlassian Help Keyboard Shortcuts About Jira Jira Credits Log In 📢 Jenkins core issues have been migrated to GitHub , no new core issues can be created in Jira Export Tools Export - CSV (All fields) Export - CSV (Current fields) Choose a delimiter Comma (,) Semicolon (;) Vertical bar (|) Caret (^) Export Cancel Refresh results {"errorMessages":["jqlTooComplex"],"errors":{}} [{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}] 0.3 0 Atlassian Jira Project Management Software About Jira Report a problem Powered by a free Atlassian Jira open source license for The Linux Foundation. Try Jira - bug tracking software for your team. Atlassian | 2026-01-13T09:29:30 |
https://issues.jenkins.io/browse/JENKINS-62268 | Loading... Log in Skip to main content Skip to sidebar Dashboards Projects Issues Give feedback to Atlassian Help Keyboard Shortcuts About Jira Jira Credits Log In 📢 Jenkins core issues have been migrated to GitHub , no new core issues can be created in Jira Jenkins JENKINS-62268 Jenkins UI Accessibility Information: This issue is archived. You can view it, but you can't modify it. Learn more Log In Open The issue is open and ready for the assignee to start work on it. "> Open Export null XML Word Printable Details Type: Epic Resolution: Unresolved Priority: Minor Component/s: core Labels: accessibility issue-exported-to-github ui ux ux-sig Epic Name: UI-Accessibility Description We would like to make Jenkins usable by as many people as possible. It includes multiple groups of users: people with disabilities, ones using mobile devices, or those with slow network connections. In general, all Jenkins users would benefit from better navigation and layouts. More details will be added soon Attachments Activity People Assignee: Unassigned Reporter: Oleg Nenashev Archiver: Jenkins Service Account Dates Created: 2020-05-13 13:08 Updated: 2025-11-25 08:04 Archived: 2025-11-25 08:04 Atlassian Jira Project Management Software About Jira Report a problem Powered by a free Atlassian Jira open source license for The Linux Foundation. Try Jira - bug tracking software for your team. Atlassian | 2026-01-13T09:29:30 |
https://meeksfamily.uk/~michael/blog/2023/Apr/index.html | Stuff Michael Meeks is doing Stuff Michael Meeks is doing This is my (in)activity log. You might like to visit Collabora Productivity a subsidiary of Collabora focusing on LibreOffice support and services for whom I work. Also if you have the time to read this sort of stuff you could enlighten yourself by going to Unraveling Wittgenstein's net or if you are feeling objectionable perhaps here . Failing that, there are all manner of interesting things to read on the LibreOffice Planet news feed . Older items: 2023 : ( J F M A M J ), 2022 : ( J F M A M J J A S O N D ), 2021 , 2019 , 2018 , 2017 , 2016 , 2015 , 2014 , 2013 , 2012 , 2011 , 2010 , 2009 , 2009 , 2008 , 2007 , 2006 , 2005 , 2004 , 2003 , 2002 , 2001 , 2000 , 1999 , legacy html Sun, 30 Apr 2023 --> 2023-04-30 Sunday All Saints; played with H, Simon & Mary. Growing in number meeting afterwards. Pizza lunch, slept in the afternoon, watched a Glass Onion in the evening. Listened to a couple of talks on Psalm 1. Sat, 29 Apr 2023 --> 2023-04-29 Saturday Up late, relaxed in the sun - and enjoyed aluminium cafe-style setting at the front in the sun. Lunch. David arrived, went for a walk out to Moulton. Home; and set-too with David on re-locating the A/C power, sorting out lighting and so on; got the top of the stairs sorted out. Watched Fury in the evening - interesting. Fri, 28 Apr 2023 --> 2023-04-28 Friday J. working, took a holiday for the first time in a while: started by some business calls, signed a customer. Out to the garage to drill new routes for cables through joists. David arrived & kindly helped. Got joists removed, cables pulled & things re-sited. Used joist-hangers to check the upper stair positioning. Fixed some substantial timbers to the wall to pack the stairs off it by 150mm. Lunch; back into action - got the stairs fixed, lots of PVA glue, hammering of dowels, large screws, and something of a fun lego assembly with wedges, and fitting of this & that. Eventually ended up with a lot of glue, and a nice new pine staircase to replace a rickety ladder together. Caught the end of Time Trap with the babes. Thu, 27 Apr 2023 --> 2023-04-27 Thursday Technical planning call; COOL community call, , 1:1 calls, ESC bits. Early band practice with Simon, Bible study group, bed. Wed, 26 Apr 2023 --> 2023-04-26 Wednesday Early partner call, sales team call plugged away at admin, calls with team members. Eventually discovered that Cypress tests execute in some almost empty DOM/document context. Poked around windows to find the right iframe to dig out the right document and find the pieces we need manually. Tue, 25 Apr 2023 --> 2023-04-25 Tuesday Mail chew, 1:1 with Pedro; stairs arrived to be fitted in the garage: a whole box full of bits of wood to glue in - fun. Plugged away at Cypress with Jaume & Gokay, interactively. Catch up with zlatan. Setup J's garden lean-to with hooks for tools & some racking. Mon, 24 Apr 2023 --> 2023-04-24 Monday Mail chew, planning call, various calls, catch up with Tor, poked at Cypress issues some more with Gokay & Jaume. Worked on isolating parallel running coolwsd's more sensibly at some length. Music with E. and a story too - been working too late many nights recently; hmm. Sun, 23 Apr 2023 --> 2023-04-23 Sunday All Saints, 2m Peter playing the organ - did some orchestration for him. Home for a snack, babes had Pizza. Alfie over to do his first laptop keyboard replacement. Kelsey, Chris, Charlie & Emma over for a late lunch, chatted with them through the afternoon; picked up the babes from StAG. Sat, 22 Apr 2023 --> 2023-04-22 Saturday Up; off to clean & de-cobweb AllSaints - climbed some rather tall ladders & chatted to people variously; bacon sandwiches. David arrived and helped out. Home for lunch, set too at the garage, removed shelving, made space for new staircase; re-hung lean-to door, and strengthened the structure. David M. moved tiles while I helped David S. install the glass on a new Velux at his house - by the fourth, we're getting quite good at it. Home, more prep work - cut out some hatch joists with the reciprocating saw, and moved some inconvenient wiring around the place. Dinner together. Worked late poking at Cypress and C++ unit test failures on busy machines. Fri, 21 Apr 2023 --> 2023-04-21 Friday Out for a run with J. early. Mail chew, plugged away at some consistency checks to detect unhelpful 3rd parties that like to eg. delete the filesystem underneath a running process, and then wonder why things stop working. Various partner calls; into Cambridge to meet up with the very charming Niels of OpenProject fame, and his brother. Took H. home from work, dinner, back to cleaning up loose ends from the day. Fixed up J's counselling website so http works (was never tested), and mended some old blog links. Thu, 20 Apr 2023 --> 2023-04-20 Thursday Wedding anniversary - 21 years - what a lovely time we've had together: what a blessing. To work! Technical planning call, COOL community call, K8s design call, catch up with Andras, ESC meeting. Apparently my blood says I need more vitamin-D - fair enough. Mihai making good progress, concrete base, bits of roof, fibreglass & epoxy. Wed, 19 Apr 2023 --> 2023-04-19 Wednesday Slept for a couple of hours; back to an all-night hackathon - (also wrote J's wedding anniversary card) - trying to unwind 'orrible, intermittent Cypress problems. Mihai arrived to build a garden lean-to / shed for J's garden tools & other bits cluttering my garage^Workshop. Sales call, went for a bleed at the hospital, lunch. All afternoon quarterly Collabora mgmt call, did some mail & review in parallel. Band practice in the evening, then out for a lovely pre-21st-wedding-anniversary-dinner with J. at a new local Turkish restaurant: lovely & lots of it. Staggered home happily. Tue, 18 Apr 2023 --> 2023-04-18 Tuesday Mail chew; overdue catch ups with Kendy, then Pedro. Slides, monthly mgmt meeting. Popped over to see David S & help him get his new velux window glassware inserted: a small piece of ply-wood with a block at the end turns out to be the optimal tool. As I try to improve my German; really pleased to read Henry Hühnchen to the family "Der Himmel stürzt ein!", sagt Henry Hühnchen . Helped M. organize and glue her chess-board together in the evening until late, hopefully the big-breaker of old PVA will still do the job. Mon, 17 Apr 2023 --> 2023-04-17 Monday Up early, mail chew, planning call, plugged away at Cypress bits with Jaume; catch up with Marc, then Philippe. Sun, 16 Apr 2023 --> 2023-04-16 Sunday All Saints - played in the morning, Sue spoke. Home for a pizza lunch, with our neighbour Tammy over to share that. Out in the evening to try to unwind a friend's laptop purchase that got twisted up; hopefully successfully. Sat, 15 Apr 2023 --> 2023-04-15 Saturday Worked much of the morning; found that Cypress tests were re-downloading & jitting all the JS, added a force cache parameter to (hopefully) markedly accelerate them. Poked at some brian-straining Cypress timing / intermittency issues; improved waiting for cursor movements. David over, out for a walk with J,H,E - M&N revising in Cambridge. Measured up the garage for some new stairs, and mounted Dad's tool cabinet. Cypress: removed extra simulated button presses on emitting text events; reviewed a number of Ash's patches, worked late. Fri, 14 Apr 2023 --> 2023-04-14 Friday Mail chew, partner call, catch up with Ash & Jaume. Lunch. Partner call. Pleased to see a nice recap of COOL days , and some wrap-up ramblings too. Reviewed some commits. Dinner, solicited and processed more product management input from partners and customers - great to have a good way of capturing where they want to go. Thu, 13 Apr 2023 --> 2023-04-13 Thursday Mail chew, sync with Miklos, COOL community call, catch up with Andras,Pedro & Anna. Sync with Cor. Quick lunch, partner call, customer call with partner. Out for a run with J. Plugged away at BinaryDataContainer re-factoring to make it swap-able. Wed, 12 Apr 2023 --> 2023-04-12 Wednesday Up earlyish, helped Dad grind some stainless strip to mend his cupboards, read The Magician's Nephew - a classic. Catch up call with Eloy; caught up with some mail. Lunch. Bid 'bye, slept & chewed mail on the way home in the car - terrible weather. Got some work done in the afternoon; All Saints band practice in the evening with H. Tue, 11 Apr 2023 --> 2023-04-11 Tuesday Up early, breakfast, helped Dad get a root out in the garden, remove lots of leaves, moss & mulch from the shed's guttering. Out for a walk around Ripley Castle in the sun with M&D - lovely - fine Ripley ice-cream afterwards. Home for lunch. M. set-too with the joiner/thicknesser to make lots of beautiful, planed beech and teak lengths to turn into a chess-board. Dug out Dad's tool cupboard for the workshop & eventually found the key for it, nice. Pleased H. had a good 1st day at HP in Cambridge. Watched an old Animal Farm (with real animals - and a happy ending) - somewhat underwhelmed; not the point. Mon, 10 Apr 2023 --> 2023-04-10 Monday Up lateish; bid 'bye to R & A & boys. Plugged away in the car at an unreliable unit test, blog update & image size profiling. Out for a walk into town, and up the castle steps - a lovely day. Jigsaw puzzle. Experimented with joiner, thicknesser with M. for her chess-board. Discovered joining on the convex surface tends to exacerbate non-flatness - fun. Sun, 09 Apr 2023 --> 2023-04-09 Sunday Robert, Amelia & boys arrived overnight; taught them to 'peg' people. Good to see them - out to All Saints - Bishop Mike speaking. H. playing the organ, Jenny there too nice. Good to catch up with people afterwards. Home for rib & drumstick lunch with the family; sat around chatting variously, slept for a bit; tea. Played Carcassonne & Camel Up in the evening with R&A, up late chatting with R. Sat, 08 Apr 2023 --> 2023-04-08 Saturday Up; strimmed the grass, re-layed-out the last PCC minutes, finally transribed the last set of APCM minutes - nice. Re-routed the front-door keeps so the door can be double-locked without excessive force - very much nicer. Spent some time with M. investigating making a copying tool for chess pieces. Fri, 07 Apr 2023 --> 2023-04-07 Friday Up lateish; time for a day off. Did some hacking - found a way to persuade SwLayIdle only to do huge invalidations rather than expensive off-screen rendering. Put the washing out. Sue, Clive & boys arrived - fine lunch, and out for a wander with them - nice to catch up. Out for a long walk with Chris Brighty in the evening, sunset over the race tracks: pretty. Ordered Ash dowel & epoxy for M's chess-board + pieces project in the evening. Thu, 06 Apr 2023 --> 2023-04-06 Thursday COOL commnuity call, monthly CP all-hands call, partner call; customer catch-up call. Finally got to some more profiling of an image movement performance problem - SwLayIdle again doing a giant double-buffered rendering - interesting. Cell group passover-style meal in the evening; lamb & questions, Christina over to see H. too. Wed, 05 Apr 2023 --> 2023-04-05 Wednesday More report writing; bits of hacking on image scaling performance, out for a run with J. Partner call. Catch up with Caolan. Band practice with H. worked on improving my organ stop-pulling skills. Grace for sleep-over with M. Watched Ponyo - something fishy about that film. Tue, 04 Apr 2023 --> 2023-04-04 Tuesday Good to get up later than 6:20am in the holidays; worked on report writing much of the day, catch-up with Marco, call with Mazin. Worked late, H's friend Charlotte stayed over. Mon, 03 Apr 2023 --> 2023-04-03 Monday Mail chew, sparse planning call - people taking a well deserved rest. Chat with allotropia team, then with our a11y team doing some encouraging work. Out for a run with J.. Mail & meetings variously. H's friend Nina around - lots of friends of H's about too. Sun, 02 Apr 2023 --> 2023-04-02 Sunday All Saints in the morning, J. at Grace's baptism at the Ark, shared lunch. Pottered around tidying the garage - amazing how many boxes of screws one can accumulate. Sat, 01 Apr 2023 --> 2023-04-01 Saturday Up lateish, got sucked into some more BinaryDataContainer preparatory re-factoring: hacking is fun! Helped M. get setup with the bandsaw to cut her chess-board out of some useful slabs from John Cornish, with David's help too: fun. Got a genuine-Meeks-sr. cupboard onto the wall. My content in this blog and associated images / data under images/ and data/ directories are (usually) created by me and (unless obviously labelled otherwise) are licensed under the public domain, and/or if that doesn't float your boat a CC0 license. I encourage linking back (of course) to help people decide for themselves, in context, in the battle for ideas, and I love fixes / improvements / corrections by private mail. In case it's not painfully obvious: the reflections reflected here are my own; mine, all mine ! and don't reflect the views of Collabora, SUSE, Novell, The Document Foundation, Spaghetti Hurlers (International), or anyone else. It's also important to realise that I'm not in on the Swedish Conspiracy . Occasionally people ask for formal photos for conferences or fun . Michael Meeks ( michael.meeks@collabora.com ) | 2026-01-13T09:29:30 |
https://aws.amazon.com/lambda/pricing/#SnapStart_Pricing | AWS Lambda Pricing Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Lambda Overview Features Pricing Getting Started Resources More Compute › AWS Lambda › Pricing AWS Lambda pricing Get started for free Request a pricing quote Overview AWS Lambda is a serverless compute service that lets you run code without provisioning or managing servers. Create workload-aware cluster scaling logic, maintain event integrations, and manage runtimes with ease. With Lambda, you can run code for virtually any type of application or backend service, all with zero administration, and only pay for what you use. You are charged based on the number of requests for your functions and the duration it takes for your code to execute. Lambda counts a request each time it starts executing in response to an event notification trigger, such as from Amazon Simple Notification Service (SNS) or Amazon EventBridge, or an invoke call, such as from Amazon API Gateway, or via the AWS SDK, including test invokes from the AWS Console. Duration is calculated from the time your code begins executing until it returns or otherwise terminates, rounded up to the nearest 1 ms*. The price depends on the amount of memory you allocate to your function. In the AWS Lambda resource model, you choose the amount of memory you want for your function, and are allocated proportional CPU power and other resources. An increase in memory size triggers an equivalent increase in CPU available to your function. To learn more, see the Function Configuration documentation. You can run your Lambda functions on processors built on either x86 or Arm architectures. AWS Lambda functions running on Graviton2, using an Arm-based processor architecture designed by AWS, deliver up to 34% better price performance compared to functions running on x86 processors. This applies to a variety of serverless workloads, such as web and mobile backends, data, and media processing. * Duration charges apply to code that runs in the handler of a function as well as initialization code that is declared outside of the handler. For Lambda functions with AWS Lambda Extensions , duration also includes the time it takes for code in the last running extension to finish executing during shutdown phase. For Lambda functions configured with SnapStart , duration also includes the time it takes for the runtime to load, any code that runs in a runtime hook , and the initialization code executed during creation of copies of snapshots created for resilience. For more details, see the Lambda Programming Model documentation. The AWS Lambda free tier includes one million free requests per month and 400,000 GB-seconds of compute time per month, usable for functions powered by both x86, and Graviton2 processors, in aggregate. Additionally, the free tier includes 100GiB of HTTP response streaming per month, beyond the first 6MB per request, which are free. Lambda also offers tiered pricing options for on-demand duration above certain monthly usage thresholds. AWS Lambda participates in Compute Savings Plans, a flexible pricing model that offers low prices on Amazon Elastic Compute Cloud (Amazon EC2), AWS Fargate, and Lambda usage, in exchange for a commitment to a consistent amount of usage (measured in $/hour) for a one- or three-year term. With Compute Savings Plans, you can save up to 17 percent on AWS Lambda. Savings apply to duration and Provisioned Concurrency. Learn more AWS Pricing Calculator Calculate your AWS Lambda and architecture cost in a single estimate. Create your custom estimate now AWS Lambda Pricing Asynchronous Event (including events from S3, SNS, EventBridge, StepFunctions, Cloudwatch Logs): You are charged for 1 request per each asynchronous Event for first 256 KB. Individual event size beyond 256 KB is charged 1 additional request for each 64 KB of chunk upto 1 MB. Duration cost depends on the amount of memory you allocate to your function. You can allocate any amount of memory to your function between 128 MB and 10,240 MB, in 1 MB increments. The table below contains a few examples of the price per 1 ms associated with different memory sizes, for usage falling within the first pricing tier – for example, up to 6 billion GB-seconds / month in US East (Ohio) x86 Price Arm Price x86 Price Arm Price Lambda on-demand duration pricing tiers are applied to aggregate monthly duration of your functions running on the same architecture (x86 or Arm, respectively), in the same region, within the account. If you’re using consolidated billing in AWS Organizations, pricing tiers are applied to the aggregate monthly duration of your functions running on the same architecture, in the same region, across the accounts in the organization. Lambda Managed Instances Lambda Managed Instances enables you to run Lambda functions on fully-managed EC2 instances in your VPC, combining Lambda's serverless developer experience with the cost efficiency and hardware flexibility of EC2. This feature is ideal for steady-state, high-volume workloads where you want to optimize costs while maintaining Lambda's operational simplicity. With Lambda Managed Instances, you can select from a wide variety of current-generation EC2 instance type to match your workload requirements, benefit from EC2 pricing options including EC2 Instance Savings Plans, Compute Savings Plans and Reserved Instances, and process multiple requests concurrently within the same execution environment to maximize resource utilization. Lambda automatically manages instance provisioning, scaling, patching, and lifecycle management, while you retain the familiar Lambda programming model and seamless integration with event sources like SQS, Kinesis, and Kafka. Pricing : Lambda Managed Instances pricing has three components: 1. Request charges : $0.20 per million requests 2. Compute management fee : 15% premium on the EC2 on-demand instance price for the instances provisioned and managed by Lambda (Premium for each instance type provided below) 3. EC2 instance charges : Standard EC2 instance pricing applies for the instances provisioned in your capacity provider. You can reduce costs by using Compute Savings Plans, Reserved Instances, or other EC2 pricing options Note that Lambda Managed Instances functions will not be paying separately for the execution duration of each request unlike Lambda (default) compute type functions. Event Source Mappings : For workloads using provisioned Event Poller Units (EPUs) with event sources like Kafka or SQS, standard EPU pricing applies. Management Fees Pricing Example: High-throughput API service Suppose you're running a high-traffic API service that processes 100 million requests per month with an average duration of 200ms per request. You configure your Lambda Managed Instance capacity provider to use m7g.xlarge instances (4 vCPU, 16 GB memory, Graviton3) and use a 3-year Compute Savings Plan for maximum cost savings. Monthly charges Request charges Monthly requests: 100M requests Request price: $0.20 per million requests Monthly request charges: 100M / 1M × $0.20 = $20 Compute charges Instance type: m7g.xlarge EC2 on-demand price: $0.1632 per hour (US East N. Virginia) With 3-year Compute Savings Plan discount (72%): $0.0457 per hour Estimated instance hours needed: ~2,000 hours/month (based on workload pattern and multi-concurrency) Monthly EC2 instance charges: 2,000 × $0.0457 = $91.40 Management fee charges Management fee: 15% of EC2 on-demand price Management fee per hour: $0.1632 × 0.15 = $0.02448 per hour Monthly management fee: 2,000 × $0.02448 = $48.96 Total monthly charges Total charges = Request charges + EC2 instance charges + Management fee charges Total charges = $20 + $91.40 + $48.96 = $160.36 Lambda Durable Functions Pricing Lambda durable functions simplify how you build reliable multi-step applications and AI workflows directly within Lambda’s existing programming model, enabling resilient and cost-effective long-running workloads. In durable functions, you use durable operations like “steps” and “waits”, which are checkpoints with optional data stored for extended periods, allowing your function to resume execution after interruptions. When functions resume, the system performs replay, automatically re-executing the event handler from the beginning while skipping completed checkpoints and continuing from the point of interruption. The lifecycle may include multiple sub-invocations (Lambda function invocations that occur when resuming after wait operations, retries, or infrastructure failures) to complete the execution. Existing Lambda compute charges apply, including for sub-invocations from replays. When using wait operations, the function suspends execution and, for on-demand functions, does not incur duration charges until execution resumes. In addition, you are charged for durable operations (such as starting executions, completing steps, and creating waits). You also pay for the amount of data written by these operations (in GB) and for data retention during and after execution (in GB-month, prorated). The retention period after completion is configurable from 1 to 90 days (default 14 days). For a full list and detailed description of durable operations, see the Lambda Developer Guide . Pricing Example: An insurance claim processing system uses Lambda durable functions to analyze claims for fraud detection, coordinate human review for high-value claims, and process approved payments. The process begins with a document analysis step that takes 30 seconds to perform LLM-based fraud detection and risk assessment. The execution then uses a wait to suspend execution for a human review (typically 7 days wait) where an adjuster reviews claims exceeding automatic approval thresholds. Finally, a payment step taking 2 seconds to process the approval decision to initiate the payment. The system processes 1,000,000 insurance claims per month. Each execution uses an 8KB invocation payload and 32KB payloads for claim analysis (step 1), approval decisions (wait), and final payment processing (step 2). The function is configured with 1GB of memory on an ARM-based processor. Completed claim records are retained for 14 days for audit and compliance. Note: Examples are based on price in US East (N. Virginia). All executions start at the beginning of the month and all steps succeed on first attempt without retries to simplify the calculations. Note: Examples are based on price in US East (N. Virginia). All executions start at the beginning of the month and all steps succeed on first attempt without retries to simplify the calculations. Monthly Compute Charges Total compute (seconds) 1,000,000 × 32s = 32,000,000 seconds Total compute (GB-s) 32,000,000 × 1GB = 32,000,000 GB-s Billable compute 32,000,000 - 400,000 free tier = 31,600,000 GB-s Compute cost 31,600,000 × $0.0000133334 = $421.34 Monthly Request Charges Total requests 2 invocations (initial + after wait) × 1,000,000 = 2,000,000 requests Billable requests 2,000,000 - 1M free tier = 1,000,000 Request cost 1M × $0.20/M = $0.20 Monthly Durable Functions Charges Operations 1M × (1 start execution + 2 steps + 1 wait) = 4M Operations cost 4M × $8.00/M = $32.00 Data Written 1M × (8KB invoke + 3 × 32KB steps/waits) = 104GB Data written cost 104GB × $0.25/GB = $26.00 Storage (running incl. 7 day wait) 104GB × (7/30) = 24.27 GB-month Storage (retained 14 days) 104GB × (14/30) = 48.53 GB-month Data Retained cost (24.27 + 48.53) GB-month × $0.15/GB-month = $10.92 Total Monthly Charges Total charges $421.34 + $0.20 + $32.00 + $26.00 + $10.92 = $490.46 Tenant Isolation Pricing Enable tenant isolation mode to isolate request processing for individual end-users or tenants invoking your Lambda function. The underlying execution environments for a tenant-isolated Lambda function are always associated with a particular tenant and are never used to execute requests from other tenants invoking the same function. This capability simplifies developing and maintaining multi-tenant applications that process tenant-specific code or data with strict isolation requirements across tenants. You are charged when Lambda creates a new tenant-isolated execution environment to serve a request, depending on the amount of memory you allocate to your function and the CPU architecture you use. To learn more about Lambda's tenant isolation capability, read the documentation . Pricing Example: Multi-tenant SaaS application Multi-tenant SaaS application Let’s assume you are building an automation platform that executes user-provided code in response to events. For example, an IT team may want to execute an automated workflow when a new employee joins their organization or transfers across departments. As another example, a DevOps team may want to trigger a CI/CD workflow when a developer commits code changes to their source code repository. Your automation platform is multi-tenant, meaning that it serves multiple end-users. Because you expect high variation in demand, by time of day and for each end-user or tenant, you build your platform using serverless services including AWS Lambda. Your automation platform supports the ability to run user-supplied code in response to events. Since you do not control the code provided by users, you enable tenant isolation mode to ensure that Lambda function invocations for each end-user are processed in separate execution environments that are isolated from one another. Assume that you have configured your Lambda function with 1024 MB of memory and x86 CPU architecture. During a typical month, your function processes 10M invokes with an average duration of 2 seconds per invoke. Your SaaS platform is used by 1K end-users or tenants. For simplicity, let’s assume that on average each tenant generates 10K invokes per month and Lambda creates 200 execution environments per tenant (i.e. a cold-start rate of 2% per tenant). Your charges would be calculated as follows: Request charges Per month, your function executes 10M times. Monthly request charges: 10M * $0.2/M = $2. Compute charges Per month, your function executes 10M times with an average duration of 2s. Your function's configured memory is 1024 MB. Monthly compute duration (seconds): 10M * 2s = 20M seconds Monthly compute (GB-s): 20M seconds * 1024 MB / 1024 MB = 20M GB-s Monthly compute charges: 20M * $0.0000166667 = $333.34 Tenant isolation charges Per month, on average, your function serves 1K unique tenants. Each tenant invokes the function 10K times with an average of 200 execution environments created per tenant (i.e. average cold-start rate of 2% for each tenant). Monthly execution environments created for 1K tenants: 200 * 1K = 200K Monthly tenant isolation charges: 200K * $0.000167 * 1024 MB / 1024MB = $33.4 Total monthly charges Total charges = Request charges + Compute charges + Tenant isolation charges Total charges = $2 + $333.34 + $33.4 = $368.74 Lambda Ephemeral Storage Pricing Ephemeral storage cost depends on the amount of ephemeral storage you allocate to your function, and function execution duration, measured in milliseconds. You can allocate any additional amount of storage to your function between 512 MB and 10,240 MB, in 1 MB increments. You can configure ephemeral storage for functions running on both x86 and Arm architectures. 512 MB of ephemeral storage is available to each Lambda function at no additional cost. You only pay for the additional ephemeral storage you configure. All examples below are based on price in US East (N. Virginia). Example 1: Mobile application backend Let’s assume you are a mobile app developer building a food ordering app. Customers can use the app to order food from a specific restaurant location, receive order status updates, and pick up the food when the order is ready. Because you expect high variation in demand, both by time of day and restaurant location, you build your mobile backend using serverless services, including AWS Lambda. Let’s assume you are a mobile app developer building a food ordering app. Customers can use the app to order food from a specific restaurant location, receive order status updates, and pick up the food when the order is ready. Because you expect high variation in demand, both by time of day and restaurant location, you build your mobile backend using serverless services, including AWS Lambda. For simplicity, let’s assume your application processes three million requests per month. The average function execution duration is 120 ms. You have configured your function with 1536 MB of memory, on an x86 based processor. Your charges would be calculated as follows: Monthly compute charges The monthly compute price is $0.0000166667 per GB-s and the free tier provides 400,000 GB-s. Total compute (seconds) = 3 million * 120ms = 360,000 seconds Total compute (GB-s) = 360,000 * 1536MB/1024 MB = 540,000 GB-s Total compute – Free tier compute = monthly billable compute GB- s 540,000 GB-s – 400,000 free tier GB-s = 140,000 GB-s Monthly compute charges = 140,000 * $0.0000166667 = $2.33 Monthly request charges The monthly request price is $0.20 per one million requests and the free tier provides 1 million requests per month. Total requests – Free tier requests = monthly billable requests 3 million requests – 1 million free tier requests = 2 million monthly billable requests Monthly request charges = 2M * $0.2/M = $0.40 Total monthly charges Total charges = Compute charges + Request charges = $2.33 + $0.40 = $2.73 per month Example 2: Enriching streaming telemetry with additional metadata Let’s say you are a logistics company with a fleet of vehicles in the field, each of which are enabled with sensors and 4G/5G connectivity to emit telemetry data into an Amazon Kinesis Data Stream. You want to use machine learning (ML) models you’ve developed to infer the health of the vehicle and predict when maintenance for particular components might be required. Let’s say you are a logistics company with a fleet of vehicles in the field, each of which are enabled with sensors and 4G/5G connectivity to emit telemetry data into an Amazon Kinesis Data Stream. You want to use machine learning (ML) models you’ve developed to infer the health of the vehicle and predict when maintenance for particular components might be required. Suppose you have 10,000 vehicles in the field, each of which is emitting telemetry once an hour in a staggered fashion with sufficient jitter. You intend to perform this inference on each payload to ensure vehicles are scheduled promptly for maintenance and ensure optimal health of your vehicle fleet. Assume the ML model is packaged along with the function and is 512 MB in size. For inference, you’veconfigured your function with 1 GB of memory, and function execution takes two seconds to complete on average on an x86 based processor. Monthly request charges : Per month, the vehicles will emit 10,000 * 24 * 31 = 7,440,000 messages which will be processed by the Lambda function. Monthly request charges → 7.44M * $0.20/million = $1.488 ~= $1.49 Monthly compute charges: Per month, the functions will be executed once per message for two seconds. Monthly compute duration (seconds) → 7.44 million * 2 seconds = 14.88 million seconds Monthly compute (GB-s) → 14.88M seconds * 1024 MB/1024 MB = 14.88 GB-s Monthly compute charges → 14.88M GB-s * $0.0000166667 = $248.00 Total monthly charges: Monthly total charges = Request charges + Compute charges = $1.49 + $248.00 = $249.49 Example 3: Performing ML on customer support tickets and interactions to improve customer experience Let’s assume you are a financial services company looking to better understand your top customer service issues. Your goal is to improve the customer experience and reduce customer churn. Your customers can chat live with your customer support staff via the mobile app you provide. You decide to deploy a natural language processing (NLP) model. Let’s assume you are a financial services company looking to better understand your top customer service issues. Your goal is to improve the customer experience and reduce customer churn. Your customers can chat live with your customer support staff via the mobile app you provide. You decide to deploy a natural language processing (NLP) model. In this case, you are using the popular Bidirectional Encoder Representations from Transformers (BERT) model in AWS Lambda. The model helps you parse, analyze, and understand the customer service interactions via the mobile app in order to display relevant support content or route the customer to the appropriate customer service agent. The number of support inquiries your inference model processes varies widely throughout the week. Let’s assume your functions running the inference model receive six million requests per month. The average function execution duration is 280 ms. You configure your function with 4096 MB of memory on an x86 based processor. You also configure your function to use 2048 MB of ephemeral storage. Your charges would be calculated as follows: Monthly compute charges: The monthly compute price is $0.0000166667 per GB-s and the free tier provides 400,000 GB-s. Total compute (seconds) = 6M * 280ms = 1,680,000 seconds Total compute (GB-s) = 1,680,000 * 4096 MB/1024 MB = 6,720,000 GB-s Total compute – AWS Free Tier compute = Monthly billable compute GB- s 6,720,000 GB-s – 400,000 free tier GB-s = 6,320,000 GB-s Monthly compute charges = 6,320,000 * $0.0000166667 = $105.33 Monthly request charges: The monthly request price is $0.20 per one million requests and the free tier provides one million requests per month. Total requests – Free tier requests = monthly billable requests 6 million requests – 1 million free tier requests = 5 million monthly billable requests Monthly request charges = 5 million * $0.2/million = $1 Monthly ephemeral storage charges: The monthly ephemeral storage price is $0.0000000309 for every GB-second and Lambda provides 512 MB of storage at no additional cost. Total compute (seconds) = 6M * 280ms = 1,680,000 seconds Total billable ephemeral storage = 2048 MB – 512 MB = 1536 MB Total ephemeral storage (GB-s) = 1,680,000 * 1536 MB/1024 MB = 2,520,000 GB-s Monthly ephemeral storage charges = 2,520,000 * $0.0000000309 = $0.08 Total monthly charges: Total charges = Compute charges + Request charges = $105.33 + $1 + $0.08 = $106.41 per month Provisioned Concurrency Pricing Enable Provisioned Concurrency for your Lambda functions for greater control over your serverless application performance. When enabled, Provisioned Concurrency keeps functions initialized and hyper-ready to respond in double-digit milliseconds. You pay for the amount of concurrency you configure, and for the period of time you configure it. When Provisioned Concurrency is enabled and executed for your function, you also pay for Requests and Duration based on the prices below. If your function exceeds the configured concurrency, you will be billed for excess function execution at the rate outlined in the AWS Lambda Pricing section above. You can enable Provisioned Concurrency for functions running on both the x86 and Arm architectures. To learn more about Provisioned Concurrency, read the documentation. Provisioned Concurrency is calculated from the time you enable it on your function until it is disabled, rounded up to the nearest five minutes. The price depends on the amount of memory you allocate to your function and the amount of concurrency that you configure on it. Duration is calculated from the time your code begins executing until it returns or otherwise terminates, rounded up to the nearest 1ms**. The price depends on the amount of memory you allocate to your function. ** Duration charges apply to code that runs in the handler of a function as well as initialization code that is declared outside of the handler. For Lambda functions with AWS Lambda Extensions, duration also includes the time it takes for code in the last running extension to finish executing during shutdown phase. For functions configured with Provisioned Concurrency, AWS Lambda periodically recycles the execution environments and re-runs your initialization code. For more details, see the Lambda Programming Model documentation. The Lambda free tier does not apply to functions enabling Provisioned Concurrency. If you enable Provisioned Concurrency for your function and execute it, you will be charged for Requests and Duration based on the price below. All examples below are based on price in US East (N. Virginia). Example 1: Mobile application launch Let’s assume you are a mobile app developer and are building a food ordering mobile application. Customers can use the application to order food from a specific restaurant location, receive order status updates, and pick up the food when the order is ready. Because you expect high variation in your application demand, both by time of day and restaurant location, you build your mobile backend using serverless services, including AWS Lambda. Let’s assume you are a mobile app developer and are building a food ordering mobile application. Customers can use the application to order food from a specific restaurant location, receive order status updates, and pick up the food when the order is ready. Because you expect high variation in your application demand, both by time of day and restaurant location, you build your mobile backend using serverless services, including AWS Lambda. For simplicity, let’s assume your application processes three million requests per month. The average function execution duration is 120 ms. You have configured your function with 1536 MB of memory on an x86 based processor. You are launching the new version of your mobile app, which you have heavily marketed. You expect a spike in demand during launch day, from noon to 8 p.m. You want your mobile app to be responsive even while demand scales up and down quickly, so you enable Provisioned Concurrency on your Lambda functions. You set Provisioned Concurrency to 100. During these eight hours, your functions received 500,000 requests. The average function execution duration while Provisioned Concurrency is enabled is 100 ms. During the rest of the month, your application receives the additional 2.5 million requests, and your functions execute in response to them without Provisioned Concurrency enabled. Your charges would be calculated as follows: Provisioned Concurrency charges: The Provisioned Concurrency price is $0.0000041667 per GB-s Total period of time for which Provisioned Concurrency is enabled (seconds): 8 hours * 3,600 seconds = 28,800 seconds Total concurrency configured (GB): 100 * 1536MB/1024MB = 150 GB Total Provisioned Concurrency amount (GB-s): 150 GB * 28,800 seconds =4,320,000 GB-s Provisioned Concurrency charges: 4.32M GB-s * $0.0000041667 = $18 Request charges: The monthly request price is $0.20 per 1 million requests and the free tier provides 1M requests per month. Total requests – Free tier requests = Monthly billable requests 3,000,000 requests – 1M free tier requests = 2,000,000 Monthly billable requests Monthly request charges = 2 * $0.20 = $0.40 Compute charges while Provisioned Concurrency is enabled: The compute price is $0.0000097222 per GB-s Total compute duration (seconds) = 500,000 * 100ms = 50,000 seconds Total compute (GB-s) = 50,000 seconds * 1536 MB / 1024 MB = 75,000 GB-s. Total compute charges = 75,000 GB-s * $0.0000097222 = $0.73 Compute charges while Provisioned Concurrency is disabled: The monthly compute price is $0.0000166667 per GB-s and the free tier provides 400,000 GB-s. Total compute (seconds) = 2.5M * 120ms = 300,000 seconds Total compute (GB-s) = 300,000 * 1536 MB / 1024 MB = 450,000 GB-s Total compute – Free tier compute = Monthly billable compute GB- s 450,000 GB-s – 400,000 free tier GB-s = 50,000 GB-s Monthly compute charges = 50,000 * $0.0000166667 = $0.83 Total monthly charges: Total charges = Provisioned Concurrency charges + Request charges + Compute charges while Provisioned Concurrency is enabled + Compute charges while Provisioned Concurrency is disabled Total charges = $18 + $0.40 + $0.73 + $0.83 = $19.96 Example 2 : Routing customers to the most relevant support solution content during Cyber Monday Let’s assume you are a retailer running a large sale during Cyber Monday, an ecommerce holiday that takes place the Monday after Thanksgiving in the United States. Your customers can chat live with customer support via the mobile app you provide. You decide to deploy a natural language processing (NLP) model. Let’s assume you are a retailer running a large sale during Cyber Monday, an ecommerce holiday that takes place the Monday after Thanksgiving in the United States. Your customers can chat live with customer support via the mobile app you provide. You decide to deploy a natural language processing (NLP) model. In this case, you are using the popular Bidirectional Encoder Representations from Transformers (BERT) model in AWS Lambda. The model helps you parse, analyze, and understand customer service interactions via the mobile app in order to display relevant support content or route the customer to the appropriate customer service agent. You will receive significantly more customer support inquiries during this sale than usual, so you decide to enable Provisioned Concurrency on your Lambda functions so your application responds quickly even while experiencing traffic spikes. Let’s assume your functions receive two million requests during the 24 hours of the sale event, while Provisioned Concurrency is enabled. The average function execution duration is 280 ms. You configure your function with 4,096 MB of memory on an x86 based processor, and set Provisioned Concurrency at seven. Your charges would be calculated as follows: Provisioned Concurrency charges: The Provisioned Concurrency price is $0.0000041667 per GB-s. Total period of time for which Provisioned Concurrency is enabled (seconds) = 24 hours * 3,600 seconds = 86,400 seconds Total concurrency configured (GB): 7 * 4096 MB / 1024 MB = 28 GB Total Provisioned Concurrency amount (GB-s) = 28 GB * 86,400 seconds = 2,419,200 GB-s Provisioned Concurrency charges = 2,419,200 GB-s * $0.0000041667 = $10.08 Compute charges while Provisioned Concurrency is enabled: The compute price is $0.0000097222 per GB-s. Total compute duration (seconds) = 2,000,000 * 280ms = 560,000 seconds Total compute (GB-s) = 560,000 seconds * 4096 MB / 1024 MB = 2,240,000 GB-s. Total compute charges = 2,240,000 GB-s * $0.0000097222 = $21.78 Monthly request charges: The monthly request price is $0.20 per 1 million requests Monthly request charges = 2M * $0.2/M = $0.40 Total monthly charges: Total charges = Provisioned Concurrency charges + Compute charges while Provisioned Concurrency is enabled + Request charges = $10.08 + $21.78 + $0.40 = $32.26 SnapStart Pricing SnapStart can improve startup performance from several seconds to as low as sub-second for latency sensitive applications. SnapStart works by snapshotting your function's initialized memory (and disk) state and caching this snapshot for low-latency access. When your function is subsequently invoked, Lambda resumes execution environments from this pre-initialized snapshot instead of initializing them from scratch, improving startup latency. A snapshot is created each time you publish a new version of your function with SnapStart enabled. You are charged for caching a snapshot over the period that your function version is active, for a minimum of 3 hours and per millisecond thereafter. The price depends on the amount of memory you allocate to your function. You are also charged each time Lambda resumes an execution environment by restoring your snapshot, with the price depending on the amount of memory you allocate to your function. SnapStart pricing does not apply to supported Java managed runtimes . Pricing Example: Enriching streaming telemetry with additional metadata Let’s say you are a logistics company with a fleet of vehicles in the field, each of which are enabled with sensors and 4G/5G connectivity to emit telemetry data into an Amazon Kinesis Data Stream. You want to use machine learning (ML) models you’ve developed to infer the health of the vehicle and predict when maintenance for particular components might be required. Suppose you have 10,000 vehicles in the field, each of which is emitting telemetry once an hour in a staggered fashion with sufficient jitter. You intend to perform this inference on each payload to ensure vehicles are scheduled promptly for maintenance and ensure optimal health of your vehicle fleet. Assume the ML model is packaged along with the function and is 512 MB in size. For inference, you’ve configured your function with 1 GB of memory, and billed execution duration is two seconds on average, on an x86 based processor. You maintain a single version of your function. For simplicity, let’s assume that 1% of all requests result in the creation of new execution environments. You notice that end-to-end processing takes several seconds for these 1% of requests. This is driven by your function initialization taking several seconds, because you import large software modules and the ML model during initialization. You want to reduce the end-to-end processing time for these requests, so you enable SnapStart on your function and publish a new version. Your charges would be calculated as follows: Request charges Per month, the vehicles will emit 10,000 * 24 * 31 = 7,440,000 messages which will be processed by the Lambda function. Monthly request charges: 7.44M * $0.20/million = $1.49 Monthly compute charges Per month, your function will be executed once per message for two seconds. Monthly compute duration (seconds): 7.44 million * 2 seconds = 14.88 million seconds Monthly compute (GB-s): 14.88M seconds * 1024 MB/1024 MB = 14.88M GB-s Monthly compute charges: 14.88M GB-s * $0.0000166667 = $248.00 SnapStart charges: Total time period over which function version is active (seconds): 24 hours * 31 days * 3600 seconds = 2,678,400 seconds Allocated function memory: 1024MB/1024MB -> 1 GB Total SnapStart Cache used: 1 GB * 2,678,400 s -> 2,678,400 GB-S SnapStart Cache charges: 2.68 million GB-s * $0.0000015046 = $4.03 Number of requests using SnapStart Restore: 1% of 7.44M = 74,400 Total SnapStart Restore used: 74,400 * 1 GB = 74,400 GB SnapStart Restore charges: 74,400 GB * $0.0001397998 = $10.4 Total SnapStart charges: SnapStart Cache charges + SnapStart Restore charges Total SnapStart charges: $4.03 + $10.4 = $14.43 Total monthly charges Total charges = Request charges + Compute charges + SnapStart charges Total charges = $1.49 + $248.00 + $14.43 = $263.92 Lambda HTTP Response Stream Pricing AWS Lambda functions can return an HTTP response stream when invoked via the InvokeWithResponseStream API or through a function URL using the ResponseStream invoke mode. HTTP response streaming can improve Time to First Byte performance and supports payloads larger than 6 MB. When using HTTP response streaming, you are charged for each GB written to the response stream by your function. You can stream the first 6 MB per request at no cost. All examples below are based on price in US East (N. Virginia). Pricing Example: Streaming Server Side Rendered Web Content Let’s assume you are a web application developer and are building a website that is server side rendered in a Lambda function. Your Lambda function dynamically generates HTML content based on the request and the results of multiple downstream service calls. Some of these calls can take a long time to return a response. To optimize your users’ page loading experience, you use Lambda’s HTTP response streaming capabilities to improve Time to First Byte performance by rendering the first chunks of HTML in the browser as soon as your function generates them. For simplicity, let’s assume your application processes three million requests per month. Let’s also assume you have exhausted the 100 GB of response streaming included in the AWS free tier. The average function duration is 500ms. You have configured your function with 1536 MB of memory on an x86 based processor. The average payload size per request is 100 KB for the first two million requests per month, and 7 MB for the last million requests per month. The example calculation assumes 1 GB = 1,024 MB. Your charges would be calculated as follows: Monthly compute charges The monthly compute price is $0.0000166667 per GB-s and the free tier provides 400,000 GB-s. Total compute (seconds) = 3 million * 500ms = 1,500,000 seconds Total compute (GB-s) = 1,500,000 * 1536MB/1024 MB = 2,250,000 GB-s Total compute – Free tier compute = monthly billable compute GB-s 2,250,000 GB-s – 400,000 free tier GB-s = 1,850,000 GB-s Monthly compute charges = 1,850,000 * $0.0000166667 = $30.83 Monthly request charges The monthly request price is $0.20 per one million requests and the free tier provides 1 million request per month. Total requests – Free tier requests = monthly billable requests 3 million requests – 1 million free tier requests = 2 million monthly billable requests Monthly request charges = 2M * $0.2/M = $0.40 Processed bytes charges The monthly bytes streamed price is $0.008 per GB streamed and the free tier provides 100 GB per month. The first 6 MB streamed per request are also free. Free bytes streamed (GB) = 2 million requests * 100 KB = 190.7 GB Since 100 KB < 6 MB per request, the 190.7 GB streamed are free. Chargeable bytes streamed (GB) = 1 million requests * (7 MB – 6 MB) = 976.56 GB Monthly bytes streamed charges = 976.56 GB * $0.008 = $7.81 Total monthly charges: Total charges = Compute charges + Request charges + Bytes Streamed charges = $30.83 + $0.40 + $7.81 = $39.04 per month Provisioned Mode for Event Source Mapping (ESM) Pricing Provisioned Mode for ESM allows you to optimize the throughput of your ESM by allocating a minimum and maximum number of resources called event pollers, and autoscaling between configured minimum and maximum limits. An event poller is the configurable resource that underpins an ESM in Provisioned Mode. Pricing is based on the provisioned minimum event pollers, and the event pollers consumed during autoscaling. Charges are calculated using a billing unit called Event Poller Unit (EPU). You pay for the number and duration of EPUs used, measured in Event-Poller-Unit-hours. SQS ESM: An EPU supports one event poller, each providing up to 1 MB/s throughput. Each SQS ESM requires a minimum of 2 event pollers. MSK or Self-managed Kafka (SMK) ESM: Each EPU supports up to 20 MB/s throughput capacity for event polling, with a default of 10 event pollers. Each event poller can scale up to 5 MB/s throughput. The number of event pollers allocated on an EPU depends on the compute capacity consumed by each event poller. You can group multiple ESMs within the same Amazon VPC to share EPU capacity and costs. To learn about Provisioned mode for Kafka ESM, read the documentation . Data Transfer: You are billed at standard AWS data transfer rates . Duration: Pricing is calculated per second, with a 1-minute minimum. Pricing Example 1: Example: Real-time streaming data analysis using Kafka Example: Real-time streaming data analysis using Kafka Suppose you are a global customer contact center solution provider and have pipelines that emit metadata related to call experience to Amazon MSK (Kafka) topics for real-time analysis. Since the traffic can be spiky and unpredictable, you want to use the Provisioned Mode for ESM to fine-tune the performance of your ESM. Suppose your Lambda function that processes these messages is configured with 1,024MB memory for x86 processor, and experiences 1M invocations per day with 2 seconds average duration. Assume that you activated Provisioned Mode for your ESM with the default 1 event poller, and your ESM scales up to consume 800 EPU-hours per month in US East (N. Virginia). Monthly compute charges The monthly compute price is $0.0000166667 per GB-s and the free tier provides 400,000 GB-s Total compute (seconds) = 1,000,000 * 30 * 2 seconds = 60,000,000 seconds Total compute (GB-s) = 60,000,000 * 1024MB/1024 = 60,000,000 GB-s Total compute – Free tier compute = monthly billable compute GB-s 60,000,000 GB-s – 400,000 free tier GB-s = 59,600,000 GB-s Monthly compute charges = 59,600,000 * $0.0000166667 = $993.3 Monthly request charges The monthly request price is $0.20 per 1 million requests. Monthly request charges = 60M requests * $0.20 = $12.00 Monthly Provisioned Mode for ESM charges EPU charges = 800 EPU-hours * $0.185 = $148 Monthly Provisioned Mode for ESM charges = $148 Total charges Total charges = Compute charges + Request charges + Provisioned Mode for ESM charges Total charges = $993.3 + $12 + $148 = $1,153.3 Pricing Example 2 Real-time event processing using Amazon SQS Example: Real-time event processing using Amazon SQS Suppose you are a financial services firm processing market data feeds and executing financial transactions using event-driven micro-services for real-time customer facing financial application. Since the traffic can be spiky and unpredictable, you want to use the Provisioned Mode for SQS ESM to fine-tune the performance of your ESM. Suppose your Lambda function that processes these events is configured with 1,024MB memory for x86 processor, and experiences 1M invocations per day with 1 seconds average duration. You have maximum event TPS of 100 which you want to process with maximum latency of 0.2 second. To achieve this latency performance, you have activated Provisioned mode for your SQS ESM with 10 minimum event pollers, and your ESM scales up to consume 8000 EPU-hours per month in US EAST (N. Virginia) region to handle your spiky low latency traffic. Monthly compute charges The monthly compute price is $0.0000166667 per GB-s Total compute (seconds) = 1,000,000 * 30 * 1 seconds = 30,000,000 seconds Total compute (GB-s) = 30,000,000 * 1024MB/1024 = 30,000,000 GB-s Total compute = monthly billable compute GB-s * $0.0000166667 Monthly compute charges = 30,000,000 * $0.0000166667 = $500 Monthly request charges The monthly request price is $0.20 per 1 million requests Monthly request charges = 30M requests * $0.20 = $6 Monthly Provisioned Mode for SQS ESM charges The EPU price is $0.00925 per EPU-hour EPU charges = 8000 EPU-hours * $0.00925 = $74 Monthly Provisioned Mode for ESM charges = $74 Total charges Total charges = Compute charges + Request charges + Provisioned Mode for ESM charges Total charges = $500 + $6 + $74 = $580 Pricing Example 3 Example: Real-time streaming data analysis using multiple Kafka ESMs Suppose you are a global customer contact center solution provider and have pipelines that emit metadata related to call experience to tens of Amazon MSK (Kafka) topics, each ingesting messages from your various products. Each topic is ingesting with maximum 500 messages per second, with average message size of 3 KB, and peak throughput of 1.5 MB/s. Since the traffic can be spiky and unpredictable, you want to use the Provisioned Mode for ESM to fine-tune the performance of your ESM. Suppose your Lambda function that processes these messages is configured with 1,024MB memory for x86 processor, and experiences 1M invocations per day with 0.2 seconds average duration. You created 10 Kafka ESMs for event processing with <1.5 MB/s of throughput per ESM, which you decided to group them under the same Poller group to optimize the costs. Assume that you activated Provisioned Mode for your ESM with the default 1 event poller, and you are using all your 10 ESMs within the same poller group in US East (N. Virginia). Monthly compute charges The monthly compute price is $0.0000166667 per GB-s and the free tier provides 400,000 GB-s Total compute (seconds) = 1,000,000 * 30 * 0.2 seconds = 6,000,000 seconds Total compute (GB-s) = 6,000,000 * 1024MB/1024 = 6,000,000 GB-s Total compute (GB-s) for all 10 ESMs = 6,000,000 GB-s * 10 = 60,000,000 GB-s Monthly compute charges = 60,000,000 * $0.0000166667 = $1,000 Monthly request charges The monthly request price is $0.20 per 1 million requests. Total monthly requests for all 100 ESMs = 1 million * 30 days * 10 ESMs = 300M requests Monthly request charges = 300M requests * $0.20 = $60.00 Monthly Provisioned Mode for ESM charges EPU-hours price is $0.185/hour and supports 10 event pollers per EPU. Total events pollers per hour = 1 event poller * 10 ESMs = 10 event pollers EPU used = 10 event pollers used / 10 event pollers supported per EPU = 1 EPU Total EPUs per month = 1 EPU * 720 hours per month = 720 EPU-hours EPU charges = 720 EPU-hours * $0.185 = $133.2 Monthly Provisioned Mode for ESM charges = $133.2 Total charges Total charges = Compute charges + Request charges + Provisioned Mode for ESM charges Total charges = $1,000 + $60 + $133.2 = $1,193.2 per month for 10 ESMs Monthly costs per ESM = $1,193.2 / 10 = $119.3 per month per ESM Data Transfer & Other Charges Data Transfer Data transferred “in” to and “out” of your AWS Lambda functions , from outside the region the function executed, will be charged at the Amazon EC2 data transfer rates as listed under " Data transfer ". Data transfer with AWS Lambda Functions is free in the same AWS Region between the following services: Amazon Simple Storage Service (S3), Amazon Glacier, Amazon DynamoDB, Amazon Simple Email Service (SES), Amazon Simple Queue Service (SQS), Amazon Kinesis, Amazon Elastic Container Registry (ECR), Amazon Simple Notification Service (SNS), Amazon Elastic File System (EFS), and Amazon SimpleDB. The usage of Amazon Virtual Private Cloud (VPC) or VPC peering, with AWS Lambda functions will incur additional charges as explained on the Amazon Elastic Compute Cloud (EC2) on-demand pricing page . A VPC peering connection is a networking connection between two VPCs that enables you to route traffic between them using private IPv4 addresses or IPv6 addresses . Additional Charges You may incur additional charges if your Lambda function utilizes other AWS services or transfers data. For example, if your Lambda function reads and writes data to or from Amazon S3, you will be billed for the read/write requests and the data stored in Amazon S3 . For details on AWS service pricing, see the pricing section of the relevant AWS service detail pages. Lambda@Edge Pricing Lambda@Edge functions are metered at a granularity of 1ms Pricing Example: If your Lambda@Edge function executed 10 million times in one month, and it ran for 10ms each time, your charges would be calculated as follows: If your Lambda@Edge function executed 10 million times in one month, and it ran for 10ms each time, your charges would be calculated as follows: Monthly compute charges The monthly compute price is $0.00000625125 per 128MB-second Total compute (seconds) = 10M * (0.01sec) = 100,000 seconds Monthly compute charges = 100,000 * $0.00000625125 = $0.63 Monthly request charges The monthly request price is $0.60 per 1 million requests.. Monthly request charges = 10M * $0.6/M = $6.00 Total monthly charges Total charges = Compute charges + Request charges = $0.63 + $6.00 = $6.63 per month Additional pricing resources AWS Pricing Calculator Easily calculate your monthly costs with AWS Get Pricing Assistance Contact AWS specialists to get a personalized quote Get started with AWS Lambda Feature Find out how AWS Lambda works Explore AWS Lambda Features Documentation Explore hands-on training Check out getting started tutorials Getting started Connect with an expert Explore support options Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:29:30 |
https://l.facebook.com/l.php?u=https%3A%2F%2Fwww.instagram.com%2F&h=AT1HefWIJJOeGFP-7wD_crWa_zBVGaYGm5mFYd453DMCYJhcQInTHAHjJLeMkz5W6wKjKUsDM0b-dJz0ZNz-f-w_r3pwONU4YYPIrnyczJkhWIH7tro9hS0GCA0fIWvoNW0PBQsC48RgEsGM | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:29:30 |
https://www.atlassian.com/fr/software/loom/ai | Loom AI | Atlassian Close Afficher cette page dans votre langue ? Toutes les langues Sélectionner votre langue 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Essayer gratuitement Fonctionnalités Explorer les fonctionnalités Notes de réunion Enregistreur d'écran Captures d'écran Loom AI Modification Back Solutions Équipes Cas d'usages Taille de l'entreprise Équipes Ventes Marketing Design Support Gestion de produit Ingénierie Cas d'usages Loom + Jira Loom + Confluence Taille de l'entreprise Enterprise Back Ressources Tarifs Plus + Moins - Essayer gratuitement Back Essayer gratuitement Lancez l'enregistrement, Loom AI fera le reste Partagez des vidéos professionnelles sans lever le petit doigt. Loom AI améliore automatiquement votre vidéo et transforme votre script en document. Essayer gratuitement Loom AI Enregistrez et partagez vos vidéos 60 % plus rapidement Loom AI affine, monte et génère automatiquement un document textuel pour votre vidéo Des réunions, mais moins de travail Laissez Loom AI prendre des notes et enregistrer les éléments d'action à entreprendre, pour continuer à travailler pendant et après les réunions. Accélérez la création et la livraison grâce aux workflows alimentés par l'IA Des documents prêts à partager en un seul clic. Les workflows de Loom AI vous aident à accomplir vos tâches importantes rapidement. Essayer gratuitement Loom AI Rédiger un document Documentez votre travail pour faire évoluer les connaissances Alignez-vous plus vite et boostez vos sprints grâce aux workflows alimentés par l'IA qui transforment vos vidéos en descriptions de pull request, SOP, et bien plus. Créer un ticket Signalez des bugs dans Jira ou Linear en quelques clics Gagnez du temps sur les signalements de bugs et les tickets. Loom capture le contenu de votre vidéo et fournit les informations essentielles pour Jira et Linear. ÉCRIRE UN MESSAGE Ajoutez du contexte automatiquement à l'aide de votre lien Loom Loom génère instantanément des messages écrits à partager avec votre lien vidéo, que ce soit par DM ou par e-mail. Des messages toujours délivrés avec Loom AI Fonctionnalités Vidéos avec Loom AI Vidéos sans Loom AI Titres Vidéos avec Loom AI Généré automatiquement Vidéos sans Loom AI Manuelle Résumés Vidéos avec Loom AI Généré automatiquement Vidéos sans Loom AI Manuelle Chapitres Vidéos avec Loom AI Généré automatiquement Vidéos sans Loom AI Manuelle Tâches Vidéos avec Loom AI Généré automatiquement Vidéos sans Loom AI Manuelle Intégrer un lien CTA Vidéos avec Loom AI Généré automatiquement Vidéos sans Loom AI Manuelle Suppression des tics de langage Vidéos avec Loom AI Généré automatiquement Vidéos sans Loom AI Non disponible Suppression des blancs Vidéos avec Loom AI Généré automatiquement Vidéos sans Loom AI Non disponible Transformez votre vidéo en document Vidéos avec Loom AI Généré automatiquement Vidéos sans Loom AI Non disponible Transformez votre vidéo en ticket Jira ou Linear Vidéos avec Loom AI Généré automatiquement Vidéos sans Loom AI Non disponible Transformez votre vidéo en message ou e-mail Vidéos avec Loom AI Généré automatiquement Vidéos sans Loom AI Non disponible Nous parlons votre langue Disponible en plus de 50 langues, Loom AI améliore et transforme votre vidéo en un document en fonction de la langue dans laquelle vous l'enregistrez. Je créais une vidéo pour un hackathon et j'ai décidé d'essayer les workflows de Loom AI. J'ai littéralement dit « WAHOU » après ma première utilisation. Il a réussi à capturer les étapes précises de la vidéo dans un document en (SEULEMENT) 20 secondes. C'est impressionnant. Un vrai plongeon dans le futur. Responsable de la sécurité et de la confiance d'une entreprise technologique Des nouvelles fonctionnalités seront bientôt disponibles Loom AI n'en est qu'à ses débuts. Chaque jour, nous imaginons et travaillons sur de nouvelles fonctionnalités puissantes ! Bientôt disponible Outils de développement de capture automatique Ajoutez instantanément les journaux de console, les informations de votre navigateur et bien plus à votre ticket Jira ou Linear Bientôt disponible Voix et avatars de l'IA La synthèse vocale et les avatars de l'IA vous permettent de créer des vidéos personnalisées à grande échelle sans avoir à réenregistrer. Bientôt disponible Connexion à Confluence Une fois que les workflows Loom AI ont transformé votre vidéo en document, ouvrez-le dans votre outil de collaboration ou de gestion de projet. Bientôt disponible Ajoutez automatiquement des visuels aux guides détaillés Enregistrez un processus et Loom AI ajoute des clips vidéo, des GIF ou des captures d'écran pour chaque étape. Ce que pensent les clients 96 % des utilisateurs de Loom déclarent que les fonctionnalités de la suite IA sont déjà très ou extrêmement utiles pour leurs workflows Loom AI permet non seulement d'économiser du temps et des efforts, mais rend également vos vidéos plus accessibles et captivantes pour votre public. 🎥 ✨ ryan carr Fondateur de Tailwind FAQ Comment acheter Loom AI ? L'administrateur de votre compte peut passer à l'offre Business + AI ou Enterprise dans les paramètres de votre espace de travail, sous l'onglet « Forfait et facturation ». Puis-je essayer Loom AI gratuitement ? Oui, vous pouvez essayer notre offre Business + AI gratuitement pendant 14 jours après votre inscription à Loom. Pourquoi passer à Loom AI ? De nombreuses entreprises ajoutent de l'IA à leurs produits. Chez Loom, notre priorité n o 1 est de créer des fonctionnalités d'IA qui répondent à notre mission, faciliter la communication. La suite Loom AI propose des fonctionnalités actuelles et à venir, conçues pour vous aider à faire ce qui suit : Travailler plus rapidement : 67 % des utilisateurs ne modifient pas le titre généré automatiquement, ce qui permet de gagner en efficacité sans investir de temps supplémentaire . La suite Loom AI réduit le temps passé à préparer et partager les Looms après l'enregistrement, vous permettant ainsi d'envoyer rapidement une vidéo soignée et de haute qualité. Augmenter la productivité : 73 % des personnes ont déclaré que c'était « très ou extrêmement utile » pour leurs workflows actuels . La suite Loom AI vous évite d'avoir à réenregistrer les Looms afin que vous puissiez faire de votre mieux pour la première prise. Communiquer efficacement : 18 % d'engagement des utilisateurs disposant de droits en lecture en plus . La suite Loom AI ajoute du contexte instantanément et automatiquement (titre, résumé, chapitres et tâches) à votre contenu pour que votre message soit clair et engager les utilisateurs disposant de droits en lecture. Comment sont utilisées mes données ? OpenAI reçoit les données de transcription sous forme de fichiers texte afin de générer des titres et des résumés. OpenAI ne reçoit ni vidéo ni audio complet. Nous n'envoyons des données qu'à des systèmes tiers de confiance soumis à des contrôles de confidentialité et de sécurité stricts. Nos sous-traitants de données tiers font l'objet d'accords appropriés avec Loom et/ou ses utilisateurs pour sécuriser et protéger la confidentialité des données. De plus, nous avons signé des accords de traitement des données (DPA) avec nos sous-traitants de données. Vous trouverez des détails ainsi que la liste des sous-traitants de données de Loom ici . Les termes d'utilisation relatifs à l'IA de Loom ici. Quelles langues sont prises en charge par Loom AI ? Les fonctionnalités d'auto-amélioration de Loom AI (comme les titres automatiques, les résumés, etc.) sont générées en plus de 50 langues. Notre nouvelle fonctionnalité de workflows alimentée par l'IA génère actuellement de la documentation uniquement en anglais. D'autres langues seront bientôt prises en charge par les workflows alimentés par l'IA. Loom vous suit partout Pour Mac, Windows, iOS et Android Télécharger Loom gratuitement Entreprise Carrières Événements Blogs Relations avec les investisseurs Atlassian Foundation Kit pour la presse Nous contacter Index de l'égalité professionnelle produits Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Voir tous les produits Ressources Support technique Achats et licences Communauté Atlassian Base de connaissances Marketplace Mon compte Créer un ticket de support Apprendre Partenaires Formation et certification Documentation Ressources développeurs Services Enterprise Découvrir toutes les ressources Copyright © 2025 Atlassian Politique de confidentialité Conditions Mentions légales Choisir la langue Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/ja_jp/lambda/latest/dg/runtimes-extensions-api.html#runtimes-extensions-api-failure | Lambda 拡張機能 API を使用した拡張機能の作成 - AWS Lambda Lambda 拡張機能 API を使用した拡張機能の作成 - AWS Lambda ドキュメント AWS Lambda デベロッパーガイド Lambda 実行環境のライフサイクル 拡張機能 API リファレンス Lambda 拡張機能 API を使用した拡張機能の作成 Lambda 関数の作成者は、拡張機能を使用して、Lambda を、モニタリング、可観測性、セキュリティ、およびガバナンスのための任意のツールと統合します。関数作成者は、AWS、 AWS パートナー 、およびオープンソースプロジェクトの拡張機能を使用できます。拡張機能の使用の詳細については、AWS Lambda コンピューティングブログの AWS 拡張機能の紹介 を参照してください。このセクションでは、Lambda Extensions API、Lambda 実行環境ライフサイクル、および Lambda Extensions API リファレンスを使用する方法を説明します。 拡張機能の作成者は、Lambda Extensions API を使用して Lambda 実行環境 に深く統合することができます。拡張機能は、関数および実行環境のライフサイクルイベントに登録できます。これらのイベントに対応して、新しいプロセスを開始し、ロジックを実行し、Lambda ライフサイクルのすべてのフェーズ (初期化、呼び出し、およびシャットダウン) を制御し、これらに参加することができます。さらに、 Runtime Logs API を使用して、ログのストリームを受信できます。 拡張機能は、実行環境で独立したプロセスとして実行され、関数の呼び出しが完全に処理された後も引き続き実行できます。拡張機能はプロセスとして実行されるため、関数とは異なる言語で記述できます。コンパイルされた言語を使用して拡張機能を実装することをお勧めします。この場合、拡張機能は、サポートされているランタイムと互換性のある自己完結型のバイナリです。すべての Lambda ランタイム は拡張機能をサポートします。コンパイルされていない言語を使用する場合は、必ず互換性のあるランタイムを拡張機能に含めてください。 Lambda は 内部拡張機能 もサポートしています。内部拡張機能は、ランタイムプロセスで別のスレッドとして実行されます。ランタイムは、内部拡張を開始および停止します。Lambda 環境と統合する別の方法は、言語固有の 環境変数とラッパースクリプト を使用することです。これらを使用して、ランタイム環境を設定し、ランタイムプロセスの起動動作を変更できます。 関数に拡張機能を追加するには、次の 2 つの方法があります。 .zip ファイルアーカイブ としてデプロイされた関数では、拡張機能を レイヤー としてデプロイします。コンテナイメージとして定義された関数の場合は、コンテナイメージに 拡張機能 を追加します。 注記 拡張機能とラッパースクリプトの例については、AWS Lambda サンプル GitHub リポジトリの 「 AWS拡張 」を参照してください。 トピック Lambda 実行環境のライフサイクル 拡張機能 API リファレンス Lambda 実行環境のライフサイクル 実行環境のライフサイクルには、以下のフェーズが含まれています。 Init : このフェーズ中、Lambda は、設定したリソースを使用して実行環境を作成またはフリーズ解除し、関数コードとすべてのレイヤーをダウンロードして、拡張機能とランタイムを初期化し、関数の初期化コード (メインハンドラーの外部にあるコード) を実行します。 Init フェーズは、最初の呼び出し中か、 プロビジョニング済みの同時実行 を有効にしている場合は関数呼び出しの前に、発生します。 Init フェーズは、 Extension init 、 Runtime init 、 Function init の 3 つのサブフェーズに分割されます。これらのサブフェーズでは、関数コードが実行される前に、すべての拡張機能とランタイムがそのセットアップタスクを完了します。 Invoke : このフェーズでは、Lambda は関数ハンドラーを呼び出します。関数が実行され、完了すると、Lambda は、別の関数呼び出しを処理する準備をします。 Shutdown : このフェーズは、Lambda 関数が一定期間呼び出しを受け取らなかった場合にトリガーされます。 Shutdown フェーズでは、Lambda はランタイムをシャットダウンし、拡張機能にアラートを出してそれらを完全に停止させた後、環境を削除します。Lambda は、各拡張機能に Shutdown イベントを送信します。これにより、環境がシャットダウンされようとしていることを各拡張機能に伝えます。 各フェーズは、Lambda からランタイム、および登録されたすべての拡張機能へのイベントから始まります。ランタイムと各拡張機能は、 Next API リクエストを送信することで完了を示します。Lambda は、各プロセスが完了して保留中のイベントがなくなると、実行環境をフリーズします。 トピック 初期化フェーズ 呼び出しフェーズ シャットダウンフェーズ アクセス許可と設定 障害処理 拡張機能のトラブルシューティング 初期化フェーズ Extension init フェーズの間、各拡張機能モジュールは、イベントを受信するために Lambda に登録されている必要があります。Lambda は、拡張機能がブートストラップシーケンスを完了していることを検証するために、拡張機能の完全なファイル名を使用します。したがって、各 Register API コールには、拡張機能の完全なファイル名を持つ Lambda-Extension-Name ヘッダーを含める必要があります。 1 つの関数に最大 10 個の拡張機能を登録できます。この制限は、 Register API コールを通じて適用されます。 各拡張機能が登録されると、Lambda は Runtime init フェーズを開始します。ランタイムプロセスは functionInit を呼び出して Function init フェーズを開始します。 Init フェーズはランタイム後に完了します。登録された各拡張機能は、 Next API リクエストを送信することで完了を示します。 注記 拡張機能は、 Init フェーズの任意の時点で初期化を完了できます。 呼び出しフェーズ Next API リクエストに応答して Lambda 関数が呼び出されると、Lambda は、ランタイム、および Invoke イベントに登録されている各拡張機能に、 Invoke イベントを送信します。 呼び出し中、外部拡張機能は関数と並行して実行されます。また、関数が完了した後も、引き続き実行されます。これにより、診断情報をキャプチャしたり、ログ、メトリクス、トレースを任意の場所に送信したりできます。 ランタイムから関数応答を受信した後、拡張機能がまだ実行中であっても、Lambda はクライアントに応答を返します。 Invoke フェーズはランタイム後に終了します。すべての拡張機能は、 Next API リクエストを送信することによって完了を示します。 イベントペイロード ：ランタイムに送信されるイベント（および Lambda 関数）は、リクエスト、ヘッダー ( RequestId など) およびペイロード全体を保持します。各拡張機能に送信されるイベントには、イベントの内容を説明するメタデータが含まれます。このライフサイクルイベントには、イベントのタイプ、関数のタイムアウト時間 ( deadlineMs ) 、 requestId 、呼び出された関数の Amazon リソースネーム (ARN) 、およびトレースヘッダーが含まれます。 関数イベント本体にアクセスする拡張機能は、その拡張機能と通信するインランタイム SDK を使用できます。関数のデベロッパーは、関数が呼び出されたときにインランタイム SDK を使用して、拡張機能にペイロードを送信します。 ペイロードの例を次に示します。 { "eventType": "INVOKE", "deadlineMs": 676051, "requestId": "3da1f2dc-3222-475e-9205-e2e6c6318895", "invokedFunctionArn": "arn:aws:lambda:us-east-1:123456789012:function:ExtensionTest", "tracing": { "type": "X-Amzn-Trace-Id", "value": "Root=1-5f35ae12-0c0fec141ab77a00bc047aa2;Parent=2be948a625588e32;Sampled=1" } } 所要時間の制限 : 関数のタイムアウト設定では、 Invoke フェーズ全体の所要時間を制限します。例えば、関数のタイムアウトを 360 秒に設定した場合、関数とすべての拡張機能は 360 秒以内に完了する必要があります。独立した呼び出し後フェーズはないことに注意してください。所要時間はランタイムおよびすべての拡張機能の呼び出しが完了するまでの合計時間であり、関数およびすべての拡張機能の実行が終了するまで計算されません。 パフォーマンスの影響と拡張機能のオーバーヘッド : 拡張機能は、関数のパフォーマンスに影響を与える可能性があります。拡張機能の作成者は、拡張機能のパフォーマンスへの影響を制御する必要があります。例えば、拡張機能でコンピューティング負荷の高い操作を実行した場合、拡張機能と関数コードで同じ CPU リソースを共有するため、関数の実行時間が長くなります。さらに、関数呼び出しの完了後に拡張機能が広範な操作を実行する場合、すべての拡張機能が完了を示すまで Invoke フェーズが継続するため、関数の実行時間が長くなります。 注記 Lambda は、関数のメモリ設定に比例して CPU パワーを割り当てます。関数と拡張機能のプロセスが同じ CPU リソースで競合するため、メモリ設定が小さい場合、実行時間と初期化時間が長くなることがあります。実行時間と初期化時間を短縮するには、メモリ設定を引き上げてみてください。 Invoke フェーズで拡張機能によって発生したパフォーマンスへの影響を確認できるように、Lambda は PostRuntimeExtensionsDuration メトリクスを出力します。このメトリクスでは、ランタイム Next API リクエストから最後の拡張機能の Next API リクエストまでの累積時間が測定されます。使用されるメモリの増加を測定するには、 MaxMemoryUsed メトリクスを使用します。関数のメトリクスの詳細については、「 Lambda での CloudWatch メトリクスの使用 」を参照してください。 関数のデベロッパーは、異なるバージョンの関数を並行して実行して、特定の拡張機能の影響を把握することができます。拡張機能の作成者は、関数のデベロッパーが適切な拡張機能を選択しやすくするために、予想されるリソース消費を公開することをお勧めします。 シャットダウンフェーズ Lambda は、ランタイムをシャットダウンしようとする際に、登録された各外部拡張機能に Shutdown を送信します。拡張機能は、この時間を最終的なクリーンアップタスクに使用できます。 Shutdown イベントは Next API リクエストに応答して送信されます。 所要時間の制限 : Shutdown フェーズの最大所要時間は、登録された拡張機能の設定によって異なります。 0 ms – 登録された拡張機能を持たない関数 500 ms - 登録された内部拡張機能を持つ関数 2000 ms - 登録された外部拡張機能を 1 つ以上持つ関数 ランタイムまたは拡張機能が制限内で Shutdown イベントに応答しない場合、Lambda は SIGKILL の通知を使用してプロセスを終了します。 イベントペイロード : Shutdown イベントには、シャットダウンの理由と残り時間 (ミリ秒単位) が含まれます。 shutdownReason には次の値が含まれています。 SPINDOWN - 正常なシャットダウン TIMEOUT - 所要時間の制限がタイムアウトしました FAILURE - エラー状態 ( out-of-memory イベントなど) { "eventType": "SHUTDOWN", "shutdownReason": "reason for shutdown", "deadlineMs": "the time and date that the function times out in Unix time milliseconds" } アクセス許可と設定 拡張機能は、Lambda 関数と同じ実行環境で実行されます。拡張機能は、CPU、メモリ、 /tmp ディスクストレージなどのリソースも関数と共有します。さらに、関数と同じ AWS Identity and Access Management (IAM) ロールとセキュリティコンテキストが使用されます。 ファイルシステムとネットワークアクセス許可 : 拡張機能は、関数ランタイムと同じファイルシステムおよびネットワーク名の名前空間で実行されます。つまり、拡張機能は関連するオペレーティングシステムと互換性がある必要があります。拡張機能で追加の 送信ネットワークトラフィック ルールが必要な場合は、これらのルールを関数の設定に適用する必要があります。 注記 関数コードディレクトリは読み取り専用であるため、拡張機能は関数コードを変更できません。 環境変数 : 拡張機能は、関数の 環境変数 にアクセスできます。ただし、ランタイムプロセスに固有の次の変数は除きます。 AWS_EXECUTION_ENV AWS_LAMBDA_LOG_GROUP_NAME AWS_LAMBDA_LOG_STREAM_NAME AWS_XRAY_CONTEXT_MISSING AWS_XRAY_DAEMON_ADDRESS LAMBDA_RUNTIME_DIR LAMBDA_TASK_ROOT _AWS_XRAY_DAEMON_ADDRESS _AWS_XRAY_DAEMON_PORT _HANDLER 障害処理 初期化の失敗 : 拡張機能が失敗した場合、Lambda は実行環境を再起動して一貫した動作を適用し、拡張機能のフェイルファストを推奨します。また、お客様によっては、拡張機能が、ログ記録、セキュリティ、ガバナンス、テレメトリ収集などのミッションクリティカルなニーズを満たす必要があります。 呼び出しの失敗 （メモリ不足、関数のタイムアウトなど）： 拡張機能はランタイムとリソースを共有するため、メモリが消耗した場合に影響を受けます。ランタイムが失敗すると、すべての拡張機能とランタイム自体が Shutdown フェーズに参加します。さらにランタイムは、現在の呼び出しの一部として、または遅延された再初期化メカニズムを通じて、自動的に再起動されます。 Invoke 中に障害が発生した場合 (関数のタイムアウトやランタイムエラーなど)、 Lambda サービスはリセットを実行します。リセットは Shutdown イベントのように動作します。まず、Lambda はランタイムをシャットダウンし、登録された各外部拡張機能に Shutdown イベントを送信します。イベントには、シャットダウンの理由が含まれます。この環境が新しい呼び出しに使用される場合、拡張機能とランタイムは次の呼び出しの一部として再初期化されます。 前示の図の詳細については、「 呼び出しフェーズ中の失敗 」を参照してください。 拡張機能のログ : Lambda は、拡張機能のログ出力を CloudWatch Logs に送信します。また Lambda は、 Init 中に各拡張機能に対して追加のログイベントも生成します。ログイベントは、成功時には名前と登録設定 (event、config) を記録し、失敗時には失敗理由を記録します。 拡張機能のトラブルシューティング Register リクエストが失敗した場合は、 Lambda-Extension-Name API コールの Register ヘッダーに拡張機能の完全なファイル名が含まれていることを確認します。 内部拡張機能に対する Register リクエストが失敗した場合は、そのリクエストが Shutdown イベントに登録されていないことを確認します。 拡張機能 API リファレンス 拡張機能 API バージョン 2020-01-01 の OpenAPI 仕様は、こちらから入手できます: extensions-api.zip API エンドポイントの値は、 AWS_LAMBDA_RUNTIME_API 環境変数から取得できます。 Register リクエストを送信するには、各 API パスの前にプレフィックス 2020-01-01/ を使用します。以下に例を示します。 http://$ { AWS_LAMBDA_RUNTIME_API}/2020-01-01/extension/register API メソッド 登録 次へ 初期化エラー 終了エラー 登録 Extension init 中、すべての拡張機能は、イベントを受信するために Lambda に登録される必要があります。Lambda は、拡張機能がブートストラップシーケンスを完了していることを検証するために、拡張機能の完全なファイル名を使用します。したがって、各 Register API コールには、拡張機能の完全なファイル名を持つ Lambda-Extension-Name ヘッダーを含める必要があります。 内部拡張機能はランタイムプロセスによって開始および停止されるため、 Shutdown イベントへの登録は許可されません。 パス – /extension/register メソッド - POST リクエストヘッダー Lambda-Extension-Name - 拡張機能の完全なファイル名。必須: はい。タイプ: 文字列。 Lambda-Extension-Accept-Feature – これを使用して、登録時にオプションの拡張機能を指定します。必須: いいえ。型: カンマで区切られた文字列。この設定を使用して指定できる機能: accountId – これを指定した場合は、拡張機能登録レスポンスに、拡張機能を登録している Lambda 関数に関連付けられたアカウント ID が含まれます。 リクエストボディのパラメータ events - 登録するイベントの配列。必須: いいえ。型: 文字列の配列 有効な文字列: INVOKE 、 SHUTDOWN 。 レスポンスヘッダー Lambda-Extension-Identifier - それ以降のすべてのリクエストに必要な、生成された一意のエージェント識別子 (UUID 文字列)。 レスポンスコード 200 - レスポンス本文には、関数名、関数バージョン、およびハンドラー名が含まれます。 400 – Bad Request 403 – Forbidden 500 – Container error 回復不能な状態。拡張機能はすぐに終了する必要があります。 例 リクエストボディの例 { 'events': [ 'INVOKE', 'SHUTDOWN'] } 例 レスポンスの例 { "functionName": "helloWorld", "functionVersion": "$LATEST", "handler": "lambda_function.lambda_handler" } 例 オプションの accountId 機能が含まれたレスポンスボディの例 { "functionName": "helloWorld", "functionVersion": "$LATEST", "handler": "lambda_function.lambda_handler", "accountId": "123456789012" } 次へ 拡張機能は Next API リクエストを送信して、次のイベント ( Invoke イベントまたは Shutdown イベント) を受信します。レスポンス本文にはペイロードが含まれます。ペイロードは、イベントデータを含む JSON ドキュメントです。 拡張機能は、新しいイベントを受信する準備ができていることを示す Next API リクエストを送信します。これはブロック呼び出しです。 拡張機能は一定期間中断される可能性があるため、返されるイベントが発生するまで、GET 呼び出しにタイムアウトを設定しないでください。 パス – /extension/event/next メソッド - GET リクエストヘッダー Lambda-Extension-Identifier - 拡張機能の一意の識別子 (UUID 文字列)。必須: はい。型: UUID 文字列。 レスポンスヘッダー Lambda-Extension-Event-Identifier – イベントの一意の識別子 (UUID 文字列)。 レスポンスコード 200 - レスポンスには、次のイベント ( EventInvoke または EventShutdown ) に関する情報が含まれます。 403 – Forbidden 500 – Container error 回復不能な状態。拡張機能はすぐに終了する必要があります。 初期化エラー 拡張機能はこのメソッドを使用して、初期化エラーを Lambda に報告します。拡張機能が登録後に初期化に失敗した場合に呼び出します。Lambda がエラーを受信すると、それ以降の API コールは成功しません。拡張機能は、Lambda からの応答を受信した後に終了する必要があります。 パス – /extension/init/error メソッド - POST リクエストヘッダー Lambda-Extension-Identifier - 拡張機能の一意の識別子。必須: はい。型: UUID 文字列。 Lambda-Extension-Function-Error-Type - 拡張機能が検出したエラータイプ。必須: はい。このヘッダーは、文字列値で構成されています。Lambda はどのような文字列でも受け入れますが、形式は <category.reason> にすることが推奨されます。例: Extension.NoSuchHandler Extension.APIKeyNotFound Extension.ConfigInvalid Extension.UnknownReason リクエストボディのパラメータ ErrorRequest - エラーに関する情報。必須: いいえ。 このフィールドは、次の構造を持つ JSON オブジェクトです。 { errorMessage: string (text description of the error), errorType: string, stackTrace: array of strings } Lambda は、 errorType として任意の値を受け入れることに注意してください。 次の例は、呼び出しで指定されたイベントデータを関数で解析できなかった Lambda 関数のエラーメッセージを示しています。 例 関数エラー { "errorMessage" : "Error parsing event data.", "errorType" : "InvalidEventDataException", "stackTrace": [ ] } レスポンスコード 202 - Accepted 400 – Bad Request 403 – Forbidden 500 – Container error 回復不能な状態。拡張機能はすぐに終了する必要があります。 終了エラー 拡張機能は、このメソッドを使用して、終了する前に Lambda にエラーを報告します。予期しない障害が発生したときに呼び出します。Lambda がエラーを受信すると、それ以降の API コールは成功しません。拡張機能は、Lambda からの応答を受信した後に終了する必要があります。 パス – /extension/exit/error メソッド - POST リクエストヘッダー Lambda-Extension-Identifier - 拡張機能の一意の識別子。必須: はい。型: UUID 文字列。 Lambda-Extension-Function-Error-Type - 拡張機能が検出したエラータイプ。必須: はい。このヘッダーは、文字列値で構成されています。Lambda はどのような文字列でも受け入れますが、形式は <category.reason> にすることが推奨されます。例: Extension.NoSuchHandler Extension.APIKeyNotFound Extension.ConfigInvalid Extension.UnknownReason リクエストボディのパラメータ ErrorRequest - エラーに関する情報。必須: いいえ。 このフィールドは、次の構造を持つ JSON オブジェクトです。 { errorMessage: string (text description of the error), errorType: string, stackTrace: array of strings } Lambda は、 errorType として任意の値を受け入れることに注意してください。 次の例は、呼び出しで指定されたイベントデータを関数で解析できなかった Lambda 関数のエラーメッセージを示しています。 例 関数エラー { "errorMessage" : "Error parsing event data.", "errorType" : "InvalidEventDataException", "stackTrace": [ ] } レスポンスコード 202 - Accepted 400 – Bad Request 403 – Forbidden 500 – Container error 回復不能な状態。拡張機能はすぐに終了する必要があります。 ブラウザで JavaScript が無効になっているか、使用できません。 AWS ドキュメントを使用するには、JavaScript を有効にする必要があります。手順については、使用するブラウザのヘルプページを参照してください。 ドキュメントの表記規則 拡張機能パートナー Telemetry API このページは役に立ちましたか? - はい ページが役に立ったことをお知らせいただき、ありがとうございます。 お時間がある場合は、何が良かったかお知らせください。今後の参考にさせていただきます。 このページは役に立ちましたか? - いいえ このページは修正が必要なことをお知らせいただき、ありがとうございます。ご期待に沿うことができず申し訳ありません。 お時間がある場合は、ドキュメントを改善する方法についてお知らせください。 | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/lambda/latest/dg/durable-basic-concepts.html | Basic concepts - AWS Lambda Basic concepts - AWS Lambda Documentation AWS Lambda Developer Guide Durable execution DurableContext Steps Wait States Invoking other functions Durable function configuration Basic concepts Lambda provides durable execution SDKs for JavaScript, TypeScript, and Python. These SDKs are the foundation for building durable functions, providing the primitives you need to checkpoint progress, handle retries, and manage execution flow. For complete SDK documentation and examples, see the JavaScript/TypeScript SDK and Python SDK on GitHub. Durable execution A durable execution represents the complete lifecycle of a Lambda durable function, using a checkpoint and replay mechanism to track business logic progress, suspend execution, and recover from failures. When functions resume after suspension or interruptions, previously completed checkpoints are replayed and the function continues execution. The lifecycle may include multiple invocations of a Lambda function to complete the execution, particularly after suspensions or failure recovery. This approach enables your function to run for extended periods (up to one year) while maintaining reliable progress despite interruptions. How replay works Lambda keeps a running log of all durable operations (steps, waits, and other operations) as your function executes. When your function needs to pause or encounters an interruption, Lambda saves this checkpoint log and stops the execution. When it's time to resume, Lambda invokes your function again from the beginning and replays the checkpoint log, substituting stored values for completed operations. This means your code runs again, but previously completed steps don't re-execute. Their stored results are used instead. This replay mechanism is fundamental to understanding durable functions. Your code must be deterministic during replay, meaning it produces the same results given the same inputs. Avoid operations with side effects (like generating random numbers or getting the current time) outside of steps, as these can produce different values during replay and cause non-deterministic behavior. DurableContext DurableContext is the context object your durable function receives. It provides methods for durable operations like steps and waits that create checkpoints and manage execution flow. Your durable function receives a DurableContext instead of the default Lambda context: TypeScript import { DurableContext, withDurableExecution, } from "@aws/durable-execution-sdk-js"; export const handler = withDurableExecution( async (event: any, context: DurableContext) => { const result = await context.step(async () => { return "step completed"; }); return result; }, ); Python from aws_durable_execution_sdk_python import ( DurableContext, durable_execution, durable_step, ) @durable_step def my_step(step_context, data): # Your business logic return result @durable_execution def handler(event, context: DurableContext): result = context.step(my_step(event["data"])) return result The Python SDK for durable functions uses synchronous methods and doesn't support await . The TypeScript SDK uses async/await . Steps Steps runs business logic with built-in retries and automatic checkpointing. Each step saves its result, ensuring your function can resume from any completed step after interruptions. TypeScript // Each step is automatically checkpointed const order = await context.step(async () => processOrder(event)); const payment = await context.step(async () => processPayment(order)); const result = await context.step(async () => completeOrder(payment)); Python # Each step is automatically checkpointed order = context.step(lambda: process_order(event)) payment = context.step(lambda: process_payment(order)) result = context.step(lambda: complete_order(payment)) Wait States Wait states are planned pauses where your function stops running (and stops charging) until it's time to continue. Use them to wait for time periods, external callbacks, or specific conditions. TypeScript // Wait for 1 hour without consuming resources await context.wait( { seconds:3600 }); // Wait for external callback const approval = await context.waitForCallback( async (callbackId) => sendApprovalRequest(callbackId) ); Python # Wait for 1 hour without consuming resources context.wait(3600) # Wait for external callback approval = context.wait_for_callback( lambda callback_id: send_approval_request(callback_id) ) When your function encounters a wait or needs to pause, Lambda saves the checkpoint log and stops the execution. When it's time to resume, Lambda invokes your function again and replays the checkpoint log, substituting stored values for completed operations. For more complex workflows, durable Lambda functions also come with advanced operations like parallel() for concurrent execution, map() for processing arrays, runInChildContext() for nested operations, and waitForCondition() for polling. See Examples for detailed examples and guidance on when to use each operation. Invoking other functions Invoke allows a durable function to call other Lambda functions and wait for their results. The calling function suspends while the invoked function executes, creating a checkpoint that preserves the result. This enables you to build modular workflows where specialized functions handle specific tasks. Use context.invoke() to call other functions from within your durable function. The invocation is checkpointed, so if your function is interrupted after the invoked function completes, it resumes with the stored result without re-invoking the function. TypeScript // Invoke another function and wait for result const customerData = await context.invoke( 'validate-customer', 'arn:aws:lambda:us-east-1:123456789012:function:customer-service:1', { customerId: event.customerId } ); // Use the result in subsequent steps const order = await context.step(async () => { return processOrder(customerData); }); Python # Invoke another function and wait for result customer_data = context.invoke( 'arn:aws:lambda:us-east-1:123456789012:function:customer-service:1', { 'customerId': event['customerId']}, name='validate-customer' ) # Use the result in subsequent steps order = context.step( lambda: process_order(customer_data), name='process-order' ) The invoked function can be either a durable or standard Lambda function. If you invoke a durable function, the calling function waits for the complete durable execution to finish. This pattern is common in microservices architectures where each function handles a specific domain, allowing you to compose complex workflows from specialized, reusable functions. Note Cross-account invocations are not supported. The invoked function must be in the same AWS account as the calling function. Durable function configuration Durable functions have specific configuration settings that control execution behavior and data retention. These settings are separate from standard Lambda function configuration and apply to the entire durable execution lifecycle. The DurableConfig object defines the configuration for durable functions: { "ExecutionTimeout": Integer, "RetentionPeriodInDays": Integer } Execution timeout The execution timeout controls how long a durable execution can run from start to completion. This is different from the Lambda function timeout, which controls how long a single function invocation can run. A durable execution can span multiple Lambda function invocations as it progresses through checkpoints, waits, and replays. The execution timeout applies to the total elapsed time of the durable execution, not to individual function invocations. Understanding the difference The Lambda function timeout (maximum 15 minutes) limits each individual invocation of your function. The durable execution timeout (maximum 1 year) limits the total time from when the execution starts until it completes, fails, or times out. During this period, your function may be invoked multiple times as it processes steps, waits, and recovers from failures. For example, if you set a durable execution timeout of 24 hours and a Lambda function timeout of 5 minutes: Each function invocation must complete within 5 minutes The entire durable execution can run for up to 24 hours Your function can be invoked many times during those 24 hours Wait operations don't count against the Lambda function timeout but do count against the execution timeout You can configure the execution timeout when creating a durable function using the Lambda console, AWS CLI, or AWS SAM. In the Lambda console, choose your function, then Configuration, Durable execution. Set the Execution timeout value in seconds (default: 86400 seconds / 24 hours, minimum: 60 seconds, maximum: 31536000 seconds / 1 year). Note The execution timeout and Lambda function timeout are different settings. The Lambda function timeout controls how long each individual invocation can run (maximum 15 minutes). The execution timeout controls the total elapsed time for the entire durable execution (maximum 1 year). Retention period The retention period controls how long Lambda retains execution history and checkpoint data after a durable execution completes. This data includes step results, execution state, and the complete checkpoint log. After the retention period expires, Lambda deletes the execution history and checkpoint data. You can no longer retrieve execution details or replay the execution. The retention period starts when the execution reaches a terminal state (SUCCEEDED, FAILED, STOPPED, or TIMED_OUT). You can configure the retention period when creating a durable function using the Lambda console, AWS CLI, or AWS SAM. In the Lambda console, choose your function, then Configuration, Durable execution. Set the Retention period value in days (default: 14 days, minimum: 1 day, maximum: 90 days). Choose a retention period based on your compliance requirements, debugging needs, and cost considerations. Longer retention periods provide more time for debugging and auditing but increase storage costs. Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Lambda durable functions Creating durable functions Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:29:30 |
https://www.atlassian.com/de/software/loom/ai | Loom AI | Atlassian Close Diese Seite in deiner Sprache anzeigen? Alle Sprachen Sprache auswählen 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Kostenlos testen Funktionen Funktionen erkunden Besprechungsnotizen Bildschirmrekorder Screenshots Loom AI Bearbeiten Back Lösungen Teams Anwendungsbeispiele Unternehmensgröße Teams Vertrieb Marketing Design Support Produktmanagement Engineering Anwendungsbeispiele Loom + Jira Loom + Confluence Unternehmensgröße Enterprise Back Resourcen Preise Mehr + Weniger - Kostenlos testen Back Kostenlos testen Drücke auf Aufnahme und die Loom AI erledigt den Rest Teile makellose Videos ohne Aufwand. Loom AI verbessert dein Video automatisch und wandelt dein Skript in ein Dokument um. Teste Loom AI kostenlos Videos um 60 % schneller aufnehmen und teilen Loom AI optimiert und schneidet deine Videos auf geradezu magische Weise und erstellt ein Textdokument dazu. Sag Hallo zu produktiven Meetings mit geringerem Aufwand Loom AI kann für dich Notizen machen und Aufgaben festhalten, damit das Meeting flüssig verläuft und die Arbeit danach direkt weitergehen kann. Schnellere Erstellung und Weitergabe mit KI-basierten Workflows Erstelle mit nur einem Klick Dokumente, die du danach sofort teilen kannst. Mit Loom AI-Workflows sind wichtige Aufgaben schnell erledigt. Teste Loom AI kostenlos Dokumenterstellung Arbeit dokumentieren, um Wissen umfassender nutzen zu können Mit KI-basierten Workflows, die dein Video in Beschreibungen für Pull-Anfragen, SOPs und mehr umwandeln, kannst du die Abstimmung beschleunigen und Sprints schneller abschließen. Erstellen eines Vorgangs Bugs in Jira oder Linear mit ein paar Klicks melden Spare bei Fehlerberichten und Tickets Zeit. Loom erfasst den Inhalt deines Videos und trägt wichtige Details für Jira und Linear automatisch ein. Nachrichtenerstellung Loom-Links automatisch Kontext hinzufügen Loom generiert sofort schriftliche Nachrichten, die du zusammen mit deinem Videolink teilen kannst – unabhängig davon, ob du dein Loom-Video per Direktnachricht oder E-Mail versendest. Erfolgreiches Messaging mit Loom AI Funktionen Videos mit Loom AI Videos ohne Loom AI Erstellung von Titeln Videos mit Loom AI Automatisch Videos ohne Loom AI Manuell Erstellung von Zusammenfassungen Videos mit Loom AI Automatisch Videos ohne Loom AI Manuell Erstellung von Kapiteln Videos mit Loom AI Automatisch Videos ohne Loom AI Manuell Aufgaben Videos mit Loom AI Automatisch Videos ohne Loom AI Manuell Einbetten eines CTA-Links Videos mit Loom AI Automatisch Videos ohne Loom AI Manuell Entfernung von Füllwörtern Videos mit Loom AI Automatisch Videos ohne Loom AI Nicht verfügbar Entfernung von Gesprächspausen Videos mit Loom AI Automatisch Videos ohne Loom AI Nicht verfügbar Umwandlung von Videos in Dokumente Videos mit Loom AI Automatisch Videos ohne Loom AI Nicht verfügbar Umwandlung von Videos in Jira- oder Linear-Vorgänge Videos mit Loom AI Automatisch Videos ohne Loom AI Nicht verfügbar Umwandlung von Videos in eine Nachricht oder E-Mail Videos mit Loom AI Automatisch Videos ohne Loom AI Nicht verfügbar Wir sprechen deine Sprache Loom AI ist in über 50 Sprachen verfügbar. Es optimiert dein Video und erstellt daraus ein Dokument in der Sprache, in der du aufnimmst. Ich wollte ein Video für einen Hack-a-Thon erstellen und beschloss, die Loom AI-Workflows auszuprobieren. Schon beim ersten Versuch war ich mehr als beeindruckt. Die KI hatte es geschafft, aus einem Video von nur 20 Sekunden(!) Länge eine Schritt-für-Schritt-Anleitung zu erfassen und in einem Dokument festzuhalten. Ich war hin und weg. Es fühlte sich wirklich wie ein Schritt in die Zukunft an. Security and Trust Manager eines großen Technologieunternehmens Bald noch mehr Funktionen Loom AI steht noch am Anfang – wir denken uns täglich neue leistungsstarke Funktionen aus und arbeiten an ihrer Umsetzung. Demnächst verfügbar Tools zur automatischen Erfassung für Entwickler Füge Konsolenprotokolle, Browserinformationen und vieles mehr sofort in ein Jira- oder Linear-Ticket ein. Demnächst verfügbar KI-Stimmen und Avatare Mit KI-Sprachausgabe und Avataren kannst du individuelle Videos im großen Stil erstellen, ohne erneut aufnehmen zu müssen. Demnächst verfügbar Verbindung zu Confluence Die Loom AI-Workflows wandeln dein Video in ein Dokument um, das du direkt in deinem Kollaborations- oder Projekttool öffnen kannst. Demnächst verfügbar Automatisches Hinzufügen von visuellen Inhalten zu Anleitungen Nimm einen Prozess auf lasse Loom AI dann Videoclips, GIFs oder Screenshots für jeden Schritt hinzufügen. Kundenstimmen 96 % der Loom-Benutzer geben an, dass die Funktionen der AI Suite bereits extrem wertvoll oder sehr wertvoll für ihre Workflows sind. Loom AI spart dir nicht nur Zeit und Mühe, sondern sorgt auch dafür, dass deine Videos für die Zielgruppe leichter zugänglich und interessanter sind. 🎥✨ Ryan Carr Gründer von Tailwind FAQs Wie erwerbe ich Loom AI? Dein Kontoadministrator kann in den Arbeitsbereichseinstellungen auf der Registerkarte für Tarif und Abrechnung ein Upgrade auf den Tarif Business + AI oder den Enterprise-Tarif veranlassen. Kann ich Loom AI kostenlos testen? Ja, du kannst unseren Tarif Business + AI 14 Tage lang kostenlos testen, nachdem du dich für Loom angemeldet hast. Warum sollte ich ein Upgrade auf Loom AI in Betracht ziehen? Viele Anbieter fügen ihren Produkten KI-Funktionen hinzu. Wir bei Loom legen Wert auf KI-Funktionen im Einklang mit unserer Mission, eine effektive Kommunikation zu ermöglichen. Die aktuellen und künftigen Funktionen der Loom AI Suite können dich folgendermaßen unterstützen: Zeitersparnis: 67 % der Benutzer übernehmen den automatisch generierten Titel ohne Bearbeitung und profitieren so von Effizienzvorteilen, ohne zusätzliche Zeit zu investieren . Die Loom AI Suite reduziert den Zeitaufwand für das Verpacken und Teilen von Loom-Videos nach der Aufnahme. So kannst du schnell ein ausgefeiltes, qualitativ hochwertiges Video versenden. Höhere Produktivität: 73 % der Benutzer geben an, dass die KI-Funktionen bereits jetzt extrem wertvoll oder sehr wertvoll für ihre Workflows sind . Die AI Suite reduziert die Notwendigkeit, Looms neu aufzunehmen. In vielen Fällen genügt also ein einziger Take. Effektive Kommunikation: Benutzer profitieren von 18 % mehr Zuschauerinteraktion . Die AI Suite fügt automatisch sofort Kontext wie Titel, Zusammenfassung, Kapitel und Aufgaben hinzu, damit deine Botschaft klar vermittelt wird und die Zuschauer sie schnell verstehen und darauf reagieren können. Wie werden meine Daten verwendet? OpenAI erhält Transkriptdaten als Textdateien, um Titel und Zusammenfassungen zu generieren. OpenAI erhält keine kompletten Video- oder Audiodateien. Wir senden Daten nur an vertrauenswürdige Drittanbietersysteme, die strengen Datenschutz- und Sicherheitskontrollen unterliegen. Unsere externen Unterauftragsverarbeiter müssen angemessene Vereinbarungen mit Loom und/oder seinen Benutzern treffen, um die Vertraulichkeit der Daten zu sichern und zu schützen. Darüber hinaus bestehen DPAs mit unseren Unterauftragsverarbeitern. Weitere Informationen und die Liste der Unterauftragsverarbeiter von Loom findest du hier . Die Nutzungsbedingungen von Loom AI sind hier zu finden. Welche Sprachen unterstützt Loom AI? Die automatischen Verbesserungsfunktionen von Loom AI (z. B. automatische Erstellung von Titeln und Zusammenfassungen) sind in über 50 Sprachen verfügbar. Unsere neue Funktion für KI-basierte Workflows kann derzeit nur Dokumentation auf Englisch generieren. Demnächst kommen weitere Sprachen hinzu. Loom funktioniert überall, wo du bist. Für Mac, Windows, iOS und Android Hol dir Loom kostenlos Unternehmen Karriere Veranstaltungen Blogs Investor Relations Atlassian Foundation Presse-Kit Kontakt Produkte Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Alle Produkte anzeigen Resourcen Technischer Support Kauf und Lizenzierung Atlassian Community Wissensdatenbank Marketplace Mein Konto Support-Ticket erstellen Lernen Partner Training und Zertifizierung Dokumentation Ressourcen für Entwickler Enterprise Services Alle Ressourcen anzeigen Copyright © 2025 Atlassian Datenschutzrichtlinie Nutzungsbedingungen Impressum Sprache wählen Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:30 |
https://issues.jenkins.io/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20labels%20%3D%20newbie-friendly%20 | Loading... Log in Skip to main content Skip to sidebar Dashboards Projects Issues Give feedback to Atlassian Help Keyboard Shortcuts About Jira Jira Credits Log In 📢 Jenkins core issues have been migrated to GitHub , no new core issues can be created in Jira Export Tools Export - CSV (All fields) Export - CSV (Current fields) Choose a delimiter Comma (,) Semicolon (;) Vertical bar (|) Caret (^) Export Cancel JENKINS-76317 Allow to define maintenance windows for clouds JENKINS-68154 Custom headers with special characters in their names JENKINS-59072 Cannot use shortcut under a folder JENKINS-55441 Lack of the Chinese Localization JENKINS-43785 Compatibility for tap plugin with pipeline plugin Refresh results {"searchers":{"groups":[{"searchers":[{"name":"Project","id":"project","key":"issue.field.project","isShown":true,"lastViewed":1768296569358,"shown":true},{"name":"Summary","id":"summary","key":"issue.field.summary","isShown":true,"shown":true},{"name":"Type","id":"issuetype","key":"issue.field.issuetype","isShown":true,"lastViewed":1768296569359,"shown":true},{"name":"Status","id":"status","key":"issue.field.status","isShown":true,"lastViewed":1768296569363,"shown":true},{"name":"Priority","id":"priority","key":"issue.field.priority","isShown":true,"shown":true},{"name":"Resolution","id":"resolution","key":"issue.field.resolution","isShown":true,"shown":true},{"name":"Creator","id":"creator","key":"issue.field.creator","isShown":true,"shown":true},{"name":"Component","id":"component","key":"issue.field.components","isShown":true,"shown":true},{"name":"% Limits","id":"workratio","key":"issue.field.workratio","isShown":true,"shown":true},{"name":"Link types","id":"issue_link_type","key":"issue.field.issuelinks","isShown":true,"shown":true},{"name":"Environment","id":"environment","key":"issue.field.environment","isShown":true,"shown":true},{"name":"Description","id":"description","key":"issue.field.description","isShown":true,"shown":true},{"name":"Comment","id":"comment","key":"issue.field.comment","isShown":true,"shown":true},{"name":"Label","id":"labels","key":"issue.field.labels","isShown":true,"lastViewed":1768296569371,"shown":true},{"name":"Query","id":"text","key":"text","isShown":true,"shown":true},{"name":"Business Value","id":"customfield_10333","key":"com.atlassian.jira.plugin.system.customfieldtypes:float","isShown":false,"shown":false},{"name":"Development","id":"customfield_10720","key":"com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary","isShown":true,"shown":true},{"name":"Epic Color","id":"customfield_10328","key":"com.pyxis.greenhopper.jira:gh-epic-color","isShown":false,"shown":false},{"name":"Epic Link","id":"customfield_10325","key":"com.pyxis.greenhopper.jira:gh-epic-link","isShown":true,"shown":true},{"name":"Epic Name","id":"customfield_10327","key":"com.pyxis.greenhopper.jira:gh-epic-label","isShown":true,"shown":true},{"name":"Epic Status","id":"customfield_10326","key":"com.pyxis.greenhopper.jira:gh-epic-status","isShown":false,"shown":false},{"name":"Epic/Theme","id":"customfield_10331","key":"com.atlassian.jira.plugin.system.customfieldtypes:labels","isShown":true,"shown":true},{"name":"Flagged","id":"customfield_10330","key":"com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes","isShown":true,"shown":true},{"name":"GitHub Users to Authorize as Committers","id":"customfield_10323","key":"com.atlassian.jira.plugin.system.customfieldtypes:textarea","isShown":true,"shown":true},{"name":"Issue Tracker","id":"customfield_11320","key":"com.atlassian.jira.plugin.system.customfieldtypes:select","isShown":true,"shown":true},{"name":"Meeting minutes URL","id":"customfield_10020","key":"com.atlassian.jira.plugin.system.customfieldtypes:url","isShown":false,"shown":false},{"name":"New Repository Name","id":"customfield_10321","key":"com.atlassian.jira.plugin.system.customfieldtypes:textfield","isShown":true,"shown":true},{"name":"Original story points","id":"customfield_11423","key":"com.atlassian.jpo:jpo-custom-field-original-story-points","isShown":true,"shown":true},{"name":"Parent Link","id":"customfield_11420","key":"com.atlassian.jpo:jpo-custom-field-parent","isShown":false,"shown":false},{"name":"Plugin Description","id":"customfield_10322","key":"com.atlassian.jira.plugin.system.customfieldtypes:textarea","isShown":true,"shown":true},{"name":"Rank","id":"customfield_10324","key":"com.pyxis.greenhopper.jira:gh-lexo-rank","isShown":true,"shown":true},{"name":"Released As","id":"customfield_10620","key":"com.atlassian.jira.plugin.system.customfieldtypes:textfield","isShown":true,"shown":true},{"name":"Repository URL","id":"customfield_10320","key":"com.atlassian.jira.plugin.system.customfieldtypes:url","isShown":true,"shown":true},{"name":"Sprint","id":"customfield_10329","key":"com.pyxis.greenhopper.jira:gh-sprint","isShown":true,"shown":true},{"name":"Story Points","id":"customfield_10332","key":"com.atlassian.jira.plugin.system.customfieldtypes:float","isShown":false,"shown":false},{"name":"Team","id":"customfield_11424","key":"com.atlassian.teams:rm-teams-custom-field-team","isShown":true,"shown":true},{"name":"URL","id":"customfield_10000","key":"com.atlassian.jira.plugin.system.customfieldtypes:url","isShown":true,"shown":true}],"type":"DETAILS","title":"Details"},{"searchers":[{"name":"Created Date","id":"created","key":"issue.field.created","isShown":true,"shown":true},{"name":"Updated Date","id":"updated","key":"issue.field.updated","isShown":true,"shown":true},{"name":"Resolution Date","id":"resolutiondate","key":"issue.field.resolution.date","isShown":true,"shown":true},{"name":"Target end","id":"customfield_11422","key":"com.atlassian.jpo:jpo-custom-field-baseline-end","isShown":true,"shown":true},{"name":"Target start","id":"customfield_11421","key":"com.atlassian.jpo:jpo-custom-field-baseline-start","isShown":true,"shown":true}],"type":"DATES","title":"Dates"},{"searchers":[{"name":"Assignee","id":"assignee","key":"issue.field.assignee","isShown":true,"lastViewed":1768296569365,"shown":true},{"name":"Reporter","id":"reporter","key":"issue.field.reporter","isShown":true,"shown":true}],"type":"PEOPLE","title":"People"}]},"values":{"issuetype":{"name":"Type","editHtml":"\n\n\n\n <div class=\"field-group aui-field-issuetype\" >\n <label for=\"searcher-type\">Type</label> <select class=\"select js-default-checkboxmultiselect\"\n id=\"searcher-type\"\n multiple=\"multiple\"\n name=\"type\"\n data-max-inline-results-displayed=\"100\"\n data-placeholder-text=\"Find Issue Types...\">\n <optgroup>\n \n <option class=\" \"\n id=\"type_-2\"\n title=\"All Standard Issue Types\"\n value=\"-2\">All Standard Issue Types</option>\n </optgroup>\n\n <optgroup label=\"Standard Issue Types\">\n \n <option class=\" imagebacked 10730 \"\n data-icon=\"/secure/viewavatar?size=xsmall&amp;avatarId=14673&amp;avatarType=issuetype\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_1\"\n title=\"Bug\"\n value=\"1\">Bug</option>\n \n <option class=\" imagebacked 10730 \"\n data-icon=\"/images/icons/issuetypes/epic.png\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_10001\"\n title=\"Epic\"\n value=\"10001\">Epic</option>\n \n <option class=\" imagebacked 10730 \"\n data-icon=\"/secure/viewavatar?size=xsmall&amp;avatarId=14680&amp;avatarType=issuetype\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_4\"\n title=\"Improvement\"\n value=\"4\">Improvement</option>\n \n <option class=\" imagebacked 10730 \"\n data-icon=\"/secure/viewavatar?size=xsmall&amp;avatarId=14681&amp;avatarType=issuetype\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_2\"\n title=\"New Feature\"\n value=\"2\">New Feature</option>\n \n <option class=\" imagebacked 10730 \"\n data-icon=\"/secure/viewavatar?size=xsmall&amp;avatarId=14670&amp;avatarType=issuetype\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_5\"\n title=\"Patch\"\n value=\"5\">Patch</option>\n \n <option class=\" imagebacked 10730 \"\n data-icon=\"/secure/viewavatar?size=xsmall&amp;avatarId=14685&amp;avatarType=issuetype\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_10002\"\n title=\"Story\"\n value=\"10002\">Story</option>\n \n <option class=\" imagebacked 10730 \"\n data-icon=\"/secure/viewavatar?size=xsmall&amp;avatarId=14688&amp;avatarType=issuetype\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_3\"\n title=\"Task\"\n value=\"3\">Task</option>\n </optgroup>\n\n <optgroup label=\"Sub-Task Issue Types\">\n </optgroup>\n </select>\n </div>\n ","validSearcher":true,"isShown":true},"project":{"name":"Project","viewHtml":" <div class=\"searcherValue\">\n \n <label class=\"fieldLabel\" for=\"fieldpid\">Project:</label><span id=\"fieldpid\" class=\"fieldValue\">\n \n <a data-pid=\"10172\" data-issue-type-ids=\"\" href=\"/browse/JENKINS\" title=\"Browse Jenkins project\">Jenkins</a> </span></div>\n","editHtml":" \n <div class=\"field-group aui-field-project\" >\n <label for=\"searcher-pid\">Project</label> <select class=\"js-project-checkboxmultiselect\"\n data-placeholder-text=\"Find Projects...\"\n id=\"searcher-pid\"\n multiple=\"multiple\"\n name=\"pid\">\n <optgroup label=\"Recent Projects\">\n </optgroup>\n <optgroup label=\"All Projects\" >\n <option data-icon=\"/secure/projectavatar?pid=10172&size=small\"\n selected=\"selected\" title=\"Jenkins\"\n value=\"10172\">\n Jenkins (JENKINS)\n </option>\n \n <option data-icon=\"/secure/projectavatar?pid=10050&size=small\"\n title=\"test\"\n value=\"10050\">\n test (TEST)\n </option>\n </optgroup>\n </select>\n </div>\n \n\n","jql":"project = \"10172\"","validSearcher":true,"isShown":true},"assignee":{"name":"Assignee","editHtml":"\n \n <div class=\"field-group aui-field-userlist\" >\n <label for=\"searcher-assigneeSelect\">Assignee</label> <fieldset rel=\"assignee\" class=\"hidden user-group-searcher-params\">\n </fieldset>\n <select class=\"js-usergroup-checkboxmultiselect\" multiple=\"multiple\" id=\"assignee\" name=\"assignee\" data-placeholder-text=\"Enter username or group\">\n <optgroup>\n <option class=\"headerOption\" data-icon=\"https://issues.jenkins.io/secure/useravatar?size=xsmall&avatarId=10293\" value=\"empty\" title=\"Unassigned\">Unassigned</option>\n </optgroup>\n <optgroup>\n </optgroup>\n </select>\n <input type=\"hidden\" name=\"check_prev_assignee\" value=\"true\">\n </div>\n \n","validSearcher":true,"isShown":true},"status":{"name":"Status","viewHtml":" <div class=\"searcherValue\">\n \n <label class=\"fieldLabel\" for=\"fieldstatus\">Status:</label><span id=\"fieldstatus\" class=\"fieldValue\">\n \n Open, In Progress, Reopened </span></div>\n","editHtml":"\n <div class=\"field-group aui-field-constants\" >\n <label for=\"searcher-status\">Status</label> <select class=\"select js-default-checkboxmultiselectstatuslozenge\"\n data-placeholder-text=\"Find Statuses...\"\n id=\"searcher-status\"\n multiple=\"multiple\"\n name=\"status\"\n data-max-inline-results-displayed=\"100\"\n data-footer-text=\"-95 more options. Continue typing to refine further.\" data-status-lozenge=\"true\">\n <optgroup >\n <option selected=\"selected\" class=\"imagebacked\" data-icon=\"/images/icons/statuses/open.png\" value=\"1\" title=\"Open\" data-simple-status=\"{&quot;id&quot;:&quot;1&quot;,&quot;name&quot;:&quot;Open&quot;,&quot;description&quot;:&quot;The issue is open and ready for the assignee to start work on it.&quot;,&quot;iconUrl&quot;:&quot;/images/icons/statuses/open.png&quot;,&quot;statusCategory&quot;:{&quot;id&quot;:2,&quot;key&quot;:&quot;new&quot;,&quot;colorName&quot;:&quot;default&quot;}}\">Open</option>\n <option selected=\"selected\" class=\"imagebacked\" data-icon=\"/images/icons/statuses/inprogress.png\" value=\"3\" title=\"In Progress\" data-simple-status=\"{&quot;id&quot;:&quot;3&quot;,&quot;name&quot;:&quot;In Progress&quot;,&quot;description&quot;:&quot;This issue is being actively worked on at the moment by the assignee.&quot;,&quot;iconUrl&quot;:&quot;/images/icons/statuses/inprogress.png&quot;,&quot;statusCategory&quot;:{&quot;id&quot;:4,&quot;key&quot;:&quot;indeterminate&quot;,&quot;colorName&quot;:&quot;inprogress&quot;}}\">In Progress</option>\n <option selected=\"selected\" class=\"imagebacked\" data-icon=\"/images/icons/statuses/reopened.png\" value=\"4\" title=\"Reopened\" data-simple-status=\"{&quot;id&quot;:&quot;4&quot;,&quot;name&quot;:&quot;Reopened&quot;,&quot;description&quot;:&quot;This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.&quot;,&quot;iconUrl&quot;:&quot;/images/icons/statuses/reopened.png&quot;,&quot;statusCategory&quot;:{&quot;id&quot;:4,&quot;key&quot;:&quot;indeterminate&quot;,&quot;colorName&quot;:&quot;inprogress&quot;}}\">Reopened</option>\n <option class=\"imagebacked\" data-icon=\"/images/icons/statuses/information.png\" value=\"10005\" title=\"In Review\" data-simple-status=\"{&quot;id&quot;:&quot;10005&quot;,&quot;name&quot;:&quot;In Review&quot;,&quot;description&quot;:&quot;&quot;,&quot;iconUrl&quot;:&quot;/images/icons/statuses/information.png&quot;,&quot;statusCategory&quot;:{&quot;id&quot;:4,&quot;key&quot;:&quot;indeterminate&quot;,&quot;colorName&quot;:&quot;inprogress&quot;}}\">In Review</option>\n <option class=\"imagebacked\" data-icon=\"/images/icons/statuses/generic.png\" value=\"10000\" title=\"Verified\" data-simple-status=\"{&quot;id&quot;:&quot;10000&quot;,&quot;name&quot;:&quot;Verified&quot;,&quot;description&quot;:&quot;Verified&quot;,&quot;iconUrl&quot;:&quot;/images/icons/statuses/generic.png&quot;,&quot;statusCategory&quot;:{&quot;id&quot;:4,&quot;key&quot;:&quot;indeterminate&quot;,&quot;colorName&quot;:&quot;inprogress&quot;}}\">Verified</option>\n <option class=\"imagebacked\" data-icon=\"/images/icons/statuses/generic.png\" value=\"10203\" title=\"Fixed but Unreleased\" data-simple-status=\"{&quot;id&quot;:&quot;10203&quot;,&quot;name&quot;:&quot;Fixed but Unreleased&quot;,&quot;description&quot;:&quot;This change has been implemented and merged, but not yet released.&quot;,&quot;iconUrl&quot;:&quot;/images/icons/statuses/generic.png&quot;,&quot;statusCategory&quot;:{&quot;id&quot;:3,&quot;key&quot;:&quot;done&quot;,&quot;colorName&quot;:&quot;success&quot;}}\">Fixed but Unreleased</option>\n <option class=\"imagebacked\" data-icon=\"/images/icons/statuses/resolved.png\" value=\"5\" title=\"Resolved\" data-simple-status=\"{&quot;id&quot;:&quot;5&quot;,&quot;name&quot;:&quot;Resolved&quot;,&quot;description&quot;:&quot;A developer had implemented a fix and is waiting for a feedback from the reporter.&quot;,&quot;iconUrl&quot;:&quot;/images/icons/statuses/resolved.png&quot;,&quot;statusCategory&quot;:{&quot;id&quot;:3,&quot;key&quot;:&quot;done&quot;,&quot;colorName&quot;:&quot;success&quot;}}\">Resolved</option>\n <option class=\"imagebacked\" data-icon=\"/images/icons/statuses/closed.png\" value=\"6\" title=\"Closed\" data-simple-status=\"{&quot;id&quot;:&quot;6&quot;,&quot;name&quot;:&quot;Closed&quot;,&quot;description&quot;:&quot;The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.&quot;,&quot;iconUrl&quot;:&quot;/images/icons/statuses/closed.png&quot;,&quot;statusCategory&quot;:{&quot;id&quot;:3,&quot;key&quot;:&quot;done&quot;,&quot;colorName&quot;:&quot;success&quot;}}\">Closed</option>\n </optgroup>\n</select>\n </div>\n \n","jql":"status in (Open, \"In Progress\", Reopened)","validSearcher":true,"isShown":true},"labels":{"name":"Label","viewHtml":" <div class=\"searcherValue\">\n \n <label class=\"fieldLabel\" for=\"fieldlabels\">Label:</label><span id=\"fieldlabels\" class=\"fieldValue\">\n \n newbie-friendly\n</span></div>\n","editHtml":"\n <div class=\"field-group aui-field-labels\" >\n <label for=\"searcher-labels\">Labels</label> <select class=\"js-label-checkboxmultiselect\" multiple=\"multiple\" id=\"searcher-labels\" name=\"labels\" data-placeholder-text=\"Find Labels...\">\n <option value=\"newbie-friendly\" title=\"newbie-friendly\" selected=\"selected\">newbie-friendly</option>\n </select>\n </div>\n \n","jql":"labels = newbie-friendly","validSearcher":true,"isShown":true}}} [{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}] 0.3 0 Atlassian Jira Project Management Software About Jira Report a problem Powered by a free Atlassian Jira open source license for The Linux Foundation. Try Jira - bug tracking software for your team. Atlassian | 2026-01-13T09:29:30 |
https://www.atlassian.com/ja/software/loom/ai | Loom AI | Atlassian Close あなたの言語 でこのページを表示しますか？ すべての言語 言語を選択する 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski 無料で試す 機能 機能の紹介 ミーティング議事録 スクリーン レコーダー スクリーンショット Loom AI 編集 Back ソリューション チーム ユースケース 企業規模 チーム 営業 マーケティング デザイン サポート プロダクトマネジメント エンジニアリング ユースケース Loom + Jira Loom + Confluence 企業規模 Enterprise Back リソース 価格 その他 + 表示を減らす - 無料で試す Back 無料で試す 録画したら、あとは Loom AI にお任せ 完璧な動画を手間なく共有しましょう。 Loom AI は動画を自動補正して、スクリプトをドキュメントに変換します。 Loom AI を無料で試す 動画の録画と共有の速度が 60% アップ Loom AI は、動画を即座に調整、編集して、テキスト ドキュメントを生成します 手間がかからない、効率的なミーティングを始めましょう Loom AI にメモ取りやアクション アイテムのキャプチャを任せることで、ミーティング中やその後の作業を円滑に進められます。 AI ワークフローによる、より迅速な構築とリリース すぐに共有できるドキュメントがワンクリックで完成します。 Loom AI ワークフローは、重要なタスクを迅速に完了するのに役立ちます。 Loom AI を無料で試す ドキュメントの作成 作業を文書化して、ナレッジを拡大 AI ワークフローで動画をプル リクエストの説明や SOP などに変換することで、チーム メンバーがすぐに足並みを揃えて、スプリントをスピードアップできます。 課題の作成 数回のクリックで Jira や Linear でのバグ報告が完了 バグ レポートやチケットにかかる時間を節約しましょう。Loom は動画のコンテンツをキャプチャして、Jira や Linear で重要な詳細を入力します。 メッセージの記入 Loom リンクでコンテキストを自動追加 Loom によって、DM やメールで送信する動画リンクと一緒に共有するメッセージが即座に生成されます。 Loom AI でメッセージを自動生成しましょう 機能 Loom AI を使用している動画 Loom AI を使用していない動画 タイトル Loom AI を使用している動画 auto-generated Loom AI を使用していない動画 手動 要約 Loom AI を使用している動画 auto-generated Loom AI を使用していない動画 手動 チャプター Loom AI を使用している動画 auto-generated Loom AI を使用していない動画 手動 タスク Loom AI を使用している動画 auto-generated Loom AI を使用していない動画 手動 CTA リンクの埋め込み Loom AI を使用している動画 auto-generated Loom AI を使用していない動画 手動 つなぎ言葉の削除 Loom AI を使用している動画 auto-generated Loom AI を使用していない動画 なし 不要な間の削除 Loom AI を使用している動画 auto-generated Loom AI を使用していない動画 なし 動画をドキュメントに変換 Loom AI を使用している動画 auto-generated Loom AI を使用していない動画 なし 動画を Jira または Linear の課題に変換 Loom AI を使用している動画 auto-generated Loom AI を使用していない動画 なし 動画をメッセージまたはメールに変換 Loom AI を使用している動画 auto-generated Loom AI を使用していない動画 なし お客様の言語で提供 Loom AI は 50 以上の言語で利用できます。録画した言語に基づいて動画を補正し、ドキュメントに変換します。 ヒントとコツを集約する動画の作成中に、Loom AI のワークフローを試してみることにしました。初めて使用したときは、本当にびっくりしました。わずか 20 秒の動画でしたが、ドキュメントで正確な手順をキャプチャしてくれたんです。驚きましたね。まさに革命だと感じました。 エンタープライズ テック企業、セキュリティ & トラスト マネージャー リリース予定の新機能 Loom AI は始まったばかりです。私たちは毎日、強力な新機能の実現を目指して開発に取り組んでいます。 近日公開 自動キャプチャ開発ツール コンソール ログやブラウザ情報などを Jira や Linear チケットに即座に追加します 近日公開 AI ボイスとアバター AI テキスト読み上げとアバターにより、録画をやり直すことなくカスタム動画を作成できます。 近日公開 Confluence への接続 Loom AI ワークフローで動画をドキュメントに変換し、そのドキュメントをコラボレーション ツールまたはプロジェクト ツールで開けます。 近日公開 手順にビジュアルを自動追加 プロセスを録画すると、Loom AI が各手順に動画クリップ、GIF、またはスクリーンショットを追加します。 お客様の声 Loom ユーザーのうち 96% が、ワークフローでの AI Suite 機能について、非常に価値がある、またはとても価値があると回答しています Loom AI は時間と労力を節約するだけでなく、動画を視聴者にとって分かりやすく、魅力的なものにします。🎥 ✨ Ryan Carr 氏 Tailwind 創設者 よくある質問 Loom AI を購入するにはどうすればいいですか? ワークスペース設定の [プランと請求] タブで、アカウント管理者によって Business + AI または Enterprise プランにアップグレードできます。 Loom AI を無料で試用できますか? はい、できます。Loom にサインアップすると、Business + AI プランを 14 日間、無料で試用できます。 Loom AI へのアップグレードを検討すべき理由はなんですか? 多くの企業が自社製品に AI を取り入れています。Loom にとっての最優先事項は、効果的なコミュニケーションを実現するという私たちの使命を推進する AI 機能を構築することです。Loom AI Suite は、現在提供されている機能と今後予定されている機能において、次のことをサポートします。 作業のスピードアップ: ユーザーのうち 67% が自動生成されたタイトルの編集を必要としないため、時間をかけずに効率を上げられます 。Loom AI Suite によって、録画後に必要となる Loom のパッケージ化と共有に費やす時間が短縮されるため、ユーザーは高品質で洗練された動画をすばやく送信できます。 生産性の向上: ユーザーのうち 73% が、現在のワークフローにとって「非常に価値がある、またはとても価値がある」と回答しています 。AI Suite を使えば、Loom を再録画する必要性が軽減されるため、たった一度の録画で作業を完了できます。 効果的なコミュニケーション: 視聴者のエンゲージメントが 18% 向上します 。AI Suite によって、タイトル、要約、チャプター、タスクなどのコンテキストが自動で瞬時に追加されます。これにより、メッセージが明確になり、視聴者がすぐに理解して行動できるようになります。 データはどのように使用されますか? OpenAI は、タイトルと要約を生成するために、トランスクリプト データをテキスト ファイルとして取得します。OpenAI がフル動画や音声を受信することはありません。 アトラシアンは、厳格なプライバシーとセキュリティ設定の対象である、信頼できるサードパーティ システムにのみデータを送信します。当社のサードパーティ副処理者は、データの機密性を保護するために、Loom やそのユーザーと適切な契約を結んでいます。さらに、アトラシアンは副処理者と DPA を締結しています。 詳細情報と Loom の副処理者のリストは、 こちら でご確認ください。Loom の AI 規約は こちら でご確認ください。 Loom AI はどの言語に対応していますか? Loom AI の自動補正機能 (自動タイトルや要約など) は、 50 以上の言語 で生成されます。 現在、新しい AI ワークフロー機能では、英語でのドキュメントのみが生成されます。今後、より多くの言語が AI ワークフローで利用可能になる予定です。 場所を問わず Loom を活用 Mac、Windows、iOS、Android 用 Loom を無料で入手 会社名 アトラシアンで働く イベント ブログ 投資家向け アトラシアン基金 プレスキット お問い合わせ 製品 Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket すべての製品を見る リソース 技術サポート 購入とライセンス アトラシアン コミュニティ ナレッジ ベース Marketplace アカウント管理 サポートを依頼する 学ぶ パートナー トレーニングと認定 ドキュメント 開発者向けリソース エンタープライズ サービス 全リソースを見る Copyright © 2025 Atlassian プライバシーポリシー 利用規約 サイト管理者情報 言語の選択 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:30 |
https://www.atlassian.com/es/software/loom/ai | Loom AI | Atlassian Close ¿Quieres ver esta página en tu idioma ? Todos los idiomas Elige tu idioma 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Probar gratis Funciones Explorar las funciones Notas de reunión Grabadora de pantalla Pantallazos Loom AI Editando Back Soluciones Equipos Casos de uso Tamaño de la empresa Equipos Ventas Marketing Diseño Soporte Gestión de productos Ingeniería Casos de uso Loom + Jira Loom + Confluence Tamaño de la empresa Enterprise Back Recursos Precios Más + Menos - Probar gratis Back Probar gratis Pulsa grabar y Loom AI se encargará del resto Comparte vídeos impecables sin mover un dedo. Loom AI mejora automáticamente tu vídeo y transforma tu guion en un documento. Prueba Loom AI gratis Graba y comparte tus vídeos un 60 % más rápido Loom AI perfecciona, edita y produce por arte de magia un documento de texto para tu vídeo Te damos la bienvenida a grandes reuniones con menos trabajo Deja que Loom AI tome notas y capture los elementos de acción para que el trabajo siga avanzando durante las reuniones y después de estas. Crea y envía más rápido con los flujos de trabajo de IA Documentos listos para compartir con un solo clic. Loom AI te ayudan a completar tareas importantes de forma rápida. Prueba Loom AI gratis Escribir un documento Documenta tu trabajo para ampliar conocimientos Alinea más rápido y acelera los sprints con los flujos de trabajo de IA que convierten tus vídeos en descripciones de solicitudes de extracción, SOP y mucho más. Crea un tique Informa de errores en Jira o Linear con unos pocos clics Ahorra tiempo en informes de errores y tickets. Loom captura el contenido de tu vídeo y rellena los detalles esenciales para Jira y Linear. ESCRIBIR UN MENSAJE Añade contexto automáticamente con tu enlace de Loom Loom genera al instante mensajes escritos para que los compartas junto a tu enlace de vídeo, tanto si envías un mensaje de Loom por mensaje directo como por correo electrónico. Los mensajes siempre llegan con Loom AI Funciones Vídeos con Loom AI Vídeos sin Loom AI Títulos Vídeos con Loom AI Generado automáticamente Vídeos sin Loom AI Manual Resúmenes Vídeos con Loom AI Generado automáticamente Vídeos sin Loom AI Manual Capítulos Vídeos con Loom AI Generado automáticamente Vídeos sin Loom AI Manual Tareas Vídeos con Loom AI Generado automáticamente Vídeos sin Loom AI Manual Insertar un enlace de CTA Vídeos con Loom AI Generado automáticamente Vídeos sin Loom AI Manual Eliminación de palabras de relleno Vídeos con Loom AI Generado automáticamente Vídeos sin Loom AI No disponible Eliminación de silencios Vídeos con Loom AI Generado automáticamente Vídeos sin Loom AI No disponible Convertir tu vídeo en un documento Vídeos con Loom AI Generado automáticamente Vídeos sin Loom AI No disponible Convertir tu vídeo en una incidencia de Jira o Linear Vídeos con Loom AI Generado automáticamente Vídeos sin Loom AI No disponible Convertir tu vídeo en un mensaje o correo electrónico Vídeos con Loom AI Generado automáticamente Vídeos sin Loom AI No disponible Hablamos tu idioma Disponible en más de 50 idiomas, Loom AI mejora y convierte tu vídeo en un documento según el idioma en el que grabes. Estaba creando un vídeo para una maratón de trucos y decidí probar los flujos de trabajo de Loom AI. Después de usarlo por primera vez, literalmente dije: "¡Guau!". Logró capturar pasos precisos en un documento con 20 (SOLO VEINTE) segundos de vídeo. Menuda sorpresa. La verdad es que parecía el futuro. Gerente de seguridad y confianza de una empresa de tecnología empresarial Próximas novedades Loom AI acaba de empezar. Estamos ideando y trabajando en nuevas y potentes funciones todos los días. Próximamente Herramientas de desarrollo con captura automática Añade al instante los registros de la consola, la información del navegador y más a tu ticket de Jira o Linear. Próximamente Avatares y voces con IA Los avatares y la conversión de texto a voz con IA te permiten crear vídeos personalizados a escala sin necesidad de volver a grabarlos. Próximamente Conexión con Confluence Después de que los flujos de trabajo de Loom AI conviertan tu vídeo en un documento, ábrelo en tu herramienta de colaboración o de proyecto. Próximamente Adición automática de imágenes a las guías paso a paso Graba un proceso y Loom AI añadirá clips de vídeo, GIF o capturas de pantalla para cada paso. Qué dicen los clientes El 96 % de los usuarios de Loom afirma que las funciones del paquete de IA ya son muy valiosas para sus flujos de trabajo Loom AI no solo ahorra tiempo y esfuerzo, sino que también hace que tus vídeos sean más accesibles y atractivos para tu público. 🎥 ✨ Ryan Carr Fundador de Tailwind Preguntas frecuentes ¿Cómo puedo comprar Loom AI? El administrador de cuenta puede mejorar al plan Business + AI o Enterprise en la configuración del espacio de trabajo, en la pestaña "Plan y facturación". ¿Puedo probar Loom AI gratis? Sí, puedes probar nuestro plan Business + AI gratis durante 14 días al registrarte en Loom. ¿Por qué debería considerar cambiarme a Loom AI? Muchas empresas están añadiendo la IA a sus productos. En Loom, nuestra prioridad número uno es crear funciones de IA que promuevan nuestra misión de lograr una comunicación eficaz. El paquete Loom AI (con las funciones tanto actuales como futuras) está diseñado para ayudarte a lo siguiente: Trabajar más rápido: el 67 % de los usuarios no editan el título generado automáticamente, lo que aumenta la eficiencia sin necesidad de invertir más tiempo .El paquete Loom AI reduce el tiempo dedicado a empaquetar y compartir mensajes de Loom después de la grabación, por lo que puedes enviar rápidamente un vídeo brillante y de alta calidad. Aumentar la productividad: el 73 % de las personas dijo que es "extremadamente o muy valioso" para sus flujos de trabajo actuales .El paquete de IA reduce la necesidad de volver a grabar mensajes de Loom para que tu primera toma sea la mejor. Comunicarte de forma eficaz: un 18 % más de participación de los espectadores .El paquete de IA añade contexto de forma instantánea y automática (título, resumen, capítulos y tareas) para garantizar que tu mensaje sea claro y los espectadores puedan acceder a él y responder rápidamente. ¿Cómo se utilizan mis datos? OpenAI recibe los datos de las transcripciones como archivos de texto para generar títulos y resúmenes. Sin embargo, no recibe vídeos ni audio completos. Solo enviamos datos a sistemas de terceros de confianza que están sujetos a estrictos controles de privacidad y seguridad. Nuestros subprocesadores externos están sujetos a los acuerdos pertinentes con Loom o sus usuarios con el fin de garantizar y proteger la confidencialidad de los datos. Además, hemos ejecutado los anexos sobre el tratamiento de datos con nuestros subprocesadores. Puedes encontrar más información y la lista de subprocesadores de Loom aquí . Puedes encontrar las condiciones de Loom AI aquí . ¿Qué idiomas admite Loom AI? Las funciones de mejora automática de Loom AI (como títulos, resúmenes, etc., automáticos) se generan en más de 50 idiomas . Actualmente, nuestra nueva función de flujos de trabajo de IA solo genera documentación en inglés. Muy pronto, se admitirán más idiomas. Loom funciona dondequiera que vayas Para Mac, Windows, iOS y Android Consigue Loom gratis Compañía Resumen Eventos Blogs Relaciones con los inversores Atlassian Foundation Kit de prensa Ponte en contacto con nosotros. Productos Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Ver todos los productos Recursos Servicio técnico Compra y licencia Comunidad de Atlassian Base de conocimientos Marketplace Mi cuenta Crear tique de asistencia Tutorial Socios Formación y certificación Documentación Recursos para desarrolladores Servicios empresariales Ver todos los recursos Copyright © 2025 Atlassian Política de privacidad Términos Impressum Selecciona un idioma Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/ja_jp/lambda/latest/dg/runtimes-extensions-api.html#runtimes-extensions-api-lifecycle | Lambda 拡張機能 API を使用した拡張機能の作成 - AWS Lambda Lambda 拡張機能 API を使用した拡張機能の作成 - AWS Lambda ドキュメント AWS Lambda デベロッパーガイド Lambda 実行環境のライフサイクル 拡張機能 API リファレンス Lambda 拡張機能 API を使用した拡張機能の作成 Lambda 関数の作成者は、拡張機能を使用して、Lambda を、モニタリング、可観測性、セキュリティ、およびガバナンスのための任意のツールと統合します。関数作成者は、AWS、 AWS パートナー 、およびオープンソースプロジェクトの拡張機能を使用できます。拡張機能の使用の詳細については、AWS Lambda コンピューティングブログの AWS 拡張機能の紹介 を参照してください。このセクションでは、Lambda Extensions API、Lambda 実行環境ライフサイクル、および Lambda Extensions API リファレンスを使用する方法を説明します。 拡張機能の作成者は、Lambda Extensions API を使用して Lambda 実行環境 に深く統合することができます。拡張機能は、関数および実行環境のライフサイクルイベントに登録できます。これらのイベントに対応して、新しいプロセスを開始し、ロジックを実行し、Lambda ライフサイクルのすべてのフェーズ (初期化、呼び出し、およびシャットダウン) を制御し、これらに参加することができます。さらに、 Runtime Logs API を使用して、ログのストリームを受信できます。 拡張機能は、実行環境で独立したプロセスとして実行され、関数の呼び出しが完全に処理された後も引き続き実行できます。拡張機能はプロセスとして実行されるため、関数とは異なる言語で記述できます。コンパイルされた言語を使用して拡張機能を実装することをお勧めします。この場合、拡張機能は、サポートされているランタイムと互換性のある自己完結型のバイナリです。すべての Lambda ランタイム は拡張機能をサポートします。コンパイルされていない言語を使用する場合は、必ず互換性のあるランタイムを拡張機能に含めてください。 Lambda は 内部拡張機能 もサポートしています。内部拡張機能は、ランタイムプロセスで別のスレッドとして実行されます。ランタイムは、内部拡張を開始および停止します。Lambda 環境と統合する別の方法は、言語固有の 環境変数とラッパースクリプト を使用することです。これらを使用して、ランタイム環境を設定し、ランタイムプロセスの起動動作を変更できます。 関数に拡張機能を追加するには、次の 2 つの方法があります。 .zip ファイルアーカイブ としてデプロイされた関数では、拡張機能を レイヤー としてデプロイします。コンテナイメージとして定義された関数の場合は、コンテナイメージに 拡張機能 を追加します。 注記 拡張機能とラッパースクリプトの例については、AWS Lambda サンプル GitHub リポジトリの 「 AWS拡張 」を参照してください。 トピック Lambda 実行環境のライフサイクル 拡張機能 API リファレンス Lambda 実行環境のライフサイクル 実行環境のライフサイクルには、以下のフェーズが含まれています。 Init : このフェーズ中、Lambda は、設定したリソースを使用して実行環境を作成またはフリーズ解除し、関数コードとすべてのレイヤーをダウンロードして、拡張機能とランタイムを初期化し、関数の初期化コード (メインハンドラーの外部にあるコード) を実行します。 Init フェーズは、最初の呼び出し中か、 プロビジョニング済みの同時実行 を有効にしている場合は関数呼び出しの前に、発生します。 Init フェーズは、 Extension init 、 Runtime init 、 Function init の 3 つのサブフェーズに分割されます。これらのサブフェーズでは、関数コードが実行される前に、すべての拡張機能とランタイムがそのセットアップタスクを完了します。 Invoke : このフェーズでは、Lambda は関数ハンドラーを呼び出します。関数が実行され、完了すると、Lambda は、別の関数呼び出しを処理する準備をします。 Shutdown : このフェーズは、Lambda 関数が一定期間呼び出しを受け取らなかった場合にトリガーされます。 Shutdown フェーズでは、Lambda はランタイムをシャットダウンし、拡張機能にアラートを出してそれらを完全に停止させた後、環境を削除します。Lambda は、各拡張機能に Shutdown イベントを送信します。これにより、環境がシャットダウンされようとしていることを各拡張機能に伝えます。 各フェーズは、Lambda からランタイム、および登録されたすべての拡張機能へのイベントから始まります。ランタイムと各拡張機能は、 Next API リクエストを送信することで完了を示します。Lambda は、各プロセスが完了して保留中のイベントがなくなると、実行環境をフリーズします。 トピック 初期化フェーズ 呼び出しフェーズ シャットダウンフェーズ アクセス許可と設定 障害処理 拡張機能のトラブルシューティング 初期化フェーズ Extension init フェーズの間、各拡張機能モジュールは、イベントを受信するために Lambda に登録されている必要があります。Lambda は、拡張機能がブートストラップシーケンスを完了していることを検証するために、拡張機能の完全なファイル名を使用します。したがって、各 Register API コールには、拡張機能の完全なファイル名を持つ Lambda-Extension-Name ヘッダーを含める必要があります。 1 つの関数に最大 10 個の拡張機能を登録できます。この制限は、 Register API コールを通じて適用されます。 各拡張機能が登録されると、Lambda は Runtime init フェーズを開始します。ランタイムプロセスは functionInit を呼び出して Function init フェーズを開始します。 Init フェーズはランタイム後に完了します。登録された各拡張機能は、 Next API リクエストを送信することで完了を示します。 注記 拡張機能は、 Init フェーズの任意の時点で初期化を完了できます。 呼び出しフェーズ Next API リクエストに応答して Lambda 関数が呼び出されると、Lambda は、ランタイム、および Invoke イベントに登録されている各拡張機能に、 Invoke イベントを送信します。 呼び出し中、外部拡張機能は関数と並行して実行されます。また、関数が完了した後も、引き続き実行されます。これにより、診断情報をキャプチャしたり、ログ、メトリクス、トレースを任意の場所に送信したりできます。 ランタイムから関数応答を受信した後、拡張機能がまだ実行中であっても、Lambda はクライアントに応答を返します。 Invoke フェーズはランタイム後に終了します。すべての拡張機能は、 Next API リクエストを送信することによって完了を示します。 イベントペイロード ：ランタイムに送信されるイベント（および Lambda 関数）は、リクエスト、ヘッダー ( RequestId など) およびペイロード全体を保持します。各拡張機能に送信されるイベントには、イベントの内容を説明するメタデータが含まれます。このライフサイクルイベントには、イベントのタイプ、関数のタイムアウト時間 ( deadlineMs ) 、 requestId 、呼び出された関数の Amazon リソースネーム (ARN) 、およびトレースヘッダーが含まれます。 関数イベント本体にアクセスする拡張機能は、その拡張機能と通信するインランタイム SDK を使用できます。関数のデベロッパーは、関数が呼び出されたときにインランタイム SDK を使用して、拡張機能にペイロードを送信します。 ペイロードの例を次に示します。 { "eventType": "INVOKE", "deadlineMs": 676051, "requestId": "3da1f2dc-3222-475e-9205-e2e6c6318895", "invokedFunctionArn": "arn:aws:lambda:us-east-1:123456789012:function:ExtensionTest", "tracing": { "type": "X-Amzn-Trace-Id", "value": "Root=1-5f35ae12-0c0fec141ab77a00bc047aa2;Parent=2be948a625588e32;Sampled=1" } } 所要時間の制限 : 関数のタイムアウト設定では、 Invoke フェーズ全体の所要時間を制限します。例えば、関数のタイムアウトを 360 秒に設定した場合、関数とすべての拡張機能は 360 秒以内に完了する必要があります。独立した呼び出し後フェーズはないことに注意してください。所要時間はランタイムおよびすべての拡張機能の呼び出しが完了するまでの合計時間であり、関数およびすべての拡張機能の実行が終了するまで計算されません。 パフォーマンスの影響と拡張機能のオーバーヘッド : 拡張機能は、関数のパフォーマンスに影響を与える可能性があります。拡張機能の作成者は、拡張機能のパフォーマンスへの影響を制御する必要があります。例えば、拡張機能でコンピューティング負荷の高い操作を実行した場合、拡張機能と関数コードで同じ CPU リソースを共有するため、関数の実行時間が長くなります。さらに、関数呼び出しの完了後に拡張機能が広範な操作を実行する場合、すべての拡張機能が完了を示すまで Invoke フェーズが継続するため、関数の実行時間が長くなります。 注記 Lambda は、関数のメモリ設定に比例して CPU パワーを割り当てます。関数と拡張機能のプロセスが同じ CPU リソースで競合するため、メモリ設定が小さい場合、実行時間と初期化時間が長くなることがあります。実行時間と初期化時間を短縮するには、メモリ設定を引き上げてみてください。 Invoke フェーズで拡張機能によって発生したパフォーマンスへの影響を確認できるように、Lambda は PostRuntimeExtensionsDuration メトリクスを出力します。このメトリクスでは、ランタイム Next API リクエストから最後の拡張機能の Next API リクエストまでの累積時間が測定されます。使用されるメモリの増加を測定するには、 MaxMemoryUsed メトリクスを使用します。関数のメトリクスの詳細については、「 Lambda での CloudWatch メトリクスの使用 」を参照してください。 関数のデベロッパーは、異なるバージョンの関数を並行して実行して、特定の拡張機能の影響を把握することができます。拡張機能の作成者は、関数のデベロッパーが適切な拡張機能を選択しやすくするために、予想されるリソース消費を公開することをお勧めします。 シャットダウンフェーズ Lambda は、ランタイムをシャットダウンしようとする際に、登録された各外部拡張機能に Shutdown を送信します。拡張機能は、この時間を最終的なクリーンアップタスクに使用できます。 Shutdown イベントは Next API リクエストに応答して送信されます。 所要時間の制限 : Shutdown フェーズの最大所要時間は、登録された拡張機能の設定によって異なります。 0 ms – 登録された拡張機能を持たない関数 500 ms - 登録された内部拡張機能を持つ関数 2000 ms - 登録された外部拡張機能を 1 つ以上持つ関数 ランタイムまたは拡張機能が制限内で Shutdown イベントに応答しない場合、Lambda は SIGKILL の通知を使用してプロセスを終了します。 イベントペイロード : Shutdown イベントには、シャットダウンの理由と残り時間 (ミリ秒単位) が含まれます。 shutdownReason には次の値が含まれています。 SPINDOWN - 正常なシャットダウン TIMEOUT - 所要時間の制限がタイムアウトしました FAILURE - エラー状態 ( out-of-memory イベントなど) { "eventType": "SHUTDOWN", "shutdownReason": "reason for shutdown", "deadlineMs": "the time and date that the function times out in Unix time milliseconds" } アクセス許可と設定 拡張機能は、Lambda 関数と同じ実行環境で実行されます。拡張機能は、CPU、メモリ、 /tmp ディスクストレージなどのリソースも関数と共有します。さらに、関数と同じ AWS Identity and Access Management (IAM) ロールとセキュリティコンテキストが使用されます。 ファイルシステムとネットワークアクセス許可 : 拡張機能は、関数ランタイムと同じファイルシステムおよびネットワーク名の名前空間で実行されます。つまり、拡張機能は関連するオペレーティングシステムと互換性がある必要があります。拡張機能で追加の 送信ネットワークトラフィック ルールが必要な場合は、これらのルールを関数の設定に適用する必要があります。 注記 関数コードディレクトリは読み取り専用であるため、拡張機能は関数コードを変更できません。 環境変数 : 拡張機能は、関数の 環境変数 にアクセスできます。ただし、ランタイムプロセスに固有の次の変数は除きます。 AWS_EXECUTION_ENV AWS_LAMBDA_LOG_GROUP_NAME AWS_LAMBDA_LOG_STREAM_NAME AWS_XRAY_CONTEXT_MISSING AWS_XRAY_DAEMON_ADDRESS LAMBDA_RUNTIME_DIR LAMBDA_TASK_ROOT _AWS_XRAY_DAEMON_ADDRESS _AWS_XRAY_DAEMON_PORT _HANDLER 障害処理 初期化の失敗 : 拡張機能が失敗した場合、Lambda は実行環境を再起動して一貫した動作を適用し、拡張機能のフェイルファストを推奨します。また、お客様によっては、拡張機能が、ログ記録、セキュリティ、ガバナンス、テレメトリ収集などのミッションクリティカルなニーズを満たす必要があります。 呼び出しの失敗 （メモリ不足、関数のタイムアウトなど）： 拡張機能はランタイムとリソースを共有するため、メモリが消耗した場合に影響を受けます。ランタイムが失敗すると、すべての拡張機能とランタイム自体が Shutdown フェーズに参加します。さらにランタイムは、現在の呼び出しの一部として、または遅延された再初期化メカニズムを通じて、自動的に再起動されます。 Invoke 中に障害が発生した場合 (関数のタイムアウトやランタイムエラーなど)、 Lambda サービスはリセットを実行します。リセットは Shutdown イベントのように動作します。まず、Lambda はランタイムをシャットダウンし、登録された各外部拡張機能に Shutdown イベントを送信します。イベントには、シャットダウンの理由が含まれます。この環境が新しい呼び出しに使用される場合、拡張機能とランタイムは次の呼び出しの一部として再初期化されます。 前示の図の詳細については、「 呼び出しフェーズ中の失敗 」を参照してください。 拡張機能のログ : Lambda は、拡張機能のログ出力を CloudWatch Logs に送信します。また Lambda は、 Init 中に各拡張機能に対して追加のログイベントも生成します。ログイベントは、成功時には名前と登録設定 (event、config) を記録し、失敗時には失敗理由を記録します。 拡張機能のトラブルシューティング Register リクエストが失敗した場合は、 Lambda-Extension-Name API コールの Register ヘッダーに拡張機能の完全なファイル名が含まれていることを確認します。 内部拡張機能に対する Register リクエストが失敗した場合は、そのリクエストが Shutdown イベントに登録されていないことを確認します。 拡張機能 API リファレンス 拡張機能 API バージョン 2020-01-01 の OpenAPI 仕様は、こちらから入手できます: extensions-api.zip API エンドポイントの値は、 AWS_LAMBDA_RUNTIME_API 環境変数から取得できます。 Register リクエストを送信するには、各 API パスの前にプレフィックス 2020-01-01/ を使用します。以下に例を示します。 http://$ { AWS_LAMBDA_RUNTIME_API}/2020-01-01/extension/register API メソッド 登録 次へ 初期化エラー 終了エラー 登録 Extension init 中、すべての拡張機能は、イベントを受信するために Lambda に登録される必要があります。Lambda は、拡張機能がブートストラップシーケンスを完了していることを検証するために、拡張機能の完全なファイル名を使用します。したがって、各 Register API コールには、拡張機能の完全なファイル名を持つ Lambda-Extension-Name ヘッダーを含める必要があります。 内部拡張機能はランタイムプロセスによって開始および停止されるため、 Shutdown イベントへの登録は許可されません。 パス – /extension/register メソッド - POST リクエストヘッダー Lambda-Extension-Name - 拡張機能の完全なファイル名。必須: はい。タイプ: 文字列。 Lambda-Extension-Accept-Feature – これを使用して、登録時にオプションの拡張機能を指定します。必須: いいえ。型: カンマで区切られた文字列。この設定を使用して指定できる機能: accountId – これを指定した場合は、拡張機能登録レスポンスに、拡張機能を登録している Lambda 関数に関連付けられたアカウント ID が含まれます。 リクエストボディのパラメータ events - 登録するイベントの配列。必須: いいえ。型: 文字列の配列 有効な文字列: INVOKE 、 SHUTDOWN 。 レスポンスヘッダー Lambda-Extension-Identifier - それ以降のすべてのリクエストに必要な、生成された一意のエージェント識別子 (UUID 文字列)。 レスポンスコード 200 - レスポンス本文には、関数名、関数バージョン、およびハンドラー名が含まれます。 400 – Bad Request 403 – Forbidden 500 – Container error 回復不能な状態。拡張機能はすぐに終了する必要があります。 例 リクエストボディの例 { 'events': [ 'INVOKE', 'SHUTDOWN'] } 例 レスポンスの例 { "functionName": "helloWorld", "functionVersion": "$LATEST", "handler": "lambda_function.lambda_handler" } 例 オプションの accountId 機能が含まれたレスポンスボディの例 { "functionName": "helloWorld", "functionVersion": "$LATEST", "handler": "lambda_function.lambda_handler", "accountId": "123456789012" } 次へ 拡張機能は Next API リクエストを送信して、次のイベント ( Invoke イベントまたは Shutdown イベント) を受信します。レスポンス本文にはペイロードが含まれます。ペイロードは、イベントデータを含む JSON ドキュメントです。 拡張機能は、新しいイベントを受信する準備ができていることを示す Next API リクエストを送信します。これはブロック呼び出しです。 拡張機能は一定期間中断される可能性があるため、返されるイベントが発生するまで、GET 呼び出しにタイムアウトを設定しないでください。 パス – /extension/event/next メソッド - GET リクエストヘッダー Lambda-Extension-Identifier - 拡張機能の一意の識別子 (UUID 文字列)。必須: はい。型: UUID 文字列。 レスポンスヘッダー Lambda-Extension-Event-Identifier – イベントの一意の識別子 (UUID 文字列)。 レスポンスコード 200 - レスポンスには、次のイベント ( EventInvoke または EventShutdown ) に関する情報が含まれます。 403 – Forbidden 500 – Container error 回復不能な状態。拡張機能はすぐに終了する必要があります。 初期化エラー 拡張機能はこのメソッドを使用して、初期化エラーを Lambda に報告します。拡張機能が登録後に初期化に失敗した場合に呼び出します。Lambda がエラーを受信すると、それ以降の API コールは成功しません。拡張機能は、Lambda からの応答を受信した後に終了する必要があります。 パス – /extension/init/error メソッド - POST リクエストヘッダー Lambda-Extension-Identifier - 拡張機能の一意の識別子。必須: はい。型: UUID 文字列。 Lambda-Extension-Function-Error-Type - 拡張機能が検出したエラータイプ。必須: はい。このヘッダーは、文字列値で構成されています。Lambda はどのような文字列でも受け入れますが、形式は <category.reason> にすることが推奨されます。例: Extension.NoSuchHandler Extension.APIKeyNotFound Extension.ConfigInvalid Extension.UnknownReason リクエストボディのパラメータ ErrorRequest - エラーに関する情報。必須: いいえ。 このフィールドは、次の構造を持つ JSON オブジェクトです。 { errorMessage: string (text description of the error), errorType: string, stackTrace: array of strings } Lambda は、 errorType として任意の値を受け入れることに注意してください。 次の例は、呼び出しで指定されたイベントデータを関数で解析できなかった Lambda 関数のエラーメッセージを示しています。 例 関数エラー { "errorMessage" : "Error parsing event data.", "errorType" : "InvalidEventDataException", "stackTrace": [ ] } レスポンスコード 202 - Accepted 400 – Bad Request 403 – Forbidden 500 – Container error 回復不能な状態。拡張機能はすぐに終了する必要があります。 終了エラー 拡張機能は、このメソッドを使用して、終了する前に Lambda にエラーを報告します。予期しない障害が発生したときに呼び出します。Lambda がエラーを受信すると、それ以降の API コールは成功しません。拡張機能は、Lambda からの応答を受信した後に終了する必要があります。 パス – /extension/exit/error メソッド - POST リクエストヘッダー Lambda-Extension-Identifier - 拡張機能の一意の識別子。必須: はい。型: UUID 文字列。 Lambda-Extension-Function-Error-Type - 拡張機能が検出したエラータイプ。必須: はい。このヘッダーは、文字列値で構成されています。Lambda はどのような文字列でも受け入れますが、形式は <category.reason> にすることが推奨されます。例: Extension.NoSuchHandler Extension.APIKeyNotFound Extension.ConfigInvalid Extension.UnknownReason リクエストボディのパラメータ ErrorRequest - エラーに関する情報。必須: いいえ。 このフィールドは、次の構造を持つ JSON オブジェクトです。 { errorMessage: string (text description of the error), errorType: string, stackTrace: array of strings } Lambda は、 errorType として任意の値を受け入れることに注意してください。 次の例は、呼び出しで指定されたイベントデータを関数で解析できなかった Lambda 関数のエラーメッセージを示しています。 例 関数エラー { "errorMessage" : "Error parsing event data.", "errorType" : "InvalidEventDataException", "stackTrace": [ ] } レスポンスコード 202 - Accepted 400 – Bad Request 403 – Forbidden 500 – Container error 回復不能な状態。拡張機能はすぐに終了する必要があります。 ブラウザで JavaScript が無効になっているか、使用できません。 AWS ドキュメントを使用するには、JavaScript を有効にする必要があります。手順については、使用するブラウザのヘルプページを参照してください。 ドキュメントの表記規則 拡張機能パートナー Telemetry API このページは役に立ちましたか? - はい ページが役に立ったことをお知らせいただき、ありがとうございます。 お時間がある場合は、何が良かったかお知らせください。今後の参考にさせていただきます。 このページは役に立ちましたか? - いいえ このページは修正が必要なことをお知らせいただき、ありがとうございます。ご期待に沿うことができず申し訳ありません。 お時間がある場合は、ドキュメントを改善する方法についてお知らせください。 | 2026-01-13T09:29:30 |
https://docs.google.com/document/d/1r_wOqtzmiIyiNWri6U3FKINWdnyHWEMF_lbSCa4jPiw | afalko's Jenkins GSoC 2019 Proposals - Google Docs 자바스크립트가 브라우저에서 활성화되어 있지 않아 이 파일을 열 수 없습니다. 활성화하고 새로고침하세요. 이 브라우저 버전은 더 이상 지원되지 않습니다. 지원되는 브라우저로 업그레이드하세요. afalko's Jenkins GSoC 2019 Proposals Tab 외부 공유 로그인 파일 수정 보기 삽입 서식 도구 확장 프로그램 도움말 접근성 디버그 드라이브에 변경사항이 저장되지 않음 이미지 옵션 이미지 바꾸기 테이블 옵션 접근성 | 2026-01-13T09:29:30 |
https://www.atlassian.com/br/software/loom/ai | Loom AI | Atlassian Close Quer visualizar esta página no seu idioma ? Todos os idiomas Escolha seu idioma 中文 Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Português Pусский Polski Experimente grátis Funções Explore as funções Anotações de reuniões Gravador de tela Capturas de tela Loom AI Edição Back Soluções Equipes Casos de uso Tamanho da empresa Equipes Vendas Marketing Design Suporte Gerenciamento de produtos Desenvolvimento Casos de uso Loom + Jira Loom + Confluence Tamanho da empresa Empresas Back Recursos Preços E mais + Menos - Experimente grátis Back Experimente grátis Aperte "gravar", e a Loom AI faz o resto Compartilhe vídeos perfeitos sem esforço. O Loom AI faz o aprimoramento automático do vídeo e transforma o roteiro em um documento. Teste a Loom AI grátis Grave e compartilhe vídeos 60% mais rápido O Loom AI refina, edita e produz um documento de texto para o vídeo como se fosse mágica Tenha ótimas reuniões com menos trabalho Deixe o Loom AI fazer anotações e coletar itens de ação para manter o andamento do trabalho durante e após as reuniões. Crie e envie com mais rapidez usando fluxos de trabalho de inteligência artificial Documentos prontos para compartilhar com um clique. Os fluxos de trabalho do Loom AI ajudam você a concluir tarefas importantes com rapidez. Teste a Loom AI grátis Escreva um documento Documente o trabalho para ampliar o conhecimento Alinhe com mais rapidez e acelere os sprints com fluxos de trabalho de inteligência artificial que transformam o vídeo em descrições de pull request, SOPs e muito mais. Criar um problema Reporte bugs no Jira ou no Linear com apenas alguns cliques Economize tempo em relatórios de bugs e tickets. O Loom coleta o conteúdo do vídeo e preenche as informações essenciais para o Jira e o Linear. ESCREVA UMA MENSAGEM Envie um contexto automático junto com o link do Loom O Loom gera mensagens escritas para você compartilhar junto com o link do vídeo, seja para enviar um loom via mensagem direta ou e-mail. As mensagens sempre chegam ao destino com o Loom AI Funções Vídeos com Loom AI Vídeos sem o Loom AI Título Vídeos com Loom AI Automático Vídeos sem o Loom AI Manual Resumos Vídeos com Loom AI Automático Vídeos sem o Loom AI Manual Capítulos Vídeos com Loom AI Automático Vídeos sem o Loom AI Manual Tarefas Vídeos com Loom AI Automático Vídeos sem o Loom AI Manual Link de CTA integrado Vídeos com Loom AI Automático Vídeos sem o Loom AI Manual Remoção de palavras de preenchimento Vídeos com Loom AI Automático Vídeos sem o Loom AI Não disponível Remoção de silêncio Vídeos com Loom AI Automático Vídeos sem o Loom AI Não disponível Transformação do vídeo em documento Vídeos com Loom AI Automático Vídeos sem o Loom AI Não disponível Transformação do vídeo em item do Jira ou do Linear Vídeos com Loom AI Automático Vídeos sem o Loom AI Não disponível Transformação do vídeo em mensagem ou e-mail Vídeos com Loom AI Automático Vídeos sem o Loom AI Não disponível A gente fala o seu idioma Disponível em mais de 50 idiomas, o Loom AI aprimora e transforma o vídeo em um documento com base no idioma em que ele foi gravado. Eu estava criando um vídeo para um hack-a-thon e decidi testar os fluxos de trabalho do Loom AI. Eu disse UAU em voz alta depois de usar pela primeira vez. Ele conseguiu coletar etapas precisas em um documento com 20 (APENAS VINTE) segundos de vídeo. Me impressionei muito. Parecia mesmo o futuro. Gerente de Segurança e Confiança, empresa de tecnologia empresarial Novas funções em breve O Loom AI está apenas começando. A gente imagina e trabalha em novas funções avançadas todos os dias! Em breve Ferramentas de desenvolvimento com captura automática Adicione na hora registros de console, informações do navegador e muito mais a tickets do Jira ou Linear Em breve Vozes e avatares por inteligência artificial A conversão de texto em fala e os avatares de inteligência artificial permitem criação de vídeos personalizados em grande escala sem necessidade de regravar. Em breve Conexão ao Confluence Depois que os fluxos de trabalho do Loom AI transformam o vídeo em documento, você pode abrir esse documento na sua ferramenta de colaboração ou projeto. Em breve Inclua mídias automáticas nos guias passo a passo Grave um processo e o Loom AI adiciona videoclipes, GIFs ou capturas de tela para cada etapa. O que os clientes estão falando Dos usuários do Loom, 96% dizem que as funções do pacote de inteligência artificial já são de extremo ou alto valor para os fluxos de trabalho O Loom AI não apenas economiza tempo e esforço, mas também torna os vídeos mais acessíveis e envolventes para o público. 🎥✨ ryan carr Fundador, Tailwind FAQs Como faço para comprar o Loom AI? O administrador da conta pode fazer o upgrade para o plano Business + AI ou Enterprise nas configurações do espaço de trabalho na guia "Plano e faturamento". Posso testar o Loom AI sem custo? Sim, você pode testar o plano Business + AI grátis por 14 dias após se inscrever no Loom. Por que eu deveria fazer o upgrade para o Loom AI? Muitas empresas estão adicionando a inteligência artificial aos produtos. No Loom, a maior prioridade é criar funções de inteligência artificial que promovam a missão de impulsionar uma comunicação eficaz. O pacote do Loom AI (tanto funções atuais como futuras) foi criado para ajudar você a: Trabalhar mais rápido: 67% dos usuários não editam o título automático, ganhando mais eficiência sem investir mais tempo . O pacote do Loom AI reduz o tempo gasto empacotando e compartilhando os Looms após a gravação, para que você possa enviar um vídeo polido e de alta qualidade com rapidez. Aumentar a produtividade: 73% das pessoas disseram que o pacote é de "extremo ou alto valor" para os fluxos de trabalho atuais . O pacote de inteligência artificial reduz a necessidade de regravar os Looms para que a primeira gravação seja a melhor. Manter uma comunicação eficiente: 18% mais engajamento dos espectadores . O pacote de inteligência artificial adiciona contexto instantâneo e automático (título, resumo, capítulos e tarefas) para garantir que a mensagem seja clara e que os espectadores possam consumir e responder com rapidez. Como meus dados são usados? O OpenAI recebe os dados de transcrição como arquivos de texto para gerar títulos e resumos. O OpenAI não recebe vídeos ou áudio completos. A gente envia os dados apenas para sistemas confiáveis de terceiros que estão sujeitos a controles rígidos de privacidade e segurança. Os subprocessadores terceirizados estão sujeitos a acordos com o Loom e/ou usuários para garantir e proteger a confidencialidade dos dados. Além disso, a gente executa acordos de processamento de dados com os subprocessadores. Você pode encontrar mais informações e uma lista dos subprocessadores do Loom aqui . Os termos de inteligência artificial do Loom podem ser encontrados aqui. Com quais idiomas o Loom AI é compatível? As funções de aprimoramento automático do Loom AI (como títulos e resumos automáticos) são geradas em mais de 50 idiomas. No momento a nova função de fluxos de trabalho de inteligência artificial gera documentação apenas em inglês. Em breve, os fluxos de trabalho vão ter compatibilidade com mais idiomas. O Loom funciona em qualquer lugar Para Mac, Windows, iOS e Android Obtenha o Loom grátis Empresa Carreiras Eventos Blogs Relações com investidores Fundação Atlassian Kit de imprensa Fale conosco produtos Rovo Jira Jira Align Jira Service Management Confluence Loom Trello Bitbucket Ver todos os produtos Recursos Suporte técnico Compras e licenciamento Comunidade da Atlassian Base de conhecimento Marketplace Minha conta Criar chamado de suporte Saiba mais Parceiros Treinamento e certificação Documentação Recursos de desenvolvedores Serviços corporativos Ver todos os recursos Copyright © 2025 Atlassian Política de privacidade Termos Aviso legal Escolha o Idioma Deutsch English Español Français Italiano 한국어 Nederlands 日本語 Polski Português русский 中文 | 2026-01-13T09:29:30 |
https://reports.jenkins.io/jelly-taglib-ref.html#hudson | Jelly Taglib references – Jenkins Jenkins Taglib Documentation Last Published: 2025-12-08 | Version: 2.528.3 | Homepage / Jelly Taglib references The following Jelly tag libraries are defined in this project. Namespace URI Description /lib/form /lib/form /lib/hudson /lib/hudson /lib/test /lib/test /lib/hudson/project Tag files used in project pages /lib/layout/dropdowns Tag library that defines components for dropdowns /lib/layout/header Tag library that defines components for headers /lib/layout Tag library that defines the basic layouts of Jenkins pages. /lib/hudson/newFromList These tags provide a higher level primitive for building a form page for creating a new item from a list of descriptors.Used in "create new job" page, for an example. /lib/form /lib/form This tag library is also available as an XML Schema Tag Name Description advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. descriptorRadioList Generate config pages from a list of Descriptors into a section. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) file Generates an input field All unknown attributes are passed through to the field. @since 2.385 form Outer-most tag of the entire form taglib, that generates <form> element. helpArea Place holder to lazy-load help text via AJAX. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 nested number Generates an input field to be used inside <f:entry/> option <option> tag for the <select> element that takes true/false for selected. optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. password Glorified <input type="password"> possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. readOnlyTextbox Generates an input field to be used inside <f:entry/> repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. repeatableDeleteButton Delete button for the <repeatable> tag. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> section Section header in the form table. select Glorified <select> control that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ListBoxModel representation of the items in your drop-down list box, and your instance field should hold the current value. slave-mode A listbox for choosing the agent's usage. submit Submit button. This should be always used instead of the plain <button> tag. textarea <textarea> tag on steroids. The textarea will be rendered to fit the content. It also gets the resize handle. textbox Generates an input field to be used inside <f:entry/> For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support toggleSwitch <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. validateButton See https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ for the reference. withCustomDescriptorByName Execute the body with a temporary currentDescriptorByNameUrl value advanced Expandable section that shows "advanced..." button by default. Upon clicking it, a section unfolds, and the HTML rendered by the body of this tag appears. Attribute Name Type Description title - Caption of the button. By default "Advanced" apply "Apply" button that submits the form but without a page transition. See hudson.util.FormApply for the server-side code. When this button is pressed, the FORM element fires the "jenkins:apply" event that allows interested parties to write back whatever states back into the INPUT elements. Attribute Name Type Description value - The text of the apply button. This tag does not accept any child elements/text. block Full-width space in the form table that can be filled with arbitrary HTML. booleanRadio Binds a boolean field to two radio buttons that say Yes/No OK/Cancel Top/Bottom. Attribute Name Type Description false - Text to be displayed for the 'false' value. Defaults to 'No'. field - Databinding field. true - Text to be displayed for the 'true' value. Defaults to 'Yes'. This tag does not accept any child elements/text. bottomButtonBar Creates a button bar at the bottom of the page for things like "Submit". The actual buttons should be specified as the body of this tag. This area will always be visible at the bottom of the screen. breadcrumb-config-outline Adds one more in-page breadcrumb that jumps to sections in the page. Put this tag right before <l:main-panel> Attribute Name Type Description title - Optional title for this breadcrumb This tag does not accept any child elements/text. checkbox <input type="checkbox"> tag that takes true/false for @checked, which is more Jelly friendly. Attribute Name Type Description checked - class - default - The default value of the checkbox, in case both @checked and @instance are null. If this attribute is unspecified or null, it defaults to unchecked, otherwise checked. description - Optional description for the checkbox field - Used for databinding. TBD. id - json - Normally, the submitted JSON will be boolean indicating whether the checkbox was checked or not. This is sometimes inconvenient if you have a UI that lets user select a subset of a set. If this attribute is present, the submitted JSON will have this as a string value if the checkbox is checked, and none otherwise, making the subset selection easier. name - negative - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. readonly (deprecated) - If set to true, this will take precedence over the onclick attribute and prevent the state of the checkbox from being changed. Note: if you want an actual read only checkbox then add: <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support title - If specified, this human readable text will follow the checkbox, and clicking this text also toggles the checkbox. tooltip - Used as tooltip of the checkbox, and, if a title is specified, of the title value - This tag does not accept any child elements/text. class-entry Invisible <f:entry> type for embedding a descriptor's $class field. Most of the time a Descriptor has an unique class name that we can use to instantiate the right Describable class, so we use the '$class' to represent that to clarify the intent. In some other times, such as templates, there are multiple Descriptors with the same Descriptor.clazz but different IDs, and in that case we put 'kind' to indicate that. In this case, to avoid confusing readers we do not put non-unique '$class'. See Descriptor.newInstancesFromHeteroList for how the reader side is handled. Attribute Name Type Description clazz - The describable class that we are instantiating via structured form submission. descriptor - The descriptor of the describable that we are instantiating via structured form submission. Mutually exclusive with clazz. This tag does not accept any child elements/text. combobox Editable drop-down combo box that supports the data binding and AJAX updates. Your descriptor should have the 'doFillXyzItems' method, which returns a ComboBoxModel representation of the items in your combo box, and your instance field should hold the current value. For a read only input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS classes that the control gets. default - The default value of the combo box, in case both @value and 'instance field ' are null. field - Used for databinding. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. description Renders a row that shows description text below an input field. descriptorList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description description - Optional attribute to set a description for the section descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. field - Either @field or @instances are required (or @field may be inherited from the ancestor <entry> element). If field is specified, instances are assumed to be instance field . When this attribute is specified, JSON structure is properly set up so that the databinding can set the field (or pass this collection as a constructor parameter of the same name. This is more modern way of doing databinding, and thus preferred approach. forceRowSet - If specified, instead of a sequence of <f:optionalBlock>s, draw a sequence of <rowSet>s. icon - Sets the icon on the sidebar item for the section anchor link The icon isn't visible in the section itself instances - Map<Descriptor,Describable> that defines current instances of those descriptors. These are used to fill initial values. Other classes that define the get(Descriptor) method works fine, too, such as DescribableList. targetType - the type for which descriptors will be configured. default to ${it.class} title - Human readable title of the section to be rendered in HTML. descriptorRadioList Generate config pages from a list of Descriptors into a section. Attribute Name Type Description descriptors (required) - hudson.model.Descriptor collection whose configuration page is rendered. instance (required) - The currently configured instance used to fill the initial values of the form. targetType - the type for which descriptors will be configured. default to ${it.class} title (required) - Human readable title of the section to be rendered in HTML. varName (required) - Used as a variable name as well as block name. dropdownDescriptorSelector Renders a single <select> control for choosing a Describable. Depending on the currently selected value, its config.jelly will be rendered below <select>, allowing the user to configure Describable. Attribute Name Type Description capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. default - If specified, this will be chosen as the default value in case the current selection is null. The default can be a specific instance or a descriptor e.g. ${descriptor.defaultSettingsProvider} or ${descriptor.defaultSettingsProvider.descriptor}. In the later case, the from input fields will be empty. descriptors - Collection that lists up all the valid candidate descriptors. If unspecified, inferred from the type of the field. field (required) - Form field name. Used for databinding. title (required) - Human readable title of this control. dropdownList Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description help - Path to the inline help. See <f:entry help="..." /> name (required) - name of the drop-down list. title - Human readable title text of this drop-down listbox. Shown in the same position as <f:entry title="..." /> dropdownListBlock Foldable block expanded when the corresponding item is selected in the drop-down list. Attribute Name Type Description lazy - If specified, the content of the dropdownListBlock will be rendered lazily when it first becomes visible. The attribute value must be the variables to be captured. See the @capture of <renderOnDemand> tag. selected boolean is this value initially selected? staplerClass - provide hint for stapler data binding. typically set to ${descriptor.clazz.name} if dropdownList is for a list of descriptors. title (required) - human readable text displayed for this list item. value (required) - value of the list item. set to <option value="..."> editableComboBox Editable drop-down combo box. Deprecated as of 1.356. Use f:combobox and databinding instead. Attribute Name Type Description clazz - Additional CSS classes that the control gets. field - Used for databinding. items - List of possible values. Either this or nested <f:editableComboBoxValue/>s are required. editableComboBoxValue Used inside <f:editableComboBox/> to specify one value of a combobox. Normally one would use multiple values. Attribute Name Type Description value (required) - This tag does not accept any child elements/text. entry An entry of the <f:form>, which is one logical row (that consists of several <TR> tags. One entry normally host one control. Attribute Name Type Description class - Classes to apply to the form item description - If it's not obvious to the user as to what the control expects, specify some description text (which currently gets rendered as small text under the control, but that may change.) This text shouldn't get too long, and in recent Hudson, this feature is somewhat de-emphasized, in favor of the inline foldable help page specified via @help. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. field - Used for the databinding. TBD. When this attribute is specified, @help is inferred, and nested input controls don't need the @field nor @name. help - URL to the HTML page. When this attribute is specified, the entry gets a (?) icon on the right, and if the user clicks it, the contents of the given URL is rendered as a box below the entry. The URL should return an HTML document wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Hudson, so it's normally something like "/plugin/foobar/help/abc.html". title - Name of the entry. Think of this like a label for the control. This content is HTML (unless the boolean variable escapeEntryTitleAndDescription is set). Use h.escape if necessary. enum Binds an enum field to a <select> element. The body of this tag is evaluated for each enum value, which is passed as 'it'. Attribute Name Type Description default - The name of the enum to set as default value for the first configuration. field - Used for databinding. TBD. enumSet Binds a set of Enum to a list of checkboxes, each with the label taken from enum Enum.toString() Should be used inside an <f:entry field='...'> element. Attribute Name Type Description field - Used for databinding. This tag does not accept any child elements/text. expandableTextbox A single-line textbox that can be expanded into a multi-line textarea. This control is useful for a field that expects multiple whitespace-separated tokens (such as URLs, glob patterns, etc.) When the user only enters a few tokens, they can keep it as a single line to save space, but to enter a large number of values, this can be turned into textarea for better visibility. If the initial value is already multi-line text, the control starts with textarea. On the server side, your program is responsible for treating ' ', \t, \r, and \n for separators. (StringTokenizer would do this.) Attribute Name Type Description field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. file Generates an input field All unknown attributes are passed through to the field. @since 2.385 Attribute Name Type Description accept - Defines the file types the file input should accept. This string is a comma-separated list. clazz - Additional CSS class(es) to add. field - Used for databinding. jsonAware - Enable structured form submission. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. This tag does not accept any child elements/text. form Outer-most tag of the entire form taglib, that generates <form> element. Attribute Name Type Description action (required) - @action of the form field. The URL where the submission is sent. autocomplete - Optional attribute for allowing browsers to perform auto complete or pre-fill the form from history. Default: false class - Classes to apply to the form enctype - @enctype of the <form> HTML element. id - ID of the form. method (required) - Submission method. Either post or get. name (required) - @name of the form. In HTML this is not a mandatory attribute, but in Hudson you should have it for testing and page scraping, so this attribute is marked required. tableClass - Optional class attribute for <table> that is created in the form. target - @target of the <form> HTML element. Works like <a target="..."> and controls which window the result of the submission goes to. helpArea Place holder to lazy-load help text via AJAX. This tag does not accept any child elements/text. helpLink Outputs a help link for a <f:form> item if help is available or a spacer if none is available. The help link is rendered as a table cell with an (?) icon. If the user clicks it, the content of the HTML fragment at the given URL is rendered in the area designated as <f:helpArea> by the caller, usually in a row beneath the item with help. The alternative spacer is just an empty table cell. This tag was introduced to ensure that the space reserved for help items is consistent over the UI whether or not help exists. @since 1.576 Attribute Name Type Description featureName - Name of the feature described by the help text, used for constructing the icon's alt attribute. Optional. url - URL to the HTML page. Optional. If not given, no help icon is displayed. The URL should return a UTF-8 encoded HTML fragment wrapped in a <div> tag. The URL is interpreted to be rooted at the context path of Jenkins, so it's normally something like "/plugin/foobar/help/abc.html". This tag does not accept any child elements/text. hetero-list Outer most tag for creating a heterogeneous list, where the user can choose arbitrary number of arbitrary items from the given list of descriptors, and configure them independently. The submission can be data-bound into List<T> where T is the common base type for the describable instances. For databinding use, please use <f:repeatableHeteroProperty /> Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. descriptors (required) - all types that the user can add. disableDragAndDrop java.lang.Boolean If true the drag and drop will not be activated. This just removes the drag and drop UI, it will not prevent users from manually submitting a different order. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. items (required) java.util.Collection existing items to be displayed. Something iterable, such as array or collection. menuAlign - Menu alignment against the button. Defaults to tl-bl name (required) - form name that receives an array for all the items in the heterogeneous list. oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) titleClassMethod - If set to an item of the form , it will be used to call to calculate each item title. hetero-radio Sibling of hetero-list, which only allows the user to pick one type from the list of descriptors and configure it. Attribute Name Type Description descriptors (required) - all types that the user can add. field (required) - Field name in the parent object where databinding happens. This tag does not accept any child elements/text. invisibleEntry Invisible <f:entry> type. Useful for adding hidden field values. link Generates an anchor element with the ability to send POST requests. @since 1.584 Attribute Name Type Description clazz - Additional CSS classes. href - Link destination URL. post - If this must send a POST request. nested number Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field java.lang.String Used for databinding. TBD. max - The maximum of the @value. This becomes the @max of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be less than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @min is specified and @min is greater than this value, both @min and @max will not work. min - The minimum of the @value. This becomes the @min of the <input> tag. This will work only @clazz is 'number', 'number-required', 'non-negative-number-required', 'positive-number', 'positive-number-required'. If specified, the @value should be greater than this value, or errors will be rendered under the text field. If this value contains non-digit characters, it will not work. If @max is specified and @max is less than this value, both @min and @max will not work. name java.lang.String This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. option <option> tag for the <select> element that takes true/false for selected. Attribute Name Type Description selected boolean If true, the option value appears as selected. value - The value to be sent when the form is submitted. If omitted, the body of the tag will be placed in the value attribute as well (due to the browser incompatibility between IE and Firefox, value attribute must be included). optionalBlock Foldable block that can be expanded to show more controls by checking the checkbox. Attribute Name Type Description checked - initial checkbox status. true/false. field - Used for databinding. TBD. Either this or @name/@title combo is required. help - If present, the (?) icon will be rendered on the right to show inline help. See @help for <f:entry>. inline - if present, the foldable section will not be grouped into a separate JSON object upon submission name - Name of the checkbox. Can be used by the server to determine if the block is collapsed or expanded at the time of submission. Note that when the block is collapsed, none of its child controls will send the values to the server (unlike <f:advanced>) negative - if present, the foldable section expands when the checkbox is unchecked. title - Human readable text that follows the checkbox. If this field is null, the checkbox degrades to a <f:rowSet>, which provides a grouping at JSON level but on the UI there's no checkbox (and you always see the body of it.) optionalProperty Renders inline an optional single-value nested data-bound property of the current instance, by using a <f:optionalBlock> This is useful when your object composes another data-bound object, and when that's optional, where the absence of the value is signified as null (in which case the optionalBlock will be drawn unchecked), and the presence of the value. Attribute Name Type Description field (required) - help - title (required) - This tag does not accept any child elements/text. password Glorified <input type="password"> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. possibleReadOnlyField prepareDatabinding Modifies the 'attrs.field' of the parent to inherit @field from the enclosing <f:entry> if available. Also computes the @checkUrl attribute. This tag does not accept any child elements/text. property Renders inline a single-value nested data-bound property of the current instance. This is useful when your object composes another data-bound object as a nested object, yet your UI would still like to render it Attribute Name Type Description field (required) - propertyDescriptor - If specified, bypass the item descriptor inference and use this instead. This tag does not accept any child elements/text. radio <input type="radio"> tag that takes true/false for @checked, which is more Jelly friendly. Note that Safari doesn't support onchange. Beware that the name attribute should be uniquified among all radio blocks on the page, such as by prefixing it with "G0025." or whatever gensym. For a read only radio input set <j:set var="readOnlyMode" value="true"/> inside your entry tag See https://www.jenkins.io/doc/developer/views/read-only/#enabling-read-only-view-support Attribute Name Type Description checked - id - name - onclick (deprecated) - Inline JavaScript to execute when the checkbox is clicked. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'class' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. title - If specified, this human readable text will follow the radio, and clicking this text also toggles the radio. value - radioBlock Radio button with a label that hides additional controls. When checked, those additional controls are displayed. This is useful for presenting mutually exclusive options, where each option comes with a sub-form that provides additional configuration. Attribute Name Type Description checked (required) boolean Should this control be initially checked or not? help - If specified, the (?) help icon will be rendered on the right, for in place help text. See <f:entry> for the details. inline - if present, the folded section will not be grouped into a separate JSON object upon submission. name (required) - Name of the radio button group. Radio buttons that are mutually exclusive need to have the same name. title (required) - Human readable label text to be rendered next to the radio button. value (required) - @value of the <input> element. readOnlyTextbox Generates an input field to be used inside <f:entry/> Attribute Name Type Description checkMessage - Override the default error message when client-side validation fails, as with clazz="required", etc. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the recommended approach. clazz - Additional CSS class(es) to add (such as client-side validation clazz="required", "number" or "positive-number"; these may be combined, as clazz="required number"). default - The default value of the text box, in case both @value is and 'instance field ' is null. field - Used for databinding. TBD. name - This becomes @name of the <input> tag. If @field is specified, this value is inferred from it. onchange (deprecated) - Inline JavaScript to execute when the textbox is changed. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. onkeyup (deprecated) - Inline JavaScript to execute when the keyup event is fired. Deprecated because this attribute is incompatible with adding Content-Security-Policy to the Jenkins UI in the future. Set 'id' or 'clazz' attributes as appropriate to look up this element in external Javascript files (e.g. adjuncts) to add the desired behavior there (DOMContentLoaded event in static forms, Behaviour.specify if this element may be dynamically added). See https://github.com/jenkinsci/jenkins/pull/6852 for an example. value - The initial value of the field. This becomes the @value of the <input> tag. If @field is specified, the current property from the "instance" object will be set as the initial value automatically, which is the recommended approach. This tag does not accept any child elements/text. repeatable Repeatable blocks used to present UI where the user can configure multiple entries of the same kind (see the Java installations configuration in the system config.) This tag works like <j:forEach> and repeatedly evaluate the body so that initially all the items get their own copy. This tag also evaluate the body once more with var=null to create a 'master copy', which is the template entry used when a new copy is inserted. HTML structure This tag mainly produces the nested DIVs with CSS classes as follows: <div class="repeated-container"> // container for the whole thing <div class="repeated-chunk"> ... copy 1 ... <div class="repeated-chunk"> ... copy 2 ... ... The 'repeated-chunk' DIVs will also have additional CSS classes that represent their positions among siblings: first : first chunk among the siblings last : last chunk among the siblings middle: neither first nor last only : it is the only chunk (automatically get first and last at the same time) Usage Note The caller of this tag should define a button to add a new copy and delete the current copy. Such buttons should have 'repeatable-add' CSS class and 'repeatable-delete' CSS class respectively (it can have other CSS classes), so that their event handlers get properly wired up. The positional CSS classes on 'repeated-chunk' DIVs (as explained above) can be used to control the visibility of such buttons. For example, this allows you to hide 'delete' button if there's only one item, or only show 'add' button on the last row. There are a few CSS classes already defined in style.css for this purpose. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - Use this collection for items if items or @field is null enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). items - The item collection to loop over. Required unless @field is given. minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. name - name used in the structured form submission. Defaults to the same name as @var. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, var - variable that receives the item of the current iteration. Accessible from the body. Required unless @field is given. varStatus - Status variable that indicates the loop status. repeatableDeleteButton Delete button for the <repeatable> tag. Attribute Name Type Description value - Caption of the button. Defaults to 'Delete'. This tag does not accept any child elements/text. repeatableHeteroProperty Data-bound only version of <f:hetero-list> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Attribute Name Type Description addCaption - caption of the 'add' button. capture - Config fragments from descriptors are rendered lazily by default, which means variables seen in the caller aren't visible to them. This attribute allows you to nominate additional variables and their values to be captured for descriptors. deleteCaption - caption of the 'delete' button. field - Used for the data binding. hasHeader - For each item, add a caption from descriptor.getDisplayName(). This also activates drag&drop (where the header is a grip), and help text support. honorOrder - If true, insert new addition by default to their 'desired' location, which is the order induced by the descriptors. menuAlign - Menu alignment against the button. Defaults to tl-bl oneEach - If true, only allow up to one instance per descriptor. targetType - the type for which descriptors will be configured. Defaults to ${it.class} (optional) This tag does not accept any child elements/text. repeatableProperty Data-bound only version of <f:repeatable> that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. Unless that nested config.jelly already adds a delete button (deprecated), you should normally put the following inside this tag: <f:block> <div align="right"> <f:repeatableDeleteButton /> </div> </f:block> Due to a bug in Stapler data binding the model elements are only set if they consist of one or more values. If all values have been removed in the user interface (i.e. the associated form is empty), then the setter is not invoked anymore. As a workaround, you need to override the corresponding configure method and clear the model property manually before invoking the data binding. See warnings-ng-plugin PR#266. Attribute Name Type Description add - If specified, this text will replace the standard "Add" text. default - The default value to use for this collection when 'instance field ' is null. enableTopButton - true if a new Add button, for adding new copy of repeatable item, should be displayed above repeatable form. Display of top button depends also on number of items. If there is no item, only one button is displayed. When at least one item is present, there are two buttons displayed (only when enableTopButton is true). One above and one below. Top button adds item on top of repeatable form. Bottom button adds item on the bottom of repeatable form. field - Used for the data binding. header - For each item, add this header. This also activates drag&drop (where the header is a grip). minimum - At least provide this number of copies initially. minimum="1" is useful to make sure there's always at least one entry for the user to fill in. noAddButton - true if the default 'add' button (that adds a new copy) shouldn't be displayed. When you use this attribute, rowSet Adds @nameRef to all table rows inside this tag, so that when the form is submitted, it gets grouped in one JSON object. Attribute Name Type Description name - if the group head is not available outside, use this attribute to specify the name. @name and @ref are mutually exclusive. ref - id of the thing that serves as the group head, if that's available separately saveApplyBar Creates the bottom bar for the "Save" and "Apply" buttons. In read only mode (<j:set var="readOnlyMode" value="true"/>) the buttons are not displayed. This tag does not accept any child elements/text. secretTextarea Enhanced version of <f:textarea/> for editing multi-line secrets. Example usage: <j:jelly xmlns:j="jelly:core" xmlns:f="/lib/form"> <f:entry title="Secret" field="secret"> <f:secretTextarea/> </f:entry> <f:entry title="Secret 2"> <f:secretTextarea field="secret2"/> </f:entry> <f:entry title="Another Secret"> <f:secretTextarea name="foo" value="${it.foo}"/> </f:entry> </j:jelly> Attribute Name Type Description checkMethod String Specify 'get' (must be lowercase) to change the HTTP method used for the AJAX requests to @checkUrl from a POST to a GET. If any other value is specified then requests will use POST. The historical default was GET and 'post' had to be specified to change that, but this was changed in Jenkins 2.285. checkUrl - If specified, the value entered in this input field will be checked (via AJAX) against this URL, and errors will be rendered under the text field. If @field is specified, this will be inferred automatically, which is the r | 2026-01-13T09:29:30 |
https://wordpress.com/zh-cn/patterns | WordPress 区块样板：让您的网页构建速度提升 10 倍 — WordPress.com WordPress.com Products WordPress Hosting WordPress for Agencies Become an Affiliate Domain Names AI Website Builder Website Builder Create a Blog Newsletter Professional Email Commerce WordPress Studio Enterprise WordPress Features Overview WordPress Themes WordPress Plugins WordPress Patterns Google Apps Resources WordPress.com Support WordPress News Business Name Generator Logo Maker Discover New Posts Popular Tags Blog Search Plans & Pricing Log In Get Started Menu Close the navigation menu Get Started Sign Up Log In About Plans & Pricing Products WordPress Hosting WordPress for Agencies Become an Affiliate Domain Names AI Website Builder Website Builder Create a Blog Newsletter Professional Email Commerce WordPress Studio Enterprise Features Overview WordPress Themes WordPress Plugins WordPress Patterns Google Apps Resources WordPress.com Support News Business Name Generator Logo Maker Discover New Posts Popular Tags Blog Search 用样板更快地构建 深入了解数百种经过专业设计的完全响应式布局，让任何类型的站点更快焕发生机。 所有分类 页眉 尾部 404模板 关于 归档模板 博文 联系 活动 表单 画廊 Hero 自介连结 位置 菜单 电子报 页面模板 页面标题 作品集 文章模板 定价 搜索模板 服务 团队 褒奖 用样板来建造任何东西 从美观、实用的设计样板库中进行选择，快速构建您或您的客户所需的页面。 标题 1 复制样板 页眉 8 个样板 页脚：营业时间，社交媒体，联系方式 复制样板 尾部 13 个样板 404 模板 1 复制样板 404模板 1 个样板 捐赠 复制样板 关于 10 个样板 归档模板 复制样板 归档模板 2 个样板 文章 (页面) 复制样板 博文 7 个样板 联系方式 1 复制样板 联系 8 个样板 事件（页面） 复制样板 活动 10 个样板 联系方式 1 复制样板 表单 7 个样板 画廊：两列文字和图像 复制样板 画廊 7 个样板 英雄 1 复制样板 Hero 13 个样板 链接在个人资料 3 复制样板 自介连结 3 个样板 地图 4 复制样板 位置 5 个样板 菜单 2 复制样板 菜单 5 个样板 电子报：左侧有图像的注册 复制样板 电子报 4 个样板 页面 - 图像优先 复制样板 页面模板 2 个样板 页面标题 1 复制样板 页面标题 2 个样板 投资组合 1 复制样板 作品集 2 个样板 单个文章偏移 复制样板 文章模板 5 个样板 定价 6 复制样板 定价 6 个样板 搜索结果照片 复制样板 搜索模板 4 个样板 服务 (页面) 复制样板 服务 10 个样板 团队 3 复制样板 团队 7 个样板 评论 3 复制样板 褒奖 6 个样板 复制、粘贴、自定义 — 就是这么简单 挑选一种样板，将其复制粘贴到您的设计中，然后按照您喜欢的方式进行自定义。 无需插件。 复制粘贴您的方式 将样板直接粘贴到 WordPress 编辑器中，对其进行完全自定义。 展现您自己的风格 样板会复制您站点的排版和调色板，确保每个页面都符合品牌形象。 打造您自己的站点 样板是常规 WordPress 区块的集合，因此您可以随心所欲地编辑每处细节。 响应式设计 所有样板均采用完全响应式设计，确保在任何设备或屏幕上都能完美呈现。 精美、精心策划的页面布局 我们的页面布局正是您需要的，可以轻松使用预先组装的样板来创建专业外观的页面。 文章 (页面) 复制样板 博文 3个布局 复制样板 联系 1个布局 事件（页面） 复制样板 活动 1个布局 画廊：两列文字和图像 复制样板 画廊 4个布局 菜单 (页面) 复制样板 菜单 1个布局 定价（页面） 复制样板 定价 1个布局 服务 (页面) 复制样板 服务 1个布局 所有关于样板 查看我们的操作指南，开始使用样板。 构建站点 视频教程 区块样板 视频教程 使用预制页面布局 免费课程 更快地启动您的站点 WordPress.com Products WordPress Hosting WordPress for Agencies Become an Affiliate Domain Names AI Website Builder Website Builder Create a Blog Professional Email Website Design Services WordPress Studio WordPress Enterprise Features Overview WordPress Themes WordPress Plugins WordPress Patterns Google Apps Resources WordPress.com Support WordPress Forums WordPress News Business Name Generator Logo Maker Discover New Posts Popular Tags Blog Search Developer Resources Accessibility Company About Press Terms of Service Privacy Policy Language Change Language English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Română Svenska Türkçe Русский Ελληνικά العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 Mobile Apps Get it on Google Play Download on the App Store Social Media WordPress.com on X (Twitter) WordPress.com on Facebook WordPress.com on Instagram WordPress.com on YouTube Automattic Work With Us Work With Us Please enable JavaScript in your browser to enjoy WordPress.com. | 2026-01-13T09:29:30 |
https://wordpress.com/ko/hosting/ | 관리형 워드프레스 호스팅 | 엄청난 속도. 강력한 보안 | WordPress.com 제품 기능 리소스 요금제 및 가격 로그인 사이트 만들기 메뉴 WordPress 호스팅 에이전시용 WordPress 제휴사 되기 도메인 네임 AI 웹사이트 제작 도구 웹사이트 제작 도구 블로그 생성 뉴스레터 Professional Email 웹사이트 디자인 서비스 상거래 워드프레스 스튜디오 엔터프라이즈 워드프레스 전체 보기 WordPress 테마 WordPress 플러그인 워드프레스 패턴 Google Apps 지원 센터 WordPress 뉴스 비즈니스 이름 생성 도구 로고 메이커 새 글 발견하기 인기있는 태그 블로그 검색 탐색 메뉴 닫기 시작하기 가입 로그인 정보 요금제 및 가격 제품 WordPress 호스팅 에이전시용 WordPress 제휴사 되기 도메인 네임 AI 웹사이트 제작 도구 웹사이트 제작 도구 블로그 생성 뉴스레터 Professional Email 웹사이트 디자인 서비스 상거래 워드프레스 스튜디오 엔터프라이즈 워드프레스 기능 전체 보기 WordPress 테마 WordPress 플러그인 워드프레스 패턴 Google Apps 리소스 지원 센터 WordPress 뉴스 비즈니스 이름 생성 도구 로고 메이커 새 글 발견하기 인기있는 태그 블로그 검색 젯팩 앱 더 알아보기 무한한 성능, 탁월한 가동 시간 무제한 성능, 탁월한 속도, 흔들림 없는 안정성을 갖춘 WordPress 사이트를 호스팅하세요. 연간 요금제에서는 모두 /월 입니다. 1년간 사용할 수 있는 무료 도메인 14일 환불 보장 무료 이전 사이트 만들기 14일 환불 보장 성능 풀스택 성능 고성능 CPU WordPress.com 사이트는 WordPress와 WooCommerce의 특정 쿼리를 놀라운 속도로 처리할 수 있는 고성능 CPU를 사용합니다. 이미지 중간 단계 오프로딩 성능 저하 없이 저장 공간 비용을 절감하세요. 이미지 썸네일을 실시간으로 생성하고 사용하지 않는 크기의 이미지는 필요할 때까지 클라우드로 전송하여 보관합니다. 자동 버스트 스케일링 트래픽 급증에도 걱정 없이 대응하세요. 맞춤형 리소스 관리 시스템이 자동으로 100개 이상의 PHP 워커로 스케일링됩니다. 전 세계 배포 전 세계 육대주에 위치한 28개 이상의 데이터센터에서 지원하는 글로벌 에지 캐시와 CDN을 통해 방문자와 가장 가까운 곳에서 콘텐츠를 제공합니다. 사이트 만들기 사이트 이전 안정성 실패란 없습니다 무제한 트래픽과 중단 없는 가동 시간 모든 요금제에서 가동 시간 99.999%와 완전 무제한 대역폭과 트래픽을 제공하므로 아무 걱정 없이 성공 가도를 달릴 수 있습니다. 실시간 백업과 원클릭 복원 사이트의 모든 부분이 실시간으로 백업됩니다. 누락된 파일을 복원해야 할 때는 클릭 한 번이면 됩니다. 자동화된 데이터센터 장애 조치 모든 WordPress.com 사이트는 실시간으로 다른 지역에 있는 두 번째 데이터 센터에 복제됩니다. 이러한 아키텍처를 통해 99.999%의 가동 시간을 보장합니다. 전문가 지원 어떤 작업을 시도하든 문제가 발생할 때는 언제나 해피니스 엔지니어의 지원을 받으실 수 있습니다. 사이트 만들기 사이트 이전 고객이 말하는 WordPress.com “WordPress.com과 함께라면 안심할 수 있습니다. 사이트 속도가 느려질 걱정이 없고 다운되지 않으며 해킹당할 위험도 없습니다. 어려운 일은 WordPress.com이 모두 알아서 처리합니다.” Chris Coyier 고객이 말하는 WordPress.com “저희는 고객에게 망설임 없이 추천할 수 있는 신뢰할 만한 호스팅 서비스를 제공하고 싶었습니다. 고객이 만족하기를 원했으니까요. 그 답은 WordPress.com이었습니다.” Ajit Bohra, LUBUS 설립자 WordPress.com 소식 고객이 말하는 WordPress.com “우리는 WordPress.com으로 이전하면서 당시 월 15유로를 지불했습니다. 450유로였던 비용이 15유로로 줄어든 거죠. 그 이후로 사이트 속도, 안정성, 가동 시간 면에서 문제를 겪은 적이 없습니다.” Tommaso Pirola AWS에서 WordPress.com으로 전환한 장기 고객 고객이 말하는 WordPress.com “WordPress.com으로 사이트를 이전한 후, WordPress 업그레이드로 인해 사이트가 다운된 적이 단 한 번도 없었습니다. 철저한 테스트와 품질 보증 덕분에 저는 사이트가 WordPress 업그레이드로 인해 문제를 겪은 적이 없다고 자랑스럽게 말할 수 있습니다.” Antony Agnel AntonyAgnel.com 고객이 말하는 WordPress.com “두 번의 모니터링에서 완벽한 가동 시간을 보여주었습니다. WordPress.com은 WP Bench 테스트에서도 가장 빠른 점수와 A+ SSL 등급을 기록했습니다. WordPress는 이 모든 테스트를 흠잡을 데 없이 통과했다고 말할 수 있습니다.” WP Hosting Benchmarks WPhostingbenchmarks.com 고객이 말하는 WordPress.com “WordPress.com은 월 290만 이상의 페이지뷰를 기록하는 Deepak의 웹사이트를 효율적으로 관리하고 있습니다. 특히 대량의 트래픽을 매끄럽게 처리하는 플랫폼의 능력에 Deepak은 매우 만족하고 있습니다.” Deepak Kumar 비즈니스 요금제 고객 사례 확장성 빌더를 위해 빌더가 제작합니다 플러그인, 테마, 사용자 정의 코드 50,000개 이상의 플러그인과 테마에 대한 풍부한 지원과 자동 업데이트를 통해 무엇이든 만들어보세요. 아니면 자체 사용자 정의 코드로 처음부터 시작해도 좋습니다. SSH, WP-CLI, GitHub 배포 기존에 사용하던 도구로 WP-CLI 명령을 실행하고 GitHub로 배포 를 자동화하고 사용자 정의 코드를 디버깅하세요. 스테이징 사이트 변경 사항을 WordPress.com 스테이징 사이트에서 먼저 테스트하세요. 그러면 라이브 사이트에 영향을 미치지 않고 취약성을 파악하고 해결할 수 있습니다. Jetpack 고급 기능 Jetpack을 신뢰하는 500만 명 이상의 사용자가 추가 보안, 성능, 성장 기능을 통해 사이트를 한 단계 업그레이드하고 있습니다. 사이트 만들기 사이트 이전 보안 보안에 진심입니다 DDoS 및 WAF 방지 WordPress.com이 여러분을 대신하여 매일 수백만 건의 악의적인 요청을 차단하고 있으므로 해킹이나 공격 시도에 대한 걱정 없이 안심하고 숙면을 취할 수 있습니다. 악성코드 검사 및 제거 자동 악성코드 검사와 원클릭 수정으로 보안 위협을 떨쳐버리세요. 실시간 활동 로그 실시간 활동 로그를 통해 사이트에서 발생하는 모든 활동을 파악하세요. 낮이든 밤이든 문제가 생기는 즉시 알게 됩니다. 무료 SSL 인증서 추가 비용 없이 사이트를 HTTP에서 HTTPS로 전환하세요. WordPress.com에 등록하고 연결한 모든 도메인은 무료 SSL 인증서를 통해 암호화됩니다. 사이트 만들기 사이트 이전 누구에게나 알맞은 요금제가 있습니다 무엇을 제작하든 세계에서 가장 좋은 관리형
WordPress 호스팅 스택에서 제작하세요. 추가 요금이 없고 사용량 제한도 없으므로 예상치 못한 비용이 발생할 일도 없습니다. 워드프레스닷컴 요금제 연 단위로 결제 월 단위 결제 연 단위로 결제 2년마다 결제 3년마다 결제 WP Cloud는 확장 가능하고 가용성이 높으며 매우 빠른 WordPress 호스팅을 추가하는 데 필요한 도구를 제공합니다. 비즈니스 WordPress 전문가가 구축한 관리형 호스팅 플랫폼으로 WordPress의 잠재력을 잠금 해제하세요. $ 40 $ 25 $ 20 $ 17.50 매달, 12개월마다 청구됨 매달, 24개월마다 청구됨 매달, 36개월마다 청구됨 연 단위 결제로 %s% 절약 Save 37% Save 50% Save 56% 1년간 사용할 수 있는 무료 도메인 저장 공간 50GB 50GB 요금제에 포함됨 50GB + 50GB 50GB + 100GB 50GB + 150 GB 50GB + 200GB 50GB + 250GB 50GB + 300GB 50GB + 350GB 저장 공간 50GB 비즈니스 받기 비즈니스 받기 비즈니스 받기 비즈니스 받기 50GB 50GB 요금제에 포함됨 50GB + 50GB 50GB + 100GB 50GB + 150 GB 50GB + 200GB 50GB + 250GB 50GB + 300GB 50GB + 350GB 저장 공간 50GB 무제한 페이지, 글, 사용자, 방문자 무제한 페이지, 글, 사용자, 방문자 1년간 사용할 수 있는 무료 도메인 1년간 사용할 수 있는 무료 도메인 myowndomain.com 같은 사용자 정의 도메인을 첫해에 무료로 이용하세요. 방문자를 위한 광고 없는 탐색 환경 방문자를 위한 광고 없는 탐색 환경 방문자에게 광고 없는 깔끔한 사이트 환경을 제공하세요. 모든 프리미엄 테마 모든 프리미엄 테마 프리미엄 디자인 테마 컬렉션을 이용하세요. 전문가 팀의 연중무휴 24시간 우선 지원 전문가 팀의 연중무휴 24시간 우선 지원 연중무휴 24시간 전문적이고 친절한 해피니스 팀의 빠른 지원. 프리미엄 통계 프리미엄 통계 UTM 추적과 기기 인사이트를 포함한 모든 통계를 잠금 해제하세요. 플러그인 설치 플러그인 설치 플러그인을 설치하면 사이트의 기능이 확장될 뿐 아니라 콘텐츠를 멋지게 소개하고 방문자와 소통할 무한한 가능성의 문이 열립니다. 사이트 전체 글꼴과 색상 사용자 정의 사이트 전체 글꼴과 색상 사용자 정의 사이트 디자인의 모든 글꼴, 색상 등 세부 사항을 제어합니다. Google Analytics 연결 Google Analytics 연결 계정을 연결하고 몇 초 만에 더욱 가치 있는 인사이트를 얻으세요. 코딩이 필요하지 않습니다. 비디오 업로드 비디오 업로드 mp4와 같은 동영상 파일을 업로드하고 방해가 되는 광고 없이 픽처 인 픽처, 자막 기능이 포함된 4K 해상도 영상을 아름답게 표시합니다. SFTP/SSH, WP-CLI, Git 명령, GitHub 배포 SFTP/SSH, WP-CLI, Git 명령, GitHub 배포 익숙한 개발자 도구를 사용하여 사이트를 관리하고 배포하세요. Popular WooCommerce의 강력한 기능으로 꿈꾸던 온라인 스토어를 현실로 만드세요. 상거래 기본 제공 프리미엄 확장 기능으로 강력한 온라인 스토어를 만드세요. $ 70 $ 45 $ 36 $ 31.50 매달, 12개월마다 청구됨 매달, 24개월마다 청구됨 매달, 36개월마다 청구됨 연 단위 결제로 %s% 절약 Save 35% Save 48% Save 55% 1년간 사용할 수 있는 무료 도메인 저장 공간 50GB 50GB 요금제에 포함됨 50GB + 50GB 50GB + 100GB 50GB + 150 GB 50GB + 200GB 50GB + 250GB 50GB + 300GB 50GB + 350GB 저장 공간 50GB 상거래 받기 상거래 받기 상거래 받기 상거래 받기 50GB 50GB 요금제에 포함됨 50GB + 50GB 50GB + 100GB 50GB + 150 GB 50GB + 200GB 50GB + 250GB 50GB + 300GB 50GB + 350GB 저장 공간 50GB 무제한 페이지, 글, 사용자, 방문자 무제한 페이지, 글, 사용자, 방문자 1년간 사용할 수 있는 무료 도메인 1년간 사용할 수 있는 무료 도메인 myowndomain.com 같은 사용자 정의 도메인을 첫해에 무료로 이용하세요. 방문자를 위한 광고 없는 탐색 환경 방문자를 위한 광고 없는 탐색 환경 방문자에게 광고 없는 깔끔한 사이트 환경을 제공하세요. 모든 프리미엄 테마와 스토어 테마 모든 프리미엄 테마와 스토어 테마 모든 테마 중에서 원하는 테마로 자유롭게 전환하세요. 전문가 팀의 연중무휴 24시간 우선 지원 전문가 팀의 연중무휴 24시간 우선 지원 연중무휴 24시간 전문적이고 친절한 해피니스 팀의 빠른 지원. 프리미엄 통계 프리미엄 통계 UTM 추적과 기기 인사이트를 포함한 모든 통계를 잠금 해제하세요. 플러그인 설치 플러그인 설치 플러그인을 설치하면 사이트의 기능이 확장될 뿐 아니라 콘텐츠를 멋지게 소개하고 방문자와 소통할 무한한 가능성의 문이 열립니다. 사이트 전체 글꼴과 색상 사용자 정의 사이트 전체 글꼴과 색상 사용자 정의 사이트 디자인의 모든 글꼴, 색상 등 세부 사항을 제어합니다. Google Analytics 연결 Google Analytics 연결 계정을 연결하고 몇 초 만에 더욱 가치 있는 인사이트를 얻으세요. 코딩이 필요하지 않습니다. 비디오 업로드 비디오 업로드 mp4와 같은 동영상 파일을 업로드하고 방해가 되는 광고 없이 픽처 인 픽처, 자막 기능이 포함된 4K 해상도 영상을 아름답게 표시합니다. SFTP/SSH, WP-CLI, Git 명령, GitHub 배포 SFTP/SSH, WP-CLI, Git 명령, GitHub 배포 익숙한 개발자 도구를 사용하여 사이트를 관리하고 배포하세요. 전자상거래 도구와 최적화된 WooCommerce 경험 전자상거래 도구와 최적화된 WooCommerce 경험 WooCommerce가 실행되는 사이트의 성능과 보안을 향상시키도록 만든 맞춤형 호스팅 솔루션을 경험하세요. 엔터프라이즈 WordPress 호스팅을 위한 신뢰할 수 있는 선택. 엔터프라이즈 WordPress의 편의성과 유연성에 더하여 탁월한 확장성, 보안, 데이터 중심 기능까지 제공합니다. $ $ $ $ US$25,000 /년부터 시작 US$25,000 /년부터 시작 US$25,000 /년부터 시작 US$25,000 /년부터 시작 문의하기 문의하기 문의하기 문의하기 요금제 비교 고객이 사용할 사이트를 제작하시나요? 더 많은 수익을 올릴 방법이 있습니다. 사이트를 WordPress.com 플랫폼으로 이전하고 고객에게 Automattic 제품을 홍보하면 호스팅에 대한 대량 구매 할인을 받을 뿐 아니라 최대 50%의 수익을 공유받을 수 있습니다. 오늘부터 제작하고 수익 얻기 질문에 답해드립니다 호스팅에 대해 알아야 할 모든 정보를 알려드립니다. 사이트 만들기 사이트 이전 다른 서비스에서 콘텐츠를 가져올 수 있나요? Blogger, GoDaddy, Wix, Squarespace 등 다양한 다른 블로깅 플랫폼에서 블로그 콘텐츠 가져오기 가 가능합니다. 독립형 호스트 WordPress 사이트에서 콘텐츠 가져오기 도 손쉽게 하실 수 있습니다. 트래픽과 대역폭이 정말 무제한인가요? 물론입니다! WordPress.com에서는 예상치 못한 사용 요금을 절대 부과하지 않습니다. 무한히 확장할 수 있고 전 세계적으로 분산된 서버 인프라는 여러분의 사이트를 언제나 빠르게 로딩하며 사이트 인기가 아무리 치솟아도 안정적으로 운영됩니다. 제가 소유하고 있던 도메인을 사용할 수 있나요? 네, 모든 WordPress.com 유료 요금제에서는 무료로 도메인을 연결 할 수 있습니다(별도의 도메인 등록 수수료를 청구하지 않습니다). 원하는 대로 도메인 을 현재 등록기관에 유지해도 되고 저희 플랫폼으로 이전해도 됩니다. 여러 사이트를 호스팅할 수 있나요? 네, 호스팅하는 사이트 개수에는 제한이 없습니다. 그 대신 사이트별로 별도의 요금제 가 필요합니다. 각 사이트에 적절한 요금제를 개별적으로 선택할 수 있으므로 필요한 기능에 대해서만 비용을 지불하시면 됩니다. 또한, WordPress.com과 Jetpack에 연결된 모든 웹사이트를 하나의 간단하고 중앙화된 관리 도구에서 관리할 수 있는 알림판을 제공합니다. 환불 정책이 궁금합니다 저희 제품에 만족하지 못하신다면 환불 기간 내에 언제든지 취소할 수 있습니다. 이유를 불문하고 신속하고 정중하게 환불해 드립니다. 환불 기간은 다음과 같습니다. 연간 WordPress.com 요금제: 14일 월간 WordPress.com 요금제: 7일 신규 도메인 등록: 96시간 기존 사이트를 이전하고 싶은데 지금 요금제를 구매하면 해당 사이트가 중단되나요? 아니요. 그렇지 않습니다! 저희와 함께 새로운 사이트를 먼저 제작한 후에 도메인을 연결하시면 됩니다. 이렇게 하면 새 사이트가 준비될 때까지 현재 사이트를 “라이브” 상태로 유지할 수 있습니다. 요금제는 지금 구매하는 것이 좋습니다. 요금제는 여러 유용한 기능 을 제공하며 특히 전문가의 연중무휴 24시간 우선 지원을 받을 수 있습니다. 단, 도메인 옵션은 해당 옵션을 준비가 될 때까지 사용하지 마세요. 도메인은 준비가 된 이후에 연결하거나 이전하는 것이 좋습니다. 이메일 계정을 받을 수 있나요? 물론입니다! 다양한 요구 사항에 맞는 여러 옵션 을 제공해 드립니다. 대부분의 고객에게는 Professional Email 서비스가 현명한 선택입니다. 이 안정적인 이메일 솔루션은 WordPress.com에 호스팅된 모든 도메인에서 이용할 수 있습니다. Google Workspace 통합도 제공해 드립니다. 더 간단한 옵션을 원하는 사용자라면 무료로 이메일 전달도 설정할 수 있습니다. 플러그인을 설치할 수 있나요? 네, 비즈니스 또는 상거래 요금제에서는 WordPress 저장소에 있는 50,000개 이상의 플러그인 을 검색하여 설치할 수 있습니다. 제가 소유하고 있는 테마를 설치할 수 있나요? 네, 모든 요금제에서는 저희 전문가들이 엄선하고 검토한 무료 테마, 프리미엄 테마 의 디렉터리에 접근 권한이 제공됩니다. WordPress.com 비즈니스 또는 상거래 요금제에서는 테마를 원하는 대로 설치할 수 있습니다. 사이트 제작을 의뢰할 수 있나요? 당연히 가능합니다! 웹사이트 제작을 의뢰하고 싶다면 프리미엄 사이트 설정 서비스인 Website Design Service를 살펴보세요. 저희 전문가들이 사이트를 제작해 드리며 영업일 기준 4일이면 라이브로 전환할 준비가 완료됩니다. 자세히 알아보려면 여기를 클릭 하세요. 실제 사람과 이야기할 수 있나요? 저희는 여러분과의 대화를 환영합니다! 모든 유료 요금제에는 해피니스 엔지니어라고 부르는 WordPress 전문가 팀의 일대일 지원 을 이용할 수 있는 권한이 포함되어 있습니다. 엔터프라이즈/성장하는 기업을 위한 WordPress 옵션이 있나요? Automattic 제품군과 WordPress에 기반한 WordPress VIP는 이러한 기업에 가장 완벽한 솔루션 입니다. 이들이 필요로 하는 탁월한 확장성, 보안, 데이터 중심적 기능과 WordPress의 편의성과 유연성이 합쳐진 제품입니다. WordPress VIP는 웹에서 가장 큰 웹사이트, 기업, 그리고 정부 기관을 지원하며, 그들이 콘텐츠를 제한 없이 대규모로 생산할 수 있도록 돕습니다. WordPress.com 제품 WordPress 호스팅 에이전시용 WordPress 제휴사 되기 도메인 네임 AI 웹사이트 제작 도구 웹사이트 제작 도구 블로그 생성 Professional Email 웹사이트 디자인 서비스 워드프레스 스튜디오 엔터프라이즈 워드프레스 기능 전체 보기 WordPress 테마 WordPress 플러그인 워드프레스 패턴 Google Apps 리소스 워드프레스닷컴 블로그 비즈니스 이름 생성 도구 로고 메이커 WordPress.com 리더 접근성 구독 삭제 도움말 지원 센터 가이드 과정 포럼 연락처 개발자 리소스 회사 정보 프레스 이용 약관 개인 정보 보호 정책 제 개인 정보를 판매하거나 공유하지 마세요 캘리포니아 사용자를 위한 개인 정보 보호 고지 Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English 모바일 앱 다운로드하기 App Store 시작하기 Google Play 소셜 미디어 Facebook의 워드프레스닷컴 워드프레스닷컴 X(Twitter) Instagram의 워드프레스닷컴 YouTube의 워드프레스닷컴 Automattic Automattic WordPress 채용 | 2026-01-13T09:29:30 |
https://id.atlassian.com/login?application=community--entry-auth&continue=https://community.atlassian.com/forums/s/plugins/common/feature/oauth2sso_v2/sso_login_redirect?referer=%2Fforums%2FJira-Align%2Fct-p%2Fjira-align&prompt=none | Log in with Atlassian account Atlassian JavaScript is disabled You should enable JavaScript to work with this page. Atlassian JavaScript load error We tried to load scripts but something went wrong. Please make sure that your network settings allow you to download scripts from the following domain: https://id-frontend.prod-east.frontend.public.atl-paas.net | 2026-01-13T09:29:30 |
https://id.atlassian.com/signup?application=community--entry-auth&continue=https://community.atlassian.com/forums/s/plugins/common/feature/oauth2sso_v2/sso_login_redirect?referer=%2Fforums%2FJira-Align%2Fct-p%2Fjira-align&prompt=none | Log in with Atlassian account Atlassian JavaScript is disabled You should enable JavaScript to work with this page. Atlassian JavaScript load error We tried to load scripts but something went wrong. Please make sure that your network settings allow you to download scripts from the following domain: https://id-frontend.prod-east.frontend.public.atl-paas.net | 2026-01-13T09:29:30 |
https://zh-cn.libreoffice.org/ | --> 主页 | LibreOffice 简体中文官方网站 - 自由免费的办公套件 --> You are using an outdated browser. Please upgrade your browser or activate Google Chrome Frame to improve your experience. English | 中文 (简体) | Deutsch | Español | Français | Italiano | More... 探索 LibreOffice 简介 新功能 模板与扩展 截图 下载 下载 LibreOffice 国内下载镜像 开发测试版 中日韩字体 便携版 Flatpak 格式的 LibreOffice Snap 格式的 LibreOffice 适用于移动设备的 LibreOffice LibreOffice Impress Remote LibreOffice Online 发行注记 源代码 帮助与支持 用户文档 社区支持 在线帮助系统 反馈及缺陷报告 专业支持 安装指南 系统需求 邮件列表 参与进来 加入我们 设计 开发者 文档编写 基础设施 本地化翻译 国际站点 Wiki 博客 ♥ 捐助 --> --> --> --> --> --> 自由免费的全能办公套件 对个人和企业均免费，不用支付授权费用。 开始探索 LibreOffice 国际化的开源项目 LibreOffice 是国际化的开源项目， 由来自全球的社区成员参与开发。 获得帮助 您也可以成为团队的一员！ LibreOffice 由社区创造，任何人都可以参与，不论您是否懂编程。在免费使用软件的同时，欢迎您贡献自己的才能和想法。 加入我们！ 更简洁，更快，更智能 LibreOffice 是一款 功能强大的办公软件 ，默认使用开放文档格式 (OpenDocument Format , ODF), 并支持 *.docx, *.xlsx, *.pptx 等其他格式。 它 包含了 Writer, Calc, Impress, Draw, Base 以及 Math 等组件，可用于处理文本文档、电子表格、演示文稿、绘图以及公式编辑。 它 可以运行于 Windows, GNU/Linux 以及 macOS 等操作系统上，并具有一致的用户体验。 自由免费的全能办公套件 对个人和企业均免费，不用支付授权费用。 开始探索 LibreOffice 国际化的开源项目 LibreOffice 是国际化的开源项目， 由来自全球的社区成员参与开发。 获得帮助 您也可以成为团队的一员！ LibreOffice 由社区创造，任何人都可以参与，不论您是否懂编程。在免费使用软件的同时，欢迎您贡献自己的才能和想法。 加入我们！ LibreOffice 的开发过程完全开放透明，开发、测试和市场推广的各个领域都需要您的参与。 加入我们 Posts from LibreOffice official blog 最新动态 来自： LibreOffice 中文社区博客 LibreOffice Podcast, Episode #6 – Language support 2026-01-12 LibreOffice is available in over 120 languages – but we want to do more! Jonathan Clark recently joined the TDF team to improve LibreOffice’s support for RTL (right-to-left) and CTL (complex text layout) scripts. In this episode, he talks to Mike Saunders about his work, and how users can help 了解更多 » The Future of Open Standards and the Importance of ODF 2026-01-09 Open standards don’t make headlines. Instead, they work quietly behind the scenes to define how information is created, shared and stored. However, as digital ecosystems become more complex and centralised, open standards are becoming increasingly important. One of the best examples is the Open Document Format (ODF), the native format 了解更多 » LibreOffice 团队招募全职带薪 C++ 程序员，致力于 RTL/CTL/中日韩语言的开发 2023-12-08 文档基金会正在招募一名全职 C++ 程序员，从事 LibreOffice 中从右到左RTL、复杂文字布局 RTL、中日韩 CJK 语言相关代码的开发。职位申请截止日期为2024 年 1 月 8 日。 了解更多 » 如何使用LibreOffice API + Python通过暴力破解的方式找到忘记的Office文件密码 2023-12-05 忘记了ods电子表格文档的密码，怎么办？如果你大概知道自己当时设置的密码的规律（比如，密码的长度，密码中包含哪些字符，是纯数字还是&[…] 了解更多 » 关注我们 Our blog Mastodon (LibreOffice) Mastodon (TDF) Twitter Impressum (法律信息) | Datenschutzerklärung (隐私政策) | Statutes (non-binding English translation) - Satzung (binding German version) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License . This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License v2.0 . “LibreOffice” and “The Document Foundation” are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy . LibreOffice was based on OpenOffice.org. | 2026-01-13T09:29:30 |
https://meeksfamily.uk/~michael/blog/2023/Jan/index.html | Stuff Michael Meeks is doing Stuff Michael Meeks is doing This is my (in)activity log. You might like to visit Collabora Productivity a subsidiary of Collabora focusing on LibreOffice support and services for whom I work. Also if you have the time to read this sort of stuff you could enlighten yourself by going to Unraveling Wittgenstein's net or if you are feeling objectionable perhaps here . Failing that, there are all manner of interesting things to read on the LibreOffice Planet news feed . Older items: 2023 : ( J F M A M J ), 2022 : ( J F M A M J J A S O N D ), 2021 , 2019 , 2018 , 2017 , 2016 , 2015 , 2014 , 2013 , 2012 , 2011 , 2010 , 2009 , 2009 , 2008 , 2007 , 2006 , 2005 , 2004 , 2003 , 2002 , 2001 , 2000 , 1999 , legacy html Tue, 31 Jan 2023 --> 2023-01-31 Tuesday Chat with Kendy, Pedro, Andras, interviews. Sync with Naomi on marketing candidates - lots of hiring and interviewing going on. Mon, 30 Jan 2023 --> 2023-01-30 Monday Planning call much of the morning; booked CS3 travel , various partner calls in the afternoon. Lovely to catch up with Sean Atkinson in the evening. Sun, 29 Jan 2023 --> 2023-01-29 Sunday All Saints in the morning, back for lunch with David, played games with J, H. & D. who kindly took babes to StAG. Relaxed. Sat, 28 Jan 2023 --> 2023-01-28 Saturday Set too with H. clearing and cleaning out the office; managed to get H's new desk cut down together on the band-saw and after binning a whole filing cabinet - eventually fitted into the corner: nice. Anne over for a birthday celebration with Bruce; lovely to see them, pie & cake for lunch. Spent some time with them; back to dunging out the office. Fri, 27 Jan 2023 --> 2023-01-27 Friday Poked at slides, chatted to Dee & Becky who came over, multi-partner conference call for several hours. Spent time cleaning out the office, shredding ancient papers etc. Thu, 26 Jan 2023 --> 2023-01-26 Thursday Catch up with Miklos, COOL community call, catch up with the OpenProject team, partner call, admin. Persevered with my Duolingo German-learning habit. Wed, 25 Jan 2023 --> 2023-01-25 Wednesday Positive weekly sales call, monthly Productivity all-hands call, catch up with Patrick, Thorsten. All Saints band practice. Tue, 24 Jan 2023 --> 2023-01-24 Tuesday Admin, mail, planning, status report, 1:1's, played with Miro a little. CP monthly management meeting. Mon, 23 Jan 2023 --> 2023-01-23 Monday Planning call; marketing call, reviewed 2023 projections with Tracie & Julie. Catch up with Philippe. AllSaints PCC meeting in the evening. Sun, 22 Jan 2023 --> 2023-01-22 Sunday All Saints, played in the morning with Peter, relaxed in the afternoon. Sat, 21 Jan 2023 --> 2023-01-21 Saturday Up lateish, dismantled washing machine, replaced the inlet hose, J. cleaned the soap dispenser, replaced the front seal & spring. Amazingly - no leaks anymore. Dug through personal tax filing, eventually with some results - filed for J. and myself late in the evening. Fri, 20 Jan 2023 --> 2023-01-20 Friday Up early, out for a run in the frost with J. Home, mail chew, admin, H. passed her driving test 1st time, happily. Catch up with Naomi & Eloy, sync call with Andras. Worked through Univention conference action items. Thu, 19 Jan 2023 --> 2023-01-19 Thursday Up early - driving babes to school due to missed train. Sync with Miklos, COOL community call, mail chew, lunch, catch-up with Andras before all afternoon C'bra Quarterly Mgmt meeting until late. Wed, 18 Jan 2023 --> 2023-01-18 Wednesday Up early; off to the workshop venue, Marc spoke on Collabora Online, lots of discussion, pleasant coffee with Andreas, tram not working, taxi to the airport, not checked-in in advance for Ryanair - what a silly system - paid the fine. Home - lovely to be back with the babes & Mary. Caught up with the news & progress. Tue, 17 Jan 2023 --> 2023-01-17 Tuesday Early breakfast with Naomi, Marc & Eloy - off to the venue, met some friends - improved my German variously by listening to some interesting talks. Talked to lots of partners & customers, enjoyed food, some music, catch up with Thorsten & Lothar, bed rather late. Mon, 16 Jan 2023 --> 2023-01-16 Monday Up early, packed, mail chew, planning call. Catch up with Mazin. Slide & data review. H. had a driving lesson, Nicki over for tea, drove to Stansted, flight to Bremen. Caught up with Eloy in-person before bed. Sun, 15 Jan 2023 --> 2023-01-15 Sunday All Saints in the morning, church vision & cornerstone retrospective meeting afterwards. Home for a fine roast, helped N. to assemble her new computer - while watching Space Balls during the length delays during installation. Watched Johnny English reborn with Mary, tea, played Rummikub with H,J & Mary. Finised up PC in the evening with N. Sat, 14 Jan 2023 --> 2023-01-14 Saturday Up earlyish, helped seal windows in guest-room for Mary R. - coming to stay with us today for a week. Removed washing machine seal: interesting 0.9mm wire necked to far smaller where it rusted 'orrible - who would use galvanized wire instead of stainless corrosive environment? Hotpoint apparently. Found the rusted screw (see previous thought), and located leak finally around rubber filling manifold. Ordered parts & re-assembled. Mary over to stay at lunch-time. Re-plumbed washing machine feed from main to avoid pump noise at night (economy-7 electricity) - pipe bending with E, soldering with H. looks good. Planning bits with H. Got ahead with admin. Fri, 13 Jan 2023 --> 2023-01-13 Friday Worked on slides for a somewhat unexpected partner call with Andras, Tor & Pedro; had the call. Caught up with Eloy. Into Cambridge to see Avatar-WoW - fantastic visual effects, somewhat unwise plot emphasis on family & planet as idol, but good fun. Back for a take-away - a treat for N's 18th. Thu, 12 Jan 2023 --> 2023-01-12 Thursday Chat with Miklos, COOL community call, interviews & offers variously - for some of our open positions . Wed, 11 Jan 2023 --> 2023-01-11 Wednesday Encouraging sales call with Eloy & Mazim, 1:1 with Kendy, partner call in the afternoon, admin. All Saints music group practice in the evening. Tue, 10 Jan 2023 --> 2023-01-10 Tuesday Calls with Pedro, Naomi, Mike K, chat with a UK based startup, sync with Philippe, back-to-back calls & admin all day. Mon, 09 Jan 2023 --> 2023-01-09 Monday Sync with Anna, ISO audit call, planning call for much of the morning, dug through E-mail, admin bits. Ordered lots of bits with Robert's help for N's new PC - a Zen 4 beastie. Sun, 08 Jan 2023 --> 2023-01-08 Sunday All Saints in the morning with Cedric on Piano. Mission meeting afterwards, home for a fine lunch, Tashi & Emily arrived - lovely to see them, picked up babes variously from StAG in the evening. Sat, 07 Jan 2023 --> 2023-01-07 Saturday J. out to All Saints - warm spaces, chewed mail, caught up on personal admin: ONS study response, personal admin etc. David over for lunch. Poked at a plumbing issue with David, before re-wiring J's counselling room, with power-over-ethernet hub, wifi extender, and other such gubbins - rather successfully. Pizza dinner, bid 'bye to David, slugged. Fri, 06 Jan 2023 --> 2023-01-06 Friday Up lateish, mail-chew, admin, interviewing bits. Amused to see that an old class-mate Tim Vincent-Smith has built a/the Pianodrome and is rescuing and re-using old pianos. Pushed a large amount of project planning out of the door somehow. Thu, 05 Jan 2023 --> 2023-01-05 Thursday Took babes to park & ride in Cambridge: train strikes. 1:1 with Miklos, COOL community call, admin. Partner catch-up, chat with Andras, more project planning. Cell group - with Mary, Leo & Alex. Wed, 04 Jan 2023 --> 2023-01-04 Wednesday Back to work, mail chew - encouraged by a lovely speedup from Noel for our projection spreadsheet: seconds to tens of milliseconds to edit; nice. Sales calls, sync with Gokay & Andras, worked on project description pieces. J. took down decorations. Call with Ben & Kendy on our hiring pipeline - if you'd like a job around Collabora Online & LibreOffice technology you can checkout Collabora careers . Bit of hacking until late, improving profiling & tracing. Tue, 03 Jan 2023 --> 2023-01-03 Tuesday Some mail chew, sync with Andras, helped to seal some annoying wooden windows, tidied the house somewhat. Helped H. machine some aluminium to repair her dead Beats headphones. Up rather late working on some maths with Miriam. A more successful day off. Mon, 02 Jan 2023 --> 2023-01-02 Monday A day off - planning calls during the morning; sync. with Andras. Out for a run with J - partner call & special pricing call, some of the afternoon off. Sun, 01 Jan 2023 --> 2023-01-01 Sunday All Saints - music with H. home, sogging action, more Jack Ryan. My content in this blog and associated images / data under images/ and data/ directories are (usually) created by me and (unless obviously labelled otherwise) are licensed under the public domain, and/or if that doesn't float your boat a CC0 license. I encourage linking back (of course) to help people decide for themselves, in context, in the battle for ideas, and I love fixes / improvements / corrections by private mail. In case it's not painfully obvious: the reflections reflected here are my own; mine, all mine ! and don't reflect the views of Collabora, SUSE, Novell, The Document Foundation, Spaghetti Hurlers (International), or anyone else. It's also important to realise that I'm not in on the Swedish Conspiracy . Occasionally people ask for formal photos for conferences or fun . Michael Meeks ( michael.meeks@collabora.com ) | 2026-01-13T09:29:30 |
https://meeksfamily.uk/~michael/blog/2023/May/index.html | Stuff Michael Meeks is doing Stuff Michael Meeks is doing This is my (in)activity log. You might like to visit Collabora Productivity a subsidiary of Collabora focusing on LibreOffice support and services for whom I work. Also if you have the time to read this sort of stuff you could enlighten yourself by going to Unraveling Wittgenstein's net or if you are feeling objectionable perhaps here . Failing that, there are all manner of interesting things to read on the LibreOffice Planet news feed . Older items: 2023 : ( J F M A M J ), 2022 : ( J F M A M J J A S O N D ), 2021 , 2019 , 2018 , 2017 , 2016 , 2015 , 2014 , 2013 , 2012 , 2011 , 2010 , 2009 , 2009 , 2008 , 2007 , 2006 , 2005 , 2004 , 2003 , 2002 , 2001 , 2000 , 1999 , legacy html Wed, 31 May 2023 --> 2023-05-31 Wednesday Up early, rushed to the nearest traffic-jam for a two hour stay on the A14; eventually got to the Suffolk Show. Saw lots of nice (heavy) horses with the pretty wife - enjoyed some sandwiches. Interrogated various vendors of insanely heavy farm equipment and admired their wares; solar powered robot planting and weeding machines - nice. Pre-fabricated concrete slab salespeople, giant tractors & lifters. Also a lot of animals & a flower show. Home late with some cold babies; Music group practice, dinner. Tue, 30 May 2023 --> 2023-05-30 Tuesday Mail chew, encouraged to see that Cor's initiative to break the deadlock and finally get an actionable vote passed to hire a couple of devs for TDF paid off with Khaled hired; great. We're also looking for a fluent German Project Manager to help out with some of our German customers and partners. Planning call for a couple of hours; lunch. Eloy 1:1, catch up with E-mail backlog. Did some work with M. to get her chess-board cut in the other dimension, and re-glued-up looking good. Mon, 29 May 2023 --> 2023-05-29 Monday Up earlyish, signed a contract, then day off. Out to see the Hawkins' in St Albans, enjoyed a day in the sun, chatting, ice-creams, slept & relaxed. Home; Le-anne had arrived to stay, nice to see her. Sun, 28 May 2023 --> 2023-05-28 Sunday All Saints in the morning, started to use ising which seems rather good. Chatted to B&C, noodle soup for lunch. Bid 'bye to B&C - picked H. up from Cambridge. Sat, 27 May 2023 --> 2023-05-27 Saturday Up earlyish, out to All Saints to run Open Church with B&C - no visitors. Home for lunch. Out for a walk from Reach to home along the dyke; cup of tea, collected the car and chatted. Fri, 26 May 2023 --> 2023-05-26 Friday Mail chew; misc. admin. Two hour process call, vendor meeting. Back to mail, slides & admin. Barbara & Colin arrived - lovely to see them after so long, sat outside in the sunshine. Thu, 25 May 2023 --> 2023-05-25 Thursday Up earlyish, tech. planning call; N. not well. COOL community call; continued to find interesting performance things to fix there. Lunch, interview, marketing strategy call; admin. Catch-up with Tracie. Bible study group, sleep. Wed, 24 May 2023 --> 2023-05-24 Wednesday Sync. with Marco, weekly sales call, chat with Sarper, lunch, sync with Caolan & Stephan, partner sales call. Into Cambridge to the Beer Festival, met up with the Collabora team, catch-up with Andrew Haley, some good tips from Simon McV, lovely. Train back with H. late. Tue, 23 May 2023 --> 2023-05-23 Tuesday Mail, 1:1s with Andras & Pedro, partner call, 1:1 with Eloy, admin, sales call; got to profiling some dialog bits and merged various improvements. Strimmed the lawn with J, helped M. with her physics revision in the evening. Mon, 22 May 2023 --> 2023-05-22 Monday Mail chew; planning call. Bruce & Anne & Louise over for lunch - luckily lots of left-overs from the lady's day Saturday. Long architecture call. Managed to get ESTAs filed eventually too. Sun, 21 May 2023 --> 2023-05-21 Sunday Cooked breakfast, gave a short talk on Psalm 1 : how's your walk ? Out for physical walking, and bid 'bye to the lads - drove Simon home listening to Sons of Korah . Lovely to see the babes again; slept exhaustedly on the sofa; picked them up from Cambridge; bed late. Sat, 20 May 2023 --> 2023-05-20 Saturday Out for a cooked breakfast nearby, then walked some miles into Walberswick, lunch at the Bell Inn, walked back by a different route together; good to have time to catch up. Dinner at the Fox Inn together; bid 'bye to Alex. Fri, 19 May 2023 --> 2023-05-19 Friday Bits of mail chewage; packed and drove Simon N to Darsham, met up with lots of Men of Faith; chatted & drank ale in the sun; BBQ, and a stew from Mihai until late. Slept in the Darsham station - a combination of train vibration, and the more impressive lorry-on- level-crossing vibration - making the bunk-house snoring experience more amusing. Thu, 18 May 2023 --> 2023-05-18 Thursday Breakfast with the parents; bid 'bye to them. Technical planning call, COOL community call, lunch, 1:1 with Miklos, E-mail & partner call. Booked flight & hotel in Berlin. Spent the evening on Psalm 1 for Sunday; really encouraging to pull it all together & to delightful to get a better understanding of the passage. Wed, 17 May 2023 --> 2023-05-17 Wednesday Partner call, weekly sales call, 23.05 release planning call. Lunch, CP all-hands call. Parents over in the afternoon - lovely to spend some time with them. Tue, 16 May 2023 --> 2023-05-16 Tuesday Partner catch-up; various meetings, tried to clear my desk somewhat, misc. calls. Mon, 15 May 2023 --> 2023-05-15 Monday Mail chew. Planning call, two hour partner call in parallel with a catch-up with the wider marketing team. Another partner call, COOL-days post-mortem and next-time planning. Quick sync with Caolan; helped sort out AC maintenance in the garden. Family dinner, off to minute PCC meeting; back late, admin. Welcoming Caolán McNamara to Collabora For anyone that doesn't know him - Caolán has contributed amazing work on the LibreOffice code-base for over two decades, latterly for RedHat. He has pioneered work in many areas around LibreOffice: helping to found The Document Foundation, and contributing to its growth and governance handling security for LibreOffice, managing CVEs and patch porting maintaining our static checking with Coverity and others getting fuzzing working, tending oss-fuzz, and incorporating a large number of fixes to stop issues escaping in releases. tending our crash-testing of ~750k documents (~60Gb) of bug documents which we continually run through (thanks to hardware sponsorship from Adfinis ) - maintaining the great quality of our filters. We expect Caolán will continue to spend time on these as part of his role at Collabora; but of course this is only a subset of the things he has contributed for RedHat some highlights being: re-working the entire LibreOffice UI to use auto-layout instead of fixed-positions, it is hard to comprehend what a huge investment this represents - with over a thousand glade dialog fragments, with over half a million lines. adapting the UI toolkit to allow native gtk (& Javascript) widgets. maintaining our gtk backends to cope with the latest gtk churn^Wimprovements. various vital features such as printing comments in the margins in writer. getting almost every package in a RedHat distro to use the same Hunspell dictionaries. complex text rendering & layout, fixing innumerable bugs, improving the user-experience and much more. RedHat was instrumental in founding The Document Foundation, and has invested far more than we had any right to expect through its team over a long period; they deserve our thanks. I expect that LibreOffice will still be available from flathub going forward. However with RedHat now choosing to laser focus its development investment into the open hybrid cloud, it became clear that in order for us to continue to enjoy Caolán's contribution - he would need a new home. Happily - this circumstance is rather similar to the history of Collabora Productivity's founding with the direction changes at SUSE, and we could act quickly. The paid and volunteer team around the code-base continues to grow. However, it is is important that we retain skills, and continue to deepen the talent pool around LibreOffice Technology and Collabora Online as circumstances change. The Collabora team is looking forward to working with Caolán to continue his work in three areas: on the underlying LibreOffice Technology , serving our customers as part of our growing ( we're hiring ) team, and of course to make Collabora Online even better for our partners and customers. Welcome Caolán! Sun, 14 May 2023 --> 2023-05-14 Sunday Up earlyish, pre-service practice with Cedric, played - home for Pizza lunch. Caught up the blog; listened to another Psalm 1 talk. Sat, 13 May 2023 --> 2023-05-13 Saturday Slept in, out for a run with J; then shopping. B&A over; took A. into town to sort out B's phone malfuctioning: an under-used PAYG phone: phoning 150 and re-enabling the SIM: the solution, sadly the UI has no hint for why its malfunctioning however. Lunch, toured new bits in the home; David over; bid 'bye to the inlaws; set too at sorting out J's garden lean-too; and getting more out of the garage. Fri, 12 May 2023 --> 2023-05-12 Friday Up late; chat with Cor, Thorsten - packed, met up with Thorsten and had a pleasant train ride together. Epic queueing nightmare for security, another RyanAir flight delayed by an hour; eventually got home to Stansted and a train strike. J. picked me up and had a very disrupted kid/taxi-service. Flushed E-mail, chased documents, dinner with the family, worked late. Thu, 11 May 2023 --> 2023-05-11 Thursday Breakfast with Frank & Bjoern; off to a rather encouraging partner meeting - lots of items ironed out. Out for dinner in the evening, and up late at a bar with Gotz, Niels & Mark. Wed, 10 May 2023 --> 2023-05-10 Wednesday Up lateish; enjoyed the warm weather, and remarkable set of people we have, toured various activities; caught up with individuals; lunch with Kendy. Bid a premature 'bye to many. Taxi, flight to Hamburg - worked on slides on the plane. Tue, 09 May 2023 --> 2023-05-09 Tuesday Talk from Philippe & Guy, rap from Rachel, mostly in-person mgmt meeting with the team; good to see them and discuss where we're going in more depth. Fine lunch; enjoyed booths run by other Collaborans, caught up with some mail; more meetings in the evening; dinner together. Individual chats until late. Mon, 08 May 2023 --> 2023-05-08 Monday Early taxi with Nick & Carolyn to Stansted; met up with a growing group of Collaborans, worked on the flight, prepping slides for the mgmt meeting. Arrived in Faro, bus with an even bigger group to the venue, enjoyed fine company, sea, food & drink - after not seeing many people in person for so long; really good to catch up again. Up late. Sun, 07 May 2023 --> 2023-05-07 Sunday All Saints in the morning; family service, making crowns for some reason. Church BBQ outside afterwards. Took all but H. into Cambridge, bed early. Sat, 06 May 2023 --> 2023-05-06 Saturday Up late, got a bit of work in; watched the conoration - pleased to see things done properly in an orderly fashion; and for the King to have impressed on them their role of service to the real King, and the nation. Surprisingly good, albeit lengthy. Sorted out J's garden lean-to somewhat, and strimmed the pernicious grass. Fri, 05 May 2023 --> 2023-05-05 Friday Customer call, team deadline chasing call, catch up with Andras, lunch; out to Josh Bendall's funeral to play violin with Mick on keyboard - a good funeral. A chunk of contract reviews; N. cooked a fine dinner, back to work until late. Thu, 04 May 2023 --> 2023-05-04 Thursday Technical planning call, COOL community call, customer deadline chasing team call, weekly sales call. Customer support call with Aron. Bits of hacking & admin. Bible study group in the evening. Reading up on Psalm 1 for the Church mens walking weekend. Wed, 03 May 2023 --> 2023-05-03 Wednesday Mail chew, early partner call, chat with Thorsten. Encouraging COOL-days marketing post-mortem, interview; All Saints band practice with Beckie & Mary. Tue, 02 May 2023 --> 2023-05-02 Tuesday Mail chew, morning planning call, lunch, picked up bits and pieces from Screwfix. Team call, catch up call with Patrick, sync with Gokay on cypress. Varnished new stairs in the evening. Mon, 01 May 2023 --> 2023-05-01 Monday Up, off to see J's parents - worked in the car a little. Lunch with B&A, fixed a number of things around the house for them - blocked drains again interestingly; tough to solve. Poked at various things in the garage; replaced light-bulbs. Chatted, and did a puzzle while babes playing scrabble. Chips on the way home, worked through mail. My content in this blog and associated images / data under images/ and data/ directories are (usually) created by me and (unless obviously labelled otherwise) are licensed under the public domain, and/or if that doesn't float your boat a CC0 license. I encourage linking back (of course) to help people decide for themselves, in context, in the battle for ideas, and I love fixes / improvements / corrections by private mail. In case it's not painfully obvious: the reflections reflected here are my own; mine, all mine ! and don't reflect the views of Collabora, SUSE, Novell, The Document Foundation, Spaghetti Hurlers (International), or anyone else. It's also important to realise that I'm not in on the Swedish Conspiracy . Occasionally people ask for formal photos for conferences or fun . Michael Meeks ( michael.meeks@collabora.com ) | 2026-01-13T09:29:30 |
https://www.sparkcapital.com/team-members/alex-finkelstein | Alex Finkelstein ABOUT Team Companies Alex Finkelstein Co-founder & General Partner, Early Alex began his career at Cambridge Associates before joining two Softbank venture capital funds. Alex then left the venture capital world to scratch his creative itch where he wrote and sold a number of original television shows to networks including Fox, Discovery, and E!. He then returned to venture as a co-founder of Spark Capital. Alex has focused on uncovering unconventional companies led by entrepreneurs who aren’t afraid to challenge the status quo. He often looks outside Silicon Valley for undiscovered, product-focused founders with a drive to reinvent , rather than copy. Alex has made investments in startups around the world including in Nigeria, Germany , and Spain, as well as in companies just two minutes from his home in Boston. He was the first investor and Board member at Flywire (Nasdaq:FLYW), Talkspace (Nasdaq:TALK), Wayfair (NYSE:W), 5min (acquired by AOL) and SoundHouse (acquired by Apollo). “I love the scrappy, underdog founders, who’ve often never done it before,” he says. Alex is a graduate of Middlebury College. alexfinkelstein @finkelstein1 Companies Adept We’re building a machine-learning model that can interact with everything on your computer. Read the Story Visit the Website Adept Capella Space Capella Space is a space company that operates a fleet of the first and only U.S. commercial SAR satellites. Co-led Series A in 2018 Read the Story Visit the Website Capella Space Cruise Cruise is building the world’s most advanced self-driving vehicles to safely connect people with the places, things, and experiences they care about. Led Series A in 2015 Acquired by General Motors in 2016 Read the Story Visit the Website Cruise Discord Discord is the easiest way to communicate over voice, video, and text with your friends and communities. Led Series C in 2016 Read the Story Visit the Website Discord Harmonix Harmonix is one of the world’s leading independent game development studios, best known for creating blockbuster franchises like Rock Band and Dance Central. Co-led Series A in 2015 Acquired by Epic Games in 2021 Read the Story Visit the Website Harmonix Instawork Instawork helps local businesses quickly fill permanent and temporary openings with the most qualified professionals in their communities. Led Series B in 2019 Read the Story Visit the Website Instawork Postmates Postmates pioneered the on-demand delivery movement in the U.S. by offering delivery from restaurants and stores previously only available offline. Led Series B in 2014 Acquired by Uber in 2020 Read the Story Visit the Website Postmates Proletariat Proletariat is a group of community-first game developers and the creators of the hit game, Spellbreak. Led Seed in 04/12/2013 Acquired by Activision/Blizzard in 2023 Read the Story Visit the Website Proletariat Zum Zūm provides safe, efficient, and reliable child transportation for school districts and busy families. Led Series B in 2018 Read the Story Visit the Website Zum © Spark Capital 2024 Contact Us Terms & Policies In 2011, Alex led the Series A of Wayfair, the company that pioneered selling furniture online. Shortly thereafter, founders Niraj Shah and Steve Conine took the company public. Today, with the duo still at the helm, Wayfair is the largest online destination for home goods in the world. Alex gave Berlin-based founder Johannes Reck his first check back in 2014. Reck started GetYourGuide after a travel mix-up that sparked a revolutionary approach to tourism. Brooke’s students, many of whom come from low-income and minority families, annually achieve the highest MCAS scores for any public school in Massachusetts. | 2026-01-13T09:29:30 |
https://meeksfamily.uk/~michael/blog/2022/Feb/index.html | Stuff Michael Meeks is doing Stuff Michael Meeks is doing This is my (in)activity log. You might like to visit Collabora Productivity a subsidiary of Collabora focusing on LibreOffice support and services for whom I work. Also if you have the time to read this sort of stuff you could enlighten yourself by going to Unraveling Wittgenstein's net or if you are feeling objectionable perhaps here . Failing that, there are all manner of interesting things to read on the LibreOffice Planet news feed . Older items: 2023 : ( J F M A M J ), 2022 : ( J F M A M J J A S O N D ), 2021 , 2019 , 2018 , 2017 , 2016 , 2015 , 2014 , 2013 , 2012 , 2011 , 2010 , 2009 , 2009 , 2008 , 2007 , 2006 , 2005 , 2004 , 2003 , 2002 , 2001 , 2000 , 1999 , legacy html Mon, 28 Feb 2022 --> 2022-02-28 Monday Planning calls. Sun, 27 Feb 2022 --> 2022-02-27 Sunday All Saints, lunch, went to collect M. and N. together - lovely building, apparently somewhat cold. Sat, 26 Feb 2022 --> 2022-02-26 Saturday Just E. at home - up early and took her to Go-Ape in Thetford to swing through the trees together: fair-do's - just as with the others; but somehow a decade after my first trip with M. I have more aches. Nice meal afterwards, enoyed spending time together. Fri, 25 Feb 2022 --> 2022-02-25 Friday Sync call with Thorsten/Lothar, last gasp of board bits. Interesting potential partner call. Took M. and N. to a StAG youth camp in a rather impressive Catholic castle-like building. Thu, 24 Feb 2022 --> 2022-02-24 Thursday COOL community call, mail chew, bits of hacking. Wed, 23 Feb 2022 --> 2022-02-23 Wednesday Slideware, encouraging Partner Council call. Tue, 22 Feb 2022 --> 2022-02-22 Tuesday Unusual but friendly call with a competitor. Positive virtual meet-up with some NHS types. Mon, 21 Feb 2022 --> 2022-02-21 Monday Planning calls. Sun, 20 Feb 2022 --> 2022-02-20 Sunday All Saints - relaxed. Sat, 19 Feb 2022 --> 2022-02-19 Saturday Painted RSJs in the garage again - got a cold. Fri, 18 Feb 2022 --> 2022-02-18 Friday Caught up with Eloy, mail, slide-ware. Wrote a unit test for root-cause fix - boost's default encoding for unknown languages is unhelpful. Thu, 17 Feb 2022 --> 2022-02-17 Thursday Mail chew; got a debug build of core to chase a nasty to it root. 1:1's with people. Wed, 16 Feb 2022 --> 2022-02-16 Wednesday Monthly all-hands. Customer crit-sit chasing again. Tue, 15 Feb 2022 --> 2022-02-15 Tuesday New fridge arrived; unwound various cunning schemes for keeping things cool - plumbed it in, wired it up. Sync with Kendy; B&A over for lunch, ate up lots of older, partially thawed food. Monthly mgmt call; worked late. Mon, 14 Feb 2022 --> 2022-02-14 Monday Planning calls as normal. Sun, 13 Feb 2022 --> 2022-02-13 Sunday Relaxed; a day of rest. Sat, 12 Feb 2022 --> 2022-02-12 Saturday J. out at her course, N & M at GenR8 - played with E. Fridge compressor now starting at least, but cuts out after a short while of cooling, and sounds unusual. Gave in and ordered new fridge/freezer - hopefully for another 15 years. Put up mirror for J, tidied up etc. Hammerited steels in the Garage - aleady rusting despite de-humidification: hmm, primed timber-window frame Fri, 11 Feb 2022 --> 2022-02-11 Friday Call with H. debugged some unexpected oddness in her Arduineo coding together. Fridge failed ~15 years old - (Samsung) compressor still working - soldered in a spare new relay in 5 minutes: should be user service-able and socketed like motor brushes really. Last TDF board meeting: deeply ambivalent about the state of TDF governance as I leave; thank goodness for the many capable new board members elected. Worked on projections. Thu, 10 Feb 2022 --> 2022-02-10 Thursday Meetings, COOL community call. Wed, 09 Feb 2022 --> 2022-02-09 Wednesday Sales call, catch up with Gokay; band practice. Tue, 08 Feb 2022 --> 2022-02-08 Tuesday Caught up with Lubos & Noel. Mon, 07 Feb 2022 --> 2022-02-07 Monday Weekly planning call. Sun, 06 Feb 2022 --> 2022-02-06 Sunday All Saints; home - gave a FOSDEM talk on the great work the team have been doing around Collabora Online Performance Sat, 05 Feb 2022 --> 2022-02-05 Saturday More data, continued on customer crit-sit until late; discovered lots of brokenness in their own infra. Fri, 04 Feb 2022 --> 2022-02-04 Friday Catch up with Eloy; helped Hannah with some curious matlab programming language: who knew that the input() type function would do variable substitution by default: most un-expected; lovely to chat with her. Thu, 03 Feb 2022 --> 2022-02-03 Thursday Customer crit-sit, up all night testing & trying to diagnose the root cause. Wed, 02 Feb 2022 --> 2022-02-02 Wedneday Caught up with Dave Neary, now at Ampere - its been too long without an in-person FOSDEM or the like. Tue, 01 Feb 2022 --> 2022-02-01 Tuesday Work; always feel a bit bad buying a valentines day card multi-pack. Took J out in the evening - such a delightful wife. My content in this blog and associated images / data under images/ and data/ directories are (usually) created by me and (unless obviously labelled otherwise) are licensed under the public domain, and/or if that doesn't float your boat a CC0 license. I encourage linking back (of course) to help people decide for themselves, in context, in the battle for ideas, and I love fixes / improvements / corrections by private mail. In case it's not painfully obvious: the reflections reflected here are my own; mine, all mine ! and don't reflect the views of Collabora, SUSE, Novell, The Document Foundation, Spaghetti Hurlers (International), or anyone else. It's also important to realise that I'm not in on the Swedish Conspiracy . Occasionally people ask for formal photos for conferences or fun . Michael Meeks ( michael.meeks@collabora.com ) | 2026-01-13T09:29:30 |
http://creativecommons.org/licenses/by-sa/2.0/deed.en | Deed - Attribution-ShareAlike 2.0 Generic - Creative Commons Skip to content Creative Commons Menu Who We Are What We Do Licenses and Tools Blog Support Us Languages available aragonés Azərbaycanca Bahasa Indonesia Basque català dansk Deutsch eesti English español Esperanto français frysk Gaeilge galego Hrvatski italiano latviešu Lietuviškai Magyar Melayu Nederlands norsk polski Português Português Brasileiro Română Slovensky Slovenščina srpski (latinica) suomi svenska Türkçe Íslenska česky Ελληνικά беларуская български Русский Українська العربيّة فارسی हिंदी বাংলা 日本語 简体中文 繁體中文 한국어 Search Donate Explore CC Global Network Join a global community working to strengthen the Commons Certificate Become an expert in creating and engaging with openly licensed materials Global Summit Attend our annual event, promoting the power of open licensing Chooser Get help choosing the appropriate license for your work Search Portal Find engines to search openly licensed material for creative and educational reuse Open Source Help us build products that maximize creativity and innovation Help us protect the commons. Make a tax deductible gift to fund our work. Donate today! Attribution-ShareAlike 2.0 Generic CC BY-SA 2.0 Deed Notice This is an older version of this license. Compared to previous versions, the 4.0 versions of all CC licenses are more user-friendly and more internationally robust . If you are licensing your own work , we strongly recommend the use of the 4.0 license instead: Deed - Attribution-ShareAlike 4.0 International Canonical URL https://creativecommons.org/licenses/by-sa/2.0/ See the legal code You are free to: Share — copy and redistribute the material in any medium or format for any purpose, even commercially. Adapt — remix, transform, and build upon the material for any purpose, even commercially. The licensor cannot revoke these freedoms as long as you follow the license terms. Under the following terms: Attribution — You must give appropriate credit , provide a link to the license, and indicate if changes were made . You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits. Notices: You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation . No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material. Creative Commons is the nonprofit behind the open licenses and other legal tools that allow creators to share their work. Our legal tools are free to use. Learn more about our work Learn more about CC Licensing Support our work Use the license for your own material. Licenses List Public Domain List Footnotes return to reference appropriate credit — If supplied, you must provide the name of the creator and attribution parties, a copyright notice, a license notice, a disclaimer notice, and a link to the material. CC licenses prior to Version 4.0 also require you to provide the title of the material if supplied, and may have other slight differences. More info return to reference indicate if changes were made — In 4.0, you must indicate if you modified the material and retain an indication of previous modifications. In 3.0 and earlier license versions, the indication of changes is only required if you create a derivative. Marking guide More info return to reference same license — You may also use a license listed as compatible at https://creativecommons.org/compatiblelicenses More info return to reference technological measures — The license prohibits application of effective technological measures, defined with reference to Article 11 of the WIPO Copyright Treaty. More info return to reference exception or limitation — The rights of users under exceptions and limitations, such as fair use and fair dealing, are not affected by the CC licenses. More info return to reference publicity, privacy, or moral rights — You may need to get additional permissions before using the material as you intend. More info Creative Commons Contact Newsletter Privacy Policies Terms Contact Us Creative Commons PO Box 1866, Mountain View, CA 94042 info@creativecommons.org +1-415-429-6753 Instagram --> Bluesky Mastodon LinkedIn Subscribe to our Newsletter Support Our Work Our work relies on you! Help us keep the Internet free and open. Donate Now Except where otherwise noted , content on this site is licensed under a Creative Commons Attribution 4.0 International license . Icons by Font Awesome . | 2026-01-13T09:29:30 |
https://meeksfamily.uk/~michael/blog/2023/Feb/index.html | Stuff Michael Meeks is doing Stuff Michael Meeks is doing This is my (in)activity log. You might like to visit Collabora Productivity a subsidiary of Collabora focusing on LibreOffice support and services for whom I work. Also if you have the time to read this sort of stuff you could enlighten yourself by going to Unraveling Wittgenstein's net or if you are feeling objectionable perhaps here . Failing that, there are all manner of interesting things to read on the LibreOffice Planet news feed . Older items: 2023 : ( J F M A M J ), 2022 : ( J F M A M J J A S O N D ), 2021 , 2019 , 2018 , 2017 , 2016 , 2015 , 2014 , 2013 , 2012 , 2011 , 2010 , 2009 , 2009 , 2008 , 2007 , 2006 , 2005 , 2004 , 2003 , 2002 , 2001 , 2000 , 1999 , legacy html Tue, 28 Feb 2023 --> 2023-02-28 Tuesday Mail chew; answered a few questions at a partner webinar by Eloy, lunch, partner call, catch up with Pedro, mail. Mon, 27 Feb 2023 --> 2023-02-27 Monday Mail chew, planning call, lunch, catch up with Paris. Sync with Guy & Eloy, chased a nasty bug. Sun, 26 Feb 2023 --> 2023-02-26 Sunday All Saints in the morning with 2m Peter, encouraging Growing in God meeting afterwards. Pizza lunch, slugged in the afternoon. Sat, 25 Feb 2023 --> 2023-02-25 Saturday Put up new light over the lathe, to be able to see what's up. Helped J. clean up after mowing the lawn. Lunch. Out for a walk at Lynford Arboretum in the afternoon with J. and H. Back, Harry Pottered in the evening. Fri, 24 Feb 2023 --> 2023-02-24 Friday Partner call, staff calls, sync with Paris; lunch. Catch up with Nicolas, Eloy, chunks of admin. Thu, 23 Feb 2023 --> 2023-02-23 Thursday Catch up with E-mail, Miklos, COOL community call, took H. to play piano for the local retirement home. Partner call, sync with Andras, catch up with Naomi. Cell group in the evening. Wed, 22 Feb 2023 --> 2023-02-22 Wednesday Up early, mail chew, positive sales call with the team, partner call, up-beat Collabora Productivity all-hands call. Dug through some legalese, call with Paris and Lubos. Out to band practice, back, mail, chat with Patrick. Tue, 21 Feb 2023 --> 2023-02-21 Tuesday Up early; out for a run with J. Catch up with Kendy, then Pedro, snatched lunch, then a partner call. Monthly management meeting, sync. with Cor, chat with accountant. Mon, 20 Feb 2023 --> 2023-02-20 Monday Mail chew, planning call, lunch with H. Marketing call, Project kick-off call with some of the team. More admin & planning. Sun, 19 Feb 2023 --> 2023-02-19 Sunday All Saints in the morning, meeting afterwards & chat with Rev Robert afterwards; back for a fine roast lunch. Relaxed with a pile of babes, out for a walk with H&M in the afternoon to see the snowdrops & lovely countryside. Sat, 18 Feb 2023 --> 2023-02-18 Saturday Up earlyish, out to Ely to do an Octagon climbing trip with M. out for a nice pub lunch afterwards together. Tried to drive home - but Nissan leaf inoperable, assumed I'd not charged it but - apparently not, a failing 12V battery - very weird needing to jump starting a car with 25kWh+ in its Li-Ion battery Home eventually; hmm. Set too grinding out the grout to get access to the inaccessible isolators feeding the dripping tap in our downstairs bathroom. Watched Tenet with the babes - amusingly: starting at the half-way point, and then re-watching from the start. Fri, 17 Feb 2023 --> 2023-02-17 Friday Up late, customer call, partner sales call, customer call, admin, synched with Anna, interview for a new marketing person, more admin. Thu, 16 Feb 2023 --> 2023-02-16 Thursday A day off! quick mail chew in the morning, drove to Aldeburg with J.H.&E. - partner/sales call at the end of the car ride, had to eat lunch during the call. Had some time to chat to B&A, tidied up a bit, drove back via Sue & Phil's new Rectory in Ipswich - lovely to see them; chips on the way home. Caught up with my blog backlog. Wed, 15 Feb 2023 --> 2023-02-15 Wednesday Encouraging sales call, partner call; synch calls, mail chew. Tue, 14 Feb 2023 --> 2023-02-14 Tuesday Valentines day cards; J. had flowers & a new pringles-like chocolate crisp thing. 1:1s, Nextcloud call, lots of admin & planning. Mon, 13 Feb 2023 --> 2023-02-13 Monday Turns out I threw out H's artwork material - cunningly left in a bin by the front-door (bother). Planning call, worked on the E-mail backlog, talk with Christopher in the evening. Sun, 12 Feb 2023 --> 2023-02-12 Sunday All Saints, band practice in the morning, slugged for much of the afternoon. Sat, 11 Feb 2023 --> 2023-02-11 Saturday J. out to help at Church with open-morning, R&A&babes arrived back from a holiday in Cypress (with muted earthquake) via Stansted for lunch. Enjoyed some time with them. Fri, 10 Feb 2023 --> 2023-02-10 Friday Hoped to clear the day to go out with M. but instead got stuck with important customer & partner calls, and feeling grotty. Urgh. Thu, 09 Feb 2023 --> 2023-02-09 Thursday Still not feeling great; various 1:1's, partner calls, hiring triage. Wed, 08 Feb 2023 --> 2023-02-08 Wednesday Feeling distinctly unwell, coughing up lumps - never good. Up late, to work! A huge backlog of things to get to - sales call, partner call, band-practice at our home. Tue, 07 Feb 2023 --> 2023-02-07 Tuesday Up early, a Eurostar homeward, popped in to the first State of Open Conference chatted to Frank; caught up with some old friends & talks. Home to see the family and recover somewhat late in the evening. Mon, 06 Feb 2023 --> 2023-02-06 Monday Breakfast, and set off to the co-working space; caught up with lots of people individually. Profiled WASM-ness with Tor in firefox with some success - no libpixman acceleration there, and the fall-back methods are horrifyingly slow. Checked on C'bras Turkish team - all well thank God. Out for dinner as a large group, had a spectacularly unpleasant interaction with someone. Enjoyed a chance to get to know Gabriele better in the evening - a kind person at a good time. Sun, 05 Feb 2023 --> 2023-02-05 Sunday Breakfast, and to the conference, more standing by the booth and meeting people left & right. Out to Le Falstaff with a set of friendly hackers, talked until late. Sat, 04 Feb 2023 --> 2023-02-04 Saturday Breakfast, off to the ULB, caught up with a good number of old friends; Dodji requested pushing my blog regularly - so I'll try to keep it more up-to-date. Quested for an internship for H. Quick chat with Lennart before my talk: Snatched some lunch somewhere, talked with Gerald, and met various friends old and new - met up with the cool kids in the LibreOffice dev-room, and gave a quick talk on COOL over lockdown. Back to the hotel, and off to Beta Co-working for a lovely community, pasta dinner - talked much of the time to Andreas, Sophie, Philippe and others. Up late in the hotel lobby. Fri, 03 Feb 2023 --> 2023-02-03 Friday Open Forum Europe day - lots of interesting people to talk to and catch up with; some good presentations too. On to the FLOSS foundations dinner afterwards, then out to the Delerium Cafe with Thorsten - fewer people than normal, caught up with some people, bed extremely late. Thu, 02 Feb 2023 --> 2023-02-02 Thursday Catch up with Miklos, various trains to FOSDEM; met Wookey while waiting for a Eurostar. Arrived, found the Bedford, worked on slides, got some food, finally finished slides without being insanely late - unusual. Perhaps it's possible to avoid the late-night zombification effect of doing the hacking then the slides just before the talk ? Wed, 01 Feb 2023 --> 2023-02-01 Wednesday Weekly sales call, partner meeting, good in-person chat with Simon N. Researched travel, slides etc. Chat with Cor. My content in this blog and associated images / data under images/ and data/ directories are (usually) created by me and (unless obviously labelled otherwise) are licensed under the public domain, and/or if that doesn't float your boat a CC0 license. I encourage linking back (of course) to help people decide for themselves, in context, in the battle for ideas, and I love fixes / improvements / corrections by private mail. In case it's not painfully obvious: the reflections reflected here are my own; mine, all mine ! and don't reflect the views of Collabora, SUSE, Novell, The Document Foundation, Spaghetti Hurlers (International), or anyone else. It's also important to realise that I'm not in on the Swedish Conspiracy . Occasionally people ask for formal photos for conferences or fun . Michael Meeks ( michael.meeks@collabora.com ) | 2026-01-13T09:29:30 |
https://community.jenkins.io/c/contributing/gsoc | Latest GSoC topics - Jenkins Jenkins Contributing GSoC Topic Replies Views Activity About the GSoC category 9 1670 March 3, 2024 [GSoC 2026] Interest in "Improving Plugin Modernizer" Project 1 6 January 12, 2026 Gsoc 2026 Rohan Bhalerao 4yrs (Java Developer) 2 10 January 12, 2026 Excited to contribute meaningfully! 0 6 January 11, 2026 Abhijeet Bhosale - Contributing to Kubernetes Plugin (Exploring Agent Lifecycle Issues) question , contributing , kubernetes 0 15 January 6, 2026 Hitanshu Jena (Interested in Jenkins GSoC 2026) 0 21 January 5, 2026 Introducation : I am Harshal Ingale 0 11 January 4, 2026 Introduction and interest in contributing to Jenkins for GSoC 2026 0 14 January 4, 2026 Interested in participating for the upcoming GSOC with this Organization 0 12 January 3, 2026 I am aiming for GSOC 2026 with this orgnisation 0 9 January 3, 2026 New Contributor Interested in Jenkins & GSoC 2026 , Looking for Guidance. 0 13 January 2, 2026 Introduction - Kshitij Khare working as a Junior SDET to enable and streamline automation 0 14 January 2, 2026 Om Rajput- Java Developer & GSoC 2026 Aspirant 0 10 January 2, 2026 Introduction – Rahul Mahto, Aspiring Jenkins GSoC 2026 Contributor 0 11 December 31, 2025 New contributor preparing for GSoC 2026 – looking for good first issues 0 33 December 24, 2025 Interested in participating GSOC 2026 gsoc 0 31 December 21, 2025 [GSoC 2026 PROJECT IDEA] Built-in Jenkins Assistant for Guided Onboarding and Pipeline Troubleshooting 0 38 December 21, 2025 [GSoC 2026 PROJECT IDEA] Jenkins Safe Actions Framework for Reliable UI POST Handling 0 22 December 20, 2025 Aditya Sah (Interested in Jenkins GSoC 2026) gsoc 1 49 December 20, 2025 Preparing for GSoC 2026 0 34 December 18, 2025 Introduction – Nikita Pandey from Oriental Institute of Science & Technology, Bhopal 22 194 December 14, 2025 Local Implementation of Jenkins - Windows 2 31 December 13, 2025 Introduction – Gayatri Kate, Aspiring GSoC 2026 Contributor 0 23 December 13, 2025 Introduction - GSoC-2026 question 0 33 December 12, 2025 GSoC 2026 Prospective Mentor: Full-Stack ML Engineer (Python/Go/NodeJs) and GSoC x2 (VLC, Oppia) alumnus 0 26 December 8, 2025 Introduction – Kovidhraj from IIIT Nagpur (Exploring Jenkins for GSoC 2026) question 0 13 December 8, 2025 Introduction - Debojyoti De Majumder from IEM Kolkata 0 7 December 7, 2025 Introduction - Adishree Bharadwaj from CMRU, Bangalore, Karnataka 0 15 December 6, 2025 Early Introduction and Guidance Request for GSoC 2026 (Jenkins) 0 38 December 5, 2025 Introduction - Utkarsh Srivastava from VIT Bhopal University(Interested in Jenkins for GSOC 2026) 0 18 December 5, 2025 next page → Home Categories Guidelines Terms of Service Privacy Policy Powered by Discourse , best viewed with JavaScript enabled | 2026-01-13T09:29:30 |
https://docs.aws.amazon.com/fr_fr/lambda/latest/dg/chapter-layers.html | Gestion des dépendances Lambda à l’aide de couches - AWS Lambda Gestion des dépendances Lambda à l’aide de couches - AWS Lambda Documentation AWS Lambda Guide du développeur Utilisation des couches Couches et versions de couches Les traductions sont fournies par des outils de traduction automatique. En cas de conflit entre le contenu d'une traduction et celui de la version originale en anglais, la version anglaise prévaudra. Gestion des dépendances Lambda à l’aide de couches Une couche Lambda est une archive de fichier .zip qui contient du code ou des données supplémentaires. Les couches contiennent généralement des dépendances de bibliothèque, une exécution personnalisée , ou des fichiers de configuration. Vous pouvez envisager d'utiliser des couches pour plusieurs raisons : Pour réduire la taille de vos packages de déploiement. Au lieu d'inclure toutes vos dépendances de fonctions avec votre code de fonction dans votre package de déploiement, placez-les dans une couche. Cela permet de maintenir la taille et l'organisation des packages de déploiement. Pour séparer la logique des fonctions de base des dépendances. Avec les couches, vous pouvez mettre à jour les dépendances de vos fonctions indépendamment du code de votre fonction, et vice versa. Cela favorise la séparation des préoccupations et vous aide à vous concentrer sur la logique de votre fonction. Pour partager les dépendances entre plusieurs fonctions. Après avoir créé une couche, vous pouvez l'appliquer à un certain nombre de fonctions de votre compte. Sans couches, vous devez inclure les mêmes dépendances dans chaque package de déploiement individuel. Pour utiliser l'éditeur de code de la console Lambda. L'éditeur de code est un outil utile pour tester rapidement les mises à jour mineures du code des fonctions. Toutefois, vous ne pouvez pas utiliser l'éditeur si la taille de votre package de déploiement est trop importante. L'utilisation de couches réduit la taille de votre package et peut débloquer l'utilisation de l'éditeur de code. Pour verrouiller une version de SDK intégrée. Les kits SDK intégrés peuvent être modifiés sans préavis au fur et à mesure qu’AWS publie de nouveaux services et fonctionnalités. Vous pouvez verrouiller une version du kit SDK en créant une couche Lambda avec la version spécifique requise. La fonction utilise alors toujours la version de la couche, même si la version intégrée au service change. Si vous utilisez des fonctions Lambda dans Go ou Rust, nous vous déconseillons d’utiliser des couches. Le code des fonctions Go et Rust est fourni sous la forme d’un exécutable, qui contient le code compilé de la fonction ainsi que toutes ses dépendances. Placer vos dépendances dans une couche oblige votre fonction à charger manuellement des assemblages supplémentaires pendant la phase d’initialisation, ce qui peut augmenter les temps de démarrage à froid. Pour des performances optimales pour les fonctions Go et Rust, incluez vos dépendances dans votre package de déploiement. Le diagramme suivant illustre les différences architecturales de haut niveau entre deux fonctions qui partagent des dépendances. L'un utilise des couches Lambda, l'autre non. Lorsque vous ajoutez une couche à une fonction, Lambda extrait le contenu de la couche dans le répertoire /opt de l' environnement d'exécution de votre fonction. Toutes les exécutions Lambda prises en charge en mode natif incluent des chemins vers des répertoires spécifiques dans le répertoire /opt . Cela permet à votre fonction d'accéder au contenu de votre couche. Pour plus d'informations sur ces chemins spécifiques et sur la manière d'empaqueter correctement vos couches, consultez Empaquetage du contenu de votre couche . Vous pouvez inclure jusqu’à cinq couches par fonction. En outre, vous ne pouvez utiliser des couches qu'avec des fonctions Lambda déployées en tant qu'archive de fichiers .zip . Pour des fonctions définies en tant qu'image de conteneur , créez un package avec votre exécution préférée et toutes les dépendances de code lorsque vous créez l'image de conteneur. Pour plus d'informations, consultez Utilisation de couches et d'extensions Lambda dans des images conteneurs sur le blog AWS Compute. Rubriques Utilisation des couches Couches et versions de couches Empaquetage du contenu de votre couche Création et suppression de couches dans Lambda Ajout de couches aux fonctions Utilisation de AWS CloudFormation avec des couches Utilisation de AWS SAM avec des couches Utilisation des couches Pour créer une couche, empaquetez vos dépendances dans un fichier .zip, de la même manière que vous créer un package de déploiement normal . Plus précisément, le processus général de création et d'utilisation de couches comporte les trois étapes suivantes : Empaquetez d'abord le contenu de votre couche. Cela implique de créer une archive de fichiers .zip. Pour de plus amples informations, consultez Empaquetage du contenu de votre couche . Créez ensuite la couche dans Lambda. Pour de plus amples informations, consultez Création et suppression de couches dans Lambda . Ajoutez la couche à vos fonctions). Pour de plus amples informations, consultez Ajout de couches aux fonctions . Couches et versions de couches Une version de couche est un instantané immuable d'une version spécifique d'une couche. Lorsque vous créez une nouvelle couche, Lambda crée une nouvelle version de couche avec un numéro de version de 1. Chaque fois que vous publiez une mise à jour de la couche, Lambda incrémente le numéro de version et crée une nouvelle version de couche. Chaque version de couche est identifiée par un Amazon Resource Name (ARN) unique. Lorsque vous ajoutez une couche à la fonction, vous devez spécifier la version de couche exacte que vous voulez utiliser (par exemple arn:aws:lambda:us-east-1:123456789012:layer:my-layer: 1 ). JavaScript est désactivé ou n'est pas disponible dans votre navigateur. Pour que vous puissiez utiliser la documentation AWS, Javascript doit être activé. Vous trouverez des instructions sur les pages d'aide de votre navigateur. Conventions de rédaction Déboguer avec VS Code Empaquetage des couches Cette page vous a-t-elle été utile ? - Oui Merci de nous avoir fait part de votre satisfaction. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer ce qui vous a plu afin que nous puissions nous améliorer davantage. Cette page vous a-t-elle été utile ? - Non Merci de nous avoir avertis que cette page avait besoin d'être retravaillée. Nous sommes désolés de ne pas avoir répondu à vos attentes. Si vous avez quelques minutes à nous consacrer, merci de nous indiquer comment nous pourrions améliorer cette documentation. | 2026-01-13T09:29:30 |
https://wp.me/PafeZ6-1dE | 워드프레스 웹사이트 또는 블로그 만들기 | 워드프레스닷컴 과정 제품 기능 리소스 요금제 및 가격 로그인 시작하기 메뉴 WordPress 호스팅 에이전시용 WordPress 제휴사 되기 도메인 네임 AI 웹사이트 제작 도구 웹사이트 제작 도구 블로그 생성 뉴스레터 Professional Email 웹사이트 디자인 서비스 상거래 워드프레스 스튜디오 엔터프라이즈 워드프레스 전체 보기 WordPress 테마 WordPress 플러그인 워드프레스 패턴 Google Apps 지원 센터 WordPress 뉴스 비즈니스 이름 생성 도구 로고 메이커 새 글 발견하기 인기있는 태그 블로그 검색 탐색 메뉴 닫기 시작하기 가입 로그인 정보 요금제 및 가격 제품 WordPress 호스팅 에이전시용 WordPress 제휴사 되기 도메인 네임 AI 웹사이트 제작 도구 웹사이트 제작 도구 블로그 생성 뉴스레터 Professional Email 웹사이트 디자인 서비스 상거래 워드프레스 스튜디오 엔터프라이즈 워드프레스 기능 전체 보기 WordPress 테마 WordPress 플러그인 워드프레스 패턴 Google Apps 리소스 지원 센터 WordPress 뉴스 비즈니스 이름 생성 도구 로고 메이커 새 글 발견하기 인기있는 태그 블로그 검색 젯팩 앱 더 알아보기 지원 센터 가이드 과정 포럼 연락처 검색 지원 센터 / 과정 지원 센터 가이드 과정 포럼 연락처 전문가에게 배우세요 워드프레스닷컴 단계별 숙련 과정 참여하기 추천 비디오 과정 워드프레스닷컴에서 웹사이트를 만드세요. 이 단계별 비디오 과정은 사이트를 만드는 데 도움이 됩니다. 회원님의 비전을 온라인으로 구현하는 데 필요한 모든 필수 사항을 알려드리겠습니다. (영어로) 과정 시작 추천 비디오 과정 워드프레스닷컴에서 블로그 생성 이 초보자 과정에서는 워드프레스닷컴에서 블로그를 만드는 방법을 알아봅니다. (영어로) 과정 시작 필요한 내용을 찾을 수 없나요? 문의하기 유료 요금제의 인간 전문가 연중무휴 지원 접근 권한으로 AI 도우미의 답변을 받으세요. 포럼에서 질문하기 질문을 둘러보며 경험이 풍부한 다른 사용자의 답변을 받으세요. WordPress.com 제품 WordPress 호스팅 에이전시용 WordPress 제휴사 되기 도메인 네임 AI 웹사이트 제작 도구 웹사이트 제작 도구 블로그 생성 Professional Email 웹사이트 디자인 서비스 워드프레스 스튜디오 엔터프라이즈 워드프레스 기능 전체 보기 WordPress 테마 WordPress 플러그인 워드프레스 패턴 Google Apps 리소스 워드프레스닷컴 블로그 비즈니스 이름 생성 도구 로고 메이커 WordPress.com 리더 접근성 구독 삭제 도움말 지원 센터 가이드 과정 포럼 연락처 개발자 리소스 회사 정보 프레스 이용 약관 개인 정보 보호 정책 제 개인 정보를 판매하거나 공유하지 마세요 캘리포니아 사용자를 위한 개인 정보 보호 고지 Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Svenska Türkçe Русский العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 English 모바일 앱 다운로드하기 App Store 시작하기 Google Play 소셜 미디어 Facebook의 워드프레스닷컴 워드프레스닷컴 X(Twitter) Instagram의 워드프레스닷컴 YouTube의 워드프레스닷컴 Automattic Automattic WordPress 채용 댓글 로드중... 댓글 달기... 이메일 (필수) 이름 (필수) 웹사이트 지원 가입 로그인 단축 링크 복사 이 콘텐츠 신고하기 구독 관리 | 2026-01-13T09:29:30 |
https://uptimerobot.com/api/v3/?ref-header | API V3 Documentation | UptimeRobot UptimeRobot REST API . UptimeRobot has an easy-to-use API. It lets you get the details of your monitors, create / edit / delete monitors, alert contacts, maintenance windows and public status pages. Response format The API returns data in JSON format. Rate limits We are trying to prevent abusive use of our API. We have rate limits based on user plan. FREE plan : 10 req/min PRO plan : monitor limit * 2 req/min ( with maximum value 5000 req/min ) We will return 429 HTTP status code in the response from API, when you hit the rate limits. Also we will return common rate limit response headers in the response: X-RateLimit-Limit - your current rate limit X-RateLimit-Remaining - number of calls left in current duration X-RateLimit-Reset - time since epoch in seconds at which the rate limiting period will end (or already ended) Retry-After - Number of second after you should retry the call Type of API keys HTTP Basic Access Authentication is used for verifying accounts. There are 3 types of api_keys for reaching the data: Account-specific api_key: Allows using all the API methods on all the monitors of an account. Monitor-specific api_keys: Allows using only the getMonitors method for the given monitor. Read-only api_key: Allows fetching data with all the get* API endpoints. How to get API keys You can get your API keys from the Integrations page under section API . | 2026-01-13T09:29:30 |
https://uptimerobot.com/privacy/ | Privacy Policy | UptimeRobot Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Go to Dashboard Register for FREE Privacy policy . UptimeRobot (a service by Uptime Robot s. r. o.) operates several websites including uptimerobot.com , uptimerobot.com/api and blog.uptimerobot.com . It is UptimeRobot's policy to respect your privacy regarding any information we may collect while operating our websites. What This Policy Covers This Privacy Policy applies to information that we collect about you when you use: Our website uptimerobot.com; Our mobile applications (including the UptimeRobot mobile app for Android and iOS); For users who qualify as data controllers, or who require specific data processing terms, a separate GDPR-compliant Data Processing Agreement (“DPA”) is available upon request and forms part of your contractual relationship with UptimeRobot. Throughout this Privacy Policy, we’ll refer to our website, mobile applications and other products and services collectively as “Services.” Below we explain how we collect, use, and share information about you, along with the choices that you have with respect to that information. Information We Collect We only collect information about you if we have a reason to do so–for example, to provide our Services, to communicate with you, or to make our Services better. We collect information in two ways: if and when you provide information to us and automatically through operating our Services. Let’s go over the information that we collect. Information You Provide to Us It’s probably no surprise that we collect information that you provide to us. The amount and type of information depends on the context and how we use the information. Here are some examples: Basic Account Information: We ask for basic information from you in order to set up your account. For example, we require individuals who sign up for an uptimerobot.com account to provide name-surname, email address , password and that’s it. Transaction and Billing Information: If you buy something from us–a subscription to a uptimerobot.com plan, SMS messages, etc., for example–you will provide additional personal and payment information that is required to process the transaction and your payment, such as your name, credit card information, and contact information. Credentials: Depending on the Services you use, you may provide us with credentials for your website (like SSH, FTP, and SFTP username and password). Communications With Us (Hi There!): You may also provide us information when you respond to surveys or communicate with our team about a support question. Information We Collect Automatically We also collect some information automatically: Log Information: Like most online service providers, we collect information that web browsers, mobile devices, and servers typically make available, such as the browser type, IP address, unique device identifiers, language preference, referring site, the date and time of access, operating system, and mobile network information. We collect log information when you use our Services–for example, when you create or make changes to your account. Usage Information: We collect information about your usage of our Services. For example, we collect information about the pages you visit or site parts that you check the most. We use this information to, for example, provide our Services to you, as well as get insights on how people use our Services, so we can make our Services better. Location Information: We may determine the approximate location of your device from your IP address. We collect and use this information to, for example, calculate how many people visit our Services from certain geographic regions. Information from Cookies & Other Technologies: A cookie is a string of information that a website stores on a visitor’s computer, and that the visitor’s browser provides to the website each time the visitor returns. Pixel tags (also called web beacons) are small blocks of code placed on websites and emails. UptimeRobot uses cookies and other technologies like pixel tags to help us identify and track visitors, usage, and access preferences for our Services, as well as track and understand email campaign effectiveness. And, we will only keep your personal information for as long as it is necessary for the purposes set out in this privacy policy, unless a longer retention period is required or permitted by law (such as tax, accounting or other legal requirements). How And Why We Use Information Purposes for Using Information We use information about you as mentioned above and for the purposes listed below: To provide our Services–for example, to set up and maintain your account or charge you for any of our paid Services; To further develop and improve our Services–for example by adding new features that we think our users will enjoy or will help them to create and manage their monitors more efficiently; To monitor and analyze trends and better understand how users interact with our Services, which helps us improve our Services and make them easier to use; To measure, gauge, and improve the effectiveness of our advertising, and better understand user retention and attrition–for example, we may analyze how many individuals purchased a plan after receiving a marketing message or the features used by those who continue to use our Services after a certain length of time; To monitor and prevent any problems with our Services, protect the security of our Services, detect and prevent fraudulent transactions and other illegal activities, fight spam, and protect the rights and property of UptimeRobot and others, which may result in us declining a transaction or the use of our Services; To communicate with you, for example through an email, about offers and promotions offered by UptimeRobot and others we think will be of interest to you, solicit your feedback, or keep you up to date on UptimeRobot and our products; and To personalize your experience using our Services, provide content recommendations, target our marketing messages to groups of our users (for example, those who have a particular plan with us or have been our user for a certain length of time), and serve relevant advertisements. Legal Bases for Collecting and Using Information A note here for those in the European Union about our legal grounds for processing information about you under EU data protection laws, which is that our use of your information is based on the grounds that: (1) The use is necessary in order to fulfill our commitments to you under our Terms of Service or other agreements with you or is necessary to administer your account–for example, in order to enable access to our website on your device or charge you for a paid plan; or (2) The use is necessary for compliance with a legal obligation; or (3) The use is necessary in order to protect your vital interests or those of another person; or (4) We have a legitimate interest in using your information–for example, to provide and update our Services, to improve our Services so that we can offer you an even better user experience, to safeguard our Services, to communicate with you, to measure, gauge, and improve the effectiveness of our advertising, and better understand user retention and attrition, to monitor and prevent any problems with our Services, and to personalize your experience; or (5) You have given us your consent–for example before we place certain cookies on your device and access and analyze them later on. Sharing Information How We Share Information We do not sell our users’ private personal information. We share information about you in the limited circumstances spelled out below and with appropriate safeguards on your privacy: Subsidiaries, Employees, and Independent Contractors: We may disclose information about you to our subsidiaries, our employees, and individuals who are our independent contractors that need to know the information in order to help us provide our Services or to process the information on our behalf. We require our subsidiaries, employees, and independent contractors to follow this Privacy Policy for personal information that we share with them. Third Party Vendors: We may share information about you with third party vendors who need to know information about you in order to provide their services to us, or to provide their services to you. This group includes vendors that help us provide our Services to you (like payment providers that process your credit and debit card information, fraud prevention services that allow us to analyze fraudulent payment transactions, SMS and email delivery services that help us stay in touch with you), those that assist us with our marketing efforts (e.g. by providing tools for identifying a specific marketing target group or improving our marketing campaigns), those that help us understand and enhance our Services (like analytics providers) who may need information about you in order to, for example, provide technical or other support services to you. We require vendors to agree to privacy commitments in order to share information with them. These vendors are listed in the "List of data sub-processors" section below. Legal Requests: We may disclose information about you in response to a subpoena, court order, or other governmental request. To Protect Rights, Property, and Others: We may disclose information about you when we believe in good faith that disclosure is reasonably necessary to protect the property or rights of UptimeRobot, third parties, or the public at large. For example, if we have a good faith belief that there is an imminent danger of death or serious physical injury, we may disclose information related to the emergency without delay. Business Transfers: In connection with any merger, sale of company assets, or acquisition of all or a portion of our business by another company, or in the unlikely event that UptimeRobot goes out of business or enters bankruptcy, user information would likely be one of the assets that is transferred or acquired by a third party. If any of these events were to happen, this Privacy Policy would continue to apply to your information and the party receiving your information may continue to use your information, but only consistent with this Privacy Policy. With Your Consent: We may share and disclose information with your consent or at your direction. For example, we may share your information with third parties with which you authorize us to do so, such as the social media services that you connect to our site. Aggregated or De-Identified Information: We may share information that has been aggregated or reasonably de-identified, so that the information could not reasonably be used to identify you. For instance, we may publish aggregate statistics about the use of our Services. Security While no online service is 100% secure, we work very hard to protect information about you against unauthorized access, use, alteration, or destruction, and take reasonable measures to do so, such as monitoring our Services for potential vulnerabilities and attacks. To enhance the security of your account, we encourage you to enable our advanced security settings, like Two Step Authentication. Choices You have several choices available when it comes to information about you: Limit the Information that You Provide: If you have an account with us, you can choose not to provide the optional account information, profile information, and transaction and billing information. Please keep in mind that if you do not provide this information, certain features of our Services–for example, paid ones, may not be accessible. Opt-Out of Electronic Communications: You may opt out of receiving promotional messages from us. Just follow the instructions in those messages. If you opt out of promotional messages, we may still send you other messages, like those about your account, monitoring alerts and legal notices. Set Your Browser to Reject Cookies: At this time, UptimeRobot does not respond to “do not track” signals across all of our Services. However, you can usually choose to set your browser to remove or reject browser cookies before using UptimeRobot’s websites, with the drawback that certain features of UptimeRobot’s websites may not function properly without the aid of cookies. Close Your Account: While we’d be very sad to see you go, if you no longer want to use our Services :( :( :( :(, you can close your uptimerobot.com account. Please keep in mind that we may continue to retain your information after closing your account, as described in Information We Collect above–for example, when that information is reasonably needed to comply with (or demonstrate our compliance with) legal obligations such as law enforcement requests, or reasonably needed for our legitimate business interests. Your Rights If you are located in certain countries, including those that fall under the scope of the European General Data Protection Regulation (AKA the “GDPR”), data protection laws give you rights with respect to your personal data, subject to any exemptions provided by the law, including the rights to: Request access to your personal data; Request correction or deletion of your personal data; Object to our use and processing of your personal data; Request that we limit our use and processing of your personal data; and Request portability of your personal data. You can usually access, correct, or delete your personal data using your account settings and tools that we offer, but if you aren’t able to do that, or you would like to contact us about one of the other rights, scroll down to How to Reach Us to, well, find out how to reach us. EU individuals also have the right to make a complaint to a government supervisory authority. How to Reach Us If you have a question about this Privacy Policy, or you would like to contact us about any of the rights mentioned in the Your Rights section above, please contact us directly via support@uptimerobot.com . Other Things You Should Know (Keep Reading!) Transferring Information Because UptimeRobot’s Services are offered worldwide, the information about you that we process when you use the Services in the EU may be used, stored, and/or accessed by individuals operating outside the European Economic Area (EEA) who work for us, other members of our group of companies, or third party data processors. This is required for the purposes listed in the How and Why We Use Information section above. When providing information about you to entities outside the EEA, we will take appropriate measures to ensure that the recipient protects your personal information adequately in accordance with this Privacy Policy as required by applicable law. Ads and Analytics Services Provided by Others Other parties may also provide analytics services via our Services. These analytics providers may set tracking technologies (like cookies) to collect information about your use of our Services and across other websites and online services. These technologies allow these third parties to recognize your device to compile information about you or others who use your device. This information allows us and other companies to, among other things, analyze and track usage. Please note this Privacy Policy only covers the collection of information by UptimeRobot and does not cover the collection of information by any third party advertisers or analytics providers. List of Sub-processors UptimeRobot uses the following products/services (which are all GDPR compliant): Limestone Networks: for sending monitoring requests and storing data. Amazon Web Services: for sending monitoring requests and storing data. Digital Ocean: for sending monitoring requests and storing data. Plivo: for sending SMS and voice notifications. Stripe: for credit card payments. 2Checkout: for credit card payments. PayPal: for PayPal and credit card payments. Google Tag Manager: for serving 3rd party scripts. Google Analytics (Universal Analytics and/or Google Analytics 4): for analyzing the browsing behavior of our users and visitors. Google BigQuery: for business analysis and analyzing the browsing behavior of our users and visitors. Google Fonts: for loading a custom fonts. Rollbar: for loggin errors and bugs. User.com: for CRM service, behavioral messages and updates about product. Intercom.com: for CRM service, customer support, online chat, behavioral messages and updates about product. Sendgrid.com: for sending emails, e.g. account related, occasional deal offers, etc. Google Ads: for auto-pausing Google ads during downtimes and for ads targeting. Facebook Ads: for auto-pausing Facebook ads during downtimes. Miscrosoft Clarity: To capture how you use and interact with our website through behavioral metrics, heatmaps, and session replay to improve and market our products/services. Website usage data is captured using first and third-party cookies and other tracking technologies to determine the popularity of products/services and online activity. Additionally, we use this information for app and web site optimization and advertising. For more information about how Microsoft collects and uses your data, visit the Microsoft Privacy Statement . “Subscribe to updates” feature on Status pages Status page is a voluntary option to showcase your uptime to your customers. With the PRO plan you can enable the subscription feature allowing your customers to subscribe to the announcements and updates you’ll share on your status page. These emails are sent from our servers. Such a customer will subscribe using his email address. This customer needs to confirm his subscription through an email he’ll receive to his inbox. His email address is stored in our database and the owner of the status page doesn’t have access to it and can’t view it anywhere. The customer can unsubscribe through a link available in every status update email he’ll receive and through an option available on the status page all the time. This action needs to be confirmed through an email too. The Status page owner or UptimeRobot has the right to remove users from this updates list anytime without informing the subscribed user. If the Status page is removed, all related data, subscribed emails included, will be removed too. Privacy Policy Changes Although most changes are likely to be minor, UptimeRobot may change its Privacy Policy from time to time, and in UptimeRobot's sole discretion. UptimeRobot encourages visitors to frequently check this page for any changes to its Privacy Policy. When making material changes to this Privacy Policy, we will provide advance notice to these material changes taking effect. Notification will be provided via website banner/notification, platform pop-up upon login, and direct email for active paying users. Non-material changes will be documented in the change log at the end of this Privacy Policy. Change log: January 8, 2026: Added Intercom to the list of sub-processors. September 23, 2025: Added Data Processing Agreement and updated Privacy Policy Changes. August 15, 2023: Updated list of sub-processors. July 27, 2023: Updated list of sub-processors. June 6, 2022: Updated list of sub-processors. April 26, 2021: Added Status pages and status updates sent from Status pages. April 23, 2021: Added Rollbar and Google Fonts to the list of sub-processors. July 15, 2019: Added Google Ads and Facebook Ads to the list of sub-processors. May 21, 2018: Updated for GDPR compliance. June 12, 2017: Removed Paylane from the list of payment processors. July 1, 2016: Updated the company name to reflect the change. May 20, 2014: Updated various typos. Nov 14, 2014: Added "payment processors used". This "Privacy Policy" is based on the "Creative Commons" licensed policy by WordPress (the awesome guys that created WordPress). Downtime happens. Get notified! Join more than 2,700,000+ happy users! UptimeRobot is one of the most popular website monitoring services in the world. Monitoring . Website monitoring SSL monitoring Domain monitoring Ping monitoring Port monitoring TCP monitoring Cron job monitoring Keyword monitoring Location-specific monitoring Response time monitoring Incident Management DNS monitoring Company . Pricing Blog Affiliate program Referral program Non profit & charities 🤲 Terms / Privacy Contact us We are hiring! Resources . Integrations API FAQs Help center Locations & IPs Comparisons Case studies Knowledge hub Roadmap Subnet calculator MX lookup Uptime calculator CrontabRobot Website change detection Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Register for FREE 🍪 This website use cookies. Learn more Decline all | Allow essential | Accept all | 2026-01-13T09:29:30 |
https://uptimerobot.com/customers/ | Meet Our Users | UptimeRobot Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Go to Dashboard Register for FREE Meet our users . Discover how 2.5M users worldwide trust UptimeRobot for reliable uptime monitoring. Start monitoring in 30 seconds See how companies monitor with UptimeRobot. WordPress VIP Thanks to monitoring thousands of domains, WordPress VIP improved response times and performance while also saving on infrastructure costs. Read more ConfigCat ConfigCat significantly enhanced the user experience and trust by making UptimeRobot and live alerts an essential part of their uptime monitoring. Read more Stratosphere Lab As a security research lab, Stratosphere needed to find reliable monitoring that would allow them to keep all IoT devices operational. Read more Heineken Heineken improves delivery efficiency, avoids disruptions, and ensures reliable operations across its global network by monitoring critical services. Read more Start monitoring in 30 seconds Why people love UptimeRobot . div; delay: 100; hidden: false, offset-top: 250"> "I have been using UptimeRobot for years in my previous job, to monitor a dozen websites. In my current job, we have just started implementing it. With 10+ years of experience working with UptimeRobot, I can say it's a very stable tool, reliable, with very few false flags. The interface is very clear, alerts are super easy to set up. Support is very responsive. Great free price plan and non-profit scheme." René V. Functional Application Manager "The ease of setup and the speed with which alerts are received in case of outages or interruptions. Its dashboard is intuitive, allowing the monitoring of multiple services from a single place, and its integration with channels like email or Microsoft Teams enhances the technical team's response capability." Roberto A. Deputy Director of Security "We've been using Uptimerobot as an organization in some form or fashion for many, many years and appreciate the stability and longevity of the product and company. They keep adding features yet maintain the simple, ease-of-use for powerful features." Jeff M. Director of Digital Experience "Very reliable service with great incident reporting and tracking. Nice and easy to set up, including to monitor other status pages (which other services some times seem to struggle with). Even the free plan feature set is quite generous and the updated interface is great too!" Edward C. Network Manager "Really positive, the solution works well over email and SMS and hasn't let me down. I like the pricing, it's really competitive compared to the market leaders and the solution has worked well for me." Colin B. Chief innovation officer "Unlike many other status page solutions, Uptime Robot provides near real-time updates fully automatically, giving you peace of mind when monitoring your services. End users, customers, and businesses can easily check the status of critical services via clear and user-friendly status pages. One standout feature is SSL certificate monitoring – Uptime Robot notifies you well in advance before a certificate expires, helping to prevent unnecessary downtime." Rico Senior Developer "I needed a simple, reliable way to know if my services go down without paying for an expensive monitoring solution. UptimeRobot has been perfect for my needs—lightweight, effective, and hassle-free." Matt A. Web Developer The leading uptime monitoring solution . Basem A. Reliable service It was a wonderful experience and I would highly recommend it. UptimeRobot has exceeded my expectations with its efficient monitoring and notification system. Thanks to their service, I've been able to stay on top of any downtime issues and ensure maximum uptime for my online presence, highly recommended! Reviewed on Capterra.com Michael N., Director of Media Relations UptimeRobot Works Great -- And Believe It! Our Native Amerrican news magazine/public service website is www.nativeamericatoday.com. Our former developer did a horrible job, which continually allowed bots to attack the site -- we went over our server's resource limits multiple times and crashed... Reviewed on G2.com Michael Palmer Piece of Mind Monitoring I have recently moved monitoring to UptimeRobot for some critical links and external facing services within our organization. Internal monitoring programs are great until the internet is down and you don't know because you can't get the alerts out... Reviewed on Trustpilot.com Basem A. Reliable service It was a wonderful experience and I would highly recommend it. UptimeRobot has exceeded my expectations with its efficient monitoring and notification system. Thanks to their service, I've been able to stay on top of any downtime issues and ensure maximum uptime for my online presence, highly recommended! Reviewed on Capterra.com Michael N., Director of Media Relations UptimeRobot Works Great -- And Believe It! Our Native Amerrican news magazine/public service website is www.nativeamericatoday.com. Our former developer did a horrible job, which continually allowed bots to attack the site -- we went over our server's resource limits multiple times and crashed... Reviewed on G2.com 4.7 stars out of 5 230+ reviews on G2 Meet our users Empowering every team to stay online . UptimeRobot, the world’s leading uptime monitoring service, serves a diverse user base. Explore tailored solutions for your role. Devops Developers Marketers Support Business owners Devops DevOps teams use UptimeRobot to catch incidents early, stay ahead of SLAs, and ensure services are reliable across environments. Explore more Developers Developers rely on UptimeRobot to instantly detect when something breaks—whether it’s an API, webhook, website or staging deployment—so they can fix issues before users notice. Explore more Marketers Marketers use UptimeRobot to monitor landing pages and campaign URLs, ensuring every visit counts and downtime doesn’t impact traffic and revenues. Explore more Support Support teams rely on UptimeRobot to stay informed when issues arise, enabling them to respond faster, keep users updated, and reduce ticket volume with real-time status updates. Explore more Business owners Business owners use UptimeRobot for peace of mind—getting alerts when their website goes down and knowing everything’s running smoothly, even when they’re not online. Explore more Start monitoring in 30 seconds How we give back. . We support more than 250 charities, non-profit organizations, and open-source projects with sponsored monitoring. Are you one of them, or would you like to suggest someone? Let us know. Explore sponsorships Simple pricing . Powerful monitoring . Save ~20% with annual billing . Annual Monthly Free . $ 0 / month Good for hobby projects. No credit card required! Register now 50 monitors 😐 5 min. monitoring interval HTTP, port & ping monitor Keyword monitor Location-specific monitoring Slow response alerts DNS monitoring SSL & Domain exp. monitor 😐 Only 5 integrations 😐 Basic status pages Notify seats unavailable No login seats available Solo . $ 8 7 8 19 15 19 / month Great for solopreneurs and hobbyists. Subscribe now 10 monitors 50 monitors 60 sec. monitoring interval HTTP, port & ping monitor Keyword monitor 🆕 Location-specific monitoring 🆕 Slow response alerts 🆕 DNS monitoring SSL & Domain exp. monitor 🙂 Only 9 integrations 😐 Basic status pages Notify seats available No login seats available Team . $ 34 29 34 / month For a small team who needs to collaborate. Subscribe now 100 monitors 60 sec. monitoring interval HTTP, port & ping monitor Keyword monitor 🆕 Location-specific monitoring 🆕 Slow response alerts 🆕 DNS monitoring SSL & Domain exp. monitor All 12 integrations Full-featured status pages 3 notify seats incl. 3 login seats incl. Enterprise . $ 64 54 64 149 124 149 376 289 376 / month For those who just need more. Subscribe now Get quote 200 monitors 500 monitors 1,000+ monitors 30 sec. monitoring interval HTTP, port & ping monitor Keyword monitor 🆕 Location-specific monitoring 🆕 Slow response alerts 🆕 DNS monitoring SSL & Domain exp. monitor All 12 integrations Full-featured status pages 5 notify seats incl. 5 login seats incl. See feature comparison Get your FREE account now, 50 monitors included ! Start monitoring in 30 seconds No credit card required! Available also on: How many monitors do you need? UptimeRobot offers custom monitoring solutions tailored for agencies, service providers, software companies, and enterprises. Number of monitors Use the slider to estimate the number of monitors. 1k 5k 15k 25k+ Email Company Name Book a demo You will be redirected to a calendar booking page Downtime happens. Get notified! Join more than 2,700,000+ happy users! UptimeRobot is one of the most popular website monitoring services in the world. Monitoring . Website monitoring SSL monitoring Domain monitoring Ping monitoring Port monitoring TCP monitoring Cron job monitoring Keyword monitoring Location-specific monitoring Response time monitoring Incident Management DNS monitoring Company . Pricing Blog Affiliate program Referral program Non profit & charities 🤲 Terms / Privacy Contact us We are hiring! Resources . Integrations API FAQs Help center Locations & IPs Comparisons Case studies Knowledge hub Roadmap Subnet calculator MX lookup Uptime calculator CrontabRobot Website change detection Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Register for FREE 🍪 This website use cookies. Learn more Decline all | Allow essential | Accept all | 2026-01-13T09:29:30 |
https://ja-jp.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0LEov6cz1ioW7wZYvRoNCYoCDjdjkEpOhWmlE0QNeDROc7WUwfwZ4g-BlF7KnMioV-t741JYgSpGwGqEsdRP0rM5Aq6g6jPSpPQMnIbNJ_Gktg0ks0bvtkQBTxCZQlzPAJ0MHuz4LYJzL7 | Facebook Facebook メールアドレスまたは電話番号 パスワード アカウントを忘れた場合 新しいアカウントを作成 機能の一時停止 機能の一時停止 この機能の使用ペースが早過ぎるため、機能の使用が一時的にブロックされました。 Back 日本語 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) Português (Brasil) Français (France) Deutsch アカウント登録 ログイン Messenger Facebook Lite 動画 Meta Pay Metaストア Meta Quest Ray-Ban Meta Meta AI Meta AIのコンテンツをもっと見る Instagram Threads 投票情報センター プライバシーポリシー プライバシーセンター Facebookについて 広告を作成 ページを作成 開発者 採用情報 Cookie AdChoices 規約 ヘルプ 連絡先のアップロードと非ユーザー 設定 アクティビティログ Meta © 2026 | 2026-01-13T09:29:30 |
https://aws.amazon.com/ec2/nitro/ | AWS Nitro System Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account Compute › Amazon EC2 › AWS Nitro System AWS Nitro System A combination of dedicated hardware and lightweight hypervisor enabling faster innovation and enhanced security Get started with a Nitro-based Instance today Why AWS Nitro System? The AWS Nitro System is the foundation for our next generation of EC2 instances that enables AWS to innovate faster, further reduce cost for our customers, and deliver added benefits like increased security and new instance types. AWS has completely re-imagined our virtualization infrastructure. Traditionally, hypervisors protect the physical hardware and bios, virtualize the CPU, storage, networking, and provide a rich set of management capabilities. With the Nitro System, we are able to break apart those functions, offload them to dedicated hardware and software, and reduce costs by delivering practically all of the resources of a server to your instances. Play Benefits Faster innovation The Nitro System is a rich collection of building blocks that can be assembled in many different ways, giving us the flexibility to design and rapidly deliver EC2 instance types with an ever-broadening selection of compute, storage, memory, and networking options. This innovation also leads to bare metal instances where customers can bring their own hypervisor or have no hypervisor. Enhanced security The Nitro System provides enhanced security that continuously monitors, protects, and verifies the instance hardware and firmware. Virtualization resources are offloaded to dedicated hardware and software minimizing the attack surface. Finally, Nitro System's security model is locked down and prohibits administrative access, eliminating the possibility of human error and tampering. Better performance and price The Nitro System delivers practically all of the compute and memory resources of the host hardware to your instances resulting in better overall performance. Additionally, dedicated Nitro Cards enable high speed networking, high speed EBS, and I/O acceleration. Not having to hold back resources for management software means more savings that can be passed on to the customer. Support for previous generation instances AWS Nitro System supports previous generation EC2 instances to extend the length of service beyond the typical lifetime of underlying hardware. The AWS Nitro System provides modern hardware and software components for EC2 instances, allowing customers to continue running their workloads on the instance families they were built on. Learn more Key Features Nitro Cards The Nitro Cards are a family of cards that offloads and accelerates IO for functions, ultimately increasing overall system performance. Key cards include Nitro Card for VPC, Nitro Card for EBS, Nitro Card for Instance Storage, Nitro Card Controller, and Nitro Security Chip. Nitro Security Chip The Nitro Security Chip enables the most secure cloud platform with a minimized attack surface as virtualization and security functions are offloaded to dedicated hardware and software. Additionally, a locked down security model prohibits all administrative access, including those of Amazon employees, eliminating the possibility of human error and tampering. Nitro Hypervisor The Nitro Hypervisor is a lightweight hypervisor that manages memory and CPU allocation and delivers performance that is indistinguishable from bare metal. AWS Nitro Enclaves AWS Nitro Enclaves enables customers to create isolated compute environments to further protect and securely process highly sensitive data such as personally identifiable information (PII), healthcare, financial, and intellectual property data within their Amazon EC2 instances. Nitro Enclaves uses the same Nitro Hypervisor technology that provides CPU and memory isolation for EC2 instances. Learn more NitroTPM NitroTPM, a Trusted Platform Module (TPM) 2.0, is a security and compatibility feature that makes it easier for customers to use applications and operating system capabilities that depend on TPMs in their EC2 instances. It conforms to the TPM 2.0 specification, which makes it easy to migrate existing on-premises workloads that use TPM functionalities to EC2. NitroTPM provides a secure cryptographic offload using the AWS Nitro System, and allows EC2 instances to generate, store, and use keys without having access to the same keys. NitroTPM can also provide a cryptographic proof of your instances' integrity via TPM attestation mechanisms. Resources Whitepapers White Paper - Security Design of the AWS Nitro System Learn more Video Video - re:Inforce - Security Benefits of EC2 Nitro Architecture (Launch Pad) Watch the video Video Video - re:Inforce - Security Benefits of EC2 Nitro Architecture (Presentation) Watch the video Video Video - re:Invent - Nitro Deep Dive (Presentation) Watch the video Video Video - re:invent - Evolution of Nitro System (Presentation) Watch the video Blog Jeff Barr Blog Read the blog Blog Perspectives - AWS Nitro System Support for Previous Generation Instances - James Hamilton Read the blog Get started with AWS 1 Sign up for an AWS account Instantly get access to the AWS Free Tier . 2 Learn with 10-minute Tutorials Explore and learn with simple tutorials . 3 Start building with AWS Begin building with step-by-step guides to help you launch your AWS project . Next steps Getting started Ready to get started? Sign up AWS Solution Have more questions? Contact us Did you find what you were looking for today? Let us know so we can improve the quality of the content on our pages. Yes No Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T09:29:30 |
https://cloudflare.com/small-business/#pricing-plans-at-a-glance | Cloudflare for Small & medium-sized businesses | Cloudflare Sign up Languages English English (United Kingdom) Deutsch Español (Latinoamérica) Español (España) Français Italiano 日本語 한국어 Polski Português (Brasil) Русский 繁體中文 简体中文 Platform Connectivity cloud Cloudflare’s connectivity cloud delivers 60+ networking, security, and performance services. Enterprise For large and medium organizations Small business For small organizations Partner Become a Cloudflare partner use cases Modernize applications Accelerate performance Ensure app availability Optimize web experience Modernize security VPN replacement Phishing protection Secure web apps and APIs Modernize networks Coffee shop networking WAN modernization Simplify your corporate network CxO topics Adopt AI Bring AI into workforces and digital experiences AI security Secure agentic AI and GenAI applications Data compliance Streamline compliance and minimize risk Post-quantum cryptography Safeguard data and meet compliance standards Industries Healthcare Banking Retail Gaming Public sector Resources Product guides Reference architectures Analyst reports Engage Events Demos Webinars Workshops Request a demo Products products Workspace security Zero trust network access Secure web gateway Email security Cloud access security broker Application security L7 DDoS protection Web application firewall API security Bot management Application performance CDN DNS Smart routing Load balancing Networking and SASE L3/4 DDoS protection NaaS / SD-WAN Firewall-as-a-service Network Interconnect plans & pricing Enterprise plans Small business plans Individual plans Compare plans Global services Support and success bundles Optimized Cloudflare experience Professional services Expert-led implementation Technical account management Focused technical management Security operations service Cloudflare monitoring and response Domain registration Buy and manage domains 1.1.1.1 Free DNS resolver Resources Product guides Reference architectures Analyst reports Product demos and tours Help me choose Developers documentation Developer library Documentation and guides Application demos Explore what you can build Tutorials Step-by-step build tutorials Reference architecture Diagrams and design patterns Products Artificial Intelligence AI Gateway Observe, control AI apps Workers AI Run ML models on our network Compute Observability Logs, metrics, and traces Workers Build, deploy serverless apps Media Images Transform, optimize images Realtime Build real-time audio/video apps Storage & database D1 Create serverless SQL databases R2 Store data without costly egress fees Plans & Pricing Workers Build and deploy serverless apps Workers KV Serverless key-value store for apps R2 Store data without costly egrees fees Explore projects Customer stories AI Demo in 30 seconds Quick guide to get started Explore Workers Playground Build, test, and deploy Developers Discord Join the community Start building Partners Partner Network Grow, innovate and meet customer needs with Cloudflare Partner Portal Find resources and register deals Partnership Types PowerUP Program Grow your business while keeping your customers connected and secure Technology Partners Explore our ecosystem of technology partners and integrators Global System Integrators Support seamless large-scale digital transformation Service Providers Discover our network of valued service providers Self-serve agency program Manage Self-Serve Accounts for your clients Peer-to-peer portal Traffic insights for your network Find a partner PowerUP your business - connect with Cloudflare Powered+ partners. Resources Engage Demos + product tours On-demand product demos Case studies Driving success with Cloudflare Webinars Insightful discussions Workshops Virtual forums Library Helpful guides, roadmaps, and more Reports Insights from Cloudflare’s research Blog Technical deep dives and product news Learning center Educational tools and how-to content Build Reference architecture Technical guides Solution + product guides Product documentation Documentation Developer documentation Explore theNET Executive insights for the digital enterprise Cloudflare TV Innovative series and events Cloudforce One Threat research and operations Radar Internet traffic and security trends Analyst reports Industry research reports Events Upcoming regional events Trust, privacy, and compliance Compliance information and policies Support Contact us Community forum Lost account access? Developers Discord Get help Company Company info Leadership Meet our leaders Investor relations Investor information Press Explore recent news Careers Explore open roles Trust, Privacy, & Safety Privacy Policy, data, and protection Trust Policy, process, and safety Compliance Certification and regulation Transparency Policy and disclosures Public Interest Humanitarian Project Galileo Government Athenian Project Elections Cloudflare For Campaigns Health Project Fair Shot Global network Global locations and status Log in Contact sales Security, performance, and reliability for your website and applications Cloudflare’s Pro and Business Plans help optimize your web performance and defend against advanced cyber attacks — while delivering a best-in-class customer experience. Get exceptional value with every subscription plan. See plans Sign up Core features Best-in-class WAF Cloudflare's Web Application Firewall (WAF) offers superior protection by analyzing incoming traffic, blocking malicious requests, and blocking OWASP threats like SQL injection, cross-site scripting (XSS), zero-day vulnerabilities. Cache Analytics for CDN optimization Easily track the site assets that are missing, expired, or ineligible for caching — then use the Cloudflare CDN to increase the number of cached resources and improve site speed. Enhanced protection with machine learning Cloudflare uses advanced machine learning to track and mitigate sophisticated, evolving cyber threats — from malicious bots and other advanced attackers. WordPress plugin Enhance the performance of your WordPress site with the Automatic Platform Optimization (APO) plugin for CDN, intelligent caching, and more. Turn it on and go (up to 300% faster). Content prefetch for Google Search Automatic Signed Exchange enables browsers to prefetch your website on Google's search results page, helping improve your core web vitals and speeding up your website. No-code performance tools The setup is simple, fast, and intuitive, and you can turn on extra features with a single click. Connect with a Cloudflare partner to help you build and protect your application or website. Find a partner Cloudflare Small Business Guide It’s easy to build and grow with Cloudflare, but just as importantly, you don’t have to trade off security to do it. To help small businesses navigate the complexities of securing their online presence, we’ve created a step-by-step guide to make it simple to get started with Cloudflare’s free plan. With Cloudflare, small businesses can launch confidently and stay protected. Download guide Looking to try a proof of concept? Start for free Frequently asked questions How does Cloudflare work? Cloudflare protects and accelerates any website online. Once your website is a part of the Cloudflare community, its web traffic is routed through our intelligent global network. We automatically optimize the delivery of your web pages so your visitors get the fastest page load times and best performance. We also block threats and limit abusive bots and crawlers from wasting your bandwidth and server resources. Where can I learn more about using Cloudflare? The easiest way to learn how to use Cloudflare is to sign-up, which takes less than 5 minutes. When is my billing date? The date you first select a paid plan will be the recurring billing date. For example: If you sign up for the first time on January 10, all future charges will be billed on the 10th of every month. What happens when I upgrade? If you currently have a paid plan (e.g. Pro) for one of your domains and upgrade to a higher priced plan (e.g. Business), the following happens: You will be debited the hourly pro-rata cost of the Business plan until the end of the billing cycle You will be credited the hourly pro-rata cost of the Pro plan until the end of the billing cycle At the beginning of the next billing cycle, you will be charged for the full cost of the Business plan You will receive an invoice upon successful payment of the upgrade Have more questions? Visit our FAQs page Trusted by millions of Internet properties View case studies GETTING STARTED Free plans Small business plans For enterprises Get a recommendation Request a demo Contact sales SOLUTIONS Connectivity cloud Application services SASE and workspace security Network services Developer platform SUPPORT Help center Customer support Community forum Developers Discord Lost account access? Cloudflare status COMPLIANCE Compliance resources Trust GDPR Responsible AI Transparency report Report abuse PUBLIC INTEREST Project Galileo Athenian Project Cloudflare for Campaigns Project Fairshot COMPANY About Cloudflare Network map Our team Logos & press kit Diversity, equity, & inclusion Impact/ESG © 2026 Cloudflare, Inc. Privacy Policy Terms of Use Report Security Issues Cookie Preferences Trademark | 2026-01-13T09:29:30 |
https://wordpress.com/zh-tw/patterns | WordPress 區塊版面配置：以 10 倍速度打造你的網頁 — WordPress.com WordPress.com Products WordPress Hosting WordPress for Agencies Become an Affiliate Domain Names AI Website Builder Website Builder Create a Blog Newsletter Professional Email Commerce WordPress Studio Enterprise WordPress Features Overview WordPress Themes WordPress Plugins WordPress Patterns Google Apps Resources WordPress.com Support WordPress News Business Name Generator Logo Maker Discover New Posts Popular Tags Blog Search Plans & Pricing Log In Get Started Menu Close the navigation menu Get Started Sign Up Log In About Plans & Pricing Products WordPress Hosting WordPress for Agencies Become an Affiliate Domain Names AI Website Builder Website Builder Create a Blog Newsletter Professional Email Commerce WordPress Studio Enterprise Features Overview WordPress Themes WordPress Plugins WordPress Patterns Google Apps Resources WordPress.com Support News Business Name Generator Logo Maker Discover New Posts Popular Tags Blog Search 使用版面配置，架站更快速 立即探索數百種專業設計、能自動調整版面的版型，快速打造出各種類型的網站。 全部分類 頁首 頁尾 404 錯誤 關於 封存範本 文章 連絡人 活動 表單 圖庫 主角 自介連結 位置 選單 電子報 頁面範本 頁面標題 作品集 文章範本 價格 搜尋範本 服務 團隊 證言 用版面配置來打造一切 擁有超多精美且功能強大的版面配置供你選用，打造出完全符合你或客戶需求的頁面，又快又輕鬆。 標題 1 複製版面配置 頁首 8 種版面配置 頁尾：營業時間、社群媒體、聯絡方式 複製版面配置 頁尾 13 種版面配置 404 範本 1 複製版面配置 404 錯誤 1 種版面配置 捐款 複製版面配置 關於 10 種版面配置 封存範本 複製版面配置 封存範本 2 種版面配置 文章 (頁面) 複製版面配置 文章 7 種版面配置 聯絡人 1 複製版面配置 連絡人 8 種版面配置 活動 (頁面) 複製版面配置 活動 10 種版面配置 聯絡人 1 複製版面配置 表單 7 種版面配置 圖庫：兩欄文字和圖片 複製版面配置 圖庫 7 種版面配置 英雄 1 複製版面配置 主角 13 種版面配置 連結在個人檔案 3 複製版面配置 自介連結 3 種版面配置 地圖 4 複製版面配置 位置 5 種版面配置 選單 2 複製版面配置 選單 5 種版面配置 電子報：圖片在左邊註冊 複製版面配置 電子報 4 種版面配置 頁面 - 先顯示圖片 複製版面配置 頁面範本 2 種版面配置 頁面標題 1 複製版面配置 頁面標題 2 種版面配置 作品集 1 複製版面配置 作品集 2 種版面配置 單一文章偏移 複製版面配置 文章範本 5 種版面配置 價格 6 複製版面配置 價格 6 種版面配置 搜尋結果照片 複製版面配置 搜尋範本 4 種版面配置 服務 (頁面) 複製版面配置 服務 10 種版面配置 Team 3 複製版面配置 團隊 7 種版面配置 檢視 3 複製版面配置 證言 6 種版面配置 複製、貼上、調整，就這麼簡單 選取一種版面配置，把它複製貼上到你的設計中，然後以你的喜好來自由調整。無需外掛程式。 複製貼上，也能展現自我 直接在 WordPress 編輯器內貼上版面配置，然後任你調整。 充分發揮你的個人風格 版面配置可以複製你網站的字體與色彩配置設定，確保每個頁面都維持一致的形象。 按你喜愛的方式調整 版面配置整合各種常用的 WordPress 區塊於一身，你可以按照自己的喜好來調整各項細節。 回應式設計 所有版面配置都完全符合回應式設計，在任何裝置或螢幕上都美輪美奐。 美觀大方的嚴選頁面版型 我們的頁面版型，可以讓你使用預先設計的版面配置，輕鬆打造出專業外觀的頁面。 文章 (頁面) 複製版面配置 文章 3 種版型 複製版面配置 連絡人 1 種版型 活動 (頁面) 複製版面配置 活動 1 種版型 圖庫：兩欄文字和圖片 複製版面配置 圖庫 4 種版型 選單 (頁面) 複製版面配置 選單 1 種版型 定價 (頁面) 複製版面配置 價格 1 種版型 服務 (頁面) 複製版面配置 服務 1 種版型 版面配置所有資訊 來看看我們的操作指南，開始使用版面配置。 打造網站 影片教學課程 區塊格式 影片教學課程 使用預製頁面版型 免費課程 讓網站更快推出上線 WordPress.com Products WordPress Hosting WordPress for Agencies Become an Affiliate Domain Names AI Website Builder Website Builder Create a Blog Professional Email Website Design Services WordPress Studio WordPress Enterprise Features Overview WordPress Themes WordPress Plugins WordPress Patterns Google Apps Resources WordPress.com Support WordPress Forums WordPress News Business Name Generator Logo Maker Discover New Posts Popular Tags Blog Search Developer Resources Accessibility Company About Press Terms of Service Privacy Policy Language Change Language English Deutsch Español Français Bahasa Indonesia Italiano Nederlands Português do Brasil Română Svenska Türkçe Русский Ελληνικά العربية עִבְרִית 日本語 한국어 简体中文 繁體中文 Mobile Apps Get it on Google Play Download on the App Store Social Media WordPress.com on X (Twitter) WordPress.com on Facebook WordPress.com on Instagram WordPress.com on YouTube Automattic Work With Us Work With Us Please enable JavaScript in your browser to enjoy WordPress.com. | 2026-01-13T09:29:30 |
https://www.linkedin.com/uas/login?session_redirect=https%3A%2F%2Fwww.linkedin.com%2Fposts%2Fbarclays-bank_news-barclays-is-collaborating-with-expectai-activity-7407466483812941824-cEgN&trk=public_post_ellipsis-menu-semaphore-sign-in-redirect&guestReportContentType=POST&_f=guest-reporting | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:30 |
https://www.linkedin.com/uas/login?session_redirect=https%3A%2F%2Fwww.linkedin.com%2Fposts%2Fbarclays-bank_news-barclays-is-collaborating-with-expectai-activity-7407466483812941824-cEgN&trk=public_post_comment_ellipsis-menu-semaphore-sign-in-redirect&guestReportContentType=COMMENT&_f=guest-reporting | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:30 |
https://www.linkedin.com/jobs/boston-consulting-group-%28bcg%29-jobs-worldwide | 1,000+ Boston Consulting Group (bcg) jobs in Worldwide Skip to main content LinkedIn Boston Consulting Group (bcg) in Worldwide Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Sign in Join for free Any time Any time (1,219) Past month (1,216) Past week (540) Past 24 hours (85) Done Company Clear text Boston Consulting Group (BCG) (879) BCG Platinion (204) Jerry (75) BCG X (31) Inverto | A BCG Company (14) Done Job type Full-time (1,108) Part-time (13) Contract (23) Temporary (5) Internship (68) Done Experience level Internship (153) Entry level (207) Associate (29) Mid-Senior level (751) Director (70) Done Remote On-site (1,054) Hybrid (88) Remote (77) Done Get notified when a new job is posted. Set alert Sign in to set job alerts for “Boston Consulting Group (bcg)” roles. Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . 1,000+ Boston Consulting Group (bcg) Jobs in Worldwide Data Scientist, United States - BCG X Data Scientist, United States - BCG X Boston Consulting Group (BCG) Brooklyn, NY Actively Hiring 1 week ago Data Scientist, United States - BCG X Data Scientist, United States - BCG X Boston Consulting Group (BCG) Manhattan Beach, CA Actively Hiring 5 days ago Data Scientist, 新卒/New Graduate 2027, BCG X , Japan Data Scientist, 新卒/New Graduate 2027, BCG X , Japan Boston Consulting Group (BCG) Tokyo, Japan Actively Hiring 4 days ago ******** *******, ******** ******** *******, ******** ****** ********** ***** (***) ***** ******, ******* ********* ** ***** ******, ******** Actively Hiring 1 week ago *********, **********, ********* *********, **********, ********* ****** ********** ***** (***) *********, ********* Actively Hiring 2 weeks ago **** *********, ****** ****** - *** * **** *********, ****** ****** - *** * ****** ********** ***** (***) *** *******, ** Actively Hiring 1 week ago **** *********, ****** ****** - *** * **** *********, ****** ****** - *** * ****** ********** ***** (***) *** *********, ** Actively Hiring 1 week ago Sign in to view all job postings Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to view more jobs Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T09:29:30 |
https://www.youtube.com/watch?v=kQxKkEm3oDA | Mind Blowing CSS Only Animation in 2023 || Demo Code - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0x7b1cabc7627ef678"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgtvVG53ZEdpdHBvZyj4oJjLBjIKCgJLUhIEGgAgIQ%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRrkDSgziX43RaETeu0PQY4YBngsjgEAZ18jHRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","decoratedAvatarViewModel","avatarViewModel","contentMetadataViewModel","sheetViewModel","listViewModel","listItemViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoAttributeViewModel","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","compactInfocardRenderer","structuredDescriptionVideoLockupRenderer","structuredDescriptionPlaylistLockupRenderer","thumbnailOverlayBottomPanelRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cardCollectionRenderer","cardRenderer","simpleCardTeaserRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgtvVG53ZEdpdHBvZyj4oJjLBjIKCgJLUhIEGgAgIQ%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwjin86GmoiSAxVoWw8CHeQvBSQyDHJlbGF0ZWQtYXV0b0iwwN7NhNKShpEBmgEFCAMQ-B3KAQRSxUZs","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=aP1dmMVyEKU\u0026start_radio=1\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"aP1dmMVyEKU","params":"EAEYAcABAdoBBAgBKgC4BQE%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjin86GmoiSAxVoWw8CHeQvBSQyDHJlbGF0ZWQtYXV0b0iwwN7NhNKShpEBmgEFCAMQ-B3KAQRSxUZs","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=aP1dmMVyEKU\u0026start_radio=1\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"aP1dmMVyEKU","params":"EAEYAcABAdoBBAgBKgC4BQE%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwjin86GmoiSAxVoWw8CHeQvBSQyDHJlbGF0ZWQtYXV0b0iwwN7NhNKShpEBmgEFCAMQ-B3KAQRSxUZs","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=aP1dmMVyEKU\u0026start_radio=1\u0026pp=QAFIAQ%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"aP1dmMVyEKU","params":"EAEYAcABAdoBBAgBKgC4BQE%3D","playerParams":"QAFIAQ%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"Mind Blowing CSS Only Animation in 2023 || Demo Code"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 473회"},"shortViewCount":{"simpleText":"조회수 473회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CMsCEMyrARgAIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC2tReEtrRW0zb0RBGmBFZ3RyVVhoTGEwVnRNMjlFUVVBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDJ0UmVFdHJSVzB6YjBSQkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CMsCEMyrARgAIhMI4p_OhpqIkgMVaFsPAh3kLwUk"}}],"trackingParams":"CMsCEMyrARgAIhMI4p_OhpqIkgMVaFsPAh3kLwUk","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"5","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNkCEKVBIhMI4p_OhpqIkgMVaFsPAh3kLwUk"}},{"innertubeCommand":{"clickTrackingParams":"CNkCEKVBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CNoCEPqGBCITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNoCEPqGBCITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"kQxKkEm3oDA"},"likeParams":"Cg0KC2tReEtrRW0zb0RBIAAyDAj5oJjLBhCl2ai_AQ%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CNoCEPqGBCITCOKfzoaaiJIDFWhbDwId5C8FJA=="}}}}}}}]}},"accessibilityText":"다른 사용자 5명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNkCEKVBIhMI4p_OhpqIkgMVaFsPAh3kLwUk","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"6","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNgCEKVBIhMI4p_OhpqIkgMVaFsPAh3kLwUk"}},{"innertubeCommand":{"clickTrackingParams":"CNgCEKVBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"kQxKkEm3oDA"},"removeLikeParams":"Cg0KC2tReEtrRW0zb0RBGAAqDAj5oJjLBhCHwqm_AQ%3D%3D"}}}]}},"accessibilityText":"다른 사용자 5명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNgCEKVBIhMI4p_OhpqIkgMVaFsPAh3kLwUk","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CMsCEMyrARgAIhMI4p_OhpqIkgMVaFsPAh3kLwUk","isTogglingDisabled":true}},"likeStatusEntityKey":"EgtrUXhLa0VtM29EQSA-KAE%3D","likeStatusEntity":{"key":"EgtrUXhLa0VtM29EQSA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNYCEKiPCSITCOKfzoaaiJIDFWhbDwId5C8FJA=="}},{"innertubeCommand":{"clickTrackingParams":"CNYCEKiPCSITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CNcCEPmGBCITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNcCEPmGBCITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"kQxKkEm3oDA"},"dislikeParams":"Cg0KC2tReEtrRW0zb0RBEAAiDAj5oJjLBhCx46q_AQ%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CNcCEPmGBCITCOKfzoaaiJIDFWhbDwId5C8FJA=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNYCEKiPCSITCOKfzoaaiJIDFWhbDwId5C8FJA==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNUCEKiPCSITCOKfzoaaiJIDFWhbDwId5C8FJA=="}},{"innertubeCommand":{"clickTrackingParams":"CNUCEKiPCSITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"kQxKkEm3oDA"},"removeLikeParams":"Cg0KC2tReEtrRW0zb0RBGAAqDAj5oJjLBhCFhKu_AQ%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNUCEKiPCSITCOKfzoaaiJIDFWhbDwId5C8FJA==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CMsCEMyrARgAIhMI4p_OhpqIkgMVaFsPAh3kLwUk","isTogglingDisabled":true}},"dislikeEntityKey":"EgtrUXhLa0VtM29EQSA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgtrUXhLa0VtM29EQSD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CNMCEOWWARgHIhMI4p_OhpqIkgMVaFsPAh3kLwUk"}},{"innertubeCommand":{"clickTrackingParams":"CNMCEOWWARgHIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtrUXhLa0VtM29EQaABAQ%3D%3D","commands":[{"clickTrackingParams":"CNMCEOWWARgHIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CNQCEI5iIhMI4p_OhpqIkgMVaFsPAh3kLwUk","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CNMCEOWWARgHIhMI4p_OhpqIkgMVaFsPAh3kLwUk","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CNECEOuQCSITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CNICEPuGBCITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DkQxKkEm3oDA\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNICEPuGBCITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CNICEPuGBCITCOKfzoaaiJIDFWhbDwId5C8FJA=="}}}}}},"trackingParams":"CNECEOuQCSITCOKfzoaaiJIDFWhbDwId5C8FJA=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CM8CEOuQCSITCOKfzoaaiJIDFWhbDwId5C8FJA=="}},{"innertubeCommand":{"clickTrackingParams":"CM8CEOuQCSITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CNACEPuGBCITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DkQxKkEm3oDA\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CNACEPuGBCITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CNACEPuGBCITCOKfzoaaiJIDFWhbDwId5C8FJA=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CM8CEOuQCSITCOKfzoaaiJIDFWhbDwId5C8FJA==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CMsCEMyrARgAIhMI4p_OhpqIkgMVaFsPAh3kLwUk","superTitleLink":{"runs":[{"text":"#threejs","navigationEndpoint":{"clickTrackingParams":"CM4CEKW3AxgAIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/threejs","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gULCgd0aHJlZWpzGAE%3D"}},"loggingDirectives":{"trackingParams":"CM4CEKW3AxgAIhMI4p_OhpqIkgMVaFsPAh3kLwUk","visibility":{"types":"12"}}},{"text":" "},{"text":"#designidea","navigationEndpoint":{"clickTrackingParams":"CM0CEKW3AxgCIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/designidea","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gUOCgpkZXNpZ25pZGVhGAE%3D"}},"loggingDirectives":{"trackingParams":"CM0CEKW3AxgCIhMI4p_OhpqIkgMVaFsPAh3kLwUk","visibility":{"types":"12"}}},{"text":" "},{"text":"#designs","navigationEndpoint":{"clickTrackingParams":"CMwCEKW3AxgEIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/hashtag/designs","webPageType":"WEB_PAGE_TYPE_BROWSE","rootVe":6827,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"FEhashtag","params":"6gULCgdkZXNpZ25zGAE%3D"}},"loggingDirectives":{"trackingParams":"CMwCEKW3AxgEIhMI4p_OhpqIkgMVaFsPAh3kLwUk","visibility":{"types":"12"}}}]},"dateText":{"simpleText":"2023. 8. 26."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"2년 전"}},"simpleText":"2년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/l3cAlSFe_4_j1D4vFIZ5rCU-_-oyUMd07c84Hl90ikbZi4E7Znuh0GylKyH4uM70oTpxed7Q=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/l3cAlSFe_4_j1D4vFIZ5rCU-_-oyUMd07c84Hl90ikbZi4E7Znuh0GylKyH4uM70oTpxed7Q=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/l3cAlSFe_4_j1D4vFIZ5rCU-_-oyUMd07c84Hl90ikbZi4E7Znuh0GylKyH4uM70oTpxed7Q=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"demo code","navigationEndpoint":{"clickTrackingParams":"CMoCEOE5IhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/@democode","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCTBG1pUL9HtP4ntbj63Fngw","canonicalBaseUrl":"/@democode"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CMoCEOE5IhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/@democode","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCTBG1pUL9HtP4ntbj63Fngw","canonicalBaseUrl":"/@democode"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 1.59천명"}},"simpleText":"구독자 1.59천명"},"trackingParams":"CMoCEOE5IhMI4p_OhpqIkgMVaFsPAh3kLwUk"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCTBG1pUL9HtP4ntbj63Fngw","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"CLwCEJsrIhMI4p_OhpqIkgMVaFsPAh3kLwUkKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"demo code을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"demo code을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. demo code 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CMkCEPBbIhMI4p_OhpqIkgMVaFsPAh3kLwUk","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. demo code 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. demo code 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CMgCEPBbIhMI4p_OhpqIkgMVaFsPAh3kLwUk","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. demo code 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"CMECEJf5ASITCOKfzoaaiJIDFWhbDwId5C8FJA==","command":{"clickTrackingParams":"CMECEJf5ASITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CMECEJf5ASITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"CMcCEOy1BBgDIhMI4p_OhpqIkgMVaFsPAh3kLwUkMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQRSxUZs","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ1RCRzFwVUw5SHRQNG50Ymo2M0ZuZ3cSAggBGAAgBFITCgIIAxILa1F4S2tFbTNvREEYAA%3D%3D"}},"trackingParams":"CMcCEOy1BBgDIhMI4p_OhpqIkgMVaFsPAh3kLwUk","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"CMYCEO21BBgEIhMI4p_OhpqIkgMVaFsPAh3kLwUkMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQRSxUZs","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ1RCRzFwVUw5SHRQNG50Ymo2M0ZuZ3cSAggDGAAgBFITCgIIAxILa1F4S2tFbTNvREEYAA%3D%3D"}},"trackingParams":"CMYCEO21BBgEIhMI4p_OhpqIkgMVaFsPAh3kLwUk","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"CMICENuLChgFIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CMICENuLChgFIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CMMCEMY4IhMI4p_OhpqIkgMVaFsPAh3kLwUk","dialogMessages":[{"runs":[{"text":"demo code"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CMUCEPBbIhMI4p_OhpqIkgMVaFsPAh3kLwUkMgV3YXRjaMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCTBG1pUL9HtP4ntbj63Fngw"],"params":"CgIIAxILa1F4S2tFbTNvREEYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CMUCEPBbIhMI4p_OhpqIkgMVaFsPAh3kLwUk"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CMQCEPBbIhMI4p_OhpqIkgMVaFsPAh3kLwUk"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"CMICENuLChgFIhMI4p_OhpqIkgMVaFsPAh3kLwUk"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"CLwCEJsrIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CMACEP2GBCITCOKfzoaaiJIDFWhbDwId5C8FJDIJc3Vic2NyaWJlygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253DkQxKkEm3oDA%26continue_action%3DQUFFLUhqbElxMmlMVkNCcmhuNWlGU2I3MGtER1d6T29YUXxBQ3Jtc0trMjFyUWFwdDRXclFLWndtTkdULWUtaW4zTjZNZkxSTllUZng1S0FjaTMwNE9vMzh2U0JuWUVFb01pLVpKVjBqQ0VHTVFCQUw4dkJHclAxUmo1WGJVb2lfR0ZmNlVES2VKc0lmejNUS25sdzdCODd0SVV4akZvdjZwdFEzTWZrM3VzcEhsNjUtdk1WQURSelNMNVUzZkxOUWV1YXhwMWNvQUpjTDhleFN3THJoUlJNWUpURmw1dUZxVFVSN09fT0xGNk5Td00\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CMACEP2GBCITCOKfzoaaiJIDFWhbDwId5C8FJMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbElxMmlMVkNCcmhuNWlGU2I3MGtER1d6T29YUXxBQ3Jtc0trMjFyUWFwdDRXclFLWndtTkdULWUtaW4zTjZNZkxSTllUZng1S0FjaTMwNE9vMzh2U0JuWUVFb01pLVpKVjBqQ0VHTVFCQUw4dkJHclAxUmo1WGJVb2lfR0ZmNlVES2VKc0lmejNUS25sdzdCODd0SVV4akZvdjZwdFEzTWZrM3VzcEhsNjUtdk1WQURSelNMNVUzZkxOUWV1YXhwMWNvQUpjTDhleFN3THJoUlJNWUpURmw1dUZxVFVSN09fT0xGNk5Td00","idamTag":"66429"}},"trackingParams":"CMACEP2GBCITCOKfzoaaiJIDFWhbDwId5C8FJA=="}}}}}},"subscribedEntityKey":"EhhVQ1RCRzFwVUw5SHRQNG50Ymo2M0ZuZ3cgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"CLwCEJsrIhMI4p_OhpqIkgMVaFsPAh3kLwUkKPgdMgV3YXRjaMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCTBG1pUL9HtP4ntbj63Fngw"],"params":"EgIIAxgAIgtrUXhLa0VtM29EQQ%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"CLwCEJsrIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"CLwCEJsrIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"CL0CEMY4IhMI4p_OhpqIkgMVaFsPAh3kLwUk","dialogMessages":[{"runs":[{"text":"demo code"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"CL8CEPBbIhMI4p_OhpqIkgMVaFsPAh3kLwUkKPgdMgV3YXRjaMoBBFLFRmw=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCTBG1pUL9HtP4ntbj63Fngw"],"params":"CgIIAxILa1F4S2tFbTNvREEYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"CL8CEPBbIhMI4p_OhpqIkgMVaFsPAh3kLwUk"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"CL4CEPBbIhMI4p_OhpqIkgMVaFsPAh3kLwUk"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUk"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUk","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Mind Blowing CSS Only Animation in 2023\n\nWe made an Awesome list of free CSS Generator\nhttps://democoding.in/awesome-free-css-gen...\n\n100 HTML Login Forms For your next project\nhttps://jonsnow7741.gumroad.com/l/100-css-... \n\nCheck my website for amazing CSS animation \nhttps://democoding.in/\n\nTime Stamps\n(0:00) - Intro\n(0:18) - 1. Catch the light game in pure CSS\n(0:58) - 2. Firework Effect Animation in Pure CSS\n(1:22) - 3. SVG Water Reflection in Pure CSS\n(1:34) - 4. Flying through hexagons animation in pure CSS\n(2:43) - 5. 3D 2023 CSS Toggle Switch Animation\n(2:53) - 6. Ring of Balls Animation in Pure CSS\n(3:12) - 7. 3D Animated Loader in CSS\n(3:28) - 8. Weird CSS Animation\n(3:38) - 9. 3D Hand Finger tap Animation\n(3:55) - 10. Ball of Balls Animation in Pure CSS\n(4:07) - 11. Morphing Flowers Animation in Pure CSS\n\n\nFollow me on Instagram : @fromgoodthings\nhttps://www.instagram.com/fromgoodthings/\n\nFollow me on Facebook \nhttps://www.facebook.com/programmingmemesb...\n\n\nSource Code\n1. https://democoding.in/codepen-ideas/catch-...\n2. https://democoding.in/codepen-ideas/firewo...\n3. https://democoding.in/codepen-ideas/svg-wa...\n4. https://democoding.in/codepen-ideas/flying...\n5. https://democoding.in/codepen-ideas/3d-202...\n6. https://democoding.in/codepen-ideas/ring-o...\n7. • 3D Animated Loader in CSS || Loaders anima... \n8. https://democoding.in/codepen-ideas/keep-c...\n9. • 3D Hand Finger tap Animation in CSS | #3d ... \n10. https://democoding.in/codepen-ideas/ball-o...\n11. https://democoding.in/codepen-ideas/morphi...\n\nPlaylist \n1. Loaders Animation \n • Loaders Animation \n\n2. Three JS Example\n • Three JS Examples \n\n3. CSS Animation example\n • CSS Animation Example \n\n4. Girls who code \n • girls who code \n\nFree CSS Tools\n1. CSS Glassmorphism Generator\nhttps://democoding.in/css-glassmorphism-ge...\n\n2. Neumorphism CSS Generator\nhttps://democoding.in/neumorphism-css-gene...\n\n3. CSS Gradient Generator\nhttps://democoding.in/css-gradient-generator\n\nWant to see more of my content? Check out my Linktree\nhttps://linktr.ee/jonSnow77\n\n#shorts #threejs #webgl #javascriptanimation #css #code #designidea #designs @democode #codepen #animation \n\nThree js animation, three js examples , three js code, three js , WebGL animation javascript animation, \nCSS loading animation, CSS loading, CSS animation tutorial, CSS loading spinner, CSS loading text animation, CSS loading page, CSS loading screen, CSS loading bar, CSS loading bar animation, CSS loading animation CSS loader, CSS loading dots, CSS loading button, css loader react, css loader angular, css loader react native, css loader flutter, css loader with z-index, css loader effect, css loading animation tutorial, loading animation figma, loading animation css, loading animation css HTML, loading animation in WordPress, loading animation in android studio, \n\nMusic \n\n\"Keys of Moon - The Epic Hero\" is under a Creative Commons license (CC BY-SA 3.0) https://creativecommons.org/licenses/...\nMusic promoted by BreakingCopyright: https://bit.ly/the-epic-hero-song","commandRuns":[{"startIndex":306,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":0,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"0초"}}},{"startIndex":322,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA\u0026t=18s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":18,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026osts=18\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"18초"}}},{"startIndex":367,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA\u0026t=58s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":58,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026osts=58\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"58초"}}},{"startIndex":417,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA\u0026t=82s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":82,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026osts=82\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"1분 22초"}}},{"startIndex":462,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA\u0026t=94s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":94,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026osts=94\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"1분 34초"}}},{"startIndex":520,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA\u0026t=163s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":163,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026osts=163\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"2분 43초"}}},{"startIndex":569,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA\u0026t=173s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":173,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026osts=173\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"2분 53초"}}},{"startIndex":619,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA\u0026t=192s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":192,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026osts=192\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"3분 12초"}}},{"startIndex":658,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA\u0026t=208s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":208,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026osts=208\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"3분 28초"}}},{"startIndex":691,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA\u0026t=218s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":218,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026osts=218\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"3분 38초"}}},{"startIndex":733,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA\u0026t=235s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":235,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026osts=235\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"3분 55초"}}},{"startIndex":783,"length":4,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=kQxKkEm3oDA\u0026t=247s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"kQxKkEm3oDA","continuePlayback":true,"startTimeSeconds":247,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr1---sn-ab02a0nfpgxapox-bh2zr.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=910c4a9049b7a030\u0026ip=1.208.108.242\u0026osts=247\u0026initcwndbps=4391250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"4분 7초"}}},{"startIndex":1301,"length":52,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=o_qSMI8hwCo","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"o_qSMI8hwCo","startTimeSeconds":0,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh2s6.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=a3fa92308f21c02a\u0026ip=1.208.108.242\u0026initcwndbps=3955000\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"YouTube Channel Link: 3D Animated Loader in CSS || Loaders animation in css || #cssanimation"}}},{"startIndex":1406,"length":52,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=Q-ha1S6KOFg","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"Q-ha1S6KOFg","startTimeSeconds":0,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh2zs.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=43e85ad52e8a3858\u0026ip=1.208.108.242\u0026initcwndbps=3626250\u0026mt=1768296317\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"YouTube Channel Link: 3D Hand Finger tap Animation in CSS | #3d Finger tap animation | #cssanimation"}}},{"startIndex":1592,"length":24,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLXFF1LYCsRv8gGY1MXW54RDIBFDFiilJX","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLXFF1LYCsRv8gGY1MXW54RDIBFDFiilJX","canonicalBaseUrl":"/playlist?list=PLXFF1LYCsRv8gGY1MXW54RDIBFDFiilJX"}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"YouTube Channel Link: Loaders Animation"}}},{"startIndex":1638,"length":24,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLXFF1LYCsRv-3vWnZETjIzx0j74O8Er4B","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLXFF1LYCsRv-3vWnZETjIzx0j74O8Er4B","canonicalBaseUrl":"/playlist?list=PLXFF1LYCsRv-3vWnZETjIzx0j74O8Er4B"}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"YouTube Channel Link: Three JS Examples"}}},{"startIndex":1689,"length":28,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLXFF1LYCsRv9RyQQfBNhhduRBkd5Rx41Q","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPLXFF1LYCsRv9RyQQfBNhhduRBkd5Rx41Q","canonicalBaseUrl":"/playlist?list=PLXFF1LYCsRv9RyQQfBNhhduRBkd5Rx41Q"}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"YouTube Channel Link: CSS Animation Example"}}},{"startIndex":1738,"length":21,"onTap":{"innertubeCommand":{"clickTrackingParams":"CLECEM2rARgBIhMI4p_OhpqIkgMVaFsPAh3kLwUkygEEUsVGbA==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PLXFF1LYCsRv-DCnn_2XkPx25dvnsf | 2026-01-13T09:29:30 |
https://es-la.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0LEov6cz1ioW7wZYvRoNCYoCDjdjkEpOhWmlE0QNeDROc7WUwfwZ4g-BlF7KnMioV-t741JYgSpGwGqEsdRP0rM5Aq6g6jPSpPQMnIbNJ_Gktg0ks0bvtkQBTxCZQlzPAJ0MHuz4LYJzL7 | Facebook Facebook Correo o teléfono Contraseña ¿Olvidaste tu cuenta? Crear cuenta nueva Se te bloqueó temporalmente Se te bloqueó temporalmente Parece que hiciste un uso indebido de esta función al ir muy rápido. Se te bloqueó su uso temporalmente. Back Español 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Registrarte Iniciar sesión Messenger Facebook Lite Video Meta Pay Tienda de Meta Meta Quest Ray-Ban Meta Meta AI Más contenido de Meta AI Instagram Threads Centro de información de votación Política de privacidad Centro de privacidad Información Crear anuncio Crear página Desarrolladores Empleo Cookies Opciones de anuncios Condiciones Ayuda Importación de contactos y no usuarios Configuración Registro de actividad Meta © 2026 | 2026-01-13T09:29:30 |
https://www.linkedin.com/posts/boston-consulting-group_ces2026-bcgatces-activity-7415853587538452480-M6YF#main-content | BCG Experts on AI Trends at CES2026 | Boston Consulting Group (BCG) posted on the topic | LinkedIn Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now Boston Consulting Group (BCG) 5,237,774 followers 2d Report this post From humanoid robots to generative and physical AI, the focus is shifting toward real operational impact across manufacturing, supply chains, and mobility. View the video from our BCG experts for more on the trends that defined #CES2026 this year. #BCGatCES …more 74 4 Comments Like Comment Share Copy LinkedIn Facebook X Imran Jamal 2d Report this comment Humanoid robots and physical AI hitting manufacturing and supply chains means we're past the demo phase. Real operational impact is where ROI lives, not in concept videos. The companies winning here aren't the flashiest. They're the ones solving bottlenecks no one talks about. Like Reply 2 Reactions 3 Reactions Sunburnt AI 2d Report this comment Spot on! The move toward humanoid robots and physical AI is exactly what we needed to see this year. Like Reply 2 Reactions 3 Reactions NAMBURU NARASIMHA RAO 1d Report this comment From Demos to Deployment CES2026 showed that AI is no longer a showcase of ideas but a platform for industrial scale impact across factories, logistics and mobility. What matters now is how leaders turn generative and physical intelligence into real productivity, resilience and competitive advantage. Like Reply 1 Reaction Eros MLima ⌚ 2d Report this comment #AI is the new future and Humanoid Robots is not the present yet. #BCG in the Future. Like Reply 1 Reaction See more comments To view or add a comment, sign in More Relevant Posts ValiantCXO 32 followers 1w Report this post Robotics and AI in American factories are transforming the manufacturing landscape like never before. Picture a bustling factory floor where robots hum alongside human workers, and artificial intelligence (AI) orchestrates the entire operation like a conductor leading a symphony. This isn’t science fiction—it’s the reality of modern American manufacturing. From automotive plants in Detroit to tech hubs in Silicon Valley, the integration of robotics and AI is boosting efficiency, cutting costs, and redefining what it means to “make it in America.” In this article, we’ll dive deep into how robotics and AI in American factories are shaping the future, exploring their benefits, challenges, and what lies ahead. Ready to see how these technologies are changing the game? Let’s get started. https://lnkd.in/dGRJRXf6 #airevolution #aiintech #ai2026 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in George Offord 2d Report this post #ces2026 #physical_ai #humanoids #ai_defined_vehicles Physical AI Made Waves At CES 2026. What Is It? Physical AI is the industry’s shorthand for AI that does not just generate content, but also can perceive the real world, reasons about it and acts on it through machines like robots, vehicles, industrial equipment and always-on consumer devices. https://lnkd.in/deA77cKt 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Fabio Nogueira 2w Report this post 🌟 The integration of AI and robotics into our daily lives has the potential to revolutionize our work and social interactions. As technology evolves, we're faced with the exciting possibility of merging human intellect with robotic precision. 🌟 The integration of AI and robotics into our daily lives has the potential to revolutionize our work and social interactions. As technology evolves, we're faced with the exciting possibility of merging human intellect with robotic precision. 🚀 Visionaries like Elon Musk predict a future where AI could make traditional jobs obsolete, allowing us to turn our passions into leisurely pursuits. But what does this mean for our society? Will automation lead to a utopia of creativity and freedom, or will it present new challenges? 📈 As we stand on the brink of this technological transformation, it's crucial to explore how these advancements will reshape our world. How can we harness the power of AI to enhance our lives while ensuring ethical considerations and inclusivity? 🔗 Watch the full video here to dive deeper into the fascinating topic: https://lnkd.in/dBMuT8-k #AI #Robotics #FutureOfWork #Innovation #Technology #Automation #DigitalTransformation #ArtificialIntelligence #TechTrends #Society #ElonMusk #Innovation #Future #Tech #MindUploading Watch here: https://lnkd.in/dQWACmBU …more AI & Robots: The Future of Work & Society #shorts https://www.youtube.com/ 7 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Robo Success 391 followers 3w Report this post The robotics industry is moving faster than ever, and 2026 will be a turning point. We've identified 5 key #trends poised to reshape everything from healthcare to the creative industries. Emotional #AI , generative #robots , nanobots, predictive intelligence, and self-healing machines... This is not science fiction; it’s already happening. Swipe through and share with us. Which trend will have the most significant impact? #DigitalMarketing #MarketingforRobots #RoboticsandAI 10 1 Comment Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Jesica Chavez 🤖🎙️ 3w Report this post Five game-changing trends shaping robotics in 2026. Technology is moving fast. Regulation, adoption, and trust? Not so much. Are we ready — or just excited? #Robotics #AI #Trends #EmbodiedAI Robo Success 391 followers 3w The robotics industry is moving faster than ever, and 2026 will be a turning point. We've identified 5 key #trends poised to reshape everything from healthcare to the creative industries. Emotional #AI , generative #robots , nanobots, predictive intelligence, and self-healing machines... This is not science fiction; it’s already happening. Swipe through and share with us. Which trend will have the most significant impact? #DigitalMarketing #MarketingforRobots #RoboticsandAI 18 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Balakumaraa Puvanendran MBCS CITP CC CL 2w Report this post As we move through late 2025, the robotics industry has pivoted from "machines that work" to "agents that relate." The convergence of Agentic AI—autonomous, goal-oriented systems—and advanced biomimetic engineering has birthed a new generation of social humanoids. For roboticists, policymakers, and C-suite executives, the challenge is no longer just mechanical; it is deeply psychological and aesthetic. Gemini - Humanizing Robots with Agentic AI gemini.google.com Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in Jim Hoey 3w Report this post AI, robotics, and energy transitions are reshaping the business landscape! McKinsey's latest insights highlight how emerging tech trends like agentic AI and adaptive robotics are driving innovation and efficiency. Stay ahead by embracing these transformative technologies and reimagining your business for the future. Explore the trends shaping tomorrow's business agenda today #BusinessTechnology #AI #AgenticAI https://lnkd.in/eWkT5y3h Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in BDO USA 184,045 followers 4w Report this post 2026 will reshape tech: AI maturation, media consolidation, robotics, and more. Explore our predictions for what’s ahead in the tech industry: https://bdousa.com/44WPf8Y #technology #AiInTech View C2PA information 4 1 Comment Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in RISE Robotics 621 followers 3w Report this post 🤖 Real-time human motion prediction just got smarter. Researchers introduced PrediFlow, a framework that predicts how humans will move during robot collaboration—and it actually accounts for how robots influence human behavior. Most prediction methods either generate unrealistic movements or miss how robots and humans interact in real-time. This new approach uses Flow Matching to refine predictions while preserving uncertainty and capturing multiple possible movement patterns. Tested on industrial disassembly tasks, it improves accuracy without sacrificing speed—staying within real-world time constraints. • Why it matters: Safer, more efficient human-robot collaboration depends on robots understanding not just where humans go, but why—and how their own presence shapes those decisions. Follow for more breakthroughs in robotics and AI! 🚀 #Robotics #HumanRobotCollaboration #MotionPrediction #AI #Automation #IndustrialRobotics Source: https://lnkd.in/gRwiqvtz View C2PA information 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in DATABEYOND 1,125 followers 4d Report this post The 2026 International Consumer Electronics Show sent a clear signal: Artificial intelligence is transitioning from perception to action. From the latest updates coming in from the event, it's evident that practical applications of AI are gaining increasing attention. This aligns perfectly with our own path. In industrial sorting, AI recognition alone is no longer sufficient. We are dedicated to developing embodied intelligence, enabling precise material handling before and after sorting—thus completing the final mile of machine replacement. At DATABEYOND , we bridge perception, decision-making, and execution—making industrial AI truly take root！ 👉 Learn More： https://www.databeyond.com #CES2026 #ArtificialIntelligence #EmbodiedAI #IndustrialAI #PhysicalAI #AIInIndustry #Robotics #Automation #WasteSorting #Databeyond 1 Like Comment Share Copy LinkedIn Facebook X To view or add a comment, sign in 5,237,774 followers View Profile Connect More from this author How to Tackle the AI Skills Gap Boston Consulting Group (BCG) 1w Our Most Essential Reads of the Year Boston Consulting Group (BCG) 3w The New Fuel-Economy Rules Just Changed the Auto Game—Again Boston Consulting Group (BCG) 3w Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T09:29:30 |
https://go.setapp.com/stp336?utm_medium=vendor_program&utm_source=Smmall+Inc&utm_content=link | Setapp | Powerful apps for Mac & iOS Marketplace Membership How it works Solve with AI+ Pricing Blog About Setapp Menu Sign in Try free Home Marketplace Membership How it works Solve with AI+ Pricing Blog About Setapp Sign in beta exclusive Meet Eney, a local-first AI assistant for busywork Learn More Dozens of apps. One subscription. Try free for 7 days Power up your workflow with Setapp, a smart way to get apps. What you get on Setapp. With a single monthly subscription, you get 260+ apps for your Mac. Tidy up your Mac Run performance optimization, free up space, remove duplicates. Write code Create applications in more than 25 languages Stay focused Boost your productivity with timed sessions Work on your music Record and mix your own music Make quick mockups Generate instant mockups for your products Plan projects Map out your ideas for impeccable planning Convert files Convert audio, video, images in seconds Customize menu bar Control and arrange your menu bar icons View all superpowers Your Setapp journey. Type in your task into Setapp search and get instant app recommendations. Search by task Explore recommendations Use on Mac & iOS Install as many as you like Musicians like Jason use Setapp to push the limits of their creativity, dancing through tasks for more time to play. Jason Staczek Authors like Scott use Setapp to organize hundreds of docs and thousands of words, making book writing look easy. Scott McKain Stage performers like Tom use Setapp to capture thoughts, plan them out, and transform ideas into action. Tom Hartman Developers like Luka use Setapp to take on massive projects with minimal effort, using the right tools for shortcuts. Luka Anicic GPT-4, Whisper, DALL·E, and other top AI models under one roof Solve with AI+ Build an effective daily routine with a single AI toolkit $14.99/mo to start. Use all the models you like 9+ powerful apps utilizing the latest AI models All 260+ apps from Setapp Membership are included Friendly UI, helpful documentation, and 24/7 support No technical knowledge required Try free for 7 days read huge documents in minutes type with voice auto-generate email replies write content from scratch take notes ask anything Setapp in your words. What you say about how Setapp powers you up. Have been using Setapp for almost two years, and I have to say it's the best and the most cost-effective way of having apps on Mac. Arash Pourhabibi @ArashPourhabibi My favorites ❤️ from @Setapp Ulysses, CleanMyMac X, Paste, MindNode, Swift Publisher. Mauricio Sanchez @m741s For those of you that wonder where I discover/get all the awesome apps for my Mac that I use, a lot of them are from Setapp! Meredith Sweet @meredith.sweet.silberstein The whole Setapp product is worth a look. I use a bunch of tools in there every day to speed up workflows. David Hill @iamdavidhill I’ve been using Setapp since the beginning. I can’t imagine what it would be like without it. I keep finding new apps that are extremely useful. Thanks! Dionne Lie @DionneLie I have been a @Setapp customer for more than a year, and I fully recommend it. Dr Juan Santander-Vela @juandesant Setapp trusted reviews. G2 Badges prove that independent Setapp members have an awesome user experience and trust Setapp. Issued by G2 — the most trusted software marketplace with authentic peer reviews. Learn more 4.8/5 (28 ratings) Media about Setapp. 260+ apps for all your tasks. Free for 7 days. Get started now More about Setapp Company Home All apps How it works Pricing About Setapp Download Setapp Getting started with Setapp Uninstall Setapp Helpful Support Trust center Join as a developer For iOS developers Setapp reviews Affiliate program Blog Inside the blog Editorial process How we evaluate apps Human writing Write for us Best apps VPN for Mac YouTube downloader for Mac Screen recorder for Mac Recovery software for Mac Password manager for Mac Video editing software for Mac Note–taking app for Mac Terminal for Mac Calendar app for Mac Remote desktop for Mac Cloud backup for Mac Screenshot tool for Mac Antivirus for Mac Browser for Mac Our best content All macOS versions All iOS versions MacBook generations in order iPhone releases in order iPad generations in order AirPods generations in order How to's View clipboard history on Mac Change folder icon or color on Mac Recover deleted iPhone photos Access unrecognized external drive Access your Mac remotely Use recovery mode on Mac View and kill processes on Mac Stop Mac from sleeping Check MacBook temperature Fix frozen Mac Reset iPhone Reset iPad Our tools Apple serial number iPhone serial number Mac serial number iPad serial number AirPods serial number Apple Watch serial number Apple warranty number Mac warranty checker iPad warranty checker HEIC to JPG HEIC to PNG HEIC to PDF GPTs for Mac Updates from our team, written with love Love is coming your way, soon. This doesn’t look right, please try again. Try once more, our server fell asleep for a bit. I agree to receive emails from Setapp as per this Privacy Notice . Please select the checkbox to continue. Need help? Terms of Use Privacy Notice English English Português do Brasil Français Deutsch Español Italiano Українська © 2026 MacPaw Way Ltd., 25 Serifou, Allure Center 11, Office No. 11-12, 2nd Floor, 3046 Zakaki, Limassol, Cyprus Sweet, let’s get you started Your email Continue or sign in with Back Create a strong password Come up with a unique password for your Setapp account: Retype Your password Show 8 characters minimum. At least 1 uppercase letter. At least 1 lowercase letter. Continue Back What should we call you? Continue with new account: Retype Your name Captcha is required I want to get pro advice on Mac apps and exclusive member offers. Accept Terms of Use , Privacy Notice and Cookie Notice Create account | 2026-01-13T09:29:30 |
https://fr-fr.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0LEov6cz1ioW7wZYvRoNCYoCDjdjkEpOhWmlE0QNeDROc7WUwfwZ4g-BlF7KnMioV-t741JYgSpGwGqEsdRP0rM5Aq6g6jPSpPQMnIbNJ_Gktg0ks0bvtkQBTxCZQlzPAJ0MHuz4LYJzL7 | Facebook Facebook Adresse e-mail ou téléphone Mot de passe Informations de compte oubliées ? Créer un compte Cette fonction est temporairement bloquée Cette fonction est temporairement bloquée Il semble que vous ayez abusé de cette fonctionnalité en l’utilisant trop vite. Vous n’êtes plus autorisé à l’utiliser. Back Français (France) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Deutsch S’inscrire Se connecter Messenger Facebook Lite Vidéo Meta Pay Boutique Meta Meta Quest Ray-Ban Meta Meta AI Plus de contenu Meta AI Instagram Threads Centre d’information sur les élections Politique de confidentialité Centre de confidentialité À propos Créer une publicité Créer une Page Développeurs Emplois Cookies Choisir sa publicité Conditions générales Aide Importation des contacts et non-utilisateurs Paramètres Historique d’activité Meta © 2026 | 2026-01-13T09:29:30 |
https://meeksfamily.uk/~michael/blog/2022/May/index.html | Stuff Michael Meeks is doing Stuff Michael Meeks is doing This is my (in)activity log. You might like to visit Collabora Productivity a subsidiary of Collabora focusing on LibreOffice support and services for whom I work. Also if you have the time to read this sort of stuff you could enlighten yourself by going to Unraveling Wittgenstein's net or if you are feeling objectionable perhaps here . Failing that, there are all manner of interesting things to read on the LibreOffice Planet news feed . Older items: 2023 : ( J F M A M J ), 2022 : ( J F M A M J J A S O N D ), 2021 , 2019 , 2018 , 2017 , 2016 , 2015 , 2014 , 2013 , 2012 , 2011 , 2010 , 2009 , 2009 , 2008 , 2007 , 2006 , 2005 , 2004 , 2003 , 2002 , 2001 , 2000 , 1999 , legacy html Tue, 31 May 2022 --> 2022-05-31 Tuesday Catch up with Kendy, N. out to a party. Distracted by some performance hacking fun - made delta-generation very much faster, spent a while reading hotspot profiles. Mon, 30 May 2022 --> 2022-05-30 Monday Planning call much of the morning; catch up with Sophie, CRM call with William, Andras, Eloy. Partner call, out for a run with J. part of a TDF board call. Sun, 29 May 2022 --> 2022-05-29 Sunday All Saints, new Vicar announced; home for pizza and some slugging. Watched Meet the Parents with the babes, bed. Sat, 28 May 2022 --> 2022-05-28 Saturday Some code review; played with diamond concrete grinder trying to avoid silicosis, loss of eyesight & hearing loss concurrently with some trouble. Helped J. in the garden removing hedge stumps, with our neighbour Russell's help. Fri, 27 May 2022 --> 2022-05-27 Friday Mail chew; poked at profiles. Catch up with Noel, positive catch-up with Frank, interesting times. Thu, 26 May 2022 --> 2022-05-26 Thursday Sync with Miklos, COOL community call, Lunch. Plugged away at some profiling action - pushed some low hanging fruit - always nice to find and fix. Helped J. dig a giant root from the hedge out. Wed, 25 May 2022 --> 2022-05-25 Wednesday Took babes to school; sales call with Eloy, picked up Miriam from school; lunch with N. too. Sync with Ash & Tor on chroot & file management for fonts. Plugged away at adapting deltas to unit tests. All Saints band practice; merged deltas - lets see what testing shows. Tue, 24 May 2022 --> 2022-05-24 Tuesday Sync with Kendy; ISO 9k1/27k1 call with Hannah & Herman. Lunch. Admin; long catch-up call with Eloy. Reading LOTR to the family in the evening - fun. Worked on Deltas a bit - got another chunk of code merged with them disabled. Mon, 23 May 2022 --> 2022-05-23 Monday Took M. to a GCSE, mail chew, planning calls, M. dropped home. Lunch with N. too. Mail chew, some research, poked at build issues; turns out having the latest libstdc++ from gcc is really important for clang. Whiteboard turned out to be a hit with E. who covered it with comic drawings. Sun, 22 May 2022 --> 2022-05-22 Sunday All Saints, played, back for pork stew lunch. Lazed in the sun in the garden, under a shade-sail in J's lap - lovely. Watched Walter Mitty in the evening. Sat, 21 May 2022 --> 2022-05-21 Saturday Had a fine time at David's helping with the guttering; hopefully sealed everything up and replaced this & that nicely. Lunch, had a go at holly-tree trimming up a ladder together. Home, put up a white-board, had a chat with H. Fri, 20 May 2022 --> 2022-05-20 Friday Mail chew; catch-up with Andras, conference paper submission. Worked on deltas happily. Thu, 19 May 2022 --> 2022-05-19 Thursday Mail chew; some catch-up, 1:1 with Miklos, COOL community call, catch-up with Pedro. Plugged away at the admin backlog. White-board arrived, hopefully in-range of a web-cam somehow - perhaps drawing big pictures is the real solution. Bible Study group in the evening, good to see Thomas too. Wed, 18 May 2022 --> 2022-05-18 Wednesday Breakfast with Marc, Sales call with Eloy, packed, more sales downstairs; bit tired; Marc did a workshop, lunch. Bid 'bye to the remaining people. Set off for train station. Hacked in the plane a little left & right. Drove back. Lovely to be home with J. and family again. Tue, 17 May 2022 --> 2022-05-17 Tuesday Up early, breakfast with Marc, off to a theatre for the (very impressive) Univention Summit. Talked with attendees, and old friends and partners much of the day. Enjoyed some talks with live translation too. Dinner in the evening together, back to the hotel bar & up until very late. Mon, 16 May 2022 --> 2022-05-16 Monday Up unfeasibly early, drove to Stansted - flight to Bremen, checked in - planning call; Kebap for lunch; calls with MikeK & Kendy, Tracie. Met up with Marc, out for a pre-dinner together with a number of Univention Summit attendees. Sun, 15 May 2022 --> 2022-05-15 Sunday All Saints, chatted to all and sundry after the service. Home for Pizza, N. not feeling at all good. Julie & Isaac over, relaxed with the family. Watched with E. and J. tea, packed for tomorrow. Sat, 14 May 2022 --> 2022-05-14 Saturday Worked on slides in the morning, recorded video & sent it out. Out to Screwfix with J. bought a 230mm Mac angle grinder and some blades - interesting. Fri, 13 May 2022 --> 2022-05-13 Friday Call with a potential partner & demo. Sad news around marketing , 1:1 with Eloy, Gokay, Kendy. Out for a run with J. Worked on slides for the Univention Summit until late. Thu, 12 May 2022 --> 2022-05-12 Thursday Catch-up with Miklos, COOL community call: not the same with Pedro on vaction, catch up with Andras, mail & admin. Wed, 11 May 2022 --> 2022-05-11 Wednesday Sales call & catch-up with Eloy; worked on deltas, catch-up with Gokay. Tue, 10 May 2022 --> 2022-05-10 Tuesday More delta work - got down to 20 patches outstanding, and lots of other important bits merged eg. make czech . Thought it was working nicely until demo'ing to Kendy in our 1:1 fun. Lunch with J. Back to deltas, catch up with Simon, deltas, dinner, deltas. Mon, 09 May 2022 --> 2022-05-09 Monday Planning call much of the morning; started working on re-basing deltas, squashing pieces out & getting everything that will compile and run by itself into master with some success, down to just 40 patches. Sun, 08 May 2022 --> 2022-05-08 Sunday All Saints, played Beckie's guitar & worship - with lots of good songs - although weak ensemble since we can't hear each other well. Pizza lunch, slugged in the garden; watched Kiki's delivery service with E. picked the babes up, and to bed. Sat, 07 May 2022 --> 2022-05-07 Saturday Up late, helped H. with some electronics, and babes with some revision. Rested variously with J. Lunch. David over, sat outside under the shade sail & chatted, put up a gate catch, rested variously. Worked late on deltas with some success. Fri, 06 May 2022 --> 2022-05-06 Friday Catch up with Andras, out for a run with J. Mail patch-review & merging. Rotated my office somehow, fast laptop still struggling tearing 4k youtube even over display-port - interesting, no doubt a software issue. Thu, 05 May 2022 --> 2022-05-05 Thursday Catch up with Miklos, COOL community call, partner debugging session: some user-agent / poly-fill JS horror in the end. Lunch. Catch-up with Andras. More mail chew & admin - poked at Skia/PPC somewhat. Wed, 04 May 2022 --> 2022-05-04 Wednesday Sales meeting, catch-up with William, setup Intel/Thinkpad - hopefully it will resume after suspend. Partner call, catch up with Gokay. Tue, 03 May 2022 --> 2022-05-03 Tuesday Catch up with Kendy & Simon, caught up with mail, fixed a chunk of FIXMEs in the online / delta work. Mon, 02 May 2022 --> 2022-05-02 Monday Partner call & planning call in parallel. B&A over for lunch, quiche and home-made doughnuts. Talked for a while together. Out to look at a local bungalo. Caught up some mail & code. Chat with H. helped M. with some maths, ordered a new Lenovo laptop to replace the ~catastrophic Dell G5s Ryzen 4800H - horrible suspend/resume problems - disappears & never returns, no logging, no errors, grim, well known & un-fixed. Sun, 01 May 2022 --> 2022-05-01 Sunday All Saints in the morning, canned music, APCM meeting. Len came back for a pizza lunch; lovely to get to know him a bit better. Watched Skyfall in the evening with E. collected N. & M. from StAG. My content in this blog and associated images / data under images/ and data/ directories are (usually) created by me and (unless obviously labelled otherwise) are licensed under the public domain, and/or if that doesn't float your boat a CC0 license. I encourage linking back (of course) to help people decide for themselves, in context, in the battle for ideas, and I love fixes / improvements / corrections by private mail. In case it's not painfully obvious: the reflections reflected here are my own; mine, all mine ! and don't reflect the views of Collabora, SUSE, Novell, The Document Foundation, Spaghetti Hurlers (International), or anyone else. It's also important to realise that I'm not in on the Swedish Conspiracy . Occasionally people ask for formal photos for conferences or fun . Michael Meeks ( michael.meeks@collabora.com ) | 2026-01-13T09:29:30 |
https://uptimerobot.com/sponsorship/?ref-header | Giving Back to Community | UptimeRobot Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Go to Dashboard Register for FREE 💚🤲🎁 UptimeRobot gives back : Get a sponsored subscription for your non-profit . Our mission is to support charitable organizations and other non-profits, in order for them to focus on what's really important. Learn more Apply for sponsored plan We happilly support 50+ charitable and non-profit organizations. 💚 Why we help What you will get How to apply Non-profits we help Apply now Why do we help ? UptimeRobot started as a FREE monitoring service and grew thanks to the support of our dedicated user community. Now, as a way of paying it forward, we want to give back by offering sponsored monitoring to meaningful projects. This sponsorship includes full access to our features and support from our team. What you'll get with sponsored monitoring . div; delay: 100; hidden: false, offset-top: 250"> Advanced monitoring Monitor up to 100 websites, servers, SSL certificates, and others as described in our paid SOLO and TEAM plans . Custom status pages Share your uptime and updates live on your own status page . Modern mobile app Get push notifications for alerts via UptimeRobot mobile app for iOS and Android. Chat support We can help you with setup or any problem you may face. How to get a sponsorship ? div; delay: 100; hidden: false, offset-top: 250"> Introduce yourself Please provide details about your nonprofit including an overview of your activities, a link to your website, and a bit of background information. Apply We'll evaluate your request If approved, we’ll promptly provide you with the next steps. Display our logo We kindly ask you to consider placing our logo and link to uptimerobot.com on your website. If it's not an option, let us know, we'll figure it out! Download logos div; delay: 100; hidden: false, offset-top: 250"> Why non-profits love UptimeRobot . We provide our customers with a good place to live. To ensure the best service, UptimeRobot is monitoring several services for us and notifies us would an issue arise: the external websites, applications, our internet connections and datacenter services. In this way we can start diagnosing and resolving issues before they are reported by employees or customers. Sander Goudswaard, Security Officer bevelandwonen.nl As a provider of real-time emergency notifications, it’s imperative that our services remain responsive 24/7. UptimeRobot allows us to be alerted the second there’s an issue within our critical infrastructure allowing us to take immediate appropriate action. In an industry where every second counts, UptimeRobot allows us to keep an eye on our critical infrastructure and be alerted immediately if an issue rises. Johnathan Martin, Operations Director lait911.com We consider in fact that monitoring services is a fundamental act of an organization that wants to safely provide a service to and user. Our non profit feels empowered by uptimerobot and can focus on support whistleblowers worldwide. Giovanni Pellerano, Project Lead globaleaks.org Museum of London UptimeRobot has been indispensable in helping the museum react quickly to unexpected website outage. The platform gives us the exact moment and length of the outage, allowing us to identify causes and resolve issues before users experience any inconvenience. Kim Van Russelt, Digital Editor museumoflondon.org.uk OpenBLD.net DNS UptimeRobot offers a superb solution with multi-port, protocol, and, of course, ping monitoring capabilities. I stay constantly updated about my services' uptime status using the UptimeRobot Telegram bot and mobile app. Additionally, the real-time status pages are highly valuable tools for identifying and diagnosing high-availability service issues. Yevgeniy Goncharov, Founder lab.sys-adm.in Orient Foundation for Arts and Culture Our charity has utilized UptimeRobot for over six years. We offer live online services to cultural charities worldwide, and having immediate awareness of any issues with our sites is paramount. Throughout these past six years, UptimeRobot has consistently provided us with a highly reliable service. Our technical team and service staff have received instant alerts during this period. In short, we rely on and are extremely satisfied with UptimeRobot. Graham Coleman, Chief Executive orient.org OpenAlt, a non-profit, focuses on an annual conference for open source, government, and society. With UptimeRobot, run by volunteers, we ensure no service disruptions go unnoticed. Varied alerts and monitors pinpoint issues while adjusted settings offer peace of mind for non-critical services. Michal Stanke, Chairman of the board openalt.org We have been using UptimeRobot services for a while now, and we love them. With the upgrade, we can also monitor our services more efficiently. All around, the service that UptimeRobot is providing is the best, and we really appreciate it! Rafal Hacus, Armbian Team armbian.com As a charity running large-scale, online, match-funding campaigns, getting immediate alerts to any issues with Salesforce and AWS availability is vitally important. Uptime Robot provides us with a service that gives us timely alerts and enough information to quickly rectify problems. The fact that it integrates with Slack is an added bonus. Dominique Standring, Chief Operating Officer biggive.org We have been using UptimeRobot services for a while now, and we love them. With the upgrade, we can also monitor our services more efficiently. All around, the service that UptimeRobot is providing is the best, and we really appreciate it! Kay Hermanns, Chief Information Officer amnesty.de Join other meaningful projects . We are happy to support all non-profit organizations with sponsored monitoring from UptimeRobot. Apply for your sponsorship today! Please fill in the form and we’ll get back to you. Terms and Conditions . div; delay: 100; hidden: false, offset-top: 250"> Monitoring for helpful projects We offer sponsored support to nonprofit organizations and their associated projects. Startups with meaningful missions can also submit requests, but we cannot guarantee sponsorship. Choose the SOLO or TEAM plan You can choose from our SOLO or TEAM paid plans with up to 100 monitors and 1-minute monitoring intervals, including all the paid features. Get 1-year sponsorship The sponsorship is offered for a year, but you can resubmit your request again after this period. Downtime happens. Get notified! Join more than 2,700,000+ happy users! UptimeRobot is one of the most popular website monitoring services in the world. Monitoring . Website monitoring SSL monitoring Domain monitoring Ping monitoring Port monitoring TCP monitoring Cron job monitoring Keyword monitoring Location-specific monitoring Response time monitoring Incident Management DNS monitoring Company . Pricing Blog Affiliate program Referral program Non profit & charities 🤲 Terms / Privacy Contact us We are hiring! Resources . Integrations API FAQs Help center Locations & IPs Comparisons Case studies Knowledge hub Roadmap Subnet calculator MX lookup Uptime calculator CrontabRobot Website change detection Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Register for FREE 🍪 This website use cookies. Learn more Decline all | Allow essential | Accept all | 2026-01-13T09:29:30 |
https://uptimerobot.com/roadmap/?ref-header | Roadmap | UptimeRobot Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Go to Dashboard Register for FREE UptimeRobot Roadmap . Discover what we're currently working on and what has been released. Subscribe to receive a monthly email highlighting our latest features. You've been subscribed successfully! 🗳️ Planned Multilocation improvements Enhanced multilocation feature with more accurate uptime insights and smarter per-region monitoring. 🤖️ In Progress Mobile app update Stay on top of your uptime wherever you go with a refreshed design and improved performance in our upcoming app release. 🚀 Released Monitor grouping Easily organize multiple monitors into logical groups for clearer oversight. View, manage, and troubleshoot related monitors all in one convenient place. Ability to choose SSL window Set your own schedule for SSL checks. Gain more control over how and when certificates are verified. DNS monitoring Keep an eye on critical DNS records. Get notified instantly if your DNS values change unexpectedly. Terraform provider Manage your monitors as code. Automate setup and updates using our official Terraform integration. Multi-location monitoring Gain local perspectives on your uptime. Track performance from multiple regions. Slow response time notifications Get alerted when response times start to deteriorate. Identify and resolve performance bottlenecks before they escalate into major incidents. New monitoring core More resilient monitoring with our revamped engine, built for maximum reliability. New public API Integrate UptimeRobot seamlessly into your workflows. Advanced incident management Streamline how you track, prioritize, and resolve outages. Stay organized and keep your team aligned. Advanced tag management Easily label and categorize monitors for quicker searches and better organization. No matching results found. Want to see another feature? Add your ideas or rate others to help improve the app! Suggest a new idea Don’t be the last one to notice that your website is down . Try UpTimeRobot - the world’s leading website monitoring service! Start monitoring for free Downtime happens. Get notified! Join more than 2,700,000+ happy users! UptimeRobot is one of the most popular website monitoring services in the world. Monitoring . Website monitoring SSL monitoring Domain monitoring Ping monitoring Port monitoring TCP monitoring Cron job monitoring Keyword monitoring Location-specific monitoring Response time monitoring Incident Management DNS monitoring Company . Pricing Blog Affiliate program Referral program Non profit & charities 🤲 Terms / Privacy Contact us We are hiring! Resources . Integrations API FAQs Help center Locations & IPs Comparisons Case studies Knowledge hub Roadmap Subnet calculator MX lookup Uptime calculator CrontabRobot Website change detection Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Register for FREE 🍪 This website use cookies. Learn more Decline all | Allow essential | Accept all | 2026-01-13T09:29:30 |
https://www.linkedin.com/login?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fposts%2Fbarclays-bank_news-barclays-is-collaborating-with-expectai-activity-7407466483812941824-cEgN&fromSignIn=true&trk=public_post_nav-header-signin | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:29:30 |
https://video.fosdem.org/2020/K.4.401/?C=N&O=D | FOSDEM - video recordings FOSDEM video recordings These talks have been recorded at FOSDEM . Special thanks to AS35701 , Belnet , cyberbits.eu , dotsrc.org , FAU , LibreLabUCM , Nikhef , Onet and OSUOSL for the bandwidth. Please contact video@fosdem.org with any questions. /2020/K.4.401/ File Name ↓ File Size ↓ Date ↓ Parent directory/ - - coreboot_amd.mp4 156.5 MiB 2020-Feb-02 18:17 coreboot_amd.webm 74.9 MiB 2020-Feb-02 18:17 fbdev.mp4 361.7 MiB 2020-Feb-01 17:01 fbdev.webm 258.3 MiB 2020-Feb-01 17:01 firmware_test.mp4 136.7 MiB 2020-Feb-02 13:53 firmware_test.webm 67.4 MiB 2020-Feb-02 13:53 fpga_hw_dbg.mp4 212.0 MiB 2020-Feb-07 14:00 fpga_hw_dbg.webm 126.3 MiB 2020-Feb-07 14:00 gpu_patterns.mp4 390.8 MiB 2020-Feb-01 18:48 gpu_patterns.webm 213.4 MiB 2020-Feb-01 18:48 kms_planes.mp4 208.5 MiB 2020-Feb-01 12:20 kms_planes.webm 100.7 MiB 2020-Feb-01 12:20 libratbag.mp4 145.0 MiB 2020-Feb-02 08:34 libratbag.webm 70.3 MiB 2020-Feb-02 08:34 mesa3d_website.mp4 219.8 MiB 2020-Feb-01 13:01 mesa3d_website.webm 100.9 MiB 2020-Feb-01 13:01 nouveau.mp4 228.4 MiB 2020-Feb-01 14:58 nouveau.webm 109.6 MiB 2020-Feb-01 14:58 olimex_oshw.mp4 404.8 MiB 2020-Feb-04 16:13 olimex_oshw.webm 203.6 MiB 2020-Feb-04 16:12 openxr.mp4 206.1 MiB 2020-Feb-01 16:10 openxr.webm 141.8 MiB 2020-Feb-01 16:10 oshw_ci.mp4 172.4 MiB 2020-Feb-04 13:54 oshw_ci.webm 161.3 MiB 2020-Feb-04 13:54 oshw_custom.mp4 393.7 MiB 2020-Feb-04 16:28 oshw_custom.webm 245.7 MiB 2020-Feb-04 16:28 paduak_toolchain.mp4 193.7 MiB 2020-Feb-02 18:04 paduak_toolchain.webm 98.8 MiB 2020-Feb-02 18:03 replicant.mp4 249.4 MiB 2020-May-25 13:53 replicant.webm 121.0 MiB 2020-May-25 13:53 riscv_fpga.mp4 309.2 MiB 2020-Feb-04 14:06 riscv_fpga.webm 196.1 MiB 2020-Feb-04 14:06 rpi4_vulkan.mp4 166.6 MiB 2020-Feb-02 08:35 rpi4_vulkan.webm 82.0 MiB 2020-Feb-02 08:35 startup_gen.mp4 125.5 MiB 2020-Feb-02 15:57 startup_gen.webm 58.6 MiB 2020-Feb-02 15:57 ttm.mp4 284.9 MiB 2020-Feb-01 18:32 ttm.webm 125.4 MiB 2020-Feb-01 18:20 videobox.mp4 395.0 MiB 2020-Feb-03 13:49 videobox.webm 269.1 MiB 2020-Feb-03 13:49 zink.mp4 126.3 MiB 2020-Feb-01 12:03 zink.webm 64.0 MiB 2020-Feb-01 12:03 This work is licensed under the Creative Commons Attribution 2.0 Belgium Licence. To view a copy of this licence, visit http://creativecommons.org/licenses/by/2.0/be/deed.en or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. | 2026-01-13T09:29:30 |
https://uptimerobot.com/affiliate/?ref-header | Affiliate & referral program | UptimeRobot Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Go to Dashboard Register for FREE UptimeRobot Affiliate Program . Work with us. Get 20% LIFETIME commission by promoting the world's leading uptime monitoring service. Or grab an exclusive merch. Start earning now or Refer to a friend Refer to a friend We are trusted by big companies Why promoting UptimeRobot is a no-brainer . Lifetime earnings . You will get a 20% commission from each monthly/annual payment made by a user who creates an account via your affiliate link. Each referred user will be bringing you the commissions as long as they keep their subscription active. A top-grade product . UptimeRobot is the world's leading uptime monitoring service with a user base of over 2,700,000+ happy users. The popularity of the service can be attributed to its simplicity, affordability and a great care for customer satisfaction. No approval process . There is no approval for affiliate registrations so you can start promoting right away. All you need is a free UptimeRobot account. Just use one of the links in the Affiliate section of the UptimeRobot dashboard and you're good to go! What UptimeRobot offers . Website monitoring Learn more Cron job monitoring Learn more Port monitoring Learn more Keyword monitoring Learn more Ping monitoring Learn more SSL monitoring Learn more Start earning now How it works . TLDR: Let's say you refer a customer that subscribes to our $28/month plan. You'll be making $5.60/month (20% from the plan) for as long as the referred user keeps his subscription. 1. Create an account . Just create the free UptimeRobot account. You can start earning instantly by enabling the affiliate program in your dashboard. Create FREE account 2. Share your affiliate link . You will find your affiliate code and a referral link in the Dashboard. You can link to any UptimeRobot's page. Just use the proper referral code. 3. Get paid . When you reach the $100 threshold, you can request a payout. Currently, we make payouts via Paypal only. Easy as that! Start earning now Get exclusive merch . Get exclusive merch you can't buy anywhere. Refer at least 5 paying users and get a limited, original UptimeRobot's merch! Refer a friend Why people love UptimeRobot? It's the most simple and easy monitoring app I know and it's made my daily life much easier . @levelsio, maker of NomadList.com, RemoteOK.io and others I use UptimeRobot to get push notifications whenever my website goes DOWN . It's really easy and quick to set up and requires no extra changes to your website . @marckohlbrugge, maker of BetaList.com, StartUp.jobs and others We strive for minimal downtime, but if something goes wrong UptimeRobot makes sure that we know about it quickly. We switched to using UptimeRobot years ago as they offered the same services we were getting from a different provider but at a fraction of the cost . I've been using UptimeRobot for years as a cost-effective way to quickly alert me when my sites were down - and when they were back up . ~ Steve "ardalis" Smith, Software Architect Frequently Asked Questions What is the commission rate? You will get a 20% LIFETIME (recurring) commission from each full price payment made by a referred user who registers and then subscribes through the link with your unique affiliate ID. In case of a discounted price, the commission is reduced by the percentage amount of the discount. How about cookies expiration? Cookies are valid for 30 days , so the referred user needs to register the UptimeRobot account within 30 days after clicking on the link with your affiliate ID. If the user subscribes to one of the paid plans later, you will get the commission either way. Keep in mind that if the user registers by using a link with someone else's affiliate ID or without it and subscribes later by using your affiliate ID link, you will not earn the commission. When do I get paid? The commissions are paid once a month via PayPal. You can request the payout upon reaching a minimum threshold of $100. Keep in mind that we reserve the right to postpone the payout until at least two different users are referred to avoid self-referrals. Are there any restricted affiliate activities? As we want to keep our Affiliate Program fair, there are some restricted activities: Coupon sites. PPC advertising with a direct link leading to any UptimeRobot website (including all the tools and landing pages) Using any UptimeRobot brand, logo or name of the tools or their misspelled versions in PPC advertising, in domains, subdomains, or in profiles on social media Using misleading or incorrect information (non-existent discounts, etc.) Using discount coupons that are not assigned to you The so-called 'self-referrals' (when you create another account while referring yourself) The restricted activities will lead to the disapproval of your affiliate commissions or the termination of the partnership. For more information, check the Terms & Conditions . Start earning now! Register for FREE Downtime happens. Get notified! Join more than 2,700,000+ happy users! UptimeRobot is one of the most popular website monitoring services in the world. Monitoring . Website monitoring SSL monitoring Domain monitoring Ping monitoring Port monitoring TCP monitoring Cron job monitoring Keyword monitoring Location-specific monitoring Response time monitoring Incident Management DNS monitoring Company . Pricing Blog Affiliate program Referral program Non profit & charities 🤲 Terms / Privacy Contact us We are hiring! Resources . Integrations API FAQs Help center Locations & IPs Comparisons Case studies Knowledge hub Roadmap Subnet calculator MX lookup Uptime calculator CrontabRobot Website change detection Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Register for FREE 🍪 This website use cookies. Learn more Decline all | Allow essential | Accept all | 2026-01-13T09:29:30 |
https://video.fosdem.org/2020/UB5.230/?C=M&O=A | FOSDEM - video recordings FOSDEM video recordings These talks have been recorded at FOSDEM . Special thanks to AS35701 , Belnet , cyberbits.eu , dotsrc.org , FAU , LibreLabUCM , Nikhef , Onet and OSUOSL for the bandwidth. Please contact video@fosdem.org with any questions. /2020/UB5.230/ File Name ↓ File Size ↓ Date ↓ Parent directory/ - - ambassadornetworks.mp4 173.5 MiB 2020-Feb-16 22:12 ambassadornetworks.webm 95.0 MiB 2020-Feb-16 22:11 burnout.mp4 144.7 MiB 2020-Feb-02 23:19 burnout.webm 73.4 MiB 2020-Feb-02 23:19 capitalismethicaloss.mp4 130.9 MiB 2020-Feb-14 17:29 capitalismethicaloss.webm 122.4 MiB 2020-Feb-14 17:29 cognitivebias.mp4 158.5 MiB 2020-Feb-02 13:50 cognitivebias.webm 78.9 MiB 2020-Feb-02 13:50 corpcommunitythrive.mp4 129.4 MiB 2020-Mar-03 19:43 corpcommunitythrive.webm 81.0 MiB 2020-Mar-03 19:43 corposscommunity.mp4 157.8 MiB 2020-Mar-03 19:21 corposscommunity.webm 98.0 MiB 2020-Mar-03 19:21 corppolicyteamoutreach.mp4 153.1 MiB 2020-Feb-19 17:42 corppolicyteamoutreach.webm 72.2 MiB 2020-Feb-19 17:42 distributedteams.mp4 169.5 MiB 2020-Feb-14 16:13 distributedteams.webm 77.2 MiB 2020-Feb-14 16:13 edufoss.mp4 183.2 MiB 2020-Mar-07 18:53 edufoss.webm 97.1 MiB 2020-Mar-07 18:53 enterpriseoss.mp4 213.2 MiB 2020-Mar-07 15:55 enterpriseoss.webm 128.2 MiB 2020-Mar-07 15:55 ethicsbackinoss.mp4 117.3 MiB 2020-Mar-02 22:33 ethicsbackinoss.webm 114.8 MiB 2020-Mar-02 22:33 ethicsoss.mp4 138.3 MiB 2020-Feb-15 09:42 ethicsoss.webm 81.8 MiB 2020-Feb-15 09:42 innersourceupstream.mp4 195.8 MiB 2020-Mar-05 00:52 innersourceupstream.webm 113.3 MiB 2020-Mar-05 00:52 leadeross.mp4 162.9 MiB 2020-Mar-04 23:15 leadeross.webm 92.9 MiB 2020-Mar-04 23:15 nextgencontributors.mp4 166.3 MiB 2020-Mar-03 20:14 nextgencontributors.webm 85.8 MiB 2020-Mar-03 20:14 osslessons.mp4 116.2 MiB 2020-Mar-03 22:10 osslessons.webm 59.5 MiB 2020-Mar-03 22:10 This work is licensed under the Creative Commons Attribution 2.0 Belgium Licence. To view a copy of this licence, visit http://creativecommons.org/licenses/by/2.0/be/deed.en or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. | 2026-01-13T09:29:30 |
https://uptimerobot.com/privacy/ | Privacy Policy | UptimeRobot Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Go to Dashboard Register for FREE Privacy policy . UptimeRobot (a service by Uptime Robot s. r. o.) operates several websites including uptimerobot.com , uptimerobot.com/api and blog.uptimerobot.com . It is UptimeRobot's policy to respect your privacy regarding any information we may collect while operating our websites. What This Policy Covers This Privacy Policy applies to information that we collect about you when you use: Our website uptimerobot.com; Our mobile applications (including the UptimeRobot mobile app for Android and iOS); For users who qualify as data controllers, or who require specific data processing terms, a separate GDPR-compliant Data Processing Agreement (“DPA”) is available upon request and forms part of your contractual relationship with UptimeRobot. Throughout this Privacy Policy, we’ll refer to our website, mobile applications and other products and services collectively as “Services.” Below we explain how we collect, use, and share information about you, along with the choices that you have with respect to that information. Information We Collect We only collect information about you if we have a reason to do so–for example, to provide our Services, to communicate with you, or to make our Services better. We collect information in two ways: if and when you provide information to us and automatically through operating our Services. Let’s go over the information that we collect. Information You Provide to Us It’s probably no surprise that we collect information that you provide to us. The amount and type of information depends on the context and how we use the information. Here are some examples: Basic Account Information: We ask for basic information from you in order to set up your account. For example, we require individuals who sign up for an uptimerobot.com account to provide name-surname, email address , password and that’s it. Transaction and Billing Information: If you buy something from us–a subscription to a uptimerobot.com plan, SMS messages, etc., for example–you will provide additional personal and payment information that is required to process the transaction and your payment, such as your name, credit card information, and contact information. Credentials: Depending on the Services you use, you may provide us with credentials for your website (like SSH, FTP, and SFTP username and password). Communications With Us (Hi There!): You may also provide us information when you respond to surveys or communicate with our team about a support question. Information We Collect Automatically We also collect some information automatically: Log Information: Like most online service providers, we collect information that web browsers, mobile devices, and servers typically make available, such as the browser type, IP address, unique device identifiers, language preference, referring site, the date and time of access, operating system, and mobile network information. We collect log information when you use our Services–for example, when you create or make changes to your account. Usage Information: We collect information about your usage of our Services. For example, we collect information about the pages you visit or site parts that you check the most. We use this information to, for example, provide our Services to you, as well as get insights on how people use our Services, so we can make our Services better. Location Information: We may determine the approximate location of your device from your IP address. We collect and use this information to, for example, calculate how many people visit our Services from certain geographic regions. Information from Cookies & Other Technologies: A cookie is a string of information that a website stores on a visitor’s computer, and that the visitor’s browser provides to the website each time the visitor returns. Pixel tags (also called web beacons) are small blocks of code placed on websites and emails. UptimeRobot uses cookies and other technologies like pixel tags to help us identify and track visitors, usage, and access preferences for our Services, as well as track and understand email campaign effectiveness. And, we will only keep your personal information for as long as it is necessary for the purposes set out in this privacy policy, unless a longer retention period is required or permitted by law (such as tax, accounting or other legal requirements). How And Why We Use Information Purposes for Using Information We use information about you as mentioned above and for the purposes listed below: To provide our Services–for example, to set up and maintain your account or charge you for any of our paid Services; To further develop and improve our Services–for example by adding new features that we think our users will enjoy or will help them to create and manage their monitors more efficiently; To monitor and analyze trends and better understand how users interact with our Services, which helps us improve our Services and make them easier to use; To measure, gauge, and improve the effectiveness of our advertising, and better understand user retention and attrition–for example, we may analyze how many individuals purchased a plan after receiving a marketing message or the features used by those who continue to use our Services after a certain length of time; To monitor and prevent any problems with our Services, protect the security of our Services, detect and prevent fraudulent transactions and other illegal activities, fight spam, and protect the rights and property of UptimeRobot and others, which may result in us declining a transaction or the use of our Services; To communicate with you, for example through an email, about offers and promotions offered by UptimeRobot and others we think will be of interest to you, solicit your feedback, or keep you up to date on UptimeRobot and our products; and To personalize your experience using our Services, provide content recommendations, target our marketing messages to groups of our users (for example, those who have a particular plan with us or have been our user for a certain length of time), and serve relevant advertisements. Legal Bases for Collecting and Using Information A note here for those in the European Union about our legal grounds for processing information about you under EU data protection laws, which is that our use of your information is based on the grounds that: (1) The use is necessary in order to fulfill our commitments to you under our Terms of Service or other agreements with you or is necessary to administer your account–for example, in order to enable access to our website on your device or charge you for a paid plan; or (2) The use is necessary for compliance with a legal obligation; or (3) The use is necessary in order to protect your vital interests or those of another person; or (4) We have a legitimate interest in using your information–for example, to provide and update our Services, to improve our Services so that we can offer you an even better user experience, to safeguard our Services, to communicate with you, to measure, gauge, and improve the effectiveness of our advertising, and better understand user retention and attrition, to monitor and prevent any problems with our Services, and to personalize your experience; or (5) You have given us your consent–for example before we place certain cookies on your device and access and analyze them later on. Sharing Information How We Share Information We do not sell our users’ private personal information. We share information about you in the limited circumstances spelled out below and with appropriate safeguards on your privacy: Subsidiaries, Employees, and Independent Contractors: We may disclose information about you to our subsidiaries, our employees, and individuals who are our independent contractors that need to know the information in order to help us provide our Services or to process the information on our behalf. We require our subsidiaries, employees, and independent contractors to follow this Privacy Policy for personal information that we share with them. Third Party Vendors: We may share information about you with third party vendors who need to know information about you in order to provide their services to us, or to provide their services to you. This group includes vendors that help us provide our Services to you (like payment providers that process your credit and debit card information, fraud prevention services that allow us to analyze fraudulent payment transactions, SMS and email delivery services that help us stay in touch with you), those that assist us with our marketing efforts (e.g. by providing tools for identifying a specific marketing target group or improving our marketing campaigns), those that help us understand and enhance our Services (like analytics providers) who may need information about you in order to, for example, provide technical or other support services to you. We require vendors to agree to privacy commitments in order to share information with them. These vendors are listed in the "List of data sub-processors" section below. Legal Requests: We may disclose information about you in response to a subpoena, court order, or other governmental request. To Protect Rights, Property, and Others: We may disclose information about you when we believe in good faith that disclosure is reasonably necessary to protect the property or rights of UptimeRobot, third parties, or the public at large. For example, if we have a good faith belief that there is an imminent danger of death or serious physical injury, we may disclose information related to the emergency without delay. Business Transfers: In connection with any merger, sale of company assets, or acquisition of all or a portion of our business by another company, or in the unlikely event that UptimeRobot goes out of business or enters bankruptcy, user information would likely be one of the assets that is transferred or acquired by a third party. If any of these events were to happen, this Privacy Policy would continue to apply to your information and the party receiving your information may continue to use your information, but only consistent with this Privacy Policy. With Your Consent: We may share and disclose information with your consent or at your direction. For example, we may share your information with third parties with which you authorize us to do so, such as the social media services that you connect to our site. Aggregated or De-Identified Information: We may share information that has been aggregated or reasonably de-identified, so that the information could not reasonably be used to identify you. For instance, we may publish aggregate statistics about the use of our Services. Security While no online service is 100% secure, we work very hard to protect information about you against unauthorized access, use, alteration, or destruction, and take reasonable measures to do so, such as monitoring our Services for potential vulnerabilities and attacks. To enhance the security of your account, we encourage you to enable our advanced security settings, like Two Step Authentication. Choices You have several choices available when it comes to information about you: Limit the Information that You Provide: If you have an account with us, you can choose not to provide the optional account information, profile information, and transaction and billing information. Please keep in mind that if you do not provide this information, certain features of our Services–for example, paid ones, may not be accessible. Opt-Out of Electronic Communications: You may opt out of receiving promotional messages from us. Just follow the instructions in those messages. If you opt out of promotional messages, we may still send you other messages, like those about your account, monitoring alerts and legal notices. Set Your Browser to Reject Cookies: At this time, UptimeRobot does not respond to “do not track” signals across all of our Services. However, you can usually choose to set your browser to remove or reject browser cookies before using UptimeRobot’s websites, with the drawback that certain features of UptimeRobot’s websites may not function properly without the aid of cookies. Close Your Account: While we’d be very sad to see you go, if you no longer want to use our Services :( :( :( :(, you can close your uptimerobot.com account. Please keep in mind that we may continue to retain your information after closing your account, as described in Information We Collect above–for example, when that information is reasonably needed to comply with (or demonstrate our compliance with) legal obligations such as law enforcement requests, or reasonably needed for our legitimate business interests. Your Rights If you are located in certain countries, including those that fall under the scope of the European General Data Protection Regulation (AKA the “GDPR”), data protection laws give you rights with respect to your personal data, subject to any exemptions provided by the law, including the rights to: Request access to your personal data; Request correction or deletion of your personal data; Object to our use and processing of your personal data; Request that we limit our use and processing of your personal data; and Request portability of your personal data. You can usually access, correct, or delete your personal data using your account settings and tools that we offer, but if you aren’t able to do that, or you would like to contact us about one of the other rights, scroll down to How to Reach Us to, well, find out how to reach us. EU individuals also have the right to make a complaint to a government supervisory authority. How to Reach Us If you have a question about this Privacy Policy, or you would like to contact us about any of the rights mentioned in the Your Rights section above, please contact us directly via support@uptimerobot.com . Other Things You Should Know (Keep Reading!) Transferring Information Because UptimeRobot’s Services are offered worldwide, the information about you that we process when you use the Services in the EU may be used, stored, and/or accessed by individuals operating outside the European Economic Area (EEA) who work for us, other members of our group of companies, or third party data processors. This is required for the purposes listed in the How and Why We Use Information section above. When providing information about you to entities outside the EEA, we will take appropriate measures to ensure that the recipient protects your personal information adequately in accordance with this Privacy Policy as required by applicable law. Ads and Analytics Services Provided by Others Other parties may also provide analytics services via our Services. These analytics providers may set tracking technologies (like cookies) to collect information about your use of our Services and across other websites and online services. These technologies allow these third parties to recognize your device to compile information about you or others who use your device. This information allows us and other companies to, among other things, analyze and track usage. Please note this Privacy Policy only covers the collection of information by UptimeRobot and does not cover the collection of information by any third party advertisers or analytics providers. List of Sub-processors UptimeRobot uses the following products/services (which are all GDPR compliant): Limestone Networks: for sending monitoring requests and storing data. Amazon Web Services: for sending monitoring requests and storing data. Digital Ocean: for sending monitoring requests and storing data. Plivo: for sending SMS and voice notifications. Stripe: for credit card payments. 2Checkout: for credit card payments. PayPal: for PayPal and credit card payments. Google Tag Manager: for serving 3rd party scripts. Google Analytics (Universal Analytics and/or Google Analytics 4): for analyzing the browsing behavior of our users and visitors. Google BigQuery: for business analysis and analyzing the browsing behavior of our users and visitors. Google Fonts: for loading a custom fonts. Rollbar: for loggin errors and bugs. User.com: for CRM service, behavioral messages and updates about product. Intercom.com: for CRM service, customer support, online chat, behavioral messages and updates about product. Sendgrid.com: for sending emails, e.g. account related, occasional deal offers, etc. Google Ads: for auto-pausing Google ads during downtimes and for ads targeting. Facebook Ads: for auto-pausing Facebook ads during downtimes. Miscrosoft Clarity: To capture how you use and interact with our website through behavioral metrics, heatmaps, and session replay to improve and market our products/services. Website usage data is captured using first and third-party cookies and other tracking technologies to determine the popularity of products/services and online activity. Additionally, we use this information for app and web site optimization and advertising. For more information about how Microsoft collects and uses your data, visit the Microsoft Privacy Statement . “Subscribe to updates” feature on Status pages Status page is a voluntary option to showcase your uptime to your customers. With the PRO plan you can enable the subscription feature allowing your customers to subscribe to the announcements and updates you’ll share on your status page. These emails are sent from our servers. Such a customer will subscribe using his email address. This customer needs to confirm his subscription through an email he’ll receive to his inbox. His email address is stored in our database and the owner of the status page doesn’t have access to it and can’t view it anywhere. The customer can unsubscribe through a link available in every status update email he’ll receive and through an option available on the status page all the time. This action needs to be confirmed through an email too. The Status page owner or UptimeRobot has the right to remove users from this updates list anytime without informing the subscribed user. If the Status page is removed, all related data, subscribed emails included, will be removed too. Privacy Policy Changes Although most changes are likely to be minor, UptimeRobot may change its Privacy Policy from time to time, and in UptimeRobot's sole discretion. UptimeRobot encourages visitors to frequently check this page for any changes to its Privacy Policy. When making material changes to this Privacy Policy, we will provide advance notice to these material changes taking effect. Notification will be provided via website banner/notification, platform pop-up upon login, and direct email for active paying users. Non-material changes will be documented in the change log at the end of this Privacy Policy. Change log: January 8, 2026: Added Intercom to the list of sub-processors. September 23, 2025: Added Data Processing Agreement and updated Privacy Policy Changes. August 15, 2023: Updated list of sub-processors. July 27, 2023: Updated list of sub-processors. June 6, 2022: Updated list of sub-processors. April 26, 2021: Added Status pages and status updates sent from Status pages. April 23, 2021: Added Rollbar and Google Fonts to the list of sub-processors. July 15, 2019: Added Google Ads and Facebook Ads to the list of sub-processors. May 21, 2018: Updated for GDPR compliance. June 12, 2017: Removed Paylane from the list of payment processors. July 1, 2016: Updated the company name to reflect the change. May 20, 2014: Updated various typos. Nov 14, 2014: Added "payment processors used". This "Privacy Policy" is based on the "Creative Commons" licensed policy by WordPress (the awesome guys that created WordPress). Downtime happens. Get notified! Join more than 2,700,000+ happy users! UptimeRobot is one of the most popular website monitoring services in the world. Monitoring . Website monitoring SSL monitoring Domain monitoring Ping monitoring Port monitoring TCP monitoring Cron job monitoring Keyword monitoring Location-specific monitoring Response time monitoring Incident Management DNS monitoring Company . Pricing Blog Affiliate program Referral program Non profit & charities 🤲 Terms / Privacy Contact us We are hiring! Resources . Integrations API FAQs Help center Locations & IPs Comparisons Case studies Knowledge hub Roadmap Subnet calculator MX lookup Uptime calculator CrontabRobot Website change detection Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Register for FREE 🍪 This website use cookies. Learn more Decline all | Allow essential | Accept all | 2026-01-13T09:29:30 |
https://www.sparkcapital.com/contact | Contact ABOUT Team Companies Offices San Francisco 332 Pine Street, Floor 7 San Francisco, CA 94104 contactus@sparkcapital.com 617-830-2000 New York City 165 Mercer Street, Floor 3 New York City, NY 10012 Boston 200 Clarendon Street, Floor 59 Boston, MA 02116 © Spark Capital 2024 Contact Us Terms & Policies | 2026-01-13T09:29:30 |
https://th-th.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fshare_channel%2F%3Ftype%3Dreshare%26amp%253Blink%3Dhttps%253A%252F%252Fdev.to%252Fsouviktests%252Fidea-to-mvp-is-it-even-a-real-problem-give-your-thoughts-5c11%26amp%253Bapp_id%3D966242223397117%26amp%253Bsource_surface%3Dexternal_reshare%26amp%253Bdisplay%26amp%253Bhashtag | Facebook Facebook อีเมลหรือโทรศัพท์ รหัสผ่าน ลืมบัญชีใช่หรือไม่ สร้างบัญชีใหม่ คุณถูกบล็อกชั่วคราว คุณถูกบล็อกชั่วคราว ดูเหมือนว่าคุณจะใช้คุณสมบัตินี้ในทางที่ผิดโดยการใช้เร็วเกินไป คุณถูกบล็อกจากการใช้โดยชั่วคราว Back ภาษาไทย 한국어 English (US) Tiếng Việt Bahasa Indonesia Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch สมัคร เข้าสู่ระบบ Messenger Facebook Lite วิดีโอ Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI เนื้อหาเพิ่มเติมจาก Meta AI Instagram Threads ศูนย์ข้อมูลการลงคะแนนเสียง นโยบายความเป็นส่วนตัว ศูนย์ความเป็นส่วนตัว เกี่ยวกับ สร้างโฆษณา สร้างเพจ ผู้พัฒนา ร่วมงานกับ Facebook คุกกี้ ตัวเลือกโฆษณา เงื่อนไข ความช่วยเหลือ การอัพโหลดผู้ติดต่อและผู้ที่ไม่ได้ใช้บริการ การตั้งค่า บันทึกกิจกรรม Meta © 2026 | 2026-01-13T09:29:30 |
https://www.sparkcapital.com/team-members/clay-fisher | Clay Fisher ABOUT Team Companies Clay Fisher General Partner, Growth As an investor on Spark’s growth team, Clay supports founders building across a range of technology sectors, including enterprise software, infrastructure , and internet. Clay embraces his appreciation for the technical details by digging into the nuts and bolts of a product so he can connect with an entrepreneur’s thinking. Before working in venture, Clay studied economics at the University of Chicago and spent time at McKinsey & Company. He later joined Allen & Company as a strategic advisor to enterprise software, consumer technology, and media businesses during mergers and acquisitions, capital raises, and principal investments. While there, he advised both startups and companies like Adobe, Slack, Facebook, Pinterest, Sony, and PagerDuty, which developed his passion for guiding teams during the high-stakes moments that come with making company-defining decisions . In all his investments, Clay looks to market structure, not market size, to inform his decision making and to help founders connect product and go-to-market strategy with broader competitive forces. “I love helping founders hone in on a product or business model that will enable their company to go up against the larger players and win,” he says. Outside of Spark, Clay enjoys music and discovering great fiction . Clay Fisher Companies Adept We’re building a machine-learning model that can interact with everything on your computer. Read the Story Visit the Website Adept Capella Space Capella Space is a space company that operates a fleet of the first and only U.S. commercial SAR satellites. Co-led Series A in 2018 Read the Story Visit the Website Capella Space Cruise Cruise is building the world’s most advanced self-driving vehicles to safely connect people with the places, things, and experiences they care about. Led Series A in 2015 Acquired by General Motors in 2016 Read the Story Visit the Website Cruise Discord Discord is the easiest way to communicate over voice, video, and text with your friends and communities. Led Series C in 2016 Read the Story Visit the Website Discord Harmonix Harmonix is one of the world’s leading independent game development studios, best known for creating blockbuster franchises like Rock Band and Dance Central. Co-led Series A in 2015 Acquired by Epic Games in 2021 Read the Story Visit the Website Harmonix Instawork Instawork helps local businesses quickly fill permanent and temporary openings with the most qualified professionals in their communities. Led Series B in 2019 Read the Story Visit the Website Instawork Postmates Postmates pioneered the on-demand delivery movement in the U.S. by offering delivery from restaurants and stores previously only available offline. Led Series B in 2014 Acquired by Uber in 2020 Read the Story Visit the Website Postmates Proletariat Proletariat is a group of community-first game developers and the creators of the hit game, Spellbreak. Led Seed in 04/12/2013 Acquired by Activision/Blizzard in 2023 Read the Story Visit the Website Proletariat Zum Zūm provides safe, efficient, and reliable child transportation for school districts and busy families. Led Series B in 2018 Read the Story Visit the Website Zum © Spark Capital 2024 Contact Us Terms & Policies “The nuts and bolts of infrastructure is something that really excites me. These are companies enabling entirely new ways of doing things—the outcomes and innovation are often a lot higher.” “Founders for the most part are engineers or product people. Deeply understanding what they're building is a big part of connecting with them.” “Selling or buying a company tends to be one of the most important and emotional decisions a CEO will make. Working with founders through these pivotal moments, helped me develop deep relationships where I earned their trust.” Clay is a major fan of rock and roll. “I always listen to the live version.. “I’ve always loved fiction. By immersing yourself in a world foreign to your own, you have no choice but to listen completely.” | 2026-01-13T09:29:30 |
https://uptimerobot.com | UptimeRobot: Free Website Monitoring Service Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Go to Dashboard Register for FREE The world's leading uptime monitoring service . 50 monitors for free 20+ integrations Real-time alerts, web & mobile Public status pages Start monitoring in 30 seconds Start monitoring in 30 seconds Trusted by over 2.5 million users and companies All you really care about. Monitored in one place. div > .card"> Website monitoring Be the first to know that your website is down! Reliable monitoring warns you before any significant trouble and saves you money. Explore more Response time monitoring Monitor response times and spot slowdowns immediately with customizable alerts. Explore more DNS monitoring Get alerted when your DNS records change. Monitor DNS entries and detect unexpected changes before they impact your service. Explore more div > .card"> SSL monitoring Don't lose visitors because of an expired SSL certificate. Get notified 30, 14 and 7 days before expiration. Explore more Domain expiration monitoring Keep your online presence secure and avoid any potential damage by monitoring your domain's expiration date. Explore more Cron job monitoring Also known as heartbeat monitoring. Monitor recurring background jobs or intranet devices connected to the internet. Explore more div > .card"> Port monitoring Is the email service still UP? How about the critical database server? Let's check! Monitor any specific service running on any port. Explore more Ping monitoring Leverage one of the most used tools administrators use to check the availability of network devices. Explore more Keyword monitoring Use keyword monitoring to check presence or absence of specific text in the request's response body (typically HTML or JSON). Explore more Start monitoring in 30 seconds Downtime happens . Get notified! Downtime happens even to the best of us. But it’s important to know it before customers are affected! Explore integrations Email Email is the most popular way for any notification. Get alerted! SMS Get alerted instantly by SMS, useful when you are offline! Voice call Get an automated voice call from us whenever your website is down. Slack Slack messages are a great way to inform the entire team! Zapier Integrate your Zapier account to get alerted right away. Telegram Telegram messages are great to get quickly alerted. Webhooks For advanced alerting you can setup custom webhooks to your specific system. Discord Get important monitor status updates in your Discord messages. Microsoft Teams Get notifications inside your MS Teams app to alert everyone in the group. See all 15 integrations Advanced features for advanced users . Share updates Response time monitoring White-labeled Status pages Maintenance windows Custom HTTP requests Multi-location checks Share updates Keep your users informed about planned maintenance or ongoing incidents with automated email notifications before they ask. Explore more Response time monitoring Receive instant alerts the moment your website or server performance drops below your defined threshold, so you can act before it affects anyone. Explore more White-labeled Status pages Customize your public status page with your own brand colors, logo, fonts, layout, theme, and advanced settings. Explore more Maintenance windows Schedule planned maintenance to avoid false downtime alerts and keep your uptime stats clean and accurate. Explore more Custom HTTP requests Fine-tune your monitoring with specific HTTP methods, headers, and request bodies tailored to your application’s needs. Multi-location checks Add monitors from specific locations that matter the most to you and identify regional incidents in time. Explore more Start monitoring in 30 seconds Keep monitoring everywhere you go, with our mobile app . Get instant notifications, manage monitors and check your uptime statistics on the go. Inform your customers about incidents with status pages . Be transparent. Inform customers of planned outages. Show them that you strive to keep your service 100% online. Check live demo Explore status pages Add your team members to keep them notified . You can invite all your team members to access your monitors, keep them notified and manage incidents. Choose from three levels of user access: read, write and notify-only. Explore incident management Why over 2.5 million users trust UptimeRobot . Basem A. Reliable service It was a wonderful experience and I would highly recommend it. UptimeRobot has exceeded my expectations with its efficient monitoring and notification system. Thanks to their service, I've been able to stay on top of any downtime issues and ensure maximum uptime for my online presence, highly recommended! Reviewed on Capterra.com Michael N., Director of Media Relations UptimeRobot Works Great -- And Believe It! Our Native Amerrican news magazine/public service website is www.nativeamericatoday.com. Our former developer did a horrible job, which continually allowed bots to attack the site -- we went over our server's resource limits multiple times and crashed... Reviewed on G2.com Michael Palmer Piece of Mind Monitoring I have recently moved monitoring to UptimeRobot for some critical links and external facing services within our organization. Internal monitoring programs are great until the internet is down and you don't know because you can't get the alerts out... Reviewed on Trustpilot.com Basem A. Reliable service It was a wonderful experience and I would highly recommend it. UptimeRobot has exceeded my expectations with its efficient monitoring and notification system. Thanks to their service, I've been able to stay on top of any downtime issues and ensure maximum uptime for my online presence, highly recommended! Reviewed on Capterra.com Michael N., Director of Media Relations UptimeRobot Works Great -- And Believe It! Our Native Amerrican news magazine/public service website is www.nativeamericatoday.com. Our former developer did a horrible job, which continually allowed bots to attack the site -- we went over our server's resource limits multiple times and crashed... Reviewed on G2.com 4.7 stars out of 5 230+ reviews on G2 Meet our users Simple pricing . Powerful monitoring . Save ~20% with annual billing . Annual Monthly Free . $ 0 / month Good for hobby projects. No credit card required! Register now 50 monitors 😐 5 min. monitoring interval HTTP, port & ping monitor Keyword monitor Location-specific monitoring Slow response alerts DNS monitoring SSL & Domain exp. monitor 😐 Only 5 integrations 😐 Basic status pages Notify seats unavailable No login seats available Solo . $ 8 7 8 19 15 19 / month Great for solopreneurs and hobbyists. Subscribe now 10 monitors 50 monitors 60 sec. monitoring interval HTTP, port & ping monitor Keyword monitor 🆕 Location-specific monitoring 🆕 Slow response alerts 🆕 DNS monitoring SSL & Domain exp. monitor 🙂 Only 9 integrations 😐 Basic status pages Notify seats available No login seats available Team . $ 34 29 34 / month For a small team who needs to collaborate. Subscribe now 100 monitors 60 sec. monitoring interval HTTP, port & ping monitor Keyword monitor 🆕 Location-specific monitoring 🆕 Slow response alerts 🆕 DNS monitoring SSL & Domain exp. monitor All 12 integrations Full-featured status pages 3 notify seats incl. 3 login seats incl. Enterprise . $ 64 54 64 149 124 149 376 289 376 / month For those who just need more. Subscribe now Get quote 200 monitors 500 monitors 1,000+ monitors 30 sec. monitoring interval HTTP, port & ping monitor Keyword monitor 🆕 Location-specific monitoring 🆕 Slow response alerts 🆕 DNS monitoring SSL & Domain exp. monitor All 12 integrations Full-featured status pages 5 notify seats incl. 5 login seats incl. See feature comparison Get your FREE account now, 50 monitors included ! Start monitoring in 30 seconds No credit card required! Available also on: Frequently asked questions . What is UptimeRobot? UptimeRobot is an uptime monitoring service that continuously checks websites, APIs, and other endpoints . It alerts you when anything goes down, degrades, or changes. So you can stay on top of your systems' current states and identify issues before your users do. UptimeRobot also provides tools to transparently communicate the real-time status and reliability of your systems, and proactively manage incidents when they happen. What is an uptime monitor? An uptime monitor is a single tool that repeatedly verifies a target webpage or service is online and working as expected. When an uptime monitor detects a problem, it instantly sends alerts (via email, SMS/IM, call, etc.) so you can respond quickly. It also records incidents with timestamps and details in your dashboard so that you can track reliability over time. Uptime monitors support various monitoring types (HTTP, Ping, Port, Keyword, DNS, Heartbeat), targets (URL/IP/Port), and alerting rules (including escalation). How do I monitor the uptime of a website? Sign up to create a free UptimeRobot account In the dashboard, click Add New Monitor Choose HTTP(S) as the monitor type and enter the website URL Set the monitoring interval and any optional settings you care about (timeouts, redirects, keyword checks) Add your preferred notification channels (email, push, Slack, SMS, etc.) and save the monitor Optionally: create a status page How do I create a status page? Sign up and create a free UptimeRobot account Create your first monitor (so there's something to display) Go to Status Pages and click Create Status Page Select the monitors (or tags) you want to show, then name the page Publish your status page Optionally: customize the design , set a custom domain, password-protect it, opt out of search engine indexing, and use announcements for incident/maintenance updates (users can subscribe with email right on your status page). What can I monitor with UptimeRobot? With UptimeRobot, you can monitor any website, API, server, application, service, network , or endpoint, whether it’s yours, a third-party vendor’s, or a dependency you rely on. Additionally, UptimeRobots supports these monitor types: HTTP/HTTPS Keywords in server responses and on-page Ping Port Cron jobs/heartbeats Website change detection Response time DNS changes SSL certificates and domain expiry The variety of monitor types lets you track availability, response behavior, certificates, scheduled jobs, and infrastructure changes from one place. How often does UptimeRobot check my website? UptimeRobot can check your site and other endpoints as often as every 30 seconds and as infrequently as every 5 minutes, depending on your monitor's settings. The available monitoring intervals in your account also depend on your plan: Free: every 5 minutes Solo/Team: every 60 seconds Enterprise: every 30 seconds Faster intervals improve time-to-detect, but can create more noise if your endpoint is flaky or the network is unstable. Can I monitor from multiple locations/regions? Yes, UptimeRobots supports location-specific monitoring . With multi-location checks, you can spot regional outages, routing problems, or CDN edge issues that won't show up from a single vantage point. It's especially useful for DNS and security scenarios where failures can first appear in one location. How do I get an alert when a website is down (by email, SMS/IM, or phone)? Add one or more notification channels and associate them with your monitors. The available personal channels include Email, SMS, Voice Call, Mobile App Push, and Email-to-SMS; and the integrations include Telegram , Slack , Microsoft Teams , Discord , Google Chat , Mattermost, PagerDuty , Splunk On-Call, Pushbullet , and Pushover . For custom workflows, you can also use Webhooks , Zapier , MCP , or API . How does UptimeRobot reduce false alarms (false positives)? UptimeRobot reduces false alarms by rechecking failures across multiple checker nodes and locations before opening an incident. You can further improve signal-to-noise by white-listing UptimeRobot’s locations and IP addresses , tuning sensitivity (timeouts and delays), and using more specific checks (such as validating a keyword or expected response behavior). For planned work, use maintenance windows to pause monitoring so expected downtime doesn’t trigger alerts or affect uptime calculation and downtime statistics. How many monitors do you need? UptimeRobot offers custom monitoring solutions tailored for agencies, service providers, software companies, and enterprises. Number of monitors Use the slider to estimate the number of monitors. 1k 5k 15k 25k+ Email Company Name Book a demo You will be redirected to a calendar booking page Downtime happens. Get notified! Join more than 2,700,000+ happy users! UptimeRobot is one of the most popular website monitoring services in the world. Monitoring . Website monitoring SSL monitoring Domain monitoring Ping monitoring Port monitoring TCP monitoring Cron job monitoring Keyword monitoring Location-specific monitoring Response time monitoring Incident Management DNS monitoring Company . Pricing Blog Affiliate program Referral program Non profit & charities 🤲 Terms / Privacy Contact us We are hiring! Resources . Integrations API FAQs Help center Locations & IPs Comparisons Case studies Knowledge hub Roadmap Subnet calculator MX lookup Uptime calculator CrontabRobot Website change detection Features Uptime monitoring Website & endpoint monitoring Keyword monitoring Ping monitoring Port monitoring Cron job monitoring Monitoring features Domain monitoring SSL monitoring Response time monitoring Multi-location monitoring DNS monitoring Incident management Status pages MCP Integrations Solutions For every team Devops Developers Marketers Support Business owners Go further with API Meet our users Customers Enterprise Resources Help & learn Help center Location and IPs API docs Knowledge hub Community Roadmap Blog Discord Referral program Affiliate program Non-profit Suggest a feature Free tools Subnet calculator Find the subnet of any IP address MX lookup Instantly check MX records for any domain Uptime calculator Calculate uptime, downtime, and outage costs CrontabRobot Create and validate crontab expressions Website change detection Track visual changes on any webpage Pricing Log In Register for FREE 🍪 This website use cookies. Learn more Decline all | Allow essential | Accept all | 2026-01-13T09:29:30 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.