Refactor PhoneNumberMatcher::parseAndVerify

CC = 13.
The function first checks whether the character sequence given has the right format to be a phone number.
Then it parses the character sequence into a PhoneNumber object.
After that, the function verifies that the PhoneNumber object is in fact a phone number, according to some accuracy setting called "leniency".
Plan: divide into three steps

check format
parse
check validity

Lizard says 7 after refactoring. I just moved out the part where the format was checked, which was quite complex.


request details: username not resolved in the payload

resources affected:
request
request timeline

after providing the username in the payload, frontend needs to be updated to include the username

Checked in version v0.3.25 and is fixed, expanded field contains the username and frontend displays it correctly.


Error loading model with timm==0.9.7

Hi there,
I tried to load the pretrained model but met an error "Unexpected key(s) in state_dict: "pretrained.model.blocks.0.attn.relative_position_index", ....". I found that this error only happened with timm=0.9.7 and would be gone with timm==0.6.7. I wonder if there is any plan to support the newest timm. Thanks!

I can load the model again by removing all item in weight containing "relative_position_index".


Add taskManager and check for libLoad errors

checked on emulator for CS8C and CS9
PR to #35

So this is currently stalled as I don't have access to SRS or a Staubli robot.
I'm willing to accept the PR based on the fact that you've tested it @JohannesFriedrich, but that would mean it'd be harder to understand future support requests -- if you're not around that is.
It would be great if we could have one more additional user confirming this is all fine. Perhaps @marshallpowell97 could take a quick look?

@JohannesFriedrich: I'm also wondering about the diffs. Did you change the line-ending used in the listed files?


fix(config/html): handle encoding issues and improve error handling in config and HTML file loading functions

Context
This pull request addresses issues related to file encoding and error handling in configuration file loading functions (load_and_validate_config_file and load_and_validate_fixer_config_file) and the HTML output generation function (fill_html_overview_statistics). The changes ensure that files are read and written with the correct encoding, preventing UnicodeDecodeError.
Description

Encoding Handling:

Updated load_and_validate_config_file, load_and_validate_fixer_config_file, and fill_html_overview_statistics to open files with encoding='utf-8' to ensure they are read and written correctly as UTF-8 encoded text.

This change prevents UnicodeDecodeError caused by incorrect or unsupported file encodings.

Specific Exception Handling:

Added specific exception handling for FileNotFoundError, yaml.YAMLError, and UnicodeDecodeError in the configuration file loading functions.
Added specific exception handling for FileNotFoundError and UnicodeDecodeError in the HTML output generation function.
This provides clearer error messages and makes debugging easier.

Default Values:

Used default values in stats.get() in fill_html_overview_statistics to handle cases where keys might be missing.

License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Could you have a look to the tests? It seems that flake8 it's failing

Could you have a look to the tests? It seems that flake8 it's failing. Using pre-commit should be enough https://docs.prowler.com/projects/prowler-open-source/en/latest/developer-guide/introduction/

All pre-commit run result is passed

Hi @pedrooot Thanks for your comment, it seems that I added some new comments and optimized a small portion of the code which resulted in a drop in coverage.

True, don't worry about that. Btw we are reviewing now 😄

Could you please change the log level to error and not exiting in those new errors? I don't think it could be a reason to exit Prowler execution since the scan can still continue.

I have made the requested changes. The log level has been changed to error for the specific exceptions, and the program will no longer exit. This allows the scan to continue even if these errors occur. Errors are now logged at the error level, and the function allows the scan to proceed without exiting the Prowler.

Could you please change the log level to error and not exiting in those new errors? I don't think it could be a reason to exit Prowler execution since the scan can still continue.

I have made the requested changes. The log level has been changed to error for the specific exceptions, and the program will no longer exit. This allows the scan to continue even if these errors occur. Errors are now logged at the error level, and the function allows the scan to proceed without exiting the Prowler.

Thanks for the changes @lshw54 ! I also change the error messages to follow our pattern.


driver: update Exoscale info

update Exoscale info
Description

update URL to .com
update data centers locations
use the current logo

Status
Ready
Checklist (tick everything that applies)

[ ] Code linting (required, can be done after the PR checks)
[x] Documentation
[ ] Tests
[ ] ICLA (required for bigger changes)

Codecov Report

Merging #1251 into trunk will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##            trunk    #1251   +/-   ##
=======================================
  Coverage   85.74%   85.74%
=======================================
  Files         356      356
  Lines       72369    72369
  Branches     6537     6537
=======================================
  Hits        62053    62053
  Misses       7715     7715
  Partials     2601     2601

Impacted Files
Coverage Δ

libcloud/compute/drivers/exoscale.py
100% <100%> (ø)
: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 888be05...a7c1672. Read the comment docs.

Sorry for the delay. I went ahead and merged this into trunk.
Thanks again for your contribution.


Prefix C-level functions to avoid collisions

This would only affect users who directly include bridgestan.h in a project, but it is useful (and fairly standard, I believe) to prefix C function names with a common string to avoid namespace issues that can arise in C. So, our C API would have functions like bs_name, while Python/Julia/R etc would still just use name.
I'm happy to make these changes, the question is just which prefix to use:

bs short, but commonly used for another meaning
stan - still short, stan_log_density etc all read naturally, but this isn't an official Stan project
bridgestan - most accurate and unambiguous, but very long

I like "bs", then "stan", then "bridgestan".

I’d say that’s my personal preference as well (hence my ordering in the original post).

I too agree with Brian's initial ordering.

I too agree with Brian's initial ordering.

That's good news because @WardBrian has already pushed the PR and I've already reviewed it.


chore: exclude .yaml file inside doc folder from sonar analysis

Description

Updated sonarcloud.properties to exclude all .yaml files within the docs folder and subdirectories.

Why
This change prevents non-code files from affecting the SonarCloud quality gate checks.
Issue
#1274
Checklist

[X] I have followed the contributing guidelines
[X] I have performed a self-review of my own code

Hi @shahmargi12 referring to eclipse-tractusx/portal-iam#207 (comment) sorry for the confusion, I meant to add such a .sonarcloud.properties in the portal-iam repo as part of this PR eclipse-tractusx/portal-iam#207, and just referenced to the portal-frontend repo as an example

Ok Sure, will do the same in portal-iam.


Ginlong Solis Inverter Datastick

Can't retrieve info:
[24/02/2021, 16:32:27] [Solis PV Inverter - Loft] {"lastSeen":1614180747975,"inverter":{"model":null,"serial":null,"firmwareMain":null,"firmwareSlave":null},"logger":{"serial":null,"version":null,"mode":null,"ap":{"ssid":null,"ip":null,"mac":null},"sta":{"ssid":null,"ip":null,"mac":null,"rssi":null}},"remoteServer":{"a":false,"b":false},"power":0,"energy":{"today":0,"total":0}}
This is de JSON reply I get manually, from the stick directly
{"g_sn":901990927,"g_ver":"ME-121001-V1.0.6(2016-10-111136)","time":1614181040,"g_time":28239,"g_err":0,"mac":"bc-54-f9-fa-ee-ca","auto_ip":0,"ip":"<IP_ADDRESS>","sub":"<IP_ADDRESS>","gate":"<IP_ADDRESS>","auto_dns":0,"dns":"<IP_ADDRESS>","dns_bak":"<IP_ADDRESS>","i_status":16,"i_type":1281,"i_num":1,"i_sn":"0003700171073020","i_ver_m":"","i_ver_s":"","i_modle":"","i_pow":"","i_pow_n":475,"i_eday":"19.10","i_eall":"22202.0","i_alarm":"","i_last_t":0,"l_a_agr":0,"l_a_ip":"<IP_ADDRESS>","l_a_port":10000}
This is the config:
{
"name": "Solis PV Inverter - Loft",
"username": "",
"password": "",
"hostname": "<IP_ADDRESS>",
"interval": 30,
"accessory": "Solis PV Inverter Homebridge Plugin"
}

Hi @bartgabriels, unfortunately it seems Solis have changed the message format between datastick  fw versions. I don't actually perform the processing within this project, but instead rely on fss/solis-inverter. I suggest you raise an issue with the upstream project.


ci: deploy Lambdas via GitHub Actions

@smauermann Ping me when the PR is ready for review

@Blightwidow @skenmy please have another look, cheers


afew: add module

Afew is an initial tagging script for notmuch mail. This module can be used like so:
{
  programs.afew = {
    enable = true;
    extraConfig = builtins.readFile ./afew.ini;
  };
}

Where afew.ini is the config file for afew.

also you may want to add it to modules/misc/news.nix

Okay, news item and example added.

Robert Helgesson<EMAIL_ADDRESS>writes:

rycee commented on this pull request.

+{ config, lib, pkgs, ... }:

+with lib;
+
+let

cfg = config.programs.afew;
configFile = ''

Generated by Home Manager.

See https://afew.readthedocs.io/en/latest/index.html

