propose logo

Hello @mekhovov @tmptrash  i am a graphic designer. I would like to know if you would be interested in me making a logo for this project. If you would have me, i would make a logo for you, and it's free.

Hi :)
Just interesting, why do you choose our project? Can you show us your
works?
In general, is a good idea ;)
сб, 23 июн. 2018 г., 04:08 dee-y<EMAIL_ADDRESS>
Hello @mekhovov https://github.com/mekhovov @tmptrash
https://github.com/tmptrash i am a graphic designer. I would like to
know if you would be interested in me making a logo for this project. If
you would have me, i would make a logo for you, and it's free.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tmptrash/construct/issues/146, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABFvERNGGQcLcabiIphMLp3JElgN-Sc5ks5t_ZUqgaJpZM4U0lQp
.

Hello @tmptrash, lolz i love contributing to open source projects especially ones without a logo. Here are a few designs i have made for other projects...

Okay, let's start this process ;) Do you need more information about our
project?
Here is unafficial logo, we have used before:
https://goo.gl/images/g4k5iM (only it's) central part
Maybe we may give each other our real emails  ;) Here is mine:
<EMAIL_ADDRESS>пн, 25 июн. 2018 г., 23:16 dee-y<EMAIL_ADDRESS>
Hello @tmptrash https://github.com/tmptrash, lolz i love contributing
to open source projects especially ones without a logo. Here are a few
designs i have made for other projects...
[image: logotype]
https://user-images.githubusercontent.com/36637989/41873358-a88dfcc6-78bc-11e8-9836-512013f53a38.png
[image: logo10]
https://user-images.githubusercontent.com/36637989/41873382-bea98d86-78bc-11e8-9a77-eff2fe087024.png
[image: tf logotype 1]
https://user-images.githubusercontent.com/36637989/41873481-fd7d2f7c-78bc-11e8-8c6f-50e00148b79b.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tmptrash/construct/issues/146#issuecomment-400081158,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABFvEQtx7SNssqJm5J6UwZI4s1K36f8Oks5uAUUTgaJpZM4U0lQp
.

Owk will have something for you soon, here is my email<EMAIL_ADDRESS>


Can I use 3.5mm jack earphone or Speakers as output device(Board: PI3)

Hi guys,
USE_VOICEHAT_I2S_DAC has been set false.
I tried to use USB audio card, everything is OK.
Now I'm trying to use a USB microphone to record voice and use 3.5mm cable on PI3 to output.
System can record voice and do recognition but there is no output on 3.5mm cable.
When I tried to use findAudioDevice to get output device, return value is always null.
Thanks
o.O

Solution:
If you are not using voice hat, change line 58 to :
private static final boolean USE_VOICEHAT_I2S_DAC = false;
Then below line 98 and 99 :
AudioDeviceInfo audioInputDevice = null;
AudioDeviceInfo audioOutputDevice = null;

Set audioInputDevice as your device, in my case, I use a usb mic, so it will be:
audioInputDevice = findAudioDevice(AudioManager.GET_DEVICES_INPUTS, AudioDeviceInfo.TYPE_USB_DEVICE);
Also set audioOutputDevice:
audioOutputDevice = findAudioDevice(AudioManager.GET_DEVICES_OUTPUTS, AudioDeviceInfo.TYPE_BUILTIN_SPEAKER);//for 3.5mm
And done.


[Bug]: Cannot build puppetter-core using @vercel/ncc since version 18.2.0

Bug description
Steps to reproduce the problem:

npm install<EMAIL_ADDRESS>create any puppeteer-core script
ncc build -m example.js -o dist

It works fine @18.1.0 and error show since 18.2.0
since 18.2.0 shown this error
Error: Cannot find package directory
at getPackageDirectory (D:\code\node\puppeteer-new\dist\index.js:3:424814)
at Object.3666 (D:\code\node\puppeteer-new\dist\index.js:3:425761)
at nccwpck_require (D:\code\node\puppeteer-new\dist\index.js:3:688282)
at D:\code\node\puppeteer-new\dist\index.js:3:688525
at D:\code\node\puppeteer-new\dist\index.js:3:688929
at Object. (D:\code\node\puppeteer-new\dist\index.js:3:688968)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
Puppeteer version
18.2.0
Node.js version
12.22.9
npm version
6.14.15
What operating system are you seeing the problem on?
Windows
Configuration file
No response
Relevant log output
No response

Node 12 is not supported anymore. Please try using Node 14+ and latest NPM. Also, if you are running Puppeteer in a different environment, make sure to have the installation folder configured https://pptr.dev/guides/configuration#examples

I tried update to node 18.12.1 and use latest puppeteer and it works.
Thank You


Skeleton of a tracer for AWS X-Ray

Signed-off-by: Marco Magdy<EMAIL_ADDRESS>Description:
A skeleton tracer to incrementally add support for AWS X-Ray
Risk Level: Low
Testing: unit tests for functionality in util - the rest of files have no business logic to test yet
Docs Changes: N/A
Release Notes: N/A

I've changed the file_name to be a DataSource

/test

macos build seems to be stuck.
/retest

/azp run

