Why use '.js' on bower package?

Very nice lib, but, I'm trying to use it in a rails project, and I'm getting some problems:

I couldn't get how to install it manually, it depends from some libs and this is not very well documented;
I couldn't use rails-assets for it, because the name of it on bower have the dot char, which is an invalid name for a ruby gem. This could be handled on rails-assets gem generator of course, but I don't really know which are the best practices for naming for bower packages.

So, if you could just explain which libs you depend from, to some other people that want to install it manually, it would be very helpful. The second point is optional, but IMHO it would be better a name without dot (PS: why not just 'dragula', since this package name is not in use on bower yet)

dragula yields EDUPLICATE when I attempt to register it. To install it manually grab the files in dist folder.

Sorry, but just get the files on dist, didn't work for me. I'm trying to use them with rails asset-pipeline, probably you handle the dependencies in a way that the asset pipeline can't get...
I'll try a little more sometime, for now, I can't spend more time investigating this things.

Just drop the script in a blank HTML page and you'll see it works well. This has nothing to do with dragula

I know it hasn't, it's just the way you handle your dependencies that are incompatible with rails asset pipeline, when I get something more on it, I'll let you know.

FWIW, dragula on bower is now registered as dragula, no dot


Create 1y24lMaeLch6jPtLCqHgJz?si=80ff908f1c554312

Whoops, it looks like you deleted the old file without adding the new one!

Sorry Mack, I'll be honest I have zero clue what I'm doing I just made this account to try and archive a Spotify playlist but I quickly realized I'm in over my head, and am just going to do it manually. So sorry for the bother, if I need to delete anything to get it out of your way let me know.

So sorry for the bother

You're not a bother! Apologies if I gave you that impression. To save you additional trouble, I'll go ahead and add the playlist myself (and close this PR). Thanks for contributing!

So sorry for the bother

You're not a bother! Apologies if I gave you that impression. To save you additional trouble, I'll go ahead and add the playlist myself (and close this PR). Thanks for contributing!

No not at all you've been great, I really appreciate your patience and willingness to help. Thanks so much for adding it!

Hey @hackjilton! This is Mac from https://spotifyplaylistarchive.com project, which uses mackorone's repository as a data source and enables users less experienced with Git and GitHub to browse snapshots with more ease.
I've just introduced a new page called Get playlist's ID from URL, which allows you to paste a Spotify playlist link and grab its ID without you having to worry about doing it manually.
Feel free to give it a go, and let me know about your experience! If you believe something needs to be improved - just let me know and I'll sort it out!


fix(auth): missing auth string in download release

I was facing some 404 when trying to download release from private organization repository.
It now use the asset url + auth string instead of raw browser_download_url

@marmorag would you mind rebasing this?

It would be nice to have this fix merged @marmorag


New Rails app - Puma config not found

I just created a new Rails application with this gem, then runned docker-compose up --build.
Log:
website_1   | /usr/local/bundle/gems/puma-3.11.2/lib/puma/dsl.rb:41:in `read': No such file or directory @ rb_sysopen - config/puma.rb (Errno::ENOENT)
website_1   | 	from /usr/local/bundle/gems/puma-3.11.2/lib/puma/dsl.rb:41:in `_load_from'
website_1   | 	from /usr/local/bundle/gems/puma-3.11.2/lib/puma/configuration.rb:192:in `block in load'
website_1   | 	from /usr/local/bundle/gems/puma-3.11.2/lib/puma/configuration.rb:192:in `each'
cable_1     | ERROR: No application configured, nothing to run
website_1   | 	from /usr/local/bundle/gems/puma-3.11.2/lib/puma/configuration.rb:192:in `load'
website_1   | 	from /usr/local/bundle/gems/puma-3.11.2/lib/puma/launcher.rb:59:in `initialize'
website_1   | 	from /usr/local/bundle/gems/puma-3.11.2/lib/puma/cli.rb:68:in `new'
website_1   | 	from /usr/local/bundle/gems/puma-3.11.2/lib/puma/cli.rb:68:in `initialize'
website_1   | 	from /usr/local/bundle/gems/puma-3.11.2/bin/puma:8:in `new'
website_1   | 	from /usr/local/bundle/gems/puma-3.11.2/bin/puma:8:in `<top (required)>'
website_1   | 	from /usr/local/bundle/bin/puma:23:in `load'
website_1   | 	from /usr/local/bundle/bin/puma:23:in `<main>'
cable_1     | Puma starting in single mode...
cable_1     | * Version 3.11.2 (ruby 2.4.3-p205), codename: Love Song
cable_1     | * Min threads: 0, max threads: 16
cable_1     | * Environment: development
sidekiq_1   | 2018-02-19T03:02:18.016Z 1 TID-gtbg1z3z5 INFO: ==================================================================
sidekiq_1   | 2018-02-19T03:02:18.016Z 1 TID-gtbg1z3z5 INFO:   Please point sidekiq to a Rails 4/5 application or a Ruby file
sidekiq_1   | 2018-02-19T03:02:18.016Z 1 TID-gtbg1z3z5 INFO:   to load your worker classes with -r [DIR|FILE].
sidekiq_1   | 2018-02-19T03:02:18.016Z 1 TID-gtbg1z3z5 INFO: ==================================================================
sidekiq_1   | 2018-02-19T03:02:18.016Z 1 TID-gtbg1z3z5 INFO: sidekiq [options]
sidekiq_1   |     -c, --concurrency INT            processor threads to use
sidekiq_1   |     -d, --daemon                     Daemonize process
sidekiq_1   |     -e, --environment ENV            Application environment
sidekiq_1   |     -g, --tag TAG                    Process tag for procline
sidekiq_1   |     -i, --index INT                  unique process index on this machine
sidekiq_1   |     -q, --queue QUEUE[,WEIGHT]       Queues to process with optional weights
sidekiq_1   |     -r, --require [PATH|DIR]         Location of Rails application with workers or file to require
sidekiq_1   |     -t, --timeout NUM                Shutdown timeout
sidekiq_1   |     -v, --verbose                    Print more verbose output
sidekiq_1   |     -C, --config PATH                path to YAML config file
sidekiq_1   |     -L, --logfile PATH               path to writable logfile
sidekiq_1   |     -P, --pidfile PATH               path to pidfile
sidekiq_1   |     -V, --version                    Print version and exit
sidekiq_1   |     -h, --help                       Show help
sidekiq_1   |
twitalytics_website_1 exited with code 1
twitalytics_sidekiq_1 exited with code 1
twitalytics_cable_1 exited with code 1

Hey, please excuse me. I created a new Rails app with the gem and now it works.

Ok, I'm closing this because I'm thinking something changed in the first app that you made which is unrelated to what this gem produces.


Add the snowflake receiver

Picking up the work by @greatestusername-splunk from https://github.com/signalfx/splunk-otel-collector/pull/5722

Thanks for putting this up @pjanotti !


New release?

4.1.0 was released in 2017, it's now 2019, it would be nice if a new release was created 👍

Will the docker images work on Windows or do they require Linux (new to containers/Docker, so sorry if this is a dumb question)?

They require linux

That's why a zip release is welcomed 👍 I've been using Exceptionless since the beginning, please don't forget about the users not being able to (or want to) use Docker.

Any specific version/distribution of linux?

