Build failed in Jenkins: ManifoldCF-mvn #715

[Apache Jenkins Server]

See 


Changes:

[kwright] Another bit of CONNECTORS-1616.

[kwright] CONNECTORS-1616: Improve error reporting for confluence authority

--
[...truncated 436.88 KB...]
AUsite/src/documentation/resources/images/en_US/SecurityArchitecture.png
AUsite/src/documentation/resources/images/en_US/faq-list-summary.png
AU
site/src/documentation/resources/images/en_US/jcifs-job-file-mapping.PNG
AU
site/src/documentation/resources/images/en_US/sharepointnativeauthority-configure-cache.PNG
AUsite/src/documentation/resources/images/en_US/ldap-configure-ldap.PNG
AU
site/src/documentation/resources/images/en_US/add-new-notification-connection-name.PNG
AU
site/src/documentation/resources/images/en_US/elasticsearch-job-parameters.png
AU
site/src/documentation/resources/images/en_US/add-new-mapping-connection-type.PNG
AU
site/src/documentation/resources/images/en_US/hdfs-repository-configure-server.PNG
AU
site/src/documentation/resources/images/en_US/document-status-example.PNG
AUsite/src/documentation/resources/images/en_US/output-throttling.PNG
AU
site/src/documentation/resources/images/en_US/add-new-transformation-connection-name.PNG
AU
site/src/documentation/resources/images/en_US/documents-library-summary.png
AUsite/src/documentation/resources/images/en_US/solr-status.PNG
AU
site/src/documentation/resources/images/en_US/view-output-connection.PNG
AUsite/src/documentation/resources/images/en_US/rss-configure-proxy.PNG
AU
site/src/documentation/resources/images/en_US/cmis-repository-connection-configuration-save.png
AU
site/src/documentation/resources/images/en_US/meridio-connection-status.PNG
AU
site/src/documentation/resources/images/en_US/web-configure-access-credentials-session.PNG
AU
site/src/documentation/resources/images/en_US/tika-job-field-mapping.PNG
AU
site/src/documentation/resources/images/en_US/documentum-authority-user-mapping.PNG
AUsite/src/documentation/resources/images/en_US/rss-configure-email.PNG
AU
site/src/documentation/resources/images/en_US/meridio-connection-web-client.PNG
AUsite/src/documentation/resources/images/en_US/web-job-exclusions.PNG
AU
site/src/documentation/resources/images/en_US/queue-status-select-connection.PNG
AU
site/src/documentation/resources/images/en_US/alfresco-repository-connection-job-lucenequery.png
AUsite/src/documentation/resources/images/en_US/web-job-hop-filters.PNG
AU
site/src/documentation/resources/images/en_US/googledrive-repository-setup-2.PNG
AU
site/src/documentation/resources/images/en_US/jcifs-configure-server.PNG
AU
site/src/documentation/resources/images/en_US/list-authority-connections.PNG
AU
site/src/documentation/resources/images/en_US/googledrive-repository-setup-4.PNG
AUsite/src/documentation/resources/images/en_US/email-job-filter.PNG
AU
site/src/documentation/resources/images/en_US/filesystem-job-output-path.PNG
AU
site/src/documentation/resources/images/en_US/list-mapping-connections.PNG
AU
site/src/documentation/resources/images/en_US/jdbc-configure-server.PNG
AU
site/src/documentation/resources/images/en_US/googledrive-repository-connection-configuration.PNG
AUsite/src/documentation/resources/images/en_US/alfresco-connector.png
AU
site/src/documentation/resources/images/en_US/wiki-configure-server.PNG
AU
site/src/documentation/resources/images/en_US/opensearchserver-history-report.PNG
AUsite/src/documentation/resources/images/en_US/mapping-throttling.PNG
AU
site/src/documentation/resources/images/en_US/documents-library-all-metadata.png
AU
site/src/documentation/resources/images/en_US/add-new-output-connection-name.PNG
AU
site/src/documentation/resources/images/en_US/cmis-repository-connection-job-cmisquery.png
AU
site/src/documentation/resources/images/en_US/livelink-connection-document-view.PNG
AU
site/src/documentation/resources/images/en_US/meridio-authority-document-server.PNG
AU
site/src/documentation/resources/images/en_US/view-mapping-connection.PNG
AUsite/src/documentation/resources/images/en_US/documentum-status.PNG
AU
site/src/documentation/resources/images/en_US/transformation-throttling.PNG
AU
site/src/documentation/resources/images/en_US/documents-library-path-rule.png
AU
site/src/documentation/resources/images/en_US/jdbc-configure-database-type.PNG
AUsite/src/documentation/resources/images/en_US/web-job-metadata.PNG
AU
site/src/documentation/resources/images/en_US/regexp-mapping-status.PNG
AU
site/src/documentation/resources/images/en_US/faq-list-all-metadata.png
AU

