Auto-Completion issues in Anaconda Python 2.7

Description of your problem
Just after installation of Anaconda Python 2.7, for win64 bits,
launching Spyder, Auto-completion does not work.
Setup is Python 2.7.12 64bits, Qt 4.8.7, PyQt4 (API v2) 4.11.4 on Windows
What steps will reproduce the problem?

Just installed  Anaconda Python 2.7, for win64 bits,

What is the expected output? What do you see instead?
SOLUTION
https://github.com/ContinuumIO/anaconda-issues/issues/768
Install JEDI 0.8.1
pip install jedi=0.8.1
Versions and main components

Spyder Version:  2.3.9
Python Version: 2.7
Operating system:
Python 2.7.12 64bits, Qt 4.8.7, PyQt4 (API v2) 4.11.4 on Windows

Dependencies
Please go to the menu entry Help > Optional Dependencies (or
Help > Dependencies), press the button Copy to clipboard
and paste the contents below:

Jedi 0.9.0 support was added for Spyder 3.0 only. Sorry, but we can't make it work for Spyder 2.3.9 because of technical limitations.


Forbidden error with Library.GetTracks datas

Hello, I bought error "Forbidden" when get Library.GetTracks datas. Any ideas why I'm getting this error?
My code:

ClientCredentials does not support accessing user-based data.
See table of https://johnnycrazy.github.io/SpotifyAPI-NET/docs/auth_introduction

Thanks for answer.


Using a fully featured encrypted filesystem

I am wondering if this project would be better using one of the existing encrypted filesystem for a private dapp's filesystem.  The benefit of using one that has already been written is that it has undergone peer review and performance and security testing.
https://github.com/MatrixAI/js-encryptedfs
The "ephemeral key" generated by peerbit could be the AES-GCM key used by an encrypted filesystem. Arbitrary access, streaming, and better privacy through random fragmentation.
https://github.com/dao-xyz/peerbit/blob/master/packages/utils/crypto/src/encryption.ts#L97
It is better to use separate keys separate needs. One KDF can be used for data at rest and another for transport. The libp2p world developed the noise protocol for their encryption needs because it supports broadcasting  and multicasting using a shared key.
https://www.wolfssl.com/tls-1-3-versus-noise-protocol/
Some libp2p clients are already using noise for encrypted broadcast/multicasting. But there isn't a really good encrypted filesystem for IPFS.  One of the best e2e protocol is of course the Signal protocol, which is what Berty is using with orbitdb and there is a javascript port:
https://github.com/signalapp/libsignal-protocol-javascript
https://berty.tech/docs/protocol

Thank you for the post. I have to spend some time digging into the references. These are great ideas.
I agree with you on separate keys for separate needs. On the other hand one have to value the importance of keeping a codebase somewhat simple. It is a tricky balance.  It is actually possible with the current implementation to have different encryption for the commits and for the peer communication.
I have spent a fair amount of time going through the signal encryption scheme. I was heavily inspired by the earlier version of Signal when doing the implementation. But there are some areas I am still exploring. The main challange has been not to introduce privacy features without thinking about what constraints this would impose on future wanted features. If all features of libsignal would be implemented the security has to be optional so you still can build apps that still can span the whole privacy, discoverability, performance space.
Yes, out of the box I have not been confident relying on the encryption features libp2p provides natively, but perhaps this could be something to consider in the future for performance improvements.
Will come back later with a more detailed answer regarding the references above.

peerbit is such a huge idea that it has a splash zone, where other projects also need a good solution for the same common problems.  To help with early growth it is best to focus on doing one thing and doing it well and encouraging adoption of a tech that devs normally wouldn't see.
Signal has vetted and approved by ex-NSA contractor Edward Snowden. Signal has perfect forward security (PFS) and messages can arrive out of order, which is why berty has had good success pairing it the signal protocol with orbitdb.
In an ideal world if every app used the best in class,  the Signal protocol being an open standard could be adopted by any number of projects that can now support Berty chat by simply supporting the same encrypted transport layer with libp2p RPCs.
The same goes for a filesystem. Multiple dapps could share a gdrive-style folder which has encrypted access control. using peerbit with zk membership means you don't need to pay gas fees to have enforce the R/W access controls on the filesystem. Fuse works in JavaScript so you can using one of the more popular encrypted filesystems like securefs on top of IPFS. A dapp developer is going to want a debug tool to mount a folder on their desktop, something FUSE does on a wide range of platforms.  Another bonus of having encryption on the FS layer is you can have multiple peerbit databases, each with their own permissions that share one application context.  So you can have user enabled chat with pub/sub, or user-supplied form posts, and then admin controlled wiki powered by a document db.

peerbit is such a huge idea that it has a splash zone, where other projects also need a good solution for the same common problems. "do one thing and do it well" applies here as well. To help with early growth of peerbit is best to focus on doing one thing well that is new and encouraging adoption of a tech that devs normally wouldn't see. In the case of peerbit it is private search - so make sure that peerbit has the best private search.

Yes. Well, how I see it is, as a { shared,  discoverable,  private } state. Basically approaching the discoverability/privacy problem, which usually are two opposing forces.

In an ideal world if every app used the best in class, the Signal protocol being an open standard could be adopted by any number of projects that can now support Berty's chat by simply supporting the same encrypted transport layer with libp2p RPCs. Now Berty becomes more useful, and so do other dapps. That is the Open Source ethos and how lasting platforms are built.

Absolutely. I totally agree with you. The challange is usually that not all apps require the same amount of security. An anecdote, not all apps are suited to be on blockchain. A transaction sending 1$ should not use the same security guarantees as for a 1000000$ transaction. Problem with many solution, in general in the security and privacy space, is that the tools are not adaptive to the problem at hand, which is an inefficiency I want to tackle.

The same goes for a filesystem, there should be one project that does this well. Multiple dapps could share a gdrive-style folder which has encrypted access control. Using peerbit with zk membership means you don't need to pay gas fees to have enforce the R/W access controls on the filesystem.

Yes, this is something I have planned on working on quite soon.

Fuse works in JavaScript so you can using one of the more popular encrypted filesystems like securefs on top of IPFS. A dapp developer is going to want a debug tool to mount a folder on their desktop, something FUSE does on a wide range of platforms. Another bonus of having encryption on the FS layer is you can have multiple peerbit databases, each with their own permissions that share one application context. So you can have user enabled chat with pub/sub, or user-supplied form posts, and then admin controlled wiki powered by a document db.

I am not familiar with Fuse, but I see what you are after. As of know you would have encryption on the FS layer, but that is controlled by whomever is making the commits to the database. As a replicator I would not have any say in how things are encrypted at rest. In fact, I can be a replicator of databases without ever be able to know the contents, just that someone are making commits and someone else is reading things (verified by ZK membership in the future).  Fuse might perhaps help the separation of concerns here (again I am not familiar with it, so I have to read more about it before I can say anything meaningful)

One last thing is a note on compliance, which if done right here could be a major market differentiator.
If someone needs a fintech or medical data app, or to store identifying medical data or other PII collected by your phone then the app will have to be reviewed by a consultancy.  In the medical space, it is common to have yearly mandatory reviews from a security team to satisfy insurance. I worked as a consultant for many years doing reviews for the medical and financial world, and I am in the top 10 for crypto and security on SO:
https://stackoverflow.com/users/183528/rook
To make the review process as easy as possible, you want to rely on security systems that have already been reviewed, or even better; something that the assessment team uses themselves (like SSL/TLS or gmail).  Signal is very popular in the hacker/infosec community and the same is true for encrypted filesystems like EncFS, which is an established project that has been assessed been approved to work in sensitive industries.
https://en.wikipedia.org/wiki/EncFS

The security guarantees for 0$ here are pretty amazing. Doing any kind of access control on chain is expensive, there

Yes! I am really excited about it.

Let me know when you are ready to start on a production-ready C++ version of this, I know some other people that might want to join. C/C++ is the future.
Thank you! I will keep in touch.

One last thing is a note on compliance, which if done right here could be a major market differentiator.

Yes it is good to consider things like this if you want to big adoption of the things you build, and perhaps also create incentives for migrations from legacy system and show that you can still act in compliance.
Its cool that you have this background, I see the way you are able to talk about all kinds of topics in detail that you have been in this space for quite a long time. I greatly appreciate all the ideas you have provided to the project!

I have been in this space for a while, although DHTs are nothing new I am excited to see the kind of features orbit/peerbit are putting out - Berty especially. I think we are closer than ever to having a good devops toolchain for these kinds of DHT dapps.
Another project similar to peerbit that is under active development is redwood:
https://github.com/redwood/redwood
Freenet and PerfectDark both have DHT client platforms with some form of a shared database.  Freenet had anonymous chat and forms over DHT almost 10 years ago, but it was very slow and building client apps for freenet is still baffling.  Developers can't just pick up and run with the libraries and frameworks they already know and love, having to learn something new is a non-starter in a hackathon where every moment matters.
... All of these projects lack adoption, adherence to standards and no thought of interoperability or compliance.  They are all building siloed monoliths for an audience of developers that have no shortage of bright platforms to build on.

I think we are closer than ever to having a good devops toolchain for these kinds of DHT dapps.

I think soo too!

Another project similar to peerbit that is under active development is redwood:
https://github.com/redwood/redwood

Spent some time digging through this. It is a very interesting project. Especially how different the developer experience is with the approach they are going with. Like, you have minimal amount of code surrounding the state, but basically patches are submitted that contains code that can be interpreted to modify the state.. It is going to be interesting too see how it unfolds

... All of these p2p db projects lack adoption, adherence to standards and no thought of interoperability, compliance, operations and maintenance. We can talk about fancy things to do with crypto, but at the end of the day: it is all in the doing - the devops limitations prevent adoption. All of these p2p dapp platforms are all building siloed monoliths for an audience of developers that have no shortage of bright and alluring platforms to build on. Bridging this gap is it's own engineering problem.

Yes. I think there is usually too long jump to adopt something new, especially if you are going from Web2 -> Web3. People don't have infinite amount of time to explore new things, and want to get started right away and reuse as much as they can from previous experiences. In addition to this, the "new" thing has to provide some actual value that is significantly better than what you have now, like reduced costs, improved privacy, or better search etc.

A very common death of app startups in the web2 space is the cost of running the database. If you are already a CouchDB user and you are struggling you can adopt another backend to keep the app afloat without needing any kind of hosting costs.

