Crash in SNAP checkpointing

I'm seeing crashes in a modified version of SNAP running with my checkpointing wrapper.
Here's my configuration:

DEBUG=1
Bounds checks
Privilege checks
Legion Spy
Flags: -lg:safe_mapper -lg:safe_ctrlrepl -lg:inorder
No compiler warnings in any component of the system with -Wall -Werror

In short, all the checks I know how to turn on are turned on. The checkpointing wrapper also passes a pretty robust set of tests currently.
Here's a sample backtrace which fails with the error message:
malloc(): unsorted double linked list corrupted

Click to expand backtrace
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140114675243008) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=140114675243008) at ./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=140114675243008, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3  0x00007f6f24d78476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4  0x00007f6f24d5e7f3 in __GI_abort () at ./stdlib/abort.c:79
#5  0x00007f6f24dbf6f6 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f6f24f11b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#6  0x00007f6f24dd6d7c in malloc_printerr (str=str@entry=0x7f6f24f14c68 "malloc(): unsorted double linked list corrupted") at ./malloc/malloc.c:5664
#7  0x00007f6f24dda35c in _int_malloc (av=av@entry=0x7f6ef8000030, bytes=bytes@entry=472) at ./malloc/malloc.c:4010
#8  0x00007f6f24ddb1b9 in __GI___libc_malloc (bytes=472) at ./malloc/malloc.c:3329
#9  0x00007f6f251159cc in operator new(unsigned long) () from /lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007f6f2542a6ab in Realm::IndexSpace<3, long long>::copy (this=0x7f6efd7082b0, srcs=std::vector of length 1, capacity 1 = {...}, dsts=std::vector of length 1, capacity 1 = {...},
    indirects=std::vector of length 0, capacity 0, requests=..., wait_on=..., priority=0) at /resilience/legion/runtime/realm/transfer/transfer.cc:5226
#11 0x00007f6f27fcdf5e in Realm::IndexSpace<3, long long>::fill (this=0x7f6efd7082b0, dsts=std::vector of length 1, capacity 1 = {...}, requests=..., fill_value=0x7f6ef81287d0, fill_value_size=24,
    wait_on=..., priority=0) at /resilience/legion/runtime/realm/indexspace.inl:887
#12 0x00007f6f28b37d26 in Legion::Internal::IndexSpaceExpression::issue_fill_internal<3, long long> (this=0x7f6ef0013d70, forest=0x564a3c3a8090, op=0x7f6ef010ee80, space=..., trace_info=...,
    dst_fields=std::vector of length 1, capacity 1 = {...}, fill_value=0x7f6ef81287d0, fill_size=24, fill_uid=25, handle=..., tree_id=52, precondition=..., pred_guard=..., unique_event=..., priority=0,
    replay=false) at /resilience/legion/runtime/legion/region_tree.inl:145
#13 0x00007f6f28b1b771 in Legion::Internal::IndexSpaceNodeT<3, long long>::issue_fill (this=0x7f6ef0013a10, op=0x7f6ef010ee80, trace_info=..., dst_fields=std::vector of length 1, capacity 1 = {...},
    fill_value=0x7f6ef81287d0, fill_size=24, fill_uid=25, handle=..., tree_id=52, precondition=..., pred_guard=..., unique_event=..., priority=0, replay=false)
    at /resilience/legion/runtime/legion/region_tree.inl:5778
#14 0x00007f6f284a5992 in Legion::Internal::FillView::issue_fill (this=0x7f6ef803b070, op=0x7f6ef010ee80, fill_expr=0x7f6ef0013d70, trace_info=...,
    dst_fields=std::vector of length 1, capacity 1 = {...}, applied_events=std::set with 0 elements, manager=0x7f6ef82314b0, precondition=..., pred_guard=...)
    at /resilience/legion/runtime/legion/legion_views.cc:5239
#15 0x00007f6f2849b124 in Legion::Internal::IndividualView::fill_from (this=0x7f6ef873ba50, fill_view=0x7f6ef803b070, precondition=..., predicate_guard=..., fill_expression=0x7f6ef0013d70,
    op=0x7f6ef010ee80, index=1, collective_match_space=0, fill_mask=..., trace_info=..., recorded_events=std::set with 0 elements, applied_events=std::set with 0 elements, across_helper=0x0,
    manage_dst_events=false, fill_restricted=false, need_valid_return=true) at /resilience/legion/runtime/legion/legion_views.cc:2335
#16 0x00007f6f27e54c69 in Legion::Internal::CopyFillAggregator::issue_fills (this=0x7f6ef8710760, target=0x7f6ef873ba50, fills=std::vector of length 1, capacity 1 = {...},
    recorded_events=std::set with 0 elements, precondition=..., fill_mask=..., trace_info=..., manage_dst_events=false, restricted_output=false, dst_events=0x7f6ef814dab8)
    at /resilience/legion/runtime/legion/legion_analysis.cc:5271
#17 0x00007f6f27e5462a in Legion::Internal::CopyFillAggregator::perform_updates (this=0x7f6ef8710760, updates=std::map with 1 element = {...}, trace_info=..., precondition=...,
    recorded_events=std::set with 0 elements, redop_index=-1, manage_dst_events=false, restricted_output=false, dst_events=0x7f6efd708ca0) at /resilience/legion/runtime/legion/legion_analysis.cc:5220
#18 0x00007f6f27e53dd5 in Legion::Internal::CopyFillAggregator::issue_updates (this=0x7f6ef8710760, trace_info=..., precondition=..., restricted_output=false, manage_dst_events=false,
    dst_events=0x7f6efd708ca0) at /resilience/legion/runtime/legion/legion_analysis.cc:5067
#19 0x00007f6f27e67990 in Legion::Internal::CopyAcrossAnalysis::perform_updates (this=0x7f6ef871cee0, perform_precondition=..., applied_events=std::set with 0 elements, already_deferred=false)
    at /resilience/legion/runtime/legion/legion_analysis.cc:8498
#20 0x00007f6f28536db5 in Legion::Internal::RegionTreeForest::copy_across (this=0x564a3c3a8090, src_req=..., dst_req=..., src_version_info=..., dst_version_info=..., src_targets=..., dst_targets=...,
    sources=std::vector of length 0, capacity 0, op=0x7f6ef010ed20, src_index=0, dst_index=1, precondition=..., src_ready=..., dst_ready=..., guard=..., reservations=std::map with 0 elements,
    trace_info=..., map_applied_events=std::set with 0 elements) at /resilience/legion/runtime/legion/region_tree.cc:2551
#21 0x00007f6f281a5feb in Legion::Internal::CopyOp::perform_copy_across (this=0x7f6ef010ed20, index=0, init_precondition=..., src_ready=..., dst_ready=..., gather_ready=..., scatter_ready=...,
    local_precondition=..., local_postcondition=..., collective_precondition=..., collective_postcondition=..., predication_guard=..., src_targets=..., dst_targets=..., gather_targets=0x0,
    scatter_targets=0x0, trace_info=..., applied_conditions=std::set with 0 elements, compute_preimages=false) at /resilience/legion/runtime/legion/legion_ops.cc:6919
#22 0x00007f6f281a5775 in Legion::Internal::CopyOp::trigger_mapping (this=0x7f6ef010ed20) at /resilience/legion/runtime/legion/legion_ops.cc:6854
#23 0x00007f6f28674532 in Legion::Internal::Runtime::legion_runtime_task (args=0x7f6ef87ff8b0, arglen=12, userdata=0x564a3c4e6790, userlen=8, p=...) at /resilience/legion/runtime/legion/runtime.cc:31712
#24 0x00007f6f257f873a in Realm::LocalTaskProcessor::execute_task (this=0x564a3c3a3490, func_id=4, task_args=...) at /resilience/legion/runtime/realm/proc_impl.cc:1135
#25 0x00007f6f25873537 in Realm::Task::execute_on_processor (this=0x7f6ef87ff730, p=...) at /resilience/legion/runtime/realm/tasks.cc:302

Here's another failure mode:
[0 - 7f3ed98fc800]    0.785309 {6}{realm}: invalid ib memory handle: id=0
snap: /resilience/legion/runtime/realm/runtime_impl.cc:2678: Realm::IBMemory* Realm::RuntimeImpl::get_ib_memory_impl(Realm::ID): Assertion `0 && "invalid ib memory handle"' failed.
snap: /resilience/legion/runtime/realm/transfer/transfer.cc:5137: void Realm::TransferOperation::notify_xd_completion(Realm::XferDesID): Assertion `tracker' failed.

Click to expand backtrace
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139907914778624) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=139907914778624) at ./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=139907914778624, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3  0x00007f3f00f53476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4  0x00007f3f00f397f3 in __GI_abort () at ./stdlib/abort.c:79
#5  0x00007f3f00f3971b in __assert_fail_base (fmt=0x7f3f010ee150 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f3f02103638 "0 && \"invalid ib memory handle\"",
    file=0x7f3f02101f80 "/resilience/legion/runtime/realm/runtime_impl.cc", line=2678, function=<optimized out>) at ./assert/assert.c:92
#6  0x00007f3f00f4ae96 in __GI___assert_fail (assertion=0x7f3f02103638 "0 && \"invalid ib memory handle\"", file=0x7f3f02101f80 "/resilience/legion/runtime/realm/runtime_impl.cc", line=2678,
    function=0x7f3f021035f0 "Realm::IBMemory* Realm::RuntimeImpl::get_ib_memory_impl(Realm::ID)") at ./assert/assert.c:101
#7  0x00007f3f01a0930c in Realm::RuntimeImpl::get_ib_memory_impl (this=0x559340e3d2f0, id=...) at /resilience/legion/runtime/realm/runtime_impl.cc:2678
#8  0x00007f3f015d9d99 in Realm::TransferOperation::allocate_ibs (this=0x7f3ed488cba0) at /resilience/legion/runtime/realm/transfer/transfer.cc:4658
#9  0x00007f3f015d9469 in Realm::TransferOperation::start_or_defer (this=0x7f3ed488cba0) at /resilience/legion/runtime/realm/transfer/transfer.cc:4577
#10 0x00007f3f015f9e10 in Realm::IndexSpace<2, long long>::copy (this=0x7f3ed98e32c0, srcs=std::vector of length 1, capacity 1 = {...}, dsts=std::vector of length 1, capacity 1 = {...},
    indirects=std::vector of length 0, capacity 0, requests=..., wait_on=..., priority=0) at /resilience/legion/runtime/realm/transfer/transfer.cc:5232
#11 0x00007f3f041a899a in Realm::IndexSpace<2, long long>::fill (this=0x7f3ed98e32c0, dsts=std::vector of length 1, capacity 1 = {...}, requests=..., fill_value=0x7f3ed468b040, fill_value_size=128,
    wait_on=..., priority=0) at /resilience/legion/runtime/realm/indexspace.inl:887
#12 0x00007f3f04ba4b50 in Legion::Internal::IndexSpaceExpression::issue_fill_internal<2, long long> (this=0x7f3ecc015de0, forest=0x559340e46090, op=0x7f3ecc113380, space=..., trace_info=...,
    dst_fields=std::vector of length 1, capacity 1 = {...}, fill_value=0x7f3ed468b040, fill_size=128, fill_uid=57, handle=..., tree_id=53, precondition=..., pred_guard=..., unique_event=..., priority=0,
    replay=false) at /resilience/legion/runtime/legion/region_tree.inl:145
