VSC EXTENSION CODE WONT RUN PROPERLY

Type: Bug
So I added an extension to run my code on google and preview it, and it worked fine for agggeeesss. Now a few days ago i went back to it and when i went to run the code, google opened, good so far. Then it closed instantly. I dont know why. But i have a feeling its to do with a node.js or something, whenever i end the task on task manager, it just reapears. And the task wasnt there before. I dont know how to get rid of it. And just to be clear, ive checked my code theres nothing wrong, i deleted the vs code file thing that apears when in the folder, and i have even restared a new code and it still does the same. My other laptop is fine too though. And i couldnt even preview this message on GitHub because when i went to create an account it just kept saying, oops sorry. Looks like something went wrong
VS Code version: Code 1.79.2 (695af097c7bd098fbf017ce3ac85e09bbc5dda06, 2023-06-14T08:57:04.379Z)
OS version: Windows_NT x64 10.0.22621
Modes:

System Info

Item
Value

CPUs
Intel(R) Celeron(R) N4100 CPU @ 1.10GHz (4 x 1094)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
7.82GB (3.21GB free)

Process Argv
--crash-reporter-id 473b1e88-3238-478c-9d3f-849ee5bc10df

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

vscode-edge-devtools
ms-
2.1.2

live-server
ms-
0.4.8

vsliveshare
ms-
1.0.5873

LiveServer
rit
5.7.9

cors-browser
Wsc
1.0.11

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30610679
3biah626:30602489
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
a9j8j154:30646983
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
03d35959:30757346
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30730052
hideindicator:30766889
pythongtdpath:30739704
bgfeh915:30763804
dh2dc718:30763024

Can you provide a minimal example or simpler steps to demonstrate the issue, it is hard to understand the issue from the description.

So i have made a html code on the visual studio code app right.
Then I added an extension that allows me to preview it on google.
It has worked for ages and allows me to look at all my creations of my html
websites.
But a week ago when i went to run the code again, it opened the google page
like normal. But then it closed.
I then clicked run again, and google opened then closed again. everytime I
try to run a code the google page just crashes. I tried uninstalling the
app and reinstalling but that didnt work. I also have a feeling its to do
with this node.js thing. Normally i end tasks in the task manager to make
my computer better but then this node.js thing showed up as one of the
tasks. I tried ending it but it just keeps on reapearing
On Fri, 16 Jun 2023 at 18:55, Robo @.***> wrote:

Can you provide a minimal example or simpler steps to demonstrate the
issue, it is hard to understand the issue from the description.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/185278#issuecomment-1594197867,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BATMSGRTEJY3QVOFXSPHE2LXLP7MLANCNFSM6AAAAAAZIN22T4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Oh, i have also found out the at the start of the code it says
<!doctype html>

When I put it back to normal  it now opens in google. I dont know
what the lang=en means though
On Wed, 21 Jun 2023 at 12:14, Autahi Coffey @.***> wrote:

So i have made a html code on the visual studio code app right.
Then I added an extension that allows me to preview it on google.
It has worked for ages and allows me to look at all my creations of my
html websites.
But a week ago when i went to run the code again, it opened the google
page like normal. But then it closed.
I then clicked run again, and google opened then closed again. everytime I
try to run a code the google page just crashes. I tried uninstalling the
app and reinstalling but that didnt work. I also have a feeling its to do
with this node.js thing. Normally i end tasks in the task manager to make
my computer better but then this node.js thing showed up as one of the
tasks. I tried ending it but it just keeps on reapearing
On Fri, 16 Jun 2023 at 18:55, Robo @.***> wrote:

Can you provide a minimal example or simpler steps to demonstrate the
issue, it is hard to understand the issue from the description.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/185278#issuecomment-1594197867,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BATMSGRTEJY3QVOFXSPHE2LXLP7MLANCNFSM6AAAAAAZIN22T4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey @alexdima, this issue might need further attention.
@DoomSlayer051107, you can help us out by closing this issue if the problem no longer exists, or adding more information.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[feat]: MSSQL Support

As a user of lazygit, this would be perfect for me, if only it had MSSQL support.

Hello,
it will be supported :) there is already a work in progress. Stay tunned :P

Can't wait for MSSQL support. Once it's available I will be downloading this immediately


Improve (and fix some) test finalization

Remove some duplicate checks from pylint
Make Mocks private to the module
Import module from typing
Allow passing the mocker in the constructor
Make MockMicrogrid an async context manager
Use the MockMicrogrid as an async context manager
Improve finalization of power distributing tests
Improve finalization of voltage streamer tests
Improve finalization of logical meter tests
Improve finalization of formula formatter tests
Improve finalization of EV charger pool tests
Improve finalization of formula composition tests
Improve finalization of battery status tests
Improve finalization of grid tests
Disable pylint check only in one line

Updated!


ServiceMonitor labels

It's good to see that the support for ServiceMonitor has now been included which will make exposing metrics to prometheus a lot easier.
In our case, prometheus is deployed to pick up servicemonitors & podmonitors with a specific label only, as I'm sure will be the case with other folks too. At the moment, the chart doesn't support adding custom labels to the ServiceMonitor.
Do you have plans to allow to add custom labels to the ServiceMonitor?
TIA

@vineetmadan Hey! No plan on my end. But I'll gladly review any changes to make it customizable in our chart.

Just a heads up, I think work is being done in this PR to add labels: https://github.com/actions-runner-controller/actions-runner-controller/pull/670


Fixed broken luis inspector.

Cherry pick of #1334 into master.

Pull Request Test Coverage Report for Build 2126

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 54.967%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/extensions/luis/client/src/App.tsx
0
1
0.0%

Totals

Change from base Build 2115:
0.02%

Covered Lines:
4866

Relevant Lines:
8314

💛  - Coveralls

Rebased and re-pushed with Chris' change


Jax GMRES on GPU largely slower than its scipy counterpart

Hello, I used the following script to compare the performance of the jax gmres solver and the one from scipy :
from time import time

import jax
import scipy
from jax import jit

def solve_jax(A, b):
    return jax.scipy.sparse.linalg.gmres(lambda v: A @ v, b,solve_method='batched', atol=1e-5)

solve_jax_jit = jit(solve_jax)

A = scipy.random.rand(30, 30)
b = scipy.random.rand(30)

t1 = time()
for i in range(20):
    x = scipy.sparse.linalg.gmres(A, b, atol=1e-5, restart=20)
    #print(i, x[0][0])
t2 = time()
for i in range(20):
    x_jax = solve_jax_jit(A, b)
    #print(i, x_jax[0][0])
t3 = time()

print(f"{(t2 - t1)/20:.2e} vs {(t3 - t2)/20:.2e}")

Here was the result :
1.09e-01 vs 2.04e+00

Nearly a 20x factor of difference ! I tried to play around with the gmres parameters but it did not change the time ratio scipy/jax.
I am using a GPU backend (could this explain the performence difference ?) on Windows (my GPU is a GTX 1650) and I have Cuda 11.6 installed. The Jax version I'm using is 0.2.26.

You are currently also measuring jit compile time in your code. Maybe try something like this
c = jit(solve_jax).lower(A, b).compile()
...
for i in range(...):
 x =  c(A, b)

Also don't forget block_until_ready(); see https://jax.readthedocs.io/en/latest/faq.html#benchmarking-jax-code for more information.
For what it's worth, this is the result of your benchmark, slightly modified, and run on a Colab CPU runtime:
import jax
import scipy
from jax import jit

def solve_jax(A, b):
    return jax.scipy.sparse.linalg.gmres(lambda v: A @ v, b,solve_method='batched', atol=1e-5)

solve_jax_jit = jit(solve_jax)

A = scipy.random.rand(30, 30)
b = scipy.random.rand(30)
_ = solve_jax_jit(A, b)[0].block_until_ready()

%timeit scipy.sparse.linalg.gmres(A, b, atol=1e-5, restart=20)
# 10 loops, best of 5: 127 ms per loop

%timeit solve_jax_jit(A, b)[0].block_until_ready()
# 100 loops, best of 5: 11.3 ms per loop

Compilation time does not seem to cause the issue ... I just ran your code and got :
121 ms ± 6.26 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)
3.15 s ± 407 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

but at least the problem seems to come from my installation.

Can you say more about how you're running this? What versions of jax and jaxlib do you have installed? Are you on CPU or GPU?

I'm using

Python 3.9
Cuda 11.6
Jax Lib 0.1.175
Jax 0.2.26
GPU version
I had the issue with both single and double precision

