chapter02 docker-compose error

docker-compose up Error Message
ERROR: for opentelemetry-collector  Cannot create container for service opentelemetry-collector: json: cannot unmarshal number 0.1 into Go struct field ContainerConfigWrapper.StopTimeout of type int
ERROR: compose.cli.main.exit_with_metrics: Encountered errors while bringing up the project.
docker-compose --version
docker-compose version 1.29.2, build unknown

Seeing the same error:
ERROR: for opentelemetry-collector  Cannot create container for service opentelemetry-collector: json: cannot unmarshal number 0.1 into Go struct field ContainerConfigWrapper.StopTimeout of type int
ERROR: Encountered errors while bringing up the project.
❯ docker-compose --version
docker-compose version 1.29.2, build 5becea4c

Good news and bad news....
The good news is that I've tracked the issue to the stop_grace_period: 100ms lines in the compose file. If you remove these, it should allow everything to come up as expected.
The bad news is that I have no idea why this is the case - that directive should work based on some research.

@qdzlug
Thank you for leading me to solving the issues.
everything is up as expected.

@mutomasa - no worries, glad it's working.
Based on https://docs.docker.com/compose/compose-file/compose-file-v3/#stop_grace_period the directive takes a duration argument, but the duration argument doesn't seem to accept ms as a unit, only h, m, s:  https://docs.docker.com/compose/compose-file/compose-file-v3/#specifying-durations
So I wager that changing it to stop_grace_period: 0.1s will likely solve the problem and keep the intended grace period. I'll check that later this weekend and open a PR if that does indeed fix it.

@qdzlug
Thank you for the docker doc link.
I am a bit suprised to accept the duration unit "ms".
so I inderstand you changed it to stop_grace_period: 0.1s.

@mutomasa - no, I actually had to change it to 1s - if you look at the error it's being converted to 0.1s and that is what is failing with the error about the int variable type.

Thanks for reporting this, I'm also surprised to see this didn't work as expected in older versions of docker compose, since according to the docs it uses durations, which according to the examples here support ms. 1s duration is ok as well, I'm happy to accept the PR.

Closing as the PR has been merged. Thanks again!


If needs review is false, publish the recipes after saving

fixed: if user is the owner and the only subscriber then the post will be published when created.

This issue was moved to k-sheth/calendar-khana-lagao#41


Port to C#

Are there any plans to port this to C# ever?

You can actually use this with C#:
// get the state chart node
var stateChart = GetNode<Node>("StateChart");

// Send an event to the state chart
stateChart.Call("send_event", "some_event");

// Set expression guard properties
stateChart.Call("set_expression_property", "health", 27);
stateChart.Call("set_expression_property", "shields", 48);

The rest is just using signals which work with C# out of the box. I should probably add this to the manual instead of the FAQ. Maybe I could also add some extension methods to Node which make this work with less strings.

I was actually thinking about doing the same thing with extension methods. It would be much appreciated.

So I have decided against extension methods and in favour of wrapper classes. This way the extension methods will not pollute the autocomplete of normal nodes with state chart specific stuff which may be confusing and/or irritating. The new way will be:
var stateChart = StateChart.Of(GetNode("StateChart"));

// send an event to the state chart
stateChart.SendEvent("some_event");

// set expression guard properties
stateChart.SetExpressionProperty("health", 27);
stateChart.SetExpressionProperty("shields", 48);

I have also added some additional support for connecting signals in code,  so this relies less on strings:
var state = State.Of(GetNode("%ActiveState"));
state.Connect(State.SignalNames.StateEntered, Callable.From(OnStateEntered));

Currently finalizing the manual and the example and then you can give this a spin.


"RuneLite" Configuration moved to the top

Just a simple change to the Configuration screen by putting the RuneLite to the top and leaving it there, or we can a "Favourites" listed on the top.

I would really like a Favorites option


ValueError in Labels issues?

