🐛 [BUGFIX]: Fix glitch when resizing window on Market + big space on clearable element in Search in Market

…c

✅ Checklist

[ ] npx changeset was attached.
[ ] Covered by automatic tests.
[ ] Impact of the changes:

...

📝 Description
Fix glitch when resizing window on Market + big space on clearable element in Search in Market

https://github.com/LedgerHQ/ledger-live/assets/112866305/94491f6a-d2d8-4b86-92a7-e9dcad01dadb
❓ Context

JIRA or GitHub link: LIVE-12816

🧐 Checklist for the PR Reviewers

The code aligns with the requirements described in the linked JIRA or GitHub issue.
The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
There are no undocumented trade-offs, technical debt, or maintainability issues.
The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
Any new dependencies have been justified and documented.
Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

/generate-screenshots


Microcode internal changes: havocs, new framing, and push through

This PRQ does three big things:

Amends the definition of Assign in Microcode to allow assignment to nothing.  This represents a havoc and implements #104.
Rewrites the command framer to work on Microcode instead of BoolExpr, implementing #112.
Adds Microcode to CommandSemantics, freeing it up for use in backends directly instead of relying on the low-level Boolean semantics or high-level PrimCommand representation.

Most changes are internal for now.

Going to push this one through as well since we have a massive backlog.


Fix #26326: az network vnet subnet update: --nat-gateway null doesn't work

Related command

Fix: https://github.com/Azure/azure-cli/issues/26326
Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.

/azp run


Issue#67: fixing custom paritioner issue

Hello, @abhijith-prabhakar !
Thank you very much for the contribution!
I'll take a look to your fix soon.
Although here are some comments for the future already:

PR against top level branch, not master. It would be easy for me to review and for you to accept new changes from the upstream.
Make commit messages (at least first) more informative and with the Git formatting rules.

All those rules and recommendations are presented in the Contribution Guide Line I've shown you before.
It isn't critical right now, but may safe our and your time in the future. At least I won't need to write similar comments and you won't read them :smile:

Merged with https://github.com/spring-projects/spring-integration-kafka/commit/4786b64f51443ff788e8985fbbf12857cf435378
Thanks @abhijith-prabhakar for the contribution


feat(wildcards)

I haven't tested this yet.  Literally, inspired, created the code real quick
Thoughts @asbjornhaland @brandoncc

@ThePrimeagen  How would this be used? I don't have any wildcard use experience in lua, so reading the code didn't help me understand the problem it solves or how to use it :-/


fix: workaround for this https://github.com/rust-lang/docs.rs/issues/1823

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

v1.0.10
GitHub release

Your semantic-release bot :package::rocket:


Validate Ticket after a long time

Am I missing something ? Once the user is authenticated it doesn't look like the ticket is ever validated again to check if the ticket/cookie is still valid (user is never prompted to login again, until the session cookie is deleted from the browser or browser is closed), unless I am not seeing something.

So the code can never react to back-end changes.
So after the user is logged in and then the user is suspended/password changed/or hacked - the user will be able to continue using the site.
https://docs.microsoft.com/en-us/aspnet/core/security/authentication/cookie?tabs=aspnetcore2x#reacting-to-back-end-changes
We cannot validate CAS ticket as its one time ( any ideas on how to check or validate on every request) or how to solve the CAS Auth Middleware to react to back-end changes

I believe adding support for the 'renew' option is what is needed.
From the docs:

if this parameter is set, single sign-on will be bypassed. In this case, CAS will require the client to present credentials regardless of the existence of a single sign-on session with CAS.

Your application will still need to implement some kind of custom ValidatePrincipal for you to invalidate the client application cookie.  If the renew option was specified as true, the user would be prompted again by CAS after you invalidate their cookie, even in the same browser session.
Would this work?

The Renew and Gateway options were implemented in the 2.0.2 release.


Merge UntradeableItemMapping and ItemMapping

This enum never really made sense when we already have ItemMapping and
its just confusing people.
Signed-off-by: Tomas Slusny<EMAIL_ADDRESS>

Needs rebase after Items Kept on Death plugin has been removed.


duplicate error throws invalid flags messages

Can you please elaborate?

it's not grammar validation duplicates.
its lexer duplicate patterns detection.
On Mon, Jun 22, 2015 at 10:46 AM, firasnajjar<EMAIL_ADDRESS>wrote:

Can you please elaborate?
—
Reply to this email directly or view it on GitHub
https://github.com/SAP/chevrotain/issues/80#issuecomment-114030076.


Figure out when we should consider a data stream closed in h2quic

For the streams used in e.g. GET requests, it looks like Chrome does not send a close. Is this a bug, are we missing something, or should we consider the stream auto-closed?
We are currently leaking streams because of this.

Duplicate of #109, forgot we had this issue already.


update roslyn to 3.1.0-beta1-19080-04

This is the latest inserted version of Roslyn.

Would be great if we could get up to date with the latest Roslyn version. What needs to happen so we can make it so?


[WFLY-13650] Allow expressions for ordinal attribute

JIRA: https://issues.redhat.com/browse/WFLY-13650
Signed-off-by: Jeff Mesnil<EMAIL_ADDRESS>

@jmesnil @bstansberry Should this not have a model version bump?

This also needs a model transformer to reject expressions for legacy hosts.

@kabir @pferraro you are both right, I'll update the PR to minor bump the management model and add a transformer for it.


close/minimise/maximise/hide buttons in Notion Enhancer

describe the bug
close/minimize/maximize/hide buttons have disappeared completely.
expected behavior
It's simple - Buttons must be on the screen.
screenshots

platform
Windows 10

This is definitely a known issue that I believe was fixed? I can normally get them back if I go to a different page and then relaunch from the tray icon (for some reason it only works on certain pages for me, and sometimes you need to relaunch a couple of times)

This is definitely a known issue that I believe was fixed? I can normally get them back if I go to a different page and then relaunch from the tray icon (for some reason it only works on certain pages for me, and sometimes you need to relaunch a couple of times)

Hello, first of all, I got to say I absolutely love this project. However, I'm having this issue as well. Sometimes the buttons show up, but sometimes I would have to restart the program multiple times. The problem seems to be getting more intense by the day. I'm not sure if a clean uninstall/install would do the trick, but if there's a way to fix this issue, I'd rather go that route. Cheers!

Hello, first of all, I got to say I absolutely love this project. However, I'm having this issue as well. Sometimes the buttons show up, but sometimes I would have to restart the program multiple times. The problem seems to be getting more intense by the day. I'm not sure if a clean uninstall/install would do the trick, but if there's a way to fix this issue, I'd rather go that route. Cheers!

hm, I thought this was fixed.
can you check the console when this happens and tell me of any errors in there? (ctrl+shift+i)

hm, I thought this was fixed.
can you check the console when this happens and tell me of any errors in there? (ctrl+shift+i)

The problem comes from core/css/buttons.css on line 127
The operation cannot be performed because the property "appendChild" is NULL.

The problem comes from core/css/buttons.css on line 127
The operation cannot be performed because the property "appendChild" is NULL.

@dragonwocky Here's the console errors you asked for. I don't know which one of these is the one causing the problem, but hopefully, this is what you are asking for.
www.notion.so-1609783109827.log

@dragonwocky Here's the console errors you asked for. I don't know which one of these is the one causing the problem, but hopefully, this is what you are asking for.
www.notion.so-1609783109827.log

Hey, just a little update. The issue resolves itself after a quick refresh (ctrl+r). However, the issue still exists upon initial opening sometimes.

Hey, just a little update. The issue resolves itself after a quick refresh (ctrl+r). However, the issue still exists upon initial opening sometimes.

try replacing line 108 in mods/core/client.js with !document.querySelector('.notion-topbar > div[style*="display: flex"]').

try replacing line 108 in mods/core/client.js with !document.querySelector('.notion-topbar > div[style*="display: flex"]').

Haven't had issues for 2 days. Looks like that sprinkle of magical dust fixed it. Thanks! @dragonwocky

Haven't had issues for 2 days. Looks like that sprinkle of magical dust fixed it. Thanks! @dragonwocky

been struggling with the same issue for a month, please kindly help solve this

 been struggling with the same issue for a month, please kindly help solve this

@dragonwocky

@ijahehehehe please don't bump closed issues, this was an old issue from a previous version of notion and the notion-enhancer that has since been resolved. If you are having problems with the current version of the notion-enhancer please create a new issue with information about what's going on.


Override copy and deepcopy on LazyUUIDTask

Fixes #41

Fairly small change to fix this bug! Since we do a deepcopy of all the task's data attributes after loading from JSON, and a recurring task has a parent, we were trying to copy a LazyUUIDTask. That meant we tried to load it in via replace(), and caused an infinite loop.
Since they're lazy by definition, the copy is implemented as just a new object with the same UUID.
Still needs a suitable test!

Thanks for looking into this, looks good!
I wonder, should we also override these methods for LazyUUIDTaskSet?

I don't think so, since child attributes are descended into and the __copy__ method is called, we get that for free anyway :)
Just added a test which actually does fail without this fix, so I'll be happy if everything passes!


sync to live

Docs Build status updates of commit d78f878:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/GetStarted.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

windows-iotcore/secure-your-device/BuildingSecureDevices.md
:white_check_mark:Succeeded

windows-iotcore/secure-your-device/Windows IoT Security.docx
:white_check_mark:Succeeded

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


fix(release): manually install yq

@mason-org/triage
 🤖 This is an automated comment.    📖 Source code


Private Endpoint Config DEPRECATED

In the documentation, it says that private_endpoint_config is DEPRECATED.
Is there any other possible way to fetch private_dns_hostname?
I've tried to fetch the entire service output but it doesn't seem to appear in any other place than that.
Is it planned to move to endpoints output?
│ Warning: Deprecated attribute
│
│   on .terraform/modules/site/modules/clickhouse/main.tf line 128, in resource "aws_secretsmanager_secret_version" "clickhouse_endpoint_secret_version":
│  128:   secret_string = clickhouse_service.aternity.private_endpoint_config.private_dns_hostname
│
│ The attribute "private_endpoint_config" is deprecated. Refer to the provider documentation for details.

hi @yardenws
thanks for reaching out.
You are right, currently there is no alternative way of getting the DNS hostname but using the deprecated field.
We are indeed working on exposing the DNS hostname field through the clickhouse_private_endpoint_config data source, but unfortunately I don't have an ETA to communicate at this stage.
I will keep this ticket open, and get back to you when I'll have news.


improve performance

tf.math.add_n is created before loop. The operator avoids building the node repeatedly.

For this issue https://github.com/captain-pool/GSOC/issues/68

