"gzip" directive is duplicate in joinmarket_webui_ssl.conf:16

Installed JAM on my Raspiblitz (running on Raspberry Pi 4) today.
After install, I tried to look at the status of Electrs, but it said nginx had failed. When I run sudo nginx -t, I get the following:
nginx: [emerg] "gzip" directive is duplicate in /etc/nginx/sites-enabled/joinmarket_webui_ssl.conf:16
nginx: configuration file /etc/nginx/nginx.conf test failed
Can I somehow fix this?

Hey! Thanks for the heads-up!
This should be fixed with https://github.com/rootzoll/raspiblitz/pull/3321
and will be released with RaspiBlitz v1.8.
A possible workaround is probably to remove the line include /etc/nginx/snippets/gzip-params.conf; from joinmarket_webui_ssl.conf: https://github.com/rootzoll/raspiblitz/blob/v1.8/home.admin/assets/nginx/sites-available/joinmarket_webui_ssl.conf#L11
But I am not sure if this version is even working as expected on RaspiBlitz.. you might want to wait for RaspiBlitz v1.8.1..

Hey @Lobbelt, did you manage to make it work?

Sorry I didn't end up using the workaround, I just flashed a fresh install of Raspiblitz on the SD card and took it from there. Holding off on JAM for now. :-)

Sorry I didn't end up using the workaround, I just flashed a fresh install of Raspiblitz on the SD card and took it from there. Holding off on JAM for now. :-)

k. Thanks for the quick response. Closing the issue now, if that is okay. Feel free to reopen if you think this is a mistake or report back in case you try it again :orange_heart:


General socks feature

As Vidalia Tor dropped out HTTP proxy Polipo from their bundle, only Socks is supported so far.
I wonder does Livestreamer support at the moment Socks proxy on HTTP streams (HLS, HDS included) and if not could it be implemented in future ?

@chrippa requests already has socks support and livestreamer still doesn't.


Add the ability to skip snatting to certain ports

This is meant to I can have ssh and wireguard listen on a couple ports without risking SNAT causing a tuple conflict by using it for outgoing.
In reality, this probably wouldn't happen, but it feels right to have this at least.

Leaving this as a PR until I've manually tested it works for my ssh-and-wireguard usecase

Manually testing, this seems to work like I'd expect.


docs: comments about code that is part of #311

See internal discussion https://prisma-company.slack.com/archives/CKCQQGXJM/p1637780511103100

Looks good can we merge?

Now after release we can 👍


Inconsistency in variable names: topbar vs top-bar

Hi Everyone,
first issue report here,
I just found inconsistent that you use "topbar" and "top-bar" to refer to the Top Bar component.
Pretty much it is a matter of renaming your setting variables.
scss/components/_top-bar.scss
11:$topbar-padding: 0.5rem !default;
15:$topbar-background: $light-gray !default;
17:/// Background color submenus within the top bar. Usefull if $topbar-background is transparent.
19:$topbar-submenu-background: $topbar-background !default;
23:$topbar-title-spacing: 0.45rem 1rem 0 1rem !default;
27:$topbar-input-width: 200px !default;
31:$topbar-unstack-breakpoint: medium !default;
45:  padding: $topbar-padding;
49:    background-color: $topbar-background;
52:  // Check if $topbar-background is differnt from $topbar-background-submenu
53:  @if ($topbar-background != $topbar-submenu-background) {
55:      background-color: $topbar-submenu-background;
61:    max-width: $topbar-input-width;
126:    @include breakpoint($topbar-unstack-breakpoint) {
146:      margin: $topbar-title-spacing;
158:      margin: $topbar-title-spacing;

scss/settings/_settings.scss
592:$topbar-padding: 0.5rem;
593:$topbar-background: $light-gray;
594:$topbar-submenu-background: $topbar-background;
595:$topbar-title-spacing: 0.45rem 1rem 0 1rem !default;
596:$topbar-input-width: 200px;
597:$topbar-unstack-breakpoint: medium;

I can contribute with a PR, i just need to be guided how to want to deprecate this and if you want to warn users when old-named variables are used

@ncoden @andycochran @brettsmason what do y'all think?

I'm not sure this is a bug. But this is also the case for accordionmenu and accordion-menu, buttongroup and button-group, closebutton and close-button, dropdownmenu and dropdown-menu, helptext and help-text, mediaobject and media-object, offcanvas and off-canvas … where we use one word for SASS and two hyphenated words for CSS classes.

If we have to be consistent now, I think we should move to lisp-case, because it is the CSS standard. However, the namespace and role of the class/variable/function/mixin can't be easily separated. This is related to the naming problem mentioned in Yetinauts/#18

@ncoden what is our plan, how do we handle this?

Closing as we will not change this in v6.


RiveScript Monolithic Version Control

RiveScript may be able to benefit from having a monolithic version control repository rather than having one repo per implementation (Perl, Python, JavaScript, Go and Java). It could also encompass and make obsolete the other closely related repos: rivescript-wd and rsts.
High Level Rationale
This would involve a temporary disruption for third party contributors as the repos get rearranged and all the implementations are migrated into the common aichaos/rivescript repo. But the benefits gained from having a common repository for all implementations may include:

Adding a new feature to RiveScript as a whole can be made easier. For example, if I'm adding a new command to the language, I can have all 5 implementations get the update simultaneously with one GitHub pull request.
The current state of affairs is that I would have to sit down all at once, clone all 5 repositories and deal with the overhead of making the changes and pull requests separately for each version. This is such an obstacle that I haven't added a new global feature to RiveScript in quite a while, because I don't want the published module versions to diverge from each other for any length of time.

Unit tests can be consolidated and kept in sync across all versions. Currently, each implementation has their own copies of unit test fixtures in their own repo so that Travis CI can run tests on push, and there is also the aichaos/rsts project which provides YAML test fixtures for the RiveScript language itself.
Currently a lot of the YAML fixtures in rsts are duplicated from the tests in the individual implementations. And currently a lot of the implementations fail the RSTS test suite due to random little quirks in their implementations (for example, the exact wording they use for error messages).
A mono-repo could bring the YAML fixtures from RSTS into the repo and all the unit tests can become RSTS tests, so that they are all kept in sync at all times and it will be easier to iron out their little quirks to all behave identically. And it's friendly for Travis CI which can still run automated unit tests.

I can make more use of GitHub features like Projects and Wikis. Currently most of the repos don't have wikis enabled until I have a repo-specific need for them (i.e., for the JavaScript version to document the Async issues that come up frequently in that project).
If all the RiveScript implementations are merged together into the aichaos/rivescript project, the existing RiveScript Community Wiki can be merged with the random odd pages from the projects' own wikis.

Impact
Impact on Contributors
Having a single repo containing 5 different programming language implementations may deter contributions from developers who are only familiar with a subset of those languages: if they fix or change a behavior, the unit tests might pass for the language they modified but fail for the ones they didn't.
This may be somewhat alleviated by using the Git Flow workflow and have the master branch be the "production ready" one where all unit tests are passing and all builds are stable.
All pull requests would instead be directed at the develop branch which is allowed to fail tests from time to time. So if a contributor fixes the JavaScript implementation and breaks the other four, those can be patched by others (or me) later before the next production-ready merge to master can be done.
Impact on Implementations
The Perl, Python, Java and JavaScript implementations shouldn't be affected too much, as their GitHub URLs aren't very important in those languages. Their links on e.g. npm and PyPI would just be updated to point to the mono-repo.
The Go version would need to get a new module name, since Go ties the GitHub source address to the module's name by default. Options may include:
import (
    // The old (current) import path
    "github.com/aichaos/rivescript-go"

    // The new GitHub import path
    "github.com/aichaos/rivescript/go"

    // Could also make use of vanity import URLs...
    // but the gopkg.in one looks ugly IMHO.
    "gopkg.in/aichaos/rivescript/go.v1"

    // A self hosted vanity URL but it would require me to maintain the
    // URL and make sure it doesn't go down, or it will break `go get`
    "rivescript.com/go"

    // I could use GitHub Pages to remove the burden of self hosting
    // a vanity URL though; the Go version can have "/rivescript" because
    // no other language uses these kinds of import paths.
    "aichaos.github.io/rivescript"
)

On a bright note: I've been struggling with the code layout in rivescript-go because I don't like a large number of Go source files cluttering up the root of the repo alongside the meta files like README.md, Changes.md and .travis.yml; as such I kept the majority of the source code (with the tons of unit tests) under a src/ subdirectory and created a wrapper API in the root of the repo instead.
If the Go source for RiveScript were kept at aichaos/rivescript/go, then the /go directory can replace the src one and all the Go source files can be kept in a sane place together. The root of the repo, having nothing to do with the Go specific implementation, can contain only meta files and no program code at all.
This would simplify the Go API as much as I've been wanting.
Impact on Travis CI
The root of the repo could probably add a Makefile for Travis CI to use which would handle the necessary logic to run through the unit tests on each implementation.

I think this unnecessarily raises the level of complexity too much to be helpful. The biggest wall it'll create is in collaboration with other developers.
And to address the file structure of the Go implementation - I'm very much a fan of keeping all my code within a src directory, where I will further categorize classes and files into subdirectories for organizational purposes. Tests I keep at the root within their own tests directory as well. This keeps the root of the project minimal and clean, and organized in a way that is easy to navigate.
If you take a look at my PHP implementation, you'll find a structure like the following:
+ logs/
+ resources/
+ src/
+ tests/
.gitattributes
.gitignore
LICENSE
README.md
composer.json
phpunit.xml
rivescript

With Go, the project structure becomes a more important problem because of the tight coupling between repository URLs (and therefore structure) and the packages in them. To put the bulk of the source code into a src/ subdirectory, I had to make a "wrapper" package at the root of the repository anyway so that I could provide a sane API to developers while also keeping the root of the repo as minimal as possible.
With the current layout, github.com/aichaos/rivescript-go is one package and github.com/aichaos/rivescript-go/src is a wholly separate one, which has a very similar API but that I encourage developers not to use... but the whole thing feels clumsy to me. The reason the src package has a similar API is that it has to export all its things up to the root package, because in Go any symbol with a capitalized first letter is exported to be used by other packages and lowercase names are internal use only (within the same package that defined it). For the high level wrapper class to get at all the functions and types of the src class, the src has to export all those symbols publicly.
Unit tests in Go become a whole other can of worms. It's possible to put the tests into a separate tests folder (and I played with that idea back and forth while working on the tests), but you end up losing a lot of the nice features of the Go tooling, such as code coverage reports. In order to get code coverage (and therefore nice highlighting of untested blocks of code in my text editor), the unit tests need to exist in the same package as the code they're testing (and be able to test internal functions and types). If I put the code into a separate tests directory, it can only test the public side of the API by treating it as a third party module. This works as far as running the tests go, but you lose the code coverage reports. It's not too bad of a loss, I suppose, because I don't bother caring about code coverage for the other implementations, but it's a really nice feature that's so easy to deal with in Go that it'd be a shame not to have it just for the sake of organizing my repository better.

Some ideas I have that could help me with the Go codebase without going to a mono-repo:

Find a way to use the rsts test suite in the Go version and get rid of all the current unit tests in favor of that.

Maybe by using git submodules to clone the rsts repo into a folder in the rivescript-go repo, and run the tests out of it; and make sure that all works with Travis CI for automated testing.
I'd lose code coverage reporting (most likely), but I could get rid of all of the *_test.go files and only have one (or less). Less source files altogether means I might be able to just bite the bullet and get rid of the src/ package and put everything into the root of the repo and solve that problem too.

Just move the Go implementation into the rivescript repo anyway, as though I'm going for a mono-repo, and I could get the benefits mentioned in the original post with organizing the repo. The src/ sub-package would become the go/ folder in rivescript without making the import URL look too silly or stuttery (e.g. github.com/aichaos/rivescript-go/go looks worse than github.com/aichaos/rivescript/go)
Or just throw in the towel and move everything from the src subpackage into the main package and just deal with the fact that I'll have 20 *.go files sitting in the same place as README.md, Changes.md, .travis.yml, .gitignore and so on. This feels very cluttered to me but other Go developers seem to care a lot less about it than I do, so, :shrug:


Fix APT upgrade conflicts with the tegra-libraries

The tegra-libraries we all split in to their own recipes however they
conflict with the old tegra-libraries packages when upgrading. This
marks the previous package dependencies as conflicts so they are removed
on an upgrade.
Signed-off-by: Mike Loder<EMAIL_ADDRESS>NOTE: I only have a PR for the Dunfell branch as I don't have a setup for the new master yocto with the updated syntax.

Good catch, we have RBREAKS_ in a number of our recipes but it does not appear to be used by anything. Not sure where that came from, i will remove it.
On a side note I only submitted a Dunfell PR as master is a different syntax and I don't have a setup to test it.

I have removed the RBREAKS_ fields from the recipes.

I've had to revert this, as the combination of the RREPLACES  and RCONFLICTS in this change is causing ordinary builds to fail when using RPM packaging (possibly others as well).
In OE-Core's package_rpm.bbclass, RREPLACES is translated into a combination of Obsoletes: and Provides: in the RPM package headers.  So the packages replacing the old tegra-libraries package are also now providing that package, so all of the packages that use RCONFLICTS to conflict with tegra-libraries are refusing to install into an RPM-based rootfs.
I don't know if what package_rpm.bbclass is doing is wrong, or if there is some other combination of settings that would allow for runtime deb package feed handling to correctly upgrade from the old (pre-32.6) tegra-libraries package to the new split packages without breaking normal rootfs builds. So for now, I'm just reverting this change.

Hum that's disappointing. Thanks for letting me know. I can keep these in our appends layer.


secp256k1_XMD:SHA-256_SSWU_RO_ missing the isogenous generator

This PR is draft since I need a hint! When hashing the lib checks that the isogenous generator maps correctly onto the target curve generator. The problem is I couldn't find the relevant generator for RFC9380 yet (via a reference, or computationally). I found out that there's a path via the isogeny kernel, but I wonder if somebody could suggest a simpler way to obtain that to continue with this.
Description

Adds hashing to the <curves/secp256k1>.
closes: none - just a development

Since this isn't ready for merging yet it seems to me the check-list is ok to postpone, correct me if I'm wrong, pls.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (master)
[ ] Linked to GitHub issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[ ] Updated relevant documentation in the code
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[ ] Re-reviewed Files changed in the GitHub PR explorer

@mmaker , I guess you've made most of this crate: could you take a look, pls. (Or tell who's the best person for this now.)


Optimize location with binary search

Should make generateMap about 15% faster. Will follow with a few more cool PRs 😎 cc @alangpierce @Rich-Harris

oops, missed this a second ago — another release, 0.23.1. Thank you!


Find ref in destructuring wip

Fixes #

Hi @okofob, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

closing as this is not a real PR


fix(relay): delete correct label from exported metrics

The documentation isn't super clear here: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/googlecloudexporter/README.md#preventing-metric-label-collisions
I think we might have to delete the service.name label instead of service_name because that is how I am setting (and probably exporting) it.

Actually, it is working so this is not needed :)


