FIX: Ensure Net::HTTP socket type is StubSocket.

When running my tests related to opensearch using the searchkick gem I was getting intermittent errors from the Webmock library as seen below. After some debug logging I noticed that StubSocket wasn't always the Net::HTTP.socket_type as expected. This change ensures the socket_type is always StubSocket as opposed to Net::BufferedIO.
https://github.com/ankane/searchkick/issues/1692
ArgumentError: wrong number of arguments (given 0, expected 1)
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:116:in `initialize'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/webmock-3.23.1/lib/webmock/http_lib_adapters/net_http.rb:121:in `new'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/webmock-3.23.1/lib/webmock/http_lib_adapters/net_http.rb:121:in `start_without_connect'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/webmock-3.23.1/lib/webmock/http_lib_adapters/net_http.rb:153:in `start'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/net-http-persistent-4.0.2/lib/net/http/persistent.rb:662:in `start'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/net-http-persistent-4.0.2/lib/net/http/persistent.rb:867:in `reset'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/net-http-persistent-4.0.2/lib/net/http/persistent.rb:604:in `connection_for'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/net-http-persistent-4.0.2/lib/net/http/persistent.rb:892:in `request'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/faraday-net_http_persistent-2.0.2/lib/faraday/adapter/net_http_persistent.rb:68:in `perform_request'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/faraday-net_http-2.1.0/lib/faraday/adapter/net_http.rb:66:in `block in call'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/faraday-2.0.1/lib/faraday/adapter.rb:45:in `connection'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/faraday-net_http-2.1.0/lib/faraday/adapter/net_http.rb:65:in `call'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/faraday_middleware-aws-sigv4-1.0.1/lib/faraday_middleware/request/aws_sigv4.rb:18:in `call'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/searchkick-5.3.1/lib/searchkick/middleware.rb:16:in `call'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/faraday-2.0.1/lib/faraday/rack_builder.rb:153:in `build_response'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/faraday-2.0.1/lib/faraday/connection.rb:445:in `run_request'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/opensearch-ruby-3.4.0/lib/opensearch/transport/transport/http/faraday.rb:56:in `block in perform_request'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/opensearch-ruby-3.4.0/lib/opensearch/transport/transport/base.rb:297:in `perform_request'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/opensearch-ruby-3.4.0/lib/opensearch/transport/transport/http/faraday.rb:45:in `perform_request'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/opensearch-ruby-3.4.0/lib/opensearch/transport/client.rb:191:in `perform_request'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/opensearch-ruby-3.4.0/lib/opensearch.rb:48:in `method_missing'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/opensearch-ruby-3.4.0/lib/opensearch/api/namespace/common.rb:46:in `perform_request'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/opensearch-ruby-3.4.0/lib/opensearch/api/actions/indices/get_alias.rb:64:in `get_alias'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/searchkick-5.3.1/lib/searchkick/index.rb:111:in `all_indices'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/searchkick-5.3.1/lib/searchkick/index.rb:125:in `clean_indices'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/searchkick-5.3.1/lib/searchkick/index.rb:361:in `full_reindex'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/searchkick-5.3.1/lib/searchkick/index.rb:254:in `reindex'
    /Users/miketaylor/.rbenv/versions/3.2.4/lib/ruby/gems/3.2.0/gems/searchkick-5.3.1/lib/searchkick/model.rb:77:in `searchkick_reindex'
    test/integration/graphql/searches_test.rb:18:in `execute'
    test/integration/graphql/searches_test.rb:32:in `block in <class:SearchesTest>'

Getting this error when trying to run tests locally
 /Users/miketaylor/dev/webmock [master]% bundle exec rake test
/Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/async-http-0.74.0/lib/async/http/endpoint.rb:25:in `<class:Endpoint>': uninitialized constant URI::WSS (NameError)

				'wss' => URI::WSS,
				            ^^^^^
	from /Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/async-http-0.74.0/lib/async/http/endpoint.rb:20:in `<module:HTTP>'
	from /Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/async-http-0.74.0/lib/async/http/endpoint.rb:18:in `<module:Async>'
	from /Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/async-http-0.74.0/lib/async/http/endpoint.rb:17:in `<top (required)>'
	from /Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/async-http-0.74.0/lib/async/http/internet.rb:8:in `require_relative'
	from /Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/async-http-0.74.0/lib/async/http/internet.rb:8:in `<top (required)>'
	from /Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/async-http-0.74.0/lib/async/http.rb:11:in `require_relative'
	from /Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/async-http-0.74.0/lib/async/http.rb:11:in `<top (required)>'
	from /Users/miketaylor/dev/webmock/lib/webmock/http_lib_adapters/async_http_client_adapter.rb:5:in `require'
	from /Users/miketaylor/dev/webmock/lib/webmock/http_lib_adapters/async_http_client_adapter.rb:5:in `<top (required)>'
	from /Users/miketaylor/dev/webmock/lib/webmock.rb:59:in `require_relative'
	from /Users/miketaylor/dev/webmock/lib/webmock.rb:59:in `<top (required)>'
	from /Users/miketaylor/dev/webmock/lib/webmock/test_unit.rb:4:in `require'
	from /Users/miketaylor/dev/webmock/lib/webmock/test_unit.rb:4:in `<top (required)>'
	from /Users/miketaylor/dev/webmock/test/test_helper.rb:6:in `require'
	from /Users/miketaylor/dev/webmock/test/test_helper.rb:6:in `<top (required)>'
	from /Users/miketaylor/dev/webmock/test/test_webmock.rb:1:in `require'
	from /Users/miketaylor/dev/webmock/test/test_webmock.rb:1:in `<top (required)>'
	from /Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/rake-13.2.1/lib/rake/rake_test_loader.rb:21:in `require'
	from /Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/rake-13.2.1/lib/rake/rake_test_loader.rb:21:in `block in <main>'
	from /Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/rake-13.2.1/lib/rake/rake_test_loader.rb:6:in `select'
	from /Users/miketaylor/.rbenv/versions/3.1.3/lib/ruby/gems/3.1.0/gems/rake-13.2.1/lib/rake/rake_test_loader.rb:6:in `<main>'
rake aborted!
Command failed with status (1)
/Users/miketaylor/.rbenv/versions/3.1.3/bin/bundle:25:in `load'
/Users/miketaylor/.rbenv/versions/3.1.3/bin/bundle:25:in `<main>'
Tasks: TOP => test
(See full trace by running task with --trace)

@sealabcore  Thank you for your work on this PR. I've noticed that while the tests in master are now passing, there aren't any new tests associated with this specific change. Could you please provide some context on why this particular modification is necessary?
I'm especially interested in understanding the rationale behind assigning @socket to be StubSocket only when it's an instance of Net::BufferedIO.
Given the lack of new tests, could you explain how we can be confident that this change works as intended and doesn't introduce any regressions? Perhaps you could suggest some test cases that would effectively validate this new behavior?


Admin Settings - *Notification Method

I see no options displayed in the Notification method field when I select the dropdown. I've tried typing in Email, push, etc. but nothing seems to take.
Have I missed a step earlier in the process? How do I get around this?
Many thanks for the assistance

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6836ad5a-2de5-6223-0514-62c83ac38d17
Version Independent ID: 8cf9565e-4998-bce4-b319-fedb7e9d835b
Content: Crisis communication app - sample template - PowerApps
Content Source: powerapps-docs/maker/canvas-apps/sample-crisis-communication-app.md
Service: powerapps
GitHub Login: @matthewbolanos
Microsoft Alias: mabolan

I also have this issue

@smolcykr @Jeffj124 ,
Have you removed the SharePoint connectors in the admin app and added your own? It comes with the existing SharePoint connectors from the exported package by default.

Thank you for reaching out. We are reviewing your feedback.

Hi @smolcykr @Jeffj124 @a-britten,
I'm investigating this issue, but am not able to replicate. We've only made two changes to the admin app since we created it:

Removed unused fields in the forms
Made PreferredSentNotification a required field in the form.

And the DeployLists flow has not been modified.
Can you help me check some settings on your end?

Confirm the SharePoint column for PreferredSentNotification indeed has the expected options. You can follow these steps:

Go to your SharePoint site where your lists were deployed using the DeployLists flow. (e.g. https://contoso.sharepoint.com/sites/CrisisComms)
In the left pane click Site Contents
Open CI_configAdminSetup
At the top right, click the settings icon > List settings
Scroll down to the list of columns. Click PreferredSentNotification. It should look like this with the 3 options (email, Teams notification, Push notification):

Q1: Let me know what you see

Check that Items property of the combo box is pointing to the right table. Follow these steps:

Import the admin app (if it's not already imported).
Remove the existing connections to SharePoint. Add your own.
Run the App's OnStart actions now. Hover over the App object in the tree view, click its ellipsis and Run OnStart:

Go to the screen for Admin settings.
Click the combo box for the PreferredSentNotification.
In the top left, change the property dropdown menu to the Items property of the combo box. Provided you have not made any changes, it should be pointing to:
<EMAIL_ADDRESS>Select and hover over the formula to see a preview of its items. It should look like this:

Q2: Let me know what your combo box shows.

Thank you Brian
Yesterday I started fresh - but with one small change - I published both apps before trying to use the drop down. This time it worked.
In my initial try I had saved both apps but had not published either when I tried to use the drop down.
Thank you so much for your reply
Sent from Yahoo Mail for iPhone
On Saturday, March 14, 2020, 5:25 AM, Brian Dang<EMAIL_ADDRESS>wrote:
Hi @smolcykr @Jeffj124 @a-britten,
I'm investigating this issue, but am not able to replicate. We've only made two changes to the admin app since we created it:

Removed unused fields in the forms
Made PreferredSentNotification a required field in the form.

And the DeployLists flow has not been modified.
Can you help me check some settings on your end?

Confirm the SharePoint column for PreferredSentNotification indeed has the expected options. You can follow these steps:

Go to your SharePoint site where your lists were deployed using the DeployLists flow. (e.g. https://contoso.sharepoint.com/sites/CrisisComms)

In the left pane click Site Contents

Open CI_configAdminSetup

At the top right, click the settings icon > List settings

Scroll down to the list of columns. Click PreferredSentNotification. It should look like this with the 3 options (email, Teams notification, Push notification):

Q1: Let me know what you see

Check that Items property of the combo box is pointing to the right table. Follow these steps:

Import the admin app (if it's not already imported).

Remove the existing connections to SharePoint. Add your own.

Run the App's OnStart actions now. Hover over the App object in the tree view, click its ellipsis and Run OnStart:

Go to the screen for Admin settings.

Click the combo box for the PreferredSentNotification.

In the top left, change the property dropdown menu to the Items property of the combo box. Provided you have not made any changes, it should be pointing to:
<EMAIL_ADDRESS>

Select and hover over the formula to see a preview of its items. It should look like this:

Q2: Let me know what your combo box shows.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I came to the same solution @smolcykr did, it was because I hadn't published the apps. Once I did that, things seemed to start working properly.


Add P3PageCopy to docs.phundament.com class reference

http://docs.phundament.com/3.0/package-p3pages.models.html

Gladly, but how? ^^

Here maybe https://github.com/phundament/app/blob/3.0/docs/guide/Pages.md


[HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [HOLD for payment 2024-06-11] [HOLD for payment 2024-06-06] Distance rates - Default rate input is 0 instead of actual amount for newly created WS

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.77-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:

Go to staging.new.expensify.com
Go offline.
Create a new workspace.

Enable Distance rates.
Go to Distance rates.
Click on the default rate.
Click Rate.

Expected Result:
The rate amount input will display the actual amount (production behavior).
Actual Result:
The rate amount input displays 0 instead of the actual amount.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/2aadb164-0531-485f-a62d-0bd561aed3ae

View all open jobs on GitHub
Issue OwnerCurrent Issue Owner: @JmillsExpensify

@JmillsExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

For the default rate 0.655, the updated version of the function calculateAmountLength() returns ... 11, whereas for the rate 0.670 coming from the API when you're online, it returns 3.
validateAmount() is called with amountMaxLength: 10, which is why the function is returning false when you're offline.

@francoisl If this is a blocker that needs to be handled asap then I'd suggest the revert since the code changes of the PR are minimal, then @bernhardoj won't be time constrained to re-work the solution.
Otherwise I'd wait for their input and possible follow-up fix.

Fixed in the version 77-3
https://github.com/Expensify/App/assets/43996225/9dec6bcf-b6d1-4c59-a95f-5a3ba89f7f91

@francoisl correctly pointed out the root cause, it's the old regex here.
https://github.com/Expensify/App/blob/f6aa6c20a18e2d64f3143815f5266d064ce7cb6a/src/libs/MoneyRequestUtils.ts#L48-L50
The calculation that we did is already correct, but the regex above matches the decimal separator (.) because 0.655 is 65.5 cents which still contains a dot.
The regex above is added in this PR to prevent NaN, Infinity, and number with scientific notation (1+e26). So, I updated the regex to be more specific.
A new PR is here

The final fix for this was just merged. This was for a regression that was originally handled internally, and then the author and C+ from the initial PR fixed it, so I believe no payment is required.

Checklist already completed above and no payments required, closing.


deploy failed

[Enter feedback here]
is the template still valid ? tried deploying it as is but deployment failed with error downloading zip file, changed the zip download link to the direct download link, but the deployed function wouldn't scale the sql database as expected

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 228988d8-beaf-9bb1-efae-c2c25130b525
Version Independent ID: 8c714c20-60f3-dd75-5ba9-a66d17410685
Content: Tutorial: Manage compute with Azure Functions - Azure Synapse Analytics
Content Source: articles/synapse-analytics/sql-data-warehouse/manage-compute-with-azure-functions.md
Service: synapse-analytics
Sub-service: sql-dw
GitHub Login: @julieMSFT
Microsoft Alias: jrasnick

Thanks for the feedback! We will review and get back to you shortly.

I confirmed the template isn't working. I have assigned the issue to the doc author to update appropriately.

Hi @matt1883 can you help direct this to the right person who can take a look at this?

#assign:liudan66

Hi @julieMSFT i am not the author for this part, can you help route it to the right person

#reassign:ronortloff

Hi @Adi-Nugraha-T
Regarding "the deployed function wouldn't scale the sql database as expected" could you confirm this was run against a Dedicated SQL pool (formerly SQL DW), not a Synapse Dedicated SQL pool.

Closing with no response from the person filing this.

#please-close


didn't work in untiiy 5.6.1f 64bit.

Hi, I found it didn't work in untiiy 5.6.1f 64bit. :) . the design is awesome.!. Holp fix it in the newest version.:)

it seems strange that i run the example even i check that the code had derived from monobehavior

@midGitub Okay -- if all is well, please also close this issue.


Add SugarSS

Hi,
we are using Plyr in our project, but we are using SugarSS for  CSS.
What do you think about add it to the dist?  I can do PR if you agreed

I'd be hesitant at this stage as I already have to maintain both SASS and LESS separately so whenever I make a change to the LESS (primary), I have to remember to retro-fit it to the SASS and this would just add to that workload. How popular is SugarSS?

It is like SASS or Stylus syntax but for PostCSS.


CLI or script for event extraction debugging

Summary
cc @romac
We currently use very rough tools to triage issues that involve packet data extraction. In the most recent example, on the ICS incentivized testnet, we needed to understand the cause of packets being stuck due to hermes not finding the packet data.

Problem Definition

Proposal
It would be very nice to have a CLI or script that:

takes an RPC endpoint, a packet query and maybe a height
retrieves the IBC events that match the query, maybe from the block results at the exact height
displays the event attributes in a human readable form

Ideally this should not use hermes code but rather the RPC endpoints directly. But it could, at least initially, be part of the hermes repo (maybe in tools).

Acceptance Criteria

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

I have pretty much exactly this in a branch, will add support for the height and open a PR.


r36s support?

Does it work with the R36S console by any chance? i don't see a build for it.

there's a build for r36s but I haven't released it yet. I'll upload soon

@haoict Any updates?

@SlyBouhafs
sorry for the delay. I uploaded the binary here: https://github.com/haoict/SimpleTerminal/releases/tag/1.4.0
let me know if it works


Support multiple versions of a given stack/sample in a given registry

Which area this feature is related to?
/area registry
Which functionality do you think we should add?
In order to provide better parent adoption, we need to start supporting multiple versions of devfile to be stored in a given registry so that the user can refer to a specific version of a parent devfile.
Why is this needed? Is your feature request related to a problem?
As a new version of devfile specification, e.g. devfile 2.2, gets introduced, stack providers may want to provide different versions of a stack to provide support based on different devfile specifications. This is important since different tools/stacks will move up to a new devfile specification support at a different pace. It will be helpful for transitioning to a newer version of the specification without causing breakage to existing tools.
Detailed description:
Describe the solution you'd like
More investigation is required to provide multiple versions of the same devfile in a registry. The area of consideration should include:

Structure the source repository on how a stack can provide different versions of the same stack/devfile
How the registry REST API, Go library allows clients to filter the specific version(s) of the devfile, e.g. only devfile 2.1 and 2.2, when querying the list of devfile the registry
Any potential new metadata needed on the index.json
How it affects the registry build
What infrastructure/API does tools need to support multiple devfile versions
How do we represent different versions in the devfile registry viewer
Stretch: take into consideration supporting devfiles of the same stack that uses different base images when designing this feature (see https://github.com/devfile/api/issues/674 for details)

Describe alternatives you've considered
Use different registries to store devfiles using different devfile specification versions. This approach means we have to maintain multiple registries at the same time and the user will need to know different URLs for the registry access as well as the registry viewer.
Additional context

proposal on index and stack/samples repository change: https://docs.google.com/document/d/1nqsK83EQLwd5CpAuAF9MEc7QC-3ONG4pVCP8OuMt4qY/edit?usp=sharing

Issues created to track the progress:

[ ] Registry Generator Change: #761
[ ] Registry Server Change: #762
[ ] Registry Library Change: #763
[ ] Devfile API Spec Change: #764
[ ] Devfile Library Change: #765

closing this issue, as the implementation is done.
for registry viewer change need to be done, see https://github.com/devfile/api/issues/811
for docs change need to be done, see https://github.com/devfile/api/issues/810
for enhancement on supporting particular stack versions from outside repos, see https://github.com/devfile/api/issues/788


Remove field @Inject in package com.speedment.tool.core.internal.controller

There are other packages too where this should be done, e.g. com.speedment.tool.propertyeditor.editor


Start optimizing designs of conditional generation tasks (done)

Currently, the code for MT and summarization are entangled. This PR tries to reasonably decouple them
As a byproduct,  following function can been further generalized: https://github.com/neulab/ExplainaBoard/blob/9a51252bf9970c207a965959856d45caef5de2f4/explainaboard/processors/conditional_generation.py#L108

LGTM. There's some dead code commented out instead of deleted, but we can fix that later given that #147 is dependent on this PR.


File transfer API

Is it already migrated to GAP 7.0.0?

Is it already migrated to GAP 7.0.0?

yep


update getBoxesWithUnspentTokens for addresses

Events include tokens, and ergs/sigusd and need to be kept separate. However, running multiple events with different wallets requires multiple nodes. To solve this, derived addresses may be used, however boxes are not allowed to co-mingle.
This will also require that ergopad control funds on primary node and additional coding may be required in the event this doesn't work. Until then, a single node can be used to handle multiple events with this model.

[ ] include addresses in parameters
[ ] default to ergopad address
[ ] implement sql solution due to performance from explorer api

https://github.com/ergo-pad/ergopad-api/tree/getUnspentBoxesByTokenId


VipsIcc: Couldn't link the profiles error in version 0.32.5+

Possible bug
Is this a possible bug in a feature of sharp, unrelated to installation?

[x] Running npm install sharp completes without error.
[x] Running node -e "require('sharp')" completes without error.

If you cannot confirm both of these, please open an installation issue instead.
Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of sharp that is not the latest, please open an issue against that package instead.
What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
  System:
    OS: macOS 13.4.1
    CPU: (12) arm64 Apple M2 Max
    Memory: 1.86 GB / 96.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node
  npmPackages:
    sharp: ^0.33.0 => 0.33.0

What are the steps to reproduce?
Try to do any conversion using withMetadata() on the image will result in VipsIcc: Couldn't link the profiles error
I've tracked the issue down to 0.32.5, versions below works fine.
What is the expected behaviour?
That it succeeds without error
Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this problem
const sharp = require('sharp');
sharp('1.jpg').withMetadata().toFile('out.jpg').catch(console.error);

Please provide sample image(s) that help explain this problem

The ICC profile embedded in this image is invalid as the PCS illuminant does not have the standard/required value of 50. Inspecting the binary data suggests the value might be 0xd32c, which doesn't look right at all. The description is "AppleVision 1710 - 9300", which suggests this profile is probably around 25 years old.
I suspect a recent improvement in the underlying lcms2 is preventing the use of this profile, and you can use the ignoreIcc constructor option to do just that.
sharp('1.jpg', { ignoreIcc: true })...

Since I discovered this while using a global custom build of vips I initially thought this was related to the version of lcms2 I used, however using same global vips build for sharp 0.32.4 it works, which make me think the change seems to come from sharp.
Did not know of ignoreIcc guess i could use that to work around it. Thank you.

Thanks, this probably relates to commit https://github.com/lovell/sharp/commit/bb7469b2d170831c1e9c23ba945166d0b4a14e23
Perhaps sharp should silently ignore the invalid profile, although the output might then be incorrect. Are you able to grant permission for me to add this image to sharp's test corpus if so?
If you're using v0.33.0, you might want to use the new withIccProfile() instead of withMetadata() for more fine-grained control over output profile.
https://sharp.pixelplumbing.com/api-output#withiccprofile

Perhaps sharp should silently ignore the invalid profile, although the output might then be incorrect

In my case that would be great!

Are you able to grant permission for me to add this image to sharp's test corpus if so?

That specific image i don't own the rights to. However I've produced a similar image with the same issue which you are free to use

If you're using v0.33.0, you might want to use the new withIccProfile() instead of withMetadata() for more fine-grained control over output profile.

Thank you for pointing this out, thats a great addition.

v0.33.1 now available with this enhancement.


Ticket/1.6.x/1346 facter i paddress

Added condition to look for ip, if not available then default to ifconfig on linux.

Did you even test this?  It not only doesn't work, it could never possibly work.


Raspberry Pi 4 Support

Is this supported on the Raspberry Pi 4? I have not been able to get it to work. Maybe I am missing something.

Yes, in fact it should specifically work only in the pi4. What's the problem?

Thank you for your reply! I have been able to get it to output through the Matrix Bonnet but can not get it to display correctly on the LED Panel. I have tried three different panels. 32x32, 32x64 and 64x64. Just single panels, I have not done any chaining yet. My end goal is to use the 64x64 panel. I think the configuration for the type of panel is wrong but I am not sure where to change those settings. Is that the dpi_output_format or something else?

On Sep 4, 2021, at 2:17 AM, sharky5102 @.***> wrote:
Yes, in fact it should specifically work only in the pi4. What's the problem?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/sharky5102/fbmatrix/issues/3#issuecomment-912925378, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI7YONCK55HJT3FXP2X53XTUAHBZBANCNFSM5DMZCISA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Avoid having an ng-if if mutiple:

https://github.com/angular-ui/ui-select/issues/217 - Is there any way to change multiple selection mode at the run time?
Instead of the accessor (in case something needs to be modified) - how about this:

      {{$select.match.fields[espLookupCtrl.displaycolumn]}}

Closing due to age - feel free to open a new PR against current master if this is still an issue.


Add SPF record to Website.

Add SPF record to Website.

I think this should fail because there will be existing TXT records ... it would be nice if there were a sensible way to merge them.


feat: Reset timer on change

What's here

Ignored yarn.lock
Added JS Doc for the function
Resetting timer on change
Pretty code

Few issues, was my code itself, gonna merge this PR and then commit changes,
Good work!


List characters not visible

When I run :set list list characters are not visible.  Switching to almost any other color scheme allows me to see them.
Relevant info:
Terminal vim 7.4.898 on OS/X
set listchars=tab:→\ ,eol:⤦,trail:·,extends:↷,precedes:↶

I do not like the ~ at the bottom of files. You can enable the highlight by the following config.
highlight NonText ctermfg={your favorite colour}


check if attribute exists before running migration script

more details here https://github.com/concrete5/concrete5/issues/5620#issuecomment-311342813
an attribute can always be deleted in concrete5, even if it's used by the core. Since this can happen I'd propose that we skip them in this context too to ensure that the update runs without any problems.

I think that a few lines are missing for https://github.com/concrete5/concrete5/pull/5623/files#diff-e94e6a941225b4e60d7c8a7e38275969: we define $availableAttributes but it's never used

@mlocati thanks, you're of course right. That migration didn't get executed again after it failed on my first attempt, that's why it slipped through my test.


Certificate issued but application doesnt update from fake cert on azzure cluster

Im using kubernetes v1.17.11 , cert-manager v1.0.2 and letsencrypt in an azzure cluster.
Ive tested the deploy using https://cert-manager.io/docs/installation/kubernetes/#verifying-the-installation
Although I can see the certificates being issued successfully the certificates, the applications still display kubernetes fake certificates.
The expected behaviour is for the applications (grafana and kiali) to have the letsencrypt certificates displayed.

/triage support
can you get us a bit more info? Like the configuration used to get the certificates? Have you went through the troubleshooting guide?

@meyskens I was using the wrong service, sorry about opening this.


leftwm: 0.4.2 -> 0.5.0

Diff: https://github.com/leftwm/leftwm/compare/0.4.2...0.5.0
Changelog: https://github.com/leftwm/leftwm/blob/0.5.0/CHANGELOG
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Version is reported incorrectly as 0.4.2 still. Reported upstream https://github.com/leftwm/leftwm/issues/1177

Hi, thanks for being so quick. I was also preparing a PR as I wanted to add myself as a package maintainer, if you like you could add me (using vuimuich).
Also I thought of changing sha256 to hash and cargoSha256 to cargoHash as this seems to be the preferred way, when the hash string is in form of sha256-.. and I wanted to install the man page that can be found in leftwm/doc/leftwm.1 but for some reason I got eval issues in local builds and hadn't yet time to sort things out.

@VuiMuich I addressed most of your suggestions. I'll leave updating maintainers to you though. :)

@VuiMuich I addressed most of your suggestions. I'll leave updating maintainers to you though. :)

Nice! Thanks.
Just one thing, to keep it in sync with the main release (see upstream issue report leftwm/leftwm#1177) I'd suggest to do directly 0.4.2 -> 0.5.1

Looks good now @VuiMuich !

Thanks! Thes PR here looks good to me as well now.


Observations I've Already IDed Showing Up in ID Please

I've noticed that observations that I long ago identified as "dicots" are showing up in my ID Please:

This is how they loaded, I didn't add the ID today.
i IDed them as Dicots long ago because they were not tagged to any species but I didn't know what they were. I think anything I did that with should be marked as reviewed. Yes it was a while ago and one or two of them perhaps I could figure out now but with 900 pages of plants to review in CA and 300 in Vermont, it seems more worth my time to look at ones I haven't seen yet.
I'm thinking maybe it's a bug, right?

I wonder if this is at all related to #643 where an observation that isn't attached to iNat taxonomy doesn't show any IDs in table view even if it has one (from someone other than the original observer).

oh, there was also that weird bug where there was a taxon swap with
'dicots' that created a bunch of multiple IDs from people... this could be
related to that too, or both. I think it's a bug rather than a feature.
They should be tagging as already IDed by me but for some reason they
aren't.
Not a huge bother to me right now, but probably worth fixing if a bug.
Here's the URL since I forgot to include it earlier, but of course it will
look different for you because you don't have the same 'reviewed' as me.
http://www.inaturalist.org/observations/id_please?captive=&created_on=&d1=&d2=&day=&filters_open=true&hrank=&iconic_taxa[]=Plantae&iconic_taxa[]=unknown&identifications=any&list_id=&lrank=&month=&nelat=&nelng=&order=desc&order_by=observations.id&page=909&place_id=51727&q=&quality_grade=needs_id&rank=&reviewed=false&search_on=&site=&swlat=&swlng=&taxon_id=&taxon_ids[]=&taxon_name=&tdate=&utf8=✓&view=&year=
On Sun, Feb 21, 2016 at 9:33 PM, carrieseltzer<EMAIL_ADDRESS>wrote:

I wonder if this is at all related to #643
https://github.com/inaturalist/inaturalist/issues/643 where an
observation that isn't attached to iNat taxonomy doesn't show any IDs in
table view even if it has one (from someone other than the original
observer).
—
Reply to this email directly or view it on GitHub
https://github.com/inaturalist/inaturalist/issues/892#issuecomment-186973808
.

--
Charlie Hohn
Montpelier, Vermont


Keyboard shortcuts (ala superhuman)

On mouseover, the following keyboard shortcuts could be available:
D = Done (if not done), or clear Done if it was
Hold D = Doing
A = Assign (user or team tab is available)
S = Sprint (or could be story view, or ability to schedule and picks days or sprints (for epics)... could also be for sizing an issue.
M = Milestones or Move (alternate for sprints)... could make sense as you scroll through with JK
Q = Quarter?
E = Epic (could let you type in an epic)
# = Could alternately be epic if we associate epics with hashtags
W = Could give weekly view so we can pick days
C = Create new issue? (alternately, could open chat / conversation)
N = Create new issue
R = Could be reload or refresh or resort if things have changed
R = Requests tab
I = Inbox... which could be same as requests tab
T = Switch team (get a list, can type the team name)
. OR ; = Show menu (equivalent of ...)
J/K = up and down in the list
L = ?  (would be a good key to use since it's home row), could be later.. or List of options... or it could let us apply Labels
F - Find (could also be future, used to move to Future milestone)... or Functions (for a menu... kind of a stretch).  Let's you search.
1 = P1
2 = P2
3 = P3
4 = P4
0 = P0
Could also have P key pressed first (optional)... or P can bring up the menu... which would offer the ability to de-assign priority

This issue is close by PR #21


Add all_data_files, all_manifests, and all_entries metadata tables

This adds 3 new metadata tables and tests:

all_data_files lists all data files in a table that are accessible from any valid (not expired) snapshot
all_entries lists all manifest entries in a table that are accessible from any valid snapshot
all_manifests lists all manifest files in a table that are accessible from any valid snapshot

These tables may contain duplicate rows. Deduplication can't be done through the current scan interface unless all of the work is done during scan planning on a single node. Duplicates are the trade-off for being able to process the metadata in parallel for large tables.
Use cases
We recently added the all_data_files and all_manifests tables to enable building services that manage data files. For example, a janitor service that cleans up orphaned or dangling data files needs to be able to list all valid files in a table. Along with the snapshots table that has manifest list locations, all_manifests and all_data_files enable listing all data and metadata files referenced by a table.
We use the all_entries table to detect the last modified time of partitions. This requires knowing when a file was appended or overwritten and requires ignoring later rewrites:
SELECT
    max(s.committed_at) as last_updated_at,
    e.data_file.partition.*
FROM db.table.all_entries e
JOIN db.table.snapshots s
  ON e.snapshot_id = s.snapshot_id
WHERE e.status = 1 AND s.operation IN ('append', 'overwrite')
GROUP BY e.data_file.partition

Thanks for the review, @danielcweeks! I'm merging this now that tests are passing after resolving the conflict.


BTCMarkets - Add Websocket / Streaming events trade and ticker

Added support for the trade and ticker events/message types
Updated the existing logic to support adding multiple message types as needed rather than a creating a new subscription with all channels every time by adding support for the addSubsription and removeSubscription messages and a rework of the subscribed channel tracking (more work can be done here to provide a more robust tracking mechanism like subscripting to heartbeat first using a block/wait approach until it is sucessfull) (will be included in next iteration).
Future iterations of changes from me will include:

support for orderbookUpdate, error orderChange and fundChange events
The orderbookUpdate event will require a locally managed order book and wil be included once implemented.

I made some comments on stuff that wasn't addressed but this is almost ready to merge

I made some comments on stuff that wasn't addressed but this is almost ready to merge

Hi Erick,
Updates was made this week. Will get them up there very soon.
Christiaan
On Thu, 28 Jan 2021 at 02:22, Erick Arce<EMAIL_ADDRESS>wrote:

I made some comments on stuff that wasn't addressed but this is almost
ready to merge
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/knowm/XChange/pull/3888#issuecomment-768359624, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACVEMQAGQKEEY2RWOAH2NHLS4AVUZANCNFSM4WFVJY4A
.

--
Christiaan du Plessis
M:   +61 (0)4 1202 5876
Please consider the environment before printing this email
NOTICE
This email and any attachments are confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.

Hi Erick,
Updates was made this week. Will get them up there very soon.
Christiaan
On Thu, 28 Jan 2021 at 02:22, Erick Arce<EMAIL_ADDRESS>wrote:

I made some comments on stuff that wasn't addressed but this is almost
ready to merge
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/knowm/XChange/pull/3888#issuecomment-768359624, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACVEMQAGQKEEY2RWOAH2NHLS4AVUZANCNFSM4WFVJY4A
.

--
Christiaan du Plessis
M:   +61 (0)4 1202 5876
Please consider the environment before printing this email
NOTICE
This email and any attachments are confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.

@duplessisc how far along are you with this?

One of the tests failed

Test is still failing, please run locally and make sure it works

Hi Erick,
I saw this, my intent was not to publish this as part of the current pull
request. Will look into the failed test as well.
Christiaan
On Wed, 3 Mar 2021 at 02:32, Erick Arce<EMAIL_ADDRESS>wrote:

One of the tests failed
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/knowm/XChange/pull/3888#issuecomment-788994854, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACVEMQFC5GDIBDCSKXZARCDTBUAKBANCNFSM4WFVJY4A
.

--
Christiaan du Plessis
M:   +61 (0)4 1202 5876
Please consider the environment before printing this email
NOTICE
This email and any attachments are confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.


Create prometheus metrics endpoint to report latency and gas usage

Description
Create prometheus metrics endpoint on the backend API to report latency and gas usage over the last hour (TBD). This endpoint can return metrics which are external to the Polymer chain.
Reasoning
We want to be able to track these external metrics in addition to on-chain IBC metrics for KPI and usage tracking.
Acceptance Criteria

Ensure that the /metrics endpoint returns latency and gas usage metrics matching the existing ibc-explorer metrics page and is consumable by Prometheus and available in grafana/gcp monitoring

@dshiell PR to review

Deployed verified contracts, need to finish investigation. Currently not working as expected.

Can be accessed at https://explorer.stg.testnet.polymer.zone/metrics and https://explorer.prod.testnet.polymer.zone/metrics


UHF-7334: Support for OPENING_HOUR_OBJECT connections

Codecov Report

Merging #141 (4b067b6) into main (e2f8518) will increase coverage by 74.72%.
The diff coverage is 91.66%.

:exclamation: Current head 4b067b6 differs from pull request most recent head 192ea66. Consider uploading reports for the commit 192ea66 to get more accurate results

@@             Coverage Diff             @@
##             main     #141       +/-   ##
===========================================
+ Coverage        0   74.72%   +74.72%
- Complexity      0      342      +342
===========================================
  Files           0       46       +46
  Lines           0     2623     +2623
===========================================
+ Hits            0     1960     +1960
- Misses          0      663      +663

Impacted Files
Coverage Δ

src/Field/Connection/Repository.php
85.71% <ø> (ø)

...lugin/Field/FieldFormatter/ConnectionFormatter.php
0.00% <0.00%> (ø)

src/Field/Connection/OpeningHourBase.php
91.66% <91.66%> (ø)

src/Entity/Unit.php
84.44% <100.00%> (ø)

src/Plugin/migrate/process/ArrayElementEquals.php
81.25% <100.00%> (ø)

... and 41 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


KAFKA-15942: Implement ConsumerInterceptors in the async consumer

We need to make sure to call the consumer interceptor and test its integration.
This is adding the required call in commitSync and commitAsync. The calls in commitAsync are executed using the same mechanism as commit callbacks, to ensure that we are calling the interceptors from a single thread, as is intended in the original KIP.
This is a stacked PR. Only review the last commit.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@philipnee could you take a look please?

hi @lucasbru - i think we might need to loosen the thread access restriction for the interceptor because i think we also need to trigger interceptors during autocommit.  There are 2 ways to achieve this:

pass an event to the main thread to execute the interceptor on poll: the interceptor might never get triggered
loosen the thread access restriction - I think we might need to do that to guarantee the interceptors can always be invoked

#2 is a bit annoying because it against the contract as you mentioned in one of the comment.  What do you think?

@philipnee Good point about auto-commits, I missed that. It's a pity that auto-commits aren't triggered from the main thread (I wonder if we could do that? Would be another architectural change).
I would go for solution num 1 because

Original KIP clearly states that it should only call into the interceptor from a single thread, so I think we'd easily break code if we start requiring them to be thread-safe. Yeah, you could write a KIP, but not sure if that's reasonable here.
When would we not trigger the interceptor in this case? If you are talking about Consumer.close(), could we make sure to empty the background event queue after closing the background thread, and then run the invoker?

Wdyt?

hi @lucasbru - thanks.  i personally prefer to make consumer interceptor thread safe because firstly, (i think) it simplifies the code quite a bit and secondly, it is possible to miss the interceptor invocation if user fail to poll/close after a commit is sent. latter is a bigger problem i think.  do you have an idea of how to fix this?
When would we not trigger the interceptor in this case? i think we always want to trigger onCommit interceptor if provided. so I think after sending the last commit sync on close, we just need to clear the queue, close the network thread, and invoke the callbacks.

@philipnee some considerations:

Does the old consumer guarantee that the interceptor is called when poll or close are not called by the consumer anymore after an autocommit? I don't think so, because it's running as part of the application thread, so how would it provide that guarantee without even being called?
I think the interceptor is meant for monitoring / metrics -- it doesn't have the strict requirements as, for example, an ongoing commit shouldn't be dropped during close because it will result in data loss or duplicate processing.

"Make the consumer interceptor thread-safe" -- How would we even do that? Consumer intereceptors are implemented by the user, we cannot make them thread safe by just putting a lock on it. The only way would be to write a KIP, have a breaking change and a migration guide, and ask all users to upgrade their code. Not sure that is worth it, given the original consumer does not seem to provide the guarantee that you are asking for.
I think the best we can do is to insert the interceptor callback into the invoker queue upon commit completion, and make sure during close to execute all commit callbacks that are enqueued, no? If the user fails to call close, we are out of luck anyways.

The javadoc for ConsumerInterceptor says "ConsumerInterceptor callbacks are called from the same thread that invokes KafkaConsumer.poll(java.time.Duration)". As a result, it is quite clear what needs to happen here without a new KIP.

In terms of implementation of the autocommit-interceptor in the application thread, I see three options:

Move auto-commit triggering to application thread. That seems cleanest to me (all commits are triggered from the application thread), but it's the largest refactoring. Then the interceptor is trivial.
Share the Invoker queue with the background thread, and access it when we register the auto-commit callback. It's already shared with the background thread implicitly as part of the commitrequest completed future.
Add a new background event in the background event queue. Seems unclean, since we already have a common datastructure shared between application & background thread for things to be invoked after a commit, and that is the "Invoker" (option 2).

My take would be option 2, using the invoker in the background thread and submitting a task for the interceptor. Seems like a clean way, re-using the mechanism of the invoker already in place, and without doing any major refactoring.
I would definitely leave the auto-commit logic in the background thread where it is, as it's truly an internal operation/request we want to perform without any direct relation with the app layer, needed from multiple places in the background even: auto-commit on the interval, but also auto-commit as part of the reconciliation process.

I agree with @lianetm that the second option seems best. The invoker mechanism already exists for commitAsync() and submitting to the invoker is already using a thread-safe object.

hey @lucasbru - i assume invoker queue here you meant by OffsetCommitCallbackInvoker.  It is not shared with the background thread.  There are two invokers used by the async consumer, one is the offset commit callback invoker, the other one is the rebalance callback.   The rebalance callback is shared by the two threads but the commit callback invoker is not.
my original thought was to use the background event to pass the interceptor onCommit event.
i think we are all on the same page about using the invoker to invoke the events.

I have updated the PR to run interceptors during auto-commits as well. Let me know what you think

This PR looks about ready to merge. Please can you change PlaintextConsumerTest to run the tests for interceptors with the new consumer. They should pass once this PR is merged.

The auto-commit one still fails, I debugged the problem and create a separate ticket (solution is clear, but we want to have this as a separate PR for potential backporting). The others are enabled.

@cadonna Can you please review this?

@cadonna The autoCommitIntercept test is flaky after this PR, but it's unrelated to this PR. I will create a separate ticket and disable it agian once your comments come in.

Test failures are unrelated


The space bar does not work in comment and don't show flag

until today everything worked fine. But today, when I write a comment under the video and hit the space bar, then it isn't working, and turn on the video.
Ceased to seem the flags of the countries in comments

i use chromium, and violentmonkey plugin (add js script)

The spacebar issue is known (#1546). If you're using a dev version higher than v492 please comment there, as that would mean that the "improbable fix" did not work.
And if I understand your last sentence right, that part is a most likely a duplicate of #1540.

Disable Shortcuts in the YouTube options if you don't use them. I don't.

strange. In Opera - all work. In Crhomium not work.

if "Enable shortcuts on page" is enabled, you are unable to type "space" or use the left and right arrow keys to navigate while typing in a comment, as if all keystrokes are catched by the video player and not in the comment box

@drummwill: As stated before, this issue is known (see #1546 for more information). The accepted workaround is to disable "Enable shortcuts on page" until @YePpHa is able to fix it properly. Shortcuts will still work when the video page element has focus as long as "Enable YouTube player shortcuts" is still enabled.

This just started to happen here (chrome 41.0.2272.101, dev build 495), but disabling shortcuts works, so no issue for me.
Cheers


Update rustc version.

Currently cratesfyi is using a much older version of rustc, and so some projects which rely on those features aren't working.
Example

Thanks for reporting, cratesfyi is using rustc 1.11.0-nightly (0554abac6 2016-06-10) now. But it is using old rustdoc.css from 1.8. New version of cratesfyi will fix this issue.

I am closing this issue since it was only exists in old versions of cratesfyi.


tests, sriov: Fix finding the iface name by mac

What this PR does / why we need it:
The existing logic may return an empty iface name, when the mac
appears in the VMI status interface report as sourcing from the
domain.
Here is an example of such a report:
{
  "mac": "de:ad:00:00:be:ef",
  "name": "sriov",
  "infoSource": "domain"
}

(the interfaceName parameter is missing)
In such cases, the poll loop should continue waiting for the data
to be updated by the guest-agent or just fail after the timeout.

This change also includes some minor cleanups to the poll function, removing the named parameters and the variable shadowing.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

/cc @maiqueb

It seems the situation is much worse.
While fixing one issue, a real problem is revealed.
The SR-IOV migration test now exhibits an issue after the migration is over: The guest-agent does not seem to report back any information (at least in the 30sec period we wait for the interface to appear in the guest).
This is not limited to networking parts, it seems not to report anything at all.
At the same time, the condition of the agent being connected is still in place, so using that as a sign that everything is fine is misleading.
/cc @enp0s3

/approve

/approve

/lgtm
/retest

Even waiting for 140sec is not enough.
The VMI status is no longer getting updated by the guest agent.
I am trying to debug this, but a sensible alternative could be to stop watching the VMI status and look into the guest with "waiting".
/hold


Alacarte membership

Adds a new variant to the memberships.
This will be used when institutions purchase "a la carte" workshops rather than buying them as a membership package.

Linting errors are result of invalid configuration for the linters. There's a pending issue: #1987


Error instead of dispatch announcement

Hey, im getting strange error for playercoords

Can you help me fix that ? im using clear download

same there


Building Anoncoin on OSX with brew

Would like to see this get solved, can tell from looking at various build configurations that this is a desired goal, when producing a Anoncoin binary, for use on OSX.
Also it came to my attention, while looking at the language translations issue that this problem is an issue...
" I think that it acts as some sort of keyboard shortcut, but this doesn't work on osx."
So we need to look at that issue, and hopefully solve any other outstanding issues, so that building 'brew' on OSX for Anoncoin completes successfully.
A question I've got:
When 1st building your toolchain in anoncoin/depends there is an option to specify a shared QT 4.6 library or build the toolchain with a statically linked QT 5.2.1 library.  On linux platforms this option to build with static QT5, works, but it disables allot of IDE integration functionality which would normally be a part of the interface, keyboard shortcuts could be one of them on an OSX build too.
Windows users are forced to have a build statically linked to a version of QT, however there IDE integrations works pretty well.  This is not true on other platforms, having a shared library QT build is important if you want IDE integration.
Why keyboard shortcuts don't work on OSX is a mystery to me, but it should.  Perhaps the problem can be solved by doing a 'brew' build.   It might be an important first step in figuring out how to get shortcuts working on a MAC & caused me to get this issue started....
In anoncoin/depends are you building while using this on your make command line? USE_LINUX_STATIC_QT5
If you are, not using it should solve the keyboard shortcut problem and others.  If not using it, and you still do not have keyboard shortcut integration, then that is not good to hear, and the only thing I can think of, that might solve the problem, is the topic of this issue.
Building with brew, as mentioned before, may need to have a few things fixed or changed, so that the builder software does it properly on OSX.  I will look into what updates might be available.
If the solutions can be found, I wanted to make this a priority issue to get resolved....  Its important we can build Anoncoin on OSX and have IDE integration working properly.
GR

The biggest problem with using brew to install the required dependencies is not the keyboard shortcuts (which is an extremely minor bug that I normally would not even notice) but rather that it is not possible to compile Anoncoin. Attached is the output from my build using qt4 and qt5
./autogen.sh
./configure --with-gui=qt5
./make

as you can see, there is some problem with "qt/anoncoinaddressvalidator.cpp"
Making all in src
  CXX      compat/libanoncoin_util_a-glibc_sanity.o
  CXX      compat/libanoncoin_util_a-glibcxx_sanity.o
  CXX      libanoncoin_util_a-clientversion.o
  CXX      libanoncoin_util_a-rpcprotocol.o
  CXX      libanoncoin_util_a-sync.o
  CXX      libanoncoin_util_a-util.o
  AR       libanoncoin_util.a
  CXX      libanoncoin_common_a-allocators.o
  CXX      libanoncoin_common_a-base58.o
  CXX      libanoncoin_common_a-chainparams.o
  CXX      libanoncoin_common_a-coins.o
  CXX      libanoncoin_common_a-core.o
  CXX      libanoncoin_common_a-hash.o
  CXX      libanoncoin_common_a-key.o
  CXX      libanoncoin_common_a-keystore.o
  CXX      libanoncoin_common_a-netbase.o
netbase.cpp:1317:5: warning: unused label 'std' [-Wunused-label]
    std:string PortStr = IsNativeI2P() ? GetArg("-i2p.options.samport", "7656") : ToStringPort();
    ^~~~
1 warning generated.
  CXX      libanoncoin_common_a-protocol.o
  CXX      libanoncoin_common_a-script.o
  CXX      libanoncoin_common_a-scrypt.o
scrypt.cpp:50:24: warning: unused function 'be32dec' [-Wunused-function]
static inline uint32_t be32dec(const void *pp)
                       ^
1 warning generated.
  CXX      libanoncoin_common_a-scrypt-sse2.o
  CXX      libanoncoin_common_a-i2pwrapper.o
  CXX      i2psam/libanoncoin_common_a-i2psam.o
  AR       libanoncoin_common.a
  CXX      libanoncoin_server_a-addrman.o
  CXX      libanoncoin_server_a-alert.o
  CXX      libanoncoin_server_a-bloom.o
  CXX      libanoncoin_server_a-checkpoints.o
  CXX      libanoncoin_server_a-init.o
init.cpp:800:5: warning: unused label 'std' [-Wunused-label]
    std:string myI2pBase32Key;
    ^~~~
1 warning generated.
  CXX      libanoncoin_server_a-leveldbwrapper.o
  CXX      libanoncoin_server_a-main.o
In file included from main.cpp:1261:
./main2.cpp:120:25: warning: unused variable 'BlockCreating' [-Wunused-variable]
    const CBlockHeader *BlockCreating = pblock;
                        ^
1 warning generated.
  CXX      libanoncoin_server_a-miner.o
  CXX      libanoncoin_server_a-net.o
  CXX      libanoncoin_server_a-noui.o
  CXX      libanoncoin_server_a-rpcblockchain.o
  CXX      libanoncoin_server_a-rpcmining.o
  CXX      libanoncoin_server_a-rpcmisc.o
  CXX      libanoncoin_server_a-rpcnet.o
  CXX      libanoncoin_server_a-rpcrawtransaction.o
  CXX      libanoncoin_server_a-rpcserver.o
  CXX      libanoncoin_server_a-txdb.o
  CXX      libanoncoin_server_a-txmempool.o
  AR       libanoncoin_server.a
  CXX      libanoncoin_cli_a-rpcclient.o
  AR       libanoncoin_cli.a
  CXX      libanoncoin_wallet_a-db.o
  CXX      libanoncoin_wallet_a-crypter.o
  CXX      libanoncoin_wallet_a-rpcdump.o
  CXX      libanoncoin_wallet_a-rpcwallet.o
  CXX      libanoncoin_wallet_a-wallet.o
  CXX      libanoncoin_wallet_a-walletdb.o
  AR       libanoncoin_wallet.a
  GEN      qt/forms/ui_aboutdialog.h
  GEN      qt/forms/ui_addressbookpage.h
  GEN      qt/forms/ui_askpassphrasedialog.h
  GEN      qt/forms/ui_coincontroldialog.h
  GEN      qt/forms/ui_editaddressdialog.h
  GEN      qt/forms/ui_helpmessagedialog.h
  GEN      qt/forms/ui_i2poptionswidget.h
  GEN      qt/forms/ui_i2pshowaddresses.h
  GEN      qt/forms/ui_intro.h
  GEN      qt/forms/ui_openuridialog.h
  GEN      qt/forms/ui_optionsdialog.h
  GEN      qt/forms/ui_overviewpage.h
  GEN      qt/forms/ui_receivecoinsdialog.h
  GEN      qt/forms/ui_receiverequestdialog.h
  GEN      qt/forms/ui_rpcconsole.h
  GEN      qt/forms/ui_sendcoinsdialog.h
  GEN      qt/forms/ui_sendcoinsentry.h
  GEN      qt/forms/ui_signverifymessagedialog.h
  GEN      qt/forms/ui_transactiondescdialog.h
  GEN      qt/paymentrequest.pb.h
  GEN      qt/anoncoin.moc
  GEN      qt/intro.moc
  GEN      qt/overviewpage.moc
  GEN      qt/rpcconsole.moc
  CXX      qt/qt_libanoncoinqt_a-anoncoinaddressvalidator.o
In file included from qt/anoncoinaddressvalidator.cpp:6:
In file included from ./qt/anoncoinaddressvalidator.h:9:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/QValidator:1:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/qvalidator.h:41:
/usr/local/Cellar/qt5/5.4.0/include/QtCore/qregularexpression.h:137:1: error: no member named 'isDetached' in 'QRegularExpression'
Q_DECLARE_SHARED(QRegularExpression)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/QtCore/qglobal.h:2215:63: note: expanded from macro 'Q_DECLARE_SHARED'
template <> inline bool qIsDetached<TYPE>(TYPE &t) { return t.isDetached(); } \
                                                            ~ ^
In file included from qt/anoncoinaddressvalidator.cpp:6:
In file included from ./qt/anoncoinaddressvalidator.h:9:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/QValidator:1:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/qvalidator.h:41:
/usr/local/Cellar/qt5/5.4.0/include/QtCore/qregularexpression.h:137:1: error: no member named 'data_ptr' in 'QRegularExpression'
Q_DECLARE_SHARED(QRegularExpression)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/QtCore/qglobal.h:2217:16: note: expanded from macro 'Q_DECLARE_SHARED'
{ qSwap(value1.data_ptr(), value2.data_ptr()); } \
        ~~~~~~ ^
In file included from qt/anoncoinaddressvalidator.cpp:6:
In file included from ./qt/anoncoinaddressvalidator.h:9:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/QValidator:1:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/qvalidator.h:41:
/usr/local/Cellar/qt5/5.4.0/include/QtCore/qregularexpression.h:137:1: error: no member named 'data_ptr' in 'QRegularExpression'
Q_DECLARE_SHARED(QRegularExpression)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/QtCore/qglobal.h:2217:50: note: expanded from macro 'Q_DECLARE_SHARED'
{ qSwap(value1.data_ptr(), value2.data_ptr()); } \
                                                 ^
/usr/local/include/QtCore/qglobal.h:2209:19: note: expanded from macro '\
Q_DECLARE_SHARED_STL'
    { swap(value1.data_ptr(), value2.data_ptr()); } \
           ~~~~~~ ^
In file included from qt/anoncoinaddressvalidator.cpp:6:
In file included from ./qt/anoncoinaddressvalidator.h:9:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/QValidator:1:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/qvalidator.h:41:
/usr/local/Cellar/qt5/5.4.0/include/QtCore/qregularexpression.h:203:1: error: no member named 'isDetached' in 'QRegularExpressionMatch'
Q_DECLARE_SHARED(QRegularExpressionMatch)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/QtCore/qglobal.h:2215:63: note: expanded from macro 'Q_DECLARE_SHARED'
template <> inline bool qIsDetached<TYPE>(TYPE &t) { return t.isDetached(); } \
                                                            ~ ^
In file included from qt/anoncoinaddressvalidator.cpp:6:
In file included from ./qt/anoncoinaddressvalidator.h:9:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/QValidator:1:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/qvalidator.h:41:
/usr/local/Cellar/qt5/5.4.0/include/QtCore/qregularexpression.h:203:1: error: no member named 'data_ptr' in 'QRegularExpressionMatch'
Q_DECLARE_SHARED(QRegularExpressionMatch)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/QtCore/qglobal.h:2217:16: note: expanded from macro 'Q_DECLARE_SHARED'
{ qSwap(value1.data_ptr(), value2.data_ptr()); } \
        ~~~~~~ ^
In file included from qt/anoncoinaddressvalidator.cpp:6:
In file included from ./qt/anoncoinaddressvalidator.h:9:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/QValidator:1:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/qvalidator.h:41:
/usr/local/Cellar/qt5/5.4.0/include/QtCore/qregularexpression.h:203:1: error: no member named 'data_ptr' in 'QRegularExpressionMatch'
Q_DECLARE_SHARED(QRegularExpressionMatch)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/QtCore/qglobal.h:2217:50: note: expanded from macro 'Q_DECLARE_SHARED'
{ qSwap(value1.data_ptr(), value2.data_ptr()); } \
                                                 ^
/usr/local/include/QtCore/qglobal.h:2209:19: note: expanded from macro '\
Q_DECLARE_SHARED_STL'
    { swap(value1.data_ptr(), value2.data_ptr()); } \
           ~~~~~~ ^
In file included from qt/anoncoinaddressvalidator.cpp:6:
In file included from ./qt/anoncoinaddressvalidator.h:9:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/QValidator:1:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/qvalidator.h:41:
/usr/local/Cellar/qt5/5.4.0/include/QtCore/qregularexpression.h:241:1: error: no member named 'isDetached' in
      'QRegularExpressionMatchIterator'
Q_DECLARE_SHARED(QRegularExpressionMatchIterator)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/QtCore/qglobal.h:2215:63: note: expanded from macro 'Q_DECLARE_SHARED'
template <> inline bool qIsDetached<TYPE>(TYPE &t) { return t.isDetached(); } \
                                                            ~ ^
In file included from qt/anoncoinaddressvalidator.cpp:6:
In file included from ./qt/anoncoinaddressvalidator.h:9:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/QValidator:1:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/qvalidator.h:41:
/usr/local/Cellar/qt5/5.4.0/include/QtCore/qregularexpression.h:241:1: error: no member named 'data_ptr' in
      'QRegularExpressionMatchIterator'
Q_DECLARE_SHARED(QRegularExpressionMatchIterator)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/QtCore/qglobal.h:2217:16: note: expanded from macro 'Q_DECLARE_SHARED'
{ qSwap(value1.data_ptr(), value2.data_ptr()); } \
        ~~~~~~ ^
In file included from qt/anoncoinaddressvalidator.cpp:6:
In file included from ./qt/anoncoinaddressvalidator.h:9:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/QValidator:1:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/qvalidator.h:41:
/usr/local/Cellar/qt5/5.4.0/include/QtCore/qregularexpression.h:241:1: error: no member named 'data_ptr' in
      'QRegularExpressionMatchIterator'
Q_DECLARE_SHARED(QRegularExpressionMatchIterator)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/include/QtCore/qglobal.h:2217:50: note: expanded from macro 'Q_DECLARE_SHARED'
{ qSwap(value1.data_ptr(), value2.data_ptr()); } \
                                                 ^
/usr/local/include/QtCore/qglobal.h:2209:19: note: expanded from macro '\
Q_DECLARE_SHARED_STL'
    { swap(value1.data_ptr(), value2.data_ptr()); } \
           ~~~~~~ ^
In file included from qt/anoncoinaddressvalidator.cpp:6:
In file included from ./qt/anoncoinaddressvalidator.h:9:
In file included from /usr/local/Cellar/qt5/5.4.0/include/QtGui/QValidator:1:
/usr/local/Cellar/qt5/5.4.0/include/QtGui/qvalidator.h:204:71: error: expected ';' at end of declaration list
    virtual QValidator::State validate(QString &input, int &pos) const Q_DECL_OVERRIDE;
                                                                      ^
                                                                      ;
10 errors generated.
make[2]: *** [qt/qt_libanoncoinqt_a-anoncoinaddressvalidator.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1

Now, using the default version of qt by not specifying anything for the configure
./autogen.sh
./configure
make

yields
Making all in src
  CXX      compat/libanoncoin_util_a-glibc_sanity.o
  CXX      compat/libanoncoin_util_a-glibcxx_sanity.o
  CXX      libanoncoin_util_a-clientversion.o
  CXX      libanoncoin_util_a-rpcprotocol.o
  CXX      libanoncoin_util_a-sync.o
  CXX      libanoncoin_util_a-util.o
  AR       libanoncoin_util.a
  CXX      libanoncoin_common_a-allocators.o
  CXX      libanoncoin_common_a-base58.o
  CXX      libanoncoin_common_a-chainparams.o
  CXX      libanoncoin_common_a-coins.o
  CXX      libanoncoin_common_a-core.o
  CXX      libanoncoin_common_a-hash.o
  CXX      libanoncoin_common_a-key.o
  CXX      libanoncoin_common_a-keystore.o
  CXX      libanoncoin_common_a-netbase.o
netbase.cpp:1317:5: warning: unused label 'std' [-Wunused-label]
    std:string PortStr = IsNativeI2P() ? GetArg("-i2p.options.samport", "7656") : ToStringPort();
    ^~~~
1 warning generated.
  CXX      libanoncoin_common_a-protocol.o
  CXX      libanoncoin_common_a-script.o
  CXX      libanoncoin_common_a-scrypt.o
scrypt.cpp:50:24: warning: unused function 'be32dec' [-Wunused-function]
static inline uint32_t be32dec(const void *pp)
                       ^
1 warning generated.
  CXX      libanoncoin_common_a-scrypt-sse2.o
  CXX      libanoncoin_common_a-i2pwrapper.o
  CXX      i2psam/libanoncoin_common_a-i2psam.o
  AR       libanoncoin_common.a
  CXX      libanoncoin_server_a-addrman.o
  CXX      libanoncoin_server_a-alert.o
  CXX      libanoncoin_server_a-bloom.o
  CXX      libanoncoin_server_a-checkpoints.o
  CXX      libanoncoin_server_a-init.o
init.cpp:800:5: warning: unused label 'std' [-Wunused-label]
    std:string myI2pBase32Key;
    ^~~~
1 warning generated.
  CXX      libanoncoin_server_a-leveldbwrapper.o
  CXX      libanoncoin_server_a-main.o
In file included from main.cpp:1261:
./main2.cpp:120:25: warning: unused variable 'BlockCreating' [-Wunused-variable]
    const CBlockHeader *BlockCreating = pblock;
                        ^
1 warning generated.
  CXX      libanoncoin_server_a-miner.o
  CXX      libanoncoin_server_a-net.o
  CXX      libanoncoin_server_a-noui.o
  CXX      libanoncoin_server_a-rpcblockchain.o
  CXX      libanoncoin_server_a-rpcmining.o
  CXX      libanoncoin_server_a-rpcmisc.o
  CXX      libanoncoin_server_a-rpcnet.o
  CXX      libanoncoin_server_a-rpcrawtransaction.o
  CXX      libanoncoin_server_a-rpcserver.o
  CXX      libanoncoin_server_a-txdb.o
  CXX      libanoncoin_server_a-txmempool.o
  AR       libanoncoin_server.a
  CXX      libanoncoin_cli_a-rpcclient.o
  AR       libanoncoin_cli.a
  CXX      libanoncoin_wallet_a-db.o
  CXX      libanoncoin_wallet_a-crypter.o
  CXX      libanoncoin_wallet_a-rpcdump.o
  CXX      libanoncoin_wallet_a-rpcwallet.o
  CXX      libanoncoin_wallet_a-wallet.o
  CXX      libanoncoin_wallet_a-walletdb.o
  AR       libanoncoin_wallet.a
  GEN      qt/forms/ui_aboutdialog.h
  GEN      qt/forms/ui_addressbookpage.h
  GEN      qt/forms/ui_askpassphrasedialog.h
  GEN      qt/forms/ui_coincontroldialog.h
  GEN      qt/forms/ui_editaddressdialog.h
  GEN      qt/forms/ui_helpmessagedialog.h
  GEN      qt/forms/ui_i2poptionswidget.h
  GEN      qt/forms/ui_i2pshowaddresses.h
  GEN      qt/forms/ui_intro.h
  GEN      qt/forms/ui_openuridialog.h
  GEN      qt/forms/ui_optionsdialog.h
  GEN      qt/forms/ui_overviewpage.h
  GEN      qt/forms/ui_receivecoinsdialog.h
  GEN      qt/forms/ui_receiverequestdialog.h
  GEN      qt/forms/ui_rpcconsole.h
  GEN      qt/forms/ui_sendcoinsdialog.h
  GEN      qt/forms/ui_sendcoinsentry.h
  GEN      qt/forms/ui_signverifymessagedialog.h
  GEN      qt/forms/ui_transactiondescdialog.h
  GEN      qt/paymentrequest.pb.h
  GEN      qt/anoncoin.moc
  GEN      qt/intro.moc
  GEN      qt/overviewpage.moc
  GEN      qt/rpcconsole.moc
  CXX      qt/qt_libanoncoinqt_a-anoncoinaddressvalidator.o
  CXX      qt/qt_libanoncoinqt_a-anoncoinamountfield.o
  CXX      qt/qt_libanoncoinqt_a-anoncoingui.o
In file included from qt/anoncoingui.cpp:11:
./qt/guiutil.h:199:42: error: no member named 'StyleAnimationUpdate' in 'QEvent'
            return (e->type() != QEvent::StyleAnimationUpdate) ? QProgressBar::event(e) : false;
                                 ~~~~~~~~^
1 error generated.
make[2]: *** [qt/qt_libanoncoinqt_a-anoncoingui.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive] Error 1


[AMBARI-23652] LogFeeder: lowercase cluster name (writing docs & znode generation)

What changes were proposed in this pull request?
Lowercase cluster name for logfeeder (cluster name is lowercase in solr anyway), it's required as logfeeder will create the cluster znode with the cluster name, and if it is with uppercase we cannot get the right logs with cluster filter
How was this patch tested?
manually with docker-env

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1941/
Test FAILed.
Test FAILured.

retest this please


Maintain our own derivations of ports where necessary

this should help resolve issues where changes in modules are made to address package updates that have reached unstable, but not stable yet. it will also prevent release blockers due to nixpkgs PRs such as those mentioned in https://github.com/catppuccin/nix/pull/65#issuecomment-2184295348

Would we be using nixpkgs as a flake input or via nvfetcher?

I think we'll just use the nixpkgs from the system in the module


Increase coverage

Changes Unknown when pulling 70a385c2f4cfa621d49f91a8bab3587c2295c482 on isocolsky:coverage into ** on bitpay:master**.

Changes Unknown when pulling 1751ca7b65e7cf13b054890327c4c424ef9d28ea on isocolsky:coverage into ** on bitpay:master**.

Coverage increased (+0.58%) to 92.5% when pulling eabdd4f35a13b9be69262752f4b0349319012119 on isocolsky:coverage into 2ae70338667e4b6b53ad49208fa57643e5636386 on bitpay:master.

Coverage increased (+0.58%) to 92.5% when pulling eabdd4f35a13b9be69262752f4b0349319012119 on isocolsky:coverage into 2ae70338667e4b6b53ad49208fa57643e5636386 on bitpay:master.

is this still wip?

Yep, just a couple more to go

Coverage increased (+1.98%) to 93.9% when pulling 2326fa298829b95bf3cce9b49cb138de4924ab41 on isocolsky:coverage into 2ae70338667e4b6b53ad49208fa57643e5636386 on bitpay:master.

Coverage increased (+2.73%) to 94.65% when pulling 4b1e27f7501b9c34a2dfd61544a506e7dca025ed on isocolsky:coverage into 2ae70338667e4b6b53ad49208fa57643e5636386 on bitpay:master.

ready for review

wow!! nice work!!


Adding the scrollToPosition

The objective is to set an alternative attribute to go to the terminal's position. I added a new parameter to receive optionally and thus be able to set whether we want it to go to where the terminal cursor is.
FIxes: #51

Thank you for taking the time to submit a Pull Request! Please ensure the pull request is linked to an issue by using the commit format _Fixes <Issue #> - _.

Done #51

@jonmbake, thanks for approving the PR.
I'm trying to understand why it is not working when you update the package in React JS. I don't know if anyone has the same problem :(


Fix deprecation warning

Fix over 100 warning on CI over:
DEPRECATION WARNING: Enumerating ActiveModel::Errors as a hash has been deprecated.
In Rails 6.1, `errors` is an array of Error objects,
therefore it should be accessed by a block with a single block
parameter like this:
person.errors.each do |error|
  attribute = error.attribute
  message = error.message
end
You are passing a block expecting two parameters,
so the old hash behavior is simulated. As this is deprecated,
this will result in an ArgumentError in Rails 7.0.
 (called from full_messages at /home/travis/build/LeadDyno/leaddyno-app/vendor/bundle/ruby/2.6.0/bundler/gems/dynamic_form-3fcd00e23e84/lib/active_model/dynamic_errors.rb:16)

https://app.travis-ci.com/github/LeadDyno/leaddyno-app/builds/270596926

I was about to ask if you check the gem with leaddyno-app because I used this code for the gem but it did not work. But seems you have updated the code, seems work. As long as you tested with the app, LGTM :D