Minor fixes

All good fixes thanks! Let us know when you're done. The tests won't pass because some notebook output has changed but I can handle that after merge.

Feel free to merge now, I don't have anything on my list at the moment. (I tend to only submit PRs when I don't expect any immediate further changes.)

I submitted a couple of PRs to the holoviews-data repository which fix the same typos in the reference data. I'm not entirely sure how the whole build/testing process works but I hope this should fix the failing build.

I'll go ahead merge, will fix the notebook tests myself.


Add a FocusZoneView component

Proposal: Add a FocusZoneView component
Summary
There are places in apps where it's useful to have keyboard arrow keys move focus instead of tab/shift, e.g. in lists. This issue proposes a FocusZoneView component for this.
Basic example
Assume the FlatList renders buttons:
<FocusZoneView>
  <FlatList ... />
</FocusZoneView>

Open Questions
I don't have time to make a PR for this, but here's a working implementation (be warned this is off an older RN Mac commit):
FocusZoneView-Mac.zip
Note one thing this implementation doesn't support is the ability to remember the last focused component when focusing back on the focus zone. I hope to get to this in the next couple weeks and if so I'll update the link here.

Linking to related issue on React Native for Windows repo;

Well we have a FocusZone in FluentUI React Native that works pretty well. Is this still an ask? I was actually curious about that.

It's not an ask for us as we are using the one I linked above internally. Previously there was talk if we should have this in the React Native macOS repo, but I think having it in FluentUI is good enough.

OK! If you're ever curious, our Fluent FocusZone supports quite a few more props like bi-directional navigation and (somewhat) remembering what your last focused component was.
https://github.com/microsoft/fluentui-react-native/tree/master/packages/components/FocusZone
https://github.com/microsoft/fluentui-react-native/blob/master/apps/fluent-tester/src/FluentTester/TestComponents/FocusZone/FocusZoneTest.tsx (Test page of examples usage)


maths equations are not rendering at display

I am facing some problem in Mathjax on current project using mathjax & ajax at same time. What is happening ajax query is pulling the mathematics equation ( which is in Latex form)  from sql database (dynamic in nature)  in a online kind of test but mathjax is not rendering the mathematics equations at display as attached. What is the reason ? If I do referesh 4-5 times than it will display equation.
Please note that I am not from computer science & IT background , no clue about what is happening , this problem is faced by one of the developer in the project.

Without more details about what you code is actually doing (like code snippets or a minimal working example), we can't do much to help you.  But I suspect you are not telling MathJax to re-typeset the page once the ajax call has succeeded.
You should probably read the documentation on dynamic pages in MathJax.  Then if you still have questions, post them to the MathJax user's forum rather than here (this issue tracker is for bug reports).


Indicate which Stripe API version this library is compatible with

There are multiple version of the Stripe API
https://stripe.com/docs/upgrades