utils: improve logging

currently, the sop uses global logging levels (fatal, error, warn, info, debug) inherited from CE SDK. this is problematic for large scenes where some rpks emit a lot of cga warnings/errors -> log flood & huge slowdown!
this needs a proper spec, i.e.

CGA errors / asset issues should be collected separately and be inspectable (cf CE problems view)
each initial shape should have a logging control to debug [confirm this, is this a good idea?]

we should have log level (including turn off logging) per generate node.
all nodes should log into the same file prefixed with the generate node name.


Update a food introduction

We can currently do the following operations on the food introduction:

Create
Delete

We should also add the Update operation to the entity.

Hello, i would like to work on this issue.


Simplify logging

Based on discussion in #2023 and #641, Flask interferes too much with logging. This patch greatly reduces the logging configuration that Flask does.

Remove LOGGER_NAME and LOGGER_HANDLER_POLICY configuration.
app.logger is always named 'flask.app'. Use the 'flask' namespace to allow other logging from Flask in the future.
Don't use a Logger subclass to override getEffectiveLevel. Call setLevel when the logger is first accessed, based on app.debug, instead of checking debug for every message.
Only one handler with one format is added, instead of different formats for production and development.
A handler is only added if there are no handlers configured that would handle the logger's getEffectiveLevel.
Handlers are never removed.
The default_handler is accessible so that it can be passed to removeHandler in case the user wants to get rid of the default handler after it is configured.
The proxy stream to environ['wsgi.errors'] is exposed as wsgi_errors_stream, in case the user wants to use it in their own configuration.
Logging documentation is split from error handling documentation and reorganized to address the key concepts.
Added documentation for injecting request information into messages.
Logging tests are split into a separate module.
Some previously miscategorized tests are correctly organized.

Great job with this!

100% coverage on logging.py: https://codecov.io/gh/pallets/flask/pull/2436/src/flask/logging.py?before=flask/logging.py

Am I understanding the new logging docs wrong? I was expecting a different log output with the injected information. https://gist.github.com/behrtam/03b484db328bd1e4c95b201871fe6c15

You didn't log anything with the app logger.

Hello guys! This is just what I need :) However, the changes are not in the latest release v0.12.2. Do you know when there will be a new release?

This is part of the 1.0 milestone. It will be released once that is complete.

So glad many people work on this...
I just experienced Flask for weeks, and I really like it...
I hope I could do more help in this community in the future days...

I am not really sure if the rename of the logger from __name__ to flask.app made sense. previously you were able to have multiple loggers for submodules (myapp.foo, myapp.bar) and their records would all propagate to myapp, which would be the name of the app logger.

I know I had a good reason at the time for changing that, but I can't remember what it was. :-/ I guess it should be ok to add the LOGGER_NAME config back in.


Update the version number in main to reflect the next future release.

Update the version number in main to reflect the next future release.

Jenkins Linux s390x Build #12498 [push] Update the version numbe... started at 21:46

Jenkins Linux amd64 Build #12486 [push] Update the version numbe... started at 20:46

Jenkins Linux ppc64le Build #11491 [push] Update the version numbe... started at 21:55

Jenkins Linux amd64 Build #12486 [push] Update the version numbe... passed after 1 hr 2 min

Jenkins Linux s390x Build #12498 [push] Update the version numbe... passed after 1 hr 26 min

Jenkins Linux ppc64le Build #11491 [push] Update the version numbe... passed after 1 hr 50 min


Missing headers in generated docs (POST, PATCH, etc.)

Description
When specifying custom headers in GET endpoints, the generated documentation is correctly build with the header field separate from the query params. In case of other HTTP Verbs (POST, PATCH, etc.), the documentation incorrectly includes the header in the request body instead of making a header field, though after specifying the inputSources in the config, request works in both cases, including the value in the request body and not in the headers OR including it in the headers and not in the request body.
Expected
Generated documentation should correctly specify the field as a header in case of POST and other HTTP Verbs.
Reproduction
Sample Repo:
https://github.com/boarush/express-zod-api/tree/bug/missing-headers
Have forked this repo and modified the example GET, POST and PATCH endpoints for in the user section.
Context

Node.js version: 20.12.2
express-zod-api version: 19.1.0

Thank you for the wonderful work! Really simple working with the library!

I assume this commit is what illustrates the issue
https://github.com/RobinTail/express-zod-api/commit/ccc098e6621f2d09961900731d0e6ebcb2cef9db

@boarush , this line controls the appearance of the parameter in headers when you generate the documentation:
https://github.com/RobinTail/express-zod-api/blob/78ea9a8c8d4ecd299b5c90a18ecfcb55d5315f9f/src/documentation-helpers.ts#L705-L706
Which means, as described in README, you should:

