Add an editor setting to import resources while unfocused

This can be used to speed up iteration by starting the import process earlier when saving files in the project folder. This also allows getting visual feedback on changes without having to click the editor window, which is useful with multi-monitor setups.
The downside is that this increases idle CPU usage and may steal CPU time from other applications when importing resources, so this is disabled by default.
This needs testing in various workflows, especially 3D ones with large scenes that can take a while to export. We need to make sure Godot doesn't try to import partially written files.

This closes https://github.com/godotengine/godot-proposals/issues/3252.

How will this behave when resources depend on each other? For example a .gltf with external textures. If it starts importing as soon as it sees the first file being added, it will likely fail.

How will this behave when resources depend on each other? For example a .gltf with external textures. If it starts importing as soon as it sees the first file being added, it will likely fail.

I could see this being an issue already with the current import system (if you focus the editor while a large glTF scene with separate textures is being written by a 3D DCC), but this will indeed be a more common occurrence with this setting enabled.
We should probably have a way to reject an import as "postponed" in this case if it doesn't fulfill certainc onditions.

Rebased and tested again, it works as expected. I've changed the reimport timer from 1.0s to 0.5s to make reimporting quicker too.

Thanks!

Is it intended that the periodic scan is also performed when the editor is still in focus?

Is it intended that the periodic scan is also performed when the editor is still in focus?

I don't know. It is possible for an external app to update a resource in the Godot project while the editor is focused. Does this work correctly when the editor is focused currently (when the new setting is disabled)? Ideally, this should always work regardless of this setting.

I am particularly concerned about instances where godot reads an incomplete file while it is being written. A classic example is exporting a large fbx or gltf from blender and then switching to godot before it is finished writing. Except now it could happen at any time.
in godot this can be very dangerous because it could refresh the scene while importing the broken file and lose data


X-HTTP-Method-Override listener

X-HTTP-Method-Override listener feature.
For this issue: https://github.com/zfcampus/zf-apigility/issues/175#issuecomment-241523026

PR for this issue: https://github.com/zfcampus/zf-apigility/issues/175#issuecomment-241523026
Didn't yet implement a solution for connecting the listener. Maybe an optional config param for enabling this listener. I think enabling this listener should be optional, feels not good to connect such a listener by default to the application.
Maybe someone from zf-campus can give some guidance on how they would like to connect it...?

Updated the PR:

Made HttpMethodOverrideListener extend AbstractListenerAggregate
Attached listener depending on x_http_method_override_enabled
Added $xHttpMethodOverrideEnabled to ContentNegotiationOptions (defaults to false);

@Wilt there is already existing module https://github.com/rstgroup/http-method-override

@snapshotpl OK, thanks.
If there is no interest to implement this in Apigility/zf-content-negotiation, then someone can just close and I will delete my PR.

@Wilt I like it, I think will be nice to have this functionality out-of-the-box. 👍

@webimpress Thanks for the feedback.
I changed to prophecy. I don't like the fact that the get method and getHttpOverrideMethods in my test aren't recognized. Is there a workaround?

@Wilt do you mean your IDE doesn't recognize these methods?
You can always add comment /** @var YourClass $variable */ before variable, and if you are using PHPStorm it will be recognized properly.
But then it's not 100% true, because prophecy object is ProphecyInterface, so maybe better if your comment will be:
/** @var YourClass|ProphecyInterface $variable */

Looks great. I think this should be baked into Apigility.

Thanks, @Wilt!

You are very welcome :smiley:


Fix some test failures

