Disable scraping during startup

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I have noticed the integration takes a long time to complete during startup (~600s) of my HA instance. I guess it will take continue to increase as more and more sensors are added.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Is it possible to disable the integration/stop the scrape process during startup and perform the scraping once HA has started?
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I have thought about this before but I'm afraid it will screw up the sensor history as they'll probably have value null/unknown until they start scraping.
600s is a looooong time tough. Scraping for different instances happens in parallel, so not sure where this time is spent on. A slow website? Any chance you could share your configuration?
And/or could you enable INFO logging for multiscrape? It will show you something like:
[homeassistant.setup] Setup of domain multiscrape took 0.6 seconds
I'm curious what value it reports there for you.

I can see that it now takes around ~360s.
I did enable INFO logging but it did not show that particular statement.
However, I enabled DEBUG logging and this is from the logs:
2022-01-13 22:32:51 DEBUG (MainThread) [custom_components.multiscrape.scraper] Updating from https://covidlive.com.au/
2022-01-13 22:32:51 DEBUG (MainThread) [custom_components.multiscrape.scraper] Updating from https://www.racv.com.au/bin/racv/fuelprice.5.json
2022-01-13 22:32:51 DEBUG (MainThread) [custom_components.multiscrape.scraper] Updating from https://www.racv.com.au/bin/racv/fuelprice.2.json
2022-01-13 22:32:51 DEBUG (MainThread) [custom_components.multiscrape.scraper] Updating from https://www.melbournepollen.com.au/
2022-01-13 22:32:51 DEBUG (MainThread) [custom_components.multiscrape.scraper] Updating from https://www.sunsmart.com.au/uvalert/default.asp?version=australia&locationid=xxx
2022-01-13 22:32:51 DEBUG (MainThread) [custom_components.multiscrape.scraper] Updating from https://www.sunsmart.com.au/uvalert/default.asp?version=australia&locationid=xxx
2022-01-13 22:33:06 DEBUG (MainThread) [custom_components.multiscrape] Finished fetching scraper data data in 14.897 seconds (success: True)
2022-01-13 22:33:06 DEBUG (MainThread) [custom_components.multiscrape] Finished fetching scraper data data in 15.255 seconds (success: True)
2022-01-13 22:33:07 DEBUG (MainThread) [custom_components.multiscrape] Finished fetching scraper data data in 15.633 seconds (success: True)
2022-01-13 22:33:07 DEBUG (MainThread) [custom_components.multiscrape] Finished fetching scraper data data in 16.033 seconds (success: True)
2022-01-13 22:33:08 DEBUG (MainThread) [custom_components.multiscrape] Finished fetching scraper data data in 16.592 seconds (success: True)
2022-01-13 22:33:08 DEBUG (MainThread) [custom_components.multiscrape] Finished fetching scraper data data in 17.002 seconds (success: True)

I'm open for ideas to improve performance, but screwing up sensor history with 'unkown' values, is not an option in my opinion. Will close for now.


It doesn't add closing bracket in INSERT mode with smartparens strict mode enabled

| is my cursor.
What did you expect to happen?
In INSERT mode
(comment

|my-func

)