Enable headers in inputSources;
The header should start with x-.

though after specifying the inputSources in the config, request works in both cases

So... What's the issue with setting inputSources?
Headers in input is the opt-in feature that you can enable that way.
Please clarify.

In the screenshots, you can see that I have specified the x-request-id header as input for both the GET and POST endpoint, however, one shows up correctly as a header in the swagger doc and one only as the part of request body.
Does this example make the problem clear?

Ok. I need to make a test...

On your screenshots both actually appear wrong, @boarush .
Even for GET request it says that the placement is query, but it should be header

And that's very confusing, because for that case I already have a test.

I think I mixed up the screenshots, those were for when I was not including the inputSources. Following are for when I am including the inputSources:

GET is absolutely correct, POST is showing double fields.

I see, it's duplicated, @boarush
Present in both "parameters" and the "body"

Confirmed, @boarush
Thank you so much for informing me and for the detailed explanation.

I think that when getting the requestBody here, it needs to exclude the headers if they're enabled.
https://github.com/RobinTail/express-zod-api/blob/78ea9a8c8d4ecd299b5c90a18ecfcb55d5315f9f/src/documentation.ts#L222-L233

🚀 Should be fixed in v19.1.1, @boarush
In case it's not, please open another issue.
Thank you once again for your contribution!


GET /apis parameters don't work

Describe the bug
cannot filter apis by namespace or fleetnamespace
To Reproduce
Steps to reproduce the behavior:

Run /apis with parameters
See wrong results

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
https://user-images.githubusercontent.com/20525304/187690142-5f230086-558b-45e6-a724-f6e41f56d783.mp4
Desktop (please complete the following information):

Kubernetes version: 1.24
Kube Gateway Version : 1.1.6

If you're querying by fleetnamespace, you also need to provide the fleetname. However, you only need to provide the namespace if your querying by namespace @mortada-codes

@mortada-codes can you confirm the above?
Close the issue if it is no longer applicable


Cypress/E2E: Fix failing tests on MM-T706 and MM-T706

Summary
Fix failing tests on MM-T706 and MM-T706
Ticket Link
none, failing on daily Cypress tests

Yup, you need the webhook server running - https://github.com/mattermost/mattermost-webapp/pull/6139/files#diff-dbe7b346ca5fa5dd87baa3de5670b91cL13

If it's for MM-T706, it's expected. Could you share the more about the failing logs/screenshot?

@saturninoabril Not sure if this is what you need but I'm attaching the cypress log

Oh and it is for MM-T706. However for MM-T707, I'm getting this one,

I'm getting this error when running the test. Not sure what's causing it, but I'm looking into it. Have you seen this?

/update-branch


Content behind login

