Current Selected Date is other than they should be (-1 day)

I have problem if I selected day and print this I have date with - 1 day
Problem is when I change firstDayOfWeak, when is default is good.
On the start ViewController I selected currentDay and calendar selected currently date
   let currentDateString = formatter.string(from: Date())
        let cellStateDateString = formatter.string(from: cellState.date)
        if currentDateString ==  cellStateDateString {
                validCell.dataLabel.textColor = selectedMounthColor
                validCell.selectedView.backgroundColor = UIColor.blue
     }

Version 7.1.5
Swift 4
Tested on iPhone X (no on simulator)
My code:
    func configureCalendar(_ calendar: JTAppleCalendarView) -> ConfigurationParameters {
        calendarView.scrollToDate(Date(), animateScroll: false)
        testCalendar.timeZone = Calendar.current.timeZone
        testCalendar.locale = Calendar.current.locale
        self.formatter.dateFormat = "yyyy MM dd"
        self.formatter.timeZone = Calendar.current.timeZone
        self.formatter.locale = Calendar.current.locale
        let startDate = formatter.date(from: "2017 01 01")
        let endDate = formatter.date(from: "2100 12 28")
        let firstDayOfWeek: DaysOfWeek = .monday // when I don't set value .monday calendar selected currently date

        let parametrs = ConfigurationParameters(startDate: startDate!,
                                                endDate: endDate!,
                                                calendar: testCalendar,
                                                firstDayOfWeek: firstDayOfWeek)
        return parametrs
    }

func calendar(_ calendar: JTAppleCalendarView, didSelectDate date: Date, cell: JTAppleCell?, cellState: CellState) {
        print(date) // date -1Day
        handleCellSelected(view: cell, cellState: cellState)
        handleCellTextColor(view: cell, cellState: cellState)
    }

This is a very popular question asked for iOS on any calendar library on github.
It happens to people in the East.
We explained it here -> https://github.com/patchthecode/JTAppleCalendar/issues/252
Will close this. Let me know if youre still stuck.


Adding São Paulo event

We are happy to announce the São Paulo edition of CodeintheDark! The event will be at Google, and we are expecting 100 developers!
Will be a pre event of FrontinSampa - a classic event for frontend developers on São Paulo.
If someone will be at Brazil, specifically at São Paulo, join us to the event!

Cool! I wish you the best of luck with the event!


refactor: mkd examples

Overview

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change
[ ] This PR includes testing instructions tests for the code change
[ ] The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories

Testing Instructions

Don't make me tap the sign.
PR Links and Envs

Repository
PR Link
PR Env

Monolith
Monolith PR
Monolith Env

Portal
Portal Link
Portal Env

Another Repo
Another Link
Another Env

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.178-alpha.902bfe.0@codecademy/gamut-labs@33.0.14-alpha.902bfe.0@codecademy/gamut@50.2.1-alpha.902bfe.0@codecademy/monaco@0.6.72-alpha.902bfe.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://62f5583fafe49c082585c372--gamut-preview.netlify.appDeploy Logs


Android - Payments - Default payment is disappearing after closed and re-open the app.

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

Action Performed:
Prerequisite: add VBA to the account

Launch the app
Log in with account
Go to Setting - Payments
Select Saving account
Tap Make default payment method
Put your password and Save
Close the app
Open the app again

Expected Result:
Default payment is not disappearing after closed and re-open the app
Actual Result:
Default payment is disappearing after closed and re-open the app.
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: No
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Feya86Katya
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/179871170-13c52f7f-9168-4c5c-a435-e73aab995835.mp4
https://user-images.githubusercontent.com/93399543/179903218-5604d5bb-3ac1-4a1e-aa31-1c05a5255bf4.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

seems related to https://github.com/Expensify/App/pull/9828
@MariaHCD the front end code looks good here and the linked Web-E PR is on production.
Will try to look at logs and see if there's any obvious reason why this wouldn't work.

Seems to be throwing here:
https://www.expensify.com/_devportal/tools/logSearch/#query=request_id:("72d79a1c5ff9305d-LAX")+AND+timestamp:[2022-07-19T23:32:50.671Z+TO+2022-07-20T01:32:50.671Z]&index=logs_expensify-017732

Throwing exception with message: '401 No user with that partner/userID/password' from auth/lib/Login.cpp:320

@kbecciv are you certain that the password entered is correct? This looks like a normal error that would throw if the password was entered incorrectly and from watching the video I think that might have happened.

@marcaaron Yes, password is correct. Just re-test with build <IP_ADDRESS> and issue is reproduced.
Also noticed the payments list is not displayed when navigate to Payments.
Please attached video.
https://user-images.githubusercontent.com/93399543/180068986-5d632ec9-df0f-478f-888c-26d8aa3ba15c.mp4

I tested with the same account and looks like there was an issue with setting the default payment method which is why the default badge doesn't stick.
2022-07-21 09:44:46 882 |<EMAIL_ADDRESS>| Cannot find bankAccountID: 0

2022-07-21 09:44:46 882 |<EMAIL_ADDRESS>| [OOPS!] API Threw: Auth SetWalletLinkedAccount returned an error ExpException - 4bbb72ecefead2582ca5df4a9b782afc ~~ message: '404 Bank account not found' 0: '[onyxMethod: 'merge' key: 'userWallet' value: '[error: 'Something went wrong. Please chat with Concierge for further assistance.']']' exceptionMessage: 'Auth SetWalletLinkedAccount returned an error' exceptionFile: '/git/releases/expensify.com/4c925fa/lib/Auth.php' exceptionLine: '117' exceptionCode: '404'

Logs: https://www.expensify.com/_devportal/tools/logSearch/#query=request_id:("72e2fffc6d40b8fd-DEN")+AND+timestamp:[2022-07-21T08:44:46.877Z+TO+2022-07-21T10:44:46.877Z]&index=logs_expensify-017754

Ok. So after this conversation in Slack this is most likely happening because tester does not have an active wallet.
https://expensify.slack.com/archives/C03TQ48KC/p1658426458912309
Myself and Chirag both tested these flows with Gold wallets and it works ok. So, I think we need some better error handling. But this is not a deploy blocker.

Thanks for the fix here! Agreed that we'll need better error handling here. In light of this announcement, I'll also have to update the format of the error data sent to the client.

Introducing better error handling here: https://github.com/Expensify/App/pull/10322
Closing in favor of: https://github.com/Expensify/Expensify/issues/216152


Unable to install through install guide

cloud@SERVER-PC:/media/cloud/SSD/moa$ sudo apt install python-dev python3-dev build-essential
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package python-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  python2-dev:i386 python2:i386 python2-dev python2 python-dev-is-python3

E: Package 'python-dev' has no installation candidate
cloud@SERVER-PC:/media/cloud/SSD/moa$

This is because python-dev is no longer in the ubuntu repository.
cloud@SERVER-PC:/media/cloud/SSD/moa$ PIPENV_VENV_IN_PROJECT=1 pipenv install
Installing dependencies from Pipfile.lock (4647c8)...
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
cloud@SERVER-PC:/media/cloud/SSD/moa$ MOA_CONFIG=config.DevelopmentConfig /usr/local/bin/pipenv run python -m moa.models
-bash: /usr/local/bin/pipenv: No such file or directory
cloud@SERVER-PC:/media/cloud/SSD/moa$ which pipenv
/home/cloud/.local/bin/pipenv

cloud@SERVER-PC:/media/cloud/SSD/moa$ MOA_CONFIG=config.DevelopmentConfig /home/cloud/.local/bin/pipenv run python -m mo
a.models
Traceback (most recent call last):
  File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/media/cloud/SSD/moa/moa/models.py", line 255, in <module>
    config = getattr(importlib.import_module('config'), moa_config)
AttributeError: module 'config' has no attribute 'config.DevelopmentConfig'
cloud@SERVER-PC:/media/cloud/SSD/moa$

I can't proceed further here.

