Explore global state for managing metadata such as pipeline status and dates

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1819
Originally created by @bencodezen on 2020-02-28 03:15:44

Related to https://gitlab.com/meltano/meltano/issues/1778#note_294766582
Data such as pipeline status, last updated date, is something that should probably be managed at a global level and only called if there is an empty state with no data, or data has been updated.
The proposal is to use a global ensurePopulated that runs across each page load to ensure that the appropriate data is available. There would be a small concern as to whether this would actually be expensive from a payload perspective since this would theoretically fetch data that the user does not need (instead of only what's relevant to the page).
To do this effectively, it would be important to map out what critical data should be included in this ensurePopulated call in order to establish the scope of what this function would be capable of.
At the moment, we have a simple working solution where we can call the APIs directly on the pages that need it, but this would be necessary once we begin to scale our calls to the point where it is impossible to manage on a per page basis.

View 2 previous comments from the original issue on GitLab


Golang list modules command timesout after 30 minutes

Describe the bug
Golang list modules command timesout after 30 minutes
Please note that same command works outside the dependencycheck (with the same environment where the dependency checker is run).
When executed outside dependency checker, "go  list -m all" lists 541 dependencies and "go  list -json -m all" gives 4551 lines of output.
Version of dependency-check used
6.0.2
Log file
2020-10-14 12:42:32,271 org.owasp.dependencycheck.analyzer.GolangModAnalyzer:242
INFO  - Golang Mod Analyzer is enabled.
2020-10-14 12:42:32,271 org.owasp.dependencycheck.Engine:762
DEBUG - Starting Golang Mod Analyzer
2020-10-14 12:42:32,271 org.owasp.dependencycheck.Engine:810
DEBUG - Parallel processing with up to 16 threads: Golang Mod Analyzer.
2020-10-14 12:42:32,272 org.owasp.dependencycheck.AnalysisTask:86
DEBUG - Begin Analysis of '/go.mod' (Golang Mod Analyzer)
2020-10-14 12:42:32,272 org.owasp.dependencycheck.analyzer.GolangModAnalyzer:197
INFO  - Launching: [go, list, -json, -m, all] from
2020-10-14 13:12:32,272 org.owasp.dependencycheck.Engine:1128
ERROR - Analysis task was cancelled.
2020-10-14 13:12:32,272 org.owasp.dependencycheck.AnalysisTask:90
WARN  - An error occurred while analyzing '/go.mod' (Golang Mod Analyzer).
2020-10-14 13:12:32,275 org.owasp.dependencycheck.AnalysisTask:91
DEBUG -
org.owasp.dependencycheck.analyzer.exception.AnalysisException: go process interrupted
at org.owasp.dependencycheck.analyzer.GolangModAnalyzer.analyzeDependency(GolangModAnalyzer.java:293)
at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
Caused by: java.lang.InterruptedException: null
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at java.lang.UNIXProcess.waitFor(UNIXProcess.java:395)
at org.owasp.dependencycheck.analyzer.GolangModAnalyzer.analyzeDependency(GolangModAnalyzer.java:290)
... 7 common frames omitted
2020-10-14 13:12:32,275 org.owasp.dependencycheck.Engine:1129
DEBUG -
java.util.concurrent.CancellationException: null
at java.util.concurrent.FutureTask.report(FutureTask.java:121)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at org.owasp.dependencycheck.Engine.executeAnalysisTasks(Engine.java:773)
at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:673)
at org.owasp.dependencycheck.App.runScan(App.java:270)
at org.owasp.dependencycheck.App.run(App.java:202)
at org.owasp.dependencycheck.App.main(App.java:83)
2020-10-14 13:12:32,585 org.owasp.dependencycheck.App:218
ERROR - One or more fatal errors occurred
2020-10-14 13:12:32,586 org.owasp.dependencycheck.App:224
ERROR - go process interrupted
2020-10-14 13:12:32,586 org.owasp.dependencycheck.App:225
DEBUG - unexpected error
org.owasp.dependencycheck.analyzer.exception.AnalysisException: go process interrupted
at org.owasp.dependencycheck.analyzer.GolangModAnalyzer.analyzeDependency(GolangModAnalyzer.java:293)
at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
Caused by: java.lang.InterruptedException: null
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at java.lang.UNIXProcess.waitFor(UNIXProcess.java:395)
at org.owasp.dependencycheck.analyzer.GolangModAnalyzer.analyzeDependency(GolangModAnalyzer.java:290)
... 7 common frames omitted
2020-10-14 13:12:32,586 org.owasp.dependencycheck.utils.Settings:751
DEBUG - Deleting ALL temporary files from <path>/<file>
2020-10-14 13:12:32,620 org.owasp.dependencycheck.App:84
DEBUG - Exit code: -13
Expected behavior
Report should be clean without any errors.

Please provide:

the version of go being used:
OS used:
A copy of the go.mod and go.sum:

Tried the same test case using Dependency checker version 6.0.3 and seeing same behavior.
Below is the exception
DEBUG - Begin Analysis of '/go.mod' (Golang Mod Analyzer)
2020-11-11 06:59:55,475 org.owasp.dependencycheck.analyzer.GolangModAnalyzer:131
WARN  - Path to go executable not set. Trying default location. If you do want to set it, please set the analyzer.golang.path property
2020-11-11 06:59:55,475 org.owasp.dependencycheck.analyzer.GolangModAnalyzer:197
INFO  - Launching: [go, list, -json, -m, all] from
2020-11-11 07:29:55,475 org.owasp.dependencycheck.Engine:1128
ERROR - Analysis task was cancelled.
2020-11-11 07:29:55,475 org.owasp.dependencycheck.AnalysisTask:90
WARN  - An error occurred while analyzing '/go.mod' (Golang Mod Analyzer).
2020-11-11 07:29:55,477 org.owasp.dependencycheck.Engine:1129
DEBUG -
java.util.concurrent.CancellationException: null
at java.util.concurrent.FutureTask.report(FutureTask.java:121)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at org.owasp.dependencycheck.Engine.executeAnalysisTasks(Engine.java:773)
at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:673)
at org.owasp.dependencycheck.App.runScan(App.java:271)
at org.owasp.dependencycheck.App.run(App.java:203)
at org.owasp.dependencycheck.App.main(App.java:84)
2020-11-11 07:29:55,477 org.owasp.dependencycheck.AnalysisTask:91
DEBUG -
org.owasp.dependencycheck.analyzer.exception.AnalysisException: go process interrupted
at org.owasp.dependencycheck.analyzer.GolangModAnalyzer.evaluateProcess(GolangModAnalyzer.java:331)
at org.owasp.dependencycheck.analyzer.GolangModAnalyzer.analyzeDependency(GolangModAnalyzer.java:318)
at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
Caused by: java.lang.InterruptedException: null
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at java.lang.UNIXProcess.waitFor(UNIXProcess.java:395)
at org.owasp.dependencycheck.analyzer.GolangModAnalyzer.evaluateProcess(GolangModAnalyzer.java:328)
... 8 common frames omitted
Below are the environment details
Go version : go version go1.14.4 linux/amd64.
OS Version : Red Hat Enterprise Linux Server release 7.7 (Maipo)
A copy of the go.mod and go.sum: Attached.
Below are the additional observations/information

As per the thread dump, dependency checker is seen waiting at GolangModAnalyzer.evaluateProcess and then gets interrupted after 30 mins.
The dependency check analysis is working with dependency checker version 5.3.2 with the same go.mod.
Executed the command  go list -json -m all on command line and no hang seen

Hello, I am seeing same issue with kubernetes project: https://github.com/kubernetes/kubernetes

I believe this is fixed in the latest. Can anyone confirm?

Can confirm that I'm still seeing a very similar issue in 6.2.2.

Also confirming the same issue in 6.2.2. Any estimate on a fix for this?


Can not obtain the lm_head.weight