has anyone ever come into the issue below when trying to test other SAM models:
Traceback (most recent call last):
File "E:\PythonProjects\Grounded-Segment-Anything\EfficientSAM\grounded_mobile_sam.py", line 145, in
main(args)
File "E:\PythonProjects\Grounded-Segment-Anything\EfficientSAM\grounded_mobile_sam.py", line 83, in main
labels = [
File "E:\PythonProjects\Grounded-Segment-Anything\EfficientSAM\grounded_mobile_sam.py", line 83, in
labels = [
ValueError: too many values to unpack (expected 5)
Let me know how to fix this please. Thank you!

detections returns 6 values, while the labels list takes into account 5. fixed by changing:
labels = [     f"{CLASSES[class_id]} {confidence:0.2f}"      for _, _, confidence, class_id, _     in detections]
to:
labels = [     f"{CLASSES[class_id]} {confidence:0.2f}"      for _, _, confidence, class_id, _, _     in detections]

thanks a lot :) @haviduck


Under compilation of class that transitively extends trait which has had private field renamed

Steps to reproduce in: https://github.com/retronym/zinc-test
$ git checkout 2d6edfb && sbt clean compile && git checkout 90072a9 && sbt compile c/console
Previous HEAD position was 90072a9 Rename private trait field a.A.{a1 => a2}
HEAD is now at 2d6edfb Add private field to trait a.A
[info] Loading settings for project global-plugins from idea.sbt,dirtymoney.sbt,gpg.sbt ...
[info] Loading global plugins from /Users/jz/.sbt/1.0/plugins
[info] Loading project definition from /Users/jz/code/zinc-test/project
[info] Loading settings for project zinc-test from build.sbt ...
[info] Set current project to zinc-test (in build file:/Users/jz/code/zinc-test/)
[info] Executing in batch mode. For better performance use sbt's shell
[success] Total time: 0 s, completed 01/05/2019 11:39:54 AM
[info] Updating ...
[info] Updating a...
[info] Done updating.
[info] Done updating.
[info] Updating b...
[info] Compiling 1 Scala source to /Users/jz/code/zinc-test/a/target/scala-2.12/classes ...
[info] Done updating.
[info] Updating c...
[info] Done updating.
[info] Done compiling.
[info] Compiling 1 Scala source to /Users/jz/code/zinc-test/b/target/scala-2.12/classes ...
[info] Done compiling.
[info] Compiling 1 Scala source to /Users/jz/code/zinc-test/c/target/scala-2.12/classes ...
[info] Done compiling.
[success] Total time: 2 s, completed 01/05/2019 11:39:56 AM
Previous HEAD position was 2d6edfb Add private field to trait a.A
HEAD is now at 90072a9 Rename private trait field a.A.{a1 => a2}
[info] Loading settings for project global-plugins from idea.sbt,dirtymoney.sbt,gpg.sbt ...
[info] Loading global plugins from /Users/jz/.sbt/1.0/plugins
[info] Loading project definition from /Users/jz/code/zinc-test/project
[info] Loading settings for project zinc-test from build.sbt ...
[info] Set current project to zinc-test (in build file:/Users/jz/code/zinc-test/)
[info] Executing in batch mode. For better performance use sbt's shell
[info] Compiling 1 Scala source to /Users/jz/code/zinc-test/a/target/scala-2.12/classes ...
[info] Done compiling.
[info] Compiling 1 Scala source to /Users/jz/code/zinc-test/b/target/scala-2.12/classes ...
[info] Done compiling.
[success] Total time: 1 s, completed 01/05/2019 11:40:03 AM
[info] Starting scala interpreter...
Welcome to Scala 2.12.7 (OpenJDK 64-Bit Server VM, Java 1.8.0-adoptopenjdk).
Type in expressions for evaluation. Or try :help.

scala> new c.C
java.lang.AbstractMethodError: c.C.a$A$_setter_$a$A$$a2_$eq(Ljava/lang/String;)V
  at a.A.$init$(x.scala:4)
  at c.C.<init>(x.scala:3)
  ... 36 elided

It happened in presentation compiler tests in the linked PR, but I just hit it in code completion. It also happened after clean ; dist/mkPack. As in the linked PR, now I will git clean -dfx and try again. So, I wasn't losing my mind. These tests were of build/pack/bin/scala, not the scala task under sbt or quick.
scala> (0x7FFFFFF: Float).toInt.toH
Failed to initialize compiler: AbstractMethodError.
This is most often remedied by a full clean and recompile.
Otherwise, your classpath may continue bytecode compiled by
different and incompatible versions of scala.

java.lang.AbstractMethodError: Receiver class scala.tools.nsc.interactive.Global$$anon$4 does not define or inherit an implementation of the resolved method abstract scala$tools$nsc$typechecker$Contexts$_setter_$scala$tools$nsc$typechecker$Contexts$$TupleOfNullAndNoSymbol_$eq(Lscala/Tuple2;)V of interface scala.tools.nsc.typechecker.Contexts.
	at scala.tools.nsc.typechecker.Contexts.$init$(Contexts.scala:1881)
	at scala.tools.nsc.interactive.Global$$anon$4.<init>(Global.scala:228)
	at scala.tools.nsc.interactive.Global.analyzer$lzycompute(Global.scala:226)
	at scala.tools.nsc.interactive.Global.analyzer(Global.scala:226)
	at scala.tools.nsc.interactive.Global.analyzer(Global.scala:113)
	at scala.tools.nsc.Global.<init>(Global.scala:993)
	at scala.tools.nsc.interactive.Global.<init>(Global.scala:119)
	at scala.tools.nsc.interpreter.PresentationCompilation$$anon$2.<init>(PresentationCompilation.scala:75)
	at scala.tools.nsc.interpreter.PresentationCompilation.newPresentationCompiler(PresentationCompilation.scala:75)
	at scala.tools.nsc.interpreter.PresentationCompilation.newPresentationCompiler$(PresentationCompilation.scala:67)
	at scala.tools.nsc.interpreter.IMain.newPresentationCompiler(IMain.scala:72)
	at scala.tools.nsc.interpreter.PresentationCompilation.presentationCompile(PresentationCompilation.scala:36)
	at scala.tools.nsc.interpreter.PresentationCompilation.presentationCompile$(PresentationCompilation.scala:33)
	at scala.tools.nsc.interpreter.IMain.presentationCompile(IMain.scala:72)
	at scala.tools.nsc.interpreter.shell.ReplCompletion.codeCompletion(ReplCompletion.scala:73)


Bump metrics to test new build

High Level Description

Adds tagging
Adds unit values to metrics
Adds better metric gathering for node collector

Merged PR: https://github.com/dcos/dcos-metrics/pull/61
Related Issues
DCOS-12410 Add unit values and arbitrary tag support
Checklist for all PR's

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Unit Testing Results
ok      github.com/dcos/dcos-metrics/util/http/helpers  0.006s
?       github.com/dcos/dcos-metrics/util/http/profiler [no test files]
github.com/dcos/dcos-metrics/collectors/framework/framework.go:67:      New                             100.0%
github.com/dcos/dcos-metrics/collectors/framework/framework.go:77:      RunFrameworkTCPListener         75.0%
github.com/dcos/dcos-metrics/collectors/framework/framework.go:102:     handleConnection                60.5%
github.com/dcos/dcos-metrics/collectors/framework/framework.go:180:     transform                       78.9%
github.com/dcos/dcos-metrics/collectors/framework/framework.go:234:     Read                            80.0%
github.com/dcos/dcos-metrics/collectors/framework/framework.go:245:     getTopic                        100.0%
github.com/dcos/dcos-metrics/collectors/framework/record.go:41:         extract                         83.9%
github.com/dcos/dcos-metrics/collectors/framework/record.go:108:        createObjectFromRecord          80.0%
github.com/dcos/dcos-metrics/collectors/mesos/agent/agent.go:154:       New                             0.0%
github.com/dcos/dcos-metrics/collectors/mesos/agent/agent.go:163:       RunPoller                       0.0%
github.com/dcos/dcos-metrics/collectors/mesos/agent/agent.go:173:       pollMesosAgent                  0.0%
github.com/dcos/dcos-metrics/collectors/mesos/agent/agent.go:193:       getContainerMetrics             100.0%
github.com/dcos/dcos-metrics/collectors/mesos/agent/agent.go:209:       getAgentState                   100.0%
github.com/dcos/dcos-metrics/collectors/mesos/agent/agent.go:223:       transformContainerMetrics       81.8%
github.com/dcos/dcos-metrics/collectors/mesos/agent/agent.go:259:       getFrameworkInfoByFrameworkID   100.0%
github.com/dcos/dcos-metrics/collectors/mesos/agent/agent.go:271:       getLabelsByContainerID          100.0%
github.com/dcos/dcos-metrics/collectors/mesos/agent/agent.go:289:       buildDatapoints                 65.6%
github.com/dcos/dcos-metrics/collectors/node/cpu.go:21:                 poll                            92.3%
github.com/dcos/dcos-metrics/collectors/node/cpu.go:41:                 addDatapoints                   100.0%
github.com/dcos/dcos-metrics/collectors/node/cpu.go:89:                 getNumCores                     85.7%
github.com/dcos/dcos-metrics/collectors/node/cpu.go:109:                init                            100.0%
github.com/dcos/dcos-metrics/collectors/node/cpu.go:116:                getCPUTimes                     100.0%
github.com/dcos/dcos-metrics/collectors/node/cpu.go:128:                calculatePcts                   100.0%
github.com/dcos/dcos-metrics/collectors/node/cpu.go:149:                round                           100.0%
github.com/dcos/dcos-metrics/collectors/node/filesystem.go:23:          poll                            83.3%
github.com/dcos/dcos-metrics/collectors/node/filesystem.go:54:          addDatapoints                   100.0%
github.com/dcos/dcos-metrics/collectors/node/load.go:15:                poll                            88.9%
github.com/dcos/dcos-metrics/collectors/node/load.go:30:                addDatapoints                   100.0%
github.com/dcos/dcos-metrics/collectors/node/memory.go:19:              poll                            87.5%
github.com/dcos/dcos-metrics/collectors/node/memory.go:45:              addDatapoints                   100.0%
github.com/dcos/dcos-metrics/collectors/node/memory.go:100:             getMemory                       100.0%
github.com/dcos/dcos-metrics/collectors/node/memory.go:105:             getSwap                         100.0%
github.com/dcos/dcos-metrics/collectors/node/metrics.go:86:             getNodeMetrics                  75.0%
github.com/dcos/dcos-metrics/collectors/node/metrics.go:117:            thisTime                        100.0%
github.com/dcos/dcos-metrics/collectors/node/network.go:25:             poll                            88.9%
github.com/dcos/dcos-metrics/collectors/node/network.go:54:             addDatapoints                   100.0%
github.com/dcos/dcos-metrics/collectors/node/node.go:43:                New                             100.0%
github.com/dcos/dcos-metrics/collectors/node/node.go:55:                RunPoller                       0.0%
github.com/dcos/dcos-metrics/collectors/node/node.go:66:                pollHost                        0.0%
github.com/dcos/dcos-metrics/collectors/node/node.go:85:                transform                       100.0%
github.com/dcos/dcos-metrics/collectors/node/process.go:13:             poll                            83.3%
github.com/dcos/dcos-metrics/collectors/node/process.go:24:             addDatapoints                   100.0%
github.com/dcos/dcos-metrics/collectors/node/process.go:35:             getProcessCount                 75.0%
github.com/dcos/dcos-metrics/collectors/node/uptime.go:13:              poll                            83.3%
github.com/dcos/dcos-metrics/collectors/node/uptime.go:23:              addDatapoints                   100.0%
github.com/dcos/dcos-metrics/config.go:90:                              setFlags                        100.0%
github.com/dcos/dcos-metrics/config.go:97:                              loadConfig                      66.7%
github.com/dcos/dcos-metrics/config.go:110:                             getNodeInfo                     58.3%
github.com/dcos/dcos-metrics/config.go:153:                             newConfig                       100.0%
github.com/dcos/dcos-metrics/config.go:184:                             getNewConfig                    50.0%
github.com/dcos/dcos-metrics/dcos-metrics.go:33:                        main                            0.0%
github.com/dcos/dcos-metrics/dcos-metrics.go:96:                        broadcast                       0.0%
github.com/dcos/dcos-metrics/dcos-metrics.go:106:                       producerIsConfigured            100.0%
github.com/dcos/dcos-metrics/producers/http/handlers.go:27:             nodeHandler                     64.3%
github.com/dcos/dcos-metrics/producers/http/handlers.go:50:             containersHandler               57.1%
github.com/dcos/dcos-metrics/producers/http/handlers.go:73:             containerHandler                66.7%
github.com/dcos/dcos-metrics/producers/http/handlers.go:91:             containerAppHandler             70.0%
github.com/dcos/dcos-metrics/producers/http/handlers.go:110:            containerAppMetricHandler       61.9%
github.com/dcos/dcos-metrics/producers/http/handlers.go:147:            pingHandler                     100.0%
github.com/dcos/dcos-metrics/producers/http/handlers.go:160:            encode                          50.0%
github.com/dcos/dcos-metrics/producers/http/http.go:51:                 New                             100.0%
github.com/dcos/dcos-metrics/producers/http/http.go:63:                 Run                             95.7%
github.com/dcos/dcos-metrics/producers/http/http.go:123:                janitor                         100.0%
github.com/dcos/dcos-metrics/producers/http/logger.go:22:               logger                          100.0%
github.com/dcos/dcos-metrics/producers/http/router.go:23:               loadRoutes                      100.0%
github.com/dcos/dcos-metrics/producers/http/router.go:41:               newRouter                       100.0%
github.com/dcos/dcos-metrics/util/http/client/client.go:38:             Fetch                           50.0%
github.com/dcos/dcos-metrics/util/http/helpers/helpers.go:30:           loadCAPool                      81.8%
github.com/dcos/dcos-metrics/util/http/helpers/helpers.go:51:           getTransport                    88.9%
github.com/dcos/dcos-metrics/util/http/helpers/helpers.go:75:           NewMetricsClient                0.0%
total:                                                                  (statements)                    69.3%

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[x] Test Results: [link to CI job test results for component]
[x] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

This is ready for review @spahl @adam-mesos @darkonie

@darkonie @adam-mesos updated.


MathJax src points to retired CDN

The MathJax CDN hosted at cdn.mathjax.org shut down on April 30, 2017. Please migrate to another CDN according to this article in the extension.

thanks for reporting, just submitted a PR

Please update the packagecontrol.io package soon. Since everything breaks now.
Thanks

should be ok ?

Great! Thanks. Will try soon. You may close this now. If there's still issue. I will comment here again.
Thank you for making this great!


Please do a new release for Python 3.11 compat

Python 3.11 is becoming the standard version in various package systems and no released version of mod_python works with it (while the issues seem to be already fixed).
Can you please do a new release?

As a packager, I ask that you reconsider.     From a packaging system viewpoint, no releases looks like "upstream is not functional", and this conclusion was indeed offered as an opinion on a pkgsrc list.    Likely primarily because of no releases, pkgsrc still has 3.5.0.   Please have a look at
https://repology.org/project/apmod:python/versions
which shows that most GNU/Linux distributions and other packaging systems are out of date relative to git master.  Debian until recently had 3.5.0 and how has git from 2021, but that seems to be the best case.
It doesn't need to be a release; a tag is fine.   That is simply a statement that upstream thinks that particular commit is stable.  Release/tags like 3.6.20230815 are fine, to unwind semantics from them other than "this commit is ok and it's the most recent one that has been blessed".
Also, the README does not explain the lack of releases, so someone looking at github is lead to incorrect conclusions.

@gdt this sounds reasonable - let me think on it for a couple of days

I created a <IP_ADDRESS> tag and adjusted the README and NEWS. LMK if more needs to be done?

That looks good.   I will try to get pkgsrc updated to the new version over the next with any luck less than a week, and if all goes as smoothly as I expect, Martin or I will ask you to close the ticket.  Thank you very much for doing this.
It will also be interesting to see repology pick this up and I suspect it will cause a lot of packaging systems and distributions to update.

pkgsrc updated.  The only wrinkle was that the body of the release has version at 3.5.0, and thus the egg name is 3.5.0, not the usual $VERSION.  But that was easy to deal with.
We are carrying two patches, both longstanding and off topic here:

add in -R in addition to -L in configure.ac (generally an issue in the python world)
don't run git at build time to compute a version (it's not a declared dependency and we want the same result always)