I would like to scrape a website behind a login form (e.g. http://quotes.toscrape.com/login). Is Dataflowkit able to send forms and keep session information during scrapping? If yes, then how?

OK, will be nice to have at least some alpha version to play with. If you can give me access to the testing version, then I might help with that...

Cookies handling is implemented for base fetcher. You can test it with http://scrape.dataflowkit.org

The video demonstrates data extraction from pages behind login.


Error in running tutorial/hello_world

Hi team,
I came to the step 3 Quantize Model and encountered an issue in the following figure.
Could you help me?  thanks a lot!

Hi @ngdymx
Can you tell me a bit more about your setup that resulted in this error? I'm trying to reproduce it on my end but I don't get the same message?
Here is the quantization settings that are working for me:
vai_q_onnx.quantize_static(
    input_model_path,
    output_model_path,
    calibration_data_reader=None,
    quant_format=vai_q_onnx.QuantFormat.QDQ,
    calibrate_method=vai_q_onnx.PowerOfTwoMethod.MinMSE,
    activation_type=vai_q_onnx.QuantType.QUInt8,
    weight_type=vai_q_onnx.QuantType.QInt8,
    enable_ipu_cnn=True,
    extra_options={'ActivationSymmetric': True}
)

Thanks,
Victoria

Hi,
Thanks.
I just follow the tutorial to setup the environment.
Um, maybe because I'm using a windows system, some paths are not set up very well, it is my guess.
I tried to change the calibrate_method to other mode, it works, wierd.

@ngdymx Just to confirm, the updates are working for you now?

Under the vai_q_onnx.PowerOfTwoMethod.MinMSE:, it still doesn't work.
It works under another mode like vai_q_onnx.PowerOfTwoMethod.NonOverflow:.


Can you send me your Node2vec KDD 16 slides?

I can't find any copy of your node2vec slide at KDD 16 meeting, can you send one ?

http://web.stanford.edu/class/cs224w/slides/19-node2vec.pdf
Mr. Leskovec send me this link , it's great!


NodeJS/React deployment, vscode/gui-git failed to detect renaming of source files

Failed to compile
./src/page.js
Cannot find file: 'RecordAssetValues.js' does not match the corresponding name on disk: './src/recordassetvalues.js'.
This error occurred during the build time and cannot be dismissed.
For some reason file rename (by F2) in VS code source files directory is not always detected by local Git, and deployment fails.
Repro steps:
1 file name RecordAsset.js -> commit git -> deploy -> works
2 rename file to recordasset.js and modify imports to point to 'recordasset' -> commit git -> deploy -> error like above
This may have something to do with the fact that VS code editor has the file open when renaming?

Hi @Kelpieracer
Thanks for reporting this.  Just to make sure I understand the problem, it seems like you're having issues with the Source Control view recognizing your changes.  If that's correct, please file an issue on VS Code (https://github.com/microsoft/vscode) since we don't have any control over this view.
If that's incorrect, then let me know and we'll try to resolve this issue!

Hi @nturinski, I think the problem is in VS Code side (Win). Just guessing, that maybe VS Code caches the file name change when the file is open in the editor, but not edited. So I see that the filename has changed in VS Code folder view, and in the editor tab. But is not actually saved yet to the file system, and therefore Git cannot know about it. I can try to reproduce it again sometime soon.

@Kelpieracer Could you leave an issue on the VS Code repo located here: https://github.com/microsoft/vscode?  They should be the one managing that view.  Unfortunately, our extension has no control over that.
Thanks again for reporting. Closing as external.


UWP .netstandard2 question

I am a user who is waiting on compatibility between SignalR & UWP compiled in .net native (release mode). As I understand from this comment #423 (comment). SignalR is now .netstandard2 compatible,  therefore when UWP is also .netstandard2 compatible, scheduled in this coming Fall Creators Update (as I have read), they should work together. Is this correct?
Will there need to be a new nugget package for this?
Thanks

There won't be a separate NuGet package. Because SignalR client targets netstandard2.0 the package we have should work with UWP.


Unclear description about re-using git credentials from ArgoCD

Describe the bug
By reading through the documentation, I stumbled upon an unclear description about whether the image updater will re-use the git credentials configured in ArgoCD or not.
To Reproduce
https://github.com/argoproj-labs/argocd-image-updater/blob/195c758c2699838390684e2acac71e0ec60eff21/docs/configuration/applications.md#L139-L140
vs.
https://github.com/argoproj-labs/argocd-image-updater/blob/195c758c2699838390684e2acac71e0ec60eff21/docs/configuration/applications.md#L164-L165
Expected behavior
Be more clear.
Additional context
None
Version
Irrelevant as this is docs related.
Logs
None

Oops. Good catch, thanks for calling that out. I believe we must have forgotten to remove the first statement once the feature to re-use Argo CD credentials for Git access was introduced.

I am not sure which one is true as I was having problems getting my repo to update and in an effort to try and get things to work I added a repository credential and it didn't fix my problem.  After looking around I came across this  https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/2.0-2.1/#replacing-repositories-and-repositorycredentials-with-secrets.
Which seems to imply that the credentials in the config map are now deprecated.
In my case, my overlay was not being updated because I had to create the git secret in the argocd namespace and not the namespace where I had my deployment.  ie.  git:secret:argocd/git-creds worked but git:secret:default/git-creds.  Did not work.


Test old components

~Designer previously had no unit tests! we should write tests for the existing components.~
Is your feature request related to a problem? Please describe.
Previously the designer had no unit tests for the react components. Since then, we've added tests using hapi/lab and sinon for stubbing. We found that this was not fit for purpose, so we're now testing react components with Jest + RTL.
Describe the solution you'd like
Refactor the existing tests so they sit closer to the components, and use jest + RTL.
Describe alternatives you've considered
n/a
Additional context
n/a

in progress. P2

@jenbutongit did this get done? It was in progress


test(bts) : bts owner can register a new coin

Feature
Coin and Token Management for NEAR BTS
Scenario
Contract owner can register a new coin

Given

User who is a BTS owner

When

Owner registers a new coin

Then

He should be able to register a new coin successfully

Test Passed. Owner is able to register new coin


chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1909

Questions ?
Please refer to the Backport tool documentation


MOSI cleanup

This PR works to start cleaning up MOSI and the organization of BaseMatrix and MatrixStorage.

Remove BaseMatrix::tileState(int64_t i, int64_t j, int device, MOSI mosi) since it's only purpose appears to be to putting MOSI in an illegal state (3f1afb)

💥 This is a breaking change to the user-accessible API, but if users are calling this function, their code is probably broken anyways

Fix a tile release bug (43e280)

Previously, if origin was invalid and all valid tiles were shared, SLATE would sometimes release the last valid copy of a tile

Make MatrixStorage iterator private to that class and ensure iterators are always protected by the map lock (0506e3)
De-duplicate some duplicated logic

BaseMatrix<scalar_t>::releaseLocalWorkspaceTile checked things that BaseMatrix::tileRelease already checks. (704972)
All of the tileGetFor* routines taking sets of tiles duplicated the same preallocation code (350db3)
The logic to inserting a workspace tile & set its life for receiving remote tiles was duplicated in 3 spots (0506e3)

CI has an error in test_lq for CUDA on leconte:
 ./test_lq
corrupted double-linked list
 *** Process received signal ***
 Signal: Aborted (6)
 Signal code:  (-6)
 [ 0] /lib64/libc.so.6(+0x54df0)[0x7f60ffa06df0]
 [ 1] /lib64/libc.so.6(+0xa154c)[0x7f60ffa5354c]
 [ 2] /lib64/libc.so.6(raise+0x16)[0x7f60ffa06d46]
 [ 3] /lib64/libc.so.6(abort+0xd3)[0x7f60ff9da7f3]
 [ 4] /lib64/libc.so.6(+0x29130)[0x7f60ff9db130]
 [ 5] /lib64/libc.so.6(+0xab617)[0x7f60ffa5d617]
 [ 6] /lib64/libc.so.6(+0xac16c)[0x7f60ffa5e16c]
 [ 7] /lib64/libc.so.6(+0xad1cb)[0x7f60ffa5f1cb]
 [ 8] /lib64/libc.so.6(free+0x55)[0x7f60ffa61955]
 [ 9] ./test_lq(_ZN9__gnu_cxx13new_allocatorISt7complexIfEE10deallocateEPS2_m+0x2f)[0x4d8aa9]
 [10] ./test_lq(_ZNSt16allocator_traitsISaISt7complexIfEEE10deallocateERS2_PS1_m+0x2b)[0x4d2eb0]
 [11] ./test_lq(_ZNSt12_Vector_baseISt7complexIfESaIS1_EE13_M_deallocateEPS1_m+0x32)[0x4cc402]
 [12] ./test_lq(_ZNSt12_Vector_baseISt7complexIfESaIS1_EED2Ev+0x3e)[0x4c532c]
 [13] ./test_lq(_ZNSt6vectorISt7complexIfESaIS1_EED1Ev+0x41)[0x4bd235]
 [14] ./test_lq[0x4b8f1e]
 [15] ./test_lq[0x4ae88b]
 [16] ./test_lq[0x4abc07]
 [17] ./test_lq[0x50e5c9]
 [18] ./test_lq[0x4ac174]
 [19] ./test_lq[0x50eced]
 [20] ./test_lq[0x4ac3b5]
 [21] /lib64/libc.so.6(+0x3feb0)[0x7f60ff9f1eb0]
 [22] /lib64/libc.so.6(__libc_start_main+0x80)[0x7f60ff9f1f60]
 [23] ./test_lq[0x4aabd5]
FAILED : exit code -6

Any ideas?

I think that's referencing to the linked list that manages memory allocations.  So, I'm guessing something wrote past the end of it's valid memory, but I don't know what.  I'll run valgrind and see what shows up.

The tests and unit tests seem to be working fine for both 1 node and 4 nodes.  The CI failure is QR, which is known to sporadically fail.  I'm working on checking a few routines with big matrices on Frontier.
But, if there's nothing else, could you mark this PR as approved @mgates3?


[DevTestLabs] az labs create environment: Fix error creating an environment from an ARM template

Description
Running az labs create environment ... to produce an environment from an ARM template produces an error on azure-cli 2.23.0 as below
cli.azure.cli.core.azclierror: The command failed with an unexpected error. Here is the traceback:
az_command_data_logger: The command failed with an unexpected error. Here is the traceback:
cli.azure.cli.core.azclierror: __init__() takes 1 positional argument but 3 were given
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 657, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 691, in _run_job
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 328, in __call__
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/__init__.py", line 807, in default_command_handler
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/lab/custom.py", line 93, in create_environment
TypeError: __init__() takes 1 positional argument but 3 were given
az_command_data_logger: __init__() takes 1 positional argument but 3 were given
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 657, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 691, in _run_job
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 328, in __call__
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/__init__.py", line 807, in default_command_handler
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/lab/custom.py", line 93, in create_environment
TypeError: __init__() takes 1 positional argument but 3 were given

The error is fixed by making the parameters for creating the type EnvironmentDeploymentProperties from positional parameters to named parameters
Testing Guide
I have made the change and run the command from a VSCode debug session. I can now successfully create an environment.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

DevTestLabs


Properly fail when there are nested columns in a file

Going to generate a Spark output to test against this and write another integration test


updated dependency on sketches-core

Let's use the latest release of sketches-core. The only change required in the Druid code was to implement one more update method, which takes char[]. Historical data must be fully compatible.

was there any change in storage format?
if not then 👍

The serialized format must be the same.

I didn't realize that Druid gets built for both JDK7 and JDK8. Support for JDK7 has been dropped in sketches-core-0.5.0. So if this is a barrier, the latest version we can use is 0.4.1

I was going to work on a new aggregator using latest sketches. This issue makes this plan questionable. Is there a plan to stop building Druid for JDK7?

@AlexanderSaydakov See https://groups.google.com/forum/#!topic/druid-user/aTGQlnF1KLk

@AlexanderSaydakov the approach taken with the caffeine (#3028), which also requires Java 8, is to have that particular extension target Java 8 but the rest of Druid target Java 7.
In this case since the datasketches extension already supported Java 7, we probably want to keep supporting it, but it should be ok to make a new datasketches-xxx extension for your new "xxx" aggregator.

👍  on the update to 0.4.1

👍


CodeCamp #46

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Add typehint for models/utils and others
Modification
Add typehint for models/utils, utils/array_converter.py and models/test_time_augs/merge_augs.py
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

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


feat: telemetry modal

Changes

adds a notification for users who have not interfered with telemetry data

Fixes

fix: #1512

How to test it

if you've played with the telemetry data just add these somewhere in the code the on the next reload the telemetry modal should show
electronStore.delete('appConfig.disableEventTracking'); electronStore.delete('appConfig.disableErrorReporting');

Screenshots

https://user-images.githubusercontent.com/5509112/161067277-58fad75a-d29d-45a4-bfef-c84201efb1c2.mov

Checklist

[x] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

I think these two buttons should disappear after you click on either one of them. What do you think @julioramosest ?

I think these two buttons should disappear after you click on either one of them. What do you think @julioramosest ?

I can delete the notification if the user clicks on either one of those buttons, this is much easier

@andreiv1992 @devcatalin you can choose from one of these options

After click on any option, the buttons are substituted with a plain text that says "Your settings have been saved."
The whole alert is substituted by a text that says "your telemetry settings have been saved."

deleting the whole thing can feel too sudden.

Let me know if this is ok
https://user-images.githubusercontent.com/5509112/161590803-4b3476ed-9a20-476c-b8e4-529dce691810.mov

@andreiv1992 Fine for me, per the video. Thanks!


BootstrapApplicationListener overrides defaultProperties of SpringApplication

We are currently using Gauge for integration tests. To setup spring context we need to start it manually like that:
        context = new SpringApplicationBuilder(Configuration)
                .web(false)
                .profiles(profile1, profile2)
                .properties("environment.type="+environment.type)
                .run()

We are using this custom setting environment.type in our custom EnvironmentPostProcessor.
Now when our EnvironmentPostProcessor gets executed:
public void postProcessEnvironment(ConfigurableEnvironment environment, SpringApplication application) {
        String type = environment.resolvePlaceholders("environment.type");

variable type is empty.
After debugging BootstrapApplicationListener I found out that SpringApplication is recreated here like that:
SpringApplicationBuilder builder = new SpringApplicationBuilder()
.profiles(environment.getActiveProfiles()).bannerMode(Mode.OFF)
.environment(bootstrapEnvironment)
.properties("spring.application.name:" + configName)
.registerShutdownHook(false).logStartupInfo(false).web(false);

and then it is run:
final ConfigurableApplicationContext context = builder.run();

So DefaultProperties from my original SpringApplicationBuilder are not provided to EnvironmentPostProcessor and the only property I see in defaultProperties is: spring.application.name.
As a workaround we need to set this property via System.setProperty.

I think your workaround is fine and this is an edge case that I don't think we want to deal with. Comment if you think otherwise.

I think that is not obvious. SpringApplicationBuilder is public API for creating application and adding spring-cloud dependencies breaks initial feature: adding custom properties to context.
Could you please explain why custom properties from initial builder can not be copied to the new builder?

That particular builder only builds the bootstrap property source. We don't want duplicate properties.

Are you doing something specific in the bootstrap phase?

No, we do not have custom bootstrap logic.
We've been using:
new SpringApplicationBuilder(StepsConfiguration).web(false)
            .profiles(profile1, profile2)
            .properties("property1=value1", "property2=value2")
            .run()

after integration with spring-cloud-starter dependencies -- setup was broken due to missing custom properties.

I don't understand. Those properties get put in the environment, just like bootstrap. Can you show the output of /env?

We have a custom Environment Class which extends StandardEnvironment - We do resolution of credentials through custom conventions that we have defined.
It would be good if there is a way to specify a custom environment class to be instantiated instead of the StandardEnvironment (done in BootstrapApplicationListener.java Line#152 StandardEnvironment bootstrapEnvironment = new StandardEnvironment();) .


Reordered pybind11 definitions for better stubgen

@leemagnusson Can you update the build process to generate type stubs ?
command which I had used:
pybind11-stubgen motor -o ~/Desktop/pyb11stubgen/ --enum-class-locations ModeDesired:motor --enum-class-locations StepperMode:motor
the path for modules might need to change tho via the --root-suffix ROOT_SUFFIX option

@leemagnusson Can you update the build process to generate type stubs ? command which I had used: pybind11-stubgen motor -o ~/Desktop/pyb11stubgen/ --enum-class-locations ModeDesired:motor --enum-class-locations StepperMode:motor
the path for modules might need to change tho via the --root-suffix ROOT_SUFFIX option

I'm not sure how best to do that. It would be easy to add this do the github action and upload it separately. But I'm not sure how to include it in the dpkg or as part of the cmake build process.

Would it possible for you to add it to github actions then? I am caught up
with LDs and Hands right now
On Wed, Aug 28, 2024, 3:43 PM leemagnusson @.***> wrote:

@leemagnusson https://github.com/leemagnusson Can you update the build
process to generate type stubs ? command which I had used: pybind11-stubgen
motor -o ~/Desktop/pyb11stubgen/ --enum-class-locations ModeDesired:motor
--enum-class-locations StepperMode:motor
the path for modules might need to change tho via the --root-suffix
ROOT_SUFFIX option
I'm not sure how best to do that. It would be easy to add this do the
github action and upload it separately. But I'm not sure how to include it
in the dpkg or as part of the cmake build process.
—
Reply to this email directly, view it on GitHub
https://github.com/unhuman-io/motor-realtime/pull/140#issuecomment-2316365198,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJSNZTRCJWKMGO7GKKOTJALZTZHCDAVCNFSM6AAAAABNJAJT26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJWGM3DKMJZHA
.
You are receiving this because you were assigned.Message ID:
@.***>


Protect against null Location in FusedLocationSource

Does any other open PR do the same thing?

No
What issue is this PR fixing?
#3344
How did you test this PR?

Tested on Android Emulator w/ Detox on a CI server where this was previously occurring. The crash does not recur.

@netshade 😻
LGTM @christopherdro 🐽


python: Implement fsspec support

fsspec is widely used in python ecosystem, we can provide support for it.

Hi, I'd love to take a look :)

Hi, I'd love to take a look :)

Thanks a lot for your intetest! Do you have a plan for this issue?

What I have tried to explore so far is to implement a OpenDALFileSystem that inherits from fsspec.AbstractFileSystem. It's just a thin wrapper around opendal.Operator.
By implementing a few methods I was able to get it to work for reading and writing (I have tried fs and gdrive services) within duckdb.
import duckdb
from opendal.fsspec import OpenDALFileSystem

fs = OpenDALFileSystem("fs", root="examples/")
duckdb.register_filesystem(fs)

rel = duckdb.sql("SELECT * FROM 'opendal:///data/example.csv'")
print(rel)

duckdb.execute("COPY (SELECT * FROM 'opendal:///data/example.csv') TO 'opendal:///data/example_copy.json'")

You can find the exploratory implementation in my fork (I can make a PR if it makes things easier)
fsspec exposes a protocol class attribute on the filesystem classes (which I assigned to "opendal"), but looking at the example above I thought it might be interesting to include the name of the service, which would unlock the ability to register different services as fsspec filesystems, and doing operations such as joining data from different services. Something like opendal+<service>?

Perfect, mostly looks good to me! The only issue I'm considering is whether to make it a separate package. This way, users won't need to install fsspec if they don't want it.

fsspec exposes a protocol class attribute on the filesystem classes (which I assigned to "opendal"), but looking at the example above I thought it might be interesting to include the name of the service, which would unlock the ability to register different services as fsspec filesystems, and doing operations such as joining data from different services. Something like opendal+<service>?

Makes sense to me! Users might want to use different services at the same time. opendal-<service> looks good to me.

Perfect, mostly looks good to me! The only issue I'm considering is whether to make it a separate package. This way, users won't need to install fsspec if they don't want it.

Yes we can either do that or have it as an extra that can be installed as such
pip install "opendal[fsspec]"

I feel like we can have an fsspec-opendal like other existing packages. The benefits include:

Simplified Packaging: The opendal package involves complex Rust-related builds. However, fsspec-opendal can be a pure Python package.
Improved Discoverability: Users will find it much easier to integrate opendal with fsspec.
Enhanced Documentation: In the future, we can offer separate documentation for fsspec-opendal.

What do you think?

I agree, seems like a practical first step. I will continue working on this and hopefully send a PR in the coming days.

I agree, seems like a practical first step. I will continue working on this and hopefully send a PR in the coming days.

Great, thanks a lot in advance!

I am happy to help if there's anything I can (from fsspec)

I am happy to help if there's anything I can (from fsspec)

Thank you so much, @martindurant! It's great to see you here.
Do you think it's a good idea to create a fsspec/opendalfs repository so we can develop this together upstream? @wey-gu, @BeautyYuYanli, @3ok, and I are all interested in helping to maintain this project.

I have no preference on where it should live - would be happy to make that repo and add collaborators.

would be happy to make that repo and add collaborators.

Great, let's get started! I'm willing to help set up the initial project layout so we can attract more contributors.

I prefer it to be part of fsspec so that the existing users of fsspec can easily use it after updating, without other changes.

Hello everyone, I'm excited to announce that this project will progress at https://github.com/fsspec/opendalfs
Welcome to join in!


Pattern passes unexpectedly

The following pattern passes with the latest version installed via pip
$ pip3 install stix2-patterns
Requirement already satisfied: stix2-patterns in /usr/local/lib/python3.6/site-packages
Requirement already satisfied: six in /usr/local/lib/python3.6/site-packages (from stix2-patterns)
Requirement already satisfied: antlr4-python3-runtime==4.7; python_version >= "3" in /usr/local/lib/python3.6/site-packages (from stix2-patterns)
$ validate-patterns
Enter a pattern to validate: [file:hashes.'SHA-256' =? 'bf07a7fbb825fc0aae7bf4a1177b2b31fcf8a3feeaf7092761e18c859ee52a9c' OR file:hashes.MD5 = 'cead3f77f6cda6ec00f57d76c9a6879f'] AND [file:hashes.'SHA-256' = 'aec070645fe53ee3b3763059376134f058cc337247c978add178b6ccdfb0019f']

PASS: [file:hashes.'SHA-256' =? 'bf07a7fbb825fc0aae7bf4a1177b2b31fcf8a3feeaf7092761e18c859ee52a9c' OR file:hashes.MD5 = 'cead3f77f6cda6ec00f57d76c9a6879f'] AND [file:hashes.'SHA-256' = 'aec070645fe53ee3b3763059376134f058cc337247c978add178b6ccdfb0019f']

I don't see where =? matches in patterns operator. In our STIX2 Patterns parser, this fails. Our parser has a catch-all pattern at the end that returns an unexpected token. Maybe that would fix this issue for your ANTLR implementation?

Well that's an antlr lexer wrinkle that slipped under the radar... I would have expected the lexer to produce an error instead of silently eating the ?.  Yeah, adding a default lexer rule triggers the expected error.  Thanks for the catch.

@varnerac This should be fixed now, but if not, feel free to reopen.


Add ChenYi015 as member

Contributions:

https://github.com/kubeflow/arena/commits/master/?author=ChenYi015
https://github.com/kubeflow/arena/issues?q=is%3Aissue+author%3AChenYi015
https://github.com/kubeflow/spark-operator/commits/master/?author=ChenYi015
https://github.com/kubeflow/spark-operator/issues?q=is%3Aissue+author%3AChenYi015

Sponsors:

@cheyang
@Syulin7

pytest output:
$ pytest test_org_yaml.py
====================================================== test session starts =======================================================
platform darwin -- Python 3.12.2, pytest-8.2.1, pluggy-1.5.0
rootdir: /Users/chenyi/Code/github.com/kubeflow/internal-acls/github-orgs
collected 1 item

test_org_yaml.py .                                                                                [100%]

======================================================= 1 passed in 0.10s ========================================================

/lgtm
/ok-to-test

/approve


Inclusion in Awesome Blazor's "Libraries and Extensions"

Send a pull request for inclusion in Awesome Blazor's "Libraries and Extensions" section:
https://github.com/AdrienTorris/awesome-blazor#libraries--extensions

Created pull request:

Now published.


minor linting improvements

Just a few small changes so that the files properly lint in my editor (visual studio code).
Sorry, this was such a minor change, I don't know if it is worth a change log or a version bump.

TODO:

[ ] Update CHANGELOG.md with your change (include reference to issue & this PR)
[x] Make sure all of the significant new logic is covered by tests
[ ] Rebase your changes on master so that they can be merged easily
[x] Make sure all tests and linter rules pass

Coverage decreased (-0.4%) to 99.265% when pulling c113ee6a2a6ee7c37954b743c600ee45e44c490b on bkinsey808:minor-linting-improvements into 08414227f6f96d6e18b1b5d05b48be843cd91899 on apollostack:master.

It's fine, no need to bump versions. Thanks a lot, especially for updating versions in package.json


It’s not syncing fonts colours dynamically with device theme

Describe the bug
Font colour is not syncing with device theme.
Expected behavior
It’s should be dynamic like Black Font for Light theme and White Font for Dark Theme.

It's an image, so it can't do it automatically, but there are instructions in the faq
https://github.com/DenverCoder1/readme-typing-svg/blob/main/docs%2Ffaq.md


Parse Environment variables to PHP Data Types

Hi guys,
I wrote a library to get values from environment variables and parse to the PHP data types. This library can be used to parse environment variables to PHP data types (like the casting to integer, float, null, boolean), parse the complex data structures like a JSON string and more with the contribution of the commnunity.
I opened a issue to phpdotenv project, and it was accept:
https://github.com/vlucas/phpdotenv/issues/121
Actually your code is used to parse some values here (boolean, empty and null):
https://github.com/laravel/framework/blob/5.1/src/Illuminate/Foundation/helpers.php#L292
I suggest to implement my library and put the responsability on it (my library is 100% covered by php unit tests and is following the PHP-FIG patterns PSR-2 and PSR-4).
Thanks! I appreciate your suggestions.

Thanks, but this can be tracked on the phpdotenv repo.

@GrahamCampbell @taylorotwell i believe that this component is interest to this project. The focus of phpdotenv project is load the environment variables and not get your values. Different of your purpose, where is necessary get the data and frequently pass on validation process like the if statement.
By example:
export ENV_BOOLEAN_TRUE=true
export ENV_BOOLEAN_FALSE=false
// the expression result true
if (Environment::get("ENV_BOOLEAN_TRUE")) { ... }
// the expression result false
if (Environment::get("ENV_BOOLEAN_FALSE")) { ... }
Otherwise without this library:
export ENV_BOOLEAN_TRUE=true
export ENV_BOOLEAN_FALSE=false
// the expression result true
if (getenv("ENV_BOOLEAN_TRUE") === "true") { ... }
// the expression result true
if (getenv("ENV_BOOLEAN_FALSE") === "false") { ... }
It is a simple example, and the library supports more resource types, like: boolean, numeric (int and float), null, json, array and unknown. See the https://github.com/jpcercal/environment/blob/master/README.md to more details.
Thanks.

i believe that this component is interest to this project.

Yes, but if you want that changing, it needs doing on that repo. I'm a collaborator there too.

Why is it needed to do this?

?


Set default PX4 parameters at first.

1.To avoid read param fail cause issue,
set default px4 parameters at first.

We've seen this issue too. We need to be careful with loading the defaults though, because it might lead to unsafe behavior until the real values are loaded. We need to investigate why this takes so long - it should take less than 100ms for all of the data to be loaded. I guess there are dropped messages or something similar.

This is fixed by #421


feat(shell): support resolve IP address in some shell commands

What problem does this PR solve?
What is changed and how it works?
Add support resolve IP address in some shell commands
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)

>>> cluster_info temp -r
[cluster_info]
meta_servers                  : smilencer-OptiPlex-7040:34601,smilencer-OptiPlex-7040:34602,smilencer-OptiPlex-7040:34603
primary_meta_server           : smilencer-OptiPlex-7040:34601
zookeeper_hosts               : <IP_ADDRESS>:22181
zookeeper_root                : /pegasus/onebox/<IP_ADDRESS>
meta_function_level           : steady
balance_operation_count       : move_pri=0,copy_pri=0,copy_sec=0,total=0
primary_replica_count_stddev  : 0.00
total_replica_count_stddev    : 0.00

>>> app temp -r
[parameters]
app_name  : temp
detailed  : true

[general]
app_name           : temp
app_id             : 2
partition_count    : 8
max_replica_count  : 3

[replicas]
pidx  ballot  replica_count  primary                        secondaries
0     3       3/3            smilencer-OptiPlex-7040:34801  [smilencer-OptiPlex-7040:34803,smilencer-OptiPlex-7040:34802]
1     3       3/3            smilencer-OptiPlex-7040:34802  [smilencer-OptiPlex-7040:34801,smilencer-OptiPlex-7040:34803]
2     3       3/3            smilencer-OptiPlex-7040:34803  [smilencer-OptiPlex-7040:34802,smilencer-OptiPlex-7040:34801]
3     3       3/3            smilencer-OptiPlex-7040:34801  [smilencer-OptiPlex-7040:34803,smilencer-OptiPlex-7040:34802]
4     3       3/3            smilencer-OptiPlex-7040:34802  [smilencer-OptiPlex-7040:34801,smilencer-OptiPlex-7040:34803]
5     3       3/3            smilencer-OptiPlex-7040:34803  [smilencer-OptiPlex-7040:34802,smilencer-OptiPlex-7040:34801]
6     3       3/3            smilencer-OptiPlex-7040:34801  [smilencer-OptiPlex-7040:34803,smilencer-OptiPlex-7040:34802]
7     3       3/3            smilencer-OptiPlex-7040:34802  [smilencer-OptiPlex-7040:34801,smilencer-OptiPlex-7040:34803]

[nodes]
node                           primary  secondary  total
smilencer-OptiPlex-7040:34801  3        5          8
smilencer-OptiPlex-7040:34802  3        5          8
smilencer-OptiPlex-7040:34803  2        6          8
                               8        16         24

[healthy]
fully_healthy_partition_count    : 8
unhealthy_partition_count        : 0
write_unhealthy_partition_count  : 0
read_unhealthy_partition_count   : 0

>>> app_disk temp -r
[parameters]
app_name  : temp
detailed  : true

[result]
app_name                            : temp
app_id                              : 2
partition_count                     : 8
max_replica_count                   : 3
disk_used_for_primary_replicas(MB)  : 0.00
disk_used_for_all_replicas(MB)      : 0.00
partitions not counted              : 0/8
replicas not counted                : 0/24

[details]
pidx  ballot  replica_count  primary                              secondaries
0     3       3/3            smilencer-OptiPlex-7040:34801(0,#0)  [smilencer-OptiPlex-7040:34803(0,#0),smilencer-OptiPlex-7040:34802(0,#0)]
1     3       3/3            smilencer-OptiPlex-7040:34802(0,#0)  [smilencer-OptiPlex-7040:34801(0,#0),smilencer-OptiPlex-7040:34803(0,#0)]
2     3       3/3            smilencer-OptiPlex-7040:34803(0,#0)  [smilencer-OptiPlex-7040:34802(0,#0),smilencer-OptiPlex-7040:34801(0,#0)]
3     3       3/3            smilencer-OptiPlex-7040:34801(0,#0)  [smilencer-OptiPlex-7040:34803(0,#0),smilencer-OptiPlex-7040:34802(0,#0)]
4     3       3/3            smilencer-OptiPlex-7040:34802(0,#0)  [smilencer-OptiPlex-7040:34801(0,#0),smilencer-OptiPlex-7040:34803(0,#0)]
5     3       3/3            smilencer-OptiPlex-7040:34803(0,#0)  [smilencer-OptiPlex-7040:34802(0,#0),smilencer-OptiPlex-7040:34801(0,#0)]
6     3       3/3            smilencer-OptiPlex-7040:34801(0,#0)  [smilencer-OptiPlex-7040:34803(0,#0),smilencer-OptiPlex-7040:34802(0,#0)]
7     3       3/3            smilencer-OptiPlex-7040:34802(0,#0)  [smilencer-OptiPlex-7040:34801(0,#0),smilencer-OptiPlex-7040:34803(0,#0)]

>>> nodes -r
[details]
address                        status
smilencer-OptiPlex-7040:34801  ALIVE
smilencer-OptiPlex-7040:34802  ALIVE
smilencer-OptiPlex-7040:34803  ALIVE

[summary]
total_node_count    : 3
alive_node_count    : 3
unalive_node_count  : 0

>>> server_info -r
COMMAND: server-info

CALL [meta-server] [localhost:34601] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08
CALL [meta-server] [localhost:34602] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08
CALL [meta-server] [localhost:34603] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34801] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34802] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34803] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08

Succeed count: 6
Failed count: 0

No code

Code changes

Has exported function/method change
Has exported variable/fields change
Has interface methods change
Has persistent data change

Side effects

Possible performance regression
Increased code complexity
Breaking backward compatibility

Related changes

Need to cherry-pick to the release branch
Need to update the documentation
Need to be included in the release note

server_info -r
COMMAND: server-info
CALL [meta-server] [localhost:34601] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08
CALL [meta-server] [localhost:34602] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08
CALL [meta-server] [localhost:34603] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34801] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34802] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34803] succeed: Pegasus Server 1.12.SNAPSHOT (79535a83b8bf972cb4e5e711cab8191c6beb069f) Release, Started at 2019-11-19 11:28:08
Succeed count: 6
Failed count: 0

这里为什么meta-server都没有变成hostname？

server_info -r
COMMAND: server-info
CALL [meta-server] [localhost:34601] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [meta-server] [localhost:34602] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [meta-server] [localhost:34603] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34801] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34802] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34803] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
Succeed count: 6
Failed count: 0

这里为什么meta-server都没有变成hostname？

server_info -r
COMMAND: server-info
CALL [meta-server] [localhost:34601] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [meta-server] [localhost:34602] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [meta-server] [localhost:34603] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34801] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34802] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34803] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
Succeed count: 6
Failed count: 0