Hello,
Thanks for your wonderful work. I am doing some testing with your code. However, I found a very strange problem.
I want to print the weight shape of lm_head (https://github.com/X-PLUG/mPLUG-Owl/blob/main/mPLUG-Owl2/mplug_owl2/model/modeling_mplug_owl2.py#L220) with the following codes.
        print("Before initializing lm_head: ", config.hidden_size, config.vocab_size)
        self.lm_head = nn.Linear(config.hidden_size, config.vocab_size, bias=False)
        print("After initializing lm_head: ", config.hidden_size, config.vocab_size)
        print("weight shape: ", self.lm_head.weight.shape)

The results are:
Before initializing lm_head:  4096 32000
After initializing lm_head:  4096 32000
weight shape:  torch.Size([0])

I just very confused why the output of lm_head.weight.shape is 0. I wonder whether you have some insights about this problem.
Monitoring this parameter is very important for me. However, I just can not obtain such a parameter during training.
Thanks.

Are you using the zero-3 strategy to initialize the model? If so, the parameters may be offloaded.


contributors list in search does not match list on project overview

Steps:

Search for "Murray"
View the project titled "Replication of SL Murray...Exp. 8" in the search results and take note of the contributor list.

3. Go to this project's overview. Look at the list of contributors on the overview.

Expected outcome: Lists will match each other exactly.
Actual outcome: Contributors are listed in the same order, but Mallorie Miller and Rebecca Goldberg have disparities in their OSF profile links.
ALSO,
Steps:

View the project titled "Replication of SL Murray...Exp. 8" in the search results again.
Click on Rebecca Goldberg's name.

Expected outcome: User will be taken to Rebecca Goldberg's OSF profile.
Actual outcome: User is taken to Sining Wu's profile.

Fishy enough it appears to me that we should dig into the underlying issue -

Also happens on this project: https://osf.io/w6fp4/
I'll look into it

OK!

Found the problem. This is what happens when you add a unreg contributor first and add a registered contributor later. I guess the search results are just applying the contributor links returned to the first few contributors.

Do we know how to resolve?

Not yet. Looking at it.

This is a result of the format of elasticsearch. Calling es.search(index=index, doc_type=doc_type, body=query) returns a formatted output that is specified in website/search/elasticsearch.py:update_node. That format stores contributor names and contributor urls in separate lists, which results in the bug. My suggestion is to use the following format in that method:
{
    'contributors': [
        {
            'url': '/a1b2c'
            'name': 'Ginny Huang'
        },
    ],
    ...
}

However if I change the format, the format would only take effect when update_node is called.
@lbanner In this case I think I need help from @fabianvf or you can just re-assign this issue to him.

OK - maybe you reach out to @fabianvf ?  --  recognizing he has SHARE priorities right now, but might give quick insight.

@huangginny I think that format would be much better. We have a migration script ready, so the impact on the elasticsearch data is irrelevant - if you make the change to the schema, we can migrate all users and nodes to make use of it.

@fabianvf Thanks, I'll try it out :)


Add historical services to !setlist using new api filter

Planning Center has added a before and after filter.
https://github.com/planningcenter/developers/issues/486
We should be able to use this to quickly query Service plans.

This is how to get a single date:
https://api.planningcenteronline.com/services/v2/service_types/173868/plans?filter=after,before&sort=sort_date&after=2018-11-10T00:00:00.000Z&before=2018-11-12T03:59:59.999Z
I'm adding this here so I don't forget.


Extension issue

Issue Type: Bug
Extension Name: tabnine-vscode
Extension Version: 3.5.1
OS Version: Windows_NT x64 10.0.19043
VS Code version: 1.62.3

:warning: We have written the needed data into your clipboard. Please paste! :warning:
gz#8927

Hi @jasmeet78, what seems to be the problem?


ARROW-15791: [Go] ipc FileWriter negative WaitGroup counter

⚠ Ticket has not been started in JIRA, please click 'Start Progress'.

Someone may want to take a look at the bot. There is no 'Start Progress' to be found anywhere in the jira ticket.

Once all the checks pass, i'll merge this. thanks for the catch @astrelsky !


Added missing dependency

I'm writing my custom build configuration file and when adding Graticule that wouldn't work. So I digged in and found out that an additional dependency on  OpenLayers/Rule.js was missing, see:
        var gratStyle = new OpenLayers.Style({},{
            rules: [new OpenLayers.Rule({'symbolizer':
                {"Point":this.labelSymbolizer,
                 "Line":this.lineSymbolizer}
            })]

It would make to also add StyleMap.js and Layer/Vector.js. Thanks.

@elemoine , how does that work? if I add those additional dependencies and commit and push to the same branch, will that also become part of this pull req?

@ZiglioNZ Yes. You'll find this very convenient. Rule is create branch for every pull request.

@elemoine Done :-)

Excellent. Thank you.


Not working on iOS with bowser

Hello, i use the browser called bowser to support the getusermedia function on ios devices.
For some reason no video is displayed when i click play and even no selection-options for the front and back camera. The dropdown box appears, but has no entries.

Hello,
Please look at these pages.
I know it can be reached only partial operation.
Android system also created a similar problem,
with system and browser context.
http://caniuse.com/#feat=stream
http://mobilehtml5.org/


Rubix caching: frequent cache evictions result in failed queries

Test setup like in https://github.com/prestosql/presto/issues/3494 but rubix.cache.usage.percentage was setup to 2. This translates to cache size of ~10GB.
Cluster was exercised with the same query as in https://github.com/prestosql/presto/issues/3494 which reads whole lineitem (171GB).
With such configuration many cache evictions are happening throughout the query execution. This itself is fine and expected. Unexpected is that as a result queries are failing:
[ip-192-168-20-199:~/workspace/tmp] [] ⌘ for in in `seq 1 50`;do /Users/lukaszos/workspace/repos/prestosql/presto/presto-cli/target/presto-cli-*-executable.jar  -f count_lineitem.sql
 ;done
Query 20200429_103854_00000_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_103913_00001_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_103925_00002_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_103931_00003_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_250fa5e5-8d62-47e0-98fa-98ce39a938b3
Query 20200429_103941_00004_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_19e8c24a-7fc9-4512-a296-555ab4efc0c2
Query 20200429_103945_00005_t8rib failed: Malformed ORC file. Could not decompress all input (output buffer too small?) [s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_250fa5e5-8d62-47e0-98fa-98ce39a938b3]
Query 20200429_103952_00006_t8rib failed: Malformed ORC file. Could not decompress all input (output buffer too small?) [s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_df899620-c77b-4012-a32c-1eb8cd1119ef]
Query 20200429_103956_00007_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_19e8c24a-7fc9-4512-a296-555ab4efc0c2
Query 20200429_103959_00008_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_104002_00009_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_104005_00010_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_104015_00011_t8rib failed: Malformed ORC file. Invalid stripe row index [s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0]
Query 20200429_104016_00012_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_104021_00013_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_104023_00014_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_104026_00015_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_104030_00016_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_19e8c24a-7fc9-4512-a296-555ab4efc0c2
Query 20200429_104032_00017_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_104037_00018_t8rib failed: Malformed ORC file. Could not decompress all input (output buffer too small?) [s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_250fa5e5-8d62-47e0-98fa-98ce39a938b3]
Query 20200429_104051_00019_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_104053_00020_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_0dbfd7b1-920d-43b6-8179-8c53dab105d0
Query 20200429_104058_00021_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_250fa5e5-8d62-47e0-98fa-98ce39a938b3
Query 20200429_104108_00022_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_250fa5e5-8d62-47e0-98fa-98ce39a938b3
Query 20200429_104120_00023_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_250fa5e5-8d62-47e0-98fa-98ce39a938b3
Query 20200429_104133_00024_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_250fa5e5-8d62-47e0-98fa-98ce39a938b3
Query 20200429_104134_00025_t8rib failed: Failed to read ORC file: s3://starburstdata-datasets/tpch-sf1000-ORC/lineitem/20180106_235637_00251_ecxdi_250fa5e5-8d62-47e0-98fa-98ce39a938b3

Logs of coordinator and worker attached:
coordinator.log.gz
worker.log.gz
Note: Presto was built using Rubix 0.3.6 with https://github.com/qubole/rubix/pull/363 applied.
Eventually system ended up in state as in https://github.com/prestosql/presto/issues/3524.
cc: @stagraqubole

There are two problems with eviction we have found:

Query cancellations is triggering evictions if file is being read from cache. This will be fixed with first commit in https://github.com/qubole/rubix/pull/368. This will remove the unnecessary evictions

There is a case where invalidations can cause errors in reads happening in parallel. This usually happens in small disks available to Rubix because the evictions are LRU and having files being read and also being LRU candidate doesn't usually happen in a decently sized disks. We have identified a solution for this too and work is underway, I will update the tracking jira here.

@stagraqubole What are recommended workarounds for this? Is it sufficient to have large enough disk?

Yes, even a modestly sized disk will minimise the chances of hitting this given LRU files would not be read at the time of eviction.

Fixed with #4551


Add tests module with ResourceMetrics

These changes create a new splunk-otel-collector/tests module to house future integration tests and a set of helpers for creating and working within testable environments.
These initial updates include the ResourceMetrics type that is roughly one-to-one w/ the OTel spec and pdata.Metrics definitions, with the exception of rolling individual datapoints up into the Metric type, which would otherwise just be a parent envelope.  I am not certain this is a desired path, and would appreciate feedback but to me fewer levels of indirection/nesting are preferred when writing test assertions.
These changes don't source the new go module with the existing Makefile or CI, as those will be addressed in subsequent PRs.

Can you show an example usage of this new testbed?

Updated w/ an example of the overall proposed metric helper additions.


[Storage] Drop Node.js 8 and IE 11 support

As mentioned in #16497, we need to ship a stable version of our storage packages after updating them to use the latest core-tracing and core-http packages. Since the latest core packages have dropped support for Node.js 8 and IE11, this PR makes the minimum changes to reflect the same in the hotfix branch before @maorleger sends out a PR to make the change to move to the latest core-tracing.
Please note that these changes are being made against the hotfix branch and not the main branch.

Thanks @EmmaZhu!


README missing performance data metrics table

While reviewing the README I noticed that performance data metrics are not specified.

NOTE: Use the atc0005/check-cert project as a reference.


Fix some comments

Description
fix some comments. including typos, struct name

Closes #<issue_number>.
Readiness checklist

[ ] I added/updated unit tests (and they pass).
[ ] I added/updated integration/compatibility tests (and they pass).
[ ] I added/updated comments and checked rendering.
[ ] I made spot refactorings.
[ ] I updated user documentation.
[ ] I ran task all, and it passed.
[ ] I ensured that PR title is good enough for the changelog.
[ ] (for maintainers only) I set Reviewers (@FerretDB/core), Milestone (Next), Labels, Project and project's Sprint fields.
[ ] I marked all done items in this checklist.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

#4238 should be merged first

Thank you!


Feat/return component

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

run: yarn lint --fix to fix linter issues


Add support for response_format in OpenAiAudio

Describe the feature or improvement you're requesting
I would like to get the word level timestamps for the transcriptions. I couldn't specify the vtt or the srt format in my requests.
Additional context
No response

Hi, in the latest release tonight i've added the segmentation for transcription and translation.
You can read it as segments or words.

For example you can get the full text and the segments that compound it.

You can do the same for translation.

Would it be possible to include the fix in the version compatible with .NTE 8.0? Thank you!


Use Dagger2 injected objects in Plugin

Hi,
I really like this library and it has brought some great improvements into my code. Thanks :-)
However I'm facing a challenge now:
I'm using Dagger2 as a dependency injection framework in my app.
I have a (CompositeAndroid) plugin that needs to have access to some injected classes.
However since plugins are added in the constructor of an Activity (or Fragment) and fields are injected in onCreate() of the root base Activity it is not possible to access injected fields on construction so I cannot pass it as a parameter to the plugin from the Activity.
Example:
abstract class LockableSupportActivityBase : DaggerSupportActivityBase() {

    @Inject
    protected lateinit var preferenceHandler: PreferenceHandler

    init {
        // this throws NotInitializedException on "preferenceHandler"
        addActivityPlugins(LockPlugin(preferenceHandler))
    }

}

Injecting the Plugin itself is also not possible since it has to be added to the Activity in the constructor and the activity also has access to injected properties only right after super.onCreate() (so it's too late).
Example:
abstract class LockableSupportActivityBase : DaggerSupportActivityBase() {

    @Inject
    protected lateinit var lockPlugin: LockPlugin

    init {
        // this throws NotInitializedException on "lockPlugin"
        addActivityPlugins(lockPlugin)
    }

}

Is there a way to work around this or is this a problem that needs a more sophisticated fix?

instead of passing the object directly into your plugin you could pass a method returning the object.
class LockPlugin(val preferenceHandlerProvider: ()-> PreferenceHandler) : ActivityPlugin { ... }

    init {
        addActivityPlugins(LockPlugin( { preferenceHandler } ))
    }

Ah that's a great idea!
Thanks for the quick reponse.
I will try it tomorrow though since it's 4 a clock in the morning around here... :D

It works!
Although it's kind of a workaround it's not that bad so I can live with it.
Thx for the quick help :)


Better framework for naming of case tables/data contexts

This PR includes some changes to the way our codapPhone api functions are setup to hopefully make managing names easier.
The only names we need to worry about keeping unique are case tables and data contexts. With this in mind, I changed the way we generate a new table with data in Transformation.tsx. Rather than call a "create data context" and "create table" function manually, you call one function that does both, and pass a desired name you'd like to use (or null if you want one generated). This lets us ensure the name isn't already in use for a table/context before calling out to iframephone.
This also gives us a little more sanity for dev purposes, as now all collections/tables/contexts that are related will have a common number in their name, rather than gensyming a new name for each resource and having table_1 contain context_2 which has collection_3.

Thanks, this is great and will make naming much more sane.
One thing I notice is that upon creating a table (either through another plugin or ours), the name shows up in our data context list as what appears to be the data context title (e.g. US Microdata). However, after producing a transformed version of that table, the original table then appears under its case table title. Any idea why this might be happening?
I feel like case table names are preferred for the dropdown, since they may correspond more intuitively to users' expectations of how things are named/grouped.

One thing I notice is that upon creating a table (either through another plugin or ours), the name shows up in our data context list as what appears to be the data context title (e.g. US Microdata). However, after producing a transformed version of that table, the original table then appears under its case table title. Any idea why this might be happening?

How are you getting this to happen? When I create a People table through the Microdata plugin, it always shows up in the dropdown as US Microdata, even after a transform.

@stardust66 Hmm interesting, I can get this by just creating the People table, then running it through a do-nothing transformation like filter true. The name changes from US Microdata (US Microdata) to People (US Microdata). Same will happen with our tables if I transform them.
@P-bibs are you able to reproduce?

Oh nevermind I didn't catch that you meant on this branch.

Hmm yes this also happens for me and I can't immediately understand why.
I agree that table names would make more sense for the user. However, are we sure that there's a one-to-one correspondence between tables and data contexts? I was under the impression that data contexts just sort of exist and you can display them through tables at will. This could lead to a scenario where there's two tables for one data context and we don't know which name to ues.

Hmm still not sure I understand why it was using the collection name instead then but feel free to push

However, are we sure that there's a one-to-one correspondence between tables and data contexts? I was under the impression that data contexts just sort of exist and you can display them through tables at will. This could lead to a scenario where there's two tables for one data context and we don't know which name to use.

Yeah, I'm not sure. I'm not against displaying both the case table and context name, as you're doing now, to disambiguate. It seems to let me rename two tables to the same name, but their context names are still unique and the user doesn't seem to have a way to change that.
This looks good to me!


Quickstart guide

It would be nice if there was a quickstart guide.  I feel like the docs at https://mkoryak.github.io/floatThead/ just kinda threw me into the deep end.  There are no basic examples in sight.
After many hours, I finally figured out this as a bare minimum:
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.1/jquery.slim.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/floatthead/2.1.4/jquery.floatThead.min.js"></script>
<script type="text/javascript">
$('table').floatThead();
</script>

Unfortunately, that leaves the text of the body visible behind the thead.  Adding bgcolor='white' to the thead's tr makes the thead text readable, but there is still some body text showing at the very top above the thead.  This is really distracting on a real webpage, but barely visible on JSFiddle: https://jsfiddle.net/Pascal666/4L0xeb3h/

Looks like I just wasted a bunch of time on this plugin.  I don't need it at all.  Adding the below to my head did everything I need.  Oh well.  Perhaps a quickstart guide will help someone else.
<style type="text/css">
table thead tr th {
  background-color: white;
  position: sticky;
  z-index: 100;
  top: 0;
}
</style>

JSFiddle: https://jsfiddle.net/Pascal666/c981j75d/

Yes sticky position will cure some of your problems. I should make a guide
about what this plugin solves that position:sticky can not.
I digress; thank you for taking the time to make a guide. I cannot make one
because I have not been diving into any deep ends for a long time. I don't
mean to sound like a jerk either. I really have no idea what a new jQuery
programmer wants to see.
 I don't need it
at all. Adding the below to my head did everything I need. Oh well.
Perhaps a quickstart guide will help someone else.

JSFiddle: https://jsfiddle.net/Pascal666/c981j75d/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mkoryak/floatThead/issues/453?email_source=notifications&email_token=AAC5WSN3HHHX6Q3ZZXCFVZLQ27RQPA5CNFSM4KATM6P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHYUO6Q#issuecomment-569460602,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC5WSNWHAPEQZQQF2R4V6TQ27RQPANCNFSM4KATM6PQ
.


[BUG] Tasks do not persist between dooit sessions

Describe the bug 🐛
After closing and re-opening the shell dooit is running in, all of my tasks have disappeared.
To Reproduce 🐣
Steps to reproduce the behavior:

Run dooit
Put in some tasks
Close the shell dooit is running in
Run dooit; old tasks are gone

Expected behavior  🤔
I expect tasks to persist between dooit sessions.
Desktop (please complete the following information):  🤖

OS: MacOS
Version: Monterey 12.3.1

Did  you quit  dooit with either ctrl+c or ctrl+q ?
dooit does not saves task on edit, it only does when quit keybindings are triggered

a customizable autosave routine would be highly appreciated ?!

I suppose saving the todo on each edit should be fine but haven't tested that for having a much larger data.
I'll stress test and see if that does not cause too much delay, we can move the saving part to a thread for non-disruptive flow :)

@kraanzu  I don't think this will interfere with the syncthing sync that I will enable for the data file but I will report back how that works.

I am even experiencing this issue while closing dooit normally...


MDF [test] free cp twice for pub

Codecov Report
Patch coverage has no change and project coverage change: +0.07 :tada:

Comparison is base (c2ddcd3) 53.11% compared to head (86aecf0) 53.19%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #547      +/-   ##
==========================================
+ Coverage   53.11%   53.19%   +0.07%
==========================================
  Files         120      120
  Lines       36577    36577
==========================================
+ Hits        19428    19456      +28
+ Misses      17149    17121      -28

see 20 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


DeepLX support other endpoints

https://deeplx.owo.network/endpoints/pro.html

Gonna check this soon, sry for the late reply.
Also anyone could create his own translator, no need to be built-in, but still, gonna check it out


Add very basic unsigned command validation

This adds some "smart" command validation for allowing buildkite-signed-pipeline upload <optional file> to be allowed through without a signature.
I've put this up early as I'm keen for your feedback on this approach @lox
I toyed with the idea of parsing the command with kingpin but:

Application.Parse only accepts split up commands (string[]) vs a single string; and
This relies on the command parsing library for security (e.g. does it ignore shell backticks? variable expansion? etc)

TODO:

[x] Use it during verify, making sure to force a signature check if a signature is found, or there are plugins used in the step
[x] Consider argument quoting/additional arguments, etc

🚢 💪🏻


Error: Unable to find module with ID: aurelia-templating-router/router-view.html

I'm submitting a bug report

Library Version:
1.2.0

Please tell us about your environment:

Operating System:
Win 10

Node Version:
6.11.0

NPM Version:
5.4.2

JSPM OR Webpack AND Version
Webpack 3.6.0

Browser:
all

Language:
Ts 2.5.3

Current behavior:
Upon attempting to load site after a successful build:
Error: Unable to find module with ID: aurelia-templating-router/router-view.html
    at WebpackLoader.<anonymous> (aurelia-loader-webpack.js:187)
    at step (aurelia-loader-webpack.js:36)
    at Object.next (aurelia-loader-webpack.js:17)
    at aurelia-loader-webpack.js:11
    at initializePromise (es6-promise.js:459)
    at new Promise (es6-promise.js:871)
    at 229.__awaiter (aurelia-loader-webpack.js:7)
    at WebpackLoader.229.WebpackLoader._import (aurelia-loader-webpack.js:152)
    at WebpackLoader.<anonymous> (aurelia-loader-webpack.js:252)
    at step (aurelia-loader-webpack.js:36)

Notes
I just bumped up the versions of my aurelia packages.
    "aurelia-animator-css": "^1.0.3",
    "aurelia-authentication": "~3.7.0",
    "aurelia-binding": "^1.3.0",
    "aurelia-bootstrapper": "^2.1.1",
    "aurelia-configuration": "^1.0.17",
    "aurelia-dependency-injection": "^1.3.2",
    "aurelia-event-aggregator": "^1.0.1",
    "aurelia-fetch-client": "^1.1.3",
    "aurelia-framework": "^1.1.5",
    "aurelia-history": "^1.1.0",
    "aurelia-i18n": "~2.0.0",
    "aurelia-loader": "^1.0.0",
    "aurelia-logging": "^1.3.1",
    "aurelia-orm": "~6.2.0",
    "aurelia-pal": "^1.4.0",
    "aurelia-route-mapper": "^0.1.0",
    "aurelia-router": "^1.4.0",
    "aurelia-task-queue": "~1.2.1",
    "aurelia-templating": "~1.5.0",
    "aurelia-templating-binding": "^1.4.0",
    "aurelia-templating-resources": "^1.5.1",
    "aurelia-templating-router": "^1.2.0",
    "aurelia-ui-virtualization": "^1.0.0-beta.3.1.1",

I've also tried setting my package.json to only point to "aurelia-bootstrapper": "^2.1.1" and still getting the issue. Really unsure of how to handle this.

On another note, the previous working versions were these:
    "aurelia-animator-css": "^1.0.2",
    "aurelia-authentication": "~3.7.0",
    "aurelia-binding": "~1.2.2",
    "aurelia-bootstrap": "^0.1.18",
    "aurelia-bootstrapper": "~2.1.1",
    "aurelia-configuration": "^1.0.17",
    "aurelia-dependency-injection": "~1.3.1",
    "aurelia-event-aggregator": "~1.0.1",
    "aurelia-fetch-client": "~1.1.2",
    "aurelia-framework": "~1.1.2",
    "aurelia-history": "~1.0.0",
    "aurelia-i18n": "~1.6.2",
    "aurelia-loader": "~1.0.0",
    "aurelia-logging": "~1.3.1",
    "aurelia-orm": "~6.2.0",
    "aurelia-pal": "^1.3.0",
    "aurelia-route-mapper": "^0.1.0",
    "aurelia-router": "~1.3.0",
    "aurelia-task-queue": "~1.2.0",
    "aurelia-templating": "~1.4.2",
    "aurelia-templating-binding": "~1.3.0",
    "aurelia-templating-resources": "~1.4.0",
    "aurelia-templating-router": "~1.1.0",

Can you providing a working example? Perhaps using gist.run. This looks like an issue with how webpack is trying to load the file, but it's hard to tell.

I'll try and set it up first thing tomorrow morning. I've reverted back to
my original versions and app is working that way. I guess there was some
breaking change somewhere along them.
On Oct 3, 2017 3:43 PM, "Matthew James Davis"<EMAIL_ADDRESS>wrote:

Can you providing a working example? Perhaps using gist.run. This looks
like an issue with how webpack is trying to load the file, but it's hard to
tell.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aurelia/templating-router/issues/63#issuecomment-333845966,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABu-_mYyIf912rEUenuAmN12ojzOXtI9ks5sojn8gaJpZM4Pr_tD
.

@Kukks if possible, could you share the other dependencies in package.json as well, in addition to the outputs of npm -v and node -v ?

@JeroenVinke  @davismj I was playing with it again and re-did the package bumps in case I missed anything: seem to work with the following:
 "devDependencies": {
    "@types/jest": "21.1.2",
    "@types/lodash": "4.14.77",
    "@types/node": "8.0.32",
    "@types/webpack": "3.0.13",
    "aurelia-loader-nodejs": "1.0.1",
    "aurelia-pal-nodejs": "1.0.0-beta.2.0.0",
    "aurelia-protractor-plugin": "1.0.5",
    "aurelia-testing": "1.0.0-beta.3.0.1",
    "aurelia-webpack-plugin": "2.0.0-rc.5",
    "autoprefixer": "7.1.4",
    "awesome-typescript-loader": "3.2.3",
    "copy-webpack-plugin": "4.1.0",
    "cross-env": "5.0.5",
    "css-loader": "0.28.7",
    "expose-loader": "0.7.3",
    "extract-text-webpack-plugin": "3.0.1",
    "file-loader": "1.1.4",
    "html-webpack-plugin": "2.30.1",
    "http-server": "0.10.0",
    "istanbul-instrumenter-loader": "3.0.0",
    "jasmine-core": "2.8.0",
    "jest": "21.2.1",
    "jest-cli": "21.2.1",
    "json-loader": "0.5.7",
    "karma": "1.7.1",
    "karma-chrome-launcher": "2.2.0",
    "karma-coverage-istanbul-reporter": "1.3.0",
    "karma-jasmine": "1.1.0",
    "karma-mocha-reporter": "2.2.4",
    "karma-webpack": "2.0.4",
    "nps": "5.7.1",
    "nps-utils": "1.4.0",
    "postcss-loader": "2.0.6",
    "protractor": "5.1.2",
    "style-loader": "0.19.0",
    "ts-jest": "21.0.1",
    "ts-node": "3.3.0",
    "typescript": "2.5.3",
    "url-loader": "0.6.1",
    "wait-on": "2.0.2",
    "webpack": "3.6.0",
    "webpack-dev-server": "2.9.1",
    "@types/hammerjs": "~2.0.34",
    "@types/nprogress": "0.0.29",
    "@types/prismjs": "~1.6.1",
    "@types/reflect-metadata": "0.0.5",
    "@types/webpack-env": "~1.13.0",
    "node-sass": "^4.5.2",
    "sass-loader": "^6.0.3",
    "svg-inline-loader": "~0.8.0",
    "ts-nameof": "^0.10.2",
    "ts-nameof-loader": "^1.0.1",
    "tslint": "~5.7.0",
    "tslint-loader": "~3.5.3"
  },
  "dependencies": {
    "aurelia-animator-css": "~1.0.3",
    "aurelia-binding": "~1.3.0",
    "aurelia-bootstrapper": "~2.1.1",
    "aurelia-dependency-injection": "~1.3.2",
    "aurelia-event-aggregator": "~1.0.1",
    "aurelia-fetch-client": "~1.1.3",
    "aurelia-framework": "~1.1.5",
    "aurelia-history": "~1.1.0",
    "aurelia-loader": "~1.0.0",
    "aurelia-logging": "~1.3.1",
    "aurelia-orm": "~6.2.0",
    "aurelia-pal": "~1.4.0",
    "aurelia-router": "~1.4.0",
    "aurelia-task-queue": "~1.2.1",
    "aurelia-templating": "~1.5.0",
    "aurelia-templating-binding": "~1.4.0",
    "aurelia-templating-resources": "~1.5.1",
    "aurelia-templating-router": "~1.2.0",
    "aurelia-ui-virtualization": "~1.0.0-beta.3.1.1",
    "aurelia-route-mapper": "~0.1.0",
    "aurelia-i18n": "~2.0.0",
    "aurelia-configuration": "~1.0.17",
    "aurelia-authentication": "~3.7.0",
    "aurelia-validation": "~1.1.1",
    "bootstrap": "~4.0.0-beta",
    "bootstrap-purr": "github:softwarespot/jquery-bootstrap-purr",
    "choices.js": "~3.0.2",
    "clipboard": "~1.7.1",
    "custom-event-polyfill": "~0.3.0",
    "es6-promise-promise": "~1.0.0",
    "flatpickr": "~3.0.7",
    "gridstack": "github:troolee/gridstack.js#8e4898557ee9f09b0f0bd576535d3f6ad277660d",
    "gulp": "github:gulpjs/gulp#4.0",
    "hammerjs": "~2.0.8",
    "hesehus-js-breakpoint": "~1.0.1",
    "i18next": "~9.0.1",
    "i18next-browser-languagedetector": "~2.0.0",
    "i18next-fetch-backend": "~0.1.0",
    "i18next-localstorage-cache": "~1.1.1",
    "intl": "~1.2.5",
    "isomorphic-fetch": "~2.2.1",
    "jquery": "~3.2.1",
    "jquery-ui": "~1.12.1",
    "keycode": "~2.1.9",
    "localforage": "~1.5.0",
    "moment": "~2.18.1",
    "nouislider": "~10.1.0",
    "nprogress": "~0.2.0",
    "popper.js": "~1.12.5",
    "prismjs": "~1.8.1",
    "raf": "~3.4.0",
    "raw-loader": "~1.0.0-beta.0",
    "reflect-metadata": "~0.1.10",
    "requirejs": "~2.3.5",
    "select2": "~4.0.4",
    "selectize": "~0.12.4",
    "sweetalert2": "~6.10.1",
    "text": "github:requirejs/text#latest",
    "webcomponents.js": "github:webcomponents/webcomponentsjs#v0"
  }

node
node -v
v6.11.0
npm -v
5.4.2

@Kukks Thanks for taking the time to investigate and follow up. That's a huge help to us. Glad everything is working, Andrew.

@davismj  I'm having the same issue. Matching my packages to the same ones @Kukks has does not fix it, nor does changing packages to the ones in the referenced issue.
Reproducible sample attached. (Dotnet)
WebClient.zip

This is quite mysterious. I have two projects. One is working with
"aurelia-templating-binding": "1.4.0",
"aurelia-templating-resources": "1.5.1",
"aurelia-templating-router": "1.2.0",
The other one shows the mentioned error "Unable to find module with ID: aurelia-templating-router/router-view.html".
Both have the exact same webpack setup with the same aurelia packages and versions.
Any ideas?

For what it's worth I got the same error when I upgraded from "aurelia-templating-router": "^1.0.0", -> "aurelia-templating-router": "^1.2.0".
I'm in the process of upgrading my aurelia-* packages. I ran npm update and had to roll back. Proceeded to do one package at a time and when I got to aurelia-templating-router that's when I go the same error as mentioned above.
Thanks --Steve

Glad I'm not alone with this...
@davismj can you reopen this? I'm out of options.

Maybe you can try and setting the deps to point to only aurelia-bootstrapper. Try also removing the npm_modules folder and to check after a fresh install if all the aurelia modules installed are the correct versions. Could be another package demanding a lower version of one specific aurelia package

@Kukks Thanks for your tip!
I changed my package.json from (only aurelia packages shown):
        "aurelia-bootstrapper": "2.1.1",
        "aurelia-event-aggregator": "1.0.1",
        "aurelia-fetch-client": "1.1.3",
        "aurelia-framework": "1.1.5",
        "aurelia-history-browser": "1.1.0",
        "aurelia-loader-webpack": "2.1.0",
        "aurelia-logging-console": "1.0.0",
        "aurelia-pal": "1.4.0",
        "aurelia-pal-browser": "1.3.0",
        "aurelia-polyfills": "1.2.2",
        "aurelia-route-recognizer": "1.1.1",
        "aurelia-router": "1.4.0",
        "aurelia-templating-binding": "1.3.0",
        "aurelia-templating-resources": "1.4.0",
        "aurelia-templating-router": "1.1.0",

To
        "aurelia-bootstrapper": "2.1.1",
        "aurelia-fetch-client": "1.1.3",

Now it works!
I used to specify all aurelia packages due to problems with different versions of npm and yarn. Sometimes packages were not included if not specified.
Some aurelia package seems to cause the issue, but I can live with this setup for the moment.
Thank you.

It doesn't work for me.
For now, I changed my dependencies to
        "aurelia-bootstrapper": "^2.1.1",
        "aurelia-loader-nodejs": "^1.0.1",
        "aurelia-templating-resources": "1.4.0",
        "aurelia-templating-router": "^1.1.0",

This is working for my electron(-compile v6.4.2) app.

@Lichtjaeger @Kukks @kuechlerm
I'm not exactly sure the source of the issue. It's not a router issue; it's a more general module loading issue, I believe. See here for a similar error in the templating-resources library: https://github.com/aurelia/templating-resources/issues/312.
It also seems to be specific to an update with both Aurelia and then webpack loader. Where possible I always use systemjs so I don't have a lot of personal experience with this issue.
Let me ping the team internally to see if someone can point me in the right direction to close out this issue once and for all. Maybe there is in fact something we can do in the router library to resolve this.
Thanks for patience, everyone.

Hey everyone, do any of you have yarn.lock or package-lock.json files? Could you try and remove those, together with node_modules and yarn or npm install again? Let me know how that goes.

Hi @JeroenVinke I do have a package-lock.json file. I'll delete it as well as my node_modules file and then try upgrading to the latest aurelia-templating-router package

@JeroenVinke I just tried it and it seems to have worked, but now I'm getting the attached warnings in the browser console. I'm going to see if I'm able to follow similar steps with the aurelia-templating-binding and aurelia-templating-resources packages.

Removing the package-lock.json file worked.
Now I only have "aurelia-bootstrapper" and "aurelia-loader-nodejs" in my dependencies.
And I don't have any warnings, unlike @sboyd .

What worked for me:
Per @kuechlerm, reducing the packages in package.json down to:
"aurelia-bootstrapper": "2.1.1",
"aurelia-fetch-client": "1.1.3",

Per @Lichtjaeger , removing the package-lock.json file
Thanks

Just so I'm clear @dkent600 you're saying I can trim all this down to just two packages.
"aurelia-bootstrapper-webpack": "^1.1.0",
"aurelia-event-aggregator": "^1.0.0",
"aurelia-fetch-client": "^1.0.1",
"aurelia-framework": "^1.1.5",
"aurelia-froala-editor": "^2.7.3",
"aurelia-google-maps": "^1.0.21",
"aurelia-history-browser": "^1.1.0",
"aurelia-loader-webpack": "^1.0.3",
"aurelia-logging-console": "^1.0.0",
"aurelia-pal-browser": "^1.0.0",
"aurelia-polyfills": "^1.1.1",
"aurelia-route-recognizer": "^1.1.1",
"aurelia-router": "^1.4.0",
"aurelia-templating-binding": "^1.4.0",
"aurelia-templating-resources": "^1.5.2",
"aurelia-templating-router": "^1.2.0",
"aurelia-validation": "^1.1.2"
To only having two packages?
"aurelia-bootstrapper": "2.1.1",
"aurelia-fetch-client": "1.1.3",

@sboyd  Certainly not all of those, but I most of them.  aurelia-bootstrapper has a lot of dependencies.  You can see them listed in its own package.json.

@dkent600 out of curiosity what Aurelia template did you start your project with? https://github.com/aurelia/skeleton-navigation I'm using the ESNext webpack template. I'm curious because I don't have an aurelia-bootstrapper package but I have a aurelia-bootstrapper-webpack package.

@sboyd I started with Aurelia-Typescript-Webpack

Thank you @dkent600

Sorry to keep spamming everyone, but @JeroenVinke any idea how to get rid of the warnings I'm regarding chunks?
https://user-images.githubusercontent.com/219548/31922606-323068d8-b833-11e7-969f-b0bc49cde2ac.png

@jods4 any thoughts on the warnings that @sboyd is getting?

@jods4 and @JeroenVinke I think I'm ok now. I commented out, and will soon delete, the first line under entry in my webpack.config.bable.js file and the warning is gone now and the app seems to still work ok.
let config = generateConfig(
{
entry: {
//'app': ['./src/main' /* this is filled by the aurelia-webpack-plugin */],
'aurelia-bootstrap': coreBundles.bootstrap,
'aurelia': coreBundles.aurelia.filter(pkg => coreBundles.bootstrap.indexOf(pkg) === -1)
},
output: {
path: outDir,
filename: "[name].[chunkhash].js"
}
},

For anyone stumbling upon the same issue and landing here: in my case it helped to delete the node_modules folder, then run npm install and then run npm dedupe! The last part made the difference.

@dmoebius
You probably use npm and you have package.lock.json
Delete that file and node_modules and reinstall dependencies.
It is an npm issue
It was discussed a lot @ https://discourse.aurelia.io/
and in https://gitter.im/aurelia/Discuss


Changed how to parse the result for error handling

Example of correct syntax found at:
https://developers.google.com/drive/web/handle-errors
This unfortunately will not solve the errors, the errors we received were in how we were parsing the error that google sent back. So this should allow us to see the real error next runthrough

Great job Michael!


fix npx can not find playwright module

also can you fix the readme quickly? it reads "debugtopus" in the run command instead of "@octomind/debugtopus"


Favicon

It's working!
Now it just needs to be a little bit bigger...

I've head good luck with http://realfavicongenerator.net/.

@jacebrowning I am not sure why it is still appearing so small I made the file size 48px x 48px

It now looks much better! @jacebrowning

This is what it looks like for me:

It's still quite a bit smaller than other favicons. What do you think?

@jacebrowning this is how mine appears.

I am not seeing a favicon.

@Allen616 What browser are you viewing it in? Could you snap a screenshot?

Here's a report of multiple browsers: http://realfavicongenerator.net/favicon_checker?protocol=https&site=citizenlabsgr-homepage-pr-21.herokuapp.com%2F

Just found that! I am going to update the code and see if this helps! Good find!

@Allen616 @jacebrowning Can you review from your side to see if this last commit has worked?

Works for me...


Uninstalling MacForge - reversing changes made to MacOS

I installed MacForge and it instructed me to make some changes to my system (partially disabling system integrity protection). I started following the steps but then I realized I was in over my head - I am not a programmer and I don't want to cripple my system's built in security just to install an app.
However, there are no instructions anywhere on how to reverse these changes made in Terminal. Since I followed some of the steps, my OS is now compromised and I don't know how to undo this. I believe there should be instructions for this for the non-programmers like myself (probably in the Uninstall article which mentions nothing about this).

The wiki has been updated with info to re-enable System Integrity
https://github.com/MacEnhance/MacForge/wiki/Uninstallation


Add Time feature (aesthetic/productive)

Add a thing so we can add time of the day for every habit so I don't have to write after every habit myself.

Plus
It would be cool if the app sends you reminder on that specific habit time.
And yeah I really like the minimalistic approach so try to keep it that way :)
Thanks
Sam

@ofalvai please consider this feature request 🙏 thank you 🙂

Yep, I would also like to have reminders in app. It would make this app almost perfect for me. I will try to see if I can implement it in reasonable time during my weekends.


No webapp on future3

Describe your problem
Webapp does not appear.
What's your hardware set up?
RPi 3 B+
CMD output:
pi@MusicPi:~/RPi-Jukebox-RFID/src/webapp $ npm run build

><EMAIL_ADDRESS>build
> react-scripts build

Creating an optimized production build...

<--- Last few GCs --->

[721:0x5943638]   373029 ms: Mark-sweep (reduce) 226.1 (236.8) -> 225.4 (236.8) MB, 4835.0 / 0.3 ms  (average mu = 0.171, current mu = 0.040) allocation failure scavenge might not succeed
[721:0x5943638]   377912 ms: Mark-sweep (reduce) 226.3 (237.0) -> 225.6 (237.3) MB, 4843.4 / 0.3 ms  (average mu = 0.094, current mu = 0.008) allocation failure scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

I've run the commands manually from the install script:
cd ${INSTALLATION_PATH}/src/webapp
npm ci --prefer-offline --no-audit --production
rm -rf build
npm run build

The install script did fail as well.
I will set this option and try again 😊

I updated the UI lib to the most recent version just before release and boom: that issue started to occur on my RPi 3+ as well.
That's why I added the NODE_OPTIONS within the install script. Maybe it does not set it right. I  briefly added a log output.
https://github.com/MiczFlor/RPi-Jukebox-RFID/blob/02d5fe89f880e607b2e7464dd9b3fe4846e860a6/installation/install-jukebox.sh#L296-L306
If you don't mind, you could retry the procedure. If it fails again, you could check the INSTALL_XXX.log file and report which options was set during the installation. Chose the development branch options during install. The commit has not been merged to the release branch yet.
Could you be a bit more specific about your SD card

With the ENV variable building the Webapps was successful.
I will try a new installation from a fresh Raspbian. Let's see if this works


Update Get-CsUserDelegates.md

First draft version released for SFB Server 2019 CU1 release.

Docs Build status updates of commit 2e1af36:
:clock10: Full build: the average full build time is 11 min(s) 55 sec(s), this is based on the last 806 build(s) for this repository.

Docs Build status updates of commit 2e1af36:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsUserDelegates.md
:white_check_mark:Succeeded
View (skype-ps)

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

Docs Build status updates of commit 3db03c5:
:clock10: Full build: the average full build time is 11 min(s) 54 sec(s), this is based on the last 814 build(s) for this repository.

Docs Build status updates of commit 3db03c5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsUserDelegates.md
:white_check_mark:Succeeded
View (skype-ps)

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


🎨 Create Home Page Overview Section

Description
I have created and styled the overview section to meet the required design.
Fixes #4
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Screenshot (optional)
Laptop

Tablet

Mini Tablet

Phone

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas

Good attempt but this issue has been closed . Please pick another open issue. Hint; don't delete code already in a file when working on it.


data-placeholder not working when add ng-options & ng-model

I have this
<select multiple chosen class="chosen-select"
      ng-model="selectedOption"
      ng-options="emp as emp.fullname for emp in employees track by emp.uuid"
      data-placeholder="Select an employee"
</select>

and the select displays the default "Select Some Options"
Thanks!

I think I have resolved this by commenting this line (90). But I don't know if it's needed for another purpose. For my, is working ok without it:
updateMessage = function() {
    if (chosen && empty) {
        element.attr('data-placeholder', chosen.results_none_found).attr('disabled', true);
    } else {
        //element.removeAttr('data-placeholder');
    }
    return element.trigger('chosen:updated');
};

https://github.com/leocaseiro/angular-chosen/issues/205

Thanks @leocaseiro !


Please mention somewhere that construction parameters should not be declared on Job class

Took me a while before I figured out that this does not work :
class SendEmailJob extends AbstractQueuedJob {
    public $to = ''; // don't do this
    private $subject = ''; // don't do this either
    public function __construct($to =<EMAIL_ADDRESS>$subject = 'Queued Email') {
        $this->to = $to; // just do this
        $this->subject = $subject; //and this
        $this->currentStep = 0;
        $this->totalSteps = 1;
    }
}

It does, but yes, it should be made clearer that if you do want to use constructor arguments,
a) they must have default parameters, as the JobService will re-create the job class passing through no constructor params
b) you must have logic in your constructor that can determine if it's been constructed by the job service, or by user-land code, and whether the constructor params are to be used.
The kind of logic to use in your constructor could be something like
public function __construct($to = null) {
	if ($to) {
		// we know that we've been called by user code, so
		// do the real initialisation work
	}
}