Same here :(


Remove dead links

Went through all of the links in the README and removed all that were dead.
Remove each one in a commit, but I can squash that if you want!
Fixes: https://github.com/jdorfman/awesome-json-datasets/issues/182

This is great work. Thank you so much @tophernuts!


Ability to utilize repository.credentials in initialRepositories

Right now when you add a repository via initialRepositories we have to specify credentials or keys for each individual repository that we would like to use. As of ArgoCD v1.4.X, we have the ability to specify a key to be used at a root of a repo (i.e org/project) level with repository.credentials. Not sure what the design of this would look like at this point, but I think it would be beneficial to be able to support both.
Happy to help add functionality here, but wanted to get others input here first.

@tylerauerbeck I am looking through the Repository Credentials section of the Argo docs and I am trying to work though how to best support configuring this. I agree though that it would be nice to have the operator support this.

Support for this has been added in #105 and will go out in the next release.


How can I make a field optional and still have validation if filled?

Hi @htabi23 , this is actually easy.  You can define a regex, which allows empty string, and also validate some specific pattern.


Add support for Ubuntu 20.04 (Focal Fossa) release

Is your feature request related to a problem? Please describe.

az cli can't be installed on Ubuntu 20.04 using apt after referring to official method, as right after apt update user will be greeted with following error:
E: The repository 'https://packages.microsoft.com/repos/azure-cli focal Release' does not have a Release file.

As I originally pointed out in https://github.com/Azure/azure-cli/issues/9585#issuecomment-608319542, only way to install it is to resort to a hack which is to add an older Ubuntu release to /etc/apt/sources.list.d/azure-cli.list file.  i.e:
deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ disco main

Which will then lead to other problems as discovered in: https://github.com/Azure/azure-cli/issues/13030#issuecomment-615547689
Describe the solution you'd like

As someone who used to create various Debian packages and handle custom repositories. Since last Ubuntu release libffi6 is availability for is 19.04, I would simply repackage this package for 20.04 and upload it as such to https://packages.microsoft.com/repos/azure-cli repo. After adding support for focal release for the repository, you've solved the problem of inability to have az cli installed and all of its features fully working on >= Ubuntu 20.04.
Describe alternatives you've considered

I would encourage you as a company to give az cli snap more attention, as one such packaging format could've solve all the problem mentioned here. I had a similar problem with my Python app which I addressed by creating a snap.
Additional context

None, please inform me if you have any additional questions and/or comments.

@fengzhou-msft please take a look

My current workaround is a pair of hacks to install the latest pre-packaged version on focal / 20.04:
# 1. Override the installer script to hardcode `eoan` package source:
curl -sL https://aka.ms/InstallAzureCLIDeb | sed 's/${CLI_REPO}/eoan/g;' | bash;

# 2. Add a symlink to make it appear that libffi 6 is installed:
cd /lib/x86_64-linux-gnu;
ln -s libffi.so.7.1.0 libffi.so.6;

My current workaround is a pair of hacks to install the latest pre-packaged version on focal / 20.04:
# 1. Override the installer script to hardcode `eoan` package source:
curl -sL https://aka.ms/InstallAzureCLIDeb | sed 's/${CLI_REPO}/eoan/g;' | bash;

# 2. Add a symlink to make it appear that libffi 6 is installed:
cd /lib/x86_64-linux-gnu;
ln -s libffi.so.7.1.0 libffi.so.6;

From WSL2 20.04 (upgraded from 18.04), I had to make the change in /usr/lib/x86_64-linux-gnu

@hajekj : Ah, yes.  I'm running az from inside a Linux Docker container, and Docker runs a Linux VM behind the scenes.  On a true Linux system, Ubuntu's /lib is a symbolic link to /usr/lib:
lrwxrwxrwx 1 root root 7 Apr 23 06:06 /lib -> usr/lib/

I don't think there's any translation of symlinks from *NIX filesystems to NTFS, so it's not surprising that you had to go to /usr/lib to find the file in WSL.

Also came across this issue. Is there a fix? I'm currently using azure-cli in a container as a temporary solution.

Looking for any update on this as having same issue here

Using the eoan install instructions above worked initially but then was unable to install az extensions properly.  I ended up falling back to the script install.

I'm experiencing the same issue.

Same issue here. The workarounds to get the package to install works but leaves you with an azure-cli that cannot install extensions. I've gotten things to work by creating my own python virutalenv and running pip install azure-cli instead since this doesn't try to do any weird distro version checks but this leaves me with only being able to run az commands when I am in that virtualenv so it's not an amazing workaround :(

@jsturtevant, @ms-lolo:  When I install azure-cli as described in my first comment above, I am able to install and use extensions.  When you say you can't install extensions, what do you mean?  It tells you that it can't?  It throws errors when you try to install extensions?  Extensions install but throw errors when you try to use them?
Wondering why I didn't have the same problem...Have you tried wading through the output of the install command and looking for errors?
az extension add --name azure-devops --debug

(feel free to install any other extension, azure-devops is just an example).
@jsturtevant: the method I posted above is the script install you said you ended up falling back to.  Can you explain what you meant?  If you don't modify the script it'll error out because there is no focal package available.  And if you do modify it to pull a prior version, you still need to satisfy the libffi dependency.

@jetzerb you're right. I was missing the libffi.so.6 and adding that let extensions install fine. but I don't think I'm ok leaving that fix in place. I don't feel comfortable making that symlink part of the process of provisioning production machines. I'm going to hold off and keep using the virtualenv until the deb package is fixed.

curl -sL https://aka.ms/InstallAzureCLIDeb | sudo ...

Not a habit you want to get into!

I'm also running into this issue.

Same issue here

I am also running into issues as my packages on the Ubuntu 20.04 LTS are failing to upgrade with the below error:
E: The repository 'https://packages.microsoft.com/repos/azure-cli focal Release' does not have a Release file.
Please do let us know the ETA when this will be available on Ubuntu 20.04 LTS.

Focal package released for azure-cli 2.6.0. Please try again.

FYI: I'm indeed able to install the 2.6.0 version on Ubuntu 20.4, via:
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash. Thanks.

Focal package released for azure-cli 2.6.0. Please try again.

Thank you, I can confirm this adds proper support for Ubuntu 20.04.


Fix #1646: hand applied patch from #1911, small change to the proposed query and create a new index

I've made two changes for this. I've made some comparisions for both changes between three versions of the query. My base have 50k pages and 100k revisions. I'm using PostgreSQL.
First I moved the LIMIT to the inner query, reducing the number of rows for some operations like the hash join.

Query
Time
Cost

Current
112ms
12183.33

PR 1911
203ms
36004.76

Inner LIMIT
123ms
19235.77

I also created an index on the created_at column.

Query
Time
Cost

Current
91ms
12183.23

PR 1911
123ms
13438.32

Inner LIMIT
81ms
10425.82

I could not apply the patch with git, probably because it's a bit old and conflicting.
I applied it by hand, at least for now, so we can discuss the solution.
This is not right because it erases the credits for both @khink and @mjec.
Thinking out loud: maybe I could add the fork from @khink as a remote and cherry pick the commits?

Finally, I was able to keep the commits from @khink and @mjec. :)

I saw it was postponed to 1.7 so just wanted to add a note.
I'm not very familiar with all the changes that are going on in Wagtail (as I don't actually use it) so if this PR diverge too much from the current code base I'll not be able to have the time to resolve the conflicts and update the PR when necessary (if the change are still in the interest of the project), so I'll need to "abandon" the PR.
The same applies to #2577.

Have re-tested with our >100k page site, and there are no performance issues at all.
Merged in 3b4c24e0b59638fb695cfd0f2637b8e5bc595214 + parents - thanks @dirtycoder, @mjec and @khink!


feat: Expose EntityGUID on NRQL Conditions.

This PR will expose EntityGUID on NRQL Alert Conditions.
These EntityGUIDs will be exposed to consumers of New Relic's Terraform Provider.
https://newrelic.atlassian.net/browse/AINTER-8515
In addition to the unit test update, I ran this locally to confirm I could see my EntityGUIDs on existing NRQL Conditions
package main

import (
	"fmt"
	"github.com/newrelic/newrelic-client-go/newrelic"
)

func main() {

	client, err := newrelic.New(newrelic.ConfigPersonalAPIKey("YOUR_API_KEY_HERE"))
	if err != nil {
		fmt.Printf("error initializing client:", err)
	}

	conditions, err := client.Alerts.ListNrqlConditions(<Your Policy ID Number Here>)
	if err != nil {
		fmt.Printf("error listing conditions", err)
	}
	for _, condition := range conditions {
		fmt.Println(*condition.EntityGUID)
	}

}

@Fallenstedt Thanks for the contribution. Just one minor suggestion and I think we'll be good to go.

@Fallenstedt Thanks for the contribution. Just one minor suggestion and I think we'll be good to go.


fetching from ostree repos sometimes fails with a gpg error

See original issue on GitLab
In GitLab by [Gitlab user @abderrahimk] on Jul 27, 2018, 21:40
Summary
fetching from ostree repos sometimes fails with a gpg error (Too many open files)
Steps to reproduce
I have been unable to reproduce this locally, but it happens consistently in the gitlab CI of gnome-build-meta when trying to fetch dependencies/base-sdk-images.bst from the bootstrap project of freedesktop-sdk. (despite my attempts to upgrade gnupg/gpgme).
What is the current bug behavior?
the fetch fails with the following error:
"GPG: Unable to complete signature verification: GPGME: Too many open files"
What is the expected correct behavior?
the fetch succeeds
Relevant logs and/or screenshots
https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/72861
https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/72764
https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/72101
https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/72084
Possible fixes
No idea.
Other relevant information
A workaround for this is to bst fetch a small number of elements (including the ostree repo) before running the full pipeline.

BuildStream version affected: 1.1.4 /milestone %"BuildStream_v1.2"

In GitLab by [Gitlab user @abderrahimk] on Jul 27, 2018, 21:40
changed the description

In GitLab by [Gitlab user @tristanvb] on Jul 28, 2018, 11:47
We are aware of this, but thanks for filing a ticket for it.
I have not verified this, but I am quite confident that we are hitting this GnuPG issue, which is fixed in the 2.2.7 release only a couple of months ago.
Once we can verify that this stops happening on systems with GnuPG >= 2.2.7, we should close this.

In GitLab by [Gitlab user @abderrahimk] on Jul 28, 2018, 19:55
One of the logs attached shows this happening with GnuPG 2.2.8
https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/72861

In GitLab by [Gitlab user @jjardon] on Jul 31, 2018, 14:43
FYI, This is affecting freedesktop-sdk as well; [Gitlab user @tristanvb] any chance we can make this a blocker for 1.2?

In GitLab by [Gitlab user @tristanvb] on Jul 31, 2018, 15:57
[Gitlab user @jjardon] no sorry thats not possible, as there is almost certainly nothing we can do about this.
The next steps for this issue is to ensure there is a corresponding ostree issue filed, and probably this is still leading back to GnuPG, but its worth bisecting ostree first before opening a GnuPG issue i think (this is happening frequently now, and didnt seem to happen at all a year or more ago).
That said, one can at least work around the issue by:

Using an https url for ostree repos
Not configuring the gpg validation key

In GitLab by [Gitlab user @jjardon] on Jul 31, 2018, 23:15
mentioned in merge request freedesktop-sdk/freedesktop-sdk!283

In GitLab by [Gitlab user @jjardon] on Aug 1, 2018, 13:56
mentioned in commit freedesktop-sdk/freedesktop-sdk[Gitlab user @7dd004839ad21be7ba784689abfc047791bf00c9]

In GitLab by [Gitlab user @jjardon] on Aug 1, 2018, 14:00
mentioned in commit freedesktop-sdk/freedesktop-sdk[Gitlab user @58447b403cba2e6be4c642751abe72d8d7c2c521]

In GitLab by [Gitlab user @jjardon] on Aug 1, 2018, 14:26
mentioned in commit freedesktop-sdk/freedesktop-sdk[Gitlab user @35fd9809091eed2414579a1dec61134313a25c31]

In GitLab by [Gitlab user @jjardon] on Aug 2, 2018, 11:03
mentioned in commit freedesktop-sdk/freedesktop-sdk[Gitlab user @bf0b038ef85cfcfb1fcfc26d9737e5889d588d8b]

