Added adapter filter

PR Summary
Fix #274
Fix #368

Removed duplicates from path list, so that same resources would not be processed multiple times;
re-enabled WMI provider
Added filter for adapters, so that in default scenarios 'List' operation on adapters is not executed, therefore reducing time.

Usage: dsc.exe resource list [OPTIONS] [RESOURCE_NAME] [ADAPTER_NAME]

Arguments:
  [RESOURCE_NAME]  Optional filter to apply to the list of resources
  [ADAPTER_NAME]   Optional adapter filter to apply to the list of resources

Options:
  -d, --description <DESCRIPTION>  Description keyword to search for in the resource description
  -t, --tags <TAGS>                Tag to search for in the resource tags
  -f, --format <FORMAT>            The output format to use [possible values: json, pretty-json, yaml]
  -h, --help                       Print help

Examples:

dsc resource list same as dsc resource list * - show all native resources, providers, but not provider-based resources (fastest);
dsc resource list *Microsoft* - same as previous but also apply *Microsoft* filter;
dsc resource list * * - show all native resources, providers, and provider-based resources (slowest);
dsc resource list * *PowerShell* - show all native resources, providers, and all resources of providers that match *PowerShell* filter
dsc resource list *MSFT_PackageManagement* *PowerShell* - same as previous but also apply *MSFT_PackageManagement* filter to resource types;

Added tests.

After trying out your branch, we should discuss some user experience options:

Currently, to use an adapter, you have to specify * or some resource name.  I would prefer something like dsc resource list --adapter Microsoft.DSC/PowerShell and have it show all the PowerShell resources
When an adapter is specified, should the list ONLY contain resources for that adapter.  I would think this would be expected unless you use a wildcard for the adapter, of course.

cc @mgreenegit, @michaeltlombardi

My thoughts:
1.

Currently, to use an adapter, you have to specify * or some resource name.  I would prefer something like dsc resource list --adapter Microsoft.DSC/PowerShell and have it show all the PowerShell resources

It is shorter to type * for type filter than --adapter of the named parameter. I'd leave it as is.

When an adapter is specified, should the list ONLY contain resources for that adapter.  I would think this would be expected unless you use a wildcard for the adapter, of course.

I agree with this; it is more intuitive than current behavior.

My thoughts: 1.

Currently, to use an adapter, you have to specify * or some resource name.  I would prefer something like dsc resource list --adapter Microsoft.DSC/PowerShell and have it show all the PowerShell resources

It is shorter to type * for type filter than --adapter of the named parameter. I'd leave it as is.

We would have a -a short name for --adapter.  Particularly on Unix where you have to single-quote the wildcard so that it doesn't get globbed, my preference is to have adapter be a named arg and not require *.

Currently, to use an adapter, you have to specify * or some resource name.  I would prefer something like dsc resource list --adapter Microsoft.DSC/PowerShell and have it show all the PowerShell resources
When an adapter is specified, should the list ONLY contain resources for that adapter.  I would think this would be expected unless you use a wildcard for the adapter, of course.

Updated code and PR description for both points.


[BSO] Mortimer doesnt ping when trip returns

🐛 Bug Report
Title.
Very easy to be idle for an hour+ due to this.

Fixed


Need help understanding how the plugin works

Hey, i need help understanding how u coded this plugin because i want to make my own plugin related to adding nodes in the graph aswell but i have no idea where to start and i haven't gotten much help from the discord aswell. I would really appreciate it if i could get some help from you. Thank you very much!

Hi @BlitzVI.
The plugin is inspired from drPilman's obsidian-graph-nested-tags plugin.
They both work on the same way:
Obsidian uses functions to render its tabs. Depending of the context, the "obsidian engine" will provide data. In the graph tab, those data are the graph nodes the plugin will mutate by adding new "tag nodes" (and link them to the existing nodes).
This mutation is made through a custom function that will be executed before the Obsidian renderer.
We replace the Obsidian renderer by our custome one. Obsidian will think he's calling its render, but he doesn't know he's actually calling our custom one. We just need to alterate the data and not the whole process, so our "custom renderer" will then call the Obsidian original renderer and pass the mutated data.
Here's an "example code".
In normal case:
// Obsidian is calling its renderer to render the tab.
function obsidianRenderer(data) {
    // Do its work. We don't care about how it works.
}

With a "prerenderer":
// Original renderer
function obsidianRenderer(data) {
    // Do its work. We don't care about it.
}

// Our custom renderer
// We reassign our custom renderer to the "Obsidian engine" with Object.setProperty(...);
function customRenderer(data) {
    // We mutate the data.
    // ...

    // As we just want to alterate the data, we call the original renderer with out mutated data.
    return obsidianRenderer(data);
}

It's kinda tricky to edit this kind of part of Obsidian since there is no real documentation about it. We directly mutate the Obsidian app object instead of using the dev API.
Don't forget to keep a copy of the original renderer function. If you unload the plugin, you need to reset the renderer to its original version.
If you need more details, feel free to ask here. If not, you can close the issue.
Happy coding!

Hi @BlitzVI. The plugin is inspired from drPilman's obsidian-graph-nested-tags plugin.
They both work on the same way: Obsidian uses functions to render its tabs. Depending of the context, the "obsidian engine" will provide data. In the graph tab, those data are the graph nodes the plugin will mutate by adding new "tag nodes" (and link them to the existing nodes). This mutation is made through a custom function that will be executed before the Obsidian renderer. We replace the Obsidian renderer by our custome one. Obsidian will think he's calling its render, but he doesn't know he's actually calling our custom one. We just need to alterate the data and not the whole process, so our "custom renderer" will then call the Obsidian original renderer and pass the mutated data.
Here's an "example code". In normal case:
// Obsidian is calling its renderer to render the tab.
function obsidianRenderer(data) {
    // Do its work. We don't care about how it works.
}

With a "prerenderer":
// Original renderer
function obsidianRenderer(data) {
    // Do its work. We don't care about it.
}

// Our custom renderer
// We reassign our custom renderer to the "Obsidian engine" with Object.setProperty(...);
function customRenderer(data) {
    // We mutate the data.
    // ...

    // As we just want to alterate the data, we call the original renderer with out mutated data.
    return obsidianRenderer(data);
}

It's kinda tricky to edit this kind of part of Obsidian since there is no real documentation about it. We directly mutate the Obsidian app object instead of using the dev API.
Don't forget to keep a copy of the original renderer function. If you unload the plugin, you need to reset the renderer to its original version.
If you need more details, feel free to ask here. If not, you can close the issue. Happy coding!

Hey tysm for the detailed reply! I've yet to read it but I was wondering if there's another way I can contact u like on discord or something?

Yes, no problem!
You can contact me on my email<EMAIL_ADDRESS>or my discord account bastian.lucas!

Yes, no problem! You can contact me on my email<EMAIL_ADDRESS>or my discord account bastian.lucas!

Hey so I just sent you a request on discord again tysm for the help!


FX Intraday

Adds interval support for foreign currency api

Build fails due to not having publish key for gradle. Can confirm using this build from locally built jar from POM file.


Add JWT authentication

Description
Please include a summary of the changes and the related issue(s) this PR addresses.
Related Jira(s)

[Jira ID]

Checklist

[ ] I have read and followed the PR naming convention
[ ] My code follows the code style of this project.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Tests
Include how to test this code change

Add package vào requirements chưa my fren


Update FAQ with ruby EOL version

The FAQ currently lists the last supported EOL version of Ruby as 1.9.3:

We will target the latest the EOL Ruby, currently that is 1.9.3.

Can the mentioned version be updated to 2.0.0 as per the Ruby docs?
The current 1.9.3 statement on the FAQ page is confusing for people who don't spend a lot of time in the Ruby ecosystem but sometimes want to contribute back to the plugins.  It's hard to know what to do with build/test failures.

@nathanhruby we have updated this and clarified our stance to support non EOL versions and will attempt to have EOL.max but in cases where you need to break compatibility for a justifiable reason it is ok in a major release of the gem. This should not really be an issue really as people should be using the embedded ruby in sensu and we will certainly keep these versions in mind when dropping version support.


Add reflection hints for field access

This provides the necessary to call Message.MESSAGE via reflection.
Reflective is meant to flag the annotated method as being invoked by reflection on any bean. You can see a usage of this annotation in @EventListener. By adding @EventListener on a bean, Spring AOT automatically registers the necessary reflection hints so that the framework can call this method using reflection.
For more fine grained access, RuntimeHints is an API on top of GraalVM's hint format. The lower-level is RuntimeHintsRegistrar that this PR uses as there's no real declarative way to see that MESSAGE is called via reflection.
Hints are gathered where they are used. In this case, if the controller is not contributed to the application, the hint isn't contributed either. This makes hints registration more modular and flexible.

Many thanks @snicoll!❤


Add a feature to test whether Stardoc support module extensions.

See https://github.com/bazelbuild/stardoc/issues/192.
See logic in
https://github.com/phst/rules_elisp/blob/8606695e977b876ffb38f881f54e50de1606a733/docs/BUILD for prior art.

In https://github.com/phst/rules_elisp/blob/8606695e977b876ffb38f881f54e50de1606a733/docs/BUILD I selectively build the extensions target (for a Starlark file containing module extensions) depending on whether the current Bazel version is 7 or not. Whether this works or not appears to depend mainly on the Bazel version, at least for recent enough Stardoc versions. Happy to switch to a better approach if there's one!

There is, you can detect the required Bazel feature directly: https://github.com/bazelbuild/stardoc/blob/bf441c86274770ea281d21e22292ecdaa6451eaa/stardoc/stardoc.bzl#L88
Let me know if that doesn't work and we can reconsider this.

It works, thanks!
https://github.com/phst/rules_elisp/commit/57787964fda190305fc7353e618da089ed3aff4b


2gang switches have a big lags