Of course, the other alternative is to set properties on the job directly after constructing it from your own code.

Actually, this was mentioned in the wiki, but I've made it a bit clearer, and referenced it from the README file

@nyeholt thanks for somewhat clarifying this, but where exactly can I put the parameters passed in to the constructor of the job in order to persist / make this information available to the running of it across multiple steps?
For example public function __construct($startDate = null, $endDate = null). I want the start and end dates available in the process() function.
Is there something built in to the queued jobs to do this, or will I have to think up my own way of storing the parameters (in DB or file) and then loading them back in the setup() function?
Any guidance you can give on this would be greatly appreciated.
Thanks.

I've made it a little clearer in the wiki page, and copy / pasted below
Job Properties QueuedJobs inherited from the AbstractQueuedJob have a default mechanism for persisting values via the __set and __get mechanism that stores items in the jobData map, which is serialize()d between executions of the job processing. All you need to do from within your job is call $this->myProperty = 'somevalue';, and it will be automatically persisted for you; HOWEVER, on subsequent creation of the job object (ie, in the __constructor()) these properties have not been loaded, so you cannot rely on them at that point.


Interaction Verification Solidity Contract

Ticket: Interaction Verification Solidity Contract
Title: Solidity Contract for Interaction Verification
Description: Develop a Solidity contract to handle interaction verification on the "Vibe to Earn" platform. Interactions are verified through QR code scans. The contract should provide a function for users to submit a QR code scan (interaction) that includes the event ID and the attendee’s wallet address.
Acceptance Criteria

