Is direct lora merging mathematically correct?

As I understand, lora merging is adding the weight together. Is it correct?
Say lora1 has L1, U1, lora2 has L2, U2. What we want is L1U1 + L2U2, but by adding them directly, we get (L1 + L2)(U1 + U2), which is L1U1 + L2U2 + L1U2 + L2U1?

Thanks for the confirmation. I wonder if there are similar things for lora-hada, seems to be much more difficult.


I want to compress a file use lzfse on system-level ,like lzvn or zlib,what could I do?

What operating system are you on?
If you are on MacOS, you can do that using AppleFSCompression (decmpfs). See APFS - how do I enable transparent compression. Note that the transparency is broken for quite a few Unix tools, and you probably only wants to do it for executables anyways.
If you are on Linux, you have to patch your filesystem. Btrfs supports ZSTD, which is quite similar to LZFSE and can be used as a starting point. The other algorithm, LZ4, is quite similar to LZVN in efficiency. (Both are usually more efficient than the Apple analogues at the same speed, so you might just be better off using them.) If you are on FreeBSD, you can use LZ4 in ZFS.
If you are on Windows, good luck. Maybe when ReactOS adds support for WofCompressedData (CompactOS stream, a bit like decmpfs) you can use it like any other algorithm.


Use real byte size limits

Fixes #1727.

Is that right? That seems fine for Cardano mainnet. But is it a fit for other (potential) users of this library? If not, then we ultimately need to make those numbers depend on eg the block type blk.

Block size is a parameter of the network and yes these limits should ultimately be configurable rather than hard coded.  But block size is independent of block type (though tx size, probably does depend on tx type).  So ultimately, these limits should be provided by a cardano-node configuration file (or hard coded there).
I think this makes it clear why we should keep the interface proposed in this PR.  Note also timeouts are different, since they are much less conservative than size limits, but in long run we will also need to make them configurable.


Opening image picker from within modal

When the image picker is triggered from within a page that was opened using showModal(), the picker is loaded behind the page. Is there any way to work around this?

Is there any update on this ?

That's an iOS-only problem. I am also looking forward to a fix. I just implemented a very ugly workaround for iOS:

Before showing the select image dialog, close the modal with an own result code
Show the image dialog
After selection, save the image on the parent page
Display the modal again with the selected image

To show the modal the second time, a timeout is needed, because we cannot display the modal inside the close modal function (the modal is still open):
`            if(values.result == 'pickImage') {
this.imagePickerProvider.selectPicture()
.then((response) => {
this.newWallPostImage = response.toBase64String('jpeg');
this.newWallPost = values.text;
                // Use a timeout, because opening the modal from here does not work
                // --> Still open. Timeout of 1 ms did not work on a real device. Maybe
                // On slower devices, we need to further increase this timeout...
                setTimeout(() => {
                    // Show the modal again this time containing the image
                    this.editWallPost();
                }, 500);
            });`

Welp, just saw the same problem here: https://github.com/NativeScript/NativeScript/issues/3195
And surprisingly, the workaround is exactly the same as mine. Although in my opinion, the timeout is a little wobbly...
Anyway, if Issue 3195 cannot be resolved, it maybe makes sense to handle this case like shown. But NativeScript could make it easier for us and handle this case automatically on iOS.

Can someone show an example here with Angular, it's not working for me on the IOS

As far as I can tell this has not been solved for Angular. Simply passing in the Page reference does not work.

@tbozhikov i haven't really got a chance to try the workout, i had to the change the structure n depend on routing instead of modals, would be nice if someone can see this solved though.. ))