You are right,  I missed that intermediates is growing. I will close this issue


Wallet Address Not Auto-Filling After Connection

Hi Folks,
I'm reaching out for a bit of help with an issue I've encountered while integrating the Solana wallet adapter into our React application, specifically with Phantom wallet connectivity.
Issue Description:
After successfully connecting the Phantom wallet, we anticipate the user's public wallet address to automatically populate a designated input field within our application. Unfortunately, this doesn't seem to be happening, and I'm a bit puzzled as to why.
Steps to Reproduce:
Visit our application. --> React App
Initiate the wallet connection by selecting the "Connect Wallet" button.
Choose the Phantom Wallet from the options and authenticate the connection.
Expected Outcome:
Post connection, the "Wallet Address" input field should reflect the user's public wallet address, showcasing a seamless integration.
Strangely, if you connect the wallet and refresh the page, it works as it should, but if you do not refresh the page, the problem persists.

Actual Outcome:
Despite a successful connection, the "Wallet Address" field remains unfilled.

You can access the entire code from the link below.
React Code

Technical Details:

React version: [18.2.0]
@solana/wallet-adapter-react version: [0.15.35]
Browser(s): [Chrome, Firefox]
Wallet Used: Phantom

Request:
I would immensely appreciate any guidance, updates, or suggestions for workarounds you might have to ensure the wallet address populates as expected.
Thank you very much for your time in advance.

In your example code you are calling the useWallet() hook outside of your WalletProvider's context. This won't work.

You are also passing wallets={[new PhantomWalletAdapter()]} to the WalletProvider. Since this will occur on every render, you'll get a new array and a new Phantom adapter. This will also not work. I would recommend looking at the example or other starter projects in the repo, or use https://github.com/solana-labs/dapp-scaffold


Input and process commands in message output area

Addresses #734

Thank you for the patch. I've tested this and while the behavior is different, somewhat better, it is not fully correct yet:
Try this test:

copy-paste the command below to the console (it prints a message on the console after 5 seconds)

def delayedprint():
  print "something printed"

qt.QTimer.singleShot(5000, delayedprint)

immediately enter "print" (without quotes, do not press Enter)
wait for the "something printed" message to appear, enter "12345" (without quotes) to complete the command, and press Enter

Current result is this:

There are two problems:

Text "12345" that I typed appear in green, while it is a user input, so it should appear blue
It should have printed "12345", in a new line; but it only printed "5" in the same line (right after 12345)

Closing. I think this was fixed by https://github.com/auneri/CTK/commit/b66882dd489bf6bcfd01aa5f70c4075c3fcae11c#diff-1c7b384dd39badd29a517054e7b7e0ac
If there is problem with the interactor, consider submitting a new issue or pull request


/usr/ports/graphics/php7-gd in BUILD_DEPENDS

===>   Returning to build of php7-extensions-1.0
===>   php7-extensions-1.0 depends on file: /usr/local/lib/php/20151012/pdf.so - not found
===>  License PHP30 accepted by the user
===>   pecl-pdflib-3.0.4 depends on file: /usr/local/sbin/pkg - found
=> pdflib-3.0.4.tgz doesn't seem to exist in /usr/ports/distfiles/PECL.
=> Attempting to fetch http://pecl.php.net/get/pdflib-3.0.4.tgz
pdflib-3.0.4.tgz                              100% of   26 kB  212 kBps 00m00s
===> Fetching all distfiles required by pecl-pdflib-3.0.4 for building
===>  Extracting for pecl-pdflib-3.0.4
=> SHA256 Checksum OK for PECL/pdflib-3.0.4.tgz.
===>  Patching for pecl-pdflib-3.0.4
===>   pecl-pdflib-3.0.4 depends on file: /usr/local/include/php/main/php.h - found
===>   pecl-pdflib-3.0.4 depends on file: /usr/local/bin/phpize - found
===>   pecl-pdflib-3.0.4 depends on file: /usr/local/lib/php/20151012/gd.so - not found
Error a dependency refers to a non existing origin: /usr/ports/graphics/php7-gd in BUILD_DEPENDS
===>   pecl-pdflib-3.0.4 depends on file: /usr/local/bin/autoconf-2.69 - found

PHP 7 was added to ports tree.
See http://www.freshports.org/lang/php70/


powi/powf simplexpr functions

Description
Yep, powi/powf, why not
Resolves https://github.com/elkowar/eww/issues/1226
Usage
In the showcase
Showcase

Additional Notes
Sooo, it's two separate expressions. They can be reduced down to a single one, that acts like powf. I just though it sometimes miiight be useful to have two of them. Just shrink it down to one expression if that's more appropriate
Checklist

[x] All widgets I've added are correctly documented.
[ ] I added my changes to CHANGELOG.md, if appropriate.
[x] The documentation in the docs/content/main directory has been adjusted to reflect my changes.
[x] I used cargo fmt to automatically format all code before committing

consider adding this to the grammar using operators as described in #1226

I kinda like it more in the form of a function. I mean, if it's more appropriate to implement it the other way, I would. Although, I would prefer for it to be this way

This seems fine to me, an operator would also work but I don't really see a massive benefit either way. I'll merge this! Thanks for your contribution!


Remove package-lock.json

It seems like this was added by mistake in https://github.com/facebook/create-react-app/pull/11188.

Thanks!


distance.nearest_nodes returning wrong distant nodes

Hi.
I'm trying to use the 'new' distance.nearest_nodes function, but it returns a node which is 12 km from the coordinates I put in, which is around the university of Magdeburg. When I use the old deprecated function get_nearest_node the resulting node is accurate. So, because the node is "just" 12 km off I thought it could have something to do with projection issues?
I found a similar problem in issue#71, but it is in regard to the old function (https://github.com/gboeing/osmnx/issues/71).
But I'm not sure where to look. I didn't find any examples of this new function being used. Is there something I'm missing?
I'm using OSMnx 1.1.1 in Python 3.9
Here is an example:
import osmnx as ox

H = ox.graph_from_place('Magdeburg, Germany', network_type='drive')

# use new function/not working
orig1 = ox.distance.nearest_nodes(H, 52.13891631423865, 11.646996097973076)

#use old deprecated function/working
orig2 = ox.get_nearest_node(H,(52.13891631423865, 11.646996097973076))

print("orig1",orig1)
print("orig2",orig2)

#%%

H.nodes[orig1]['y']
#%%
H.nodes[orig1]['x']

#%%

H.nodes[orig2]['y']
#%%
H.nodes[orig2]['x']

See the distance.nearest_nodes function documentation. The coordinate arguments should be in the order x, y but you are passing them in the order y, x.


Refactoring: move window files to under the window directory

I have moved the code files for the native window under surface directory to under window directory.

@Mai-Matsuura Please review this PR.

@HidenoriMatsubayashi I've checked the changes and it looks fine.


spark-core and spark-sql should be provided dependencies

Since you do not want to bundle spark with your software, at least not in most of use cases (when people run their application with spark-submit)

Hi,
If I'm right, you want Spark to be include in the dependencies of this provider. In that case, we don't think we should bundle spark with this provider. It's not a common practice


pip command for 3.6.8 not working

I tried using pip install chamberconnectlibrary-3.6.8 and got this message:
ERROR: Could not find a version that satisfies the requirement chamberconnectlibrary-3.6.8 (from versions: none)
ERROR: No matching distribution found for chamberconnectlibrary-3.6.8
I'm using python 3.9.4 and pip 22.3.1
Does anyone know if there's a problem?

It looks like the python3 version has not been pushed to pypi. Until that happens you may use (as long as you also have git installed):
pip install git+https://github.com/EspecNorthAmerica/ChamberConnectLibrary.git@py3-chamberconnectlibrary
or
pip3 install git+https://github.com/EspecNorthAmerica/ChamberConnectLibrary.git@py3-chamberconnectlibrary

It looks like the python3 version has not been pushed to pypi. Until that happens you may use (as long as you also have git installed):
pip install git+https://github.com/EspecNorthAmerica/ChamberConnectLibrary.git@py3-chamberconnectlibrary
or
pip3 install git+https://github.com/EspecNorthAmerica/ChamberConnectLibrary.git@py3-chamberconnectlibrary

Thank you very much, it worked properly.

Any Python3 version on or above 3.6.8 will work with the chamberconnectlibrary-3.6.8, but it PYPI has not been completely pushed. In the meantime, you may still use it; simply pull and use it directly in the directory. The complete PYPI will be pushed soon.

I tried using pip install chamberconnectlibrary-3.6.8 and got this message:
ERROR: Could not find a version that satisfies the requirement chamberconnectlibrary-3.6.8 (from versions: none) ERROR: No matching distribution found for chamberconnectlibrary-3.6.8
I'm using python 3.9.4 and pip 22.3.1
Does anyone know if there's a problem?

Any Python3 version on or above 3.6.8 will work with the chamberconnectlibrary-3.6.8, but it PYPI has not been completely pushed. In the meantime, you may still use it; simply pull and use it directly in the directory. The complete PYPI will be pushed soon.


ConnectionDriver does not resolve for the close() caller