There are a few issues with https://github.com/JuliaHealth/KomaMRI.jl/pull/405 I noticed while running tests today. I forgot about the :skipci tag test filter, so I was only running the CPU tests while testing KomaMRICore. It turns out the GPU SimpleMotion and ArbitraryMotion tests were failing as a result of doing away with the custom adapt_storage definitions. However, after adding back the equivalent adapt_storage functions in KomaMetalExt and KomaCUDAExt, these tests pass once again. The other issue was in line 338 in SimulatorCore.jl:
sim_params[precision]
should be:
sim_params["precision"]
Also fixed in this pull request. So with these changes, all 85 of the KomaMRICore tests pass when using CUDA and Metal (still not sure about AMD / oneAPI until #147 )

It turns out my first commit had syntax issues in each of the /ext modules, which caused them not to be loaded ... and then all the GPU tests defaulted back to the CPU which is why they passed (and I did not notice at the time since we use @supress when running tests for the simulate function).
With the last commit, the syntax issues are gone but the tests are back to failing for SimpleMotion and ArbitraryMotion 😭 (at least with Metal, I haven't checked CUDA yet)

Can you share the error? Maybe @pvillacorta can help

I think I fixed the most recent error for ArbitraryMotion - the problem was that I wasn't importing Adapt in the /ext modules, so the adapt_storage functions defined there weren't actually getting called. I'm running the ArbitraryMotion test now and although it's taking a while, it is 73% of the way through and hasn't errored out yet 🤞

Hey, I just uploaded #408, where there is no need of a custom adapt function for ArbitraryMotion. Maybe, once this #406 PR is merged into master, I can merge from master into #408 and see if everything works. It should be easy. Thank you :)

Thanks @pvillacorta , it looks like #408 should simplify the GPU transfer for these MotionModel structs! I was actually able to get the SimpleMotion and ArbitraryMotion GPU tests to pass for CUDA with my latest commit. The main issue was that the tests pass sim_params["precision"] = "f64". Previously, we were using CUDA.cu() to convert structs to the device which always converts to f32 so the Phantom struct ended up being f32 entirely. Now that we are using the adapt_storage functions to the CUDABackend() type which CUDA.jl defines, this is no longer the case, and there end up being type issues since some of the Motion structs were hardcoded to convert to f32. Since these are also part of the Phantom object, the type parameter {T} cannot be different for the Motion field and the other fields. It did work, however, when I got rid of the f32 for NoMotion and SimpleMotion and changed the GPU transfer to just return identical copies of those structs, and left the ArbitraryMotion GPU transfer the same while also getting rid of f32. The only custom adapt logic I still had to define was for the Vector{LinearInterpolator} type to element wise convert to CuArray, MtlArray, etc., but looking at your pull request I don't think this will be necessary for much longer.
Can you take a look at these latest changes and let me know if everything looks good? If possible, I think if possible, it would be preferable to make the MotionModel structs precision-agnostic so they will work with f64 as well and once you are ready to merge your pull request you can simplify a bit further.
The last thing is that for Metal, the SimpleMotion test is still failing. There is no error, but the numbers are off in the final norm comparison. I haven't looked into it deeply yet, but this will also need to be fixed before this PR can be merged.

After talking with Pablo and Carlos, I think we are good to merge for now. There is still the 1 failing SimpleMotion test for Metal, but this appears to due to phase rotation, since:
KomaMRICore.KomaMRIPlots.plot(abs.(signal))
matches the ground truth, and:
KomaMRICore.KomaMRIPlots.plot(imag.(signal))
does not match.
So perhaps something in the SimpleMotion implementation is interacting weirdly with Metal. Although for now, we can keep the :skipci tags for the SimpleMotion and ArbitraryMotion tests since these features are still experimental, and there's a chance these issues will be fixed soon with #408 .


Login-Signing out & refreshing the login page, user is logged in again

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.42-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation:
Action Performed:

Go to https://staging.new.expensify.com/
Using "G", login as gmail user
Tap profile icon
Tap sign out
Now refresh the login page immediately

Expected Result:
Signing out and refreshing the login page, user must not be logged in again.
Actual Result:
Signing out and refreshing the login page, user is logged in again.
The app with infinite loading home page is shown instead of login page on refresh.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/b4751d9d-73f4-45f9-9082-cc76678bd4f4

View all open jobs on GitHub

I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

We think that this bug might be related to #wave9-collect-signup
CC @MitchExpensify

Any ideas on this @francoisl ? Happy to loop into Wave 9

Hm at first glance I don't think it's related to wave9. @hayata-suenaga is this the same thing you were looking into already and asking about here?

No I don't believe this is related to the issue I'm working on
I'm working on an issue where the user is logged out when they're not supposed
The issue described in this issue is happening probably because we're not clearing the auth cookie

Hm, I'm also not able to repro this. Gonna apply the label to have QA include this in the retest rotation, but if we can't repro it and we it's not tied to a wave perhaps we should close.

Issue not reproducible during KI retests. (First week)


build: redirect API to app root in k8s config

Details
Fixed kubernetes redirect to app-root. Based on Slack discussion and also similar to #211 but for Kubernetes
Testing
Tested on our deployment.
Documentation
None
Closing issues
If your changes fix any issue/s, put closes #XXXX in your comment to auto-close it/them.
Credit
Add your credentials to the list of contributors once your pull request was merged.

This change, as it is now, seems fine. It is a hard-wired path, but it is following the specification. It could be documented on how it works and how to change it, but the change itself looks good to me.


[Discussion] Mechanic built-in preload utility function

Context
Some functions need to run slow code (like loading a bigger static file) upfront. This code is currently re-run on every preview, which can make things feel slow and less snappy in the UI.
To solve this the concept of function memoization could be used. Essentially a memoized function creates a cache based on it's input and immediately returns the cache, if its inputs didn't change – for example the useMemo hook in React.
This PR explores the possibilities of adding memoization as a utility to Mechanic. It should serve as a starting point for debate how we want to implement this.
The actual implementation of memoization is fairly simple. The hard part is really: How do we want to expose this function to the users?
Prototypical Solution

Adds mechanicPreload function that is exported from mechanic core
mechanicPreload can be imported into a design function
Users can use mechanicPreload to control what they want to be cached. It is an opt-in performance optimization.
mechanicPreload is modelled after useMemo. It takes a function without arguments and an array of depedencies from the parent scope. Whenever the value of one of the dependencies changes the provided function is run.

const font = await mechanicPreload(async () => await loadOpentypeFont(fontFile), [fontFile]);

Other approaches to memoization
"Default" memoization in functional programming
The above implementation was chosen for the prototype based on the assumption that if people know about memoization they probably know about the way React does it
Traditionally memoization is realized by returning a memoizable function from another function (this sounds more confusing than the code looks):
const fontLoader = makeMemoizableFunction(async (fontFile) => await loadOpentypeFont(fontFile));
const font = await fontLoader(inputs.font);

While personally I find this approach more explicit I'm unsure if this is the right way to expose this functionality as this is deeply tied to functional programming, which probably not all of mechanic's users are super familiar with.
Ideal solution
The ideal solution from a user's perspective would be to not needing to worry about memoization and dependencies at all. Just wrap the things you want to cache inside a preload function and Mechanic will figure out how to cache it.
const font = await mechanicPreload(async () => await loadOpentypeFont(fontFile));

However this is also the hardest to implement. For the above example I can't think of a way for Mechanic to know about the function's dependencies (which it needs to build the cache key) that wouldn't involve some sort of parsing and AST magic. But maybe I'm missing an obvious solution.
TL;DR – I just want to see this in action
Logo Canvas on DSI Logo Maker has been updated to use memoization on the font loading. You can compare this to another design function to see the difference in rendering this makes.

This is really lovely! I only have two small comments:

Are we sure that the mechanicPreload function isn't resettting its memoed objects whenever the design function is run, since the design function is re-run in a completely newly generated iframe?
I'm sold on the function syntax, but I'm wondering about the name. Since it's used in the context of the design function and not before, how about something like just memo? People can always rename in the import if they want.

Once these are taken care of, let's get it in :)

The way it's set up it only resets on page reload. JavaScript modules are singletons by default. By importing it directly from mechanic and not passing it into the handler function we make sure there only ever is one instance of the memoization cache around. The iframe sets up the function initially and then provides a run function that executes the handler with the current values again. So it's not refreshing the page and the memoization function inside the handler still points to the singleton.
Agreed, I'll rename the function and rebase this PR to point to main and then request official review :blush:

Excelllllleeeeent. Let's get it in! And let's remember to have a list of things to document for the docs.


stateSave not working for regex_checkbox

When stateStave option is enabled in Datatables and the regex checkbox is checked, after reload it is unchecked.

#498 Is a related PR for this.

fixed by @misanek in PR 498


what's up with inverness park district, libertyville fpd in response report?

Both were sent, responded, marked done and shipped ...
So why is their status/threads blank on the response report?

Contact for Inverness Park District was listed under "Iverness Park District."
The label was probably later corrected, but the discrepancy between contact and label broke msg.thread_lookup(), which is a contact-based lookup that would have failed when trying to find labels named for the same agency.
ACTION: Corrected spelling of Inverness Park District in Contacts. Should resolve that issue.
TODO: This wasn't the case with Libertyville FPD. Investigation continues ...

Looks like Libertyville FPD is actually Libertyville. Instead of being marked *NA, it was re-labeled Libertyville.
Verifying with Jared and closing.


 See https://www.omim.org/entry/618011

Never mind, this term was recently added.


[DOC] Add how to enable IR debug messages.

Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.
@tqchen @kparzysz-quic

Thank you @zackcquic !


Feature: Add an option to disallow popover from closing when clicked outside of its body

Bug, feature request, or proposal:
Feature Request
What is the expected behaviour?
Have the popover stay opened when the user clicks outside of popover body
What is the current behaviour?
Popover will close when the user clicks anywhere on the page outside the popover.
What are the steps to reproduce?
This is reproducible on the demo page:
https://uixd.co.uk/open-source-software/material-extended/demo/
What is the use-case or motivation for changing an existing behaviour?
mdePopoverCloseOnClick input directive allows popover to stay open when the user clicks inside the popover body. A similar option should be given to have the popover persist to prevent the popover from closing when the user clicks anywhere else. This is especially important when the popover can contain complex forms / buttons etc. to which the users must interact with.

@shuhkla
This feature has just landed in the master, it will require [mdePopoverBackdropCloseOnClick]="false" to be set on the trigger element.


Trouble running examples/custom_message_package on Windows 11

Hi,
I'm running into some trouble running the example message generator.
I managed to set up ROS2 with the following specs for my machine:
OS: Windows 11
CPU Architecture: x86_64
ROS2 Version: Humble
When building the Go message bindings go generate within the greeter directory, I ran into a couple of problems, but most of the time I'm met with an empty message definition. I've properly sourced the ROS2 overlay but somehow the message keeps generating nothing.
Here is a snippet of some commands I've been running. Is there anything out of the ordinary happening here?
C:\Projects\LearnGoRos2Client\rclgo>call C:\dev\ros2_humble\local_setup.bat
"[rti_connext_dds_cmake_module][warning] RTI Connext DDS environment script not found (\resource\scripts\rtisetenv_x64Win64VS2017.bat). RTI Connext DDS will not be available at runtime, unless you already configured PATH manually."
**********************************************************************
** Visual Studio 2019 Developer Command Prompt v16.11.18
** Copyright (c) 2021 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x86_x64'

C:\Projects\LearnGoRos2Client\rclgo>cd examples\custom_message_package\greeting_msgs

C:\Projects\LearnGoRos2Client\rclgo\examples\custom_message_package\greeting_msgs>colcon build
Starting >>> greeting_msgs
--- stderr: greeting_msgs
CMake Warning (dev) at C:/dev/ros2_humble/share/rosidl_generator_py/cmake/rosidl_generator_py_generate_interfaces.cmake:20 (find_package):
  Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
  are removed.  Run "cmake --help-policy CMP0148" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

Call Stack (most recent call first):
  C:/dev/ros2_humble/share/ament_cmake_core/cmake/core/ament_execute_extensions.cmake:48 (include)
  C:/dev/ros2_humble/share/rosidl_cmake/cmake/rosidl_generate_interfaces.cmake:286 (ament_execute_extensions)
  CMakeLists.txt:12 (rosidl_generate_interfaces)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at C:/dev/ros2_humble/share/python_cmake_module/cmake/Modules/FindPythonExtra.cmake:52 (find_package):
  Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
  are removed.  Run "cmake --help-policy CMP0148" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

Call Stack (most recent call first):
  C:/dev/ros2_humble/share/rosidl_generator_py/cmake/rosidl_generator_py_generate_interfaces.cmake:23 (find_package)
  C:/dev/ros2_humble/share/ament_cmake_core/cmake/core/ament_execute_extensions.cmake:48 (include)
  C:/dev/ros2_humble/share/rosidl_cmake/cmake/rosidl_generate_interfaces.cmake:286 (ament_execute_extensions)
  CMakeLists.txt:12 (rosidl_generate_interfaces)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at C:/dev/ros2_humble/share/python_cmake_module/cmake/Modules/FindPythonExtra.cmake:140 (find_package):
  Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
  are removed.  Run "cmake --help-policy CMP0148" for policy details.  Use
  the cmake_policy command to set the policy and suppress this warning.

Call Stack (most recent call first):
  C:/dev/ros2_humble/share/rosidl_generator_py/cmake/rosidl_generator_py_generate_interfaces.cmake:23 (find_package)
  C:/dev/ros2_humble/share/ament_cmake_core/cmake/core/ament_execute_extensions.cmake:48 (include)
  C:/dev/ros2_humble/share/rosidl_cmake/cmake/rosidl_generate_interfaces.cmake:286 (ament_execute_extensions)
  CMakeLists.txt:12 (rosidl_generate_interfaces)
This warning is for project developers.  Use -Wno-dev to suppress it.

---
Finished <<< greeting_msgs [9.42s]

Summary: 1 package finished [9.66s]
  1 package had stderr output: greeting_msgs
WNDPROC return value cannot be converted to LRESULT
TypeError: WPARAM is simple, so must be an int object (got NoneType)

C:\Projects\LearnGoRos2Client\rclgo\examples\custom_message_package\greeting_msgs>.\install\setup.bat
"[rti_connext_dds_cmake_module][warning] RTI Connext DDS environment script not found (\resource\scripts\rtisetenv_x64Win64VS2017.bat). RTI Connext DDS will not be available at runtime, unless you already configured PATH manually."
om/tiiuae/rclgo/cmd/rclgo-gen generate -d msgs
Generating all importer: msgs\msgs.gen.go

C:\Projects\LearnGoRos2Client\rclgo\examples\custom_message_package\greeting_msgs>cd ../greeter

C:\Projects\LearnGoRos2Client\rclgo\examples\custom_message_package\greeter>go generate
go: updates to go.mod needed; to update it:
        go mod tidy

C:\Projects\LearnGoRos2Client\rclgo\examples\custom_message_package\greeter>go generate
Generating all importer: msgs\msgs.gen.go

C:\Projects\LearnGoRos2Client\rclgo\examples\custom_message_package\greeter>go mod tidy
go: finding module for package github.com/tiiuae/rclgo/examples/custom_message_package/greeter/msgs/greeting_msgs/msg
github.com/tiiuae/rclgo/examples/custom_message_package/greeter imports
        github.com/tiiuae/rclgo/examples/custom_message_package/greeter/msgs/greeting_msgs/msg: module github.com/tiiuae/rclgo@latest found (v0.0.0, replaced by ../../..), but does not contain package github.com/tiiuae/rclgo/examples/custom_message_package/greeter/msgs/greeting_msgs/msg

C:\Projects\LearnGoRos2Client\rclgo\examples\custom_message_package\greeter>go run github.com/tiiuae/rclgo/cmd/rclgo-gen generate -d msgs
Generating all importer: msgs\msgs.gen.go

C:\Projects\LearnGoRos2Client\rclgo\examples\custom_message_package\greeter>echo %AMENT_PREFIX_PATH%
C:\Projects\LearnGoRos2Client\rclgo\examples\custom_message_package\greeting_msgs\install\greeting_msgs;C:\dev\ros2_humble

C:\Projects\LearnGoRos2Client\rclgo\examples\custom_message_package\greeter>go run github.com/tiiuae/rclgo/cmd/rclgo-gen generate -d msgs --root-path="%AMENT_PREFIX_PATH%"
Generating all importer: msgs\msgs.gen.go

Also here is the msgs.gen.go file, note that it generates an empty file:
/*
This file is part of rclgo

Copyright © 2021 Technology Innovation Institute, United Arab Emirates

Licensed under the Apache License, Version 2.0 (the "License");
    http://www.apache.org/licenses/LICENSE-2.0
*/

// Code generated by rclgo-gen. DO NOT EDIT.

package msgs

import (
)

Hi, I made some fixes, can you try the newest version?

Hi,
It looks like you've fixed the file generation, nice!
But now I'm running into the same issue as described in issue #12. It looks like the headers of the Windows ROS2 libraries aren't set up properly, or perhaps I'm linking them incorrectly.
The environment setup:
SET GOOS=windows
SET GOARCH=386
SET CGO_ENABLED=1
SET CGO_CFLAGS=-IC:\dev\ros2_humble\include\rosidl_runtime_c -IC:\dev\ros2_humble\include\rcl_action -IC:\dev\ros2_humble\include\action_msgs -IC:\dev\ros2_humble\include\unique_identifier_msgs -IC:\dev\ros2_humble\include\builtin_interfaces -IC:\dev\ros2_humble\include\rosidl_typesupport_interface -IC:\dev\ros2_humble\include\rcl -IC:\dev\ros2_humble\include\rcutils -IC:\dev\ros2_humble\include\rmw -IC:\dev\ros2_humble\include\rcl_yaml_param_parser

SET CGO_LDFLAGS=-LC:\dev\ros2_humble\Lib -Wl,-rpath,li

Compiler: tdm-gcc
Then afterwards I receive the following errors when I go build
..\..\..\pkg\rclgo\action.go:416:12: could not determine kind of name for C.rcl_action_accept_new_goal
..\..\..\pkg\rclgo\action.go:649:9: could not determine kind of name for C.rcl_action_cancel_response_fini
..\..\..\pkg\rclgo\action.go:888:8: could not determine kind of name for C.rcl_action_client_fini
..\..\..\pkg\rclgo\action.go:862:8: could not determine kind of name for C.rcl_action_client_init
..\..\..\pkg\rclgo\action.go:1213:8: could not determine kind of name for C.rcl_action_client_wait_set_get_entities_ready
..\..\..\pkg\rclgo\action.go:535:9: could not determine kind of name for C.rcl_action_expire_goals
..\..\..\pkg\rclgo\action.go:693:8: could not determine kind of name for C.rcl_action_get_goal_status_array
..\..\..\pkg\rclgo\action.go:633:13: could not determine kind of name for C.rcl_action_get_zero_initialized_cancel_response
..\..\..\pkg\rclgo\action.go:829:16: could not determine kind of name for C.rcl_action_get_zero_initialized_client
..\..\..\pkg\rclgo\action.go:110:17: could not determine kind of name for C.rcl_action_get_zero_initialized_goal_info
..\..\..\pkg\rclgo\action.go:691:14: could not determine kind of name for C.rcl_action_get_zero_initialized_goal_status_array
..\..\..\pkg\rclgo\action.go:340:14: could not determine kind of name for C.rcl_action_get_zero_initialized_server

...

cgo:
gcc errors for preamble:
In file included from C:\dev\ros2_humble\include\rcutils/rcutils/allocator.h:28,
                 from C:\dev\ros2_humble\include\rcl/rcl/allocator.h:25,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/types.h:30,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/action_client.h:23,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/rcl_action.h:50,
                 from ..\..\..\pkg\rclgo\action.go:6:
C:\dev\ros2_humble\include\rcutils/rcutils/macros.h:30:29: error: unknown type name '_Check_return_'
   30 | #define RCUTILS_WARN_UNUSED _Check_return_
      |                             ^~~~~~~~~~~~~~
C:\dev\ros2_humble\include\rcutils/rcutils/allocator.h:84:1: note: in expansion of macro 'RCUTILS_WARN_UNUSED'
   84 | RCUTILS_WARN_UNUSED
      | ^~~~~~~~~~~~~~~~~~~
In file included from C:\dev\ros2_humble\include\rcl/rcl/allocator.h:25,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/types.h:30,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/action_client.h:23,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/rcl_action.h:50,
                 from ..\..\..\pkg\rclgo\action.go:6:
C:\dev\ros2_humble\include\rcutils/rcutils/allocator.h:86:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'rcutils_get_zero_initialized_allocator'
   86 | rcutils_get_zero_initialized_allocator(void);
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from C:\dev\ros2_humble\include\rcutils/rcutils/allocator.h:28,
                 from C:\dev\ros2_humble\include\rcl/rcl/allocator.h:25,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/types.h:30,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/action_client.h:23,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/rcl_action.h:50,
                 from ..\..\..\pkg\rclgo\action.go:6:
C:\dev\ros2_humble\include\rcutils/rcutils/macros.h:30:29: error: unknown type name '_Check_return_'
   30 | #define RCUTILS_WARN_UNUSED _Check_return_
      |                             ^~~~~~~~~~~~~~
C:\dev\ros2_humble\include\rcutils/rcutils/allocator.h:107:1: note: in expansion of macro 'RCUTILS_WARN_UNUSED'
  107 | RCUTILS_WARN_UNUSED
      | ^~~~~~~~~~~~~~~~~~~
In file included from C:\dev\ros2_humble\include\rcl/rcl/allocator.h:25,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/types.h:30,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/action_client.h:23,
                 from C:\dev\ros2_humble\include\rcl_action/rcl_action/rcl_action.h:50,
                 from ..\..\..\pkg\rclgo\action.go:6:

...

I'm going to try to run this in Ubuntu instead of Windows, but if you have any other suggestions to try I'm open to them.

It looks like the rclgo greeter example builds properly in Ubuntu 22.04 out of the box with a regular ROS2 install. I'm not sure what else we'd need in Windows to accomplish this, but it seems to be a problem in the ROS2 libraries in Windows.
For the time being though, I'll just use Ubuntu.


Propose-downstream reported as error even it created PR successfully

This is the case when we show an error on the dashboard, but the PR was successfully created:

GitHub status for the release commit:

Dashboard:

Dashboard detail

Final PR:
https://src.fedoraproject.org/rpms/packit/pull-request/379
Logs

2022-09-16 11:47:40.805 logging.py        INFO   File already uploaded: /tmp/packit-dist-git5nmsgp7u/packitos-0.59.1.tar.gz
2022-09-16 11:47:40.808 logging.py        INFO   All sources were already uploaded.
2022-09-16 11:47:40.915 base_git.py       DEBUG  About to add all & commit.
2022-09-16 11:47:41.986 distgit.py        DEBUG  About to force push changes to branch '0.59.1-f37-update' of a fork 'fork' of the dist-git repo.
2022-09-16 11:47:41.987 base_git.py       INFO   Pushing changes to remote 'fork' using refspec '0.59.1-f37-update'.
2022-09-16 11:47:50.478 base_git.py       INFO   Push summary: [new branch]
2022-09-16 11:47:50.479 distgit.py        DEBUG  About to create dist-git pull request from '0.59.1-f37-update' to 'f37'.
2022-09-16 11:48:08.341 distgit.py        INFO   PR created: https://src.fedoraproject.org/rpms/packit/pull-request/379
2022-09-16 11:48:08.341 api.py            INFO   Checking out the original branch main.

Sentry issues around that time:

https://sentry.io/share/issue/b150d978bfe34642bcd06826454a60a5/
https://sentry.io/share/issue/ede7b1c8d9eb41d6b7951f8f0e947d01/
https://sentry.io/share/issue/9aa1663cf13545eb81e3ab73c3d0f5a6/ (probably unrelated)

From a quick look, the problem here is in the try-except block https://github.com/packit/packit-service/blob/main/packit_service/worker/handlers/distgit.py#L256-L312, the scope of try should be smaller, e.g. not cover setting of GH status, because in case of GH outage we fall to the except branch and the error state is set also for non-error propose downstream itself.


Update PPP for Cheryl Toh

Resolves #171

Pull Request Test Coverage Report for Build 285

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.74%

Totals

Change from base Build 284:
0.0%

Covered Lines:
2288

Relevant Lines:
2494

💛  - Coveralls


Adding ability to output numbers

Just wrap in a string?
r.p('5000');

That works for a literal string, but if your dealing with number in a var or JSON you'd have to call obj.number.toString(). I don't think you should have to do that.
If we didn't want to support number types, it fails silently. At the minimum we should have a console.warn message about invalid types.

Ok. Can we add a test for it? Thanks!

Published as v1.3.0


Obtain dy in the solution of an ODE

Is there an easy way to obtain $dy$ besides $y$ in the solution provided by an ODE-Solver?
I'm aware that it's possible to compute $dy$ from the defined ODE. However in my case I'm solving an equation
$A \cdot dy=b$    where     $A = f(t, y),  b = g(t, y)$   to compute $dy$.
Construction $A$ and solving for $dy$ is computationally expensive. Therefor computing $dy$ from $y$ after solving the ODE is quite inefficient. Since $dy$ will be computed anyways to solve the ODE, I was wondering if there is a way to include $dy$ in the solution.

Not really, unfortunately. The places at which you choose to get outputs (as specified by SaveAt) need not in general correspond to the locations at which the ODE solver will make evaluations.

Makes sense. Thanks for the response!


Move confluence docs to GitHub / README

All documentation should be on GitHub and we should sunset confluence docs.

When we do so @jacob (what is your handle?) and @carey (what is your handle) -- can we use my proposed guide?
I am open to changing it, but I want us to make it readable and usable (@manikantanr )
https://github.com/communitybridge/easycla/blob/master/docs/guide-to-user-guide.md

@fayazg this GitHub is where we can track : https://jira.linuxfoundation.org/browse/PG-21  -- outstanding part of that thread is knowing sunsetting time.  Let's put that in the plan against this Issue.

When we do so @jacob (what is your handle?) and @carey (what is your handle) -- can we use my proposed guide?
I am open to changing it, but I want us to make it readable and usable (@manikantanr )
https://github.com/communitybridge/easycla/blob/master/docs/guide-to-user-guide.md

@jpalmerLinuxFoundation

Just checking up on this work

There are alot of docs now ported: https://jira.linuxfoundation.org/browse/PG-21
@jpalmerLinuxFoundation  -- the docs from @CareyLF  are all correct and updated?
When the UX changes, these will need to bel updated as well when the time comes.
LMK then we can hopefully close this.


where to download a old version mxnet R package?

I need mxnet_0.10.1.tar.gz

The code is available here on Github. https://github.com/apache/incubator-mxnet/releases/tag/v0.10.0
I'm not sure about the difference to 0.10.1. Maybe you can try with 0.10.0 first.
Possibly 0.10.1 is just the tip of the https://github.com/apache/incubator-mxnet/commits/v0.10.0-support branch

The code is available here on Github. https://github.com/apache/incubator-mxnet/releases/tag/v0.10.0
I'm not sure about the difference to 0.10.1. Maybe you can try with 0.10.0 first.
Possibly 0.10.1 is just the tip of the https://github.com/apache/incubator-mxnet/commits/v0.10.0-support branch

Thanks, I found a branch of v0.10.0 and I don't know how to download it as an R package (https://github.com/apache/incubator-mxnet/tree/v0.10.0-support/R-package)

You need to follow the build from source instructions:
https://github.com/apache/incubator-mxnet/blob/8713d257cde97a660a459aa8a50a780944cf823c/docs/get_started/build_from_source.md#build-mxnet-from-source
and
https://github.com/apache/incubator-mxnet/blob/8713d257cde97a660a459aa8a50a780944cf823c/docs/get_started/build_from_source.md#build-the-r-package
I'll close the issue for now, but please reopen if there is any problem.
Note though that such old releases don't receive any support / fixes anymore.

I don't have linux system and don't know how to build, is there a mirror website to download  this version R package file (tzr.gz format)?
Much thanks

You can use aws s3 ls --recursive s3://apache-mxnet/R/CRAN/ to list the available pre-built packages. Prebuilt packages for windows and OS X for R 3.4 seem available.

Can you help me download the v0.10.0 packege file for windows for me? I only have windows system and the terminal code is not allowed.

R/CRAN/bin/windows/contrib/3.4/mxnet_0.10.1.zip

https://apache-mxnet.s3-accelerate.dualstack.amazonaws.com/R/CRAN/bin/windows/contrib/3.4/mxnet_0.10.1.zip


[FLINK-19684][Connector][jdbc]  Fix the Jdbc-connector's  'lookup.max-retries' option implementation

What is the purpose of the change
The Jdbc-connector's 'lookup.max-retries' option implementation is different from the meaning.
Brief change log

JdbcRowDataLookupFunction#eval

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency):no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Thank you for your contribution, I just left a min comment.

LGTM

Could you add tests for this? For example, I think setting 'lookup.max-retries=1' can reproduce this problem.

@wuchong, thank you, I add some tests.

@wuchong please review the ITCase,Thank you.

The failed Kafka test is not related to this PR.
Will merge this one.


DBZ-6773 Adding support for new field/header mappings to ExtractNewDocumentState

https://issues.redhat.com/browse/DBZ-6773

@jcechace Applied, thanks


Take into accound IV values on initial transfer

Short Description:
Read pokemon_potential config and take into account when running an initial transfer
Changes:

Read config.pokemon_potential in initial transfer worker and compare with each pokemon.

@OpenPoGo/maintainers

Nice catch, surprised this was overlooked originally.
:+1:

also maybe for the pokemon under the IV & CP limit you could work out CP * IV to figure out the best option to keep.
for examples sake:
if you have 3 x Bulbasaur

90 CP & 80% IV
110 CP & 60% IV
120 CP & 60% IV

calculate CP * IV to decide which one to keep

90 * 0.8 = 72
100 * 0.6 = 60
120 * 0.6 = 72

Keep No.1 as works out better overall (No.3 is just as good based on calculations but No.1 has higher IV which should be priority?)

I think that CP isn't very important running the bot, as you generate so much stardust (and capture plenty of pokemon for the candies)

I agree with @MaxLeiter, I'm much more concerned about IV than CP.

@andythorne think you forgot what branch you're on

ah feck, let me just fix that...

phew, there we go!

@MaxLeiter I blame drinking + approving commits.  They do not go together :P
Anyway, added a comment on something I think you should change.  There might be a better way of handling that, I just used the logic that was already there

Good spot @jtdroste. Updated :)
I've refactored to use @wchill's new event system as well.