I installed the Windows build following these instruction (using the jaxlib-0.1.75+cuda111-cp39-none-win_amd64.whl wheel)
so maybe the issue is within this build. (https://github.com/cloudhan/jax-windows-builder)

This is a known issue with JAX's iterative methods on GPUs. XLA's loops on GPU sync back to the host CPU on each loop iteration, so they are slow if the function being solved is quick to evaluate. I actually made a benchmark for this issue that we passed off to the XLA GPU team.
The work-around is either to run this sort of computation on the CPU instead (e.g., by copying all arrays explicitly to the CPU with jax.device_put). Or you could also try using TPUs, for which XLA is able to run loops entirely on device.
We could also consider writing/leveraging custom CUDA kernels or iterative solvers on GPUs, but would be a major undertaking and would have disadvantages (like losing pytree support).

having the same problem on CPU,
import numpy as np
import scipy.sparse as scipy_sparse
from scipy.sparse.linalg import lgmres as scipy_gmres
import time

def create_sparse_matrix(n, density=0.01):
    A = scipy_sparse.random(n, n, density=density, format='csr')
    return A

def benchmark_scipy_gmres(A_scipy, b, tol=1e-5, maxiter=1000):
    start_time = time.time()
    x, info = scipy_gmres(A_scipy, b)
    end_time = time.time()

    # Check convergence
    residual = np.linalg.norm(A_scipy @ x - b)
    converged = info == 0  # GMRES returns 0 if converged

    return x, end_time - start_time, converged, float(residual), int(info)

def run_benchmark(n_values, num_runs=1):
    results = []

    for n in n_values:
        scipy_times = []
        convergence_rates = []
        residuals = []
        infos = []

        for _ in range(num_runs):
            A = create_sparse_matrix(n)
            b = np.random.rand(n)

            _, scipy_time, converged, residual, info = benchmark_scipy_gmres(A, b)

            scipy_times.append(scipy_time)
            convergence_rates.append(float(converged))
            residuals.append(residual)
            infos.append(info)

        results.append({
            'n': n,
            'scipy_avg_time': np.mean(scipy_times),
            'convergence_rate': np.mean(convergence_rates),
            'avg_residual': np.mean(residuals),
            'avg_info': np.mean(infos)
        })
        print(f"Completed benchmarks for n={n}")

    return results

if __name__ == "__main__":
    n_values = [100, 500, 1000, 2000]
    results = run_benchmark(n_values)

    print("\nBenchmark Results:")
    print("n\tSciPy GMRES (s)\tConv. Rate\tAvg. Residual\tAvg. Info")
    for result in results:
        print(f"{result['n']}\t{result['scipy_avg_time']:.4f}\t\t{result['convergence_rate']:.2f}\t\t{result['avg_residual']:.2e}\t\t{result['avg_info']:.2f}")

vs
`import numpy as np
import scipy.sparse as scipy_sparse
import jax
import jax.numpy as jnp
from jax.experimental import sparse
from jax.scipy.sparse.linalg import gmres as jax_gmres
import time
def create_sparse_matrix(n, density=0.01):
A = scipy_sparse.random(n, n, density=density, format='csr')
return A
def scipy_to_jax_sparse(scipy_sparse_mat):
return sparse.BCSR.from_scipy_sparse(scipy_sparse_mat)
def benchmark_jax_gmres(A_scipy, b, tol=1e-5, maxiter=1000):
A_jax = scipy_to_jax_sparse(A_scipy)
b_jax = jnp.array(b)
@jax.jit
def jax_gmres_solve(A, b):
    x, info = jax_gmres(A, b)
    return x, info

# Compile the function
_ = jax_gmres_solve(A_jax, b_jax)

# Benchmark the compiled function
start_time = time.time()
x, info = jax_gmres_solve(A_jax, b_jax)
x = x.block_until_ready()  # Ensure computation is complete
end_time = time.time()

# Check convergence
residual = jnp.linalg.norm(A_jax @ x - b_jax)
converged = info == 0  # GMRES returns 0 if converged

return x, end_time - start_time, converged, float(residual), int(info)

def run_benchmark(n_values, num_runs=1):
results = []
for n in n_values:
    jax_times = []
    convergence_rates = []
    residuals = []
    infos = []

    for _ in range(num_runs):
        A = create_sparse_matrix(n)
        b = np.random.rand(n)

        _, jax_time, converged, residual, info = benchmark_jax_gmres(A, b)

        jax_times.append(jax_time)
        convergence_rates.append(float(converged))
        residuals.append(residual)
        infos.append(info)

    results.append({
        'n': n,
        'jax_avg_time': np.mean(jax_times),
        'convergence_rate': np.mean(convergence_rates),
        'avg_residual': np.mean(residuals),
        'avg_info': np.mean(infos)
    })
    print(f"Completed benchmarks for n={n}")

return results

if name == "main":
n_values = [100, 500, 1000, 2000]
results = run_benchmark(n_values)
print("\nBenchmark Results:")
print("n\tJAX GMRES (s)\tConv. Rate\tAvg. Residual\tAvg. Info")
for result in results:
    print(f"{result['n']}\t{result['jax_avg_time']:.4f}\t\t{result['convergence_rate']:.2f}\t\t{result['avg_residual']:.2e}\t\t{result['avg_info']:.2f}")`

@michelkluger — It's hard to say much here since you didn't include the results of your benchmarks, but some high level thoughts: All of the sparse support in JAX is experimental so your milage may vary on the actual performance of these APIs. But, there have been some changes in how XLA handles CPU iterations, so I'd be interested to know how the performance compares with and without the XLA_FLAGS=--xla_cpu_use_thunk_runtime=false environment variable set to know if there is a specific regression here.

I tried to create a new script, to guarantee that comparison is more fair, same matrix and everything

import numpy as np
import scipy.sparse as sp
from scipy.sparse.linalg import gmres as scipy_gmres
import jax
import jax.numpy as jnp
from jax.experimental import sparse as jax_sparse
from jax.scipy.sparse.linalg import gmres as jax_gmres
import time
import pandas as pd

# Constants
MATRIX_DENSITY = 0.1
TOLERANCE = 1e-5
MAX_ITERATIONS = 1000
NUM_RUNS = 1
N_VALUES = [100, 200, 500, 1000]
OUTPUT_FILE = "gmres_benchmark_results.csv"

def create_sparse_matrix(n, density=MATRIX_DENSITY):
    A = sp.random(n, n, density=density, format='csr')
    return A

def benchmark_scipy_gmres(A, b, tol=TOLERANCE, maxiter=MAX_ITERATIONS):
    start_time = time.time()
    try:
        x, info = scipy_gmres(A, b, atol=tol, maxiter=maxiter, restart=min(maxiter, A.shape[0]))
        end_time = time.time()
        residual = np.linalg.norm(A @ x - b)
        return end_time - start_time, info == 0, residual
    except Exception as e:
        print(f"SciPy GMRES error: {str(e)}")
        return np.nan, False, np.nan

@jax.jit
def jax_gmres_solve(A, b, tol=TOLERANCE, maxiter=MAX_ITERATIONS):
    x, info = jax_gmres(A, b, tol=tol, maxiter=maxiter, restart=min(maxiter, A.shape[1]))
    return x, info

def benchmark_jax_gmres(A, b, tol=TOLERANCE, maxiter=MAX_ITERATIONS):
    A_jax = jax_sparse.BCOO.from_scipy_sparse(A)
    b_jax = jnp.array(b)

    # Warm-up run
    _ = jax_gmres_solve(A_jax, b_jax)

    start_time = time.time()
    try:
        x, info = jax_gmres_solve(A_jax, b_jax)
        x = x.block_until_ready()
        end_time = time.time()

        residual = jnp.linalg.norm(A_jax @ x - b_jax)
        return end_time - start_time, info == 0, float(residual)
    except Exception as e:
        print(f"JAX GMRES error: {str(e)}")
        return np.nan, False, np.nan

def run_benchmark(n_values, num_runs=NUM_RUNS):
    results = []

    for n in n_values:
        print(f"Running benchmark for n={n}")
        for _ in range(num_runs):
            A = create_sparse_matrix(n)
            b = np.random.rand(n)

            scipy_time, scipy_conv, scipy_res = benchmark_scipy_gmres(A, b)
            jax_time, jax_conv, jax_res = benchmark_jax_gmres(A, b)

            results.append({
                'n': n,
                'scipy_time': scipy_time,
                'scipy_conv': scipy_conv,
                'scipy_res': scipy_res,
                'jax_time': jax_time,
                'jax_conv': jax_conv,
                'jax_res': jax_res,
                'speedup': scipy_time / jax_time if jax_time > 0 else np.nan
            })

    return pd.DataFrame(results)

if __name__ == "__main__":
    results_df = run_benchmark(N_VALUES)

    summary = results_df.groupby('n').mean()
    summary = summary[['scipy_time', 'jax_time', 'speedup', 'scipy_conv', 'jax_conv', 'scipy_res', 'jax_res']]
    summary.columns = ['SciPy Time (s)', 'JAX Time (s)', 'Speedup', 'SciPy Conv. Rate', 'JAX Conv. Rate', 'SciPy Residual', 'JAX Residual']

    print("\nBenchmark Results Summary:")
    pd.set_option('display.float_format', lambda x: f"{x:.4f}")
    print(summary)

    summary.to_csv(OUTPUT_FILE)
    print(f"\nResults have been saved to '{OUTPUT_FILE}'")

@michelkluger — It's hard to say much here since you didn't include the results of your benchmarks, but some high level thoughts: All of the sparse support in JAX is experimental so your milage may vary on the actual performance of these APIs. But, there have been some changes in how XLA handles CPU iterations, so I'd be interested to know how the performance compares with and without the XLA_FLAGS=--xla_cpu_use_thunk_runtime=false environment variable set to know if there is a specific regression here.

I added a new script for more fair comparison, I am surprised, because from all I read, Jax was meant to be so much faster, but I am very new to that, so it is very much possible that I made some mistakes, be happy to learn from that

Thanks! I ran this script locally and I can confirm that the performance with XLA_FLAGS=--xla_cpu_use_thunk_runtime=false is comparable to scipy, but without we have a major performance regression.
Pinging @ezhulenev who has been looking into related performance issues.

@michelkluger — For your specific use case, I'd recommend setting that environment variable for now.

@michelkluger — For your specific use case, I'd recommend setting that environment variable for now.

I ran with the flag,

Set the XLA flag
os.environ['XLA_FLAGS'] = '--xla_cpu_use_thunk_runtime=false'
tested with
# get XLA_FLAGS env variable
def get_xla_flags():
    try:
        return os.environ["XLA_FLAGS"]
    except KeyError:
        return None
get_xla_flags()

What happens if you replace the sparse.BCSR matrix with a dense matrix? The jax.experimental.sparse code is just a reference implementation, and is quite slow even for simple operations like sparse matmul.

What happens if you replace the sparse.BCSR matrix with a dense matrix? The jax.experimental.sparse code is just a reference implementation, and is quite slow even for simple operations like sparse matmul. I wouldn't be surprised if slow sparse matmul is driving the performance here.

are we referring to the new or old script?


Descriptions don't match up with titles on front page

Needs further investigation I'm currently working other projects for uni though

Tempname array needs correcting for some reason "No description" is not being appended in the correct place in the array not sure why will test when on pc

Page also only loads 30 repos need to add page to get request

Fixed by https://github.com/futurelucas4502/futurelucas4502.github.io/commit/f3425113c7182bf422e316ecb0b90e1558f618e3


'ascii' codec can't encode characters in position 11-14: ordinal not in range(128)

Hi guys,
I managed so far to get this package working for xhtml2pdf==0.0.5. For newer version, I get the following error in xhtml2pdf. The decoding of the rendered pdf text (value) seems to be the problem. This is as far as my assessment went. It would be nice if easy-pdf would also work for the newer version of xhtml2pdf.
cheers,
Besma

:+1: same issue

I have the same problem what can I do

Same here ....

I got the same problem.
@bmcharek Can you tell me what the exact versions of the dependencies are to make it work?


[Question / Feature Request] Perform more complex search queries

Hi SteinHq team!
I wonder if it is possible to make more complex queries using search{} feature?
I'm looking for a way to test if a value is "greater then" a field and "less then" another field.
Example:
https://api.steinhq.com/v1/storages/[my_sheet]?search={"startdate"<="2020-05-01","enddate">="2020-05-01" }
Thanks!
gciola

Hey, gciola!
That definitely seems reasonable. I've heard that suggestion numerous times, and I think it's time I implement it. There are a couple more details I'll need to figure out about the intended behaviour and corner cases before implementing, but things are a bit busy right now. I'll get back to it as soon as possible, though.
Sorry for the delay, and thanks for the suggestion!


Delete jobs.json

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/APEXTest/AirLocTesting, working directory: W:\ijxm-s, target branch: master, target branch commit: 8d7fc40441bd4a5746bc2db055c8db054f395468, source branch: ResxAC1035, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


'app-messages' is not a known element

Versions
Angular CLI: 1.7.4
Node: 9.11.1
OS: win32 x64
Angular: 5.2.10
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cli: 1.7.4
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.5.3
webpack: 3.11.0

Windows 10

Repro steps
Step 1. Run ng test as directed from https://angular.io/guide/testing after finishing the tutorial from https://angular.io/tutorial (i.e., running ng test using the code from the tutorial).
Step 2. Chrome window automatically opens. Get error about "'router-outlet' is not a known element". Googled that error and found fix. But no such fix found for "'app-messages' is not a known element".
Observed behavior
<!-- Normally this includes a stack trace and some more information. -->

Error: Template parse errors:
'app-messages' is not a known element:
1. If 'app-messages' is an Angular component, then verify that it is part of this module.
2. If 'app-messages' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. ("
</nav>
<router-outlet></router-outlet>
[ERROR ->]<app-messages></app-messages>"): ng:///DynamicTestModule/AppComponent.html@6:0
    at syntaxError (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/compiler/esm5/compiler.js:486:22)
    at<EMAIL_ADDRESS>(http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/compiler/esm5/compiler.js:24674:1)
    at<EMAIL_ADDRESS>(http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/compiler/esm5/compiler.js:34629:1)
    at<EMAIL_ADDRESS>(http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/compiler/esm5/compiler.js:34604:1)
    at http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/compiler/esm5/compiler.js:34505:48
    at Set.forEach (<anonymous>)
    at<EMAIL_ADDRESS>(http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/compiler/esm5/compiler.js:34505:1)
    at http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/compiler/esm5/compiler.js:34393:1
    at Object.then (http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/compiler/esm5/compiler.js:475:33)
    at<EMAIL_ADDRESS>(http://localhost:9876/_karma_webpack_/webpack:/node_modules/@angular/compiler/esm5/compiler.js:34391:1)

Desired behavior

Mention any other details that might be useful (optional)
Ran ng test from my code root directory.

I created a home component that I could not render and kept getting the same error. Here is how I solved it.
I checked the app.component.ts file to see if the component was imported and added to @NgModule declarations. Since it wasn't I added the following:

import { HomeComponent } from './home/home.component';

@NgModule({
declarations: [
AppComponent,
HomeComponent
]

I'm not sure why it wasn't added when the CLI generated the component but this is was my solution. Let me know if it worked for you or what you ended up finding as a solution.


Test step sometimes halts and times out

From time to time, the test step, specifically when running prove, will come to a halt and cause the step to time out and fail.
This produces false failures and is very annoying if occurring on a workflow on master branch, since there's no way to re-run workflows to show the build actually was good.

Current workaround is to cancel the workflow (or let it time out) and re-run all jobs.
Still needs a fix.


merge dev to master

In Progress
Changes to mention:

Fixed issues

dataset undefined error in case of swipeToSlide but finite slides
slideWidth issue by transform scale
variableWidth + finite alignment problems
wrapper direction rtl issues

Mixins to Pure Functions

getWidth, getHeight
swipeDirection

Other Changes

removed sass, using pure CSS instead
enforced dir='ltr' in the slider, so dir='rtl' in wrapper doesn't break the slider
corrected up/down direction conventions

"removed sass" - why?


issue #216, Added Apple Park image to 06-02 WORKPLACE, traditional-mandarin version

Same as the other PR.


Attempt to mimic changes from upstream PR#27467

Problem: if a process that's been started for 'docker exec' exits fast enough, the daemon can receive a 'process exited' update from containerd before it starts passing stdio data back and forth, losing its output.
Why it happens: the 'process exited' state change message is only processed after acquiring a lock for the container, and while most of the exec() setup is done while holding that lock, the lock is freed when libcontainerd calls back to set up the passing of stdio data.
Proposed change: call getExecConfig() before AddProcess(), and modify AddProcess() to take a callback that the daemon can hand it that remembers the exec.Config value that was retrieved.
The effect should be comparable to the changes in https://github.com/docker/docker/pull/27467 (in that we now hold the libcontainerd client lock, and make sure that we don't obtain the Container object's lock by calling getExecConfig()), but without additional refactoring.

@ncdc could you test this out?

Can we get a brew/koji build?

@ncdc for which releases?

@nalind I have Fedora 24, RHEL 7.2, and RHEL 7.3 VMs. You pick? 😄

Try http://koji.fedoraproject.org/koji/taskinfo?taskID=16242921 for f24 scratch builds.  Thanks!

[test]please

retest this please

@rh-atomic-bot retest this please

https://github.com/projectatomic/docker/pull/209 - a completely different PR 3 days ago produces the same fatal error on testing (I believe)

@jwhonce tests are busted in RH CI, I usually run them locally before merging PR here

@runcom So we have this busted-ness and the containers/image busted-ness. This is being tested elsewhere

@jwhonce containers/image isn't busted anymore (your PR over there just requires a rebase now and it will be good to go).
As for the tests here, they are busted for various reason, such as, tests virtual machines running out of memory, cross compilation broken by some of our patches and whatnot. I would suggest having a Trello card to track a fix to our testing for projectatomic/docker and in the meantime just running tests locally as I do everytime.

FYI I wasn't able to begin testing this until just now. I'll keep the infinite loop running as long as it will go and report if/when I see it break.

So far so good. Still running. No flakes.

(F24)

docker-latest-1.12.2-2.git8f1975c.fc24.0.bz1389474.1.x86_64
docker-common-1.12.2-5.git8f1975c.fc25.x86_64
container-selinux-1.12.2-5.git8f1975c.fc25.x86_64

I'm not sure exactly how long it took, but my reproducer was able to reproduce the issue using the F24 RPMs listed above.

Taking a closer look at the F24 candidate builds here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=16242921
I'm afraid it looks like they do not actually contain this fix.  This commit is included in the SRPM as a patch but is not applied during the %prep process.  I'm re-running a build with these patches included and applied on top of docker-latest-1.12.3 and will update with a link if it is successful.

The x86_64 portion of the build has now finished successfully here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=16262294
You can confirm that the attach patch has applied in the build log:
https://kojipkgs.fedoraproject.org//work/tasks/2294/16262294/build.log
Apologies @ncdc but can you restart testing with this build?

My apologies.  I mistakenly assumed that the Fedora .spec used %autosetup, like the EL .spec does, and didn't double-check it.

@nalind - No worries

@ncdc - Is your reproducer something sufficiently well documented and/or scripted that some others of us could run it locally?

Yes. See the docker github issue I opened.
On Tuesday, November 1, 2016, Ian McLeod<EMAIL_ADDRESS>wrote:

@ncdc https://github.com/ncdc - Is your reproducer something
sufficiently well documented and/or scripted that some others of us could
run it locally?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/projectatomic/docker/pull/212#issuecomment-257554761,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABYu9cacC04AjzfONrL3gQQfONM2Bbks5q5zDLgaJpZM4Kj0c1
.

Ahh yes.  This:
https://github.com/docker/docker/issues/27289
@ncdc - Many thanks.
@runcom, @nalind, @jwhonce - See reproducer script in the issue linked above.

I just kicked off a new test using the new F24 RPM.

Any update?

I wasn't able to get it to flake
On Tue, Nov 8, 2016 at 5:36 AM Antonio Murdaca<EMAIL_ADDRESS>wrote:

Any update?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/projectatomic/docker/pull/212#issuecomment-259102702,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABYv8Oh5GVBYv40GZ34n4ko7K_oD1iks5q8FC0gaJpZM4Kj0c1
.

Great!!! ping @rhatdan @imcleod @jwhonce

it failed for me last night on rhel 7.3.0 and 1.12.3-4.  Here is my setup and load:
running in container
running in container
running in container
running in container
running in container
rpc error: code = 2 desc = containerd: container not started
OMG
[root@rhel-730 ~]#
[root@rhel-730 ~]# docker ps
CONTAINER ID        IMAGE                                     COMMAND                  CREATED             STATUS              PORTS                            NAMES
ea8413ec4d93        httpd                                     "httpd-foreground"       14 hours ago        Up 14 hours         80/tcp                           loving_agnesi
165d5a7aba11        nginx                                     "nginx -g 'daemon off"   16 hours ago        Up 16 hours         80/tcp, 443/tcp                  nginx
04f9249f23e9        cockpit/kubernetes:latest                 "/usr/libexec/cockpit"   16 hours ago        Up 16 hours         <IP_ADDRESS>:9090->9090/tcp           atomic-registry-console
5d3bd0447229        openshift/origin:latest                   "/usr/bin/openshift s"   16 hours ago        Up 16 hours         53/tcp, <IP_ADDRESS>:8443->8443/tcp   atomic-registry-master
b1f6b13574e2        openshift/origin-docker-registry:latest   "/bin/sh -c 'DOCKER_R"   16 hours ago        Up 16 hours                                          atomic-registry
[root@rhel-730 ~]# docker version
Client:
Version:         1.12.3
API version:     1.24
Package version: docker-common-1.12.3-4.el7.x86_64
Go version:      go1.6.2
Git commit:      f320458-redhat
Built:           Mon Nov  7 10:15:24 2016
OS/Arch:         linux/amd64
Server:
Version:         1.12.3
API version:     1.24
Package version: docker-common-1.12.3-4.el7.x86_64
Go version:      go1.6.2
Git commit:      f320458-redhat
Built:           Mon Nov  7 10:15:24 2016
OS/Arch:         linux/amd64
[root@rhel-730 ~]#

I commented on the bz. This is a different failure condition.


Graphical Glitches

Sometimes the screen would be filled with a colour and the graphics that this script adds. So far, I've seen blue and green cover the screen

Duplicate of phantom bug

Issue #452 - fix in progress

It's fixed as of right now.


Looking for a way to reuse the same schema with .merge

Hi,
Hope you're fine!
I would like some guidance here, because I did not find any answer through multiple researches, and it is maybe a bug. I would like to know if I'm doing wrong or if a bug is  likely to be suspected here or inside nestjs/swagger
Here are my schemas:
// Some utils I would like to reuse

export const stringToDateString = z
	.string()
	.refine(val => !Number.isNaN(Date.parse(val)), {
		message: 'Invalid datetime string',
	})
	.transform(val => new Date(val).toISOString());

export const dateToDateString = z.date().transform(date => date.toISOString());

export const dateToDatelike = z.union([stringToDateString, dateToDateString]);

export const startAndEndDates = z
	.object({
		start_date: dateToDatelike,
		end_date: dateToDatelike,
	})
	.refine(
		({ start_date, end_date }) =>
			isBefore(new Date(start_date), new Date(end_date)),
		{
			message: 'La date de début dépasse la date de fin',
		}
	);

// ##### Phase schema #####

const base = z.object({
	// Some properties
});

export const PhaseSchema = base.merge(startAndEndDates.innerType());

// ##### Cycle Schema #####

const base = z.object({
	// Some properties
});

export const CycleSchema = base.merge(startAndEndDates.innerType());

If I'm doing this, I'm getting this error:
Error: A circular dependency has been detected (property key: "start_date"). Please, make sure that each side of a bidirectional relationships are using lazy resolvers ("type: () => ClassType").
This error is generated by @nestjs/swagger, but I'm not sure this is related, and I think the root cause is my schema.
It's worth noting that I also tried using z.lazy(), according to the mentionned error, in many ways but without success.
Is anyone can help here ? It could be interesting to have this kind of usecase directly in the documentation 😄
Have a nice day

The "lazy resolvers" they're talking about isn't z.lazy(). That error is coming from Nest (I think) not Zod. I'm not familiar with Nest, but this seems to be a bug in their cycle detection. Or if you're using @anatine/zod-nestjs it may be a bug there.


Correctly add new section ‘Package Design’

 PW: Add Term to Navigation and Scheduling Package Design under Trends


Cancel provisionee run when user cancels secret entry

This passes our local tests, but I wasn't able to get to the point in the desktop provisioning flow that makes this call with the desktop code that is in this branch (forked this morning).  I imagine @chrisnojima has it in a different branch.
So I'd like to wait to see if it works for @chrisnojima before merging.
r? @maxtaco and @chrisnojima

:+1:

tested w/ electron, works! :+1:


pm:drawstart event don't work in programatically mode

I enable drawing mode programatically. Event pm:drawstart don't triggered.
Example on jsfiddle: https://jsfiddle.net/ermakof/ehsc6vp4/16/

You're enabling drawing mode before you bind the event, thus the event can't trigger. If you first bind the event and then enable draw mode it works as supposed.
I updated your example to show how it works: https://jsfiddle.net/ehsc6vp4/33/

Thanks so much!


Module not found: Can't resolve 'material-ui/RadioButton'

I believe installer does not include all components. I have tried many components but none of them exists. I have even checked subfolders of material-ui.

no RadioButton
no AutoComplete

There are more. How can we install them? I have tried each of following and none of them is working...
npm i -S material-ui
npm i -S material-ui@next
npm i -S material-ui@release
My versions:
"material-ui": "^1.0.0-beta.21",
"react": "^16.1.1",

You are installing material-ui wrongly.
https://docs.npmjs.com/cli/install
It should be:
npm install material-ui@next --save

This is how i have innstalled it. I am not soing anything wrong. What i am doing is following their instructions:
https://material-ui-next.com/getting-started/installation/
Following instructions at https://material-ui-next.com/guides/migration-v0.x I have fixed it using:
npm install material-ui@latest
npm install material-ui-next@latest
And now of course another problem:
TypeError: Cannot read property 'prepareStyles' of undefined

Have you properly finished all the steps of the guide?
You do not mention going through step 2 and 3.

Run the migration helper on your project.
After that, you are free to migrate one component instance at the time.

What i did is just used npm commands i have written in my previous post. So I could install. I can import. But the problem occurs once i try to use it. I am getting this error.

Most of documentations are lack of explanation. I see that migration helper also have problem.
jscodeshift -t
What exactly do i need to run here?

Let's say i am trying to use
import AutoComplete from 'material-ui/AutoComplete';
How can i do the migration?

@Dumanix I suggest you to browse the documentation of v1.
there is no RadioButton on the V1 branch check this, see https://material-ui-next.com/demos/selection-controls/#radio-buttons
There is directly no Autocomplete, but you could build one with third parties library, see https://material-ui-next.com/demos/autocomplete/

It looks like there is?
import Radio, { RadioGroup } from 'material-ui/Radio';
Also they advertise like they have AutoComplete

Well this issue is not solved but closed...

The redux-form tutorials still, as of Apr 2019, reference the old names related to RadioButton. If you landed here by a google search for the missing function names: it appears the logic still exists in @material-ui (not material-ui), but the redux-form tutorial still needs to be updated to the current names in material-ui version 0.20.2+.
Reference: redux-form 7.3.0 example.

https://redux-form.com/8.1.0/examples/material-ui/ uses the namespaced packages. The only issue is the codesandbox.


Move bundle-size-tools to new build-tools

bundle-size-tools have been moved from tools\bundle-size-tools to build-tools\packages\bundle-size-tools. The intention for this move is to have bundle-size-tools as part of the same release group.
git mv has been used
AB#1611

@tylerbutler -- I don't know why the build-tools CI is failing. can you please take a look at it?


Phoenix Generators

I think it would be great to get some phoenix generators in here. This is my "best case" api
mix jsonapi.gen.resource User users name:string email:string bio:string number_of_pets:integer
* creating priv/repo/migrations/20150409213440_create_user.exs
* creating web/models/user.ex
* creating test/models/user_test.exs
* creating web/controllers/user_controller.ex
* creating web/views/user_view.ex
* creating test/controllers/user_controller_test.exs

Add the resource to your browser scope in web/router.ex:

    resources "/users", UserController

and then update your repository by running migrations:

    $ mix ecto.migrate

And then
mix jsonapi.gen.resource Post posts title:string body:string belongs_to:User
* creating priv/repo/migrations/20150409213440_create_post.exs
* creating web/models/post.ex
* creating test/models/post_test.exs
* creating web/controllers/post_controller.ex
* creating web/views/post_view.ex
* creating test/controllers/post_controller_test.exs

Add the resource to your browser scope in web/router.ex:

    resources "/posts", PostController
    #TODO Figure out all the different LINKS routes we can insert here

and then update your repository by running migrations:

    $ mix ecto.migrate

Then you could do a
GET /posts?include=user&fields=title,body,user.name&order=-posts.created_at
And it would work out of the box.

Switching over a project soon, so I'll see if I can provide some unique insight!

Awesome feedback! I don't personally use the generators and have found maintaining them to be a tad bit a pain over time (we've got generators here: https://github.com/slime-lang/phoenix_slime).
That said if someone wants to do the work and maintain them as things change with Ecto, Phoenix, etc then we should keep this open 👍


ICRC-29 Allow redirect by signer to different origin

Updated the spec to allow for redirect by the signer to a different origin. Previously a PR was made to switch to polling to make this possible but e.g. the authentication part in the spec did not allow for a signer origin that changes due to e.g. a redirect.
Also a note has been added regarding closing the signer window.

After some more testing, if the signer redirects after the page has loaded with e.g. JS, the opener will be lost after the redirect to the new domain. But if the redirect to another domain is done by e.g. a 301 or 308 http response header, the opener will be available and working.
So the changes in this MR will enable a signer to change it's domain name while redirecting it's old domain name for relying parties that still interact with the old domain name.

Updated implementation that includes these changes can be found at https://github.com/slide-computer/signer-js/blob/main/packages/signer/src/icrc29/postMessageTransport.ts

@frederikrothenberger Updated the MR as discussed in last WG meeting.


Fix - Quay Storage Directory

Currently if you run the installer with a user that does not have UID = 1000 and has a umask that is not 002 (e.g. 027) and quayStorage pointing to a (not yet) existing dir. The container wil not have permissions to write files in the directory. The commit should fix this.
The describe situation results in bad gateway 502 errors in when pushing to the registry. In the quay-app this results in various permission denied errors in the logs.

/cherry-pick mirror-registry-2.0-rhel-8


Create umbraco-marketplace.json

Hi @idseefeld - I noted you'd listed this package on the Umbraco marketplace, so firstly, thanks for taking the time to do that.  I noticed though that we only have the details collected from NuGet for the package... which is fine, but to help it to be found more easily it's possible to provide additional information, as is discussed here.
To get started with this I've created this PR, which will at least ensure your package is listed under what looks to be the appropriate category.  You can add more, like more tags, links, or extended descriptions and readme information.  I hope that's useful for you.

👍@AndyButland Thank you Andy!


Indicator Ingestion Loops Indefinitely

Loops indefinitely (every hour) after ingesting Indicators
Command:
python3 misp_import.py -f -nb -d -v -p -i
The following Hash shows the hourly repeat cycle
sudo grep -i 308648c0db  /var/log/messages > crowdstrike-ioc-loop.log
(.ohm) [rx118r@md2nj02ap:~]$ more crowdstrike-ioc-loop.log
Apr  9 10:54:31 <IP_ADDRESS> docker: md2nj02ap misp-dev3[18458]: add -- Attribute (513760240) from Event (2016952): Payload delivery/sha256 308648c0dbd0ceeceadcdfdfd9e5be68e004eeab286d910b3af3cac81b292f4b -- Attribute "308648c0dbd0ceeceadcdfdfd9e5be68e004
eeab286d910b3af3cac81b292f4b" (513760240) added by User<EMAIL_ADDRESS>(238).
Apr  9 11:34:01 <IP_ADDRESS> docker: md2nj02ap misp-dev3[12922]: edit -- Attribute (513760240) from Event (2016952): Payload delivery/sha256 308648c0dbd0ceeceadcdfdfd9e5be68e004eeab286d910b3af3cac81b292f4b -- Attribute "308648c0dbd0ceeceadcdfdfd9e5be68e00
4eeab286d910b3af3cac81b292f4b" (513760240) updated by User<EMAIL_ADDRESS>(238).
Apr  9 12:32:16 <IP_ADDRESS> docker: md2nj02ap misp-dev3[5952]: edit -- Attribute (513760240) from Event (2016952): Payload delivery/sha256 308648c0dbd0ceeceadcdfdfd9e5be68e004eeab286d910b3af3cac81b292f4b -- Attribute "308648c0dbd0ceeceadcdfdfd9e5be68e004
eeab286d910b3af3cac81b292f4b" (513760240) updated by User<EMAIL_ADDRESS>(238).

Snipped Log

python3 misp_import.py -f -nb -d -v -p -i
[2023-04-08 18:43:13,699] INFO     misp_tools    MISP Import for CrowdStrike Threat Intelligence v0.6.8
[2023-04-08 18:43:13,699] INFO     config  CHECK CONFIG
[2023-04-08 18:43:13,700] DEBUG    config  client_id                                   value redacted, check config file
[2023-04-08 18:43:13,700] DEBUG    config  client_secret                               value redacted, check config file
[2023-04-08 18:43:13,700] DEBUG    config  crowdstrike_url                             US1
[2023-04-08 18:43:13,700] DEBUG    config  api_request_max                             5000
[2023-04-08 18:43:13,700] DEBUG    config  api_enable_ssl                              True
[2023-04-08 18:43:13,700] DEBUG    config  reports_timestamp_filename                  lastReportsUpdate.dat
[2023-04-08 18:43:13,700] DEBUG    config  indicators_timestamp_filename               lastIndicatorsUpdate.dat
[2023-04-08 18:43:13,700] DEBUG    config  actors_timestamp_filename                   lastActorsUpdate.dat
[2023-04-08 18:43:13,700] DEBUG    config  init_reports_days_before                    365
[2023-04-08 18:43:13,700] DEBUG    config  init_indicators_minutes_before              20220
[2023-04-08 18:43:13,700] DEBUG    config  init_actors_days_before                     730
[2023-04-08 18:43:13,700] DEBUG    config  reports_unique_tag                          CrowdStrike: REPORT
[2023-04-08 18:43:13,700] DEBUG    config  indicators_unique_tag                       CrowdStrike: INDICATOR
[2023-04-08 18:43:13,700] DEBUG    config  actors_unique_tag                           CrowdStrike: ACTOR
[2023-04-08 18:43:13,700] DEBUG    config  reports_tags                                att:source="Crowdstrike.Report"
[2023-04-08 18:43:13,700] DEBUG    config  indicators_tags                             att:source="Crowdstrike.Indicators"
[2023-04-08 18:43:13,700] DEBUG    config  actors_tags                                 att:source="Crowdstrike.Actors"
[2023-04-08 18:43:13,700] DEBUG    config  unknown_mapping                             CrowdStrike:indicator:galaxy: UNATTRIBUTED
[2023-04-08 18:43:13,700] DEBUG    config  unattributed_title                          CrowdStrike Unattributed indicators:
[2023-04-08 18:43:13,700] DEBUG    config  indicator_type_title                        Indicator Type:
[2023-04-08 18:43:13,700] DEBUG    config  malware_family_title                        Malware Family:
[2023-04-08 18:43:13,700] DEBUG    config  log_duplicates_as_sightings                 True
[2023-04-08 18:43:13,700] DEBUG    config  misp_url                                    https://3samisp
[2023-04-08 18:43:13,700] DEBUG    config  misp_auth_key                               value redacted, check config file
[2023-04-08 18:43:13,700] DEBUG    config  crowdstrike_org_uuid                        ca4f4b5d-db04-4a5e-a6de-e60636dc01be
[2023-04-08 18:43:13,700] DEBUG    config  misp_enable_ssl                             False
[2023-04-08 18:43:13,700] WARNING  config  misp_enable_ssl                             SSL is disabled for MISP API requests
[2023-04-08 18:43:13,701] DEBUG    config  ind_attribute_batch_size                    2500
[2023-04-08 18:43:13,701] DEBUG    config  event_save_memory_refresh_interval          180
[2023-04-08 18:43:13,701] DEBUG    config  max_threads                                 16
[2023-04-08 18:43:13,701] DEBUG    config  miss_track_file                             no_galaxy_mapping.log
[2023-04-08 18:43:13,701] DEBUG    config  galaxies_map_file                           galaxy.ini
[2023-04-08 18:43:13,701] DEBUG    config  tag_unknown_galaxy_maps                     True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_kill-chain                        True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_information-security-data-source  True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_type                              True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_iep                               False
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_iep2                              True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_iep2_version                      False
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_tlp                               True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_workflow                          True
[2023-04-08 18:43:14,200] INFO     config  No configuration errors found (1 warning)
[2023-04-08 18:43:14,200] INFO     config
[2023-04-08 18:43:14,200] INFO     config  ____ _  _ ____ ____ _  _ ____    ___  ____ ____ ____ ____ ___
[2023-04-08 18:43:14,200] INFO     config  |    |__| |___ |    |_/  [__     |__] |__| [__  [__  |___ |  \
[2023-04-08 18:43:14,200] INFO     config  |___ |  | |___ |___ | \_ ___]    |    |  | ___] ___] |___ |__/
[2023-04-08 18:43:14,200] INFO     config
[2023-04-08 18:43:15,171] INFO     processor/main       BEGIN INDICATORS IMPORT
[2023-04-08 18:43:15,171] INFO     processor/main       Retrieving lookup data for import of CrowdStrike indicators into MISP.
[2023-04-08 18:43:15,477] INFO     processor/main       Adding 24 CrowdStrike indicator type events to MISP.
[2023-04-08 18:43:15,498] INFO     processor/main       Retrieved 0 CrowdStrike indicator malware family events from MISP.
[2023-04-08 18:43:15,559] INFO     processor/thread_9   Retrieved 15 coin_address indicators from MISP.
[2023-04-08 18:43:15,561] INFO     processor/thread_13  Retrieved 50 device_name indicators from MISP.
[2023-04-08 18:43:15,601] INFO     processor/thread_13  Retrieved 29 service_name indicators from MISP.
[2023-04-08 18:43:15,608] INFO     processor/thread_12  Retrieved 495 registry indicators from MISP.
[2023-04-08 18:43:15,670] INFO     processor/thread_8   Retrieved 309 bitcoin_address indicators from MISP.
[2023-04-08 18:43:15,927] INFO     processor/thread_7   Retrieved 3,922 mutex_name indicators from MISP.
[2023-04-08 18:43:15,994] INFO     processor/thread_12  Retrieved 449 port indicators from MISP.
[2023-04-08 18:43:16,043] INFO     processor/thread_3   Retrieved 1,770 hash_imphash indicators from MISP.
[2023-04-08 18:43:38,543] INFO     processor/thread_15  Retrieved 254 campaign_id indicators from MISP.
[2023-04-08 18:43:40,720] INFO     processor/thread_13  Retrieved 90,336 user_agent indicators from MISP.
[2023-04-08 18:43:50,679] INFO     processor/thread_5   Retrieved 201,177 file_path indicators from MISP.
[2023-04-08 18:43:54,259] INFO     processor/thread_4   Retrieved 201,177 file_name indicators from MISP.
[2023-04-08 18:44:01,788] INFO     processor/thread_2   Retrieved 412,962 hash_sha1 indicators from MISP.
[2023-04-08 18:44:11,313] INFO     processor/thread_10  Retrieved 69,724 email_address indicators from MISP.
[2023-04-08 18:46:12,074] INFO     processor/thread_14  Retrieved 1,612,502 domain indicators from MISP.
[2023-04-08 18:46:50,764] INFO     processor/thread_11  Retrieved 815,731 email_subject indicators from MISP.
[2023-04-08 18:50:00,881] INFO     processor/thread_1   Retrieved 2,934,089 hash_sha256 indicators from MISP.
[2023-04-08 18:52:23,975] INFO     processor/thread_0   Retrieved 3,477,861 hash_md5 indicators from MISP.
[2023-04-08 18:56:45,404] INFO     processor/thread_9   Retrieved 4,795,407 ip_address indicators from MISP.
[2023-04-08 19:26:34,611] INFO     processor/thread_6   Retrieved 16,710,078 url indicators from MISP.
[2023-04-08 19:26:57,388] INFO     processor/main       Found 0 pre-existing indicators within CrowdStrike reports.
[2023-04-08 19:27:18,498] INFO     processor/main       Starting import of CrowdStrike indicators into MISP.
[2023-04-08 19:27:39,189] INFO     processor/main       Retrieved 5,000 of 2,789,355 remaining indicators.
[2023-04-08 19:27:39,190] DEBUG    processor/main       Configuration states we should process batches of 2,500 indicators.
[2023-04-08 19:27:39,190] INFO     processor/main       Processing batch of 2,500 indicators.
[2023-04-08 19:27:39,191] DEBUG    processor/thread_0   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,191] DEBUG    processor/thread_0   Start creation of malware family event object
[2023-04-08 19:27:39,192] DEBUG    processor/thread_0   Complete initial malware family object creation
[2023-04-08 19:27:39,192] DEBUG    processor/thread_0   Successfully created malware family event for CobaltStrike
[2023-04-08 19:27:39,281] DEBUG    processor/thread_1   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,281] DEBUG    processor/thread_1   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,282] DEBUG    processor/thread_2   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,282] DEBUG    processor/thread_2   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,282] DEBUG    processor/thread_3   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,282] DEBUG    processor/thread_3   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,283] DEBUG    processor/thread_4   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,283] DEBUG    processor/thread_4   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,283] DEBUG    processor/thread_5   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,283] DEBUG    processor/thread_5   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_6   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_6   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_7   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_7   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_8   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_8   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_9   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,285] DEBUG    processor/thread_9   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,285] DEBUG    processor/thread_10  Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,285] DEBUG    processor/thread_10  Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,285] DEBUG    processor/thread_11  Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,285] DEBUG    processor/thread_11  Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,286] DEBUG    processor/thread_12  Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,286] DEBUG    processor/thread_12  Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,286] DEBUG    processor/thread_13  Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,286] DEBUG    processor/thread_13  Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,287] DEBUG    processor/thread_14  Malware Family identified: Emotet
[2023-04-08 19:27:39,287] DEBUG    processor/thread_14  Start creation of malware family event object
[2023-04-08 19:27:39,288] DEBUG    processor/thread_14  Complete initial malware family object creation
[2023-04-08 19:27:39,288] DEBUG    processor/thread_14  Successfully created malware family event for Emotet
[2023-04-08 19:27:39,382] DEBUG    processor/thread_15  Malware Family identified: Emotet
[2023-04-08 19:27:39,382] DEBUG    processor/thread_15  Found existing malware family event for Emotet
[2023-04-08 19:27:39,382] DEBUG    processor/thread_0   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,383] DEBUG    processor/thread_1   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,383] DEBUG    processor/thread_0   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,383] DEBUG    processor/thread_2   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,383] DEBUG    processor/thread_2   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,383] DEBUG    processor/thread_1   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,383] DEBUG    processor/thread_4   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,383] DEBUG    processor/thread_0   Tagged threat COMMODITY
[2023-04-08 19:27:39,383] DEBUG    processor/thread_5   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,383] DEBUG    processor/thread_3   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,384] DEBUG    processor/thread_7   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,384] DEBUG    processor/thread_2   Tagged threat COMMODITY
[2023-04-08 19:27:39,384] DEBUG    processor/thread_8   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,384] DEBUG    processor/thread_9   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,384] DEBUG    processor/thread_1   Tagged threat COMMODITY
[2023-04-08 19:27:39,384] DEBUG    processor/thread_10  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,384] DEBUG    processor/thread_11  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,386] DEBUG    processor/thread_11  Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,384] DEBUG    processor/thread_4   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,384] DEBUG    processor/thread_12  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,385] DEBUG    processor/thread_13  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,385] DEBUG    processor/thread_5   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,385] DEBUG    processor/thread_14  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,385] DEBUG    processor/thread_15  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,385] DEBUG    processor/thread_3   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,385] DEBUG    processor/thread_6   Malware Family identified: Emotet
[2023-04-08 19:27:39,385] DEBUG    processor/thread_7   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,385] DEBUG    processor/thread_2   Tagged threat CRIMINAL
[2023-04-08 19:27:39,385] DEBUG    processor/thread_8   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,385] DEBUG    processor/thread_9   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,385] DEBUG    processor/thread_1   Tagged threat CRIMINAL
[2023-04-08 19:27:39,385] DEBUG    processor/thread_10  Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,384] DEBUG    processor/thread_0   Tagged threat CRIMINAL
[2023-04-08 19:27:39,386] DEBUG    processor/thread_11  Tagged threat COMMODITY
[2023-04-08 19:27:39,386] DEBUG    processor/thread_4   Tagged threat COMMODITY
[2023-04-08 19:27:39,386] DEBUG    processor/thread_12  Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,386] DEBUG    processor/thread_13  Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,386] DEBUG    processor/thread_5   Tagged threat COMMODITY
[2023-04-08 19:27:39,386] DEBUG    processor/thread_14  Tagged malware EMOTET
[2023-04-08 19:27:39,386] DEBUG    processor/thread_15  Tagged malware EMOTET
[2023-04-08 19:27:39,386] DEBUG    processor/thread_3   Tagged threat COMMODITY
[2023-04-08 19:27:39,386] DEBUG    processor/thread_6   Found existing malware family event for Emotet
[2023-04-08 19:27:39,386] DEBUG    processor/thread_7   Tagged threat COMMODITY
[2023-04-08 19:27:39,386] DEBUG    processor/thread_2   Tagged threat RAT
[2023-04-08 19:27:39,387] DEBUG    processor/thread_8   Tagged threat COMMODITY
[2023-04-08 19:27:39,387] DEBUG    processor/thread_9   Tagged threat COMMODITY
[2023-04-08 19:27:39,387] DEBUG    processor/thread_1   Tagged threat RAT
[2023-04-08 19:27:39,387] DEBUG    processor/thread_10  Tagged threat COMMODITY
[2023-04-08 19:27:39,387] DEBUG    processor/thread_0   Tagged threat RAT
[2023-04-08 19:27:39,387] DEBUG    processor/thread_11  Tagged threat CRIMINAL
[2023-04-08 19:27:39,387] DEBUG    processor/thread_4   Tagged threat CRIMINAL
[2023-04-08 19:27:39,387] DEBUG    processor/thread_12  Tagged threat COMMODITY
[2023-04-08 19:27:39,387] DEBUG    processor/thread_13  Tagged threat COMMODITY
[2023-04-08 19:27:39,387] DEBUG    processor/thread_5   Tagged threat CRIMINAL
[2023-04-08 19:27:39,387] DEBUG    processor/thread_14  Tagged threat CRIMINAL
[2023-04-08 19:27:39,387] DEBUG    processor/thread_15  Tagged threat CRIMINAL
[2023-04-08 19:27:39,388] DEBUG    processor/thread_3   Tagged threat CRIMINAL
[2023-04-08 19:27:39,388] DEBUG    processor/thread_6   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,388] DEBUG    processor/thread_7   Tagged threat CRIMINAL
[2023-04-08 19:27:39,388] DEBUG    processor/thread_2   Added 47f3a99ed0aaa1b269f14888f3c8e5de032a0840b822d4574e95db68d3811688 indicators to event Indicator Type: SHA256 hashes
[2023-04-08 19:27:39,388] DEBUG    processor/thread_8   Tagged threat CRIMINAL
[2023-04-08 19:27:39,388] DEBUG    processor/thread_9   Tagged threat CRIMINAL
[2023-04-08 19:27:39,389] DEBUG    processor/thread_1   Added 36bb3d9152a14b9912b714714ada5a22 indicators to event Indicator Type: MD5 hashes
[2023-04-08 19:27:39,389] DEBUG    processor/thread_10  Tagged threat CRIMINAL
[2023-04-08 19:27:39,389] DEBUG    processor/thread_0   Added 5fd1a44bfdc904a775cfa81748f4aaad38036e3d indicators to event Indicator Type: SHA1 hashes
[2023-04-08 19:27:39,389] DEBUG    processor/thread_11  Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_4   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_12  Tagged threat CRIMINAL
[2023-04-08 19:27:39,390] DEBUG    processor/thread_13  Tagged threat CRIMINAL
[2023-04-08 19:27:39,390] DEBUG    processor/thread_5   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_14  Tagged threat DOWNLOADER
[2023-04-08 19:27:39,390] DEBUG    processor/thread_15  Tagged threat DOWNLOADER
[2023-04-08 19:27:39,390] DEBUG    processor/thread_3   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_6   Tagged malware EMOTET
[2023-04-08 19:27:39,390] DEBUG    processor/thread_7   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_2   Updated Malware Family: CobaltStrike event threat level to HIGH
[2023-04-08 19:27:39,390] DEBUG    processor/thread_8   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_9   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_10  Tagged threat RAT
[2023-04-08 19:27:39,391] DEBUG    processor/thread_12  Tagged threat RAT
[2023-04-08 19:27:39,391] DEBUG    processor/thread_13  Tagged threat RAT
[2023-04-08 19:27:39,393] DEBUG    processor/thread_6   Tagged threat CRIMINAL
[2023-04-08 19:27:39,394] DEBUG    processor/thread_11  Added 94f764473f2946521f4050be6f2d35b5 indicators to event Indicator Type: MD5 hashes
[2023-04-08 19:27:39,396] DEBUG    processor/thread_12  Added 89612615ce912b66a0394497efc5ee8cb6c49a25 indicators to event Indicator Type: SHA1 hashes
[2023-04-08 19:27:39,394] DEBUG    processor/thread_5   Added 5cbeb0a6c5a10eada07b4e9555b1bd3d indicators to event Indicator Type: MD5 hashes
[2023-04-08 19:27:39,395] DEBUG    processor/thread_14  Added 46d8f2195fb9e7d6fc0423422cd2f6e3 indicators to event Indicator Type: MD5 hashes
[2023-04-08 19:27:39,395] DEBUG    processor/thread_15  Added 1ca44f66a74a642426ee371f65964ee062abb9b77a83f7ce33cbdf99982ebe54 indicators to event Indicator Type: SHA256 hashes
[2023-04-08 19:27:39,395] DEBUG    processor/thread_3   Added 3be7535aaad8e5deb0a7b0ce21a4c5e3a2f3701e86c30b4b3846cdda25fa4feb indicators to event Indicator Type: SHA256 hashes
[2023-04-08 19:27:39,395] DEBUG    processor/thread_7   Added e98ee554b026f21b6aefd9c0018d618a254f378e91d12ee2169eec1198fd2124 indicators to event Indicator Type: SHA256 hashes
[2023-04-08 19:27:39,396] DEBUG    processor/thread_2   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,396] DEBUG    processor/thread_1   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,396] DEBUG    processor/thread_0   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,396] DEBUG    processor/thread_8   Added d9a61afbaf06e316abd49511f01ad2b83b970ea4 indicators to event Indicator Type: SHA1 hashes
[2023-04-08 19:27:39,396] DEBUG    processor/thread_6   Tagged threat DOWNLOADER
[2023-04-08 19:27:39,396] DEBUG    processor/thread_9   Added 360379b4abb8cffb2f75ede5f8e06df5 indicators to event Indicator Type: MD5 hashes
[2023-04-08 19:27:39,396] DEBUG    processor/thread_10  Added https://soguo.quest/multiply/archives/555EDYREXV indicators to event Indicator Type: Web addresses
[2023-04-08 19:27:39,394] DEBUG    processor/thread_4   Added a287f05c4f62ac867ad28239a41a474a1bb846a4 indicators to event Indicator Type: SHA1 hashes
[2023-04-08 19:27:39,396] DEBUG    processor/thread_13  Added b1722602adda0e01ad1629d538152a3f1ed22f40b04d67276d1ce140e7253381 indicators to event Indicator Type: SHA256 hashes
[2023-04-08 19:27:39,397] DEBUG    processor/thread_11  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,397] DEBUG    processor/thread_12  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,397] DEBUG    processor/thread_5   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,397] DEBUG    processor/thread_14  Updated Malware Family: Emotet event threat level to HIGH
[2023-04-08 19:27:39,397] DEBUG    processor/thread_2   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,398] DEBUG    processor/thread_1   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,398] DEBUG    processor/thread_0   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,398] DEBUG    processor/thread_11  Tagged malware COBALTSTRIKE
python3 misp_import.py -f -nb -d -v -p -i
[2023-04-08 18:43:13,699] INFO     misp_tools    MISP Import for CrowdStrike Threat Intelligence v0.6.8
[2023-04-08 18:43:13,699] INFO     config  CHECK CONFIG
[2023-04-08 18:43:13,700] DEBUG    config  client_id                                   value redacted, check config file
[2023-04-08 18:43:13,700] DEBUG    config  client_secret                               value redacted, check config file
[2023-04-08 18:43:13,700] DEBUG    config  crowdstrike_url                             US1
[2023-04-08 18:43:13,700] DEBUG    config  api_request_max                             5000
[2023-04-08 18:43:13,700] DEBUG    config  api_enable_ssl                              True
[2023-04-08 18:43:13,700] DEBUG    config  reports_timestamp_filename                  lastReportsUpdate.dat
[2023-04-08 18:43:13,700] DEBUG    config  indicators_timestamp_filename               lastIndicatorsUpdate.dat
[2023-04-08 18:43:13,700] DEBUG    config  actors_timestamp_filename                   lastActorsUpdate.dat
[2023-04-08 18:43:13,700] DEBUG    config  init_reports_days_before                    365
[2023-04-08 18:43:13,700] DEBUG    config  init_indicators_minutes_before              20220
[2023-04-08 18:43:13,700] DEBUG    config  init_actors_days_before                     730
[2023-04-08 18:43:13,700] DEBUG    config  reports_unique_tag                          CrowdStrike: REPORT
[2023-04-08 18:43:13,700] DEBUG    config  indicators_unique_tag                       CrowdStrike: INDICATOR
[2023-04-08 18:43:13,700] DEBUG    config  actors_unique_tag                           CrowdStrike: ACTOR
[2023-04-08 18:43:13,700] DEBUG    config  reports_tags                                att:source="Crowdstrike.Report"
[2023-04-08 18:43:13,700] DEBUG    config  indicators_tags                             att:source="Crowdstrike.Indicators"
[2023-04-08 18:43:13,700] DEBUG    config  actors_tags                                 att:source="Crowdstrike.Actors"
[2023-04-08 18:43:13,700] DEBUG    config  unknown_mapping                             CrowdStrike:indicator:galaxy: UNATTRIBUTED
[2023-04-08 18:43:13,700] DEBUG    config  unattributed_title                          CrowdStrike Unattributed indicators:
[2023-04-08 18:43:13,700] DEBUG    config  indicator_type_title                        Indicator Type:
[2023-04-08 18:43:13,700] DEBUG    config  malware_family_title                        Malware Family:
[2023-04-08 18:43:13,700] DEBUG    config  log_duplicates_as_sightings                 True
[2023-04-08 18:43:13,700] DEBUG    config  misp_url                                    https://3samisp
[2023-04-08 18:43:13,700] DEBUG    config  misp_auth_key                               value redacted, check config file
[2023-04-08 18:43:13,700] DEBUG    config  crowdstrike_org_uuid                        ca4f4b5d-db04-4a5e-a6de-e60636dc01be
[2023-04-08 18:43:13,700] DEBUG    config  misp_enable_ssl                             False
[2023-04-08 18:43:13,700] WARNING  config  misp_enable_ssl                             SSL is disabled for MISP API requests
[2023-04-08 18:43:13,701] DEBUG    config  ind_attribute_batch_size                    2500
[2023-04-08 18:43:13,701] DEBUG    config  event_save_memory_refresh_interval          180
[2023-04-08 18:43:13,701] DEBUG    config  max_threads                                 16
[2023-04-08 18:43:13,701] DEBUG    config  miss_track_file                             no_galaxy_mapping.log
[2023-04-08 18:43:13,701] DEBUG    config  galaxies_map_file                           galaxy.ini
[2023-04-08 18:43:13,701] DEBUG    config  tag_unknown_galaxy_maps                     True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_kill-chain                        True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_information-security-data-source  True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_type                              True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_iep                               False
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_iep2                              True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_iep2_version                      False
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_tlp                               True
[2023-04-08 18:43:13,701] DEBUG    config  taxonomic_workflow                          True
[2023-04-08 18:43:14,200] INFO     config  No configuration errors found (1 warning)
[2023-04-08 18:43:14,200] INFO     config
[2023-04-08 18:43:14,200] INFO     config  ____ _  _ ____ ____ _  _ ____    ___  ____ ____ ____ ____ ___
[2023-04-08 18:43:14,200] INFO     config  |    |__| |___ |    |_/  [__     |__] |__| [__  [__  |___ |  \
[2023-04-08 18:43:14,200] INFO     config  |___ |  | |___ |___ | \_ ___]    |    |  | ___] ___] |___ |__/
[2023-04-08 18:43:14,200] INFO     config
[2023-04-08 18:43:15,171] INFO     processor/main       BEGIN INDICATORS IMPORT
[2023-04-08 18:43:15,171] INFO     processor/main       Retrieving lookup data for import of CrowdStrike indicators into MISP.
[2023-04-08 18:43:15,477] INFO     processor/main       Adding 24 CrowdStrike indicator type events to MISP.
[2023-04-08 18:43:15,498] INFO     processor/main       Retrieved 0 CrowdStrike indicator malware family events from MISP.
[2023-04-08 18:43:15,559] INFO     processor/thread_9   Retrieved 15 coin_address indicators from MISP.
[2023-04-08 18:43:15,561] INFO     processor/thread_13  Retrieved 50 device_name indicators from MISP.
[2023-04-08 18:43:15,601] INFO     processor/thread_13  Retrieved 29 service_name indicators from MISP.
[2023-04-08 18:43:15,608] INFO     processor/thread_12  Retrieved 495 registry indicators from MISP.
[2023-04-08 18:43:15,670] INFO     processor/thread_8   Retrieved 309 bitcoin_address indicators from MISP.
[2023-04-08 18:43:15,927] INFO     processor/thread_7   Retrieved 3,922 mutex_name indicators from MISP.
[2023-04-08 18:43:15,994] INFO     processor/thread_12  Retrieved 449 port indicators from MISP.
[2023-04-08 18:43:16,043] INFO     processor/thread_3   Retrieved 1,770 hash_imphash indicators from MISP.
[2023-04-08 18:43:38,543] INFO     processor/thread_15  Retrieved 254 campaign_id indicators from MISP.
[2023-04-08 18:43:40,720] INFO     processor/thread_13  Retrieved 90,336 user_agent indicators from MISP.
[2023-04-08 18:43:50,679] INFO     processor/thread_5   Retrieved 201,177 file_path indicators from MISP.
[2023-04-08 18:43:54,259] INFO     processor/thread_4   Retrieved 201,177 file_name indicators from MISP.
[2023-04-08 18:44:01,788] INFO     processor/thread_2   Retrieved 412,962 hash_sha1 indicators from MISP.
[2023-04-08 18:44:11,313] INFO     processor/thread_10  Retrieved 69,724 email_address indicators from MISP.
[2023-04-08 18:46:12,074] INFO     processor/thread_14  Retrieved 1,612,502 domain indicators from MISP.
[2023-04-08 18:46:50,764] INFO     processor/thread_11  Retrieved 815,731 email_subject indicators from MISP.
[2023-04-08 18:50:00,881] INFO     processor/thread_1   Retrieved 2,934,089 hash_sha256 indicators from MISP.
[2023-04-08 18:52:23,975] INFO     processor/thread_0   Retrieved 3,477,861 hash_md5 indicators from MISP.
[2023-04-08 18:56:45,404] INFO     processor/thread_9   Retrieved 4,795,407 ip_address indicators from MISP.
[2023-04-08 19:26:34,611] INFO     processor/thread_6   Retrieved 16,710,078 url indicators from MISP.
[2023-04-08 19:26:57,388] INFO     processor/main       Found 0 pre-existing indicators within CrowdStrike reports.
[2023-04-08 19:27:18,498] INFO     processor/main       Starting import of CrowdStrike indicators into MISP.
[2023-04-08 19:27:39,189] INFO     processor/main       Retrieved 5,000 of 2,789,355 remaining indicators.
[2023-04-08 19:27:39,190] DEBUG    processor/main       Configuration states we should process batches of 2,500 indicators.
[2023-04-08 19:27:39,190] INFO     processor/main       Processing batch of 2,500 indicators.
[2023-04-08 19:27:39,191] DEBUG    processor/thread_0   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,191] DEBUG    processor/thread_0   Start creation of malware family event object
[2023-04-08 19:27:39,192] DEBUG    processor/thread_0   Complete initial malware family object creation
[2023-04-08 19:27:39,192] DEBUG    processor/thread_0   Successfully created malware family event for CobaltStrike
[2023-04-08 19:27:39,281] DEBUG    processor/thread_1   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,281] DEBUG    processor/thread_1   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,282] DEBUG    processor/thread_2   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,282] DEBUG    processor/thread_2   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,282] DEBUG    processor/thread_3   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,282] DEBUG    processor/thread_3   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,283] DEBUG    processor/thread_4   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,283] DEBUG    processor/thread_4   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,283] DEBUG    processor/thread_5   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,283] DEBUG    processor/thread_5   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_6   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_6   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_7   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_7   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_8   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_8   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,284] DEBUG    processor/thread_9   Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,285] DEBUG    processor/thread_9   Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,285] DEBUG    processor/thread_10  Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,285] DEBUG    processor/thread_10  Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,285] DEBUG    processor/thread_11  Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,285] DEBUG    processor/thread_11  Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,286] DEBUG    processor/thread_12  Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,286] DEBUG    processor/thread_12  Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,286] DEBUG    processor/thread_13  Malware Family identified: CobaltStrike
[2023-04-08 19:27:39,286] DEBUG    processor/thread_13  Found existing malware family event for CobaltStrike
[2023-04-08 19:27:39,287] DEBUG    processor/thread_14  Malware Family identified: Emotet
[2023-04-08 19:27:39,287] DEBUG    processor/thread_14  Start creation of malware family event object
[2023-04-08 19:27:39,288] DEBUG    processor/thread_14  Complete initial malware family object creation
[2023-04-08 19:27:39,288] DEBUG    processor/thread_14  Successfully created malware family event for Emotet
[2023-04-08 19:27:39,382] DEBUG    processor/thread_15  Malware Family identified: Emotet
[2023-04-08 19:27:39,382] DEBUG    processor/thread_15  Found existing malware family event for Emotet
[2023-04-08 19:27:39,382] DEBUG    processor/thread_0   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,383] DEBUG    processor/thread_1   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,383] DEBUG    processor/thread_0   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,383] DEBUG    processor/thread_2   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,383] DEBUG    processor/thread_2   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,383] DEBUG    processor/thread_1   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,383] DEBUG    processor/thread_4   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,383] DEBUG    processor/thread_0   Tagged threat COMMODITY
[2023-04-08 19:27:39,383] DEBUG    processor/thread_5   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,383] DEBUG    processor/thread_3   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,384] DEBUG    processor/thread_7   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,384] DEBUG    processor/thread_2   Tagged threat COMMODITY
[2023-04-08 19:27:39,384] DEBUG    processor/thread_8   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,384] DEBUG    processor/thread_9   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,384] DEBUG    processor/thread_1   Tagged threat COMMODITY
[2023-04-08 19:27:39,384] DEBUG    processor/thread_10  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,384] DEBUG    processor/thread_11  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,386] DEBUG    processor/thread_11  Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,384] DEBUG    processor/thread_4   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,384] DEBUG    processor/thread_12  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,385] DEBUG    processor/thread_13  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,385] DEBUG    processor/thread_5   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,385] DEBUG    processor/thread_14  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,385] DEBUG    processor/thread_15  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,385] DEBUG    processor/thread_3   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,385] DEBUG    processor/thread_6   Malware Family identified: Emotet
[2023-04-08 19:27:39,385] DEBUG    processor/thread_7   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,385] DEBUG    processor/thread_2   Tagged threat CRIMINAL
[2023-04-08 19:27:39,385] DEBUG    processor/thread_8   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,385] DEBUG    processor/thread_9   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,385] DEBUG    processor/thread_1   Tagged threat CRIMINAL
[2023-04-08 19:27:39,385] DEBUG    processor/thread_10  Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,384] DEBUG    processor/thread_0   Tagged threat CRIMINAL
[2023-04-08 19:27:39,386] DEBUG    processor/thread_11  Tagged threat COMMODITY
[2023-04-08 19:27:39,386] DEBUG    processor/thread_4   Tagged threat COMMODITY
[2023-04-08 19:27:39,386] DEBUG    processor/thread_12  Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,386] DEBUG    processor/thread_13  Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,386] DEBUG    processor/thread_5   Tagged threat COMMODITY
[2023-04-08 19:27:39,386] DEBUG    processor/thread_14  Tagged malware EMOTET
[2023-04-08 19:27:39,386] DEBUG    processor/thread_15  Tagged malware EMOTET
[2023-04-08 19:27:39,386] DEBUG    processor/thread_3   Tagged threat COMMODITY
[2023-04-08 19:27:39,386] DEBUG    processor/thread_6   Found existing malware family event for Emotet
[2023-04-08 19:27:39,386] DEBUG    processor/thread_7   Tagged threat COMMODITY
[2023-04-08 19:27:39,386] DEBUG    processor/thread_2   Tagged threat RAT
[2023-04-08 19:27:39,387] DEBUG    processor/thread_8   Tagged threat COMMODITY
[2023-04-08 19:27:39,387] DEBUG    processor/thread_9   Tagged threat COMMODITY
[2023-04-08 19:27:39,387] DEBUG    processor/thread_1   Tagged threat RAT
[2023-04-08 19:27:39,387] DEBUG    processor/thread_10  Tagged threat COMMODITY
[2023-04-08 19:27:39,387] DEBUG    processor/thread_0   Tagged threat RAT
[2023-04-08 19:27:39,387] DEBUG    processor/thread_11  Tagged threat CRIMINAL
[2023-04-08 19:27:39,387] DEBUG    processor/thread_4   Tagged threat CRIMINAL
[2023-04-08 19:27:39,387] DEBUG    processor/thread_12  Tagged threat COMMODITY
[2023-04-08 19:27:39,387] DEBUG    processor/thread_13  Tagged threat COMMODITY
[2023-04-08 19:27:39,387] DEBUG    processor/thread_5   Tagged threat CRIMINAL
[2023-04-08 19:27:39,387] DEBUG    processor/thread_14  Tagged threat CRIMINAL
[2023-04-08 19:27:39,387] DEBUG    processor/thread_15  Tagged threat CRIMINAL
[2023-04-08 19:27:39,388] DEBUG    processor/thread_3   Tagged threat CRIMINAL
[2023-04-08 19:27:39,388] DEBUG    processor/thread_6   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,388] DEBUG    processor/thread_7   Tagged threat CRIMINAL
[2023-04-08 19:27:39,388] DEBUG    processor/thread_2   Added 47f3a99ed0aaa1b269f14888f3c8e5de032a0840b822d4574e95db68d3811688 indicators to event Indicator Type: SHA256 hashes
[2023-04-08 19:27:39,388] DEBUG    processor/thread_8   Tagged threat CRIMINAL
[2023-04-08 19:27:39,388] DEBUG    processor/thread_9   Tagged threat CRIMINAL
[2023-04-08 19:27:39,389] DEBUG    processor/thread_1   Added 36bb3d9152a14b9912b714714ada5a22 indicators to event Indicator Type: MD5 hashes
[2023-04-08 19:27:39,389] DEBUG    processor/thread_10  Tagged threat CRIMINAL
[2023-04-08 19:27:39,389] DEBUG    processor/thread_0   Added 5fd1a44bfdc904a775cfa81748f4aaad38036e3d indicators to event Indicator Type: SHA1 hashes
[2023-04-08 19:27:39,389] DEBUG    processor/thread_11  Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_4   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_12  Tagged threat CRIMINAL
[2023-04-08 19:27:39,390] DEBUG    processor/thread_13  Tagged threat CRIMINAL
[2023-04-08 19:27:39,390] DEBUG    processor/thread_5   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_14  Tagged threat DOWNLOADER
[2023-04-08 19:27:39,390] DEBUG    processor/thread_15  Tagged threat DOWNLOADER
[2023-04-08 19:27:39,390] DEBUG    processor/thread_3   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_6   Tagged malware EMOTET
[2023-04-08 19:27:39,390] DEBUG    processor/thread_7   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_2   Updated Malware Family: CobaltStrike event threat level to HIGH
[2023-04-08 19:27:39,390] DEBUG    processor/thread_8   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_9   Tagged threat RAT
[2023-04-08 19:27:39,390] DEBUG    processor/thread_10  Tagged threat RAT
[2023-04-08 19:27:39,391] DEBUG    processor/thread_12  Tagged threat RAT
[2023-04-08 19:27:39,391] DEBUG    processor/thread_13  Tagged threat RAT
[2023-04-08 19:27:39,393] DEBUG    processor/thread_6   Tagged threat CRIMINAL
[2023-04-08 19:27:39,394] DEBUG    processor/thread_11  Added 94f764473f2946521f4050be6f2d35b5 indicators to event Indicator Type: MD5 hashes
[2023-04-08 19:27:39,396] DEBUG    processor/thread_12  Added 89612615ce912b66a0394497efc5ee8cb6c49a25 indicators to event Indicator Type: SHA1 hashes
[2023-04-08 19:27:39,394] DEBUG    processor/thread_5   Added 5cbeb0a6c5a10eada07b4e9555b1bd3d indicators to event Indicator Type: MD5 hashes
[2023-04-08 19:27:39,395] DEBUG    processor/thread_14  Added 46d8f2195fb9e7d6fc0423422cd2f6e3 indicators to event Indicator Type: MD5 hashes
[2023-04-08 19:27:39,395] DEBUG    processor/thread_15  Added 1ca44f66a74a642426ee371f65964ee062abb9b77a83f7ce33cbdf99982ebe54 indicators to event Indicator Type: SHA256 hashes
[2023-04-08 19:27:39,395] DEBUG    processor/thread_3   Added 3be7535aaad8e5deb0a7b0ce21a4c5e3a2f3701e86c30b4b3846cdda25fa4feb indicators to event Indicator Type: SHA256 hashes
[2023-04-08 19:27:39,395] DEBUG    processor/thread_7   Added e98ee554b026f21b6aefd9c0018d618a254f378e91d12ee2169eec1198fd2124 indicators to event Indicator Type: SHA256 hashes
[2023-04-08 19:27:39,396] DEBUG    processor/thread_2   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,396] DEBUG    processor/thread_1   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,396] DEBUG    processor/thread_0   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,396] DEBUG    processor/thread_8   Added d9a61afbaf06e316abd49511f01ad2b83b970ea4 indicators to event Indicator Type: SHA1 hashes
[2023-04-08 19:27:39,396] DEBUG    processor/thread_6   Tagged threat DOWNLOADER
[2023-04-08 19:27:39,396] DEBUG    processor/thread_9   Added 360379b4abb8cffb2f75ede5f8e06df5 indicators to event Indicator Type: MD5 hashes
[2023-04-08 19:27:39,396] DEBUG    processor/thread_10  Added https://soguo.quest/multiply/archives/555EDYREXV indicators to event Indicator Type: Web addresses
[2023-04-08 19:27:39,394] DEBUG    processor/thread_4   Added a287f05c4f62ac867ad28239a41a474a1bb846a4 indicators to event Indicator Type: SHA1 hashes
[2023-04-08 19:27:39,396] DEBUG    processor/thread_13  Added b1722602adda0e01ad1629d538152a3f1ed22f40b04d67276d1ce140e7253381 indicators to event Indicator Type: SHA256 hashes
[2023-04-08 19:27:39,397] DEBUG    processor/thread_11  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,397] DEBUG    processor/thread_12  Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,397] DEBUG    processor/thread_5   Tagged malicious-confidence HIGH
[2023-04-08 19:27:39,397] DEBUG    processor/thread_14  Updated Malware Family: Emotet event threat level to HIGH
[2023-04-08 19:27:39,397] DEBUG    processor/thread_2   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,398] DEBUG    processor/thread_1   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,398] DEBUG    processor/thread_0   Tagged malware COBALTSTRIKE
[2023-04-08 19:27:39,398] DEBUG    processor/thread_11  Tagged malware COBALTSTRIKE

