Implement IChatClient on HuggingFaceApi

 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.


Restrict login access to only WATO google accounts and check for groups

Currently users can login with any google account (including non-WATO accounts). We want to enforce that only users who have google accounts of the format<EMAIL_ADDRESS>can login.
Additionally, we want to see if we can whitelist specific non-WATO accounts (i.e. our Finance Coordinator's uwaterloo email) so that we can authenticate specific individuals that should have access to our finance system
As a final task, investigate whether or not its possible to check for a users google group - we want to be able to see if given a user id, whether or not they're part of a given user google group.
e.g<EMAIL_ADDRESS><EMAIL_ADDRESS>You can view your own groups here: https://groups.google.com/u/0/my-groups

Partially done: issue is we are doing validation in the frontend currently. need to switch to backend somehow, want to avoid using firebase functions since they cost money.


Draft 2134 add general option signif_digits

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[ ] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[ ] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[ ] Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
[ ] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[ ] Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
[ ] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[ ] Address any updates needed for vignettes and/or templates
[ ] Update NEWS.md under the header # admiral (development version) if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[ ] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[ ] Address or fix all lintr warnings and errors - lintr::lint_package()
[ ] Run R CMD check locally and address all errors and warnings - devtools::check()
[ ] Link the issue in the Development Section on the right hand side.
[ ] Address all merge conflicts and resolve appropriately
[ ] Pat yourself on the back for a job well done! Much love to your accomplishment!

@bms63 @zdz2101 would appreciate some early feedback on this. I have created a new general option to hold significant digits, do you think we need to document it anywhere else? We mentioned it in Lab Grading Vignette but not that its a general option. I couldn't see any particular documentation around general options, except in the man files of the functions.

I have two suggestions:

We could print messages or warnings when signif is used when the user has not actively specified digits themselves. This way we can ensure that users are aware of our use of signif.

For some functions we expect users to input comparisons themselves (I think). We should mention in the documentation for these arguments that we encourage the use of signif. Alternatively, we could scan their inputs and return a message or a warning when no such measures were taken (that is probably a bit more tricky, and a bit more hand-holding, but I think it would be pretty useful).

What do you all think?

I have two suggestions:

We could print messages or warnings when signif is used when the user has not actively specified digits themselves. This way we can ensure that users are aware of our use of signif.
For some functions we expect users to input comparisons themselves (I think). We should mention in the documentation for these arguments that we encourage the use of signif. Alternatively, we could scan their inputs and return a message or a warning when no such measures were taken (that is probably a bit more tricky, and a bit more hand-holding, but I think it would be pretty useful).

What do you all think?

I'm okay with the first option.  @millerg23 could you implement with this PR?
The second one sounds very tough to implement to me.  Also a little invasive to the user where now admiral is watching over them :)

Does anyone know what the See Also is used here? @pharmaverse/admiral

ah nvm i see that this is being used in those functions.

Okay ... got another one!!  @pharmaverse/admiral  Is this statement true?

@bms63 @zdz2101 would appreciate some early feedback on this. I have created a new general option to hold significant digits, do you think we need to document it anywhere else? We mentioned it in Lab Grading Vignette but not that its a general option. I couldn't see any particular documentation around general options, except in the man files of the functions.

I think if we incorporate the messaging suggested by @StefanThoma, couple with the updated documentation and mention in vignette, then we have done the best that we can.   Love to see the blog post pointed to as well!!
After that - just need some tests.  Many thanks again!!

@millerg23 just checking on progress and if you need anything from me?

@bms63 @zdz2101 @StefanThoma I think I addressed all QC comments. Added a unit test for derive_var_anrind, to show how increasing significant digits changes the result. Added links to blog post in several places included NEWS file. Also added checks that a positive integer is being passed in for significant digits in the 2 functions that use it

@bms63 @StefanThoma thanks for feedback, I added in suggested text.


Semantic highlighting flickers on 1.62.0 and later

Does this issue occur when all extensions are disabled?: Yes(except for rust-analyzer as that provides the highlighting)

VS Code Version: 1.62.0-insider b3318bc0524af3d74034b8bb8a64df0ccf35549a
OS Version: Windows 10

Steps to Reproduce:

Open a rust project with the rust-analyzer installed
Type in a rust file where semantic highlighted tokens can be observed.