@mailiam @tbozhikov
Even with the latest version of this plugin, I am still not able to open the ImagePicker in an existing modal. Here is my example [project](https://github.com/abhayastudios/image-picker-issue79 that:

opens a modal
gets a reference from that Page (though ViewChild, but also tried through shownModally event)
pass this reference to ImagePicker create

It does open the ImagePicker but it will open an new modal on top of the existing one.
Any ideas?

I was facing the same issue with the error of window hierarchy, I Solved it by just adding a Timeout of 10 milliseconds.
let context = imagepicker.create({ mode: "single" });
this.startSelection(context);

public startSelection(context) {
		let _that = this;
		setTimeout(function() {
		context
			.authorize()
			.then(() => {
				return context.present();
			})
			.then((selection) => {
				selection.forEach(function (selected) {
					let source = new ImageSourceModule.ImageSource();
					if (source && source !== null) {
						source.fromAsset(selected).then((source) => {
						}, error => { });
					}
				});
			}).catch(function (e) {
				console.log(e);
			});
		}, 10);
	}


Workflow for recetox-aplcms

The recetox-aplcms tool should also contain a workflow which connects the individual steps and pipes the data in the correct way so that it is actually easier to use.

[x] Create Galaxy workflow
[ ] Finalize workflow documentation
[ ] Upload workflow to GitHub
[ ] Publish workflow in History
[ ] Create workflow test
[ ] Upload workflow to workflow-hub

This should be revisited and properly finished with the new release of apLCMSv0.10.0 and the consequent update of its wrappers in RECETOX/galaxytools#308.

@hechth do we want to include the mzml_validator as the first step of the workflows?

@hechth do we want to include the mzml_validator as the first step of the workflows?

Not at this point


Allow regridding for projections in non-degree type units

Addresses #222
Some projections, like OSGB, have units which cannot be converted to degrees (i.e. meters) and cause regridding to fail. This PR assumes that where a coordinate system exists, units ought to already be compatible with it.

Using pyproj.Proj could be an easy way of converting these cases to degrees.

Using pyproj.Proj could be an easy way of converting these cases to degrees.

This conversion ought to happen at this point:
https://github.com/SciTools-incubator/iris-esmf-regrid/blob/eca3a2a0dc4d5a2e8a2c8ae8535127f719d5fa4c/esmf_regrid/_esmf_sdo.py#L224-L225
I would imagine that cartopy would be calling Proj here anyway. I think that in the case where units are supplied in meters, at this point cartopy describes the projection as being described in meters and is expecting data to be in meters. There is still a case that there could be more to be done to ensure that units are compatible with the coordinate system, but I'm not sure what it would mean for a coordinate to have a unit which disagreed with the coordinate system.
The approach I've gone for is to treat the coordinate system as the single source of truth for a coordinate where it exists. This seems the simplest way to do things for the time being.

Do you plan to add some testing to this PR?

Do you plan to add some testing to this PR?

Yes, I have been thinking about adding tests. I think I would ideally want some OSGB data (or a subset of such data) to work with, since thats where this problem showed up. The closest I can find in iris-test-data seems to be transverse mercator (which i think OSGB is an instance of). If you have any other ideas of data to test this on let me know.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @stephenworsley!


Better error message when locator assertions have bad expected value types

Simple description about the feature
If you accidentally provide a non-string/non-regex value to an assertion like expect(page.get_by_label('Calculated Total').to have_value(1.25) then you get a cryptic error

 Playwright::Error:
   expectedText[0]: expected object, got null

it would be nice to have a more helpful error to debug what is wrong

### Usecase / Motivation
* any tests that have math involved
* easier test debugging

I submitted a PR https://github.com/YusukeIwaki/playwright-ruby-client/pull/302


updated read me

added chakr innovations
Checklist

[x] I reviewed 2 other open pull requests. Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
[x] I read and followed the CONTRIBUTING guidelines.
[x] This pull request has a title in the format Add Company Name. Or Add Company1, Company2 and Company3 if it adds multiple companies.

:x: Update README.md
:x: Added Orbital Systems
:white_check_mark: Add Orbital Systems
:white_check_mark: Add Orbital Systems and Bulb

[x] I added entries in alphabetical order.
[x] The description is simple and doesn't contain unnecessary buzzwords. It needs to say what the company does, it's not a sales pitch.

:x: Disruptive company developing cutting-edge AI-enabled solutions to provide farmers with a decision support system.
:white_check_mark: They use satellites to help farmers monitor crops and lower their emissions by reducing their nitrogen usage.

Could we squash the commits to 1 and change it for a better commit message? i.e Add Chakr Innovation and Blue Sky Analytics


Adding AML Workspace ID Property

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

I thought we already had this parameter? I guess it was missing form swagger, i assume?

Yes this was not exposed, but now we are suggesting to unlink via ARM template deployment and hence this parameter should be visible in ARM template reference. So adding in swagger

As identified in the automated checks there are breaking changes, please follow Azure Breaking changes approval request form as defined @Breaking Change Process

As identified in the automated checks there are breaking changes, please follow Azure Breaking changes approval request form as defined @Breaking Change Process

This change is not breaking change. The current property is already supported by our service and we are exposing it in swagger. This is an optional parameter which don't need to specify always. Let us know if we want to discuss further on this.


Update API group of resource type events

events went from the events.k8s.io into the core API group. Came across this, because I wasn't able to kubectl get events with just the events.k8s.io in the role rules.

On the contrary, I believe the Event type is being migrated from core to the events.k8s.io group where the v1 version was just announced in 1.19. You can create an event like this:
apiVersion: events.k8s.io/v1
kind: Event
metadata:
  name: test-event
eventTime: "2020-09-11T02:42:23.123456Z"
reportingController: my-operator
reportingInstance: my-operator-xzddfy
action: update
reason: Temporature too high
regarding:
  namespace: default
  kind: Pod
  name: pod111    # this has to be something existent
type: Normal

@tengqm But in the API Reference v1.19 the Event type (from the core group) is listed under the "Metadata APIs" section and the types from the event.k8s.io group are listed under the "Old API Versions" section.
It's correct that you can create an Event using events.k8s.io. But when I defined a role, which should permit to GET the events emitted by pods, I was not able to do that with the following rule:
- apiGroups: ["events.k8s.io"]
  resources: ["events"]
  verbs: ["get", "list", "watch"]

kubectl get events then throws the following error for example:
Error from server (Forbidden): events is forbidden: User "system:serviceaccount:restricted-example:default" cannot list resource "events" in API group "" in the namespace "restricted-example"

@tengqm But in the API Reference v1.19 the Event type (from the core group) is listed under the "Metadata APIs" section and the types from the event.k8s.io group are listed under the "Old API Versions" section.

Yes, I agree that this is confusing.

@bttger It smells like a bug when the RBAC role doesn't work. I'd suggest you file a bug in kubernetes/kubernetes and tag it '/sig auth'.

@bttger It smells like a bug when the RBAC role doesn't work. I'd suggest you file a bug in kubernetes/kubernetes and tag it '/sig auth'.

I have done.

It smells like a bug when the RBAC role doesn't work

The RBAC role is permitting access to the described API group. To access the old and new API group, both groups must be included in the role.
The documentation at https://kubernetes.io/docs/reference/kubectl/overview/#resource-types does not include all the resources output by kubectl api-resources as it claims:

This output can be retrieved from kubectl api-resources, and was accurate as of Kubernetes 1.13.3

kubectl version
Client Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.3-dirty", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"dirty", BuildDate:"2020-09-17T18:41:21Z", GoVersion:"go1.11.1", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.3-dirty", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"dirty", BuildDate:"2020-09-17T18:41:21Z", GoVersion:"go1.11.1", Compiler:"gc", Platform:"darwin/amd64"}

kubectl api-resources
NAME                              SHORTNAMES   APIGROUP                       NAMESPACED   KIND
...
events                            ev                                          true         Event
...
events                            ev           events.k8s.io                  true         Event

@liggitt Thanks for the details. Filing an issue for updating the resource type list which is too old.

@tengqm @liggitt Thank you. Closing this now.


Intermittent Bad request

From time to time, apache returns BadRequest error.
Apache error - header too long, we need to increase the limit
HW to investigate after holidays

This seems to work:
in /etc/apache2/sites-enabled/000-default.conf put LimitRequestFieldSize 16384 and restart apache (or container)
We will see if this is a proper fix after the holidays

I could not reproduce the problem anymore.


"Dependencies" without graphviz installed produces:  »“Download_macos.php” can’t be found.«

After the info alert that "dot" needs to be installed, another alert pops up with the Finder icon, saying:

“Download_macos.php” can’t be found.

It seems the PHP URL String doesn't work. Maybe constructing a URL directly can help, or the php file extension isn't recognized by NSWorkspace.

This was just a silly bug in converting to a URL. Can you download a try now?


[BUG] Pager within NavigationView scrolls to next page during edge swipe gesture (for navigating back)

Describe the bug
When using a Pager within subview of a NavigationView and then navigating back using a swipe gesture from the left screen edge, the gesture causes the pager to go to the next page while the swipe gesture is being performed, see video below.
To Reproduce

Have a NavigationView that contains a NavigationLink with a destination view that contains a Pager
Navigate into the destination view
Swipe from the left screen edge (pop gesture) to navigate back

Expected: Navigates back to the previous view, the pager doesn't change.
Actual: The pager swipes to the next page while the gesture is being performed. It's doesn't always happen but pretty often, maybe depending on how quick the gesture is performed.
Code to reproduce (drop into the Examples in SwiftUIPagerExample):
import SwiftUI

struct NavigationExampleView: View {
    var body: some View {
        NavigationView {
            NavigationLink(destination: PagerView()) {
                Label("Navigate", systemImage: "folder")
            }
        }
    }
}

struct PagerView: View {
    @StateObject var page: Page = .first()
    // For older versions:
    // @State var page: Int = 0

    @State var items = [
        Item(name: "blue", color: Color.blue),
        Item(name: "red", color: Color.red)
    ]

    var body: some View {
        Pager(page: page,
              data: items,
              content: { item in
                  Text(item.name)
                      .frame(maxWidth: .infinity, maxHeight: .infinity)
                      .background(item.color)
              })
        // Doing this fixes the problem, but disables dragging (duh):
        // .allowsDragging(false)
    }
}

struct Item: Equatable, Identifiable {
    var name: String
    var color: Color

    var id: String {
        name
    }
}

struct NavigationExampleView_Previews: PreviewProvider {
    static var previews: some View {
        NavigationExampleView()
    }
}

Screenshots / Videos
https://user-images.githubusercontent.com/16778/158742041-9943a2d6-adb1-4019-a22d-aa10c06e867b.mp4
Notice how, while performing the edge swipe gesture to navigate back, the pager goes to the next page (from blue to red).
Environment:

OSX: Xcode 13.3, iOS 15.4
Device: iPhone 13 Pro
SwiftUIPager version: 2.3.2 (and earlier versions too)

Additional context
Some observations:

Problem seems to be in onDragChanged in PagerContent. When adding a print for newOffset at the end of the method, I'm getting values like 0.0, 4.0, -386.0. The last one seems strange. I'm not sure how exactly the ongoing gesture for NavigationView affects the pager's gesture coordinates, but somewhere there seems to be the problem.
When changing the swipeGesture to DragGesture(minimumDistance: minimumDistance, coordinateSpace: .global), it fixes the problem in this particular case, but that would probably have other unintended side effects.

I'm having the exact same issue, but with swiping from the top edge to view the notification center.

Hi @robinst thanks for the suggestion. I'll take a look, I'm aware of the issue of that exists when you combine gestures in (or views that implicitly have a gesture) in SwiftUI. In UIKit there are option to request a gesture to fail before being recognized but the same doesn't apply here.
I'll take a look at your suggestion. I can always create a beta version and get feedback from it

Out of curiosity, have you tried delaysTouches and pagingPriority?

@fermoya My use of the component is currently very "barebones", but I'm thinking maybe it would be simpler to just adjust the "gesturable area", so that it doesn't react when the touch starts outside of the safe area?

That should be already possible, the library ships with swipeInteractionArea modifier. It's possible to limit the interaction to just the page and not the whole container.
Problem here is there's no such thing as a safe area here. Pagerexpands and takes up as much space as its container. If the the parent expands till the status bar, then so does Pager. In your case it would be a matter of ensuring this. I'm guessing wrapping Pager into a VStack.
Similarly, using swipeInteractionArea might help in case .page is selected, although I don't think it would make much of a difference if the page reaches the edges of the screen.
I'll take a look at coordinateSpace, it seems like a good start

Out of curiosity, have you tried delaysTouches and pagingPriority?

Yeah just tried that, it doesn't change anything.

I'll take a look at coordinateSpace, it seems like a good start

Note that that breaks the "More" example where swiping is vertical or right to left (because of rotation3DEffect). But that could be fixed by changing the code in onDragChanged to be aware of the direction instead.

this should be fixed here in case you want to check it out:
https://github.com/fermoya/SwiftUIPager/releases/tag/2.3.3-beta.3

Yess, that fixes it, thank you :)! Hopefully it fixes @denizdogan's problem too.