We have this marked as not safe for -j builds and I just confirmed that this broke when I tried it.   Docs say to run make without -j, quietly by omission, so only sort of a bug :-)
Happy to file bugs if useful, and I totally understand if these are below the line of what you want to deal with.   Surely everybody who cares has dealt by now.

@gdt thank you for your efforts! Might you have a link to the aforementioned patches?

Only if you promise not to laugh about CVS.

http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/www/ap2-python/?only_with_tag=MAIN
cvsweb.netbsd.org/bsdweb.cgi/~checkout~/pkgsrc/www/ap2-python/patches/patch-configure.in?rev=1.1&content-type=text/plain&only_with_tag=MAIN
cvsweb.netbsd.org/bsdweb.cgi/~checkout~/pkgsrc/www/ap2-python/patches/patch-dist_version.sh?rev=1.2&content-type=text/plain&only_with_tag=MAIN

The configure patch is really hacky, modifying flags in a way that is only safe because they were just set to one thing.  The basic issue is that  you need -R (or -Wl,-R or -Wl,-rpath) to link the module so it can find python.   This is probably avoided on most GNU/Linux because everything is --prefix=/usr, but in general it doesn't work.     The situation is compounded by python's config script not dealing with -R like it should.

Lol, for the life of me cannot remember whether mod_python was in CVS at some point... It must have 'cause mp predates SVN?
Okay, closing this for now. Thank you all!


Ver1.8.2

    try:
        self.cursor_buffered.execute(sql_unlock)
        self.disconnect_db_buffered()
    except pymysql.Error as e:
        self.logger.debug('Got error {!r}, errno is {}'.format(e, e.args[0]))

Catching mysql variable wait_timeout set too short exception.
For a very large table, such as 100000000 rows, is easy to happen.
This problem took us a lot of time to troubeshooting

Hi, it seems to me that you are trying to merge from a wrong branch (1.8.2) into master which base branch is 2.0.
Any chance you can fork the repository and issue a pull request from the branch 2.0?
Or I can review the suggested changes in the comment and add them to the next beta (and add you as contributor).
Thanks

I'm closing this PR as I cannot merge it with all those conflicts.
Happy to merge your changes coming from the correct version.
Please issue a PR from a forked repository against the branch ver2.0.
Thanks


$ missing in the example's innermost Console.WriteLine(...)

There's a $ missing in the example's innermost Console.WriteLine(). The Output is not properly displayed.

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

ID: 728b8960-bd9b-6e47-0697-1ede60319dcc
Version Independent ID: f2080e9b-3a61-ec89-eb34-b61aff1641fa
Content: Create a nested group
Content Source: docs/csharp/linq/create-a-nested-group.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Already fixed in PR https://github.com/dotnet/samples/pull/149

@mariaw @BillWagner this can be closed, see ^^

Thanks for letting us know, @d-dizhevsky.


Fail to capture and replay OpenGL ES on Linux

Description
I'm  trying to capture an OpenGL ES desktop application on Linux but it crashes.
I manage to capture if I modify this line:
LibraryHooks::RegisterLibraryHook("libGL.so.1", &GLHooked);
by setting the FunctionLoadCallback to NULL in the RegisterHooks() method of the glx_hooks.cpp.
Can we make a fix for this?
Replaying doesn't work for me either, the problem is that RenderDoc uses the Mesa library while NVIDIA should be used.
Could you give a solution for this problem?
Thank you.

Environment

RenderDoc build: v1.x 2018-07-12
Operating System: Ubuntu Linux
API: OpenGL ES

Can you give more information: What program are you running? Where is the crash happening exactly? We can make a fix if it's a RenderDoc bug but I need more information to determine what the correct fix is. You can't just remove that callback to fix your case as that will break for other cases, and it shouldn't be necessary.
I don't understand what you mean that mesa is used instead of NVIDIA's driver. RenderDoc doesn't select any particular driver it just calls into the system libraries, it's up to the system's configuration to determine which driver is used.
I did find a bug that caused libGLESv2.so not to be hooked properly, I've just pushed a fixed for that so it would be worth trying with latest code as of now, but it doesn't sound like what you were running into.

I was running a GLES desktop application which uses SOIL to load images and I crashed because version is null here:
const char *version = (const char *)GL.glGetString(eGL_VERSION);
in the FetchEnabledExtensions() method of gl_common.cpp.
Since then I have tried other GLES applications (without SOIL) and they can be captured fine.
I couldn't capture Vulkan desktop applications either, only if i remove or modify libGL.so.1 hooking like in my previous comment.
As for the replaying, the application is compiled with NVIDIA but when it is replayed, the Mesa library is called. Setting up the library path environment variable when running RenderDoc solves this problem though.

I still need more information to investigate this. If it's only any program using SOIL can you share an example either as source or binary that I can run to debug this? glGetString returning NULL suggests something is very wrong, are there any GL errors?
Changing the libGL.so.1 hooking only clouds the issue, this will maybe hide some symptom but it's not a real fix. You mention that you have trouble capturing from Vulkan applications which is a different issue, but you don't say what actually happens or goes wrong.
I don't understand what you mean by "compiled with NVIDIA". It sounds like your system is misconfigured if there's some library mismatch or you need to set the library path environment variable, none of that should be necessary to run RenderDoc.

I'm sending the GLES example code attached. I didn't get any GL error for this.
When I tried to capture the Vulkan, I got VK_ERROR_INCOMPATIBLE_DRIVER error message after vkCreateInstance was called.
GLES_SOIL.zip

Thank you for the repro. I don't think it's related to SOIL, it was a bug where it seems that on linux calling GL functions in libGL isn't equivalent to libGLESv2, and the example you gave was linked against libGLESv2. I applied the same fix as windows to forcibly clear and re-initialise the GL function pointers using eglGetProcAddress. Hopefully that will work well enough.
The vulkan errors were a problem with my hack around some broken distributions that ship the nvidia vulkan ICD as libGL.so. Using RTLD_NEXT to fetch the ICD functions doesn't work if libGL.so wasn't loaded earlier, because the loader loads the ICD as RTLD_LOCAL. Instead I grab the handle when it's loaded and look at it directly.

Both GLES and Vulkan capturing works fine now, thank you.


[feature] FAQ bot add, list, and define

Purpose of pull request
Related Issue: resolves #30
Pull request checklist

[x] Branch and PR are named correctly
[ ] Updated relevant documentation
[x] Tested with a tester bot
[x] Wrote unit tests for changes
3/3 done

PR-specific checklist

[x] Responds to ++faq add
[x] Responds to ++faq list
[x] Responds to ++faq define
[ ] Responds to ++faq delete
[x] Responds to ++faq list -i
[ ] Handles duplicates with ++faq define
[x] Restricts commands that write to the database to certain roles

Testing instructions
++faq

Do you want to partition out the commands a bit to different PRs? Would be easier to review that way and incrementally upload to main bot without having to do massive rollbacks (if god forbid we had to)

Any reason why ++faq delete was scrapped?
Also, as a personal note: I think it'd be interesting to have aliases: ++fd <word> for ++faq define <word>. Although ++faq d <word> would be a good candidate too.

Not scrapped per se as much as can be done in multiple PRs since they are pretty independent of each other


tests: introducing 'find_next' function

can be used to limit find for consecutive message only.

@gdubicki @dmerejkowsky please check if you can, this should only take up to 5 minutes of your time.


different behavior of Run vs Run Without Debugging. (python code)

not sure if this is a bug or a feature, but what is the difference between:
clicking on Run (triangle) button vs Run Without Debugging (Ctrl+F5) ?
Because when I run this Python code:
import os
os.startfile("textfile.txt")

by Ctrl+F5 (Run Without Debugging), as I'm used to, nothing happens. The code runs as if "silently" and no window (application) is open to view the text file.
But when I run the code by clicking on the Run (triangle) button, it behaves correctly (and my Notepad++ pops up, opens).
Sorry if this should have been reported elsewhere...

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.73.1
OS Version: Windows 11

Steps to Reproduce:

You should have a "textfile.txt" in your project/working directory.
Try to run the above python code, by those two ways as described.

Please file on the python extension repo


Reoserv Fixes

This branch contains all the fixes for the bugs listed here:
https://docs.google.com/spreadsheets/d/1knlYz-HFolGtnz_yLi7ZrTkYN6AZKkNV6jO9Lri7BBg/edit#gid=0
Let me know if you have any questions :)

These issues are fixed in the new use_sdk branch

Closing this PR; these issues are addressed by the migration to eolib-dotnet and confirmed fixed.


setup: incorporate latest changes from drake

This change is

ci / macos catalina 10.15 (pull_request) failure is expected until the day after RobotLocomotion/drake#14395 merges.

+@EricCousineau-TRI for review.

Relates #61


Linked List Interview Questions

Description 📜
Adding the LinkedLlist questions which are frequently asked in interview

Domain of Contribution 📊

[x] C/CPP
[x] Competitive Programming

/assign


Including a Warning message to the readme.md

Purpose

Adding warning message informing the users of the repository to be deprecated.

resolve https://github.com/wso2/kubernetes-pipeline/issues/119

resolve https://github.com/wso2/kubernetes-pipeline/issues/119

resolve https://github.com/wso2/kubernetes-pipeline/issues/119


Top percent applied to an item in a vertical container give undesired results (c++)

Issues and Steps to Reproduce

Create a flex node
Add another flex node inside the first.
Make the parent flex container as "vertical" direction.
apply top % to the inside flex item.

Expected Behavior

Actual Behavior

Hi @sanjayQ,
I know it's a long time ago you posted that issue. Unfortunately I'm not able to reproduce that with the latest version, with your described steps.
I have the following layout, does that match your issue? (Default values compared to the web apply, see: https://jsfiddle.net/emilsjolander/jckmwztt/)


Add option to Ignore invalid receiver addresses

If one of email address is invalid, it will cause the entire message to fail.
Is there a way filter the invalid address, and send the email success?

Actually, I was already adding a flag on MailerBuilder for ignoring failed email validation, when I realized that's the same as turning validation off completely.
To answer your question, yes that's already possible:
currentMailerBuilder
   .clearEmailAddressCriteria()
   (..)


Regions on the same note but with different groups do get muted

This happens e.g. with keyswitches. This behavior is slightly different from Cakewalk's apparently, I'll let @kinwie detail :)