I have 2gang switches (from 3 different company). Switches works good with Tuya App and integrations with Tuya Cloud to HA.
All switches uses 3.4 protocal version. Switches connected to HA with this integrations works very slow. If I click switch with HA, the switch sometimes change state after 5 second. I selected 2 gang switch with timer in second form in configuration in HA. Sometimes the switches are inactive.
I need help.
Logs:
`Logger: homeassistant.helpers.entity
Source: helpers/entity.py:527
First occurred: December 30, 2022 at 15:14:34 (3873 occurrences)
Last logged: 18:17:14
Update of switch.biuroswiatla_switch_2 is taking over 10 seconds
Update of switch.salonglowne_switch_1 is taking over 10 seconds
Update of switch.salonglowne_switch_2 is taking over 10 seconds
Update of number.salonglowne_timer_1 is taking over 10 seconds
Update of number.salonglowne_timer_2 is taking over 10 seconds`
`This error originated from a custom integration.
Logger: custom_components.tuya_local.device
Source: custom_components/tuya_local/device.py:142
Integration: Tuya Local (documentation, issues)
First occurred: December 30, 2022 at 21:51:55 (839 occurrences)
Last logged: 18:17:00
Failed to refresh device state for Test.
Failed to refresh device state for SalonGlowne.
Failed to refresh device state for BiuroSwiatla.`
`Logger: homeassistant.components.number
Source: helpers/entity_platform.py:797
Integration: Number (documentation, issues)
First occurred: December 30, 2022 at 15:32:29 (1371 occurrences)
Last logged: 18:17:11
Updating tuya_local number took longer than the scheduled update interval 0:00:30`

I experience the same

The same is here on one gang switch with the protocol v3.4

Did you set the protocol explicitly to 3.4, or is it still on auto?  If on auto, the performance may be improved by fixing the protocol to 3.4, which you can do in the device config in the latest version.
I suspect there may still be issues with 3.4, and any errors communicating may be causing the auto protocol selection to go searching the protocol versions again, which will cause delay.

I set the protocol explicitly to 3.4

I'm not sure if it will help with these 3.4 device problems, but the latest change introduces persistent connections, which should improve responsiveness in general.

I described the problem on https://github.com/jasonacox/tinytuya/issues/258
I'm waiting for reply.

Are the lags now fixed as appears to be the feedback on the upstream report?  If so, maybe this needs to be moved to discussions, so others can find it and give ideas about what fixes these 3.4 device lags (rebooting, disabling the built-in HA tuya integration, etc)

I don't have lags now.


[ZEPPELIN-1781] Failed to run the script 'test_zeppelin_pr.py' on Windows 10

What is this PR for?
Fix failure of script execution on Windows 10
What type of PR is it?
[Bug Fix]
Todos
What is the Jira issue?
ZEPPELIN-1781
How should this be tested?
Run 'test_zeppelin_pr.py' on Windows 10.
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Looks like the Python2 CI test failed, could you take a look?
16/12/09 15:15:01 INFO PySparkInterpreter: File /tmp/zeppelin_pyspark-9170445727539307406.py created
16/12/09 15:15:01 INFO SparkInterpreter: Sending metainfos to Zeppelin server: {url=http://<IP_ADDRESS>:4040}
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 132.031 sec <<< FAILURE! - in org.apache.zeppelin.spark.PySparkInterpreterTest
testBasicIntp(org.apache.zeppelin.spark.PySparkInterpreterTest)  Time elapsed: 129.658 sec  <<< FAILURE!
java.lang.AssertionError: expected:<SUCCESS> but was:<ERROR>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:144)
	at org.apache.zeppelin.spark.PySparkInterpreterTest.testBasicIntp(PySparkInterpreterTest.java:128)

@felixcheung
I opened the PR again, but there was errors elsewhere. Zeppelin test seems unstable.

So there were 2 runs
The older run https://travis-ci.org/apache/zeppelin/jobs/182613697 failed with Spark cluster tests
The newer run https://travis-ci.org/apache/zeppelin/builds/183250971 failed with cassandra tests
Given that and no code changes between, I think we could attribute the failures to flaky test.

@cuspymd have you tested this with Python 2.x and Python 3.x? I'm not sure we have automated test covered for Python + Spark on both.

@felixcheung The script 'test_zeppelin_pr.py' could be run on only Python 2 before this PR.
Anyway, I made additional modifications to run in python 3 as well.
And  the script 'test_zeppelin_pr.py' is for development, not for ptyhon interpreter.
I can't found a unit test about the scripts of 'dev' folder.
Can you let me know if it exists, or do you think you need to test the scripts of 'dev' folder in the future?

ah, sorry for missing this earlier. I didn't realize this is dev/test_* - these are test scripts that do not have automated tests

sorry I didnt see this. LGTM, CI passed,
merging if no more comment

merged to master. thanks!


Multi-terms Aggregation Performance Optimization

Starting this thread to discuss ideas for optimizing multi-terms aggregation.
Sample query:
{
  "size": 0,
  "aggs": {
    "important_terms": {
      "multi_terms": {
        "terms": [
          {
            "field": "process.name"
          },
          {
            "field": "event.id"
          },
          {
            "field": "cloud.region"
          }
        ]
      }
    }
  }
}

Current flow overview:
For each document, increment the count of composite (formed using multiple fields) bucket.
Initial ideas for optimization:
Trying out to see if for certain scenarios, will it make sense to start  the execution from the postings data instead. For example, taking into account the possible buckets and then finding intersection among different buckets to find intersection of documents. Finding doc intersections for different fields is something which we can experiment out to find if it makes any advantage than the current workflow in terms of performance.

So I started thinking of some ideas.
One of the ideas which came was to take intersection of document set for postings data for 2 fields (in case there are 2 fields involved in a multi-term aggregation), but when doing some basic math around time complexity, it turns out that the resultant time complexity might be greater than the present approach of iterating though all documents in a a match-set. Also, taking intersection of 2 postings data only works for match-all top level query with no document deletes, so not the  direction worth approaching.
Let me see if I can find more ways to see possible optimizations.

Linking https://github.com/opensearch-project/OpenSearch/pull/14993 here as this PR contributes to improving multi-terms aggregation.


runtime: confusing panic on parallel calls to yield function

Go version
go1.23.0-windows-amd64
Output of go env in your module/workspace:
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\hauntedness\AppData\Local\go-build
set GOENV=C:\Users\hauntedness\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=rangefunc
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\hauntedness\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\hauntedness\go
set GOPRIVATE=
set GOPROXY=https://goproxy.cn,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.23.0
set GODEBUG=
set GOTELEMETRY=on
set GOTELEMETRYDIR=C:\Users\hauntedness\AppData\Roaming\go\telemetry
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=D:\temp\dot\go.mod
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\HAUNTE~1\AppData\Local\Temp\go-build2719328347=/tmp/go-build -gno-record-gcc-switches

What did you do?
package main

import (
	"fmt"
	"sync"
)

func main() {
	for i := range WaitAll(10) {
		fmt.Println(i)
	}
}

func WaitAll(total int) func(yield func(i int) bool) {
	return func(yield func(i int) bool) {
		wg := &sync.WaitGroup{}
		wg.Add(total)
		for i := range total {
			go func(j int) {
				defer wg.Done()
				if !yield(j) {
					panic("Shouldn't be broken.")
				}
			}(i)
		}
		wg.Wait()
	}
}

See https://go.dev/play/p/_X0iHMy6lH1
What did you see happen?
==================
panic: runtime error: range function continued iteration after loop body panic
goroutine 21 [running]:
main.main-range1(0x2)
D:/temp/dot/play/iter.go:9 +0xf3
main.main.WaitAll.func1.1(0x2)
D:/temp/dot/play/iter.go:21 +0x8c
created by main.main.WaitAll.func1 in goroutine 1
D:/temp/dot/play/iter.go:19 +0x8c
exit status 2
What did you expect to see?
No panic

Related Issues and Documentation

cmd/compile: Go1.22RC1 compiler crash when using GOEXPERIMENT=rangefunc #64930 (closed)
sync.WaitGroup panic trouble me #39013 (closed)
cmd/compile: panic during generic deadcode #56777 (closed)
    runtime: waitforsingleobject wait_failed #65255 (closed)
affected/package: sync #50544 (closed)
cmd/compile: ICE compiling rangefunc for < 1.23 in combination with Cgo #67497 (closed)
testing: inconsistent behaviors between running tests directly and after compiling the code first #59879 (closed)
testing: "panic: Log in goroutine after Test..." is unreliable due to lack of synchronization on t.done #67701
panic: runtime error Crash in Orphaned gorutines cant be handled #47261 (closed)
cmd/objdump: panic: runtime error: index out of range [1048574] when disassembling empty infinite loop #36570 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

I can recreate this on my laptop, but only if I use go run -race.
It's hard to see how parallel calls to a yield function could work, but we should see if we can produce a better error message for this case.

you are calling yield from a separate go routine, so the panic seems to be appropriate; not least as there are no guarantees when the separate go routine is scheduled, so well after the main go routine quickly finished the loop. The message looks clear and correct to me.

CC @dr2chase

you are calling yield from a separate go routine, so the panic seems to be appropriate; not least as there are no guarantees when the separate go routine is scheduled, so well after the main go routine quickly finished the loop. The message looks clear and correct to me.

But there is a (*sync.WaitGroup).Wait(), why would the main goroutine finished without respect the waitgroup?
And let me add more comment.
The same code works well for go 1.22.6
And also it works well if the code changed into below:
func main() {
	WaitAll(10)(func(i int) bool {
		fmt.Println(i)
		return true
	})
}

remove everything related to the WaitGroup then it becomes hopefully clear that you are creating Go routines in the range body that then call yield. The wait group doesn't matter; misplaced yield call? Maybe you want to discuss this in the forum, what you intend to achieve here?

remove everything related to the WaitGroup then it becomes hopefully clear that you are creating Go routines in the range body that then call yield. The wait group doesn't matter; misplaced yield call? Maybe you want to discuss this in the forum, what you intend to achieve here?

I want to simply the WaitGroup boilerplate. I think the wait group does matter, because I want it to wait all of the yield call.

@thediveo I agree that some panic would be acceptable for this program, but "range function continued iteration after loop body panic" is just inaccurate.  The loop body did not panic.

