esp_mqtt_client_subscribe macro _Generic error for const char* topic type (IDFGH-12386)

Answers checklist.

[x] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.2.1
Operating System used.
Linux
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
What is the expected behavior?
Expected that esp_mqtt_client_subscribe with const char* second param will be expanded to esp_mqtt_client_subscribe_single
What is the actual behavior?
Build failed because esp_mqtt_client_subscribe macro does not support const char*, only char*
Steps to reproduce.

Call esp_mqtt_client_subscribe from C source, pass const char* as second arg.
Try build

Build or installation Logs.
/root/esp/v5.2.1/esp-idf/components/mqtt/esp-mqtt/include/mqtt_client.h:464:84: error: '_Generic' selector of type 'const char *' is not compatible with any association

More Information.
API Reference instruct use char* if I want to single subscribe, but in fact inside esp-idf does not change this code and it should be const. Cast to char* seems bad practice. Besides esp_mqtt_client_subscribe_single expect const char* param, so it is types mismatch. You can just add const char *: esp_mqtt_client_subscribe_single, \  in 465 line of mqtt_client.h.

https://github.com/espressif/esp-mqtt/commit/32102558d3c0d58c8ed45e0029a29da26cb398a5#r139737900

@euripedesrocha

espressif/esp-mqtt@3210255#r139737900

Yep:)

I am still having this error in idf-5.2.1.

This is an bug, not a feature. It's been fixed on master, and should be backported to release/v5.2 at least.

Hi @KaeLL and @Zeni241 this will be backported.

I found that its still not be backported. Any hope in near future????

@euripedesrocha Thanks for info, I will check and report if any problem.


Fix Basketball Player Injury Status

Fixes #178 and adds injured field to player object

Codecov Report

Merging #180 (a838fd7) into master (c688b2a) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #180      +/-   ##
==========================================
+ Coverage   93.31%   93.33%   +0.01%
==========================================
  Files          22       22
  Lines         868      870       +2
==========================================
+ Hits          810      812       +2
  Misses         58       58

Impacted Files
Coverage Δ

espn_api/basketball/player.py
96.29% <100.00%> (+0.29%)
:arrow_up:

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 c688b2a...a838fd7. Read the comment docs.

Codecov Report

Merging #180 (a838fd7) into master (c688b2a) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #180      +/-   ##
==========================================
+ Coverage   93.31%   93.33%   +0.01%
==========================================
  Files          22       22
  Lines         868      870       +2
==========================================
+ Hits          810      812       +2
  Misses         58       58

Impacted Files
Coverage Δ

espn_api/basketball/player.py
96.29% <100.00%> (+0.29%)
:arrow_up:

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 c688b2a...a838fd7. Read the comment docs.


ksp-1.9.0-1.0.12 is too old for kotlin-1.9.10

If I use MocKMP ich get "ksp-1.9.0-1.0.12 is too old for kotlin-1.9.10. Please upgrade ksp or downgrade kotlin-gradle-plugin to 1.9.0." by build the Projekt. Is that a Problem?

Facing the same issue.

MocKMP 2.0 has been released and does not apply the KSP plugin anymore.
You are therefore free to apply the version you want ;)


Add Random function to template functions

Adds Random function to pick N random items from sequence.
The function can be used to generate random content to the sites. For example to display random quote or display list of random blog posts.
It of course should be noted that in a context of STATIC site generator randomising is bit odd. However sites that are updated regularly or even automatically can achieve benefits from this. Also random works fine when used in a single-templates.

Looks good to me, and I agree about the usefulness.
But I would suggest to rename the function to shuffle -- which is what this does, isn't it?
(I will have a look into that failing test on Windows -- not related to this)