Seconded. I just started with Stripe, they automatically start people with the latest API, which is currently incompatible with django-stripe-payments. (For what it's worth, my current error is AttributeError on customer.active_card.fingerprint when calling the update_card method. )
Excerpt from the message from Stripe support:
I'm really sorry about the trouble: we did deploy a small change to when we decide to show fingerprints, but it was thoroughly tested to avoid changing any existing behavior. I suspect you being on a higher API version, but sending low Stripe-Version headers with every request (this is done by your django plugin), is a case we hadn't accounted for (very few people actually use Stripe-Version headers for older version).

You are right. Lots of work planned here. Just trying to find the time.
Sent from my iPhone

On Mar 22, 2015, at 1:11 AM, caacree<EMAIL_ADDRESS>wrote:
Seconded. I just started with Stripe, they automatically start people with the latest API, which is currently incompatible with django-stripe-payments. (For what it's worth, my current error is AttributeError on customer.active_card.fingerprint when calling the update_card method. )
Excerpt from the message from Stripe support:
I'm really sorry about the trouble: we did deploy a small change to when we decide to show fingerprints, but it was thoroughly tested to avoid changing any existing behavior. I suspect you being on a higher API version, but sending low Stripe-Version headers with every request (this is done by your django plugin), is a case we hadn't accounted for (very few people actually use Stripe-Version headers for older version).
—
Reply to this email directly or view it on GitHub.

For what it's worth, the project I'm using this library with is using the API version from 2014-06-17 and it seems to work alright

+1 on hitting issues with supported version of Stripe's API.
@paltman any estimate when the time might be found? There appear to be issues with the project's auto build and it's starting to feel a little unmaintained. I don't mean to apply pressure! Just pointing it out. :) If you've got a plan and can push a slice of the work my way, I'd be happy to give you a PR.

One thing that makes this really tricky, in my opinion is the processing of webhooks.
Outbound api calls to stripe can be forced to use a certain api version. django-stripe-payments already does this using the STRIPE_API_VERSION setting. As long as the default STRIPE_API_VERSION is correct and matches the implementation of outbound calls, I don't see why anyone would have any issues here...
Webhooks, on the other hand, big problem.  Webhooks are always sent using your Stripe account's API version. This means that django-stripe-payments will be processing webhook objects of completely 'random' structure and may not process them correctly.
Stripe does not let you set your account's api version!!!! They only let you upgrade to the latest version. This means django-stripe-payments users will almost never be using the right version on their webhook messages.
Strictly speaking, this is terrible. Practically speaking though, many people will probably get away with relatively error-free webhook processing.
I don't want to get into TLDR territory here... Has anyone else thought about this issue?

We now support latest API version.  Making this a setting is a little strange as to get to this point I had to refactor a lot of the modeling, so I don't think one can easily just set this setting to any old version and things just magically work. In addition, as @wahuneke pointed out it's important that it's in sync with what the webhooks are going to be sending.

Awesome! Thanks @paltman


Skip NativeLibraryLoader on non-Windows platforms

Fix #101

Can you replace the code in NativeLibraryLoader instead?

Or does it fail before that because it tries to JIT the P/Invoke methods?

It fails because of https://github.com/aspnet/dnx/issues/2442

Hmm, given that the DNX codepaths here are just temporary anyway... :shipit:


fix: Make auth token required for every request

Replace selective authenticator with definite interceptor

Fixes #461

@mejariamol Please review

@mejariamol Please review


Share a worker pool among pipelines that use the same image

If multiple pipelines use the same image, there's no reason why they can't share the same worker pool.

stale

This one we're going to be looking at doing in 1.8

It's less clear now that this is something we want to do, it means that workers from different pipelines can starve each other out.


[SD-1068] preparation for external configuration extension

Current coverage is 84.87%

Merging #967 into master will decrease coverage by -0.09% as of a1ad319

@@            master    #967   diff @@
======================================
  Files            7       7
  Stmts          592     595     +3
  Branches        36      36
  Methods          0       0
======================================
+ Hit            503     505     +2
  Partial          0       0
- Missed          89      90     +1

Review entire Coverage Diff as of a1ad319

Powered by Codecov. Updated on successful CI builds.

superseded by #975


[Snyk] Security upgrade werkzeug from 1.0.1 to 3.0.3

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

⚠ Warning
Flask 1.1.2 requires Werkzeug, which is not installed.

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

661/1000  Why? Recently disclosed, Has a fix available, CVSS 7.5
Remote Code Execution (RCE) SNYK-PYTHON-WERKZEUG-6808933
werkzeug:  1.0.1 -> 3.0.3
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Remote Code Execution (RCE)

Qovery can create a Preview Environment for this PR.
To trigger its creation, please post a comment with one of the following command.

Command
Blueprint environment

/qovery  preview 86d23237-413e-4d36-8107-dd4eefb5c091
blueprint

/qovery  preview {all|UUID1,UUID2,...}
To preview multiple environments

This comment has been generated from Qovery AI :robot:.
Below, a word from its wisdom :

One day they will all understand


Website not displayed correctly in any browser on Windows 10 (Firefox/Chrome/InternetExplorer/Edge)

Describe the bug
social.technet.microsoft.com looks like a notepad document.
To Reproduce

Use any browser on Windows 10 to visit: https://social.technet.microsoft.com

Expected behavior
A normal functioning website with stylesheets etc.
Screenshots

Desktop (please complete the following information):
See screenshot:
Windows 10 Pro 64bit
Internet explorer 11 (the version popup does not allow copy paste so you can type the superlong version yourself.)
Chrome  75.0.3770.100 (Official Build) (64-bit) (cohort: Stable)
Firefox 68.0 (64-bit)

I have windows 10 and tried this site on Google Chrome, Edge and Internet Explorer and all three loaded correctly. I would suggest trying to reset chrome, clear the cache or reinstalling chrome if the issue still persists.

@fun29 thanks for reporting this. It was likely a temporary glitch. The issue is no longer reproducible.

Agreed, no longer reproducible for me either.


'See also extend' does not have a link to the 'extend' operator section

[Enter feedback here]
See also extend does not have a link to the 'extend' operator section

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

ID: 3d21a5c6-ae80-52d0-7d06-43191081b656
Version Independent ID: 799a41ab-2353-1bbc-8132-69eeb4678154
Content: Project operator - Azure Data Explorer
Content Source: data-explorer/kusto/query/projectoperator.md
Service: data-explorer
GitHub Login: @orspod
Microsoft Alias: orspodek

@searleser97  Thanks for noticing that! I've updated this link in the docs, and this change should go live in a few hours.
https://github.com/MicrosoftDocs/dataexplorer-docs-pr/pull/1995
#please-close


KAFKA-5130: Refactor TC In-memory Cache

Collapsed the ownedPartitions, pendingTxnMap and the transactionMetadataCache into a single in-memory structure, which is a two-layered map: first keyed by the transactionTxnLog, and then valued with the current coordinatorEpoch of that map plus another map keyed by the transactional id.

Use transactionalId across the modules in transactional coordinator, attach this id with the transactional marker entries.

Use two keys: transactionalId and txnLogPartitionId in the writeMarkerPurgatory as well as passing it along with the TxnMarkerEntry, so that TransactionMarkerRequestCompletionHandler can use it to access the two-layered map upon getting responses.

Use one queue per broker-id and txnLogPartitionId. Also when there is a possible update on the end point associated with the broker-id, update the Node without clearing the queue but relying on the requests to retry in the next round.

Centralize the error handling callback for appending-metadata-to-log and sending-markers-to-brokers in TransactionStateManager#appendTransactionToLog, and TransactionMarkerChannelManager#addTxnMarkersToSend.

Always update the in-memory transaction metadata AFTER the txn log has been appended and replicated, and then double check on the cache to make sure nothing has changed since log appending. The only exception is when initializing the pid for the first time, in which we will put a dummy into the cache but set its pendingState as Empty (so it will be valid to transit from Empty to Empty) so that it can be updated after the log append has completed.

@dguy @junrao
I am still working to fixing all the unit tests but the non-testing code is ready for reviews.

Looks like the build fails with compilation errors..

@apurvam those are unit test compilations. I'm still working on those but non-testing code does build.

ah.. ok.. thanks!

@hachikuji @dguy @junrao I have addressed your comments. Two major modifications:

TransactionMarkerRequestCompletionHandler: exhaust all possible error codes.
Merge TransactionMarkerChannel into TransactionMarkerChannelManager.

@hachikuji addressed your comments, and fixed unit tests.
Also another observation is that we are unnecessarily sending multiple txn marker requests to a single broker for txnIds from different txn topic partitions, I have grouped them into a single request as well in this PR.

Merged to trunk.

@junrao Thanks for the comments, I will try to incorporate them in a follow-up PR.


Use the DEFAULT_ROLES_PATH constant from ansible to find the role paths

My ansible directory has the following format:
$ tree -L 1 ansible/
ansible/
|-- ansible.cfg
|-- environments
|-- inventory
|-- jobs
|-- plugins
|-- roles
`-- rules

My playbooks are put in the environments directory.
I use the ANSIBLE_ROLES_PATH variable to change the behaviour of ansible.
ansible-lint should use the same variable.
The code is taken from https://github.com/ansible/ansible/blob/release1.8.1/lib/ansible/playbook/play.py#L191-L207

@willthames Is there something preventing you to merge it?

Not really. Tested this, looks good, merging.
Apologies for the delay

Thank you!


Update v1.25.0.md

Description of the change:
Motivation for the change:
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

@spolti - Could you please signoff the commit? rest looks fine.


[Bug]: https://docs.chain.link/data-feeds/price-feeds links to itself

Describe the bug
Top link does nothing.
To Reproduce
Visit https://docs.chain.link/data-feeds/price-feeds
Click "› Learn how to read answers from Data Feeds" in the what's next section.
Takes you no where.
URLs
[- https://docs.chain.link/..

...
](https://docs.chain.link/data-feeds/price-feeds)

Expected behavior
No response
Additional context
No response

Thank you for reporting this!


How to get header by single email id?

like this:
header = sever.get_header(id)

looks like https://github.com/ZYunH/zmail#mailserverget_headersstart_indexnoneend_indexnone


Request for clarification over licensing of codebase

I noticed that the entire codebase is meant to be licensed under Apache 2.0, however, many individual scripts have "Copyright(c) 2023 lyuwenyu. All Rights Reserved." at the top.
I would like to seek some clarification as to whether or not the entire codebase is licensed under Apache 2.0?

Yes, entire codebase in this repo under Apache 2.0.  You can use it with confidence under that licence.

Awesome, thank you!


2021-11-09 equity dashboard chart data update

Equity dashboard stats updates in this PR may be reviewed on staging - here.
After reviewing, if all looks well, approve and merge this Pull Request.
If there are issues with the data:

Note concerns or issues here by commenting on this PR
Work with Triston directly to resolve data issues
Alert the COVID19 site team in Slack (in the Equity page channel)

Hi all - Below is my preliminary data review.
I observe one red flag — :warning: I don’t believe the X-Axis for the HE Metric Graph extended as it should (to about Nov. 2); as of now, it ends on the same date as last week (Oct. 24). Could we double check if the graph updated?
:bulb: All noticeable highlights are in report below. Otherwise, I observe no other red flags. Thank you!
1. Blue Box Updates:
:heavy_check_mark: All percentage values are appear reasonable —

Death rate for Latino people compared to statewide (Blue Box 1) remains unchanged
Case Rate for Pacific Islanders (Blue Box 2) increases by 1% to 46%, after 3 weeks at 45%
Death rate for Black people compared to statewide (Blue Box 3) remains unchanged
Case rate for communities with median income (Blue Box 4) decreases by 1% to 32%, after 9 weeks at 33%

2. Death Rate/100K by R&E:
:heavy_check_mark: Statewide COVID Deaths/100K stays at 3 for four consecutive weeks. All R&E Deaths/100K remain identical or nearly identical to last week (any and all changes are ≤ 0.1). Asian American continues in its second week as the lowest, non-<11 rate. All values are reasonable.
:bulb: After being <11 last week, AI/AN returns to being the highest rate this week.
3. Case Rate/100K by R&E:
:heavy_check_mark: Like last week, this week largely shows stability in all Case/100K rates. Any changes from last week are ≤9. Statewide remains unchanged at 270 (same value as the last three consecutive weeks). NHPI Cases/100K remains the highest rate. Multi-Race Cases/100K remains the lowest rate. All values appear reasonable.
4. Testing Rate/100K by R&E:
:heavy_check_mark:  Unlike the decreasing trend we observe over the past three consecutive weeks, Testing Rates/100K generally increase. NHPI Testing/100K, which decreases slightly (by ~.12%), is the primary exception. Statewide increases from 12,626 to 12,779.
:heavy_check_mark: NHPI Testing/100K remains the highest rate, Multi-Race Testing/100K remains the lowest rate.
5. Community case rate/100K by median annual household income bracket:
:heavy_check_mark: After two consecutive weeks of noticeable increases in all income brackets’ case rates, this week we observe little to no change in case rates. Any case rate changes for the brackets are  ≤0.1. Statewide decreases from 12.5 to 12.3, a value between the $40-60K & $60-80K income brackets’ case rates. All values are reasonable.
6. HE Metric:
:warning:  I don’t think the X-Axis for the HE Metric Graph extended as it should (to about Nov. 2); as of now, it ends on the same date as last week (Oct. 24).

@sindhuravuri Agreed.  When I look at last week's data here, it extended to October 23.
https://github.com/cagov/covid-static-data/blob/main/data/reviewed/equitydash/healthequity-california.json
The new data only goes to October 24 for some reason.
https://github.com/cagov/covid-static-data/blob/main/data/to-review/equitydash/healthequity-california.json
When I execute the SQL in Snowflake, the result only goes to 10-24.
select COUNTY, DATE, METRIC, METRIC_VALUE, METRIC_VALUE_30_DAYS_AGO, METRIC_VALUE_DIFF from COVID.PRODUCTION.VW_EQUITY_METRIC_POS_30_DAY_BY_CNT;

Should we publish as is, and extend it later?


feat: [RHTAP-1282] Refactor jvmbuildservice controller code

Description
This PR divides jvmbuildservice controller methods into files based on targeted object and adds missing comments.
Issue ticket number and link
RHTAP-1282
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Checklist:

[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

cc @stuartwdouglas  @psturc

/retest-required


Fixes for JS reserved words catch, char, and delete

Using pdf.js in a project that leverages http://yui.github.io/yuicompressor/ caused errors due to pdf.js's use of JavaScript reserved words.

This seems like a limitation with a particular minifier, rather than PDF.js itself, see e.g. the discussion in https://github.com/mozilla/pdf.js/issues/4547.
Closing as invalid.

OK so 'char' is not a reserved work but 'catch' and 'delete' are reserved words. So there is still an issue with the code currently not meeting ECMA standards.

The way that catch and delete are used is spec compliant (e.g. note that catch is used with Promises). It seems that the issue might be that the minifier incorrectly flags all usages of those "words" as incorrect, instead of analysing how they are used.
Since this is a limitation of the minifier used, I'd suggest filing a bug with the minifier instead.
Also, there's an (experimental) minified build target for PDF.js, please see https://github.com/mozilla/pdf.js/blob/master/make.js#L653.

So there is still an issue with the code currently not meeting ECMA standards.

@meyermc catch is used in ECMAScript Promise API (see https://tc39.github.io/ecma262/#sec-promise.prototype.catch). Also IdentifierName is not Identifier, and 'catch' and 'delete' is allowed not be used IdentifierName (see http://www.ecma-international.org/ecma-262/5.1/#sec-A)

OK that makes sense, thanks for the detailed response.


Unprocessed log entries should be kept

From time to time, log entries are not accepted by coralogix (either connection reset or malformed). If this happens, log entries should be stored in a DLQ.

if it's only a connection issue, they should probably be rejected, so the next time they will be retried?

not sure, whether a subscription filter has the same reject-retry semantics as an SQS induced trigger, but I'll check

:tada: This issue has been resolved in version 1.2.3 :tada:
The release is available on:

v1.2.3
v1.2.3
GitHub release

Your semantic-release bot :package::rocket:


Enhance VAST Python bindings

This PR integrates all features from #2518.

[x] Add IP address extension type
[ ] Support native conversion to pandas

:memo: Reviewer Checklist
All functionality is covered by unit tests. Please check them.

I didn't copy over from #2518 this functionality:
def fmt_ip(df: pd.DataFrame, ip_columns: list[str]) -> pd.DataFrame:
mavam marked this conversation as resolved.
    """Formats IP of a dataframe Pass columns to format as arguments."""
    columns = []
    for col_name in df.keys():
        if col_name in ip_columns:
            columns.append(df[col_name].apply(unpack_ip))
        else:
            columns.append(df[col_name])
    return pd.concat(columns, axis=1)

and the corresponding test:
def test_fmt_ip():
    df = pd.DataFrame(
        [b"\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\n\x01\x15\xa5"],
        columns=["ip"],
    )
    assert vua.fmt_ip(df, ip_columns=["ip"]).ip[0] == ipaddress.IPv4Address(
        "<IP_ADDRESS>"
    )

Everything else should be covered. That said, I think there might be an automatic conversion possible when calling to_pandas() on a Table instance, per the Arrow documentation.

Some inspiration for the pandas extension type: https://github.com/ContinuumIO/cyberpandas/blob/master/cyberpandas/ip_array.py

Here's an example that shows the registered extension types when printing a Zeek HTTP log:
pyarrow.Table
ts: timestamp[ns]
uid: string
id.orig_h: extension<vast.address<IPAddressType>>
id.orig_p: uint64
id.resp_h: extension<vast.address<IPAddressType>>
id.resp_p: uint64
trans_depth: uint64
method: string
host: string
uri: string
referrer: string
user_agent: string
request_body_len: uint64
response_body_len: uint64
status_code: uint64
status_msg: string
info_code: uint64
info_msg: string
filename: string
tags: list<item: string>
  child 0, item: string
username: string
password: string
proxied: list<item: string>
  child 0, item: string
mime_type: string
md5: string
extraction_file: string

Note extension<vast.address<IPAddressType>>.

@dominiklohmann can you check whether the names in bbdcf65 are correct?

@dominiklohmann Do we have an example record batch with all extension types somewhere? This would be lovely for testing so that we can be assured that the two implementations align.

I'm inclined to move the pandas conversion into a separate PR, given that this one is all about extension types. Thoughts?

@dominiklohmann Do we have an example record batch with all extension types somewhere? This would be lovely for testing so that we can be assured that the two implementations align.

I commented this in some thread. We don't right now (except for the old Arrow v1 FlatBuffers table), but it should be easy enough to create and check in as a binary file for use in unit tests.

A small side note that slipped through the previous PR: the README should instruct to run
poetry install --all-extras

Otherwise neither the examples nore the tests work


Better well-typed Core generator

It turns out the generator for well-typed Core is most likely to just return constants rather than using the input stream at all.
At the moment we have
tryExpForType :: ValType -> Context -> Gen (Exp ..)

which takes a context and a type, and tries to build an expression that fits that type. The problem is that it's quite unlikely that any of the variables in the context will have the exact right type.
We should be able to implement the other direction, which returns a (probably) well-typed expression and its type.
tryExpWithType :: Context -> Gen (Exp .., ValType)

This will be far more likely to choose something from the context. It will probably need to use tryExpForType when applying primitives and so on though.

very useful :potable_water:


Add-BitbucketRepositoryBranchRestriction does not remove branch_type property

This causes the error:
branch_type is only valid when branch_match_kind is branching_model"
When trying to add a merge check using the Add-BitbucketRepositoryBranchRestriction Cmdlet. To reproduce:
$ReferenceRepoSlug = "RefRepo"
$DestinationRepoSlug = "DiffRepo"

$BranchName = "development"
Get-BitbucketRepositoryBranchRestriction -RepoSlug $ReferenceRepoSlug | Where-Object -Property pattern -EQ $BranchName | Where-Object { $_.GetType().Name -eq "MergeCheck" } | ForEach-Object {
$Check = New-BitbucketRepositoryBranchRestrictionMergeCheck -Kind $_.kind -Pattern $_.pattern -Value $_.value
Add-BitbucketRepositoryBranchRestriction -RepoSlug $DestinationRepoSlug -Restriction $Check
}

The incorrect logic is https://github.com/beyondcomputing-org/Atlassian.Bitbucket/blob/b59de675ad4fed33fb104f9bd266041ad6c98d11/Atlassian.Bitbucket.Repository.BranchRestriction.psm1#L52
When excluding a property in this manner, you need to specify a wildcard for the -Property parameter. Will submit a PR in accordance with the contributing guidelines shortly.

#15

Thanks @variableresistor.  I need to make some other updates for API deprecations but then I'll circle around and take a look at this as well.

Thanks for the contribution @variableresistor .  The PR has been merged and version 0.29.1 published on the PS Gallery.


Delete a single product by ID

As a manager, I need the functionality to delete a single item by ID, so that when a product gets sold out or I don’t want to sell it anymore, I can remove it from shelves.

Closing as it is a duplicate.


Add some badges in README.md

Add two badges for Slack link and Apache license link in README.md
Issue = #95

lgtm :)

@byeolbit
How do you think add your name and email to the AUTHOR files for participating this project?

@romandev
I added my name and email to AUTHORS and fixed slack invatation link in README.md
PTAL


Fall back to Meson WrapDB for dependencies

Rather than hand-bundling uthash and supporting a missing Check dependency, fall back to WrapDB builds for both.  meson build --wrap-mode=nofallback can be used to disable the fallbacks, forcing both libraries to come from the system.
Also fix API docs and clean up compiler option handling.

Thanks for the review!  Updated for comments.

LGTM!


question: Has anyone tested thread-priority with WASM?

Has anyone tested thread-priority with WASM?

That is a good question and I have never had anything even remotely connected to WASM, so I literally have no idea. Let's wait until someone else answer this question.

According to the information I have found, it should work, but the crate can't be built right now due to libc not supporting the necessary functions for it to work: pthread_setschedparam and pthread_getschedparam.

Thank you, @vityafx.  It might be great to have that support added.


Added tests for VMD

In order to have VMD added to the next Boost release I am adding VMD tests to 'master'. The tests have been in 'develop' already and I have been watching the results and making any corrections necessary.

Added VMD to the .gitmodules for Master.


Fix broken link for x11rb examples directory

Broken Link - https://github.com/psychon/x11rb/tree/master/examples
Updated Link - https://github.com/psychon/x11rb/tree/master/x11rb/examples

Thanks for this PR & sorry for missing this link in the conversion


Run doc_generation workflow on a new release

Codecov Report

Merging #369 (b9674b5) into master (4d0f857) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #369   +/-   ##
=========================================
  Coverage     98.32%   98.32%
  Complexity     1578     1578
=========================================
  Files           147      147
  Lines          4245     4245
=========================================
  Hits           4174     4174
  Misses           71       71

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4d0f857...b9674b5. Read the comment docs.


wasm version

Thanks for your project!
I'm just wondering that if there is any plan for wasm version?

Hello!
I'm not familiar with WASM. Is there anything in particular that doesn't work? Is it not able to compile?

Noop, just curious about wasm version, no specific issues.
I'm not familiar with Rust, also new to wasm. I tried to build it myself and failed to execute at Javascript side
https://gist.github.com/jerry7536/b574989644a93ed674416955ef9f715b
my code sucks and an official wasm build would be great

I haven't tried building on WASM, but an issue with the snippet is here:
let tagged_file = Probe::new(Cursor::new(buf)).read().expect("fail to read");

When using Probe::new, you'll need to call guess_file_type on it (or set_file_type if you already know the type). So this will always panic since Probe::read fails when no FileType is present.

Thanks! that effects!

Gist updated. New version successfully read the tag. Thanks!

Getting lofty to read tags in wasm is pretty straightforward now. Unfortunately though the browser APIs for reading parts of files are all async so there doesn't seem to be a way to pass this to the Read object that lofty's Probe::new wants. So in order to read the tag you have to read the entire file into memory first. For larger files this can be slow.
Is there any way around this other than adding an async API to lofty?

Is there any way around this other than adding an async API to lofty?

I don't believe so. Lofty will need the entire file to be present in many cases, as sometimes times there will be tags written at the end or we have to guess the stream length. This is just something that'll have to wait for Keyword Generics.

Lofty will need the entire file to be present in many cases, as sometimes times there will be tags written at the end or we have to guess the stream length.

Interesting. So in cases like that reading the entire file first shouldn't take any extra time anyway.
I think I'll bundle up what I have now as a wasm-ified version of lofty that would make it easy to to read tags in a browser or nodejs app.

Some preliminary experiments suggest that even when reading the entire file into memory lofty in wasm is still faster than the pure JS library I've been using (https://github.com/Borewit/music-metadata) for smaller lossy audio files like opus. But the I/O is too heavy for larger lossless files like flac and it's much slower there.

larger lossless files like flac and it's much slower there.

I'd imagine flac would be slower, since it currently eagerly allocates blocks. That's something I've been meaning to fix since it's less than ideal.

I have noticed that even compiling and running lofty natively (not in wasm) that reading tags from flac files is quite a bit slower than opus or aac. I just assumed it was because flac files required a lot more I/O but I confess I haven't looked into the details.

Do you have benchmarks setup comparing Lofty and music-metadata? If they're decently far apart that's something I'd like to spend some time working on. Performance work just isn't something I've sat down and done, I really just focus on adding features and bug fixes right now.

I haven't done any proper benchmarks yet, just some observations using various methods to scan a library of about 15k tracks. For my primary use case, compiling lofty natively and using direct file access, lofty is very very fast. Running the same scan in a browser using music-metadata is at least an order of magnitude slower. Some very preliminary experiments with running lofty via wasm in the browser suggest it's also faster there at least on small, lossy files.
The main limitation with music-metadata is it only reads tags and doesn't support writing at all, hence my interest in getting lofty going in a browser environment.

I don't have any experience with WASM, but I am always open to improving the experience with it. I'll probably get around to reducing the allocations in FLAC this week, which might help you out a little. The main blocker is keyword generics, though.
If you do end up doing some benchmarks, please do share them. I haven't done any benchmarks comparing Lofty to other libraries so that'd be nice to have. I'll move this over to a discussion.


ToC Generation Refactor

Note: this PR is easier to review one commit at a time, and the commit messages roughly describe each change.
Changes:

now *-src.yml files are mandatory for each docs version
*-src.yml files get turned into *-gen.yml files
renamed *-manual.yml files to the new *-src.yml format
ToCs now contain only entries with uris (unless they have children)
pages now specify their ToC name using the title or toc_title front matter property
removed the name property from ToC entries, moving it to the respective page where necessary

@riknoll @rakatyal @nikhilkh please review when you have a moment.

LGTM


Identify and document similar game design projects

We are always looking for inspiration from existing game designs!
Feel free to leave any games and their designs in the comments section on this issue.
In the comment, please include,
Organization/Project Name:
Link to Work:
Game Mechanics used:

Organization/Project Name: No Man's Land by Janna Ullrich
Link to Work: http://jannaullrich.de/ (actual site of project down)
Game Mechanics used: Board game

'No Man's Land' is a board game that aims to expose the absurd practices of today's immigration industry. It embodies the bureaucratic prison in which refugees get stuck after they have fled their country but can't enter another.


Support updated_prop

Motivation

This is a Stripe-specific prop extension.
Test plan

See included automated tests.

This should also have a sizable drop in missing methods on pay-server.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build result here:
→ https://go/builds/bui_HTlJxiVe7PbPxa

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build result here:
→ file
StandaloneBundle
the
can
config
source
rake
ast
bigdecimal
bundler
byebug
coderay
dogstatsd
excon
multipart-post
interception
jaro_winkler
json
little-plugger
multi_json
method_source
mini_portile2
nio4r
parallel
yard
psych
rack
rainbow
rexml
ruby-progressbar
unicode-display_width
rubyzip
subprocess
tins
faraday
logging
nokogiri
parser
pry
sorbet-runtime
term-ansicolor
terminal-table
sentry-raven
pry-byebug
pry-rescue
rubocop
rubocop-daemon
rubocop-minitest
rubocop-performance
pry-doc
sorbet-runtime
complete!
gems
https://go/builds/bui_HTmQ0F7S4J8Tsc

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build result here:
→ https://go/builds/bui_HTnJrjws3KDwai

Trying to re-surface this, as we've seen this causing issues at Stripe

Closing and opening a new one, as there are a bunch of merge conflicts


Add zeitgeist based dependency check

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Adding an automatic dependency check using zeitgeist. We also split-up the GitHub actions matrix to provide a more visual experience.
Which issue(s) this PR fixes:

None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

/approve
/lgtm


feat: http url interpolation SOFIE-3310

About the Contributor
This pull request is posted on behalf of the NRK.
Type of Contribution
This is a Feature
New Behavior
This allows for defining the urls for the httpsend device, as well as urls passed to the renderers in sofieChef and casparcg, in a format that allows for taking fragments from the datastore.
For example an object could look something like:
{
  deviceType: 'httpSend',
  type: 'post',
  url: {
    key: `http://example.com/{{subPath}?apiKey={{apiKey}}`,
    args: {
      subPath: 'my-default', // Overriden by the datastore
      apiKey: '', // Taken from datastore
    }
  },
  $references: {
    'url.args.subPath': {
      datastoreKey: 'httpSubpath',
      overwrite: true,
    },
    'url.args.apiKey': {
      datastoreKey: 'httpApiKey',
      overwrite: false,
    }
  }
}