👍 looks good to me.


Use psr7 request body instead of parsedBody

According to the PSR-7 spec, the behavior of ServerRequestInterface::parsedBody is only really specified for multipart/form-data and application/x-www-form-urlencoded requests (in which case it should contain the contents of $_POST). With other request types, the parsedBody MAY return an unserialized version of the body, but since it's not really practical to build parsers for all known formats into a http library it should be perfectly acceptable to return nothing. This PR moves the parsing of the json body into parsePsrRequest.

@mwijngaard mind checking if https://github.com/webonyx/graphql-php/pull/598 does not replace this already?

@simPod Yes it would seem so :-). I noticed that after i submitted the PR. But I left mine open as your PR has been open for a long time and this fix seems more trivial so I was hoping it would be merged a little quicker.

I am going to close this as #598 is merged now


Are larger files (videos) truncated?

Is it just me and my test blogs or are videos broken and truncated and only around <10mb size after the download? Was there any size limit for videos previously?
Someone around here who is downloading more videos than I do? I rarely use the application myself right now, so it's hard for me to detect all the issues.
Thanks for any reply.

I don't know what changes tumblr makes to the video files after upload, as I don't back up my own blog, but when I download from other blogs, I get many long videos that are larger than 10MB. 100+MB is not uncommon.

Okay, thanks! That's good to know.
Most of the files I've looked at all seemed to have an improper ending which made me suspicious. I've thought already I've messed up the bandwidth throttling implementation, even though the pictures all seemed to okay. Bandwidth throttling turned out be much more complicated than I thought initially.