Yes, tested. Working as expected and enhanced Cakewalk's behavior :+1:

The original RGC sfz player and Cakewalk DropZone has a nice self-choking behavior (same group= and off_by number) which preserved its polyphonic voicing per note. But it has one flaw, which it can't choke the same note when some other functions combined, e.g. using CC 4 for hihats control.
So this sfizz enhanced behavior solved that flaw and will works perfectly fine with any specific behavior of other sfz players, e.g. Cakewalk players and ARIA/sforzando.


README explain cargo run permission for gdb #113

Update README.md to explain how to give cargo run permission to launch gdb.
As discussed in discord and #113, on first-run the gdb debugger doesn't give cargo run permission to run gdb automatically and load the FW to the HW.
This PR updates the README.md to show a command which can give this permission, and limits the permission addition to the scope of the stm32f1xx-hal repository in use.
Because of the different conventions between Linux and Windows, the two commands were unable to be distilled into the same line of text.
It is unknown if only the Linux example is wanted, and the windows version of the command should be removed?
It seems the README.md already makes this assumption elsewhere?
Suggestions are welcome.

It is unknown if only the Linux example is wanted, and the windows version of the command should be removed?

We definitvely should have windows instructions as well if possible. Forutnately, I have been able to avoid using windows for years :P, unfortunately that means that I can't really write instructions for it


Support new schema (resolves LOAD-18, LOAD-17, LOAD-20, LOAD-21)

Note: I realize there should be only one issue per PR. most of those are sub-tasks of the main issue LOAD-18, and the last (LOAD-17) is essentially a test and should be included with this PR
This PR adds support for loading data with the new metadata schema defined in shemas.py.
What's new:

a revised README explaining how to run the loader with the new format and how its different from loading from the old format
Tests that run against the output of the new newt-transformer (LOAD-20)
Test for the metadata.json that gets loaded to make sure that it's formatted according to the schema we give to the dss (LOAD-17)
The new loader that can understand the new format that is output from newt-transformer (LOAD-18, LOAD-21)

What still needs to be done:

[ ] I haven't yet tried to upload the 107 using the new format. I was waiting for input from @mikebaumann before doing this. Since the new 'standard' loader passes tests, I don't imagine this will be an issue however.
[ ] Possibly (depending on input of @david4096 and @mikebaumann) remove the old gen3 loader. I think we should keep it around for at least another iteration as a backup.

┆Issue Number: LOAD-24

Well now we have a logging system set up and the mysteriously failing Travis builds have mysteriously resumed passing. Looking at the log from one of the failing builds, 68 there was a socket error which makes me think this was maybe a network error on Travis?
Perhaps this indicates that the retry mechanism used for the loader needs some improvement. @mikebaumann can you weigh in?

Okay @mikebaumann, I've implemented most of your suggestions. You found a lot of important mistakes and gave me a lot of ideas for improvements! I've responded to some of your comments above, but I'll summarize everything again.

I haven't implemented most of your suggestions for improved tests. I thought of some new ones myself while doing your suggestions. I compiled a list and propose to postpone these test improvements for another PR since it seems like it will be a good amount of work.

I set log level to INFO by default as per your suggestion but propose keeping it at WARNING but adding a --verbose option that switches to INFO. I'm not too attached either way.

You suggested making tests run the default log level (INFO). I think it can be really handy having log DEBUG for tests. I set up logging in the first place in order to debug Travis, and in general when tests fail it's useful to be able to see the full log without having to run modified tests again. Can you convince me why it's worth it to use the default log level for tests?

The schemas require some fields that are not required for loading (but all fields required for loading are required by the schemas). Should this be changed? I think this could be discussed in person.

The way I've it set up now, when a bundle fails to load, its information is logged real time. You suggested making a summary of all of the bundles that fail and logging it at the end. I think that's a great idea, but was considering adding a command line option to output the the summary to a file. What do you think?


Fix logical errors and typos in Spec equilibrium object

There were a few bugs in the Spec equilibrium object that I spotted:

Many error checks were written, but the raise clause was omitted, so they didn't take effect
The RHS of the assignments to si.iota[0:self.nvol+1] and si.oita[0:self.nvol+1] had the wrong shape
array shape check in as_spec compared tuple to list and always raised
the initial guess should have nvol elements, not mvol-1

I noticed, that parts of the codebase assume all profiles to be the same size (mvol), in this example according to the error message local_full_x = self.mvol
https://github.com/hiddenSymmetries/simsopt/blob/9fc2c36c7888aa3f677af3ad4f71d63a3e673a21/src/simsopt/mhd/profiles.py#L93-L98
or here, where volume_current_profile is simply overwritten in the vacuum region for freeboundary runs, so the profile entry has to be at least mvol in size:
https://github.com/hiddenSymmetries/simsopt/blob/9fc2c36c7888aa3f677af3ad4f71d63a3e673a21/src/simsopt/mhd/spec.py#L1001-L1019
while other parts create different sizes for different profiles.
https://github.com/hiddenSymmetries/simsopt/blob/9fc2c36c7888aa3f677af3ad4f71d63a3e673a21/src/simsopt/mhd/spec.py#L766-L781
What is the intended design @smiet ? I think variable size will result in stricter error handling, whereas having the same size might confuse users, on which elements actually affect the result. Of course, having all profiles the same size makes them easier to switch out, iterate over, etc.

@missing-user Thank you for the great work! Sorry to keep you waiting.  The inconsistencies are not intentional and need to be addressed.
The design relies on the user to enforce that the 'ProfileSpec' object is the right size and type for the profile in question. There are some helper functions that aid the user in generating profiles. From the simsopt side it is important that the profiles only contain the degrees-of-freedom that actually affect the plasma, so having them all mvol is not an option.

I noticed, that parts of the codebase assume all profiles to be the same size (mvol), in this example according to the error message local_full_x = self.mvol

The error is in the message here, the test compares to the number of degrees-of-freedom of the SpecProfile instance against the 'volume' (interface label) that is trying to be set, which depends on the profile, and the message should be changed to reflect that.

or here, where volume_current_profile is simply overwritten in the vacuum region for freeboundary runs, so although nvol elements are used, the profile has to be at least mvol in size:

This is due to the (confusing) use of 'cumulative profiles'. The profile on the simsopt side has nvol degrees-of-freedom, but on the SPEC side needs to populate mvol elements of the array.
The value of the volume current in the vacuum needs to be changed if the current inside of it is changed, but this cannot be to an arbitrary value and should not be a DoF.
We have to keep the DoFs on the simsopt side correct, as the optimizer dislikes having degrees-of-freedom that do not change anything (or worse, they do change the elements of the array, leads to calculations that do not reflect physical reality, i.e. current in the vacuum region).
I have not tested the profiles extensively, and there are indeed likely inconsistensies that you point  out, like:

Also @smiet , shouldn't iota profiles be nvol+1 elements and not mvol? How can the vacuum computational boundary have a prescribed iota? #457 (comment)

Yes, this must be wrong.
I now see that the the Spec.activate_profile() function might not work correctly for all profiles, volume-current should skip the first element for example.
I see you refactored the NormalField, but there is a simsopt specific issue with this: when changing a single element in the array, the recompute bell is not triggered. Setting the entire Optimizable.local_full_x does trigger it, or you can do it manually.
I did very much appreciate the full-array setters and getters set_vns_vns_asarray as it made code more readable, and it is used in CoilNormalField which gets the full array from a Fourier Transform, and needs it to be set. Could you rename the deleted get_dofs to _array_to_dofs that acts on the input array and sets the local_full_x?


Add a basic proptest for compactsize encodings.

Closes #110.

This "finds" and fixes two bugs, for sort of cheating values of "find" (the first was a rustc warning, and the second I spotted while looking at the librustzcash code).


Property LLM: Chat to find properties in London

Project Name
Property LLM
Description
Motivation
Many London university students struggle to find suitable accommodation, particularly when it comes to meeting the specific requirements of landlords and navigating the nuances of rental criteria. With high demand and limited guidance, students often face difficulties in matching with the right landlords, leading to frustration and unproductive searches. To address this, my team and I developed Property LLM, a platform designed to help students find studios and rooms by filtering both landlord and tenant requirements. By providing a tailored match between students and landlords, Property LLM simplifies the rental process, making it easier and more efficient for students to find the right accommodation in London.
Screenshot

Challenges Faced
Permissions with roles / unfamiliarity with Azure services.
Unable to get the OpenAI Embeddings to work with the Azure Storage.
Adding the all / required roles per documentation still encounter Permission APIError.
Further Work
Need to get vector embeddings to work and further explore the idea of geo-spatial embeddings. Which will also incorporate in the knowledge that the property is located.
Technology & Languages

[ ] JavaScript
[ ] Java
[ ] .NET
[X] Python
[ ] AI Studio
[X] AI Search
[ ] PostgreSQL
[X] Cosmos DB
[ ] Azure SQL

Project Repository URL
https://github.com/ericma1999/raghack
Deployed Endpoint URL
No response
Project Video
https://youtu.be/mtAGiixrlGA
Team Members
ericma1999

Hello @ericma1999, thank you for participating in RAG Hack!
The team is working hard to distribute badges. Please have each team member fill out this form:
aka.ms/raghack/badge-dist
Thank you!


Omnidata pretrain model

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

NEW LINKS I FOUND:
gdown '1Jrh-bRnJEjyMCS7f-WsaFlccfPjJPPHI&confirm=t' # omnidata depth (v2)
gdown '1wNxVO4vVbDEMEpnAi_jwQObf2MFodcBR&confirm=t' # omnidata normals (v2)


Group pod outputs since they can be very long

The output for each pod can be 1000s of lines long, which makes it very difficult to navigate between sections of the output, even with the green headings.

:heart: :tada:!


Doesn't seem to work with map variables?