In this example, the 'apiKey' will be taken from the datastore, avoiding being baked into the rundown.
And the 'subPath' being taken from the datastore, means it can be changed while playing the rundown more easily.
The syntax of the interpolation matches the translations format we use elsewhere in Sofie.
This has been added to the httpSend and sofieChef devices, and to casparcg for the html content type
Testing Instructions

Other Information

Status

[x] PR is ready to be reviewed.
[x] The functionality has been tested by the author.
[ ] Relevant unit tests has been added / updated.
[ ] Relevant documentation (code comments, system documentation) has been added / updated.

Codecov Report
Attention: Patch coverage is 56.52174% with 10 lines in your changes missing coverage. Please review.

Project coverage is 55.68%. Comparing base (7acebc8) to head (9406a73).

Files
Patch %
Lines

packages/timeline-state-resolver/src/lib.ts
27.27%
8 Missing :warning:

...-state-resolver/src/integrations/casparCG/index.ts
50.00%
1 Missing :warning:

...esolver/src/integrations/sofieChef/stateBuilder.ts
50.00%
1 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##           release51     #342      +/-   ##
=============================================
- Coverage      55.71%   55.68%   -0.04%
=============================================
  Files            129      129
  Lines          10117    10132      +15
  Branches        2446     2441       -5
