Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 46B5F200CC1 for ; Mon, 10 Jul 2017 16:21:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 453321659B7; Mon, 10 Jul 2017 14:21:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 87C1B1659B0 for ; Mon, 10 Jul 2017 16:21:03 +0200 (CEST) Received: (qmail 58213 invoked by uid 500); 10 Jul 2017 14:21:02 -0000 Mailing-List: contact issues-help@ariatosca.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ariatosca.incubator.apache.org Delivered-To: mailing list issues@ariatosca.incubator.apache.org Received: (qmail 58204 invoked by uid 99); 10 Jul 2017 14:21:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jul 2017 14:21:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 462F5193743 for ; Mon, 10 Jul 2017 14:21:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id RvOy1EPDlQwu for ; Mon, 10 Jul 2017 14:21:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4050D6245C for ; Mon, 10 Jul 2017 14:21:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 78752E090E for ; Mon, 10 Jul 2017 14:21:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1C78B24686 for ; Mon, 10 Jul 2017 14:21:00 +0000 (UTC) Date: Mon, 10 Jul 2017 14:21:00 +0000 (UTC) From: "Maxim Orlov (JIRA)" To: issues@ariatosca.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ARIA-312) Validation of workflow and operation kwargs raise False alarms MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 10 Jul 2017 14:21:04 -0000 [ https://issues.apache.org/jira/browse/ARIA-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Orlov updated ARIA-312: ----------------------------- Description: Each workflow and operation has a validation function which validates the kwargs provided for that function. However, it sometimes raises false alarms, which prevents from the operation or the workflow from running entirely. e.g. validating {{ foo(arg1, arg2=2, arg3=3) }} with {{ kwargs={'arg1': 1, 'arg3': 3} }} raises an issue was: Each workflow and operation has a validation function which validates the kwargs provided for that function. However, it sometimes raises false alarms, which prevents from the operation or the workflow from running entirely. e.g. validating ```foo(arg1, arg2=2, arg3=3)``` with `kwargs={'arg1': 1, 'arg3': 3}` raises an issue > Validation of workflow and operation kwargs raise False alarms > -------------------------------------------------------------- > > Key: ARIA-312 > URL: https://issues.apache.org/jira/browse/ARIA-312 > Project: AriaTosca > Issue Type: Bug > Reporter: Maxim Orlov > Priority: Critical > > Each workflow and operation has a validation function which validates the kwargs provided for that function. > However, it sometimes raises false alarms, which prevents from the operation or the workflow from running entirely. e.g. validating {{ foo(arg1, arg2=2, arg3=3) }} with {{ kwargs={'arg1': 1, 'arg3': 3} }} raises an issue -- This message was sent by Atlassian JIRA (v6.4.14#64029)