How to know when the Dialogs are dismissed?

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
I'm trying to integrate a new plugin and my trouble is that I need to load it until all Popups are dismissed. I want to find when this specific view is fully loaded:

In which section of the App.js is dismissed or is there any other file?
Describe the solution you'd like
I'd like to have the documentation about this change, perhaps, it can be added to the Wiki.
Describe alternatives you've considered
I tried to load it in the Index, but it didn't work as expected.
Additional context
Add any other context or screenshots about the feature request here.

Any idea? :\


This expression of GrafanaRequestsFailing  executes an error. Error executing query: multiple matches for labels: many-to-one matching must be explicit (group_left/group_right)

What happened?
There is a problem with this  expr that the alertname is GrafanaRequestsFailing in file manifests/grafana-prometheusRule.yaml

Prometheus Operator version:
quay.io/prometheus-operator/prometheus-operator:v0.57.0

Kubernetes version information:
v1.22.5

Manifests:
manifests/grafana-prometheusRule.yaml

Perhaps the expression should be as follows:
100 * sum by (namespace,handler,job) (namespace_job_handler_statuscode:grafana_http_request_duration_seconds_count:rate5m{handler!~"/api/datasources/proxy/:id.*|/api/ds/query|/api/tsdb/query", status_code=~"5.."}) / sum by (namespace,handler,job) (namespace_job_handler_statuscode:grafana_http_request_duration_seconds_count:rate5m{handler!~"/api/datasources/proxy/:id.*|/api/ds/query|/api/tsdb/query"})

I'm having the same problem on k8s 1.25. It seems that the current query can't handle a single (namespace,handler,job) combination receiving two unique 50X errors. I'm planning on creating an overlay but it seems like an easy fix to make here...

@fculpo I've been using it for five months with no problems


[Event Request] New IntegrationEvent in Table 36 "Sales Header", function CopySellToCustomerAddressFieldsFromCustomer

Hello,
please extends IntegrationEvent in Table 36 "Sales Header", function CopySellToCustomerAddressFieldsFromCustomer
            OnCopySelltoCustomerAddressFieldsFromCustomerOnBeforeAssignRespCenter(Rec, SellToCustomer, IsHandled);
            if not IsHandled then begin
                "Responsibility Center" := UserSetupMgt.GetRespCenter(0, SellToCustomer."Responsibility Center");
                OnCopySelltoCustomerAddressFieldsFromCustomerOnAfterAssignRespCenter(Rec, SellToCustomer, CurrFieldNo);
            end;
            // Start
            IsHandled := false;
            OnCopySelltoCustomerAddressFieldsFromCustomerOnBeforeUpdateLocationCode(Rec, SellToCustomer, IsHandled);
            if not IsHandled then
                // Stop
                UpdateLocationCode(SellToCustomer."Location Code");
        end;

        OnAfterCopySellToCustomerAddressFieldsFromCustomer(Rec, SellToCustomer, CurrFieldNo, SkipBillToContact, SkipSellToContact);
    end;

    [IntegrationEvent(false, false)]
    local procedure OnCopySelltoCustomerAddressFieldsFromCustomerOnBeforeUpdateLocationCode(var SalesHeader: Record "Sales Header"; var SellToCustomer: Record Customer; var IsHandled: Boolean)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10874.


Add the option to instantiate the same rule more than once

This is a feature that we want to have for detekt 2.0
Needed changes
There are multiple changes that should be made to make this possible. Here a list with all the changes that we need:

RuleSets shouldn't instantiate the rules. They should provider factories to pass a confguration to create that rule.

State: #6733

Rules shouldn't pick their own configuration from its parent configuration. We should provide their configuration directly.

State: #6767

The Rule id can't be hardcoded. If a rule can have multiple instances the id should change between those instances.

State: No started

The Config class should provide an API to read all the subconfigurations inside it.

State: Started but we have too many implementations of Config so it will take a while to implement it for all of them and their tests.

The core should read the Config and instantiate the rules from there.

State: This should be the easiest. We need to align on the new yaml key to find the rule but the change should be as easy as this:

.flatMap { (ruleSet, ruleSetConfig) ->
    ruleSetConfig.subconfigs
        .map { (configId, config) ->
            val ruleId = config.valueOrNull("rule") ?: configId
            val ruleProvider = checkNotNull(ruleSet.rules[ruleId]) {
                "Unknown rule ${ruleSet.id}:$ruleId"
            }
            ruleProvider.invoke(config)
        }
}

This is a huge change. There is code that assumes that the rules have a hardcoded id or that the there is only one instance of each. And this is a breaking change, we need to change the API for 3 main classes/interfaces: RuleSet, Rule and Config. This will impact every single third party rule out there.
Also, those are the big "chunks" that should be done, then a lot of minor changes should be made on the way to be able to make those possible.

You are correct, that's exactly the use case. Could I ask you how do you imagine the configuration should look like to make your use case work?

I need to write down all my thoughts about Rule/Issue/Finding and all that part of the detekt API:
We need to talk about rule ids. Right now it's easy! Every Rule has an Issue. The Issue stores the id and the description of the Rule. And Rule.id is just syntax sugar for Rule.issue.id.
That works when you only have one instance per rule. But once you have multiple instance of the same rule the thing gets messy really quick.
First of all the rules need 2 ids:

One to identify the type of the rule (needed to link for its documentation, for example)
One to identify the instance of the rule (as a user I want to know which configuration of the rule raised that issue)

The first one can be hardcode. It can even be the simpleName or the fullQualifiedName of the Rule. But the second is way trickier. First of all, that id should come from Config (aka yaml). And how are we going to expose those different ids?
Issue is a nice API. It's used in two different places: the Rule and the Finding. Issue is like a "RuleInfo" class. It is an elegant way to tell the Finding who created it but without having a reference to a Rule.
So, if we need two different ids for a rule both should be inside Issue.
An issue right now is:
class Issue(
    val id: String,
    val description: String,
)

I would propouse:
class Issue(
    val id: String,
    val ruleId: String,
    val description: String,
)

Where instanceId, in general, would be the same as ruleId. It will change only when we define a different id.
So, how would this look like on the yaml?
style:
  ForbiddenJavaIoFile:
    active: true
    rule: ForbiddenImport
    ignoreAnnotated:
      - "JavaIoFileIsOk"
    imports:
      - value: "java.io.File"
        reason: 'case-sensitivity issues'
  ForbiddenImport:
    active: true
    imports:
      - value: "some.unrelated.import"
        reason: "some other reason"

A configuration like that will create this two instances like this:
listOf(
  ForbiddenImport(
    Issue(id = "ForbiddenJavaIoFile", ruleId = "ForbiddenImport", ...),
    ...
  ),
  ForbiddenImport(
    Issue(id = "ForbiddenImport", ruleId = "ForbiddenImport", ...),
    ...
  ),
)

