[JBoss JIRA] (JBIDE-23125) CDK server adapter: NPE when trying to find cdk connection
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23125?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23125.
---------------------------------
Closing. I haven't seen this myself. Please reopen should this happen again.
> CDK server adapter: NPE when trying to find cdk connection
> ----------------------------------------------------------
>
> Key: JBIDE-23125
> URL: https://issues.jboss.org/browse/JBIDE-23125
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
>
> This was automatically reproted in aeri https://redhat.ctrlflow.com/reviewers#!/problems/57c68f6be4b0fd7621ccda10
> {code}
> Bundle: org.eclipse.jface 3.12.0.v20160518-1929
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> Exception:
> java.lang.NullPointerException: null
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.findDockerConnection(CDKDockerUtility.java:39)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:104)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:182)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:198)
> at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
> at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2191)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1229)
> at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:463)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1258)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
> at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:405)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23161) Update bundled and website schema with wf10.1 schema
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23161?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23161.
---------------------------------
I can see the updates, but I'm not really sure how to verify that it's all correct, so I made a follow up jira for that: JBIDE-23311
Closing this.
> Update bundled and website schema with wf10.1 schema
> ----------------------------------------------------
>
> Key: JBIDE-23161
> URL: https://issues.jboss.org/browse/JBIDE-23161
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.4.2.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
>
> WildFly 10.1 is released, so two tasks need to be done.
> 1) Make a pull request to https://github.com/robstryker/jboss.org.schema with schema changes
> 2) Make a pull request to https://github.com/jbosstools/jbosstools-server/tree/master/as/plugins/or... with schema changes
> {code}
> # Check out repos and DL new app server
> wget http://download.jboss.org/wildfly/10.1.0.Final/wildfly-10.1.0.Final.zip
> unzip wildfly-10.1.0.Final.zip
> git clone git@github.com:robstryker/jboss.org.schema.git
> git clone git@github.com:jbosstools/jbosstools-server.git
> tmpdir=`pwd`
> echo $tmpdir
> # Build the catalog plugin
> cd jbosstools-server/as/plugins/org.jboss.tools.as.catalog/
> mvn clean verify -DskipTests
> cd target/classes/
> echo "$tmpdir/wildfly-10.1.0.Final/docs/schema"
> # Copy new or modified schema into the jboss.org.schema repo
> java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
> "$tmpdir/wildfly-10.1.0.Final/docs/schema" \
> "$tmpdir/jboss.org.schema/schema_htdocs" jbossas
> # Copy new or modified schema into the catalog schema folder
> java org.jboss.tools.as.catalog.internal.CopyReleasedSchemaToJBossOrg \
> "$tmpdir/wildfly-10.1.0.Final/docs/schema" \
> "$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema" xsd
> # Commit the changes to jboss.org.schema repo
> cd $tmpdir/jboss.org.schema/schema_htdocs
> git checkout -b wildfly101schema
> git add -A
> git commit -a -m "Update schema from WildFly 10.1.0 Final"
> # TODO ACTION REQUIRED, push to your own repo and initiate pull request
> cd $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/target/classes/
> git checkout -b wildfly101schema
> # Update plugin.xml for catalog
> java -Dplugin.root.dir=$tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/ \
> -Doutput.mode=generateCatalog\
> org.jboss.tools.as.catalog.internal.GeneratePluginXmlCatalog > $tmpdir/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/plugin.xml
> git add -A
> git commit -a -m "Update schema from WildFly 10.1.0 Final"
> #TODO ACTION REQUIRED, push to your own repo and initiate a PR
>
> # run a build to verify it works
> cd $tmpdir/jbosstools-server
> mvn clean install -DskipTests
> # Now run CatalogValidationTest manually
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23311) Review xsd schema files in org.jboss.tools.as.catalog for wf 10.1
by Martin Malina (JIRA)
Martin Malina created JBIDE-23311:
-------------------------------------
Summary: Review xsd schema files in org.jboss.tools.as.catalog for wf 10.1
Key: JBIDE-23311
URL: https://issues.jboss.org/browse/JBIDE-23311
Project: Tools (JBoss Tools)
Issue Type: Task
Components: server
Affects Versions: 4.4.2.AM2
Reporter: Martin Malina
Assignee: Rob Stryker
Rather than reopening JBIDE-23161 to ask you about some discrepancies that I found, I am opening this JIRA.
I compared the contents of org.jboss.tools.as.catalog_3.2.2.v20160923-0424.jar and what's in the wildfly 10.1.0 zip. And there are some diffs. I understand that there will always be more in the plugin - we keep some previous versions. But there are many xsd files missing in the plugin:
{code}
$ comm -23 xsd-list-wf.txt xsd-list-plugin.txt
application-client_6.xsd
application-client_7.xsd
application_1_4.xsd
application_5.xsd
application_6.xsd
application_7.xsd
ejb-jar_2_1.xsd
ejb-jar_3_0.xsd
ejb-jar_3_1.xsd
ejb-jar_3_2.xsd
j2ee_1_4.xsd
j2ee_jaxrpc_mapping_1_1.xsd
j2ee_web_services_1_1.xsd
j2ee_web_services_client_1_1.xsd
javaee_5.xsd
javaee_6.xsd
javaee_7.xsd
javaee_web_services_1_2.xsd
javaee_web_services_1_3.xsd
javaee_web_services_1_4.xsd
javaee_web_services_client_1_2.xsd
javaee_web_services_client_1_3.xsd
javaee_web_services_client_1_4.xsd
jbxb_1_0.xsd
jsp_2_0.xsd
jsp_2_1.xsd
jsp_2_2.xsd
jsp_2_3.xsd
orm_1_0.xsd
persistence_1_0.xsd
persistence_2_0.xsd
web-app_2_4.xsd
web-app_2_5.xsd
web-app_3_0.xsd
web-app_3_1.xsd
web-common_3_0.xsd
web-common_3_1.xsd
web-facelettaglibrary_2_2.xsd
web-facesconfig_1_2.xsd
web-facesconfig_2_2.xsd
web-fragment_3_0.xsd
web-fragment_3_1.xsd
web-jsptaglibrary_2_0.xsd
web-jsptaglibrary_2_1.xsd
web-partialresponse_2_2.xsd
nattura:jar rasp$ find . -name javaee_7.xsd
nattura:jar rasp$ comm -23 xsd-list-wf.txt xsd-list-plugin.txt
application-client_6.xsd
application-client_7.xsd
application_1_4.xsd
application_5.xsd
application_6.xsd
application_7.xsd
ejb-jar_2_1.xsd
ejb-jar_3_0.xsd
ejb-jar_3_1.xsd
ejb-jar_3_2.xsd
j2ee_1_4.xsd
j2ee_jaxrpc_mapping_1_1.xsd
j2ee_web_services_1_1.xsd
j2ee_web_services_client_1_1.xsd
javaee_5.xsd
javaee_6.xsd
javaee_7.xsd
javaee_web_services_1_2.xsd
javaee_web_services_1_3.xsd
javaee_web_services_1_4.xsd
javaee_web_services_client_1_2.xsd
javaee_web_services_client_1_3.xsd
javaee_web_services_client_1_4.xsd
jbxb_1_0.xsd
jsp_2_0.xsd
jsp_2_1.xsd
jsp_2_2.xsd
jsp_2_3.xsd
orm_1_0.xsd
persistence_1_0.xsd
persistence_2_0.xsd
web-app_2_4.xsd
web-app_2_5.xsd
web-app_3_0.xsd
web-app_3_1.xsd
web-common_3_0.xsd
web-common_3_1.xsd
web-facelettaglibrary_2_2.xsd
web-facesconfig_1_2.xsd
web-facesconfig_2_2.xsd
web-fragment_3_0.xsd
web-fragment_3_1.xsd
web-jsptaglibrary_2_0.xsd
web-jsptaglibrary_2_1.xsd
web-partialresponse_2_2.xsd
nattura:jar rasp$
nattura:jar rasp$
nattura:jar rasp$
nattura:jar rasp$
nattura:jar rasp$
nattura:jar rasp$
nattura:jar rasp$ comm -23 xsd-list-wf.txt xsd-list-plugin.txt
application-client_6.xsd
application-client_7.xsd
application_1_4.xsd
application_5.xsd
application_6.xsd
application_7.xsd
ejb-jar_2_1.xsd
ejb-jar_3_0.xsd
ejb-jar_3_1.xsd
ejb-jar_3_2.xsd
j2ee_1_4.xsd
j2ee_jaxrpc_mapping_1_1.xsd
j2ee_web_services_1_1.xsd
j2ee_web_services_client_1_1.xsd
javaee_5.xsd
javaee_6.xsd
javaee_7.xsd
javaee_web_services_1_2.xsd
javaee_web_services_1_3.xsd
javaee_web_services_1_4.xsd
javaee_web_services_client_1_2.xsd
javaee_web_services_client_1_3.xsd
javaee_web_services_client_1_4.xsd
jbxb_1_0.xsd
jsp_2_0.xsd
jsp_2_1.xsd
jsp_2_2.xsd
jsp_2_3.xsd
orm_1_0.xsd
persistence_1_0.xsd
persistence_2_0.xsd
web-app_2_4.xsd
web-app_2_5.xsd
web-app_3_0.xsd
web-app_3_1.xsd
web-common_3_0.xsd
web-common_3_1.xsd
web-facelettaglibrary_2_2.xsd
web-facesconfig_1_2.xsd
web-facesconfig_2_2.xsd
web-fragment_3_0.xsd
web-fragment_3_1.xsd
web-jsptaglibrary_2_0.xsd
web-jsptaglibrary_2_1.xsd
web-partialresponse_2_2.xsd
{code}
But I randomly checked one and it was visible in Preferences -> XML -> XML Catalog. My guess is that these are not ours so they will be present in some Eclipse plugin and we don't need to add them. Can you confirm this?
And in that case, what would you recommend as the best option to verify that our catalog is correct and also that the jboss.org.schema git repo is correct?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23307) Provide a menu in Forge view to trigger the forge wizard
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23307?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-23307:
-----------------------------------------
your provided screenshot is what I had in mind.
Thanks for implementing it so fast.
my feedback:
- little amount code but an incredible usability improvement!
- on Windows, I don't have the Ctrl+4 displayed in the menu action
- I put a comment on the commit: it will be nice to update the readme also to explain that the wizard can be launched using this menu or with Ctrl+4
- for later, the menu appears in dropdown, maybe we can provide it directly side by side the other buttons of the view?
- not related to this bug but it took me so long time to test it locally, we need to consider providing the IDE metafiles for the project see https://issues.jboss.org/browse/JBIDE-23310
> Provide a menu in Forge view to trigger the forge wizard
> --------------------------------------------------------
>
> Key: JBIDE-23307
> URL: https://issues.jboss.org/browse/JBIDE-23307
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: forge
> Affects Versions: 4.4.1.Final
> Reporter: Aurélien Pupier
> Assignee: George Gastaldi
> Labels: new_and_noteworthy, usability
> Fix For: 4.4.2.AM2
>
> Attachments: Screenshot from 2016-10-10 15-04-15.png
>
>
> Having to guess the first time and then to remind the Ctrl+4 shortcut is just impossible.
> please provide a menu in Forge view to trigger the action to open the wizard
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4055) Bundles should "import-package" javax.servlet
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4055?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4055.
-----------------------------
> Bundles should "import-package" javax.servlet
> ---------------------------------------------
>
> Key: JBDS-4055
> URL: https://issues.jboss.org/browse/JBDS-4055
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Mat Booth
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 10.2.0.AM1
>
>
> I have an environment where I am using a different implementation of javax.servlet 3.1.0 that has a different bundle symbolic name.
> Because of this, some jboss bundles that use "Require-Bundle" fail to load with errors like the following:
> {code}
> !ENTRY org.jboss.tools.livereload.core 4 0 2016-09-21 18:08:45.542
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1176]
> Unresolved requirement: Require-Bundle: javax.servlet; bundle-version="3.1.0"
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Ideally, these dependencies should be specified instead with "Import-Package" as recommended by OSGi.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22818) vagrant service-manager call experiences timeout after output
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22818?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22818.
---------------------------------
I never encountered this myself, so unfortunately I cannot really be 100 % sure that this is fixed. But sooner or later this would pop up. So I am closing this for now.
> vagrant service-manager call experiences timeout after output
> --------------------------------------------------------------
>
> Key: JBIDE-22818
> URL: https://issues.jboss.org/browse/JBIDE-22818
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
>
> {noformat}
> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869
> !MESSAGE Unable to successfully complete a call to vagrant service-manager.
> !STACK 0
> java.util.concurrent.TimeoutException: Process output:
> ^[[0m # docker env:^[[0m # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235)
> !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139
> !MESSAGE Unable to successfully complete a call to vagrant service-manager.
> !STACK 0
> java.util.concurrent.TimeoutException: Process output:
> ^[[0m # docker env:^[[0m # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months