Don't emit stderr on successful bootstrap.

Context: it can be annoying to have tools output to stderr in non-error cases, because some consoles/UIs highlight errors in a special way. You don't want attention called too non-error cases. The unfortunate alternative is to redirect stderr to stdout, but then real errors don't get highlighted.
This came up when I was adding vcpkg into the Docker images we use for github.com/NVIDIA/thrust and github.com/NVIDIA/cub


Behavior Of textAlignment="right" with whitespace:pre-wrap

When textAlignment="right", I would expect pressing 'space' in a no-wrap scenario to introduce another space into the text content. However, because of whitespace:pre-wrap the space is not added until I press another character.  Changing whitespace to 'normal' solves this problem. However, changing it to 'normal' also introduces other irregularities, such as misplaced cursors after deletion.
The situation I'm using Draft in is a spreadsheet-cell, because I wanted to take advantage of the rich text capabilities of draft for things like autocompletion of cell references (which often contain metadata for my application), functions, etc. In many spreadsheet cells numeric values are right-aligned in the cell, with spaces appending normally and the cell enlarging (usually by multiples of column width) as you type. What's the standard way to disable or override Draft's text-wrapping and resizing behavior?

Yeah, that's annoying.
You'll definitely need to keep white-space: pre-wrap to avoid whitespace collapsing, for the reason you mentioned. Draft selection behavior needs the character count in text nodes to match the model.
A couple ideas:

Does it behave properly if you use white-space: pre?
You could possibly use handleBeforeInput to intercept spacebar presses, and insert a non-breaking space '\u00a0' instead. I don't know for sure if that would prevent the collapsing, but I have a hunch that it would.

It seems like this question has been sufficiently answered so I am going to close this issue. Thanks for bringing it up!


Fix Storybook compilation warning

The warning -
WARNING in ../core/src/components/Table/index.ts 1:0-47
"export 'TableColumn' was not found in './Table'
 @ ../core/src/components/Table/Table.stories.tsx
 @ ../core/src/components sync ^\.\/(?:(?:(?!\.)(?:(?:(?!(?:|\/)\.).)*?)\/)?(?!\.)(?=.)[^/]*?\.stories\.tsx\/?)$
 @ ./.storybook/generated-entry.js
 @ multi /Users/himanshu/workspace/spotify/backstage/node_modules/<EMAIL_ADDRESS>/Users/himanshu/workspace/spotify/backstage/node_modules/<EMAIL_ADDRESS>./.storybook/config.js ./.storybook/generated-entry.js (webpack)-hot-middleware/client.js?reload=true&quiet=true

Related issue #700
Related PR #701
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[x] All tests are passing yarn test
[ ] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[ ] Prettier run on changed files
[ ] Tests added for new functionality
[ ] Regression tests added for bug fixes

Created #718 😅

Thanks @Rugvip @freben !


Version migration error Deprecated API usage: No "GlobalWorkerOptions.workerSrc"

I'm migrating from pdfjs-dist 2.0.391 to 2.4.456.
The project is with AngularJs 1.6.9
Configuration:

Web browser: Chrome/87.0.4280.141
Operating system: Windows NT 10
PDF.js version: 2.0.391

import pdfjs from 'pdfjs-dist/build/pdf';
exclude: [       path.resolve(nodeModules, 'core-js'),       path.resolve(nodeModules, 'pdfjs-dist'),   ],
const configurarFactoriesBasicas = (app) => {     app.factory('pdfjs', () => pdfjs); };
erro: Deprecated API usage: No "GlobalWorkerOptions.workerSrc" specified.

You need to set workerSrc to the location of the worker file; see https://github.com/mozilla/pdf.js/blob/master/examples/learning/helloworld.html#L22-L26 for example.

You need to set workerSrc to the location of the worker file; see https://github.com/mozilla/pdf.js/blob/master/examples/learning/helloworld.html#L22-L26 for example.

I'm migrating from pdfjs-dist 2.0.391 to 2.4.456.

Please note that neither of those versions are supported any more; the latest releases can be found at https://github.com/mozilla/pdf.js/releases

I'm migrating from pdfjs-dist 2.0.391 to 2.4.456.

Please note that neither of those versions are supported any more; the latest releases can be found at https://github.com/mozilla/pdf.js/releases

@timvandermeij
A doubt, for version 2.7.570 it is necessary to do the same thing and it is compatible with AngulaJs 1.6.9?

You need to set workerSrc to the location of the worker file; see https://github.com/mozilla/pdf.js/blob/master/examples/learning/helloworld.html#L22-L26 for example.

@timvandermeij
A doubt, for version 2.7.570 it is necessary to do the same thing and it is compatible with AngulaJs 1.6.9?

You need to set workerSrc to the location of the worker file; see https://github.com/mozilla/pdf.js/blob/master/examples/learning/helloworld.html#L22-L26 for example.

This is for the library itself; we don't provide Angular integration nor do we officially support it.

This is for the library itself; we don't provide Angular integration nor do we officially support it.


README update

The link to the crate wasn't showing up for me (presumably, because of http)
Also cleaned up some stuff and merged sections, to make it smaller

bors r+


Create view for Building creation and update

For your information, part of this issue is being discussed in

#285.


fix: unsqueeze simp, re Yaël's comments on #11259

This PR reverts/simplifies some of the "squeeze simp" changes in #11259.
See #11259 for context.

This PR has been on the queue for a long time now, we should make a decision.
Yael: I gather you're against the simp only because it mentions too many low-level lemmas which might change. So how about avoiding a non-terminal simp by using the suffices new_goal by simp idiom?

I agree that reintroducing the nonterminal simp isn't right here. If any change is wanted here,

So how about avoiding a non-terminal simp by using the suffices new_goal by simp idiom?
sounds good to me.

Sure, we can try. I'm not yet convinced it's better than having rfl following simp, though


Added Footer

Added footer
Removed unused variables
Optimised a little
Removed previous errors.
Made footer mobile responsive

added collaborators page


Add SemiDynamic/Dynamic to the structural equality check

@vigoo I am not sure if this is still relevant. Please re-open if so! 🙏


Adding binomial distribution to Chainer

Adding binomial distribution to chainer.distributions.
I also created a test for this in chainer/tests/chainer_tests/distributions_tests/test_binomial.py
For some reason, the sample test within my test file gives a type casting issue. However, I verified this distribution is working by calling the distribution from another file and observing the result.
Ex.
dist = chainer.distributions.Binomial(n, p)
dist.sample_n(20) #this works as intended
If you can help me fix the test issue, it would be great, but it seems the distributions is working.

This seems to be a duplicate of https://github.com/chainer/chainer/pull/5160.

@hsezhiyan thanks for your PR, although it ended up being a duplicate. In the future, you could ask in our Slack channels for missing features. If you don't have an account already, there's a link in the README.md.


ESP32 gets no IP and returns no error if esp_netif_create_default_wifi_sta() called before esp_event_loop_create_default() (IDFGH-10321)

I am learning ESP32 and ESP-IDF. I was trying to make it connect to WiFi. I looked at the https://github.com/espressif/esp-idf/tree/master/examples/wifi/getting_started/station example and copied relevant method calls until things started working. In this code
void wifi_init_sta(void)
{
    s_wifi_event_group = xEventGroupCreate();

    ESP_ERROR_CHECK(esp_netif_init());

    ESP_ERROR_CHECK(esp_event_loop_create_default());
    esp_netif_create_default_wifi_sta();

    wifi_init_config_t cfg = WIFI_INIT_CONFIG_DEFAULT();
    ESP_ERROR_CHECK(esp_wifi_init(&cfg));

I skipped esp_event_loop_create_default() because I didn't know why I need it at first. At a later point I found out why and added this call somewhere before esp_event_handler_instance_register() calls. This worked, I got the WIFI_EVENT_STA_CONNECTED event in my event handler (again, derived from the example), but I never got the IP_EVENT_STA_GOT_IP nor the device ever asked for IP (checked on my router). No runtime errors or warning logs were generated that would hint this being the problem.
I think this should result in an error of sorts. It's not obvious there is a tight coupling (or dependency) between these two methods and the example doesn't mention this tight coupling either. This was very difficult to troubleshoot for a beginner like me, I spent a couple of hours on this.
The reason for this call order requirement is because esp_netif_create_default_wifi_sta() calls esp_event_handler_register() which as a result relies on already existing event loop created by the user.
Also, the esp_netif_create_default_wifi_sta documentation doesn't mention this requirement either.
The implementation looks like this:
/**
 * @brief User init default station (official API)
 */
esp_netif_t* esp_netif_create_default_wifi_sta(void)
{
    esp_netif_config_t cfg = ESP_NETIF_DEFAULT_WIFI_STA();
    esp_netif_t *netif = esp_netif_new(&cfg);
    assert(netif);
    esp_netif_attach_wifi_station(netif);
    esp_wifi_set_default_wifi_sta_handlers();
    return netif;
}

The esp_wifi_set_default_wifi_sta_handlers() call internally returns errors but this function doesn't handle them in any way. I think even assert() as seen in assert(netif) would be better than this. Please don't ignore errors.
An alternative could be the esp_wifi_set_default_wifi_sta_handlers function would create its own event loop so it wouldn't depend on the user's event loop.

Good point. Wi-Fi deinitialization has the same issue, where the order of function calls isn't clear.


Update RTD

The following RTD cells need to be re-run to remove the errors and update the tutorials:

https://covalent.readthedocs.io/en/latest/tutorials/machine_learning/mnist_classifier.html
https://covalent.readthedocs.io/en/latest/tutorials/machine_learning/classical_quantum_svm.html

error no longer exists


Dealing with lsp-auto-hover-enable and large info boxes

I use lsp-auto-hover-enable and it's generally good, except when I stumble upon info boxes that contain a lot of information.
In such cases it's possible that the info box will cover almost 100% of my editor, so I no longer see the context (the code where my cursor is).
Here's me navigating in a Go project, I'm pressing h to move left, and once I hit the big info box I try to cancel it with Esc:

I would like to brainstorm how this UX can be improved 🙂
One obvious idea would be to support Esc, so that if I press it, the info box should not reappear instantly, until I move cursor.
Another idea would be perhaps to limit the amount of text that can be displayed in the info box, cut it and add ellipsis in the end.
Maybe we could detect the cursor position and make sure the info box will never overlap with the cursor?

Right after I posted the message I learned about
lsp_hover_anchor and lsp_hover_max_lines parameters...
These two help already, but I would like kak-lsp do that for me if possible, in other words in the situation like on the picture below (with both options enabled), I would like kak-lsp to limit the hover information to as many lines as possible that will not overlap with my cursor:

Maybe this should be fixed on the kakoune side by handling info boxes that are too big by for example rendering only a portion of it, or making it scrollable.

Any fix for this？

@mawww I think a scrollable infobox would fix the above issue...
The only problem being, is it possible or not
If it isn't, I can start toying with kak-lsp to see if I can achieve a better hovering...

I think mawww/kakoune#4043 would be needed to do this (which seems like a good idea to me). I have no idea how hard that would be...
In the meantime, I think @maximbaz is right — Esc should  properly deal  with lsp-auto-hover-enable.
Is there any way to direct lsp-hover output to something other than an info box? Like to another buffer?


Add how-to guides for using async database clients

Complementary to #4 , we should write how-to guides explaining how to configure and use an async database client in order to perform database queries asynchronously in a Bocadillo app.
Note: this is a temporary but reasonable solution waiting for a sane async ORM to come around, like Tortoise.
Available async clients for popular databases are:

asyncpg: async PostgreSQL client
aiomysql: async version of PyMySQL
aiosqlite: async version of sqlite3

If possible and relevant, we should also provide snippets that abstract away common logic such as connecting to the database or handling cursors, so that app-side code looks something like:
from asyncdb import query  # <- snippet

async def get_products(req, res):
    results = await query('SELECT id, name, price FROM products;')
    # do something with `results`

Guidelines on contributing documentation have been added to CONTRIBUTING.md. Feel free to reach out to discuss any ideas!

@alin23 If you're interested in giving the asyncpg guide a go, I'd be more than happy to see what you come up with based on your past experience! 👍

Thanks @alin23.

I'd really like to see that PR merged ^_^

Just a note: keep in mind that Bocadillo is still in alpha, so I wouldn't advise using it in production (if that's what you're planning to do). Beyond possible API changes, there are still some important aspects that haven't been dealt with yet, such as security. 😉

Hi @alin23, have you got any chance to look at the asyncpg guide yet? :blush:

Nope, not yet. The company I'm working with is on a last-mile talk with investors and I have to make sure everything's on track here. So I won't have much time for open source work these weeks.
Sorry for overpromising, I'd really like to contribute to this but I don't have the time yet

I've just read more thoroughly through the Tortoise ORM docs and I thought — Tortoise may actually be sufficient for this how-to guide. At least, it's a more user-friendly advice than resorting to a raw client, and it will be very familiar to those who have used Django in the past.
I'm leaving a link to their Get started guide here for reference. Might be worth adapting it to show how to setup the DB, create a model and use it in some views.

It definitely looks much better than raw sql ^_^
I think we need a startup event that runs after the loop is initialized but before the server is started to allow initialization for this. Do we have anything like this?

We don't yet, but that's definitely doable (at worst wrapping around Starlette's event handling). Plus I've been thinking we'd need this at some point.
It looks like opening connections needs the startup event and cleaning up needs shutdown.
If you're feeling like it you can open a feature request for that? :)

Sure!

Awesome work! On 19th I'm getting back from a trip and I can hop on this db stuff.


[ODS-4831] Update Load Tools Documentation

@raghuramakrishna ODS-4398 added baseurl to smoke test and xml lookup utilities as well, can you extend the PR to indicate deprecation there as well?


Add configuration for AppVeyor CI

Minimal configuration for AppVeyor CI:

use ruby
disable default build and run test script
change default git checkout newlines
set ENV variables

Tests at AppVeyor are a) failing and b) the check here had to be manually triggered by me (via a curl request), but that is to be expected as quite some changes have to be implemented. But this PR enables us to enable b) and get future PRs automatically tested on Windows.