Continues for 23+ Hours
[2023-04-09 13:30:55,429] DEBUG    processor/thread_10  Added 4e97d128b5e06ea4cda3cdef1bbe0c28 indicators to event Indicator Type: MD5 hashes
[2023-04-09 13:30:55,456] DEBUG    processor/thread_12  Tagged mitre-attck RESOURCEDEVELOPMENT
[2023-04-09 13:30:55,522] DEBUG    processor/thread_3   Tagged threat DOWNLOADER
[2023-04-09 13:30:55,605] DEBUG    processor/thread_5   Tagged mitre-attck PERSISTENCE
[2023-04-09 13:30:55,656] DEBUG    processor/thread_6   Tagged mitre-attck RESOURCEDEVELOPMENT
[2023-04-09 13:30:55,687] DEBUG    processor/thread_0   Tagged mitre-attck COMMANDANDCONTROL
[2023-04-09 13:30:55,744] DEBUG    processor/thread_1   Tagged mitre-attck COMMANDANDCONTROL
[2023-04-09 13:30:55,852] DEBUG    processor/thread_15  Tagged mitre-attck PRIVILEGEESCALATION
[2023-04-09 13:30:55,888] DEBUG    processor/thread_8   Tagged mitre-attck COMMANDANDCONTROL
[2023-04-09 13:30:55,919] DEBUG    processor/thread_11  Tagged mitre-attck COMMANDANDCONTROL
[2023-04-09 13:30:55,955] DEBUG    processor/thread_13  Tagged mitre-attck PERSISTENCE
[2023-04-09 13:30:55,981] DEBUG    processor/thread_9   Tagged mitre-attck INITIALACCESS
[2023-04-09 13:30:56,063] DEBUG    processor/thread_10  Tagged malicious-confidence HIGH
[2023-04-09 13:30:56,084] DEBUG    processor/thread_12  Tagged mitre-attck RESOURCEDEVELOPMENT
[2023-04-09 13:30:57,001] DEBUG    processor/thread_12  Tagged mitre-attck RESOURCEDEVELOPMENT
[2023-04-09 13:30:56,197] DEBUG    processor/thread_6   Tagged mitre-attck RESOURCEDEVELOPMENT
[2023-04-09 13:30:56,290] DEBUG    processor/thread_0   Tagged mitre-attck DEFENSEEVASION
[2023-04-09 13:30:56,383] DEBUG    processor/thread_1   Tagged mitre-attck COMMANDANDCONTROL
[2023-04-09 13:30:56,486] DEBUG    processor/thread_15  Tagged mitre-attck RESOURCEDEVELOPMENT
[2023-04-09 13:30:56,580] DEBUG    processor/thread_8   Tagged mitre-attck COMMANDANDCONTROL
[2023-04-09 13:30:56,714] DEBUG    processor/thread_11  Tagged mitre-attck COMMANDANDCONTROL
[2023-04-09 13:30:56,817] DEBUG    processor/thread_13  Tagged mitre-attck PERSISTENCE
[2023-04-09 13:30:56,889] DEBUG    processor/thread_9   Tagged mitre-attck LATERALMOVEMENT
[2023-04-09 13:30:56,971] DEBUG    processor/thread_10  Tagged malware SALITYV4
[2023-04-09 13:30:56,182] DEBUG    processor/thread_5   Tagged mitre-attck PERSISTENCE
[2023-04-09 13:30:57,001] DEBUG    processor/thread_12  Tagged mitre-attck RESOURCEDEVELOPMENT
[2023-04-09 13:30:57,084] DEBUG    processor/thread_6   Tagged threat BOTNET
[2023-04-09 13:30:57,768] DEBUG    processor/thread_6   Tagged threat COMMODITY
[2023-04-09 13:30:57,773] DEBUG    processor/thread_6   Tagged threat CRIMINAL
[2023-04-09 13:30:57,779] DEBUG    processor/thread_6   Tagged threat DOWNLOADER
[2023-04-09 13:30:57,367] DEBUG    processor/thread_8   Tagged mitre-attck COMMANDANDCONTROL
[2023-04-09 13:30:57,475] DEBUG    processor/thread_11  Tagged mitre-attck COMMANDANDCONTROL
^CError in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/opt/rh/rh-python38/root/usr/lib64/python3.8/concurrent/futures/thread.py", line 40, in _python_exit
[2023-04-09 13:30:57,527] DEBUG    processor/thread_13  Tagged mitre-attck PERSISTENCE
    t.join()
  File "/opt/rh/rh-python38/root/usr/lib64/python3.8/threading.py", line 1011, in join