Thanks for the quick fix @fermoya, I've bought you a few coffees as a thank you :)

@fermoya So you just to circle back, swipeInteractionArea did nothing for me, as you expected. My issue is that the pager covers the entire screen, and when I swipe down from the very top of the screen to open the notification center, the pager also swipes up. Should I open another issue about this?

@denizdogan try the mates version 2.3.3 if that helps but what you must ensure then is that Pager stats within the Safe Area. That's up to you, not the library, check out the examples in the repo.

@fermoya Sorry, I should have mentioned I was already using 2.3.3. That's unfortunate to hear, IMO the library would do good to allow us to define offsets from the edges where the pager should ignore gestures.

@denizdogan please open a new issue and share your code or a small snippet to reproduce, maybe a video too. But please, first check out the examples in the repo. I’m using a Pager inside a NavigationView and it doesn’t use the safe area. What I’m saying is Pager doesn’t use the safe area unless you specify it so my guess is there’s something in your code that makes it use it.
please open a new thread


Change Boot Log level from "INFO" to "WARN"

https://github.com/pinpoint-apm/pinpoint/blob/master/bootstraps/bootstrap/src/main/java/com/navercorp/pinpoint/bootstrap/BootLogger.java#L41
-Dpinpoint.agent.bootlogger.loglevel=WARN
You can change the log level with -D option.


Remove datatime from imshow