${cfg.extraConfig}
'';
+in
+{
options.programs.afew = {
enable = mkOption {

enable = mkEnableOption "the Afew initial tagging script for Notmuch";

Ah, wasn't aware of this. Fixed in 125da0330d4e14fd7fb0c28dc3a8b1525fe3221a

Rebased to master in 061c7b633f66ff73b281f08991c6c0a541877e66. Thanks!


Add content-type application/octet-stream

We use Amazon S3 bucket for hosting websites. After dynamically uploading the files when a create a build, the Content-Type by default is set to binary/octet-stream by system defined.

is it possible to add content-type application/octet-stream font support?

@AhmedBG


Fix the QR code link with the correct value in the documentation

Problem
The docs are still not pointing to project-chip gh-pages branch
Change overview
Update the QR code link in the documents
Testing
NA

@woody-apple I think we would need this PR to be cherrypicked in the SVE branch too as the code in there actually uses project-chip link but the documentation doesn't point to that. :-)


Feature importance

To enhance interpretability, I implemented feature_importance methods and used them in the notebooks.

@mayagos please have a look and merge if it's OK


aot snapshot file is being held/locked by dart_precompiled_runtime on Windows for duration of dart program execution

https://github.com/dart-lang/sdk/blob/18c0a39f672f0df29d93f346c03811f11e9fa5a3/runtime/bin/elf_loader.cc#L152 is kept
as part of Mappable https://github.com/dart-lang/sdk/blob/18c0a39f672f0df29d93f346c03811f11e9fa5a3/runtime/bin/elf_loader.cc#L595, LoadedElf https://github.com/dart-lang/sdk/blob/18c0a39f672f0df29d93f346c03811f11e9fa5a3/runtime/bin/elf_loader.cc#L610 that is kept in https://github.com/dart-lang/sdk/blob/18c0a39f672f0df29d93f346c03811f11e9fa5a3/runtime/bin/main_impl.cc#L1211 global for duration of program execution
cc @rmacnak-google

The change below seems to fix the problem:
diff --git a/runtime/bin/elf_loader.cc b/runtime/bin/elf_loader.cc
index ff44319e339..70baa9c142a 100644
--- a/runtime/bin/elf_loader.cc
+++ b/runtime/bin/elf_loader.cc
@@ -289,6 +289,8 @@ bool LoadedElf::Load() {
   CHECK(ReadSectionStringTable());
   CHECK(ReadSections());

+  mappable_.reset();
+
   return true;
 }


[Event Request change] - Codeunit 5720 Item Reference Management

Hi,
There is an event as below in the codeunit:
[IntegrationEvent(false, false)]
local procedure OnPurchaseReferenceNoLookUpOnAfterSetFilters(ItemReference: Record "Item Reference"; PurchaseLine: Record "Purchase Line")
begin
end;
Item Reference parameter in the above event should be as var.
Can you please look into this and change ASAP?
Thanks & regards
Varun Reddy

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Bug in GPCoregularizedRegression constructor

The constructor takes W_rank as an argument, but it's never used anywhere. Presumably it's supposed to set W_rank for the default kernel if a custom one is not provided, but instead we have
if kernel is None:
    kernel = kern.RBF(X.shape[1]-1)

    kernel = util.multioutput.ICM(input_dim=X.shape[1]-1, num_outputs=Ny, kernel=kernel, W_rank=1,name=kernel_name)

Either this should be changed to
    kernel = util.multioutput.ICM(input_dim=X.shape[1]-1, num_outputs=Ny, kernel=kernel, W_rank=W_rank,name=kernel_name)

or W_rank should be removed from the constructor's argument list. Thanks!

It seems to be a bug. Thanks for spotting it. Would you mind creating a pull request to fix it?

The pull request has been merged. Thanks!


Fix argument testing in homeshick.fish

Hi,
just noticed a small bug in the fish wrapper, which causes it to print error message when invoked without arguments. This PR adds an unit test, and fixes the issue.
Thanks for this cool project BTW!

@herrbischoff, could you sign off on this? Seems OK to me, but I am on vacation right now, hence the slow response time and the inability to test :-)

LGTM 👍

Cool! Merging.
Thank you @psliwka!


Variants Reference

RFC feature description
https://github.com/mincho-js/working-group/blob/main/text/001-css-nesting.md#7-variants-reference
The solution I'd like
Implement similarly to #46
Screenshots or video
No response
Alternatives I've considered
No response
Additional context
No response

merged.


feat(rollup) Add ts plugin for better style components experience

Original PR by @maciekgrzybek

install and add typescript-plugin-styled-components to the rollup config
plugins creates better developer experience by adding meaningful class names

This will be great. Major improvement for debugging styles.

ermagerrd this is so much better

@all-contributors please add @maciekgrzybek for builds

@all-contributors please add @maciekgrzybek for build

apparently that's not a thing
@all-contributors please add @maciekgrzybek for infra


[Bug]: Need Improvement in the Footer section

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Need improvement in the Footer section for the better look

Expected behavior
The Footer should be more impressive and with the proper links availabe to it.
Add ScreenShots
No response
What browsers are you seeing the problem on?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Refer to the main website link @Ankur-Rai-19


It CRASHES!

I just got a new mod but when I try to open up block lancher it loads then 3 seconds after I open the app it says "Unfortunately Block Lancher has stopped working please try again" I try 1000 times and the same thing happens!

Jesus! It takes 2-3 weeks to finalize the update!

Plz, close this report because, were spending more time dealing with reports than fixing Blocklauncher.
Thx!

@PrincessRuby80 what version of Minecraft and Block Launcher are you using?  If you can't get BL to load, you can go into the Play Store and you can then see the version by looking at the app in the store.


Fix some typos

Fix some typos:
Similarily -> Similarly
ommited -> omitted
Signed-off-by: Rui Cao<EMAIL_ADDRESS>

/ok-to-test
/lgtm


Preflight: GPS check

Adds additional checks to make sure the GPS receiver is working as it should:

Makes the Preflight check fail if CBRK_GPSFAIL is not enabled and there is no GPS module connected to the Pixhawk.

Commander will warn the user if there is excessive signal-to-noise ratio detected on the GPS receiver (more than 40% noise per millisecond). This check is only done while the drone is disarmed.

Flight log with GPS signal interference
http://dash.oznet.ch/view/Zb9wUAEgeCcL2Se6hD6j8Y (note GPS.N is below 50%, normally it should be around 80% to operate normally)
The position glitch at the end is caused by eventually GPS loss (it is supposed to hold position in windy conditions)
Flight Log with interference fixed
http://dash.oznet.ch/view/sc7bjcnnzHBWU4DWixVs2Y

@tumbili Please add to your testing. Looks useful and probably should make it still into the release.

This is only tested with a UBlox GPS. It could be that the other GPS driver types need more time to boot/initialize before they are detected.

@Zefz @LorenzMeier Tested this yesterday, looks good.

Please wait before merging, I think I got a false positive for missing GPS and I am looking into why this happens.

@Zefz The GPS driver only starts to publish once it has position data / is synced to the GPS receiver if I recall correctly, but your implementation looks like it assumes data from the GPS module once booted, not once locked. I think you need you need to differentiate between the pre-arm check and the preflight check. The system should not go into a lock state if no GPS lock is present yet.

I discovered that the GPS driver can sometimes use up to 3 seconds to initialize, so increasing the poll timeout from 1 second to 4 seconds seems to have done the trick.
@LorenzMeier: The GPS driver does not require a fix to publish data. It will publish "no fix" messages before it has fix as well.
This of course means that if GPS module is missing or broken the Preflight check can block up to 4 seconds. But this is intended as the gps_check_circuit_breaker makes sure that the system cannot enter a ready-to-fly state unless all sensors are present and working (now including the GPS).
Without this check the system will boot and signal no error even without the GPS working at all. (so this optional stricter check makes sure that you haven't forgotten to plug in GPS or have a broken GPS module plugged in)

Note: The circuit-breaker for GPS check is enabled by default, so you have to disable the circuit-breaker to enable this check.

With a minor change to the GPS driver, we can detect that the driver is working correctly much sooner, allowing a significant shorter timeout on the preflight check.

Can we just stay in the init state but not block in the check until either the GPS is there or the timeout had passed? Reason being that we try to get to a point where we can do in-air restore and all hidden block / sleep calls can be an issue.

I think the GPS check should be skipped in an in-flight restore. What do you do anyways if a pre-flight check fails in-flight? Then the system cannot arm itself anyways?
One of the purposes of the preflight check is to give the user feedback that the system is ready to fly, so it doesn't make much sense to run the preflight check if we are doing an in-air restore?

So this is good to go now?

Yes, I rebooted the Pixhawk 30 times to verify that it worked each time.
Furthermore I tested the noise level detection works correctly by putting the RC module and antennas basically on top of the GPS antenna.
The only thing that might need to be done is your suggestion of not running the GPS check on in-air restore (is there a way the commander knows this before the Preflight check is run?)

@Zefz Hi, it looks like you know a lot about GPS. We have recently got a few warnings of noisy GPS signal, and we are now investigating it. However, we still have a few open questions, and it'd be great if you could help us and answer them (either here or privately if you wish):

What is actually noise per millisecond? I see that it's clearly related to SNR, but I could not find how and why it is separate from SNR.
How does it relate to SNR?
You mentioned you tested it by putting RC module and antennas on top of it - does telemetry can have similar effect?


Call out how write:packages requires repo scope on PATs

Why:

Closes #2660
What's being changed:
The docs used to recommend removing repo scope when creating a PAT with write:packages, but it's not possible. So, clearly call that out, and when linking to the security best practices, also call out which practice to follow.

Check off the following:

[ ] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[x] For content changes, I have reviewed the localization checklist (feels wordy)
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

I see in the preview that the warning appears twice.

I don't know the best way to get it to appear only once when both reusables are included in the same page. Should I worry about the warning appearing when either reusable appears by itself? If not, which reusable should the warning appear in?
I feel like, if it appears in only one place, it should be in reusables.package_registry.authenticate_with_pat_for_container_registry  and not data reusables.package_registry.authenticate-to-container-registry-steps (matching where the original warning appeared)

@dgholz Thanks so much for opening a PR! I'll get this triaged for review ⚡

Note: Since this PR was opened there have been some changes to this feature. GitHub Container Registry now supports using the GITHUB_TOKEN for GitHub Actions workflows, which improves the security experience here since users don't have to rely on a PAT in a workflow.
I also noted a workaround for only selecting the write:packages scope with this url: https://github.com/settings/tokens/new?scopes=write:packages.


Dual inclusion of raylib.h

This isn't necessarily an issue. I just wanted to summarize a couple of things here.
Currently there are two versions of raylib.h available to the examples at compile time. The older version is found at release/include/raylib.h alongside release/libs/linux/libraylib.a . I believe the purpose of these and some other object files is to enable immediate interaction with the examples without building libraylib locally. Additionally, a more current version is available at src/raylib.h. This is the one that is built against when making raylib. The difference is in the definition of GenImagePerlinNoise. The actual function isn't relevant here, and with proper use, this isn't a serious problem. It's actually useful for inspecting the inner workings of the toolchain.
The problems occurring with RAYLIB_LIBTYPE=SHARED have, I think, been sorted out in #480 by addressing the precedence of INCLUDE_PATHS components within examples/Makefile.
On the RAYLIB_LIBTYPE=STATIC side, there is still one case where it is problem. If someone fails to src/$ make clean the provided release/libs/linux/libraylib.a before src/$ make, libraylib.a will compile but the conflict of objects/headers? throws an immediate error on GenImagePerlinNoise in the same examples/textures/textures_image_generation compilation step that was showing the precedence issue with RAYLIB_LIBTYPE=SHARED in examples/Makefile. The easiest solution is to just tell everyone make clean up front. There is now a visual message suggesting to do so during plain ole src/$ make, also in PR480.
I'm not suggesting that the files should match. I'm sure there are good reasons for having a seperate release/ "package" and I would not have been able to diagnose these issues without the errors exposed here. Anyway, just pointing this out because I love to read my own stuff. ;^)

I need to update release/ libs at some point, now that we only have a single master branch they should be latest stable version all the time...

If it's just a matter of copying src/raylib.h to release/include/raylib.h and rebuilding libraylib.a, I can put it in #480.


x-axis is not rounded correctly

For some datasets, I am getting x-axis values that are not rounded correctly (in a way that looks like JavaScript math issues):

I'm using the following data:
[{"x":0.13372623292811447,"y":8730.31524},{"x":0.13767990338492847,"y":8730.31524},{"x":0.14021854318724314,"y":8730.31524},{"x":0.14459258531430835,"y":8733.59608},{"x":0.14800638604875163,"y":8733.59608},{"x":0.15206944322541138,"y":8733.59608},{"x":0.15589290660094193,"y":8730.31524},{"x":0.15860517763068477,"y":8730.31524},{"x":0.16360614955208888,"y":8730.31524},{"x":0.16629781423563672,"y":8730.31524},{"x":0.16899335460828133,"y":8730.31524},{"x":0.17372068269523036,"y":8730.31524},{"x":0.17733982284321775,"y":8717.19188},{"x":0.18057300786272124,"y":8717.19188},{"x":0.18574030211043183,"y":8717.19188},{"x":0.18778633875369594,"y":8717.19188},{"x":0.19259757534779726,"y":8707.34936},{"x":0.19453529666066735,"y":8707.34936},{"x":0.19924344686698048,"y":8707.34936},{"x":0.20178002970220332,"y":8707.34936},{"x":0.2042674345250027,"y":8707.34936},{"x":0.209027041453048,"y":8707.34936},{"x":0.21327188430386196,"y":8710.6302},{"x":0.2177737369627652,"y":8710.6302},{"x":0.2218624072771569,"y":8710.6302},{"x":0.22667147355165565,"y":8713.911039999999},{"x":0.2321813063785132,"y":8717.19188},{"x":0.23877503918494336,"y":8717.19188},{"x":0.2441586917489518,"y":8717.19188},{"x":0.24945764943397827,"y":8717.19188},{"x":0.25370822690092737,"y":8717.19188},{"x":0.25641857274100627,"y":8723.75356},{"x":0.25882780470735706,"y":8723.75356},{"x":0.2638082071705127,"y":8723.75356},{"x":0.26664587966783404,"y":8723.75356},{"x":0.26832477299566954,"y":8723.75356},{"x":0.2733579972806675,"y":8723.75356},{"x":0.2752776761027687,"y":8723.75356},{"x":0.2783734024377751,"y":8723.75356},{"x":0.28245611072583077,"y":8723.75356},{"x":0.28775145529811513,"y":8723.75356},{"x":0.2903362806708258,"y":8723.75356},{"x":0.2941538236063945,"y":8723.75356},{"x":1.5444990373775116,"y":8723.75356},{"x":1.5491845904068675,"y":8723.75356},{"x":1.5521358745099059,"y":8723.75356},{"x":1.555886284512655,"y":8723.75356},{"x":1.5609847665625602,"y":8723.75356},{"x":1.565241070919272,"y":8723.75356},{"x":1.5697297636333833,"y":8723.75356},{"x":1.5722594778320198,"y":8723.75356},{"x":1.5747300377331137,"y":8723.75356},{"x":1.5798770891728646,"y":8723.75356},{"x":1.5864565572467677,"y":8717.19188},{"x":1.5922122694191871,"y":8717.19188},{"x":1.5978949674875182,"y":8717.19188},{"x":1.6032786200515268,"y":8717.19188},{"x":1.6081509473155968,"y":8713.911039999999},{"x":1.614573037723672,"y":8713.911039999999},{"x":1.6207216268428868,"y":8710.6302},{"x":1.6262786256801522,"y":8707.34936},{"x":1.6316034600548248,"y":8707.34936},{"x":1.636508530865456,"y":8707.34936},{"x":1.6416592994422725,"y":8707.34936},{"x":1.6463744659946031,"y":8717.19188},{"x":1.6512891049183542,"y":8717.19188},{"x":1.6553799024220655,"y":8717.19188},{"x":1.6590558075069963,"y":8717.19188},{"x":1.6609926306871121,"y":8717.19188},{"x":1.663144766237228,"y":8730.31524},{"x":1.6649006568403961,"y":8730.31524},{"x":1.6676788431357485,"y":8730.31524},{"x":1.6695628421863549,"y":8730.31524},{"x":1.6737140159392359,"y":8730.31524},{"x":1.6764371706684351,"y":8730.31524},{"x":1.6785244605036236,"y":8730.31524},{"x":1.6806741692885814,"y":8730.31524},{"x":1.684736369912649,"y":8733.59608},{"x":1.687551882372338,"y":8733.59608},{"x":1.6897834004559997,"y":8733.59608},{"x":1.6923438784223217,"y":8730.31524},{"x":1.6947079104944547,"y":8730.31524},{"x":1.6972293576311177,"y":8730.31524},{"x":1.7019078499031963,"y":8730.31524},{"x":1.7039884603937856,"y":8730.31524}]
with an XYPlot that looks like this:
   <XYPlot width={620} height={190}>             <XAxis               labelFormat={v =>${v} mi.}             />             <YAxis               labelFormat={v => ${v} ft.}             />             <AreaSeries marginLeft={70} marginTop={20} fill="#9DC7F1" color="#7CB5EC" opacity="0.9" data={this.getElevationData()}/>     </XYPlot>

Hey 	@timfpark!
I understood your point, but it doesn't seem to be the problem on our side. You get the value in labelFormat function which is not formatted at all. This means, that your function is responsible for formatting this value. Precision issues in JavaScript are quite common, you should format the number first and after that append the "mi." in the end.
I also highly suggest to check out the latest version of react-vis: some of the formatting issues are gone there (please take a look at the list of changes first).


[no issue]fixed bug that exception is not handled in HttpSensor

Dear Airflow Maintainers,
Please accept this PR that addresses no issues.
If exception happens in poke function in HttpSensor, it is not
well handled that make the sensor finish successfully, which is
incorrect obviously.

Thanks for the contribution! You need to create a jira as per specs. This is a requirement by apache. Next to that please update your commit message to follow the guidelines (imperative title)


A number of typos in the Documentation

There's a number of typos on this page:
https://www.npmjs.com/package/homebridge-cmd4
I've detailed them for you below.
Section "About the Cmd4 Plugin"
Typo in "Similiar to other command plugins,"
Similiar is wrong. It should be Similar
Typo in "but now they can appear as a Garage Door openner"
openner is wrong. It should be opener
Typo in "and you can cntrol all of their characteristics too."
Cntrol is wrong. It should be control
Section "Features"
Typo in "Cmd4 supports, Lights, Garage Door Openners"
Openners is wrong. It should be Openers
Typo in "so that accessories like a garage door is updated in HomeKit after it was closed or openned."
openned is wrong. It should be opened
Typo in "Cmd4 can be configured to respond to actual devices directly or by modofying the script file it calls"
modofying is wrong. It should be modifying
Section "Whats new in 2.2"
Typo in "This release also defines constants for all thecharacteristics "
thecharacteristics is wrong. It should be the characteristics
Section "Installation"
Typo in Step 5 "SHELL> homebrige"
homebrige is wrong. It should be homebridge
Typo in Step 6 "The gist of it is that you entet the manual code"
entet is wrong. It should be enter
Section "Troubleshooting"
Typo in Step 1 "is expected to run from a users home "
users is wrong. It should be user's
Section "Adding in fakegato-history"
Typo in Step 3 "enable polling and interval for the accesory"
accesory is wrong. It should be accessory
Typo in Step 3 "according to the fakegato-hitory documents "
hitory is wrong. It should be history
Section "Raspbian-Stretch"
Typo in Step 2 "Os.tmpDir() is depricated"
depricated is wrong. It should be deprecated
Typo in Step 3 "commentiing out the others and save the file"
commentiing is wrong. It should be commenting
Typo in Step 4 "Update sources or you wil not be able to download "
wil is wrong. It should be will
Typo in Step 5 "It ahould return >=8.11.1"
ahould is wrong. It should be should
Section "Unit Testing"
Typo in Step 1 "This is done seperate from the"
seperate is wrong. It should be separate
Typo in Step 3 "Install homebridge-cmd4 development dependancies"
dependancies is wrong. It should be dependencies
Section "Rationale"
Typo in Step 3 "If you were wondering what happenned to version 3"
happenned is wrong. It should be happened

Hi,
My wife thanks you!  I will fix them shortly.  I should add spell check
to my vi sessions.
John
On Sun, Jul 19, 2020 at 2:44 AM jsiegenthaler<EMAIL_ADDRESS>wrote:

There's a number of typos on this page:
https://www.npmjs.com/package/homebridge-cmd4
I've detailed them for you below.
Section "About the Cmd4 Plugin"
Typo in "Similiar to other command plugins,"
Similiar is wrong. It should be Similar
Typo in "but now they can appear as a Garage Door openner"
openner is wrong. It should be opener
Typo in "and you can cntrol all of their characteristics too."
Cntrol is wrong. It should be control
Section "Features"
Typo in "Cmd4 supports, Lights, Garage Door Openners"
Openners is wrong. It should be Openers
Typo in "so that accessories like a garage door is updated in HomeKit
after it was closed or openned."
openned is wrong. It should be opened
Typo in "Cmd4 can be configured to respond to actual devices directly or
by modofying the script file it calls"
modofying is wrong. It should be modifying
Section "Whats new in 2.2"
Typo in "This release also defines constants for all thecharacteristics
"
thecharacteristics is wrong. It should be the characteristics
Section "Installation"
Typo in Step 5 "SHELL> homebrige"
homebrige is wrong. It should be homebridge
Typo in Step 6 "The gist of it is that you entet the manual code"
entet is wrong. It should be enter
Section "Troubleshooting"
Typo in Step 1 "is expected to run from a users home "
users is wrong. It should be user's
Section "Adding in fakegato-history"
Typo in Step 3 "enable polling and interval for the accesory"
accesory is wrong. It should be accessory
Typo in Step 3 "according to the fakegato-hitory documents "
hitory is wrong. It should be history
Section "Raspbian-Stretch"
Typo in Step 2 "Os.tmpDir() is depricated"
depricated is wrong. It should be deprecated
Typo in Step 3 "commentiing out the others and save the file"
commentiing is wrong. It should be commenting
Typo in Step 4 "Update sources or you wil not be able to download "
wil is wrong. It should be will
Typo in Step 5 "It ahould return >=8.11.1"
ahould is wrong. It should be should
Section "Unit Testing"
Typo in Step 1 "This is done seperate from the"
seperate is wrong. It should be separate
Typo in Step 3 "Install homebridge-cmd4 development dependancies"
dependancies is wrong. It should be dependencies
Section "Rationale"
Typo in Step 3 "If you were wondering what happenned to version 3"
happenned is wrong. It should be happened
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/61, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4KQUGBYPTIZGWH44LR4KI6TANCNFSM4PA6FK3Q
.

Fixed under commit 3f36727.   I'm not actually that bad.  I do need an operation on my eyes, but I would not let the surgeon go near them. So I'll blame it on that.  I do very much appreciate you checking it though. Thanks again.

You are welcome. I had both eyes operated over the last few years. Scary but better afterwards.

You are braver than I was.  I was in the chair with one eye clamped open
and then bailed as they were bringing the scraper towards my eyeball.
TTFN,
John
On Mon, Jul 20, 2020 at 6:46 AM jsiegenthaler<EMAIL_ADDRESS>wrote:

You are welcome. I had both eyes operated over the last few years. Scary
but better afterwards.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/61#issuecomment-660952104,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4QS54SQYOM6P4SKMTR4QN6TANCNFSM4PA6FK3Q
.


After upgrading to React-Native 0.56.0 metro build fails (TypeError: Cannot read property 'ast' of null)

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
Run react-native info in your terminal and paste its contents here.
  React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.5
      CPU: x64 Intel(R) Core(TM) i5-5287U CPU @ 2.90GHz
      Memory: 45.86 MB / 8.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 8.11.3 - ~/.nvm/versions/node/v8.11.3/bin/node
      Yarn: 1.7.0 - /usr/local/bin/yarn
      npm: 5.6.0 - ~/.nvm/versions/node/v8.11.3/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
      Android SDK:
        Build Tools: 23.0.1, 25.0.1, 26.0.2, 27.0.3, 28.0.0
        API Levels: 23, 25, 26, 27
    IDEs:
      Android Studio: 3.1 AI-173.4819257
      Xcode: 9.4/9F1027a - /usr/bin/xcodebuild
    npmPackages:
      react: 16.4.1 => 16.4.1
      react-native: 0.56.0 => 0.56.0
    npmGlobalPackages:
      react-native-cli: 2.0.1

Description
After upgrading to react-native version 0.56.0 my metro build fails with the error message TypeError: Cannot read property 'ast' of null.
I also read this issue #19827 but could not fix my issue with the suggestions there.
From the error message it seams the bug is in the metro src.
Detailed error message:
error: bundling failed: TypeError: Cannot read property 'ast' of null
    at Object.transform (/Users/david/projects/churchtools-mobile/node_modules/metro/src/reactNativeTransformer.js:167:48)
    at Object.<anonymous> (/Users/david/projects/churchtools-mobile/node_modules/metro/src/JSTransformer/worker.js:204:23)
    at Generator.next (<anonymous>)
    at step (/Users/david/projects/churchtools-mobile/node_modules/metro/src/JSTransformer/worker.js:328:291)
    at /Users/david/projects/churchtools-mobile/node_modules/metro/src/JSTransformer/worker.js:328:521
    at new Promise (<anonymous>)
    at Object.<anonymous> (/Users/david/projects/churchtools-mobile/node_modules/metro/src/JSTransformer/worker.js:328:202)
    at Object.transformCode [as transform] (/Users/david/projects/churchtools-mobile/node_modules/metro/src/JSTransformer/worker.js:292:93)
    at execMethod (/Users/david/projects/churchtools-mobile/node_modules/jest-worker/build/child.js:90:29)

Do you have ignore section in your .babel.rc by any chance? It doesn't work for me well (config gets unresolved, and babel transformation fails), so I removed this section for now. Probably also need to test with newer babel / metro and file an issue.

Wish there was a solution for this. Ignore was working for me before I upgraded my babel from beta.47 to 7.0.0. Issue is with React-Native 0.57.0 too.

This looks like a bug in metro. I found a patch that fixes it: https://github.com/facebook/metro/issues/255#issuecomment-423819590


bot can't reply after several hours

bot can't reply after several hours.but It works if I restart the bot.

Could you post some example code?

var Botkit = require('botkit');
var tuling = require('./tuling')

var entry = {
  run:run
}

function run(){
  var controller = Botkit.slackbot({
    debug: process.env.debug || false
    //include "log: false" to disable logging
    //or a "logLevel" integer from 0 to 7 to adjust logging verbosity
  });

  controller.spawn({
    token: process.env.token,
  }).startRTM()

  controller.on('direct_message',function(bot,message){
    var body = tuling.reply(message.text);
    bodyJson = JSON.parse(body)
    bot.reply(message,bodyJson.text);
  })
}

module.exports = entry

@peterswimm any ideas

@spywhere I'll check it. thank you ~

@ringtail Did that solve your issue?

@peterswimm I solved it by restarting it when it is down.

You can actually specify the number of retries when you spawn your bot (how many times it will try to reconnect if it loses current connection)
I usually set mine to something like 500 or 1000
controller.spawn({
    token: process.env.token,
    retries: 500
  }).startRTM()

There should be better documentation on this..

@YemSalat Instead of increasing the retry count, detecting network changes should be the solution in this case.

@anonrig I borrowed the solution from here: https://github.com/howdyai/botkit/issues/104
Why do you think this case can not be solved by specifying the number of retries?

@YemSalat ,
The config property name of retries should be retry, I think.
code
https://github.com/howdyai/botkit/blob/master/lib/Slackbot_worker.js#L24
doc
https://github.com/howdyai/botkit/blob/master/readme-slack.md#controllerspawn

In some cases, using a finite number of tries, will not be possible. Because one can't determine the amount of time it requires to try to reconnect, because this problem is not based on the amount of tries but based on the change of the network adapter. Therefore, I suggest detecting the network changes and act upon if it is connected.

@anonrig Note that you can use Infinity for the value of 'retry'. (Indeed it's 'retry', not 'retries').
From Slackbot_worker.js:

// config.retry, can be Infinity too
var retryEnabled = bot.config.retry ? true : false;
var maxRetry = isNaN(bot.config.retry) || bot.config.retry <= 0 ? 3 : bot.config.retry;

My bots randomly all disconnect at the exact same time - this happens even after moving the bots to a different box running a different OS. These disconnects occur every 1-3 days, almost always overnight, and may be tied to slack server maintenance windows for all I know.
@anonrig If the preferred behavior is to respond to network changes, can you provide a simple working example of a bot reconnecting itself?

#261 might be helpful.

Was noticing the same problem and realized slack was closing the rtm connection or the overall connection had dropped. There is a bug in how the retry attributes are defined and used which causes the retry logic to fail.
https://github.com/howdyai/botkit/pull/532
Reconnect has been working flawlessly since.  I also use this code for slack notifications on RTM close and reconnect failures. Hope this helps.
console.log('\n\n*** '+moment().tz('America/Los_Angeles').format()+' ** The RTM api just closed');

try {
controller.findTeamById('<SLACK_TEAM_ID_HERE>', function(err, team) {
var alertBot = controller.spawn(team);
alertBot.api.chat.postMessage(
{
channel : '<SLACK_CHANNEL_ID_HERE>',
text: 'GUYS!!! I just got an RTM Close event trigger for this team --> '+bot.team_info.id+' '+bot.team_info.name+' .',
attachments: [],
}, function (err, response) {
});
});
} catch (err) {
console.log('\n\n*** '+moment().tz('America/Los_Angeles').format()+' Tried to send alert for an rtm_close event but failed with this error: '+err);
}
});

controller.on('rtm_reconnect_failed',function(bot) {
console.log('\n\n*** '+moment().tz('America/Los_Angeles').format()+' ** Unable to automatically reconnect to rtm after a closed conection.');

try {
controller.findTeamById('<SLACK_TEAM_ID_HERE>', function(err, team) {
var alertBot = controller.spawn(team);
alertBot.api.chat.postMessage(
{
channel : '<SLACK_CHANNEL_ID_HERE>',
text: 'GUYS!!! I just got an RTM Reconnect Failed trigger for this team --> '+bot.team_info.id+' name: '+bot.team_info.name+'. The team either uninstalled the app or there was an issue which requires a resart of the bot.',
attachments: [],
}, function (err, response) {
});
});
} catch (err) {
console.log('\n\n*** '+moment().tz('America/Los_Angeles').format()+' Tried to send alert for an rtm_reconnect_failed event but failed with this error: '+err);
}
});


Make UML Diagram

https://marketplace.visualstudio.com/items?itemName=jebbs.plantuml
That´s a lightweight tool to get it running and in version control

closed with  05ee248


Installing gotk3 on Windows 10 (msys2)

I've been trying to install gotk3 for the past few days now, and I'm getting this error:
go\src\github.com\gotk3\gotk3\glib\application.go:157:2: could not determine kind of name for C.g_application_send_notification go\src\github.com\gotk3\gotk3\glib\application.go:165:2: could not determine kind of name for C.g_application_withdraw_notification cgo: gcc errors for preamble: In file included from go\src\github.com\gotk3\gotk3\glib\application.go:7: ./glib.go.h:95:8: error: unknown type name 'GNotification'  static GNotification *         ^~~~~~~~~~~~~  when running go get github.com/gotk3/gotk3/gtk
I've followed the guide (using old Fedora 20 rpms, and using msys2 to install mingw because the links in the guide don't work)
My path has C:\Fedora, the gopath and gohome, and it has the msys2/mingw64/bin folders.

