Add atmega164pa support

This requires a bump of the avr-device dependency, which is not included here. Also specifically depends on https://github.com/Rahix/avr-device/pull/139

Commit 1a0040dc07d37054ccaa93d43a9d2db5f46da3b2 bumped avr-device so now the ATmega164PA should be available.

Commit 1a0040d bumped avr-device so now the ATmega164PA should be available.

Thanks Rahix! I've fixed the first commit of this series to use the changed definition of avr_hal_generic::impl_port_traditional!, and I re-ran avr-specs/sync-from-upstream.py atmega164pa and fixup'd the second commit of the series.
I'd say this is now ready for review and, if you have no comments, to be merged.

Hi @tronje, I'll take this opportunity to ask about avr_hal_generic::impl_port_traditional!, since you had to adapt your PR to it. What do you think about the re-design, and about applying the same ideas to the other modules? I ask because I plan to continue refactoring (#457 is up as we speak), and having feedback is always good.

I like it, it's a lot more concise than before.  Based on existing usage of the macro, it was easy to figure out what I needed to do. Maybe a short explanatory doc comment with an example would be nice to have, anyway.
I should point out that I may not be the best person to quiz about this. We just needed support for the atmega164pa, I don't have particularly good knowledge of avr-hal.
In any case, thanks for your work :slightly_smiling_face:

@Rahix friendly ping :slightly_smiling_face:
I've rebased this onto the latest main branch.

Thanks for the ping and sorry for my slow responses...

No worries!

Code looks good, thanks a lot!

Thanks :slightly_smiling_face:

I do see your EEPROM fix. I think we should merge it to ensure the EEPROM code is not completely wrong but I'd like to understand why the current implementation is broken... Do you have any insight into this?

Unfortunately, not really. All that I do know, I know from #406.

Thanks @Rahix! Really appreciate your work :slightly_smiling_face:


feature: yarn install (through a flag)

This PR adds support for yarn in the application. 🎉
User can install & use yarn by adding a flag --yarn when he initializes a project using preact create my_app --yarn.
Added install-dependencies.js since I want to keep create.js clean and simple.
For now cancelling the tests since they will fail for sure 😛
Log - https://gist.github.com/reznord/8b13c890c68e9e45454de2d7fe7c7395
Tests are the only thing that are failing now, else we are good to go with yarn 😎
@rkostrzewski @developit please help with the tests !!

Closing #31 in favour of this

Here is the latest log from the failed tests - https://gist.github.com/reznord/f69ddcf6f0caad99bb9d83ce61381ca8
Progress: Tests are not failing that worse 😛


nixos/nullmailer: allow users in the nullmailer group to send mails

In combination with https://github.com/NixOS/nixpkgs/pull/231673 this allows hardened services to use nullmailer's sendmail.
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

However, I don't understand why exactly is it needed. #231673 doesn't seem to directly require this change. Do you mean that hardened services can share the group with nullmailer and thus talk to it?

yes but because sendmail is always a setuid binary it can't be executed at all under hardened services.


ENUM file created

backend is clean coded now

https://github.com/kalviumcommunity/AppInfo/pull/1
`Feedback: on this PR
commit messages should be well written -- not "new".
This is great resource: https://www.freecodecamp.org/news/how-to-write-better-git-commit-messages/
`
Multiple times you got the same feedback to improve the commit messages.
Hope you will improve on it now.


User never signaled connection

Unknown reason, dedicated server. First time joining create this error and stops the player from doing anything except being in a weird state of spectating. Until map restart, changelevel or just round restart.

Dedicated server, no other addons.
Edit: Happens every time after restarting the dedicated server.
Edit2: Seems to also happen randomly but it did on d3_c17_04

Can you use "lambda_log all" and post a clean log when this is happening. I'm trying to reproduce this without success.

https://dl.dropboxusercontent.com/u/17687819/random shit/console.log

Thanks, that certainly helps. Seems like you are timing out for no reason handled by the gamemode. I will look into it.

Fixed in next upcoming update


soc: rt11xx: usb2: Typo in clock initialization of usb2

a typo in usb2 clock initialization which impact the function of usb2.

if it is a bug, then you will have to link a bug report to merge to 4.0.

if it is a bug, then you will have to link a bug report to merge to 4.0.

it is a bug reported by someone but no bug report, how to do?

if it is a bug, then you will have to link a bug report to merge to 4.0.

it is a bug reported by someone but no bug report, how to do?

you just need to make a github issue on this repo with the bug report template

bug report created: #81027


Feedback from Exec Meeting

HI All,
Alex demoed the Grow and WtC apps in the CYP IAPT exec meeting yesterday and collected feedback about the products. The feedback received for the 'WtC' is outlined below:

Loved the concept of popping the balloons, but suggest this is inverted so that young people pop the non-applicable balloons, leaving the balloons that best describe them.
'Select Activities that you like doing' section: suggestion that this wording is too sophisticated for target user. Can the activities either be changed to something simpler like 'playing' 'sleeping' etc, or can there be the the option to write your own activities.
-Group felt that 'Welcome to CAMHS' is a misleading title for what is actually included in the app. Suggestions to change title to something like 'Things I might get asked at CAMHS', so that it acts as a discussion prompt for parents to bring up the concept of CAMHS, prepares the child and gives families the opportunity to use the app before their first visit.
Suggest moving the first question 'how many fruit...' to later in the form; this is asking about eating fruit which is often a bone of contention for young people and might put them off completing the form.
OVerall: the app looks great and is appealing, but the language throughout is too sophisticated and would benefit from being adapted to a  younger audience.

Thank you @CharlotteBarrett :)

I am closing this issue as we have incorporated these suggestions where possible in sprint 2.


[Loc] mssql update 9-15-2022

This PR fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
28035

Relevant Lines:
62103

💛  - Coveralls


 The PR also contains some helper functions for measuring and sending test run times to InfluxDB. The results will become visible on Grafana dashboard as soon as the related Jenkins job starts running periodically.
Lastly, the PR introduces a new option: parallelism, which can be used to set the degree of Flink's parallelism.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

 If you remember what is was about, please add it once again.

@lostluck I accidentally overwrote your commit by a force push (I could have created a "fix" commit...) If you remember what is was about, please add it once again.

Nevermind, I've just found it somehow!

I don't think it actually has anything to do with this PR, as it would break if they were actually replaced anywhere. Just odd.

I don't think it actually has anything to do with this PR, as it would break if they were actually replaced anywhere. Just odd.

I know this problem. Every "worker" gets swapped, because one of defined Jenkins credentials has username "worker". So Jenkins thinks there's a credential leak and tries to de-identify console logs.


A way to add a angular-material select in a column?

<mdt-table selectable-rows="true" paginated-rows="{isEnabled: true, rowsPerPageValues: [5,10,20,100]}">
  <mdt-header-row>
    <mdt-column align-rule="left" column-sort="true">Type</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Invoice Number</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Client</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Due Date</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Balance</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Total</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Status</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Action</mdt-column>
  </mdt-header-row>

  <mdt-row
          ng-repeat="invoice in invoices | filter: searchText"
          table-row-id="invoice._id">
    <mdt-cell>{{invoice.type}}</mdt-cell>
    <mdt-cell>{{invoice.invoiceNumber}}</mdt-cell>
    <mdt-cell>{{invoice.client.company.name}}</mdt-cell>
    <mdt-cell>{{invoice.due | date: 'medium'}}</mdt-cell>
    <mdt-cell>{{invoice.balance | currency}}</mdt-cell>
    <mdt-cell>{{invoice.total | currency}}</mdt-cell>
    <mdt-cell>{{invoice.status || "Open"}}</mdt-cell>

    <mdt-cell>
      <md-input-container>
        Select Action
        <md-select ng-model="invoice.action">
          <md-option ng-repeat="action in actions" value="{{action}}">
            {{action}}
          </md-option>
        </md-select>
      </md-input-container>
    </mdt-cell>
  </mdt-row>

</mdt-table>

Is there a way to add a select or dropdown with actions in a column? I'm trying to create some actions to each row to be able to view more details about the invoice in this example or pay the invoice.

Sure you can, just try to get rid of <mdt-row> element first, since it's going to be deprecated.
Use mdt-row-paginator or mdt-row attribute instead.
Then you can use mdt-custom-cell to add any custom elements to your cell.

@iamisti thanks for the quick reply
I was able to get the table working with mdt-row but ended up with another problem
here's the code:
<mdt-table selectable-rows="true" paginated-rows="{isEnabled: true, rowsPerPageValues: [5,10,20,100]}"
           mdt-row="tableData">
  <mdt-header-row>
    <mdt-column align-rule="right" column-sort="true">Invoice Number</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Client</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Due Date</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Balance</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Total</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Status</mdt-column>
    <mdt-column align-rule="right" column-sort="true">Action</mdt-column>
  </mdt-header-row>

  <mdt-custom-cell column-key="action">

      <md-input-container flex-gt-sm>
        Select Action
        <md-select ng-model="invoice.action" md-on-close="doAction(invoice.action, invoice)">
          <md-option ng-repeat="action in actions" value="{{action}}">
            {{action}}
          </md-option>
        </md-select>
      </md-input-container>

  </mdt-custom-cell>

</mdt-table>

and here's the error:

This doesn't happen if I change the md-select into a normal select tag. I will just use this option for now.

I think the issue is similar than #153 , can you please try with the solution of that ticket?

for now I just want a simple solution with a simple select
I did this:
<mdt-custom-cell column-key="action">
  <select class="form-control" ng-model="invoice.action" ng-change="checkChange()">
    <option value="" selected disabled>Select an action</option>
    <option ng-click="checkChange()" value="Receive Payment">Receive Payment</option>
    <option value="View Invoice">View Invoice</option>
    <option value="View History">View History</option>
  </select>
</mdt-custom-cell>

but now, none of the actions are executing, ng-change or ng-click aren't doing anything at all.
I've tried also creating a directive like this:
'use strict';

angular.module('myApp')
.directive('simpleSelect', function() {
  return {
    restrict: 'EA',
    templateUrl: 'client/components/simpleSelect/simple-select.view.ng.html',
    replace: false,
    scope: {
      changeAction: '@',
      modelAction: '@'
    },
    link: function(scope, elem, attrs) {
      scope.property = 'simpleSelect';
    }
  };
});

and html
<select class="form-control" ng-model="modelAction">
  <option value="" selected disabled>Select an action</option>
  <option ng-click="changeAction" value="Receive Payment">Receive Payment</option>
  <option value="View Invoice">View Invoice</option>
  <option value="View History">View History</option>
