Module hooks documentation

Hi,
Where are module hooks documentation?
The link in released v.1.0.0 is broken.
Could anyone help me?
Thanks.

@derevandal  see the github doc repository https://github.com/nuxt/docs/blob/c6493850060aa798542abcc811ced23c3c401fab/en/guide/modules.md#run-tasks-on-specific-hooks

Thanks, bro!
De: Nicolas PENNEC
Enviado:terça-feira, 20 de março de 2018 14:41
Para: nuxt/nuxt.js
Cc:André Van Dal; Mention
Assunto: Re: [nuxt/nuxt.js] Module hooks documentation (#3069)
@derevandal see the github doc repository https://github.com/nuxt/docs/blob/c6493850060aa798542abcc811ced23c3c401fab/en/guide/modules.md#run-tasks-on-specific-hooks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


feature: speaker notes

Hello Scanny,
I'm new to GitHub so my apologies if this is not the right place to ask for this.
I have to prepare PowerPoint slides from an Access database, all text or number fields.
My idea was to first save it as an Excel spreadsheet and then extract the
data and build the text slides with python-pptx, but for me it's mandatory that one
of the text fields has to go as speaker notes.
Do you think it is feasible? or that you might implement it in the future?
Thank you very much,

Closed as duplicate of #122.


bump teal-x86_64.yaml base os

Signed-off-by: Itxaka<EMAIL_ADDRESS>

yep, sorry was too eager and added the bump and missed bumping cos, bumping arm64, too images etc...
Althougth as far as I can remember I tried to bump it some time ago and failed miserably.

Weird, looks like we are not passing the flavor to the docker builds. Orange, blue and green are all attempting to build with teal values. This should have not been altered in this PR, feels like an unrelated issue.

yeah, docker builds are totally broken, not sure if we should just disable them like they were just a couple of months ago.

A bit concerned about the failures on the bios installer tests thinking I doubt it has direct relation with the changes here though

yup, gonna wait until is re-run, according to the logs, there was a disconnection so it could not copy the proper files into the VM so it failed.
Gotta wait for a while thought, its run on macos workers are we have none available right now ¬_¬

ah, I see!
Its just that due to https://github.com/rancher/elemental-cli/pull/287 we now start the custom files from 90, and before we just copied the cloud config files into 99-custom.yaml, so in the test we check for that specific file, thus it wont work.
Will merge this and send a PR to fix the tests.

Its just that due to rancher/elemental-cli#287 we now start the custom files from 90, and before we just copied the cloud config files into 99-custom.yaml, so in the test we check for that specific file, thus it wont work.

Good catch! Damn, we are overlooking this repository... I wish we had a cleaner relation between elemental and  elemental-toolkit repos...

To be honest, on testing just getting transient/new files by specific name is pretty bad as its error prone. We should not get that file directly but just look at the files in /oem and check all of them instead :D
Although a cross project testing like zuul does would be really nice in this case :D


keepassxc: fix darwin build

Motivation for this change
This PR allows keepassxc to build on macOS.

Removed the unnecessary libmicrohttpd dependency, which doesn't build on macOS. KeepassXC removed this dependency in 2.1.2.
Fixed a compiler error related to the Touch ID feature by adding a dependency on the LocalAuthentication framework. Compiler error that was fixed:

[ 64%] Building CXX object src/CMakeFiles/keepassx_core.dir/keys/drivers/YubiKey.cpp.o
[ 64%] Building CXX object src/CMakeFiles/keepassx_core.dir/touchid/TouchID.mm.o
/private/var/folders/qx/jwzr4j413sj76yplz7xqx22h0000gn/T/nix-build-keepassxc-2.5.1.drv-0/source/src/touchid/TouchID.mm:11:10: fatal error: 'LocalAuthentication/LocalAuthentication.h' file not found
#include <LocalAuthentication/LocalAuthentication.h>
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
make[2]: *** [src/CMakeFiles/keepassx_core.dir/build.make:2065: src/CMakeFiles/keepassx_core.dir/touchid/TouchID.mm.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:641: src/CMakeFiles/keepassx_core.dir/all] Error 2
make: *** [Makefile:163: all] Error 2
builder for '/nix/store/a7wrkjifshgxjls99gj344yvi3rwvfzm-keepassxc-2.5.1.drv' failed with exit code 2
error: build of '/nix/store/a7wrkjifshgxjls99gj344yvi3rwvfzm-keepassxc-2.5.1.drv' failed

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @jonafato

Please include the very useful info in the PR message in the commit message.

Added some more info to the commit message


Plug Synth to AudioWorklet

This PR allow the Synth to run in the background using an AudioWorklet
The changes are minimal.
I made a sample page for testing
codepen

The worklet synth work simlarly to the standard synth.
It takes a new parameter here "beepbox_synth.js". This is the url of the source that will run in the background worker.
For simplicity both client and worker run the same code.

All fair points. It is certainly not a feature yet, it is more like a proof of concept.
Let me rewind a bit on the story.
I am looking for musics and a music player for my new game.
I have discovered beepbox only days ago. I know not much about it.
Embedding the script and starting the music is simple but I soon realized that the music is running in the browser UI thread.
When my game is busy the music is stuttering (not sure if this is the right word).
So I tried to make the minimal changes so that the whole music player (synth.js) could run in an AudioWorkletProcessor.
I hacked my way in, trying to change as little as possible. By large the code do not use the browser but there are some usage of "navigator" and "document".
For simplicity I took the option to have the same source on both server and client.  You probably wouldn't do it in a proper release.
This PR is just a proof concept of that.
As it stand the WorkletSynth allow me to start and stop any music and change the volume at runtime and it doesn't slow down when I do calculations in the UI. It is what I was after.
PS: I just tried the IFRAME here: https://ganaye.com/beepbox/ . In my browser the music still seem to be played in the UI thread. When I click the Calculation buttons the music stops for a second regardless of whether the song plays on the main frame or the IFrame.
What am I missing?
I am going through your question again to make sure I miss nothing.

What's the use case for these changes? Are you embedding the synthesizer in a page, using it in a game, ...?

Yes a game in dev (ganaye.com/slego)

When people use the synthesizer outside of the editor it's typically via an iframe (the "song player") so it's interesting to hear about other uses people have for it.

I had no idea. people use an iframe, the music is still not working well for me using this.

In any case, there are definitely a few changes bundled up here that really should be done regardless (e.g. side effects when parsing Songs, hard dependency on things that aren't available for workers or other similarly more limited environments), but I have a feeling that running the synthesizer in a worker in this very fire-and-forget way is something that's better left more to the example code for integrating the synth into a web page/app, as it indeed takes very little work to set up in case it's important.

It'd be lovely if the synth.js could run in a background worker of any kind.
It is just a matter of checking if the document or navigator exist before using it.

Running the synthesizer in an dedicated audio thread for the editor has been a goal for a while now after the deprecation of ScriptProcessorNode, but that complicates everything quite a bit. I'm also not sure what that would mean for the public Synth API (e.g. would it transparently run the CPU-intensive code in a worker behind the scenes? That's less flexible than leaving it up to the caller, so I would assume no, but maybe a ready-to-use class is better?).

This is how I plugged the volume:
set volume(volume: number) {
    this._volume = volume;
    this.audioWorkletNode?.port.postMessage({ type: 'volume', data: volume });
}

I suppose any api call would need to be pushed though postMessage like this:
I don't expect this branch to go in. It took me just a few minutes to hack.
I pushed it as "PR" to attract your attention and possibly start a proper contribution.


manifest for docker.io/aerokube/selenoid:latest not found

First I tried
https://github.com/aerokube/selenoid-ui/blob/master/docker-compose.yml
It was working couple of months ago
The above commnad
And
docker pull aerokube/selenoid
Returning
Trying to pull repository docker.io/aerokube/selenoid ...
manifest for docker.io/aerokube/selenoid:latest not found
But a specific version from history is working
docker pull aerokube/selenoid:1.10.7
Trying to pull repository docker.io/aerokube/selenoid ...
1.10.7: Pulling from docker.io/aerokube/selenoid
97518928ae5f: Pull complete
af0870f9b422: Pull complete
dc8779278fdd: Pull complete
Digest: sha256:2e3b71da1f5f5302f239f806cbe9cd6010f9cd8d496d25ade74e89fde8eed1c5
Status: Downloaded newer image for docker.io/aerokube/selenoid:1.10.7
First I thought the latest tag may not exisit anymore. So I went in there and looked
And found the latest

@rahul-vinaudit something on your side. Everything works.

How can it be a problem at my end, when I'm getting error from the server
Is ti a particular docker version that it supports.
Can you tell me the docker version you are using

@rahul-vinaudit already existing layer is alpine:3 layer.

@vania-pooh
It is working on ubuntu machines but not on the centos machines
108  yum install docker --assumeyes
109  systemctl start docker
110  systemctl enable docker
111  systemctl status docker
112  docker pull aerokube/selenoid:latest

@rahul-vinaudit we don't have experience with CentOS. Probably they just broke something in Docker package. I tested things on MacOS.

@vania-pooh
Which all linux OS do you support

@rahul-vinaudit we test everything on Ubuntu. What you are seeing is a Docker issue, not related to Selenoid at all.


Window freeze after moving tabs

OS: Arch with i3
If i want move a tab it freeze and i have to kill the process to restart atom.

Thanks for reaching out!
Besides filing out the template as mentioned below, this sounds like a duplicate of https://github.com/atom/tabs/issues/541 so you can subscribe there if you'd like.

We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way :grinning:


Preserve this value

(see gist)

I went ahead and merged this change, along with a unit test.  Thank you!
Published as v0.9.1


cartographer_ros build error "could not find a package configuration file provided by "tf2_eigen""

I followed the instructions but have problems:
......
_CMake Warning at /home/tmp/ros/share/catkin/cmake/catkinConfig.cmake:76 (find_package):
Could not find a package configuration file provided by "tf2_eigen" with
any of the following names:
tf2_eigenConfig.cmake
tf2_eigen-config.cmake

Add the installation prefix of "tf2_eigen" to CMAKE_PREFIX_PATH or set
"tf2_eigen_DIR" to a directory containing one of the above files.  If
"tf2_eigen" provides a separate development package or SDK, be sure it has
been installed.
Call Stack (most recent call first):
CMakeLists.txt:45 (find_package)
-- Could not find the required component 'tf2_eigen'. The following CMake error indicates that you either need to install the package with the same name or change your environment so that it can be found.
CMake Error at /home/tmp/ros/share/catkin/cmake/catkinConfig.cmake:83 (find_package):
Could not find a package configuration file provided by "tf2_eigen" with
any of the following names:
tf2_eigenConfig.cmake
tf2_eigen-config.cmake

Add the installation prefix of "tf2_eigen" to CMAKE_PREFIX_PATH or set
"tf2_eigen_DIR" to a directory containing one of the above files.  If
"tf2_eigen" provides a separate development package or SDK, be sure it has
been installed.
Call Stack (most recent call first):
CMakeLists.txt:45 (find_package)
-- Configuring incomplete, errors occurred!
See also "/apollo/modules/slam/catkin_ws/build_isolated/cartographer_ros/CMakeFiles/CMakeOutput.log".
See also "/apollo/modules/slam/catkin_ws/build_isolated/cartographer_ros/CMakeFiles/CMakeError.log".
<== Failed to process package 'cartographer_ros':
Command '['/apollo/modules/slam/catkin_ws/install_isolated/env.sh', 'cmake', '/apollo/modules/slam/catkin_ws/src/cartographer_ros/cartographer_ros', '-DCATKIN_DEVEL_PREFIX=/apollo/modules/slam/catkin_ws/devel_isolated/cartographer_ros', '-DCMAKE_INSTALL_PREFIX=/apollo/modules/slam/catkin_ws/install_isolated', '-G', 'Ninja']' returned non-zero exit status 1_
......
System config:
gcc version 4.8.5 (Ubuntu 4.8.5-2 ubuntu1~14.04.1)
ROS Indigo
Any help would be appreciated.Thanks!

sudo apt install ros-indigo-tf2-eigen
This might also be useful for you: https://github.com/googlecartographer/cartographer_ros/blob/master/scripts/install_debs.sh


Update/workflow inputs

required changes to the template after DIalogy MR#41

Thank you @us241098 can you please check the changes here? there is a big update planned. I believe I have taken care of your updates there as well but would be nice to have you review.

oh, haven't noticed that we are removing the jinja templates. yes, #13 is taking care of everything.


how you make an exe????

https://www.geeksforgeeks.org/convert-python-script-to-exe-file/ @webbrowser11

thanks btw how did you even see this so fast XD i never get this attention on my repos

@BDadmehr0

thanks btw how did you even see this so fast XD i never get this attention on my repos

Hey, no problem!, I was browsing for good issues to contribute to, and this one caught my eye. The solution seemed straightforward (just sharing a link), so I thought I’d help out. Thanks for the kind words! Keep up the great work on your repos!


Remove COSIGN_EXPERIMENTAL: "true" env variable for signing images

Starting with cosign v2.0.0, COSIGN_EXPERIMENTAL=1 is no longer required to have identity-based ("keyless") signing and transparency.
Ref: https://github.com/sigstore/cosign/blob/main/CHANGELOG.md#v200

Hi, @sandipanpanda thank you for your contribution. I have tested these changes, and it seems the signing is failing.
https://github.com/cilium/cilium/actions/runs/4699250917/jobs/8332495550?pr=24884


[Doc][Webhook] CircleCI Orb to send deployment webhook events

Documentation Scope
For the CircleCI Plugin, it still requires a Webhook even to report on deployments. I've created a CircleCI Orb to make this easy to implement for users of that CI/CD tool.
https://circleci.com/developer/orbs/orb/ezypay/devlake-orb?version=0.1.0
Describe the Change
I don't know where/how to document this. It might even be better to move this Orb project under this project/repo.
Screenshots
n/a
Additional context
I'm open to opinions on how to integrate this into the project.

Thank you for your contribution. And I have read your codes and comments in devlake-orb. It's perfect.
You must have read https://devlake.apache.org/zh/docs/Plugins/webhook/ ,  there is a doc about Circle CI https://devlake.apache.org/zh/docs/Plugins/circleci.  I think these two documents are both okay, and I prefer the former.
It's not a big problem.
DevLake's website is in this repo: https://github.com/apache/incubator-devlake-website, just open a PR and submit your changes.
cc @Startrekzky

@jeff-knurek I saw in your orb that the post URL has the webhook identifier hardcoded. The webhooks don't always have ID = 1.


[FLINK-6751] [docs] Add missing documentation for User-Defined Functions Page

Thank you very much for contributing to Apache Flink - we are happy that you want to help us improve Flink. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.
Please understand that we do not do this to make contributions to Flink a hassle. In order to uphold a high standard of quality for code contributions, while at the same time managing a large number of contributions, we need contributors to prepare the contributions well, and give reviewers enough contextual information for the review. Please also understand that contributions that do not follow this guide will take longer to review and thus typically be picked up with lower priority by the community.
Contribution Checklist

Make sure that the pull request corresponds to a JIRA issue. Exceptions are made for typos in JavaDoc or documentation files, which need no JIRA issue.

Name the pull request in the form "[FLINK-XXXX] [component] Title of the pull request", where FLINK-XXXX should be replaced by the actual issue number. Skip component if you are unsure about which is the best component.
Typo fixes that have no associated JIRA issue should be named following this pattern: [hotfix] [docs] Fix typo in event time introduction or [hotfix] [javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator.

Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.

Make sure that the change passes the automated tests, i.e., mvn clean verify passes. You can set up Travis CI to do that following this guide.

Each pull request should address only one issue, not mix up code from multiple issues.

Each commit in the pull request has a meaningful commit message (including the JIRA id)

Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below.

(The sections below can be removed for hotfixes of typos)
What is the purpose of the change

add missing (TODO) documentation for user-defined functions page

Brief change log

add missing (TODO) documentation for user-defined functions page
a typo fix in udagg comment

Verifying this change
-the documentation part has been manually verified by build_docs.sh
Does this pull request potentially affect one of the following parts:

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

Documentation

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

Please fill out the PR template, this will make the review process easier.

Thanks for the PR @shaoxuan-wang. I'll merge it.


Python port RFC

Would a Python port that doesn't need bash, and thus would be much easier to run on Windows, be something worth doing? I've done some work on that and am using it in-house. It will need more work before being ready for wider testing. If that's a direction the project would consider worthwhile, I'd take some time to work on it.
Ideally, I'd like Python as the only major dependency besides git, with necessary packages bundled, and have it runnable without installation, i.e. directly from a git checkout. The "main application" would have a CLI as it has now, and a minimal GUI that provides feedback, launches the file picker and browser, etc. The GUI would be tk-based to minimize dependencies.
Plan:

[ ] Cleanly port the exiting bash scripts to Python with minimal refactoring, and ensure that they work on all platforms. This wouldn't do much except dropping bash and awk (?) as dependencies. The architecture remains.
[ ] Add pure Python dependencies as submodules or sources checked into the codebase. The aim is to make it work for KiCad 7 and 8 with Python, git and KiCad as the only dependencies.
[ ] Refactor the scripts into a single application, potentially removing some dependencies if feasible.
[ ] Add the optional GUI.
[ ] Further cull dependencies if at all possible. KiCad has Python library code for accessing design databases, with backwards-compatibility. It should be possible eventually to make the application self-standing, i.e. with no dependencies other than Python, git, and KiCad libraries needed by the project (not even a KiCad binary).

I think redesign using python would be good. However I am not going to change Kiri. It is a bit complex task and I don't use this tool that much to justify this change. However feel free to start a new project to implement what you are proposing. Based on what you said it may be really good. Also, since it can be just a python script it can be easily added to Kicad's addon manager.


PatternFly milestone update

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

Project coverage is 76.96%. Comparing base (47bec97) to head (5fc8696).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1074   +/-   ##
=======================================
  Coverage   76.96%   76.96%
=======================================
  Files          68       68
  Lines         673      673
  Branches      119      100   -19
=======================================
  Hits          518      518
- Misses        139      155   +16
+ Partials       16        0   -16

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


Fix inconsistent brackets

Summary
Fix three sample files brackets.
Fixes #23574

Not sure why build isn't working unless I accidently fixed the wrong files. Will see if I can look over it again tomorrow maybe.

Not sure why build isn't working unless I accidently fixed the wrong files and don't know where the right ones are. Will see if I can look over it again tomorrow maybe.

@BenjaminMichaelis You need to add a csproj file:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net5.0</TargetFramework>
  </PropertyGroup>

</Project>

@Youssef1313

You need to add a csproj file:

Why would it be the case that a csproj file needs to be added for existing files that are just having small modifications done to them? Seems like if that was the case they would of been failing already before the modifications and that would be an issue of its own.

@Youssef1313

You need to add a csproj file:

Why would it be the case that a csproj file needs to be added for existing files that are just having small modifications done to them? Seems like if that is the case the build would of been failing already before the modifications in this PR and that would be an issue of its own or the case in previous modifications to these files.

The build is only triggered for modified files since not all code files in the repository have project files, and it's still a ton of work.

Thanks for making these changes @BenjaminMichaelis
As @Youssef1313 pointed out, many of our older samples didn't have projects ported over when they were migrated from MSDN. To fix this error, add a .csproj file as shown above.
One different recommendation:

If the build failed due to multiple entry points, consider splitting into different projects.

Another alternative is to specify the startup object in the project file. That's covered here: https://docs.microsoft.com/dotnet/csharp/language-reference/compiler-options/advanced#mainentrypoint-or-startupobject


Decompiled sources

Hello, @harrylepotter
It's nice to see continuation of electric-monk/pycarplay (which is great I think, by the way). Good work 👍
I've encountered this Gist, and I wonder where this come from? I've only found "decompilable" versions without wireless connection, probably older ones.
This one helped me with something (as I work on a node.js version of this receiver as a personal side-project), I wanted to thank you for sharing it. Maybe I could help with something as well, as I've got a bit familiar with this protocol, and took different approach with video/audio output streaming.

Hey @ppietak thanks for your message. Stoked that someone is getting value from the project!
For the gist shown, i essentially took the 'last known good version without malware' (found somehere on 4x4shop.ca - cant remember where) and ran it through an online Jad decompiler (http://www.javadecompilers.com/). It was then a matter of painstakingly looking at the decompiled output and cross-referencing/renaming symbols to something human readable, using @electric-monk's protocol.py as a reference of known parts of the protocol. I recall this taking the better part of a day to do over a thanksgiving weekend.
I seem to recall the 4x4shop.ca version of the .apk having support for the wireless connection, but i never really dug into it.

Cool! didn't know this website, indeed their version nicely decompiles itself 👍

It was then a matter of painstakingly looking at the decompiled output and cross-referencing/renaming symbols to something human readable, using @electric-monk's protocol.py as a reference of known parts of the protocol

Yeah, did't the same thing for myself - but once it starts making sense, I find it quite interesting :)
Thank you for all information. I think publish this node.js version too, but now I'm struggling a bit with sending a microphone input (it kinda worked for a moment, but usb connection "crashes" are still common, what I'm trying to avoid).

@ppietak did you ever get anywhere with your Node JS version?

@evy0311 kind of, I've put it off for a while, cause I had no spare time for it. I remember my main struggle was to send audio into the dongle properly, as no matter how I've tried (with various sample rates, bit depth, data buffering, etc), after some time of recording it was causing connection errors.
Other things work - receiving video, audio music+commands, wireless auto-connecting, mouse+keyboard mapping, although it may require some adjustments cause I didn't put any effort to make this setup easier for other people yet. And it may depend on a Raspberry Pi it's used on - initially I was developing it on RPI 3, but later I've reconfigured it for RPI 4.
https://github.com/ppietak/node-carplay

Awesome! I'll check it out here soon and see if I can mess around with it.

@ppietak Ive been playing around with your NodeJS version, and I can see everything happening in the console, but there is no video. This is on a RPi 4. Ideas?

@ppietak looking at it, do I need to implement something like mplayer or omxplayer to display the output from the frame buffer? Or should the application automatically have something pop up already that displays the CarPlay video?

Probably I'd have to put my hands on it again, and check it, but

I'm using framebuffer directly, which should simply draw pixels on a configured/chosen display, cause it seemed to be the fastest option
before that, H.264 needs to be converted to "rgb565le" buffer, and it happens with ffmpeg
I think I'll need to get through the setup once again to remind myself what had to be done in order to make it work, but I can't give this a priority right now, so I can't tell when I'll be able to do that. I remember that I used to check if fbdev is working, by piping some static images (with "cat" or something) onto the /dev/fb0 - maybe this will help somehow.

Definitely helps! I'll be toying around with this later this week to see where I can get with it.
I know you have the touchscreen stuff implemented, did you have actual CarPlay video displaying on the screen with touchscreen inputs working? If so I can try to tackle this and get it going.

Sorry for the delay, but yes - it worked on 7" Waveshare 1024x600 HDMI touchscreen. Without multi-touch (but I'm not sure if it's supported in CarPlay anyway).


Open & Link Tracking Documentation enhancement

In case of local only access to postal management portal (eg. ssh proxy or openvpn) it is not necessary to bind extra static ip for this purpose. Sample config is:

/etc/nginx/sites-enabled/default

server {
    listen 8080;
    server_name postal.example.com;
    return 301 https://$host:8443$request_uri;
}

server {
    listen 8443 ssl;
    root /opt/postal/app/public;
    server_name postal.example.com;
...
location / {
       client_max_body_size 50M;
       try_files $uri $uri/index.html $uri.html @puma;
    }

location /assets {
       add_header Cache-Control max-age=3600;
    }

location @puma {
       proxy_set_header X-Real-IP  $remote_addr;
       proxy_set_header Host $host:8443;
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
       proxy_set_header X-Forwarded-Proto https;
       proxy_pass http://<IP_ADDRESS>:5000;
    }

/opt/postal/config/postal.yml

web:
  # The host that the management interface will be available on
  host: postal.example.com
  # The protocol that requests to the management interface should happen on
  protocol: https

fast_server:
  # This can be enabled to enable click & open tracking on emails. It is disabled by
  # default as it requires a separate static IP address on your server.
  enabled: true
  bind_address: <IP_ADDRESS> # the only internal static ip
...
smtp_server:
  tls_enabled: true

/etc/hosts on your local machine (# ssh local port forwarding for 8443)

...
<IP_ADDRESS> postal.example.com
...

Fast server uses 80 and 443 ports by default and management portal can be accessed via https://postal.example.com:8443

This is an interesting alternate configuration as long as people who use the interface will know the port to connect to.

Yes, that's right.

For convenience, could fast_server then be modified to redirect to e.g. port 8080 for requests that are obviously not from tracking links? Would there be any potential pitfalls in doing this?

The point of this configuration is to make port 80 and 443 available for the fast server to process click tracking.
https://github.com/atech/postal/blob/master/config/postal.defaults.yml suggests that you can also control the ports used by click tracking but theoretically you are going to be tracking links more than visiting the postal interface so it makes more sense to keep the click tracking links simple.
If you want to change the ports that click tracking uses then apparently theres nothing stopping you.

The suggestion was rather that it might be possible to still allow access to the management interface on the default port by having fast_server redirect to postal.example.com:8080 when it receives a request that's not a click/load request (e.g. an empty path).
In other words, people who use the interface wouldn't have to know what port to connect to.

I understand you now.
It might be possible to add in this feature however that would mean that anyone with any valid click tracking link could end up at your Postal login screen so could be viewed as an exposure risk.

Yes, that crossed my mind as well. Given the already public nature of the server (reverse-dns, MX records, etc.), this may be acceptable. Only an 'invalid' tracking/open request would result in redirection, otherwise it's processed normally.
My other concern is whether Certbot, as it's currently used, would support validation/renewal correctly with a single IP configuration, such that a valid certificate is always available to both server processes.


Obfuscating Dart code Error

Running the command
flutter build apk --obfuscate --split-debug-info=/<project-name>/<directory>
Error result:
FAILURE: Build failed with an exception.

* Where:
Script '/opt/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 896

* What went wrong:
Execution failed for task ':app:compileFlutterBuildRelease'.
> Process 'command '/opt/flutter/bin/flutter'' finished with non-zero exit value 1

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

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

BUILD FAILED in 22s
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done                      23.7s
Gradle task assembleRelease failed with exit code 1

flutter doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 1.20.4, on Linux, locale en_GB.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.49.2)
[!] Connected device
    ! No devices available

! Doctor found issues in 1 category

flutter build apk --obfuscate --split-debug-info=/<project-name>/<directory> is not a valid command, you need to run something like flutter build apk --obfuscate --split-debug-info=debug_info
@beingcoderr

flutter build apk --obfuscate --split-debug-info=/<project-name>/<directory> is not a valid command, you need to run something like flutter build apk --obfuscate --split-debug-info=debug_info
@beingcoderr

Thanks it worked. I followed the following documentation.
https://flutter.dev/docs/deployment/obfuscate

flutter build apk --obfuscate --split-debug-info=debug_info command does complete without any error but after doing flutter install on a physical device, app installs but crash on the very begining.
Where as flutter build apk --obfuscate --split-debug-info=/<project-name>/<directory> again giving following error
`FAILURE: Build failed with an exception.

Where:
Script 'C:\Programs\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 904

What went wrong:
Execution failed for task ':app:compileFlutterBuildRelease'.

Process 'command 'C:\Programs\flutter\bin\flutter.bat'' finished with non-zero exit value 1

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

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

BUILD FAILED in 20s
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done                      21.3s
Gradle task assembleRelease failed with exit code 1`
Also Why this command flutter build apk --obfuscate --split-debug-info=/<project-name>/<directory>  is not a valid command? As this exactly how it states on official flutter docs  https://flutter.dev/docs/deployment/obfuscate
My flutter doctor output
[√] Flutter (Channel stable, 1.22.5, on Microsoft Windows [Version 10.0.17763.1697], locale en-GB) [!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)     X Android license status unknown.       Run flutter doctor --android-licenses to accept the SDK licenses.       See https://flutter.dev/docs/get-started/install/windows#android-setup for more details. [√] Android Studio (version 4.0) [√] Connected device (1 available)

flutter build apk --obfuscate --split-debug-info=debug_info command does complete without any error but after doing flutter install on a physical device, app installs but crash on the very begining.
Where as flutter build apk --obfuscate --split-debug-info=/<project-name>/<directory> again giving following error
`FAILURE: Build failed with an exception.

Where:
Script 'C:\Programs\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 904

What went wrong:
Execution failed for task ':app:compileFlutterBuildRelease'.

Process 'command 'C:\Programs\flutter\bin\flutter.bat'' finished with non-zero exit value 1

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

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

BUILD FAILED in 20s
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done                      21.3s
Gradle task assembleRelease failed with exit code 1`
Also Why this command flutter build apk --obfuscate --split-debug-info=/<project-name>/<directory>  is not a valid command? As this exactly how it states on official flutter docs  https://flutter.dev/docs/deployment/obfuscate
My flutter doctor output
[√] Flutter (Channel stable, 1.22.5, on Microsoft Windows [Version 10.0.17763.1697], locale en-GB) [!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)     X Android license status unknown.       Run flutter doctor --android-licenses to accept the SDK licenses.       See https://flutter.dev/docs/get-started/install/windows#android-setup for more details. [√] Android Studio (version 4.0) [√] Connected device (1 available)

@Faizan-sts  did you manage to get it working?
flutter build apk --obfuscate --split-debug-info=/<project-name>/<directory> command can't work if you type it into your terminal like this.
You need to type flutter build apk --obfuscate --split-debug-info=./debug/debug for example to specify a path to the debug file


chore(main): release 1.4.0

:robot: I have created a release beep boop
1.4.0 (2023-10-11)
Features

🚀 添加在线检查更新功能 (8de04e0)

Bug Fixes

🔨 修复无线配对时表单验证错误 (7cd9ea3)
🔨 修复直接进行无线连接时没有处理配对设备的问题 (4263d07)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/viarotel-org/escrcpy/releases/tag/v1.4.0 :sunflower:


Scheduling issue

Hi,
I initially scheduled a job to run at 5AM every minute for an hour and then rescheduled it to run at 7AM once a day. For some reason the job still runs at 5AM. Is there a config persistence that I need to clear?
Thanks,
Karthik

Hi,
I initially scheduled a job to run at 5AM every minute for an hour and then rescheduled it to run at 7AM once a day. For some reason the job still runs at 5AM. Is there a config persistence that I need to clear?
Thanks,
Karthik

I think it's good idea to always use the destroy method after any recurring job if finished. Although you'd have to create another cron job to kill that job and itself.
var cron = require('node-cron');

var task = cron.schedule('* 5 * * *', () =>  {
  console.log('running task every minute past 5AM');
});

var endtask = cron.schedule('0 6 * * *', () =>  {
  console.log('end the recurring task, and this task at 6AM');
  task.destroy();
  endTask.destroy();
});

Hi,
I initially scheduled a job to run at 5AM every minute for an hour and then rescheduled it to run at 7AM once a day. For some reason the job still runs at 5AM. Is there a config persistence that I need to clear?
Thanks,
Karthik

I think it's good idea to always use the destroy method after any recurring job if finished. Although you'd have to create another cron job to kill that job and itself.
var cron = require('node-cron');

var task = cron.schedule('* 5 * * *', () =>  {
  console.log('running task every minute past 5AM');
});

var endtask = cron.schedule('0 6 * * *', () =>  {
  console.log('end the recurring task, and this task at 6AM');
  task.destroy();
  endTask.destroy();
});

Thanks Jon for the reply.
I have redeployed the script with a new cron(7 AM) schedule but somehow the job is still running with the old cron(5 AM).
In the current state, my script doesn't have any traces of the 5 AM cron.  Will it persist all the old crons?
Thanks.

I don't know what your environment looks like... but on my end if I stop my node instance from running that will automatically end all cron jobs in memory.
Try stopping your node instance completely, restart it with your new script.

Does this cron job run to complete the missed schedule post restart or stopped node for a while and start back?

I initially scheduled a job to run at 5AM every minute for an hour and then rescheduled it to run at 7AM once a day.

Your crontimes string ''* 5 * * *'' is built to repeat every day. Before calling the cron.schedule you could build the string with the current day only so that it will only schedule on that particular day.


Add the option to change the UI Theme at runtime

Type of Change

[x] New feature
[x] UI/UX improvement

Description
This PR Adds a new Button to Switch from Light to Dark Mode at runtime.
Winutil will persist the setting across reboots and start with the latest theme used.
Impact
As this PR completely overhauls how the Properties for the UI Elements are stored (now as Resource Objects), it touches almost EVERY UI Element. Still, IMHO this creates a good foundation to unify how we handle properties like colors in the future in a scalable, maintainable way.
Testing
Tested on Win11
Please test thoroughly as this revamps many of the UI internals and might have missed something.
Issue related to PR

Resolves #2696

Additional Information
I simplified the themes (completely removed the pulsing) and decided to keep only a Light and a Dark Theme. This can be easily extended in the future, for example, to allow more than 2 Themes or even Custom Themes that the user can modify.

[x] Check if it's possible to reimplement the pretty Togglebuttonstyles
[x] Rename _default to "Lite" and recreate a section and logic in the json and ps1 to hold common settings
[x] Check what logic in Set-WinUtilUITheme is needed (e.g. loading themes to a PSObject)
[x] Check it the other options (font sizes etc.) can also be loaded as a Resource
[x] Make the Theme change persistent across app reboots
[x] Unify / optimize coding style and cleanup tasks
[x] Document Changes

Hey Marterich
Just tested this and the refactor is much easy to customize now. The redundant values were removed that a plus point but seems that the changes made in #2722 were not implemented.

Hey Marterich Just tested this and the refactor is much easy to customize now. The redundant values were removed that a plus point but seems that the changes made in #2722 were not implemented. Also instead of light and dark theme switch there should be option to switch between themes

I've reimplemented the Theme changes you referenced.
Regarding a Dropdown menu or something to manually select the Theme, I would mark this up as "future development potential for a later PR"


Hombridge 0.4.24 results in issues with homebridge-nest  1.2.2

When updated to Homebridge 0.4.24 / hap-nodejs 0.4.29 I received the following error.  I have fallen back to Homebridge 0.4.22 / hap-nodes 0.4.27 and the issue was resolved.
[8/15/2017, 7:04:33 PM] TypeError: Cannot read property 'on' of undefined
at NestThermostatAccessory.NestDeviceAccessory.bindCharacteristic (/usr/local/lib/node_modules/homebridge-nest/lib/nest-device-accessory.js:65:9)
at NestThermostatAccessory.NestDeviceAccessory (/usr/local/lib/node_modules/homebridge-nest/lib/nest-device-accessory.js:52:10)
at new NestThermostatAccessory (/usr/local/lib/node_modules/homebridge-nest/lib/nest-thermostat-accessory.js:35:22)
at Object. (/usr/local/lib/node_modules/homebridge-nest/index.js:117:23)
at Object. (/usr/local/lib/node_modules/homebridge-nest/index.js:124:4)
at /usr/local/lib/node_modules/homebridge-nest/index.js:152:28
[8/15/2017, 7:04:33 PM] Falling back to legacy API.
[8/15/2017, 7:04:34 PM] Away for Nest is: false
[8/15/2017, 7:04:34 PM] Temperature unit for Nest is: Fahrenheit
[8/15/2017, 7:04:34 PM] Current temperature for Nest is: 26.92999
[8/15/2017, 7:04:34 PM] Current heating for Nest is: 2
[8/15/2017, 7:04:34 PM] Current humidity for Nest is: 61
[8/15/2017, 7:04:34 PM] Target heating for Nest is: 2
[8/15/2017, 7:04:34 PM] Target temperature for Nest is: 26.666666666666668
[8/15/2017, 7:04:34 PM] Initializing platform accessory 'Nest'...

It looks like the plugin is setting the "Software Revision" characteristic which Apple removed. Let me review a few areas to see what can be done to help make it more compatible. We added the characteristic so they are available, but it seems that optional characteristics being removed have caused some issues.
I'm looking to see if the code can be safely tweaked to allow adding other characteristics the way that this plugin was adding the optional ones.

Give it a try with Homebridge 0.4.25 which was just updated.

Although Homebridge seems to run OK I am receiving the following warning when initial starting:
HAP Warning: Characteristic 00000054-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 0000003E-0000-1000-8000-0026BB765291. Adding anyway.
Regards,
Doug

Douglas Blakeley
<EMAIL_ADDRESS>On Aug 16, 2017, 1:26 AM -0400, pdlove<EMAIL_ADDRESS>wrote:

Give it a try with Homebridge 0.4.25 which was just updated.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

That is expected. HomeKit no longer has Characteristic 54 (Software Version) as an optional characteristic for the the service 3E (Accessory Info). The plugin developer needs to resolve that, but everything should work fine unless Apple starts rejecting that characteristic.  The warning is there to make sure people are aware in case they start having trouble. I'm going to try and determine a simple way to add the textual name, but for now the UUID will have to work.

Hi,
Thanks for the prompt explanation.  Looks like the problem is in the homebridge-nest package.  The error is generated for the Nest Thermostat and then the Nest Protect.  I will post a problem report on the homebridge-nest page.
Regards,
Doug

Douglas Blakeley
<EMAIL_ADDRESS>On Aug 16, 2017, 11:49 AM -0400, pdlove<EMAIL_ADDRESS>wrote:

That is expected. HomeKit no longer has Characteristic 54 (Software Version) as an optional characteristic for the the service 3E (Accessory Info). The plugin developer needs to resolve that, but everything should work fine unless Apple starts rejecting that characteristic. The warning is there to make sure people are aware in case they start having trouble. I'm going to try and determine a simple way to add the textual name, but for now the UUID will have to work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Make sure you link this issue there as well. Everything should run fine despite the warning.

Since upgrading to iOS11, my Nest Thermostat is no longer recognised by the Home app.  There’s an icon, but it has an error against it, and the “Type” is not set.  Could this be related to the “HAP Warning” error (which I am also getting when I start homebridge)?

I have not had an issue with iOS 11 and my Nest Thermostat.  I would suggest restarting your iPhone (restart, not power off/on), restart Homebridge, and then relaunch the Home app on your iPhone.  If you are using an Apple TV or iPad for automations and remote access I suggest that you also restart this device also.
My understanding is that the HAP warning is due to the query on "software version" which is no longer supported by HomeKit and is probably not the cause of your problem.


Python 3 support

Have a lot of errors on python3.4 with str & byte convert.
Example, when i try used Frame() or feedback_server.items() a was error

"TypeError: Can't convert 'bytes' object to str implicitly"

For second trouble i fixed it simply:
apns.py
def items(self):
      """
      A generator that yields (token_hex, fail_time) pairs retrieved from
      the APNs feedback server
      """
      buff = b'' #changed buff = '' to buff = b''

But cant fixed the same for Frame()

Just change '/xx' to b'/xx'
And all working now.

Another Python 3 compatibility issue (tested with 3.6.0):
  File "/Users/jason/.virtualenvs/cv/lib/python3.6/site-packages/apns.py", line 218     except ssl.SSLError, err:                        ^ SyntaxError: invalid syntax
Also, not sure what version of Python 3 is supported, might be good to add that somewhere to the README.md.

This is something that is in mind, but I don't have time to follow-up right now.

@jd20 the code you're quoting doesn't exist any more on the master branch, but the version of the library on PyPi is out of date (see https://github.com/djacobs/PyAPNs/issues/163). The master version from GitHub should be usable on Python 3.


Correct rectangle size for Captcha background

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
no

Fixed issues

can you briefly describe the problem? also we need a CHANGELOG entry to merge it.

This is not a bug.
Function "imagefilledrectangle" gets rectangle as "x1, y1, x2, y2", so to fill rectangle on entire image we need to pass 0, 0, width-1, height-1. Now passed 0, 0, width, height, that 1 pixel more than needed on both axis.

OK. imagefilledrectangle uses coordinates and these are 0-indexed. The fix is valid.

Merged. Thank you.


Accept multiple --group-match for OR search.

Related to :

https://github.com/awslabs/ssosync/pull/55

https://app.shortcut.com/cartoteam/story/198357/configure-aws-sso


Remaining charge time not updating

Hi,
The remaining charge time sensor doesn't seem to update. The ID app is clear of anything however the HA integration shows time remaining.
Thanks.

This is a known bug. Dont have a fix for it yet
https://github.com/mitch-dc/volkswagen_we_connect_id/issues/111


fix: when resolving dependencies the branch attribute should be preferred

When resolving package version dependencies the branch attribute of the dependency should be used to select the package version, not the branch name in the parameter unless the dependency doesn't specify a branch.
For example, my dependency below failed to resolve when building a package version because an equivalent build number (<IP_ADDRESS>) doesn't exist on branch dev when running the command:
sf package version create -p myPackage -b dev -k redacted -w 30 --code-coverage
"dependencies": [         {           "package": "myPackageDependency",           "versionNumber": "<IP_ADDRESS>",           "branch": "build"         },
I have built and linked packages locally and can verify this patch resolved the issue.

@David-Polehonski - Thank you for the PR!  I'll get this merged in but we should have a unit test for it.  Should be pretty simple.  I'd just copy the 'should create the package version create request with branch' test (lines 319-337 of packageVersionCreate.test.ts) and modify it to pass in a dependency.branch and verify the correct branch was passed to the packageCreateStub.

@David-Polehonski @shetzel @cristiand391
We faced with the same issue last week and suggested a bit different fix here: https://github.com/forcedotcom/cli/issues/2183
Our suggestion:
const branch = (dependency.branch || dependency.branch === '') ? dependency.branch : this.options.branch;
Current fix by @David-Polehonski :
const branch = dependency.branch === '' ? this.options.branch : dependency.branch;
Our concern is that current fix introduce a wrong behaviour if branch is specified for dependency explicitly as empty, e.g.:
"dependencies": [
  {
    "package": "My Base Package",
    "versionNumber": "1.8.0.LATEST",
    "branch": ""
  }
]

In such case, if we create a package version from command line specifying branch key explicitly (e.g. --branch=myTestBranch), it should still respect empty branch dependency (according to sfdx guide), but with @David-Polehonski fix seems like it's going to be overwritten and would be looking for 'My Base Package' version dependency within myTestBranch, which is incorrect.


spec refers to hardware vector table as a load

Apologies if I am missing something, but it is unclear to me how you return to the interrupted context when a fault occurs accessing the vector table based off xtvt.
The spec says "If there is an access exception on the table fetch, xepc is written with the faulting address", but that would immediately overwrite the PC of the interrupted context before there has been any opportunity to save it.
I also noticed that spec is consistent in referring to the vector table access as a fetch (for the purposes of permission checking etc) rather than a load, apart from:
"The inhv bit when set at xRET informs hardware to repeat the table load using the address in
xEPC to obtain the address of the trap handler that is then written to the PC instead of
directly writing xEPC to the PC. ........ The more privileged
layer does not have to distinguish CLIC vector table reads from other forms of data
page fault and can handle them using exactly the same code."
Any clarification  on these two points would be helpful.

that's correct that if the access exception on the table fetch is the same priv as the interrupt handler, that xepc is lost.  that's what the spec means when it says:  Horizontal traps (same privilege level) are unrecoverable.
But we should probably clarify that statement since systems can figure out ways to recover but we just mean that the interrupted context is lost.

But I think both vertical and horizontal interrupted contexts are corrupted as the PC of the interrupted context would always be stored in xepc (with its privilege level in xpp), the value of xepc would then be immediately over-written with the faulting vector table entry address.

vertical should be ok.
When a trap is taken into S-mode, sepc is written with the virtual address of the instruction
that was interrupted
if there is an access exception into m-mode due to the table fetch:
When a trap is taken into M-mode, mepc is written with the virtual address of the instruction that encountered the exception.
so in vertical interrupt contexts, it is a different epc.
but I guess you may have understood vertical to just mean the u-mode code is interrupted to m-mode handler as being the vertical interrupt context?  The clic spec intends vertical to mean the interrupt handler and the exception handler are vertical.

I think the bottom line is that the mechanism does not support delivery of interrupts into m-mode. In particular, in a U/M system (assuming no N extension) it is not a recoverable situation so perhaps the scheme should be  omitted altogether from those profiles.

Closed with https://github.com/riscv/riscv-fast-interrupt/commit/edc9d203ad3956d54e85221448b7bb5e28f34eaa


Bugfix/docker build memory

Jenkins builds were failing, apparently due to a single file in the AWS CPP SDK that we compile in.  I found this issue which had the same error.
https://github.com/awslabs/aws-lambda-cpp/issues/14
Here is my jenkins log showing the same error happening:  https://jenkins.corp.alleninstitute.org/job/docker-images/job/agentsim/job/main/8/execution/node/22/log/
It appears that the build was basically causing memory issues with the compiler on our Jenkins machines.  It's not trivial to add memory capacity on Jenkins.
I discovered that the AWS SDK has a build flag to avoid this situation which slows the build down but requires less memory.
Switching the build flag seems to make the build happy again.

For more context on the changes, a "unity build" generally means you bundle a whole bunch of code files under one single file in an automatic way at build time.   This lets you compile fewer files but at the cost of having a larger file to compile.


MAINT: Update vendored uarray version

Reference issue
See gh-11272 and the associated pypy issue 3131
What does this implement/fix?
This updates the vendored uarray version to include compilation fixes for pypy3's C-API from Quansight-Labs/uarray#218.
This should mean that scipy can be built with the latest pypy3. Haven't confirmed yet though.

I tried building scipy under pypy3 but run into a few other issues

pybind11's headers install to a bad location with pypy's distutils pypy/pypy#3140.
scipy.linalg.interpolative is failing to link with lots of multiple definition errors

That said, building fft and _lib as stand-alone modules does work.

scipy.linalg.interpolative is failing to link with lots of multiple definition errors

Hmm, that used to work. I think commit 6fb2a329a3242ab is the only one that could have affected this since we removed PyPy from CI in April 2019. Or it's a PyPy issue of course.

This LGTM, so merging. Thanks Peter

Okay, so #11176 was the issue. I ran the build once before rebasing on master and that left the old split files in the linalg/src directory. After rebasing on master, the file glob in #11176 picked up both the original and the split sources.
After running a git clean, the build succeeds.

Added backport label since this fixes 1.4 for pypy users.

In the context of backports here is a patch that I used to fix this for the 1.4.1 release generated using the following command
git diff v1.4.1 a2a4c6a3ec9b03c0cbb809930cf268532d7c97f6 -- \
scipy/_lib/_uarray/__init__.py  \
scipy/_lib/_uarray/_backend.py  \
scipy/_lib/_uarray/_uarray_dispatch.cxx  \
scipy/_lib/_uarray/scipychanges.patch \
scipy/_lib/uarray.py


feat: add the table's color according to table settings

Hi @BOCOVO
I also actively use your plugins. headerColor setting is also useful for our visualization. So I decide to make the changes and contribute into the plugin.
Added:

Add headerColor in table settings #30

Hi @tv-long !
I'm very happy to hear you're using the plugin.
Thank you very much for your contribution ❤ , it is an essential feature.
I'll merge the PR and release a new version as soon as possible so you can enjoy the functionality straight away.

Thanks a lot @tv-long ! It works fine 🔥 .


New repo in which to put experimental scripts

When developing code working with new data or similar, that code will not necessarily be part of the framework or other established repos. Would still be useful to have under version control and shared between us. Maybe we can create a new repo to hold such code?

can't a branch do?
I guess we could keep it updated often with the master and never merge it in.

Branch or specific directory like (/demo /examples) might be appropriate for scripts related to specific ccpi module.
If the scripts and data would be horizontal accross CCPi modules then I'd recommend to consider new repo or use some existing horizontal repo (e.g. CCPi-VirtualMachine already has some demo code, demo Jupyter notebooks using multiple CCPi and other related stuff).
For small-medium data github is OK. For large data I recommend rather Zenodo and reference it from scripts.

Thanks both. What I have in mind is code that is not demos and not to be
distributed routinely as part of our software. Rather it is scripts and
analysis and playing around with new data using various parts such as the
framework, maybe regularisation toolkit or other things.
On Thu, 14 Feb 2019, 11:06 Tomas Kulhanek<EMAIL_ADDRESS>wrote:

Branch or specific directory like (/demo /examples) might be appropriate
for scripts related to specific ccpi module.
If the scripts and data would be horizontal accross CCPi modules then I'd
recommend to consider new repo or use some existing horizontal repo (e.g.
CCPi-VirtualMachine already has some demo code, demo Jupyter notebooks
using multiple CCPi and other related stuff).
For small-medium data github is OK. For large data I recommend rather
Zenodo and reference it from scripts.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vais-ral/CCPi-Framework/issues/182#issuecomment-463587442,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJg5CPAK3GG97HoBre6i7S7XN1x60oz_ks5vNUMsgaJpZM4a7N9F
.

OK. Then for dirty stuff separate repository would be better as it will not affect branch of existing one.

Github allows free private repos and you can invite 3 collaborators.
Or use paid account for private repo without limitation
I have such repository for some of my past research - about 20% polished and coppied to another repository as demos. The rest 80% kept in dirty stuff.

@paskino Could you set up a private repo, named something like CCPi-framework-sandbox that we could use for this purpose?


Add more facts

I am new to open source and I would like to make my first contribution by adding some more interesting facts to facts.json

Sorry for the late reply! Feel free to contribute at any time. 😄


Link to wiki pages

Resolves #239

This change is

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

Comparison is base (0e04bae) 71.68% compared to head (8d9bcae) 71.68%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #241   +/-   ##
=======================================
  Coverage   71.68%   71.68%
=======================================
  Files         133      133
  Lines        5827     5827
  Branches      924      924
=======================================
  Hits         4177     4177
  Misses       1225     1225
  Partials      425      425

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


FOR THOSE WHO HAVE ISSUES WITH HTTPX

So, you know that I choose HTTPX and removed Requests.
But I can see a ton of people who have issues with HTTPX.
Please, post here any problems and issues that HTTPX causes.
Any other issues will be just removed from here.
You should provide:

full code that you tried to run
full logs of running code that you provided INCLUDING ERROR THAT HTTPX CAUSED
python version
libs versions (httpx and aminofixfix)

What you should try first:

reinstall python (or pydroid if you use this.. "godlike" thing)
reinstall httpx and aminofixfix
set timeouts to zero

Thanks!

Freezing the issue as I don't see any complaints about HTTPX + Requests support has been done.


Gpl 988 investigate queries for kanban

First iteration of kanban / swimlane view of work in progress, for Heron lab staff / managers.
GPL-988 and GPL-953
Linked PR in Sequencescape - https://github.com/sanger/sequencescape/pull/3188

@JamesGlover Thanks for the comments, they were really helpful. I think I've addressed them all. Could you have another look please? Then I'll probably deploy to training so that the users can have a go with it with realistic data.


Issue

Alen is requesting jenkins user access to build-osuosl-ppc64le-ubuntu-16.10

@alenbadel how long will you require access?

Access requested until Wednesday Dec. 13, 2017

@alenbadel
Alen, please give a reason why you are requesting access.

Hi, all.
I was able to fix up OpenJ9 issue 769. I don't require access anymore to the PPCLE machines.
Thank you for the resources.

Access has been revoked.
closing issue

@bblondin Seems another issue has come up in regards to OpenJ9 Issue 769 blocking PPCLE builds on adoptOpenJDK.
Could I get access back to the system?

@alenbadel I think we are all fixed now


Airflow native UI integration improvements

Narrows the Connection fields required down to login and password, representing API Key and API Secret, respectively.
Removes the fallback_connector_id from the example_dag.py, we'd rather have these fail if a connector is not specified.

Self-approved so we can build a candidate package.


saveBlockListToBucket and return error:  AccessControlListNotSupported:

Configured the settings as per the document. When doing the test the IP is showing in DynamoDB but the S3 action of creating the object ip_blocklist is not working. Verified the Cloudwatch and the following error is showing
2022-01-25T10:54:35.629Z	c356fb0f-d991-4bba-b620-0487a211c007	INFO	calling generator script.
2022-01-25T10:54:36.223Z	c356fb0f-d991-4bba-b620-0487a211c007	INFO	called scanDBTable: scan completed.
2022-01-25T10:54:36.385Z	c356fb0f-d991-4bba-b620-0487a211c007	INFO	called bucketExists: no error.
2022-01-25T10:54:36.709Z	c356fb0f-d991-4bba-b620-0487a211c007	INFO	called saveBlockListToBucket and return error:  AccessControlListNotSupported: The bucket does not allow ACLs    at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/services/s3.js:699:35)    at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:106:20)    at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:78:10)    at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:688:14)    at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10)    at AcceptorStateMachine.runTo (/var/runtime/node_modules/aws-sdk/lib/state_machine.js:14:12)    at /var/runtime/node_modules/aws-sdk/lib/state_machine.js:26:10    at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:38:9)    at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:690:12)    at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
END RequestId: c356fb0f-d991-4bba-b620-0487a211c007
Also during the IAM policy creation which grants permissions to operate on the S3 bucket, It is notice that there is not HeadBucket Access level which is mentioned in the document.
Please let me know what is missing in the S3 permission and how this can be resolved.