In GitLab by [Gitlab user @jjardon] on Aug 3, 2018, 12:38
mentioned in commit freedesktop-sdk/freedesktop-sdk[Gitlab user @c9809f4da20dd9f3adc7aaeefa255cea2ff556ea]

In GitLab by [Gitlab user @jjardon] on Aug 4, 2018, 00:20
mentioned in commit freedesktop-sdk/freedesktop-sdk[Gitlab user @02d47196e5fb7424d60b747e84bff2221ae11e13]

In GitLab by [Gitlab user @tlater] on Sep 25, 2018, 15:10
mentioned in merge request website!93

In GitLab by [Gitlab user @nanonyme] on Feb 13, 2019, 08:18
Was there ever any progress on this? I can't spot linked ostree issue and from what I can see the workaround changes trust model significantly (you move trust from owner of ostree repo to SSL root CA's)

@gtristan it looks like this is probably just yet another case of bst1 running trashing all fd's available. It's possible the situation is made worse through the way bst1 uses ostree (bst-plugins-external switched to calling ostree binary which has many other benefits as well). We now have GPG verification enabled with fd limits set ridiculously high and haven't ran into issues so this can probably be closed.

Thanks, lets close this.


Multi-level RNN example

Multi-level RNNs are getting more popular, important especially (but not only) for character level models. Moreover, they are a bit unintuitive in Keras when they are bidirectional. This example demonstrates how to construct them, a few common tricks, and a few exercises that might prove educational for newcomers to RNNs for NLP.
I had to answer a question about how to build these in Keras maybe four times in the last month alone, I really see a lot of interest and the github issues of Keras contain scattered, obsolete and misleading information.  I also tried to point out some common pitfalls, e.g. not taking result variance into account.

The docstring would need more detailed explanation of how the model works (this will be read by people with no previous background in bi-directional RNNs).
How about instead creating a PR for a Bidirectional wrapper for RNNs, in layers/wrappers.py? This would be more reusable and would be readily applicable to any existing RNN. You already have all the code to make it happen ;-)

It seems that the simple "shallow" model such as CNN, FastText can achieve quite good performance on text classification w.r.t. both accuracy and training time. Could you explain why should we apply the multi-level RNN on text classification? Any paper reference will be appreciated.

@pasky : we have merged the Bidirectional wrapper. What do you want to do with your example -- do you want to adapt it to use the Bidirectional wrapper?

@pasky You can make your code much prettier with the Bidirectional wrapper :
input = Input((maxlen,))
embeddings = Embedding(max_features, 128)(input)
rnn_output = embeddings
for i in range(nb_levels):
	rnn_output = Dropout(0.3)(rnn_output)
	rnn_output = Bidirectional((GRU(128, return_sequences=True)), merge_mode='sum')(rnn_output)
	rnn_output = merge([rnn_output, embeddings], mode='sum')  # Feeding the input sequence at every level imporves accuracy
output = Lambda(lambda x:x[:, -1, :], output_shape=lambda s: (s[0], s[2]))(rnn_output)  # We require the final timestep only
output = Dropout(0.25)(output)
output = Dense(1, activation='sigmoid')(output)
model = Model(input=input, output=output)

Oh, I'm glad that Bidirectional() layer indeed did land meanwhile! I think that makes the example less educational, especially since the accuracy improvement is very minuscule.
One general class of problems not included in Keras examples is sequence tagging, and multi-level RNNs shine in that area a lot. The problem is that e.g. the CoNLL2003 NER dataset (which is the most standard sequence tagging dataset I'd say) is not freely available. My past models were run on non-public data too.
Any ideas re what data we could use to demo this? I'll think about it too, and be happy to convert the example to a sequence prediction task, which I think would make it a lot more useful.

There should be some open sequence tagging dataset.. it doesn't seem sensible to use this for imdb since fasttext example can reach 90% accuracy in 3 less than seconds.

So my restrictions are: (A) freely available, ideally easily automatically downloadable from 3rd-party location; (B) English if possible (I could use the opportunity to also show how to preinitialize word embeddings from GloVe or such.); (C) ideally referenced in some recent academic papers.
I looked at part-of-speech tagging and treebanks, but the free ones all seem kind of obscure.
A NER option may be http://schwa.org/projects/resources/wiki/Wikiner though it's a bit obscure (didn't see a paper from other people than its authors that would benchmark on it).
Some bleeding edge datasets for NLP sequence tagging that come to mind are the WikiReading dataset and https://stanford-qa.com/ - but the task requires some explaining, is pretty hard and the datasets aren't that small. But we could just go with that anyway...

I would consider using Stanford QA since it will only rise in popularity over the next couple years. It will be good to have a stanford_qa module in keras.datasets to automatically download and process it.

Closing outdated PR. If you still care about the content of the PR, please submit a new PR to master, updated for the Keras 2.0 API.


Chaincode Intall and approve failed

Describe the bug
hello i forked this repository with the updates.

first i install and configured the prerequisites following the oficcial documentation

install:
https://blockchain-automation-framework.readthedocs.io/en/latest/prerequisites.html
configure:
https://blockchain-automation-framework.readthedocs.io/en/latest/operations/configure_prerequisites.html

I edited the  network.yaml of example for use one orderer and two organizations and put it in a folder called build.

the edition looks like this images:
a)  I use the fabric plataform without the frontend and external dns.

b) I only use two organizations with one orderer.

c) this tree elements have the same external uri suffix:

d)  i added my own chaincode:

it is to highlight that I am using  a cluster in gcp for run the network and i already have done the test on two types of container runtime ( one is the docker and the other the containerd).

when i run the ansible command:

ansible-playbook platforms/shared/configuration/site.yaml --inventory-file=platforms/shared/inventory/  -e<EMAIL_ADDRESS>-e 'ansible_python_interpreter=/usr/bin/python3'
and come to the part in the chaincode going to be installed I get the following errors:
a) If it is the example chaincode, it can be installed but when it seeks to be approved it gives me the following error:
Error: timed out waiting for txid on all peers
I had already commented on this error in the previous issue but I updated the repository and it still does not happen to me.
b) If the chaincode is another (my case), it won't install it and the results show me that the chaincode no exist.
I have checked the installation template to see some hint why it happens, but I am still new to ansible and kubernetes.
I found the following:

From what I understand the chaincode is cloned using my github credentials and it is stored in the tmp folder of the container then it is copied to the chaincode folder. Then a variable is exported which refers to the directory where the chaincode will be packaged. However that variable refers to the chaincode's main.go being found inside a folder named after the chaincode's name.
I edited this since my chaincode folder is configured differently, so now it appears to me that it is. However it gives me the following error:
Error: error getting chaincode bytes: failed to calculate dependencies: incomplete package: github.com/hyperledger/fabric-contract-api-go/contractapi
from what I saw is due to the lack of some dependencies, so what should I do to be able to download these dependencies?.
Environment (please complete the following information):

GKE Cluster
Docker and Containerd runtimes

another question with what type of containers run in k8s with docker or containerd?

Same as issue #1307

Closed because it is the same issue #1307


New cryptocurrency in 200 lines of code

Excluding merges, 1 author has pushed 20 commits to master and 20 commits to all branches.


Getting all the attributes from AD

I am trying to get all attributes related to users so when I use attrlist=['*'] in the paged search I get about 125 attributes. When I tried the Get-ADUser in Powershell to to enumerate all the attributes there are about 205. I am trying to get the remaining attributes as well is there a way to do that? The missing attributes include -
AccountNotDelegated, AllowReversiblePasswordEncryption, BadLogonCount, CannotChangePassword, DoesNotRequirePreAuth etc.
example code -
with client.connect() as conn:
    result = conn.paged_search(base=base, scope=2, filter_exp=query, attrlist=['*'],
                               page_size=1000, attrsonly=False)

Powershell code -
 Get-ADUser -Server $Server -Filter $Filter -ResultPageSize 1000 -Properties *

If you explicitly add these attributes to the attrlist  can you collect them?

I tried doing that but the attributes didn't return.
with client.connect() as conn:
    result = conn.paged_search(base=base, scope=2, filter_exp=query, attrlist=['AccountNotDelegated', 'AllowReversiblePasswordEncryption'], page_size=1000, attrsonly=False)

The result only has 'dn'

Can it be access rights problem?
Is there a UserAccountControl attribute for the entity?

Looked through the docs but I cannot find all the attributes. Some might be there but if multiple flags are True this wasn't very reliable.
The following are the UserControl Attributes that I tried to match with -

https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/useraccountcontrol-manipulate-account-properties
https://jackstromberg.com/2013/01/useraccountcontrol-attributeflag-values/

I double checked if it's access related then I wouldn't be able to query the same using Powershell.

In 1.3.0 added a UserAccountControl class to easily parse the attribute.


NullReferenceException in ResolutionStrategy.cs when InjectionParameter value is null

This is in Stashbox 2.7.4 so forgive me if this has been found / fixed already.
I have an unusual edge case where I need to set an InjectionParameter with a null value. Upon attempting to resolve the service, a NullReferenceException is thrown.
After some debugging, I found that the problem area is in ResolutionStrategy.cs, line 43 (in BuildResolutionExpression):
var matchingParam = injectionParameters?.FirstOrDefault(param => param.Name == typeInformation.ParameterOrMemberName);
if (matchingParam != null)
    return matchingParam.Value.GetType() == typeInformation.Type
        ? matchingParam.Value.AsConstant()
        : matchingParam.Value.AsConstant().ConvertTo(typeInformation.Type);

You're already checking matchingParam for null, but the dependence on matchingParam.Value.GetType() and matchingParam.Value.AsConstant() both will cause NullReferenceExceptions here because matchingParam.Value is null.
Unfortunately I can't think of an immediate solution to this and it's definitely a strange use case. Fortunately since Stashbox is so flexible I should be able to find a workaround. :)

Hey, thanks for pointing this out, I'll fix this in the next release!

fixed in v2.5.7


lightbox: Disable controls on video previews in lightbox.

Setting any value for a boolean attribute (like "controls") enables it.

Merged and marked as a backport candidate, thanks @alexmv!