I agree that the shuffle would be more descriptive name. Maybe the count parameter should also be removed as the template library already contains functions for slicing sequences (first, ```after`` etc.). That way the function would better follow the single responsibility principle.

Yes, agree, this would be much cleaner without the count. The unix way.

@EitZei any luck with the windows testing? I'd like to merge it if it's ready.

the windows build issues were from somewhere else. I've merged this as 9008ac0. Thanks for your contribution @EitZei !

@EitZei, could open a new pull request and add a few words about shuffle in the documentation?

@digitalcraftsman Will do.

Thank you.


Enable audio peaks to be passed as a param

This should address https://github.com/mspae/react-wavesurfer/issues/14

@mspae I've just merged https://github.com/mspae/react-wavesurfer/pull/17 as this enabled peaks but only for HTMLElements.

Awesome, was just about to do the same. I've published it as 0.5.0
Thanks!


FStar.Set.as_list doesn't extract to OCaml

FStar.Set.as_list is defined in terms of as_set' which already has a note
(* WHY IS THIS HERE? It is not strictly part of the interface *)
let rec as_set' (#a:eqtype) (l:list a) : set a =

Because this function defined in the .fsti file but not in the .fst or in ml/FStar_Set.ml, no code is generated for as_set' and as a result OCaml compilation fails on modules that call FStar.Set.as_list:
179 |              FStar_Set.union (FStar_Set.singleton hd) (FStar_Set.as_set' tl))
                                                             ^^^^^^^^^^^^^^^^^
Error: Unbound value FStar_Set.as_set'

(The extracted code would probably be fine if it was a constant list?  I think that's the intent of using normalize_term here.)
Workaround: copy the definition of as_list' into the calling module and use that instead.

Hi @mgritter , thanks for the report. Would you be interested in doing a PR that fixes it by adding definitions of both as_set and as_set' in ulib/ml/FStar_Set.ml, they can be defined as BatSet.of_list. And yes, for literal lists, F* would reduce as_set' and this would work.

I'd be happy to take a look.  Is there a way to write an extraction unit test that I should follow?
It looks like adding the .fst file to SHOULD_EXTRACT_CLOSE in bug-reports/Makefile will try to extract and run the code?


Windows Deployment

can u give step by step tutorial on howto deploy this on window,including the bower and grunt installation,. I already try on my own but it is not successful. thanks.

tried to install on Windows 10 64-bit with Xampp installed and stuck at that.. can u help me solve it. Already try a couple of solution but still the same prob


Soda having small lag spikes on a simple project

When running the server_in_smoke.ms example project (after replacing soda.exe with the appropriate OS-specific version), the game frequently spikes below 30 FPS (especially when updating multiple sprites at once), but otherwise has a stable 60 fps. Is anyone else experiencing this issue? If so, why might this be happening with such a relatively small project? (comment line 11 to see the lag when creating new sprites on a smaller project)
Tested on the lastest soda build, on windows 10.
soda fps lag.zip

Are you sure that project is complete?  I seem to be missing spriteFont.ms (which windowManager.ms is trying to import).

...I did try commenting out line 11, which eliminated the errors, but no matter how furiously I click to create puffs of smoke(?), my "Lagspikes Total:" is still 0.


Version 1.0.0

This version introduces some new features:

[x] lots of refactoring to code base
[x] create test_with_server macro. No more need to start a server each test.
[x] separate responses for a path using the route macro. See #21.
[x] the macros can receive some arguments, like default_response.
[x] dynamic responses using %Response{} struct. See #23.
[x] FakeServer.Status will be replaced by %Response{}, that is much more flexible.
[x] introduce FakeControllers. With it, FakeServer calls a function to choose the correct reply.
[ ] better docs

Coverage decreased (-0.2%) to 98.387% when pulling 60cd559b48d716a876e823d5e1971d52aa23c61b on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.2%) to 98.387% when pulling 60cd559b48d716a876e823d5e1971d52aa23c61b on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.2%) to 98.387% when pulling b588476dace0e51fcf4d6ee66566245fcd367b6e on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.2%) to 98.387% when pulling b588476dace0e51fcf4d6ee66566245fcd367b6e on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.2%) to 98.387% when pulling a00815c1ceb5ab544cef72fb02d373e1796eca14 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.2%) to 98.387% when pulling a00815c1ceb5ab544cef72fb02d373e1796eca14 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.2%) to 98.387% when pulling a00815c1ceb5ab544cef72fb02d373e1796eca14 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.2%) to 98.387% when pulling a00815c1ceb5ab544cef72fb02d373e1796eca14 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Cool. It's a great improvement to the API. +1 to 1.0.0 release for this.

Coverage decreased (-17.1%) to 81.481% when pulling 4e2c4a0c5def8896668c259c9c8b0b1a5d1dbec1 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage increased (+0.1%) to 98.765% when pulling bff22b6f4df43e041f0f8757f28c3eeb685e09d2 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.02%) to 98.611% when pulling 3023d353956e3af85578716dac74a7502052c0b0 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.02%) to 98.611% when pulling 3023d353956e3af85578716dac74a7502052c0b0 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.02%) to 98.611% when pulling 3023d353956e3af85578716dac74a7502052c0b0 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.02%) to 98.611% when pulling 3023d353956e3af85578716dac74a7502052c0b0 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.02%) to 98.611% when pulling 4b624a26fbb24f512b5aa9a98005f19ee4d21322 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.02%) to 98.611% when pulling 4b624a26fbb24f512b5aa9a98005f19ee4d21322 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.02%) to 98.611% when pulling 4b624a26fbb24f512b5aa9a98005f19ee4d21322 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage decreased (-0.02%) to 98.611% when pulling 4e14d73c2cc9d10fb475042078a70fa604d73292 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage increased (+0.05%) to 98.684% when pulling 9f4efe07c754d641f964a9a27f48c4fc99ae20ae on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage increased (+0.05%) to 98.684% when pulling cfe2281ee99ff34996532703951337de2c323f36 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage increased (+0.05%) to 98.684% when pulling cfe2281ee99ff34996532703951337de2c323f36 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage increased (+0.05%) to 98.684% when pulling cfe2281ee99ff34996532703951337de2c323f36 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Closes #21, #22 and #23

Coverage increased (+0.05%) to 98.684% when pulling cfe2281ee99ff34996532703951337de2c323f36 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage increased (+0.05%) to 98.684% when pulling cfe2281ee99ff34996532703951337de2c323f36 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.

Coverage increased (+0.05%) to 98.684% when pulling cfe2281ee99ff34996532703951337de2c323f36 on 1.0.0 into d32ab54f79044ab5ff03c544ce3ee6dc9353e4d5 on master.


Enable syntax highlighting for EditorConfig files

EditorConfig  files, named .editorconfig, are just dosini files.

I'll include it, thanks


Swap codecov targets around

Third time lucky?
This swaps the targets around, we want a minimal coverage of a diff/PR of 20% and for the project as a whole we are happy as long as it doesn't decrease (auto).

@betatim I think the lesser coverage is because https://github.com/jupyter/repo2docker/pull/475 was merged, making the... code smaller? Unclear, but feels like a bug in codecov.
Feel free to merge whenever :)


Tree overlay hides monster number

Affected Scenario(s): [59 and all scenarios with trees and (flyin creatures or players)]
Describe the bug
The number of the monster is hidden when it is flying over a tree overlay tile.
To Reproduce
Steps to reproduce the behavior:

Start scenario 59
Move an Imp (or any monster) onto a tree.
Note that the number of the monster is no longer visible.

Browser : Chrome
Scenario 59 used as an example

Should definitely fix this! I'll add it to the next release :-)


feat: neutron dao with interchain security

Task 1
Task 2
This PR implements a neutron's vision of governance. It uses admin module in bound with smart contract bindings, provided w this pr.
testing:

make init
from this pr ./test_proposal.sh

also i don't see parameter change proposals in the testing script, please add it

Tried it, script works.


added windows 11

after reading this article, i confirmed windows 11 is supported

Learn Build status updates of commit 6d4033d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows/security/threat-protection/security-policy-settings/create-permanent-shared-objects.md
:white_check_mark:Succeeded

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


find -cmin -amin -mmin

looks like this could easily be added to find, similar to ctime, atime, mtime, just changing the unit value to, what, 60?

On 12/09/2016 12:38 PM, brian-leidos wrote:

looks like this could easily be added to find, similar to ctime, atime,
mtime, just changing the unit value to, what, 60?

Easily, sure. Please tell me more about your use case?
Explanation: I don't always know where to draw the line on featuritis so
for non-posix extensions I tend to wait for an actual user to show up
and complain about it being missing. "Package $NAME's makefile broke
because it did find -cmin" is a strong argument for adding it. "I was
reading through the man page and wondering why you hadn't done this, but
I've never used it before myself either" not so much. And yes, that
second one's come up more than once, which is why I ask. :)
Sigh, I should probably add that to the FAQ.
Thanks,
Rob
P.S. The shell's $((42*60)) is an underappreciated posix feature. Not a
substitute for other things people actually use, I'm just saying it's nice.

My use case has to do with forensics. After I install or run an app, wanting to find what's changed in the file system. find -cmin/amin/mmin is supported in Linux, macOS, though I'm not sure about Posix. Obviously, I could put a file and use the -newer option, but as a forensic standpoint, I'd rather not be introducing new files like that. Make sense?

On 12/11/2016 06:29 PM, brian-leidos wrote:

My use case has to do with forensics. After I install or run an app,
wanting to find what's changed in the file system. find -cmin/amin/mmin
is supported in Linux, macOS, though I'm not sure about Posix.
Obviously, I could put a file and use the -newer option, but as a
forensic standpoint, I'd rather not be introducing new files like that.
Make sense?

I.E. "this is an option I personally use". Got it.
Huh, digging into it, -atime isn't seconds, it's days. There should
probably be -asec and friends too, but I'm reluctant to add new API out
of the blue. (And if I was going to do that I'd want to add a suffix to
-atime to specify seconds, minutes, or hours.)
Ok, how about this: I'll implement the existing -amin/cmin/mmin api but
not add it to the help text, and also implement an "-atime 3m" suffix
to specify units (years days hours minutes). Then document the second
one, but accept both syntaxes for compatibility, and have "-atime" vs
"-amin" change which default units to use.
Sound reasonable?
Rob

Hey Rob. Yeah, that sounds like an even better implementation. Thanks!

these changes went in years ago (and don't seem to have caused any trouble), so close this bug?


Add tiny changes to model_training_walkthrough.ipynb

Tiny changes, barely noticeable.
P.S. Assuming allDifferentiableVariables will be deprecated later here, as it currently won't run without it in Google Colab after installing the latest Swift4TF version.

@8bitmp3: sorry for the late review! We're not able to commit this suggestion because the source branch reads unknown repository - perhaps it was deleted.
If you have time, could you please create a new PR applying the suggestion? We'll review that one more quickly.


Security hole - Can login, without a password using the reset password

Steps to reproduce. (I've only tested this on local dev environment)
Go to login
Type in a valid username
Click reset password
When you get to the reset password window, change the url to the base url eg. http://localhost:3000 on the addressbar and enter
You get to the Start Chatting initial page
Click Start Chatting button
You are logged in as the user which you tried to rest the password.
This happens because it logs you in for the password reset flow.

I realised that this is not an issue on a hosted environment, as the link code is too complex to guess


api/services: define the introspection API

After several requests for information about platform support,
configuration introspection and feature switches, we now have a solution
that should work in all these use cases. The Introspection API hooks
into the plugin subsystem registration process. During registration,
plugins declare several pieces of information, allowing clients to
discover the cababilities and support that a containerd instance
provides, including whether or not it loaded with an error.
To allow symmetrical error reporting, the google/rpc.Status protobuf
definitions have been brought in from the googleapis project.
Unfortunately, we had to generate these in place to match our protobuf
system.
Once we like this design, we can add an implementation to integrate it
directly with the plugin system.
Enjoy!
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

If you're curious about how this integrates with the plugin system, it might be helpful to read through https://github.com/containerd/containerd/blob/master/plugin/plugin.go#L51.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1597   +/-   ##
=======================================
  Coverage   46.29%   46.29%
=======================================
  Files          24       24
  Lines        3378     3378
=======================================
  Hits         1564     1564
  Misses       1456     1456
  Partials      358      358

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 28882fd...1c83fe7. Read the comment docs.

@AkihiroSuda Is this what you are looking for?

SGTM

LGTM


Update versions in "NuGet Update" docs

https://microsoft.github.io/react-native-windows/docs/next/nuget-update
Directs searching for specific 0.63 strings

Would be good to have these references generic so we don't have to manually update on each release.

Seems like we're mostly using 0.63 as an example, so this might be fine to leave as is. @dannyvv do you think we need to update the docs you wrote for 0.64? https://microsoft.github.io/react-native-windows/docs/next/nuget-update

Seems like we're mostly using 0.63 as an example, so this might be fine to leave as is. @dannyvv do you think we need to update the docs you wrote for 0.64? https://microsoft.github.io/react-native-windows/docs/next/nuget-update


Patch for /port/atomic_pointer.h

Sparcv9 AtomicPointer implementation

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 3 Oct 2012 at 8:56
Attachments:

atomic_pointer.h.patch

Patch modified: added "#undef ARCH_CPU_SPARCV9_FAMILY" at the end of the header

Original comment by<EMAIL_ADDRESS>on 9 Oct 2012 at 1:59
Attachments:

atomic_pointer.h.patch

Fixed in 1.6.0.

Original comment by<EMAIL_ADDRESS>on 12 Oct 2012 at 7:53

Changed state: Fixed


Add support for searching for songs instead of just providing links

I know that linking songs is tedious. I think that what people will want is to be able to request songs just by providing the name and artist or something, like enchanted taylor swift to get queued up. This is obviously significantly different from how the code works now, so would have to see how feasible it is.

Just posting evidence that it worked.


multiple warnings on installation. Won't edit API key or delete it after running [BUG]

C:\ai\flowise>npm install -g flowise
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '>=18.15.0 <19.0.0 || ^20' },
npm WARN EBADENGINE   current: { node: 'v21.7.1', npm: '10.5.0' }
npm WARN EBADENGINE }
npm WARN deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated<EMAIL_ADDRESS>Use your platform's native atob() and btoa() methods instead
npm WARN deprecated<EMAIL_ADDRESS>Use your platform's native DOMException instead
npm WARN deprecated<EMAIL_ADDRESS>Use mz or fs-extra^3.0 with Promise Support
npm WARN deprecated<EMAIL_ADDRESS>cross-spawn no longer requires a build toolchain, use it instead
npm WARN deprecated<EMAIL_ADDRESS>The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued.  Upgrade to @latest

these are the warnings, do you have the error stack trace/messages?

nope.. got rid of flowise. Too much hassle. Will just use langchain.


Wait for kueue to be available before install custom resources.

Fixes / Features

Wait for kueue to be available before install custom resources.

Testing / Documentation
Testing details.

[ y/n ] Tests pass
[ y/n ] Appropriate changes to documentation are included in the PR

cc @mwysokin

cc @IrvingMg

Anybody know why this error happens?

This repo does not allow for forks, that's why it is failing

This repo does not allow for forks, that's why it is failing. Please switch to local branch and than we will try to fix it.

I don't have permissions :(

Please give it a try now

Please give it a try now

Thanks!

Please let me know if you can work from local branch now

Please let me know if you can work from local branch now

Thank you! Now it works.

Due to switching to local branch.
https://github.com/AI-Hypercomputer/xpk/pull/235

Due to switching to local branch.
https://github.com/AI-Hypercomputer/xpk/pull/235


batch: Setting up benchmark for executors.

Help to understand the performance with our implementation.

[ ] HashJoinExecutor.
[ ] NestedLoopJoinExecutor.
[ ] SortMergeJoinExecutor.
[ ] HashAggExecutor.
[ ] LimitExecutor.
[ ] MergeSortExchangeExecutor.
[ ] OrderByExecutor.
[ ] ProjectionExecutor.
[ ] #3528
[ ] SortAggExecutor.
[ ] TopNExecutor.

This is much needed! I will try to help with some of them if that's ok :)

This is much needed! I will try to help with some of them if that's ok :)

Welcome to join! I'm setting up benchmark of FilterExecutor as an example, and feel free to pick up others.

What's the goal? What's the baseline?

What's the goal? What's the baseline?

The goal is to help understand the result of our later optimizations. Currently we don't have baseline, and the current implementation is baseline.

After #3827  We can generate random Datum, so we can enrich data types used in this benchmark? cc @wzzzzd


[Request] Configurable aspects for Nodes

Is it possible to have a value set in the config for the value 255 within https://github.com/KryptonCaptain/MagicBees/blob/1.7.10-krypt/src/main/java/magicbees/main/utils/compat/thaumcraft/NodeHelper.java#L113 to be able to be pulled from a setting within the MagicBees.cfg?
Non java dev example would be to replace while (aspectsBase.getAmount(aspectToAdd) > 255 && rollAttempts < 20);  with while (aspectsBase.getAmount(aspectToAdd) > ( maxAspects -1) && rollAttempts < 20);
maxAspects being defined in the config that is the maximum amount of aspects to be added to the node, default being 256 - keeping in line with the intended change done by MagicBees devs but allow for people to go back to super nodes (like https://i.imgur.com/7Ety75u.png )

Yeah, I can do that pretty easily

Aight, head on over to Releases

Thank you very much!


OpenAPI schema generation fails if the GeometryField is not in the model

This piece of code will cause the schema generation to fail if the GeometryField is not in the model, e.g. it is an annotation or a custom property.
I don't see any simple solution (without custom get_field), beside having multiple serializer fields: PointField, LineStringField, etc.)

@dhaval-mehta what do you think on this?


Add the file 'build/generated-resources/test' to .classpath only if is it exists

Context
When importing Gradle into Eclipse, adding a non existent file to the .classpath as a source makes the project unbuildable.
Contributor Checklist

[x ] Review Contribution Guidelines
[x ] Sign Gradle CLA
[x ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@donat could you take a look at this simple PR since you're more familiar with Eclipse?

I just hit this problem (reported by @zosrothko  here) and the changes in this pull request got rid of the errors about a missing build/generated-resources/test (a lot of subprojects are missing that folder). (I pulled these changes down and rebased them atop the latest in master)
For what it's worth, I'm running Eclipse Oxygen.1a (4.7.1a) with Groovy Compiler 2.4.13 on OpenJDK 1.8.0_151-1-redhat on Windows 10.
I do see some other errors, but I'll dig deeper first to make sure I haven't missed any step in setting all this up.

@zosrothko Thanks!


provide OS errors when unable to open a file

No comments, looks fine to me.

If in the future we could wait for pull requests to finishing building on TravisCI before merging, that'd be great. :heart:


Support multi-processing on tf.py_func

This would be a great feature to have. The tf.py_func op is very handy for certain custom operations, but when training on multiple GPUs it ends up becoming a bottleneck that slows everything down. One way to get around that is to allow tf.py_fun to run on a different process each time, and by doing so avoid the GIL bottleneck. This could be enabled only when stateful = False, to avoid unintended side effects.

I cann't agree more! I also try to use multi gpu in my project, but I failed because of py_func.

Unfortunately, multiprocessing's fork does not play nicely with tensorflow's threads (https://github.com/tensorflow/tensorflow/issues/5448) or threads in general (http://www.linuxprogrammingblog.com/threads-and-fork-think-twice-before-using-them)

py_func is definitely super useful for quick tests, but it is difficult to make it work well in multithreading contexts. A lot of the problem is due to Python's extremely limiting notion of threading. Nobody is actively working on this right now. @alextp may have more comments.

@sjperkins Thanks for the links. If I understand the discussion there correctly, in Python 3.4+ using multiprocessing.set_start_method('spawn')  gets around the fork issues. I don't know if there is a way to get the same effect on 2.7, but even if not, having it working on Python 3 is still a big win.

I believe you can write your own wrapper around py_func to do this, a forking_py_func decorator which calls the py_func decorator on a function wrapped by a safe fork.

@alextp Could you explain in more detail how to wrap a forking_py_func around py_func to do multiprocessing? Thanks

Actually on second thought the tensorflow runtime uses threads and it's
unlikely that liberal use of multiprocessing will work here.
On Tue, Aug 8, 2017 at 10:54 PM, yj8907<EMAIL_ADDRESS>wrote:

@alextp https://github.com/alextp Could you explain in more detail how
to wrap a forking_py_func around py_func to do multiprocessing? Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/10624#issuecomment-321159590,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAATxXud4ed051lwJN75WS6DspqSjozXks5sWUmXgaJpZM4N2R8f
.

--

Alex

@alextp Then if I write a new op kernel in C++ and register it, will it avoid the bottleneck problem of py_func in multi gpu? I have this same problem of py_func slowing down multi-gpu speed.

Yes
On Wed, Aug 9, 2017 at 12:30 PM, yj8907<EMAIL_ADDRESS>wrote:

@alextp https://github.com/alextp Then if I write a new op kernel in
C++ and register it, will it avoid the bottleneck problem of py_func in
multi gpu? I have this same problem of py_func slowing down multi-gpu speed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/10624#issuecomment-321357536,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAATxYgBjfWXnxFNvrtjgQMAVdUKOLTGks5sWgjYgaJpZM4N2R8f
.

--

Alex

This issue is automatically closed due to lack of activity. Please re-open if this is still an issue for you. Thanks!

will this still move forward? Or the py_function thing should be totally ignored when pursuing performance?

py_function is very hard to do performantly


GitHub is depreciating set-env & add-path commands

Hello,
I'm sure you're already aware of this via your own use, but apparently GitHub is depreciating set-env and add-path commands, which will now trigger warnings in builds.

Thanks for the heads-up -- I wasn't aware of this.

Fixed by #16

Wow this was not a trivial fix. Thanks :)

Yeah, took a bit of figuring out.

Would it be possible to tag a new version that contains the fixes for this issue? Otherwise users are enticed by the GitHub marketplace to use the newest version (v2.0 at the time of writing), which will soon stop working.

Yes, done, thanks.


Evm 185 stf smart contract env

Sounds good. I will get that done after the evm staticcal is done
On Fri, Jul 8, 2022, 2:33 PM i-Alex @.***> wrote:

@.**** commented on this pull request.
Good
Let's have a python test similar to the sc_evm_bootstrap.py, where we
will send a tx that deploys the smart contact using this tool, then invoke
methods of that smart contract
—
Reply to this email directly, view it on GitHub
https://github.com/HorizenOfficial/Sidechains-SDK/pull/447#pullrequestreview-1032848740,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVBYBB56CIPNN33TPIB3MYDVTAN2LANCNFSM53AO5B4Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

Once eth_call is fixed and works properly, I would like to automatically parse outputs of smart contract calls and things like that, so that the parsing and getting of outputs doesn't have to be done manually again. See the TODOs @i-Alex


chore: bdd-spring-1580760266 to 0.0.1

chore: Promote bdd-spring-1580760266 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


Change homepage emphasis...

to focus on the message given in the London ElasticSearch User Group presentation, specifically:
Logsearch is a distribution of the Elasticsearch ELK stack optimised for running on a cloud IaaS
that enables you to:

Quickly create a local ELK stack to experiment with
Deploy, upgrade and operate a production ELK stack in the cloud
An ELK development environment

Resolved by PR #16


Add perf testing github action

Adapted from ember-data's performance CI.
This will pass start working once https://github.com/hjdivad/ember-m3/pull/1156 is merged. In the meantime you can go to https://github.com/hjdivad/ember-m3/pull/1141 to see it in action

Ready for a rebase


chartjs-wrapper-3.1 - Color class does not implement serialisable

Currently using chart-js-wrapper version 3.1.0 in which the Color class does not implement serialisable
As a workaround, I extended the color class and implemented serialisable. The application runs fine in sequential manner.
But in browser, on clicking back button, wicket application throws an error requesting for Parent color class to implement serialisable.
Any suggestions for workaround? Or it would be great if you could release the latest version of the chart-js.wrapper with the changes. Any timeline specified?
Really appreciate if you could help in this
RgbColorSerial is my local class that extends serialisable
Error log:
java.lang.RuntimeException: Could not deserialize object from byte[]
at org.apache.wicket.serialize.java.JavaSerializer.deserialize(JavaSerializer.java:143)
Caused by: java.io.InvalidClassException: com.alcatel.ngna.optical.gui.network.statistics.charts.RgbColorSerial; no valid constructor

The snapshot is available at the following repo: https://oss.jfrog.org/artifactory/oss-snapshot-local. You should be able to use in your pom by addidng the following to the repositories block:
<repository>
      <id>snapshots-repo</id>
      <name>snapshots</name>
      <url>https://oss.jfrog.org/artifactory/oss-snapshot-local</url>
</repository>

Have a look at this page for an example: https://maven.apache.org/guides/mini/guide-multiple-repositories.html.
You can then just add the dependency like this:
<dependency>
  <groupId>de.adesso.wicked-charts</groupId>
  <artifactId>wicked-charts-wicket6</artifactId>
  <version>3.2.0-SNAPSHOT</version>
  <type>pom</type>
</dependency>

Hope this helps.

My bad for missing out on the repo, Thanks so much for pointing to the right one! This really helps 👍

Will import and check the same in my application and get back to you about the status!

@pvidhey9
I will close this issue if the problem has been resolved for you :)


[PartEditor] Provide search input to filter operators

Let's provide a search editbox to filter operators with name and opcode.

from #822

done


webgl : add framebuffer API

I also set wasm32-unknown-unknown as default web target so you just have to 'cargo web start'.
Also I'm displaying the opengl error type in check_gl_error.
This is merely a test pull request to see if you're accepting them or if you'd rather walk alone for now.
Things I'd like to work on :

better separation of the game and the engine, having the engine in a separate crate
better support of some specific opengl versions (for example some 3.x versions require a vertex array object)

Look good for me, but have you tested the WebGLFrameBuffer object in Firefox ?
Using stdweb js! macro to return some WebGL object (i don know which one, but at least some of it) will fail in Firefox. It is because there are a bug in Firefox to store a webgl object in a weakmap and the stdweb side using JS WeakMap to store an reference for gc.
On the other hand, my current demo did not use this api and i cannot test it for myself. And i could merge your code now and fixed it when it is being used. Ok ?

I haven't tested it already. I'm trying to use the engine from another crate but I'm not there yet as I've got an issue with the asset database (cannot poll Result twice in   unigame::engine::asset::asset_database::Resourceunigame::engine::render::shader::Shader::try_borrowunigame::engine::render::shader::Shader
at unigame\src\engine\asset\asset_database.rs:91)
As you said, this doesn't break unigame and might be fixed later, once I manage to test it from my own crate. I've made the change you requested.

asset_database.rs:91 ? Um... It should be failed to load some assets. Are you using the master branch now ?

Yes, I have a project with this Cargo.toml :
[dependencies]
unigame={ path="../unigame" }
futures = "0.1"
nalgebra   = "0.13"
nphysics3d = "0.7.2"
ncollide = "0.13.0"
webgl = {path="../unigame/webgl"}
uni-app = {path="../unigame/uni-app"}
uni-glsl = {path="../unigame/uni-glsl"}

[dependencies.lazy_static]
version = "1.0"
features = ["nightly"]

# Image related dependencies
[dependencies.image]
version = "*"
default-features = false
features = ["png_codec"]

[replace]
"rand:0.3.20" = { path = "../unigame/wasm-rand" }
"rustc-serialize:0.3.24" = { path = "../unigame/wasm-rustc-serialize" }

../unigame being a clone of the master branch (including this pull request)
Running in native mode results in this error :
     Running `target\release\viper.exe`
preprocessing phong_vs.glsl...
preprocessing phong_fs.glsl...
preprocessing ui_fs.glsl...
preprocessing ui_vs.fs...
preprocessing phong_vs.glsl...
preprocessing phong_fs.glsl...
preprocessing ui_fs.glsl...
preprocessing ui_vs.fs...
thread 'main' panicked at 'cannot poll Result twice', libcore\option.rs:917:5

but the web version runs fine (provided I copy the static/ directory to my crate)

thanks! so that was my static/ directory than was under src/ instead of at the crate root. It works now.

Free feel to post an issue if you have any other problem 👍


SW-5706 Implemented endpoint to return application boundary as a GeoJson

#2367  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tommylau523 and the rest of your teammates on  Graphite

Merge activity

Sep 5, 7:19 PM EDT: @tommylau523 merged this pull request with Graphite.


Clarify Support for PHP 8.3.x and 9.x?

The README at the root mentions this extension is for PHP7, but has managed to work for 8.0-8.2. However, it is incompatible with PHP 8.3 (atleast ds 1.4). Could the root readme clarify what the official support plans are for PHP > 7?
For reference, here's the issue with 8.3:
Unable to load dynamic library 'ds.so' (tried: /usr/lib/php/20230831/ds.so (/usr/lib/php/20230831/ds.so: undefined symbol: fast_add_function)

Mostly wondering if it's worth it trying to make Ds happen (i was super excited when it first came out) or just to migrate back to the built-in types since every version seems to require delaying updating PHP to get compatibility.

Used Alpinelinux build with 8.3 to run https://github.com/php-ds/benchmarks and no issues found

I'll clarify in my case I was on Debian and PHP came from https://packages.sury.org/php/ while I'm not sure where php-ds came from, but looking at the date code in my log, it seems older than the one here: https://packages.sury.org/php/pool/main/p/php-ds/ so maybe I'm pulling from the wrong repo.
In either case, I intentionally made this issue generic since it's not clear what the long term support strategy/plan is. It's been years and the repo still says "for PHP 7"

Thank you for bringing this to my attention, it's about time that the version information is not around PHP 7 anymore, as it was when this project started. I'll take a look at support for 8.3 also, shouldn't be much work.

@andypost alpine package has the patch for php 8.3 https://git.alpinelinux.org/aports/tree/community/php83-pecl-ds/fix-php83.patch

@rtheunissen required changes for PHP 8.3 already merged https://github.com/php-ds/ext-ds/pull/195 so only new release mentioning new support constraints would be good

Related https://github.com/php-ds/ext-ds/issues/196

I'll release a new version on PECL after fixing #200

Hope this helps, output from MacOS with PHP 8.3
pecl install ds
downloading ds-1.4.0.tgz ...
Starting to download ds-1.4.0.tgz (53,121 bytes)
.............done: 53,121 bytes
96 source files, building
running: phpize
Configuring for:
PHP Api Version:         20230831
Zend Module Api No:      20230831
Zend Extension Api No:   420230831
building in /private/tmp/pear/temp/pear-build-porterjiDr7us/ds-1.4.0
running: /private/tmp/pear/temp/ds/configure --with-php-config=/opt/homebrew/opt/php/bin/php-config
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for a sed that does not truncate output... /usr/bin/sed
checking for pkg-config... /opt/homebrew/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for cc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether cc accepts -g... yes
checking for cc option to enable C11 features... none needed
checking how to run the C preprocessor... cc -E
checking for icc... no
checking for suncc... no
checking for system library directory... lib
checking if compiler supports -Wl,-rpath,... yes
checking build system type... aarch64-apple-darwin22.6.0
checking host system type... aarch64-apple-darwin22.6.0
checking target system type... aarch64-apple-darwin22.6.0
checking for PHP prefix... /opt/homebrew/Cellar/php/8.3.0
checking for PHP includes... -I/opt/homebrew/Cellar/php/8.3.0/include/php -I/opt/homebrew/Cellar/php/8.3.0/include/php/main -I/opt/homebrew/Cellar/php/8.3.0/include/php/TSRM -I/opt/homebrew/Cellar/php/8.3.0/include/php/Zend -I/opt/homebrew/Cellar/php/8.3.0/include/php/ext -I/opt/homebrew/Cellar/php/8.3.0/include/php/ext/date/lib
checking for PHP extension directory... /opt/homebrew/Cellar/php/8.3.0/pecl/20230831
checking for PHP installed headers prefix... /opt/homebrew/Cellar/php/8.3.0/include/php
checking if debug is enabled... no
checking if zts is enabled... no
checking for gawk... no
checking for nawk... no
checking for awk... awk
checking if awk is broken... no
checking whether to enable ds support... yes, shared
checking for a sed that does not truncate output... /usr/bin/sed
checking for ld used by cc... /Library/Developer/CommandLineTools/usr/bin/ld
checking if the linker (/Library/Developer/CommandLineTools/usr/bin/ld) is GNU ld... no
checking for /Library/Developer/CommandLineTools/usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 786432
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking for dsymutil... dsymutil
checking for nmedit... nmedit
checking for -single_module linker flag... ld: warning: -single_module is obsolete
yes
checking for -exported_symbols_list linker flag... yes
checking if cc supports -fno-rtti -fno-exceptions... yes
checking for cc option to produce PIC... -fno-common
checking if cc PIC flag -fno-common works... yes
checking if cc static flag -static works... no
checking if cc supports -c -o file.o... yes
checking whether the cc linker (/Library/Developer/CommandLineTools/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin22.6.0 dyld
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no

creating libtool
appending configuration tag "CXX" to libtool
configure: patching config.h.in
configure: creating ./config.status
config.status: creating config.h
running: make
/bin/sh /private/tmp/pear/temp/pear-build-porterjiDr7us/ds-1.4.0/libtool --mode=compile cc -I. -I/private/tmp/pear/temp/ds -I/private/tmp/pear/temp/pear-build-porterjiDr7us/ds-1.4.0/include -I/private/tmp/pear/temp/pear-build-porterjiDr7us/ds-1.4.0/main -I/private/tmp/pear/temp/ds -I/opt/homebrew/Cellar/php/8.3.0/include/php -I/opt/homebrew/Cellar/php/8.3.0/include/php/main -I/opt/homebrew/Cellar/php/8.3.0/include/php/TSRM -I/opt/homebrew/Cellar/php/8.3.0/include/php/Zend -I/opt/homebrew/Cellar/php/8.3.0/include/php/ext -I/opt/homebrew/Cellar/php/8.3.0/include/php/ext/date/lib  -I/opt/homebrew/opt/libpq/include -I/opt/homebrew/opt/openssl@3/include -L/opt/homebrew/opt/openssl@3/lib -I/opt/homebrew/opt/pcre2/include -L/opt/homebrew/opt/pcre2/lib -I/opt/homebrew/opt/postgresql@14/include/postgresql@14 -L/opt/homebrew/opt/postgresql@14/lib/postgresql@14 -I/opt/homebrew/opt/libpq/include -I/opt/homebrew/opt/openssl@3/include -L/opt/homebrew/opt/openssl@3/lib -I/opt/homebrew/opt/pcre2/include -L/opt/homebrew/opt/
pcre2/lib -I/opt/homebrew/opt/postgresql@14/include/postgresql@14 -L/opt/homebrew/opt/postgresql@14/lib/postgresql@14 -DHAVE_CONFIG_H  -g -O2 -D_GNU_SOURCE    -DZEND_COMPILE_DL_EXT=1 -c /private/tmp/pear/temp/ds/src/common.c -o src/common.lo  -MMD -MF src/common.dep -MT src/common.lo
mkdir src/.libs
 cc -I. -I/private/tmp/pear/temp/ds -I/private/tmp/pear/temp/pear-build-porterjiDr7us/ds-1.4.0/include -I/private/tmp/pear/temp/pear-build-porterjiDr7us/ds-1.4.0/main -I/private/tmp/pear/temp/ds -I/opt/homebrew/Cellar/php/8.3.0/include/php -I/opt/homebrew/Cellar/php/8.3.0/include/php/main -I/opt/homebrew/Cellar/php/8.3.0/include/php/TSRM -I/opt/homebrew/Cellar/php/8.3.0/include/php/Zend -I/opt/homebrew/Cellar/php/8.3.0/include/php/ext -I/opt/homebrew/Cellar/php/8.3.0/include/php/ext/date/lib -I/opt/homebrew/opt/libpq/include -I/opt/homebrew/opt/openssl@3/include -L/opt/homebrew/opt/openssl@3/lib -I/opt/homebrew/opt/pcre2/include -L/opt/homebrew/opt/pcre2/lib -I/opt/homebrew/opt/postgresql@14/include/postgresql@14 -L/opt/homebrew/opt/postgresql@14/lib/postgresql@14 -I/opt/homebrew/opt/libpq/include -I/opt/homebrew/opt/openssl@3/include -L/opt/homebrew/opt/openssl@3/lib -I/opt/homebrew/opt/pcre2/include -L/opt/homebrew/opt/pcre2/lib -I/opt/homebrew/opt/postgresql@14/include/postgresql@14 -L/opt/homebrew/opt/po
stgresql@14/lib/postgresql@14 -DHAVE_CONFIG_H -g -O2 -D_GNU_SOURCE -DZEND_COMPILE_DL_EXT=1 -c /private/tmp/pear/temp/ds/src/common.c -MMD -MF src/common.dep -MT src/common.lo  -fno-common -DPIC -o src/.libs/common.o
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/openssl@3/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/pcre2/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/postgresql@14/lib/postgresql@14' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/openssl@3/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/pcre2/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/postgresql@14/lib/postgresql@14' [-Wunused-command-line-argument]
/bin/sh /private/tmp/pear/temp/pear-build-porterjiDr7us/ds-1.4.0/libtool --mode=compile cc -I. -I/private/tmp/pear/temp/ds -I/private/tmp/pear/temp/pear-build-porterjiDr7us/ds-1.4.0/include -I/private/tmp/pear/temp/pear-build-porterjiDr7us/ds-1.4.0/main -I/private/tmp/pear/temp/ds -I/opt/homebrew/Cellar/php/8.3.0/include/php -I/opt/homebrew/Cellar/php/8.3.0/include/php/main -I/opt/homebrew/Cellar/php/8.3.0/include/php/TSRM -I/opt/homebrew/Cellar/php/8.3.0/include/php/Zend -I/opt/homebrew/Cellar/php/8.3.0/include/php/ext -I/opt/homebrew/Cellar/php/8.3.0/include/php/ext/date/lib  -I/opt/homebrew/opt/libpq/include -I/opt/homebrew/opt/openssl@3/include -L/opt/homebrew/opt/openssl@3/lib -I/opt/homebrew/opt/pcre2/include -L/opt/homebrew/opt/pcre2/lib -I/opt/homebrew/opt/postgresql@14/include/postgresql@14 -L/opt/homebrew/opt/postgresql@14/lib/postgresql@14 -I/opt/homebrew/opt/libpq/include -I/opt/homebrew/opt/openssl@3/include -L/opt/homebrew/opt/openssl@3/lib -I/opt/homebrew/opt/pcre2/include -L/opt/homebrew/opt/
pcre2/lib -I/opt/homebrew/opt/postgresql@14/include/postgresql@14 -L/opt/homebrew/opt/postgresql@14/lib/postgresql@14 -DHAVE_CONFIG_H  -g -O2 -D_GNU_SOURCE    -DZEND_COMPILE_DL_EXT=1 -c /private/tmp/pear/temp/ds/src/ds/ds_vector.c -o src/ds/ds_vector.lo  -MMD -MF src/ds/ds_vector.dep -MT src/ds/ds_vector.lo
mkdir src/ds/.libs
 cc -I. -I/private/tmp/pear/temp/ds -I/private/tmp/pear/temp/pear-build-porterjiDr7us/ds-1.4.0/include -I/private/tmp/pear/temp/pear-build-porterjiDr7us/ds-1.4.0/main -I/private/tmp/pear/temp/ds -I/opt/homebrew/Cellar/php/8.3.0/include/php -I/opt/homebrew/Cellar/php/8.3.0/include/php/main -I/opt/homebrew/Cellar/php/8.3.0/include/php/TSRM -I/opt/homebrew/Cellar/php/8.3.0/include/php/Zend -I/opt/homebrew/Cellar/php/8.3.0/include/php/ext -I/opt/homebrew/Cellar/php/8.3.0/include/php/ext/date/lib -I/opt/homebrew/opt/libpq/include -I/opt/homebrew/opt/openssl@3/include -L/opt/homebrew/opt/openssl@3/lib -I/opt/homebrew/opt/pcre2/include -L/opt/homebrew/opt/pcre2/lib -I/opt/homebrew/opt/postgresql@14/include/postgresql@14 -L/opt/homebrew/opt/postgresql@14/lib/postgresql@14 -I/opt/homebrew/opt/libpq/include -I/opt/homebrew/opt/openssl@3/include -L/opt/homebrew/opt/openssl@3/lib -I/opt/homebrew/opt/pcre2/include -L/opt/homebrew/opt/pcre2/lib -I/opt/homebrew/opt/postgresql@14/include/postgresql@14 -L/opt/homebrew/opt/po
stgresql@14/lib/postgresql@14 -DHAVE_CONFIG_H -g -O2 -D_GNU_SOURCE -DZEND_COMPILE_DL_EXT=1 -c /private/tmp/pear/temp/ds/src/ds/ds_vector.c -MMD -MF src/ds/ds_vector.dep -MT src/ds/ds_vector.lo  -fno-common -DPIC -o src/ds/.libs/ds_vector.o
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/openssl@3/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/pcre2/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/postgresql@14/lib/postgresql@14' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/openssl@3/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/pcre2/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/opt/homebrew/opt/postgresql@14/lib/postgresql@14' [-Wunused-command-line-argument]
/private/tmp/pear/temp/ds/src/ds/ds_vector.c:707:9: error: call to undeclared function 'fast_add_function'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
        DS_ADD_TO_SUM(value, return_value);
        ^
/private/tmp/pear/temp/ds/src/ds/../common.h:90:9: note: expanded from macro 'DS_ADD_TO_SUM'
        fast_add_function(sum, sum, val);                               \
        ^
/private/tmp/pear/temp/ds/src/ds/ds_vector.c:707:9: error: call to undeclared function 'fast_add_function'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
/private/tmp/pear/temp/ds/src/ds/../common.h:95:9: note: expanded from macro 'DS_ADD_TO_SUM'
        fast_add_function(sum, sum, &_num);                             \
        ^
2 errors generated.
make: *** [src/ds/ds_vector.lo] Error 1
ERROR: `make' failed

Released on PECL as 1.5.0

@rtheunissen please create a tag for release commit, I'm packing the extension for Alpinelinux and it handy to use tag to download composer.json for release to run tests https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/57617

@andypost tagged as v1.5.0 — I'll keep tagging releases from now on.

Thank you a lot!


Use shipping information for Apple Pay

Description

Tested scenarios

Fixed issue:

Hi @ThermScissorpunch,
Thanks for the Pull Request! Looks good to me. We will validate with the team and merge your pull request.
Regards,
Rik
Adyen

Hi @ThermScissorpunch ,
Thank you for the contribution, we will release the changes in the next release :)
Best,
Attila
Adyen