When I type ( I expect that closing round bracket will be added.
(comment

(|)my-func

)

What actually happened?
It doesn't
(comment

(|my-func

)

Additional details:

I have enabled smartparens global strict mode.

Basically it happens only if next symbol after cursor is not a space or \n, but some character.

Additional:
When then I type closing bracket it just move existing one to the end of word
(comment

(my-func)|

If I press closing bracket again it says 'we can not insert unbalanced closing delimiter in strict mode'

The original issue is not a bug. Please familiarize yourself with the default smartparens config in the same file and tweak as you like. e.g.
(after! smartparens
  (sp-pair "(" nil :unless '(:rem sp-point-before-word-p)))


Failed compilation due to trait not implemented

Discovered this issue while trying to build version v0.1.2 inside a container (rust:1-slim-bookworm) and with regular cargo installation.
How to reproduce
FROM rust:1-slim-bookworm
RUN apt-get update && apt-get install -y pkg-config libssl-dev
RUN cargo install mega-cli

Otherwise just call cargo install mega-cli to reproduce.
Error message
error[E0277]: `std::option::Option<std::string::String>` doesn't implement `std::fmt::Display`
  --> /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/mega-cli-0.1.2/src/commands/auth/me.rs:53:9
   |
53 |         user.country_code,
   |         ^^^^^^^^^^^^^^^^^ `std::option::Option<std::string::String>` cannot be formatted with the default formatter
   |
   = help: the trait `std::fmt::Display` is not implemented for `std::option::Option<std::string::String>`
   = note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
   = note: this error originates in the macro `format_args` which comes from the expansion of the macro `crate::info` (in Nightly builds, run with -Z macro-backtrace for more info)
For more information about this error, try `rustc --explain E0277`.
error: could not compile `mega-cli` (bin "mega-cli") due to 1 previous error
error: failed to compile `mega-cli v0.1.2`, intermediate artifacts can be found at `/tmp/cargo-installlgdlGF`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

Hello, thanks for reporting this issue.
This was due to me updating the underlying mega library with a minor semver update (v0.7.4), in order to address the bug reported in #2.
I wrongly assessed that the change would not require a dedicated mega-cli release in order to make use of that fix.
I've now made a new v0.1.3 release of mega-cli, which fixes this compilation error.
If you wish to make your Dockerfile more resilient to similar issues in the future, you may consider adding the --locked flag to your cargo install command, like so:
cargo install --locked mega-cli

This will stick to using the exact crate versions listed in the Cargo.lock file, instead of optimistically updating dependencies using semver.
I'm sorry for the inconvenience, and I'll be more careful going forward when releasing updates to the mega library.


Fix Config File Path  Issue

Why make this change?

Closes #1674 ConfigFile was not found when running in the Azure Container Apps.

What is this change?

Because of the way we used to fetch the cofigFileName, the path was lost, due to which using config file present in a different directory was giving file not found error.
So we updated the method to fetch the configFileNamewihoutExtension to keep the original path.
To run Azure Container Apps --ConfigFileName is provided with the full path name to the mounted config file.

How was this tested?

[X] Running In Azure Container Apps
BEFORE:

AFTER:

[X] Local Testing
BEFORE:

AFTER:

[X] Unit Tests

In the past, we've had issues with local Docker containers finding the desired config file. The root cause of those issues where an incorrect file/folder mapping to the Docker container. could that be the case with this issue too?
In the PR description, can you describe what behavior you observed in Az Container apps?

Was the desired config file being overwritten in the file share, when looking for a config file in the root of the file share?
Is this issue only seen when the config file is placed in a folder? (not root of file share) e.g. FileShare::\\config.jsonvs. FileShare::\\subFolder\config.json


RFE: API semantic versioning

Version numbering allows the clear identification of built artefacts and their compatibility to their respective consumers. Semantic versioning’ which is based on 3 numbers and an alphanumeric string:
[major] 	. 	[minor]	 .	 [patch]

The major number is bumped up when an incompatible (ie. breaking) change has been made to the api from the previous version. So any developer planning to use this library can easily see that a breaking change has been included.
The minor version is bumped up when a change has been made to the functionality within the artefact that is still backwards compatible. ie. the api has not been changed however the functionality is now different to previous.
I would focus on managing Major and Minor releases, that implies:

Major releases (2.0.0) : if toolbox detects a previous major release in 3scale, for instance already exists the release 1.x then -> Create a new services and import service specification.
Minor releases (1.0.0) : if toolbox detects this is minor upgrade, then rename older service in 3scale and reimport the Active Docs.

My opinion is that hard-coding this behaviour into the toolbox based just on the spec version number would be unexpected behaviour in some cases by customers, and would inflexible and not adapt to different customers' ways of handling versioning.
An update to a specified system_named service would change to be a create of a new service instead and then we'd have two services (would need to capture the new service's system_name?).
You'd also lack control over the previous version and a separate command would be needed to delete the old one (when the customer decides to deprecate it).
If we added a flag to the toolbox to control this behaviour, then the caller of the toolbox (e.g. a Jenkins pipeline) would have to implement the logic to use the flag or not, thus externalizing part of the logic anyway. So it would be similar to implementing the logic there (outside the toolbox) to do an update or a create.
So, for me, the implementation that would make most sense would be for the toolbox to provide predictable primitive commands (i.e. NOT do this), and have this customer-dependant versioning logic outside of the toolbox (e.g. in a workflow, or jenkins pipeline) and invoke either an update or a create, with the OAI spec.

Semantic versioning has became an industry ipso facto standard approach to resolve the problem of managing API releases. I've seen that ALL companies with I've have been worked or they are already following semantic versioning or they are thinking to follow it.
In my opinión this is one of the most important feature of Toolbox for these reasons:

Everybody who implements an API Management solution must deal with the versioning topic. It doesn't make sense enforce all customers to develop its own semantic versioning, when this feature can be provided OOTB only once by the API Manager.
API versioning is an important matter of the API Manager Platform, which it should provide a solution to handle all use cases (at least described in the standard semantic versioning). Jenkins orchestate deployments pipelines, promotions among environments, it isn't responsible for knowing how to replace a 3scale Active Docs.
-Current 3scale Ansible CICD playbook provides this feature OOTB, the feedback always has been positive for the useful capabilities.
-Perform the same versioning mechanism for the whole company API Lifecycle.
-Regarding flexibility a flag disabling this behaviour would be enough, but at least from API Manager layer, we are providing a solution for dealing API versioning using the standar that almost everyone is using.
Also there are business case a part of customer demand:
Benefits to implement this feature in Toolbox: we are talking about:
Improving time to market (less time during 3scale implementation)
Avoid developers error prone (avoid support cases)
Less ramp up time to learn 3scale technology for partners or developers. Implementers don't have to know deeper 3scale techincal knowledge.
Rapid integration with current API backend lifecycle.

I wouldn't hard code it, I would probably accept a version number optionally. If it's minor release then update, if it's major, then create new service. The param is optional so if not passed, by default always updates the service. The caller (e.g. Jenkins pipelines) would have to manage passing versions, yes.

Will be implemented by 3scale API. Not a toolbox issue anymore
https://issues.redhat.com/browse/THREESCALE-2343


[SMALLFIX]Replace explicit type argument with <>

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2558/
Test PASSed.

alluxio-bot, merge this please


if ldapadd exits non-zero then fail.

Update the exec command to fail if the ldapadd command exits non-zero.  Previously, the ldapadd command's exit status was ignored and the ".done" file was created whether or not ldapadd was successful.

Sorry for replying so late.
Merged, thanks for your contribution!


Update create-an-account.md

Old info was pointing users to a MR "Preview", we are now in GA and its just the regular azure portal

@FlorianBorn71

Can you review this PR?

IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks for fixing @Jak-MS! I will submit now

#sign-off


update fork repository with original (head) repository

rebase and merge (keep forked repository in sync with head repository)


error

rsyncy -arv --stats /home/iomari/downloads iomari:/temp/gittemp/
[::::::::::::::::::::::::::::::]   0% |           0 |                | 0:05:08 | scan \
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(644) [sender=3.1.3]

BTW, running the command as rsync works perfectly.

I'm unable to reproduce this.


Set basic server-side notification settings

We should support the three user settings enable_offline_push_notifications, enable_online_push_notifications, enable_stream_push_notifications. These let the user control, at a coarse granularity, whether and when the server sends them push notifications.
The user docs for these settings are here:
https://zulip.com/help/mobile-notifications
https://zulip.com/help/stream-notifications
In particular these three are supported in the legacy zulip-mobile app.
In the API, they appear in the same three places (for initial data, events, and user requests to edit them) as all user settings. See the existing settings in our code listed in the UserSettingsName enum, and look at the references to any one of those enum values.

This came up in beta feedback today:

As I enabled notifications for Flutter beta and allowed everything on OS/Android level. And at the end came an idea that I disabled them via web app.


feat: add support for hardcoded datasource uid

Changes:
Hardcoded datasource uids are now preserved, we can set the fixed UID of datasource for GrafanaDashboard using alerting
Fixes: https://github.com/grafana-operator/grafana-operator/issues/1056

Ping @weisdd , since you did the dashboard implementation

@christhai thanks for the PR!
I think it's not yet ready to be merged. Some issues:

In onDatasourceCreated, there's inconsistency between which uid a datasource is created with and which one is added to grafana status. The latter is used to clean up a datasource when CR is deleted. - I think that won't work with the current implementation;
ExistingId tries to find a datasource by CR's uid, so the operator would always think a data source with hardcoded uid does not exist;
The code doesn't have logic for a case where uid gets changed.

If you'd like to continue working on this PR, please, ping me when you feel it's ready to be reviewed again.

@weisdd if possible, can you work on this feature on your side?   it should be faster, thanks

@christhai sure


Search After - Scroll problem.

I have been problem with the uso of scroll.
"Result window is too large, from + size must be less than or equal to: [10000] but was [10020]"
I need use "Search After" to fix, but I not found on Jest.
https://www.elastic.co/guide/en/elasticsearch/reference/5.2/search-request-search-after.html
Any help to fix?
More reference about problem:
https://stackoverflow.com/questions/42972508/how-to-get-more-than-10-thousand-documents-at-a-time-from-elasticsearch-using-je
https://stackoverflow.com/questions/35206409/elasticsearch-2-1-result-window-is-too-large-index-max-result-window

Hi @matheussl22 , I think that searchAfter is usable with Jest. I will check how we can integrate it.

SearchRequest searchRequest = new SearchRequest(INDEX_NAME);
SearchSourceBuilder source = searchRequest.source();
source.query(QueryBuilders.termQuery("condition","1"));
source.sort("condition",SortOrder.DESC);
source.searchAfter(new Object[]{id});
source.from(0);
source.size(size);
SearchResponse search = restHighLevelClient.search(searchRequest, RequestOptions.DEFAULT);
org.elasticsearch.search.SearchHits hits = search.getHits();
List<Map<String, Object>> collect = Arrays.stream(hits.getHits()).map(temp -> temp.getSourceAsMap()).collect(Collectors.toList());


Creation of lineage for artifact and execution using D3.js

Related Issues / Pull Requests
List all related issues and/or pull requests if there are any.
Description
Include a brief summary of the proposed changes.
What changes are proposed in this pull request?

[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected; for instance,
examples in this repository need to be updated too).
[ ] This change requires a documentation update.

Checklist:

[ ] My code follows the style guidelines of this project (PEP-8 with Google-style docstrings).
[ ] My code modifies existing public API, or introduces new public API, and I updated or wrote docstrings that
uses Google-style formatting and any other formatting that is supported by mkdocs and plugins this project
uses.
[ ] I have commented my code.
[ ] My code requires documentation updates, and I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.

A refactoring suggestion, if possible, let's move all "query" files to a particular folder.

Hi Shreyas, thank you for the feedback! I understand the suggestion to move all query files into one folder. However, moving them now would add code overhead and require extra testing to ensure everything works correctly. Since these are the final files with no further additions, keeping the current structure might be more efficient to avoid unnecessary changes. Let me know your thoughts!

Sure, for now we can have same file structure. We can have dedicated PR for this refactoring sometime later.

@annmary-roy this PR is ready to go from our side


Add the e2e-k3s-runner crate to run e2e test

Closing up some old PR's.  Freel free to re-open or create new if still wish to get it merged


Replace ArrowError with DataFusionError in DF context

Which issue does this PR close?

Closes #5039.
Rationale for this change
See #5039

What changes are included in this PR?
Replace ArrowError with DataFusionError in DF context

Are these changes tested?
Yes

Are there any user-facing changes?
User will get DatafusionError::ArrowError instead arrow::ArrowError for datafusion contexts

@tustvold please check whenever you have time, the code rotting fast :)

Thanks @tustvold for your review. Fixed all the comments

cc @liukun4515 , You may also be interested in this.


[do not merge] Rebased 001e6c7

This is being tested here: https://github.com/stackrox/stackrox/pull/3255

Right, the conflict doesn't matter because this will be force-pushed. It is a straight-up rebase of our changes, preserving linear history.
I'm holding off on force-pushing to main because this causes a bump in K8s deps to v0.24.x, which is currently failing in rox: https://github.com/stackrox/stackrox/pull/3255

This has been promoted to the new main branch. The old state of main has be preserved as branch main-backup-2022-10-05.


Implement managed identity for Cosmos DB converter

Implement managed identity support for Cosmos DB converter

Implemented in PR: https://github.com/Azure/azure-webjobs-sdk-extensions/pull/802


ManyToMany example

DBFlow Version: 3.1.1
Issue Kind (Bug, Question, Feature): Question
Description:
Can someone provide a working example of ManyToMany relationship and usage of @ManyToMany annotation + how to properly set up all others foreign keys and methods. I've tried to use it, insert manually into auto-generated table but it crashes with SQLite exception about too many files opened or too large transaction.
Thanks

Not sure if this is the place to post this question, but if you could provide more info into what is generated and your models look like, that might help.


Improved Truncation accordingly

Fixes: https://github.com/zulip/zulip/issues/25260
I tried to enhance the truncation logic; however, the issue comprised two tasks. The initial task involved rectifying the truncation logic, The second task required checking the standards for notification APIs. Regrettably, I was unable to locate relevant documentation. Could you kindly provide some resources?

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@alya can you please review my PR

Your commit and PR needs to follow our guidelines and style; please carefully read through https://zulip.readthedocs.io/en/latest/contributing/commit-discipline.html and https://zulip.readthedocs.io/en/latest/git/pull-requests.html

@karlstolley okay let me fix this

Since my commit has deleted, i tried to fix this branch with rebase and gitk but it did not help. I have resolved this issue and made a new PR #28515


Support all eosio blockchains

https://github.com/greymass/eos-voter/issues/314

Added a couple of commits to cover https://github.com/greymass/eos-voter/issues/336. I figured it would be easier to base my work off of this branch so we won't have to merge everything several times.


can't save to local disk

after downloading  completely, sometimes I can't save the videos to local.
I was downloading many  videos at a time

sorry to hear that, can you share a link for a specific video?

Will reopen if a link will be shared


Typescript definitions are outdated

For example, now Collection.prototype.find(query) returns an array while it is defined as LokiCollection.find(query: LokiQuery): LokiResultset<E> in the typescript definitions.

Your right, collection find should return object[] or null.  It should be just collection.chain() that returns a (Loki) 'Resultset'.
@TeamworkGuy2 kindly provided those definitions.  I've  not yet had time to research this enough to be familiar with the syntax to fix any issues with them.
If you are able to, it would be nice if you could help update those as our v1.4.x (main) branch is stable (maybe a few non-breaking extra constructor options we may want to add).   Otherwise I will add this to my todo list for when I (or anyone interested in updating these) can get around it.

If I ever have spare time I'll update it.  But it's a 6+ hour process for me to extract accurate definitions from a library of loki.js' size and it's a very boring task :)

Great... while my request was meant for @mnasyrov, if you ever get some time, it would be appreciated :)
Would be nice if there was a way to leverage jsdoc/closure annotations to scaffold some definitions.

Sorry guys, have no time right now.

There are definition file generators from js like dtsmake, but they also require manual work to define type structures.

Moving the whole of the project to TypeScript could be an option, since that could favor reading the code and submitting patches/issues/contributions.
--R

Any update on this?

This project look pretty awesome, too bad there are no up-to-date TypeScript typings available. Just wanted to add my +1 for conversion to TypeScript or maintaining official typings.

I found some time to update the definition; I'll hopefully be finished by the end of the weekend.

@thasmo
Have a look at https://github.com/LokiJS-Forge/LokiJS2 - a official successor, converted to Typescript (but still beta).

@Viatorus Thanks! Tried it but it seems the npm package doesn't include typing or do I miss something?

Next update should have them - probably tomorrow.
On Nov 25, 2017 13:06, "Thomas Deinhamer"<EMAIL_ADDRESS>wrote:

@Viatorus https://github.com/viatorus Thanks! Tried it but it seems the
npm package doesn't include typing or do I miss something?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/techfort/LokiJS/issues/467#issuecomment-346936625,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADeCl_WqEMpXL9E8WLW8wXhEU6b36aSnks5s6ALJgaJpZM4JtrFC
.

Latest lokijs 1.5.1 definition just got merged to definitely typed (pull: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/21747, commit: https://github.com/DefinitelyTyped/DefinitelyTyped/commit/766089f4e8107fd0fba147ed4543ae4b3cb0b3b8).
Should auto update to npm in a day or two.

I can't get how do I use LokiIndexedAdapter with typings now. :(

@foxel I'm not sure how LokiIndexedAdapter works, I've never used it.  I probably won't have time to analyze the code and write a definition in the near future. :/
If you're familiar with LokiIndexedAdapter, please help write one up and send a pull request to DefinitelyTyped!
Also take a look at these definitions inside lokijs, maybe they're related to what you're looking for:

LokiPersistenceAdapter
LokiMemoryAdapter
LokiPartitioningAdapter
LokiFsAdapter
LokiLocalStorageAdapter

@TeamworkGuy2 Will the typescript definitions for 1.5.2 work for loki 1.5.5 or are their too many changes?

@ShiroiKuma A quick diff of the src/lokijs.js files from releases version 1.5.2 zip to 1.5.5 zip shows there's several changes to method signatures and enumerations, for example LokiOps has some new values and Resultset.prototype.simplesort 2nd parameter changed from a boolean to an options object (although it looks like you can still pass a boolean for backward compatibility).
Answer: I'm not sure, I don't work on LokiJS, I just wrote a one time definition for it which I updated once or twice.

I did update our typescript definitions but apparently i missed a versioning number somewhere because when i run :
npm i @types/lokijs

it will report version 1.5.2, however the definitions are actually 1.5.3 which are latest.
@TeamworkGuy2 : any idea why that might be?

@obeliskos I'm not sure why it's wrong, version numbers of npm @types packages are controlled by the version string in the definitely typed definition file (for lokijs see https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/lokijs/index.d.ts)
You're right though, NPM https://www.npmjs.com/package/@types/lokijs lists the version as 1.5.2.
I'd report it as an issue to the DefinitelyTyped repository, although that repository has over 2000 open issues and the Microsoft team doesn't curate it much.
You could look at the types-publisher tool the definitely typed team use for publishing the packages: https://github.com/Microsoft/types-publisher
looks like you changed


LibXML::parser failures leak memory

Which can be seen in 11memory.t. Number of leaked objects jumps after 11 Multiple failures

.myDoc doesn't get GC by LibXML in xmlParseContext, so we've got to make sure we clean up any that haven't been published due to errors.


Add ppc64le architecture

Add ppc64le architecture for the current architecture check.
Description
Ability to build OpenSearch on ppc64le architecture
Issues Resolved
https://github.com/opensearch-project/OpenSearch/issues/1303
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@helix-loop Thanks! The PR needs git commit --amend -s to get DCO to pass.
In the meantime, do we need both ppc64 and ppc64le? And what hardware did you test this on?

@dblock It would be better to have both, but I can only test and tested this on ppc64le.

Is this ready? Unit tests?

@helix-loop are you still working on this? What is left to get this from draft to ready-to-merge?

Currently not. I guess the Unit tests are missing to get this ready. However https://github.com/opensearch-project/OpenSearch/pull/3930 seems to be further.

@helix-loop : Are you still working on this ?

@helix-loop Thank you for your contribution! I'm afraid that I have to close this PR.
As mentioned in issue #1303, the code change is made by commit https://github.com/opensearch-project/OpenSearch/commit/d76adf3504e3001a84d53177af8ea36af2cc65c1


.hdbtable indeces type in not taken into account

If we have the following hdbtable definition:
table.schemaName = "DBADMIN";
table.temporary = true;
table.tableType = COLUMNSTORE;
table.loggingType = NOLOGGING;
table.columns = [
	{name = "Col1"; sqlType = NVARCHAR; nullable = false; length = 20; comment = "dummy comment";},
	{name = "Col2"; sqlType = INTEGER; nullable = false;},
	{name = "Col5"; sqlType = NVARCHAR; nullable = false; length = 20; defaultValue = "Defaultvalue";},
    {name = "Col66"; sqlType = NVARCHAR; nullable = true; length = 20; defaultValue = "Defaultvalue";},
    {name = "Col77"; sqlType = NVARCHAR; nullable = true; length = 20; defaultValue = "Defaultvalue";}];
table.indexes =  [
	{name = "BB112"; unique = true; order = DSC; indexColumns = ["Col2"];},
	{name = "BB212"; unique = true; order = DSC; indexType = B_TREE; indexColumns = ["Col1"];}];
table.primaryKey.pkcolumns = ["Col1", "Col2","Col5"];

the SQL to be generated is:
CREATE COLUMN TABLE "DBADMIN"."p1::file" ( "Col1" NVARCHAR (20) NOT NULL , "Col2" INTEGER  NOT
 NULL , "Col5" NVARCHAR (20) DEFAULT 'Defaultvalue'  NOT NULL , "Col66" NVARCHAR (20) DEFAULT 'Defaultvalue'  , "Col77" NVARCHAR (20) DEFAULT 'Defaultvalue'  , PRIMARY KEY("Col1" , "Col2" , "Col5") , CONSTRAINT "BB112" UNIQUE ( "Col2" ), CONSTRAINT "BB212" UNIQUE ( "Col1" ))

As you can deduce by the snippet, the index type is not considered at all. All indeces have been created as normal constraints. This might be a limitation on our side.

Investigation:
No matter what the index type is (B_TREE or CPB_TREE) in case of table.tableType = COLUMNSTORE; the value persisted in the DB is INVERTED VALUE.
If the indexType is set to B_TREE or CPB_TREE when creating ROW table
CREATE ROW TABLE "DBADMIN"."row"( "Col1" NVARCHAR (20) NOT NULL , "Col2" INTEGER  NOT
 NULL , "Col5" NVARCHAR (20) DEFAULT 'Defaultvalue'  NOT NULL , "Col66" NVARCHAR (20) DEFAULT 'Defaultvalue'  , "Col77" NVARCHAR (20) DEFAULT 'Defaultvalue'  , PRIMARY KEY("Col1" , "Col2" , "Col5") , CONSTRAINT "I1" UNIQUE BTREE ( "Col2" ), CONSTRAINT "I2" UNIQUE CPBTREE ( "Col1" ))

, then the index type is persisted as BTREE UNIQUE and CPBTREE UNIQUE

Currently we don't support ROW table creation, so a new issue will be created this to be implemented, so it will make sense to have indexType support as well.

Refference for index Types:
https://help.sap.com/viewer/4fe29514fd584807ac9f2a04f6754767/2.0.03/en-US/20a7044375191014a939f50ae14306f7.html

Issue cloned to https://github.com/eclipse/dirigible/issues/1270

Fixed with: https://github.com/eclipse/dirigible/pull/1289


Typescript errors with all ViewStyle props

I'm feeding styles from StyleSheet.create into topViewStyle and cameraStyle, but getting errors that I think are related to wrong type definitions.
How can it be reproduced?

Build details?

"react-native-qrcode-scanner": "^1.2.1",

I think this should fix it. #185

@moaazsidat we should close this one because it seems to be fixed along with #185


[DEM-942] Fix for Qiskit Aqua VQE

Added max_experiments to configurational. It is an optional but necessary for aqua.
texparams in QasmInstructions are gone with qiskit terra 0.8.0.

Coverage remained the same at 100.0% when pulling 72eafae86137ac8df786f9a0df8caf41e74b6c70 on feature/dem942/aquavqe into 0706253ad3a4cf1539a41ebb01c0d014219d95fa on dev.


Feature request: What if you can add iOS emoji's instead of only Android ones?

See this article, for example. They've used iOS emojis on the Android platform with the help of the Android package.
Would love to see this in feature updates. Thanks ;)

Interesting, but I think Android users won't enjoy suddenly iOS emojis that they aren't used with 🤔 Currently I'm not planing to make this possible. If you need this I would rather suggest to fork the repository and apply those changes directly.


Compilation failure (mistralrs-paged-att)

Describe the bug
Trying to build current master with cargo build --release --features "cuda flash-attn" results in compilation failure:

That's my second attempt to build, where the first attempt failed because of #569
SO: Windows 11 x64
Terminal: Powershell
Cuda Toolkit: 12.5
Latest commit
ba40a2b

@vitorfdl I think #589 should resolve this, can you please confirm with:
git pull
git switch windows_pa_build_fix

And then rebuild?

cargo build --release --features "cuda"                                                                          pwsh  20:38:39 
   Compiling mistralrs-pyo3 v0.1.26 (C:\ai-models\mistral.rs\mistralrs-pyo3)
   Compiling mistralrs-bench v0.1.26 (C:\ai-models\mistral.rs\mistralrs-bench)
   Compiling mistralrs-server v0.1.26 (C:\ai-models\mistral.rs\mistralrs-server)
error: linking with `link.exe` failed: exit code: 1181
error: could not compile `mistralrs-bench` (bin "mistralrs-bench") due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: linking with `link.exe` failed: exit code: 1181
error: could not compile `mistralrs-pyo3` (lib) due to 1 previous error
error: linking with `link.exe` failed: exit code: 1181
error: could not compile `mistralrs-server` (bin "mistralrs-server") due to 1 previous error

The changes seems to have fixed the problems that were popping up previously. But now there is this new error when trying to compile with CUDA.

Yeah, that makes sense. If it is compiling mistralrs-server, it compiled mistralrs-core so the CUDA compilation errors should be gone.

Yeah, usually when I got linking issues is on a lib that I just need to install.
In this case, the error is    = note: LINK : fatal error LNK1181: cannot open input file 'mistralcuda.lib'
So I'm unsure if I can fix that myself.

@vitorfdl I just opened #591 which should fix this, can you please run:
git pull
git switch cuda_kernels_build_windows

Building with cuda seems fixed. Now as for the flash-attn, I'm still getting errors:
--- stderr
 vitorfdl    mistral.rs   cuda_kernels_build_window ≡  1  44.394s⠀   cargo build --release --features "cuda flash-attn"                                                       pwsh  04:44:07 
   Compiling candle-flash-attn v0.6.0 (https://github.com/EricLBuehler/candle.git?rev=c967be9#c967be9c)
   Compiling mistralrs-core v0.1.26 (C:\ai-models\mistral.rs\mistralrs-core)
error: failed to run custom build command for `candle-flash-attn v0.6.0 (https://github.com/EricLBuehler/candle.git?rev=c967be9#c967be9c)`

Caused by:
  process didn't exit successfully: `C:\ai-models\mistral.rs\target\release\build\candle-flash-attn-a145d740d88eab38\build-script-build` (exit code: 101)
    --- stdout
    (...)
  flash_fwd_hdim32_bf16_sm80.cu
  flash_fwd_hdim96_fp16_sm80.cu
  flash_fwd_hdim128_fp16_sm80.cu
  flash_fwd_hdim160_bf16_sm80.cu
  flash_fwd_hdim224_fp16_sm80.cu
  flash_fwd_hdim160_fp16_sm80.cu
  flash_fwd_hdim224_bf16_sm80.cu
  flash_api.cu
  thread '<unnamed>' panicked at C:\Users\vitorfdl\.cargo\registry\src\index.crates.io-6f17d22bba15001f\bindgen_cuda-0.1.5\src\lib.rs:262:21:
  nvcc error while executing compiling: "nvcc" "--gpu-architecture=sm_89" "-c" "-o" "C:\\ai-models\\mistral.rs\\target\\release\\build\\candle-flash-attn-b7579997ed1ea5c6\\out\\flash_fwd_hdim128_fp16_sm80-759fdfecd1f0ed1c.o" "--default-stream" "per-thread" "-std=c++17" "-O3" "-U__CUDA_NO_HALF_OPERATORS__" "-U__CUDA_NO_HALF_CONVERSIONS__" "-U__CUDA_NO_HALF2_OPERATORS__" "-U__CUDA_NO_BFLOAT16_CONVERSIONS__" "-Icutlass/include" "--expt-relaxed-constexpr" "--expt-extended-lambda" "--use_fast_math" "--verbose" "kernels/flash_fwd_hdim128_fp16_sm80.cu"

@vitorfdl can you please put the error in a GH Gist?

@vitorfdl looks like Flash attention V2 is not compatible with Cutlass V3 on Windows (refs Dao-AILab/flash-attention/#345, docs). I think if you compile without this it should be fine!

@vitorfdl looks like Flash attention V2 is not compatible with Cutlass V3 on Windows (refs Dao-AILab/flash-attention/#345, docs). I think if you compile without this it should be fine!

You mean, compiling without the -fa parameter?

Yes, without --features flash-attn should work

Yeah, I've confirmed in earlier comments that building with cuda only works fine.
But then I lost the flash-attn feature right? I've compiled llamacpp and it does make a lot difference in speeds to have flash attention working.
Nonetheless, I think the issues are fixed as I can now compile mistralrs

@vitorfdl closing as there have been no comments for a bit. Please feel free to reopen.


Tests fail on node 18

Somehow, native fetch is being invoked in the jsonld document loader, bypassing mocks
(node:81130) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
    jsonld context caching
      ✗ fetches and caches new contexts
        - jsonld.InvalidUrl: Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.
      ✗ caches redirected contexts by original url
        - jsonld.InvalidUrl: Dereferencing a URL did not result in a valid JSON-LD object. Possible causes are an inaccessible URL perhaps due to a same-origin policy (ensure the server uses CORS if you are using client-side JavaScript), too many redirects, a non-JSON response, or more than one HTTP Link Header was provided for a remote context.

nock issue for reference - https://github.com/nock/nock/issues/2397

@wmurphyrd the workaround of using node --no-experimental-fetch is not working for me. Am I doing something wrong?


feat: New nitro binary file for older CPU generation

Problem
Some users now use older generation of CPU, we need to build an additional nitro bin file for these machines end integrate that to Jan App
Success Criteria

a new bin file for nitro with older version of CPU suppored
intergrate to Jan app successfully

Close this ticket since LLAMA_AVX and LLAMA_AVX2 is enable by default in llamacpp if LLAMA_NATIVE=OFF https://github.com/janhq/nitro/pull/368

doesn't seem it working @hiento09


Where to find datasets for wake word detection training?

Hello. I think it would be nice to include some links or hints in the README about this.

The problem is that I have no idea where to find those. I was recommended to use these ones https://github.com/Picovoice/wake-word-benchmark/tree/master/audio but you'll still need to collect the records with no wakeword sound.
What I did with the wakeword I built is to collect some minutes of records from a podcast through the microphone by running a for loop in a bash script using rustpotter-cli records --ms 2000 $i.wav, there were still many false positives in my live tests so I just collected a bunch of false positives using rustpotter-cli spot -t 0.8 --record-path ./noises trained.rpw (the 'noises' folder needs to exists), I also added some more positive detections recorded the same way to balance the numbers, at that point the medium and large model sizes started to be confident.
I also noticed that the audio quality matters, I collected all the initial records using my MacBook microphone with captures very clean sound, when I changed to use the model on my Jabra speaker with a Raspberry PI, I have to take some records there and added it to the dataset to achieve similar performance, because it captures the audio with some minor eco and background noise. That is another thing that stopped me to trying to collect and share a dataset, at the end it seems like a task that requires a group of people with several devices to be involved in.
Currently I'm using a medium size model with threshold 0.93, min counter 15, and the gain normalizer filter and I having a pretty good experience where the detection works most of the time even when I'm watching tv.
In case you are interested on my setup, I'm using it with OpenHAB with a whisper.cpp add-on I'm working on (for voice generation I'm still using a cloud service), and it gives me an acceptable experience, my server is running in an Orange Pi 5, I will get a Raspberry 5 in a couple of weeks, which can be overclocked to 3.0hz I think, I hope it works a little faster there. I'm using a small fine tuned whisper model for Spanish I found on HF. As speaker I'm using a Jabra Speaker2 40 connected to a Raspberry Pi Zero 2 W (previously I was using an older Jabra speaker but the sound was not too good as commented).
https://github.com/GiviMAD/rustpotter/assets/9007708/d40625aa-07eb-4714-a1c8-70a7d78c63bb
The setup is summarized here https://community.openhab.org/t/dialog-processing-with-the-pulseaudiobinding/148191, still I don't think anyone has tried it and succeed.

There is Mozilla Common Voice. And the words cut are provided by mswc. I could add a PR.


fix: docker build issues

Addresses build issues in Dockerfiles. Yarn was not pulling files as expected, defaulting to PnP rather than the module folder.
Changes 🚧

Adds any vitest config ephemeral files to ignore files.
Enforce node_modules for Yarn in docker build files.

To test 🔬

You can run yarn nx run registration1:container, while Docker is running, and ensure the build of the container completes.

Rolling these changes into PR #1869, as they serve as a base for that.


New Crowdin translations

Enjoy!

Coverage remained the same at 30.013% when pulling f420521ffda787596715b20e9f151ac51150d230 on l10n_master into 44e4e1a17232fc7859f2fc2532ecebd7cd080652 on master.


Chore: Update infiniteScroll type

Please make sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

el-table裡面沒法用

el-table裡面沒法用

希望后续可以在 el-table 里使用 infiniteScroll


[Bug]: adding clip to element.screenshot creates invalid outputs

Bug description
Greetings folks! I am attempting to screenshot an element with its margin, not the default clip settings.
Unfortunately, I am getting some odd behavior when I try to set the clip setting of screenshot.
I would have expected setting clip to bbox (in the screenshot below) to be a no-op:

Instead, the screenshots output are in many cases empty:

If I comment the line that says clip: bbox, I get the expected behavior -- although, if I comment this line, I don't know of another way to configure the screenshot clipping behavior to use the element margins.
I appreciate any help! Is this a bug? am I calling the API incorrectly? Is any more information required to properly diagnose the situation?  Thanks!!
Puppeteer version
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Node.js version
v18.7.0
npm version
8.18.0
What operating system are you seeing the problem on?
macOS
Relevant log output
No response

This way works.. the only issue is that I don't yet know how to screenshot elements with margins

Could you provide a sample script?

This can probably be merged with #8833 because it is roughly the same problem


Crashing whenever I try to watch a friend streaming

It closes out the app and cuts me from call, I relaunch and it says that Better Discord caused a crash and to try repairing and disabling plugins. I did all this, it still crashes.

Issues regarding the client should be directed to => https://github.com/rauenzi/betterdiscordapp.
Also:


Feature request: extract hour/minute data for publish_date

Right now, an article's publish_date returns a datetime object with a month, day, and year.
It would be great if it could also try to extract an hour (or even minute!) from the article source.

Would also be great if we could have timezone data.


Likert Component

Description
Hey! I Have a new component I hope can be included for our use in Elevundersøkelsen at UDIR. This component fits our needs and should be functional for others to use. It requires a list in the datamodel and is linked in the new dataModelBinding type for the likert.
I have spoken with @Febakke about the design and functionality.
PR to support pdf generation: https://github.com/Altinn/altinn-studio/pull/8441
Likert component desktop
You should be able to use keyboard navigation in the table. The table uses auto-layout provided by the browser.

Likert component mobile
Used mediaQuery: max-width:992px. In mobile view the component is rendered as Accordians. Every accordian is opend and can be closed after selection.

Layout.json
Layout file in your alltinn studio app:
{
        "id": "likert",
        "required": false,
        "optionsId": "frequency",
        "type": "Likert",
        "textResourceBindings": {
          "title": "layoutSchoolWork"
        },
        "dataModelBindings": {
          "likert": {
            "list": "Questions",
            "question": "Id",
            "answer": "Answer",
            "start": "1",
            "end": "4"
          }
        }
}

id*: unique id
required: true or false (All questions will be included in the required)
optionsId*: links to an options file, just like radiobutton component.
textResourceBinding.title*: Title displayed above table/ accordians
dataModelBindings.likert.list*: link to datamodel field (must be a list)
dataModelBindings.likert.question*: link to datamodel field for the question (can be id in text resource file)
dataModelBindings.likert.answer*: link to datamodel field for where the answere is stored. The anwer is the value of the options defined in optionsId
dataModelBindings.likert.start: (optional) Used to slice the array of questions (inclusive), if not provided we start from index 0
dataModelBindings.likert.end:  (optional) Used to slice the array of questions (exclusive), if not provided we end with length of likert list

In the example above our datamodel looks something like this:
Questions: [
   {Id: "This question will be filtered out", Answer: ""},
   {Id: "qSchoolWorkHomeWork", Answer: "1"},
   {Id: "qSchoolWorkCalculator", Answer: "7"},
   {Id: "You can include text directly her", Answer: "7"},
   {Id: "This question will be filtered out", Answer: "7"},
   {Id: "This question will be filtered out", Answer: "7"}
]

Here qSchoolWorkHomeWork, qSchoolWorkCalculator id's to the resource text file.
Verification

[ ] All tests run except one snapshot test with repeating group localy. This one also failes on main branch.
[ ] Manual testing done (required)
[ ] Relevant automated test added (if you find this hard, leave it and we'll help out)
[ ] All tests run green

Documentation

[ ] User documentation is updated with a separate linked PR in altinn-studio-docs. Dette skal jeg begynne på.
[ ] Changelog is updated with a separate linked PR

[ ] altinn-app-frontend- Har ikke gjort dette.
[ ] nuget-packages - Ikke relevant?

A few extra TODOs:

[ ] Update https://github.com/Altinn/altinn-cdn/blob/master/schemas/json/layout/layout.schema.v1.json
[ ] Support for configuration in Altinn Studio.

A few extra TODOs:

[ ]  Update https://github.com/Altinn/altinn-cdn/blob/master/schemas/json/layout/layout.schema.v1.json
[ ]  Support for configuration in Altinn Studio.

https://github.com/Altinn/altinn-cdn/pull/95

A few extra TODOs:

[ ]  Update https://github.com/Altinn/altinn-cdn/blob/master/schemas/json/layout/layout.schema.v1.json
[ ]  Support for configuration in Altinn Studio.

Is this something you guys can help out with? Support for configuration in Altinn Studio

Hi @lasseklovstad!
Thanks for this contribution! We have added reviewing this PR to our current sprint (I saw that @lorang92 mentioned this in a Slack thread earlier today), and will do our best to get back to you as soon as possible. The changes in this PR address some new concepts that we have not supported before - as such we will need some time to review it and determine how to best get this component into our code base 😄
We will get in touch if we need some more info or input from you!
Regarding support for configuration in Studio, I see that we are lacking documentation for this. Might want to hold off on that while we review this PR, in case there are any changes here that would affect that implementation. I have created an issue to update the docs with instructions, will try to get it prioritized. Otherwise you can message us on Slack when you're ready to start and we can guide you through it.

@lasseklovstad What does the data model set up look like in the xsd/JSONSchema data model? Do you have an example app in f.ex. Altinn Studio that I can look at?

@lasseklovstad What does the data model set up look like in the xsd/JSONSchema data model? Do you have an example app in f.ex. Altinn Studio that I can look at?

@nkylstad I have an example here: https://altinn.studio/repos/udir/elevundersokelsen/src/branch/REU-466-Likert-oppsett
The questions is populated into the model in the instantiationhandler: https://altinn.studio/repos/udir/elevundersokelsen/src/branch/REU-466-Likert-oppsett/App/logic/InstantiationHandler.cs
and the Likert json config is seen here: https://altinn.studio/repos/udir/elevundersokelsen/src/branch/REU-466-Likert-oppsett/App/ui/student-survey/layouts/school-work.json
if you want to run this app localy you need to add custom claims to the altin platform described in this PR: https://github.com/Altinn/altinn-studio/pull/8434

@lasseklovstad What does the data model set up look like in the xsd/JSONSchema data model? Do you have an example app in f.ex. Altinn Studio that I can look at?

@nkylstad I pushed a change in the altinn so that you can run it without the claims locally for testing. https://altinn.studio/repos/udir/elevundersokelsen/src/branch/REU-466-Likert-oppsett

@nkylstad
Sounds good!


Add a user mapping to Auth0 properties for username, email and roles in Sitecore

Enhance the existing user mapping to Auth0 properties and add the username, email and roles in Sitecore.

@kate-orlova I added mapping of additional profile properties and roles.


update and share tasks

Diego:

docs/tutorials/htc_init.md: initialize the htcondor env on laptop or lxplus
docs/tutorials/htc_job.md: submit your first job
docs/dev/htc.md: how to map a new user in htcondor

Daniele:

docs/dev/iam.md: how to enable new users via IAM

Mirco:

docs/tutorials/dask_init.md: how to init and manage a dask cluster
 docs/tutorials/dask_scripting.md: how to produce a script that scale out to dask

Tommaso:

docs/tutorials/dask_interactive.md: how to use dask interactively
docs/tutorials/aaa_access.md (not existing yet --> to be created): how to access data on AAA

Introduction part --> Daniele

in intro:

howto resources allocation (short and long term)
distributed vs local


Send Firmware on USB running HID Payload

So, after finally finding a USB with 2303, I followed demo 1 which worked great (didn't even need to short any pins).
So it works great with the Rubber Ducky payload, but now apparently all the PCs I am using don't recognize the device as a USB device (appears to be a keyboard according to device manager). I plug in the USB, the script runs, and a "Removable Disk (F:)" option appears, though double clicking on it just gives the "Please insert a disk into Removable Disk (F:)" error. Attempting to use GetInfo with DriveCom.exe results in a "System.InvalidOperationException: DeviceIoControl failed: 0079" error.
Before I take it apart and try to short the pins (if that would even help), just wanted to check to see if anyone else ran into this. And just to check, if I do have to short the pins, are the two pins to short the left-most pins the arrow points to in this pic: https://github.com/adamcaudill/Psychson/blob/master/docs/PinsToShortUponPlugInForBootMode.jpg

That is normal. If u short the Pins error 79 should be gone. It is Pin 2 and 3 in the Picture. Not Pin 1 and 2!

Thank you very much! Glad I asked about the pins first :)
That worked great to solve the problem, thanks again!


List.map2 unexpected behavior

Maybe this is intentional but:
-- haskell
[5,6,6,7,7,8] = (+) <$> [1,2,3] <*> [4,5]

-- elm
[5, 7] = List.map2 (+) [1,2,3] [4,5]

obviously [5,6,6,7,7,8] /= [5,7], why? Is there a utility function to provide the traditional lift behavior?

As to why:

The Applicative instance for standard lists in Haskell is this.
But there's also an Applicative instance for so-called ZipLists, here.
Of the two, Elm chooses the ZipList version (because, I think, it's the one that is analogous to the Applicative instance for Signal).

Continuing your example, in Haskell you would have:
ZipList [5,7] = (+) <$> ZipList [1,2,3] <*> ZipList [4,5]

I think this library does what you want.
The idea is that the "exploring all possibilities" version of things is way less common in practice. I have still not used lists that way in a real life Haskell program after like 5+ years.

Hmm, I thought the definition of Lists as a Applicative Functor needed to consistent with List as a Monad.
Doesn't this break that? It may be more practical in practice, but it feels unsound (I'm not actually a math guy). NDet also doesn't seem like the appropriate place for this, as the result should be deterministic. Believe it or not, I use this functionality somewhat regularly. Maybe it should be added to List.Extra?

Maybe talk to the List.Extra folks. There are some discussions on the list about how the applicative laws are not followed exactly with how it works here. I think both sides of this are explained there if you can find it.
Not looking to change this really. The fact that something can be seen as an Applicative Functor does not necessarily mean that's the best API.

Fair enough. I submitted a PR to List.Exta. We will see what they say. Overall I've enjoyed how elm tends to fall on the side of good api vs math when those are in conflict (Error over Either ect). But I feel like the true math thingies still need a home.
https://github.com/circuithub/elm-list-extra/pull/12

@Fresheyeball, saying "Lists as a Applicative Functor needed to consistent with List as a Monad" isn't very relevant when there is no Monad instance for Lists (in Elm). Also, as observed already in the original "Applicative Functors" paper, a type constructor (like List) can have more than one useful Applicative Functor instance. I think they even use the above example with the two different ways of making lists Applicative in Haskell:
[5,6,6,7,7,8] = (+) <$> [1,2,3] <*> [4,5]
ZipList [5,7] = (+) <$> ZipList [1,2,3] <*> ZipList [4,5]

Only one of the two (the first) has a corresponding Monad instance. Because none can exist for the second. That doesn't mean the second one is not a useful Applicative instance. There is also nothing unsound about it. It satisfies all the laws expected of Applicatives. (I don't understand Evan's comment about "how the applicative laws are not followed exactly with how it works here". I think they are followed just fine.)
About NDet and determinism, yes, of course the resulting list is a deterministic value. But it models nondetderminism. After all, the "List as a Monad" you mention is typically called the nondeterminism monad.

@jvoigtlaender fascinating! That was all news to me, like I said, I'm not a math guy. So... it sounds like both of the examples you provided are useful and valid Applicative instances, and I was more just accustomed to the first one because I think of lists as Monads and mentally work backward to Applicative.
If this was a system with type-classes where there is an Applicative class and a Monad class, I expect them to align, making the ZipList version a newtype. But this is Elm, and it seems fair that the ZipList version is more useful in practice. It all seems good to me. @circuithub already merged my PR with the other instance.
If you are willing to humor me. Why is the List Monad called the nondeterminism monad when the values produced are deterministic?

About "list monad = nondeterminism monad" (in classic math papers, it would probably be "set monad = nondeterminism monad", but most functional programmers make do with lists): All the answers here seem good to me. Also one of Wadler's first monad papers (for functional programmers) contains such a discussion. (It discusses a series of extensions of a base interpreter for a simple language. When it comes to realizing a nondeterministic language feature, the natural monad to choose is the list monad.) A precursor to this, before the general concept of monads was introduced into FP, was his paper "How to Replace Failure by a List of Successes" (easy to find online), which uses lists for modelling backtracking (= nondeterministic algorithms), but uses just list comprehensions instead of a monadic API.


Demo isn't working at the moment

Hi,
I was was looking for a similar solution for combining calendar feeds (but for a privately share link, and not a public calendar), and I noticed your demo link isn't working at the moment.

Cheers,
Noa
P.S. Is there a way to use your gem without hosting the resulting calendar publicly?

 It looks like Meetup have just deprecated API keys in favour of OAuth 2, which is why this broke. It might take some time to fix this.
In the meantime, other calendar integrations (Google Calendar, iCal) should work fine.
Yes, you can use the gem without hosting the calendar publicly. How did you want to run it?


Fix incorrect work with double-quoted substrings.

Their content was not ignored. Original function works correctly.
// correct
dateFormat('2017-06-16', "'yyyy'") // yyyy

// wrong
dateFormat('2017-06-16', '"yyyy"') // "2017"

Ah, that's why it didnt work! Thank you :) 👍

We just ran into this issue in our project using a custom mask as well, it would be great if this could be accepted as it solves the problem. @felixge

I'm not maintaining this project anymore and have notifications turned off by default. If one of you wants to help in the future, and e.g. cut a npm release for this, please let me know your GH+NPM usernames so I can give you access.

@felixge I'm happy to help. I'm doowb on both GitHub and NPM.

@doowb I added you on GH/NPM. Feel free to cut a new release for this change. Thanks a ton :)

Thanks! Published as 3.0.3.


Accessibility help doesn't show when message in chat editor is focused

Repro:

Chat: Open Session in Editor
Click the intro message
Alt+f1, :bug: nothing happens
Click the textbox
Alt+f1, the help shows

The original issue of Alt+F1 not showing when the intro message is focused still repros for me.

Yes, I actually misread the issue and fixed the bug where the accessible view wouldn't open, but not the one where accessibility help does not when this is focused.

The context key is false when I click the intro message.


💲[Native Checkout] RewardCardContainerView snapshots and view model bindings

📲 What

Adds the view model outputs for binding the reward card UI elements.
Incorporates the state type introduced in #764 and adds functions to determine the state of discrete UI elements.

🤔 Why
Rewards can be in many different states based on:

whether or not the project is live.
if the user has backed the project.
if their payment method has errored.
the availability of the reward.
the position of the 43rd moon of Saturn.

🛠 How
I found that it was easier to determine that all the states had been covered by recording snapshot tests with all of the combinations, I will add view model tests in a subsequent PR and link it back here.
👀 See
Examples of just some of the states (see 45 recorded snapshots for all of them):

Live, Non-backed, available, timebased
Live, backed
Live, backed, errored
Live, no longer available
Live, backed different reward

♿ Accessibility

[ ] Tap targets use minimum of 44x44 pts dimensions
[ ] Works with VoiceOver
[ ] Supports Dynamic Type

✅ Acceptance criteria
Given that there are just so many combinations of states (approx 45 if I have it correct), I think looking through the snapshots, the naming of the snapshot tests, carefully inspecting the properties set on the templates and confirming that the state in the snapshot makes sense, it should be fairly sufficient as AC. Of course run it on device and look out for strangeness but I'm not sure what else to suggest for full QA test coverage other than going through each of the combinations.
⏰ TODO

[ ] Merge in correct styles once that sweep is completed.
[ ] Add VM tests (separate PR).

 Reward States


Looking forward to release soon!

Fantastic work! Looking forward to release soon!

Does the team have a plan for when the code will be released?

Yes. The code is under preparing and will be released soon. Stay tuned!

Hope you can publish a todo list as soon as possible. It's a attractive job.
Looking forward to release soon!

I was impressed with your work on "Lite DETR : An Interleaved Multi-Scale Encoder for Efficient DETR
" and would like to express my appreciation for your contributions.
I'm wondering if you have any plans to release the source code of this project on GitHub or any other platform. I believe many people in the community would benefit from being able to learn from and build upon your work.

Thanks for your interest. The code will be available this month.


bugfix:处理业务id筛选条件不生效的问题

Codecov Report

Merging #489 (c40a878) into v2.6.x_develop (2d79953) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@               Coverage Diff               @@
##           v2.6.x_develop     #489   +/-   ##
===============================================
  Coverage           62.67%   62.68%
===============================================
  Files                 441      441
  Lines               27261    27262    +1
===============================================
+ Hits                17087    17088    +1
  Misses              10174    10174

Impacted Files
Coverage Δ

itsm/ticket/managers.py
41.37% <ø> (ø)

itsm/ticket/serializers/ticket.py
70.45% <100.00%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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


Update changelog

Coverage increased (+0.02%) to 98.612% when pulling dd7493275f96478acff79dcdf1bed36b21de3a77 on release-3.5.4 into 0c30a24bf8bfbfebfc591840243ffd01105bb916 on master.

need to redo this for the next release anyway, closing


Is there any way of passing HTML code into the value prop?

Hello!
First off i'd like to say that this library have saved me from trashing a project that I've been working on, so thank you for sharing!
I have a question however, and that is, is there any way of passing HTML tags or perhaps another component that can parse the HTML onto the value parameter?
Thank you in advance!

Hey @sandmountain unfortunately it's not on the scope of the project and there are some good limitations on iOS for it.
If you wanna put some effort and create a PR with an alternative you're mostly welcomed!
Thanks


[FEATURE] Accessibility - Add unique titles to frames

Expected Behavior
Frames must have unique title attribute
https://dequeuniversity.com/rules/axe/1.1/frame-title
Current Behavior
<iframe class="chartjs-hidden-iframe" tabindex="-1" style="display: block; overflow: hidden; border: 0px; margin: 0px; top: 0px; left: 0px; bottom: 0px; right: 0px; height: 100%; width: 100%; position: absolute; pointer-events: none; z-index: -1;">

Possible Solution
<iframe title="Unique title goes here" class="chartjs-hidden-iframe" tabindex="-1" style="display: block; overflow: hidden; border: 0px; margin: 0px; top: 0px; left: 0px; bottom: 0px; right: 0px; height: 100%; width: 100%; position: absolute; pointer-events: none; z-index: -1;">

I'm new to contributing to this project but I've been looking at this issue and I was thinking we could use the uid of each chart to create this unique title. One way to do this would be to modify createResizer() to accept chart id as the second argument. So we would have to change this:
    function createResizer(handler) {
	    var iframe = document.createElement('iframe');
            iframe.className = 'chartjs-hidden-iframe';

to something like:
    function createResizer(handler, chartId) {
	    var iframe = document.createElement('iframe');
	    iframe.title = 'Resizer Frame for Chart ' + chartId;
	    iframe.className = 'chartjs-hidden-iframe';

Also, inside addResizeListener, we would have to change the call to createResizer:
function addResizeListener(node, listener, chart){
   // ....
   stub.resizer = createResizer(notify, chart.id);

Any thoughts? I'm very new to this project  so forgive me if I'm missing something major in here.

@devjeetr I don't think the resizer should be bound to the chart id since it will soon be possible to share the same resizer between multiple charts. Instead, I would keep it simple and set a generic (and short) title (e.g. title="chartjs-iframe"). Anyway, this iframe is going to be replaced by divs hopefully soon.

@frankspin89 @devjeetr starting #4596, we don't use IFRAME anymore


drg whoami endpoints igores output format

It looks like the drg whoami endpoints commands ignores -o json:
$ drg whoami endpoints -o json
NAME                        URL
api                         http://localhost:8011
console                     http://localhost:8010
coap                        coap://localhost:5683
http                        http://localhost:8088
mqtt                        localhost:1883
mqtt_ws                     http://localhost:20880
mqtt_ws_browser             http://localhost:21880
mqtt_integration            localhost:18883
mqtt_integration_ws         http://localhost:10443
mqtt_integration_ws_browser http://localhost:11443
websocket_integration       ws://localhost:10002
sso                         http://localhost:8080
issuer_url                  http://localhost:8080/realms/master
redirect_url                http://localhost:8010
registry                    http://localhost:10004
command_url                 http://localhost:10003
kafka_bootstrap_servers     localhost:9092

I know, it's tracked here : https://github.com/drogue-iot/drg/issues/107

Sorry, I didn't check.


feature: improved url parsing to determine owner and repo of PR

Feature idea:
There's a good base in bin/metadata.js:parsePRId (lines 72 -78), but I think we could do more and directly parse the url for owner and repo, without removing actual options.
Usage would then be :
get-metadata <id-or-url> [<owner> <repo>]
If called with url: id, owner and repo would be extracted from it
If called with integer id: owner and repo would have to be given as args or else would default to nodejs and node respectively.
Todo:

[ ] When first arg is url, extract owner, repo, and pr-id from it
When first arg is integer:

[ ] Check second arg for owner and third arg for repo if given
[ ] Default owner to nodejs and repo to node if not
[ ] Allow args to be given in any other order when named? (--repo=node --owner=nodejs)

Feel free to add things!

Following discussion in #30 I'm starting a test file for functional cli testing.
It will live in tests/functional/index.js and will cover the functionalities described in the checkboxes.
in bdd-style specs:
get-metadata should:

[ ] throw when called without arguments/with non-url string argument
When given numeric first argument :

[ ] get PR from nodejs/node if no other arguments
[ ] get PR from nodejs as owner if second string argument is given
[ ] get PR from owner given as second argument and repo given as third argument
[ ] get PR from owner given as -o/--owner flag argument and repo given as -r/--repo flag argument

[ ] get PR from url when given as only argument by extracting owner, repo and PR id
[ ] throw if given url as first argument and other args are given

@joyeecheung is that ok for you?

@Tiriel SGTM, although I think you can just put it under test/intergration? Also if we don't mock the authentication part then it would be a bit harder to put it on CI.

No problem, I'll put it in test/integration!
As for the mocking part, do you think it possible to use env vars to create a temporary .ncurc file with auth informations? I know secured env vars can be defined in Travis CI, I just don't know about the mocking file part...

@Tiriel An easier way to test the CLI would be to export a function that use yargs to parse a string if given, or process.argv otherwise, and returns an object with all the options that we want. That way you will only need to test stuff like assert.deepStrictEqual(parseArgs('-o=sth -r=sth'), {owner: 'sth', 'repo': 'sth'}) and test for errors and stdout (maybe need to fork another process to test erroneous inputs). Also in that case you can put it in test/unit since it does not actually fire any requests.
You can pass a string to yargs to get it parse that instead of process.argv( take a look at their tests)
Also I am thinking about refactoring the binary file a bit so we can put all data in one object and stub methods for tests.
// parseArgs parse string with yargs if given, or process.argv if not
var args = parseArgs();
// Stub methods e.g. data.getReviews,  that returns fixtures wrapped in promises
run(args, data, logger, analyzers);
// Check if stubs are properly called, loggers have proper logs.

Okay, I think I see what you mean. More like unit-testing only the args processing part than the actual calls, since we already know they work and are tested elsewhere?
As for the bin refactoring it does seem good to me, but I think I'll stay on the url parsing + testing for this issue/PR and leave to another one, I feel I already have to much changes in one PR. Would that be ok to you?

I think we can close this now that https://github.com/joyeecheung/node-core-utils/pull/30 has landed. Thanks!


Polygon, Geometry and Feature get the following error

..\data\node_modules\mongoose\lib\schema\array.js:58
this.caster = new caster(null, castOptions);
^
TypeError: string is not a function
at new SchemaArray (\data\node_modules\mongoose\lib\schema\array.js:58:19)
at Function.Schema.interpretAsType (..\data\node_modules\mongoose\lib\schema.js:350:12)
at Schema.path (..\data\node_modules\mongoose\lib\schema.js:305:29)
at Schema.add (..\data\node_modules\mongoose\lib\schema.js:217:12)
at Schema.add (..\data\node_modules\mongoose\lib\schema.js:212:14)
at new Schema (..\data\node_modules\mongoose\lib\schema.js:73:10)
at Mongoose.Schema (..\data\node_modules\mongoose\lib\schema.js:53:12)
at Object.

@markstos mongoose 4.0.3, mongodb 2.6.9...still experiencing this issue.  The fix to allow validation would to use the Schema.Types from mongoose, which would require adding that dependency.  Without, we have to use an empty array, which falls back on a Mixed type.  Will you accept a pull request that essentially does what @heatmonkey proposed, or do you have another fix for this issue?

@mmacmillan I don't mind adding a dependency, if we can fix this and still have validation.
I don't have an alternate fix for this.

This should be fixed by the 1.0.0 release, thanks to @joshkopecek
Notice the syntax is slightly different, so it's not a drop-in upgrade.
Re-open if you still see an issue with the 1.0 release.


Next release availability question

I was experiencing the issue that was resolved in https://github.com/angular-ui/ui-slider/pull/78.  What kind of time frame can be expected until the next release so that I can bring in the fix?

https://github.com/angular-ui/ui-slider/releases/tag/v0.1.2


Null Safety

Is your feature request related to a problem? Please describe.
I would like to use flutter_riverpod with null safety on the beta channel.
Describe the solution you'd like
Create a prerelease version of flutter_riverpod by migrating to null safety
Describe alternatives you've considered
I haven't really considered other alternatives.
Additional context
None

There's already a null-safety version of flutter_riverpod published: 0.13.0-nullsafety.1


Creating a report field with the same name in lowercase will replace the report field name that is in uppercase.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.33-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @jayeshmangwani
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1726145655221189
Action Performed:

Open App Go to Settings
Click on Workspaces -> Select any workspace
Go to More Features -> Enable Report Fields
Go to Report Fields
Add a new field named 'abc' (lowercase) and select any Type
Add a new field named 'ABC' (uppercase) and select any Type
Notice that the older field named 'abc' is replaced by 'ABC'.

Expected Result:
Either the field names should be created separately, or we should prevent creating the same field name in different cases
Actual Result:
An uppercase field name (ABC) will be replaced by the corresponding lowercase field name (abc)
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/e9163947-6180-45b2-af3b-1437f1d619ec
https://github.com/user-attachments/assets/7fe6bdb4-ca70-4209-a534-ac4c9d851864
Add any screenshot/video evidence

View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.

Creating a report field with the same name in lowercase will replace the report field name that is in uppercase.

What is the root cause of that problem?

When generating fieldID and fieldKey for Onyx Data here  we make use of generateFieldID
https://github.com/Expensify/App/blob/ef6a64c2f5a193babdb2f14a172aea4748502033/src/libs/WorkspaceReportFieldUtils.ts#L66-L68
And generateFieldID capitalize the name so fieldKey generated for Abc and ABC will be equivalent, hence replaces the old key on onyx merge.

What changes do you think we should make in order to solve the problem?

Change validation case such that user can’t create a report field when similar key exist in different case.
To do so, when validating for existing value - compare existing values with new value in UpperCase .

  } else if (Object.values(policy?.fieldList ?? {}).some((reportField) => reportField.name.toUpperCase() === name.toUpperCase())) {

https://github.com/Expensify/App/blob/ef6a64c2f5a193babdb2f14a172aea4748502033/src/pages/workspace/reportFields/CreateReportFieldsPage.tsx#L69
What alternative solutions did you explore? (Optional)

Alternatively we could remove toUpperCase() from generateFieldID
https://github.com/Expensify/App/blob/ef6a64c2f5a193babdb2f14a172aea4748502033/src/libs/WorkspaceReportFieldUtils.ts#L66-L68
So now both ABC and Abc will generate different fieldKey and would not be merged together on Onyx Merge event.
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

Proposal
Updated added additional changes required for alternate solution.

I think this is expected behaviour as the report field names are essentially the same. I can't really think of a use-case where customers would need the same report field name but in lower-case and upper-case.
Let me get some input on this

Then we should extend the validation to warn the user about this so they do not accidentally replace their old field. See proposal

I don't think we need to do anything for this at the moment, I'm going to close it out.


Sema: Progress towards an improved "too complex" check

The expression timer is currently set to 10 minutes, so in practice 'too complex' expressions are caught by the solver memory or scope threshold. Since llvm::TimeRecord class collects a lot of information, we spend a lot of CPU time just querying system calls.
I want to get rid of the timer entirely, and possibly turn off the scope threshold by default too. To do that, I'm first introducing some counters for trail steps. Like counting solver scopes, this is a measure of work done by the solver, but it is more fine-grained, and should more closely correlate with wall time.
Also I made it so that passing -Xfrontend -solver-expression-time-threshold=0 now disables the timer, however the trail check doesn't quite replicate the behaviors of the existing timer with conjunctions and closures, so it's not quite ready to be turned off by default yet.
This will address rdar://109613871 once the timer is turned off by default.

@swift-ci Please test source compatibility

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please test source compatibility


Remove unsed local variable from NodePrinter

local bool variable isSerialized in NodePrinter is unused from source.

@swift-ci Please smoke test

@swift-ci Please test

Hi @rollmind, thanks for the PR. New contributors don't have CI privileges, so that won't work.
@swift-ci smoke test and merge

@varungandhi-apple thank you :)

Not sure why the PR testing failed earlier, but looks like this code has already changed and this local variable is no longer present. Closing the PR.


Lightning strike's projectile damage with multistrike is mistaken

As the title says, when you link multistrike to lightning strike, the projectile atts doesnt go up, even tho it directly depends on the melee atts, so it should (the problem is clearly that multistrike is tagged as 'melee' and PoB then ignores it when looking at the projectiles). I belive there are a few other interactions that work incorrectly with lightning strike as well.
Thank you very much, (love your software btw).
Nicolas.

As noted in #241, the attack speed calculation for projectile parts of melee skills has never been correct, due to limitations in the design of the skill part system. However, the recent bug fix to Multistrike has exaggerated the problem somewhat, and overhauling the skill part system to fix the issue is now a high priority. Unfortunately though, the overhaul is likely to take a fair bit of work, and it may be a while before I can get around to it.


"Unsupported keyword argument dir"-error when calling notebook(dir="/some/path")

Hi guys,
on a fresh 0.5 RC4 install with IJulia 1.2.0, I get an error message when trying to open the notebook in a different directory via notebook(dir="/some/path") (as described in the readme, actual path replaced), while it works fine when opening a notebook in the home directory without passing on a path.
The error message reads:
julia> notebook(dir="/some/path")
ERROR: MethodError: no method matching notebook(; dir="/some/path")
Closest candidates are:
  notebook(; detached) at /Users/[removed]/.julia/v0.5/IJulia/src/IJulia.jl:192 got unsupported keyword argument "dir"
 in (::IJulia.#kw##notebook)(::Array{Any,1}, ::IJulia.#notebook) at ./<missing>:0

My system information:

Julia Version 0.5.0-rc4+0
Commit 9c76c3e* (2016-09-09 01:43 UTC)
Platform Info:
System: Darwin (x86_64-apple-darwin15.6.0)
CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
WORD_SIZE: 64
BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Haswell)
LAPACK: libopenblas64_
LIBM: libopenlibm
LLVM: libLLVM-3.7.1 (ORCJIT, broadwell)

Sorry, I just realized I hadn't tagged a new version of IJulia in a while.  It works now in IJulia master, and if you wait a day or so it will work after you do Pkg.update().


how to compile complex folders

https://github.com/gkz/LiveScript/blob/master/Makefile#L16
like:
src/
    lib/
       xxx.js # files and sub folders
    models/
    routers/

@willin, lsc by itself is one file in, one file out. Handling multiple files is up to some other tool—in the line you linked, it's make that is running lsc for each file in src. Adapting the Makefile to handle deeper folder structures is (A) not difficult and (B) a make question, not a LiveScript question.


Allow active effects on items to use the @item variable in change values

I was going to file this for core Foundry but since it's the system that adds @item to the roll data I filed it here.
With the new active effect transferral mode, the active effect exists on the item but is applied to the actor. Could we use the item's getRollData so we'd have access to the @item variable? There are some people on the Discord server that use one of the 3 resources to track a value that then gets used by an active effect. For example, in Van Richten's Guide to Ravenloft, there's a Stress mechanic that gives a penalty to d20 rolls. With a resource, it'd be easy to reference that value in an active effect but with them being deprecated that makes it hard to track this. If it's an active effect on an item, it could use - @item.system.uses.value in the change values.

Probably shouldn't be added before #2965. It should be possible to get the item's roll data regardless of whether the effect is transferred since we keep track of the source effect. It'd be a problem if the source effect's item is not owned by the actor though.

Honestly there just needs to generally be a look at how Stress (which briefly showed up in the UA as a playtest version of Exhausted) can be better represented natively; I do get the idea here, but it seems very hacky for what is a lot closer to a core mechanic than not.


Bundles the Julia extracted folder instead of compressed zip

So this is a try-fix attempt to remove the need for admin permissions for the first run.

The need for first run was due to the need of extracting Julia portable zip, this PR removes the need for that by bundling the extracted folder instead of the zip.
Size different is not much because electron-builder also compresses the assets.
Extracting functionality is still there, it acts as a backup.
This PR also allows people to use custom Julia binaries by adding "CUSTOM-JULIA-PATH" key in the config file. If this is present, it takes priority over the default "JULIA-PATH".

The DEBUG_PROJECT_PATH argument sets a default project path for development purposes.


Add some JSON key instances (and swagger paramschema) for GYMintingPolicyId and GYAssetClass

Just a few simple instances I'm upstreaming from another project. It's likely that some other types are missing these specific typeclass instances (they are quite useful) but I don't have any off the top of my head right now.

@TotallyNotChase, thanks for this PR! There are some adjustments needed to be done in our CI to get this through, which I'll attempt to do for asap. Also, the current main commit of Atlas has numerous fixes which has not been released so I'll suggest to use latest commit of main for the client app.


Need a better API to create ErrorValues

Description:
$subject. Need an API to create ErrorValues https://github.com/ballerina-platform/ballerina-lang/blob/9582b76c4e6cc6042b9cd0e62e390984bc088acd/stdlib/http/src/main/java/org/ballerinalang/net/http/HttpUtil.java#L1691
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

There is already a set of APIs: https://github.com/ballerina-platform/ballerina-lang/blob/v1.1.0/bvm/ballerina-runtime/src/main/java/org/ballerinalang/jvm/BallerinaErrors.java#L75
Would that not be sufficient?

Had a chat with @arukshani, the requirement here is to provide an API to create an error value in the https://github.com/ballerina-platform/ballerina-lang/blob/v1.1.0/bvm/ballerina-runtime/src/main/java/org/ballerinalang/jvm/BallerinaValues.java class, that is capable of creating an error value, using the error type defined in a given package. Such APIs are available for records and objects, but not for other user defined types.

Further checking on this, I just realised that reason to provide an API BallerinaValues.java is because the value class implementations for objects and records are dynamic and there is no way for the BValueCreator.java class to know which class to use for value creation.
But this is not the case with other user defined types such as error and etc, where the value class is predefined. Hence we actually don't need that API, and BValueCreator.java can be used.
No matter what API is used, it will required to mention  the org name, package name and the version of the type, from which we are creating a value.


CLI crashes on addClass

I don't know much about this stuff, but it seems like an import statement is wrong. :)

oh good. Thanks, I'll take a gander


how would you preserve scroll position?

in your demo at https://trungdq88.github.io/react-router-page-transition/simple/ if i scroll and click on 11 and go back, i'm not longer looking at the same scroll position, is there a way to fix that?
(feel free to close that issue if you think this is out of scope of this lib)
thanks

When the transition ends, the previous page will be completely unmounted, therefore the DOM state (in this case scroll position) is lost.
In order to restore scroll position, you can try save the position on componentWillUnmount somewhere (like redux's state or the wrapper component's state), then restore it in componentDidMount.
So yeah, this issue is out of scope for this lib.


Implementation of transferring crypto

According to concept of new user tasks, we need a solution to transfer crypto as reward to users.

Any related API or documentation?


fix: picklist scroll

[ ] I have followed (at least) the PR section of the contributing guide.
@90milesbridge/tigger

Pull Request Test Coverage Report for Build 4302

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 80.824%

Totals

Change from base Build 4296:
0.0%

Covered Lines:
2998

Relevant Lines:
3594

💛  - Coveralls


No way to serve on localhost only

This doesnt make any sense at all. Can you please explain?

If I type serve, then my files get served to anybody on my network, whereas I want it to be only served on localhost.
There is no way to do this judging from the output from serve --help. Ideally, serve would accept an address to bind on, instead of simply binding to <IP_ADDRESS>.

Great catch, we should definitely have a flag for that! 👍
serve --local

or
serve --only-local

(I think the first one is better).
And then it only listens on localhost instead of <IP_ADDRESS>.

It might be better to accept an address to bind on, instead of arbitrarily constraining the user between a choice of <IP_ADDRESS> / localhost.
A particular machine could have more than 1 IP address for instance. You should be able to serve on once of those IPs without affecting the other.

Closed in https://github.com/zeit/serve/pull/327#pullrequestreview-99129079


Remove charts folder from `make generate

What this PR does / why we need it:
This PR removes charts folder from make generate target because it does not exist.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
/cc @RaphaelVogel
Release note:

NONE

/lgtm


Implemented IDisposable into MMDevice and added releasing of COM object to AudioEndpointVolume Dispose

Should help with #200 as the unused AudioEndpointVolume COM objects can be easily removed if the MMDevice instance is no longer being used to prevent memory leaks.

thanks, had to make an additional fix due to some dispose issues with the Volume Mixer demo, but seems OK now


Specify check severity in test scenario documentation only

Is your feature request related to a problem? Please describe.
Currently, an understanding of the expected overall behavior of a test scenario from the test scenario documentation is missing information regarding what will/should happen when a check fails.  This is important because failed checks sometimes/often serve as flow control to, for instance, stop the test scenario early or even stop the test run early.  Instead, this information is provided only in Python when check.record_failed is called.
Describe the solution you'd like
We already have the ability to specify the severity of a failed check in documentation, and that documentation information is already available programmatically.  We should migrate all check severity information into documentation and remove the ability to specify severity at runtime.  This will clarify and simplify test behavior.
Describe alternatives you've considered
We could leave maximum flexibility to specify severity in documentation or in code or override documentation in code.  While that would provide maximum developer flexibility, I am unaware of any value we would gain/retain under that approach and we would lose the clarity and simplicity that would accompany specification of check severity in documentation only.
Execution plan
The record_failed method has wide usage throughout the codebase (~260 instances) and currently severity is a required parameter.  Therefore, we will probably need to phase this change in over many PRs.  I suspect a strategy like the following would be effective:

Make severity an optional parameter to record_failed and have it default to the documented value when not specified (throwing ValueError if not specified via either means)
Remove severity parameter from record_failed calls where severity is specified in documentation
Add severity to check documentation in some subset of the codebase (probably not all at once)
Repeat steps 2-3 until all specifications of the severity parameter of record_failed have been removed
Remove the severity parameter from record_failed

When executing step 2, we should keep any eye out for any record_failed invocations that pass the now-removed participants parameter positionally, as it is possible those invocations may have been missed in #403 and #414


Decrease version range for pyarrow

You're right, a bit more room doesn't hurt. I'd like to be somewhat restrictive though as we were seeing some inconsistencies lately between versions. We could go with >=10 for example which maps to the arrow version released in gds 2.3.0. I'll also update the tox.ini

You're right, a bit more room doesn't hurt. I'd like to be somewhat restrictive though as we were seeing some inconsistencies lately between versions, also downgrading pip installations seems ok so users can always choose an earlier version of the client. We could go with >=10 for example which maps to the arrow version released in gds 2.3.0. I'll also update the tox.ini.

ah ok! pyarrow is so annoying haha. But you're right, users can use earlier version of the client. But probably there are not many reasons why they shouldn't just use the latest. Maybe if they're on a very old python version 🤔 anyway, >= 10 sounds reasonable!


Don't Catch - Out of pokeballs

Expected Behavior
Expected to catch I've poké balls and great ballls
Actual Behavior
[#] Something rustles nearby!
[#] A Wild Growlithe appeared! [CP 473] [Potential 0.76]
[x] Out of pokeballs, switching to farming mode...

Other Information
OS:  Win10
Git Commit: cb3d799b0c143ee0ad28aee9d50be7d4e13587c1

This problem is caused by line 261, 264, 267  in /pokemongo_bot/init.py.
remove '.value' on each of those lines to fix it.
Item.ITEM_POKE_BALL.value   -->   Item.ITEM_POKE_BALL

@LennertW  the problem still persists
[#] PokeBalls: 0
[#] GreatBalls: 0
[#] UltraBalls: 0

@gpires weird, seems to work for me (don't think I changed anything else):
                if item['inventory_item_data']['item']['item_id'] == Item.ITEM_POKE_BALL:
                    print('Poke Ball count: ' + str(item['inventory_item_data']['item']['count']))
                    balls_stock[1] = item['inventory_item_data']['item']['count']
                if item['inventory_item_data']['item']['item_id'] == Item.ITEM_GREAT_BALL:
                    print('Great Ball count: ' + str(item['inventory_item_data']['item']['count']))
                    balls_stock[2] = item['inventory_item_data']['item']['count']
                if item['inventory_item_data']['item']['item_id'] == Item.ITEM_ULTRA_BALL:
                    print('Ultra Ball count: ' + str(item['inventory_item_data']['item']['count']))
                    balls_stock[3] = item['inventory_item_data']['item']['count']

[#] PokeBalls: 154
[#] GreatBalls: 0
[#] UltraBalls: 0

Make sure you saved changes.
Try adding print statements to check what values are checked:
print item['inventory_item_data']['item']['item_id']
print Item.ITEM_POKE_BALL
I changed a few (unrelated) things so my code is a mess, if its not fixed I will create a pull request later today.

@LennertW  That's what I have, Can't debug the code right now. But it must be a typo or something.

please confirm if issue persists

tracking in #801


Fix links in todos

In todos there are links in [label](url) format, they are showing in raw format. Let's show only label, that should be enough.
➕ check projects, tags, groups and other todoist's features

done


fix: Make sure the optimizer calls the type's get_queryset for nested lists/connections

Fix #562

Summary by Sourcery
This pull request fixes an issue where the optimizer was not calling the type's get_queryset method for nested lists and connections. It also refactors the optimizer to use _default_manager for prefetching when prefetch_custom_queryset is enabled. Additionally, a new test is added to ensure the correct behavior.

Bug Fixes:

Ensure the optimizer calls the type's get_queryset method for nested lists and connections.

Enhancements:

Refactor the optimizer to use _default_manager for prefetching when prefetch_custom_queryset is enabled, otherwise use _base_manager.

Tests:

Add a test to verify that the optimizer calls the type's get_queryset method for nested lists and connections.

Codecov Report
Attention: Patch coverage is 75.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 88.89%. Comparing base (1023674) to head (2f85416).

Files
Patch %
Lines

strawberry_django/optimizer.py
75.00%
3 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #568   +/-   ##
=======================================
  Coverage   88.88%   88.89%
=======================================
  Files          41       41
  Lines        3545     3547    +2
=======================================
+ Hits         3151     3153    +2
  Misses        394      394

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