Backported in https://github.com/zulip/zulip/pull/31216.


When I use CDN to introduce it directly into HTML for development, the unocss plug-in of vscode does not work.

UnoCSS version
0.62.2
Describe the bug
When I use CDN to directly introduce it into HTML for development, the unocss plug-in of vscode does not work, there is no preview, and there is no prompt.
Reproduction

Create a new html page
Install UnoCSS’s vscode plug-in
Insert the following code in html

<!DOCTYPE html>

    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Document</title>
    <link rel="stylesheet"<EMAIL_ADDRESS>


Switch to purescript-dom

Bower can't find the right version of purescript-foreign.

Oops, that's the examples that are failing, I forgot to bump ace/affjax.

There we go.


Issue with CI/CD running twice

What is the issue?
After a PR closes, the CI/CD of the project runs twice (for the PR and for the versioning automation).
What do you suggest?
Find a way to it only run it once.

This caused a bug, of deploying documentation without the versioning information.

Add in the documentation that docs/changelog.rst should ONLY be modified in a release PR.


Arithmetic Operations on Images using OpenCV

I would like to perform addition and subtraction on two images.
I am a participant at GSSOC'21, requesting admins to assign me this issue.

Assigning you with the same @ricsin23.


403 not treated as error

According to the HTTP standard, successful responses are those whose status codes are in the 200-300 range. But sqlalchemy backend is not treating 403 as a error and not populating error column. Essentially request_error function is not getting called.

what about any other 4xx or 5xx?

Same. No error is logged based on response code.

I think that's right behavior. Status code is written in database, and further operations is expected to be customized by user.


can vcpkg support vc-ltl？

https://github.com/Chuyu-Team/VC-LTL

We can’t reopen this issue until a PR is opened, unfortunately, consider making a pull request!


💡[Feature]: Hair type classification using CNN and neural Networks

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Dataset link : https://www.kaggle.com/datasets/kavyasreeb/hair-type-dataset
classification if inputed image hair type into straight, curly ,weavy ,curly , deadlocks, krinky etc based on user inouted and CNN classification technique. i will provide a compleet analysis of ipynb file and streamlit based gui application for the same
please assign this issue to me under gssoc'24  extended and hactoberfest-accepted tag
Use Case
This will be useful in identifying the hairtype of different user using aiml techniques
Benefits
Smart Automation
Add ScreenShots
NA
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

https://github.com/recodehive/machine-learning-repos/issues/1367

I want to contribute in this.


cleos walletapi connection errors need improvement

I get following when I try to connect to my wallet API through cleos:
cleos -n -v -u https://eos.XXX.YYY --wallet-url https://eos-wallet.XXX.YYY wallet list
Unable to connect to keosd, if keosd is running please kill the process and try again.
103359ms thread-0   main.cpp:2577                 main                 ] connect error: 1100000 connection_exception: Connection Exception
Unable to connect to keosd
    {}
    thread-0  main.cpp:726 try_port

It appears that cleos can connect to nodeos API through https no problem, but for some reason has problems with wallet API ? Not much debugging output there so...

In https://github.com/EOSIO/eos/blob/379cb1a9e2a6557221d946eef4c5c83ddd156799/programs/cleos/main.cpp#L739
I see     if (parsed_url.server != "localhost" && parsed_url.server != "<IP_ADDRESS>")         return; - does that suppose to mean that cleos doesn't support remote keosd addresses, only localhost ?

related to https://github.com/EOSIO/eos/issues/3878

Closed as duplicate, will track progress in #3878


BetaWarningState Grammar Check

Idk I felt like it
Neat little attention to detail
Please add it; it's like the least buggy thing in this engine

we cant merge this for a secret dev feature we're adding in the new update.. you'll see, trust me its good :]

👀👀👀👀


Data not displayed in view_list.html

Issue

As shown in the above image, data isn't being displayed for the user. I see the issue is that the data is not being sent in the /view_list route and as a result, there's no data to be displayed in the front end
Solution idea
->Just pass the data required in the arguments when the route is being redirected in the backend. This should resolve the issue.

This is resolved now the thing previously was data not being sent. I have changed that below is the screen shot of the fixed issue.


cannot import name 'execute' from 'qiskit'

Environment

Qiskit version: 1.00
Python version: 3.12.2
Operating system: Windows 10

What is happening?
Hi all! Can anybody help me?
I have a qasm-file and want to run (execute) it in python. I installed Qiskit 1.0.0, but got the error: cannot import name 'execute' from 'qiskit'.
How can we reproduce the issue?
Here is my code:
from qiskit import QuantumCircuit, execute, Aer
import json
--- Creating a quantum circuit from a qasm file
circuit = QuantumCircuit.from_qasm_file('NAME.qasm')
--- Backend selection
backend = Aer.get_backend('qasm_simulator')
--- Executing the scheme on the selected backend
job = execute(circuit, backend, shots=1024)
--- Getting results
result = job.result().get_counts()
result_json = json.dumps(result)
print(result_json)