Configured the settings as per the document. When doing the test the IP is showing in DynamoDB but the S3 action of creating the object ip_blocklist is not working. Verified the Cloudwatch and the following error is showing
2022-01-25T10:54:35.629Z c356fb0f-d991-4bba-b620-0487a211c007 INFO calling generator script. 2022-01-25T10:54:36.223Z c356fb0f-d991-4bba-b620-0487a211c007 INFO called scanDBTable: scan completed. 2022-01-25T10:54:36.385Z c356fb0f-d991-4bba-b620-0487a211c007 INFO called bucketExists: no error. 2022-01-25T10:54:36.709Z c356fb0f-d991-4bba-b620-0487a211c007 INFO called saveBlockListToBucket and return error: AccessControlListNotSupported: The bucket does not allow ACLs at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/services/s3.js:699:35) at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:106:20) at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:78:10) at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:688:14) at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/var/runtime/node_modules/aws-sdk/lib/state_machine.js:14:12) at /var/runtime/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:38:9) at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:690:12) at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:116:18) END RequestId: c356fb0f-d991-4bba-b620-0487a211c007
Also during the IAM policy creation which grants permissions to operate on the S3 bucket, It is notice that there is not HeadBucket Access level which is mentioned in the document.
Please let me know what is missing in the S3 permission and how this can be resolved.