Decelerate for traffic lights

Resolves #4

Not Reviewed

Not Reviewed but closing so you can perform your activities.

Merged without review approval using my administrator privileges. The change will be reviewed later on by @jonam85


Automation of publishing plugin-packages

Currently, we have a Github action npm-publish.
Would be great to create support for doing this as well for the plugin-packages.

@ammmze - are you familiar with how to enforce commit messages to be in the required format? I've seen a few github actions (not many seem to handle multiple commits in a PR), and some client-side git hooks (even a sym link to .git/hooks/ since git won't pull the .git/hooks folder if it were committed). Or is it purely just dev diligence and rebasing/amending and force-pushing when needed?

@6utt3rfly Sorry, I haven't had a chance to work on this yet.
I've only implemented it once before in this project I don't use anymore, but I know there are some people still using it. It's using commitlint to lint the commits and it uses husky to manage client side pre-commit hooks and github actions to lint the commits on push.
Here is the commit where I initially added it. Then looks like I added a prompt thing in the next commit. Not sure how much either one of those tools (commitlint and husky) have changed since I implemented it, so what I did there may or may not still work.

Thanks @ammmze - it helped for PR #177!


SDP-11809 Added support of ghcr.io

@alexeysas once you have merged this to main please create a new tag and update the v1 tag to point to your new tag.