Expected Behavior
To be able to provide tags as variables in a packer build
Current Behavior
With a step like below the pipeline errors with a usage error i.e. Usage: packer build [options] TEMPLATE
      # Had issues with multiline for arguments
      - name: Build and Publish
        uses: hashicorp/packer-github-actions@master
        with:
          command: build
          arguments: |
            -on-error=abort
            -var security_group_id=sg-111111111111
            -var region=eu-west-1
            -var subnet_id=subnet-1111111111
            -var instance_type=t3.medium
            -var root_volume_size_gb=50
            -var runner_version=2.286.1
            -var tags="{ sandbox=${{ github.event.inputs.sandbox }} }"
          target: images/linux-amzn2/github_agent.linux.pkr.hcl
        env:
          PACKER_LOG: 1

I've tried various variations e.g.:
            -var tags="{ sandbox=${{ github.event.inputs.sandbox }} }"
            -var tags="{ sandbox=\"${{ github.event.inputs.sandbox }}\" }"
            -var tags="{ sandbox=true }"

I've also tried providing my arguments all on a single line and I get the same error.
If I remove the tag variable it works:
      # Had issues with multiline for arguments
      - name: Build and Publish
        uses: hashicorp/packer-github-actions@master
        with:
          command: build
          arguments: |
            -on-error=abort
            -var security_group_id=sg-111111111111
            -var region=eu-west-1
            -var subnet_id=subnet-1111111111
            -var instance_type=t3.medium
            -var root_volume_size_gb=50
            -var runner_version=2.286.1

Steps to Reproduce

Create a packer template that takes in a variable with the tags structure shown abve
Attempt to build said template providing the variable with the tags structure

I am also facing the issue. Can you please let me know what is the solution for this? I am not sure why it is closed without a solution.

It seems this repository has changed a bit since I used it and raised this issue. It was called hashicorp/packer-github-actions at the time which appears to be legacy, hashicorp/packer-github-actions worked as an abstraction to the packer binary. It now appears the repository instead is solely concerend with for setting up the packer binary for you to then use the binary directly itself instead of via a nice declarative interface. I believe I just did the tagging as an additional step so I didn't need a map.

Ok. Thank you for the quick response. However in my case, I want to merge some tags from SSM Parameter store of AWS along with some hardcoded tags while calling Packer Build from GitHub Actions. I have tried many things, but nothing seems to be working. It will be great, if you can post an example, if you know.

Either way it's a case of doing the tagging outside of the action with the aws cli. Going to close the issue as the repository now works fundamentally differently so this issue is no longer valid.


fix: Missing Scenario API in lower SAPUI5 versions

https://github.com/SAP/open-ux-tools/issues/2121

Consume scenario from control property editor common

@mmilko01 Can you please also add since JSDoc comment to the type definitions in sap.ui.fl.d.ts? So it is clearer in to future that this is not available for all UI5 versions.

Added with: d89ed6a42aac7bca00f416aa0ec57aa42012c7d7
Please take a look.


Fix unreadable sentence in localization doc

Fixes https://github.com/dotnet/AspNetCore.Docs/issues/18608

Thanks for calling it out @ssdevref and for fixing this @scottaddie. This happened in the API cross-link update sweep a few days ago ... 😈 Sneaky Markdown:tm: 😈 in a large PR.


Support BoxedUint::gcd(_vartime) where self and rhs have a different number of limbs

The PR currently has just a testcase illustrating the problem.
So the question is, what should the behavior be? We can equalize the sizes of the arguments at the top level, but that would make gcd() not constant time wrt numbers of limbs. Then again, would users assume that it is?

It's part of the general implicit widening problem: #312. Implicit widening may make sense.
In many places we currently just panic rather than performing implicit widening, relying on the caller to widen appropriately.

I can try to add implicit widening in a separate PR, unless you want to add it in this one. I think it's appropriate here.

That's fine, it can wait until the resolution on #312. It's just that the error caught me off-guard.

BoxedUnsatInt needs to allocate anyway, so we can implicitly widen there while also converting to u62-ish limbs

We need to equalize the number of limbs earlier, when making sure the first argument is odd and conditionally swapping them.

@fjarri I was suggesting finding the max of the two limb counts, similar to how it finds the max of two bits, then pass a limb count hint in when constructing BoxedUnsatInt.
That would be as opposed to calling BoxedUint::widen which would add another allocation.

But the difference in limb numbers will already lead to panic before that, in BoxedUint::gcd()

Aah! Yes, that is a problem, though there are several paths through Bernstein-Yang that avoid that.
I'm surprised there isn't a better length assert! for that function.

Actually, it won't even lead to panic if the first argument is longer, it'll just behave incorrectly.

Will merge this to have a set of test cases for widening behavior, and then I'll take a look at actually implementing it. It shouldn't be too hard.


Compatibility list of Zigbee Thermostats and HVACs units compatible with ZHA?

Could there be a compatibility list of Zigbee Thermostat and HVAC units compatible with ZHA climate?
@Adminiuga has just submitted a first pull request for "ZHA Climate" (beta) with thermostats support were he mentions "tested with Sinope and Zen Zigbee thermostats".

See new ZHA climate feature PR https://github.com/home-assistant/core/pull/35682 and docs https://github.com/home-assistant/home-assistant.io/pull/13506

As I do not yet own any Zigbee Thermostat and HVAC units I was wondering what other Thermostat and HVAC units are based on Zigbee devices and are or could be made compatible with ZHA climate feature?
As I understand it, the manufacturer's interpretation of the Zigbee specifications varies wildly between vendors as some device firmware developers deviate from standards, (which indeed is why ZHA Device Handlers are even needed in the first place).
Most thermostat and HVAC control devices also seem to have different feature sets, and not just by the fact that some full HVAC controllers (temperature, fan, heating/cooling system control) while others only have basic temperature controls (heating with no cooling, etc.).
To try to sort out this confusion, a few other projects, like ex. Zigbee2mqtt and deCONZ, has a wiki or webpages editable via GitHub with lists of "supported devices" which kind-of also acts as lists of recommended devices in regards with what features should at least work with ZHA.

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/information/supported_devices.md
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Supported-Devices

Quick google search found these devices, some of which are central thermostats / HVAC control units and others are thermostats with different feature set. Zigbee2mqtt pages does offer feature-sets.
Centralite Pearl Thermostat (3157100) - HVAC, fan, and A/C Controller

https://centralite.com/products/pearl-thermostat

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/3157100.md

Zen Thermostat (Zen-01 / Zen-01-W) - Zigbee Edition - HVAC controller (temperature, heating/cooling system control)

https://store.zenthermostat.com/products/zen-thermostat

Sinope TH1123ZB - Smart thermostat for electric heating 3000 W / 4000 W – Zigbee

https://www.sinopetech.com/us/product/smart-thermostat-for-electric-heating-3000-w-zigbee/

Sinope TH1124ZB

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/TH1124ZB.md

Sinope TH1300ZB - Smart floor heating thermostat 3600 W – Zigbee

https://www.sinopetech.com/us/product/smart-floor-heating-thermostat-3600-w-zigbee/

Sinope TH1400ZB - Low voltage smart thermostat 24 Vac – Zigbee

https://www.sinopetech.com/us/product/low-voltage-smart-thermostat-24-vac-zigbee/

Sinope TH1500ZB

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/TH1500ZB.md

Stelpro Ki Convector (ST218) line-voltage thermostat
Stelpro Ki (STZB402) line-voltage thermostat

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/STZB402.md

Stelpro Maestro (SMT402 & MT402AD) line-voltage  line-voltage thermostats

https://www.stelpro.com/en-CA/maestro-smart-thermostat

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/SMT402.md
https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/SMT402AD.md

Schneider Electric Wiser Thermostat Radiator Valve (WV704R0A0902) - Temperature, battery, keypad lock, heating demand

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/WV704R0A0902.md

Eurotronic Spirit Zigbee - Thermostat Radiator Valve (TRV)

https://eurotronic.org/produkte/zigbee-heizkoerperthermostat/spirit-zigbee/
https://eurotronic.org/wp-content/uploads/2019/11/Spirit_ZigBee_BAL_web_EN_November-2019.pdf

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/SPZB0001.md

Siterwell GS361A-H04 - TRV - Same Tuya hardware as Viessmann ZK03840 & Essentials Smart 120112?

https://www.china-siter.com/product/194.html

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/GS361A-H04.md

https://siterlink.en.alibaba.com/?spm=a2756.trade-order-list.0.0.38b976e9thNNyI&tracelog=from_orderlist_company

https://www.red-dot.org/project/siterwell-gs361-39193/

Viessmann ViCare (ZK03840) - TRV (Thermostat Radiator Valve) - Same as Siterwell GS361A-H04 based on Tuya hardware?
-https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/ZK03840.md
Essentials Smart (120112) - TRV (Thermostat Radiator Valve) - Same as Siterwell GS361A-H04 based on Tuya hardware?

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/GS361A-H04.md

Moes Radiator valve (HY369RT) - TVR (Thermostat Radiator Valve)- Based on Tuya Zigbee 3.0 compatible hardware?

https://www.moeshouse.com/products/zigbee-smart-thermostatic-radiator-valve-controller-trv-thermostat-tuya-temperature-voice-control-works-with-alexa-google-home

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/HY369RT.md

SASWELL SEA801 / SEA801-Zigbee (SEA801-Tuya-Zigbee) TVR - Based on Tuya Zigbee compatible hardware?

https://www.saswell.com/etrv-smart-radiator-valve-tuya-zigbee-thermostatic-radiator-valve-sea801-zigbee_p103.html

https://saswell.en.alibaba.com/product/60747147965-806204213/TUYA_zigbee_radiator_thermostat_wifi_thermostatic_radiator_valve.html

Leviton Wireless Omnistat2 (RC-2000WH / RC-2000WHZB) Multistage & Heat Pump Thermostat

https://www.leviton.com/en/products/RC-2000WHZB

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/RC-2000WH.md

eCozy Smart Thermostat (1TST-EU) - TVR (Thermostat Radiator Valve)

http://www.ecozy.de/en/support/thermostat

Danfoss Ally Radiator Thermostat (TRV)