=============================================
+ Hits            5637     5642       +5
- Misses          4103     4113      +10
  Partials         377      377

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


Bitcoin Core and OmniCore run at a time

is there any solution to run OMNI core and BTC core  both wallets at a time? when i install Omni core wallet it overides my bitcoin.conf file which is my BTC wallet file located in  Roaming folder/Bitcoin. or is there any settings which make them differ to each other ?

You can use option "-datadir" to seperate your enviroment. (https://en.bitcoin.it/wiki/Data_directory)

thanks issue resolved.

Hi there, the related options are -rpcport, -port and -datadir, because you not only need to ensure they use a different datadir, but also different ports.


[BUG]: isExternalPlaybackActive' is unavailable in visionOS

Version
6.4.3
What platforms are you having the problem on?
visionOS
System Version
2.0
On what device are you experiencing the issue?
Simulator
Architecture
New architecture with interop layer
What happened?
When building project I get the error isExternalPlaybackActive' is unavailable in visionOS
Reproduction
repository link
Reproduction
Step to reproduce this bug are:
Install react-native-video with npm
Run pod install
Build project in Xcode

Hi, thanks for reporting the issue! isExternalPlaybackActive is not supported for visionOS rn, try to remove this prop for visionOS platform. @KrzysztofMoch should we convert this issue to feature request?

@AdamGoodApp I just push a branch to fix the issue can you have a try on this branch please ?

I finnally tested on apple vision pro on emulator, It works fine !

func applicationWillResignActive(notification _: NSNotification!) {
        let isExternalPlaybackActive = _player?.isExternalPlaybackActive ?? false
        if _playInBackground || _playWhenInactive || !_isPlaying || isExternalPlaybackActive { return }

        _player?.pause()
        _player?.rate = 0.0
    }

'isExternalPlaybackActive' is unavailable in visionOS
"react-native-video": "^6.4.5" Upgraded npm package and ran pod install again.


split pasted key-value-pairs for environment variable names

Intercept the paste-action of environment variables in the section 'Environment Variables' on the screen for creating a new stack.
The interception should break the pasted content on the first occurrence of the character '=' and put everything after it into the value field (asking for confirmation if the value-field is not empty).

Hi Thanks for raising however Closing this ticket as this would be an impractical and hard to implement solution. Also a feature request is already open here https://github.com/portainer/portainer/issues/1857 to improve the env var UI and a PR is in progress here https://github.com/portainer/portainer/pull/4175

Just to clarify on the closing of the feature request, the advanced mode that should be introduced in #4175 will solve this problem by allowing you to copy/paste one or multiple key/values.


Upload of txt files

Hello,
i've just started using the extension and it's working so far for scripts.
The upload of *.txt files is broken though.
This is in fact a bit confusing, as the README.md does not mention txt files - but it's in the code.
I get the toast (as activated in settings), that the file was uploaded - but it does not appear in Bitburner.
There is no error message in Bitburners debugger.
In vscode the plugin reports some errors that seem to be unrelated:
Cannot read property 'dispose' of undefined
Cannot read property 'dispose' of undefined
Cannot read property 'dispose' of undefined
Cannot read property 'dispose' of undefined

Game version (Steam): Bitburner v1.3.0 (5ebb96a0)
vscode: 1.63.2
Plugin: 1.3.3
Regards!

I can reproduce this bug myself. After a bit digging into the problem, I found the following thing out.
In my opinion the bug lies in the Bitburner project, the API-Server more precisely. I don't think the vs code extension can fix it.
In short: The game refuses to accept txt files because it is not a valid script. The game only accepts script files with extensions ( .js, .script, .ns )
When the VS Code Extention pushes a file to the game then it sends a post request to the API-Server. For Post  request a function, called  writeToScriptFile, is called. It is for writing saving a script to the game. Of course this function checks if the file is a valid script by looking at the extension. The extension txt is not valid for a script file.


Lacking important features

Sounds awesome, but since you can't use it with EFCore due to navigation property circular references, or deserialization to immutable POCOs (private or internal setters) this library, or subobjects being ignored, this is near useless until .NET 5.

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

ID: 588ae32f-3429-143f-824c-5ab2d046d24a
Version Independent ID: 002f9f2a-48d1-0671-a079-b99b9f6bab58
Content: How to serialize and deserialize JSON using C# - .NET
Content Source: docs/standard/serialization/system-text-json-how-to.md
Product: dotnet
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

@Allann Thanks for the comments.  For the latest information on reference handling, see issues 37786 and 38579. On private setters, see 38163.  I don't understand the reference to "subobjects being ignored" -- could you clarify what you mean by that?

https://github.com/dotnet/corefx/issues/42515


fix(security): Stop panicking on state RPC or block requests with very large heights

Motivation
We have a few panics that can be triggered remotely by rpc methods or blocks with very large heights.
Close #6595.
Solution
This fixes the panics in getblock, z_gettreestate, getblockhash, and committing blocks to the state.
The following calls do not panic anymore.

 curl --silent --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblock", "params": ["2147483647", 1] }' -H 'Content-type: application/json' http://<IP_ADDRESS>:6666/ | jq
curl --silent --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblock", "params": ["2147483647", 0] }' -H 'Content-type: application/json' http://<IP_ADDRESS>:6666/ | jq
curl --silent --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "z_gettreestate", "params": ["2147483647"] }' -H 'Content-type: application/json' http://<IP_ADDRESS>:6666/ | jq

Not Impacted
getaddresstxids is not affected by this issue because it returns another error first, but it was fixed anyway.
getblocksubsidy is not affected because it doesn't use the state.
get_network_sol_ps and get_network_hash_ps have a different bug that will be fixed in #6688.
Review
@oxarbitrage (or anyone else) can review the new tests in this PR.
Reviewer Checklist

[ ] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?

[ ] Does it change concurrent code, unsafe code, or consensus rules?

[ ] How do you know it works? Does it have tests?

Follow Up Work

#6688

Failed due to #5819


Any plan on applying it to Action tube detection

Hi great work!
Thanks for sharing the code.
Do you have any plan to apply it on the action tube detection problem? I guess we have to strip off text encoder.
Best
Gurkirt

Hi, I do not plan to apply it to action tube detection, but this is a very relevant problem! Yes, you would have to strip off the text encoder. Also, maybe a different pretraining than the one used in our work should be used.

Thanks for the reply. https://arxiv.org/abs/2104.00969 looks similar to yours as well. Can you point out major difference to this one?

This is indeed relevant related work! I would actually say that the main differences are related to the specific task each of the works tackles: a task with natural language inputs in our case, and a task without natural language input but that requires predicting an action label in their case.


Task#2 (Setup local development environment for NetworkX)