Query associations

Ideas for how it would look: https://gist.github.com/paulcsmith/0a511ab3db994e7b43ad48b8e3dba4a2
Blocked by: https://github.com/luckyframework/lucky_record/issues/128

Moving this to "Next" milestone since this can be done using the existing joins methods and #56 once that is done


Add GW1000 driver for ecowitt support

I'm currently migrating my Weewx setup to containers, but I'm lacking the GW1000 driver for my Ecowitt weather station.
I tried mapping it inside the container via volumes, but that was too hard..
I know the interceptor plugin does a similar thing, but I prefer the GW1000 driver.
🗣 Description
Add the GW1000 driver, similar to the already existing mqtt & interceptor plugins

With the release of v5 I've moved away from pre-installing extensions in the container as the migration of the WeeWX project to pip has made library management easier.


Remove comms and ui args from most calls

This PR aims to simplify methods calls by removing the comms and ui parameters, given that the ones assigned to the config singleton will always be used

@aristizabal95 thanks for taking care of this daunting issue! Looks good to me.
also I removed ui/comms from the remaining utils


Adding UpdateSchemaOptions in Upload and Query

@jskeet PTAL. I addressed your comments and changed EnumMap to what I understood you were proposing.
Also LMK if you prefer a specific InvalidFlagsConversion test method (see my answer to your comment).
Thanks!