Hi @sreekumarpg Please read the AWS documentation here: PutObjectAcl
And read the ! Important note in red on the above doc.

@JaydenLiang , Thanks for the update.
I have enabled the Public access to the S3 bucket and enabled ACL to Everyone list/read. Now the IP is updating in the S3 bucket ip_blocklist object.


ELCC 2: Add Pull Request and Issue Templates

Fixes https://yg-hpw.atlassian.net/browse/ELCC-2
Context
In the past I've found it helps to keep me focused on smaller solutions when I have a Pull Request and Issue template.
See https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository
Testing Instructions

Begin the issue creation wizard in the repo and see what it looks like. I think this will only work once changes are in main?
Do the same with the PR template. I think this will only work once changes are in main?

Created this in the wrong repo again ...

See https://github.com/icefoganalytics/elcc-data-management/pull/41


Add Node 11 support

Fixes #2521

[x] wait for Node 11 on TravisCI
[ ] wait for Node 11 on AppVeyor https://github.com/appveyor/ci/issues/2707
[ ] make any necessary binding changes

Seeing a compilation failure on Linux builds
 g++-4.7 '-DNODE_GYP_MODULE_NAME=libsass' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DLIBSASS_VERSION="3.5.4"' -I/home/travis/.node-gyp/11.0.0/include/node -I/home/travis/.node-gyp/11.0.0/src -I/home/travis/.node-gyp/11.0.0/deps/openssl/config -I/home/travis/.node-gyp/11.0.0/deps/openssl/openssl/include -I/home/travis/.node-gyp/11.0.0/deps/uv/include -I/home/travis/.node-gyp/11.0.0/deps/zlib -I/home/travis/.node-gyp/11.0.0/deps/v8/include -I../src/libsass/include  -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -fno-omit-frame-pointer -std=gnu++1y -std=c++0x -fexceptions -frtti -MMD -MF ./Release/.deps/Release/obj.target/libsass/src/libsass/src/ast.o.d.raw   -c -o Release/obj.target/libsass/src/libsass/src/ast.o ../src/libsass/src/ast.cpp
