[jira] [Updated] (NIFI-12695) Add RFC 7636 PKCE Support to OpenID Connect Integration
[ https://issues.apache.org/jira/browse/NIFI-12695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12695: Status: Patch Available (was: Open) > Add RFC 7636 PKCE Support to OpenID Connect Integration > --- > > Key: NIFI-12695 > URL: https://issues.apache.org/jira/browse/NIFI-12695 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Julien G. >Assignee: David Handermann >Priority: Major > > It might be intersting to allow the OIDC authentication with PKCE code. It > should be done in a way that NiFi must remain compatible with OIDC provider > that doesn't implement it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12695) Add RFC 7636 PKCE Support to OpenID Connect Integration
[ https://issues.apache.org/jira/browse/NIFI-12695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12695: Summary: Add RFC 7636 PKCE Support to OpenID Connect Integration (was: OIDC authentication with PKCE code ) > Add RFC 7636 PKCE Support to OpenID Connect Integration > --- > > Key: NIFI-12695 > URL: https://issues.apache.org/jira/browse/NIFI-12695 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Julien G. >Assignee: David Handermann >Priority: Major > > It might be intersting to allow the OIDC authentication with PKCE code. It > should be done in a way that NiFi must remain compatible with OIDC provider > that doesn't implement it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12701) RAT check failure
[ https://issues.apache.org/jira/browse/NIFI-12701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bean updated NIFI-12701: - Status: Patch Available (was: In Progress) > RAT check failure > - > > Key: NIFI-12701 > URL: https://issues.apache.org/jira/browse/NIFI-12701 > Project: Apache NiFi > Issue Type: Bug >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > > Files with unapproved licenses: > > nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/.prettierignore > This file was introduced with NIFI-12686. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12701) RAT check failure
[ https://issues.apache.org/jira/browse/NIFI-12701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bean reassigned NIFI-12701: Assignee: Mark Bean > RAT check failure > - > > Key: NIFI-12701 > URL: https://issues.apache.org/jira/browse/NIFI-12701 > Project: Apache NiFi > Issue Type: Bug >Reporter: Mark Bean >Assignee: Mark Bean >Priority: Major > > Files with unapproved licenses: > > nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/.prettierignore > This file was introduced with NIFI-12686. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12695) OIDC authentication with PKCE code
[ https://issues.apache.org/jira/browse/NIFI-12695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann reassigned NIFI-12695: --- Assignee: David Handermann > OIDC authentication with PKCE code > --- > > Key: NIFI-12695 > URL: https://issues.apache.org/jira/browse/NIFI-12695 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Julien G. >Assignee: David Handermann >Priority: Major > > It might be intersting to allow the OIDC authentication with PKCE code. It > should be done in a way that NiFi must remain compatible with OIDC provider > that doesn't implement it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12701) RAT check failure
Mark Bean created NIFI-12701: Summary: RAT check failure Key: NIFI-12701 URL: https://issues.apache.org/jira/browse/NIFI-12701 Project: Apache NiFi Issue Type: Bug Reporter: Mark Bean Files with unapproved licenses: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/.prettierignore This file was introduced with NIFI-12686. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12700) PutKudu memory optimization for unbatched flush mode (AUTO_FLUSH_SYNC)
Emilio Setiadarma created NIFI-12700: Summary: PutKudu memory optimization for unbatched flush mode (AUTO_FLUSH_SYNC) Key: NIFI-12700 URL: https://issues.apache.org/jira/browse/NIFI-12700 Project: Apache NiFi Issue Type: Improvement Reporter: Emilio Setiadarma Assignee: Emilio Setiadarma The PutKudu processor's existing implementation uses a Map of KuduOperation -> FlowFile to keep track of which FlowFile was processing when the KuduOperation was created. This is mapping is eventually used to associate FlowFiles with the RowError (if any occurs), a mapping that is necessary for transferring FlowFiles to success/failure relationships or logging failures among other things. For very large inputs, Kudu Operation objects can grow very large. There is no memory leak, but still could cause OutOfMemory issues in very large input data. There is a possibility to not require the use of a KuduOperation -> FlowFile map for unbatched flush modes (e.g. when using the AUTO_FLUSH_SYNC flush mode, where the KuduSession.apply() would have already flushed the buffer before returning, [https://kudu.apache.org/apidocs/org/apache/kudu/client/SessionConfiguration.FlushMode.html)|https://kudu.apache.org/apidocs/org/apache/kudu/client/SessionConfiguration.FlushMode.html] This Jira attempts to capture the efforts for refactoring PutKudu processor to make it more memory optimized. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12684) Canvas Controller Services - General API error response handling
[ https://issues.apache.org/jira/browse/NIFI-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12684: --- Status: Patch Available (was: In Progress) > Canvas Controller Services - General API error response handling > > > Key: NIFI-12684 > URL: https://issues.apache.org/jira/browse/NIFI-12684 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > Update the Canvas Controller Services page to show API error responses. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12683) Consider PG permissions in Toolbox
[ https://issues.apache.org/jira/browse/NIFI-12683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12683: --- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Consider PG permissions in Toolbox > -- > > Key: NIFI-12683 > URL: https://issues.apache.org/jira/browse/NIFI-12683 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Update the new canvas items in the Toolbox to consider the permissions in the > current Process Group. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12641) Add local file upload option in PutS3 processor
[ https://issues.apache.org/jira/browse/NIFI-12641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael W Moser reassigned NIFI-12641: -- Assignee: (was: Peter Turcsanyi) > Add local file upload option in PutS3 processor > --- > > Key: NIFI-12641 > URL: https://issues.apache.org/jira/browse/NIFI-12641 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Balázs Gerner >Priority: Major > > There are cases when the files to be uploaded to Azure Storage are available > on the local filesystem where NiFi is running. That is, the flow could read > and upload the files directly from the filesystem without adding it in NiFi's > content repo which is an overhead in this case (can be relevant for huge > files). > Add "Data to Upload" property with options "FlowFile's Content" (default, > current behaviour) and "Local File". Using the latter, the user can by-pass > the content repo and upload the file from the local filesystem to Azure > Storage directly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12641) Add local file upload option in PutS3 processor
[ https://issues.apache.org/jira/browse/NIFI-12641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael W Moser resolved NIFI-12641. Resolution: Duplicate > Add local file upload option in PutS3 processor > --- > > Key: NIFI-12641 > URL: https://issues.apache.org/jira/browse/NIFI-12641 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Balázs Gerner >Priority: Major > > There are cases when the files to be uploaded to Azure Storage are available > on the local filesystem where NiFi is running. That is, the flow could read > and upload the files directly from the filesystem without adding it in NiFi's > content repo which is an overhead in this case (can be relevant for huge > files). > Add "Data to Upload" property with options "FlowFile's Content" (default, > current behaviour) and "Local File". Using the latter, the user can by-pass > the content repo and upload the file from the local filesystem to Azure > Storage directly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12641) Add local file upload option in PutS3 processor
[ https://issues.apache.org/jira/browse/NIFI-12641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael W Moser updated NIFI-12641: --- Fix Version/s: (was: 2.0.0-M1) (was: 1.23.0) > Add local file upload option in PutS3 processor > --- > > Key: NIFI-12641 > URL: https://issues.apache.org/jira/browse/NIFI-12641 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Balázs Gerner >Assignee: Peter Turcsanyi >Priority: Major > > There are cases when the files to be uploaded to Azure Storage are available > on the local filesystem where NiFi is running. That is, the flow could read > and upload the files directly from the filesystem without adding it in NiFi's > content repo which is an overhead in this case (can be relevant for huge > files). > Add "Data to Upload" property with options "FlowFile's Content" (default, > current behaviour) and "Local File". Using the latter, the user can by-pass > the content repo and upload the file from the local filesystem to Azure > Storage directly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12689) Upgrade testcontainers.version to 1.19.4
[ https://issues.apache.org/jira/browse/NIFI-12689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12689. - Fix Version/s: 2.0.0 1.26.0 Resolution: Fixed > Upgrade testcontainers.version to 1.19.4 > > > Key: NIFI-12689 > URL: https://issues.apache.org/jira/browse/NIFI-12689 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Fix For: 2.0.0, 1.26.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Upgrade testcontainers.version to 1.19.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12689) Upgrade testcontainers.version to 1.19.4
[ https://issues.apache.org/jira/browse/NIFI-12689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12689: Affects Version/s: (was: 2.0.0-M2) > Upgrade testcontainers.version to 1.19.4 > > > Key: NIFI-12689 > URL: https://issues.apache.org/jira/browse/NIFI-12689 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Upgrade testcontainers.version to 1.19.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12689) Upgrade testcontainers.version to 1.19.4
[ https://issues.apache.org/jira/browse/NIFI-12689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12689: Priority: Minor (was: Major) > Upgrade testcontainers.version to 1.19.4 > > > Key: NIFI-12689 > URL: https://issues.apache.org/jira/browse/NIFI-12689 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Upgrade testcontainers.version to 1.19.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12690) Update opentelemetry-proto to 1.1.0-alpha
[ https://issues.apache.org/jira/browse/NIFI-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12690: Component/s: Extensions > Update opentelemetry-proto to 1.1.0-alpha > - > > Key: NIFI-12690 > URL: https://issues.apache.org/jira/browse/NIFI-12690 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Update opentelemetry-proto to 1.1.0-alpha -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12690) Update opentelemetry-proto to 1.1.0-alpha
[ https://issues.apache.org/jira/browse/NIFI-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12690. - Fix Version/s: 2.0.0 1.26.0 Resolution: Fixed > Update opentelemetry-proto to 1.1.0-alpha > - > > Key: NIFI-12690 > URL: https://issues.apache.org/jira/browse/NIFI-12690 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Fix For: 2.0.0, 1.26.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Update opentelemetry-proto to 1.1.0-alpha -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12690) Update opentelemetry-proto to 1.1.0-alpha
[ https://issues.apache.org/jira/browse/NIFI-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12690: Affects Version/s: (was: 2.0.0-M2) > Update opentelemetry-proto to 1.1.0-alpha > - > > Key: NIFI-12690 > URL: https://issues.apache.org/jira/browse/NIFI-12690 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Update opentelemetry-proto to 1.1.0-alpha -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12690) Update opentelemetry-proto to 1.1.0-alpha
[ https://issues.apache.org/jira/browse/NIFI-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12690: Priority: Minor (was: Major) > Update opentelemetry-proto to 1.1.0-alpha > - > > Key: NIFI-12690 > URL: https://issues.apache.org/jira/browse/NIFI-12690 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike R >Assignee: Mike R >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Update opentelemetry-proto to 1.1.0-alpha -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12699) Unit test timeout value too short for systems with slow disks
Mark Bean created NIFI-12699: Summary: Unit test timeout value too short for systems with slow disks Key: NIFI-12699 URL: https://issues.apache.org/jira/browse/NIFI-12699 Project: Apache NiFi Issue Type: Improvement Components: Tools and Build Reporter: Mark Bean Assignee: Mark Bean When building NiFi on a VM with relatively old disks, a unit test consistently fails due timing out. The unit test in question is: TestStandardFlowFileQueue.testListFlowFilesResultsLimitedCollection Extend the timeout from 5 sec to 10 sec. The value of 10 allows consistent passing of this unit test. On systems with faster disks, this increase in timeout will be inconsequential, i.e. will not slow down the build. Yet, the extension will allow compilation on older systems. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12687) BUG - y axis is missing from status history charts
[ https://issues.apache.org/jira/browse/NIFI-12687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Aslan reassigned NIFI-12687: -- Assignee: Scott Aslan > BUG - y axis is missing from status history charts > -- > > Key: NIFI-12687 > URL: https://issues.apache.org/jira/browse/NIFI-12687 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > > NiFi 1.x: > !https://private-user-images.githubusercontent.com/713866/300824635-c3dd91cd-d1e3-4435-a061-c942d908db97.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDY2MjQ4OTIsIm5iZiI6MTcwNjYyNDU5MiwicGF0aCI6Ii83MTM4NjYvMzAwODI0NjM1LWMzZGQ5MWNkLWQxZTMtNDQzNS1hMDYxLWM5NDJkOTA4ZGI5Ny5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEzMFQxNDIzMTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03YjlmMTg3YmUyN2Q1NWZkMWQ4ZDk4OGYxZjAxZjA1Mjc1MTc3MzI4M2Y0ZTczZGEyNzk3NTYwODFjZmQ4YjAxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.3ugCkPl9mECLrZIG55Fla6ndlOzMKxq098dKqUIv-bw! > > New UI: > !https://private-user-images.githubusercontent.com/713866/300824398-05fd832e-5051-458c-b0b5-0149dd203944.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDY2MjQ4OTIsIm5iZiI6MTcwNjYyNDU5MiwicGF0aCI6Ii83MTM4NjYvMzAwODI0Mzk4LTA1ZmQ4MzJlLTUwNTEtNDU4Yy1iMGI1LTAxNDlkZDIwMzk0NC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEzMFQxNDIzMTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00MmJhZDVlNDA3NzM5NjZmZGJkNzMzMDAzNWNhMmIwZjQ4OGJiZDk3YzU0MTgzMWI0ZjA2MDc1NWFlODcyMjk3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.sweJ-smR0nptjUc0dOJkEqlP975WFrPAhVE9M2BxGYQ! > > Discussion: https://github.com/apache/nifi/pull/8294#discussion_r1471227264 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12698) Introduce Dark Mode
Scott Aslan created NIFI-12698: -- Summary: Introduce Dark Mode Key: NIFI-12698 URL: https://issues.apache.org/jira/browse/NIFI-12698 Project: Apache NiFi Issue Type: Sub-task Reporter: Scott Aslan Assignee: Scott Aslan -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-9770) Upgrade Cassandra Components to Datastax 4 Driver
[
https://issues.apache.org/jira/browse/NIFI-9770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812435#comment-17812435
]
David Handermann commented on NIFI-9770:
Thanks [~mike.thomsen], I'm not actively working on this right now, so if you
get to the point of having something ready, feel free to note that. I'll also
update if I end up taking a closer look at these changes.
> Upgrade Cassandra Components to Datastax 4 Driver
> -
>
> Key: NIFI-9770
> URL: https://issues.apache.org/jira/browse/NIFI-9770
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: David Handermann
>Priority: Major
>
> The Processors and Controller Services in the {{nifi-cassandra-bundle}}
> leverage the Datastax Driver version 3.10.2, which includes a transitive
> dependency on Google Guava 19.0. Older versions of Google Guava have several
> associated vulnerabilities, which do not appear to impact the Datastax Driver
> directly. In order to upgrade to a more recent version of Google Guava,
> however, it is necessary to upgrade to a recent version 4 release of the
> Datastax Driver. Datastax Driver 4.14.0 depends on Google Guava 25.0.
> The Datastax Driver version 4 supports access to Cassandra 2.1 and above, but
> upgrading the driver from version 3 to version 4 requires a number of
> changes. Several of the client configuration properties, accessible through
> NiFi component properties, must be provided through a different approach than
> the current driver configuration strategy. The Datastax Driver Upgrade Guide
> provides a summary of the relevant driver changes:
> https://docs.datastax.com/en/developer/java-driver/4.13/upgrade_guide/#4-0-0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] NIFI-12697: Allow disabling scientific notation when writing JSON; us… [nifi]
markap14 opened a new pull request, #8319: URL: https://github.com/apache/nifi/pull/8319 …e Jackson's internal implementations for parsing big integers and floating-point numbers more efficiently # Summary [NIFI-0](https://issues.apache.org/jira/browse/NIFI-0) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12697) Improve JSON Reader/Writer handling of floating-point numbers
Mark Payne created NIFI-12697: - Summary: Improve JSON Reader/Writer handling of floating-point numbers Key: NIFI-12697 URL: https://issues.apache.org/jira/browse/NIFI-12697 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Mark Payne Assignee: Mark Payne Fix For: 2.0.0 The JSON Writer currently provides no way to dictate whether or not floating-point numbers should use scientific notation. Several people have run into issues where the downstream systems do not understand scientific notation. We should allow this to be configurable. Specifically, we should not change the behavior of existing services, but we should default new services so that they do not use scientific notation. Additionally, the Jackson parser has the ability to use its own implementation of floating point parsing, which should be faster than the default version supplied by Java. We should enable that feature. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-1931) QueryDatabaseTable processor; setFetchSize not working for postgres driver causing out of memory
[ https://issues.apache.org/jira/browse/NIFI-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812423#comment-17812423 ] Dmitry Dmitriev commented on NIFI-1931: --- Hi! We experience the same issue here. Would it be possible to add either a property "AutoCommit" to the QueryDatabaseTable processor, so that it can be switched off for Postgresql? Or add custom code that will switch AutoCommit property off before starting the processing? There are some ideas here on how it can be done [https://stackoverflow.com/questions/17475105/when-does-the-postgresql-jdbc-driver-fetch-rows-after-executing-a-query] Any ideas appreciated! Thank you! Dmitry > QueryDatabaseTable processor; setFetchSize not working for postgres driver > causing out of memory > > > Key: NIFI-1931 > URL: https://issues.apache.org/jira/browse/NIFI-1931 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 0.6.1 >Reporter: Paul Bormans >Priority: Major > > With NIFI-1691 the ability to specify the fetch size is added. However for > postgres driver (or at least for postgresql-9.4.1208.jre6.jar) this seems not > to be working since after some time out of memory is reported in the logs. > See https://jdbc.postgresql.org/documentation/head/query.html also for some > constraints; like auto commit needs to be set to False. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12686) Add Linting
[ https://issues.apache.org/jira/browse/NIFI-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812420#comment-17812420 ] ASF subversion and git services commented on NIFI-12686: Commit d9012539740390d3abbe5230eed8be4c78657ff6 in nifi's branch refs/heads/main from Rob Fellows [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d901253974 ] [NIFI-12686] eslint configuration (#8313) * [NIFI-12686] eslint configuration for ts files * add linting to the default maven build * updates for RAT plugin * remove .eslitrc as it wasn't needed. updated RAT config This closes #8313 > Add Linting > --- > > Key: NIFI-12686 > URL: https://issues.apache.org/jira/browse/NIFI-12686 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12686) Add Linting
[ https://issues.apache.org/jira/browse/NIFI-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12686: --- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Add Linting > --- > > Key: NIFI-12686 > URL: https://issues.apache.org/jira/browse/NIFI-12686 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Fix For: 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12686] eslint configuration [nifi]
mcgilman merged PR #8313: URL: https://github.com/apache/nifi/pull/8313 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] NIFI-12696 Fix authorization issues when requesting FlowAnalysisResults [nifi]
tpalfy opened a new pull request, #8318: URL: https://github.com/apache/nifi/pull/8318 RuleViolations (these objects only reside in memory only) now contain the type of the component that is responsible for the violation. This is used in StandardNiFiServiceFacade to fix and improve the authorization logic. # Summary [NIFI-12696](https://issues.apache.org/jira/browse/NIFI-12696) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12694) BUG - Console error messages when Starting/Stopping a process group
[
https://issues.apache.org/jira/browse/NIFI-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Fellows updated NIFI-12694:
---
Status: Patch Available (was: In Progress)
> BUG - Console error messages when Starting/Stopping a process group
> ---
>
> Key: NIFI-12694
> URL: https://issues.apache.org/jira/browse/NIFI-12694
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Rob Fellows
>Assignee: Rob Fellows
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> _This doesn't seem to affect functionality_
>
> There are 2 distinct errors in the console when starting/stopping process
> groups either from the operation control or the context menu:
> {noformat}
> ERROR TypeError: Cannot read properties of undefined (reading 'canRead')
> at OperationControl.getContextName (operation-control.component.ts:134:40)
> at OperationControl_ng_container_6_div_1_Template
> (operation-control.component.html:38:61)
> at executeTemplate (core.mjs:12003:13)
> at refreshView (core.mjs:13498:13)
> at detectChangesInView (core.mjs:13663:9)
> at detectChangesInEmbeddedViews (core.mjs:13606:13)
> at refreshView (core.mjs:13522:9)
> at detectChangesInView (core.mjs:13663:9)
> at detectChangesInEmbeddedViews (core.mjs:13606:13)
> at refreshView (core.mjs:13522:9){noformat}
> {noformat}
> ERROR TypeError: Cannot read properties of undefined (reading 'canRead')
> at SVGRectElement. (process-group-manager.service.ts:204:34)
> at SVGRectElement. (classed.js:58:12)
> at Selection.__WEBPACK_DEFAULT_EXPORT__ [as each] (each.js:5:37)
> at Selection.__WEBPACK_DEFAULT_EXPORT__ [as classed] (classed.js:71:15)
> at ProcessGroupManager.updateProcessGroups
> (process-group-manager.service.ts:203:39)
> at ProcessGroupManager.set (process-group-manager.service.ts:1368:14)
> at Object.next (process-group-manager.service.ts:1326:22)
> at ConsumerObserver.next (Subscriber.js:91:33)
> at SafeSubscriber._next (Subscriber.js:60:26)
> at SafeSubscriber.next (Subscriber.js:31:18){noformat}
>
> Both appear related to the reducer assuming the response of the api call
> returns the whole object with `permissions` and such. in the case of process
> groups, it is a very sparse return object and doesn't have those.
>
> We should be sure the "fix" works for all startable/stoppable components.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-12694) BUG - Console error messages when Starting/Stopping a process group
[
https://issues.apache.org/jira/browse/NIFI-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Fellows reassigned NIFI-12694:
--
Assignee: Rob Fellows
> BUG - Console error messages when Starting/Stopping a process group
> ---
>
> Key: NIFI-12694
> URL: https://issues.apache.org/jira/browse/NIFI-12694
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Rob Fellows
>Assignee: Rob Fellows
>Priority: Major
>
> _This doesn't seem to affect functionality_
>
> There are 2 distinct errors in the console when starting/stopping process
> groups either from the operation control or the context menu:
> {noformat}
> ERROR TypeError: Cannot read properties of undefined (reading 'canRead')
> at OperationControl.getContextName (operation-control.component.ts:134:40)
> at OperationControl_ng_container_6_div_1_Template
> (operation-control.component.html:38:61)
> at executeTemplate (core.mjs:12003:13)
> at refreshView (core.mjs:13498:13)
> at detectChangesInView (core.mjs:13663:9)
> at detectChangesInEmbeddedViews (core.mjs:13606:13)
> at refreshView (core.mjs:13522:9)
> at detectChangesInView (core.mjs:13663:9)
> at detectChangesInEmbeddedViews (core.mjs:13606:13)
> at refreshView (core.mjs:13522:9){noformat}
> {noformat}
> ERROR TypeError: Cannot read properties of undefined (reading 'canRead')
> at SVGRectElement. (process-group-manager.service.ts:204:34)
> at SVGRectElement. (classed.js:58:12)
> at Selection.__WEBPACK_DEFAULT_EXPORT__ [as each] (each.js:5:37)
> at Selection.__WEBPACK_DEFAULT_EXPORT__ [as classed] (classed.js:71:15)
> at ProcessGroupManager.updateProcessGroups
> (process-group-manager.service.ts:203:39)
> at ProcessGroupManager.set (process-group-manager.service.ts:1368:14)
> at Object.next (process-group-manager.service.ts:1326:22)
> at ConsumerObserver.next (Subscriber.js:91:33)
> at SafeSubscriber._next (Subscriber.js:60:26)
> at SafeSubscriber.next (Subscriber.js:31:18){noformat}
>
> Both appear related to the reducer assuming the response of the api call
> returns the whole object with `permissions` and such. in the case of process
> groups, it is a very sparse return object and doesn't have those.
>
> We should be sure the "fix" works for all startable/stoppable components.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12675) Python Processor erroring when creating custom relationships
[
https://issues.apache.org/jira/browse/NIFI-12675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-12675:
--
Status: Patch Available (was: Open)
> Python Processor erroring when creating custom relationships
>
>
> Key: NIFI-12675
> URL: https://issues.apache.org/jira/browse/NIFI-12675
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> From apache Slack thread
> ([https://apachenifi.slack.com/archives/C0L9VCD47/p1706176890922519):]
> {quote}Hello, I am trying to test some custom python processors with nifi
> 2.0.0-M1
> It works fine except when I try to add custom relationships to it (other than
> the default success, failure and original).
> Here's what I am trying:
> {code:java}
> self.matched = Relationship("matched", "flowfiles having a match with
> the regex")
> self.unmatched = Relationship("unmatched", "flowfiles not having any
> match with regex")
> self.failure = Relationship("failure", "flowfiles for which process
> errored while matching")
> self.relationships = {self.matched, self.unmatched, self.failure}
> {code}
> I get py4j complaining about AttributeError: 'set' object has no attribute
> '_get_object_id'
> which seems like the auto conversion of Python to java container is not
> happening for "Relationship" class. Any idea what could be wrong here?
> {quote}
> The problem appears to be that Relationships created are of type
> {{nifiapi.Relationship}} but that is being sent back to the Java side without
> being converted into a {{org.apache.nifi.processor.Relationship}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] NIFI-12675: Fixed bug that caused custom Relationships not to work on… [nifi]
markap14 opened a new pull request, #8316: URL: https://github.com/apache/nifi/pull/8316 … Python Processors. Added unit test to verify. Also addressed issue in PythonControllerInteractionIT where it did not wait for Processors to become valid (originally this wasn't necessary but when we refactored Processors to initialize in the background this was overlooked). # Summary [NIFI-0](https://issues.apache.org/jira/browse/NIFI-0) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12696) Fix authorization issues when requesting FlowAnalysisResults
Tamas Palfy created NIFI-12696: -- Summary: Fix authorization issues when requesting FlowAnalysisResults Key: NIFI-12696 URL: https://issues.apache.org/jira/browse/NIFI-12696 Project: Apache NiFi Issue Type: Bug Reporter: Tamas Palfy When requesting FlowAnalysisResults the authorization logic performed has a couple of issues: # Doesn't handle exceptions thrown when the a component producing a result is tested to be a Port. The logic goes through possible component types and when reaches Ports it throws an exception. # As the logic goest through possible components, the mismatching ones throw ResourceNotFoundExceptions. These are captured but this is a bad practice in general. Throwing and capturing exceptions in non-exceptional cases is bad from both design and performance perspective. # The number of possible components checked is too limited. If a component is unrecognized, the corresponding violation will have a PermissionDTO attached with canRead and canWrite set to false, essentially rendering the result unavailable and thus leading to a false negative. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12696) Fix authorization issues when requesting FlowAnalysisResults
[ https://issues.apache.org/jira/browse/NIFI-12696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tamas Palfy reassigned NIFI-12696: -- Assignee: Tamas Palfy > Fix authorization issues when requesting FlowAnalysisResults > > > Key: NIFI-12696 > URL: https://issues.apache.org/jira/browse/NIFI-12696 > Project: Apache NiFi > Issue Type: Bug >Reporter: Tamas Palfy >Assignee: Tamas Palfy >Priority: Major > > When requesting FlowAnalysisResults the authorization logic performed has a > couple of issues: > # Doesn't handle exceptions thrown when the a component producing a result is > tested to be a Port. The logic goes through possible component types and when > reaches Ports it throws an exception. > # As the logic goest through possible components, the mismatching ones throw > ResourceNotFoundExceptions. These are captured but this is a bad practice in > general. Throwing and capturing exceptions in non-exceptional cases is bad > from both design and performance perspective. > # The number of possible components checked is too limited. If a component is > unrecognized, the corresponding violation will have a PermissionDTO attached > with canRead and canWrite set to false, essentially rendering the result > unavailable and thus leading to a false negative. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12693: Moved notification of python process that a Processor was… [nifi]
markap14 opened a new pull request, #8315: URL: https://github.com/apache/nifi/pull/8315 … removed to a background (virtual) thread. Also noted in testing that in one instance a Python Processor never became valid because it had cached property descriptors before the processor was fully initialized, so updated code to ensure that we do not cache values before initialization is completed. # Summary [NIFI-0](https://issues.apache.org/jira/browse/NIFI-0) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12695) OIDC authentication with PKCE code
Julien G. created NIFI-12695: Summary: OIDC authentication with PKCE code Key: NIFI-12695 URL: https://issues.apache.org/jira/browse/NIFI-12695 Project: Apache NiFi Issue Type: Improvement Reporter: Julien G. It might be intersting to allow the OIDC authentication with PKCE code. It should be done in a way that NiFi must remain compatible with OIDC provider that doesn't implement it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12693) When Processor is removed, Python Process should be notified asynchronously
[ https://issues.apache.org/jira/browse/NIFI-12693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-12693: -- Status: Patch Available (was: Open) > When Processor is removed, Python Process should be notified asynchronously > --- > > Key: NIFI-12693 > URL: https://issues.apache.org/jira/browse/NIFI-12693 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > When a Processor is removed, the PythonBridge is notified of the removal, and > it then notifies any relevant Python process. This is done synchronously > during the removal. I encountered two occurrences in which notifying the > Python process failed. > While the failure itself is not a huge concern, the handling of those > failures resulted in very bad outcomes. In the first instance, the > communication with the Python process was blocked on a socket read or write. > As a result, the Service Facade's lock was never released, and no web > requests could be made; they all blocked on the read lock. This resulted in > requiring a restart of NiFi. > In the other scenario, the call did not block indefinitely but threw an > Exception. In this case, the associated Connections were never removed. As a > result, I could no longer navigate to that Process Group in the UI, or the UI > would have errors because there were Connections whose source or destination > didn't exist. This required manually removing those connections from the > flow.json file to recover. > Since the intention of this action is simply a notification so that the > Python process can cleanup after itself, this notification should be moved to > a background thread, so that any failures are simply logged without causing > problematic side effects. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12686) Add Linting
[ https://issues.apache.org/jira/browse/NIFI-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12686: --- Status: Patch Available (was: In Progress) > Add Linting > --- > > Key: NIFI-12686 > URL: https://issues.apache.org/jira/browse/NIFI-12686 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12694) BUG - Console error messages when Starting/Stopping a process group
Rob Fellows created NIFI-12694:
--
Summary: BUG - Console error messages when Starting/Stopping a
process group
Key: NIFI-12694
URL: https://issues.apache.org/jira/browse/NIFI-12694
Project: Apache NiFi
Issue Type: Sub-task
Reporter: Rob Fellows
_This doesn't seem to affect functionality_
There are 2 distinct errors in the console when starting/stopping process
groups either from the operation control or the context menu:
{noformat}
ERROR TypeError: Cannot read properties of undefined (reading 'canRead')
at OperationControl.getContextName (operation-control.component.ts:134:40)
at OperationControl_ng_container_6_div_1_Template
(operation-control.component.html:38:61)
at executeTemplate (core.mjs:12003:13)
at refreshView (core.mjs:13498:13)
at detectChangesInView (core.mjs:13663:9)
at detectChangesInEmbeddedViews (core.mjs:13606:13)
at refreshView (core.mjs:13522:9)
at detectChangesInView (core.mjs:13663:9)
at detectChangesInEmbeddedViews (core.mjs:13606:13)
at refreshView (core.mjs:13522:9){noformat}
{noformat}
ERROR TypeError: Cannot read properties of undefined (reading 'canRead')
at SVGRectElement. (process-group-manager.service.ts:204:34)
at SVGRectElement. (classed.js:58:12)
at Selection.__WEBPACK_DEFAULT_EXPORT__ [as each] (each.js:5:37)
at Selection.__WEBPACK_DEFAULT_EXPORT__ [as classed] (classed.js:71:15)
at ProcessGroupManager.updateProcessGroups
(process-group-manager.service.ts:203:39)
at ProcessGroupManager.set (process-group-manager.service.ts:1368:14)
at Object.next (process-group-manager.service.ts:1326:22)
at ConsumerObserver.next (Subscriber.js:91:33)
at SafeSubscriber._next (Subscriber.js:60:26)
at SafeSubscriber.next (Subscriber.js:31:18){noformat}
Both appear related to the reducer assuming the response of the api call
returns the whole object with `permissions` and such. in the case of process
groups, it is a very sparse return object and doesn't have those.
We should be sure the "fix" works for all startable/stoppable components.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12693) When Processor is removed, Python Process should be notified asynchronously
Mark Payne created NIFI-12693: - Summary: When Processor is removed, Python Process should be notified asynchronously Key: NIFI-12693 URL: https://issues.apache.org/jira/browse/NIFI-12693 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 2.0.0 When a Processor is removed, the PythonBridge is notified of the removal, and it then notifies any relevant Python process. This is done synchronously during the removal. I encountered two occurrences in which notifying the Python process failed. While the failure itself is not a huge concern, the handling of those failures resulted in very bad outcomes. In the first instance, the communication with the Python process was blocked on a socket read or write. As a result, the Service Facade's lock was never released, and no web requests could be made; they all blocked on the read lock. This resulted in requiring a restart of NiFi. In the other scenario, the call did not block indefinitely but threw an Exception. In this case, the associated Connections were never removed. As a result, I could no longer navigate to that Process Group in the UI, or the UI would have errors because there were Connections whose source or destination didn't exist. This required manually removing those connections from the flow.json file to recover. Since the intention of this action is simply a notification so that the Python process can cleanup after itself, this notification should be moved to a background thread, so that any failures are simply logged without causing problematic side effects. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12649) Explain why run-nifi.bat closes
[ https://issues.apache.org/jira/browse/NIFI-12649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812370#comment-17812370 ] Simon AUBERT commented on NIFI-12649: - Hello [~mosermw] and thanks for your time and answer. As mentioned, yes, I finally found the source of the error and managed to solve it. My ticket is about having a better way than using a screenshot to get the error message because the window closed immediatly. (and yes, I tried the cmd and it didn't work, I forgot the error message but clearly not the one of the screenshot). Even a small run_nifi_bat.log would be great. Anything that stores the error message would be great. I lost more time (and to be frank temper^^) trying to get the error message than solving the error itself. Best regards, Simon > Explain why run-nifi.bat closes > --- > > Key: NIFI-12649 > URL: https://issues.apache.org/jira/browse/NIFI-12649 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Affects Versions: 2.0.0-M1 > Environment: All >Reporter: Simon AUBERT >Priority: Major > Attachments: image-2024-01-21-10-03-26-177.png > > > Hello all, > Here a frustrating issue that can be solved very easily : I follow the > instructions here [https://nifi.apache.org/documentation/v2/] in order to use > nifi on windows. > So I launched the run-nifi.bat and it closes the windows almost immediatly, > before I can read the message and apparently without logging anything. I lost > a lost of time to find the issue... (a not up to date jdk). How did I do ? By > using Greenshot to make a screenshot and luckily, I got the exact message. > !image-2024-01-21-10-03-26-177.png! > So I would like a way to know why this window closes. I guess logging the > issue to a file can be doable. > Best regards, > Simon -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12686] eslint configuration [nifi]
mcgilman commented on PR #8313: URL: https://github.com/apache/nifi/pull/8313#issuecomment-1917151726 Will review... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (NIFI-12692) Update jline.version to 3.25.1
[ https://issues.apache.org/jira/browse/NIFI-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R reassigned NIFI-12692: - Assignee: Mike R > Update jline.version to 3.25.1 > -- > > Key: NIFI-12692 > URL: https://issues.apache.org/jira/browse/NIFI-12692 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M2 >Reporter: Mike R >Assignee: Mike R >Priority: Major > > Update jline.version to 3.25.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12692) Update jline.version to 3.25.1
Mike R created NIFI-12692: - Summary: Update jline.version to 3.25.1 Key: NIFI-12692 URL: https://issues.apache.org/jira/browse/NIFI-12692 Project: Apache NiFi Issue Type: Improvement Affects Versions: 2.0.0-M2 Reporter: Mike R Update jline.version to 3.25.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12649) Explain why run-nifi.bat closes
[ https://issues.apache.org/jira/browse/NIFI-12649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812362#comment-17812362 ] Michael W Moser commented on NIFI-12649: Hello [~simon.aubert] . Apache NiFi 2.0.0 requires a Java 21 runtime environment or higher. The error you attached shows that you are using Java 17. This will not work. If you open a command window first and then type the run-nifi.bat command, then the window should not close. > Explain why run-nifi.bat closes > --- > > Key: NIFI-12649 > URL: https://issues.apache.org/jira/browse/NIFI-12649 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Affects Versions: 2.0.0-M1 > Environment: All >Reporter: Simon AUBERT >Priority: Major > Attachments: image-2024-01-21-10-03-26-177.png > > > Hello all, > Here a frustrating issue that can be solved very easily : I follow the > instructions here [https://nifi.apache.org/documentation/v2/] in order to use > nifi on windows. > So I launched the run-nifi.bat and it closes the windows almost immediatly, > before I can read the message and apparently without logging anything. I lost > a lost of time to find the issue... (a not up to date jdk). How did I do ? By > using Greenshot to make a screenshot and luckily, I got the exact message. > !image-2024-01-21-10-03-26-177.png! > So I would like a way to know why this window closes. I guess logging the > issue to a file can be doable. > Best regards, > Simon -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12691) Update okio to 3.7.0
[ https://issues.apache.org/jira/browse/NIFI-12691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R reassigned NIFI-12691: - Assignee: Mike R > Update okio to 3.7.0 > > > Key: NIFI-12691 > URL: https://issues.apache.org/jira/browse/NIFI-12691 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike R >Assignee: Mike R >Priority: Major > Fix For: 2.0.0-M2 > > > Update okio to 3.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12691) Update okio to 3.7.0
Mike R created NIFI-12691: - Summary: Update okio to 3.7.0 Key: NIFI-12691 URL: https://issues.apache.org/jira/browse/NIFI-12691 Project: Apache NiFi Issue Type: Improvement Reporter: Mike R Fix For: 2.0.0-M2 Update okio to 3.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12690 Update opentelemetry-proto to 1.1.0-alpha [nifi]
mr1716 opened a new pull request, #8314: URL: https://github.com/apache/nifi/pull/8314 # Summary [NIFI-12690](https://issues.apache.org/jira/browse/NIFI-12690) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI-12690) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12690) Update opentelemetry-proto to 1.1.0-alpha
Mike R created NIFI-12690: - Summary: Update opentelemetry-proto to 1.1.0-alpha Key: NIFI-12690 URL: https://issues.apache.org/jira/browse/NIFI-12690 Project: Apache NiFi Issue Type: Improvement Affects Versions: 2.0.0-M2 Reporter: Mike R Update opentelemetry-proto to 1.1.0-alpha -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12690) Update opentelemetry-proto to 1.1.0-alpha
[ https://issues.apache.org/jira/browse/NIFI-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R reassigned NIFI-12690: - Assignee: Mike R > Update opentelemetry-proto to 1.1.0-alpha > - > > Key: NIFI-12690 > URL: https://issues.apache.org/jira/browse/NIFI-12690 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M2 >Reporter: Mike R >Assignee: Mike R >Priority: Major > > Update opentelemetry-proto to 1.1.0-alpha -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [NIFI-12686] eslint configuration [nifi]
rfellows opened a new pull request, #8313: URL: https://github.com/apache/nifi/pull/8313 also added linting to the default maven build. errors will make the build fail, warning will not. [NIFI-12686](https://issues.apache.org/jira/browse/NIFI-12686) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] NIFI-12689 Upgrade testcontainers.version to 1.19.4 [nifi]
mr1716 opened a new pull request, #8312: URL: https://github.com/apache/nifi/pull/8312 # Summary [NIFI-12689](https://issues.apache.org/jira/browse/NIFI-12689 ) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI-12689) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (NIFI-12689) Upgrade testcontainers.version to 1.19.4
[ https://issues.apache.org/jira/browse/NIFI-12689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R reassigned NIFI-12689: - Assignee: Mike R > Upgrade testcontainers.version to 1.19.4 > > > Key: NIFI-12689 > URL: https://issues.apache.org/jira/browse/NIFI-12689 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M2 >Reporter: Mike R >Assignee: Mike R >Priority: Major > > Upgrade testcontainers.version to 1.19.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12689) Upgrade testcontainers.version to 1.19.4
Mike R created NIFI-12689: - Summary: Upgrade testcontainers.version to 1.19.4 Key: NIFI-12689 URL: https://issues.apache.org/jira/browse/NIFI-12689 Project: Apache NiFi Issue Type: Improvement Affects Versions: 2.0.0-M2 Reporter: Mike R Upgrade testcontainers.version to 1.19.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12688) Upgrade mysql-connector-j to 8.3.0
[ https://issues.apache.org/jira/browse/NIFI-12688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R reassigned NIFI-12688: - Assignee: Mike R > Upgrade mysql-connector-j to 8.3.0 > -- > > Key: NIFI-12688 > URL: https://issues.apache.org/jira/browse/NIFI-12688 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.0.0-M2 >Reporter: Mike R >Assignee: Mike R >Priority: Major > > Upgrade mysql-connector-j to 8.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12688) Upgrade mysql-connector-j to 8.3.0
Mike R created NIFI-12688: - Summary: Upgrade mysql-connector-j to 8.3.0 Key: NIFI-12688 URL: https://issues.apache.org/jira/browse/NIFI-12688 Project: Apache NiFi Issue Type: Improvement Affects Versions: 2.0.0-M2 Reporter: Mike R Upgrade mysql-connector-j to 8.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12662) Conduct Apache NiFi 1.25.0 Release
[ https://issues.apache.org/jira/browse/NIFI-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard resolved NIFI-12662. --- Resolution: Fixed > Conduct Apache NiFi 1.25.0 Release > -- > > Key: NIFI-12662 > URL: https://issues.apache.org/jira/browse/NIFI-12662 > Project: Apache NiFi > Issue Type: Task >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > Fix For: 1.25.0 > > > Conduct Apache NiFi 1.25.0 Release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12687) BUG - y axis is missing from status history charts
Scott Aslan created NIFI-12687: -- Summary: BUG - y axis is missing from status history charts Key: NIFI-12687 URL: https://issues.apache.org/jira/browse/NIFI-12687 Project: Apache NiFi Issue Type: Sub-task Reporter: Scott Aslan NiFi 1.x: !https://private-user-images.githubusercontent.com/713866/300824635-c3dd91cd-d1e3-4435-a061-c942d908db97.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDY2MjQ4OTIsIm5iZiI6MTcwNjYyNDU5MiwicGF0aCI6Ii83MTM4NjYvMzAwODI0NjM1LWMzZGQ5MWNkLWQxZTMtNDQzNS1hMDYxLWM5NDJkOTA4ZGI5Ny5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEzMFQxNDIzMTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03YjlmMTg3YmUyN2Q1NWZkMWQ4ZDk4OGYxZjAxZjA1Mjc1MTc3MzI4M2Y0ZTczZGEyNzk3NTYwODFjZmQ4YjAxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.3ugCkPl9mECLrZIG55Fla6ndlOzMKxq098dKqUIv-bw! New UI: !https://private-user-images.githubusercontent.com/713866/300824398-05fd832e-5051-458c-b0b5-0149dd203944.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDY2MjQ4OTIsIm5iZiI6MTcwNjYyNDU5MiwicGF0aCI6Ii83MTM4NjYvMzAwODI0Mzk4LTA1ZmQ4MzJlLTUwNTEtNDU4Yy1iMGI1LTAxNDlkZDIwMzk0NC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDEzMFQxNDIzMTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00MmJhZDVlNDA3NzM5NjZmZGJkNzMzMDAzNWNhMmIwZjQ4OGJiZDk3YzU0MTgzMWI0ZjA2MDc1NWFlODcyMjk3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.sweJ-smR0nptjUc0dOJkEqlP975WFrPAhVE9M2BxGYQ! Discussion: https://github.com/apache/nifi/pull/8294#discussion_r1471227264 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12686) Add Linting
Rob Fellows created NIFI-12686: -- Summary: Add Linting Key: NIFI-12686 URL: https://issues.apache.org/jira/browse/NIFI-12686 Project: Apache NiFi Issue Type: Sub-task Reporter: Rob Fellows Assignee: Rob Fellows -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12662) Conduct Apache NiFi 1.25.0 Release
[ https://issues.apache.org/jira/browse/NIFI-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812331#comment-17812331 ] ASF subversion and git services commented on NIFI-12662: Commit 6ecc398d3f92425447e43242af4992757e25b3c5 in nifi's branch refs/heads/support/nifi-1.x from Pierre Villard [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6ecc398d3f ] NIFI-12662-RC1 prepare release nifi-1.25.0-RC1 > Conduct Apache NiFi 1.25.0 Release > -- > > Key: NIFI-12662 > URL: https://issues.apache.org/jira/browse/NIFI-12662 > Project: Apache NiFi > Issue Type: Task >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > Fix For: 1.25.0 > > > Conduct Apache NiFi 1.25.0 Release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12662) Conduct Apache NiFi 1.25.0 Release
[ https://issues.apache.org/jira/browse/NIFI-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812333#comment-17812333 ] ASF subversion and git services commented on NIFI-12662: Commit b3297c55935b6d771498e55601ff74b6534da8fb in nifi's branch refs/heads/support/nifi-1.x from Pierre Villard [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b3297c5593 ] Merge branch 'NIFI-12662-RC1' into support/nifi-1.x > Conduct Apache NiFi 1.25.0 Release > -- > > Key: NIFI-12662 > URL: https://issues.apache.org/jira/browse/NIFI-12662 > Project: Apache NiFi > Issue Type: Task >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > Fix For: 1.25.0 > > > Conduct Apache NiFi 1.25.0 Release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12662) Conduct Apache NiFi 1.25.0 Release
[ https://issues.apache.org/jira/browse/NIFI-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812332#comment-17812332 ] ASF subversion and git services commented on NIFI-12662: Commit 65c33d08aac4a4563e030a515f13463dad8d4ee6 in nifi's branch refs/heads/support/nifi-1.x from Pierre Villard [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=65c33d08aa ] NIFI-12662-RC1 prepare for next development iteration > Conduct Apache NiFi 1.25.0 Release > -- > > Key: NIFI-12662 > URL: https://issues.apache.org/jira/browse/NIFI-12662 > Project: Apache NiFi > Issue Type: Task >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > Fix For: 1.25.0 > > > Conduct Apache NiFi 1.25.0 Release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12655) Better theme support
[ https://issues.apache.org/jira/browse/NIFI-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12655: --- Fix Version/s: 2.0.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Better theme support > > > Key: NIFI-12655 > URL: https://issues.apache.org/jira/browse/NIFI-12655 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Fix For: 2.0.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > The new ui is based on Angular Material components. We should follow the > [https://v16.material.angular.io/guide/theming] and > [https://v16.material.angular.io/guide/theming-your-components] guides as > well as the Material design color system: > [https://m2.material.io/design/color/the-color-system.html.|https://m2.material.io/design/color/the-color-system.html] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12655) Better theme support
[ https://issues.apache.org/jira/browse/NIFI-12655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812324#comment-17812324 ] ASF subversion and git services commented on NIFI-12655: Commit 8b2758cd185c67031129b26871d870582ed1df76 in nifi's branch refs/heads/main from Scott Aslan [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=8b2758cd18 ] [NIFI-12655] theme NiFi following Material Design spec and leveraging Angular Material themes (#8294) * [NIFI-12655] theme nifi following Material Design and leveraging Angular Material themes * update accent palette usage to $nifi-canvas-accent-light-palette * fix layout of create process group dialog This closes #8294 > Better theme support > > > Key: NIFI-12655 > URL: https://issues.apache.org/jira/browse/NIFI-12655 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > The new ui is based on Angular Material components. We should follow the > [https://v16.material.angular.io/guide/theming] and > [https://v16.material.angular.io/guide/theming-your-components] guides as > well as the Material design color system: > [https://m2.material.io/design/color/the-color-system.html.|https://m2.material.io/design/color/the-color-system.html] -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12655] theme NiFi following Material Design spec and leveraging Angular Material themes [nifi]
rfellows merged PR #8294: URL: https://github.com/apache/nifi/pull/8294 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] [NIFI-12655] theme NiFi following Material Design spec and leveraging Angular Material themes [nifi]
rfellows commented on code in PR #8294:
URL: https://github.com/apache/nifi/pull/8294#discussion_r1471257727
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/ui/common/status-history/_status-history.component-theme.scss:
##
@@ -0,0 +1,63 @@
+/*!
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+@use 'sass:map';
+@use '@angular/material' as mat;
+
+@mixin theme($material-theme, $canvas-theme) {
+// Get the color config from the theme.
+$color-config: mat.get-color-config($material-theme);
+$canvas-color-config: mat.get-color-config($canvas-theme);
+
+// Get the color palette from the color-config.
+$primary-palette: map.get($color-config, 'primary');
+$canvas-primary-palette: map.get($canvas-color-config, 'primary');
+
+// Get hues from palette
+$primary-palette-700: mat.get-color-from-palette($primary-palette, 700);
+$canvas-primary-palette-900:
mat.get-color-from-palette($canvas-primary-palette, 900);
+$canvas-primary-palette-A100:
mat.get-color-from-palette($canvas-primary-palette, 'A100');
+$canvas-primary-palette-A700:
mat.get-color-from-palette($canvas-primary-palette, 'A700');
+
+#status-history-chart-container,
+#status-history-chart-control-container {
+background-color: $canvas-primary-palette-900;
+
+.axis path,
+.axis line {
+fill: none;
+stroke: $canvas-primary-palette-A100;
Review Comment:
Let's just come back to this in the future. This PR is too big to keep
rebasing over and over.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] [NIFI-12655] theme NiFi following Material Design spec and leveraging Angular Material themes [nifi]
rfellows commented on code in PR #8294:
URL: https://github.com/apache/nifi/pull/8294#discussion_r1471227264
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/ui/common/status-history/_status-history.component-theme.scss:
##
@@ -0,0 +1,63 @@
+/*!
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+@use 'sass:map';
+@use '@angular/material' as mat;
+
+@mixin theme($material-theme, $canvas-theme) {
+// Get the color config from the theme.
+$color-config: mat.get-color-config($material-theme);
+$canvas-color-config: mat.get-color-config($canvas-theme);
+
+// Get the color palette from the color-config.
+$primary-palette: map.get($color-config, 'primary');
+$canvas-primary-palette: map.get($canvas-color-config, 'primary');
+
+// Get hues from palette
+$primary-palette-700: mat.get-color-from-palette($primary-palette, 700);
+$canvas-primary-palette-900:
mat.get-color-from-palette($canvas-primary-palette, 900);
+$canvas-primary-palette-A100:
mat.get-color-from-palette($canvas-primary-palette, 'A100');
+$canvas-primary-palette-A700:
mat.get-color-from-palette($canvas-primary-palette, 'A700');
+
+#status-history-chart-container,
+#status-history-chart-control-container {
+background-color: $canvas-primary-palette-900;
+
+.axis path,
+.axis line {
+fill: none;
+stroke: $canvas-primary-palette-A100;
Review Comment:
This translates into a transparent stroke for the chart axis lines
(invisible).
New UI, no x or y axis:
https://github.com/apache/nifi/assets/713866/05fd832e-5051-458c-b0b5-0149dd203944";>
Old UI, both x and y axis
https://github.com/apache/nifi/assets/713866/c3dd91cd-d1e3-4435-a061-c942d908db97";>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Created] (NIFI-12685) NiFi Cluster - java.net.SocketTimeoutException: timeout
Giovanni created NIFI-12685:
---
Summary: NiFi Cluster - java.net.SocketTimeoutException: timeout
Key: NIFI-12685
URL: https://issues.apache.org/jira/browse/NIFI-12685
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 1.22.0
Reporter: Giovanni
Attachments: image-2024-01-30-10-19-30-651.png
Hi,
I have a 3 nodes cluster and every time I try to edit a workflow one of the
nodes goes timeout and UI return the following error:
!image-2024-01-30-10-19-30-651.png!
At the same time one of the nodes reports the following log in the nifi-app.log:
{code:java}
2024-01-30 09:11:28,489 WARN [Replicate Request Thread-496]
o.a.n.c.c.h.r.ThreadPoolRequestReplicator
java.net.SocketTimeoutException: timeout
at okio.SocketAsyncTimeout.newTimeoutException(JvmOkio.kt:147)
at okio.AsyncTimeout.access$newTimeoutException(AsyncTimeout.kt:158)
at okio.AsyncTimeout$source$1.read(AsyncTimeout.kt:337)
at okio.RealBufferedSource.indexOf(RealBufferedSource.kt:427)
at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.kt:320)
at okhttp3.internal.http1.HeadersReader.readLine(HeadersReader.kt:29)
at
okhttp3.internal.http1.Http1ExchangeCodec.readResponseHeaders(Http1ExchangeCodec.kt:180)
at
okhttp3.internal.connection.Exchange.readResponseHeaders(Exchange.kt:110)
at
okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.kt:93)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at
okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:34)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at
okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at
okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at
okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
at okhttp3.internal.connection.RealCall.execute(RealCall.kt:154)
at
org.apache.nifi.cluster.coordination.http.replication.okhttp.OkHttpReplicationClient.replicate(OkHttpReplicationClient.java:136)
at
org.apache.nifi.cluster.coordination.http.replication.okhttp.OkHttpReplicationClient.replicate(OkHttpReplicationClient.java:130)
at
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator.replicateRequest(ThreadPoolRequestReplicator.java:645)
at
org.apache.nifi.cluster.coordination.http.replication.ThreadPoolRequestReplicator$NodeHttpRequest.run(ThreadPoolRequestReplicator.java:869)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.net.SocketException: Socket closed
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:183)
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
at
java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:484)
at
java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:478)
at
java.base/sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(SSLSocketInputRecord.java:70)
at
java.base/sun.security.ssl.SSLSocketImpl.readApplicationRecord(SSLSocketImpl.java:1455)
at
java.base/sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:1066)
at okio.InputStreamSource.read(JvmOkio.kt:94)
at okio.AsyncTimeout$source$1.read(AsyncTimeout.kt:125)
... 26 common frames omitted {code}
As I thought it was a performance issue, I doubled each nodes resources but the
error is still occurring.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
