Fix options extraction for Facter::Core::Execution.execute

The documentation of Facter::Core::Execution.execute indicate that the
options hash accept 3 values (expand is not documented):

on_fail
logger
time_limit

However, when options are extracted by the extract_options method, the
key limit is checked instead of time_limit as documented.
Assume the documentation is right and the implementation is wrong, and
fix the latter.

Can one of the admins verify this patch?

The issue was spotted and reported by @johanfleury.

This is a bit embarrassing... it looks like on Facter 3 the option was called timeout: https://github.com/puppetlabs/facter/blob/3.x/lib/src/ruby/module.cc#L959
I'm not sure how limit and time_limit came to be. I think it would be best if we updated the documentation and code to refer to timeout as the correct parameter, to make it easier for folks who upgrade from Facter 3.

See also #2428

@johanfleury Ah, I missed your PR!  I am not sure about the syntax you used to alter the docstrings to document each value… and I can't find a properly generated doc… rdoc might not be the right tool?
As requested @GabrielNagy I used timeout everywhere, added backward compatibility with the documented key and the actual key, and added a warning in case of unexpected key.

Thanks a lot @smortex and @johanfleury! A couple more things:

we should file a ticket for this change; otherwise it won't get in the release notes: https://tickets.puppetlabs.com/ under the FACT project
commit(s) should be updated with the ticket ID instead of (maint)
it would be ideal to have some unit tests for the warn on unexpected key behavior (as the behavior of timeout is already tested in acceptance) - unfortunately it seems that there are no unit tests at all for this class; I can help with this if you want, just let me know

@johanfleury Ah, I missed your PR! I am not sure about the syntax you used to alter the docstrings to document each value… and I can't find a properly generated doc… rdoc might not be the right tool?

My understanding is that they use yard.


Nucleo-H563ZI with NSH configuration

Created stm32h5 directory to add support for the H5 chip, and used a Nucleo-H563ZI dev board during development. The goal was to get a working nutshell through the STLink connector on the board.
Code contained in PR was written in collaboration with @kywwilson11.
Note: Please adhere to Contributing Guidelines.
Summary
There has not been support for STM32H5 chips, so this should provide a starting point for further development. Being able to get to a nutshell on a dev board seems like a good first step.
Impact
Testing
Testing was done by building the configuration, programming the board and seeing the characters printed during start, followed by nsh> working.
OS: Ubuntu 24.04 (Running in WSL2 on Windows 11)
Compiler: arm-none-eabi-gcc (15:13.2.rel1-2) 13.2.1 20231009
Target:

Arch: STM32H5
Chip: STM32H563ZIT6U
Board: Nucleo-H563ZI
Config: nucleo-h563zi:nsh config (added by this PR)

If this PR needs to be broken up into smaller components, please advise on what components would make the most sense as the first step in the process.

@stbenn there is not fixed rule. You can create an initial commit that add the new arch with the headers files, then the peripherals and later on the board support

@acassis Would you suggest closing this PR to do that then? The main reason this PR was so large is because we wanted to get the H5 to a point you could actually do something with it (nutshell).

@acassis Would you suggest closing this PR to do that then? The main reason this PR was so large is because we wanted to get the H5 to a point you could actually do something with it (nutshell).

It is up to you, it is possible to create new commit and use git push forced to update your PR

Thank you @stbenn !! Great work, and most welcome! However, as @acassis mentioned it is better to include this kind of change in small parts, so we can test integration step by step and pinpoint / fix possible problems that arise during build on various platforms and configurations :-)

On the other hand if all builds and works fine splitting that big change is a lot of additional work and may result in additional problems :-P


show_viewport_deferred on web cause not able to change theme.

Describe the bug
If I use show_viewport_deferred on web cause not able to change theme.
Native is able to.
To Reproduce
Steps to reproduce the behavior:

Expected behavior

Screenshots

Desktop (please complete the following information):

OS:
Browser
Version

Smartphone (please complete the following information):

Device:
OS:
Browser
Version

Additional context

I'm sorry. I was crazy.


X-Hub-Signature does not match blob signature

I did everything what said in Developing an App guide, but I'm getting this X-Hub-Signature does not match blob signature error:
Error: X-Hub-Signature does not match blob signature
      at EventSource.events.addEventListener (/Users/denysdovhan/...bot/node_modules/probot/lib/webhook-proxy.js:25:19)
      at EventSource.emit (events.js:160:13)
      at _emit (/Users/denysdovhan/...bot/node_modules/eventsource/lib/eventsource.js:222:17)
      at parseEventStreamLine (/Users/denysdovhan/...bot/node_modules/eventsource/lib/eventsource.js:237:9)
      at IncomingMessage.<anonymous> (/Users/denysdovhan/...bot/node_modules/eventsource/lib/eventsource.js:200:11)
      at IncomingMessage.emit (events.js:160:13)
      at addChunk (_stream_readable.js:269:12)
      at readableAddChunk (_stream_readable.js:256:11)
      at IncomingMessage.Readable.push (_stream_readable.js:213:10)
      at HTTPParser.parserOnBody (_http_common.js:139:22)
      at TLSSocket.socketOnData (_http_client.js:439:20)
      at TLSSocket.emit (events.js:160:13)
      at addChunk (_stream_readable.js:269:12)
      at readableAddChunk (_stream_readable.js:256:11)
      at TLSSocket.Readable.push (_stream_readable.js:213:10)
      at TLSWrap.onread (net.js:599:20)

Can anyone help to resolve this problem?

@denysdovhan :wave: this is a confusing error, but it basically means that the WEBHOOK_SECRET in you .env file does not match the secret configured for the GitHub App. Go into the settings for your GitHub App and update the secret to whatever you have configured in .env and it should fix it. Let me know if it doesn't.

It does! Huge thank you!
P.S: Maybe there's a reason to cover it in docs. Also, it looks like the website is a bit outdated: content is not the same as in repo.

Maybe there's a reason to cover it in docs

Better still, working on it in #434. Thanks for the report, this was the last kick in the butt I needed to finally do this 🎉

Actually, probot is a very interesting project. I'm surprised almost nobody heard about it. I'll try to build a bot for the needs of my project and if my experience will be successful, I'm definitely going to write some articles or make talk about probot.
It seems like a good way for extending GitHub's functionality.


Does FuckAdBlock work on mobile?

Does V4 work on mobile? Are there any examples?

Yes, it's here: https://fuckadblock.sitexw.fr/beta/

Fuckadblock

Unfortunately, yes


reworked lcddisplay, now working with charcreation

comments to webpage:
Fritzing collor of 5v is red not yellow

example for 4 line display is missing

example on how to create special characters is missing, also a link to the web site, to create this characters is missing


Crashes with "trace trap"

System Details

OS: Ubuntu 24.04
Thorium-Raspi Version: M126.0.6478.246

Problem
Crashes immediately on running.
Terminal:
sudo dpkg -i thorium-browser_126.0.6478.246_arm64.deb
thorium-browser
[1] 9056 trace trap thorium-browser
I also tried the zipped version (thorium-browser_126.0.6478.246_arm64.zip).  It produces the same error.
I reverted back to version 124, which does not have any problems.
Regards,
Daniel

@dbonner Dang. I'll be honest I didn't test this release on a real Pi like I usually do

Experienced the exact same problem  (RPi 5 with Debian 12), both with deb and zip upgrades from version 124, and with clean install. Also reverted back to version 124 for the time being. A fix would be much appreciated, thank you for your good work!
Kind regards, Pieter

@dbonner @wegweisernl Unfortunately, its very hard to debug on arm64, since you can't do much on the pi besides GDB
So I end up just "trying things", rebuilding, and retesting until it runs lol.
If they would do the work to allow native compilation and debugging on arm64, it would make it easier.
Currently, x64 is the only supported build platform. Building for x86, arm32, arm64, powerPC, or RISC-V requires cross compiling

Hi @Alex313031 and @wegweisernl,
I could only find one other person who is building Chromium for arm64. I don't know if it would help to look at their website: https://xtradeb.net/
All the best, Daniel (@dbonner)

Following, because I'm using Thorium as the only Chromium browser with native H.264 support that runs on ARM64, but the latest release crashes with "trace trap" for me too.

@dbonner @LorDisturbia @wegweisernl Personally tested the new M128 builds and they are working now > https://github.com/Alex313031/Thorium-Raspi/releases/tag/M128.0.6613.194

Thanks! M128.0.6613.194 zip file is working great in Armbian 23.02.2 jammy community, kernel 6.1.11-meson64. Well done sir ☺

Thank you very much! Just installed M128 and it works like a charm.

Issue has been resolved.


Could not resolve com.facebook.react:react-native:0.20.+.

Hello @ekreutz
When I try to generate apk, the error message says:
Could not resolve com.facebook.react:react-native:0.20.+.
   Required by: project :app > project :react-native-barcode-scanner-google

Have any way to update the RN inside the package or other way to fix this?

Complete error message:
\android>gradlew assembleRelease

> Configure project :react-native-barcode-scanner-google
WARNING: Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html
WARNING: The specified Android SDK Build Tools version (23.0.1) is ignored, as it is below the minimum supported version (28.0.3) for Android Gradle Plugin 3.4.2.
Android SDK Build Tools 28.0.3 will be used.
To suppress this warning, remove "buildToolsVersion '23.0.1'" from your build.gradle file, as each version of the Android Gradle Plugin now has a default version of the build tools.

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:compileReleaseJavaWithJavac'.
> Could not resolve all task dependencies for configuration ':app:releaseCompileClasspath'.
   > Could not resolve com.facebook.react:react-native:0.20.+.
     Required by:
         project :app > project :react-native-barcode-scanner-google
      > Failed to list versions for com.facebook.react:react-native.
         > Unable to load Maven meta-data from https://dl.google.com/dl/android/maven2/com/facebook/react/react-native/maven-metadata.xml.
            > Could not get resource 'https://dl.google.com/dl/android/maven2/com/facebook/react/react-native/maven-metadata.xml'.
               > Could not GET 'https://dl.google.com/dl/android/maven2/com/facebook/react/react-native/maven-metadata.xml'.
                  > dl.google.com

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 31s

FIXED:
I'd edited these files to:
\node_modules\react-native-barcode-scanner-google\android\build.gradle:
apply plugin: 'com.android.library'

android {
    compileSdkVersion 28
    buildToolsVersion "28.0.3"

    defaultConfig {
        minSdkVersion 16
        targetSdkVersion 28
        versionCode 1
        versionName "1.0"
    }
}

dependencies {
    compile 'com.google.android.gms:play-services-vision:8.4.0' // 8.1.0 or higher required
    compile 'com.facebook.react:react-native:0.61.1'
}

\node_modules\react-native-barcode-scanner-google\android\src\main\java\com\ekreutz\barcodescanner\BarcodeScannerPackage.java
package com.ekreutz.barcodescanner;

import com.facebook.react.ReactPackage;
import com.facebook.react.bridge.JavaScriptModule;
import com.facebook.react.bridge.NativeModule;
import com.facebook.react.bridge.ReactApplicationContext;
import com.facebook.react.uimanager.ViewManager;