Contract Deployment

The contract should be deployable on the Ethereum blockchain.

The contract should initialize with zero interactions recorded.

QR Code Interaction Submission

Users must be able to submit a QR code scan (interaction).

Each interaction must include the event ID and the attendee’s wallet address.

The contract should store interactions securely.

Interaction Validation

The contract should validate the interaction to ensure it includes a valid event ID and wallet address.

Duplicate interactions for the same event and attendee should be prevented.

Admin Functions

Only the admin should be able to manage event IDs and interaction data.

The admin should be able to review and manage interactions if necessary.

Events

Events should be emitted for each QR code interaction submission and validation.

Solidity Contract

// SPDX-License-Identifier: MIT

pragma solidity ^0.8.0;

contract InteractionVerification {

    struct Interaction {

        uint eventId;

        address attendee;

        bool isValid;

    }

    address public admin;

    uint public interactionCount;

    mapping(uint => Interaction) public interactions;

    mapping(uint => mapping(address => bool)) public eventAttendees;

    event InteractionSubmitted(uint interactionId, uint eventId, address attendee);

    event InteractionValidated(uint interactionId, uint eventId, address attendee);

    modifier onlyAdmin() {

        require(msg.sender == admin, "Only admin can perform this action");

        _;

    }

    constructor() {

        admin = msg.sender;

        interactionCount = 0;

    }

    function submitInteraction(uint _eventId) public {

        require(!eventAttendees[_eventId][msg.sender], "Interaction already submitted for this event");

        interactionCount++;

        interactions[interactionCount] = Interaction({

            eventId: _eventId,

            attendee: msg.sender,

            isValid: true

        });

        eventAttendees[_eventId][msg.sender] = true;

        emit InteractionSubmitted(interactionCount, _eventId, msg.sender);

        emit InteractionValidated(interactionCount, _eventId, msg.sender);

    }

    function validateInteraction(uint _interactionId) public view returns (bool) {

        Interaction memory interaction = interactions[_interactionId];

        return interaction.isValid;

    }

    function invalidateInteraction(uint _interactionId) public onlyAdmin {

        interactions[_interactionId].isValid = false;

    }

    // Function to get interaction details

    function getInteraction(uint _interactionId) public view returns (uint eventId, address attendee, bool isValid) {

        Interaction memory interaction = interactions[_interactionId];

        return (interaction.eventId, interaction.attendee, interaction.isValid);

    }

}