#13 0x00007f3f04b88d4c in Legion::Internal::IndexSpaceNodeT<2, long long>::issue_fill (this=0x7f3ecc015a80, op=0x7f3ecc113380, trace_info=..., dst_fields=std::vector of length 1, capacity 1 = {...},
    fill_value=0x7f3ed468b040, fill_size=128, fill_uid=57, handle=..., tree_id=53, precondition=..., pred_guard=..., unique_event=..., priority=0, replay=false)
    at /resilience/legion/runtime/legion/region_tree.inl:5778
#14 0x00007f3f04680992 in Legion::Internal::FillView::issue_fill (this=0x7f3ed468ad80, op=0x7f3ecc113380, fill_expr=0x7f3ecc015de0, trace_info=...,
    dst_fields=std::vector of length 1, capacity 1 = {...}, applied_events=std::set with 0 elements, manager=0x7f3ed4246070, precondition=..., pred_guard=...)
    at /resilience/legion/runtime/legion/legion_views.cc:5239
#15 0x00007f3f04676124 in Legion::Internal::IndividualView::fill_from (this=0x7f3ed473aa70, fill_view=0x7f3ed468ad80, precondition=..., predicate_guard=..., fill_expression=0x7f3ecc015de0,
    op=0x7f3ecc113380, index=1, collective_match_space=0, fill_mask=..., trace_info=..., recorded_events=std::set with 0 elements, applied_events=std::set with 0 elements, across_helper=0x0,
    manage_dst_events=false, fill_restricted=false, need_valid_return=true) at /resilience/legion/runtime/legion/legion_views.cc:2335
#16 0x00007f3f0402fc69 in Legion::Internal::CopyFillAggregator::issue_fills (this=0x7f3ed4710020, target=0x7f3ed473aa70, fills=std::vector of length 1, capacity 1 = {...},
    recorded_events=std::set with 0 elements, precondition=..., fill_mask=..., trace_info=..., manage_dst_events=false, restricted_output=false, dst_events=0x7f3ed4155558)
    at /resilience/legion/runtime/legion/legion_analysis.cc:5271
#17 0x00007f3f0402f62a in Legion::Internal::CopyFillAggregator::perform_updates (this=0x7f3ed4710020, updates=std::map with 1 element = {...}, trace_info=..., precondition=...,
    recorded_events=std::set with 0 elements, redop_index=-1, manage_dst_events=false, restricted_output=false, dst_events=0x7f3ed98e3ca0) at /resilience/legion/runtime/legion/legion_analysis.cc:5220
#18 0x00007f3f0402edd5 in Legion::Internal::CopyFillAggregator::issue_updates (this=0x7f3ed4710020, trace_info=..., precondition=..., restricted_output=false, manage_dst_events=false,
    dst_events=0x7f3ed98e3ca0) at /resilience/legion/runtime/legion/legion_analysis.cc:5067
#19 0x00007f3f04042990 in Legion::Internal::CopyAcrossAnalysis::perform_updates (this=0x7f3ed470fa80, perform_precondition=..., applied_events=std::set with 0 elements, already_deferred=false)
    at /resilience/legion/runtime/legion/legion_analysis.cc:8498
#20 0x00007f3f04711db5 in Legion::Internal::RegionTreeForest::copy_across (this=0x559340e46090, src_req=..., dst_req=..., src_version_info=..., dst_version_info=..., src_targets=..., dst_targets=...,
    sources=std::vector of length 0, capacity 0, op=0x7f3ecc113220, src_index=0, dst_index=1, precondition=..., src_ready=..., dst_ready=..., guard=..., reservations=std::map with 0 elements,
    trace_info=..., map_applied_events=std::set with 0 elements) at /resilience/legion/runtime/legion/region_tree.cc:2551
#21 0x00007f3f04380feb in Legion::Internal::CopyOp::perform_copy_across (this=0x7f3ecc113220, index=0, init_precondition=..., src_ready=..., dst_ready=..., gather_ready=..., scatter_ready=...,
    local_precondition=..., local_postcondition=..., collective_precondition=..., collective_postcondition=..., predication_guard=..., src_targets=..., dst_targets=..., gather_targets=0x0,
    scatter_targets=0x0, trace_info=..., applied_conditions=std::set with 0 elements, compute_preimages=false) at /resilience/legion/runtime/legion/legion_ops.cc:6919
#22 0x00007f3f04380775 in Legion::Internal::CopyOp::trigger_mapping (this=0x7f3ecc113220) at /resilience/legion/runtime/legion/legion_ops.cc:6854
#23 0x00007f3f0484f532 in Legion::Internal::Runtime::legion_runtime_task (args=0x7f3ed4784460, arglen=12, userdata=0x559340f84790, userlen=8, p=...) at /resilience/legion/runtime/legion/runtime.cc:31712
#24 0x00007f3f019d373a in Realm::LocalTaskProcessor::execute_task (this=0x559340e41490, func_id=4, task_args=...) at /resilience/legion/runtime/realm/proc_impl.cc:1135

How do I debug this?

Is this a single node run?  If you're not building with either gasnet or cuda, you can run with valgrind and hopefully it'll find the source of the memory corruption.

Yes, single node, CPU-only. I'll try that.
(If there's anything I need to do to make valgrind happy, please remind me.)

After rediscovering the exact flags to use to convince SNAP to compile with an instruction set that valgrind understands, here's what I'm seeing:
valgrind.log

Pasting the relevant bit here:
==53578==    at 0x4852990: memmove (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==53578==    by 0x79E2461: Realm::TransferDesc::perform_analysis() (transfer.cc:4181)
==53578==    by 0x79E0633: Realm::TransferDesc::check_analysis_preconditions() (transfer.cc:3906)
==53578==    by 0x7A63AE6: Realm::TransferDesc::TransferDesc<3, long long>(Realm::IndexSpace<3, long long>, std::vector<Realm::CopySrcDstField, std::allocator<Realm::CopySrcDstField> > const&, std::vector<Realm::CopySrcDstField, std::allocator<Realm::CopySrcDstField> > const&, std::vector<Realm::CopyIndirection<3, long long>::Base const*, std::allocator<Realm::CopyIndirection<3, long long>::Base const*> > const&, Realm::ProfilingRequestSet const&) (transfer.inl:180)
==53578==    by 0x7A11A06: Realm::IndexSpace<3, long long>::copy(std::vector<Realm::CopySrcDstField, std::allocator<Realm::CopySrcDstField> > const&, std::vector<Realm::CopySrcDstField, std::allocator<Realm::CopySrcDstField> > const&, std::vector<Realm::CopyIndirection<3, long long>::Base const*, std::allocator<Realm::CopyIndirection<3, long long>::Base const*> > const&, Realm::ProfilingRequestSet const&, Realm::Event, int) const (transfer.cc:5217)
==53578==    by 0x643742F: Realm::IndexSpace<3, long long>::fill(std::vector<Realm::CopySrcDstField, std::allocator<Realm::CopySrcDstField> > const&, Realm::ProfilingRequestSet const&, void const*, unsigned long, Realm::Event, int) const (indexspace.inl:887)
==53578==    by 0x6F853F8: Legion::Internal::ApEvent Legion::Internal::IndexSpaceExpression::issue_fill_internal<3, long long>(Legion::Internal::RegionTreeForest*, Legion::Internal::Operation*, Realm::IndexSpace<3, long long> const&, Legion::Internal::PhysicalTraceInfo const&, std::vector<Realm::CopySrcDstField, std::allocator<Realm::CopySrcDstField> > const&, void const*, unsigned long, Legion::Internal::ApEvent, Legion::Internal::PredEvent, Legion::Internal::LgEvent, int, bool) (region_tree.inl:145)

Yeah, this code looks wrong.  @elliottslaughter can you try lifting the following code:
https://gitlab.com/StanfordLegion/legion/-/blob/master/runtime/realm/transfer/transfer.cc#L4181-4186
out of the innermost for loop it's in?  Either before the loop (line 4166) or after (4199) should be fine, but having it
inside is bad for multi-hop fill operations.

That appears to resolve this issue. For posterity here is the diff I am running with:
diff --git a/runtime/realm/transfer/transfer.cc b/runtime/realm/transfer/transfer.cc
index 3421d179d..64909819d 100644
--- a/runtime/realm/transfer/transfer.cc
+++ b/runtime/realm/transfer/transfer.cc
@@ -4177,13 +4177,6 @@ namespace Realm {
                                                                 combined_field_size,
                                                                 domain_size * combined_field_size) :
                              TransferGraph::XDTemplate::mk_edge(ib_idx - 1));
-         // FIXME: handle multiple fields
-         memcpy(static_cast<char *>(fill_data)+fill_ofs,
-                ((srcs[i].size <= CopySrcDstField::MAX_DIRECT_SIZE) ?
-                   srcs[i].fill_data.direct :
-                   srcs[i].fill_data.indirect),
-                srcs[i].size);
-         fill_ofs += srcs[i].size;

          xdn.outputs.resize(1);
           xdn.outputs[0] = ((j == (pathlen - 1)) ?
@@ -4197,6 +4190,14 @@ namespace Realm {
           }
        }

+        // FIXME: handle multiple fields
+        memcpy(static_cast<char *>(fill_data)+fill_ofs,
+               ((srcs[i].size <= CopySrcDstField::MAX_DIRECT_SIZE) ?
+                  srcs[i].fill_data.direct :
+                  srcs[i].fill_data.indirect),
+               srcs[i].size);
+        fill_ofs += srcs[i].size;
+
         prof_usage.source = Memory::NO_MEMORY;
         prof_usage.target = dst_mem;
         prof_usage.size += domain_size * combined_field_size;

Do you want me to commit this, or do you want to?

For posterity, here is a new valgrind log after applying the patch above. There are some conditional jumps on uninitialized values at the start and some mismatched delete / delete [] at the end. Just thought you might want to know.
valgrind_new.txt

Committed the patch in d8951af045cc241662e7db6f10637331dde81890.

 Calling malloc and then in-place new, followed by a delete on the object is completely reasonable.

CI seems to be happy. Closing.


Document social login, access token vs. authorization code

We need to update our documentation of social login, with the following changes:

We now support access token and authorization code callbacks from the social provider, so we should update the documentation to describe how each can by done, and a little information on why you might choose one over the other.

We need to describe the new scope options that are available, e.g. stormpath.web.social.google.scope

I'll just tag along on this issue for social login documentation:
https://docs.stormpath.com/nodejs/express/latest/social_login.html#google-login states that you need to turn on the G+ API; as per testing @robertjd, @bretterer and I did about a month ago, it's no longer needed and we can remove that step from setup.

Note: make sure to document the need to use "postmessage" as the callback url on the directory provider configuration when using the access token flow for google.

Is there a reason you want to use postmessage, instead of the actual callback URI? It's been causing problems in Android.

@edjiang the "postmessage" value is used when the client is a JS app in a browser, so it's a particular use case (not a global one).  Does that address the concern?

Does the Express SDK use the auth code or javascript (implicit) OAuth flows?
Basically our implementation of Stormpath right now means that the implicit grant type and Android SDK are incompatible. Period.

The Express SDK supports both, and uses auth code in it's default login page for all providers except facebook.

Let me forward you an email I wrote to the customer success team about this issue.

Oh ok, I need to read the earlier thing better. I guess this is just documenting the implicit flow, but the default is still authorization code. I guess that's fine.


Update github repo link on Hackage

Please correct repo link guys:
https://hackage.haskell.org/package/turtle
for now it's point to
https://github.com/Gabriella439/Haskell-Turtle-Library

I published a revision fixing this on Hackage


Modrinth Support

Why close this without giving a reason?

No description or any information provided. I have zero idea what the mod is about and have never ever heard about it before. No link of any description of what you are looking for my mod to support or how.  It's a CurseForge (Minecraft) alternative. Don't take it rudely but just searching Modrinth is enough to know what it is. I agree with you, this should be already explained in the issue description.

Issues with improper descriptions are automatically closed.

Okay, sorry, I would think a straight forward title would be enough. My bad


Strange/wrong Error message when giving list of function pointers to jitted function

Hi!
I had an issue with a function which didnt work, and the error message is kind of wrong... (sorry for long code, the function throwing an error is FF, other function are helper functions which are arguments in FF).

@njit("float64[:](float64[:])")
def rho1_grad(x):
    return np.array([2*x[0], 2*x[1], 0., 0.])

@njit("float64[:,:](float64[:])")
def rho1_hesse(x):
    return np.array([
        [2., 0., 0., 0.],
        [0., 2., 0., 0.],
        [0., 0., 0., 0.],
        [0., 0., 0., 0.]
    ])

@njit("float64[:](float64[:])")
def rho2_grad(x):
    return np.array([2*(x[0]-x[2]), 2*(x[1]-x[3]), 2*(x[2]-x[0]), 2*(x[3]-x[1])])

@njit("float64[:,:](float64[:])")
def rho2_hesse(x):
    return np.array([
        [ 2.,  0., -2.,  0.],
        [ 0.,  2.,  0., -2.],
        [-2.,  0.,  2.,  0.],
        [ 0., -2.,  0.,  2.]
    ])

@jit(nopython=False)
def FF(x, v, fs_grad, fs_hesse):
    n = len(x)
    m = len(fs_grad)
    grads = np.empty((n,m))
    vHv = np.empty(m)
    for k in range(m):
        grads[:,k] = fs_grad[k](x)
        hesse = fs_hesse[k](x)
        vHv[k] = v@hesse@v
    lmbds = -np.linalg.solve(grads.T @ grads, vHv)
    a = grads @ lmbds
    return v, a

# Throwing the error:
FF(np.array([1.,1.,1.,0.]), np.array([1.,1.,1.,0.]), fs_grad=[rho1_grad, rho2_grad], fs_hesse=[rho1_hesse, rho2_hesse])
# Variation:
# FF(np.array([1.,1.,1.,0.]), np.array([1.,1.,1.,0.]), fs_grad=[rho1_grad, rho2_grad], fs_hesse=[0, 0])

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-11-908887c274c2> in <module>()
     44
     45
---> 46 FF(np.array([1.,1.,1.,0.]), np.array([1.,1.,1.,0.]), fs_grad=[rho1_grad, rho2_grad], fs_hesse=[rho1_hesse, rho2_hesse])
     47 #FF(np.array([1.,1.,1.,0.]), np.array([1.,1.,1.,0.]), fs_grad=[rho1_grad, rho2_grad], fs_hesse=[0, 0])

TypeError: can't unbox heterogeneous list: type(CPUDispatcher(<function rho1_grad at 0x000000002C1F86A8>)) != type(CPUDispatcher(<function rho2_grad at 0x000000002C5F4730>))

So it says that the list of function fs_grad = [rho1_grad, rho2_grad] is making problems, ok... But the funny thing is, if i turn on the "Variation" of the call (last line in the code), which changes the argument of fs_hesse (and not fs_grad), the actual error is gone (there is an error because the subfunction was replaced by a 0 which is not callable):
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-10-208c3d236307> in <module>()
     45
     46 #FF(np.array([1.,1.,1.,0.]), np.array([1.,1.,1.,0.]), fs_grad=[rho1_grad, rho2_grad], fs_hesse=[rho1_hesse, rho2_hesse])
---> 47 FF(np.array([1.,1.,1.,0.]), np.array([1.,1.,1.,0.]), fs_grad=[rho1_grad, rho2_grad], fs_hesse=[0, 0])

TypeError: 'int' object is not callable

For the actual problem I have a workaround by using a function wrapper, but I thought I post this error message because it looks like a wrong error attribution

@mha-py thanks for submitting this. I have reduced this to smaller reproducer:
from numba import njit

@njit
def one():
    return 1

@njit
def two():
    return 2

@njit
def test(f1):
    return f1[0]() + f1[1]()

print(test([one, two]))

Effectively, what this points too, is that lists of function pointers as arguments are not yet supported. A workaround in this case would be:
from numba import njit

@njit
def one():
    return 1

@njit
def two():
    return 2

@njit
def test(f1, f2):
    return f1() + f2()

print(test(one, two))

The reason, the error goes away when using ints, is because the error with the ints is detected before the issue with the list can be detected.

I am marking this as a feature_request, although I am not even sure it can be done.

Another workaround would be to use tuples:
print(test(f1=(one, two), f2=(three, four)))

Note: I have updates the issue title to reflect it's current state as a feature request.

Thank you for answering! Atm I am putting both functions results into one function and stack their outputs to an array, that worked for me

@mha-py thanks for following up!


#19319 Fix q-string rule chars unreading

The case in the issue should not be reproducible anymore.
Also q-strings should work. Example: q'[What's a quote among friends?]'
Only for Oracle.