They are just running linux containers of which you can run on windows too (or should be able to (https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/linux-containers). We don't know what the deployment methods will be for release, we want it to be super easy for everyone to install and upgrade and manage. Docker really makes that really easy and a lot of people have told us that as well. You can clone master right now and just do docker-compose up and run everything which is awesome :).

We got the health checks out there in prod and will be making minor tweaks here and there. Release should be incoming soon.

Glad to hear, looking forward to that, thanks for the update @niemyjski!

Any date @niemyjski? Maybe not close this issue until it's released? 👍

We are code complete now and have been running it in production for two weeks now without any issues. We have decided that we will tag a release on GitHub when we have docs documenting the new configuration (migration), running with docker-compose, as well as helm. Please use the docker images located here for a stable 5.x build. These should work on both windows and linux and we will do additional testing to ensure it's a smooth migration.
We understand that we traditionally released a zip release with artifacts, but going forward with the 5.x release we are only going to release via docker images. We have limited resources to support both models and this is the future industry wide. This will allow everyone to seamlessly upgrade or downgrade with ease while ensuring configuration and dependencies are running correctly thus reducing troubleshooting. We are going to spend time updating the documentation to make this process easier.
Please note that if you wish to deploy with the traditional model, you can clone the repository, build the project and deploy the artifacts as you always have.

I can't use Docker so it's a shame that there will not be a zip release anymore. I've tried in the past to create a combined version with UI (similar to current zip) but couldn't get it to work. Some guide on that would be welcome if you don't want to release a zip anymore.

Are there any specific reasons/limitations that you cannot use docker? I'd like to understand this more. You'd need to compile the project manually and then copy the build artifacts. I'd say if you want to use Exceptionless outside of docker the easiest way is going to be pull down the code, build it in release mode and then copy the Exceptionless.Web artifacts and host it like you would an asp.net core website. You'll want to run jobs in process or you'll need to create one or more additional website instances for jobs.

I already use the virtualization from CPU and docker doesn't run as it needs Hyper-V. I also don't want to loose all the data I already have in Exceptionless (which is quite a lot), and as there's no good way to keep existing API keys I'd rather use the existing data.
A few weeks ago I've tried to build project (seemed to build OK) and UI, but UI only showed blank page with tons of errors in console. I'll have to retry this some day I think...

We need to dig into this further and document the process, but I believe all you'd need to do is ensure nested virtualization is enabled and run your docker image on one of the vms or on the main machine. You don't have to lose any elastic data. You can use your existing elastic infrastructure and update configuration to point to it.
If you could log any issues you are having with trying to build that would be greatly appreciated.

I cannot run Docker as I already use the virtualization features of the CPU for other purposes and Hyper-V would block that. Due to other requirements this is not possible to change at the moment. I suspect there are more people not able to run docker, so that's why a zip release is still welcome.
(I could indeed reuse Elastic but then the point of running it in containers would be even less as it would just be for hosting)
I'll have to take another look at building and combining everything here but I guess I have to continue to run the old version for now...

OK, I had some time to further look into this and I've managed to combine this project and the UI (still needs a little more testing but looks very promising). For it to work, there needs a little bit of code added to this project in order to serve the .less files. Nothing major, just a few LOC. Would you accept a PR for that?
Furthermore, I'm not sure if this is normal for heartbeats (through web browser)? This also happens in my local docker instance.
XHR GET<EMAIL_ADDRESS>[HTTP/1.1 200 OK 3ms]
->
XML Parsing Error: no root element found
Location<EMAIL_ADDRESS>Line Number 1, Column 1:
Anyway, what I did (if someone else needs it):

Build Exceptionless (this solution) and publish Exceptionless.Web on new profile, Release / netcoreapp2.2 / Self-Contained or Framework Dependent / win-x64 (or whatever you need there). This takes some time to first publish, be patient. You will also need to copy appsettings.yml and set whatever you need.
Open Exceptionless.UI/src folder and run npx bower install.
Copy everything from UI to the published Exceptionless.Web/wwwroot. You don't need all the grunt stuff.

If you use IIS, make sure you set app pool to No Managed Code and install ASP.NET Core IIS package.

OK, I had some time to further look into this and I've managed to combine this project and the UI again. For it to work, there needs a little bit of code added to this project in order to serve the .less files. Nothing major, just a few LOC. See the PR for that.
Furthermore, I'm not sure if this is normal for heartbeats (through web browser)? This also happens in my local docker instance.
XHR GET<EMAIL_ADDRESS>[HTTP/1.1 200 OK 3ms]
->
XML Parsing Error: no root element found
Location<EMAIL_ADDRESS>Line Number 1, Column 1:
Anyway, what I did (if someone else needs it):

Build Exceptionless (this solution) and publish Exceptionless.Web on new profile, Release / netcoreapp2.2 / Self-Contained or Framework Dependent / win-x64 (or whatever you need there). This takes some time to first publish, be patient. You will also need to copy appsettings.yml and update it to whatever you need.
Open Exceptionless.UI/src folder and run npx bower install & npx bower install & npx grunt build.
Exceptionless.UI/src/dist to the published Exceptionless.Web/wwwroot.
Update app.config.xyz.js with whatever you need.

That should do it 👍
If you use IIS, make sure you set app pool to No Managed Code and install ASP.NET Core IIS package.

@niemyjski I've noticed that since I've upgraded to this new version, no new data is shown in UI anymore. The storage/archive/.. and storage/q/... (this one contains a few thousand empty folders) are huge and I can see they're getting filled with new data. So for some reason the data isn't propagated to the UI. I'm not that knowledgeable about the inner workings of Exceptionless, but I'm guessing this has something to do with the jobs. Or would it be something else? I have RunJobsInProcess: true in appsettings.yml and tried to restart the site but that didn't work. I can see the GeoLite2-City.mmdb getting updated so at least some of the jobs are working.
Going through the log, I've noticed this is repeatedly logged:

System.ApplicationException: Error creating index events-v1-2019.03.11: Server: (400) Type: mapper_parsing_exception Reason: "Failed to parse mapping [events]: Root mapping definition has unsupported parameters:  [_size : {enabled=true}]" CausedBy: "Type: mapper_parsing_exception Reason: "Root mapping definition has unsupported parameters:  [_size : {enabled=true}]""
at Foundatio.Repositories.Elasticsearch.Configuration.IndexBase.CreateIndexAsync(String name, Func2 descriptor)    at Foundatio.Repositories.Elasticsearch.Configuration.DailyIndex.EnsureIndexAsync(DateTime utcDate)    at Foundatio.Repositories.Elasticsearch.ElasticRepositoryBase1.IndexDocumentsAsync(IReadOnlyCollection1 documents, Boolean isCreateOperation, ICommandOptions options)    at Foundatio.Repositories.Elasticsearch.ElasticRepositoryBase1.AddAsync(IEnumerable1 documents, ICommandOptions options)    at Exceptionless.Core.Pipeline.SaveEventAction.ProcessBatchAsync(ICollection1 contexts)

Did anything change in the elastic db that needs a manual update or something?

Seems my murmur size plugin got removed, no idea what caused that, it all looks good now 👍

Hey, sorry for the late reply. Are you using the ui in the master branch? Is any data being put into elastic search? Hmm, looks like it's failing to create the index because of the missing size plugin.. I'm assuming you are using the new docker image for elastic? @ejsmith we need to create our own elastic image.

I found a post of you somewhere on elastic search site with pretty much this error and I've reinstalled the murmur size plugin and after restarting exceptionless it immediately imported all the data into elastic and the UI is showing the new content again. I'm using non-docker elastic instance (just the installer).

I just wanted to let you know we just pushed a new major version :) https://github.com/exceptionless/Exceptionless/releases/tag/v5.0.0


Tier config with invalid tenant fails on rebalance with NPE

If a tier config is added with an invalid tenant, the table config update is succeeds but a rebalance of the table returns with an NPE. Then to find the exact error the controller logs need to be searched.
Is that intended as a tenant may not always be present? Or should adding a tier config that contains a tag which does not point to any instance fail when updating the table config?

I think we should add this check to the table config validation.
cc @klsince

trying to fix this issue with https://github.com/apache/pinot/pull/10705
btw, I couldn't reproduce NPE, but still saw that table config with non-existing serverTag could be added, which failed table rebalance but with error msg "No instance found with tag: A_OFFLINE".


Task: Add a button on the README page to deploy the whole platform

We want to add a button on the documentation to be able to initialize the portal deployment with just one click on AWS

After analysis there is no similar thing on Amazon side to deploy via a button.
There is the creation of a link to create a stack from a template (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-create-stacks-quick-create-links.html)
but Amazon constrains the URL to be a URL pointing to a template stored in an S3 :
TemplateURL Location of file containing the template body. The URL must point to a template (max size: 460,800 bytes) that's located in an Amazon S3 bucket. For more information, see Template anatomy.
The simplest solution to satisfy the need is to add a link to the cloudformation template file and to inform the 2 ways to create resources via the template (AWS console or AWS CLI)


Commit1

Hi
Committed a url that I believe is quite vital source of java development and news around it.
thanks
Umesh

Hi,
Your commit messages should tell about the changes. You have just mentioned commit1 which doesn't explain anything about the changes.

Closing this PR for now :+1:


17.06: improve the Docker for Mac networking workaround

Proposed changes
In Docker for Mac 17.05 and earlier, there is no easy way for a container to contact a service running on the host (such as a local HTTP proxy) without knowing the host's IP addresses. The workaround in the docs is to add a new IP alias and use that.
In the upcoming 17.06 release of Docker for Mac, there is a special internal DNS name docker.for.mac.localhost. This patch replaces the IP alias workaround with a note about the new DNS name.
Unreleased project version (optional)
This only applies to Docker for Mac 17.06.

I tried changing the base but you need to rebase it locally.

@mstanleyjones I've rebased onto vnext-engine and changed the base of the PR in github -- hopefully this looks ok.


Python server 4x slower than C++ async one?

Hi, I ran two greeter server examples: one uses python, and the other uses c++ async. And I slightly modified the c++ async client to say hello for 10000 times:
// ...
  GreeterClient greeter(grpc::CreateChannel(
      "localhost:50051", grpc::InsecureChannelCredentials()));
  const int T = 10000;
  long st = gettime();  // calls gettimeofday(&ts,NULL), return ms
  std::string user("world");
  for (int i = 0; i < T; ++i) {
    greeter.SayHello(user);
  }
  long ed = gettime();
  long d = ed-st;
  printf("tested %d times\ntotal %ldms\naverage %.6fms\n", T, d, static_cast<double>(d) / T);
// ...

The c++ async server and client were compiled with -O2. I ran tests on macOS and Ubuntu 14.04, both with grpc 1.0. On macOS, grpc is installed using brew. On Ubuntu, grpc is installed from the source code. On both platform, the python binding is installed using pip. And here is the result:

OS
server
total time
average time per rpc

macOS
c++ async
1202ms
0.1202ms

macOS
python
4445ms
0.4445ms

Ubuntu
c++ async
933ms
0.0933ms

Ubuntu
python
4340ms
0.4340ms

It seems that python server is 4x slower than c++ async one. Is it really true, or just for me? Will this be fixed?

Oh, hey, cool, Python's only 4x slower than C++.
I'm going to assume that you were running this all locally and that there was no network variability. Then you have a loop going, wherein Python is going to increment reference counts, decrement reference counts, allocate, deallocate, hash-lookup, acquire/release the GIL, and error check, again and again and again (and that's all in the language runtime, outside anything gRPC can do without becoming an even thinner wrapper around the core and telling users to not implement their servers in pure Python), things that C++ as a language doesn't do without the developer's explicit instruction (and thus things that C++ devs can avoid). So, Python's going to be slower, and for idiomatic implementations of the same algorithm vanilla-Python will almost always (I'd even say 'always') be slower.
I can't specifically point at anything without running profiles, but it's unreasonable to expect Python implementations to be competitive performance-wise with tuned C/C++, even if it's only a thin-wrapper.


eDSL: Tidy memories

This PR tidies up the way we perform loads and stores to 1-d memories of both flavors (seq and comb). The helpers are now unified, with a flag to indicate whether the memory in question is combinational. We can even imagine adding a warning message that hints that we generally encourage the use of seq memories.

@calebmkim just a heads up that we have exactly two files that are using combinational memories via the eDSL. Those are gen_exp and gen_ntt_pipeline. Take a look if you'd like; changing them over to seq should be easy if you want!

Alrighty I have carved that one comment out into its own issue. I'm merging this PR.


lf2: Add version 2.0a

Little Fighter 2 (often abbreviated as LF2) is a free fighting game that is well-known in the Chinese-speaking region.  (homepage) (Wikipedia)
Notes:

checkver/autoupdate is not needed because LF2 has not been updated since 2009.

The installer from the official source cannot be properly extracted. Also the silent switch (/S) causes error for some reason. Therefore I use a third-party source (azo freeware) instead. Is this acceptable?

I'm getting an error on startup on Windows 10:

I've found a post about that error message online but I'm not sure how well this applies to an application released in 2009.

I'm getting an error on startup on Windows 10:

I found that this problem can be solved by installing VCRedist 2005. (scoop install vcredist2005).
Also there will be an error if we start the application(lf2.exe) without setting working directory to the same path as lf2.exe. Therefore I added a PS-script so that shim-exes can work properly.
Thank you for testing it out!

I still can't get it to work after installing vcredist2005, but I'll merge it anyway as I suppose it works on your PC.


Document few additions introduced with 2020.05

Str now has .Date and DateTime coercers
Date.yyyy-mm-dd now takes a separator parameter, defaulting to -
Add Date.dd-mm-yyyy and Date.mm-dd-yyyy methods
Add Date.last-date-in-month and Date.first-day-in-month methods

We can probably update the "dd" check in the examples compilation to ignore mm-dd and dd-mm so we don't need to tag these methods.


Support watching a single node

Description

Fixes https://github.com/projectcalico/calico/issues/1739
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Thanks Casey!


[KOGITO-4798] Extracted Makefile test commands

https://issues.redhat.com/browse/KOGITO-4798
This is the first part of the PR. Another one will come to rhpam-kogito-operator to use this new test Makefile.
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[x] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster
[ ] You've added a RELEASE_NOTES.md entry regarding this change

/jenkins test


The deny_by_default TRUE setting should not block apigility admin

array(
    'zf-mvc-auth' => array(
        'deny_by_default' => true
    ),
)

If deny_by_default is set to TRUE, the application home route, Apigility admin, documentation route and the swagger documentation routes are also blocked. Is this really desirable?
If yes, what is an easy way to figure out what all the apigility admin controllers are?

