🔌  Plugin: Tekton

Goal
This epic aims to develop a new Backstage UI plugin in the Janus repo. This UI plugin should provide Backstage users with the ability to see the detailed status of the tekton pipeline associated with a service.  They should also be able to view detailed logs of the tekton pipeline associated with a service.
Evaluate existing community plugin to find issues and opportunities for improvement & enhancement
What problem does this solve? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Use cases
A clear and concise description of persona and associated use cases that need to be supported.
Acceptance criteria

[x]  Evaluate the plugin, using this BS Plugin Evaluation Templates

Additional context
Add any other context or screenshots about the feature request here.
Issues in Epic

[x] https://github.com/janus-idp/backstage-plugins/issues/83
[x] https://github.com/janus-idp/backstage-plugins/issues/112
[x] https://github.com/janus-idp/backstage-plugins/issues/201
[x] https://github.com/janus-idp/backstage-plugins/issues/182
[x] https://github.com/janus-idp/backstage-plugins/issues/128
[x] https://github.com/janus-idp/backstage-plugins/issues/111
[x] https://github.com/janus-idp/backstage-plugins/issues/161
[x] https://github.com/janus-idp/backstage-plugins/issues/237
[x] https://github.com/janus-idp/backstage-plugins/issues/255
[x] #304

Stakeholder sign-off

[ ] QE
[ ] Doc

@josephca @rnapoles-rh can one of you sign off for QE.
@hmanwani-rh @rkratky can one of you sign off for doc?


Removed root user check, just use sudo

This make it easier

Another question, why rename it from awake?

Hi @drq883. Just saw this while going over my repositories. It was a fun app to write. I'll try to merge your changes. There seem to be conflicts so I'll try go over them.
About the name, short for Tesrminal Wake and play on Terminal patient with insomnia.. Don't think anyone would give it enough thought to get it. I wanted a unique name but a different one would probably be better.
Hope you enjoyed this script. I was aiming to establish core functionalities that are not available in more popular apps, such as sleep after, wake locked mode, sleep duration, external screen lid control logic (mMac stays unlocked on lid close when ext monitor is connected), etc.
Thanks for youe contribution!


Close the ResultSet

This commit makes sure that the ResultSet internally created by count is closed.

I've noticed another case in SpannerConverter#mapToList but I am not sure where to fix it.


Undeclared dependency on "clone" causes npm install to fail

On installing semantic-ui, I get the following error:
|
><EMAIL_ADDRESS>install /Users/lachlan/.go/src/github.com/lox/xyz/node_modules/semantic-ui
> gulp install

module.js:338
    throw err;
          ^
Error: Cannot find module 'clone'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/Users/lachlan/.go/src/github.com/lox/xyz/node_modules/gulp-util/node_modules/vinyl/index.js:2:13)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)

Just tested on ubuntu with npm install semantic-ui and its working for me. If you have a package.json setup for your project try rming node_modules and re-installing, npm update
If you are still getting the issue, do you have any more info. Do you have other dependencies in the project? What platform?

Perhaps try npm cache clean

@lox Did you ever work out what was happening? I'm getting this same error.

@dannynimmo I got this after keyboard interrupting a package installation.  npm cache clean and reinstalling said package did the job.

I'm having this issue on ubuntu 17.04


Google Cloud Registry support?

I was looking through the Pulumi docs and I found this for AWS:
image: awsx.ecs.Image.fromPath("nginx", "./app"),

Is there an equivalent for GCR (gcr.io) images? I wasn't able to find one.

Is there an equivalent for GCR (gcr.io) images? I wasn't able to find one.

There isn't a higher-level component for this in our GCP package, no. Under the covers, though, I believe this is just using @pulumi/docker and AWS ECR. I think you could achieve the same effect using @pulumi/docker and https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/gcp/container/#getRegistryRepository .

Thanks @pgavlin , that ended up working fine for me.


请教一下如何使用azure接口的openai api-key?

We will plan to support this in the future! Thanks for your interest on our work.


Contact Us/Comment mailto

Look into setting up a USDA outlook group for the SoyBase Contact US/Comment to send an email to the entire SoyBase team.

Email_exchange.pdf

[ ] Public contact form - needs to live somewhere
[ ] PowerAutomate flow - executed as the shared email address
[ ] Finalize wording and style of the form -- Assigned to Jackie

@nathanweeks
I reviewed the contact branch with the i-framed contact form.  I would like to request that you elongate the i-frame about one more inch so that the user can see the word Message. I want to make sure that the user knows that is a message section to the form. Please mention me in the comment or pull request so that I know to look at this again. Thank you for all  your help.


failure to import key should have a higher logging level than INFO

At the moment importing malformed keys with the notary client raises no error. using the debug flag -D we can see the error is being logged at INFO level.
eg.
notary key import priv.key -D
> DEBU[0000] Using the following trust directory: /Users/XXX/.docker/trust
> INFO[0000] failed to import key to store: Invalid key generated, key may be encrypted and does not contain path header

looks like this was closed by #1179?

@endophage: 👍  yes!


hot pixel mask

Using sep, I constructed the hotpixel identification, though not well-tested.

Anyway done.