@hauntedness Why do you want to call the yield function in parallel in different goroutines?

The requirement is that a yield function may be called if all calls to the yield have returns true and f has not terminated.
This bans parallel calls. (Not calls from multiple Go routines.) WaitAll is violating this. For parallel calls you can still write:
WaitAll(10)(func(i int) bool {
	fmt.Println(i)
	return true
})

A panic happening here is WAI.

I agree that some panic would be acceptable for this program, but "range function continued iteration after loop body panic" is just inaccurate. The loop body did not panic.

I am about 90% sure this is the state variable for the loop being being set to the state that detects early exits (panics) still being set when a parallel call happens and it is read. A different wording seems appropriate.

@hauntedness Why do you want to call the yield function in parallel in different goroutines?

I want less boilerplate...
And I did this in go 1.22 and that time I ever checked the orginal propose. I remember the spec did say something related to multiple goroutine but it's not forbiden doing that.

The requirement is that a yield function may be called if all calls to the yield have returns true and f has not terminated.
This bans parallel calls. (Not calls from multiple Go routines.) WaitAll is violating this. For parallel calls you can still write:
WaitAll(10)(func(i int) bool {
	fmt.Println(i)
	return true
})

A panic happening here is WAI.

I agree that some panic would be acceptable for this program, but "range function continued iteration after loop body panic" is just inaccurate. The loop body did not panic.

I am about 90% sure this is the state variable for the loop being being set to the state that detects early exits (panics) still being set when a parallel call happens and it is read. A different wording seems appropriate.

Thanks for those information but it will not always panic. eg. Below doesn't panic
func main() {
	for i := range WaitAll(10) {
		_ = i
	}
}

@timothy-king
Can you give more illustration? Which point the WaitAll violate? The waitgroup guarantee all the yield call even it panics. The yield call may return false, but here it doesn't. And f ofcourse would not terminate ealier than yield
The requirement is that a yield function may be called if all calls to the yield have returns true and f has not terminated.

The requirement is that a yield function may be called if all calls to the yield have returns true and f has not terminated.

There is to the best of my knowledge no specification given as to the temporal behavior of overlapping yields and this probably includes the invisible code inserted behind the scenes to check for out of range yield calls. This might fit in with the race detector getting tripped.
If I understand this correctly then your code happens to work on some systems some times, but might have never been guaranteed by the spec to be supported.

@hauntedness The rule that @timothy-king stated is "a yield function may be called if all calls to the yield have returns true and f has not terminated."
Your program does not obey that rule.  It calls the yield function even though a previous call to the yield function has not yet returned.  That is, it makes multiple calls to the yield function in parallel.
The fact that in some cases your program does not panic does not mean that your program is following the rules.

Ok, you mean the yield calls are not independent, they must be called sequential or at least sequential access some internal shared state right?
As it is supper hiden rule here,  do we consider to add a vet? I believe lot's of people would do it similar。

Yes: you can't call yield until the previous call to yield has returned.  In the language spec this is written as (https://go.dev/ref/spec#For_statements):

After each successive loop iteration, yield returns true and may be called again to continue the loop.

I think it's too early to say whether we need a vet check for this.  We only want vet checks for errors that are frequently made.  This strikes me as unlikely to be frequent.
I also don't know how we could write an accurate vet check here.

Thanks for those information but it will not always panic. eg. Below doesn't panic

It should. Try increasing the constant to a few hundred thousand and turning on -race.

Which point the WaitAll violate?

For WaitAll(10), after the second iteration there will be two newly go routines. So 3 goroutines: the original, the goroutine created for j==0, and the goroutine created for j==1. Now suspend the original go routine, schedule the j==1 goroutine and execute to the body of the yield (right before fmt.Println), and now schedule j==1 goroutine, and execute until it calls yield. The call the yield from j==0 has not returned true yet. This is a violation.

There is to the best of my knowledge no specification given as to the temporal behavior of overlapping yields and this probably includes the invisible code inserted behind the scenes to check for out of range yield calls.

The implementations definitely believe this is the requirement. The spec hints at this (everything after "If yield is called before f returns," is calling out specific conditions). IMO could/should spell this out more. (IMO the even bigger hole in the spec is that f is required to preserve panicking from yield. That is totally underspecified, and the implementation chooses to panic right now.)

Ok, you mean the yield calls are not independent, they must be called sequential or at least sequential access some internal shared state right?

Correct. The code below sequences yield calls correctly (even if it 'misses the point'):
func WaitAllCorrect(total int) func(yield func(i int) bool) {
	return func(yield func(i int) bool) {
		wg := &sync.WaitGroup{}
		wg.Add(total)
		var mu sync.Mutex // guards yield and done
		var done bool
		for i := range total {
			go func(j int) {
				defer wg.Done()
				mu.Lock()
				defer mu.Unlock()
				if !done && !yield(j) {
					done = true
					panic("Shouldn't be broken.")
				}
			}(i)
		}
		wg.Wait()
	}
}

As it is supper hiden rule here, do we consider to add a vet? I believe lot's of people would do it similar。

Maybe. We discussed this before the release. The discussion concluded that we need more evidence of what to check for before creating a proposal/checker.
As for "super hidden", we can advertise this better in the spec or a future blog post.

There is to the best of my knowledge no specification given as to the temporal behavior of overlapping yields and this probably includes the invisible code inserted behind the scenes to check for out of range yield calls.

The implementations definitely believe this is the requirement. The spec hints at this (everything after "If yield is called before f returns," is calling out specific conditions).

I actually meant what you so succinctly put into words, where I utterly failed with mine.

CC @golang/compiler

Do I understand this right, that multiple yield functions can not be processed concurrently and this is by design?

@lmittmann I'm not sure precisely what you are asking.  A single iterator function, that takes a yield function as an argument, can't call that yield function concurrently.  There is no restrictions on different yield functions passed to different iterator functions.


Add textDocument/convertDocumentation request

Support documentation live preview in Swift files by handling requests to convert documentation using Swift DocC.
This PR adds a new request method textDocument/convertDocumentation that responds with a JSON encoded RenderNode created using Swift DocC's ConvertService. This request has two parameters:

A text document for which to convert documentation
A position within the text document that will be used to find the nearest documentable symbol

The request is only supported on macOS and Linux until Swift DocC can be made to support Windows.

@swift-ci please test

@swift-ci please test

@swift-ci please test windows platform

@swift-ci please test

@swift-ci please test windows platform


create branch -> change coding -> switch back to master -> error

When create a new branch and do a change in an Interface (additional optional paramter) ...activate all things fine... Push the code to remote repo
Now switch back to master (without merge) the pull get an esxception that the package cannot created. I want to have the old inteface implementation ... Mayby i missunderstood something...

hi mr. Red,
can you paste a screenshot of the error here in the issue?
perhaps if you also can create a repository with the objects needed to reproduce the error? it sounds like just a dummy interface is needed.

@rednose84 can you help providing additional information?

closing issue, @rednose84 feel free to open a new issue with the same problem, please just provide more information(see above)


Plugin DependencyManagement overrides Wiremock dependencies

Version 5.0.0 of your excellent plugin (thanks for all your work) promises to be decoupled from the WireMock version itself. However, the plugin's POM still contains a dependencyManagement section that overrides some of WireMock's own dependencies (e.g. the asm 7.0 dependency from WireMock 2.25.1 is overwritten with version 5.2 in release 5.0.0 of the plugin).
Is there any particular reason why the plugin manages some of WireMock's transitive dependencies?

Nice catch and interesting finding btw. Thanks for flagging this. With dependency scope provided, using dependencyConvergence rule of maven-enforcer-plugin doesn't make much sense, as we won't have much control over the transitive dependencies either. I removed dependencyManagement section and released version 5.0.1.


Add an scenario to upload a file.

As part of a project in Angular and JAVA we are facing some difficulties to upload a file from the Angular side to JAVA.
Maybe an example in this projects could help other developers to see how it's done.

relates to #8


Locked wallet is unlocked after restart

I have two wallets open within Sparrow. If I lock one of them (View - Lock Wallet) then close the application, when I reopen the Sparrow the locked wallet is unlocked.

This is expected behavior. I don’t think most users would want their wallet to be locked just after they have entered their password to open it - if it was, they would need to enter their password twice. It’s easy enough to lock with the keyboard shortcut.


Update README - add screenshots

Add screenshots
Update blog/readme, explain how code was made REST and SOAP, background runner

Updated.


not work tts sonos

`Logger: homeassistant.components.automation.svitlo_kukhnia_single
Source: helpers/script.py:409
Integration: Автоматизація (documentation, issues)
First occurred: 19:24:22 (6 occurrences)
Last logged: 19:51:17
Світло Кухня (single): Error executing script. Service not found for call_service at pos 2: Unable to find service tts.google_translate_say
Світло Кухня (single): Error executing script. Service not found for call_service at pos 2: Unable to find service tts.google_translate`
`alias: Світло Кухня (single)
description: ""
trigger:

platform: event
event_type: mega.binary
event_data:
entity_id: binary_sensor.megad3_12
type: single
condition: []
action:
service: light.toggle
target:
entity_id: light.dimmer_kitchen_led
data:
brightness: 255
transition: 3
service: script.text_to_speech_on_sonos
data:
entity_id: media_player.stolovaia
message: упс
max_wait: 5
mode: single`

Hi @amgstone , When the script.text_to_speech_on_sonos script was created from the blueprint, you were able specify the text-to-speech provider to use (and it defaults to Google Translate). From the above error it seems to indicate that either the Google Translate text-to-speech provider isn't installed in your Home Assistant or that it isn't setup to use the name tts.google_translate. Can you confirm?

So looks like in your configuration you changed the Google Text-To-Speech to be called google_say . . . based on this:

So when you create a script from my blueprint, use the google_say instead of the default of googe_translate . . . it is done on this screen you sent:

good!!!!


Integrating 3rd-party validation libraries: Open up the design of ValidationVisitor