Also I would vote to use value class for the ids to have better type safety. If we have 2 different ids it will be difficult to know which oen use.

Sounds good. I like the proposal.

I have to admit, I don't know if there is already a built-in feature in YAML that would solve this issue. If there is not though, maybe we would want to provide our own "templates" or other inheritance mechanism in the configuration files.

There is the concept of anchors that you might be able to use.

My proposal about implement config in case user need a the rule twice or more time. We add special char for separate rule name and the rule id.
style:
  MaxLineLength:
    maxLineLength: 100
  MaxLineLength%some_id:
    maxLineLength: 100

On parsing stage we can check the key for contains % and split the string to rule name. Then add two rule to ruleset.

MaxLineLenght()
MaxLineLenght(id = some_id)

I use a % as spec char.
Is the proposal have any sence ?

It does have sense. I like it! I would say that : is a good candidate MaxLineLength:some_id
style:
  MaxLineLength:
    maxLineLength: 100
  MaxLineLength:some_id:
    maxLineLength: 100

The only problem with that is that yaml uses : a lot already so I don't know if it is a good idea or not.
Other char options: ;, /, |, =, , and -.

I suggest a + as special char. The + is already using as splitter for alias in email naming convention. Also, the plus symbol clearly indicates an addition/extension.
Email Sub-addressing

I don't agree with the @ special character, this character is used in so many programs for communication as a special character, (slack, discord, github, mail...)
This will be inconvenient for people when communicating about their detekt rules. Each time you type the @ some program suggest a popup.

Ok, I think we need other options in discussion:)
One more point about works with ids, Do the [special char] must the valid id itself?
I think it should, because otherwise we will need extra validation of yaml parsing.

Do we know if anyone is using yaml schema validation for the detekt config? I think auto-complete should still work for the general rule instance, but validation would fail. But I guess that is already the case for 3rd party rules.
We should take into account #4162, when thinking about this.

/ can work. We can think of the ID as a path or the name of the rule as a directory. I like the discussion to see pros and cons

Ok, at #7263 I have the first working version of detekt running multiple instances of the same rule with different configurations.
There is still work to do but it works!
Missing things:

tests, lots of them.
Rework the config validator, our config files now are different! Probably all this part needs a full refactor. Now that we have the annotations on the rules to generate the config file we could also autogenerate the code that validates it... I'm not sure but it would be cool. But I don't want to go that far for this issue.
Documentation, we need to explain how to use this feature.
Take some decissions about naming and how do we want the configuration to look like. For now I'm using / as the separator but I would like to hear feedback about how it looks like.
Work on the reports and baseline. We need to use the instance id to report the issues, no the name of the rule itself.


Large data crash app on letter scrolling

Hello, i have really large list and when i'm trying scroll it by letter library crash app... It can't find where to scroll because didn;t render this items yet... Do you have any ideas how to fix it... Data about 6000 words grouped by letters...

@Ildar7sins  did you find a solution for that?

Nope, I left it as it is
вт, 25 февр. 2020 г. в 17:48, Aleverh<EMAIL_ADDRESS>
@Ildar7sins https://github.com/Ildar7sins did you find a solution for
that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CoderJWYang/react-native-alphabet-sectionlist/issues/1?email_source=notifications&email_token=AFM3QQI7OPO5T22ZP3D5RWTREUHSVA5CNFSM4J3Q4ZT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM32P7I#issuecomment-590850045,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFM3QQMM5DX7USHZ5TNTIALREUHSVANCNFSM4J3Q4ZTQ
.


feat: allow folder of problem matcher registration

Allows registering of new problem matchers by adding them to folder

What about merging this?

Allows registering of new problem matchers by adding them to folder


Conflict between gas_multiplier and gas_adjustment

Summary of Bug

Running with --config flag expects gas_multiplier while other commands expect gas_adjustment
Using gas_multiplier = 2,  hermes tx raw create-client ibc-1 ibc-0 throws : hermes tx raw create-client ibc-1 ibc-0
Version

hermes 1.0.0
gaia 4.2.1
Steps to Reproduce

Create a config file with gas_adjustment = 1.0 instead of gas_multiplier
cargo run -q --bin hermes -- --config "$CONFIG_FILE" keys add --chain "$CHAIN_0_ID" --key-file "$GAIA_DATA/$CHAIN_0_ID/user_seed.json"` (command used by `ibc-rs/scripts/init-hermes`)

should throw :
error: hermes fatal error: config error: config file specifies deprecated setting gas_adjustment = 1` for the chain 'ibc-0'; to get the same behavior, use `gas_multiplier = 2`

Then replace gas_adjustment by gas_multiplier
hermes tx raw create-client ibc-1 ibc-0

throws :
The Hermes configuration file at path '~/.hermes/config.toml' is invalid, reason: parse error: unknown field `gas_multiplier`, expected one of `id`, `rpc_addr`, `websocket_addr`, `grpc_addr`, `rpc_timeout`, `account_prefix`, `key_name`, `key_store_type`, `store_prefix`, `default_gas`, `max_gas`, `gas_adjustment`, `fee_granter`, `max_msg_num`, `max_tx_size`, `clock_drift`, `max_block_time`, `trusting_period`, `memo_prefix`, `proof_specs`, `trust_threshold`, `gas_price`, `packet_filter`, `address_type` for key `chains` at line 239 column 1

Acceptance Criteria

Every command only expects gas_adjustment or gas_multiplier

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

What's happening here is that when you do not pass the --config FILE option, Hermes will load the configuration from ~/.hermes/config.toml instead of FILE.
In your case, it seems that the config file at  ~/.hermes/config.toml still mentions the now deprecated gas_adjustment setting. To fix this you should be able to switch from gas_adjustment to gas_multiplier in that config file, or just always pass the --config FILE option with a path to a valid/up-to-date configuration file.

From private chat: the issue is that binary in the second command is outdated. That stems from the fact that cargo install ibc-relayer-cli (as per the guide) will install Hermes 0.15.0 instead of 1.0.0-rc.0 as the latter is a pre-release. We need to update the guide to fix the Cargo installation step.


Automated cherry pick of #9775: fix(cloudevent): default policy

Cherry pick of #9775 on release/3.7.
#9775: fix(cloudevent): default policy

Codecov Report

Merging #9776 (0ff3997) into release/3.7 (56d583e) will increase coverage by 9.92%.
The diff coverage is 0.00%.

@@               Coverage Diff                @@
##           release/3.7    #9776       +/-   ##
================================================
+ Coverage         6.00%   15.92%    +9.92%
================================================
  Files              845      124      -721
  Lines           131245    12780   -118465
================================================
- Hits              7879     2035     -5844
+ Misses          122665    10554   -112111
+ Partials           701      191      -510

Flag
Coverage Δ