After the changes this bug https://github.com/djc/quinn/issues/283#issuecomment-478995185 where the connection-driver only exited much later with timeout error seems now partially solved partially transpiring into another buggy behaviour.
So peer-A connects to peer-B. If peer-B calls Connection::close() the peer-A's driver resolves with error along the lines of connection-closed-by-peer - which is reasonable. peer-B's IncomingStreams and other children streams from it all exit with error about the connection closure as well. However peer-B's connection driver never resolves. Not even after some timeout etc., which it used to resolve previously after.
Similarly if peer-A called Connection::close() 1st everything at peer-B's end - IncomingStreams and children streams from it, the connection-driver - all resolve. I even called peer-B's Connection::close() at this point to ensure it doesn't cause a panic or something since everything else for it had exited and it doesn't (and it shouldn't so OK). However peer-A's connection driver never resolves.
So it seems the peer who calls the close() resolves everything for the remote while its own driver remains unresolved.

btw a side question was it necessary to consume self in Connection::close() ? I now have to do conn.clone().close() in code now if it's a part of bigger object where i want to run closures in dtor (since i cannot move stuff out in dtors and close() consumes self). I mean it's clone-able and all clones refer to the same underlying connection so other clones can still call clone and panic and the semantics don't really save anyone from anything - just make it unergonomic to work with.
See std's TcpStream for instance. That too has try_clone() giving a reference to the same underlying stream and they don't really consume self by ref in say shutdown. You can still call further shutdowns on the same handle or the clones and you will get error or otherwise depending on the platform. For us we can always return error in case of quinn since the behaviour is not platform dependent. Or you could panic (which i think what the document says) though i would usually prefer a result but am OK with whatever is decided.
However to me it appears to make it a bit unergonomic (and also different in design than what ppl might be used to coming from a std socket API

Ok this https://github.com/djc/quinn/issues/288#issue-428778633 was just noise. It turned out i was logging only the map_err() on the driver and now logging map() path too i can see both peers resolve their respective drivers no matter who calls close() - the caller gracefully and the remote with error that peer closed the connection.
I'm just going to raise this https://github.com/djc/quinn/issues/288#issuecomment-479502301 as a separate issue but that's not a bug so not critical.
Closing this.


In repl, allow reifying more concisely than repeating the entire instruction

i.e., it might figure out that what you typed reifies some part of the entire instruction, and just keep the rest intact.


BUG: Download from 'vivo.sx' no longer works (since a couple of weeks)

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 that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2<IP_ADDRESS>. 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 2<IP_ADDRESS>

Before submitting an issue make sure you have:

[ x] At least skimmed through README and most notably FAQ and BUGS sections
[ x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

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

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

This is a BUG-report.
Downloads from the site 'vivo.sx' no longer work (for me?). The protocol output follows:
$ ./youtube-dl --verbose http://vivo.sx/bfb7f37eff
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'http://vivo.sx/bfb7f37eff']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.12 - Linux-4.6.0-1-amd64-x86_64-with-debian-stretch-sid
[debug] exe versions: avconv 11.3-6, avprobe 3.1.1-2, ffmpeg 3.1.1-2, ffprobe 3.1.1-2, rtmpdump 2.4
[debug] Proxy map: {}
[Shared] bfb7f37eff: Downloading webpage
[Shared] bfb7f37eff: Downloading video page
ERROR: Unable to extract video URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "./youtube-dl/youtube_dl/YoutubeDL.py", line 682, in extract_info
    ie_result = ie.extract(url)
  File "./youtube-dl/youtube_dl/extractor/common.py", line 347, in extract
    return self._real_extract(url)
  File "./youtube-dl/youtube_dl/extractor/shared.py", line 55, in _real_extract
    r'data-url="([^"]+)"', video_page, 'video URL')
  File "./youtube-dl/youtube_dl/extractor/common.py", line 659, in _html_search_regex
    res = self._search_regex(pattern, string, name, default, fatal, flags, group)
  File "./youtube-dl/youtube_dl/extractor/common.py", line 650, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract video URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
<end of log>

When i perform each step manually (using 'wget'), the "download" still works, meaning: When issuing a POST-request with the form-data from the just downloaded web-page, i get the "downlad" page, which no longer contains the hidden form, but the URL of the video.
The problem is independent of the video-id, that is regardless of which video i'm trying to download from 'vivo.sx', 'youtube-dl' fails with the same error message as displayed in the protocol.
I have no solution for this problem. All what i can see is that the POST-request obviously fails, because 'youtube-dl' downloads the same webpage (with the same hidden form). I tried different methods - from "waiting" like in the 'streamcloud' extractor module to "removing" the stored cookie to multiple reloads (with and without delays), but nothing works ...

OK, thanks!


Adding ability to recurse a dist dir

This is another way to address https://github.com/gorilla-co/s3pypi/issues/88

I think being able to use tox and upload to s3 in a cross platform native python way is worth the extra lines of code. Let me know if you would like me to add documentation to how to use s3pypi in tox with example config, or if you would like to see better test coverage for this change,  or what other improvements I might be able to make.

I see how this could be beneficial in environments without shell expansion, but I'm also hesitant. What if someone writes s3pypi foo/* expecting this to go only one level deep, like most shell commands would? Am I being paranoid?

This is a good point. Let me see if i can come up with a way to address shell expansion having already explored a directory in a clean way.

I see how this could be beneficial in environments without shell expansion, but I'm also hesitant. What if someone writes s3pypi foo/* expecting this to go only one level deep, like most shell commands would? Am I being paranoid?

This is a good point. Let me see if i can come up with a way to address shell expansion having already explored a directory in a clean way.

oops, accidentally closed this, mea culpa.

I see how this could be beneficial in environments without shell expansion, but I'm also hesitant. What if someone writes s3pypi foo/* expecting this to go only one level deep, like most shell commands would? Am I being paranoid?

we could add a --dir option, that allows you to specify a directory, and leave the existing args behavior as is.

we could add a --dir option, that allows you to specify a directory, and leave the existing args behavior as is.

That sounds reasonable. What do you think of calling it -r, --recursive (a boolean flag)?

we could add a --dir option, that allows you to specify a directory, and leave the existing args behavior as is.

That sounds reasonable. What do you think of calling it -r, --recursive (a boolean flag)?

I am on board 100%. Ill get to work on it.

we could add a --dir option, that allows you to specify a directory, and leave the existing args behavior as is.

That sounds reasonable. What do you think of calling it -r, --recursive (a boolean flag)?

I am on board 100%. Ill get to work on it.

ok, one of these days I am going to figure out how to not close the silly pr. very sorry for the email spam

we could add a --dir option, that allows you to specify a directory, and leave the existing args behavior as is.

That sounds reasonable. What do you think of calling it -r, --recursive (a boolean flag)?

If we use a -r --recursive, should it go infinitely deep?

If we use a -r --recursive, should it go infinitely deep?

Sure, that's the most obvious behaviour given the name. I guess in practice deep recursion won't be needed much, and if I understand correctly you only need it for a single level, right?

Hey, I had a realization. Because Tox is not auto-expanding the command line, we can just handle that specific case. We know that the file will come in as a non-existant file, since it is a file pattern. I am going to open a new pull request to look at this option and discuss.

We should probably see if we like https://github.com/gorilla-co/s3pypi/pull/90 more than this pull request. If so, then we can close this one.

closing in favor of #90


async/await laconia/batch

Current version of laconia/batch requires callback parameter, this parameter should be removed from v2.0.0, before it we need some alternative to laconia/batch that use async/await instead of EventEmiter. Or rewrite it to use callback even when laconia/core don't.

Closed in favour of https://github.com/laconiajs/laconia/issues/838


Check how residual mortality rate is updated

Ideally residual mortality rate is updated automatically when new diseases are added

Here is what I've found about this:

1. Computing excess_mean
-------------------

for each AGE, SEX in {0, ... 100} X {female, male}:
    excess_mean[AGE, SEX] <- mean(F(P)) for each P in population such that P.age = AGE and P.sex = SEX

where:

function F(P):
    let M <- 1

    for each DISEASE in P's active diseases:
        M <- M * (1 - DISEASE.excess_mortality)

    return clip M, such that 0 <= M <= 1

2. Computing residual_mortality
-------------------------------

for each AGE, SEX in {0, ... 100} X {female, male}:
    residual_mortality[AGE, SEX] <- 1 - (1 - death_rate[AGE, SEX]) / excess_mean[AGE, SEX]

    clip residual_mortality between 0 and 1 inclusive

Notes:

death_rate is computed from the static backend data (./data/undb/mortality/M[country].csv, which must be defined for all years in the simulation.

DISEASE.excess_mortality is defined in the static backend data (./data/diseases/[disease]/D[country].csv. IMPORTANT: if undefined for a given disease, age and gender, it will (again, this problem...) return a default value of zero. That includes if anything is misspelled.

Let me know if anything doesn't make sense.


Pageupdown

PR for adding page up and down in text view

Fixes https://github.com/migueldeicaza/gui.cs/issues/139


refactor(legacy support): use unified component

Here is another attempt at implementing #71...

uses in-element-polyfill and maybe-in-element AST transforms to allow to use in-element with legacy support back to Ember 1.13 (ember-wormhole based) and support for renderInPlace (@cibernox fyi :))
Cleaned up unnecessary legacy components

BREAKING CHANGE:
Support for Ember <1.13 has been dropped!

This is awesome! I'll take a closer look in the next couple days, and confer with @pzuraq about how we want to handle dropping 1.11.
I believe the current version of ember-popper is solid enough that those on < 1.13 could use it where necessary, then possibly make this a beta v1.0.0 release?

Ok, this is green now. Removed the left over Ember 1.11 scenario form the Travis config.
Also one test for Ember Canary was failing before, which is now passing somehow, although nothing has changed!? But the same failed test can be seen on master, so not related I think...

Merged! I'll whip up a beta release of 1.0 tomorrow


WIP: Dummy PR

to test triggers

/test-v1a1-integration

/test-v1a1-centos-integration

/test-v1a1-centos-integration

/test-v1a1-integration

/test-v1a1-centos-integration

/test-v1a1-integration


add fallback to kubeclient 0 if only one is provided

Changes
if only one kubeclient is provided (most likely for a phase one merge), switch kubelet to use it.
Validation
Validate on local environment with

2 tp 1 rp, 2 endpoints in TENANT_SERVERS
1 tp 1 rp, 1 endpoint in TENANT_SERVERS

Pod goes into running into both cases.

change list doesn't look right. fixing.

/approve

/lgtm


4RC3 findOneAndUpdate returns not updated doc

In 4rc3 findOneAndUpdate works incorrectly (it updates, but callback result is not updated version of document).
var childSchema = new Schema({
    name: String,
});

var child = new Child({ name: 'Mary'});

child.save(function(){
    Child.findOneAndUpdate({_id: child.id}, {name: 'Jery}, function(err, updated){
        console.log('updated.name', updated.name) // --> 'Mary' - value before update
        Child.findOne({_id: child.id}, function(err, found){
            console.log('found.name', found.name) // --> 'Jerry' - value was actually updated in DB
        })
    })
})

This is by design. See 4.0 release notes and #2262. MongoDB's findAndModify has a new option that determines whether it returns the document before or after update. In the mongodb server and node driver new is false by default, but in mongoose 3.x new was true by default. In 4.0 mongoose will use false by default because IMO mongoose shouldn't set conflicting defaults unless there's a very good reason to.
var childSchema = new Schema({
    name: String,
});

var child = new Child({ name: 'Mary'});

child.save(function(){
    // Added the 'options' parameter below, setting the `new` option to true to get the new doc back
    Child.findOneAndUpdate({_id: child.id}, {name: 'Jery}, { 'new': true }, function(err, updated){
        console.log('updated.name', updated.name) // --> 'Mary' - value before update
        Child.findOne({_id: child.id}, function(err, found){
            console.log('found.name', found.name) // --> 'Jerry' - value was actually updated in DB
        })
    })
})

Thanks.

Putting the default to false really is one of those bad good ideas.
Thanks for the time wasted changing that during the version migration.

Sorry for difficulty. It's up there on the migration docs. However, this was a necessary change IMO.


Small over allocation in each aws_string

Hi !
It seems that aws_string_new_from_array is over allocating a bit of memory in each string.
Because of the fact that aws_string is defined as follow :
struct aws_string {
    struct aws_allocator *const allocator;
    const size_t len;
    const uint8_t bytes[1];
};

given alignment constraints in C, sizeof (struct aws_string) is 24.
The offset in a string struct denoted by str->bytes is 16 (allocator is at 0, len is at 8).
Now, aws_string_new_from_array allocates memory in the following way:
size_t malloc_size;
    if (aws_add_size_checked(sizeof(struct aws_string) + 1, len, &malloc_size)) {
        return NULL;
    }
    struct aws_string *str = aws_mem_acquire(allocator, malloc_size);
    if (!str) {
        return NULL;
    }

so it allocates 24 + length + 1 bytes, while only 16 + length + 1 bytes are needed.
So every aws_string contains 8 too many bytes that will never be accessed at the end of the object.
It's really not a lot, but it's an easy fix.

https://github.com/awslabs/aws-c-common/pull/1099 should resolve the overallocation.


Should not force

It would be good to be able to push all the script bits created by django-bootstrap3-datetimepicker to the end of the file, rather than the beginning.

@barchiesi  Indeed! I've got the same problem. It is best to include all the JS after the above-the-fold content, and the datetimepicker templates are in that content.
After over 2 years, is there any way to include the scripts afterwards?


Stellar API <IP_ADDRESS> crashes on "Injecting Stellar Manager"

Well, here we are again...
So now, after testing out Stellar Skies, I decided to use it with the rest of my mods because it looked really cool. But now when I go into my world, it says "Injecting Stellar Manager" and then crashes.
From the looks of the crash report, it looks like it's coming from Stellar API. I tried recreating the whole directory and replacing Stellar API, but no luck there. I also noticed it said Stellarium in there, which I can understand because I used to have Stellarium in there before I got rid of it because it was erroring.
Crash report: http://pastebin.com/mQAgDG8n
Logs: http://pastebin.com/b0rBBkjg
If you know why this is happening, please tell me. Right now, my thoughts are leaning on OptiFine, though. Thanks in advance!
(BTW, really looking forward to when Stellarium is done!)

This is problem with slimevoid's littleblock mod doing some hacking into the world. IT SHOULD NOT CREATE ANY WORLD INSTANCE ON THE WORLDEVENT.LOAD, at least itshould do it at last.
Just remove the mod, I expect there would be tons of replacements.

damn, i really liked that mod. well, if it means i can have stellar skies and all that shit then i can definitely get rid of it. thanks

You would better repot it to the author of the mod.

That I shall do.


ImportError: cannot import name 'Literal' from 'playwright.sync_api'

After playwright version https://github.com/microsoft/playwright-python/releases/tag/v0.171.1 when running example: https://github.com/Visual-Regression-Tracker/examples-python/tree/master/playwright error occurs:
Traceback (most recent call last):   File "**path_to_project**/examples-python/playwright/example.py", line 8, in <module>     from visual_regression_tracker.playwright import PlaywrightVisualRegressionTracker, PageTrackOptions, \   File "**path_to_env**/lib/python3.8/site-packages/visual_regression_tracker/playwright.py", line 7, in <module>     from playwright.sync_api import Literal, FloatRect ImportError: cannot import name 'Literal' from 'playwright.sync_api'

will be fixed by https://github.com/Visual-Regression-Tracker/sdk-python/issues/21

@schurakov  fixed in 4.8.0


[ISSUE-124] Add fallback mechanism for blocks read inconsistent

What changes were proposed in this pull request?

Add fallback mechanism for blocks read inconsistent
Why are the changes needed?

When the data in this first server is damaged, application will fail. #124 #129
Does this PR introduce any user-facing change?

No
How was this patch tested?

Already added

Codecov Report

Merging #276 (0e369de) into master (47effb2) will decrease coverage by 1.60%.
The diff coverage is 19.04%.

@@             Coverage Diff              @@
##             master     #276      +/-   ##
============================================
- Coverage     59.71%   58.10%   -1.61%
+ Complexity     1377     1303      -74
============================================
  Files           166      157       -9
  Lines          8918     8492     -426
  Branches        853      840      -13
============================================
- Hits           5325     4934     -391
+ Misses         3318     3287      -31
+ Partials        275      271       -4

Impacted Files
Coverage Δ

...torage/handler/impl/AbstractClientReadHandler.java
16.66% <0.00%> (-3.34%)
:arrow_down:

...torage/handler/impl/ComposedClientReadHandler.java
0.00% <0.00%> (ø)

...e/storage/handler/impl/HdfsShuffleReadHandler.java
57.14% <0.00%> (ø)

...handler/impl/LocalFileQuorumClientReadHandler.java
0.00% <0.00%> (ø)

.../storage/handler/impl/MemoryClientReadHandler.java
0.00% <0.00%> (ø)

...ge/handler/impl/MemoryQuorumClientReadHandler.java
0.00% <0.00%> (ø)

...storage/handler/impl/DataSkippableReadHandler.java
75.00% <25.00%> (-9.38%)
:arrow_down:

...le/storage/handler/impl/HdfsClientReadHandler.java
63.21% <25.00%> (-12.13%)
:arrow_down:

...che/uniffle/client/impl/ShuffleReadClientImpl.java
87.96% <83.33%> (-1.73%)
:arrow_down:

... and 11 more

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

What's the relation between this pr and #129 ?

What's the relation between this pr and #129 ?

As what we discuss in #129, #129 is not the best and it will be split into multiple prs and this pr is one of them.

One question: Should we use the concept of FALLBACK. In my opinion, we use fallback mechanism to process error or exception, but it's normal for us to read memory, localfile and hdfs at the same time.

One question: Should we use the concept of FALLBACK. In my opinion, we use fallback mechanism to process error or exception, but it's normal for us to read memory, localfile and hdfs at the same time.

The major reasion is the client just read from one shuffle server, it is a bug. #124

One question: Should we use the concept of FALLBACK. In my opinion, we use fallback mechanism to process error or exception, but it's normal for us to read memory, localfile and hdfs at the same time.

So, what is your opinion?

One question: Should we use the concept of FALLBACK. In my opinion, we use fallback mechanism to process error or exception, but it's normal for us to read memory, localfile and hdfs at the same time.

So, what is your opinion?

Should we use method next() instead of fallback()?
We shouldn't have the concept of maxFallbackTimes.

Should we use method next() instead of fallback()?
We shouldn't have the concept of maxFallbackTimes.

How about fallback() -> nextRound() and maxFallbackTimes -> maxRounds?

Should we use method next() instead of fallback()?
We shouldn't have the concept of maxFallbackTimes.

How about fallback() -> nextRound() and maxFallbackTimes -> maxRounds?
If you have three replicas, every replica have memory, disk and hdfs. Whether maxRounds 3 is enough to read all the data?

If you have three replicas, every replica have memory, disk and hdfs. Whether maxRounds 3 is enough to read all the data?

No guarantee. For example, the blocks is incomplete after first round, and than can't read from any shuffle server which store the missing blocks

If you have three replicas, every replica have memory, disk and hdfs. Whether maxRounds 3 is enough to read all the data?

No guarantee. For example, the blocks is incomplete after first round, and than can't read from any shuffle server which store the missing blocks

So I feel that maxRounds isn't reasonable for this situation.

So I feel that maxRounds isn't reasonable for this situation.

I have another solution：

Set maxFailTimes and failTime in every handler
When readShuffleData fail, ++failTime
When readShuffleData  success, failTime = 0
If failTime >= maxFailTimes , finished=true
What do you think?

So I feel that maxRounds isn't reasonable for this situation.

I have another solution：

Set maxFailTimes and failTime in every handler
When readShuffleData fail, ++failTime
When readShuffleData  success, failTime = 0
If failTime >= maxFailTimes , finished=true
What do you think?

MaxFailureTime will tolerate the logic of replicas, this is my biggest concern.

MaxFailureTime will tolerate the logic of replicas, this is my biggest concern.

I don't understand

MaxFailureTime will tolerate the logic of replicas, this is my biggest concern.

I don't understand

For replica logic, if we use 7 replicas, we should read 4 replica successfully, but if maxFailure is 3 . Although we have 4 correct replicas, the application will fail because the app  may read 3 wrong replicas.

For replica logic, if we use 7 replicas, we should read 4 replica successfully, but if maxFailure is 3 . Although we have 4 correct replicas, the application will fail because the app may read 3 wrong replicas.

I mean maxFailTimes is for each replica.

For replica logic, if we use 7 replicas, we should read 4 replica successfully, but if maxFailure is 3 . Although we have 4 correct replicas, the application will fail because the app may read 3 wrong replicas.

I mean maxFailTimes is for each replica.

It seems ok.

@jerqi What wrong with CI now?

@jerqi What wrong with CI now?

Maybe your test code have endless loop. The test code can't stop.

Is there any design doc mentioned in #124?

I have another solution：

Set maxFailTimes and failTime in every handler
When readShuffleData fail, ++failTime
When readShuffleData  success, failTime = 0
If failTime >= maxFailTimes , finished=true

If you can't understand, i will try to write a design doc.  @duanmeng

I have another solution：

Set maxFailTimes and failTime in every handler
When readShuffleData fail, ++failTime
When readShuffleData  success, failTime = 0
If failTime >= maxFailTimes , finished=true

If you can't understand, i will try to write a design doc. @duanmeng

No hurry, let's focus on this pr first.

Could we use the order server A memory -> server A LOCALFILE -> server A HDFS server B memory -> server B LOCALFILE -> server B HDFS server C memory -> server C LOCALFILE -> server C HDFS or the order server A memory -> server B memory -> server C memory server A LOCALFILE -> server B LOCALFILE -> server C LOCALFILE HDFS
Other order may produce problems because memory data may be flushed after we mark the handler finished state.

I think the first solution is better, i will try to do it.

We'd better have a layer abstraction to encapsulate the order logic.

Could we use the order
server A memory -> server A LOCALFILE -> server A HDFS
server B memory -> server B LOCALFILE -> server B HDFS
server C memory -> server C LOCALFILE -> server C HDFS

I have already followed this plan. If the basic logic is OK, i will remove some deprecated class and add more uts. @jerqi

The basic logic is ok. I think you can go ahead.

PTAL @jerqi

LGTM except for minor issues , cc @Gustfh Do you have another suggestion?

Merged. thanks all.


Updates to documentation for managing Task History data

Content was added to support the release of Task History. Specifically, this is the addition of documentation to educate Admins for how to delete and extract Task History data for projects in their environments

@SerdarSoysal , is this a merge you can help with?

Using an alternative approach to open the PR


[Request] increase radiation radius.

I have a suggestion.
I would like that if the radiation get higher also the radius grows so you need to keep the radiation low or your base could get radiated.

You can already increase these settings in the config


Move all wallet specific helpers to @kadena/wallet

Please confirm the following:

[X] I have read the Code of Conduct
[X] The feature was not suggested before

Is your feature request related to a problem?
@kadena/wallet could be a place for all wallet specific helpers
I believe we also need to think about the api, since wallets have some features like connect,get accounts and etc...
we had a related discussion here
https://github.com/kadena-community/kadena.js/pull/750
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Do you have any additional context?
No response
Participation

[ ] I am willing to submit a pull request for this feature request.

I suggest we use @kadena/wallet-adapters as a name. With wallet people could get the idea that the contents are for wallet builders. It is also in line with others in the space, such as MetaMask and Solana


rebase distribution-specific build

Signed-off-by: Sally O'Malley<EMAIL_ADDRESS>

closing https://github.com/rhatdan/docker/pull/102

Merged.


[he_IL] email username transliteration

I'm using Faker to test localization issues in my application and I've found the bug in [he_IL] locale.
$faker = Faker\Factory::create( 'he_IL' );

$client['first_name'] = $faker->firstName;   // result is 'פורת'
$client['last_name']  = $faker->lastName;   // result is 'תאומים'
$client['email']      = $faker->unique()->safeEmail; // result is<EMAIL_ADDRESS>
When I'm using this code for ModelFactory I'm getting email unique error.
  [PDOException (23000)]
  SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry<EMAIL_ADDRESS>for key 'users_email_unique'

I haven't php_intl ext in my docker container and seems static::toAscii($string) knows nothing about [he_IL]

Hi.
I checked through the Hebrew generator and noticed that there is no e-mail method in the locale. In the absence of it, Faker seems to use the generic e-mail addresses. Maybe this should be added in order to make the structure consistent.
I will submit a pull request in order to fix the transliteration.

I will close this issue since it seems to no longer be relevant. I tried it with code above and following data is returned:
Array
(
    [first_name] => רימון
    [last_name] => אייגש
    [email] =><EMAIL_ADDRESS>)


Preventing drop on another item in the same list

I'm using sortablejs for reordering the list. The list is a bunch of Bootstrap 4 divs with class "col" on them so basically I'm reordering a layout by dragging the paragraphs.
When I drag the containers so that the other has time to move "out of the way", everything works, but if I drag an item onto another item, weird things happen. I think the code tries to merge all the character data of the div into the one I dropped it on. The cols also include toolbars that are not part of the item data but somehow these also get merged.
I would like to stop the behavior when the items are trying to merge and just limit it to the reordering (where the items move out of the way.
Is there something different going on when the sortable items are dragged on top of each other? Is there a way to prevent this action?

Hi
Please reproduce the problem on stackblitz or plunkr.

unclear + inactivity => closing


add notifications screen

@keybase/react-hackers notifications screen. the toggle logic will be handled in the action (like clicking unsubscribe from all should uncheck the other settings)

@keybase/react-hackers bump


[Unity][Pass] Reuse prior infra to implement more complete DCE

As a follow-up to https://github.com/apache/tvm/pull/14262, I just noticed that I previously implemented a function called RemoveAllUnused (https://github.com/apache/tvm/pull/14043) that can do function-wise DCE and should be more complete than https://github.com/apache/tvm/pull/14262 as RemoveAllUnused can also remove dead dataflow blocks (added two test-cases to show that).
Sorry, I should have mentioned that earlier to avoid duplication... but still I am putting a patch here in case it is desired.
cc: @spectrometerHBH @tqchen

At the high level, https://github.com/apache/tvm/pull/14043 is based on a fix-point algorithm to remove unused dataflow statements iteratively. While I think @spectrometerHBH 's impl is more efficient based on the assumption from the dataflow block.

BTW, although this patch uses RemoveAllUnused over @spectrometerHBH 's implementation, it did not remove the prior implementation as well. Not sure if we should just keep it in case of future usage or just trim it to simplify the code...

I think we can simply trim it and consolidate the use

For now:

tvm.relax.transform.DeadCodeElimination is the pass for running DCE over an IRModule.
tvm.relax.analysis.remove_all_unused is the pass that .... over a function.

tvm.relax.transform.DeadCodeElimination is implemented based on tvm.relax.analysis.remove_all_unused. I did not sync the function name for the two, as I saw there are other uses for RemoveAllUnused so just want to be conservative first.

@ganler Thanks for the clarification!


CAN Bus Disengage

When using a StreamDeck to recall camera presets through Middle Control it disengages or disconnects from the Blackmagic Television Switcher thereby not saving my zoom or focus in the preset. After about 10 sec. it reengages the CAN Bus on my Middle Things Control UI.

Hello, that looks more like a hardware issue. Could you please send us an email to<EMAIL_ADDRESS>with your APC-R serial number ?


Add Stream-based Control Flow for Observation Emitter

This commit introduces tokio streams to control how often a third-party
adapter is called to fetch data from a data source. The adapter is called
on an interval using a timer, and the results are chunked before being
returned as a stream.
It adds a simple stream-based pipeline to gather observations
as they're emitted by a local cache. It plumbs together a futures API
to make event handling nature and easy.
chore: Add stream-based control flow for third-party adapters.

#5  👈
trunk

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @RobbieMcKinstry and the rest of your teammates on  Graphite


installation

is the satisfactory docker  ready for use jet and if can you explain how to use it in pterodactyl

No, it was a proof of concept I was messing around with.  I will not be providing any builds or support for it.

Ok thanks for the answer


Update Jackson to 2.8.5

There are 2 code changes:

use non generic factory method 'writerWithPrettyPrinter'
replace deprecated exception method

Thanks for doing this, @jensraaby. I'd like to leave this open for a while (probably at least a week or two) to make sure that anyone who needs the older Jackson version is able to upgrade.
We should probably ask around in the Finch Gitter room in particular, since finch-circe provides support for using Jackson for parsing and printing, and this change will force all finch-circe users to be on the newer Jackson release.

@jensraaby An alternative approach would be to split circe-jackson into its own repo in the new circe organization and cross-publish it for multiple Jackson releases. I don't really want to have circe-jackson25, circe-jackson26, etc. in the circe build itself, but it seems totally reasonable to promote this to a new repo and have those modules there.

Thanks for the information. I've had issues with multiple Jackson versions before (like this https://github.com/twitter/twitter-server/issues/4)

Current coverage is 82.60% (diff: 100%)

Merging #501 into master will increase coverage by 0.19%

@@             master       #501   diff @@
==========================================
  Files            77         77
  Lines          2041       2041
  Methods        1893       1896     +3
  Messages          0          0
  Branches        148        145     -3
==========================================
+ Hits           1682       1686     +4
+ Misses          359        355     -4
  Partials          0          0

Powered by Codecov. Last update 9ec2549...e2e3bb3

Sorry that link should have been  #43

I'm going to go ahead and merge this, filter-branch the circe-jackson source into the new circe-jackson repo I've got set up, and then we can delete all the circe-jackson stuff in this repo in a follow-up PR.


[Event Request] Page 9255 "Tasks Matrix" - OnBeforePageRunOnMatrixOnDrillDown

Describe the request
I want to run a custom page instead of the default "Task List". Therefore, I request the following event:
local procedure MatrixOnDrillDown(ColumnID: Integer)
//NEW BEGIN
var
	IsHandled: Boolean;
//NEW END
begin
	//...
	Task.SetFilter("Salesperson Code", Rec.GetFilter("Salesperson Filter"));
	Task.SetFilter("Team Code", Rec.GetFilter("Team Filter"));
	Task.SetFilter("Contact Company No.", Rec.GetFilter("Contact Company Filter"));
	Task.SetFilter(Status, Rec.GetFilter("Task Status Filter"));
	Task.SetFilter(Closed, Rec.GetFilter("Task Closed Filter"));
	Task.SetFilter(Priority, Rec.GetFilter("Priority Filter"));
	Task.SetFilter("System To-do Type", Rec.GetFilter("System Task Type Filter"));
	//NEW BEGIN
	IsHandled := false;
	OnBeforePageRunOnMatrixOnDrillDown(Rec.Task, IsHandled);
	if not IsHandled then
	//NEW END
		PAGE.RunModal(PAGE::"Task List", Task);
end;
[IntegrationEvent(false, false)]
local procedure OnBeforePageRunOnMatrixOnDrillDown(Task: Record "To-do"; var IsHandled: Boolean)
begin
end;

Additional context
I want to run a custom page instead of the default "Task List" on the Matrix Drill Down.
Internal work item: AB#544568

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 23206.


Fate reservations moved out of memory

closes #4131
Fate reservations were moved out of memory. This is a WIP PR* for one part that is needed for having Fate be distributed in the future.

Reservations for MetaFateStore were moved out of memory into ZooKeeper
Reservations for UserFateStore were moved out of memory into the Accumulo Fate table

Is an additional column which just indicates whether the FateId of that row is reserved or not

Added test MultipleStoresIT

Tests the new functionality of how reservations are stored
I also included a couple tests in MultipleStoresIT that are testing the reserve/unreserve functionality and that it still works as intended. This can be moved from this class if desired.

Verified existing tests in the fate test package (FateIT, FateOpsCommandsIT, FateStoreIT, ZooMutatorIT, FateMutatorImplIT, UserFateStoreIT) still pass

*There are still a few things I have marked as TODO that I would like input/suggestions on. These are marked in the code as "TODO 4131".

Marking this as ready for review, since it may not be reviewed otherwise

I have made the following changes in https://github.com/apache/accumulo/pull/4524/commits/e6671fbb903da53014bd64e53ad125351add6a04:

Combined the LockID and reservation attempt UUID into one new object: FateReservation
Now cover edge case with tryReserve() where a write may make it to the server, but the server dies before a response is received
New FATE Thread: DeadReservationCleaner which deletes reservations held by Managers that have since died
Created new classes: ColumnValueMappingIterator and ReservationMappingIterator. ColumnValueMappingIterator abstracts out the common functionality of ReservationMappingIterator and StatusMappingIterator. ReservationMappingIterator is an iterator used for determining if the reservation column for a FateId has a FateReservation set or not
Expanded/improved/simplified MultipleStoresIT tests

There are also some comments/questions labeled "TODO 4131" that I would like input on.
I also have to resolve the merge conflicts which I will do now.

@keith-turner, @DomGarguilo
I have addressed all of the review changes, and this PR is ready for re-review. However, some tests are no longer passing (e.g., ComprehensiveIT). I believe this is an issue with my new implementation of createAndReserve. I believe the issue is with the UserFateStore implementation, but could be both. Posting this new commit now to get the other changes out, and to potentially receive feedback on what might be wrong with createAndReserve(). I will continue to look into what the issue might be in the meantime. Please take a look at my new review comments and my new commit message:

Stricter check of the column value for fate reservations. If anything unexpected is seen, an error is now thrown.
Simplified MetaFateStore.getActiveReservations() to only read from ZooKeeper once.
Combined the two scans that were done in AbstractFateStore.runnable() into one. This meant adding FateReservation to FateIdStatus and refactoring Meta/UserFateStore.getTransactions().
No longer use/store a string representation of the FateReservation (was used in UserFateStore). Now, only the serialized value is used. This keeps the usage of FateReservation consistent across Meta and UserFateStore. It was also unneccessary, so simplifies code.
Moved AbstractFateStore.createAndReserve() implementation into Meta and UserFateStore, and rewrote the impl for each to work with the new way reservations are stored. This also allowed me to delete methods that were only used by AFS.createAndReserve(): create(FateId, FateKey), getStatusAndKey(FateId), create(FateKey).
Fixed how concurrentStatusChangeCallers was decremented in AbstractFateStore.waitForStatusChange()
Small change to MetaFateStore.deleteDeadReservations() to avoid reading from ZK unnecessarily
Added isReservedBy() method to MetaFateStore.NodeValue to avoid code duplication and make the code more clear.
Since the FateIdStatus now has the FateReservation, realized Meta and UserFateStore.getActiveReservations() could now be simplified to just call list(). This also made the impls the same, so moved to AbstractFateStore. This also made me realize that I had put getActiveReservations() method signature in FateStore, but would be better suited for ReadOnlyFateStore, so moved it there.
Deleted FateStore.isReserved(FateId)... No longer needed/used
Moved UNKNOWN status check in AbstractFateStore.reserve() into waiting loop
Now log when a dead reservation is detected and deleted
Minor change to Fate: no longer create the executor for the dead reservation cleaner if it's not going to be used

I have found and addressed the bug in my most recent commit. This PR is now ready for full review.
The tests verified to still pass: the sunny day tests, all fate tests (ZooMutatorIT, FateMutatorImplIT, UserFateStoreIT, FateInterleavingIT, FateIT, FateOpsCommandsIT, ComprehensiveFlakyFateIT, DeleteRowsFlakyFateIT, ManagerRepoIT, and MultipleStoresIT (new test added)) except FateStoreIT. FateStoreIT reflects a method that has been removed in this PR, and want to receive feedback about the removal of this method before changes are made to this test. Have a "TODO 4131" marking this so this is not forgotten.

@keith-turner - Addressed all review comments, this PR is ready for re-review.
See new commit bd1f17472c8d289878e19d7121f9fc9347e95596
I also fixed FateStoreIT to work with the new impl of createAndReserve(). A method was deleted in<PHONE_NUMBER>387ae537af7050106c9645aac19aae that was no longer used which FateStoreIT relied on. Upon fixing this test, noticed that the original impl of createAndReserve expected an error to be thrown in a certain situation, but in the new implementation, an empty optional was returned instead. Fixed the new impl to match the previous impl for this case. This meant changing UFS.createAndReserve and MFS.createAndReserve.
Also verified existing Fate tests still pass: ZooMutatorIT,FateMutatorImplIT,UserFateStoreIT,FateInterleavingIT,FateIT,FateOpsCommandsIT,ComprehensiveFlakyFateIT,DeleteRowsFlakyFateIT,ManagerRepoIT,MultipleStoresIT,FateStoreIT
and verified sunny day tests still pass.

I am finally looking through the test changes right now.   Everything else looks good.

I have compiled and wrote all the follow on issues for this to be merged. This covers all the issues I marked in this PR as TODO 4131 and all the unresolved review comments.
Here is a synopsis of the follow on issues I will create:

Refactor MultipleStoresIT to function more similarly to other Fate tests like FateIT
Add FateKey toString() method
Move MetaFateStore to org.apache.accumulo.core.fate.zookeeper
Deprecate AbstractFateStore.createDummyLockID(): this includes creating a path in ZK for utilities to get a ZK lock, changing admin fate fail and admin fate delete commands to get a LockID at this path and no longer require the Manager to be down, and only use a LockID for a store if write operations are expected: the store should fail on write operations if writes are not expected.
Replace AFS.verifyReserved with a condition on the RESERVATION_COLUMN to verify that it is reserved
Make WorkFinder and the TransactionRunners critical to the Manager
Refactor how the RESERVATION_COLUMN works for UserFateStore: create/delete column on reserve/unreserve
Additional fate test case from https://github.com/apache/accumulo/pull/4524#discussion_r1702301996

Here are some questions I still have:

This was an existing TODO that you had marked in your "distributed FATE" WIP PR:

// TODO 4131
// TODO make the max time a function of the number of concurrent callers, as the number of
// concurrent callers increases then increase the max wait time
// TODO could support signaling within this instance for known events
// TODO made the maxWait low so this would be responsive... that may put a lot of load in
// the case there are lots of things waiting...

I made the max wait = curr num callers in seconds. Does this address the first TODO? For the other two TODOs, I was not sure what was to be done, so I left them. Can these be safely deleted without creating follow on issue(s)? If follow on issues should be made, perhaps it would be best for you to write these or explain it here because I am not sure what should be done.

Re one of your review comments:
"Not a change to make in this PR. Thinking if we push all of the Fate data into a single node it would be nice to use JSON. That would make the data stored in ZK more human readable and it would make it easier to serialize and de-serialize."
Could you elaborate on what you mean by "all of the Fate data into a single node". By "all" do you mean the Repos, TxInfo, Status, Reservation, and FateKey would be in one ZK node? Writing the issue, I want to be sure I'm understanding correctly.

Can https://github.com/apache/accumulo/pull/4524#discussion_r1663064467 be resolved? Or should an issue be made?

There was a TODO regarding whether the ZooUtil.LockID was the best type for the lock. Should I make a follow on issue regarding this or is ZooUtil.LockID okay?

Can this https://github.com/apache/accumulo/pull/4524#discussion_r1663064467 be resolved or should a follow on issue be made?

Can these be resolved: https://github.com/apache/accumulo/pull/4524#discussion_r1670934639, https://github.com/apache/accumulo/pull/4524#discussion_r1695958819

The DeadReservationCleaner runs every 30 seconds. Is this okay? Should this be longer? Shorter?

Once the above questions are answered, I can complete my full list of new follow-on issues. This will allow me to remove all the TODO 4131 in this PR and all the comments in this PR can be resolved as all of these will be addressed or have a follow on issue created for them.

I resolved a few of the comments.

There was a TODO regarding whether the ZooUtil.LockID was the best type for the lock. Should I make a follow on issue regarding this or is ZooUtil.LockID okay?

That type seems like the best exiting type to used, so I do not think an issue is needed.

The DeadReservationCleaner runs every 30 seconds. Is this okay? Should this be longer? Shorter?

30 seconds seems too short to me.  Would be doing a lot of work and usually never finding anything, should probably be longer maybe 2 or 3 minutes.

Could you elaborate on what you mean by "all of the Fate data into a single node". By "all" do you mean the Repos, TxInfo, Status, Reservation, and FateKey would be in one ZK node? Writing the issue, I want to be sure I'm understanding correctly.

I was thinking of putting all data that is related to a single fate id into a single zk node.  This will allow atomic updates.  It will be slower (always have to rewrite all repos when adding/removing).  We are only using it for the metadata table.  So thinking it will make things more correct at the expense of speed but that tradeoff is good for metadata related fates.

Can these be safely deleted without creating follow on issue(s)? If follow on issues should be made, perhaps it would be best for you to write these or explain it here because I am not sure what should be done.

Yeah you can delete those.  I will look into it and open an issue if needed.

@kevinrr888 it seems like the only unresolved conversations are covered by your list of issues to open.  I just left those open for now.

The TODO 4131 comments have now been removed and I believe this PR is ready to be merged :tada:
I was planning on creating the follow-on issues after this is merged in as a batch of new issues.
As suggested by @ctubbsii in our meeting today, I will post a list of all the outstanding changes to be made below. The trivial ones, I will just make a PR for without creating an issue, the more involved follow-ons will be tracked in an issue.
Here is the list of changes to be made:
To be tracked by issue:

[ ] Refactor MultipleStoresIT to function more similarly to other Fate tests like FateIT
[ ] Deprecate AbstractFateStore.createDummyLockID(): this includes creating a path in ZK for utilities to get a ZK lock, changing admin fate fail and admin fate delete commands to get a LockID at this path and no longer require the Manager to be down, and only use a LockID for a store if write operations are expected: the store should fail on write operations if writes are not expected.
[ ] A single ZK node for all fate data for each fate id
[ ] Replace AFS.verifyReserved with a condition on the RESERVATION_COLUMN to verify that it is reserved
[ ] Make WorkFinder and the TransactionRunners critical to the Manager
[ ] Refactor how the RESERVATION_COLUMN works for UserFateStore: create/delete column on reserve/unreserve

Will do in one or a few small PRs:

[ ] Add a toString() to FateKey
[ ] Move MetaFateStore to org.apache.accumulo.core.fate.zookeeper
[ ] Periodic clean up of dead reservations should be increased from every 30 seconds to every few minutes
[ ] Add additional fate test case suggested in https://github.com/apache/accumulo/pull/4524#discussion_r1702301996

Resolved the merge conflicts with AbstractFateStore using the new CountDownTimer.
Also noticed a sync block that should have been removed so removed that.
AbstractFateStore should probably be looked at again before this is merged.

@kevinrr888 -

This was an existing TODO that you had marked in your "distributed FATE" WIP PR:
// TODO 4131
// TODO make the max time a function of the number of concurrent callers, as the number of
// concurrent callers increases then increase the max wait time
// TODO could support signaling within this instance for known events
// TODO made the maxWait low so this would be responsive... that may put a lot of load in
// the case there are lots of things waiting...
I made the max wait = curr num callers in seconds. Does this address the first TODO? For the other two TODOs, I was not sure what was to be done, so I left them. Can these be safely deleted without creating follow on issue(s)? If follow on issues should be made, perhaps it would be best for you to write these or explain it here because I am not sure what should be done.

@keith-turner -

Yeah you can delete those. I will look into it and open an issue if needed.

This may still need to be looked into just posting this as a reminder just in case


Unable to edit location

Once a server is added, there is no way to edit its location.

Any progress on this? I just noticed this and actually had to write my own SQL queries to update a location.

This is fixed in upcoming version link


Distributed data parallel training for streaming datasets

Feature request
Any documentations for the the load_dataset(streaming=True) for (multi-node multi-GPU) DDP training?
Motivation
Given a bunch of data files, it is expected to split them onto different GPUs. Is there a guide or documentation?
Your contribution
Does it requires manually split on data files for each worker in DatasetBuilder._split_generator()? What isIterableDatasetShard expected to do?

Hi ! According to https://huggingface.co/docs/datasets/use_with_pytorch#stream-data you can use the pytorch DataLoader with num_workers>0 to distribute the shards across your workers (it uses torch.utils.data.get_worker_info() to get the worker ID and select the right subsets of shards to use)

@cyk1337 does streaming datasets with multi-gpu works for you? I am testing on one node, but this is freezing, https://github.com/huggingface/datasets/issues/5123
In case you could make this work, could you share with me your codes?
thank you

+1

This has been implemented in datasets 2.8:
from datasets.distributed import split_dataset_by_node

ds = split_dataset_by_node(ds, rank=rank, world_size=world_size)

i'm having hanging issues with this when using DDP and allocating the datasets with split_dataset_by_node 🤔


Searching for bugs, nothing to see here... xgubmo

Searching for bugs, nothing to see here... xgubmo

 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.


Corrected examples

https://github.com/MicrosoftDocs/office-docs-powershell/issues/5606

Docs Build status updates of commit 19ce7d4:
:clock10: Full build: the average full build time is 17 min(s) 53 sec(s), this is based on the last 1000 build(s) for this repository.


Pod CPU throttling even when limits aren't reached

Environmental Info:
K3s Version:
k3s version v1.21.5+k3s2 (724ef700)
go version go1.16.8
Node(s) CPU architecture, OS, and Version:
Linux dedicated-master-1 5.4.0-96-generic #109-Ubuntu SMP Wed Jan 12 16:49:16 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
3 servers, one master, 3 workers
Describe the bug:
The pods are throttled even when the limits aren't reached.
Steps To Reproduce:

create a container with a 200 mili CPU limit, then make some load inside the pod until 100 mili CPU units are consumed.

Expected behavior:
The CPU should be throttled when the usage is close to the CPU limit.
Actual behavior:
The CPU is being throttled when the CPU usage is 50% from the target limit, especially when the target limit is <= 1000 milis.
Additional context / logs:

Backporting
I don't know if this issue needs backporting.

K3s does not modify upstream's behavior at all with regards to resource allocation. What you're probably running into has something to do with how the kernel allocates time slices based on CPU allocations, see:
https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#how-pods-with-resource-limits-are-run


Plan for Angular 8 Support?

I would like to upgrade my angular-7 project to angular-8.
Do you have a plan for upgrading it to support angular-8? If not, how can I help with it?
I have cloned the master-branch and locally upgraded to angular8. Unittests were through with small modification.
Shall I create a new branch and push it and create merge request?
Also I would like to know how I can test it with my local app(s).

sure, I would.
not always have time for it.

Shall I create a new branch and push it and create merge request?
it would be fantastic!

Also I would like to know how I can test it with my local app(s).
you can build npm package locally(https://github.com/stevermeister/ngx-wig/blob/master/package.json#L11) and import it to your project (instead of npm one)

.. and I was not allowed to push..

here you can find information how to do pull requests - https://help.github.com/en/articles/creating-a-pull-request-from-a-fork

But it doesn't work with angular7. it says
it's not good. ideally to keep backwards compatibility with previous version

it was a stupid mistake... my project was original with angular6 and upgraded to angular7. That time it wasn't a problem and therefore ngx-wig package remained with an old version (1.6!!).
I've upgraded it to 2.1.1 and has no problem at all.. sorry that i've bothered you.


No app file found in directory

I have created a brand new app, followed the instructions provided, however when I run the uploadToHockeyApp task, I get the following error:
No app file found in directory /Users/jm/Documents/Android/SampleApp/build
I have only specified my api key. Is there anything else that needs to be specified? Thanks

I got it working by specifying the outputDirectory. Is this required for Android?

Hi @jpcmorton :
no this is not required if you use the android gradle plugin.
Could you please post your build.gradle?

buildscript {
    repositories {
        jcenter()
        mavenCentral()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:1.0.0'
        classpath 'de.felixschulze.gradle:gradle-hockeyapp-plugin:3.0'
        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

repositories {
    mavenCentral()
}

allprojects {
    repositories {
        jcenter()
    }
}

apply plugin: 'de.felixschulze.gradle.hockeyapp'

hockeyapp {
    apiToken = "APITOKEN"
    outputDirectory = 'app/build/outputs/apk'
    appFileNameRegex = '.*.apk'
}

When you remove appFileNameRegex and outputDirectory it should work automatically?

No, I get
No applicationFile found or no appFileNameRegex provided.

I am using Android Gradle on OSX 10.10. This is literally a fresh install of android studio and a brand new app after I formatted my computer. But I guess in the end it doesn't matter if I can specify the location of the APK.

Could you please run with --debug and post the output about the location of the apk?

I'm closing this issue during inactivity. Please feel free to open again if the issue is not solved.

I'm having the same issue as well. Will post log shortly


Convert groovy Gradle scripts to Kotlin

Description
In preparation for the automated release integration, we need to bring the Gradle configuration inline with the rest of the Hedera projects. To do so, we need to convert the groovy scripts to Kotlin and introduce the standard build-logic mechanism used by the other Gradle projects.

Hey @nathanklick, this issue seems to be completed in this PR - https://github.com/hashgraph/hedera-sdk-java/pull/1732
I will go ahead and close the issue now. Let me know if you believe there are any pending items related to this conversion to Kotlin.


⚠ Bofrost.lu has degraded performance

In f97987a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1339 ms

Resolved: Bofrost.lu performance has improved in 8b9cef5 after 9 minutes.


Karma unti test with $httpBackend.Response(500) nevers callsback the .then onError()

Test
it("Test", function () {
var group;
group = { "name": "G1", "id": "a73b8a9c-e319-4058-9499-9c615a9b1c7e" };
$httpBackend.expectPOST("api/myUrl").respond(500);
returnedPromiseObject = mySvc.getNames(dummyData);
$httpBackend.flush();
expect(returnedPromiseObject.$$state.value.status).toBe(error.status);
});

### Service
 function getNames(group) {
            var deferred = $q.defer();
            $http.post("api/myUrl", group).then(
                function (response) {
                    deferred.resolve(response.data);
                },
                function (error) {
                    deferred.reject(error);
                }
            );
            return deferred.promise;
        };

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


Add trajectory information

We should make some basic system information very easily accessible. All of this data is already available via different MDAnalysis function and methods, but it would be nice to have them readily accessible.

This was already added during the development of the server.


feat: add stripe authentication support

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

@nhcarrigan, thanks for that.

Thanks @ahmadabdolsaheb, the code looks good.  Try and get the QAing done tomorrow.

Here are the test cards: https://stripe.com/docs/billing/subscriptions/fixed-price#test

In that case, I'm happy to merge this and test on staging.  @nhcarrigan do you want to take a final look?


Export all the json responses from a domain name to a file?

I tried to read the docs as much as I can and read the blogs, still didn't figure out how I can,
export all the Json resonses from a specific domain name to a file (ideally a CSV file so can I anayalze them or put them in a database)

Does http://docs.mitmproxy.org/en/stable/mitmdump.html#filtering-saved-traffic satisfy your needs?

not really, I wanna export the recieved json to a human readable CSV ... that output just writes in a way mitmproxy can read it

If you need a custom output format, I'd recommend to just write an inline script for this: Just open a file in start() and write your csv line in response().
https://github.com/mitmproxy/mitmproxy/blob/master/examples/modify_response_body.py
https://github.com/mitmproxy/mitmproxy/blob/master/examples/filt.py

Thanks for response, so how can I make the script say only do it if it is a json response, for example I dont want to export the JPG or other Non-Json responses to a file?

My previous comment should have you covered how you can use mitmproxy filters :wink:
Apart from that, you can of course check the response object manually. http://docs.mitmproxy.org/en/stable/dev/models.html#netlib.http.Response

thanks I appreciate it, I will study it, is there a way I can get more real-life examples? other than those in the examples folder, any other documents I can study?

There's http://docs.mitmproxy.org/en/stable/scripting/inlinescripts.html, http://docs.mitmproxy.org/en/stable/dev/models.html and the examples in the example folder. Those should cover the mitmproxy-specific parts, everything else should be normal Python.

Where is Slack ?

@medyagh see https://github.com/mitmproxy/mitmproxy/#documentation--help
or just go to http://slack.mitmproxy.org/ to join our Slack channel.


Remove dependency on odo. Optimize categoricals

This PR removes the dependency on odo, addressing #424. Some code was borrowed from odo and placed into utils.py, but optimized to address #396 and be much more performant when handling categorical dtypes.

Looks great.  Ready to merge?

Yes, I believe so @jbednar. Forgot to mention - this PR also gets rid of the dask import warning about get_sync being moved.


cannot find keyword in the chat history

I need to find a keyword, it's usfull especially in a long chat history, but copilot chat panel seams never ever match my keyword against with questions and answers at all.

Yeah, this doesn't work well currently.

This search functionality has been removed. It would be nice to have it back and functional. Maybe some sort of accordion-style history of prompts and responses, too, so that I can easily scan my high-level questions to find a recent question which I know is relevant.


Addition of existing Security groups to EKS cluster

We have modified the stacks according to our requirements to launch worker nodes in private subnets and include boot nodes. Now, we are facing issues in the boot node accessing the EKS cluster API endpoint. We have fixed this by manually adding the security group to EKS by allowing the entire VPC CIDR or allowing the IP of the boot node alone. We need to add this security group within eksctl commands as shown below.
We tried by adding  below values
clusterSecurityGroup="sg-1234567". but failed with association.
Resources:
BootNodeProfile:
Type: AWS::IAM::InstanceProfile
Properties:
Roles:
- !Ref RoleName
Path: /
BootNode:
Type: AWS::EC2::Instance
Metadata:
AWS::CloudFormation::Init:
configSets:
Required:
- StackPropertiesFile
StackPropertiesFile:
commands:
01_create_opt_ibm:
command: mkdir -p /opt/ibm
test: test ! -d /opt/ibm
files:
/opt/ibm/cluster.yaml:
mode: '000755'
owner: root
group: root
content:
!Sub
- |
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
name: ${ClusterName}
region: ${AWS::Region}
vpc:
subnets:
private:
${AZ1}: { id: ${PrivateSubnet1ID} }
${AZ2}: { id: ${PrivateSubnet2ID} }
${AZ3}: { id: ${PrivateSubnet3ID} }
clusterEndpoints:
publicAccess:  true
privateAccess: true
managedNodeGroups:
- name: ng-1-workers
instanceType: m5.large
desiredCapacity: 3
privateNetworking: true
- AZ1: !Ref AvailabilityZone1
AZ2: !Ref AvailabilityZone2
AZ3: !Ref AvailabilityZone3
PrivateSubnet1ID: !Ref PrivateSubnet1ID
PrivateSubnet2ID: !Ref PrivateSubnet2ID
PrivateSubnet3ID: !Ref PrivateSubnet3ID
ClusterName: !Ref EKSClusterName
Thanks,
Murali

The above issue does not appear to be a question/problem relating to the MQ Helm chart. It sounds like you need assistance from AWS to configure you EKS cluster correctly.

Closing as unrelated to MQ Helm and no update.


Fix spec tests failing on weave container running

Could be related to this. https://github.com/docker/docker/issues/14788

closing this in favour of #583


doc updates for release alpha.16

doc updates for release alpha.16

@daxian-dbw Travis CI again is failed on Class parser tests.
The problem always happens after this point , isn't it?
If so then the problem is in Get-RuntimeError
And there is only [scriptblock]::Create - Maybe we have a bug in the C# code?

@iSazonov This is annoying and we have trouble reproducing it locally. It could be a .NET Core bug. We are investigating to generate dump in case of a hang in CI build.

Today I tried unsuccessfully to reproduce this issue on WSL. 😕  We do not make any progress without the dump.

@daxian-dbw I attached a script to get PR list:
$a=Search-PR ([datetime]::Today.AddDays(-5)) ([datetime]::Today.AddDays(-3))
$a | Format-PRforNotes

title                                                 number user         closed_at
-----                                                 ------ ----         ---------
Fix reference to sshd service restarting                3138 SteveL-MSFT  2017-02-13T22:13:13Z
Fix class parsing (issue 3083)                          3103 iSazonov     2017-02-14T00:45:01Z
Approve console cmdlets tests                           3101 iSazonov     2017-02-14T19:00:04Z
Implement RoleDefinitions RoleCapabilityFiles keyword   3067 PaulHigin    2017-02-14T18:42:18Z
Treat unbound command parameters as command arguments   2919 AndrewGaspar 2017-02-14T00:02:57Z

SearchPR.txt

Thanks @iSazonov 😄


NSDocument changes, take #2

This PR is a continuation of #136. It does the just about the bare minimum required to migrate to the NSDocument model, and rolls back some of the broader changes in that PR. (I do, for the record, think those changes were a net positive, but I want to make this PR as single-purpose as possible.)
Some notes:
The more I read docs, the more I suspect that the NSDocument model is the correct model for this application; however there's an argument for making this change more incrementally and more thoughtfully. If this PR looks too messy (and it looks pretty messy to me) I'm happy to start again, and work more incrementally.
In any case, the codebase after this PR is asking for a refactor, and some clarity around separation of responsibilities: There is no clear separation of responsibilities between Document, EditView, and EditViewController. We also no longer have an AppWindowController class, but I suspect we will want one again at some point in the future. Anyway: I would like to have a clearer conceptual model of what code should go where. I think that the EditView should only be responsible for code related to drawing and rendering the view. Any non-drawing code (responder chain/event handling, communicating with the back end) should be handled by the EditViewController. I'm not totally sure right now where the Document fits in, but I haven't read too too deeply into the NSDocument model yet.
I also have some ideas for clearing up all the [String: AnyObject]'s, that's halfway between going fully-static and staying stringy. But that will be a separate PR.
Some issues:

saving / opening needs more work. Save, in particular, is currently always bringing up the 'save as' dialog box.

I haven't implemented the New Tab menu item & associated hotkey, because my first look at this made it seem like I'll need to add back the NSWindowController, and if I do that I would like it to be a separate PR.

the cursor does not blink when a new document opens. (https://github.com/google/xi-editor/issues/161)

I couldn't for the life of me figure out where the initial window size used to be set, and all windows were being created with the minimum size; I added some placeholder code to Document that sets sane (to me) defaults for a new file, although this is pretty sloppy.

tl; dr:
If you're okay with this PR, then I promise to do some cleanup shortly. If you aren't okay with this PR, I still think moving in this direction is probably the right decision (and now is the right time) but I'm happy to do that work more incrementally.

Overall this looks like a good direction. Thanks for making it more focused, and also offering to break it up into even smaller chunks - that was one of the reasons why it took me so long to get to the previous one. But this one doesn't look too overly scary.
Having a separate EditViewController to deal with responder events does seem like it fits into the Cocoa approach.
Let's chat a bit before making too much change on the [String: AnyObject] stuff. I'm certainly happy to hear your ideas on it.
Would you like to merge this PR as-is, and do further cleanup in followups, or refine before merging? As you point out, some functionality is regressing, but it doesn't seem too bad as a temporary situation.

RE: cleanup: my thought was that if this seemed like a direction you were interested in, we could merge this as-is, so that subsequent changes can be in smaller & easier to read PRs, and to avoid big feature branches.
Re: [String: AnyObject]: I appreciate your interest in keeping the flexibility of stringly typing, and I don't have a totally coherent proposal right now, but I'm playing around with some ways to reduce & concentrate the boilerplate. Nothing drastic.
As it sounds like you're approximately okay with this direction, I'll spend a few hours this morning doing some clean-up, with the expectation that that will be a separate PR. Some goals for that:

clear up the relationship between the EditView, the EditViewController, and the Document.
add a menu item for new tab, and figure out a way to intelligently incorporate that into our architecture.
Ensure that whatever choices I make will make it fairly trivial to implement split views, feel like a logical extension of tabs, and something that might be a logical next step for me.
Fix saving. I assume we would like to opt-out of all the built-in autosave etc behaviour?

Sounds great, thanks! Yes, I'd like to opt out of autosave for now, but I'm not opposed to the idea of keeping the state somewhere so that exiting without saving might give the option to restore. However, I feel the need to be extra careful about where potentially sensitive information should be stored. Future work in any case.


Minting 3.0 requirements definition

Minting V3.0 working and requirements.

[ ] Farming rewards 3.0 definition.

TFT earned per month per node =
   ( + CU farmed * CU farming reward
    + SU farmed * SU farming reward
    + NU used * NU farming reward
    + IPAddr used * IPAddr farming reward ) * multiplier

[ ] Formulas to be used are below.  They come  form the calculator and all other publications need to reflect these fomulas.

# CU=min((MRU-1)/4, CRU*2)
# SU=HRU/1200 + (SRU/300)(0.8
# NU=max(measured GB's in, measured GB's out)
# IPAddr = measured amount of hours of IPv4 used

[ ] Rewards at time of writing:

Unit
description
rewards

Compute Unit (CU)
typically 2 vcpu, 4 GB mem, 50 GB storage
51.81 TFT/month

Storage Unit (SU)
typically 1 TB of netto usable storage
32.38 TFT/month

Network Unit (NU)
1 GB of data transferred as used by TFGrid user for Public IP Addr
0.65 TFT/GB

Public IPv4 Address
Public IP Address as used by a TFGrid user
0.11 TFT/hour

[ ]  Certified farming (nodes) get 25% more tokens as a reward

DIY
Certified

multiplier
1
1.25

[ ] TFT value pegged to USD (pricing changes in line with TFT/USD rate).  This is the value number used to calculate how much TFT's a CU/SU/NU/IPv4 gets as a proof of capacity reward.

[ ] current TFT to USD value is 0.05 , calculated on 2021-10-08 05:46:11
[ ] TFT value will be fixed for 1 month
[ ] TFT value will be calculated as an average over the last month.

[ ] Investigate and agree whether a longer period is required to avoid / counter manipulation by token holders.

[ ] Token value information comes from Liquid and coinmarket cap
[ ]  The reward TFT's for CU/SU/NU/IPv4 are locked for 60 months once farming starts for a 3node (first boot & registration to blockchain) or at date of purchase when certified 3node.
[ ] If a farmer decides to keep 3nodes online longer that the 60 month period a new TFT price for CU/SU/NU/IPv4 will be set for new period of 60 months.

[ ] This needs to be done automatically, without (application) service interruption
[ ] Minimal SLA’s need to be achieved before the farming reward can be earned (uptime, bandwidth, latency, …)

[ ] Minimal SLA for Europe is: 99%
[ ] Minimal SLA for North America is: 99%
[ ] Minimal SLA for South America is: ?
[ ] Minimal SLA for Africa is: ?
[ ] Minimal SLA for Australia is: 99%
[ ] Minimal SLA for Asia is: 99%
[ ] Minimal SLA for South East Asia is: ?

[ ] All farming reward tokens are locked.  Tokens are released when 30% of the 3node capacity is being utilized.  This 30% check is done once, once the farmers 3nodes has reached 30% utilization all historic tokens are released and all future farming reward tokens are no longer locked up.
[ ] On TF Grid3.0 all farmers have registered there nodes on the TF Chain (polkadot/substrate).  All farming rewards should be paid to substrate accounts. However there are two options to mint:

[ ] Minting 3.0 remains operational on the Stellar network.
[ ] Minting 3.0 starts on the TF Chain.
[ ] Minting 2.0 stays on the Stellar network and minting 3.0 commences on the TF Chain.

In order to minimize the risk of not being seen as a utility token non of the capacity utilization tokens end of getting in the farmers wallet.  No utilization tokens end up in the farmers wallet.

that's not true: The reward TFT's for CU/SU/NU/IPv4 are locked for 60 months once farming starts for a 3node (first boot & registration to blockchain) or at date of purchase when certified 3node.
TFT minted each month are locked until 30% of the node's capacity are used or after 24 month.

Duplicate of #48?

#48 is not a spec sheet - that a discussion. I meant this to be a spec sheet and spec sheet only.

certified: SLA is 99.5% for datacenter farmers and 97% for home and office farmers diy: suggest 90% details: https://library.threefold.me/info/threefold#/tfgrid/farming/threefold__farming_certified_requirements

Implemented in the top spec list.

that's not true: The reward TFT's for CU/SU/NU/IPv4 are locked for 60 months once farming starts for a 3node (first boot & registration to blockchain) or at date of purchase when certified 3node.
TFT minted each month are locked until 30% of the node's capacity are used or after 24 month.

Implemented comment in top requirements list.


Reopen pull request (update domains)

Hi, I’m sorry I accidentally deleted my repository that so delete my pull request. Fortunately I had a backup here the file edit :
Update remove domains

LMAO - This file only serve to get in the way