Back in 2015, I had a discussion with @rynowak was very helpful in getting some changes into the MVC validation pipeline that would make it easier for 3rd party validation libraries to integrate with MVC's validation infrastructure (#1260), but unfortunately there are still several blocks that make this difficult.
The main issue is that the MVC validation pipeline does not run model-level validators if any property-level validators have failed for the current model object. This behaviour is not customizable/overridable as the ValidationVisitor class is made almost entirely of nonvirtual, private methods.
For example, the FluentValidation library executes all rules in one go after model binding has occurred (ie it validates already set property values, rather than one property at a time like DataAnnotations). Unfortunately this does not work well if you mix DataAnnotations and FluentValidation in the same project. If a DataAnnotations attribute validator fails, then FluentValidation will never be executed as the property-level DataAnnotations rule prevents model-validators rules from running.
Current workarounds:

Bypass the ModelValidatorProvider Api entirely and instead implement a custom IObjectModelValidator that does the work. Not ideal as you lose many of the benefits of the ModelValidatorProvider api (eg the ability to mix multiple validation libraries)
Fork the code for the ValidationVisitor and maintain separately. Not ideal for obvious reasons

Proposal: Modify ValidationVisitor to either:

Add a property to control whether property-level errors should prevent model-level validators for running
Open up the class to make the methods protected virtual instead of private (and add protected property getters for the private fields) so 3rd party validation libraries can add this logic in themselves if option 1) is not something that you feel should be in the core framework.

For option 1, the VisitComplexType method would be modified as follows:
private bool VisitComplexType(IValidationStrategy defaultStrategy)
{
    var isValid = true;

    if (_model != null && _metadata.ValidateChildren)
    {
        var strategy = _strategy ?? defaultStrategy;
        isValid = VisitChildren(strategy);
    }
    else if (_model != null)
    {
        // Suppress validation for the entries matching this prefix. This will temporarily set
        // the current node to 'skipped' but we're going to visit it right away, so subsequent
        // code will set it to 'valid' or 'invalid'
        SuppressValidation(_key);
    }

    // Original check
    //if (isValid && !_modelState.HasReachedMaxErrors)
    //{
    //    isValid &= ValidateNode();
    //}

    // Proposed new check:
    if ((isValid || ValidateComplexTypesIfChildValidationFails) && !_modelState.HasReachedMaxErrors)
    {
        isValid &= ValidateNode();
    }

    return isValid;
}

public bool ValidateComplexTypesIfChildValidationFails {get;set;}

If going with option 2), then all the private methods including VisitComplexType should be made protected virtual, and protected properties with getters would be needed to expose the private fields to subclasses.
I would be happy to submit a pull request for either approach depending on what's preferred.

Would be great to get a response to this. /cc @rynowak @Eilon

Sorry for the delay, I think both of your proposals are reasonable. If you'd prefer to do just proposal one (ValidateComplexTypesIfChildValidationFails) that's fine too.
Feel free to send a PR, and if you don't have a chance, I will get to this before we ship 2.1

Thanks, I've created a pull request that implements both proposals and adds tests. Let me know if you'd like me to make any changes.