Hi! I have completed this task which was #3 . Kindly check it. @rossbar @dschult @MridulS

@29riyasaxena could you add the full output of pytest? Thanks!

@29riyasaxena could you add the full output of pytest? Thanks!

Hi! I have modified the output file. Please check it..

Thanks @29riyasaxena!

Thanks @29riyasaxena!

My pleasure @MridulS ! Can you please check the other file which I have committed, I don't know why it has not gone to another PR.

Yeah I checked that too, it looks good to me.
It didn't go to a new PR as it's on the same branch main. It's recommended not to work on the main branch and create new branches for every PR :)

Okay thanks Sir!
Should I delete this file and create another PR for that task?

No need for that, it's already merged in https://github.com/networkx/outreachy/tree/main/2022-round-1/29riyasaxena

No need for that, it's already merged in https://github.com/networkx/outreachy/tree/main/2022-round-1/29riyasaxena
Okay, thanks a lot! :)


Building from jupyter/* containers generates error when running apt update

Using a very simple Dockerfile
# Copyright (c) Jupyter Development Team.
# Distributed under the terms of the Modified BSD License.
#ARG BASE_CONTAINER=jupyter/scipy-notebook
ARG BASE_CONTAINER=jupyter/tensorflow-notebook
FROM $BASE_CONTAINER

# Fix: https://github.com/hadolint/hadolint/wiki/DL4006
# Fix: https://github.com/koalaman/shellcheck/wiki/SC3014
SHELL ["/bin/bash", "-o", "pipefail", "-c"]

RUN pip install tensorboard

# Temporarily commented because APT is throwing a fit right now
RUN apt-get update --yes
RUN apt-get install --yes --no-install-recommends \
    nodejs npm
RUN apt-get clean && rm -rf /var/lib/apt/lists/*

Building the container results in this error:
#6 14.72 Get:17 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [49.4 kB]
#6 15.16 Get:18 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [23.3 kB]
#6 15.21 Fetched 26.5 MB in 15s (1,785 kB/s)
#6 15.21 Reading package lists...
#6 16.25 E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
#6 16.25 E: Sub-process returned an error code

The workaround is simple. Add the line below before you run the apt command:
RUN mv /etc/apt/apt.conf.d/docker-clean{,.disabled}

This disables an apt post-execution script that is throwing an error trying to delete things that don't exist.


TTNN Runtime refactor

Refactor TTNN Runtime:

Move Ops to their own dedicated directories/files/namespaces.
Add program context that manages the state of the program (borrowed tensors/devices, intermed tensors generated by ops)
Add program executor class that executes the program

To add a new op:

Update an existing op file or create a new op file under operations, implement the op run API.
Add the new source file (if applicable) to operations/CMakeLists.txt
Add a new case to the runOperation method of ProgramExecutor.

Thanks @jnie-TT for putting together changes!  My first thought is that all of the double nested directory structure for ops should be flattened, and it's okay to group similiar in single directory for easier viewing.
For example, instead of LHS, flatten to RHS:

eltwise/binary/binary.cpp -> eltwise/binary.cpp
eltwise/unary/unary.cpp -> eltwise/unary.cpp
data_movement/concat/concat.cpp -> data_movement/concat.cpp
data_movement/reshape/reshape.cpp -> data_movement/reshape.cpp

etc, basically applies to all files.

I agree with Kyle, I think the double nesting can be flattened by 1 level.


test

What problem does this PR solve?
Issue Number: close #8754
Problem Summary:
What is changed and how it works?

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-all-tests

/run-all-tests


GH-37041: [MATLAB] Implement Feather V1 Reader using new MATLAB Interface APIs

Rationale for this change
Now that we've have the basic building blocks for tabular IO in the MATLAB Interface (Array, Schema, RecordBatch), we can implement a Feather V1 reader in terms of the new APIs.
This is a follow up to #37043, where a new Feather V1 internal Writer object was added.
What changes are included in this PR?

Added a new class called arrow.internal.io.feather.Reader which can be used to read Feather V1 files. It has one public property named Filename and one public method named read.

Example Usage:
>> T = array2table(rand(3))

T =

  3x3 table

     Var1        Var2       Var3
    _______    ________    _______

    0.79221    0.035712    0.67874
    0.95949     0.84913    0.75774
    0.65574     0.93399    0.74313

>> filename = "test.feather";

>> featherwrite(filename, T)

>> reader = arrow.internal.io.feather.Reader(filename)

reader =

  Reader with properties:

    Filename: "test.feather"

>> T = reader.read()

T =

  3x3 table

     Var1        Var2       Var3
    _______    ________    _______

    0.79221    0.035712    0.67874
    0.95949     0.84913    0.75774
    0.65574     0.93399    0.74313

Are these changes tested?
Yes.

Added Reader to feather/tRoundTrip.m.

Are there any user-facing changes?
No.
These are only internal objects right now.
Future Directions

Re-implement featherread in terms of the new Reader object.
Remove legacy feather code and infrastructure.

Notes

For conciseness, I renamed the C++ Proxy class FeatherWriter to Writer since it is already inside of a feather namespace / "package".

Closes: #37041

Linting failures appear unrelated to these changes.

+1


Add separate elevator room the player enters before arriving at a new floor

Currently, when the player wants to go to a new floor, they press the button in the directory and are instantly taken there. It would be great if we could change it so that after selecting the floor button, the elevator opens up for the player to enter. They would then be in the elevator interior for a short period before exiting on the desired floor.
It would be a cool bonus if while in the elevator there was a slight screen-shaking animation too while it is moving!

For this, I imagine we could pull from the decontamination map in the Javascript Test Labs. It's doing a few of the things mentioned here, minus the screen-shake, freezing the player, and level transitioning. Are there existing sounds we could use for this too?

I'm going to remove this from the current milestone so we can focus on API Academy features. This would still be a nice feature for us to work on in the future so I'll leave the issue.


⚠ ClamAV has degraded performance

In 41b2ef8, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 442 ms

Resolved: ClamAV performance has improved in 8fd224b.


mlruns directory copied when incorrect path passed

When I run:
neptune mlflow mlruns

mlruns directory is copied to the mlruns directory creating:
mlruns/
    0/
   mlruns/

Fixed in #8


Force json response for autodraw drawing agent

Within /gpt converse there is an agent that creates a prompt and determines if drawing is needed when a conversation message is sent with gpt-vision, currently, when I set response_format in the request to the model, the upstream API seems to complain saying that that parameter isn't allowed.
It may be not supported by gpt-4-vision? Otherwise, we need to find a fix so we don't depend on retries to enforce JSON.

yeah turns out gpt-4-vision doesn't support json response format so we have to stick with what we do currently


Allow authentication to be set in app.ini / migrate all authentication to app.ini

From @stevenroose on May 28, 2016 0:38
We are trying to package Gogs to work with YunoHost, but this issue affects anyone packaging Gogs automatic installation.
We want to enable LDAP authentication during installation, but when automating the installation, it is hard to inject the authentication config into the SQL table because the table is only initialized on the first run.
Since the app.ini is the place we can manipulate Gogs configuration for automated installation, ideally authentication configuration should be here too.
Since I have no idea of how authentication is implemented in general, I don't know if there are arguments why authentication should be in SQL at all. If there are no fundamental arguments, I would be willing to try and migrate authentication config to app.ini, making sure compatibility is maintained for upgrading users.
Copied from original issue: gogits/gogs#3142

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39281540-allow-authentication-to-be-set-in-app-ini-migrate-all-authentication-to-app-ini?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

From @Unknwon on July 2, 2016 15:45
Hi... actually I'm not quite understand what you're trying to describe... but set auth info in app.ini would be acceptable, it seems a dirty workaround instead of a solution.

From @Unknwon on July 7, 2016 23:53
Gogs supports theoretically unlimited authentication sources, that's why config in file is not possible.

It just seems to me that authentication settings are part of the installation configuration rather than something to do at runtime. So it should be put in app.ini instead of the database.
Many packaged versions of Gogs that are specifically made for a certain software distribution will want to automatically integrate Gogs with the authentication scheme they use during the installation period. That is currently impossible because the authentication section from Gogs can only be accessed while it is running through the web interface or through the underlying SQL DB.
So what I propose is a new app.ini section f.e. [authentication] or [ldap] where the required LDAP parameters can be provided.
Examples of apps using config files for auth (I think the ones that don't are actually very rare) are: Owncloud, Seafile, Roundcube, Ampache, Baikal and actually all of the ones that I came across when packaging apps for YunoHost.

From @jerrykan on July 8, 2016 12:48
Having to configure the authentication sources in the DB is an impediment to being able to deploy gogs using configuration management tools. I imagine it would be possible to implement any number of authentication sources using the following sort of scheme in the app.ini
[auth]
backend = ldap_ad, ldap_openldap, pam

[auth_ldap_ad]
type = ldap
... (other ldap specific settings) ..

[auth_ldap_ad]
type = ldap
... (ldap specific settings) ..

[auth_pam]
type = pam
... (pam specific settings) ..

the backend value in the [auth] section defines the priority of the authentication sources that are enabled and are references to the [auth_*] sections which contain the configuration for each authentication source.
It may require a little more processing of the app.ini file to load the configuration settings, but it should be possible.

From @jerrykan on July 9, 2016 14:2
@Unknwon my personal preference would be to keep everything in app.ini so there is only one file to configure/manage, but I don't see any major issues if it were to be implemented in another config file.

From @Unknwon on July 8, 2016 13:6
@jerrykan good point, but I think we probably should just make a new file named auth_sources.ini or auth_sources.conf?

From @Unknwon on July 9, 2016 14:15
app.ini is more about site configuration, but authentication sources are site data in my opinion.

From @jerrykan on July 10, 2016 13:19
I don't see configuring authentication backends as being any different to configuring the database or mail servers. It is site specific, generally configured during initial setup, and rarely changes. So I wouldn't really consider the it data.

@Unknwon Can you point me to where auth configuration is located? Perhaps I can try and implement the migration myself.

From @Unknwon on August 3, 2016 4:23
@stevenroose login_source table.

I don't think that storeing LDAP configuration on app.ini is a better idea. But I think It could be done via Gitea APIs. We can provide LDAP configuration API so that you can add it just call the APIs.

It does make sense to me for site configuration to be in a configuration file rather than in the database, I've actually found myself in the troubling situation of having to migrate a database table to fully replicate a configuration (rather than just copying the custom/ directory over)

Of course, we could add some subcommand to gitea admin command to finish the work.

Setting up authentication is part of the installation. Right now if you
only want LDAP users, there's a catch-22 because you need to login to
add an authentication method but you cannot login because LDAP is not
configured yet. The same holds with any other type except the default one.
I've setup quite a number of self-hosted web services and all of them
store auth config statically.
On 21-11-16 02:54, Lunny Xiao wrote:

Of course, we could add some subcommand to |gitea admin| command to
finish the work.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/go-gitea/gitea/issues/183#issuecomment-261824704,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0F3M7NQbhDhPbr4wdjhF_XrYBvYx1Dks5rAPnGgaJpZM4KzyA0.

I also think the authentication mechanism should be refactored to be explicit about which auth method is in use from the web UI. It should also help adding more complex auth methods (like OAuth/OpenID)

Or we can add LDAP or SMTP config on installation page?

For most of the systems we manage that have to use an "install page" to install/configure a system is a real pain. Every configuration management tool available makes it easy to mange plain text configuration files, hence why it is so desirable for configuration to be done in config files instead of in the DB. Even for advanced users who don't use config management tools being able to edit a file and restart the service is much easier than running some SQL on a DB or make and API request to make configuration changes. With configuration files you also don't end up in a situation where authentication breaks and you can't log into the system to make the necessary configuration changes to fix things.
Having "install pages" are useful to help new users get something up and going, but forcing advanced users to use them is an anti-feature, when all they want to do is copy a pre-made configuration file into place and be done with the configuration side of things.

So that, I think maybe https://github.com/go-gitea/gitea/issues/209 will resolve this.

@jerrykan I totally agree.  It makes sense for OpenID, but not for the different username/password types. Username/password methods with different DB types (because LDAP is just another DB to store user information) should all use the regular username/password fields. While I agree for the more exotic methods, an explicit button/whatever is good.

I agree that all (non-per-user) configuration should be possible to make via a config file.
@stevenroose but for a quick work-around, how tied is gitea/xorm to the schema version (apparently stored in the version table)? Can you just create an SQL script that would setup the bare minimum schema and values for configuring LDAP and then let the first run upgrade the schema to whatever is the current version?

For what it's worth, [at]Unknwon claims he has implemented something in Gogs, on 12th of April 2018 (GMT +8). Here's the link: https://github.com/gogits/gogs/issues/3142#issuecomment-380815756

So is this feature frozen, declined or will be implemented in the future?

I think it's waiting for someone (you?) to implement it

@strk, did you have the chance to take a look at unknwon's supposed implementation?

I worked around this with a post-configure script that I run after the app starts up:
post-configure.txt

^ That example is for adding PAM authentication

@stevenroose I didn't have a chance to look at Googs implementation but that comment  is really interesting.

Since gitea admin auth command line could manage auth source. I think this issue maybe not necessary.

According to the docs (https://docs.gitea.io/en-us/command-line/) there is only a command for oauth.
Is there any for ldap (or other sources)?
Is there anybody who are being able to fully automate install of gitea without any login first?

There's a PR to add ldap configuration but it's sort of languishing because no-one has had a chance to look at it.  (#6681)

./gitea admin auth --help
NAME:
   Gitea admin auth - Modify external auth providers

USAGE:
   Gitea admin auth command [command options] [arguments...]

COMMANDS:
     add-oauth           Add new Oauth authentication source
     update-oauth        Update existing Oauth authentication source
     add-ldap            Add new LDAP (via Bind DN) authentication source
     update-ldap         Update existing LDAP (via Bind DN) authentication source
     add-ldap-simple     Add new LDAP (simple auth) authentication source
     update-ldap-simple  Update existing LDAP (simple auth) authentication source
     list                List auth sources
     delete              Delete specific auth source

I think this issue can be closed now ...

@6543 Does the git admin auth command store the configuration in the app.ini file or in the database? if it is just updating the configuration in the database then it isn't solving the use-case outlined in this issue.

no auth is stored in db

closing as via CLI is how we've chosen to go, and this method works for many different packagings of Gitea, even our Helm-chart uses the CLI and I've seen customized docker images use entrypoints with the CLI.


Documentation missing: How to wrap a struct with lifetime?

I have a struct with a lifetime:
pub struct Foo<'a> {
    // ...
}

How to wrap that?

So it seems like this is not possible.
What I did to ship around this issue is introducing a (static) cache where objects are fetched again and again from, so I do not run into a lifetime issue.
This is a clumsy solution, but it works for me. The result can be seen here: https://github.com/matthiasbeyer/imag/pull/847. By now it works fine and I hope it will work with my bindings. They are almost finished (the first step towards a full-featured ruby binding for my libraries at least, not the complete bindings).

Hey @matthiasbeyer!
Yes, ruru does not support structs with lifetimes for now and I haven't found a way to easily implement this.
On the other hand, if a struct has a lifetime, it has a reference to another Rust object. When a struct is moved to a Ruby object with wrap_data, it kinda leaves Rust world and moves to a Ruby world until ruru fetches it back with get_data. During that period of time the object which is referenced by current struct, can be freed and borrow checker cannot guarantee that. That's why I believe only structs with 'static lifetimes can be wrapped with wrap_data, though I will need to check this.


Updating Control Tower UI with new Guardrails

Hello,
I was just wondering if these new SCPs and Config rules could appear as new Guardrails in the Control Tower console?
Cheers,

@charyeezy Currently AWS Control Tower does not support custom guardrails so there is no integration with guardrails provided with AWS Control Tower and those external, such as those applied with this solution. Hence, external guardrails for the time being will not appear in the AWS Control Tower console. Custom guardrails is a roadmap item that the product team is pursuing.

Thank you for your response. I will be on the lookout.


Connection marked as broken because of SQLSTATE(08S01) , ErrorCode(0)

Environment
2019-05-23 13:17:26.350 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : HikariPool-1 - configuration:
2019-05-23 13:17:26.356 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : allowPoolSuspension.............false
2019-05-23 13:17:26.357 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : autoCommit......................true
2019-05-23 13:17:26.357 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : catalog.........................none
2019-05-23 13:17:26.357 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : connectionInitSql...............none
2019-05-23 13:17:26.357 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : connectionTestQuery.............none
2019-05-23 13:17:26.357 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : connectionTimeout...............30000
2019-05-23 13:17:26.357 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : dataSource......................none
2019-05-23 13:17:26.358 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : dataSourceClassName.............none
2019-05-23 13:17:26.358 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : dataSourceJNDI..................none
2019-05-23 13:17:26.358 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : dataSourceProperties............{password=}
2019-05-23 13:17:26.359 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : driverClassName................."com.mysql.cj.jdbc.Driver"
2019-05-23 13:17:26.359 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : healthCheckProperties...........{}
2019-05-23 13:17:26.359 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : healthCheckRegistry.............none
2019-05-23 13:17:26.359 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : idleTimeout.....................600000
2019-05-23 13:17:26.359 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : initializationFailTimeout.......1
2019-05-23 13:17:26.359 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : isolateInternalQueries..........false
2019-05-23 13:17:26.360 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : leakDetectionThreshold..........0
2019-05-23 13:17:26.360 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : maxLifetime.....................1800000
2019-05-23 13:17:26.360 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : maximumPoolSize.................10
2019-05-23 13:17:26.360 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : metricRegistry..................none
2019-05-23 13:17:26.360 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : metricsTrackerFactory...........none
2019-05-23 13:17:26.361 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : minimumIdle.....................10
2019-05-23 13:17:26.361 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : password........................
2019-05-23 13:17:26.362 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : poolName........................"HikariPool-1"
2019-05-23 13:17:26.362 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : readOnly........................false
2019-05-23 13:17:26.362 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : registerMbeans..................false
2019-05-23 13:17:26.363 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : scheduledExecutor...............none
2019-05-23 13:17:26.363 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : schema..........................none
2019-05-23 13:17:26.363 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : threadFactory...................internal
2019-05-23 13:17:26.363 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : transactionIsolation............default
2019-05-23 13:17:26.363 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : username……………………”user”
2019-05-23 13:17:26.363 DEBUG 8 --- [ main] com.zaxxer.hikari.HikariConfig : validationTimeout...............5000
Connection 1 :
2019-05-28 02:19:56.776 DEBUG 8 --- [onnection adder] com.zaxxer.hikari.pool.HikariPool : HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@3cfb82b
2019-05-28 02:43:34.120 WARN 8 --- [pp-queue-prod-1] com.zaxxer.hikari.pool.ProxyConnection : HikariPool-1 - Connection com.mysql.cj.jdbc.ConnectionImpl@3cfb82b marked as broken because of SQLSTATE(08S01), ErrorCode(0)
2019-05-28 02:43:34.121 DEBUG 8 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase : HikariPool-1 - Closing connection com.mysql.cj.jdbc.ConnectionImpl@3cfb82b: (connection is broken)
Connection 2 :
2019-05-28 02:18:50.900 DEBUG 8 --- [onnection adder] com.zaxxer.hikari.pool.HikariPool : HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@300cfd48
2019-05-28 02:43:15.554 WARN 8 --- [pp-queue-prod-1] com.zaxxer.hikari.pool.PoolBase : HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@300cfd48 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2019-05-28 02:43:15.555 DEBUG 8 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase : HikariPool-1 - Closing connection com.mysql.cj.jdbc.ConnectionImpl@300cfd48: (connection is dead)
Query : Why connection 1 got broken when maxLifeTime is set to 30 minutes? IdleTimeout is 10 minutes but it won’t be applicable as maximumPoolSize is same as minimumIdle.
Similar observation is for connection 2, it was found to be dead/Closed.
Can you please help me understand the cause of the above observation.

@sahilarya2000 The database is clearly closing connections after roughly 25 minutes.  This could be due to a configuration on the database-side, or a timeout imposed by some infrastructure component in-between the application and the database -- such as firewall.
If you want a definitive answer, you'll need to start troubleshooting by looking the DB configuration, and the network path between the application and the database.  If you are not so curious, then simply lower the maxLifetime as suggested by the log message, to something like 20 minutes.

now, i have this exception, too, it's sure that it dose not timeout about connection, because i restart server and request http interface then get this exception!

I just started seeing intermittent Connection marked as broken because of SQLSTATE(08S01) errors the other day as well. Have not been able to figure out what is going on. EC2->Aurora MySQL using HikariCP-3.2.0

https://stackoverflow.com/questions/54804275/hikaripool-1-connection-marked-as-broken-because-of-sqlstate08s01-errorcode this may help someone

Anybody full understood?

I just started seeing intermittent Connection marked as broken because of SQLSTATE(08S01) errors the other day as well. Have not been able to figure out what is going on. EC2->Aurora MySQL using HikariCP-3.2.0

Did you get any solution for this issue. I'm also getting same error.


Exec as argument of next Exec calls

Writing #159 I thought that it could be good to have a way to use the stdout of a command executed with Exec as parameter of  a following Exec call.
For being even more useful, it could be possible to support several Exec calls.
And to even go further (sorry, I'm blowing my mind), they could also be used as values to replace on a specific format string.
NOTE I'm not familiar with the script implementation, so I don't know if this is feasible, or if it's hard to implement or not.
Let me write some example of an hypothetical API for each of the above wacky ideas.
Right now, script allows to do this
script.Exec("echo hello world").Exec("cut -d ' ' -f 1").Output()

This translate to the shell script
echo hello world | cut -d ' ' -f 1

I'm exposing an example with shell script that I think that I cannot translate using script to a pipe execution as before; each numbered item relates, in the same order, to the three things that I exposed at the beginning of this issue.
For keeping the examples concise, they are ilustrative examples rather than a specific use case that I'm having.

 ls $(lsb_release -cs)

 ls $(lsb_release -cs) $(dpkg --print-architecture)

 echo  "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian $(lsb_release -cs) stable"

In script isn't currently possible without having to execute each of them speartelly. I'm going to show how script could offer it with some unexisting methods without stating if their names are good nor if it's a good idea to have them.

There should be somehow to indicates that the output of the previous Exec is passed as an argument on the following Exec call.

script.Exec("lsb_release -cs").AsArg().Exec("ls").Output()

There should be somehow as 1 but with the possibility to pipe several Exec calls.

script.Exec("lsb_release -cs").AsArg().Exec("dpkg --print-architecture").AsArg().Exec("ls").Output()

There should be somehow to indicates that the outputs are kept as an internal value that can be referenced in the formatter.

script.Exec("lsb_release -cs").AsFmt().Exec("dpk --print-architecture").AsFmt().Exec(`echo  "deb [arch=@{1} signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian @{2} stable"`).Output()

In this case I used echo inside of an Exec, but it could be extended to each source functions that receive a string as a parameter, hence it could be also done as
script.Exec("lsb_release -cs").AsFmt().Exec("dpk --print-architecture").AsFmt().Echo("deb [arch=@{1} signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian @{2} stable").Output()

It may help to know that you can use ExecForEach with a Go template. For example:
script.Exec("lsb_release -cs").ExecForEach("ls {{.}}").Stdout()

Thank you, I missed that method.
Does it solve the 3 use case?


fix: set contents of complementary sidebar based on attention

Resolves #7650
Resolves #7825

@ZaymonFC I think that should be unneeded now... I meant to remove it. Will test without it before landing


Add username autocompletion popup menu

Pull request checklist:

[X] CHANGELOG.md was updated, if applicable

Description
This PR adds a popup menu for autocompleting usernames with an '@' prefix, similar to the existing one for emotes with ':'.

Showing the popup is an optional feature with a toggle setting turned on by default, when the setting is off you can still autocomplete as usual.
The strategy for finding usernames to complete should be the same as for the existing @ autocompletion.

When testing, also test the emote autocompletion menu, as this addition can affect it, and the implementation is also inspired by it.
Also looking for feedback on the appearance of the menu.
Closes #1979

Emote and username autocompletion menus work as intended for me.
One thing about the appearance. I think it would be nice to have some sort of indicator like DankChat does to indicate that it is a person. I provided some examples below:
DankChat:

Current PR:

Requested Changes:

Also the username doesn't seem to be vertically centered.

I dislike the code duplication. I would probably have reused the existing :-popup code and allowed it to show text without images. I haven't tested the functionality yet.

One thing about the appearance. I think it would be nice to have some sort of indicator like DankChat does to indicate that it is a person.

Not sure about this. The web chat equivalent contains only text, and unlike the DankChat example you provided, here it is clear when you are auto completing an emote vs a username based on the prefix used. Open to more opinions about this though.

Also the username doesn't seem to be vertically centered.

I think this is also the case in the emote completion popup, just less noticeable. I can look into it though.

I dislike the code duplication. I would probably have reused the existing :-popup code and allowed it to show text without images.

I mostly agree, it just wasn't instantly obvious what the best way to combine this with the existing emote menu is, and I wanted to get something that works quickly. I can definitely try to do some more combining of the functionality and improve the code. If you have any more specific ideas I'd like to hear them.

I combined the code for the emote completion menu and the new username menu, now definitely test the emote completion as well when testing as it is handled by the same code.
Also usernames should be vertically centered now.


Update checkout discount calculations

I want to merge this change because...

I want to add discount calculations based on include_taxes_in_prices site setting
(SALEOR-4943)
Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-4943 Update checkout's discount calculations

Depends on #8103


[vcpkg baseline][many ports] Fix build error

Fix baseline issues, these changes need to fix togather, since they affected each other in CI testing.

[X] wxwidgets
[X] mlpack
[X] embree2
[X] embree3
[ ] opencv4
[ ] zxing-cpp
[ ] dbow2

Fix wxwidgets bug:

F:\vcpkg\buildtrees\wxwidgets\x86-windows-dbg\libs\stc\cotire\wxscintilla_CXX_prefix.hxx(4): fatal error C1083: Cannot open include file: 'F:\vcpkg\buildtrees\wxwidgets\src\54f4f955a1-1de49a51d0\build\cmake\lib\stc\CONFIG': No such file or directory

It's becuase the parameter wxSCINTILLA_PREC_HEADER is empty:
if(wxBUILD_PRECOMP)
    # The auto-generated header causes undefined members and identifiers in the
    # standard c++ headers when using clang.
    # Do not disable precompiled headers entirely but use the main Scintilla
    # header as prefix header so there is at least a small speedup.
    if ("${CMAKE_CXX_COMPILER_ID}" MATCHES "Clang")
        set(wxSCINTILLA_PREC_HEADER "${wxSOURCE_DIR}/src/stc/scintilla/include/Scintilla.h")
    endif()
    wx_target_enable_precomp(wxscintilla ${wxSCINTILLA_PREC_HEADER})
endif()

causes the leaked field CONFIG to be set in set_target_properties in function wx_target_enable_precomp.
Then, get_property obtained the property and read its file path, resulting in the generation of the wrong wxscintilla_CXX_prefix.hxx:
/* cotire.cmake 1.8.0 generated file */
/* F:/vcpkg/buildtrees/wxwidgets/x86-windows-dbg/libs/stc/cotire/wxscintilla_CXX_prefix.hxx */
/* cotire.cmake 1.8.0 generated file */
/* F:/vcpkg/buildtrees/wxwidgets/x86-windows-dbg/libs/stc/cotire/wxscintilla_CXX_prefix.hxx */
#ifdef __cplusplus
#include "F:\vcpkg\buildtrees\wxwidgets\src\54f4f955a1-1de49a51d0\build\cmake\lib\stc\CONFIG"
#endif