What do you think about the original query?
SELECT q.* FROM dual q;
Do you have plans to add it to your tests?

I'm not sure this concrete case should be tested somehow, but I added it.

verified


Automatic scrolling to current date on page load

Hello Team,
I have a slickgrid list where it consists of hundreds of data and I have a column named Nidate which consists of date. I ordered it by date desc and I have lot of future dates in it and instead of scrolling down to the current date I need an automatic scrolling of the slickgrid to the current date whenever the page is loaded.
I just want to know how this can be achieved in slickgrid. Please let me know on this.
Thanks

grid.ScrollTo(rowIndex)
Please ask questions on StackOverflow in future.
Also read: www.slickgrid.net


@keyup not working

Hi, I'm using @keyup.enter with this package. But nothing event fired.
Could you please take a look into it?
Thank you very much!
Here is my code:
<textarea-autosize
class="form-control"
rows="1"
:min-height="40"
:max-height="300"
ref="comment"
v-model="bodyComment"
@keydown.enter.exact.prevent
@keyup.enter.exact="addComment(activity._id)"
@keydown.enter.shift.exact="newline" />

I find out a solution. I add the ‘native’ modifier to the keyup event.
Like this:
@keydown.enter.native
@keyup.enter.native


java.io.FileNotFoundException: /data/user/0/XXX/cache/110826232119603-1.jpg

android 10
java.io.FileNotFoundException: /data/user/0/XXX/cache/110826232119603-1.jpg

只有那张图片报错，路径是/data/user/0/XXX开头的，其他图片路径是正确的

It looks like this image was deleted, but MediaStore was not notified.

The problem will be resolved.
You can try to use 0.5.0-dev.3.


feature-list-for-release-notes 0.0.4

New Pull Request Checklist
Please mark the points which you did / accept.

[X] I read the Step Development Guideline
[X] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[X] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[X] I read and accept the Abandoned Step policy

Hi @maqoo ,
thanks for the new step version, it looks great to me!


When printing analysis messages to the console, separate the texttual…

… description from the rest with a ':' instead of '-'
Context:
I've been trying to get the analyzer results integrated into a CI build at work, which is running in Azure DevOps.
I've got the SARIF results file being consumed by the MS SAST scans tab DevOps extension, and that appears to be working nicely.
However, I though it might be nice if the results could be displayed as regular build warnings as well as in the sarif, so they just display in the main build output instead of you having to look at a different tab to see issues.
I couldn't get the results to show up as warnings, but then noticed that the analysers CLI tool currently outputs the results to the console with the final field separated from the rest with a - rather than the usual : and it does seem that changing that causes the output to be recognised as warnings (complete with yellow text output rather than white).
Is this a reasonable change to make?

Note: I haven't been able to run the unit tests locally due to the issue I mentioned at https://github.com/ionide/FSharp.Analyzers.SDK/pull/182#issuecomment-1951337520

Would you mind adding a screen shot of the before and after that you see in your CI?

If I run my fun.build script with the current analyzers sdk version, I get this:

and with the modification I get this:

Also If I enable a binlog in the build, I now get warnings shown in the log:

whereas before I only had messages:

refs this 'determine what's a warning by pattern matching' behaviour in MSBuild I think? https://learn.microsoft.com/en-us/visualstudio/msbuild/msbuild-diagnostic-format-for-tasks?view=vs-2022

perfect, that's what I expected the cause to be - the SDK is now emitting errors matching the MSBuild Canonical Error Format.


[DRAFT] Mip-Splatting implementation

Implementation of Mip-Splatting. Tested on bicycle scenes and works OK.
Here is a comparison when trained with factor 4 and render with factor 1.

Left is from gsplat's default setting and right is from this PR.
Benchmark results on 7 scenes of Mip-NeRF 360 dataset:

PSNR
SSIM
LPIPS
num_GS (M)

classic
28.989
0.871
0.136
3.23

antialiased
29.043
0.871
0.139
3.37

mip-splatting (this PR)
29.051
0.872
0.138
3.16

mip-splatting (this PR) + cuda implementation of compute_3D_smoothing_filter
29.017
0.873
0.139
3.14

Here is the benchmark results of training with factor 8 and render with factor 8, 4, 2, 1.
metric is PSNR, SSIM and LPIPS.

1x
2x
4x
8x
avg.
1x
2x
4x
8x
avg.
1x
2x
4x
8x
avg.

classic
30.08
23.14
20.34
19.18
23.18
0.912
0.722
0.597
0.605
0.709
0.049
0.169
0.327
0.470
0.254

antialiased
29.77
24.69
22.39
21.65
24.63
0.904
0.736
0.605
0.588
0.708
0.056
0.174
0.304
0.438
0.243

mip-splatting (this PR)
30.29
26.84
26.07
26.14
27.33
0.916
0.799
0.748
0.776
0.810
0.050
0.192
0.309
0.428
0.245

Clean up later.

Awesome @niujinshuchong !
I'm thinking if there is a way to elegantly message some of implementation into the gsplat library, e.g., into rasterization() function so that the downstream users (e.g., nerfstudio) can just import and use.
It doesn't have to be living in the rasterization() function if it does not fit there. We could also put some implementation in to like gsplat/mip.py, so that ppl can use it with:
from gsplat.mip import ...
# and do their thing

I'll come back to it later with a closer look. Great job!

@liruilong940607 Thanks for the suggestions. I added a cuda implementation of compute_3D_smoothing_filter and it can be imported from gsplat. The benchmark results (see top) are reasonable. For now, I create a new script simple_trainer_mip_splatting.py and it almost the same as simple_trainer.py, do you think we should merge them or make it separate? I also added a training script to use multiple gpus.

Thanks for the benchmarking! Really nice! Yeah from a quick going through of the training script, it seems to be very compatible with the original one so I would suggest we merge the two! Just need a flag in the config, e.g.(--mip_splatting?) and a couple if else in the code.

What's the plan on merging this PR? I am particularly interested in this feature (esp. the 3D filter part).