I'd say your version of glib is outdated.
Check this out: https://github.com/UwUNote/uwunote/issues/1#issuecomment-414850043

I have updated the guide on the wiki, it should work now if you follow that:
https://github.com/gotk3/gotk3/wiki/Installing-on-Windows


Add stream schema cli

add cli commands for stream schema related operations.
to fix: run stream schema ginkgo tests together may fail.

@sacloudy Please fix issues raised by the checkers

Most cases failed to expect the first one. This might relate to the following place:
https://github.com/apache/skywalking-banyandb/blob/main/banyand/liaison/http/server.go#L125
The HTTP server blocks and the GracefulStop doesn't contain any operation to stop the server. Would you please use http.Server instead of http.ListenAndServer ?

Codecov Report

Merging #165 (3bf0cda) into main (945857d) will decrease coverage by 0.40%.
The diff coverage is 44.06%.

@@            Coverage Diff             @@
##             main     #165      +/-   ##
==========================================
- Coverage   53.52%   53.12%   -0.41%
==========================================
  Files          86       90       +4
  Lines        7869     8275     +406
==========================================
+ Hits         4212     4396     +184
- Misses       3262     3433     +171
- Partials      395      446      +51

Impacted Files
Coverage Δ

banyand/metadata/schema/group.go
61.66% <0.00%> (ø)