All the semantic tokens will lose their coloring until the server resends the highlighting response that has been requested by the client. This does not occur on VSCode 1.61.0 it does occur on 1.62.0(non-insider) though.
cc https://github.com/rust-analyzer/rust-analyzer/issues/10690

I'm not sure when this started since I only started to notice it and get annoyed by it earlier yesterday but as of recently the syntax highlighting that underlines mutable bindings in VSCode has been persistently annoying. Everytime I start and stop typing, every mutable binding on my screen briefly loses its underlining. This occurs even if I'm not changing any actual code
Even weirder, it only really happens when I type two characters consecutively. Typing one, pausing, then typing another doesn't trigger it. See below:

Let me know if there's anything else I can provide, but here are my relevant versions:
rust-analyzer version: a824768 2021-11-04 nightly vscode-insiders version: 1.62.0-insider b3318bc0524af3d74034b8bb8a64df0ccf35549a OS: Win 10

@Veykril I cannot reproduce the flicker on Linux. I believe this is not a problem with semantic tokens, but a problem with the rendering of underlines. To rule out a problem related with underlines, could you please configure the following:
  "editor.semanticTokenColorCustomizations": {
    "rules": {
      "parameter": "#ff0000"
    }
  }

https://user-images.githubusercontent.com/5047891/141199601-417054c1-36d7-4a39-b7b0-1427a81e6d7c.mp4
To give you an idea, this is the kind of issue we have seen in the past: https://github.com/microsoft/vscode/issues/76642

This is unfortunately not just an issue with underlines as can be seen here, the issue becomes more apparent in bigger rust files(when the server takes longer to calculate the highlighting again)

Steps to verify

clone https://github.com/rust-analyzer/rust-analyzer
install rust and the rust analyzer extension
configure:

  "editor.semanticTokenColorCustomizations": {
    "rules": {
      "parameter": "#ff0000"
    }
  }

open a Rust file and type in it

In 1.62.1, depending on your speed, tokens would flicker.

No more flicker in VS Code 1.62.2 (b87304b8e799b5ce827be46f8e185d37)
(And I could reproduce the flicker in 1.62.0 - and I noticed that the flicker starts after some time, not immediately...)


[Outlook] (format) Add separators between members/methods

Docs Build status updates of commit 8f79a18:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/objectmodel/preview-requirement-set/office.context.mailbox.diagnostics.md
:white_check_mark:Succeeded

docs/reference/objectmodel/preview-requirement-set/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/preview-requirement-set/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/objectmodel/preview-requirement-set/office.context.mailbox.userProfile.md
:white_check_mark:Succeeded

docs/reference/objectmodel/preview-requirement-set/office.context.md
:white_check_mark:Succeeded

docs/reference/objectmodel/preview-requirement-set/office.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/office.context.mailbox.diagnostics.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/office.context.mailbox.userProfile.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/office.context.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/office.md
:white_check_mark:Succeeded

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


Batch matrix-matrix product slower than Pytorch

I'm doing a batch matrix multiplication using matmul but it seems to be slower than using bmm function from Pytorch. Specifically,
sentence = tf.constant(tf.random.normal([10240, 32, 3]))
w = tf.constant(tf.random.normal([10240, 3, 1]))

%timeit tf.matmul(sentence, w)
725 µs ± 9.57 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

compared to
sentence = torch.randn(10240, 32, 3).to(device)
w = torch.randn(10240, 3, 1).to(device)

%timeit torch.bmm(sentence, w)
78.5 µs ± 14 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

Is there anyway to speed up the batch matrix-matrix product computation?
Also, normal matrix multiplication seems to be slightly slower than Pytorch
sentence = tf.constant(tf.random.normal([10240, 32]))
w = tf.constant(tf.random.normal([32, 1]))

%timeit tf.matmul(sentence, w)
42.6 µs ± 807 ns per loop (mean ± std. dev. of 7 runs, 10000 loops each)

compared to
sentence = torch.randn(10240, 32).to(device)
w = torch.randn(32, 1).to(device)

%timeit torch.mm(sentence, w)
19.2 µs ± 1.38 µs per loop (mean ± std. dev. of 7 runs, 10000 loops each)

but I guess that's between the acceptable limits.
Tested with eager mode both on 1.13 and 2.0-alpha.
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): Binary
TensorFlow version (use command below): Both 1.13 and 2.0-alpha
Python version: 3.7
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: CUDA 10.0/CuDNN 7.3.1
GPU model and memory: NVidia Titan V