https://zigbeealliance.org/zigbee_products/danfoss-ally-radiator-thermostat/

Bitron Video Wireless thermostat AV2010/32 902010/32

https://bvsite.smabit.eu/index.php/produkte/smart-home-produkte/funkthermostat/

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/AV2010_32.md

Hive Heating thermostat (SLR1b)  (thermostat, occupied heating, weekly schedule)

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/SLR1b.md

Hive Heating thermostat remote control (WPT1) (none, communicate via Hive Heating thermostat SLR1b)

https://github.com/Koenkk/zigbee2mqtt.io/blob/master/docs/devices/WPT1.md

@Hedda https://zigbee.blakadder.com/zha.html seems like a good source.

Hey there, I want to use the "Viessmann ViCare (ZK03840) - TRV (Thermostat Radiator Valve)" mentioned above, but it doesn't seem working currently. I tried paring it multiple times, but it just not work.
Does anyone have a solution for this?


docs: add child theme with custom homepage

closes #867
adds click-to-copy npm init @open-wc command to homepage, by creating a
Vue child theme

Is it possible to .trim() in the copy element? Of just manually collapse the HTML? Currently, the line breaks get copied and it will paste active (start the command without pressing Enter) into the command line.

good eye.
probably best is to wrap the text itself, and have the copy element extend to fill it's container via CSS.
also, NB: https://github.com/vuejs/vuepress/issues/1583#issuecomment-555022256

pushed a fix


UX: Remove AdminPageSubheader style override

In this core commit https://github.com/discourse/discourse/pull/29149 we
are changing the subheader title to H2 and making the size smaller,
this style override is no longer needed.

test flake


Issue a better error for exactOptionalPropertyTypes

A project under --strict will likely break in TypeScript 4.4, and it won't be obvious why.
foo/thing.ts:37:5 - error TS2322: Type 'SomeData | undefined' is not assignable to type 'SomeData'.
  Type 'undefined' is not assignable to type 'SomeData'.

37     data: data,
       ~~~~

What I would propose is that we give some better error message in these cases such as
The source property type 'SomeData | undefined' is not compatible with the target property type 'SomeData' under '--strictOptionalProperties'. Consider adding 'undefined' to the type of the target property.

This could then be given a quick fix.
We could give this error when

The source property is optional and the target type includes undefinedness
The types would otherwise be compatible if you were to remove the undefined from the target.

@simeyla has also filed #45058 where, if directly assigning an undefined to a property, we could potentially suggest a delete operator.


Return binary

In your comments you mention it's not possible to send binary via AWS API Gateway as it expects JSON response from Lambda. You can do it with:
serverless.yml
plugins:
  - serverless-apigwy-binary # <-- Add
...
functions:
  run:
    description: Run headless Chromium
    memorySize: 1536
    timeout: 30
    handler: handler.run

    events:
      - http:
          path: chrome
          method: get
          contentHandling: CONVERT_TO_BINARY. # <-- Add

handler:
{
                        statusCode: 200,
                        isBase64Encoded: true,  // <-- Add
                        body: screenshot.toString('base64')
}

I'm working on a PR right now.

Hi @willfarrell that's great news!
Please be sure to raise your PR against the develop branch. I think perhaps a standalone example in serverless-framework/ would be a good place to put an example binary-supported service.

Will do. I am running into the ES6 not compiling for tests and serverless.
$ yarn test
/Users/willfarrell/Development/github/serverless-chrome/examples/serverless-framework/aws/src/captureScreenshot.test.js:15
import test from 'ava';
^^^^^^
SyntaxError: Unexpected token import

Am I missing a flag somewhere? I didn't see anything in the docs.

Gah, webpacks was removed from develop ... I'll PR what I have now. It should work as is. I'll let you decide how you want webpacks to work for the project.


Object.assign doesn't work by default in Internet Explorer

We use Object.assign in the following line - https://github.com/scniro/react-codemirror2/blob/3250f5833f48e65a1b560dc3059f0ce4ed0771fd/src/index.tsx#L616
Unfortunately, Internet Explorer doesn't have a definition for the same. And its very difficult to override object.assign from an external module :(
Can we depend on an external library (like core-js) to get the definition for assign and use that instead?

@anandsainath Are you using webpack/babel? I suppose I can add a polyfill, but it feels so... gross. I'll keep you posted with if I add anything but I definitely think you can handle this through a bundler.

fixed with the 4.3.0 release

@scniro Thank you! :)


envoy send RST tcp segment

After three handshakes, the HTTP request is sent, and the RST fragment is returned

Sorry can you elaborate on this some more? Configuration used, how you are reproducing this, what you expect, etc.

Sorry can you elaborate on this some more? Configuration used, how you are reproducing this, what you expect, etc.

Envoy acts as the data control surface for Istio,Istio redirects the port through the iptable to 15006. The envoy listens to 15006. But when the client connects the envoy through 15006, the result envoy sends RST.

Sorry there's not much I can do without more information about the config Envoy is using. I'm guessing there is a misconfiguration that causes Envoy to reset the incoming request.
I suggest bringing this to the Istio folks brings to help understand what configuration Envoy is using here.

The tcp hand shake is complete: iptables says yes. It's very likely the envoy listener is ready.
Could you turn on the access log at envoy? With the access log you can understand if a filter chain is found or not. If the filter chain is selected, usually the detailed error flag is revealed in the access log

The tcp hand shake is complete: iptables says yes. It's very likely the envoy listener is ready.
Could you turn on the access log at envoy? With the access log you can understand if a filter chain is found or not. If the filter chain is selected, usually the detailed error flag is revealed in the access log

thank you

Sorry there's not much I can do without more information about the config Envoy is using. I'm guessing there is a misconfiguration that causes Envoy to reset the incoming request.
I suggest bringing this to the Istio folks brings to help understand what configuration Envoy is using here.

thank you

Sorry there's not much I can do without more information about the config Envoy is using. I'm guessing there is a misconfiguration that causes Envoy to reset the incoming request.
I suggest bringing this to the Istio folks brings to help understand what configuration Envoy is using here.

When you access an envoy using iptables to redirect ports, does an envoy have the ability to disable requests from an upstream service that does not exist on a port?For example, the upstream service listens on 80, which I can only access through 80, even though the port is redirected

The tcp hand shake is complete: iptables says yes. It's very likely the envoy listener is ready.
Could you turn on the access log at envoy? With the access log you can understand if a filter chain is found or not. If the filter chain is selected, usually the detailed error flag is revealed in the access log

When you access an envoy using iptables to redirect ports, does an envoy have the ability to disable requests from an upstream service that does not exist on a port?For example, the upstream service listens on 80, which I can only access through 80, even though the port is redirected

When you access an envoy using iptables to redirect ports, does an envoy have the ability to disable requests from an upstream service that does not exist on a port?For example, the upstream service listens on 80, which I can only access through 80, even though the port is redirected

Sorry I cannot understand. Can you rephrase?
Meanwhile please check if bind_to_port works for you https://github.com/envoyproxy/envoy/blob/58606021040b5719db9b6ff3d18ceebdff50fcda/api/envoy/config/listener/v3/listener.proto#L276


Allow RO servers to run without Kerberos enabled.

In order to address Issue #278.

lgtm

Thanks, I merged it in.


Edit readme

Add "display" prop to the Table of Style Props

Codecov Report

Merging #114 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #114   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           5      5
  Lines         190    190
=====================================
  Hits          190    190

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 671be0c...7d6e021. Read the comment docs.

Thanks!


Create local script to generate distributable artifacts

This should output the following:

Shared library for musl (.so/.dll/.dylib)
Header file (.h)
C++ wrapper functions (.cpp/.hpp)

The script can be referenced here: https://github.com/contentauth/c2pa-c/blob/main/Makefile


merge everything add dropdown styling

You have one file you are putting in my _notebooks directory without proper location.  Also, you have a lot of images and you should put them into a directory to help me remember where they belong
/csp/fundamentals/...


Making annotation be italic

Just a personal opinion. Italic style of @property looks probably better.
In addition, according to the generated html files, the @property also appears to be italic.

Thanks @terryzhuo110  for this pull request.


Add a difficulty sort

@monizb can you help me to check this problem? When I click Details, I got errors of aria-. Even though my code is same with the code in material ui documentations.

@monizb can you help me to check this problem? When I click Details, I got errors of aria-. Even though my code is same with the code in material ui documentations.

Which Details are you talking about?

@kodelebah no worries, that does happen sometimes, if you there is one small change here to be made, instead of calling it Difficulty level, can we rather say: "No. of PRs:" ?

@kodelebah no worries, that does happen sometimes, there is one small change here to be made, instead of calling it Difficulty level, can we rather say: "No. of PRs:" ?

Okay, I will changed it later when I fix this issue #6.

@kodelebah Thank you soo much for this PR!! 🥳🥳


/usr/lib/udev is hardcoded

When I run generate-zbm on Gentoo (openrc, USE=split-usr in case that makes a difference), I get:
# generate-zbm
Mounting /boot/efi
Creating ZFSBootMenu 1.8.1 from kernel /boot/vmlinuz-5.4.51-gentoo-x86_64
dracut-install: ERROR: installing '/usr/lib/udev/vdev_id'
dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.djkjGC/initramfs -a /usr/lib/udev/vdev_id
dracut: failed to install essential executable '/usr/lib/udev/vdev_id'
Failed to create /tmp/mo7y7dzWV3/zfsbootmenu.efi
Unmounting /boot/efi

I see that /usr/lib/udev is hardcoded in https://github.com/zbm-dev/zfsbootmenu/blob/ac8a8edafbbcd8e22013de676982edcd590445d9/90zfsbootmenu/module-setup.sh . If I change every /usr/lib/udev to /lib/udev, the problem goes away.

Thank you for opening this issue. I'll get a more permanent fix for you to test later today.

Thank you for opening this issue. I'll get a more permanent fix for you to test later today.

Upstream ZFS uses some placeholder strings and replaces them on install, that's probably a good approach here too.

Upstream ZFS uses some placeholder strings and replaces them on install, that's probably a good approach here too.

