Add internal/inputs package and rewrite tsbs_generate_data

For a long time, our two generation binaries -- tsbs_generate_data
and tsbs_generate_queries -- have shared (roughly) a fair bit of
code, especially when it comes to flags and validation. However,
they were never truly in sync and combining them has been a long
wanted to-do. Similarly, to enable better tooling around TSBS, it
would be beneficial if more of its functionality was exposed as a
library instead of a CLI that needs to be called.
To those ends, this PR is a first step in addressing both of them.
It introduces the internal/inputs package, which can eventually be
moved to pkg/inputs when we are ready for other things to consume
its API. This package will contain the structs, interfaces, and
functions for generating 'input' to other TSBS tools. For now, that
only includes generating data files (for tsbs_load_* binaries) and
query files (for tsbs_run_queries_* binaries). This PR starts by
introducing these building blocks and converting tsbs_generate_data
to use it.
The idea is that each type of input (e.g., data, queries) is handled
by a Generator, which is customized by a GeneratorConfig. The config
contains fields such as the PRNG seed, number of items to generate,
etc, which are used by the Generator to control the output. These
GeneratorConfigs come with a means of easily adding their fields
to a flag.FlagSet, making them work well with CLIs while also not
restricting their use to only CLIs. Once configured, this
GeneratorConfig is passed to a Generator, which then produces the
output.
This design has a few other nice features to help cleanup TSBS.
One, it uses an approach of bubbling up errors and passing them
back to the caller, allowing for more graceful error handling. CLIs
can output them to the console, while other programs using the
library can pass them to another error handling system if they
desire. Two, Generators should be designed with an Out field that
allows the caller to point to any io.Writer it wants -- not
just the console or a file.
The next step will be to convert tsbs_generate_queries to use this
as well, which will be done in a follow up PR.

Codecov Report

Merging #64 into master will increase coverage by 0.58%.
The diff coverage is 84.09%.

@@            Coverage Diff             @@
##           master      #64      +/-   ##
==========================================
+ Coverage   51.58%   52.17%   +0.58%
==========================================
  Files          73       75       +2
  Lines        3586     3590       +4
==========================================
+ Hits         1850     1873      +23
+ Misses       1720     1697      -23
- Partials       16       20       +4

Impacted Files
Coverage Δ

internal/inputs/generator.go
58.82% <58.82%> (ø)

internal/inputs/utils.go
63.15% <63.15%> (ø)

internal/inputs/generator_data.go
90% <90%> (ø)

Continue to review full report at Codecov.

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


Check for conflict with bootstrap navbar because of z-index

We could maybe have the same problem:
https://github.com/voronianski/ngprogress-lite/pull/18

HI @dasois is this still required?

The z-index in ngprogress is already high in the default CSS, so I don't think this would be a problem. Also, users could also override the styling in their own codebase if required.
I will close this issue base on the above. Re-open if you think necessary.


Question:The old plugin always inserts the css file at the top of the head tag.

The old plugin always inserts the css file at the top of the head tag, and the following is the style that I refer to by other ui components. I often need to override their style, but the old plugin always compiles the .st.css file. Generated css inserted to the top

@barak007

Just to clarify,
the new integration puts the bundled CSS before any other custom stylesheets? would you like it to be after?
Is this project open so we can see it? or can you provide the configuration you use?

rules: [
      {
        oneOf: [
          StylablePlugin.rule(),
          {
            test: /\.tsx?$/,
            exclude: /node_modules/,
            use: [
              { loader: "cache-loader" },
              // {
              //   loader: "thread-loader",
              //   options: {
              //     // there should be 1 cpu for the fork-ts-checker-webpack-plugin
              //     workers: require("os").cpus().length - 1
              //   }
              // },
              { loader: "react-hot-loader/webpack" },
              {
                loader: "ts-loader",
                options: {
                  // transpileOnly: true,
                  happyPackMode: true, // IMPORTANT! use happyPackMode mode to speed-up compilation and reduce errors reported to webpack
                  getCustomTransformers: () => ({
                    before: [
                      tsImportPluginFactory({
                        style: true
                      })
                    ]
                  }),
                  compilerOptions: {
                    module: "esnext"
                  }
                }
              }
            ]
          },
          {
            test: /\.less$/,
            oneOf: [
              {
                use: [
                  {
                    loader: "style-loader"
                  },
                  {
                    loader: "css-loader",
                    options: {
                      sourceMap: true
                    }
                  },
                  {
                    loader: "less-loader",
                    options: {
                      javascriptEnabled: true,
                      modifyVars: theme,
                      sourceMap: true
                    }
                  }
                ]
              }
            ]
          },
          {
            test: /(?!\.st)\.css$/,
            use: [
              {
                loader: "style-loader"
              },
              {
                loader: "css-loader",
                options: {
                  sourceMap: true
                }
              }
            ]
          },

          {
            test: /\.(jpe?g|png|gif)$/i,
            use: [
              {
                loader: "file-loader",
                options: {
                  hash: "sha512",
                  digest: "hex",
                  name: "[hash].[ext]"
                }
              },
              {
                loader: "image-webpack-loader",
                options: {
                  query: {
                    mozjpeg: {
                      progressive: true
                    },
                    gifsicle: {
                      interlaced: false
                    },
                    optipng: {
                      optimizationLevel: 4
                    },
                    pngquant: {
                      quality: "75-90",
                      speed: 3
                    }
                  }
                }
              }
            ]
          }
        ]
      }
    ]

The above code is my configuration, I tried a variety of orders, but the StylablePlugin is always the first time to insert main.css into the html head tag. And when I change the order, I will also report various errors. For example, the oneOf is necessary. I cannot write loaders directly in the rules.
@idoros

@idoros I tried to upgrade to webpack4 but some of the plugins are in conflict, so I went back to the original version later. If the new plugin can customize the placement, I'd certainly be happy to use it. I like the Stylable project very much, but I feel that it's a problem. There are too few people who contribute code, so there is no way to solve the problem.

First of all let me agree that the transition from Webpack v3 to v4 has been tough. but at the moment it seems that most of the ecosystem has moved on, and its incredibly hard to stay behind. So with no relation to Stylable, I recommend upgrading to v4.
We will be stopping support for our Webpack v3 integration in the near future, but even with the next version, I'm not sure I understand what you are trying to do. I see you are using Stylable, CSS modules, LESS and JSS. How are they "extending" each other or operate together?
I would love to help, but I need a working example of the project in order to see whats going on.
Can you describe your build pipeline flow? or provide a more extensive reference for your project?

@idoros
For reproduce this issue, I upload a simple project.
Step:

1 npm install
2  npm start

https://github.com/linmodev/reproduce/tree/master/StylableWebpackPlugin
Note:
This project has three webpack config files.

webpack.config.dev.js can work well.
webpack.config.dev2.js has some errors like under picture show.

webpack.config.dev3.js has some errors like under picture show.

I have to say that it is really troublesome to reproduce this problem

a few things to try:

your condition to filter out .st.css files seems broken. You can see in config.dev3 that the result stylesheet modules go through style-loader. try changing the options of style-loader to:

test: /\.css$/,
exclude: [/\.st\.css/]

the order of oneOf or Webpack rules have no affect on the order of result style/link tags. But style-loader has some options to control. Try changing 'inserAt' if you want Stylable to be after other generated CSS.

happy to help :)


Move scripts to litex-conda-ci submodule

This PR:

Moves all scripts to litex-conda-ci
Updates all paths in README
This PR should not be merged before https://github.com/litex-hub/litex-conda-ci/pull/1 , and bumping litex-conda-ci submodule.

Had to update one of the renode patches to make it pass. If it should be added as separate PR, please let me know.