When I tried to identify sky emissions, I found that there remain (many) hot pixels even after masking them.
These figures show a raw detector image of a dark frame and a hot pixel mask made from it by current pyird.
(They are zoomed up where the hot pixel cluster exists to make it easy to see. This cluster doesn't affect the extracted spectrum, though.)
You can see that the cross-shaped hot pixel cannot identify correctly.
I will revise the code to identify hot pixels (or make a new one).

Yeah, the last one I made was a very beta version. I agree that we need to revise it!

The hotpixel mask is updated in #58


typo fix

removed un-necessary text

@asgr86 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@asgr86 Thank you for this correction!


Reading Awkward Arrays requires URLs that are too long

I don't remember where I mentioned this[^1], but one thing that I'm using this for is to collect metadata for a set of ROOT files, which can then be accessed more quickly (like kerchunk, but ROOT metadata is big enough that it can't be JSON).
I started this project (https://github.com/jpivarski/tiled-uproot), using Awkward Arrays in Tiled for the metadata. For each PB of ROOT data, I estimate about 10 TB of metadata will be needed in the database. (User derived quantities will be smaller, and it will be nice to be able to access the original ROOT data and derived quantities with the same tools.)
I ran this on 3 typical files, resulting in an Awkward Array whose Form JSON is 786 kB, has 5639 buffers containing a total of 42 MB. With more files, the size of the Form and number of buffers will not increase, but the total amount of data in the buffers will increase.
I had no trouble writing this Awkward Array in Tiled, and I could read back small slices of it. However, some queries, the ones addressing the larger parts of the array, raised this error:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/jpivarski/mambaforge/envs/tiled/lib/python3.10/site-packages/tiled/client/awkward.py", line 55, in __getitem__
    return self.read(slice=slice)
  File "/home/jpivarski/mambaforge/envs/tiled/lib/python3.10/site-packages/tiled/client/awkward.py", line 39, in read
    self.context.http_client.get(
  File "/home/jpivarski/mambaforge/envs/tiled/lib/python3.10/site-packages/httpx/_client.py", line 1041, in get
    return self.request(
  File "/home/jpivarski/mambaforge/envs/tiled/lib/python3.10/site-packages/httpx/_client.py", line 801, in request
    request = self.build_request(
  File "/home/jpivarski/mambaforge/envs/tiled/lib/python3.10/site-packages/httpx/_client.py", line 358, in build_request
    return Request(
  File "/home/jpivarski/mambaforge/envs/tiled/lib/python3.10/site-packages/httpx/_models.py", line 330, in __init__
    self.url = self.url.copy_merge_params(params=params)
  File "/home/jpivarski/mambaforge/envs/tiled/lib/python3.10/site-packages/httpx/_urls.py", line 360, in copy_merge_params
    return self.copy_with(params=self.params.merge(params))
  File "/home/jpivarski/mambaforge/envs/tiled/lib/python3.10/site-packages/httpx/_urls.py", line 348, in copy_with
    return URL(self, **kwargs)
  File "/home/jpivarski/mambaforge/envs/tiled/lib/python3.10/site-packages/httpx/_urls.py", line 115, in __init__
    self._uri_reference = url._uri_reference.copy_with(**kwargs)
  File "/home/jpivarski/mambaforge/envs/tiled/lib/python3.10/site-packages/httpx/_urlparse.py", line 134, in copy_with
    return urlparse("", **defaults)
  File "/home/jpivarski/mambaforge/envs/tiled/lib/python3.10/site-packages/httpx/_urlparse.py", line 200, in urlparse
    raise InvalidURL(f"URL component '{key}' too long")

Given this scale of Form JSON, maybe the URL-based query can be replaced by POST data?
[^1]: Finally found it: it was a private email with subject line "Using Tiled as a kerchunk-like database for ROOT files". I copied it here: https://github.com/jpivarski/tiled-uproot/discussions/1.

Yes, I think that make sense.
I once read an argument that every GET route should also support POST, for this reason. While I wouldn't take that argument so far, this is a case where it applies: we should support GET for ease of use in simple cases (typing into curl ...) and POST for the general case where the concatenated names of the form keys may grow large.
I am very interested in this use case; I replied in the linked Discussion.


chore: run phpstan on tests dir

https://github.com/nunomaduro/larastan/issues/462
Now that I've kinda dug into how the test suite works, I realize that phpstan is run individually on each feature test file. Is that something we want to continue doing?

I think tests should be tested in a separate run with configuration that is a copy of phpstan.neon.dist -> tests/phpstan-tests.neon

tests/phpstan-tests.neon
includes:
    - ../extension.neon
parameters:
    bootstrap: ../bootstrap.php
    level: max
    paths:
        - ./
    reportUnmatchedIgnoredErrors: false
    checkGenericClassInNonGenericObjectType: false
    ignoreErrors:
        - '#Method Illuminate\\Contracts\\Foundation\\Application::basePath\(\) invoked with 1 parameter, 0 required.#'
        - '#Call to an undefined method Mockery\\ExpectationInterface#'
        - '#Mockery\\(?:Legacy)?MockInterface#'
        - '#Parameter \#4 \$phpDocParameterTypes of method PHPStan\\Reflection\\Php\\PhpMethodReflectionFactory::create#'

and in Travis: vendor/bin/phpstan analyze -c tests/phpstan-tests.neon

Hey @szepeviktor sure, I can totally do that.
I'm curious behind the rationale in wanting to maintain a duplicated phpstan.neon file? Would there be something problematic with reusing the same phpstan config file, but passing the directory to analyse? I'm going to push up a commit doing that, but please let me know if I'm not seeing something!

trying to reproduce and fix
 Line   Application/database/migrations/2020_01_30_000000_create_users_table.php
 ------ --------------------------------------------------------------------------
  23     Call to an undefined method
         Illuminate\Database\Schema\Blueprint::unknownColumnType().

@szepeviktor The only thing I'm noticing that needs to be different in the configs right now is checkMissingIterableValueType: false, which I only added because I didn't get around to fixing those errors yet. Am I missing something else that needs to be different in the phpstan configs between src and tests?

Please revert the main config file changes as Larastan does not need its own extension to run phpstan on itself.
Asd this new one
includes:
    - ../extension.neon
parameters:
    bootstrap: ../bootstrap.php
    level: max
    paths:
        - ./

I see, the main concern is including the extension when analysing the src directory. Ok, I'll make a second config for analysing tests directory

the main concern is

Yes.
One part is peach, the other is gummy bear :)

looks very promising https://travis-ci.org/nunomaduro/larastan/jobs/649636004

Yeah, I'm trying to reproduce that error locally but struggling to do so at the moment. I'll keep working on it :)

This is the Blueprint class
https://github.com/laravel/framework/blob/v6.15.0/src/Illuminate/Database/Schema/Blueprint.php#L13

I can't reproduce locally. Any guidance is appreciated. Something to do with the rememberToken it seems.
./vendor/bin/phpstan analyse -c ./tests/phpstan-tests.neon tests/Application/database/migrations/2020_01_30_000000_create_users_table.php --ansi
 1/1 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%

 [OK] No errors

Any guidance is appreciated.

What is your PHP version?
Do you have xdebug enabled?

Do you have contracts?
https://github.com/nunomaduro/larastan/blob/master/.travis.yml#L27

trying to reproduce https://travis-ci.org/nunomaduro/larastan/jobs/649636008?utm_medium=notification&utm_source=github_status on 7.4
php -v
PHP 7.4.2 (cli) (built: Jan 22 2020 06:30:58) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.2, Copyright (c), by Zend Technologies

composer require "illuminate/contracts:^6.0" --dev --prefer-dist --no-interaction --no-suggest -q && composer test
> phpunit --colors=always
PHPUnit 8.5.2 by Sebastian Bergmann and contributors.

Runtime:       PHP 7.4.2
Configuration:.../repos/larastan/phpunit.xml.dist

..........................                                        26 / 26 (100%)

Time: 13.74 seconds, Memory: 12.00 MB

OK (26 tests, 26 assertions)
> phpstan analyse --ansi
Note: Using configuration file .../repos/larastan/phpstan.neon.dist.
 65/65 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%

 [OK] No errors

> phpstan analyse -c ./tests/phpstan-tests.neon --ansi
 34/34 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%

 [OK] No errors

Very weird.
@nunomaduro Could you help us?

Oh derp, I was behind master.
https://github.com/nunomaduro/larastan/commit/8a992b4c6ab1b4254b23bd1e36acb641b37d6993
@canvural should we not be failing on this?

This also makes it very easy to just run 1 test while developing. IE just /vendor/bin/phpstan analyse tests/Features/Models/Relations.php  -c tests/phpstan-tests.neon --debug --memory-limit=1G -vvv

Do we want to
excludes_analyse:
        - ./Features

in the tests config file considering that is currently being covered by phpunit?

@mr-feek Can you resolve the current conflicts?

I am not sure about this one. We do not have any real unit tests. We only have this kind of feature and acceptance tests. So running a static analysis over this does not make sense. There is no real gain out of it. So :-1: from me.

@canvural Thanks for review this. And thanks @mr-feek for the proposal.


[#3667] Add grouping to initiative tracker

Adds automatic grouping to the initiative tracker. This will group any combatants with the same initiative and the same base actor into a group.

Groups are displayed as collapsible sections in the combat tracker that use the name from the base actor's prototype token. It lists the number of combatants in the group, and when one of the group members is active it displays how far through the group that actor is.
Currently only offers the one grouping mode, but could be expanded in the future to support different grouping such as splitting it into "friendly" and "hostile" groups.
Closes #3667

This will group any combatants with the same initiative and the same base actor into a group.

What about:

TokenDocument#disposition
PrototypeToken#actorLink
TokenDocument#name

It's quite common to use a generic monster for a one-off NPC. Steve the Quest Giver Goblin the party rescues from a cage surely shouldn't be grouped with the rest of them.

This will group any combatants with the same initiative and the same base actor into a group.

What about:

TokenDocument#disposition
PrototypeToken#actorLink
TokenDocument#name

It's quite common to use a generic monster for a one-off NPC. Steve the Quest Giver Goblin the party rescues from a cage surely shouldn't be grouped with the rest of them.

We could take disposition & actor link into account (probably never group if actor link is true), but we wouldn't want to use the token name otherwise adding numbers or adjectives like the goblins in the screenshots above would prevent them from ever being grouped.

Is this intended to work best with flat initiative per #4812 or are there plans for streamlining the process of setting init values for a group, re:

The DM makes one roll for an entire group of identical creatures


Application giving an error as The app encountered an error processing your request. If you are an administrator of the app, view the full error in the logs. See aka.ms/appservice-logs for more information. Error type: <class 'openai.AuthenticationError'>

We ran the script as per the shared in "https://github.com/Azure-Samples/azure-search-openai-demo" and used existing resources.
While sending any query to application, its giving an error stating "The app encountered an error processing your request.
If you are an administrator of the app, view the full error in the logs. See aka.ms/appservice-logs for more information.
Error type: <class 'openai.AuthenticationError'>"

Hi @javedunfyd
Could you confirm ?

You are on latest main
If an index has been created and contains data

Remove any .md5 in /data/* .
Run ./scripts/prepdocs.py from root directory.

In data floder, there are lot of .md5 files. Shall I remove it?

Run ./scripts/prepdocs.py from root directory. This also I have done but still there is no difference in error.

In data floder, there are lot of .md5 files. Shall I remove it?

Yeah remove them and try running prepdocs.py again. md5 would prevent existing files to be picked up for new service and index.

Here's giving an error.

The 404 error should be fine to ignore, that's only necessary if you have App Service authentication enabled, but I presume you don't (it's typically off).
In terms of openai.AuthenticationError, I suggest you check Application Insights for more information. Open Azure Portal, open the resource group for this app, open Application Insights, and select "Failures" under Investigate. You should see AuthenticationError listed, and you can click it for a longer traceback.
Most likely, something is misconfigured about your OpenAI connection. You can also open App Service in the Azure Portal and check the environment variables in the configuration to see how they look.


Incorrect start date and size

I'm receiving an issue where some of the older torrents have the wrong start date, 50 or so with the exact same time and date and larger downloads seem to have a negative size

so the wrong getSize was my bad, I'm apparently running in 32bit i've sorted that now but it still seems to be returning an incorrect start date.


PubSub and Connection both have __del__s

Hi,
I've been going through the code base trying to get a better grasp of how redis-py works. I've noticed an ancient issue: #163 , which added dunder dels to a number of classes.
Note that PubSub has a dunder del that, if there's a reference to a connection, will try to disconnect the connection. Note that Connection also has a dunder del, which will try to close it. Now also note that in Pythons < 3.4 (http://legacy.python.org/dev/peps/pep-0442/) these objects, if caught by the garbage collector, will never actually be finalized (i.e. their dunder dels executed). So if PubSub actually does have a reference to a connection, it's dunder del will never actually be called.

Sorry, I had a brain fart; this won't actually be a problem unless there's a reference cycle - the Connection doesn't have a reference to the PubSub. Still, made me think - __del__s can be complex.


Spec generators

Hey Nick,
what do you think?
it was kind hard to find documentation about testing generators with rspec (I even don't know a lot with unit test)... but i found this:
http://stevehodgkiss.com/posts/testing-rails-3-generators-with-rspec
that used this gem:
https://github.com/stevehodgkiss/generator_spec
hope it's OK!
after this commit, it generates the full widget path and also generates all actions tests for that widget

Hey nick, looks like i've got my brand new personal coding coach hehehe
look if it's OK now!

Thanks bro, it's here: https://github.com/apotonick/rspec-apotomo/commit/701568f5009c839761935b2cad674b878d611696
Can we have the same for rspec-cells?

hey nick, is there anything i missed in my tests? 'couse the gem build status is 'failing', shown in readme...


[SPARK-28005][YARN] Remove unnecessary log from SparkRackResolver

What changes were proposed in this pull request?
SparkRackResolver generates an INFO message every time is called with 0 arguments.
In this PR I've deleted it because it's too verbose.
How was this patch tested?
Existing unit tests + spark-shell.

cc @squito @andrasbeni

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Test build #106768 has started for PR 24935 at commit d27c356.

Test build #106768 has finished for PR 24935 at commit d27c356.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106768/
Test PASSed.

Test build #106830 has started for PR 24935 at commit 3b7bf80.

Test build #106830 has finished for PR 24935 at commit 3b7bf80.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106830/
Test PASSed.

Test build #106888 has started for PR 24935 at commit 317d0b5.

Test build #106890 has started for PR 24935 at commit 6d8aec0.

Test build #106888 has finished for PR 24935 at commit 317d0b5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106888/
Test PASSed.

Test build #106890 has finished for PR 24935 at commit 6d8aec0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106890/
Test FAILed.

retest this please

Test build #106895 has started for PR 24935 at commit 6d8aec0.

Test build #106895 has finished for PR 24935 at commit 6d8aec0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106895/
Test PASSed.

lgtm

merged to master, thanks @gaborgsomogyi

Thanks @squito @dongjoon-hyun @srowen @HeartSaVioR


Upgrade sbt-scalaxb from 1.9.0 to 1.9.1

Updates org.scalaxb:sbt-scalaxb from 1.9.0 to 1.9.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalaxb", artifactId = "sbt-scalaxb" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalaxb", artifactId = "sbt-scalaxb" }
}]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #125.


Displaying message when MediaViewer activity is empty

Fix attempt at #1003 .

Sounds good but I'm surprise that the empty message is display every time.
I'm expect to have a condition to display it only if no content is read.

Its working fine on my local computer. Please let me know how do I reproduce the issue.
https://user-images.githubusercontent.com/89119829/159202337-14c27a84-5136-4c6a-aa6c-d991c8a36eb0.mp4

Your latest commit no longer work (see error below).

The previous one worked but I'm expect to change visibility of the message according of the way the activity is launch.

Umm, my latest commit works fine on my pc. Both when opening sugarizer in browser as well as electron. @llaske
https://user-images.githubusercontent.com/89119829/159894296-202e8883-3805-4bf5-94b0-335057fa248c.mp4
As can be seen, the message is visible only when no content is read, and when content is viewed the message is not visible.

I've reproduced the issue on a new environment.
Could you test again on your side?

Tested again on my side, seems to work as shown in the above video though. Please wait, I will once again thoroughly try to check where this inconsistency is coming from.
Just so that we are on the same page, the problem is that on your side the code I want to get merged does not work as shown in the video, right?

@AnandChourasia007 Yes it doesn't work like in your video, I've got an error message in the Javascript console. So I never seen the message.
I suggest you to try to reapply your update on the latest dev branch.

Fixed in https://github.com/llaske/sugarizer/pull/1081


refactor: Adding dependency injection for StorageConnector

Purpose

This PR is the first step towards #2446
Injects StorageConnector as a dependency to FetchTranscription & StartTranscription.
Adds Startup.cs for the azure functions to be able to register the dependencies going forward.
Refactors the corresponding calls to AudioFileInfo & TranscriptionProcessor.
Tested executing all the functions.
Will add corresponding tests soon & update this PR.

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

PR looks good, thanks a lot!
Please do not forget to increment the version in the ARM template.


Duplicate protocol definition of 'RCTBridgeModule' is ignored

Description:
Mac ：10.15.3
Xcode: 11.3
React Native version:
"react": "^16.0.0-alpha.6",
"react-native": "0.43.4",

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
Issues without reproduction steps or code are likely to stall.

Expected Results
Xcode can run it normal

Snack, code example, screenshot, or link to a repository:
Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
You may provide a screenshot of the application if you think it is relevant to your bug report.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

0.43 is pretty old at this point, and not guaranteed to work with xcode 11.3. Can you please test on latest?


IsFunc: fix check templateRecvMethodType

fix https://github.com/goplus/spx/issues/223

Codecov Report

Merging #209 (2c089ee) into main (03f8be9) will decrease coverage by 0.00%.
The diff coverage is 40.00%.

@@            Coverage Diff             @@
##             main     #209      +/-   ##
==========================================
- Coverage   94.77%   94.76%   -0.01%
==========================================
  Files          12       12
  Lines        5777     5829      +52
==========================================
+ Hits         5475     5524      +49
- Misses        234      237       +3
  Partials       68       68

Impacted Files
Coverage Δ

func.go
96.08% <40.00%> (-1.26%)
:arrow_down:

package.go
100.00% <0.00%> (ø)

type_var_and_const.go
98.63% <0.00%> (+<0.01%)
:arrow_up:

codebuild.go
95.83% <0.00%> (+<0.01%)
:arrow_up:

stmt.go
94.58% <0.00%> (+0.08%)
:arrow_up:

builtin.go
94.43% <0.00%> (+0.22%)
:arrow_up:

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 03f8be9...2c089ee. Read the comment docs.


Repo maven releases

Hi,
I am trying to compile the oidc-plugin component and throws me an error regarding the maven repository. When I test the URL, it tells me Access Denied. You can help me with that.
Thank you.

Please paste the complete stacktrace, thanks.

This is the complete stacktrace.
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for nl.finalist.liferay.oidc:oidc-parent:0.2.3-SNAPSHOT: Could not transfer artifact nl.iprofs.pom:parent:pom:2.0.24 from/to releases-public (https://nexus.iprofs.nl/content/repositories/releases-public): Access denied to https://nexus.iprofs.nl/content/repositories/releases-public/nl/iprofs/pom/parent/2.0.24/parent-2.0.24.pom. Error code 401, Unauthorized and 'parent.relativePath' points at wrong local POM @ line 5, column 13
@
[ERROR] The build could not read 1 project -> [Help 1]
org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for nl.finalist.liferay.oidc:oidc-parent:0.2.3-SNAPSHOT: Could not transfer artifact nl.iprofs.pom:parent:pom:2.0.24 from/to releases-public (https://nexus.iprofs.nl/content/repositories/releases-public): Access denied to https://nexus.iprofs.nl/content/repositories/releases-public/nl/iprofs/pom/parent/2.0.24/parent-2.0.24.pom. Error code 401, Unauthorized and 'parent.relativePath' points at wrong local POM @ line 5, column 13
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:422)
at org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:419)
at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:410)
at org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:83)
at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:491)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:219)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

[ERROR]
[ERROR]   The project nl.finalist.liferay.oidc:oidc-parent:0.2.3-SNAPSHOT (/Users/jcperez/Proyectos/bicevida/liferay-oidc-plugin/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for nl.finalist.liferay.oidc:oidc-parent:0.2.3-SNAPSHOT: Could not transfer artifact nl.iprofs.pom:parent:pom:2.0.24 from/to releases-public (https://nexus.iprofs.nl/content/repositories/releases-public): Access denied to https://nexus.iprofs.nl/content/repositories/releases-public/nl/iprofs/pom/parent/2.0.24/parent-2.0.24.pom. Error code 401, Unauthorized and 'parent.relativePath' points at wrong local POM @ line 5, column 13 -> [Help 2]
org.apache.maven.model.resolution.UnresolvableModelException: Could not transfer artifact nl.iprofs.pom:parent:pom:2.0.24 from/to releases-public (https://nexus.iprofs.nl/content/repositories/releases-public): Access denied to https://nexus.iprofs.nl/content/repositories/releases-public/nl/iprofs/pom/parent/2.0.24/parent-2.0.24.pom. Error code 401, Unauthorized
at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:197)
at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:246)
at org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:1000)
at org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:800)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:329)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:469)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:438)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:401)
at org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:419)
at org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:410)
at org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:83)
at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:491)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:219)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact nl.iprofs.pom:parent:pom:2.0.24 from/to releases-public (https://nexus.iprofs.nl/content/repositories/releases-public): Access denied to https://nexus.iprofs.nl/content/repositories/releases-public/nl/iprofs/pom/parent/2.0.24/parent-2.0.24.pom. Error code 401, Unauthorized
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)
at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:193)
... 25 more
Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact nl.iprofs.pom:parent:pom:2.0.24 from/to releases-public (https://nexus.iprofs.nl/content/repositories/releases-public): Access denied to https://nexus.iprofs.nl/content/repositories/releases-public/nl/iprofs/pom/parent/2.0.24/parent-2.0.24.pom. Error code 401, Unauthorized
at io.takari.aether.connector.AetherRepositoryConnector$2.wrap(AetherRepositoryConnector.java:895)
at io.takari.aether.connector.AetherRepositoryConnector$2.wrap(AetherRepositoryConnector.java:1)
at io.takari.aether.connector.AetherRepositoryConnector$GetTask.flush(AetherRepositoryConnector.java:673)
at io.takari.aether.connector.AetherRepositoryConnector.get(AetherRepositoryConnector.java:310)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
... 29 more
Caused by: io.takari.aether.connector.AuthorizationException: Access denied to https://nexus.iprofs.nl/content/repositories/releases-public/nl/iprofs/pom/parent/2.0.24/parent-2.0.24.pom. Error code 401, Unauthorized
at io.takari.aether.connector.AetherRepositoryConnector.handleResponseCode(AetherRepositoryConnector.java:369)
at io.takari.aether.connector.AetherRepositoryConnector.access$8(AetherRepositoryConnector.java:363)
at io.takari.aether.connector.AetherRepositoryConnector$GetTask.resumableGet(AetherRepositoryConnector.java:603)
at io.takari.aether.connector.AetherRepositoryConnector$GetTask.run(AetherRepositoryConnector.java:453)
at io.takari.aether.connector.AetherRepositoryConnector.get(AetherRepositoryConnector.java:304)
... 31 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

Thanks for pointing this out.
I raised an internal ticket about this; I my opinion this repo should allow unauthenticated access indeed. Please bear with me...

Of course I will have patience, the plugin is great and I am working to get roles from the tokenid and be able to assign them to liferay dynamically. Of course if this contribution serves, I will add it for public use

I try again and work fine. Thanks for all your support.
Please close this thread.

Thanks for reporting back, I also understood from my colleague that the issue was solved.

Hi,
I have problem similar to jotaceperez, described in the comment from 22 May 2017. When I try to compile the oidc-plugin, maven throws me an error regarding the maven repository. I work with Liferay 7.0-ga3 so I using plugin in version 0.2.2
Logs :
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for nl.finalist.liferay.oidc:oidc-parent:0.2.2: Could not transfer artifact nl.iprofs.pom:parent:pom:2.0.24 from/to releases-public (https://nexus.iprofs.nl/content/repositories/releases-public): nexus.iprofs.nl and 'parent.relativePath' points at wrong local POM @ line 5, column 13
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project nl.finalist.liferay.oidc:oidc-parent:0.2.2 (C:\Users\Dell\Documents\liferay\liferay-oidc-plugin-oidc-parent-0.2.2\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for nl.finalist.liferay.oidc:oidc-parent:0.2.2: Could not transfer artifact nl.iprofs.pom:parent:pom:2.0.24 from/to releases-public (https://nexus.iprofs.nl/content/repositories/releases-public): nexus.iprofs.nl and 'parent.relativePath' points at wrong local POM @ line 5, column 13: Unknown host nexus.iprofs.nl -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
I would be very grateful if anyone could help me with this.

Yup, you're right, repos have changed again. I'll open this issue again and try to fix it.. Stay tuned.

@Wroblewski-Piotr Now that I read your comment a bit closer, I realize you're using an older version.
I'm sorry, but I'm not planning to backport the nexus url change into the 0.2.2 release. It's working again in master now, will leave it at that.

@gvanderploeg Thanks for Your answer.
Is it posible to get nl.iprofs, in version that I need, to compile plugin in version 0.2.2 from You ? As I wrote in previous comment, I working with Liferay 7.0-ga3 where plugin in version 0.2.2 is used, and I need make only a liitle changes. I do not want to use latest version of plugin because implementation of it could take lot of time, and current solution working really good.
thanks in advance


Add ordered version of the operator

Thanks @jaceksokol -- since Akka's equivalent is ordered, we need the order support you're adding but we could also have a mapAsyncPartitionedUnordered or something like that too - so it's useful to support both ordered and unordered in the internal code.

Thanks @jaceksokol. The key remaining API question is whether to replace the bufferSize parameter with a perPartition paramteter like the Akka API. Or we can have both. But the key question is whether it is feasible to support controlling the parallelism per partition as well as the existing parallelism setting that applies to the full job.

I don't see a point in processing elements in parallel within a partition. From my perspective processing elements sequentially per partition can speed up processing while preserving the order of messages for a key. Processing events per partition in parallel seems to be similar to processing elements in parallel without the notion of a partition and ordering. Am I missing something?

The perPartition is documented at https://doc.akka.io/docs/akka/current/stream/operators/Source-or-Flow/mapAsyncPartitioned.html
Maybe the value is more about buffering and when to apply back pressure than about the number of parallel events that can be processed for a partition value.


Fixed two spacing errors in source/User_Guide/Transactional_Templates/create_edit.md

Quickly proofread and fixed two spacing errors in the document where it read "Editoror" and "Editorby"

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

Hello @churrizo,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


fix(config): allow any url scheme in the manifest

Added manifest permissions to allow the loading of a config from any url
scheme.
Closes #14

This change can be tested using this artifact: https://github.com/Silthus/chrome-enterprise-tab-rotate/suites/492326215/artifacts/2409835

This change allows me to load config files hosted in Azure. Cheers

:tada: This PR is included in version 1.0.2 :tada:
The release is available on:

Chrome Web Store
GitHub release

Your semantic-release bot :package::rocket:


Slot explanation paragraph sometimes gets displayed multiple times on a page

Summary of the bug
On pages for components which have subcomponents, the paragraph above the slots tables (explaining what slots are) gets repeated multiple times throughout the page.
🪜 How to reproduce

Go to the top navigation code page, for example.
Scroll down through the sections for the different subcomponents e.g. "Navigation item details", "Navigation button details".
See that the paragraph under the "Slots" headings is displayed once for each subcomponent slot table, and it is therefore repeated multiple times.

📸 Screenshots or code
This is the paragraph that is repeated:

🧐 Expected behaviour
While this is not a huge deal, it does mean that there is a lot of redundant information being displayed. It should really only be shown once per page at most.

Bigger issue here of looking at how we format the pages with sub children components


Fix/check writable permissions

Still can't run recruit_reviewers().
File "/Users/mandler/projects/openreview-py/openreview/conference/webfield.py", line 46, in set_landing_page
return self.client.post_group(group)
...
openreview.openreview.OpenReviewException: [{'type': 'forbidden', 'path': 'id', 'value': 'adai.ai', 'user'<EMAIL_ADDRESS>Where<EMAIL_ADDRESS>is a member of Program_Chairs.

Somehow I'm not getting these changes when I checkout fix/check-writable-permissions.


fails to build with clang 3.4

Hello,
Trying to compile polybar on debian jessie fails with clang 3.4
on branch master, current commit:
$ cat .git/refs/heads/master
111bfc58e915d2710930e9e2520b54906590622a

Thanks for your support !
With clang 3.4
** Fetching submodules
** Setting build options
** Enable i3 module ------- [Y/n]: n
** Enable volume module --- [Y/n]: Y
** Enable network module -- [Y/n]: Y
** Enable mpd module ------ [Y/n]: n
** Using compiler: g++/gcc
** Executing cmake command
-- The C compiler identification is Clang 3.4.2
-- The CXX compiler identification is Clang 3.4.2
-- Check for working C compiler: /usr/bin/clang-3.4
-- Check for working C compiler: /usr/bin/clang-3.4 -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/clang++-3.4
-- Check for working CXX compiler: /usr/bin/clang++-3.4 -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- No build type specified; using Release
-- Using supported compiler Clang
-- No preferred c++lib specified... linking against system default
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.28")
-- --------------------------
--  Build type: Release
--  Compiler C: /usr/bin/clang-3.4
--  Compiler C++: /usr/bin/clang++-3.4
--  Compiler flags:  -Wall -Wextra -Werror -O3 -pedantic -pedantic-errors -ffunction-sections -fdata-sections
--    release: -O3 -DNDEBUG
--  Linker flags:  -Wl,--gc-sections
--  C++ library: system default
-- --------------------------
--  Build testsuite      OFF
--  Debug logging        OFF
--  Verbose tracing      OFF
--  Draw debug hints     OFF
--  Enable ccache        OFF
-- --------------------------
--  Enable alsa          ON
--  Enable i3            OFF
--  Enable mpd           OFF
--  Enable network       ON
-- --------------------------
--  XRANDR support       ON
--  XRENDER support      OFF
--  XDAMAGE support      OFF
--  XSYNC support        OFF
--  XCOMPOSITE support   OFF
--  XKB support          ON
-- --------------------------
-- Boost version: 1.55.0
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so
-- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found X11: /usr/lib/x86_64-linux-gnu/libX11.so
-- Found X11_XCB: /usr/lib/x86_64-linux-gnu/libX11-xcb.so
-- Checking for module 'fontconfig'
--   Found fontconfig, version 2.11.0
-- Checking for module 'xcb-proto'
--   Found xcb-proto, version 1.10
-- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.9", minimum required is "2.7")
-- XCB[XCB]: Found component XCB
-- Found XCB_XCB: /usr/lib/x86_64-linux-gnu/libxcb.so
-- XCB[ICCCM]: Found component ICCCM
-- Found XCB_ICCCM: /usr/lib/x86_64-linux-gnu/libxcb-icccm.so
-- XCB[EWMH]: Found component EWMH
-- Found XCB_EWMH: /usr/lib/x86_64-linux-gnu/libxcb-ewmh.so
-- XCB[UTIL]: Found component UTIL
-- Found XCB_UTIL: /usr/lib/x86_64-linux-gnu/libxcb-util.so
-- XCB[IMAGE]: Found component IMAGE
-- Found XCB_IMAGE: /usr/lib/x86_64-linux-gnu/libxcb-image.so
-- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb-icccm.so;/usr/lib/x86_64-linux-gnu/libxcb-ewmh.so;/usr/lib/x86_64-linux-gnu/libxcb-util.so;/usr/lib/x86_64-linux-gnu/libxcb-image.so
-- Searching for xcbgen with python2
-- Found xcbgen in /usr/lib/python2.7/dist-packages
-- XCB[RANDR]: Found component RANDR
-- Found XCB_RANDR: /usr/lib/x86_64-linux-gnu/libxcb-randr.so
-- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb-icccm.so;/usr/lib/x86_64-linux-gnu/libxcb-ewmh.so;/usr/lib/x86_64-linux-gnu/libxcb-util.so;/usr/lib/x86_64-linux-gnu/libxcb-image.so;/usr/lib/x86_64-linux-gnu/libxcb-randr.so
-- XCB[XKB]: Found component XKB
-- Found XCB_XKB: /usr/lib/x86_64-linux-gnu/libxcb-xkb.so
-- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb-icccm.so;/usr/lib/x86_64-linux-gnu/libxcb-ewmh.so;/usr/lib/x86_64-linux-gnu/libxcb-util.so;/usr/lib/x86_64-linux-gnu/libxcb-image.so;/usr/lib/x86_64-linux-gnu/libxcb-randr.so;/usr/lib/x86_64-linux-gnu/libxcb-xkb.so
-- xpp: including xcb proto randr.xml
-- xpp: including xcb proto xkb.xml
-- xpp: including xcb proto xproto.xml
-- Found ALSA: /usr/lib/x86_64-linux-gnu/libasound.so (found version "1.0.28")
-- Found Libiw: /usr/lib/x86_64-linux-gnu/libiw.so
-- Configuring done
-- Generating done
-- Build files have been written to: /home/test/tools/polybar/build
** Building project
Scanning dependencies of target xpp
[  1%] Linking CXX static library libxpp.a
list: size, ['red', 'green', 'blue']
list: size, ['red', 'green', 'blue']
[  1%] Built target xpp
Scanning dependencies of target polybar
[  1%] Linking CXX static library libxpp.a
list: size, ['red', 'green', 'blue']
list: size, ['red', 'green', 'blue']
[  1%] Built target xpp
Scanning dependencies of target polybar
[  2%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/alsa.cpp.o
[  4%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/net.cpp.o
[  5%] Building CXX object bin/CMakeFiles/polybar.dir/components/bar.cpp.o
In file included from /home/test/tools/polybar/src/components/bar.cpp:3:
In file included from /home/test/tools/polybar/include/components/bar.hpp:9:
In file included from /home/test/tools/polybar/include/x11/connection.hpp:11:
In file included from /home/test/tools/polybar/include/x11/extensions.hpp:21:
/home/test/tools/polybar/include/x11/xkb.hpp:11:34: error: unknown warning group '-Wkeyword-macro', ignored
      [-Werror,-Wunknown-pragmas]
#pragma clang diagnostic ignored "-Wkeyword-macro"
                                 ^
1 error generated.
bin/CMakeFiles/polybar.dir/build.make:110: recipe for target 'bin/CMakeFiles/polybar.dir/components/bar.cpp.o' failed
make[2]: *** [bin/CMakeFiles/polybar.dir/components/bar.cpp.o] Error 1
CMakeFiles/Makefile2:265: recipe for target 'bin/CMakeFiles/polybar.dir/all' failed
make[1]: *** [bin/CMakeFiles/polybar.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
** Failed to build project

and with clang 3.5:
** Building project
Scanning dependencies of target xpp
[  1%] Linking CXX static library libxpp.a
list: size, ['red', 'green', 'blue']
list: size, ['red', 'green', 'blue']
[  1%] Built target xpp
Scanning dependencies of target polybar
[  2%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/alsa.cpp.o
[  4%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/net.cpp.o
[  5%] Building CXX object bin/CMakeFiles/polybar.dir/components/bar.cpp.o
In file included from /home/adg/tools/polybar/src/components/bar.cpp:3:
In file included from /home/adg/tools/polybar/include/components/bar.hpp:9:
In file included from /home/adg/tools/polybar/include/x11/connection.hpp:11:
In file included from /home/adg/tools/polybar/include/x11/extensions.hpp:21:
/home/test/tools/polybar/include/x11/xkb.hpp:11:34: error: unknown warning group '-Wkeyword-macro', ignored
      [-Werror,-Wunknown-pragmas]
#pragma clang diagnostic ignored "-Wkeyword-macro"
                                 ^
1 error generated.
bin/CMakeFiles/polybar.dir/build.make:110: recipe for target 'bin/CMakeFiles/polybar.dir/components/bar.cpp.o' failed
make[2]: *** [bin/CMakeFiles/polybar.dir/components/bar.cpp.o] Error 1
CMakeFiles/Makefile2:265: recipe for target 'bin/CMakeFiles/polybar.dir/all' failed
make[1]: *** [bin/CMakeFiles/polybar.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
** Failed to build project

different error with clang 3.8:
** Building project
Scanning dependencies of target xpp
[  1%] Linking CXX static library libxpp.a
list: size, ['red', 'green', 'blue']
list: size, ['red', 'green', 'blue']
[  1%] Built target xpp
Scanning dependencies of target polybar
[  2%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/alsa.cpp.o
[  4%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/net.cpp.o
[  5%] Building CXX object bin/CMakeFiles/polybar.dir/components/bar.cpp.o
[  7%] Building CXX object bin/CMakeFiles/polybar.dir/components/builder.cpp.o
[  8%] Building CXX object bin/CMakeFiles/polybar.dir/components/command_line.cpp.o
[  9%] Building CXX object bin/CMakeFiles/polybar.dir/components/config.cpp.o
/home/adg/tools/polybar/src/components/config.cpp:66:43: error: no member named 'value' in
      'boost::optional<boost::property_tree::basic_ptree<std::basic_string<char>, std::basic_string<char>,
      std::less<std::basic_string<char> > > &>'
        if (!base_section || base_section.value().empty()) {
                             ~~~~~~~~~~~~ ^
1 error generated.
bin/CMakeFiles/polybar.dir/build.make:182: recipe for target 'bin/CMakeFiles/polybar.dir/components/config.cpp.o' failed
make[2]: *** [bin/CMakeFiles/polybar.dir/components/config.cpp.o] Error 1
CMakeFiles/Makefile2:265: recipe for target 'bin/CMakeFiles/polybar.dir/all' failed
make[1]: *** [bin/CMakeFiles/polybar.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
** Failed to build project

When commenting out the offending line in polybar/include/x11/xkb.hpp (#pragma clang diagnostic ignored "-Wkeyword-macro"), I get:
Scanning dependencies of target polybar
[  2%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/alsa.cpp.o
[  4%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/net.cpp.o
[  5%] Building CXX object bin/CMakeFiles/polybar.dir/components/bar.cpp.o
[  7%] Building CXX object bin/CMakeFiles/polybar.dir/components/builder.cpp.o
[  8%] Building CXX object bin/CMakeFiles/polybar.dir/components/command_line.cpp.o
[  9%] Building CXX object bin/CMakeFiles/polybar.dir/components/config.cpp.o
In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:137:36: error: no matching constructor for initialization of
      'map<polybar::v2_0_0::loglevel, string>'
  map<loglevel, string> m_prefixes {
                                   ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:270:9: note: candidate template ignored: couldn't
      infer template argument '_InputIterator'
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:236:9: note: candidate constructor template not
      viable: requires 3 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:253:9: note: candidate constructor template not
      viable: requires 2 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last)
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:208:7: note: candidate constructor not viable:
      requires at most 3 arguments, but 4 were provided
      map(initializer_list<value_type> __l,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:171:7: note: candidate constructor not viable:
      requires at most 2 arguments, but 4 were provided
      map(const _Compare& __comp,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:220:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(const map& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:224:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(map&& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:230:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(initializer_list<value_type> __l, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:182:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(const map& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:193:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(map&& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:216:7: note: candidate constructor not viable:
      requires single argument '__a', but 4 arguments were provided
      map(const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:162:7: note: candidate constructor not viable:
      requires 0 arguments, but 4 were provided
      map()
      ^
In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:147:36: error: no matching constructor for initialization of
      'map<polybar::v2_0_0::loglevel, string>'
  map<loglevel, string> m_suffixes {
                                   ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:270:9: note: candidate template ignored: couldn't
      infer template argument '_InputIterator'
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:236:9: note: candidate constructor template not
      viable: requires 3 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:253:9: note: candidate constructor template not
      viable: requires 2 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last)
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:208:7: note: candidate constructor not viable:
      requires at most 3 arguments, but 4 were provided
      map(initializer_list<value_type> __l,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:171:7: note: candidate constructor not viable:
      requires at most 2 arguments, but 4 were provided
      map(const _Compare& __comp,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:220:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(const map& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:224:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(map&& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:230:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(initializer_list<value_type> __l, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:182:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(const map& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:193:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(map&& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:216:7: note: candidate constructor not viable:
      requires single argument '__a', but 4 arguments were provided
      map(const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:162:7: note: candidate constructor not viable:
      requires 0 arguments, but 4 were provided
      map()
      ^
/home/test/tools/polybar/src/components/config.cpp:66:43: error: no member named 'value' in
      'boost::optional<boost::property_tree::basic_ptree<std::basic_string<char>, std::basic_string<char>,
      std::less<std::basic_string<char> > > &>'
        if (!base_section || base_section.value().empty()) {
                             ~~~~~~~~~~~~ ^
3 errors generated.
bin/CMakeFiles/polybar.dir/build.make:182: recipe for target 'bin/CMakeFiles/polybar.dir/components/config.cpp.o' failed
make[2]: *** [bin/CMakeFiles/polybar.dir/components/config.cpp.o] Error 1
CMakeFiles/Makefile2:265: recipe for target 'bin/CMakeFiles/polybar.dir/all' failed
make[1]: *** [bin/CMakeFiles/polybar.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
** Failed to build project

Thanks !

Could you try again with the last 2 commits

thanks for your help !
It fixes this issue apparently but I'm hitting three more afterwards with clang-3.4:
error 1:
In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:137:36: error: no matching constructor for initialization of
      'map<polybar::v2_0_0::loglevel, string>'
  map<loglevel, string> m_prefixes {

error 2:
In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:147:36: error: no matching constructor for initialization of
      'map<polybar::v2_0_0::loglevel, string>'
  map<loglevel, string> m_suffixes {

error 3:
In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:99:54: error: unused parameter 'values' [-Werror,-Wunused-parameter]
  void output(loglevel level, string format, Args... values) const {

the full log:
** Building project
Scanning dependencies of target xpp
[  1%] Linking CXX static library libxpp.a
list: size, ['red', 'green', 'blue']
list: size, ['red', 'green', 'blue']
[  1%] Built target xpp
Scanning dependencies of target polybar
[  2%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/alsa.cpp.o
[  4%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/net.cpp.o
[  5%] Building CXX object bin/CMakeFiles/polybar.dir/components/bar.cpp.o
[  7%] Building CXX object bin/CMakeFiles/polybar.dir/components/builder.cpp.o
[  8%] Building CXX object bin/CMakeFiles/polybar.dir/components/command_line.cpp.o
[  9%] Building CXX object bin/CMakeFiles/polybar.dir/components/config.cpp.o
In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:137:36: error: no matching constructor for initialization of
      'map<polybar::v2_0_0::loglevel, string>'
  map<loglevel, string> m_prefixes {
                                   ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:270:9: note: candidate template ignored: couldn't
      infer template argument '_InputIterator'
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:236:9: note: candidate constructor template not
      viable: requires 3 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:253:9: note: candidate constructor template not
      viable: requires 2 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last)
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:162:7: note: candidate constructor not viable:
      requires 0 arguments, but 4 were provided
      map()
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:171:7: note: candidate constructor not viable:
      requires at most 2 arguments, but 4 were provided
      map(const _Compare& __comp,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:182:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(const map& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:193:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(map&& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:208:7: note: candidate constructor not viable:
      requires at most 3 arguments, but 4 were provided
      map(initializer_list<value_type> __l,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:216:7: note: candidate constructor not viable:
      requires single argument '__a', but 4 arguments were provided
      map(const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:220:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(const map& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:224:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(map&& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:230:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(initializer_list<value_type> __l, const allocator_type& __a)

In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:147:36: error: no matching constructor for initialization of
      'map<polybar::v2_0_0::loglevel, string>'
  map<loglevel, string> m_suffixes {
                                   ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:270:9: note: candidate template ignored: couldn't
      infer template argument '_InputIterator'
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:236:9: note: candidate constructor template not
      viable: requires 3 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:253:9: note: candidate constructor template not
      viable: requires 2 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last)
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:162:7: note: candidate constructor not viable:
      requires 0 arguments, but 4 were provided
      map()
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:171:7: note: candidate constructor not viable:
      requires at most 2 arguments, but 4 were provided
      map(const _Compare& __comp,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:182:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(const map& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:193:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(map&& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:208:7: note: candidate constructor not viable:
      requires at most 3 arguments, but 4 were provided
      map(initializer_list<value_type> __l,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:216:7: note: candidate constructor not viable:
      requires single argument '__a', but 4 arguments were provided
      map(const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:220:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(const map& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:224:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(map&& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:230:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(initializer_list<value_type> __l, const allocator_type& __a)
      ^
In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:99:54: error: unused parameter 'values' [-Werror,-Wunused-parameter]
  void output(loglevel level, string format, Args... values) const {
                                                     ^
3 errors generated.
bin/CMakeFiles/polybar.dir/build.make:182: recipe for target 'bin/CMakeFiles/polybar.dir/components/config.cpp.o' failed
make[2]: *** [bin/CMakeFiles/polybar.dir/components/config.cpp.o] Error 1
CMakeFiles/Makefile2:265: recipe for target 'bin/CMakeFiles/polybar.dir/all' failed
make[1]: *** [bin/CMakeFiles/polybar.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
** Failed to build project

2 errors with clang3.5:
error 1:
In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:137:36: error: no matching constructor for initialization of
      'map<polybar::v2_0_0::loglevel, string>'
  map<loglevel, string> m_prefixes {

error 2:
In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:147:36: error: no matching constructor for initialization of
      'map<polybar::v2_0_0::loglevel, string>'
  map<loglevel, string> m_suffixes {

the full log:
** Building project
Scanning dependencies of target xpp
[  1%] Linking CXX static library libxpp.a
list: size, ['red', 'green', 'blue']
list: size, ['red', 'green', 'blue']
[  1%] Built target xpp
Scanning dependencies of target polybar
[  2%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/alsa.cpp.o
[  4%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/net.cpp.o
[  5%] Building CXX object bin/CMakeFiles/polybar.dir/components/bar.cpp.o
[  7%] Building CXX object bin/CMakeFiles/polybar.dir/components/builder.cpp.o
[  8%] Building CXX object bin/CMakeFiles/polybar.dir/components/command_line.cpp.o
[  9%] Building CXX object bin/CMakeFiles/polybar.dir/components/config.cpp.o
In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:137:36: error: no matching constructor for initialization of
      'map<polybar::v2_0_0::loglevel, string>'
  map<loglevel, string> m_prefixes {
                                   ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:270:9: note: candidate template ignored: couldn't
      infer template argument '_InputIterator'
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:236:9: note: candidate constructor template not
      viable: requires 3 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:253:9: note: candidate constructor template not
      viable: requires 2 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last)
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:208:7: note: candidate constructor not viable:
      requires at most 3 arguments, but 4 were provided
      map(initializer_list<value_type> __l,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:171:7: note: candidate constructor not viable:
      requires at most 2 arguments, but 4 were provided
      map(const _Compare& __comp,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:220:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(const map& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:224:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(map&& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:230:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(initializer_list<value_type> __l, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:182:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(const map& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:193:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(map&& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:216:7: note: candidate constructor not viable:
      requires single argument '__a', but 4 arguments were provided
      map(const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:162:7: note: candidate constructor not viable:
      requires 0 arguments, but 4 were provided
      map()
      ^
In file included from /home/test/tools/polybar/src/components/config.cpp:4:
In file included from /home/test/tools/polybar/include/components/config.hpp:9:
/home/test/tools/polybar/include/components/logger.hpp:147:36: error: no matching constructor for initialization of
      'map<polybar::v2_0_0::loglevel, string>'
  map<loglevel, string> m_suffixes {
                                   ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:270:9: note: candidate template ignored: couldn't
      infer template argument '_InputIterator'
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:236:9: note: candidate constructor template not
      viable: requires 3 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last,
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:253:9: note: candidate constructor template not
      viable: requires 2 arguments, but 4 were provided
        map(_InputIterator __first, _InputIterator __last)
        ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:208:7: note: candidate constructor not viable:
      requires at most 3 arguments, but 4 were provided
      map(initializer_list<value_type> __l,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:171:7: note: candidate constructor not viable:
      requires at most 2 arguments, but 4 were provided
      map(const _Compare& __comp,
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:220:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(const map& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:224:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(map&& __m, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:230:7: note: candidate constructor not viable:
      requires 2 arguments, but 4 were provided
      map(initializer_list<value_type> __l, const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:182:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(const map& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:193:7: note: candidate constructor not viable:
      requires single argument '__x', but 4 arguments were provided
      map(map&& __x)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:216:7: note: candidate constructor not viable:
      requires single argument '__a', but 4 arguments were provided
      map(const allocator_type& __a)
      ^
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/bits/stl_map.h:162:7: note: candidate constructor not viable:
      requires 0 arguments, but 4 were provided
      map()
      ^
2 errors generated.
bin/CMakeFiles/polybar.dir/build.make:182: recipe for target 'bin/CMakeFiles/polybar.dir/components/config.cpp.o' failed
make[2]: *** [bin/CMakeFiles/polybar.dir/components/config.cpp.o] Error 1
CMakeFiles/Makefile2:265: recipe for target 'bin/CMakeFiles/polybar.dir/all' failed
make[1]: *** [bin/CMakeFiles/polybar.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
** Failed to build project

Are there no recent version of a c++ lib available in your distro repository?

Well it's not available in the stable version, only on testing.
I tested it and I can confirm it works with gcc 6.2 !

Great project BTW !!
It's all good, thanks for your help.

Thanks!

note: I referenced the wrong issue, it was meant to be referenced to #280


Upgrade guava to 27.0.1

Motivation
As reported in #3493 we're using Guava 21 which has some known vulnerabilities. Upgrade to latest version.

@merlimat @jiazhai do we need this pull request for 2.4.0? or can it be moved to 2.5.0?

@merlimat @sijie I don't think we're hit by the vuln in guava. We should try to track the latest where possible though in any case.

@merlimat Is this PR need to onboard the 2.6.0 release? or we can move it to 2.7.0?

move to 2.7.0


[GHSA-fp9f-44c2-cw27] Code injection via nginx.ingress.kubernetes.io/permanent...

Updates

Affected products
Description
Source code location
Summary

Comments
Update the missing details

Do you mean for this to be the affected product?
https://pkg.go.dev/github.com/kubernetes/ingress-nginx

Do you mean for this to be the affected product? https://pkg.go.dev/github.com/kubernetes/ingress-nginx

Indeed I do. I assume what I entered is incorrect (I'm not hip on how Go package names work). If you have magic to fix it go for it, if not I'm happy to update this PR

I tried to fix my commit with the correct name, I don't have permission unfortunately

Gotcha, so the go package naming scheme is a kinda sorta dns. Look ups are done via the go proxy pkg.go.dev and there's something in there that gives package owners the capacity to publish (or not) specific tags.
https://proxy.golang.org/
So, github.com/kubernetes/ingress-nginx is the package name proposed in this context, but looking at the versions available this would likely be one that we reject due to the discrepancy between the versions discussed and the versions actually available for download.
Looks like k8s.io/ingress-nginx is another path to access the same backing repo and with differing versions again. Neat! Which of the two do you want to go with here? k8s.io/ingress-nginx or github.com/kubernetes/ingress-nginx?

Hi @joshbressers, thanks for your patience as we handle contributions from around the holidays. We ultimately decided to go with k8s.io/ingress-nginx as the affected product because the version on https://pkg.go.dev/k8s.io/ingress-nginx more closely matches the versions used on GitHub, while github.com/kubernetes/ingress-nginx uses pseudoversions on https://pkg.go.dev/github.com/kubernetes/ingress-nginx. There is, of course, room to continue the conversation, but the advisory is now reviewed and you have received credit for your contribution to the information therein. 🙂


Project structure uncommon

Hey guys
I tried whether deps.rs works for my repository here.
But apparently I have my code structured in an uncommon way according to this.
Can you help in what way my rust project is uncommonly structured? As far as I know it's perfectly common :)

But apparently I have my code structured in an uncommon way according to this.

Hm, for me the link you posted works without a problem. :thinking: Did you change anything in the meantime?

But apparently I have my code structured in an uncommon way according to this.

Hm, for me the link you posted works without a problem.  Did you change anything in the meantime?

I didn't change anything but it works for me now as well. Maybe there was an update to deps.rs :) Thank you!


Element ref was specified as a string (root) but no owner was set

Error: Element ref was specified as a string (root) but no owner was set. This could happen for one of the following reasons:

You may be adding a ref to a function component
You may be adding a ref to a component that was not created inside a component's render method
You have multiple copies of React loaded
See https://fb.me/react-refs-must-have-owner for more information.

I'm getting this error too. Not able to use this library.

facing same issue. unbale to use this package.


Support the Partitioned flag on cookies

Is your feature request related to a problem? Please describe.
Add support for the Partitioned flag on cookies
see https://developers.google.com/privacy-sandbox/3pcd/chips

this is complete in 4.3.2


Why this package does not support IDbConnection?

I have to pass IDbConnection to the external library but I cannot find such implementation. Can someone please explain why it wasn't implemented and is there any other alternatives to Xamarin? Thanks.

Switched to Microsoft.Data.Sqlite. Everything works ok so far.


Add caffeine cache implementation

https://github.com/jhipster/generator-jhipster-quarkus/issues/9

[X] Enable User Hibernate second level cache (Entity, relationships and methods)
[X] Enable Entity Hibernate second level cache (Entity and relationships)
[X] Enable Caffeine Quarkus cache (maven and gradle)
[X] Activate cache prompt with Caffeine
[X] Enable UserService cache through Quarkus impl
[X] Update CI
[X] Update npm tests
[x] CI is green
[ ] set cache properties to default values for production purpose

@nshaw @joewhite101
I was a little bit annoyed with duplication code issues in tests, I decided to create a "test context builder API" to have something modular and reusable. No more duplicated code, builder pattern based api, default and generic methods for main cases with the possibility to override context properties such prompts, options...

The Quarkus properties have not been added for the moment. We could do it by 2 ways:

configure for user cache
configure for entity caches by using a needle (Quarkus needle in properties file) -> this mean we need to create a needle, test it...

I have nod idea if we should provide default configuration or let users change it according to they need.
FYI in JHipster we have Java configuration that define default values provided by the JHipster framework: https://github.com/jhipster/generator-jhipster/blob/main/generators/server/templates/src/main/java/package/config/CacheConfiguration.java.ejs#L203 it's a bit different because this Java class configuration while we have properties configuration in Quarkus.
/discuss

@avdev4j , 1) I like the test refactoring, less code especially in this area is always good.  2) I'd favor defaulting to prod-ready settings which would include a default cache configuration. (I assume a cluster-aware implementation, e.g. redis, is also on the roadmap.) I don't think I know enough in this area to comment on which option is better but providing a default will help get a developer one step closer to a full application.

I'd favor defaulting to prod-ready settings which would include a default cache configuration (I assume a cluster-aware implementation, e.g. redis, is also on the roadmap.)

This is my main issue right now. I think the best thing to do is to set caches with default values just like JHipster does.
quarkus.cache.caffeine.ENTITY.maximum-size=100
quarkus.cache.caffeine.ENTITY.expire-after-write=3600S

We need to do this for:

User entity
Authority entity
Each generated Entity

[ ] Add constants for maximum-size and expire-after-write properties
[ ] Update application.properties for both User and Authority
[ ] Add tests in server test generator test suite
[ ] Add needle and needle-api for Quarkus application.properties
[ ] Use needle api, every time we create a new Entity, to add maximum-size and expire-after-write properties
[ ] Add tests in entity-server generator test suite

I will do it tomorrow ;)

Sounds like a good plan, thanks!

Oh and yes, we need to provide a least a solution for distributed cache implementation. Unfortunately, it seems Quarkus does not provide an abstraction for this kind of scenario. The only solution seems to be using a client librairie. I have in mind redis, Infinispan and Hazelcast.
I would like to do it for the next PR, It will be better to separate those from the current one.

@joewhite101 probably has an opinion but we have Infinispan for Entando 6.2 and are adding redis for 6.3, so those would be my preferences, with Hazelcast in third place.
Definitely agree, doing that in its own PR makes sense. This one already has a lot.

I agree, according to main JHipster features I would say:

redis
infinispan (in beta in the main project)
Hazelcast (seems to be to less popular right now)

Redis seems to be quite used by cloud services too but I don't master this point so only suppositions.

How JHipster deal with Spring Cache:
code layer: applicative cache --- hibernate 2nd level cache
                               |
             abstraction layer: Spring cache manager
                               |
          implementation layer:  Caffeine, Redis, EhCache...

It's easy to understand that both applicative and hibernate 2nd level cache share the same implementation, so if we use a distributed or centralized one we can't have issue with synchronization between different instances.
Also, the code won't change because it will always use the Spring annotations, only the configuration part will be different according to the chosen solution.
Unfortunately, this is not possible in Quarkus. We have Quarkus cache but it has only one impl with Caffeine. If we use that with Hibernate 2nd level cache we would not have issue because everything is local.
Indeed, because Hibernate handles is own cache impl, we can't use it with distributed one.
For me we coud only to that :

Allow hibernate 2nd level cache only with Caffeine or without cache aka 'no' (or any local caching solution in the future)
Provide another caching solution outside Quarkus cache with client like Redis or Infinispan (will be done in another PR)

The behavior will be (include in this PR):
On app generation

You chose Caffeine: User and UserService have a Quarkus cache impl (userByLogin and userByEmail), application.properties has configuration set

    @CacheResult(cacheName = USERS_BY_LOGIN_CACHE)
    public static Optional<User> findOneWithAuthoritiesByLogin(String login) {
        return find("FROM User u LEFT JOIN FETCH u.authorities WHERE u.login = ?1", login)
            .firstResultOptional();
    }

    @CacheInvalidate(cacheName = User.USERS_BY_LOGIN_CACHE)
    public void clearUserCachesByLogin(String login) {}

    # configure your caches
    quarkus.cache.caffeine."usersByEmail".maximum-size=100
    quarkus.cache.caffeine."usersByEmail".expire-after-write=3600S
    quarkus.cache.caffeine."usersByLogin".maximum-size=100
    quarkus.cache.caffeine."usersByLogin".expire-after-write=3600S

You chose Hibernate 2nd level cache: User and Authority have annotations

    @Entity
    @Table(name = "jhi_user")
    @Cacheable
    public class User extends PanacheEntityBase implements Serializable {};

    @Cache(usage = CacheConcurrencyStrategy.READ_ONLY)
    @BatchSize(size = 20)
    public Set<Authority> authorities = new HashSet<>();

On entity generation e.g. foo
For this part nothing will be done with Caffeine, it's up to developer to do something close we have in User/UserService. Applicative cache is more related to business logic.

Hibernate second level cache is selected: The entity has all annotations, we add properties for each cache in application properties (relationship includes)

    @Entity
    @Table(name = "foo")
    @Cacheable
    @RegisterForReflection
    public class Foo extends PanacheEntityBase implements Serializable {}

    @Cache(usage = CacheConcurrencyStrategy.READ_WRITE)
    public Set<Label> labels = new HashSet<>();

    quarkus.hibernate-orm.cache."io.github.jhipster.sample.domain.Foo".expiration.max-idle=3600S
    quarkus.hibernate-orm.cache."io.github.jhipster.sample.domain.Foo".memory.object-count=100
    quarkus.hibernate-orm.cache."io.github.jhipster.sample.domain.Foo.labels".expiration.max-idle=3600S
    quarkus.hibernate-orm.cache."io.github.jhipster.sample.domain.Foo.labels".memory.object-count=100

@nshaw @joewhite101 @danielpetisme
I wrote this documentation to explain a bit more how this works, hope it will help  (we could update the readme to add that).

Regarding the caching doc, should it be done in the README.MD or in an external documentation


Refactor the code

Refactor: Codebase Cleanup and Application Structure Enhancement
Summary
This PR focuses on codebase cleanup and improving the structure of the application to adhere to best practices, including YAGNI (You Aren't Gonna Need It), KISS (Keep It Simple, Stupid), DRY (Don't Repeat Yourself), and the Ruby style guide. Additionally, SOLID principles, with a special emphasis on the Single-responsibility Principle, have been followed to create a cleaner and more maintainable codebase.
Changes Made
Codebase Cleanup

Conducted a thorough code review and identified areas for improvement.
Removed unnecessary or redundant code that violated the YAGNI and DRY principles.
Simplified complex logic to adhere to the KISS principle.

Application Structure Enhancement

Extracted and refactored pieces of logic into separate classes to promote single responsibility and better code organization.
Introduced classes for managing books, people, and rentals, ensuring each class has a clear and distinct purpose.
Created a separate class, Menu, for handling user interactions and menu options.
Updated main.rb to serve solely as the entry point for the application, responsible for starting the code and asking the user for initial choices or quitting.

Style Guide and SOLID Principles

Ensured the codebase follows the Ruby style guide for readability and consistency.
Adhered to SOLID principles, with particular emphasis on the Single-responsibility Principle, to create more maintainable and modular code.

Reviewer's Notes
I invite the code reviewer to thoroughly examine the refactored codebase and provide feedback on code quality, design, adherence to best practices, and adherence to SOLID principles. Your insights are highly valued. Thank you for taking the time to review this PR.

Thank you @Shedrack-Sunday


Internal api fixes

Changes
Removed use of internal itwin.js internal APIs from source code.
Note: alpha and beta APIs are still in use where there are no fully public alternatives.
Testing
Ran coverage testing to execute all unit tests.

Did a quick pass didnt see any internal api usage? Most of it was just eslint disable deprecation comments?
Shouldnt this pr fold in changes from https://github.com/iTwin/appui/pull/198 now?