MAINT: optimize.basinhopping: fix acceptance of failed local search

Reference issue
Closes gh-7799
What does this implement/fix?
basinhopping does not consider the success message of minimize when it decides whether to accept a step. This can lead to incorrect results (e.g. gh-7799). This PR implements the solutions suggested in https://github.com/scipy/scipy/issues/7799#issuecomment-1286053309.
Additional information
I have not yet documented the new accept_test interface. It does not necessarily need to be public.
Besides fixing a bug, this PR also shows how we can change the callback interface in a backward-compatible way. This may be useful for many local and global optimizers, since we've discussed making callbacks more consistent by passing in only one parameter - and OptimizeResult.

Really? I don't see why. As you say, it is unambiguously a bug that leads to incorrect solutions. It's not intended or documented behavior, and there are no public interface changes here, so does it really need a post?

Fine by me. I just assumed out loud you would do this so I should not merge without that.
It's ready for me.

Yeah, I think it's ready. We'll send a post before the available signature is made public, though. Thanks!

CI failures are unrelated. The refguide_check issue is coming from sparse.

In it goes then. Thanks again Matt!


Implementing the IRequestClient interface properly

Someone forgot to add the default value.

yeah I think it used to be explicit. But that annoyed people using var


command to show snapshots by parent

Hi,
let say i've created a snapshot using
rustic -r rclone:testremote:cyberpanel.net backup /home/backup/cyberpanel.net/config.json --password "" --parent fb6f173a58e2e5f3e4e55471989092234d3d042a9ea693f25f04301c59ffdb5b

Now how can I see childs of fb6f173a58e2e5f3e4e55471989092234d3d042a9ea693f25f04301c59ffdb5b
thanks.

I'm still trying to figure out your use case where you need to find the parent.
It seems you want to have that config.json at hand when you restore the snapshot fb6f173a58e2e5f3e4e55471989092234d3d042a9ea693f25f04301c59ffdb5b, right?
I think a much better solution would be to simply backup that config.json together with all you've backuped into just one snapshot. #458 will allow you to do
rustic backup <YOUR_SOURCE> /home/backup/cyberpanel.net/config.json
You then can even independently restore both paths by:
rustic restore <SNAP>:<YOUR_SOURCE> <DESTINATION>
rustic restore <SNAP>:/home/backup/cyberpanel.net/config.json /path/to/restore/json/

Hope this is able to simplify your setting...

You understood the problem right, however, when I put two paths in backup command it create two seprate snapshots then I don't know the snapshot of the config one.
Actually each snapshot of database, data (files) need to have config of that specific time attached to it..

when I put two paths in backup command it create two seprate snapshots then I don't know the snapshot of the config one.

This is exactly what #458 changes. After this is merged, only 1 snapshot will be created.

wao, let me check

Closing this as I think #458 covers the use case.


Up arrow generates JS error

https://jsfiddle.net/urkaj76k/
Pressing Up arrow key, generates Uncaught TypeError: Cannot read property 'top' of undefined

I was able to reproduce this, here's the traceback
Uncaught TypeError: Cannot read property 'top' of undefined
(anonymous function) @ select2.full.js:1076
S2.define.Observable.invoke @ select2.full.js:614
S2.define.Observable.trigger @ select2.full.js:604
S2.define.Select2.trigger @ select2.full.js:5167
(anonymous function) @ select2.full.js:5100
S2.define.Observable.invoke @ select2.full.js:614
S2.define.Observable.trigger @ select2.full.js:604
S2.define.Select2.trigger @ select2.full.js:5167
(anonymous function) @ select2.full.js:5018
S2.define.Observable.invoke @ select2.full.js:614
S2.define.Observable.trigger @ select2.full.js:608
(anonymous function) @ select2.full.js:1820
jQuery.event.dispatch @ jquery-git.js:4979
jQuery.event.add.elemData.handle @ jquery-git.js:4659

The issue appears to be that hitting UP will trigger the highlighting routines to shift the highlight, but that can't be done because there are no options in the dropdown. This should only happen if there is nothing in the results box, which currently can only happen if there is an AJAX error. Otherwise it will display the normal "no results found" message.
I'm tempted to call this a duplicate of https://github.com/select2/select2/issues/3501.

Actually I noticed this when I was trying to make options appear for multiple select, but was passing Ajax delay and dataType parameters. So no Ajax call was made, but also no options displayed :) That link to JsFiddle is what I mean

This error still occurs in version 4.0.5.

Seems like it only happens in controls populated via AJAX, when no results are returned by a request (even a successful request).

Fixed in #5127.


IRIDA-Biohansel: Adding our own schema for other Species

We want to use Biohansel pipeline in IRIDA for Campy and more species. Is it possible to include schema for Campy?

Campy has high genetic diversity, so a cgMLST approach may be better than a SNP-based approach for this pathogen. That said, we are currently developing an automated schema-production tool, and we will explore its usefulness with more genetically diverse pathogens, such as Campy.  We will include links and information on the BioHansel GitHub page as new schemas and tools are available.  Thank you for the suggestion!

What about Listeria?

We have started a project to create subtyping schemas for some of the major clonal complexes of Listeria (CC1, CC2, and CC4).  We however expect to determine the clonal complex using MLST, prior to running these BioHansel schemas.


more utility functions and better docs for nested tuples

Done.

Wow, quick :) I meant to change entupleN to tupleN as well. What do you think?

Oh, I see. The reason I choice entuple is because entuple is a verb (a made up one), while tuple is a noun. However, after thinking about it more, I like tuple naming convention because it matches Tuple, except for case.

Done.

Thanks!


Fix: Improved Warranty Card UI for responsiveness and multi-language …

Proposed Changes

Fixes #9071
Adjusted the layout of the asset warranty card for improved responsiveness across various screen sizes
Added css to handle text overflow, so that text remains within card boundaries on smaller/medium screens
Added language support inside warranty card without overlapping text or icons

@ohcnetwork/care-fe-code-reviewers
Merge Checklist

[ ] Add specs that demonstrate bug fixes and verify responsiveness on different devices and screen sizes
[ ] Update product documentation with new responsiveness guidelines for warranty card layout
[ ] Ensure that UI text is stored in I18n files for improved localization support
[ ] Prepare screenshot or demo video showing the new layout and attach it to the issue for documentation purposes
[ ] Request for Peer Reviews from @ohcnetwork/care-fe-code-reviewers team
[ ] Complete QA testing to validate the layout on various devices and confirm text overflow handling works as expected

Summary by CodeRabbit
Release Notes

New Features

Enhanced localization with new Marathi and English strings for customer support and warranty details.
Introduction of a new utility function for string formatting in snake_case.

Improvements

Updated layout for asset management buttons for better usability.
Streamlined rendering logic for various components, improving performance and clarity.
Adjusted conditions for displaying sample type details in the patient components.

Bug Fixes

Ensured correct display of sample types based on updated conditions.

Styling Updates

Complete overhaul of CSS styles for a more cohesive and modern design across components.
Improved responsiveness and visual presentation for multiple UI elements.

Chores

Cleaned up code by removing unused components and optimizing imports.
Updated project file structure and configuration settings.

@AlgoFoe  Can you get the unnecessary file inclusions (like tsconfig.json as well as package.json) removed from the PR? Git checkout command should be useful.

@rithviknishad and @Jacobjeevan, apologies for the confusion! This was my first time contributing, and I encountered several merge conflicts that I couldn’t resolve easily. I’ve decided to close the current PR and will open a new one shortly with the required changes. Thank you for your understanding!


Merged main dev 1.25

This PR syncs the main branch with the dev-1.25 branch.

/retitle Sync main branch into dev-1.25

Commits 31b677f, 32f6b46, 0f506a1 were merged in PR https://github.com/kubernetes/website/pull/34817/
The author for PR https://github.com/kubernetes/website/pull/34817/ stated the following in this comment about the errors in those commits:

...

31b677f: The error occurred because the file content/ko/examples/pods/pod-with-affinity-anti-affinity.yaml is missing.

Resolved by the following commit fff1dcf

32f6b46: It was the 'tide' that complained there existed a merge conflict.
And that merge conflict is resolved in this PR.
0f506a1: It was the 'tide' that complained there existed a merge conflict.
And that merge conflict is resolved in this PR.

Currently GitHub UI is saying "This branch has no conflicts with the base branch", so it seems that there exists no merge conflict,
and merging this PR will not break the build, since the Netlify preview of this PR looks fine.

Errors are resolved in PR https://github.com/kubernetes/website/pull/34817/ which has 45 commits
/approve

/lgtm


Rewrite Lessons

Rewrite lessons for better flow and SEO.

It seems good enough as an initial draft. I need to add some custom videos. so much work left to do, so little time.


ci: fix regression in docker push.

I think this snafu came from moving to an array in #11005.
Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

@mattklein123 this can be merged once the DockerHub setup for the VRP repositories is done.

Created and setup permissions for:
https://hub.docker.com/repository/docker/envoyproxy/envoy-google-vrp
https://hub.docker.com/repository/docker/envoyproxy/envoy-google-vrp-dev
@htuch can you merge and monitor when you are ready?


Required "legal" content

There are some legal requirements, even for a personal website (sigh)...

[ ] Privacy / Datenschutz

Ref: https://dejure.org/gesetze/DSGVO

What: https://dejure.org/gesetze/DSGVO/12.html
Art. 13 defines, which information must be provided:

Name and means of contact (is a mail address sufficient?!)
Which information is stored/processed?
Why is that information stored/processed (most likely Art. 6 (1) f) "Berechtigtes Interesse"; requires explanation, what is that interest (providing, maintaining and improving the service)

[ ] Contact / Kontakt / Impressum

Ref: https://dejure.org/gesetze/TMG
Esp. §5 (1) / (2)

Resources (German)

https://www.ihk.de/wiesbaden/recht/rechtsberatung/internetrecht-und-werbung/internetauftritt-rechtliche-anforderungen-und-pflichten-1255572
https://www.ihk-muenchen.de/de/Service/Recht-und-Steuern/Internetrecht/Rechtssichere-Internetseite/
https://www.ratgeberrecht.eu/leistungen/muster-datenschutzerklaerung.html

Address Services
German law requires websites to have an actual contact address. I don't want to publish my private address.
Here's a list of possible services:

https://impressum-privatschutz.de/angebot
https://anschrift.net/pakete/
https://www.postflex.de/de/pakete-preise/
https://impressumservice.eu/


LED strips: solder and mount on bot

@AudraHagerman and Braeden (does he have a git account?) did this


Benchmarking: currencies and emergency pallets

Can you fork off master and add your changes to have fewer file changes? @chexware

Can you fork off master and add your changes to have fewer file changes? @chexware

Sure will do that !


ENH: Adding support of GridSearchCV for mne.decoding.LinearModel

Reference issue
Example: Fixes #7027 .
What does this implement/fix?
This PR adds the support of GridSearchCV for LinearModel. I also ran the decoding/tests/test_base.py and got the 3 passed.