Looks like genkernel (which I use for the initramfs) finds the directory using pkg-config: https://github.com/gentoo/genkernel/blob/369cfa98f72675a285ec98439e9054ab57b234c9/gen_funcs.sh#L1142

Looks like genkernel (which I use for the initramfs) finds the directory using pkg-config: https://github.com/gentoo/genkernel/blob/369cfa98f72675a285ec98439e9054ab57b234c9/gen_funcs.sh#L1142


Nuget Installation Fails

When attempting to install the v10.0.0-beta release I got the following errors form the Nuget package manager:
Restoring packages for NativeBindingsGenerator.csproj...
Restoring packages for NativeBindingsGenerator.csproj...
  GET https://api.nuget.org/v3-flatcontainer/clangsharp.pinvokegenerator/index.json
  OK https://api.nuget.org/v3-flatcontainer/clangsharp.pinvokegenerator/index.json 143ms
  GET https://api.nuget.org/v3-flatcontainer/clangsharp.pinvokegenerator/10.0.0-beta/clangsharp.pinvokegenerator.10.0.0-beta.nupkg
  OK https://api.nuget.org/v3-flatcontainer/clangsharp.pinvokegenerator/10.0.0-beta/clangsharp.pinvokegenerator.10.0.0-beta.nupkg 151ms
  GET https://api.nuget.org/v3-flatcontainer/clangsharp/index.json
  OK https://api.nuget.org/v3-flatcontainer/clangsharp/index.json 152ms
  GET https://api.nuget.org/v3-flatcontainer/clangsharp/10.0.0-beta/clangsharp.10.0.0-beta.nupkg
  OK https://api.nuget.org/v3-flatcontainer/clangsharp/10.0.0-beta/clangsharp.10.0.0-beta.nupkg 154ms