[jira] [Assigned] (CONNECTORS-1616) Confluence Authority does not handle Confluence API errors

[Karl Wright (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CONNECTORS-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Wright reassigned CONNECTORS-1616:
---

   Resolution: Fixed
 Assignee: Karl Wright
Fix Version/s: (was: ManifoldCF 2.12)
   ManifoldCF 2.14

> Confluence Authority does not handle Confluence API errors
> --
>
> Key: CONNECTORS-1616
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1616
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Confluence connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Julien Massiera
>Assignee: Karl Wright
>Priority: Critical
> Fix For: ManifoldCF 2.14
>
> Attachments: patch-CONNECTORS-1616.diff
>
>
> The Confluence Authority asks spaces permissions for each space returned by 
> the getSpaces() method of the ConfluenceClient class.
>  The concerned method getSpacePermissionsForUser(Space space, String 
> username) sends a request to Confluence and triggers a ConfluenceException if 
> the request response is different from 200, otherwise it parses the response 
> as a JSONArray to get the permissions.
> The problem is that even with a 200 request response code, the content of the 
> response may be a simple JSONObject that explains an internal Confluence 
> error. It happens frequently when the username is not allowed to get 
> permissions on certain spaces :
> {code:java}
> {
> "id": null,
> "error": {
> "code": 500,
> "message": "The application was unable to serve your request: 
> com.atlassian.confluence.rpc.NotPermittedException: Only space administrators 
> can view permissions for other users in the space.",
> "data": "com.atlassian.confluence.rpc.NotPermittedException: Only space 
> administrators can view permissions for other users in the 
> space.\ncom.atlassian.confluence.rpc.NotPermittedException: Only space 
> administrators can view permissions for other users in the space.\n\tat 
> com.atlassian.confluence.rpc.soap.services.SpacesSoapService.getPermissions(SpacesSoapService.java:188)\n\tat
>  
> com.atlassian.confluence.rpc.soap.XhtmlSoapService.getPermissionsForUser(XhtmlSoapService.java:226)\n\tat
>  sun.reflect.GeneratedMethodAccessor3812.invoke(Unknown Source)\n\tat 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:498)\n\tat"
> }
> }
> {code}
> As a username will almost never have the rights to get permissions on ALL 
> spaces, it is problematic because the response parsing process triggers an 
> Exception and so the Confluence Authority response is 
> UNREACHABLEAUTHORITY:confluence, instead of delivering permissions for 
> allowed spaces.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Comment Edited] (CONNECTORS-1616) Confluence Authority does not handle Confluence API errors

[Julien Massiera (JIRA)]

[ 
https://issues.apache.org/jira/browse/CONNECTORS-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897978#comment-16897978
 ] 

Julien Massiera edited comment on CONNECTORS-1616 at 8/1/19 11:05 AM:
--

I would agree with you but as I said in the comment it is IMPOSSIBLE to give a 
user to the authority that have sufficient rights to get individual permissions 
for all spaces. 
 It was the first thing I asked to the administrator of the target Confluence. 
He said that, at least for Confluence v6, it is impossible even for a 
Confluence admin to get permissions for all spaces and it is also impossible to 
manually force a user as admin to all spaces. It is a Confluence security 
restriction.
 So what should we do ? Well to have a user that have sufficient permissions to 
all spaces you need to ask to each space owner to add in the space admin list 
the user configured in the authority (which is an admin user to be clear). It 
may be possible if you have a Confluence site with just few spaces and like 10 
space owners but for a Confluence site with hundred/thousand of spaces and 
hundred of different space owners ? And even, what if some space owners simply 
do not want to add the user as an admin of their space(s) ?
 So the use case here is : I have an authority user that will NEVER have rights 
to get permissions on all spaces but the authority connector should still work 
and provide permissions for at least the spaces on which the authority user is 
allowed to get them. And we spread the info to the space owners that if they 
want their data to be accessible, they have to add the authority user as an 
admin user of their space(s)
 So without this patch and in the current state, this connector is utterly 
useless in a production environment as the authority will never return any 
permissions (cause at the fist space encountered on which the authority cannot 
get permissions, the exception is thrown and the response will be UNREACHABLE) 
and so it is not possible to display any Confluence data crawled by MCF if the 
security is activated...  


