i'm trying to configure superset alerts and reporting (deployed on kubernetes) but i'm running into a bug when my alert tries to screenshot my chart. After configuring the alert, I get the following logs in my superset worker node:
superset Scheduling alert Test2 eta: 2022-12-10 00:40:00
│ superset [2022-12-10 00:40:00,367: INFO/ForkPoolWorker-31] Scheduling alert Test2 eta: 2022-12-10 00:40:00
│ superset Query for Test2 took 170.06 ms
│ superset [2022-12-10 00:40:00,751: INFO/ForkPoolWorker-31] Query for Test2 took 170.06 ms
│ superset Screenshotting chart at http://superset:8088/superset/slice/93/?standalone=true
│ superset [2022-12-10 00:40:00,764: INFO/ForkPoolWorker-31] Screenshotting chart at http://superset:8088/superset/slice/93/?standalone=true
│ superset Init selenium driver │
│ superset [2022-12-10 00:40:00,767: INFO/ForkPoolWorker-31] Init selenium driver
superset Taking a PNG screenshot or url http://superset:8088/superset/slice/93/?standalone=true&standalone=3 │
│ superset [2022-12-10 00:40:11,678: INFO/ForkPoolWorker-31] Taking a PNG screenshot or url http://superset:8088/superset/slice/93/?standalone=true&standalone=3 │
│ superset (Background on this error at: http://sqlalche.me/e/13/2j85)
│ superset
│ superset During handling of the above exception, another exception occurred:
│ superset
│ superset Traceback (most recent call last):
│ superset File "/app/superset/tasks/scheduler.py", line 71, in execute
│ superset task_id, report_schedule_id, scheduled_dttm_,
│ superset File "/app/superset/reports/commands/execute.py", line 584, in run
│ superset raise ReportScheduleUnexpectedError(str(ex))
│ superset superset.reports.commands.exceptions.ReportScheduleUnexpectedError: (psycopg2.errors.IdleInTransactionSessionTimeout) terminating connection due to idle-in-transaction timeout
│ superset SSL connection has been closed unexpectedly
I've enabled THUMBNAIL_SELENIUM_USER="admin" and verified that a superset user named admin has admin rights and verified that the slice it's trying to access does, in fact, exist. Has anyone else come across this bug before?
I've gotten the same configuration to work in my staging environment but not in production.
Related
I am using gradle wrapper to run my pitest. I have parent build.gradle which has the pitest defined. My subprojects does not have any pitest. If I run the pitest on individual project for example gradlew clean :myproject:pitest. Then the pitest is successful. But if I try to run pitest from parent using gradlew clean pitest. Then it failes with the below error
> Task :pitest
4:57:34 PM PIT >> INFO : Verbose logging is disabled. If you encounter an
problem please enable it before reporting an issue.
4:57:35 PM PIT >> INFO : Sending 0 test classes to minion
4:57:35 PM PIT >> INFO : Sent tests to minion
4:57:35 PM PIT >> SEVERE : Error generating coverage. Please check that your
classpath contains JUnit 4.6 or above.
Exception in thread "main" org.pitest.util.PitError: Coverage generation
minion exited abnormally. Please check the classpath.
Please copy and paste the information and the complete stacktrace below when
reporting an issue
VM : Java HotSpot(TM) 64-Bit Server VM
Vendor : Oracle Corporation
Version : 25.152-b16
Uptime : 2390
Input ->
1 : -Dfile.encoding=windows-1252
2 : -Duser.country=US
3 : -Duser.language=en
4 : -Duser.variant
BootClassPathSupported : true
Please copy and paste the information and the complete stacktrace below when
reporting an issue
VM : Java HotSpot(TM) 64-Bit Server VM
Vendor : Oracle Corporation
Version : 25.152-b16
Uptime : 2391
Input ->
1 : -Dfile.encoding=windows-1252
2 : -Duser.country=US
3 : -Duser.language=en
4 : -Duser.variant
BootClassPathSupported : true
at
org.pitest.util.Unchecked.translateCheckedException(Unchecked.java:20)
at
org.pitest.coverage.execute.DefaultCoverageGenerator.calculateCoverage(DefaultCoverageGenerator.java:103)
at
org.pitest.coverage.execute.DefaultCoverageGenerator.calculateCoverage(DefaultCoverageGenerator.java:49)
at
org.pitest.mutationtest.tooling.MutationCoverage.runReport(MutationCoverage.java:115)
at
org.pitest.mutationtest.tooling.EntryPoint.execute(EntryPoint.java:116)
at
org.pitest.mutationtest.tooling.EntryPoint.execute(EntryPoint.java:49)
at
org.pitest.mutationtest.commandline.MutationCoverageReport.runReport(MutationCoverageReport.java:87)
at
org.pitest.mutationtest.commandline.MutationCoverageReport.main(MutationCoverageReport.java:45)
Caused by: org.pitest.util.PitError: Coverage generation minion exited
abnormally. Please check the classpath.
Please copy and paste the information and the complete stacktrace below when
reporting an issue
VM : Java HotSpot(TM) 64-Bit Server VM
Vendor : Oracle Corporation
Version : 25.152-b16
Uptime : 2390
Input ->
1 : -Dfile.encoding=windows-1252
2 : -Duser.country=US
3 : -Duser.language=en
4 : -Duser.variant
BootClassPathSupported : true
at
org.pitest.coverage.execute.DefaultCoverageGenerator.gatherCoverageData(DefaultCoverageGenerator.java:137)
at
org.pitest.coverage.execute.DefaultCoverageGenerator.calculateCoverage(DefaultCoverageGenerator.java:87)
Can any one direct what may be going wrong as I am using JUNIT 4.12 which is greater than 4.6 which is mentioned in the error.
In my experience, adding explicit dependency to Junit is needed although there are no tests in the submodule.
For me this fixed the problem:
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.11</version>
<scope>test</scope>
</dependency>
rxRemoteHadoopMRCall()
====== xxxx.cloudapp.azure.com (Master HPA Process) has started run at Sat Mar 18 08:15:43 2017 ======
17/03/18 03:16:36 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where application
Warning: libjvm.so not found in /log/cloudera/parcels/MRS-9.0.1/hadoop, searching system-wide
Internal Error: Cannot reset hdfs internal params while connected to an hdfs file system.
Error in try({ :
Internal Error: Cannot reset hdfs internal params while connected to an hdfs file system.
I wonder if this is a problem with locating JRE. You can try setting JAVA_HOME for your user ($HOME/.bashrc) or for all users (etc/environment) on the node you're connecting to. It should point to a place that correctly resolves this path: $JAVA_HOME/jre/lib/amd64/server/libjvm.so
I'm trying to deploy the Java backend of a web application on GlassFish 4.1.1. I use OSGi with declarative services. Declarative services seem to work when the bundle in question is published as a JAR but I'm having some trouble with WARs: Felix doesn't seem to find the the component descriptors (OSGI-INF/SomeComponent.xml).
I put together a very simple example to illustrate this.
The bundle is called com.ex.client.
Here's the MANIFEST.MF:
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Client
Bundle-SymbolicName: com.ex.client
Bundle-Version: 1.0.0.qualifier
Bundle-RequiredExecutionEnvironment: JavaSE-1.8
Import-Package: com.ex.auth,
javax.servlet;version="3.1.0",
javax.servlet.http;version="3.1.0",
org.osgi.framework
Service-Component: OSGI-INF/ClientServlet.xml
Web-ContextPath: /hi
Bundle-ClassPath: WEB-INF/classes
Here's the structure of the resulting WAR file:
com.ex.client.war
|
+-- META-INF
| |
| +-- MANIFEST.MF (as shown above)
|
+-- OSGI-INF
| |
| +-- ClientServlet.xml
|
+-- WEB-INF
|
+-- classes
| |
| +-- binaries
|
+-- web.xml
And here's Felix complaining that it cannot find OSGI-INF/ClientServlet.xml:
Info: Installed C:\glassfish-4.1.1\glassfish\domains\domain1\autodeploy\bundles\com.ex.client.war
Severe: ERROR: com.ex.client (333): Component descriptor entry 'OSGI-INF/ClientServlet.xml' not found
Info: Started bundle: file:/C:/glassfish-4.1.1/glassfish/domains/domain1/autodeploy/bundles/com.ex.client.war
Info: Started bundle: file:/C:/glassfish-4.1.1/glassfish/domains/domain1/autodeploy/bundles/com.ex.client.war
Info: Expanded at file:/C:/glassfish-4.1.1/glassfish/domains/domain1/osgi-cache/felix/bundle309/data/applications/bundle333-1456241385614/
Info: visiting unvisited references
Info: uris = [file:/C:/glassfish-4.1.1/glassfish/domains/domain1/osgi-cache/felix/bundle309/data/applications/bundle333-1456241385614/WEB-INF/classes/]
Info: visiting unvisited references
Info: visiting unvisited references
Info: total number of classes with faces annotation = 0
Info: Loading application [com.ex.client_1.0.0.qualifier] at [/hi]
Info: Registered ServletContext as a service with properties: {osgi.web.symbolicname=com.ex.client, osgi.web.version=1.0.0.qualifier, osgi.web.contextpath=/hi}
Info: deployed bundle com.ex.client [333] at file:/C:/glassfish-4.1.1/glassfish/domains/domain1/osgi-cache/felix/bundle309/data/applications/bundle333-1456241385614/
When I go to the location
C:/glassfish-4.1.1/glassfish/domains/domain1/osgi-cache/felix/bundle309/data/applications/bundle333-1456241385614/
mentioned above I see the exact same structure as within the WAR file. OSGI-INF/ClientServlet.xml is there.
I googled "Component descriptor entry * not found" and found the code that logs the message (note: I'm not sure if this is the correct version): http://grepcode.com/file/repo1.maven.org/maven2/org.apache.felix/org.apache.felix.scr/1.8.2/org/apache/felix/scr/impl/BundleComponentActivator.java#150
URL[] descriptorURLs = findDescriptors( m_bundle, descriptorLocation );
if ( descriptorURLs.length == 0 )
{
// 112.4.1 If an XML document specified by the header cannot be located in the bundle and its attached
// fragments, SCR must log an error message with the Log Service, if present, and continue.
log( LogService.LOG_ERROR, "Component descriptor entry ''{0}'' not found", new Object[]
{ descriptorLocation }, null, null, null );
continue;
}
Where as far as I can tell descriptorLocation should be OSGI-INF/ClientServlet.xml (what I wrote in the Service-Component in the manifest). Somehow findDescriptors( m_bundle, descriptorLocation ), doesn't find the XML file.
I copied the findDescriptors method into a class in my bundle and I'm printing the results:
Info: bundle://333.0:0/OSGI-INF/ClientServlet.xml
So /OSGI-INF/ClientServlet.xml is indeed there and can be found using the same code that is failing for BundleComponentActivator (again, if this is really the same version of the code; I'm struggling to find out which version GlassFish 4.1.1 uses). So I think the problem is that when BundleComponentActivator first tries to find this XML, it isn't there yet. It works later for me because at that point it has been unpacked and made available.
So... what to do? Am I wrong to think that this should work? Am I packing things incorrectly?
In a production installation over 'WAS_LIBERTY_CORE_V8.5.5.4' with 'DB2':
I have now a simple configuration in server.xml.
The mobilefirst console shows the runtimes but I can't deploy adapters or applications. This is the content of messages.log. This 2 lines appears every attempt to upload an adapter/application:
[19/04/15 19:19:37:667 CEST] 0000008e org.apache.wink.server.internal.registry.ResourceRegistry I The system cannot find any method in the com.ibm.worklight.admin.services.RuntimeService class that supports POST. Verify that a method exists.
[19/04/15 19:19:37:683 CEST] 0000008e org.apache.wink.server.internal.RequestProcessor I The following error occurred during the invocation of the handlers chain: WebApplicationException (405) with message 'null' while processing POST request sent to http://MACHINENAME:9080/wladmin/management-apis/1.0/runtimes/test/
More info:
wlp.install.dir = C:/IBM/WebSphere/Liberty/
java.home = C:\Program Files\Java\jdk1.7.0_79\jre
java.version = 1.7.0_79
java.runtime = Java(TM) SE Runtime Environment (1.7.0_79-b15)
os = Windows Server 2008 R2 (6.1; amd64) (en_US)
DB: DB2 in localhost
Complete server.xml file: https://drive.google.com/file/d/0BxAEyIioPI2YT2NPZXdCcktoT1U/view?usp=sharing
Complete console.log file: https://drive.google.com/file/d/0BxAEyIioPI2YUDhLZDQ0Qmgydk0/view?usp=sharing
Complete messages.log file: https://drive.google.com/file/d/0BxAEyIioPI2YdUREcjcyd3JYNGs/view?usp=sharing
I'm tried with other Java version like 'SDK_JAVA_TE_V7.0_WASLC_V8.5.5', with other runtimes, reinstalling all...
Per the comments, the error appears to happen only in IE 9.
As a work around, use a different browser such as Safari, Chrome, Firefox, Opera, etc... in order to deploy artifacts.
The issue with IE 9 will be investigated.
I'd like to use the function bitrand(), which is in the compat.jl package. Here is what I did:
julia> Pkg.add("compat")
INFO: Nothing to be done
julia> using Compat
julia> bitrand()
ERROR: bitrand not defined
julia> Pkg.update()
INFO: Updating METADATA...
INFO: Computing changes...
INFO: No packages to install, update or remove
julia> using Compat
julia> bitrand()
ERROR: bitrand not defined
julia> Compat.bitrand()
ERROR: bitrand not defined
For info, I am using Julia-0.3.2. Thank you!
EDIT
julia> Pkg.status()
3 required packages:
- Compat 0.2.10
- Distributions 0.6.3
- StatsBase 0.6.10
3 additional packages:
- ArrayViews 0.4.8
- JSON 0.4.0
- PDMats 0.3.1
julia> Pkg.add("Compat")
INFO: Nothing to be done
julia> using Compat
julia> bitrand()
ERROR: bitrand not defined
This definitely works for me on Julia v0.3.3 with Compat.jl v0.2.10, so can you do the following:
Pkg.rm("Compat")
Run readdir(Pkg.dir()) to confirm its gone
Pkg.update()
Pkg.add("Compat") with a capital C
Close and re-open Julia, just to be sure
using Compat