Win10 not starting miningcore

win 10 / i7-8 core / 32 GB ram + 32 virtual memory / 2tb ssd (over 500gb free)
i started miningcore with:
miningcore -c config.json
the error after a minute after start:
[2021-12-03 14:51:42.1385] [I] [StatsRecorder] Stats GC complete
[2021-12-03 14:52:33.7697] [E] [eth1] System.OutOfMemoryException: ethash_full_new IO or memory error
the full output:
[2021-12-03 14:51:26.3075] [I] [Core] Version <IP_ADDRESS>-master [0075cb7666a7f9a6c5b9e48fef5adb2b09df869a]
[2021-12-03 14:51:26.3198] [I] [Core] Runtime .NET 6.0.0-rtm.21522.10 on Microsoft Windows 10.0.19043 [X64]
[2021-12-03 14:51:26.3198] [I] [Core] Prometheus Metrics <IP_ADDRESS>:4000/metrics
[2021-12-03 14:51:26.3198] [I] [Core] WebSocket notifications streaming <IP_ADDRESS>:4000/notifications
[2021-12-03 14:51:26.7018] [I] [XmlKeyManager] User profile is available. Using 'C:\Users\me\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.
[2021-12-03 14:51:26.7242] [I] [ShareRecorder] Online
[2021-12-03 14:51:26.7514] [I] [PayoutManager] Online
[2021-12-03 14:51:26.7514] [I] [StatsRecorder] Online
[2021-12-03 14:51:26.8436] [I] [Core] 53 coins loaded from C:\Users\me\miningcore\build\coins.json
[2021-12-03 14:51:26.8571] [I] [eth1] Starting Pool ...
[2021-12-03 14:51:26.8571] [I] [eth1] ExtraNonceProvider using 4 bits for instance id, 12 bits for 4095 values, instance id = 0x0
[2021-12-03 14:51:26.8571] [I] [Core] API Access to /api/admin restricted to <IP_ADDRESS>,::1,::ffff:<IP_ADDRESS>
[2021-12-03 14:51:26.8571] [I] [Core] API Access to /metrics restricted to <IP_ADDRESS>,::1,::ffff:<IP_ADDRESS>
[2021-12-03 14:51:26.8571] [I] [eth1] Starting Job Manager ...
[2021-12-03 14:51:26.9104] [I] [Lifetime] Now listening on: http://<IP_ADDRESS>:4000
[2021-12-03 14:51:26.9104] [I] [Lifetime] Application started. Press Ctrl+C to shut down.
[2021-12-03 14:51:26.9104] [I] [Lifetime] Hosting environment: Production
[2021-12-03 14:51:26.9129] [I] [Lifetime] Content root path: C:\Users\me\miningcore\build
[2021-12-03 14:51:26.9508] [I] [eth1] All daemons online
[2021-12-03 14:51:26.9508] [I] [eth1] All daemons synched with blockchain
[2021-12-03 14:51:27.0556] [I] [eth1] Loading current DAG ...
[2021-12-03 14:51:27.0556] [I] [eth1] No pre-generated DAG available, creating new for epoch 457
[2021-12-03 14:51:27.0556] [I] [eth1] Generating DAG for epoch 457
[2021-12-03 14:51:41.7766] [I] [StatsRecorder] Performing Stats GC
[2021-12-03 14:51:42.1385] [I] [StatsRecorder] Stats GC complete
[2021-12-03 14:52:33.7697] [E] [eth1] System.OutOfMemoryException: ethash_full_new IO or memory error
at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.b__0() in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70
at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90
at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527
at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113    at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290    at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379 System.OutOfMemoryException: ethash_full_new IO or memory error    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.<GenerateAsync>b__0() in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99    at System.Threading.Tasks.Task.InnerInvoke()    at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location ---    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)    at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location ---    at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70    at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90    at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527    at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113
at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290
at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.b__0() in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70
at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90
at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527
at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113    at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290    at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379 [2021-12-03 14:52:33.8430] [E] [Host] BackgroundService failed System.OutOfMemoryException: ethash_full_new IO or memory error    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.<GenerateAsync>b__0() in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99    at System.Threading.Tasks.Task.InnerInvoke()    at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location ---    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)    at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location ---    at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70    at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90    at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527    at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113
at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290
at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379
at Miningcore.Program.<>c__DisplayClass15_0.<b__0>d.MoveNext() in C:\Users\me\Miningcore\miningcore\src\Miningcore\Program.cs:line 358
--- End of stack trace from previous location ---
at Miningcore.Program.ExecuteAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Program.cs:line 333
at Microsoft.Extensions.Hosting.Internal.Host.TryExecuteBackgroundServiceAsync(BackgroundService backgroundService)    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.b__0() in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70
at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90
at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527
at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113    at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290    at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379    at Miningcore.Program.<>c__DisplayClass15_0.<<RunPool>b__0>d.MoveNext() in C:\Users\me\Miningcore\miningcore\src\Miningcore\Program.cs:line 358 --- End of stack trace from previous location ---    at Miningcore.Program.ExecuteAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Program.cs:line 333    at Microsoft.Extensions.Hosting.Internal.Host.TryExecuteBackgroundServiceAsync(BackgroundService backgroundService) [2021-12-03 14:52:33.8430] [F] [Host] The HostOptions.BackgroundServiceExceptionBehavior is configured to StopHost. A BackgroundService has thrown an unhandled exception, and the IHost instance is stopping. To avoid this behavior, configure this to Ignore; however the BackgroundService will not be restarted. System.OutOfMemoryException: ethash_full_new IO or memory error    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.<GenerateAsync>b__0() in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99    at System.Threading.Tasks.Task.InnerInvoke()    at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location ---    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)    at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location ---    at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70    at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90    at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527    at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113
at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290
at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379
at Miningcore.Program.<>c__DisplayClass15_0.<b__0>d.MoveNext() in C:\Users\me\Miningcore\miningcore\src\Miningcore\Program.cs:line 358
--- End of stack trace from previous location ---
at Miningcore.Program.ExecuteAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Program.cs:line 333
at Microsoft.Extensions.Hosting.Internal.Host.TryExecuteBackgroundServiceAsync(BackgroundService backgroundService)    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.b__0() in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70
at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90
at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527
at Miningcore.Blockchain.JobManagerBase`1.StartAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113
at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290
at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379
at Miningcore.Program.<>c__DisplayClass15_0.<b__0>d.MoveNext() in C:\Users\me\Miningcore\miningcore\src\Miningcore\Program.cs:line 358
--- End of stack trace from previous location ---
at Miningcore.Program.ExecuteAsync(CancellationToken ct) in C:\Users\me\Miningcore\miningcore\src\Miningcore\Program.cs:line 333
at Microsoft.Extensions.Hosting.Internal.Host.TryExecuteBackgroundServiceAsync(BackgroundService backgroundService)
[2021-12-03 14:52:33.8660] [I] [Lifetime] Application is shutting down...

I believe this should be fix with Release 64. Opinons @BitWizJason

That is correct @oliverw. It is definitely the same exception. @Raspimann make sure you pull latest master.

i cloned version 64 ... compiled it ... the same after generate DAG:
Version: <IP_ADDRESS>-master
...
[2021-12-03 15:30:24.4739] [I] [StatsRecorder] Stats GC complete
[2021-12-03 15:31:17.2166] [E] [eth1] System.OutOfMemoryException: ethash_full_new IO or memory error
at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.b__0() in C:\Users\ich\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)

Show the full log please.

here the full output:
[2021-12-03 15:30:08.6336] [I] [Core] Version <IP_ADDRESS>-master [0075cb7666a7f9a6c5b9e48fef5adb2b09df869a]
[2021-12-03 15:30:08.6447] [I] [Core] Runtime .NET 6.0.0-rtm.21522.10 on Microsoft Windows 10.0.19043 [X64]
[2021-12-03 15:30:08.6512] [I] [Core] Prometheus Metrics <IP_ADDRESS>:4000/metrics
[2021-12-03 15:30:08.6512] [I] [Core] WebSocket notifications streaming <IP_ADDRESS>:4000/notifications
[2021-12-03 15:30:09.0348] [I] [XmlKeyManager] User profile is available. Using 'C:\Users\me\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.
[2021-12-03 15:30:09.0582] [I] [ShareRecorder] Online
[2021-12-03 15:30:09.0854] [I] [PayoutManager] Online
[2021-12-03 15:30:09.0923] [I] [StatsRecorder] Online
[2021-12-03 15:30:09.1836] [I] [Core] 53 coins loaded from C:\Users\me\miningcore\build\coins.json
[2021-12-03 15:30:09.1977] [I] [eth1] Starting Pool ...
[2021-12-03 15:30:09.1977] [I] [eth1] ExtraNonceProvider using 4 bits for instance id, 12 bits for 4095 values, instance id = 0xB
[2021-12-03 15:30:09.1977] [I] [Core] API Access to /api/admin restricted to <IP_ADDRESS>,::1,::ffff:<IP_ADDRESS>
[2021-12-03 15:30:09.1977] [I] [Core] API Access to /metrics restricted to <IP_ADDRESS>,::1,::ffff:<IP_ADDRESS>
[2021-12-03 15:30:09.1977] [I] [eth1] Starting Job Manager ...
[2021-12-03 15:30:09.2556] [I] [Lifetime] Now listening on: http://<IP_ADDRESS>:4000
[2021-12-03 15:30:09.2556] [I] [Lifetime] Application started. Press Ctrl+C to shut down.
[2021-12-03 15:30:09.2577] [I] [Lifetime] Hosting environment: Production
[2021-12-03 15:30:09.2577] [I] [Lifetime] Content root path: C:\Users\me\miningcore\build
[2021-12-03 15:30:09.2797] [I] [eth1] All daemons online
[2021-12-03 15:30:09.2797] [I] [eth1] All daemons synched with blockchain
[2021-12-03 15:30:09.3436] [I] [eth1] Loading current DAG ...
[2021-12-03 15:30:09.3436] [I] [eth1] No pre-generated DAG available, creating new for epoch 457
[2021-12-03 15:30:09.3436] [I] [eth1] Generating DAG for epoch 457
[2021-12-03 15:30:24.1209] [I] [StatsRecorder] Performing Stats GC
[2021-12-03 15:30:24.4739] [I] [StatsRecorder] Stats GC complete
[2021-12-03 15:31:17.2166] [E] [eth1] System.OutOfMemoryException: ethash_full_new IO or memory error
at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.b__0() in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70
at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90
at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527
at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113    at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290    at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379 System.OutOfMemoryException: ethash_full_new IO or memory error    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.<GenerateAsync>b__0() in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99    at System.Threading.Tasks.Task.InnerInvoke()    at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location ---    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)    at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location ---    at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70    at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90    at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527    at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113
at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290
at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.b__0() in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70
at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90
at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527
at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113    at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290    at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379 [2021-12-03 15:31:17.2854] [E] [Host] BackgroundService failed System.OutOfMemoryException: ethash_full_new IO or memory error    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.<GenerateAsync>b__0() in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99    at System.Threading.Tasks.Task.InnerInvoke()    at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location ---    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)    at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location ---    at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70    at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90    at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527    at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113
at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290
at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379
at Miningcore.Program.<>c__DisplayClass15_0.<b__0>d.MoveNext() in C:\Users\me\miningcore\src\Miningcore\Program.cs:line 358
--- End of stack trace from previous location ---
at Miningcore.Program.ExecuteAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Program.cs:line 333
at Microsoft.Extensions.Hosting.Internal.Host.TryExecuteBackgroundServiceAsync(BackgroundService backgroundService)    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.b__0() in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70
at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90
at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527
at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113    at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290    at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379    at Miningcore.Program.<>c__DisplayClass15_0.<<RunPool>b__0>d.MoveNext() in C:\Users\me\miningcore\src\Miningcore\Program.cs:line 358 --- End of stack trace from previous location ---    at Miningcore.Program.ExecuteAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Program.cs:line 333    at Microsoft.Extensions.Hosting.Internal.Host.TryExecuteBackgroundServiceAsync(BackgroundService backgroundService) [2021-12-03 15:31:17.3017] [F] [Host] The HostOptions.BackgroundServiceExceptionBehavior is configured to StopHost. A BackgroundService has thrown an unhandled exception, and the IHost instance is stopping. To avoid this behavior, configure this to Ignore; however the BackgroundService will not be restarted. System.OutOfMemoryException: ethash_full_new IO or memory error    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.<GenerateAsync>b__0() in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99    at System.Threading.Tasks.Task.InnerInvoke()    at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location ---    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)    at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location ---    at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70    at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90    at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527    at Miningcore.Blockchain.JobManagerBase1.StartAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113
at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290
at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379
at Miningcore.Program.<>c__DisplayClass15_0.<b__0>d.MoveNext() in C:\Users\me\miningcore\src\Miningcore\Program.cs:line 358
--- End of stack trace from previous location ---
at Miningcore.Program.ExecuteAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Program.cs:line 333
at Microsoft.Extensions.Hosting.Internal.Host.TryExecuteBackgroundServiceAsync(BackgroundService backgroundService)    at Miningcore.Crypto.Hashing.Ethash.Dag.<>c__DisplayClass14_0.b__0() in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 99
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__271_0(Object obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Miningcore.Crypto.Hashing.Ethash.Dag.GenerateAsync(String dagDir, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\Dag.cs:line 70
at Miningcore.Crypto.Hashing.Ethash.EthashFull.GetDagAsync(UInt64 block, ILogger logger, CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Crypto\Hashing\Ethash\EthashFull.cs:line 90
at Miningcore.Blockchain.Ethereum.EthereumJobManager.PostStartInitAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumJobManager.cs:line 527
at Miningcore.Blockchain.JobManagerBase`1.StartAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\JobManagerBase.cs:line 113
at Miningcore.Blockchain.Ethereum.EthereumPool.SetupJobManager(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Blockchain\Ethereum\EthereumPool.cs:line 290
at Miningcore.Mining.PoolBase.RunAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Mining\PoolBase.cs:line 379
at Miningcore.Program.<>c__DisplayClass15_0.<b__0>d.MoveNext() in C:\Users\me\miningcore\src\Miningcore\Program.cs:line 358
--- End of stack trace from previous location ---
at Miningcore.Program.ExecuteAsync(CancellationToken ct) in C:\Users\me\miningcore\src\Miningcore\Program.cs:line 333
at Microsoft.Extensions.Hosting.Internal.Host.TryExecuteBackgroundServiceAsync(BackgroundService backgroundService)
[2021-12-03 15:31:17.3171] [I] [Lifetime] Application is shutting down...

Are you sure there's enough space on the drive? The DAG is a couple GB.

I should not have been as definitive. There are a number of other reasons that it can fail with the same exception. @Raspimann see the code/methods here Related Code 1 and here Related Code 2

Yes, over 500gb free disk

i'm the root/admin with all privileges

It is hard to offer more then basic troubleshooting for an external library. You would need to build libethhash in Debug and attach a debugger to really get to the bottom of the issue.

I was also getting the same exception on Windows 10 64bit but after rebuilding libethhash and miningcore with the changes included in release 64 I was able to successfully generate the dag.

so i delete all version of miningcore and cloned it new. compiled.
so i have the latest version:  Version <IP_ADDRESS>-master
but i have the same problem ... same error

does miningcore go only in geth "light" modus?
code "dag.cs" where the first error displayed "ethash_full_new IO or memory error":
...
try
{
// Generate the actual DAG
handle = LibEthhash.ethash_full_new(dagDir, light, progress =>
{
logger.Info(() => $"Generating DAG for epoch {Epoch}: {progress}%");
                        return !ct.IsCancellationRequested ? 0 : 1;
                    });

                    if(handle == IntPtr.Zero)
                        throw new OutOfMemoryException("ethash_full_new IO or memory error");

                    logger.Info(() => $"Done generating DAG for epoch {Epoch} after {DateTime.Now - started}");
                }

                finally
                {
                    if(light != IntPtr.Zero)
                        LibEthhash.ethash_light_delete(light);
                }

i use geth in full modus ...
the dag was full generated, but i thing not in the right way, because the handle must be zero and cause an error
code "dag.cs" where the first error displayed "ethash_full_new IO or memory error":
...
try
{
// Generate the actual DAG
handle = LibEthhash.ethash_full_new(dagDir, light, progress =>
{
logger.Info(() => $"Generating DAG for epoch {Epoch}: {progress}%");
                    return !ct.IsCancellationRequested ? 0 : 1;
                });

                if(handle == IntPtr.Zero)
                    throw new OutOfMemoryException("ethash_full_new IO or memory error");

                logger.Info(() => $"Done generating DAG for epoch {Epoch} after {DateTime.Now - started}");
            }

            finally
            {
                if(light != IntPtr.Zero)
                    LibEthhash.ethash_light_delete(light);
            }

I also face this problem.
After tracing code, I found it was return false at line 381 in libethhash/internal.c
But dag-file was created successfully.
My dev environment is win10( build 1903) and using vs 2022 community using eth Ropsten testnet.

I also face this problem.
After debugging using vs2022,  I found that was some problem at line line 69 in libethhash/mmap_win32.c
The return value was NULL when call MapViewOfFile function.
Then I called GetLastError() before line 71 and got error code 5( that's mean 'ERROR_ACCESS_DENIED')
But all thing is fine on linux OS but failed on Win10.
Any idea about this ?

libethhash/mmap_win32.c

The filename makes it obvious that this is not the same code that runs on Linux. Memory mapped files are handled differently on Windows.

Yeah, I knew the difference. Just provide some information.

Yeah, I knew the difference. Just provide some information.

Much appreciated 👍

Maybe not the answer but I modify line 56 in libethhash/mmap_win32.c
from
h = CreateFileMapping(mmap_fd, NULL, flProtect, DWORD_HI(end), DWORD_LO(end), NULL);
to
h = CreateFileMapping(mmap_fd, NULL, flProtect, 0, 0, NULL );
It seems works.

Maybe not the answer but I modify line 56 in libethhash/mmap_win32.c from h = CreateFileMapping(mmap_fd, NULL, flProtect, DWORD_HI(end), DWORD_LO(end), NULL); to h = CreateFileMapping(mmap_fd, NULL, flProtect, 0, 0, NULL ); It seems works.

Excellent find. Thank you.

@bryanhuang0927 @Raspimann Could you guys give the oliverw branch a try?

ok, i modify the code first like @oliverw and then i manually copied the libethash into the build and bin\release.
this is the output:
...
[2021-12-07 10:30:09.4163] [I] [eth1] All daemons online
[2021-12-07 10:30:09.4163] [I] [eth1] All daemons synched with blockchain
[2021-12-07 10:30:09.4934] [I] [eth1] Loading current DAG ...
[2021-12-07 10:30:09.4934] [I] [eth1] No pre-generated DAG available, creating new for epoch 458
[2021-12-07 10:30:09.4934] [I] [eth1] Generating DAG for epoch 458
[2021-12-07 10:30:24.2313] [I] [StatsRecorder] Performing Stats GC
[2021-12-07 10:30:24.5767] [I] [StatsRecorder] Stats GC complete
[2021-12-07 10:31:18.6210] [I] [eth1] Generating DAG for epoch 458: 0%
[2021-12-07 10:32:06.2526] [I] [eth1] Generating DAG for epoch 458: 1%
[2021-12-07 10:32:54.4403] [I] [eth1] Generating DAG for epoch 458: 2%
[2021-12-07 10:33:42.3724] [I] [eth1] Generating DAG for epoch 458: 3%
[2021-12-07 10:34:30.5782] [I] [eth1] Generating DAG for epoch 458: 4%
[2021-12-07 10:35:18.5798] [I] [eth1] Generating DAG for epoch 458: 5%
[2021-12-07 10:36:06.4200] [I] [eth1] Generating DAG for epoch 458: 6%
[2021-12-07 10:36:54.1941] [I] [eth1] Generating DAG for epoch 458: 7%
[2021-12-07 10:37:41.8948] [I] [eth1] Generating DAG for epoch 458: 8%
[2021-12-07 10:38:29.7188] [I] [eth1] Generating DAG for epoch 458: 9%
[2021-12-07 10:39:17.3372] [I] [eth1] Generating DAG for epoch 458: 10%
[2021-12-07 10:40:05.1490] [I] [eth1] Generating DAG for epoch 458: 11%
[2021-12-07 10:40:53.3370] [I] [eth1] Generating DAG for epoch 458: 12%
[2021-12-07 10:41:40.9864] [I] [eth1] Generating DAG for epoch 458: 13%
[2021-12-07 10:42:28.9658] [I] [eth1] Generating DAG for epoch 458: 14%
[2021-12-07 10:43:16.9117] [I] [eth1] Generating DAG for epoch 458: 15%
[2021-12-07 10:44:04.7573] [I] [eth1] Generating DAG for epoch 458: 16%
[2021-12-07 10:44:53.1316] [I] [eth1] Generating DAG for epoch 458: 17%
[2021-12-07 10:45:41.1471] [I] [eth1] Generating DAG for epoch 458: 18%
[2021-12-07 10:46:29.2277] [I] [eth1] Generating DAG for epoch 458: 19%
[2021-12-07 10:47:17.2130] [I] [eth1] Generating DAG for epoch 458: 20%
[2021-12-07 10:48:05.2066] [I] [eth1] Generating DAG for epoch 458: 21%
[2021-12-07 10:48:54.0388] [I] [eth1] Generating DAG for epoch 458: 22%
[2021-12-07 10:49:42.4087] [I] [eth1] Generating DAG for epoch 458: 23%
[2021-12-07 10:50:31.1577] [I] [eth1] Generating DAG for epoch 458: 24%
[2021-12-07 10:51:19.6521] [I] [eth1] Generating DAG for epoch 458: 25%
[2021-12-07 10:52:07.3382] [I] [eth1] Generating DAG for epoch 458: 26%
[2021-12-07 10:52:55.3233] [I] [eth1] Generating DAG for epoch 458: 27%
[2021-12-07 10:53:43.0146] [I] [eth1] Generating DAG for epoch 458: 28%
[2021-12-07 10:54:30.9140] [I] [eth1] Generating DAG for epoch 458: 29%
[2021-12-07 10:55:18.4168] [I] [eth1] Generating DAG for epoch 458: 30%
[2021-12-07 10:56:05.8537] [I] [eth1] Generating DAG for epoch 458: 31%
[2021-12-07 10:56:53.9226] [I] [eth1] Generating DAG for epoch 458: 32%
[2021-12-07 10:57:42.0586] [I] [eth1] Generating DAG for epoch 458: 33%
[2021-12-07 10:58:30.2546] [I] [eth1] Generating DAG for epoch 458: 34%
[2021-12-07 10:59:18.2172] [I] [eth1] Generating DAG for epoch 458: 35%
[2021-12-07 11:00:06.0689] [I] [eth1] Generating DAG for epoch 458: 36%
[2021-12-07 11:00:54.3674] [I] [eth1] Generating DAG for epoch 458: 37%
[2021-12-07 11:01:42.4779] [I] [eth1] Generating DAG for epoch 458: 38%
[2021-12-07 11:02:30.6420] [I] [eth1] Generating DAG for epoch 458: 39%
[2021-12-07 11:03:18.5755] [I] [eth1] Generating DAG for epoch 458: 40%
[2021-12-07 11:04:06.4895] [I] [eth1] Generating DAG for epoch 458: 41%
[2021-12-07 11:04:54.7411] [I] [eth1] Generating DAG for epoch 458: 42%
[2021-12-07 11:05:42.7006] [I] [eth1] Generating DAG for epoch 458: 43%
[2021-12-07 11:06:30.7728] [I] [eth1] Generating DAG for epoch 458: 44%
[2021-12-07 11:07:18.4705] [I] [eth1] Generating DAG for epoch 458: 45%
[2021-12-07 11:08:06.4581] [I] [eth1] Generating DAG for epoch 458: 46%
[2021-12-07 11:08:54.5733] [I] [eth1] Generating DAG for epoch 458: 47%
[2021-12-07 11:09:42.4683] [I] [eth1] Generating DAG for epoch 458: 48%
[2021-12-07 11:10:30.4623] [I] [eth1] Generating DAG for epoch 458: 49%
[2021-12-07 11:11:18.3120] [I] [eth1] Generating DAG for epoch 458: 50%
[2021-12-07 11:12:05.9250] [I] [eth1] Generating DAG for epoch 458: 51%
[2021-12-07 11:12:54.0888] [I] [eth1] Generating DAG for epoch 458: 52%
[2021-12-07 11:13:42.0126] [I] [eth1] Generating DAG for epoch 458: 53%
[2021-12-07 11:14:30.0314] [I] [eth1] Generating DAG for epoch 458: 54%
[2021-12-07 11:15:18.0462] [I] [eth1] Generating DAG for epoch 458: 55%
[2021-12-07 11:16:06.0243] [I] [eth1] Generating DAG for epoch 458: 56%
[2021-12-07 11:16:54.2109] [I] [eth1] Generating DAG for epoch 458: 57%
[2021-12-07 11:17:42.2240] [I] [eth1] Generating DAG for epoch 458: 58%
[2021-12-07 11:18:30.2126] [I] [eth1] Generating DAG for epoch 458: 59%
[2021-12-07 11:19:17.9988] [I] [eth1] Generating DAG for epoch 458: 60%
[2021-12-07 11:20:05.9185] [I] [eth1] Generating DAG for epoch 458: 61%
[2021-12-07 11:20:54.0221] [I] [eth1] Generating DAG for epoch 458: 62%
[2021-12-07 11:21:42.0039] [I] [eth1] Generating DAG for epoch 458: 63%
[2021-12-07 11:22:30.0229] [I] [eth1] Generating DAG for epoch 458: 64%
[2021-12-07 11:23:17.9463] [I] [eth1] Generating DAG for epoch 458: 65%
[2021-12-07 11:24:05.9740] [I] [eth1] Generating DAG for epoch 458: 66%
[2021-12-07 11:24:54.0825] [I] [eth1] Generating DAG for epoch 458: 67%
[2021-12-07 11:25:42.0645] [I] [eth1] Generating DAG for epoch 458: 68%
[2021-12-07 11:26:29.8895] [I] [eth1] Generating DAG for epoch 458: 69%
[2021-12-07 11:27:18.2137] [I] [eth1] Generating DAG for epoch 458: 70%
[2021-12-07 11:28:06.0649] [I] [eth1] Generating DAG for epoch 458: 71%
[2021-12-07 11:28:53.9413] [I] [eth1] Generating DAG for epoch 458: 72%
[2021-12-07 11:29:41.5408] [I] [eth1] Generating DAG for epoch 458: 73%
[2021-12-07 11:30:29.5312] [I] [eth1] Generating DAG for epoch 458: 74%
[2021-12-07 11:31:17.7114] [I] [eth1] Generating DAG for epoch 458: 75%
[2021-12-07 11:32:05.2245] [I] [eth1] Generating DAG for epoch 458: 76%
[2021-12-07 11:32:53.1520] [I] [eth1] Generating DAG for epoch 458: 77%
[2021-12-07 11:33:41.0211] [I] [eth1] Generating DAG for epoch 458: 78%
[2021-12-07 11:34:28.9864] [I] [eth1] Generating DAG for epoch 458: 79%
[2021-12-07 11:35:17.0831] [I] [eth1] Generating DAG for epoch 458: 80%
[2021-12-07 11:36:04.9036] [I] [eth1] Generating DAG for epoch 458: 81%
[2021-12-07 11:36:52.9326] [I] [eth1] Generating DAG for epoch 458: 82%
[2021-12-07 11:37:40.7848] [I] [eth1] Generating DAG for epoch 458: 83%
[2021-12-07 11:38:28.6093] [I] [eth1] Generating DAG for epoch 458: 84%
[2021-12-07 11:39:16.5335] [I] [eth1] Generating DAG for epoch 458: 85%
[2021-12-07 11:40:04.0847] [I] [eth1] Generating DAG for epoch 458: 86%
[2021-12-07 11:40:52.0721] [I] [eth1] Generating DAG for epoch 458: 87%
[2021-12-07 11:41:39.9247] [I] [eth1] Generating DAG for epoch 458: 88%
[2021-12-07 11:42:27.5871] [I] [eth1] Generating DAG for epoch 458: 89%
[2021-12-07 11:43:15.5758] [I] [eth1] Generating DAG for epoch 458: 90%
[2021-12-07 11:44:03.3225] [I] [eth1] Generating DAG for epoch 458: 91%
[2021-12-07 11:44:51.4336] [I] [eth1] Generating DAG for epoch 458: 92%
[2021-12-07 11:45:39.3305] [I] [eth1] Generating DAG for epoch 458: 93%
[2021-12-07 11:46:27.2050] [I] [eth1] Generating DAG for epoch 458: 94%
[2021-12-07 11:47:15.4016] [I] [eth1] Generating DAG for epoch 458: 95%
[2021-12-07 11:48:03.2722] [I] [eth1] Generating DAG for epoch 458: 96%
[2021-12-07 11:48:51.2948] [I] [eth1] Generating DAG for epoch 458: 97%
[2021-12-07 11:49:39.1403] [I] [eth1] Generating DAG for epoch 458: 98%
[2021-12-07 11:50:26.9118] [I] [eth1] Generating DAG for epoch 458: 99%
[2021-12-07 11:51:15.0153] [I] [eth1] Generating DAG for epoch 458: 100%
[2021-12-07 11:51:15.0153] [I] [eth1] Done generating DAG for epoch 458 after 01:21:05.5217063
[2021-12-07 11:51:15.0307] [I] [eth1] Loaded current DAG
[2021-12-07 11:51:15.0483] [I] [eth1] Job Manager Online
[2021-12-07 11:51:15.2346] [I] [eth1] New work at height 13758104 and header 0xe71178b358d55813855186f1e8c04d5b71b0bd1284cc6fedecba03410024b387 via [POLL]
[2021-12-07 11:51:15.2346] [I] [eth1] Broadcasting job
[2021-12-07 11:51:15.2988] [I] [eth1] Pool Online
[2021-12-07 11:51:15.2988] [I] [eth1]
Mining Pool:            eth1
Coin Type:              ETH [ETH]
Network Connected:      Ethereum-Mainnet
Detected Reward Type:   POW
Current Block Height:   13758104
Current Connect Peers:  12
Network Difficulty:<PHONE_NUMBER>4434672
Network Hash Rate:      692,36 TH/s
Stratum Port(s):        4073
Pool Fee:               1,0%
i thing it works now ... but on my machine (win10/32GB/i7-8cores/2TB ssd) the time to generate the dag is very very slow ... 20 minutes in the log ... the max. on cpu is 20 percent, mostly under 10 percent ... all other between 2 5 precent

Yes, its always slow not just for you. And a bit of advise please avoid creating frankenstein builds using one of the native libs from one release with the managed code from another one. In this case it is fine and I'm 100% sure everything works as it should.


in XCode 7.3 crashed

I upgrade my xcode to 7.3
then my project can't launched..
It crashed in SVProgressHUD.m,352 lines..
NSBundle *bundle = [NSBundle bundleForClass:[SVProgressHUD class]];
//get nil url,then it crashed
NSURL *url = [bundle URLForResource:@"SVProgressHUD" withExtension:@"bundle"];
NSBundle *imageBundle = [NSBundle bundleWithURL:url];
Sorry about my bad English T.T
I need help,thank you!

Just checked. Works for me in demo and my apps. What is different in your app than in the demo? Did you add the Bundle to Targets->Build Phases->Copy Bundle Resources? Do you use Cocoapods? Did you run pod install?

I did't do it,before xcode 7.3,it works well

Hmm, there must be some weird things in your setup because demo and my apps (overall 5 projects) do work. Please check and reinstall.

OK,let me try,thanks

delete the contents of the folder "dereved data" and rebuild all. :smiley:

I change a computer,it work's well,i did't change any code,i'm so bad,it cost me 3 days...thank you all~~

Hey! just happen to our live version. 6 crashes from one user! Any ideas?

Did you deploy the Bundle?

Of course i have deploy the bundle. Many users use the app without any issue.
The specific user using iOS 7 and the device is jailbreak!


Switching to use upstream tensor.pack/unpack ops

benchmarks: comp-stats

This depends on https://github.com/iree-org/iree/pull/12153 and https://reviews.llvm.org/D144151

It also depends on https://github.com/llvm/llvm-project/commit/be75cf931f3fd3f23a04d3e8f441f09a3cf08ef9

@MaheshRavishankar this is ready for review. Please take a look when you're available, thanks!


Add Tidy Explorer

Tidy up your file explorer, hide or pin files and folders with just one click.
This extension allows you to configure glob patterns and group related glob patterns into "Pockets". Then you can toggle the files that match an individual pattern or all patterns in a Pocket to:
hide the files in the file Explorer (one-click adding into the "files.exclude" setting)
pin the files in the "Tidy Explorer"
When you have a complex project with a large number of files and folders, this extension help you reduce the distractions from uninterested files (e.g. auto-generated) and focus on the files you are working on.
See https://marketplace.visualstudio.com/items?itemName=bingtimren.tidy-explorer
Name of the extension you are adding
Tidy Explorer
Why do you think this extension is awesome?
When working with a large and complex project, developer often wants to focus on a small set of files at a time, and the rest of the files (configurations, files not being worked on) become a distraction, also makes the files being worked on or of interest difficult to find.
Tidy explorer allows you to category your files (define in "Pockets"), hide or pin them with single click.
Make sure that:

[X] Screenshot/GIF included (to demonstrate the plugin functionality)

[X] ToC updated

@Langit12  hi thanks for commenting but I'm now sure about what you mean exactly. Anything I can do?


[Bugfix] Overlapping issue in Video Slider

This PR addresses issue #1.
The video slider was overlapping due to the end segment of the slider being placed at the start of the nth second, rather than at the end.
For instance, consider the following segment data:
 const segmentsData = [{
    start:0,
    end:3,
    title:"Test - 1"
  },{
    start:4,
    end:6,
    title:"Test - 2"
  },{
    start:7,
    end:10,
    title:"Final Test"
  }
];

In the first segment, where the end time is 3 seconds, the current code begins the segment at the start of the 3rd second. Each second contains 1000ms, and this was causing the segments to overlap.
To resolve this issue, I added 1s to the end segment. Consequently, the segment now starts at the end of the nth second, which corrects the problem.
Current Issue which exists in 100xDevs video player:

After Implementation:
https://github.com/code100x/cms/assets/34382211/fdec7ea1-be8f-4abe-8f58-471e24b2943a
Note: When providing the segment data, keep in mind that segments shouldn't collide at the end of time, as this will lead to overlap issues. If you want me to add an additional method to ensure this end time does not collide with another segment and is within the video duration, please let me know and I will add those checks.

Could you please have a look at this PR @hkirat  and share your opinion? Does it satisfy your needs or do you require something else?

Great start can u add some padding around please? Seems a lil constraint

Is this width sufficient, or should I increase it a little more?

@sahilsuman933 the problem is not with segments overlapping from my understanding but with the title of the segment.
if the title is too long it doesn't break and go on the next line. This is due to the fixed with of 200px.
Now you can think that changing the width fixes the issue, sort of yes, but now if you last segment title is too long is will overflow the screen.
Try to make the title go on a new line

You are correct, @siinghd, but this PR addresses a different issue. If you watch the attached video, you'll notice that even though I set the end segment to 3 seconds, it appears before the end of the 3 seconds, which shouldn't happen.
https://github.com/code100x/cms/assets/34382211/67e7f88c-8a39-431e-8343-e51c8cbe1770

Closing in favor of https://github.com/code100x/cms/pull/15


Bunch of Questions

Description
Does this support ingesting existing metadata on PDFs or does it all have to be manual? Can you embed images/use VLM's? does it link back to the original source file if stored in the same location? how do you remove things from the database/update saved locations/re-embed after something is deleted? is there a way to change the size of the points in the 3d view? mapplotlib may be good to integrate instead of the 3d visual. also, is there a way to merge embeddings if you previously embedded so you dont have to redo it?
Additional context
sorry, a lot of questions

Hey, thanks for the questions!

Currently, you have to add any metadata manually
You cannot embed images
It cannot link back to the original file in your filesystem
You can delete documents via the Document Tab or you can directly modify the data in your Weaviate instance (depending on the deployment type you chose)
You can't change the points size, good idea with matplotlib I'll think about it
Right now, if you add data you always have to re-embed it unfortunately


st2ctl reload --register-all fails when pack name has spaces

SUMMARY
st2ctl reload --register-all is throwing schema validator error when pack name contains spaces in spite of having ref property in the pack.yaml file.
ISSUE TYPE

Bug Report

STACKSTORM VERSION
Paste the output of st2 --version:
st2 2.9.1, on Python 2.7.6

OS / ENVIRONMENT / INSTALL METHOD

docker: st2-docker project

STEPS TO REPRODUCE
Pack code: https://docs.stackstorm.com/reference/packs.html#creating-your-first-pack

Create a pack.yaml file with  ref and name property.
Add spaces in name property
install pack: st2 pack install file:///$PWD    :  Succeed
Manual installation:  copy entire content of pack into:  /opt/stackstorm/packs/

Try to register config:

st2ctl reload --register-all
schema validation failed error should show up in the console.

---
ref: nexus3
name: Sontatype nexus3
description: Sontatype nexus3 stackstorm pack
keywords:
    - example
    - test
version: 0.1.0
python_versions:
  - "2"
  - "3"
author: Sonu K. Meena
email<EMAIL_ADDRESS>
EXPECTED RESULTS

It should register pack without any schema issue

ACTUAL RESULTS
  utils.DeprecatedIn23,
2019-02-20 08:22:54,066 INFO [-] Connecting to database "st2" @ "mongo:27017" as user "None".
2019-02-20 08:22:54,073 INFO [-] Successfully connected to database "st2" @ "mongo:27017" as user "None".
2019-02-20 08:22:54,444 INFO [-] =========================================================
2019-02-20 08:22:54,444 INFO [-] ############## Registering triggers #####################
2019-02-20 08:22:54,444 INFO [-] =========================================================
2019-02-20 08:22:54,470 WARNING [-] Failed to register sensors: Failed to register pack "Sontatype Nexus3": Pack ref / name can only contain valid word characters (a-z, 0-9 and _), dashes are not allowed.

'Sontatype Nexus3' does not match '^[a-z0-9_]+$'

Failed validating 'pattern' in schema['properties']['ref']:
    {'default': None,
     'description': 'Reference for the pack, used as an internal id.',
     'pattern': '^[a-z0-9_]+$',
     'type': ['string', 'null']}

On instance['ref']:
    'Sontatype Nexus3'
Traceback (most recent call last):
  File "/usr/bin/st2-register-content", line 22, in <module>
    sys.exit(content_loader.main(sys.argv[1:]))
  File "/opt/stackstorm/st2/local/lib/python2.7/site-packages/st2common/content/bootstrap.py", line 389, in main
    register_content()
  File "/opt/stackstorm/st2/local/lib/python2.7/site-packages/st2common/content/bootstrap.py", line 336, in register_content
    register_triggers()
  File "/opt/stackstorm/st2/local/lib/python2.7/site-packages/st2common/content/bootstrap.py", line 146, in register_triggers
    raise e
ValueError: Failed to register pack "Sontatype Nexus3": Pack ref / name can only contain valid word characters (a-z, 0-9 and _), dashes are not allowed.

'Sontatype Nexus3' does not match '^[a-z0-9_]+$'

Failed validating 'pattern' in schema['properties']['ref']:
    {'default': None,
     'description': 'Reference for the pack, used as an internal id.',
     'pattern': '^[a-z0-9_]+$',
     'type': ['string', 'null']}

On instance['ref']:
    'Sontatype Nexus3'
##### st2 components status #####
st2actionrunner PID: 111

install pack: st2 pack install file:///$PWD    :  Succeed

So it succeeded when you ran st2 pack install, but failed when you tried to manually register it?
What does your sensor yaml contain?

There are tests related to packs with a space in the 'name:` field - see https://github.com/StackStorm/st2/blob/master/st2tests/st2tests/fixtures/packs/dummy_pack_16/pack.yaml
But I wonder if this is somehow connected to https://github.com/StackStorm/st2/issues/3682
It may be that this becomes an issue when you have sensors

@LindsayHill
Correct:  st2 pack install works but manual registration fails even without sensors
root@72b8ebf04e73:/nexus3# rm -rf sensors
root@72b8ebf04e73:/nexus3# rm -rf /opt/stackstorm/packs/nexus3/*
root@72b8ebf04e73:/nexus3# cp -rf ./* /opt/stackstorm/packs/nexus3/
root@72b8ebf04e73:/nexus3# tree -L 2 /opt/stackstorm/packs/nexus3/
/opt/stackstorm/packs/nexus3/
├── actions
│   ├── create_repositories.yaml
│   ├── create_scripts.yaml
│   ├── delete_repositories.yaml
│   ├── delete_scripts.yaml
│   ├── get_repositories.yaml
│   ├── get_scripts.yaml
│   ├── lib
│   ├── list_repositories.yaml
│   ├── list_scripts.yaml
│   ├── run.py
│   └── run_scripts.yaml
├── aliases
├── config.schema.yaml
├── icon.png
├── nexus3.yaml.example
├── pack.yaml
├── policies
│   └── retry_core_http_on_timeout.yaml
├── README.md
├── README-test.md
├── requirements.txt
└── rules

2019-02-20 14:36:57,355 WARNING [-] Failed to register sensors: Failed to register pack "Sontatype Nexus3": Pack ref / name can only contain valid word characters (a-z, 0-9 and _), dashes are not allowed.

'Sontatype Nexus3' does not match '^[a-z0-9_]+$'

Failed validating 'pattern' in schema['properties']['ref']:
    {'default': None,
     'description': 'Reference for the pack, used as an internal id.',
     'pattern': '^[a-z0-9_]+$',
     'type': ['string', 'null']}

On instance['ref']:
    'Sontatype Nexus3'
Traceback (most recent call last):
  File "/usr/bin/st2-register-content", line 22, in <module>
    sys.exit(content_loader.main(sys.argv[1:]))
  File "/opt/stackstorm/st2/local/lib/python2.7/site-packages/st2common/content/bootstrap.py", line 389, in main
    register_content()
  File "/opt/stackstorm/st2/local/lib/python2.7/site-packages/st2common/content/bootstrap.py", line 336, in register_content
    register_triggers()
  File "/opt/stackstorm/st2/local/lib/python2.7/site-packages/st2common/content/bootstrap.py", line 146, in register_triggers
    raise e
ValueError: Failed to register pack "Sontatype Nexus3": Pack ref / name can only contain valid word characters (a-z, 0-9 and _), dashes are not allowed.

'Sontatype Nexus3' does not match '^[a-z0-9_]+$'

Failed validating 'pattern' in schema['properties']['ref']:
    {'default': None,
     'description': 'Reference for the pack, used as an internal id.',
     'pattern': '^[a-z0-9_]+$',
     'type': ['string', 'null']}

On instance['ref']:
    'Sontatype Nexus3'

I'm following the official pack guide:
https://docs.stackstorm.com/reference/packs.html#creating-your-first-pack
Sensor:
---
class_name: "HelloSensor"
entry_point: "sensor1.py"
description: "Test sensor that emits triggers."
trigger_types:
  -
    name: "event1"
    description: "An example trigger."
    payload_schema:
      type: "object"

manual registration fails even without sensors

It's possible that what's happened here is that you still have some reference to the sensor in the DB. Just deleting the content from disk doesn't delete it from DB.

Just running some tests on my system:
vagrant@stackstorm:~$ st2 --version
st2 2.10.1, on Python 2.7.12
vagrant@stackstorm:~$

Start with a very simple pack containing no actions or sensors:
vagrant@stackstorm:~$ cd mypack/
vagrant@stackstorm:~/mypack$ ll
total 16
drwxrwxr-x 3 vagrant vagrant 4096 Feb 20 14:48 ./
drwxr-xr-x 8 vagrant vagrant 4096 Feb 20 14:48 ../
drwxrwxr-x 8 vagrant vagrant 4096 Feb 20 14:48 .git/
-rwxrwxr-x 1 vagrant vagrant  123 Feb 20 14:48 pack.yaml*
vagrant@stackstorm:~/mypack$ cat pack.yaml
---
ref: mypack
name: My Pack
description: My Test Pack
version: 1.0.0
author: StackStorm, Inc.
email<EMAIL_ADDRESS>vagrant@stackstorm:~/mypack$

Installing the pack works fine:
vagrant@stackstorm:~$ st2 pack install file:///home/vagrant/mypack

	[ succeeded ] download pack
	[ succeeded ] make a prerun
	[ succeeded ] install pack dependencies
	[ succeeded ] register pack

+-------------+------------------+
| Property    | Value            |
+-------------+------------------+
| name        | My Pack          |
| description | My Test Pack     |
| version     | 1.0.0            |
| author      | StackStorm, Inc. |
+-------------+------------------+
vagrant@stackstorm:~$

At this point it is registered, but we will re-register everything to see if we can trigger any errors:
vagrant@stackstorm:~$ sudo st2ctl reload --register-all
Registering content...[flags = --config-file /etc/st2/st2.conf --register-all]
2019-02-20 14:50:01,751 INFO [-] Connecting to database "st2" @ "<IP_ADDRESS>:27017" as user "stackstorm".
2019-02-20 14:50:01,791 INFO [-] Successfully connected to database "st2" @ "<IP_ADDRESS>:27017" as user "stackstorm".
2019-02-20 14:50:02,364 INFO [-] =========================================================
2019-02-20 14:50:02,366 INFO [-] ############## Registering triggers #####################
2019-02-20 14:50:02,367 INFO [-] =========================================================
2019-02-20 14:50:02,602 INFO [-] Registered 0 triggers.
2019-02-20 14:50:02,605 INFO [-] =========================================================
2019-02-20 14:50:02,606 INFO [-] ############## Registering sensors ######################
2019-02-20 14:50:02,607 INFO [-] =========================================================
2019-02-20 14:50:02,651 INFO [-] Registered 1 sensors.
2019-02-20 14:50:02,657 INFO [-] =========================================================
2019-02-20 14:50:02,660 INFO [-] ############## Registering runners ######################
2019-02-20 14:50:02,664 INFO [-] =========================================================
2019-02-20 14:50:04,686 INFO [-] Registered 18 runners.
2019-02-20 14:50:04,686 INFO [-] =========================================================
2019-02-20 14:50:04,686 INFO [-] ############## Registering actions ######################
2019-02-20 14:50:04,686 INFO [-] =========================================================
2019-02-20 14:50:08,612 INFO [-] Registered 76 actions.
2019-02-20 14:50:08,612 INFO [-] =========================================================
2019-02-20 14:50:08,613 INFO [-] ############## Registering rules ########################
2019-02-20 14:50:08,613 INFO [-] =========================================================
2019-02-20 14:50:08,705 INFO [-] Registered 1 rules.
2019-02-20 14:50:08,705 INFO [-] =========================================================
2019-02-20 14:50:08,705 INFO [-] ############## Registering aliases ######################
2019-02-20 14:50:08,705 INFO [-] =========================================================
2019-02-20 14:50:08,928 INFO [-] Registered 11 aliases.
2019-02-20 14:50:08,928 INFO [-] =========================================================
2019-02-20 14:50:08,929 INFO [-] ############## Registering policy types #################
2019-02-20 14:50:08,930 INFO [-] =========================================================
2019-02-20 14:50:08,961 INFO [-] Registered 3 policy types.
2019-02-20 14:50:08,962 INFO [-] =========================================================
2019-02-20 14:50:08,963 INFO [-] ############## Registering policies #####################
2019-02-20 14:50:08,963 INFO [-] =========================================================
2019-02-20 14:50:08,965 INFO [-] Registered 0 policies.
2019-02-20 14:50:08,966 INFO [-] =========================================================
2019-02-20 14:50:08,967 INFO [-] ############## Registering configs ######################
2019-02-20 14:50:08,968 INFO [-] =========================================================
2019-02-20 14:50:08,973 INFO [-] Registered 0 configs.
##### st2 components status #####
st2actionrunner PID: 1014
st2actionrunner PID: 1070
st2actionrunner PID: 1103
st2actionrunner PID: 1106
st2actionrunner PID: 1114
st2actionrunner PID: 1117
st2actionrunner PID: 1129
st2actionrunner PID: 1133
st2actionrunner PID: 1143
st2actionrunner PID: 1146
st2api PID: 796
st2api PID: 2150
st2stream PID: 799
st2stream PID: 2149
st2auth PID: 790
st2auth PID: 2172
st2garbagecollector PID: 805
st2notifier PID: 813
st2resultstracker PID: 811
st2rulesengine PID: 814
st2sensorcontainer PID: 818
st2chatops is not running.
st2timersengine PID: 823
st2workflowengine PID: 792
st2scheduler PID: 800
mistral-server PID: 1063
mistral.api PID: 1021
mistral.api PID: 2124
mistral.api PID: 2133
vagrant@stackstorm:~$

So far so good. I'll do some more tests with adding actions & sensors to this pack.

@LindsayHill

Out of interest, why were you doing st2 pack install, then doing manual copy & registration?

st2 pack install is a current workaround for me to register all **.yaml files. I do copy to update all my *.py files as they don't require any reload.
Since manual registration doesn't work for me, every time i need to update any yaml file, i had to do everything from scratch

remove pack: st2 pack remove nexus3
install again : st2 pack install nexus3

It's possible that what's happened here is that you still have some reference to the sensor in the DB. Just deleting the content from disk doesn't delete it from DB.

Not sure. Probably not. otherwise  st2 pack list and st2 sensor list should pick something.

@LindsayHill
please pull this repo and try to register it:
https://github.com/sahilsk/stackstorm-nexus3

Thanks for that repo. I just installed it, and then also did a reload, and everything works as expected:
vagrant@stackstorm:~$ st2 pack install https://github.com/sahilsk/stackstorm-nexus3

	[ succeeded ] download pack
	[ succeeded ] make a prerun
	[ succeeded ] install pack dependencies
	[ succeeded ] register pack

+-------------+----------------------------------+
| Property    | Value                            |
+-------------+----------------------------------+
| name        | Sontatype nexus3                 |
| description | Sontatype nexus3 stackstorm pack |
| version     | 0.1.0                            |
| author      | Sonu K. Meena                    |
+-------------+----------------------------------+
vagrant@stackstorm:~$ sudo st2ctl reload --register-all
Registering content...[flags = --config-file /etc/st2/st2.conf --register-all]
2019-02-20 15:02:55,039 INFO [-] Connecting to database "st2" @ "<IP_ADDRESS>:27017" as user "stackstorm".
2019-02-20 15:02:55,081 INFO [-] Successfully connected to database "st2" @ "<IP_ADDRESS>:27017" as user "stackstorm".
2019-02-20 15:02:55,715 INFO [-] =========================================================
2019-02-20 15:02:55,716 INFO [-] ############## Registering triggers #####################
2019-02-20 15:02:55,716 INFO [-] =========================================================
2019-02-20 15:02:56,024 INFO [-] Registered 0 triggers.
2019-02-20 15:02:56,025 INFO [-] =========================================================
2019-02-20 15:02:56,025 INFO [-] ############## Registering sensors ######################
2019-02-20 15:02:56,026 INFO [-] =========================================================
2019-02-20 15:02:56,064 INFO [-] Registered 1 sensors.
2019-02-20 15:02:56,064 INFO [-] =========================================================
2019-02-20 15:02:56,065 INFO [-] ############## Registering runners ######################
2019-02-20 15:02:56,065 INFO [-] =========================================================
2019-02-20 15:02:57,951 INFO [-] Registered 18 runners.
2019-02-20 15:02:57,952 INFO [-] =========================================================
2019-02-20 15:02:57,952 INFO [-] ############## Registering actions ######################
2019-02-20 15:02:57,952 INFO [-] =========================================================
2019-02-20 15:03:00,997 INFO [-] Registered 85 actions.
2019-02-20 15:03:00,998 INFO [-] =========================================================
2019-02-20 15:03:00,999 INFO [-] ############## Registering rules ########################
2019-02-20 15:03:01,002 INFO [-] =========================================================
2019-02-20 15:03:01,047 INFO [-] Registered 1 rules.
2019-02-20 15:03:01,048 INFO [-] =========================================================
2019-02-20 15:03:01,048 INFO [-] ############## Registering aliases ######################
2019-02-20 15:03:01,048 INFO [-] =========================================================
2019-02-20 15:03:01,297 INFO [-] Registered 11 aliases.
2019-02-20 15:03:01,298 INFO [-] =========================================================
2019-02-20 15:03:01,299 INFO [-] ############## Registering policy types #################
2019-02-20 15:03:01,299 INFO [-] =========================================================
2019-02-20 15:03:01,348 INFO [-] Registered 3 policy types.
2019-02-20 15:03:01,349 INFO [-] =========================================================
2019-02-20 15:03:01,349 INFO [-] ############## Registering policies #####################
2019-02-20 15:03:01,350 INFO [-] =========================================================
2019-02-20 15:03:01,378 INFO [-] Registered 1 policies.
2019-02-20 15:03:01,380 INFO [-] =========================================================
2019-02-20 15:03:01,381 INFO [-] ############## Registering configs ######################
2019-02-20 15:03:01,382 INFO [-] =========================================================
2019-02-20 15:03:01,383 INFO [-] Registered 0 configs.
##### st2 components status #####
st2actionrunner PID: 1014
st2actionrunner PID: 1070
st2actionrunner PID: 1103
st2actionrunner PID: 1106
st2actionrunner PID: 1114
st2actionrunner PID: 1117
st2actionrunner PID: 1129
st2actionrunner PID: 1133
st2actionrunner PID: 1143
st2actionrunner PID: 1146
st2api PID: 796
st2api PID: 2150
st2stream PID: 799
st2stream PID: 2149
st2auth PID: 790
st2auth PID: 2172
st2garbagecollector PID: 805
st2notifier PID: 813
st2resultstracker PID: 811
st2rulesengine PID: 814
st2sensorcontainer PID: 818
st2chatops is not running.
st2timersengine PID: 823
st2workflowengine PID: 792
st2scheduler PID: 800
mistral-server PID: 1063
mistral.api PID: 1021
mistral.api PID: 2124
mistral.api PID: 2133
vagrant@stackstorm:~$

My current suspicion is that you have something else somewhere under /opt/stackstorm/packs that is causing problems at registration time, since it tries to register everything it finds.

When you do st2 pack install, it only registers that pack-specific content. When you do st2ctl reload, it tries to register everything. Might be some other content you have there that is breaking things. Unfortunately the registration script is not telling us exactly which file it is that causes problems.
But here's something interesting: In that repo you provided, you have this: name: Sontatype nexus3
But: look at the error message you were getting earlier: 'Sontatype Nexus3' does not match '^[a-z0-9_]+$'
Note the upper-case "Nexus3".
So now I'm pretty sure that you've got something leftover or incorrectly copied under /opt/stackstorm/packs (or any other path you have configured under system_packs_base_path).
You could try something like grep -r Nexus3 /opt/stackstorm/packs to track it down

@LindsayHill  nice catch.  Something fishy was going on. I didn't find anything buggy inside packs directory.
I re-created stackstorm container from st2-docker  with all volumes pruned. This time everything is working smoothly.
During development of this pack, I did change pack name multiple times.  This could have left some dangling sensors inside.
Anyways, thanks for the help @LindsayHill
btw, in future you can leverage this stackstorm pack scaffolding project : generator-st2pack (alpha) to create pack instantly.

Odd, must have been something hanging around. Good to know it's working now.
There's also this for pack scaffolding - https://github.com/EncoreTechnologies/cookiecutter-stackstorm


Make BaseInput overridable

Reasons for making this change
All the other components in registry fields & widgets are overridable. BaseInput shouldn't be an exception. Customizing BaseInput is useful e.g. for propagating changes only on text input blur.
BTW there is something wrong with the npm commit hook - after pushing the first commit I noticed that some files were prettified after pushing, but the prettified changes were in git staging and weren't pushed.
Checklist

[ ] I'm updating documentation

[ ] I've checked the rendering of the Markdown text I've added
[ ] If I'm adding a new section, I've updated the Table of Content

[x] I'm adding or updating code

[ ] I've added and/or updated tests
[ ] I've updated docs if needed
[x] I've run npm run cs-format on my branch to conform my code to prettier coding style

[ ] I'm adding a new feature

[ ] I've updated the playground with an example use of the feature

Looks OK to me. Can we add a brief note to the documentation explaining that this is possible and why you might want to do this?
Regarding the commit hook, I've never heard of it accidentally not committing stuff. I'm more familiar with husky committing too much stuff, as in https://github.com/Kinto/kinto-admin/issues/419.

Can we change 'BaseInput' to 'BaseInputWidget' to make it consistent?
Since BaseInput is not an open API, the name change should not affect anyone anyway.

That sounds OK to me.

Can we change 'BaseInput' to 'BaseInputWidget' to make it consistent?
Since BaseInput is not an open API, the name change should not affect anyone anyway.

On the other hand, excluding the "Widget" part in the component/file name communicates that it's not a widget. It isn't a widget because you can't use BaseInput with ui:widget in uiSchema. Maybe we should move it away from widgets directory or use an underscore in the file name, but I think it's OK like it is now.

Thanks!

Hi guys,
I've just updated to the latest version of react-jsonschema-form and faced the issue with Jest snapshot tests. We have a custom widget that is actually a wrapper for original TextWidget.
With that PR being merged to master, snapshot test of custom widget is starting to fail with "unable to read property widgets of undefined".
Shouldn't default registry be defined as a default prop for TextWidget? I found a workaround providing registry as a property for custom widget but that looks like a hack to me.
import { getDefaultRegistry } from 'react-jsonschema-form/lib/utils';
<CustomTextWidget  registry={getDefaultRegistry()} />

Please share your thoughts.

The registry property must be passed to child fields/widgets always. If BaseInput doesn't receive registry, then it's likely that some of your custom fields/widgets doesn't pass the registry property properly.
We can't use the default registry as a default, because then the custom fields/widgets wouldn't be used.

@olzraiti, thanks for the response!
Shouldn't we define registry as a required propType than?

@anlesk Yes, good idea. Feel free to open a pull request for that :)


Review and update CHIP architecture pyramid

Just have a doubt regarding the protocol stack:

Why are the bottom two layers (message framing and routing & IP framing and transport management) present in the application layer?
What are their functions? The tasks mentioned in the README file seem like these should be executed in the the lower layers of the IP stack.

SW BRB: @robszewczyk @anush-apple  Care to take a peek?

SW BRB: @robszewczyk @anush-apple  Care to take a peek?

Stale.


DHCP indicate new config if there's a packet buffer provided

Description
If the user provides a buffer in which to store the packets, then the contents of the received packet will be buffered and included in the returned Config when the DHCP connection is made. However, it isn't included in the Config struct until the value is returned to the user, so the equality check for whether to call config_changed disregards any additional information in the buffer beyond what this library parses.
For my purposes, I need access to the contents of the buffer when they change as a result of a new packet, even if everything else is the same. Since two packets will almost certainly not be the same thanks to the magic cookie (unless the packet gets duplicated on the network, which is an acceptably low risk for my use of smoltcp), an acceptable option for my uses is to just always return the new configuration when a packet is received (gated on whether a buffer is provided to return the packet into).
Alternatives
While this approach is the easiest and best for my uses, I can think of the following alternatives which would also work and might be preferred for other use-cases:

Allow the user to specify whether they wish to receive all packets instead of opting all users who provide a buffer into this behavior
Allow the user to provide a closure which compares the old and new packets and returns true if this represents a new config which should be returned.
Compare the old packet to the new packet (either byte-by-byte or looking at the provided options) and only return a new config if differences are found.

Verification
In my setup, I was seeing bugs that were caused by smoltcp not exposing the config when the only changes were in the additional options that I want to use but which smoltcp doesn't use directly. Using this branch instead of the main release fixed those bugs and I was able to verify that it behaves the way I expected. I think this verification, along with CI tests passing, should be sufficient for verifying this PR.

Are there any updates on this? Are you guys considering what to do with this? Not interested in accepting this PR? Wanting me to do one of the alternatives I listed? Too busy to look at it now and planning to get around to looking at this at some point? I'd appreciate some sort of feedback so I can know where this PR stands.


Document consul proto URI correctly

LGTM, thanks Ahmet

@abronan needs to confirm, but I think consul only takes one addr.
@ahmetalpbalkan are you using an outdated version of swarm ? here is the current usage:

@vieux yes I think I was using 0.2.0, however why in your screenshot consul doesn't list multiple IPs? Is it not supported?

@ahmetalpbalkan Consul only takes one address :) See #583 for more informations.