@iamsc can you please add a new test in  https://github.com/mne-tools/mne-python/blob/master/mne/decoding/tests/test_base.py ? thx

@iamsc can you please add a new test in https://github.com/mne-tools/mne-python/blob/master/mne/decoding/tests/test_base.py ? thx

No problem~ I have modified some tests in test_base.py.
Because the original test_get_coef function in test_base.py only focused on the regression estimator tests, I added some new tests which considers some possible types of estimators, likes classification, regression, classification with GridSearchCV, regression with GridSearchCV.
Moreover, in test_linearmodel function, I also added the classification/regression with GridSearchCV tests.

@iamsc you have some flake8 errors. Run make pep or flake8 on your files to see what's wrong

@iamsc you have some flake8 errors. Run make pep or flake8 on your files to see what's wrong

Sorry for those errors. I have already fixed those errors on my files using make pep.
However, there are still some other errors from make pep, likes mne/tests/test_docstring_parameters.py. I just ignored this kind of errors because I have not modified those files in this PR.

tests should be as fast as possible. Can you report how long it takes to run now compared to before?

If it only sets cv as 2, the test duration will decrease 77.17 seconds compared to before.
========================================================================== slowest 20 test durations ===========================================================================
180.56s call     mne/decoding/tests/test_base.py::test_get_coef
3.36s setup    mne/decoding/tests/test_base.py::test_get_coef
0.50s call     mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.08s call     mne/decoding/tests/test_base.py::test_linearmodel
0.00s setup    mne/decoding/tests/test_base.py::test_linearmodel
0.00s setup    mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.00s teardown mne/decoding/tests/test_base.py::test_get_coef
0.00s teardown mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.00s teardown mne/decoding/tests/test_base.py::test_linearmodel

Results (184.80s):
       3 passed

If I remove 1000 from C list in parameter grids and set cv  as 2, the test duration will decrease to 15.92 seconds.
========================================================================== slowest 20 test durations ===========================================================================
11.61s call     mne/decoding/tests/test_base.py::test_get_coef
3.60s setup    mne/decoding/tests/test_base.py::test_get_coef
0.19s call     mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.03s call     mne/decoding/tests/test_base.py::test_linearmodel
0.00s setup    mne/decoding/tests/test_base.py::test_linearmodel
0.00s setup    mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.00s teardown mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.00s teardown mne/decoding/tests/test_base.py::test_get_coef
0.00s teardown mne/decoding/tests/test_base.py::test_linearmodel

Results (15.69s):
       3 passed

I will re-commit the second one later.

Even 11 sec is quite long for a test. How long is it in master? Ideally these changes wouldn't add more than 0.1 sec or so. We run a lot of tests, and a lot that do much more complex processing than this, so we need to keep test times to a minimum.
If you need help speeding it up let me know and I can look at tweaking the test to get the time down

Even 11 sec is quite long for a test. How long is it in master? Ideally these changes wouldn't add more than 0.1 sec or so. We run a lot of tests, and a lot that do much more complex processing than this, so we need to keep test times to a minimum.
If you need help speeding it up let me know and I can look at tweaking the test to get the time down

Here is the time duration results of master:
========================================================================== slowest 20 test durations ===========================================================================
3.59s setup    mne/decoding/tests/test_base.py::test_get_coef
0.70s call     mne/decoding/tests/test_base.py::test_get_coef
0.23s call     mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.01s call     mne/decoding/tests/test_base.py::test_linearmodel
0.00s setup    mne/decoding/tests/test_base.py::test_linearmodel
0.00s teardown mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.00s teardown mne/decoding/tests/test_base.py::test_get_coef
0.00s setup    mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.00s teardown mne/decoding/tests/test_base.py::test_linearmodel

Results (4.82s):
       3 passed

I also tried to remove 100 from C list further, the results are as follows:
========================================================================== slowest 20 test durations ===========================================================================
4.07s setup    mne/decoding/tests/test_base.py::test_get_coef
1.32s call     mne/decoding/tests/test_base.py::test_get_coef
0.21s call     mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.02s call     mne/decoding/tests/test_base.py::test_linearmodel
0.00s setup    mne/decoding/tests/test_base.py::test_linearmodel
0.00s teardown mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.00s setup    mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.00s teardown mne/decoding/tests/test_base.py::test_linearmodel
0.00s teardown mne/decoding/tests/test_base.py::test_get_coef

Results (6.03s):
       3 passed

It seems like to close to the time duration in master. I come up with some possible directions I can try with, such as reducing the testing sample size, removing some tests for the possible types of estimators, etc. @larsoner do you have other suggestions that I can also try with?

I would try those, plus reducing the number of samples and/or features.
If the regressors/estimators you are iterating over are sklearn estimators, you probably don't need to do more than one. We can trust them to adhere to their own API requirements, so testing a single one should work.

Thanks @larsoner for your suggestions. I have tweaked some tests, including removing some estimators, reducing the parameter space, and reducing the number of samples.
Here is the new time duration:
========================================================================== slowest 20 test durations ===========================================================================
3.22s setup    mne/decoding/tests/test_base.py::test_get_coef
0.79s call     mne/decoding/tests/test_base.py::test_get_coef
0.21s call     mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.02s call     mne/decoding/tests/test_base.py::test_linearmodel
0.00s setup    mne/decoding/tests/test_base.py::test_linearmodel
0.00s setup    mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.00s teardown mne/decoding/tests/test_base.py::test_cross_val_multiscore
0.00s teardown mne/decoding/tests/test_base.py::test_linearmodel
0.00s teardown mne/decoding/tests/test_base.py::test_get_coef

Results (4.43s):
       3 passed

OK~ No problem.

Thx @iamsc !

I’m happy to contribute to MNE and learn from you folks. Thanks @agramfort and @larsoner .
Sent with GitHawk

looking forward to your next PRs :)
thanks for contributing


nightly CI fails due to NetCDF compile error

julia 1.10

workaround: I removed nightly test from .github/workflow.yaml


feat: Upgrade builder

Upgrade builder version

Current dependencies on/for this PR:

main

PR #326   👈

This stack of pull requests is managed by Graphite.


dev: Added Nix Flake support

Enables Nix users to get the git version of waybar
Enables Nix users to develop waybar easily
Adds a fully reproducible development environment

The user only has to install Nix, no other depencencies
Automatic dev env on directory entry through .envrc

Just renamed .envrc to .envrc.sample :)

Thanks! Sorry, I didn't see the review before but thanks you for the merge!


Searching functionality in pivottable

Is there an in-built function to search for keywords which will return the specific rows in pivottable.
Does the filter option work for this option? If it does then can you give me an example.

No, there isn't such a feature, sorry!

On Dec 7, 2016, at 17:40, ridonkz<EMAIL_ADDRESS>wrote:
Is there an in-built function to search for keywords which will return the specific rows in pivottable.
Does the filter option work for this option? If it does then can you give me an example.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Proposal: (Period[T]) Periodic and similar methods returns iter.Seq[Time[T]] instead of channel

https://github.com/golang/go/issues/61897 がacceptedになりました。
これに伴い、コレクションを返すAPIではiter.Seqを返すことがおそらく一般的になっていくと思います。
例えばGo標準ライブラリのproposal https://github.com/golang/go/issues/53987#issuecomment-1945059803 は、最終的にiter.Seqを返すAPIとしてacceptされました。
同様に、synchroでコレクションを返すAPIをiter.Seqに対応させるプランはあるでしょうか？（もしあれば、実装することに興味があります）
具体的には以下のようなものです。
細かいところが十分考えられていないのですが、少し見ていただいた印象としてもしポジティブであればより具体的に考えたいと思っています。
Proposal
synchroではコレクションを返すメソッドとしてPeriod[T]などがunexportedな型periodical[T]を返しており、これの実体は<-chan Time[T]になっていると思います。これの代わりに、iter.Seqを返すようにするというProposalです。
func (Period[T]) Periodic() iter.Seq[Time[T]]

Edit: 最初aliasを使う形で書いていたのですが、言語仕様上できないことに気づき、修正しました。
メリット

https://github.com/golang/go/issues/61898 のようなiter.Seqを前提としたAPIと組み合わせられるようになること
将来的に標準的になりそうなAPIに合わせられること

実は具体的なユースケースが手元にあるわけではなく、これを提供することで大きいメリットがあるかどうかはわかっていません。
互換性などについてのノート
https://github.com/nobishino/synchro/commit/1fd88144f74d7a8deeb788cbd9e1dc2cf3279d72 でテストを書きましたが、少なくとも一部で後方互換性がありません。

もともとはperiodical型がchannelなので、channel型の変数に代入できるという性質(テストのProperty 1)があった。periodicalの型定義をiter.Seqに置き換えると、この代入はできなくなる。
もともとperiodical型がchannelなので、for ~ range文で直接使うこともできた(テストのProperty 2)。この性質はrange over funcが実装された後のGoバージョンでは維持される。
Sliceメソッドを削除する必要が生じる。

※Sliceメソッドを定義できるようにtype periodical[T TimeZone]  iter.Seq[Time[T]]を戻り値とした場合、戻り値の値をiter.Seq[Time[T]]型の変数(関数の引数も含む)にそのままでは代入できなくなる。（型変換をすればできると思われる）

Hello @nobishino !! Thank you for describing the proposal. I have indeed considered iterators in the past.
Regarding the proposal you have presented, honestly, I don't feel like the benefits outweigh the disruption to backward compatibility.
func (p Period[T]) Periodic(next func(Time[T]) Time[T]) periodical[T]

If there are benefits to implementing the iterator interface, perhaps we could provide an Iter() method similar to the Slice() method, so that we can enjoy the benefits you are proposing.
What do you think?

Thank you! I would add some more detail and options for my proposal.
First of all, my proposal is motivated not by specific use-case, but by my personal technical curiosity.
So feel free to decline for not having specific use-case 😸

honestly, I don't feel like the benefits outweigh the disruption to backward compatibility.

Thanks for feedback! Based on that, I came up with several options which keeps backward compatibility as follows.
Option 2, 2-2, and 3 are illustrated in my draft branch: https://github.com/nobishino/synchro/commits/wip-period-sequence-api
Option 1: Add no new API for iter.Seq
This is obvious and completely reasonable option 😃
pros:

No API Addition.

cons:

Not enjoying benefits which iter ecosystem would provide.