which is not exist.

Fix mlpack configure bug, already fixed in upstream https://github.com/mlpack/mlpack/commit/52e123e56792638c957d0229b001ae14a9e94a75.

@cenit When building opencv4:x86-windows or opencv4:x64-windows, we met a error message:
CMake Error at cmake/OpenCVGenConfig.cmake:49 (export):
  export Export set "OpenCVModules" not found.
Call Stack (most recent call first):
  CMakeLists.txt:923 (include)

And for opencv4:x64-linux:
The following empty directories were found:

    /home/usr/work/vcpkg/packages/opencv4_x64-linux/debug

If a directory should be populated but is not, this might indicate an error in the portfile.
If the directories are not needed and their creation cannot be disabled, use something like this in the portfile to remove them:

    file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/a/dir" "${CURRENT_PACKAGES_DIR}/some/other/dir")

Found 1 error(s). Please correct the portfile:
    /home/usr/work/vcpkg/ports/opencv4/portfile.cmake

Can you please take a look?
Thanks.

Fix embree2/embree3 CI test failures:
CMake Error in CMakeLists.txt:
  You have set CMAKE_BACKWARDS_COMPATIBILITY to a CMake version less than
  2.4.  This version of CMake only supports backwards compatibility with
  CMake 2.4 or later.  For compatibility with older versions please use any
  CMake 2.8.x release or lower.