bydbctl/internal/cmd/use_group.go
25.92% <25.92%> (ø)

banyand/metadata/schema/stream.go
46.29% <40.00%> (-0.65%)
:arrow_down:

bydbctl/internal/cmd/stream.go
41.69% <41.69%> (ø)

bydbctl/internal/cmd/group.go
47.69% <47.69%> (ø)

bydbctl/internal/cmd/root.go
58.33% <50.00%> (+58.33%)
:arrow_up:

banyand/measure/service.go
73.33% <100.00%> (ø)

banyand/stream/service.go
65.78% <100.00%> (-0.45%)
:arrow_down:

bydbctl/internal/cmd/bydb_cmd.go
100.00% <100.00%> (ø)

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


chore(chaosengine): adding imagePullSecrets & resource in engine-concepts

Signed-off-by: shubhamchaudhary<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Checklist:

[ ] Fixes #
[ ] Labelled this PR & related issue with documentation tag

We can also include spec.component.args - it is missing right now

PR has been updated with review comments. LGTM


Allow inheritance from standard cells

Move the code creating the KCell from __call__ for _kcell.
This will allow to make inheritance.
E.g.
```Create a post-processed waveguide```
import kfactory as kf

class TestBendEuler(kf.cells.euler.BendEuler):  # type: ignore[unused-ignore, misc]
    def __init__(self) -> None:
        super().__init__(kf.kcl)

    @kf.cell  # type: ignore[misc, unused-ignore]
    def __call__(self, width: float) -> kf.KCell:  # type: ignore[override, unused-ignore]
        c = self._kcell(
            width=width,
            radius=30,
            layer=LAYER.WG,
            enclosure=wg_enc,
            angle=90,
            resolution=150,
        )
        c.info.creation_time = "2023-02-12Z23:00:00"

        return c

