Streamlit UI bug for Slack source

dlt version
0.4.7
Describe the problem
I am using dlt to load data from the Slack source to DuckDB. Then, I'm viewing the data in the Streamlit UI with dlt pipeline slack show. The table $CHANNEL_NAME_channel_join has errors. Due to the nature of Streamlit (render top to bottom), subsequent tables are not loaded nor displayed.
Expected behavior
The UI works properly when downgrading via pip install dlt==0.4.6

Full trace available in the UI
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 584, in _run_script
    exec(code, module.__dict__)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/dlt/helpers/streamlit_app/pages/dashboard.py", line 53, in <module>
    render_with_pipeline(show)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/dlt/helpers/streamlit_app/utils.py", line 38, in render_with_pipeline
    render_func(pipeline)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/dlt/helpers/streamlit_app/pages/dashboard.py", line 49, in show
    write_data_explorer_page(pipeline)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/dlt/helpers/streamlit_app/pages/dashboard.py", line 37, in write_data_explorer_page
    list_table_hints(pipeline, tables)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/dlt/helpers/streamlit_app/blocks/table_hints.py", line 59, in list_table_hints
    resource_state_info(
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/dlt/helpers/streamlit_app/blocks/resource_state.py", line 28, in resource_state_info
    spec = yaml.safe_dump(resource)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/__init__.py", line 269, in safe_dump
    return dump_all([data], stream, Dumper=SafeDumper, **kwds)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/__init__.py", line 241, in dump_all
    dumper.represent(data)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 27, in represent
    node = self.represent_data(data)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 48, in represent_data
    node = self.yaml_representers[data_types[0]](self, data)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 207, in represent_dict
    return self.represent_mapping('tag:yaml.org,2002:map', data)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 118, in represent_mapping
    node_value = self.represent_data(item_value)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 48, in represent_data
    node = self.yaml_representers[data_types[0]](self, data)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 207, in represent_dict
    return self.represent_mapping('tag:yaml.org,2002:map', data)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 118, in represent_mapping
    node_value = self.represent_data(item_value)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 48, in represent_data
    node = self.yaml_representers[data_types[0]](self, data)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 207, in represent_dict
    return self.represent_mapping('tag:yaml.org,2002:map', data)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 118, in represent_mapping
    node_value = self.represent_data(item_value)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 58, in represent_data
    node = self.yaml_representers[None](self, data)
File "/home/tjean/projects/dagworks/hamilton/examples/dlt/venv/lib/python3.10/site-packages/yaml/representer.py", line 231, in represent_undefined
    raise RepresenterError("cannot represent an object", data)

Steps to reproduce
My pipeline code
slack_pipeline = dlt.pipeline(
    pipeline_name="slack",
    destination='duckdb',
    dataset_name="slack_data",
    full_refresh=True,
)

dlt_source = slack.slack_source(selected_channels=["general", "dlt"], replies=True)

Operating system
Linux
Runtime environment
Local
Python version
3.10
dlt data source
dlt verified source for Slack
dlt destination
DuckDB
Other deployment details
No response
Additional information
It works properly for v0.4.6

Fix has been merged and will be available in the new version


[Bug Report] Slider show input setting Too strong, can't set width

Element UI version
2.4.1
OS/Browsers version
windows7 chrome67
Vue version
2.5.2
Reproduction Link
https://jsfiddle.net/2e1y97sm/
Steps to reproduce
Using the Slider component, the outer layer width is 250px
What is Expected?
Ability to set the width of the show-input
What is actually happening?
Unable to set the width of show-input

This is the effect of eqxiu which i wanted. :

I used element-ui and have divided it into two lines. The effect is still so bad.
Can element ui do a better job? So many pits

Sorry about that, UI library may not cover every case. In this case, you can overwrite the CSS.

@jikkai 好坑好坑


Add basic Calmscan functionality

Scans files when uploaded. As requested in #97
Uses: https://github.com/kylefarris/clamscan
Requires: clamav installed.

Base is changing, will review this functionality again once I merge into master


Allow Cloudflare Pages Adapter To Use .env.development

Describe the problem
So basically I wanted to deploy a project using static public environment variables as recommended by the SvelteKit docs but I can't because upon testing I found that Cloudflare is loading production variables in the preview deployment which can lead to some bad stuff like sending development data to a production analytics environment.
It probably happens because Vite loads production env variables when running the build command.
Describe the proposed solution
Since Cloudflare Pages doesn't allow for a separate build command for preview deployments, we should either load .env.development for preview deployments or better yet add an option in the adapter config for Cloudflare Pages where we can specify which env file to use for preview deployments.
Alternatives considered
No response
Importance
nice to have
Additional Information
No response

Hey @dummdidumm, do you build the SvelteKit App locally and then upload it to Cloudflare pages or do you use Cloudflare pages' Git integration?
Because if you use automatic builds, you need to add those development env variables in your Cloudflare pages project as preview environment variables. If you don't do that, Cloudflare will - as it seems - use the production environment variables as fallback.
Never had problems with preview environment variables and Cloudflare


Data feeds not submit at right intervals

one reason: DB is not configured correctly, the data table is not achieved, too many records make it slow to read and write


Increase visibility of the prerequisites in the getting started doc.

As it is, it's a bit easy to miss (parenthetical, etc.)

Ugh.  Wrong repo.


Read from stdin when "-" is passed as input file

Allows piping a template through tpl by simply doing:
echo "template" | tpl -

Thanks :)


[BUG] Tag is assigned to new row and removed from last row

Describe the bug

When you create a new row in a sorted column, it be will auto assigned a tag but removed the tag assigned to the last row
To Reproduce

Add 5 rows
Make one column a tag type
Sort the rows
Add a tag to all rows
Add a new row that should jump up when sorted

Expected behavior

The new item will not have a tag applied to it. The last row will keep the tag already assigned to it.
Using Mobile App?

No

Fixed in 3.0.0


Adding Near Earth Objects App

This app hits the Near Earth Object API NeoWs to display the name of the next nearest object to Earth as well as the relative time, distance, and speed of when it will miss.
Also allows the user to configure kilometers vs miles.

I have read the CLA Document and I hereby sign the CLA

recheck

@noahcolvin Looks great, thanks for the PR!

Hi @noahcolvin. Unfortunately I had to revert this because it was failing tests.
The flavor of Starlark we use on our server does not allow while loops. Is it possible to rewrite find_soonest_starting to use a for loop that ranges over a fixed sequence?


Update global carbon budget

Adapt global carbon budget steps to the new ETL code and metadata definitions.
A few things to note:

The data page for the most important indicator, per capita consumption-based emissions, doesn't seem to react to my changes in the garden yaml file.
I have also refactored the GDP Maddison dataset.
There are a few TODOs in the garden yaml file, that should be done when we can have common definitions.

The data page for the most important indicator, per capita consumption-based emissions, doesn't seem to react to my changes in the garden yaml file.

That might be because there's still YAML file in the grapher step that overrides the garden file.

The data page for the most important indicator, per capita consumption-based emissions, doesn't seem to react to my changes in the garden yaml file.

That might be because there's still YAML file in the grapher step that overrides the garden file.

True, I deleted the grapher file from the previous step 🤦 . Thanks! I'll fix it now!


make client manage it's own time

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
now the client will manage it's own time around getting products
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Further Information
Please also include relevant motivation and context.
List any dependencies that are required for this change.

testing in demo prior to merge to ensure it matches behavior expected


Incorrect username and password

Hi,
I'm totally new to Dart and AWS Cognito.  I downloaded the project, modified the value and run.  I was able to register a new user but when I tried to log in, I got an error "Incorrect username and password".
Thanks,
VV

can you post the code you are using, it's almost impossible to help you with only this information

There are multiple reasons for this error to occur. But if by any chance that you have enabled "remember device" in your User Pool, you will see this failure on the second and subsequent times that you login. You can take a look at the fix I did at: https://github.com/jonsaw/amazon-cognito-identity-dart/pull/62


add new prfile image TobiasPape

Hello Andreas,
I changed my about image. If you don't mind I will merge it to the master.

Pull Request Test Coverage Report for Build 727

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

Totals

Change from base Build 725:
0.0%

Covered Lines:
1532

Relevant Lines:
1851

💛  - Coveralls


Don't try to create certificates with CN>64bytes

These are rejected by certmanager as they are not allowed in the spec

@leochr This is ready for review. It passes local testing, but no e2e tests delivered yet.


Add a new load DDS event

Please describe the problem you're trying to solve
I discussed with @Rolv-Apneseth on Discord about adding a new load event to make implementing bypass.yazi easier.
I just tried some changes in https://github.com/sxyazi/yazi/pull/1374 and found that a larger-scale refactor is needed to make it work. Specifically, the yazi_dds crate can't access the FolderStage in yazi_core because yazi_dds is a dependency of yazi_core, which would cause a circular dependency.
So, I'll track it in this issue and implement it in the next target (0.3.1).
Would you be willing to contribute this feature?

[X] Yes, I'll give it a shot