provide structured error to detect duplicate names

In some cases, the user may want to detect duplicate names when decoding and fall back to trying again with the AllowDuplicateNames options. The stack pointers are relatively worthless when duplicate names are enabled, but at least you can succeed.
There is a TODO to clean up the errors, but just want to track my use case specifically.
This issue also means that I'm requesting that SyntacticError potentially have an Unwrap method.

Thanks. I requested the same thing during the design process and I believe it is agreed we need it.

#66 introduces jsontext.ErrDuplicateName, which will always be wrapped in a jsontext.SyntacticError, which itself has a JSON pointer to the exact error location.
The name of a duplicate JSON object member can be extracted as:
err := ...
var serr jsontext.SyntacticError
if errors.As(err, &serr) && serr.Err == jsontext.ErrDuplicateName {
    ptr := serr.JSONPointer // JSON pointer to duplicate name
    name := ptr.LastToken() // duplicate name itself
    ...
}

Closing as completed.


Add a Developer guide

A quite extensive markdown file explaining a bit how cairo native works and how to learn its code base.

Codecov Report

Merging #285 (3a6d206) into main (d0904fc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #285   +/-   ##
=======================================
  Coverage   67.84%   67.84%
=======================================
  Files         109      109
  Lines       20099    20099
=======================================
  Hits        13636    13636
  Misses       6463     6463

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