The execute function has been removed in Qiskit 1.0 (see https://github.com/Qiskit/qiskit/pull/11565) after being deprecated in 0.46. The release notes (see https://docs.quantum.ibm.com/api/qiskit/release-notes/0.46#deprecation-notes) describe what you can use as replacement. It also seems you're using a legacy import of Aer, which should now be import from qiskit_aer instead.
Here's an updated version of your snippet
from qiskit import QuantumCircuit
from qiskit_aer import Aer
import json

# Creating a quantum circuit from a qasm file
circuit = QuantumCircuit.from_qasm_file('NAME.qasm')

# Backend selection
backend = Aer.get_backend('qasm_simulator')

# Executing the scheme on the selected backend
job = backend.run(circuit, shots=1024)

# Getting results
result = job.result().get_counts()
result_json = json.dumps(result)

print(result_json)

Alternatively you could also use the Sampler primitive to execute the circuit.


Symbolic link in plugin directory pointing to itself causes issues in plugin install

Mini explanation
When running the test for prep (initially concurrently) tests would fail. Tried running serially, still got an error.
Adding some more verbosity, the error seems to be that the installation process may be trying to do something recursive?
Issue Notes:
Command executed (after sourcing testing virtualenv):
python3 /home/marflo/Documents/iRODS/irods_testing_environment/run_plugin_tests.py --project-directory /home/marflo/Documents/iRODS/irods_testing_environment/projects/rockylinux-9/rockylinux-9-postgres-14.8/ --irods-package-directory /home/marflo/Documents/iRODS/build-artifacts/rockylinux-9/packages/ --output-directory /home/marflo/Documents/iRODS/build-artifacts/rockylinux-9/logs/ --plugin-package-directory /home/marflo/Documents/iRODS/build-artifacts/rockylinux-9/prep -vv irods_rule_engine_plugin_python

From the logs (with extra before & after error):
...
2024-04-29 12:47:32,655 - [rockylinux-9-postgres-148_irods-catalog-provider_1]: running test [None]
2024-04-29 12:47:34,266 - Processing /tmp/tmpz9gyo_bk/irods_python_ci_utilities

2024-04-29 12:47:34,266 -   DEPRECATION: A future pip version will change local packages to be built in-place without first copying to a temporary directory. We recommend you use --use-feature=in-tree-build to t
est your packages with this new behavior before it becomes the default.
   pip 21.3 will remove support for this functionality. You can find discussion regarding this at https://github.com/pypa/pip/issues/7555.

2024-04-29 12:47:34,607 - Using legacy 'setup.py install' for irods-python-ci-utilities, since package 'wheel' is not installed.

2024-04-29 12:47:34,732 - Installing collected packages: irods-python-ci-utilities

2024-04-29 12:47:34,734 -     Running setup.py install for irods-python-ci-utilities: started

2024-04-29 12:47:35,084 -     Running setup.py install for irods-python-ci-utilities: finished with status 'done'

2024-04-29 12:47:35,093 - Successfully installed irods-python-ci-utilities-0.1

2024-04-29 12:47:35,093 - WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instea
d: https://pip.pypa.io/warnings/venv

2024-04-29 12:47:37,879 - Traceback (most recent call last):
  File "/tmp/tmpcaq1wrbz/irods_rule_engine_plugin_python/irods_consortium_continuous_integration_test_hook.py", line 46, in <module>

2024-04-29 12:47:37,880 - Last metadata expiration check: 0:00:28 ago on Mon Apr 29 17:47:08 2024.
Dependencies resolved.
Nothing to do.
Complete!

Last metadata expiration check: 0:00:29 ago on Mon Apr 29 17:47:08 2024.
Not a valid rpm file path: /home/marflo/Documents/iRODS/build-artifacts/rockylinux-9/prep/Rocky linux_9/Rocky linux_9

Error: Nothing to do.

2024-04-29 12:47:37,880 -     main()
  File "/tmp/tmpcaq1wrbz/irods_rule_engine_plugin_python/irods_consortium_continuous_integration_test_hook.py", line 25, in main

2024-04-29 12:47:37,881 -     irods_python_ci_utilities.install_os_packages_from_files([os.path.join(plugin_dir, entry) for entry in os.listdir(plugin_dir)])
  File "/usr/local/lib/python3.9/site-packages/irods_python_ci_utilities/irods_python_ci_utilities.py", line 139, in install_os_packages_from_files

2024-04-29 12:47:37,881 -     dispatch_map[get_distribution()](files)
  File "/usr/local/lib/python3.9/site-packages/irods_python_ci_utilities/irods_python_ci_utilities.py", line 115, in install_os_packages_from_files_dnf

2024-04-29 12:47:37,881 -     subprocess_get_output(args, check_rc=True)
  File "/usr/local/lib/python3.9/site-packages/irods_python_ci_utilities/irods_python_ci_utilities.py", line 64, in subprocess_get_output

2024-04-29 12:47:37,882 -     raise RuntimeError('''subprocess_get_output() failed
RuntimeError: subprocess_get_output() failed
args: (['sudo', 'dnf', 'localinstall', '-y', '--nogpgcheck', '/home/marflo/Documents/iRODS/build-artifacts/rockylinux-9/prep/Rocky linux_9/irods-rule-engine-plugin-python-<IP_ADDRESS>-0.el9.x86_64.rpm', '/home/marflo/Documents/iRODS/build-artifacts/rockylinux-9/prep/Rocky linux_9/Rocky linux_9'],)
kwargs: {'stdout': -1, 'stderr': -1}
returncode: 1
stdout: Last metadata expiration check: 0:00:29 ago on Mon Apr 29 17:47:08 2024.
Not a valid rpm file path: /home/marflo/Documents/iRODS/build-artifacts/rockylinux-9/prep/Rocky linux_9/Rocky linux_9

stderr: Error: Nothing to do.

2024-04-29 12:47:37,907 - [rockylinux-9-postgres-148_irods-catalog-provider_1]: cmd [1] [['python3', '/tmp/tmpcaq1wrbz/irods_rule_engine_plugin_python/irods_consortium_continuous_integration_test_hook.py', '--built_packages_root_directory', '/home/marflo/Documents/iRODS/build-artifacts/rockylinux-9/prep']]
2024-04-29 12:47:37,907 - [rockylinux-9-postgres-148_irods-catalog-provider_1]: test failed [[   5.2512]s] [all tests]
2024-04-29 12:47:37,907 - [rockylinux-9-postgres-148_irods-catalog-provider_1]: Queue is empty!
2024-04-29 12:47:37,908 - [rockylinux-9-postgres-148_irods-catalog-provider_1]: tests that failed [[(None, 5.251229763031006)]]
2024-04-29 12:47:37,908 - [rockylinux-9-postgres-148_irods-catalog-provider_1]: some tests failed
2024-04-29 12:47:37,909 - [[1]]
2024-04-29 12:47:37,909 - [[1]]
2024-04-29 12:47:37,909 - ==== begin test run results ====
...

Directory of prep looks like so:
marflo@westwing:~/Documents/iRODS$ ls -l build-artifacts/rockylinux-9/prep
total 2144
-rw-r--r-- 1 root   root   2194183 Apr 29 09:51  irods-rule-engine-plugin-python-<IP_ADDRESS>-0.el9.x86_64.rpm
lrwxrwxrwx 1 marflo marflo       1 Apr 29 09:29 'Rocky linux_9' -> .

Mini Note
This might be prep specific? This sym-link style worked with some other plugins (curl, index, logical, metadata).

Just noting here that this may be an issue for https://github.com/irods/irods_python_ci_utilities rather than the testing environment. But let's keep it here for now.

I have not observed this issue myself, despite using symbolic links like this.


Crash while using latest build

Hi! I'm crashing when i paste this stream url and press play:
https://gist.github.com/vpontin/0bbd016875fbc978c9b30f166eccc453
I'm using OpenFM-1.9.4-<IP_ADDRESS>, Minecraft 1.10.2 (i assume most 1.9.4 mods are compatible with 1.10.x) and Forge b2014.
The stream url is: http://<IP_ADDRESS>:7998/ and according with Winamp:
Server: SHOUTcast Distributed Network Audio Server/Linux v1.9.8
Content-Type: audio/mpeg

No, in this case OpenFM isn't 1.10 compatible, there were some minor changes in the networking system that I've got to port for

Uh i understand.
I hate asking ETAs, but now with gamax92 helping in the network system, do you have plans to port to 1.10?
Thanks in advance!

Actually I can't reproduce that running OpenFM-1.9.4-<IP_ADDRESS>.jar with Forge 1.10.2-<IP_ADDRESS>4.  Though the coremod doesn't run so the SPIs that do the decoding don't get extracted so nothing plays.

Any updates on this...?

Oh i'm sorry, i will try to test using another stream.

Running the latest version (OpenFM-1.9.4-<IP_ADDRESS>) on a fresh (no mods) Forge profile with the same build (1.10.2 b2014) dont gives any errors. I will test on my "Production" build before closing


Line feed after post-login command not working / Windows 10

Although the return character after the command works on a linux server as expected (i.e. command executes), on a windows server it copies the command in prompt and ignores all return characters.

Device: Xiaomi Mi A2 Lite
OS: Android 9
ConnectBot Version: 1.9.6
Server OS: Windows 10
Server version: <IP_ADDRESS> (windows built in openssh server)

I assume this is a multi-line post-login command? (i.e., the line return is integrated into the post-login command)

Uh it is a one-liner followed by a return character

I'm having this issue too. My guess is cmd.exe interprets lf alone not as an enter. I couldn't find an easy way to insert cr with android keyboards, so I wasn't able to test my hypothesis.

Logging on to say, this is still an issue.

I was able to work around this limitation by using this app, UnicodePad, to create a cr-lf sequence and copy-paste it into the connectbot cmd field.

I was able to work around this limitation by using this app, UnicodePad, to create a cr-lf sequence and copy-paste it into the connectbot cmd field.

Can confirm this works, just make sure you use the unicode symbol U+000D and paste it right after the post-login command, and it works fine.


check for String object as well as string

In Autocomplete if you return a String Object (instead of a simple string) i.e. new String('foo bar') for the getOptionLabel callback it raises an error.
The bigger problem is that if the option is complex and cannot be converted json, it will be a hard failure, due these lines in the code:
      if (typeof optionLabel !== 'string') {
        var erroneousReturn = optionLabel === undefined ? 'undefined' : "".concat(Object(_babel_runtime_helpers_esm_typeof__WEBPACK_IMPORTED_MODULE_2__["default"])(optionLabel), " (").concat(optionLabel, ")");
        console.error("Material-UI: The `getOptionLabel` method of ".concat(componentName, " returned ").concat(erroneousReturn, " instead of a string for ").concat(JSON.stringify(option), "."));
      }

TypeError
Converting circular structure to JSON
    --> starting at object with constructor 'Object'
    --- property 'loop' closes the circle
    at getOptionLabel (https://dkicr.csb.app/node_modules/
material-ui/lab/esm/useAutocomplete/useAutocomplete.js:66:173

This may seem like a contrived example, but its not.  Its quite possible to have options that represent complex data structures, and then to have a the structure keeping some data as String objects for effeciency

[X] The issue is present in the latest release.
[X] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Raises an error and possibly even crashes!
Expected Behavior 🤔
It should be fine for getOptionLabel to return new String('foo bar')
Steps to Reproduce 🕹
take any example put a circular dependency in the option and instead of returning a simple string return new String(s)
<Autocomplete
  id="combo-box-demo"
  options={top100Films}
  getOptionLabel= {(option) => { option.loop = option; new String(option.title) }}
  style={{ width: 300 }}
  renderInput={(params) => <TextField {...params} label="Combo box" variant="outlined" />}
/>

see https://codesandbox.io/s/material-demo-943tg

Tech
Version

Material-UI
v4.0.0-alpha.56

Tip: check the signature

I don't understand the comment.   Clearly I understand that the signature calls for a string.   I am not disagreeing that the code "works" "as expected", so perhaps I should have called this a feature???  Like what the feature be called?  Why not simply do this? Instead
String({'foo': "bar"}).toString()
instead of forcing the programmer to meet an unncessarily restrictive API.  There is surely no performance reason for doing so.
Furthermore it IS A bug in the sense that not meeting the API should give a sensible error, message not:
TypeError
Converting circular structure to JSON
    --> starting at object with constructor 'Object'
    --- property 'loop' closes the circle
    at getOptionLabel (https://dkicr.csb.app/node_modules/
material-ui/lab/esm/useAutocomplete/useAutocomplete.js:66:173

@catmando Any update on this?

I've run into this "Converting circular structure to JSON" error when my options are circular (so they cannot be JSON-ified) and I'm not setting isOptionEqualToValue. In my case, the error comes from MUI attempting to print a warning telling me to set isOptionEqualToValue. The code for producing the warning attempt to JSON.stringify the option causing the warning and results in this perplexing error. It'd be great if the warning code was resistant to this.
As to why the options would be circular - I'm using filterOptions to take the combination of query/options and augment every matching option with some JSX that depends on the query. This JSX will then be consumed by renderOptions. Turns out JSX objects are circular. Still, I think my use of the options is reasonable.


Doorbell Chime Silent Mode

v<IP_ADDRESS>10 of the Reolink Doorbell contained the change "Integrate Reolink Chime silent mode", this doesn't seem to be exposed through their app, but I was wondering if this functionality could be supported by this library? Thanks!

I also saw that one in the release notes.
However if its not available in the Reolink app/client/web client, there is no way to figure out the commands I need to send.
Moreover it will most likely be very buggy if its not yet implemented in the Reolink app/client
So unfortunately we will have to wait for Reolink to properly support it first.


Exploit PETSc matrix block structure

Address https://github.com/mfem/mfem/issues/3142

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#3179
@stefanozampini
@tzanio
@v-dobrev + @jandrej
8/31/22
⌛due 9/14/22
⌛due 9/21/22

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

Is this ready for review? It's a small and non-intrusive change that we can review pretty quickly.

Is this ready for review? It's a small and non-intrusive change that we can review pretty quickly.

Yes,  it is ready to go

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

@tzanio @v-dobrev any reason to hold this MR for getting merged?

Sorry for the delay @stefanozampini.
We will try to merge it soon, but it likely be after the mfem-4.5 release which we are finalizing this week.

Sorry for the delay @stefanozampini.
We will try to merge it soon, but it likely be after the mfem-4.5 release which we are finalizing this week.

Can you try to squeeze it in? It is minimal and should be no harm

Merged in next for testing...

Re-merged in next for testing...

Re-merged in next for testing...


Cleanup: remove the celo/clabs Grafana cross integration

To speed up the adoption of Grafana, the two instances that had been set up (celo and clabs) have been "integrated", meaning their primary Prometheus and Alertmanager datasources are available in both.
This is not desirable long term because it can cause confusion and configuration mistakes. This should be removed once all required data is available in the clabs instance.

The celo instance has no more access to the clabs prometheus datasource.

The celo prometheus datasource has been queried from within the clabs instance in the last 30d, holding off for now: https://clabs.grafana.net/datasources/edit/15/insights.

Removed the celo prometheus datasource from within the clabs instance.


Provide a way to positively detect WSL from an app compiled on Linux.

I understand that support is always improving, but it seems unlikely that the specific network functionality (raw sockets, packet sniffing, netlink routes) required by Nmap will ever be supported in WSL/BashOnWindows. We would like to be able to detect WSL and provide users with a helpful message pointing them to our Windows-native build, while allowing our app to continue until the first crash/error.
Is there any stable, predictable method for detecting whether our built-on-Linux program is being run on Windows Subsystem for Linux?

Can't speculate on 'stable', but /proc/version has the string 'Microsoft' which seems a pretty safe bet.

@therealkenc For the time being this is probably the best way to do it.  I can't promise that we'll never change the content of these ProcFs files, but I think it's unlikely we'll change it to something that doesn't contain "Microsoft" or "WSL".
/proc/sys/kernel/osrelease
/proc/version

@benhillis Do you guys over at Microsoft think you might ever support any/most/all of this low-level functionality used by nmap, eventually, in the (distant) future? Are there reasons in principle why you wouldn't want to or couldn't realistically support them?

@fpqc There's a lot of surface areas and features to cover in limited time.  The best way to help us prioritize work is by adding items to our User Voice page.

@benhillis Yes absolutely you only have a limited time before the Anniversary update for Win10.  I was just asking if the team over at Microsoft is planning on eventually seeing the project through to something on which the whole of the Linux userland can run (albeit maybe sometimes requiring tweaks).  I mean, of course, Microsoft is a business, not a charity, and ultimately development will continue only if WSL meets business goals, but I was just asking whether the current plan is that development will continue by the WSL team improving compatibility for the foreseeable future.
I think WSL is really Windows 10's new "Killer App" (to use some cliched marketing lingo), and I personally know several people already who have moved (or are prepared to move) back to a Windows ecosystem from Linux because it's such an exciting project.
My biggest worry is that MS is going to take the project to something like 85% completion and then let it stagnate.  WSL is something for which I would be willing to pay and for which my company would also be willing to pay, so I hope that development will continue past the anniversary release.

@fpqc This question is definitely above my pay-grade but I'll try to answer as best I can :)
I will say that as a developer on this feature I'm excited about the future of the project don't see it stagnating any time soon.  We have some exciting things planned that make me optimistic about the future of our technology.
Thank you for your kind words.

Closing this out since the discussion has run its course.

It would be great if someone would update config.guess to detect Ubuntu on Windows.

@haydentech For now, it's better not to mainline patches to add WSL support, because it will start fudging tests that the devs would like to solve by improving their driver.  The best way to test that is real-world usage, with software hitting all of the syscalls we would expect on a real Linux system.  The team is planning to implement unimplemented syscalls and fix buggy ones.

It would be great if someone would update config.guess

Unfortunately that doesn't work, because the header files (both kernel and glibc) lie by design. "It's a feature". So, say you push a config.guess patch to savanah to return x86_64-pc-wslwin-gnu, and it gets accepted by the FSF. But, then what.
That won't (for example) make PulseAudio (#486) realize that PTHREAD_PRIO_INHERIT is defined in the pthread.h header, but said feature does not actually work on the platform. You are going to have to push a patch to PA's ax_pthread.m4 too. And if you are going to patch PA to teach it about pc-wslwin-gnu, well... might as well be checking /proc/version. No one pushes a compile-time platform check like that mind you, because Stephen is liable fix the thing without notice.

@therealkenc I don't expect a config.guess change to magically fix all problems resulting from differences in the 2 platforms.  But it would fix my build problem, for one, and be a basis for future enhancements in other products.  Right now, there is nothing to build on.  Having config.guess return the same result for the two platforms is nonsensical.

I echo @fpqc's sentiment above
@fpqc - Regarding your comment, and specifically about raw sockets, the problem is that Windows does not natively support AF_PACKET socket domain. The functionality is exposed through other means on Windows because there are nmap tools on the internet that works on Windows. But, mapping AF_PACKET directly over that functionality is not feasible because of our commitment to compatibility. We are seriously discussing with the core networking team to light up these scenarios, now that it is pretty high on user voice (thanks for the feedback). As @benhillis mentions, some of these will take time given the surface area. Things are not out of reach technically, if there is demand.

@therealkenc  ... Having config.guess return the same result for the two platforms is nonsensical.

That is one thesis. But it isn't me or Microsoft you have to convince. You need to convince the GNU maintainers to accept your patch that adds the new triplet.

uname -r | sed -n 's/.*\( *Microsoft *\).*/\1/p'
will output "Microsoft"
Guess that will be pretty unique for WSL :D

@benhillis I patched systemd to detect WSL1 as a container https://github.com/systemd/systemd/pull/11932 . Now with WSL2 on the horizon I'm wondering how those two could be reliably detected as different environments? WSL2 seems to be closer to a VM, but it is expected to be different from a full Hyper-V VM.

With CMake, the check can be simply
if (CMAKE_SYSTEM_NAME STREQUAL "Linux" AND CMAKE_HOST_SYSTEM_VERSION MATCHES "Microsoft")
  set(WSL True)
endif()

if (WSL)
  message("Doing WSL-specific stuff...")
endif()

uname -r | sed -n 's/.*\( *Microsoft *\).*/\1/p'
will output "Microsoft"
Guess that will be pretty unique for WSL :D

In my WSL2 Ubuntu image, it does not. I believe it might be because microsoft is lower-cased:
Adjusting the regex to include /i should work in either case:
$ uname -r | sed -n 's/.*\( *Microsoft *\).*/\1/ip'
microsoft

I do have the following environment variables present when I open a WSL terminal, though:
$ env | grep -i wsl
WSL_INTEROP=/run/WSL/18840_interop
WSL_DISTRO_NAME=Ubuntu

@rbalint @benhillis et al: I've just committed a change so that under WSL2 /proc/sys/kernel/osrelease will be of the form major.minor.patch-microsoft-WSL2-flavour, so for example:
4.19.112-microsoft-WSL2-standard
This should make it both deterministic and unique, and at the same time be compatible with the previous checks that looked for the "WSL" substring, like the systemd one.
The "microsoft" substring could appear in non-WSL2 kernel images as well, so it shouldn't be relied upon to find out if one is in WSL.
This should trickle down in the public at some point in the future - not really involved with that side of things so can't say for certain :-)

The "microsoft" substring could appear in non-WSL2 kernel images as well, so it shouldn't be relied upon to find out if one is in WSL.

This is what I was concerned about. Thank you for addressing it 🙌.

This should make it both deterministic and unique, and at the same time be compatible with the previous checks that looked for the "WSL" substring, like the systemd one.

Perfect!

@rbalint @benhillis et al: I've just committed a change so that under WSL2 /proc/sys/kernel/osrelease will be of the form major.minor.patch-microsoft-WSL2-flavour, so for example:
4.19.112-microsoft-WSL2-standard
This should make it both deterministic and unique, and at the same time be compatible with the previous checks that looked for the "WSL" substring, like the systemd one.

Looking at https://github.com/microsoft/WSL2-Linux-Kernel, I see that the change to include WSL2 was apparently applied just to the 5.4.y kernel branch (and version components are in a slightly different order: CONFIG_LOCALVERSION="-microsoft-standard-WSL2"), and the 4.19.y branch still has CONFIG_LOCALVERSION="-microsoft-standard".

The "microsoft" substring could appear in non-WSL2 kernel images as well, so it shouldn't be relied upon to find out if one is in WSL.
This should trickle down in the public at some point in the future - not really involved with that side of things so can't say for certain :-)

Recently WSL2 support was backported to Windows 10 versions 1903 and 1909, and apparently that backport still uses the 4.19.y kernel with the same -microsoft-standard version string which does not contain WSL2. If that backport would stay with the 4.19.y kernel branch for its lifetime, some solution for detecting those WSL2 environments would be needed.
I'm thinking about the following solution:

If /proc/sys/kernel/osrelease contains either the capitalized Microsoft substring or the all-caps WSL substring, the environment is considered to be WSL without any further checks.
If /proc/sys/kernel/osrelease contains the lowercase microsoft substring, this might be WSL2 with the 4.19.y kernel, or it might be something else from Microsoft, therefore some additional check is needed. What check could be used here? Initially I thought about testing whether the /run/WSL directory exists, but apparently that directory disappears when interop is turned off in /etc/wsl.conf, so it's not a 100% reliable test.

Could the existence of the /usr/sbin/wslpath symlink, and/or the success of something like wslpath -w /, be used as a fallback test for those old kernel versions? Is wslpath -w / guaranteed to succeed in the WSL environment?
Or maybe the first test after finding microsoft in osrelease would be to check for the /run/WSL directory; if it exists, consider the environment to be WSL; if it does not exist, try running wslpath (obviously I would want to avoid running external tools, but just the existence of /usr/sbin/wslpath might give a false positive if someone used WSL to prepare the system image and then just packed it into a tarball and placed into a different environment; /run is usually tmpfs, so should be safer against bringing its contents from another system).
@bluca Maybe there is another solution for detecting those 4.19.y-based WSL2 environments?

(and version components are in a slightly different order: CONFIG_LOCALVERSION="-microsoft-standard-WSL2"), and the 4.19.y branch still has CONFIG_LOCALVERSION="-microsoft-standard".

Yeah, some tools mistakenly took a dependency on the exact string "microsoft-standard" being there - they have been fixed since, but we swapped the order to try and keep backward compatibility.
Let me check where the 4.19.y branch is delivered from. If it's still released, then I can add the WSL2 suffix there too. I would advise against taking dependencies on anything else, as things like /run and /usr/sbin can and are manipulated by the distro of choice, so there's no guarantee.

What about /proc/sys/fs/binfmt_misc/WSLInterop? Looks like that name is hardcoded in /init (which is provided by the WSL subsystem, not by the distro), and the registration is performed even when interop is disabled. Although the distro can choose to unmount the binfmt_misc FS from there, this case could just be declared as unsupported (and if something decides to unregister that handler, interop will be broken for all concurrently running WSL2 distros, because they run as containers in a single shared Linux VM). What happens in some future WSL releases is also not really important, because that detection code would only be used when a 4.19.y-microsoft-standard kernel is encountered, and hopefully the kernel would be upgraded to something marked WSL2 before any significant changes in those places.
(Actually for my immediate use case even testing for /run/WSL could be enough, because a WSL environment with disabled interop won't work for me anyway — the reason why I want to detect WSL is that I want to call Windows utilities which access USB devices in that case instead of trying to use equivalent Linux tools for that.)

the reason why I want to detect WSL is that I want to call Windows utilities which access USB devices in that case instead of trying to use equivalent Linux tools for that.)

In which case doing any kind of which lookup for some .exe like explorer.exe is probably sufficient for those purposes...

@bjeanes Thanks for reminding me about that very simple solution. Actually in some cases I already use powershell.exe (cmd.exe is useless because of its restriction for UNC paths), so I could probably just use that.

This method does not use external processes.
https://gist.github.com/abl/d004dcad84a16ddd670f5337ba5b896d
if [[ -f "/mnt/c/WINDOWS/system32/wsl.exe" ]]; then
  # We're in WSL, which defaults to umask 0 and causes issues with compaudit
  umask 0022
fi

if [[ -f "/mnt/c/WINDOWS/system32/wsl.exe" ]]; then

That method assumes that the 9p automount point hasn't be changed or turned off with wsl.conf. Use the osversion. There is a more recent landing zone at #4555.

What about checking for /etc/wsl.conf as a fallback if the directory /run/WSL doesn't exist? It sounds like you would need at least one of those two filesystem nodes.
Something like this bash code is what I have in mind:
if [[ -f "/run/WSL" ]] || [[ -f "/etc/wsl.conf" ]]; then
    echo "is wsl"
fi

WSL in /proc/sys/kernel/osrelease is supported everywhere and cannot be broken by the distro image, since it's provided by the kernel.

Since the distinction between WSL1 and WSL2 is that the first runs inside a container while the second runs in a virtual machine, we can make use of "systemd-detect-virt --container" to differentiate from both environments.
if [ -n "${WSL_DISTRO_NAME}" ]; then
  # In WSL but which one?
  virt_container="$(systemd-detect-virt --container)"
  case ${virt_container} in
    wsl)
      echo "This is WSL 1"
      ;;
    none)
      echo "This is WSL 2"
      ;;
    *)
      echo "Don't known ${virt_container}"
      ;;
  esac
fi

@BeErikk and @therealkenc, what about CBLMariner? Does this method not apply to that operating-system? It is Alpine Linux, which is as much Linux as all else except WSL.

What about systemd-detect-virt?
Responds with wsl

@mlromramse, and returns none on bare metal. That's not bad.


Incorrect embedding dimension  after training

I want to use dna2vec for E. coli genome.
When I set 2<=k<=8, I got (86479,100);
When I set 3<=k<8, I got (86614,100), and the correct dimension should be (87360,100) that $87360+16=4^2+4^3+4^4+4^5+4^6+4^7+4^8$.
So I don' know why I got 2 different results.
I also check every Kmer from 2 to 8, I find the dimension is correct from 2 to 7.
However, in k=8, the dimension is (64450,100) rather than (65536,100), and $65536-64450 != 87630-86614$.
This is horrible! There is nowhere to match.

@pnpnpn please take a time to help me, it is important for me, thanks!
The E. coli genome can be downloaded from https://regulondb.ccg.unam.mx/menu/download/datasets/files/Gene_sequence.txt.
The config:
inputs: inputs/E_coli_K12/*.txt
k-low: 2
k-high: 8
vec-dim: 100
epoch: 10
context: 5
out-dir: results/E_coli/

Today, I make a comparation between kmers of embedding vector and the complete kmer composition where 3<=k<=8.
I find there are two difference sites:

the occurence of some kmer compisitons is low frequency；
there is no occurence of some kmer compisitons

So, I'd like to know if there is a better way to solve a such situation when I make a embedding operation.  After all there are some kmer compositions lacking when embedding. Thanks!
@pnpnpn @aldro61 @alevenberg

I found that it seems to be related to parameter min_count, but why the embedding vector got from 2<=k<=8 and 3<=k<=8 don't match?

Maybe your problem has something to do with this place. When reading the source code, you will find that when extracting k-mers, they are not completely extracted from start to end of a sequence, but rather there is randomness：
generators.py
    @staticmethod
    def random_chunks(rng, li, min_chunk, max_chunk):
        """
        Both min_chunk and max_chunk are inclusive
        """
        it = iter(li)
        while True:
            head_it = islice(it, rng.randint(min_chunk, max_chunk + 1))
            nxt = '' . join(head_it)

            # throw out chunks that are not within the kmer range
            if len(nxt) >= min_chunk:
                yield nxt
            else:
                break

Because the human genome is relatively large, after random sampling, it is likely to obtain all combinations of k-mers. However, for the genome of E. coli, which is much smaller, the sample size is relatively small, so it is possible that some k-mers were not included in the statistics you mentioned earlier.


The application panicked (crashed). Message:  No target contract Location: utils/src/lib.rs:146

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[x] Foundryup

What version of Foundry are you on?
forge 0.2.0 (d7733ee 2022-10-03T00:08:41.50531996Z)
What command(s) is the bug in?
forge test
Operating System
Linux
Describe the bug
Running into the following issue when running forge test.
The application panicked (crashed).
Message:  No target contract
Location: utils/src/lib.rs:146

This is a bug. Consider reporting it at https://github.com/foundry-rs/foundry

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   1: __libc_start_main<unknown>
      at <unknown source file>:<unknown line>

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
/home/runner/work/_temp/obfusedworkername.sh: line 1:  2819 Aborted                 (core dumped) RUST_BACKTRACE=full forge test -vvv --gas-report --force
Error: Process completed with exit code 134.

This occurs when running forge test with combinations of the flags -vvv, --optimize, and --gas-report.
This does not occur on my local, it only occurs when running in a GitHub action context.

hmm, this looks like a linking issue.
looks like you're running this from a script, could you check that the root path is correct?

@mattsse Thank you for the quick response. I just double checked our path where we are running forge test and it seems correct (the same directory as where I run it in my local).
I should also note this job was running without crashes before. The only common difference between failing jobs and successful jobs is some new Solidity contracts and Solidity Forge tests that we have added.

is some new Solidity contracts

those are checked in? it works locally but not in CI?
is this public?
it looks like the contract depends on another contract that we don't find in the project graph.

@mattsse Gotcha - I'll take a look at the contract dependencies and see if one of them is incorrectly referenced

also try forge tree
maybe there's something off with different versions

Hmm forge tree doesn't seem to be outputting any error messages

@mattsse The updates you merged into main were extremely helpful.
Now I am able to reproduce the issue locally (I suspect some artifact in my local foundry cache was preventing the error from occurring) and I get a helpful error message:
The application panicked (crashed).
Message:  No target contract named FiduHelpers.json:FiduHelpers
Location: utils/src/lib.rs:151

However it seems like my path to FiduHelpers.json is correct where it is referenced in a separate solidity files.
FiduHelpers.sol has a pragma solidity ^0.8.16; statement at the top of the file, and the contract that imports it also has a pragma solidity ^0.8.16; statement at the top of the file.
I noticed Hardhat was compiling the build artifacts into two separate Solidity version named files FIduHelpers.0.8.16.json & FiduHelpers.0.8.17.json, and I guessed that Forge might be doing something similar under the hood during compilation.
I also noticed the following under our solidity-files-cache.json:
    "contracts/library/FiduHelpers.sol": {
      "lastModificationDate":<PHONE_NUMBER>316,
      "contentHash": "f237dca93231eb55cc4012593c0eea8b",
      "sourceName": "contracts/library/FiduHelpers.sol",
      "solcConfig": {
        "settings": {
          "optimizer": {
            "enabled": true,
            "runs": 200
          },
          "metadata": {
            "bytecodeHash": "ipfs"
          },
          "outputSelection": {
            "*": {
              "": [
                "ast"
              ],
              "*": [
                "abi",
                "evm.bytecode",
                "evm.deployedBytecode",
                "evm.methodIdentifiers",
                "metadata"
              ]
            }
          },
          "evmVersion": "london",
          "libraries": {}
        }
      },
      "imports": [],
      "versionRequirement": "^0.8.16",
      "artifacts": {
        "FiduHelpers": {
          "0.8.17+commit.8df45f5f.Darwin.appleclang": "FiduHelpers.sol/FiduHelpers.0.8.17.json"
        }
      }
    },

When I pin FiduHelpers to Solidity 0.8.16 by modifying the pragma statement in FiduHelpers to pragma solidity 0.8.16;, the error no longer occurs.
I also see these changes in the solidity-files-cache.json file:
    "contracts/library/FiduHelpers.sol": {
      "lastModificationDate":<PHONE_NUMBER>358,
      "contentHash": "9c660b81b0dde7332e6ce49b4c49971e",
      "sourceName": "contracts/library/FiduHelpers.sol",
      "solcConfig": {
        "settings": {
          "optimizer": {
            "enabled": true,
            "runs": 200
          },
          "metadata": {
            "bytecodeHash": "ipfs"
          },
          "outputSelection": {
            "*": {
              "": [
                "ast"
              ],
              "*": [
                "abi",
                "evm.bytecode",
                "evm.deployedBytecode",
                "evm.methodIdentifiers",
                "metadata"
              ]
            }
          },
          "evmVersion": "london",
          "libraries": {}
        }
      },
      "imports": [],
      "versionRequirement": "=0.8.16",
      "artifacts": {
        "FiduHelpers": {
          "0.8.16+commit.07a7930e.Darwin.appleclang": "FiduHelpers.sol/FiduHelpers.json"
        }
      }
    },

I am getting this same issue now in my Github Action CI:
Compiler run successful!
The application panicked (crashed).
Message:  No target contract named contracts/libraries/SafeDecimalMath.sol:SafeDecimalMath
Location: utils/src/lib.rs:[26](https://github.com/Kwenta/token/actions/runs/5560678914/job/15063354666#step:9:27)9

Did you work out what this issue is?

This is likely fixed, we refactored library linking and we've had many other improvements


Provide information about message instead of only the payload in unfiltered_messages

When using unfiltered_messages to receive all MQTT messages it would be useful if information about the message was provided instead of just the payload. For example, the topic field of the message at minimum would be useful.
This could be achieved by passing msg to messages.put_nowait in _cb_and_generator instead of msg.payload. The downside is that this exposes an instance of a class from mqtt.paho.

Thanks for taking interest in the API. I'm open to changes. Let's have a look.

When using unfiltered_messages to receive all MQTT messages it would be useful if information about the message was provided instead of just the payload. For example, the topic field of the message at minimum would be useful.

Sounds reasonable. This way, asyncio-mqtt feels more like a wrapper around paho-mqtt, which is the intent.

This could be achieved by passing msg to messages.put_nowait in _cb_and_generator instead of msg.payload

Yup, it is indeed a simple change in the implementation. I like that.

The downside is that this exposes an instance of a class from mqtt.paho.

Specifically, the MQTTMessage class. Said class is simple and well-defined. I have no problem with exposing it directly. This follows the "asyncio-mqtt is merely a wrapper around paho-mqtt" argument.
Of course, this is a breaking change but I vote for it in these early stages of the API.
Thanks again. Do you want to make the pull request or should I just do the change?

I'm happy to send a PR, thanks for the useful library!


Failed assertion: line 3874 pos 15: 'crossAxisAlignment != CrossAxisAlignment.baseline || textBaseline != null': is not true.

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

@for-that-case you need to be more specific what the issue is, besides you should check stackoverflow for app related errors which you face it's quite probable someone else had ran into the same thing before. If none of that works create an issue here with proper reproduction steps and logs.
Thank you

Hi @for-that-case,
When opening an issue, please provide some or all information mentioned in issue template.

issue template
If you are looking for support, please check out our documentation
or consider asking a question on Stack Overflow:
- https://flutter.dev/
- https://api.flutter.dev/
- https://stackoverflow.com/questions/tagged/flutter?sort=frequent

If you have found a bug or if our documentation doesn't have an answer
to what you're looking for, then fill our the template below. Please read
our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports

Steps to Reproduce

Please tell us exactly how to reproduce the problem you are running into.

Please attach a small application (ideally just one main.dart file) that
reproduces the problem. You could use https://gist.github.com/ for this.

If the problem is with your application's rendering, then please attach
a screenshot and explain what the problem is.

1. ...
2. ...
3. ...

Please tell us which target platform(s) the problem occurs (Android / iOS / Web / macOS / Linux / Windows)
Which target OS version, for Web, browser, is the test system running?
Does the problem occur on emulator/simulator as well as on physical devices?

Target Platform:
Target OS version/browser:
Devices:

Run your application with `flutter run --verbose` and attach all the
log output below between the lines with the backticks. If there is an
exception, please see if the error message includes enough information
to explain how to solve the issue.

Run `flutter analyze` and attach any output of that command below.
If there are any analysis errors, try resolving them before filing this issue.

Finally, paste the output of running `flutter doctor -v` here.

Closing, as no information is provided.


BuildCacheService#store should be asynchron

Assume that I implement my own BuildCacheService.
Currently the BuildCaceService#store has to be synchronously.
Which means that it will block the whole Gradle build.
Expected Behavior
From my point of view there is nothing against to make BuildCacheService#store asynchronously somehow.
The cached artifacts could be saved in the local cache anyway. And even if - because storing took some time - another Gradle Build have already started the store could be asynchronously...
So basically my request is to make store asynchronously :)
Current Behavior
The BuildCacheService#store is synchronously.
I already tried it to move to another thread with new Thread().... But then the cache can't be saved because it raises a FileNotFoundException.
I already talked about this behaviour in Slack with @lptr.
See the details below 👇

Context
Currently I implement my own "remote" BuildCacheService.
And I observer that the store method blocks the whole build because my server "take some time".
But as I want to have blazing fast builds I wanted to make this think asynchronously.
Steps to Reproduce (for bugs)
Implement your own BuildCacheService and move the "saving" of the artifact into another thread:
object: Thread() {
  override fun run() {
    Thread.sleep(10000)
    // Here I create a test file of the artifact and save it somewhere locally
  }
}

👆 This fails
Notes
As I understood @lptr correctly this is already on your roadmap.
But because I found no issue about it I thought I could open one to make this more public and trackable 😇

Thanks for reporting @StefMa!


Draft: Configurable no-reminder message pattern

Have a configurable blocklist message or pattern and when encountered no reminders are sent.
Reference: https://progress.opensuse.org/issues/106368

Now if you could just fix the style issues I have introduced :)

Now if you could just fix the style issues I have introduced :)

There were issues even before, I expected changes so I did not run black yet.


Wireframes

As a future store owner, I want to decide what my store will look like, so that I can have a store I'm happy with.

create wireframes
ensure wireframes are shareable and safe from loss (i.e. In the cloud)

Uploaded to google drive, I need to present them.


Add new custom block "DetailsBlock" with expanding answers and demonstrate it in a BreadPage and in a new FAQ page.

@lb- suggested adding a DetailsBlock to showcase a custom block with its own HTML template. The DetailsBlock includes three fields: summary (CharField), content (RichTextField), and open (BooleanField, defaulting to open). This block is ideal for creating an FAQ page with expanding answers and allows for the use of semantic and modern HTML.
Changes Made:

Created a DetailsBlock class inheriting from StructBlock with the specified fields.
Added the DetailsBlock to the StreamField used by other pages for their content, providing them with the option to include a details block.

Created a template, details_block.html, for rendering the DetailsBlock.
Added CSS selectors for the DetailsBlock summary and content in the main CSS file.
Demonstrated the usage of the DetailsBlock in a bread page.

Implemented a standalone StreamField with only the DetailsBlock option, showcased in a new FAQ page of the StandardPage type.

Created sample data for both the bread page and the FAQ page, stored in bakerydemo/base/fixtures/bakerydemo.json.

Added the FAQ page to the navigation menu.

@gzark1 can you close this PR if the newer one is preferred

Closing in favour of #425.


Removal of unused imports leads to syntax error

See #1206
Running ruff --select F401 --fix against
x = 1; import sys
import os

if True:
    x = 1; import sys
    import os

produces

if True:

:)

I feel like the else should be:
Ok(Fix::deletion(stmt.location, stmt.end_location.unwrap()))

...but... why didn't I do that in the first place?

(At least, that logic does the right thing for the case above.)

I'm guessing it's a formatting thing, the version above doesn't leave behind as many empty newlines. That's my guess at least. We should probably either do Ok(Fix::deletion(stmt.location, stmt.end_location.unwrap())) and accept the newlines (Black will clean them up), or only do the above when the statement is the only statement on the line (which will require looking at the text content, probably).

What do you think, @squiddy?

I think I saw you mentioning that you plan for ruff to become a formatter itself. With that in mind, I'd slightly prefer accepting newlines over introspecting the line further. Let's have black (or humans) fix the newline issue and let ruff deal with it eventually.
The fix ideally can also handle this scenario:
import sys; import bar
bar

Removing just the statement, based on its location, yields:
; import bar
bar

(Is the latter invalid syntax? Or just undesirable?)

Hehe, now I needed to check myself again. It is invalid.

Ok cool :)

I am working on this, it's just a bit tricky. But I think I've mostly figured out the rules.


Django IntelliSense in html files doesn't work well.

Describe the bug

Steps to Reproduce

Create a Django Web Project.
Navigate to app/about.html.
In a "Django Web Project", validate html completions in app/about.html.

Expected behavior
Html completions appear when typing '<' and contain the standard expected set of html elements valid for that position.

Additional context and screenshots
When "<" is input, "<<" is displayed.

@ttSpace This doesn't repro for me on Microsoft Visual Studio Enterprise 2022 (64-bit) - Int Preview Version 17.7.0 Preview 3.0 [33813.580.main], could you check again? Thanks.

@StellaHuang95 I cannot repro in today's build 17.7.0 Preview 3.0 [33814.347.main],  Python Package: 17.0.23150.1.


[CakePHP] Update release policy link

The new link gives more information on EOL dates.

Discussed in https://github.com/endoflife-date/endoflife.date/pull/2268/files#r1064428402.

This field name is confusing on endoflife.date. IMHO it should be named supportPolicyLink because that's the "more information" link displayed at the end of the article that is supposed to give more details on how the product is managing its support, EOL dates, and versions.
Linking to the security policy was also proposed but it is not the best choice either.
It would be great if someone in the CakePHP team could also document what's planned for 4.x and 5.x on https://github.com/cakephp/cakephp/wiki.

Going forward the CakePHP team will continue to support 4.x and develop 5.x. Once 5.0.0 is released, 4.x will receive bugfixes for 24 months, and security fixes for 36 months.

@ravage84 a review from you would be much appreciated.

Note that the removed link will be reintroduced in the project description in #2291.

Perhaps the wiki should link to the Release Policy as well?
How about policyURL or policyLink instead as the field name? We can have some guidance as to what we prefer (something like "Support Policy > EOL Page > Release Policy > Versioning Policy") but as our guidance says - these pages should be hosted/linked together - so linking to one should ideally work for most users.

@ravage84 suggested change for the wiki:

CakePHP core
branch
PHP min
PHP max
Release Policy

2.x EOL
2.x
PHP 5.4
PHP 7.4
NA

3.x EOL
3.x
PHP 5.6
PHP 7.4
NA

4.x
4.x / 4.next
PHP 7.2
Latest
https://book.cakephp.org/4/en/release-policy.html

5.0 (upcoming)
5.x
PHP 8.1
Latest
https://book.cakephp.org/5/en/release-policy.html

How about policyURL or policyLink instead as the field name?

This name does not convey any meaning (e.g. which policy ?). Maybe eolPolicyLink, that's what people coming to endoflife.date are looking for IMHO.

merging this, the wiki is much more relevant for us. Will create a new issue for field name

@marcwrobel thank you for your proposal. We can work with that for the moment.
The CakePHP team is working on a release/support policy page but it's not ready and at the final URL, yet:
https://github.com/cakephp/cakephp/wiki/End-of-life-prototype