Yes. That will be great

Another thing, regarding

All of these p2p dapp platforms are all building siloed monoliths [...]

The same problem is now very prevalent for figuring out what a "DID" should be. In my opinion this an optimization problem where the longevity of the standard depends on the entropy you are applying it for. You can do a bad one in a matter of minutes, that only solves the identity problem for your particular silo.
My idea, is that it is not super important that you create the perfect standard out of the box, but create a solution that allows a new solution in the future to easily replace it. The actual DID in some sense would be the merkle root of all identity migrations, that would yield Log(n) "computational complexity" on verification where N is standards/solutions you are compatible/have migrated from.

It is also interesting to think that really good silos eventually become standards in some sense

The same problem is now very prevalent for figuring out what a "DID" should be. In my opinion this an optimization problem where the longevity of the standard depends on the entropy you are applying it for. You can do a bad one in a matter of minutes, that only solves the identity problem for your particular silo

There is a difference between a silo and a domain.  Microsoft LDAP for domain controllers did this beautifully, LDAP is used heavily in domain access control where a corporation becomes a kind of kingdom.  Since the web0.1 space, domain names via DNS have been the domain identifier - but now in web3 we have .eth domains and really other chains what to have their own TLDs and there are projects to just help arbitrary chains get their own TLD. So who do you trust?  Do you trust the government and ICANN? Or do you even have an option of what certificate authority or naming authority you use - and simply providing that option opens doors. "Build it and they will come."

My idea, is that it is not super important that you create the perfect standard out of the box (since this is a fundamentally a hard problem since you have to consider huge set of domains and timeframe), but to create a solution that allows a new solution in the future to easily replace it. The actual DID in some sense would be the merkle root of all identity migrations, that would yield Log(N) "computational complexity" on verification where N is standards/solutions you are compatible/have migrated from.

No you fit perfectly as a research project out on the edge - sure there are projects adding privacy to Kad and IPFS - but I don't know of any other project that can do federated private search and that really changes the game.   But in order to get adoption you need standards, compliance, and agreement.  If privacy and security is the selling point, then it needs to solve compliance and be an open standard so that no one can be locked out and that new tools can be made in the ecosystem.
On the topic of merkle roots, I can't believe that redwood doesn't use them! I think the author doesn't have a background in cryptography otherwise it would be a no-brainer.  You could have the user choose a merkel root from a trusted naming authority, within that namespace the authority issues branches which represent a domain controlled by an org.    Maybe we can reach out to these maintainers,  the freenet and perfectdark community as well and pool together what works into a formal standard.

But in order to get adoption you need standards, compliance, and agreement

Yes ... !

On the topic of merkle roots, I can't believe that redwood doesn't use them!

Not sure, but I think it is more to that. These guys have explored the space for some time, I am pretty sure they have some reason (if they are not doing it)
Going to have a talk with them on the next Braid meeting showing a little Peerbit stuff and hopefully have some interesting discussion.

Maybe we can reach out to these maintainers, the freenet and perfectdark community as well and pool together what works into a formal standard.

Yes that would be good. I think I have to absord a lot of ideas/concepts coming weeks and months since there has been so much work in this space that is important to learn from, why certain parts succeeded and others failed. And also try to find synergies with projects that already exist. Implement libsignal is something I really want to do asap, but I know there will be headaches doing so, not perhaps for technical reasons, but because the problem domain that libsignal is designed for is different from this.

libsignal is going to be huge for PRISM protections and also compliance for HIPPA.  Berty said they are using some adapted signal protocol for orbitdb that still relies on ratcheting - so maybe you can take a peak at their implementation.

Yes that would be good. I think I have to absord a lot of ideas/concepts coming weeks and months since there has been so much work in this space that is important to learn from, why certain parts succeeded and others failed. And also try to find synergies with projects that already exist. Implement libsignal is something I really want to do asap, but I know there will be headaches doing so, not perhaps for technical reasons, but because the problem domain that libsignal is designed for is different from this.

Cloudflare's use of Merkle Trees in nimbus interesting:
https://blog.cloudflare.com/introducing-certificate-transparency-and-nimbus/

libsignal is going to be huge for PRISM protections and also compliance for HIPPA. Berty said they are using some adapted signal protocol for orbitdb that still relies on ratcheting - so maybe you can take a peak at their implementation.

Yes it, is going to be interesting to see how they (if they) pulled it off 🕵♂

Cloudflare's use of Merkle Trees in nimbus interesting:
https://blog.cloudflare.com/introducing-certificate-transparency-and-nimbus/

hmm


WAS_Image_Save Images output

WAS_Image_Save
an images output was added to firstly force saving before the images are sent to the next group/node and secondly to have the possibility to bypass the node. so that saving can be switched on/off if necessary and the images can still be forwarded through the node to the next node in line.

Sounds good, thank you.

its just a small change but it helps me a lot thank you very much :)


Backend should be mocked just by matching URL and method, data and others optional

When setting up my mocks, if my actual HTTP request includes data and I fail to include the data attribute in the mock request, the entire HTTP request is not intercepted.
mock( [
{
    request:
    {
	  path: '/api/user/list',
	  withCredentials: true,
	  method: 'post',
    },
    ...
] };

This fails to intercept the request and I can see my backend being hit. However...
mock( [
{
    request:
    {
	  path: '/api/user/list',
	  withCredentials: true,
	  method: 'post',
	  data:
	  {
		listItem:
		{
			name: 'new list item'
		}
	}
    },
    ...
] };

This WILL intercept the request. This was unexpected behavior to me, especially because leaving out `withCredentials` exhibits opposite behavior: the request is mocked.

Part of me feels like the HTTP request should get mocked simply by matching just the URL and method, and everything else is optional.

Regardless, this behavior should be consistent and documented.

Does this make sense?

Yes. I understand your problem, and yes that was the original behavior. I'll change it back and release soon. I will update here when ready.

Done! Just published new version 0.1.13 with the fix. Let me know how that works for you.


A lot of (Android) deficiencies are outdated

Description
As discussed in #144 I had some trouble to make it running, but now I was able to generate the code and to diff it with my existing code. While there are huge improvements for my code base regarding CI I noticed that a lot of dependencies are very outdated.
Outdated versions

The Gradle wrapper you ship 6.7; I'm currently using 8.1, but there is already 8.5 (however I'm not sure if that version is already compatible)
In a all AndroidManifest.xml is still a package attribute, that is outdated and should not used anymore AFIK
Your build.gradle references kotlin 1.6.10 (in another file even 1.3.50 was referenced) the latest version is 1.9.22
Your build.gradle references the android gradle plugin 4.1.0 the latest version is 8.3

Hi @rekire 👋  ! Thanks for opening this issue.
We need to check this dependencies, if indeed they have to be updated, would you like contributing with a Pull Request?

General I would like, but I do not really understand yet, which files I would need to edit and which would needs to be regenerated. If you have some documentation I would check what I can do.

Fair point. We don't have a CONTRIBUTING.md in this repo yet. Here are some points to get you started.

Complete the needed updates in the src/my_plugin folder. This allows you to run things locally and ensure that the changes are working correctly.
Open a PR with the changes in the src/my_plugin folder so it can be checked against the CI pipeline and go through the normal review process.
When the changes are accepted and merged into main the generate_template.yaml workflow will kick off to make the needed changes to the brick.

Hope this helps and looking forward to seeing the contribution :)


how to display multiple images

Php: 7.2
Voyager: 1.1
How to loop through images in multiple images attribute in database
people , i got an issue while diplaying multiple images , i tried the {{ Voyager::image($sld->image) }} property and it didn t work , is there any other property which it makes looping the array .

thanks

The field holds a JSON-encoded array of paths.  Just json_decode() it, loop over the result, and display them individually within the loop.

thanks

Please read again what @fletch3555 wrote.
You have to json_decode everything first, then loop through them


Fixing problems with the loader and the error state

Error state wasn't working, due to a problem with model attribute setting and loader view now is listening to loaded event  (https://github.com/CartoDB/cartodb.js/pull/1129/files#r53784263).
CR: @javisantana
Fixes #236 using https://github.com/CartoDB/cartodb.js/pull/1129/files.