这里为什么meta-server都没有变成hostname？

localhost是被<IP_ADDRESS>解析出来的，smilencer-OptiPlex-7040:34803这个域名是被本机ip解析出来的

server_info -r
COMMAND: server-info
CALL [meta-server] [localhost:34601] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [meta-server] [localhost:34602] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [meta-server] [localhost:34603] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34801] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34802] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
CALL [replica-server] [smilencer-OptiPlex-7040:34803] succeed: Pegasus Server 1.12.SNAPSHOT (79535a8) Release, Started at 2019-11-19 11:28:08
Succeed count: 6
Failed count: 0

这里为什么meta-server都没有变成hostname？

localhost是被<IP_ADDRESS>解析出来的，smilencer-OptiPlex-7040:34803这个域名是被本机ip解析出来的


Date

I just have one question. Can I change date language from English to (in my end) Spanish?

Yes you can. Polybar has a locale option as part of the bar configuration. For you the correct setting would probably be locale = es_ES.UTF-8

That did the trick. Thanks!


check that we are appropriately handling  plot.xy dispatch

plot.xy(xy, type, pch = par("pch"), lty = par("lty"),
        col = par("col"), bg = NA,
        cex = 1, lwd = par("lwd"), ...)

I have created a test for this. Will be in next push


feat(linter/import) support check re-export in named