aFlag
15.92% <0.00%> (+9.92%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apis/input.go
0.00% <ø> (ø)

pkg/apis/list.go
0.00% <ø> (ø)

pkg/compute/guestdrivers/aliyun.go
2.56% <0.00%> (-0.17%)
:arrow_down:

pkg/compute/guestdrivers/apsara.go
13.63% <0.00%> (-0.65%)
:arrow_down:

pkg/compute/guestdrivers/managedvirtual.go
0.00% <0.00%> (ø)

pkg/compute/guestdrivers/utils.go
0.00% <0.00%> (ø)

pkg/util/k8s/kubeadm/kubeadm.go

pkg/compute/models/secgroupresource.go

pkg/compute/models/specs.go

pkg/mcclient/options/k8s/fed_clusterrolebinding.go

... and 639 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #9776 (0ff3997) into release/3.7 (56d583e) will increase coverage by 9.92%.
The diff coverage is 0.00%.

@@               Coverage Diff                @@
##           release/3.7    #9776       +/-   ##
================================================
+ Coverage         6.00%   15.92%    +9.92%
================================================
  Files              845      124      -721
  Lines           131245    12780   -118465
================================================
- Hits              7879     2035     -5844
+ Misses          122665    10554   -112111
+ Partials           701      191      -510

Flag
Coverage Δ

aFlag
15.92% <0.00%> (+9.92%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apis/input.go
0.00% <ø> (ø)

pkg/apis/list.go
0.00% <ø> (ø)

pkg/compute/guestdrivers/aliyun.go
2.56% <0.00%> (-0.17%)
:arrow_down:

pkg/compute/guestdrivers/apsara.go
13.63% <0.00%> (-0.65%)
:arrow_down:

pkg/compute/guestdrivers/managedvirtual.go
0.00% <0.00%> (ø)

pkg/compute/guestdrivers/utils.go
0.00% <0.00%> (ø)

pkg/util/k8s/kubeadm/kubeadm.go

pkg/compute/models/secgroupresource.go

pkg/compute/models/specs.go

pkg/mcclient/options/k8s/fed_clusterrolebinding.go

... and 639 more

Continue to review full report at Codecov.

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


Adding new rank property to sensitivity label object

You don't have permission to trigger SDK Automation.
Please add yourself to Azure group from opensource portal if you are MSFT employee,
or please ask reviewer to add comment *** /openapibot sdkautomation ***.
Please ask<EMAIL_ADDRESS>(or NullMDR in github) for additional help.

Can one of the admins verify this patch?

/openapibot sdkautomation

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk


File with platform dependent name has been skipped

It appears I have a note with a $ sign in its name, that file doesn't gets synced into an iOS vault. Can't those special characters be escaped/unicoded/etc. ?

I may have fallen asleep: I completely misunderstood the specification.
Tested by Mac, Windows, Linux, Android, and iOS. Every device allowed $sign.
This will be fixed in the next release!
Sorry for trouble you. And thank you for your report!
Always helpful!

Fixed on 0.1.22.


Create a log file even when there's nothing to do

  }

why is this needed? it looks like we are already handing the error gracefully a few lines down. Additional I/Os should be avoided if possible.

Refers to: cmd/copyEnumeratorInit.go:276 in e31e17f. [](commit_id = e31e17f1cdbe1ea59c6dab7f3357eee05162bc91, deletion_comment = False)

OK so some explaining with that last commit:
For some reason, Git didn't mind merging this branch onto a branch based on master. But if I'd just rebased, every file in azcopy would have merge conflicts.

Will merge once CI passes

Squash and merge


Window rules: null pointer deref / crash

Noticed yabai crashing within a second of opening the Workflows pane in the Alfred Preferences app. Looking at it with lldb it's likely a null pointer deref somewhere related to the window title when applying the window rules? Haven't yet dug any deeper, will do later if more info is needed. The relevant rule for Alfred Preferences is visible below as well.
[...]
EVENT_HANDLER_DAEMON_MESSAGE: msg 'rule --add app=^Finder$ title=^Copy$ sticky=on'
EVENT_HANDLER_DAEMON_MESSAGE: msg 'rule --add app=^Little Snitch Network Monitor$ fullscreen=on'
EVENT_HANDLER_DAEMON_MESSAGE: msg 'rule --add app=^Alfred Preferences$ manage=off'
EVENT_HANDLER_DAEMON_MESSAGE: msg 'rule --add app=^System Preferences$ manage=off'
EVENT_HANDLER_DAEMON_MESSAGE: msg 'rule --add app=^Chrome$ title=^Picture in Picture$ sticky=on'
EVENT_HANDLER_DAEMON_MESSAGE: msg 'rule --add app=^Digital Colou?r Meter$ sticky=on'
EVENT_HANDLER_APPLICATION_FRONT_SWITCHED: Alfred Preferences
EVENT_HANDLER_APPLICATION_DEACTIVATED: iTerm2
EVENT_HANDLER_APPLICATION_ACTIVATED: Alfred Preferences
Process 18394 stopped
* thread #6, stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
    frame #0: 0x00007fff4a3dff1e CoreFoundation`CFStringGetLength + 10
CoreFoundation`CFStringGetLength:
->  0x7fff4a3dff1e <+10>: movq   (%rdi), %rax
    0x7fff4a3dff21 <+13>: testq  %rax, %rax
    0x7fff4a3dff24 <+16>: je     0x7fff4a3dff51            ; <+61>
    0x7fff4a3dff26 <+18>: leaq   0x5b2c0e13(%rip), %rcx    ; __CFConstantStringClassReferencePtr
(lldb) bt
* thread #6, stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
  * frame #0: 0x00007fff4a3dff1e CoreFoundation`CFStringGetLength + 10
    frame #1: 0x00000001000132f5 yabai`window_title + 69
    frame #2: 0x0000000100006d95 yabai`window_manager_apply_rule_to_window + 117
    frame #3: 0x000000010001e608 yabai`EVENT_HANDLER_WINDOW_CREATED + 344
    frame #4: 0x00000001000054a8 yabai`eventloop_run + 88
    frame #5: 0x00007fff76a9f2eb libsystem_pthread.dylib`_pthread_body + 126
    frame #6: 0x00007fff76aa2249 libsystem_pthread.dylib`_pthread_start + 66
    frame #7: 0x00007fff76a9e40d libsystem_pthread.dylib`thread_start + 13
(lldb)

That is indeed a null deref when accessing the CFStringRef object which should be containing the window title. This is supposed to be handled, but I guess I made a mistake when reverse engineering that function:https://github.com/koekeishiya/yabai/blob/master/src/window.c#L167
Guess I'll change that to validate the pointer rather than relying on the result code.

Just to confirm: the issue is fixed.


contents(centos stream): add centos stream help

added basic usage for centos stream.
modify usage of epel for centos stream.
See also https://github.com/tuna/issues/issues/1603

It seems that I mistakenly clicked on re-request review.


Amirsalar hosseini & Arwin jafari

updated by ME and @ArvinNotDev
for this request we create two apps(appointment and medicine) and complete their models

Since you have already committed i recommend you remove .idea directory since its just a part of pycharm  not the project
I also recommend you changing the .gitignore configuration to ignore whole .idea directory


Cache bundler dependencies

Hi @magnusvk,
So the issue is because you customize the install phase in .travis.yml by explicitly updating dependencies (see these lines), which makes them installed to a different directory ~/.rvm/gems other than the default directory vendor/bundle. You may see this for reference.
So now I've changed cache to point to the directory where gems are installed, and seems working. I restarted some jobs and I see that dependencies are being used from the cache. Thanks.

Thank you!


HTML Tooltips not showing inline SVG

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
When you put some inline SVG inside tooltips they're not added to the tooltip html (
). They're missing from the tooltip content. However it works with .
Reduced test cases
<a href="#"  data-bs-toggle="tooltip" data-bs-placement="right" data-bs-title="
<svg role='img' focusable='false' width='28' height='28' xmlns='http://www.w3.org/2000/svg' viewBox='0 0 28 28'><circle cx='14px' cy='14px' r='14px' fill='currentColor'></circle></svg>Some Content
"  data-bs-html="true"> Hello
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome, Safari, Firefox, Microsoft Edge, Opera
What version of Bootstrap are you using?
5.3.0

