unixproxy and socksproxy are used before config files are parsed

Right now you can't configure unixproxy or socksproxy in the yaml files because they are used before the config files are loaded.

Weird, I thought this used to work.  I confirmed what you are seeing, I will try to figure out how to fix this.  Thanks!
-Cory

Fixed and released: https://github.com/Netflix-Skunkworks/go-jira/releases/tag/v1.0.14


eureka-client1.10.14  rejected from java.util.concurrent.ThreadPoolExecutor

I used the eureka-client1.10.14 version in SpringCloud2020.3. There are some WARN logs recently. I put the detailed information below. Is it because my thread pool is not enough?  looking forward to the reply;
WARN c.n.discovery.TimedSupervisorTask -task supervisor rejected the task
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@4bbc4fb3 rejected from java.util.concurrent.ThreadPoolExecutor@6577728a[Running, pool size = 2, active threads = 2, queued tasks = 0, completed tasks = 19838]
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112)
at com.netflix.discovery.TimedSupervisorTask.run(TimedSupervisorTask.java:66)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Hello, @Sunywdev, the 2020.x line is no longer supported. Please upgrade to 2021.x and verify if the issue persists.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Use middleware approach to handle callbacks

Middleware allows caller to add custom functions to work with Secrets as they see fit. This option allows multiple layers callback and also leaves concurrent and blocking problem to the caller.
~We still need to open up Secrets to allow the caller to interact with it.~
This is entirely open for discussion. I just find it easier to express the idea with actual code :)

The middleware part looks good to me in general, but we still need to export enough fields to Secret to make it useful to the callers.

Thought I would have a different PR for that as we haven't decide what/how to open up Secrets.

@konradreiche what do you think of this approach? Also what's your opinion on how to open up Secrets? Adding accessors to secret maps could be one way, we just need to make sure it's read only with mutex.
Also, what's the value in vault attribute?
cc @fishy

Added Secrets accessor, PTAL

What the are use cases for the middlewares here? @andizzle you wrote:

This option allows multiple layers callback and also leaves concurrent and blocking problem to the caller.

What would be a concrete example that would justify adding this additional complexity?

What would be a concrete example that would justify adding this additional complexity?

Considering the Store can hold multiple secrets, it is possible that the main application runs different secret consumers that needs their own callback logic. For example, an application could be using a kafka producer that requires authentication, a thridparty integration point that requires api token, and a message encryption key that encrypts outgoing messages.
Use multiple middlewares helps avoid a big callback function that has mixed secrets load/reload logic. Each secret consumer can hook up with the callback with their own middleware, it's much smaller footprint.
One can also create individual call functions and call then in a final callback functions that is hooked up in the Store, but that requires more organization and planning on the client side, which may not be very intuitive for the caller.

To Allow register middleware from other lib, we just need to make this function public.
https://github.com/reddit/baseplate.go/pull/20/files#diff-1a3fa2e612f9f352390e03634cc256d0R70

To allow register middleware from other lib, we just need to make this function public.
https://github.com/reddit/baseplate.go/pull/20/files#diff-1a3fa2e612f9f352390e03634cc256d0R70

It will be slightly more complex than that. After Store is initialized, calling that function will not give you the initial secret values, instead, the new middleware will only be called when the next time secrets changes. So we need to call the new middleware with whatever we already have when a new middleware is registered.

I see. The middleware needs to be called upon registration in this scenario. I need to put more thoughts into this. This does make it a compelling reason to keep the middleware approach.


Python: SignedTransaction payload changes

https://github.com/iotaledger/iota-sdk/pull/1483

[ ] Remove all occurrences of essence.

Closed by https://github.com/iotaledger/iota-sdk/pull/1553


Webpack cache not compatible with mini-css-extract-plugin

Bug report
What is the current behavior?
module.cache.cacheDirectory is not compatible with mini-css-extract-plugin
Receive the following error
2021-01-20-07:34:23 3|admin-webpack   | <w> [webpack.cache.PackFileCacheStrategy] Skipped not serializable cache item 'mini-css-extract-plugin /home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less|0|Compilation/modules|/home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less': No serializer registered for Warning
If the current behavior is a bug, please provide the steps to reproduce.
Install mini-css-extract-plugin and have webpack config with
    cache: {       type: 'filesystem',       cacheDirectory: './cache',     },
What is the expected behavior?
Allow plugin to be resolved or to have a way to ignore exclude module plugin. Previously, hard-source-webpack-plugin had a way to exclude module plugins, but since that plugin is no longer needed in due to webpack's built in cache system it would be nice to either allow it to be resolved with mini-css-extract-plugin or ignore it.
Other relevant information:
webpack version:  5.16.0
Node.js version: 14.15.4

These is some warning emitted somewhere in the chain, which is not serializable. Caching is automatically skipped for that item. The remaining items will still be cached.

These is some warning emitted somewhere in the chain, which is not serializable. Caching is automatically skipped for that item. The remaining items will still be cached.

@gita-v Please provide reproducible test repo

@gita-v Please provide reproducible test repo

Sorry I did not include entire messages -- when I do stats.logging = verbose I do not receive any additional logs, is there anyway else to debug?
2021-01-20-14:48:29 3|admin-webpack   | <i> [webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Node.js doesn't offer a (nice) way to introspect the ESM dependency graph yet.
2021-01-20-14:48:29 3|admin-webpack   | <i> Until a full solution is available webpack uses an experimental ESM tracking based on parsing.
2021-01-20-14:48:29 3|admin-webpack   | <i> As best effort webpack parses the ESM files to guess dependencies. But this can lead to expensive and incorrect tracking.
2021-01-20-14:48:33 3|admin-webpack   | <w> [webpack.cache.PackFileCacheStrategy] Skipped not serializable cache item 'mini-css-extract-plugin /home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less|0|Compilation/modules|/home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less': No serializer registered for Warning
2021-01-20-14:48:33 3|admin-webpack   | <w> while serializing webpack/lib/cache/PackFileCacheStrategy.PackContentItems -> webpack/lib/NormalModule -> Array { 1 items } -> webpack/lib/ModuleWarning -> Warning

Okay, I will try and include repro test repo :)

Sorry I did not include entire messages -- when I do stats.logging = verbose I do not receive any additional logs, is there anyway else to debug?
2021-01-20-14:48:29 3|admin-webpack   | <i> [webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Node.js doesn't offer a (nice) way to introspect the ESM dependency graph yet.
2021-01-20-14:48:29 3|admin-webpack   | <i> Until a full solution is available webpack uses an experimental ESM tracking based on parsing.
2021-01-20-14:48:29 3|admin-webpack   | <i> As best effort webpack parses the ESM files to guess dependencies. But this can lead to expensive and incorrect tracking.
2021-01-20-14:48:33 3|admin-webpack   | <w> [webpack.cache.PackFileCacheStrategy] Skipped not serializable cache item 'mini-css-extract-plugin /home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less|0|Compilation/modules|/home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less': No serializer registered for Warning
2021-01-20-14:48:33 3|admin-webpack   | <w> while serializing webpack/lib/cache/PackFileCacheStrategy.PackContentItems -> webpack/lib/NormalModule -> Array { 1 items } -> webpack/lib/ModuleWarning -> Warning

Okay, I will try and include repro test repo :)

What is the warning in your printed stats?

What is the warning in your printed stats?