#2769  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite


Downloading playlist from Pornhub

i am trying to download playlist but failing all the time
youtube-dl https://www.pornhub.com/playlist/34691191 --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://www.pornhub.com/playlist/34691191', '--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2019.04.07
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.17134
[debug] exe versions: none
[debug] Proxy map: {}
[PornHubPlaylist] 34691191: Downloading webpage
ERROR: Unable to download webpage: <urlopen error [Errno 11001] getaddrinfo failed> (caused by URLError(gaierror(11001, 'getaddrinfo failed'),))
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpspbwh57p\build\youtube_dl\extractor\common.py", line 626, in _request_webpage
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpspbwh57p\build\youtube_dl\YoutubeDL.py", line 2227, in urlopen
File "C:\Python\Python34\lib\urllib\request.py", line 464, in open
File "C:\Python\Python34\lib\urllib\request.py", line 482, in _open
File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpspbwh57p\build\youtube_dl\utils.py", line 1140, in https_open
File "C:\Python\Python34\lib\urllib\request.py", line 1185, in do_open

Network issue on your side.

Network issue on your side.

but it's downloading videos from youtube with idm and even i can download with savido.net
but with that i can only download single video


Question: Camera vertical field of view

A Question about the field of view of cameras in Carla.
When setting the fov parameter it sets both the horizontal as well as the vertical fov. Is there any possibility to set them individually?