g++-4.7: error: unrecognized command line option ‘-std=gnu++1y’

If gnu++1y is needed, then gcc 4.7 is too old.
https://github.com/nodejs/node/blob/v11.0.0/BUILDING.md#unixmacos  says
gcc and g++ 4.9.4 or newer, or
clang and clang++ 3.4.2 or newer (macOS: latest Xcode Command Line Tools)

We need to keep the old compiler for the other systems. I wonder which systems we can no longer support on 11 due to this requirement.

@saper I fixed that error by making sure it had GCC 4.9 for 11.
It does look like FreeBSD 10 was dropped for Node 11 https://nodejs.org/en/blog/release/v11.0.0/ so that might affect your binary builds

Thanks, I noticed that - I am using 10 to build the modules but there is no problem to switch to 11 if needed. Fortunately a supported clang is available on both versions.

np, and it probalby makes sense to keep building <11 on FreeBSD 10 if you have the capacity to keep it around. I'm not really sure if that makes sense in terms of how people upgrade the distros in the FreeBSD world.

Solution

upgrade or reinstall node-sass and sass-loader

AppVeyor has added Node 11 support. We've begun the process of building the binaries.

Try now


Demo link not working

Hi @mduvall! I wasn't sure if it was still being maintained but incase it is - the demo link doesn't seem to be working, could you please take a look?