This is entire logs
2021-01-20-14:48:29 3|admin-webpack   |  SMP  ⏱  Outputted timing info to /home/admin/code/experimental/data/speed-measure-plugin/adminApp.json
2021-01-20-14:48:29 3|admin-webpack   | assets by status 14.4 MiB [cached] 3 assets
2021-01-20-14:48:29 3|admin-webpack   | asset ../server/adminApp.manifest.json 396 bytes [compared for emit]
2021-01-20-14:48:29 3|admin-webpack   | Entrypoint admin 14.4 MiB (12.8 MiB) = admin.c39ce583af9f7c469503.css 204 KiB admin.4278b67dd41d7d451ca9.entry.js 14.2 MiB 2 auxiliary assets
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.Compiler
2021-01-20-14:48:29 3|admin-webpack   | <t> make hook: 50564.265626 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> finish make hook: 0.017626 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> finish compilation: 162.414972 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> seal compilation: 5896.216194 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> afterCompile hook: 0.023244 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> emitAssets: 14.956756 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> emitRecords: 0.09881 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.ResolverCachePlugin
2021-01-20-14:48:29 3|admin-webpack   |     19% really resolved (4833 real resolves with 0 cached but invalid, 20774 cached valid, 0 concurrent)
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.FlagDependencyExportsPlugin
2021-01-20-14:48:29 3|admin-webpack   | <t> restore cached provided exports: 14.608635 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> figure out provided exports: 42.808026 ms
2021-01-20-14:48:29 3|admin-webpack   |     100% of exports of modules have been determined (2294 not cached, 122 flagged uncacheable, 0 from cache, 51 additional calculations due to dependencies)
2021-01-20-14:48:29 3|admin-webpack   | <t> store provided exports into cache: 13.587705 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.Compilation
2021-01-20-14:48:29 3|admin-webpack   | <t> finish modules: 72.186891 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> report dependency errors and warnings: 90.207305 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> optimize dependencies: 2.281524 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> create chunks: 134.200177 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> optimize: 58.6758 ms
2021-01-20-14:48:29 3|admin-webpack   |     2399 modules hashed (0.99 variants per module in average)
2021-01-20-14:48:29 3|admin-webpack   | <t> module hashing: 252.909999 ms
2021-01-20-14:48:29 3|admin-webpack   |     100% code generated (2399 generated, 0 from cache)
2021-01-20-14:48:29 3|admin-webpack   | <t> code generation: 545.38469 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> runtime requirements: 19.188473 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: initialize hash: 0.007992 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: hash child compilations: 0.170446 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: sort chunks: 0.034117 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: hash runtime modules: 11.976173 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: hash chunks: 54.854794 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: hash digest: 0.075316 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: process full hash modules: 0.002351 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: 67.205703 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> record hash: 0.009 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> module assets: 1.403647 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> create chunk assets: 82.870847 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> process assets: 4699.4892899999995 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.SideEffectsFlagPlugin
2021-01-20-14:48:29 3|admin-webpack   | <t> update dependencies: 2.206187 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.buildChunkGraph
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: prepare: 69.631736 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: visiting: 30.8293 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: calculating available modules: 0.837674 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: merging available modules: 0.314884 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: check modules for revisit: 0.133392 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: visiting: 12.457728 ms
2021-01-20-14:48:29 3|admin-webpack   |     5028 queue items processed (2400 blocks)
2021-01-20-14:48:29 3|admin-webpack   |     1 chunk groups connected
2021-01-20-14:48:29 3|admin-webpack   |     1 chunk groups processed for merging (1 module sets, 0 forked, 0 + 0 modules forked, 0 + 0 modules merged into fork, 0 resulting modules)
2021-01-20-14:48:29 3|admin-webpack   |     1 chunk group info updated (0 already connected chunk groups reconnected)
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: 114.279067 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> connectChunkGroups: 0.205075 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> cleanup: 0.005437 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.SplitChunksPlugin
2021-01-20-14:48:29 3|admin-webpack   | <t> prepare: 0.052314 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> modules: 39.167552 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> queue: 0.237514 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> maxSize: 0.085626 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.FileSystemInfo
2021-01-20-14:48:29 3|admin-webpack   |     7128 new snapshots created
2021-01-20-14:48:29 3|admin-webpack   |     0% root snapshot uncached (0 / 20774)
2021-01-20-14:48:29 3|admin-webpack   |     0% children snapshot uncached (0 / 0)
2021-01-20-14:48:29 3|admin-webpack   |     0 entries tested
2021-01-20-14:48:29 3|admin-webpack   |     File info in cache: 6187 timestamps 0 hashes 0 timestamp hash combinations
2021-01-20-14:48:29 3|admin-webpack   |     File timestamp snapshot optimization: 45% (6715/14830) entries shared via 242 shared snapshots (1655 times referenced)
2021-01-20-14:48:29 3|admin-webpack   |     Directory info in cache: 0 timestamps 0 hashes 0 timestamp hash combinations
2021-01-20-14:48:29 3|admin-webpack   |     Missing items snapshot optimization: 82% (29011/35232) entries shared via 287 shared snapshots (4454 times referenced)
2021-01-20-14:48:29 3|admin-webpack   |     Managed items info in cache: 504 items
2021-01-20-14:48:29 3|admin-webpack   |     Managed items snapshot optimization: 15% (1160/7804) entries shared via 34 shared snapshots (158 times referenced)
2021-01-20-14:48:29 3|admin-webpack   |     Managed files snapshot optimization: 32% (3338/10443) entries shared via 183 shared snapshots (781 times referenced)
2021-01-20-14:48:29 3|admin-webpack   |     Managed contexts snapshot optimization: 0% (0/1) entries shared via 0 shared snapshots (0 times referenced)
2021-01-20-14:48:29 3|admin-webpack   |     Managed missing snapshot optimization: 34% (2382/7108) entries shared via 141 shared snapshots (337 times referenced)
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.Watching
2021-01-20-14:48:29 3|admin-webpack   | <t> done hook: 24.854293 ms
2021-01-20-14:48:29 3|admin-webpack   | webpack 5.14.0 compiled successfully in 56662 ms
2021-01-20-14:48:29 3|admin-webpack   | <i> [webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Node.js doesn't offer a (nice) way to introspect the ESM dependency graph yet.
2021-01-20-14:48:29 3|admin-webpack   | <i> Until a full solution is available webpack uses an experimental ESM tracking based on parsing.
2021-01-20-14:48:29 3|admin-webpack   | <i> As best effort webpack parses the ESM files to guess dependencies. But this can lead to expensive and incorrect tracking.
2021-01-20-14:48:33 3|admin-webpack   | <w> [webpack.cache.PackFileCacheStrategy] Skipped not serializable cache item 'mini-css-extract-plugin /home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less|0|Compilation/modules|/home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less': No serializer registered for Warning
2021-01-20-14:48:33 3|admin-webpack   | <w> while serializing webpack/lib/cache/PackFileCacheStrategy.PackContentItems -> webpack/lib/NormalModule -> Array { 1 items } -> webpack/lib/ModuleWarning -> Warning

This is entire logs
2021-01-20-14:48:29 3|admin-webpack   |  SMP  ⏱  Outputted timing info to /home/admin/code/experimental/data/speed-measure-plugin/adminApp.json
2021-01-20-14:48:29 3|admin-webpack   | assets by status 14.4 MiB [cached] 3 assets
2021-01-20-14:48:29 3|admin-webpack   | asset ../server/adminApp.manifest.json 396 bytes [compared for emit]
2021-01-20-14:48:29 3|admin-webpack   | Entrypoint admin 14.4 MiB (12.8 MiB) = admin.c39ce583af9f7c469503.css 204 KiB admin.4278b67dd41d7d451ca9.entry.js 14.2 MiB 2 auxiliary assets
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.Compiler
2021-01-20-14:48:29 3|admin-webpack   | <t> make hook: 50564.265626 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> finish make hook: 0.017626 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> finish compilation: 162.414972 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> seal compilation: 5896.216194 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> afterCompile hook: 0.023244 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> emitAssets: 14.956756 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> emitRecords: 0.09881 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.ResolverCachePlugin
2021-01-20-14:48:29 3|admin-webpack   |     19% really resolved (4833 real resolves with 0 cached but invalid, 20774 cached valid, 0 concurrent)
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.FlagDependencyExportsPlugin
2021-01-20-14:48:29 3|admin-webpack   | <t> restore cached provided exports: 14.608635 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> figure out provided exports: 42.808026 ms
2021-01-20-14:48:29 3|admin-webpack   |     100% of exports of modules have been determined (2294 not cached, 122 flagged uncacheable, 0 from cache, 51 additional calculations due to dependencies)
2021-01-20-14:48:29 3|admin-webpack   | <t> store provided exports into cache: 13.587705 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.Compilation
2021-01-20-14:48:29 3|admin-webpack   | <t> finish modules: 72.186891 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> report dependency errors and warnings: 90.207305 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> optimize dependencies: 2.281524 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> create chunks: 134.200177 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> optimize: 58.6758 ms
2021-01-20-14:48:29 3|admin-webpack   |     2399 modules hashed (0.99 variants per module in average)
2021-01-20-14:48:29 3|admin-webpack   | <t> module hashing: 252.909999 ms
2021-01-20-14:48:29 3|admin-webpack   |     100% code generated (2399 generated, 0 from cache)
2021-01-20-14:48:29 3|admin-webpack   | <t> code generation: 545.38469 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> runtime requirements: 19.188473 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: initialize hash: 0.007992 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: hash child compilations: 0.170446 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: sort chunks: 0.034117 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: hash runtime modules: 11.976173 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: hash chunks: 54.854794 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: hash digest: 0.075316 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: process full hash modules: 0.002351 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> hashing: 67.205703 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> record hash: 0.009 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> module assets: 1.403647 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> create chunk assets: 82.870847 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> process assets: 4699.4892899999995 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.SideEffectsFlagPlugin
2021-01-20-14:48:29 3|admin-webpack   | <t> update dependencies: 2.206187 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.buildChunkGraph
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: prepare: 69.631736 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: visiting: 30.8293 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: calculating available modules: 0.837674 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: merging available modules: 0.314884 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: check modules for revisit: 0.133392 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: visiting: 12.457728 ms
2021-01-20-14:48:29 3|admin-webpack   |     5028 queue items processed (2400 blocks)
2021-01-20-14:48:29 3|admin-webpack   |     1 chunk groups connected
2021-01-20-14:48:29 3|admin-webpack   |     1 chunk groups processed for merging (1 module sets, 0 forked, 0 + 0 modules forked, 0 + 0 modules merged into fork, 0 resulting modules)
2021-01-20-14:48:29 3|admin-webpack   |     1 chunk group info updated (0 already connected chunk groups reconnected)
2021-01-20-14:48:29 3|admin-webpack   | <t> visitModules: 114.279067 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> connectChunkGroups: 0.205075 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> cleanup: 0.005437 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.SplitChunksPlugin
2021-01-20-14:48:29 3|admin-webpack   | <t> prepare: 0.052314 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> modules: 39.167552 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> queue: 0.237514 ms
2021-01-20-14:48:29 3|admin-webpack   | <t> maxSize: 0.085626 ms
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.FileSystemInfo
2021-01-20-14:48:29 3|admin-webpack   |     7128 new snapshots created
2021-01-20-14:48:29 3|admin-webpack   |     0% root snapshot uncached (0 / 20774)
2021-01-20-14:48:29 3|admin-webpack   |     0% children snapshot uncached (0 / 0)
2021-01-20-14:48:29 3|admin-webpack   |     0 entries tested
2021-01-20-14:48:29 3|admin-webpack   |     File info in cache: 6187 timestamps 0 hashes 0 timestamp hash combinations
2021-01-20-14:48:29 3|admin-webpack   |     File timestamp snapshot optimization: 45% (6715/14830) entries shared via 242 shared snapshots (1655 times referenced)
2021-01-20-14:48:29 3|admin-webpack   |     Directory info in cache: 0 timestamps 0 hashes 0 timestamp hash combinations
2021-01-20-14:48:29 3|admin-webpack   |     Missing items snapshot optimization: 82% (29011/35232) entries shared via 287 shared snapshots (4454 times referenced)
2021-01-20-14:48:29 3|admin-webpack   |     Managed items info in cache: 504 items
2021-01-20-14:48:29 3|admin-webpack   |     Managed items snapshot optimization: 15% (1160/7804) entries shared via 34 shared snapshots (158 times referenced)
2021-01-20-14:48:29 3|admin-webpack   |     Managed files snapshot optimization: 32% (3338/10443) entries shared via 183 shared snapshots (781 times referenced)
2021-01-20-14:48:29 3|admin-webpack   |     Managed contexts snapshot optimization: 0% (0/1) entries shared via 0 shared snapshots (0 times referenced)
2021-01-20-14:48:29 3|admin-webpack   |     Managed missing snapshot optimization: 34% (2382/7108) entries shared via 141 shared snapshots (337 times referenced)
2021-01-20-14:48:29 3|admin-webpack   | LOG from webpack.Watching
2021-01-20-14:48:29 3|admin-webpack   | <t> done hook: 24.854293 ms
2021-01-20-14:48:29 3|admin-webpack   | webpack 5.14.0 compiled successfully in 56662 ms
2021-01-20-14:48:29 3|admin-webpack   | <i> [webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] Node.js doesn't offer a (nice) way to introspect the ESM dependency graph yet.
2021-01-20-14:48:29 3|admin-webpack   | <i> Until a full solution is available webpack uses an experimental ESM tracking based on parsing.
2021-01-20-14:48:29 3|admin-webpack   | <i> As best effort webpack parses the ESM files to guess dependencies. But this can lead to expensive and incorrect tracking.
2021-01-20-14:48:33 3|admin-webpack   | <w> [webpack.cache.PackFileCacheStrategy] Skipped not serializable cache item 'mini-css-extract-plugin /home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less|0|Compilation/modules|/home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less': No serializer registered for Warning
2021-01-20-14:48:33 3|admin-webpack   | <w> while serializing webpack/lib/cache/PackFileCacheStrategy.PackContentItems -> webpack/lib/NormalModule -> Array { 1 items } -> webpack/lib/ModuleWarning -> Warning

Please create reproducible test repo, you have a Module warning webpack/lib/ModuleWarning -> Warning, so module was skipped, maybe you have plugins or something else that remove it from stats

Please create reproducible test repo, you have a Module warning webpack/lib/ModuleWarning -> Warning, so module was skipped, maybe you have plugins or something else that remove it from stats

Okay, will do -- thank you. Is there any way to get more log info?

Okay, will do -- thank you. Is there any way to get more log info?

Go to webpack/lib/ModuleWarning and put console.log(this.name, this.warning, this.details) here https://github.com/webpack/webpack/blob/master/lib/ModuleWarning.js#L40

Go to webpack/lib/ModuleWarning and put console.log(this.name, this.warning, this.details) here https://github.com/webpack/webpack/blob/master/lib/ModuleWarning.js#L40

Thank you!
2021-01-20-07:48:38 3|admin-webpack   | ModuleWarning [Warning: Warning
2021-01-20-07:48:38 3|admin-webpack   | (45:3) Replace fill-available to stretch, because spec had been changed] undefined

I guess one of the plugins is using fill-available I will find and replace, thank you for replying so fast.

Thank you!
2021-01-20-07:48:38 3|admin-webpack   | ModuleWarning [Warning: Warning
2021-01-20-07:48:38 3|admin-webpack   | (45:3) Replace fill-available to stretch, because spec had been changed] undefined

I guess one of the plugins is using fill-available I will find and replace, thank you for replying so fast.

@gita-v Can we close? it from autoprefixer

@gita-v Can we close? it from autoprefixer

Yes, thank you!

Yes, thank you!

@sokra @alexander-akait Can webpack show more detailed output for warnings like this?
Compare, warning showed by webpack:
2021-01-20-07:34:23 3|admin-webpack | <w> [webpack.cache.PackFileCacheStrategy] Skipped not serializable cache item 'mini-css-extract-plugin /home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less|0|Compilation/modules|/home/admin/code/experimental/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].use[1]!/home/admin/code/experimental/node_modules/postcss-loader/src/index.js??ruleSet[1].rules[1].use[2]!/home/admin/code/experimental/node_modules/less-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/home/admin/code/experimental/modules/browser/navigation/private/published_doc_interactions.less': No serializer registered for Warning

And an actual warning from autoprefixer:
2021-01-20-07:48:38 3|admin-webpack   | ModuleWarning [Warning: Warning
2021-01-20-07:48:38 3|admin-webpack   | (45:3) Replace fill-available to stretch, because spec had been changed]

There is no way to figure out why the warning has appeared in the first place without console.log inside webpack/lib

@meskill You have warning in your CSS from autoprefixer, so we can't cache this module due warning, you need fix warning

@meskill You have warning in your CSS from autoprefixer, so we can't cache this module due warning, you need fix warning

I totally understand that, my question was only about webpack output - currently it strips important information which will help to fix warnings

@meskill hm, can you provide example? What is stats value? You should get full warning description

@alexander-akait Example in the initial post in this issue:
webpack shows this ...<file with warning>... : No serializer registered for Warning with no actual warning text
and after your suggestion to add console.log

Go to webpack/lib/ModuleWarning and put console.log(this.name, this.warning, this.details) here https://github.com/webpack/webpack/blob/master/lib/ModuleWarning.js#L40

The string (45:3) Replace fill-available to stretch, because spec had been changed] will be shown.
stats option is set to minimal in my webpack config

