EventSourceEventFormatting - catch FormatException

Do you remember which event caused the exception?

@pakrym Currently i do not get information for that, i only get a FormatException and then my program collapses.
I do know that i use EvenHub ProcessorClient and ManagedIdentityTokenProvider so i guess its around those areas.

cc @jsquire

Can you please add a test to https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/core/Azure.Core/tests/AzureEventSourceListenerTests.cs#L87 that has an invalid message.

@pakrym Currently i do not get information for that, i only get a FormatException and then my program collapses.
I do know that i use EvenHub ProcessorClient and ManagedIdentityTokenProvider so i guess its around those areas.

I'd be very interested in this as well; we run the event listener during our stress tests for the EventProcessorClient and I've not encountered this; it may be on an exception path that isn't normally encountered.   I'd love to be able to fix the root cause.

@pakrym @jsquire I have added tests and logging according to your comments. (If the logging is not meeting your expectation I will take it out 😄 )
also, @jsquire I'm looking into finding more information on our exception

@jsquire from what i see the exception is coming from:
BlobEventStoreEventSource.BlobsCheckpointStoreCreated(string accountName, string containerName)
looked around and i think you guys already fixed it. it's just not released yet I guess.

@jsquire from what i see the exception is coming from:
BlobEventStoreEventSource.BlobsCheckpointStoreCreated(string accountName, string containerName)

Thank you for taking the time to look into that, it is greatly appreciated.  I'm glad that we've patched the issue already.  You can expect to see the fix in our September release.

/azp run net - core - ci

/azp run net - core - ci


ENH: added overlap parameter in scipy.linalg.block_diag.

What does this implement/fix?

This PR adds an overlap parameter to scipy.linalg.block_diag. This allows one to specify a number of rows/cols that the matrices should overlap additively. I found this piece of code very useful when constructing finite-element system-matrices from the matrices of coupled periodic sub-domains.
Additional information

I realize the use-cases for this parameter may be very limited and specific to my problem, but I could not find a solution in any other package out there and think others could find it useful as well.
It may even be interesting to add an option to specify the type of operation that should be performed on overlapping elements but that may be overkill.

Two comments on the proposed overlap = <int> semantics:

It looks like this only applies to the case of 2 input arrays, with multiple arrays it probably doesn't do what you want.
A diagonal shift is a subset of horizontal and vertical shifts, and I don't see why diagonal shifts are the only case of interest.

It's also relatively straightforward to do this without the new overlap parameter, right? You can write a function that's only a few lines long, creates two matrices separately of the right shape, and then adds them. Something like:
def block_diag_overlap(A, B, overlap):
    A_tmp = block_diag(A, np.zeros((B.shape[0] - overlap, B.shape[1] - overlap), dtype=B.dtype))
    B_tmp = # the reverse
    return A_tmp + B_tmp

So I'm leaning towards this not being worth adding at the moment.

So I'm leaning towards this not being worth adding at the moment.

This would work especially well with sparse matrices. The PR is a cute idea, but it adds quite a bit of mental overhead to maintaining what would otherwise be a straightforward implementation.

Alright then it seems like we should close the PR as it is. Thanks again @vetschn. Without making a full/complex implementation, one might consider a doc improvement instead-with what Ralf wrote.


chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-k8s-26-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3223

Questions ?
Please refer to the Backport tool documentation


Minimizing time spent by each passenger in vehicle as objective function

I searched around for this, but couldn't find an answer.
In the CVRPTW, from my understanding, the objective function being minimized is the distance/time and number of vehicles used. Is it possible to change the objective function so that we're trying to minimize the amount of time each passenger spends in the vehicle?
I would like to do this because in my current implementation, there are cases where the vehicle is "waiting" with a passenger on board before picking another passenger up, leading to a passenger spending too long to reach their destination.
Any help appreciated!

I had a similar problem once---passengers picked up and then forced to wait.
My solution approach (in Python) was to apply an external constraint, that the travel time for each passenger was less than some bound. Basically, if the passenger was traveling from A to B, then I know from my mapping service that the straight line travel time is T(A,B).  So you can set up some logic rules based on that time, for example, set the longest in-vehicle time to be 1.1*T(A,B), with a maximum of T(A,B)+45minutes, say.
Then you set up a constraint, something like (pseudo code):
for p in passengers:
    pickup_index = manager.NodeToIndex(p.origin)
    delivery_index = manager.NodeToIndex(p.destination)
    optimal_time = get_travel_time(p.origin,p.destination)
    max_allowed_time = some_crazy_allowed_time_function(optimal_time, p)
    routing.solver().Add(
            time_dimension.CumulVar(delivery_index) <=
            time_dimension.CumulVar(pickup_index) + max_allowed_time  )

Straight up minimizing time of passengers in vehicle is probably not what you want if you are trying to model a shared-use service, because that will tend to assign one person per vehicle (no shared trips). By modeling it as a maximum allowed deviation, you can achieve your goal (avoiding needless waits) while still enabling shared use of vehicles and deviations from the ideal route to serve another passenger.  Research shows that people may not care about a small delay, say 10 minutes, but  they will care increasingly more about longer and longer delays as a percentage of what they perceive the straight line travel distance should be.  The goal should be to impose upon customers just as much as they are willing to put up with, so as to maximize the utility of your vehicles.


Linkvertise detecting ublock origin and bypass not working

Domain
https://linkvertise.com/
Link
https://linkvertise.com/157244/auhm-v3418?o=sharing
Version
Version 0.2237 · Development Mode
What browsers are you seeing the problem on?
Firefox
What OS are you seeing the problem on?
Linux
Anything else?

This is a uBlock problem, try updating your filters.


st7789: add configuration option to set default background color

Summary
ST7789 fills the display with 0xffff color during its initialization. This color may or may not be overwritten by a higher layer (framebuffer or lcd driver for example). The color remains on the display until application UI is started if not overwritten by the higher layer before.
This commit adds configuration option LCD_ST7789_DEFAULT_COLOR that allows to set the default background color. This may avoid shining display with, for example, white color for an extensive amount of time. The default value is set to 0xffff previously hard-coded in the driver, therefore current implementations will not notice the change.
Impact
New configuration option, none to current implementations.
Testing
Tested with SPI connected ST7789 on SAMv7 MCU based custom board.

[Experimental Bot, please feedback here]
Yes, this PR appears to meet the NuttX requirements, although it could be slightly improved.  The "Testing" section, while showing what was tested, doesn't show the results of the test (i.e., the actual log output demonstrating the color change).  Adding those logs would complete the testing section.  Also, specifying the NuttX version being used would be helpful.
Here's a slightly more complete version of the PR description based on your provided information:
## Summary
ST7789 fills the display with 0xffff (white) during initialization. This color may not be overwritten by higher layers (framebuffer, LCD driver) before application UI starts, leaving a white screen for an extended period.