Hi @FranekStark,
We are using unreal's default cameras and the Field of View they allow to modify only changes horizontal fov

The FOV is fixed, but as the viewport size changes, the aspect ratio is allowed to change, adjusting how much you see in the non-constrained axis. FOV can be expressed either as a fixed horizontal FOV or a fixed vertical FOV, and the engine currently uses fixed horizontal FOV, so the vertical FOV changes as the aspect ratio changes.
I found a video that might be helpful if you want to modify carla's unreal project. But for now, you can't set the vFOV individually from the API
https://www.youtube.com/watch?v=ZVEfspETs84&ab_channel=HarryPearce

@Madecu thanks a lot for your explanations. As the fov and the ratio are related to each other it makes indeed a lot of sense to set the v-fov via the image ratio.

Does this then imply square pixels?


[Fix] Classes : about.md is empty.

Again. I'll never learn it.

introduction.md needs to be copied.

on it.  😉   ... but perhaps we should template it, so that at minimum it copies introduction.md??

I always leave it out, so the main discussion is not spread over two almost identical files.
Then I promise to add it after the introduction.md is done.

🤔   I wonder if adding a comment to the empty file when its created would help?  Something like:
Note: Once the introduction.md is complete, copy it here.

I would like to have a template for the about.md file, like the one in configlet that builds the introduction for exercises


intall fastlane error

ERROR:  While executing gem ... (Gem::DependencyError)
Unable to resolve dependencies: fastlane requires commander-fastlane (< 5.0.0, >= 4.4.5), fastimage (< 3.0.0, >= 2.1.0), google-api-client (< 0.13.0, >= 0.12.0)

Do you use a Gemfile? Can you run bundle update?

Here is more information on this topic https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile

@KrauseFx @fastlane-bot Thanks! I had Changed the gem sources to "https://rubygems.org/" and had solved this issues.

Awesome :+1:


support numpy int dtypes in shapes

One of two very small issues I ran into trying to run an existing code base on keras 3. This allows passing a tuple of numpy (or any other valid) int types to Input(shape=...). I am preloading some data to generate the model shape on the fly, and the lib I'm using to wrangle that data happens to output shape as numpy ints.

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (d7268f3) 79.37% compared to head (12e2385) 55.90%.
Report is 2 commits behind head on master.

Files
Patch %
Lines

keras/backend/common/variables.py
33.33%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #18850       +/-   ##
===========================================
- Coverage   79.37%   55.90%   -23.47%
===========================================
  Files         336      336
  Lines       34778    34780        +2
  Branches     6841     6842        +1
===========================================
- Hits        27605    19444     -8161
- Misses       5590    13859     +8269
+ Partials     1583     1477      -106

Flag
Coverage Δ

keras
55.90% <33.33%> (-23.34%)
:arrow_down:

keras-jax
?

keras-numpy
55.90% <33.33%> (-0.01%)
:arrow_down:

keras-tensorflow
?

keras-torch
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


UI: bulk action support for various resources

Description
This PR supports ui bulk action for various resources. Following are addressed as part of this PR:

Bulk action support for various resources
Suppression of notification pop up (that appears on the top right corner of the screen) for async jobs in case the operation progress modal is open
Router links added to notification list for failed jobs/operations
Progress View - would have a filter column to filter the jobs by state
Cancel will be the default button for bulk operations
Different hue used for alert message for destructive bulk operations - like delete, stop, i,e, those that could lead to a possible down-time - to indicate to the users that such actions need to be performed with caution

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[X] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[X] Major
[ ] Minor

Screenshots (if appropriate):
How Has This Been Tested?

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5034 (SL-JID-189)

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5034 (SL-JID-205)

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5034 (SL-JID-216)

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5034 (SL-JID-223)

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5034 (SL-JID-230)

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5034 (SL-JID-236)

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5034 (SL-JID-250)

@blueorangutan package

@vladimirpetrov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 323

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5034 (SL-JID-282)

@blueorangutan package

@vladimirpetrov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: centos7 :heavy_check_mark: centos8 :heavy_check_mark: debian. SL-JID 391

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5034 (SL-JID-325)

@Pearl1594 can you look at the conflicts?

@blueorangutan ui

@Pearl1594 a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

Done @DaanHoogland

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5034 (SL-JID-364)


Allow specifying custom port for fn start

This resolves #247

We could easily extend this to support multiple instances. With the contexts support in the CLI we could also allow specifying a context name to fn start and start containers with the context name in the name. We could also then populate a context configuration file for each started fn server.


Hide "Max Rate Hz" if "Max Rate" is unchecked when importing WAV sample

Max Rate Hz has no effect when Max Rate is unchecked, so it shouldn't be displayed in this case.

Thanks!


Build failed when using searchable_dropdown

I have used the searchable dropdown in one of my pages. My application is working fine in debug mode so I can run it on an emulator. But I'm getting my build failed when trying to build the apk using "flutter build apk" command.
Here is the error log I'm getting.

e: C:\flutter.pub-cache\hosted\pub.dartlang.org\searchable_dropdown-1.1.3\android\src\main\kotlin\bsi\iceman\searchable_dropdown\SearchableDropdownPlugin.kt: (3, 28): Unresolved reference: NonNull
e: C:\flutter.pub-cache\hosted\pub.dartlang.org\searchable_dropdown-1.1.3\android\src\main\kotlin\bsi\iceman\searchable_dropdown\SearchableDropdownPlugin.kt: (19, 36): Unresolved reference: NonNull
e: C:\flutter.pub-cache\hosted\pub.dartlang.org\searchable_dropdown-1.1.3\android\src\main\kotlin\bsi\iceman\searchable_dropdown\SearchableDropdownPlugin.kt: (41, 30): Unresolved reference: NonNull
e: C:\flutter.pub-cache\hosted\pub.dartlang.org\searchable_dropdown-1.1.3\android\src\main\kotlin\bsi\iceman\searchable_dropdown\SearchableDropdownPlugin.kt: (41, 57): Unresolved reference: NonNull
e: C:\flutter.pub-cache\hosted\pub.dartlang.org\searchable_dropdown-1.1.3\android\src\main\kotlin\bsi\iceman\searchable_dropdown\SearchableDropdownPlugin.kt: (49, 38): Unresolved reference: NonNull

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':compileReleaseKotlin'.

Compilation error. See log for more details

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 2s
The plugin searchable_dropdown could not be built due to the issue above.

flutter doctor -v output

[√] Flutter (Channel stable, v1.12.13+hotfix.8, on Microsoft Windows [Version 10.0.18363.752], locale en-US)
• Flutter version 1.12.13+hotfix.8 at C:\flutter
• Framework revision 0b8abb4724 (8 weeks ago), 2020-02-11 11:44:36 -0800
• Engine revision e1e6ced81d
• Dart version 2.7.0

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
• Android SDK at C:\Users\tharindu.s.GEVEO\AppData\Local\Android\Sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.3
• ANDROID_HOME = C:\Users\tharindu.s.GEVEO\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
• All Android licenses accepted.
[!] Android Studio (version 3.6)
• Android Studio at C:\Program Files\Android\Android Studio
X Flutter plugin not installed; this adds Flutter specific functionality.
X Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
[√] VS Code (version 1.43.2)
• VS Code at C:\Users\tharindu.s.GEVEO\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.9.1
[√] VS Code, 64-bit edition
• VS Code at C:\Program Files\Microsoft VS Code
• Flutter extension version 3.9.1
[√] Connected device (1 available)
• Android SDK built for x86 • emulator-5554 • android-x86 • Android 10 (API 29) (emulator)
! Doctor found issues in 1 category.

Hello @Tharindu-Diluksha ,
Thanks for reporting this issue!
I am trying to upgrade my tools to see if I can reproduce your issue this way.
In the meantime, would you like to share a minimal project with this issue so that I can try it for myself?

So far, I didn't find a way to reproduce.
An example project would probably help.

@lcuis I have found a few more issues related to appcenter (We are also using appcenter). Can this be a problem for me? Since the build issue was never there before integrating the searchable_dropdown.
Can you give any insights? Thanks

FAILURE: Build completed with 3 failures.

1: Task failed with an exception.

What went wrong:
Execution failed for task ':appcenter:verifyReleaseResources'.

A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
Android resource linking failed
C:\Users\tharindu.s.GEVEO.gradle\caches\transforms-2\files-2.1\0a271e99b6771ad4a84318244d532fb7\core-1.0.0\res\values\values.xml:57:5-88:25: AAPT: error: resource android:attr/fontVariationSettings not found.

 C:\Users\tharindu.s.GEVEO\.gradle\caches\transforms-2\files-2.1\0a271e99b6771ad4a84318244d532fb7\core-1.0.0\res\values\values.xml:57:5-88:25: AAPT: error: resource android:attr/ttcIndex not found.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.

What went wrong:
Execution failed for task ':appcenter_analytics:verifyReleaseResources'.

A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
Android resource linking failed
C:\Users\tharindu.s.GEVEO.gradle\caches\transforms-2\files-2.1\0a271e99b6771ad4a84318244d532fb7\core-1.0.0\res\values\values.xml:57:5-88:25: AAPT: error: resource android:attr/fontVariationSettings not found.

 C:\Users\tharindu.s.GEVEO\.gradle\caches\transforms-2\files-2.1\0a271e99b6771ad4a84318244d532fb7\core-1.0.0\res\values\values.xml:57:5-88:25: AAPT: error: resource android:attr/ttcIndex not found.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