</select>

and table:
<mdt-custom-cell column-key="action">
  <simple-select modelAction="{{invoice.action}}" changeAction="{{checkChange()}}"></simple-select>
</mdt-custom-cell>

but now what it does is execute the checkChange() function multiple times even when I don't even change the option.

Solution
I was kept checking the examples and notice the clientScope, after adding it like this:
<mdt-custom-cell column-key="action">
  <select class="form-control" ng-model="clientScope.invoice[rowId].action"
          ng-change="clientScope.doAction(clientScope.invoice[rowId].action, clientScope.getInvoiceWithId(rowId))">
    <option value="" selected disabled>Select an action</option>
    <option value="Receive Payment">Receive Payment</option>
    <option value="View Invoice">View Invoice</option>
    <option value="View History">View History</option>
  </select>
</mdt-custom-cell>

It works.

cool! I'll improve the documentation too, because now it's a bit chaotic since the I was just continuously adding new features to it. We need a much clearer documentation.


Please Add these features , I will be highly thankful

--> Please add this Folder Preview Affect in Files UWP,

--> Please add an Option to Apply a (Layout Mode) to a folder and all its subfolders and files.
--> Kindly, try to add Advanced utilities in Properties Tab , just like in Windows File Explorer.

@YHZ-EPIC Please open new issues and upvote existing ones for each item here.


Removed temporary files

src/Custom/ArticleBundle/Entity/Article.php~
src/Custom/MainBundle/Entity/User.php~
src/Custom/PartnerBundle/Entity/Partner.php~

Thanks for contributing.


Add .vscode/ folder to ignored files

It's just a folder where vscode dumps configuration files and other things not needed

Duplicate of #2244


Create convenience command to link Docker socket path to localDocker.socketPath setting

We offer a convenience command for uploading PEM paths (connections.addSSLPemPath) and updating the ssl.pemPaths value, but don't have the same convenience for the localDocker.socketPath setting.

Closed as part of https://github.com/confluentinc/vscode/pull/614


Adding feature, Range Based Lock

Adding feature, Range Based lock to HPX
API:
range_lock rl;
lockId = rl.lock(rangeBegin, rangeEnd);
rl.unlock(lockId);
Pending Task:
Adding tests

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)??(=)InfoPropertyBeforeAfterHPX Commitdcb541576898d370113946ba15fb58c20c8325b29da61de2f3f1673886cbc916056d19a3ac2bc167HPX Datetime2023-05-10T12:07:53+00:002023-11-02T04:22:07+00:00Datetime2023-05-10T14:50:18.616050-05:002023-11-01T23:30:22.792853-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch(=)InfoPropertyBeforeAfterHPX Commitdcb541576898d370113946ba15fb58c20c8325b29da61de2f3f1673886cbc916056d19a3ac2bc167HPX Datetime2023-05-10T12:07:53+00:002023-11-02T04:22:07+00:00Datetime2023-05-10T14:52:35.047119-05:002023-11-01T23:32:35.779661-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)-(=)InfoPropertyBeforeAfterHPX Commitdcb541576898d370113946ba15fb58c20c8325b29da61de2f3f1673886cbc916056d19a3ac2bc167HPX Datetime2023-05-10T12:07:53+00:002023-11-02T04:22:07+00:00Datetime2023-05-10T14:52:52.237641-05:002023-11-01T23:32:52.616083-05:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduClusternamerostamrostamCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1EnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

More comprehensive tests on the way @hkaiser. Will add them soon.

@hkaiser do we have a concurrent hash map like the one by boost or the one by folly?

@hkaiser do we have a concurrent hash map like the one by boost or the one by folly?

No we don't have something like that.

@Johan511 I know that currently the reporting of the build logs for the HPX CIs is broken (we're working on fixing this). For this reason, here is the error message that makes the builders fail:
/.../hpx/libs/core/synchronization/include/hpx/synchronization/range_mutex.hpp:71:25: error: no member named 'get' in 'hpx::synchronization::detail::range_mutex<hpx::detail::spinlock<true>, std::lock_guard>'

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)??-InfoPropertyBeforeAfterHPX Commitdcb541576898d370113946ba15fb58c20c8325b26834baab450742da0b0694281ff770008ca9ec91HPX Datetime2023-05-10T12:07:53+00:002024-02-07T09:11:33+00:00EnvfileHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamDatetime2023-05-10T14:50:18.616050-05:002024-02-07T03:20:02.039903-06:00ComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch=InfoPropertyBeforeAfterHPX Commitdcb541576898d370113946ba15fb58c20c8325b26834baab450742da0b0694281ff770008ca9ec91HPX Datetime2023-05-10T12:07:53+00:002024-02-07T09:11:33+00:00EnvfileHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamDatetime2023-05-10T14:52:35.047119-05:002024-02-07T03:22:15.846511-06:00ComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale+(=)=Stream Benchmark - Triad(=)=(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPX Commitdcb541576898d370113946ba15fb58c20c8325b26834baab450742da0b0694281ff770008ca9ec91HPX Datetime2023-05-10T12:07:53+00:002024-02-07T09:11:33+00:00EnvfileHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamDatetime2023-05-10T14:52:52.237641-05:002024-02-07T03:22:32.733787-06:00Explanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

I have not looked at the implementation (I will examine it later), but I'm curious as to the use case for the range-lock. Is this work inspired by the GSoC project I proposed a few years ago (with an astrophysics particle code in mind), or do you have another use case that requires it? (or perhaps it was "just for fun" as an interesting project to try?)

Hi @biddisco, this is a fun piece of work inspired by the GSoC project you had proposed. I didn't have an use-case in mind, I had tested out it's performance based on the amount of time it took to execute the test. It'd be great if I could test the impact of the code on a more real life scenario.

@hkaiser can you have a look at the CI? I am not able to view the logs on the jenkins CI.
Also is there any reference I could use to write documentation? Maybe some sort of specialized mutex somewhere in HPX.

@hkaiser can you have a look at the CI? I am not able to view the logs on the jenkins CI. Also is there any reference I could use to write documentation? Maybe some sort of specialized mutex somewhere in HPX.

Sory for the CI issues. We're currently working on a solution for this problem.


cluster: deactivate it

@hsanjuan It went and restarted the cluster containers so I deactivated it. Wanna delete some code? :):)

@lgierth sure, will do!


Tk multitenant

Pull request description
This draft introduces an option to deploy Testkube in multiple namespace in the the same k8s cluster. It deploys all TK components in Release namespace, except for testkube-operator which is by default deployed to testkube-system namespace, unless specified otherwise.
A few points:

If a user chooses another namespace for the testkube-operator, they need to provide it in values.yaml file (default is testkube-system)
If a user installs TK in another namespace, they need to disable testkube-operator: --set testkube-operator.enabled=false via CLI or in the values.yaml.

Important!
Testkube Operator creates ClusterRoles which cannot be changed. The Operator is deployed once with the first chart installation of Testkube.
Thus if you uninstall the first release of TK, it will uninstall TK Operator as well so it needs to be running.
Example of installation.
Fresh TK install:
helm install testkube testkube/testkube -n testkube --create-namespace --debug
OR
helm upgrade testkube testkube/testkube -n testkube --create-namespace --debug
TK install in another namespace in the same cluster:
helm install testkube testkube/testkube -n your-namespace --create-namespace --debug  --set testkube-operator.enabled=false
Checklist (choose whats happened)

[ ] breaking change! (describe)
[x] tested locally
[x] tested on cluster
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

Breaking changes

Changes
If TK is already running in your cluster, it will re-create the Operator in another namespace and replace Testkube API's ClusterRoles with Roles
Fixes

Things checked, and working:

Single-namespace installation (default), cluster-wide permissions - being able to watch any namespace (backwards compatibility)
Multi-namespace installation (testkube-api.multinamespace.enabled=true)
Triggers in the installation namespace
Triggers in additionalNamespaces
Upgrade of existing installation - after upgrade it's not possible to watch any namespace than the installation namespace

Note:
It's NOT possible to set additionalNamespaces to namespace where another testkube instance is already installed. But, that is the only limitation I found

Option to add additionalNamespaces is available now..


import rocksdb issuse:  undefined symbol: _ZTIN7rocksdb10ComparatorE

1.Collecting python-rocksdb
Requirement already satisfied: setuptools in /home/guosheng/.local/lib/python2.7/site-packages (from python-rocksdb)
Installing collected packages: python-rocksdb
Successfully installed python-rocksdb-0.6.7
2.
guosheng@guosheng:~/code/db_rock/rocksdb/pyrocks_test$ python
Python 2.7.12 (default, Nov 19 2016, 06:48:10)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import rocksdb
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/dist-packages/rocksdb/init.py", line 1, in
from ._rocksdb import *
ImportError: /usr/local/lib/python2.7/dist-packages/rocksdb/_rocksdb.so: undefined symbol: _ZTIN7rocksdb10ComparatorE

How you built rocksdb?

