Route boost::current_exception to std::current_exception when available?

From https://github.com/boostorg/system/pull/18, suggested by @ned14:

Also, one might consider also rerouting  boost::current_exception()  to  std::current_exception() . The latter is surely always going to be equal or better to the Boost implementation.

It is unclear to me who the target audience for such rerouting would be.
If you use boost::throw_exception() to throw, then boost::current_exception() / boost::rethrow_exception() work as well as std::current_exception() / std::rethrow_exception(), but you must use the boost versions if you do need your code to work on old compilers; if you don't, you may (should?) use the std versions.
If you don't use boost::throw_exception() to throw, then you should always use the std::current_exception() / std::rethrow_exception(), since your code won't work correctly on old compilers anyway.
Secondly, there are other components in Boost, e.g. boost::function, which aren't "rerouted". If such rerouting is needed, it should probably be done uniformly for all such components, though I'm not sure if there are important subtle semantic differences (there probably are.)

This rerouting would only apply on C++ 11 or newer, and presumably only on compilers without borked std::current_exception().
I get the argument "why bother rerouting?". But there is also the argument "why not bother rerouting?". Unlike boost::function, as far as I am aware, there is zero known behavioural differences between std::current_exception/rethrow_exception and boost::current_exception/rethrow_exception. Plus, rerouting these keeps symmetry with the rerouting of Boost.System to its std equivalents.

My question wasn't so much "why", but who would benefit? I understand the motivation, and I'm not against it in principle, but I am worried about possibly breaking client code which currently works fine, and I think that it is important to understand who cares about this change.
The safe approach would be to provide a new configuration macro, e.g. BOOST_EXCEPTION_USE_STD_EXCEPTION_PTR (off by default), which would guarantee nothing will break. Would that work? This isn't just paranoia, recently I tried to remove the support for non-intrusive boost::exception_ptr, specific for MSVC, thinking that probably nobody uses it any more (since modern compilers have std::exception_ptr), but it turned out I was wrong, so that's back in.
(By the way, I am not aware of any differences between std::function and boost::function, when I changed the allocator support in boost::function to match that of boost::shared_ptr, I wrote a proposal which made it into the standard as well :). But possibly I'm missing something.)

Actually I've realized that there is another problem: the custom error info container in boost::exception is held by a boost::shared_ptr, and all copies of a boost::exception object share that state. Only when making a boost::exception_ptr, the copied exception object doesn't share that state with the source, but that copy is not created using the copy constructor. A copy created by std::current_exception would share that state, potentially with explosive consequences if the exception is transported to another thread.
While this design is not ideal and can probably be safely changed so boost::exception objects never share state, this would not be a trivial change.

This discussion stalled, was there a conclusion (for example, since it was not trivial, will we do it?)

I don't know if this can be fixed. I'll try to explain simpler:
A boost::exception object holds a map of data, through a custom intrusive refcounting smart pointer. Copying exception objects within a thread only changes the refcount.
But that map is not thread-safe, so when a boost::exception object is transported to another thread, we must create a copy of the map, which boost::current_exception knows and does, but std::current_exception would simply invoke the copy constructor, which won't copy the map.
Maybe it can be done with a move constructor, but this would require #ifdefing, since I don't think it's a good idea to break C++03 support.
I'll close this for now, if anyone has an idea for a workaround, feel free to reopen and continue the discussion.

I have a suggestion (that would solve my use case):

first have boost::current_exception() do its current work, and recover the exception_ptr
then, if this 'failed' (and we would get an exception_ptr pointing to an unknown_exception), reroute to std::current_exception() if supported

This would:
a) keep existing code using Boost.Exception facilities working correctly
b) make code not using Boost.Exception to throw, work correctly, as if std::current_exception was used
For reference, in my use case I need to

use boost::future (which uses boost::current_exception() to transport exceptions across threads)
but I cannot use Boost.Exception facilities to throw exceptions (third party code throwing)

Does this make sense?

Reroute to std::current_exception, how? std::exception_ptr and boost::exception_ptr are different types.

Hum... maybe wrap the std::exception_ptr in current_exception and unwrap it in rethrow_exception?
In boost::exception_detail::current_exception_impl() (around boost/exception/detail/exception_ptr.hpp:424 in boost 1.64)
catch(...)
{
   try {
        // wrap the std::exception_ptr in a clone-enabled Boost.Exception object
       return exception_ptr(shared_ptr<exception_detail::clone_base const>(
              boost::enable_current_exception(std::current_exception()).clone()));
    }
   catch(...) {
      return exception_detail::current_exception_unknown_exception();
   }
}

In boost::rethrow_exception():
   try {
        p.ptr_->rethrow();
    } catch (const std::exception_ptr& ep) {
            std::rethrow_exception(ep);
   }

This (pseudo)code is for exposition only. Also, for simplicity this code assumes std::current_exception is available. I could provide a PR if necessary, but I doubt I can get all the #ifdef-ing right!
PS: I took inspiration from https://stackoverflow.com/questions/22010388/converting-stdexception-ptr-to-boostexception-ptr/22881981

I'm testing the above locally and it looks like it works. Two caveats, though:

clone is private so we need a reference to the base class

exception_detail::clone_base const& base {
    boost::enable_current_exception(std::current_exception())};
return exception_ptr(shared_ptr<exception_detail::clone_base const>(base.clone()));

the catch(std::exception&) (that redirects to current_exception_unknown_std_exception()) above the catch all clause, is intercepting my user defined exception type (which inherits from std::exception) so I had to remove it for this to work. Not sure if that breaks anything, as the std::current_exception should transport that case correctly.

What do you think?

Oh I see, your idea is to use std::exception_ptr as a way to be able to clone any exception properly, but still returning a boost::exception_ptr. I had misunderstood, I thought you wanted to go the other way around, to be able to effectively make boost::exception_ptr be std::exception_ptr where available.
This is a great idea, thank you. Since you said you've tested, I'm assuming you can send a pull request?

I'm testing locally against Boost 1.64.0. I guess you'd like the PR against devel branch?
Also, do you know which Boost preprocessor macro can I use to detect support for std::exception_ptr?

