javacore-analyser 2.2.0.dev79__tar.gz → 2.2.0.dev91__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/.travis.yml +2 -2
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/CONTRIBUTING.md +39 -1
- javacore_analyser-2.2.0.dev91/Dockerfile +17 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/PKG-INFO +5 -4
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/README.md +4 -3
- javacore_analyser-2.2.0.dev79/Dockerfile +0 -15
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/.github/ISSUE_TEMPLATE/bug_report.md +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/.github/ISSUE_TEMPLATE/feature_request.md +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/.github/dco.yml +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/.gitignore +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/CHANGELOG.md +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/CODE_OF_CONDUCT.md +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/LICENSE +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/MAINTAINERS.md +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/REQUIREMENTS.md +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/SECURITY.md +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/docs/ClassDiagram.png +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/docs/dom_example.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/pyproject.toml +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/requirements.txt +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/__init__.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/__main__.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/abstract_snapshot_collection.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/code_snapshot_collection.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/constants.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/expand.js +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/html/error.html +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/html/processing_data.html +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/chart.js +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/chartjs-adapter-date-fns.bundle.min.js +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/jq.css +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/jquery.mark.min.js +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/jquery.min.js +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/jquery.tablesorter.min.js +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/jquery.tablesorter.widgets.min.js +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/search.js +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/sorting.js +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/theme.blue.css +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/theme.default.min.css +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/jquery/wait2scripts.js +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/style.css +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/xml/index.xml +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/xml/javacores/javacore.xml +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/xml/javacores/javacore.xsl +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/xml/report.xsl +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/xml/threads/thread.xml +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/xml/threads/thread.xsl +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/har_file.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/java_thread.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/javacore.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/javacore_analyser_batch.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/javacore_analyser_web.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/javacore_set.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/logging_utils.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/snapshot_collection.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/snapshot_collection_collection.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/stack_trace.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/stack_trace_element.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/stack_trace_kind.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/templates/index.html +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/thread_snapshot.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/tips.py +0 -0
- {javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/verbose_gc.py +0 -0
@@ -29,5 +29,5 @@ deploy:
|
|
29
29
|
file: dist/*
|
30
30
|
on:
|
31
31
|
# all_branches: true # uncomment for testing purposes
|
32
|
-
branch: main # uncomment on production
|
33
|
-
tags: true # We need to consider if we want to publish all versions or every build
|
32
|
+
# branch: main # uncomment on production
|
33
|
+
tags: true # We need to consider if we want to publish all versions or every build
|
@@ -94,7 +94,7 @@ To run web application:
|
|
94
94
|
|
95
95
|
## Build pip package
|
96
96
|
Follow the steps from [Packaging projects](https://packaging.python.org/en/latest/tutorials/packaging-projects/).
|
97
|
-
Currently Chris
|
97
|
+
Currently Chris and Tad have an API keys for test and production pypi
|
98
98
|
|
99
99
|
## Build container localy
|
100
100
|
To build a container:
|
@@ -115,6 +115,43 @@ or
|
|
115
115
|
`-p` specifies port mapping. The application in container is running on port 5000. You can map it to another port on
|
116
116
|
your machine (5001 in this example).
|
117
117
|
|
118
|
+
|
119
|
+
## Publish the container to ghcr.io/ibm/javacore-analyser
|
120
|
+
Once you built the container locally, you might need to publish it on ghcr.io/ibm/javacore-analyser.
|
121
|
+
Here are the instructions:
|
122
|
+
https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry.
|
123
|
+
Steps:
|
124
|
+
1. Generate the token by navigating to https://github.com/settings/tokens/new?scopes=write:packages.
|
125
|
+
* Select the read:packages scope to download container images and read their metadata.
|
126
|
+
* Select the write:packages scope to download and upload container images and read and write their metadata.
|
127
|
+
* Select the delete:packages scope to delete container images.
|
128
|
+
NOTE: you can use the same token for multiple pushes until it does not expire.
|
129
|
+
2. Tag image:
|
130
|
+
```commandline
|
131
|
+
podman image tag localhost/javacore-analyser ghcr.io/ibm/javacore-analyser:latest
|
132
|
+
podman image tag localhost/javacore-analyser ghcr.io/ibm/javacore-analyser:2.1
|
133
|
+
```
|
134
|
+
3. Push the image:
|
135
|
+
```commandline
|
136
|
+
export CR_PAT=<token-id generated in step 1>
|
137
|
+
echo $CR_PAT | podman login ghcr.io -u USERNAME --password-stdin
|
138
|
+
podman push ghcr.io/ibm/javacore-analyser:2.1
|
139
|
+
podman push ghcr.io/ibm/javacore-analyser:latest
|
140
|
+
```
|
141
|
+
|
142
|
+
## Build and Publish multiplatform image
|
143
|
+
To publish the image for multiple platforms, follow these instructions:
|
144
|
+
https://developers.redhat.com/articles/2023/11/03/how-build-multi-architecture-container-images#benefits_of_multi_architecture_containers
|
145
|
+
```commandline
|
146
|
+
<Generate token if you do not have it yet>
|
147
|
+
export CR_PAT=<token-id generated in step 1>
|
148
|
+
echo $CR_PAT | podman login ghcr.io -u USERNAME --password-stdin
|
149
|
+
podman manifest create javacore-analyser:2.1
|
150
|
+
podman build --platform linux/amd64,linux/arm64,linux/i386 --manifest javacore-analyser:2.1 .
|
151
|
+
podman manifest push javacore-analyser:2.1 docker://ghcr.io/ibm/javacore-analyser:2.1
|
152
|
+
podman manifest push javacore-analyser:2.1 docker://ghcr.io/ibm/javacore-analyser:latest
|
153
|
+
```
|
154
|
+
|
118
155
|
## Releasing a new version
|
119
156
|
Release a new version is partially automated by Travis. Here are the steps:
|
120
157
|
1. Make sure you are on `main` branch in your repository.
|
@@ -162,6 +199,7 @@ https://github.com/settings/tokens/new
|
|
162
199
|
6. Publish release.
|
163
200
|
7. Copy release notes to [CHANGELOG.md](CHANGELOG.md) file.
|
164
201
|
|
202
|
+
|
165
203
|
## Testing
|
166
204
|
As default the tests in Pycharm are ran in the current selected directory. However we want to run them in main
|
167
205
|
directory of the tool (**javacore-analyser** directory, not **test** directory).
|
@@ -0,0 +1,17 @@
|
|
1
|
+
#
|
2
|
+
# Copyright IBM Corp. 2024 - 2024
|
3
|
+
# SPDX-License-Identifier: Apache-2.0
|
4
|
+
#
|
5
|
+
|
6
|
+
FROM python:3
|
7
|
+
|
8
|
+
LABEL org.opencontainers.image.source="https://github.com/IBM/javacore-analyser"
|
9
|
+
LABEL org.opencontainers.image.description="This is a tool to analyse IBM Javacore files and provide the report used to analyse hang/outage and performance issues."
|
10
|
+
LABEL org.opencontainers.image.licenses="Apache-2.0"
|
11
|
+
|
12
|
+
EXPOSE 5000/tcp
|
13
|
+
RUN mkdir /reports
|
14
|
+
VOLUME ["/reports"]
|
15
|
+
|
16
|
+
RUN ["pip", "install", "--no-cache-dir", "javacore-analyser"]
|
17
|
+
CMD ["javacore_analyser_web", "--port=5000", "--reports-dir=/reports"]
|
@@ -1,6 +1,6 @@
|
|
1
1
|
Metadata-Version: 2.4
|
2
2
|
Name: javacore_analyser
|
3
|
-
Version: 2.2.0.
|
3
|
+
Version: 2.2.0.dev91
|
4
4
|
Summary: The tool to review IBM Javacore files
|
5
5
|
Project-URL: Homepage, https://github.com/IBM/javacore-analyser
|
6
6
|
Project-URL: Issues, https://github.com/IBM/javacore-analyser/issues
|
@@ -312,19 +312,20 @@ You can type the following command to obtain the help:
|
|
312
312
|
or
|
313
313
|
`python -m javacore_analyser web --port=5000 --reports-dir=/data/reports_dir`
|
314
314
|
|
315
|
+
|
315
316
|
The first parameter set the port to use by application. If not specified, 5000 will be used.
|
316
317
|
The second parameter sets where the reports need to be stored. If not set, then the `reports` dir will be created in current location.
|
317
318
|
|
318
319
|
Now you can type (http://localhost:5000/).
|
319
320
|
|
320
321
|
### Running container image
|
321
|
-
There is
|
322
|
+
There is a Docker/Podman container managed by one of projects developers. Use the following command
|
322
323
|
to start it:
|
323
324
|
|
324
|
-
`podman run -it --rm --name javacore-analyser --mount type=bind,src="/local-reports-dir",target=/reports -p 5001:5000 ghcr.io/
|
325
|
+
`podman run -it --rm --name javacore-analyser --mount type=bind,src="/local-reports-dir",target=/reports -p 5001:5000 ghcr.io/ibm/javacore-analyser:latest`
|
325
326
|
|
326
327
|
or
|
327
|
-
`docker run -it --rm --name javacore-analyser --mount type=bind,src="/local-reports-dir",target=/reports -p 5001:5000 ghcr.io/
|
328
|
+
`docker run -it --rm --name javacore-analyser --mount type=bind,src="/local-reports-dir",target=/reports -p 5001:5000 ghcr.io/ibm/javacore-analyser:latest`
|
328
329
|
|
329
330
|
The `mount` option specifies where you want locally to store the reports. The reports in the container are stored in
|
330
331
|
`/reports` directory. If you remove mount option, the application will work but the reports will not persist after
|
@@ -73,19 +73,20 @@ You can type the following command to obtain the help:
|
|
73
73
|
or
|
74
74
|
`python -m javacore_analyser web --port=5000 --reports-dir=/data/reports_dir`
|
75
75
|
|
76
|
+
|
76
77
|
The first parameter set the port to use by application. If not specified, 5000 will be used.
|
77
78
|
The second parameter sets where the reports need to be stored. If not set, then the `reports` dir will be created in current location.
|
78
79
|
|
79
80
|
Now you can type (http://localhost:5000/).
|
80
81
|
|
81
82
|
### Running container image
|
82
|
-
There is
|
83
|
+
There is a Docker/Podman container managed by one of projects developers. Use the following command
|
83
84
|
to start it:
|
84
85
|
|
85
|
-
`podman run -it --rm --name javacore-analyser --mount type=bind,src="/local-reports-dir",target=/reports -p 5001:5000 ghcr.io/
|
86
|
+
`podman run -it --rm --name javacore-analyser --mount type=bind,src="/local-reports-dir",target=/reports -p 5001:5000 ghcr.io/ibm/javacore-analyser:latest`
|
86
87
|
|
87
88
|
or
|
88
|
-
`docker run -it --rm --name javacore-analyser --mount type=bind,src="/local-reports-dir",target=/reports -p 5001:5000 ghcr.io/
|
89
|
+
`docker run -it --rm --name javacore-analyser --mount type=bind,src="/local-reports-dir",target=/reports -p 5001:5000 ghcr.io/ibm/javacore-analyser:latest`
|
89
90
|
|
90
91
|
The `mount` option specifies where you want locally to store the reports. The reports in the container are stored in
|
91
92
|
`/reports` directory. If you remove mount option, the application will work but the reports will not persist after
|
@@ -1,15 +0,0 @@
|
|
1
|
-
#
|
2
|
-
# Copyright IBM Corp. 2024 - 2024
|
3
|
-
# SPDX-License-Identifier: Apache-2.0
|
4
|
-
#
|
5
|
-
|
6
|
-
FROM python:3
|
7
|
-
|
8
|
-
EXPOSE 5000/tcp
|
9
|
-
ENV REPORTS_DIR=/reports
|
10
|
-
RUN mkdir /reports
|
11
|
-
VOLUME ["/reports"]
|
12
|
-
|
13
|
-
RUN pip install --no-cache-dir --root-user-action ignore javacore-analyser
|
14
|
-
|
15
|
-
CMD [ "javacore_analyser_web" ]
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/.github/ISSUE_TEMPLATE/bug_report.md
RENAMED
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/__init__.py
RENAMED
File without changes
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/__main__.py
RENAMED
File without changes
|
File without changes
|
File without changes
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/constants.py
RENAMED
File without changes
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/expand.js
RENAMED
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/data/style.css
RENAMED
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/har_file.py
RENAMED
File without changes
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/java_thread.py
RENAMED
File without changes
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/javacore.py
RENAMED
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/stack_trace.py
RENAMED
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/tips.py
RENAMED
File without changes
|
{javacore_analyser-2.2.0.dev79 → javacore_analyser-2.2.0.dev91}/src/javacore_analyser/verbose_gc.py
RENAMED
File without changes
|