Dear sir or madam,
My name is Ger  from the Netherlands and have a question about Onvif datatime.
Everything is working well but i have the problem that when i image from cap2 = cv2.VideoCapture('rtsp://, also the date and time are visseble in the cv2.imshow('frame2', frame2)
Can you explane to me how remove date/time or how i remove the seconds from the time from Onvif.
The problem is, when i use the rectangle for camera-detection the seconds give a rectangle everytime the seconds change.
many thanks in advance foor helpen making an solution for this.
Greetings Ger

You have to go to the camera configuration and disable the timestamp.

Dear @ssieb
Thanks for answer and possible solution.
No more thought of it and opened the camera via Icee.
Unfortunately, there is no way to adjust the time settings. Do you know any other options?
In the attachment the problem I am having with Python

Thanks and greetings
Ger

It's very strange that the camera doesn't let you disable the overlays.  I guess you'll have to cut those sections out with software or get your motion detection to ignore those areas.

That i was trying to do.
But i am not a virtuose in Python and wil ignore the above lines of the screen.
How, i have to find out.
Anyway, thanks for helping me
Ger

I have no idea.  You'll have to look at the docs of whatever you're using for motion detection.  I'm guessing that's opencv from your variable names.

I made a if / else and filtering the small rectangle out.
This works but missing the small parts.
I search further and see, perhaps someone no if it is possible to configer the timestamp by Python in the url.


in DAO view, the "Opened decisions N" button shows a number of total ballots (in any state, not only active).

fixed in d0d6a62


OpenSSL::SSL::SSLError

I realize this is a very new gem. Thanks for your work!
I've been spiking recently on integrating Viewpoint into my app and I recently decided I'd like to integrate use of Exchange's Autodiscovery so my user's wouldn't need to know their EWS endpoints.
That being said, I experienced the following while playing with this gem:
client = Autodiscover::Client.new(email: user.email, password: user.password)
#=> #<Autodiscover::Client:0x007ff4c8413768 ...<details snipped>...>

data = client.autodiscover
#=> OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
#   from /Code/ews_poc/vendor/bundle/gems/httpclient-<IP_ADDRESS>/lib/httpclient/session.rb:307:in `connect'

I haven't had to deal with server certificates at all while playing with your `WinRb/Viewpoint' gem, so I thought this might be a "new gem; version 0.1.0; all-of-the-things don't work yet!" kinda thing.
On a whim, I did the following:
pox_request = Autodiscover::PoxRequest.new(client)
# => #<Autodiscover::PoxRequest:0x007ff4c4af9b80 ...<details snipped>...>

pox_request.send(:request_body)
#=> "<?xml version=\"1.0\"?>\n<Autodiscover xmlns=\"http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006\">\n  <Request>\n<EMAIL_ADDRESS>  <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableResponseSchema>\n  </Request>\n</Autodiscover>\n"

pox_request.send(:available_urls).to_a
#=> ["https://advisory.com/autodiscover/autodiscover.xml", "https://autodiscover.advisory.com/autodiscover/autodiscover.xml", nil]

pox_request.instance_variable_get(:@formatted_urls)
#=> ["https://users_domain.com/autodiscover/autodiscover.xml", "https://autodiscover.users_domain.com/autodiscover/autodiscover.xml"]

pox_request.instance_variable_get(:@formatted_urls).each { |url| url.gsub!(/https/, 'http') }
=> ["http://users_domain.com/autodiscover/autodiscover.xml", "http://autodiscover.users_domain.com/autodiscover/autodiscover.xml"]

response = pox_request.autodiscover
#=> #<Autodiscover::PoxResponse:0x007ff4caaca488 ...<details snipped>...>

response.ews_url
#=> "https://mail.users_domain.com/ews/exchange.asmx"

Should I expect that I need to deal with server certificates? Is the gem supposed to handle this sort of thing but it just isn't handled yet?

The reason you are seeing the SSL error is because the https domains that are being tried with Autodiscover have invalid certs for their domain. In the case of advisory.com the cert is only valid for www.advisory.com and autodiscover.advisory.com has a cert for mail.advisory.com. My point being is that this is a misconfiguration for autodiscover. I can add an option to ignore SSL errors but in the meantime you can do one of the following:

Keep those hosts from resolving to an actual web server so autodiscover fails and moves on to the non-https hosts.
Get valid certificates for those hosts
Turn off SSL verification, knowing that this basically removes any point to SSL.

client.http.ssl_config.verify_mode = OpenSSL::SSL::VERIFY_NONE

Awesome answer, thanks! :+1:
This is the information I was looking for. Should I go ahead an close this for you? Or would you prefer to handle that yourself?

Leave it open for now. I'll add an option to ignore SSL in the initialization or something and log it to this ticket.


S3 source connector + Parquet

This takes #327 and adds on Parquet support. Doing this directly instead of https://github.com/rcjmurillo/arroyo/pull/1 so we can get it into the next release.

We'll want to either figure out the issues with the web creation of file sources/sinks (maybe @jbeisen can help here?) or disable it

thank you for following up the work, will close #327.


Port to Firefox Extension

Is it in the roadmap to port this nice extension to Firefox?

Hey there @ramisedhom -- for feature requests, please start a discussion under the "Discussions" tab rather than filing an issue.  On this project (like many others), "Issues" is for only bugs and committed work.
To answer your question briefly, though: probably eventually?

@coddingtonbear sorry didn't notice that you're using discussions section

Oh, there's no reason to be sorry -- that you didn't know that is entirely my fault.  I just haven't found the time to put together a "New Issue" template that'll make that clear.

There is discussion for this here.


Savages with sticks dealing no damage

ive noticed that savages with staffs deal no damage to any npc, only to the player. idk if this is on my end but i have no errors showing up.

Do they deal damage in vanilla?

Do they deal damage in vanilla? Also if they do, can you provide me with a save that has that scenario set up (before it happens ofc) so I can test? (Also if you do explain what I have to do when loading to have it happen) Your saves are located in %AppData%\..\LocalLow\Acid Wizard Studio\Darkwood\1_4Save

im currently in the swamp so theres not alot of savages but this works with any savage that has a staff. theres plenty in chapter 1

There is nothing in my mod that changes the damage of npcs to other npcs, you can try disabling either custom items or custom characters and seeing if it's fixed and then telling me which one it was or you can give me a save where i can consistently test
if you disable both of those and it's still not dealing damage, then in vanilla they function the same
I have no time for a game i already beat and know the lore to spend time playing it for a minor issue like this, I'm sorry that's just how it is


NX 12 Compatibility

Hello Devin,
I have been enjoying the @ionic/angular integration on Nx 11 and cannot thank you enough for your great work!
Recently I am trying to start a new Nx workspace with the latest Nx version using create-Nx, and adding nxtend with ionic angular has not worked out for me ( you can try it out yourself). Is the plugin not compatible with Nx 12? When I was successful in installing the packages, Nx serve command failed with error about missing stack.
This can be replicated by updating to latest nx cli and nx workspace, and starting a new nx ionic angular application from scratch following the nxtend docs. Is this an issue with me missing some steps? If that is the case and you were able to successfully run nx serve with ionic/angular, and build with capacitor then it would be really helpful if you could list the steps you did on your end.
Looking forward to your quick response,
Best Regards
Samrat

Hey there, thanks for this. I haven't had much time to look into the Nx 12 migration yet but I plan to here soon. When that all out there I'll try and remember to update this issue, and the new version will be 12.0.

% ng add @nxtend/firebase
The add command requires to be run in an Angular project, but a project definition could not be found.

What would a good manual workaround be in the meantime? I tried rolling back to Nx 11 and still had problems. Firebase with Nx seems a bit difficult so I was hoping this plugin would do the trick. Thanks!

OK I got it now (I think), even in Nx 12. The docs are off. The way to install firebase that works for me at present (for an app named my-app which is the default in my angular.json) is:
npm install --legacy-peer-deps -D @nxtend/firebase
nx generate @nxtend/firebase:firebase-project
nx run my-app:firebase --cmd init
nx run my-app:firebase --cmd="emulators:start"

That gets you firebase in the top-level package.json, plus the firebase goodies inside apps/my-app including the functions directory, and starts the emulators you installed. There are more challenges to getting functions to work but at least that got me somewhere. Thanks!

Just curious, what npm version are you using? And glad things are working for you. I have an official Nx 12 branch in progress now, I just need to test everything.

I'm using npm 6.4.11 as angular demands v6. Your firebase thing worked fine, but it means the firebase is associated with an individual app, and I wanted the monorepo to model several apps off one firebase, so I backed it out. I find so far that if you only want one firebase instance for the whole monorepo, just working directly with firebase as Google intended, putting the /functions folder and such at top level of the repo, works fine. It's designed to attach to an existing repo, and I couldn't find any definitive way of working with firebase inside Nx, although this thread had some interesting options for more sophisticated uses.
However I am using @nxtend/ionic-angular with Nx12 and it's working great so far, thanks so much! I found out about all this from your ionic blog article and now am wondering why ionic doesn't migrate all their default builds to Nx as it gets us Jest/Cypress rather than the ancient Jasmine/Protractor, and shared libraries, incremental builds, stricter typescript, etc. I should have known about all this a couple months ago.

@spicemix Hi - I've just released an Nx plugin for Firebase that I mainly wrote for my own use, but perhaps might be useful for others. It supports multiple firebase projects in an Nx workspace amongst other handy features: https://www.npmjs.com/package/@simondotm/nxfirebase

Hi, is there an update, when we can use this with nx12? I get these errors, when I try to create a fresh project with nx.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@nrwl/workspace
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nxtend/capacitor
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nxtend/ionic-angular
npm ERR!     dev @nxtend/ionic-angular@"*" from the root project

@DaSchTour v12.0.0 of all the plugins has been released. It sounds like you might need to update your plugins. I would double check the Capacitor 3 migration guide: https://capacitorjs.com/docs/updating/3-0


fix(rhel8): re-enable redhat 8 build and test

these were removed because they were failing. The failure seems transient / has been resolved to putting them back

:tada: This PR is included in version 4.30.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Make it auto-install dependencies (pymbar, etc)

This can be closed since setup.py provides this.

@wesbarnett - can you clarify? Doesn't setup.py just check if the requirements are present?
What I had in mind here was in connection with making it conda-installable (#6 ). Particularly, many packages have information on what other packages are required so that if you, say, "conda install alchemical-analysis" it would also install anything alchemical-analysis requires.

I don't know anything about conda, but I know that if the install method uses setup.py (like pip) it will automatically pull the dependencies via pip. So when I install it on my system using "sudo python setup.py install", it pulls in pymbar. If the minimum version of pymbar is not satisfied with that method it throws an exception (currently they pip-installable pymbar is behind what you require, so it does throw an exception; before that change it did pull in pymbar successfully).


isReadyToStart design

Currently, isReadyToStart depends on a finding a SpotlightAnt widget with index zero (0). That is ok in the automatic playback use case, however I am currently limited for a interactive use case. In my App, the spotlights are very dynamic (depending on the set of active features etc), so I would prefer to have start receive a parameter on either:

which index to start with
or to ignore the lookup for a index zero, but instead use the lowest index it found to start the show

Does that make sense?
As my index calculation is all based on a enum, I don't want to introduce a separate enum or complicate the index calculation logic too much. It's more a matter of which widgets exist in the tree.

Not using an index for the start point can be toggled as a feature.
I'm considering allowing the user to provide a callback to determine which spotlight to show. If we want the very first widget to be shown, we can simply pass a callback that always returns true. Does this make sense to you?

The pull request(#8) is ready. @ened, could you please help ensure that the requirement is satisfied?

Close the issue because it has been a while. Open a new one if needed.


Issues with new Limitation imposed by Docker

Hi, could you please see if you can have a workaround for the following error (You have reached your pull rate limit) that we receive when trying to pull the docker image? Thanks
Failed to pull image "docker.io/vromero/activemq-artemis:2.15.0": rpc error: code = Unknown desc = Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Nothing can be done at my side except perhaps publishing somewhere else, which I'm not keen with right now as discoverability would suffer. Alternatively, at your side consider these solutions: https://www.docker.com/increase-rate-limits


Support multiple connections.

At the moment, the frames from all WebSocket connections are mixed together. The extension should allow for choosing which connection should be inspected.


Match with keypath

[x] I have read the CONTRIBUTING.

🔗 Closing issues
This closes #17
📖 Summary
let predicate: Predicate<String> = .match(description: "description", \.isEmpty)
🛠 About Implementation
✅ About Testing
ℹ Other information

Codecov Report

Merging #38 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #38      +/-   ##
=========================================
+ Coverage   97.08%   97.1%   +0.02%
=========================================
  Files          19      19
  Lines         240     242       +2
=========================================
+ Hits          233     235       +2
  Misses          7       7

Impacted Files
Coverage Δ

Sources/MockSwift/Predicates/Predicate.swift
86.95% <100%> (+1.24%)
:arrow_up:

Continue to review full report at Codecov.

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


Error opening jacocoagent.jar due to long path

Adapted from GRADLE-3547 entered by @wolfs, in turn from this Gradle thread from Vital Lobachevskij.
Expected Behavior
Using the jacoco plugin should never yield an Error opening zip file or JAR manifest missing error regardless of the length of the path to the project (build) directory and to the jacocoagent.jar nested inside of it.
Current Behavior
In a project whose build directory path is so long as to nest the expanded jacoco agent JAR such that the full path is somewhere beyond ~160 or ~170 characters, gradle test errors with the message beginning like the following.
Error opening zip file or JAR manifest missing : ../../build/components/my.long.subproject.name/tmp/expandedArchives/org.jacoco.agent-<IP_ADDRESS>602180812.jar_29dabwwwl4sb8maj0h13tor2d/jacocoagent.jar [...]

Context
In my use case I want to run code coverage on Jenkins agents whose workspace (and thus Gradle build) directories are nested deeply enough to almost always push the jacoco agent's full path past the 160-180 threshhold that triggers the above error.
Steps to Reproduce (for bugs)
Note: Though the OP described this as stemming from a long subproject name, I suspect the error would occur any time the file path length is somewhere beyond 160 or 170--at least on Windows. Here are the original steps:
When ‘jacoco’ plugin is applied for all subproject in my multiproject build
subprojects {
  apply plugin: 'jacoco'
}

gradle test failed with the error like this one:
:my.long.subproject.name:test
Error opening zip file or JAR manifest missing : ../../build/components/my.long.subproject.name/tmp/expandedArchives/org.jacoco.agent-<IP_ADDRESS>602180812.jar_29dabwwwl4sb8maj0h13tor2d/jacocoagent.jar
Error occurred during initialization of VM
agent library failed to init: instrument
Could not write standard input into: Gradle Test Executor 2.
java.io.IOException: The pipe is being closed
        at java.io.FileOutputStream.writeBytes(Native Method)
        at java.io.FileOutputStream.write(FileOutputStream.java:326)
        at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
        at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:56)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
        at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
:my.long.subproject.name:test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':my.long.subproject.name:test'.
> Process Gradle Test Executor 2 finished with non-zero exit value 1

I've found that Gradle starts 'Gradle Test Executor' processes using commands like this one:
java.exe -Djava.security.manager=worker.org.gradle.process.internal.worker.child.BootstrapSecurityManager -javaagent:../../build/components/my.long.subproject.name/tmp/expandedArchives/org.jacoco.agent-<IP_ADDRESS>602180812.jar_29dabwwwl4sb8maj0h13tor2d/jacocoagent.jar=destfile=../../build/components/my.long.subproject.name/jacoco/test.exec,append=true,inclnolocationclasses=false,dumponexit=true,output=file,jmx=false -Xms256m -Xmx1024m -Dfile.encoding=windows-1251 -Duser.country=US -Duser.language=en -Duser.variant -ea -cp C:\Users\Vital_Lobachevskij\.gradle\caches\2.14\workerMain\gradle-worker.jar worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Test Executor 2'

It works in the same way for all subprojects. But, if the subproject name is rather long, e.g. ‘my.long.subproject.name’, Gradle can’t open jacocoagent.jar. On my local, full path to this jar for ‘my.long.subproject.name’ is
d:\Projects\...\build\components\my.long.subproject.name\tmp\expandedArchives\org.jacoco.agent-<IP_ADDRESS>602180812.jar_29dabwwwl4sb8maj0h13tor2d\jacocoagent.jar (179 chars) and the error is thrown.
If I move project folder to the root of disk D, the full path will be shorter (156 chars) and unit tests are passed successfully and code coverage is generated.
Your Environment
OP's env: Gradle 2.14 on Windows 10
My env: Gradle 3.1 and Zulu OpenJDK 1.8.0_102-b14 on Windows 7 Pro

I had the same issue, can confirm that reducing full path length fixes the issue.

Is there a workaround for this if the project path or name cannot be changed? Are there any plans for fixing this (if even possible in Gradle, as opposed to JaCoCo)?

Oh and just by the way, this affects Gradle version 5.6.1 still.

We are facing an issue on similar lines where commands like 'gradle build' and 'gradle test' runs successfully but if I run 'gradle clean build' it fails with below error:
> Task :compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Could not write standard input to Gradle Test Executor 2.
java.io.IOException: The pipe is being closed
        at java.io.FileOutputStream.writeBytes(Native Method)
        at java.io.FileOutputStream.write(FileOutputStream.java:326)
        at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
        at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:66)
        at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:51)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
        at java.lang.Thread.run(Thread.java:748)