I know it's a little bit late, but I think I have a better solution than add all of the zf-apigility-admin's controllers to the config file.
The ideia is to attach a listener to the \ZF\MvcAuth\MvcAuthEvent::EVENT_AUTHORIZATION event in order to allow any request from the zf-apigility-admin.
Here is the listener class itself.
Maybe we could turn this into a pull-request. What you guys say?
use Zend\EventManager\AbstractListenerAggregate;
use Zend\EventManager\EventManagerInterface;
use ZF\MvcAuth\MvcAuthEvent;

/**
 * This listener makes the zf-mvc-auth module allow all requests from zf-apigility-admin-ui when the 'deny_by_default'
 * flag is true.
 */
class AllowAllApigilityRequests extends AbstractListenerAggregate
{
    public function __invoke(MvcAuthEvent $authEvent)
    {
        $mvcEvent   = $authEvent->getMvcEvent();
        $routeMatch = $mvcEvent->getRouteMatch();

        if (!$routeMatch) {
            return;
        }

        if (strpos((string)$routeMatch->getMatchedRouteName(), 'zf-apigility') === 0) {
            /** @var \ZF\MvcAuth\Authorization\AclAuthorization $authorization */
            $authorization = $authEvent->getAuthorizationService();
            $authorization->allow($authorization->getRoles());
        }
    }

    /**
     * Attach one or more listeners
     *
     * Implementors may add an optional $priority argument; the EventManager
     * implementation will pass this to the aggregate.
     *
     * @param EventManagerInterface $events
     *
     * @return void
     */
    public function attach(EventManagerInterface $events)
    {
        $this->listeners[] = $events->attach(MvcAuthEvent::EVENT_AUTHORIZATION, $this, 2);
    }
}

This repository has been closed and moved to laminas-api-tools/api-tools-mvc-auth; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-mvc-auth/issues/22.


Slew function

Is it possible to add a SLEW to the CVs of each channel in the layout track "note" mode?
Perhaps add SLEW in the LENGTH tab by displaying a curve and allowing you to select the length of the SLEW.
SLEW is a curve logarythmic:
https://www.researchgate.net/figure/Slew-rate-control-for-Slow-Mode_fig19_237570362
Curve in bue and red
Thanks, Gil

do you mean the already present "slide" feature?

In fact, this could be an improvement to the "SLIDE" function by adding a parameter on the duration of the "SLIDE" because currently the "SLIDE" lasts the time of the note.
If the note in longuest, the slide also.
Musically, the actuel slide doesn't always give good results.

Have u tried changing the slide time in the sequence page?

Yes
However, the time slide acts on all notes, and it would be great if it could be defined per note.
Add a Time slide page in the NOTE tab
And then, if I currently lower the time slide to 0%, the amplitude of the note increases, for example:

at 50%, the CV note is at 1.8V
at 20% the CV note is at 4V
at 80%; the note is at 0.5V
-> it's no longer the same note, the sound is weird with high notes)

I've done the test with the PAM PRO ALM and the pitch of the note doesn't change if you change the time.

Hi,
Perhaps the SLIDE function could be left as it is for users who already use it.
Create a new SLEW function that can be selected and configured for each step.
This would add 2 features to the NOTE tab

SLEW
SLEW TIME
SLEW PROB, if possible

Thanks, Gil

due to memory limits It's very hard to impplement additional layouts, but I can see what we can do on it

So perhaps we might as well delete the glide function, which musically doesn't work properly.
Gil

Sorry,
SLIDE
So perhaps we might as well delete the SLIDE function, which musically doesn't work properly.


[Feature Request] Dark/light Theme switch support

Existing Component
No
Component Name
None
Description
just like other UI libraries, it is nice to have the light/dark theme support.

有自定义主题功能
https://elementui.github.io/theme-chalk-preview/#/zh-CN

@qingdengyue how are we supposed to dynamically swtich back and forth between a light and a dark theme when the user clicks on a switch for example:

is there a way I can have a element-variables.scss and another one called element-dark-variables.scss and switch dynamically between them?

Sorry, we have no plan to support this.
有在线主题编辑器：https://element.eleme.cn/#/zh-CN/component/custom-theme


Feature: Highlights feed page

This needs the following completed first
https://github.com/open-sauced/insights/issues/827
https://github.com/open-sauced/insights/issues/828
https://www.figma.com/file/OpVX6WT7dmWqnwRuEvADMF/OpenSauced-—-Insights-(insights.opensauced.pizza)?node-id=6180%3A7075&t=vWHWaxU7Z8POmO55-0

URL should be a insights.opensauced.pizza/feed


Is it possible to use Voucherify js SDK in Angular apps ?

It should be, but we do not recommend it since using SDK in Angular App would mean exposing your Voucherify API Keys to end-users.
We are recommending using Voucherify SDK on your backend services behind some kind of authentication.
If you really wish to use this SDK on front-end, then you should use:
const { VoucherifyClientSide } = require('@voucherify/sdk')

and use client side API Key pairs


[gitlab] JOBOWNERS update

What does this PR do?

Updates team attributions in the .gitlab/JOBOWNERS file.
Motivation

Redirect new jobs mistakenly being reported to wrong teams.
Additional Notes

n/a
Possible Drawbacks / Trade-offs

n/a
Describe how to test/QA your changes

n/a

/merge


changeset no longer works since master changed to main

I was working on this PR: https://github.com/FormidableLabs/urql/pull/904 and noticed that I can't use changeset command now.
➜  urql: yarn changeset
yarn run v1.22.4
$ /Users/dotansimha/Dev/urql/node_modules/.bin/changeset
🦋  error Error: Failed to find where HEAD diverged from master. Does master exist?
🦋  error     at getDivergedCommit (/Users/dotansimha/Dev/urql/node_modules/@changesets/git/dist/git.cjs.dev.js:51:11)
🦋  error     at async getChangedFilesSince (/Users/dotansimha/Dev/urql/node_modules/@changesets/git/dist/git.cjs.dev.js:69:22)
🦋  error     at async Object.getChangedPackagesSinceRef (/Users/dotansimha/Dev/urql/node_modules/@changesets/git/dist/git.cjs.dev.js:108:24)
🦋  error     at async add (/Users/dotansimha/Dev/urql/node_modules/@changesets/cli/dist/cli.cjs.dev.js:369:29)
🦋  error     at async /Users/dotansimha/Dev/urql/node_modules/@changesets/cli/dist/cli.cjs.dev.js:1008:5
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Hey,
I fixed it, this should be okay now when rebased with main.

It works now, thanks @JoviDeCroock

any workaround?


cluster wide http proxy with authentication not working in OKD 4.5 ga