Allow using symbolic error names in YAML.

Fixes https://github.com/project-chip/connectedhomeip/issues/12318
Problem
Can't write error: CONSTRAINT_ERROR in YAML.
Change overview
Make it possible to do that.
Testing
Manual inspection of generated test code, plus tests pass.

Fast tracking, given this is updating tests to add better functionality.


When i call $model->addToIndex();

BadMethodCallException
Method Illuminate\Database\Eloquent\Collection::addToIndex does not exist.

Seems like you're calling addToIndex() on a Collection (of models, presumably) not on a single Model.

Seems like you're calling addToIndex() on a Collection (of models, presumably) not on a single Model.

I have same error, in the docs say its possible...
You can also index a collection of models:

    $books = Book::where('id', '<', 200)->get();
    $books->addToIndex();

Extend ElasticquentCollection or add "use ElasticquentCollectionTrait;" to your Eloquent models


error trying to connect: dns error

Issue description
When staking, this error may show in the error log:
Sun, 26 Dec 2021 02:14:07 GMT
ReqwestError: error sending request for url (<url>): error trying to connect: dns error: failed to lookup address information: nodename nor servname provided, or not known

There doesn't seem to be a reason for any DNS error (no outages at the DNS provider and we haven't changed any related DNS records lately) but looking up the error shows that this may be an issue in hyper or reqwest related to making many concurrent requests (and could potentially be specific to macOS).
Related issues:

https://github.com/instructure/canvas-data-loader/issues/3
https://github.com/denoland/deno/issues/8155

Firefly version
1.3.0
OS details
macOS 11.6.1
Can the issue be reliably reproduced?
Yes
Steps to reproduce the issue
Attempt a wallet operation that involves many API requests (for example, syncing the wallet or staking)
Expected behaviour
No errors
Actual behaviour
DNS errors
Errors
No response

@rajivshah3 - actually it might be any OS-related that has local DNS cache (Ubuntu Linux, macOS, etc.) wrongly (defaults) configured.
For example: my Arch Linux has a local resolver (cache) with defaults. With having Firefly running (in the background) and the laptop resumed from a hibernation, usually, for the next few seconds (until my PC gets the network up) resolver is caching NX domains for any request my computer did. With wrongly set Negative TTL cache you may have NXDOMAIN cached for a while.
In addition: if you are not using a local DNS resolver (cache), the same misconfiguration may have a home router, an ISP provider, etc.

Closing issue due to inactivity, please upgrade to the latest app version and reopen the issue if the problem persists 🌷


Replace Eigen vectors of strings with std::vectorstd::string

Submission Checklist

[x] Run unit tests: ./runTests.py src/test/unit
[X] Run cpplint: make cpplint
[X] Declare copyright holder and open-source license: see below