[ ] Update CartoDB.js version (commit pointing to https://github.com/CartoDB/cartodb.js/pull/1129).

:es:

I feel this fix (#236) could be helpful for current examples (density-dot mainly) and probably for you too @AbelVM.
cc @saleiva


guest dvm fail

DVM: "Distributed Virtual Memory", an Arm interconnect
protocol. When sharing a process address space, TLB invalidations from the
CPU are broadcasted to the SMMU, so we don't have to send commands through
the SMMU queue to invalidate IOTLBs
guest: fail
estuary:/mnt$ ./test_sva_bind -s 0x1000 -b 0x1000 -k t
TLB test failed, broken invalidate! VA=0xffff9d3f9000-0xffff9d3fafff
host: succeed
sudo ./test_sva_bind -s 0x1000 -b 0x1000 -k t                                                                                bad status (s=66, t=3, expected)
wd_sched_work: -14
TLB test success
SUCCESS

replaced by iommufd, closed now.


MINIFICPP-2346: Replace CMake FetchContent with Conan Packager for Faster Builds

NOTE: I do want to give a heads up, this is a draft PR. I will make further progress soon.
I have included a sample of conan integration providing a faster alternative to CMake's FetchContent for building MiNiFi CPP faster first using abseil external lib dependency managed by conan. I will update the rest of MiNiFi CPP's FetchContent with conditional statements for including conan packager's prebuilt binary C++ conan package for MiNiFi.
Also kept backward compatibility for cmake FetchContent by adding two MiNiFi CPP options: one for using CMake FetchContent and the other for using the more faster approach conan packager to manage C++ external lib dependencies. With conan, usually conan will install prebuilt binary conan packages from conancenter or some other conan repo where the prebuilt binary conan packages reside. For now, we'll stick with using conancenter as it is open source.
Verified I can run conan install command from MiNiFi root folder where conanfile.py resides and successfully install abseil prebuilt binary conan package for MiNiFi C++, then ran cmake generate from MiNiFi's build folder and then started to run make. Stopped early on make since MiNiFi would try to download and build all the remaining external lib dependencies with CMake FetchContent since they arent managed by conan yet.
Also in Abseil.cmake's file, I added conditional statement to check if user set the USE_CONAN_PACKAGER option or the USE_CMAKE_FETCH_CONTENT option. Will do similar approach for the remaining external lib dependencies
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file?
[ ] If applicable, have you updated the NOTICE file?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

There are a few things we would need for this to be viable:

The python bootstrap should be updated to support selecting each extension with its dependencies installed from Conan vs FetchContent
I think CMake should be updated to allow selecting the dependency source on a per-extension basis. This is also needed to implement the first point.
(optional) If we're doing the per-extension dependency source selection, a normal find_package could be added as well, to use the system version of libs. This may not be trivial to get working, but if it works at least at a few places, it can be an easy win.
I wouldn't flood FetchContent users with "SLOW" messages. Until we can ensure that all dependencies have viable binary packages on conan center, there isn't necessarily a build speed difference. We need to discuss how to handle these cases with Conan. And even after we can ensure binary packages for all major targets, FetchContent can still be a viable option, even if it builds the packages.

Let's see how this progresses, these can be done separately as well.

@lordgamez thanks for the suggestion, I'll switch the default option to USE_FETCH_CONTENT for now. I'm excited to hear it was planned for 1.0.0 release to bring this feature to the build infrastructure. When is the planned release date, so I can track that target date?

@szaszm thanks for sharing the requirements and what you guys are looking for to make this PR viable. I will shift the updates to meet those requirements. I appreciate it.

1.0.0 will be released some time after NiFi 2.0, but there is no clear target date. We were just discussing the idea (so no commitment), as third party library builds are already taking up the majority of the build time. I think someone would have given it a second try in the following months.
I did a first try of moving everything to Conan 2-3 years ago, but it quickly got too complex. Me not being very familiar with Conan probably didn't help it.
Thanks for the contribution! :)

You will need to rebase your PR for the CI to work.

@martinzink thanks for the suggestion. I brought MINIFI-2346 to up to date with latest upstream MiNiFi C++ main branch. Ubuntu 20.04 and Docker build for integration tests passed. The other CI/CDs failed. Its probably related to some of the changes I am introducing to the build infrastructure. I have mainly been testing the updates in a Ubuntu 22.04 docker container. I haven't tested them yet on Windows or Mac OS X. Those 2 last OSs, I'd test later. I also would need to look into why CI/CD is failing too. After I finish refactoring build infrastructure to support Conan version 2 and keep backward compatibility with the standalone CMake approach, I will work toward updating the MiNiFi bootstrap py script with conan support too. I will get to the CI/CD issues as soon as I can, but those will probably be the last updates.

@james94 I'm busy with other commitments to keep up with this, but I'd like to prevent wasting too much of your time on something we can't use. We can't review a 17k diff, so it will never be merged as is stands now.
If you want to pursue this, please create a separate pull request, where you only convert a single dependency to build with conan, so we can provide feedback there, and only change what's absolutely necessary. A good first target could be OpenSSL, because it takes forever to build on Windows.
Please make an effort to keep the diff as small as possible, in the 100s if possible, but keep it under 1000. We can review many small pull requests, but not giants like this. Example: #603 didn't get any reviews, despite being a very valuable feature
As the conversion of the first dependency is reviewed, we both learn from it, and subsequent dependency source conversions will be easier. Please only pursue 1 or max 2 features at a time, so we can keep up and provide the necessary feedback. This will inevitably take a few months.
I'll also give some early feedback on things I noticed so far:

Please use a proper multi-choice option for selecting the source of a dependency instead of USE_CONAN_PACKAGER and USE_CMAKE_FETCH_CONTENT binary options. For example: MINIFI_OPENSSL_SOURCE: [conan|find_package|bundled]. The second option could keep just find_package, and rely on sources from the system. If it doesn't work, just having [conan|bundled] is fine.
Please don't include patches that are not strictly necessary to make conan builds work
Please prefix minifi-related options with MINIFI_ in cmake. Not all options follow this now, but future new CMake options should.
Please don't add new dependencies in the context of converting to Conan. For example, minifi doesn't depend on ffmpeg or libtiff at the moment. If they're needed for a new feature, the new feature needs to be a separate pull request.

Thanks for your suggestion @szaszm
I was considering to break this PR into multiple parts because like you said there is a lot to review. Actually, with each major update and commit hash, my goal was to make it easier to track each section of the new update that I made. For example with just updating OpenSSL to have USE_CONAN_PACKAGER support and backward compatibility for USE_CMAKE_FETCH_CONTENT, which impacts libminifi, we could reference my current commit hash from UPDATE (May 4, 2024) - 2d1b884 and extract out just the part for OpenSSL, so its a smaller PR following your suggestions. Once its approved, we're on the same page for what you guys are looking for, we could look toward bringing up USE_CONAN_PACKAGER support for building the whole libminifi like I do in commit 2d1b884.
I will follow up with a smaller PR for OpenSSL impacting part of libminifi.


Add a field for "elementVersion"?

I think it would be helpful to specify a version for the custom element. For example, if I add a few major properties/events to an element, I should be able to say that the element is now version 2.0.0

The assumption so far is that this file is published with an NPM package and so the containing package version is the version for everything contained within.
Thinking about this a bit more, I think we should support cases where the manifest is not necessarily associated w/ a package.json (ie, if a bunch are bundled) and we should optionally support duplicating some of the package info, like name and version, in the Package interface.

I think we should support cases where the manifest is not necessarily associated w/ a package.json

I think so too. If we take the devtools addon @matsuuu is working on, there is a need for some browser based tools to know about the custom elements they are running without having to know they came from npm. The CEM could be referenced in the source like we do with sourcemaps for such cases.

I wonder what the usecases are where we can have access to a custom-elements.json, but not a package.json.
It might be a bit double, but I do think it could be useful to have a version and even something like a packageName on the Package doc, which could be used to create URLs for things like unpkg, e.g. https://unpkg.com/${packageName}@${version}?module

Something that I've grown accustomed to from the Vim/NeoVim scene is that each plugin is named by the repo it resides in.
e.g.
Plugin Matsuuu/pinkmare can be found in https://github.com/Matsuuu/pinkmare
So to expand on the idea @thepassle proposed, it would be really nice to be able to link a web component to the github repo it resides in, and maybe other sites like npm.
As for the implementation. I'm going to assume that a big portion or people run a analysis tool on a project with a package.json, and the package.json format has a repository -field. We could take it straight from there. Other cases could be that it could be given through a configuration file or a command line argument, and then appended to the manifest.
This could allow tooling / plugin developers to link the component to a external repository with ease.

An example use case for this could be the Developer Tools I'm working on. As a lot of sites using web components ship packaged by some tool, the source can be transpiled, minified, etc. But a user inspecting said page with Web Component DevTools might be interested in "How they created this component".
As the user inspects the component, if the developers included the repository url in the manifest, there would appear a link to the github repository, if not even the exact file, for the user to follow and see the actual implementation.
This would also help people find the actual implementation source for typescript components, which are transpiled by default.

I agree with @thepassle. I think we could consider optional packageVersion and packageName fields for the entire manifest, but I don't think we should version individual declarations.


Confusing sample commands

## PACS, Overall, K=3
python data_list_generator.py --dataset PACS --target art_painting --mode overall --style adain --K 3 &
python data_list_generator.py --dataset PACS --target cartoon --mode overall --style adain --K 3 &
python data_list_generator.py --dataset PACS --target photo --mode overall --style adain --K 3 &
python data_list_generator.py --dataset PACS --target sketch --mode overall --style adain --K 3 &

As shown above, if I run the command, there would not exist a really 'target' domain, which is defined following the leave-one-domain-out setting.
Therefore, should I remove all & and choose the one our own experiment needs the most???

Yes, of course you can! Those four lines are just for leave-one-domain-out  evaluation purpose.


Improved lockdown of the keyboard and mouse

Dude @androsj! These changes are awesome! Are you cool with me including them upstream?

Sure, go ahead!I'm really glad you liked it

Dammit. I thought I was all clever pushing the Squash and Merge button but it stripped out the authorship. Hang on while I do crazy things.

Bwahaha git push --force master FTW!

Your contribution may be squashed, but it will never be forgotten!


Fix go get in auto-fork action

This PR should fix the following error in auto-fork action.
https://github.com/knative-sandbox/knobots/runs/1986629761?check_suite_focus=true
Run go get knative.dev/test-infra/buoy@master
  go get knative.dev/test-infra/buoy@master
  shell: /bin/bash -e {0}
  env:
    GOROOT: /opt/hostedtoolcache/go/1.15.8/x64
go: cannot use path@version syntax in GOPATH mode
Error: Process completed with exit code 1.

Changes

:bug: Fix go get in auto-fork action

/kind bug
/cc @n3wscott

Well, it's a bit strange but the error is cause by @version format. I guess  go's trying to detect go.mod on the filesystem.
For the reference, the similar setup is also used in other actions, e.g. see. Frankly something I haven't expected to be needed with newer go binaries.


[BUG] ToU rates do not update

Version of ha-openei
0.1.1
Describe the bug
After installing and configuring against my plan, the initial load of utility rates is correct.  However, when the change in time happens to a higher window (say 2:59pm to 3:00pm), the sensor (in my case sensor.pacific_gas_electric_co_current_energy_rate does not update to the new rate.
Expected behavior: value of sensor.pacific_gas_electric_co_current_energy_rate changes from 0.18 to 0.36
Actual behavior: value of sensor.pacific_gas_electric_co_current_energy_rate does not change after initial setup of the rate plan.
Debug log

2021-09-08 13:04:53 INFO (SyncWorker_1) [homeassistant.util.package] Attempting install of python-openei==0.1.9
2021-09-08 13:08:25 INFO (MainThread) [homeassistant.setup] Setting up openei
2021-09-08 13:08:25 INFO (MainThread) [homeassistant.setup] Setup of domain openei took 0.0 seconds
2021-09-08 13:08:25 INFO (MainThread) [custom_components.openei]
-------------------------------------------------------------------
OpenEI
Version: 0.0.1
This is a custom integration!
If you have any issues with this you need to open an issue here:
https://github.com/firstof9/ha-openei/issues
-------------------------------------------------------------------

2021-09-08 13:08:25 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.openei
2021-09-08 13:08:25 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.openei
2021-09-08 13:08:25 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new binary_sensor.openei entity: binary_sensor.pacific_gas_electric_co_approval
2021-09-08 13:08:25 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.openei entity: sensor.pacific_gas_electric_co_current_energy_rate
2021-09-08 13:08:25 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.openei entity: sensor.pacific_gas_electric_co_distributed_generation
2021-09-08 13:08:25 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.openei entity: sensor.pacific_gas_electric_co_plan_name
2021-09-08 13:08:25 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.openei entity: sensor.pacific_gas_electric_co_all_listed_rates

If I restart HA when OpenEI starts it does successfully pick up the new current correct rate, but I wouldn't expect to have to do that.
This is the relevant rate plan: https://openei.org/apps/USURDB/rate/view/60a50f795457a33a3856fb5c#3__Energy

Should be fixed in 0.1.2

I can confirm that 0.1.2 corrects this behavior.  Thanks!


Unicode decoding in docker-compose.yml

Rancher Version:
v1.1.0
Docker Version:
1.10.3
OS and where are the hosts located? (cloud, bare metal, etc):
centos7
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle v0.165.4
Steps to Reproduce:
Set an answer to a non ascii character like "è"
Results:
Rancher during the .yml parsing will throw "Failed to unmarshal Map or Slice: " and the character will be encoded as "xE?"
If you set the value to \u00e8 (unicode rapresentation of "è") no error will be thrown
Expected:
I will expect to set the special character and proper encoding should be performed.

Sorry but I don't think this is an enhancement, I wanted to report it as a bug.
With a non ascii character rancher-compose will always stop working and it's impossible to deploy.

+1

For QA - all three hyphens should be supported:
Regular: -
Option + hyphens: –
two hyphens: —
All non-ascii character should be supported for example:
œ∑˙ß®∫ƒ˜†∂˜

Make sure to test with Chinese as well - here is the related issue #5414

Tested with rancher-server version - v1.2.0-pre2-rc2 and rancher-compose version - v0.9.1-rc .
Having Non-ascii characters in docker-compose.yml and rancher-compose.yml works as expected.
Following are some of Non-ascii characters tested with:
"œ∑˙ß®∫ƒ˜†∂˜"
"±èéü−−∠∫∴♥Œ♦‰"
"–a—"


Correlation ratio in nominal.py class

Hello and thank you for this useful package. I have been calculating the correlation with nominal.py class. I have a non-linear numeric data and categorical data. I was wondering which statistical method are you using when you calculate correlation ratio with non-linear numeric and categorical data?

Correlation ratio is defined in the same way regardless if the data is linear or not. You can see the definition here: https://en.wikipedia.org/wiki/Correlation_ratio

I see thank you. Have a good day.


Implement reduceRight function

Refs: #64
Copied from #83

I've done squashing redundant commits so I think the branch is ready for merge.
I'm not authorized to merge so @nechaido, @tshemsedinov or @belochub, please, do it for me.

@nechaido, that definitely looks better though it's a bit of hassle requiring not just renaming but also moving some changes between commits.
I'll do it


Possible race condition after applying edit in Facet

Original author: thadguidry (November 17, 2010 18:09:19)
What steps will reproduce the problem?

Apply an edit in a Facet
During which time a possible Save project condition is pending or happening.
Facet tries to update/refresh after applying update and then freezes.  Facet window may even disappear if you force a Refresh on the browser trying to get anything to respond.

What is the expected output? What do you see instead?
Frozen browser window with WORKING... or Facet window left in unusable unclickable state.
Screenshot and command line trace attached.  Last instances of command line trace is a refresh on the browser after the frozen facet state.
Original issue: http://code.google.com/p/google-refine/issues/detail?id=234

No longer need this fixed. Closing.


How to find the days of phase Moon

Hello, first I want to thank you for this very nice library!
For my question, I try to find the days of new moon, for example today: 28 November 2022 is “5 days young Moon”.
Is there any idea how to get those days?
BTW: I wish to have moon eclipses, seems like is most of calculations already exist
astronomy.stackexchange.com/questions/231/what-is-the-formula-to-predict-lunar-and-solar-eclipses-accurately
Thank you

Assuming a fixed lunar cycle of 29.53058770576 days, you can multiply the phaseValue by that number to get the age of the moon in days.
--DH
Sample code
var dt=new Date("28 November 2022");
var info=SunCalc.getMoonIllumination(dt);
console.log(info.phaseValue * 29.53058770576);

Results:
4.747607392596853

Note: I did open what I believe to be a bug with phaseValue:  https://github.com/Hypnos3/suncalc3/issues/7

Seems like phaseValue >  angle changes from negative to +
``const phaseValue = 0.5 + 0.5 * inc * (angle < 0 ? -1 : 1) / Math.PI;`
Needs different calculation?

After a few calculations and tests,
seems to me that getMoonIllumination() need to set a full Date :time or timestamp otherwise gives wrong results
my tests
var dt = new Date("2024-02-09T20:00:00.00Z");
//var dt = new Date("2024-02-09");
var div = document.getElementById('slot');
var para = '';
var extra = '';
var S1 = SunCalc.getMoonIllumination(dt);
var md = new Date(S1.next.newMoon.value);
var dayopt = {weekday:'short',year:'numeric',month:'short',day:'numeric',hour:'2-digit',minute:'2-digit',second:'2-digit'};

para += '
Next New Moon: '+md.toLocaleString('en',dayopt)+'
';

	for (let i = 1; i < 31; i++) {
		dt.setDate(i);
		let info=SunCalc.getMoonIllumination(dt),
		dayMoon = Math.trunc(info.phaseValue * 29.53058770576);
		extra = (dayMoon === 0 || dayMoon === 1 || dayMoon === 29) ? 'phaseValue > '+info.phaseValue : '';
		para+= '
Day moon = '+dayMoon+' '+info.phase.emoji+' '+dt.toLocaleString('en',dayopt)+' '+extra+'
';
	};

div.innerHTML = para;

In my PC says

Next New Moon: Sun, Mar 10, 2024, 10:43:50 AM
Day moon = 21 🌗 Thu, Feb 1, 2024, 10:00:00 PM
Day moon = 22 🌗 Fri, Feb 2, 2024, 10:00:00 PM
Day moon = 23 🌗 Sat, Feb 3, 2024, 10:00:00 PM
Day moon = 24 🌘 Sun, Feb 4, 2024, 10:00:00 PM
Day moon = 25 🌘 Mon, Feb 5, 2024, 10:00:00 PM
Day moon = 26 🌘 Tue, Feb 6, 2024, 10:00:00 PM
Day moon = 27 🌘 Wed, Feb 7, 2024, 10:00:00 PM
Day moon = 28 🌘 Thu, Feb 8, 2024, 10:00:00 PM
Day moon = 29 🌚 Fri, Feb 9, 2024, 10:00:00 PM phaseValue > 0.9869340148714654
Day moon = 1 🌒 Sat, Feb 10, 2024, 10:00:00 PM phaseValue > 0.03422037458855848
Day moon = 2 🌒 Sun, Feb 11, 2024, 10:00:00 PM
Day moon = 3 🌒 Mon, Feb 12, 2024, 10:00:00 PM
Day moon = 4 🌒 Tue, Feb 13, 2024, 10:00:00 PM
Day moon = 5 🌒 Wed, Feb 14, 2024, 10:00:00 PM
Day moon = 6 🌓 Thu, Feb 15, 2024, 10:00:00 PM
Day moon = 7 🌓 Fri, Feb 16, 2024, 10:00:00 PM
Day moon = 8 🌔 Sat, Feb 17, 2024, 10:00:00 PM
Day moon = 9 🌔 Sun, Feb 18, 2024, 10:00:00 PM
Day moon = 10 🌔 Mon, Feb 19, 2024, 10:00:00 PM
Day moon = 11 🌔 Tue, Feb 20, 2024, 10:00:00 PM
Day moon = 12 🌔 Wed, Feb 21, 2024, 10:00:00 PM
Day moon = 13 🌔 Thu, Feb 22, 2024, 10:00:00 PM
Day moon = 14 🌝 Fri, Feb 23, 2024, 10:00:00 PM
Day moon = 15 🌝 Sat, Feb 24, 2024, 10:00:00 PM
Day moon = 15 🌖 Sun, Feb 25, 2024, 10:00:00 PM
Day moon = 16 🌖 Mon, Feb 26, 2024, 10:00:00 PM
Day moon = 17 🌖 Tue, Feb 27, 2024, 10:00:00 PM
Day moon = 18 🌖 Wed, Feb 28, 2024, 10:00:00 PM
Day moon = 19 🌖 Thu, Feb 29, 2024, 10:00:00 PM
Day moon = 20 🌖 Fri, Mar 1, 2024, 10:00:00 PM

Thanks, and hope to find solution for phaseValue!


Update data application to include xconf and pre-install files

Need to index the application for searching and browsing.

Add post install and git-sync as well.


Question: how to position addon-info "inline" option?

I'd like to place proptype tables in my stories as documentation. So I know I need to use the inline option, but it doesn't seem like you can customize where the inline pieces are placed - would it be possible to tell where inline should place the prop table(s) (above/below rendered story)?

@trevordmiller, the code of the addon-info that renders everything is located here
You are welcome to play with it and PR =)

Ok thanks


Network command to "rebuild" the TileList

How this would be properly leveraged I'm not entirely sure, and it wouldn't be inexpensive. It may involve manually iterating over the current tile entity list, which is something I'm not sure I want to be doing or whether I should be doing.

At this point in time, the TileList is sufficiently robust as to not require something like this, and I'm not sure how it would be properly leveraged. Potential implementation:

Iterate over every ServerNetwork (excluding Hives) and wipe tile lists
Iterate over every TileEntity (filtering ITEs) and re-mark them as incomingITEs for server tick
???

That should be sufficient to rebuild every network on the server. I may look into doing this.


Prevent goroutine leak in http service for persistent query connections

Required for all non-trivial PRs

[ ] Rebased/mergable
[ ] Tests pass
[ ] CHANGELOG.md updated
[ ] Sign CLA (if not already signed)

Required only if applicable
You can erase any checkboxes below this note if they are not applicable to your Pull Request.

[ ] InfluxQL Spec updated

Most likely, what you're trying to do isn't possible. Pipelining and CloseNotify() are documented as not compatible with each other. Can you explain to me how you're trying to use the server where you need to use HTTP pipelining? Can you show me a reproducer that causes the leaked goroutine?
It might be best just to have the server send the Connection: close header to force a new connection and prevent this issue.

I can accept that. The latest patch seems to work, so far. The reproducer is Grafana running a query with a relatively high refresh interval (e.g. 10s).

I think unless there's a required performance reason it's better to just force the connection to close. The use of CloseNotify() like that is undefined and seems to differ based on the Go version used, so I'm cautious to include this code. I'm going to review it anyway though in case we want to include it as a defensive coding mechanism.
Does Grafana use pipelined queries?

I don't think Grafana is pipelining queries based on what I've seen, but it is reusing a given TCP socket for multiple serial queries.

@aaronknister is it using a single connection for multiple queries (by separating statements with a semi-colon) or using the same underlying socket to make multiple HTTP calls? Reusing a TCP socket would be the later.
Either way, I think this change should work fine. I was thinking over the weekend about adding this anyway for safety. Can you update the changelog and sign the CLA? Be sure to give yourself credit in the changelog.
Thanks.

Something I didn't notice. Can you make this change on master? If we think this is worthy of adding to a bugfix release, we'll cherry pick it to the 0.12 branch.

I've opened #6413 with the change on master. Should I close out this PR?


[LUIS] List Entities (aka Closed Lists) & Intents/Utterances

I can already programmatically (or via LUIS.ai GUI) add ClosedList entities.
But can I define these entities in an intent utterance? Not via the GUI so far, but how about programmatically? Just like any other entity?
How else can we use such lists otherwise?

@paulkp are you using C# or Node SDK for BotBuilder?

@paulkp You don't need to define the List Entities inside of an utterance. List Entities aren't machine learned, but (basically) used for regexp testing. If LUIS detects the the word of a list entity inside of an utterance it will match it to it's Canonical Form. Here's an example of results for a matched list entity from an utterance:
{
    "entity": "ice cream",
    "type": "Desserts",
    "startIndex": 12,
    "endIndex": 20,
    "resolution": {
        "values": [
            "FrozenDesserts"
        ]
    }
}

Examining this code excerpt, the "type" is the entity name of the List. The "value" property in "resolution" is the Canonical Form(s), which we can think of it as the ultimate value we want passed to our chatbot. Which in this case is, "FrozenDesserts", which is admittedly not the best example.
Here is the List Entity "Desserts" from the .json of my LUIS model:
"closedLists": [
    {
      "name": "Desserts",
      "subLists": [
      {
        "canonicalForm": "FrozenDesserts",
        "list": [
          "sorbet",
          "gleato",
          "popsicle",
          "ice cream",
          "sherbet"
        ]
      }
    ]
  }
],

In regards to the SDKs there aren't explicit class/methods to handle them yet, but they are coming. So it might require a little work to get them out for the time being.

I'm closing this issue, but if there are any questions or comments please feel free to post them here.

So disregard my earlier comments about having methods that automatically parse down to the canonical form,  the list entities are the same as regular entities (except for the addition of canonical forms).
Having a method as previously described is a duplicate of the entity finding methods already in the SDKs,  more importantly users are able to manually extract the canonical forms themselves without needing a lot of legwork.
There are no plans for include such methods in the SDK (at least for Node), feel free to post here or in PR 2735 that had methods for finding canonical forms.


[EPIC] fine grained permissions

let's talk about organization concept and fine grained rbac permissions for WCs and MCs
Related
https://github.com/giantswarm/roadmap/issues/1746

@piontec you moved this to watching. is there a way forward or can it be closed?

It's so old no one really knows what it's about. Rotten and closing.


WIP: push_notifications_enabled migration to have current information about bouncer registration state.

#27881

Screenshots and screen captures:

Self-review checklist

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

Communicate decisions, questions, and potential concerns.

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

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

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

Completed manual review and testing of the following:

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

Only first 3 commits are worth reviewing as of now. 4th has a lot of bad code written as of now that we'll fix.

Closing this was a misclick. Posted some comments and configured https://github.com/zulip/zulip/pull/27881 to merge the first two prep commits, since those looked done.

Working on writing tests.

Working on writing tests.

https://github.com/zulip/zulip/pull/27939#issuecomment-1837965615

I pushed a bunch of tweaks, mostly to documentation; there's one testing failing after rebasing on top of https://github.com/zulip/zulip/commit/a67dd6dc1fb4b9946ff50fb57e08eaf99b3cf6cf, which I don't understand at all -- this PR doesn't seem to add an extra call to that function in do_create_realm...

An extra call was mistakenly added during rebase. Fixed it.


How to clear audiorecorder value after I process it, help!

When I use audio = audiorecorder("", "") to record audio and call process_audio to process it.

then switch the sidebar's radio value to 'low', process_audio is called again.

I want the audio read when I click the sidebar to be empty, so process_audio is not called repeatedly.
like st.chat_input("Please enter a question").
import streamlit as st
from audiorecorder import audiorecorder

st.title("Audio Recorder")
audio = audiorecorder("", "")

with st.sidebar:
    option = st.radio("Options", ["high", "medium", "low"])

def process_audio(audio_in):
    with st.chat_message("user"):
        st.write(f'Option: {option}')
        st.write("audio length:", len(audio_in))
        st.write("Process audio is finished")

if len(audio) > 0:
    # To play audio in frontend:
    st.audio(audio.export().read())

    # To save audio to a file, use pydub export method:
    audio.export("audio.wav", format="wav")

    process_audio(audio)

Hello !
It seems this is more of a streamlit question than an issue related to this component.
I think what you want to do is not very much in the spirit of how streamlit works.
The best way to avoid processing things repeatedly in streamlit is to use caching.
Please see https://docs.streamlit.io/develop/api-reference/caching-and-state/st.cache_data
For example, you could simply do:
@st.cache_data
def process_audio(audio_in):
    with st.chat_message("user"):
        st.write(f'Option: {option}')
        st.write("audio length:", len(audio_in))
        st.write("Process audio is finished")

If this fail, you might need to make the audio_in input hashable with something like:
from pydub import AudioSegment
import io
import hashlib

# Function to convert AudioSegment to a byte array
def audio_segment_to_bytes(audio_segment):
    buf = io.BytesIO()
    audio_segment.export(buf, format="wav")
    return buf.getvalue()

# Custom hash function for AudioSegment
def audio_segment_hash_func(audio_segment):
    byte_data = audio_segment_to_bytes(audio_segment)
    return hashlib.md5(byte_data).hexdigest()

# Cached function that takes an AudioSegment as input
@st.cache_data(hash_funcs={AudioSegment: audio_segment_hash_func})
def process_audio(audio_in):
    with st.chat_message("user"):
        st.write(f'Option: {option}')
        st.write("audio length:", len(audio_in))
        st.write("Process audio is finished")

If you really want to clear the audio when you click the radio, then you could something like:

  def reset_audio():
    del st.session_state.audio

  option = st.radio("Options", ["high", "medium", "low"], on_change=reset_audio)

but again, I do not think this is the best way to go with this.
Hope this helps !
Good luck !

Otherwise:
If I understand well, what you want is that nothing happens when you click on the radio.
If that's the case, maybe wrapping it with an @st.experimental_fragment could work:
@st.experimental_fragment
def define_option():
    with st.sidebar:
        option = st.radio("Options", ["high", "medium", "low"])

define_option()

and then you can access the option with st.session_state.option.
I didn't run any of the above code, so there may be errors...

Thank you very much for answering so quickly. I tested st.cache_data(hash_funcs={AudioSegment: audio_segment_hash_func}) and it meets the requirements.
Yes, this is not the best way. But st.chat_input indeed works. When I enter the question and switch the radio on the sidebar, it does not repeat the call.
import streamlit as st

st.title("chat_input example")

with st.sidebar:
    option = st.radio("Options", ["high", "medium", "low"])

def process_input(question_in):
    with st.chat_message("user"):
        st.write(f'Option: {option}')
        st.write("question_in:", question_in)
        st.write("Process audio is finished")

if question := st.chat_input("Please enter a question"):
    process_input(question)

When I input 'hello'：

when I click low, There is no output on the page because the process_input method is not being called.

I actually wanted this effect.

Otherwise: If I understand well, what you want is that nothing happens when you click on the radio. If that's the case, maybe wrapping it with an @st.experimental_fragment could work:
@st.experimental_fragment
def define_option():
    with st.sidebar:
        option = st.radio("Options", ["high", "medium", "low"])

define_option()

and then you can access the option with st.session_state.option.
I didn't run any of the above code, so there may be errors...

Otherwise: If I understand well, what you want is that nothing happens when you click on the radio. If that's the case, maybe wrapping it with an @st.experimental_fragment could work:
@st.experimental_fragment
def define_option():
    with st.sidebar:
        option = st.radio("Options", ["high", "medium", "low"])

define_option()

and then you can access the option with st.session_state.option.
I didn't run any of the above code, so there may be errors...

Thanks，But I have multiple radio components, which makes my code more complex.

Now I use a Button to control whether to process speech. After the speech input is complete, the user needs to click the button to invoke the speech processing function. This causes a slight decrease in user experience and is not a good solution.

I see.
Maybe in your case the simplest is to delete the audio after processing....
def process_audio(audio_in):
    with st.chat_message("user"):
        st.write(f'Option: {option}')
        st.write("audio length:", len(audio_in))
        st.write("Process audio is finished")
        del st.session_state.audio

Happy this could help !

I see.
Maybe in your case the simplest is to delete the audio after processing....
def process_audio(audio_in):
    with st.chat_message("user"):
        st.write(f'Option: {option}')
        st.write("audio length:", len(audio_in))
        st.write("Process audio is finished")
        del st.session_state.audio

Happy this could help !

Thanks, but It doesn't work after I test it.

I add  key="audio" to audiorecorder.
import streamlit as st
from audiorecorder import audiorecorder

st.title("Audio Recorder")
audio = audiorecorder("", "", key="audio")

with st.sidebar:
    option = st.radio("Options", ["high", "medium", "low"])

def process_audio(audio_in):
    with st.chat_message("user"):
        st.write(f'Option: {option}')
        st.write("audio length:", len(audio_in))
        st.write("Process audio is finished")
        del st.session_state.audio

if len(audio) > 0:
    # To play audio in frontend:
    st.audio(audio.export().read())

    # To save audio to a file, use pydub export method:
    audio.export("audio.wav", format="wav")

    process_audio(audio)


Error sign when having no tests to run

Thank you for writing this awesome plugin.
I found a case that I think it should be considered as PASS:

I'm seeing this too after getting it all running nicely - so I'd like to take a stab at this one @akinsho @sergii4 ?


Minimal Admin Dashboard for Adding Users

We should allow the following dashboard for an admin only.

This should also allow setting a Display Name, and a randomly selected Emoji.
Emoji lists:
https://unicode.org/emoji/charts/full-emoji-list.html
https://gist.github.com/rxaviers/7360908
https://gist.github.com/roachhd/1f029bd4b50b8a524f3c

We could create another, "resetpassword," table which forces a user to go to a reset password process upon first login. If the passwordresetneeded boolean is not cleared in postgres, then user is not able to visit other parts of the site.

Remaining To Do List on this Task:
Backend
Admin Validation Function:
Implement a Golang validation function that verifies a user is an ADMIN before allowing them to perform the AddUser function.
Change Password Route:
Create a /changepassword route in the server that handles password change requests.
Change Password Function:
Develop a ChangePassword function in Golang that:
Validates the user's current session.
Hashes the new password.
Updates the user's password in the database.
Password Change Validation Function:
Create a ChangePasswordNeeded validation function to check if the user needs to change their password.
Ensure that secure actions such as create, trade, etc., cannot be undertaken until the user has changed their password.
Update Routes for Secure Actions:
Modify routes to restrict access to certain actions like /create, ensuring they are inaccessible if the user needs to change their password.
Frontend
ChangePassword.jsx Component:
Design and implement a ChangePassword.jsx layout that includes:
An input field for the new password.
Instructions or guidelines on creating a secure password.
A button to submit the new password.
Modify Sidebar for Conditional Access:
Adjust the sidebar to show only the "Change Password" option if the user has the MustChangePassword flag set to true.
Redirection After Password Change:
Set up redirection to the /profile page or another appropriate page once the password change is successfully completed.
UI Feedback for Actions:
Implement user feedback mechanisms for both successful and unsuccessful password updates, such as notifications or alerts.
General
Testing and Validation:
Thoroughly test the new password change feature to ensure it works seamlessly across different scenarios and handles edge cases properly.
Documentation:
Update the system documentation to include information about the new password change requirement and its impact on user interaction with the system.
This list provides a comprehensive roadmap for adding the forced password change feature to your system, ensuring both security and usability are maintained.


Rust version update - 1.62

Description
While doing the #699 , I found that rust version 1.62 is released recently.
clippy status
clippy seems to be released 1.62.0
some clippy warnings
With 1.62 setting, I found some clippy warnings. It would be nice to resolve when updating the rust lang version

macro related warnings

github action link
clippy explanation

unused lifetime

github action link

note
I saw there is a good pr related to this - #564 .

As I mentioned before, I will try to solve the following issue.


Better documentation needed around what an App Service Plan is, and clearer differentiation of the 3 options in Function App creation.

This page fails to clearly talk about the App Service Plan that you have to create for Premium. https://docs.microsoft.com/en-us/azure/azure-functions/functions-premium-plan
“Hosting plan that defines how resources are allocated to your function app. Select Premium, and then select the defaults for Windows Plan and Sku and size.”
The fact that all 3 Function App UI options (Consumption, Premium, and App Service Plan) still use an App Service Plan (just not a ‘standard’, dedicated one) was very confusing, as the documentation doesn’t particularly point that out unless you dig around for it. Without knowing to dig around for it, its easy to assume everything that talks about an App Service Plan function refers to your Consumption app. Further, since my Premium function app clearly had an App Service Plan that looks and talks like a Standard App Service Plan, most of the documentation for App Service Plan appear to be applicable to Premium (and fortunately, that is mostly true).
Very frustrating that despite all 3 having App Service Plan in their properties, one option is straight up just called ‘App Service Plan’. We spent far longer than should have been necessary being confused about what portions of https://docs.microsoft.com/en-us/azure/app-service/overview applied to which function app scenarios, and about what constituted a Premium app (after all, once you create the Premium function app, if you go to the App Service Plan that you created as part of it, its Scaling options sure look exactly like the Standard App Service Plan scaling options, leading to confusion around the abilility to scale dynamically based on events in Premium and causing us to doubt whether what we had created WAS Premium, since this page clearly DOES NOT mention App Service Plan even once, and we CLEARLY had an App Service Plan after creating what we believed (correctly) to be a Premium FuncApp).
Now that the differences are clear and I understand everything above, the documentation is much easier to understand, but I suspect I am not the only one who has had to reach enlightenment after a bitter and frustrating battle with this aspect of the documentation.

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

ID: 3847e16b-92ae-0202-c7e1-ca9a8474e65f
Version Independent ID: a25b6b5b-05ab-b3b2-616c-5d06eadb928d
Content: Azure Functions Premium plan
Content Source: articles/azure-functions/functions-premium-plan.md
Service: azure-functions
GitHub Login: @jeffhollan
Microsoft Alias: jehollan

@EklipZgit Thanks for the feedback. We are looking into this and will get back to you shortly.

@EklipZgit The comparison has already given at the start of the document. Just mentioning here if any chance there is a miss.
"For a comparison of the Premium plan and other plan and hosting types, see function scale and hosting options.

I don't think there is a doc change required for this. For now will proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


passing props with transitionTo

Is it possible to set the props when calling transitionTo? This way my component does not have to special case between normal rendering with props vs. using getParams() with react-router.
Thanks.

+1 - I was like, good lord this component is not complicated enough for {...this.props} to have mysteriously stopped working

:+1:

This way my component does not have to special case between normal rendering with props vs. using getParams()

Sounds like an anti-pattern. Why not have a component that uses props and a separate route handler that passes params to it? Something like <Component {...this.getParams()} />.
Yeah two components is more verbose but then you don't need to complicate the router and get nice clean separation of route handler and the actual component. This wouldn't work well anyway: what if your component has to prop? It would be impossible to specify from Link. If we go for <Link props={{ prop: something }}>, what if you specify some prop that is already specified by the parent route handler with <RouteHandler prop={somethingElse}>? Who wins? When edge cases break so easily, it's a good indication that design isn't solid. Since there's a very simple workaround, I'm closing this, but please let me know if I missed something!


GEODE-3744: Local region will not participate in a transaction hosted…

… remotely.
TransactionException will be thrown if a local region participates in a transaction
not hosted locally.

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Add a reviewer.
@nreich


Look Assigner: Ignore invalid entity ids in get_folders query

Changelog Description

Fixes an issue where look assigner would not list anything if it had to list entries that had invalid ids (those that are NOT valid uuid patterns) and hence the ayon_api.get_folders query would fail.
Additional info

Ignore invalid entity ids in get_folders query to avoid GraphQlQueryFailed exception which then also fails to return for the valid ids in the set.
Fixes #84
Note that due to other logic in the code a warning will still be logged for these invalid ids, which is as intended. For example:
// Warning: ayon_maya.tools.mayalookassigner.commands : Id found on 2 nodes for which no folder is found database, skipping 'ac991b60b4c5a70'
// Warning: ayon_maya.tools.mayalookassigner.commands : Id found on 2 nodes for which no folder is found database, skipping 'ac991b60b1eeb7fc773031a70'

Testing notes:

Load some assets
Go to the cbId attribute. Remove some characters from before the : in the value.
Try the look assigner on that node - it doesn't list anything. (should log a warning instead!)
Now try that node together with nodes that do have valid ids - it still lists nothing. (should list instead, plus log warning)

OR
Load a scene with OpenPype assets together with a scene with AYON asset. Look assigner should still list entries for AYON.

@m-u-r-p-h-y can you run this through your demo scene with the alembic character? :)


[plugins] Add engine retain cycle tests to all plugins

We've had bugs in a number of plugins where just setting them up creates a retain cycle that keeps the engine alive forever (e.g., due to engine foot-guns like https://github.com/flutter/flutter/issues/102990).
We should have a test in every plugin that calls registerWithRegistrar with a fake registrar that holds a strong reference to it when a channel handler is added, and also that returns itself as any of the called helper objects (binary messenger, texture registrar, etc.—using a strict mock to make sure we aren't missing any and accidentally returning nil). The test should drop its reference to the fake registrar, and then ensure that it nils out.
This would be more strict than the engine actually is (e.g., the binary messenger won't make a loop any more), but it should probably never actually be necessary to have a strong reference to something that's owned by the engine anyway, because if the engine is gone calling it is at best a no-op anyway (and in some cases an error).
This would ensure we aren't relying on add-to-app customers to find these one at a time, and also be a good backstop against accidentally introducing retain loop foot-guns with any new engine APIs.
/cc @jmagman @cyanglaz

Very good, all plugins should be tested, because in the pure flutter project, the performance is very good, in the mixed project, the engine is prone to memory leaks, causing the app to run abnormally.


[BUG] Plugin not compatible with SeleniumBase: conflicting option string: --browser

I can put in a fix by changing the --browser option tp --pwbrowser. Let me know. I made required changes to couple of places and is working now.

Which other pytest plugins are you using? Are you using pytest-selenium?

Yes and a couple of others. I guess we can use a virtual environment but
imho --browser is too common as an option parameter. But thanks for the
quick response.
Best Regards
Sumit Mahajan
On Mon, Oct 5, 2020 at 2:05 PM Max Schmitt<EMAIL_ADDRESS>wrote:

Which other pytest plugins are you using? Are you using pytest-selenium?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/playwright-pytest/issues/14#issuecomment-703796370,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHC43P4MG5BNAMA4UP3VPOLSJIDHLANCNFSM4SFABLBA
.

Could you provide us a list of plugins which you use? pytest-selenium seem not to cause a CLI argument clash.

Found the rootcause. It's this library https://github.com/seleniumbase/SeleniumBase

Had a discussion with pfeldman offline. It's not considered as a bug since normally the users won't use SeleniumBase in combination with playwright-pytest.

I am testing playwright, seleniumbase,I found a temporary solution:
Open with a text editor "c:\python38\Lib\site-packages\pytest_playwright\pytest_playwright.py"
Find line 175，Modify "--browser" to "--browserr"
When using pytest-playwright:
pytest my.py --browserr firefox

I am testing playwright, seleniumbase,I found a temporary solution:
Open with a text editor "c:\python38\Lib\site-packages\pytest_playwright\pytest_playwright.py"
Find line 175，Modify "--browser" to "--browserr"
When using pytest-playwright:
pytest my.py --browserr firefox

playwright-python运行网页脚本的速度比seleniumbase要快一些。

playwright-python运行网页脚本的速度比seleniumbase要快一些。


FAIL: TestServer_DatabaseRetentionPolicyAutoCreate

Bug report
System info:

influxdb v1.1
go version go1.6.2 linux/amd64

Steps to reproduce:

go install ./cmd/...
go test ./cmd/...

Expected behavior: [What you expected to happen]
Tests passed
Actual behavior: [What actually happened]
> go test ./cmd/...
?       github.com/influxdata/influxdb/cmd      [no test files]
?       github.com/influxdata/influxdb/cmd/influx       [no test files]
ok      github.com/influxdata/influxdb/cmd/influx/cli   0.011s
?       github.com/influxdata/influxdb/cmd/influx_inspect       [no test files]
ok      github.com/influxdata/influxdb/cmd/influx_inspect/dumptsm       0.002s
ok      github.com/influxdata/influxdb/cmd/influx_inspect/export        0.002s
ok      github.com/influxdata/influxdb/cmd/influx_inspect/help  0.001s
ok      github.com/influxdata/influxdb/cmd/influx_inspect/report        0.005s
ok      github.com/influxdata/influxdb/cmd/influx_inspect/verify        0.009s
?       github.com/influxdata/influxdb/cmd/influx_stress        [no test files]
?       github.com/influxdata/influxdb/cmd/influx_tsm   [no test files]
?       github.com/influxdata/influxdb/cmd/influx_tsm/b1        [no test files]
?       github.com/influxdata/influxdb/cmd/influx_tsm/bz1       [no test files]
?       github.com/influxdata/influxdb/cmd/influx_tsm/stats     [no test files]
?       github.com/influxdata/influxdb/cmd/influx_tsm/tsdb      [no test files]
?       github.com/influxdata/influxdb/cmd/influx_tsm/tsdb/internal     [no test files]
?       github.com/influxdata/influxdb/cmd/influxd      [no test files]
?       github.com/influxdata/influxdb/cmd/influxd/backup       [no test files]
?       github.com/influxdata/influxdb/cmd/influxd/help [no test files]
?       github.com/influxdata/influxdb/cmd/influxd/restore      [no test files]
2016/11/23 16:01:50 deprecated config option [cluster] replaced with [coordinator]; [cluster] will not be supported in a future release
[store] 2016/11/23 16:01:50 Using data dir: /tmp/influxd-678932382
[subscriber] 2016/11/23 16:01:50 opened service
[monitor] 2016/11/23 16:01:50 Starting monitor system
[monitor] 2016/11/23 16:01:50 'build' registered for diagnostics monitoring
[monitor] 2016/11/23 16:01:50 'runtime' registered for diagnostics monitoring
[monitor] 2016/11/23 16:01:50 'network' registered for diagnostics monitoring
[monitor] 2016/11/23 16:01:50 'system' registered for diagnostics monitoring
[shard-precreation] 2016/11/23 16:01:50 Starting precreation service with check interval of 10m0s, advance period of 30m0s
[snapshot] 2016/11/23 16:01:50 Starting snapshot service
[continuous_querier] 2016/11/23 16:01:50 Starting continuous query service
[httpd] 2016/11/23 16:01:50 Starting HTTP service
[httpd] 2016/11/23 16:01:50 Authentication enabled: false
[httpd] 2016/11/23 16:01:50 Listening on HTTP: <IP_ADDRESS>:58832
[retention] 2016/11/23 16:01:50 Starting retention policy enforcement service with check interval of 30m0s
[monitor] 2016/11/23 16:01:50 shutting down monitor system
[shard-precreation] 2016/11/23 16:01:50 Precreation service terminating
[snapshot] 2016/11/23 16:01:50 snapshot listener closed
[continuous_querier] 2016/11/23 16:01:50 continuous query service terminating
[retention] 2016/11/23 16:01:50 retention policy enforcement terminating
[subscriber] 2016/11/23 16:01:50 closed service
--- FAIL: TestServer_DatabaseRetentionPolicyAutoCreate (0.00s)
        server_test.go:306: show retention policies should return auto-created policy: unexpected results
                query:  SHOW RETENTION POLICIES ON db0
                params:  map[]
                exp:    {"results":[{"series":[{"columns":["name","duration","shardGroupDuration","replicaN","default"],"values":[["autogen","0s","168h0m0s",1,true]]}]}]}
                actual: {"results":[{"series":[{"columns":["name","duration","shardGroupDuration","replicaN","default"],"values":[["autogen","0","168h0m0s",1,true]]}]}]}

--- FAIL: TestServer_Query_DefaultDBAndRP (2.00s)
        server_test.go:586: default rp exists: unexpected results
                query:  show retention policies ON db0
                params:  map[]
                exp:    {"results":[{"series":[{"columns":["name","duration","shardGroupDuration","replicaN","default"],"values":[["autogen","0s","168h0m0s",1,false],["rp0","0s","168h0m0s",1,true]]}]}]}
                actual: {"results":[{"series":[{"columns":["name","duration","shardGroupDuration","replicaN","default"],"values":[["autogen","0","168h0m0s",1,false],["rp0","0","168h0m0s",1,true]]}]}]}

FAIL
FAIL    github.com/influxdata/influxdb/cmd/influxd/run  80.279s

@matwey was this using the 1.1 tag?

@e-dard yes, v1.1.0 tag

@matwey does it happen every time? We're not seeing it here.

Go 1.7 changed the format string of a zero duration from 0 to 0s.
If you need to build InfluxDB 1.1 (or 1.2), use Go 1.7.


lubelogger: 1.2.1 -> 1.2.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/hargata/lubelog/releases.
meta.description for lubelogger is: A vehicle service records and maintainence tracker
meta.homepage for lubelogger is: https://lubelogger.com
meta.changelog for lubelogger is: https://github.com/hargata/lubelog/releases/tag/v1.2.2
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.2.2 with grep in /nix/store/8qgv0paws8dh0g6dw147mvjjbashh3dz-lubelogger-1.2.2
found 1.2.2 in filename of file in /nix/store/8qgv0paws8dh0g6dw147mvjjbashh3dz-lubelogger-1.2.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
lubelogger

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8qgv0paws8dh0g6dw147mvjjbashh3dz-lubelogger-1.2.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A lubelogger https://github.com/r-ryantm/nixpkgs/archive/6a0c4fbe04238867c3a6593da3b34294d07f37da.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/6a0c4fbe04238867c3a6593da3b34294d07f37da#lubelogger

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8qgv0paws8dh0g6dw147mvjjbashh3dz-lubelogger-1.2.2
ls -la /nix/store/8qgv0paws8dh0g6dw147mvjjbashh3dz-lubelogger-1.2.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

lubelogger

Maintainer pings
cc @Samasaur1 for testing.

Would you like to test https://discourse.nixos.org/t/nixpkgs-merge-bot-testing-and-plan/39824/12?
(Just type @NixOS/nixpkgs-merge-bot merge in a comment)

@Samasaur1 Would you like to test https://discourse.nixos.org/t/nixpkgs-merge-bot-testing-and-plan/39824/12?
(Just type @NixOS/nixpkgs-merge-bot merge in a comment)

sure!
@NixOS/nixpkgs-merge-bot merge

@wegank is the bot watiing on ofBorg or did something else go wrong?

Something went wrong. Will investigate it after getting back to ny computer. Sorry for the inconvenience. I guess we have an error in the parsing code of the of borg checks


What credentials are needed to run the authentication:basic-auth test?

Describe the bug
To help with #502 I try to start with the included test "authentication:basic-auth". But when I run this test without any further configuration I get this output:
><EMAIL_ADDRESS>authentication:basic-auth
> wdio run test/e2e/authentication/wdio-basic-auth-authentication.conf.ts

Execution of 2 workers started at 2023-08-23T11:25:13.286Z

[0-1] RUNNING in chrome - /test/e2e/Authentication.test.ts
[0-0] RUNNING in chrome - /test/e2e/Basic.test.ts
[0-1] 2023-08-23T11:25:40.142Z ERROR webdriver: Request failed with status 400 due to invalid cookie domain: invalid cookie domain
[0-1]   (Session info: chrome=116.0.5845.110)
[0-1] /Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/webdriver/build/utils.js:198
[0-1]     return new CustomRequestError(body, requestOptions);
[0-1]            ^
[0-1] invalid cookie domain: invalid cookie domain
[0-1]   (Session info: chrome=116.0.5845.110)
[0-1]     at getErrorFromResponseBody (/Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/webdriver/build/utils.js:198:12)
[0-1]     at NodeJSRequest._request (/Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/webdriver/build/request/index.js:166:60)
[0-1]     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[0-1]     at async Browser.wrapCommandFn (/Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/@wdio/utils/build/shim.js:137:29)
[0-1]     at async Browser.setCookies (/Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/webdriverio/build/commands/browser/setCookies.js:63:9)
[0-1]     at async Browser.wrapCommandFn (/Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/@wdio/utils/build/shim.js:137:29)
[0-1] FAILED in chrome - /test/e2e/Authentication.test.ts
[0-0] 2023-08-23T11:25:40.189Z ERROR webdriver: Request failed with status 400 due to invalid cookie domain: invalid cookie domain
[0-0]   (Session info: chrome=116.0.5845.110)
[0-0] /Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/webdriver/build/utils.js:198
[0-0]     return new CustomRequestError(body, requestOptions);
[0-0]            ^
[0-0] invalid cookie domain: invalid cookie domain
[0-0]   (Session info: chrome=116.0.5845.110)
[0-0]     at getErrorFromResponseBody (/Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/webdriver/build/utils.js:198:12)
[0-0]     at NodeJSRequest._request (/Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/webdriver/build/request/index.js:166:60)
[0-0]     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[0-0]     at async Browser.wrapCommandFn (/Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/@wdio/utils/build/shim.js:137:29)
[0-0]     at async Browser.setCookies (/Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/webdriverio/build/commands/browser/setCookies.js:63:9)
[0-0]     at async Browser.wrapCommandFn (/Users/gwolf/Documents/Projects/ui5/wdi5/node_modules/@wdio/utils/build/shim.js:137:29)
[0-0] FAILED in chrome - /test/e2e/Basic.test.ts

Spec Files:      0 passed, 2 failed, 2 total (100% completed) in 00:00:26

npm ERR! Lifecycle script `authentication:basic-auth` failed with error:
npm ERR! Error: command failed
npm ERR!   in workspace<EMAIL_ADDRESS>npm ERR!   at location: /Users/gwolf/Documents/Projects/ui5/wdi5/examples/ui5-ts-app

To Reproduce
Steps to reproduce the behavior:

Clone this repository
Install the npm packages
Run 'npm run authentication:basic-auth -w examples/ui5-ts-app'
See error

Expected behavior
Provide instructions for a contributor what credentials can be used for basic authentication.

this already got into wdi5 2.0: https://ui5-community.github.io/wdi5/#/authentication?id=cap-authentication-only-during-development


Not downloading from hacs

hey,
seems like it's not downloading from hacs (v0.24.1) on HA (v105.3)
here are the logs:
2020-02-12 14:02:55 ERROR (MainThread) [hacs.repository.plugin.maykar.custom-header] Download was not complete [No content to download]
2020-02-12 14:02:55 ERROR (MainThread) [hacs.repository.plugin.maykar.custom-header] Download was not complete [No content to download]
2020-02-12 14:02:55 ERROR (MainThread) [hacs.repository.plugin.maykar.custom-header] Download was not complete [No content to download]
thanks for the help!

I am having the same issue as well.
But it seems to be a HACS issue ... I had just updated HACS before installing.  CH was not installing, but so was others.  I rolled HACS back to 21.2 and was able to load CH


Release pipeline seems to be disabled

Hi,
It looks as though the pipeline for this project has been disabled due to inactivity, meaning that the most recent version of kustomize (5.3.0) is not yet in the version of this container image published to docker hub (which has 5.2.1).
I found out as I am using the latest version of the image but it does not contain the most recent version of kustomize.
While there are lots of ways for me as a user to work around it, I thought you might like to know.
-Malcolm

Hi, Malcolm.
First of all, thank you for letting us know about the issue. I'll check and
fix it as soon as possible.
2023년 12월 18일 (월) 20:31, Malcolm Lea @.***>님이 작성:

Hi,
It looks as though the pipeline for this project has been disabled due to
inactivity, meaning that the most recent version of kustomize (5.3.0) is
not yet in the version of this container image published to docker hub
(which has 5.2.1).
I found out as I am using the latest version of the image but it does not
contain the most recent version of kustomize.
While there are lots of ways for me as a user to work around it, I thought
you might like to know.
-Malcolm
—
Reply to this email directly, view it on GitHub
https://github.com/line/kubectl-kustomize/issues/13, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFWCSXK4YFHDQIZREO3SCLYKBAUDAVCNFSM6AAAAABAZRCS66VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2DMNRXGM4DKMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Switched broken pypip.in badges to shields.io

Hello, this is an auto-generated Pull Request. (Feedback?)
Some time ago, pypip.in shut down. This broke the badges for a bunch of repositories, including inquiry. Thankfully, an equivalent service is run by shields.io. This pull request changes the badge to use shields.io instead.

Codecov Report

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

@@            Coverage Diff            @@
##             master       #4   +/-   ##
=========================================
  Coverage          ?   74.92%
=========================================
  Files             ?        8
  Lines             ?      666
  Branches          ?      160
=========================================
  Hits              ?      499
  Misses            ?      115
  Partials          ?       52

Continue to review full report at Codecov.

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


Typo in imageResize module name

I can verify this. Uppercase first letter does not load the module on the latest versions of both quill and the lib.

I have merge all your pull requets. https://www.npmjs.com/package/@taoqf/quill-image-resize-module

just came across this issue, saw the demo uses the correct casing fortunately.
@lobothijau any chance of a merge?


[Cordova] Cordova + Phonegap TCP Transport

In the browser, we don't have access to TCP Sockets as we do with nodejs. However, when in cordova/phonegap environment, you have access to a webview for running JS but also a plugin architecture, where you can expose native functionality as a JS API. Hence, there could be a transport written for cordova/phonegap in Android/iOS that enables us to have a nodejs-like js-ipfs instance in a webview.
This would help with developing mobile applications for JS developers.
There are some prior art with this as well, https://www.npmjs.com/package/cordova-plugin-chrome-apps-sockets-tcp comes from Google and exposes a sockets API whose interface can be seen here: https://developer.chrome.com/apps/sockets_tcp
There is also https://github.com/blocshop/sockets-for-cordova
Ideally, the interface exposed by the plugin would be identical to the nodejs interface for sockets, and then https://github.com/libp2p/js-libp2p-tcp could be easily adapted to work.
Existing, similar issues:

Daemon on Cordova - Android - https://github.com/ipfs/js-ipfs/issues/834
ipfs.files.add callbacks and promises do not resolve on Ionic2 platform - https://github.com/ipfs/js-ipfs/issues/802

Seems like the APIs are quite different among those plugins and the on that js-libp2p-tcp uses -which is Node's. We can either write a new transport specific for cordova or shim the node api on top of one of those plugins.

Looks like there is a node api plugin for cordova already - https://github.com/feross/chrome-net :)

That chrome net is a great find @dryajov. We can actually enable js-ipfs to just take in a whole custom libp2p instance so that runtimes like Cordoba can use the caps they have.
@xSkyripper, how does that sound? This shouldn't be hard to make it happen.

Is this still actual? I'd like to familiarize myself with the whole thing on a deeper level and looking for an entry point. I could try to implement this one.

Having bridges for native transport and peer discovery support would be great, there still currently isn't any. While there are jvm and swift implementations of libp2p in early phases, there would still need to be bridges built for things like Cordova / React Native.
In theory we should be able to use websockets to run things in a browser build, although I don't believe that's been tested in Cordova. @jayarjo if you'd like to look into getting libp2p running in a mobile build that would be a nice tool for mobile app development.
I think starting with a browser build of libp2p and integrating in native components as needed, or to enhance the experience would be a good path.

This would help with developing mobile applications for JS developers.

For now, you can use WebRTC or WebSocket on mobile devices. We're not officially supporting Cordova anytime soon (if community members want to hack it to work, we're happy to review PRs/provide assistance.)


HIVE-27008: Partial cherry-pick of HIVE-20718 Add perf cli driver with constraints

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

@zabetak @abstractdog @cnauroth This is a slightly complicated fix for the current_date_timestamp.q test. The issue was a parsing issue in this test case where "explain cbo select current_timestamp() from alltypesorc" was not able to parse. Failure link : http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-4020/1/tests. In my local cherry picking this commit made sure that Hive was able to parse this. Now that test failed due to some assertion error which I fixed in this commit 8d1899e57e67b5b0fe06 . Now I need your suggestion :

HIVE-20718 has a lot of merge conflicts mainly with HIVE-17040. For now in this PR I have made the test case scenario work with the minimalist changes I could cherry pick from HIVE-20718 (note I did not cherry pick HIVE-17040 in this PR). But there are some more changes that need to be included. Should we go ahead with this?
Second approach can be cherry picking HIVE-17040 and then cherry picking HIVE-20718. Not sure how many merge conflicts will come in this but I will raise another PR for both these changes combined. I prefer this approach but that would mean creating two tickets or should I cherry pick them in one?

@zabetak @abstractdog @cnauroth FYI I have raised a new PR : https://github.com/apache/hive/pull/4065 for HIVE-17040. Appears HIVE-17040 is a clean backport as far as .java files are concerned. There were some conflicts in the test. Can we agree that we can merge it(will fix the new test failures if any) and then merge this PR with a clean backport of HIVE-20718?


Streaming the payload

It would be very useful to have access to the remaining input data after parsing, so that one can process the payload a few pieces at a time using multiple FPGA pipelines. Extract a block from the remaining input and emit a block of the same or varying size for encoding, encrypting or compressing on the link layer.
The hardware would be placed next to the parser to allow looping, but execute after deparser, with a communication to the deparser for emitting payloads and adding them to the Ethernet checksum.
ProcessPayload(packet_in input, packet_out output, in headers) {
block_t data;
input.extract(data);
if (isValid(input)) {
// Add input to each pipeline while it is still processing old requests
thread (
process(data.pipelineA);,
process(data.pipelineB);,
process(data.pipelineC);,
process(data.pipelineD);
, output.emit(data););
// Go to the next block while the pipelines are running
transition repeat;
} else {
WaitForPipelines;
transition done;
}
}
The Pipeline objects would be collections of functions processed in steps and storing intermediate results in FPGA registers to allow using a high frequency and not stall too much. They would only have read access to the shared header and must flush out all results before another header may be connected.
Model:
Parser
VerifyChecksum
Ingress
Egress
ComputeChecksum
Deparser
ProcessPayload
This would not be able to merge or split packets, but maybe a better suggestion can be functionally complete.

Thanks for the comment.
There are many ways to model packet data, its operations, and their restrictions in a P4 program. But I don't believe the question of whether the packet is available in the pipeline is a P4 language issue -- it's really a matter for architectures to figure out.
This repository is primarily for work on the language specification. So I'm going to close this issue. But I encourage you to discuss this capability on the P4 Forum and, if there is interest in fleshing it out, coming back with a concrete proposal for an architecture that implements the desired functionality.


Will it work for all ip?

Will it work for all ip?, If not is the a way to update the local db?

It should do, yes.

Thanks...


Removes the redundant map2html5Impl.xsl import

Description
The nav.xsl file is used only as a part of map2html5-coverImpl[_template].xsl which already imports map2html5Impl.xsl.
Motivation and Context
Let's avoid the annoying Saxon message about multiple imports.
How Has This Been Tested?
gradlew test
Type of Changes

Bug fix (non-breaking change which fixes an issue)

Checklist

My code follows the code style of this project.

https://github.com/dita-ot/dita-ot/wiki/Java-Coding-Conventions
https://github.com/dita-ot/dita-ot/wiki/XSLT-Coding-Conventions

This would fix #2821 and might be worth including in the 3.0.4 hotfix.

Oh, right. Maybe we should. Will need to create a new PR for the cherry-picked commit.

Since this change was merged to develop and hotfix/3.04, I'm getting new errors in HTML5 builds:
Failed to transform document: A sequence of more than one item is not allowed as the value of variable $input.map (text(""), text("DITA Open Toolkit"), ...)

The navigation is no longer generated correctly.

Reverted in 0197aed35f376dc29e26da03b699dc302f53d1a5