Describe the bug
After configuration cluster wide proxy with authentication, network operator fail with error
"The configuration is invalid for proxy 'cluster'
(invalid httpProxy URI: parse http://user:pass@host:3128: invalid port ":pass" after host).
Use 'oc edit proxy.config.openshift.io cluster' to fix."

Loks like it bug.
The first group user:pass is recognized as host:port.
Version

OKD version: 4.5.0-0.okd-2020-07-14-153706-ga
vSphere IPI install method
How reproducible

Install OKD 4.5.0-0.okd-2020-07-14-153706-ga behind transparent proxy and after that update cluster wide proxy for proxy with authentication
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.5-e2e-aws-proxy/1295873283949858816
Log bundle

https://drive.google.com/file/d/1IqnMWwUn4EdTaB0cLinn_DAEPdOLUpxN/view?usp=sharing

The configuration is invalid for proxy 'cluster'

Where does that message come from? I don't see it anywhere in the logs. httpProxy is set to http://<IP_ADDRESS>:3128.


Sizes of app.js and vendor.js

Thanks for this repo, it's very helpful!  I was surprised after cloning and building unoptimised (npm run build) that the app.js file is 4.8MB, vendor.js is 5.45MB while common.js is only 4.65kB.  Even with the --optimize-minimize switch the app.js file is still 577kB.
Looking inside app.js there seems to be a lot of Angular in there, when I was expecting that to be in vendor.js.
I'm fairly new to WebPack, so I was wondering if someone could help me understand what is happening here.  If vendor modules required by the application are being bundled into app.js then what is the purpose of vendor.js?  Or if they should not be, then why is app.js so large?

Ok, I think I've worked out the problem....
Starting with everything fresh again, the webpack.config.js contains these lines:
  plugins: [
    new CommonsChunkPlugin({ name: 'vendor', filename: 'vendor.js', minChunks: Infinity }),
    new CommonsChunkPlugin({ name: 'common', filename: 'common.js', minChunks: 2, chunks: ['app'] })
  ],

And I get this output:
     Asset     Size  Chunks             Chunk Names
    app.js   4.8 MB    0, 2  [emitted]  app
 vendor.js  5.45 MB    1, 2  [emitted]  vendor
 common.js  3.65 kB       2  [emitted]  common
   app.map  5.11 MB    0, 2  [emitted]  app
vendor.map  5.91 MB    1, 2  [emitted]  vendor
common.map  3.68 kB       2  [emitted]  common

Removing the chunks property from the common chunk:
  plugins: [
    new CommonsChunkPlugin({ name: 'vendor', filename: 'vendor.js', minChunks: Infinity }),
    new CommonsChunkPlugin({ name: 'common', filename: 'common.js', minChunks: 2 })
  ],

Give this:
     Asset     Size  Chunks             Chunk Names
    app.js  7.31 kB    0, 2  [emitted]  app
 vendor.js  5.45 MB    1, 2  [emitted]  vendor
 common.js  3.65 kB       2  [emitted]  common
   app.map  8.14 kB    0, 2  [emitted]  app
vendor.map   5.9 MB    1, 2  [emitted]  vendor
common.map  3.67 kB       2  [emitted]  common

And finally putting both entries into the chunks property:
  plugins: [
    new CommonsChunkPlugin({ name: 'vendor', filename: 'vendor.js', minChunks: Infinity }),
    new CommonsChunkPlugin({ name: 'common', filename: 'common.js', minChunks: 2, chunks: ['app', 'vendor'] })
  ],

Gives this:
     Asset     Size  Chunks             Chunk Names
    app.js  7.31 kB       0  [emitted]  app
 vendor.js   652 kB       1  [emitted]  vendor
 common.js   4.8 MB       2  [emitted]  common
   app.map  8.14 kB       0  [emitted]  app
vendor.map   800 kB       1  [emitted]  vendor
common.map  5.11 MB       2  [emitted]  common

Which appears to be using the files correctly.

fixed by your pr https://github.com/AngularClass/angular2-webpack-starter/pull/159, thanks again

why common js is big size ? its downloaded to client side, its probably make slow  ?


[hardknott] gstreamer1.0-omx: rename bbappend to match new 1.18.0 version from oe-core

Be aware that this PR could be merged only after branching current master branch as gatesgarth.
Alternatively we can rename the bbappend to be completely version agnostic (as the same patches apply cleanly on 1.16.* and 1.18.*)
On side note LAYERSERIES_COMPAT_raspberrypi = "sumo thud warrior zeus dunfell gatesgarth"
should really be shortened to something people might actively use meta-raspberrypi layer with, e.g. since
36c3c2e7ca09806da460328767565bbf872a6ad8 it probably doesn't even parse with anything older than zeus (where gstreamer was upgraded to 1.16.*)

since we have dunfell branch, I think we should delete all entries up to dunfell in LAYERSERIES_COMPAT secondly, I think branching gatesgarth is good idea too.

@kraj shall we keep master for a while and do a late branching when we have incompatible changes? We've done that before and it worked well. It also helps in maintaining while there is nothing incompatible in between master and hardknott.

@agherzan it's not about "nothing incompatible in between master and hardknott." but between gatesgarth and hardknott/master, right now there is no meta-raspberrypi branch compatible with gatesgarth release, that's why gatesgarth has to be branched from commit before this PR was merged.

Shoot. Missed that one. Thanks for pointing it out. I'll branch.

Easy job: https://github.com/agherzan/meta-raspberrypi/tree/gatesgarth. Now I'll merge this in master. Cheers for this.

@kraj shall we keep master for a while and do a late branching when we have incompatible changes? We've done that before and it worked well. It also helps in maintaining while there is nothing incompatible in between master and hardknott.

@agherzan I think we should branch now, since there are these gstreamer changes which we need to accommodate
and I don't like the idea of having multiple versions.

@kraj are you referring to gatesgarth or harnknot?

hardknott branch should be created in +- 6 months, not now, I'm pretty sure he was referring to gatesgarth :)

@shr-project We also need to refresh this PR:

commit da390c5a3a8a9e7393b59de7abce997bb7d8cba4
Author: Alexander Kanavin<EMAIL_ADDRESS>Date:   Mon Nov 2 17:48:55 2020 +0100
gstreamer1.0: upgrade 1.18.0 -> 1.18.1

@kraj shall we keep master for a while and do a late branching when we have incompatible changes? We've done that before and it worked well. It also helps in maintaining while there is nothing incompatible in between master and hardknott.

@agherzan I think we should branch now, since there are these gstreamer changes which we need to accommodate
and I don't like the idea of having multiple versions.

I am saying to branch gatesgarth and master is hardknott as of now.

@kraj That's what I thought. gatesgarth was already created. So we are good with that.

@agherzan it's named gstreamer1.0-omx_1.18%.bbappend so it works with current master as well (unless you want me to update commit message to say 1.18.1 instead of 1.18.0.
Or does one of those patches fail to apply on 1.18.1? I need to double check if one of my world build already finished with 1.18.1 in oe-core.

Just give it a sanity check just in case. No need to deal with the commit log if it works.

@agherzan it's named gstreamer1.0-omx_1.18%.bbappend so it works with current master as well (unless you want me to update commit message to say 1.18.1 instead of 1.18.0.
Or does one of those patches fail to apply on 1.18.1? I need to double check if one of my world build already finished with 1.18.1 in oe-core.

1.18% is fine.

Just give it a sanity check just in case. No need to deal with the commit log if it works.

only gstreamer1.0 was upgraded, no change in gstreamer1.0-omx, so it should be fine

@shr-project Cheers for the check and PR. Merged.


catkin_make_isolated --install --use-ninja --pkg cartographer_ros     error

I didn't encounter this error before, following is log
 Installing: /home/xiaoqiang/Documents/ros/install_isolated/share/cartographer_ros/launch
-- Installing: /home/xiaoqiang/Documents/ros/install_isolated/share/cartographer_ros/launch/software_institute.launch
-- Up-to-date: /home/xiaoqiang/Documents/ros/install_isolated/share/cartographer_ros/launch/\
CMake Error at cmake_install.cmake:142 (file):
  file INSTALL cannot set permissions on
  "/home/xiaoqiang/Documents/ros/install_isolated/share/cartographer_ros/launch/\"

FAILED: cd /home/xiaoqiang/Documents/ros/build_isolated/cartographer_ros && /usr/bin/cmake -P cmake_install.cmake
ninja: build stopped: subcommand failed.
<== Failed to process package 'cartographer_ros':
  Command '['/home/xiaoqiang/Documents/ros/install_isolated/env.sh', 'ninja', 'install']' returned non-zero exit status 1

Reproduce this error by running:
==> cd /home/xiaoqiang/Documents/ros/build_isolated/cartographer_ros && /home/xiaoqiang/Documents/ros/install_isolated/env.sh ninja install

Command failed, exiting.

why is install_isolated/share/cartographer_ros/launch/\  created, very strange. How to solve this, I remove the launch folder, but it didn't work.

Did you check the permissions of your Linux user account for these directories?

Did you check the permissions of your Linux user account for these directories?

Did you check the permissions of your Linux user account for these directories?

I did. But never mind, I'm using the other computer, so I close this issue

Did you check the permissions of your Linux user account for these directories?

I did. But never mind, I'm using the other computer, so I close this issue


Bump aes-gcm and chacha20poly1305

@mcginty Any chance this could be merged (and released?)

I just was going through my dep tree, looking for anything I could help out by bumping and found this again. Ping @mcginty, as a friendly reminder, if you have the time :)

I am shocked to discover I have once again noticed this, once again gotten to work on a quick commit to help out and contribute, and once again noticed I already did.
I really should work on improving my memory, yet at least it's a decent reminder to ping @mcginty :sweat_smile:

Ahhhh my bad!!


ERROR! 'notify' is not a valid attribute for a Block

Question
Someone facing this issue?
ERROR! 'notify' is not a valid attribute for a Block
The error appears to be in '/home/cis_rhel7/roles/RHEL7-CIS/tasks/prelim.yml': line 204, colum
n 3, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:

name: "PRELIM | Optional | If IPv6 disable to stop chronyd listening"
^ here

**Environment:
ansible 2.10.8
config file = /home/ansible/cis_rhel7/ansible.cfg
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]

hi @achebib
Thank you for taking the time to raise the issue and providing this most helpful information.
Unfortunately it didn't get a chance to run to show that the minimal version of ansible is 2.11.1 that is supported. It failed while loading the content hence why you have the error.
2.10 is now quite old it went EOL May 2022. We do try and keep it as backwardly compatible as possible but unfortunately this is not possible in this case for the version you are using.
It maybe just a matter of moving it to the task for the one control, but other items may then fail.
kindest
uk-bolly

hi @achebib
I will close this issue, for reference i have managed to run a newer version of python on a rhel7 control node using  virtual environment, which may help you.
many thanks
uk-bolly


v1.12 Backports 2023-05-15

[ ] #20236 (@joestringer)

had to rerun make -C Documentation update-helm-values

[ ] #25215 (@youngnick)

⚠ Dropped since it has a bug

[ ] #25352 (@jrajahalme)

Once this PR is merged, you can update the PR labels via:
for pr in 20236 25352; do contrib/backporting/set-labels.py $pr done 1.12; done

or with
make add-labels BRANCH=v1.12 ISSUES=20236,25352

/test-backport-1.12

/test-backport-1.12

/test-1.22-4.9

/test-backport-1.12

/test-backport-1.12

/test-backport-1.12

/test-backport-1.12

/test-1.24-net-next

/ci-l4lb-1.12


 (:

Thanks!


chore: promote jx3-python-app to version 0.0.3

chore: promote jx3-python-app to version 0.0.3
this commit will trigger a pipeline to generate the actual kubernetes resources to perform the promotion which will create a second commit on this Pull Request before it can merge

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@testingcicdonk8s: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

verify
76febd8a8fce03eab784b0d271063d969ab7b341
link
/test verify

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Sidebar layout

Based on our call I created draft of menu that would make sense to me.
- What is Kubewarden? (rename from "Introduction")

- Getting Started
  - Overview (main components from Tutorials -> QuickStart)
  - Install & Upgrade
    - Install Kubewarden stack
    - Deploy policies (default PolicyServer, recommended policies, mention ArtifactHub)
    - Supported Upgrade path
    - Other methods
      - Fleet
      - AirGap
      - Without Kubernetes (Raw)

- How-to Guides
  - Operators
    - Using policies (create policy, monitor -> protect mode)
    - Configuration
      - Configure Policies
      - Configure Policy Server
        - Using custom CA
        - Using private registries
      - Telemetry
    - Audit Scanner
    - UI Extension
    - Airgap (remove, move to installation)

  - Developers
    - Writing policies
      - Rust, Rego, ...
    - Testing policies
    - Publishing policies
      - ArtifactHub

  - Advanced topics
    - Kwctl
    - Policies (could be in How-to -> )
      - Mutating policies
      - Context aware
      - Raw policies
    - Security
      - Secure supply chain
      - Custom certificate authorities
      - Verifying Kubewarden
    - PSP migration

- Reference Guides (split KW vs * comparison and other non-reference into new section)
  - CRDs
  - Architecture
  - Dependency matrix
  - KW vs OPA Gatekeeper
  - KW vs NeuVector (add here?)
  - remove Thread model (move to Advanced topics -> Security -> Thread model)
  - remove OCI registry support (move to How-to -> Developers -> Publishing policies)?
  - remove Operator Manual (move to How-to -> Operators)
  - remove Rancher UI Extension (move to How-to -> UI Extension)
  - remove Airgap (move to Getting Started -> Installation -> Airgap)
  - remove Monitor mode (move to Howto -> Operators -> Using Policies)
  - remove Fleet (move to Getting Started -> Installation -> Fleet)
  - remove Upgrade path (move to Getting Started -> Installation & Upgrades -> Upgrade path)
  - remove Policy evaluation timeout (move to HowTo -> Operators -> Configuration -> Policy evaluation timeout)

- Tutorials (remove whole section)
  - Quick start (move to Getting Started -> Overview)
  - Common tasks (move to How-to -> Advanced topics -> kwctl)
  - Writing policies (move to How-to -> Developers -> Writing policies)
  - Testing policies (move to How-to -> Advanced topics -> kwctl),  rename from "testing" - it sounds like QA work
  - Publish policies to Artifact Hub (move to How-to -> Developers -> Publish policies)
  - Verifying Kubewarden (move to How-to -> Advanced topics -> Security)

- Explanations (remove whole section)
  - Mutating policies (move to How-to -> Advanced topics -> Policies)
  - Distributing policies (move to How-to -> Developers -> Publishing policies)
  - Context aware policies (move to How-to -> Advanced topics -> Policies)
  - Comparisons (move to Reference KW vs ...)
  - Audit Scanner (move to How-to -> Operators -> Audit Scanner)

Thanks @kravciak, a great start. @kubewarden/kubewarden-developers please add comments/thoughts/contributions.

Thanks for giving this a loop!
My 2 cents (wow is this difficult).
I wouldn't remove Tutorials and Explanations, but keep within the Divio system.
Diataxis may not be perfect, but that way we don't need to think and iterate on
the docs structure.
I would make the How-Tos the one separated in Persona sections:
- How-tos
  - Operators
    - Installation & upgrade
      - Helm
      - Fleet
      - Airgap
    - Configuring Policies (create policy, monitor -> protect mode)
    - Configuring Policy Servers
      - Using custom CA
      - Using private registries
    - Telemetry
    - Audit Scanner & PolicyReports
    - UI Extension
    - Verifying Kubewarden
  - Policy users
    - Obtaining policies
    - Testing policies
  - Policy authors
    - Writing policies
    - Publishing policies

I would keep Tutorials as a way to learn about Kubewarden aspects.
They help when you don't even know what's possible with Kubewarden.
- Tutorials:
  - Quickstart
  - Using kwctl
  - Deploying mutating, context-aware policies
  - Using PolicyReports (for the future)

I would make Explanations more dry, without steps. If there are a lot of steps
that don't explain, it's a How-To. Link more to Explanations from other pages in the future.
- Explanations:
  - Mutating policies
  - Context aware policies
  - Comparisons
  - Audit scanner limitations

I would start with the Reference guides as low hanging fruit and try to flatten it:
Reference guides:
- Reference Guides
  - CRDs
  - Architecture
  - Dependency matrix
  - remove KW vs OPA Gatekeeper (move to Explanations)
  - Thread model
  - OCI registry support
  - Policy Specification
  - remove Operator Manual (move to How-to -> Operators)
  - remove Rancher UI Extension (move to How-to)
  - remove Airgap (move to Getting Started -> Installation)
  - remove Monitor mode (move to Howto -> Operators)
  - remove Fleet (move to HowTo -> Installation -> Fleet)
  - Custom Certificate authorities (from How-Tos)
  - Upgrade path
  - remove Policy evaluation timeout (move to Explanations -> Policy evaluation timeout)

I would move the Quick start out of tutorials and merge it with What is Kubewarden? (rename from "Introduction"). Leaving the What is Kuberwarden  as the end section of the Quick start. But still keeping the Tutorial section for all the others. Just to have a very low friction  way to start learning Kubewarden.
I'm not sure if I would split How-to guides using personas. Sometimes I think some people do not know what exactly persona in the Kubewarden world they belong to. Or our persona does not match what they think it is. However, everybody know what problem needs to be solve. Therefore, I would remove the personas categorization. But this does not means that we should not have personas in mind while writing the docs. ;-)
Another thing that is not clear to me is the Advance topics section. What define an advanced topic? If I'm writing a docs about a "obscure" and "advance" policy feature. Where I put it? How-to or Advanced topics?  That's where I think Diataxis system helps to define where to put stuff. However, I don't think we need just the 4 proposed sections. Maybe is a matter of renaming it. But I would like to ensure that I understand the goal of the section.

, I would remove the personas categorization. But this does not means that we should not have personas in mind while writing the docs. ;-)

