[jira] [Commented] (NIFI-5) Add details to reason messages of standard validators
[ https://issues.apache.org/jira/browse/NIFI-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999706#comment-15999706 ] Andre F de Miranda commented on NIFI-5: --- [~joewitt] No sure I am reading this right but I have the impression this JIRA has been addressed already? Currently if we have multiple different properties, the UI will mention what particular property is invalid. Cheers > Add details to reason messages of standard validators > - > > Key: NIFI-5 > URL: https://issues.apache.org/jira/browse/NIFI-5 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Joseph Witt >Assignee: Andre F de Miranda >Priority: Minor > > The reason messages for the standard validators are vague and make it > difficult for admins/DFMs to diagnose certain problems. For intance, when > one of our processors has properties for two or three directories. If only > one does not exist it just says 'directory does not exist' but doesn't > indicate which property that was for. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-871) Site-to-Site does not report the actual hostname that it was trying to connect to when it fails to connect
[ https://issues.apache.org/jira/browse/NIFI-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999704#comment-15999704 ] Andre F de Miranda commented on NIFI-871: - [~markap14] Ping? > Site-to-Site does not report the actual hostname that it was trying to > connect to when it fails to connect > -- > > Key: NIFI-871 > URL: https://issues.apache.org/jira/browse/NIFI-871 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Mark Payne >Assignee: Andre F de Miranda > > In testing the patch provided for NIFI-868, I set the nifi properties to > advertise the hostname as "otherhost". Site-to-Site, of course, failed to > connect, but rather indicating that it could not connect to otherhost, it > simply indicated that it was the RemoteProcessGroup connected to > http://localhost:8080/nifi. This is misleading because it leads the user to > believe that the Remote Process Group is having trouble connecting to > localhost, when in reality it is attempting to connect to "otherhost". We > should indicate which host we are connecting to when providing an error like > this. > 2015-08-19 13:03:46,083 WARN [Timer-Driven Process Thread-10] > o.a.n.c.t.ContinuallyRunConnectableTask > RemoteGroupPort[name=in,target=http://localhost:8080/nifi] Administratively > Pausing for 10 seconds due to processing failure: java.lang.RuntimeException: > java.nio.channels.UnresolvedAddressException > java.lang.RuntimeException: java.nio.channels.UnresolvedAddressException > at > org.apache.nifi.controller.AbstractPort.onTrigger(AbstractPort.java:234) > ~[nifi-framework-core-api-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.tasks.ContinuallyRunConnectableTask.call(ContinuallyRunConnectableTask.java:80) > [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.tasks.ContinuallyRunConnectableTask.call(ContinuallyRunConnectableTask.java:40) > [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:119) > [nifi-framework-core-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [na:1.8.0_51] > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > [na:1.8.0_51] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > [na:1.8.0_51] > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > [na:1.8.0_51] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_51] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_51] > at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51] > Caused by: java.nio.channels.UnresolvedAddressException: null > at sun.nio.ch.Net.checkAddress(Net.java:123) ~[na:1.8.0_51] > at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:622) > ~[na:1.8.0_51] > at java.nio.channels.SocketChannel.open(SocketChannel.java:189) > ~[na:1.8.0_51] > at > org.apache.nifi.remote.client.socket.EndpointConnectionPool.establishSiteToSiteConnection(EndpointConnectionPool.java:708) > ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.remote.client.socket.EndpointConnectionPool.establishSiteToSiteConnection(EndpointConnectionPool.java:682) > ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.remote.client.socket.EndpointConnectionPool.getEndpointConnection(EndpointConnectionPool.java:300) > ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.remote.client.socket.SocketClient.createTransaction(SocketClient.java:129) > ~[nifi-site-to-site-client-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.remote.StandardRemoteGroupPort.onTrigger(StandardRemoteGroupPort.java:167) > ~[nifi-site-to-site-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > at > org.apache.nifi.controller.AbstractPort.onTrigger(AbstractPort.java:227) > ~[nifi-framework-core-api-0.3.0-SNAPSHOT.jar:0.3.0-SNAPSHOT] > ... 10 common frames omitted -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-439) Documentation should reflect that a component has been deprecated
[ https://issues.apache.org/jira/browse/NIFI-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre F de Miranda updated NIFI-439: Resolution: Fixed Status: Resolved (was: Patch Available) This is being implemented as part NIFI-391 > Documentation should reflect that a component has been deprecated > - > > Key: NIFI-439 > URL: https://issues.apache.org/jira/browse/NIFI-439 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Documentation & Website >Reporter: Dan Bress >Assignee: Andre F de Miranda > > If a component becomes deprecated, the generated html documentation for that > component should reflect that, and inform the user what other components they > should be using instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-391) Need ability to deprecate components
[ https://issues.apache.org/jira/browse/NIFI-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre F de Miranda updated NIFI-391: Status: Patch Available (was: In Progress) > Need ability to deprecate components > > > Key: NIFI-391 > URL: https://issues.apache.org/jira/browse/NIFI-391 > Project: Apache NiFi > Issue Type: New Feature > Components: Core Framework, Core UI, Extensions >Reporter: Mark Payne >Assignee: Andre F de Miranda > > The API should allow processors to be marked as deprecated such that the UI > then shows on the graph that the Processor is deprecated. > Additionally, the UI should show in the Status Bar that there are deprecated > components (processors, reporting tasks, controller services) in the flow. > This valuable because of improvements such as NIFI-377. In this case, we have > a community member making the Base64EncodeContent processor more generic so > that it can encode/decode base 16,32, and 64. At this point, > Base64EncodeContent doesn't make sense as a name, so there is a more generic > EncodeContent processor. We don't need both, so we want to deprecated the > Base64EncodeContent processor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-439) Documentation should reflect that a component has been deprecated
[ https://issues.apache.org/jira/browse/NIFI-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre F de Miranda updated NIFI-439: Status: Patch Available (was: In Progress) > Documentation should reflect that a component has been deprecated > - > > Key: NIFI-439 > URL: https://issues.apache.org/jira/browse/NIFI-439 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Documentation & Website >Reporter: Dan Bress >Assignee: Andre F de Miranda > > If a component becomes deprecated, the generated html documentation for that > component should reflect that, and inform the user what other components they > should be using instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-391) Need ability to deprecate components
[ https://issues.apache.org/jira/browse/NIFI-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999684#comment-15999684 ] ASF GitHub Bot commented on NIFI-391: - Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/1718 @mcgilman based on the following screenshot( this is a snipped of data related to a locally deprecated `ListenLumberjack`) I suspect this should be a good starting point for the UX work (I've left anything but documentation untouched).  Please let me know if I missed something. > Need ability to deprecate components > > > Key: NIFI-391 > URL: https://issues.apache.org/jira/browse/NIFI-391 > Project: Apache NiFi > Issue Type: New Feature > Components: Core Framework, Core UI, Extensions >Reporter: Mark Payne >Assignee: Andre F de Miranda > > The API should allow processors to be marked as deprecated such that the UI > then shows on the graph that the Processor is deprecated. > Additionally, the UI should show in the Status Bar that there are deprecated > components (processors, reporting tasks, controller services) in the flow. > This valuable because of improvements such as NIFI-377. In this case, we have > a community member making the Base64EncodeContent processor more generic so > that it can encode/decode base 16,32, and 64. At this point, > Base64EncodeContent doesn't make sense as a name, so there is a more generic > EncodeContent processor. We don't need both, so we want to deprecated the > Base64EncodeContent processor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] nifi issue #1718: NIFI-391 - Introduce the ability to deprecate a component
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/1718 @mcgilman based on the following screenshot( this is a snipped of data related to a locally deprecated `ListenLumberjack`) I suspect this should be a good starting point for the UX work (I've left anything but documentation untouched).  Please let me know if I missed something. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-3830) Clicking on any component on Linux causes %3F to continuously be added to beginning of query string
[ https://issues.apache.org/jira/browse/NIFI-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3830: -- Attachment: malformed query string.png > Clicking on any component on Linux causes %3F to continuously be added to > beginning of query string > --- > > Key: NIFI-3830 > URL: https://issues.apache.org/jira/browse/NIFI-3830 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Linux > Firefox & Chromium >Reporter: Aldrin Piri >Priority: Minor > Attachments: malformed query string.png > > > In Debian across both Firefox and Chromium, selecting a component causes > another %3F (encoded ?) to be prepended to the query string after the > original ?. > The URL remains the same until moving up the hierarchy (exiting a process > group). The UI and URL is still functional but imagine it might cause > problems should this cause the URL to exceed max length. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3830) Clicking on any component on Linux causes %3F to continuously be added to beginning of query string
Aldrin Piri created NIFI-3830: - Summary: Clicking on any component on Linux causes %3F to continuously be added to beginning of query string Key: NIFI-3830 URL: https://issues.apache.org/jira/browse/NIFI-3830 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.2.0 Environment: Linux Firefox & Chromium Reporter: Aldrin Piri Priority: Minor In Debian across both Firefox and Chromium, selecting a component causes another %3F (encoded ?) to be prepended to the query string after the original ?. The URL remains the same until moving up the hierarchy (exiting a process group). The UI and URL is still functional but imagine it might cause problems should this cause the URL to exceed max length. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3829) Processor has visual defect and shows canvas
[ https://issues.apache.org/jira/browse/NIFI-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3829: -- Attachment: transparent processor info.png > Processor has visual defect and shows canvas > > > Key: NIFI-3829 > URL: https://issues.apache.org/jira/browse/NIFI-3829 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Debian Stretch > Firefox 41.4 >Reporter: Aldrin Piri >Priority: Trivial > Attachments: transparent processor info.png > > > In Debian on Firefox (Chrome/Chromium seems unaffected as well as on OS X and > Windows), a processor after being placed on the canvas and then subsequently > moved, causes the background behind the processor name, version, NAR > disappears and allows the canvas to show through. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3829) Processor has visual defect and shows canvas
Aldrin Piri created NIFI-3829: - Summary: Processor has visual defect and shows canvas Key: NIFI-3829 URL: https://issues.apache.org/jira/browse/NIFI-3829 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.2.0 Environment: Debian Stretch Firefox 41.4 Reporter: Aldrin Piri Priority: Trivial In Debian on Firefox (Chrome/Chromium seems unaffected as well as on OS X and Windows), a processor after being placed on the canvas and then subsequently moved, causes the background behind the processor name, version, NAR disappears and allows the canvas to show through. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] nifi-minifi-cpp pull request #94: MINIFI-302 Exclude generated docs from the...
GitHub user apiri opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/94 MINIFI-302 Exclude generated docs from the source tarball MINIFI-302 Exclude generated docs from the source tarball via CPack ignore. You can merge this pull request into a Git repository by running: $ git pull https://github.com/apiri/nifi-minifi-cpp MINIFI-302 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/94.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #94 commit 8f0f53283562cb6418174c559132bf6378ca1d76 Author: Aldrin Piri Date: 2017-05-07T04:29:54Z MINIFI-302 Exclude generated docs from the source tarball via CPack ignore. Signed-off-by: Aldrin Piri --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi-minifi-cpp pull request #93: MINIFI-301 Removing extraneous third party...
Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi-cpp/pull/93 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi-minifi-cpp issue #93: MINIFI-301 Removing extraneous third party resour...
Github user benqiu2016 commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/93 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi-minifi-cpp pull request #92: MINIFI-299: Update Readme.
Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi-cpp/pull/92 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi-minifi-cpp issue #92: MINIFI-299: Update Readme.
Github user apiri commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/92 These changes look good. Thanks for taking the time to update. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi-minifi-cpp issue #92: MINIFI-299: Update Readme.
Github user apiri commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/92 reviewing --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi-minifi-cpp pull request #93: MINIFI-301 Removing extraneous third party...
GitHub user apiri opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/93 MINIFI-301 Removing extraneous third party resources MINIFI-301 Removing extraneous third party resources from the project source tree. You can merge this pull request into a Git repository by running: $ git pull https://github.com/apiri/nifi-minifi-cpp MINIFI-301 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/93.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #93 commit a830fd45d04e98e250d6e30176c07b3b3ecdfb6d Author: Aldrin Piri Date: 2017-05-06T19:04:49Z MINIFI-301 Removing extraneous third party resources from the project source tree. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-3770) Perform Release Manager duties for 1.2.0 Release
[ https://issues.apache.org/jira/browse/NIFI-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999511#comment-15999511 ] Bryan Bende commented on NIFI-3770: --- [~joewitt] go for it, totally open to editing/formatting/etc. > Perform Release Manager duties for 1.2.0 Release > > > Key: NIFI-3770 > URL: https://issues.apache.org/jira/browse/NIFI-3770 > Project: Apache NiFi > Issue Type: Task >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: 1.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3770) Perform Release Manager duties for 1.2.0 Release
[ https://issues.apache.org/jira/browse/NIFI-3770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999493#comment-15999493 ] Joseph Witt commented on NIFI-3770: --- [~bbende] do you mind if I do some editing of the release notes? Would like to make them a bit higher level. > Perform Release Manager duties for 1.2.0 Release > > > Key: NIFI-3770 > URL: https://issues.apache.org/jira/browse/NIFI-3770 > Project: Apache NiFi > Issue Type: Task >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: 1.2.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3828) Fix for NIFI-3776 prevents mock processor documentation from rendering properly
Andre F de Miranda created NIFI-3828:
Summary: Fix for NIFI-3776 prevents mock processor documentation
from rendering properly
Key: NIFI-3828
URL: https://issues.apache.org/jira/browse/NIFI-3828
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Andre F de Miranda
Priority: Minor
Because the mock {{FullyDocumentedControllerService}},
{{FullyDocumentedReportingTask}} and {{ExampleProcessor}} are not identified by
the introduce bundles related syntax, the test units struggle to create links
to the mock processors.
{code}
[main] WARN org.apache.nifi.documentation.html.HtmlDocumentationWriter - Could
not link to
org.apache.nifi.documentation.example.FullyDocumentedControllerService because
no bundles were found
[main] WARN org.apache.nifi.documentation.html.HtmlDocumentationWriter - Could
not link to org.apache.nifi.documentation.example.FullyDocumentedReportingTask
because no bundles were found
[main] WARN org.apache.nifi.documentation.html.HtmlDocumentationWriter - Could
not link to org.apache.nifi.processor.ExampleProcessor because no bundles were
found
[main] INFO org.apache.nifi.mock.MockComponentLogger - Initializing...
{code}
While the impact is negligible and isn't negative to the build, this new
behavior is different from the previously existing behavior where the mock
processors would render their documentation identically to what a normal
processor would.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (NIFI-3827) GeoIP database may route to mach when IP is identified as an anonymous proxy
Andre F de Miranda created NIFI-3827: Summary: GeoIP database may route to mach when IP is identified as an anonymous proxy Key: NIFI-3827 URL: https://issues.apache.org/jira/browse/NIFI-3827 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.1.1, 0.6.1, 1.2.0 Reporter: Andre F de Miranda Assignee: Andre F de Miranda When IP is listed in the MaxMind GeoIP database but is marked as an anonymous proxy it may be treated as a match but lack any details on why the match occurred (it will have not latitude, longitude, country, city or similar data) Whenever matches occur due to existence of traits we should add attributes to the flowfile so the users can identify the reason for the match -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (NIFI-2008) GeoEnrichIP - Routing IPs with Null attributes as Found
[ https://issues.apache.org/jira/browse/NIFI-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre F de Miranda resolved NIFI-2008. -- Resolution: Won't Fix [~randy_b] I had time to validate the behavior and it seems like it seems indeed to be caused by anonymous proxies lacking country but having matches within the database. I agree with [~pvillard] point that given the data is indeed contained within the database we should close this ticket as Won't Fix. I will also create a new one to track the addition of an attribute in case the MaxMind DB indicates the site is an anonymous proxy. > GeoEnrichIP - Routing IPs with Null attributes as Found > --- > > Key: NIFI-2008 > URL: https://issues.apache.org/jira/browse/NIFI-2008 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 0.6.1 >Reporter: Randy Bovay >Assignee: Andre F de Miranda > > I have an IP that is being found in the MaxMind database, but has no values > returned. (See below to check yourself) > NiFi is routing this to 'found', but since there are no Attributes populated, > I cannot work with the return values. > IP: 216.151.180.197 > https://www.maxmind.com/en/geoip-demo -- This message was sent by Atlassian JIRA (v6.3.15#6346)