@ahmetalpbalkan It was a documentation error that we fixed in 0.3.

@abronan hmm, I'm using swarm version 0.3.0 (28cd51b) and join --help also shows 1 IP for consul. However my manager runs with multiple consul IPs without giving any errors?
azureuser@swarm-master-0:~$ docker inspect compose_swarm_1 | head -n 12
[
{
    "Id": "8122b9bb9930e2ca419702d91555bc92c87538bf92c4bf29f438a9af175cbb99",
    "Created": "2015-07-26T02:11:20.3822512Z",
    "Path": "/swarm",
    "Args": [
        "manage",
        "--replication",
        "--advertise",
        "<IP_ADDRESS>:2376",
        "consul://<IP_ADDRESS>:8500,<IP_ADDRESS>:8500,<IP_ADDRESS>:8500/nodes"
    ],

@ahmetalpbalkan Good point! The discovery part changed a lot since 0.2 and this is actually due to the migration to libkv. So swarm will accept multiple IPs but libkv will discard other specified IPs for Consul. I guess that we should add a check upstream in swarm to avoid confusion or just ignore and document that properly.

@abronan ok opening another bug.


Pass the codecov token in CI to the uploader

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 84.11%. Comparing base (2b9c3a4) to head (f479863).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1737      +/-   ##
==========================================
+ Coverage   79.95%   84.11%   +4.16%
==========================================
  Files         197      198       +1
  Lines       21879    22241     +362
  Branches     4342     4695     +353
==========================================
+ Hits        17494    18709    +1215
- Misses       2252     2610     +358
+ Partials     2133      922    -1211

Flag
Coverage Δ

py-unittests
84.11% <ø> (+4.16%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 107 files with indirect coverage changes

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9d875e7...f479863. Read the comment docs.

I have the same fix in #1739. This PR can be dropped

@markreidvfx looks like the token way was still failing, trying via an env var now.

@ssteinbach I'm pretty sure token works. At least that how I got it working on my fork before I created the arm64 PR. using CODECOV_TOKEN never worked for me.


Bump version of dependency eyeglass

Bump version of dependency eyeglass to fix build error
of sub-dependency deasync with newer node releases.
Pull Request for fixing issue https://github.com/danielguillan/modernizr-mixin/issues/26.

Does the CI also test for successful installation/usage as eyeglass package?

Thank you very much, @strarsis!
I don't use Eyeglass so I would greatly apreciate a pull request including those CI tests too!


RBD create panel defaults to 3 rbds

When creating a new RBD in ceph the ui defaults to creating 3. It should default to 1

#291


Failed Jenkins Build

Travis failed to build due to wrong angular version. Angular bootstrap requires version lesser than 1.3.0.
We can either:

Downgrade angular version
Replace drop down menu with material's select.

As for now I am favouring second option as it is only one dependency on angular bootstrap, i.e the drop down being used as logout.
See commit 2b046691d3.

Due to dateline. We will replace the logout with a normal link for now.

Keeping an eye on the development of md-menu which suits our need here perfectly. It is expected to be out in 0.10.0 release.


Stay compatible with legacy PHP versions

Hi,
I sometimes use the " PentesterLab Free VM - From SQL Injection to Shell" to teach application security, and in June students report that p0wny@shell doesn't work.
In fact, the VM use a legacy PHP version (X-Powered-By: PHP/5.3.3-7+squeeze3) and p0wny@shell v2023.05.10 and above use short array syntax [] introduced in PHP 5.4.
By replacing [] by the old syntax array() the new version works well with old PHP versions 5 (and above of course). It's easier to do as changing the PHP version of the VM :wink:.

PHP 5.3.x is quite old and should not be used anymore (not supported for 9 years).
But I don't see any disadvantage in merging this, except for worse readability.

As there is still old PHP versions in production, I think it is a good idea to be compatible.
Thank you for the PR :)


[GSSOC'21] Linear Search and Binary Search  in Python

Hi I am Malavika R Vikraman , participating in GSSOC'21 .
I would like to contribute by adding Linear Search and Binary Search  in Python  to this project.
Kindly assign this issue to me!
@anubhavitis @dheerajkotwani @tarun26091999 @todi-2000 @geekquad @plazzy99

hii @anubhavitis  please assign this issue to me I am gssoc'21 participant

binary search present at #106. raise separate issue for linear search.

@tarun26091999  I have created a issue #602  . Please do Kindly Assign it to me


HIP-RA & Monte Carlo user manual instructions

https://github.com/softwareengineerprogrammer/GEOPHIRES-X/commit/44b56fd527518ef4fd2cbcd26f3ecb80cc1aee35


Added urlrewrite plugin for Rlsbb

Motivation for changes:
rlsbb does not provide all possible download links (notably rapidgator links are missing) in their rss feed.
This urlrewrite plugin grabs additional links from the rlsbb.ru website and adds them to the urls field of the entry.
This plugin works similar to the rmz urlrewrite plugin which was just pulled recently:
#1879
Detailed changes:
rlsbb.ru urlrewriter
Version 0.1

Configuration

rlsbb:
  filehosters_re:
    - domain\.com
    - domain2\.org
  link_text_re:
    - UPLOADGiG
    - NiTROFLARE
    - RAPiDGATOR
  parse_comments: no

filehosters_re: Only add links that match any of the regular expressions
  listed under filehosters_re.
link_text_re: search for <a> tags where the text (not the url) matches
  one of the given regular expressions. The href property of these <a> tags
  will be used as the url (or urls).
parse_comments: whether the plugin should also parse the comments or only
  the main post. Note that it is highly recommended to use filehosters_re
  if you enable parse_comments. Otherwise, the plugin may return too
  many and even some potentially dangerous links.

If more than one valid link is found, the url of the entry is rewritten to
the first link found. The complete list of valid links is placed in the
'urls' field of the entry.

Therefore, it is recommended, that you configure your output to use the
'urls' field instead of the 'url' field.

For example, to use jdownloader 2 as output, you would use the exec plugin:
exec:
  - echo "text={{urls}}" >> "/path/to/jd2/folderwatch/{{title}}.crawljob"

Config usage if relevant (new plugin or updated schema):
    rlsbb:
      filehosters_re:
        - domain\.com
        - domain2\.org
      link_text_re:
        - UPLOADGiG
        - NiTROFLARE
        - RAPiDGATOR
      parse_comments: no

Log and/or tests output (preferably both):
DEBUG  rlsbb  TASK  Searching <entry url> for a tags where the text matches one of: <link_text_re>
DEBUG  rlsbb  TASK  Found link elements: <html <a> elements>
DEBUG  rlsbb  TASK  Comment parsing enabled: found <number> comments
WARNING  rlsbb  TASK  You have enabled comment parsing but you did not define any filehoster_re filter. You may get a lot of unwanted and potentially dangerous links from the comments.
DEBUG  rlsbb  TASK  Using filehosters_re filters: <list of filter expressions>
DEBUG  rlsbb  TASK  Url: "<link found at entry url>" matched filter: <expression>

VERBOSE  rlsbb  TASK  Found <number> links at <entry url>

To Do:

[ ] Add ability to work as a search plugin.

Thanks a lot!


Allow parameters block for StorageClass

Documentation around parameters block for storageClass - https://kubernetes.io/docs/concepts/storage/storage-classes/#parameters
For our use-case we wanted the volume to be of xfs file system and we were able to achieve it with this block -
parameters:
  fsType: xfs

So, I am adding a way in helm chart to specify parameters block for the storageClass.

@mdfaizsiddiqui
local-path-provisioner actually creates a directory on a local filesystem (it can be xfs, ext4 and so one), so the fsType seems not really used.
Can you elaborate more on the fsType? Thank you.

this is also useful if you want to achieve other things, like eg. limiting default storageClass to some notePath:
parameters:
  nodePath: /srv/k8s/pv/default

@mdfaizsiddiqui Can you help resolve the conflicts? Thank you.

@mdfaizsiddiqui Can you help resolve the conflicts? Thank you.

Hey, I've fixed all the conflicts, but due to this new change I had to moved the parameter introduced as part of this PR  to the new parameters section.

@derekbit can you help merge this PR, thanks.


PYIC-3796: Add evaluate gpg45 scores to end

Proposed changes
What changed

Added a lambda call to the end, where it would normally go straight to IPV_SUCCESS_PAGE

Add new CHECK_GPG45_SCORES state behind gpg45ScoresAtEnd flag

Why did it change

Because we're trying to make the only call of the evaluate gpg45 call at the end, to evaluate a profile

Issue tracking

PYIC-3796

Checklists
Environment variables or secrets

[ ] Documented in the README
[ ] Added to deployment repository
[ ] Added to local startup repository

I've tested it with and without the feature flag, both work for the automated tests
I use this to run the automated tests:
F2F_QUEUE_NAME=stubQueue_F2FQueue_dev-mikec CIMIT_API_KEY=HJ2vVrlAi53LotGQ3XeRma54IwXuhu6f6JTBLUFo ORCHESTRATOR_STUB_URL='https://orchstub:348/tuj![hsDd@dev-mikec.02.core.dev.stubs.account.gov.uk](mailto:hsDd@dev-mikec.02.core.dev.stubs.account.gov.uk)' BROWSER=chrome-headless ./gradlew runTests -Ptags="@Build" -Pthreads="10"


Support more style range options

I'm curious when full is wanted/needed?

I suppose I've had a few float rasters but the data range was always much larger than 255 and thus the tiles would come back looking a single color. Setting full to 1 might still have the same issue?

All makes sense! Thanks for the explanation!


apiextensions.k8s.io/v1beta1

Hello,
Is there a way to generate CRDs compatible with apiextensions.k8s.io/v1beta1 in operator 0.18?
This's required to run operator in k8s < 1.16
Thanks

Hi @kotyara85,
Yes. You can use the flag --crd-version=v1beta1 to generate the CRD's in using the old api. Also, note that you can use the flag --help to get all options for the commands or check its docs for the specific version. For example see: https://v0-18-x.sdk.operatorframework.io/docs/cli/operator-sdk_add_crd/. It might help you.
Closing this one as sorted out.


Added  Code of Conduct to project

Pull Request Template
What have you Changed(must)
Write here what you have changed in the codebase
Issue no.(must) -
Pr will be close and marked as spam. If issue number not found or issue was assigned to someone else.
Marking as spam can block your account from HacktoberFest.
Self Check(Tick After Making pull Request)

[ ] This issue was assigned to me if not it will be marked as spam.
[ ] My file is in the proper folder
[x] I am following clean code and Documentation.
[ ] I have added the title and what program will do first in the file
[ ] I have named the file as (Problem #). (Problem Title(in Camel Case)).(extension)
ex. 2. AddToNumbers.py

README - How to Contribute

@jivthesh you have to mention the issue number in the PR Body.


refactor: free list page ref & mut

Adds types that encapsulate manipulation of a free list page.

#399  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @pepyakin and the rest of your teammates on  Graphite


Clarify in the docs matching by wildcard of the sni_domains field in listener components

title: sni_domains: clarify in the documentation matching by a wildcard
Description:
According to https://github.com/envoyproxy/envoy/blob/a22159aa1274f63b1b83e56ccc4482e0a01a6d80/source/common/ssl/context_manager_impl.cc#L116
the wildcard is allowed before the first dot, it means that www.example.com will be matched by an SNI domain *.example.com, but not by *.com or *. The proposed PR changes the docs to explain it.
Risk Level: Low
Testing:
Documentation change, no testing.
Docs Changes:
The PR is a docs change only.
Release Notes:
None.
Fixes #3363 .

Closing it since the commits were not signed, my first PR to Envoy, sorry. Resubmitted with a signed commit https://github.com/envoyproxy/envoy/pull/3372.


Tab no longer acts as expected in settings

When I tab complete a settings key in the past I would hit tab again to complete it, however now this just moved the cursor to the end.

Result after tab:

This is a regression in 1.25.

:) Wow @octref That's quite some findings
Auto-completions are not completed on pressing tab in Insiders if you are in snippet mode and not at the last tab stop of the snippet
That's why you dont see the issue when you changed $1 -> $0
The change in behavior was made as part of #50776
This not only affects json files but all files that use snippets. The issue is under discussion in #51722
We can keep this issue open if we want to change the json language service to return $0 when there is a single tab stop.
Else, we should close in favor of #51722

@jrieken Another option is update snippets with single tab stop such that the single tab stop is always $0

If I get this right, the problem is that tab is used both in the suggest widget and for snippets.
If both the suggest widget is open and the user is in snippet mode, who to give precedence?
IMO it has to be the suggest widget, especially if the user already use cursor down to select a specific proposal.


How to run a function on onclick event in a button?

Im trying to run a function on onclick event, like here https://github.com/karaxnim/karax/blob/master/tests/nativehtmlgen.nim
How can i change "javascript:myFunc()" with nim's functions, or at least include js function in a nim file?

You could create a separate module that you compile to js.
proc myFunc {.exportc.} =
  echo "hello"

And load that on your page so that it runs when the user clicks the link.
It may be better though to create a karax SPA instead of using it for server side templates, depending on what you are building?

I'm just trying nim out, awesome language. I did what you suggested and got file.js, now im not sure how to include it inside file.nim so i can use that function on onclick = . I'm sorry I'm still noob.

You could add this line into your karax template to load the script:
script(`type`="text/javascript", src="./file.js")

Though your webserver will need to serve it somehow.
If the webpage you are building has a lot of interactivity I would recommend building it as an SPA (compile a karax app to js) instead of using server side templates. If you need help or advice I'd suggest joining the #webdev channel on the Nim chat channels (discord/irc/matrix etc)

I'm going to close this for now, please re-open and comment if you want to discuss this further @Corazone777


[QUESTION] Unexpected behaviour of BackgroundTask in AWS Lambda

First check

[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the FastAPI documentation, with the integrated search.
[x] I already searched in Google "How to X in FastAPI" and didn't find any information.

Description
I'm running FastAPI on AWS Lambda using Magnum ASGI adapter like below where handler is the entry point for API endpoints specified in serverless.yml.
from fastapi import FastAPI
from mangum import Mangum

app = FastAPI()

handler = Mangum(app)

I have recently implemented a BackgroundTask on one of the route endpoints as documented in FastAPI which has to generates a CSV file and upload to S3 and then send an email to the user. The setup works fine locally using uvicorn (bypassing Magnum) and returns a quick HTTP response while the background task takes its own sweet time and does its work.
However, when deployed on AWS Lambda, the request doesn't complete until the background task is also completed in the same request which increases the response latency and defeats the whole purpose of using a BackgroundTask.
What could be going wrong here?
Additional context
Python: 3.8
FastAPI: 0.54

@tiangolo Any updates on this?

Reference: https://stackoverflow.com/questions/44668605/aws-lambda-to-run-in-background-even-after-sending-response-to-api-gateway

Thanks, @phy25 for the link. It looks like all synchronous invocations must complete fully before sending a response. I have made plans to use Step Functions to execute my workflow, just wanted to confirm if this is not limited by FastAPI in any way before moving ahead with the implementation.

Thanks for the help here @phy25 ! :clap: :bow:
Thanks for reporting back and closing the issue @anil-grexit  :+1:
Yeah, as I understand those function services like lambda start the app only for the request and kill it right after.

@tiangolo Google Cloud Function supports "Async tasks" .

@tiangolo Google Cloud Function supports "Async tasks" .

@aniljaiswal How did you solve this? I have the exact same setup.

@renkasiyas The way lambda works is that once the request is completed, the lambda returns a response and is ready to handle other requests. So any background tasks you queue in async fashion is lost. I am using SQS to push those background tasks and they are handled via a different lambda function.