Maybe autoprefixer don't provide more information, but we can provide this and print file where warning happens. Can you provide small example? Here place to improve https://github.com/webpack-contrib/postcss-loader/blob/master/src/Warning.js

Receiving the same error @gita-codaio reported. Webpack @5.50.0, cache enabled.
I was able to narrow it down a bit and it seems that presence of "display: contents" within a class is causing it.
Once removed, the warning is gone. Hope it gives a bit of a clue.

This reply earlier in the thread helped me troubleshoot my silent CSS failure (I had one rule with an empty url that couldn't resolve): https://github.com/webpack/webpack/issues/12458#issuecomment-763713922
How can we make this a more user-friendly message to explicitly log warnings?
Are these merely getting suppressed by autoprefixer?

For anyone else facing the issue.
Webpack doesn't show any warning except the warning about serialization while caching because actual warning happens in child compilers used by mini-css-extract-plugin. And you need to specify { children: true } in webpack config to see the actual message. But it will show a lot of successful message with info about children.
Another option is to set experimentalUseImportModule flag for mini-css-extract-plugin in order to not use child compilers.

Maybe autoprefixer don't provide more information, but we can provide this and print file where warning happens. Can you provide small example? Here place to improve https://github.com/webpack-contrib/postcss-loader/blob/master/src/Warning.js

Hi Alexander, is this the solution to the issue? To build a way to display warnings, into this file?
It would be ideal to have a setting to report only warnings from child compilers, and none of the success messages (as @meskill reports). Would this same file be the place to do that? I believe this is a feature that is needed.

@robrecord Do you mean change stats output?

I am just curious if this will invalidate all Webpack caches. If not, is there a way to ignore this warning because my problematic CSS file cannot be modified in the node_modules directory of Node.js? @alexander-akait

@childrentime Please provide error/warning message

@robrecord What output in console do you have? Because this problem should be fixed, just want to verify your problem

[webpack.cache.PackFileCacheStrategy] Skipped not serializable cache item 'Compilation/modules|.../css-loader/dist/cjs.js??ruleSet[1].rules[1].use[2]!/.../postcss-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/.../resolve-url-loader/index.js!/.../sass-loader/dist/cjs.js??ruleSet[1].rules[1].use[5]!/.../sku-selector/lib/OCSkuSelector/style.module.scss': No serializer registered for Warning
while serializing webpack/lib/cache/PackFileCacheStrategy.PackContentItems -> webpack/lib/NormalModule -> Array { 2 items } -> webpack/lib/ModuleWarning -> Warning
[webpack.cache.PackFileCacheStrategy] Skipped not serializable cache item 'Compilation/modules|.../css-loader/dist/cjs.js??ruleSet[1].rules[1].use[2]!/.../postcss-loader/dist/cjs.js??ruleSet[1].rules[1].use[3]!/.../resolve-url-loader/index.js!/.../sass-loader/dist/cjs.js??ruleSet[1].rules[1].use[5]!/.../cornerstone-ui/lib/PurchaseInfo/index.module.scss': No serializer registered for Warning
while serializing webpack/lib/cache/PackFileCacheStrategy.PackContentItems -> webpack/lib/NormalModule -> Array { 3 items } -> webpack/lib/ModuleWarning -> Warning

@alexander-akait here is my warning. And I think it is because autoprefixer's warning make mini-css-extract-plugin can not  correctly serialize some css.  I tried ignoreWaining but can not remove it in my console.
I will write a GitHub repository to reproduce it when having time.

@childrentime I see, is it possible to disable this warnings, I have ideas how we can solve it

@alexander-akait https://github.com/childrentime/webpack-cache-reproduce. check out this repository, it can reproduce it.

Obviously, it's caused by this.emitWarning function by postcss-loader. https://webpack.js.org/api/loaders/#thisemitwarning, how should we fix it?
The yellow warnings are really ugly.


[DataCube API Book] Adding to chart

Hi,
Please help, I've started a new project with tvjs-xp and I've add my own datacube from server successfully. But this is a rather confusing me. I want to add a few of new array data to chart.data. But I cant find a function from datacube on datacube.js, neither in DataCube API Book.
My goal is adding a responsively new data in times which can moving based on that new data change (Like Binomo). But first, I have to find how to add or push a new data to chart.data array.
Thanks for advice.

Sorry, my fault. Obviously I can user dc.merge to add. Before, it cant  affect my chart because the new data have wrong values. So Im gonna close this issue..
Thanks before


Provide citation information for all functions/classes/modules

We need to make a better job of providing citation information for Fatiando components. The coolest thing I've seen so far is duecredit. We can annotate our code with references and the user can use duecredit to generate a full list of references (including external libraries).

#222 could use this maybe

So #293 seems to be working well. We should consider rolling this out for all the methods we have implemented.
As a general preference, do we want to use a DOI or a BibTeX fragment? Some methods may not have a DOI if they are in a thesis or similar, but to use BibTeX generally is more effort, and takes up more space.


Add definition for “condition” to website glossary.

The definition I want you to add for this word is “An expression that determines the evaluation of a control structure.”

I added it into the _data/glossary_terms.yml, not just need to upload all changes


[HUDI-5884] Support bulk_insert for insert_overwrite and insert_overwrite_table

Change Logs

Will not delete the table location if using SaveMode.Overwrite for bulk_insert, insert_overwrite
Add bulk_insert support for insert_overwrite and insert_overwrite_table
Add tests to cover new feature

Impact
This is a breaking change for users who rely on SaveMode.Overwrite with bulk_insert to drop the table, now old table data will still exist, but replaced by the new written data.
Risk level (write none, low medium or high below)
low
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@hudi-bot run azure

Hey @alexeykudinkin @nsivabalan, could you please take a look?

Hi, @stream2000 Could you also please review this, this fixes the pr https://github.com/apache/hudi/pull/8015

Gentle ping @alexeykudinkin @xushiyan @danny0405 @yihua

I am yet to review fully, but have taken one pass. Can you break it down into two PRs - a) don't delete the table location if using SaveMode.Overwrite for bulk_insert, insert_overwrite, b) add support for bulk_insert for insert_overwrite and insert_overwrite_table.