I think this PR is just about cleaning up, add doc strings and update webpage. It would be nice to finish it up.
Not sure if @niujinshuchong still has time for it. But I might be able to find some cycles in the next two weeks to help with finishing up this PR.

@liruilong940607 Yes, it just need to be clean up. I will find some time to continue. However, it would be great if you can help with it. Sorry for the late reply.


Code folding doesn't work!

Issue Type: Bug
I have extensive comments in all my stored procedures. The arrows that let me  show/hide them are gone. I have enabled code folding in settings, but it seems to have no effect. The custom keyboard shortcuts I created to let me show/hide comments also don't work.
Azure Data Studio version: azuredatastudio 1.42.0 (22f384e569bc90d8b3231cc8c8cff99ea16c5052, 2023-03-17T18:15:48.982Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
Preview Features: Enabled

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i9-11950H @ 2.60GHz (16 x 2611)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
63.20GB (48.83GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

query-editor-boost
dre
0.4.1

ssmskeymap
kev
1.1.0

admin-tool-ext-win
Mic
0.1.2

import
Mic
1.5.4

query-history
Mic
0.5.3

extra-sql-script-as
pac
0.5.0

sql-search
Red
0.4.2

(1 theme extensions excluded)

My bad.  Code folding indicators hide when not hovered by a mouse. (Not crazy about that.) My keyboard shortcuts also got borked by the new update. Fixed. Please disregard.


MH-12970, Senseless XACML parsing

The method getAclFromInputStream(…) should parse an XACML file from a
given input stream and return the ACL object. The current implementation
internally parses the input stream, catching possible exceptions and
packing the result in an Option only to unpack it again right
afterwards which throws an exception in case the exception had been
caught before. Then the result is packed in a Tuple with a statically
set AclScope which, of course, is immediately unpacked again with the
scope just being discarded.
Finally, the one usage of this would break if there was any problem with
the ACL instead of handling this gracefully, falling back to a strict
non-permissive access rule.
This patch replaces all this mess with a straightforward implementation
of parsing the ACL from the given XACML input stream.
Work sponsored by SWITCH

Fixed typo in log statement. Should now be ready to go.


crash in cluster initialization with SDS

(Posting publicly because this was already disclosed in Istio/Istio).
Ref: https://github.com/istio/istio/issues/45045
==32==ERROR: AddressSanitizer: heap-use-after-free on address 0x616000153080 at pc 0x55754d7ef7d6 bp 0x7fff67057010 sp 0x7fff67057008
READ of size 8 at 0x616000153080 thread T0
    #0 0x55754d7ef7d5 in Envoy::Upstream::ClusterManagerInitHelper::initializeSecondaryClusters() /proc/self/cwd/external/envoy/source/common/upstream/cluster_manager_impl.cc:162:14

Hey @kyessenov have you got an updates on this ?

I don't have an update.


{packaging} Update azure-common to 1.1.28

Related command
Used by many azure-cli commands.
Description
The azure-common package was updated to 1.1.28 about four months ago and I'd like to get it updated in Fedora Linux.
Testing Guide
Existing testing processes should be used.

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

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

packaging

@major, which new features from azure-common 1.1.28 will CLI commands must use? if the answer is NO, we'd prefer not to upgrade as there may be breaking changes in new version of azure-common which will break Azure CLI.


Format JSX with newlines and indentation

Description
This modifies how generated JSX is formatted such that it includes newlines and indentation. Previously, much of the content would be on a single line. Here's an example of the new output:
<MimeTabs className={'openapi-tabs__mime'}>
  <TabItem label={'application/json'} value={'application/json-schema'}>

Body

        required

        <SchemaItem
          collapsible={false}
          name={'username'}
          required={true}
          schemaName={'Username'}
          qualifierMessage={undefined}
          schema={{ title: 'Username', type: 'string' }}
        ></SchemaItem>
        <SchemaItem
          collapsible={false}
          name={'password'}
          required={true}
          schemaName={'Password'}
          qualifierMessage={undefined}
          schema={{ title: 'Password', type: 'string' }}
        ></SchemaItem>

  </TabItem>
</MimeTabs>

Motivation and Context
There are two motivations:

It's easier to read the generated MDX, and diffs are also much cleaner and easier to read when regenerating docs.
The new formatting is compatible with @mdx-js/react v1 and v2. The previous formatting was only compatible with v1, and is one of the blockers to docusaurus v3 compatibility. See #591 for an open issue.

How Has This Been Tested?
I've tested this manually with my own API documentation.
Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

[X] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes if appropriate.
[x] All new and existing tests passed.

I've discovered that this can break markdown formatting of response descriptions with mdx v1 because they're no longer on their own lines without indentation. Is there any plan to have a branch for docusaurus v3 compatibility? This might be a better fit for that. If not, I can try to preserve the mdx v1 behavior while still adding support for v2, the generated code will just be a bit uglier.

Hi @sangaline, thanks for PR and suggestions.
If you haven't seen it already, I would recommend reading through https://github.com/PaloAltoNetworks/docusaurus-openapi-docs/pull/514 for additional background/work on this issue, which resulted in https://docusaurus-openapi.tryingpan.dev/#markdowngenerators.
We haven't yet identified/explored the breaking changes introduced between Docusaurus 2.4.1 - v3.0.0. If there's some path to maintaining backward compatibility, we may explore that but, based on past experience, that may not be possible without a major refactor.

Hi @sangaline, any luck with solving for the broken descriptions?

See #660 for implementation of your changes


Change event driven architecture to event sourced and framework agnostic

Is your feature request related to a problem? Please describe.
Kafka is not the only solution for an event-driven architecture.
I think it would be more valuable to describe an enterprise-level event-sourced architecture that specifically dives into concepts like CQRS and DDD and how they play well with not only decentralization but also with event-sourcing.
Describe the solution you'd like
Remove Kafka and avoid Kafka-specific features.
Add CQRS principles
Add DDD principles
Describe alternatives you've considered
Perhaps leave event driven architecture as the main context but still remove Kafka references.
Additional context

Very good suggestion. The article on "Event driven architecture with Kafka" was written specifically about Kafka and its capabilities. Let's write a separate article about CQRS and DDD principles.


Not able to upload files from postman to durpal dev portal.

Selected file with binary. I get 403 forbidden errors.

Hello @simantstha,
This repository is about the JSON:API specification itself. Questions about specific implementations like Drupal should be asked at other places. E.g. StackOverflow or a Drupal community chat.
I'm closing this issue as off topic.
Best Jeldrik


OWASP Zap Automation Investigation

OWASP Zap Automation Investigation

Added OWASP Zap report generate in GitHub Actions. An example can be found here: https://github.com/opendcs/rest_api/actions/runs/7597437443. The HTML report is attached as well as a brief Markdown summary in the GitHub Action job summary: https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/


Choosing "Install AppMap Agent" creates appmap.yml

Currently, the IntelliJ extension creates an appmap.yml in the project only when the user first starts their app or tests with AppMap (via the custom Run Configurations).
We are planning to use the presence of appmap.yml in a project as a definitive sign that the user has successfully installed AppMap there. Therefore, we want the IntelliJ plugin to create the appmap.yml when they instead click this button to launch the "Install AppMap Agent" action:

for Java only
create for all Java modules if none was found

:tada: This issue has been resolved in version 0.45.6 :tada:
The release is available on:

v0.45.6
GitHub release

Your semantic-release bot :package::rocket:


python: Replace NamedTuple with dataclass

Certainly looks to be a nice cleanup :)

Merged, thanks @andersk!


Making feature restrictions explicit

This page should state explicitly that Analyze in Excel is a Power BI service feature which makes it unavailable in Power BI Report Server and Power BI Embedded.

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

ID: 2fcb95bc-abb8-5147-ddc5-00714e30f79b
Version Independent ID: 45626f2c-9e5c-6bdd-6fbb-b82c279962e0
Content: Analyze in Excel for Power BI - Power BI
Content Source: powerbi-docs/service-analyze-in-excel.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment @otravers - we'll let the writer know so the article can be updated.

Added author, labels.

Thanks for pointing that out - we've updated the article. The change will show up within 24 hours.


support: Correctly show Unspecified org type at /activity/support.

Because the org type is marked as "hidden", the HTML was being generated
for orgs with Unspecified .org_type with no <option> selected, meaning
it was displayed on the page using the first <option> in the list
(Business). The /support endpoint should ignore the "hidden" property,
since there's no reason not to - we only want to hide this org type from
regular users during Org registration.
Here's a screenshot showing how this was displayed in a misleading way in the case of an organization with no .org_type set;

Merged, thanks for fixing this @mateuszmandera!


Profilermanager (VS Windows only)

Enables ability to call external profiler, specifically Intel® VTune™ Amplifier.

Is this superseded by #4155? If so, can you close this PR?


Upgrading to React 16 - Implement Error Boundaries and Polyfills

Feature Update
#510 Needs additional, very simple fixes
React version 16 is fresh out of the master branch and the changelog notes some minor breaking changes.
Why is this feature being added?

Version 16 adds some great new functionality, but needs some love to get it upgraded safely.

Bug Report

Implement polyfills in Jest.

https://github.com/facebook/jest/issues/4545#issuecomment-332762365

Implement polyfills for ES6 map and set.

https://github.com/facebook/react/blob/master/CHANGELOG.md#new-js-environment-requirements

Implement polyfill for requestAnimationFrame

https://github.com/facebook/jest/issues/4545#issuecomment-332762365

Implement Error Boundaries
https://reactjs.org/blog/2017/07/26/error-handling-in-react-16.html#introducing-error-boundaries

These changes shouldn't take more than an hour, with the exception of maybe the Error Boundaries. I'd need to understand the scope of their necessity, but if all is a go then by all means. Just at minimum do the requestAnimationFrame polyfill.

@sethbergman I am working on upgrading this to React 16.

@jenniferkaplannyc @sethbergman is mid cherrypick on this isse - apologies.

Fixed in #542

We need access to our CI/build process to debug the issues arising from implementing React 16 in production.

https://reactjs.org/blog/2017/09/26/react-v16.0.html#upgrading

I was having this same problem when I tried to upgrade your site, but then I saw the issue was closed so I deleted my files. However, were there any depreciation warnings in the previous version of React? If so, lets fix those to see if that resolves the issue when upgrading.

We're on 15.4, not 15.6 as it states in the article. There would need to be an upgrade to 15.6 first I believe.

But yes there were many peerDependencies that were giving warnings.

Linking this one here too: https://medium.com/ecmastack/what-you-need-to-know-about-react-16-a4e216522041

I think we should work through those first. If that is too time consuming then lets keep it on the current version of React.

On Oct 2, 2017, at 12:32 PM, Seth Bergman<EMAIL_ADDRESS>wrote:
But yes there were many peerDependencies that were giving warnings.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/OperationCode/operationcode_frontend/issues/532#issuecomment-333589066, or mute the thread https://github.com/notifications/unsubscribe-auth/AWBNPZujJD9bf0qLYV156hjxz_t_vU2wks5soRAYgaJpZM4Pp9vN.

Perhaps a good next step would be to move to 15.6 to have more visibility on deprecation warnings.

Yes, that is a very good idea!

On Oct 2, 2017, at 12:35 PM, Kyle Holmberg<EMAIL_ADDRESS>wrote:
Perhaps a good next step would be to move to 15.6 to have more visibility on deprecation warnings.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/OperationCode/operationcode_frontend/issues/532#issuecomment-333589935, or mute the thread https://github.com/notifications/unsubscribe-auth/AWBNPS-nM3H5GmlmYTr5a46nz7j5DFZ6ks5soRDQgaJpZM4Pp9vN.

I agree wholeheartedly!

@jenniferkaplannyc or @sethbergman feel free to grab #556

I'm about to take a nap. :+1:

@sethbergman @kylemh Any hints on how to locally test if the shims and polyfills work correctly?

I'm not sure why were not receiving dev warnings for dependencies, but I'm fairly certain that Storybook, React-Modal, and another few components have not yet made the move to React 16, thereby blocking this issue.

@kylemh Does this still need to be open? package.json shows that we're already on React v16 .

@jjhampton nope


Update heroku docs

I'm working on getting txgh working in Heroku and the docs lead me down a rough path. These docs bring it up to what I had to do to make things work.

Hey @BillWeiss thanks for taking the time to update the docs, we are in a process of making some patches to txgh so that it plays nicely with our new webhooks. I will test the heroku deployment in a day or two and go ahead with merging your PR.
Thanks again!


Navigation through the documentation

Thanks for adding these, not sure if we need them on all the pages, but I will merge it! We can easily change these in the future!

I'm wanting to work on the documentation, do you have anything you wish somebody was working on?

There are lot's of things that need to be done, but I need to set up at least one of the pages they way I imagined, so you can base your work on that... If I have time I might do that tomorrow, or early next week, and then there are plenty of components to document!


Support specifying figure names in _run_analysis

What is the expected behavior?
The main method for running an analysis is _run_analysis:
https://github.com/Qiskit/qiskit-experiments/blob/a0beb41ec0757429031e0e6e7a7855dcc72877cd/qiskit_experiments/framework/base_analysis.py#L200-L204
There is no way to specify names for the figures, so they can only be retrieved by index, even though ExperimentData.figure supports retrieving by string name.

Possibly a related issue: #182

closing as #764 allows defining the figure names by changing figure_names in the analysis options.
please open another new issue if more flexibility is required


Controlling table width

How to implement the logic so that table width expand to cover whole device with when table width is smaller than the device width, also available space equally distributed to columns & if table width bigger than the device width it will function as usual i.e. scrollable.

+1

Unfortunately, there is nothing in TableView that automatically resolves this for now. The TableView only calculates the minimum value the column should be. So if there is an empty area, it does not say that I may use it.
There is a way to solve this but you have to do it.
By taking the incoming column widths via getColumnWidth(int columnPosition), you can compare with the width of the TableView, check whether the case you have mentioned occurs, you can assign a width to the corresponding columns yourself using setColumnWidth(int columnPosition, int width)


How to auto-open/auto-jump to last view before last exit?

When I connect to a database I want immediately afterwards to auto-open resp. auto-jump to the last view before last exit/disconnect.
So when I saw recently
MySQL / Databases / mydatabase123 / Tables / mytable456 ---> Data Tab
then exactly this view/page should be re-opened again.
How can I achieve this?

Already implemented


Total Distance Moved Calculation

Function that returns the total distance travelled by the bot.

Can I work on this?


Add support for incoming proxy protocol

Clear and concise description of the problem
As an admin, running woodpecker behind reverse proxies / loadbalancers (i.e. HAProxy, nginx), I'd like to have the real client IP in my logs without needing an extra proxy breaking the TLS connection and mapping them to the X- Headers.
Suggested solution
We could add support for the widely adopted Proxy Protocol (which is pretty much the standard in all major loadbalancers, reverse proxies, web application firewalls, etc. link to non-definitive list) to woodpecker-server. By now v2 is the most common, though in enterprise hardware (I hate those things) v1 is still fairly common.
Alternative
At least add the possibility to limit hosts from which the X- headers are accepted (important when having woodpeckers server exposed, while still using a reverse proxy for some cases, as otherwise spoofing of the client-ip may occur.
Additional context
Using the Proxy Protocol allows for TLS pass-through (not breaking TLS before it reaches the server) without losing the clients real IP address.
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

@gapodo is this similar/same to #837 ?

The short answer is no...

#837 is about authentication via a reverse proxy, while FR this is about handling traffic forwarded to woodpecker in a way that preserves the clients IP, allowing them to be logged / handled accordingly (this becomes important when monitoring e.g. for attempted logins, weird search entries,...).
Using the proxy-protocol is typical in setups where there is a Loadbalancer, Layer4 stream router (think HaProxy in tcp mode), a Web Application Firewall, IDS or similar, also many "cloud" setups (think hosting at azure, google or amazon) allow for the use of the proxy-protocol, to allow for better request handling.


where is writer_bytes_array

Search before asking

[x] I searched the issues and found no similar issues.

What happened + What you expected to happen
branch: main
i canot find the writer_bytes_array  code

Reproduction way
Anything else
Are you willing to submit a PR?

[x] Yes I am willing to submit a PR!

https://github.com/search?q=repo%3Aalibaba%2Fyalantinglibs writer_bytes_array&type=code

😂，thanks for your report. It's a typo. I'll add more test for it.

😂，thanks for your report. It's a typo. I'll add more test for it.

it`s okay，but looks like there's another problem. I'll sync it up later

The function struct_pack::read/struct_pack::write/struct_pack::get_needed_size, which is designed for help user to serialize/deserialize the user-defined type. However, the document of those functions is miss, and it‘s not perfect and needs to be refactored and use the same code as the internal implementation.
I will improve it later.

For now, I will just make a simple bugfix.


30:38: execution error: Can’t get application "Spotify". (-1728)

I just installed it via npm but I cannot set token with "spotify token" command.

What happends if you try an other command like spotify play?

➜  ~ spotify play
30:38: execution error: Can’t get application "Spotify". (-1728)
Playing Spotify.
30:34: execution error: The variable play is not defined. (-2753)

I just installed npm with homebrew and tried https://github.com/sindresorhus/speed-test to make sure my environment works.

Did it work ? I re-installed spotify-cli-mac and it works for me
Can you try reinstalling it?

I found a problem. After uninstall, I can still access the command spotify. But I don't know how to find where the remaining files are.

https://stackoverflow.com/questions/5926672/where-does-npm-install-packages

Thank you! I finally found out the problem.

➜  ~ type spotify
spotify is a shell function from /Users/greenmoon55/.oh-my-zsh/plugins/osx/osx.plugin.zsh

which is https://github.com/robbyrussell/oh-my-zsh/blob/master/plugins/osx/osx.plugin.zsh

Ah oke sweet!


model.fit(..., verbose=0) still prints stuff

Click to expand!
Issue Type
Bug
Source
binary
Tensorflow Version
tf 2.9.1
Custom Code
Yes
OS Platform and Distribution
Windows 10 Build 17763
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
I expected to see nothing when calling `model.fit(..., verbose=0)`

Standalone code to reproduce the issue
import os
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '2'
from tensorflow import keras
from keras.layers import InputLayer, Dense

data = [
	[ [0,0], [0] ],
	[ [0,1], [1] ],
	[ [1,0], [1] ],
	[ [1,1], [0] ],
]
x_train = [i[0] for i in data]
y_train = [i[1] for i in data]

model = keras.Sequential([
	InputLayer(2),
	Dense(units=8, activation='sigmoid'),
	Dense(units=1, activation='sigmoid'),
])
model.compile(optimizer=keras.optimizers.SGD(0.6), loss='mean_squared_error')

model.fit(x_train, y_train, batch_size=1, epochs=500, verbose=0)

print(
	model.predict(  [ [0,0], [0,1], [1,0], [1,1] ]  )
)

Relevant log output
No response

The method for fit has nothing defined for verbose = 0. Find attached screenshot from tensorflow/tensorflow/python/keras/engine/training.py

Hi @m-ahmadi,
Thank you for opening the issue. Development of keras moved to another repository.
Could you post this issue on keras-team/keras repo.
To know more please refer:
https://discuss.tensorflow.org/t/keras-project-moved-to-new-repository-in-https-github-com-keras-team-keras/1999
Thank you!


Need update and a guide to run this project on idea

This is a very great project for pepole want to use kotlin to develop frontend and backend, but two major problem must be sloved to satisfy those pepole:

update this project to working with ktor 0.9
a guide to how to config this to run on idea

Thanks for the open source effort again, learn so much

0.9.1 is already out there, should update to it


Correction for raw affiliation Laboratory of Molecular Biology of the Cell, UMR 5239, Ecole Normale Supérieure de Lyon, Centre National de la Recherche Scientifique, 69007 Lyon, France

Correction needed for raw affiliation Laboratory of Molecular Biology of the Cell, UMR 5239, Ecole Normale Supérieure de Lyon, Centre National de la Recherche Scientifique, 69007 Lyon, France
raw_affiliation_name: Laboratory of Molecular Biology of the Cell, UMR 5239, Ecole Normale Supérieure de Lyon, Centre National de la Recherche Scientifique, 69007 Lyon, France
new_rors: 02feahw73;029brtt94;01bj4fd12
previous_rors: 02feahw73;029brtt94
works_examples: W2078032922
contact: 86e0ceb3b96d8545dbb36ee87f979b01:08f2e6c582e96d28d6ac4bd46958 @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-01. The new affiliations should be visible within the next 7 days.


Speech SDK for Windows IoT Core UWP running on ARM (Raspberry Pi)

Hi, it's stated that ARM devices running Windows IoT Core are currently not yet supported. When is this going to be possible? This prevents anyone from using popular IoT devices with Windows and this library

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

ID: efae7ff6-5557-221f-7539-5d2d1883127d
Version Independent ID: 4b868e15-0248-635c-aa2f-d591bbc77d65
Content: About the Cognitive Services Speech SDK - Microsoft Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/speech-sdk.md
Service: cognitive-services
GitHub Login: @v-jerkin
Microsoft Alias: v-jerkin

@jjgriff93 Thanks for the feedback! We are currently investigating and will update you shortly.
@v-jerkin Do you have any idea about that? Thanks a lot!

@YutongTie-MSFT please reassign to @erhopf

This is a feature request. Please reassign to @WSturman.

this will be supported in the future, but won't be ready for a few month. Tentatively in the first half cy19

#please-close
This feature is on our current roadmap.


Update ResourceAuthorizeAttribute.cs

This gives intellisense warnings that Roles and Users should not be used.

Nice ;) thanks!


Make initializeGlExtensions protected

This function is used in subclass PlatformEGLHeadless (see here) resulting in build errors.

LGTM. Can you please accept the CLA?

CLA has been accepted. Is it possible for me to apply the label "internal" or would somebody else need to do that?

CLA has been accepted. Is it possible for me to apply the label "internal" or would somebody else need to do that?

Applied it for you.  thanks.


Add include guard to kits/cpp/lux/kit.hpp

Add include guard to kits/cpp/lux/kit.hpp so that multiple #include's
don't mess up C++ autocompleters in editors such as vim. This issue
was found when I tried to modularize code into separate class in
different files.
Changes are already put in simple.zip.

oh this makes sense, thanks for catching this out!

closes #56


Applies hotfixes to RSS reader app

What this PR does

[x] Changes the default value of bypass_cors from false to true. This is because the default value set for the rss_url is the one from BBC.
[x] Ensures that the app is tested against various RSS feed sources

RSS URLs I've tested so far

URL
Requires CORS
bypass_cors

http://feeds.bbci.co.uk/news/rss.xml
Yes
true

https://lifehacker.com/rss
Yes
true

https://www.reddit.com/.rss
Yes
true

https://rss.nytimes.com/services/xml/rss/nyt/US.xml
No
false

http://rss.sciam.com/sciam/60secsciencepodcast
Yes
true

Furthermore, you can see a curated list of RSS feeds here — https://github.com/plenaryapp/awesome-rss-feeds.

@vpetersson, requesting a code review...


Added CDN-JS support

Hey I submited this repo to wellknown cdn provider and now its time to add to getting started page:
https://cdnjs.com/libraries/vue-tour
<script src="https://cdnjs.cloudflare.com/ajax/libs/vue-tour/1.6.0/vue-tour.umd.min.js" integrity="sha512-uAuPH2bRtMDXOaZVCyeaiD+nYrwR8yFQWk9Qu3KiMU1nVjSdQkkw60gIfoYHqtQa1/pnTWLy+Vo1lhV4jQU74w==" crossorigin="anonymous"></script>

<script src="https://cdnjs.cloudflare.com/ajax/libs/vue-tour/1.6.0/vue-tour.common.js" integrity="sha512-0PsIi6EuMH2mfjNO++HJK6PQpkn6He2vwGbvlVItpOkf6Ea9Qo/A0n+ViWb+TP1cE+VkAStzl9tQQn6Y4Kf0MA==" crossorigin="anonymous"></script>

<script src="https://cdnjs.cloudflare.com/ajax/libs/vue-tour/1.6.0/vue-tour.common.min.js" integrity="sha512-d/xxiS42v3gsXoZ2tnLfWP0twUp1/bfYNDFACPLSBrgZE2Na2D/GlaEP6zo79EpTsRPgyUdjYntj+7WOMR1C4A==" crossorigin="anonymous"></script>

<script src="https://cdnjs.cloudflare.com/ajax/libs/vue-tour/1.6.0/vue-tour.umd.js" integrity="sha512-zogBmAi1pPOXELv8RKwHtrOXIb1qLhSgoPFlAbTg/gCG2v91bGrzHEK1+4vsEoMOHYiDdgRE8vbj58aR88RJFA==" crossorigin="anonymous"></script>

Also keep in mind, cdnjs team will be changing github repo to add this official repo (instead of mine). But that's not  a problem, because cdn js is pulling data from npm. https://github.com/cdnjs/packages/pull/672

Thanks for submission. Is it possible to include CSS file? We need CSS styles if we want Vue Tour to be smooth running.


Add buf_group field to Readv and RecvMsg opcodes

Follow-up to #123, this enables the use of io_uring's automatic buffer selection for those operations.

Would you like to add a test?

Added.

It looks like ci hangs on tcp_buffer_select, and it looks like the kernel that ci is currently using doesn't support this feature. we may need to mark it as unstable until we update the ci kernel.

It looks like ci hangs on tcp_buffer_select, and it looks like the kernel that ci is currently using doesn't support this feature. we may need to mark it as unstable until we update the ci kernel.

This pr is great with supporting buf_group field to Readv and RecvMsg opcode. When would the pr be merged ?

@glenn-wang We need to mark the feature as unstable and pass the ci test.

@glenn-wang We need to mark the feature as unstable and pass the ci test.

Hi, @quininer
This pr still not be merged, even could not be as unstable feature.

The buf_group field may not be tested for the Read op either. Maybe it is enough to add the support without adding unit tests for it. Users of this crate can always report if they find a problem and even provide a fix. The users of this crate seem to be  very good at uring and Rust issues.

And maybe someone wants to propose a way for the unit tests to check the version of kernel they are running on. The kernel uring API itself isn't great at always providing a backwards compatible way of checking that one of its features is supported; they try for many features but many fell through the cracks - in terms of being able to check for support. The liburing documentation always falls back on describing what version of kernel the feature started being supported in.

We can use not(feature = "ci") cfg to allow ci to skip this test temporarily. like https://github.com/tokio-rs/io-uring/blob/38de039be7827b3a11566bf45e1745377c4bc29c/io-uring-test/src/main.rs#L89-L92

@quininer Don't merge this yet. I've run the test on a 6.1 kernel and found a unit test failure. Let me investigate and push something else up to fix it.

@quininer I think it is good to merge now. Squash merge I hope. You are welcome to look at this last merge of mine and see if the difference between a 5.15 kernel and a 6.1 kernel, that I was getting with this branch, in case you can make more sense out of it than I did.

@quininer @glenn-wang @mrakh While I'm getting the unit test better setup it, it has become clear recvmsg and BUFFER_SELECT are generally incompatible unless one sets the msg_iovlen value to 1, as the API doesn't allow for returning multiple buffer IDs. Just one buffer ID can be returned in the cqe, there is no field in the iovec for placing it, so the application would not know what buffers had been selected. I've seen both a 5.15 and a 6.1 kernel return a result of EINVAL when the msg_iovlen is 2, so while the liburing man pages don't document it, I believe recvmsg and BUFFER_SELECT is only valid when a single iovec is specified and the kernel uring device enforces that - which will beg the question for most apps of why even bother using recvmsg with provided buffers.
And I'm not going to go through the same trials with readv but I suspect the same. There's no sense in trying to gather into multiple buffers with a readv length other than 1 because the API would have no way of returning multiple buffer ids.

Hey @FrankReh, thanks for following up with this. Having buffer selection for recvmsg and readv is still useful even with the 1-iovec limitation because they have additional functionality not available through the more generic interfaces:

recvmsg returns important auxiliary data through the struct msghdr* argument. AFAIK, it's the only way using io_uring to get the source IP of an incoming UDP packet.
readv op contains a flags argument to specify things like RWF_DSYNC or RWF_SYNC on a per-invocation basis.

@mrakh Good points.

@quininer Ready for another review.

Thank you! @FrankReh @mrakh


add last site config modified time to environment api

this would allow a better polling to see if the new config is effective than polluting with dummy appSettings.

looks good


Can't install ngx-ui

When I use command npm i @swimlane/ngx-ui --S ,
It has error like this
npm ERR! path F:\workspace\ERPWorkspace\erpweb\node_modules@angular\flex-layout
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename 'F:\workspace\ERPWorkspace\erpweb\node_modules@angular\flex-layout' -><EMAIL_ADDRESS>npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR!      C:\Users\ittiwat123\AppData\Roaming\npm-cache_logs\2017-06-26T06_08_38_918Z-debug.log

angular/cli: 1.1.3
node: 8.1.2
npm: 5.0.3
os: win32 x64
angular/animations: 4.2.4
angular/common: 4.2.4
angular/compiler: 4.2.4
angular/core: 4.2.4
angular/forms: 4.2.4
angular/http: 4.2.4
angular/platform-browser: 4.2.4
angular/platform-browser-dynamic: 4.2.4
angular/router: 4.2.4
angular/compiler-cli: 4.2.4
angular/language-service: 4.2.4

Hey @IttiwatNir seems like an issue with flex-layout that is causing this issue, could you please do the following within your project directory:
rm -rf node_modules
npm cache clean
npm i @swimlane/ngx-ui --S


[DOC] Add NGC references back to README

Report needed documentation
We removed the NGC references from the getting started section temporarily as to avoid confusion on the multiple paths to get started. The removed link directed users here: https://catalog.ngc.nvidia.com/orgs/nvidia/teams/morpheus/collections/morpheus_. This is where a user would go if they want to use Helm charts to run Morpheus in a K8s environment.
Describe the documentation you'd like
This link and wording around it should be added back into the README.md file once we can decide on the wording to avoid potential confusion with users mixing and matching paths to get started.

To be clear, this issue should separate the documentation pieces that should be seen only after release from the pieces that are seen during development. This means:

Remove all references of NGC and pre-built containers from the root README
Add the NGC references to the root of the docs/index.rst
Add a link to NGC in each of the releases pages
Ensure all version numbers match in the repo


Support Quilt (server software / mod-loader) for auto-updating

Importance: 5/10
Problem:
Can not auto update/download quilt mod loader
https://quiltmc.org/
Solution:
Implement auto-updating quilt to AutoPlug

I am working on it.

Quilt's dead

Quilt is alive as far as I can tell, but this would have to be implemented into the MCServerUpdater library and is hard since differently from Fabric, it has an additional JAR that actually downloads the final server JAR.


Format tags ignore permission checks

It appears that format tags are not respecting permissions associated to that tag.
Test with chathcat.tag.color

Test with chathcat.tag.bold

While debugging it looks like the permission checks are building the resolver correctly, but Minimessage renders the tags anyway.

Interesting. Will look into it right away.

Found the problem. We're not using a custom MiniMessage instance but rather the default one.
https://github.com/HelpChat/ChatChat/blob/76e449732f1629e8f43f8b32eb2c7c70631ba2fe/plugin/src/main/java/at/helpch/chatchat/util/MessageProcessor.java#L346-L347
Will make a PR with the fix soon.


Special character ignored in request

Issue and Steps to Reproduce
I use useOidcFetch from @axa-fr/react-oidc to make call to a BE.
When i inser some special character (Eg: #) the character will be removed from url.
I tried to pass the information in options, but the package seems to ignore everything that i put in option,
Version used ^6.25.6

Hi @LucaNitti , do you have more information about your problem?

hi @LucaNitti , I close the issue.
if you have more information or more detail, you can continue to give it so I will reopen it .


Szokeasaurusrex/asyncio ci test failure debugging

Using this PR to debug why some tests are failing in CI

Done testing


Adding packaged torrent-client to POW.

Checking for dependencies required to clear Python 2.7 test environment.

Coverage remained the same at 77.827% when pulling 343ed16d2a58c90317ce2004d06fad3dfde3a7e9 on jaideep-seth:dev into 19c0ee1e8fcb89d3a94136603907740fb7eac748 on openworm:dev.

Hey @mwatts15 , have you ever had the test clear only 3.6 and 3.7 but not 2.7? Have you faced this before and how did you solve? -Thanks!


White space fix for puppet-lint

Just a couple of whitespace fixes for playing nicer with our, and probably others, linters.

Cheers, thank you.


sqlite-storage don't save in .db ?

Hello everyone. I can insert, edit, delete in my .db, but when I will see it in .db folder in /android/app/src/main/assets/example.db, nothing is saved. the emulator create a database temporary ?

The actual database is created elsewhere. Please refer to the documentation. The database provided in the application is used for initializing the target database only. You can figure out the location of the actual database file if you put a breakpoint in your IDE on a line from SQLPlugin file ...

this problem solved ?
because i face same issues like this..


implement and test the streaming mode

The library seems to be working properly for POLLING but is never tested for the streaming mode.
As this sensor is state of the art for usage in weather station or environmental stations support for the streaming mode would enhance its usability.
Waiting until I have the hardware. (added label).

requested a free sample

requested price for a sensor,

No sensor yet, as far as CI testing goes stream mode seems to work.

Got no sensor, and issue exists too long so it will be closed.


improve flow controller

A lot of code cleanup, as well as a fix for #409.

Codecov Report

Merging #413 into master will increase coverage by 0.54%.

@@            Coverage Diff             @@
##           master     #413      +/-   ##
==========================================
+ Coverage    88.9%   89.45%   +0.54%
==========================================
  Files          78       78
  Lines        5119     5118       -1
==========================================
+ Hits         4551     4578      +27
+ Misses        377      356      -21
+ Partials      191      184       -7

Impacted Files
Coverage Δ

flowcontrol/flow_control_manager.go
100% <100%> (+20.97%)
:white_check_mark:

flowcontrol/flow_controller.go
97.65% <97.62%> (+2.84%)
:white_check_mark:

Continue to review full report at Codecov.

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


Rekey - alt_bn128 and poseidon_syscall

Problem
#294 requires new feature gate keys.
Summary of Changes

Rekeys enable_alt_bn128_compression_syscall and enable_poseidon_syscall.
Adds simplify_alt_bn128_syscall_error_codes.

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

Project coverage is 81.9%. Comparing base (e8526f6) to head (81f5ecb).
Report is 18 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #319   +/-   ##
=======================================
  Coverage    81.9%    81.9%
=======================================
  Files         837      837
  Lines      226874   226875    +1
=======================================
+ Hits       185868   185875    +7
+ Misses      41006    41000    -6


Laravel 9.x Shift

This pull request includes the changes for upgrading to Laravel 9.x. Feel free to commit any additional changes to the shift-60142 branch.
Before merging, you need to:

Checkout the shift-60142 branch
Review all pull request comments for additional changes
Run composer update (if the scripts fail, add --no-scripts)
Clear any config, route, or view cache
Thoroughly test your application (no tests?, no CI?)

If you need help with your upgrade, check out the Human Shifts. You may also join the Shifty Coders Slack workspace to level-up your Laravel skills.

:information_source: Laravel 9 moved the resources/lang folder to the top level of the project. While Shift moved and replaced references to this folder, you may have additional references to this folder which need to be updated.

:warning: Laravel 9 transitioned from SwiftMailer to Symfony Mailer. While this transition should be relatively seamless and Shift automates any tedious changes, there are some changes which are not reliably automated.
Dependencies
Some mail providers may require an additional dependency. For example, if you are using Mailgun, then you will need to install the symfony/mailgun-mailer package:
composer require symfony/mailgun-mailer symfony/http-client

For more details on what has changed you may review the Symfony Mailer section of the Upgrade Guide.

:x: Shift could not upgrade the following files since they differed from the default Laravel version. You will need to compare these files against the default Laravel 9 versions and merge any changes:

[ ] public/index.php

:warning: The FILESYSTEM_DRIVER environment variable was renamed to FILESYSTEM_DISK in Laravel 9. Shift did not find this variable referenced in your committed files, but you should review any additional environment configuration and rename this variable.

:warning: Shift upgraded your configuration files by defaulting them and merging your true customizations. These include values which are not changeable through core ENV variables.
You should review this commit for additional customizations or opportunities to use new ENV variables. If you have a lot of customizations, you may undo this commit with git revert a85a3397 and make the config file changes manually.

:information_source: The FILESYSTEM_CLOUD environment variable was removed in a later release of Laravel 8. While you may still use the cloud disk, you are encouraged to configure your own disks.

:information_source: Shift updated your dependencies for Laravel 9. While many of the popular packages are reviewed, you may have to update additional packages in order for your application to be compatible with Laravel 9.
Watch dealing with dependencies for tips on handling any additional package incompatibilities.

:warning: The token driver for API authentication is no longer available. This driver was not very robust and was removed from the documentation. Laravel now recommends using Sanctum.
If you were using the token driver, you may re-add it within your auth.php configuration file, then migrate to Sanctum at your convenience.

:tada: Congratulations, you're now running the latest version of Laravel!
Next, you may optionally run the following Shifts to ensure your application is fully upgraded, adopts the latest Laravel conventions, and easier to maintain in the future:

Upgrade Checker ensures your application is fully upgraded by detecting any outdated code.
Laravel Fixer automatically updates your code to the latest Laravel conventions.
Tests Generator intelligently generates model factories, HTTP Tests, and configuration for your application.
CI Generator intelligently generates CI jobs to lint PHP, check code style, and run tests, including Dusk.

You may also use the Shift Workbench to automate common tasks for maintaining your Laravel and PHP applications.


feat(adaptors): add adaptor for Azure Static Web Apps

What is it?

[x] Feature / enhancement
[ ] Bug
[ ] Docs / tests

Description
This adds an adaptor, a middleware and a starter for Azure Static Web Apps. It also includes documentation how to use the adaptor. Closes #2053
Use cases and why

Deploy Qwik application to Azure Static Web Apps

Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

There is a working demo running here: https://salmon-dune-02a16c603.2.azurestaticapps.net/
Code for the demo is here: https://github.com/derkoe/qwik-swa-demo
This uses a pre-released version of qwik-city in my namespace: https://www.npmjs.com/package/@derkoe/qwik-city

Awesome work!!!


Capture metrics for CPU, bandwidth, browser main thread

As per the meta issue and Uptime UI implementation, we have a requirement for the Synthetics Agent to capture the following additional metrics, so they can be included in the Uptime reporting:

CPU utilization
Network download bandwidth
Browser main thread

I would move this issue to the beats repo, We need to measure the CPU/Bandwidth of the running container and isolate the stats from that.

As discussed in the tech sync:

CPU utilization - is expected to be collected from the host/beat
Network download bandwidth - is expected to be collected from the host/beat
Browser main thread - is expected to be collected from the browser

A future spike may be needed to determine the approach/implementation for getting this data

For CPU utilisation we can use previous work done by APM agents


update module id to name

what

Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
Use bullet points to be concise and to the point.

why

Provide the justifications for the changes (e.g. business case).
Describe why these changes were made (e.g. why do these commits fix the problem?)
Use bullet points to be concise and to the point.

references

Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
Use closes #123, if this PR closes a GitHub issue #123

@deepak7093 could you fill out the pr template?
Why are you making this change?


Reverted the changes in f4bf1f5

Since wfastcgi is no longer actively maintained by Microsoft, HttpPlatformHandler should remain the recommended approach in this article.
It is more common to call this IIS out-of-band module "HttpPlatformHandler", instead of "HttpPlatform". You can find that formal name from IIS documentation like https://www.iis.net/downloads/microsoft/httpplatformhandler.
ASP.NET Core module is irrelevant. People often were confused due to an ambiguous announcement made by ASP.NET Core team. I wrote about that in https://docs.lextudio.com/blog/the-rough-history-of-iis-httpplatformhandler/#the-mist-of-aspnet-core.
HttpPlatformHandler alone can handle Python web apps very well, so there is no need to use an ASP.NET Core specific module (which is also bigger to load into memory due to ASP.NET Core in-process mode).

Thus, in this pull request I reverted all changes made in the earlier commit, and revised HttpPlatformHandler name in references.

@cwebster-99
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off Had a discussion offline about the implications of this change and strictly recommending HttpPlatformHandler for the Python audience.


Add a log for the errors

Log the errors to a file only for that.

All the logs will be in the same file. This file is created by the logging module.


Please add a link to the errata to the README

For some reason, searching for the book title ("Beginning C++ Game Programming") does not work from the Packt support page.  Note that "Beginning C Game Programming" works.
The code downloads and errata page is located at:
https://www.packtpub.com/books/content/support/25367

Hi @tony--
This issue is resolved now. We have updated our website to fix the issue.
Thanks for finding this out.
Regards,


Add add_link to span api/sdk

The specification has recently been updated to add the ability to add span links after span creation.
See:

https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#add-link
https://github.com/open-telemetry/opentelemetry-specification/pull/3678
https://github.com/open-telemetry/opentelemetry-specification/pull/3887

This updates the API and SDK to add this new method.
Note: I am not fully sure how you all are handling additive changes to the API. With Ruby being very permissive with method definitions, I assume shipping everything together is fine.
If you think that could cause an issue (like the API being used with a lower version of the SDK), I'm happy to split this PR into two, so the SDK is shipped first, and the API in another release.

Can you tell me how links added using the add_link method are ignored by Samplers?

SDK samplers, which perform head sampling (not collector samplers, or any other tail sampler) run on span creation. So when add_link is called, the head sampling decision has already been made, and is not reconsidered with the new link.

SDK samplers, which perform head sampling (not collector samplers, or any other tail sampler) run on span creation. ...

Thank you, @dmathieu. This connects the dots!


Forwarded slots don't receive props

Version
3.1.2
Reproduction link
https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IFBhcmVudCBmcm9tICcuL1BhcmVudC52dWUnXG48L3NjcmlwdD5cblxuPHRlbXBsYXRlPlxuXHQ8UGFyZW50PlxuICAgIDx0ZW1wbGF0ZSAjb3B0aW9uPVwieyB2YWx1ZSB9XCI+XG4gICAgXHR7eyB2YWx1ZSB9fSt7eyB2YWx1ZSB9fVxuICAgIDwvdGVtcGxhdGU+XG4gIDwvUGFyZW50PlxuPC90ZW1wbGF0ZT5cblxuIiwiQ2hpbGQudnVlIjoiPHRlbXBsYXRlPlxuXHQ8c2xvdCB2YWx1ZT1cImZvb1wiPjwvc2xvdD5cbjwvdGVtcGxhdGU+IiwiUGFyZW50LnZ1ZSI6IjxzY3JpcHQgc2V0dXA+XG4gIGltcG9ydCBDaGlsZCBmcm9tICcuL0NoaWxkLnZ1ZSdcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+XG4gIDxDaGlsZD5cbiAgICA8c2xvdCBuYW1lPVwib3B0aW9uXCI+PC9zbG90PlxuICA8L0NoaWxkPlxuPC90ZW1wbGF0ZT5cbiJ9
Steps to reproduce
check reproduction
What is expected?
option slot in app.vue should receive props from Child component and render foo+foo
What is actually happening?
Forwarded slots don't receive props from Child component. Take a look at the generated code for Parent component.
 default: _withCtx(() => [
  _renderSlot(_ctx.$slots, "option")
]),

There's a workaround for this issue but I wonder if can be avoided?
<Child>
  <template #default="props">
    <slot v-bind="props" name="option"></slot>
  </template>
</Child>

// Edit: hmm I see it currently works like in vue 2, so I assume changing this would be a breaking change?

<script setup>
  import Child from './Child.vue'
</script>

<template>
  <Child v-slot="{ value }">
    <slot name="option" :value="value"></slot>
  </Child>
</template>


remove check for EKS regions

Description of your changes
Remove the check for EKS regions because it's hard to keep the list updated manually
The AWS API will tell us an error anyway (albeit only during runtime).
Relevant discussion: https://crossplane.slack.com/archives/CEG3T90A1/p1582580141019500?thread_ts=1582578523.016300&cid=CEG3T90A1
Checklist
I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[ ] Updated any relevant documentation, examples, or release notes.
[ ] Updated the dependencies in app.yaml to include any new role permissions.

Thanks @janwillies!


FPS affects physics!

Hello. I have simulation (game plinko) - balls falling down from exact coordinates into baskets. Repeating the same simulation over and over, results are different!
Also, when I slow down time the simulation results become very different.
I made this issue, beause I need same results in multiple simulations using same exact fall coordinates.

Indeed, I experience the same thing.

Indeed, I experience the same effect.

Indeed, I experience the same effect.

And what to do? I need the same results on server and client...

There's a PR all about timing inconsistencies. Regardless, you should fix your timestep to achieve determinism.
https://github.com/liabru/matter-js/pull/777

There's a PR all about timing inconsistencies. Regardless, you should fix your timestep to achieve determinism.
#777

help pls, I quoted reply in #777

Pretty much as @wmike1987 says (thanks!)

I experience the same problem (wich sound to me logical unless you use fixed time step you IMHO cannot get same results), Ifixed it by using fixed time step (see below), this solution may be added as an option of the Engine.update ?
lastFrameTime = frameTime;
frameTime =  Date.now();
let frameDuration = frameTime - lastFrameTime;`
let repeat= Math.floor(frameDuration/maximumFrameInterval);
let  remainingTime = frameDuration%maximumFrameInterval;
frameTime -= remainingTime;
for(var n=0;n<repeat;n++)
{
   Matter.Engine.update(engine, maximumFrameInterval);
}

I experience the same problem (wich sound to me logical unless you use fixed time step you IMHO cannot get same results), Ifixed it by using fixed time step (see below), this solution may be added as an option of the Engine.update ?
lastFrameTime = frameTime;
frameTime =  Date.now();
let frameDuration = frameTime - lastFrameTime;`
let repeat= Math.floor(frameDuration/maximumFrameInterval);
let  remainingTime = frameDuration%maximumFrameInterval;
frameTime -= remainingTime;
for(var n=0;n<repeat;n++)
{
   Matter.Engine.update(engine, maximumFrameInterval);
}

@DzzD good to know that approach is working for you, it's worth trying out branch #777 too if you get chance.
I've got similar prototypes of adaptive fixed timestep for Matter.Runner but none are yet production ready, it is something I'll prioritise though when I get back to #777.

@DzzD good to know that approach is working for you, it's worth trying out branch #777 too if you get chance.
I've got similar prototypes of adaptive fixed timestep for Matter.Runner but none are yet production ready, it is something I'll prioritise though when I get back to #777.

Closing this thread to refer to updates in #702 on this topic, thanks again for the reports here.


Add props to allow for custom CSS styles

Proposal to add inline styles to Modal elements, which will allow for overwriting default style values.
Attempts to fix #7 and allow manual fixes to #10 and #18 by using width: '80%' or any other value for width other than the default 500px. Previously, there was code in modalFactory.js that used a prop titled customStyle that didn't actually exist. This expands on that idea by exposing 3 new props, 1 for each the styles defined individually for each Modal type (modalStyle, backdropStyle and contentStyle).

@yuanyan looks like this first originated in #15, but wasn't documented in the README


Re-introduce #627

Restore #627
The changes originally introduced in hotwired/turbo#627 had some
negative side effects, including a batch of the current Chrome
failures.
To resolve the issues, the diff was reverted by hotwired/turbo#715.
This commit re-introduces the changes proposed in hotwired/turbo#627
with additional test coverage to ensure that the rendering timing plays
nice with Snapshot caching and other existing rendering behavior.
Co-authored-by: Alex Robbin<EMAIL_ADDRESS>

@seanpdoyle what are we missing to reintroduce this change?

@seanpdoyle what are we missing to reintroduce this change?

The implementation needs to be changed so that the test suite passes.
The failures in CI are genuine.

Is this still feasible? My application uses a Spotify audio player iframe, meaning that even with the data-turbo-permanent attribute the iframe is reloaded on page navigation and the user's playback is interrupted. If turbo could use a non-body element as the root node that would solve my problem, since I could move the iframe out of that node.


image optimization doesn't work

I'm using latest version of tf-next.
Building and deploying works just fine, but, images are not displayed at runtime.
Here is the endpoint called: https://xxxxx.example.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fportrait.05e9d5ee.png&w=96&q=75
and here is the response:
"w" parameter (width) of xx is not allowed

I have tried other width values (1 to 1200) and none works.
I find out that allowed values are defined as TF_VARS: https://github.com/milliHQ/terraform-aws-next-js-image-optimization/blob/54409d7349fe90d0a528345330f9a5ff8dd2e9dc/lib/handler.ts#L80-L91
And then, image-optimizer from Pixel just 'pass' the values: https://github.com/milliHQ/pixel/blob/2137f7905ec64f04dba13560b690b327936d2893/packages/core/lib/image-optimizer.ts#L89-L90
And finally, image-optimizer from Vercel just apply rules based on config: https://github.com/vercel/next.js/blob/6b8e499c7bf13914cca92f9da1737d358133ee20/packages/next/server/image-optimizer.ts#L140-L144
However, I saw that next_image module is defined with empty array value:
  next_image_domains      = []
  next_image_image_sizes  = []
  next_image_device_sizes = []

What is the right thing to do here?
Thanks in advance,
Izio.

This might be of use. I noticed that this error is also mentioned in the issues on Next's official repo: https://github.com/vercel/next.js/issues/38225

@michaelchora Rough plan is to add it by this month, but cannot say for sure if it works.


simplify or document how to change the pattern

Changing just the pattern seems kinda complicated for a new or impatient user:
  opts = {
    progress = {
      display = {
        progress_icon = {
          pattern = "clock",
          period = 1,
        },
      },
    },
  },

Why does it need so much nesting? In addition the period has to be specified or it doesn't work.
Wouldn't it be more user friendly to just say:
  opts = {
    pattern = "clock",
  },

Alternatively documenting the example above in the README would be a great help for new users that just want to change the pattern.

Thanks.


add NODE_PATH as default resolve location

What kind of change does this PR introduce?
bugfix
Did you add tests for your changes?
no
If relevant, link to documentation update:
N/A
Summary
Adds $NODE_PATH as default location for modules
Does this PR introduce a breaking change?
No
Other information
fixes #4479

I agree. We should stick to node's and browserify's default resolving behavior as close as possible.

see issue


Added Basic Calculator

New Project - Basic Calculator [GSSoC'23] #2117
Close #2117
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

Please add gssoc label to this one and PR #2016

I have moved it already. Please check again

@pranjay-poddar Please approve this PR.


Move microdata out of translation files. Fixes #536

That's thoughtful. There is lots of coverage in the renderer specs, so maybe just move that to a unit test for this class?

@jcoyne - I'll look to those


LANG-1067: Add a reflection-based variant of DiffBuilder

Coverage decreased (-0.02%) to 93.54% when pulling a3e2bb7f50c08d7bbe24b8bc746d6cc17e7bc851 on PascalSchumacher:add_reflection_diff_builder into 05647d46e9ac2bf674b320e8467616aa72954f3e on apache:master.

Coverage decreased (-0.02%) to 93.646% when pulling 21d4d19fae77703819377630c8cfcc54d01dcc75 on PascalSchumacher:add_reflection_diff_builder into dfd69e038cc7035031d1807c4ade870d2a7e2ece on apache:master.

Coverage decreased (-0.02%) to 93.646% when pulling dc7ab96a56916d854e1061e7ef5c702c0b3f2faa on PascalSchumacher:add_reflection_diff_builder into dfd69e038cc7035031d1807c4ade870d2a7e2ece on apache:master.

https://github.com/apache/commons-lang/commit/011775551ef75d75f81189eb4604fd0f2ed424ba


⚠ Index has degraded performance

In 336c7aa, Index (https://index.ononoki.org) experienced degraded performance:

HTTP code: 200
Response time: 5366 ms

Resolved: Index performance has improved in ffb8eea after 11 minutes.


Connect to Elastic by url

Hello!
I need to connect from Elastalert to ES by url like this https://myserver.org/elastalert/ , is it possible?
Not by host:post
thanks in advance for the answer

ElastAlert is no longer maintained. Please use ElastAlert2 instead.


How does INT constraint work?

argmax
"A number: [N]"
from
'openai/text-ada-001'
where
INT(N)
If for some reason the token with the highest log probability is not an integer, what would LMQL do?

LMQL applies logit masking to force the model to predict a sequence of tokens that correspond to an integer value.
This means, when the model predicts the value of N, during generation we do not allow an arbitrary choice of next token, but limit the set of choices, available to the model, to only those (sub)tokens that correspond to possible integer value. For instance, in the token distribution of the model we would disallow tokens like "four", "hello" and  allow only tokens like "01", "12", "0", etc..
This is done automatically by translating the high-level INT(N) constraint into a token mask, and masking the output distribution accordingly. To learn more about constraints and how they are implemented, be sure to also read the corresponding chapter in the documentation: https://docs.lmql.ai/en/latest/language/constraints.html

As a followup question, with the OpenAI API, it seems like they don't output the distribution (just the top max 5 log probs). What distribution does lmql use then?

For the OpenAI API there is an additional logit_bias parameter (at least for non-Chat models), which allows you to bias the distribution according to the provided constraints.


Funhouse appears to only play 4 tones before running out of timers

We were playing around with the Funhouse from our Ada Box using circuit python.  (We love it by the way).  It seems to only play 4 tones before throwing an exception that "all timers in use.".  The following snippet can be used to demonstrate the error.  Each button press plays one tone for one second.  Even if you wait several seconds between button pushes, it still throws the exception.  We're the latest circuit python 6.
from adafruit_funhouse import FunHouse
import time
funhouse = FunHouse(default_bg=None)

tones = [
    {'f' : 659, 'd' : 1},
    {'f' : 987, 'd' : 1},
    {'f' : 880, 'd' : 1},
    {'f' : 659, 'd' : 1},
    {'f' : 1000, 'd' : 1},
    {'f' : 700, 'd' : 1}
]

current = 0
while True:
    if funhouse.peripherals.button_down :
        t = tones[current]
        funhouse.peripherals.play_tone(t['f'], t['d'])
        current += 1
        if current == len(tones):
            current = 0

@makermelissa My guess would be that the library isn't releasing the timer.
@DarcInc What version of CircuitPython are you running this on? There is a chance that it's an internal bug.

That's certainly possible. I didn't realize it needed to release anything.

I was able to reproduce the issue with both CircuitPython 6.3 and 7.0. The FunHouse library directly calls simpleio's tone() function. It's in a weird while loop thing, but even with that bit commented out, the issue still occurs, so I don't think the issue is in the FunHouse library. I even explicitly tried adding a deinit() call to simpleio and it still held onto the timers, so I am leaning towards this being an internal bug at this point.
@tannewt should I transfer the issue or create a new one on the main CircuitPython repo?

@makermelissa Please test with absolute latest because I think it was fixed by https://github.com/adafruit/circuitpython/pull/4999 and transfer if it is still an issue. Thanks!

Absolute latest worked. Closing this issue because it was fixed by https://github.com/adafruit/circuitpython/pull/4999.


Use SMALLINT if the Spark dataType is ShortType

Now the connector creates Redshift table with INTEGER column if the DataFrame column is short. After this change, the connector creates SMALLINT column.
Note that this change will change the behavior if the DataFrame has ShortType column
The issue was opened long time ago https://github.com/databricks/spark-redshift/issues/401 but not fixed

@aajisaka Thank you for your feature submission. We are currently reviewing this feature.

@aajisaka We have confirmed this is a bug and will address this in an upcoming release.

Thank you @aajisaka for submitting a fix for this issue. I am merging this into the mainline and it will be part of the next release.


Barback unexpectedly "hides" available asset from the transformer causing it to fail

Reproduction (I could not create a smaller one unfortunately):
$ git clone https://github.com/mraleph/irhydra.git
$ git checkout origin/interesting-mode
$ pub get
$ pub build
There would be multiple exceptions inside SASS transformer during build stage. The root cause of those exceptions is that all *.scss files in the project depend on the partial _ui.scss which barback makes unavailable for some reason.

This issue has been moved to dart-lang/barback#57.