your build ways : (the pyrocks_test/ has finished)
mkdir build
cd build
guosheng@guosheng:~/code/rocksdb/rocksdb/build$ ### cmake ..
-- JNI library is disabled
-- Configuring done
-- Generating done
-- Build files have been written to: /home/guosheng/code/rocksdb/rocksdb/build
guosheng@guosheng:~/code/rocksdb/rocksdb/build$ make
[  1%] Built target testutillib
Scanning dependencies of target build_version
[  1%] Building CXX object CMakeFiles/build_version.dir/build_version.cc.o
[  1%] Built target build_version
[  2%] Linking CXX shared library librocksdb.so
[ 31%] Built target rocksdb-shared
[ 31%] Linking CXX executable c_test
[ 31%] Built target c_test
[ 31%] Built target gtest
[ 31%] Built target testharness
[ 31%] Linking CXX executable ttl_test
[ 31%] Built target ttl_test
[ 31%] Linking CXX executable write_prepared_transaction_test
[ 31%] Built target write_prepared_transaction_test
[ 31%] Linking CXX executable transaction_test
[ 31%] Built target transaction_test
[ 31%] Linking CXX executable compact_on_deletion_collector_test
[ 32%] Built target compact_on_deletion_collector_test
[ 33%] Linking CXX executable redis_lists_test
[ 33%] Built target redis_lists_test
[ 33%] Linking CXX executable option_change_migration_test
[ 33%] Built target option_change_migration_test
[ 33%] Linking CXX executable object_registry_test
[ 33%] Built target object_registry_test
[ 33%] Linking CXX executable memory_test
[ 33%] Built target memory_test
[ 33%] Linking CXX executable geodb_test
[ 33%] Built target geodb_test
[ 33%] Linking CXX executable json_document_test
[ 33%] Built target json_document_test
[ 33%] Linking CXX executable document_db_test
[ 33%] Built target document_db_test
[ 33%] Linking CXX executable date_tiered_test
[ 34%] Built target date_tiered_test
[ 34%] Linking CXX executable column_aware_encoding_test
[ 34%] Built target column_aware_encoding_test
[ 34%] Linking CXX executable checkpoint_test
[ 34%] Built target checkpoint_test
[ 34%] Linking CXX executable cassandra_serialize_test
[ 35%] Built target cassandra_serialize_test
[ 35%] Linking CXX executable cassandra_row_merge_test
[ 35%] Built target cassandra_row_merge_test
[ 35%] Linking CXX executable cassandra_functional_test
[ 35%] Built target cassandra_functional_test
[ 36%] Linking CXX executable backupable_db_test
[ 36%] Built target backupable_db_test
[ 36%] Linking CXX executable timer_queue_test
[ 36%] Built target timer_queue_test
[ 36%] Linking CXX executable slice_transform_test
[ 36%] Built target slice_transform_test
[ 36%] Linking CXX executable heap_test
[ 36%] Built target heap_test
[ 36%] Linking CXX executable hash_test
[ 36%] Built target hash_test
[ 36%] Linking CXX executable blob_db_test
[ 36%] Built target blob_db_test
[ 36%] Linking CXX executable filelock_test
[ 36%] Built target filelock_test
[ 37%] Linking CXX executable file_reader_writer_test
[ 37%] Built target file_reader_writer_test
[ 37%] Linking CXX executable event_logger_test
[ 37%] Built target event_logger_test
[ 37%] Linking CXX executable options_util_test
[ 37%] Built target options_util_test
[ 38%] Linking CXX executable crc32c_test
[ 38%] Built target crc32c_test
[ 38%] Linking CXX executable coding_test
[ 38%] Built target coding_test
[ 38%] Linking CXX executable spatial_db_test
[ 38%] Built target spatial_db_test
[ 38%] Linking CXX executable auto_roll_logger_test
[ 38%] Built target auto_roll_logger_test
[ 38%] Linking CXX executable sst_dump_test
[ 39%] Built target sst_dump_test
[ 39%] Linking CXX executable db_test2
[ 39%] Built target db_test2
[ 39%] Linking CXX executable merge_helper_test
[ 39%] Built target merge_helper_test
[ 39%] Linking CXX executable db_test
[ 39%] Built target db_test
[ 39%] Linking CXX executable compact_files_test
[ 39%] Built target compact_files_test
[ 39%] Linking CXX executable prefix_test
[ 39%] Built target prefix_test
[ 40%] Linking CXX executable db_sst_test
[ 40%] Built target db_sst_test
[ 40%] Linking CXX executable db_bloom_filter_test
[ 40%] Built target db_bloom_filter_test
[ 40%] Linking CXX executable thread_list_test
[ 40%] Built target thread_list_test
[ 41%] Linking CXX executable log_test
[ 41%] Built target log_test
[ 41%] Linking CXX executable db_log_iter_test
[ 41%] Built target db_log_iter_test
[ 41%] Linking CXX executable write_batch_with_index_test
[ 41%] Built target write_batch_with_index_test
[ 41%] Linking CXX executable arena_test
[ 41%] Built target arena_test
[ 41%] Linking CXX executable version_set_test
[ 41%] Built target version_set_test
[ 41%] Linking CXX executable db_iter_test
[ 42%] Built target db_iter_test
[ 42%] Linking CXX executable db_inplace_update_test
[ 42%] Built target db_inplace_update_test
[ 42%] Linking CXX executable db_flush_test
[ 42%] Built target db_flush_test
[ 42%] Linking CXX executable db_dynamic_level_test
[ 43%] Built target db_dynamic_level_test
[ 43%] Linking CXX executable env_basic_test
[ 44%] Built target env_basic_test
[ 45%] Linking CXX executable db_memtable_test
[ 45%] Built target db_memtable_test
[ 45%] Linking CXX executable db_compaction_filter_test
[ 45%] Built target db_compaction_filter_test
[ 45%] Linking CXX executable cache_test
[ 46%] Built target cache_test
[ 46%] Linking CXX executable stringappend_test
[ 46%] Built target stringappend_test
[ 46%] Linking CXX executable autovector_test
[ 46%] Built target autovector_test
[ 46%] Linking CXX executable dbformat_test
[ 46%] Built target dbformat_test
[ 46%] Linking CXX executable dynamic_bloom_test
[ 46%] Built target dynamic_bloom_test
[ 47%] Linking CXX executable hash_table_bench
[ 47%] Built target hash_table_bench
[ 47%] Linking CXX static library librocksdb.a
[ 76%] Built target rocksdb
[ 76%] Linking CXX executable plain_table_db_test
[ 77%] Built target plain_table_db_test
[ 77%] Linking CXX executable table_reader_bench
[ 77%] Built target table_reader_bench
[ 77%] Linking CXX executable thread_local_test
[ 78%] Built target thread_local_test
[ 78%] Linking CXX executable compaction_iterator_test
[ 78%] Built target compaction_iterator_test
[ 78%] Linking CXX executable db_table_properties_test
[ 78%] Built target db_table_properties_test
[ 78%] Linking CXX executable compaction_job_stats_test
[ 78%] Built target compaction_job_stats_test
[ 78%] Linking CXX executable cache_bench
[ 78%] Built target cache_bench
[ 79%] Linking CXX executable table_properties_collector_test
[ 79%] Built target table_properties_collector_test
[ 80%] Linking CXX executable db_block_cache_test
[ 80%] Built target db_block_cache_test
[ 80%] Linking CXX executable options_settable_test
[ 80%] Built target options_settable_test
[ 81%] Linking CXX executable column_aware_encoding_exp
[ 81%] Built target column_aware_encoding_exp
[ 81%] Linking CXX executable persistent_cache_test
[ 81%] Built target persistent_cache_test
[ 81%] Linking CXX executable db_basic_test
[ 81%] Built target db_basic_test
[ 81%] Linking CXX executable db_merge_operator_test
[ 81%] Built target db_merge_operator_test
[ 81%] Linking CXX executable db_universal_compaction_test
[ 81%] Built target db_universal_compaction_test
[ 82%] Linking CXX executable delete_scheduler_test
[ 82%] Built target delete_scheduler_test
[ 82%] Linking CXX executable db_range_del_test
[ 83%] Built target db_range_del_test
[ 83%] Linking CXX executable db_properties_test
[ 83%] Built target db_properties_test
[ 83%] Linking CXX executable memtablerep_bench
[ 83%] Built target memtablerep_bench
[ 83%] Linking CXX executable corruption_test
[ 83%] Built target corruption_test
[ 83%] Linking CXX executable cassandra_format_test
[ 83%] Built target cassandra_format_test
[ 83%] Linking CXX executable options_file_test
[ 83%] Built target options_file_test
[ 83%] Linking CXX executable db_options_test
[ 83%] Built target db_options_test
[ 83%] Linking CXX executable ldb_cmd_test
[ 83%] Built target ldb_cmd_test
[ 83%] Linking CXX executable column_family_test
[ 83%] Built target column_family_test
[ 83%] Linking CXX executable rate_limiter_test
[ 83%] Built target rate_limiter_test
[ 83%] Linking CXX executable lru_cache_test
[ 83%] Built target lru_cache_test
[ 83%] Linking CXX executable cuckoo_table_db_test
[ 83%] Built target cuckoo_table_db_test
[ 84%] Linking CXX executable db_tailing_iter_test
[ 84%] Built target db_tailing_iter_test
[ 84%] Linking CXX executable bloom_test
[ 85%] Built target bloom_test
[ 85%] Linking CXX executable db_wal_test
[ 86%] Built target db_wal_test
[ 86%] Linking CXX executable comparator_db_test
[ 86%] Built target comparator_db_test
[ 86%] Linking CXX executable db_write_test
[ 86%] Built target db_write_test
[ 86%] Linking CXX executable db_bench
[ 86%] Built target db_bench
[ 86%] Linking CXX executable compaction_picker_test
[ 86%] Built target compaction_picker_test
[ 86%] Linking CXX executable deletefile_test
[ 86%] Built target deletefile_test
[ 86%] Linking CXX executable external_sst_file_basic_test
[ 86%] Built target external_sst_file_basic_test
[ 86%] Linking CXX executable fault_injection_test
[ 86%] Built target fault_injection_test
[ 86%] Linking CXX executable file_indexer_test
[ 86%] Built target file_indexer_test
[ 86%] Linking CXX executable hash_table_test
[ 86%] Built target hash_table_test
[ 86%] Linking CXX executable filename_test
[ 86%] Built target filename_test
[ 86%] Linking CXX executable external_sst_file_test
[ 87%] Built target external_sst_file_test
[ 88%] Linking CXX executable wal_manager_test
[ 88%] Built target wal_manager_test
[ 88%] Linking CXX executable flush_job_test
[ 88%] Built target flush_job_test
[ 89%] Linking CXX executable compaction_job_test
[ 89%] Built target compaction_job_test
[ 89%] Linking CXX executable db_io_failure_test
[ 89%] Built target db_io_failure_test
[ 89%] Linking CXX executable manual_compaction_test
[ 89%] Built target manual_compaction_test
[ 90%] Linking CXX executable memtable_list_test
[ 90%] Built target memtable_list_test
[ 90%] Linking CXX executable perf_context_test
[ 90%] Built target perf_context_test
[ 90%] Linking CXX executable table_test
[ 90%] Built target table_test
[ 90%] Linking CXX executable repair_test
[ 90%] Built target repair_test
[ 90%] Linking CXX executable version_builder_test
[ 91%] Built target version_builder_test
[ 91%] Linking CXX executable version_edit_test
[ 91%] Built target version_edit_test
[ 91%] Linking CXX executable rocks_lua_test
[ 91%] Built target rocks_lua_test
[ 91%] Linking CXX executable write_batch_test
[ 91%] Built target write_batch_test
[ 91%] Linking CXX executable write_callback_test
[ 92%] Built target write_callback_test
[ 93%] Linking CXX executable optimistic_transaction_test
[ 93%] Built target optimistic_transaction_test
[ 93%] Linking CXX executable env_test
[ 93%] Built target env_test
[ 93%] Linking CXX executable mock_env_test
[ 93%] Built target mock_env_test
[ 93%] Linking CXX executable db_iterator_test
[ 93%] Built target db_iterator_test
[ 93%] Linking CXX executable inlineskiplist_test
[ 93%] Built target inlineskiplist_test
[ 93%] Linking CXX executable skiplist_test
[ 94%] Built target skiplist_test
[ 94%] Linking CXX executable db_compaction_test
[ 94%] Built target db_compaction_test
[ 94%] Linking CXX executable listener_test
[ 94%] Built target listener_test
[ 94%] Linking CXX executable write_buffer_manager_test
[ 94%] Built target write_buffer_manager_test
[ 95%] Linking CXX executable histogram_test
[ 95%] Built target histogram_test
[ 95%] Linking CXX executable cuckoo_table_builder_test
[ 95%] Built target cuckoo_table_builder_test
[ 95%] Linking CXX executable sim_cache_test
[ 95%] Built target sim_cache_test
[ 95%] Linking CXX executable db_statistics_test
[ 95%] Built target db_statistics_test
[ 95%] Linking CXX executable iostats_context_test
[ 95%] Built target iostats_context_test
[ 95%] Linking CXX executable reduce_levels_test
[ 95%] Built target reduce_levels_test
[ 95%] Linking CXX executable statistics_test
[ 95%] Built target statistics_test
[ 95%] Linking CXX executable block_test
[ 95%] Built target block_test
[ 95%] Linking CXX executable options_test
[ 96%] Built target options_test
[ 96%] Linking CXX executable merger_test
[ 97%] Built target merger_test
[ 97%] Linking CXX executable block_based_filter_block_test
[ 97%] Built target block_based_filter_block_test
[ 97%] Linking CXX executable write_controller_test
[ 97%] Built target write_controller_test
[ 97%] Linking CXX executable cuckoo_table_reader_test
[ 97%] Built target cuckoo_table_reader_test
[ 97%] Linking CXX executable merge_test
[ 97%] Built target merge_test
[ 97%] Linking CXX executable full_filter_block_test
[ 98%] Built target full_filter_block_test
[ 99%] Linking CXX executable write_stress
[ 99%] Built target write_stress
[ 99%] Linking CXX executable db_stress
[ 99%] Built target db_stress
[ 99%] Linking CXX executable sst_dump
[ 99%] Built target sst_dump
[ 99%] Linking CXX executable ldb
[100%] Built target ldb
[100%] Linking CXX executable db_repl_stress
[100%] Built target db_repl_stress
[100%] Linking CXX executable db_sanity_test
[100%] Built target db_sanity_test
[100%] Linking CXX executable rocksdb_undump
[100%] Built target rocksdb_undump
[100%] Linking CXX executable rocksdb_dump
[100%] Built target rocksdb_dump
guosheng@guosheng:~/code/rocksdb/rocksdb/build$ export CPLUS_INCLUDE_PATH=${CPLUS_INCLUDE_PATH}:pwd/../include
guosheng@guosheng:~/code/rocksdb/rocksdb/build$ export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:pwd
guosheng@guosheng:~/code/rocksdb/rocksdb/build$ export LIBRARY_PATH=${LIBRARY_PATH}:pwd
guosheng@guosheng:~/code/rocksdb/rocksdb/build$ source ~/.bashrc
guosheng@guosheng:~/code/rocksdb/rocksdb/build$ cd ../
guosheng@guosheng:~/code/rocksdb/rocksdb$ cd pyrocks_test/
guosheng@guosheng:~/code/rocksdb/rocksdb/pyrocks_test$ python
Python 2.7.12 (default, Nov 19 2016, 06:48:10)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.

