Window switcher "Spotlight style"

Basically as stated by the title, press a hotkey, get some sort of input box up that can search through open windows using part of the window title (or app name?) and similar. Could potentially be extended to to add launcher features later on.

I might be alone in thinking this, but I don't actually think this should be apart of kwm itself, I think that kwm should offer support for apps like Alfred, Flashlight (spotlight) or Quicksilver though kwmc commands.
There would be a command like kwmc read window-list which would return a delimited list of windowIds and window names. This list could then be parsed by applications and used in their interface. Then the windowID could be used to tell kwmc window -f id 30303 to focus that particular window.
Curious what other people think though.

Seems like a good idea if integration like that is possible. I have never used Alfred and similar so no idea how that would be achieved.

All of the ones I mentioned allow for scripting. I know for a fact that such a integration can be achieved with Alfred. It has a very extensive "workflow" (scripting) system https://www.alfredapp.com/workflows/

There would be a command like kwmc read window-list which would return a delimited list of windowIds and window names. This list could then be parsed by applications and used in their interface. Then the windowID could be used to tell kwmc window -f id 30303 to focus that particular window.

So something like the following {{id, name}, {id, name}, (id, name}}, and kwmc window -f id windowid to give focus?

This could be expanded to a more general kwmc Alfred workflow, considering Alfred workflows have support for autocompletion based on what has already been typed and all that and can even give subtexts for every command.

Yeah, I was imagining something a lot like that, expect instead of braces and commas there would be new lines:
id, app, name
id, app, name
id, app, name
...etc

I've made a very basic Alfred workflow that just runs kwmc commands here. If we can get the window ids I can work on getting that implemented.

kwmc read windows will return a list of visible windows on the active space:
windowid, app, title
windowid2, app2, title2

kwmc window -f id windowid can be used to set focus.

I have a super hacked together poof of concept Alfred workflow, it works!
Some things I've noticed working on it: Comma was a bad choice on my part, we maybe should have gone with tabs? Commas can show up in window titles, not sure about tabs. We might need a more easily delimited character. (can tab characters show up in window titles?)
If anyone is curious to try what I have so far I can upload it.

Newlines cannot appear in window titles, just change it to. I'm very much interested in your script if you'd like to share.
windowid
app
title

windowid
app
title

That would actually make it a little bit more awkward to parse. I can solve the comma issue, I just need to not use bash to do the Alfred Workflow in.
kwm window switcher.zip
Here is the Alfred workflow. Please keep in mind this is proof of concept only and will change. You will also be required to edit both of the scripts in the workflow to point to your kwmc location.
There are probably bugs and issues, you've been warned :)

Also, I have noticed that kwmc read windows only lists the windows of the currently focused display. Is there a way all windows can be returned or is there a technical limitation to that?

I can make it return windows of all monitors if needed.

Alfred only gets opened in the main display, so having all windows returned
might be useful.
However I don't know how the focus and window list behaves with specs. That
may be a concern.
On Tue, Feb 9, 2016 at 11:48 AM koekeishiya<EMAIL_ADDRESS>wrote:

I can make it return windows of all monitors if needed.
—
Reply to this email directly or view it on GitHub
https://github.com/koekeishiya/kwm/issues/115#issuecomment-182029589.

Focusing across monitors should work fine with how Kwm currently works. I'll give it a try in a sec and push a commit.

@koekeishiya
That last commit made the read windows way too inclusive. It is including some menu bar windows
116755, BetterTouchTool,
116752, BetterTouchTool,
712, BitBar,
115875, Dropbox,
115872, Dropbox,
167, iStat Menus Status,
120, SystemUIServer,
111756, Alfred 2,
111753, Bowtie,
111750, iStat Menus Status,
111749, iStat Menus Status,
111748, iStat Menus Status,
111747, iStat Menus Status,
111746, iStat Menus Status,
111745, iStat Menus Status,
111744, iStat Menus Status,
111741, LastPass,
111734, Plex Media Server,
111736, BitBar,
111737, Spotlight,
111725, SystemUIServer,
111722, SystemUIServer,
150, iStat Menus Status,
146, LastPass,
83092, Plex Media Server,
69644, Spotlight,
205, Alfred 2,
201, Bowtie,
195, iStat Menus Status,
189, iStat Menus Status,
183, iStat Menus Status,
173, iStat Menus Status,
157, iStat Menus Status,
115, SystemUIServer,
111709, Window Server, Menubar
108, Window Server, Menubar
116827, kwm-overlay,
116826, kwm-overlay,
80485, iTerm2, zsh
64471, iTerm2, zsh
30625, Messages,
68368, iTerm2, node
112732, Google Chrome,
112733, Google Chrome, Tree restore issues with too few windows · Issue #157 · koekeishiya/kwm
85554, Slack, Slack
90240, iTunes, iTunes

@koekeishiya thanks, that last commit fixed the filtered window list, and it does in fact work across displays.
I have run into an issue where if the space is in monocle mode it does not bring the window to the front, just focus the monocle window that is currently visible

Does this happen if the monocle screen already has focus?

It might be worth considering using a pre-specified format, like for instance json.
This would handle escaping of any character and has encoding and decoding  libraries available for most languages.

@koekeishiya good call, it only happens when the monocle screen does not have focus. If it does, it works as expected.


Detect "DB Down" and return an error in ".well-known/openid-configuration"

Question
Dears,
in my installation of IdS4 I use mySql (with Entity Framework) for User Store and json files for clients configuration: I realized that when the mySql service is stopped, the .well-known/openid-configuration api responds correctly however.
My question is: in your opinion, what's the best method to propagate the connection error towards the .well-known/openid-configuration api response?

I would rather implement a health check endpoint.

@arogges .well-know/openid-configuration endpoint is OpenId compliant and have different pourposes. So for this case isn't the best option.
Could you try AspNetCore.Diagnostics.HealthChecks. It publish a healthcheck endpoint, which is one of the best alternative for your needs.


Property 'presentable' does not exist on type 'SchemaField'

Sorry, should we add presentable to SchemaField ?

Yes, I forgot to add it. I'll update it with the next release (the related Dart DTO will also have to be changed).
As a temp workaround for now if you need to access it or set it in a TS environment you can try using the brackets-string notation, aka. field["presentable"] = true.


MDEXP-602 - Export shared MARC instances

Purpose
MDEXP-602 - Export shared MARC instances
Approach
How does this change fulfill the purpose?
TODOS and Open Questions

[ ] Use GitHub checklists. When solved, check the box and explain the answer.

Learning
Describe the research stage. Add links to blog posts, patterns, libraries or addons used to solve this problem.


Implement reader software to Batch Job definition lookup

In order to support multiple readers and versions of readers, implement a mechanism of using the software and its version to determine which job definition (and thus which Docker image) is appropriate.
Could potentially be implemented as:

A lambda function which reads some configuration file potentially partially derived from the job definitions defined in the Batch Cloudformation deployment stage
SSM parameters (less flexible)

While this is still desirable in the medium term (i.e. to provide the user with options to use different version of BioFormats, etc), the immediate need of synchronising the BioFormats version used in scan and extract can be solved instead by setting the versions in stone when the scan job is launched and carried forward as a parameter to the extract job executions.


Merge ddcloud_server_nic into ddcloud_server

Due to a limitation arising from differences between the CloudControl model and the Terraform life-cycle model, additional network adapters in a server are currently modelled as separate resources (see previous discussion relating to this change in #33 and #52). This is inelegant and unintuitive.
Now, however, I've worked out a way that we can do better :)
We now have the ability to match up network adapters by index (ddcloud_server.network_adapter is a List instead of a Set).
So for the simplest (default) case, you'd have something like:
resource "ddcloud_server" "server1" {
  name = "server1"

  # ...

  # Equivalent to primary_adapter_ipv4 = "<IP_ADDRESS>"
  #
  # This works because the default value for the index property is 0 (i.e. the primary adapter).
  network_adapter {
    ipv4 = "<IP_ADDRESS>"
  }
}

Or with multiple adapters:
resource "ddcloud_server" "server1" {
  name = "server1"

  # ...

  # Equivalent to primary_adapter_ipv4 = "<IP_ADDRESS>"
  network_adapter {
    ipv4  = "<IP_ADDRESS>"
  }

  # Equivalent to ddcloud_server_nic
  network_adapter {
    vlan  = "${var.vlan_id}"
    type  = "VMXNET3"
  }

  # Equivalent to ddcloud_server_nic
  network_adapter {
    ipv4  = "<IP_ADDRESS>"
    type  = "E1000"
  }
}

Note that the adapters must appear in the same order that they appear in CloudControl (with the primary network adapter being first, at index 0).
When we create each network adapter, we can store a calculated id property on it representing the adapter Id from CloudControl. This Id allows us to match up the adapter state with information returned by CloudControl.
CC: @johnamurray @kumarappanc @wninobla - can I get some input from you guys?

Can I suggest that the additional NICs to be included (as an "additionalNic" parameter in CloudControl Server APIs) during server deployment instead of adding them after server deployment?
The reason is because it will save significant effort in configuring the NIC adapters at the OS level. I know it can be automated using CI tools but I would still prefer to keep it simple by deploying the server with additional NICs parameters included.

Agreed - that's why I'm merging them back in :)

This feature is sufficiently mature to be merged back into the v1.2 branch.

Hey after the disks issues are solved, I have moved on to test the network adapters. Currently have two issues I think needs to be solved for now (before Picard release).

Unable to specify index for "network_adapters"
When updating additional NIC, it will re-deploy the server. (which should only remove the current NIC and add back the NIC with the updated configuration) For "type", I think we can leave it for now as when the Picard release rolls out, it will support updating of "type" (e.g. E1000 or VMXNET3)