When a statement torch.bmm returns, it does not mean the computation has finished. The computation on GPU tensors is asynchronous.
So you cannot use %timeit to time it.
Also, most cuda functions are slower in the first few iterations, which are often excluded from timing.

@lioutasb Please provide simple reproducible code to investigate it further.

@lioutasb Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


configurationRegistry Library

The implementation and UI of the vscode configurationRegistry has progressed a long way from the initial implementation.
If the configurationRegistry was pulled out into its own library, it would be very powerful tool.
I see two parts to this library, the first part is the configurationRegistry itself that would allow developers to add and defined configurations to a registry.
The send part to this, would be a UI component that would allow editing of the registry itself to create the override file.

@KamalAman Are you asking to extract configuration component into separate node_module?

Yes, if that is something that would be possible.

Sorry we do not have plans to do it.


False positives in reported critical battery states

Strange behavior, seen this a few times (every few weeks roughly) already, today I took the time to have a look at it:
binary_sensor.lock_door_a_battery_low became active, so did the binary_sensor.lock_door_a_keypad_battery_low entity:

Please note this is the lock battery entity (the keypad has none according to https://github.com/technyon/nuki_hub/issues/257) which is obviously NOT critical:

I also checked the lock and Keypad battery state with the Nuki iOS app immediately (roughly 16:53):

lock: exactly as provided by Nuki-Hub to HA (as shown above)
keypad: green text "ausreichend geladen" (in English basically: battery is okay)

I'm wondering

where this comes from
how I could debug this once it happens again (where exactly to look at in MQTT Explorer at the time this happens again?)

Of course it can be the lock and or Keypad (at the same time? hmm...) itself, but as I checked the iOS app immediately and everything was looking fine there...
My theory is: lock and/or keypad were sending rubbish for a very short time. NH of course catched it. Exactly one hour later the correct state has been read by NH from the lock and transfered via MQTT to HA again. Does that make sense and match these NH settings?
NUKI Hub version: 8.26
...
lockStInterval: 3600
configInterval: 3600
batInterval: 7200
kpInterval: 1800
kpEnabled: true
...

Hi,
The battery percentage/critical information is actually sent in the lock state request (lockStInterval) ... so it should correct itself either after the timeout of one hour, or if you execute some lock action.
Why this would be incorrectly reported I can only guess. Bluetooth should have enough checks to prevent corrrupt data to be received. So either the lock sends the wrong data sometimes, or it gets corrupted after receiving it .... both very hard for me to reproduce.
Other than this everything works fine?

Other than this everything works fine?

Yes. Very stable, no issues.
What about debug options to check if it's actually sent from the lock itself?

This firmware will the relevant fields to serial and/or mqtt. To decode, check the API documentation:
https://developer.nuki.io/page/nuki-smart-lock-api-2/2#heading--keyturner-states
Fields "Critical Battery state" and "Accessory Battery State".
nuki_hub-8.29-dbg-1.zip

I need to update my HA Core first (still running NH 8.26 because of #227) to not run into https://github.com/technyon/nuki_hub/issues/227 again.

is this could be about this? the battery dropped to 60% and then up again to more than 90%
Never saw a similar behaviour in the last 3 weeks

Unfortunately I have no good explanation. NUKI Hub just forwards to MQTT whatever battery level/state the lock sends. It  would be interesting to know what level the App would report at the same time, but that's gound to be quite hard to catch.

@technyon Makes sense. I will try to catch this information next time it happens. I was scared because I thought the battery wouldn't last a month! :D

@cagnulein Were you able to investigate the issue further?

@technyon didn't have issue again after that

ok, I'll close for now then. Should the issue come up again, let me know.

I know this issue is closed. And I did not see this issue for a quite long time. But just now two things happened:

"battery low" entity got triggered

Very very strangely: the "battery level" value is, well... a "bit" strange - I mean 100 % is great, and more is even better right 🤣

At the same time the "battery voltage" is completely fine:

I checked MQTT:

At the same time directly in Nuki iOS app:

Seems like this wrong reading happened right during/after a NH restart:

Another (manual) NH restart "solved" the current incident:

I lost a bit track of this issue, not sure if there was an update meanwhile trying to handle those obviously wrong values (admitted: the battery level > 100 % thing is new, could be filtered...). Disclosure: I'm on NH v8.26.
--> Edit: ah I see, it seems like 8.27 had some juice in there to handle this, right? Wanted to share the > 100 % experience anyway.

If a level above 100% is reported, this must be a fluke in the Nuki firmware. There are 6 bits representing the battery level, you multiply the value by 2 and that's the level. Sure it could be filtered.


Title should now be editable for Users

#818
Title was already in the table as a column. So I just had to update the code a bit so it's updateable
Changelog:

Added Title in serializers
Updated form to include title
Updated details page to include title

 User Management | Add title as an optional field when creating a new user |2|


tcpbridge doesn't seem to work with multiple --p2p

One works but multiple fails.. why?

Oh it does.. I just don't know how argparse works.
Wrong:
--p2p 1/1-2/1 --p2p 1/2-3/1

Correct use:
--p2p 1/1-2/1 1/2-3/1


Update DG

Target user profile, value proposition, user stories, use cases, non-functional requirements, and glossary added for next iteration


Add codepen examples for tutorial

We keep talking about it, so I went ahead and gave it a shot.
I used codepen because JsBin requires a Pro account to embed HTTPS bins, which is a bummer. The default codepen styling works ok though w/ the site aesthetic IMO.
I made them click-to-load in the interest of not slowing the site down any more than necessary. Here's an example of the embed before clicking

and then after

The pens aren't editable on the page (because that requires a Pro account) but even seeing them up & working seems pretty worthwhile to me.
Thoughts? Should I take this further? I think the homepage is probably the biggest bang for our buck in terms of showing live examples so limited it to that page, but they're simple enough to add to other pages if it's worthwhile.

LGTM :-)


[SE-0133] flatten() has been renamed to joined()

Depends on apple/swift#3809

This code could just use flatMap, I'm going to fix it to just do that instead so you can proceed with SE-0133 with less overhead.

Done in fae6d5e62fca3993c11e427d36c0bda28c3e1db0.

Great, thanks!


Inspector - Include option to install custom modules with the powershell installer

Include option to install custom modules with the powershell installer

Need to update the branch in the code when this is complete.


Add Nong Song: Polargeist x Black and Yellow

Song Name
Polargeist x Black and Yellow
Artist Name
Step, Wiz Khalifa
Source
Direct file download
Youtube Link
No response
Direct File Link
https://cdn.discordapp.com/attachments/666654256908206101/1269788886201008178/Polargeist.mp3?ex=66b1568e&is=66b0050e&hm=64c900e27773200a0560aa2a84233bd9afcc91e481e5f1b5d035257d76f1e401&
Song ID
2
Start Offset [ms]
0
Extra
No response

reject
non-YouTube sources are not supported, unless it is a permanent direct download link from a CDN that has given permission for Auto Nong to download from
(yours is not permanent)


Add Overflow Hidden to "Site" Content Container

Jira
http://vjira2:8080/browse/BDS-1959
Summary
Small CSS update to the "Site" component to prevent negative margin offsets from adding extra whitespace on the bottom of the page + shadows from spilling out.

This update was originally required for Academy's homepage designs but could also be used in any places where we want to have Cards getting pulled up / over into neighboring sections.

Side note 1. I know overflow: hidden; might look scary but considering that anything that would normally overflow (ex. the global header / dropdown) is contained within a separate region, this PR should have a quite low risk.

Side note 2. The original homepage build absolutely required this but the most recent iteration seems to tolerate not having this slightly more (although shadows still spill out). I'd still rather see us get this in given the extra whitespace problems probably will return elsewhere otherwise.

How to test

? Any thoughts?

Appreciate this being in its own PR-- small but worth discussion.
I know the header component in Drupal targets .c-bolt-site__content, so there are potential for gotchas there. There are also some tricky things that happen with mobile search filters (not a Bolt component). I tested both briefly though and didn't see any issues.
CC @charginghawk in case there's anything else you can think of that might be affected.
Otherwise, approved :shipit:!

@remydenton I'm gonna get this merged down to master to keep our punch list moving along -- plenty of time to still discuss if we need it 👍


Enabling the OpenJS Foundation CLA bot

Hi, I've been talking with @sokra and @chenxsan about changing from the old JSF CLA bot to the new OpenJS Foundation EasyCLA bot. If you're a regular contributor to webpack, you'll want to keep reading for some tips on handling the transition.
First, some brief background. A few years ago the JS Foundation merged with Node.js Foundation to form the OpenJS Foundation. The JS Foundation required a CLA, and operated a bot to enforce signatures. The OpenJS Foundation no longer requires projects to use a CLA; it is left to each project's maintainers to decide whether to use the DCO (at minimum) or the OpenJS Foundation CLA.
For projects that continue using a CLA, two big things changed. First, we're using a different tool called EasyCLA. It is developed and managed by the Linux Foundation (including the underlying infrastructure). CLAs can be signed either by individuals acting on their own behalf, or signed by companies on behalf of their employees. Also, because we're working from a centralized CLA infrastructure, contributors who sign the OpenJS Foundation CLA once are covered for any other OpenJS Foundation projects.
Second, we've changed the text of the CLA. The JSF CLA was essentially a bespoke wrapper around the text of the DCO, which meant contributors (and their legal counsel) would have to evaluate something completely new. In keeping with the Principle of Least Astonishment, we've changed to the much more common Apache-style CLA templates. If you need your company to sign your CLA, there's now a much better chance your counsel will recognize what they're seeing.
Because the organization and the CLA text have both changed, we can't continue to use the old signatures. Subsequent contributions will require you to sign the new document. To be clear, this only applies to new contributions; prior contributors do not need to go back and re-sign the document unless they make a new contribution.
So what do you need to do? You can always just wait until the bot is enabled and sign the doc when you open your first PR. If you aren't already in the system, it'll leave a comment on your PR with a link to follow. If you want to make things easier, or if you're a high-volume contributor and want to get it out of the way early, you can pre-sign the OpenJS Foundation CLA by opening a trivial PR against this repo (we periodically close open PRs).
If you have any questions, please ask!

I am 👍🏻 on this, the old bot is a bit buggy as well.

Following up on this, I've just enabled EasyCLA across both https://github.com/webpack and https://github.com/webpack-contrib and deleted the webhook for the JSF CLA.
@snitin315 I see in another commit that the old bot was hung up on a response (i.e., the license/cla check never returns). Based upon some other projects that were using the JSF CLA infra, here's one thing that seems to work:

In the repo settings, I go into Branches and edit the branch protection rules
I remove license/cla
Closing and immediately reopening the PR seems to retrigger the checks, and clear out the license/cla one.

I see this one has that issue, I'm going to attempt to close/re-open and see if it fixes it.

Thank you help, I think we can close it since we reconfigured it everywhere


incorrect url in the readme for "CAPI tilt guide"

URL for "CAPI tilt guide" is incorrect. it refers to non existing page https://master.cluster-api.sigs.k8s.io/developer/tilt.html

/assign

@sanya301 thanks for fixing this issue


VuesticSwitch toggle listen for option change

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

I'm submitting a ...

[ ] bug report
[x] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

Do you want to request a feature or report a bug?
Feature

What is the current behavior?
When using a VuesticSwitch component there is no way to listen for element change. It is possible to listen for the v-on:input event, however the problem is that this is fired when component is mounted and therefore it cannot be used to track option changes in the switch component.

If the current behavior is a bug, please provide the steps to reproduce, ideally also a screenshot or gif if it's a style issue
To reroduce:

<template>

      <vuestic-switch v-on:input="updated" v-model="globalVisibility">
        Visible
        Hidden
      </vuestic-switch>

</template>

What is the expected behavior?
The alert should not occur as soon as the component is mounted. This is not the case

What is the motivation / use case for changing the behavior?
In order to correctly listen for element change we either need to introduce a change event to be emitted in the setValue method, or we can comment out this line) from the component

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
N/A