Store profession skill

Currently the skill:n:x conditional only works if the user has opened the profession window for the desired skill previously during the session. This is due to API limitations and is not ideal.
A workaround is to cache and store data in SavedVariables and fall back to those if the user has not yet opened the profession window.
To do:

Cache data

When the user opens their profession window
When skill is gained

Save cached data to SV
Rewrite the skill conditional to use cached data instead of API

Implemented in 2e6401c


GUI is needed for installing Rancher

What kind of request is this (question/bug/enhancement/feature request):
Enhancement
All installation descriptions that I found included manual UI steps for setting the initial password. It would be great to be able to e.g. provide this as an environment variable to the Docker container. The same holds for API Keys, where manual creation is necessary.
Environment information

Rancher 2 afaik all versions

See https://github.com/rancher/rancher/issues/16225, this has been discussed before.

Hey, thanks for the fast response, it would be great, if this would find its way into the manual.


test: add test for applying org.jsonschema2dataclass before java plugin

Thanks for merging. Would you please publish a release?

Thank you for your PRs :) I;m working on next release right now


FDO DB model improvements

Description
Change FDO DB model to allow future improvements and store more information.

When adding new OVs, this will create a disconnected FDO device.
Adding the ability to add initial user with multiple SSH keys.
Adding the ability to add PEM cert to the FDO device.

Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I run go fmt ./... to check that my code is properly formatted
[x] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #414 (d70f7a1) into main (6f67ce1) will increase coverage by 0.95%.
The diff coverage is 91.22%.

:exclamation: Current head d70f7a1 differs from pull request most recent head 09c6a92. Consider uploading reports for the commit 09c6a92 to get more accurate results

@@            Coverage Diff             @@
##             main     #414      +/-   ##
==========================================
+ Coverage   30.45%   31.41%   +0.95%
==========================================
  Files          32       32
  Lines        3201     3247      +46
==========================================
+ Hits          975     1020      +45
  Misses       2122     2122
- Partials      104      105       +1

Impacted Files
Coverage Δ

pkg/services/ownershipvoucher.go
96.24% <91.22%> (-3.76%)
:arrow_down:

pkg/routes/imagesets.go
35.11% <0.00%> (+1.25%)
:arrow_up:

pkg/services/updates.go
37.86% <0.00%> (+2.74%)
:arrow_up:

Continue to review full report at Codecov.

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


Release with .unitypackage

A little suggestion is to release with the .unitypackage file. It would benefit people who don't use UPM.