# could also use bend_euler = TestBendEuler()
bend = TestBendEuler()(width=1)

@joamatab

not really, this seems overly complicated

You have to choose, either make it inheritable as a class or use no decorator.
With this you now have three choices:

The above
my_kcell.dup() (needs name change to avoid collision, i.e. doesn't change the cached KCell)
use e.g. kf.cells.straight.straight._kcell(...) to get the uncached version directly and wrap that in a @cell decorator to cache (this will not set all settings though, only the ones passed to the new function with @cell)

I can't give you something to inject a post_process into an existing function. At that point, just unlock the cell and modify it, it's the same as if you were grabbing kwargs from the footprint of the function.

then, l prefer keeping the cell decorator as it is and then passing an explicit post_process function
https://github.com/gdsfactory/gdsfactory/pull/2524


feat: support configuring local walrus env

Refer to https://github.com/seal-io/docs/pull/191/files for the UX.
Related Issue:
https://github.com/seal-io/walrus/issues/2062

the --env-file is syntactic sugar that loads the env vars from a file without specifying --env one by one, which means modifying local.env also cannot update the existing container's running options after docker restart. we can verify this by docker inspect.
if so, I suggest supporting something like this: SERVER_foo walrus local install/reinstall, and also give a fixed docker network to avoid the IP change after reinstall. See https://github.com/seal-io/walrus/pull/1999.
to implement this, we can filter out the env vars from os.Environ with SERVER_ prefix, and lock the special env vars we need, like SERVER_ENABLE_AUTHN and SERVER_SETTING_LOCAL_ENVIRONMENT_MODE, finally, inject the filter list into cmd.Env.


Add ctx.wrappers array

Goes along with koajs/compose#52.

Copied from another conversation:
If we implement this, I'd be in favor of removing the deprecated generator to promise conversion in favor of koa-convert providing a wrapper to convert generators to promise-based middleware. I think that would be the more versatile approach, as some people might want to use generators with the new argument syntax until async/await arrives. The current approach would convert them as if they took ctx as this instead of an argument, and you'd have to extend the Koa Application to change that.

also see https://github.com/koajs/compose/pull/51

would really love more people to express their opinions, otherwise, I'm inclined to just merge it!

This and #707 preform the same purpose different ways, so only one should be merged. Do you prefer this one?

I'll just close this as it has little relevance today IMO. Maybe there's still a need for wrappers but I doubt it personally and the same functionality can be approached in user land. Also, over the years I haven't really seen any requests for wrappers. If I remember correctly, this was brought to light due to TJ's original issue to simplify mw profiling, though today this can be solved with async_hooks which seems more like native approach Koa should aim towards. Please reopen if I'm wrong :)


Add rpad function to MysqlSqlModule

Add support for function rpad described in the MySQL docs.
Add function to MysqlFunctionDef in MysqlSqlModule
Add test in FunctionDefSpec

I would like to take this issue


Regarding the problem of SeamlessM4T translating and cloning timbre/spoken language, here are cases

Regarding using only one audio sample, you can speak multiple languages using the tone of the audio sample. In fact, what you use is: seamless
You can refer to this: https://replicate.com/adirik/seamless-expressive
He seems to have also quoted seamless: https://github.com/replicate/cog-seamlessexpressive
demo:https://www.youtube.com/watch?v=lgL_rCF02Ng
You can refer to the recently popular ones: https://github.com/RVC-Boss/GPT-SoVITS

I don’t know if your project can translate text and clone multi-language sounds based on samples at the same time, but SeamlessM4T seems to be possible. At the same time, I saw this case, but Seamless did not do this in huggingface space. It’s just Translating audio does not clone audio !original [english:

Is GPT-SoVITS a new replacement for RVC?

https://replicate.com/adirik/seamless-expressive

You can upload an audio test, as if translated directly and clone the sound at the same time   https://replicate.com/adirik/seamless-expressive

He uses seamless   ：https://huggingface.co/facebook/seamless-expressive
  I don't know why you do this

Is GPT-SoVITS a new replacement for RVC?
GPT-SoVITS   can also Too complicated to use 。
You only need to upload a piece of audio, and you can use SeamlessExpressive. However, the SeamlessExpressive model needs to be reviewed before it can be obtained. I don’t know what the difference is between it and SeamlessM4T.

He uses seamless ：https://huggingface.co/facebook/seamless-expressive  I don't know why you do this

Ah now I remember this seamless-expressive, I got it confused with seamlessM4T. To be honest, I doubt that many people will be willing to fill out the form.
GPOT-SoVITS and SeamlessM4T can be done though.

So here's the post-mortem - since seamless-expressive has a restrictive, unique license (many people don't use a project with a custom license), and the development has been very slow (again, happens a lot with non-open-source style licenses), I will probably not include seamless-expressive, neither as a plugin, also because:
2. Restrictions. You will not, and will not permit, assist or cause any third party to:
        a. use the Seamless Materials or any outputs or results of the Seamless Materials in connection with any commercial uses or for any uses other than Noncommercial Research Uses;

This is ridiculous, by that standard I could break their license just by writing an article on how to install seamless-expressive.


Add "swap" metric

add swap
@dstokesf5
@jsevedge
What issues does this address?

Fixes #
WIP #

What does this change do?
add swap metric
Where should the reviewer start?
Any background context?
swap usage is an important health metric, usually polled by snmp in legacy environment

@amolari, before we go much further with this pull request, have you reviewed and addressed the section in the README regarding the contributor license agreement: https://github.com/F5Networks/f5-telemetry-streaming#f5-networks-contributor-license-agreement

ok, please discard then, I'll open an issue


Fails with Meteor 1.6.1

There are two issues with running the bundler against Meteor 1.6.1.  This results in you getting a "Meteor is not defined" error in the console.

In the build of 1.6.1, the global-imports.js file moved has moved directories, hence the bundler is not including it in the meteor-client.js
The _OnMigrate method has been removed from Meteor.  You should use Reload._onMigrate instead.

Fixes;

In bundler.js change the filter to pick up the missing file; ie.
.filter(function (pack) {
return (pack.where === "client" &&
pack.type === "js" &&
Path.dirname(pack.path) === "packages")
|| pack.path.indexOf('global-imports') > -1
})

Change the post-bundle.js to;

if (Package.reload) {
Reload._onMigrate(function () {
return [false];
});
}
I would push these changes up to the repo in a PR, but I don't have access.

@robport I tested your changes and they worked great.
To be able to submit a PR to a branch that you do not have access to you can follow these steps...

Fork the repository (it will make robport/meteor-client-bundler a repo that you have access to)
Clone the repository locally
Make the desired changes
Run git add -A
Run git checkout -b fix-issue-<number>
Run `git commit -m 'Fixes #<number'
Run git push
Visit http://github.com/robport/meteor-client-bundler
Click branches then click new pull request next to fix-issue-
Add any notes to the pull request and then submit it

By default it is made against the repository you originally forked from

Once approved it will add your changes into the repo you do not have access to

As an example I did this for your issue.
Which you should see above this comment.
If you decide to follow these steps and submit a PR with your changes I will gladly close mine.
If not, I added credit to you in the pull request message and commit message.

@afaur please go ahead and merge your PR.  Thanks for the credit.
Regards,
Rob

@robport It will be up to the maintainer to merge the changes.
Thanks for your fix on this it helped me out.

Ah, gotcha.  I'll know what to do next time.

I can confirm that the fix works, thank you!
@Urigo Uri can you please merge them in when you have spare minute? Thanks!

thank you everyone for the fix and the testing!
just merged and released version 0.4.0.
Please let me know if that works for you.
Sorry for the late response from me

@Urigo Works like a charm, thanks!


Clear doesn't change the selected person

Steps to repro:

select 1
clear

Another method: have only 1 person in the app and run delete 1


[TASK] Allow NULL value for overrideConfiguration

Migrated from Gerrit: https://review.typo3.org/#/c/40193/
Change-Id: I51b4ad9f2c1e4abed271e7586f4c828137842c1f
Releases: master

:+1:

Required for: https://github.com/neos/neos-development-collection/pull/31

:+1: by reading

:+1: We use it like that in many projects.
The PR should be updated to target the Neos 2.0 branch if it should be included in 2.0.

The PR should be updated to target the Neos 2.0 branch if it should be included in 2.0.

The PR should be updated to target the Neos 2.0 branch if it should be included in 2.0.

Let's merge only on master this not really a bugfix

:1: by reading for master.

stumbling upon this almost a year later, this breaks if no $persistenceIdentifier is set because it tries to call
$factory->build(NULL, ...)

@bwaidelich
Hello Bastian,
A few more comments on this can be found here.
I see there is a check in the Form.html template that makes sure that the formIdentifier (persistenceIdentifier) is present, but the problem is still there. However, I don't understand how formIdentifier is populated, I don't see it in fusion or in myForm.yaml configuration. Looks like it fetches the value of 'identifier' from myForm.yaml though.


OS name and version should be provided to CF scripts

Description:
We need to provide OS name and version as parameters to the CF scripts. There is a blocker when trying to run CF scripts for OSes other than ubuntu since the existing scripts involve logic which is depend on ubuntu (ex. apt-get). We can't switch such logic due to absence of OS and OS version in CF scripts.
Affected Product Version:
0.9.0-m18
Related Issues:
#483

This will be closed with PR to add OS name to the CF script.


chore/bump runtime

@Magnus-Kuhn have you checked the diff between these versions?

this is not what I meant - if you bump the version here you have to make sure all diffs get added to the dart code. This means you have to check the runtime diff between 4.13.1 and 4.14.2.
@britsta can you make sure to double-check this?


Add new Scroll Through Image To Change Text Parallax Effect

Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
null
Describe alternatives you've considered
null
Additional context

Assigning 🎊🎊


HBbase  serialization cannot obtain the timeout period?

Why didn't HBase assign the timeout time of RequestHeader when serializing the request?
As a result, HBase serialization cannot obtain the timeout period.
https://github.com/tsuna/gohbase/blob/master/pb/RPC.proto#L130
https://github.com/tsuna/gohbase/blob/master/region/client.go#L624

Indeed, I have started to investigate this here https://github.com/tsuna/gohbase/pull/215

nice~

I haven’t got a chance yet to test if it’s working


Atomic templates (no/less xml)

As a Cobigen user, I want to download as few templates as possible so that i have an easy time figuring out which templates to use.
Users should be able to manually download templates/add template dependencies for the type of project they want to more easily use and develop the templates they actually want.
Additionally, the context.xml file could be taken apart or replaced it with something different so users and developers do not have to sift through the "overstuffed" file to find what they need.
This is a workshop topic, any ideas are welcome and can be discussed in the comments

My thoughts:

I thiink we first need to define the new structure of a template archive

I would suggest to stay with JAR files that can be put on class/module path (ZIP files might be more natural for other languages but after all CobiGen is written in Java and a JAR is only a ZIP with a different extension).
In general we need to figure out which JARs from the classpath are templates and which dont.
IMHO the easiest and cleanest way would be to use ServiceLoader that is already established by CobiGen for plugin management. So CobiGen could provide a minimal interface like TemplatesProvider that will be called to load the templates. Then CobiGen just follows the ServiceLoader pattern to load all registered implementations of TemplatesProvider to find any form of templates and also be a replacement for context.xml as pluggable snippets from code.
CobiGen core could already provide abstract base classes for TemplateProvider - e.g.

one to load them by scanning the JAR containing the TemplateProvider implementation derived from that base class from a root package templates (replacement for text templates like freemarker or velocity).
another one to load language agnostic templates. Here you will have the source code inside the JAR that may again be in the templates folder (to be discussed) and for Java also the *.class files that need to be loaded via regular classloader and we need a namespacing to avoid that two independent template JARs clash by containing the same fully-qualified class name.
The nice thing about this approach is that even future ways of how templates can be found and loaded can be addressed in the TemplateProvider implementation giving a lot of flexibility.

Also we really need to make a choice if we want to create a new CobiGen2 innovation product or if we want to carry the entire compatibility history of CobiGen. Without compatibility it would be relatively easy to fork CobiGen, refactor it to an MVP with the new features and migrate some of our templates to this new world (combined with language-agnostic templates, etc.). When we have reached this point, we could revisit and see if there is a compatibility path or if it is too much effort compared to its value. Otherwise I fear that we will never even reach the state of the MVP as compatibility will slow us down heavily.


tensorflow Docker behaves different to host (produces nan)

System information
Have I written custom code (as opposed to using a stock
example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g.,
Linux Ubuntu 16.04): Linux Mint 19.3 (ubuntu)
TensorFlow installed from (source or
binary): binary
TensorFlow version (use command below): tf-nightly
Python version: 3.8 and 3.6
two systems:
Host: NVIDIA-SMI 435.21       Driver Version: 435.21       CUDA Version: 10.1 TF: 2.2.0-dev20200325
Docker: NVIDIA-SMI 435.21       Driver Version: 435.21       CUDA Version: 10.1 TF: 2.2.0-dev20200325
Describe the current behavior
In Docker the gradient calculation produces only NANs
On the host the same model produces normal gradients
Describe the expected behavior
in docker the same gradients should be produced
Standalone code to reproduce the issue
can not be provided, sorry, very big model, and problem is hard to locate.
if i can locate the problem i will provide a Standalone code
Other info / logs Include any logs or source code that would be helpful to
Gradient magnitude on host:
...
    [3.31210213e-05 -2.52332793e-05 -2.79605388e-06 ... -1.31225511e-06 1.79109138e-05 3.6471597e-06]
    [-4.21071627e-06 5.53799646e-06 4.40907201e-07 ... -7.86542842e-07 -6.31262401e-06 -7.09808887e-07]
    [-2.62982558e-05 -6.01945476e-06 -3.60058812e-06 ... 4.37716608e-06 5.87437571e-05 4.91119135e-06]]

UPDATE:
OK i found the problem, this is a similar issue to  #511 and  #1244
it had nothing to do with docker, but with gpu and cpu inferenz.
On the host the cuda lib could not be loaded and so it ran on cpu and worked, after fixing cuda, it stopt working on gpu on the host to.


Unable to import in android studio

Please ensure you have given all the following requested information in your report.
Issue details
Hi I am not able to import the libgdx into my android studio 2.x

Reproduction steps/code
Even if you think your issue is trivial to reproduce, please supply a SSCCE that demonstrates your issue.  This saves time on our end, and makes it much more likely that your issue will be fixed.
You can find barebones templates here
Version of LibGDX and/or relevant dependencies
Please provide the version(s) affected.
Stacktrace
//Please provide the stacktrace if applicable

Please select the affected platforms

[x] Android

You either don't have enough RAM, or you have a 32bit jdk installed on a 64bit system. If you have the first case, lower the RAM in gradle.properties file, if its the second, uninstall the 32bit jdk and install a 64bit one.


[Feature] Announce Snackbar appearance to screen reader

Description of Change

Recognized the issue with the screen reader not reading the announceForAccessibility was only a problem in iOS and it appeared to be an issue due to the synchronous nature of the storybook test case so iOS was immediately refocusing the button at near enough the same time to not do the announceForAccessibility.
Resolved by creating a useEffect on the Snackbar display that:

Has an empty dependency array so the useEffect is only run once on initial render since otherwise the announceForAccessibility was being triggered multiple times (on appearance and disappearance)
Has a 50ms delay so that if whatever is bringing up the Snackbar is synchronous (not generally how it's used, but could be) it still announces correctly

Testing Packages

0.21.1-alpha.10

Screenshots/Video

iOS:
https://github.com/user-attachments/assets/335e4726-ab05-431f-909b-fdffc6ccaaea
Android:
https://github.com/user-attachments/assets/5f889ace-fd70-45d7-bf2c-9c1e185d4f37
Flagship iOS (somewhat janky from app-level focus that they'll need to address during implementation):
https://github.com/user-attachments/assets/571f55bc-cd8a-4a15-a881-8123cdda436e
Flagship Android (also somewhat janky in a different way from app-level focus that they'll need to address during implementation):
https://github.com/user-attachments/assets/046f41f4-a28e-433f-bb4d-632be14b0641
Testing

Tested it performs as expected in Storybook. Also tested flagship which was a bit janky, but due to app-level setting focus.

[x] Tested on iOS
[x] Tested on Android
Tested on Web

N/A

PR Checklist
Code reviewer validation:

General

[x] PR is linked to ticket(s)
[x] PR has changelog label applied if it's to be included in the changelog
[x] Acceptance criteria:

All satisfied or
Documented reason for not being performed or
Split to separate ticket and ticket is linked by relevant AC(s)

[x] Above PR sections adequately filled out
[x] If any breaking changes, in accordance with the pre-1.0.0 versioning guidelines: a CU ticket has been created for the VA Mobile App detailing necessary adjustments with the package version that will be published by this ticket

Code

[x] Tests are included if appropriate (or split to separate ticket)
[x] New functions have proper TSDoc annotations

Publish

While changes do warrant a new version per the versioning guidelines, postponed for later following functional changes to Snackbar.

Did you identify how the app would fix the jankiness?

I did not.
It may involve changes on our end. There is a slightly different function, announceForAccessibilityWithOptions, which can make iOS queue up the announcement behind other screen reader behavior similar the how Android behaves. There's also settings for Android to be assertive and interrupt, but not sure how easily we can apply that to announceForAccessibility. There's enough ambiguity that I think we can leave it to flagship implementing and work with them on how best to sort it out then.
I have added a comment to the handoff ticket so they are on the lookout for it at least.


There might be a bug

I think line 86 in crow.py should be fixed by:
return sknormalize(x.reshape(1,-1), copy=copy)

What seems to be the problem?


Use a separate webhook secret for the GH App

Summary
instead of reusing the same one we already use for repos
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
manually by setting the webhook secret in the config file and making sure that I can validate incoming messages with the right secret and can't with the wrong secret
provider:
  github-app:
    app_name: jakub-s-local-minder-test
    app_id: 864067
    user_id: 165174215
    private_key: ".secrets/github-app.pem"
    webhook_secret: "test5"

Review Checklist:

[x] Reviewed my own code for quality and clarity.
[x] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[x] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 47.225% (+0.009%) from 47.216%
when pulling c2d16aa3babb4bb70430b3008a6dd082bdf6fca6 on jhrozek:ghapp_separate_webhook_secret
into 87bb8aaa3da34c035017c95b57bad8020ae112dc on stacklok:main.


Add Text-to-Speech streaming from file region tags

Adding region tags to the Text-to-Speech streaming from file code snippet

Done, I also went ahead and included the imports on livecaption for consistency since they're kind of twins :)


Workflow updates

Enable Windows tests in CI.
Possibly fixes #362.

@shanedell, I got the Scala tests working under Windows, now it looks like some yarn pathing issue where a build artifact is not being found where expected.  Mind taking a look?

I'm able to successfully run the TS client lifecycle tests in PowerShell on Windows 11 Pro
PS D:\git\omega-edit> Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
PS D:\git\omega-edit> yarn workspace @omega-edit/client test
yarn workspace v1.22.22
yarn run v1.22.22
$ yarn package && yarn install-client-local
$ yarn compile-src && yarn build && yarn --cwd out cache clean
$ run-script-os
$ ./compile-proto.bat

D:\git\omega-edit\proto>(
set "OUT_DIR=D:\git\omega-edit\packages\client\"
 set "TS_OUT_DIR=D:\git\omega-edit\packages\client\"
 if not exist "D:\git\omega-edit\packages\client\src" (mkdir "D:\git\omega-edit\packages\client\src" )
 cd "D:\git\omega-edit\packages\client\..\..\proto"
 D:\git\omega-edit\packages\client\node_modules\.bin\grpc_tools_node_protoc.cmd         --plugin=protoc-gen-ts="D:\git\omega-edit\packages\client\node_modules\.bin\protoc-gen-ts.cmd"         --plugin=protoc-gen-grpc="D:\git\omega-edit\packages\client\node_modules\.bin\grpc_tools_node_protoc_plugin.cmd"         --js_out=import_style=commonjs:"D:\git\omega-edit\packages\client\src"         --grpc_out=grpc_js:"D:\git\omega-edit\packages\client\src"         --ts_out=grpc_js:"D:\git\omega-edit\packages\client\src"         omega_edit.proto
)
$ webpack --mode=production
assets by path *.ts 149 KiB
  asset omega_edit_grpc_pb.d.ts 73 KiB [compared for emit] [from: src/omega_edit_grpc_pb.d.ts] [copied]
  asset omega_edit_pb.d.ts 47.7 KiB [compared for emit] [from: src/omega_edit_pb.d.ts] [copied]
  asset session.d.ts 10.5 KiB [compared for emit]
  asset change.d.ts 9.89 KiB [compared for emit]
  + 7 assets
assets by path *.js 1.05 MiB
  asset main.js 869 KiB [compared for emit] [minimized] (name: main) 2 related assets
  asset pino-worker.js 142 KiB [compared for emit] [minimized] 1 related asset
  asset pino-file.js 58.1 KiB [compared for emit] [minimized] 1 related asset
  asset thread-stream-worker.js 3.61 KiB [compared for emit] [minimized] 1 related asset
  asset pino-pipeline-worker.js 1.99 KiB [compared for emit] [minimized] 1 related asset
asset LICENSE.txt 11.3 KiB [compared for emit] [from: ../../LICENSE.txt] [copied]
asset package.json 2.29 KiB [compared for emit] [from: package.json] [copied]
asset README.md 2.27 KiB [compared for emit] [from: README.md] [copied]
runtime modules 793 bytes 4 modules
orphan modules 42 bytes [orphan] 1 module
modules by path ../../node_modules/ 1.45 MiB
  javascript modules 1.43 MiB 204 modules
  json modules 13.9 KiB
    modules by path ../../node_modules/protobufjs/ 10 KiB 4 modules
<EMAIL_ADDRESS>2.54 KiB [built] [code generated]
    ../../node_modules/thread-stream/package.json 1.34 KiB [built] [code generated]
modules by path ./src/ 429 KiB
  modules by path ./src/*.ts 126 KiB 9 modules
  modules by path ./src/*.js 303 KiB
    ./src/omega_edit_pb.js 268 KiB [built] [code generated]
    ./src/omega_edit_grpc_pb.js 34.3 KiB [built] [code generated]
+ 21 modules
webpack 5.91.0 compiled successfully in 9670 ms
success Cleared cache.
$ run-script-os
$ yarn --cwd out pack --install-if-needed -f omega-edit-node-client-v%npm_package_version%.tgz
success Wrote tarball to "omega-edit-node-client-v0.9.78.tgz".
$ run-script-os
$ yarn add file:%INIT_CWD%/omega-edit-node-client-v%npm_package_version%.tgz
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 0 new dependencies.
$ (yarn test:lifecycle) || (yarn posttest && exit 1)
$ mocha --exit --timeout 50000 --slow 35000 --require ts-node/register ./tests/specs/server.spec.ts

  Server
    ✔ on port 9011 should stop immediately via stopServiceOnPort using 'SIGTERM'
    ✔ on port 9011 should stop immediately via PID using 'SIGTERM'
    ✔ on port 9011 should stop immediately via stopServiceOnPort using 'SIGKILL'
    ✔ on port 9011 should stop immediately via PID using 'SIGKILL'
    ✔ on port 9011 should stop gracefully via API
    ✔ on port 9011 should stop immediately via API (20124ms)

  6 passing (47s)

$ yarn remove @omega-edit/client
[1/2] Removing module @omega-edit/client...
[2/2] Regenerating lockfile and installing missing dependencies...
success Uninstalled packages.
Done in 96.18s.
Done in 96.44s.

Not sure what the problem is yet in CI.

Looks like all the TS client tests are passing, just something is causing mocha to choke at the end of the test suite in Windows.


Fuzzy matching repository name in GET repositories API

Coverage decreased (-0.3%) to 60.663% when pulling c6e65d2dede67e12e082a0c03c336a20563e8017 on ywk253100:180322_repo into 8b739dcbbbd8ef4679c57bbaa1f64d51c6d8a158 on vmware:master.


Update theme via the Grav admin

Hello,
I installed hypertext via the theme tab and I just saw that I have the 2.2.3 release.
How can I have the latest release via the theme tab please?

My bad. Forgot to increment the version number, so Grav doesn't realize who has outdated versions.  Pushed a new release; give it some time to land.

Thank you. Not yet available, even if I click on the "check" button. I'll close the issue when it will be ok.

Update is not yet available 🤔

Looks like grav picked it up. I'm getting update theme notifications on my other sites that use this theme.  ^_^


update(query): add CWE information to volume_has_sensitive_host_directory

** Reason for Proposed Changes**

CWE information for the query was missing

** Proposed Changes**

Adding 668 as Exposure of Resource to Wrong Sphere seems the best fit covering both confidentiality and integrity concerns.

I submit this contribution under the Apache-2.0 license.

Thanks a lot @ArturRibeiro-CX ... would you mind re-checking the update. Are the changes acceptable?

Hi @julianthome,
Just to let you know that your PR was merged today.
Thanks for your contribution to KICS.
Best regards.


Gtest update

[unittests] Update unittests for new gtest version …
Remove gtest version check comments and update unittests for the new
gtest versions.

[neuralnet] Neural network bugfix
Two PRs merged have caused main branch to fail.
This patch provides temporary fix.
Proper fix  will be done with layer_v2.

Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1286. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.


Accumulo Store tests may fail depending on the order they run

Some Accumulo Store tests use the MockAccumuloStore instead of the SingleUseMockAccumuloStore.
This means the Gaffer accumulo table is shared between tests and different schemas are used for different tests so the table contains the wrong schema.

Merged into develop.


update add sub-folder for index.js

Addresses issue https://github.com/OfficeDev/outlook-dev-docs/issues/340

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/add-ins/quick-start.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[hb_input] get unicode from ordinal past 10000 on narrow Python build

When trying to run hbinput on the Roboto sources, I get the following traceback
Traceback (most recent call last):
  File "_hbtest.py", line 8, in <module>
    print seq.all_inputs()
  File "/Users/marc/Documents/nototools/nototools/hb_input.py", line 60, in all_inputs
    cur_input = self.input_from_name(name, pad=is_zero_width)
  File "/Users/marc/Documents/nototools/nototools/hb_input.py", line 97, in input_from_name
    text = unichr(self.reverse_cmap[name])
ValueError: unichr() arg not in range(0x10000) (narrow Python build)

If you're running a narrow Python build, the function unichr will only return unicode chars from ordinals up to 10000. Roboto has two glyphs which are outside this range, uni1F16A and uni1F16B.
We can address this issue by converting the ordinal into a unicode esc string, its then stored as a UT-16 surrogate pair on narrow build, which can then be reencoded back to utf-8.
This is not my solution but it works nicely. Found it here, https://stackoverflow.com/questions/7105874/valueerror-unichr-arg-not-in-range0x10000-narrow-python-build/7107319

Why reinvent the wheel? Fonttools is already a requirement of nototools and includes a unichr that does exactly that, in the fontTools.misc.py23 module

@anthrotype thanks!, I'll investigate and use that instead.

@anthrotype thanks! does exactly what I wanted.
More than happy to squash and clean up this commit message if approved.


"Run Without Debugging" DOES stop at breakpoint

VSCode Version: 1.52.1
OS Version: Windows_NT x64 10.018363

Steps to Reproduce:

place a breakpoint in c++ code
select "Run Without Debugging", the program stops at the breakpoint.

Is this as designed or a bug? At least, the visual studio does not work in this way. It is quite embarrassing to  VS users like me. Thank you.

Does this issue occur when all extensions are disabled?: Yes/No

I just tried this and it works just fine for me with javascript and latest vscode insiders.
Please file this issue against the c++ extension. Thanks

I just tried this and it works just fine for me with javascript and latest vscode insiders.
Please file this issue against the c++ extension. Thanks

You have not tested exactly. Please try it with c/c++ code.  I am afraid that it may not be caused by c++ extension, but by Code.

You have not tested exactly. Please try it with c/c++ code.  I am afraid that it may not be caused by c++ extension, but by Code.

@idebtor c++ is not natively supported by VS Code. I don't think it is fair to expect @isidorn to install an extension to investigate your issue unless the developers of the extension first investigate and assert that the problem lies in VS Code.

@idebtor c++ is not natively supported by VS Code. I don't think it is fair to expect @isidorn to install an extension to investigate your issue unless the developers of the extension first investigate and assert that the problem lies in VS Code.

Thanks for your comments.
As you know, Gdb and c++ existed long before VS Code ever exists.  However, you may be right.  So, I posted the same question with a concrete example to StackOverflow. I have not got a response yet.  For your reference:
Stackoverflow link
Thanks in advance.

Thanks for your comments.
As you know, Gdb and c++ existed long before VS Code ever exists.  However, you may be right.  So, I posted the same question with a concrete example to StackOverflow. I have not got a response yet.  For your reference:
Stackoverflow link
Thanks in advance.

/extC++

/extC++

I suggest you use "Report Issue" from the Help menu in VS Code. Set the "File on" dropdown to "An extension". Pick your C++ extension. Add title and steps to reproduce. Use the "Preview on GitHub" button. In the browser page that opens you should see the new issue drafted on the correct repo for the extension. Submit it. Then close the Issue Reporter dialog via its [X] titlebar button.

I suggest you use "Report Issue" from the Help menu in VS Code. Set the "File on" dropdown to "An extension". Pick your C++ extension. Add title and steps to reproduce. Use the "Preview on GitHub" button. In the browser page that opens you should see the new issue drafted on the correct repo for the extension. Submit it. Then close the Issue Reporter dialog via its [X] titlebar button.

Wow~
Thanks for your suggestion and kind guide to filing it that I never knew. I will do it soon.
It is very kind of you.
Many thanks~
(a debtor)<><

Wow~
Thanks for your suggestion and kind guide to filing it that I never knew. I will do it soon.
It is very kind of you.
Many thanks~
(a debtor)<><

As @gjsjohnmurray suggested thankfully, I was able to file it. For your information,
github filing at vscode-cpptools
Blessings, (a debtor)<><

As @gjsjohnmurray suggested thankfully, I was able to file it. For your information,
github filing at vscode-cpptools
Blessings, (a debtor)<><

Hi @gjsjohnmurray,
Believe it or not, I've got the answer from the Microsoft team(vscode-cpptools), finally. VS Code is supposed to implement it.  I spent days and days. You know how to help others. Your suggestion and guide really helped me and will help many others as well.
Here is the answer for your reference.
answer
Duplicate of #5680
The cpptools debuggers (cppvsdbg and cppdbg) do not support run without debugging.
We ignore the noDebug boolean in LaunchRequestArguments . We will just start a debug session.
This will need to be implemented.
See: #5680 (comment)

Hi @gjsjohnmurray,
Believe it or not, I've got the answer from the Microsoft team(vscode-cpptools), finally. VS Code is supposed to implement it.  I spent days and days. You know how to help others. Your suggestion and guide really helped me and will help many others as well.
Here is the answer for your reference.
answer
Duplicate of #5680
The cpptools debuggers (cppvsdbg and cppdbg) do not support run without debugging.
We ignore the noDebug boolean in LaunchRequestArguments . We will just start a debug session.
This will need to be implemented.
See: #5680 (comment)


Live Sketch Through WebCam

Checklist

Please note that in case of below checklist not updated accordingly, the maintainers have the right to immediately close your pull request.

[x] You created a branch from dev branch.
[x] You PR is raised on dev branch and not onmaster.
[x] Blog follows Blog Guidelines.
[x] You have read the Contribution Guidlines before creating this PR.
[x] Checked for any duplicate blog entry.
[x] Checked for all grammatical errors in the blog.
[x] You have not published the blog content anywhere else on the internet on platforms like medium, dev.to etc.
[x] The content is not copy-pasted from anywhere else on the Internet.

Description of change

OpenCV is a powerful computer vision library so why not use it? Here, I have implemented use of OpenCV to see live realtime black and white sketch through webcam.
Author Details for Blog Post Entry

id: Sharvari Raut
bio: AI Enthusiast
github: sharur7
linkedin: https://www.linkedin.com/in/sharvari-raut-a62a99171/
medium: sharur7
twitter: aree_yarr_sharu
Issue:
#233

@puneetsingh24  I have updated my index.md please review it again


CpuIdFactory: Simplify the interface

The concrete CpuIdFactory does not need to be exposed in the header to the users. Instead a single templated free function would suffice to create a factory parameterized with the desired configuration object. This unclutters the header and avoids exposing unneeded dependencies in the header.
By introducing a helper class CpuIdFactoryWithCallback for each concrete factory we only need one specialization of the free function CreateCpuIdFactory(). Each specialization injects a callback in in the helper class that contains the actual creation logic and captures the configuration object.
Further refactoring could extract the concrete specializations of CreateCpuIdFactory into separate translation units. This would completely decouple the concrete types from each other, and save recompilation of all factories if just one concrete type is changed.

Merged manually. Closing as resolved.


Datasets problem

Excuse me, when I tred to train your model I found the datasets.md was empty.
So how can I prepare my datasets or have the datasets.md finished?
Thanks!

Hi! I'll take a look at this today. Due to the messy license of the images in the COCO dataset, I will only release the annotations from CSE.
Along with the annotations, I'll publish  a script to parse the coco dataset/CSE annotations, and generate the final dataset (with images & annotations).

Thanks a lot!

The docs/DATASETS.md is now updated. Please notify me if you have any issues with downloading the COCO-cse dataset.

Thanks for your update!
But I found some mistakes in the docs/DATASETS.md

Somewhere the datasets use Coco2017 and somewhere is Coco2014.
In the introduce of Coco_cse structure, there appears three times of train.

I followed your train code and find some mistakes which made it stop at the dataloader's collate_fn. Maybe it should add a resize function before the dataloader.

Thanks for notifying me! I fixed the typos now :)
Regarding the error in train.py, it's due to a bug in the coco-cse downloading script. This commit fixes the issue. You need to delete the dataset and regenerate it again.


Cannot find self defined plugin when executing code

I write a plugin under my project/plugins folder:
from taskweaver.plugin import Plugin, register_plugin
from typing import List
try:
    from snownlp import SnowNLP
except ImportError:
    raise ImportError("Please install snownlp with `pip install snownlp`")

@register_plugin
class SentimentAnalysis(Plugin):
    def _init(self) -> None:
        pass

    def sentiment_to_score(self, sentiment: float) -> int:
        """Map (0,1) to 1-5
        """
        return int(sentiment  * 5) + 1

    def __call__(self, inputs: List[str]):
        results = []
        for review in inputs:
            s = SnowNLP(review)
            rating = self.sentiment_to_score(s.sentiments)
            results.append(rating)
        return results

Here is the yaml file:
name: sentiment_analysis
enabled: true
required: false
description: >-
  sentiment_analysis processes a list of text inputs and assigns a sentiment score from 1 to 5, based on the polarity of the text.
examples:
  sentiment_scores = sentiment_analysis(["Very good product", "Bad quality", "A little noisy"])

parameters:
  - name: inputs
    type: list
    required: true
    description: >-
      A list of sentences to be analyzed for sentiment polarity.

returns:
  - name: sentiment_scores
    type: list
    description: >-
      A list of sentiment scores (from 1 to 5, integer) for each input string, based on the analysis.

However, the taskweaver cannot find this plugin:

This is the folder structure.

The symptom suggests that TaskWeaver can find your plugin (because the code had been generated correctly), but calling it led to an error. Please first check the FAQ here to see if the problem can be fixed. There is also a way of debugging the plugin in the FAQ.

Hey there! This might sound a bit silly, but I’ve noticed something that might be helpful. YAML files can be quite sensitive to special characters. I found that avoiding the use of >- characters made it easier to register plugins without any issues. It worked for me, so I thought I’d share in case it helps!


⚠ ClamAV has degraded performance

In 80473f1, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 195 ms

Resolved: ClamAV performance has improved in 9ebffc7.


imp: accept any string-like parameter

Use the power of the AsRef trait to take generic parameters for several API functions. This makes the API more ergonomic because the callers may pass in static str slices or references to owned Strings
or even more exotic things like a Cow, all based on their particular situation.
Update the tests and examples to use the most natural types they have available.
Fixes #77. No existing code should break, as &String implements AsRef<str> and AsRef<Path>

Oh no. The note in examples/service_account/Cargo.toml about not using the local version of the crate means it's nearly impossible to update things. I guess I'll keep the examples as they were to prove that these changes won't break things.

Codecov Report

Merging #90 into master will increase coverage by 0.75%.
The diff coverage is 66.66%.

@@            Coverage Diff            @@
##           master     #90      +/-   ##
=========================================
+ Coverage   47.14%   47.9%   +0.75%
=========================================
  Files          10      10
  Lines        1016    1002      -14
=========================================
+ Hits          479     480       +1
+ Misses        537     522      -15

Flag
Coverage Δ

#stable
47.9% <66.66%> (+0.75%)
:arrow_up:

Impacted Files
Coverage Δ

src/storage.rs
15.47% <ø> (+2.21%)
:arrow_up:

src/authenticator.rs
40.99% <0%> (+0.25%)
:arrow_up:

src/authenticator_delegate.rs
28.3% <0%> (ø)
:arrow_up:

src/device.rs
88.23% <100%> (ø)
:arrow_up:

src/refresh.rs
86.76% <100%> (ø)
:arrow_up:

src/helper.rs
64.51% <100%> (+1.18%)
:arrow_up:

src/service_account.rs
43.97% <66.66%> (ø)
: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 de57b8f...6428023. Read the comment docs.

Thank you!


Start implementing multiple language support for national calendars

Fixes #150
Summary of changes

move all calendar resources to a /calendars subfolder
separate out diocesan calendars into their own subfolder /dioceses
create /i18n subfolders for all national calendars
reorder the /wider_region folder structure to more closely resemble /nations

TODO: update all code references to any of these folders (perhaps we should finally create globals, so we don't have to update scattered references, for example create a class with constants?)

This PR will also implement #266 as proof of concept.

I'd say that we're at a point now that we can start merging to development, and pass to further testing on the development branch using the UnitTest interface (which might require a couple touch ups too, maybe?)


Replace webpack's uglify with new uglify plugin to allow ES6 uglification

This change will automatically allow webpack to minify ES6 code.

Alternatively, should use provide user an way to use their own uglify plugin?
    webpackConfig.plugins.push(
      new webpack.DefinePlugin(TASK_CONFIG.javascripts.production.definePlugin),
      (webpackConfig.uglifyPlugin) // Allow the use of other uglifier
        ? new webpackConfig.uglifyPlugin(uglifyConfig)
        : new UglifyJsPlugin(uglifyConfig),
      new webpack.NoEmitOnErrorsPlugin()
    )


PECL Redis missing from composer dependencies

I noticed OpenTHC\Service\Redis makes use of the \Redis class, and after looking at the usage of \Redis's interface, I believe it's PECL Redis class.
Common's composer configuration is missing the ext-redis requirement. I have a project that is dependent on OpenTHC\Service\Redis and did not have the php7.4-redis package installed. When I used the library's Redis::factory method, I would get a PHP fatal error because it could not find the \Redis class.
When I added the ext-redis requirement to my project's composer configuration and then ran composer update, I was able to get a fatal error from composer because the redis extension was not installed.
I then installed the pecl redis extension on my system for PHP 7.4, and re-ran the composer update. After this, composer was able to complete updating. And my script could make use of the OpenTHC\Service\Redis class.

Fixed in 8bcc9d8