> Task :test
Error occurred during initialization of VM
agent library failed to init: instrument
Error opening zip file or JAR manifest missing : build/tmp/expandedArchives/org.jacoco.agent-0.8.4.jar_7bfc4fd986d61dbf92065775ff3714a0/jacocoagent.jar
Error occurred during initialization of VM
agent library failed to init: instrument
Error opening zip file or JAR manifest missing : build/tmp/expandedArchives/org.jacoco.agent-0.8.4.jar_7bfc4fd986d61dbf92065775ff3714a0/jacocoagent.jar

You can see that path is not that big. What I have noticed is during 'gradle build' and 'gradle test' it is able to create 'expandedArchives' folder under 'build/tmp' location and hence tests run successfully but while running 'gradle clean build' it cleans build folder but can not create the required folder structure again.
Any leads on this issue. How can I resolve this.
Here is the build environment:
Gradle - 5.6.2
Jacoco - 0.8.4
IntelliJ - 2019.2.3 Ultimate Edition
OS - Windows 7

I submit that a system that auto-closes tickets because no one on your end looked at it is sub-optimal. It doesn't make these issues go away.

I am facing the same issue, Any known fix/workaround for this?

We are facing an issue on similar lines where commands like 'gradle build' and 'gradle test' runs successfully but if I run 'gradle clean build' it fails with below error:
> Task :compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Could not write standard input to Gradle Test Executor 2.
java.io.IOException: The pipe is being closed
        at java.io.FileOutputStream.writeBytes(Native Method)
        at java.io.FileOutputStream.write(FileOutputStream.java:326)
        at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
        at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:66)
        at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:51)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
        at java.lang.Thread.run(Thread.java:748)

> Task :test
Error occurred during initialization of VM
agent library failed to init: instrument
Error opening zip file or JAR manifest missing : build/tmp/expandedArchives/org.jacoco.agent-0.8.4.jar_7bfc4fd986d61dbf92065775ff3714a0/jacocoagent.jar
Error occurred during initialization of VM
agent library failed to init: instrument
Error opening zip file or JAR manifest missing : build/tmp/expandedArchives/org.jacoco.agent-0.8.4.jar_7bfc4fd986d61dbf92065775ff3714a0/jacocoagent.jar

You can see that path is not that big. What I have noticed is during 'gradle build' and 'gradle test' it is able to create 'expandedArchives' folder under 'build/tmp' location and hence tests run successfully but while running 'gradle clean build' it cleans build folder but can not create the required folder structure again.
Any leads on this issue. How can I resolve this.
Here is the build environment: Gradle - 5.6.2 Jacoco - 0.8.4 Java - 8 IntelliJ - 2019.2.3 Ultimate Edition OS - Windows 7

Have same issue, Gradle 8.1.1 JDK 17

We have the same isisue gradle 7.5.1 jacoco 0.8.8 MacOs

clean build started failing for me out of the blue, even for projects/configurations that worked before. Gradle 8.1, 8.5, 8.6, 8.7, does not matter. As mentioned above, simply build or check works.
While inspecting DEBUG logs and trying to debug what Gradle does internally, I noticed that file resolution for jacocoAgent and lock acquisition on /build/tmp/.cache/expanded happens before tasks start. As a result, Gradle properly unpacks jacoco JAR and gets a valid path, but :clean task just wipes the whole build dir after that.

I'm having the same issue on a Mac M3 with IDEA 2024.1 update. clean build fails but just build is fine.

Up the issue and approve @edudar 's  assumption: idea-IU-233.15026.9 (previous build from now) works fine, current build idea-IU-241.14494.240 has the issue. My issue was like that with jacocoagent.jar, after downgrading build is fine again.

Im facing the same issue:

IntelliJ IDEA 2024.1 (Ultimate Edition), Build #IU-241.14494.240, built on March 28, 2024
gradle-7.6.1
useing plugin { id 'jacoco' } without a specific version


[BEAM-4501] Update a few more apache/beam-site references

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

Run Website PreCommit

R: @swegner

LGTM, thanks!


Alternate Destinations - URI issue

