Update mirb.c

Next time, we want to see more descriptive message than Update mirb.c,
for example, fixed a typo in comment.


Support for ruby symbol-to-block cast with &

It'd be super cool if I could convert
[1, 2, 3, 4].map(&:to_s)

to
[1, 2, 3, 4].map do |i|
  i.to_s
end

This is a bit ambiguous because of the name of the block parameter - it could just always be i, or maybe the singularization of the variable if a variable is used instead of a literal? But then there's localization...

I've pushed a commit that should implement this. Could you try it out and see if it feels right?

Doesn't work with method names containing either ! or &

Looks great besides that.

Ah, of course. I've just pushed a commit that should fix that.

LGTM! :grinning:


Python 2/3 compatibilty fixes for example notebooks

Tested with both python 3.7 and 2.7 installs

The animation files are not present as they don't generate correctly for me on jasmin. Might be worth re-running them to get them back


Getting value?

How does one get the value of all of the select boxes? As soon as the checkbox is marked my function fires off. Can you provide an example?

I also need the value of all the selected boxes. Please let us know if it can be done with current package.

I also need this :(

same

in my component state I define an array (initial value is from redux store)
this.state = {
    taskTypeName: props.taskFilters.taskTypeName
}

then I use this component
<View>
    <MultipleChoice
        style={{ backgroundColor: 'white' }}
        options={this.props.taskTypes}
        selectedOptions={this.state.taskTypeName}
        onSelection={this.onSelectionsChange}
    />
</View>

and my state is getting updated automatically with the selected items. log the state in onSelection as follows and you will have all your selection in the state.
onSelectionsChange = (selectedTaskType) => {
  console.log(selectedTaskType, this.state.taskTypeName);
}


rejecting single zero port

rejecting single zero port and adding support for single digit port numbers

Could you add unit tests for this?

@kvesteri i added the test cases

tests failing


PUT /model with model_server fails: 'dict' object has no attribute 'url'

Rasa version: Rasa 1.1.0a1
Python version: Python 3.6.8
Operating system (windows, osx, ...): Docker image rasa/rasa:latest-full
Linux 6f5ab25d1c4d 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 GNU/Linux
Issue: using model_server endpoint for https://rasa.com/docs/rasa/api/http-api/#tag/Model/paths/~1model/put leads to error
AttributeError: 'dict' object has no attribute 'url'
Error (including full traceback):
  File "/usr/local/lib/python3.6/site-packages/rasa/server.py", line 258, in _load_agent
    action_endpoint=action_endpoint,
  File "/usr/local/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/usr/local/lib/python3.6/site-packages/rasa/core/agent.py", line 246, in load_agent
    model_server,
  File "/usr/local/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/usr/local/lib/python3.6/site-packages/rasa/core/agent.py", line 53, in load_from_server
    await _update_model_from_server(model_server, agent)
  File "/usr/local/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/usr/local/lib/python3.6/site-packages/rasa/core/agent.py", line 107, in _update_model_from_server
    if not is_url(model_server.url):
AttributeError: 'dict' object has no attribute 'url'

Command or request that led to error:
curl -X PUT -H 'Content-Type: application/json' -i http://localhost:5005/model --data '{"model_file": null, "model_server": {"url": "http://localhost:5000/model/8b200dad622c4ed9b9636e8ec7b12660", "params": {}, "headers": {}, "basic_auth": {}, "token": "", "token_name": "", "wait_time_between_pulls": 0}}'

Issue seems to be because of following files:
https://github.com/RasaHQ/rasa/blob/e4d3335a7834b56ab52c68bb30ae58b94e9b6ddd/rasa/server.py#L818
model_server is just a get on json, never converted to an object.
https://github.com/RasaHQ/rasa/blob/e4d3335a7834b56ab52c68bb30ae58b94e9b6ddd/rasa/core/agent.py#L107
Accessing the json object (dict) as if its an EndpointConfig
This pull request fixes it: https://github.com/RasaHQ/rasa/pull/3769

Thanks for raising this and providing a great level of detail! As mentioned in the PR, we'll review it asap :)

Hello, @mmalhotra I have the same issue, if you solved it, can you guide me please !!

@illi88 this is fixed in the latest docker image:
I can confirm it in the following sha:
"Id": "sha256:a4e11142877cd6f14361f1ba27c4e2dffa7746526f17435f1f54a04e575a62a3"


Add wjdp.uk

Size was 28k when measured today.
See https://tools.pingdom.com/#5dd19536a7800000

Looks good, but I'm getting 28.4 KB pretty consistently - maybe update to that and then I'll merge 😃

Looks good, but I'm getting 28.4 KB pretty consistently - maybe update to that and then I'll merge 😃


cloak docs authentication

Github authentication for Cloak docs.

@jpadams: Because cloak is now open, I guess this PR is not relevant anymore, right ?

@slumbering what would happen if we merge this? any issues?
Seems like it could be valuable to capture this in the codebase since you've just got it working again. WDYT?

@jpadams yep there is one issue while I try to authenticate. Even if I have access to the cloak repo, I get an error 401. Not sure why because the api that check users permission works 🤔 . It shouldn't be a problem to fix the issue thought. I was just wondering do we still want to keep cloak docs private as cloak itself is now available in dagger repo? Moreover we are working with Vikram on docs versioning implementation.


fix(deps): revert fullcalendar to 4.4.0 as it breaks calendar. Fixes HELP-1281

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


Enhanced Game Animations and Transitions #183

PR Description 📜
Enhancing game animations and transitions for smoother user experience. Updates include optimizing keyframes, adjusting durations, and ensuring performance
Fixes #183

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ ] I have added screenshot for review.

include a video demo

Hello @Ultimecia1463
Can you fix the merge conflict?

Hello @Ultimecia1463 Can you fix the merge conflict?

yes

@Lovelyfin00 done

I can't test your PR on my end
Can you include a video demo?

I can't test your PR on my end Can you include a video demo?

ok i'll post a video demo

Hi @Ultimecia1463
I was able to test it out and I saw nothing related to animations. Where'd you add the animations and transitions?
Also, I'd like you to undo the changes on the instructions container. It makes it smaller and not good for user experience.

before
https://github.com/GameSphere-MultiPlayer/Dot-Box/assets/144516349/ce87c3d3-72c7-4455-b12c-e85a40a074b3
after
https://github.com/GameSphere-MultiPlayer/Dot-Box/assets/144516349/ce8551e4-7964-436c-b607-a74b2dc447b5
changed box fill animation and player win animation

@Lovelyfin00 look into it


feat: Adding gvfs-nfs package to silverblue image.

This addition enhances the file manager's functionality, allowing users to mount NFS storages via Nautilus.

Thank you!


Add support for storage controllers

The Q release (v2.5) of the CloudControl API has introduced support for explicitly controlling the storage controllers in a deployed server.
Because the behaviour of disk management when using custom storage controllers diverges from the existing behaviour, storage controllers and their disks will be managed via a separate ddcloud_storage_controller resource type:
resource "ddcloud_server" {
  name = "My server"

  // Disks can either be specified here (order now matters)
  disk {
    // SCSI unit Id can no longer be specified here
    size_gb = 10
    speed   = "STANDARD"
  }
}

resource "ddcloud_storage_controller" {
  server = "${ddcloud_server.my_server.id}"
  adapter_type = "LSI_LOGIC_PARALLEL"
  bus_number = 1

  // Or disks can be specified here (order does not matter)
  disk {
    scsi_unit_id = 0 // SCSI unit Id can now be specified here
    size_gb       = 10
    speed         = "STANDARD"
  }
}

For a given ddcloud_server, you can either specify disks the old way (inline, but without a SCSI unit Id) or with an explicit storage controller (but not both). Since disks specified the old way no longer have an explicit SCSI unit Id, their order now matters (i.e. you cannot have 3 disks and remove disk 2). Disks specified via the new way (with explicit storage controller) have an explicit SCSI unit Id and their order there does not matter.
These breaking API changes are expected to also require refactoring of the existing ddcloud_server resource implementation due to changes in the format of information returned by v2.5 of the CloudControl API.
Note that it's theoretically possible to to support specifying disks and controllers in the same ddcloud_server resource but this would greatly complicate the provider implementation for this resource type (disks with a value for controller_id would have to be processed after any controller entries, and Terraform may no longer be able to automatically warn the user about changes that force a new resource or are otherwise invalid).
See below for an alternative design proposal.
See also:

DimensionDataResearch/go-dd-cloud-compute#12
DimensionDataResearch/dd-cloud-compute-terraform#33
DimensionDataResearch/dd-cloud-compute-terraform#52
DimensionDataResearch/dd-cloud-compute-terraform#56

CC: @kumarappanc @mingsheng36 @wninobla @jeffstoner @johnamurray @alexbacchin
Your input would be appreciated, both regarding this design and the trade-offs it involves.

A possible alternative for the design might rely on the fact that disks that don't explicitly specify a controller Id are always created against controller 0 (the default controller).
resource "ddcloud_server" "my_server" {
	name = "My Server"

	storage_controller {
		bus          = 1
		adapter_type = "BUS_LOGIC"
	}

	// Old-style disk (implicitly targets controller 0)
	disk {
		scsi_unit_id = 0
		size_gb      = 10
		speed		 = "STANDARD"
	}

	// New-style disk (explicitly targets controller 1)
	disk {
		bus          = 1
		scsi_unit_id = 0
		size_gb      = 10
		speed		 = "STANDARD"
	}
}

Note that some experimentation is required to see if this is a viable approach (if the internal model can be modified so that we're always explicitly targeting a specific storage controller, and simply default that controller to 0 when it's not specified by the user then it just might work).