import java.util.Arrays;
import java.util.Collections;
import java.util.List;

public class BarcodeScannerPackage implements ReactPackage {

    private BarcodeScannerManager barcodeScannerManager;

    public BarcodeScannerPackage() {
        barcodeScannerManager = new BarcodeScannerManager();
    }

// commented the next line (@hladf Override) because showed an error during the 'assembleRelease'
    // @Override
    public List<Class<? extends JavaScriptModule>> createJSModules() {
        return Collections.emptyList();
    }


[ISSUE #5390] not to print some useless log in PopReviveService

Make sure set the target branch to develop
What is the purpose of the change
close #5390
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #5391 (cb60377) into develop (e863f48) will decrease coverage by 0.12%.
The diff coverage is 36.25%.

@@              Coverage Diff              @@
##             develop    #5391      +/-   ##
=============================================
- Coverage      43.24%   43.11%   -0.13%
- Complexity      7881     7991     +110
=============================================
  Files           1006     1016      +10
  Lines          70046    71499    +1453
  Branches        9259     9463     +204
=============================================
+ Hits           30290    30829     +539
- Misses         35963    36784     +821
- Partials        3793     3886      +93

Impacted Files
Coverage Δ

...a/org/apache/rocketmq/broker/BrokerController.java
46.71% <0.00%> (+2.84%)
:arrow_up:

...rocketmq/broker/processor/AckMessageProcessor.java
44.64% <0.00%> (-0.41%)
:arrow_down:

...broker/processor/ChangeInvisibleTimeProcessor.java
56.58% <0.00%> (-10.39%)
:arrow_down:

...rocketmq/broker/processor/PopMessageProcessor.java
38.03% <0.00%> (-0.14%)
:arrow_down:

...he/rocketmq/broker/processor/PopReviveService.java
36.14% <0.00%> (-1.59%)
:arrow_down:

.../transaction/queue/TransactionalMessageBridge.java
74.03% <0.00%> (-2.54%)
:arrow_down:

...apache/rocketmq/common/message/MessageDecoder.java
62.70% <ø> (ø)

...ache/rocketmq/common/utils/CleanupPolicyUtils.java
0.00% <0.00%> (ø)

...va/org/apache/rocketmq/namesrv/NamesrvStartup.java
15.83% <0.00%> (-0.14%)
:arrow_down:

...org/apache/rocketmq/store/AppendMessageResult.java
63.63% <0.00%> (-3.04%)
:arrow_down:

... and 50 more

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


Behavior when gradient is undefined at starting point

The initial value and gradient is undefined because the start value is y = 0 and there is 1 / y^2
This could be classified as expected behavior?
Ipopt is able to solve the model.
Uno
julia> using JuMP, AmplNLWriter, Uno_jll

julia> begin
           model = Model() do
               return AmplNLWriter.Optimizer(Uno_jll.amplexe; directory = "/tmp/uno")
           end
           set_attribute(model, "preset", "ipopt")
           set_attribute(model, "linear_solver", "MUMPS")
           @variable(model, x >= 0)
           @variable(model, y >= 0)
           @objective(model, Min, x + y)
           @constraint(model, y >= 1 / (x + 0.1) - 0.5)
           @constraint(model, x >= y^(-2) - 0.5)
           @constraint(model, 4 / (x + y + 0.1) >= 1)
           optimize!(model)
           solution_summary(model)
       end
Model /tmp/uno/model.nl
Options:
- AMPL_write_solution_to_file = yes
- BQPD_kmax = 500
- BQPD_print_subproblem = no
- LP_solver = BQPD
- LS_backtracking_ratio = 0.5
- LS_min_step_length = 5e-7
- LS_scale_duals_with_step_length = yes
- QP_solver = BQPD
- TR_activity_tolerance = 1e-6
- TR_aggressive_decrease_factor = 4
- TR_decrease_factor = 2
- TR_increase_factor = 2
- TR_min_radius = 1e-7
- TR_radius = 10.
- TR_radius_reset_threshold = 1e-4
- armijo_decrease_fraction = 1e-8
- armijo_tolerance = 1e-9
- barrier_damping_factor = 1e-5
- barrier_default_multiplier = 1
- barrier_initial_parameter = 0.1
- barrier_k_epsilon = 10
- barrier_k_mu = 0.2
- barrier_k_sigma = 1e10
- barrier_push_variable_to_interior_k1 = 1e-2
- barrier_push_variable_to_interior_k2 = 1e-2
- barrier_regularization_exponent = 0.25
- barrier_small_direction_factor = 10.
- barrier_smax = 100
- barrier_tau_min = 0.99
- barrier_theta_mu = 1.5
- barrier_update_fraction = 10
- constraint_relaxation_strategy = feasibility_restoration
- convexify_QP = false
- dual_regularization_fraction = 1e-8
- enforce_linear_constraints = no
- filter_beta = 0.99999
- filter_capacity = 50
- filter_fact = 1e4
- filter_gamma = 1e-8
- filter_sufficient_infeasibility_decrease_factor = 0.9
- filter_switching_infeasibility_exponent = 1.1
- filter_type = standard
- filter_ubd = 1e4
- function_scaling_factor = 100
- function_scaling_threshold = 100
- funnel_beta = 0.9999
- funnel_fact = 1.5
- funnel_gamma = 0.001
- funnel_kappa = 0.5
- funnel_require_acceptance_wrt_current_iterate = no
- funnel_ubd = 1.0
- funnel_update_strategy = 1
- globalization_mechanism = LS
- globalization_strategy = waechter_filter_method
- hessian_model = exact
- l1_constraint_violation_coefficient = 1000.
- l1_relaxation_decrease_factor = 10.
- l1_relaxation_epsilon1 = 0.1
- l1_relaxation_epsilon2 = 0.1
- l1_relaxation_fixed_parameter = no
- l1_relaxation_initial_parameter = 1.
- l1_relaxation_residual_small_threshold = 1e-12
- l1_small_duals_threshold = 1e-10
- least_square_multiplier_max_norm = 1e3
- linear_solver = MUMPS
- logger = INFO
- loose_tolerance = 1e-6
- loose_tolerance_consecutive_iteration_threshold = 15
- max_iterations = 2000
- nonmonotone_filter_number_dominated_entries = 3
- primal_regularization_decrease_factor = 3.
- primal_regularization_fast_increase_factor = 100.
- primal_regularization_initial_factor = 1e-4
- primal_regularization_lb = 1e-20
- primal_regularization_slow_increase_factor = 8.
- print_solution = no
- progress_norm = L1
- protect_actual_reduction_against_roundoff = yes
- regularization_failure_threshold = 1e40
- regularization_increase_factor = 2
- regularization_initial_value = 1e-4
- residual_norm = INF
- residual_scaling_threshold = 100.
- scale_functions = yes
- scale_residuals = yes
- sparse_format = COO
- statistics_LS_step_length_column_order = 10
- statistics_SOC_column_order = 9
- statistics_TR_radius_column_order = 10
- statistics_barrier_parameter_column_order = 8
- statistics_complementarity_column_order = 105
- statistics_dual_feasibility_column_order = 102
- statistics_funnel_width_column_order = 25
- statistics_major_column_order = 1
- statistics_minor_column_order = 2
- statistics_objective_column_order = 100
- statistics_penalty_parameter_column_order = 5
- statistics_primal_feasibility_column_order = 101
- statistics_print_header_every_iterations = 15
- statistics_regularization_column_order = 21
- statistics_restoration_phase_column_order = 20
- statistics_stationarity_column_order = 104
- statistics_status_column_order = 200
- statistics_step_norm_column_order = 31
- subproblem = primal_dual_interior_point
- switch_to_optimality_requires_linearized_feasibility = no
- switching_delta = 1
- switching_infeasibility_exponent = 2
- threshold_unsuccessful_attempts = 8
- time_limit = inf
- tolerance = 1e-8
- unbounded_objective_threshold = -1e20
A numerical error was encountered while evaluating a gradient

* Solver : AmplNLWriter

* Status
  Result count       : 0
  Termination status : OTHER_ERROR
  Message from the solver:
  "Error calling the solver. The solver executed normally, but no `.sol` file was created. This usually means that there is an issue with the formulation of your model. Check the solver's logs for details."

* Candidate solution (result #1)
  Primal status      : NO_SOLUTION
  Dual status        : NO_SOLUTION

* Work counters
  Solve time (sec)   : 5.04861e-02

Ipopt
julia> using JuMP, AmplNLWriter, Ipopt_jll

julia> begin
           model = Model() do
               return AmplNLWriter.Optimizer(Ipopt_jll.amplexe; directory = "/tmp/uno")
           end
           @variable(model, x >= 0)
           @variable(model, y >= 0)
           @objective(model, Min, x + y)
           @constraint(model, y >= 1 / (x + 0.1) - 0.5)
           @constraint(model, x >= y^(-2) - 0.5)
           @constraint(model, 4 / (x + y + 0.1) >= 1)
           optimize!(model)
           solution_summary(model)
       end
Ipopt 3.14.16:

******************************************************************************
This program contains Ipopt, a library for large-scale nonlinear optimization.
 Ipopt is released as open source code under the Eclipse Public License (EPL).
         For more information visit https://github.com/coin-or/Ipopt
******************************************************************************

This is Ipopt version 3.14.16, running with linear solver MUMPS 5.7.3.

Number of nonzeros in equality constraint Jacobian...:        0
Number of nonzeros in inequality constraint Jacobian.:        6
Number of nonzeros in Lagrangian Hessian.............:        3

Error in an AMPL evaluation. Run with "halt_on_ampl_error yes" to see details.
Error evaluating Jacobian of inequality constraints at user provided starting point.
  No scaling factors for inequality constraints computed!
Total number of variables............................:        2
                     variables with only lower bounds:        2
                variables with lower and upper bounds:        0
                     variables with only upper bounds:        0
Total number of equality constraints.................:        0
Total number of inequality constraints...............:        3
        inequality constraints with only lower bounds:        3
   inequality constraints with lower and upper bounds:        0
        inequality constraints with only upper bounds:        0

iter    objective    inf_pr   inf_du lg(mu)  ||d||  lg(rg) alpha_du alpha_pr  ls
   0  1.9999980e-02 1.00e+04 1.00e+00  -1.0 0.00e+00    -  0.00e+00 0.00e+00   0
   1  1.2970166e-01 4.44e+03 1.54e+00  -1.0 3.05e+01    -  6.73e-01 1.00e+00h  1
   2  3.3093968e-01 1.97e+03 5.50e+00  -1.0 7.03e-01    -  9.90e-01 1.00e+00h  1
   3  6.7513596e-01 8.68e+02 2.15e+00  -1.0 3.06e+01    -  5.84e-01 1.00e+00h  1
   4  1.1679898e+00 3.54e+02 7.81e-01  -1.0 8.04e+01    -  8.69e-01 1.00e+00h  1
   5  1.5899014e+00 1.25e+02 5.99e-01  -1.0 1.43e+01  -4.0 1.00e+00 1.00e+00h  1
   6  1.1438428e+00 2.23e+00 2.18e+00  -1.0 1.06e+03    -  1.16e-01 1.00e+00h  1
   7  1.0968948e+00 4.12e+00 1.24e+00  -1.0 1.23e+03    -  4.33e-01 3.41e-02H  1
   8  1.2596142e+00 6.00e+00 6.71e-01  -1.0 1.82e+01    -  1.00e+00 6.48e-01h  1
   9  1.5288200e+00 3.26e-01 2.96e-01  -1.0 1.12e+01    -  5.90e-01 1.00e+00f  1
iter    objective    inf_pr   inf_du lg(mu)  ||d||  lg(rg) alpha_du alpha_pr  ls
  10  1.5175081e+00 6.73e-01 5.20e-02  -1.0 1.19e+01    -  1.00e+00 9.39e-01h  1
  11  1.5389696e+00 8.57e-02 2.72e-01  -1.7 1.95e-01    -  9.43e-01 1.00e+00h  1
  12  1.5530770e+00 3.61e-02 4.23e-02  -1.7 2.67e-01    -  1.00e+00 8.88e-01h  1
  13  1.5512281e+00 0.00e+00 1.20e-02  -2.5 3.89e-02    -  1.00e+00 1.00e+00h  1
  14  1.5452320e+00 0.00e+00 5.49e-05  -3.8 1.50e-02    -  1.00e+00 1.00e+00h  1
  15  1.5449761e+00 0.00e+00 5.00e-08  -5.7 6.09e-04    -  1.00e+00 1.00e+00h  1
  16  1.5449724e+00 0.00e+00 1.96e-11  -8.6 6.17e-06    -  1.00e+00 1.00e+00h  1

Number of Iterations....: 16

                                   (scaled)                 (unscaled)
Objective...............:   1.5449723892994804e+00    1.5449723892994804e+00
Dual infeasibility......:   1.9611753075064438e-11    1.9611753075064438e-11
Constraint violation....:   0.0000000000000000e+00    0.0000000000000000e+00
Variable bound violation:   0.0000000000000000e+00    0.0000000000000000e+00
Complementarity.........:   2.5161366532942358e-09    2.5161366532942358e-09
Overall NLP error.......:   2.5161366532942358e-09    2.5161366532942358e-09

Number of objective function evaluations             = 18
Number of objective gradient evaluations             = 17
Number of equality constraint evaluations            = 0
Number of inequality constraint evaluations          = 18
Number of equality constraint Jacobian evaluations   = 0
Number of inequality constraint Jacobian evaluations = 17
Number of Lagrangian Hessian evaluations             = 16
Total seconds in IPOPT                               = 0.007

EXIT: Optimal Solution Found.
* Solver : AmplNLWriter

* Status
  Result count       : 1
  Termination status : LOCALLY_SOLVED
  Message from the solver:
  "Ipopt 3.14.16: Optimal Solution Found"

* Candidate solution (result #1)
  Primal status      : FEASIBLE_POINT
  Dual status        : FEASIBLE_POINT
  Objective value    : 1.54497e+00
  Dual objective value : 1.54497e+00

* Work counters
  Solve time (sec)   : 3.55769e-01

Ah! That's an interesting one :)
Uno's ipopt preset performs function scaling (using the gradients at the initial point), THEN perturbs the primal point such that it doesn't sit at its bounds. IPOPT seems to be doing the opposite (perturb the bounds THEN scale), which makes total sense. But it's the kind of things that are not really documented...
I will implement the same behavior as IPOPT, which should fix the issue.

But it's the kind of things that are not really documented...

Hahahahaha. Yeah. I guess this is why it's helpful to have a fairly comprehensive test suite.
So far, I've run only MINLPTests.jl. Once we fix the dual issue I can run the much larger set of MOI.Test.runtests (I didn't for now, because too many things will fail).


How to create Custom Audioprocessor

Hello team,
I'm working on integrating libraries like SoundTouch and Rubberband for pitch and tempo modifications in ExoPlayer. Initially, I used Sonic (the default in ExoPlayer), but due to quality concerns, I decided to switch to Rubberband/SoundTouch. I've implemented the necessary JNI bridge and created a custom audio processor, using Sonic.java as a reference. While speed and tempo adjustments are working well, I'm facing an issue with looping. Specifically, there's a noticeable delay between the end and the start of the file when looping, which impacts the smoothness of the experience.
I'm trying to understand how ExoPlayer handles looping internally, but I might have missed something in my custom implementation. I’d appreciate any insights or suggestions on what could be causing this issue. If helpful, I can share my CustomAudioProcessor code for further review.
Thanks in advance for your help!
`  class RubberBandAudioProcessor : AudioProcessor {
val SAMPLE_RATE_NO_CHANGE = -1
private val CLOSE_THRESHOLD = 0.0001f

private val MIN_BYTES_FOR_DURATION_SCALING_CALCULATION = 1024

private var pendingOutputSampleRate = 0
private var speed = 1f
private var pitch = 1f

private var pendingInputAudioFormat: AudioProcessor.AudioFormat
private var pendingOutputAudioFormat: AudioProcessor.AudioFormat
private var inputAudioFormat: AudioProcessor.AudioFormat
private var outputAudioFormat: AudioProcessor.AudioFormat

private var pendingSonicRecreation = false
private var rb: RubberBandStretcher? = null
private var buffer: ByteBuffer
private var shortBuffer: ShortBuffer
private var outputBuffer: ByteBuffer
private var inputBytes: Long = 0
private var outputBytes: Long = 0
private var inputEnded = false

init {
    speed = 1f
    pitch = 1f
    pendingInputAudioFormat = AudioProcessor.AudioFormat.NOT_SET
    pendingOutputAudioFormat = AudioProcessor.AudioFormat.NOT_SET
    inputAudioFormat = AudioProcessor.AudioFormat.NOT_SET
    outputAudioFormat = AudioProcessor.AudioFormat.NOT_SET
    buffer = AudioProcessor.EMPTY_BUFFER
    shortBuffer = buffer.asShortBuffer()
    outputBuffer = AudioProcessor.EMPTY_BUFFER
    pendingOutputSampleRate = SAMPLE_RATE_NO_CHANGE
}

fun setSpeed(speed: Float) {
    if (this.speed != speed) {
        this.speed = 1/speed
        rb?.timeRatio = 1/speed.toDouble()
        pendingSonicRecreation = true
    }
}

fun setPitch(pitch: Float) {
    if (this.pitch != pitch) {
        this.pitch = pitch
        rb?.pitchScale=pitch.toDouble()
        pendingSonicRecreation = true
    }
}

fun setOutputSampleRateHz(sampleRateHz: Int) {
    pendingOutputSampleRate = sampleRateHz
}

fun getMediaDuration(playoutDuration: Long): Long {
    return if (outputBytes >= MIN_BYTES_FOR_DURATION_SCALING_CALCULATION) {
        val processedInputBytes = inputBytes - Assertions.checkNotNull(rb).samplesRequired
        if (outputAudioFormat.sampleRate == inputAudioFormat.sampleRate) Util.scaleLargeTimestamp(
            playoutDuration,
            processedInputBytes,
            outputBytes
        ) else Util.scaleLargeTimestamp(
            playoutDuration,
            processedInputBytes * outputAudioFormat.sampleRate,
            outputBytes * inputAudioFormat.sampleRate
        )
    } else {
        (speed.toDouble() * playoutDuration).toLong()
    }
}

@Throws(UnhandledAudioFormatException::class)
override fun configure(inputAudioFormat: AudioProcessor.AudioFormat): AudioProcessor.AudioFormat {
    if (inputAudioFormat.encoding != C.ENCODING_PCM_16BIT) {
        throw UnhandledAudioFormatException(inputAudioFormat)
    }
    val outputSampleRateHz =
        if (pendingOutputSampleRate == SAMPLE_RATE_NO_CHANGE) inputAudioFormat.sampleRate else pendingOutputSampleRate
    pendingInputAudioFormat = inputAudioFormat
    pendingOutputAudioFormat = AudioProcessor.AudioFormat(
        outputSampleRateHz,
        inputAudioFormat.channelCount,
        C.ENCODING_PCM_16BIT
    )

    pendingSonicRecreation = true
    return pendingOutputAudioFormat
}

override fun isActive(): Boolean {
    val outputSampleRate = pendingOutputAudioFormat.sampleRate
    val inputSampleRate = pendingInputAudioFormat.sampleRate
    val speedDifference = abs(speed - 1f)
    val pitchDifference = abs(pitch - 1f)

    val isOutputSampleRateValid = outputSampleRate != Format.NO_VALUE
    val isSpeedChanged = speedDifference >= CLOSE_THRESHOLD
    val isPitchChanged = pitchDifference >= CLOSE_THRESHOLD
    val isSampleRateDifferent = outputSampleRate != inputSampleRate
    return true; // returning true because i want to use this audioprocessor.
    // return (isOutputSampleRateValid
    //         && (isSpeedChanged || isPitchChanged || isSampleRateDifferent))
}

override fun queueInput(inputBuffer: ByteBuffer) {
    if (!inputBuffer.hasRemaining()) {
        return
    }
    val rb = Assertions.checkNotNull(rb)
    val shortBuffer = inputBuffer.asShortBuffer()
    val inputSize = inputBuffer.remaining()
    inputBytes += inputSize.toLong()
    rb.process(shortBuffer, inputAudioFormat.channelCount, false)
    inputBuffer.position(inputBuffer.position() + inputSize)
}

override fun queueEndOfStream() {
    Log.e("RUBBERBANDAUDIOPROCESSOR","QueueEndOfStream");
    if (rb != null) {
        rb!!.queueEndOfStream()
    }
    inputEnded = true
}

override fun getOutput(): ByteBuffer {

    val rb = rb
    val channelCount = inputAudioFormat.channelCount
    val samplesRequired = rb?.samplesRequired
    if (rb != null) {
        val outputSize = rb.available()
        if (outputSize > 0) {
            if (buffer.capacity() < outputSize * channelCount * 2) {
                buffer = ByteBuffer.allocateDirect(outputSize * channelCount * 2)
                    .order(ByteOrder.nativeOrder())
                shortBuffer = buffer.asShortBuffer()
            } else {
                buffer.clear()
                shortBuffer.clear()
            }
            val retrieved = rb.retrieve(shortBuffer, channelCount)
            outputBytes += retrieved.toLong() * channelCount * 2
            buffer.limit(retrieved * channelCount * 2)
            outputBuffer = buffer
        }
    }
    val outputBuffer = outputBuffer
    this.outputBuffer = AudioProcessor.EMPTY_BUFFER
    return outputBuffer
}

override fun isEnded(): Boolean {
    Log.e("inputeEnded", inputEnded.toString())
    Log.e("rb", rb.toString())
    val samplesRequired= rb?.samplesRequired

    Log.e("rb sample required", samplesRequired.toString())

   // return inputEnded && (rb == null || samplesRequired == 0)
    return inputEnded
}

override fun flush() {
    val isAct=isActive();
    Log.e("IsActive", isAct.toString())

    if (isAct) {
        Log.e("pendingSonicRecreation", pendingSonicRecreation.toString()  )
        inputAudioFormat = pendingInputAudioFormat
        outputAudioFormat = pendingOutputAudioFormat
        if (pendingSonicRecreation) {

            rb = RubberBandStretcher(
                inputAudioFormat.sampleRate,
                inputAudioFormat.channelCount,
                RubberBandStretcher.OptionProcessRealTime.or(RubberBandStretcher.OptionEngineFiner).or(RubberBandStretcher.OptionWindowShort).or(RubberBandStretcher.OptionFormantPreserved).or(RubberBandStretcher.OptionPitchHighConsistency),
                speed.toDouble(),
                pitch.toDouble()
            )

        } else if (rb != null) {

            rb!!.reset()
        }
    }
    outputBuffer = AudioProcessor.EMPTY_BUFFER
    inputBytes = 0
    outputBytes = 0
    inputEnded = false
}

override fun reset() {
    speed = 1f
    pitch = 1f
    pendingInputAudioFormat = AudioProcessor.AudioFormat.NOT_SET
    pendingOutputAudioFormat = AudioProcessor.AudioFormat.NOT_SET
    inputAudioFormat = AudioProcessor.AudioFormat.NOT_SET
    outputAudioFormat = AudioProcessor.AudioFormat.NOT_SET
    buffer = AudioProcessor.EMPTY_BUFFER
    shortBuffer = buffer.asShortBuffer()
    outputBuffer = AudioProcessor.EMPTY_BUFFER
    pendingOutputSampleRate = SAMPLE_RATE_NO_CHANGE
    pendingSonicRecreation = false
    rb = null
    inputBytes = 0
    outputBytes = 0
    inputEnded = false
  }

}
`

Specifically, there's a noticeable delay between the end and the start of the file when looping, which impacts the smoothness of the experience.

I can't observe a delay when using the default SonicAudioProcessor for speed adjustments. Could you clarify what kind of delay you are looking at? I assume it's between some method calls in the audio processor?

Reassigning to @tonihei for triage, as this seems more related to looping than audio processors.

Initially, I used Sonic (the default in ExoPlayer), but due to quality concerns, I decided to switch to Rubberband/SoundTouch.

@iamvikashh OOI, would you mind sharing those quality concerns or what did not meet your expectations? Feedback is always welcome :)

Actually, in my use case, I'm working with tabla sound files and adjusting the tempo of these files. The issue arises with certain BPMs—specifically, when I play a 160 BPM tabla file at 145 BPM, I hear a fluttering, echo-like sound that distorts the tabla. Interestingly, this issue only occurs with tabla music. When I tested it with other instruments, like a tanpura sound file, everything sounded fine.

I'm wondering if this issue might be related to how I've implemented the custom processor or if there's something about the way ExoPlayer handles looping with non-default processors.

I'm afraid we can't debug your custom code in detail. I suggest you compare calls and behavior between SonicAudioProcessor and yours to see where they are different and maybe that points to the source of the delay you observed?


WIP: read in 2011 boundaries

Pull Request submission
Insert detailed bullet points about your changes here!
Insert any instructions to help the reviewer, e.g. "install new requirements from requirements.txt"
*Let the reviewer know what data files are needed (to be grabbed from sync)
Closes or fixes
Fixes #
Code

[ ] Requirements My/our code matches the requirements of the ticket
[ ] Functionality: New functions meet requirements in issue ticket
[ ] Compliant Code Code is as PEP 8 compliant as I can humanly make it
[ ] Code runs The code runs on my machine
[ ] Clean Code

[ ] Code has been linted (use your favourite linter)
[ ] Code adheres to DRY

Documentation
Any new code includes all the following forms of documentation:

[ ] Function Documentation Docstrings within the function(s') definition(s) have been created

[ ] Includes parameters and returns for all major functions
[ ] Includes data types

[ ] Updated Documentation: Working doc has been updated and a new ticket to update the master documentation has been created.

Data

[ ] All data needed to run this script has been added to Sync

Testing

[ ] Unit tests Unit tests have been created and are passing or a new ticket to create tests has been created

Peer Review Section

[ ] All requirements install from (updated) requirements.txt
[ ] Documentation has been created and is clear - check the google Doc
[ ] Doctrings (Google format) have been created and accurately describe the function's functionality
[ ] Unit tests pass, or if not present a new ticket to create tests has been created
[ ] Code runs The code runs on reviewer's machine

Final approval (post-review)
The author has responded to my review and made changes to my satisfaction.

[ ] I recommend merging this request.

Review comments
Insert detailed comments here!
These might include, but not exclusively:

bugs that need fixing (does it work as expected? and does it work with other code
that it is likely to interact with?)
alternative methods (could it be written more efficiently or with more clarity?)
documentation improvements (does the documentation reflect how the code actually works?)
additional tests that should be implemented (do the tests effectively assure that it
works correctly?)
code style improvements (could the code be written more clearly?)

Your suggestions should be tailored to the code that you are reviewing.
Be critical and clear, but not mean. Ask questions and set actions.

With thanks to Musa the file OA2011 to LAD2011 lookup is called the Output Area 2011 to Settlements and Localities 2012 Lookup. It can be found here:  https://www.nrscotland.gov.uk/files//geography/2011-census/OA11_to_SettLoc12.xlsx
https://www.nrscotland.gov.uk/statistics-and-data/geography/our-products/census-datasets/2011-census/2011-indexes


fix hash function name according to the spec

Signed-off-by: zaihaoyin<EMAIL_ADDRESS>This PR fixes https://github.com/notaryproject/notation/issues/268.
According to the plugin spec, the hashAlgorithm field of GenerateSignatureRequest should be one of the following strings.
  // Hash algorithm associated with the key spec, plugin must
  // hash the payload using this hash algorithm
  "hashAlgorithm" : "SHA_256" | "SHA_384" | "SHA_512",

However, the current implementation uses crypto.Hash.String(), which will return a string like SHA-256 and break the azure-kv plugin.
Also need to update notation-go and notation to make the plugin works.

Codecov Report

Merging #20 (7629ab8) into main (c435938) will increase coverage by 0.05%.
The diff coverage is 86.66%.

@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
+ Coverage   63.89%   63.95%   +0.05%
==========================================
  Files          23       23
  Lines        1504     1512       +8
==========================================
+ Hits          961      967       +6
- Misses        414      416       +2
  Partials      129      129

Impacted Files
Coverage Δ

signer/types.go
90.90% <85.71%> (-5.10%)
:arrow_down:

signer/utils.go
86.66% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

@chloeyin We still need to change notation-go right? "SHA-256" is actually not following the spec you mentioned above.

@chloeyin We still need to change notation-go right? "SHA-256" is actually not following the spec you mentioned above.

Yes, we need to update notation-go and notation to make the plugin work.

@chloeyin We still need to change notation-go right? "SHA-256" is actually not following the spec you mentioned above.

Yes, we need to update notation-go and notation to make the plugin work.

And with this PR merged, the remaining fix is as simple as psp.keySpec.SignatureAlgorithm().Hash(), just removing the .String().

LGTM

@chloeyin @shizhMSFT, I couldn't review this PR earlier. This isn't the correct fix.
The plugin spec is implemented by notation-go. notation-core-go does not know anything about plugin request/response types, which is where the generate-signature.Request.hashAlgorithm is defined. The fix involves translating hash alg names into ones required by plugin spec.
I'm actually in favor of the plugin spec being updated to use standard hash alg names, so we can avoid any translation at all.
https://github.com/notaryproject/notaryproject/blob/main/specs/plugin-extensibility.md#generate-signature


Invalid difficulty reported

velesd reports incorrect difficulty via getblockchaininfo call.
conf file:
server=1
listen=1
daemon=0
gen=0
rpcthreads=12
dbcache=5
maxconnections=10
deprecatedrpc=accounts
algo=sha256d
samples output of getblockchaininfo:
{"result":{"chain":"main","blocks":269390,"headers":269390,"bestblockhash":"6ceaa8d9e1000d6af7c1f697a62ff57dd5de1c80285281defd275a37e5f7caee","difficulty":3831.391509370843,"mediantime":1574118779,"verificationprogress":1.097842440893784e-05,"initialblockdownload":false,"chainwork":"00000000000000000000000000000000000000000000016d813667f86cc444f5","size_on_disk":224296637,"pruned":false,"softforks":[{"id":"bip34","version":2,"reject":{"status":true}},{"id":"bip66","version":3,"reject":{"status":true}},{"id":"bip65","version":4,"reject":{"status":true}}],"bip9_softforks":{"csv":{"status":"active","startTime":0,"timeout":9223372036854775807,"since":6048},"segwit":{"status":"active","startTime":0,"timeout":9223372036854775807,"since":6048}},"warnings":""},"error":null,"id":"1"}
decoding nBits from getblocktemplate provides accurate difficulty of 28118634.611017339 at the same time.

This is the expected behaviour, the getblockchaininfo command reports the difficuly of the algo that produced the last block found - for example, in the result above the bectblockhash is 6ceaa8d9e1000d6af7c1f697a62ff57dd5de1c80285281defd275a37e5f7caee which is not sha256d hash, so the reported difficulty 3831.391509370843 was the difficulty of the algo that produced said block.

what api call should be used to get the actual diff on the algo then?
should I keep decoding nBits from getblockstemplate to get actual diff every time I need it instead?

You can get actual diff with getmininginfo or with getmultialgostatus

ok, a bit inconvenient, but I can work with that


RTC: fix play crash or no stream for rtmp2rtc tips.(#2728)

If I don't publish stream, SRS will crash.
and if I publish RTC stream, SRS don't distribute RTC stream.
Config as follows:
vhost __defaultVhost__ {
    rtc {
        enabled     on;
        # @see https://github.com/ossrs/srs/wiki/v4_CN_WebRTC#rtmp-to-rtc
        rtmp_to_rtc off;
        # @see https://github.com/ossrs/srs/wiki/v4_CN_WebRTC#rtc-to-rtmp
        rtc_to_rtmp off;
    }
}

Codecov Report

Merging #2863 (f5b601d) into 4.0release (08910e5) will not change coverage.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           4.0release    #2863   +/-   ##
===========================================
  Coverage       60.22%   60.22%
===========================================
  Files             121      121
  Lines           51070    51070
===========================================
  Hits            30756    30756
  Misses          20314    20314

Impacted Files
Coverage Δ

trunk/src/app/srs_app_rtc_api.cpp
0.00% <0.00%> (ø)

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 08910e5...f5b601d. Read the comment docs.


feat(rust): delete secure channel

Current Behavior
Not implemented

Proposed Changes
Implement as described in #3287

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam-contributors repository.

Great, trying out the changes now.

The changes look great. Could you resolve these clippy lints please, then we can merge https://github.com/build-trust/ockam/runs/7926818253?check_suite_focus=true

@Retamogordo thank for fixing the clippy lints. You can ignore the commit check failure .. I'll sign the commit during the merge.
Could you make the change to address this comment please https://github.com/build-trust/ockam/pull/3288#discussion_r950603232

Thank you for another awesome contribution! 🥳 🎈


Fix broken list structure in TOC

Fixes #917 by adding a  for first-level headings.

Whoops, thanks for the catch. Is there any reason we can't just rename the div to a ul?


[INTEL MKL]  Added mkl_einsum op

Added mkl_einsum op Implementation, In addition to   adding mkl_einsum, It also refactors mkl_batch_matmul op.

@vishakha-nervana  Can you please check @kkimdev's comments and keep us posted ? Thanks!

Also, please wait for @penpornk 's review.

@penpornk Please review my PR.I have acknowledged changes.

@penpornk I have made changes as per your request, please let me know if there's any AR for me regarding refactoring.

@penpornk I have made changes as per your request, please let me know if there's any AR for me regarding refactoring.

@vishakha-nervana Can you please resolve conflicts? Thanks!

@vishakha-nervana Any update on this PR? Please. Thanks!

@vishakha-nervana Any update on this PR? Please. Thanks!

I have resolved all the conflicts long, ago @penpornk Is there any change I need to do in this branch?

@vishakha-nervana Can you please address Ubuntu Sanity errors? Thanks!

@vishakha-nervana Can you please address Ubuntu Sanity errors? Thanks!

@gbaned Done.


do async blocks, ir (low-level)

Story
Addresses #1482.
Description
The do-async block, do async <block>, returns a future containing the result of <block>.
Unlike an async expression, do async <block> evaluates <block> synchronously at first,  switching to asynchronous computation only at the first await of a pending future within <block>.
The expression do async <block> has type async T provided

<block> has type T;
the expression occurs in an asynchronous context (i.e. in the body of a (non-query) shared function, asynchronous function, async expression or another do async block).

Do-async blocks can be nested, with the exit of a return or throw determined by lexical scoping.
It is a compile-time error for <block> to contain a break to a label declared outside the do-async block.
The expression do async <block> evaluates by entering the evaluation of <block>, executing synchronously  --  just like a do <block> --
until the first await of a pending future, if any.
Unless evaluation traps, it returns a future holding the actual or eventual result of <block>.
During the synchronous execution of <block>:

a return expression exits the block with a completed future, storing the returned value;
a throw expression resumes execution from the nearest enclosing try ... catch ... handler within <block> or, if there is none, exits the do-async block
with a failed future storing the error;
a trap causes do async <block> to trap;
an await expression of
** a successfully completed future continues execution with the contents of that future, or
** a failed, completed future propagates the error contents of the future as if thrown (see above), or
** a pending future exits the do-async block with a new, pending future whose completion with the result of <block> is suspended, waiting on the result of the awaited future.

NOTE: Evaluation of a do-async block is synchronous while possible, switching to asynchronous when necessary.
By contrast, evaluation of the similar async <block-or-exp> (without do) immediately returns a pending future and always computes the result of <block-or-exp> asynchronously,
never blocking evaluation of the enclosing expression.
NOTE: Do-async blocks are useful for abstracting asynchronous code into re-useable functions, without introducing redundant and expensive async expressions just to
satisfy the type checker.
Guidance
You can review this PR in one go by changing base to master, or by first reviewing the stacked PRs:
#2180 (frontend changes) typing and AST interpreter
#2244 (high-level ir changes) ir and high-level IR interpreter
This PR does the low-level ir changes needed to express async/await lowering and adds tests and examples.
See design/asynccps.md for more details of the lowering.
Once this is in, I suggest we abandon the old sugar for asynchronous local functions and make do-exp the desugaring. I have not done that yet.

[x] fix premature refund bug (cf. calc.mo)
[x] cleanup construct ml
[x] cleanup async.ml/CPSAwait case
[x] relax effect, ir_effect to be less conservative
[x] update asynccps.md
[x] document
[x] dogfood in prelude where app to avoid redundant context switches
[x] more checks in check_ir
[x] run on replica while smoking a cigarette
[x] add test for every possible static error in test/fail
[x]  fix interpretation of CPSDoAsync, CPSAwait (even though we never execute them in our tests)
[ ] remove silly scheduling of success and reject continuation from both interpreters (these context switches are redundant)
[ ] typing of async e and do async {} is identical now - share the code (or better, identify the constructs)

Do you want to keep this PR alive, or is this dead (possibly superseded by https://github.com/dfinity/motoko/issues/2945)?


Block::isAlias returns true for non aliased blocks and false for aliased blocks

I think it should be the other way around.
To test this, I created a form block in the main area, then copy and pasted it into the main area again. I added var_dump($this->block->isAlias()) to the view and saw that the original block returns true and the aliased block returns false.
On top of that I wasn't able to figure out how to differentiate between a block and its aliases.

Hmm, I haven't verified personally but I imagine you're seeing this because $this->block is actually pointing to an instance of the clipboard proxy block, which is probably NOT an alias.
We used to handle pasted blocks by simply aliasing them into areas, but this caused all kinds of problems. Using the proxy block is much nicer.


Fixes #602.
Relates to #464 and #468.

I think getting rid of warnings is laudable, but this might not be very high impact in the Rust code, as we are planning to delete it and move to C++ for this anyway.

I think getting rid of warnings is laudable, but this might not be very high impact in the Rust code, as we are planning to delete it and move to C++ for this anyway.

Understood, it's nice to keep the build clean in any case (there were some hidden warnings that pointed to real dead code that had possible interim ramifications), but I'll minimize time spent on Rust.


FEAT-#96: Add python-versioneer to get exact unidist version

Signed-off-by: Igoshev, Yaroslav<EMAIL_ADDRESS>What do these changes do?

[x] passes flake8 .
[x] passes black .


k8s cluster_domain is not supported by Rancher

Today we default k8s namespace to the k8s default domain value - "cluster.local". But there is a way to override the default domain by specifying cluster_domain in the service template:
cluster-domain=<default local domain>

We should add support for overriding default domain in Rancher dns based on the k8s service clusterDomain; and only if not specified, set to cluster.local.
@ibuildthecloud

@alena1108 Do you think we should fix this?
We can ask the user what their cluster domain should be on before kubernetes system stack start.

Technically, not a bug but a limitation.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


feat: Change minimum version 3.6 -> 3.8

Summary
Write the summary about this PR.

최소 python version을 3.6.5 -> 3.8

Changes
Write changes in detail.

python 버전에 맞춰 디펜던시들 버전 변경
github action ci test 수정

How to Test?
Write a way to test the changes.

Checklist

[ ] Do you pass all the tests?
[ ] Do you write the changes on document such as README?

Codecov Report

Merging #109 (b5a4b9c) into main (70a5a33) will increase coverage by 0.48%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #109      +/-   ##
==========================================
+ Coverage   81.07%   81.56%   +0.48%
==========================================
  Files          24       24
  Lines         560      564       +4
==========================================
+ Hits          454      460       +6
+ Misses        106      104       -2

Flag
Coverage Δ

unittests
81.56% <100.00%> (+0.48%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

onebone/feature/time.py
73.91% <100.00%> (ø)

onebone/signal/smoothing.py
79.68% <0.00%> (+4.68%)
:arrow_up:

Continue to review full report at Codecov.

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

minimum 3.8은 너무 높지 않을까요?

@kyunghwan-onepredict  벌써 3.6 지원 종료군요.. 말씀하신 포인트들에 동의합니다.

기범님 LGTM

Good!


Error while running train.py

Hello I tried to install gnina but I always get this error
I already added this in bashrc and sourced it
export PYTHONPATH=/usr/local/python:$PYTHONPATH
./scripts/train.py -h
Traceback (most recent call last):
File "./scripts/train.py", line 11, in
import caffe
File "/usr/local/python/caffe/init.py", line 2, in
from ._caffe import init_log, log, set_mode_cpu, set_mode_gpu, set_device, Layer, get_solver, layer_type_list, set_random_seed, solver_count, set_solver_count, solver_rank, set_solver_rank, set_multiprocess, Layer, get_solver, has_nccl, device_synchronize
ImportError: cannot import name has_nccl

That should be defined in /usr/local/python/caffe/_caffe.so
Are you sure you linking with the gnina-specific version of caffe and not some vanilla distribution?  Check the timestamp of _caffe.so to make sure it it was installed when you installed gnina.


I cannot view information regarding data and applications

I cannot view information regarding data and applications and if I have policies configured, the application only brings me results for devices and identity

Hi @IsaacVS160883 - only Identity and Devices report back assessment information currently. As we continue to build out the other pillars, and enhance Data, these other sections will begin to light up.


Command Line Switch "ExecutePythonScript" not working with UnrealEnginePython

I have to run some project assembly process from within the command line and this flag seems to only be working with UE4's native python. How can I use it with your extension ? Is there any other way to run python script right after project has been opened (from command line without any user interaction).
Thank you.

I am not sure when ue_site.py is being called but it give me ImportError:
LogPython: Error: cannot import name PyFbxFactory
LogPython: Error: ImportError: cannot import name PyFbxFactory
Is this because the plugin is installed as a part of the project and not the editor itself ?
PyCommandlet does not seem to run the file at all.
Code is OK and running successfully from the editor.

Hi @rdeioris ,
Thank you so much for help !
PyCommandlet is running the script. I believe it does not like dots in the middle of the filepath and does not seem to work with relative paths "/Game/Scripts/...".

Hi, you may want to check this:
https://github.com/20tab/UnrealEnginePython/issues/268

Hi @unbit ,
Thanks, I wil give it s try.
Hi @rdeioris,
Running the same code via PyCommandlet and UEP Editor yields different results. PyCommandlet execution is not creating a Skeleton for SkeletalMesh in case of FBX import. I have tried default importUI settings but no luck. Do I have to create Skeleton manually and assign it to the mesh.Skeleton ?


Issue in Camera Switching Sample

If we switch camera for more than 2 times then one stream gets blank

Did anybody face this problem?


Update prompt_styler.py

Fixes https://github.com/al-swaiti/ComfyUI-OllamaGemini/issues/8

literally stumbled here for this fix to watch it get merged in real time


Update readme

Changes
https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000J5fPrSAJ
Re-opened because last PR did not merge

won't merge :(


[WIP] fix transition-group transition on empty array - #4900

#4900

What the hell, I didn't close this. I was trying to push the test case I added


🐞 [Bug]: Farmerbot, Timezone UTC not local

What happened?
The readme of farmerbot says:
⚠ Be careful: The timezone of the farmerbot will be the same as the time zone of the machine the farmerbot running inside.
But on my side, I set the wakeup of the nodes at 1pm and it starts at 8am. So the time is 1pm UTC = 8am EST. This works as EST = UTC - 5.
We could write:
⚠ Be careful: The timezone of the farmerbot is in UTC.
Or we really make the farmerbot in the timezone of the machine the farmerbot is running inside.

Can you provide more logs from your machine?

Of course! Here it is.
fbotgologs.md
Let me know if you need anything else! Thanks.

can you please do datetimectl,  code checks shows it's using datetime local to the machine

I am deploying on a full VM on the farm itself, node 3860. Here's the output:
root@fbotgo:~# timedatectl
               Local time: Tue 2024-01-23 19:17:53 UTC
           Universal time: Tue 2024-01-23 19:17:53 UTC
                 RTC time: n/a
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

You are right the node is set to UTC. It seems playground full vm node gets the UTC timedate, or at least in this case. We can close the issue I think. I thought the node would get the local time zone.


Add Flask-Mail to dependencies

Flask-Mail is imported in utils.py
Otherwise, I get this trace when starting the server.
Traceback (most recent call last):
  File "serve.py", line 2, in <module>
    app = create_app()
  File "[..]\CTFd\CTFd\__init__.py", line 23, in create_app
    from CTFd.views import views
  File "[..]\CTFd\CTFd\views.py", line 2, in <module>
    from CTFd.utils import authed, ip2long, long2ip, is_setup, validate_url, get_config, set_config, sha512, get_ip
  File "[..]\CTFd\CTFd\utils.py", line 6, in <module>
    from flask.ext.mail import Message
  File "C:\Python27\lib\site-packages\flask\exthook.py", line 87, in load_module
    raise ImportError('No module named %s' % fullname)
ImportError: No module named flask.ext.mail

Flask Mail is no longer used. That's a leftover from moving to smtplib. Sorry about that I'll commit a fix right now.

Thanks


Design document for Custom Resource Metrics Exporter

This is the design for Metrics Exporter which will be
used to export metrics related to Custom Resources of
interest to OCS.
Signed-off-by: Umanga Chapagain<EMAIL_ADDRESS>

/override ci/prow/images
/override ci/prow/ocs-operator-ci
/override ci/prow/ocs-operator-e2e-aws
/override ci/prow/red-hat-storage-ocs-ci-e2e-aws
/override ci/prow/verify-latest-csv

/override ci/prow/images
/override ci/prow/ocs-operator-ci
/override ci/prow/ocs-operator-e2e-aws
/override ci/prow/red-hat-storage-ocs-ci-e2e-aws
/override ci/prow/verify-latest-csv


Memory safety

The garbage collector in newer Go (e.g. 1.5) got smarter. jerr sometimes gets collected and we crash.
Here: https://github.com/pixiv/go-libjpeg/blob/a79c3a8f1d88709bc1e79de4a37dadcfc36dd62d/jpeg/decompress.go#L77
and here: https://github.com/pixiv/go-libjpeg/blob/a79c3a8f1d88709bc1e79de4a37dadcfc36dd62d/jpeg/compress.go#L57
It is possible the source/dest managers will have similar issues. I've added some ugly code to keep jerr and mgr referenced and the crashes went away.
Some related issues:

https://github.com/golang/go/issues/11345
https://github.com/golang/go/issues/10303

I see. go-thumber does it better (but uglier).
https://github.com/pixiv/go-thumber/blob/master/jpeg/jpeg_read.go#L155-L177
I'm trying to fix it cleanly, if I can. Any idea?

https://github.com/pixiv/go-libjpeg/pull/22 This probably solves.

The mgr made by makeDestinationManager may still be garbage collected.
In the meanwhile, It is okay to have a Go struct allocated on the C heap. However, variables reference by that struct will not be scanned by Go GC. In this case, the r variable is not referenced in Go anymore.

Really? makeDestinationManager returns the mgr and accessed later by defer releaseDestinationManager(dstManager), so it doesn't look like a problem to me.

@edvakf sorry I missed the commits following e801a2.

Cool

https://github.com/golang/proposal/blob/master/design/12416-cgo-pointers.md
We cannot assign io.Reader/io.Writer to a C struct in Go 1.6.

See #25.

#25 is merged.


Adding forgor password feature (Backend and frontend)

Is your proposal related to a problem?
If user forgets his password theres no way to login in his account
(Write your answer here.)
Describe the solution you'd like
I wanted to add forget password functionality, so user can change his passsword
(Describe your proposed solution here.)

@Sourabh782 Go for it

@MitulSonagara i am having a problem regarding mail, i have added backend routes but mail is giving a error, can you help resolve it?

i am sure its some setup error


Improve AcroForm/XFA form type detection

The commit messages contain more information about the individual changes.
Fixes #12217.
Replaces #12254.
For completeness, here is the list of test PDF files with the form type detection results from before/after this patch (note that we only fallback if only XFA is available):

File
Before
After
Notes

http://www.aloaha.com/wp-content/uploads/2016/07/SampleForm-1.pdf
AcroForm, XFA, fallback
AcroForm, XFA, no fallback

http://www.cic.gc.ca/english/pdf/kits/forms/IMM5257E.PDF
AcroForm, XFA, fallback
XFA, fallback
SigFlags bit set and nested signature in Fields.

https://web.archive.org/web/20121105185256if_/http://www.northeastern.edu/hrm/pdfs/resources/benefits/MBTA-pretax-form-July2012.pdf
AcroForm, XFA, fallback
XFA, fallback
Empty Fields.

https://web.archive.org/web/20110918100215/http://www.irs.gov/pub/irs-pdf/f1040.pdf
AcroForm, no fallback
AcroForm, no fallback
SigFlags available, but first bit not set.

https://github.com/mozilla/pdf.js/files/762326/212241.6.pdf
AcroForm, no fallback
AcroForm, no fallback
SigFlags bit set and multiple signatures in Fields.

/botio test

Thank you for the review! I have addressed all comments in the new commit series.

/botio unittest

/botio makeref


Issues Using FinGPT/fingpt-forecaster_dow30_llama2-7b_lora

Good Day,
First of all, love this project. Thanks for all everyone does who contributes.
I am new to huggingface so thanks for bearing with me. Anyways, I am trying to load the dow30 model but always get the issue: "OSError: base_models/Llama-2-7b-chat-hf is not a local folder and is not a valid model identifier listed on 'https://huggingface.co/models'". Is there something I am missing?
For example, I get that error when simply running: pipeline('text-generation','FinGPT/fingpt-forecaster_dow30_llama2-7b_lora')
I also try following the Readme for the forecaster, but keep getting a "can't find the .config file"
Any help would be much appreciated!

There were some mistakes in the README instructions, and the code in demo.ipynb was intended for loading models from disk. Now I've corrected them both. Try again and see if there are any more things we can help you with.

thanks so much for your quick response! I have a follow up question in regards to the .readme line of code:
model = PeftModel.from_pretrained('FinGPT/fingpt-forecaster_dow30_llama2-7b_lora')
I am getting the error: "TypeError: PeftModel.from_pretrained() missing 1 required positional argument: 'model_id'"
Shouldn't the code be:
model = PeftModel.from_pretrained(base_model,'FinGPT/fingpt-forecaster_dow30_llama2-7b_lora') ?

quick response! I have a follow up question in regards to the .readme line of code:
model = PeftModel.from_pretrained('FinGPT/fingpt-forecaster_dow30_llama2-7b_lora')
I am getting the error: "TypeError: PeftMo

You're right. Thanks for pointing that out, my bad for not reviewing the README codes. Fixing it.


2015 Weekly Hangouts, Roadmap & Contributors' Guide

Development of Anvil Connect should be driven by the people that depend on it most. You're invited to take part in weekly Google Hangouts as we map out the future of the project, talk through specs, review code, and help each other ship in the year to come.
We now have users on at least 4 continents, so scheduling group hangouts to work for everyone is getting tricky. We propose meeting up every Thursday for one hour, alternating between 2 PM and 9 AM Pacific time, starting with 2 PM on Thursday, January 15th, followed by 9 AM on January 22nd, and so on.
Roadmap for 2015
We made enormous strides last year by shipping a usable subset of the OpenID Connect Core specification and testing the waters in production. Now there's a huge amount of work to be done building on last year's progress to make Anvil into the obvious choice for an OIDC-based auth service.
The outline presented here contains loosely prioritized, high level suggestions for where to direct our efforts going forward. Topics are tentatively included based on outstanding issues, real-world user feedback, lessons learned in practice, and needs we can clearly anticipate. This is not a final roadmap, rather a place to start the conversation.
Proposed Roadmap Outline

Single Sign-On via OIDC Sessions
Additional authentication features (email verification, 2FA, etc)
Support for more requested OAuth providers and protocols (LDAP, OpenID, WS-Fed, SAML, etc)
Client libraries for a variety of languages, frameworks and platforms
Issuing API Keys (2-Legged OAuth)
Attribute-based Access Control (ABAC)
Groups
Invite-based registration
Middleware "hooks" for programmatically customizing auth flows
Brokering API access and marshaling third-party tokens
API discovery and generated/dynamic client code
Device identity for IoT
Improved administration via Web, Mobile, CLI & REST API
Containerized deployment support
Continuous integration and reference deployment
Complete, tested OIDC interoperability
Code security audits and penetration testing
Self-contained persistence and horizontal scalability
Multi-tenancy
Move repositories to a GitHub Organization
Tutorials, examples, blog posts, website, and API documentation
Funding

We don't have the bandwidth to work on every conceivable improvement simultaneously, so we'll need to reach a consensus on priorities. We want your input so that we're building what's needed, as it's needed. You can influence priorities by contributing your thoughts to the roadmap, collaborating on development, or  by helping to fund the project.
Toward a Contributors' Guide
We recognize the fact that the impact of infrastructure is leveraged. Our work affects not only our direct users, but their users as well. To the extent that it's deployed, our code potentially impacts privacy, security, business continuity, revenue, bottom line, liability, and investments in development.
Awareness of that potential affects the choices we make about software development. These choices should eventually be contemplated and codified; not only does this guide new contributors toward participating successfully, it also helps us stay on track and improve our game as we grow. The requirements for the guide's contents are open for debate, and a loose outline will be provided for us to develop and refine.
Participating
All users, contributors and interested parties are welcome to join the hangouts. Please comment on this post if you'd like an invite or email<EMAIL_ADDRESS>cc: @tomkersten, @ckarande, @nrhope, @sridharAJ, @petebot, @psexton, @gcrahay, @forthguy, @radu-c, @zhengt, @slattery, @nevraeka, @KjeldLoozen, @igi64, @duaneallam, @mmontone, @deftnerd, @AC-3PG, @adi-ads, @miguelcoba, @dreamineering
You're invited because you forked, watched, or contributed to Anvil Connect and related projects, or we've talked.

@christiansmith definitely my bearded brother. Send it my way. I will attend as many as I can

@christiansmith +1

Hi Christian,
Will try to attend the afternoon variants. However it's a bit tricky for me
to make 9am due to school drop-offs for the kids etc, so means I have to
take the calls at home. Would prefer an hour later if that doesn't impact
other attendees? Otherwise will do my best.
Thanks,
Norval
On Tue, Jan 13, 2015 at 5:02 AM, Christian Smith<EMAIL_ADDRESS>wrote:

Development of Anvil Connect
https://github.com/christiansmith/anvil-connect should be driven by the
people that depend on it most. You're invited to take part in weekly Google
Hangouts as we map out the future of the project, talk through specs,
review code, and help each other ship in the year to come.
We now have users on at least 4 continents, so scheduling group hangouts
to work for everyone is getting tricky. We propose meeting up every
Thursday for one hour, alternating between 2 PM and 9 AM Pacific time,
starting with 2 PM on Thursday, January 15th, followed by 9 AM on
January 22nd, and so on.
Roadmap for 2015
We made enormous strides last year by shipping a usable subset of the OpenID
Connect Core http://openid.net/specs/openid-connect-core-1_0.html
specification and testing the waters in production. Now there's a huge
amount of work to be done building on last year's progress to make Anvil
into the obvious choice for an OIDC-based auth service.
The outline presented here contains loosely prioritized, high level
suggestions for where to direct our efforts going forward. Topics are
tentatively included based on outstanding issues, real-world user feedback,
lessons learned in practice, and needs we can clearly anticipate. This is
not a final roadmap, rather a place to start the conversation.
Proposed Roadmap Outline

Single Sign-On via OIDC Sessions
http://openid.net/specs/openid-connect-session-1_0.html
Additional authentication features (email verification, 2FA, etc)
Support for more requested OAuth providers and protocols (LDAP,
OpenID, WS-Fed, SAML, etc)
Client libraries for a variety of languages, frameworks and platforms
Issuing API Keys (2-Legged OAuth)
Attribute-based Access Control (ABAC)
Groups
Invite-based registration
Middleware "hooks" for programmatically customizing auth flows
Brokering API access and marshaling third-party tokens
API discovery and generated/dynamic client code
Device identity for IoT
Improved administration via Web, Mobile, CLI & REST API
Containerized deployment support
Continuous integration and reference deployment
Complete, tested OIDC interoperability
Code security audits and penetration testing
Self-contained persistence and horizontal scalability
Multi-tenancy
Move repositories to a GitHub Organization
Tutorials, examples, blog posts, website, and API documentation
Funding

We don't have the bandwidth to work on every conceivable improvement
simultaneously, so we'll need to reach a consensus on priorities. We want
your input so that we're building what's needed, as it's needed. You can
influence priorities by contributing your thoughts to the roadmap,
collaborating on development, or by helping to fund the project.
Toward a Contributors' Guide
We recognize the fact that the impact of infrastructure is leveraged. Our
work affects not only our direct users, but their users as well. To the
extent that it's deployed, our code potentially impacts privacy, security,
business continuity, revenue, bottom line, liability, and investments in
development.
Awareness of that potential affects the choices we make about software
development. These choices should eventually be contemplated and codified;
not only does this guide new contributors toward participating
successfully, it also helps us stay on track and improve our game as we
grow. The requirements for the guide's contents are open for debate, and a
loose outline will be provided for us to develop and refine.
Participating
All users, contributors and interested parties are welcome to join the
hangouts. Please comment on this post if you'd like an invite or email
<EMAIL_ADDRESS>cc: @tomkersten https://github.com/tomkersten, @ckarande
https://github.com/ckarande, @nrhope https://github.com/nrhope,
@sridharAJ https://github.com/sridharAJ, @petebot
https://github.com/petebot, @psexton https://github.com/psexton,
@gcrahay https://github.com/gcrahay, @forthguy
https://github.com/forthguy, @radu-c https://github.com/radu-c,
@zhengt https://github.com/zhengt, @slattery
https://github.com/slattery, @nevraeka https://github.com/nevraeka,
@KjeldLoozen https://github.com/KjeldLoozen, @igi64, @duaneallam
https://github.com/duaneallam, @mmontone https://github.com/mmontone,
@deftnerd https://github.com/deftnerd, @AC-3PG
https://github.com/AC-3PG, @adi-ads https://github.com/adi-ads,
@miguelcoba https://github.com/miguelcoba, @dreamineering
https://github.com/dreamineering
You're invited because you forked, watched, or contributed to Anvil
Connect and related projects, or we've talked.
—
Reply to this email directly or view it on GitHub
https://github.com/christiansmith/anvil-connect/issues/61.

Won't be able to make the 2pm but count me in for 9am one

Hi Christian
This road map is very helpful.  I am sure we will need to work on
prioritizing tasks.
I won't be able to make today's hangout but should be able to join upcoming
sessions.
Best
Chetan
Won't be able to make the 2pm but count me in for 9am one
—
Reply to this email directly or view it on GitHub
https://github.com/christiansmith/anvil-connect/issues/61#issuecomment-69932949
.

@christiansmith  I'm working on my prioritized list...could you explain "Issuing API Keys (2-Legged OAuth)" a little bit please? How does it work/impact client applications? What kind of applications? What are the key problems it solves?
I think I know the gist of this, but wanted to ping you about it to confirm...and thought others may be interested.

@tomkersten
This originally came up back in July and we filed issue #52. There's some discussion there. Also, Twitter has an explanation in their docs.
API keys would most likely be implemented using the OAuth 2.0 Client Credentials Grant which would issue a JWT access token. These tokens would be used only for server to server communication, never from a web browser or native client.
The client tokens could be used for any scenario that requires authentication of the client without the context of an authenticated user. For example, they could be used for rate limiting third party API access, or for service to service communication within your realm.
All the advantages of JWTs as user-specific access tokens also apply to client-specific access tokens; encoded claims, use of scope for permissions, verifying with signatures instead of db queries or auth server requests, etc.
The OIDC dynamic client registration we already implement issues a JWT "client registration token" which functions as an API key for the /register/:uuid endpoint. However, we have no way at present to recover or reissue a key after registration.

@christiansmith Perfect, and thanks. The Twitter link is great, btw.
Will post some more thoughts hopefully later today.

Improved logging #62 should be added to the roadmap.

A prioritized list from my perspective, with some context to each:

Invite-based registration

Being able to limit sign-ups to the peopel I invite would be handy, particularly now...in the "early" days of application usage & development.

Improved administration via Web, Mobile, CLI & REST API

I'd like to build out a separate "profile" service of some sort. I plan to then add to the profile information as appropriate for our particular context. Being able to interface with pretty much all aspects of a user's account in Anvil will be necessary for me (which applications do they have access to, which have they used, what is their profile picture, email, etc.).

Additional authentication features (email verification, 2FA, etc)

Right now we are using Google, but I will not be surprised if this changes to ONLY allow "internal" accounts (email/password). If that ends up happening, at least the basics of this would absolutely be required. The "basics" in my mind would be: Email verification (click link to confirm), "Forgot password" support, and the ability to change your password easily somewhere. Given my comments about a profile service from above, doing so via a "trusted" application over the API would likely come in handy in this case.

Single Sign-On via OIDC Sessions

This just makes sense as soon as you have multiple applications. Also, it demos well...which is great for both Anvil and anyone who sets up an Anvil server. I'm conflicted on whether this is "before" the "Middleware hooks" in the list of priorities, but for now, I'd put it above.

Middleware "hooks" for programmatically customizing auth flows

I think this would be valuable for several things, and I know we've spoken about it in the past...but the only things that are popping in my mind about it now would be metrics- & logging-related.

Attribute-based Access Control (ABAC)

I still need to read up on this a bit to fully understand it, but...it sounds like it would be a nice fit for some of our user/group/permission scenarios.

Great input @tomkersten. Thanks!

@christiansmith fyi: i added "Issuing API Keys (2-Legged OAuth)" to my previous comment...somehow forgot that initially.

I think we should split out the Contributor's guide into its own issue. This issue is rather comprehensive in its scope.


Add and,or and not conditions to the Compendium Browser trait filter

Maybe radios with "all of above" and "any of above"? For the "not" bit, how about a :no_entry_sign: next to the :x:?

I tried a 🚫 element at first but I can't get it into the tag without breaking the styling of the whole thing. 😫

I think we can eschew the "Condition" part.


SEPG Automated Release - v1.1.0

SEPG Details
Release Build Link: https://sou-jenkins2.swinfra.net/job/Auto-Release/774/
Build Token: github.com/CAFapi/oraclelinux-base-images/main/8b830fedc91665ec563d6e1db596d5100821d511
Versioning Behaviour: Roll on to next minor
Artifacts For Release
Docker

cafapi/oraclelinux-base:1.1.0 (Static Tag)
cafapi/oraclelinux-base:1.1 (Dynamic Tag)
cafapi/oraclelinux-base:1 (Dynamic Tag)
cafapi/oraclelinux-base:latest (Dynamic Tag)
cafapi/oraclelinux-jre17:1.1.0 (Static Tag)
cafapi/oraclelinux-jre17:1.1 (Dynamic Tag)
cafapi/oraclelinux-jre17:1 (Dynamic Tag)
cafapi/oraclelinux-jre17:latest (Dynamic Tag)
cafapi/oraclelinux-jre21:1.1.0 (Static Tag)
cafapi/oraclelinux-jre21:1.1 (Dynamic Tag)
cafapi/oraclelinux-jre21:1 (Dynamic Tag)
cafapi/oraclelinux-jre21:latest (Dynamic Tag)

 Build Stage
Action
Status

Release Checks
completed
:heavy_check_mark:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here


makefile: preserve timestamps and set permissions on install

Does this mean everyone on M1 14 inch MacBook can soon install speakers audio just by updating Asahi ? Just asking because of “the device-tree enabling”-thing which no one gives the right instructions for.
mvg
Combass
Jean-Marie Bastiaens
Zaakvoerder
@.*** - @.***
www.combass.be
+32 485894441
BE 0769.937.302
IBAN BE58 3632 1574 1679

Op 23 jul. 2023, om 16:37 heeft Davide Cavalca @.***> het volgende geschreven:
You can view, comment on, or merge this pull request online at:
https://github.com/chadmed/asahi-audio/pull/11
Commit Summary
fc1d74b https://github.com/chadmed/asahi-audio/pull/11/commits/fc1d74b41a4023cc55e258ab95562c24ae07ac15 makefile: preserve timestamps and set permissions on install
File Changes (1 file https://github.com/chadmed/asahi-audio/pull/11/files)
M Makefile https://github.com/chadmed/asahi-audio/pull/11/files#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52 (26)
Patch Links:
https://github.com/chadmed/asahi-audio/pull/11.patch
https://github.com/chadmed/asahi-audio/pull/11.diff
—
Reply to this email directly, view it on GitHub https://github.com/chadmed/asahi-audio/pull/11, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7AMMRIGF65QKO3KG5X3CL3XRUZLRANCNFSM6AAAAAA2UR2H3M.
You are receiving this because you are subscribed to this thread.

An announcement will be made when there is something to announce.


remove 'beta' messaging; add missing filter toggles

Removing 'beta' messaging for Operator GA release tomorrow.
Also added missing filter goggles on the Monitoring K8s page.

This change is


remove isRequired parameter from floating input label

this is unnecessary since user input validation is done server side and not client side. In fact, the noValidate option is used on forms to avoid ugly popups.

Actually I don't need to remove the required parameter. Instead, I just need to show something special like a star or something, when a field is required. I totally forgot that this was the reason why I included the prop.


enables regularization for slicewise transformations

currently implementing regularization of rotation, however the regularization of center of mass should be done beforehand, by simply smoothing the data along z direction also (currently, smoothing is done inplane).

fixed in #999

Example of result on a distorted spinal cord:


Galal branch

Checklists
General Checks

[ ] the branch is up to date with main/master
[ ] the code works when pulled and run locally
[ ] All CI checks pass
[ ] all conflicts are resolved (if any)
[ ] PR has a descriptive title
[ ] PR has appropriate labels and milestones for easy identification
[x] PR it is assigned to the owner
[x] reviewers are assigned
[ ] the PR contributes only one focused change
[ ] It is in the appropriate column in the project board (if necessary)
[ ] has short and clear description
[ ] is linked to an issue (if it is related)
[ ] feedback is addressed (if any and if it is appropriate feedback.)

Markdown

[x] the markdown source is formatted
[x] spelling and grammar is correct in all text
[ ] The markdown looks correct when you preview the file
[x] all links and images work
[ ] any embedded code snippets are formatted

You have a nice bio @galalkoro98
You have some problems:

Make sure your branch is updated by using git pull main
Make sure you passed all linting and format before pushing your changes.


Texture resolution does not match the device resolution.

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment

OS: Windows 10
scrcpy version: 2.1.1
installation method: Windows release
device model:  Mumu12 Android Emulator v.3.5.22 (2201)
Android version: 12

Describe the bug
The emulator resolution is 960X540, which is verified by scrcpy and adb cmd.
>adb shell wm size

Physical size: 540x960

or
>scrcpy  --list-displays

scrcpy 2.1.1 <https://github.com/Genymobile/scrcpy>
INFO: ADB device found:
INFO:     --> (tcpip)       <IP_ADDRESS>:16384            device  V2199GA
scr...1 file pushed, 0 skipped. 1.6 MB/s (56995 bytes in 0.034s)
[server] INFO: List of displays:
    --display=0    (960x540)
    --display=2    (960x540)

However, when I use scrcpy, the screen resolution is 960X536. The display resolution height (536) is a little lower than origin height (540), as shown by the scrcpy cmd.
>scrcpy --display=0

scrcpy 2.1.1 <https://github.com/Genymobile/scrcpy>
INFO: ADB device found:
INFO:     --> (tcpip)       <IP_ADDRESS>:16384            device  V2199GA
scr...1 file pushed, 0 skipped. 1.6 MB/s (56995 bytes in 0.034s)
[server] INFO: Device: [vivo] vivo V2199GA (Android 12)
INFO: Renderer: direct3d
INFO: Texture: 960x536

When I set the emulator device resolution to any other value e.g.1920X1080, 1280X720, the texture resolution keeps the same.
Once I set the emulator device resolution to 960X540, the texture resolution is 960X536.

scrcpy rounds the size to a multiple of 8, because many encoders do not support a size which is not multiple of 8.

Got it. Many thanks for you help. @rom1v

You could try to disable this rounding and see if it works for you:
https://github.com/Genymobile/scrcpy/blob/1ee46970e373ea3c34c3d9b632fef34982d7a52b/server/src/main/java/com/genymobile/scrcpy/ScreenInfo.java#L111-L117

Thanks, this is exact what I am looking for. @rom1v


Update dependencies

This PR updates all dependencies for the project, including the eslint/ eslint-plugin-react dependencies that got a couple of versions ahead of us.
cc/ @GoodForOneFare

👍


Use --fair-sched=yes option with valgrind

Running valgrind's memcheck with multithreaded examples is known to be slow.
Using --fair-sched=yes option improves execution speed significantly, reducing time spent by Tsetlini's github workflow.

--fair-sched=yes does not seem to improve valgrind execution speed in virtualized github actions environment.


Extra dependencies on raspbian Jessie (raspberry pi)

It works on raspberry pi (raspbian Jessie). Just make sure the following python packages are installed:
sudo apt-get install python-dev
sudo pip install netifaces
sudo pip install enum34

It might help someone else in the future. :-)

The dependencies should be installed as part of installing the package from pypi. (but yes, python-dev is needed for netifaces)

Well, pip did not do it for me so I figured something is wrong in the dependencies configuration. Pip just complained about netif aces when installing pychromecast.

I needed to install as described above to get it working for me on Raspbian Jessie lite. Thanks for making a note of it.


Clean up comments

Fix some typos
Ensure consistent formatting for docstrings

Thanks @jsiegle :)

Hi Josh.
Thank you very much for having a look into this.
Sorry for typos they are mine.
I made two comments on your patch.
have a good day.

Merci Josh.


Feature Request: ValuePrefix/-Suffix for Widget string

I would like to strongly structure certain areas of my website and assign the translationKey uniformly. e.g. the translationKey of my blog posts should be pre-assigned with post-. This value prefix should not be editable.
Unfortunately, I got this idea from the existing prefix / suffix implementation, but there is a different functionality here.

Well yes, I’ve implemented https://github.com/decaporg/decap-cms/pull/6836 a few weeks ago, but I think prefix and suffix for the UI visibility purpose are ill-named. Another PR https://github.com/decaporg/decap-cms/pull/6675 I have also implemented uses prefix in the right way.
I think no one uses it in Sveltia CMS yet; I could rename the current prefix/suffix properties to something else and implement this as prefix/suffix.

I think no one uses it in Sveltia CMS yet; I could rename the current prefix/suffix properties to something else, say before_input/after_input, and implement this as prefix/suffix.

Sounds promising.


Docker container out of date?

Apart from a weird bug that I'm facing with devenv in devcontainers, I've noticed that the docker container at ghcr.io/cachix/devenv seems to still be version 0.6.2. Will this get updated?

There's now https://github.com/cachix/devenv/pkgs/container/devenv built from the main branch if you need the latest.

Pushed v0.6.3!


Compiler error when mocking classes with generics

worked in 3.4.2, broken in 3.5.0
real example:
      class MockableBroadcast[T: ClassTag] extends org.apache.spark.broadcast.Broadcast[T](42L) {
        override protected def getValue(): Nothing = ???
        override protected def doUnpersist(blocking: Boolean): Unit = ???
        override protected def doDestroy(blocking: Boolean): Unit = ???
      }
      val lookup= mock[MockableBroadcast[Map[String, Long]]]

minified example:
      class Foo[T: ClassTag]
      val mf = mock[Foo[Nothing]]

compiler error:
Error:(55, 20) type mismatch;
 found   : scala.reflect.ClassTag[T]
 required: scala.reflect.ClassTag[Nothing]
Note: T >: Nothing, but trait ClassTag is invariant in type T.
You may wish to investigate a wildcard type such as `_ >: Nothing`. (SLS 3.2.10)
      val mf = mock[Foo[Nothing]]

cause: changes to MockMaker.initDef

https://github.com/paulbutcher/ScalaMock/blob/88504cc7a0a519324680df17b1a96b7aa71720a5/core/shared/src/main/scala/org/scalamock/clazz/MockMaker.scala#L222
typeSignatureIn returns the parameter T, not the materialised type (e.g. Int)

Bit stuck on this one, so I asked at https://stackoverflow.com/questions/42044540/obtaining-the-realised-type-for-a-scala-class-using-macros and gitter

very stuck, the solution with .dealias is more difficult to implement than I thought. Also MockAdapter for 2.10 redirects this to .normalize

Okay, I found workaround, you need to specify all the types (including _ in F[_]) explicitly by creating another class which extends from the generic one


Add comments to exported functions

Right now godoc.org contains documentation for ledis, but there are almost zero comments on hundreds of exported functions.
It would be very helpful to have these comments as it will make the package much easier to use.
It might be a good idea to tag it as a HELP WANTED: BEGINNERS issue so that beginners can try their hand at open source contributions. Running a linter over the code will tell you the files that need changing. It was done with great effect at InfluxDB

Thank you @nii236

Now I have no time to do it, I will try to improve it later.


Remove May 16 webinar

Remove the May 16 webinar from Webinar: Introduction to California’s plain language standard. Potentially remove the page and updated CalAcademy as well.

Page removed from site, including link from CalAcademy.


Camera and Microphone not working

Describe the bug
When I click on the Microphone/Camera button that should ask me to give permission for the app and activate the Microphone/Camera, nothing happens.
Expected behavior
I should get a permission request window and then enable that functionality
Screenshots

Device (please complete the following information):
Samsung Galaxy S8 - 9.0
Additional context
I just changed the ASWV_URL on the example project to point to my website

You need to add microphone permission in the Manifest and MainActivity, camera permissions are already there, so just try doing that first.

So, as you said, the camera permission is already there, but it doesn't work for me here.

I believe your app needs direct stream of information which isn't possible as of now with SWV. You need to integrate WBRTC features in the app to stream any live content.

Ok, I'll look into that

hello,
i use the same software (bigbluebutton), on chrome it works fine and it's requesting for permission  ,
why in your webview this doesn’t work?

@freehussain chrome is not a webview app, it's a chromium engine.
we've very limited resources here to work with.
don't you wonder why is chrome more than 50MB while SWV is just 5MB?


Max connections open flag does not work

What platforms are affected?
linux
What architectures are affected?
amd64
What SpiceDB version are you using?
V1.32.0
Steps to Reproduce
Have the following argument on command line:
--datastore-conn-max-open=10
Expected Result
Connection limits are limited to the setting in the flag and cannot exceed the amount of connections
We have a max replicas of 10, and our database has a max connection of 200. But with 10 max replicas and 10 max connections flag, we sometimes get too many connections used in our database, when this is the only service that connects to that database.
We also get a message the flag is deprecated, but can't find any documentation on the spicedb site that has what to use instead, it still references --datastore-conn-max-open
Actual Result

I get an error on startup saying Flag --datastore-conn-max-open has been deprecated, connection pooling has been split into read and write pools
Despite having this value set to 10, and have maximum 10 replicas, we get to too many connections used (our database has a max of 200)

The deprecation warning is indicating that this flag has been superseded by these two:
--datastore-conn-pool-write-max-open int                           number of concurrent connections open in a remote datastore's connection pool (default 10)
--datastore-conn-pool-read-max-open int                            number of concurrent connections open in a remote datastore's connection pool (default 20)

The numbers don't entirely line up, but can you try using the read + write flags rather than the old flag?
Also keep in mind that this is on the individual SpiceDB node, so if you're running multiple nodes and/or have autoscaling in place, you need to account for that.

I'm not sure which DB you're using, but it may also be appropriate to consider using a connection pooler (e.g. pgbouncer for postgres)

I don't think this is the reason you are observing those excess connections, but I'll leave it here for reference, since there was a recent bug on how min connections was handled: https://github.com/authzed/spicedb/pull/1747
Aside from the read-and-write connection pools, connections are opened for other reasons, outside of those pools:

datastore health checks: that will be at least 1 extra connection used every time the health check is run
Watch API calls: in the case of CockroachDB, a new connection will be created per Watch API call.

We recommend:

using the read/write conn pool specific flags (spicedb serve --help should describe those flags)
do not configure pools to max out the database's available connections: leave some headroom for things like health checks.

Also somewhat related, as of https://github.com/authzed/spicedb/pull/1994 there should be better support for connection poolers like pgbouncer

i did use pgBouncer initially, but it was transactional and not supported by spicedb.
I've updated to use what @tstirrat15 referenced and the too many connections issue has been resolved.