Hmm.. Picard also supports exchanging NIC VLANs.. So I guess we might need to wait a few days for Picard to roll-out before working on this issue.

Yeah, index is no longer a valid property - instead, the adapter's index is derived from its position in the configuration.

As for switching VLANs we can support that in a subsequent release :)

I'll update the docs for index.

Updating a network adapter shouldn't force a new resource though - that sounds like a bug. I'll have a look into it.
On 2 Dec. 2016, at 2:02 am, Ming Sheng <notifications<EMAIL_ADDRESS>wrote:
Hey after the disks issues are solved, I have moved on to test the network adapters. Currently have two issues I think needs to be solved for now (before Picard release).

Unable to specify index for "network_adapters"
When updating additional NIC, it will re-deploy the server. (which should only remove the current NIC and add back the NIC with the updated configuration) For "type", I think we can leave it for now as when the Picard release rolls out, it will support updating of "type" (e.g. E1000 or VMXNET3)

You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/56#issuecomment-264195541, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezA1vnUSl9yT1D_b4p5SkA4BKtXhHks5rDuF2gaJpZM4K8LLW.
itevomcid

Actually, the docs have already been updated (RE: index).

@mingsheng36 - I don't think that's a bug; changing the VLAN or adapter type will force re-deployment. This is by design because the CloudControl API doesn't support that either.
Later, when we do use the newer CloudControl APIs we can change this.

Ok, @mingsheng36 and @wninobla - turns out updating the network adapters is much much harder than I initially expected it to be. The problem is that if you have 3 adapters, and then remove the second adapter, Terraform just chops off the last adapter from the list it presents to us as the current state. I'm going to have to play around with this for a while, but I suspect the behaviour is going to have to be:

You can change the IP address on a network adapter, and that's all that will happen
You can add a network adapter, and that's all that will happen
If you remove any network adapter, then all network adapters will be removed and re-created. It's kinda ugly, but I honestly can't see any other way to deal with the problem given the limitations imposed by Terraform's state model.

Before I go ahead with this, though, I wanted to see what you guys thought. Is removing and re-adding all network adapters when one is removed an acceptable trade-off for keeping state consistent? If not, we may have to rethink merging the NICs into the server because otherwise there's no simple way to deal with them.

Hmm. I initially thought that network_adapters should behave like disks and also suppose to have the same logic as disk? e.g. When you remove a disks, it will remove any disk in that position?

To answer your question i think removing and re-adding a network_adapter will cause alot of issue in the OS. Like for example RHEL, they will increment the network_adapter count (eth0 --> eth1) and OS admin will have to re-configure the NIC again.

Disks are identified by SCSI Unit ID, but yes it's a problem. So as I see it, we have a couple of choices:

Prevent removal of network adapters
I reckon this is pretty much a non-starter
Document the limitation, indicating that you will get undefined behaviour if you remove any adapter(s) that aren't the last (N) adapter(s). Document what is and isn't supported. A bit ugly, I reckon.

If you have A, B, C, and D, then you can safely remove C and D (or just D) but not B (A is the primary adapter and cannot be removed).
You can add adapters whenever you want.
You can change the IP address on an adapter whenever you want.

Move network adapters back to their own resource type (ddcloud_server_nic). Slightly awkward and unintuitive, but at least it's reliable.

Note how they deal with this for the AWS provider:
https://www.terraform.io/docs/providers/aws/r/instance.html#block-devices
Making any changes to the disks means the EC2 instance will be destroyed and recreated.

And Azure ARM provider doesn't support update of VMs at all (only destroy and recreate).