I feel like I'm probably being daft but I don't think this covers load jobs as well as query jobs? http://googlecloudplatform.github.io/google-cloud-dotnet/docs/Google.Cloud.BigQuery.V2/history.html claims it does but looking at the code for CreateLoadJobOptions.cs I think that was missed (perhaps deliberately?) as part of this PR.
I'm happy to submit a PR for it but it's pretty much just copy paste coding from the work that @amanda-tarafa has already done so maybe not worth me doing?

@DaveTCode when we said that we were covering load jobs we were referring to all the Upload*Options.cs that hold options for uploading data in different formats to tables that might already exist.
Let me check if CreateLoadJobOptions.cs slipped past us and we didn't included changes there when we had to. I will update here once I've checked.

Great! Thanks :) I'd send a patch but frankly I just copy pasted your code around so I don't think there's any point!


Seems that stagehand 1.1.6 has been released but is not tagged

There is no git tag for version 1.1.6 even though it has been pushed to the public pub repository.
Previous versions do seem to have tags.
This leads me to believe there is a CI job or a script that used to do this, it may be pointing to the old repository that used to be under github.com/google.

I did a cursory check under tools/ and couldn't find anything, if there is something I missed that I can update, feel free to point me in the right direction.

Correction - it is indeed tagged. The convention is different. The other tags are prefixed with v, this one is not. Github's UI made this difficult to see, I did not previously think to scroll all the way to the bottom since I saw a convention there. Would it be worth adhering to convention? This is up to the project contributors obviously, it may be that this removal of the prefix was deliberate.
https://github.com/dart-lang/stagehand/tree/1.1.6

Thanks for looking into this. We do indeed have a convention to use "v" (as mentioned in Pushing a new version), and I think that this exception was just an accident.
I'm closing this and will deal with this "v" thing off thread. ;)
cc @kevmoo

Did not notice the wiki before - 👍


How does SyncWithHystory knows store has changes as you dispatch history API like 'push' from react-router-redux

Trying to understand basic usage of history API provided by this module.
Next code is assumed to change route
import { routerMiddleware, push } from 'react-router-redux'
store.dispatch(push('/any_route'))

'push' returns action of @@router/CALL_HISTORY_METHOD type.
routerMiddleware is designed to tell exactly this action type from others and in case of dispatching 'push' it implicitly calls history.push which is clear.
Browser location is changed and app should be notified of it.
In order to notify app 'syncHistoryWithStore' is used. Internally,
history.listen(handleLocationChange) is called which actually listen to store changes using store.subscribe() and in case of location change in store dispatches LOCATION_CHANGED action
Here comes my question.
As our initially dispatched 'push' action is handled by middleware only and only calles history.push, (no reducer handles @@router/CALL_HISTORY_METHOD action except for middleware ) how does store.subscribe handler is called and who changes the store with new location as we just call history. push method?

The middleware/actions and syncHistoryWithStore are really two independent tools provided by this library. You can use one without the other. They don't interact directly at all.
I'd suggest reading through the syncHistoryWithStore code in more detail. The basic gist is that we hook into history.listen to dispatch location changes to the store, and override the returned listen method to listen to store changes instead of history changes. We basically shim in the store in the middle of history's location change events.

@timdorr hello.
Do I understand it right that
unsubscribeFromHistory = history.listen(handleLocationChange)
listens to history change and dispatches 'LOCATION_CHANGE' on history change and then you override
listen method to listen to store instead of history?


[RFC] diffopt/diffexpr: local settings

Sometimes it would be useful to configure local diff options, e.g. "diffopt+=iwhite".
According to the help diffs are bound to the current tab, so it might make sense to allow for tab-local settings here - but tab-local settings do not exist yet.
The next best thing would be to have those be window-local settings, but then the question arises what would be used if those are different across windows being diffed.
It could use the options from the current window then, resulting in potentially different appearance (re-parsing) when changing the window (and the options differ).
What do you think?

Sometimes it would be useful to configure local diff options, e.g.
"diffopt+=iwhite".
According to the help diffs are bound to the current tab, so it might
make sense to allow for tab-local settings here - but tab-local
settings do not exist yet.
The next best thing would be to have those be window-local settings,
but then the question arises what would be used if those are different
across windows being diffed.
It could use the options from the current window then, resulting in
potentially different appearance (re-parsing) when changing the window
(and the options differ).
What do you think?

Tab-local options would be best for this specific case.  It's in the
todo list:
8   Add local options for each tab page?  E.g., 'diffopt' could differ between
tab pages.
However, it's only useful in very few cases.  And would require quite a
bit if work to implement.
We do have tab-local variables.  How about using l:diffopt-option ?
--
I'm not familiar with this proof, but I'm aware of a significant
following of toddlers who believe that peanut butter is the solution
to all of life's problems... 		-- Tim Hammerquist
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

We do have tab-local variables. How about using l:diffopt-option ?

Assuming you mean t:diffopt I think that's good.
t:diffexpr should be handled there then also.

Can't this be handled by a custom plugin and TabEnter autocommands?

Am 07.08.2019 um 00:13 schrieb Daniel Hahler<EMAIL_ADDRESS>We do have tab-local variables. How about using l:diffopt-option ?
Assuming you mean t:diffopt I think that's good.
t:diffexpr should be handled there then also.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Bugfixes and better flow for the welcome page

Updated the Physiqual gem to the current revision.

Fixes the double requests for data when clicking on the overview. This bug was fixed by disabling turbolinks for this one hyperlink.

The welcome page only shows buttons to add information from specific service providers if the user does not already have a token with those service providers.

The button to show the overview is now separate from the buttons to add data from service providers.

Adding data from service providers is now more transparently labeled (has its own heading), which disappears if the user has tokens for all supported service providers.

If the user has only a Google token, but no FitBit token (or vice versa), only the button to add data from FitBit is shown under the "Add data from a service provider" heading.

verder lgtm


NullpointerException on server error

The connector throws an NPE when the server has an error. The connector assumes an exception to have a message and null-checks on that. Should be adjusted.

Has been resolved

Resolved in commit 809dc4c1


Docker image build for v4.1.0-beta4  is failing