There is no config macro in Boost to detect std::exception_ptr support. Probably just check for C++11 support (e.g. #if __cplusplus > 199711L) and assume std::exception_ptr is available.
You can send a diff with Boost 1.64.0 if that's easier. I'll review and commit manually. Thank you!

My main compiler is VS2015, so I'm afraid __cplusplus does not work for me: for some reason it's still defined to be 199711L.
I'm looking at Boost.Config and I can't find anything suitable.
Maybe I can just use BOOST_NO_CXX11_NOEXCEPT, and assume that if noexcept is supported, then std::current_exception is also supported?
Or maybe I should bring this up in the mailing list?

It can't hurt to talk on the mailing list. But it may be safe to assume exception_ptr is supported if __cplusplus is greater than 199711L.

I'm working to provide a PR over develop branch.
BTW, my boss gave me green light to do this task using company time, so I'll do this with my corporatey github account, just to clarify I'm not doing this in my own free time.

About the docs, should I update the html files under doc/ directly?
I thought there would be some other source from which the html files are generated...

The changes (code, tests and docs) are ready in my fork (https://github.com/dmenendez-gruposantander/exception).
However I have a dependency on Boost.Config PR boostorg/config#285 being merged to develop (for BOOST_NO_CXX11_HDR_EXCEPTION).
Which is stalled due to CI testing being borked right now :(
I'll create a PR as soon as #285 is merged to develop.

Yes, let's wait until the config change gets merged, and then I'll look at the PR. Thank you!

Now that the Boost.Config changes have been merged to develop (thanks @jzmaddock!) I've created PR #24 with my changes, so let the code review begin!
Unfortunately, some CI tests are unexpectedly failing, and I'm having a hard time deciphering the errors...
For some versions of gcc it seems confused about instantiating abstract class clone_base (which I'd say I'm not) and the clang tests I don't think are even related to my changes!
Any help with this is appreciated, as I am being optimistic and was hoping to get this merged in time for the 1.72 release.

The clang errors are because Travis switched to Xenial by default; dist: trusty needs to be added to .travis.yml as the old clang versions don't work on Xenial.

Hum... This is not something I should fix in my PR, is it?

Is there something I can do to help with this issue?
Not that I'm familiar with the CI setting, but if all it takes is "dist: trusty needs to be added to .travis.yml" then I could... create a PR for that?

Hi, I'm sorry to be nagging about this, but I don't see how I can get this PR merged...
Is the CI config already fixed?
How do I "retry" the PR?
I'd really like to get this merged for 1.72, please.

OK, I added dist: trusty in my PR and the clang problems are solved.
However I still have problem with old versions of gcc which get confused when I bind a exception_detail::clone_base const& to the temporary coming out of boost::enable_current_exception().
Somehow gcc thinks I want a copy!
Ideas?
I tried const auto& but the actual type returned from boost::enable_current_exception() has clone() as a private member function!

At last! All tests are green!
Could you review the proposed changes for this PR please?
PS: the gcc problem was due to initializing the reference with braces instead of using =
go figure! slaps face

Yes, I'll look at it. Thank you!

Done.


Make ComposedHookTypes associative

As pointed out in my last PR (https://github.com/collegevine/purescript-elmish-hooks/pull/13#discussion_r786936834), HookType wasn’t really a monoid, because ComposedHookTypes (and therefore bind) wasn’t associative. This, I think, fixes that.
Look, associativity

And it has the expected type

Error message
Here, the second hook is a different type in each of the conditionals. The squiggly line doesn’t show the right place, but I think this was always the case because of do notation.

Maybe also add a test for this, so it doesn't break later.

Just realized there is a drawback to this. Now if we have one custom hook that uses another custom hook, we can’t add the first hooks type to the second’s:
type UseFoo = UseState Int <> UseEffect Unit

useFoo :: Hook UseFoo Unit

-- Doesn’t work
useBar :: Hook (UseFoo <> UseEffect Unit) Unit

-- Works
useBar :: Hook (UseState Int <> UseEffect Unit <> UseEffect Unit) Unit

But you can do this:
useBar :: ComposedHookTypes UseFoo (UseEffect Unit) t => Hook t Unit

This is a bit inconvenient to use (in Haskell the operator <> itself could be a type family), but fortunately you only have to use it if you make new hooks.

But you can do this:

Oh nice!

Maybe also add a test for this, so it doesn't break later.

I was wondering about this. How do I add tests for compile-time guarantees? Should I just add a test that does some grouped binding? That way if it breaks the test will just fail to compile?

Yes, that's exactly what I meant for tests.
Technically you could also add a negative test, but that's harder: you can't have it be part of your test code, you have to keep it as a string, and then compile it and check that you get the right error. Do that if you're feeling adventurous, but I really only meant the positive test.


error in example?

I think there may be an error in one of the examples.
In the section,
Convert Scikit-learn pipelines
you have:
pipeline = make_pipeline(normalizer, linear_svc)
...
pipeline_onnx = convert_sklearn(linear_svc, name='NormalizerLinearSVC',
input_features=[('input', FloatTensorType([1, 3]))])
Shouldn't this be:
pipeline_onnx = convert_sklearn(pipeline, name='NormalizerLinearSVC',
input_features=[('input', FloatTensorType([1, 3]))])

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

ID: e6bf772d-9f06-0114-305a-058c6bea5786
Version Independent ID: 297ca67d-9d10-eb87-f26e-4d72eefe252f
Content: Convert ML models to ONNX with WinMLTools
Content Source: docs/convert-model-winmltools.md
Product: machine-learning
GitHub Login: @wschin
Microsoft Alias: wechi

This repo has changed significantly since this issue was first raised, and further changes are upcoming. As such, I'm going through and closing many of these stale issues which sat unassigned for a long while.


Add podAnnotations value for setting annotations on pods

Also, remove "annotationsPod" settings documented in README. They did
nothing.  The naming was inconsistent with other charts, so that is
changed as well.
What this PR does / why we need it: This allows us to add some annotations to the pods so that we can hook up a datadog integration (but it could allow any other pod annotation as well).

/assign @lachie83

/ok-to-test

/lgtm


How to debug SqlScript in VS 2015

I'm sorry, just simple question how to show or debug sql script that generated by serenity in VS 2015? :)
Thanks

You debug it in Chrome, not VS

Sorry, i though you are talking about javascript.
You can see it while debugging it in VS2015, or turn logging level to Debug in web.config settings and have log files under App_Data/log, or use Stackify Prefix, Glimpse, Mini profiler or similar tool.

Thanks Jaiq.


Add client pool and server rotation

Pull Request Test Coverage Report for Build 173

91 of 130 (70.0%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.2%) to 54.356%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

litecoin/wallet.go
0
1
0.0%

zcash/wallet.go
0
1
0.0%

bitcoin/wallet.go
0
2
0.0%

client/client.go
17
20
85.0%

client/mock.go
0
3
0.0%

client/pool.go
74
103
71.84%

Totals

Change from base Build 169:
1.2%

Covered Lines:
2296

Relevant Lines:
4224

💛  - Coveralls


[BugFix] PPO params

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (a115079) 89.96% compared to head (3c9d786) 83.92%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #59      +/-   ##
==========================================
- Coverage   89.96%   83.92%   -6.05%
==========================================
  Files          69       64       -5
  Lines        2731     2613     -118
==========================================
- Hits         2457     2193     -264
- Misses        274      420     +146

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


default to v4 package after v4 release

closing as not planned as we are separating to a different repo to handle product naming


Extract Views

Extracted Slider = added accent color
Button = added label;

Meets expectations. View the Google doc for comments.


Java:Compile-time error

I use Sniprun in neovim to run the Golang code normally, but when I try to run the Java code, I get a Compile-time error. And the program can be successfully executed when I use the java command. Where should I check the log and how to troubleshoot it?Thank you!
JDK version: 20.0.1

Hmm at first glance it's not broken  (also on jdk20.0.1)...

There should be a log in your cache directory (~/.cache on Linux and ~/library/Caches on MacOS usually) /sniprun/sniprun.log
You could also check the content of the java_original directory, where a 'Main.java' file is created each time you run a snippet. This file should be compilable with javac and the resulting executable is run with java
If you want me to help debug your issue, please send those files (review them first if you don't want to share information such as file names or usernames)


Card does not show

when i run this locally i dont see the card in the example

Pull master and try again

still having the issue attached is what i see

Did you find a solution? I'm dealing with the same issue.


Update index error message and add tests

Codecov Report

Merging #405 (79835b3) into master (b6611ba) will increase coverage by 3.67%.
The diff coverage is 94.73%.

@@             Coverage Diff              @@
##             master     #405      +/-   ##
============================================
+ Coverage     75.85%   79.52%   +3.67%
- Complexity     1019     1064      +45
============================================
  Files           136      136
  Lines          3205     3214       +9
  Branches        431      432       +1
============================================
+ Hits           2431     2556     +125
+ Misses          710      588     -122
- Partials         64       70       +6

Impacted Files
Coverage Δ

src/main/java/seedu/awe/MainApp.java
0.00% <0.00%> (ø)

...c/main/java/seedu/awe/commons/util/StringUtil.java
95.45% <100.00%> (+0.71%)
:arrow_up:

.../seedu/awe/logic/commands/FindExpensesCommand.java
100.00% <100.00%> (+11.76%)
:arrow_up:

.../seedu/awe/logic/commands/ListExpensesCommand.java
88.88% <100.00%> (+4.27%)
:arrow_up:

...u/awe/logic/parser/DeleteContactCommandParser.java
100.00% <100.00%> (ø)

...u/awe/logic/parser/DeleteExpenseCommandParser.java
100.00% <100.00%> (ø)

...java/seedu/awe/logic/parser/EditCommandParser.java
92.00% <100.00%> (+0.69%)
:arrow_up:

...du/awe/logic/parser/ListExpensesCommandParser.java
100.00% <100.00%> (+100.00%)
:arrow_up:

...c/main/java/seedu/awe/logic/parser/ParserUtil.java
96.73% <100.00%> (ø)

src/main/java/seedu/awe/model/tag/Tag.java
100.00% <0.00%> (ø)

... and 9 more

Continue to review full report at Codecov.

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


timed out waiting for VM to start

Describe the bug
startTimeout(cause: Optional(SwiftJSONRPC.InvocationError.applicationError(cause: SwiftJSONRPC.HTTPRequestExecutorError(reason: SwiftJSONRPC.HTTPRequestExecutorError.Reason.httpClientError(error: URLSessionError(cause: Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo={_kCFStreamErrorCodeKey=61, NSUnderlyingError=0x60000067df80 {Error Domain=kCFErrorDomainCFNetwork Code=-1004 "(null)" UserInfo={_NSURLErrorNWPathKey=satisfied (Path is satisfied), viable, interface: lo0, _kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask .<5319>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDataTask .<5319>"
), NSLocalizedDescription=Could not connect to the server., NSErrorFailingURLStringKey=http://<IP_ADDRESS>:42506/, NSErrorFailingURLKey=http://<IP_ADDRESS>:42506/, _kCFStreamErrorDomainKey=1})), request: SwiftJSONRPC.HTTPRequest(method: SwiftJSONRPC.HTTPMethod.post, url: http://<IP_ADDRESS>:42506, headers: ["Content-Type": "application/json"], body: Optional(45 bytes)), response: nil))))
To Reproduce
No response
Expected behavior
No response
Diagnostic report (required)
No response
Screenshots and additional context (optional)
No response

Please share a diagnostic report from Help -> Collect Diagnostics.

Please share a diagnostic report from Help -> Collect Diagnostics.

when i restart the mac  orb its work

Still, please share the diagnostics anyway. It contains info from the last run that will help debug this.

，请分享诊断结果。它包含上次运行的信息，有助于调试。

its done

Can you paste the output/link here?

您可以将输出/链接粘贴到此处吗？

OrbStack info:
Version: 0.17.1 (170100)
Commit: 542d71ebea7b190bb932c1cc60c5a0d6f2fc89e4 (v0.17.1)
System info:
macOS: 13.5.1 (22G90)
CPU: arm64, 10 cores
CPU model: Apple M2 Pro
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2023-09-08T07-26-33.359899Z.zip

OrbStack info:
Version: 0.17.1 (170100)
Commit: 542d71ebea7b190bb932c1cc60c5a0d6f2fc89e4 (v0.17.1)
System info:
macOS: 13.5.1 (22G90)
CPU: arm64, 10 cores
CPU model: Apple M1 Pro
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2023-09-08T08-42-55.526325Z.zip

Here has same problem.
startTimeout(cause: Optional(SwiftJSONRPC.InvocationError.applicationError(cause: SwiftJSONRPC.HTTPRequestExecutorError(reason: SwiftJSONRPC.HTTPRequestExecutorError.Reason.httpClientError(error: URLSessionError(cause: Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo={_kCFStreamErrorCodeKey=61, NSUnderlyingError=0x600003d62280 {Error Domain=kCFErrorDomainCFNetwork Code=-1004 "(null)" UserInfo={_NSURLErrorNWPathKey=satisfied (Path is satisfied), viable, interface: lo0, _kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <D5DC4FA3-6875-4D19-AB7E-235DEAFE2F2A>.<9439>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDataTask <D5DC4FA3-6875-4D19-AB7E-235DEAFE2F2A>.<9439>"
), NSLocalizedDescription=Could not connect to the server., NSErrorFailingURLStringKey=http://<IP_ADDRESS>:42506/, NSErrorFailingURLKey=http://<IP_ADDRESS>:42506/, _kCFStreamErrorDomainKey=1})), request: SwiftJSONRPC.HTTPRequest(method: SwiftJSONRPC.HTTPMethod.post, url: http://<IP_ADDRESS>:42506, headers: ["Content-Type": "application/json"], body: Optional(45 bytes)), response: nil))))

Check logs for more details.

This is because the OrbStack service got stuck on something the last time you tried to stop it. There's not enough info to tell why, but you can work around it by running orb stop -f.

i got same problem. App didn't respond then I forced it to stop, then ran it again and got an error
OrbStack info:
Version: 0.17.1 (170100)
Commit: 542d71ebea7b190bb932c1cc60c5a0d6f2fc89e4 (v0.17.1)
System info:
macOS: 13.4 (22F66)
CPU: arm64, 10 cores
CPU model: Apple M1 Pro
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2023-09-08T11-31-12.068383Z.zip

Can you all try to reproduce the issue on this build, then wait a few minutes and share a diagnostic report? Thanks!

Apple Silicon: https://cdn-updates.orbstack.dev/exp/OrbStack_v0.17.1-125-g22e41dbe8_16094_arm64.dmg
Intel: https://cdn-updates.orbstack.dev/exp/OrbStack_v0.17.1-125-g22e41dbe8_16094_amd64.dmg

I've reproduced the issue and no longer get any errors with that version

@khoirulamri Great, please share a debug report so I can see what's actually causing this and fix it better.

Fixed in v1.0.0.

i'm facing this issue and here is my bug report
OrbStack info:
Version: 1.5.1
Commit: 4cfac15e1080617c70eb163966e1cb2009dac1c2 (v1.5.1)
System info:
macOS: 14.4 (23E214)
CPU: arm64, 10 cores
CPU model: Apple M1 Pro
Model: MacBookPro18,3
Memory: 16 GiB
Diagnostic report failed: get presigned url: Post "https://api-license.orbstack.dev/api/v1/debug/diag_reports": context deadline exceeded (Client.Timeout exceeded while awaiting headers)


Unable to resolve type reference that is only in ErrorType

Is there an existing issue for this?

[X] I have searched the existing issues

Product
Hot Chocolate
Describe the bug
I tried to use mutation error configuration in HC 13.6 preview 31, but an error occured on fetching schema:
HotChocolate.SchemaException: For more details look at the `Errors` property.

      1. Unable to resolve type reference `Int32! (Output)`. (HotChocolate.Types.ErrorObjectType<CustomError>)

         at HotChocolate.Configuration.RegisteredType.GetType[T](TypeReference typeRef)
         at HotChocolate.Types.OutputFieldBase`1.OnCompleteField(ITypeCompletionContext context, ITypeSystemMember declaringMember, TDefinition definition)
         at HotChocolate.Types.ObjectField.OnCompleteField(ITypeCompletionContext context, ITypeSystemMember declaringMember, ObjectFieldDefinition definition)
         at HotChocolate.Types.FieldBase`1.CompleteField(ITypeCompletionContext context, ITypeSystemMember declaringMember)
         at HotChocolate.Internal.FieldInitHelper.CompleteFieldsInternal[TField](ITypeCompletionContext context, ITypeSystemMember declaringMember, TField[] fields)
         at HotChocolate.Internal.FieldInitHelper.CompleteFieldsInternal[TFieldDefinition,TField](ITypeCompletionContext context, ITypeSystemMember declaringMember, IEnumerable`1 fieldDefinitions, Func`3 fieldFactory, Int32 fieldCount)
         at HotChocolate.Internal.FieldInitHelper.CompleteFields[TFieldDefinition,TField](ITypeCompletionContext context, ITypeSystemMember declaringMember, IReadOnlyList`1 fieldDefs, Func`3 fieldFactory)
         at HotChocolate.Types.ObjectType.OnCompleteFields(ITypeCompletionContext context, ObjectTypeDefinition definition)
         at HotChocolate.Types.ObjectType.OnCompleteType(ITypeCompletionContext context, ObjectTypeDefinition definition)
         at HotChocolate.Types.TypeSystemObjectBase`1.CompleteType(ITypeCompletionContext context)
         at HotChocolate.Configuration.TypeInitializer.CompleteType(RegisteredType registeredType)
         at HotChocolate.Configuration.TypeInitializer.ProcessTypes(TypeDependencyFulfilled fulfilled, Func`2 action)
         at HotChocolate.Configuration.TypeInitializer.CompleteTypes()
         at HotChocolate.Configuration.TypeInitializer.Initialize()
         at HotChocolate.SchemaBuilder.Setup.InitializeTypes(SchemaBuilder builder, IDescriptorContext context, IReadOnlyList`1 types)
         at HotChocolate.SchemaBuilder.Setup.Create(SchemaBuilder builder, LazySchema lazySchema, IDescriptorContext context)
         at HotChocolate.SchemaBuilder.Create(IDescriptorContext context)
         at HotChocolate.SchemaBuilder.HotChocolate.ISchemaBuilder.Create(IDescriptorContext context)
         at HotChocolate.Execution.RequestExecutorResolver.CreateSchemaAsync(ConfigurationContext context, RequestExecutorSetup setup, RequestExecutorOptions executorOptions, IServiceProvider schemaServices, TypeModuleChangeMonitor typeModuleChangeMonitor, CancellationToken cancellationToken)
         at HotChocolate.Execution.RequestExecutorResolver.CreateSchemaServicesAsync(ConfigurationContext context, RequestExecutorSetup setup, CancellationToken cancellationToken)
         at HotChocolate.Execution.RequestExecutorResolver.GetRequestExecutorNoLockAsync(String schemaName, CancellationToken cancellationToken)
         at HotChocolate.Execution.RequestExecutorResolver.GetRequestExecutorAsync(String schemaName, CancellationToken cancellationToken)
         at HotChocolate.Execution.RequestExecutorProxy.GetRequestExecutorAsync(CancellationToken cancellationToken)
         at HotChocolate.Execution.RequestExecutorProxy.GetSchemaAsync(CancellationToken cancellationToken)
         at HotChocolate.AspNetCore.HttpGetSchemaMiddleware.HandleRequestAsync(HttpContext context)
         at HotChocolate.AspNetCore.HttpGetSchemaMiddleware.InvokeAsync(HttpContext context)
         at HotChocolate.AspNetCore.HttpGetMiddleware.InvokeAsync(HttpContext context)
         at HotChocolate.AspNetCore.HttpMultipartMiddleware.InvokeAsync(HttpContext context)
         at HotChocolate.AspNetCore.HttpPostMiddlewareBase.InvokeAsync(HttpContext context)
         at Microsoft.AspNetCore.Builder.EndpointRouteBuilderExtensions.<>c__DisplayClass19_0.<<UseCancellation>b__1>d.MoveNext()
      --- End of stack trace from previous location ---
         at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
         at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)

Steps to reproduce
using HotChocolate;
using HotChocolate.Types;
using HotChocolate.Types.Descriptors;
using HotChocolate.Types.Descriptors.Definitions;

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddGraphQLServer()
    .AddMutationConventions()
    .AddMutationErrorConfiguration<CustomErrorConfig>()
    .AddQueryType<Query>()
    .AddMutationType<Mutation>()
    ;

var app = builder.Build();

app.MapGraphQL();

app.Run();

class CustomErrorConfig : MutationErrorConfiguration
{
    public override void OnConfigure(IDescriptorContext context, ObjectFieldDefinition mutationField)
    {
        mutationField.AddErrorType(context, typeof(CustomError));
        mutationField.MiddlewareDefinitions.Add(new(next => async ctx => {
            try {
                await next(ctx);
            } catch (Exception ex) {
                ctx.Result = new MutationError(new CustomError(1, ex.Message));
            }
        }));
    }
}

public record CustomError(int ErrorCode, string Message);

public class Query {
    public Foo GetFoo() => new("Baz");
}

public class Mutation {
    public Foo AddFoo() {
        throw new Exception("foo");
    }
}

public record Foo(string Bar);

Relevant log output
No response
Additional Context?
When Foo is changed to include int field, the exception is gone:
public record Foo(string Bar, int Baz = 1);

Version
13.6.0-preview.31

Good Catch! I will do a fix tomorrow.

We will fix that in the next release ... towards the end of this year.

I have a similar issue to this, at least the error seems to be the same. If this is not the same issue, I can create a new issue.
Here's what I have:
Installed packages:

HotChocolate/13.7.0
HotChocolate.AspNetCore/13.7.0

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddGraphQLServer()
    .AddMutationConventions()
    .AddQueryType<Query>()
    .AddMutationType<Mutation>()
    ;

var app = builder.Build();

app.MapGraphQL();

app.Run();

public class Query {
    public Foo GetFoo() => new("Baz");
}

public class Mutation {

    [Error(typeof(CustomException))]
    public Foo AddFoo() {
        throw new CustomException();
    }
}

public record Foo(string Bar);

public class CustomException : Exception
{
    public ErrorDetail[] ErrorDetails { get; }

    public CustomException(params ErrorDetail[] errorDetails)
    {
        ErrorDetails = errorDetails;
    }
}

public class ErrorDetail
{
    public ErrorDetail(ErrorReason reason)
    {
        Reason = reason;
    }
    public ErrorReason Reason { get; }
}

public enum ErrorReason { A, B, C, }

When I run it and try to make a GraphQL request (query or mutation), I get the following error:
HotChocolate.SchemaException: For more details look at the `Errors` property.

1. Unable to resolve type reference `[ErrorDetail!]! (Output)`. (HotChocolate.Types.ExceptionObjectType<CustomException>)

   at HotChocolate.Configuration.RegisteredType.GetType[T](TypeReference typeRef)
   at HotChocolate.Types.OutputFieldBase`1.OnCompleteField(ITypeCompletionContext context, ITypeSystemMember declaringMember, TDefinition definition)
   at HotChocolate.Types.ObjectField.OnCompleteField(ITypeCompletionContext context, ITypeSystemMember declaringMember, ObjectFieldDefinition definition)
   at HotChocolate.Types.FieldBase`1.CompleteField(ITypeCompletionContext context, ITypeSystemMember declaringMember)
   at HotChocolate.Internal.FieldInitHelper.CompleteFieldsInternal[TField](ITypeCompletionContext context, ITypeSystemMember declaringMember, TField[] fields)
   at HotChocolate.Internal.FieldInitHelper.CompleteFieldsInternal[TFieldDefinition,TField](ITypeCompletionContext context, ITypeSystemMember declaringMember, IEnumerable`1 fieldDefinitions, Func`3 fieldFactory, Int32 fieldCount)
   at HotChocolate.Internal.FieldInitHelper.CompleteFields[TFieldDefinition,TField](ITypeCompletionContext context, ITypeSystemMember declaringMember, IReadOnlyList`1 fieldDefs, Func`3 fieldFactory)
   at HotChocolate.Types.ObjectType.OnCompleteFields(ITypeCompletionContext context, ObjectTypeDefinition definition)
   at HotChocolate.Types.ObjectType.OnCompleteType(ITypeCompletionContext context, ObjectTypeDefinition definition)
   at HotChocolate.Types.TypeSystemObjectBase`1.CompleteType(ITypeCompletionContext context)
   at HotChocolate.Configuration.TypeInitializer.CompleteType(RegisteredType registeredType)
   at HotChocolate.Configuration.TypeInitializer.<CompleteTypes>b__30_0(RegisteredType type)
   at HotChocolate.Configuration.TypeInitializer.ProcessTypes(TypeDependencyFulfilled fulfilled, Func`2 action)
   at HotChocolate.Configuration.TypeInitializer.CompleteTypes()
   at HotChocolate.Configuration.TypeInitializer.Initialize()
   at HotChocolate.SchemaBuilder.Setup.InitializeTypes(SchemaBuilder builder, IDescriptorContext context, IReadOnlyList`1 types)
   at HotChocolate.SchemaBuilder.Setup.Create(SchemaBuilder builder, LazySchema lazySchema, IDescriptorContext context)
   at HotChocolate.SchemaBuilder.Create(IDescriptorContext context)
   at HotChocolate.SchemaBuilder.HotChocolate.ISchemaBuilder.Create(IDescriptorContext context)
   at HotChocolate.Execution.RequestExecutorResolver.CreateSchemaAsync(ConfigurationContext context, RequestExecutorSetup setup, RequestExecutorOptions executorOptions, IServiceProvider schemaServices, TypeModuleChangeMonitor typeModuleChangeMonitor, CancellationToken cancellationToken)
   at HotChocolate.Execution.RequestExecutorResolver.CreateSchemaServicesAsync(ConfigurationContext context, RequestExecutorSetup setup, CancellationToken cancellationToken)
   at HotChocolate.Execution.RequestExecutorResolver.GetRequestExecutorNoLockAsync(String schemaName, CancellationToken cancellationToken)
   at HotChocolate.Execution.RequestExecutorResolver.GetRequestExecutorAsync(String schemaName, CancellationToken cancellationToken)
   at HotChocolate.Execution.RequestExecutorProxy.GetRequestExecutorAsync(CancellationToken cancellationToken)
   at HotChocolate.AspNetCore.HttpPostMiddlewareBase.HandleRequestAsync(HttpContext context)
   at HotChocolate.AspNetCore.HttpPostMiddlewareBase.InvokeAsync(HttpContext context)
   at Microsoft.AspNetCore.Builder.EndpointRouteBuilderExtensions.<>c__DisplayClass19_0.<<UseCancellation>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)

Am I mussing something during service registration or is this related to this issue? Or maybe even an unrelated issue?

@michaelstaib any updates on this bug? Has been resolved?

It's fixed in hc 14

It's fixed in hc 14

So for anyone stuck with this issue when migrating from v12 to v13, do you suggest to just wait until v14 is out and then directly update from v12 to v14?


MYRIAD-186 Clean up the build

Looks good, but will need to update the scripts/Dockerfiles in the docker directory as well (otherwise those will fail to build).

@DarinJ You mean re open this one?

@zjaffee no this one I merged. It was #59 in the merge commit for #57 I put closes #59.


Requirements vs. Suggestions

The project team should implement tools to support the community around an open source project, such as mailing lists, message forums, a version control, wiki, and tracking mechanisms, such as Kanban boards to track issues and bugs on the GitHub repository.

It’s typical for policies like this to use SHALL for requirements and SHOULD for suggestions, but it’s not clear if that’s what’s happening here. If it is, I would suggest explicitly referencing RFC 2119 (https://tools.ietf.org/html/rfc2119) and capitalizing the words to call them out, per that RFC.

As of v1.1, SHOULD is the correct term used here, as per RFC 2119 referenced above. Future versions will take this issue into consideration if we make any changes. Thank you for bringing this to our attention.


Update scribe, scribe-file to 3.6.10

Updates

com.outr:scribe
com.outr:scribe-file

from 3.5.5 to 3.6.10.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.outr" } ]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #430.


Update to PureScript v0.15.0

Description of the change
Backlinking to purescript/purescript#4244
Updates project to compile on v0.15.0 PureScript.

Checklist:

[x] Added the change to the changelog's "Unreleased" section with a reference to this PR (e.g. "- Made a change (#0000)")
[x] Linked any existing issues or proposals that this pull request should close
[ ] Updated or added relevant documentation
[ ] Added a test for the contribution (if applicable)

Can that be done as a separate PR? It'll mess up this diff otherwise.

Yes, absolutely.


What is this domain referring to ? and why to use it ?

The domain can be used so when a user vists the URL, you could choose to render a QR code on that page with the invitation (as long as you own the domain of course). If you do not intend on using it, a sample domain can be used.
For the future, it might be nice to know that we have a Discord (https://discord.com/invite/yjvGPd5FCU) which is a better place for these questions.


PlaySound 'wrong', why does is pause the right sound?

The other two sounds seem really different from this last sound.
Why?

Because it overlaps. When wrong answer starts, correct sound should be muted.

But right and wrong sounds are never used for the same question right?
It's always waiting + wrong or waiting + right.


reformat registrations page to give info on each registration template

From the community repo: https://github.com/CenterForOpenScience/community/issues/264
Current Behavior
Users can select a registration template from a dropdown menu after clicking "new registration." To know what is included in a template, they must select it—there is no preview or information available ahead of time.
Suggested Behavior
Users should be provided with a brief description of each registration template (and perhaps have access to the questions ahead of time). The community team suggests that instead of using a dropdown menu to select an option, the user is presented with collapsable descriptions of each:

If the questions were to be provided ahead of time as well, PDFs could be linked to from those descriptions. The parenthetical text below could be muted text, shown not in parentheses.
Suggested content for each tab:
Open Ended: You will be asked to provide a narrative summary of what is contained in your project. There is no minimum character length. This template is not a valid submission for the Pre-registration Prize.
OSF Standard (pre-data collection): You will be asked if data collection is underway and if you have looked at your data already. You will be provided an opportunity to post other comments about your project. This template is not a valid submission for the Pre-registration Prize.
Brandt et al 2013 Replication Recipe (pre-data collection): This template is intended for use when conducting a replication. You will be asked a series of questions about the study you intend to replicate. This template is not a valid submission for the Pre-registration Prize.
Brandt et al 2013 Replication Recipe (post-data collection): This template is intended for use when conducting a replication. You will be asked a series of questions about your completed replication.  This template is not a valid submission for the Pre-registration Prize.
Pre-Registration Prize (pre-data collection):  You will be asked a series of questions to ensure that your sampling, design, and analysis plans are solidified prior to beginning your study. Publications that pre-register with this template may be eligible for a $1,000 prize. See project page for complete information.

I'm 100% onboard here. We will very likely implement this as part of the Prereg prize development

@samchrisinger -- OK I assign this to you, so we make sure it is covered? Thanks.

:+1:, got it

WIP, but

Sorry @jlcohoon , after seeing the pre or post data collection recommendation in this format, I think the wording (that I had approved!) is a bit misleading. Pre-reg prize can use preexisting data under certain circumstances and this format also makes it look like there is a separate post data-collection pre-reg prize template. Please revise as follows:
Open Ended Registration Form: You will be asked to provide a narrative summary of what is contained in your project. There is no minimum character length. This template is not a valid submission for the Pre-registration Prize.
OSF Standard Pre-Data Collection: You will be asked if data collection is underway and if you have looked at your data already. You will be provided an opportunity to post other comments about your project. This template is not a valid submission for the Pre-registration Prize.
Brandt et al 2013 Replication Recipe Pre-Data Collection: This template is intended for use when conducting a replication and should be used before collecting data. You will be asked a series of questions about the study you intend to replicate. This template is not a valid submission for the Pre-registration Prize.
Brandt et al 2013 Replication Recipe Post-Data Collection: This template is intended for use when conducting a replication and should be used after collecting data. You will be asked a series of questions about your completed replication. This template is not a valid submission for the Pre-registration Prize.
Pre-Registration Prize: You will be asked a series of questions to ensure that your sampling, design, and analysis plans are specified prior to beginning your study. Publications that pre-register with this template may be eligible for a $1,000 prize. This template can be used prior to data collection and, under certain circumstances, can be used with preexisting data. See project page for complete information.

@samchrisinger This mockup looks really good and brings the information right to the user earlier and in a clear way. Thanks for including the "Fulfills" category. We use "form" "schema" and "template" somewhat interchageably in a few different places. For consistency, let's refer to each of these as "templates." So please change the wording to "Please select a registration template to continue:"

That's fine by me. @samchrisinger, cancel my previous comments!


Code - OSS

Project description
Open source code editor developed by Microsoft for Windows, Linux and macOS. It includes support for debugging, embedded Git control, syntax highlighting, intelligent code completion, snippets, and code refactoring. It is also customizable, so users can change the editor's theme, keyboard shortcuts, and preferences.
This is not to be confused with the microsoft licensed vscode product which is already packaged.
Metadata

homepage URL: https://github.com/microsoft/vscode/
source URL: https://github.com/microsoft/vscode/
license: mit
platforms: unix, linux, darwin, windows

PR in https://github.com/NixOS/nixpkgs/pull/86122

Oops, wasn't aware of the PR in progress, thanks for mentionning it ;)


FileNotFoundError: [Errno 2] No such file or directory: 'face_module\work_space\save\model_ir_se50.pth'

where is the model file?

please download with this link. Then move to the path.Link


feat: implement list models in REST server

What does this PR do?
Add list models operation to the REST server
Let's make @cescoffier happy !
Screenshot / video of UI
N/A
What issues does this PR fix or reference?
#1296
How to test this PR?
Two ways:

curl localhost:10434/api/tags
OLLAMA_HOST=<IP_ADDRESS>:10434 ollama ls

\me happy :-) Thanks @jeffmaury


Wired Network connection Dont work

Hello,
When i connect all of the blocks / peripherals in the mod with networki cables and modems i dont recive a responce,
but when i connect the peripherals directly conected to a computer it works without errors.

The methods the i used:
local p = peripheral.wrap("openperipheral_sensor_0")
local players = {}
p = peripheral.wrap("openperipheral_sensor_0")
p.getplayers
p = peripheral.find("openperipheral_sensor")
p.getplayers
ps. test it with all peripheral it didnt work autocomplete and all peripheral

You're using the wrong name for the function. getPlayers() is the correct name. Capital P.
There is an openp directory with a documentation program in it. "openp/docs <side/peripheral-name>" to list the functions.
You can do stuff like:
openp/docs openperipheral_sensor_1
openp/docs openperipheral_sensor_1 getPlayers
Should list the docs for you.


MacOS 11.1

Hi,
Apologies if this has already been asked but I couldn't find anything on it.
Does Yabai have any issues running on MacOS 11.1? I have the update ready but have been putting off installing until I'm sure Yabai will work fine on it (including all SA features).

yabai is running perfectly on my machine.

16 inch MacBook Pro with macOS 11.1.
yabai: the latest master (installed with HEAD)

yabai is running perfectly on my machine.
* 16 inch MacBook Pro with macOS 11.1.

* yabai: the latest master (installed with `HEAD`)

Happy to hear it. I don't currently have Yabai installed from HEAD though, so I might look into that if this thread doesn't get any other replies from people running release versions. I'll likely update and see how I go, and fall back to HEAD if need be. When I update I'll report back here with my experience.

The released version worked well on my machine as well. I updated yabai to the newest master from the released version (which is the second newest commit on the master actually) this morning.


Add locale param to login

The most important change is https://github.com/schibsted/account-sdk-browser/compare/add-locale-param-to-login?expand=1#diff-b8139375bef5ea9da4706270fef9c716R183 . I believe that it shouldn't have big influence since it will skip only empty string query params.

I think we should, but new payment flow is not exposed yet in sdk. We can add all of params when we will introduce new payment flow urls

Sure, just saying the links generated by payment.js go to the BFF, and so they will direct the user to a BFF login flow before jumping onto the payment part. Feels like "whenever new payment flows go live" can be controlled on the backend with (possibly) no JS SDK changes?
Anyway, feel free to merge this PR when/if you want to 👍


southparkstudios.com is broken

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
Croatia
Provide a description that is worded well enough to be understood
Downloading any episode from www.southparkstudios.com ends with error Sorry, this video is not found or no longer available due to date or rights restrictions. But it can be watch on the site.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
yt-dlp -vU https://www.southparkstudios.com/episodes/egyait/south-park-raising-the-bar-season-16-ep-9
[debug] Command-line config: ['-vU', 'https://www.southparkstudios.com/episodes/egyait/south-park-raising-the-bar-season-16-ep-9']
[debug] User config "/Users/username/.config/yt-dlp/config": ['-o', '~/Downloads/%(title)s - %(id)s.%(ext)s', '--extractor-args', 'youtube:player_client=web']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp [12b248ce6]
[debug] Python 3.12.3 (CPython arm64 64bit) - macOS-14.4.1-arm64-arm-64bit (OpenSSL 3.3.1 4 Jun 2024)
[debug] exe versions: ffmpeg 7.0.1 (setts), ffprobe 7.0.1
[debug] Optional libraries: Cryptodome-3.20.0, brotli-1.1.0, certifi-2024.06.02, mutagen-1.47.0, requests-2.32.2, sqlite3-3.46.0, urllib3-2.2.1, websockets-12.0
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1820 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp)
[southpark.cc.com] Extracting URL: https://www.southparkstudios.com/episodes/egyait/south-park-raising-the-bar-season-16-ep-9
[southpark.cc.com] south-park-raising-the-bar-season-16-ep-9: Downloading webpage
[southpark.cc.com] c541c989-b10c-4ef8-9dbc-66000eff7bcd: Downloading info
[southpark.cc.com] 4fc3f0ad-97e1-4714-a2a4-504cca017075: Extracting information
[southpark.cc.com] 4fc3f0ad-97e1-4714-a2a4-504cca017075: Downloading video urls
ERROR: [southpark.cc.com] egyait/south-park-raising-the-bar-season-16-ep-9: southpark.cc.com returned error: not_found -
      Sorry, this video is not found or no longer available due to date or rights restrictions.

  File "/opt/homebrew/Cellar/yt-dlp/HEAD-add96eb/libexec/lib/python3.12/site-packages/yt_dlp/extractor/common.py", line 733, in extract
    ie_result = self._real_extract(url)
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/yt-dlp/HEAD-add96eb/libexec/lib/python3.12/site-packages/yt_dlp/extractor/mtv.py", line 322, in _real_extract
    return self._get_videos_info(mgid, url=url)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/yt-dlp/HEAD-add96eb/libexec/lib/python3.12/site-packages/yt_dlp/extractor/mtv.py", line 226, in _get_videos_info
    return self._get_videos_info_from_url(info_url, video_id, use_hls)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/yt-dlp/HEAD-add96eb/libexec/lib/python3.12/site-packages/yt_dlp/extractor/mtv.py", line 238, in _get_videos_info_from_url
    info = self._get_video_info(item, use_hls)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/yt-dlp/HEAD-add96eb/libexec/lib/python3.12/site-packages/yt_dlp/extractor/mtv.py", line 149, in _get_video_info
    raise ExtractorError(message, expected=True)

Related: #2621 (and all of the other MTV services issues)


Fix config loading errors

Checklist
GitHub

[x] I've given this PR a concise, self-descriptive, and meaningful title
[x] I've linked relevant issues in the PR body
[x] I've applied the relevant labels to this PR
[x] I've assigned a reviewer

PR contents

[x] I've consulted ivadomed's internal developer documentation to ensure my contribution is in line with any relevant design decisions
[x] I've added relevant tests for my contribution
[x] I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description

throw more specific errors when config files are not found
Linked issues

resolves #943

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 9 (55.56%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 70.739%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ivadomed/config_manager.py
5
9
55.56%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
4308

Relevant Lines:
6090

💛  - Coveralls


Save Issues

I've found a bug with SpellPouch. Adding abilities to an existing group doesn't update DefGroups.json. You have to move the abilities within the group after adding a new ability for it to save.

Good catch. Will fix.


Headers encoding problem in Zend\Mail\Message

My mail client do not recognize mail format when I set mail Message charset to UTF-8.
Here what I got in mail headers

To: =?UTF-8?Q?=D0=A1=D1=82=D0=blahblah
Subject: =?UTF-8?Q?=D0=95=D1=81=D1=blahblah
From: =?UTF-8?Q?=D0=A0=D0=B0=D0=B4=blahblah
MIME-Version: 1.0
Content-Type: =?UTF-8?Q?text/html?=
Content-Transfer-Encoding: =?UTF-8?Q?8bit?=
Content-Disposition: =?UTF-8?Q?inline?=

According to RFC http://www.ietf.org/rfc/rfc2047.txt only specific mail headers can be encoded when charset is set to other than ASCII.

http://www.ietf.org/rfc/rfc2047.txt
....
These are the ONLY locations where an 'encoded-word' may appear.  In  particular:

An 'encoded-word' MUST NOT appear in any portion of an 'addr-spec'.
An 'encoded-word' MUST NOT appear within a 'quoted-string'.
An 'encoded-word' MUST NOT be used in a Received header field.
An 'encoded-word' MUST NOT be used in parameter of a MIME
Content-Type or Content-Disposition field, or in any structured
field body except within a 'comment' or 'phrase'.
....

Temporary solution can be
foreach(array('Subject', 'From', 'To') as $_h){
    $mail->getHeaders()->get($_h)->setEncoding('UTF-8');
}

$transport->send($mail);

This issue has been closed as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html


[SPARK-25150][SQL] Rewrite condition when deduplicate Join

What changes were proposed in this pull request?
ResolveReferences rule modifies (deduplicates) conflicting AttributeReferences in left and right side of a Join. It changes the right side to avoid conflicts but it forgot to change the references in the condition of the join. Solution is to rewrite the condition too.
Details:
With this PR, if any of the resolved attributes in a join condition refer to an attribute that is replaced during the deduplication (dedupRight()) then the join condition is modified to reflect the change.
The modification is done regardless whether the reference is on the left or the right side of the condition.
This PR has no effect on unresolved attributes. Those attributes are resolved later by different rules.
This PR helps in those cases where same origin dataframes (b, c) are joined to a different origin one (a):
val a = spark.range(1, 5)
val b = spark.range(10)
val c = b.filter($"id" % 2 === 0)
val r = a.join(b, a("id") === b("id"), "inner").join(c, a("id") === c("id"), "inner")

Here the result of a join b contains an id attribute coming from b. That attribute conflicts with the id attribute of c in the second join so c("id") is deduplicated to let's say X and the join condition a("id") === c("id") needs to be modified to a("id") === X to get correct results.
I believe it is also worth explaining some situations where this PR does't help (but also does no harm). In cases where same origin dataframes are joined to each other:
val b = spark.range(10)
val c = b.filter($"id" % 2 === 0)
val r = b.join(c, b("id") === c("id"), "inner")

In this latter case the deduplication is applied as both b and c have an id attribute (that actually refer to the same resolved attribute (have the same ExprId)). Deduplication results c("id") to be changed to let's say X. So in this case both b("id") and c("id") in the join condition are modified to X by the changes introduced in this PR. The reason why the result will be correct with this PR (and is correct without this PR) is that the current implementation of Spark contains a "hack" in Dataframe that fixes EqualTo and EqualNullSafe type of conditions with identical references on both sides. The hack rewrites these join conditions by re-resolving the attributes with the name of the attribute on both the left and right sides.
Please note that until a resolved attribute doesn't contain some kind of reference to it's dataframe not all  cases of join can be handled properly. Such an initiative can be found in https://github.com/apache/spark/pull/21449.
How was this patch tested?
Added unit test.
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

Test build #95625 has started for PR 22318 at commit 8e58345.

Test build #95625 has finished for PR 22318 at commit 8e58345.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95625/
Test FAILed.

Also added missing if attr.resolved which I think will fix the UT issues.

Test build #95632 has finished for PR 22318 at commit d6e316a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95632/
Test PASSed.

@mgaido91 , 2.2 also suffered from this.

Test build #95714 has started for PR 22318 at commit d56f33c.

Test build #95720 has started for PR 22318 at commit 809b8a8.

LGTM

Test build #95714 has finished for PR 22318 at commit d56f33c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class AttributeMap[+A](val baseMap: Map[ExprId, (Attribute, A)])

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95714/
Test FAILed.

retest this please

Test build #95723 has started for PR 22318 at commit 809b8a8.

Test build #95720 has finished for PR 22318 at commit 809b8a8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95720/
Test PASSed.

Test build #95723 has finished for PR 22318 at commit 809b8a8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95723/
Test PASSed.

Test build #95750 has started for PR 22318 at commit 938bd7f.

Test build #95750 has finished for PR 22318 at commit 938bd7f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95750/
Test FAILed.

retest this please

Test build #95757 has started for PR 22318 at commit 938bd7f.

Test build #95757 has finished for PR 22318 at commit 938bd7f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95757/
Test PASSed.

LGTM

How does this work? When we have duplicated attributes in the join condition, how can we know which attribute comes from which side?

Can you define the scope of this PR? In which case we should change the references in the join condition?

@cloud-fan , I added some explanation to the description in which cases this PR helps and also where it doesn't.

@cloud-fan,  does the new description defines the scope as you suggested? Is there anything I can add to this PR?

@cloud-fan could you please help me with this PR and take it one step forward?

For a query similar to the one in the PR description:
a.join(b, a("id") === b("id"), "inner").join(c, a("id") === b("id"), "inner"
It is interpreted as a cartesian products now. But after this change, it is as the same as the query:
a.join(b, a("id") === b("id"), "inner").join(c, a("id") === c("id"), "inner")

Thanks @viirya, your analysis is correct.
Unfortunately an attribute doesn't have a reference to its dataset so I don't think this scenario can be solved easily. I believe the good solution would be something like https://github.com/apache/spark/pull/21449
But I would argue that my PR still does make sense and an a("id") === b("id") condition in a join where c is joined is not expected, and actually very likely a typo.

Also please consider that currently (and also after this PR) using b and c from the description:
b.join(c, b("id") === b("id"), "inner")

is interpreted as
b.join(c, b("id") === c("id"), "inner")

so my PR just extends this feature to the case with subsequent joins.
@cloud-fan , @viirya what do you think?

@srowen, I saw your last comment on https://github.com/peter-toth/spark/tree/SPARK-25150. I submitted this PR to solve that ticket and I believe the description here explains what is the real issue there.
I would appreciate your thoughts on this PR, unfortunately it got stuck a bit lately. Thanks.

@srowen the change seems fine to me as I think this does improve the behavior of attributes deduplication (I think it was a bug not rewriting the join condition with the new references).
The point is that in order to have a really correct and expected behavior in all the conditions we need to keep a reference of the dataset an attribute is from. That is why I created #21449 and I know @cloud-fan mentioned he had a similar PR for the same reason. But that is another story. In general I think both this and something like #21449 is needed in order to handle properly all the cases.

Can one of the admins verify this patch?

@peter-toth we cannot fix the issue of the description without changing the existing behaviour?

@maropu, I don't think we can. Actually this is how we deal with simpler joins
Do you think changing the behaviour is unacceptable?

In the example @viirya described above (https://github.com/apache/spark/pull/22318#issuecomment-426317617), I think the interpretation is unclear to most users and I'm fairly concerned that it could be error-prone...

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/15742/
Test PASSed.


Inconsistent and invisible Unicode character handling in editor and inspector

Godot version
3.3.2.stable
System information
Windows 10, 2D
Issue description
Leaving everything as default, Godot gives 3 entirely different responses to the single Unicode Down Arrow ⬇ U+2B07 symbol.  (You can find a one on this page to copy and paste: https://unicode-table.com/en/2B07/ )

The symbol appears correctly in the text if you paste it into a string in the GDscript editor window

The symbol appears as a Diamond Question Mark � if you paste it into the Inspector Text window of a Label node.

The symbol is invisible in the 2D rendered image of the label with default font.

To make the Down Arrow work I loaded the Fira font into some of the labels, and then it is rendered.
By paging down the Fira list of symbols I found another interesting symbol, a little skull and crossbones: ☠  This is U+2620
https://www.1001fonts.com/fira-mono-font.html
(It would be great if Godot previewed a grid of all the glyphs available in a Font so I could easily see which ones existed out of all that could be there, but that's another feature request.)
Pasting one of these into the editor creates an invisible character that you can only tell is there because the cursor stalls when you use the cursor keys to advance across it.

This indicates that #871 was incompletely fixed.

Steps to reproduce
See minimal project and instructions above
Minimal reproduction project
unicode_tests.zip

The symbol appears correctly in the text if you paste it into a string in the GDscript editor window
The symbol appears as a Diamond Question Mark � if you paste it into the Inspector Text window of a Label node.
The symbol is invisible in the 2D rendered image of the label with default font.

Code editor use Hack font, editor UI (e.g. Inspector) use Noto font, default project font is bitmap font based on the Noto (latin-1 chars only).

This indicates that Godot editor accepts non-ascii chars but doesn't show them #871 was incompletely fixed.

In 3.x it's fixed only for dynamic fonts, bitmap fonts do not have a fallback symbol. In 4.0, a box with missing character hex code is drawn for all font.


Taginfo problems

Notwithstanding https://github.com/shortbread-tiles/shortbread-docs/issues/35 , https://taginfo.openstreetmap.org/projects/shortbread_tiles#tags doesn't seem correct - only 19 tags listed, some of which are clearly misspelt.
https://shortbread-tiles.org/taginfo.json (which is where I presume https://github.com/shortbread-tiles/shortbread-docs/blob/main/shortbread-website/static/taginfo.json goes) seems better, but there are still some misspellings (e.g. https://taginfo.openstreetmap.org/tags/aerialways=cable_car#overview ).  "jsonlint" is happy with the current repository version.
I'm happy to submit a PR fixing the obvious typos and nudging "data_updated" to a later date if that's the preferred way forward.

@SomeoneElseOSM PR would be great, thank you!


question: modifying the training set for intuitionistic propositional logic?

hi,  a question here:
if I remember correctly the paper mentions "other logics".
did you try changing the construction process to produce 'intuitionistic propositional logic' instead of classical logic?
Thanks
Valeria

No, we haven't tried that.
But I agree it would be interesting to do intuitionistic logic and see how
the results compare.
On Mon, Nov 2, 2020 at 6:23 PM Valeria de Paiva<EMAIL_ADDRESS>wrote:

hi, a question here:
if I remember correctly the paper mentions "other logics".
did you try changing the construction process to produce 'intuitionistic
propositional logic' instead of classical logic?
Thanks
Valeria
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deepmind/logical-entailment-dataset/issues/2, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHCZGKGYRGNJ76BTAHREDDSN32KTANCNFSM4THZVVBA
.

thanks for the prompt reply!


Fix 1.21 doc reference

The PR https://github.com/kubernetes-sigs/reference-docs/pull/207 to prepare the 1.21 API reference doc has been merged, so this PR updates the api-ref-generator git submodule with the latest version.
Then, make api-reference has been run again, to cleanup some files remaining from the previous API reference release (it seems the merge of https://github.com/kubernetes/website/pull/23294 failed to remove these files).

Build error is:
fatal: No url found for submodule path 'api-ref-generator/docsy-example/themes/docsy' in .gitmodules

I'm not very comfortable with git submodules. In https://github.com/kubernetes-sigs/reference-docs/pull/191, a submodule has been added to the reference-docs repository, which is a submodule of this repository, and the error seems related to this nested sub-module.

I'm not very comfortable with git submodules. In kubernetes-sigs/reference-docs#191, a submodule has been added to the reference-docs repository, which is a submodule of this repository, and the error seems related to this nested sub-module.

Possibly related, https://github.com/kubernetes-sigs/reference-docs/pull/227.

/lgtm

Thanks @feloy!
/approve


incomplete HTML if  VF is not enabled

If Virtual Fabric (FC) is not installed or activated, the module runs into an error and aborts, the html output is also incomplete!
output:
Dashboard incoming, please wait...
Collect data from Device 2, please wait
WARNING: Table Header can't be processed properly. Names on the list to merge were not found in Table Header.
WARNING: Table Header can't be processed properly. Names on the list to merge were not found in Table Header.
WARNING: Table Header can't be processed properly. Names on the list to merge were not found in Table Header.
WARNING: Table Header can't be processed properly. Names on the list to merge were not found in Table Header.
WARNING: Table Header can't be processed properly. Names on the list to merge were not found in Table Header.
WARNING: Table Header can't be processed properly. Names on the list to merge were not found in Table Header.
WARNING: Table Header can't be processed properly. Names on the list to merge were not found in Table Header.
WARNING: Table Header can't be processed properly. Names on the list to merge were not found in Table Header.
WARNING: Table Header can't be processed properly. Names on the list to merge were not found in Table Header.
WARNING: New-TableCondition - None of the column names exists disc_c3 in condition. Skipping.
WARNING: New-TableCondition - None of the column names exists disc_c3 in condition. Skipping.
WARNING: New-TableCondition - None of the column names exists link_fail in condition. Skipping.
WARNING: New-TableCondition - None of the column names exists link_fail in condition. Skipping.
WARNING: New-TableCondition - None of the column names exists loss_sig in condition. Skipping.
Dashboard incoming, please wait...

Test output:
san_fcs15:rglanz> firmwareshow && ipaddrshow && lscfg --show -n && switchshow && porterrshow && portbuffershow && zoneshow
Appl     Primary/Secondary Versions
------------------------------------------
FOS      v8.2.2b
         v8.2.2b

SWITCH
Ethernet IP Address: <IP_ADDRESS>
Ethernet Subnet mask: <IP_ADDRESS>
Gateway IP Address: <IP_ADDRESS>
DHCP: Off
lscfg: requires VF to be enabled.

add a Workaround in v0.0.2 if VF is not enabled


DB: fix how operation and collection names are recorded for complex queries (opt-in db.query.text on metrics, new db.query.synthetic recommended attribute)

Fixes #1159, #805
Related: #521
Based on the discussion on slack https://cloud-native.slack.com/archives/C06HH05KNMC/p1728891505239829 and spec discussion on 10/25/24:

having a single operation/collection name on metrics is not enough
it provides a baseline that works for nosql and sql with simple queries
it can work better if/once we provide a way for users to supply their own operation alias/other context
it's misleading to record one operation/collection when in fact there are multiple

We can however:

allow users to enable capturing sanitized value of a db.query.text as opt-in to mitigate shortcomings of single operation/collection name.
create a synthetic query text from a combination of operations and collections (like SELECT foo, UPDATE bar, DELETE bar - it'd have low-ish cardinality, would be shorter than a query, won't have any sensitive information that needs sanitization and would be readable enough. This allows to make it recommended on metrics.

This PR implements both options as discussed in https://github.com/open-telemetry/semantic-conventions/issues/805#issuecomment-2414781903
Merge requirement checklist

[x] CONTRIBUTING.md guidelines followed.
[ ] Change log entry added, according to the guidelines in When to add a changelog entry.

If your PR does not need a change log, start the PR title with [chore]

[x ] schema-next.yaml updated with changes to existing conventions.

some possibilities for naming:

db.query.synthetic
db.query.short
db.query.summary
db.query.description

I really like the db.query.summary - it's accurate, it can be collected by other means (e.g. via a comment or a contextual attribute like in https://github.com/open-telemetry/oteps/pull/207). the db.query.synthetic would have limited opportunity to evolve into something more usable.


Changed the code to NOT store full tokens in the data store (memory)

This is good security practice since a breach of the DB will not lead to tokens being stolen
This is good security practice because admins of the DB do not have access to sensitive information
Reworked the unit tests to be more standard
Added removeAll to the different DB token types
Covered all the DB code now with tests

Bump the major version number since this is a potentially breaking change for people using it.


Generic/DisallowShortOpenTag: improve code coverage

Description
This PR improves code coverage for the Generic.PHP.DisallowShortOpenTag sniff.
Related issues/external references
Part of https://github.com/PHPCSStandards/PHP_CodeSniffer/issues/146
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

[ ] This change is only breaking for integrators, not for external standards or end-users.

[ ] Documentation improvement

PR checklist

[x] I have checked there is no other PR open for the same change.
[x] I have read the Contribution Guidelines.
[x] I grant the project the right to include and distribute the code under the BSD-3-Clause license (and I have the right to grant these rights).
[x] I have added tests to cover my changes.
[x] I have verified that the code complies with the projects coding standards.
[ ] [Required for new sniffs] I have added XML documentation for the sniff.

@jrfnl, while checking your suggestion for the snippet clipping test (https://github.com/PHPCSStandards/PHP_CodeSniffer/pull/638#discussion_r1815755817), I noticed that the test to ensure that close tags are recognized as such only if placed after the open tag needs to be the last test on the file as there should be no close tag after the open tag:
https://github.com/PHPCSStandards/PHP_CodeSniffer/blob/856fa777b91bf7e33ef8d7a035735fb7fc8abc79/src/Standards/Generic/Tests/PHP/DisallowShortOpenTagUnitTest.3.inc#L18-L19
I wonder if we should indicate that in the code comment above it or if this test should be moved to its own file?

I wonder if we should indicate that in the code comment above it or if this test should be moved to its own file?

Adding a code comment would be good. As it's not a parse error, I don't think this needs a separate test file.

Ok, I just added a comment documenting that the test must be the last one in the file.


Inconsistent formatting in destructuring nested structs

Here's how creation gets formatted:
Outer {
    ...
    inner: Inner {
        ...
    },
}

But here's what happens when you destructure in a method param:
fn foo(
    Outer {
        ...
        inner:
            Inner {
                ...
            },
    }: &Outer,
) {

Here's what it should look like to be consistent and not use excessive indentation:
fn foo(
    Outer {
        ...
        inner: Inner {
            ...
        },
    }: &Outer,
) {

Thanks for reaching out.
I think this may be related to #5117, possibly a duplicate as they both deal with struct literals vs struct patterns.

Ah yep, I think that's the same issue.


[WIP] WNet training

This PR implements WNet training directly in napari

[x] Local testing
[ ] Upload new WNet weights based on new best model
[ ] Coverage
[ ] Docs

Codecov Report

:exclamation: No coverage uploaded for pull request base (cy/training@1971d8d). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             cy/training      #47   +/-   ##
==============================================
  Coverage               ?   80.42%
==============================================
  Files                  ?       46
  Lines                  ?     5424
  Branches               ?        0
==============================================
  Hits                   ?     4362
  Misses                 ?     1062
  Partials               ?        0

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


Stopped working?

Stopped working this morning now asking for a beta code

Yes sorry about that, had a database issue so needed to do a reset. Let me know your email and I’ll send you another invite.
Sent via Superhuman iOS ( @.*** )
On Thu, Dec 21 2023 at 4:10 pm, Prof D < @.*** > wrote:

Stopped working this morning now asking for a beta code
—
Reply to this email directly, view it on GitHub (
https://github.com/hankhank10/loglink-server/issues/40 ) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AGCVMWPGN6MIJHFJONTATALYKRNQRAVCNFSM6AAAAABA6UADB6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TENZQGMYDCNA
).
You are receiving this because you are subscribed to this thread. Message
ID: <hankhank10/loglink-server/issues/40 @ github. com>

<EMAIL_ADDRESS>Cheers

Should be with you now @richd67 - let me know if it's working

Cheers all working again


(maint) Use a network instead of --link in the container tests

Test PASSed

CLA signed by all contributors.

Test PASSed

Retriggered Travis container tests, and they've passed.


KeyEventManager throws _CastError: Null check operator used on a null value on Flutter Web

Seen in production Flutter Web logs. Unsure of cause or how to reproduce.
_CastError: Null check operator used on a null value
  File "hardware_keyboard.dart", line 902, in KeyEventManager._convertRawEventAndStore
  File "raw_keyboard.dart", line 695, in RawKeyboard.handleRawKeyEvent
  File "hardware_keyboard.dart", line 818, in KeyEventManager.handleRawKeyMessage
  File "platform_channel.dart", line 77, in BasicMessageChannel.setMessageHandler.<fn>
  File "platform_channel.dart", line 76, in BasicMessageChannel.setMessageHandler.<fn>
  File "binding.dart", line 377, in _DefaultBinaryMessenger.setMessageHandler.<fn>
  File "binding.dart", line 374, in _DefaultBinaryMessenger.setMessageHandler.<fn>
  File "hooks.dart", line 190, in _invoke2.<fn>
  File "zone.dart", line 1426, in _rootRun
  File "zone.dart", line 1328, in _CustomZone.run
  File "zone.dart", line 1236, in _CustomZone.runGuarded
  File "hooks.dart", line 189, in _invoke2
  File "channel_buffers.dart", line 42, in _ChannelCallbackRecord.invoke
  File "channel_buffers.dart", line 132, in _Channel.push
  File "channel_buffers.dart", line 329, in ChannelBuffers.push
  File "platform_dispatcher.dart", line 583, in PlatformDispatcher._dispatchPlatformMessage
  File "hooks.dart", line 89, in _dispatchPlatformMessage

Logs

Logs

[✓] Flutter (Channel stable, 2.10.4, on macOS 12.3 21E230 darwin-arm, locale en-US)
    • Flutter version 2.10.4 at /Users/james/Development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision c860cba910 (2 weeks ago), 2022-03-25 00:23:12 -0500
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/james/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)

[✓] VS Code (version 1.66.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.32.0

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 100.0.4896.75

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Same as https://github.com/flutter/flutter/issues/100773.


MuJoCo 3.1.4 modifies the MjModel.nbvh value which is not reported in changelogs

Thanks for maintaining MuJoCo.
The Gymnasium CI found that one of our environments (Pusher-v4 and Pusher-v5) nbvh has changed due to using the latest version of MuJoCo 3.1.4
https://github.com/Farama-Foundation/Gymnasium/actions/runs/8644901511/job/23700995661
Looking through the changelogs for 3.1.4 I don't see any mention of nbvh being modified, my guess is that this isn't a bug but I wished to report it in case it was and if possible an explanation of what the change is about in case this affects the environment's behaviour
cc: @Kallinteris-Andreas

Thanks for noticing!
This is almost certainly due to the optimization in c5aa22b177676928e5f1d7ffdcc2195657fe472c
Since it had no user facing consequences other than a speedup, it did not make it to the changelog.

Thanks @yuvaltassa for the explanation


Dev to main sync

Date: 28-12-23
Developer Name: @skv93-coder

Prs going to sync

https://github.com/Real-Dev-Squad/website-dashboard/pull/659

Issue list

https://github.com/Real-Dev-Squad/website-backend/issues/1707

Documentation Updated?

[ ] Yes
[x] No

If your feature adds a new API, then documentation related to the feature like API-Contracts, and Data-models  must be updated.
Breaking Changes

[ ] Yes
[x] No

If your feature introduces breaking changes or if something is missing, please mention the related issue tickets.
Development Tested?

[x] Yes
[ ] No

Confirm whether the changes have been tested locally during development.
Tested in Staging?

[x] Yes
[ ] No

Indicate whether the changes have been tested in the staging environment.
Under Feature Flag

[x] Yes
[ ] No

Specify if the changes are currently under a feature flag.
Database Changes

[ ] Yes
[x] No

Indicate whether the changes include modifications to the database.
Screenshots
Staging proof
screen-capture (6).webm
Additional Notes
Include any additional notes, considerations, or explanations that might be helpful for reviewers.


BindableDouble throws exception when propagating precision

var number = new BindableDouble(1000);
var bindable = new Bindable<double>();

bindable.BindTo(number);

number.Precision = 0.5f;

In the above code, bindable does not support precision, so the line will crash. The same will likely happen with min/max values, that only BindableNumber (and by extension, BindableDouble) support.
Likewise, this is also going to be an issue with BindableInt and BindableLong.
I believe this is pretty unexpected behaviour, thoughts?

If there's a way to work around this then we should. If not, at very least it should probably not crash.


Custom weighting not working

Describe the bug
Asset allocation is equally weighted when no optimisation method is provided.
To Reproduce
Use the documented example for custom asset allocation.
portfolio = Engine(
      start_date = "2018-01-01",
      portfolio= ["BABA", "PDD", "KO", "AMD","^IXIC"],
      weights = [0.1, 0.3, 0.15, 0.25, 0.2], #custom weights
)

Expected behavior
portfolio.weights equals to [0.1, 0.3, 0.15, 0.25, 0.2]
Actual behavior
portfolio.weights equals to [0.2, 0.2, 0.2, 0.2, 0.2]

I believe this issue was introduced on this PR: https://github.com/ssantoshp/Empyrial/pull/35

Hi ✋
Thanks for reporting this issue. I just fixed it, it should be fine now. You can check it here: https://colab.research.google.com/drive/1dygKh3LsmBEtevSXLCG2h_8bvpSACbYt?usp=sharing

It's working perfectly, thanks!! 😄


'stromnetzgraz:energy_consumption:...' not present for second meter

After installing and configuring the Stromnetz device, I only see one 'stromnetzgraz:energy_consumption:..' sensor/entity and am unable to add the second meter to the energy dashboard.

Hi,
yes both methers have actual values and IME enabled.
Here is the web portal data for the meter that can be added:

Here the data for the meter that CAN'T be added:

home-assistant_stromnetzgraz_2024-03-02T07-42-18.512Z.log

Sorry, no Python knowledge here.
It seems, when starting up, the XXXX60 meter doesn't show any information. After the second fetch (6h), it shows data.

Just installed the 0.13 update and re-added the integration. This log file might be more relevant:
home-assistant_stromnetzgraz_2024-03-02T07-42-18.512Z.log

home-assistant_stromnetzgraz_2024-03-02T15-53-40.864Z.log
Sorry, here is the log file I intended to upload. I'll have the debug log run until tomorrow.

That might have been the case. I thought that it could help as well.
Here is the log file which ran since yesterday:
home-assistant_stromnetzgraz_2024-03-03T08-47-11.232Z.log
No entries for the other meter at all.

Hi @dreautall,
would there be anything to do from my side to make this work?
Perhaps contacting Stromnetz Graz about the issues?


Problem on console without support of color

Here on Win 7 x64 SP1 it shows errors:

Cheers.

(Tracking issue based off of https://github.com/Xithrius/twitch-tui/issues/629#issuecomment-2256077185)

(Tracking issue based off of https://github.com/Xithrius/twitch-tui/issues/629#issuecomment-2256077185)

https://github.com/Xithrius/twitch-tui/issues/629

#629

In the last issue that was tracking this you had a config with everything needed, but this error is saying that you're missing a section. Are you sure you placed it in the right path? Also, regardless of if NO_COLOR is enabled or not, I don't specify underlining in any of the styles besides ctrl + f highlighting, which isn't enabled by default. I'm not too sure what's causing this issue, and I don't really have a direct way of reproducing it either.

Nevermind I believe I've found the issue, but it's going to take a while to fix.

I believe I've fixed the problem in the release linked below. If not, feel free to re-open this issue.
https://github.com/Xithrius/twitch-tui/releases/tag/v2.6.16

Now it works ! Thank you very much, you're god !

No problem. Have a good one!


Issue-transitions for axis ticks

Automated Review Comments
Issues in src/components/Axis.js:

(2, 'Hardcoded string found')
Issues in src/components/AxisTick.js:
(13, 'Line exceeds 80 characters')
(14, 'Hardcoded string found')
(18, 'Hardcoded string found')
(19, 'Hardcoded string found')
(31, 'Line exceeds 80 characters')
(33, 'Line exceeds 80 characters')
(35, 'Hardcoded string found')
(36, 'Hardcoded string found')
(40, 'Hardcoded string found')
(41, 'Hardcoded string found')
(42, 'Hardcoded string found')
(43, 'Hardcoded string found')
(48, 'Hardcoded string found')
(50, 'Hardcoded string found')
(54, 'Hardcoded string found')
(59, 'Hardcoded string found')
Issues in src/components/Example.js:
(1, 'Line exceeds 80 characters')
(10, 'Line exceeds 80 characters')

I got it.


Big Number formatting(Slice with in Slice) and conditional formatting

Hi,
I have a scenario where i  want to add an image and two numbers in big number section  as shown in screenshot attached. I am not able to get how it can be achieved.
Also there is one more requirement to change the image conditionally on basis of number like if number is positive image(arrow) displayed should be in green if negative it should be in red (conditional formatting)
Can anyone please help me how to incorporate the same.
Thanks in advanced!!

I agree !
Having KPIs that cannot go from green to red (depending on the metric/% change) is not that useful.
Of course, it's useful to sum things up. However I think what decision-makers need (or even any user that monitors an app/ a business) is to quickly see if things go well or not.
Colors are the best way to quickly get it :

All the KPIs are green ? Things are OK
One of them is red ? I will check it

What's more, with colors, you cannot make a mistake by reading too fast.

Yes, I also agree!


Python executable from config file

Hi there!
I encountered the same issue as #517, also for a similar (the same?) use case.
I am running Dask Jobqueue on a SLURM system where all Python applications have to run inside (Apptainer) containers. Thus, I would like to be able to configure Dask jobqueue to use a containerized Python executable.
Currently, I can specify a custom Python path using the Dask Jobqueue Python API, but I cannot do it via the config file. It would be nice to allow for such feature, especially for users who use the Jupyter dask-lab extension, which relies uniquely on the values from the config files.
Introducing the changes as in this PR allows me to set the following in the Dask config file, so that all workers spawned by the cluster run inside containers:
jobqueue:
  slurm:
    python: 'apptainer exec oras://ghcr.io/fnattino/test-jupyterdask-image-apptainer:latest python'

Thanks! I think you need to reformat some files using black.

Thanks, merging!


Slaves not Opening trades when using 100% of balance

Using Stop Limit with 100% balance

Using buy Limit with 100% balance

what is 100% balance?

Hi Mohammed,
Its When the master account uses all of its funds to do a trade
Sent from my iPhone

On May 25, 2020, at 09:14, Mohamed Rashad<EMAIL_ADDRESS>wrote:

what is 100% balance?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Please pull the latest version, we fixed this bug.
Let me know if fixed.

I did a new pull yesterday,
I’ll try again later today
Thanks for the help!
Sent from my iPhone

On May 25, 2020, at 09:39, Mohamed Rashad<EMAIL_ADDRESS>wrote:

Please pull the latest version, we fixed this bug.
Let me know if fixed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I ran I new test, the issue still happening

I really found several bugs, one of them is that the system opens a order not from the entire available balance, but also from the blocked one (that is, which one is in orders). This will cause a "influenced of balance" error if you have other orders open.
     Also, an error can be detected by manipulations during the program's operation with the balance of those coins that are specified in config.csv in the first line.
     Now I am working on global refactoring and web sockets so I can fix these problems in the next pull-quest but it can take about a week

can you break them to smaller parts? like multiple pull requests so I can review and edit if needed?

Solved!


Possible segfault on GKE

Is there an existing issue for this?

[X] I have checked for existing issues https://github.com/getsentry/profiling-node/issues
[X] I have reviewed the documentation https://docs.sentry.io/
[X] I am using the latest SDK release https://github.com/getsentry/profiling-node/releases

How do you use Sentry?
Sentry Saas (sentry.io)
SDK Version
0.0.12
Link to Sentry event
No response
What environment is your node script running in?
GKE
How is your code deployed and bundled?
N/A
Steps to Reproduce
Deploy with GKE
Expected Result
Profiling works
Actual Result
Doesnt work

Managed to reproduce when deployed to google cloud run and running a load test. I applied a few patched in order while deploying the new version (building from source on node:18/alpine) and after https://github.com/getsentry/profiling-node/pull/89 the error stopped. Still needs to be confirmed by customers once we release the binaries


DCOS-13707: Safer alternative to parseInt for reducers

In some places in the reducers we are using plain parseInt when we are processing a value. This results in some unwanted NaN values being collected to the output.
This PR introduces the parseIntValue function that applies parseInt to the given value and it returns it's numerical representation only if it is indeed a number. Otherwise it passes through the value.
It allso replaces parseInt(value, 10) in all other places it was used

I have been thinking on implementing that one by myself 👍

LGTM! 💯  💖

mesosphere-ci retest this please 🙏

Works great! Nice job! 🏆 🏅


Fix #89 (Guarded task start() method running before guard)

Fix #89
Based on https://github.com/libgdx/gdx-ai/issues/89#issuecomment-273288584
Not fully tested.

Could you update CHANGES file?

Done


Use RPC tag for all artifact publishing and consuming

The implementation to discover the current release tag has been implemented in the RPC group_vars to replace the current module-based method. This mechanism is far simpler and does not rely on task execution to derive it.
In order to override the openstack_release variable to match the value of rpc_release, the rpc_release value must be available without requiring the use of a module and task. The values are therefore set in the user_*.yml override files.
Connected https://github.com/rcbops/u-suk-dev/issues/765

Your content preview is now ready. :bow:

:mag_right: Preview

:eyes: Preview

HULK PREVIEW

recheck_ceph
recheck_swift

squash and we are good to merge?

I don't believe it should be squashed, personally.

Oh no, indeed.