After examining the docs and code for most of the other Terraform providers written by Hashicorp, it's clear that none of them really support messing around with disks and network adapters to this degree. I'm guessing it's because Terraform's state data model can't really cope with these sorts of changes properly. So perhaps we're trying to be too clever here by half.
So yes - it's looking like option 2 or 3 is the only way to go here. I can live with 2 if the documentation makes it clear what is and isn't possible (i.e. you can change the order of the network_adapter entries, but if you remove one from the middle then all bets are off). We can probably even raise an error when we discover that an adapter appears to have gone missing from the middle (explaining that it's not a supported scenario).
Either that, or back to ddcloud_server_nic. Thoughts?
CC: @kumarappanc @johnamurray @alexbacchin - any opinion on this guys?

Personally, due to the OS limitations as well as the initial design goals of the DD cloud provider with Terra form, I'd say this is considered a change dual to say patching a box.  So, you either treat it with a different method like Chef or you destroy and recreate the asset.  If we look at it as immutable assets we should as ourselves which have a are considered minor vs which ones require destroying the VM since its supposed to be throw away.  If we decide to think of this as a true infrastructure tool and treat the VMs as actual physical servers that we maintain then I'd say we need to do what you all were talking about.  Makes for a bigger headache for Adam in the end though... 😀
Just my two cents worth....  I am open to anyone disagreeing... 😋
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Friday, December 2, 2016 8:20 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Merge ddcloud_server_nic into ddcloud_server (#56)
After examining the docs and code for most of the other Terraform providers written by Hashicorp, it's clear that none of them really support messing around with disks and network adapters to this degree. I'm guessing it's because Terraform's state data model can't really cope with these sorts of changes properly. So perhaps we're trying to be too clever here by half.
So yes - it's looking like option 2 or 3 is the only way to go here. I can live with 2 if the documentation makes it clear what is and isn't possible (i.e. you can change the order of the network_adapter entries, but if you remove one from the middle then all bets are off). We can probably even raise an error when we discover that an adapter appears to have gone missing from the middle (explaining that it's not a supported scenario).
Either that, or back to ddcloud_server_nic. Thoughts?
CC: @kumarappanchttps://github.com/kumarappanc @johnamurrayhttps://github.com/johnamurray @alexbacchinhttps://github.com/alexbacchin - any opinion on this guys?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/56#issuecomment-264615500, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v8VQ59AdHoIgslAL4Z3Fz2-LGw2jks5rEO4GgaJpZM4K8LLW.
itevomcid

I agree with you @wninobla, and not just because it suits me ;-)
I think we've hit a limitation of what Terraform itself is capable of, and I don't see it as being all that worthwhile to change. To be honest, I'm probably OK with marking the entire network_adapter collection as ForceNew: true so that any change to network adapters will result in the server being destroyed and recreated. If anyone has a genuine scenario where they might change this, then I'm happy to discuss but otherwise this is my preferred solution.

I beg to differ. Understand that it is the limitation of terraform and it was not designed to handle this kind of change, but I hope we would not go with the bottom-up approach towards the design of this provider.
Nonetheless, if going with option 3 allows us to update and delete NIC without causing any deletion to unnecessary items from existing server, I would gladly vote for it as it can achieve that outcome :

Move network adapters back to their own resource type (ddcloud_server_nic). Slightly awkward and unintuitive, but at least it's reliable.

I have not used terraform to deploy any instance on AWS yet, hence I will not be able to tell how are they doing this but from what I know, our MCP design is fundamentally different from theirs and I think if there is something that they can't support and we can, it would be really be awesome to have something for us to boost about when introducing terraform to internal teams or clients.
However, if it is requires too much effort to go with option 3, then I am OK with supporting only the removal of the last network_adapter.

No, I'm open to option 3 as well - @kumarappanc already did this work a while back (ddcloud_server_nic), and it was only after others asked if we could merge it into ddcloud_server so they didn't have to track 2 different resources for the server's network adapters that we did this work.
The main advantage of having all adapters in ddcloud_server is that we can deploy the server with all of them connected. Otherwise we (potentially) have to shut down the server and restart it once for each network adapter we're changing.

I imagine that different types of consumer will have different use cases, and therefore different priorities.
We could make the primary network adapter part of ddcloud_server and then have an ddcloud_network_adapter instance for each additional network adapter in the server.
This will allow all network adapters to be managed separately (as @kumarappanc did in the first place) but it will also make additional network adapters slower to add / modify / remove (and you won't be able to deploy a server with anything but the primary adapter; others will have to be added after deploy).

I have not used terraform to deploy any instance on AWS yet, hence I will not be able to tell how are they doing this but from what I know, our MCP design is fundamentally different from theirs

BTW, it's not just AWS - its also Azure (both SRM and ARM), GCE, Digital Ocean, etc. This seems to be the state of the art for now.

No, I'm open to option 3 as well - @kumarappanc already did this work a while back (ddcloud_server_nic), and it was only after others asked if we could merge it into ddcloud_server so they didn't have to track 2 different resources for the server's network adapters that we did this work.

If we have to sacrifice the deploying of of additional network_adapters during deployment VS supporting CRUD of network adapter, I would choose the later. Having longer deployment time (a few mins) is not a concern in my opinion, since it is automated and the difference is not that huge. My main concern is the need to manually configure the network_adapters at the OS, however I think this can be solved using CM tools like Ansible, just that it requires more effort (reasonable) for the users to build up the process which I think is acceptable given the situation that we are facing now.
My vote is still option 3. :+1:

Noted :)
On 3 Dec. 2016, at 4:38 pm, Ming Sheng <notifications<EMAIL_ADDRESS>wrote:
No, I'm open to option 3 as well - @kumarappanchttps://github.com/kumarappanc already did this work a while back (ddcloud_server_nic), and it was only after others asked if we could merge it into ddcloud_server so they didn't have to track 2 different resources for the server's network adapters that we did this work.
If we have to sacrifice the deploying of of additional network_adapters during deployment VS supporting CRUD of network adapter, I would choose the later. Having longer deployment time (a few mins) is not a concern in my opinion, since it is automated and the difference is not that huge. My main concern is the need to manually configure the network_adapters at the OS, however I think this can be solved using CM tools like Ansible, just that it requires more effort (reasonable) for the users to build up the process which I think is acceptable given the situation that we are facing now.
My vote is still option 3. ?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/56#issuecomment-264618658, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezLx7IUToxznEyRaJwKMITWO-pC-wks5rEQBlgaJpZM4K8LLW.
itevomcid

BTW it's more than a few minutes - if the server is running before you start it could be 30 mins or more if you have a lot of NICs to add or change.
On 3 Dec. 2016, at 4:38 pm, Ming Sheng <notifications<EMAIL_ADDRESS>wrote:
No, I'm open to option 3 as well - @kumarappanchttps://github.com/kumarappanc already did this work a while back (ddcloud_server_nic), and it was only after others asked if we could merge it into ddcloud_server so they didn't have to track 2 different resources for the server's network adapters that we did this work.
If we have to sacrifice the deploying of of additional network_adapters during deployment VS supporting CRUD of network adapter, I would choose the later. Having longer deployment time (a few mins) is not a concern in my opinion, since it is automated and the difference is not that huge. My main concern is the need to manually configure the network_adapters at the OS, however I think this can be solved using CM tools like Ansible, just that it requires more effort (reasonable) for the users to build up the process which I think is acceptable given the situation that we are facing now.
My vote is still option 3. ?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/56#issuecomment-264618658, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezLx7IUToxznEyRaJwKMITWO-pC-wks5rEQBlgaJpZM4K8LLW.
itevomcid

BTW, it's not just AWS - its also Azure (both SRM and ARM), GCE, Digital Ocean, etc. This seems to be the state of the art for now.

I see. Pardon me as I might be wrong here but re-deploying a whole server because of network configs does not make any sense to me for MCP as you know we do not have something like EBS.. if our server is delete, there goes our disks and data too..

BTW it's more than a few minutes - if the server is running before you start it could be 30 mins or more if you have a lot of NICs to add or change.

So far from my own experience, the most number of NICs I have added to a server is 3.. And I think adding a NIC is quite fast? Might be 3mins per NIC and 30minutes max like what you mentioned, but I think this is a rare and extreme case as too much NIC will choke up the server resources

Yeah - that's a fair point. I can see for some scenarios that's a non-starter.
On 3 Dec. 2016, at 4:44 pm, Ming Sheng <notifications<EMAIL_ADDRESS>wrote:
BTW, it's not just AWS - its also Azure (both SRM and ARM), GCE, Digital Ocean, etc. This seems to be the state of the art for now.
I see. Pardon me as I might be wrong here but re-deploying a whole server because of network configs does not make any sense to me for MCP as you know we do not have something like EBS.. if our server is delete, there goes our disks and data too..

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/56#issuecomment-264618933, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezHjJBoYSRVUSE7Br-PJspVss31IVks5rEQGigaJpZM4K8LLW.
itevomcid

True.
On 3 Dec. 2016, at 4:51 pm, Ming Sheng <notifications<EMAIL_ADDRESS>wrote:
BTW it's more than a few minutes - if the server is running before you start it could be 30 mins or more if you have a lot of NICs to add or change.
So far from my own experience, the most number of NICs I have added to a server is 3.. And I think adding a NIC is quite fast? Might be 3mins per NIC and 30minutes max like what you mentioned, but I think this is a rare and extreme case as too much NIC will choke up the server resources

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/56#issuecomment-264619240, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezLSzlaAEBvHPvq58cO04oAdEO9Bgks5rEQNbgaJpZM4K8LLW.
itevomcid

@tintoy Hope my comments helps you with the decision :) and BTW, really appreciate the effort to improve this!

For sure - great to get feedback on how it's used in the real world :)
On 3 Dec. 2016, at 5:57 pm, Ming Sheng <notifications<EMAIL_ADDRESS>wrote:
@tintoyhttps://github.com/tintoy Hope my comments helps you with the decision :) and BTW, really appreciate the effort to improve this!

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/56#issuecomment-264622109, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezIiRn0h-apcc5DzX9dx_36tJo7C2ks5rERK8gaJpZM4K8LLW.
itevomcid

BTW, there is a 4th option - support both (but not in combination).

You can always modify (but never add / remove) the primary network adapter on a ddcloud_server (exposed as primary_network_adapter).
You can specify additional NICs as additional_network_adapter on ddcloud_server but then they are immutable after deployment.
Otherwise, you can specify the primary adapter on the ddcloud_server, and additional NICs via ddcloud_network_adapter (in which case they can be changed).

I don't know about others, but my opinion is to standardize with option 3 only.

It will save effort on on the codes and maintainability
It is also makes it less complex to understand for users
Also, might want to wait till Picard release (API v2.4) before working on this? As there might be changes that could be included in terraform.

What do you think @tintoy ?

Already using it for some things - that's why MAC address and adapter type are now computed from current state :)
No VLAN switch for now though...
On 3 Dec. 2016, at 7:02 pm, Ming Sheng <notifications<EMAIL_ADDRESS>wrote:
I don't know about others, but my opinion is to standardize with option 3 only.

It will save effort on on the codes and maintainability
It is also makes it less complex to understand for users
Also, might want to wait till Picard release (API v2.4) before working on this? As there might be changes that could be included in terraform.

What do you think @tintoyhttps://github.com/tintoy ?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/56#issuecomment-264624633, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezGhn5v0P9bZfu5DqMltpTuSKUC0vks5rESIYgaJpZM4K8LLW.
itevomcid

FWIW, AWS and other providers also support the dual-use pattern. But I'll see what's involved - if we can share code between then it might be ok.

Already using it for some things - that's why MAC address and adapter type are now computed from current state :)

Thats fast! 💯

Ok @mingsheng36 and @wninobla. After seeing the various use-cases people have, I've decided to support both :)
Next build will have it.

Now available in v1.2-preview5.

Nice - and I barely said anything... =)  I really need to test some of these things out now.  This coming week is for that.  =)
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Adam Friedman<EMAIL_ADDRESS>Sent: Saturday, December 3, 2016 3:55 PM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Mention
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Merge ddcloud_server_nic into ddcloud_server (#56)
Now available in v1.2-preview5https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/releases/tag/v1.2-preview5.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/56#issuecomment-264674027, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v3zRNonb3XTC6wKUEHQ2Qf6mZADsks5rEgGAgaJpZM4K8LLW.
itevomcid

@tintoy Seems like adapter "tyue" is missed out for both schema?
https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/blob/development/v1.2/docs/resource_types/server.md
https://github.com/DimensionDataResearch/dd-cloud-compute-terraform/blob/development/v1.2/docs/resource_types/network_adapter.md

Sorry, I'm not sure what you mean - the pages you link do show the adapter type:

Are you on the v1.2 or v1.0 branch? This is v1.2-only.

I am on 1.2 branch. My apologies for not going through all the document, was looking at the example actually. :(

Thanks!

Verified (manually and via automated acceptance tests) in v1.2.0-beta1.


export IPResponse interface

@CoolCyberBrain thanks for this and apologies for the massive delay. This module should be usable from Node so fetch can't be assumed to be in the environment. Are you able to update the PR?

@CoolCyberBrain actually I've just merged #28 which introduces ky instead of request. If you could rebase off what's in master now that would be awesome.

ipLocation.LocationData will be exported in v7.


Can't use in swift 5 Xcode 10.3

New Issue Checklist

[ ] I have read and understood the CONTRIBUTING guide
[ ] I have read the Documentation or CocoaDocs
[ ] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
e.g. ios / osx / tvos / watchos

Platform Version
e.g. 8.0

CocoaLumberjack Version
~ 3.5.3

Integration Method
manually

Xcode Version
Xcode 10.3

Repro rate
e.g. all the time (100%) / sometimes x% / only once

Demo project link
e.g. link to a demo project that highlights the issue

Issue Description and Steps
Running DDLogDebug("测试一下"); does not print anything.

@changanli Could you please fill out the issue template and provide a little more details on what is not working?
Also, there is no Swift 5.2 yet. There's Swift 5.0 (which is the current stable version) and there's Swift 5.1 (which is currently in beta and available with Xcode 10.4 beta). Since we don't officially support beta's, you might see errors there.
Unofficially, however, I can tell you that CocoaLumberjack should currently work with Swift 5.1. 😉

can't not print any thing!!! I don't know why!!!

@changanli This does not answer much of what I asked.
Again:

What Swift version are you referring to (there is no Swift 5.2)?
What version of CocoaLumberjack are you using?
What integration method are you using (CocoaPods, Carthage, manual)?
Have you tried to reproduce this in a small sample project?

A few more that could help narrow this down:

What loggers are you using?
What's the level of the messages you're trying to log?
Have you changed the global log level (and if so, to what)?

Xcode 10.3 swift_version: Swift 5
maybe 3.5.3, i download today
integration: manual
DDLogDebug("测试一下");

@changanli Thanks. I've updated the issue description based on your reply.
DDLogDebug is the second most verbose way to print a message. It should not be filtered by default, but could you please test logging your message using DDLogError? By default, DDLogError logs synchronously and is rarely filtered.
If that doesn't work, then I still need to know what loggers you're using.

it dosen't work。
DispatchQueue.main.asyncAfter(deadline: .now() + 0.2) {
DDLogError("测试一下")
}

Demo:  https://github.com/changanli/CocoaLumberjackTest
Xcode 10 swift 5 , you can download this,Thank you!

@changanli I've had a look at your project. You never add any loggers and thus no messages will be logged. Please refer to the "How to get started" section in our README to see an example on how to add loggers.
The DDLogXYZ functions just pass the message to a DDLog instance (if it passes the global log level). DDLog will then dispatch the message to all added loggers. In your case no logger was ever added and therefor the message(s) will simply be dropped.


Update docs/setup/production-environment/turnkey/gce.md to follow v1.18 of the original text

I updated the content/ja/docs/setup/production-environment/turnkey/gce.md to follow v1.18 of the original (English) text.
The following link is the differences between v1.17 and v1.18:
https://gist.github.com/inductor/c5961124a77fff385810347dba45a651
This PR fixes this issue:
#26519

I signed it

/approve

/assign
/cc @kakts @makocchi-git @bells17

/lgtm


html

I was wondering whether there is a functionality to not wipe all the html in the extraction process, for example, for the 10-ks it would be nice to know what is for example tables, lists, headings etc, this would give html tag information and probably some info about hierarchical relationships
There probably is also some benefit in getting the row_id, if ever it is used in some vectorised database, which most of the use cases is for, one would like to point back to where one got the text in the filing.
It would be awesome to get more hierarchy somehow out of the dataset ala these guys https://github.com/alphanome-ai/sec-parser

There probably is also some benefit in getting the row_id, if ever it is used in some vectorised database, which most of the use cases is for, one would like to point back to where one got the text in the filing.

Hi @firmai, I'll be implementing table parsing in a future advanced parser.
It's a bit frustrating because I've known and prototyped how to extracted nested hierarchy + tables from html, pdf, and txt filings since September, but I can't justify the time expenditure (~ 2 months) without revenue/funding source.

Hi @firmai, I'll be implementing table parsing in a future advanced parser.
It's a bit frustrating because I've known and prototyped how to extracted nested hierarchy + tables from html, pdf, and txt filings since September, but I can't justify the time expenditure (~ 2 months) without revenue/funding source.

Why don't you call out for sponsorship on Linkedin, I will share it as far as I can, and can also contribute by January? Also if you need some help on this, will be happy to open an MS teams to colaborate, think this would be a really good addition to your open source package.

Hey @firmai - that's a great suggestion! Let me think about it and get back to you.


test: restructure json integration tests

Description
Simplify integration test structure and add some more assertions
Test Steps

Checklist:

[x] I have tested my changes. No regression in existing tests.
[x] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Pending #74


Feature Request - Device Disable

Good Day
Would be nice to add Device Enable / Disable feature:
Device Status: Disabled. (Still get location data and save to DB)
Can not select in reporting until enabled. (Accounting Platforms Integration)
Rest-Api to be able to modify between enabled / disabled. (Accounting Platforms Integration)
Could you add something like this?
Thank You
Albertus Geyser

Could you explain the purpose of such modification?
According to current traccar roles implementation, who will be able switch enable/disable devices?

Good Day
The admin will be able to disable / enable devices.
The use is to link accounting to Traccar for instance if a user has 5 trackers and he pays per month per tracker then when a certain tracker is not paid for then the accounting software will disable unpaid tracker selection in reporting . . . drop downs, but positions will still be recorded in database. If user pay for the tracker then device will again be available in drop downs to be selected to see where tracker is located, or see history of where tracker was when were unpaid.
I think the main idea is to remove device selection from reporting and not see where device is currently when disabled.
Hope this could be done.
Thank You
Albertus Geyser

But should device still be visible in list? And should user be able modify(except enabling)/delete device?
I think "to store or not to store" data from disabled device should be configurable. I can imagine use cases when users will wait that data from disabled device is not stored in DB.

I think device should not be visible. The easiest way to implement this is to exclude disabled devices from user list if user is not admin.

It is easiest, but not the best I think...

Suddenly disappeared device is not very good user experience
I believe one "not payed" device usually mean it is not needed and user can delete it. I'm sure such devices will live on server until admin remember to cleanup.

I suggest to block reports and positions (last) for such devices and users/managers can't enable them.

Agree as long as the implementation is not overcomplicated.
Also, we need to handle situation when user tries to get report for multiple devices some of which are disabled and some are not.
Maybe the right solution is to basically return zero data for disabled devices. It will look a new device with no data at all. Solves report issue.
We can also highlight it in device list with grey background or something like that.

Good Day
Thank you for feedback and support with this.
I think if implementing we should look at it as a cable company where if you do not pay because you forgot or do not have money now then they wont delete your device details. . . but will enable device to enable you to watch TV again. I think people can deliberately not pay, but certain people do forget about it and we should give then details (reporting) if device enabled again.
Again Thank You all for this.
Albertus Geyser

We are not considering removal of the device. Device will be there and admin can always re-enable it. We are basically discussing what the user experience should be with disabled devices.

Great . . .
Thank You very much.
Albertus Geyser

Where is this on the documentation? how to disable via the API?

This is not even released yet.

this is really a useful feature... ETA for the release?

It will be release with next official version of Traccar. We don't have a date yet.


haskellPackages: update stackage and hackage

This Merge
This PR is the regular merge of the haskell-updates branch into master.
This branch is being continually built and tested by hydra at https://hydra.nixos.org/jobset/nixpkgs/haskell-updates. You may be able to find an up-to-date Hydra build report at cdepillabout/nix-haskell-updates-status.
We roughly aim to merge these haskell-updates PRs at least once every two weeks. See the @NixOS/haskell team calendar for who is currently in charge of this branch.
haskellPackages Workflow Summary
Our workflow is currently described in pkgs/development/haskell-modules/HACKING.md.
The short version is this:

We regularly update the Stackage and Hackage pins on haskell-updates (normally at the beginning of a merge window).
The community fixes builds of Haskell packages on that branch.
We aim at at least one merge of haskell-updates into master every two weeks.
We only do the merge if the mergeable job is succeeding on hydra.
If a maintained package is still broken at the time of merge, we will only merge if the maintainer has been pinged 7 days in advance. (If you care about a Haskell package, become a maintainer!)

More information about Haskell packages in nixpkgs can be found in the nixpkgs manual.

This is the follow-up to #300455. Come to #haskell:nixos.org if you have any questions.

Apparently, some of these changes are now blocking nixpkgs-unstable:
https://hydra.nixos.org/build/256453077#tabs-constituents

@vcunat Seems like this is a flaky test failure as I can't reproduce it anymore. I've restarted the offending jobs (at least in trunk-combined), hopefully that's going to be that.
Sorry we did not catch this – we've stopped monitoring darwin closely a while ago as we lack the maintainers for that platform. I'll figure something out that at least the channel blocking jobs get more eyes.

Oh, OK, just flaky.  Certainly not a significant problem, though ideally we'd skip flaky test if it's not difficult.


Implement asymmetric encrypt/decrypt in the PKCS#11 provider

Summary
Implement the asymmetric (RSA) encryption/decryption primitives in the PKCS#11 provider.
Details
Equivalent to this request to implement them in the TPM provider: https://github.com/parallaxsecond/parsec/issues/217
Definition of Done
Integration tests of asymmetric encrypt/decrypt using RSA key pair with SoftHSM.

To make the added asymmetric encryption/decryption be used by the dbus-parsec project, we would have to also support RsaOaep as an asymmetric encryption algorithm. See where it is used in dbus-parsec.

Do we not support that? I mean, we don't support asymmetric encryption for now with PKCS11, but when we add it we can add support for all of the primitives.


correctly initialize scratch descriptor for gemm autotuning

Fixes #25761. Scratch should be initialized with the same descriptor as output_matrix, and not assume that output_matrix is column major.

@ngimel please sign CLA

I signed it!

Thanks!
I verified this also fixes JAX issue https://github.com/google/jax/issues/304 .


Should I remove system node?

Hi,
In the documentation is says "You can (but should not?) keep your previous "system" node install". Could you please elaborate on this a bit and let me know how I can safely remove the system node install?

You're welcome to keep or remove it.
How to remove it depends on how you installed it.

I downloaded the 8.11.3 LTS from the node website

In that case you’ll need to manually remove the directories if you want to uninstall it; but it’s perfectly fine to keep that around.

No I think it is not perfectly fine to keep that around, because I met a problem, the global modules of system would interfere in node of nvm. Like following.
I had some modules in the global of system node:
GQSM@Applede-MacBook-Pro ~ % nvm current
system
GQSM@Applede-MacBook-Pro ~ % npm ls -g --depth=0
/usr/local/lib
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
Then I change to node of nvm:
GQSM@Applede-MacBook-Pro ~ % nvm use v12.18.3
Now using node v12.18.3 (npm v6.14.6)
GQSM@Applede-MacBook-Pro ~ % npm ls -g --depth=0
/Users/GQSM/.nvm/versions/node/v12.18.3/lib
└──<EMAIL_ADDRESS>
GQSM@Applede-MacBook-Pro ~ % webpack-cli --version
3.1.0

When I change to node of nvm, I still can access modules of system node. My version of nvm is v0.35.3, I don't know how to solve this problemm. But I think the problem is with node of system?

@ms314006 thats a feature, not a bug. You can either uninstall those system global modules (or your entire system node), you can remove that directory from your PATH, or you can install the same global modules in your nvm-managed node.
The best alternative is to avoid having global modules installed at all :-) install things locally and/or use npx.

@ljharb I am really grateful your reply so fast and clearly! I will try to uninstall entire system node, really thank for your comments!

How do I find out where the system node is installed? If I check /usr/local/bin then node does not point to anywhere...?

@nerdess which node

@ljharb the yellow one

@nerdess no, the literal command you run to find out where a binary is located is called which. Run which node on your terminal.

You could also use for example nvm alias default v18.17.1 to set default version, that would also stop falling back to the system version when starting the terminal.


Post to Discord when CI fails

This turns out to be a million times easier than sending emails. I don't
love it, but it's a whole lot better than the current situation.
The result currently looks like this (the bot avatar and name as well as
the channel it posts to can be configured on the Discord side):

Another option would be creating an issue on each failure. I like that
a lot better for tracking purposes, but I don't think it has the same
visibility and there's still no way to create rotations on GitHub, so
we couldn't auto-assign the issue easily. It would also be quite noisy.
We could always post to the same issue, but then the issue isn't that
useful for tracking.
My intent is to start this out in the #github channel and then graduate
it to the #builds channel if everything seems to be working. For now I
also went with an action that does all the Discord message formatting
for you. If we wanted more customization, we could switch to a
different one (there are quite a few). There's someone in the issues
for this action complaining that the release is unauditable:
https://github.com/sarisia/actions-status-discord/issues/364, but the
author shows how you can get the audit trail and I'm not too worried.
I guess if this is considered adequate then:
Fixes https://github.com/iree-org/iree/issues/9857
Tested: turned on runs on pushes to another branch and pushed to it.

This is great. Thanks.

Well I'm not sure it's great, but it's something :-P


is this repo dead?

hi @umhan35 I'd like to ask if you plan on maintaining the repo, or if you're looking for some maintainers. There are currently several issues that make it not possible to use the package with newest RN. :/ The PRs are already there but not being merged/reviewed.
thanks :)