As there was a change requested in litex-conda-ci this will be ready to merge after https://github.com/litex-hub/litex-conda-ci/pull/3 is merged.


Crash while performing redisClusterAsyncFree()

Hi, came across this crash during one of the runs.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007e36c41fe3a2 in selectNode (nodes=<optimized out>)
[Current thread is 1 (Thread 0x7e36b50b3a40 (LWP 21))]
(gdb) bt
#0  0x00007e36c41fe3a2 in selectNode (nodes=<optimized out>)
#1  updateSlotMapAsync (acc=acc@entry=0x58a8403266c0)
#2  0x00007e36c41fe598 in clusterSlotsReplyCallback (ac=<optimized out>, r=0x0, privdata=0x58a8403266c0)
#3  0x00007e36c420ce79 in __redisRunCallback (reply=0x0, cb=0x7fffa203cfc0, ac=0x58a84f4e8780)
#4  __redisAsyncFree (ac=0x58a84f4e8780)
#5  0x00007e36c420d645 in redisAsyncFree (ac=<optimized out>)
#6  0x00007e36c41f9e90 in freeRedisClusterNode (node=0x58a87df71bc0)
#7  0x00007e36c41f7c56 in _dictClear (ht=0x58a85c542180)
#8  dictRelease (ht=0x58a85c542180)
#9  0x00007e36c41fbfc6 in redisClusterFree (cc=0x58a84218b300)
#10 0x00007e36c41ff555 in redisClusterAsyncFree (acc=0x58a8403266c0)
### layers below called from application while shutting down.

Looks like the execution was at this line number when the crash happened
https://github.com/Nordix/hiredis-cluster/blob/a2f1b825dda8f1438bd0df93880185d1e879da99/hircluster.c#L3878
I am suspecting the reason for SEGV could be the below code area:
https://github.com/Nordix/hiredis-cluster/blob/a2f1b825dda8f1438bd0df93880185d1e879da99/dict.c#L179
where, even though we are freeing up the memory pointed by redisClusterNode*, we are not unlinking it from the table. Hence it gets looked up later on(during selectNode()), which would be a dangling pointer.
        if ((he = ht->table[i]) == NULL)
            continue;
        while (he) {
            nextHe = he->next;
            dictFreeEntryKey(ht, he);
            dictFreeEntryVal(ht, he);      // memory released, but entry not set to NULL, so ht->table holds a dangling pointer ?
            hi_free(he);
            ht->used--;
            he = nextHe;
        }

And also, other thing that looks odd is the library trying to reattempt discovery when the redisClusterAsyncContext object is getting deleted. Maybe we should prevent that path altogether, in case of redisClusterAsyncFree() where it's about to tear everything down anyways.
cc: @bjosv

I don't see that address being explicitly set to 0 after memory is freed. Do you agree with the analysis?

Posting some more thoughts,
selectNode() is trying to do a dictNext(). So, if we don't set the he object to NULL once we free it inside _dictClear(), any later dictNext() access might still think the entry as valid and try to process that.

maybe something in lines of:
    while (he) {
        nextHe = he->next;
   +    ht->tabl[i] = nextHe;
        dictFreeEntryKey(ht, he);
        dictFreeEntryVal(ht, he);
        hi_free(he);
        ht->used--;
        he = nextHe;
    }


Add showwcase icon in icons.md

What would you like to share?
Please add Showwcase icon, Showwcase is a network built for developers so it will be great if anyone adds the showwcase icon in icons.md we can add the showwcase icon in our linkfree also
If you want to checkout showwcase here is the link
Additional information
No response

Hi @hasnainmakada-99 , There is already an issue was created for the addition of showcase icon #1043 . Thank You :pray:

Ok @vikasganiga05 I'm closing this one


az vm {create,update} should block non-ASCII hostnames for Linux VMs

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

Describe the bug
Linux does not permit non-ASCII characters in hostnames, but neither az vm create nor az vm update blocks them. This will result in failure to create the VM (create) via OS Provisioning Timeout (OSPTO) and can cause a VM to become unbootable (update).
The Azure portal already blocks attempts to use non-ASCII hostnames for Linux VMs.
From the Linux documentation for hostname(7) - Linux manual page (man7.org):

Each element of the hostname must be from 1 to 63 characters long
       and the entire hostname, including the dots, can be at most 253
       characters long.  Valid characters for hostnames are ASCII
       letters from a to z, the digits from 0 to 9, and the hyphen (-).
       A hostname may not start with a hyphen.

To Reproduce

az vm create --name 'mapxu-test-name-乱写一些单词' using a Linux VM image.
Expected behavior

An error message should be issued.
Environment summary

Linux VM
Additional context

@zhoxing-ms for awareness


created basic response for edge cases and ties

#4

@Benjamin-Ung  could you handle the merge conflict?

#33 may be associated please confirm, merge and then close the issue if so.


Lock the shared resources when they are used

Purpose:
At the end of this pull request, a shared resource have to be locked before it can be used or modified. This issue prepares the future thread pool which will be implemented later.
Added features:

Lock the shared resources in the systems in the client's room

Warning:
From now on, each shared resource must be locked before being used or modified !
This will close #240

Codecov Report

Merging #254 (676bb08) into master (5954ff0) will increase coverage by 0.41%.
The diff coverage is 0.00%.

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


[RC2] web page flashes white blank on load

I just upgraded my project from RC1 to RC2 and now it has a strange behaviour. Everytime a new page is loading, the browser shows a white blank page for half a second (until the new page is loaded). My webpage has a dark background, that's why it really doesn't look good.
This problem occurs on Google Chrome (latest version) but not on Firefox. I am 99% sure it's caused by RC2, because I didn't have this problem with RC1.

Can you run your browser's network trace tools to perhaps see where the time is being spent? Is it network? Rendering? JavaScript? CSS? It might be good to compare the two browsers where you're seeing the different behavior. That might help narrow it down.

Hi @Eilon , I just used the network trace tools. The difference between RC1 and RC2 seems to be the following:
On RC1, the current page is still shown when the new page loads. After loading a few stuff, let's call this time X, it changes to the new page, which then finishes loading.
On RC2, the current page switches immediately to the new page, showing a blank page. Then when it reaches time X, the new page is shown and finishes loading.
Here is a screenshot where i cancelled loading shortly before time X was reached:

The problem can be reproduced very easily:
In Visual Studio create a new Asp Net Core Web Application. Then start the page in Google Chrome and hit the "About"-Button several times. You will notice how for a very short amount of time the page is totally white, causing an unpleasant experience.

Hmm, well, at a fundamental level, the default background in every browser I know of is white, so while it's loading "the next page" it's reasonable to expect there to be some default (i.e. white) background. But, I'm not sure why that would be different between RC1 and RC2...

No, I don't think it is reasonable. Normal behaviour sould be to keep the current background color at least until the background color of the next page is loaded, whereby a seamless toggle can happen. Otherwise we have this disturbing white flash.
As I mentioned before, in Firefox this doesn't happen, the "toggle" works seamless.

@jemala this is regular browser behavior, I don't know if there's much that a server framework can do about it. The browser decides when to redraw the background of the page. It might do it immediately after the user clicks, it might do it the moment the server responds to the request (but before sending any data back), or it might wait until it has downloaded all of the destination's HTML, CSS, and JavaScript.

@Eilon I agree. It's just strange that this behaviour appears in RC2 but not RC1. I'll do some more investigation and close this issue. Thank you for your help!