Thanks.
Works as you described in for toggle and checkbox elements in 2.0.


Add Ruby 2.4 to the test matrix

Ensure that old rubies use Nokogiri 1.6.8
Fixes #1453

Related: I've added PR #1455 to remove support for the unmaintained Ruby 1.9.x.


PDF reference documentación support for spring Spring Kafka 3.2.x

Hi, I have observed that the last release version with pdf support is:

https://docs.spring.io/spring-kafka/docs/3.0.x/reference/

But the following version doesn’t have pdf support:

https://docs.spring.io/spring-kafka/docs/3.1.x/
https://docs.spring.io/spring-kafka/docs/3.2.x/
https://docs.spring.io/spring-kafka/docs/3.3.x/
https://docs.spring.io/spring-kafka/docs/current/

In theory, the GA version is 3.2.x but it has not a pdf version:
https://spring.io/projects/spring-kafka#learn
can you add it?
many thanks in advance
Juan Antonio

Hi @jabrena, After the 3.0.x generation, we moved to a new antora-based model for reference documents. The PDF output is no longer available as before.


Need export  time series data to storage

If I need to export the time series data of a certain stage of a process into the database, for example export gpu usage to my Influxdb, is that some features or plugins can do it?

You would have to add a plugin for storing statistics in databases


Update wordings on Jira configuration page to question-based sentences