https://github.com/localz/react-native-searchbar is a very good alternative, and supports Android too!

@umhan35 can you please comment on this? Thanks :)

@vonovak, more flexibility, actively maintained, try it out and see for yourself. :)

Hmm, I actually thought based on the dead homepage and lack of Github activity that it was possible @umhan35 may have passed away - it does happen occasionally. However, @umhan35's Facebook account seems to have been active in October, so it's possible he's just decided to step aside from open source for a while. Perfectly acceptable (although a public announcement would have been appreciated), but it may be time for the community to take over the maintenance burden, fork repos and upload alternate NPM modules.

Since @umhan35 is not responding, I have reached out to npm to claim the package name. If that goes through, the community may continue the development in a fork and publish under the same npm name. If anyone is interested in being a maintainer, let me know.

👎 I'm not passing away. I was still working for your guys this Jan for free. I'm busy with my PhD now. I'll try to contact @iRoachie if he'd like to be a collaborator of this repo and I'll add him to npm too.


Error running model_target.py

Hello,
I am trying to recreate the results of subtask B, 2 way classification of the tweets, and I have taken the following steps:
change the TASK = 'BD' in model_target.py
When I try running model_target.py, I am through until the model being trained, and then I get an error
TypeError: Using a tf.Tensor as a Python bool is not allowed. Use if t is not None: instead of if t: to test if a tensor is defined, and use TensorFlow ops such as tf.cond to execute subgraphs conditioned on the value of a tensor.
I have tried installing an older version of Tensorflow, but still get the same result.
Here is the full error:---------
TypeError                                 Traceback (most recent call last)
 in ()