If you configure or add another destination, there is an issue with the URI.
You do not recieve any data
The issue is the uri for anything other than default needs to be "complete" https://splunk:8088/services/collector/event
For now the workaround is like the example below
SC4S_DEST_SPLUNK_HEC_BACKUP_URL=https://SPLUNK_SERVER:8088/services/collector/event

confirmed issue


Schema.org metadata only includes primary author

Issue Summary
The schema.org metadata in JSON-LD only shows the primary author. For multi-author posts that means that author information is missing even though multiple authors are shown elsewhere.
Steps to Reproduce
On a recent Ghost version (I use Ghost Pro) look at the schema.org of a post with multiple authors (either in the page source or with a browser plugin).
Ghost Version
5.25.3
Node.js Version
16
How did you install Ghost?
Ghost Pro
Database type
MySQL 8
Browser & OS version
Chrome 108 (arm64)
Relevant log / error output
n/a

Code of Conduct

[X] I agree to be friendly and polite to people in this repository

What was it that you were expecting to see? References for how to handle this correctly in Schema.org would be great.

I expected to see all authors I added in the Ghost editor to show up in the schema.org markup, just as they do in the Ghost API. Basically generating the schema.org from authors (which can be one or more JSON objects) instead of generating the schema.org from the primary author. I can do a pull request if that helps.

I left a comment a while ago that described the issue. I will make a pull request to clarify what needs to be done, maybe that is easier.


Make dispatch promisified

For most of my projects, I have to make multiple dispatch calls in process and I normally write like this:
const logic = createLogic({
  type: FOO,
  async process({ getState, action }, dispatch, done) {
    try {
      const json = await api.get(...).getBody();
      dispatch(setAuthToken(json.token));
      dispatch(fetchUser());
    } finally {
      done();
    }
  }
});

But this (very occasionally) fails, because fetchUser relies on a valid auth token and sometimes it was called before setAuthToken was completed, despite being dispatched order.
What about making dispatch a function that returns a promise? So that I can use await in front of it. Like this:
await dispatch(setAuthToken(json.token));
dispatch(fetchUser());

I can do monkeypatching for redux's store.dispatch function, but it looks like redux-logic's dispatch is different.

FYI, here's my implementation for redux's store.dispatch patching.
store.js
const store = createStore(...);
const { dispatch } = store;

store.dispatch = action =>
  new Promise(resolve => {
    EE.once(`redux-action/${action.type}`, resolve);
    dispatch(action);
  });

general-logics.js
const promiseStyleDispatchLogic = createLogic({
  type: '*',
  process({ action }) {
    EE.emit(`redux-action/${action.type}`);
  }
});