Is there anything I have to do to get this PR merged?
Also, should I squash the commits? or is the person merging this PR expected to do the squashing?

/azp run envoy-macos


refactoring of retry/retryOption

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

Codecov Report
Attention: 26 lines in your changes are missing coverage. Please review.

Comparison is base (a9598a0) 66.96% compared to head (09947e9) 39.11%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #850       +/-   ##
===========================================
- Coverage   66.96%   39.11%   -27.86%
===========================================
  Files         250      192       -58
  Lines       23647    20132     -3515
===========================================
- Hits        15836     7875     -7961
- Misses       6997    11911     +4914
+ Partials      814      346      -468

Flag
Coverage Δ

?

go-1.17.x
39.11% <21.21%> (-26.42%)
:arrow_down:

go-1.20.x
?

go-1.21.x
?

integration
?

macOS
39.11% <21.21%> (-0.18%)
:arrow_down:

ubuntu
?

unit
39.11% <21.21%> (-0.28%)
:arrow_down:

windows
?

ydb-22.5
?

ydb-23.1
?

ydb-23.2
?

ydb-23.3
?

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

Files
Coverage Δ

retry/retry.go
55.30% <21.21%> (-35.47%)
:arrow_down:

... and 191 files with indirect coverage changes

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


Small notebook fixes

Minor fixes/improvements to existing notebooks.

One thing I was meaning to do was to add some info about hv.help to the element notebooks. I am happy to do that in this PR once you are done with your fixes.

I'm done for now, so go ahead.

I'll do that now but because I will need to touch all the element notebooks I want to decide on the message now because I won't want to change it later.

Should the message be at the start or the end of the element notebooks? I am leaning towards the end.
Should the message be generic so it can copy/pasted or should it mention the element name? Latter is nicer but more effort (so I guess I'll do that?).

Assuming it is something I append to the element notebooks maybe something like this, e.g for Curve:
To get additional help as well as a list of available style and plot options, use hv.help(hv.Curve).
Is that any good and do you think that would assist people?

I think at the end is easier to ignore once people get it, and it isn't the first thing they will want to do even if it's new.  I'd vote for:

For full documentation and the available style and plot options, use hv.help(hv.Curve).

It would be nice if the output of hv.help(hv.Curve) could be linked to the text hv.help(hv.Curve), but that maybe too much work for today?

It would be nice if the output of hv.help(hv.Curve) could be linked to the text hv.help(hv.Curve), but that maybe too much work for today?

Not today, but I'll use the format you suggested, thanks!

It was pretty tedious going but all the element notebooks are now updated with a pointer to ```hv.help`` at the end.
Happy to see this PR merged if @philippjfr agrees it is ready.

Thanks, looks good but tedious indeed. Will merge now.


--embed-thumbnail

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2019.02.18. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2019.02.18

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[x] Feature request (request for a new functionality)
[ ] Question
[ ] Other

there should be a flag to enable crop-out of the thumbnail.
i hate having non-square album covers in my music library. it looks terrible.
a lot of music on youtube just has the round vinyl sticker or the album artwork as video and the thumbnail. so cropping those thumbnails would only be of benefit.

Made a fix myself by using --exec and imagemagick
cropThumbnail.sh:
#!/bin/bash
file="$1"
convert "${file%.*}.webp" -gravity center -extent 1:1 "${file%.*}.webp"

then append --exec "before_dl:sh ./cropThumbnail.sh"
but yes, having this already inside youtubet-dl would be much easier


Polygon edge documentation is down

[ Documentation ]
Description
Polygon edge documentation is down since the release of v0.8 (supernets).
Steps to reproduce

Go to https://wiki.polygon.technology/docs/edge/
You can see a "Page Not Found" error message, this happens with any page of the polygon edge documentation, even tho you can still search for stuff from that documentation and find results, but when you click on it, you get the "page not found" message.

Can you reopen the archived page so we can back it up as we are currently running on v0.6.3?

Hi @lucaspan, thanks for raising this.
The source of the archived edge docs are still available in the repo, here. We had decided to put them in archive mode and not continue hosting them on the Polygon Wiki. Here is an example of a notice on the new Supernet docs:

Before diving into the documentation, please keep the following points in mind:
Polygon Supernets were officially introduced in v0.7.x of the Polygon Edge client.
The Polygon team will prioritize the latest version of the Edge client and as a result, will no longer provide support for older versions (v0.6.2 and earlier).
The repository will remain accessible, and users may fork it and use it as they wish, subject to applicable open-source license terms. It is highly recommended to upgrade to the latest version, which includes the most up-to-date features and fixes. However, users who prefer to stay on older versions may continue to do so.
Polygon Edge serves as a consensus client implementation for Polygon Supernets, much like how Geth serves as a client implementation for Ethereum.
Both geth and Edge serve as intermediaries between nodes and their respective blockchains, allowing users to interact with the network and take advantage of its benefits. To draw an analogy, Geth and Edge are to Ethereum and Supernets what web browsers are to the internet, enabling users to access and interact with the network.

The intent was to redirect the old endpoints to the new Supernet docs, which we can fix, or what I think would be better is to redirect them to the actual source of the archived edge docs on GitHub.