oh my, now it's 2018-5-29.
I am also about to report the demo link not working.

Clearly, no one maintaining this anymore.


[bug] Inconsistent behavior in QueryVulnsViaVulnNodeNeighbors

Description
When running the command guacone query vuln "pkg:guac/spdx/ghcr.io/guacsec/vul-image-latest" --vuln-id "ghsa-7rjr-3q55-vv33" --search-depth 1 --num-path 1, it sometimes fails with the error message:
"level":"fatal","ts":1698673615.8497112,"caller":"cmd/vulnerability.go:123","msg":"error querying neighbor: error certify vulnerability node not found, incomplete data. Please ensure certifier has run"

This error occurs because the node ID passed as the vulnerabilityNodeID parameter in QueryVulnsViaVulnNodeNeighbors is not a *model.NeighborsNeighborsCertifyVuln. https://github.com/guacsec/guac/blob/b178fcd705990574f704a72ddde82e2dfb6c8948/cmd/guacone/cmd/vulnerability.go#L332-L342.
The problem stems from the fact that multiple IDs are available, but only the first one, vulnResponse.Vulnerabilities[0].VulnerabilityIDs, is being passed. The command's inconsistent behavior is due to the first ID not being a *model.NeighborsNeighborsCertifyVuln.
https://github.com/guacsec/guac/blob/b178fcd705990574f704a72ddde82e2dfb6c8948/cmd/guacone/cmd/vulnerability.go#L117-L121
Expected Behavior
The function QueryVulnsViaVulnNodeNeighbors should be able to handle multiple IDs from vulnResponse.Vulnerabilities[0].VulnerabilityIDs and not just the first one. This would ensure consistent behavior and accurate vulnerability querying.
Steps to Reproduce