Given the HTML you're including, you're probably running into an HTML parsing error first and our sanitizer second. https://getbootstrap.com/docs/5.3/components/tooltips/#options

It appears that the issue is caused by Bootstrap's sanitizer rather than the HTML included. I have done some unit testing and the SVG does not seem to be passed through in any case - as soon as there is an SVG tag, it does not pass through.


Add more to content of pages, along with slight reordering of nav bar

LOL Cam I appreciate the GIF. I honestly haven't felt like I've been as productive as I can be, so I'm gonna pick up the pace.


Move aiida-core~=2.6 dependency to dev

This PR reverts the aiida-core dependency back to ~=2.1 and moves the ~=2.6 pin to dev dependencies. See resolved issue for detail.
Resolves #180

Unfortunately it is not so easy. There were a number of changes in the API of aiida-core in v2.6 that we already adjusted to, amongst which the hashing. See bcc0129cc0b1b6fa5ddfe7d91f09d805ceb40d15
The issue says

However, this dependency leads to conflicts with packages using aiida-pseudo that have yet to upgrade.

What are the specific problems? I think we should rather work to fix those than revert here.

The issue says

However, this dependency leads to conflicts with packages using aiida-pseudo that have yet to upgrade.

What are the specific problems? I think we should rather work to fix those than revert here.

I'll let @superstar54 explain. It was mostly a concern for those who use older versions of aiida-core AND aiida-pseudo.
As for the particular issue at hand, we're trying to release aiidalab-qe. All of our tests are running into an issue with aiida-pseudo w.r.t downloading the pseudos. This was "fixed" in #179, which already includes the ~=2.6 pin. This is now causing issues with the release due to aiidalab dependencies, but let me see if I can overcome those issues. I think it has already been tested with 2.6 and a new image is available. I'll check.

Hi @sphuber , thanks for the quick comment.

What are the specific problems? I think we should rather work to fix those than revert here.

We want to use aiida-pseudo inside the AiiDAlab docker image, which fixs aiida-core version==2.5.1.

We avoid the issue by using the latest AiiDAlab full-stack image with aiida-core 2.6.
As discussed with @edan-bainglass , we closed this PR.


delete unnecessary/clumsy statement

I don't think the paragraph needs this sentence: "Lightweight local services are less compelling than they once were."

Thanks @jones77 but I'm going to leave it in.  It's what the author intended to write - what he intended to convey, and it feels like the correct context for juxtaposing local services with remote ones.


Parallel-safe white noise generation

Fixes #85

Sorry, actually I'm just going to merge this since it's such a small change - don't want to waste your time @ludgerpaehler.


[folder request] Folders on top of the list

Do you request a file icon or a folder icon?
"Folder"
Which endings or names shall it applied to?
List endings or names here.

All folders

Which reference can be used?
List here images or links to references e.g. the language logo.

Am I understanding you correctly that you would like to have a feature, to toggle the order of the file browser items according to their type (file or folder) such that folders are always listed before files?

Without feedback, I will close this issue soon. :)

would love to see any configuration for this plugin, started using it accidentally because of new icons in nova 9 that I cant get used to.

Am I understanding you correctly that you would like to have a feature, to toggle the order of the file browser items according to their type (file or folder) such that folders are always listed before files?

yeah exactly, sorry for responding so late

@TeddRod v1.1.0 now allows to change order of file browser items. :)
Also @thfrlw I added basic configuration option to hide specific items in file browser (currently only by exact matching). Maybe this improves your usage of this extension.


Update to work with Python3 where needed

Today, I continued to work on the HILICS device. I thought I had ironed out most issues last week but when working on it today I found a few errors the would be thrown that related to some of the classes being used. I worked through to find the issues. I will continue to rectify the issue in order to start practicing the labs and ensuring they are well written.


Permits to ask for a response mandatory signed

Add and handle a configuration parameter to be used to ask for a response mandatory signed

Hi, build with jdk11 fails but it shouldn't be up to me ...
Please, let me know if I missed something.
Regards.


Error when Remove item of list child

Hi Team,
I have a error.
I have a list of modal.
Step 1:  Add an item (not valid by antotation) to list on front end
Step 2: Click save and run editContext.ValidateObjectTree()  return false -> OK show error to front end
Step 3: Then I remove this item
Step 4:  Click save and  editContext.ValidateObjectTree()
But  this return false and error
When i get editContext.GetValidationMessages() This return msg error of deleted item
Please help me fix it

Do any of the Editcontext methods help?
https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.components.forms.editcontext?view=aspnetcore-3.1#methods

@mrpmorris I'm having the same issue, but can only reproduce in a WebAssembly project.