EE is an instance of EventEmitter (https://github.com/primus/eventemitter3)

I replaced this monkeypatching with a redux middleware since monkeypatching looks a little hacky. Here's my simple middleware:
function promisifyDispatchMiddleware() {
  return next => action =>
    new Promise(resolve => {
      if (action.type) {
        EE.once(`redux-action/${action.type}`, resolve);
      }
      next(action);
    });
}

@artificis is the action for setAuthToken not synchronous? I'm wondering why it would need a promise.

 There are other cases. For instance, I need to update intercom parameter if user logs in, and I want this action to be dispatched only after fetchUser action is complete. I know I can solve this by moving code that updates intercom parameter into fetchUser logic, but this breaks DRY principle if I need to update intercom data in other place also. I want multiple action dispatches to be composable, not monolithic.

@artificis is the action for setAuthToken not synchronous? I'm wondering why it would need a promise.

Good day,
I have an effect that executes an async function, but after that function is executed my effect does not dispatch the next sync action. Any guidance on what I could be doing wrong?
The code sample below:
   effects: [
      {
        type: [`FORM_TRANSMIT`],
        gaurd: fn((t) => (ctx, allow, reject) => {
          const payload = t.omit(['status'], t.at('action.payload', ctx))
          if (t.allOf([t.notEmpty(payload), t.notNil(payload)])) {
            allow(ctx.action)
          }
          reject()
        }),
        options: { dispatchReturn: false },
        effect: fn((t) => async ({ getState, action }, dispatch, done) => {
          const state = getState()

          const viewActions = initViews.state.viewActions[action.payload.active]
          const [err, res] = await a.of(
            viewActions.transmit({
              state: state[viewKey].views[action.payload.active],
              next: action.payload,
            })
          )

          dispatch(
            ctx.mutators.formTransmitComplete({
              viewKey,
              payload: t.merge(state[viewKey], { user: res.user }),
            })
          )
          done()
        }),
      },
      {
        type: `MODAL_CHANGE`,
        effect: fn((t) => (context, dispatch, done) => {
          const state = context.getState()
          return (state.home.modal.formData = context.action.payload)
        }),
      },
    ]

My create logic function looks as follows:
createLogic({
          name: view.name,
          type: t.isType(type, 'array')
            ? t.map((actionType) => `${view.name}/${actionType}`, type)
            : `${view.name}/${type}`,
          validate: gaurd,
          processOptions: {
            dispatchReturn: t.atOr(false, 'dispatchReturn', options),
          },
          process: effect,
          ...extra,
        })

When I return another action from the effect, only then does it work.


Option to suppress the log level in log messages

Duplicate of #414. Implemented as showLevel which defaults to true.


Grammar combinator for strings

I've given a nicer definition, but actually I added a combinator just for StackPrism which should probably be in Data.StackPrism.
Also, I just realized I didn't actually add any exports for any of the new combinators I added in these pull requests.


Detect if webcam is in use by a process

This should be easy enough to do, I think - you should be able to look at fuser /dev/video0. If it reports something, then the webcam is on - otherwise it's off. (You might be able to get fancy and check video1 as well.)
Microphone might be handy, too, but I don't think you can get there from /dev/ - Google says you need to look at find /proc/asound -name status -exec grep -v closed {} + and see if it reports an output or not.
Even if it isn't natively built-in, it might be handy as an example script for people who want to write their own scripts?

For completeness, here's the script I run:

# Check if /dev/video0 is being used by any process
output=$(fuser /dev/video0)

# Initialize variables
sensor_state="false"

# Check the length of the output string
if [ ${#output} -gt 0 ]; then
  sensor_state="true"
fi

# Create the JSON output
json_output='{
  "schedule": "@every 5s",
  "sensors": [
    {
      "sensor_name": "Webcam",
      "sensor_type": "binary",
      "sensor_device_class": "power",
      "sensor_icon": "mdi:webcam",
      "sensor_state": "'"$sensor_state"'"
    }
  ]
}'

# Output the JSON
echo "$json_output"```

Note that although the sensor UI correctly reports the webcam state, for some reason Home Assistant always reports `on`. Not sure if that's a bug in my script or Go HASS Agent.

Hey @Jay2645 I like this idea, I can easily see knowing when the microphone or webcam is in use as being useful to automate some action with Home Assistant.
I will have to think about whether it is possible to get this info without polling directly. I'll see if I can find it somewhere on D-Bus...
I also like the idea of collecting example scripts. I'm wondering where would be a good place to put them? In the go-hass-agent repo? In another separate repo?
I can also see a docs improvement I should make around binary sensors and their values :wink: I will add that in the next release.

Sorry - for some reason Github has stopped sending me emails!
Somewhere like docs/examples would be good, in my opinion. People will be going into the docs anyway to learn how to make scripts, and having examples right next to them makes sense to me. If it were to be in another repo, I would expect the docs to also be in that repo (like the main Home Assistant project). But I think for the short-medium term, having it in here makes perfect sense. They're just text files, so they're small.

Thanks for the script, it works very well :)
I updated this line to detect if any camera is active:
From:
output=$(fuser /dev/video0)

To:
output=$(fuser /dev/video*)


add Indicator

Looking for a good animation library. I don't really want to write CATransaction.begin and commit.


Feature Request: Develop an Automatic Report Generator with Scheduler

Re: enhancement
It would be beneficial if you can develop an automatic report generator with email scheduler.
Options in this feature/module would;

Select Report
Select who to email to - predefined or adhoc
Select frequency, reoccurring days, say send OAS Summary report, every fortnight on a Thursday morning at 9 am

All the reports by you Pete and Topo are brilliant, By having a automatic scheduler, it saves the leaders having to log in and run one of at least 2-4 reports every couple of times per month. Ultimately the idea is the reports lands in the leader email box. He/She will simply open and print the PDF with minimal effort. The report can either be posted on a notice board or used when doing badge work with the Scout/s.
Regards,
Did

Yeah, I agree. I also wanted to have alerting for things like pending approvals and maybe a combination of toast notifications and emails depending on the user settings. This will require some sort of "Back End" which I am working through some ideas that would still keep the data within the Scouts systems to reduce and security issues or concerns.
I am trying to work out if every branch uses Office 365 because if they do I have a few options of using its inbuilt features to manage these sorts of back-end tasks and simultaneously keeping it within Scouts controlled areas.


SyntaxError: invalid syntax

Tried running it the first time and seeing this.

Using Python 2? Need a recent enough version of Python 3.

@gakada thank you this solves it. I'm new to python 😇


RUN apt-get update missing

File: engine/examples/mongodb.md, CC @mstanleyjones
RUN apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv EA312927
RUN apt-get install -y --no-install-recommends software-properties-common
RUN echo "deb http://repo.mongodb.org/apt/ubuntu $(cat /etc/lsb-release | grep DISTRIB_CODENAME | cut -d= -f2)/mongodb-org/3.2 multiverse" | tee /etc/apt/sources.list.d/mongodb-org-3.2.list

Thanks for the report. FYI, we are now pulling in all the docs from the official Docker library images, and will probably eventually deprecate this content in favor of https://docs.docker.com/samples/mongo/.
cc/ @johndmulhausen

As far as I can tell you've done the content migration and https://docs.docker.com/engine/examples/mongodb/ no longer exists, so there's nothing to fix.
@selvendran-varathan I'm going to close this issue, but feel free to comment.


Fix avatar offset on PR/issue timeline view

Before:

After:

Codecov Report

Merging #13753 (24117e8) into master (63aeb0a) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13753   +/-   ##
=======================================
  Coverage   42.23%   42.23%
=======================================
  Files         699      699
  Lines       76957    76957
=======================================
+ Hits        32503    32505    +2
  Misses      39090    39090
+ Partials     5364     5362    -2

Impacted Files
Coverage Δ

modules/queue/workerpool.go
58.77% <0.00%> (-1.23%)
:arrow_down:

modules/avatar/avatar.go
54.76% <0.00%> (+4.76%)
:arrow_up:

modules/util/timer.go
85.71% <0.00%> (+42.85%)
:arrow_up:

Continue to review full report at Codecov.

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


Don't log unwanted when not initialized

Thank you for your contribution to Abseil!
Before submitting this PR, please be sure to read our contributing
guidelines.
If you are a Googler, please also note that it is required that you send us a
Piper CL instead of using the GitHub pull-request process. The code propagation
process will deliver the change to GitHub.

Sorry, I don't have any google account, so cannot sign this damned CLA
Feel free to consider this as a bug report, and fix it yourself.


Got a codec error in download process

like this.

hello👋 can you send the text version instead into this thread? copy paste it maybe? thank you.

I think i found the problem. My method to check if aria2 is installed or not is by calling it with subprocess.getoutput. I think i'll change the method into if os.path.exists instead.

hello👋 can you send the text version instead into this thread? copy paste it maybe? thank you.

oh,of course.
————————————————————————————————————————————
Traceback (most recent call last):
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\site-packages\gradio\routes.py", line 337, in run_predict
output = await app.get_blocks().process_api(
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\site-packages\gradio\blocks.py", line 1015, in process_api
result = await self.call_function(
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\site-packages\gradio\blocks.py", line 833, in call_function
prediction = await anyio.to_thread.run_sync(
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\site-packages\anyio\to_thread.py", line 31, in run_sync
return await get_asynclib().run_sync_in_worker_thread(
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\site-packages\anyio_backends_asyncio.py", line 937, in run_sync_in_worker_thread
return await future
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\site-packages\anyio_backends_asyncio.py", line 867, in run
result = context.run(func, *args)
File "F:\AI Art Tools\stable-diffusion-webui_2301\extensions\batchlinks-webui\scripts\batchlinks-downloader.py", line 1430, in run
civitdown2(currentlink, currentfolder, choosedowner, currenttorename, False, civitdefault, civitpruned, civitvae)
File "F:\AI Art Tools\stable-diffusion-webui_2301\extensions\batchlinks-webui\scripts\batchlinks-downloader.py", line 746, in civitdown2
hfdown(data_url, data_save_path, downloader, currentmode)
File "F:\AI Art Tools\stable-diffusion-webui_2301\extensions\batchlinks-webui\scripts\batchlinks-downloader.py", line 877, in hfdown
checkaria = subprocess.getoutput(ariapath)
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\subprocess.py", line 643, in getoutput
return getstatusoutput(cmd)[1]
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\subprocess.py", line 624, in getstatusoutput
data = check_output(cmd, shell=True, text=True, stderr=STDOUT)
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\subprocess.py", line 420, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\subprocess.py", line 503, in run
stdout, stderr = process.communicate(input, timeout=timeout)
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\subprocess.py", line 1139, in communicate
stdout = self.stdout.read()
File "F:\AI Art Tools\stable-diffusion-webui_2301\python\lib\codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd5 in position 4: invalid continuation byte
————————————————————————————————————————————

I think i found the problem. My method to check if aria2 is installed or not is by calling it with subprocess.getoutput. I think i'll change the method into if os.path.exists instead.

got it,thank you so much

@nemuruibai hello👋 i hopefully fixed the thing now. I checked it with a virtual machine to make sure it work.
Also remember that you need to makes sure that you add python 3.10 to PATH when you were installing Python before


Add XInput device ID for wireless Series 2 Elite controller

Adds to the list of XInput GUIDs the XInput device ID for the Xbox One Elite Series 2 controller when connected wirelessly.
Resolves #81816
Change is compatible with 3.x.

Thanks!

Got it, thank you!

Cherry-picked for 4.1.3.

Cherry-picked for 3.6.

Cherry-picked for 3.5.4.


manageSubscriptionStatusChange activated twice after subscribing

Bug report
firestore-stripe-subscriptions
Describe the bug
The manageSubscriptionStatusChange function is activated twice when someone subscribes, this doesn't seem necessary to me. It happens once on the customer.subscription.created event and once for the checkout.session.completed. If I'm thinking correctly here the checkout.session.completed event is actually not necessary for everything to work?
To Reproduce
No steps necessary, see logs that proof that it activates the function twice.
Expected behavior
Remove the checkout.session.completed event entirely, or give guidance on why its activated.

@koenmtb1 Stripe Checkout waits for checkout.session.completed to be processed by the webhook handler before redirecting back to your return_url. This way you know for sure that the subscription (and optionally the custom claim) has been created in Cloud Firestore by the time your user returns back to your app, making sure they will see their subscription status reflected at that point.
Therefore if you use Stripe Checkout, you will likely want to listen to checkout.session.completed but you could remove customer.subscription.created from your list of events in your Stripe Dashboard.
However, customer.subscription.created is needed if you create the subscription through different means than Stripe Checkout, e.g. if you create subscriptions in your Stripe Dashboard, or directly via the Stripe API.
But depending on your integration, you can potentially remove one of the events from your list.

@thorsten-stripe Thank you for your response, I also understand a little bit more.
But I have another question about this. You told use we shouldn't remove customer.subscription.created because we can create subscription in Dashboard or directly via Stripe API.
What about the other way around? Why not removing checkout.session.completed?
I don't see any use case when checkout.session.completed is needed for subscription.
We can use only customer.subscription.created, customer.subscription.updated and customer.subscription.deleted.

The reason you want to use checkout.session.completed is that Stripe Checkout waits for the checkout.session.completed webhook event to be processed before redirecting your customer back to your page. This means that we are sure that by the time your customer lands back on your page, we have updated your Cloud Firestore and custom claims. This isn't the case for customer.subscription.created, so it could happen that your customer lands back on your page but their subscription status has not yet been synced. Hope that makes sense.

Thank you for your response.
Now, it totally makes sense for me.

@thorsten-stripe I've another question to these events. At the end of customer.subscription.created, the code run the following code: https://github.com/stripe/stripe-firebase-extensions/blob/114d09c6f4d3310acd3cc67702991ad02808047d/firestore-stripe-subscriptions/functions/src/index.ts#L436
If I understand correctly, it updates the customer personal information provided during checkout session, right? For example during checkout, the customer can indicates his name for his payment and it also update his own customer information by adding his name. Otherwise, the customer name stays empty.
My question is why we don't use the following attribute: https://stripe.com/docs/api/checkout/sessions/create
Is it the same thing?


Manufacture Top and Bottom Plate

Laser cut the Top and Bottom Plate out of HDPE.
Material will be received on Friday 3/23.
Cameron will get it laser cut on Saturday 3/24.

Will need to be formatted in dxf file

Plates were cut with laser cutter out of black HDPE. Any further machining can be done by hand with hand drill.


Generated code for AllianceService/ListUsers2 doesn't work

It should return a list of Message objects and a list of User objects, but it only returns a list of Message objects. This edge case of an endpoint returning 2 collections hasn't been noticed, yet and requires an overhaul of the backend.

Changed:

the way return types of endpoints are being determined
the way return types are being passed to core.get_entities_from_path()
the way core.get_entities_from_path() parses the return type from the endpoint given


Msys2 git create strange directory when path with "/" delimiter is used

Please, look at screenshot

Git created garbage folder "c" in the current directory.
This is only appeared, when I use unix-style delimiter in path.

Seems you use not MSYS2 version of git

Also don't use it in cmd, but in MSYS2 shell or MinGW shell instead.

Chech that you use git from my msys2 git package

I have only msys2 git in my system.
Running from msys2 shell has the same effect. Garbage folder still create in current working dir.

I confirm the problem, but at the same time, trying to use Windows style path with the msys2 version of git is not a good idea. The msys2 version of git works best with Unix style paths like /c/Temp/.... If this is coming from a tool, I suggest you to switch to a native version of git (i.e. Git For Windows, it can be installed proper instead msys2 if needed). This version is a native Windows version and deals correctly with Windows paths.
Note below, C:\msys2\tmp is where /tmp is mapped by default, adapt to your system.
Tests using msys2 git (/usr/bin/git):
$ mkdir -p /tmp/test_git_msys2
$ cd /tmp/test_git_msys2

$ which git
/usr/bin/git

$ git --version
git version 2.7.2

$ git clone https://github.com/rtyley/small-test-repo.git 'C:/msys2/tmp/test_git_msys2/another'
$ ls
another/    C:/
$ rm -rf *

$ git clone https://github.com/rtyley/small-test-repo.git 'C:\msys2\tmp\test_git_msys2\another'
$ ls
another/
$ rm -rf *

Tests using mingw64 a.k.a Git For Windows version git (/mingw64/bin/git):
$ mkdir -p /tmp/test_git_mingw64
$ cd /tmp/test_git_mingw64

$ which git
/mingw64/bin/git

$ git --version
git version 2.7.2.windows.1

$ git clone https://github.com/rtyley/small-test-repo.git 'C:/msys2/tmp/test_git_mingw64/another'
$ ls
another/
$ rm -rf *

$ git clone https://github.com/rtyley/small-test-repo.git 'C:\msys2\tmp\test_git_mingw64\another'
$ ls
another/
$ rm -rf *

Bottom line, use either Unix path (/c/Users/...) or Windows Path (C:\msys2\tmp) or use a native git package.
Regards,
Matt

Thank you for advice.
I tried windows native git and it works without this issue.

@zdm, no problem.
@Alexpux Feel free to close issue is you think it's a won't fix.

I need to fix this.

Is this patch already merged and updated git version accessible via pacman? I see, that issue still present.

@zdm You can check it. Compare your git version with pkgbuild in git repo.
$ pacman -Ss |grep "/git"
msys/git 2.8.1-1 (VCS)

Pkgbuild in git repo is 2.8.1-2.

If you want the fix before it hits the repos, then build it for yourself.
It's probably a lot easier than you imagine.

Hi.
FYI, today git was updated to msys/git 2.8.1-5 (VCS) [installed], but issue still present.

I had fixed it for Windows-normal paths (using backslashes), but not for Windows-mixed paths (using slashes). Now it should work with either.

[warning] git man installation related.
pacman -S git

...
warning: could not get file information for usr/share/man/man3/Git::I18N.3pm.gz
warning: could not get file information for usr/share/man/man3/Git::SVN::Editor.3pm.gz
warning: could not get file information for usr/share/man/man3/Git::SVN::Fetcher.3pm.gz
warning: could not get file information for usr/share/man/man3/Git::SVN::Memoize::YAML.3pm.gz
warning: could not get file information for usr/share/man/man3/Git::SVN::Prompt.3pm.gz
warning: could not get file information for usr/share/man/man3/Git::SVN::Ra.3pm.gz
warning: could not get file information for usr/share/man/man3/Git::SVN::Utils.3pm.gz
....
success installed with warning

look at those dir usr/share/man/man3/Git* have two underscore should it be one _ or colon ::?
thanks


Remove the copying CodeCommit instruction

Remove the copying CodeCommit instruction since the updated command takes care of that

is https://github.com/jackiu/aws-fault-injection-simulator-workshop.git still up? looks like its not there or in private state.


React Native image borderRadius not working.

Image borderRadius/Native base Thumbnail circular shape/Gifted chat showUserAvatar={true}/any type of circular images are not working in Android 5.1 Lollipop.
Details
I am trying to display an image from a URL. In the emulator image displays perfectly. When I run this on the device it displays a black block and after some moment the app crashes without any error. (I have reveiw the adb logcat)
If I remove borderRadius property from Image style it works perfectly. But I need the circular shape.
I tried to native-base Thumbnail instead of Image but the problem persists. Then I tried to make a circular shape using View with overflow:hidden property but image edge not smooth. How can I solve this?
Screenshots
Black Block image in the device

Example of code

Please pardon any mistake and help me.

react-native info command not work.
_

C:\Users\Name\MyProject>react-native info
info Fetching system and libraries information...
error Unable to print environment info.
Error: Command failed: wmic os get Caption
'wmic' is not recognized as an internal or external command,
operable program or batch file.

_
react-native -v command:
react-native-cli: 2.0.1
react-native: 0.61.5

Try to wrap the image with a view with the dimensions you want and, in the image, put these styles to resize, like this:
return (
        <View
            style={styles.container}
        >
            <Image
                style={styles.image}
                source={{ uri: <LINK OF IMAGE> }}
            />
        </View>
    )
}

const styles = StyleSheet.create({
    container: {
        height: 150,
        width: Dimensions.get('window').width / 3,
        marginHorizontal: 5,
        justifyContent: 'center',
        alignItems: 'center',
    },
    image: {
        flex: 1,
        width: null,
        height: null,
        resizeMode: 'contain'
    },
})

If it doesn't work, try replacing the image style with:
image: {           width: '100%',         resizeMode: 'contain',         borderRadius: 60  }

I have try this. Image not display both emulator and device.

The problem is solved.
The main problem was Google Cloud Storage where I stored the pictures.
Having trouble using various features of Google Cloud Platform from my country.
The black blocks we see here are basically loading from cache memory. So these are showing black block in circular shape. Because, images are saved in cache memory with square shape.
I have tried in VPN and everything is ok.
Thank you.

The problem is solved.
The main problem was Google Cloud Storage where I stored the pictures.
Having trouble using various features of Google Cloud Platform from my country.
The black blocks we see here are basically loading from cache memory. So these are showing black block in circular shape. Because, images are saved in cache memory with square shape.
I have tried in VPN and everything is ok.
Thank you.