Installing ClangSharp 10.0.0-beta.
Installing ClangSharp.PInvokeGenerator 10.0.0-beta.
Installing NuGet package ClangSharp.PInvokeGenerator 10.0.0-beta.
System.Threading.Tasks.TaskCanceledException: A task was canceled.
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.ProjectSystem.CommonProjectSystemTools.GetResultOrThrowFirstException[T](Task`1 task)
   at Microsoft.VisualStudio.ProjectSystem.Build.BuildUtilities.<>c.<<AppendFlushLoggersTask>b__17_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.ProjectSystem.Build.BuildUtilities.<>c__DisplayClass16_0.<AppendUnregisterLoggersTask>b__0(Task`1 flt)
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Microsoft.VisualStudio.ProjectSystem.Build.BuildProject.<BuildCoreAsync>d__97.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Microsoft.VisualStudio.ProjectSystem.Build.BuildManagerHostBatchingService.<SubmitBuildAsync>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.VisualStudio.ProjectSystem.Build.BuildProject.<BuildCoreAsync>d__97.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.ProjectSystem.Build.BuildProject.<BuildAsync>d__85.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Microsoft.VisualStudio.ProjectSystem.References.ResolvableReferencesProviderBase`2.<CalculateResolvedReferenceItemsAsync>d__61.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.ProjectSystem.ConfiguredProjectCache`1.<>c__DisplayClass16_0.<<GetValueSlowAsync>b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Threading.JoinableTask.<JoinAsync>d__68.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Threading.JoinableTask`1.<JoinAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.ProjectSystem.ConfiguredProjectCache`1.<GetValueSlowAsync>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.ProjectSystem.References.ResolvableReferencesProviderBase`2.<GetResolvedReferenceAsync>d__32.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.ProjectSystem.References.ResolvableReferencesProviderBase`2.<>c__DisplayClass43_0.<<AddAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Threading.JoinableTask.<JoinAsync>d__68.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Threading.JoinableTask`1.<JoinAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.ProjectSystem.ProjectLockService.<ExecuteWithinLockAsync>d__114`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.VisualStudio.ProjectSystem.ProjectLockService.<ExecuteWithinLockAsync>d__114`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.Threading.AwaitExtensions.ExecuteContinuationSynchronouslyAwaiter`1.GetResult()
   at Microsoft.VisualStudio.ProjectSystem.References.ResolvableReferencesProviderBase`2.<AddAsync>d__43.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.VisualStudio.ProjectSystem.References.PackageReferencesService.<AddAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NuGet.PackageManagement.VisualStudio.NetCorePackageReferenceProject.<InstallPackageAsync>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NuGet.PackageManagement.NuGetPackageManager.<ExecuteBuildIntegratedProjectActionsAsync>d__78.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NuGet.PackageManagement.NuGetPackageManager.<ExecuteNuGetProjectActionsAsync>d__76.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NuGet.PackageManagement.NuGetPackageManager.<ExecuteNuGetProjectActionsAsync>d__75.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NuGet.PackageManagement.NuGetPackageManager.<ExecuteNuGetProjectActionsAsync>d__74.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NuGet.PackageManagement.UI.UIActionEngine.<ExecuteActionsAsync>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NuGet.PackageManagement.UI.UIActionEngine.<>c__DisplayClass12_0.<<PerformActionImplAsync>b__0>d.MoveNext()
Time Elapsed: 00:00:02.5083459
========== Finished ==========

Second try seemed to work


[Feature request] Modernizing the XAML Controls Gallery icon

Summary of the new feature/enhancement
The current XAML Controls Gallery icon is in the MDL2 style. Since WinUI is modernizing the Windows XAML platform, the gallery app icon should reflect this as well. It should be at the front of innovation and reflect the latest changes of the Windows platform. In 2020, we'll see lots of inbox application icons modernized (more on Microsoft Design's push to re-design hundreds of OS icons here).
Proposed technical implementation details
The proposal is to redesign the current XAML Controls Gallery icon, so it feels part of the Windows 10 family of experiences (e.g. Terminal, other inbox apps)

While add it, maybe we need to change the (tile) accent color as well so it fits in a bit more with the other icons.

Would be nice if we can bring the WinUI logo to this app icon as well!

For context, here is the current Xaml Controls Gallery icon:

I gave it a shot.. This is a 1:1 port to the newer style. Concept 2 is using similar colors like the new Calculator icon.

I designed the WinUI Library logo, and so something linked to it may make sense.  There was talk at the time about the app possibly being renamed WinUI Controls Gallery.

Some of the early ideas I proposed for the WinUI logo was designing the 3 matching logos

I think it would be better to continue this discussion in #210 , so that we don't have multiple threads for the same issue.

Agreed that we shouldn't have multiple threads on this issue. I think we're going to get more traction on this thread, so I'm going to close #210 as a dupe and localize the conversation here.

@niels9001 - I'm loving this direction as it seems like a natural evolution of the existing icon. A thought: what if it incorporated more color? I'm thinking something like the blue in the Mail icon:

Wasn't this an old issue before?

Excited about this, I can have a go at doing some designs, but not sure I'll be able to come up with something fruitful 😅

Here are three concepts I came up with.

Just a quick idea

Here are two more concepts I came up with.

Just a recommendation, if someone downvotes an idea, they should explain why. Without context, it makes it harder for everyone to work on and improve their designs.

@mdtauk, I really like the concept behind what you posted on the other thread (linked below) because it establishes this idea that the Xaml Controls Gallery (XCG) is a breakdown or dissection of WinUI's control offering. It gives me this "let's look at the inside of it" feeling that's an inherent step in a developer's journey.
https://github.com/microsoft/Xaml-Controls-Gallery/issues/210#issuecomment-536199523

Please don't let me over influence this conversation though. @stmoy is the app owner, I'm just joining in on the fun. 😄

Another idea

@mdtauk Great stuff! I really like your concept where we have a similar style for all 3 icons (well at least XAML Controls and the Toolkit, since these are actual apps).
It's important that these icon scale well as well - would be nice to see some smaller versions (and maybe on a tile?) to see how that would work.
Ideally we'd create some sort of template we can all use and test these!

I created a basic template based on @niels9001 idea, I will continue working on it and adding additional places to visualize the icon at different scales.
https://www.figma.com/file/XpDRbAlSKC9rV3MNLqAPJS/XAML-Controls-Gallery-Icon?node-id=0%3A1

@mdtauk Great stuff! I really like your concept where we have a similar style for all 3 icons (well at least XAML Controls and the Toolkit, since these are actual apps).
It's important that these icon scale well as well - would be nice to see some smaller versions (and maybe on a tile?) to see how that would work.
Ideally we'd create some sort of template we can all use and test these!

Here's my attempt — it is heavily inspired by the great work done by @niels9001 and @mdtauk ! :)

Here is another concept.

I love the creativity and inspiration shown on this thread!
I'm noticing some themes that I wanted to highlight for more riffing:

Many of the icons are a stack or collection of elements. I really like this motif because the Gallery is fundamentally a collection of samples and controls.

Many submissions include < / > - this metaphor directly relates to the markup part of Xaml. Even the new WinUI logo incorporates the brackets - but in a more subtle, nuanced way. I wonder if we need to overtly include < / > or if the icon can be more subtle about the brackets? More specifically, I wonder if it'd be possible to directly incorporate the WinUI logo in the icon to make the relationship more explicit?

The new Fluent iconography includes depth, color, texture, and shadows. In contrast, the old XCG icon was flat-white per MDL2 guidelines. Most of the submissions in this thread include depth, shadows, and texture - but I'd love to see how color can also be used in creative ways to do things like build hierarchy.

I'm so excited to see what you come up with. Y'all rock.

Here are a few more ideas.

I like the concepts

and

the most for now have they are referencing the WinUI product while also reflecting the building-blocks showcase nature of the Xaml Controls Gallery app.
I don't think we need to make the new logo cupe based as theat adds additional load to the user's eyes as seen in the cases so far (3D + different depth + different colors) and to be honest, I'm having a bit of a challenge to read the XCG's mission out of these versions for now.
As such, my current preferences are the two concepts shown above as they perfectly cover the connection to WinUI and the control-sample nature of the XCG!

I'm not that good at designs, but here's potentially something for inspiration:

I like the idea of having a file tab since it indicates that it can be searched through. This is just one draft but I'm happy to go back and make changes/share the file based on feedback.

I couldn't let you have all the fun without me! 😉
The general consensus across Twitter and GitHub is that folks loved @niels9001's original concepts:

I really liked that these concepts added some Fluent flair to the original Gallery icon while still maintaining consistency with the current layered icon. However, I'd really like to take this opportunity to move to something a bit more colorful.
Taking inspiration from the above concepts, I created this:

This icon moves away from the current Gallery color and instead aligns with the colors found in the WinUI logo.
Thoughts? Because Niels's logo had the most positive feedback and because I really want some color in the logo, we're probably going to go with this version pending significant feedback.

@stmoy I would soften the corner radii to match the new fabric icons released in Windows 10.

@stmoy
I love that!!! Adding the WinUI color looks great! Maybe change the corner radius (as @yaichenbaum mentioned) so it's slightly less round and in line with the other icons?
I think you have a winner here! Would be nice to have a similar version of that for the Community Toolkit app as other proposed above :)? I will open up an issue on their repo as well and mention this one!

Second what @yaichenbaum and @niels9001 suggested about softening the corner radius 🙂

Agree with the tighter corners. How does this look? I used @yaichenbaum's previous reply as a guide. I also slightly modified the shadows.

This gif compares the old and new:

It looks really good! Would it be possible to get someone who worked on the other new icons in Windows 10 to look it over and see if it can be polished a bit further?


ValueError related error

I'm trying to redo the coding and found in the environment there is the error raised:

ValueError: shapes(2,2)and(1,2)not aligned: 2(dim 1)!= 1(dim @)
And as the code is somewhat 6 years from now I checked the error raise message and the code it should be a problem relating with the environment and package editions, would you please provide the virtual environment requirements which can successfully run the main script? Thank you.

Problem solved by joint discussion:
For those who are facing the same issues please refer to the _local_da_global_ds function and do restrictions on the definition of the matrixs.

Left is Simpleshipai and right is ShipAI, for reason of finding the issue I'm using the SimpleshipAI and being questioned about ShipAI I checked the code and found the bug.


Feature/countries

Implement selection of countries

Multiple countries at once/tickbox possible, instead of single country selection? I type frequently in French and Portuguese - while those two share a few accents, there are a bunch that aren't shared. I'm sure there are others, e.g. a Norse person who's learning a Latin language.
Heh... even English has a few math symbols/em dashes/archaic accents that are unrepresented... æ œ – (em dash, I think...?) - (normal dash) ⁸ (superscript numbers) ½ (fractions) ≠≈ ø × √ ÷ (math symbols, perhaps on number keys?) ⁑ ⁂ ★ § ‼ ‽ (typography/writing), α β γ (Greek letters) ...
Idea: a "Maths" flag that can be checked for math symbols, English flag for archaic British English characters, a "Writers" flag for typography characters like dashes, daggers/asterisks

@Darthagnon I created #22 and #23 to keep a trace.
Math is something I already had in mind, but require some work to do it (it is not just adding symbol, but the layout of the different type of keyboards can create some trouble. So it will have to wait a bit for the app to be evolve further.


video writer fails for uncompressed video with latest ffmpeg 2.8

When using cv2.VideoWriter (tested in Python, not tested in C), the writer silently fails to write uncompressed video file (tested with mkv, avi, wmv containers) when using ffmpeg 2.8 or ffmpeg snapshot from today (2015-10-02). The generated files have nearly zero size (probably only headers are written). The writer works with ffmpeg 2.7.2.
ffmpeg is downloaded from http://ffmpeg.org/releases/
tested on Ubuntu 15.04
Testing code:
import numpy as np
import cv2
import os

np.random.seed(0)

# test different containers
for fn_mask in ['test_%s.mkv', 'test_%s.avi', 'test_%s.wmv']:
  # test different codecs
  for fourcc_name, fourcc in [('uncompressed', 0), ('mp4v', cv2.VideoWriter_fourcc(*'mp4v')), ('xvid', cv2.VideoWriter_fourcc(*'MJPG'))]:
    fn = fn_mask % fourcc_name

    writer = cv2.VideoWriter(fn, fourcc, 25, (100, 100))

    # generate random 100x100 images
    for i in range(0,100):
        img = np.random.random_integers(0, 255, (100,100,3)).astype(np.uint8)
        writer.write(img)

    writer.release()

    # test result (is generated file too small?)
    fs = os.path.getsize(fn)

    print '%s [%dB] [%s]' % (fn, fs, 'FAIL' if fs<10000 else 'OK')

Output:

opencv-3.0.0 compiled with ffmpeg 2.7.2 - is OK

test_uncompressed.mkv [1504712B] [OK]
test_mp4v.mkv [309958B] [OK]
test_xvid.mkv [819482B] [OK]
test_uncompressed.avi [1508086B] [OK]
test_mp4v.avi [319296B] [OK]
test_xvid.avi [1291120B] [OK]
test_uncompressed.wmv [1517443B] [OK]
test_mp4v.wmv [320684B] [OK]
test_xvid.wmv [826237B] [OK]

opencv-3.0.0 compiled with ffmpeg 2.8 - FAILS

test_uncompressed.mkv [587B] [FAIL]
test_mp4v.mkv [310026B] [OK]
test_xvid.mkv [819550B] [OK]
test_uncompressed.avi [5686B] [FAIL]
test_mp4v.avi [319296B] [OK]
test_xvid.avi [1291120B] [OK]
test_uncompressed.wmv [533B] [FAIL]
test_mp4v.wmv [320684B] [OK]
test_xvid.wmv [826237B] [OK]

opencv-master (from 2015-10-02) compiled with ffmpeg 2.8 - FAILS

test_uncompressed.mkv [587B] [FAIL]
test_mp4v.mkv [310026B] [OK]
test_xvid.mkv [819550B] [OK]
test_uncompressed.avi [5686B] [FAIL]
test_mp4v.avi [319296B] [OK]
test_xvid.avi [1291120B] [OK]
test_uncompressed.wmv [533B] [FAIL]
test_mp4v.wmv [320684B] [OK]
test_xvid.wmv [826237B] [OK]

opencv-master (from 2015-10-02) compiled with ffmpeg snapshot (from 2015-10-02) - FAILS

test_uncompressed.mkv [584B] [FAIL]
test_mp4v.mkv [310022B] [OK]
test_xvid.mkv [819397B] [OK]
test_uncompressed.avi [5686B] [FAIL]
test_mp4v.avi [319194B] [OK]
test_xvid.avi [1291120B] [OK]
test_uncompressed.wmv [531B] [FAIL]
test_mp4v.wmv [320681B] [OK]
test_xvid.wmv [826235B] [OK]

I confirm that OpenCV-master with

ffmpeg 2.7.2 works fine.
ffmpeg 2.8 writes only headers in case of fourcc=0.

Existed OpenCV debug logs don't show warnings/problems about failed ffmpeg calls.
Currently I have no ideas about problem location, but looks like that some incompatible changes were introduced into ffmpeg.

I just run test bin/opencv_test_videoio
passes for ffmpeg 2.7.2
fails in one test for ffmpeg 2.8:
[ RUN      ] Videoio_Video.ffmpeg_writebig
ERROR: File name: /tmp/__opencv_temp.NOIuEr.00000000.avi is very small (data write problems?)
ERROR: File name: /tmp/__opencv_temp.vmnbHQ.30323449.avi is very small (data write problems?)
OpenCV: FFMPEG: tag 0x34363248/'H264' is not supported with codec id 28 and format 'mp4 / MP4 (MPEG-4 Part 14)'
OpenCV: FFMPEG: fallback to use tag 0x00000021/'!???'
/home/axe/opencv/opencv-3.0.0-ffmpeg-2.8/build/opencv-3.0.0/modules/ts/src/ts.cpp:515: Failure
Failed

        failure reason: Invalid function output
        test case #-1
        seed: ffffffffffffffff
-----------------------------------

[  FAILED  ] Videoio_Video.ffmpeg_writebig (10069 ms)

Failed cases is fourcc=0 and fourcc=I420. Both are uncompressed cases.
H264 is warning only, but file is OK (ffmpeg can't use FOURCC for mp4 files directly).

I run git bisect on ffmpeg repo and it finds this commit:
https://github.com/FFmpeg/FFmpeg/commit/c41a59330f49c16acfa9b0552608fa1f41a0d823
c41a59330f49c16acfa9b0552608fa1f41a0d823 is the first bad commit
commit c41a59330f49c16acfa9b0552608fa1f41a0d823
Author: Michael Niedermayer<EMAIL_ADDRESS>Date:   Sat Sep 5 11:56:23 2015 +0200

    avcodec/rawenc: Use AVFrame parameters instead of AVCodecContext

    This allows encoding raw frames with changing dimensions

    Signed-off-by: Michael Niedermayer<EMAIL_ADDRESS>
:040000 040000 6ef39a3a0ce9828e776c19929c9edf9be478352b b9880d04586786dfaa7b0846a38a8f440d6e6a80 M	libavcodec

@pcampr I added PR with properly filled AVFrame fields. Please take a look on it.

@alalek I tried your PR in my build (ffmpeg 2.8) and it works (both my py test script and bin/opencv_test_videoio test). Seems completely fine now :+1:
Thanks for really fast fix!


To add to PG from our users

As far as I think, simple points that can be included are:
(These are not necessarily cocos2d-x specific points but can be included to make PG as complete guide from start to shipment using cocos2d-x)

Where all to change the min/max-sdk version so that it's compatible with different android versions while we're building finally.
How to remove those libraries which are not being used so that the final apk can be of as low size as possible.
Changing package name. It's easy but can be included if you want.
How to set proguard settings
I'll be shipping my first game after a month or so, so I am not sure what exactly people face or aren't aware of while shipping the game.

Original topic: http://discuss.cocos2d-x.org/t/programmers-guide/30622

@slackmoehrle
This link has some key points that one should keep in mind to reduce apk size. These points are difficult to find online at one place. PG can consolidate good points for cocos2d-x games.
https://medium.com/pregbuddy-engineering/how-we-reduced-our-android-app-size-by-65-54b17ae9a3c6#.qqluopy6u

I'll keep the list from my side updated here.
1) There are several mobiles with different architectures. So, building for each or one apk is enough, using APP_ABI := armeabi armeabi-v7a x86