Yea, sure, will do so

Also, I want to understand the use case when we need this. If you can elaborate a bit more on why we need this, that would be great.

Currently, we want to migrate all existing hive tables to HUDI table, given many hive tables

usually perform insert_overwrite operation to overwrite the partition
written by batch jobs, could contains TB level data one day
doesn't need to perform the tag, drop duplicates

bulk_insert mode fit such scenario well, we can use bulk_insert mode to boost the write performance and make users easier to migrate existing hive table to hudi table.

Hi @codope @stream2000  Gentle ping... Could you please take a look again?

@hudi-bot run azure

Hey, @codope, all comments are resolved, could you pls review it again?

Looks good to me. @yihua @nsivabalan If you can take one pass, that would be great.

@yihua Gentle ping... could you pls help to review it?

@yihua Gentle ping... could you pls help to review it?

Sorry for the delay.  I will review this PR this week.

@boneanxs meanwhile, could you rebase the PR on the latest master?

can we just keep the bulk insert part, while extract the behavior change (i.e. not delete the table location if using SaveMode.Overwrite for bulk_insert, insert_overwrite) to a separate PR

@codope removed the breaking changes

Thanks @boneanxs for extracting out the breaking change. Left one minor comment for the config. Can you also squash all commits to one?

@codope Thanks for reviewing, address the comment and squashed all commits.


NVIDIA DLDSR breaks everything, no keys are pressed, resolution get overriden

Current Behavior
When I press scan, the game res is set to 1024×768 or something, and nothing happens, except black flash for the screenshots I guess
Expected Behavior
The scanner continues to scan
Reproducing a Behavior
Have DLDSR 1.78x and 2.25x enabled (nvidia 3xxx or 4xxx gpu) on a 1080p 16:9 monitor
Set Genshin Impact to 1920x1080 windowed (1620p for dldsr 2x25 is detected as native and is the only one available in fullscreen)
Device OS
Windows 11
Genshin Impact Version
4.3?
Inventory Kamera Version
1.3.12
Screen resolution, screen mode, and UI scale
1920x1080, windowed, 100% scale in windows, one monitor enabled
Additional notes and remarks

I have another 1080p monitor, turned off
I have 2 of these virtual device drivers (1x 2234p, 1x 2234p hdr), but the displays are "disconnected" in display settings
https://github.com/itsmikethetech/Virtual-Display-Driver

Evidence
I log off of windows to stop it, and GenshinData folder is empty, even though it seemed to have (tried) to take screenshots
Preflight Checklist

[X] I have checked for similar issues in the issue page, and I have not found any similar to mine.
[X] I am using the latest version of the scanner.
[X] I tried setting the scanning delay to maximum, and it still doesn't work.
[ ] I have attached the video recording to the bug report.
[ ] I have attached the error log to the bug report.
[X] I am available to later explains the issue.
[X] I have disabled all screen filtering software or plugins (i.e. HDR, Image Sharpening) while scanning.
[X] I use default in-game keybindings or have configured keybindings for the scanner.

I can't change the resolution in-game, it doesn't apply
I disabled dldsr, sign off of windows, relogin, and now genshin looks like this...

And it crash during loading

Actually it happens in any case, even with dldsr off in nvcp...

This does not seem related to Inventory Kamera so I am going to close this issue. Custom launch options are user-dependent and will not be built into Kamera as edge cases.


log files are on the top level - should be in a subdir

attestation$ gradle build
attestation$ ls Log*
Log4j-charsets.properties  Log4j-config.xsd  Log4j-events.dtd
Log4j-events.xsd  Log4j-levels.xsd

Hi guys,
Could you please share the trick over how to reproduce this issue? "gradle test" could not reproduce the logs listed above.

verified unreproducible. could be fixed by someone. closing.


fix(ffe-core): Visual indication on left menu

Solves  https://github.com/SpareBank1/designsystem/issues/326
Not sure if ffe-core is correct package but did not find anything closer

Coverage remained the same at 80.583% when pulling f61ebc32fa8c939910813ab805f6dcc2e9d5c1aa on manglande-visuell-sporing-i-venstremeny into 2f86fd29b96c538ca6d7b208f49e1a8c093c2073 on develop.

Coverage remained the same at 80.583% when pulling f61ebc32fa8c939910813ab805f6dcc2e9d5c1aa on manglande-visuell-sporing-i-venstremeny into 2f86fd29b96c538ca6d7b208f49e1a8c093c2073 on develop.


[Bug] Error while configuring integration on 2021.4

Hi Tomaae, I ask you for help because I get this error when I try to integrate OMV. In your opinion, how could I solve? Thanks so much.

I see, its something HA changed in last release. I will have to look into changing setup procedure.

Thank you very much for everything and for the work you do ... We will wait for the update :-)

I don't know, where you are living, tomaae, but you are welcome in Amsterdam for some coffe and testing ;-)

Hi Tomaae, I have the "same" problem!
Version core-2021.4.3
Version supervisor-2021.03.9
No 'version' key in the manifest file for custom integration 'openmediavault'. As of Home Assistant 2021.6, this integration will no longer be loaded. Please report this to the maintainer of 'openmediavault