[2023-04-09 13:30:57,619] DEBUG    processor/thread_9   Tagged mitre-attck PERSISTENCE
^C  File "/opt/rh/rh-python38/root/usr/lib64/python3.8/threading.py", line 1027, in _wait_for_tstate_lock
[2023-04-09 13:30:57,657] DEBUG    processor/thread_4   Added 85f8fd4e4b1d701e431a4dfb0145e856 indicators to event Malware Family: Salityv4
[2023-04-09 13:30:57,686] DEBUG    processor/thread_10  Tagged mitre-attck COMMANDANDCONTROL
^CKeyboardInterrupt

FYSA - Still running several days later...

Something's definitely not right here. Might have to kill that process and try to restart at a newer timestamp.  (I'm working on recreating this.)

The “Indicator” ingestion has been behaving like this forever.
Patrick Maroney
Principal - Cybersecurity
Chief Security Office
AT&T Services, Inc.
From: Joshua Hiller @.>
Date: Tuesday, April 18, 2023 at 5:59 PM
To: CrowdStrike/MISP-tools @.>
Cc: MARONEY, PATRICK @.>, Author @.>
Subject: Re: [CrowdStrike/MISP-tools] Indicator Ingestion Loops Indefinitely (Issue #113)
Something's definitely not right here. Might have to kill that process and try to restart at a newer timestamp. (I'm working on recreating this.)
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/CrowdStrike/MISP-tools/issues/113*issuecomment-1513840619__;Iw!!BhdT!kwOHKbH7KwHyO8Unun00ptqv340MKkuHHtGeTSWgU__seq0wxH1p-RflIm1OEQVtrhhHyKUkuo94_ljRBdspLoaM7E4$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AAYSFYKUWM2KZBHAOBUOYC3XB4FBRANCNFSM6AAAAAAWYFGQ7Q__;!!BhdT!kwOHKbH7KwHyO8Unun00ptqv340MKkuHHtGeTSWgU__seq0wxH1p-RflIm1OEQVtrhhHyKUkuo94_ljRBdspcPLZbXk$.
You are receiving this because you authored the thread.Message ID: @.***>