Good point, I agree with this.

I like @viccuad's proposal, with the twist suggested by @jvanz above :+1:

From my side, I'm ok with any of the suggestions (even if I have listed my preferences) because they are an improvement of the status quo.

My first draft

title: Proposed layout
Kubewarden

What is Kubewarden

Quick start

Tutorials

Writing policies
Testing policies
Publishing policies
Verification
What next?

Explanation

Mutating policies

Context-aware policies

Distributing policies
?? Can the content for distributing policies here be incorporated into the tutorial page for publishing? This will be me not understanding the distinction between distributing and publishing of policies.

Comparisons

Kubewarden vs OPA Gatekeeper

Audit Scanner

Limitations
Policy reports

Kubewarden architecture

How-Tos

Installation, upgrades and removal

Other installation scenarios
Upgrading

Supported upgrade paths

Removal
Dependency matrix (moved from Reference)

Common tasks (?? split into separate documents, maybe this should be 'Administration' in Tutorials?)

Find policies
Install and test policies
Using kwctl
Enforce policies
What next?

PSP Migration
Pod security admission
Secure supply chain
Custom certificate authorities
Raw policies
Audit scanner installation (?? Should this be here)

Reference

Operator manual (from How-tos, merge with the one already here)

Configuring policy servers

Custom CAs
Private registries

Configuring policies
Quick start guides

OpenTelemetry
Metrics
Tracing

Air gap

Requirements
Installation

Metrics Reference
Custom Resource Definitions (CRDs)
Verification configuration

Policy specification
OCI Registry Support
Threat model
Rancher UI extension

Installation
Monitoring
Tracing

Monitor mode
Rancher Fleet
Policy evaluation timeout

Agree on the distribution. Some comments:

?? Can the content for distributing policies here be incorporated into the tutorial page for publishing? This will be me not understanding the distinction between distributing and publishing of policies.

I think it's fine, and since there are steps, it feels more like a tutorial than an explanation anyways.

Common tasks (?? split into separate documents, maybe this should be 'Administration' in Tutorials?)

Agree, common tasks for whom? If not in tutorial, I would prefer them flat in How-Tos.

Audit scanner installation (?? Should this be here)

I prefer it there, but could go in either. Tutorials IMHO should be for when one doesn't have any idea of what they need to know, How-Tos for when one knows what they need to do but don't know how. And I'm not sure Audit Scanner installation counts as tutorial.

Reference

IMHO it should be flat and full of reference docs only, no steps. E.g: "Configuring policy servers", "metrics", "tracing", "airgap", "Rancher UI extension" all have steps, I feel they belong in How-Tos. If they explain a specific file or resource format, that part should be moved to "Reference" and the originating page should be made to link the new reference page.

LGTM. :-)

Comparisons (?? Does this need a sub-section? Are more coming?)

At least we will have Kyverno, maybe more. I'm ok flattening though for discoverability. Or having the subsections open by default.
LGTM :).