@jemala thanks I understand. I definitely agree it's unusual behavior to see that kind of change. Perhaps ASP.NET Core RC2 starts sending a response to the browser faster, so the browser "prepares itself" by clearing the rendering of the page... that's why I was curious with the network trace. I'm curious if you have a comparison of RC1 and RC2 behavior in the affected browser. Perhaps we'll see some difference there that would explain it. (Though, even if we learn that, I'm still not sure there's anything we could reasonably do.)

@Eilon I wasn't able to reproduce this problem when the webpage is deployed, that's why I am fine with this issue now. I think it has something to do with running the webpage locally over Visual Studio.

It's possible that this is caused by https://github.com/aspnet/Mvc/issues/4671 The root cause of that issue is that browserlink is inserting a BOM and causing chrome to do wierd things.
@jemala have you tried removing browserlink?

@rynowak I just tried it out and removed app.UseBrowserLink(); and the problem still occurs. But as I mentioned before, I am finde with it, since production environment on my server doesn't have this issue.

@rynowak You got it! I removed app.UseBrowserLink(); and now everything is working like a charm!


Remove a-micro-copy atom

Removes this deprecated atom. Companion to https://github.com/cfpb/consumerfinance.gov/pull/7914
Removals

Remove a-micro-copy atom.

Testing

PR checks should pass.

Closes https://github.com/cfpb/design-system/issues/1701


Error on launch

I keep getting the following when attempting to launch:
Traceback (most recent call last):
File "/usr/local/bin/rtv", line 9, in
load_entry_point('rtv==1.9.0', 'console_scripts', 'rtv')()
File "/usr/lib/python3/dist-packages/pkg_resources.py", line 337, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2280, in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources.py", line 1990, in load
entry = import(self.module_name, globals(),globals(), ['name'])
File "/usr/local/lib/python3.2/dist-packages/rtv/main.py", line 127, in
sys.exit(main())
File "/usr/local/lib/python3.2/dist-packages/rtv/main.py", line 108, in main
page.loop()
File "/usr/local/lib/python3.2/dist-packages/rtv/page.py", line 67, in loop
self.draw()
File "/usr/local/lib/python3.2/dist-packages/rtv/page.py", line 260, in draw
self._draw_header()
File "/usr/local/lib/python3.2/dist-packages/rtv/page.py", line 278, in _draw_header
self.term.add_line(window, sub_name, 0, 0)
File "/usr/local/lib/python3.2/dist-packages/rtv/terminal.py", line 251, in add_line
window.addstr(row, col, text, *params)
TypeError: must be str, not bytes
Any ideas?

Hi, I'm sorry that you're having problems!
It looks like you're using python 3.2. That version of python has some annoying unicode problems and as such is not supported by rtv and some of its dependencies (https://github.com/praw-dev/praw/pull/532). If you have python 2.7 on your system I would suggest trying that instead. If that's not an option, you will need to install python 3.3+

And that would do it, my apologies.


Improve readability of assertion failure messages

Fixes #764 as also discussed in this comment by

Moving the assertion expression at the end
Replacing the GetFailureMessage with GetExpectation which returns only the expectation from the BaseAssertCondition
Replacing the Passes method with GetResult which returns not only a boolean value, but an AssertionResult which also contains the failure message.

This allows the assertion message to be combined to read like an english sentence, e.g.
instead of
Assert.That(myClass).HasMember(x => x.Nested.Nested.Nested.Number).EqualTo(1)
MyClass.Number:
    Expected: 1
    Received: 123

it would read
Expected myClass MyClass.Number to be equal to 1, but received 123.
At Assert.That(myClass).HasMember(x => x.Nested.Nested.Nested.Number).EqualTo(1)