Reference https://cmake.org/cmake/help/latest/policy/CMP0001.html#policy:CMP0001

The opencv4 issue is OPENCV_MODULES_BUILD always be cleaned after insert items.
The dbow2 and zxing-cpp regressions are related to opencv4 regression.

The opencv4 failures start from https://github.com/microsoft/vcpkg/commit/b369b110b16b149066271a09ee56f1b9dcaec7d6.
Related PR https://github.com/microsoft/vcpkg/pull/17955

i saw few days ago that opencv is not even tested in many CI configs... i will take a look and send fixes asap (might take a couple of days, sorry)

yeah I can confirm anyway that in the last 24h OpenCV was broken for everybody here on vcpkg.
Again a PR was merged and that broke all my "bleeding edge" pipelines. They are really bleeding....

this is making the fix much more urgent also for me

#17991 will revert #17955 @JackBoosY

/azp run

@dan-shaw, could you help merge this PR?


Failing at work, seek help

I successfully uploaded my data to the website, but my job failed after running for a long time. I don't know which step I went wrong. I hope you can give me guidance. Best wishes to you.

Hi Shuhui-Dong,
Please direct help requests to<EMAIL_ADDRESS>The NP Analyst team


PR: Initial "Docker" support.

This PR builds on top of https://github.com/AcademySoftwareFoundation/OpenColorIO-Config-ACES/pull/5 and provides initial Docker support. I haven't timed the container build but it is quite long because it builds OCIO and pulls a few dependencies for LaTeX.
Assuming the repo is cloned, pointed to that branch and you have cd in the root directory:
To build the container:
docker build -t aswf/opencolorio-config-aces:latest .