Option 2: Add Seq() method to periodical[T]
This corresponds to your Iter() method idea. (I wrote this as Seq accidentally, and don't have strong preference for either name.)
Sample implementation for this option is given here:
https://github.com/nobishino/synchro/commit/f3e54956f41868778e22549e56fd70d23bc14b00
Since iter package is not yet provided as standard library, I write the sample using my fake package github.com/nobishino/gocoro/iter.
pros:

Simple to implement
Add least new API (only 1 method to already existing type)

cons:

When break statement is used, which is translated to false return value from yield function, the goroutine associated with periodical instance is not terminated. (illustrated in the next commit's test: https://github.com/nobishino/synchro/commit/608b66973645e2420361d209771b60902bb27189)

And, I think users don't expect iter.Seq[Time] cause such resource leakage for break statement.

Option 2-2: Same as Option 2 but address goroutine termination
This is variant of Option 2, but addresses the goroutine termination issue.
If we keep backward compatibility, we would need somewhat awkward implementation like https://github.com/nobishino/synchro/commit/608b66973645e2420361d209771b60902bb27189
pros:

Add least new API (only 1 method to already existing type).
No goroutine leakage.

cons:

Implementation would be complex and awkward.

Option 3: Add new methods to Period[T] type which returns iter.Seq
Option 3 adds several methods to Period[T](not periodical[T]) which have same functionality to PeriodicXXX family but returns iter.Seq instead. This option needs following addition to Period[T]'s API:

func (p Period[T]) Sequence(next func(Time[T]) Time[T) iter.Seq[Time[T]]
func (p Period[T]) SequenceDuration(d time.Duration) iter.Seq[Time[T]]
func (p Period[T]) SequenceDate(years int, months int, days int) iter.Seq[Time[T]]
func (p Period[T]) SequenceAdvance(u1 Unit, u2 ...Unit) iter.Seq[Time[T]]
func (p Period[T]) SequenceISODuration(duration string) iter.Seq[Time[T]]

Illustrated in https://github.com/nobishino/synchro/commit/336c4742536bb602e4ba68d54b0f31c5a0eda18a
pros:

Simple to implement.
No goroutine leakage.

cons:

5 new public API needs to be added.

Summary
I have explained 4 options which keep backward compatibility. Comparing these, there seems several objectives we want to meet, but I couldn't find the way to meet all of these.

Conform to & enjoy benefits of iter ecosystem
Have least addition of public APIs
Have simple & readable implementation
Make sure no resource leakage is caused by natural usage

My personal preference is Option 3, which meets 1, 3, 4 but giving up 2.
If we think the benefit of 1 is not too huge, I would think Option 1 (not adding new feature at least for now) is good decision.

Thank you for the wonderful proposal of Pros and Cons, @nobishino. It has become clear to me how we can approach each of them.
The policy I support is as follows:

I don't want to increase the number of APIs that are currently unlikely to be used.

The reason is that having similar APIs can lead to confusion among users about which one to use.

I don't want to return types that depend on third-party packages.

This is because we would lose control if we depended solely on this package. There is a possibility of performing Breaking Changes when maintenance stops or when bugs occur that require fixes dependent on external factors. I want to avoid this as much as possible.

As for the direction, I think Option 2, 2-2 is the better for me.
Although it was mentioned that it might become complicated, I believe that by implementing it in this way, where all processing for iteration is enclosed in the Seq() method, it won't become complex. What do you think?
func (p periodical[T]) Seq() iter.Seq[Time[T]] {
	return func(yield func(Time[T]) bool) {
		for current := range p {
			if !yield(current) {
				break
			}
		}
		go func() {
			for current := range p {
				// Prevents leakage of the sending goroutine by reading
				// all channels sent to periodical[T].
			}
		}()
	}
}

I would submit a PR when iter.Seq is released(or about to be released).
Here is WIP branch: https://github.com/nobishino/synchro/commit/ce1f98f43494dc50974ffcf5a564fe646280551a
I will continue from this WIP when iter.Seq is ready to use.
(By the way, that PR would need to update go.mod to require Go1.23.0)

@nobishino I'm sorry for late response.
I updated go version in https://github.com/Code-Hex/synchro/pull/39


Fuzz testing

We should add fuzz testing to detect any inputs that cause the decoder to crash

I can help with that. I was holding it off because I wasn't sure if the decoder is ready for this kind of testing.


HOSTEDCP-1542: Implement Workload Identity in Azure for Data Plane Components

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes HOSTEDCP-1542
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/test verify
/test e2e-aks

/retest


Setup CI

It will be easy for Rust, but i am not sure about flutter/dart.

Ideally every commit to master would create a new Testflight or Google Play Console build for the flutter app

codemagic looks good for this (can even build the desktop versions as well if you'd like) https://flutterci.com/


[AutoDiff] Support direct init reference differentiation.

Support @differentiable function conversion for init references, in
addition to func references and literal closures. Minor usability improvement.
Resolves SR-12562.

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - b4fa7e00276cb5f7906b47c0892b4f984b60c541

Unrelated Linux failure.
@swift-ci Please test Linux

Build failed
Swift Test Linux Platform
Git Sha - b4fa7e00276cb5f7906b47c0892b4f984b60c541

@swift-ci Please test Linux


Applied fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

代码修正


Relative paths when importing Excel files

We need to use relative paths when importing resources:
For reference, from @jia-chenhua:

And for the relative path issue, now in the env.py, it reads the Excel xlsx file using a relative path './compiled_workbook_objects/Pathways to Net Zero - Simplified.xlsx'. This is fine for testing using the 'test_reference_environment_direct_deployment.py' because this script is located in the \netzerotc\environment\ folder. However, when running the training and evaluation scripts train.py and evaluate.py, these scripts are in \netzerotc\local_agent_training_and_evaluation\ , so currently in these 2 scripts, I had to manually add os.chdir("../environment/") before creating the environment env = gym.make("reference_environment_direct_deployment:reference-environment-direct-deployment-v0") (this will read and compile the Excel workbook) and add os.chdir("../local_agent_training_and_evaluation/") after it to switch back to training and evaluation scripts own directory. This approach is only an ad hoc solution, and John would like to use some package to get the absolute Git path and use this path inside the env.py. I tried the gitpython package and use import git  at the beginning, but the import git doesn't work if I don't have git executable installed, since I use a portable git GUI without git installed, so I didn't use the git executable. So please let me know if you have simpler solution without using the gitpython package but also able to get the absolute path so that the training and evaluation scripts can be run in their own folder without switching to other ones.

This will be fixed by https://github.com/rangl-labs/netzerotc/pull/34

We can rely on python itself to do this instead of adding more complexity.
Flip the problem and let the environment figure out its own location. You can rely on the in-built __file__ variable to do this:
p = Path(__file__)

# determine the relative path to the workbooks directory
workbooks = p.resolve().parent.parent / "compiled_workbook_objects"
sensitivities = p.resolve().parent.parent / "sensitivities"

while also needing to implement #36 and #5

I can see there's a revert commit here https://github.com/rangl-labs/netzerotc/pull/34/commits/17aa28bd11c0c5525826c4426dca83e50025f572
Let me know if there are still any issues. Apologies I should have consulted with you, and just assumed that this would be tolerable. Black is a de facto standard for python these days – so you will see resistance whenever it's not used. We can apply black once you've got your changes in.
I suggest that we create pull requests for each stream of work – at the moment we only have pull request #34.
It's perfectly okay to address multiple issues with one pull request.
At the moment if we look at #36 or #5, there is no clear way to see where the work is being done. We want to have a situation where we can click on an issue, then see a link to the relevant pull request that is implementing the content.

Hi @masonlr , sorry for the delay in response. I had very limited previous experience of using git/GitHub before (probably only the 3 very basic operations: pull, commit, push), so I didn't know it was so easy to revert a specific commit while keeping other commits retained or even untouched, especially in a nice git GUI (like https://github.com/gitextensions/gitextensions).
And yes, let's apply black formatter later when there is no significant change or further implementation is needed. In fact, the major complaint that I have with the black formatter is that, it blindly format everything without too much control over it, and for lines like Pathways2Net0ColumnInds = np.array(['P','Q','R','S','T','U','V','W','X','Y','Z','AA','AB','AC','AD','AE','AF','AG','AH','AI']) in the env.py, the black formatter will make every single string/character occupy one line, which is not only wasting the very limited code editor's space inside Spyder IDE, but also makes mouse scrolling navigation in code editor of Spyder IDE much more inconvenient/inefficient, unless I change my mouse scrolling's number of lines per notch of mouse wheel to a much larger number globally in my OS, which will affect my using of other software. So if there is some way to "protect" some lines of code to be not blindly formatted by black formatter, then I think I should be fine with it. But again, we can do that later.
Regarding the pull request, should we create another "fast development/implementation/issue fixing" branch based on the direct_action_on_deployment branch, and then frequently merge small or every single change to this direct_action_on_deployment branch? Or should we work on the direct_action_on_deployment branch, but frequently create merge request to merge the changes to the main/master branch? (Sorry, I'm still a newcomer to GitHub's branch management/pull requests, so apologies for not being able to respond to your request of creating more pull request earlier, while keeping pushing new commits during the course of implementing new things or fixing the issues).

it blindly formats everything without too much control over it

This is the main reason that black exists. It is opinionated.  😏

the black formatter will make every single string/character occupy one line

This is hinting that there could be higher-level issues with the setup. For example, it might be hinting that the array shouldn't be written in-line here and should be in a config variable elsewhere in the code, or read in from a config file. It might be hinting that variable names are too long. There are other benefits, for example, in terms of testing and interactive iteration, where you can comment out a single element in the array – this is not possible when it's in-line. Here, the black formatting is what's called "stable under refactoring" – it's designed so that the git diff statements are easy to read (which is important when collaborating), not necessarily to use the smallest number of editor lines.

Regarding the pull request

Branches represent units of work. Ideally these should be very limited in scope and remain open for less than one week. This means that branches should be short lived and the only reliable surviving branch is main. Branches are "cheap" in git, so there is no problem with having several branches open at one time – as long as they are short lived.

but frequently create merge request

Once you think it's in a good enough state, we need to merge direct_action_on_deployment into main and immediately delete direct_action_on_deployment. If there are more items that haven't been finished, capture them in an issue and start working on them on a new branch based on the newly updated main branch. Communicate what is going on using a new pull request.

Sorry, I'm still a newcomer to GitHub's branch

No worries. There are lots of different ways that projects do this, so it's not always clear.
One of the simplest explanations is here: https://guides.github.com/introduction/flow/


Add support for consuming typings in global scope

From (I think) TypeScript 2.1+ the recommended export formula for libraries which support UMD is to use the export as namespace structure. Without this, one cannot use the typed moment global variable. See this as a reference: https://github.com/Microsoft/TypeScript/wiki/What's-new-in-TypeScript#support-for-umd-module-definitions

Any movement on this?

closing as duplicate of #3880


Started bot programming

Please write what libraries did you installed
@Dmytrenko-Roman

Please write what libraries did you installed
Only aiogram?
@Dmytrenko-Roman

I installed only aiogram.

My review above is outdated because some lines have now other numbers, but problems still existed

Look at the linter problems

Outdated


docs: add link list of timezones php.net

Description
Add find the complete list of timezones supported by PHP.
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[ ] Conforms to style guide

Thank you @datamweb


Create visual representation of program data/models

Set up pycallgraph to generate image of data architecture to show in presentation and use as a visual aid for our development

http://pycallgraph.slowchop.com/en/master/

Currently blocked due to django.db.migrations.state.InvalidBasesError once runserver is back up, I can implement this

now getting Error: [Errno 2] No such file or directory: '/mnt/freegeek/bin/activate_this.py'


Player Lookup Leading To Not Found

Describe the bug
Attempting to lookup myself using my battlenet ID leads to a 404
To Reproduce
If applicable, steps to reproduce the behavior:

Go to https://overfast-api.tekrop.fr/players/Robert-12124

Expected behavior
To be able to see my stats since I can on the blizard page
https://overwatch.blizzard.com/en-us/search/?q=Robert#12124

Hello @relia1,
Thank you for the bug report. I can see the results for "Robert" on the Blizzard page, but your exact profile isn't displayed. This page is calling another URL to make the search, and this is the one I'm using in the API.
Here is the URL : https://overwatch.blizzard.com/en-us/search/account-by-name/Robert#12124/
If you search for your exact profile, you won't find it in the data :/
That's why the API is saying your profile can't be found. Did you make sure your profile privacy is set to "public" ?
You should have a "Career Profile Visibility" within the "Social" menu for that. You'll also need to quit the game after changing the option for the changes to be effective on Blizzard pages.
Let me know if it solves your issue 👍

Dang I had doubled checked visibility, but I have done it from a battlenet account level. Updating the visibility within overwatch allows me to query myself now. Thank you!


Like in #26 , 1.18.2's version 0.2.0 requires a non-existent version of Create.

Title. #26

Hi! The issue should be fixed in the latest release.
You can find it in:
Curseforge: https://www.curseforge.com/minecraft/mc-mods/createutilities/files/5228626
Modrinth: https://modrinth.com/mod/create-utilities/version/kV99Qqsh


free: make free text search better

Requires some polishing here and there. Feedback very welcome!

I also
suggest renaming bot.ts to main.ts


What is the goal of chai-spies?

The readme states up front that the primary purpose of chai-spies is to serve as an example of how to create a Chai plugin. This statement suggests that its role as a mocking library is secondary. It mentions that only the most basic of functionality is provided, and even goes so far as to recommend an alternative library if advanced functionality is desired.
Of course, just because those words were written x years ago doesn't mean they're true now, or that it's the way things should be going forward. However, as the Chai ecosystem grows and the number of maintainers increases, I think it's valuable to reach an understanding on what the goal of chai-spies is so that we're all of the right mindset when evaluating feature requests.
My opinion is that the originally stated goal and minimalistic scope of chai-spies should be strictly maintained, and that when it comes to users requesting advanced features, we should point them at sinon and chai-sinon. I think we do more good for the community overall by throwing our support behind these existing libraries rather than duplicating their efforts, and that chai-spies fulfills its own niche quite nicely as being super minimalistic.
With that said, I'll fall in line behind the popular opinion on this issue. Achieving clarity in the goal of chai-spies is more important to me than my opinion. But in that case I'd like to learn more about what the strengths of chai-spies are in comparison to sinon and sinon-chai, other than it being lightweight, so that we can work to maximize those strengths going forward.

@keithamus @meeber probably I can share my vision of chai spies:
Robust, easy to use library with nice chai integration

Few reasons why I don't like sinon to much terms with different methods (stub, spy, whatever), in order to use sinon you need to go through the whole docs and eventually you will not find answer to your question.
On the other hand chai-spies something intuitive, you dont need much docs. Just few methods. And then it's easy to guess like:
const spy = chai.spy()
const returnFive = chai.spy.returns(5) // so, you write what you need: `spy returns 5` I haven't seen more obvious way to do it in js frameworks
const array = []
chai.spy.on(array, 'push')
expect(array.push).not.to.have.been.called()

const interface = chai.spy.object({ run: null })
expect(interface.run).not.to.have.been.called()

Also I think the main goal of this ticket is to change README file to highlight this.
Does it make sense?

@meeber do you have any thoughts on this?

I think it's clear that some people prefer chai-spies over sinon-chai, and that the features being requested recently can be implemented without sacrificing the qualities that make them prefer chai-spies. So, more power to this plugin!


Support for reference counted items in nopython lists

I believe this is an old (almost ancient) issue that can now be closed. With the advent of the  numba.typed.List we can store reference  counted types such as Numpy arrays in it. I think this is what this feature was asking for. I will close this now, as I believe the functionality requested exists.


basic.vim contains Unicode dash

Not sure if intentional, basic.vim contains Unicode dash on line 3. If replaced with ASCII dash entire file would be ASCII.

Fixed in https://github.com/amix/vimrc/pull/720


Refactor enable_restricted_attackers

Depends on #3
Refactor team_permutation.enable_restricted_attackers() and create a global store for easier data management.
The store is a global variable defined as a module, that holds all the app data. This allows us to have all the needed global data in one place. Some changes will be made as it is not 100% how the app will look at the end of the refactoring process.
List of changes
Store

Creation of a global data store. A class was used instead of a data class due to the mutability of the values. The data store has to hold data being accessed from everywhere in the code base.
If a value is accessed only in a specific folder, create a local data store at the folder's location to avoid bloating the code.
Create classes for collections of data: Team (friendly and enemy/opponent), and Settings.

Enable restricted attackers

Delete the globals from the file and change them by their store values
No changes in the code's logic. Only a comment: It seems that a lot of manipulations done are matrices manipulation, in which Pandas and NumPy are good at. Pandas is easier to use, but NumPy is way faster (especially in big datasets).

Thank you for this and #3 ! Good idea about the store and using NumPy for matrix manipulation. The speedup could certainly be relevant.


[Feature][UI Next] Add workflow instance startup params

Purpose of the pull request

add workflow instance startup params

Brief change log

Releated issues
#7928

Codecov Report

Merging #8501 (aa00935) into dev (922283e) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #8501      +/-   ##
============================================
- Coverage     45.38%   45.37%   -0.02%
+ Complexity     4031     4029       -2
============================================
  Files           686      686
  Lines         26725    26725
  Branches       2870     2870
============================================
- Hits          12130    12126       -4
- Misses        13451    13453       +2
- Partials       1144     1146       +2

Impacted Files
Coverage Δ

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.70% <0.00%> (-2.82%)
:arrow_down:

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 922283e...aa00935. Read the comment docs.


Fix TypeDefinitionResult.label typo in LSIF spec

The included example below also has the missing Result:
{ id: 37, type: "vertex", label: "typeDefinitionResult", result: 7 }

Thanks!

Ignore my last comment. Not awake yet :-)

I can reopen if you want, closed it due to lack of feedback

No need. I have it open right now and will quickly fix it. Thanks for reminding.

Done!

Thank you!


Simpler custom component support

Right  now, the home page says that custom components can be provided by putting them into filters.py, sources.py, transforms.py, or views.py in the directory where you launch lumen.  That's great, but having so many files seems like overkill for most users, particularly if they are using multiple projects in different directories, where they will end up copying all those files between multiple project directories. My gut tells me we should just suggest they put things into a single file, e.g. custom.py, and save those other files for more obscure cases where people want to install extensions in some central location.
It might be better to make this more explicit as well, at least allowing a user to state explicitly that a given .py file (of any name) is to be executed before continuing: lumen serve --run custom.py dashboard.yml.  (If not --run, maybe --custom or --preload.) That way they can keep the file in a central location covering multiple projects, if desired, and indeed we may want to support running ~/.lumen/custom.py automatically for that reason (though that does have security implications and is less explicit).

That way they can keep the file in a central location covering multiple projects

Disgree with this, if they want to keep it in a central location they should make a package out of it and explicitly provide the import path. Having it in some global location will inevitably result in users forgetting to bundle up the file when they share the dashboard specification and result in a non-reproducible environment. So I will strongly argue for one of two approaches:

You provide one or more files which must live right alongside the dashboard specification. I agree that this does not have to be separate files for each type of component so I'm happy to standardize this into a single custom.py file but continuing to support separate files (i.e. filters.py, sources.py, transforms.py and views.py).

To reference any other external component users should supply the full import path to their custom package in the type field, e.g. type: my_custom_package.some_module.MyCustomSource.

1 sounds good, but I'm not sure how you imagine 2 to work with Lumen Builder. How would such components become available in the dropdown selectors?  That's the case I'm focusing on.

Sounds good. We'll need some good docs explaining these two approaches (app-focused and module-focused) and making it easy for people to get started defining such a module, including how to develop with it (e.g. pip install -e .).


⚠ PrivateHD has degraded performance

In 3ae64a8, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2184 ms

Resolved: PrivateHD performance has improved in 98260be.


Crash when unequipping weapons with Valve Index in pipboy menu

Having a crash every time when unequipping a weapon in pipboy menu (left controller trackpad click/right controller stick click in wrist mode, left trackpad click/right stick click/right trigger in projected mode) when using FRIK.
Unequipping armor does not produce this crash.
Tested with versions 45, 51 52 and 54.
No similar crashes with FRIK disabled.
Using the FO4VR Index Controller hack v1.1 with your index controller mapping for the game. There did not seem to be a difference which other mods were enabled. At minimum I only had UFO4P+VR fix, DLC VR Fixes, VR Tools and Buffout 4 enabled along with FRIK.
Additionally, the favorites/drop submenu in pipboy does not seem to work in wrist-mode.
When in projected mode, it opens with right trackpad click.
Without FRIK, the submenu opens with left grip in wrist mode.
Here is the MO2 modlist I had, savegame and windbg screenshot
FRIK_54_INDEX_CRASH.zip

thanks i will take a look.
that windbg output looks to be from some thread and probably not where the crash is.     any chance you can run with the crash logger from buffout vr and see if it says differently?

Thanks for the fast response, I updated the zip with the crashlog
Unfortunately, the Buffout4.log file from earlier was probably overwritten, but here are both buffout logs from the most recent crash
Buffout4.log
crash-2022-10-22-14-30-18.log

thanks!    i think this is a bit more helpful.
i saw someone else post a log with a similar stack and register content so that's good that may be a common crash i can fix here.    let me look into it and see if i can reproduce on my end.

ok i know why it's crashing but gotta figure out how the hell to fix it now.    hopefully i have a fix later

ok uploaded a new version with a fix.
Problem was when unequipping it kept a pointer valid for the weapon erquippment data which houses the muzzle flash.   however it wasn't a real object.    so i check that the virtual function table matches expected weapon data which should prevent this crash from happening

yeah it seems you had a binding problem.   the submenu works fine for me with my bindings.
to be honest i hate how we have to do bindings in this game.   it's not intuitive at all.    i might try to go look at if i can hook directly into the game to get better binding controls.
when i get a chance i'll post how i have my index set up but yeah sounds like you had some conflicts


MINOR: remove "gradle wrapper" from travis.yml

> Failed to apply plugin [class 'com.github.spotbugs.snom.SpotBugsBasePlugin']
   > Gradle version Gradle 5.1.1 is unsupported. Please use Gradle 5.6 or later.

com.github.spotbugs.snom.SpotBugsBasePlugin requires gradle 5.6+ but the gradle supported by travis is 4.0 or 5.1.1 (https://docs.travis-ci.com/user/reference/trusty/#gradle-version and https://docs.travis-ci.com/user/reference/xenial/)
However, we don't need to call gradle wrapper since gradlew already exists in our project.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ijuma Thanks for approving! Merge it to trunk. Will file another PR to handle travis error.


Add an example of the weak deduction theorem in use

Time: Sun, 24 Feb 2019 09:07:40 -0800 (PST)
From: "'Alexander van der Vekens' via Metamath"

... I would also like to see an example of the weak deduction theorem in  section 3.9.2 (page 93). Maybe ~ renegcl can be used/prepared for this.

I've added more text, and referred to renegcl as an example.  I didn't include the entire proof of renegcl; instead, I've tried to focus on the big picture.

Done.


”Search region” is not present in the page

Screenshots
Version
OS : WIN 10
Browser : Chrome
Tools:JAWS
Webchat Version : "4.3.1-master.98c662f"
Describe the bug
Screen Reader users will get impacted if “Search message” region is not present in the page
To Reproduce
Steps to reproduce the behavior:
Repro Steps:
Step 1: Enable Jaws  and open the above URL in latest Chrome browser .
Step 2: Navigate to the page using cursor mode(down arrow)
Step 3: Use "Insert + Ctr + R" to open region window.
Step 4: Observe and verify whether “search message”  region is present in the page using “R” key stroke
Expected behavior
"Search region” should be present in the page
Additional context

[Bug]

@maggi1129 thank you for filing this issue! I am waiting for a response from the accessibility team to see what browser(s) we should support JAWS in. I will update this issue when I hear back from them. :)

@maggi1129, thanks for your patience. I confirmed with the accessibility team that we want to support JAWS and Chrome. I will inform the team about this issue and get back to this once I have done some more research and have more information available.

@maggi1129 we suggest using the following supported screen reader technology. We do not officially support JAWS.
Narrator on MS Edge (non-chromium)
NVDA on Chrome, Firefox, MS Chromium Edge
VoiceOver on Safari


[CI] Check if tests are to be run for build and pyspark matrix jobs

What changes were proposed in this pull request?
This makes the CI aware when instances of matrix jobs build and pyspark do actually not have any changes and there do not run any tests. Then, uploading files can be skipped as well, allowing to enable #36413.
This also makes the fact visible that tests for a matrix job are actually not run:

Though the job itself is run, the test step is skipped. Before, you would have to open the test step and see no tests were run.
Ideally, the whole job should be skipped. But that would require defining the module sets into the precondition job.
Why are the changes needed?
All instances of matrix jobs build and pyspark are skipped if none of their respective modules have changes. When changes exists, all instances are run, but some instances then do not run any tests, as their sub-set of modules do not have changes.
Does this PR introduce any user-facing change?
No
How was this patch tested?
It does seem that this cannot be tested from a branch, because these changes invoke a changes in the root module, which kicks off all tests.

@HyukjinKwon do you agree that ideally, the subset of modules build and tested in matrix jobs should be defined in precondition job, where it can check each subset for changes and then configure the matrix strategy and skip respective jobs? Than all this magic happens in one place.

Yeah, I think ideally all has to be skipped properly at precondition, and your previous fix makes sense.

Yeah, would that need a very big change? If we can make the change surgically, that would be great.

I wouldn't call it surgically, more a rework :-/

This is the most surgically I could get. Individual matrix jobs cannot be skipped (which I would have preferred) because the job.<job-id>.if field cannot evaluate matrix, so there is no way to have individual conditions (e.g. sql being skipped entirely while core being tested).
If you are happy with it, I'll create a corresponding JIRA. If not, please feel free to close this.

I wouldn't call it surgically, more a rework :-/

Ah, now I got your point. So precondition defines the modules to build/test, and the following jobs actully test/build those modules (from precondition)   .... I think it sounds like it would be a great improvement.

Can one of the admins verify this patch?

Yes, the idea was to define the strategy matrix as JSON in precondition. GitHub gives this working example:
https://docs.github.com/en/actions/learn-github-actions/expressions#fromjson
Then, module sets would be defined once in one place. There, it could run is-changed.py for each of the module sets and add that to the JSON. Here is a sketch: https://docs.github.com/en/actions/learn-github-actions/expressions#fromjson
Ideally, individual jobs of the build and pyspark matrix then would be skipped as easily as this:
build:
  strategy:
    matrix: ${{ fromJSON( needs.precondition.outputs.spark-matrix ) }}
  if: matrix.run != 'false' && matrix.changed != 'false'

But this is not allowed, matrix does not work in the if clause: https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability


Installer corrupts BCD

Describe the bug
After creating an installer usb, I boot my NUC and it gets into the installer. After it does its thing it restarts however after that there are multiple entries in the bios boot menu and none of them are bootable. Neither Windows nor Installer usb. When usb is plugged all of the boot entries show Bootloader osx too. Only thing that stays working is the UEFI shell. Which I can use to boot into windows and clean up the bcd. I also tried the installer usb with boot menu installed. If I miss the 5 second countdown it restarts and same thing happens once again. No more bootable usb. I have done this 3 times now. I don't think I'm missing a detail but let me know if I do. Apparently someone had a similar issue over at osx86 forums but he was able to pass the installation.
Expected behavior
I expected to continue booting from the usb and complete the installation.
Environment:

10.14.4 on a VM
10.14.5
2.3.4 and 2.4

Additional context
I discovered a bad RAM module and took it out. However it seems to have changed nothing
Logs
install.log

Is this closed or it doesn’t need further help?

Solved. I tried flashing the BIOS once more after the removal of the faulty ram. Now it boots.


feat(cli): add hint for interruption when using "gas cp" to upload data

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 86.649%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
6373

Relevant Lines:
7355

💛  - Coveralls


Code generation for Okta Client methods

Resolves 297424

Handlebars templating ✅
Flake8 compliant ✅
methods and logic included ✅

Added ✅:

Resource clients for modularization
Base model classes
Binary handling

Need to work on 🛠:

Implementing Read-Only properties
Classes for Enums


Mock + Setuptools installation issues

Issues installing Mock seen in OSX and older versions of Ubuntu. Looks to be due to a bug in setuptools.
Copying pyparsing-2.1.10-py2.7.egg to /private/var/folders/b_/f18v0pvd6xq091flxcgl9fvm0000gn/T/easy_install-coTkZz/mock-2.0.0/.eggs

Installed /private/var/folders/b_/f18v0pvd6xq091flxcgl9fvm0000gn/T/easy_install-coTkZz/mock-2.0.0/.eggs/pyparsing-2.1.10-py2.7.egg
Marker evaluation failed, see the following error.  For more information see: http://docs.openstack.org/developer/pbr/compatibility.html#evaluate-marker
ERROR:root:Error parsing
Traceback (most recent call last):
  File "/private/var/folders/b_/f18v0pvd6xq091flxcgl9fvm0000gn/T/easy_install-coTkZz/mock-2.0.0/.eggs/pbr-1.10.0-py2.7.egg/pbr/core.py", line 111, in pbr
    attrs = util.cfg_to_args(path, dist.script_args)
  File "/private/var/folders/b_/f18v0pvd6xq091flxcgl9fvm0000gn/T/easy_install-coTkZz/mock-2.0.0/.eggs/pbr-1.10.0-py2.7.egg/pbr/util.py", line 248, in cfg_to_args
    kwargs = setup_cfg_to_setup_kwargs(config, script_args)
  File "/private/var/folders/b_/f18v0pvd6xq091flxcgl9fvm0000gn/T/easy_install-coTkZz/mock-2.0.0/.eggs/pbr-1.10.0-py2.7.egg/pbr/util.py", line 431, in setup_cfg_to_setup_kwargs
    if pkg_resources.evaluate_marker('(%s)' % env_marker):
  File "/Users/jesse/.virtualenvs/p2/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1481, in evaluate_marker
    return cls.interpret(parser.expr(text).totuple(1)[1])
  File "/Users/jesse/.virtualenvs/p2/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1515, in interpret
    return op(nodelist)
  File "/Users/jesse/.virtualenvs/p2/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1429, in atom
    return cls.interpret(nodelist[2])
  File "/Users/jesse/.virtualenvs/p2/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1515, in interpret
    return op(nodelist)
  File "/Users/jesse/.virtualenvs/p2/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1450, in comparison
    raise SyntaxError(msg)
SyntaxError: '<' operator not allowed in environment markers

seen here as well https://github.com/openaps/openaps/issues/95

work around in https://github.com/jesseward/plex-lastfm-scrobbler/commit/3404178e3f4f2efb3f24f837060ad83e3773d08f


[user]. reputed keyword yields misguiding error message

?- [user].
begin_of_file.
a.
Error: syntax error, operator expected '.', line 2, 'a.
'
   true.
?-

I cannot spot the syntax error.

Just in case, a programmer thinks it should/could be a predicate:
$ cat be.pl
begin_of_file.
b.
e.
end_of_file.

$ tpl
?- [be].
   true.
?- listing.
b.
e.
   true.
?-

$ gprolog
| ?- [be].
compiling ...

| ?- listing.
begin_of_file.  % unexpected
b.
e.
yes
| ?-

I guess gprolog gone wrong.
One more thing:
$ tpl
?- end_of_file.
uncaught exception: error(existence_error(procedure,end_of_file/0),end_of_file/0)
?-

This should trigger a "halt".

What is begin_of_file? It is just a regular name. Why is it 'reputed'?

SICStus:
| ?- [user].
% compiling user...
| begin_of_file.
|
% compiled user in module user, 100 msec 459424 bytes
yes
| ?- begin_of_file.
yes

And nothing else is expected.

The begin_of_file is a virtual term introduced by Logtalk 3.00.7 (released on September, 2015) for its term-expansion mechanism. SWI-Prolog copied it (without attribution) after I posted an example using it to its public forum. Before Logtalk added this term, there was already (as I found later) SICStus Prolog beginning_of_file virtual term also for term-expansion (introduced on version 4.2.1).

$ sicstus
SICStus 4.7.1 (x86_64-darwin-18.7.0): Fri Jan 21 19:45:28 CET 2022
Licensed to Paulo Moura
% consulting /Users/pmoura/.sicstusrc...
% consulted /Users/pmoura/.sicstusrc in module user, 4 msec 50272 bytes
| ?- [user].
% compiling user...
| beginning_of_file.
| a.
|
% compiled user in module user, 34 msec 434064 bytes
yes
| ?- beginning_of_file.
! Existence error in user:beginning_of_file/0
! procedure user:beginning_of_file/0 does not exist
! goal:  user:beginning_of_file
| ?-

Thanks for the illustration. So beginning_of_file. is not begin_of_file.

To enhance the discussion a bit:
It is not even a "directive"
$ cat be.pl
z.
begin_of_file.
a.
end_of_file.
m.

$ tpl
?- [be].
   true.
?- listing.
z.
a.
   true.
?-

$ cat be.pl
end_of_file.
The obvious purpose of this file is to show that the directive "end_of_file"
allows to write many things subsequently about the purpose of this file.
$

$ tpl
?- [be].
   true.
?- listing.
   true.

?- end_of_file. % fixed!
$

I guess "begin_of_file" flourish in obscurity.
(as long as it does not behave what its name suggests)

It's well documented:
https://logtalk.org/manuals/userman/expansion.html#virtual-source-file-terms-and-loading-context

@pmoura oh, I see, thank you.
Its time for me to enter the world of logtalk.
Be warned, I come sneaking up but handicapped.
(because I've learned the way of thinking object-oriented from "self", prototype-based)
https://en.wikipedia.org/wiki/Self_(programming_language)

Logtalk supports prototypes, which, given your experience with Self, should help. I suggest you start with:
https://learnxinyminutes.com/docs/logtalk/


24 hour format resets 24:00 to 00:00

Hi,
First of all thanks for the great work!
This is probably not an issue for date/time, but it is an issue for certain cases (in insurance for instance) where user needs to input 24:00 instead of 00:00. How is it possible to override the default hh:mm mask so that "24:00" is a valid input?

I also need an option to enter just time 24:00 (alias hh:mm), but I'm confused how to extend the inputmask.date.extensions.js to add new alias that will allow this without ruining default mask.
Can you please help?

I have the same issue. I need the option to allow times to max: 24:00.
In the documentation of datetime extension i found that inputFormat: HHH and max: 24 should work. But it only works if i use two inputs for Hours and Minutes.
I found someone having the same issue here:
https://stackoverflow.com/questions/52391659/how-to-define-hour-like-2400-and-dont-change-to-0000
https://jsfiddle.net/vy1jwuwn/50/
But no solution for this.
Please help

I also need an option to enter 24 in some situations. I confirm that at least with v5, HHH doesn't work.

@toxpal ,  @Jan-ipb,
In v5 try with "H2:MM"
https://jsfiddle.net/bq6ngrv3/2/

Alright, let me test on my won project...

Works fine for me

I need the user to enter from 00:00 to 24:00 but 23:59 is the max, I already try max: 25 and nothing, I'v tried this regex ^(((([0-1][0-9])|(2[0-3])):?[0-5][0-9])|(24:?00)), but doesn't work either. H2:00 not working too, is there a way I could use this regex? or any better solution?


Error: Type Ng2SearchPipeModule does not have 'ɵmod' property

I've got this error :
ERROR Error: Uncaught (in promise): Error: Type Ng2SearchPipeModule does not have 'ɵmod' property.
Even if I loaded the module correctelly (I guess):
import { NgModule } from '@angular/core';
import { CommonModule } from '@angular/common';
import { FormsModule } from '@angular/forms';

import { IonicModule } from '@ionic/angular';
import { Ng2SearchPipeModule } from 'ng2-search-filter';

import { HomePageRoutingModule } from './home-routing.module';

import { HomePage } from './home.page';

@NgModule({
    imports: [
        CommonModule,
        FormsModule,
        IonicModule,
        HomePageRoutingModule,
        Ng2SearchPipeModule,
    ],
    providers: [
    ],
    declarations: [
        HomePage,
    ],
})
export class HomePageModule {}

Any idea about this issue ?

Sorry I installed new packages and I guess that caused the error, after reopening the shell and serve the app, no errors appears. Sorry :)


SLING-5792, SLING-5868, SLING-5795

SLING-5792: API to manage Authentication Requirement
Changes

new interface 'AuthenticationRequirement'
implemented by SlingAuthenticator
additionally: annotations with helper classes in the impl package to improve readability

Notes
with the implementation in SlingAuthenticator the values in the 'props' map change from array of AuthenticationRequirementHolder to a Set, which IMO corresponds better to the PathBasedHolderCache, which at some point has changed from ArrayList to SortedSet... but that for sure requires a careful review (also from a performance PoV)
TODO

the original code synchronized on 'props' before updating the PathBasedHolderCache, which itself was synchronized. That looks troublesome to me and with the patch this is separated.
I would like to write some benchmarks to be able to compare performance of AuthenticationRequirement vs. the ServiceListener approach as well as the effect of moving from array to Set in the props-map. But: I couldn't find the right way of doing this in Apache Sling (see also SLING-5791 for a specific issue).

SLING-5795 and SLING-5868
Changes

new module 'org.apache.sling.auth.requirement' in the contrib/auth space
new public API 'LoginPathProvider'
implementation based on Jackrabbit Oak that allows to mark subtrees with the set of configured supported paths to require authentication including an optional login path.

TODO

currently snapshot dependency to 'org.apache.sling.auth.core' due to usage of 'AuthenticationRequirement'
repo-init that defines the service-user required for the default implementation
Oak index definition that prevents traversal for initial query

With the upcoming migration to git this repository will be deleted. If the pull request contains data that should be re-submitted I suggest that you save the changes locally and resubmit them after the migration, which will likely happen on Monday the 9th of October.


Add imageRect argument to initialAreaBuilder

issue #129

Update of the test code is https://github.com/chooyan-eng/crop_your_image/commit/48b6b203a4ac59e106dbe7457432839ac2352679 .


$parse gives lexer error parsing this "Ahsan's birthday"

Lexer Error: Unterminated quote at columns 295-303 ["Ahsan] in expression [{....,"title":"Ahsan].
where obj =
{.....,"title":"Ahsan's birthday"}

Version of Angular? Plunkr to reproduce? Expression should be string, not array.

I am not able to reproduce this with the given information, would it be possible to get a plunker that shows this issue?

After one week without any feedback, I am closing this issue. If you are still experiencing this issue, feel free to reopen it.


changes to linear region selection feature

[x] update feature event pick_info table for LinearRegionSelector
[x] update feature event pick_info table for LinearSelector
[x] refactor feature name LinearBoundsFeature -> LinearRegionSelectionFeature
[x] add more info to event pick_info
[x] make selection an abstract property in base and override in all subclasses

[x] rename bounds to selection for LinearRegionSelector

so many CI runs, will try to look into how limit the runs by having PRs in draft or something similar so that the CI only gets run when we are ab to try and merge!


Doesn't work with '-useLegacyAOT no'

I can only get this Library to work with standard compiling, when using the new quick compile with '-useLegacyAOT no'  gestures no longer work.
This is fine, but with large projects which can take up to 1 hour to compile, it becomes a problem.  Is there anyway to have this library work with the quick compile?

This seems to be broken again in AIR 16. I need to update an app for 64 Bit Support and this fix isn't working :(
Does anyone know of a fix for AIR 16 ?
Any help is appreciated.

@jonathonpitman as I said before, I can't test that. But there was another problem related to GestureState static initialization recently https://github.com/fljot/Gestouch/issues/71 which is solvable, but still.. maybe I should get rid of it.

@johnstejskal I summon you

Tried the for loop fix as well..   still doesn't work with -useLegacyAOT no   :(

@jonathonpitman ok as a first quickfix option I recommend you to try to replace const with var and create those in _initClass() method. If won't work – we need to move those static constants into different class.

in which file do I need to do this ?

GestureState we are talking about

You mean change for example
public static const POSSIBLE:GestureState = new cls("POSSIBLE") as GestureState;
to
public static var POSSIBLE:GestureState = new cls("POSSIBLE") as GestureState;
What do I put in the _initClass ?

@jonathonpitman yes, const to var, but then you put new ... into _initClass()

Can you be more specific on what to put in the _initClass ?  Sorry :(   I'll test this and post results. Hopefully it works

LIke
public static var POSSIBLE:GestureState;
then
POSSIBLE = new cls("POSSIBLE") as GestureState;
Like that ?

No errors ..  this is what I have changed... still doesnt work though.
package org.gestouch.core
{
import flash.utils.Dictionary;
import flash.errors.IllegalOperationError;
/**
 * @author Pavel fljot
 */
final public class GestureState
{

	private static var cls:Class = GestureState;
	public static var POSSIBLE:GestureState;
	public static var RECOGNIZED:GestureState;
	public static var BEGAN:GestureState;
	public static var CHANGED:GestureState;
	public static var ENDED:GestureState;
	public static var CANCELLED:GestureState;
	public static var FAILED:GestureState;

	private static var allStatesInitialized:Boolean;

	private var name:String;
	private var eventType:String;
	private var validTransitionStateMap:Dictionary = new Dictionary();

	{
		_initClass();
	}

	public function GestureState(name:String, isEndState:Boolean = false)
	{
		if (allStatesInitialized)
		{
			throw new IllegalOperationError("You cannot create gesture states." +
			"Use predefined constats like GestureState.RECOGNIZED");
		}

		this.name = "GestureState." + name;
		this.eventType = "gesture" + name.charAt(0).toUpperCase() + name.substr(1).toLowerCase();
		this._isEndState = isEndState;
	}

	private static function _initClass():void
	{

	POSSIBLE = new cls("POSSIBLE") as GestureState;
	RECOGNIZED = new cls("RECOGNIZED", true) as GestureState;
	BEGAN = new cls("BEGAN") as GestureState;
	CHANGED = new cls("CHANGED") as GestureState;
	ENDED = new cls("ENDED", true) as GestureState;
	CANCELLED = new cls("CANCELLED", true) as GestureState;
	FAILED = new cls("FAILED", true) as GestureState;

		POSSIBLE.setValidNextStates(RECOGNIZED, BEGAN, FAILED);
		RECOGNIZED.setValidNextStates(POSSIBLE);
		BEGAN.setValidNextStates(CHANGED, ENDED, CANCELLED);
		CHANGED.setValidNextStates(CHANGED, ENDED, CANCELLED);
		ENDED.setValidNextStates(POSSIBLE);
		FAILED.setValidNextStates(POSSIBLE);
		CANCELLED.setValidNextStates(POSSIBLE);

		allStatesInitialized = true;
	}

	public function toString():String
	{
		return name;
	}

	private function setValidNextStates(...states):void
	{
		for each (var state:GestureState in states)
		{
			validTransitionStateMap[state] = true;
		}
	}

	gestouch_internal function toEventType():String
	{
		return eventType;
	}

	gestouch_internal function canTransitionTo(state:GestureState):Boolean
	{
		return (state in validTransitionStateMap);
	}

	private var _isEndState:Boolean = false;
	gestouch_internal function get isEndState():Boolean
	{
		return _isEndState;
	}
}

}

What is "doesn't work" exactly? Is it the same issues as originally that constants are somehow all equal? Or what? Does _initClass() method even executed?
Try inlining static initializator (_initClass()) (see example below).
If you're short in time and need a really quickfix, try to move all constants into another class, let's say GestureStates (note the trailing s) or GestureStateEnum:
final public class GestureStates
{
    public static const POSSIBLE:GestureState = new GestureState("POSSIBLE");
    ...
    //do the static initialization method
    //or even try inline it like this
    {
        POSSIBLE.setValidNextStates(RECOGNIZED, BEGAN, FAILED);
    }
}

Put some effort, it's just a few calls! Cmon people, I don't have any profiles to test myself.

What's not working for me is that it becomes unresponsive. No touch detected.  There are no errors though.
I'm not so advanced sorry.

I am really confused here..  sorry ;(

Something crashes the whole app .. nothing responds once Gestouch is initialized. ... Strange that no errors are thrown though.

Well you have to add some logs to understand where it don't work, right?

I have put in trace statements.  I can see that the _init function is called. So it is getting that far.

So, are the gesture states (constants) initialized properly?

Weird... Everything is working with the new public release of AIR 16

And this is why I'm leaving Flash platform...

to make matters worse...  Now everything is working great in my app .. I submitted it and Apple rejected it instantly.
Invalid Binary Error
Minimum OS Version Mismatch - The minimum OS version (LC_VERSION_MIN_IPHONEOS) in the binary ('6.0') for architecture ('armv7') differs from the MinimumOSVersion ('7.0') in the Info.plist.
Ughhhh! .. It's really tooo bad. I love making apps in AIR .. it's so easy to make cross platform apps.


After using slice_assign, gradient descent cannot track the model parameters

I found that after using slice_assign in the loss function, gradient descent cannot track the model parameters. I believe this is the main reason why the loss becomes NaN after the first iteration when I apply my implementation of CTC loss to the CRNN model.
pub fn forward(&self, input: Tensor<B, 3>) -> Tensor<B, 1> {
    let device = input.device();
    let [d1, d2, d3] = input.dims();

    let input2 = Tensor::empty(input.shape(), &device);
    input2
        .clone()
        .slice_assign([0..d1, 0..d2, 0..d3], input.clone());

    input2.mean()
}

The actual reason for my implementation of CTC loss becoming NaN after iterations is that the logarithm of zero is taken, not due to slice_assign. Now, I am not certain if there is a bug in slice_assign... perhaps more investigation is needed.

@nathanielsimard  I'm trying to train a CRNN model from scratch, but after a day of training, there's still no sign of convergence in the model. Then I noticed that only the parameters of the last layer were being updated. Here is the minimal reproducible example:
use burn::{
    backend::{ndarray::NdArrayDevice, Autodiff, NdArray},
    module::Module,
    nn::{Linear, LinearConfig, Lstm, LstmConfig},
    optim::{AdamConfig, GradientsParams, Optimizer},
    record::{FullPrecisionSettings, PrettyJsonFileRecorder},
    tensor::{
        backend::{AutodiffBackend, Backend},
        Tensor,
    },
};

fn main() {
    run::<Autodiff<NdArray>>(NdArrayDevice::Cpu);
}

fn run<B: AutodiffBackend>(device: B::Device) {
    let mut model = Model::<B>::new(&device);
    let mut optim = AdamConfig::new().init();
    let pfr = PrettyJsonFileRecorder::<FullPrecisionSettings>::new();

    for iteration in 0..51 {
        let input = Tensor::random(
            [2, 10, 5],
            burn::tensor::Distribution::Uniform(-1.0, 1.0),
            &device,
        );
        let output = model.forward(input);
        let loss = output.mean();

        println!(
            "[Train - Iteration {}] Loss {:.5}",
            iteration,
            loss.clone().into_scalar()
        );

        let grads = loss.backward();
        let grads = GradientsParams::from_grads(grads, &model);

        model = optim.step(0.001, model, grads);

        if iteration % 10 == 0 {
            model
                .clone()
                .lstm
                .save_file(format!("./lstm-{:02}", iteration), &pfr)
                .unwrap();
            model
                .clone()
                .linear
                .save_file(format!("./linear-{:02}", iteration), &pfr)
                .unwrap();
        }
    }
}

#[derive(Module, Debug)]
pub struct Model<B: Backend> {
    lstm: Lstm<B>,
    linear: Linear<B>,
}

impl<B: Backend> Model<B> {
    pub fn new(device: &B::Device) -> Self {
        Self {
            lstm: LstmConfig::new(5, 10, true).init(device),
            linear: LinearConfig::new(10, 20).init(device),
        }
    }

    pub fn forward(&self, input: Tensor<B, 3>) -> Tensor<B, 2> {
        let (_, x) = self.lstm.forward(input, None);
        let [batch_size, seq_length, d_hidden] = x.dims();
        let x = x.reshape([batch_size * seq_length, d_hidden]);
        let x = self.linear.forward(x);

        x
    }
}

After some investigation, I believe this is due to the use of slice_assign in the implementation of LSTM. After replacing it with Tensor::cat instead of Tensor::slice_assign, the parameters of LSTM can be updated correctly.
pub fn forward(
    &self,
    batched_input: Tensor<B, 3>,
    state: Option<(Tensor<B, 2>, Tensor<B, 2>)>,
) -> (Tensor<B, 3>, Tensor<B, 3>) {
    let [batch_size, seq_length, _] = batched_input.shape().dims;
    let device = &batched_input.device();

    let (mut cell_state, mut hidden_state) = match state {
        Some((cell_state, hidden_state)) => (cell_state, hidden_state),
        None => (
            Tensor::zeros([batch_size, self.d_hidden], device),
            Tensor::zeros([batch_size, self.d_hidden], device),
        ),
    };

    let mut batched_cell_state_vec = Vec::with_capacity(seq_length);
    let mut batched_hidden_state_vec = Vec::with_capacity(seq_length);

    for input_t in batched_input.iter_dim(1) {
        let input_t = input_t.squeeze(1);
        // f(orget)g(ate) tensors
        let biased_fg_input_sum = self.gate_product(&input_t, &hidden_state, &self.forget_gate);
        let forget_values = activation::sigmoid(biased_fg_input_sum); // to multiply with cell state

        // i(nput)g(ate) tensors
        let biased_ig_input_sum = self.gate_product(&input_t, &hidden_state, &self.input_gate);
        let add_values = activation::sigmoid(biased_ig_input_sum);

        // o(output)g(ate) tensors
        let biased_og_input_sum = self.gate_product(&input_t, &hidden_state, &self.output_gate);
        let output_values = activation::sigmoid(biased_og_input_sum);

        // c(ell)g(ate) tensors
        let biased_cg_input_sum = self.gate_product(&input_t, &hidden_state, &self.cell_gate);
        let candidate_cell_values = biased_cg_input_sum.tanh();

        cell_state = forget_values * cell_state.clone() + add_values * candidate_cell_values;
        hidden_state = output_values * cell_state.clone().tanh();

        let unsqueezed_shape = [cell_state.shape().dims[0], 1, cell_state.shape().dims[1]];

        let unsqueezed_cell_state = cell_state.clone().reshape(unsqueezed_shape);
        let unsqueezed_hidden_state = hidden_state.clone().reshape(unsqueezed_shape);

        // store the state for this timestep
        batched_cell_state_vec.push(unsqueezed_cell_state);
        batched_hidden_state_vec.push(unsqueezed_hidden_state);
    }

    let batched_cell_state = Tensor::cat(batched_cell_state_vec, 1);
    let batched_hidden_state = Tensor::cat(batched_hidden_state_vec, 1);

    (batched_cell_state, batched_hidden_state)
}

Thanks @wcshds for the example with LSTM, it will help us in fixing this.

I found that after using slice_assign in the loss function, gradient descent cannot track the model parameters. I believe this is the main reason why the loss becomes NaN after the first iteration when I apply my implementation of CTC loss to the CRNN model.
pub fn forward(&self, input: Tensor<B, 3>) -> Tensor<B, 1> {
    let device = input.device();
    let [d1, d2, d3] = input.dims();

    let input2 = Tensor::empty(input.shape(), &device);
    input2
        .clone()
        .slice_assign([0..d1, 0..d2, 0..d3], input.clone());

    input2.mean()
}

I found the actual problem in this code. Slide assign doesn't actually mutate any data in input2, it returns a new tensor handle that should be used afterward:
pub fn forward(&self, input: Tensor<B, 3>) -> Tensor<B, 1> {
    let device = input.device();
    let [d1, d2, d3] = input.dims();

    let input2 = Tensor::empty(input.shape(), &device);
    let x = input2.slice_assign([0..d1, 0..d2, 0..d3], input);

    x.mean()
}

There are no mutable operation in the tensor API, every operation returns the result that should be used!

There are no mutable operation in the tensor API, every operation returns the result that should be used!

Thank you very much for pointing out the actual problem! I often forget that.

@wcshds I added some tests comparing slice_assign and cat backwards in #1146 but I can't find a bug


Question about stored mp3

Domoticz is able to play stored mp3 files on the gateway: https://www.domoticz.com/wiki/Xiaomi_Gateway_(Aqara)
Is this something that can be accomplished with miio?

according to the api spec, udp command:
{"cmd":"write","model":"gateway","sid":"mysid","short_id":0,"data":"{\"mid\":10005}" }
should play mp3 nr5, any idea how is can send this with miio?

getting there
sending another command to the ip of the gateway onport 9898:
{ "cmd": "write" , "model": "gateway", "sid": "mysid", "short_id": 0, "data": "{" rg b ":<PHONE_NUMBER>}"}
results in error no key


Fix matchAnnotation() function

Fix #35

The _fileUriFromPackageUri() has an assert that checks the scheme of the source library for a specific value, but it works fine when invoked by DartEditor.
Now I'm not sure if this is really a bug, or if I'm not doing it right...

Good try. I need to approach this another way. Stay tuned.


Snow stuffs

Replacement for ancient issue #487 fleshed out a bit more since we have more options now.

[ ] Add one or more sizes of snow blocks made of slabs (1/8th, 1/4th..) that can be placed. Maybe a full snow block too that doesn't have a dirt side showing (pure snow)
[ ] Ability to / example of using them during world gen to place on top of snow-covered blocks (add to the TutorialWorldGeneration repo/guide?)
[ ] Maybe experiment with making the smaller slabs penetrable.  Make it risky to climb in snow! Add a chance the player will fall if climbing blocks covered in snow, causing a tiny bit of damage if so
[ ] Find a way to create snowshoes that make pure snow blocks of any height no longer penetrable (so a player can walk on top of them - this might be tricky)
[x] Enhance the WeatherManager module to add snowy weather that deposits snow slabs (I think it has rain, just no graphic for it?)
[ ] Add logic so that if for whatever reason a snow slab grows to a full block switch it to an actual non-penetrable full snow block. And/or maybe turn heavy enough snow build-up into ice blocks.
[ ] Maybe allow pure snow slabs/blocks to be "scooped" for modules that have buckets (could then be heated to get water)
[ ] Wax philosophically about the potential of other slab-based materials that could work similarly (pseudo-liquids like tar?)

Some of these items are probably appropriate for the general backlog (stuff we could do, but no real priority) but we do have snow blocks and it is a pretty basic concept so we should further the cause of the white walkers at least a little before archiving the rest. Winter is coming.

Hello, thinking about implementing this block, anything i should know before getting stuck with it haha 😄

A good starting point would be the tutorial on world generation. If you haven't already, do have a look at our wiki. In particular the sections block attributes, potentially also on block shapes.
That said about world generation, the other issues are more related to gameplay. Josharias Survival is one of the game modes that also deal with affecting the player. There are other module which use our Entity Component System for buffs, item equipments, etc.
Overall, it should be fairly easy to get started on this one. How detailed this will get is up to you ;-)

Hi is someone working on this issue? I believe I saw a full snow block pull request but I was unsure if anything else has also been completed.

Hi! Just to add to the conversation there do appear to be some snowy areas here and there, using the snow block. I think it'd be useful to make them their own separate biome, rather than just part of the biome they're encompassed in. Also, I'm not sure if it's been said but plants crop up in these biomes. I think they should be removed to add to the snowiness!
I have a screenshot of this behavior here:

Heya @rchau0623 :-)
There actually is a snow biome in the main world generator, but I'm not sure how hard it is to find one. It even used to have ice blocks in the water ages ago. What you usually see is snow blocks over a certain height, I think that was added back when we included unlimited height. Yeah those could use improvement and the flora generator needs to know not to put regular plants there.

@Cervator Ohhh I see! That's awesome! Sorry for the confusion

is this still open?can i work on  it?

Hello ! we are a team of 7 students who would like to work on this issue. Thus, we would like to know if this issue is still open and if  we can work on it.

hey there @Ewwweee
generally all open issues are technically open, so yes you could work on it.
however, there might be work items that would actually help us more than this one tbh...
for instance, you could have a look at https://terasology.org/contribute/#hot-topics for currently ongoing workstreams.
we currently don't have capacity for supporting you with other endeavors (especially contributions to in-game content) much, simply because we're a very small group of maintainers right now and need to focus on stabilizing the engine before we can get back to content considerations.
if you are still set on working on content, though, in particular weather-related, then I'd like to encourage you to take the idea of https://github.com/Terasology/ClimateConditions/pull/18 and bring it to completion as that's a requirement we need to get taken care of before any other weather-related content. in the past we already had to disable weather-related content because it's not usable as long as the underlying maps are based on noise rather than the generated world.
also, please feel free to come talk to us on our Discord, that's more suitable for discussing where to contribute than individual github issues :wink:

Oh hello 7 year old issue! This brings back memories.
At least after 7 years we do have the depositing of snow slabs happening in the WeatherManager, so hooray, checked one box! However that's also somewhat representative of how fast some areas of the project move I'm afraid ... 😅 And who knows if that still works in the WeatherManager.
As noted you are free to play around where you feel like it, make something your own, but help with priority issues would be appreciated, and we can better support those. And yeah definitely get on Discord, easy to chat and give more advice there 👍


SUBMARINE-752. Drop profile spark 2.3

What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - https://submarine.apache.org/contribution/contributions.html
We use Apache Spark 2.4.x as default and drop profile spark-2.3 for future-proofing updating
the Spark 2.4 is LTS and it's better for us to maintain. The functionality for spark 2.3 and earlier is still kept
What type of PR is it?
Improvement
Todos

[ ] - Task

What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/SUBMARINE-752

How should this be tested?

First time? Setup Travis CI as described on https://submarine.apache.org/contribution/contributions.html#continuous-integration
Strongly recommended: add automated unit tests for any new or changed behavior
Outline any manual steps to test the PR here.

PASSING existing tests
Screenshots (if appropriate)
Questions:

Does the licenses files need update? Yes/No
Is there breaking changes for older versions? Yes/No
Does this needs documentation? Yes/No

cc @jiwq @xunliu  thanks


[287] fix undefined window

Deployed to https://beghp.github.io/gh-pages-rc-6- [x] package.json:version has been updated with npm version patch (or major/minor as appropriate)- [ ] @brainhubeu/react-carousel version has been updated in docs-www/package.json to the same which is in package.json:version

I'm in a Gatsby environment as well and introducing window to the global state in this way will actually conflict with other plugins that check to see if window is defined.
I believe a better way would be to truly check to see if window is defined in the component itself. For example, in Carousel.js componentDidMount:
if (typeof window !== "undefined") {
    // setting size of a carousel in state
    window.addEventListener('resize', this.onResize);
    this.onResize();

    // setting size of a carousel in state based on styling
    window.addEventListener('load', this.onResize);

    // setting autoplay interval
    this.resetInterval();
}

@ebello
Thanks for your comment.
It looks that the best way for now is using Next.js and rendering Carousel on the client side.
In future maybe we'll provide server-side working - I guess the best way would be to configure webpack to generate two bundles: one for client side and another for server side.

@ebello
please see https://github.com/brainhubeu/react-carousel/pull/301

For anyone looking for quick workaround, that's what I have done to use react-carousel with SSR, without Next.js:

Remove all regular import Carousel, { Dots } from "@brainhubeu/react-carousel".
Remove styles import from js (i had to do this as it also caused crash while compiling), import these styles inside css/scss/less instead
Make sure your component contains similar checks in constructor and render:

function isBrowser() {
  return typeof window !== "undefined";
}

class MySuperSlider extends React.Component {
  constructor(props) {
    super(props);

    if (isBrowser()) {
      this.Carousel = require("@brainhubeu/react-carousel").default;
      this.Dots = require("@brainhubeu/react-carousel").Dots;
    }
  }

  render() {
    if (!isBrowser()) {
      return null;
    }

    const { Carousel, Dots } = this.

    // Do stuff using <Carousel> and <Dots>
    // just like you would with regular import
  }
}

I do realize that this solution is far from elegant, but it gets the job done, and is easier than migrating whole project to Next.js :)

Simple approach that's inline with how things were working prior to the webpack v4 upgrade on PR #344


"mdMenuTriggerFor" -> "md-menu-trigger-for"

looks like property "mdMenuTriggerFor" should be "md-menu-trigger-for"

signing completed

No it shouldn't, all of the Material properties were switched to camelCase for consistency.

but I have error now:
"Can't bind to 'mdMenuTriggerFor' since it isn't a known property of 'button'. ("<md-toolbar [color]="primary">
<button md-icon-button [ERROR ->][mdMenuTriggerFor]="menu">"
with "md-menu-trigger-for" I have no compilation errors, I do something wrong?

The renamed properties haven't been released yet. You should use md-menu-trigger-for until the next release.

OK
it is a pity that Marty brought the documentation without the code


Include problems in GET /transactions/{id}/results

Depends on https://github.com/RelationalAI/relationalai-infra/pull/2334.
Including problems when fetching results. This will be deprecated when problems are included in relations and not an independent arrow file.
I'm not sure if this is the best way to represent the output, but I'm open to ideas!

Changed the representation here https://github.com/RelationalAI/rai-sdk-python/pull/78/ to be similar to problems/results short-path sync output, now it looks like this:


Improve AntreaProxy route syncing on Windows

This PR fixes the following issues:

AntreaAgent logs "Failed to sync route" when attempting to sync route entries
every time.
AntreaAgent logs "Failed to install route for Service CIDR" err="failed to
delete stale Service CIDR route" during startup.

For the first issue, previously, to recover the connected route of antrea-gw0
(assuming the IP address is <IP_ADDRESS>/24) that may have been deleted by mistake,
a route with a destination <IP_ADDRESS>/24 and gateway <IP_ADDRESS> was periodically
synced. However, this caused an error because an existing active route with the
same destination but a different gateway <IP_ADDRESS> should have already been
automatically installed when antrea-gw0 was created. To address this issue, this
PR changes the gateway of the recover route from <IP_ADDRESS> to <IP_ADDRESS>, which
matches the existing installed route. This ensures that the periodic sync will
not cause any errors.
For the second issue, previously, when syncing the second ClusterIP, the stale
route entry installed for the first ClusterIP is added to the stale routes twice.
This results in the error log.
Signed-off-by: Hongliang Liu<EMAIL_ADDRESS>

/test-windows-all

/test-windows-all

/test-all
/test-windows-all

Should the description be updated?

Should the description be updated?

I'll check the description.

Should the description be updated?

Updated

/test-windows-all

/test-all
/test-windows-all

/test-e2e

/test-e2e

/test-windows-proxyall-e2e

/test-windows-proxyall-e2e

I saw that the failed case in windows-proxyall-e2e is the well-known flaky test TestNodePortLocal/testNPLChangePortRangeAgentRestart. Do we still need any tests for this PR? @tnqn

I saw that the failed case in windows-proxyall-e2e is the well-known flaky test TestNodePortLocal/testNPLChangePortRangeAgentRestart. Do we still need any tests for this PR? @tnqn

It can be ignored

Aren't the issues introduced in release-1.12? Do them really need backport?


Dongsinlooi

added timer and cache
take it if u wan

Good improvement, but I still need some time to review your code.
Btw cache folder doesn't need to be pushed to github, you can add this folder in gitignore file in the mean time.
Ex:

An useful doc about how to add cache folder to gitignore:
https://git-scm.com/docs/gitignore#:~:text=For example%2C a pattern doc/frotz/ matches doc/frotz directory%2C but not a/doc/frotz directory%3B however frotz/ matches frotz and a/frotz that is a directory (all paths are relative from the .gitignore file).

[heart]         Dong Sin Looi reacted to your message:

From: zhenkaisitecore @.>
Sent: Thursday, September 14, 2023 1:57:01 AM
To: zhenkaisitecore/sitecore-codex @.>
Cc: Dong Sin Looi @.>; Author @.>
Subject: Re: [zhenkaisitecore/sitecore-codex] Dongsinlooi (PR #9)
Good improvement, but I still need some time to review your code.
Btw cache folder doesn't need to be pushed to github, you can add this folder in gitignore file in the mean time.
Ex:
[image]https://user-images.githubusercontent.com/75464455/267829297-e9219956-a88c-4c39-b223-71a3cb2f1c14.png
An useful doc about how to add cache folder to gitignore:
https://git-scm.com/docs/gitignore#:~:text=For example%2C a pattern doc/frotz/ matches doc/frotz directory%2C but not a/doc/frotz directory%3B however frotz/ matches frotz and a/frotz that is a directory (all paths are relative from the .gitignore file).
—
Reply to this email directly, view it on GitHubhttps://github.com/zhenkaisitecore/sitecore-codex/pull/9#issuecomment-1718628901, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYCRPEYHN6JF3DRFNEIPTTTX2JP63ANCNFSM6AAAAAA4WP7X4Y.
You are receiving this because you authored the thread.Message ID: @.***>
This message and its attachments are for the designated recipient only and may contain proprietary or otherwise confidential information. If you have received this message in error, please notify the sender immediately and delete the original. Any other sharing, copying or use of this message by you is strictly prohibited.