Given what's coming in the R release (support for IDE/SATA,) there may be another jumbling of the storage subsystem metadata. The design phase of this is currently on-going, so I can't comment on exactly what changes are happening (because they're very much in-flux) but we should be careful with the modeling - might want to consider using "disk type" structures that cater to the bus they're attached to (IDE disks won't have a scsi_unit_id, etc.)

There are (currently) 4 storage adapters supported by the platform:
There are four adapters supported by vSphere:

BusLogic Parallel - This was one of the first two emulated vSCSI controllers made available in the VMware platform, and remains commonly used on older version of Windows as the driver is available by default.
LSI Logic Parallel - This was the other emulated vSCSI controller made available in the VMware platform, and remains commonly used on UNIX Operating Systems
LSI Logic SAS - This is a newer evolution of the parallel driver supported (and in some cases required) for newer versions of Microsoft Windows. It was designed to replace the BusLogic Parallel adapter and provides better performance than the original BusLogic Parallel adapter.
VMware Paravirtual - This is a VMware-specific driver that is virtualization-aware and designed to support very high throughput with minimal processing cost and is therefore the most efficient driver. However, this driver requires that VM Tools be installed and running in order to function properly. There are some other restrictions, particularly on older operating systems - review the appropriate VMware documentation for more details.

(source: https://docs.mcp-services.net/pages/viewpage.action;jsessionid=E61080748C1D3F34342D36D225289A95?pageId=3015251)

Your statement

disks which don't explicitly specify a controller Id are always created against controller 0 (the default controller)

conflicts with the defined MCP behavior

If you do not manually select the SCSI Controller and position of the disk, it will be added sequentially to the next available SCSI controller and position.

(source: https://docs.mcp-services.net/display/CCD/How+to+Add+Additional+Local+Storage+(Disk)+to+a+Cloud+Server - Prerequisite 5.)

Thanks for the feedback - that's useful :)
Unfortunately it sounds like these changes may make the provider quite painful to use, so I may hold off on building anything until we can find a design compromise that fits. I'll keep thinking about it.

conflicts with the defined MCP behavior

On the other hand, this is Terraform behaviour we're talking about, not CloudControl. As long as the behaviour is well-documented, I think I'd still be comfortable with it.
As for SATA controllers, we could add a sata_disk type:
resource "ddcloud_server" "my_server" {
  name = "My Server"

  // SCSI disk, bus 0
  disk {
    scsi_unit_id = 0
    size_gb      = 10
  }

  // SCSI disk, bus 1
  disk {
    bus          = 1
    scsi_unit_id = 0
    size_gb      = 100
  }

  // SATA disk
  sata_disk {
    size_gb = 50
  }
}

Just my two cents worth…
Since we treat the no guest OS customization differently in terms of deployment vs. on that does guest OS customization maybe we just keep it separate.  In other words, maybe you have a different method that handles ddcloud_server vs. say one that’s dedicated to storage say ddcloud_storage?  Not sure if that makes it more convoluted but we kind of already do that for NIC’s and anti-affinity.  Deleting/changing around post deployment may be easier although I’m not sure what we have to adhere to API wise (e.g. VM’s currently require to always have one disk connected).
Again just some thoughts here.  If I’m off-base please ignore as it’s Monday… =)
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data
P  Please consider the environment before printing this email
From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, April 17, 2017 1:19 PM
To: DimensionDataResearch/dd-cloud-compute-terraform<EMAIL_ADDRESS>Cc: William Ninobla (ITaaS<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [SUSPICIOUS MESSAGE] Re: [DimensionDataResearch/dd-cloud-compute-terraform] Add support for storage controllers (#84)
This message contains suspicious characteristics and has originated from outside your organization

Thanks for the feedback - that's useful :)
Unfortunately it sounds like these changes may make the provider quite painful to use, so I may hold off on building anything until we can find a design compromise that fits. I'll keep thinking about it.
—
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/84#issuecomment-294579732, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9vxuj59lMw6SbwhMLCd41J2YaOs4yks5rw8kzgaJpZM4M-7AM.
itevomcid

(I'm trying to be mindful of backward-compatibility here)

Thanks @wninobla - that does make sense. I'm favouring option 2 at the moment as it's a little more user-friendly, but I'm open to suggestions :)

Works for me.  It’ll keep the existing server.tf files consistent if they break them out vs. doing it as one big monolithic build.  And yeah I agree on the behavior piece.  We’ll just need to flag it as one that we can do during a build vs. after the fact.
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data
P  Please consider the environment before printing this email
From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, April 17, 2017 1:30 PM
To: DimensionDataResearch/dd-cloud-compute-terraform<EMAIL_ADDRESS>Cc: William Ninobla (ITaaS<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [SUSPICIOUS MESSAGE] Re: [DimensionDataResearch/dd-cloud-compute-terraform] Add support for storage controllers (#84)
This message contains suspicious characteristics and has originated from outside your organization

(I'm trying to be mindful of backward-compatibility here)
—
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/84#issuecomment-294583064, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v-t8Q9K96OjCcEkjfTV1NgrMgUYzks5rw8uygaJpZM4M-7AM.
itevomcid

I’d say deleting some snips vs. adding new one’s is 50/50.  Just depends on how complex someone has gotten with their TF files.  Then again , most of those folks code for a living so it should be more of an annoyance than a blocker so…
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data
P  Please consider the environment before printing this email
From: Adam Friedman<EMAIL_ADDRESS>Sent: Monday, April 17, 2017 1:32 PM
To: DimensionDataResearch/dd-cloud-compute-terraform<EMAIL_ADDRESS>Cc: William Ninobla (ITaaS<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [SUSPICIOUS MESSAGE] Re: [DimensionDataResearch/dd-cloud-compute-terraform] Add support for storage controllers (#84)
This message contains suspicious characteristics and has originated from outside your organization

Thanks @wninoblahttps://github.com/wninobla - that does make sense. I'm favouring option 2 at the moment as it's a little more user-friendly, but I'm open to suggestions :)
—
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/84#issuecomment-294583977, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v3ynEvsx2W3Zb_SU38OmHH4C2OZSks5rw8xagaJpZM4M-7AM.
itevomcid

Same here, backwards compatibility is a must. These storage adapters changes makes practically no difference for 90% of the users as the underlying physical storage infrastructure still the same.

Breaking changes to Terraform provider schema are risky for users - not so much for new deployments, but for existing deployments where the configuration suddenly means something different than it did before. Something I'd like to minimise if possible :)

On the other hand, this is Terraform behaviour we're talking about, not CloudControl. As long as the behaviour is well-documented, I think I'd still be comfortable with it.

Just to clarify, @jeffstoner, the design ethos for our Terraform provider is to use CloudControl terminology and semantics wherever it's practical to do so unless it conflicts with Terraform's resource / schema / life-cycle model.
We currently use a disk's SCSI unit Id to uniquely identify each disk in the configuration because the Id is only known after deployment (so we match up CloudControl Ids to SCSI unit Ids). The proposed design attempts to retain those semantics because otherwise we have no way to tell which disk is which except by their ordering (which is undesirable - otherwise if you had 3 disks and removed the middle we'd have no way of knowing that).

The commit's a bit messy (latest version of Go and associated tooling is more pedantic than usual and had to fix a lot of code-analysis warnings) but I've built a (totally untested) first attempt at implementing option 2. Thanks to some earlier refactoring I'm pleased to say it wasn't actually that much work.
I'll try to have a go at actually testing it sometime today or tomorrow to see what breaks (and, if broken, whether it can be fixed).

Working on a prototype for option 1 in feature/ddcloud-storage-controller.

Ok, so the following configuration works correctly now (branch for option 1):
provider "ddcloud" {
	region = "AU"
}

data "ddcloud_networkdomain" "ansible_test" {
	name		= "AnsibleTest"
	datacenter	= "AU9"
}

data "ddcloud_vlan" "ansible_vlan" {
	name			= "AnsibleVLAN"
	networkdomain	= "${data.ddcloud_networkdomain.ansible_test.id}"
}

resource "ddcloud_server" "test_server" {
	name			= "TerraformTestServer1"

	image			= "Ubuntu 16 64-bit 2 CPU"

	networkdomain	= "${data.ddcloud_networkdomain.ansible_test.id}"

	primary_network_adapter {
		vlan = "${data.ddcloud_vlan.ansible_vlan.id}"
	}

	admin_password	= "snausages!"
}

resource "ddcloud_storage_controller" "test_server_controller_0" {
	server			= "${ddcloud_server.test_server.id}"
	scsi_bus_number	= 0

	disk {
		scsi_unit_id	= 0
		size_gb			= 20
	}

	disk {
		scsi_unit_id	= 1
		size_gb			= 40
	}
}

resource "ddcloud_storage_controller" "test_server_controller_1" {
	server			= "${ddcloud_server.test_server.id}"
	scsi_bus_number	= 1

	disk {
		scsi_unit_id	= 0
		size_gb			= 30
	}

	disk {
		scsi_unit_id	= 1
		size_gb			= 25
	}
}

If I remove disk 2 (scsi_unit_id = 1) on test_server_controller_1, Terraform produces incorrect diff output when running terraform plan but does behave correctly when running terraform apply. Pretty sure the diff output is due to a bug in Terraform (not really related, but along similar lines to hashicorp/terraform#10520).

Implemented in 1.3.0-alpha2.


2.0.2

[x] channelOnly

Don't merge now!

slash gui https://github.com/Garlic-Team/GCommands/commit/f2b3382373c8066498677699d2fb2b31d6f3b5dc

https://github.com/Garlic-Team/GCommands/commit/5f2abaddb1ebf44044f4a5ea8acf7154283dbaea

https://github.com/Garlic-Team/GCommands/commit/a4241be25b6ab6960e8fe34a5b06e140fd44b638

https://github.com/Garlic-Team/GCommands/commit/94c8c3fb63e3123c29c969e1bd263cc1e30bc342

https://github.com/Garlic-Team/GCommands/commit/3845ecd565224dd77a06a96fbad1197d196eecdd

https://docs.npmjs.com/about-semantic-versioning

https://gcommands.js.org/guide/additional/fromv2tov3.html

https://github.com/Garlic-Team/GCommands/commit/b46a68ee77423d598977b4a6a2e2896f8675b73c

guide https://github.com/Garlic-Team/GCommands/commit/610c2323b5320ceb4069534d35e9188135bc0d7d

guide https://github.com/Garlic-Team/GCommands/commit/fb986f87a56508fdc8e88dcf9cfcf079bd84e29b

https://github.com/Garlic-Team/GCommands/commit/3165838f2d5fb4ea15f4084ad572380e7ed1549e

https://github.com/Garlic-Team/GCommands/commit/c98ca691a6838093b7988a7c8bc3e3a588ed3bee

https://github.com/Garlic-Team/GCommands/commit/f94d5fba26741c9f07ab16309c89499fff4deadb

guide https://github.com/Garlic-Team/GCommands/commit/03401517d6c610df01872cd8bb09b5e2721dbcc7

guide https://github.com/Garlic-Team/GCommands/commit/3da924fb85780e40a7b461e46268b078617a091e

guide https://github.com/Garlic-Team/GCommands/commit/accd027e2b1c386472ca681d8e44c7056f812b95

docs https://github.com/Garlic-Team/GCommands/commit/acc20012e313045f5ab432f42a1a9c071d0f29d5

guide https://github.com/Garlic-Team/GCommands/commit/41c908fb7be9412ba1b20f2d33d9c70a68e9554e

waiting @SebestikCZ  for review

asi ok

Okay, merge 😄

https://github.com/Garlic-Team/GCommands/commit/accfd293586582c854765847e204c9b49d3b0558


Glyph Search

Description
Opinionated glyph picker that allows you to paste pretty arrows (←→), special keys (⌃⌘⇧⌫) and other cool stuff (❖◇♡★☆) without opening Character Viewer. The goal of this extension is not to replace the Character Viewer altogether, but to provide a faster alternative for frequently used characters that probably did not make it onto your keyboard
Screencast
https://user-images.githubusercontent.com/11464592/218311230-b97c1c25-b093-4c16-9019-f9c2f4afe2e5.mp4

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

PSA: Due to the lack of better options, I had to include basically every character from Inter as an SVG, so there's about 8mb of SVGs in the assets folder. While reviewing, you can filter them out using the File Filter dropdown :)

Just a question, did you see this extension before making yours?

Hi! I did, and tried integrating it into my workflow, but I have found myself going back to the Inter charset page and copying the glyphs from there. Usually, it’s a lot easier for me to visually pick one arrow from ten different options than to try and find it using search, and for that a grid layout works a lot better than a list layout, where the glyph is ten times smaller.At first, I wanted to contribute to the extension you mentioned, but then quickly realised that Raycast API doesn’t allow devs to show glyphs in a grid, only vector images, and that would mean I would need to bundle 40 thousand images with the extension. Another approach would be to only use a subset of characters (like I did in my extension), and it will probably work for most people, but for everyone else it will probably break their workflow (https://xkcd.com/1172/)Hopefully this makes sense, but I will understand if my extension will be considered a duplicate On 14 Feb 2023, at 21:47, Per Nielsen Tikær @.***> wrote:
Just a question, did you see this extension before making yours?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Is there a way to download the icons from a secure path, like the GitHub repo, on opening the command? Would be more nice and save more than 8mb in the repo 😊

Trying to figure out how to do it right now, will maybe release it next week. I got the SVGs from here, so I'll probably try to parse them out of this page at runtime.

You can maybe see how it's done in https://www.raycast.com/yug2005/react-icons
basically: react-icons has a bunch of JSONs to specify what icons exist, and when the extension loads, the data in those JSONs is used to create URLs to GitHub

Done! Moved the SVGs to a separate repo, now the extension loads the glyphs from there


warn when attempting to select a disabled option - Issue #1531

The use case is this:
I have a cucumber test that is working fine. Than I add a "disabled" option to some items dynamically. The test still passes, while a user couldn't select an option.

@Vanuan What driver are you using?

It's phantomjs

Posted there https://github.com/ariya/phantomjs/issues/13303

Oh, no it's poltergeist

@Vanuan but is it actually selecting the option, or just ignoring the select --- I would hope it's just ignoring the select.  Capybara will not be throwing an exception for this behavior currently (just issuing a warning - which will also issue for poltergeist), so I would hope poltergeist throw since that would mean different drivers with different behaviors.   If you want your test to fail when trying to select a disabled element then you will need to assert that the value was or was not actually selected.


Major refactoring

Goals of this refactoring:

reduce redundancy
improve flag handling

I see mixture of commits(deployment strategies + refactoring).
Also, apply the comments we talked on the first review.
In the PR comment, explain in details what have you done

Closing this until change is redone


Ticks and Crosses don't show up when using bg colors

The colors feature is fantastic!  However, there is a problem when using chalk's bg colors.  The icons (ticks / crosses etc that appear to the left of tests) don't show up.  Any idea why this might be?
Thanks again!

It's because the symbols are also styled by chalk and if for example the success color is bgGreen you will not see the symbol ✔ because it is also green but on a green background.
We can fix this by giving the symbol the same color from the config.

Released as v1.1.1

awesome!


Recheck if data still needs to be loaded?

Hi,
I have this case that after fetchData there is still white space that mugen could still fill in with data, but he don't want to becasue there is no scroll yet. In smaller resolution it's working fine (scroll is there from very beggining) but in higher resolution it's stops to work. I have tried to experiment with couple combinations of params but no effects. I know that one solution would be to take bigger chunk of data, but still you will be able to find screen resolution that this chunk of data is unsufficient to fill whole white space.
Any ideas? Thanks!
P.S.
Great plugin mate!

You can put a button inside <mugen-scroll> component to allow user to trigger fetchData manually:
<mugen-scroll :should-handle="!loading" :handler="fetchData">
  <button @click="fetchData">{{ loading ? 'Loading...' : 'Load more' }}</button>
</mugen-scroll>

Hmm I don't really feel like this is a good solution... I'm looking for some kind of automated solution here...

@egoist , @marverix : Mugen-scroll only shows what is handed to it. If this passes the visible scroll barrier, it will hook an event listener to do something once that point is reached. If the data is above the screen height however, there is nothing more to scroll until you send more data.
Suggestions include:

Send more initial data to ensure you have enough data to cover visible screen estate in height axis
Do your own JS calculations for height and call your fetchData function based upon the result

In short; Mugen-scroll does nothing wrong, and expects the developer to know (or research) what caveats exist when connecting data retrieval to scroll-linked events.

Ok, thanks :)


How to programmatically create a schema?

Hello! I wonder whether it is possible to create a schema programmatically?
For example, this code should generate a query class with two query fields. However, it ends up with an exception: AttributeError: type object 'Query' has no attribute '_type_definition'.
import random

from strawberry.asgi import GraphQL
from starlette.applications import Starlette
import strawberry

query_dict = {}

names = ["random_float", "random_int"]
types = [float, int]

for i, (n, t) in enumerate(zip(names, types)):
    @strawberry.field
    def member_fcn(self) -> t:
            if i == 0:
                return random.random()

            elif i == 1:
                return random.randint(0, 100)

    query_dict[n] = member_fcn

Query = type("Query", (object,), query_dict)

schema = strawberry.Schema(Query)

graphql = GraphQL(schema)

app = Starlette(debug=True)
app.mount("/graphql", graphql)

I think you might be able to do this by passing your dynamic class to the strawberry.type function (use it as a function, not a decorator) before giving it to the Schema

@BryceBeagle
Thank you for your lightning fast response: I can confirm it is working to register the dynamic schemas. Attaches the code below.
import asyncio
import random

from strawberry.asgi import GraphQL
from starlette.applications import Starlette
import strawberry

query_dict = {}

names = ["random_float", "random_int"]
types = [float, int]

for i, (n, t) in enumerate(zip(names, types)):
    @strawberry.field
    def member_fcn(self) -> t:
            if i == 0:
                return random.random()

            elif i == 1:
                return random.randint(0, 100)

    query_dict[n] = member_fcn

Query = strawberry.type(type("Query", (object,), query_dict))

subscription_dict = {}

names = ["random_float", "random_int"]
types = [float, int]

for i, (n, t) in enumerate(zip(names, types)):
    @strawberry.subscription
    async def member_fcn() -> t:
        for _ in range(5):
            if i == 0:
                yield random.random()

            elif i == 1:
                yield random.randint(0, 100)

            await asyncio.sleep(0.5)

    subscription_dict[n] = member_fcn

Subscription = strawberry.type(type("Subscription", (object,), subscription_dict))

schema = strawberry.Schema(Query, subscription=Subscription)

graphql = GraphQL(schema)

app = Starlette(debug=True)
app.mount("/graphql", graphql)


Set up version 0.16

Sets up beta 0.16.0

bump version to 0.16.0.dev1
shuffle CORE_VERSION_MAP -> CORE_VERSION_MAP.last

add 0.16.0.dev1 Version map to CORE_VERSION_MAP

unfreeze CI platform versions back to latest

Codecov Report

Merging #1417 (576e23a) into main (0950f50) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1417   +/-   ##
=======================================
  Coverage   86.06%   86.06%
=======================================
  Files         201      201
  Lines       21062    21062
  Branches     2461     2461
=======================================
  Hits        18127    18127
  Misses       2333     2333
  Partials      602      602

Flag
Coverage Δ

py-unittests
86.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


TypeError when comparing objects without constructor

🐛 Bug Report
expect(Object.create(null)).toStrictEqual({});
// TypeError: Cannot read property 'name' of undefined

Hey @sirian, thanks for reporting. This appears to be fixed on latest:

#7005


Add common logical operators

I've got a feeling that this will make describing complex filters a lot easier.

I like it when it's easy to add things
:+1:


Chain icon needs to be unique for all the chains and wallets on chain /wallets dropdown

Steps to reproduce:
1.Open demo app
2.connect and sign in
3.Then check the chain and wallet icons
Actual result:
Chain icon and wallet icon is looking same for all the chains and wallets

Expected result:
Chain icon and wallet icons should be unique

https://github.com/getsafle/safle-keyless-js/assets/149378074/845d9953-c87a-43fe-939a-29d731f218fa
Issue is fixed now

https://github.com/getsafle/safle-keyless-js/assets/149378074/85ca927b-c17b-4bdb-9586-39f7b8ee9679
Issue if fixed now


add support for kernelSU

Currently it is not working on kernelsu, so please add support for kernelSU!

Hey, what is your setup? Are you using ZygiskNext with kernelSU? Are you able to run any other Zygisk based modules?

Hey, what is your setup? Are you using ZygiskNext with kernelSU? Are you able to run any other Zygisk based modules?

Yes, I'm using zygiskNext on kernelsu and yeh I'm able to use other zygiskNext based module and those are working fine. Only problem on your this module. Btw the problem is it is only transferring config.json.example file on /data/local/tmp/re.zyg.fri/ directory when i flash and reboot the device. While it is working when I'm on magisk

I have a guess based that only the config.json.example is in the directory.
The module is using the busybox of magisk to extract the gadgets. So I assume it can't find the busybox binary because it is on a different path.
Could you maybe download and try out the version here? I have no kernelsu device at hand currently to quickly test it.
https://github.com/lico-n/ZygiskFrida/actions/runs/8857846035

I have a guess based that only the config.json.example is in the directory.
The module is using the busybox of magisk to extract the gadgets. So I assume it can't find the busybox binary because it is on a different path.
Could you maybe download and try out the version here? I have no kernelsu device at hand currently to quickly test it.
https://github.com/lico-n/ZygiskFrida/actions/runs/8857846035

Yes, this worked. Thank you!


Update navicat-premium-essentials to version 12.0.7

Updated navicat-premium-essentials to version 12.0.7 and replaced sha256 checksum.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as 3639aa97f512cf938a7a3eeb99c2044a582451c1. Your contribution is still credited to you.


Request for more samples regarding "FieldFileTypeRenderer" to override fields

Category
[ ] Enhancement
[ ] Bug
[X ] Question
Version
Please specify what version of the library you are using: [ sp-dev-fx-controls-react v1.19.0  ]
If you are not using the latest release, please update and see if the issue is resolved before submitting an issue.
Question
It is possible that someone could create more samples regarding "FieldFileTypeRenderer" or the other fields  that is more clear on how to use this controls and how to override existing fields in Lists.
https://pnp.github.io/sp-dev-fx-controls-react/controls/fields/main/
Thank you for your attention

Hi @aaclage - the sample has been added to PnP Extensions Sample Gallery


[Update Snap] Push

Checklist
All items in the list below needs to be satisfied.

[ ] Is the summary of the change documented in this ticket?
[ ] Has a MetaMask Snaps team member reviewed whether the changes need to be vetted?
[ ] If there are changes that need to be vetted, attach a description and the relevant fixes/remediations to this issue.
[ ] The corresponding pull request in this repo has been merged.

This update includes:

A break in the switch statement used by the cronjob https://github.com/ethereum-push-notification-service/push-protocol-snaps/commit/25271a46262e0c5338c3e3374b26cf4f267e7abe
Some typo fixes and a parameter fix to the opt-in method: https://github.com/ethereum-push-notification-service/push-protocol-snaps/commit/373f33c8778814dbd991a36a63709e67d1ab9de5#diff-882b3d754bf3ea4009d454b04d75ab6c6a36b0059cda92fbd3761437dc433b95

New version is 1.0.9


format for windmill.yml

Hi All,
Do we have template to update values from windmill.yml
I would like to run the project in Docker container and wants to change hostname from <IP_ADDRESS> to <IP_ADDRESS> to get accessible outside container.

I found the solution. Closing issue. If anyone faced same let me know , I am happy to provide you solution

thanks @sbbagal13 !


feat(STONEINTG-869): e2e test of gitlab integration reporting

in this PR we implement happy-path of feature integration gilab reporting ensure that the build and integration pipelinerun are reported in the associated gitlab branch as we validate the status of pipelineruns succeeded as expected.
Signed-off-by: Kasem Alem<EMAIL_ADDRESS>Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
STONEINTG-869
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/retest

/test redhat-appstudio-e2e


Invoking DELETE endpoint for users returns method not allowed (405)

Even though the API is documented, it is not accessible.
This causes a failure in the core-api deleteAccount mutation.

are you sure the user's home directory is already empty?  If it is not empty, this error message is expected.

The home directory should not even exist as I'm pretty sure it was never created, so it should return 404. But even if it exists and is not empty it should not return 405. In that case it should probably return 422 or 400.
405 means the endpoint exists but the method (GET, POST, etc.) is not supported for the endpoint.

I will have a look. The suggestion of code 422 is also a good one. I will also change it in case the dir is not empty.

Come to think about it, in the non-empty case, 403 (not allowed/forbidden) might also be acceptable.
In the non-existing case I would still expect it to return 404.

The fix is provided in PR #13


Hide from Alt + Tab

I'd like to know if there is any way to hide the app from showing in alt tab when it's minimized in the system tray, i find it pretty annoying that it's there all the time.
I like the app, but i just want it to run in the background, not to see it every time i Alt + Tab.
Thanks.

Good suggestion...

is it "easily" doable?
Also, is there a way to change the incoming message color (while keeping the animation) other than just editing it frame by frame and key by key? I only want to make it the same colour as when the app connects to discord (discord "blue") but changing it one by one seems like a lot of work hahahaha
Thanks!

After hand painting my N-th fire animation, I created a whole toolset for quickly making animations.
Take a look at the first videos in the guide. You can make some epic animations in a few minutes.
https://chroma.razer.com/ChromaGuide/

Awesome, i'll take a look at it. Thanks.
What about the main subject of the issue? is it doable?

Yes it's totally doable. I can add it to the backlog. I can't give any sort of ETA for this.

It would be great if you do that, i'll stay tuned to see when it's implemented. Thanks!


Brand expression – Type token

Sync with Dragos to establish the new type token and changes to any existing type tokens

[x] meeting has occurred
[x] Agreement between Dragos, Jean, Olivia
[ ] Issues opened on Carbon repo to update tokens
[ ] Open issues to update design kits

Meeting scheduled for 5/11 to review implications of type token change


Setup automated end to end tests for a Forseti on GKE Deployment

[ ] Run all Forseti end to end tests on a  Forseti on GKE deployment.
[ ] Add new Forseti on GKE stage to Travis
[ ] Please add sub tasks for this effort.

Will not complete at this time.


Additional language for conformance statement

Proposed additional conformance language to support future certification work (cribbed from https://tools.ietf.org/html/rfc2616).
Closes #373
Signed-off-by: Stephen R. Walli<EMAIL_ADDRESS>

@vbatts @crosbymichael PTAL

LGTM except for https://github.com/opencontainers/runtime-spec/pull/374#discussion_r58956137

LGTM save Jon's comment
On Thu, Apr 7, 2016, 18:51 Vish Kannan<EMAIL_ADDRESS>wrote:

LGTM except for #374 (comment)
https://github.com/opencontainers/runtime-spec/pull/374#discussion_r58956137
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/opencontainers/runtime-spec/pull/374#issuecomment-207126705

Fixed.


Querydsl collections leftjoin

Hi All,
I managed to successfully use querydsl for collections using normal joins and left joins when there is a collection linked to an object. However I didn't managed to do the other way round.
This is my case:
Person Class:
@QueryEntity
public class Person {
    private Integer id;
    private String firstName;
    private String lastName;
    private List<Address> addresses = new ArrayList<>();

    public Person() {
    }

    public Person(Integer id, String firstName, String lastName) {
        this.id = id;
        this.firstName = firstName;
        this.lastName = lastName;
    }

    // getters and setters
    ...
}

Address Class:
@QueryEntity
public class Address {
    private Integer id;
    private String street1;
    private String street2;
    private String city;
    private Person person;

    public Address() {
    }
    public Address(Integer id, String street1, String street2, String city, Person person) {
        this.id = id;
        this.street1 = street1;
        this.street2 = street2;
        this.city = city;
        this.person = person;
    }

    // getters and setters
    ...
}

Main Application:
public class App {
    private static Logger l = LoggerFactory.getLogger(App.class);
    private static List<Person> persons;
    private static List<Address> addresses;

    public static void main(String[] args) {
        initData();

        QPerson qperson = QPerson.person;
        QAddress qaddress = new QAddress("address");
        for (Tuple o : from(qperson, persons)
                .leftJoin(qperson.addresses, qaddress)
                .select(qperson, qaddress)
                .fetch()) {
            l.info("------------------> {} - {}",
                o.get(qperson).getFirstName(),
                o.get(qaddress) == null ? null : o.get(qaddress).getStreet1());
        }
    }

    private static void initData() {
        Person p1 = new Person(1, "Name1", "Surname1");
        Person p2 = new Person(2, "Name2", "Surname2");
        Person p3 = new Person(3, "Name3", "Surname3");
        Person p4 = new Person(4, "Name4", "Surname4");
        Person p5 = new Person(5, "Name5", "Surname5");
        Person p6 = new Person(6, "Name6", "Surname6");

        persons = Arrays.asList(p1, p2, p3, p4, p5, p6);

        Address a1 = new Address(1, "Street11", "Street21", "City1", p1);
        Address a2 = new Address(2, "Street12", "Street22", "City2", p2);

        p1.getAddresses().add(a1);
        p2.getAddresses().add(a2);

        addresses = Arrays.asList(a1, a2);
        System.out.println();
    }
}

if I replace the above query with the below i get all persons with and without an address:
from(qperson, persons).leftJoin(qperson.addresses, qaddress).select(qperson, qaddress).fetch()
How can I create a query so that I can retrieve all addresses that have a person assigned to them and not?
Thank you all for the help.
QueryDSLTest.zip

How can I create a query so that I can retrieve all addresses that have a person assigned to them and not?

If you want them in the same format, then query.from(qaddress, addresses).select(qaddress, qaddress.person).fetch().
Or did you mean something else?

Hi Timo,
yes, that is exactly what I needed. The documentation for querydsl doesn't help much with examples.
Thanks a lot for the quick reply and help.


Split crate to two

This crate are great but it consist two functionalities: fat file system interface and implementation and sd/mcc card high level driver. I think we need to split this crate to two - one for fat fs and one for sd card abstraction. Thanks.

This crate is intended to allow you to read/write files on a FAT formatted SD card on your Rust Embedded device, as easily as using the SdFat Arduino library.

Can you list the advantages that splitting the crate would bring? As stated in the README, the primary goal is simplicity.

I make library clear: you can extend and update fat fs crate without hw depends and you can improve hw support without changes in fat fs. So crate is staied commonly easy for use - you can create default feature flag for use another hw support, or you can support hw extension as in serilalization in serde.

OK, so if embedded-sdmmc was left as a simple, high-level crate, I'm fine with the FAT implementation being booted off into fat-rs or something, where it can be consumed by other applications / crates without all the SD stuff coming along too.

Likewise the SD over SPI protocol implementation, and any future SD over SD Bus implementation - they can be in other crates, as long as this crate brings it all together is a nice easy to use format.

I'd like to continue this discussion but instead of splitting it up, let's create a feature for enabling the fs for fat32 & fat16.
This will allow people to still depend on the crate for raw access, like for using it with e.g. littlefs2

But if you don't use the FAT32 code, it all gets dead-code eliminated, doesn't it?

I'm also interested in using the FAT32 part of this crate without the SD card part. In particular I'm looking at using it on top of a VirtIO block device using https://docs.rs/virtio-drivers/latest/virtio_drivers/device/blk/struct.VirtIOBlk.html. VirtIO also uses 512 byte sectors so that seems reasonable.
How would you feel about moving the BlockDevice trait into embedded-io? It seems like a useful abstraction that would make sense for other filesystem implementations too. There is also the block-device crate, but it looks like it hasn't been updated in a while or used very widely, so I think embedded-io makes more sense, if they will accept it.

I wouldn't want to drop the BlockDevice trait but I'm happy to see a PR that implements it for any T: embedded::io::Read + Write + Seek if that's useful to you.
You could also implement those traits on our File objects. Which I think would let you mount a disk, and then mount a disk image on that disk.

As an aside I wrote a VirtIO vring implementation in Rust from scratch in 2018 to do inter core RPC on a Beagleboard X15. Glad there's crate for it now! It was a doozy.
https://github.com/cambridgeconsultants/rust-beagleboardx15-demo/blob/master/bare-metal/ipu-demo/vring/src/lib.rs

Edit: I misread. You want to add a BlockDevice trait TO embedded-io. I'm fine with that.

I'd like to add a BlockDevice trait to embedded-io (or possibly embedded-storage), and then use that here in embedded-sdmmc-rs in place of the trait you currently have in this crate. I then plan to implement the new BlockDevice trait in other crates, to allow them to be composed with this crate in either direction.

Sounds fine to me.

I sent https://github.com/rust-embedded-community/embedded-storage/pull/59 to add the trait to the embedded-storage crate.


Experimental preference breaks site

This experimental preference breaks the left hand navigation bar on the Google Cloud documentation page.
https://github.com/yokoffing/Betterfox/blob/09dd87a3abcb15a88798941e5ed74e4aa593108c/user.js#L56

Very easy to reproduce. Great find!

Not sure if I'm imagining things, or the browser feels a tiny bit more performant with this off.

No worries. I've removed it in the next release.


Arrays in dynamic objects with different properties

Thank you for this excellent and simple rules engine. Implementing this with a complex JSON where the JSON can be highly dynamic for a combination of filters and found the following:
This occurs If the JSON has an array and each object in the array is slightly different.
Input parameter is (ExpandoObject, showing JSON for it)
{
	"lines": [{
			"property1": "value",
			"property2": "value"
		},
		{
			"property1": "value",
			"property2": "value",
			"property3": "new value"
		}
	]
}

The input parameter passed to the rule for execution has the list of 'lines' in which for index 1 property3 does not exists
i.e.
_input1.lines[1].property3 does not exists
If the input parameter (ExpandoObject, showing JSON for it)
{
	"lines": [{
			"property1": "value",
			"property2": "value",
			"property3": "value"
		},
		{
			"property1": "value",
			"property2": "value"
		}
	]
}

The input parameter passed to the rule for execution has the list of 'lines' in which for index 0 property3 exists, and is null for index 1
i.e.
_input1.lines[0].property3="value";
_input1.lines[1].property3=null;

If the input parameter (ExpandoObject, showing JSON for it)
{
	"lines": [{
			"property1": "value",
			"property2": "value",
			"property3": "value"
		},
		{
			"property1": "value",
			"property2": "value",
			"property3": "new value"
		}
	]
}

The input parameter passed to the rule for execution has the list of 'lines' in which for index 0 property3 exists, and  for index 1 has the correct value
i.e.
_input1.lines[0].property3="value";
_input1.lines[1].property3="new value";

Hi @macxdev, Thanks for raising this issue, It helped me discover a universal solution for such scenarios
For complex json scenarios, you can pass JObject instead of ExpandoObject.
It supports all access scenario and equality checks.
i.e
_input1.lines[0].property3="value";
_input1.lines[1].property3="new value";

works out of the box;
For advance access (calling a method, performing operations( +,-, etc)), you might need to cast the object.
Casting syntax in rulesEngine is different from regular c#
typename(<expression>)

e.g. string(input1.lines[0].property3)

``` As based conversion (value as string in regular c#
As(<expression>,typename)

e.g. As(input1.lines[0].property3,string)

It will take me sometime to document, usage of JObject over ExpandoObject. You can try it out and see if it

Thanks @abbasc52 for the response, I greatly appreciate it. I will give it a go tomorrow and report if I find anything. For the conversions, thank you and also thank you for adding the ability to add helper classes, the one I wrote I think should be able to handle it.

@abbasc52  thank you, confirming this is working well i.e. using JObject. The rules are also simpler. Thank you. As I have a fair few rules to check this on if I find any other issue will open a new one.
Thank you again for the response and the solution.


Demo Final is empty

Demo final is empty. There is no final content.

I see it here: https://github.com/DeborahK/Angular-ReactiveForms/tree/master/Demo-Final
Can you tell me what you see when you access that folder? Maybe screen shot it?

Hi Deborah,
I see it now. :)
Thank you for great content. You are  the best teacher ever!
Keep up the great work.


Elvish as an embedded scripting language?

I am considering using Elvish as an embedded scripting language in a project, and just wondered if you guys had any tips or thoughts on how you would do that, if it's feasible at all, etc.
I was originally going to use Bash, but due to the fact the internal modules I will be calling will return objects, not text, Bash will not work.
Then I thought about using Elvish. It has support for lists and maps, which I figure I can use to create arbitrary 'objects', and is a shell scripting language.
My questions/concerns are:

can I add user defined types/functions such that the Elvish interpreter will recognize them, much like you can in otto and gopher-lua?
what should I remove that is unneeded in a embedded scripting scenario? Things like the file browser, package manager don't seem useful in my use case and would just bloat the compiled binary.
can I parse input scripts/code server side, generate and AST and serialize and send it over the wire to a client which would deserialize the AST and execute it with the Elvish interpreter?

In theory, Elvish is already embeddable by the virtue of having a modular design; in your Go code you can use github.com/elves/elvish/parse to parse and github.com/elves/elvish/eval to evaluate Elvish code.
Elvish functions and elvish values are Go functions and values of particular shapes. In fact, the line editor component (github.com/elves/elvish/edit, although a better, but incomplete version is github.com/elves/elvish/newedit) is written exactly as some kind of addon to the core.
The AST is probably serializable, but I have not checked.
In principle, you should be able to just refer to the godoc for the parse and eval packages (https://godoc.elv.sh/parse, https://godoc.elv.sh/eval) as well as the source code of the newedit package to see how Elvish can be embedded. However, the APIs are not very well documented, neither are they stable. Neither is the Elvish language stable.
Nonetheless, your request is a very reasonable one, and ensuring that Elvish is embeddable is beneficial for making sure that the internal architecture of Elvish is modular enough, with good internal APIs. Still, since the stability of internal API as well as the language will only become a goal after the 1.0 release, I encourage you to give it a try, but beware of all the caveats mentioned above.

Perfect, from what I've read of the API from the godoc your answer is what I expected. One additional requirement I forgot to mention is that I would like to parse and compile the input code/script before sending and executing it on the client, but as you said that shouldn't be a problem.
I totally understand that Elvish isn't stable, and can accept that for this project. Just out of curiosity though, do you have any idea/timeline when Elvish will hit v1.0?

I have written my thoughts in #815.

@capnspacehook Compiling the Elvish code and sending the compiled code over wire is much harder than sending the AST, as Elvish's compiler actually compiles the AST into Go closures, which are inherently unserializable. You can only use the compiler to do the checking, and re-compile it on the client though.

Hmm ok, that's really good to know. I will have to that then, compile to check on the server, send, recompile and execute on the client.

So it seems the result of parse.AsChunk, parse.Chunk is not serializable, as it has unexported fields that also contain unexported fields etc...

So after taking a deep dive into the source of the parse and eval packages, I've been able to understand and tweak what I needed to to make Elvish work as I need it to. There are some things I changed in my private fork that are specific to my use case, but there are other changes I had to make that are more general I think. So I will keep this issue open to discuss issues I come across when embedding elvish that may affect other users.
That being said, I can't express enough just how well written and designed Elvish is, it's a pleasure to work with, and it's syntax is very intuitive and simple. Thanks again for such a great project.

Hi - really glad that you like the design!
I would love to learn from your changes. - I try to write the code in a general way, but since all of the packages are really only used in the Elvish program, it's almost unavoidable that some parts get unnecessarily specific. In general, I feel understanding more use cases can be quite helpful for improving the internal design.

No problem, yeah the intuitive syntax and the ability to use lists and maps in a shell scripting context is great.
Yeah there's a few things I know looking back that I changed that could benefit others:

I created an exported wrapper for eval.addBuiltinFns(), if people are embedding Elvish, a common use case is to add custom builtins/functions to the interpreter.
I created an exported wrapper for parse.node.setSourceText(), when serializing an Elvish parse tree (parse.Chunk) the sourceText field is needed for tilde nodes only I believe.

There are more changes I made, but they were specific to my use case and would not be good changes to make to Elvish generally.


chore(main): release base 0.0.14

:robot: I have created a release beep boop
0.0.14 (2024-10-12)
Bug Fixes

🐛 fix project build 11 (#101) (d81d79f)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

base-v0.0.14
:sunflower:


Exit code 0 when JSON is invalid

This may be a platform issue, as I'm (unfortunately) on Windows for debugging.
We're trying to incorporate the validator into an existing workflow, and it'd be helpful to parse the process exit code as being zero/nonzero to determine if the validation was successful. Would it be possible to update the exit code to be something other than 0 if validation failed, or does that risk breaking too much?
If memory serves, this is something I was able to rely on with xmllint in the past, so it should hopefully be in convention for validation tools, but don't quote me on that...
(also, as part of this, would be nice to have the "invalid _____" diag written to stderr instead of stdout, but that's far less important to me)

Currently, a 0 exit code is always returned. But, it sounds like it would be useful for non-zero codes to be returned when validation fails, so I will discuss with the team about adding this to the validator.

That is very close to what I was trying, but I introduced a bug along the way. :-(
This is the function I got to work:
`
const exec = util.promisify(require('child_process').exec);
async function validateFile(path, fileType, outputPath) {
const { stdout, stderr, err } = await exec('cms-mrf-validator validate ' + path + ' v1.0.0 -t ' + fileType + ' -o ' + outputPath );
if (err) {
console.log(err);
return;
}
}`
Thanks!!

@ahwitz I've opened PR #62 that I think will help with this. If you have time, please take a look at it and see if it looks like the changes to exit codes meet your expectations.

@mint-thompson - looks great, and utils.ts:110-ish is exactly what we were looking for. Only because I saw those lines: there may be some people out there who are looking for stderr output instead of/in addition to error codes, and making 108/109 a console.error instead of console.log might help, but the exitCode = 1 is more than enough for us. Thanks a ton!


adapting ddpg agent for the Atari environment

I'd like to adapt the ddpg agent for environments other than Pendulum-v0. One problem is that the environment action is Discrete(6) for the Atari environment but a numpy array for the Pendulum-v0 environment. Is there a way to avoid statements which use the shape of the action variable?
ie
File "/lib/python2.7/site-packages/keras_rl-0.2.0rc1-py2.7.egg/rl/agents/ddpg.py", line 222, in select_action
assert noise.shape == action.shape

You could reuse some of the code from this PR: https://github.com/openai/gym/pull/451
The code flattens arbitrary spaces into single vectors.
You would still have to write custom code for searching, because searching a discreet space is different than searching a continuous space. However, you should be able to use that PR to write the same model for any spaces.
Cheers,
Ben


Incorrect sample code

There are three things wrong with the sample code here:

The default buffer size is 2GB, not 64KB. There's no need to set it explicitly in most cases.
HttpClient is meant to be created as a single instance and shared, not created for each request (or for each click of the button in this case).
The line that calls downloadTasksQuery.ToArray() is unnecessary. Once you start awaiting tasks, they will start.

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

ID: 702427b0-0bcc-1152-75a5-c909717723c0
Version Independent ID: 0dbb92ca-4166-ceaf-1083-1280703a9c15
Content: How to: Extend the async Walkthrough by Using Task.WhenAll (C#)
Content Source: docs/csharp/programming-guide/concepts/async/how-to-extend-the-async-walkthrough-by-using-task-whenall.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for writing this up @mj1856
The async area will be updated shortly. This is helpful to address these concerns.


[KYUUBI #3406] [Subtask] [Doc] Add PySpark client docs

Why are the changes needed?

close #3406.
Add PySpark client docs.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #3407 (692197e) into master (b3ecaef) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3407      +/-   ##
============================================
- Coverage     51.47%   51.45%   -0.02%
  Complexity       13       13
============================================
  Files           480      480
  Lines         26664    26664
  Branches       3728     3728
============================================
- Hits          13724    13719       -5
- Misses        11598    11601       +3
- Partials       1342     1344       +2

Impacted Files
Coverage Δ

...pache/kyuubi/engine/YarnApplicationOperation.scala
66.66% <0.00%> (-1.86%)
:arrow_down:

...ache/kyuubi/operation/KyuubiOperationManager.scala
80.82% <0.00%> (-1.37%)
:arrow_down:

...ain/scala/org/apache/kyuubi/engine/EngineRef.scala
72.26% <0.00%> (-0.85%)
:arrow_down:

...yuubi/server/metadata/jdbc/JDBCMetadataStore.scala
89.27% <0.00%> (-0.70%)
:arrow_down:

...a/org/apache/kyuubi/service/TFrontendService.scala
91.17% <0.00%> (-0.30%)
:arrow_down:

...g/apache/kyuubi/operation/BatchJobSubmission.scala
74.64% <0.00%> (ø)

...n/scala/org/apache/kyuubi/engine/ProcBuilder.scala
83.22% <0.00%> (+0.62%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks for adding this document, have some high-level thoughts.
We should not narrow the Kyuubi JDBC data source use cases into PySpark, it's also suitable for spark-shell, spark-sql and the normal spark jar jobs, right? So, I think maybe we can split the doc into two parts, the 1st part is "How to use Kyuubi as a Spark JDBC data source", and the 2nd is "How to use PySpark to access Kyuubi JDBC data source".

Also, to unconfusing users, we should emphasize there are TWO Spark applications in such use architects, and the most benefit is security but not performance, the arch also suitable for spark-shell

Yes. But so far this docs is purposed for python user (like AI team and etc.) accessing to Kyuubi and it is put under /client/python rather than discussing all avaialble accessing way in Spark which could be enhanced in future docs solely for Spark under /client.  And they are not confusing with two spark jobs as discussed in first paragraph it is about connect to Kyuubi but not the any realted to Spark engine.

Thanks, merging to master/1.6


HT Cell Proliferation page

Complete a basic implementation of the HT Cell Proliferation page; pages/pdanalysis/htproliferation.py.
This page will implement some base functionality using the Thunor Core library to load and analyze high-throughput cell proliferation data. We can link to the Thunor Web application for users needing more advanced features and database support.

Thunor Web app: https://www.thunor.net/
Since it was developed by LoLab at Vandy (which no longer exists), I wonder if the web app is still being maintained or supported.

Thunor Core: https://github.com/alubbock/thunor

Hi Blake, hope you're well. Yes, trying to maintain Thunor Core and Web as time permits. Feel free to open issues if you find anything amiss or have requests, I'll try to take a look. Cheers, Alex

Since Thunor Web is still active and supported, I think I'll just add an external tools section and point users to it for HT Cell Proliferation analysis rather than trying to implement a subset of features in the Aurora app. Then, I can focus more on implementing the compartmental modeling and non-compartmental analysis features.

Addressed in PR https://github.com/Borealis-BioModeling/aurora-pkpd/pull/20


Feature/160/conditional settings

Closes #160

[x] update Changelog
[x] update Documentation in README
[x] add ability to pass JS functions in the preferences object to the renderer
[x] add ability to programmatically hide fields
[x] add ability to programmatically hide groups
[x] add ability to programmatically hide sections

Can be done with a new property on field, group or section items: hideFunction: (preferences) => { return true; }

Nice work on this


How do I enable front camera to scan barcode?

There is no property exposed to set the camera facing barcode/qrcode. Is there any way it can be done?

Did you find any solutions?


404 And System.ArgumentNullException Downloading System.Runtime.Extensions in dnu restore

After upgrading to beta5 I ran into an issue with dnu restore encountering a 404 when pulling in the package System.Runtime.Extensions v4.0.10-beta-22828. I didn't pull in this package manually, it's a dependency for something else. I'm not sure whether the issue was related to beta5 or if I just coincidentally noticed it then as switching the packages back to beta4 and using the beta4 dnvm does not fix the issue.
Here is a gist with the log, my project.json file and my NuGet.config file:
https://gist.github.com/DylanDonkersgoed/caca3ab545c9a4613fe0
The last dependency is a local class library which restores without issue.

Try dnu restore --no-cache from the command line. Like like your package cache is corrupted. BTW this should be fixed in later releases.

Thank you for your response @davidfowl. I did try that a few times and it had no effect. I forgot to comment here but I did actually resolve the issue. It appeared to be related to a breaking change I missed between beta4 and beta5, specifically that the Microsoft.Framework.ConfigurationModel packages were now the Microsoft.Framework.Configuration packages.
I'm not sure why it still occurred when I switched back to beta4, perhaps this was related to a corrupted package cache. I can't remember if I did a full dnu restore --no-cache after switching back to beta4.


2023.2/2024.1: disable python deprecation warnings (pt. 2)

Make it possible to set the environment variable PYTHONWARNINGS for all containers managed with the kolla_container Ansible module. Set to ignore::DeprecationWarning by default to disable all deprecation warnings.
Related to osism/issues#641

The current patch will not work. The /opt/configuration/environments/kolla/configuration.yml file is not available on the nodes itself.


Mention Stack-Templatizer?

Heya, I wrote a small application the other day for turning a folder into a stack template:
https://github.com/prikhi/stack-templatizer
Essentially you create the folders and files for a template, run the application, and it'll build the hsfiles template for you. So you can use your editor's linting, autoformatting, etc when building out the template.
I'm wondering if you'd like to stick a link to the app in your readme or something?

I added something to README.md under 'related initatives'.


Update reference about importing npm packages

Now that Ember Auto Import is a default, we can say that 'it just works'
(I used Highcharts as the example because I've used it before and I know it works, but can be changed to any other example, or can remove the example too)

Ah good idea, updated with suggestion!


Bungee-side permissionsEX

Hello, please? :D It's would be nice

You mean something like this? https://github.com/weaondara/BungeePerms
If that is what your talking about, i can look into implementing the bungee side permissionsEX

Yes yes! And I think mysql support is needed, then all perms will work from bungee and spigot :3
P.S. Sorry im bad at english :+1:

PEX2.0 is implementation-abstract -- there are currently spigot and sponge versions. a bungee version could be added by anybody interested.

@zml2008 I'll send a push once i get some of the bungee side working :)

Awesome! Would be a useful addition to have.
I'll also need to rethink how cache invalidations will be synced across active instances in 2.0. Currently I'm thinking about replacing the current NetEvents-based system with one that is backend-specific -- meaning each backend handles its own update notifications -- so file will monitor the permissions file for modifications, sql will be notified about changes to the database (hopefully, I'm not sure about the best way to do this with the database)

@zml2008 the only plugin that comes close to matching pex with bungee support is BungeePerms (https://github.com/weaondara/BungeePerms), but the owner of that project seems to be inactive. Spigot has a few wiki articles on bungeecord development (https://www.spigotmc.org/wiki/bungeecord/) if you want to look through them.
On the Bukkit side of things, we will probably need to add a config option that enables bungee support. Sense bungeecord has a plugin channel option, for communicating between servers, all we would need to do is use that ideally. If you have skype, feel free to pm me, and i'll message you my skype, because that would be easier for communication.

I don't use skype -- but PEX is on IRC, #permissionsex on irc.esper.net, and I hang around there, so poke me there to talk.


resize chart on update

fixes #1468
(see also https://www.chartjs.org/docs/latest/developers/api.html)

Does not work reliably.


Add media query and provide appropriate view: landscape (desktop) or portrait (mobile)

I think our default view is great for mobile portrait, but not great for desktop. an easy fix is clipping the viewbox for desktop, and letting it scale.
So "0 0 500 700" becomes "0 0 500 450" on desktop...
also, adjusting the fonts when making this switch would be good.

I can do this but I think I need to work with someone as to how we want the gages to look. They get cut off if I change the viewBox to the above.

Mary, I think a better way to get it is to load/inject the svg to the DOM and choose from two svg versions to do this. Possible?
That way we can get the best layout for each and also filter some gages out of the mobile view

See ajax injection part of https://zengenti.com/en-us/blog/authors/jasonalvis/intro-to-front-end-svgs.aspx

Closed by PR #84 and PR #85


Implementing Different techniques for image filtering

[1]  Sobel-x
[2]  Sobel-y
[3]  gaussian
[4]  bilateral

[1]  Sobel-x
[2]  Sobel-y
[3]  gaussian
[4]  bilateral

I am GSSoC'21 participant and I want to work on this issue.
Kindly assign this to me. @geekquad


Unknown plugin "module-resolver"

I'm getting this error:
.../node_modules/react-vis/dist/index.js: Unknown plugin "module-resolver" specified in
".../node_modules/react-vis/package.json" at 0

Versions:
npm: 5.5.1
react-vis: 1.8.0
react: 16.2.0
parcel-bundler: 1.2.0

Hi!
Do you have a more complete stacktrace you could share on pastebin maybe? By looking at the bundled index.js I don't see any reference to this. Not sure if parcel-related?

@balthazar

@balthazar That exact error was thrown when i copied over the example from here.

Are you using aliases or links?

@balthazar not to my knowledge.

And babel-plugin-module-resolver is not installed in your dependency tree?

Can you try installing it as a temporary workaround? We might want to switch it to a core dep instead of a dev one, weirdly we didn't got the issue before.

@balthazar I installed it as a dep, and then i get this:

@balthazar  And adding that dep gives me the same error but for stage-0. I'm guessing it will keep going...

Looks like because it's seeing these in the babel config of the package it automatically requires them, even if the dist is already built and shouldn't require them. Can you instead remove this prop from the package and see how that goes?

@balthazar Ohhh... if that's the case then this might actually be a parcel error. I had a discussion over there about just that earlier today. https://github.com/parcel-bundler/parcel/issues/351

we will close this for now

@Olian04 Were you able to resolve this issue?  I am running into the same issue with webpack, and am not having any luck...

@mathewleland I wasn't. I decided not to use react-vis

I got the same error
Fixed it with manually installing babel-plugin-module-resolver as dev dependency

https://github.com/uber/react-vis/blob/master/package.json#L65 the dependency is already in the package.json. Have you tried installing the dependencies using yarn instead of npm?

@balthazar Still getting the same issue


Unify the commands operator-sdk add api  and operator-sdk add controller

Feature Request
Is your feature request related to a problem? Please describe.
Lead and make easier the understatement of the concepts for developers built the operator projects. We can find many projects where we have many CR/CRDs using the same controller and/or not representing each one an object.
My current understanding is that an operator project is designed to have resources where each type of resource(CR/CRD) has its own controller and you can indeed manage any resource in any controller since the resources impl in your operator project works in exactly the same way that the API resources as "corev1.Service" for example.
So, when a CR/CRD is created/defined means a new resource/class(representation) with these attributes. So, if we use the same class to define all the different sorts of resources, we may be hurting concepts such as encapsulation, single resposanbilty principle and almost for sure cohesion that may cause unexpected sides effects such difficulty to read, maintain/improve and extend, to mention a few. Just to clarify my POV, it is the same as defining a user class which will have attributes related to other objects as fruits and furniture for example.
Describe the solution you'd like
Unify the commands operator-sdk add api  and operator-sdk add controller in order to make more clear the purpose and lead developers following the controller-runtime design.
E.g $ operator-sdk add --api-version=redhat-operator.example.com/v1alpha1 --kind=App will do all actions that is done currently in  operator-sdk add api --api-version=redhat-operator.example.com/v1alpha1 --kind=App + operator-sdk add controller --api-version=redhat-operator.example.com/v1alpha1 --kind=App which could be removed from the project in order of we just keep one command.

Hi, @shawn-hurley @jmrodri @hasbro17 wdyt?

@camilamacedo86 I can imagine there are use cases where you the controller to API (CRD) is not one to one. Maybe you want one controller to own two CRDS because otherwise they are managing some common resources.

Hi @tony-clarke-amdocs in my understand it goes implicitly against the design of the controller-runtime. Also, note that you can manage any object in any controller no matter if it is our own api and/or k8s, and/or openshift one.
See here: https://github.com/operator-framework/operator-sdk/issues/1383#issuecomment-489604367 as well.

@camilamacedo86 You're right that having a controller reconcile multiple CR types is an anti pattern.
However you would still want the ability to define a new API type in your project, without necessarily reconciling it as a primary type in your controller. For e.g the prometheus-operator's controller only reconciles the Prometheus resource but it still has the ServiceMonitor defined as the secondary API type which is watched, but is not the primary resource that the operator gets reconcile requests for. That is still a valid operator pattern.
Or if you already have an API type e.g Kind=AppService Group/Version=app.example.com/v1 defined. And you want to define v2 of the same Group and Kind. You don't need to add a controller in that case as well.
So while your rationale is correct that the add api and add controller operations are most commonly performed together, that is not always the case.
So even if we replace the two commands with a single command of add api, we will still need to keep around a flag e.g --controller=true/false to dictate whether we want a controller scaffolded with that API or not.
$ operator-sdk add api --api-version=app.example.com/v1alpha1 --kind=AppService --controller=true

So I don't know if there is much to gain from replacing the add controller subcommand with an optional flag --controller flag if users still have to distinguish when and when not to scaffold a controller. Both are equivalent UX wise, in my opinion.

Hi @hasbro17,
My goal with this RFE is we make the design implicit for its users and lead them to use it in the best way as possible automatically.
Wdyt over we resolve the v2 scenario programmatically? I mean before the unified command creates the controller we check if the kind has already a controller created for it? Or what about doing as you suggested by using a flag but just when the controller should not be created? I mean, by default the controller be always created unless we use something like --no-controller or  --controller=false

Closing this as we're not considering UX changes before we explore the Kubebuilder integration. All of the above may come about as a result of that integration.
https://github.com/kubernetes-sigs/kubebuilder/blob/master/designs/integrating-kubebuilder-and-osdk.md
#1955


Tutorial Page btp-app-kyma-prepare-dev-environment.md Issue. PROD

Tutorial issue found: https://github.com/sap-tutorials/Tutorials/blob/master/tutorials/btp-app-kyma-prepare-dev-environment/btp-app-kyma-prepare-dev-environment.md contains invalid tags. Even though your tutorial was created, the invalid tags listed below were disregarded. Please double-check the following tags:

software-product>sap-btp-kyma-runtime

Affected server: PROD

fixed yesterday


Updating put_synonyms api specification

With the recent changes, put_synonmys can now support both list and object. Updating he specification to reflect the change.

@pquentin Does this spec change need to be backported?

Good point! I applied the backport 8.14 and backport 8.15 labels to do so. Thank you.


Specgloss test set doesn't have a fallback

Set a metallicRough with a fallback that looks definitely like specgloss isn't working. Like a red X.

Merged #269


How to use for image cloud recognition

Hi
I need to detect image target on cloud. Please guide me about it.
Thank You

Hi,
This sample can not use cloud recognition now.
You need change VuforiaManager for cloud recognition.
You can reference the vuforia portal.
https://library.vuforia.com/articles/Solution/How-To-Implement-Cloud-Recognition-using-the-Native-SDKs

Can we just implement their code into your VuforiaManager.mm class?
How would I call it / use it from viewController?

Hi there,
I have found a way to use your code plus some of my own to get metadata from cloud recognition. If you would like to add my code to your repo, let me know :)

@byroncoetsee
Had you been able to use cloud recognition?
Please give me pull request if you can.

Hi
did you have any luck regarding this issue ?

@byroncoetsee's pull request #17

@yshrkt, unfortunately, your link from above is not working:
https://library.vuforia.com/articles/Solution/How-To-Implement-Cloud-Recognition-using-the-Native-SDKs
What is required to get cloud recognition working on Swift? I am very bad with Obj-C
Thank you for your work yshrkt! It helped me so much to get started with AR.

@dexterslabor
Hi, You need to handle TargetFinder and TargetSearchResult for working with cloud recognition.
PR #17 seem to include a lot of unnecessary changes, so I can't approve it...
New link is below.
https://library.vuforia.com/articles/Solution/How-To-Implement-Cloud-Reco.html

@yshrkt
Is there any chance you can provide a little hint to guide me how to do it? Which part of the file I will need to modify? Have been stuck for a whole day.. thank you very much!

@kikikiktai
Hi,
Did you fine the way to use cloud reco in swift? I have trouble making it too.
Thanks

@FritzHsiao At the end I used Obj-c++ to complete the cloud reco part, and I'm mostly referencing the Vuforia Examples. I suggest you to check out and try to study the example first, good luck!

@kikikiktai
Thanks for the hint. I use Vuforia Examples for my older projects written in Obj-c, just drag in to my project. Is it the same way in swift project with bridge header?

@yshrkt  @byroncoetsee  @aliaziada  @dexterslabor  anyone can found tutorial , sample code or any solution for cloud recognition implementation in swift? I have trouble making it too.


Reimplement Backend: Implement IMAP + Getting Emails With Python

Is your feature request related to a problem? Please describe.
Python seems to be more suitable for getting work done quickly, easier for an MVP
Describe the solution you'd like
Implement a FastAPI backend with Python + OAuth2.0 & IMAP for getting emails, avoiding using Gmail API.

Issues has been fixed with Go.


Gofmt -s doesn't work

How can I add the -s argument in gofmt?
I tried the below configuration but it doesn't work.
{
  "Fmt": {
    "format_on_save": true,
    "rules": [
      {
        "selector": "source.go",
        "cmd": ["gofmt", "-s"],
      },
    ],
  },
}

is seems that this did the trick:
{
    "format_on_save": true,
    "rules": [
      {
        "selector": "source.go",
        "cmd": ["gofmt", "-s"],
      },
    ],
}


Making IO Stats computation optional

The newly introduced stats in the PR #1702 and #117
are currently computed all time the irrespective of whether or not its needed. Since it is in a fairly hot code path, it could affect the performance when these stats are not needed. Hence, this PR aims to hide those stats computation behind a flag which controls the same.

And rebase over commit 720440036d67c74b602d6b13fafed3ab36ef008d.

Rebased @Thejas-bhat 's changes over tip of master.


Display LN describtion

Is your feature request related to a problem? Please describe.
As a user of OpenSCD I want to show the LN describtion in the IED browser
So I can understand the LN better
Describe the solution you'd like
An edit button on the LN's in the IED browser:

And an dialog to show and edit the describtion.
Requirements
Show and edit LN description fields
Additional information
desc is part of the SCL XSD's

Test Files
If possible provide a file that can be used to test the feature and explain what is the outcome of the test with the test file

@Sander3003 Sure I will work on it.

Is your feature request related to a problem? Please describe.
As a user of OpenSCD I want to show the LN describtion in the IED browser
So, it gives a better understanding about the LNode.
Describe the solution you'd like
At the moment it is possible to see all the necessary information of a Logical Node in the Substation plug-in but the LN description is still missing in that Edit LNode wizard.
To reach out this dialog box, the desired LNode has to be selected and then by clicking on the Edit icon, this wizard will be appeared. See below in the picture:

Currently, It is not possible to see the same information in the IED plug-in. To have this information and adding the LN description, an edit button needs to be added for the LNodes in the IED browser. An edit button on the LN's in the IED browser can be added as below:

Attribute
Required or Optional

desc
optional

iedName
optional

ldInst
optional

prefix
optional

lnClass
required

lnInst
optional

lnType
optional

After clicking on the Edit icon, the below Edit Logical wizard will be apeared. Below

And an dialog to show and edit the describtion.

Hi you two. I would like to comment on this:

I am seeing two-story descriptions and find it very irritating. If the story description is not sufficient we can edit it and when it is hard to adopt I would open a new one and point from this one that it is handled in the new issue. For the reviewer, it is crucial to have a straight forward reference to review against.
The wizard that is see is for the element LNode as well as the table with the attributes. The element shown in the SCL is the element LN and I would add LN0 as well just as they are close code wise. Now it makes sense to add the description field in the wizard of all three of the element, but I would then split those up.

Agree @JakobVogelsang it is confunsing to create an new issues if the one is around the same topic.

@Sander3003 Jakob's comment is related to the scenario I added beneath this story. Using Jakob's feedback, I crafted a new narrative addressing the concerns raised in the comment.

Closed by https://github.com/openscd/open-scd/issues/1465


[Doc Enhancement][Update people picker]

Added a sample code

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/task-modules-and-cards/cards/people-picker.md
100
0
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit c326815:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/task-modules-and-cards/cards/people-picker.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Log out logic

Hi guys,
can you explain one thing.
I'de like to understand what i should make on server side(drf), when user log out on client side.
On client side i remove Athorization header from request, but what need to do on server side in django part. How to remove current access/refresh tokens that had recieved on client ? And where they are stored?

Hi @volartem, there is an ongoing discussion, see #28

Thanks


blackmagic: 1.6.1 -> 1.6.1-311-gfbf1963

I updated the version number to include the commit ID as upstream
apparently doesn't plan on making another stable release:
https://github.com/blacksphere/blackmagic/issues/486
This is my first nixpkgs contribution, so apologies if I've messed
anything up! I had to switch to a newer gcc-arm-embedded to get it
to compile properly.

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @pjones

cc @matthewbauer

Other than that, this looks good to me!

@GrahamcOfBorg build blackmagic

@thoughtpolice This is what's in the manual

If a package is not a release but a commit from a repository, then the version part of the name must be the date of that (fetched) commit. The date must be in "YYYY-MM-DD" format. Also append "unstable" to the name - e.g., "pkgname-unstable-2014-09-23".

https://nixos.org/nixpkgs/manual/#sec-package-naming

For consistency for the tree I've been trying to have version be unstable-YYYY-MM-DD since the rule hasn't been updated for pname.

Normally, I try to keep the latest stable version number included in the version string, as well as the number of commits since that tag, and the git hash, rather than using the date. Nix will look at version in order to determine if e.g. nix-env -u needs to upgrade a package. (Check out builtins.compareVersions for more.)

I'll have to check this again, but last time I discussed this with someone there wasn't an issue with nix-env and this versioning.

Ah, I see. I wasn't aware we actually had recommendations for this (personally I find dates a little less informative than the actual git-based string, and that's what I've been using for a long time, while being somewhat nicer for a user to tell -- but that's neither here nor there.) I retract my complaint, then!

Ah, I see. I wasn't aware we actually had recommendations for this (personally I find dates a little less informative than the actual git-based string, and that's what I've been using for a long time, while being somewhat nicer for a user to tell -- but that's neither here nor there.) I retract my complaint, then!

TBH we should change these recommendations to something a little bit better, IIRC all packages that use this versioning are ignored by repology.

Okay, I swapped the version back to the date format. I left out the -unstable from the name since upstream seems to consider the master branch to be stable and isn't planning on doing more versioned releases. Let me know if there's anything else I need to do to get this merged ^^

I left out the -unstable from the name since upstream seems to consider the master branch to be stable and isn't planning on doing more versioned releases.

unstable should be in the version, it's in the guideline if referenced.

Okay, I bumped the commit and added the unstable- prefix. For what it's worth, the version = "YYYY-MM-DD" form seems to dominate in nixpkgs, although there's probably a fair number of packages that use that versioning scheme for stable releases, and I personally think it makes the most sense when considering packages for  which a version from VCS isn't necessarily viewed as inherently unstable:
[emily@yukari:~/etc/nixos/extern/nixpkgs]$ rg 'version *= *"\d{4}-\d{1,2}-\d{1,2}"' | wc -l
876

[emily@yukari:~/etc/nixos/extern/nixpkgs]$ rg 'version *= *"\d{4}\.\d{1,2}\.\d{1,2}"' | wc -l
170

[emily@yukari:~/etc/nixos/extern/nixpkgs]$ rg 'version *= *"unstable-\d{4}-\d{1,2}-\d{1,2}"' | wc -l
127

Okay, I bumped the commit and added the unstable- prefix. For what it's worth, the version = "YYYY-MM-DD" form seems to dominate in nixpkgs, although there's probably a fair number of packages that use that versioning scheme for stable releases, and I personally think it makes the most sense when considering packages for which a version from VCS isn't necessarily viewed as inherently unstable:
[emily@yukari:~/etc/nixos/extern/nixpkgs]$ rg 'version *= *"\d{4}-\d{1,2}-\d{1,2}"' | wc -l
876

[emily@yukari:~/etc/nixos/extern/nixpkgs]$ rg 'version *= *"\d{4}\.\d{1,2}\.\d{1,2}"' | wc -l
170

[emily@yukari:~/etc/nixos/extern/nixpkgs]$ rg 'version *= *"unstable-\d{4}-\d{1,2}-\d{1,2}"' | wc -l
127

It's likely you'll find more entries in name for unstable along with the date in version, since pname just happened recently.

Thanks for contributing @emilazy.
Apologies on the little speed bump around version, I hope I explained everything properly.