was (Author: julienfl):
I would agree with you but as I said in the comment it is IMPOSSIBLE to give a 
user to the authority that have sufficient rights to get individual permissions 
for all spaces. 
It was the first thing I asked to the administrator of the target Confluence. 
He said that, at least for Confluence v6, it is impossible even for a 
Confluence admin to get permissions for all spaces and it is also impossible to 
manually force a user as admin to all spaces. It is a Confluence security 
restriction.
So what should we do ? Well to have a user that have sufficient permissions to 
all spaces you need to ask to each space owner to add in the space admin list 
the user configured in the authority (which is an admin user to be clear). It 
is may be possible if you have a Confluence site with just few spaces and like 
10 space owners but for a Confluence site with hundred/thousand of spaces and 
hundred of different space owners ? And even, what if some space owners simply 
do not want to add the user as an admin of their space(s) ?
So the use case here is : I have an authority user that will NEVER have rights 
to get permissions on all spaces but the authority connector should still work 
and provide permissions for at least the spaces on which the authority user is 
allowed to get them. And we spread the info to the space owners that if they 
want their data to be accessible, they have to add the authority user as an 
admin user of their space(s)
So without this patch and in the current state, this connector is utterly 
useless in a production environment as the authority will never return any 
permissions (cause at the fist space encountered on which the authority cannot 
get permissions, the exception is thrown and the response will be UNREACHABLE) 
and so it is not possible to display any Confluence data crawled by MCF if the 
security is activated...  

> Confluence Authority does not handle Confluence API errors
> --
>
> Key: CONNECTORS-1616
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1616
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Confluence connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Julien Massiera
>Priority: Critical
> Fix For: ManifoldCF 2.12
>
> Attachments: patch-CONNECTORS-1616.diff
>
>
> The Confluence Authority asks spaces permissions for each space returned by 
> the getSpaces() method of the ConfluenceClient class.
>  The concerned method getSpacePermissionsForUser(Space space, String 
> username) sends a request to Confluence and triggers a ConfluenceException if 
> the request response is different from 200, otherwise it parses the 

[jira] [Commented] (CONNECTORS-1616) Confluence Authority does not handle Confluence API errors

[Julien Massiera (JIRA)]

[ 
https://issues.apache.org/jira/browse/CONNECTORS-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897978#comment-16897978
 ] 

Julien Massiera commented on CONNECTORS-1616:
-

I would agree with you but as I said in the comment it is IMPOSSIBLE to give a 
user to the authority that have sufficient rights to get individual permissions 
for all spaces. 
It was the first thing I asked to the administrator of the target Confluence. 
He said that, at least for Confluence v6, it is impossible even for a 
Confluence admin to get permissions for all spaces and it is also impossible to 
manually force a user as admin to all spaces. It is a Confluence security 
restriction.
So what should we do ? Well to have a user that have sufficient permissions to 
all spaces you need to ask to each space owner to add in the space admin list 
the user configured in the authority (which is an admin user to be clear). It 
is may be possible if you have a Confluence site with just few spaces and like 
10 space owners but for a Confluence site with hundred/thousand of spaces and 
hundred of different space owners ? And even, what if some space owners simply 
do not want to add the user as an admin of their space(s) ?
So the use case here is : I have an authority user that will NEVER have rights 
to get permissions on all spaces but the authority connector should still work 
and provide permissions for at least the spaces on which the authority user is 
allowed to get them. And we spread the info to the space owners that if they 
want their data to be accessible, they have to add the authority user as an 
admin user of their space(s)
So without this patch and in the current state, this connector is utterly 
useless in a production environment as the authority will never return any 
permissions (cause at the fist space encountered on which the authority cannot 
get permissions, the exception is thrown and the response will be UNREACHABLE) 
and so it is not possible to display any Confluence data crawled by MCF if the 
security is activated...  