Test Cases

Deployment:

Deploy the contract and verify the admin, interactionCount, and initial state of interactions.

QR Code Interaction Submission:

Submit a new interaction with a valid event ID.

Verify the interaction is stored with the correct event ID and attendee's wallet address.

Emit InteractionSubmitted and InteractionValidated events.

Interaction Validation:

Validate an interaction to ensure it is marked as valid.

Prevent duplicate interactions for the same event and attendee.

Admin Functions:

Invalidate an interaction and verify its status is updated.

Ensure only the admin can perform interaction invalidation.

Events:

Emit appropriate events for interaction submission and validation.

Edge Cases:

Test behavior when attempting to submit duplicate interactions for the same event and attendee.

Ensure the contract handles multiple interactions and validations correctly.

Verify no unauthorized users can invalidate interactions.

points: 1, 2, 3, 5, 8, 13, 21
@russlive215
@Fr0z0n3
@noireconnect2024
@wvwatson
points:


Stop triggering event for deleted keys

CI is borked because it relies on the original quickwit-builder Docker image t_t


python310Packages.pyunifiprotect: 4.0.11 -> 4.0.12

Description of changes
https://github.com/briis/pyunifiprotect/releases/tag/v4.0.12

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 185807 run on x86_64-linux 1

4 packages built:

home-assistant-component-tests.unifiprotect
python310Packages.pyunifiprotect
python39Packages.pyunifiprotect
unifi-protect-backup


When pickling compiled templates, open file as binary for writing.

This is consistent with the unpickling operation where the file is
opened as binary, and without this change, under Windows, unpickling
fails.  This change does not seem to have negative implications for
Linux.

Should be ok for Linux too, thanks


Exceptions passed over the wire to clients must not reference server types

Currently the EntityConfigurationException constructed on the server has its cause set to the original ConfigurationException (which is only available on the server classpath).  We should avoid situations like this where objects sent over the wire reference types only available on the classpath of the server.  In this case we discussed this and think it's best if rather than chaining the original exception as a cause we instead reskin the original ConfigurationException as an EntityConfigurationException.  Maybe we could just do this via a writeReplace method?

It sounds like the writeReplace approach should work.  I suspect that we want to replace any exceptions on the server with some sort of "ServerSideExceptionWrapper", or something, so that it doesn't matter what the user code is doing or what other types it might use.
I will experiment with this and see if I can come up with something nice.

This will be handled purely on the API-side, related to how the exceptions are serialized:  Terracotta-OSS/terracotta-apis#190


arch(arm64_32) is not recognized by swiftc

This line emits a warning:
https://github.com/apple/swift-atomics/blob/df9f811f19a852fa7b78af9cffa8ec447eaeb40a/Sources/Atomics/AtomicStrongReference.swift#L82
warning: unknown architecture for build configuration 'arch'

According to TSPL, only i386, x86_64, arm and arm64 are supported.