Describe the solution you'd like
.
Additional context
No response

That's great, thank you. Sounds tricky.

Please try https://github.com/sxyazi/yazi/pull/1980


[Feature Request] buystoplimit and sellstoplimit percent

I might say that this buystop and sellstop limit is very useful to implement.
For example:
buystoplimit: 0.5%
sellstoplimit: 0.5%

gekko will stop buying if the current bid price exceeded the 0.5% from the original price that gekko wanted to buy.
gekko will stop selling if the current ask price is lower of 0.5% from the original price.

This is something you can implement in your own strategies! Read more information on how to create strategies here: https://gekko.wizb.it/docs/strategies/creating_a_strategy.html

@jaguar666 I have created a strategy like this. Try it at (https://github.com/pushkarnagle/gekko-buyatsellat)

I posted on the r/gekko about this, I wasn't able to figure out how to do it, my JavaScript skills are weak
https://redd.it/6z5s2d
If someone could help that'd be great.

@epepper Can you please elaborate in detail what you want to do in your strategy which you have posted on Reddit?

@pushkarnagle First off, thank you for your help with everything. Second I was hoping to finish it up, so I could add it as a custom strat.
Maybe I am making a noob mistake, but when I load it into custom, the my_custom_setting = 10 is still there (yes I know this isn't handled by the custom strat file), but it doesn't work in paper trader.

This is the guide to making a stop loss in your strat where imo it belongs:
http://gekkowarez.com/how-to-put-a-stop-loss-into-your-gekko-strategy/

@pushkarnagle i will try your strategy. thank you

great stuff! Feel free to add this to the docs in a PR!


bump wiremock to 0.6

:wave: I'm not sure if the maintainer is still around. But we use this crate at my company for testing.
Unfortunately, this crate doesn't fully work with wiremock 0.6.
Cargo is happy to have the current version in the same crate with the latest wiremock. However, it breaks down in use. Here's an example failure where the parts matcher no longer satisfies the Match trait in new wiremock:
error[E0277]: the trait bound `wiremock_multipart::matchers::NumberOfParts: wiremock::Match` is not satisfied
   --> crates/clients/src/http.rs:450:18
    |
450 |             .and(NumberOfParts(2))
    |              --- ^^^^^^^^^^^^^^^^ the trait `for<'a> Fn(&'a wiremock::Request)` is not implemented for `wiremock_multipart::matchers::NumberOfParts`, which is required by `wiremock_multipart::matchers::NumberOfParts: wiremock::Match`
    |              |
    |              required by a bound introduced by this call
    |
    = help: the following other types implement trait `wiremock::Match`:
              AnyMatcher
              BasicAuthMatcher
              BearerTokenMatcher
              BodyContainsMatcher
              BodyExactMatcher
              BodyPartialJsonMatcher
              HeaderExactMatcher
              HeaderExistsMatcher
            and 8 others

In this PR, I bumped the version and fixed APIs broken by wiremock-multipart 0.6.
I'd love to get this crate updated over using my fork. Please let me know what I can do to help!

Hi Billy!
Thanks for the pull request! I just merged it and published<EMAIL_ADDRESS>😄


Support for handling py_library dependencies

This is great, thanks for sharing.  One thing that appears to be missing is hooking up any py_library dependencies as part of the generated venv

Hi @svermeulen - I'd like to address this issue but want to make sure I understand your problem first. Would it be possible to put together a small reproducible example?
If not - when is a py_library not included in site-packages causing problems? Are you setting imports on your libraries?

Hi @Paveltarno. Are you already using Bazel for these libraries (just not this package)? If so, are you setting the imports parameter?

Yes I am (as part of a poc) setting it to [.]
On Mon, 5 Dec 2022 at 20:50 Jeremy Volkman @.***> wrote:

Hi @Paveltarno https://github.com/Paveltarno. Are you already using
Bazel for these libraries (just not this package)? If so, are you setting
the imports https://bazel.build/reference/be/python#py_library.imports
parameter?
—
Reply to this email directly, view it on GitHub
https://github.com/cedarai/rules_pyvenv/issues/1#issuecomment-1337949196,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2ICKGPYG5HQDQZRFMDN43WLY2ODANCNFSM5ZFNNNWQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Paveltarno can you try again with #5 merged? With this change, py_library deps will be linked into site-packages if they specify imports.

looks like it works! perfect, thanks a lot @jvolkman

Great. In that case I'm going to close this as resolved. Thanks for confirming!


New package: MicrosoftCorporation.MicrosoftOffice version 16.0.18129.20158

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.9 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

Manifest: The manifest file path must match PackageIdentifier and PackageVersion properties from manifest. actual
'manifests\m\MicrosoftCorporation\MicrosoftOffice\16.0.18129.20158', expected
'manifests\m\Microsoft\Office\16.0.18129.20158'

The file names and paths haven't been updated yet. They have to match.


Hack for conda includes

One needs to add their conda include paths below which is a hack.
https://github.com/lcompilers/lc/blob/9c855f961ac54f70199e21cb4ff0388531485d47/src/lc/clang_ast_to_asr.h#L1855-L1870

We need to fix this in a robust way. Let's see what we need:

We need to recognize the C++ standard library and not parse its Clang AST nodes at all, instead recognize what is included (say std::out) and handle it directly
We need to recognize user include files and treat them in a special way: parse those separately into an ASR module, and then just include such a module
We need to recognize third-party libraries like xtensor, not parse it and treat it directly

How to do that? Here are some ideas:

We can require user include names to not clash with C++ standard library nor with any third-party library that we support directly. So iostream will always mean C++ standard library and never a user include. Then we can simply match for the name of the include at the end of the path and be done with it. This will be conda independent and user installation independent. But it has a downside that user include file must not clash, which might be ok for the main include files, but I suspect even a lot of the standard library (and xtensor) recursive includes might have some more "common" names that might clash.
We can require a compiler flag (similar to -I) to specify the C++ standard library path, and another or the same flag to also specify xtensor location. And/or a special flag to specify user include locations, for example we could require strict -I flags for all user includes, and if the Clang AST header file is specified explcitly using -I, then it is user header file, otherwise it is "built-in". The problem is what to do if we use a conda environment that has both xtensor and user include files with the same prefix.
We can specify conda include dir explicitly, or support something like --include-conda.


Brmix handler causes diverse errors with kerker mixing

Bug found by @becca9835
Summary
When the Brmix error handler attempts kerker mixing (IMIX=1), some structures will freeze or fail to converge electronically.
This was found to occur in supercells of TiZnF6 during the diffusion/all-paths workflow:
# Corrections on start endpoint
error_handler,correction_applied
Brmix,switched ISTART to 1
Brmix,switched IMIX to 1
Frozen,switched ALGO from Fast to Normal
SubspaceMatrix,set PREC to Accurate
SubspaceMatrix,set PREC to Accurate

# Corrections on final endpoint
error_handler,correction_applied
Brmix,switched ISTART to 1
Brmix,switched IMIX to 1
Frozen,switched ALGO from Fast to Normal

And the electronic steps fail with a random error: SubspaceMatrix in one case and FEXCF in another. Here's an example output (note the dE values are extremely large)...
       N       E                     dE             d eps       ncg     rms          rms(c)
....
DAV:  64    -0.125420877426E+09   -0.10870E+09   -0.39817E+06  7132   0.257E+03    0.853E+02
DAV:  65    -0.486651072255E+07    0.12055E+09   -0.23485E+07  8184   0.794E+03    0.637E+02
DAV:  66    -0.572827786901E+09   -0.56796E+09   -0.18630E+05  7012   0.214E+03    0.816E+02
DAV:  67    -0.341940195437E+08    0.53863E+09   -0.33029E+08  8081   0.494E+03    0.178E+03
DAV:  68    -0.427685616200E+08   -0.85745E+07   -0.21172E+07  9760   0.233E+04    0.110E+03
DAV:  69    -0.168538912173E+07    0.41083E+08   -0.14705E+05  7339   0.321E+03    0.773E+02
DAV:  70    -0.150069475204E+07    0.18469E+06   -0.26725E+05  6720   0.248E+03    0.437E+02
DAV:  71    -0.180826820380E+07   -0.30757E+06   -0.35787E+05  6797   0.243E+03    0.131E+03
DAV:  72    -0.979785830352E+09   -0.97798E+09   -0.84861E+09  8368   0.986E+03    0.120E+03
DAV:  73    -0.460435894991E+07    0.97518E+09   -0.18151E+05  7988   0.228E+03    0.928E+02
DAV:  74    -0.759008862840E+06    0.38454E+07   -0.12247E+06  6883   0.402E+03    0.133E+03
DAV:  75    -0.906004244009E+07   -0.83010E+07   -0.10614E+07  7760   0.139E+04    0.285E+03
 ERROR FEXCF: supplied exchange-correlation table
    is too small, maximal index :        4032

VASP's official comment on the FEXCF error is incomplete, and others have seen this error caused by a wide range of setups. All of them seem to have mixing parameters in common.
In TiZnF6, these errors begin when Brmix sets IMIX=1, so I attribute this error the Kerker mixing. In fact, when I remove IMIX=1, the relaxation works properly.
Proposed Fix
There are a couple of options...

add a condition to Brmix that skips kerker mixing for unitcells > 50 atoms (e.g. supercells)
add a condition to Frozen that checks if non-default mixing is present and clears it if so
add a new error handler that checks for FEXCF or extremely dE values

I ended up going with fix number 2 (adding a check to the Frozen error handler).
I haven't tested it yet, but I'll attempt a dev run on warwulf some time this week.


sensor alerts

Watchdog process should check queues and disk utilization, write alerts straight to disk for delivery by filebeat.

Disk utilization done, queue length remains.

Donezo.


Add eval back in

It might be possible to do eval timeout and setinterval by just looking for errors that occur from it. This can be done by adding a window.onerror handler.

Just kidding. This does not work how I thought it did.

Why not? What's the problem with your solution?


Base URL with appended 'directory'

We have a situation where we have our app being basically hosted via nginx to a specific single server configuration.  This server configuration is using 'locations' to shuttle off to various other applications.
What we basically have is this, a sails app hosted at https://somenginx.com:9999/sailsapp which points to (via a proxy_pass) https://localhost:1337
The problem is, all the links/resources/etc that are being requested subsequent to that initial page are not using the /sailsapp part as their base URL.
Does anyone know of a way to get sails to add this to the base URL?  I tried putting in a proxyHost and proxyPort (even using "9999/sailsapp" as the proxyPort out of despeartion), but I haven't found a way to do this yet.
Thanks for any help!

I think this should be solved in front of node; e.g. you should be hosting node behind nginx or apache anyway; those will have more robust URL rewrite features available.


V2 : Fix Deserializers

These changes update the various deserializers to:

deserialize(options, source)
new options.filename
corrected options.output to accept only 'script' or 'geometry'

And of course, updating CLI and CORE code to use these new standards.
All Submissions:

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[X] Does your submission pass tests?

@kaosat-dev please review.

@kaosat-dev please merge


[BEAM-13496] Upgrade Flink runner to include log4j patches.

Please add a meaningful description for your change here

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

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

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

GitHub Actions Tests Status (on master branch)

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

FYI @tvalentyn this is another log4j-related change, we should merge this into the release if possible.

@ibzib - Could you send a CP to the release branch?

#16300


Causes React sites to freeze

After installing the extension, going to sites like facebook.com or reactjs.org would freeze the tab it's on. The sites work like normal immediately after disabling the extension.

I am sad when you say 'smaller-scale React applications.''


Feature: sealos run xx.tar.gz

Which command or component
sealos run
Detailed description of the feature
Install from tar.gz offline image package，Make offline installation easier.

Agreed, this feature is really helpful for the offline installation as sealos need to pull, save, load image and run, why not just run the package directory? just put a little more efforts and help the vast majority of users.
Simplicity is beauty!

yes， pull save then load run , It's too complicated.

@willzhang can you provide this feature? Check the suffix is "tar.gz" then call the load function first.

@willzhang can you provide this feature? Check the suffix is "tar.gz" then call the load function first.

no，I'm not good at golang


Feat:  Adding more styles to subscribe to newsletter section

Describe the feature
Adding more styles to subscribe to newsletter section
It can be styled more.. the text is not aligned.. buttons can be added with hovering effect
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[ ] I'm a GSSOC'24 contributor
[X] I'm a VSoC'24 contributor
[X] I want to work on this issue

@SuhainaFathimaM but we are creating another page for it. After the completion of this page, I will let you know to add this in the future.

Please search for another issue and raise it, which I'm happy to assign to you. :)


process.env.FOLKTALE_DOCS is not replaced by Webpack 5

By default Webpack 5 only replace process.env.NODE_ENV when bundling. But Folktale uses process.env.FOLKTALE_DOCS and process.env.FOLKTALE_ASSERTIONS in three distribution files. When executed, those bundled files throws an error because process is undefined.
Steps to reproduce
It can be reproduced by bundling with Webpack 5 a file that contains eg. Task.of().
Expected behaviour
Run the bundle without throwing an error.
Observed behaviour
The bundled file throws an error because process is undefined.
Environment

OS: Debian Buster
JavaScript VM: V8 (NodeJS 15)
Folktale version: 2.3.0

Additional information
It can be fixed by adding plugins: [new webpack.EnvironmentPlugin({ FOLKTALE_DOCS: false })] in the Webpack configuration file. This could be documented in the Folktale documentation.
Or FOLKTALE_DOCS and FOLKTALE_ASSERTIONS can be moved/nested as object properties in process.env.NODE_ENV, but I'm aware that browsers are not necessary the main platform target of this library, therefore this change might not be worth it. However, and to answer this comment (what most users of the library are interested in seeing), this change could lower the barrier of entry for adopting Folktale, which I should say is IMHO the best FP ADT library I found and use since a few years now.

Ah, I'm not very familiar with JS tooling at this point. Is that a new thing in WebPack?
Looks like there aren't many instances of it in the source, so it should be doable to just test for process first. I was worried it was being used for dead code elimination, but that isn't the case. I'll try to push a new version this week or the next.

Ah, I'm not very familiar with JS tooling at this point. Is that a new thing in WebPack?
Looks like there aren't many instances of it in the source, so it should be doable to just test for process first. I was worried it was being used for dead code elimination, but that isn't the case. I'll try to push a new version this week or the next.

Yes, Webpack 5 now only set process.env.NODE_ENV from configuration.nodeEnv = configuration.mode (default is 'production'). I also think testing for process will do the trick as well. Thank you! 👍

process is not defined.
[...]
Want to use environment variables with process.env.VARIABLE? You need to use the DefinePlugin or EnvironmentPlugin to define these variables in the configuration.
Consider using VARIABLE instead and make sure to check typeof VARIABLE !== 'undefined' too. process.env is Node.js specific and should be avoided in frontend code.

https://webpack.js.org/migrate/5/

Yes, Webpack 5 now only set process.env.NODE_ENV from configuration.nodeEnv = configuration.mode (default is 'production'). I also think testing for process will do the trick as well. Thank you! 👍

process is not defined.
[...]
Want to use environment variables with process.env.VARIABLE? You need to use the DefinePlugin or EnvironmentPlugin to define these variables in the configuration.
Consider using VARIABLE instead and make sure to check typeof VARIABLE !== 'undefined' too. process.env is Node.js specific and should be avoided in frontend code.

https://webpack.js.org/migrate/5/

I just ran across this one too. Because folktale was being used by a dependency and not the current project it was not all that easy to track down the issue.
Thanks for cdoublev for posting the plugins: [new webpack.EnvironmentPlugin({ FOLKTALE_DOCS: false })] fix. It worked for me.
But, yeah. I would be in favor of some kind of update which meant folktale didn't die instantly whenever you try to run it on the web.

Spoke too soon. To get it all working I also had to add FOLKTALE_ASSERTIONS to the environment plugin:
plugins: [new webpack.EnvironmentPlugin({
   FOLKTALE_DOCS: false,
   FOLKTALE_ASSERTIONS: false
})]

This fell through my todo list. The proper fix is simple, but releasing it is going to take a while as the build system has degraded quite a bit over the years.


Alternative tool for container testing

Hey,
nice project. You might consider using https://github.com/GoogleContainerTools/container-structure-test as most tests are covered there already.

hi
thanks
yeah svrunit kinda exists since a very long time right now (maybe before the other), just had to release it because we are using it in another open source project :D
now im having fun improving it way more

omg but honestly...that looks a lot like this :D haha , i wasnt aware of that


chore: merge develop into master for v0.4.1 release

Pull Request doc
Proposed release notes
This is the final PreREISE release which will support Python 3.7.
Closed Issues

Table Change Function for Users (#160)
Wind/Solar/Hydro Profiles (#161)
Reorganize documentation (#172)
HRRR data (#176)
Linting error N818 (#182)
Data Intake: add HIFLD open and related external data (#185)
Create bus data frame from HIFLD line and substation data (#205)
Augment known HIFLD transmission lines with transformers within substations (#206)
Data Intake Collections for Building Electrification Profile Generation (#207)
Parse EPA and EIA data into one table of generator data to be used in the HIFLD Grid (#222)
Add single function that kicks off all HIFLD Grid building (#226)
Build distribution of demand to HIFLD buses (#229)
Demand Flexibility and Demand Flexibility Cost Data (#230)
Improve handling of DC lines when loading HIFLD data (#233)
Any missing HRRR data causes calculation of power output to fail (#244)

Merged pull requests (features)

feat: add cli to download rap data (@goccert25)
refactor: separate WindData and DataSource classes (@goccert25)
feat: add solar data cli downloader (#178) (@goccert25)
feat: add ability to select grid model to cli (#184) (@goccert25)
feat: map buses to balancing authorities (#181) (@BainanXia)
feat: add stubs for demand and hydro data cli (#190) (@goccert25)
Load HIFLD data (#196) (@rouille)
feat: process plant data to create data frame (#197) (@danielolsen)
feat: add functions to perform transmission line filtering (#199) (@danielolsen)
feat: identify closest substations by ID, not just name (#202) (@danielolsen)
feat: add filter of substations based on network of lines (#203) (@danielolsen)
feat: add function to infer line voltages (#208) (@danielolsen)
feat: add function to create buses from substations and lines (#210) (@danielolsen)
feat: add ability to download hrrr data (#212) (@goccert25)
feat: add functions to load EIA and EPA data from blob storage (#214) (@danielolsen)
feat: add functions to connect islands with minimum cost in topology module (#216) (@BainanXia)
feat: add transmission to substation track selection (#217) (@rouille)
feat: add function to create transformers within substations (#218) (@danielolsen)
feat: add functions to estimate branch parameters (impedance and rating) (#219) (@danielolsen)
feat: calculate pout based on hrrr data (#221) (@goccert25)
feat: add heat rate parameter estimation (#225) (@danielolsen)
feat: add options to use KDTree in connecting islands by MST (#228) (@BainanXia)
feat: add function to assign demand to buses proportional to population (#235) (@danielolsen)
feat: add top-level HIFLD grid orchestration function (#236) (@danielolsen)
feat: filter DC lines out of AC transmission network processing within HIFLD construction (#237) (@danielolsen)
feat: separate interconnections via network topology (#240) (@danielolsen)
refactor/feat: decouple solar profile generation from Grid object, add individual calculation (#247) (@danielolsen)

Merged pull requests (fixes etc.)

ci: add pep8-naming to flake8 and fix warnings (#157) (@jon-hagg)
Update dependencies (#158) (@jon-hagg)
chore: remove all declarations (#159) (@jon-hagg)
ci: add coverage report to pytest (#161) (@jon-hagg)
chore: create bug report issue template (#162) (@rouille)
chore: create feature request issue template (#165) (@rouille)
Update dependencies (#166) (@jon-hagg)
docs: update setup documentation (#167) (@goccert25)
Use integration marker for test fetching data (#169) (@rouille)
Update dependencies (#170) (@jon-hagg)
chore: update packages manually (#177) (@jon-hagg)
Report code coverage (#179) (@jon-hagg)
chore: fix N818 warning from pep8-naming (#183) (@jon-hagg)
Profiles generation documentation (#187) (@rouille)
chore: update packages with dependency on urllib3 (#188) (@jon-hagg)
fix: add imputation of missing wind data for cli (#189) (@goccert25)
Folder structure an ATTRIBUTION file (#191)
Load zone file (#192) (@rouille)
chore: add const file (#194) (@rouille)
docs: rewrite README (#195) (@rouille)
data: manually fix BA county map to remove duplicate assignments (#198) (@BainanXia)
refactor: use groupby to speed up distance calculations (#204) (@danielolsen)
Update dependencies (#209) (@jon-hagg)
ci: replace docs trigger with generic one (#211) (@jon-hagg)
Package related cleanup (#215) (@jon-hagg)
refactor: switch (lon, lat) points to (lat, lon) (#223) (@danielolsen)
refactor: change transmission processing code to expect (lat, lon) instead of (lon, lat) (#224) (@danielolsen)
docs: improve section on documentation in README (#231) (@rouille)
docs: change author (#232) (@rouille)
fix: various issues with HIFLD transmission loading/processing (#239) (@danielolsen)
fix: handle empty HRRR data files via linear imputation (#245) (@danielolsen)
chore: disable tests for failing geo lookup API (#250) (@danielolsen)
chore: narrow dependencies, bump version number to prepare for v0.4.1 release (#251) (@danielolsen)

New contributors

@goccert25

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b7d93ff). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #252   +/-   ##
=========================================
  Coverage          ?   71.29%
=========================================
  Files             ?       75
  Lines             ?     2665
  Branches          ?      344
=========================================
  Hits              ?     1900
  Misses            ?      692
  Partials          ?       73

Continue to review full report at Codecov.

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


fix(python): Add python azure blob read support

I know there's a larger effort to have the python client based on the core rust implementation, but in the meantime there have been several issues (#1072 and #485) with some of the azure blob storage calls due to pyarrow not natively supporting an azure backend. To this end, I've added an optional import of the fsspec implementation of azure blob storage adlfs and passed it to pyarrow.fs. I've modified the existing test and manually verified it with some real credentials to make sure it behaves as expected.
It should be now as simple as:
import lancedb

db = lancedb.connect("az://blob_name/path")
table = db.open_table("test")
table.search(...)

Thank you for this cool project and we're excited to start using this for real shortly! 🎉  And thanks to @dwhitena for bringing it to my attention with his prediction guard posts.

Remember to install the adlfs>=2024.2.0 when use the azure blob

Tips: Remember to install the adlfs>=2024.2.0 when use the azure blob

Thank you for this! I was giving up until I saw this post.

Testing this today. It seems like I can write a vector index to az with .create_index(), but when I try a full text index it writes to a local file. Similarly, when I move the fts index to azure and try to use it, the table can't find it.
Posting here to see if that's out of scope for this PR? I can add an issue if needed, just not sure if it'll be addressed in the async api, or if it was unintentional.

Testing this today. It seems like I can write a vector index to az with .create_index(), but when I try a full text index it writes to a local file. Similarly, when I move the fts index to azure and try to use it, the table can't find it.
Posting here to see if that's out of scope for this PR? I can add an issue if needed, just not sure if it'll be addressed in the async api, or if it was unintentional.

FTS Index's issue ,you can check https://github.com/quickwit-oss/tantivy-py/issues/194

Tips: Remember to install the adlfs>=2024.2.0 when use the azure blob

@QianZhu @wjones127 Can you please include this information in the docs: https://lancedb.github.io/lancedb/guides/storage/#azure-blob-storage
It took me 2 hours to find this comment 😢

Tips: Remember to install the adlfs>=2024.2.0 when use the azure blob

@QianZhu @wjones127 Can you please include this information in the docs: https://lancedb.github.io/lancedb/guides/storage/#azure-blob-storage
It took me 2 hours to find this comment 😢

Hi @fcakyon Thank you for pointing it out!adlfs>=2024.2.0 is needed for sync connection here. We are working on consolidation of Python sync and async APIs. Will update the docs after this work is completed.


Would circle-map works for Nanopore reads?

Hi,
I read your interesting paper and wanted to try this pipeline.  I have some circular DNA reads produced by the Circle-seq method and sequenced by nanopore.  I am wondering if this pipeline would work for Nanopore sequencing data with relatively low coverage?
Thanks

Dear @weijiaweijia,
I have never tried to run Circle-Map on nanopore data. And the algorithm is designed to work for short reads. So, I do not know if it  will work. I am sorry I cannot help here.
Best,
Iñigo


[FEAT] Backoff throttle strategy

This pull request adds the ability to keep track of the number of retries a user has made in the last N seconds, sending direct messages to those who abuse the service.

🚢


Unclear documentation about PolyBase support

In this documentation, there are several mentions about Polybase not being supported by Azure AD authentication. In most cases, it specifically specifies MSI-based Azure AD Application token authentication as not being supposted. So my question is: does "Azure AD Application token authentication with a service principal" support PolyBase?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b8f48c7b-2f52-6fe0-9ea6-358380e0c815
Version Independent ID: 7f448f1e-8d3d-fb5c-6f68-837e46e7b176
Content: Copy data to and from Azure SQL Data Warehouse by using Azure Data Factory
Content Source: articles/data-factory/connector-azure-sql-data-warehouse.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@BE-Digital-Solutions Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@BE-Digital-Solutions service principal auth is supported. As the doc called out, only MSI is not supported.
#please-close


chore: Adding adminSettingsVisible variable in User type

Description

Adding adminSettingsVisible variable in User type for supporting GAC

TL;DR - This change is GAC related. Does not impact users.

Fixes # (issue)

if no issue exists, please create an issue and ask the maintainers about this first

Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Tested it on GAC feature branch. Works as expected.

Manual

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=1acdc70


CI E2E in SimplySecure

Which issue this PR addresses:

Implements Vnet peering solution for SimplySecure V2. This builds on the solution by adding a check for RP_MODE=development. There are two flags at play which work as follows:

CI=False, RP_MODE=development => Used for Local Cluster Creations using hack scripts
CI=True, RP_MODE=development =>  Used for E2E tests run against each PR
CI=True, RP_MODE unset / int / production => Used for E2E on Int / Prod environments
CI=False, RP_MODE unset / int / prodution => Used for creating actual clusters

What this PR does / why we need it:

This PR enables VPN support on our CI-E2E Pipelines. The pipeline connects to a vpn before creating private clusters and running end to end tests. This will facilitate running pipelines when SimplySecure V2 is enabled on our subscriptions
Test plan for issue:

Going to wait for Public Int pipeline to run successfully, we should see the following log messages for certain tests which don't run in development mode
skipping tests in non-development environment

public int RPmode=int
Public Prod RPmode=""
FF Int RPmode=int
FF Prod RPmode=""

Is there any documentation that needs to be updated for this PR?

Its the same changes as the previous PR that got reverted. The issue with that PR was it did not check for RP_MODE=development. This PR adds that condition, waiting for the first Public Int Deploy to run successfully to verify that it indeed skips when RP_MODE=development

Can verify that EV2 in int is skipping tests which are specific to development environments
2022-09-29 13:22:28.737552: skipping tests in non-development environment


Removing internal dependencies

Removing internal dependencies from the Kie Server Java Client docs maven dependencies example

merged into master and 6.4.x, thanks @jesuino


Collapse node

A user should be able to collapse nodes after they have expanded them. This make it so that the user does not need to restart the program if they accidentally expand the wrong link.

Great idea, will add to backlog thank you.

Moved to backlog of web-based app


drivers: gpio: Xilinx Processor System MIO / EMIO GPIO controller driver

Driver implementation plus device tree and SoC initialization code (MMU setup) integration for the Xilinx Processor System MIO / EMIO GPIO controller as contained in both the Zynq-7000 and the ZynqMP (UltraScale+) SoC families.
No modification of the ZynqMP initialization code (MPU regions setup) is required, as the controller's register space is already covered by an existing region definition.

A bit of a strange GPIO driver

I guess GPIO controllers which first provide you with a large number of I/O pins, but then require you to basically hardwire them & have the configuration tied in part to the FPGA bitstream are uncommon. Also, maxing out the MIO (external) GPIO pins will most likely result in you having very little unused I/O pin resources left in particular in the smaller footprints of the Zynq-7000 series. At least for this controller, interrupt handling is straightforward, while Xilinx's other supported GPIO driver, the IP-core-based AXI GPIO controller, does have an interrupt line and an interrupt pending bit, but no per-pin interrupt status bits. Therefore, if you want interrupt support for that controller, every value change upon data register read and write operations must be stored so that it can be determined within the ISR which pin actually triggered the interrupt. So all in all, the design isn't that bad, just the large number of pins requires this bank-wise access workaround due to bit mask size limitations.
Thanks for the review, Marti!

I'm suggesting a DNM until @mnkp can review as GPIO maintainer.

Hi Piotr, thanks for the review.

Could you check if the driver is passing tests/drivers/gpio/gpio_api_1pin/ test. And possibly also tests/drivers/gpio/gpio_basic_api/.

With the changes as committed today, both of those test cases pass:

gpio_basic_api passes upon addition of an overlay for the board I'm working with (and which I'm going to contribute once this driver is mainlined, I didn't yet want to contribute a board that can't do the blinky sample, it's the Digilent/Avnet Zedboard). There are two GPIO-capable pins available on one of the board's expansion connectors that can be bridged.

gpio_api_1pin passes, but there's a bit of a board-specific issue here. This test case uses the same pin alias as the blinky sample. Did the board vendor provide an LED tied to a GPIO controlled by this driver? Yes, they did. Does the blink sample work with it? Yes, it does. So does this test case which uses the same DT alias to grab a GPIO pin for testing work? No, it doesn't.

Here's why: the designers of the Zedboard made a bit of an unfortunate design decision. The one LED connected to this GPIO controller, and therefore the obvious choice for the blinky-compatible alias, is connected to pin MIO7, which equals bank 0, pin 7. They could have gone for a few other pins which by default are available for GPIO, such as MIO12 and MIO13, which I used in the overlay for the gpio_basic_api test, or MIO0, which I eventually used for this test. Those would have worked for the gpio_api_1pin test just fine. So why won't MIO7 which the test case accesses via the led0 alias work? The answer is in the Zynq-7000's Technical Reference Manual, section 14.2.3: Out of all the pins managed by this controller, MIO7 and MIO8 are special, they are output-only pins which are used by the SoC to transport voltage control information during the power-on sequence. For exactly those two pins, not even software-generated interrupts work. There seems to be no feedback from the output data to the interrupt detection logic.
Long story short, due to this issue, I changed the led0 alias over from MIO7 to MIO0, and everything worked just fine. Unfortunately, there's no LED on that pin, and I guess having a working mapping for blinky is more important. So anyone wanting to run this test case on a Zedboard will likely have to manually move led0 over to another MIO pin in order to successfully run this test. The pins used for the gpio_basic_api test are always available.

@mbolivar-nordic Now that this has been merged, should the DNM label be removed for completeness' sake?


added "color-all" for shear action (#966)

@montlikadani your first step wasn't bad, I continued by adding the appropiate behaviour for colors in CMIMaterial#getGeneralMaterialName.
I couldn't test it because of dependency problems in your pom.xml, but I'm quite confident that it should work more or less because it works analogous to shullker_box-all. stripped_log-all, tipped_arrow-all, etc.
Please feel free to test this and to change stuff in code.
You're right, 16 (with income and experience its 48) lines doesn't matter in the jobConfig, but with /jobs info  it takes a whole page just with these colors with same income.

Thanks very much! 👍
Have you tested if the reward of crafting stained_glass-all and block breaking log-all still works?
I suspect
https://github.com/Zrips/Jobs/pull/970/commits/f681deb313a44743b4f4e5e774a7225b9c557dbc#diff-3e5a53476c0732062a0f06d5afb42180176ee665c312f22054851e3f0d815ff5R392-R397
causing the subType to stay empty instead of getting set to ":all".
Why did you add this? The subType has already been set correctly there.
So it should'nt be necessary to be overridden again here:
https://github.com/Zrips/Jobs/pull/970/commits/f681deb313a44743b4f4e5e774a7225b9c557dbc#diff-3e5a53476c0732062a0f06d5afb42180176ee665c312f22054851e3f0d815ff5R620

Have you tested if the reward of crafting stained_glass-all and block breaking log-all still works?
I suspect
f681deb#diff-3e5a53476c0732062a0f06d5afb42180176ee665c312f22054851e3f0d815ff5R392-R397
causing the subType to stay empty instead of getting set to ":all".
Why did you add this? The subType has already been set correctly there.
So it should'nt be necessary to be overridden again here:
f681deb#diff-3e5a53476c0732062a0f06d5afb42180176ee665c312f22054851e3f0d815ff5R620

Literally if we removes these two checks, then it causes to not work and throws an "invalid Action type property: wood-all", because under these checks the myKey is getting split to only return the name, ignoring the -all identifier. So it should works.

https://github.com/Zrips/Jobs/commit/f1194bfd32f1de8dda024008e2dae7a1c008c9e4


Rename to ratatui-template

Can we rename this to ratatui-template? It'll be consistent with ratatui-async-template.

Done in 29521ff9b56be139cb90081622e87d7e4e58340a


live concatination of two observable lists

I have tried to implement a concatenation of two observable lists.
What do you think about the method LiveConcatenation.multi(...)? Is it OK? Or should it be dropped out with classes EmptyLiveList and LiveListWrapper?
Is LiveConcatenation a proper class name?
How can we extend API of LiveList class?

Factory method LiveList.concat(list1, list2).
Methods append(list) and prepend(list).

Could you add anything else?

Hi, you did a very good job, given the lack of documentation of LiveList internals. Unfortunately, concatenation cannot be correctly implemented as a view of the two underlying lists with the current event propagation ReactFX. Automatic prevention of glitches would be necessary to implement it correctly. (And I'm seriously considering that for a future version of ReactFX.) For now, concatenation would have to maintain a copy of the two lists.
Here is a scenario where the implementation as view would fail:
LiveList<String> l1 = new LiveArrayList<>("a", "b");
LiveList<String> l2 = new LiveArrayList<>("c", "d");
l1.observeQuasiChanges(ch -> l2.add("x"));
LiveList<String> con = concat(l1, l2);
l1.add("y");

Note that order of listeners is not defined, but assume the observer added to l1 is notified before the concatenation is notified of a change in l1. l1.add("y") will trigger l2.add("x"), and observers of con will be notified of "x" added at position 5, while the last observed size of con was 4, so the highest valid position for addition would be 4. Only after that are they notified of addition of "y" at position 2.

The failing case above would be rather uncommon in real applications, but we should think about all the corner cases, so that the user does not have to.


Create an 'add multiple ingredients' function for /add-recipes

Add new line to ingredients section.

Do you want to add a redirect back to the profile page after a user successfully adds a recipe?

Closed #93


Include FirebaseAuth 5.0.1 in Firebase 5.2.0

cherry-pick FirebaseAuth extension fix to release-5.2.0 branch
Update release to include FirebaseAuth 5.0.1

cc: @bojeil-google


bump version to v1.0.0

Signed-off-by: Lonng<EMAIL_ADDRESS>bump version to v1.0.0

Codecov Report

Merging #295 into master will decrease coverage by 0.28%.
The diff coverage is 35.35%.

@@            Coverage Diff             @@
##           master     #295      +/-   ##
==========================================
- Coverage   23.50%   23.21%   -0.29%
==========================================
  Files          36       36
  Lines        2936     2955      +19
==========================================
- Hits          690      686       -4
- Misses       2152     2175      +23
  Partials       94       94

Impacted Files
Coverage Δ

cmd/help.go
38.88% <ø> (ø)

cmd/list.go
15.57% <0.00%> (ø)

cmd/root.go
48.19% <0.00%> (ø)

cmd/run.go
0.00% <0.00%> (ø)

cmd/telemetry.go
29.68% <ø> (ø)

cmd/uninstall.go
35.59% <0.00%> (-0.62%)
:arrow_down:

pkg/repository/clone_mirror.go
0.00% <0.00%> (ø)

pkg/repository/v1manifest/local_manifests.go
0.00% <0.00%> (ø)

pkg/repository/v1manifest/manifest.go
0.00% <ø> (ø)

pkg/repository/mirror.go
5.64% <27.27%> (+1.40%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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


is_extension_available - extension not found in case of space in string pattern

Fixes #741

Ok will push only one commit fixing the issue.

LGTM - needs formatting fix though.

Thanks. Format fixed

All the Travis jobs passed but Travis never reported back to Github. Merging.


Make data mapping optional

What it says in the title. As a bonus model.clear starts working again for strict models.
Note: this is a breaking change.

@jsahlen How about this? And then only use this when we know that we actually need conversion?


Update the style of build_docker.py

This PR implements a few style updates to build_docker.py and replaces termcolor with built-in features. Specifically:

[x] Consistent use of line breaks for each argument;
[x] Consistent use of indentation before arguments;
[x] Consistent use of double and single quotations for strings;
[x] Consistent use of line break before closing parenthesis;
[x] Use the backtick for quoting a substring;
[x] Use the number of spaces for indentation instead of giving a string containing the number of spaces intended;
[x] termcolor is currently the only non-standard dependency of this script. This PR implements a method that provides the same functionality with built-in features. This would simplify running this script in another environment without installing additional packages.

Thanks @mwalker174!


updated docs, fixed redundant/unused import warnings

With compiler v <IP_ADDRESS> there were a few warnings that I've fixed.

Thanks :+1:


feat(register-of-applications): populate applications table with filt…

…ered data
-exclude pre application stage from table data;
-update query string builder to accommodate API changes

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

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


Separate component logs for readability

Description of Problem the Feature Should Solve
At the moment, we have all logs from MCAD, InstaScale, and the Operator displayed in one single log. It is not immediately obvious and it can get difficult sometimes to identify which logs belong to which component.
Describe the Solution You Would Like to See
Here are a few ideas:

Something in the lines of [component] logs.
Prefixing the component's name to the logs and then simply grep them. (Might be hard to keep consistent)
TBD

Relates to #113. One dimension to add to the structured logs should be the component name.

Relates to #113. A dimension to add to the structured logs should be the component name.

I like that idea a lot, exactly! That would solve this. Then maybe we could get the logs using grep or some kind of log viewer for filtering.


evaluating core stories with two stage fallback causes an error

Rasa version: master
Python version: 3.6
Operating system (windows, osx, ...): mac
Issue:
evaluating core stories with two stage fallback causes an error:
Traceback (most recent call last):
  File "/usr/local/Cellar/python/3.6.5_1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/local/Cellar/python/3.6.5_1/Frameworks/Python.framework/Versions/3.6/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/Users/ghost/Documents/rasa/rasa_core/rasa_core/evaluate.py", line 686, in <module>
    cmdline_arguments.e2e)
  File "/Users/ghost/Documents/rasa/rasa_core/rasa_core/evaluate.py", line 511, in run_story_evaluation
    use_e2e)
  File "/.../core/test.py", line 470, in collect_story_predictions
    in_training_data_fraction = _in_training_data_fraction(action_list)
  File "/...core/test.py", line 425, in _in_training_data_fraction
    a["action"] for a in action_list
  File "/.../core/test.py", line 426, in <listcomp>
    if not SimplePolicyEnsemble.is_not_memo_policy(a["policy"])
  File "/.../core/policies/ensemble.py", line 306, in is_not_memo_policy
    is_memo = best_policy_name.endswith(
AttributeError: 'NoneType' object has no attribute 'endswith'

Getting this issue how can i resolve it . i am using
rasa==0.1.1
rasa-addons==0.5.9
rasa-core==0.14.4
rasa-core-sdk==0.14.0
rasa-nlu==0.15.0

this should be fixed in rasa 1.0


PR: A couple of fixes for the Internal console

Description of Changes

Restore parent for InternalShell. This sets the right parent and style for the completion widget in the console (regression introduced in #17657).
Fix saving command history, which was not working due to the incorrect initialization of some mixins (regression introduced in #23024).

Issue(s) Resolved
Fixes #23196.
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:

@meeseeksdev please backport to 6.x


Update include_retried_jobs description

As pointed out in https://github.com/buildkite/docs/issues/645, our description for the builds API param include_retried_jobs isn't super clear.
The PR updates the description to @dws-uber's words suggestion 🙌🏻 Thanks @dws-uber! 🙇🏻♀
Closes #645

@toolmantim how much do you care about proper apostrophes? I'm stomping one here, but can put it back if you have feels!


Adding simvue Handler to logging module does not show logs in Events UI

After adding the simvue Handler to the Python logging module as per the documentation, and then adding debug (also confirmed to happen with info) level log messages to the code, the log messages do not appear in the Events page of the UI. Only events manually added with the log_event() method are seen.
Once fixed, additionally need to add a unit test to check the functionality of the simvue Handler with the logging module.
Code I used to provoke the issue:
import random
import time
import numpy
import os
import pathlib
import json
import logging
from simvue import Run, Handler

if __name__ == "__main__":

    with Run() as run:
        # Configure the run
        run.config(suppress_errors=True,
            resources_metrics_interval=10)

        # Create a variable to store the number of runs
        num_iterations = 300

        # Initialise the run
        run.init(name='random-numbers-%d' % time.time(),
                description='Monitoring of the generation of random integers between 0 and 10.',
                tags=['random-numbers', 'v1'],
                folder='/rand_nums',
                metadata={
                    'number_of_iterations': num_iterations,
                    'result_converged': False
                })

        # Create a logger, add the Simvue Handler so that log messages are shown in the UI
        logger = logging.getLogger(__name__)
        logger.addHandler(Handler(run))

        # Save the code as an artifact
        run.save(os.path.abspath(__file__), 'code')

        # Set details about the folder which we have created to store our runs:
        run.set_folder_details('/rand_nums',
                       metadata={'environment': 'testing'},
                        tags=['random-numbers',],
                       description='Stores all runs which monitor the function to create random integers between 0 and 10.')

        # Add an alert to monitor the value of the mean
        run.add_alert(
            name='mean_outside_acceptable_range',
            source='metrics',
            frequency=1,
            rule='is outside range',
            range_low=4,
            range_high=6,
            metric='averages.mean',
            window=2
        )

        # And another alert to check the log for division by zero errors
        run.add_alert(
            name='zero_division_error',
            source='events',
            frequency=1,
            pattern='Division by Zero Error',
            )

        # Initialise an empty array which expects integers to store the random numbers
        all_numbers = numpy.array([], dtype=numpy.int64)

        # Initialise an empty array which expects floats to store the percentage changes in the mean
        percentage_changes_in_mean = numpy.array([], dtype=numpy.float64)

        run.log_event("Random Number Generation Started!")

        mean = 0
        # Generate 10 random numbers, one per second
        for count in range(0, num_iterations):
            random_number = random.randint(0, 10)
            all_numbers = numpy.append(all_numbers, random_number)

            # Record the previous iteration's value of the mean
            previous_mean = mean

            mean = float(numpy.average(all_numbers))
            median = int(numpy.median(all_numbers))
            mode = int(numpy.bincount(all_numbers).argmax())

            # To avoid division by zero in the case where mean = 0, manually set percentage change to zero
            if mean == 0:
                percentage_change = 0
            else:
                # Calculate the percentage change in the mean from this iteration
                percentage_change = ((mean - previous_mean) / mean) * 100

            percentage_changes_in_mean = numpy.append(percentage_changes_in_mean, percentage_change)

            # Add a debug log message containing this percentage change
            logger.info(f"Mean has changed by {percentage_change} in iteration {count}.")

            # Log the metrics, so that they can be seen in the Simvue UI in real time
            run.log_metrics({'random_number': random_number}, step=count)

            run.log_metrics({
                'averages.mean': mean,
                'averages.median': median,
                'averages.mode': mode
            }, step=count)

            # Catch any Exception throws from this calculation:
            try:
                # Calculate and log our new metric
                new_stat = mean / abs(median - mode)
                run.log_metrics({'new_stat': new_stat}, step=count)
            # Log event if divide by zero encountered during calculation
            except ZeroDivisionError as err:
                run.log_event(str(err))

            time.sleep(1)

        run.log_event("Random Number Generation Completed!")

        # Save the final values of the averages to a JSON file and store as an artifact
        averages_out = {
            'mean': mean,
            'median': median,
            'mode': mode
        }
        with open(os.path.join(pathlib.Path(__file__).parent, "averages_out.json"), "w") as out_file:
            json.dump(averages_out, out_file)

        run.save(os.path.join(pathlib.Path(__file__).parent, "averages_out.json"), 'output')

        # Store the array of random numbers and percentage changes as artifacts
        run.save(all_numbers, 'output', name='all_random_numbers')
        run.save(percentage_changes_in_mean, 'output', name='percentage_changes_in_mean')

        # Update metadata and tags once the run is completed
        run.update_metadata({'mean': mean})

        if 4.9 < mean < 5.1:
            run.update_metadata({'result_converged': True})

        run.update_tags(['completed'])

Found the issue, need to set the level of the Logger correctly before attempting to add logs. I assumed that the Handler would automatically set this to the highest level, but actually it makes more sense for the user to set this for their logger. I will add  a note to the docs explaining this in the Tracking & Monitoring section, and in the Tutorial.


Update Calico and Canal tabs in kubeadm docs

Fixes broken links and updates manifest references to use the newest Calico version (v3.1).

/assign @zacharysarah

@praseodym Thanks for the update! Just a minor edit.

@Rajakavitha1 Thanks! Updated :+1:

/lgtm

/approve


Bootstrap 4.5.2 - input type=image with class form-control has padding applied.

Only noted while building out a demo of some permutations of input tags for a legacy website, found that the form-control class  from _forms.scss adds the padding for .form-control as  padding: .375rem .75rem;
Recommend excluding for just the input[type=image] with:
input[type=image].form-control {
  padding:0;
}

Example:
<input type="image" src="https://www.giantgeek.com/images/button-login.gif" class="form-control" />

Example - the red button is for comparison as an

I don't see this element get used that often, but I feel like that's what I'd expect if you're using Bootstrap's form components. This feels pretty consistent with the rest of our form controls, and I wouldn't expect something edge-to-edge or custom beyond that.
Thoughts @twbs/css-review?

this goes back to the discussions about how opinionated the reset should be, and whether or not some of its styles should be moved to the explicit .btn class.

My two cents: in that case, simply use .p-0 or do not use .form-control at all: input[type="image"] just works like img, there's probably no need for our form styles, is it?

I don't see this element get used that often, but I feel like that's what I'd expect if you're using Bootstrap's form components. This feels pretty consistent with the rest of our form controls, and I wouldn't expect something edge-to-edge or custom beyond that.

Agreed
If you don't want <input type="image" /> to look like .form-control, than just leave out the .form-control class?

as sorry, missed that the original had .form-control. in that case yes, agree...if you don't want the standard styling for .form-control, don't use .form-control - no need to special-case it (again, because some authors may well want the image plus the standardised/normalised padding)

Gonna close it now, guess we gave enough feedback here 🙂


Add ability to auto update Insiders build of extension

Others have done this https://github.com/Microsoft/vscode/issues/15756#issuecomment-425287642
Updating label to code health + enhancement.
I.e. even if not exposed to end users, it would be good for in-house use. Much like out of band LS installs.

We already have the python file to do this...

Note: This is not for extension authors. That python file builds the extension.
This is for users of the developer build of the extension, i.e. dog fooding.
VSC doesn't provide a pre-release channel of extensions, and that's why we host our extension on a blob store, and users need to install it manually.
The benefit, is:

We'll have a regular set of users who are constantly testing/using the dev version of the extension.
We have the potential to get feedback before the release.

Either way, this would be great for in house developers.
UX (similar to out of band installs of LS):

Download and install extension every daily, weekly
Manual download and install of the extension (via some command)

Will need to consider impact of downloading LS every time we update the extension (e.g. if we update extension every day, then LS will be downloaded every day).

Have a look at how C++ extension does the auto updating.

Prescribed Solution

Download vsix
Identify path to VSCode executable

Run VSC executable with the args --install-extension <path to vsix>

Check C++ extension for:

Get path to VSC
How to install extension...

Message to be displayed when we update extension to insiders when user installs stable into insider for first time:

We noticed you are using VS Code Insiders. Reload to use the Insiders build of the extension.
[Use Stable] [Reload]
We should do this only once if they haven't configured a channel

A user setting python.insidersChannel is added. Default value is Stable.
VSCODE INSIDERS
Expected first session:
Insiders is installed first, and then the following message is displayed:

We noticed you are using VS Code Insiders. Reload to use the Insiders build of the extension.
[Use Stable] [Reload]

Option 1 - 'Use Stable'

Setting gets set to 'Stable, Stable` is installed. We do not reload and No reload prompt shows up.

Option 2 - 'Reload'

Setting gets changed to 'InsidersWeekly' and we reload.

Option 3- Close the prompt

Setting gets changed to 'InsidersWeekly', we do not reload. Note insiders is already installed, but not used. (Will be using insiders from the next session)

Expected second session:

Open user settings.json. Verify setting python.insidersChannel shows up with the correct value. Here's what you will according to the option selected:

Option 1 - 'Use Stable'
Note:  You will see in the following behavior in Extension Development Host, ignore this. The actual behavior in the VSIX will be different. If using VSIX, you will note that Stable is installed and nothing happens, which is the expected behavior

Once extension activates, Stable will be installed again. You will get a Reload prompt, 'Please reload while switching between channels'. Ignore that.

Option 2 - 'Reload'

Insiders version of extension is installed.

VSCODE STABLE
Expected first session: No such prompt is displayed, user keeps using the stable extension.
ON CHANGING CHANNEL MID-SESSION
You will see the following commands in the command palette:

Switch to InsidersWeekly - Does not show up when channel is 'InsidersWeekly'. Using this will install insiders build and You will get a Reload prompt, 'Please reload while switching between channels'.
Switch to InsidersDaily - Does not show up when channel is 'InsidersDaily'. Using this will install insiders build and You will get a Reload prompt, 'Please reload while switching between channels'.
Switch to Stable - Does not show up when channel is 'Stable'. Using this will install stable build and You will get a Reload prompt, 'Please reload while switching between channels'.

I got a language server extraction failure:
Language server extraction failed
Error: ENOENT: no such file or directory, open 'C:\Users\brcan\.vscode-insiders\extensions\ms-python.python-2019.7.24761-dev\languageServer.0.3.22\cs\Microsoft.VisualStudio.Threading.resources.dll'
Starting Jedi Python language engine.

The prompt says "Please reload the window switching between insiders channel". I would reword that as "Please reload the window to change the insiders channel".

You still get prompted if you already have the setting specified. We should probably skip if it's set.

Making manual installs work
The problem is if you install via .vsix you will get it immediately overwritten by the "Stable" default setting. The proposed fix is:

Drop "Stable"
Add a "default" setting which is "we do nothing, VS Code handles things"
Rename "InsidersWeekly" and "InsidersDaily" to "weekly" and "daily", respectively)

This will then let .vsix installs work as expected. People can revert back using the built-in support in VS Code for rolling back to older versions. This also won't break people who are using forks of the extension as otherwise we would start forcibly updating them to stable or our insiders builds instead of their fork.

Suppose a user is using "weekly/daily", and he decides to install an older version of the extension. He would still be forced to use the insiders version of the extension. I don't think we want that.

@karrtikr I don't think it can be avoided. If you want to control what version of the extension you want installed you then need to be on the "default" setting to let VS Code handle it for you, otherwise you're handing installation control to us under "weekly" and "daily".

I have verified that I now have a "python.insidersChannel" user setting.  Switching it to "daily" it immediately downloaded the .vsix and prompted me to reload.  So that all looks good.
However...
From https://github.com/microsoft/vscode-python/issues/2772#issuecomment-510611220 I gather that, when using insiders already, I was supposed to be prompted about what I wanted to do.  I was never prompted.  It simply used the default setting, "off".  That's fine, but if that expected prompt was a requirement for this feature then this issue needs more work.  @luabud, what needs to be done here?

FWIW, Don manually double-checked about the prompt.  It worked as expected.  I must have been prompted a while back and VS Code still remembered.


Per-pipeline installation

There should be a way to install dependencies for only the pipelines that you are interested in running.

Added this for the contrast_phase pipeline which requires XGBoost.


use semaphore keyed by saga id

Info
Sagas with different IDs can be safely be processed concurrently. Create a semaphore per unique Saga Id rather than using a single sempahore.
Changes

...

Codecov Report

Merging #18 into master will decrease coverage by 3.4%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
- Coverage   26.89%   23.49%   -3.41%
==========================================
  Files          18       19       +1
  Lines         290      332      +42
==========================================
  Hits           78       78
- Misses        212      254      +42

Impacted Files
Coverage Δ

src/Chronicle/Managers/SagaCoordinator.cs
0% <0%> (ø)
:arrow_up:

src/Chronicle/Utils/KeyedSemaphore.cs
0% <0%> (ø)

Continue to review full report at Codecov.

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

Thanks for your PR! This does not fulfil requirements described in contributing.md file but I put your suggestions in my last commit. Thank you for your help anyway!


[5.6] Fix *scan methods for phpredis

This adds the adapter methods to properly utilize PhpRedis commands for scan, sscan, hscan, and zscan. fixes #24222 .... take 3.
I think there was some confusion caused by myself perhaps, I fell into an old work habit where if a PR was rejected, that meant a new branch because enough was wrong that it was beyond fixing. Clearly that is not what was expected, so I noticed the merge that caused the failed tests was drawing from the original branch. I won't be making that mistake again and will just continue on the same branch for a feature, but just to be clear the branch name changed and I added a v2 on the end. I apologize for that....still relatively new to contributing.
To be clear the most current branch is fix-scan-methods-for-phpredis-v2. I do still have the old branch locally, so if it makes it easier I can just move the changes from this branch to the original and retarget the PR.

Reverted all this. Causes tests on master to break completely. I'm never merging this on 5.6. You can try it submit it to master if you want or let someone else handle it.
/cc @tillkruss


Docs: Remove unnecessary parts in the issue templates

Overview

This PR refines the existing issue templates by removing unnecessary parts.
Changes

Removed the default title because sometimes to prevent from forgeting to modify it.
Removed the "additional contexts" section because we sometimes forget to delete it when there is no additional context. "Additional Contexts" is a generic title and cannot be used as is.

Note

Assignee Checklist:

[x] The base branch is correct (See: Types of Branches)
[x] The branch name follows the Branch Naming Conventions
[x] The correct assignees and reviewers have been designated for this PR
[x] The coding style follows the Coding Style Guide
[x] All the related issues are associated with this PR
[x] All criteria in the associated issues are met (please tick the checkboxes)
[x] My changes do not generate new warnings or errors (especially in the console)

Reviewer Checklist:

[ ] The code follows the generic best practices and our Coding Style Guide
[ ] Code is well-commented and easy to understand
[ ] UI changes accurately reflect the provided design

@kotaaaa @kanta1207 Thank you for your reviews!


[Admin][Order] Add button for downloading an invoice on order show page

I'd love to see a Behat test covering button's appearance! 👍


[Enhancement]: Switch from Google SDK to Google CLI and update Google Client Libraries BOM

Module
GCloud
Proposal
The dependencies must be updated to use the Google Cloud CLI, as well as library updates

Hi @ddobrin, you mean switching from gcr.io/google.com/cloudsdktool/cloud-sdk to gcr.io/google.com/cloudsdktool/google-cloud-cli in our tests, right? BigtableEmulatorContainer, DatastoreEmulatorContainer, FirestoreEmulatorContainer and PubSubEmulatorContainer already support both images.
Dependabot will run tomorrow, so, I'll wait for it to update images and dependencies.

Hi @eddumelendez
yes, that's the one.
I would suggest also updating the Google client libraries BOM:
testImplementation platform("com.google.cloud:libraries-bom:26.19.0")
and the Guava version
testImplementation 'com.google.guava:guava:32.1.1-jre'


How can I get the beta in STANDARD format?

Hi Bjarni,
I woule like to know how I can get the beta value in the STANDARD format, using the scaled genotype or no-scaled genotype? The two ways may get different beta value. I will be happy if you can tell me the right answer. Thanks for your kindly help.
Best,
Sheng

Hi Sheng, I apologize for the slow reply, but I was on holiday in April.
Anyways, the actual beta value is not used, only the sign.  The betas used by LDpred internally are derived from the p-value.  Let me know if this doesn't answer your question.
Best,
Bjarni


Canvas pixel color tests

With thanks to @pjanik for solving the Travis problem, I rebased this branch on the snapshot tests branch - though this is only one file, it does require the same configuration to pass the automated tests. Once the first PR is merged this can be used. @kevinsantos-cc you may want to have a look and see if these color-based tests are useful to you.

Looks good Chris, I can definitely see this being useful. Thanks for the comments, as well as the helpers Piotr.

@kevinsantos-cc, I'm fine, but not sure if @dstrawberrygirl was planning to add something here or not. I guess you guys can replace sleep with the new helpers and extract some code to helper function too.

@dstrawberrygirl and @kevinsantos-cc, any update on that? I guess it'd be nice if we get PRs cleaned up before we stop working on this project for a while.

Updated the branch to use the helpers that @pjanik has added to the project. I tried refactoring and creating a quick helper for the color tests but was unable to achieve the same result - if time permits, it might be good to revisit this tomorrow.


verify_delegate() document ValueError and TypeError

Fixes #1817
Description of the changes being introduced by the pull request:
Add missing documentation for ValueError and TypeError inside
Metadata.verify_delegate().
Signed-off-by: Martin Vrachev<EMAIL_ADDRESS>Please verify and check that the pull request fulfills the following
requirements:

[ ] The code follows the Code Style Guidelines
[ ] Tests have been added for the bug fix or new feature
[ ] Docs have been added for the bug fix or new feature

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1118

Relevant Lines:
1134

💛  - Coveralls


Added colour blocks

ive added colour blocks

i wasnt able to test because i develop on windows :)

don't edit your comment to ping me
please provide a screenshot of this in action. if it doesn't work on windows use WSL or something.


aviation style checklist:0.1.0

I am submitting

[x] a new package
[ ] an update for a package

Description: This is a template which is intended to be used to create checklists in a style that is inspired by aviation.

I have read and followed the submission guidelines and, in particular, I

[ ] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

I have not ticked selected a name that isn't the most obvious or canonical name for what the package does yet, as I am not sure the name suffices. I think the name is fine, but I would like some feedback first if possible.
Thanks

@elegaanz would the name "AeroCheck" be good?

Yes, perfect.

Should be ready now 😄

Thank you!

@elegaanz thank you for the review! And sorry for the hassle 😅 . Next time ill do it all correctly the first time.


[QA] No image preview of places on maps

Explorer Alpha build version:
0.3.170-main-251ca6c
Issue Description:

By clicking on places on the map or searching, there is no image preview or thumbnail for the scene.
Steps to reproduce:

Go to the map
Make a search or click on any parcel that has a scene deployed

Expected behaviour:
Previews or thumbnails should be visible
Platforms / OS:

[ ] Windows 11
[x] Windows 10
[ ] Mac Sonoma
[ ] Mac (specify the version on Additional Notes)

Evidence:

Additional Notes:

Already fixed in main


CID not implemented: McGroupStatusReq

Is this a bug or a feature request?
bug request
What did you expect?
rpc success
What happened?
rpc error
code = Internal desc = handle remote multicast setup command error: CID not implemented: McGroupStatusReq" grpc.code=Internal grpc.method=HandleUplinkData grpc.request.deadline="2019-09-22T08:50:51Z" grpc.service=as.ApplicationServerService grpc.start_time="2019-09-22T08:50:50Z" grpc.time_ms=5.085 peer.address="<IP_ADDRESS>:53912" span.kind=server system=grpc
What version are your using?
3.3.1
How can your issue be reproduced?
just send sensor msg
Could you share your log output?
time="2019-09-22T08:50:50Z" level=error msg="finished unary call with code Internal" error="rpc error: code = Internal desc = handle remote multicast setup command error: CID not implemented: McGroupStatusReq" grpc.code=Internal grpc.method=HandleUplinkData grpc.request.deadline="2019-09-22T08:50:51Z" grpc.service=as.ApplicationServerService grpc.start_time="2019-09-22T08:50:50Z" grpc.time_ms=5.085 peer.address="<IP_ADDRESS>:53912" span.kind=server system=grpc

On which port is the device sending its payloads? Could it be that you are using port 200? In this case it collides with the ports proposed for FUOTA:
https://lora-alliance.org/sites/default/files/2019-04/tr002-fuota_process_summary-v1.0.0.pdf

@brocaar  you are right, thank you for your reply!

Hello!
@brocaar, we use a device that is implemented on the specification of LoRaWAN v1.0.1. And this device uses port 201.
Because the specification "LoRaWAN Fragmented Data Block Transport v1.0.0 Specification" is optional, then only those devices that transmit large amounts of data should support it. Therefore, the device we use does not support it.
Specification "LoRaWAN Fragmented Data Block Transport v1.0.0"  is in addition to the specifications of the MAC layer LoRaWAN v1.0.2 and v1.1.
The device we use supports the specification of the MAC level LoRaWAN v1.0.1.
lora-app-server supporting the specification LoRaWAN v1.0.2 and v1.1 must support the operation of devices v1.0.0 and v1.0.1.
Changing the LoRaWAN MAC version in the Device Profile does not produce a result.
Can you fix it or help solve the problem?
30 16:17:29 loraservers lora-app-server[18237]: time="2019-09-30T16:17:29+03:00" level=error msg="finished unary call with code Internal" error="rpc error: code = Internal desc = handle remote fragmentation session command error: CID not implemented: PackageVersionReq" grpc.code=Internal grpc.method=HandleUplinkData grpc.request.deadline="2019-09-30T16:17:30+03:00" grpc.service=as.ApplicationServerService grpc.start_time="2019-09-30T16:17:29+03:00" grpc.time_ms=4.841 peer.address="<IP_ADDRESS>:49572" span.kind=server system=grpc