Run the command guacone query vuln "pkg:guac/spdx/ghcr.io/guacsec/vul-image-latest" --vuln-id "ghsa-7rjr-3q55-vv33" --search-depth 1 --num-path 1.
Observe the inconsistent behavior and occasional failure with the error message mentioned above.

Possible Solution
A possible solution could be to iterate over all the IDs in vulnResponse.Vulnerabilities[0].VulnerabilityIDs and pass them to QueryVulnsViaVulnNodeNeighbors instead of just using the first one. This would ensure that all available IDs are used and could potentially solve the issue.

Hey @nathannaveen so this is not a bug. That error message occurs because the osv certifier has not completed running on all the dependency packages to make them with a certifyVuln (if even they have no vulnerability). If you look in the documentation: https://docs.guac.sh/querying-via-cli/#step-3-run-the-query-vulnerability-cli this message is something that we speak about.

A possible solution could be to iterate over all the IDs in vulnResponse.Vulnerabilities[0].VulnerabilityIDs and pass them to QueryVulnsViaVulnNodeNeighbors instead of just using the first one. This would ensure that all available IDs are used and could potentially solve the issue.

Yes this should iterate over all vulnResponse.Vulnerabilities, not just the first one as a vulnerability ID may be defined with another type (for example as osv and cve). In that case, we would want to check both.