This enables the package to be used in watchOS apps built with Xcode. (https://bugs.swift.org/browse/SR-13709)
We could replace the arch(arm64_32) condition with os(watchOS), but that feels even further away from the thing this is intended to query. Perhaps we can replace the compile-time condition with a runtime check for Int.bitWidth.

This enables the package to be used in watchOS apps built with Xcode. (https://bugs.swift.org/browse/SR-13709)
We could replace the arch(arm64_32) condition with os(watchOS), but that feels even further away from the thing this is intended to query. Perhaps we can replace the compile-time condition with a runtime check for Int.bitWidth.

Until the compiler side problem is fixed (it seems like a big task from a cursory look), would it make sense to add a comment here with the JIRA number and having the os(watchOS) with an explanation that ideally it ought to be arch(arm64_32)? If we do that, then folks trying to compile the package don't have to see the warning, at the cost of some non-ideal configuration in the implementation.

Until the compiler side problem is fixed (it seems like a big task from a cursory look), would it make sense to add a comment here with the JIRA number and having the os(watchOS) with an explanation that ideally it ought to be arch(arm64_32)? If we do that, then folks trying to compile the package don't have to see the warning, at the cost of some non-ideal configuration in the implementation.

My worry is that such workarounds have a tendency of remaining in the codebase long after they're obsoleted by platform/compiler changes.
However, if Int.bitWidth == 32 seems like an excellent way to get rid of the warning while also preventing any and all future platform issues -- and also greatly improving readability. (The package is already heavily relying on constant folding/dead code elimination, so this is unlikely to be a big deal.)

My worry is that such workarounds have a tendency of remaining in the codebase long after they're obsoleted by platform/compiler changes.
However, if Int.bitWidth == 32 seems like an excellent way to get rid of the warning while also preventing any and all future platform issues -- and also greatly improving readability. (The package is already heavily relying on constant folding/dead code elimination, so this is unlikely to be a big deal.)

armv7k and arm64_32 slices of watchOS code have to be bitcode-compatible, so can we actually have behavior that diverges based on compiler target here?

armv7k and arm64_32 slices of watchOS code have to be bitcode-compatible, so can we actually have behavior that diverges based on compiler target here?

However, if Int.bitWidth == 32 seems like an excellent way to get rid of the warning while also preventing any and all future platform issues -- and also greatly improving readability. (The package is already heavily relying on constant folding/dead code elimination, so this is unlikely to be a big deal.)

That is also a good workaround IMO, certainly clearer than the os(watchOS). 👍🏼

However, if Int.bitWidth == 32 seems like an excellent way to get rid of the warning while also preventing any and all future platform issues -- and also greatly improving readability. (The package is already heavily relying on constant folding/dead code elimination, so this is unlikely to be a big deal.)

That is also a good workaround IMO, certainly clearer than the os(watchOS). 👍🏼

@jckarter AFAICT all of the approaches (including the original code) maintain that invariant. Do you see an issue I'm not seeing?

@jckarter AFAICT all of the approaches (including the original code) maintain that invariant. Do you see an issue I'm not seeing?

I was responding more to Varun's comment about why arch(arm64_32) might not be supported, since conditional compilation that leads to divergent armv7k/arm64_32 behavior isn't really feasible for watchOS.

I was responding more to Varun's comment about why arch(arm64_32) might not be supported, since conditional compilation that leads to divergent armv7k/arm64_32 behavior isn't really feasible for watchOS.

arch(arm64_32) is supported by the toolchains distributed in Xcode, and because it's disjunct from arch(arm), Swift packages that support watchOS sometimes need to mention it -- otherwise they'd have divergent behavior between watch platforms.
The swift.org toolchains don't support compiling code for arm64_32. This is fine, as watchOS apps are expected to get compiled with the proprietary toolchains. However, the open-source compilers also emit a pointless diagnostic whenever they come across arch(arm64_32), which makes the life of cross-platform package developers a tiny bit more difficult. It doesn't help that the diagnostic triggers even in inactive code:
func foo() {
  #if false
  #if arch(arm64_32) // warning: Unknown architecture for build configuration 'arch'. Did you mean 'arm64'?
  print("Hello, arm64_32")
  #endif
  #endif
}

arch(arm64_32) is supported by the toolchains distributed in Xcode, and because it's disjunct from arch(arm), Swift packages that support watchOS sometimes need to mention it -- otherwise they'd have divergent behavior between watch platforms.
The swift.org toolchains don't support compiling code for arm64_32. This is fine, as watchOS apps are expected to get compiled with the proprietary toolchains. However, the open-source compilers also emit a pointless diagnostic whenever they come across arch(arm64_32), which makes the life of cross-platform package developers a tiny bit more difficult. It doesn't help that the diagnostic triggers even in inactive code:
func foo() {
  #if false
  #if arch(arm64_32) // warning: Unknown architecture for build configuration 'arch'. Did you mean 'arm64'?
  print("Hello, arm64_32")
  #endif
  #endif
}


Update README.md for safe-apps-web3modal

The requestProvider method should be called instead of the connect method.

Спасибо!


Request: Fix Ring of Pyromania; doesn't trigger from Metamagic: Elemental Spell (Fire)

Was excited for my Winter Witch to proc Elemental Barrage and to deal some bonus Fire damage from items by converting 50% of all my spell damage to fire however initial testing doesn't show any bonus damage from Ring of Pyromania.
I tested:

Ice Spears + Elemental Spell (50% Fire)
Vampiric Touch + Elemental Spell (50% Fire) + Frozen Caress

Both spells worked perfectly otherwise. Is it because they don't have a Fire descriptor? (My research had indicated that this item was "damage inflicted" not "spell type cast". Haven't tested with other scenarios like 100% fire.

Follow up question: is "Elemental Spell" applied after "Elemental Bloodline"? If I take Elemental Bloodline (Water) to change a spell (Chain Lightning) into ice damage can I think apply Elemental Spell (Fire) to change 50% of the damage to Fire (and hence proc Elemental Barrage)? Because I hope so!


How to control ETS2 and emulate steering wheel in Windows?

Hi all! How to control ETS2 and emulate steering wheel in Windows?

Windows is not supported yet. But it's on our roadmap and i feel like i should work on it sooner or later.

Hi!
Can I install it on Windows 10 with subsystem for Linux? Is it possible to do that?


Allow a specified address to disable/enable the Exchange

Description
For purposes of Baklava, we might need to periodically turn the Exchange off. This PR adds freeze and unfreeze functions to the Exchange, allowing an address specified at migration time (and modifiable via setFreezer) to disable the exchange function.
Tested
Unit tests.
Other changes
This PR adds a new helper contract, Freezable, that specifies a freezer address and provides modifiers to disable certain contract functions if the contract becomes "frozen".
This is in anticipation of a similar change needed in LockedGold.
Related issues

Begins to address #1431

Backwards compatibility
Not backwards compatible, changes Exchange storage layout.

Did you mean to re-assign to me?


Processor client

I see all the tests are working except the ones where you pass numThreads as a parameter.
@JoshLove-msft Could you please check these 2 tests Receive_Event(int numThreads) and Receive_Event_Consumes_All_Messages(int numThreads)?

I see all the tests are working except the ones where you pass numThreads as a parameter.
@JoshLove-msft Could you please check these 2 tests Receive_Event(int numThreads) and Receive_Event_Consumes_All_Messages(int numThreads)?

They are working locally. I will a timeout for the tests to avoid hanging entire run. How can you tell that these tests are failing? Are they failing for you locally?

They are working for me locally. I will a timeout for the tests to avoid hanging entire run. How can you tell that these tests are failing? Are they failing for you locally?

Sorry, I wasn't clear before. I meant the above 2 tests are hanging for me locally, not failing.


Theme submission: Tokiwa

Theme submission
Please make sure that you have read the theme submission guidelines before submitting a theme. The guidelines provide all relevant information and requirements that have to be fulfilled before the submission. Please tick the relevant boxes for your theme in the checklist below:
Link to my theme repository: https://github.com/heyeshuang/hugo-theme-tokiwa
I made sure that...

[x] the repository contains a good README.md describing my theme
[x] an open source license has been added to LICENSE.md
[x] all metadata have been added to theme.toml
[x] screenshots have been added in the images/ folder with the required dimensions
[x] in case I'm using a customized demo via the exampleSite folder that

[x] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
[x] I tested that my theme's demo works with the content directory of gohugoio/HugoBasicExample

[x] I tested my theme against the gohugoio/HugoBasicExample

[x] I've checked the developer tools' console in my browser for error messages

[x] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

N.B. By submitting a theme to the Hugo Themes Showcase you understand that you need to maintain your theme. You will need to keep an eye on whether your theme's demo generates on the Hugo website, whenever there is a new release. We are a very small team and we just cannot keep up opening issues in the various theme repositories to notify authors. Whenever a theme demo breaks and remains broken then at some point it will be removed from the list without prior warning. If you no longer wish to maintain a theme please let us know.
New themes will usually be promoted on Hugo's official Twitter account. If you would like to be mentioned in the tweet please add your Twitter username to this submission.
Link to my Twitter account (optional): https://twitter.com/heyeshuang
Feel free to ask questions. We're glad to help.

About the git repo size
Some Chinese web fonts are used in this theme, and they are much bigger (~13 MB in total) than fonts for Latin. If Chinese characters are absent, loading fonts can be disabled in config.toml.

@heyeshuang
First of all write in the README that this theme is a fork of the hugo-starter-theme and link to its GitHub repository: https://github.com/jimfrenette/hugo-starter
Second give proper credit to the original author in theme.toml. Use the original table and fill out all required fields.
Third and more important. The hugo-starter theme uses an MIT LICENSE.
The MIT is a permissive LICENSE that has one important requirement:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

Meaning you have to keep the original unaltered copyright notice in all future distributions of the software.
You have switched to the GPL 3 LICENSE for the theme but you have to retain the original MIT LICENSE copyright notice.
The MIT can be combined with the GPL v3 -see here for more info
However after line 675 of the GPL 3  LICENSE you must add the original MIT copyright notice:
MIT LICENSE (click to see)
This theme incorporates work covered by the following copyright and
permission notice:
Copyright (c) 2019 Jim Frenette
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

On a final note I really think that you should mix the GPL 3 with the MIT only if you have very good reason.
I would prefer it if you released the Tokiwa theme under the MIT license and just add your name under Jim Frenette's name like so:
The MIT License (MIT)

Copyright (c) 2019 Jim Frenette
Copyright (c) 2020 Heyeshuang (or whatever your real name is)

<--- the rest of the MIT LICENSE goes here -->

After you do the above let me know so that I can test the theme with the Hugo themes Build Script.

Okay, fixed. Although I like GNU, I find GPL not suitable for a theme.

@heyeshuang
Why are you crediting all these people?
Copyright (c) 2020 He Yeshuang Copyright (c) 2014 Steve Francia Copyright (c) Adam Wathan<EMAIL_ADDRESS>Copyright (c) Jonathan Reinink<EMAIL_ADDRESS>Copyright (c) 2019 Tailwind Toolbox Copyright (c) 2019 Jim Frenette

You do not need to credit the Hugo creator (Steve Francia). You are using the software but you have not modify it. Steve should not be credited as an author of the theme.
As for the creators of the TailwindCSS framework again you are using it as an asset, you do not redistribute it or have modify it. So again you need to include the TailwindCSS creators as authors of the theme.
As I said above you only need to include the following:
The MIT License (MIT)

Copyright (c) 2020 He Yeshuang
Copyright (c) 2019 Jim Frenette

As I have entered it above. Meaning first line your name then second line the name of the original theme's author.
No other names.
Once you do this let me know, so that we can finally put the licensing issues behind us for good.
I will test your theme further next weekend and give you detailed feedback.

Hello @onedrawingperday ,
I credit Steve Francia because I introduce hugoBasicExample and modded its config.toml in exampleSite.
And for tailwindCSS, I found a note in the MIT license:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

The app.css file is partly clipped(or copied) from tailwindCSS by webpack.
Parts of these two repositories are included in my theme, without difference from hugo-starter-theme, so I'm not clear why they don't need to be in that license.
In case I misunderstand the MIT license or what, please let me know.

The LICENSE is about the authorship of the THEME.
The hugoBasicExample is a SAMPLE Hugo project  that illustrates how the demo content should be organized for the Hugo Themes website.
TailwindCSS is a THEME ASSET that may change in the future, whenever you decide that you no longer want to keep using that framework.
You are already giving credit to Tailwind CSS, hugoBasicExample and other assets in the README, so my opinion is that it is not needed to also include these credits in the actual LICENSE.
However if you feel that you have to include these credits then go ahead..
I am not a legal expert. But whenever you decide to change framework you will have to remove the copyright notice to TailwindCSS from the LICENSE.

On another note.
The default language of the demo config needs to be in English since the content on the Hugo Themes website is meant for an international audience.
You need to provide translations by using https://gohugo.io/functions/i18n/#readout and calling these strings in the templates so that users can modify them easily according to their own language.
You should not hardcode strings in the templates in Mandarin.
You need to remove exampleSite/configTaxo.toml this file is needed only for the Hugo Themes website and it has no place in your theme's exampleSite.
You also need to remove /exampleSite/content/homepage since this also not be needed by your theme demo.
Let me know once you push changes to the repo.

Fixed. There are some Mandarin strings not hard-coded but placed in the config.toml only to show the font. And now they are removed.
By the way, thanks for your patience.

I will not handle this submission further. My available time has been exhausted. Also I am muting this topic, because I cannot be further disturbed.
cc: @digitalcraftsman

@heyeshuang I'll be to continue the review of your theme on Monday.

Thank you for applying the requested changes. In the example config file I noticed that the social media links all refer to a user named hh. On some platforms this username is actually in use. In order to keep the demo content neutral please use an url like github.com/ instead of github.com/hh.

Okay, fixed that.

Your theme should appear soon on Hugo's theme site. Next, I'll promote your theme on Hugo's official Twitter account.

Thank you!


Add ProjectionPursuit (new PR)

Codecov Report

Merging #141 (ae12985) into master (a075bb8) will decrease coverage by 4.44%.
The diff coverage is 53.06%.

@@            Coverage Diff             @@
##           master     #141      +/-   ##
==========================================
- Coverage   94.71%   90.26%   -4.45%
==========================================
  Files          26       27       +1
  Lines         795      894      +99
==========================================
+ Hits          753      807      +54
- Misses         42       87      +45

Impacted Files
Coverage Δ

src/transforms.jl
100.00% <ø> (ø)

src/transforms/projectionpursuit.jl
53.06% <53.06%> (ø)

src/transforms/scale.jl
100.00% <0.00%> (+5.55%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Hi @juliohm
I already changed to \cdot notation, checked that the diag function really gives a unitary vector and got rid of some outdated notation.
But when I tried to change the plots in the visual test, they didn't get plotted all too well:

One of the possible changes would be to modify the gr settings to change the size of the image, but even so the graphics at the diagonal keep coming out as lines (just like in the images above), so for now I just did the test with each corner separately and will continue checking the problem of the diagonals.

I already changed to \cdot notation, checked that the diag function really gives a unitary vector and got rid of some outdated notation.

That is great @DianaPat , now we can remove the normalization of alpha inside the rscore function, and only normalize it in the neadermead step. I will propose the changes so that you can review and accept.

But when I tried to change the plots in the visual test, they didn't get plotted all too well:

Let's just plot the result of the corner plot after the transformation in one figure and the result of reverting the transformation in a separate figure. They don't need to be in the same figure. Also, you can pass the option size=(800,800) to the specific plot commands to overwrite the default size set in the gr command.

Hi @DianaPat can you please double check that this GitHub option is enabled on this PR?
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork
I fixed the problem locally and would like to push the changes to the PR.

It is enabled

Hi @DianaPat it is saying that permission is denied. Can you incorporate the fixes in your local copy and regenerate the figures?

Remove the option aspectratio=:equal from the runtests.jl file and place it in every existing plot command that existed before in the test files. Basically, scale.jl, zscore.jl, eigenanalysis.jl, if I recall correctly.
Delete all png files in the test/data directory and rerun the tests to generate new figures.
You should see all corner plots correctly plotted now. The aspectratio option was the issue.

After you make the changes you will see that the projection pursuit result is not looking quite right yet. The final distribution is not spherical visually indicating that either the number of iterations wasn't enough or that some other bug is still hidden somewhere.

Yes, I'm already looking for this bug and other ones I've found. I'll update as soon as I find something!

Hi @juliohm, I think the error is fixed.
In fact the function was not comparing the data to a gaussian up to perc percentile, but with 1-perc. There was also an issue with just taking a higher percentile because the optim function raised an error. That part was just fixed with the float at line 93.
But then the tests stopped passing (at this point I'm wondering how did they pass before), so I relaxed the conditions.
At this point I think maybe it would be better to change all occurrences of perc to 1-perc in the code so we can keep the previous value, as it is more intuitive.

Hi @DianaPat thank you for checking it. Can you please move the float call to within the definition of the basis function? This function should return a floating point vector always to avoid type instability.
Regarding the percentile option, you mean that it is more intuitive to use the value .99? It would be great if you could make the appropriate changes. After that, it would be interesting to print the number of iterations of structure removal that are happening with the test cases. It seems that the structure is not quite Gaussian still? The point cloud has some borders that differ visually from a multivariate Gaussian.

I already made some experiments. Without any modification of parameters it runs the structure removal cycle 23 times. By changing the parameters a little, it reached 101 iterations; the problem is that it took aprox. 300 seg, so the tests would take more time.
I saved the figures to do a comparison of improvement:

I am finding it strange that the the points near the "tails" of the resulting distribution are somewhat spread. If you plot the ideal standard Gaussian you will be able to see the difference. Do you know how to use the VSCode debugger? You could add a plot command inside the structure removal loop and then add a breakpoint to see the plot at each iteration. Another thing you can do is check the optimal alphas as we did in class to see if everything is working as expected. Finally, a good diagnostic would be to plot the q-q plot of the transformed columns against the standard Gaussian to see if they pass through the identity line.

The tails diverge from a gaussian outside the interval [-3,3]. I double checked the removal structure function but it's working as expected.
I went back to the bibliography (Friedman pg 255) and found this:

When I tried increasing the deg argument, there was a slight improvement, but it came at the cost of time.

That is a very good catch. Can you comment on the time increase? Is it 2x
slower? How the plots look like with higher degrees? Can we find a good
compromise by default?
Em dom., 16 de out. de 2022 19:46, DianaPat @.***>
escreveu:

You are right!
The tails diverge from a gaussian outside the interval [-3,3]. I double
checked the removal structure function but it's working as expected.
I went back to the bibliography (Friedman pg 255) and found this:
[image: Tails_under]
https://user-images.githubusercontent.com/105749646/196061909-119106f3-f4c8-461f-a664-4cc8d7baff4b.PNG
When I tried increasing the deg argument, there was a slight improvement,
but it came at the cost of time.
—
Reply to this email directly, view it on GitHub
https://github.com/JuliaML/TableTransforms.jl/pull/141#issuecomment-1280074599,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZQW3MAVSGX4ULX2O5SD7TWDSAUBANCNFSM6AAAAAAQZXLHKQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

The time increase is ~3.5x:
With deg=5 it took around 16 sec to obtain the answer (image on the left), and with deg=30 it took 352 sec (image on the right)

Thank you @DianaPat for these careful checks. I agree with you that the time cost does not pay off, and we just need to be aware of this behavior near the tails.
I will try to review the PR one more time during the day. It would be important to plot the transformed and reversed data for both data sets if that is not already done.

That is really awesome @DianaPat. I think we finally made it! 🎉 Congrats!
One additional change we could implement to avoid depending on the heavy Optim.jl package is replace it with the NelderMead.jl package, which only implements the algorithm are currently using: https://github.com/jwscook/NelderMead.jl
You can learn more about the algorithm in this lecture: https://youtu.be/vOYlVvT3W80 It is beautiful and simple idea.
In theory, we would just need to replace the Optim.optimize function by the NelderMead.optimise function and rerun the tests. If you feel that you have some time to try this out, please go ahead. Otherwise, I invite you to review the original PR you submitted to compare how much you improved your coding skills in the process 👏🏽
These picky reviews pay off in the long run, and I am really happy you went all the way to the end! 🥇

Thank you, I learned a lot from this experience!
On the other hand, I tried to implement the change of package, but it seems that the autor have not registered the package, so I couldn't do it. For now will leave it as is while I look for other alternatives.

I've opened an issue requesting registration: https://github.com/jwscook/NelderMead.jl/issues/5

@DianaPat NelderMead.jl is now registered 👌🏽 would you like to give it a try here to see if the results are the same?


Add rbmods / rockmods provider

Update Me checks updates by scraping websites, downloading APKs, extracting APK info, and sending it to VirusTotal for analysis.
Unfortunately, Rock Mods can't be added due to the complexity of data scraping. The download links are indirect, often from external sources, and the navigation involves captchas, which our scraping bot currently doesn't support.


Add Alfredo Deza

Adds the yaml profile and the 400x400 profile picture

Docs Build status updates of commit 3054ebb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/alfredo-deza.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/alfredo-deza.png
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Fixing issues faced on dockerizing the-app

Updated Akka configuration to use IPv4.
Updated 3.4 version of MongoDB in docker-compose.yml to avoid error “The 'cursor' option is required, except for aggregate with the explain argument" , "code" : 9 , "codeName” at linked docker containers.

Thanks @shivaprasadlk - looks good to me


row column must be always in the same order in functions

const out = new IJS(2, 3); row is the second param (height)
image.setValue(); row is the first param

Are there other function than setRow/getRow and setPixel/getPixel which have row as the first param?

i think it's better to have height as the first param in the constructor

I'm not sure about that. In possible all other software, image dimensions are referenced in the opposite order (width, height).

We will change the implementation in order to call the parameters in the order column, row. This will also make the API more similar to the old image-js.