Description
To help users easily understand

why to configure
what to configure
how to configure
during the plugin configuration, especially Jira configuration page

Describe the solution you'd like
Change the description/tips to question-based sentences.
For instance, now the description for "issue type mapping" is

"Your issue types will be converted to 3 standard types for metrics calculation, such as requirement count.

For better understanding, we can modify it to something like:

What issue types would you consider as a requirement?
What issue types would you consider as a bug?
What issue types would you consider as a incident?

Will be addressed #1862


More control over the xml_generator command ?

I am trying to parse the libC library, I had it working on Ubuntu. I've now switched to nixos but the working castxml command doesn't seem to be built from pygccxml.
My current python code has:
xml_generator_config = parser.xml_generator_configuration_t(
            xml_generator_path=generator_path,
            xml_generator=generator_name,
            include_paths=[
                "/nix/store/c30dlkmiyrjxxjv6nv63igjkzcj1fzxi-gcc-6.4.0/lib/gcc/x86_64-unknown-linux-gnu/6.4.0/include",
                "/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include",
            ],
            cflags=" ",
            castxml_epic_version=1,
            )

with pygccxml 1.9.1 and castxml
castxml -v
clang version 4.0.1 (tags/RELEASE_401/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir:
Found candidate GCC installation: /nix/store/052l3p8a4m9iabs1smf1myj3g2w6rlij-gcc-6.4.0/lib/gcc/x86_64-unknown-linux-gnu/6.4.0
Found candidate GCC installation: /nix/store/052l3p8a4m9iabs1smf1myj3g2w6rlij-gcc-6.4.0/lib64/gcc/x86_64-unknown-linux-gnu/6.4.0
Selected GCC installation: /nix/store/052l3p8a4m9iabs1smf1myj3g2w6rlij-gcc-6.4.0/lib64/gcc/x86_64-unknown-linux-gnu/6.4.0
Candidate multilib: .;@m64
Selected multilib: .;@m64

pygccxml generates and calls the following command (which fails):
/nix/store/bgsr6clnq2ivppapayqdbzklkmqbd75b-CastXML-20171003/bin/castxml  -nostdinc -I/nix/store/c30dlkmiyrjxxjv6nv63igjkzcj1fzxi-gcc-6.4.0/lib/gcc/x86_64-unknown-linux-gnu/6.4.0/include -I/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include   -I"." -I"/nix/store/c30dlkmiyrjxxjv6nv63igjkzcj1fzxi-gcc-6.4.0/lib/gcc/x86_64-unknown-linux-gnu/6.4.0/include" -c -x c++ --castxml-cc-gnu /home/teto/.nix-profile/bin/clang++ --castxml-output=1 -o /run/user/1000/tmp6d6aac0v.xml test.h
/nix/store/bgsr6clnq2ivppapayqdbzklkmqbd75b-CastXML-20171003/bin/castxml  -nostdinc -I/nix/store/c30dlkmiyrjxxjv6nv63igjkzcj1fzxi-gcc-6.4.0/lib/gcc/x86_64-unknown-linux-gnu/6.4.0/include -I/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include   -I"." -I"/nix/store/c30dlkmiyrjxxjv6nv63igjkzcj1fzxi-gcc-6.4.0/lib/gcc/x86_64-unknown-linux-gnu/6.4.0/include"  -x c++ --castxml-cc-gnu /home/teto/.nix-profile/bin/clang++ --castxml-output=1 -o /run/user/1000/tmp6d6aac0v.xml test.h
In file included from test.h:3:
In file included from /nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/stdio.h:862:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:360:7: warning: use of logical '&&' with constant
      operand [-Wconstant-logical-operand]
      && __builtin_constant_p (__n)
      ^  ~~~~~~~~~~~~~~~~~~~~~~~~~~
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:360:7: note: use '&' for a bitwise operation
      && __builtin_constant_p (__n)
      ^~
      &
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:360:7: note: remove constant to silence this warning
      && __builtin_constant_p (__n)
~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:43:8: error: redefinition of a 'extern inline'
      function 'vsprintf' is not supported in C++
__NTH (vsprintf (char *__restrict __s, const char *__restrict __fmt,
       ^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:43:8: note: previous definition is here
__NTH (vsprintf (char *__restrict __s, const char *__restrict __fmt,
       ^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:74:8: error: redefinition of a 'extern inline'
      function 'vsnprintf' is not supported in C++
__NTH (vsnprintf (char *__restrict __s, size_t __n,
       ^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:74:8: note: previous definition is here
__NTH (vsnprintf (char *__restrict __s, size_t __n,
       ^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:114:1: error: redefinition of a 'extern inline'
      function 'vprintf' is not supported in C++
vprintf (const char *__restrict __fmt, _G_va_list __ap)
^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:114:1: note: previous definition is here
vprintf (const char *__restrict __fmt, _G_va_list __ap)
^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:124:1: error: redefinition of a 'extern inline'
      function 'vfprintf' is not supported in C++
vfprintf (FILE *__restrict __stream,
^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:124:1: note: previous definition is here
vfprintf (FILE *__restrict __stream,
^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:150:1: error: redefinition of a 'extern inline'
      function 'vdprintf' is not supported in C++
vdprintf (int __fd, const char *__restrict __fmt, _G_va_list __ap)
^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:150:1: note: previous definition is here
vdprintf (int __fd, const char *__restrict __fmt, _G_va_list __ap)
^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:207:8: error: redefinition of a 'extern inline'
      function 'vasprintf' is not supported in C++
__NTH (vasprintf (char **__restrict __ptr, const char *__restrict __fmt,
       ^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:207:8: note: previous definition is here
__NTH (vasprintf (char **__restrict __ptr, const char *__restrict __fmt,
       ^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:214:8: error: redefinition of a 'extern inline'
      function 'obstack_vprintf' is not supported in C++
__NTH (obstack_vprintf (struct obstack *__restrict __obstack,
       ^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:214:8: note: previous definition is here
__NTH (obstack_vprintf (struct obstack *__restrict __obstack,
       ^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:232:1: error: redefinition of a 'extern inline'
      function 'gets' is not supported in C++
gets (char *__str)
^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:232:1: note: previous definition is here
gets (char *__str)
^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:252:1: error: redefinition of a 'extern inline'
      function 'fgets' is not supported in C++
fgets (char *__restrict __s, int __n, FILE *__restrict __stream)
^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:252:1: note: previous definition is here
fgets (char *__restrict __s, int __n, FILE *__restrict __stream)
^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:281:1: error: redefinition of a 'extern inline'
      function 'fread' is not supported in C++
fread (void *__restrict __ptr, size_t __size, size_t __n,
^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:281:1: note: previous definition is here
fread (void *__restrict __ptr, size_t __size, size_t __n,
^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:310:1: error: redefinition of a 'extern inline'
      function 'fgets_unlocked' is not supported in C++
fgets_unlocked (char *__restrict __s, int __n, FILE *__restrict __stream)
^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:310:1: note: previous definition is here
fgets_unlocked (char *__restrict __s, int __n, FILE *__restrict __stream)
^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:342:1: error: redefinition of a 'extern inline'
      function 'fread_unlocked' is not supported in C++
fread_unlocked (void *__restrict __ptr, size_t __size, size_t __n,
^
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:342:1: note: previous definition is here
fread_unlocked (void *__restrict __ptr, size_t __size, size_t __n,
^
In file included from test.h:11:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:360:7: warning: use of logical '&&' with constant
      operand [-Wconstant-logical-operand]
      && __builtin_constant_p (__n)
      ^  ~~~~~~~~~~~~~~~~~~~~~~~~~~
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:360:7: note: use '&' for a bitwise operation
      && __builtin_constant_p (__n)
      ^~
      &
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/stdio2.h:360:7: note: remove constant to silence this warning
      && __builtin_constant_p (__n)
~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from test.h:13:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/wchar.h:325:47: warning: comparison of unsigned expression >= 0 is
      always true [-Wtautological-compare]
{ return (__builtin_constant_p (__wc) && __wc >= L'\0' && __wc <= L'\x7f'
                                         ~~~~ ^  ~~~~~
In file included from test.h:70:
In file included from /nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/math.h:711:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/bits/mathinline.h:152:64: warning: use of GNU old-style field
      designator extension [-Wgnu-designator]
  __extension__ union { long double __l; int __i[3]; } __u = { __l: __x };
                                                               ^~~~
                                                               .__l =
4 warnings and 12 errors generated.

If I edit the command manually aka remove the -c -x c++ --castxml-cc-gnu  it seems to work better :
/nix/store/bgsr6clnq2ivppapayqdbzklkmqbd75b-CastXML-20171003/bin/castxml  -nostdinc -I/nix/store/c30dlkmiyrjxxjv6nv63igjkzcj1fzxi-gcc-6.4.0/lib/gcc/x86_64-unknown-linux-gnu/6.4.0/include -I/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include   -I"." -I"/nix/store/c30dlkmiyrjxxjv6nv63igjkzcj1fzxi-gcc-6.4.0/lib/gcc/x86_64-unknown-linux-gnu/6.4.0/include"   --castxml-cc-gnu /home/teto/.nix-profile/bin/clang++ --castxml-output=1 -o /run/user/1000/tmp6d6aac0v.xml test.h
/nix/store/bgsr6clnq2ivppapayqdbzklkmqbd75b-CastXML-20171003/bin/castxml  -nostdinc -I/nix/store/c30dlkmiyrjxxjv6nv63igjkzcj1fzxi-gcc-6.4.0/lib/gcc/x86_64-unknown-linux-gnu/6.4.0/include -I/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include   -I"." -I"/nix/store/c30dlkmiyrjxxjv6nv63igjkzcj1fzxi-gcc-6.4.0/lib/gcc/x86_64-unknown-linux-gnu/6.4.0/include"    /home/teto/.nix-profile/bin/clang++ --castxml-output=1 -o /run/user/1000/tmp6d6aac0v.xml test.h
warning: /home/teto/.nix-profile/bin/clang++: 'linker' input unused [-Wunused-command-line-argument]
In file included from test.h:10:
/nix/store/mqalq0v2laqblw00dp7pwwckj2ra6jyh-glibc-2.26-75-dev/include/setjmp.h:54:12: warning: declaration of built-in function
      '__sigsetjmp' requires inclusion of the header <setjmp.h> [-Wbuiltin-requires-header]
extern int __sigsetjmp (struct __jmp_buf_tag __env[1], int __savemask) __THROWNL;
           ^
1 warning generated.

Looking at the code, the  --castxml-cc-gnu seems always added on linux so I wonder if there is a way around.

Hi. I’ll need to have a closer look to this.
One thing is that I would like to keep the cast mal command line setup as automatic as possible, so that a user does not have to fiddle too much with flags for castxml. This has always been like this in pygccxml, so I would like to keep that ease of use.
I thought that the —castxml-cc-gnu was needed for Linux. If I remember well it tells castxml that it will work with gcc. But I am unsure now. Maybe you could trace down what that flag does exactly in castxml.
Also, you may need to add a c++11 flag for gcc6, but I think it is not mandatory (but may help here)


apply setting from test kafka found in other projects

fixed typo aerosike -> aerospike

Codecov Report

Merging #31 into develop will increase coverage by 0.14%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##             develop      #31      +/-   ##
=============================================
+ Coverage      82.28%   82.43%   +0.14%
- Complexity       215      218       +3
=============================================
  Files             60       60
  Lines            734      740       +6
  Branches          11       11
=============================================
+ Hits             604      610       +6
  Misses           123      123
  Partials           7        7

Impacted Files
Coverage Δ
Complexity Δ

...kafka/properties/KafkaConfigurationProperties.java
93.75% <100%> (+1.44%)
14 <3> (+3)
:arrow_up:

...spike/EmbeddedAerospikeBootstrapConfiguration.java
100% <100%> (ø)
6 <1> (ø)
:arrow_down:

...fka/configuration/KafkaContainerConfiguration.java
100% <100%> (ø)
7 <0> (ø)
:arrow_down:

...aytika/test/aerospike/AerospikeTestOperations.java
77.77% <100%> (ø)
11 <2> (ø)
:arrow_down:

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 7072b7a...2e75ff5. Read the comment docs.