> Confluence Authority does not handle Confluence API errors
> --
>
> Key: CONNECTORS-1616
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1616
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Confluence connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Julien Massiera
>Priority: Critical
> Fix For: ManifoldCF 2.12
>
> Attachments: patch-CONNECTORS-1616.diff
>
>
> The Confluence Authority asks spaces permissions for each space returned by 
> the getSpaces() method of the ConfluenceClient class.
>  The concerned method getSpacePermissionsForUser(Space space, String 
> username) sends a request to Confluence and triggers a ConfluenceException if 
> the request response is different from 200, otherwise it parses the response 
> as a JSONArray to get the permissions.
> The problem is that even with a 200 request response code, the content of the 
> response may be a simple JSONObject that explains an internal Confluence 
> error. It happens frequently when the username is not allowed to get 
> permissions on certain spaces :
> {code:java}
> {
> "id": null,
> "error": {
> "code": 500,
> "message": "The application was unable to serve your request: 
> com.atlassian.confluence.rpc.NotPermittedException: Only space administrators 
> can view permissions for other users in the space.",
> "data": "com.atlassian.confluence.rpc.NotPermittedException: Only space 
> administrators can view permissions for other users in the 
> space.\ncom.atlassian.confluence.rpc.NotPermittedException: Only space 
> administrators can view permissions for other users in the space.\n\tat 
> com.atlassian.confluence.rpc.soap.services.SpacesSoapService.getPermissions(SpacesSoapService.java:188)\n\tat
>  
> com.atlassian.confluence.rpc.soap.XhtmlSoapService.getPermissionsForUser(XhtmlSoapService.java:226)\n\tat
>  sun.reflect.GeneratedMethodAccessor3812.invoke(Unknown Source)\n\tat 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:498)\n\tat"
> }
> }
> {code}
> As a username will almost never have the rights to get permissions on ALL 
> spaces, it is problematic because the response parsing process triggers an 
> Exception and so the Confluence Authority response is 
> UNREACHABLEAUTHORITY:confluence, instead of delivering permissions for 
> allowed spaces.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Commented] (CONNECTORS-1616) Confluence Authority does not handle Confluence API errors

[Karl Wright (JIRA)]

[ 
https://issues.apache.org/jira/browse/CONNECTORS-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897946#comment-16897946
 ] 

Karl Wright commented on CONNECTORS-1616:
-

So, the issue here is that you are giving the authority insufficient 
permissions to be able to get individual user permissions.  You can't fix that 
by simply ignoring it.  I don't understand, therefore, why you expect this 
patch to solve anything for you.  It seems to me like it would just obscure the 
fact that you are configuring a user without admin privs.


> Confluence Authority does not handle Confluence API errors
> --
>
> Key: CONNECTORS-1616
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1616
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Confluence connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Julien Massiera
>Priority: Critical
> Fix For: ManifoldCF 2.12
>
> Attachments: patch-CONNECTORS-1616.diff
>
>
> The Confluence Authority asks spaces permissions for each space returned by 
> the getSpaces() method of the ConfluenceClient class.
>  The concerned method getSpacePermissionsForUser(Space space, String 
> username) sends a request to Confluence and triggers a ConfluenceException if 
> the request response is different from 200, otherwise it parses the response 
> as a JSONArray to get the permissions.
> The problem is that even with a 200 request response code, the content of the 
> response may be a simple JSONObject that explains an internal Confluence 
> error. It happens frequently when the username is not allowed to get 
> permissions on certain spaces :
> {code:java}
> {
> "id": null,
> "error": {
> "code": 500,
> "message": "The application was unable to serve your request: 
> com.atlassian.confluence.rpc.NotPermittedException: Only space administrators 
> can view permissions for other users in the space.",
> "data": "com.atlassian.confluence.rpc.NotPermittedException: Only space 
> administrators can view permissions for other users in the 
> space.\ncom.atlassian.confluence.rpc.NotPermittedException: Only space 
> administrators can view permissions for other users in the space.\n\tat 
> com.atlassian.confluence.rpc.soap.services.SpacesSoapService.getPermissions(SpacesSoapService.java:188)\n\tat
>  
> com.atlassian.confluence.rpc.soap.XhtmlSoapService.getPermissionsForUser(XhtmlSoapService.java:226)\n\tat
>  sun.reflect.GeneratedMethodAccessor3812.invoke(Unknown Source)\n\tat 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:498)\n\tat"
> }
> }
> {code}
> As a username will almost never have the rights to get permissions on ALL 
> spaces, it is problematic because the response parsing process triggers an 
> Exception and so the Confluence Authority response is 
> UNREACHABLEAUTHORITY:confluence, instead of delivering permissions for 
> allowed spaces.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Commented] (CONNECTORS-1616) Confluence Authority does not handle Confluence API errors

[Karl Wright (JIRA)]

[ 
https://issues.apache.org/jira/browse/CONNECTORS-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897940#comment-16897940
 ] 

Karl Wright commented on CONNECTORS-1616:
-

Ok, there are some problems with it.  Why did you remove stream parsing for the 
JSON?  I'll have to edit.