Describe the Problem
v4.1.0-beta4 Docker image build is failed with this error:
The headers or library files could not be found for jpeg,
a required dependency when compiling Pillow from source.
Please see the install instructions at:
https://pillow.readthedocs.io/en/latest/installation.html
----------------------------------------
[91mCommand "/usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-uuz803rl/pillow/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-qckm79pm-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-build-uuz803rl/pillow/
[0mThe command '/bin/sh -c pip-3 install kiwisolver==1.0.1 && pip-3 install plotly==4.9.0 && pip-3 install kaleido && pip-3 install pandas && pip-3 install numpy && pip-3 install scipy && pip-3 install PyYAML && pip-3 install psutil && pip-3 install requests && pip-3 install matplotlib && pip-3 install lxml && pip-3 install pymysql && pip-3 install retrying && pip-3 install cython && pip-3 install statsmodels' returned a non-zero code: 1
build hook failed! (1)

Need to fix the build
Expected Behavior
Docker image should be successfully build for all releases
Environment
Describe your runtime environment:
1. Machine: (e.g. HPC name, Linux Workstation, Mac Laptop)
2. OS: (e.g. RedHat Linux, MacOS)
3. Software version number(s)
To Reproduce
Describe the steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
Post relevant sample data following these instructions:
https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee

[ ] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required

Labels

[ ] Select component(s)
[ ] Select priority
[ ] Select requestor(s)

Projects and Milestone

[ ] Select Organization level Project for support of the current coordinated release
[ ] Select Repository level Project for development toward the next official release or add alert: NEED PROJECT ASSIGNMENT label
[ ] Select Milestone as the next bugfix version

Define Related Issue(s)
Consider the impact to the other METplus components.

[ ] METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy

Bugfix Checklist
See the METplus Workflow for details.

[ ] Complete the issue definition above, including the Time Estimate and Funding Source.
[ ] Fork this repository or create a branch of main_<Version>.
Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
[ ] Fix the bug and test your changes.
[ ] Add/update log messages for easier debugging.
[ ] Add/update unit tests.
[ ] Add/update documentation.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into main_<Version>.
Pull request: bugfix <Issue Number> main_<Version> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s) and Linked issues
Select: Organization level software support Project for the current coordinated release
Select: Milestone as the next bugfix version
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Complete the steps above to fix the bug on the develop branch.
Branch name:  bugfix_<Issue Number>_develop_<Description>
Pull request: bugfix <Issue Number> develop <Description>
Select: Reviewer(s) and Linked issues
Select: Repository level development cycle Project for the next official release
Select: Milestone as the next official version
[ ] Close this issue.

some suggestions from stackowerflow:
apt-get install libjpeg-dev zlib1g-dev
pip3 install Pillow
sudo pip install -U setuptools


Added Linear Search Issue#3435

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
yes
Description
Added Linear search algo in kotlin.
(Write your answer here.)
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixes #3435
(Write your answer here.)

hey, @ankitaggarwal23 I had updated the requested changes please have a look at them.

@HarshCasper please merge this. Thank you.


Error: Rendered fewer hooks than expected. This may be caused by an accidental early return statement.

Hello! Nice try. Happy to see this lib built for optimizing render with Proxies.
Assuming you would like to get some feedback, here's one case.
I think the api is fine and it's just an implementation matter.
https://codesandbox.io/s/statery-clicker-game-forked-l67qu?file=/src/App.tsx Click "Toggle".

Yes, this is currently a caveat that I'm not happy about, and as you probably already know, is caused by property accesses to the proxy object invoking React hooks.
The current workaround is to immediately destructure the proxy into the variables you need before using them in expressions (like I'm doing in the example sandbox and the examples in the README), but of course there's an element of surprise to this that I'm not fond of, and do want to fix. I'm just still thinking about how to do it nicely.

Fixed in the upcoming 0.4.0 release.

The latest code 05e3452ffda65ae9555655837f9352c22a7d4f14 looks pretty clean.
You might want to use Set() as well for listeners which would reduce the bundle size.


chore(main): release 0.6.0

:robot: I have created a release beep boop
0.6.0 (2023-12-13)
Features

day12 completed (f63bbf8)
day13 completed (aeb16e1)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fretboarder/aoc23/releases/tag/v0.6.0 :sunflower:


Header and footer images not found or not readable

Hi,
I'm facing this issue after upgrading from asciidoctor-pdf-1.5.0.alpha.17 to asciidoctor-pdf-1.5.0.beta.2.
$ gem install asciidoctor-pdf -v 1.5.0.alpha.17
Successfully installed asciidoctor-pdf-1.5.0.alpha.17
Parsing documentation for asciidoctor-pdf-1.5.0.alpha.17
Installing ri documentation for asciidoctor-pdf-1.5.0.alpha.17
Done installing documentation for asciidoctor-pdf after 2 seconds
1 gem installed

$ asciidoctor-pdf -v
Asciidoctor PDF 1.5.0.alpha.17 using Asciidoctor 2.0.10 [https://asciidoctor.org]
Runtime Environment (ruby 2.5.5p157 (2019-03-15 revision 67260) [x64-mingw32]) (lc:CP850 fs:Windows-1252 in:UTF-8 ex:UTF-8)

$ asciidoctor-pdf ./header-footer-image-test.adoc -o ./header-footer-image-test-1.5.0.alpha.17.pdf

$ gem update asciidoctor-pdf
Updating installed gems
Updating asciidoctor-pdf
Successfully installed asciidoctor-pdf-1.5.0.beta.2
Parsing documentation for asciidoctor-pdf-1.5.0.beta.2
Installing ri documentation for asciidoctor-pdf-1.5.0.beta.2
Installing darkfish documentation for asciidoctor-pdf-1.5.0.beta.2
Done installing documentation for asciidoctor-pdf after 4 seconds
Parsing documentation for asciidoctor-pdf-1.5.0.beta.2
Done installing documentation for asciidoctor-pdf after 1 seconds
Gems updated: asciidoctor-pdf

$ asciidoctor-pdf -v
Asciidoctor PDF 1.5.0.beta.2 using Asciidoctor 2.0.10 [https://asciidoctor.org]
Runtime Environment (ruby 2.5.5p157 (2019-03-15 revision 67260) [x64-mingw32]) (lc:CP850 fs:Windows-1252 in:UTF-8 ex:UTF-8)

$ asciidoctor-pdf ./header-footer-image-test.adoc -o ./header-footer-image-test-1.5.0.beta.2.pdf
asciidoctor: WARNING: image to embed not found or not readable: <PATH_TO_ROOT_DIR>/styles/pdf/logo.svg
asciidoctor: WARNING: image to embed not found or not readable: <PATH_TO_ROOT_DIR>/styles/pdf/test.svg

Sources and output files attached.
header-footer-image-test-1.5.0.zip
It looks like this behavior has been around since asciidoctor-pdf-1.5.0.alpha.18.
Could you please have a look at it? Thank you.
Regards

Images in the theme file are resolved relative to pdf-themesdir (which is the directory where the theme file is located). This was unclear before and was fixed going into beta. In your case, the image references in the theme file need to be as follows:
image:../../images/test.svg[width=25]

(Or you can move the images into the themes folder, which is where they should be located).
We could consider adding support for the docdir and/or docimagesdir attribute references in the theme to reference locations relative to the current document. This could be related to #588.

Images in the theme file are now resolved consistently (always relative to pdf-themesdir).
I'll file a separate issue to make the docdir (or docimagesdir) attributes available to the theme.

Thanks Dan for the clarification and the proposed enhancement.
TODO update the Theming Guide.

I've already documented it here: https://github.com/asciidoctor/asciidoctor-pdf/blob/master/docs/theming-guide.adoc#images

Yes, sorry, I was looking for it here : https://github.com/asciidoctor/asciidoctor-pdf/blob/master/docs/theming-guide.adoc#images-1

I went ahead and added the info there too.


[WPF] Renderer support for TextBlock headings

From @golddove  in #5626: "NET WPF doesn't support HeadingLevel on AutomationProperties (see: dotnet/wpf#1825), unlike UWP XAML."
Moving this our of 21.03 and marking blocked.


Refactor embeddable element specs

As the behavior of the specs is identical, we can move most of the logic into a shared context.

+1

+1 Interesting concept this shared_context... I wonder if it is available for use with chefspec and if we could make any use of it.

@ifosch this is a part of rspec-core, so I guess it should be available...
See https://relishapp.com/rspec/rspec-core/docs/example-groups/shared-context


Touch does not work after returning with edge swiping gesture of CupertinoPageRoute.

Run this.

import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

void main() => runApp(Root());

class Root extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(home: First());
  }
}

class First extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('First'),
      ),
      body: Center(
        child: RaisedButton(
          child: const Text('Go To Second'),
          onPressed: () {
            Navigator.of(context).push(
              CupertinoPageRoute(
                builder: (BuildContext context) {
                  return Second();
                },
              ),
            );
          },
        ),
      ),
    );
  }
}