As this project has not been updated for a long time, here is one for ppl who need it. (github does not support .unitypackage so it's inside a zip)
NaughtyAttributes_2.1.4.unitypackage.zip
Also, you can check openUPM where there is a "Manual Installation" that you can install this project without using openupm command, with just a text editor


DevTools failed to load SourceMap: Could not load content for .../js/vue-step-wizard.common.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Everything works perfectly but this error doesn't go away.

@jekayode Can you put a screenshot of this error? Also can you try disabling Adblock or running the code into incognito mode to check if it still exists. Thanks

Thank you for your swift response @tushargugnani
This is in Google Chrome Incognito.

Regards

Thank you, It's a warning. This should not effect the plugin functionality.  I will check and revert on the fix for this.

Awesome.
Yes, just as you've noted, everything works perfectly as expected.
Thank you for the great job you are doing.
I am learning from your blog and I hope very soon, I will be able to contribute to this and other Open Source projects from the knowlege.


navbar example

Can you please add a navbar example with the collapse component to the documentation?
Thanks,
Joep

+1 For that

Wow! What a coincidence I'm also looking for that. +1.

Well, after relentless searching I found the example in ember-bootstrap/tests/dummy/app/templates/collapse.hbs. Enjoy @joepadmiraal and @zoamel!
It would be great if that is shown in the published documentation. But nonetheless, great job to kaliber5!

@plainsimple123 Thanks for pointing to that example, but that is not exactly what I am looking for.
I'm looking for an example which includes the navbar.
I currently have something like this, but it is not working correctly.
For example when the navbar is closed in a small window and the window is made larger, the navbar stays invisible.

  {{#bs-button class="navbar-toggle" toggle=true active=notCollapsed action="toggle"}}
    Toggle navigation

  {{/bs-button}}
  Ember.js example

{{#bs-collapse collapsed=collapsed}}

        {{#active-link}} {{#link-to 'groups'}}Groups{{/link-to}} {{/active-link}}
        {{#active-link}} {{#link-to 'students'}}Students{{/link-to}} {{/active-link}}

{{/bs-collapse}}

@plainsimple123 I plan to integrate the demo app from tests/dummy into the official documentation page (http://kaliber5.github.io/ember-bootstrap/), hopefully soon.

@joepadmiraal Can you please show me a code example of what you want to achieve using the original bootstrap.js? I am not sure I unterstand what your goal is...

@simonihmig Basicaly its just this navbar example from the official Bootstrap site.
When the browser window is made smaller the navbar will hide the buttons and show a button to collapse and expand the button list.

Hello, I would like to add to this topic my question:
Is there any example of ember-bootstrap with some side nav element menu?

I think joepadmiraal wants an example of how to target the bs-collapse component from the bs-button.
In bootstrap you would spilt a class via data-target attribute on the button. Off course ember doesn't work that way.
I'm interested in such a solution too...
and ps. very nice library this is... thanks a LOT

I figured it out;
https://gist.github.com/basz/99772922468152fb946d

Nice piece of work, @basz. If I understand your gist, you're using it to collapse a sidebar, not the kind of responsive alternate menu presentation shown in the Bootstrap navbar example that @joepadmiraal cited.
Digging into it, I agree that the cross-component signaling isn't very Ember-y and would require a different approach. I also found that using markup or componentization to group the elements needing collapse breaks ember-bootstrap's strong assumptions about the relationships between child and parent components (as detected by nearestOfType) in a way that will requires some redesign or other accommodation.

I've started adding bs-navbar functionality in https://github.com/srvance/ember-bootstrap/commit/7763bf2690d265019bff48c049863bec26faf8c6.

This has been implemented by #123 and will be released as 0.9.0 soon. All credits go to @srvance!


Loggable: Class LogEntry not found

Hello!
In my app developed with Symfony 4.2 and API Platform,
I install DoctrineExtensions bundle to use Loggable extension,
and I follow instructions in Symfony documentation and Loggable extension.
When I only use one EntityManager, everything works.
But I wanna move the LogEntry entity table to another database.
So I created a second EntityManager as described in the Symfony doc.
After, I modify in my app an entity that has the annotation @Gedmo\Loggable
and I get this error:
The class 'Gedmo\Loggable\Entity\LogEntry' was not found in the chain configured namespaces 'App\Entity'.
My config/packages/doctrine.yaml file:
parameters:
    env(DATABASE_URL): ''

doctrine:
    dbal:
        connections:
            default:
                driver: 'pdo_mysql'
                server_version: '%env(resolve:SERVER_VERSION)%'
                charset: utf8mb4
                default_table_options:
                    charset: utf8mb4
                    collate: utf8mb4_unicode_ci
                url: '%env(resolve:DATABASE_URL)%'
            log:
                driver: 'pdo_mysql'
                server_version: '%env(resolve:SERVER_VERSION)%'
                charset: utf8mb4
                default_table_options:
                    charset: utf8mb4
                    collate: utf8mb4_unicode_ci
                url: '%env(resolve:LOG_DATABASE_URL)%'
    orm:
        auto_generate_proxy_classes: '%kernel.debug%'
        entity_managers:
            default:
                naming_strategy: doctrine.orm.naming_strategy.underscore
                mappings:
                    App:
                        is_bundle: false
                        type: annotation
                        dir: '%kernel.project_dir%/src/Entity'
                        prefix: 'App\Entity'
            log:
                naming_strategy: doctrine.orm.naming_strategy.underscore
                connection: log
                mappings:
                    gedmo_loggable:
                        is_bundle: false
                        type: annotation
                        dir: '%kernel.project_dir%/vendor/gedmo/doctrine-extensions/lib/Gedmo/Loggable/Entity'
                        prefix: 'Gedmo\Loggable\Entity'
                        alias: GedmoLoggable

Example of Entity that I want to watch:
<?php
namespace App\Entity;

...
use Gedmo\Mapping\Annotation as Gedmo;
...

/**
 * @ApiResource
 * @Gedmo\Loggable
 * @ORM\Table(name="patients")
 */
class Patient
{
    /**
     * @ORM\Id
     * @ORM\Column(type="guid", unique=true)
     * @ORM\GeneratedValue(strategy="UUID")
     * @Assert\Uuid
     */
    private $id;

    /**
     * @ORM\Column(length=50)
     * @Assert\NotBlank()
     * @Assert\Length(max=50)
     * @Gedmo\Versioned
     */
    public $familyName;

    /**
     * @ORM\Column(length=50)
     * @Assert\NotBlank()
     * @Assert\Length(max=50)
     * @Gedmo\Versioned
     */
    public $firstName;

    ...
}

I tried to add and remove some properties in the doctrine.yaml but I always get the same error...
Thanks for your time.

In fact, the problem is it's the default entity manager that is used in the bundle. It should be appreciated that we could specify the Entity Manager to use with the Loggable Bundle.
It's the same problem in #366.

well, the way the extensions work is that they need to have the LogEntry entity mapped for the same entity manager than the one managing the entities on which you want the loggable behavior. That's not something this bundle can change.
The extensions are maintained at https://github.com/Atlantic18/DoctrineExtensions, not in this repo (which only configures them in a Symfony project). If you want to request a feature to allow managing the LogEntry entities with a separate entity manager, that's where it needs to be requested.


Testing to prepare for screen recording

Purpose
Testing in order to record the pipeline working
Proposed Change
changing the active cases box from blue to red
Checklist

[x ] change color

[ ] record pipeline

Additional
Learning

I'm going to do this again in the morning and record it, this was just for me to test.


On hover stop autoplay mode issue

Hello
I have used this plugin for vertically slide on my website but need to stop slide on hover how i can stop this with autoplayDisableOnInteraction:false because i want start and stop slider on hover

For example with jQuery:
---js
var swiper = new Swiper('.swiper-container', {
// ...
});
$('.swiper-container').on('hover', function(){
swiper.stopAutoplay();
});

$(".swiper-container").hover(function(){
swiper.stopAutoplay();
}, function(){
swiper.startAutoplay();
});


Error with api-url: "Maximum call stack size exceeded"

Hi to everyone, I'm using with vuetable2 and Laravel 5.4 and I have a problem with api-url calls. From the official example https://github.com/ratiw/vuetable-2-with-laravel-5.4 I tried to change a little the table, changing the columns and the api-url. In the api-url I put a route that return a json.
When I test the table I receive the error:
app.a7be721….js:98292 Uncaught RangeError: Maximum call stack size exceeded
at VueComponent.Vue._render (app.a7be721….js:98292)
at VueComponent.updateComponent (app.a7be721….js:96826)
at Watcher.get (app.a7be721….js:97165)
at new Watcher (app.a7be721….js:97148)
at mountComponent (app.a7be721….js:96830)
at VueComponent.Vue$3.$mount (app.a7be721….js:101957)
at VueComponent.Vue$3.$mount (app.a7be721….js:104056)
at init (app.a7be721….js:97745)
at createComponent (app.a7be721….js:99288)
at createElm (app.a7be721….js:99231)
Does anyone can help me? From the official example I have only change columns and api-url parameter.
Thank you very much,

@ErnstShackleton There might be a loop somewhere in your code that causes the problem. Since, you're using a compiled version of the script, it's very hard to identify which as the error message is not very helpful.

@ratiw Thanks ratiw!


⚠ Bofrost.fr has degraded performance

In 0f0ea4b, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1902 ms

Resolved: Bofrost.fr performance has improved in a3fb443 after 26 minutes.


⚠ Minecraft has degraded performance

In 925a6b5, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1137 ms

Resolved: Minecraft performance has improved in f939f8e.


Plugin name completion is failed in Neovim

In Neovim, E117 is occurred when try to complete the plugin name from the suggestions.
Neovim does not have matchfuzzy() currently...
ref: https://github.com/neovim/neovim/pull/12995

Thank you. I fixed.

Thank you for the quick response ✨


rough draft of readme

note -- I will submit the PR with the new files that this references now
(PR https://github.com/clulab/eidos/pull/90)

"small set of rules" => "grammar"

Also, good plan doing this PR separate from code changes!

And FWIW .\shell also works on certain machines.

If RAPShell => EidosShell, is there any problem leaving it in agro.demo, or should that be changed as well?

We shouldn’t use the “agro” name anywhere in the software.

On Feb 18, 2018, at 7:47 PM, Keith Alcock<EMAIL_ADDRESS>wrote:
If RAPShell => EidosShell, is there any problem leaving it in agro.demo, or should that be changed as well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes, I think we should move it, not just rename agro.  The actual directory
separation we have is largely meaningless. Keith, given that you were
thinking some subprojects I was hoping you steer me to repo goodness and
truth... or at least suggest an appropriate directory structure. :)
On Sun, Feb 18, 2018 at 7:49 PM Mihai Surdeanu<EMAIL_ADDRESS>wrote:

We shouldn’t use the “agro” name anywhere in the software.

On Feb 18, 2018, at 7:47 PM, Keith Alcock<EMAIL_ADDRESS>wrote:
If RAPShell => EidosShell, is there any problem leaving it in agro.demo,
or should that be changed as well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/89#issuecomment-366576540, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFIniVVdntd0TqMHg8GNCTpV3g0kPQl-ks5tWOEOgaJpZM4SJ5U6
.

In something just submitted, I renamed it to eidos.demo and decided it wasn't too bad to have these Apps packaged in the same jar.  They provide examples of how to use the API.   I'm not sure about having these outside the org.clulab.wm namespace, however. and that goes for Utils.  However, one step at a time.
We might want to merge this one even though not quite complete in order to avoid merge conflicts.

@kwalcock re: And FWIW .\shell also works on certain machines. -- I am not quite sure what you mean by this and how I should address it

I was vague.  It is .\shell for windows.  There is a shell.bat to take care of this.  Windows users will figure it out, so it may not be worth mentioning.  Are you ready to merge?  It's more perfect than what we have.

I think it's ready to merge -- def better than what we have and @Mihai I
can continue to make any changes you want....?
On Mon, Feb 19, 2018 at 1:56 PM, Keith Alcock<EMAIL_ADDRESS>wrote:

I was vague. It is .\shell for windows. There is a shell.bat to take care
of this. Windows users will figure it out, so it may not be worth
mentioning. Are you ready to merge? It's more perfect than what we have.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/89#issuecomment-366800793, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFIniZoB-k7SMymSxteMU-7En54DNLWpks5tWd_4gaJpZM4SJ5U6
.

Yep, please merge.
On Mon, Feb 19, 2018 at 2:50 PM, bsharpataz<EMAIL_ADDRESS>wrote:

I think it's ready to merge -- def better than what we have and @Mihai I
can continue to make any changes you want....?
On Mon, Feb 19, 2018 at 1:56 PM, Keith Alcock<EMAIL_ADDRESS>wrote:

I was vague. It is .\shell for windows. There is a shell.bat to take care
of this. Windows users will figure it out, so it may not be worth
mentioning. Are you ready to merge? It's more perfect than what we have.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/89#issuecomment-366800793, or
mute
the thread
<https://github.com/notifications/unsubscribe-
auth/AFIniZoB-k7SMymSxteMU-7En54DNLWpks5tWd_4gaJpZM4SJ5U6>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/pull/89#issuecomment-366811044, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABH-ziE3QYegMbVm84jbYSKXkW0eQEHGks5tWeycgaJpZM4SJ5U6
.


Add profile data

Added my profile data to UserData.ts

Added my profile data to UserData.ts

LGTM🚀


PatternView

When I click in one point Pattern Activity will crash. How can I fix that?

 Caused by: java.lang.IndexOutOfBoundsException: Index: 2, Size: 2
    at java.util.ArrayList.get(ArrayList.java:437)
    at com.kevalpatel.passcodeview.authenticator.PasscodeViewPatternAuthenticator.isValidPattern(PasscodeViewPatternAuthenticator.java:45)

Hi Patel can you please help me out with this bug and also indicator by default is not displayed , after pin entered it is displayed, but in the image in the blog the indicators are present by default with stroke. Please help me out.
 Caused by: java.lang.IndexOutOfBoundsException: Index: 2, Size: 2
    at java.util.ArrayList.get(ArrayList.java:437)
    at com.kevalpatel.passcodeview.authenticator.PasscodeViewPatternAuthenticator.isValidPattern(PasscodeViewPatternAuthenticator.java:45)


Update licensing requirement.

As per MC533652
Updated May 8, 2023: While in Public Preview, Avatars for Microsoft Teams was supported for all SKUs. However, at General Availability, Avatars for Microsoft Teams will only be supported for the following SKUs: Microsoft 365 Enterprise E3, Microsoft 365 Enterprise E5, Microsoft 365 Business Standard, Microsoft 365 Business Premium or Teams Premium.
Current documentation does not include Teams Premium.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 122d9ead-09d3-f605-1bfb-6ae0fce81636
Version Independent ID: 122d9ead-09d3-f605-1bfb-6ae0fce81636
Content: Set up avatars for Microsoft Teams - Microsoft Teams
Content Source: Teams/meeting-avatars.md
Service: msteams
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

Information is now in the article.


"KeyBase is not implemented yet" in version 0.9.0

I'm trying to directly instantiate a ndb.Key() to use with my Entity object.
However looking at the source code, this instantiates a KeyBase class which is not yet implemented.
I'm not sure if you have a different version of this class.
raise NotImplementedError('KeyBase class is not set up (yet)') NotImplementedError: KeyBase class is not set up (yet)
Instantiated from KeyClass line 49.

Yes. Basically I didnt't want to have a hard depency to google.cloud.datastore and because of problems when loading google.cloud.datastore which itself load grpc in a forking environment I decided to do runtime patching via:

import ndb_orm as ndb
ndb.enable_use_with_gcd(client.project)

This should add the missing class from google.cloud.datastore.

Oh yea!!! My bad!!!. I missed the "enabling" in my test code. Thanks


Ignore line anchor links with leading zeroes (#21728)

Backport #21728
Fixes: https://github.com/go-gitea/gitea/issues/21722

It passed the CI and is up to date, can be merged.


implement exponentiation for ITensors with QNs

One thing about this implementation that I'm not sure about-
currently it will not support the scenario :
i1 = Index([QN(0)=>1,QN(1)=>2],"i1")
i2 = Index([QN(0)=>1,QN(1)=>2],"i2")
A = randomITensor(QN(),i1,i2,dag(i1)', dag(i2)')
Lis = IndexSet(i1,dag(i1)')
Ris = IndexSet(i2,dag(i2)')
exp(A,Lis,Ris )

Because the order 2 block-sparse tensor with combined indices AC= A*combiner(Lis...)*combiner(Ris...) will not be block diagonal.
But since AC still has zero flux it is my understanding (which might be incorrect) that it should be possible to exponentiate it block by block, preserving the block structure, and the reason it is not represented as a block diagonal tensor is because both indices  of AC have an  (arbitrary?) OUT direction.
It is very possible that this scenario has no use-case, but it just made me wonder whether I made some mistake in the implementation and it should be also supported.

Hi Ori,
Thanks for the contribution, this will be useful to have.
The case you bring up is a good one, and I realized that it is also a problem for the eigen function right now:
i1 = Index([QN(0)=>1,QN(1)=>2],"i1")
i2 = Index([QN(0)=>1,QN(1)=>2],"i2")
A = randomITensor(i1, dag(i1)', dag(i2), i2')
eigen(A, (i1,i1'), (i2,i2'))

which leads to the same kind of error about requiring block diagonal matrices. This is a very important case to handle for both eigen and exp, since operators like this with mixed arrows show up naturally in MPS transfer matrices:
i_1  ---<--------<----- i_2
          |  T |
i_1' --->-------->----- i_2'

(for an infinite MPS with a one-site unit cell A and indices (i_1, s, dag(i_2)), the transfer matrix T is A * dag(prime(A, not(s)))).
There are a few things here:

Right now, the combiner is a bit arbitrary about the direction it gives to the combined Index. If the inputs to combiner are all Out or all In, the combined Index will be Out or In respectively. If the arrows of the input indices are mixed, then the combined Index will arbitrarily be Out. For applications like this, I can add a keyword argument to combiner that lets the user choose the direction of the combined Index. That should fix the problem for both eigen and exp, since they can specify the combiners should have opposite directions and then the matrices will be block diagonal. (Possibly combiner could pick the direction based on the first input Index, that could also solve this particular problem.)
Like in eigen, we should check that pairs of indices (i.e. (Linds[n],Rinds[n])) have the same spaces and opposite directions. This would define them as proper maps between the same spaces. I believe this restriction makes sense given the definition of the matrix exponential in terms of a power series. See here for checks we should add.
For functions like this, we are allowing users to pass indices with any directions (many ITensor functions don't require input index directions to be correct, like eigen, svd, replaceinds, etc.). In eigen, I explicitly just fix the directions to the correct ones here.
I think it would be nice to design this function like eigen, in two layers. The inner layer here explicitly accepts two collections of indices. Then, the outer layer here wraps the inner layer, and assumes the left set of indices are primed and the right set of indices are unprimed. That convention is used there since the ITensor is seen as a map from the unprimed right indices to the primed left indices, and that function is finding right eigenvectors. I think it would be nice to use the same convention for exp (especially considering that the matrix exponential is very related to an eigendecomposition, since it can be computed using an eigendecomposition).

So for now, could you please address (2), (3) and (4)? I can fix (1) for both eigen and exp in a different PR.
-Matt

Yes, that is true, there are definitely more general inputs that would allow for proper maps between isomorphic spaces, and we could consider allowing more general inputs in the future. Part of the motivation is the Hermitian case of exp (and eigen), where not only the size of the space matters but also the ordering of the local Hilbert spaces. For example, for an ITensor with indices (i', j', dag(i), dag(j)), it may only be Hermitian if it is considered as a map from (i, j) -> (i', j'), but not (i, j) -> (j', i'). That becomes more difficult to reason about (for the user and for us) if the function doesn't restrict to pairs of indices of equal spaces and opposite arrows. Just to illustrate why it gets subtle:
julia> i = Index(2, "i");

julia> j = Index(2, "j");

julia> A = randomITensor(i', j', dag(i), dag(j));

julia> A += swapprime(dag(A), 0, 1);

julia> Cij = combiner(i, j);

julia> Cji = combiner(j, i);

julia> @show A*Cij*Cij';
A * Cij * Cij' = ITensor ord=2
Dim 1: (dim=4|id=457|"CMB,Link")
Dim 2: (dim=4|id=457|"CMB,Link")'
NDTensors.Dense{Float64,Array{Float64,1}}
 4×4
 -1.0625949643764634   1.4012742994320175  -1.0021983667374323   -2.4843572644996805
  1.4012742994320175  -1.280522473293159    2.9234750385583164   -0.5344858357713442
 -1.0021983667374323   2.9234750385583164  -0.11195568258709207  -1.3774283944554442
 -2.4843572644996805  -0.5344858357713442  -1.3774283944554442    0.9449780471267247

julia> @show A*Cji*Cji';
A * Cji * Cji' = ITensor ord=2
Dim 1: (dim=4|id=828|"CMB,Link")
Dim 2: (dim=4|id=828|"CMB,Link")'
NDTensors.Dense{Float64,Array{Float64,1}}
 4×4
 -1.0625949643764634  -1.0021983667374323    1.4012742994320175  -2.4843572644996805
 -1.0021983667374323  -0.11195568258709207   2.9234750385583164  -1.3774283944554442
  1.4012742994320175   2.9234750385583164   -1.280522473293159   -0.5344858357713442
 -2.4843572644996805  -1.3774283944554442   -0.5344858357713442   0.9449780471267247

julia> @show A*Cji*Cij';
A * Cji * Cij' = ITensor ord=2
Dim 1: (dim=4|id=828|"CMB,Link")
Dim 2: (dim=4|id=457|"CMB,Link")'
NDTensors.Dense{Float64,Array{Float64,1}}
 4×4
 -1.0625949643764634   1.4012742994320175  -1.0021983667374323   -2.4843572644996805
 -1.0021983667374323   2.9234750385583164  -0.11195568258709207  -1.3774283944554442
  1.4012742994320175  -1.280522473293159    2.9234750385583164   -0.5344858357713442
 -2.4843572644996805  -0.5344858357713442  -1.3774283944554442    0.9449780471267247

Additionally, at least for eigen, it is helpful to limit the accepted input to pairs of indices because when the eigenvector is applied to the ITensor operator on the right, it will result in a new vector scaled by the eigenvalue with the same set of indices (though maybe primed, or however else the Index labels might get modified). One could argue that a similar reasoning should apply to exp, where the ITensor operator would be used in a Taylor series expansion and must be multiplied by itself over and over.
More practically, if we allowed more general inputs (like maps from 2 indices to 1), for QN ITensors it is not guaranteed that when the two indices are combined into 1 that the combiner would combine them such that the QNs are ordered in the same way as the other Index. For example, for an ITensor mapping (i,j) -> k, when (i,j) are combined into c in general the QNs may be ordered differently than the QNs of k. We could try to fix cases like that, but it starts to lead to a rabbithole where allowing more general inputs can lead to much more complicated code, with possibly little payoff.

Also, to give some context, the C++ version of ITensor only allows pairs of primed and unprimed indices for functions like this, and that had been sufficient for nearly every use case. These versions in the Julia version are already significantly more general by allowing any pairs of indices, not just primed and unprimed pairs.

Thanks for taking the time to clarify Matt.
This makes sense (I was mainly just wondering if I'm not understanding something mathematically about QN tensors or about how they are implemented when asking this), and it's definitely good enough for my use case where I just want to exponentiate few-site operators :)

I updated the PR adding the checks similar to eigen + adding the method allowing exponentiation without specifying the indices.
I tried to clarify the restrictions on the indices in the docstring, not sure it is clear enough.

Looks great, thanks again for your work on this! I'll start working on the new combiner feature so we can fix the issue you brought up in your first comment.


[GHSA-65fx-pmw6-rcfm] An issue was discovered in Python 3.11 through 3.11.4. If...

Updates

Affected products
References
Source code location
Summary

Comments
Add patch links and other informations related to CVE-2023-41105.

Hey @sunSUNQ, the python interpreter is out of scope for us. We only index on packages in our supported ecosystems
https://github.com/github/advisory-database/?tab=readme-ov-file#supported-ecosystems


ModuleNotFoundError: No module named 'loss_classes' how to resolve this. Please help

Traceback (most recent call last):
File "main.py", line 4, in
from train import train_emotic
File "/content/gdrive/MyDrive/Deep learning Models/emotic-master/emotic-master/train.py", line 16, in
from loss_classes import DiscreteLoss, ContinuousLoss_SL1, ContinuousLoss_L2
ModuleNotFoundError: No module named 'loss_classes'

Could you please let me know how did you resolve this error?


[System tests] deposit liquidated outside Coverage Pools

This pull request adds a system test for a scenario where the deposit is liquidated outside Coverage Pools.
There are two test cases:

auction is partially filled (deposit status is checked by Coverage Pools in onAuctionPartiallyFilled)
auction is fully filled (deposit status is checked by the Deposit contract itself in function purchaseSignerBondsAtAuction)

It also removes an integration test for the same scenario (scenarios involving handling tBTC deposits are better tested using system tests).
Refs https://github.com/keep-network/coverage-pools/issues/83

Please note the changes introduced by https://github.com/keep-network/coverage-pools/pull/88 before merging. SignerBondsEscrow has been renamed.

👀


(Enhancement) Make part of lan switch is actually an IP setting

On ctapp.io i can set up a wireless network to use the AP as DHCP server (coova chilli), use lan for dhcp services or i can disable both switches.
for a better and easier understandig it would help to move the "make part of lan" switch to the IP settings  because they clearly determine each other [and optionaly remove that repeater switch which actually hides the wds bridge option as described in your documentation http://docs.cucumberwifi.io/article/157-creating-a-wireless-bridge]

maybe these switches could be summed up to a radio button saying:
DHCP: (on/ off / use lan) but thats optional for my suggested enhancement

Closing. Not going to implement.


infinite loop in nox -s docs-live

on current main, if I do this:
rm -r .nox/
rm -r node_modules/
rm package-lock.json
mamba env create -n pst python
conda activate pst
pip install sphinx-theme-builder[cli]
pip install -e .[dev]

I would expect nox -s docs-live to work, but it does not: it runs to completion and pops open the browser window and then immediately starts rebuilding as if a file had changed. It continues rebuilding indefinitely as soon as the prior (re-)build completes. Even if I were ok with all that needless rebuilding happening in the background, it makes the live site hard to use because it gets a reload signal frequently, and the page reload is slow (reason unknown but presumably related, since it's a local site).
(NB: this was happening before I recreated the dev env / deleted all the node modules and nox envs; I recreated the dev env from scratch just to make sure it wasn't a fluke).

as @gabalafou noted here this appears to be caused by the language translation files changing. cc @jpmckinney any insight into how to prevent this?

Ignore changes to those files as far as rebuilds go. I’m not familiar with the nox command but if it’s using sphinx-autobuild then there is an option to ignore


mavros problem?

When I tried to catkin build as the instruction, I had the following error messages:
Errors     << mavros:make /home/htkim/catkin_ws/logs/mavros/build.make.000.log
In file included from /home/htkim/catkin_ws/src/mavros/mavros/src/lib/enum_sensor_orientation.cpp:17:0:
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:70:40: error: ‘std::__cxx11::string mavros::utils::to_string’ redeclared as different kind of symbol
 std::string to_string(mavlink::common::MAV_AUTOPILOT e);
                                        ^~~~~~~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:68:13: note: previous declaration ‘std::__cxx11::string mavros::utils::to_string(mavlink::common::MAV_SENSOR_ORIENTATION)’
 std::string to_string(mavlink::common::MAV_SENSOR_ORIENTATION e);
             ^~~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:70:40: error: ‘MAV_AUTOPILOT’ is not a member of ‘mavlink::common’
 std::string to_string(mavlink::common::MAV_AUTOPILOT e);
                                        ^~~~~~~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:70:40: note: suggested alternative:
In file included from /home/htkim/catkin_ws/devel/include/mavlink/v2.0/common/common.hpp:2290:0,
                 from /home/htkim/catkin_ws/src/mavros/libmavconn/include/mavconn/mavlink_dialect.h:26,
                 from /home/htkim/catkin_ws/src/mavros/mavros_msgs/include/mavros_msgs/mavlink_convert.h:18,
                 from /home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:22,
                 from /home/htkim/catkin_ws/src/mavros/mavros/src/lib/enum_sensor_orientation.cpp:17:
/home/htkim/catkin_ws/devel/include/mavlink/v2.0/common/../minimal/minimal.hpp:34:12: note:   ‘mavlink::minimal::MAV_AUTOPILOT’
 enum class MAV_AUTOPILOT : uint8_t
            ^~~~~~~~~~~~~
In file included from /home/htkim/catkin_ws/src/mavros/mavros/src/lib/enum_sensor_orientation.cpp:17:0:
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:71:40: error: ‘std::__cxx11::string mavros::utils::to_string’ redeclared as different kind of symbol
 std::string to_string(mavlink::common::MAV_TYPE e);
                                        ^~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:68:13: note: previous declaration ‘std::__cxx11::string mavros::utils::to_string(mavlink::common::MAV_SENSOR_ORIENTATION)’
 std::string to_string(mavlink::common::MAV_SENSOR_ORIENTATION e);
             ^~~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:71:40: error: ‘MAV_TYPE’ is not a member of ‘mavlink::common’
 std::string to_string(mavlink::common::MAV_TYPE e);
                                        ^~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:71:40: note: suggested alternative: ‘AIS_TYPE’
 std::string to_string(mavlink::common::MAV_TYPE e);
                                        ^~~~~~~~
                                        AIS_TYPE
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:72:40: error: ‘std::__cxx11::string mavros::utils::to_string’ redeclared as different kind of symbol
 std::string to_string(mavlink::common::MAV_STATE e);
                                        ^~~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:68:13: note: previous declaration ‘std::__cxx11::string mavros::utils::to_string(mavlink::common::MAV_SENSOR_ORIENTATION)’
 std::string to_string(mavlink::common::MAV_SENSOR_ORIENTATION e);
             ^~~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:72:40: error: ‘MAV_STATE’ is not a member of ‘mavlink::common’
 std::string to_string(mavlink::common::MAV_STATE e);
                                        ^~~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:72:40: note: suggested alternative: ‘MAV_FRAME’
 std::string to_string(mavlink::common::MAV_STATE e);
                                        ^~~~~~~~~
                                        MAV_FRAME
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:73:40: error: ‘std::__cxx11::string mavros::utils::to_string’ redeclared as different kind of symbol
 std::string to_string(mavlink::common::MAV_COMPONENT e);
                                        ^~~~~~~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:68:13: note: previous declaration ‘std::__cxx11::string mavros::utils::to_string(mavlink::common::MAV_SENSOR_ORIENTATION)’
 std::string to_string(mavlink::common::MAV_SENSOR_ORIENTATION e);
             ^~~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:73:40: error: ‘MAV_COMPONENT’ is not a member of ‘mavlink::common’
 std::string to_string(mavlink::common::MAV_COMPONENT e);
                                        ^~~~~~~~~~~~~
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:73:40: note: suggested alternative: ‘MAV_MODE’
 std::string to_string(mavlink::common::MAV_COMPONENT e);
                                        ^~~~~~~~~~~~~
                                        MAV_MODE
/home/htkim/catkin_ws/src/mavros/mavros/include/mavros/utils.h:114:18: error: ‘MAV_TYPE’ in namespace ‘mavlink::common’ does not name a type
 mavlink::common::MAV_TYPE mav_type_from_str(const std::string &mav_type);
                  ^~~~~~~~
make[2]: *** [CMakeFiles/mavros.dir/src/lib/enum_sensor_orientation.cpp.o] Error 1
make[1]: *** [CMakeFiles/mavros.dir/all] Error 2
make: *** [all] Error 2

You seem to have the wrong mavlink/mavros version. Which instructions are you following to install mavros?


v1.47.6

Description
Upgrade from <IP_ADDRESS> to 1.47.6
Types of changes

✅ Chore

@saterus metabase support seems to indicate that we should be able to do this?  I am doubtful, but it's been too long, so I don't recall what the errors was originally.  So, I'd like to merge this and then try it in our metabase staging enviornment.


node_link_data() got an unexpected keyword argument 'edges'

I getting below when it is going to save the JSON file,
Processing file [162/162]: scrap_job/jobs/web_crawl_job.pys.pyyy.pyyyn.pyys.py.pypy

Completed processing 162 files across 159 directories

Saving graph...

Error: node_link_data() got an unexpected keyword argument 'edges'

Done.

Solid & safe contribution, thank you!

Sorry to step in to a closed topic, but this actually caused an issue with my setup (first time running it) - I'm on windows.  It appeared to run successfully (parsed 60+ files) and then output an error -  "Error saving graph: node_link_data() got an unexpected keyword argument 'edges'" and then it quit after a timeout.
After I found this thread, I went into the file and removed the 'edges="links"' argument and it ran without issue.
I haven't dug much farther but wanted to pass this on.  Thanks for working on this, looking forward to trying it out!

Thank you for taking the time to share this. Will recreate the bug and fix!


Link boringocsp lib to unit tests

I'm not sure why only this test is affected, but I saw a link issue when I run make check where I build ATS with boringocsp library.

@maskit This has a trivial merge conflict on 9.2.1, I can fix it easily, unless you want to make a 9.2.x PR.

Removed from 9.2.x project as we are dropping ocspboring support and the library has never been open-sourced.


Loadpoint: make fast mode obey vehicle phase limits

fix #14403

@GrimmiMeloni why should we do this? There's no benefit. The vehicle phases settings is only a hint. Imho it does not make sense to treat it as a restriction. And even if it were I'd still consider fast mode exactly that. If vehicle is capable of 1p only it will only charge 1p, regardless if we set 3p.

No problem. Lets close here.


How to use with Vietnamese?

My suggestions array is:
 {
  "suggestions": [
    "du lịch Việt Nam",
    "lịch trình du lịch Việt Nam",
    "phượt Việt Nam",
    "Việt Nam",
    "check-in Việt Nam",
    "hạ long việt nam",
    "hoa đào ở việt nam",
    "mùa hoa gạo việt nam"
  ]
}

When I typed: "Việt Nam" or "việt nam", it worked, it showed a list of tags
However when I typed "Viet Nam" or "viet nam", it didn't work, not show a list of tags.
How can i fix it for Vietnamese.
Thank you so much

Sorry for the very late reply. Currently the suggestions filtering does not do such thing. If you want to do custom check while filtering the suggestions, you can check this option and try writing some custom condition in that callback function.
https://github.com/amsify42/jquery.amsify.suggestags#suggestmatch

I hope the last message helped you find the solution for your problem. I am closing the issue, if you think the problem is not solved you can reopen it.


Anongost 0.16 - Reborn, from scratch.

Seems better to upgrade source while at it. Then we can also get rid of some old trash :)

As a note regarding this and your other PR (and I know both have been open for a long time), any changes/PRs should be atomic and small, this PR is just too big for anyone to review (even github won’t show all the changes) plus the fact that unit tests doesn’t work and there is no way of knowing the stability of the changes means they will never get merged
Instead you should split functional additions, file rebranding and documentation changes on their own smaller PRs
Cheers!


classPrefix and tablePrefix configuration properties

Reviewing a configuration file, I'm wondering if it's time to remove classPrefix and tablePrefix properties.

classPrefix was introduced years ago, when Propel was distributed as Pear package. In fact, it's a sort of old style Pear namespace, when PHP (3 and 4 versions) didn's support them. Since Propel2 is distributed via Composer and it adheres to PSRs, the code base and generated classes support namespaces. So, imho there's no need of this option.
`tablePrefix' is an old style way to put different projects tables in one single database. Some years ago, host providers often included only one database in their plans, so table prefix was a forced choice in many cases. Today, the cheapest host plan offers almost 5 databases so, imho we could remove this property without problems.

From the code point of view, we can reduce a bit of complexity, by removing several if statements (actually, not many).
If you're agree, I can prepare a pull request.

We could deprecate those for the time being, with or without throwing a notice, and remove it then in the next major release?
We do have one upcoming now the next days, and maybe we shouldn't hard-remove anything that quickly.

We could deprecate those for the time being, with or without throwing a notice, and remove it then in the next major release?
We do have one upcoming now the next days, and maybe we shouldn't hard-remove anything that quickly.

I'm closing this issue by now: I'll remember it near next major release 😄

I'm closing this issue by now: I'll remember it near next major release 😄

We can still move forward here.
I just hinted that maybe deprecation and then removing is better than removing it right away.

We can still move forward here.
I just hinted that maybe deprecation and then removing is better than removing it right away.


Does not work when the user has more than 1 device

I does not allow to select an specific device. It would be a really nice feature

Hmm, I have only one device, so I never tested this 😬
I will refactor for handle, multiple devices.


add a default instance type for GCP

mirror what we do for AWS and provide a default instance type for GCP when creating a clusterDeployment

/test gcp-e2e-test

/test e2e-gcp

It is not sufficient to fill out the field when using hiveutl create-cluster. If the field needs to be filled out for Hive to work, then the field needs to be made mandatory. Otherwise a user creating a clusterdeployment may created an accepted clusterdeployment that will fail once the cluster has been installed.

/close
we'll use the installer's functions to fill in defaults for the installconfig


Update tutorials for qiskit-ibm-provider

Scope
Work on tutorials that explain how to get started with qiskit-ibm-provider.
Starting points:

https://github.com/Qiskit/qiskit-ibm-runtime/tree/main/docs/tutorials and
https://github.com/Qiskit/qiskit-ibm-provider/tree/main/docs/tutorials

Acceptance Criteria

Most important use-cases are identified and covered via tutorials
Tutorials available at https://github.com/Qiskit/qiskit-ibm-provider/tree/main/docs/tutorials work

@kt474 is that something you'd be interested to start with? Now that the major rework for https://github.com/Qiskit/qiskit-ibm-provider/issues/237 is done and runtime and experiment service have been removed from qiskit-ibm-provider, I believe it is a good time to write a tutorial from a user's perspective to verify that everything works as expected.
Thoughts, @rathishcholarajan?

@kt474 is that something you'd be interested to start with? Now that the major rework for #237 is done and runtime and experiment service have been removed from qiskit-ibm-provider, I believe it is a good time to write a tutorial from a user's perspective to verify that everything works as expected.
Thoughts, @rathishcholarajan?

Yeah I think updating tutorials is definitely a necessary step after we get all the tests working - so when that's done I'd be happy to work on this

Added this to the "Provider 0.1" release because I think this is an important part that we need prior to releasing 0.1


Bugfix - FlatList keyExtractor for multicolumn layout

Summary:
The FlatList keyExtractor for the case of multicolumn lists was causing remounts of all items, in case a single item was removed.
This bug was caused by the fact that the item received by the keyExtractor in case of multicolumn lists, is not an ITEM, but a ROW. This can be seen if you console.log(items) in FlatList's keyExtractor in case of multicolumn layout.
If you check this in the RNTester app, in case of multicolumn layout you will see a following item:
[
    {
        "key": "88",
        "pressed": false,
        "text": "Lorem ipsum dolor sit amet,[...]",
        "title": "Item 88"
    },
    {
        "key": "89",
        "pressed": false,
        "text": "Lorem ipsum dolor sit amet,[...]",
         "title": "Item 89"
    }
]

While in case of single column you will see the following:
{
    "key": "585",
    "pressed": false,
    "text":
    "Lorem ipsum dolor sit amet, [...]",
    "title": "Item 585"
}

Why is this important?
In case of multicolumn layout and a functionality where items can be removed (for example because of a user action), ALL items are unmounted and mounted again. This is caused by how the keyExtractor is built.
Example
The following expo snack shows the unmount/mounting issue in a multicolumn layout:
https://snack.expo.dev/@p-syche/multicolumn
You can remove the numcolumns={3} and remove items in a basic list to see how items are unmounted correctly.
In case of single column only the items coming into the view are mounted.
I created a repo with the same Expo Snack and added a patch for FlatList to demonstrate the bug being fixed:
https://github.com/p-syche/multicolumn-RN-patch/
Changelog:
[GENERAL] [FIXED] - Fixed keyExtractor for multicolumn FlatList.
Test Plan:
I added two buttons to the RNTester app, which let the user remove the 3rd or the 5th element in the FlatList. Pressing either of these buttons we can check that the changed keyExtractor works as expected and does not cause unmounting of all items in the list.

Point for discussion
I was thinking about adding a new prop to FlatList, something like keyExtractorForRow, which would be used in multicolumn layout. This prop would return the array of items for a given index (row).
The solution I implemented is simpler and I don't think it has any downsides, so I abandoned the idea for the new prop.
I'd be very glad to hear your opinions on both solutions.

@NickGerleman the changes in this PR concern multicolumn FlatList only. In the case of multicolumn FlatList, what the keyExtractor receives is the entire row, which is a static wrapper.
I recorded an android emulator with a patched app from this repo: https://github.com/p-syche/multicolumn-RN-patch/
In this repo item IDs are used to generate item keys and in item titles. You can see that when an item is removed everything is working correctly:
https://github.com/facebook/react-native/assets/4152181/806361db-3488-48ed-9959-79058cf7b788

Before, when we are generating a key for a row, was the key based on the combined items of the row? Reading the code, it seems like that was the intent.
So, e.g. we would remount if the list of items in the row changed, and that is the issue?

So, e.g. we would remount if the list of items in the row changed, and that is the issue?

Yes, the entire list would remount - which is unnecessary. The existing implementation works, but is not performant and causes visible problems in case of big lists. We observed this performance issue in a real application in production.

The potential problem I am seeing here, is that we are now reusing keys for a previous row. Wouldn't that allow restoring incorrect state to some existing item, if the row key is now the same as a previous row, in a different state?

@NickGerleman I'm sorry I don't understand your question :( could you clarify what you mean by:

if the row key is now the same as a previous row, in a different state?

React uses keys to map the identity of items, after rendering, to e.g. keep state associated with a rendered component.
Before, when we remove a single item, instead of a row, all of the keys change, because the identity of every row changes. That causes this unmount issue.
But, if we remove that identity, and only ever key based on position, a row may now share a key as some previously completely different row. So, it seems like we defeat the purpose of keying items, and being able to correlate state between them.
It's not how the component works today, but this kind of feels like the scenario where an idea component would organize cells using layout, where the React children list can still be flat, and we can key each item individually (and keep identities stable on item changed), while having row/column be a layout-level concept. Though otherwise, I'm not sure the best practices around compounding keys like this, and if remount is the correct behavior.
@rickhanlonii do you know the best practice here?

Hello @NickGerleman ,
Thank you for your detailed answer 👍
I think I haven't described well enough the issue that this PR is trying to solve. I'll quote two of your sentences:

React uses keys to map the identity of items, after rendering, to e.g. keep state associated with a rendered component.

--> Yes, of course 👍 This PR does not change that.

Before, when we remove a single item, instead of a row, all of the keys change, because the identity of every row changes (because items are shifted by one). That causes this unmount issue.

--> Yes, that is what happens, but it should not. When you remove an item from a list that is not in a multicolumn layout - all keys do not change - why should they change in a multicolumn layout?
I think the most important point here is that by changing the keyExtractor for multicolumn layouts, we're not touching the keys of particular elements. Every item still has it's own key, even if this item is in a different row. You can see that in log examples I put in the PR description.

@p-syche here is a repro, for where not using keyExtractor can cause state to be incorrectly associated. See how after we remove "c", it's state gets transferred to "d". This happens after your change, but not before.
https://github.com/facebook/react-native/assets/835219/78d4f248-0862-4d73-b6dc-49310dd5f8e9
/**
 * @flow strict-local
 * @format
 */

import * as React from 'react';
import {useCallback, useState} from 'react';
import {FlatList, Pressable, StyleSheet, Text, View} from 'react-native';

type ListCellProps = {
  item: string,
  ...
};

function ListCell({item}: ListCellProps): React.Node {
  const [isPressed, setIsPressed] = useState(false);

  return (
    <Pressable
      style={[styles.listCell, {backgroundColor: isPressed ? 'blue' : 'red'}]}
      onPress={useCallback(() => setIsPressed(!isPressed), [isPressed])}>
      <Text>{item}</Text>
    </Pressable>
  );
}

const MemoListCell = React.memo(ListCell);

function keyExtractor(item: string, index: number): string {
  return item;
}

export default function Playground(): React.Node {
  const [items, setItems] = useState(['a', 'b', 'c', 'd', 'e', 'f']);

  return (
    <View>
      <Pressable
        onPress={useCallback(
          () => setItems(items.filter(i => i !== 'c')),
          [items],
        )}>
        <Text>Remove C</Text>
      </Pressable>
      <FlatList
        numColumns={2}
        data={items}
        renderItem={useCallback(
          ({item}) => (
            <MemoListCell item={item} />
          ),
          [],
        )}
        keyExtractor={keyExtractor}
      />
    </View>
  );
}

const styles = StyleSheet.create({
  listCell: {
    height: 50,
    flex: 1,
  },
});

@NickGerleman thank you for the reproduction 🙌  I see the issue now.
Do you agree however that the current implementation, causing remounts, should be changed? Or do you think it should stay as is?

Hello again @NickGerleman :)
I have just updated this PR to include changes in how the key is built for items in case of multicolumn layout.
Before - the item index was used for the item key. I suggest we use a different strategy:
const key = keyExtractor(it, index * cols + kk); (changed here )
With this change, items keep their state correctly, unless they change rows. You can see that on the screen recording below:
https://github.com/user-attachments/assets/582bbcac-991b-42be-9ad4-57ec9146cc17
Please let me know how you feel about this updated solution.


eth_getTransactionByHash returns null

Describe the bug
The hive test for eth_getTransactionByHash fails, returning null instead of the transaction.
>>  {"jsonrpc":"2.0","id":1,"method":"eth_getTransactionByHash","params":["0x0d9ba049a158972e7fc1066122ceb31e431483ebf84f90f845f02e326942d467"]}
<<  {"jsonrpc":"2.0","result":null,"id":1}
response differs from expected:
 {
   "id": 1,
   "jsonrpc": "2.0",
-  "result": null
+  "result": {
+    "blockHash": "0xfe21bb173f43067a9f90cfc59bbb6830a7a2929b5de4a61f372a9db28e87f9ae",
+    "blockNumber": "0x2",
+    "chainId": "0x539",
+    "from": "0x658bdf435d810c91414ec09147daa6db62406379",
+    "gas": "0x5208",
+    "gasPrice": "0x2db08787",
+    "hash": "0x0d9ba049a158972e7fc1066122ceb31e431483ebf84f90f845f02e326942d467",
+    "input": "0x",
+    "nonce": "0x1",
+    "r": "0x52a6f622013359249316f4c017a67bc2c659f513dac5efea43a84b6ce4e462b1",
+    "s": "0x55ba2a779eaf62efa7d641a32ea329faabf9f097d376e2e400115a5151b9470",
+    "to": "0x658bdf435d810c91414ec09147daa6db62406379",
+    "transactionIndex": "0x0",
+    "type": "0x0",
+    "v": "0xa95",
+    "value": "0x3e8"
+  }
 }

Steps to reproduce
Run hive:
./hive --client reth --sim ethereum/rpc-compat --sim.limit "eth_getTransactionByHash"

Node logs
No response
Platform(s)
No response
What version/commit are you on?
No response
Code of Conduct

[X] I agree to follow the Code of Conduct

blocked by #1905

fixed by #1905


Ability To Rename Token Groups In Subsequent Sets

Is your feature request related to a problem? Please describe.
When a group for instance is collapsed in one theme, it also collapses in all sets that contain this same token-group for overwriting to take place. Or when you change a single token's name, in the popup modal you are offered to rename it even in the subsequent sets that have the same defined. However, when attempting to rename a token group (parent), it is apparent that a manual change is required in every set containing the same token-group.
Describe the solution you'd like
Display and option to even rename the token-groups in subsequent sets when changed.
Screenshots:
When renaming tokens

When renaming token-groups (parent)

This request has been moved to our new feedback tool. Go check out https://tokensstudio.featurebase.app/ to create a free account. You can upvote and comment on existing posts, make a new request, and subscribe to be notified when requests move into our roadmap.

Added to Featurebase Roadmap : 🌜Theme management (pro) enhancements


Add way to include total number of results (ignoring limit)

It would be nice to be able to add the number of total results available; in our case, hitting Enter will do a complete search, but we only show the top 10 results in typeahead. If there are 25 results, we'd like to be able to say, in the footer template, for example, "25 results available; press enter to see all" (or whatever other configurable text we'd like). Right now, there doesn't even appear to be a way to see how many total suggestions there were.

This is a good idea, and I would go further and say I for one would appreciate the ability to open a full list in a larger widget (like a Twitter Bootstrap modal).
But it may be a good start/compromise to start by lazy loading results, as @vikashgoyal requested in ticket #1556 of Twitter's Typeahead.js.


Clarify key mapping / add warning for fat-fingered Mac users

From @kevinmickey on May 28, 2016 12:28
The README states the key-mapping as cmd-alt-q.  I ignorantly/mistakenly used shift-option instead of option.  It turns out that, on a mac, this nearby key-mapping happens to force quit all applications and immediately log the user out...
Could you add (or cmd-opt-q on Mac) to the README?  (I did not use the command palette, which appears to use icons instead of 'alt' or 'opt'.)
Maybe also add a warning for those with fat fingers?
Copied from original issue: atom/autoflow#49

From @ManuelSchneid3r on March 7, 2017 12:34
Further you could note the default for other platforms.

I made a PR for this and tried to follow to contributing guidelines as closely as I could. Any feedback is welcome.

On review with the team, we've decided that we're not going to accept this change. We don't believe that duplicating macOS key bindings containing alt with ones that contain opt is going to make our README's or other documentation easier to follow on the whole. Additionally, there are many key bindings that, when mistyped, could have unforeseen consequences. There are hundreds of key bindings in Atom and placing and maintaining caveats on all the possible ways they could be mistyped is not something we want to take on.
Thanks for the suggestion and thank you @thomasstep for the help :bow:


Build Player selection screen.

The screen will go after the LoginScreen and will be invoked after the Player clicks on the Start button.
The screen will look like this:

Steps:

Create new XAML page.

Have the LoginScreen start button bring the Player to the new XAML page. See LoginScreen::OnDemoClicked.

Create the XAML page to mimic the desired screen.

The Player Select page will contain the Players name, health level.

The Player will be able to use the game controller to select through the options.

"Copy Player" will not be an option. Only "Erase Player."

Be able to populate the screen with data from an API that will be provided.


error: accumulating resources

I went through the steps to deploy Jitsi on my microk8s cluster with kustomize and recieve following error:
error: accumulating resources: accumulation err='accumulating resources from 'https://github.com/jitsi-contrib/jitsi-kubernetes/tree/main/doc/kustomize': yaml: line 218: mapping values are not allowed in this context': evalsymlink failure on '/tmp/kustomize-2873540753/tree/main/doc/kustomize' : lstat /tmp/kustomize-2873540753/tree: no such file or directory
What have I done wrong?
The plan is to run jitsi on a internal server and access the Service with the IP, without exposing anything to the internet, so a https certificate by letsencrypt is not required or relevant for us.
I enabled the Ingress microk8s addon and created the .yaml files like this:
010-deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    k8s-app: jitsi
  name: jitsi
  namespace: jitsi
spec:
  template:
    metadata:
      labels:
        k8s-app: jitsi
    spec:
      containers:
        - name: web
          env:
            - name: PUBLIC_URL
              value: "http://<IP_ADDRESS>"

        - name: prosody
          env:
            - name: PUBLIC_URL
              value: "http://<IP_ADDRESS>"

041-ingress.yaml
---
###################################################
# Ingress
###################################################
kind: Ingress
apiVersion: networking.k8s.io/v1
metadata:
  name: jitsi
  namespace: jitsi
  annotations:
    cert-manager.io/cluster-issuer: "letsencrypt-prod"
spec:
  tls:
  - hosts:
    - <IP_ADDRESS>
    secretName: tls-jitsi
  rules:
  - host: <IP_ADDRESS>
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: web
            port:
              number: 80

kustomization.yaml
namespace: jitsi
bases:
- https://github.com/jitsi-contrib/jitsi-kubernetes/tree/main/doc/kustomize

resources:
- 041-ingress.yaml

patchesStrategicMerge:
- 010-deployment.yaml

Thank you for your help!

I attempted a fresh microk8s installation on my local computer and ended up with the same Error, mentioning line 220.
Here are all commands i executed:
Installing Microk8s and dashboard:
sudo snap install microk8s --classic
sudo ufw allow in on cni0 && sudo ufw allow out on cni0
sudo ufw default allow routed
sudo microk8s enable dns dashboard storage
sudo microk8s status
sudo microk8s kubectl get all --all-namespaces
token=$(microk8s kubectl -n kube-system get secret | grep default-token | cut -d " " -f1)
sudo microk8s microk8s kubectl -n kube-system describe secret $token
Attempting installation with kustomize:
mkdir my-jitsi
cd my-jitsi
vim kustomization.yaml
vim 010-deployment.yaml
-> I took the ingress file out
-> I set the PUBLIC_URL to my IP
sudo microk8s kubectl create namespace jitsi
sudo microk8s kubectl create secret generic jitsi-config -n jitsi --from-literal=JICOFO_COMPONENT_SECRET=start --from-literal=JICOFO_AUTH_PASSWORD=start --from-literal=JVB_AUTH_PASSWORD=start
sudo microk8s kubectl apply -k ./my-jitsi

Oh! Now I see that there is a typo in the docu.
The deployment file is 030-deployment.yaml and not '010-.....'
I think this causes the problem. Just rename your 010-deployment.yaml into 030-deployment.yaml This should do the trick.
I will update the documentation. Please let me know if this works for you.

I updated the file name and kustomization.yaml
Sadly the issue remains.
error: accumulating resources: accumulation err='accumulating resources from 'https://github.com/jitsi-contrib/jitsi-kubernetes/tree/main/doc/kustomize': yaml: line 225: mapping values are not allowed in this context': evalsymlink failure on '/tmp/kustomize-1066009744/tree/main/doc/kustomize' : lstat /tmp/kustomize-1066009744/tree: no such file or directory

Then please take out the patchesStrategicMerge resoruce and test if this did work.
If yes, than something in your 030-deployment.yaml is incorrect.

The attempt with just the kustomization.yaml, without the resources and patchesStrategicMerge files did not work either, same error.
I appreciate your support!
Another idea is, the containerization of snap could cause issues accessing the tmp files.

ok, then I am no longer convinced that microk8s fully support kustomize. The error messages are also not helpful.

Since I also do not know how to continue here, we have gone back to working with Kompose.

Same issue here. I am on a bare metal cluster so i dont think it is because of microk8s.

Just to sort things out: if you remove the resources and patches in your kustzomiz file like the following one. Is it working?
namespace: jitsi
bases:
- https://github.com/jitsi-contrib/jitsi-kubernetes/tree/main/doc/kustomize

#resources:
#- 041-ingress.yaml

#patchesStrategicMerge:
#- 030-deployment.yaml

I have tried the helm install. Helm install is working.

Still same issues when resources and patches are removed..

Can someone narrow down the issue if this is related to the kubernetes environment/version? I am running in v1.21.6 and can not reproduce this kind of issue.

I am running v1.22.4

Running 1.21.7 in aks.
We managed to use a workaround by downloading all the base files locally and not use the base feature. We have a plan to test this with a clean microk8s environment.

From: Jose Olivera @.>
Sent: Wednesday, February 23, 2022 1:10:26 PM
To: jitsi-contrib/jitsi-kubernetes @.>
Cc: Tim Nilimaa-Svärd @.>; Comment @.>
Subject: Re: [jitsi-contrib/jitsi-kubernetes] error: accumulating resources (Issue #19)
I am running v1.22.4
—
Reply to this email directly, view it on GitHubhttps://github.com/jitsi-contrib/jitsi-kubernetes/issues/19#issuecomment-1048717883, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABN27S4DDKT42J5BUN6HIIDU4TFDFANCNFSM5NX323SA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>

same problem, k3s v1.22.7

Ok so the deal is that kustomize git urls are a complete mess and there's a whole chaos of issues and PRs about it, with this being the latest: https://github.com/kubernetes-sigs/kustomize/issues/4454
What worked for me was removing https:// and /tree/main from the url, so you have:
`
namespace: jitsi
bases:

github.com/jitsi-contrib/jitsi-kubernetes/doc/kustomize
...
`
I can go ahead and make a PR for this.

Yes you are totally right! There is in deed a wrong URL in the docu and I have overseen this all the time during this discussion.

Please give us some feedback if this solves your problem.
Solution:
replace in your kustomization.yaml  file the line
- https://github.com/jitsi-contrib/jitsi-kubernetes/tree/main/doc/kustomize

with
- github.com/jitsi-contrib/jitsi-kubernetes/doc/kustomize


Sonar Go unit test reporting jobs failing mentioning old Java version

What happened:
On multiple repos, the Go unit test reporting job is failing with

The version of Java (11.0.20) used to run this analysis is deprecated, and SonarCloud no longer supports it.

https://github.com/submariner-io/subctl/actions/runs/7972580977/job/21766423780
What you expected to happen:
I don't remember configuring a Java version and I don't see one in our current config, but need to look around more.

This doesn't seem to be an issue anymore.


TopicTest with wildcards failed due to user doesn't have permission='CREATE_ADDRESS'

description:

subscriber is not able to subscribe to topic via wildcard. We have topics with names test-topic-pubsub-${X}.${Y} and 5 consumers which try to subscribe to test-topic-pubsub-1.* ,-2.*, ...etc
senders send messages to each topic successfully
works good with bare artemis instance: https://github.com/kornys/DurableSubscriptionTest/blob/master/src/test/java/topictests/TopicNonDurableTests.java#L90

prerequisites:

enmasse running in multitenant mode: sh ./templates/install/deploy-openshift.sh -a "none standard" -o "multitenant"

steps to reproduce:

execute already existing test:
make MULTITENANT=true SYSTEMTEST_ARGS='io.enmasse.systemtest.brokered.TopicTest#testTopicPubSubWildcards systemtests
https://github.com/EnMasseProject/enmasse/blob/f5e517ecd24d00f56bd3b83fead9175b379320a3/systemtests/src/test/java/io/enmasse/systemtest/brokered/TopicTest.java#L21
output from test:

3265158 [vert.x-eventloop-thread-0] INFO test - Receiver link 'test-topic-pubsub0.*' opened, granting credits
3265158 [vert.x-eventloop-thread-0] INFO test - Link closed with Error{condition=amqp:unauthorized-access, description='AMQ219015: not authorized to create consumer, AMQ119032: User: test does not have permission='CREATE_ADDRESS' on address test-topic-pubsub0.*', info=null}
3265549 [vert.x-eventloop-thread-0] INFO test - Receiver link 'test-topic-pubsub1.*' opened, granting credits
3265549 [vert.x-eventloop-thread-0] INFO test - Link closed with Error{condition=amqp:unauthorized-access, description='AMQ219015: not authorized to create consumer, AMQ119032: User: test does not have permission='CREATE_ADDRESS' on address test-topic-pubsub1.*', info=null}
3265942 [vert.x-eventloop-thread-0] INFO test - Receiver link 'test-topic-pubsub2.*' opened, granting credits
3265942 [vert.x-eventloop-thread-0] INFO test - Link closed with Error{condition=amqp:unauthorized-access, description='AMQ219015: not authorized to create consumer, AMQ119032: User: test does not have permission='CREATE_ADDRESS' on address test-topic-pubsub2.*', info=null}
3266330 [vert.x-eventloop-thread-0] INFO test - Receiver link 'test-topic-pubsub3.*' opened, granting credits
3266330 [vert.x-eventloop-thread-0] INFO test - Link closed with Error{condition=amqp:unauthorized-access, description='AMQ219015: not authorized to create consumer, AMQ119032: User: test does not have permission='CREATE_ADDRESS' on address test-topic-pubsub3.*', info=null}
3266720 [vert.x-eventloop-thread-0] INFO test - Receiver link 'test-topic-pubsub4.*' opened, granting credits
3266720 [vert.x-eventloop-thread-0] INFO test - Link closed with Error{condition=amqp:unauthorized-access, description='AMQ219015: not authorized to create consumer, AMQ119032: User: test does not have permission='CREATE_ADDRESS' on address test-topic-pubsub4.*', info=null}

@rgodfrey imo would be nice to prioritize this


Send messages to large set of users from CSV

Hi,
Can we increase size of the message in the database so that we can send messages from CSV to 5000 users.
We tried to send a message to around 1000 users and it failed for us.
Any feedback will be appreciated.

Hi @ShalinShah84 ,
Thanks for raising the query. I kindly request the sharing of a screenshot demonstrating the CSV message sending option you're utilizing.

Hi,

We don't get any error message while sending messages, but the CSV does not send message to users if the csv file consists of more than 500 records.

We used the following repo
https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/tree/v4.1.5

Hi @ShalinShah84 ,
The option feature- send in chat to list of users provided in a valid CSV is yet to be implemented in our official CC. We consider this a customized version.
Our support scope is very limited with the standard version as the area of code modification is not known to us for customized versions. We will not be able to provide much assistance on this issue as the deployed instance is a customized version.
Please let us know if you have any issues with the standard version.


[Bug] Pydantic's SecretStr type is not supported

Describe the bug
Trying to return a pydantic model with an attribute SecretStr yields the following error:
Traceback (most recent call last):
  File "handle_request", line 96, in handle_request
  File "/tmp/test_sanic/.venv/lib/python3.10/site-packages/sanic_ext/extensions/openapi/openapi.py", line 232, in handler
    retval = await retval
  File "/tmp/test_sanic/.venv/lib/python3.10/site-packages/sanic_ext/extras/validation/decorator.py", line 75, in decorated_function
    retval = await retval
  File "/tmp/test_sanic/server.py", line 25, in user
    return json(body)
  File "/tmp/test_sanic/.venv/lib/python3.10/site-packages/sanic/response/convenience.py", line 50, in json
    return JSONResponse(
  File "/tmp/test_sanic/.venv/lib/python3.10/site-packages/sanic/response/types.py", line 248, in __init__
    self._encode_body(self._use_dumps(body, **self._use_dumps_kwargs)),
TypeError: User(username='string', password=SecretStr('**********')) is not JSON serializable

Maybe it is not intended to support this but I supposed that I get a representation containing * marks.
The pydantic documentation describes that it will be formatted using * on serializing to json.
If I uncomment the response part of the openapi decorator I get the following error message:
  ...
  File "/usr/lib/python3.10/typing.py", line 694, in _evaluate
    eval(self.__forward_code__, globalns, localns),
  File "<string>", line 1, in <module>
NameError: name 'unicode' is not defined

To Reproduce
from sanic import Sanic, json
from sanic_ext import openapi, validate

from pydantic import BaseModel, SecretStr

class User(BaseModel):
    username: str
    password: SecretStr

app = Sanic("MyHelloWorldApp")

@app.post("/user")
@openapi.definition(
    body={'application/json': User.schema()},
    # response=[
    #     openapi.definitions.Response(
    #         content={"application/json": User},
    #         description="...",
    #         status=200,
    #     )
    # ]
)
@validate(json=User)
async def user(request, body: User):
    return json(body)

Expected behavior
To get a json representation consisting '*' marks.
Environment (please complete the following information):

OS: Manjaro
Browser: firefox

I was able to partially fix the problem by changing the default function for dumping models to json by using the function pydantic_encoder:
from sanic import Sanic, json
from sanic_ext import openapi, validate

from pydantic import BaseModel, SecretStr

class User(BaseModel):
    username: str
    password: SecretStr

from json import dumps as json_dumps

from functools import partial
from pydantic.json import pydantic_encoder

dumps = partial(json_dumps, default=pydantic_encoder)

app = Sanic("MyHelloWorldApp",
            dumps=dumps)

@app.post("/user")
@openapi.definition(
    body={'application/json': User.schema()},
    # response=[
    #     openapi.definitions.Response(
    #         content={"application/json": User},
    #         description="...",
    #         status=200,
    #     )
    # ]
)
@validate(json=User)
async def user(request, body: User):
    return json(body)

This eliminates the TypeError but does not have any impact on the NameError.
BTW, I am using Sanic v22.12.0.

Looks like pydantic is doing some voodoo magic under the hood. Not sure how to address this yet.


Support RealmValue (aka mixed)

Support RealmValue that allows users to store different types in the same field
@RealmModel()
class _AnythingGoes {
  @Indexed()
  late RealmValue any;
  late List<RealmValue> manyAny;
}

void main() {
  final realm = Realm(Configuration.local([AnythingGoes.schema]));

  final something = realm.write(() => realm.add(AnythingGoes(any: RealmValue.string('text'))));

  realm.write(() {
    something.manyAny.addAll([null, true, 'text', 42, 3.14].map(RealmValue.from));
  });
}

Resolves: #684

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

25 of 25 (100.0%)  changed or added relevant lines in 7 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.05%) to 89.151%

Files with Coverage Reduction
New Missed Lines
%

lib/src/realm_class.dart
1
92.66%

Totals

Change from base Build<PHONE_NUMBER>:
0.05%

Covered Lines:
2794

Relevant Lines:
3134

💛  - Coveralls

We probably need to expose ObjectType similarly to what we're doing in C#.

I assume this is catch the error case that you cannot store embedded objects in a RealmValue (or asymmetric objects for that matter, when we eventually support those).
I have reworked the code to catch this misuse in the type system.

@nirinchev I couldn't get your meaning for this one
We probably need to expose ObjectType similarly to what we're doing in C#.

Could you clarify this. Especially important if it is a reason to block a PR.

Okay, I had forgotten some things in dart, so I believe there's more work needed to support RealmValue, but that can probably be split into a different PR. Here's an example of an issue that we can't handle today. Let's say you have a synchronized Realm with the following schema (this is v1 of your app).
class MyDynamic {
  RealmValue value;
}

class Person {
  String name;
}

In v2, you add a new type - Dog. Now, a new client comes in and adds a Dog instance as a value for MyDynamic.value.  In C# and other SDKs we expose the object schema on RealmObject instances, so you could do something like:
final obj = myDynamic.value.as<RealmObjectBase>();
switch (obj.schema.name) {
  case "Person": // do something
  default:
    final nameProp = obj.schema.properties.firstOrNull(p => p.name == "name");
    if (nameProp != null && nameProp.propertyType == RealmPropertyType.string) {
      // do something with the name
    }
}

My thinking with exposing ObjectType on RealmValue was to support use cases like:
public String getDisplayName(RealmValue value) {
  switch (value.objectType) {
    case null:
      // value is not an object or is null - do nothing
	  return "unknown";
    case "Person":
      final person = value.as<Person>();
      return '${person.firstName} ${person.lastName}';
    case "Company":
      final company = value.as<Company>();
      return company.legalEntity.name;
    default:
      final obj = value.as<RealmObjectBase>();
      final nameProp = obj.schema.properties.firstOrNull(p => p.name == "name");
      if (nameProp != null || nameProp.propertyType == 'string') {
        return obj.dynamic.get<string>('name');
      }

      return "unknown";
  }
}

But again, this depends on the schema being available on the realm object.