101                       attention="context",
102                       clipnorm=.1,
--> 103                       classes=len(classes))
104
105 plot(nn_model, show_layer_names=True, show_shapes=True, to_file="model_task4_sub{}.png".format(TASK))
/models/neural/keras_models.py in target_RNN(wv, tweet_max_length, aspect_max_length, classes, **kwargs)
175     h_aspects = shared_RNN(aspects_emb)
176     h_aspects = Dropout(drop_target_rnn)(h_aspects)
--> 177     h_aspects = MeanOverTime()(h_aspects)
178     h_aspects = RepeatVector(tweet_max_length)(h_aspects)
179
~/anaconda2/envs/py35/lib/python3.5/site-packages/keras/engine/topology.py in call(self, x, mask)
570         if inbound_layers:
571             # This will call layer.build() if necessary.
--> 572             self.add_inbound_node(inbound_layers, node_indices, tensor_indices)
573             # Outputs were already computed when calling self.add_inbound_node.
574             outputs = self.inbound_nodes[-1].output_tensors
~/anaconda2/envs/py35/lib/python3.5/site-packages/keras/engine/topology.py in add_inbound_node(self, inbound_layers, node_indices, tensor_indices)
633         # creating the node automatically updates self.inbound_nodes
634         # as well as outbound_nodes on inbound layers.
--> 635         Node.create_node(self, inbound_layers, node_indices, tensor_indices)
636
637     def get_output_shape_for(self, input_shape):
~/anaconda2/envs/py35/lib/python3.5/site-packages/keras/engine/topology.py in create_node(cls, outbound_layer, inbound_layers, node_indices, tensor_indices)
164
165         if len(input_tensors) == 1:
--> 166             output_tensors = to_list(outbound_layer.call(input_tensors[0], mask=input_masks[0]))
167             output_masks = to_list(outbound_layer.compute_mask(input_tensors[0], input_masks[0]))
168             # TODO: try to auto-infer shape
~/anaconda2/envs/py35/lib/python3.5/site-packages/kutilities/layers.py in call(self, x, mask)
21         if mask is not None:
22             mask = K.cast(mask, 'float32')
---> 23             if not K.any(mask):
24                 return K.mean(x, axis=1)
25             else:
~/anaconda2/envs/py35/lib/python3.5/site-packages/tensorflow/python/framework/ops.py in bool(self)
612       TypeError.
613     """
--> 614     raise TypeError("Using a tf.Tensor as a Python bool is not allowed. "
615                     "Use if t is not None: instead of if t: to test if a "
616                     "tensor is defined, and use TensorFlow ops such as "
TypeError: Using a tf.Tensor as a Python bool is not allowed. Use if t is not None: instead of if t: to test if a tensor is defined, and use TensorFlow ops such as tf.cond to execute subgraphs conditioned on the value of a tensor.

Did you solve this problem? I have the same problem also.

Nope :(

Please tell me what version of keras are you using and with what backend, in order to be able to reproduce the problem. I don't use Keras for my projects anymore, but i will look into it.

I use keras==1.2.2 with tensorflow backend.
Thanks for your reply.

Unfortunately, i have updated the repo in order to work with keras 2.x. There are some breaking changes from keras 1.X to 2.x. Also, this may be  a TF issue. Note that my initial model was implemented in keras 1.2.2 with theano backend and i never tested it with TF.
Anyway, tell me also what is your version of TF and i will try to see what causes the problem when i get the time.

I have tried TensorFlow versions 1.4 upto 1.7, but the problem persisted. Thank you for letting me know about Keras version, I also used 1.2.x for Keras with TensorFlow backend.

Hi guys, sorry for taking so long to update the repository. I just updated the codebase. It now works with the latest versions of Keras (2.2.0)  and Tensorflow (1.8.0). Please pull from the master and upgrade your packages from the requirements.
Please let me know if the updated code resolves your issues.


[DOCS] Documentation on wasmcloud-control-interface

Is your feature request related to a problem? Please describe.
At the moment, the crate wasmcloud-control-interface still has pretty barebones documentation. Similar to our recent improvements for the wasmcloud-host crate, we should write Rust documentation for the control interface.
Describe the solution you'd like
Public structs shown on https://docs.rs/wasmcloud-control-interface/0.3.0/wasmcloud_control_interface/ have annotations, it would be nice to be able to highlight the Client type in some way as that has all of the important methods for interacting with the control interface.
Describe alternatives you've considered
I've considered removing the control-interface entirely so we don't have to write documentation but I think that isn't the best path forward.

This has been taken care of, as the control interface crate Client type now has full documentation and even a couple of good examples.


move .fetch_data into FWF handler or the DataRow constructor maybe?

The syntax the library currently uses is a little gross, we always call .fetch_data when we create the data row. This might allow us to more easily implement configs if we just want to make stencil DataRows and not fill them with any data, but even then you would need to fetch_data to get the column formatting.
Basically, we just need something to help make this syntax nicer:
# Create the header record and get the data for it.
header_record = HeaderRecord()
header_record.fetch_data()

.fetch_data could return the instance, instead of the data row. We can still go grab the data if we want it, but having fetch_data return the instance allows us to move it all onto one line? We could also have a flag in the constructor for if we want to init_with_data and call fetch_data inside the constructor. This means it's more flexible and can conform to the different needs.


Missing feature: flattenFragments when calculating costs

I am missing a flattenFragments option when calculating costs(similar to the https://github.com/Escape-Technologies/graphql-armor/pull/436 that exists for maxDepth), and I am interested in contributing by adding this feature.
More context on a previous issue here: https://github.com/Escape-Technologies/graphql-armor/issues/474

I am missing a flattenFragments option when calculating costs(similar to the #436 that exists for maxDepth), and I am interested in contributing by adding this feature.
More context on a previous issue here: #474

Sure thing, unless it is breaking, let me know how I can assist !

My changes are here - https://github.com/Escape-Technologies/graphql-armor/pull/724

I have some trouble getting the mookme and commit messages to work, so I edited them directly on github. Maybe it is documented somewhere in the repo and I missed it, but couldn't get my "git commit" command to work

https://github.com/Escape-Technologies/graphql-armor/pull/724


Finished task

Added a function that user can duplicate a workflow in the dashboard with the same content.
And both the creation time and last modified time will be the time that the duplicate operation happens
#1207

@Rkyzzy Also, another minor comment, please update the PR description and title in a more describable manner.


Add io.openshift.tags label to Dockerfile.rhel9

Downstream patch synced upstream.

For future archaeologists - the labels added here are required to build with Konflux.

[test]


update: public rest-api

Full-node

how many transactions this node has already produced
how many this node has already produced
Current block vs node block
leasing on this node
Active features
node address
Version

Address

get balance of a list of address, with token or not
get token balance, get all tokens
get alias address or the reverse
get balance with confirmations
validate address

Transactions

transactions from one address
total number of transactions
unconfirmed transactions
transmit transaction
transactions by id

Block

block sequence, /header/full
last/first block, height/header/full
get block by id

Tokens

get all the tokens from the network
get all NFT from the network
distribution of a Token

Peers

get peers, number/full-data
connect to new peer
clear blacklist

it's a very good idea

RPC for notify events


How to install?

I didn't find any package for this on conan and vcpkg. I would be good to have the library on these package manager as C++23 is far away.

I've made a PR to add it to vcpkg: https://github.com/microsoft/vcpkg/pull/21820

It's merged now


[WIP] Gk/operatorapp

Closed in favor of https://github.com/vacuumlabs/ledgerjs-cardano-shelley/pull/103


gma500_gfx

Issue description
gma500_gfx is not working, without any output to dmesg.
I "confirmed" that gma500_gfx is the concerned module since this is the module used in both Arch Linux and Lubuntu. A thing to note is that this already runs before X is started.
Steps to reproduce
Boot up nixos according to technical details
Technical details
Sorry for not following the format, I've accidentally overwritten my system, and neither am I concerned if this will really get fixed.
Fresh install of nixos through a 16.03 LiveCD.
Notebook is a Toshiba NB520 with an Atom processor with Intel GMA 3650.

Same story here, on NixOS Stable, too.
gma500_gfx is not loaded on startup. Instead, i915 is. Blacklisting i915 and adding gma500_gfx to kernelModules does not help. i915 is still loaded, as is gma500_gfx, but it is not visible in lspci -vv, see:
lspci -vv on NixOS 16.03:
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Device 100b
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at dfc00000 (32-bit, non-prefetchable) [size=1M]
        Region 1: I/O ports at f100 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [b0] Vendor Specific Information: Len=07 <?>
        Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
                Address: 00000000  Data: 0000

The same command on Debian:
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Atom Processor D2xxx/N2xxx Integrated Graphics Controller
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 31
        Region 0: Memory at dfc00000 (32-bit, non-prefetchable) [size=1M]
        Region 1: I/O ports at f100 [size=8]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [b0] Vendor Specific Information: Len=07 <?>
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0f00c  Data: 41a2
        Kernel driver in use: gma500
        Kernel modules: gma500_gfx

Ah. I thought I was able to post the solution here. It doesn't support all
vias ootb, you need to recompile it.
On Aug 4, 2016 2:30 AM, "Michal Rus"<EMAIL_ADDRESS>wrote:

Same story here, on NixOS Stable, too.
gma500_gfx is not loaded on startup. Instead, i915 is. Blacklisting i915
and adding gma500_gfx to kernelModules does not help. i915 is still
loaded, as is gma500_gfx, but it is not visible in lspci -vv, see:
lspci -vv on NixOS 16.03:
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 100b
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 11
Region 0: Memory at dfc00000 (32-bit, non-prefetchable) [size=1M]
Region 1: I/O ports at f100 [size=8]
Expansion ROM at  [disabled]
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [b0] Vendor Specific Information: Len=07 <?>
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: 00000000  Data: 0000
The same command on Debian:
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Atom Processor D2xxx/N2xxx Integrated Graphics Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 31
Region 0: Memory at dfc00000 (32-bit, non-prefetchable) [size=1M]
Region 1: I/O ports at f100 [size=8]
[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [b0] Vendor Specific Information: Len=07 <?>
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0f00c  Data: 41a2
Kernel driver in use: gma500
Kernel modules: gma500_gfx
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/14727#issuecomment-237325725,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJMI5wNjE9tnngSB6DNxyR36jdnGSzKSks5qcN1mgaJpZM4IId1r
.

Yes, most probably. I’m now waiting for the kernel to recompile on my mom’s Intel™ Atom® running @ 1.6 GHz… Not really that convenient. :smiley:
Compare Debian:
m@debian% modinfo gma500_fgx
filename:       /lib/modules/3.16.0-4-amd64/kernel/drivers/gpu/drm/gma500/gma500_gfx.ko
license:        GPL
description:    DRM driver for the Intel GMA500, GMA600, GMA3600, GMA3650
author:         Alan Cox<EMAIL_ADDRESS>and others
alias:          pci:v00008086d00000BEFsv*sd*bc*sc*i*
alias:          pci:v00008086d00000BEEsv*sd*bc*sc*i*
alias:          pci:v00008086d00000BEDsv*sd*bc*sc*i*
alias:          pci:v00008086d00000BECsv*sd*bc*sc*i*
alias:          pci:v00008086d00000BEBsv*sd*bc*sc*i*
alias:          pci:v00008086d00000BEAsv*sd*bc*sc*i*
alias:          pci:v00008086d00000BE9sv*sd*bc*sc*i*
alias:          pci:v00008086d00000BE8sv*sd*bc*sc*i*
alias:          pci:v00008086d00000BE7sv*sd*bc*sc*i*
alias:          pci:v00008086d00000BE6sv*sd*bc*sc*i*
alias:          pci:v00008086d00000BE5sv*sd*bc*sc*i*
alias:          pci:v00008086d00000BE4sv*sd*bc*sc*i*
alias:          pci:v00008086d00000BE3sv*sd*bc*sc*i*
alias:          pci:v00008086d00000BE2sv*sd*bc*sc*i*
alias:          pci:v00008086d00000BE1sv*sd*bc*sc*i*
alias:          pci:v00008086d00000BE0sv*sd*bc*sc*i*
alias:          pci:v00008086d00004108sv*sd*bc*sc*i*
alias:          pci:v00008086d00004107sv*sd*bc*sc*i*
alias:          pci:v00008086d00004106sv*sd*bc*sc*i*
alias:          pci:v00008086d00004105sv*sd*bc*sc*i*
alias:          pci:v00008086d00004104sv*sd*bc*sc*i*
alias:          pci:v00008086d00004103sv*sd*bc*sc*i*
alias:          pci:v00008086d00004102sv*sd*bc*sc*i*
alias:          pci:v00008086d00004101sv*sd*bc*sc*i*
alias:          pci:v00008086d00004100sv*sd*bc*sc*i*
alias:          pci:v00008086d00008109sv*sd*bc*sc*i*
alias:          pci:v00008086d00008108sv*sd*bc*sc*i*
depends:        drm,drm_kms_helper,i2c-core,video,i2c-algo-bit
intree:         Y
vermagic:       3.16.0-4-amd64 SMP mod_unload modversions

with NixOS:
m@nixos% modinfo gma500_fgx
filename:       /run/booted-system/kernel-modules/lib/modules//4.4.13/kernel/drivers/gpu/drm/gma500/gma500_gfx.ko.xz
license:        GPL
description:    DRM driver for the Intel GMA500, GMA600, GMA3600, GMA3650
author:         Alan Cox<EMAIL_ADDRESS>and others
alias:          pci:v00008086d00008109sv*sd*bc*sc*i*
alias:          pci:v00008086d00008108sv*sd*bc*sc*i*
depends:        drm,drm_kms_helper,i2c-core,video,i2c-algo-bit
intree:         Y
vermagic:       4.4.13 SMP mod_unload modversions

In kernel config, the Debian above has:
CONFIG_DRM_GMA500=m
CONFIG_DRM_GMA600=y
CONFIG_DRM_GMA3600=y

… while we have:
CONFIG_DRM_GMA500=m
# CONFIG_DRM_GMA600 is not set
# CONFIG_DRM_GMA3600 is not set

I changed this, and am currently waiting. And waiting… And waiting… :smile_cat:

Yeah, confirmed this is the issue. You have to enable these in your kernel configuration:

DRM_GMA600 y
DRM_GMA3600 y

… e.g. in /etc/nixos/configuration.nix:
{
  nixpkgs.config.packageOverrides = super: {
    stdenv = super.stdenv // {
      platform = super.stdenv.platform // {
        kernelExtraConfig = ''
          DRM_GMA600 y
          DRM_GMA3600 y
        '';
      };
    };
  };
}

@edolstra, @shlevy, @joachifm, I’d like to propose adding those to options to the mainline kernels. These VGA controllers are usually put into slow netbooks. It took me 12 hours today to recompile the kernel on my mom’s netbook, for her to have working graphics. Both Debian and Arch have these options enabled, I’ve not checked other distros. @joachifm says this “sounds like an uncontroversial feature request.” What do you think?


Ignecarus not showing in recently killed/repeat trip

🐛 Bug Report
I've been doing igne over and over and it's never in the recently killed list I have to do /k name:Ignecarus (Solo) each time I return. also it doesn't appear as a repeat for the repeat trip button when I do =m mentioned In post #4058 by @Wcp7

This is just due to how the code works, it can't really show here, only 'normal' monsters can.


Use cleaner, up-to-date syntax

I have problem with new syntax, msbuild does not compile right.
Have you tried on ,net core.

Not yet, it doesn't build properly, I have to solve that first.

Also I prefer not having it so people not coming from CSharp can understand


fix: convert all getters to methods

The patch converts all the getters in the codebase into the methods.
For example, the request.url getter becomes the request.url()
method.
This is done in order to unify the API and make it more predictable.
The general rule for all further changes would be:

there are no getters/fields exposed in the api
the only exceptions are "namespaces", e.g. page.keyboard

Fixes #280.
BREAKING CHANGE:
This patch ditches getters and replaces them with methods throughout
the API. The following methods were added instead of the fields:

dialog.type()
consoleMessage.args()
consoleMessage.text()
consoleMessage.type()
request.headers()
request.method()
request.postData()
request.resourceType()
request.url()
response.headers()
response.ok()
response.status()
response.url()

Do any examples need to be changed?

@JoelEinbinder Yes, there's a missed spot in the docs. I just got bit by this.
Happy to fix, but do I use this issue for the PR or a new one?

Good catch. Referencing issue #280 would be great. Thanks!

You got it.


Use alternative to ogre

ogre and ogre_tools are only available until groovy. Is there an alternative for kinetic or melodic?

The ogre and ogre_tools build_depend lines can probably be deleted, are they causing you problems?  It catkiin builds without complaint for me in melodic.

@lucasw You are right, it builds and seems to work. So I guess these dependencies should be removed.


Iterators: Implement Map, ReduceByKey, Filter, and HashJoin.

This PR implements a handful more operators in the same spirit as the existing two.
This makes the set of operators expressive enough to implement about half of TPC-H (a standard database benchmark) except for the final sorting of the result. In addition to sorting (and TopK), the main missing operators are anti-join and outer join; further operators (such as left anti-join and left outer join) are also helpful for performance.

Looks great, please merge at your convenience!


Docs: broken link for implementation example

See https://github.com/ga4gh-beacon/beacon-v2/commit/16db543100221f40453f0dbe2950375fb65d58e3

Would be happy to provide a PR for https://github.com/gaurav-nelson/github-action-markdown-link-check so dead links are flagged as part of your CI. Let me know if that'd be helpful.

@surchs IMO yes! Would probably look at it for other projects, too :-)


initial commit for MultiReQA

Added MultiReQA, which is a dataset containing the sentence boundary annotation from eight publicly available QA datasets including SearchQA, TriviaQA, HotpotQA, NaturalQuestions, SQuAD, BioASQ, RelationExtraction, and TextbookQA.

looks like this dataset includes changes about many other files than the ones for multi_re_qa
Can you create another branch and another PR please ?

looks like this dataset includes changes about many other files than the ones for multi_re_qa
Can you create another branch and another PR please ?

Sure I will do that. Thank you.


Fix Flaky Test RecoveryFromGatewayIT.testShardStoreFetchMultiNodeMultiIndexesUsingBatchAction

Description
In RecoveryFromGatewayIT test, the created indices may be not started yet, but is used immediately, which will cause unexpected exception. when it throws the exception, the scene is as follows:

Related Issues
Resolves #14304

Check List

[ ] Functionality includes testing.
[ ] API changes companion pull request created, if applicable.
[ ] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@gaobinlong it's ok now, please have a look.


Unable to target bosh-lite VM on OS X Sierra

I've updated ruby to a newer version and set target with rbenv and suggested in other closed thread with no success.
Leto:bosh-lite chad$ ruby -v
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin16]
Leto:bosh-lite chad$ bosh -v
BOSH 1.3262.24.0
Leto:bosh-lite chad$ which bosh
/Users/chad/.rbenv/shims/bosh
Leto:bosh-lite chad$ bosh target <IP_ADDRESS> lite
RSA 1024 bit CA certificates are loaded due to old openssl compatibility
[WARNING] cannot access director, trying 4 more times...
[WARNING] cannot access director, trying 3 more times...
[WARNING] cannot access director, trying 2 more times...
[WARNING] cannot access director, trying 1 more times...
cannot access director (SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: sslv3 alert handshake failure)
nc -z <IP_ADDRESS> 25555
Connection to <IP_ADDRESS> port 25555 [tcp/*] succeeded!
Leto:bosh-lite chad$ curl -vk https://<IP_ADDRESS>:25555/info

Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 25555 (#0)
TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Server certificate: <IP_ADDRESS>

GET /info HTTP/1.1
Host: <IP_ADDRESS>:25555
User-Agent: curl/7.49.1
Accept: /

< HTTP/1.1 200 OK
< Server: nginx
< Date: Mon, 07 Nov 2016 23:39:15 GMT
< Content-Type: application/json
< Content-Length: 358
< Connection: keep-alive
< X-Content-Type-Options: nosniff
<

Connection #0 to host <IP_ADDRESS> left intact
{"name":"Bosh Lite Director","uuid":"fb70f16a-4d6f-41f8-bc2e-0181a03dff18","version":"1.3262.3.0 (00000000)","user":null,"cpi":"warden_cpi","user_authentication":{"type":"basic","options":{}},"features":{"dns":{"status":false,"extras":{"domain_name":null}},"compiled_package_cache":{"status":true,"extras":{"provider":"local"}},"snapshots":{"status":false}}}Leto:bosh-lite chad$

SSH in via vagrant has no issue, so doesn't appear to be a routing issue.
Leto:bosh-lite chad$ vagrant ssh
Welcome to Ubuntu 14.04.4 LTS (GNU/Linux 4.2.0-42-generic x86_64)

Documentation:  https://help.ubuntu.com/
vagrant@bosh-lite:~$

Anyone have any suggestions for troubleshooting bosh connection?

Please see https://github.com/cloudfoundry/bosh/issues/1322 for some suggestions. Perhaps try brew install ruby and use that ruby?

Ok I manually had installed the latest ruby, and had set my system using rbenv to use this latest version as shown above.  instructions from here:  https://gorails.com/setup/osx/10.12-sierra
I ran the command 'brew install ruby' and like magic it is now working for bosh target. I was not using the system ruby, which was being blamed as the culprit,
Leto:~ chad$ ruby -v
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin16]
Leto:~ chad$ which ruby
/Users/chad/.rbenv/shims/ruby
I'm not sure what configuration or link the brew install is creating, but it is now working none the less. Thank you!


atuin: 15.0.0 -> 16.0.0

Description of changes
https://github.com/atuinsh/atuin/releases
this mostly fixing a breakage with nushell 0.83 for me, so it would be amazing if this was merged quickly.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

this mostly fixing a breakage with nushell 0.83 for me, so it would be amazing if this was merged quickly.

If you are in a hurry then overlays are always an option to get the update into your config immediately.

@SuperSandro2000 took care of your comment.


No Game Over

You can go to lives = 0 or lower and no game over is called. Its nice for debugging, and we should keep a feature like that to run thru the levels. But it should work in beta 1.

Yes, you removed it xD @themangomago

works again


Provide empty mock for dgram module

dgram is an node module that provides an implementation of UDP Datagram sockets.
I'm using a package that depends on dgram, but does not need it for the most part. Providing an empty mock for dgram; just like there are empty mocks for fs, net and tls modules would save me from ejecting like in #672.
This should be as simple as adding line: dgram: 'empty' (NOTE: I have not tested this yet!) to the webpack configuration files, I can also provide a PR if you want.

I feel okay taking a PR like this.

#2600 here is the PR

Fixed by #2600.


Sorting lost while selecting row/re-rendering

Expected Behavior
Once column header is clicked to sort an column, it gets sorted. After that if a row is selected/custom button column is clicked, the sorted column should remain as it is.
Current Behavior
Sorted column is lost if row is selected or button column is clicked.
Steps to Reproduce (for bugs)

Your Environment

Tech
Version

Material-UI
4.8

MUI-datatables
2.13.3

React
16.12

browser - Chrome
78

etc

Do you use server-side?
So see the below example
https://github.com/gregnb/mui-datatables/blob/master/examples/serverside-sorting/index.js

This is fixed as of version 2.15.0 (latest version is 3.0.0).


Add the function of importing icon libraries

I am wordering if it is possible for typst to add the function of importing icon libraries, such as font-awesome?

Isn't it already possible to use these libraries as fonts with their corresponding Unicode icons? E.g. using the font "FontAwesome" for a single character should already work.

I did this super simply like this:
#let fa(codepoint) = text(font: "FontAwesome", codepoint)
#let fa-github = fa("\u{f09b}")
#let fa-envelope = fa("\u{f0e0}")
#let fa-map-marker = fa("\u{f041}")
#let fa-suitcase = fa("\u{f0f2}")

Somebody could make a template that could be imported with all the icons.

Somebody could make a template that could be imported with all the icons.

Hi, I have just created a repo that provides all free icons with the format fa-<icon-name>: https://github.com/duskmoon314/typst-fontawesome
The idea is to use FontAwesome's desktop fonts with a curried function fa-icon:
#let fa-icon(
  name,
  fa-version: "Font Awesome 6",
  fa-set: "Free"
) = text.with(
  font: fa-version + " " + fa-set,
  name
)

And function for specific icons is like this:
#let fa-chess-queen = fa-icon("\u{f445}")

The usage would be:
#fa-chess-queen(fill: blue)

Please give it a try and share your thought. 😄

Closing this in favor of the package. (It's out of scope for the compiler.)


Added lv locale

Forgot to guilp build, done that now. Is something still wrong?

Actually, please do not build... If you can, just force push without the last commit. Otherwise I'll handle it.

Merged manually. Thanks!


bugfix(op-node): syncClient incorrectly removes peer issue

Background
When the staticPeer is configured with a DNS address (such as /dns/xxx.com/tcp/xxx/p2p/xxx), a peer can obtain multiple IP addresses through domain name resolution. However, in Libp2p, dialing concurrently can result in one peer corresponding to multiple connections, which is exacerbated by multiple IP addresses. If one of the connections is disconnected due to an unstable network or other reasons, the Notifiee.Disconnected event is triggered. At this time, the peer is removed from the syncClient, and the processing flow of the peerLoop exits. The log displays the message stopped syncing loop of peer. However, the peer still has other connections that can be used for p2p synchronization. Therefore, we should not remove this peer unless we determine that all of its connections are disconnected and there are no available connections, just like the check performed by the monitorStaticPeers function.
Solution
Add a condition to determine when to remove a peer from the syncClient: only remove the peer if it cannot establish a connection.

The same changes have been submitted to the Optimism chain: https://github.com/ethereum-optimism/optimism/pull/7348 and were approved


New maintainer needed.

I don't really use this in any of my projects anymore and do not have the time to maintain it.
Currently this module has very very light responsibilities, which is mostly managing pull requests from greenkeeper.
If you are interested in taking this module over please leave a comment in this issue.

Hi, @wraithgar!
I would be interested in maintaining this project. My focus these days are on APIs, and Hapi and JSON-API have become my go-tos for REST APIs. So this is a good fit for me.
Are you planning to stay involved in the project or leave it entirely?

Howdy @kjellmorten! I do not intend to be involved in the project at all.

Ok, no worries. I can take this off your shoulders. :)

What is your npm username?  Do you mind if I transfer this repo to your account?

Please do. It's @kjellmorten, just as on Github.


bump pkgversion, fixes #86

Codecov Report

Merging #87 (7d102e0) into master (c9f5e4d) will decrease coverage by 0.52%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #87      +/-   ##
==========================================
- Coverage   89.15%   88.62%   -0.53%
==========================================
  Files          13       13
  Lines         756      756
==========================================
- Hits          674      670       -4
- Misses         82       86       +4

Impacted Files
Coverage Δ

src/utils.jl
63.07% <0.00%> (-6.16%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


= Unity 2020.1 compatible persistent, local WorldAnchorStore

Describe the problem
Unity 2020.1 will remove WorldAnchorStore functionality.
Describe the solution you'd like
WorldAnchorManager wrapping another solution that allows for local, persistent world anchors.
Describe alternatives you've considered

Using Azure Cloud, which while allowing a number of free requests per month, requires a credit card attached to an Azure account.
Using deprecated code with warnings in it like https://www.anderslundgren.se/creating-local-world-anchors-on-hololens-2/ and staying on 2019 for the forseeable future.

Additional context
N/A

This is coming! We've been working with Unity to add an extension to the Windows XR Plugin to allow for anchor store access for XRAnchor/XRReferencePoint.

Fantastic; good to hear! I'll be looking forward to seeing it implemented 👍

Finally an update! The API has shipped (or will ship any moment) in the 2.5 package.
The APIs to use are TryGetAnchorStoreAsync and the resulting XRAnchorStore APIs.
Happy to provide some additional examples of use if requested, and we should update WorldAnchorStore in MRTK to support this API.

@keveleigh I am trying to write an implementation that uses the new API for placing, saving and sharing Spatial Anchors.
I got this to work using the XRReferencePointSubsystem and XRAnchorStore. My Code is based on an example found here:
https://forum.unity.com/threads/world-anchors-on-the-hl2-with-the-new-xr-plugin.1035256/#post-6711919
But currently my code only allows me to persistently save anchors on 1 device (local). I would like to share the saved Anchor to another device. Only Saving the TrackableId seems to be insufficient to 'find' the Anchor when not saved to the XRAnchorStore (which is only local data, I assume).
What is the best way to share the locations of these anchors between devices (without using Azure)?
I found this class in the native UWP code:
https://docs.microsoft.com/en-us/uwp/api/windows.perception.spatial.spatialanchortransfermanager?view=winrt-19041
Is there an already existing implementation of this within the Unity API? Or some examples of how to best combine this with the existing API? Or maybe there is an entirely different way which I overlooked?
Thanks in advance!

@keveleigh I am trying to write an implementation that uses the new API for placing, saving and sharing Spatial Anchors.
I got this to work using the XRReferencePointSubsystem and XRAnchorStore. My Code is based on an example found here:
https://forum.unity.com/threads/world-anchors-on-the-hl2-with-the-new-xr-plugin.1035256/#post-6711919
But currently my code only allows me to persistently save anchors on 1 device (local). I would like to share the saved Anchor to another device. Only Saving the TrackableId seems to be insufficient to 'find' the Anchor when not saved to the XRAnchorStore (which is only local data, I assume).
What is the best way to share the locations of these anchors between devices (without using Azure)?
I found this class in the native UWP code:
https://docs.microsoft.com/en-us/uwp/api/windows.perception.spatial.spatialanchortransfermanager?view=winrt-19041
Is there an already existing implementation of this within the Unity API? Or some examples of how to best combine this with the existing API? Or maybe there is an entirely different way which I overlooked?
Thanks in advance!

I think before there was the WorldAnchorTransferBatch in C# as documented by this documentation page, but maybe this is for the deprecated API and an equivalent doesn't exist yet in the new API?

I think before there was the WorldAnchorTransferBatch in C# as documented by this documentation page, but maybe this is for the deprecated API and an equivalent doesn't exist yet in the new API?

@wspaas I'm very interested in your findings when you hopefully find a solution, please update us if you make progress :)

@wspaas I'm very interested in your findings when you hopefully find a solution, please update us if you make progress :)

Any update on this?

Looking forward to update

Looking forward to the update

Hello, my team and I also really need a solution on this when it's possible ! Any news?

Hi, are there any updates?

Hello,I also need a solution.

Still looking for a solution. Any news?

I've got anchor downloading/uploading working in Unity 2021 (and 2020, but I haven't tested the code since updating it to 2021).
I pulled the code from an existing project and haven't tested if the code works standalone. But it might be a nice place to start for you guys. A very important step is to create an Assembly definition to enable the MR_OPENXR define when you're using unity 2021.
https://gist.github.com/NLR-L/795741d9a2e13e59809fc5c4af49e0ce
Maybe if I've got some time I'll make an small example project to show how anchors can be shared using Mirror  as the networking solution.

I'm sorry I can't post the code of the solution.
But you can make use of the unity ArFoundation package, to convert an anchor to an anchor pointer.
https://forum.unity.com/threads/arfoundation-aranchor-nativeptr-needs-extra-conversion-for-openxr.1199446/
Then you can use this SpatialAnchor together with the SpatialAnchorExporter to export your anchors.
When you read out this data you can import it with the SpatialAnchorTransferManager.
I've got to go, and will talk more about the importing of the anchor later.

For OpenXR, we have some samples showing off the new XRAnchorStore APIs: https://github.com/microsoft/OpenXR-Unity-MixedReality-Samples/blob/3917606bae2dd495cdd5680d33701ccd2caee3d7/BasicSample/Assets/ARAnchor/Scripts/AnchorsSample.cs#L51

What's the status ?
What is the solution to share a world anchor locally between 2 HL2 ?
Can we follow this guide to share anchors locally ?
Should we follow this sampleinstead ?
Or should we use this sample ?

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


hledger-iadd-1.1.4 test suite does not compile

Citing from http://hydra.nixos.org/build/47699412/nixlog/1/raw:
tests/Data/Text/Zipper/Generic/WordsSpec.hs:15:1: error:
    Ambiguous interface for ‘Data.Text.Zipper.Generic.Words’:
      it was found in multiple packages:
      text-zipper-0.10 hledger-iadd-1.1.4

Yes, text-zipper now includes this module. I will remove it from hledger-iadd later today -- in the meantime compile it without tests or use an older text-zipper.

Done and released. Thanks for reporting!


A bit.ly url does not work

other links that r shorted needs to be working or else this may not be a true rickroll detector fix this plz

Same as #1

How can you possibly do that?
Let's break down the problem:

At the moment, there is a 'rickroll' url directory, located at https://raw.githubusercontent.com/PGgamer2/Rickroll-Detector/main/rickrolls.json that is site is using
It matches the video ID and identifies if it is in the directory

Now how do bit.ly url's work (or any shortener)?

A URL Redirect is created.

Now it's obvious that it is impossible to repeatedly add new shortened URLs and the list will not end.
Potential Solution:

Identify a method to pre-expand the URL before scanning the Video ID for a rickroll

As stated in #1, I can't expand all shortened URLs because I can't make the browser resolve redirections nor download webpages without receiving a CORS error. The only thing I can do is implement a resolver specifically for Bitly by using their API. The problem with this approach is that I would need to do that for every URL shortener.


⚠ ClamAV has degraded performance

In 28c5359, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in f998a1d.


Publish and Unpublish APIs not working for aem62

Activate and deactivate page working perfectly in aem6.1. It in fact runs thru the create page dialog as well clearly.
But it is not working in aem 62.  seems stuck.
if this is a friendly framework for aem 62, It would be great to call it out now itself as we will moving to aem 64 sooner so that I will be able to find out an alternative else stop using the compiled classes and use the framework directly so that we get to fix it as we face issues while using it.

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"css selector","selector":"button[icon='globeStrike']"}
(Session info: chrome=66.0.3359.139)
(Driver info: chromedriver=2.38.551581 (2c9c29527ada10af4745ab26dd000ebb6d5e055e),platform=Mac OS X 10.12.6 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.11.0', revision: 'e59cfb3', time: '2018-03-11T20:26:55.152Z'
System info: host: 'C02SNYAUGVC1', ip: '<IP_ADDRESS>', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.12.6', java.version: '1.8.0_152'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities {acceptInsecureCerts: false, acceptSslCerts: false, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 2.38.551581 (2c9c29527ada10..., userDataDir: /var/folders/gv/jdzvrj1j5cg...}, cssSelectorsEnabled: true, databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: MAC, platformName: MAC, rotatable: false, setWindowRect: true, takesHeapSnapshot: true, takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: , version: 66.0.3359.139, webStorageEnabled: true}
Session ID: ab21eea294f22d84607e783a17d66c48
*** Element info: {Using=css selector, value=button[icon='globeStrike']}

Closing this for now, in case of any further update/questions, let us know.


Integration Test - Release - 2019/02/07 22:39:31

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest3 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.


[PAYEX-770]feat: add endpoint for listing checkout sessions

Add listing checkout sessions endpoint in sample app
https://circlepay.atlassian.net/browse/PAYEX-770

Could you add a screenshot?