import rocksdb
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/dist-packages/rocksdb/init.py", line 1, in
from ._rocksdb import *
ImportError: /usr/local/lib/python2.7/dist-packages/rocksdb/_rocksdb.so: undefined symbol: _ZTIN7rocksdb10ComparatorE

Did you use pyenv or other virtualenv?

i have  installed  python3;
in addition； because i import the rrocksdb  failed,so i try  to  many ways,and install the python-rocksdb many times in different  dir.

Facing the same issue.
Working on python 3.6
Steps followed are:
apt-get install build-essential libsnappy-dev zlib1g-dev libbz2-dev libgflags-dev
sudo apt-get install build-essential libsnappy-dev zlib1g-dev libbz2-dev libgflags-dev
git clone https://github.com/facebook/rocksdb.git
cd rocksdb/
mkdir build &&  cd build
cmake ..
make
cd ..
export CPLUS_INCLUDE_PATH=${CPLUS_INCLUDE_PATH}:include
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:build
export LIBRARY_PATH=${LIBRARY_PATH}:build
pip install cython
pip install python-rocksdb
python3.6 -c 'import rocksdb'
Output:
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.6/dist-packages/rocksdb/init.py", line 1, in
from ._rocksdb import *
ImportError: /usr/local/lib/python3.6/dist-packages/rocksdb/_rocksdb.cpython-36m-x86_64-linux-gnu.so: undefined symbol: _ZTIN7rocksdb10ComparatorE
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/init.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in
import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in
from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in
import apt
File "/usr/lib/python3/dist-packages/apt/init.py", line 23, in
import apt_pkg
ModuleNotFoundError: No module named 'apt_pkg'
Original exception was:
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.6/dist-packages/rocksdb/init.py", line 1, in
from ._rocksdb import *
ImportError: /usr/local/lib/python3.6/dist-packages/rocksdb/_rocksdb.cpython-36m-x86_64-linux-gnu.so: undefined symbol: _ZTIN7rocksdb10ComparatorE

Hi guys,
I use pyenv (https://github.com/pyenv/pyenv) to manage the python environment.
And it works without exceptions.
Can you try pyenv to install  python-rocksdb?

the document for installation is updated.
thanks @rimpybharot .
@azhuoinfogs
do you activate python virtual environment?

Yes I used virtualenv for python-rocksdb.

same problem, was able to get it working by doing make install from the rocksdb build directory.
These are the steps I used:
ubuntu:~/src/rocksdb$ mkdir build && cd build
... clipped
ubuntu:~/src/rocksdb/build$ cmake ..
... clipped
ubuntu:~/src/rocksdb/build$ sudo make install-shared INSTALL_PATH=/usr
make: *** No rule to make target 'install-shared'.  Stop.
ubuntu:~/src/rocksdb/build$ cd ..
ubuntu:~/src/rocksdb$ sudo make install-shared INSTALL_PATH=/usr
... This seemed to work, but python-rocksdb still doesn't work ...
ubuntu:~/src/rocksdb$ cd build
ubuntu:~/src/rocksdb/build$ sudo make install
... clipped

After the last step I reinstalled python-rocksdb to be safe and everything works.

thx @schmidtc
i work on python2.7
after your suggest it's work nomal

thx @schmidtc
i work on python2.7
after your suggest it's work nomal

This worked for me:
sudo apt-get install build-essential libsnappy-dev zlib1g-dev libbz2-dev libgflags-dev
git clone https://github.com/facebook/rocksdb.git
cd rocksdb
mkdir build && cd build
cmake ..
make
sudo make install INSTALL_PATH=/usr

Install / reinstall python-rocksdb
sudo pip3.6 uninstall python-rocksdb
sudo pip3.6 install python-rocksdb

This is the same problem as #17.
rocksdb in release mode adds -fno-rtti unless you specify USE_RTTI=1 while building, accidentally build in debug mode, or use the CMake build (which is missing this optimization).
But python-rocksdb doesn't add this flag, so things are incompatible.


runtest.py is not in distribution package

Hi, I think in Pypi the distribution package doesn't contain runtest.py. This causes running test on distribution package failed. Is there any reason tests are excluded from distribution?

No, but I don't see the need personally. If you'd like to send a PR, I'd accept it.


Link to the FAQ entry "How to behave if I am partially or completely vaccinated, but receive a red warning in the Corona-Warn-App?" on the increased risk detail screen

Current Implementation
The increased risk detail screen doesn't mention what to do if one is already vaccinated and receives this increased risk encounter.
Suggested Enhancement
Add a new bullet point to the guidelines which are shown when the app has detected an increased risk.
The text of the bullet point should be:
"If you are vaccinated against COVID-19 be alert for typical COVID-19 symptoms. Even vaccinated people can show symptoms in breakthrough cases. If you notice any suspicious symptoms, get tested." and link to the FAQ entry https://www.coronawarn.app/en/faq/#vac_cert_red_warning.
Expected Benefits
Users which are vaccinated against COVID-19 and receive a notification about an encounter with increased risk can find information on how to behave directly inside of the app and are guided to the FAQ in an easy way.

@Ein-Tim
Your suggestion is related to https://github.com/corona-warn-app/cwa-wishlist/issues/488 where I suggested that the app should use the vaccination status of the smartphone user to modify the risk assessment and message.
Your suggestion is to just add the scenario of a vaccination user to the guidelines text output, as can be seen on the screenshots:
https://www.coronawarn.app/en/screenshots/#ios_cards or
https://www.coronawarn.app/en/screenshots/#android_cards
like https://www.coronawarn.app/assets/screenshots/2-10/en/android/TracingDetailsFragment_tracing_increased.png

I support your suggestion!

The guidelines might also want to cover the case of a recovered person receiving a red warning.

This issue has been mitigated in version 2.15.1 with the updated texts.

@Ein-Tim Thanks for following up!


Feature: Add telemetry to understand if & how the extension is used

This ties in well with #8 and check which languages / frameworks are used, where developers would drop off/have issues with.

Basic telemetry implemented with #58.


Fix active_dims handling in pyro.contrib.gp

Simple fix to use | rather than + for set operations.
Tested

added a regression test
fixed a nearby death test

cc @fehiepsi

LGTM. It was a bug and @fritzo already fixed it.


Add existing ECR policy to controller IAM role

Goes some way to resolve https://github.com/coreos/coreos-kubernetes/issues/620

Replaced by coreos/kube-aws/pull/35


Complain loudly when there are missing @EntityMappings

Hello!
We just rewrote our entire platform from DGS to Spring GraphQL and generally we are very happy with what you have built here! We just stumbled upon one bug we had caused by misconfiguration that got kind of buried in the runtime errors where I think a louder crash upon launch maybe should be preferable.
The "problem"
In short: We had a copy paste error in one of our @EntityMapping declarations for a federated entity, and the result was that some of our federated queries failed without any loud exception simply with the error message No entity fetcher. We noticed eventually because some of our outer use cases failed, of course, but I wonder if the library could detect this problem earlier and complain super-loudly. I think DGS does this, but I am not 100% sure.
In detail, here's what happens (if I read the code correctly):

If there is a missing @EntityMapping, then the EntitiesDataFetcher produces a regular GraphQL error
This, I assume, is to possibly be able to produce values for any entities that are NOT missing a handler

The suggestion
What if FederationSchemaFactory could (either in afterPropertiesSet or createSchemaTransformer or similar), double check that the list of provided @EntityMapping covers all the declared, resolvable, federated entities (types with @key(..., resolvable: true)), and if not crash with a user friendly exception?
Unless I am missing something, this should be the behaviour one would want, because if you didn't want an @EntityMapping, then you likely should mark the entity in the schema as resolvable: false. And my experience in general with Spring is that it is very good at complaining loudly with a clear explanation when there is a suspected misconfiguration.

More specifically in our case - the copy-paste error we had meant that we have DUPLICATE @EntityMapping declarations for the same time - which also didn't produce any kind of warning or error - which itself maybe should've been an error.
Let me know what you think, and whether you are open to me making an attempt at building this myself and sending a PR.

Thanks for the suggestion, and good to hear your experience has been good.
We will consider if we can integrate this into the SchemaMappingInspector. It should be possible but federation is a higher level package and there can't be a direct dependence.
Alternatively, it would be straightforward to build it into the FederationSchemaFactory which knows about entity mappings, abd can discover federated entity types similar to the way SchemaTransformer does.

Sounds nice! Thanks for the quick reply! Let me know if I can be of help in any way.


Upgrades may be researched multiple times

Once researched, an upgrade should not be researchable again.
Example bo
Bo given by https://github.com/BurnySc2/sc2-planner/issues/18#issuecomment-764218650

I could try and do this one!

Fixed in https://github.com/BurnySc2/sc2-planner/pull/36
However it could also require an error message if possible.


Proxy device: port range

Required information

Distribution: ubuntu
Distribution version: 18.04
The output of "lxc info" or if that fails:

config:
  core.https_address: <IP_ADDRESS>:8443
  core.trust_password: true
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses:
  - <IP_ADDRESS>:8443
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
...
    -----END CERTIFICATE-----
  certificate_fingerprint: [masked]
  driver: lxc
  driver_version: 3.0.0
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.15.0-20-generic
  server: lxd
  server_pid: 1785
  server_version: 3.0.0
  storage: btrfs
  storage_version: "4.4"
  server_clustered: true
  server_name: lxdhost

Issue description
Proxy device port ranges possibly not implemented?
Steps to reproduce
lxc launch ubuntu:18.04 c1
lxc exec c1 -- apt install nginx
lxc config device add c1 http proxy listen=tcp:<IP_ADDRESS>:80 connect=tcp:<IP_ADDRESS>:80 bind=host

using the browser to get <IP_ADDRESS>:80 results in the nginx welcome page. continuing with
lxc config device remove c1 http
lxc config device add c1 http proxy listen=tcp:<IP_ADDRESS>:70-90 connect=tcp:<IP_ADDRESS>:70-90 bind=host

returns Device http added to c1 but the port range doesnt work. So either the syntax is different (and I couldn't find it), or this isn't implemented. Implementing this is IMO quite important for the usability of the proxy device, some services, i.e. ftp, require a dedicated range of ports (in case of ftp for passive transfers). Other uses may be i.e. in p2p networking, etc.

Seems like something that might be worth implementing.

Should be fine so long as we can have a single forkproxy instance handle the entire port range, if we need one proxy process per port that'd be quite wasteful and difficult to track.

That shouldn't be too hard. We basically have two good options:

threaded-listeners aka separate go routines for each port
single-threaded epoll-listener

Also, I'm just going to support this for TCP now, not UDP.

Ah, what's making udp harder?

If we do UDP support we also need to support cross-protocol which takes a little more thinking since we need to pool on multiple instances then.

Also I'm almost certain that {e}poll() might be the way to go here. If users give us something like:
tcp:ip:1,2,3,4,5,6,10-200,800-1200

we're going to be using a lot of go routines.

Oh right, I plan on supporting the following syntax tcp:ip:1,2,3,4,5,6,10-200,800-1200 aka:
<protocol>:<addr>:<port_0>[-]<port_n>[,<port>]...

Well, forwarding between udp and tcp is something we can certainly skip (even in general if that lets us cleanup some code) as I can't really think of a legitimate usecase for this.
However forwarding a range of UDP port is very common (needed for FTP for example) so we should really support that part :)
Does banning forwarding between udp and tcp in general (and returning a suitable error) make things easier for us? If so, please do that :)