3: Task failed with an exception.

What went wrong:
Execution failed for task ':appcenter_crashes:verifyReleaseResources'.

A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
Android resource linking failed
C:\Users\tharindu.s.GEVEO.gradle\caches\transforms-2\files-2.1\0a271e99b6771ad4a84318244d532fb7\core-1.0.0\res\values\values.xml:57:5-88:25: AAPT: error: resource android:attr/fontVariationSettings not found.

 C:\Users\tharindu.s.GEVEO\.gradle\caches\transforms-2\files-2.1\0a271e99b6771ad4a84318244d532fb7\core-1.0.0\res\values\values.xml:57:5-88:25: AAPT: error: resource android:attr/ttcIndex not found.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

Get more help at https://help.gradle.org

BUILD FAILED in 1m 17s

Hello @Tharindu-Diluksha ,
Thanks for this additional information.
I don't know whether using appcenter could be an issue, I never used it so far.
I have a few questions that may help solving this issue:

Do those errors occur only when adding searchable_dropdown?
Did you try this solution? https://github.com/crosswalk-project/cordova-plugin-crosswalk-webview/issues/205#issuecomment-371669478
Would you like to share a minimal failing project so that I can try to reproduce?

Hi @lcuis Thanks for your quick reply.

Yes the error occurs only after adding searchable_dropdown.
No, since it is related to cordova plugin.
I have created a minimal failing project In https://github.com/Tharindu-Diluksha/test-searchable-dropdown

In the repository, the master branch includes the searchable_dropdown and there is the build failure.
Also, there is another branch ("without-searchable-dropdown") without the searchable_dropdown and it can be built successfully.
(In both branches I'm getting the appcenter related issue but I think that has nothing to do with this since the code in "without-searchable-dropdown" branch can be built successfully using "flutter build apk" command.)

Hello @Tharindu-Diluksha ,
Thank you very much for sharing the project with me!
I confirm that I can reproduce the issue with this project:
~/AndroidStudioProjects/test-searchable-dropdown$ flutter build apk
You are building a fat APK that includes binaries for android-arm, android-arm64, android-x64.
If you are deploying the app to the Play Store, it's recommended to use app bundles or split the APK to reduce the APK size.
    To generate an app bundle, run:
        flutter build appbundle --target-platform android-arm,android-arm64,android-x64
        Learn more on: https://developer.android.com/guide/app-bundle
    To split the APKs per ABI, run:
        flutter build apk --target-platform android-arm,android-arm64,android-x64 --split-per-abi
        Learn more on:  https://developer.android.com/studio/build/configure-apk-splits#configure-abi-split
Running Gradle task 'assembleRelease'...                                                                                Note: /home/lcuis/progs/flutter/.pub-cache/hosted/pub.dartlang.org/appcenter-0.2.1/android/src/main/java/com/aloisdeniel/flutter/appcenter/AppcenterPlugin.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Calling mockable JAR artifact transform to create file: /home/lcuis/.gradle/caches/transforms-2/files-2.1/98f3f4a6433e701e219fb48a51099b4f/android.jar with input /home/lcuis/progs/AndroidSDK/platforms/android-27/android.jar
Removed unused resources: Binary resource data reduced from 46KB to 37KB: Removed 19%

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':appcenter:verifyReleaseResources'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > Android resource linking failed
     /home/lcuis/.gradle/caches/transforms-2/files-2.1/a528b13ac93e64cafa3d0480e2c93207/core-1.1.0/res/values/values.xml:142:5-173:25: AAPT: error: resource android:attr/fontVariationSettings not found.

     /home/lcuis/.gradle/caches/transforms-2/files-2.1/a528b13ac93e64cafa3d0480e2c93207/core-1.1.0/res/values/values.xml:142:5-173:25: AAPT: error: resource android:attr/ttcIndex not found.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':appcenter_analytics:verifyReleaseResources'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > Android resource linking failed
     /home/lcuis/.gradle/caches/transforms-2/files-2.1/a528b13ac93e64cafa3d0480e2c93207/core-1.1.0/res/values/values.xml:142:5-173:25: AAPT: error: resource android:attr/fontVariationSettings not found.

     /home/lcuis/.gradle/caches/transforms-2/files-2.1/a528b13ac93e64cafa3d0480e2c93207/core-1.1.0/res/values/values.xml:142:5-173:25: AAPT: error: resource android:attr/ttcIndex not found.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

BUILD FAILED in 2m 25s
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done                     146.3s (!)
The built failed likely due to AndroidX incompatibilities in a plugin. The tool is about to try using Jetfier to solve the incompatibility.
Building plugin appcenter...
Running Gradle task 'assembleAarRelease'...                            ⣯

Running Gradle task 'assembleAarRelease'... Done                  326.3s (!)
✓ Built build/app/outputs/repo.
Building plugin appcenter_analytics...
Running Gradle task 'assembleAarRelease'...
Running Gradle task 'assembleAarRelease'... Done                    2.9s
✓ Built build/app/outputs/repo.
Building plugin appcenter_crashes...
Running Gradle task 'assembleAarRelease'...
Running Gradle task 'assembleAarRelease'... Done                    2.3s
✓ Built build/app/outputs/repo.
Building plugin searchable_dropdown...
Running Gradle task 'assembleAarRelease'...
Running Gradle task 'assembleAarRelease'... Done                    2.3s
> Task :assembleAarRelease UP-TO-DATE
> Task :preBuild UP-TO-DATE
> Task :preReleaseBuild UP-TO-DATE
> Task :compileReleaseAidl NO-SOURCE
> Task :compileReleaseRenderscript NO-SOURCE
> Task :checkReleaseManifest
> Task :generateReleaseBuildConfig
> Task :generateReleaseResValues
> Task :generateReleaseResources
> Task :packageReleaseResources
> Task :mergeReleaseShaders
> Task :compileReleaseShaders
> Task :generateReleaseAssets
> Task :packageReleaseAssets
> Task :parseReleaseLibraryResources
> Task :packageReleaseRenderscript NO-SOURCE
> Task :processReleaseJavaRes NO-SOURCE
> Task :mergeReleaseJniLibFolders
> Task :prepareLintJarForPublish
> Task :processReleaseManifest
> Task :generateReleaseRFile

> Task :compileReleaseKotlin FAILED

> Task :mergeReleaseNativeLibs
> Task :stripReleaseDebugSymbols
> Task :transformNativeLibsWithSyncJniLibsForRelease
16 actionable tasks: 16 executed

e: /home/lcuis/progs/flutter/.pub-cache/hosted/pub.dartlang.org/searchable_dropdown-1.1.3/android/src/main/kotlin/bsi/iceman/searchable_dropdown/SearchableDropdownPlugin.kt: (3, 28): Unresolved reference: NonNull
e: /home/lcuis/progs/flutter/.pub-cache/hosted/pub.dartlang.org/searchable_dropdown-1.1.3/android/src/main/kotlin/bsi/iceman/searchable_dropdown/SearchableDropdownPlugin.kt: (19, 36): Unresolved reference: NonNull
e: /home/lcuis/progs/flutter/.pub-cache/hosted/pub.dartlang.org/searchable_dropdown-1.1.3/android/src/main/kotlin/bsi/iceman/searchable_dropdown/SearchableDropdownPlugin.kt: (41, 30): Unresolved reference: NonNull
e: /home/lcuis/progs/flutter/.pub-cache/hosted/pub.dartlang.org/searchable_dropdown-1.1.3/android/src/main/kotlin/bsi/iceman/searchable_dropdown/SearchableDropdownPlugin.kt: (41, 57): Unresolved reference: NonNull
e: /home/lcuis/progs/flutter/.pub-cache/hosted/pub.dartlang.org/searchable_dropdown-1.1.3/android/src/main/kotlin/bsi/iceman/searchable_dropdown/SearchableDropdownPlugin.kt: (49, 38): Unresolved reference: NonNull

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileReleaseKotlin'.
> Compilation error. See log for more details

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2s

The plugin searchable_dropdown could not be built due to the issue above.
~/AndroidStudioProjects/test-searchable-dropdown$

This is good news. I'll try to understand better the issue and look for a solution.

All the error messages disappear when I comment out the 3 appcenterrelated lines in the pubspec.yaml file:
flutter build apk
You are building a fat APK that includes binaries for android-arm, android-arm64, android-x64.
If you are deploying the app to the Play Store, it's recommended to use app bundles or split the APK to reduce the APK size.
    To generate an app bundle, run:
        flutter build appbundle --target-platform android-arm,android-arm64,android-x64
        Learn more on: https://developer.android.com/guide/app-bundle
    To split the APKs per ABI, run:
        flutter build apk --target-platform android-arm,android-arm64,android-x64 --split-per-abi
        Learn more on:  https://developer.android.com/studio/build/configure-apk-splits#configure-abi-split
Removed unused resources: Binary resource data reduced from 45KB to 37KB: Removed 19%
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done                      41.9s
✓ Built build/app/outputs/apk/release/app-release.apk (16.2MB).

Here is an issue that seems to be related:
https://github.com/flutter/flutter/issues/46873
I tried the following commands which took quite some time to execute:
flutter clean
flutter pub cache repair

I still had the same errors with the 3 appcenter lines.
So I tried the following commands:
flutter channel master
flutter upgrade
flutter clean
flutter build apk

Still had the same errors.
Sorry, I'm not familiar with appcenter. Is there a configuration file that we can change to try to solve this issue from the appcenter perspective?

@lcuis Thank you very much. I'll try to investigate further and resolve this with appcenter.


Add: 3MTT_QuestionPool_AIML

Question pool on the AI/ML track for the 3MTT program.

Commit passed guideline review. Waiting on other expert for question quality review.