I've moved the properties below the ctor as requested. Something went wrong with the PR when merging latest changes from dev so I've recreated the PR (#7075)

Fixed by: 9c59e63 a06d0d0 0ccfe4c 5a6bc3a


Test upgrade from 1.2.7 to 1.4.0

[x] Test the upgrade from 1.2.7 to 1.4.0
[ ] Validate FQDN upgrade

[ ] Work with @raybejjani to have an FQDN policy loaded throughout the upgrade.
[ ] Upgrade to 1.4.0 with the poller enabled and make sure that FQDN policy continues to work

[ ] Document release notes required for upgrade

One particular task necessary for upgrade if we're going to support FQDN poller with v1.4: https://github.com/cilium/cilium/issues/6870

Second test, tried to upgrade from the 1.2 YAML above, again with the same monkey setup, this time with no poller configured in v1.4:
cilium-1.4-no-dnspoller.yaml.txt
FQDN monkey pods restarted once about one minute after upgrade. Log:
fqdn-failure-2019-02-02-01:31:05Z.txt
Pods appear happy after the one failure.

I also tried starting from v1.2 with no DNS proxy rules, then upgrading directly to the v1.4 YAML and sure enough, the toFQDNs rules stopped working. This is expected; upgrade requires the user to intervene in one way or another - either add the DNS proxy rules, or add the DNS poller argument to the Cilium args.


[P000603] Sen. Rand Paul

Sen. Rand Paul:
http://www.paul.senate.gov
Likely contact form URL to start with:
http://www.paul.senate.gov/?p=contact

Hey @crdunwel, it looks like Sen. Paul has changed his form again.  Submissions aren't going through, can you take a look?

Looks like its changed a bit, now at this url: http://www.paul.senate.gov/connect/email-rand, will try to fix it myself

Probably can close this since #1463 was merged?

yep, yaml is working


iOS UTM HV Issues

5026.A
Fedora 37 Workstation arm64 fails to install to hard drive crashes and causes the whole app to crash and cause a device resping and/or reboot upon click install to hard drive on Live ISO mode.  Basic graphical install also yeilds a blank black screen.
I was really impressed at how Fedora 37 ran even on a live ISO.  Fedora 37 and Windows 11 really complements iPadOS really well.  I hope to see in a future update that it is alas possible to install and boot Fedora arm64 from a virtual disk drive some day.
5026.B
Some bug reports when using Win11 on UTM HV 4.1.5;
The VM doesn’t run in background
Changes of landscape to portrait mode on ipad crashes the app.
No screenshots of VM are saving.
Exiting the app when entering homescreen or app switching crashes the VM.
All previous things works when ran somewhat on Win10 but not at all in Win11.
If one absolutely stays put in the VM without any interaction with iPadOS VM is stable.
All sound in Windows 11 is significantly more stuttering and jarring to the speakers than in Windows 10.
Even After spice guests tools.
5026.C
Also if anyone knows how to get windows 10 arm64 working in 2023 as the ISO results in Blue screen of death errors during new VM installation procedures.  According to UUP scripts and users below version has been discontinued by Microsoft Servers.
Does anyone have a Windows 10 multi_creatingISO_21390.2025_en-us_arm64_professional ISO file in order to preserve keeping alive UTM Windows 10 Virtualization Alive. Please Post a cloud link of such an ISO.
Device is iPad Pro 5th Gen 12.9 M1 with iPadOS 15.1 Xina jailbreaken and Trollstore Included.
Configuration (required)

UTM Version: 4.1.5 HV
OS Version: iPadOS 15.1        Fedora 37, WIndows 10, Windows 11
Device Model: iPad Pro 12.9 M1
Is it jailbroken (name jailbreak used)? Xina
How did you install UTM? Trollstore

5026.A SOLVED
[mijorus] commented
Disabling GPU acceleration was enough to make it work!
Display > Display Card > Virtio RamFb
well, GPU acceleration is hit or miss in my experience.
On Ubuntu for example, some apps just won't launch when GPU acceleration is enabled.
About fedora, UTM should either default to virtio ramrb or add a paragraph about this workaround. Out of the box is just unusable.
Primeboy77 Comments - That this little maneuver has rectified functionality of the Fedora 37 Workstation arm64 VM.

5026.B Semi-Solved
Once again the >>>>
Disabling GPU acceleration was enough to make it work!
Display > Display Card > Virtio RamFb
*Fixes All F' up delayed video and sound in Windows 11 from being significantly more stuttering and jarring to the speakers

5026.C Solved
Damn Once again the >>>>
"Disabling GPU acceleration was enough to make it work!
Display > Display Card > Virtio RamFb"
*This modification of defaults settings supplants the desire of Windows 10 as a superior in video and sound.
Due to improving virtualization of video and sound by so much.

"Disabling GPU acceleration was enough to make it work!
Display > Display Card > Virtio RamFb"
it's work!! thanks


feat: router.leafRoutes for excluding from nested pages

Types of changes

[x] New feature (a non-breaking change which adds functionality)

Description

A potential fix for #4008 and also many similar issues.
In current router.js, if we have pages like:
+-- nuxt.config.js
+-- pages
|   +-- _id.vue
|   +-- _id
|       +-- _name.vue
|       +-- _name
|           +-- _sub.vue

The generated routes will be like:
[{
  path: "/:id",
  component: _1808b1d3,
  name: "id",
  children: [{
    path: ":name?",
    component: _43247de7,
    name: "id-name",
    children: [{
      path: ":sub?",
      component: _19715728,
      name: "id-name-sub"
    }]
  }]
}]

In this case, if _id.vue does't contain NuxtChild and we access http://localhost:3000/foo/123, only _id.vue will be rendered and both asyncData will be executed which are all inappropriate.
The expected behaviour should be only pages/_id/_name.vue and it's asyncData is rendered/executed.
But it's also kind of complex to know that if page contains NuxtChild, so I proposed this pr which introduces leafRoutes (temporary name) for marking the page as a leaf route.
The leaf route means that the children of this page are not nested, so the generated routes will be like:
// nuxt.config.js
export default {
  router: {
    leafRoutes: ['_id', '_id/_name']
  }
}
// router.js
[{
  path: "/:id",
  component: _1808b1d3,
  name: "id"
}, {
  path: "/:id/:name?",
  component: _43247de7,
  name: "id-name"
}, {
  path: "/:id/:name?/:sub?",
  component: _19715728,
  name: "id-name-sub"
}]

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Thanks Clark, it looks good to me at first sight.
But instead of defining again in nuxt.config.js, I would like that we start using router-extras to instead set this « leaf » mode or « not nested » right inside the page. So when removing the file, we don’t have to change anything else.
Cc @pi0

Agree with @Atinux about advising to use route-extras for this mode. Can be both an option in nuxt.config or using router-extras.

What if we suggest such structure to enable leaf mode:
+-- nuxt.config.js
+-- pages
|   +-- _slug.vue
|   +-- _id
|       +-- _name.vue
|       +-- _name
|           +-- _sub.vue

The point is that if dynamic param names are not equal, we assume they have no relation together. (So no <nuxt-child> in _slug.vue


feat: 0x0B -SIGNEXTEND

Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: Closes #93 Closes #100
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[x] No

Added changes to CHANGELOG.md

[x] Yes
[ ] No

Other information

CI and good to go

changelog conflicts rip wtf this is painful


RequestApi.addRequest : callback is not a function

Hello,
I'm exploiting this zimbra resource, and i can normally authenticate which is great and get back my auth token, but when I try to call the GetAccountInfo and when i send the request, i to this over my terminal :

debug: Validating options
debug: RequestApi#addRequest called
debug: Validating options
debug: Creating new request
debug: Adding new request to stack: {"params":{"account":{"by":"name","_content":"mycontent"},"_jsns":"urn:zimbraAccount"},"namespace":"zimbraAccount","name":"GetAccountInfoRequest"}
C:\Users\Code\Desktop\Freelance\testZimbra\node_modules\jszimbra\lib\api\request.js:126
        callback(null);
        ^

TypeError: callback is not a function
    at RequestApi.addRequest (C:\Users\Code\Desktop\Freelance\testZimbra\node_modules\jszimbra\lib\api\request.js:126:9)
    at C:\Users\Code\Desktop\Freelance\testZimbra\api.js:24:13
    at CommunicationApi.getRequest (C:\Users\Code\Desktop\Freelance\testZimbra\node_modules\jszimbra\lib\api\communication.js:442:5)
    at C:\Users\Code\Desktop\Freelance\testZimbra\api.js:20:10
    at CommunicationApi._handleAuthResponse (C:\Users\Code\Desktop\Freelance\testZimbra\node_modules\jszimbra\lib\api\communication.js:109:9)
    at C:\Users\Code\Desktop\Freelance\testZimbra\node_modules\jszimbra\lib\api\communication.js:580:25
    at Request.handleRequestResponse [as _callback] (C:\Users\Code\Desktop\Freelance\testZimbra\node_modules\unirest\index.js:461:25)
    at Request.self.callback (C:\Users\Code\Desktop\Freelance\testZimbra\node_modules\request\request.js:373:22)
    at emitTwo (events.js:87:13)
    at Request.emit (events.js:172:7)

and here's my code :
var z = require('jszimbra');

var comm = new z.Communication({
    url: "my resource link"
});

// Authenticate

comm.auth({
    "username": "user",
    "secret": "pass",
    "isPassword": true
}, function(err) {
    if (err) {
        // An error occured authenticating!

    }
    console.log('done !')
        // Now, carry on creating requests and sending them
    comm.getRequest({}, function(err, req) {
        if (err) {
            // Can't create a new request
        }
        req.addRequest({
            name: "GetAccountInfoRequest",
            namespace: "zimbraAccount",
            params: {
                "account": {
                    "by": "name",
                    "_content": "mycontent"
                }
            },
            function(err) {
                if (err) {
                    // Can not add request to the request handler
                }
                comm.send(req, function(err, response) {
                    if (err) {
                        // Can not send request
                    }
                    // response holds our response

                    console.log(response.get().GetAccountInfoResponse);
                });
            }

        });
    })
});

Is there any explanation for this or any solution ?

Yes, in the callback of req.addRequest() you get a request object back, that you should use in comm.send instead of the previous variable "req".
So it should be:
req.addRequest({
...
}, function (err, newRequest) {
   if (err) {
...
   }
   comm.send(newRequest, ...)
}

Have a look at the README. It's documented there.

@dploeger  same problem it's not working at all. with same error message.

Could you please repost your modified code?

Her's the modified code :
var z = require('js-zimbra');

/*var comm = new z.Communication({
    url: "my-resource"
});

// Authenticate

comm.auth({
            "username": "user",
            "secret": "pass",
            "isPassword": true
        }, function(err) {
            if (err) {
                // An error occured authenticating!

            }

                // Now, carry on creating requests and sending them
            comm.getRequest({}, function(err, req) {
                    if (err) {
                        // Can't create a new request
                    }
                    req.addRequest({
                            name: "GetAccountInfoRequest",
                            namespace: "zimbraAccount",
                            params: {
                                "account": {
                                    "by": "name",
                                    "_content": "mycontent"
                            }
                        }, function(err, nreq) {
                            if (err) {
                                console.log('err', err);
                            }
                            comm.send(nreq, function(err, res){
                                if(err) {
                                    console.log('err', err);
                                }
                                console.log(res);
                            })
                        }
                    })
            })
        });

Sorry, I've misread the code in your first post. You were right all along, but I'm stumped why the error is happening. I will check this and get back to you.

@dploeger when i switched from single request to batch request, i got what i need, thing do work i got for the getAccountInfoREquest two responses (obviously) but things do work, but please if you can find out why the first one do catch it will be awesome.

Hi @houssem-yahiaoui
Its or your code its missing a } in the call to addRequest, I think it should be:
 req.addRequest({
                            name: "GetAccountInfoRequest",
                            namespace: "zimbraAccount",
                            params: {
                                "account": {
                                    "by": "name",
                                    "_content": "mycontent"
                                 }
                            }
                        }, function(err, nreq) {

@pbruna  that in fact fixed it ! thank you !


fix: checkmark classic component.

:tada: This PR is included in version 1.0.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Move fixture generation to contrib and add test

As suggested in https://github.com/go-gitea/gitea/pull/10247#pullrequestreview-358917813, I've moved the fixture generation to contrib:
go run -tags 'sqlite sqlite_unlock_notify' contrib/fixtures/fixture_generation.go

I've also added a unit test for checking if the derivative fixtures (currently access.yml) match the expected generation.
It looks more "natural", but it's a lot more of code. I have mixed feelings of whether this is the best way or the one we've just merged. I'll leave the decision to you guys.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b2f04f4). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master   #10277   +/-   ##
=========================================
  Coverage          ?   43.68%
=========================================
  Files             ?      585
  Lines             ?    80988
  Branches          ?        0
=========================================
  Hits              ?    35380
  Misses            ?    41227
  Partials          ?     4381

Impacted Files
Coverage Δ

models/fixture_generation.go
65.38% <100%> (ø)

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 b2f04f4...e6cf45f. Read the comment docs.


menu on the bottom in mobile layout overlaps tiles

When:

Using mobile layout (customTheme: CUSTOM_THEMES.MOBILE)
Having menu on the bottom (menuPosition: MENU_POSITIONS.BOTTOM)
There is enough tiles to enable page scrolling
Page is scrolled to the very bottom

then the bottom menu partially overlaps bottom tiles which, depending on the overlapped tiles, might make it harder/impossible to interact with them.
See a screenshot:

It should be possible to scroll more so that tile is not overlapped by menu.

Just add little bit to the height of group. e.g. + 0.5

Probably bottom margin of group also should work

Presume the matter is resolved and we can close this one?

While I appreciate how customisable this project is and how easily we can workaround issues, I think this should still be fixed in core.
It would be easy to fix it for mobile layout, but I think it should be fixed for all themes which would be quite a bit more work. Basically make sure that it's always possible to scroll page so that tiles are unobstructed by toolbar. For non-mobile layouts toolbar is even bigger so it's even easier to make it obstruct tiles if there is enough content vertically.

For non-mobile themes which  have page menu on the left, having menu  overlap the tiles is kinda a feature.

I'm only talking about menu on the bottom. I haven't seen menu on the left obstructing tiles.

OK, I see it. But in that case there is no problem as it's possible to scroll page all the way to the left (or right, depending how you look at it) and then no tiles are obstructed.

Would you be able to provide a PR of what you think would be the best fix? Please keep in mind that we should only edit .less.

For my specific issue the fix could be:
diff --git a/styles/themes.less b/styles/themes.less
index 37c1a58..56c282f 100644
--- a/styles/themes.less
+++ b/styles/themes.less
@@ -151,6 +151,18 @@
          }
       }
    }
+
+   &.-menu-bottom {
+      .page {
+         padding-bottom: 44px;
+      }
+
+      @media (min-width: 500px) {
+         .page {
+            padding-bottom: 56px;
+         }
+      }
+   }
 }

 .-theme-mobile, .-theme-winphone {

But as I said, all themes should have similar fix (this change only handles MOBILE and WINPHONE). I could probably work on full fix in soon future, if you are not gonna handle it before.

I'd love to get people on board so it could become a joint project.

Thanks for the commit. Believe we can close it.


confused error:Library not loaded

finished download and cmake with python2 done,after make successfulliy I run the instruction python Demo.py
and then error occur:
StaceydeMacBook-Air:bgslibrary Stacey_W$ python Demo.py
Traceback (most recent call last):
File "Demo.py", line 3, in
import libbgs
ImportError: dlopen(/usr/local/bgslibrary/build/libbgs.so, 2): Library not loaded: @rpath/libopencv_stitching.3.3.dylib
Referenced from: /usr/local/bgslibrary/build/libbgs.so
Reason: image not found
and I use otool to see the Library Dependencies,so why it can't load the library??
/usr/local/bgslibrary/build/libbgs.so:

finally I found the mistakes about my opencv.
There some trouble in my opencv linking.

Someone meet the same questions as me can try to reinstall your opencv, and it may help


question: obadooga - text_generation_webui_xtts

you have plans to make your work compatible to
https://github.com/oobabooga/text-generation-webui
???

No, why would I?


[data model] enforce 250 KB size limit for Move objects

Don't allow the BCS bytes of a Move value object to be larger than 250 KB. This should mitigate some performance issues we are seeing from reading/writing/updating very large objects.
We have discussed a limit of 1-2MB before and may increase this limit accordingly, but want to start with something small to encourage folks to use the new dynamic fields feature (which is the recommended way for dealing with large collections or data).
We will enforce a separate, less stringent limit for package objects in a subsequent PR.

I remember a while ago we also set a limit on gas that's targeting a 2M package size (or 1, I don't remember). Is that still needed? @oxade

2MB for both objects & packages is what was communicated to me and is what I've been telling people.
It is what we planned to enforce using gas price controls as part of gas maintenance release changes.
I was not aware of this new 250kB decision so I cannot speak on it.
I'm halting further size related gas actions for now.

I will halt further size related gas actions until we have clarity on this as a stable value is needed for calibration.

Yes 2MB for both objects & packages is what was communicated to me and is what I've been telling people.

On this, couple of things:

We have discussed a limit of 1-2MB before and may increase this limit accordingly, but want to start with something small to encourage folks to use the new dynamic fields feature (which is the recommended way for dealing with large collections or data).  I worry that if we let objects be 2MB, that is permissive enough to still allow pretty big collections inside objects, whereas folks should really refactor to dynamic fields unless they are very sure the collection is fixed-size. For devs, I think it will be much less disruptive if we get strict exactly once and then (possibly) loosen the requirements from there
The "big" objects that are causing us problems in devnet right now (and are the motivation for this change) are "only" 1.77MB, so I don't think enforcing the 2MB limit will help us with our current problems.
@gdanezis made the point that a separate Move object and package size limit makes sense given that it's much easier to support large immutable objects than it is to support large mutable ones. The Sui Framework is already a bit bigger than 250KB (316KB), but it's also a huge package, so ~500KB feels like a reasonable starting point there.

I will halt further size related gas actions until we have clarity on this as a stable value is needed for calibration.

Can you elaborate on how the limits plug into gas calibration?

@sblackshear is there an ongoing thread on what problems we are seeing on devnet from these big objects?  Are these storage related?


is there a way to increase ulimit ?

I get the following failures when trying to update my system.
building the system configuration...
error (ignored): error: opening directory '/tmp/nix-build-perl-5.36.0-env.drv-4': Too many open files
error (ignored): error: opening directory '/nix/store/lkpm61x3fsckk4cniy4clsgp62wg9xn6-perl-5.36.0-env.drv.chroot': Too many open files
error (ignored): error: opening directory '/nix/store/kqwhbsypilb7g7sky5a6v1l1r1cr89vi-perl-5.36.0-env.drv.chroot/nix/store/0h17z31z87cfggv77bakfk7cdk1r06fr-perl-5.36.0-env/lib/perl5/5.36.0': Too many open files
error: creating pipe: Too many open files

is there an attribute to increase the ulimit ?

This error is awesome, I love macOS. Maybe we should make an issue label for macOS specific issues.
https://apple.stackexchange.com/questions/32235/how-to-properly-increase-a-ulimit-n-limits
If you do find a solution you can prepend to the command, let me know and I'll implement a fix. With the new Nixinate I'm working on, you'd be able to add this to your preDeployScript, so hang tight!

And thank you for making these issue reports, it's really interesting to see the edge cases that you are hitting.

ulimit -n 8196
should do it.
looking forward to the new nixinate!

did you see my previous comment, I've just ran into the error again. (it's for a deployment that needs a lot of derivations built).

hey @MatthewCroughan , let me know if there is anything I can do more to help on this one.

@happysalada can't you just run ulimit -n 8196 on your machine? That should fix the issue, right? Alternatively, it seems like buildOn = "remote" could solve this as well (if the target is powerful enough, of course).
Are you proposing that the nixinate script should set the ulimit? Is that even possible inside a sandboxed shell?

Im using remote already
The ulimit looks like it doesnt persist between different shells, ive tried setting it in another shell and it didnt affect my deployment
I dont feel too strongly about this issue, as my workaround is just to build less things

Ah got you. Just to clarify, are you deploying from a MacOS host to a remote Linux machine or from a Linux host to a remote MacOS machine? I do have one of each so could try to replicate and integrate a workaround, it seems straightforward enough.

Macos host to a linux machine.
My current workaround is to build less stuff at first then to rebuild the rest on the second deploy.
I havent found another way around this problem yet.

https://unix.stackexchange.com/questions/108174/how-to-persistently-control-maximum-system-resource-consumption-on-mac
now thats a weird and wonderful way to set ulimit!!! Apple , how do make setting a simple configuration option like ulimit so mind numbing diffiicult.
Anyway, that think apple has a future over 'just running photoshop'... is greatly mistaken.


asynk: 2.0.0-rc2 -> 2.0.0, add CalDAV support

Update to the latest release and fix missing/custom python libraries so CardDAV works.

Built locally, thanks.


Clicking on the Product

Oops!
Something went wrong and we couldn't process your request.
Please go back to the previous page and try again.
For additional assistance, please reference the WHMCS TroubleShooting Guide »
Laminas\HttpHandlerRunner\Exception\EmitterException: Unable to emit response; headers already sent in /home/botservi/public_html/vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php:19
Stack trace:
#0 /home/botservi/public_html/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitterTrait.php(36): Laminas\HttpHandlerRunner\Exception\EmitterException::forHeadersSent()
#1 /home/botservi/public_html/vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitter.php(27): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->assertNoPreviousOutput()
#2 /home/botservi/public_html/clientarea.php(0): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->emit(Object(WHMCS\ClientArea))
#3 {main}

WHMCS breaking when viewing a product is not a module related issue. Contact WHMCS for assistance if you can't figure it out.


net: config: Add VLAN identifier as network initial configuration

Add a new Kconfig parameter NET_CONFIG_MY_VLAN_ID as initial network configuration to enable users to set VLAN identifier at startup.
Add a call in net_config_init_by_iface(...) function to setup the VLAN identifier in the device if the Kconfig parameter is different from zero.

I think the config library is starting to show its limitations as it only supports to setup one instance of a "thing" only. In the past @cfriedt suggested using dt to configure networking config options and with dt we could have a configuration setup for multiple instances of things. Someone would just need to define dt options for networking.

Ultimately I think this is going to be the correct solution, because DT is the only way we have to configure multi-instance devices and hardware in general.

@jukkar @carlescufi Hi! Can you point me to the discussion about that? We are definitely interested in setting up more than one device at boot time and we can spend some time for that, I've thought before we could use DT but I was not sure until now, because you mention that.
So if you have already a design I think we can work on that feature, as long as it meets our requirements.
Also, is there a space where people can discuss these kind of things, like a chat or something? A forum?
Thanks :)

There is a big reservation with using DT for describing software "metadata" rather than hardware information. See
#49431
#50441
And probably more...

Also, is there a space where people can discuss these kind of things, like a chat or something? A forum?

You can join the discord chat (recommended), or use the mailing lists.

Also, is there a space where people can discuss these kind of things, like a chat or something? A forum?

@luca-fancellu
https://chat.zephyrproject.org/
Then join the #networking channel

There is a big reservation with using DT for describing software "metadata" rather than hardware information. See #49431 #50441 And probably more...

Thanks @pdgendt. I think we are going to have to bring this to the Architecture WG, because USB had the same problem and they ended up using DT for this.
Also see https://github.com/zephyrproject-rtos/zephyr/issues/29750
@pdgendt @rlubos @luca-fancellu @jukkar let's continue the discussion on Discord. @luca-fancellu feel free to start a thread there


aligned the back-to-top arrow and the chat icon

Description
I have changed the padding of back-to-top arrow to make it aligned with the chat icon.
Fixes: #809
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] 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

Checklist:

[x] I have made this from my own
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@huamanraj for issue #809

Great contribution to GSSOC'24! 🎉


How to provide backpressure when using ApiStreamObserver?

You can use the async GRPC client stub and pass in a ClientResponseObserver in place of the StreamObserver, which has an additional method called beforeStart that provides a ClientCallStreamObserver that has the request(count) method.
However, I cannot find a similar request(count) method in ApiStreamObserver to provide backpressure.

Hey @meltsufin, is this a better question for googleapis/gax-java?

@kolea2 You're right!
https://github.com/googleapis/gax-java/issues/773

Thanks! :)


#issue0.1

[x] setup file
[x] requirements file
[x] logger and exception
[x] environment
[x] template for code
[x] github repository

First issue sucessfully completed


Command not found

I tried using "grunt" but it says "/bin/sh: grunt: command not found". But when I "CD" to the project from a terminal and used "grunt" command, it worked fine. It goes the same for "bower". But built-in commands like "CD", "LS" are working fine in your plugin. How do I fix it?

Install this plugin?


ACLs for GCS bucket for engine artifacts should be further restricted

We should restrict the ACLs to only automated bots.
Would have prevented https://github.com/flutter/flutter/issues/104387.
See internal go/flutter-dart-oom-retro for more context.

Blocked on codesigning implementation.

@godofredoc @XilaiZhang any update?

The ACLs for individuals will be removed after the Aug 2023 release.
@itsjustkevin FYI

This is now complete.


Could Blazor work on Electron to make cross-platform desktop apps?

I wonder if it would be possible to marry Blazor and Electron for an all (or nearly all) c# cross-platform desktop application development experience?

offtop: Browser + Razor + Electron = guess what...

There is already a project that does this - https://github.com/ElectronNET/Electron.NET. Theoretically yes you could use Blazor to coordinate the UI, but it's not a scenario we're focusing on at the moment.

not just theoretically. I tried it. It actual works. :D and Looks extrem nice.
You can do

look at https://learn-blazor.com/getting-started/getting-blazor/ and install Visual Studio template
make a new solution and select Blazor Project (I tried on .NET Code)
there will be 3 Projects Client and Server + Shared (be careful)
start Server and try it out in your browser
now the Electron.NET Part see https://github.com/ElectronNET/Electron.NET
add package ElectronNET.API
follow their Github page and add  .UseElectron(args) to program.cs (using Electron.API namespace)
add Task.Run(async () => await Electron.WindowManager.CreateWindowAsync()); to Startup.cs (u have to care the namespaces for sure)
add package package Electron.CLI
modify the csproj file for CLI Tools
maybe a restore and build command
command line commands : dotnet electronize init and dotnet electronize start
there could be Anti-Virus SW and so which is freaking out because ELECTRON.NET Create a browser view based GUI (allow)
finish

Just for anyone else curious and finding this issue - you can use the standard electron, example here:
https://github.com/roceh/electronblazortest
Even though its very early days I do find the data binding much easier to use in Blazor than XAML personally.

... and now we know one reason Microsoft bought Github (the creators/maintainers of Electron)

Called it.

Here's a screenshot of a recent experiment we did to do a partial port of the Azure Storage Explorer (Electron app written in JS) to Blazor + Electron.NET and then ran it on a Mac:

This was just an experiment, but the startup perf looks great the UI perf is nice and fluid.

dotnet new blazor-electron-vscode-like-app --name AwesomeBlazor

Listview, tabs, popup! Did you guys used Bootstrap to create the UI?

@danroth27 is that experiment open-source? In a repo anyway?

@chris-ray No, it was just an internal experiment to help us understand how well it would work and what sort of architectural adjustments it would require.

@SteveSandersonMS Just cloned and ran the Electron-Experiment - with debugger-support!
Very cool!

Blazor + Electron would be ideal for our scenario : we build control systems for complicated science equipment (high powered lasers) interfacing with specialist cameras, actuators and so on. The control logic is in C#, and we'd really like to have an HTML based UI (currently using WinForms and WPF).

For those that didn't watch the livestream, here's steve's electron sample app https://github.com/SteveSandersonMS/BlazorElectronExperiment.Sample

I can't seem to follow @dotChris90 's instructions with Blazor 0.4.0, which is a shame! Electron complains about being included with a netstandard2.0 project 😐

I tried the Sample from Steve and it works fine for me.
This is great, I hope this experiment became official project.
Great job thank you.

This is brilliant. Please, please support this.
We are trying to find appropriate technology to port our huge and complex financial app and browser just isn’t cut to it and never will be.
Yes, part of app can be in browser, but main parts, massive data entry, connection to devices like scanners, barcode readers, RFID scanners ... browser will never be a platform for such scenarios.
But electron plus Blazor ... getting serious goosebumps.
OOB Silverlight was so close a long time ago, please don’t make this another OOB Silverlight.
No Balmer to blame this time as well :-)

This is very useful in our case. We can easily convert our WPF+Winforms thick client to Blazor + Electron. Are there any plans to make it one of Blazor hosting modes?

Server side Blazor is now official project and will ship in core 3.0. Given that, Electron + Server side Blazor will be the true cross platform experience. You don't even have to depend on webassembly and you can take advantage of all core 3.0 can do (full debugger support for example). Everything runs locally so no need to worry about UI responsiveness and signalr connection problems.

I've tried the experiment at https://github.com/SteveSandersonMS/BlazorElectronExperiment.Sample, allowed me to create a nice looking cross platform UI pretty quickly.
Would be nice if it was more officially supported.

I noticed that using Electron is much faster and much more responsive. Starting the application it loads almost instantly. In browsers this takes quite some time.
I have experimented with long running, computationally heavy methods started with Task.Run at a button click. I am using classic .NET events to report updates. The event handlers then call StateHasChanged to update the UI. In Client-side blazor this was simply ignored and the UI was updated only after the long running method finished (I assume because client-side Blazor is single-threaded). In server-side Blazor I injected a service and polled every second to display a status update. In the BlazorElectronExperiment.Sample above the client-side blazor code was doing all UI updates properly and also pretty fast.

I think this is the Winform/WPF killer, MS won't like it:)

Dead tech doesn't need to be killed. Rather it's artificially kept alive, because of a lack of alternatives. Even this is not production-ready yet and who knows when it will be. The desktop has not gone away and I doubt it will, rather it has diversified and successful apps need to go x-plat. MS seems to be highly interested to bind developers to their stacks, though they still lack an idea on how to turn that into money. I will not be surprised if eventually we have to pay for this. MS earns nothing from an x-plat app running on Linux. And Azure can hardly provide some value for desktop apps. I think that's the dilemma, not that they don't like it. Eventually, we'll see this with a GPL license sticker and have a commercial licensing option. :-)

I would not mind paying for it a single bit. It is the cleanest financial model - there is a product you like, product which enables you to make money, you pay for it, you get the product, end of story.
Infinitely better than various ad-based models where I am turned into a product to get "free stuff". No thanks.

I would also be super interested in the blazor+electron combination for creating cross platform tools. The software projects of the company I work for are quite desktop focused (WinForms/WPF). Looking at our customer base and feedback I'm sure that an increasing amount would love to see cross platform support.
Most devs in my team know their way around C#.NET - so the switch to blazor running in electron would be a good upgrade path.

Speaking of which @rubenwe , I had trouble getting the Electron example to work with components (incl. Layout and Navigation) in a shared dll. It worked fine in client-side blazor and server-side blazor. Did you have any success?

Am I only one who thinks that everything goes wrong? Why we can't just have html+css render in .NET and some .NET API for manipulating with DOM? Why we need so many other things (V8, JavaScript, WASM, etc)?

@kripergvg You can modify DOM only by using JS atm.

Is there any ETA on getting C# directly work with DOM rather than interop by JS?

Not anytime soon i imagine - that would mean WebAssembly as a standard having direct access to all browser APIs/DOM, implemented and shipped in the browsers and then Blazor can take advantage of that.
No idea if that's even on the cards in WASM's future right now.

for all who interested in running blazor on electron, there is an interesting framework called bionic.
see the documentation. here

Here's a screenshot of a recent experiment we did to do a partial port of the Azure Storage Explorer (Electron app written in JS) to Blazor + Electron.NET and then ran it on a Mac:

This was just an experiment, but the startup perf looks great the UI perf is nice and fluid.

Hello @danroth27  , is your Azure Storage Explorer source code available somewhere ?
I'm actually re-working my Blazor.Xamarin plugin in order to make it works with Blazor 0.8.0, on UWP, iOS 12 and Android 4.4 and more .
There is work to do on the Android side, as Android WebView renderer is old , and even some recent Chrome for Android version does not support WebAssembly by default. I managed to create Xamarin Bindings for GeckoView usage on Xamarin as a WebView replacement, and Blazor works like a charm even on an old Android 4.4.
When all thoses works will be done, it would be nice, as a proof of concept, to see if i can embed and load Azure Storage Explorer on theses platform. Looking them from a tablet on iOS or Android as a standalone app would be nice !

Hi @Daddoon,
The code for the Azure Storage Explorer is not public. Maybe you could try the pizza store app from the Blazor workshop instead? https://aka.ms/blazorworkshop.
Also, please note that we're aren't monitoring this issue tracker closely anymore. If you have Blazor questions or issues please open them on the https://github.com/aspnet/aspnetcore repo.

Any chance to get the source code of @stevesandersonms demo at NDC-London?

@xclud Which one are you looking for? One of these?:

https://github.com/SteveSandersonMS/RazorComponentsSentimentAnalysis
https://github.com/danroth27/RazorComponentDemos
https://github.com/danroth27/BlazorExcelSpreadsheet

@danroth27 Thank you. I was looking for RazorComponentDemos but the two also are great to have.

Am I only one who thinks that everything goes wrong? Why can't we just have html+css render in .NET and some .NET API for manipulating with DOM? Why we need so many other things (V8, JavaScript, WASM, etc)?

Actually, by adding .NET Core hosting capabilities to Electron, we instantly get all benefits of Blazor Server Side Rendering


Popovers (focus) are buggy!

The documentation says to use focus on popovers in order to have them close when clicking outside. This fails on an iPhone.
If I change it to click, it will fire, but then not close when tapping outside.
All I want is for the popover to work with a click or tap - and close on another click or tap anywhere else on the page. This should be the standard/default functionality.
Has anyone had any success implementing them this way?

Duplicate of #16028.
Blame WebKit (in part): https://bugs.webkit.org/show_bug.cgi?id=151933

Here's my attempt at accomplishing this:
  $('[data-toggle="popover"]').popover({html: true});
  function closePopovers() {
    $('.popover').popover('hide');
    $("html").unbind("click", closePopovers);
  };
  $('[data-toggle="popover"]').on('shown.bs.popover', function () {
    setTimeout(function() {
      $("html").bind("click", closePopovers);
    }, 0);
  })

But now apparently there is also a bug where hiding a popover requires you to click twice to open it again? Gotta be kidding me :( 👎

Cool! I'll tell my clients to blame webkit when my app doesn't work, that should work just great.

Sorry, that was incredibly snarky. Its a bit late. Well, thanks for the update/info.

To be honest...what I posted above isn't the end of the world. If the user taps once, then is at least able to tap outside to close it, they've already seen what they need to see.
A double tap to open it again isn't the worst thing ever. At least a tap outside of the tooltip closes it. I bet that takes care of most cases.
Thanks for the prompt response and info @cvrebert - If you know of any workarounds to the double click/tap to open after a hide is called? I imagine there is another issue open for that?

This has some good insight, I'll check it out tomorrow: http://stackoverflow.com/questions/32581987/need-click-twice-after-hide-a-shown-bootstrap-popover

Thank you for revising your comment to remove the snark. 😄  Bootstrap isn't corporate-backed and the Core Team is few in number, thus we don't always have the time or resources to fix every issue as quickly as we'd like to. Bootstrap is largely a labor of love. Thus we greatly appreciate the community's patience and understanding.

If you know of any workarounds to the double click/tap to open after a hide is called? I imagine there is another issue open for that?

Yep, #16732.


fixup! Pass test command line around in setup.py (fix #442)

For whatever reason, under 3.6 we're now getting passed setup.py test discover where we weren't before.
This brutal change fixes the problem, though it means you can't pass flags through setup.py to pytest any more.
This feature has always been problematic, however, as most of the useful flags don't get passed through anyway.
Instead, if I need to pass arguments to pytest, I call it directly.  Less typing anyway.
Note this is a fixup.  With your permission, I'm going to rebase it into dev to clean up all these failed pulls and commits.

Fixes #501

lgtm

Should I fold it into the original commit on dev?  That was my plan - otherwise, it means that any commit between the original commit and now will seem broken.
I wish Travis didn't change underneath us - how is this happening?

Yeah, that would probably be best.
On Tue, Dec 5, 2017 at 8:23 AM, Tom Swirly<EMAIL_ADDRESS>wrote:

Should I fold it into the original commit on dev? That was my plan -
otherwise, it means that any commit between the original commit and now
will seem broken.
I wish Travis didn't change underneath us - how is this happening?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/503#issuecomment-349302582,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6rXkaxPInYFeXiia1QBUeK4UH8qoks5s9UPTgaJpZM4Qwnyr
.

The rebase is complete.


Add initial search usage doc.

Forked from @jgeewax's version in #972, and updated to match patterns from PubSub/BigQuery/DNS.

LGTM
Please hold off on merging until @jgeewax is able to discuss the "confidential" marking part.


jsii-rosetta peer dependency outdated

jsii-rosetta peer dependency defined in jsii-docgen package.json "maxes out" at version 5.5.0, but there is now a fresh version 5.6.0 available.
This blocks upgrading JSII in Projen projects to 5.6.0.
An example output when trying to install dependencies n Projen+JSII powered project:
❯ npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: XXXXXXXXXX
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/jsii-rosetta
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ~5.0.14 || ~5.1.2 || ~5.2.0 || ~5.3.0 || ~5.4.0 || ~5.5.0" from<EMAIL_ADDRESS>npm ERR! node_modules/jsii-docgen
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/Ari.Palo/.npm/_logs/2024-11-19T17_39_56_792Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /Users/Ari.Palo/.npm/_logs/2024-11-19T17_39_56_792Z-debug-0.log

I started working on a fix. Unless any issues, I'm gonne send a PR.

Thanks @aripalo for reporting this. Looks like we missed a step in the release of rosetta.


Feature/modularize

This PR resolves #309
Kudos to @johthor and @BjoernKasteleiner to implement this during our great hacking session on Oct., 11th!
Note: Currently it is missing adjustments to the architecture documentation. Therefore it is just a draft.

+1


[test] add retain_active_session option for ePSKc deactivate API

Depends-On: openthread/ot-br-posix#2537

This PR is the unit test for ot-br-posix PR https://github.com/openthread/ot-br-posix/pull/2537; After this PR merged,  #2537 CI failures would be clear (due to DBus parameter added and checked)


chore: bump van-stock-count-api-tools version

Sure no changes are needed? This is like 3 breaking changes away from what was there

No changes required here. this  just wraps the function into an angular service and expose it to the integrated dashboard where it is consumed as an angular service.
  translate (data, version) {
    return VANApiTools.translateReport(data, version)
  }
}```


Some stylegan2 installation trouble

I had some errors running your stylegan2 code on Ubuntu 16, but found a solution here:
https://stackoverflow.com/questions/59342888/tensorflow-error-this-file-requires-compiler-and-library-support-for-the-iso-c#
Changed line 64 and 127 of dnnlib/tflib/custom_ops.py as in the stackoverflow answer and comment. Maybe something to change in this code, or note if anyone else have the same issue.

I'm not sure why this is caused, since the original code works fine in my cases. Maybe I'll update the code if it turns out to be a general problem and has no side effects.


Girvan-Newman algorithm has an error

Update line 64 in girvan_newman.py to G = nx.from_numpy_array(adj_matrix) instead of G = nx.from_numpy_matrix(adj_matrix)

I have purposed a change on my PR


Create weapon art for mech builder/battle scenes

Translate weapon art from cards into parts that appear on/attached to the mech.

Create module art for

Shotgun
Missile
Laser
Railgun


Fix codeowners for the release branch

the release branch codeowner's file never got updated to what it is on master. We should update the release branch to use that codeowner's file

There is also:
https://github.com/celestiaorg/celestia-core/blob/53593e612dd373df461ad8037743f9e7c6526667/.github/dependabot.yml#L23-L25


failure on first connect of feather device

Working from a newly created project, I try to connect to my feather board and get the following error. But the DeviceScript server does start, so the second time I connect is successful.

for future repros: you change your setting to start the devtools in a terminal; then try this again and you should get a better error message in the devicescript terminal page.


Support draco encoded glTFs

In the future.

This issue should probably tie back into #35

For a rough overview of the work required:
GLTFLoader can be configured with DRACOLoader instance:
var loader = new THREE.GLTFLoader();
THREE.DRACOLoader.setDecoderPath( '/examples/js/libs/draco' );
loader.setDRACOLoader( new THREE.DRACOLoader() );

DRACOLoader is small, and can be included in the bundle. If the model uses Draco compression, GLTFLoader will automatically defer to DRACOLoader, which in turn loads either (1) the JS decoder, or (2) the WASM decoder based on browser support. Including both decoders in the bundle is probably impractical, so I think end-users may have to host the decoder libs alongside their model. Here are the libs: https://github.com/mrdoob/three.js/tree/dev/examples/js/libs/draco/gltf.
Will likely need at least one attribute, e.g. draco-decoder-path="path/to/decoders", added.

Hm I don't know the status of magic leap support here.

@rcabanier do you know whether magic leap supports Draco decoding?

Can you provide a pointer to draco? Is it a new format or a preprocessor?

@rcabanier Draco is a compression library. It can be used as a standalone format (.drc) but more often it is used as a compression scheme within a glTF model, through the KHR_draco_mesh_compression extension. It's that glTF extension we're interested in here. Typically this reduces the size of the geometry (not textures or animation) in the model by 85–95%. glTF files using Draco can be decoded in a preprocess step, or during the normal loading process using the provided decoders.
Glad to provide more technical details and example models if that would be helpful. :)

@donmccurdy is there a way to convert from a Draco compressed gltf to a regular one?

Also, do you have data on how common these types of gltf are?

Hi @rcabanier — you can convert both ways (compressed <--> uncompressed), the compression is lossy but otherwise reversible.
One popular tool that implements this is glTF-Pipeline. This tool is useful for authoring and testing, but relies on node.js and the Cesium engine so you wouldn't want to ship it in Prismatic I imagine.
Re-implementing that decompression in Prismatic should be straightforward enough, but does require that you use the Draco WASM, JS, or native decoding library.
Draco compression is a popular optimization for glTF users, particularly on web for bandwidth considerations, but typically that compression is added manually — asset libraries like Sketchfab, Poly, and TurboSquid do not distribute glTF files that are already compressed. Most authoring tools (e.g. Blender, Substance Painter) also output uncompressed files, the only exception I know of is Adobe Dimension 2.0, which outputs compressed files with the Draco extension.

Hi folks, sorry to be effectively leaving a +1 but Draco support is basically essential for remotely realistic 3D models and I don't know how you're managing without it (all your models are low poly?). The benefits are absolutely enormous (unlike the file sizes). As Don mentioned Three already has good working Draco decompression available in conjunction with GLTFLoader.
Assuming a target audience for the model viewer is things like online shopping etc, this probably needs some attention again. Facebook have the same problem with 3d posts not supporting draco either, combined with capped file sizes, hobbling the usefulness of the feature.
To give some perspective, in my own use case draco cuts model sizes (and therefore user wait times) from 14mb to 2mb (for example). Big models are common when starting from CAD model sources rather than designing them to be low poly from the start.

@webprofusion-chrisc good news! If you check our project board, you'll see that DRACO support is on deck for this sprint.

sorry to be effectively leaving a +1

No apologies needed, we love getting feedback 🙌

I don't know how you're managing without it

Basic glTF support was, of course, the first order of business. There is a lot of free content available in non-compressed glTF, so it basic support has been suitable as we have ramped up the project.
It's also worth noting that DRACO support would add significant byte size and some complexity to the <model-viewer> payload.

@cdata it may be worth looking at this PR, rather than the checked-in version of DRACOLoader:
https://github.com/mrdoob/three.js/pull/15249. In particular using workers will prevent <model-viewer/> from hanging the rest of the page, and will parallelize decoding when multiple viewers are present.

Thanks for the heads up @donmccurdy . I had mistakenly assumed that the DRACO loader was already usable from a worker.
What outstanding work is remaining to get that PR merged?

The GLTFDRACOLoader class in that PR is compatible with the GLTFLoader already, because it has the same API as the older class and can be provided similarly:
gltfLoader.setDRACOLoader( dracoLoader );

So it doesn't strictly have to be merged, but I would eventually liked to get it submitted, and the remaining items are listed here: https://github.com/mrdoob/three.js/pull/15249#issuecomment-439102607. (1) and (2) only affect merging it into three.js, but (3) may affect performance and is relevant here.


Improve record/play features

Short term

Add history-like list to recording
Make sure it works with undo/redo

Mid term

Make it possible to give titles and descriptions to certain steps, which are then displayed when playing back

Long term

Add milestone steps to recording and export recording to an HTML presentation which uses a library like impress.js
Make the presentation editable in a web interface like strut.io to add other things

I'm going to add the recorded steps as part of the history and make it appear in the history list with a red highlighting.

Update manipulations in "play next" function


Number 0.0000001 is recognized as string 1.0E-8 in the function result

Example:
Variable 'a' is a string.
<?php

require __DIR__ . "/vendor/autoload.php";

$context = new \Smuuf\Primi\Context;
$interpreter = new \Smuuf\Primi\Interpreter($context);

$context->setVariable('teste', \Smuuf\Primi\Structures\Value::buildAutomatic(function() {
        return 0.00000001;
}));

try {

    $interpreter->run('a = teste()'); // expect variable 'a' be a Number but it is a string

    foreach ($context->getVariables() as $name => $value) {
        printf("%s (%s) ... %s\n", $name, $value::TYPE, json_encode($value->getInternalValue()));
    }

} catch (\Smuuf\Primi\ErrorException $e) {
    die($e->getMessage());
}

Eu usei o seguinte ao retornar float:
return sprintf("%.20f", '0.00000000001');

I believe it would be better if this value was not converted to a string

I agree.
I think I currently have a working prototype where handling number values is implemented with bcmath, where Primi can handle arbitrarily large numbers and also quite small numbers (up to 128 decimal points at the moment, but this might change - or be configurable). Preliminary benchmarks show somewhere around ~10% performance hit when using bcmath instead of native PHP integers and floats, but that seems like a pretty good tradeoff.

If it were configurable it would be great

the precision of php already working for me, there was only one problem when converting the function return


add docker and make file

I added docker file for ros-melodic.

@zhaozhongch Can you review my PR?