Summary
Fixes #2864 as described in the subject and the issue. As a bonus already mentioned in the issue, the  stan::mcmc::chains(const Eigen::Matrix<std::string, Dynamic, 1>& constructor can be removed.
How to Verify
Existing tests should pass.
Side Effects
The type of stan::io::stan_csv::header has changed, but this is not referenced directly by any of our interfaces.
Documentation
None.
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Marco Colombo
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Thanks for the review! I'll merge as soon as tests pass.

This has had 3 consecutive random failures in Travis due to some error in the apt-get phase, so totally unrelated to the changes in this PR. How can we get past this?

@serban-nicusor-toptal and @seantalts --- what's the right path forward for this?  See the previous comment about apt-get failures.

The underlying apt-get issues should have been solved in #2868. If you know how to restart tests without pushing a new commit, perhaps it will go through.

@mcol Travis job restarted, hope it will take the new configuration.

Thanks @serban-nicusor-toptal, it has now passed the tests. Github tells me I'm not authorized to merge this PR, so someone else will have to do it for me.

I'm not sure why you wouldn't be approved to merge.  You're on the maintainers list, which is what is giving us merge permission.

I can merge on stan-dev/math, but here the button was shaded and the interface mentioned not being authorized... it's no big deal for me, though, as long as there are kind souls out there to do the merges for me. :)

Looks like Stan may be using separate permissions, so I added you to the stan team, too.  Let me know if you still have problems merging going forward.


track wont play through

Acknowledgement

[X] I have read Getting-Started and FAQ

🐛 Describe the bug
the play cursor doesnt move at all when i hit play or press space. it acts like i didnt press the input at all, i can still drag the cursor around and do everything in the program

everything else in the program is normal but this
Explains how to reproduce the bug
1 - Install program
2 - Install voicebank (I used Momone Momo cute vb, doesnt have a .yaml file)
3 - Make a new part and put notes on it
4 - Press space (cursor wont move)
5 - Press play button on the regular menu (cursor wont move)
OS & Version
Windows 10
Logs
log20240705.txt
2024-07-05 14:28:51.844 -03:00 [INF] Logging initialized.
2024-07-05 14:28:52.719 -03:00 [INF] Microsoft Windows NT 10.0.19045.0
2024-07-05 14:28:52.809 -03:00 [INF] Microsoft Windows 10.0.19045 X64 X64
2024-07-05 14:28:52.810 -03:00 [INF] OpenUtau v<IP_ADDRESS> win10-x64
2024-07-05 14:28:52.810 -03:00 [INF] Data path = C:\New Folder\OpenUTAU
2024-07-05 14:28:52.810 -03:00 [INF] Cache path = C:\New Folder\OpenUTAU\Cache
2024-07-05 14:29:10.937 -03:00 [INF] Initializing application.
2024-07-05 14:29:13.463 -03:00 [INF] Initializing culture.
2024-07-05 14:29:14.167 -03:00 [INF] Initialized culture.
2024-07-05 14:29:14.199 -03:00 [INF] Initializing theme.
2024-07-05 14:29:14.424 -03:00 [INF] Initialized theme.
2024-07-05 14:29:14.425 -03:00 [INF] Initializing OpenUtau.
2024-07-05 14:29:14.519 -03:00 [INF] Searching singers.
2024-07-05 14:29:14.704 -03:00 [INF] Search all singers: 00:00:00.1022017
2024-07-05 14:29:15.456 -03:00 [INF] Search all plugins: 00:00:00.8555133
2024-07-05 14:29:15.519 -03:00 [INF] Search all legacy plugins: 00:00:00.0634730
2024-07-05 14:29:15.521 -03:00 [INF] Initialized OpenUtau.
2024-07-05 14:29:15.521 -03:00 [INF] Initializing audio.
2024-07-05 14:29:15.866 -03:00 [INF] ReleaseSourceTemp C:\New Folder\OpenUTAU\Cache
2024-07-05 14:29:17.048 -03:00 [INF] Initialized audio.
2024-07-05 14:29:17.048 -03:00 [INF] Initialized application.
2024-07-05 14:29:17.049 -03:00 [INF] Framework initialization completed.
2024-07-05 14:29:17.816 -03:00 [INF] Creating main window.
2024-07-05 14:29:19.181 -03:00 [INF] Initialized main window component.
2024-07-05 14:29:19.654 -03:00 [INF] Main window checking Update.
2024-07-05 14:29:19.664 -03:00 [INF] Created main window.
2024-07-05 14:29:20.515 -03:00 [INF] SchedulePreRender
2024-07-05 14:29:20.958 -03:00 [INF] Publish notification Load project
2024-07-05 14:29:27.246 -03:00 [INF] Checking update at: https://github.com/stakira/OpenUtau/releases/tag/build/0.1.327
2024-07-05 14:29:27.247 -03:00 [INF] Checking appcast: https://github.com/stakira/OpenUtau/releases/download/build/0.1.327/appcast.win-x64.xml
2024-07-05 14:29:31.581 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:29:35.766 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:29:36.934 -03:00 [INF] Checking update at: https://github.com/stakira/OpenUtau/releases/tag/build/0.1.327
2024-07-05 14:29:36.934 -03:00 [INF] Checking appcast: https://github.com/stakira/OpenUtau/releases/download/build/0.1.327/appcast.win-x64.xml
2024-07-05 14:29:40.403 -03:00 [INF] Skipping update 0.1.327
2024-07-05 14:29:41.987 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:30:29.970 -03:00 [INF] Searching singers.
2024-07-05 14:30:30.128 -03:00 [INF] Search all singers: 00:00:00.1572362
2024-07-05 14:30:30.129 -03:00 [INF] Publish notification Singers changed.
2024-07-05 14:30:35.034 -03:00 [INF] undoGroup started
2024-07-05 14:30:35.035 -03:00 [INF] ExecuteCmd Change singer
2024-07-05 14:30:35.361 -03:00 [INF] undoGroup ended
2024-07-05 14:30:35.361 -03:00 [INF] SchedulePreRender
2024-07-05 14:30:35.361 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:30:46.279 -03:00 [INF] undoGroup started
2024-07-05 14:30:46.353 -03:00 [INF] ExecuteCmd Change phonemizer
2024-07-05 14:30:46.354 -03:00 [INF] undoGroup ended
2024-07-05 14:30:46.354 -03:00 [INF] SchedulePreRender
2024-07-05 14:30:46.355 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:30:49.273 -03:00 [INF] undoGroup started
2024-07-05 14:30:49.273 -03:00 [INF] ExecuteCmd Change render setting
2024-07-05 14:30:49.274 -03:00 [INF] undoGroup ended
2024-07-05 14:30:49.274 -03:00 [INF] SchedulePreRender
2024-07-05 14:30:49.274 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:30:50.308 -03:00 [INF] undoGroup started
2024-07-05 14:30:50.308 -03:00 [INF] ExecuteCmd Add part
2024-07-05 14:30:50.595 -03:00 [INF] undoGroup ended
2024-07-05 14:30:50.596 -03:00 [INF] SchedulePreRender
2024-07-05 14:30:50.596 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:30:50.647 -03:00 [INF] undoGroup started
2024-07-05 14:30:50.688 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:30:50.691 -03:00 [INF] undoGroup ended
2024-07-05 14:30:50.692 -03:00 [INF] SchedulePreRender
2024-07-05 14:30:50.695 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:30:51.358 -03:00 [INF] undoGroup started
2024-07-05 14:30:51.628 -03:00 [INF] ExecuteCmd Move parts
2024-07-05 14:30:51.631 -03:00 [INF] ExecuteCmd Move parts
2024-07-05 14:30:51.632 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:30:51.632 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:30:51.657 -03:00 [INF] ExecuteCmd Move parts
2024-07-05 14:30:51.658 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:30:51.727 -03:00 [INF] ExecuteCmd Move parts
2024-07-05 14:30:51.729 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:30:52.073 -03:00 [INF] undoGroup ended
2024-07-05 14:30:52.073 -03:00 [INF] SchedulePreRender
2024-07-05 14:30:52.074 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:30:52.364 -03:00 [INF] undoGroup started
2024-07-05 14:30:52.527 -03:00 [INF] undoGroup ended
2024-07-05 14:30:52.527 -03:00 [INF] SchedulePreRender
2024-07-05 14:30:52.528 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:30:52.533 -03:00 [INF] undoGroup started
2024-07-05 14:30:52.643 -03:00 [INF] Publish notification Select expression dyn
2024-07-05 14:30:52.670 -03:00 [INF] Publish notification Select expression dyn
2024-07-05 14:30:52.671 -03:00 [INF] Publish notification Select expression pitd
2024-07-05 14:30:52.674 -03:00 [INF] Publish notification Select expression dyn
2024-07-05 14:30:52.675 -03:00 [INF] Publish notification Select expression clr
2024-07-05 14:30:52.676 -03:00 [INF] Publish notification Select expression dyn
2024-07-05 14:30:52.677 -03:00 [INF] Publish notification Select expression eng
2024-07-05 14:30:52.679 -03:00 [INF] Publish notification Select expression dyn
2024-07-05 14:30:52.680 -03:00 [INF] Publish notification Select expression vel
2024-07-05 14:30:53.233 -03:00 [INF] Publish notification Select expression dyn
2024-07-05 14:30:53.234 -03:00 [INF] Publish notification Select expression pitd
2024-07-05 14:30:53.235 -03:00 [INF] Publish notification Select expression clr
2024-07-05 14:30:53.236 -03:00 [INF] Publish notification Select expression eng
2024-07-05 14:30:53.236 -03:00 [INF] Publish notification Select expression vel
2024-07-05 14:30:53.238 -03:00 [INF] Publish notification Load part
2024-07-05 14:30:53.240 -03:00 [INF] undoGroup ended
2024-07-05 14:30:53.240 -03:00 [INF] SchedulePreRender
2024-07-05 14:30:53.241 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:30:53.644 -03:00 [INF] Created bitmap 925, 60
2024-07-05 14:30:57.484 -03:00 [INF] Created bitmap 1282, 60
2024-07-05 14:30:58.890 -03:00 [INF] undoGroup started
2024-07-05 14:30:59.418 -03:00 [INF] ExecuteCmd Add note
2024-07-05 14:31:00.268 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:00.269 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:00.269 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:00.271 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:00.454 -03:00 [INF] undoGroup ended
2024-07-05 14:31:00.455 -03:00 [INF] SchedulePreRender
2024-07-05 14:31:00.455 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:31:01.638 -03:00 [INF] undoGroup started
2024-07-05 14:31:01.639 -03:00 [INF] ExecuteCmd Add note
2024-07-05 14:31:01.710 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:01.712 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:01.713 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:01.714 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.001 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.001 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.003 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.059 -03:00 [INF] ExecuteCmd Move 1 notes
2024-07-05 14:31:02.060 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.060 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.062 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.063 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.066 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.070 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.071 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.072 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.083 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.083 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.085 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.096 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.097 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.098 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.103 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.104 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.104 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.110 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.110 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.111 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.124 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.124 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.125 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.138 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.138 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.139 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.144 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.144 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.146 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.159 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.159 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.160 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.193 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:31:02.194 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:31:02.195 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:31:02.662 -03:00 [INF] undoGroup ended
2024-07-05 14:31:02.662 -03:00 [INF] SchedulePreRender
2024-07-05 14:31:02.662 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:31:04.006 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:31:08.996 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:31:16.279 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:32:07.936 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:32:10.557 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:32:28.380 -03:00 [INF] undoGroup started
2024-07-05 14:32:28.380 -03:00 [INF] ExecuteCmd Add note
2024-07-05 14:32:28.444 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:32:28.444 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:32:28.446 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:32:28.447 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:32:28.629 -03:00 [INF] ExecuteCmd Move 1 notes
2024-07-05 14:32:28.630 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:32:28.650 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:32:28.650 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:32:28.651 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:32:28.710 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:32:28.710 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:32:28.711 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:32:29.324 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:32:29.324 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:32:29.326 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:32:29.364 -03:00 [INF] ExecuteCmd Move 1 notes
2024-07-05 14:32:29.364 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:32:29.364 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:32:29.365 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:32:29.365 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:32:29.427 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:32:29.428 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:32:29.429 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:32:29.778 -03:00 [INF] ExecuteCmd Change 1 notes duration
2024-07-05 14:32:29.779 -03:00 [INF] ExecuteCmd Change vibrato length
2024-07-05 14:32:29.780 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:32:29.915 -03:00 [INF] ExecuteCmd Move 1 notes
2024-07-05 14:32:29.916 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:32:30.393 -03:00 [INF] undoGroup ended
2024-07-05 14:32:30.393 -03:00 [INF] SchedulePreRender
2024-07-05 14:32:30.394 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:32:30.949 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:32:31.607 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:32:31.769 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:32:31.911 -03:00 [INF] StartPlayback at 00:00:00
2024-07-05 14:32:37.823 -03:00 [INF] StartPlayback at 00:00:00.5000000
2024-07-05 14:34:27.784 -03:00 [INF] StartPlayback at 00:00:00.5000000
2024-07-05 14:34:30.341 -03:00 [INF] StartPlayback at 00:00:00.1875000
2024-07-05 14:53:33.906 -03:00 [INF] undoGroup started
2024-07-05 14:53:34.342 -03:00 [INF] ExecuteCmd Move parts
2024-07-05 14:53:36.039 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:53:36.160 -03:00 [INF] ExecuteCmd Move parts
2024-07-05 14:53:36.163 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:53:36.164 -03:00 [INF] ExecuteCmd Move parts
2024-07-05 14:53:36.169 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:53:36.913 -03:00 [INF] ExecuteCmd Move parts
2024-07-05 14:53:36.939 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:53:36.947 -03:00 [INF] ExecuteCmd Move parts
2024-07-05 14:53:36.948 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:53:36.989 -03:00 [INF] ExecuteCmd Move parts
2024-07-05 14:53:36.990 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:53:37.216 -03:00 [INF] ExecuteCmd Move parts
2024-07-05 14:53:37.218 -03:00 [INF] Publish notification Phonemized
2024-07-05 14:53:38.774 -03:00 [INF] undoGroup ended
2024-07-05 14:53:38.774 -03:00 [INF] SchedulePreRender
2024-07-05 14:53:38.775 -03:00 [INF] Publish notification Pre-render notification.
2024-07-05 14:53:39.915 -03:00 [INF] StartPlayback at 00:00:00
when it says StartPlayback , the playback dont start
and i literally just installed openutau