To open a shell inside it:
docker run -it -v ${PWD}:/home/aswf/OpenColorIO-Config-ACES aswf/opencolorio-config-aces:latest /bin/bash

To build the reference config from within the container:
invoke build-reference-config

Or from outside:
invoke docker-run-build-reference-config

Hello!
It has been 14 days, shall we? :)


Thoughts on changing font size location

I find myself doing this very often:
  title: {
    fontFamily: Fonts.bold,
    fontSize: Metrics.fonts.medium,
    color: Colors.charcoal
  },

I think it would feel a lot "cleaner" to do this:
  title: {
    fontFamily: Fonts.bold,
    fontSize: Fonts.size.medium,
    color: Colors.charcoal
  },

It would be a relatively easy change. When i thing of "font size" i don't think of the "metrics" object, i think of the "font" object.
Make sure verify the following before submitting an issue.

[x] Issue does not already exist
[x] You have example code or some other reproduce experiment that we can verify

I could get on board with that.
In spirit, it's similar to how we're switching styles to live under both containers and components.
It's a scoping concern.  Makes sense.
How far do we go though?
Do colors come under fonts too?  (My gut says no)

No. Font sizes are specific to fonts. Colors are generic.

I like how it reads.  You have my vote.

I'll submit a quick PR and we can discuss there.


Add unique submission ID to group SUPERB submissions

In SUPERB we have one prediction repo per task, so we need a way to group them together. Ideally there would be a submission ID in the model card which is created automatically one a push.

No longer relevant since the evaluation will now be handled by s3prl on the SUPERB infra


Move slangc to use the new compile API.

I’m currently using slangc for my projects. Is there somewhere I could look to find out more about the new API?

@natevm sorry for the delay! There's some info on this here: https://shader-slang.com/slang/user-guide/compiling.


Turn off depandabot for this repo

We don't need dependabot for this repo, we effectively get it everything we update the SDK branch were on

Would be a huge quality of life win if someone gets a chance


iOS Build Error: 'kSecMatchSubjectWholeString' symbol not found

Hello,
I am developing a universal SDK that depends on the rust-security-framework for using Keychain functionalities. After updating this dependency recently, I encountered a compilation issue on the iOS platform.
Error Output
Undefined symbols for architecture arm64:
  "_kSecMatchSubjectWholeString", referenced from:
      security_framework::item::ItemSearchOptions::search::h115ebc3a4f9ba099 in libxxx-kit_static.a[arm64][1774](security_framework-3f9eb5a707bf396a.security_framework.a39d3ed3f5cf992f-cgu.08.rcgu.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Environment

iOS version: 17.4.1
Xcode version: 15.3
Language: Swift + Rust
rust-security-framework version: 2.11.0

Documentation Reference
Apple Developer Documentation link that states kSecMatchSubjectWholeString  is only available on macOS.
Thank you for looking into this issue. I appreciate any guidance or updates you can provide.

#204 Merged

This PR #204 may require a new release to take effect. May I ask if @kornelski has any plans to release a new version recently? I will keep this issue open until the problem is confirmed resolved.

Note: Use the cargo update -p security-framework --precise 2.10.0 command to roll back to version v2.10.0 to ensure iOS can compile correctly.

Hi @kornelski, you may remember me, I'm the person who contributed the iOS support for this crate a few years ago. I see that @sfackler has marked this crate as needing a maintainer, and I see that things on the iOS side have gotten into a bit of disrepair. I am, in fact, willing to help maintain this crate, as I am still very active on both macOS and iOS and use this crate often.  Feel free to ping me via email if this is of any interest to you.

@brotskydotcom Yes, please. Help is very welcome.

OK, I'll try to review the outstanding issues and make some recommendations/submit some PRs over the next week or so. I think probably there are a few issues (such as this one and #206) that are probably worth releasing the fixes for in the near term.


NullPointerException on FeignClientFactoryBean

I am trying to write integration test to my service.
My service is using Feign to communicate with another service.
When i am running the test i am getting the following NPE:
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.intel.swiss.microservices.nbocollectorservice.iface.IDataJobService': FactoryBean threw exception on object creation; nested exception is java.lang.NullPointerException
	at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:175)
	at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:103)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1606)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:254)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:207)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.addCandidateEntry(DefaultListableBeanFactory.java:1289)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:1258)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1094)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1059)
	at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:835)
	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:741)
	... 77 common frames omitted
Caused by: java.lang.NullPointerException: null
	at org.springframework.cloud.netflix.feign.FeignClientFactoryBean.loadBalance(FeignClientFactoryBean.java:147)
	at org.springframework.cloud.netflix.feign.FeignClientFactoryBean.getObject(FeignClientFactoryBean.java:168)
	at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:168)
	... 88 common frames omitted

The problem is that the Targeter interface is null, although it is autowired to the factory. Also i made sure that the FeignAutoConfiguration class is loaded on the test and it is. I see in the FeignAutoConfiguration the following:
@Configuration
	@ConditionalOnClass(name = "feign.hystrix.HystrixFeign")
	protected static class HystrixFeignTargeterConfiguration {
		@Bean
		@ConditionalOnMissingBean
		public Targeter feignTargeter() {
			return new HystrixTargeter();
		}
	}

	@Configuration
	@ConditionalOnMissingClass("feign.hystrix.HystrixFeign")
	protected static class DefaultFeignTargeterConfiguration {
		@Bean
		@ConditionalOnMissingBean
		public Targeter feignTargeter() {
			return new DefaultTargeter();
		}
	}

None of those methods are invoked during runtime of the test but other beans in the class are created.
Spring Cloud Camden release train
Spring Boot 1.4.2

This is my test configuration:
@RunWith(SpringRunner.class)
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT, classes = Application.class)
@TestPropertySource(properties = {
    "debug=true"
})
@DirtiesContext

@SpringBootApplication
@EnableFeignClients
@EnableHystrixDashboard
@EnableDiscoveryClient
@EnableHystrix
public class Application  {
...
}

@ezraroi what specific version are you using? Targeter hasn't been autowired since https://github.com/spring-cloud/spring-cloud-netflix/commit/f30e8b7b4630db74b1cccf436fb3f50f94618427 in Camden.SR1. SR3 is the latest.

I am on Camden.Release

Duplicate of #1366 which has been fixed for two releases.

So should i move from release to SR3 or just remove dev tools?

The fix is in SR1, so update to at least that or the latest.

Isnt Camden.Release is the latest SR3?

SR3 is the latest.

Cool thanks. I was sure release points to the latest

no, it doesn't


[added] Mention shouldCloseOnOverlayClick dependency

Mention shouldCloseOnOverlayClick dependency on onRequestClose in order to function properly.
Changes proposed:

add mention that shouldCloseOnOverlayClick depends on having the onRequestClose  prop in order to function properly when it's set to true

Acceptance Checklist:

[x] All commits have been squashed to one.
[x] The commit message follows the guidelines in CONTRIBUTING.md.
[x] Documentation (README.md) and examples have been updated as needed.
[x] If this is a code change, a spec testing the functionality has been added.
[x] If the commit message has [changed] or [removed], there is an upgrade path above.

Coverage remained the same at 87.173% when pulling 43a339b5259c481fb5ac5eedb1eb8c2535ad9cbb on whitecrownclown:patch-1 into a2d5c4e558c19a6c1277a0128e4263de0fb6bbc6 on reactjs:master.

Coverage remained the same at 87.173% when pulling 43a339b5259c481fb5ac5eedb1eb8c2535ad9cbb on whitecrownclown:patch-1 into a2d5c4e558c19a6c1277a0128e4263de0fb6bbc6 on reactjs:master.

@whitecrownclown Thank you!

Coverage remained the same at 87.173% when pulling 43a339b5259c481fb5ac5eedb1eb8c2535ad9cbb on whitecrownclown:patch-1 into a2d5c4e558c19a6c1277a0128e4263de0fb6bbc6 on reactjs:master.

Related #462.

@whitecrownclown can you add to your commit message [chore]?

@diasbruno I believe you already did, i'm not really used to contributing to github yet, i appreciate any help in getting used to it.

@whitecrownclown that was there title of the issue :).
On your last git commit, try to find on your tool where you can amend or edit to the commit message (or on your terminal you can git commit --amend -m "[chore] {the message}".

@whitecrownclown Thank you so much.


Improve the UX of the Home Page

Align the buttons and space them correctly in the home HTML File.

@arjungarg07  I would like to work on this issue, can you please assign it to me?

@arjungarg07 Please assign it to me


Implement networked states with inputs, trusted, auth, etc.

Implement a new networking model with GameStates full of inputs processed in a single update/tick period.

[ ] Implement a GameState interface
[ ] Implement a Input interface
[ ] Implement an Authorization interface
[ ] Handle all of the above.

Obsolete.


Config param INLINE_TEMPLATES not working correctly

...
  /**
   * The flag to include templates into JS app prod file.
   * Per default the option is `true`, but can it can be set to false using `--inline-template false`
   * flag when running `npm run build.prod`.
   * @type {boolean}
   */
  INLINE_TEMPLATES = argv['inline-template'] !== 'false';
...

If you will try to set it to false and make a npm run build.prod, it will not build a correct build, because your app.js will try to load templates from root directory.

Thanks for the issue! We should remove this option since we always inline the templates in prod and never in dev.

@mgechev , I'm not using this one, just want to notify you. I will close the issue.

Lets reopen it in order to remember to remove the option tomorrow :-)

@mgechev , pull request is ready for this one.

Awesome! Thanks!

I was correctly working for me.
Just need to specify full path to the template, Ex: templateUrl: "\app\client\path\to\file.html"

@troyanskiy , we know that, but, it's will be a deprecated feature.

I'see...