RuntimeError: I/O must be done in the executor; Use await hass.async_add_executor_job() at custom_components/openmediavault/omv_api.py, line 128: response = self.connection.post(
2021-04-12 17:56:15 WARNING (MainThread) [homeassistant.util.async] Detected I/O inside the event loop. This is causing stability issues. Please report issue to the custom component author for openmediavault doing I/O at custom_components/openmediavault/omv_api.py, line 128: response = self._connection.post(
2021-04-12 17:56:15 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 422, in _handle_request
resp = await self._request_handler(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 499, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 56, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 18, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 74, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 129, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 131, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 155, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 60, in wrapper
result = await method(view, request, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 107, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 156, in async_configure
result = await self._async_handle_step(flow, cur_step["step_id"], user_input)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 214, in _async_handle_step
result: dict = await getattr(flow, method)(user_input)
File "/config/custom_components/openmediavault/config_flow.py", line 78, in async_step_user
if not api.connect():
File "/config/custom_components/openmediavault/omv_api.py", line 128, in connect
response = self._connection.post(
File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 590, in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 542, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 655, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.8/site-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 699, in urlopen
httplib_response = self._make_request(
File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 394, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 234, in request
super(HTTPConnection, self).request(method, url, body=body, headers=headers)
File "/usr/local/lib/python3.8/http/client.py", line 1255, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.8/http/client.py", line 1266, in send_request
self.putrequest(method, url, **skips)
File "/usr/local/lib/python3.8/site-packages/urllib3/connection.py", line 214, in putrequest
return HTTPConnection.putrequest(self, method, url, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/util/async.py", line 150, in protected_loop_func
check_loop()
File "/usr/src/homeassistant/homeassistant/util/async.py", line 139, in check_loop
raise RuntimeError(
RuntimeError: I/O must be done in the executor; Use await hass.async_add_executor_job() at custom_components/openmediavault/omv_api.py, line 128: response = self._connection.post

dont worry, I know what the issue is

sorry

no worries.
fix is already released.

Thank you very much for the quick help.
Works perfectly again!

Thanks Tomaae now it works perfectly.  ;-)

A question Tomaae, I saw that the integration gives some disconnections (I am attaching the LOG) in your opinion how can it be solved?

I cannot see that screenshot, it didnt upload right

Sorry, here's the screenshot. Practically it always repeats the same mistake. logs out and then comes back online.
Hope you can help me. Thanks so much...

that part above that you cut off may be the problem. check your SSL settings are correct

Hi Tomaae, it's definitely my ssl configuration problem. Although I've only noticed it now.
I use duckdns and can connect remotely via https. What do you think I can change to solve? If you need more screenshots with data, I'm at your disposal (I have attached that log that was cut).  It seems he wants an attribute that he thinks is wrong, but I don't understand.
Thank you and good evening.

try unchecking verify ssl when setting up the integration. that could help. or dont use ssl when connecting to omv if its in your network.

I tried but nothing to do. i checked the ssl and it is correct. I unchecked the checkbox when configuring the integration, but to no avail. I can't understand, may it be that I need to make some changes on OMV? I have no certificates set up and I am running home assistant in docker on OMV. Do you have any advice? It's a shame because the integration works perfectly but it gives me constant disconnections and fills my register with HA.

it actually works? I though it does not work at all based on your screenshot.
If you can provide me first few minutes of debug log after HA restart, we cam find something out.

Okay, later I do everything and I update you on a new report. Thank you...


Is it possible to unlock on a windows Hyper-V host?

I am hoping there might be some way to unlock this for use with Hyper-V.
Is that possible using something like WSL or do I need to unlock on linux host and then transfer card to my hyper-v host?

No, this simply will not work for Hyper-V. It is linux only, and essentially none of the code has a Windows/Hyper-V equivalent.

I think it is very useful to port this hack on windows


add support for multiple rmb relays in the rmb sdk

Is your feature request related to a problem? Please describe
rmb-peer supports connecting to multiple relays for redundancy. This feature allows the rmb-peer to continue operating if one of the relays is facing technical problems.
It also allows messages to be balanced between multiple relays.
Describe the solution you'd like
Support for multiple relays need to also be implemented in the go client

WIP

Investigating twin updates on different relays when multiple relays are supported

verified:
used my mnemonic which has only one relay configured to make an rmb call using the rmb-sdk peer and added two relays with the option WithRelay()

and my twin relays is updated, the two relays hostnames separated by _


Don't attempt to unlock if locks aren't in use

If locks are disabled, this is unnecessary work.

Make sense. Thanks!


Fixed travis evaluation of the acnv workflow

Closes #680
Travis.yml wasn't properly evaluating the tests of the acnv workflows, as it did not fail if one of the workflows fails.
Also I disabled QC for Travis tests since the CreatePanelOfNormals threw out all samples on the test data.

@LeeTL1220 Could you please take a look?

@LeeTL1220 Oooops, I need to fix the stuff with HetCoverage first

@LeeTL1220 Finally done! I ended up setting stringency and readDepthThreshold low for WGS test, but kept default values for the WES test, as it was giving me a different type of error(I will send a detailed email). Could you please review it when you get a chance? Thanks!

@asmirnov239 Minor comment.  Please address then feel free to merge.


Please add untranslated en source strings to the hu file.

Please add untranslated en source strings to the hu file.
For example, Contact, Mails unread, Junk mails, Junk score of, ThirdStats makes no claim to the correctness of the data displayed., In case of possible problems, please create a bug report.

We translate the file using a web browser.
Thank you

Thank you for the detailed instructions.
Should be at 100% now.
Thank you once again.


Merge with textextensions

Added extenstions from the bevry/textextensions package
Added .gitignore

Note:
I think .gitkeep could go both ways, since it's meant to always just be an empty file. I can take it or leave it

Considering the bevry package has been around a few years prior to this one, I don't see why this one was created. I put forward the notion of closing this package and making it a redirect to the bevry one.


Fix travis ci rebuilds

coveralls.io returns an error when rebuilding, as the build information
has not changed (PR, id, etc. is the same).
Fix this by appending a random number to the travis job id. Fixes #238.

Will submit new PR that passes tests


Fix Traffic Monitor CRConfig for empty string numbers

Changes the CRConfig struct to not use ,string, which fails to parse
when the value is "".
This is a critical issue which causes the TM to fail to start, or
while running, fail to get new CRConfigs, if a value is "", for
example, if a delivery service has its TTL empty.
Fixes #1116

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-whatchanged/48/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/178/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/139/


Change 'master' branch name to 'main'

While I don't personally see a problem with the master branch name, I am well aware that others feel it is offensive and want to avoid it for this reason. I've tried to summarize some of the details around this in this ticket, hopefully in a reasonably neutral and balanced way (even though neutrality is much harder in practice than in theory...).
Pros

It can make the project "feel more inclusive" to people who are offended by the master terminology.
It avoids language which some feel is offensive.
It doesn't cost much.

Cons

It can be considered a solution looking for a problem.
It doesn't in any way help solve problems for people who are really affected by modern slavery (i.e. human trafficing).
It tends to put the focus on minor things (like the name of the mainline branch for a software project) instead of making real changes in people's lives (like giving a small amount of money every month to a charity).

What are other FOSS projects doing?

Languages & groups using main

.NET - all pinned projects except for one (installer) have switched to main

The dotnet organization has decided to rename all default branches to main: https://github.com/dotnet/announcements/issues/172

F#: uses main
Node.js: ~uses master~

Changed to main in June 2022: https://github.com/nodejs/node/issues/33864#issuecomment-1139645911

Rakudo (i.e. "Perl 6"): ~uses master~

Seem to have changed at around December 2022: https://github.com/rakudo/rakudo/commit/c3e0eb7c18164558361baddf77af83893012be38

Languages & groups using master

Python: changed from master to main  around May 2021: https://github.com/python/cpython/pull/25860
Ruby: uses master
Java (OpenJDK): uses master

Javascript frameworks

Ember.js: ~uses master~

Seems to have been changed sometime around April 2023: https://github.com/emberjs/ember.js/pull/20436

React: changed from master to main in June 2021: https://github.com/facebook/react/issues/21767
Angular: ~uses master~

Changed to main sometime before May 2022: https://github.com/angular/angular/pull/45856

What are the projects with the most stars on GitHub doing?
Based on data from https://github.com/EvanLi/Github-Ranking#most-stars

3 repos use main
6 repos use master
1 repo uses something else

Noteworthy quotes
somecoder wrote as a comment to Scott Hanselman's blog post (emphasis is mine)

sorry guys, I know you have good intentions here, but I believe you are actually doing damage.
I noticed a trend recently that in many cases, our black fellows don't take a situation offensive - the white liberals do it in their name - at least that is what they think they do. For sure, that have not been asked to do so. So they just assume they are acting in other persons best interest.
But it actually does something opposite to the intention.  It implies that you cannot be relaxed in their presence, but must constantly pay attention to your vocabulary.
I mean, think about it. Is this really closing the racial divide or expanding it? Does anyone particularly enjoy standing in the middle of mine field? Because this is what you are effectively doing. You are tossing mines around race, so I am no longer able to enjoy the company, but constantly fear that something is about to explode.

Further reading

Software Freedom Conservancy: Regarding Git and Branch Naming
GitHub: Renaming the default branch from master
Felipe Contreras: Why renaming Git’s master branch is a terrible idea
Scott Hanselman: Easily rename your Git default branch from master to main

My personal stance on this: I have a greater understanding that master/slave is considered offensive than the word master in itself. "Master" is a much broader word than the specific master/slave context.
For now, I think I'll end up with considering this a "wontfix" issue. If a number of other programming languages (and git projects at large) follow suite with the .NET folks and we end up being in minority here, I think I'll be open to reconsidering this.
If you personally are offended by this (the master branch name wording), I'm also particularly interested in hearing from you. Your opinion is valuable to me! :+1: Especially if you have ancestors who suffered from slavery, feel free to reach out to me (in private if you so prefer). You can find my contact details in my GitHub profile.

(Updated the issue description in https://github.com/perlang-org/perlang/issues/171#issue-835222488 with the current state of the other repos mentioned)


Add a Unique place module

You need to think about how to correctly build the API so that the url looks “beautiful” (Search Engine Friendly).
A unique place must have a unique url within the user

Finally I was free for this project. Today I built this module


Optionally swallow no PR found errors

Background
Right now, all commits before a PR is created "fail" because No pull_request found for commit. This makes it appear like there are more problems than actually exist in the repo:

AC

an optional input parameter to swallow these errors

+1 Having the same issue


Spatial Audio Demo Not Working

I have tried the spatial audio demo, its not working?
I have joined from two different systems, and using headphones on both.
Did I miss something here?
I can't hear anyone in the channel.
Also, related question, Is spatial audio works with voice only version or you need full version of the sdk?
I'm using CPP sample

I can hear my voice on a normal audio call.

That’s what I did in the first place.
I stored the player unique ID, and updated the position whenever they moved(for both self and remote player).
it didn’t work, so I tried the demo. It wasn’t working either. I tried playing with settings the range, but that had no effect on the output.

Agora-Unreal-SDK-CPP-Example/Source/AgoraExample/SpatialAudioWidget.cpp
my develop branch fix this bug.

Agora-Unreal-SDK-CPP-Example/Source/AgoraExample/SpatialAudioWidget.cpp
my develop branch fix this bug.

Thanks for the reply. Which branch is your develop branch?

Agora-Unreal-SDK-CPP-Example/Source/AgoraExample/SpatialAudioWidget.cpp
my develop branch fix this bug.

Thanks for the reply. Which branch is your develop branch?

Looks like there is only one other branch. I’ll check that out. Do I need to update the plugin as well? Like take the plugin source from develop branch? @oneSitDown

You just copy the code here and go to the master branch

You just copy the code here and go to the master branch

Okay, Ill copy the code from dev branch for Agora-Unreal-SDK-CPP-Example/Source/AgoraExample/SpatialAudioWidget.cpp.
Also, do I need Agora_Unreal_RTC_CPP_SDK_4.0.0-alpha.1_FULL.zip for spatial audio or Agora_Unreal_RTC_CPP_SDK_4.0.0-alpha.1_VOICE.zip is enough?
@oneSitDown

use VOICE enough

Hi, it started working, but the voice is very law. So I tried playing with the range value, It works for values less than 1000 (which is 10Meter in unreal). Is there any upper limit in range?
Thanks for the quick replies.

Hi, It works perfectly now!
I did set the values for range and unit to make it work.
auto ret = LocalSpatialAudioEngine->setAudioRecvRange(1000); //10 Meters
auto ret = LocalSpatialAudioEngine->setDistanceUnit(0.05);
Thanks for the support @oneSitDown.
I'm closing this ticket.


Echo Test

I figured out the echo test problems I was having.
In the example notes at the top of the code it indicates to launch with -1 on the listener and 0 for the sender.
When I did that nothing happened. Reading through the code as the crucial line just before the sending call the following was seen.
if (id >= 2)
So I tried instead of 0 on the sender a value of 2 or higher and funnily enough it started to not only send "pings"
[12:18:48 +08:00] [I] Sent: Ping SendQueueBytes=232��
But on the receiving rpi major activity and packets received.
[12:18:48 +08:00] [I] Got bytes: 148 3 0 0 5 6 7 8 9 10 0 0 0 0 0 0 0 0 0 0 0 0  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0  0 0 0 0 0 0 0 0 0 0 0 0 0

Thanks updated the comments


CHYT system.query_log table is highly unparsable with QT

When selecting from the system.query_log table via CHYT + QT, you get the following conversion error:
Query:
    SELECT *
    FROM system.query_log
    LIMIT 50;

Error:
    Conversion of ClickHouse type Enum8('QueryStart' = 1, 'QueryFinish' = 2, 'ExceptionBeforeStart' = 3, 'ExceptionWhileProcessing' = 4) to YT type system is not supported[1]

Some other columns are also not convertible, such as LowCardinality(String):
Query:
    SELECT query_kind
    FROM system.query_log
    LIMIT 50;

Error:
    Conversion of ClickHouse type LowCardinality(String) to YT type system is not supported[1]

Let's support all types from system.query_log in QT!

Fixed in faf468ec522aa769d03633b0ce19677ce3512559


Fixed 'TODO' in parser re: Integer bounds

I changed ValueInt Int32 to ValueInt Integer and then handled bounds checking in the parser.
The problem with using Int32 is that floatingOrInteger doesn't behave well in conjunction with scientific when constrained to Int32 -- we get a nonsense overflow number when the number parsed by scientific is out of the Int32 range.

The bounds requirement is from <IP_ADDRESS> of the Spec.
I think we can just do a typesafe cast using Data.Typeable to convert the Integer to an Int32.  I'll update the PR.

So cast doesn't work (which should've been obvious to me) as it would have to know how to check  bounds -- thus, it'll always return Nothing.  Instead can just use fromIntegral after performing the bounds check.
Updated and rebased.

Something got messed up in the rebase.  Closing and resubmitting.


Add log when VRF-evaluation slot disagrees from slot at actual time of proposal.

There is currently a bug which occurs when the proposal takes place slightly after the scheduled time if it's long enough after that it's a slot later than expected.
This PR attaches the "scheduled slot" to the proposal data and uses that, only using the actual time to check for consistency and logging a warning if the actual time falls in the next slot.

LGTM


[HELP] Can't Deploy When updated to the latest version

When updated to the latest commit, and using the deploy command below:

it returned errors as below.

Is it possible that   has conflict with   ?

dropped support for as a fix for a recent rce vulnerability in package ``

Thanks. That will handle the problem.
P.S. In that package, is it possible to use   function instead of   on line 4, the main file(which would certainly speed up the process)?

oh this is funny and i like it。

Thanks. That will handle the problem.
P.S. In that package, is it possible to use   function instead of   on line 4, the main file(which would certainly speed up the process)?

Yes you can, although instead I would recommend the following:

This is much better as it increases readability of your code without compromising effectiveness.


Set upper bounds in our build-depends cabal fields

We decided to use PVP to version our packages. That strongly implies/requires that we are specifying upper bounds in our cabal files.
This task is to add upper bounds to all of our cabal files.
For this bootstrap, we should just use the current MAJOR(.MAJOR).MINOR.* bounds (or cabal's <=^ caret operator) for whatever MAJOR and MINOR the cabal solver currently chooses for our dependencies.

The draft tool on PR #4208 could help assure we use the same bounds in every .cabal file (at least every .cabal file inside of the same package bundle).


Add user and token for CI

What does this PR do?
It adds a user and the associated token to tests Optimum on the Hub.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


⚠ Bofrost.de has degraded performance

In 3ec42c0, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1150 ms

Resolved: Bofrost.de performance has improved in aeb73af.


freerdp Multiple window taskbar preview error

There are two Windows and partial overlap at win10 client
1.Taskbar preview window

2.Overlaps show errors

nice pictures, just no idea what you´re doing ;)
could you add the requested information required for an issue? closing otherwise.

I think this is a bug
version freerdp-2.0.0-rc4 release
remoteapp
repeat steps, Very easy to reproduce
1.open multiple windows
2.if two windows overlap
3.click the taskbar window preview, window redraw error
I guess it's a gdi caching mechanism,the overwritten bitmap is truncated

case WM_PAINT:
{
if (!wfc)
return 0;
		hDC = BeginPaint(hWnd, &ps);
		x = ps.rcPaint.left;
		y = ps.rcPaint.top;
		width = ps.rcPaint.right - ps.rcPaint.left + 1;
		height = ps.rcPaint.bottom - ps.rcPaint.top + 1;
		BitBlt(hDC, x, y, width, height, wfc->primary->hdc, railWindow->x + x,
		       railWindow->y + y, SRCCOPY);
		EndPaint(hWnd, &ps);
	}

wfc->primary->hdc save to bitmap, it's error

nice pictures, just no idea what you´re doing ;)
could you add the requested information required for an issue? closing otherwise.

case WM_PAINT:
{
if (!wfc)
return 0;
		hDC = BeginPaint(hWnd, &ps);
		x = ps.rcPaint.left;
		y = ps.rcPaint.top;
		width = ps.rcPaint.right - ps.rcPaint.left + 1;
		height = ps.rcPaint.bottom - ps.rcPaint.top + 1;
		BitBlt(hDC, x, y, width, height, wfc->primary->hdc, railWindow->x + x,
		       railWindow->y + y, SRCCOPY);
		EndPaint(hWnd, &ps);
	}

wfc->primary->hdc save to bitmap, it's error

nice pictures, just no idea what you´re doing ;)
could you add the requested information required for an issue? closing otherwise.

All window draws are in one cache,If there is overlap, the preview will not work

@wang332127858 ok, now I got your issue. Yes, rail needs some overhaul, but it will not make it in 2.0.


Got crash issue from fabric.

Platform: ios
Issue #: 1061
Issue ID: 5ba553daf8b88c2963c7df84
Session ID: 68ceead1616b476fb390e1b15bdce378_DNE_0_v2
Date: 2018-09-28T14:44:00Z
OS Version: 11.4.1 (15G77)
Device: iPhone 6s
RAM Free: 4.7%
Disk Free: 41.1%
Crashed: NSOperationQueue 0x1c1024040 (QOS: UNSPECIFIED)
0  libsystem_platform.dylib       0x18159aa80 _platform_memmove + 176
1  CoreFoundation                 0x18184ac3c -[__NSArrayM insertObject:atIndex:] + 356
2  CoreFoundation                 0x18184ac3c -[_NSArrayM insertObject:atIndex:] + 356
3  NHNetworkTime                  0x104463d54 -[NHNetworkClock createAssociations] + 1340
4  CoreFoundation                 0x181986580 invoking + 144
5  CoreFoundation                 0x181865748 -[NSInvocation invoke] + 284
6  Foundation                     0x1823a7308 -[NSInvocationOperation main] + 40
7  Foundation                     0x1822e7cac -[__NSOperationInternal _start:] + 848
8  Foundation                     0x1823a876c __NSOQSchedule_f + 404
9  libdispatch.dylib              0x181270a60 _dispatch_client_callout + 16
10 libdispatch.dylib              0x181278e94 _dispatch_continuation_pop$VARIANT$mp + 424
11 libdispatch.dylib              0x1812777cc _dispatch_async_redirect_invoke$VARIANT$mp + 604
12 libdispatch.dylib              0x18127dcac _dispatch_root_queue_drain + 588
13 libdispatch.dylib              0x18127d9fc _dispatch_worker_thread3 + 120
14 libsystem_pthread.dylib        0x1815a3fac _pthread_wqthread + 1176
15 libsystem_pthread.dylib        0x1815a3b08 start_wqthread + 4

Could you please provide more detail for me? For example, how you use this lib in your project.

I use cocoapod to configure this lib in our project. From the Podfile.lock file I found that NHNetworkTime version is 1.7. We found several crash in this lib but frequency is not so high (10-20).


Bug in round-robin ranking with unplayed matches

Here, the ranking should be:

Also, the played matches are wrong.


Phone number highlight incorrect if text contains the string 'phone'

I have noticed a issue with the phone number detection not working correctly when the labels text contains the string 'phone' in it. Here is a screenshot.

If you look at the second and third cell you can see what I mean. Some of the text has been highlighted from the word 'Phone'. Had a quick look at the source and this project uses a NSDataDetector to pull out the links. So maybe its a bug with this apple api. (Also seems to be only happening since iOS 7) and couldn't find anything about this in the NSDataDetector docs.

Can you share some of your code? Generally you'll want to make sure you are assigning to the text property after most other properties have been set, particularly your data detector type.

@jasonblood If the word "phone" were involved here, I would expect to see the same issue in your fourth cell, right? I think it's more likely there is a table cell reuse problem.

hi @jhersh sorry about the slow reply (didn't get a notification about a response). I will try and get a sample project with this happening when I get some time.
But this is roughly how the label is set up in the cell ```
    _messageLabel = [[TTTAttributedLabel alloc] initWithFrame:CGRectZero];
    _messageLabel.textColor = CONTENT_TEXTCOLOR_LIGHT;
    _messageLabel.backgroundColor = [UIColor clearColor];
    _messageLabel.numberOfLines = 0;
    _messageLabel.enabledTextCheckingTypes = NSTextCheckingTypeLink | NSTextCheckingTypePhoneNumber; ```

And then the text is set on the label using the text property. So I hooked up the debugger and set a breakpoint here https://github.com/TTTAttributedLabel/TTTAttributedLabel/blob/master/TTTAttributedLabel/TTTAttributedLabel.m#L1125 and the data detector seems to parse the phone part out sometimes. So I guess this is an Apple bug


Update artifact if the name is the same

Hi, is it possible to update an artifact if we add an artifact with the same name several times?
I am currently using the mongodb observer and when I add the same artifact twice it is saved twice.
I would like to store intermediate results, but have only the final versions, not the versions in between.
Thanks, cheers!

+1

If you use NeptuneObserver the artifact file with the same name gets overwritten by default.
Check out the readme.md or neptune-contrib docs if interested.

Also wondering if there is a way to overwrite observed data with the mongodb observer rather than having multiple versions.
I tried looking into Neptune, it looks like it is only available as an external service, which is a big no-no for me at the moment (HIPAA rules).
I am interested in storing checkpointing data, but only need the last set, and not everything along the way (a lot of data that grows very quickly), and would like to have it attached to the data (the only reason to migrate to sacred in an attempt to avoid building my own database setup).
It looks like the file observer overwrite the data, but it's very hard to browse the outputs (I need to go one by one to find the correct one).
Thanks

I started looking into the code to see what it would take to change things.
Looks like the function of interest is
sacred/observers/mongo.py:artifact_event(266)
It should be easy enough to check self.run_entry["artifacts"] to see if an entry for the said file name exists and replace it, it looks like the question is the use of
self.fs.put (where self.fs is an instance of gridfs.GridFS)
which I'm guessing generates a new file each time, so it won't help to delete the entry without deleting the file first

I think I found a solution (doesn't give a choice right now, just replaces files with the same name - matches ).
No new files show up, the DB keeps growing, but very slowly, and from what I gathered, it seems to be related to the way mongodb works (doesn't shrink in size by default) rather than extra files (unrelated - deleting experiments through omniboard doesn't free up space either).
diff --git a/sacred/observers/mongo.py b/sacred/observers/mongo.py
index c4dc73d..b95ba5c 100644
--- a/sacred/observers/mongo.py
+++ b/sacred/observers/mongo.py
@@ -298,6 +298,13 @@ class MongoObserver(RunObserver):
         self.save()

     def artifact_event(self, name, filename, metadata=None, content_type=None):
+        # Check first if a file with the same name is already in the database
+        # Delete it and remove it from the artifacts
+        for i, e in enumerate(self.run_entry["artifacts"]):
+            if name == e['name']:
+                self.fs.delete(e['file_id'])
+                self.run_entry["artifacts"].pop(i)
+
         with open(filename, "rb") as f:
             run_id = self.run_entry["_id"]
             db_filename = "artifact://{}/{}/{}".format(self.runs.name, run_id, name)

@laughingrice
I see you found a solution, that is good.
Just wanted to say that regarding:

I tried looking into Neptune, it looks like it is only available as an external service, which is a big no-no for me at the moment (HIPAA rules).

You can have Neptune deployed on-premise to be compliant with those.
We just send you a VM + instructions to test it out (and instructions for scalable deployment on a Kubernetes Cluster if you want after).

@jakubczakon

You can have Neptune deployed on-premise to be compliant with those.
We just send you a VM + instructions to test it out (and instructions for scalable deployment on a Kubernetes Cluster if you want after).

Thank you.
I did not see a message through github. I did get an email from Kamil at Neptune about setting up an academic account, but it didn't mention on-premise deployment.

We have recently found this feature to be quite useful, and I would love to see this feature upstreamed -- see PR #925 . Sorry for resurrecting an old issue. Happy to update the PR to address any issues/requests.


Add a feature spec for building cluster in Azure

Backport of #584 .

 Add a feature spec for building cluster in Azure

@bear454 : We need a bsc number to port fixes to this branch. I would say, if this goes along with a bug fix, then I am fine to merge this after we have release 3.0, so this is shipped as a maintenance updates. Right now we are only merging P1 fixes, but we will open the gates again in short.
Have in mind, a bug fix could also be "enabling integration with Azure cluster".

@jordimassaguerpla I'm fine with waiting a while to merge this in... there's no rush on it.

I guess this is good to be merged since the release is out.

Oh, there's no bsc number. =/

vitoravelino commented 5 days ago

Oh, there's no bsc number. =/

This doesn't solve a "bug" - there is currently no known defect; just an effort to provide proper testing framework consistently across all environments; e.g. this is an enhancement but is not user-facing.

This doesn't solve a "bug" - there is currently no known defect; just an effort to provide proper testing framework consistently across all environments; e.g. this is an enhancement but is not user-facing.

I know, you already have my +1. I guess using enhancement#azure-spec would solve the backport rule. Just guessing...

bear454 dismissed vitoravelino’s stale review

Well, github dismissed the review when I changed the commit message... I didn't do anything with reviews ;-)

@MaximilianMeister : It is ok to merge this one. Our package excludes files under spec directory and this can be useful when looking for regressions for new commits into 3.0 branch,


[BUG] process definition does not show on UI (工作流在页面不显示问题)

Problem Description
After upgrading from 1.1.0 to 1.2.0, individual project workflows cannot be queried on the page, but tasks are still executed normally.

I solved the problem this way
I found in the t_ds_project table that there is a project with the same name in the exception project, and both projects have the same user_id, but the flag of one project is 0 and the other is 1. This should be the flag used to delete in the previous version. But both items of version 1.2.0 are displayed on the page. Later, I deleted the items that had been deleted before, and then returned to normal.

问题描述
从1.1.0升级到1.2.0后，个别项目工作流在页面查询不到，但是任务依然正常执行。
解决过程
我在t_ds_project发现异常项目存在同名项目，并且这两个项目都有同一个user_id，但是一个项目的flag是0，另一个是1，这应该是之前版本的用来删除的标志。但是1.2.0版本这两个项目都在页面上显示了。后来我又删除了一遍之前已经删除过的项目，然后就恢复正常了。

please use english to describle your idea

Problem Description
After upgrading from 1.1.0 to 1.2.0, individual project workflows cannot be queried on the page, but tasks are still executed normally.

I solved the problem this way
I found in the t_ds_project table that there is a project with the same name in the exception project, and both projects have the same user_id, but the flag of one project is 0 and the other is 1. This should be the flag used to delete in the previous version. But both items of version 1.2.0 are displayed on the page. Later, I deleted the items that had been deleted before, and then returned to normal.

I have same problem.

Close this issue since no updates for long time


Generalize Configuration class

The Configuration class contains quite a bit of code specific to Mixer and Renderer. It can be generalized to support loading of arbitrary configuration data.
Additionally, the Configuration class can serve as a bridge between the XML serialized format, and the in memory configuration data, which is largely key/value storage with support for various data types, now implemented as Dictionary. It is one of the few places in NAS2D that is heavily dependent on XML code, the other being Sprite, and can be used as a basis for the Sprite, along with downstream uses in OPHD.
One of the end goals of this work, is to decouple the library and downstream project code from the XML code. That will make it easier to upgrade or replace the TinyXML1 dependency. In particular, it can be made an external dependency installed through vcpkg, it can be upgraded to TinyXML2, or it can even possibly be swapped out for another serialization format such as JSON.
Reference: #211, #239

A lot of work has already been put into this effort, though was not previously tracked using a specific issue. By opening this issue, that work from various PRs can be collected into a single place, along with new work to complete that goal.

Mostly thinking out loud here.
Looking at the Configuration class, there are sections of methods relating to video and audio that should be removed. Each method comes in get/set pairs.
Video methods to remove:
	// Video Options
	int graphicsWidth() const;
	int graphicsHeight() const;
	int graphicsColorDepth() const;
	bool fullscreen() const;
	bool vsync() const;

	void graphicsWidth(int width);
	void graphicsHeight(int height);
	void graphicsColorDepth(int bpp);
	void fullscreen(bool fullscreen);
	void vsync(bool vsync);

Audio methods to remove:
	// Audio Options
	int audioMixRate() const;
	int audioStereoChannels() const;
	int audioSfxVolume() const;
	int audioMusicVolume() const;
	int audioBufferSize() const;
	std::string mixer() const;

	void audioMixRate(int mixrate);
	void audioStereoChannels(int channels);
	void audioSfxVolume(int volume);
	void audioMusicVolume(int volume);
	void audioBufferSize(int size);
	void mixer(const std::string& mixer);

Similarly the ability to set defaults is currently too specific to video and audio settings, and so may be removed:
	void setDefaultValues();

Related to the above are the private methods to parse those specific options, which will need to be removed:
	void parseGraphics(const Dictionary& dictionary);
	void parseAudio(const Dictionary& dictionary);

Implementation details will need to change. Currently the Configuration implementation contains many constants for the video and audio settings. In particular, it contains allowed options, allowed values, default values, as well as code to detect out of range values and replace them with defaults. Particular settings needed by various components, as well as their allowed values, are best determined by the components themselves, and so this code should be pushed out to those components.
For the RendererOpenGL class, it should be responsible for allowed options (screenwidth, screenheight, bitdepth, fullscreen, vsync), allowed values (minimum size 800x600, maximum size limited by graphics hardware), default values (1080p resolution), and mapping of out of range values to defaults (size of 640x480 -> 800x600 or maybe 1080p).
Similarly the MixerSDL class should be responsible for allowed options (mixrate, channels, sfxvolume, musicvolume, bufferlength), allowed values (audio quality 11025, 22050, 44100), default values (medium quality 22050), and mapping of out of range values to defaults (audio quality 100 -> 22050).

One slightly unfortunately aspect of the above design, is that configuration setting names found in configuration files become somewhat dictated by the objects that need initialization settings (Renderer and Mixer subclasses). That may not be appropriate if the configuration file is already of a pre-determined format which is not compatible with the default configuration setting names or format. Perhaps a developer is using a custom binary settings file, and needs to initialize Renderer or Mixer objects using their custom format.
One way to keep coupling loose is to use Options structs that can be passed to their constructors, rather than passing Configuration related objects directly. That way if a developer has custom configuration data, they can provide their own mapping to an Options struct, and use that to initialize a Renderer or Mixer object. As a convenience, a method can be provided that takes Configuration data and using default configuration setting names maps settings to the class specific Options struct. That provides a default way for objects to be initialized with very little code, while also not locking in developers to a specific configuration data format. Such convenience conversion methods should be packaged with the component being initialized, rather than as part of the Configuration class.
Effectively these class specific Options parsing methods will replace the private methods parseGraphics, and parseAudio being remove above.

Tied to the parsing of class specific Options structs, is handling of out of range values. They may result in exceptions raised by constructors, or it might be handled by mapping out of range values to default values. If out of range values are mapped to default values, one way might be to convert an Options struct to a new modified Options struct. That way such checking and re-mapping can be done for any data source, not just data coming from a Configuration object.

One area that needs further refinement, is how setting changes can be saved. That might involve reading back into a class specific Options struct, and then either saving it a custom way, or using a convenience method to write a class specific Options struct to a Configuration data store. Getting data back into an Options struct may require a custom method for each Renderer or Mixer. As the type of Options struct being returned is class specific, this method could not possibly be made virtual. Instead, it would be a regular class method on each subclass, and knowledge of the subclass type would be needed to call it.
Another option is to not worry about reading back data. Instead, make it a user interface issue. The user interface will somehow be responsible for setting (most) options, and so when they are set, they can be recorded there, by the user interface. The user interface is then responsible for updating the Configuration data store. That eliminates the need to read back values from the Renderer or Mixer subclass.
One limitation of saving settings only through the user interface is being able to detect when out of range options are re-mapped. If there is a function that can error check and re-map class specific Options structs before object initialization, then the actual Options struct data can be stored, before the object is initialized. That should be fine, provided the object doesn't modify settings further during or after construction. At least, not without being told to update settings by a call from the user interface.
Similarly, if an object might update it's own state, maybe the OS forces a minimized/maximized type change due to alt-tab or similar, the object might be responsible for providing an event that the user interface can listen to and make appropriate changes.  This seems like the most reasonable approach.

The external interface for the Configuration class has been simplified by removing all methods relating to:
"graphics", "audio", "options"
There's still a bit of work needed to cleanup the internal implementation of Configuration. Some of the above named sections still have special internal processing.

To remove final internal dependence on section names "graphics", "audio", and "options", some aspects of the Configuration class design will need to be updated. Currently the Configuration class reports errors in the loadData method when those required configuration section names are not found. This error reporting will need to be lifted out of the Configuration class. It would instead be reported in Game, or in main in OPHD.
Error reporting is done using the ReportProblemNames method. This method will need to move out of the anonymous namespace. Perhaps the value calculating version of it can be moved to ContainerUtils.h. Converting those values to exception methods might then be done inline. With error checking lifted to the calling code in place, we can then remove the ReportProblemNames method.
In the reverse direction, the saveData method currently calls DictionaryToXmlElementOptions, so that the "options" section can be written in its special sub-tag attribute format, while the "graphics", and "audio" sections are collected to be written in the standard attribute format. Instead, all sections should simply be output in the standard attribute format. (Previously other section names were ignored and not written to the file). At this point the DictionaryToXmlElementOptions method can be removed.
The ParseOptionsToDictionary method can then be deprecated. We may want to delay removal for some time, to allow saved game files to be loaded and resaved to convert their format to standard attributes for the "options" section.
There is a merge method for combining Dictionary objects from two collections. Potentially this could be generalized and moved into ContainerUtils.h. This task would be considered optional.

It seems the existing code for ReportProblemNames contains a bit of a bug:
const auto missing = names - required; // Bug

This should be the opposite:
const auto missing = required - names;

The exception message formatting code calls join, so I want to keep that part of of ContainerUtils.h, and creating extra internal library dependencies between header files.
Actually, seeing as how the calculation involves using a custom operator- defined for std::vector, it would be fairly easy to inline the whole method where it is used.

Had an additional thought on this. Since OPHD specifies default configuration settings for each of the "graphics", "audio", and "options" sections, those sections can never be missing once defaults are merged with the loaded settings. Hence, if that check were lifted from the Configuration class to the caller, there would actually be no need to do the check from OPHD. Other downstream projects may be in a similar situation, where they can provide a default, rather than check for the absence of a Configuration setting after load.
With that in mind, we could reasonably safely remove the internal check without worrying about having a corresponding check already being done at the point of call. Effectively this allows us to defer on how we refactor ReportProblemNames.

Currently there are some outstanding tasks related to this issue:

Generalizing and making public the ability to check keys against a required and optional set, and report back any missing or unexpected keys.
Loading/saving data to a section with a name other than "configuration". This may make the code more reusable for things like the Sprite class.
Related to the Sprite class, is the ability to check the file for a required or minimum version number.

I think I'd like to limit the scope of this issue to generalizing Configuration to handle an arbitrary set of sections, where each section is an arbitrary set of key/value pairs. In particular, there should be no special handling of any given section or key. With all the work so far completed, that seems to be the current state of affairs. As such, I'd like to close this issue as now completed.
Remaining work to refactor the Sprite loading code should be handled under a new separate issue. In particular, the Sprite loading code needs to be able to handle arrays of data (the frame list), which is not a feature needed or supported by the Configuration class. The ability to check for and ensure a minimum required version number can also be tracked under such a new issue for similar reasons, along with being able to load elements other than a "configuration" section.
The support code for required and optional sets of keys might also be considered out of scope. It's not clear we'll need such code going forward, so it might get removed. More likely though, it may get generalized and made public, perhaps as a split set of functions. It seems likely text input file processing code may need such features, whether it be for Configuration or Sprite, or XML or JSON formats. I think such work should be deferred to the new issue, as future work may better inform where to place such updated code, so it is accessible to all text processing methods that might need it.


Timepicker not showing the value passed to Datetime component

Hi everyone,
I passed the time value, for example value={this.props.time} into the <Datetime/> component with prop dateFormat={false}, but when I clicked into the input box to choose another time, the timepicker always shows 12:00 AM. Since I'm using Redux and it re-renders the component everytime I maked a change to the state tree through onChange function so I always stuck at 12:00 AM.
Is there any way to make the timepicker to show the value I passed into it?

I've found out the problem, I was passing the time in wrong format (the time was in "hh:mm" format), but I set timeFormat="hh:mm A" that's why <Datetime/> couldn't display it properly.

can u show more code, im having the same issue