I'm currently thinking about brute-force way using go routines for a first try and if we run into performance issues going down the epoll route. It would be nice but it would also involve a lot of C boilerplate and careful handling of cgo memory handling. The way I thought about it was essentially to register an fd in an epoll instance and then as data add the go listener but I suspect that the go listener containers go pointers which is illegal in cgo. So go routines it is for now.

I concur with @stgraber. Cross-protocol support on whole port ranges is something I can't imagine to actually use, except for some really unorthodox setups. Otoh having the UDP range forward to an UDP range makes total sense. The FTP usecase + some mailstack scenarios are actually one the important reasons why I opened this issue.

If it's abstractable easily I'll support everything. I have the infrastructure in place already.

@killua-eu, I just sent a branch marked as RFC. Please take a look if this covers your use case. I specifically need to know whether the following is what we want or not (//cc @stgraber):

The old implementation used to call connect() every time a new client got
accepted. Iiuc, this is not what we want. Ideally, we'd want all clients to
dump their traffic to the same connect()ion. This is especially true when we
are forwarding multiple ports. Unfortunately, this makes the actual
implementation more complex.
In any case, I might be mistaken and what we want is that each new accepted
client on the forwarded port also causes a new connect() call.

The gist is that each new client (for UDP and TCP) causes accept() but all share the same connect() to forward to.

@brauner , the usual usecase for me is to map a port range to a port range, keeping the port range sizes the same on listen and connect, I commented https://github.com/lxc/lxd/pull/4663/files#diff-fc8681e9ed281b244aced7594682e21f accordingly. Not being familiar with the lxd codebase and go, I only skimmed through the code.

@stgraber , @brauner: Guys, I just want to send a big THANK YOU to both of you. This (along with the other pf issues you closed really fast) is a really big deal greatly simplifying all my LXD deployments.


Simplify label explanation

Simplify hardware CSV label explanation in docs.

/approve
/cherry-pick release-0.10


Reorganize pages

This PR re-organize the overall documentation structure.
Main topics:
Tools -> tool folder
Editing -> editing folder
Executing -> runtime-service-modeling folder
Reference -> reference folder

Replaced by https://github.com/IBM/bamoe-docs/pull/122


feat: filter barracuda

There is no host here. Checked avi_vantage_no_host and worked. Please review

:tada: This PR is included in version 2.25.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Hiver Extension (Install Hiver for your browser, and supercharge your Gmail to provide stellar personalized customer service.)

Describe the solution you'd like
you will be able to access any number of shared email accounts such as marketing@, help@, right from your own inbox – no more switching accounts! On top of that, you will be able to assign tasks to teammates and track their status.5 days ago
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

@Sulagna-Dutta-Roy I request you to add the GSSOC Label

No pull request received since long time. Closing this


how to set title in winbox.addControl

It's possible to set title over image(icon)?
Or show message when cursor hover on the image.

You can achieve this by applying the title in the oncreate callback by using standard Javascript.
WinBox({
    oncreate: function(options){
        const nodes = this.window.querySelectorAll(".wb-title, .wb-icon");
        nodes[0].title = nodes[1].title = "Some title";
    }
});


[Kotlin] General DSL Cleanup and Simplification

Most DSL functions are now unit functions. This greatly simplifies the type hierarchy of the builder classes and should be source code compatible with code from prior versions.

Coverage remained the same at 100.0% when pulling a1eee898501dc768d9863f266004d68e45413c64 on jeffgbutler:kotlin-dsl-cleanup into 84956871baa56dce545c35494cd3bb2bcbfa9fe1 on mybatis:master.


Add namespace to the xpanse user with the role CSP

We want to add the namespace property to the xpanse users with the role CSP.
As we are using Zitadel to manage our users, the meta field may be a good choice, let's have a try.

[ ] Add namespace property to the meta of the users with the role CSP
[ ] Turn this property to namespace at the API level of the xpanse.

I will take this.


enhane Use pool executor for s3 operation

Proposed changes
Issue Number: close #xxx
The default executor of Aws S3 SDK is so cpu-consuming because it uses one atomic bool to do cas operation to do thread allocation and detach logic.

There would be a lot of CPU consumption when concurrent request reaches.
So this pr makes all the S3 operation invoked in one thread pool.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

We don't need pool executor if we had already used the sync interface.


rChat in 7.1 version

rChat module doesn't work in WOW 7.1 version

Blizzard renamed the Social button to something stupidly bizarre.
Will upload fix shortly.

ver. 1.9.15 fixes this problem.


Feature Request : Sync due dates between Trello & Habitica

Hi :)
I think you meant another project, probably this one: Trello-habitica


CSV Sender: Onboarding and operations - adding individuals to upload data

Problem statement
As a CSV upload pilot sender
I want to add other individual to submit reports for the facility
So that [we can report daily - individuals can be sick and go on vacation]
What you need to know

2.24.22 communication: "Once we are really going, can I have another person added to be able to submit the reports for us? That report would be very helpful in that situation too."
a big part of the invisible work of onboarding senders is the learning that takes place and the very micro practices each user created to understand the task and complete the task.

Acceptance criteria

[ ] ...

To do

[ ] ...

Closing this ticket with uploader's move to simplereport


flynn install on <IP_ADDRESS>

I am running the flynn-cli and need to bind the web-installer to <IP_ADDRESS> instead of localhost.
The cli only allows:
flynn install
and nothing like:
flynn install -h <IP_ADDRESS>
What do I need to change/adjust to make this happen?

I think I found the file:
flynn/installer/http.go
Can this be updated to support binding to <IP_ADDRESS> ?

@Kentoseth although the output of flynn install includes http://localhost, the installer does in fact bind to <IP_ADDRESS> as desired.


"This test did not perform any assertions" warning when using Actions\expectDone in test

Hi,
I have set up a test case following the documentation at https://brain-wp.github.io/BrainMonkey/docs/wordpress-hooks-done.html#test-fired-hooks-with-expectations - my test case is almost identical to the example provided in docs.
I noticed that when the test fails, there's an error reported, but when it passes, PHPUnit (I'm using version 6.5.7) complains about it being risky: "This test did not perform any assertions".
Is this expected behavior?