@pxp928 OK I see, thanks for the clarification!
I will leave this issue open since we should still be iterating over all vulnResponse.Vulnerabilities.


Cease catching non-HTTP errors

Description
ControllerTester catches any exceptions and wraps them into a TestResponse. If the error is a valid HTTP status code then it will set it on the response, otherwise it ignores them. This ignoring means that any regular exception (i.e. developer mistake) will return a TestResponse with 200 status and a null body - very misleading.
This PR re-throws exceptions that are non-HTTP statuses to prevent masking underlying issues.
Checklist:

[X] Securely signed commits
[X] Component(s) with PHPdocs
[X] Unit testing, with >80% coverage
n/a User guide updated
[X] Conforms to style guide

This should actually be considered an addendum to https://github.com/codeigniter4/CodeIgniter4/pull/4379, which hasn't been released yet so I think it should not break anything. Tests that error out with "invalid status code" on 4.1 would now throw the original exception instead.


[Addition]: Petite Eggshell Buffalo, Joyous Coral Pheasant, Brisk Champagne Raven, Great Golden Osprey, Restless Daffodil Perch

Hotspot b58 Addresses
11HX1G6PtVmgnnqhaPYXVTX69Jdg2CZ4icUgrwuFfaKXUQ3rfL7
117wBDSCkL61LeGrdABxqTLYggQUj6mwNjDvsKmNjieCFCNTps8
112ue8xyi9i4zJJqrLA9FdHTMDDjWHgr1eyPePXAXMMFayh29cTD
1178w3NHLSg4YmHGGUFZcFdoJ7PwxqEuNScuB5E2xfWFCpvJ5hW
113E6VAYpWLaoH5oRDWwNWjGFiGBBMZvVjeB1v54PxLWtzteT5k
Discord Handle
UQY#1605
Reason(s)
-Every hotspot in this list is sending upwards of 20 beacons a day.
-They are only beaconing and witnessing each other. Consistent 4 witnesses every single time like clockwork
-Every hotspot is attached to a separate wallet, but I think it can be assumed that they are somehow related
-Obviously because of those sent beacons, earnings are unrealistically high. Each hotspot on this list is making upwards of 2HNT a day
-Every hotspot is also a deeper connect hotspot. That by itself is obviously not sketchy, the the combination of everything else makes this suspect.
Obviously there is some gaming going on here. Adding these hotspots for review.

I notice the same in my area all points to the same miner Deeper

also the IP for these Hotspots is coming from Santa Clara CA. not china where the hex location is.


Pressing "Cmd + B"  or "Cmd + I" crashes the editor

I noticed the Flutter grey box of death in release mode when trying to toggle bold and italics in the editor.
It seems that in #167, when migrating to the Attribution classes, the document_keyboard_actions.dart file was not updated to use boldAttribution in favor of 'bold' and italicsAttribution in favor of 'italics'.
I fixed it for myself here on a separate branch as I don't have the time to make a PR with proper tests right now.
I guess we'll want to fix this before merging the marketing website to main, with proper tests?

I've verified the bug. It specifically happens when using the shortcuts to toggle the text entry mode, as opposed to toggling styles for a selection span.


merge from arlac77/npm-package-template-esm-only

package.json

chore(scripts): cover@#overwrite c8 -x 'tests/**/*' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp

.travis.yml

chore(travis): (jobs.include)
chore(travis): add 13.3.0 remove 13.2.0 (jobs.include.node_js)
chore(travis): (script)

Codecov Report

Merging #626 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #626   +/-   ##
=======================================
  Coverage   95.35%   95.35%
=======================================
  Files           9        9
  Lines         581      581
  Branches       71       71
=======================================
  Hits          554      554
  Misses         27       27

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 62b20ab...ba897d1. Read the comment docs.

:tada: This PR is included in version 8.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Unable to parse any pdf

I am facing issues while using the LlamaParse python library. My usage is as follows:
p=LlamaParse(verbose=True, api_key="xxxxxxxx",parsing_instruction='''
Try your best to parse the table contents carefully and in a proper markdown format, without any formatting errors.''',
language='en',gpt4o_mode=True,gpt4o_api_key=os.environ['OPENAI_API_KEY'],skip_diagonal_text=True)
json_objs=p.get_json_result(r"PATH_TO_PDF")
Error:
Started parsing the file under job_id xxxxxxxxx
Error while parsing the file PATH_TO_PDF: Failed to parse the file: xxxxxxxx, status: ERROR
What is the cause for this error? Is there a way to know what went wrong?

I guess it's linked to how this issue started a couple days ago:
https://github.com/run-llama/llama_parse/issues/261

This should be fixed since our latest API release.
If it happens again, please re-open this issue.


Spring boot Azure functions do not work properly when changing AzureSpringBootRequestHandler to FunctionsInvoker

I have tried the following sample, and it works correctly as is.

https://github.com/Azure-Samples/hello-spring-function-azure

Correct result.
$ curl http://localhost:7071/api/hello?name=Azure
{
  "message": "Hello, Azure!\n"
}

In this sample, AzureSpringBootRequestHandler is used, and since this class is deprecated, I rewrote it to FunctionInvoker and it does not work correctly.

public class HelloHandler extends FunctionInvoker<User, Greeting> {

    @FunctionName("hello")
    public HttpResponseMessage execute(
            @HttpTrigger(name = "request", methods = {HttpMethod.GET, HttpMethod.POST}, authLevel = AuthorizationLevel.ANONYMOUS) HttpRequestMessage<Optional<User>> request,
            ExecutionContext context) {
        User user = request.getBody()
                .filter((u -> u.getName() != null))
                .orElseGet(() -> new User(
                        request.getQueryParameters()
                                .getOrDefault("name", "world")));
        context.getLogger().info("Greeting user name: " + user.getName());

        return request
                .createResponseBuilder(HttpStatus.OK)
                .body(handleRequest(user, context))
                .header("Content-Type", "application/json")
                .build();
    }
}

Wrong result
$ curl http://localhost:7071/api/hello?name=Azure
{
  "onErrorCall": {},
  "optimizableOperator": {},
  "source": {}
}

This sample also use Mono. I thinks handleRequests method will retrun a Mono object.
@Component
public class HelloFunction implements Function<Mono<User>, Mono<Greeting>> {

    public Mono<Greeting> apply(Mono<User> mono) {
        return mono.map(user -> new Greeting("Hello, " + user.getName() + "!\n"));
    }
}

I output the log, and got [2021-04-30T09:33:06.390Z] class reactor.core.publisher.MonoPeekTerminal.
        Object result =  handleRequest(user, context);
        context.getLogger().info(result.getClass().toString());

Thanks.

Any update on this? Is it possible to use Spring WebFlux with FunctionInvoker?

Indeed there was an issue but it is fixed now and will be available with the v3.1.3 which we're planning to release tomorrow.
Also, the whole point of new FunctionInvoker is to eliminate all the code that you have above, so I also added the example - https://github.com/spring-cloud/spring-cloud-function/blob/main/spring-cloud-function-samples/function-sample-azure/src/main/java/example/ReactiveUppercaseHandler.java


Add Aniruddha-Seshu Markdown

Project Request

Proejct Request to Add [your name] markdown file and route

Field
Description

Name
Aniruddha Seshu

Email
<EMAIL_ADDRESS>

Github
Hashi-Rama-1

What do you what to contribute to:

[ ] HackFest GDSC Contributor
[ ] Hacktober Fest Contributor

Please add your github link.

Please add your github link instead of github username.


Update README.md

Fixed spelling and grammar mistakes

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


khard: remove dependency to vdirsyncer

Things done:

[x] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
[x] Built on platform(s): NixOS
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

More
cc @matthiasbeyer @domenkozar

khard and vdirsyncer can be used together, but there are no real dependency between them.

:+1: I agree on that.


Configuration - commandline arguments

Hello, I was unable to reproduce the project, It would be interesting to have a tutorial.
How are these arguments supposed to look? Thank you
# infra/ctfd/BUILD.bazel
env = {
        # FIXME: configure DATABASE_URL and SECRET_KEY here
        "SECRET_KEY": "AAAA",
        "DATABASE_URL": "mysql+pymysql://user:AAAA@localhost/ctfdb",
},

# infra/isodb/BUILD.bazel
args = [
    # FIXME: configure dbaddr here
    "mysql+pymysql://user:AAAA@localhost/ctfdb",
],

# infra/gaia/BUILD.bazel
args = [
    # FIXME: configure dbaddr here
    "mysql+pymysql://user:AAAA@localhost/ctfdb",
],

# infra/flaganizer/BUILD.bazel
args = [
    # FIXME: configure flag_key here
    "flag_key": AAAA,
],

# infra/ctfproxy/BUILD.bazel
args = [
    # FIXME: configure ssl_cert, ssl_key, mtls_ca here. See config.go for more optional configuration
    ssl_cert = /etc/letsencrypt/live/CTFProxy/cert.pem,
    ssl_key = /etc/letsencrypt/live/CTFProxy/privkey.pem,
    mtls_ca = /etc/letsencrypt/live/CTFProxy/fullchain.pem,

    # FIXME: configure cert_gcs_bucket gcp_service_account gcp_project here
    ?
],

Hi, i am also trying to use this project but having a hard time understand it, had you made any more progress on how to reproduce the project to make it running ?


Fix "commit suicide if the zk connection is dropped" test

#3528 introduces a new test in LeaderIntegrationTest called "commit suicide if the zk connection is dropped".
It succeeds only when running in isolation. We have to investigate why it's failing and fix the test or Marathon.