class Second extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('Second'),
      ),
      body: Container(),
    );
  }
}

Tap Go To Second button to go Second screen.

Pop Second screen with back button of appBar.

It's OK, no problem.

Tap Go To Second again.

Pop Second screen with edge swipe gesture.

You can see that the Go To Second button cannot be touched.

$ flutter doctor -v
[✓] Flutter (Channel master, v1.10.6-pre.29, on Mac OS X 10.13.6 17G8030, locale ja-JP)
    • Flutter version 1.10.6-pre.29 at /buildroot/flutter
    • Framework revision 919cc97f6a (15 hours ago), 2019-09-20 14:57:05 -0700
    • Engine revision 99092a0436
    • Dart version 2.6.0 (build 2.6.0-dev.0.0 7c1821c4aa)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/yuichi/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • CocoaPods version 1.7.5

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

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 39.0.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

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

[✓] Connected device (4 available)
    • Android SDK built for x86 • emulator-5554 • android-x86    • Android 9 (API 28) (emulator)
    • macOS                     • macOS         • darwin-x64     • Mac OS X 10.13.6 17G8030
    • Chrome                    • chrome        • web-javascript • Google Chrome 77.0.3865.90
    • Server                    • web           • web-javascript • Flutter Tools

• No issues found!

It's no problem on the stable channel:

[✓] Flutter (Channel stable, v1.9.1+hotfix.2, on Mac OS X 10.13.6 17G8030, locale ja-JP)
    • Flutter version 1.9.1+hotfix.2 at /buildroot/flutter
    • Framework revision 2d2a1ffec9 (2 weeks ago), 2019-09-06 18:39:49 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

I have noticed that it will be possible to touch again when it is re-laid out by rotating the screen or other operation (by ui.window.onMetricsChanged() and so on) after the  swipe animation.

+1

+1 had to change channel to dev because another issue that crashes android side when importing:
"io.flutter.embedding.android.FlutterActivity"
now we run into this bug.

@HansMuller for triage.

pushNamed() and pushReplacementNamed() still works as expected.

CC @LongCatIsLooong
I believe we've already been looking at a similar issue.

I can reproduce the problem. I believe it was introduced in https://github.com/flutter/flutter/pull/40466. Working on a fix now.

#41141 reverts the change that caused the bug and #41150 fixes it.  If all goes well, I will just land #41150. Just waiting for a green build window.


Wanna Books

build_your_own_website_the_right_way_using_html_css_3rd_edition.pdf
build_your_own_web_site_2nd_edition.pdf
creating_a_website_the_missing_manual_3rd_edition.pdf
python_3_web_development.pdf
python_web_development_with_django.pdf
learning_python_5th_edition.pdf

my email<EMAIL_ADDRESS>thank you :-)

@lanpong email sent.


In normal mode copy and open the "$" motion doesn't work.

Contour Terminal version
Contour Terminal Emulator 0.4.2-master-f73c3235
Installer source
Github: source code cloned
Operating System
Ubuntu 22.04
Architecture
x86-64
Other Software
No response
Steps to reproduce
Get into normal mode and try to open (o$) or yank (y$) to the end of the line. Note, that I'm on Hungarian keyboard so my $ is accessed via AltGr-é.
Expected Behavior
Copy or open happens.
Actual Behavior
Nothing happens.
Additional notes
The movement itself works, so $ goes to the end of the line.

@ferdinandyb would you mind running contour the following way?:
contour debug gui.input,vt.input

Reproduce the above in a most minimal way, then copy'n'paste the debug output in here.
I think it's not necessarily a vi input issue but rather a keyboard layout mapping issue, how characters are received from the GUI and then passed to the backend.

Here are the logs:
https://0x0.st/HD0J.debug
I selected a previous command from history to echo some characters, opened normal mode, went up to the output of the echo and pressed y$. This should be the relevant part:
[2024-02-03 14:30:35.592635171.592634] [gui.input] Key Release event received:  UpArrow
[2024-02-03 14:30:37.467588312.467588] [gui.input] Character Press event received:  'y'
[2024-02-03 14:30:37.467635762.467635] [vt.input] Incomplete input: y
[2024-02-03 14:30:37.568359621.568359] [gui.input] Character Release event received:  'y'
[2024-02-03 14:30:37.574636563.574636] [gui.input] Input not handled for mods  key 0x1001103
[2024-02-03 14:30:37.629425616.629425] [gui.input] Character Press event received:  '$'
[2024-02-03 14:30:37.629484125.629483] [vt.input] Invalid command: y$
[2024-02-03 14:30:37.629497966.629497] [vt.input] Resetting pending input: y$
[2024-02-03 14:30:37.723124675.723124] [gui.input] Input not handled for mods  key 0x1001103
[2024-02-03 14:30:37.740029145.740028] [gui.input] Character Release event received:  '\xc3\xa9'
[2024-02-03 14:30:41.852474124.852473] [gui.input] Character Press event received:  'i'

So i think that we do not implement this motion in normal mode, you can get same behavior if will switch to visual mode first and then $y


Feature extraction and representation

Hi,
I'm trying to recreate the results from this paper for a university project with a different dataset. However, this repostitory provides only the saved label predictions and some raw features. Is it possible to provide the code that was used to extract features (IDT, micro-expressions, etc.) from the videos?
Thanks!

Hi,
I'm trying to recreate the results from this paper for a university project with a different dataset. However, this repostitory provides only the saved label predictions and some raw features. Is it possible to provide the code that was used to extract features (IDT, micro-expressions, etc.) from the videos?
Thanks!

I'm interested too


[Microsoft.AzureStackHCI] update for 2022-12-15-preview api-version

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.

@pathuang-sia can you please fix the test? and when do you like to release this new sdk?

Closing this PR as breaking change committee suggested skipping sdk generation for this api-version. We will submit a new request when 2023-09-01 api-version has been merged to main for Microsoft.AzureStackHCI


Fixing missing messages.json file

LGTM!

Coverage remained the same at 70.161% when pulling afc51cd24fb9b86a8acfb88f6decd9d801a4e4b0 on mistercrunch:fix_translations into ef59b6b6508d29588931755d22023b845ced8712 on apache:master.

Coverage remained the same at 70.161% when pulling afc51cd24fb9b86a8acfb88f6decd9d801a4e4b0 on mistercrunch:fix_translations into ef59b6b6508d29588931755d22023b845ced8712 on apache:master.