> Confluence Authority does not handle Confluence API errors
> --
>
> Key: CONNECTORS-1616
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1616
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Confluence connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Julien Massiera
>Priority: Critical
> Fix For: ManifoldCF 2.12
>
> Attachments: patch-CONNECTORS-1616.diff
>
>
> The Confluence Authority asks spaces permissions for each space returned by 
> the getSpaces() method of the ConfluenceClient class.
>  The concerned method getSpacePermissionsForUser(Space space, String 
> username) sends a request to Confluence and triggers a ConfluenceException if 
> the request response is different from 200, otherwise it parses the response 
> as a JSONArray to get the permissions.
> The problem is that even with a 200 request response code, the content of the 
> response may be a simple JSONObject that explains an internal Confluence 
> error. It happens frequently when the username is not allowed to get 
> permissions on certain spaces :
> {code:java}
> {
> "id": null,
> "error": {
> "code": 500,
> "message": "The application was unable to serve your request: 
> com.atlassian.confluence.rpc.NotPermittedException: Only space administrators 
> can view permissions for other users in the space.",
> "data": "com.atlassian.confluence.rpc.NotPermittedException: Only space 
> administrators can view permissions for other users in the 
> space.\ncom.atlassian.confluence.rpc.NotPermittedException: Only space 
> administrators can view permissions for other users in the space.\n\tat 
> com.atlassian.confluence.rpc.soap.services.SpacesSoapService.getPermissions(SpacesSoapService.java:188)\n\tat
>  
> com.atlassian.confluence.rpc.soap.XhtmlSoapService.getPermissionsForUser(XhtmlSoapService.java:226)\n\tat
>  sun.reflect.GeneratedMethodAccessor3812.invoke(Unknown Source)\n\tat 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:498)\n\tat"
> }
> }
> {code}
> As a username will almost never have the rights to get permissions on ALL 
> spaces, it is problematic because the response parsing process triggers an 
> Exception and so the Confluence Authority response is 
> UNREACHABLEAUTHORITY:confluence, instead of delivering permissions for 
> allowed spaces.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Commented] (CONNECTORS-1616) Confluence Authority does not handle Confluence API errors

[Julien Massiera (JIRA)]

[ 
https://issues.apache.org/jira/browse/CONNECTORS-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897851#comment-16897851
 ] 

Julien Massiera commented on CONNECTORS-1616:
-

[~kwri...@metacarta.com], patch is available

> Confluence Authority does not handle Confluence API errors
> --
>
> Key: CONNECTORS-1616
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1616
> Project: ManifoldCF
>  Issue Type: Bug
>  Components: Confluence connector
>Affects Versions: ManifoldCF 2.12
>Reporter: Julien Massiera
>Priority: Critical
> Fix For: ManifoldCF 2.12
>
> Attachments: patch-CONNECTORS-1616.diff
>
>
> The Confluence Authority asks spaces permissions for each space returned by 
> the getSpaces() method of the ConfluenceClient class.
>  The concerned method getSpacePermissionsForUser(Space space, String 
> username) sends a request to Confluence and triggers a ConfluenceException if 
> the request response is different from 200, otherwise it parses the response 
> as a JSONArray to get the permissions.
> The problem is that even with a 200 request response code, the content of the 
> response may be a simple JSONObject that explains an internal Confluence 
> error. It happens frequently when the username is not allowed to get 
> permissions on certain spaces :
> {code:java}
> {
> "id": null,
> "error": {
> "code": 500,
> "message": "The application was unable to serve your request: 
> com.atlassian.confluence.rpc.NotPermittedException: Only space administrators 
> can view permissions for other users in the space.",
> "data": "com.atlassian.confluence.rpc.NotPermittedException: Only space 
> administrators can view permissions for other users in the 
> space.\ncom.atlassian.confluence.rpc.NotPermittedException: Only space 
> administrators can view permissions for other users in the space.\n\tat 
> com.atlassian.confluence.rpc.soap.services.SpacesSoapService.getPermissions(SpacesSoapService.java:188)\n\tat
>  
> com.atlassian.confluence.rpc.soap.XhtmlSoapService.getPermissionsForUser(XhtmlSoapService.java:226)\n\tat
>  sun.reflect.GeneratedMethodAccessor3812.invoke(Unknown Source)\n\tat 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:498)\n\tat"
> }
> }
> {code}
> As a username will almost never have the rights to get permissions on ALL 
> spaces, it is problematic because the response parsing process triggers an 
> Exception and so the Confluence Authority response is 
> UNREACHABLEAUTHORITY:confluence, instead of delivering permissions for 
> allowed spaces.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)