Also added some tests for correctly throwing exceptions (see #294) where the new output reads e.g.
Expected action to have Message equal to "Fails_For_Some_Other_Reason", but it differs at index 10:
              ↓
   "Fails_For_Exceptions_With_Different_Message"
   "Fails_For_Some_Other_Reason"
              ↑.
At Assert.That(action).ThrowsException.With.Message.EqualTo("Fails_For_Some_Other_Reason", StringCompar...

@thomhurst : I don't understand why the pipeline fails.
Locally all unit tests compile and succeed, but on the pipeline the TimeoutTests5 fail 🙈

@thomhurst : I don't understand why the pipeline fails. Locally all unit tests compile and succeed, but on the pipeline the TimeoutTests5 fail 🙈

It looks like one of the assertions has broken. If you go to the pipeline output, then scroll above the table you can expand each step to see it's full output.
I'm seeing this:
failed MatrixTest(2) (46ms)
    Expected value to be equal to 1
     or
    to be equal to 2
     or
    to be equal to 3, but the received value 2 is different and the received value
  2 is different.
    At Assert.That(value).IsEqualTo(1).Or.IsEqualTo(2).Or.IsEqualTo(3)

Thanks @vbreuss !


Add Dockerfile and README.md information

Hi, thanks for this package.
Attached is a Dockerfile to allow a user to run this without installing the dependencies on their local machine.

Thank you very much for this contribution. I think this tool will be more convenient for users with the help of Docker.
Thank you.


Trajectory Prediction

I have a question please.
It is logical that the tracks might have different length appearance in the video.
Is there a phase of pre-processing that you make them in the same size of length(which I didn't found it in function get_data) or the model deal with it automatically ?
Thank you

Hi,
You are correct, it is logical to make them the same size (perhaps by padding). what we did, however, is that we excluded shorter tracks (below  obs_lenght+pred_length) when reading the raw annotations from the data interface. There were very few cases excluded.

Thank you for the clarification and for the great work, it went very well on my own dataset.


Remove distributed functionality

It looks like #1 was closed due to master being force-pushed with no way to open the PR again. Opening a new PR until I know if I can actually reopen #1 somehow.

@hkaiser are you planning to have a closer look at this? Or do you have further responses to the comments that @aurianer has made?

launch perftests

Performance test report

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4f84d7fff4ebb721fd29f0fb7005b75d09fb2b23cHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-12T12:10:23+00:00Hostnamenid00007nid01341Datetime2021-11-12T12:57:36.293079+01:002021-11-12T13:29:09.101376+01:00ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add-(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)-(=)Stream Benchmark - Copy(=)=(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4f84d7fff4ebb721fd29f0fb7005b75d09fb2b23cHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-12T12:10:23+00:00Hostnamenid00007nid01341Datetime2021-11-12T12:57:50.824026+01:002021-11-12T13:29:23.787867+01:00ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4aac4249aea7878cca14608d92aa3b44b33d78ddaHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-12T13:54:01+00:00EnvfileClusternamedaintdaintDatetime2021-11-12T12:57:36.293079+01:002021-11-12T14:58:56.099132+01:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Hostnamenid00007nid00359ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)(=)--Stream Benchmark - Scale(=)=(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)=InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4aac4249aea7878cca14608d92aa3b44b33d78ddaHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-12T13:54:01+00:00EnvfileClusternamedaintdaintDatetime2021-11-12T12:57:50.824026+01:002021-11-12T14:59:10.698098+01:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Hostnamenid00007nid00359Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch-InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e45086cf21bdd33847871e1be8aaff7fb04b8a8a23HPXLocal Datetime2021-11-12T11:29:27+00:002021-11-16T09:57:49+00:00Datetime2021-11-12T12:57:36.293079+01:002021-11-16T11:04:04.424142+01:00ClusternamedaintdaintHostnamenid00007nid00397Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad-(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e45086cf21bdd33847871e1be8aaff7fb04b8a8a23HPXLocal Datetime2021-11-12T11:29:27+00:002021-11-16T09:57:49+00:00Datetime2021-11-12T12:57:50.824026+01:002021-11-16T11:04:19.365439+01:00ClusternamedaintdaintHostnamenid00007nid00397Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4936999a61f27ca7f187d84cd1cba26c24c1ba9beHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-17T11:28:07+00:00EnvfileClusternamedaintdaintHostnamenid00007nid01294Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2021-11-12T12:57:36.293079+01:002021-11-17T12:37:18.979943+01:00ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add--(=)Stream Benchmark - Scale(=)(=)-Stream Benchmark - Triad-(=)(=)Stream Benchmark - Copy(=)-(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4936999a61f27ca7f187d84cd1cba26c24c1ba9beHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-17T11:28:07+00:00EnvfileClusternamedaintdaintHostnamenid00007nid01294Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2021-11-12T12:57:50.824026+01:002021-11-17T12:37:33.714006+01:00Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch=InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e47eb48791b025e35b653838d84cc5880e0f703eacHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-18T10:03:30+00:00Hostnamenid00007nid01191Datetime2021-11-12T12:57:36.293079+01:002021-11-18T11:08:44.589454+01:00ClusternamedaintdaintEnvfileCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add-(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e47eb48791b025e35b653838d84cc5880e0f703eacHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-18T10:03:30+00:00Hostnamenid00007nid01191Datetime2021-11-12T12:57:50.824026+01:002021-11-18T11:08:59.091130+01:00ClusternamedaintdaintEnvfileCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

@hkaiser I've added a check that prints an error message as follows if it detects inconsistently cased CMake cache variables:
CMake Error at cmake/HPXLocal_Message.cmake:51 (message):
  HPXLocal expects all HPXLocal variables to be prefixed with HPXLocal.
  Found the following variables with inconsistent casing: HPXLOCAL_WITH_BLAH
  HPX_LOCAL_WITH_BOO.  Please unset the listed variables and set them with
  the correctly cased prefix instead.
Call Stack (most recent call first):
  cmake/HPXLocal_CheckOptionsCase.cmake:20 (hpx_local_error)
  CMakeLists.txt:113 (include)

-- Configuring incomplete, errors occurred!

Let me know if you think a different message would be better. The check takes a measurable but negligible amount of time (a few tens of ms on my system), so I think we're ok here.

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-25T11:45:13+00:00HPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4e93bc556bb577c5eeb6f4d0a1965aad8f65d6874ClusternamedaintdaintDatetime2021-11-12T12:57:36.293079+01:002021-11-25T13:18:00.497054+01:00Hostnamenid00007nid00858EnvfileCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)-(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-25T11:45:13+00:00HPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4e93bc556bb577c5eeb6f4d0a1965aad8f65d6874ClusternamedaintdaintDatetime2021-11-12T12:57:50.824026+01:002021-11-25T13:18:15.144849+01:00Hostnamenid00007nid00858EnvfileCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch-InfoPropertyBeforeAfterHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-29T12:43:36+00:00HPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e41e8e2495ac1ce2136436419ec2f91433951bba76EnvfileDatetime2021-11-12T12:57:36.293079+01:002021-11-29T13:49:21.955395+01:00Hostnamenid00007nid00787Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale-(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-29T12:43:36+00:00HPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e41e8e2495ac1ce2136436419ec2f91433951bba76EnvfileDatetime2021-11-12T12:57:50.824026+01:002021-11-29T13:49:36.603100+01:00Hostnamenid00007nid00787Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch-InfoPropertyBeforeAfterHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-30T12:58:11+00:00HPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e46b0ce51dcc6b958b49b1a6275d59d2adb20c8d63ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Hostnamenid00007nid01251Datetime2021-11-12T12:57:36.293079+01:002021-11-30T14:04:13.740256+01:00EnvfileComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)-(=)Stream Benchmark - Scale-(=)-Stream Benchmark - Triad(=)(=)-Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Datetime2021-11-12T11:29:27+00:002021-11-30T12:58:11+00:00HPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e46b0ce51dcc6b958b49b1a6275d59d2adb20c8d63ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Hostnamenid00007nid01251Datetime2021-11-12T12:57:50.824026+01:002021-11-30T14:04:28.661573+01:00EnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch-InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4d208e6471d79a1bad845e20e21416d591994af62HPXLocal Datetime2021-11-12T11:29:27+00:002021-12-01T11:55:59+00:00ClusternamedaintdaintEnvfileHostnamenid00007nid00377Datetime2021-11-12T12:57:36.293079+01:002021-12-01T13:29:50.429928+01:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)--(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4d208e6471d79a1bad845e20e21416d591994af62HPXLocal Datetime2021-11-12T11:29:27+00:002021-12-01T11:55:59+00:00ClusternamedaintdaintEnvfileHostnamenid00007nid00377Datetime2021-11-12T12:57:50.824026+01:002021-12-01T13:30:05.143677+01:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4335d6980b949f785b256efec1c86268d45ef8409HPXLocal Datetime2021-11-12T11:29:27+00:002021-12-08T10:27:19+00:00Hostnamenid00007nid00088Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintEnvfileDatetime2021-11-12T12:57:36.293079+01:002021-12-08T11:34:06.729116+01:00ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad-(=)(=)Stream Benchmark - Copy(=)(=)=InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4335d6980b949f785b256efec1c86268d45ef8409HPXLocal Datetime2021-11-12T11:29:27+00:002021-12-08T10:27:19+00:00Hostnamenid00007nid00088Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintEnvfileDatetime2021-11-12T12:57:50.824026+01:002021-12-08T11:34:21.445098+01:00Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch=InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e41777efa185670922e9e14e27011eda7c980d58caHPXLocal Datetime2021-11-12T11:29:27+00:002021-12-10T13:38:45+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileDatetime2021-11-12T12:57:36.293079+01:002021-12-10T14:44:48.477544+01:00ClusternamedaintdaintHostnamenid00007nid00025ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add-(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e41777efa185670922e9e14e27011eda7c980d58caHPXLocal Datetime2021-11-12T11:29:27+00:002021-12-10T13:38:45+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileDatetime2021-11-12T12:57:50.824026+01:002021-12-10T14:45:03.101234+01:00ClusternamedaintdaintHostnamenid00007nid00025Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch-InfoPropertyBeforeAfterHPXLocal Datetime2021-11-12T11:29:27+00:002021-12-10T13:50:04+00:00HPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4f499a2233385060b8a2612ab88163e62b0881888Hostnamenid00007nid00243Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileClusternamedaintdaintDatetime2021-11-12T12:57:36.293079+01:002021-12-10T15:19:42.442217+01:00ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Datetime2021-11-12T11:29:27+00:002021-12-10T13:50:04+00:00HPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4f499a2233385060b8a2612ab88163e62b0881888Hostnamenid00007nid00243Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileClusternamedaintdaintDatetime2021-11-12T12:57:50.824026+01:002021-12-10T15:19:57.079887+01:00Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch-InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e43144a72b429d1303b80b0055b92624b0f8117c90HPXLocal Datetime2021-11-12T11:29:27+00:002021-12-10T14:20:48+00:00ClusternamedaintdaintEnvfileDatetime2021-11-12T12:57:36.293079+01:002021-12-10T15:35:55.319667+01:00Hostnamenid00007nid00589Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad=(=)(=)Stream Benchmark - Copy(=)=(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e43144a72b429d1303b80b0055b92624b0f8117c90HPXLocal Datetime2021-11-12T11:29:27+00:002021-12-10T14:20:48+00:00ClusternamedaintdaintEnvfileDatetime2021-11-12T12:57:50.824026+01:002021-12-10T15:36:09.898168+01:00Hostnamenid00007nid00589Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch+InfoPropertyBeforeAfterHPXLocal Datetime2021-12-10T13:50:04+00:002021-12-10T14:37:42+00:00HPXLocal Commitf499a2233385060b8a2612ab88163e62b088188807df735c9f93a082f146438cd554bb2eb966dae9ClusternamedaintdaintDatetime2021-12-10T15:19:42.442217+01:002021-12-10T15:45:18.095948+01:00EnvfileHostnamenid00243nid00111Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)(=)-Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy-(=)(=)InfoPropertyBeforeAfterHPXLocal Datetime2021-11-12T11:29:27+00:002021-12-10T14:37:42+00:00HPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e407df735c9f93a082f146438cd554bb2eb966dae9ClusternamedaintdaintDatetime2021-11-12T12:57:50.824026+01:002021-12-10T15:45:33.019452+01:00EnvfileHostnamenid00007nid00111Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch=InfoPropertyBeforeAfterHPXLocal Commitf499a2233385060b8a2612ab88163e62b0881888ff771179d3d6c09924f905e962e7945e616cc9baHPXLocal Datetime2021-12-10T13:50:04+00:002021-12-10T14:47:19+00:00Hostnamenid00243nid00242ClusternamedaintdaintDatetime2021-12-10T15:19:42.442217+01:002021-12-10T15:57:25.555543+01:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)-(=)Stream Benchmark - Scale(=)(=)-Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)=(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4ff771179d3d6c09924f905e962e7945e616cc9baHPXLocal Datetime2021-11-12T11:29:27+00:002021-12-10T14:47:19+00:00Hostnamenid00007nid00242ClusternamedaintdaintDatetime2021-11-12T12:57:50.824026+01:002021-12-10T15:57:40.807974+01:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch=InfoPropertyBeforeAfterHPXLocal Commitf499a2233385060b8a2612ab88163e62b0881888cd461874d1f40c3fb7b4d86946697d27f5026f5fHPXLocal Datetime2021-12-10T13:50:04+00:002021-12-13T11:56:43+00:00ClusternamedaintdaintEnvfileHostnamenid00243nid01171Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2021-12-10T15:19:42.442217+01:002021-12-13T13:38:39.606556+01:00ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add--(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)--Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4cd461874d1f40c3fb7b4d86946697d27f5026f5fHPXLocal Datetime2021-11-12T11:29:27+00:002021-12-13T11:56:43+00:00ClusternamedaintdaintEnvfileHostnamenid00007nid01171Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2021-11-12T12:57:50.824026+01:002021-12-13T13:38:54.371612+01:00Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPXLocal Datetime2021-12-10T13:50:04+00:002021-12-15T13:50:40+00:00HPXLocal Commitf499a2233385060b8a2612ab88163e62b08818885d572cce71ac0bd2e503d6748a09cbb4e93b3a28Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileDatetime2021-12-10T15:19:42.442217+01:002021-12-15T15:00:12.368952+01:00Hostnamenid00243nid01569ClusternamedaintdaintComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add-(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy=(=)(=)InfoPropertyBeforeAfterHPXLocal Datetime2021-11-12T11:29:27+00:002021-12-15T13:50:40+00:00HPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e45d572cce71ac0bd2e503d6748a09cbb4e93b3a28Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0EnvfileDatetime2021-11-12T12:57:50.824026+01:002021-12-15T15:00:27.079813+01:00Hostnamenid00007nid01569ClusternamedaintdaintExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPXLocal Datetime2021-12-10T13:50:04+00:002021-12-15T16:26:56+00:00HPXLocal Commitf499a2233385060b8a2612ab88163e62b08818885e505ea92cbe12911113420956fa43884c4b8feaCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2021-12-10T15:19:42.442217+01:002021-12-15T17:34:07.770571+01:00Hostnamenid00243nid00156ClusternamedaintdaintEnvfileComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)-(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)-(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Datetime2021-11-12T11:29:27+00:002021-12-15T16:26:56+00:00HPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e45e505ea92cbe12911113420956fa43884c4b8feaCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2021-11-12T12:57:50.824026+01:002021-12-15T17:34:22.420288+01:00Hostnamenid00007nid00156ClusternamedaintdaintEnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPXLocal Commitf499a2233385060b8a2612ab88163e62b0881888db150af5b2b9789975fff05ca90e93469e39b3acHPXLocal Datetime2021-12-10T13:50:04+00:002021-12-16T19:30:10+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Hostnamenid00243nid00635ClusternamedaintdaintEnvfileDatetime2021-12-10T15:19:42.442217+01:002021-12-16T20:39:49.183706+01:00ComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad-(=)(=)Stream Benchmark - Copy(=)-(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4db150af5b2b9789975fff05ca90e93469e39b3acHPXLocal Datetime2021-11-12T11:29:27+00:002021-12-16T19:30:10+00:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Hostnamenid00007nid00635ClusternamedaintdaintEnvfileDatetime2021-11-12T12:57:50.824026+01:002021-12-16T20:40:03.779285+01:00Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

@msimberg thanks for moving this forward!


AngularJS bundle not being loaded by karma

Hi, I already asked on SO, but the question got very low visibility and I don't believe I'll get an answer there. So I hope you won't mind too much that I'm asking here. I also asked on gitter, but got no responses.
If you could just please hear me out, I suspect my issue is probably something trivial which I'm unable to see and you might easily spot it. I already tried everything I could think of and am practically out of ideas at this point.
Webpack version:
v3.3.0
Webpack Karma version:
v2.0.5
Karma version:
v1.7.1
Please tell us about your environment:
Windows 10
Browser: [PhantomJS] (karma-phantom-launcher v1.0.4)
Issue:
I described everything in great detail in that SO thread but this is the short version:
Basically my issue is that I believe the AngularJS bundle is not being loaded by karma. I use AngularJS written in Typescript and the webpack transpiles it into JS and for all the dev purposes - it works great. It builds the app, runs it, and it works fine in the browser.
However, when I try to wire it up with karma-webpack, karma runs, jasmine runs, but the app does not get loaded - I don't see any console.logs that are supposed to come from the app (this worked with my old gulp setup) and I can't even inject a simple service with angular-mocks so I could do a simple test of a service method.
For how I understand it, my setup should work but it doesn't and I have no idea why.
If this it's too much hassle for you guys - I can totally understand you. In that case just ignore this and close the case. But, I figured if anyone will know how to help - it will be you guys.
In any case - thanks a lot! Cheers.

I extracted a few files into a simple app and put it to a fresh repo so the issue could be easily reproduced.
npm install
npm run serve:dev # run the app
npm run test # run karma tests

Create file at the root of your directory with the following content
const testsContext = require.context(".", true, /_test$/)

testsContext.keys().forEach(testsContext)

Make this the only file in your files and preprocessors object array (in my case the file is called webpack.tests.js)
files: ['webpack.tests.js'],
preprocessors: {
      'webpack.tests.js': ['webpack', 'sourcemap'],
    },

At the beginning of your webpack.tests.js file (or the name you put it), add the lines that import angular, angular-mocks, polyfills and such, it should work

Hi @jesujcastillom,
I have same issue. I think karma not load bundle created by preprocessors webpack.
In your last example, you are importing again your raw sources and do not use bundle created by webpack.
Do I correctly understand ?
If I do, how could we use webpack bundle ?
Thanks for your answer

Closing as this is quite an old ticket and @jesujcastillom seems to have a solution posted. If you are still having problems with the current build, feel free to open another issue and I'll assist as best I can!


Question about the Tools in your Library

Hello there,
I came across your library when doing some research on color theory, SASS, and ways in which to convert RGB colors to LAB. Nice work here, looks very promising. I plan to download it and give it a try in a project.
I was doing this research because I have a series of mixins and functions that I want to create to help solve a problem:

Clients have brand colors that do not meet accessibility goals (Level AA most typically)
The HSB color space provides a way to adjust saturation and brightness to achieve a higher contrast without changing the Hue, which preserves the original intention of the color. Iit is imperfect, but it mostly works if the designer adjusts both values and judges what will pass vs. what preserves the original intent of the color.
Making these adjustments is a manual process that a designer or a savvy developer needs to do, esp. when the client's brand "blue" might be used over white, light grey, or light blue. Each of these scenarios means tweaking the blue to pass contrast ratio checks.
SASS can darken(), lighten(), saturate(), scale-color(), etc… but none of these do those things with the goal of hitting a target contrast ratio when compared to another color.

I am interested in the latter… with lots of math and comparison checking, I'd like to create a mixin that can take two color values and adjusts the one foreground color value to pass an accessibility threshold, like so: color: a11y-foreground($foreground, $background, $font-size: 16, $bold-or-not: false, $wcag-level: 'AA').
I got pretty far but am stuck on how to calculate the distance between colors properly. That's why I was investigating LAB. Do you have any advice here, or any tools in the Chromatic library that could help achieve this?
Thanks so much for any answer.

This module is just a wrapper around chroma-js, to make its functions available from sass.
So, for color distances, you might want to look at chroma.distance from chroma-js.

Thanks, I headed in that direction.


Upgrade Conscrypt to 1.0.0.RC10

Motivation:
Getting the latest Conscrypt goodies.
Modifications:
A few API changes have occurred, specifically in the Conscrypt
class.
Result:
Netty now builds and tests against Conscrypt 1.0.0.RC10

@nmittler can you please rebase ?

@normanmaurer done

@normanmaurer any other comments or shall I commit?

@nmittler go for it

@normanmaurer I'm in the process of cutting another release candidate that the Jetty guys need, which has a couple more API changes.  I'll just update this PR to use RC11 once it's available on Maven central.

@nmittler works for me

@normanmaurer PTAL

@nmittler ship it to 4.1 and 4.0 please

Cherry-picked into 4.1 (5a6ee27cee9df99404016f124d3768f9793dff59) and 4.0 (1cac3d6cee4abdb44b3b45d81a7bee35ed589a18)


Speed controls

We should add speed controls:

Dedicated controller API (probably like muted, just stores the value and applies it to the underlying AVPlayer).
Integration in the iOS control center with the dedicated API.
Integration in the tvOS 15 info panel with a dedicated button.
On iOS, the easiest is probably to integrate speed selection in the tracks popover (maybe with a settings icon). Other possibilities include a dedicated button or maybe an action which could be optionally added to a custom menu (see #107)
Disabled for livestreams.

Question: Do we have to offer the possibility to customize the list of predefined speeds? What happens when a non-supported speed is set via the API? (do we add a temporary entry in the UI to display its value?).

Beware:

Speeds must be > 0.
Even with an API providing standard speeds it is possible to set the player rate to any value. Any UI displaying standard speeds should therefore display an other entry if this happens to be the case, with the value (as we do for subtitles not available for some content but still saved at the system level).

For livestreams locking the playback rate is difficult (as we don't know that a stream is live until we play it). Moreover this seems to work, at least probably using some buffering (< 1 are applied, > 1 are ignored because we cannot play in the future). For the moment I won't do anything special, we'll see if work is really required to prevent playback speed changes for livestreams.

I made a proposal with the settings icon replacing the tracks icon but we'll keep the tracks icon.

I tested the addition of a playback speed button on tvOS. On my tvOS 15.4 beta device the button is deselected after making a choice. This is apparently not related to changes triggering a button reload but most likely an issue which I don't experience in the ivOS 15.3 simulator.

I finished the implementation. The question above still remains to be answered, but the API and testing work is done.

The speed has been restricted to 1x for livestreams without DVR. Slower speeds could work (buffering would still need to be studied) but the UX obtained is awkward (you cannot fast forward to the live conditions).

@defagos Thanks for driving this nice player feature to the SRG SSR Apple player.


Splunk Connect NameSpace indexer

Hi guys, i try to push my Namespaced Loggs into an own index.
First i set the annotation in the Namespace with my index Name. According to the docu it should work right away, but it dont. The problem could be the hardcoded value in the value.yaml during the installation? Should i let the field index = *** at value.yaml empty?
Thanks.
Best
Bruslan

It seems that if you change the index annotation, you have to restart the Pod, so that the logs get written in the new index.
Is that so normal and desirable?

@Mr-iX it should rake effect immediately. please use latest version. (chart 1.4.3). If you still have an issue, please open a new issue. closing this.


Rename histories

Allow histories to be renamed. Also rename histories that are uploaded so they match the original name, that is, remove the '(uploaded history...)' text added by Galaxy to the history name

It has been possible to rename histories for some time.  However, a history can not be renamed until the upload completes, which could be quite some time and would require polling for the job to complete.  There does not appear to be a way to specify the name as part of the import as there is with datasets.


[catmem] Don't Close Pipe When EoF is Reached

Description
This PR closes https://github.com/demikernel/demikernel/issues/480
Summary of Changes

Added a new example application to expose https://github.com/demikernel/demikernel/issues/480.
Added new example application to demikernel_ci.
Added Pipe abstraction to Catmem LibOS.
Fixed https://github.com/demikernel/demikernel/issues/480.

The changes to catmem conflict with my changes in PR #486. It should be easy to replace the ring field in CatmemQueue without disturbing any of the rest of the code, but I'm not sure what order in which these two PRs should go in. Otherwise, the changes look good to me.

Yes, let us work together on your enhancement changes to make sure that they also cover this bug fix.


Question about training time of EDAPS

Hello, thanks for your great work. I noticed that in your paper, you mentioned that the training of EDAPS only requires 21 hours on a single RTX 2080Ti GPU. However, when I trained EDAPS using the default settings and the provided script,
python run_experiments.py --config configs/edaps/syn2cs_uda_warm_dfthings_rcs_croppl_a999_edaps_s0.py

it took almost three days to complete. I used a single RTX 2080Ti GPU as well. Additionally, I trained DAFormer with the default settings, and it only took one day. I would like to know if there is any mistake I made during the training process. I would greatly appreciate any suggestions you could provide. Thank you!

@Tocmac : You can check the training and evaluation log here: https://drive.google.com/file/d/1Dqm58cW8l6cWl_uhJ-I0QRx3DaCjp_--/view?usp=sharing, or 20221025_114656.log.


Demo for amp-web-push component

AMP by Example demo for amp-web-push component.

This demo requires two extra static files: a helper iframe and a permission dialog (placed at the /static/webpush/ folder).
It follows the VAPID standard for Webpush.
Uses an IndexedDB database ("web-push-db"), to store and retrieve the Webpush subscription object, to avoid storing it on a remote DB.
The SW had to be updated to include the events suggested in the documentation, to store and retrieve the tokens and listen to "push" events.
The SW will also intercept the request from the form of the page for the "send-push" event, retrieve the token from IndexedDB and send a request to an endpoint at: https://demo-amp-web-push.glitch.me/send-push, so the notification can be created and sent in the backend with the WebPush Node library.

Thanks for your comments, I'll work on them.
I deployed a version here: https://amp-web-push-demo.firebaseapp.com/components/amp-web-push/.
On that version, playground is not working, as I only deployed the static part.
Please, let me know if you need anything else.

Thanks Demian for the preview, I left some other comments.

This is great, thanks Chiara. I'll include your recommendations on my update.

Hi @kul3r4 just made changes based on your comments and uploaded a new version here:
https://amp-web-push-demo.firebaseapp.com/components/amp-web-push/

Looks good

Can you re-enable the playground. Otherwise looks great! Thanks a lot for your work!

@sebastianbenz thank you for the help! I just enabled Playground, please, let me know if I can do something else.

👍


refactor(Set/Countable): redefine Set.Countable

Turn Set.Countable s into an abbreviation for _root_.Countable s.
This means that it can now be used as a [s.Countable] typeclass argument.
fix compile.

maintainer merge

@eric-wieser I changed from abbrev to def. Could you please have another look?


⚠ Bofrost.be has degraded performance

In a8ce338, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 3181 ms

Resolved: Bofrost.be performance has improved in 64d5718.


version control

This is a feature request somewhat related to #3548.  What I'd like to see is local integration with version control.  For Git, for example, if a notebook is stored in a local git repo, every save should result in a commit.  The UI should have an option for pushing local commits to the origin. And maybe a UI option to pull the latest commit from the origin.

Beaker Lab has version control.
And there are already a lot of nice git UIs.
So while this is possible I don't see it happening anytime soon in standalone Beaker.
Thanks for the suggestion.

That's a shame because Beaker Lab isn't a viable solution to me because of corporate policies.  I'm sure many business users are in the same boat.


Support MongoDB case insensitive collection name

Fixes https://github.com/prestosql/presto/issues/1102
Currently any MongoDB collection with uppercase name like "Hello" could not be queried.
This PR makes it possible by supporting case insensitivity for collection name, providing solution for case 2 mentioned here https://github.com/prestosql/presto/issues/1102#issuecomment-536331360, it doesn't help case 1 though.

@cla-bot check

@tchunwei could you please rebase on current master and squash commits? Ideally, there should be just one commit after that.

@findepi thanks for guiding, has rebased, made it into single commit and force pushed. Kindly let me know if I did it incorrectly, thanks again.

@tchunwei  Why was this closed?

@buffcode that was done unintentionally, was rebasing my code then accidentally wiped my commit, will re-open later

Thank you @ebyhr for your effort guiding me and reviewing the code. Have updated the code based on the feedback for your further review.

any updated about this?

I am sorry I do not have much time for this and this is consider low priority for me so will put this aside first. Also, this PR will be a temporary solution until https://github.com/prestosql/presto/pull/2350 is ready. So I think it would be better to wait for https://github.com/prestosql/presto/pull/2350 since it is a better approach?

I am sorry I do not have much time for this and this is consider low priority for me so will put this aside first. Also, this PR will be a temporary solution until #2350 is ready. So I think it would be better to wait for #2350 since it is a better approach?

ok, thanks

Any updates of this?

Covered by #3453


docs: Incorrect information during v1beta1-migration.md to official document version 0.32.x

Fixes #N/A
Description
incorrect information during v1beta1-migration to official document version 0.32.x
How was this change tested?
N/A
Does this change impact docs?

[x] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 82.342%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
6174

Relevant Lines:
7498

💛  - Coveralls


Release: Roadmap

Hi, guys!
I think that we're ready to form roadmap for 1.0 release, we can keep this issue as global TODO :ship:

There is bunch of refactors that we need to do:

[ ] #599 Fix prop warnings in tests and docs;
[ ] #607 Improve performance with update to class-based components;
[ ] #564 Update docs to latest pattern;
[ ] #623 Update callbacks for passing props;
[ ] #524 Remove propTypes in production builds, allow small builds;

Add missing components:

[ ] #185 Advertisement
[ ] #447 Dimmer
[ ] #191 Embed
[ ] #192 Nag
[ ] #182 Reveal
[ ] #196 Shape
[ ] #197 Sidebar
[ ] #198 Sticky
[ ] #199 Tab
[ ] #200 Transition

@jcarbo @levithomason Do I miss something?

Heads up, there is already an actual v1.0 milestone.  Let's use that instead of a checklist.  It is a little easier to manage and has better GitHub integration.
You can add issues like so:


typing.Annotated is not suggested for auto-import in Quick Fix menu

Environment data

Pylance version: v2024.10.1
OS and version:

Host: macOS Sequoia 15.1 (24B82)
Remote: Ubuntu 20.04.6 LTS

Python version: 3.10.13

Code Snippet
Define an Annotated type Result:
from typing import Annotated, Generic, Literal, TypeVar

from pydantic import BaseModel, Field

T_co = TypeVar("T_co", covariant=True)
E_co = TypeVar("E_co", covariant=True)

class Success(BaseModel, Generic[T_co]):
    type: Literal["success"] = "success"
    value: T_co

class Error(BaseModel, Generic[E_co]):
    type: Literal["error"] = "error"
    error: E_co

Result = Annotated[
    Success[T_co] | Error[E_co],
    Field(discriminator="type"),
]

Repro Steps
Introduce a new usage of an Annotated type and use "Quick Fix" in VSCode.

In a different file write:

foo: Result[int, str] = Success(value=10)
# cursor: |

Use Quick Fix shortcut

Expected behavior
Import of module defining Result is suggested.
Actual behavior
Module defining Result is not suggested.
Logs
2024-10-25 16:18:54.319 [info] [Info  - 4:18:54 PM] (2069442) Server root directory: file:///home/reuben/.vscode-server/extensions/ms-python.vscode-pylance-2024.10.1/dist
2024-10-25 16:18:54.320 [info] [Info  - 4:18:54 PM] (2069442) Pylance language server 2024.10.1 (pyright version 1.1.382, commit e46efc6b) starting
2024-10-25 16:18:54.325 [info] [Info  - 4:18:54 PM] (2069442) Starting service instance "redacted"
2024-10-25 16:18:54.958 [info] [Info  - 4:18:54 PM] (2069442) Setting environmentName for service "redacted": "3.10.13 (next-vavphVWf venv)"
2024-10-25 16:18:54.975 [info] [Info  - 4:18:54 PM] (2069442) Setting pythonPath for service "redacted": "/home/reuben/.local/share/virtualenvs/next-vavphVWf/bin/python"
2024-10-25 16:18:54.976 [info] [Info  - 4:18:54 PM] (2069442) No include entries specified; assuming /home/reuben/dev/redacted
2024-10-25 16:18:54.982 [info] [Info  - 4:18:54 PM] (2069442) Auto-excluding **/node_modules
2024-10-25 16:18:54.982 [info] [Info  - 4:18:54 PM] (2069442) Auto-excluding **/__pycache__
2024-10-25 16:18:55.003 [info] [Info  - 4:18:55 PM] (2069442) Auto-excluding **/.*
2024-10-25 16:18:55.025 [info] [Info  - 4:18:55 PM] (2069442) Assuming Python version 3.10.13.final.0
2024-10-25 16:18:55.296 [info] [Info  - 4:18:55 PM] (2069442) Found 1047 source files
2024-10-25 16:18:55.705 [info] [Info  - 4:18:55 PM] (2069442) Background analysis(1) root directory: file:///home/reuben/.vscode-server/extensions/ms-python.vscode-pylance-2024.10.1/dist
2024-10-25 16:18:55.705 [info] [Info  - 4:18:55 PM] (2069442) Background analysis(1) started
2024-10-25 16:18:55.706 [info] [Info  - 4:18:55 PM] (2069442) Indexer background runner(2) root directory: file:///home/reuben/.vscode-server/extensions/ms-python.vscode-pylance-2024.10.1/dist (index)
2024-10-25 16:18:55.706 [info] [Info  - 4:18:55 PM] (2069442) Indexing(2) started
2024-10-25 16:18:56.156 [info] [Info  - 4:18:56 PM] (2069442) scanned(2) 544 files over 1 exec env
2024-10-25 16:18:56.429 [info] [Info  - 4:18:56 PM] (2069442) indexed(2) 544 files over 1 exec env
2024-10-25 16:18:56.552 [info] [Info  - 4:18:56 PM] (2069442) Indexing finished(2).
2024-10-25 16:19:01.116 [info] [Info  - 4:19:01 PM] (2069442) Starting service instance "<default>"
2024-10-25 16:19:01.131 [info] [Info  - 4:19:01 PM] (2069442) Setting environmentName for service "<default>": "3.10.13 (next-vavphVWf venv)"
2024-10-25 16:19:01.131 [info] [Info  - 4:19:01 PM] (2069442) Setting pythonPath for service "<default>": "/home/reuben/.local/share/virtualenvs/next-vavphVWf/bin/python"
2024-10-25 16:19:01.131 [info] [Info  - 4:19:01 PM] (2069442) No include entries specified; assuming /<default workspace root>
2024-10-25 16:19:01.131 [info] [Info  - 4:19:01 PM] (2069442) Auto-excluding **/node_modules
2024-10-25 16:19:01.131 [info] [Info  - 4:19:01 PM] (2069442) Auto-excluding **/__pycache__
2024-10-25 16:19:01.131 [info] [Info  - 4:19:01 PM] (2069442) Auto-excluding **/.*
2024-10-25 16:19:01.162 [info] [Info  - 4:19:01 PM] (2069442) Assuming Python version 3.10.13.final.0
2024-10-25 16:19:01.221 [info] [Error - 4:19:01 PM] (2069442) File or directory "/<default workspace root>" does not exist.
2024-10-25 16:19:01.221 [info] [Info  - 4:19:01 PM] (2069442) No source files found.
2024-10-25 16:19:01.225 [info] [Info  - 4:19:01 PM] (2069442) [id_0] Logging started
2024-10-25 16:19:01.440 [info] [Info  - 4:19:01 PM] (2069442) Found 1047 source files
2024-10-25 16:19:01.516 [info] [Error - 4:19:01 PM] (2069442) File or directory "/<default workspace root>" does not exist.
2024-10-25 16:19:01.516 [info] [Info  - 4:19:01 PM] (2069442) No source files found.
2024-10-25 16:19:01.520 [info] [Info  - 4:19:01 PM] (2069442) Background analysis(3) root directory: file:///home/reuben/.vscode-server/extensions/ms-python.vscode-pylance-2024.10.1/dist
2024-10-25 16:19:01.520 [info] [Info  - 4:19:01 PM] (2069442) Background analysis(3) started
2024-10-25 16:19:04.436 [info] (Client) The existing extension didn't exit within 10 seconds. New instance will start, but you might encounter issues.
2024-10-25 16:19:04.436 [info] (Client) Pylance async client (2024.10.1) started with python extension (2024.16.1)
2024-10-25 16:19:14.616 [info] [Info  - 4:19:14 PM] (2069442) [id_0] Logging stopped at /tmp/pyright-2069442-JlwFjC36EsjZ/pylance_2024.10.1_id_0.txt

Thanks for reporting, I can reproduce


Unable to discover some unit test projects

From @niemyjski on February 8, 2017 17:2
Since the latest VS2017  RC3 update I'm unable to discover all of my unit test projects...
Just clone (https://github.com/exceptionless/foundatio) and try building different projects / run the Foundatio.Redis tests (they aren't found or listed in the test runner). I haven't tried via the command line
Copied from original issue: dotnet/sdk#839

I tried to run the tests via the command line and they ran.. so it appears to be just a VS issue

The tests are not discovered because following dependencies are not present in Foundatio.Redis.Tests csproj:
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.0.0-*" />
    <PackageReference Include="xunit" Version="2.2.0-*" />
    <PackageReference Include="xunit.runner.visualstudio" Version="2.2.0-*" />

After adding them, tests show up.

Closing this. Please reopen if you still observe this behavior.


Error after deleting all bounding boxes

Hi, I am getting an error IndexError: index 0 is out of bounds for axis 0 with size 0 which is triggered from the BoundingBoxList.inside() method. This happens when I have an empty bounding box layer after deleting a bounding box. I think napari tries to see if the mouse is inside a bounding box but since there are no bounding boxes it throws this error every time the mouse coords update.
I'm using napari-bbox version 0.0.7 and napari version 0.4.18.
Napari info:
napari: 0.4.18
Platform: macOS-14.3-x86_64-i386-64bit
System: MacOS 14.3
Python: 3.9.17 (main, Jun 20 2023, 17:03:39) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
Qt: 5.15.2
PyQt5: 5.15.6
NumPy: 1.26.4
SciPy: 1.12.0
Dask: 2022.04.0
VisPy: 0.12.2
magicgui: 0.4.0
superqt: 0.6.2
in-n-out: 0.1.9
app-model: 0.2.4
npe2: 0.7.4
OpenGL:

GL version: 2.1 INTEL-22.1.29
MAX_TEXTURE_SIZE: 16384

Hey @grahamross123,
I think this is the same issue as #12. This was already solved, but a new release wasn't created yet. If you would like to try it, install the plugin from Github. If you need any help with that, just let me know!
Cheers,
David

Hi @bauerdavid,
You're right, I missed that - got it working now!
Thanks,
Graham


Multi-cloud workflows

I'd like to run a workflow that starts in one cloud provider (e.g. Azure) and finishes in another (e.g. AWS or GCP.)

See #3523


Create an Enemy object to store methods and properties related to the enemy that our player has to battle.

An Enemy object has the following properties:
name
weapon
health
strength
agility
potion
An Enemy object has the following methods:
getDescription()
getHealth()
getAttackValue()
isAlive()
reduceHealth()
Write appropriate tests for the Enemy() constructor and methods.

Completed creating an Enemy object along with the following properties.
Completed all the following methods for the enemy.


Fix 2D image conversion to 8 bit

Checklist
GitHub

[x] I've given this PR a concise, self-descriptive, and meaningful title
[x] I've linked relevant issues in the PR body
[x] I've applied the relevant labels to this PR
[x] I've assigned a reviewer

PR contents

[ ] I've consulted ivadomed's internal developer documentation to ensure my contribution is in line with any relevant design decisions
[ ] I've added relevant tests for my contribution
[ ] I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description
IVADOMED's implentation of loading 2D images (eg histology) has a bug where if 16bit TIFs (maybe other formats too, only one tested) are loaded,

the image isn't properly converted to 8 bits and instead gets "cut off",

This proposed fix should do the conversion properly and resolve this issue, which was first raised in AxonDeepSeg,

Linked issues
https://github.com/axondeepseg/axondeepseg/issues/737

To test, maybe I/we should apply these changes to the IVADOMED code in an ADS environment, and test that the segmentation runs correctly. I've so far only tested the change in a Python shell outside of the ADS workflow

Thanks @hermancollin !

Note that we still have this warning when we apply the model, at which stage the image is loaded in ivadomed.

I prefer a warning than an empty image =)
From the tests though, it seems like I need to use a different syntax as IVADOMED pulls a more recent version of Pillow,
TypeError: The keyword `as_gray` is no longer supported.Use `mode='F'` for a backward-compatible result, or  `mode='L'` for an integer-valued result.

I'll have to test to see if I resolve it in IVADOMED with this new syntax, that it doesn't break when we then later on import it from ADS's environment.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 74.269%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4676

Relevant Lines:
6296

💛  - Coveralls

I just tested a 16bit image and it segmented well (i.e. ivadomed side ok) but napari didn't display it correctly (meaning changes needed on the ADS side). So this IVADOMED issue can be closed now, we'll deal with with the rest on the ADS repo!

@mathieuboudreau As far as I remember, #1297 was supposed to fix imageio issues by migrating to v3 essentially combining this PR & #1292 😅

I forgot to show the images in my last comment:
Here's the raw image:

And them loaded in napari and segmented masks:

Lovely!!! 🚀