This is because you did not integrate Mockery (which is used under the hood) and PHPUnit.
You can do this by adding the following trait to your (base) test case class:
class MyTest extends MyTestCase {

    use \Mockery\Adapter\Phpunit\MockeryPHPUnitIntegration;

    /* ... */
}

This has been discussed before (on Twitter), and I thought the result was that this should be documented somewhere. Brain Monkey will most probably not take care of this kind of integration, because it is specific to PHPUnit (althoug Brain Monkey itself if framework-anostic).

Hi Thorsten,
Thanks, your suggestion fixed the problem!
It seems this has been already documented (in 7a5b4ce8d000090bdc6cdb193ea3045a86b0d5ad), but the online docs have not been updated since.


Search text must include the start of the field value in order to return results

When searching for an activity or event based on the name or type (depending on how app is configured), no results are returned unless the text entered matches the beginning of the value for the configured field.
For example, using the Event Locator, we'll use the event "Concert with Soloist Ruth Capobianco" as a repro case:

Launch the application and click OK in the splash screen

On the search panel, search using "Concert"

Note how the correct event is returned under the events heading.  Because "Concert" is the start of the string:

Now search using "Ruth Cabobianco".  No results are found.  Because "Ruth Cabobianco" appears later in the string:

The application essentially requires the users to know the exact name of the feature in order to successfully search for it.  We can get around this slightly by configuring the SearchExpression in the config.js to allow searching on multiple fields (e.g. Event Name and Event Type: SearchExpression: "UPPER(EVENTTYPE) LIKE UPPER('${0}%') OR UPPER(EVENTNM) LIKE UPPER('${0}%')",), allowing users to search using words like "music".  Regardless, the search experience would be better if it recognized substrings from the middle/end of the field value.
Note:  This is not a new issue.  It is present in the currently released version of the application.
FYI @jessnoo

Verified with https://github.com/Esri/configurable-locator/commit/f29655826e983450e244d578c251f56d805459ff.


adding NCL language

https://github.com/search?utf8=✓&q=extension%3Ancl+NOT+what

Thanks for the pull request! Do you know if these files are NCL too?

Those are poorly-named documentation files for NCL functions.

What's better?
On Jun 6, 2015 3:10 PM, "Ryan Pavlick"<EMAIL_ADDRESS>wrote:

Those are poorly-named documentation files for NCL functions.
—
Reply to this email directly or view it on GitHub
https://github.com/github/linguist/pull/2440#issuecomment-109582179.

extension:ncl NOT "THE_URL" NOT "ISO-8859-1"

Would it be correct to recognize these files as Text?

@pchaigno Yes.

In this case, could you add .ncl to the Text entry in languages.yml too (with a sample in samples/Text/)?

@pchaigno I added the example to Text and updated the license in the grammar submodule.

@pchaigno I updated the grammar submodule link to https.

It's still failing locally. I don't think you can just update the .gitmodules file. You'll probably have to remove the submodule and add it again to be sure :/

I'll see first if it's not an issue on my side...

@pchaigno I removed the submodule and added it back with https.

I tested the detection of .ncl files with 2,000 samples:
| Text | NCL |
---- | ---- | ---- |
1,000 Text files | 60.39% | 39.61% |
1,000 NCL files | 7.45% | 92.55% |
The Bayesian classifier doesn't seem to be very good at distinguishing Text and NCL files :/
We could try to improve it by adding more samples or we can define a new heuristic rule.
Do you want me to send you the sample files?

Yes, please do.

@rpavlick In your inbox :zap:

@pchiagno So, if I manually go through these and sort out the errors, would that help?

@pchaigno So, if I manually go through these and sort out the errors, would that help?

Not really. It's a matter of keywords so there's not much to do there except for adding new samples.
If adding a few more samples doesn't improve things, we'll see how to define a new heuristic rule.

@pchaigno I added quite a few NCL samples.

That's a bit over the top, isn't it? :smile:

@rpavlick We currently can't add too much samples because of #2117 :/

@pchaigno @larsbrinkhoff I decreased the number of added samples.

@rpavlick Could you test the detection results in local with the samples I gave you?

@pchaigno What is the command to run that test?

bundle exec rake samples # once
bundle exec rake test

@pchaigno
It is getting hung up on a false detection of Frege in one of the Text samples. Do you have any suggestions for implementing a heuristic?