OK, all there now. I am closing as done. The output (https://github.com/kubewarden/docs/issues/332#issuecomment-1923873589) will be used in the new card for the actual docs code change issue.


chore: initialize klog flags

What this PR does / why we need it:
Initializes logger flags like -logtostderr and -v.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #113
Special notes for your reviewer:
Do we want to change any of the defaults?
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
Release note:

initialize logger flags

/cc @chuckha

/assign @vincepri


Find components by name

Idea:
Is there a way to tell in scripting all the components the objects have?
for example, in save editor I can drop the player_female.entity and see all the components, the components can be called with the following script:
player:FindComponentByName(CName.new("TPPRepresentation")) -- Car/Body component
player:FindComponentByName(CName.new("root")) -- Animation Component

-- BUT ALSO (THIS IS FOR FEMALE PLAYER ONLY)
player:FindComponentByName(CName.new("body")) -- Mesh Component

But it would be nice if there is a function to see all the components on a certain class, not only player.
And by the why, root component have all sorts of UKNOWN TYPES.

Also there is a BUG in these components related to props.
For example:
local comp = player:FindComponentByName(CName.new("someComponent"))
print(#comp.somePropArray) -- has array of classes
print(comp.somePropArray[1].x) -- prints 1
comp.somePropArray[1].x = 20
print(comp.somePropArray[1].x) -- still prints 1

WORKAROUND FOR NOW:
local comp = player:FindComponentByName(CName.new("someComponent"))
print(#comp.somePropArray) -- has array of classes
print(Dump(comp.somePropArray[1], false)) -- Dumps class `someClass`

local newClass = NewObject('someClass')
newClass.x = 20

comp.somePropArray[1] = newClass
print(comp.somePropArray[1].x) -- now it will print 20

I'll split this into two issues if you dont mind cause having enhancement and bug in one is not ideal :P

yes good idea, i hide the comment.


feat: jest coverage output

https://github.com/aspect-build/rules_jest/issues/34
First time doing anything coverage-related in Bazel, so I may be doing something weird.

@thesayyn knows this stuff well and could give a good review here

Thanks for the feedback @thesayyn. This is ready for review again.


Feature Request: Control of local device GPIO pins

This is particularly relevant to the wall plates that come with built in relays for local load switching (i.e. light switch )
But could be used for any purpose on the device eg driving an led or monitoring a PIR.
These could just subscribe / publish states, but ideally would be linked to buttons, this way a light switch can still function as a light switch in the event that the wall plate cannot talk to the server.
openHasp implementation is described here -  https://www.openhasp.com/0.6.3/configuration/gpio/

Would love to se this as well. Especially local GPIO's that are capable of PWM so you can adjust brightness, fan speed, etc.


Migrated project to langchain, added devcontainer, updated the some prompts

updated prompts for categorical feature definitions, added Fixed Few-Shot prompting to them

Hello @AaLexUser! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file fedot_llm/chains.py:

Line 122:80: E501 line too long (83 > 79 characters)
Line 136:80: E501 line too long (82 > 79 characters)
Line 182:80: E501 line too long (106 > 79 characters)
Line 241:80: E501 line too long (83 > 79 characters)
Line 251:80: E501 line too long (141 > 79 characters)
Line 252:80: E501 line too long (85 > 79 characters)
Line 253:1: W293 blank line contains whitespace
Line 258:21: E128 continuation line under-indented for visual indent
Line 259:21: E131 continuation line unaligned for hanging indent
Line 259:80: E501 line too long (96 > 79 characters)

In the file fedot_llm/chat.py:

Line 7:80: E501 line too long (103 > 79 characters)
Line 8:80: E501 line too long (82 > 79 characters)
Line 15:1: E303 too many blank lines (3)
Line 84:80: E501 line too long (85 > 79 characters)
Line 98:80: E501 line too long (84 > 79 characters)
Line 102:1: W293 blank line contains whitespace
Line 113:10: W292 no newline at end of file

In the file fedot_llm/data/data.py:

Line 11:1: E302 expected 2 blank lines, found 1
Line 16:1: W293 blank line contains whitespace
Line 29:1: W293 blank line contains whitespace
Line 42:1: W293 blank line contains whitespace
Line 86:1: W293 blank line contains whitespace
Line 88:80: E501 line too long (83 > 79 characters)
Line 89:80: E501 line too long (92 > 79 characters)
Line 98:80: E501 line too long (126 > 79 characters)
Line 101:80: E501 line too long (88 > 79 characters)
Line 119:80: E501 line too long (81 > 79 characters)
Line 125:80: E501 line too long (109 > 79 characters)
Line 131:1: E302 expected 2 blank lines, found 1
Line 136:1: W293 blank line contains whitespace
Line 153:1: W293 blank line contains whitespace
Line 308:80: E501 line too long (135 > 79 characters)
Line 310:80: E501 line too long (89 > 79 characters)

In the file fedot_llm/prompts.py:

Line 1:80: E501 line too long (87 > 79 characters)
Line 7:10: W291 trailing whitespace
Line 15:10: W291 trailing whitespace
Line 19:80: E501 line too long (148 > 79 characters)
Line 23:10: W291 trailing whitespace
Line 27:80: E501 line too long (133 > 79 characters)
Line 34:80: E501 line too long (147 > 79 characters)
Line 42:80: E501 line too long (106 > 79 characters)
Line 49:80: E501 line too long (120 > 79 characters)
Line 56:48: W291 trailing whitespace
Line 58:17: E127 continuation line over-indented for visual indent
Line 59:80: E501 line too long (94 > 79 characters)
Line 60:80: E501 line too long (82 > 79 characters)
Line 62:17: E124 closing bracket does not match visual indentation
Line 63:13: E231 missing whitespace after ','
Line 64:13: E127 continuation line over-indented for visual indent
Line 71:80: E501 line too long (110 > 79 characters)
Line 74:80: E501 line too long (101 > 79 characters)
Line 74:102: W291 trailing whitespace
Line 75:80: E501 line too long (194 > 79 characters)
Line 76:17: E127 continuation line over-indented for visual indent
Line 76:80: E501 line too long (153 > 79 characters)
Line 77:80: E501 line too long (83 > 79 characters)
Line 78:80: E501 line too long (88 > 79 characters)
Line 79:80: E501 line too long (173 > 79 characters)
Line 80:17: E127 continuation line over-indented for visual indent
Line 80:80: E501 line too long (207 > 79 characters)
Line 81:80: E501 line too long (82 > 79 characters)
Line 82:80: E501 line too long (106 > 79 characters)
Line 83:80: E501 line too long (173 > 79 characters)
Line 84:17: E127 continuation line over-indented for visual indent
Line 84:80: E501 line too long (172 > 79 characters)
Line 85:80: E501 line too long (83 > 79 characters)
Line 86:1: W293 blank line contains whitespace
Line 87:1: W293 blank line contains whitespace
Line 101:80: E501 line too long (101 > 79 characters)
Line 102:80: E501 line too long (88 > 79 characters)
Line 103:80: E501 line too long (99 > 79 characters)
Line 104:80: E501 line too long (88 > 79 characters)
Line 105:80: E501 line too long (95 > 79 characters)
Line 106:80: E501 line too long (83 > 79 characters)
Line 115:80: E501 line too long (134 > 79 characters)
Line 116:17: E127 continuation line over-indented for visual indent
Line 116:80: E501 line too long (95 > 79 characters)
Line 123:17: E127 continuation line over-indented for visual indent
Line 124:80: E501 line too long (114 > 79 characters)
Line 127:80: E501 line too long (257 > 79 characters)
Line 127:258: W291 trailing whitespace
Line 128:80: E501 line too long (245 > 79 characters)
Line 130:80: E501 line too long (178 > 79 characters)
Line 132:80: E501 line too long (187 > 79 characters)
Line 133:80: E501 line too long (240 > 79 characters)
Line 134:80: E501 line too long (336 > 79 characters)
Line 137:80: E501 line too long (188 > 79 characters)
Line 138:80: E501 line too long (146 > 79 characters)
Line 139:80: E501 line too long (153 > 79 characters)
Line 141:80: E501 line too long (247 > 79 characters)
Line 142:80: E501 line too long (347 > 79 characters)
Line 143:80: E501 line too long (245 > 79 characters)
Line 144:17: E124 closing bracket does not match visual indentation
Line 150:80: E501 line too long (118 > 79 characters)
Line 155:5: E124 closing bracket does not match visual indentation
Line 157:131: W292 no newline at end of file

In the file nlangchain/output_parsers/__init__.py:

Line 1:71: W292 no newline at end of file

In the file nlangchain/output_parsers/retry.py:

Line 59:80: E501 line too long (88 > 79 characters)
Line 60:80: E501 line too long (88 > 79 characters)
Line 61:80: E501 line too long (85 > 79 characters)
Line 89:80: E501 line too long (81 > 79 characters)
Line 126:80: E501 line too long (88 > 79 characters)
Line 164:80: E501 line too long (85 > 79 characters)
Line 183:80: E501 line too long (80 > 79 characters)
Line 191:80: E501 line too long (88 > 79 characters)
Line 193:80: E501 line too long (81 > 79 characters)
Line 195:80: E501 line too long (85 > 79 characters)
Line 223:80: E501 line too long (81 > 79 characters)
Line 251:80: E501 line too long (88 > 79 characters)
Line 281:80: E501 line too long (85 > 79 characters)


How about one topic to multiple tables?

Dear all,
Is there any guides for one topic sourced from multiple tables in a db, and sink to another db?
Thanks!

Hi @wefine
Sourcing one topic from multiple tables is not possible now. We might implement this at some point, but a Transformation plugin might be a better place for this.
I hope I understand right what you want to achieve. If gathering all the data in one topic is only for putting them later in one table, will it help if you subscribe the sink connector to multiple topics and set table.name.format=target-table?

@ivanyu Thanks for your time!
A logic database db1 has 10 tables, such as tb1, tb2... and another database db2 has the same structure with db1. I need to sync db1 to db2, so I use dbz-mysql-connector with 'combine' transform to put all tables of db1 to one topic, but I don't know how to use jdbc-connector to separate them to db2.
Thanks again!


Faulty symlink when using WinGet

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment

OS: Windows 10
scrcpy version: 2.0
installation method: winget
device model: Lenovo P1M
Android version: 5.1

Describe the bug
After installing through winget, a symlink is generated at %LOCALAPPDATA%\Microsoft\WinGet\Links as a mean of getting the executable into Path. However, when executing the symlink through the terminal (PowerShell 7.3.4 Core on Win10), it doesn't execute anything, just outputting nothing and returning to prompt. Even though manually going through the directory using File Explorer and opening it by double-clicking will launch it as normal.
 ASUS  PS  Monday 09:20:08 PM
┌ C:\Users\ASUS
└ ❯ scrcpy

 ASUS  PS  Monday 09:20:12 PM
┌ C:\Users\ASUS
└ ❯

And no, the custom PS profile isn't interfering with anything. Heck, running with -noprofile will return an error instead, as if there was no symlink at all.
PowerShell 7.3.4
PS C:\Users\ASUS> scrcpy
scrcpy: The term 'scrcpy' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
PS C:\Users\ASUS>

However, executing the command via cmd.exe results in a stream of error prompts instead, reading: "The code execution cannot proceed because [multiple DLLs] was not found. Reinstalling the program may fix this problem."

Please report to WinGet.

WinGet repo confirmed that this is an upstream issue with their app not being able to handle portable executables with DLLs

their app not being able to handle portable executables with DLLs

Then they should probably build a non-portable version and use the dependencies (ffmpeg, sdl, libusb) from their repo: https://github.com/Genymobile/scrcpy/blob/958f22490b3ab86677bd8b6126ddaa4de4082798/meson_options.txt#L4

Yup, just had the same problem.   You might consider removing the mention of winget from
/windows.md
PS: Thanks, scrcpy sounds like just what I was looking for.

Upstream solution available in Winget 1.9 clients
https://github.com/microsoft/winget-pkgs/issues/107858#issuecomment-2515716218

This has been fixed for all versions of the Genymobile.scrcpy package in microsoft/winget-pkgs, including the latest 3.1 release of scrcpy. scrcpy binaries (dlls, etc.) are now properly added to path winget.


Memory problems with AORSA on cori

Hei AORSA experts,
I finally started to work with AORSA in the earnest. I already did one big run in the past but there I had insufficient resolution. I have changed the scenario such that k_perp is smaller.
This AORSA run, however, crashed on CORI. I ran it successfully on my laptop with 16x16 modes to make sure the input is OK.
Only real change that I am aware of is that changed the nmodesx=288 and nmodesy=504 such that they are an integer multiple of my nprow=72 npcol=72.
Input file, batch script and .e file attached. The .o file is empty. I followed the instructions on this page to submit the AORSA run.
Any insights are appreciated.
With kind regards
Severin
P.S. Note that I had to change the extension of the files for github to accept them.
AORSA2D_e33599278.txt
aorsa2d_in.txt
batchscript_cori_full.txt

I just got the E-Mail from SLURM that the job failed again with exit code 134. I did not change anything besides cleaning up my AORSA distribution as explained above.
Errorlog looks the same as before but I attached it anyway.
AORSA2D_e33651923.txt

Hi Severin, I don't think that the nmodesx needs to be related to nprow etc, only that nprow and npcol need to match the number of processors requested in the batch script. But of course I could be wrong.
I'd suggest doing an interactive session, and looking at the output of some smaller runs with different configurations on that same input file if you suspect a problem related to the np and nmode inputs. Meanwhile, I'll try to reproduce your error.

OK, looks like I'll need the eqdsk file as well. Can you open up the permissions on the path on cori where your run is so I can grab the inputs?

I did not know your NERSC username so please find the equilibrium file attached. Make sure to remove the .txt.
Thanks for your help!
g165908.03000_1_0MA_2_0T.txt

I tried running on 8 interactive nodes with a 128 by 256 grid and this AORSA task also managed to start. I didn't let it finish to avoid wasting CPU hours. I also adjusted the grid size to be 288*512 modes. I resubmitted the calculation with 72x128 CPUs so that the distribution of CPU/s per column and row entry is equal. Let's see how this goes...

You may simply be running out of memory on the available nodes for the 288x512 problem. I forget if there is output to tell you what the per-node memory usage is, but 288x512 is a very large problem. I'd suggest looking through some of the initial run setup output for a successful small run to see if it prints out the memory usage. I used to have a calculator to estimate the usage for another version of AORSA, but I'm not sure what exists for this one. @cornwalllau how do you approach that issue?

The memory is tricky. There is a scaling that I forgotten (N^4 for Wdot calculation). Unfortunately, I can't seem to find any records of this. When I started, Fred already had some example files so I never really did a calculator like David. I just scaled it based on the scaling. As David said, you can always increase the number of processors.
I did notice you don't specify srun -n 5184 in your batchscript where 5184 is number of cores. I usually do in mine. I'm not 100% sure if it's necessary, but it may be.

On Mon, August 24, 2020 4:43 pm, cornwalllau wrote:

The memory is tricky. There is a scaling that I forgotten (N^4 for Wdot
calculation). Unfortunately, I can't seem to find any records of this. When I
started, Fred already had some example files so I never really did a
calculator like David. I just scaled it based on the scaling. As David said,
you can always increase the number of processors.
I did notice you don't specify srun -n 5184 in your batchscript where 5184 is
number of cores. I usually do in mine. I'm not 100% sure if it's necessary,
but it may be.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ORNL-Fusion/aorsa/issues/29#issuecomment-679355603

As David points out, this is a very large run. I'd stick with 128x128 in the
debug queue to develop runs. Lower the frequency if needed to make the
wavelength larger until you are confident in your case set up and then try
larger runs. Slurm commands will tell you how much RAM a case used. For 2D
runs, memory usage should go like (Nx*Ny)^2 :: there are Nx kx and Ny ky modes
at each Nx,Ny point. Doubling the resolution increases ram usage by 16x, so
generally you should increase number of cores by 16x for each doubling of
resolution in both x and y. For helicons? I'm not sure it is useful to
increase only one dimension as those waves tend to curl around and need equal
amounts of kx and ky. Perhaps your domain box is also 2x1 for elongated
plasma, then it would make sense to do that.
-john

When I tried running AORSA back in May I used Cornwall's original grid layout which was 448 by 384. This run finished on a 72x72 CPU grid without errors and used (according to sacct) only about 3.8 TB of memory. The problem I am trying to solve is 15 % smaller and in my first attempt, it had 20.7 GB available totally.
One difference is, however, that I have turned on new_wdot for the new run while it was off for the one in May so that might make the difference.
@jcwright77 I will try lowering the frequency and see how much memory a 128 by 256 grid requires. This grid layout I could run on 8 nodes. With your memory scaling, I can then extrapolate the amount of memory needed. That is a good idea.
As for my grid, it is exactly as you suspected and we are dealing with a 1 m wide by 2 m high plasma. I used the cold plasma dispersion and the plasma shape to calculate the mode numbers I need to resolve.
Thank you all for the pointers!

Just a quick follow up.
I submitted AORSA with a frequency of 128 MHz on a 128 by 256 grid on 8 nodes and this run allocates 1.14 TB of memory in the beginning of the run. Now, applying John's scaling rule to the failed runs totals to 22.3 TB of required memory while there is only 20.7 TB available. I guess Cornwall's original run got away with this because there were only 16 CPUs per node back then while there was still 128 GB of memory per node.
So I suspect my new submission asking for twice the amount of nodes and requesting 40 TB should be fine.
I'll close this thread if my latest submission finishes successfully.
Thanks again for all your help.

OK, I'm going to add an issue to have the code print out some estimates of matrix sizes etc to try and make this less painful.

My Job failed again. I also went over the math from yesterday and I made a mistake. For some reason, I thought that the conversion from KB to TB was 10^-6 instead of 10^-9.
With that error taken care of, the task with the largest VMSize has only 1.09 GB for my 128x256 debug case. Note that there is 128 GB of physical memory to be shared among 32 CPUs, which means there is 4 GB per CPU minus whatever the OS needs.
I suppose the 3rd row 33723327.0 just refers to the parent task and is not a sum of all tasks?
JobID    JobName   NTasks     MaxRSS  MaxVMSize

33723327        AORSA2D
33723327.ba+      batch        1      0.01G      1.09G
33723327.ex+     extern        8      0.00G      0.49G
33723327.0     xaorsa2d      256      2.06G      3.29G
Here is also the summary from my latest failed job:
JobID    JobName   NTasks     MaxRSS  MaxVMSize

33715899        AORSA2D
33715899.ba+      batch        1      0.02G      1.41G
33715899.ex+     extern      288      0.00G      0.43G
33715899.0     xaorsa2d     9216      1.30G      1.93G
From the data above it doesn't seem like the problem will go away by just chucking even more nodes at it.
I am still very new to MPI computing, so I have no idea if I am diagnosing this problem correctly.
Any insight would be appreciated.

can you send the out15 and log_aorsa2d file. Or also let me and others into your directory. My username is lauch.

These are runs with the high resolutions
out15.txt
log_aorsa2d.txt
And here the successful debug run with 128x256 modes with f = 128 MHz:
log_aorsa2d.txt
out15.txt

Ok, based on these output files, you didn't even reach the matrix loading stage, so this should not be a memory issue. Given that you did have a successful 128x256 run, my gut is that the large number of modes triggered something in the code. In my hazy memory, I sort of recalled that Fred hardcoded a maximum number of modes in x and y direction in src/size_mod.f90 for reasons that I don't remember (memory allocation in fortran?). Indeed in that file, it is set to 500 as the maximum number and appears consistent with your these runs to date. I suggest you recompile with 600 in both nmodesmax and mmodesmax in size_mod.f90 following the instructions in that file and give it another try for both a small case in the debug queue to make sure you recompiled correctly and then the desired large case.
If this is the issue, we should consider how to make this more user friendly in the future.

So I went and testing @cornwalllau's idea by taking a small problem, but reducing the parameters in size_mod.f90 to be even smaller, i.e., nmodesmax=15 or so for a 16x16 problem. And indeed the code crashes at the same place @AreWeDreaming is seeing his output end. Here is my test output for reference ...
      n   capr_bpol_mid
         1  4.7418E-02
         2  1.5270E-01
         3  3.1170E-01
         4  4.5062E-01
         5  5.4156E-01
         6  5.9893E-01
         7  6.4010E-01
         8  6.4010E-01
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 WARNING (sigma.f) : rhoij > rho(nnodex,jmid)
 rho_in =
 profile_in =
         129         257

Program received signal SIGFPE: Floating-point exception - erroneous arithmetic operation.

Backtrace for this error:
#0  0x7f2d1622aaed in ???
#1  0x7f2d16229d25 in ???
#2  0x7f2d158a2fcf in ???
#3  0x5579defed848 in a2dmnmx_r4_
	at src/fieldws.f:5363
#4  0x5579defeca30 in ezconc_
	at src/fieldws.f:5429
#5  0x5579defe87f8 in eqdsk_plot_
	at src/eqdsk_plot.f90:806
#6  0x5579defd3e53 in eqdsk_setup_
	at src/eqdsk_setup.f:2186
#7  0x5579df06e051 in aorsa2dmain
	at src/aorsa2dMain.F:1840
#8  0x5579dee81a68 in main
	at src/aorsa2dMain.F:14

So, what i'll do now is push a change that forces a check on this so it at least tells you what the problem is, and does so at the very beginning of the run.

OK, I've pushed a change to master which now checks this as the first thing it does. @AreWeDreaming you should pull and recompile, then check that it does indeed fail on your large run. Then, edit src/size_mod.f90 to enable the size you want to run by making sure nmodesmax >= nmodesx and mmodesmax >= nmodesy.

Thank you Cornwall for finding culprit and David for fixing it. Did you intentionally set the makefile such that it compiles in debug mode? Otherwise, I will replace -g with -O2 since I hope to resubmit my calculation asap. Also, I tried to fix the issue myself in the Fix_large_grids branch,, but for some reason, my debug test case never got through the queue. I guess you can delete that branch now.

Hmm, I explicitly recall removing the -g flag I was using. I must have missed something. Let me check.

Ah, it was in multiple places. Although I think it was also in there before - perhaps you removed it in your local source? In any event, I've pushed a change that removes it.

The  -g is still in the makefile in F90FLAGS. I replaced it with O2.

Increasing nmodesmax  and mmodesmax fixed the issue. Thanks for your help folks!


fix: allow both email and phone number type

Description of changes

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies

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

Codecov Report

Merging #8850 (5cd5864) into master (86467d6) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #8850   +/-   ##
=======================================
  Coverage   56.55%   56.55%
=======================================
  Files         837      837
  Lines       47358    47359    +1
  Branches     9505     9505
=======================================
+ Hits        26781    26782    +1
  Misses      19766    19766
  Partials      811      811

Impacted Files
Coverage Δ

...e-walkthrough-types/awsCognito-user-input-types.ts
100.00% <100.00%> (ø)

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 86467d6...5cd5864. Read the comment docs.


implement TimeValLike for std::time::Duration

This was suggested by @fiveop in #494
I'm not sure how you want me to handle the mismatch between i64 everywhere in this api and u64 in Duration; should I panic if someone passes a negative duration?

Shall hold off on this while #516 gets decided on? Thanks for pushing these changes though!

I'm going to close this in favor of whatever comes out of #516, which I think we have on a good track. I don't think this implementation will be required.


2x slower using post-training quantization from tensorflow-lite

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
TensorFlow installed from (source or binary):  pip install -U tf-nightly
TensorFlow version (use command below): '1.12.0-dev20181012'
Python version: 2.7.12

Describe the problem
I read and run the post-training quantization code from official tensorflow Medium (https://medium.com/tensorflow/introducing-the-model-optimization-toolkit-for-tensorflow-254aca1ba0a3).
The post said the technique can result in up to 3x faster execution for relevant machine learning models. But I found during inference is 2x slower.
Source code / logs
I run the Colab notebook (https://colab.research.google.com/github/tensorflow/tensorflow/blob/master/tensorflow/contrib/lite/tutorials/post_training_quant.ipynb) and compare inference time before and after quantization from the Evaluate the models section.
The log before quantization:
Accuracy after 500 images: 0.976000
Accuracy after 1000 images: 0.966000
Accuracy after 1500 images: 0.958667
Accuracy after 2000 images: 0.956500
Accuracy after 2500 images: 0.952400
Accuracy after 3000 images: 0.956667
Accuracy after 3500 images: 0.957429
Accuracy after 4000 images: 0.955000
Accuracy after 4500 images: 0.955333
Accuracy after 5000 images: 0.954800
Accuracy after 5500 images: 0.958182
Accuracy after 6000 images: 0.959000
Accuracy after 6500 images: 0.960462
Accuracy after 7000 images: 0.961571
Accuracy after 7500 images: 0.963600
Accuracy after 8000 images: 0.965250
Accuracy after 8500 images: 0.966471
Accuracy after 9000 images: 0.968222
Accuracy after 9500 images: 0.969158
Accuracy after 10000 images: 0.968000
0.968
42.6 sec

The log after quantization:
Accuracy after 500 images: 0.976000
Accuracy after 1000 images: 0.967000
Accuracy after 1500 images: 0.959333
Accuracy after 2000 images: 0.957000
Accuracy after 2500 images: 0.952800
Accuracy after 3000 images: 0.957000
Accuracy after 3500 images: 0.957714
Accuracy after 4000 images: 0.955500
Accuracy after 4500 images: 0.955778
Accuracy after 5000 images: 0.955200
Accuracy after 5500 images: 0.958545
Accuracy after 6000 images: 0.959333
Accuracy after 6500 images: 0.960769
Accuracy after 7000 images: 0.961857
Accuracy after 7500 images: 0.963867
Accuracy after 8000 images: 0.965500
Accuracy after 8500 images: 0.966706
Accuracy after 9000 images: 0.968444
Accuracy after 9500 images: 0.969368
Accuracy after 10000 images: 0.968300
0.9683
74.5 sec

The accuracy is basically the same, but it's much slower.

do you understand the principle of post-training ? how does it achieve the quant ?

Why the issue is close?

It is slower after quantization. During post training the weights are quantized whereas the activations are quantized and dequantized on the fly at inference.

@wt-huang Does the quantized model will using float at inference?


Feature request: mouse support for selecting dates

It looks like to could be slightly tricky since we need to convert pixel co-ordinates to dates.
https://tldp.org/HOWTO/NCURSES-Programming-HOWTO/mouse.html
I mention this because diary works fine on Android under Termux, but navigating the calendar isn't very nice with the on-screen keyboard. It's probably nicer to be able to tap a date to select it (and Termux fakes mouse events from the touch screen, I think).
While we're there, we could add mouse-wheel support for scrolling up and down if the user has ncurses-6 - https://stackoverflow.com/questions/42356352/mouse-scroll-up-ncurses-c#answer-42357034. It should be as simple as binding mouse 4/5 to what J/K currently do.
Somewhat related to #49.

Hi @bovine3dom can you review this first draft on your device? Thanks.
Unfortunately I could not get the mouse 4/5 events working (they were not firing on my Ubuntu 20.04, probably, ncurses was not compiled with the feature flag --enable-ext-mouse? https://invisible-island.net/ncurses/ncurses-mapsyms.html#ext_mouse).
~/Downloads/diary$ ldd diary | grep ncur
	libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 (0x00007f4cc84dc000)

Let's see what can be done...

The pixel co-ordination to date conversion is not perfect :) I used BUTTON1_CLICKED (short click) instead of BUTTON1_PRESSED (long press), this might be a bit different on your device..

implemented in #79


otel-webserver-module: String field

nginx version: 1.22.0
otel-webserver-module: v1.0.3
nginx log：
[libprotobuf ERROR /grpc/third_party/protobuf/src/google/protobuf/wire_format_lite.cc:577] String field 'opentelemetry.proto.common.v1.AnyValue.string_value' contains invalid UTF-8 data when serializing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes.

Hi @lework,
We need more information on this for us to really understand the problem.

I have the same issue.
nginx version: 1.22.1
otel-webserver-module: v1.0.3
/etc/nginx/config.d/opentelemetry_module.conf:
    NginxModuleEnabled ON;
    NginxModuleOtelSpanExporter otlp;
    NginxModuleOtelExporterEndpoint http://otel-collector-collector.monitoring:4317;
    NginxModuleServiceName nginx-instrumentation;
    NginxModuleServiceNamespace default;
    NginxModuleServiceInstanceId nginx-instrumentation-test;
    NginxModuleResolveBackends ON;

The only config in the nginx.conf related to otel is loading the module and including the conf.d directory.  Every time a server path is hit, the following error is printed:
2023/03/22 13:13:50 [error] 12#12: *32 mod_opentelemetry: startMonitoringRequest: Starting Request Monitoring for: /nginx-health HTTP/1.1 Host, client: <IP_ADDRESS>, server: _, request: "GET /nginx-health HTTP/1.1", host: "<IP_ADDRESS>:80"
2023/03/22 13:13:50 [error] 12#12: *32 mod_opentelemetry: stopMonitoringRequest: Request Ends with result code: 0 while logging request, client: <IP_ADDRESS>, server: _, request: "GET /nginx-health HTTP/1.1", host: "<IP_ADDRESS>:80"
[libprotobuf ERROR /grpc/third_party/protobuf/src/google/protobuf/wire_format_lite.cc:577] String field 'opentelemetry.proto.common.v1.AnyValue.string_value' contains invalid UTF-8 data when serializing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes.`

I am seeing traces in jaeger coming from the nginx-instrumentation service. They are not linking to the traces coming from the app, although that may be unrelated

Me too,I have the same issue.
nginx version: 1.23.0
otel-webserver-module: v1.0.3
/etc/nginx/config.d/opentelemetry_module.conf:
NginxModuleEnabled ON;
NginxModuleOtelSpanExporter otlp;
NginxModuleOtelExporterEndpoint http://otel-collector.open-telemetry:4317;
NginxModuleServiceName DemoService;
NginxModuleServiceNamespace DemoServiceNamespace;
NginxModuleServiceInstanceId DemoInstanceId;
NginxModuleResolveBackends ON;
NginxModuleTraceAsError ON;

It seems to have made the same mistake:
[libprotobuf ERROR /grpc/third_party/protobuf/src/google/protobuf/wire_format_lite.cc:577] String field 'opentelemetry.proto.common.v1.AnyValue.string_value' contains invalid UTF-8 data when serializing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes.
[libp

And how do i fix them?

I have the same error too...
2023-03-31T08:14:00.148875200Z [libprotobuf ERROR /grpc/third_party/protobuf/src/google/protobuf/wire_format_lite.cc:577] String field 'opentelemetry.proto.common.v1.AnyValue.string_value' contains invalid UTF-8 data when serializing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes.

something changed?

I have the same error too...
[libprotobuf ERROR /grpc/third_party/protobuf/src/google/protobuf/wire_format_lite.cc:577] String field 'opentelemetry.proto.common.v1.AnyValue.string_value' contains invalid UTF-8 data when serializing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes. [libprotobuf ERROR /grpc/third_party/protobuf/src/google/protobuf/wire_format_lite.cc:577] String field 'opentelemetry.proto.common.v1.AnyValue.string_value' contains invalid UTF-8 data when serializing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes. [libprotobuf ERROR /grpc/third_party/protobuf/src/google/protobuf/wire_format_lite.cc:577] String field 'opentelemetry.proto.common.v1.AnyValue.string_value' contains invalid UTF-8 data when serializing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes. [libprotobuf ERROR /grpc/third_party/protobuf/src/google/protobuf/wire_format_lite.cc:577] String field 'opentelemetry.proto.common.v1.AnyValue.string_value' contains invalid UTF-8 data when serializing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes. [libprotobuf ERROR /grpc/third_party/protobuf/src/google/protobuf/wire_format_lite.cc:577] String field 'opentelemetry.proto.common.v1.AnyValue.string_value' contains invalid UTF-8 data when serializing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes.

I'm encountering the same issue, when will this be released?

Same error using
ENV OTEL_EXPORTER_OTLP_HEADERS="Authorization: Bearer ..."
and nginx env directive.

Isn't it a duplicate of https://github.com/open-telemetry/opentelemetry-cpp-contrib/issues/247 ? As far as I understand, the issue is already fixed. The problem is that there were no releases since then.

Isn't it a duplicate of #247 ? As far as I understand, the issue is already fixed. The problem is that there were no releases since then.

Just asked about this on the merged fix PR.

otel-webserver-module: v1.0.3
HI BrendanGalloway

Were you able to start nginx after adding the otel 1.0.3 libraries ngx_http_opentelemetry_module.so and libopentelemetry_*.so ?
I am trying to do it for RHEL Nginx 1.22.1 but getting error on startup due to compatibility issues.
Regards
Senthil

change a port that has never been used and restart, maybe we can deal with this problem


Update first Getting Started items as section intro

With #116570, the first item in a section will be what new users see first when opening VS Code. The content needs to explain better what this is all about – encourage a new user go through this list and explain what they will get out of it.
The first entry image/title/description and section title/descriptions need to be updated for:

[ ] Setup VS Code
[ ] Fundamentals
[ ] Codespaces

cc @misolori

/duplicate of #116976


Allow onClick interpret as a bool type

Fixed warning "Warning: Expected onClick listener to be a function, instead got a value of boolean type."

I'm not sure what this means. onClick has to be a function, because we call it.


Open Source License?

Hi, do you mind adding an open-source license so that I can use this at work?
Thanks!

Happy to - and done :)


Convert Root Pages and viewers to Typescript

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features

What kind of change does this PR introduce? *
No new behavior was added. I just converted a sort of files to typescript and adapted the system to work properly

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Actually I converted many other files to ts. Do you have interest to merge it?


Complete main README links for .NET documentation

There are links in the main README to the README files for each language binding, as well as to appropriate sections for building/installation and testing. The .NET sections are missing a few of these sections currently and links/sections should be updated as needed.

Is there any progress on this? Is the C# version of the library in a state it can be released? We would really like to use that if possible.

Hi @jjathman . Due to a bunch of random reasons working against me, I have not been able to finish the C# version 😔 I'm blocking off a week at the end of August to get this up to speed and released. Stay tuned and thanks for your interest.


Document distributed tree construction

This change documents another application of compact ranges,
the distributed tree construction.
Part of #4.

Ping


Driver now uses a read-only YAML configuration

It prevents nasty side-effects and reduce risk of introducing bugs.

Coverage decreased (-2.6%) to 85.966% when pulling ff9b6820267cd02546b0109b54b99b1d7d3f139a on enh/frozen-config into 95004a4dcfd1058e9222b0ad45622276617fdf41 on master.

Coverage decreased (-2.6%) to 85.966% when pulling ff9b6820267cd02546b0109b54b99b1d7d3f139a on enh/frozen-config into 95004a4dcfd1058e9222b0ad45622276617fdf41 on master.

I will squash commits after your approval @ohm314 So please do not merge.


Unable to find a sequencer node

Describe the bug
E1207 16:42:17.609799      52 [ld:srv:WG0] HashBasedSequencerLocator.cpp:208] locateSequencer() No available sequencer node for log<PHONE_NUMBER>427387899. All sequencer nodes are unavailable.
E1207 16:42:17.609859      52 [ld:srv:WG0] SequencerRouter.cpp:56] operator()() skipped at least 2 log entries
E1207 16:42:17.609873      52 [ld:srv:WG0] SequencerRouter.cpp:56] operator()() Error during sequencer lookup for log<PHONE_NUMBER>427387899 (NOSEQUENCER), reporting NOSEQUENCER.
E1207 16:42:17.609884      52 [ld:srv:WG0] SequencerRouter.cpp:105] onFailure() skipped at least 2 log entries
E1207 16:42:17.609893      52 [ld:srv:WG0] SequencerRouter.cpp:105] onFailure() Error during sequencer routing for log<PHONE_NUMBER>427387899 (NOSEQUENCER), request[type:GET_SEQ_STATE_REQ_TYPE, handler:0x7f24c45ba5a8].
W1207 16:42:17.609905      52 [ld:srv:WG0] GetSeqStateRequest.cpp:512] onSequencerRoutingFailure() Unable to find a sequencer node for log<PHONE_NUMBER>427387899, rqid:25769803838, ctx:rsm, err(NOSEQUENCER)
W1207 16:42:17.609916      52 [ld:srv:WG0] GetSeqStateRequest.cpp:700] finalize() GET_SEQ_STATE for log<PHONE_NUMBER>427387899 (rqid:25769803838, ctx:rsm) returned NOSEQUENCER: no sequencer was found for log
E1207 16:42:17.609982      60 [ld:srv:WB3] SyncSequencerRequest.cpp:178] onGotSeqState() Got sequencer state (id:25769803838) for log:4611686018427387899, status:NOSEQUENCER: no sequencer was found for log,sequencer:[invalid NodeID], last_released_lsn:LSN_INVALID, next_lsn:LSN_INVALID

Would you mind describing the steps to reproduce this issue?
Feel free to reopen if you still have this problem.

Using HStreamDB v0.15.0 which is deployed by the docker-compose file, when calling docker compose -f compose.yaml restart, the client will throw this error, but only sustain a moment

@lafirest It's OK because the cluster needs to do some initialization if you restart all the nodes. You can wait a few moments after your restart, or let your client retry a few times while receiving NOSEQUENCER error.