Note: Marathon does not suicide anymore on connection loss.

@jeschkies: Marathon suicides on abdication loss. Retested on master.

I don't see the test marked as Unstable - close this ticket.

Okay, Marathon does not suicide in NetworkPartitionIntegrationTest I will investigate that.


Created datasets by custom splitter

How can i see the datasets which i fit the model after used custom splitter like below example ?
"split_type" : TimeSeriesSplit(n_splits=5,  max_train_size=10, test_size=2, gap=1)

@tugra-alp Do you mean seeing the X_train and X_val for each fold during the hyperparameter search? Or the full training data used for the final model training?

Actually, i prefer to see X_train and X_val in each split.

Right now there is no such info exposed. You need to insert some logging statement after:
https://github.com/microsoft/FLAML/blob/2f5d6169d3b5cc025eb2516cbd003fced924a88e/flaml/ml.py#L452-L457


Blog app: add devise

Blog app: add devise
In this PR, We implemented the following features:

Removed current_user method in ApplicationController.

Install and set up devise.
  - Can register a new user.
  - User logs in with a combination of email and password.
  -  Hashed passwords are stored in the database.
  - Ask for confirmation by email.
  -  Can reset password.

Created a login and signup form based on wireframes

Oww.....Thanks @uwadonat


Bloatpilot bug in RC version

If you keep clicking on "Add most hated" in Bloatpilot, you can add the same entries several times. Using latest RC version.

should be fixed in latest release


use @astrojs/node vs. astrojs-node-aws-amplify

I took a look at the adapter and noticed an unexpected dependency: astrojs-node-aws-amplify.
Per the npm page https://www.npmjs.com/package/astrojs-node-aws-amplify and the code it looks like this package is a wildcat publish of  @astrojs/node by @alexnguyennz .
Out of curiosity is there a reason for this? Why not directly use the dependency @astrojs/node?
If there isn't a particular reason then please consider this issue to revise this package to use @astrojs/node directly.

Hi, that is a slightly modified version of the official Node.js adapter that adds some exports (that isn't included in the original adapter). Otherwise the code is essential identical.
You can check out the package.json file in the npm page you linked to see the difference - it includes the standalone.js export which is used. I did this originally so it would be clear that it was using official code more or less (instead of bundling the files directly in the adapter) but perhaps this wasn't the best idea.


[adapter-vercel] Build fails - path to bundle not being correctly outputted on Windows?

Describe the bug

run npm run build on SvelteKit project (was working fine before updating vercel-adapter)

ER: Project builds successfully
AR: The following errors:
> Using @sveltejs/adapter-vercel
 > .svelte-kit/vercel-tmp/entry.js:3:20: error: Could not resolve "..outputserver/app.js" (mark it as external to exclude it from the bundle)
    3 │ import { App } from '..\output\server/app.js';
      ╵                     ~~~~~~~~~~~~~~~~~~~~~~~~~

 > .svelte-kit/vercel-tmp/manifest.js:8:16: error: Could not resolve "..outputserver/nodes/0.js" (mark it as external to exclude it from the bundle, or add ".catch()" to handle the failure at run-time)
    8 │       () => import('..\output\server/nodes/0.js'),
      ╵                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 > .svelte-kit/vercel-tmp/manifest.js:9:16: error: Could not resolve "..outputserver/nodes/1.js" (mark it as external to exclude it from the bundle, or add ".catch()" to handle the failure at run-time)
    9 │       () => import('..\output\server/nodes/1.js'),
      ╵                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 > .svelte-kit/vercel-tmp/manifest.js:10:16: error: Could not resolve "..outputserver/nodes/4.js" (mark it as external to exclude it from the bundle, or add ".catch()" to handle the failure at run-time)
    10 │       () => import('..\output\server/nodes/4.js'),
       ╵                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 > .svelte-kit/vercel-tmp/manifest.js:11:16: error: Could not resolve "..outputserver/nodes/5.js" (mark it as external to exclude it from the bundle, or add ".catch()" to handle the failure at run-time)
    11 │       () => import('..\output\server/nodes/5.js')
       ╵                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Note the paths have forward slashes and the error path seems wrong > ..outputserver instead of ..\output\server, looks like \ is not being escaped properly perhaps? This would only show up on Windows and iirc no Svelte maintainers use Windows??
I would love to submit a PR but would need some guidance.
Reproduction
https://github.com/CobyPear/adapter-vercel-repro
clone the repo, npm i and npm run build should show the following errors in the console (on WIndows 11, will check Ubuntu if I have time):
> .svelte-kit/vercel-tmp/entry.js:3:20: error: Could not resolve "..outputserver/app.js" (mark it as external to exclude it from the bundle)
   3 │ import { App } from '..\output\server/app.js';
     ╵                     ~~~~~~~~~~~~~~~~~~~~~~~~~

> .svelte-kit/vercel-tmp/manifest.js:8:16: error: Could not resolve "..outputserver/nodes/0.js" (mark it as external to exclude it from the bundle, or add ".catch()" to handle the failure at run-time)
   8 │       () => import('..\output\server/nodes/0.js'),
     ╵                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

> .svelte-kit/vercel-tmp/manifest.js:9:16: error: Could not resolve "..outputserver/nodes/1.js" (mark it as external to exclude it from the bundle, or add ".catch()" to handle the failure at run-time)
   9 │       () => import('..\output\server/nodes/1.js'),
     ╵                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

> .svelte-kit/vercel-tmp/manifest.js:10:16: error: Could not resolve "..outputserver/nodes/2.js" (mark it as external to exclude it from the bundle, or add ".catch()" to handle the failure at run-time)
   10 │       () => import('..\output\server/nodes/2.js')
      ╵                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   ```

### Logs

_No response_

### System Info

```shell
for the reproduction project:

System:
   OS: Windows 10 10.0.22000
   CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
   Memory: 4.96 GB / 15.89 GB
 Binaries:
   Node: 16.8.0 - C:\Program Files\nodejs\node.EXE
   Yarn: 1.22.17 - C:\Program Files\nodejs\yarn.CMD
   npm: 7.21.0 - C:\Program Files\nodejs\npm.CMD
 Browsers:
   Chrome: 96.0.4664.110
   Edge: Spartan (44.22000.120.0), Chromium (96.0.1054.62)
   Internet Explorer: 11.0.22000.120
 npmPackages:
   @sveltejs/adapter-auto: next => 1.0.0-next.7
   @sveltejs/adapter-vercel: next => 1.0.0-next.34
   @sveltejs/kit: next => 1.0.0-next.211
   svelte: ^3.44.0 => 3.44.3

Not sure how accurate that is. I'm on Windows 11

Severity
blocking an upgrade
Additional Information
Not sure how to work around this at the moment, any help is much appreciated :)

As expected this works fine on Ubuntu. Something to do with path.relative in the new builder API is not friendly to windows.

Is this resolved by the linked PR?

It should be resolved in the latest version (1.0.0-next.35)

So I deployed my svelte-kit project to vercel and got this exact same error. It builds fine on my windows pc

same error on vercel, builds fine on manjaro.

Same error

same error on vercel. I am using a mac.

same error here.
using a mac.

same error here. using a mac.

update: I just run "npm update" and works fine

Yup updating npm worked for me. Thanks @gpaiva985 !


libcxxmini: Add missing runtime related classes.

Summary
reference:https://github.com/libcxxrt/libcxxrt/tree/master/src
Impact
libcxxmini
Testing
ci test

[Experimental Bot, please feedback here]
No, this PR does not fully meet the NuttX requirements. While it provides a reference and mentions impact on libcxxmini, it lacks crucial details.  Here's a breakdown of what's missing:

Summary:  The summary is insufficient. It needs to explain why the libcxxmini change is necessary (bug fix, new feature, update, etc.), what part of the code is changed functionally, and how the change works. Simply referencing the source code doesn't explain the changes.
Impact:  While "libcxxmini" is mentioned, there's no explanation of the specific impact.  All the "NO / YES" questions need to be answered explicitly.  If any answer is "YES," a description of the impact is required. For example, if the build process changes, how does it change?  If documentation updates are needed, were they provided?
Testing: "ci test" is not enough.  The PR needs to specify the build host operating system, CPU architecture, compiler, and version. It also needs target architecture, board, and configuration.  Most importantly, it needs to provide actual testing logs before and after the change, demonstrating that the change works as intended.  Just saying "ci test" doesn't prove anything without the logs themselves.

In short, the PR needs significantly more detail to meet the NuttX requirements.  It needs to clearly articulate the "why," "what," and "how" of the change, its full impact, and provide concrete evidence of testing.


[FEATURE REQ] Release SCA 6.0.0-beta.4

Context
If Spring Boot releases the RC2 and Spring Cloud 2022.0.0-RC2, upgrade to the latest RC version for Spring Cloud Azure 6.0.0-beta4.
Goal
Release Spring Cloud Azure 6.0.0-beta.4.

closing to avoid meaningless issue

Updated to the major version 5, see more from Spring Cloud Azure 5.0 Release.


Remove hip landmarks from [annotations, calculations]

Goals
Simplify code by removing unnecessary calculations
Tasks

[ ] Verify hip landmarks aren't being used in detecting good bad posture
[ ] Verify removing hip landmarks won't break anything

Hip landmarks are still important for current posture calculation, and will be further useful when is_standing() is used in later iterations


Fix link to bundle contract doc

Changes
Fix link and add a link from the pipelinerun docs since the taskrun docs link to it.
/kind documentation
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[n/a] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
NONE

/lgtm


fix: Add dependencies on symbol imports

Issue #
When trying to build the client under the smithy projections, it would fail due to a misconfigured package manifest.
Description of changes
Add dependencies on symbol imports, and also:

Add CI step to build test projections
Add test projection with useInterceptors

Scope

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

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

Converting to draft, for some reason this makes codegen unstable.


Future plans

Hey @greglook great set of libraries you have implemented so far. Any plans to go further with the development ? Anything I can help with ?
Cheers,
Bahadir

Hi @bcambel - I haven't had a chance to work on these in a bit, but the idea is very much alive! A lot of my recent efforts were in the merkledag-server and merkledag-browser repos - getting a repository set up that is easy to interact with from the command line as well as the browser is an important next step.