Failure:
TestHeuristcs#test_fr_by_heuristics [/Users/rpavlick/Github/linguist/test/test_heuristics.rb:122]:
Failed for /Users/rpavlick/Github/linguist/samples/Text/NhlUpdateWorkstation-help.ncl.
--- expected
+++ actual
@@ -1 +1 @@
-[#<Linguist::Language name=Text>]
+[#<Linguist::Language name=Frege>]

#2441 should fix this. In the meantime, you can change "Text" => all_fixtures("Text") to "Text" => all_fixtures("Text", "*.fr") in test_heuristics.rb.

@pchaigno
From a large sample (n=951) of known NCL files taken from Github, it is now predicting with ~98% accuracy.
For a large sample of  (n=751) other files with extension .ncl, it is around 92%. From those, nearly all of the errors come from one github repository (https://github.com/fanghuan/ncl) and they all contain the text strings, "THE_URL:" and "THE_TITLE:".

For a large sample (n=751) of other files with extension .ncl, it is around 92%.

Do you mean 92% files correctly identified as Text?

@pchaigno
Yes, it correctly identifies 92% as Text.

@pchaigno @larsbrinkhoff I decreased the number of added samples.

I'd really like to see this dramatically reduced (see https://github.com/github/linguist/pull/2117). What happens if we reduce to ~5 NCL sample files? Does Linguist still do a reasonable job?

@arfon @pchaigno @larsbrinkhoff
I reduced it to 16 samples in /samples/NCL and 8 samples in /samples/Text. It correctly classifies my whole set of known NCL files (n=951). I tried with 5 samples but could not get the same level of accuracy.
It incorrectly classifies all of the .ncl files in the github repository fanghuan/ncl. All of these files contain the text strings, "THE_URL:" and "THE_TITLE:". It did not misclassify any other Text files with extension .ncl.

I reduced it to 16 samples in /samples/NCL and 8 samples in /samples/Text. It correctly classifies my whole set of known NCL files (n=951).

With 100% accuracy? Does that mean it that the results are better with less samples??

I also removed a sample from /samples/Text which probably should have been classified as an NCL file. I think that probably made most of the difference, although I didn't test it atomically.

I also removed a sample from /samples/Text which should have been classified as an NCL file. I think that probably made most of the difference, although I didn't test it atomically.

Okay, that makes more sense :-)

I don't get the same results for the Text files :/
$ bundle exec linguist ../samples-ncl-text/
79.94%  NCL
20.06%  Text

Full results here: https://gist.github.com/pchaigno/2478bc86dd831382bfba

@pchaigno
They all look correctly classified to me, except for the ones in 'fanghuan/ncl'. I went manually went through all of the ones where I didn't already know based on the filename or the repository owner.

It now correctly classifies all of my test files.

@rpavlick thanks for this. These changes will be live in the next release of Linguist (next couple of weeks)

Great! Thanks.


Toggle facing breaks continuous focus

Steps to reproduce:

Start cameraview with focus set on continuous and facing set on back;
Toggle facing using cameraView.toggleFacing();
Camera does not focus anymore, neither in back or front facing.

Calling cameraView.setFocus(CameraKit.Constants.FOCUS_CONTINUOUS) after toggling does not help.

Hi! i have to put CameraKit.Constants.FOCUS_CONTINUOUS as a default Value to make it work.

What do you mean?

Has the cause of this been found yet? I am also able to reproduce this issue on 0.12.1

I found a temporary workaround to get focus working again after switching camera until the underlying issue is resolved.
After changing to the front or back camera:
cameraView.stop()
cameraView.start()
cameraView.setFocus(CameraKit.Constants.FOCUS_CONTINUOUS)

This issue has been resolved in v1.0.0. Closing this issue. If there still are focus issues in 1.0.0 I will make new ticket to keep track!


Support adding dataframes of metadata

At present, one must either add metadata from a file (load_meta()) or individually (set_meta()). We can extend one of these (probably best to do so on set_meta()) to support loading multiple metadata columns in one go.
Does anyone have an opinion before I propose an implementation?
cc @danielhuppmann

Sure, good idea! For completeness, you can already pass a suitable pd.DataFrame at initialization using
pyam.DataFrame(data, meta=<some meta frame>)

This is implemented here, should be just a few lines (and a test) to extend set_meta()
https://github.com/IAMconsortium/pyam/blob/1abb9784c7bb79cc3701deb5161fa20c1899d2ae/pyam/core.py#L206

closed by #679


collapse-callout Quarto extension

Link to suggestion
https://github.com/shafayetShafee/collapse-callout
Targeted section
Extensions
Describe your suggestion
Filter that provides global options to make the Callout Blocks collapsible in HTML documents.
Checklist

[X] checked if your suggestion is not already listed in Awesome Quarto list.
[X] checked if it can fit in an existed section or open a discussion to suggest any new sections..
[X] checked when it's a repository if it's maintained (archived repository will be rejected).

Added in #177


Minimize Code Smells

https://github.com/sopra-fs23-group-32/SoPra23_Client/commit/91ff4f39135efe2aa16ab2811fecce3b689efeaa


Error starting the app up.

I don't know what happens but I couldn't get it to work. I'm sure everything required is installed and I followed the instructions step by step.
/ Ubuntu 20.04 Focal Fossa here.
Traceback (most recent call last):
  File "./main.py", line 3, in <module>
    from youtube import Youtube
  File "/home/owz/smd/youtube.py", line 5, in <module>
    from pytube import YouTube
  File "/home/owz/.local/lib/python3.8/site-packages/pytube/__init__.py", line 16, in <module>
    from pytube.streams import Stream
  File "/home/owz/.local/lib/python3.8/site-packages/pytube/streams.py", line 17, in <module>
    from pytube import extract
  File "/home/owz/.local/lib/python3.8/site-packages/pytube/extract.py", line 7, in <module>
    from pytube.compat import quote
ImportError: cannot import name 'quote' from 'pytube.compat' (/home/owz/.local/lib/python3.8/site-packages/pytube/compat.py)

+1 on this. Followed step by step (although I wish the instructions were more detailed), and I achieve the above result on Ubuntu 20.04 and Python 3.8. Any help would be much appreciated.

+1 on this. Followed step by step (although I wish the instructions were more detailed), and I achieve the above result on Ubuntu 20.04 and Python 3.8. Any help would be much appreciated.

I guess it's because of old Python version used. I'll also try different methods to see if I can achieve usage of it. Anyway, thanks for confirming. :)

Try changing the pytube version

Try changing the pytube version

Can you tell us how? Because the version it grabs is latest one, which causes the problem.

Try changing the pytube version

Can you tell us how? Because the version it grabs is latest one, which causes the problem.
You can use this code pip3 install pytube==your pytube version
Change the pytube version to the one you want. For example,
pip3 install pytube==9.0

Try changing the pytube version

Can you tell us how? Because the version it grabs is latest one, which causes the problem.

You can use this code pip3 install pytube==your pytube version
Change the pytube version to the one you want. For example,
pip3 install pytube==9.0

Installing 9.0 fixed this particular issue... brought many more to light but it seems to be the solution for this issue.

Got it. Thanks for lighting me up, everyone. Now closing the issue as it's resolved now.


Add first name and last name to user card when verify IDIR user

Describe the task
Display first name and last name to user card when verify IDIR user when grant user access.
Private Zenhub Image
Acceptance Criteria

[x] backend get first name and last name information from our IDIM proxy project, and return to frontend
[x] backend from_api_json method update json_dict["userId"] to json_dict.get("userId") to avoid key error in not found case
[x] frontend receive first name and last name information from back and display in the user card
[ ] verify if still need to show display name, if not, remove the display name and create a ticket in IDIM-PROXY project to remove display name in the return data and clean up return data in the not found case to only return "found: false"

This ticket is blocked by https://app.zenhub.com/workspaces/fsa-fingerprint-61f04f08304d3e001a4f2578/issues/gh/bcgov/nr-fam-idim-lookup-proxy/40
Additional Context

This ticket may encounter issue faced at #365 (see the ticket comment on temporary solution for api-client gen).
A special note is added in client-code-gen README to deal with current bug from swagger spec. Please also take a look of the note when generating api-client code.

Cleanup ticket created in the nr-fam-idim-lookup-proxy project: https://app.zenhub.com/workspaces/fsa-fingerprint-61f04f08304d3e001a4f2578/issues/gh/bcgov/nr-fam-idim-lookup-proxy/64
and the cleanup need to wait until we deploy the changes in FAM prod

@MCatherine1994  looks good


SKETCH_VERSION "2.1.1" does not fit in the ESP-01 memory

Hi.
I am trying to compile Sketch v2.1.1 on an ESP8266 ESP-01 and it tells me that it does not fit. By selecting a minimum of 512K (64K SPIFFS) in order to upload "index.html" the memory usage is 104%.

Disabling some things that I do not need in "definitions.h" I get down to 101%.
//#define USE_NEOANIMATIONFX  // Uses NeoAnimationFX, PIN is ignored & set to RX/GPIO3 or UART method: D4/GPIO2, see: https://github.com/debsahu/NeoAnimationFX
#define USE_WS2812FX          // Uses WS2812FX, see: https://github.com/kitesurfer1404/WS2812FX

// Neopixel
#define PIN 0           // PIN (14 / D5) where neopixel / WS2811 strip is attached
#define NUMLEDS 22       // Number of leds in the strip
//#define BUILTIN_LED 2    // ESP-12F has the built in LED on GPIO2, see https://github.com/esp8266/Arduino/issues/2192
//#define BUTTON 4         // Input pin (4 / D2) for switching the LED strip on / off, connect this PIN to ground to trigger button.

const char HOSTNAME[] = "McLighting01";   // Friedly hostname

#define HTTP_OTA             // If defined, enable ESP8266HTTPUpdateServer OTA code.
//#define ENABLE_OTA         // If defined, enable Arduino OTA code.
#define ENABLE_AMQTT         // If defined, enable Async MQTT code, see: https://github.com/marvinroger/async-mqtt-client
//#define ENABLE_MQTT        // If defined, enable MQTT client code, see: https://github.com/toblum/McLighting/wiki/MQTT-API
//#define ENABLE_HOMEASSISTANT // If defined, enable Homeassistant integration, ENABLE_MQTT must be active
//#define ENABLE_BUTTON        // If defined, enable button handling code, see: https://github.com/toblum/McLighting/wiki/Button-control
//#define MQTT_HOME_ASSISTANT_SUPPORT // If defined, use AMQTT and select Tools -> IwIP Variant -> Higher Bandwidth
#define ENABLE_LEGACY_ANIMATIONS

Do you think you can purge more?
I think it would be interesting to be able to use this project again in ESP-01.
Thank you.

Disable OTA, I don't think you will have enough space to OTA anyways.

Also have you seen this: https://youtu.be/xyc1gCjguRU very easy to do.


change term to satisfy policheck requirements

PR Summary
change term 'hang' to approved verbiage
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

Lol, if that's what it takes to make the tool happy, then why not 😂

part of the MS policy checks we're required to do


Fix doc warnings

Documentation build has been emitting a number of warnings, each of which generating invalid (corrupt) documentation.

No, I think it's enough to fix those sphinx complains about.

In offline discussion, we need to write class name only when an attribute name is ambiguous.

LGTM


train_online.py error  attribute or import error

Rasa Core version: 0.11.1
Python version: 3.6.7
Operating system (windows, osx, ...): Windows
Issue: when i use, train_online.py like this :
from rasa_core.training import online
agent.train(data,
batch_size=50,
epochs=200,
max_training_samples=300)
online.run_online_learning(agent)
i am getting :
online.run_online_learning(agent)
AttributeError: module 'rasa_core.training.online' has no attribute 'run_online_learning'
and when i use
from rasa_core.interactive import interactive
agent.train(data,
batch_size=50,
epochs=200,
max_training_samples=300)
interactive.run_interactive_learning(agent)
i am getting :
from rasa_core.interactive import interactive
ModuleNotFoundError: No module named 'rasa_core.interactive'
which one is correct and how can i solve my problem ?
Thanks.
Content of domain file (if used & relevant):

it's rasa_core.training.interactive i believe

i got same error
Traceback (most recent call last):
File "train_online.py", line 8, in
from rasa_core.training.interactive import interactive
ModuleNotFoundError: No module named 'rasa_core.training.interactive'


Support for TypeScript 1.5/latest module kind output options 'umd' and 'system'

grunt-ts allows to use the latest TypeScript 1.5 beta compiler with the 'compiler' option. However, compiling with option 'module': 'umd' breaks with the message: 'WARNING: Option "module" does only support "amd" | "commonjs"'
The file modules/compile.ts should be modified to allow 'umd' and 'system' module kinds.

We're working on it. In the meantime feel free to search for that error text.  It should hopefully be fairly straightforward to delete that check.

Should be working in 4.2.0-beta.1 which I just pushed to npm.  Please let me know if not.  Thanks for the report!


fix for #8512

Change Summary
This is hopefully a fix for #8512, that I've reported a few days ago.
Basically, it makes PlainValidator.__get_pydantic_core_schema__ reuse other annotations informations.
If I did anything wrong, please let me know.
Related issue number
fix #8512
Checklist

[ ] The pull request title is a good summary of the changes - it will be used in the changelog
[X] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[X] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Selected Reviewer: @lig

please review

I require assistance to fix the type-checking issue mentionned in the linting job


Update for Hedwig master

This PR is to update this adapter to be inline with the changes discussed in hedwig-im/hedwig#38.
Currently using esl/exml is causing breakage on Romeo. See scrogson/romeo#5.
I'm in the process of updating Romeo to use fast_xml. This will be better for the user experience since fast_xml is on hex.pm it can just be pulled in along with Romeo.

Thanks! I hadn't noticed the issue myself yet, as we're still on an earlier locked version of exml I assume..


full page reload when component has been modified

Describe the bug
Changing single component using create-react-app will show immediate  results meanwhile using vite, it triggers full page reload. On large application its very bad DX because it takes 6 seconds to see results on even small changes.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This is due to HMR. This allows for changes in the server without having to restart it. You can disable HMR by appending/modifying your vite.config.ts file:
export default defineConfig({
  server {
    hmr: false,
  },
});

This makes it so that websites delivered by the server don't reload themselves.

This is due to HMR. This allows for changes in the server without having to restart it. You can disable HMR by appending/modifying your vite.config.ts file:
export default defineConfig({
  server {
    hmr: false,
  },
});

This makes it so that websites delivered by the server don't reload themselves.

Disabling HMR does not help because then you wont see changes on the screen. Normally vite detects a change in a single component and it updates screen without restarting the whole application.

In my provided github repo, something breaks HMR so that it detects a change in a single component,but instead of updating component, it reloads the application. Reloading the whole app is very slow for a large codebase.

when that app was using<EMAIL_ADDRESS>HMR was working as expected.

I just realised this today in my app and it turns out this also happens when creating a new vite react app from scratch.
Downgrade to<EMAIL_ADDRESS>and HMR works again:

The issue appears from<EMAIL_ADDRESS>onwards as far as I can see.

I just realised this today in my app and it turns out this also happens when creating a new vite react app from scratch.
Downgrade to<EMAIL_ADDRESS>and HMR works again:

The issue appears from<EMAIL_ADDRESS>onwards as far as I can see.

oh interesting ! I will test it tomorrow

@desko27 apparently I was using legacy import reactJsx from "vite-react-jsx" plugin  in my applications. All I had to do is to switch to @vitejs/plugin-react and HMR has been solved
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'

export default defineConfig({
 plugins: [react()]
})

Same issue for us. A downgrade to  2.5.10 fixed

Followed @Digital-Coder advise and it works! Thanks


fix(deps): update module golang.org/x/tools to v0.25.0

This PR contains the following updates:

Package
Type
Update
Change

golang.org/x/tools
require
minor
v0.24.0 -> v0.25.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

2 additional dependencies were updated

Details:

Package
Change

golang.org/x/mod
v0.20.0 -> v0.21.0

golang.org/x/net
v0.28.0 -> v0.29.0


mm:initialize ensure alignment.

Summary
Broken by 635cfadc2598f14d7cac4482acd9ed85d5dbe5ac
On an stm32 the heap is formed from
const uintptr_t g_idle_topstack = HEAP_BASE;
where HEAP_BASE is &_ebss + CONFIG_IDLE_STACKSIZE.
Both these values are not deterministic. One
comes from the compiler, the other the system
configurator.
a 3 byte bss and 250 byte stack would lead to
and unaligned address used as the heap to be.
The compiler used clever strd r1,r3,[r5,#8] to
store 2 values in one memory cycle into the
heap_impl struct. Resulting in a hardfault.
Change the amount of bss or the CONFIG_IDLE_STACKSIZE
could lead to a non-functional NuttX system.
Impact
Critical to fix in 10.1 release
Testing
cuav_x7pro_bootloader [PX4]

FYI @mage1

I don't believe this is a problem.  The alignment is handled at link time by the linker script.
NOTE:

where HEAP_BASE is &_bss + CONFIG_IDLE_STACKSIZE.

Actually _ebss, not _bss.  _ebss should be the end+1 address of .bss
For stm32f4discovery:
.bss : ALIGN(4) {
    _sbss = ABSOLUTE(.);
    *(.bss .bss.*)
    *(.gnu.linkonce.b.*)
    *(COMMON)
    . = ALIGN(4);
    _ebss = ABSOLUTE(.);
} > sram

So _ebss will always be aligned.  A three byte misalignment is impossible.  But there could still be an alignment issue since the stack requires 16-byte alignment.
I would think that the correct fix might be to change this to ALIGN(16) in the linker script?

@patacongo -  ALIGN(8) did not work, the there wild card is the CONFIG_IDLE_STACKSIZE. The fix is restoring how it worked before the 635cfad.  The change broke the alignment.  Before the heap was adjusted, the changed code intercedes and uses the unaligned value.

The run below is with the align 8
24001530 A _ebss

The next step is common ISR on the way to hard fault

The change looks good.

I walked through this with @davids5. I agree with the fix.
This change broke things:
635cfad
What I find interesting about this change is that @davids5 raised a valid criticism about the change needing a better explanation and yet it was approved without even a response to his comment.

I think @davids5's concern is addressed before merging: both background info and ASAN heap manager is provided in PR.

Changes effecting such a critical piece of memory should get a more thorough review than a single reviewer.

Four people join the review in 3 days and get approved before merging. The issue is hard to find in our environment since most link scripts(include ours) add algin(4)/align(8) after .bss.
Anyway, thank you and @davids5 spending the time to find the root cause.

I think @davids5's concern is addressed before merging: both background info and ASAN heap manager is provided in PR.

Testing
Pass the build without error.
No. Build testing an architectural change of this nature was NOT addressing my concerns.
Yet you merged it.
No one diversity tested it or had a chance to commented on the potential security issue this change could be used to exploit.
The diversity of configuration used to test is what finds this type of thing. Testing on Real HW finds this sort of thing.
I think this raises a bigger issue. The authored by, 'reviewed byandcommitted by` should NOT be that same organization. That would be akin to merging your own PR.  There needs to be real testing and approval on changes greater that a emergency build fix that effect the system.

I think @davids5's concern is addressed before merging: both background info and ASAN heap manager is provided in PR.

Testing
Pass the build without error.
No. Build testing an architectural change of this nature was NOT addressing my concerns.

The change pass our internal test. The real problem is that your CONFIG_IDLE_STACKSIZE is too odd, but we don't have the similar config to reproduce this issue.

Yet you merged it.

If you look at the timeline: https://github.com/apache/incubator-nuttx/pull/3086

PR is created on March 17
You give the comment for more info, we update PR immediately
There are more dissusion and clarification on March 18
I ask people for more comment on March 19
Nobody give the nagtive feedback or request more time to test
I finally merge PR on March 20

No one diversity tested it or had a chance to commented on the potential security issue this change could be used to exploit.
The diversity of configuration used to test is what finds this type of thing. Testing on Real HW finds this sort of thing.
I think this raises a bigger issue. The authored by, reviewed by and committed by should NOT be that same organization. That would be akin to merging your own PR. There needs to be real testing and approval on changes greater that a emergency build fix that effect the system.

Yes, we need more test to avoid the regression. But, please give some test plan or progress in PR, so we can coordinate with each other.

Yes, we need more test to avoid the regression. But, please give some test plan or progress in PR, so we can coordinate with each other.

I think we need to give people more time. Everyone is dealing with their own sets of problems on a day to day basis. 3 days is an eternity when it's your work you're trying to push through - but it's not so long when you've got your own deadlines and then additional PRs come in that need thorough testing/review.
To @davids5 point, this is why it is probably better practice to not allow individuals from the same organization to approve PRs. Both will be incentivized to get it through. Much sophisticated engineering is done and cross-checked using red/blue teams. This mentality helps be critical of the others work. The same philosophy should be being applied here.
I really don't want to create processes that are burdensome and slow things down. However, I do think it's important that we adjust our process to avoid regressions like this and improve the security/reliability of the OS.
What I would propose is this:

Change 'Impact' in the PR template to be 'What boards will be affected by this change?'
To this, common answers will be:
- All stm32h7 boards
- All boards
- Any board using XX driver
The reason for this question is to be able to quickly find PRs that will effect everyone. If the PR states it effects all boards, as this change would, we can add a tag to the PR. Those PRs should get a more thorough review.

Any PR that gets the tag, or is otherwise labeled a critical change should be reviewed by more than 1 person. Perhaps we say 2 is enough, or maybe it should be 3. In either case we should setup Github to require 2-3 accepted reviews before allowing a merge.

In general, I think we should set a policy that individuals from the same organization cannot approve their own PRs.

If this seems like a reasonable proposal, we can move the conversation to the dev list.
Let me know what you guys think.
-Anthony

I agree to improve the process to get more review from more people.

We discussed before the idea of using Code Owners and disabling the merge until XX approvals.  It seems that Code Owners is frowned on in Apache but still there are some projects using this feature and I believe we can do so as well (unless there is a better way).
Regarding the "no merge from the same organisation", I think this should be subject to some exceptions.  Some areas are only of interest to the people of one organisation.  Waiting for approvals from others won't achieve much.
As for changing "Impact" to "What boards will be affected by this change?", I find "Impact" a broader term that includes everything, boards, fs, networking, build system, etc.  We just have to clarify in that section.

If this seems like a reasonable proposal, we can move the conversation to the dev list.

Yes, please.  Let's move this discussion to the mailing list.


Feasts

Currently feasts don't register since they are in your bags, there is however a way to get a spell id, that I'm going to cross reference w/ all of the feasts to see if I can't come up with a way to check them.

I have found a way using the foodspell/drinkspell auras to find that you are eating a feast. Now the rest is just getting that information by eating each specific type of feast.


[GameTest][Bug] /reload not working with existing imports at all.

Describe the bug
/reload and gametest doesn't work correctly as if I /reload on existing imports file, game test just stops except for main with no error until I load back into the worldthe world
.
To Reproduce
Steps to reproduce the behavior:

import files in the main manifest import
tick something in one files
run /reload

Expected behavior
nothing happens
Resulting behavior
main runs except for the unchanged imports
Desktop (please complete the following information):

OS: Windows 11
Version: 1.19.10 beta

Nothing was changed in the files after world load.
https://user-images.githubusercontent.com/49619048/171726736-996b7d81-fd91-4cfd-84f5-9ec96260ce57.mp4

Opened an issue for tracking.

It might be that import scoped vars do not reset but idk

Hello!
It looks like we've made some progress on this. Since it's been a while, I'm going to close this issue, but if you have any additional feedback, please reach out to us!
Thanks!


ownChildren for reactions is null

I have a feed and I'm implementing the logic add reactions to reactions (i.e. liking post comments).
When getting the coments for a certain post i set the filter with:
.filter(LookupKind.ACTIVITY, {postId}, DEFAULT, limit, "comment")
In the result "ownChildren" is always null. I would expect it to contain data if I had liked the comment (this is the behaviour in iOS).
I need that in order to identify the post I've liked.
How can I get my own reactions to to reactions?
Cheers
gz#12930

Agent comment from Cody Smith in Zendesk ticket #12930:Hello,
We will look into this use case and get back to you as soon as we can.
Best,
Cody
°°°

Hello @ude
To further assist you with this issue, could you send an email to<EMAIL_ADDRESS>and include the app_id, user_id, feed group, and feed id you are experiencing this with?
Once we have this information in our support system we will investigate this further.
Best Regards,
Cody

This is a server sdk so it needs to pass user id additionally. Needs a fix.


Provide a consistent appearance to bullets in service-accounts and rbac

Indent the bullets using a multiple of 2 spaces
Remove trailing spaces

/kind cleanup

Thanks @windsonsea
previews look good to me:
https://deploy-preview-42187--kubernetes-io-main-staging.netlify.app/docs/concepts/security/rbac-good-practices/
https://deploy-preview-42187--kubernetes-io-main-staging.netlify.app/docs/concepts/security/service-accounts/
/lgtm


Messaging infra state manager

@enmasse-ci run tests profile=isolated-shared-infra

:x: Test Summary :x:
TEST_PROFILE: isolated-shared-infra
TEST_CASE:
TOTAL: 12
PASS: 10
FAIL: 1
SKIP: 1
BUILD_NUMBER: 367
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testInfraStaticScalingStrategy in io.enmasse.systemtest.sharedinfra.MessagingInfraTest

@lulf could you please rebase on current master and rewrite tests to current new model? Or I can do that

@enmasse-ci run tests profile=isolated-shared-infra

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=isolated-shared-infra

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: isolated-shared-infra
TEST_CASE:
TOTAL: 12
PASS: 12
FAIL: 0
SKIP: 0
BUILD_NUMBER: 390

@enmasse-ci run tests profile=isolated-shared-infra

:x: Test Summary :x:
TEST_PROFILE: isolated-shared-infra
TEST_CASE:
TOTAL: 12
PASS: 11
FAIL: 1
SKIP: 0
BUILD_NUMBER: 398
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testInfraStaticScalingStrategy in io.enmasse.systemtest.sharedinfra.MessagingInfraTest

@enmasse-ci run tests profile=isolated-shared-infra

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: isolated-shared-infra
TEST_CASE:
TOTAL: 12
PASS: 12
FAIL: 0
SKIP: 0
BUILD_NUMBER: 399


Add truncate option to csvlook

I found myself needing an option to truncate to the top n rows often while working with CSV files. Example usage:
csvlook --truncate 5 < example.csv

The head command is not particularly suited got this because of the fact that you need to consider the first 3 lines are part of the header. While you could just stay manually adding 3 to your head argument each time I thought it would make more sense to just provide the option from within csvlook.

Just noting to myself that agate has a max_rows option, which can be used to implement the same functionality as in this PR once #515 is closed.

@onyxfish Before implementing (not via this PR), are you good with adding this option to csvlook?

Just saw this feature was merged in with the option --max-rows so will close this PR