Caused by requested data segment size.

May I asked what the ideal configuration is, that alleviate this issue? I'm coming across the same thing. I believe my pull request is minimal however, it is also a matter of having lower technical specifications. With only 16GBs of RAM, I am working with currently, large volumes of data being pulled will cause the connect to break or the job gets killed due to memory exhaustion
[2024-04-05 13:38:38,814] DEBUG    config  client_id                                   value redacted, check config file
[2024-04-05 13:38:38,814] DEBUG    config  client_secret                               value redacted, check config file
[2024-04-05 13:38:38,814] DEBUG    config  crowdstrike_url                             auto
[2024-04-05 13:38:38,814] DEBUG    config  api_request_max                             2500
[2024-04-05 13:38:38,814] DEBUG    config  api_enable_ssl                              True
[2024-04-05 13:38:38,815] DEBUG    config  reports_timestamp_filename                  lastReportsUpdate.dat
[2024-04-05 13:38:38,815] DEBUG    config  indicators_timestamp_filename               lastIndicatorsUpdate.dat
[2024-04-05 13:38:38,815] DEBUG    config  actors_timestamp_filename                   lastActorsUpdate.dat
[2024-04-05 13:38:38,815] DEBUG    config  init_reports_days_before                    1
[2024-04-05 13:38:38,815] DEBUG    config  init_indicators_minutes_before              60
[2024-04-05 13:38:38,815] DEBUG    config  init_actors_days_before                     1
[2024-04-05 13:38:38,815] DEBUG    config  reports_tags                                value not specified
[2024-04-05 13:38:38,815] DEBUG    config  indicators_tags                             value not specified
[2024-04-05 13:38:38,816] DEBUG    config  actors_tags                                 value not specified
[2024-04-05 13:38:38,816] DEBUG    config  unknown_mapping                             CrowdStrike:indicator:galaxy: UNATTRIBUTED
[2024-04-05 13:38:38,816] DEBUG    config  unattributed_title                          Unattributed indicators:
[2024-04-05 13:38:38,816] DEBUG    config  indicator_type_title                        Indicator Type:
[2024-04-05 13:38:38,816] DEBUG    config  malware_family_title                        Malware Family:
[2024-04-05 13:38:38,816] DEBUG    config  misp_url                                    [REDACTED]
[2024-04-05 13:38:38,816] DEBUG    config  misp_auth_key                               value redacted, check config file
[2024-04-05 13:38:38,816] DEBUG    config  crowdstrike_org_uuid                        [REDACTED]
[2024-04-05 13:38:38,817] DEBUG    config  miss_track_file                             no_galaxy_mapping.log
[2024-04-05 13:38:38,817] DEBUG    config  galaxies_map_file                           galaxy.ini
[2024-04-05 13:38:38,817] DEBUG    config  misp_enable_ssl                             False
[2024-04-05 13:38:38,817] WARNING  config  misp_enable_ssl                             SSL is disabled for MISP API requests
[2024-04-05 13:38:38,817] DEBUG    config  misp_malware_family_range                   7d
[2024-04-05 13:38:38,817] DEBUG    config  ind_attribute_batch_size                    50
[2024-04-05 13:38:38,817] DEBUG    config  event_save_memory_refresh_interval          180
[2024-04-05 13:38:38,818] DEBUG    config  max_threads                                 10
[2024-04-05 13:38:38,818] DEBUG    config  tag_unknown_galaxy_maps                     True
[2024-04-05 13:38:38,818] DEBUG    config  taxonomic_kill-chain                        True
[2024-04-05 13:38:38,818] DEBUG    config  taxonomic_information-security-data-source  True
[2024-04-05 13:38:38,818] DEBUG    config  taxonomic_type                              True
[2024-04-05 13:38:38,818] DEBUG    config  taxonomic_iep                               False
[2024-04-05 13:38:38,818] DEBUG    config  taxonomic_iep2                              True
[2024-04-05 13:38:38,818] DEBUG    config  taxonomic_iep2_version                      False
[2024-04-05 13:38:38,818] DEBUG    config  taxonomic_tlp                               True
[2024-04-05 13:38:38,819] DEBUG    config  taxonomic_workflow                          True