Copy files from sample 2 to a new WebAssembly project.
Add a ` to samples/02-FluentValidation/FluentValidationSample/Pages/Index.razor
add Console.WriteLine(editContext.ValidateObjectTree()); to void SubmitForm
Run the project
Submit the form and verify errors from the summary
Remove an address
See that the summary still has errors from that address

Unfortunately, there is no way for me to clear out existing error messages. You'll have to call editContext.Validate() before calling editContext.ValidateObjectTree


Doesn't do anything...

i tried the sample. Pressed "start" and nothing happens. Also tried "stop" after that, and still nothing. What is going on?
I have given it permission to capture the screen, btw.

also i got it to crash on some case, when pressing home and then returning to the app (it's more steps than this, but i can't reproduce) . Here's the log:
01-01 19:13:27.876 7249-7302/com.example.android.screencapture E/Surface: dequeueBuffer: IGraphicBufferProducer::requestBuffer failed: -22
01-01 19:13:27.876 7249-7302/com.example.android.screencapture E/libEGL: eglMakeCurrent:895 error 3003 (EGL_BAD_ALLOC)
01-01 19:13:27.876 7249-7302/com.example.android.screencapture A/OpenGLRenderer: Failed to make current on surface 0xb486d220, error=EGL_BAD_ALLOC
01-01 19:13:27.876 7249-7302/com.example.android.screencapture A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 7302 (RenderThread)
01-01 19:14:18.221 9294-9344/com.example.android.screencapture E/Parcel: dup failed in Parcel::read, fd 1 of 4
dup(-2147483647) = -1 [errno: 9 (Bad file number)]
fcntl(-2147483647, F_GETFD) = -1 [errno: 9 (Bad file number)]
flat 0x0 type 0

also i got it to crash on some case, when pressing home and then returning to the app (it's more steps than this, but i can't reproduce) . Here's the log:
01-01 19:13:27.876 7249-7302/com.example.android.screencapture E/Surface: dequeueBuffer: IGraphicBufferProducer::requestBuffer failed: -22
01-01 19:13:27.876 7249-7302/com.example.android.screencapture E/libEGL: eglMakeCurrent:895 error 3003 (EGL_BAD_ALLOC)
01-01 19:13:27.876 7249-7302/com.example.android.screencapture A/OpenGLRenderer: Failed to make current on surface 0xb486d220, error=EGL_BAD_ALLOC
01-01 19:13:27.876 7249-7302/com.example.android.screencapture A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 7302 (RenderThread)
01-01 19:14:18.221 9294-9344/com.example.android.screencapture E/Parcel: dup failed in Parcel::read, fd 1 of 4
dup(-2147483647) = -1 [errno: 9 (Bad file number)]
fcntl(-2147483647, F_GETFD) = -1 [errno: 9 (Bad file number)]
flat 0x0 type 0


Decoder is ambiguous for type lookup in this context

I get the above error where I'm extending Decoder.
extension Decoder { // 'Decoder' is ambiguous for type lookup in this context

}

I'm using Xcode 9 beta 4 so I understand that this has something to do with Swift 4. A naming conflict perhaps?
Any quick fix for this? I have the library installed via CocoaPods so I can't edit the source there.

try using the explicit namespace - Gloss.Decoder

That works!

naming will be updated to JSONDecodable and JSONEncodable as of version 2.0.0-beta.2

Gloss.Decodable


Clarification re: Type is part of the declaration of 2 modules

Hi, and thanks for a great library! I'm currently evaluating this for one of our Angular applications and I've come across one of the issues documented here where I have the following situation:

Module A and module B both import CommonModule from @angular/common.
Module B depends on module A.
I try to test a component in module B where I need to mock out something from CommonModule explicitly.

I have set up a StackBlitz showcasing what I try to do here: https://stackblitz.com/edit/angular-ivy-7cnyfm?file=src/app/feature/sample.component.spec.ts
I basically have:

SharedModule which imports CommonModule.
FeatureModule which imports SharedModule and CommonModule
A SampleComponent in SharedModule which takes a date input and passes it to the Angular DatePipe.

I set this up according to my understanding of the docs I linked earlier like this:
MockBuilder(SampleComponent)
  .keep(FeatureModule)
  .mock(SharedModule)
  .mock(DatePipe, value => 'MOCK:' + value);

This fails with the following error:

Error: Type NgClass is part of the declarations of 2 modules: CommonModule and MockOfCommonModule! Please consider moving NgClass to a higher module that imports CommonModule and MockOfCommonModule. You can also create a new NgModule that exports and includes NgClass then import that NgModule in CommonModule and MockOfCommonModule.

...and then repeated for more or less everything else in CommonModule.
Am I misunderstanding the docs here? I'd be happy to help clarify if I understood what the problem was, but as far as I'm able to tell this should be how things are intended to work.
This error also occurs if I stop including SharedModule in my FeatureModule and set the tests up like this, leading me to believe this isn't the same case as in the documentation:
MockBuilder(SampleComponent, FeatureModule)
  .mock(DatePipe, value => 'MOCK:' + value);

Setting it up like in the documentation with .keep(FeatureModule) and .mock(CommonModule) also yields the same results.

Hi,
thanks for the report.
yeah, a very good case :) CommonModule is never mocked and skipped everywhere, but finally there is a good example why we need to process its declarations.
Thanks! It will be fixed with the next release.

Ah, right. That explains it. It probably also explains why I see the default implemented behavior of DatePipe if I just do MockBuilder(SampleComponent, FeatureModule) when my understanding was that all dependencies would be mocked by default even if I don't specify the mock myself.
Is there anything I can do to work around this for the time being? I don't see any clear points where this would happen in MockModule or MockBuilder after glancing through the code quickly but.

MockBuilder(SampleComponent, FeatureModule) is the right direction and it does mock everything, besides SampleComponent and CommonModule.
The idea around skipping CommonModule everywhere is that people usually don't expect ngIf, ngFor, async to be mocked. I think to change this approach so in the end CommonModule would be processed as .keep by default and anything inside of it could be adjusted for testing needs.
About a work around.... A good question :) I think you could try .exclude(CommonModule).mock(DatePipe, ...), but I'm if it works on the current version.

It works, sort of, except it's going to be a bit of a pain to set up all the keeps. I'll refactor the code slightly to use our own pipes for formatting these dates so its easier to mock - we should do that for other purposes as well so it's no big issue.
But then I've found the source to my issues here, so I'm gonna go ahead and close this issue. I'll revisit once the next release is out to see if we can do things differently at that point but for now this gets me further - thanks a lot for the help!

Nice.
Btw, please keep the issue open, it works like a remind for me to solve it when I have time. It will be closed during a release process of the next version.

So, actually ng-mocks does process CommonModule, but the problem is that BrowserDynamicTestingModule exports BrowserTestingModule which exports BrowserModule which exports CommonModule.
Looking for a solution how to inject MockOfCommonModule into BrowserDynamicTestingModule.

Hi @tanordheim,
could you verify whether this version works for you needs?
ng-mocks.zip
Thanks in advance!

For my usecase, this worked. The test case below yielded the expected "Type NgClass is part of the declarations of 2 modules" error on the latest release, and passed successfully with the version you attached.
@Component({
  template: '<p>{{ testDate | date:"short" }}',
})
class TestComponent {
  testDate = new Date();
}

describe('DatePipe mock', () => {
  beforeEach(() => {
    return MockBuilder(TestComponent, SharedModule)
      .mock(DatePipe, (v: any) => 'mocked:' + v);
  });

  it('should use mocked date pipe', () => {
    const fixture = MockRender(TestComponent);
    expect(fixture.point.nativeElement.textContent).toContain('mocked');
  });
});

Thanks for the feedback! On the upcoming weekend, I'll release a new version with the fix.


Async not used

The template does not use async at all. Is there any particular reason for that? Do celery, sqlalchemy etc work with async?
How much code will have to be changed for async?

I was trying to find out that info. So no asyncpg?

I couldn't find a way to use sqlalchemy with async-await for my previous project so I decided to check the Databases project

For database async application, tortoise-orm is fine too.

sqlalchemy 1.4 enables async use of the ORM

I am having the same questions/doubts +1
It would seem the generated code might not be production ready as it involves blocking operations, going against the async paradigm.  🤔


refactor(OpenTelemetry): remove SDK version from meter name

Description

This removes the SDK version from the meter name, as this is adequately tracked by the user agent attribute.
References

Review Checklist

[x] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 69.15%. Comparing base (a00f039) to head (2e2be25).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #134      +/-   ##
==========================================
- Coverage   69.15%   69.15%   -0.01%
==========================================
  Files         122      122
  Lines        9746     9745       -1
==========================================
- Hits         6740     6739       -1
  Misses       3006     3006

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


All paths relative to config file location.

Currently all paths in the configuration are relative to the current working directory. Making paths relative to the config file they are declared in will open up some possibilities in the future. Paths declared from the command line should be relative to the current working directory, however.
Related to #187.

Ended up not having a separate working directory for command line options. It was far more economical to change the working directory to the location of the config file.


Updating python runtimes in README where the feature is not working.

Issue #, if available:
Description of changes:
The feature doesn't work with Python3.10 and Python3.11.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks for the update. @pushkarchawda


use a variable to skip the copy of certificate

Like in the consul role, let the certificates to be copied in a different way

Thanks!


build: add cmake config to use find_package

what

add cmake config
install config file
add conan to readme

why

allow usage of cmake's find_package

@kingkili Ping.

Overall this looks good, but I am running into problems when using the submodule curl. Can please have look into it.

Overall this looks good, but I am running into problems when using the submodule curl. Can please have look into it.

which problems do you have?
usging find_package is only intended when you choose to use the system CURL library
using the vendored CURL library should probably only done for development, as linking two different CURL libs results in undefined behaviour

Yes but it should be still possible to build the library without system curl, since it fails while configuring it else.
Steps to reproduce:
git clone https://github.com/gocarlos/cpr --recursive
mkdir cpr/build
cd cpr/build
cmake .. -DUSE_SYSTEM_CURL=OFF -DUSE_SYSTEM_GTEST=OFF
´´´
Which will result in the [log](https://github.com/whoshuu/cpr/files/4626856/log.txt)

With #383 I would say all features proposed here have been merged.
I’m closing this.
Feel free to open a new PR if something is missing.


python311Packages.openai: 1.39.0 -> 1.40.0

Description of changes
Update to latest version, add new dependencies, and do some small cleanup.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 332797 run on aarch64-darwin 1

72 packages marked as broken and skipped:

chatgpt-retrieval-plugin
chatgpt-retrieval-plugin.dist
khoj
khoj.dist
python311Packages.llama-index
python311Packages.llama-index-agent-openai
python311Packages.llama-index-agent-openai.dist
python311Packages.llama-index-cli
python311Packages.llama-index-cli.dist
python311Packages.llama-index-core
python311Packages.llama-index-core.dist
python311Packages.llama-index-embeddings-gemini
python311Packages.llama-index-embeddings-gemini.dist
python311Packages.llama-index-embeddings-google
python311Packages.llama-index-embeddings-google.dist
python311Packages.llama-index-embeddings-huggingface
python311Packages.llama-index-embeddings-huggingface.dist
python311Packages.llama-index-embeddings-ollama
python311Packages.llama-index-embeddings-ollama.dist
python311Packages.llama-index-embeddings-openai
python311Packages.llama-index-embeddings-openai.dist
python311Packages.llama-index-graph-stores-nebula
python311Packages.llama-index-graph-stores-nebula.dist
python311Packages.llama-index-graph-stores-neo4j
python311Packages.llama-index-graph-stores-neo4j.dist
python311Packages.llama-index-graph-stores-neptune
python311Packages.llama-index-graph-stores-neptune.dist
python311Packages.llama-index-indices-managed-llama-cloud
python311Packages.llama-index-indices-managed-llama-cloud.dist
python311Packages.llama-index-legacy
python311Packages.llama-index-legacy.dist
python311Packages.llama-index-llms-ollama
python311Packages.llama-index-llms-ollama.dist
python311Packages.llama-index-llms-openai
python311Packages.llama-index-llms-openai-like
python311Packages.llama-index-llms-openai-like.dist
python311Packages.llama-index-llms-openai.dist
python311Packages.llama-index-multi-modal-llms-openai
python311Packages.llama-index-multi-modal-llms-openai.dist
python311Packages.llama-index-program-openai
python311Packages.llama-index-program-openai.dist
python311Packages.llama-index-question-gen-openai
python311Packages.llama-index-question-gen-openai.dist
python311Packages.llama-index-readers-database
python311Packages.llama-index-readers-database.dist
python311Packages.llama-index-readers-file
python311Packages.llama-index-readers-file.dist
python311Packages.llama-index-readers-json
python311Packages.llama-index-readers-json.dist
python311Packages.llama-index-readers-llama-parse
python311Packages.llama-index-readers-llama-parse.dist
python311Packages.llama-index-readers-s3
python311Packages.llama-index-readers-s3.dist
python311Packages.llama-index-readers-twitter
python311Packages.llama-index-readers-twitter.dist
python311Packages.llama-index-readers-txtai
python311Packages.llama-index-readers-txtai.dist
python311Packages.llama-index-readers-weather
python311Packages.llama-index-readers-weather.dist
python311Packages.llama-index-vector-stores-chroma
python311Packages.llama-index-vector-stores-chroma.dist
python311Packages.llama-index-vector-stores-google
python311Packages.llama-index-vector-stores-google.dist
python311Packages.llama-index-vector-stores-postgres
python311Packages.llama-index-vector-stores-postgres.dist
python311Packages.llama-index-vector-stores-qdrant
python311Packages.llama-index-vector-stores-qdrant.dist
python311Packages.llama-index.dist
python311Packages.llama-parse
python311Packages.llama-parse.dist
python311Packages.private-gpt
python311Packages.private-gpt.dist

6 packages failed to build:

mealie
mealie.dist
open-interpreter (python312Packages.open-interpreter)
open-interpreter.dist (python312Packages.open-interpreter.dist)
python311Packages.open-interpreter
python311Packages.open-interpreter.dist

87 packages built:

chatblade
chatblade.dist
checkov
checkov.dist
imaginer
llm (python312Packages.llm)
llm.dist (python312Packages.llm.dist)
open-webui
open-webui.dist
openai (python312Packages.openai)
openai.dist (python312Packages.openai.dist)
pentestgpt
pentestgpt.dist
python311Packages.graphrag
python311Packages.graphrag.dist
python311Packages.guidance
python311Packages.guidance.dist
python311Packages.instructor
python311Packages.instructor.dist
python311Packages.langchain
python311Packages.langchain-azure-dynamic-sessions
python311Packages.langchain-azure-dynamic-sessions.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-huggingface
python311Packages.langchain-huggingface.dist
python311Packages.langchain-mongodb
python311Packages.langchain-mongodb.dist
python311Packages.langchain-openai
python311Packages.langchain-openai.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langgraph
python311Packages.langgraph.dist
python311Packages.langsmith
python311Packages.langsmith.dist
python311Packages.litellm
python311Packages.litellm.dist
python311Packages.llm
python311Packages.llm.dist
python311Packages.llmx
python311Packages.llmx.dist
python311Packages.openai
python311Packages.openai.dist
python312Packages.graphrag
python312Packages.graphrag.dist
python312Packages.guidance
python312Packages.guidance.dist
python312Packages.instructor
python312Packages.instructor.dist
python312Packages.langchain
python312Packages.langchain-azure-dynamic-sessions
python312Packages.langchain-azure-dynamic-sessions.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-huggingface
python312Packages.langchain-huggingface.dist
python312Packages.langchain-mongodb
python312Packages.langchain-mongodb.dist
python312Packages.langchain-openai
python312Packages.langchain-openai.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langgraph
python312Packages.langgraph.dist
python312Packages.langsmith
python312Packages.langsmith.dist
python312Packages.litellm
python312Packages.litellm.dist
python312Packages.llmx
python312Packages.llmx.dist
shell-genie
shell-genie.dist
shell-gpt
shell-gpt.dist
sploitscan
sploitscan.dist

I merged the PR, please use python312Packages next time.


Deck tables should be js-sortable

Sort by size of competition, finish, colors, etc. are all useful.

I did this.


Spaces

It appears that the primary sails repo generates code with spaces. However, sails-generate-model
appears to use tabs.  The result is this weird mix of tabs and spaces in generated code: Screen shot
To keep consistency, replace the hard tabs in the templates with spaces. The rest of the code,
that is the non template code, I am indifferent about.

@JemiloII looks like the templates have had <%if (lang === 'js') {%>...<%} else if (lang === 'coffee'){ %> added to them. @nategood if you want to update the current templates to use spaces, I'll merge it in.


Restore old Gemini API

Converting the Gemini calls to use the OpenAI API shim was attractive, but doesn't actually work with structured calls. Restore the old way of using the Gemini API using Google's SDK.

See #14


Issue with calling action when migrating from Redux Form v5.3.3 to v6.1.1

Hi Everyone,
I can't seem to figure out why my action is not being called when I migrated my version 5 redux form to v6. Currently, action is being called but nothing is being returned and no dispatch is sent to reducer at the moment.  I am using redux thunk as a reducer, but my action never gets dispatched to the reducer when I make the switch. V5 version redux-form works perfectly. Below is my action/action creator, V5 and v6 form components.
I am pointing out in line 8 of the action where the function stops returning results.
using version 6.1.1 and migrating from 5.3.3.
I need to migrate because of the improvement in deep forms in version 6 has drastically improved my other parts of the app but I can't get this seemingly simple Sign In component to work...
Thanks!
ACTION
import axios from 'axios';
import {browserHistory} from 'react-router';
import {AUTH_USER, UNAUTH_USER, AUTH_ERROR, ROOT_AUTH_URL} from '../constants/auth.constants';

export function signinUser({email, password}) {
  console.log('email and password in action', email, password);
---- The console above returns the correct message in the browser. ----
**---- NOTHING IS RENDERED below this in redux form v6. V5 WORKS perfect.**-----------------
  return dispatch => {
    console.log('pass the return'); ------> does not work :-(
        // Submit email/password to the server
    axios.post(`${ROOT_AUTH_URL}signin`, {email, password})
    .then(response => {
      console.log('response', response);
      // - Update state to indicate user is authenticated: flag will turn to "true"
      dispatch({type: AUTH_USER});
      // - Save the JWT token in local storage
      localStorage.setItem('token', response.data.token);

      // - redirect to the route '/feature'
      browserHistory.push('/');
    })
    .catch(() => {
                    // if request is bad...
                    // - Show an error to the user
      dispatch(authError('Bad Login Info!'));
    });
  }
}
**---- ABOVE is NOT RENDERED in v6.. while in v5 works perfect **-----------------

VERSION 6.1.1 REDUX FORM COMPONENT
import React, {Component, PropTypes} from 'react';
import {reduxForm, Field} from 'redux-form';
import {signinUser} from '../../actions/auth.actions';

class Signin extends Component {
    // used to take supplied inputs and check auth
  handleFormSubmit({email, password}) {
        // Need something to log user in
    console.log('test', email, password);
    signinUser({email, password});
  }

  renderAlert() {
    if (this.props.errorMessage) {
      return (

          Oops! {this.props.errorMessage}

        );
    }
  }

  render() {
    // handleSubmit is a built in redux-form helper to bind ui to values
    const {handleSubmit} = this.props;

    return (
      <form onSubmit={handleSubmit(this.handleFormSubmit.bind(this))}>
        <fieldset className="form-group">
          Email:
          <Field name="email" component="input" type="text" required className="form-control"/>
        </fieldset>
        <fieldset className="form-group">
          Password:
          <Field name="password" component="input" type="password" required className="form-control"/>
        </fieldset>
        {this.renderAlert()}
        <button action="submit" className="btn btn-primary">Sign in</button>
      </form>
    );
  }
}

Signin.propTypes = {
  signinUser: PropTypes.func,
  errorMessage: PropTypes.string,
  handleSubmit: PropTypes.func
};

function mapStateToProps(state) {
  return {errorMessage: state.auth.error};
}

export default reduxForm({
  form: 'signin'
}, mapStateToProps, signinUser)(Signin);

VERSION 5.3.3 REDUX FORM COMPONENT
import React, {Component, PropTypes} from 'react';
import {reduxForm} from 'redux-form';
import * as actions from '../../actions/auth.actions';
class Signin extends Component {
    // used to take supplied inputs and check auth
  handleFormSubmit({email, password}) {
        // Need something to log user in
    this.props.signinUser({email, password});
  }

  renderAlert() {
    if (this.props.errorMessage) {
      return (

          Oops! {this.props.errorMessage}

        );
    }
  }

  render() {
    // handleSubmit is a built in redux-form helper to bind ui to values
    const {handleSubmit, fields: {email, password}} = this.props;

    return (
      <form onSubmit={handleSubmit(this.handleFormSubmit.bind(this))}>
        <fieldset className="form-group">
          Email:
          <input {...email} type="text" required className="form-control"/>
        </fieldset>
        <fieldset className="form-group">
          Password:
          <input {...password} type="password" required className="form-control"/>
        </fieldset>
        {this.renderAlert()}
        <button action="submit" className="btn btn-primary">Sign in</button>
      </form>
    );
  }
}

Signin.propTypes = {
  signinUser: PropTypes.func,
  errorMessage: PropTypes.string,
  handleSubmit: PropTypes.func,
  fields: PropTypes.object
};

function mapStateToProps(state) {
  return {errorMessage: state.auth.error};
}

export default reduxForm({
  form: 'signin',
  fields: ['email', 'password']
}, mapStateToProps, actions)(Signin);

I didn't analyze all of the code, but the first thing I see that can be problematic is in the component and reduxForm call:
export default reduxForm({
  form: 'signin'
}, mapStateToProps, signinUser)(Signin);

As you can see in the docs (http://redux-form.com/6.1.1/docs/api/ReduxForm.md/), as of now, reduxForm only takes configuration object. If you want to use redux's mapStateToProps and mapDispatchToProps, you need to use connect (as with other connected redux components/containers). You can do something like this:
// (other imports)
import { connect } from 'react-redux';

// (your component code)

const SigninForm = reduxForm({
    // (your redux-form config)
});

const mapStateToProps = (state) => {
    return {
        // (data you want to get from your store)
    };
};

// simple version of mapDispatchToProps - more advanced usage in the docs:
// https://github.com/reactjs/react-redux/blob/master/docs/api.md
const mapDispatchToProps = {
    signinUser,
};

export default connect(mapStateToProps, mapDispatchToProps)(SigninForm);

And then you can dispatch signinUser action using this.props.signinUser(youData) (remember to bind the method that uses this.props or use arrow functions with static class properties).
Let me know if that helps.

@iyn  I use your approach on redux-form 6.7 version and react-boilerplate, I got an error
Uncaught TypeError: Cannot read property 'props' of undefined
Seems it's come from react-boilerplate or "redux-form/immutable" when I tried on create-react-app and work well.
Do you have any solution?

Closing with bulk close of v5 issues. If this issue still requires action and/or also affects v6/7, please request a reopen with details or raise a new issue. v5 PR's are still welcomed.


Upgrade to Pyodide 0.23.4 (with Python 3.11) and compile dependencies

(@alexmojaki can you rebase this when you have a moment)

From sandbox/pyodide, I ran build_packages.sh and it ran to completion, building everything needed :+1:. I then tried running GRIST_SANDBOX_FLAVOR=pyodide yarn start and opening a document, but I got this error:
2023-07-31 18:03:50.301 - info: Sandbox stderr: [pyodide sandbox] [package] Loaded et_xmlfile, executing, asttokens, iso8601, lazy_object_proxy, chardet, pure_eval, python_dateutil, astroid, sortedcontainers, six, unittest_xml_reporting, stack_data, roman, wrapt, typing_extensions, openpyxl, friendly_traceback, phonenumberslite sandboxPid=692865, flavor=pyodide, command=undefined, entryPoint=(default), docId=smStzDu4B6G5AT4CmVxdua
2023-07-31 18:03:50.394 - info: Sandbox stderr: [pyodide error] PythonError: Traceback (most recent call last):
  File "/lib/python3.10/_pyodide/_base.py", line 460, in eval_code
    .run(globals, locals)
  File "/lib/python3.10/_pyodide/_base.py", line 306, in run
    coroutine = eval(self.code, globals, locals)
  File "<exec>", line 5, in <module>
  File "/grist/grist.py", line 8, in <module>
    from usertypes import Any, Text, Blob, Int, Bool, Date, DateTime, \
  File "/grist/usertypes.py", line 21, in <module>
    import six
ImportError: bad magic number in 'six': b'\xa7\r\r

I saw a pyodide version number in setup.sh that looked out of step with the rest of the PR, updating that and replacing _build/worker seemed to do the trick.
For the unrelated test failure - I made a series of changes to test/nbrowser/SelectBySummary.ts that could be worth considering for test/nbrowser/SelectByRefList.ts - can't actually say if any of them change anything, since I can't duplicate the failure, so I'm just whittling away at possibilities. The SelectBy tests have been flakey since the order of test file evaluation became less deterministic.
I'd like to run make save_packages to save the painstakingly built output, but I wonder if there needs to be some kind of overall version number in the path? Are any build files that happen to have the same name currently usable by grist-static in its current state?

I'd like to run make save_packages to save the painstakingly built output, but I wonder if there needs to be some kind of overall version number in the path? Are any build files that happen to have the same name currently usable by grist-static in its current state?

Just for clarity on this - pyodide is the default python engine for grist-electron these days. As a desktop app grist-electron gets build on a matrix of platforms, so building the wheels for it repeatedly would be a significant slowdown. So it is best if the wheels are cached. See e.g.:
https://github.com/gristlabs/grist-electron/blob/ee6e73cfe8a8464d84538c826ab3edcaa03f3c71/scripts/setup.sh#L170-L176
I think when the pyodide engine in grist-core is updated, we should probably assign it a version and cache material in a distinct path. Then grist-electron and grist-static can get updated on their own schedule.

I didn't realise the pyodide sandbox flavor was actually still being used!
I think grouping the packages by pyodide version makes sense.

I didn't realise the pyodide sandbox flavor was actually still being used!

It is a relatively new thing. I cobbled together the pyodide sandbox in order to have some kind of sandboxing option for Windows users of the desktop app. Then realized that it came close to making something like grist-static possible, so I started hacking on that. None of this was really planned, it was a rogue project.

I think grouping the packages by pyodide version makes sense.

Who should make that happen? Do you plan to do it in this PR? This PR works well for me now, the one remaining issue is the package layout. Currently if you follow the README in sandbox/pyodide, you'll end up getting packages for a different version from https://s3.amazonaws.com/grist-pynbox/pyodide/packages/

(The sporadically failing TypeChange.ntest test should be fixed on main now)

Rather than the pyodide version, let's just use a custom version number for this purpose to also account for things like changes in requirements. So e.g. we could start with s3://grist-pynbox/pyodide/packages/v2/ and then later change that to v3 etc.
Let's try to avoid accidentally deleting/replacing uploaded files if we forget to update the version number. Is there an easy alternative to aws s3 sync that fails if there's already files in that 'directory'? Otherwise, a low tech solution could be to remove save_packages from Makefile and explain what to do in the README so that people are more likely to do it carefully.
If you could take over from here I'd really appreciate that, bit overwhelmed atm

Rather than the pyodide version, let's just use a custom version number for this purpose to also account for things like changes in requirements. So e.g. we could start with s3://grist-pynbox/pyodide/packages/v2/ and then later change that to v3 etc.

Sounds good.

Let's try to avoid accidentally deleting/replacing uploaded files if we forget to update the version number. Is there an easy alternative to aws s3 sync that fails if there's already files in that 'directory'? Otherwise, a low tech solution could be to remove save_packages from Makefile and explain what to do in the README so that people are more likely to do it carefully.

There may be a flag, I can check. The set of people who can upload to grist-pynbox is very low though.