Please provide a full screenshot of your piano roll window.
Also, does this happen on every voicebank of just this voicebank?

well found the issue myself i was just being stupid. lyrics werent in hiragana writing, i forgot to convert them
now i've found the option to convert lyrics and the thing works as normal
sorry for the incovenience


fzf-lua previews of md change order every time nvim is run

I just noticed this while building the logs feature. fzf-lua preview windows, e.g. when using SF md list, have the table key,value pairs in a different order every time nvim is run. I hadn't noticed that before, and can't really tell why it's happening. My best guess is that vim.json.decode is returning a table in a different order each time, but can't think why that would be the case.

interesting, I didn't even noticed this. In rare cases, I need to eyeball the lastModifiedDate or lastModifiedByName. I don't really know, probably you need to ask from fzf-lua?

I'm currently looking into it, which is how I ran into that other formatting issue. I'm trying to see where the table loses it's order

It looks like the issue is with lua's print command, which does not follow the table's "printed" order:

I'm going to see if there's some other way we can accomplish that. I've tried pushing vim.inspect into fzf-lua's contents table, but unfortunately it means the preview windows shows a full table, braces and all (though it does respect order)


Networks

Support having clusters with different networks.
Discussion needed
Note that this breaks the functionality for deleting the ingress & is a breaking change (the fw name changes so it doesn't match fw rules created by previous kubemci versions anymore).
I saw a lot of TODOs in the code regarding networks, so I figured you have thought about the same problems as I encountered. Namely that the naming is problematic: once you have more than a single fw rule, you can not know which firewall rules exist, so then deleting them becomes a much harder problem. I noticed that this is made even worse by the fact that kubernetes/ingress-gce lacks the method to list firewall rules.

Oops.. unintentional branch deletion.

We are hitting exactly this problem, that two clusters are unhealthy because of no firewall rules for different vpc's. How can we help to implement this branch?.

We actually used my fork already in production: it worked fine. Both multi-network and multi-mode (CONNECTION/UTILIZATION) support were needed in our case.

@hermanbanken Thanks for letting us know. We are undecided if we will change our network topology to a single VPC or we will try your branch. If we use your branch I will let you know if we hit any bugs.


[Key Vault] Final updates for releases

Description
This gets the final things in order to release KV packages tomorrow (3/25), with three main changes:

New, real recordings for azure-keyvault-administration tests on API version 7.3
Changelogs updated for the correct release date, and with the full set of relevant changes since the last stable release
test-resources.json and platform-matrix.json updated to deploy Managed HSMs in northcentralus, rather than the default location, in order to circumvent deployment issues that have been experienced in other regions this week

All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

/azp run python - keyvault - tests


plot_nodal_solution instant closes after first plot

Hello,
Got an issue when using the plot_nodal_solution function.
An interactive plot appears as expected.
If you close that window and run the function again.
The window pops up, instantly closes and prints information to the console.
Using PyCharm and python 3.6. Any ideas?
Thanks

What version of pyvista Are you using?

What version of pyvista Are you using?

Version 0.22.1

Try using an earlier version of pyvista, as I think that’s the issue you’re running into.  Let me know if any work out.

Still happens on version 0.21.4.
No issue when running:
plotter = pv.Plotter()
plotter.show()
or
pv.BackgroundPlotter()

Does it occur with any of the plotting functions?

Still having this issue with the other plotting functions?  For example:
result.plot()

Hello, yes, the issue still occurs.
Python 3.6, pyansys 0.39.2 and pyvista 0.22.2.
import pyansys
result = pyansys.read_binary(path_to_rst)
result.plot_nodal_solution(rnum)
same result with:
result.plot()
Briefly appears, the closes and prints a list of tuples.

Closing issue as looks like it is a PyVista problem


Linter doesn't show anything in umbrella application on windows 10

Hello!
I have installed credo linter for Elixir Phoenix umbrella app.
mix credo works fine in console.
But, unfortunately, in vscode linter doesn't show any messages.
Here is my vscode setup:
Version: 1.55.2 (system setup)
commit: 3c4e3df9e89829dce27b7b5c24508306b151f30d
Date: 2021-04-13T09:35:57.887Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.18363
.credo.exs file was generated by mix credo.gen.config command.
I have created some module in apps/ folder, like this:
http://prntscr.com/11iklcd
and see strange behavior in terminal:
http://prntscr.com/11ikhyy
No linting tips shown.
And in non-umbrella app everything works as expected:
http://prntscr.com/11ikrzc
I would appreciate any help to solve this question.
Thanks!

Hey @talismandev !
The strange warning message you see comes from the mix credo command.
I have not worked with umbrella projects before, therefore I do not exactly know where the issue comes from.
But where are the files .mix.exs (where credo is defined in the deps) and .credo.exs located? In the root directory where apps/ lives, or within?

But where are the files .mix.exs (where credo is defined in the deps) and .credo.exs located? In the root directory where apps/ lives, or within?

Both are defined in the root directory.
credo version:
{:credo, "<= 1.4.0", only: [:dev, :test], runtime: false}

Okay, and how did you open your project in VS Code? Did you open an app that lives inside the apps/ directory or did you open the root directory?

Okay, and how did you open your project in VS Code? Did you open an app that lives inside the apps/ directory or did you open the root directory?

I open the root directory to work with the whole project.

Hm, very strange.
Okay, I just published a new version (0.4.2) of this extension that improves error reporting. Maybe you could download it (the new version will probably be available in a few minutes), enable the extension's configuration option "elixir.credo.enableDebug": true, reload your VS Code Window and re-open your project and an elixir file, and show me the output channel of this extension? That'd be great!

Sure.
After 0.4.2 installation I see the following:
http://prntscr.com/11it76a

It looks like, vscode recognizes apostrophe at the end of the line as the part of the filename (and can't find file).

This should not have anything to do with it, but thanks for pointing it out! I'll remove these apostrophes in the logs in the future.

If I change slashes in filepath, like this:
mix credo d:/umb_project/apps/some_module/lib/some_module.ex

This is so weird 😄 Apparently elixir writes this warning to the stderr. Let me draft a new version and I'll get back to you in minute as soon as it's released.

This should not have anything to do with it, but thanks for pointing it out! I'll remove these apostrophes in the logs in the future.

this is my misunderstanding. Everything is fine with apostrophes. The link is working on another OS as expected.
There is a problem with slashes in filepath on windows.

This should not have anything to do with it, but thanks for pointing it out! I'll remove these apostrophes in the logs in the future.

this is my misunderstanding. Everything is fine with apostrophes. The link is working on another OS as expected.
There is a problem with slashes in filepath on windows.

This is so weird 😄 Apparently elixir writes this warning to the stderr. Let me draft a new version and I'll get back to you in minute as soon as it's released.

I have installed 0.4.3 and this is the debug output:

Elixir Linter (Credo) initiated successfully.

An error occurred: 'warning: parentheses are required when piping into a function call. For example:

foo 1 |> bar 2 |> baz 3

is ambiguous and should be written as
foo(1) |> bar(2) |> baz(3)

Ambiguous pipe found at:
nofilename:41
' - Error Object: null

Okay, this makes sense. The warning you see is a compiler warning by Elixir. I believe the file you want linted has such a problem of ambiguous pipes. But apparently this is written to the stderr even though it is no error.
That's why the linting process would be interrupted.
As of v0.4.4 which is available now, this should not happen anymore. Can you verify this after upgrading to 0.4.4?

You were right!
Probably one of the files in umbrella has such a problem with pipes.
After 0.4.4 installation the lint process fixed.
Thank you so much!

Great, thanks for your help during debugging! 😄


TT-5354 Handle flat

TT-5346 and TT-5314
can type reference and description
can't change publishing to flat
warn users before adding publishing titles.

Sara reviewed it


What are the statistics affected by alfred qc --bed?

Hi Tobias
I haven't dug closely into the source code for this, so apologies if this question is a bit lazy:
What are the metrics affects by using the optional --bed flag for alfred qc?
I suspect this affects things like target coverage calculated....but I'm not sure what else.
Given a standard WGS normal BAM at 40x, what would you expect the different to be between including the target BED or excluding it?
Thank you for the help

Hi,
The optional BED file of target regions will not affect the whole-genome statistics. For the Alfred web app you will get the same statistics in the "Summary stats" tab and in addition some summary statistics for the BED file like the fraction of reads in a BED target region.
For the GC content, you will still have the sample and reference GC distribution but in addition the GC distribution for the BED file.
Most importantly you will get 2 additional plots related to the input BED file:
(1) Target coverage distribution (Fraction of targets above a coverage level 1x, 2x, 3x, ....)
(2) The on-target rate (Fraction of reads on target at 0bp extension, 25bp extension, ...)
In short, a BED file makes sense for all targeted assays (whole-exome sequencing, Haloplex, PCR amplicon sequencing, ...)
Best, Tobias

Hi @tobiasrausch
Thank you much for the prompt reply.

For the GC content, you will still have the sample and reference GC distribution but in addition the GC distribution for the BED file.

Most importantly you will get 2 additional plots related to the input BED file:
(1) Target coverage distribution (Fraction of targets above a coverage level 1x, 2x, 3x, ....)
(2) The on-target rate (Fraction of reads on target at 0bp extension, 25bp extension, ...)

Ah, this does make a great deal of sense. Right, I see how this works now in the source code a bit better now as well.
Thank you for the help! I'm still not entirely sure how this relates to tools for targeted assays which require both target and baits intervals.

Hi @tobiasrausch
Thanks for the prompt reply.


WIP: check tests

checking test failures due to too many open files.

This change is

/test kubeflow-fairing-presubmit


Add description to ReadMe explaining custom scriptlets

Please provide description explaining what the custom scriptlets cover vs. what default uBO scriplets cover.
Thanks!

I feel it might be a laborious task for task for me to undertake. Sorry.

If I were to summarise, whatever scriptlets that are not present in uBO  what I think deserve to be added for my use.


Online / Incremental updates

I am very interested in this library. Congrats and thanks for making this available for others to experiment with.
Does the library include support for online updates?
E.g. Say we fit a regression GP to some data X_original and Y_original.  We later receive additional data points X_new and Y_new. Does one have to re-fit the entire model for all of [X_original + X_new] and [Y_original + Y_new]? Or does GPy have support for incremetal updates?

1: You can add in new data by the add_xy methods. The nature of GPs require you to fit the molehill, but as you are at a optimized state, you can just refit from there with optimize.
2: there is a stochastic variational implementation in svi_gp, which allows for online updates by approximation.

On 20 Dec 2016, at 23:00, Amelio Vazquez-Reina<EMAIL_ADDRESS>wrote:
I am very interested in this library. Congrats and thanks for making this available for others to experiment with.
Does the library include support for online updates?
E.g. Say we fit a regression GP to some data X_original and Y_original. We later receive additional data points X_new and Y_new. Does one have to re-fit the entire model for all of [X_original + X_new] and [Y_original + Y_new]? Or does GPy have support for incremetal updates?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks @mzwiessele  Re-1 what do you mean by "the nature of GPs require you to fit the molehill?".  Isn't this more a property of the fitting mechanism?
E.g. if the default fitting mechanism (using optimize) isn't fitting an actual posterior  (and it's instead just getting an MLE estimate instead), one can't just update the posterior in the usual Bayesian way.
Or are you referring to something else?

Hi. Just to follow up on this, is there a way to do a rank one Cholesky update to the GP kernel matrix? I think that's the typical way that additions to the training set are handled. I'm not seeing an add_xy method in the documentation so I thought I'd check here first.

It is in there, see m.set_xy(x,y) and more, just hit m.set_

On 6 Mar 2017, at 20:29, alexfeld<EMAIL_ADDRESS>wrote:
Hi. Just to follow up on this, is there a way to do a rank one Cholesky update to the GP kernel matrix? I think that's the typical way that additions to the training set are handled. I'm not seeing an add_xy method in the documentation so I thought I'd check here first.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Ah I see. It looks like this is computing a brand new kernel matrix and Cholesky decomposition every time the data is updated. Is that correct?

Indeed. In the utility function there is a rank one update for the EP implementation, if I am not mistaken. Maybe ExpectationPropagation is a good place to start for an implementation of this feature.

On 6 Mar 2017, at 22:09, alexfeld<EMAIL_ADDRESS>wrote:
Ah I see. It looks like this is computing a brand new kernel matrix and Cholesky decomposition every time the data is updated. Is that correct?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok, so please correct me if I'm wrong, but it appears that if you change the data (e.g. by adding a training point) the following things happen

the inference method is called which computes the new kernel matrix and it's Cholesky decomposition
a new Posterior object which contains the new Cholesky decomposition and kernel matrix for calculating the posterior values but nothing else

It seems to me that with this workflow, if you want to update X to add new training points then there are two options

save the value of X in the Inference object and then add a method called update_inference to compute the update to the posterior
modify the existing inference method to use the old posterior to compute an update if it exists

Since I'm not familiar with your paramz framework, do you think either of these would work or would a different method be better? I would add a method to the GP class called update_XY that appended new training points to the existing X and Y vectors/matrices.
The process for the rank 1 update to the Cholesky and kernel is as follows
Knew = [[K(X,X)        K(X, xnew)],
              [K(xnew,X)  K(xnew, xnew)]
u = solve(L,K(X,xnew))
v =
Lnew = [[L     0],
              [u.T v]]

The end result would be a function like util.linalg.pdinv except L is provided instead of A and each items would be computed using a rank one update. The other difference is the storage of the old Cholesky inside the Inference class instead of just through the Posterior. This could be accomplished most easily by adding an input the the inference method that takes in an optional Posterior instance and then parses that object for the required data.
What do you think?

I forgot to mention, this process would require that GP be able to differentiate between an update to X and a brand new specification of X.


x/time/rate: reservation's delay is longer than expected if the previous one is not ok

What version of Go are you using (go version)?

$ go version
go version go1.17 darwin/amd64

Does this issue reproduce with the latest release?
Yes, it reproduces with go1.18.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/cn/Library/Caches/go-build"
GOENV="/Users/cn/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/cn/Workspace/golang/pkg/mod"
GOOS="darwin"
GOPATH="/Users/cn/Workspace/golang"
GOPRIVATE=""
GOPROXY="https://goproxy.cn,direct"
GOROOT="/Users/cn/Workspace/gosdk/go1.17"
GOSUMDB="sum.golang.google.cn"
GOTMPDIR=""
GOTOOLDIR="/Users/cn/Workspace/gosdk/go1.17/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.17"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/9d/p9d0dmmj04zfrll8cm7rndsm0000gn/T/go-build2220765180=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

https://go.dev/play/p/vGnnjsqOcTp?v=goprev.
What did you expect to see?
I expect r.Delay() returns 200ms, just like https://go.dev/play/p/knb4-IPMUFd?v=goprev.
What did you see instead?
r.Delay() returns 300ms. Both of previous reservations are not ok, why the later reservation returns different delay.

/cc @bcmills @Sajmani

I think the correct value is 300ms.
See https://go.dev/play/p/X_jeZbv_mRy?v=goprev which removes the line lim.ReserveN(t0, 3) that causes the error.
Note that the burst is 2 so that at t1 before the request (lim.ReserveN(t1, 2).OK()), there are 2 tokens in the bucket (instead of 3).
Regarding the error caused by lim.ReserveN(t0, 3), I have sent a CL to fix it.