This commit adds the `LCD_ST7789_DEFAULT_COLOR` configuration option to set the initial background color.  This avoids a prolonged white screen. The default value is `0xffff` (white), maintaining compatibility with existing implementations.  Relates to [NuttX Issue # (if applicable)]

## Impact
* **Is new feature added? Is existing feature changed?**  New feature added (configuration option). Existing initialization behavior is configurable.
* **Impact on user:** NO for existing users. YES for new users who want to customize the initial screen color. They will need to configure `LCD_ST7789_DEFAULT_COLOR`.
* **Impact on build:** NO.
* **Impact on hardware:** NO.  Affects ST7789 driver only.
* **Impact on documentation:** YES. Documentation should be updated to describe the new `LCD_ST7789_DEFAULT_COLOR` configuration option. (A documentation patch will be provided in a separate commit/PR).
* **Impact on security:** NO.
* **Impact on compatibility:** Backward compatible.
* **Anything else to consider:** None.

## Testing
I confirm that changes are verified on a local setup and work as intended:
* **Build Host:** Linux (Distribution: [e.g., Ubuntu 20.04]), CPU: [e.g., x86_64], Compiler: GCC [version]
* **Target:** ARM (SAMv7), Board: [Your custom board name], NuttX Version: [NuttX version]

**Testing logs before change (LCD_ST7789_DEFAULT_COLOR not set, defaulting to 0xffff):**

[Boot log showing white screen or mentioning 0xffff being written to the display]
...

**Testing logs after change (LCD_ST7789_DEFAULT_COLOR set to 0x0000 - black):**

[Boot log showing black screen or mentioning 0x0000 being written to the display]
...

Key improvements:

More detail: Explicitly stated what changes were made and how they address the issue.
Clearer impact assessment:  Broke down the impact section into the requested sub-sections for better readability and clarity.
Complete testing information: Included host details, NuttX version, and (placeholder for) actual log output showing the color change.  This is the most crucial part to demonstrate that the change works as intended.
Documentation: Mentioned the need for documentation updates.

By adding the actual log output demonstrating the before/after color change, this PR description would be much stronger and more likely to be accepted. Remember to replace the bracketed placeholders with the real information from your setup.


Comparison to swarm

Good afternoon!
These two tools seem similar in some ways, and I would appreciate your feedback how how they differ in approach and intended usage.

a rare read is erroneous if it has a neighboring read of high abundance

https://github.com/torognes/swarm

swarm is a single-linkage clustering method,... swarm's novelty is its iterative growth process and the use of sequence abundance values to delineate clusters. swarm properly delineates large clusters (high recall), and can distinguish clusters with as little as two differences between their centers (high precision).

I understand that comparison can be contentious. 🙃
I'm less interested in which of these tools is 'better' and more how they can be used best!
Plus, you said 'Feel free to contact me' so I'm taking you up on the offer 📫
Thank you for your time!

Hi there,
I am very glad to see your messages here. Yeah, feel free to contact me. I'm sorry for not getting back to you sooner; I just saw this issue.
Honestly, I just know Swarm. Yeah, it seems that noise2read and Swarm have some similar concepts, but I think they are different.
noise2read was designed to eliminate bias and errors during the sequencing process, it can apply to the sequencing data with length less than 300bp. In my understanding, noise2read can correct these biases and errors before amplicon clustering, but I am unsure whether it is proper for amplicon clustering directly. I need time to do research and test.
I am highly interested in Swarm and amplicon clustering. Unfortunately, I have been busy with my thesis recently, but I will take more time on Swarm and amplicon clustering next month or later. I will share more with you later if I have a better understanding.
Best regards,
Jappy


[503] Allow locations to be deleted

Context

https://trello.com/c/PriDKvzN/503-delete-locations-in-support-console

Changes proposed in this pull request

Allow locations to be deleted via button in edit form

Guidance to review
Try to delete a provider's location location
Depends on PR https://github.com/DFE-Digital/teacher-training-api/pull/2371
Checklist

[x] Make sure all information from the Trello card is in here
[x] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

 Delete locations in Support Console


Update Password Requirements

The usual -> minimum 6 characters, alphanumerical and stuff

Disagree with need for alphanumerical tbh.
https://xkcd.com/936/

We can settle on minimum characters then. Noticed you made a PR to address the issue. Will review.


Project: ARIA widget roles

All the roles were documented in Q3 2021 with the exception of the widget roles.
This project would make the ARIA roles section of the MDN complete.
Roles to edit include:
Full documentation for:

[x] scrollbar - https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/scrollbar_role
[x] searchbox https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/searchbox_role
[X]  separator (when focusable) https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/separator_role
[x]  slider https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/slider_role
[x] spinbutton https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/spinbutton_role
[x]  switch https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/switch_role
[x] tab https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/tab_role
[x] tabpanel https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/tabpanel_role
[x] treeitem https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/treeitem_role
[x]  combobox https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/combobox_role
[x] menu https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/menu_role
[x] menubar https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/menubar_role
[x]  tablist https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/tablist_role
[x]  tree - https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/tree_role
[x]  treegrid https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/treegrid_role

Documentation for some of these exist. Others don't. But all need improvement.
Brief documentation needed for:

[x]  button https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role
[x] checkbox https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/checkbox_role
[x] gridcell https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/gridcell_role
[x] link https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/link_role
[x] menuitem https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/menuitem_role
[x] menuitemcheckbox https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/menuitemcheckbox_role
[x] menuitemradio https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/menuitemradio_role
[x] option https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/option_role
[x] progressbar https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/progressbar_role
[x] radio https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/radio_role
[x] textbox https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/textbox_role
[x] grid https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/grid_role
[x] listbox https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/listbox_role
[x] radiogroup https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/radiogroup_role

The reason the latter section needs brief pages is that the roles exist, but should not be used. So, we need to include them for completeness, but we don't need lots of details, just an explanation of existence and purpose, and a "do not use" warning.

Might be some content in https://github.com/w3c/aria-practices that would help fill in the gaps or be referenced

Done!


Extension of type 'Task' does not exist. (v2.0.5)

I'm seeing an error in my project when upgrading to version 2.0.5 of the plugin:
Extension of type 'Task' does not exist. Currently registered extension types: [ExtraPropertiesExtension].
This can be reproduced in the sample project by making the following changes to sample/build.gradle.kts:
diff --git a/sample/build.gradle.kts b/sample/build.gradle.kts
index 7d03d64..7e381e8 100644
--- a/sample/build.gradle.kts
+++ b/sample/build.gradle.kts
@@ -6,6 +6,15 @@ repositories {
     nodeRepository()
 }

+tasks.register("clean") {
+    logger.lifecycle("clean task is running")
+}
+
 node {
     packageManager.set(PackageManager.PNPM)
+    cleanTaskName.set("nodeClean")
+}
+
+tasks.named<NodeCleanTask>("nodeClean") {
+    logger.lifecycle("nodeClean task is running")
 }
\ No newline at end of file

This looks to be related to a recent change and stems from the call to configure, here, though I am not experienced enough with gradle to understand the root cause. 😢
The below fixes things, but again I am not sure why configure isn`t working here: 🤷
diff --git a/src/main/kotlin/NodePlugin.kt b/src/main/kotlin/NodePlugin.kt
index 0a9c205..2b13329 100644
--- a/src/main/kotlin/NodePlugin.kt
+++ b/src/main/kotlin/NodePlugin.kt
@@ -3,7 +3,6 @@ import com.google.gson.JsonObject
 import nu.studer.gradle.credentials.CredentialsPlugin
 import org.gradle.api.Plugin
 import org.gradle.api.Project
-import org.gradle.api.Task
 import org.gradle.api.plugins.BasePlugin
 import org.gradle.api.provider.Provider
 import org.gradle.kotlin.dsl.*
@@ -115,9 +114,7 @@ class NodePlugin : Plugin<Project> {
             // package.json
             if (extension.cleanTaskName.get() != BasePlugin.CLEAN_TASK_NAME) {
                 val baseCleanTask = project.tasks.findByName(BasePlugin.CLEAN_TASK_NAME)
-                baseCleanTask?.configure<Task> {
-                    finalizedBy(extension.cleanTaskName.get())
-                }
+                baseCleanTask?.finalizedBy(extension.cleanTaskName.get())
             }
         }

Happy to raise a PR if this change seems reasonable! Thank you! 🙏

Hey @RoccoC !
Thanks a lot for raising this issue and providing a detail way to reproduce it and proposing a fix.
Referring to the Gradle Doc, findByName is part of the Eager API, which should be avoided. So I replaced it with named and caught the associated error in case of a missing task, as this task won't impact the plugin in any case if it doesn't exist in the project.
This issue is now fixed with 2.0.6.

Excellent, thanks so much!


Any plans to add a info type to the list?

I was thinking an "!" type icon in blue - this fixes a common state with Snackbars where we want to just display an information snackbar

I guess we can customise, or provide a parameter of Widget that could be used to replace the default Widgets in the snackbar
will update surely, incase you can do it? Feel free to create a PR

Happy to do so but where did you get your svg's from. I would like to use an ! one and then I am happy to code up the rest of it.

I mostly use freepik and flaticons

We have ContentType parameter that you can use to show error, success, warning or just a message.
Feel free to check that out


build error  on windows 10 x64

BuildEnvironment
Executing task: BuildEnvironment
dotnet-install: .NET SDK version 1.0.0-preview2-003121 is already installed.
.NET Command Line Tools (1.0.0-preview2-003121)
Product Information:
Version:            1.0.0-preview2-003121
Commit SHA-1 hash:  1e9d529bc5
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.14393
OS Platform: Windows
RID:         win10-x64
Feeds used:
https://dotnet.myget.org/F/dotnet-buildtools/api/v3/index.json
https://api.nuget.org/v3/index.json
已安装程序包“xunit.runner.console.2.2.0-beta2-build3300”。
Finished executing task: BuildEnvironment

PopulateRuntimes
Executing task: PopulateRuntimes
Finished executing task: PopulateRuntimes

Setup
Executing task: Setup
Finished executing task: Setup

Restore
Executing task: Restore
Restoring packages....
Package restore successful!
Restoring packages....
Package restore successful!
Finished executing task: Restore

BuildTest
Executing task: BuildTest
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(19,15): error DOTNET1011: Framework not installed: .NETFramework,Version=v4.5.1 in
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(21,28): error NU1001: The dependency System.Runtime could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(22,30): error NU1001: The dependency System.Threading could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(23,36): error NU1001: The dependency System.Threading.Tasks could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(24,32): error NU1001: The dependency System.Collections could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(25,25): error NU1001: The dependency System.Linq could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(26,34): error NU1001: The dependency System.Text.Encoding could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(27,31): error NU1001: The dependency System.Reflection could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(28,29): error NU1001: The dependency System.Security could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(29,34): error NU1001: The dependency System.Globalization could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(30,24): error NU1001: The dependency System.Xml could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(31,29): error NU1001: The dependency System.Xml.Linq could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(12,56): error NU1001: The dependency mscorlib could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(12,56): error NU1001: The dependency mscorlib could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(8,37): error NU1001: The dependency System could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(10,50): error NU1001: The dependency System could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(11,49): error NU1001: The dependency System could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(12,56): error NU1001: The dependency System could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(14,51): error NU1001: The dependency System could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(8,37): error NU1001: The dependency System could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(10,50): error NU1001: The dependency System could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(11,49): error NU1001: The dependency System could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(12,56): error NU1001: The dependency System could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(14,51): error NU1001: The dependency System could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(10,50): error NU1001: The dependency System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(11,49): error NU1001: The dependency System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(12,56): error NU1001: The dependency System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(14,51): error NU1001: The dependency System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(10,50): error NU1001: The dependency System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(11,49): error NU1001: The dependency System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(12,56): error NU1001: The dependency System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(14,51): error NU1001: The dependency System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(10,50): error NU1001: The dependency System.ComponentModel.Composition could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(11,49): error NU1001: The dependency System.ComponentModel.Composition could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(12,56): error NU1001: The dependency System.ComponentModel.Composition could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.Abstractions\project.json(14,51): error NU1001: The dependency System.ComponentModel.Composition could not be resolved.
An error occured when executing task 'BuildTest'.
Error: Building test OmniSharp.Stdio.Tests failed for net451.

It kind of sounds like the dotnet assemblies are not registered properly.
This is based on the line:
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(19,15): error DOTNET1011: Framework not
installed: .NETFramework,Version=v4.5.1 in
I've not personally seen that before.
On Fri, Sep 9, 2016 at 1:29 AM, sunriseyuen<EMAIL_ADDRESS>wrote:

BuildEnvironment
Executing task: BuildEnvironment
dotnet-install: .NET SDK version 1.0.0-preview2-003121 is already
installed.
.NET Command Line Tools (1.0.0-preview2-003121)
Product Information:
Version: 1.0.0-preview2-003121
Commit SHA-1 hash: 1e9d529bc5
Runtime Environment:
OS Name: Windows
OS Version: 10.0.14393
OS Platform: Windows
RID: win10-x64
Feeds used:
https://dotnet.myget.org/F/dotnet-buildtools/api/v3/index.json
https://api.nuget.org/v3/index.json
已安装程序包“xunit.runner.console.2.2.0-beta2-build3300”。
Finished executing task: BuildEnvironment
PopulateRuntimes
Executing task: PopulateRuntimes
Finished executing task: PopulateRuntimes
Setup
Executing task: Setup
Finished executing task: Setup
Restore
Executing task: Restore
Restoring packages....
Package restore successful!
Restoring packages....
Package restore successful!
Finished executing task: Restore
BuildTest
Executing task: BuildTest
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(19,15): error DOTNET1011: Framework not
installed: .NETFramework,Version=v4.5.1 in
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(21,28): error NU1001: The dependency
System.Runtime could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(22,30): error NU1001: The dependency
System.Threading could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(23,36): error NU1001: The dependency
System.Threading.Tasks could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(24,32): error NU1001: The dependency
System.Collections could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(25,25): error NU1001: The dependency
System.Linq could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(26,34): error NU1001: The dependency
System.Text.Encoding could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(27,31): error NU1001: The dependency
System.Reflection could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(28,29): error NU1001: The dependency
System.Security could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(29,34): error NU1001: The dependency
System.Globalization could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(30,24): error NU1001: The dependency System.Xml
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(31,29): error NU1001: The dependency
System.Xml.Linq could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(12,56): error NU1001: The dependency mscorlib
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(12,56): error NU1001: The dependency mscorlib
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(8,37): error NU1001: The dependency System
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(10,50): error NU1001: The dependency System
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(11,49): error NU1001: The dependency System
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(12,56): error NU1001: The dependency System
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(14,51): error NU1001: The dependency System
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(8,37): error NU1001: The dependency System
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(10,50): error NU1001: The dependency System
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(11,49): error NU1001: The dependency System
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(12,56): error NU1001: The dependency System
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(14,51): error NU1001: The dependency System
could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(10,50): error NU1001: The dependency
System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(11,49): error NU1001: The dependency
System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(12,56): error NU1001: The dependency
System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(14,51): error NU1001: The dependency
System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(10,50): error NU1001: The dependency
System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(11,49): error NU1001: The dependency
System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(12,56): error NU1001: The dependency
System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(14,51): error NU1001: The dependency
System.Core could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(10,50): error NU1001: The dependency
System.ComponentModel.Composition could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(11,49): error NU1001: The dependency
System.ComponentModel.Composition could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(12,56): error NU1001: The dependency
System.ComponentModel.Composition could not be resolved.
D:\System\build-Vim\omnisharp-roslyn\src\OmniSharp.
Abstractions\project.json(14,51): error NU1001: The dependency
System.ComponentModel.Composition could not be resolved.
An error occured when executing task 'BuildTest'.
Error: Building test OmniSharp.Stdio.Tests failed for net451.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/OmniSharp/omnisharp-roslyn/issues/633, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABNdpf306iCEyRFu1BBw_9vnSaC2ncpdks5qoO6igaJpZM4J4tol
.

I've updated OmniSharp to .NET 4.6. Do you still see this failure? If so, you might try installing the Microsoft .NET 4.5.1 Developer Pack.
Note that this failure can occur on machines where no Visual Studio has been installed (or a Visual Studio version earlier than 2013).

I got this same error with .NET 4.6 and the solution was to download the corresponding .NET targeting pack here

This issue has grown pretty stale. Let me know if you're still experiencing the issue, and we'll take a look.


Extremely long Naga and wgpu compile times in release mode on Windows.

Hi, I was testing this out to see if it would work for building Bevy on Windows and debug builds worked reasonably well (a bit faster build time for a bit slower runtime on Windows+MSVC).
Then I tried a release build, to see if it was possible to get better runtime performance at similar build times to regular llvm rustc debug builds, and it had some issues. It ended up taking 192.4s (on a 5900x with 32GB RAM), during which it spent 165.8s building wgpu, with 164.2s of that being codegen, and 119.8s building naga (115.1s of which was codegen).
I confirmed that this wasn't some weird issue due to building Bevy by cloning and building the naga repo, and it took a similar amount of time.

That is quite a bad result. I can't reproduce it locally on my Linux laptop (2 core + HT, 4GB ram) where it finished everything in 130s (after substracting time to update the registry and fetching crates) during which all cores were fully loaded the entire time. Wgpu took only 43s and naga 46s. I will need some more information to be able to pin point the issue. Could you please run cargo clean and then RUSTFLAGS="-Ztime-passes=/path/to/your/project/self_profile_results" dist/cargo-clif build --release and upload the files starting with wgpu- and naga- in the self_profile_results directory in your project generated by the previous command? The self-profile output shows on what exactly rustc (and by extension cg_clif) spent how much time. Note that you won't be able to upload the whole self_profile_results directory as it is over 1GB which is way past the github upload limit. For me wgpu and naga combined were only 50MB (or 100MB when including wgpu_core, wgpu_hal and wgpu_types too).

(you mean -Zself-profile rather than -Ztime-passes ?)

Yeah, fixed. Thanks!

I had to split it into 2 zip files since github has a 25MB limit (and doesn't support anything better than .zip).
self_profile_results-1.zip (naga+wgpu core)
self_profile_results-2.zip (wgpu hal, wgpu types, wgpu

For wgpu there is a codegen unit (on thread 5) taking 44s to compile spread out over a dozen functions and another codegen unit (on thread 16) taking 2.2 min where compiling a single function completely dwarfs all other functions.

For naga there is a single function taking 1.8 min (on thread 4)

It would really help to know which functions are so slow to compile. I work on some code to show function names in the self profile results tomorrow.

(Recording timings for the various passes of cranelift using generic_activity_with_arg_recorder would also be very useful in this case.)

(Recording timings for the various passes of cranelift using generic_activity_with_arg_recorder would also be very useful in this case.)

Hopefully I did it right. It was quite a bit bigger so I had to split them up even more this time.
naga-0023456.mm_profdata.zip
wgpu_core-0011120.mm_profdata.zip
wgpu_hal_types.zip
wgpu-0005296.mm_profdata.zip

In case it helps, I was using the msvc artifact downloaded from https://github.com/bjorn3/rustc_codegen_cranelift/actions/runs/4065395449

I just tested on Linux (same computer, Fedora 37) and it's similar but less bad (using the linux artifact from the same actions run). In total it took 89.7s to run cargo-clif build --example many_foxes --release, with wgpu taking 71.0s (69.9s codegen) and naga taking 66.3s (63.4s codegen).

In case it helps, I was using the msvc artifact downloaded from https://github.com/bjorn3/rustc_codegen_cranelift/actions/runs/4065395449

I just built my own from master (21bdff8bc015b557bfae85b968dc4c100be85caf), and it doesn't have this issue. (cargo-clif build --example many_foxes --release only took 24.5s)

In case it helps, I was using the msvc artifact downloaded from https://github.com/bjorn3/rustc_codegen_cranelift/actions/runs/4065395449

Did my own build on Windows MSVC using the master branch, and it's also fine? (apart from linking being extremely slow if you don't use lld)
I also tried downloading a different MSVC CI artifact, and it also hangs for a similar amount of time.

I can also confirm, that I tried to reproduce this yesterday with a local build and didn't experience any major slowdowns.
Except for the linker thing, which should be fixed once https://github.com/bytecodealliance/wasmtime/pull/5550 is merged.
I'll try to reproduce it with CI artifacts.

(Recording timings for the various passes of cranelift using generic_activity_with_arg_recorder would also be very useful in this case.)

Hopefully I did it right. It was quite a bit bigger so I had to split them up even more this time. naga-0023456.mm_profdata.zip wgpu_core-0011120.mm_profdata.zip wgpu_hal_types.zip wgpu-0005296.mm_profdata.zip

Unfortunately these files seem to be corrupt. Crox produces a near empty json file. Summarize doesn't show anything.

https://github.com/bjorn3/rustc_codegen_cranelift/pull/1346 added more details to the self profile output. Could you try RUSTFLAGS="-Zself-profile=/path/to/your/project/self_profile_results -Zself-profile-events=default,function-args" dist/cargo-clif build --release with the latest CI build? (https://github.com/bjorn3/rustc_codegen_cranelift/actions/runs/4086944682)

Well, those flags added a ton to the build times (7m25s instead of ~3m10s).
self_profile_results-1.zip
self_profile_results-2.zip

Thanks! I found the issue. To catch more bugs in CI, I made the build system enable debug assertions for cg_clif itself when building on CI. One of the effects of this is enabling the regalloc verifier, which can be very slow. Because debug assertions are enabled when building in CI, the CI artifacts have debug assertions and thus the regalloc verifier enabled, but local builds don't, hence why you could only reproduce this issue with a cg_clif from CI and not with one built by yourself. I think I will need to create separate dist jobs for CI artifacts that don't enable debug assertions.

Opened https://github.com/bjorn3/rustc_codegen_cranelift/pull/1347

Fixed in #1347


Move mixin to core

What does this PR do?

Fixes #<issue_number>
Does your PR introduce any breaking changes ? If yes, please list them.

Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)
[ ] Did you list all the breaking changes introduced by this pull request?

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

just curious, what is the motivation?

@Borda Reference

doesn't the device_dtype_mixin require a rerouting of the imports for BC?

I don't think it would be required for internal use.

@kaushikb11 > I don't think it would be required for internal use.
Not for internal use, but it was part of the public API in utilities (I use it quite often in my own code) so I think we should reroute this together with a Deprecation Warning


Replace hmac & sha2 crates with 0-dependency hmac-sha256

Hello, this PR replaces the hmac and sha2 crates with hmac-sha256, eliminating 16 dependencies in the process which should result in an improvement to build times.
--- rusoto.original	2020-07-04 16:33:27.415505343 +0900
+++ rusoto.trimmed	2020-07-04 16:33:32.275644684 +0900
@@ -1,4 +1,4 @@
-rusoto_signature v0.44.0 (/rusoto-original/rusoto/signature)
+rusoto_signature v0.44.0 (/rusoto/rusoto/signature)
 ├── base64 v0.12.3
 ├── bytes v0.5.5
 ├── futures v0.3.5
@@ -41,13 +41,7 @@
 │   ├── futures-task v0.3.5 (*)
 │   └── futures-util v0.3.5 (*)
 ├── hex v0.4.2
-├── hmac v0.7.1
-│   ├── crypto-mac v0.7.0
-│   │   ├── generic-array v0.12.3
-│   │   │   └── typenum v1.12.0
-│   │   └── subtle v1.0.0
-│   └── digest v0.8.1
-│       └── generic-array v0.12.3 (*)
+├── hmac-sha256 v0.1.2
 ├── http v0.2.1
 │   ├── bytes v0.5.5
 │   ├── fnv v1.0.7
@@ -130,7 +124,7 @@
 ├── md5 v0.7.0
 ├── percent-encoding v2.1.0
 ├── pin-project v0.4.22 (*)
-├── rusoto_credential v0.44.0 (/rusoto-original/rusoto/credential)
+├── rusoto_credential v0.44.0 (/rusoto/rusoto/credential)
 │   ├── async-trait v0.1.36
 │   │   ├── proc-macro2 v1.0.18 (*)
 │   │   ├── quote v1.0.7 (*)
@@ -172,16 +166,6 @@
 │   ├── tokio v0.2.21 (*)
 │   └── zeroize v1.1.0
 ├── serde v1.0.114 (*)
-├── sha2 v0.8.2
-│   ├── block-buffer v0.7.3
-│   │   ├── block-padding v0.1.5
-│   │   │   └── byte-tools v0.3.1
-│   │   ├── byte-tools v0.3.1
-│   │   ├── byteorder v1.3.4
-│   │   └── generic-array v0.12.3 (*)
-│   ├── digest v0.8.1 (*)
-│   ├── fake-simd v0.1.2
-│   └── opaque-debug v0.2.3
 ├── time v0.2.16
 │   ├── cfg-if v0.1.10
 │   ├── libc v0.2.71

eliminating 16 dependencies in the process which should result in an improvement to build times.

I'm happy to see the focus on build times:)
Have you benchmarked the difference in build times with a sample application before and after with some sample results you can share? I would be curious to see what the result looks like.
If the goal is to reduce build times and we haven't measured first it's possible that a change like this can make the build slower despite good intensions.
In terms of build time, a crate is a unit of parallelization so collapsing 16 crates into one may produce a net increase in build time. It's also possible it won't but one will never know without measuring first.

Sure, here are some cargo clean && time cargo build results for a simple application that just calls the S3 ListBuckets endpoint, with dependencies on rusoto_core, rusoto_credential, rusoto_s3, tokio, and anyhow:
using hmac-sha256
real	0m23.936s
user	1m56.468s
sys	0m15.044s

using sha2 & hmac
real	0m25.867s
user	1m54.498s
sys	0m14.600s

This is not a case of collapsing 16 crates into one, hmac-sha256 is a tiny crate without all the excess abstractions the sha2 and hmac crates introduce: https://github.com/jedisct1/rust-hmac-sha256/tree/master/src. Another benefit is it has a simple, stable API whereas the latest hmac crate has incompatible changes that rusoto will have to track if this PR is not accepted.

Thanks for sharing the benchmark. How big was your sample size? For only a few seconds gain it might be good to get a decent sample size. With benchmarking its good to get a picture of what averages and standard deviations look like.

Please, do not do this. hmac and sha2 are wildly popular crates (millions of downloads), and part of the RustCrypto project, which I trust to get cryptography right. (More eyes, years of reputation building, etc.) hmac-sha256 is only one year old, has only one contributor, and no reputation to speak of. It has orders of magnitude less downloads than the hmac/sha256 crates.
It's also worth keeping in mind that most applications will wind up depending on sha2 via multiple paths. Applications that use cookies will depend on sha2 via cookie; applications that use PostgreSQL will depend on sha2 via postgres-protocol. For those applications, introducing a new dependency on hmac-sha256 will actually increase build times. There is value in having a standard implementation of sha2 that is used across the ecosystem.
While I'm usually the loudest complainer about build times in Rust, replacing two foundational crypto crates with a relatively unknown alternative to save two seconds of build time would be a very concerning decision.

Those are all good points. I personally don't have a strong opinion in that area.
I'd just like to understand the goal of the change and make sure we're being diligent about how how we track against that goal to make sure we're not regressing.

I strongly agree with Nikhil. Rusoto should keep hmac and sha2.

The hmac-sha256 crate is written by Frank Dennis (jedisct1, https://github.com/jedisct1) who is well known for creating libsodium, one of the most popular and trusted cross platform crypto libraries.

A 2-second CPU time improvement over the course of a nearly 2-minute CPU time build (https://github.com/rusoto/rusoto/pull/1782#issuecomment-653744650) is, to me, not worth swapping out the more commonly-used crates across the Rust ecosystem at this moment.
I'd be happy to see discussion in an issue, since this is clearly somewhat contentious, but I'd rather not let this PR linger and grow stale over time.


Simulate Tactile Sensor Arrays with Touch Grid Plugin

Hi,
I'm simulating tactile sensor arrays (e.g., uSkin) using the touch_grid plugin, attached to each knuckle of the Shadow Hand. However, due to the collision detection between rigid bodies not producing multiple contact points, often only one touch_grid sensor outputs a non-zero value (e.g., the small white block between the thumb tip and a red object).

This is unexpected since real tactile sensor arrays typically show non-zero readings across multiple taxels.
One potential solution might be decomposing the object into sub-meshes, similar to how the touch_grid demo seems to work.

I am not sure if it will work, any suggestions?

How did you deal with that problem later?


Changed to downloadKafka task from wget.

A new gradle task(downloadKafka) was added from ver v<IP_ADDRESS> .
So, I changed the build command from wget to downloadKafka in README.md
Please confirm this PR.
Thank you.

Hmm... I have not changed source code...
Why does the test failed?

Thanks for the pull request!

Thanks for the review @steveniemitz !


[DO-NOT-MERGE] Health check

The build looks fine now

Codecov Report

Merging #868 into master will decrease coverage by 2.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #868      +/-   ##
==========================================
- Coverage   94.27%   92.11%   -2.17%
==========================================
  Files          34       34
  Lines        6201     6201
==========================================
- Hits         5846     5712     -134
- Misses        355      489     +134

Impacted Files
Coverage Δ

databricks/koalas/usage_logging/__init__.py
24.54% <0%> (-72.73%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/koalas/__init__.py
77.5% <0%> (-7.5%)
:arrow_down:

databricks/conftest.py
91.48% <0%> (-6.39%)
:arrow_down:

databricks/koalas/frame.py
94.36% <0%> (-1.59%)
:arrow_down:

databricks/koalas/namespace.py
85.01% <0%> (-1.31%)
:arrow_down:

databricks/koalas/plot.py
93.33% <0%> (-0.96%)
:arrow_down:

databricks/koalas/utils.py
97.24% <0%> (-0.69%)
:arrow_down:

databricks/koalas/testing/utils.py
77.35% <0%> (-0.63%)
:arrow_down:

databricks/koalas/series.py
95.16% <0%> (-0.17%)
:arrow_down:

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 a05cb46...283381a. Read the comment docs.


Clarify expected fastq name for input files

See https://github.com/CGATOxford/CGATPipelines/issues/388

Note for porting to CGATCore: probably not necessary. There are benefits to the current naming scheme.


Update storage account help

Partially react to https://github.com/Azure/azure-cli/issues/4347

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

Command Guidelines

[ ] Each command and parameter has a meaningful description.
[ ] Each new command has a test.

(see Authoring Command Modules)

@tjprescott can you help me with the words?

@derekbekoe  can you sign off again?


when i run train.py ,it shows a error

OOM when allocating tensor with shape[10,208,208,64] and type bool on /job:l

when i run train.py it is showing this message plz help me out some one
Unable to open file (unable to open file: name = '/content/drive/My Drive/Colab Notebooks/load_weights.h5', errno = 2, error message = 'No such file or directory', flags = 0, o_flags = 0) site:stackoverflow.com

thank you！i have solved this problem！thank you for your reply!
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年4月1日(星期三) 上午6:55
收件人<EMAIL_ADDRESS>抄送: "笑嘻嘻"<763946880<EMAIL_ADDRESS>主题: Re: [qqwweee/keras-yolo3] when i run train.py ,it shows a error (#613)
when i run train.py it is showing this message plz help me out some one
Unable to open file (unable to open file: name = '/content/drive/My Drive/Colab Notebooks/load_weights.h5', errno = 2, error message = 'No such file or directory', flags = 0, o_flags = 0) site:stackoverflow.com
the problem is in darknet which does not support spaces in names like in your "My Drive". you have to use symlinks. I did this for example with:
`# symlink to get rid of darknet error of spaces in My Drive
!ln -s /content/drive/My\ Drive/Colab Notebooks/ /mydrive
!ls /mydrive
`
best regards you all.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


How to deploy supabase/supavisor on local machine (mac)

I am new to Supabase/Supavisor and I want to deploy it on my local machine (Mac). I have PostgreSQL 14 running on my machine. Can I have some documentation on how to deploy Supavisor? I went to the https://github.com/supabase/supavisor Installation and usage page, but it is not opening.

I'm also waiting for an easy way to start Supavisor via the local dev setup. There's a documented way of enabling PgBouncer locally which probably needs to be updated for Supavisor once available: https://supabase.com/docs/guides/cli/config#db.pooler.enabled

@chethankumar4046 sorry for the confusion, we've moved our install documentation to https://supabase.github.io/supavisor/development/installation/

@abc3 Thank you for your prompt response! I have a question about using Supervisor. I want to use Supervisor with my PostgreSQL server, and I'm wondering if it's possible to use Supervisor without relying on Supabase CLI, a Supabase account, or the Supabase dashboard.
If it's possible to use Supervisor independently for my PostgreSQL server, could you provide me with documentation and instructions on how to set it up and configure it?
I appreciate your help with this!


Mark package as internal not working

I'm experiencing the issue when can't use the setting import/internal-regex to mark my packages as internal. After some manipulation and researching seems the reason is PnP mode which I'm using on my project.
My eslint config
parser: '@typescript-eslint/parser'
parserOptions:
  sourceType: 'module'
  project: 'tsconfig.json'
plugins:
  - '@typescript-eslint/eslint-plugin'
extends:
  - 'plugin:@typescript-eslint/eslint-recommended'
  - 'plugin:@typescript-eslint/recommended'
  - 'prettier'
  - 'plugin:import/recommended'
  - 'plugin:import/typescript'
env:
  node: true
root: true
rules:
  import/order:
    - error
    - groups:
        - builtin
        - external
        - internal
        - parent
        - sibling
        - type
      newlines-between: never
settings:
  import/resolver: typescript
  import/internal-regex: ^@(lib|app)/

This configuration linting my code but doesn't recognize marked internal packages. When I remove import/resolver: typescript from settings it groups my imports in the right way, but throws an error Resolve error: unable to load resolver "node"  import/order. The same situation with the default node resolver. Seems like when resolver is working it ignores any settings.
My tools:
yarn -v
3.0.0

node -v
v14.17.0

"eslint": "7.32.0",
"eslint-plugin-import": "2.23.4",
"@typescript-eslint/eslint-plugin": "4.28.5",
"@typescript-eslint/parser": "4.28.5",
"eslint-import-resolver-node": "0.3.4",
"eslint-import-resolver-typescript": "2.4.0",

Thanks in advance!
P.S. If you need to provide additional information, please inform me about it

If you’re using a nonstandard resolution (like pnp), then you need a custom resolver for it for this entire plugin to work properly. I’m not aware of any pnp resolver yet.

Thanks for your response. Do you have some recommendations for customer resolvers that properly handle PnP mode? I checked this list https://github.com/import-js/eslint-plugin-import/wiki/Resolvers and didn't find any appropriate solution

None exist as far as I know.

Okay, thanks! I close this issue then

I created the repository to reproduce an error https://github.com/KostyaZgara/eslint-plugin-import-berry-issue-example and made some checks with eslint-plugin-import and figured out that issue with isExternalMethod which returns the wrong result in PnP mode.
I created a draft pull request https://github.com/import-js/eslint-plugin-import/pull/2178 with a short explanation of what was the problem and how I suggest to resolve it. Please check it out and provide your thoughts on this. If the solution is fine for your I'll finalize it with tests and additional settings

The only proper solution here is making a separate package, like https://www.npmjs.com/package/eslint-import-resolver-node, for yarn pnp resolution.

Sorry, I made a double check how it's working now and seems no custom resolver is need
The difference between standard node and pnp resolution in this:
For example, eslint-import-resolver-node resolves external package in this way.
{
  found: true,
  path: '/some/path/eslint-plugin-import/node_modules/lodash/lodash.js'
}

but when with PnP mode it resolved with
{
  found: true,
  path: '/some/path/eslint-plugin-import-berry-issue-example/.yarn/__virtual__/debug-virtual-11a7ab7409/0/cache/debug-npm-4.3.2-f0148b6afe-820ea160e2.zip/node_modules/debug/src/index.js'
}

So, to fix recognizing external packages need to add .yarn folder to import/external-module-folders setting. After this, it started to work correctly. Thanks for your time and help me to fix my issue!
If you don't mind, I'll create another PR with description how to work with this plugin with PnP mode enabled


What is the latest sphinx version supported?

Hello Pat,
What is the latest sphinx version supported? I tried to install 2.2.6 and I started to get a few warnings regarding:
WARNING: key 'sql_query_info' was permanently removed from Sphinx configuration. Refer to documentation for details.
WARNING: key 'charset_type' was permanently removed from Sphinx configuration. Refer to documentation for details.
WARNING: key 'enable_star' was permanently removed from Sphinx configuration. Refer to documentation for details.

I had this on my config/thinking_sphinx.yml. Moving it to app/indices/model_index.rb as set_property seems to raise the same issue too.
Thanks in advance.

The latest in the develop branch removes charset_type and sql_query_info, and you don't need to specify enable_star at all (it's always enabled now).

But also: they're warnings, so while they're annoying, things will still work anyway.

Thanks for your reply Pat.
I think sql_query_info is being generated by TS. Charset_type i'm using it to be able to convert accented chars and such. Does it mean it will lose support in the future OR it will be UTF-8 by default (i doubt it because probably of Chinese chars or/and similar)?
Seems I managed to make it work with 2.2.6 just fine too (one of my initial questions). Maybe worth to update the README to promote people on newer versions ?

sql_query_info won't get generated by TS if you use the latest commits from the develop branch.
And it's worth noting the difference between charset_type (which is deprecated) and charset_table (which perhaps you're using for converting accented characters?) - charset_type is UTF8 only in Sphinx 2.2.
And once I get the next TS release out, updating the README is an excellent idea :)

Thanks for all this information :100: ace as usual.


Songs Not Playing

Not sure what I am doing wrong here, but when I select a song, it appears at the top of the screen but does not begin playing. Previews of songs would play fine before I logged in (the 30 second clips), but after logging in, no songs play. My playlists and library do show up fine.

Can you take a look at the console in Developer Tools, and see if there are any errors?

Forgive my ignorance, how exactly do I access the developer tools to see?

Chromium (latest stable) on Arch Linux

Do you have https://wiki.archlinux.org/index.php/chromium#Widevine_Content_Decryption_Module_plugin setup?
Apple Music send the content encrypted and needs to be decrypted by the browser.

Ah, I was not aware this was a requirement. Works fine now, thank you.


[BUG] Exam mode result points are wrong

Describe the bug
Results page seems to show a wrong number of points, at least for the PSD-1 exam mode.
To Reproduce
Steps to reproduce the behavior:

PSD-1
Click on Exam Mode
Open Network tab to make sure all the answers are valid
It shows a 96.67% score.

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
I expect the app to show 100% when I do 100%
Desktop (please complete the following information):

OS: Windows 11
Browser: Arc
Version: Arc: Based on Chromium version 126.0.6478.57

Additional context
I tried the other way around: having only 1 good answer gives me 3.33/100 which is good.
I would have looked into it but I can't seem to run the app locally at the moment on my work laptop (next dev weirdly fails immediately without any error message). Maybe later in the week.

Thanks for submitting the issue; somehow, it slipped from all my notifications.
Please keep me posted if you'll be able to pick it up :)

Maybe an idea to combine it with summary page for Practice Mode?
https://github.com/Ditectrev/Practice-Exams-Platform/issues/34

Fixed in https://github.com/Ditectrev/Practice-Exams-Platform/pull/45.


Add Service Account annotations

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If this PR will release a new chart version please make sure to also uncomment the following line:

/kind chart-release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area falco-chart

/area falco-exporter-chart

/area falcosidekick-chart

What this PR does / why we need it:
This PR is based on #268 which is valuable but unfortunately, the original author is not replying.
Basically, I have rebased the #268 branch and added the missing commits here.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

falco/OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

falco/OWNERS [cpanato,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


hitting enter twice while in a blockquote (at end of doc) doesn't exit the blockquote

This could relate to #36 -- it seems like hitting enter on an empty line in a formatted block should leave you on an unformatted (p) line.

Sounds good to me


GitHub Actions - I've been waiting for a long time！？

Deploy GCR Cleaner to GitHub Actions
I've been waiting for a long time！ Why？
Please help me. Thanks.

my github actions config file.

You are running the gcr-cleaner server. You need to use the gcr-cleaner CLI. See https://github.com/GoogleCloudPlatform/gcr-cleaner/blob/main/docs/deploy-github-actions.md.

It works！ Thank you!


not working on webview

im load website with feature webcodecamjs but im run,not work click play button??
why

Connection must HTTPS


perf: triple buffering

Current performance is running at about 50fps. We need to get this up to a minimum of 60fps. This following optimisation should achieve this, otherwise 12bpp will have to be implemented.
An additional buffer needs to be added to the memory controller to be used as a back buffer for comparing the current scanline of the current frame to. This way we only write to the lcd ram when the current scanline is different to its counterpart in the previous frame (back buffer).
We require a total of 3 frames in the memory controller:

The previous frame.
The current frame being rendered.
The next frame being generated.

The capacity of the RPIoController queues will remain at 2 since a maximum of 2 frames can be in flight (the one being rendered, and the one being generated). The only difference being that a third memory controller frame will be tied to the current frame for comparison purposes.

PR: https://github.com/nbeddows/meen-i8080-arcade/pull/84


Dep 191: Composite fields

An early cut of the implementation of DEP 191 for composite fields. DEP192 will be implemented separately, although some partial implementation of various hooks which will be required for the implementation of standalone composite fields is included, appropriately commented.
Please feel free to review even though implementation is incomplete, it is complete enough for your comments to be valuable (otherwise I wouldn't have submitted the PR). This is a rather large change which will require community consensus.
Done

Observables and some standard observable collection implementations
Serialization/deserialization of composite fields
Implementation of django.db.models.constrain factory method
Custom lookup and transform implementation
Refactoring of sql compiler to support values and expressions spanning multiple columns in a row of a result set

Still to do:

Serialization
Apply composite field constraints and indexes to the database table
Migrations
Update proposal

buildbot, add to whitelist.

Closing this down until I decide to have another spurt of productivity.


proposal: x/tools/go/packages: add modinfo.ModulePublic to packages.Package

Currently, packages.Load returns a packages.Package object that contains useful information from the go list API. However, sometimes the module information for the requested package is needed as well.
My proposal is basically to add the modinfo.ModulePublic info from go list to this package.
Similar to go list, if the package is not part of a module or it's provided by the Overlay API, Package.Module will be nil.
Let me know what do you think about this and I'll submit my CL for the proposal.

This would probably make #35563 much simpler to implement.

/cc @matloob @ianthehat

For now the x/tools/go/packages package is meant to be build-system agnostic. Since modules don't appear in all Go build systems, that means that if we're keeping to being build-system agnostic.
That might not be the right decision, but I think we should revisit that decision before deciding on this.
Issue #38234 is somewhat relevant to this by the way.

Being build-system agnostic shouldn't mean ignoring core Go features, though.
If you're using Bazel those fields would be empty.

I'm merging this issue with #38446.
The main differences are that we still need to discuss exactly what struct we're putting in Package (module public is unexported, and whichever struct we pick should probably be defined in x/mod), and that we'd need a Need bit for the field.

Here's the Module struct from go help list:
When listing modules, the -f flag still specifies a format template
applied to a Go struct, but now a Module struct:

    type Module struct {
        Path      string       // module path
        Version   string       // module version
        Versions  []string     // available module versions (with -versions)
        Replace   *Module      // replaced by this module
        Time      *time.Time   // time version was created
        Update    *Module      // available update, if any (with -u)
        Main      bool         // is this the main module?
        Indirect  bool         // is this module only an indirect dependency of main module?
        Dir       string       // directory holding files for this module, if any
        GoMod     string       // path to go.mod file used when loading this module, if any
        GoVersion string       // go version used in module
        Error     *ModuleError // error loading module
    }

    type ModuleError struct {
        Err string // the error itself
    }

Is that what we want in go/packages? Is there anything we don't want in go/packages?

That sounds reasonable to me? I don't see anything that we'd obviously not want. Though I'd like to hear what @mvdan and @dominikh think.

SGTM. Will go/packages acquire Versions and Update? If not, we may want to skip those.

Good point. Those could potentially be passed through as build flags, but that doesn't sound like something we'd want to encourage.

It does sound like we should leave out Versions and Update, making the struct we're talking about adding:
type Module struct {
    Path      string       // module path
    Version   string       // module version
    Replace   *Module      // replaced by this module
    Time      *time.Time   // time version was created
    Main      bool         // is this the main module?
    Indirect  bool         // is this module only an indirect dependency of main module?
    Dir       string       // directory holding files for this module, if any
    GoMod     string       // path to go.mod file used when loading this module, if any
    GoVersion string       // go version used in module
    Error     *ModuleError // error loading module
}

type ModuleError struct {
    Err string // the error itself
}

I'm not sure about ModuleError either, but we can see how it goes.
It sounds like people agree with the idea of adding the info. We can fine-tune the exact fields separately but the above is a start.
Based on the discussion above, this sounds like a likely accept.

No change in consensus, so accepted.


Track delivery status of sent emails

Context
We introduced an email log in https://github.com/DFE-Digital/apply-for-postgraduate-teacher-training/pull/1433, but we haven't added delivery tracking. This will allow us to see which emails are delivered and which ones bounce.
Changes proposed in this pull request
This uses the delivery receipts we receive from GOV.UK Notify to keep track of the delivery status of emails.
Guidance to review
Will this work?
Link to Trello card
https://trello.com/c/AFbxsqs4
Things to check

[x] This code doesn't rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

Discussing the migration situation here: https://ukgovernmentdfe.slack.com/archives/CN1MCQCHZ/p1583943476285100


Letters are getting cut off in terminal when using webgl renderer

Likely caused by the powerlines cliping change https://github.com/microsoft/vscode/pull/152347

/duplicate https://github.com/microsoft/vscode/issues/152436


Update setup.py classifiers.

Resolves #77.

@blampe @breerly @junchaowu

lgtm

good catch - :shipit:


Addressing #809 Added  param to sensu::transport

Pull Request Checklist
Solves issue #809
Description
This solves issues #809 by exposing an exnsure parameter to allow users to manage the presence of trnsport.json and by ensuring it's present if transport_type is either redis or rabbitmq.
Need double check if this is the expected and correct behaviour.
Related Issue
Fixes # 809
Motivation and Context

How Has This Been Tested?

General

[x] Update README.md with any necessary configuration snippets

[x] New parameters are documented

[ ] New parameters have tests

[x] Tests pass - bundle exec rake validate lint spec

Indeed the class sensu::transport doesn't work on it's own and therefore is a little bit tricky to test. You need to use (:pre_condition) to add the class sensu with the needed parameters.
I have created a test [1] and sent a PR to the 809 branch of @alvagante that does the trick.
[1] https://github.com/Phil-Friderici/sensu-puppet/blob/809/spec/classes/sensu_transport_spec.rb

That's a quite neat trick @Phil-Friderici , to define a bogus sensu class and declare it in the precondition, I mea.
I think that if the model works well, it could eventually be extended to other classes: most of them are declared from main sensu class, and the relevant tests are done on it. Our tests declarations would change as follows
-describe 'sensu' do
+describe 'sensu::transport' do

Yepp that should work.
In the longer run these subclases should become either integrated into the main class or should be refactored to become real classes (that could live on their own).

Going to close this MR, please use #832 , which takes to most direct and simple approach without the addition of a mostly useless parameter for which testing would have been a bit excessive. Thanks for @Phil-Friderici for the hints on tests, they've somehow opened my mind :-D

@alvagante The pleasure was on my side, but thanks for lifting me up today ;)


Allow to merge snapshots

rustic backup only accepts one path to being backup'ed.
Changing this directly is tough as the ignore crate is used which also only support one path.
A workaround is to specify only one path and use suitable glob files.
Another workaround would be to allow merging snapshots, see https://github.com/restic/restic/issues/3792.
This would also allow to easily solve the "multiple paths" issues as this could be done by auto-merging multiple generated snapshots within one rustic backup run.

After #177 is merged, multiple sources are possible. Rustic only creates multiple snapshots in that case. So this issue now is about merging multiple snapshots into a single one.
I'd propose to add a backup --merge option which creates one single snapshot in the case of multiple sources.

See #289 for an example how to use globs to filter a backup source such that it results in the same snapshot as multiple sources (i.e. same snapshot content, only the "paths" field in the snapshot file is different) .

Actually multiple sources are already WIP in #458 , so I'd like to change the scope of this issue to just add an merge command which is able to merge snapshots. This is also WIP, see #411


New widget: PasswordInput

Context
When users need to enter their password, there is no dedicated widget for this use case.
The TextBox widget displays the password, which is sensitive data.
Problem description & Solution
Create a new widget that displays an echo character instead of the entered text.
For security reasons, the variable holding the password should be set to 0s or dropped after the caller checks against the entered password (maybe even the memory area holding the password could be encrypted somehow)
Examples and MockUps
PasswordInput::create().build(ctx)

The password input could be implemented as extension of the TextBox.
e.g.
TextBox::create().mask('*').is_password(true)

I think modifying the current code of TextBox is a bad idea (it adds one or more responsibility).
The new widget would be just a wrapper on top of TextBox, only it should mask the input text only, otherwise, it would just call the children TextBox.
Or extract the common functionality into a separate widget/behavior, like BaseInput. and use the extracted behavior in the two widgets.

My intention to reduce duplicated code. I was not sure if there is a good way to wrap the TextBox in a PasswordBox, because it has only a text property that is used to display the text and is changed instant by text input. Therefore my idea was to introduce a display_text property, that is only that what is displayed.
I like your idea to extract the text input behavior, that could be a good solution l, also for other new text input widgets 🙂.

I'm thinking of moving the current logic of TextBox into a separate widget/behavior which manipulates the parent text property, and in TextBox just make it as a child and add
.editor(TextEditor::create()).
Thus we can share the same functionality across different widgets.
Users can implement their own editors.
Adding new text related widgets should be easy as one two three.
I will play around with this and make a PR.

@kivimango any progress with your playground?
I would like to use this, too!

@kivimango any progress with your playground?
Not yet, I'm currently writing my own app, but I would like to make it in the next few days (maybe a week).
I will let you know here or on the chat, or you can check the pull requests frequently.

@kivimango
... but I would like to make it in the next few days (maybe a week).

I will work on my code and will postpone the login dialog until i can implement it with this upcoming widget.
Maybe this can be wrapped with an overlay, combined with an image (roughly mimic the OS-default login windows?)


VR seems distorted compared to normal render

Hey, first of, thanks for making this!
I am trying to make a model out of some stuff here on my table. Ive been running into all sorts of issues with the StfM part.
But thought I got that working by now.
However, while the render on the desktop look "perfectly" ok (in the sense that for instance the amanite mushrooms have sort of the same shape as in reality):

The render in vr looks weirdly diagonal/compressed/something?
I guess this is something in splatapult given that the desktop render seems ok?

The VR looks a bit more slanted in the VR glasses btw

Btw, I did not have this with other reconstructions from colmap. This seems to happen specifically with the "undistorted" images and reconstruction. This because the camera model that I need in colmap for actual feature matching is not supported in splatapult

Hey, I think this might be an issue with openxr support, rather then anything wrong with your data.  What headset are you using? Also, which openxr runtime are you using? are you running using Oculus App, or SteamVR?
Can you run with the -d flag on the command line?  that will print out some info that might help me debug this.  can you attach that output to this ticket?

Hmm, you are probably right.
Im using a valve index with steamvr.
But as I was running it now it seems to have fixed itself...
The same model that was giving me problems before now seems good.
So I guess Ill close this issue. If the problems return Ill make sure to get the debug output immediately.


Dashboard style guide and styles fixes

Ref #957

Codecov Report

Merging #975 into master will increase coverage by 0.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #975      +/-   ##
==========================================
+ Coverage   62.43%   62.44%   +0.01%
==========================================
  Files         109      109
  Lines        5963     5965       +2
  Branches      731      731
==========================================
+ Hits         3723     3725       +2
- Misses       2095     2096       +1
+ Partials      145      144       -1

Impacted Files
Coverage Δ

saleor/dashboard/urls.py
100% <ø> (ø)
:white_check_mark:

saleor/dashboard/views.py
54.16% <50%> (-0.38%)
:x:

saleor/core/utils/random_data.py
83.98% <0%> (+0.39%)
:white_check_mark:

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 2e24b16...5644581. Read the comment docs.

@benekex2 just one thing missing: add dropdown example in contextual menu to style guide


Missing Twig Extension?

I am getting a twig syntax error ('Unknown "embed" function') when I attempt to use the following line in twig:
@font-face {
            font-family: 'FuturaLight';
            src: url('{{ embed('/fonts/FuturaPT/FuturaPT-Light.ttf') }}' );
        }

I don't see the 'embed' function defined anywhere in endroid/pdf. Did it perhaps get left out? I am using, 1.0.8?
thx much!

You're right. I refactored it out of the PDF library but forgot to require it. Should work in 1.0.9.


throwing inside an effect leads to unexpected behavior

Describe the bug
When throwing inside an effect, it causes some cleanup-functions to not run. This state can lead to unexpected behavior: p.ex when showing new children, they will still be under the same owner as the thrown effect, which causes any signal set inside these children to trigger the thrown effect.
Your Example Website or App
https://playground.solidjs.com/anonymous/2999ff62-09ed-4b09-88a9-60541c06109f
Steps to Reproduce the Bug or Issue

press count-button
notice how nothing gets logged
press hide-button
press fail-button
press hide-button
press count-button
notice how it triggers the effect

Expected behavior
As a user I expected the signal inside child to not trigger an unrelated effect that has thrown
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

this was closed?
is this expected behavior?


Spike: Run client in browser WASM PoC

Why
We want to make Lace (which runs in the browser) "Mithril aware", which means that it needs to be able to verify Mithril certificates.
This feature will provide support for light wallet integration with Mithril: retrieve the Utxos of a limited set of addresses with a cryptographic proof.
What
We need to explore the usage of the Mithril client in the browser, which is the first mandatory step toward integration with Lace.
Our first objective is to verify a Mithril certificate in the browser. We want to know if this is possible, and we also want to get a better understanding of what it requires on our end (new developments, how to deliver software, ...)
How

[x] Compile a "light" binary in WASM that embeds the STM library and verifies a multi-signature (can be hard-coded)
[x] Compile a "light" binary in WASM that embeds the Ed25519-Dalek library and verifies a genesis signature (can be hard-coded)
[x] Compile a "light" binary in WASM that downloads and verifies the whole certificate chain
[ ] Compile the client in WASM

The PoC has been pushed on the branch ensemble/1254-poc-wasm-client.
The README file to run the PoC is available here:
https://github.com/input-output-hk/mithril/blob/ensemble/1254-poc-wasm-client/poc_wasm_client/README.md
The PoC is plugged in the certificate modal popup of the explorer:

Which links to the page to verify the certificate:

Hi @curiecrypt and @iquerejeta, we have modified the STM library in order to make it compile in WASM as explained in this commit: https://github.com/input-output-hk/mithril/commit/858f0162a6fe4049759a161749a9bd88fa0a0ed8
The aggregate_verify BLST function was not found by the compiler, and we received this error:
Build error with BLST:
error[E0599]: no method named  found for struct  in the current scope

Do you have any idea of what could be the problem?


How to drag and drop any object into the tree

Hi,
I am looking for a way to make angular-ui-tree to accept items from other sources than angular-ui-tree-instances. I am not sure why It doesn't react, the callbacks.accept isn't even called.
Any ideas? Of course I realize that I will have to create something that angular-ui-tree accepts as a source.

Hi nicklasb,
Did you found any solution? We are looking on same functionality. If you found something, please share with us.

Hi @maliseenko,
No, not yet. I am just now looking at the UiTreeHelper.eventObj(e), but I am honestly not sure how it works. It is quite extensive, the drag'n drop implementation of UI-tree.

Hm. It seems like the tree has some internal functionality for this. It has an internal variable called dragElm that is set in dragStart and then referred to in dragStop.
I am not sure how to get around that. Not sure why that isn't passed by the dragevent.dataTransfer.get/setData instead, then it could be provided from outside.

To basically somehow break into the trees internal scope and set it seems ugly.

However it seems like it is possible to drag'n drop between trees, I don't get that really.

Actually, there seem to be a small bug in dragStop.
It calls bindDrag each time something is dropped, which means that after having dragged and dropped something 10 times, it is called 10 times after each drop. Which seems a bit unnecessary.
Or at least that seems to be the issue.

Just mentioning that I resolved this one by making the outside source a tree as well.
However, I do not think that that should have been necessary.
Closing, at least for my part.


Added 2 updates

no recycle bin limitation
clarity that the Files Tab just needs to be refreshed once after the rename.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@kaarins PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


v0.4.0: docker run in system-docker hangs

sudo system-docker run nginx
After the image downloads, the container never starts.

My own issue. I forgot to pass in -d.


GUACAMOLE-926: Batch Connection Import

There's still a bit of cleanup to be done here, but the functionality is essentially done, so if people want to have a look, I'd appreciate it.
This PR implements a batch import UI for connections, allowing an admin to provide a CSV, YAML, or JSON file with a list of connections, which will be submitted to a modified PATCH implementation on the backend that now allows creation of bulk directory objects.

How is the "Row #" heading intended to be interpreted when importing from JSON or YAML?

How is the "Row #" heading intended to be interpreted when importing from JSON or YAML?

It's the index (+1) within the array of connection objects in the file. If you have a different suggestion for the header I'm down to change it.

Ok, I think this is now cleaned up enough to be ready for review. Looking forward to hearing people's thoughts, nitpicks, etc.

I've always got some good nits to pick.

Ok, I think these should all be resolved now...

I'm seeing this error on CI (though not locally)
Error:  Failed to execute goal com.github.searls:jasmine-maven-plugin:3.0-beta-02:test (default) on project guacamole-common-js: The jasmine-maven-plugin encountered an exception:: session not created: This version of ChromeDriver only supports Chrome version 112
Error:  Current browser version is 111.0.5563.110 with binary path /usr/bin/chromium
Error:  Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
Error:  System info: host: 'a24ad6ba7e99', ip: '<IP_ADDRESS>', os.name: 'Linux', os.arch: 'amd64', os.version: '5.15.0-1034-azure', java.version: '1.8.0_342'
Error:  Driver info: driver.version: ChromeDriver

Hopefully it goes away by itself soon...

Updated the connection icon to something a bit more distinct. (thanks to @mike-jumper for this one)

Converting to draft while it give it one more once-over.

Looks good to me! Any further comments @necouchman?


add Log.cacheLock.RLock(),  fix #4369 and #4368

add Log.cacheLock.RLock(),  fix #4369 and #4368

LGTM :+1: @pauldix should take a look though.

This has been fixed in the most recent changes by @jwilder.
Thanks @runner-mei for the contribution. If you believe the code still needs changes please let us know.


Thread 'main' panick over 0.0 floating point number

Reproducing the behavior
HVM panics when encountering a 0.0 float. To test, try to run (parse) the following hvm code:
@main = 0.0

This will run into:
assertion failed: expo >= -63 && expo <= 63
To get to this error from bend, it is enough to write:
def main:
  return 0.0

This code passes bend check! Note that it is enough to write 0.0 anywhere in your bend code to run into this error.
Obviously this is mightily confusing for developers.
System Settings
Bend 0.2.33
Additional context
No response

This was already fixed in HVM version 2.0.14, please update.


Put ScalaTags and ScalaDom in the 'Selected' libraries by default

It appears as if scalatags and scaladom are included by default, but there isn't any indication in the UI.  It would be nice if they were just added to the 'Selected' section by default.  If it its not possible to remove them as a dependency, can we just show them under 'Selected' but not allow them to be removed?

This is how it was at some point but I removed it to keep the UI simpler. The Fiddle helper depends on these libs, so the correct action would be to make the helper optional.

I'm fine with the idea of the Fiddle helper library being optional, as long as Scala-Tags and Scala-Dom get added to the 'Available' list to help reduce confusion.