PUT send is doing Quotation on json payload

Hi,
i need to send via PUT an octetstream/json element via put. requests is quoting the full string. Example:
    testdata = '[{"cid": "1","uuid": "sdasd"}]'
    response = requests.put(requestUrl, auth=self.auth, json=testdata)

can be seen in Wireshare like this:
"[{"cid": "1","uuid": "sdasd"}]"
if i use POST it is unquoted.
My remote REST Interface is not able to handle the quoted strings. I wasn't able to find any option where i can turn of the quotation.

If you read the documentation closely, you'll see your code should look like:
    testdata = [{"cid": "1","uuid": "sdasd"}]
    response = requests.put(requestUrl, auth=self.auth, json=testdata)

the response is within a class which contains the auth definitin like:
self.auth = HTTPBasicAuth(username, password)
and i use this later on.
And how does the auth content influence the payload?

@czerwe

I don't understand your question
The issue tracker is not a support forum. Please use StackOverflow

I am sorry about missleaded:
if found out that this seems to work:
testdata = [{"cid": 1, "uuid":2}]
response = requests.put(requestUrl, auth=self.auth, headers={"Content-Type": 'application/json'}, data=json.dumps(testdata))
using jsons doing quotation. From my point it's a missbehavior of the json handler in the session.
Nevertheless sorry.

It is not an error in the Json handler. The json handler does not accept a string, it accepts the Python object directly. The difference between what you provided and what @sigmavirus24 gave is this:
testdata = '[{"cid": "1","uuid": "sdasd"}]'
testdata = [{"cid": "1","uuid": "sdasd"}]

I was already wondering.
Your right. I tried so many things that some error output from the response miss leaded me.
Thank you both. Next time i will ask in StackOverflow first.
Sorry.


Duplicate Correction Suggestions

The word "punctation" (and similar variations, e.g. "punctations" and "punctuations") will produce two suggestions for replacing the word with "punctuation". Produced on the WriteWithHarper website.

Thanks for pointing this out! You've found a relatively obscure bug, but I've managed to locate and squash it as of the latest commits.


Running executables sporadically fails with ETXTBSY (Text file busy)

Current Behavior
Running executables concurrently (with Exec, project.exec, ExecOperations.exec plus the JavaExec versions) can fail sporadically if the Gradle daemon process has recently written a file.
Expected Behavior
This should work
Context (optional)
In https://github.com/gradle/gradle/pull/30269, I removed the use of native-platform's ProcessLauncher in favor of the JDK's built-in ProcessBuilder.
On non-Windows platforms, we were already using an implementation of ProcessLauncher that used ProcessBuilder; however, ProcessLauncher also had a workaround to only launch a single executable at a time:
https://github.com/gradle/native-platform/blob/master/native-platform/src/main/java/net/rubygrapefruit/platform/internal/WrapperProcessLauncher.java#L33-L37
This appears to be related to a Java platform bug which is a common problem across other programs on Linux/Unix.  Go has a good explanation of the problem.
Self-contained Reproducer Project
You can reproduce this outside of Gradle with this Groovy script:
def threads = []
1000.times { idx ->
  threads << new Thread({
    def script = new File("script$idx")
    script.text = """#!/bin/bash
    echo "Hello $it"
    """
    script.executable = true
    def pb = new ProcessBuilder(script.absolutePath)
    def p
    //synchronized(Object.class) {
       p = pb.start()
    //}
    p.waitFor()
    script.delete()
  })
}
println("starting")
threads.each { it.start() }
println("waiting")
threads.each { it.join() }
println("done")

Putting the synchronized block back in "fixes" it.
Gradle version
8.11
Gradle version that used to work
<8.11
Build scan URL (optional)
No response
Your Environment (optional)
No response

Any updates here? We'd really love a fix for this so we can adopt 8.11.*

Fixed with:

#31283


Refactor Ethfinex class

The Ethfinex class is no longer returning price data when queried. It seems that some changes may have been made to the underlying API in the last 6-9 months. They have also rebranded to https://deversifi.com
To do:

Investigate API changes and refactor class to restore functionality
Change branding to reflect their new site "deversifi"

DeversiFi docs:
https://docs.deversifi.com/?version=latest

Congratulations! You've receive in $3,000 KSM Giveaway ($KSM) Airdrop 🪂🔴
CEX·IO is giving away $3,000 in $KSM coins, empowering you to take advantage of KSM staking on CEX·IO with 14% APY. Join the giveaway and earn a chance to win up to $500. Stake Kusama with CEX·IO, get high rewards and win prizes!
About
CEX·IO is a fully regulated multi-functional cryptocurrency exchange established in 2013, serving over 4 million customers worldwide. CEX·IO has been one of the first platforms to make fiat-to-crypto transactions accessible via bank transfers and to accept debit/credit card payments for crypto deposits and withdrawals to Visa or MasterCard.
→ How to join the $3,000 KSM Giveaway Airdrop?
Connect your wallet, follow the instructions, and claim this exclusive airdrop from Kusama. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

Step-by-Step Guide ''CEX·IO Kusama Giveaway''
Access the Kusama platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Use the connect method to interact with the contract
💰 Connect and receive your tokens
→ Claim Your $KSM Today

Congratulations! You've been chosen to receive a $7,000 Rewards. 🪂🔴
Trading and Launch Rewards are live on dYdX Chain! ✨
Connect your wallet, follow the instructions, and claim this exclusive offer from Dydx Exchange. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

🚀 Claim Your Rewards Now! Check Eligibility
Access the Dydx Exchange platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Connect your wallet twice
📋 Register on the platform
💰 Claim your Rewards, up to $2,000!

@dydxprotocol

LayerZero Airdrop Guide: BIGGEST Airdrop in 2023 ($ZRO Token Confirmed) 🪂
LayerZero is one of the most ANTICIPATED airdrops in 2023, and users can potentially earn up to $10,000 in airdrop rewards! This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Claim Now on Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Share on Social Media:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
FFeliziani, @redtree0, @benjamindmc61, @ZombieChowder11, @william-zh, @cart0uche, @LeonKennedy, @mkorat1717, @dselmanovic, @woahdy, @omerdn1, @flux0uz, @nimitzufo, @whitedoghub, @shellhue, @vipycm, @omnimark, @sulexiu, @mengguang, @sudhamstarun

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!


In requestBuilder._getFacetFilters when state.hierarchicalFacetsRefinements is parsed - it only process the first element/value

Our issue:
We have the following situation:

A brand menu filter (HierarchicalMenu widget), which contains root brands and their sub-categories.
It seems that HierarchicalMenu menu allows faceting by only one value - currently selected option.
We have a use case where we need to add one or more additional values to the above one - in particular - to filter by the selected brand/sub-brand and in addition with None (adding OR filter).
We tried to use onSearchStateChange to inject dynamically the additional facet filter, but seems that does not works for HierarchicalMenu since it only process the first element from state.hierarchicalFacetsRefinements.
Also in case of fixing the above, consider changing the behaviour of the HierarchicalMenu widget as well - to support multi-values selection.

Our widget looks like this:
 <HierarchicalMenu
     key="brandMenu"
     attributes={['brand.lvl0', 'brand.lvl1']}
     separator="/"
     defaultRefinement={defaultRefinement}
     showParentLevel
  />

and
class App extends Component {
   constructor(props) {

  ............

      this.searchParams = {
        hitsPerPage: 60,
        disjunctiveFacetsRefinements,
        filters,
        facetFilters
      };
    }

.............

  handleSearchStateChange(nextSearchState) {
    if (!this.mounted) {
      return;
    }
    onSearchStateChange(nextSearchState);

    const dynamicBrandFilters = ['brand.lvl0:None'];

    this.searchParams.facetFilters = {
      ...this.searchParams.facetFilters,
      ...dynamicBrandFilters,
    };

    this.setState({ searchState: nextSearchState });
  }
}

and
 <InstantSearch
   searchClient={this.algoliaClient}
   indexName={this.props.indexes.products}
   searchState={this.state.searchState}
   onSearchStateChange={this.handleSearchStateChange}
   resultsState={this.resultState}
 >
<Configure {...this.searchParams} />

Expected behaviour:

We can dynamically add one or more additional (OR) facet filters to the  HierarchicalMenu current refinement, using onSearchStateChange.

Looking forward for any feedback or suggestion to workaround this (if possible).
Thank you in advance!

What you're trying to achieve seems to be a "disjunctive hierarchical menu". This feature is not supported in our JavaScript Helper (the underlying library that manages the state) because it would trigger too many requests to the Algolia API.
If despite this technical constraint you'd still like to implement this feature, the only solution as of now would be to see how the Helper manages hierarchical facets and to support multiple selections in a custom hierarchical menu widget.
Closing because duplicate of #1658. You can subscribe to this issue to be notified when we plan to support this feature.


HARP-13721: update Prettier to v2

Signed-off-by: Daniele Bacarella<EMAIL_ADDRESS>Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

This is a separate PR from #2014 as it touches several files and introduces minor modifications to the code style.
Prettier v2

 arrowParens is set to "always" by default, before it was "avoid" -https://prettier.io/docs/en/options.html#arrow-function-parentheses
This rule was overridden in .prettierrc.json to stick with the previous style in use.

trailingComma is set to "es5" by default, before it was "none" - https://prettier.io/docs/en/options.html#trailing-commas
This rule was overridden in .prettierrc.json to stick with the previous style in use.

Prettier now insert a space before the parenthesis and the keyword function, for example:
const foo = function() {...} -> const foo = function () {...}
It doesn't provide a rule to suppress it and I couldn't find a workaround either

This is a separate PR from #2014 as it touches several files and introduces minor modifications to the code style.
Prettier v2

 arrowParens is set to "always" by default, before it was "avoid" -https://prettier.io/docs/en/options.html#arrow-function-parentheses
This rule was overridden in .prettierrc.json to stick with the previous style in use.

trailingComma is set to "es5" by default, before it was "none" - https://prettier.io/docs/en/options.html#trailing-commas
This rule was overridden in .prettierrc.json to stick with the previous style in use.

Prettier now insert a space before the parenthesis and the keyword function, for example:
const foo = function() {...} -> const foo = function () {...}
It doesn't provide a rule to suppress it and I couldn't find a workaround either


Plugin basics using PHP_CS, WPCS and namespacing

This pull request adds a PHP_CS configuration file and formats all files according to PHP and WordPress Coding Standards.
It also uses namespacing to make the plugin more portable and simplify notation of its components.
See https://github.com/WordPress/WordPress-Coding-Standards

Replaced by pull #3 because of branch renaming.


the block is not ou

The node is running normally, but the block is not out, what is the reason? The key is also placed in the Data directory

@binny1024 Can you provide some more details on the issue are you having?

Thank you very much for your attention, the problem has been resolved, it is caused by the port not being fully open.


IDENTITY-6399 [IDP Configs] [Connectors & Authenticators] Doesn't allow saving empty values for mandatory fields when they are disabled

In the IDP configuration

configure an authenticator or a connector
Save the configs
Disable the authenticator or connector
remove all fileds
Press Update button
Give an error saying that mandatory fields are missing.

Then to save it user need to fill the mandatory fields.
Instead, if the Connector or the Authenticator is disabled it should not give an error saying that the mandatory fields are missing.
Labels
Type: Bug
Priority: Normal
Component/s: identity-provider
Severity: Major
Estimated Complexity: Moderate
Issue migrated from: https://wso2.org/jira/browse/IDENTITY-6399

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Add cookie_domain when clearing sessions #65

Add a cookie_domain header part when clearing sessions, in case it exists (see https://github.com/alex-oleshkevich/starsessions/issues/65 )

Thank you! Can we have a test for this?

Thank you! Can we have a test for this?

Sure thing, will update after work today!


feat!: add ReferrerFinder to Repository interface

Resolves #356

Codecov Report

Merging #357 (9c3efe6) into main (f701e60) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #357   +/-   ##
=======================================
  Coverage   72.52%   72.52%
=======================================
  Files          38       38
  Lines        3945     3945
=======================================
  Hits         2861     2861
  Misses        805      805
  Partials      279      279

Impacted Files
Coverage Δ

registry/repository.go
0.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[filebeat] document probe workaround for kafka output

This commit document the workaround to work with Filebeat output which don't support testing.
This is required as the default readiness probe use filebeat test output command.
Fixes #694

backported to 6.8, 7.8and 7.x branches


Uncaught TypeError: afterglow.getPlayer(...).pause is not a function

The following code:
$(document).ready(function(){
	afterglow.getPlayer("UNIQUE_VIDEO_ID").pause();
 });

or
$( ".afterglow" ).each(function( index ) {
	afterglow.on($(this).attr("id"), 'ready', function(){
		afterglow.getPlayer($(this).attr("id")).pause();
	});
});

cause
Uncaught TypeError: afterglow.getPlayer(...).pause is not a function
Why and how to fix it?

This is a timing issue. When you call pause(), the video has not been initialized, so afterglow.getPlayer("UNIQUE_VIDEO_ID") will not return a valid player. Make sure to call afterglow.init() before this. Maybe, the ready event will help you (http://docs.afterglowplayer.com/docs/events#available-events), as it should allow you to wait for the video to be ready before trying to act on it.

$(window).on('load', function() {});
Should help if some one is still looking the answer.
I migrate to vidoejs since HLS streaming was requared.


Percy

Context
Same as on the other repo!
Changes proposed in this pull request
Guidance to review
Testing

Is there a way to check for the randomness madness before we merge it in? Granted, we use a lot less randomness in our factories, but you know, for our sanity's sake :D

I manually check it, seems fine to me


Error in TeXstudio: Undefined control sequence

Hello,
I would like to use the nice kao template to write a thesis. Compiling the code in Overleaf works fine. However, as I often work offline, I downloaded the project from Overleaf to work on it offline.
When I compile the code using TeXstudio, I always get the following error:
Undefined control sequence. \mainmatter
Do you know where this error comes from and what I can do to solve the problem?
Thanks a lot!
Simone

It might be this bug: https://github.com/fmarotta/kaobook/issues/74
Can you make sure, that your LaTeX packages (especially koma-script) are up to date and recheck?

Hey Alexander Zeilmann,
thanks a lot for your hint, I did not think into updating the packages... I updated MikTex and all packages and the error is gone!
Cheers,
Simone


Implement parsing and tests for bind point and capture point combinations

This is the current syntax proposed for using bind point and capture points together.
The usage of bind points which reference captured variables need to be distinctive from normal bind points for the purposes of data flow analysis and coherence checks. This allow us to book-end grouped operations which may need to succeed of fail as a unit. It also allows us to distinguish chains within a stanza which may have their own failure semantics.
bind point
A bind point is where we normally inject binding values. There is no change to this, but it is included for the sake of distinguishing between the normal bindings and the ones which explicitly reference captured variables.
{binding}

capture point
A capture point is a designated variable within an operation which, upon successful completion of the operation, should be extracted.
[capture]

global capture point
A global capture point is exactly like a capture point, except that it will store the named variable into a process global state cache.
[[capture]]

capture reference
When you need to use a captured value, you reference it like this.
{$capturedvar}

global capture reference
When you need to use a global captured value, you reference it like this.
{$$capturedvar}

All of these forms should be considered short-hand for a universally consistent variable reference form to be clarified later. It will likely take the shape of {[<namespace>:][name.]...<fieldname>}.

Basic parsing for this is already in the code base, but the extended forms and the scope qualifier needs to be added.


enable boolean ops tests in test_dtype_alu

these todos are done with compeq

Tests failing

will reopon once i fix the LLVM bug, it seems related to nan ALUs only


fix: update platform names

What did you fix? (provide a description or issue closes statement)
xbox and playstation are evolving into multi-console scenarios, so it makes more sense to refer to them by their more generic names instead of the individual product

Reproduction steps

Open Settings
Tap to hold the Xbox logo
See that it shows "Microsoft Xbox One"... but I play on the Xbox Series X!

Evidence/screenshot/link to line
You can see my changes here
Considerations

Does this contain a new dependency? [No]
Does this introduce opinionated data formatting or manual data entry? [No]
Does this pr include updated data files in a separate commit that can be reverted for a clean code-only pr? [No]
Have I run the linter? [No]
Is is a bug fix, feature request, or enhancement? [Maintenance]

:tada: This PR is included in version 2.3.23 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add airdash by @simonbengtsson

[x] Project URL:
[x] One project per pull request
[x] Update contents.json instead of README
[x] Screenshot included
[x] Avoid iOS or open-source in description as it is assumed
[x] Use this commit title format if applicable: Add app-name by @github-username
[x] Use approved format for your entry

Thank you!


ui: Use faster animation for mark as read

Fixes: #613
Final Result:
https://github.com/user-attachments/assets/95912caf-2b7d-4676-b07e-a74c551aace0

Oh, sorry this one had to be marked as a draft as I am still waiting for confirmation for some decisions.
But thanks for the review!

@Khader-1 Are there still open questions in the chat discussion? If so it'd be good to bump the discussion to clarify the question you currently have; it looks to me like the questions there have been answered and we have a direction to go with.
(I think the link above is a different thread than you meant; the one for this PR looks to be here.)

You're right, thank for the catch @gnprice!
This is ready for review now @rajveermalviya.

Thanks @chrisbobbe! I misunderstood what Vlad meant with i pressed state. I think the new implementation matches the one you described. PTAL

Thanks @chrisbobbe! I've made a new revision, PTAL.

Thanks @chrisbobbe! A new revision is here PTAL.

Thanks @chrisbobbe and @gnprice for the reviews! I've pushed a new revision PTAL.

Thanks @gnprice! I've pushed a new revision PTAL.

Thanks for the revision! Merging.
I squashed this commit:
a24104ba9 msglist [nfc]: Remove unnecessary whitespace
into the one after it, since that one is already touching neighboring code and this two-line change didn't seem like it made that any harder to read.


Update popover to match MD spec (placement below trigger element)

Bug Report
Ionic version:

[x] 4.x
Current behavior:

Currently the ion-popover and popover controller positions overlays OVER the triggering / target element.
https://media.giphy.com/media/2A1KjUxeiYyn4rAZUk/giphy.gif
Expected behavior:

As per the MD spec, Default placement for a dropdown menu is typically positioned below the element that generates it.
https://puu.sh/CIKPM/21c27b4953.png
Steps to reproduce:

Use popover controller and pass in $event from the (click) event on an element.
Related code:

Other information:

Ionic info:

Ionic:

   ionic (Ionic CLI)             : 4.8.0 (/Users/daem0n/.nvm/versions/node/v11.6.0/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.0.0
   @angular-devkit/build-angular : 0.11.4
   @angular-devkit/schematics    : 7.2.1
   @angular/cli                  : 7.2.1
   @ionic/angular-toolkit        : 1.2.2

Cordova:

   cordova (Cordova CLI) : 8.1.2<EMAIL_ADDRESS>   Cordova Platforms     : ios 4.5.5
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 2.1.4, (and 23 other plugins)

System:

   Android SDK Tools : 26.1.1 (/Users/daem0n/Library/Android/sdk)
   ios-deploy        : 1.9.4
   NodeJS            : v11.6.0 (/Users/daem0n/.nvm/versions/node/v11.6.0/bin/node)
   npm               : 6.7.0
   OS                : macOS High Sierra
   Xcode             : Xcode 10.1 Build version 10B61

It looks like this was fixed by your PR: https://github.com/ionic-team/ionic/pull/17429
Thanks for the issue and PR!


DIDComm RecipientKeys are they Verification or Encryption keys

As seen in the didComm example: https://github.com/hyperledger/aries-rfcs/blob/master/features/0067-didcomm-diddoc-conventions/README.md#service-conventions
recipientKeys are shown as verification keys.
The DIDComm RFC does not mention what's the intended use of keys in RecipientKeys, are they used for encryption only, signature verification only or both?
The official definition of recipientKeys from Aries-RFC 067 is the following:

recipientKeys : This is an array of did key references used to denote the default recipients of an endpoint. (note-1)

Notes

The keys featured in this array must resolve to keys of the same type, for example a mix Ed25519VerificationKey2018 or RsaVerificationKey2018 in the same array is invalid.

I personally prefer to separate encryption and verification keys to increase security resilience, but the spec doesn't mention this anywhere. This issue is created to discuss a more detailed definition of the purpose of keys contained in recipientKeys (and probably routingKeys as well).
This issue is raised due to a related discussion in did-core

recipientKeys are definitely for encryption -- it's what the sender uses for encrypting the message intended for the recipient.  I'm not sure where they are also used for signing, but @llorllale mentioned they are used for signing.  routingKeys are only for encryption, so I think we are fine there.

@swcurran
Just below https://github.com/hyperledger/aries-rfcs/blob/master/features/0023-did-exchange/README.md#example-1

The key used in the signed attachment must be verified against the invitation's recipientKeys for continuity.

There's some confusing text in that RFC... need to clear it up... eg.:

This message is required in the flow, as it updates the provisional information presented in the invitation.

"Updates"?

@llorllale the issue is our framework implementation already does signature validation with recipientKeys :(
changing the wording requires changing our code as well.
ref @sandrask
If we remove this signature verification, then we can treat recipientKeys as encryption only keys.

@swcurran, it seems recipientKeys need to have verification keys to verify the (original) invitation signer. The verification must use the recipientKey to ensure the signer is the original sender and avoid man-in-the-middle attacks (by only verifying the key found in the signed attachment as mentioned here)
My proposal is to add a new list of keys in the didComm service so that we can have 1 list for encryption keys and the other for verification keys. The two list can defined as:
RecipientVerKeys
RecipientEncKeys
Or any other suitable names.
Regardless, both RFCs 0023 and 0067 need to be updated to clarify the use of public keys.

@Baha-sk

My proposal is to add a new list of keys in the didComm service so that we can have 1 list for encryption keys and the other for verification keys. The two list can defined as:
RecipientVerKeys
RecipientEncKeys

We only need verification on oob invitations only. So I suggest we modify the OOB invitation to have a separate entry for the verification keys. Then make it clear in the didcomm service conventions that the recipientKeys are only for encryption.

Don't we need verification keys throughout the relationship?  For example, to be able to sign attachments.  That's why I was thinking there would be additional places.  That said, I think @Baha-sk is right that it is on DID Exchange at the start and then when we rotate the keys, which we've not spent much time on yet...

@swcurran

Don't we need verification keys throughout the relationship? For example, to be able to sign attachments. That's why I was thinking there would be additional places.

Yes, we do need them. The key's purpose should be declared via its verification relationship... for signing VCs we have assertionMethod and for signing VPs we use authentication.... The latter is a bit of a puzzle to me; I think it's because the Holder is implicitly authenticating themselves as such via the proof property.

My proposal is to add a new list of keys in the didComm service so that we can have 1 list for encryption keys and the other for verification keys. The two list can defined as:
RecipientVerKeys
RecipientEncKeys

We only need verification on oob invitations only. So I suggest we modify the OOB invitation to have a separate entry for the verification keys. Then make it clear in the didcomm service conventions that the recipientKeys are only for encryption.

Need to consider implicit invitations in public DIDs... the service entries are constrained to recipientKeys, routingKeys... we want the did-communication service type to reference encryption keys only

Additional considerations:

size of the explicit invitation object (QR codes, query parameter)
this verification is used only when verifying the signature on the response's attachment with the keys in the invitation object

@swcurran @dhh1128 @Baha-sk
Path forward agreed to on today's B call:

keep adding just one signature to the attachment in the response
implicit invitations (public DIDs): invitee can use any verification key found in the public DID to verify the signature in the response. If the signature does not verify against any of the verification keys in the public DID -> reject (problem-report?)

TODO verification relationship

explicit invitations: need a new field that specifies the verification key to use

Sounds good.  Are you doing the 434 PR for the last bullet?  How about adding the "priority" field at the same time, as noted in the issue raised earlier today in #523


Allowing duplicate definitions when parsing dsdl

duplicate == the same thing more than once. This is okay.
redefined == the same identifer used by incompatible definitions.
this is not okay.
In complex build systems duplicate dsdl files can get pulled in from
multiple dependencies and end up in long lists of paths that are
passed into the pyuavcan dsdl compiler. This change to the dsdl
parser allows this without throwing errors but enforces that the
duplicated definitions are compatible. This elminiates the need
for special case handling in build systems to try to find the duplicates
before invoking pyuavcan and adds a new check where such complex
systems will be notified when duplicated definitions get out of
sync.

This does not quite contradict the v0 spec, but it would be against the v1 spec unless I misunderstood the described use case. We can accept this in v0 but not v1 unless the reasoning presented in this discussion is shown to be flawed (it is related to static compatibility checking we have defined for v1): https://forum.uavcan.org/t/new-dsdl-directive-for-simple-compile-time-checks/190/16?u=pavel.kirienko
It starts with this quote:

PyDSDL prohibits the same root namespace from being defined in several different locations. Meaning that spreading definitions belonging to the same root namespace across different directories is not permitted (e.g. /foo/bar/uavcan , /baz/bar/uavcan ).

And several posts later ends here:

What is prohibited is that you can’t invoke a parser with two root namespace directories both ending with the same final path component: /foo/bar/uavcan , /abc/baz/uavcan ; because that would imply that either the same definitions are supplied twice, or members of the same root namespace are distributed across several directories. The latter is dangerous because if a parser is ever invoked on only one of those directories, it will be unable to detect possible conflicts with the other.

Documented in the specification, section 3.1.3 File hierarchy:

A directory defining a namespace will always define said namespace in its entirety, meaning that the contents of a namespace cannot be spread across different directories sharing the same name.

Is it true that you are proposing a mere v0 implementation detail and not suggesting to change that part of v1 spec?

Is it true that you are proposing a mere v0 implementation detail and not suggesting to change that part of v1 spec?

I guess I'm proposing that we allow this in v0 and discuss it for v1. I think we should only restrict what the types resolve to not where they come from. As I mentioned in my commit, this emerged for us as we deployed UAVCAN to distinct parts of a system and then recombined these parts in integration builds. Not only does allowing the duplication simplify the ability to deal with distributed development pipelines it actually provides a really useful compile-time check that two parts of a given system are still utilizing a compatible message definition when they are integrated. For V1 this becomes more sophisticated (read: the duplicate versus redefinition logic may be more involved) but the value is the same.

Also: If you accept this in v0 I'll drive the changes in v1.

I'll drive the changes in v1.

Whatever. I don't immediately see how the obvious issues with definition consistency and enforcing versioning constraints are resolved in the workflow case you described but if you think they are resolvable then sure let's discuss that (not here). When (if) starting that discussion, could you please also provide a practical example (real-life or constructed).
I should note that the underlying idea of keeping all members of a namespace in the same directory is to make types that coexist in the same environment at runtime (which is the UAVCAN bus they are used within) also coexist in the same environment at compile time (which is the root namespace directory). If you look at it this way, you'd probably see that centralized management of a namespace is desirable for ensuring wire compatibility.


Door Lock state updates in HomeKit, but can't control it

Describe The Bug:

I've installed/configured this plugin according to the ReadMe, and unlike the other recent issues I've seen, everything seems to be fine for me, cookie successful and devices appearing. :)
However, when I try to control my door lock through HomeKit, it says no response and produces the log below. If I control it from Alexa, or manually, the state updates in the home app.
To Reproduce:
Add a door lock to Alexa through a compatible manufacturer. (Mine is Level.)
Turn on unlock by app and unlock by voice in the Alexa app.
Lock/unlock the door through Alexa, and through HomeKit via this plugin.

Expected behavior:

The door should lock/unlock regardless of method, and report it's state to both Alexa and HomeKit.
Logs:

[10/30/2023, 2:55:29 PM] [HomebridgeAlexaSmartHome] Front Door - Set target lock state - HttpError(Error setting smart home device state. Reason: Timeout)
[10/30/2023, 2:55:30 PM] [HomebridgeAlexaSmartHome] Front Door - Set target lock state - RequestUnsuccessful(Error setting smart home device state. Response: {
  "controlResponses": [],
  "errors": [
    {
      "entity": {
        "entityId": "68964737-3c2c-406b-b944-e2aeca9002c6",
        "entityType": "APPLIANCE"
      },
      "code": "IotaServiceException",
      "message": "ALREADY_IN_OPERATION",
      "data": null
    }
  ]
}. Error code: IotaServiceException)
[10/30/2023, 2:55:33 PM] [HomebridgeAlexaSmartHome] Front Door - Set target lock state - RequestUnsuccessful(Error setting smart home device state. Response: {
  "controlResponses": [],
  "errors": [
    {
      "entity": {
        "entityId": "68964737-3c2c-406b-b944-e2aeca9002c6",
        "entityType": "APPLIANCE"
      },
      "code": "IotaServiceException",
      "message": "ALREADY_IN_OPERATION",
      "data": null
    }
  ]
}. Error code: IotaServiceException)

Plugin Config:

    {
        "devices": [
            "Front Door"
        ],
        "auth": {
            "refreshInterval": 4,
            "proxy": {
                "clientHost": "<IP_ADDRESS>",
                "port": 9000
            }
        },
        "amazonDomain": "amazon.com",
        "language": "en-US",
        "performance": {
            "cacheTTL": 30,
            "backgroundRefresh": false
        },
        "debug": false,
        "platform": "HomebridgeAlexaSmartHome"
    }

Environment:

Plugin Version: latest
Homebridge Version: 1.6.1
Node.js Version: 18.15.0
NPM Version: 9.5.0
Operating System: Synology DSM 7

Interestingly, I changed the device state cash lifetime to 15 and also played with enabling/disabling the refresh in background option, and it seems to control the physical lock now, but the state still does not update accurately.

Anytime I close and re-open the Home app, the state seems to be updated correctly. But while in the home app, if I lock/unlock the door, it successfully completes but doesn't change the state until I restart the home app. This doesn't seem to matter whether or not I have background refresh on or off, or the amount of time specified for device cache state.

This is the current debug log, which looks normal to me so I'm not sure where to start digging.

[10/30/2023, 10:30:10 PM] Registering platform 'homebridge-alexa-smarthome.HomebridgeAlexaSmartHome'
[10/30/2023, 10:30:16 PM] [HomebridgeAlexaSmartHome] Initializing HomebridgeAlexaSmartHome platform...
[10/30/2023, 10:30:16 PM] [HomebridgeAlexaSmartHome] Loading accessory from cache: Front Door
[10/30/2023, 10:30:17 PM] [HomebridgeAlexaSmartHome] Alexa-Remote: cookie was provided
[10/30/2023, 10:30:19 PM] [HomebridgeAlexaSmartHome] Alexa-Remote: Authentication checked: true
[10/30/2023, 10:30:20 PM] [HomebridgeAlexaSmartHome] Alexa-Remote: Change Base URL for API calls to na-api-alexa.amazon.com
[10/30/2023, 10:30:24 PM] [HomebridgeAlexaSmartHome] Successfully authenticated Alexa account.
[10/30/2023, 10:30:25 PM] [HomebridgeAlexaSmartHome] Found 158 devices connected to the current Alexa account.
[10/30/2023, 10:30:25 PM] [HomebridgeAlexaSmartHome] BEGIN devices connected to Alexa account
[10/30/2023, 10:30:25 PM] [HomebridgeAlexaSmartHome] Found all 1 devices in plugin settings.
[10/30/2023, 10:30:25 PM] [HomebridgeAlexaSmartHome] Updating device states
[10/30/2023, 10:30:25 PM] [HomebridgeAlexaSmartHome] Front Door ::: Attempting to add accessory(s) for device: {
[10/30/2023, 10:30:25 PM] [HomebridgeAlexaSmartHome] Front Door ::: Current state: [
[10/30/2023, 10:30:25 PM] [HomebridgeAlexaSmartHome] Front Door ::: Range capabilities: {}
[10/30/2023, 10:30:25 PM] [HomebridgeAlexaSmartHome] Restored existing accessory from cache: Front Door
[10/30/2023, 10:30:31 PM] [HomebridgeAlexaSmartHome] Obtained device states from cache
[10/30/2023, 10:30:31 PM] [HomebridgeAlexaSmartHome] Front Door - Get lock state result: 1
[10/30/2023, 10:30:31 PM] [HomebridgeAlexaSmartHome] Obtained device states from cache
[10/30/2023, 10:30:31 PM] [HomebridgeAlexaSmartHome] Front Door - Get lock target state result: 1
[10/30/2023, 10:30:42 PM] [HomebridgeAlexaSmartHome] Front Door - Triggered set target lock state: 0
[10/30/2023, 10:31:09 PM] [HomebridgeAlexaSmartHome] Front Door - Triggered set target lock state: 1
[10/30/2023, 10:31:25 PM] [HomebridgeAlexaSmartHome] Updating device states
[10/30/2023, 10:32:25 PM] [HomebridgeAlexaSmartHome] Updating device states
[10/30/2023, 10:33:26 PM] [HomebridgeAlexaSmartHome] Updating device states
[10/30/2023, 10:34:26 PM] [HomebridgeAlexaSmartHome] Updating device states
[10/30/2023, 10:35:27 PM] [HomebridgeAlexaSmartHome] Updating device states

Seems I missed this issue awhile ago, apologies. The plugin only updates at most every 60 seconds so that may be why you needed to close and reopen the home app to see the change. I'm going to close this issue because that is expected but I will take this into consideration if there are ways to improve that. Thanks!


Tooltip stuck and not hiding [Sublime Text 4, Build 4094]

Sublime Text 4
Build 4094
Demo (GIF)

Close and re-open file does not help, tooltip is still on same position in unhidden state.

Sorry, look like a duplicate #760


Library switches view when updating episode count

Thank you for taking the time to open an issue!
For bug reports please include the following section in your issue details.

Description: Assuming something isn't properly tracking the AJAX calls going out for the library and it ends up thinking the tab I'm on isn't actually the one I'm on 😄
Steps to reproduce: Open up my library, switch to a tab that takes long to load (for me Completed).  Before that finishes loading, switch to Currently Watching.  Increment an episode count for a show.  Count will update but the view will switch to the previous tabs content (Completed).
Screenshots (if applicable):

OS and Browser: Mac Sierra - Chrome 55.0.2883.95

Thanks for the report @astraldragon! I'm going to look into this today.

With the re-brand seems like the project is still open source.  May take a look at learning some Ember 😄

@astraldragon Yeah, staying open source was a very important goal for us, even after the rebrand. Currently, it's mostly @vevix, @JoshFabian and me working on client side. Especially testing needs lots of love after rushing through a lot of things during release, so any contribution is welcome 😄

Tests are always welcome 😸!

@astraldragon shoot me an email if you'd like to join our dev slack<EMAIL_ADDRESS>

Yeah for sure.  I'll ping you.


Vendor client

Also vendor go-winio and go-jsonw.

This is the kbfs side of https://github.com/keybase/client/pull/13514/files -- once everything is approved and that is landed, I'll update the vendor hashes on this PR and merge it.

Ping! Note that the circleci failure is expected -- the other two should pass now.

Ah! Just realized you are already doing vendoring here. I'll rebase after this is in then!

CircleCI passes, so merging (previous runs had Jenkins / Appveyor pass)


ui-client: update NPM dependencies

Updates npm dependencies in ui-client to be able to build with newer
node versions. Node 12 isn't available for aarch64 (Apple M1) and building
with a newer local node version would fail because of libscss being
outdated and not building. While updating webpack the the extract-text
plugin was replaces with mini-css-extract because extract-text is
deprecated.

@joao-silveira @slisson can one of you test this on their local machine as well with a clean checkout? It worked for me but since I changed the copy plugin it might be that files are at different locations.


how to run on mac after librarys installed

I installed and libraries and I opened jumpcutter.py in terminal but it doesn't seem to work.

You need to be more specific: What error messages is it giving? What python version are you using? Are you using python 3?

If you need to, adjust the frame rate to something else if the videos go out of sync


Retry refusing to stop even after previous retry executed successfully

I have added a retry mechanism to retry 100 times for any failure (I wanted to handle RabbitMQ connection failure). Say if connection established in 10th retry I was expecting to stop retry and proceed with fresh execution. But unfortunately, retry didn't stop even after connection established. It has retried until the configured number of times before picking up fresh message. My code to retry looks like below,
c.UseRetry(Retry.Interval(totalRetryCount, TimeSpan.FromSeconds(retryInterval)));
I have tried with lambda expression as well but didn't work

What version of MT are you running?

MT 3.5.7

c.UseRetry(x => x.Interval(totalRetryCount, TimeSpan.FromSeconds(retryInterval)));

Notice the change from what you have above.

@vnathv please confirm this resolved your issue, and close it.


Cloud Witness?

Should this documentation not reference use of Azure Storage Blob as a Cloud Witness rather than using a VM FSW?

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

ID: 9f4f2ef2-d071-c86e-0afe-ff6aed852132
Version Independent ID: 20998982-0546-5814-76a7-cd53abe9d590
Content: SQL Server Availability Groups - Azure Virtual Machines - Overview
Content Source: articles/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-availability-group-overview.md
Service: virtual-machines-sql
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

@alexjmoore Thanks for the feedback! We are currently investigating and will update you shortly.

@alexjmoore I have assigned this to the content author to review and update the doc as appropriate.
@MikeRayMSFT can you please take a look?

@alexjmoore - thank you for the comment. You are correct - that you can use a cloud witness for the availability group. For instructions, see Deploy a Cloud Witness for a Failover Cluster
. The servers have to be Windows Server 2016. The tutorial applies to Windows Server 2012 as well.
I've taken a work item to update the content - if you like you can submit a specific edit on the article in GitHub.

Wow, such quick response! :-) I guess there is a question as to if the article is updated to show two options or not.  Also it references a marketplace template, so I guess there is also a question as to if an updated/additional template to use the Cloud Witness.  I only mention it because use of a Cloud Witness seems the more 'proper' approach for a greenfield Azure deployment.

That's a great point - that an cloud witness is better for a new deployment. It's more economical, simpler, and should be more reliable. I have a work item to update the tutorial. I'll also pass back to the product group the requirement for an updated template.
Thanks
#please-close


feature: Release the V1 Admin API

We just published the configuration for the Firestore V1 Admin API to Github. This PR updates synthtool and update.sh to pull in the new configuration.
The manual changes in this PR are 6c3f1a0, 67a8430 and d8ea6a7.

Linkinator is failing with two missing files:
[404] http://localhost:5294/google.firestore.admin.v1.html
[404] http://localhost:5294/google.longrunning.html
These are not generated by yarn docs, but I am struggling to find out why.

Added these docs via #591


Enhance Telemetrix buffer size up to 4096 bytes

[ ] Increase buffer size of Telemetrix server up to 4096 bytes

[ ] Allow to flush 4096 bytes into Telemetrix server at once

Solved in commit 01eec39
Tested with bubble-code.py example

Measure atbubble-code.py example. The speed of program after enhancement is faster 27 times.
With 4096 bytes buffer, FPS = 2.7.
With 28 bytes buffer, FPS = 0.1.
Video: buffer size = 28
https://user-images.githubusercontent.com/48436368/146335799-b1845b4d-a5c2-4aff-8bd0-5202e1588aaf.mp4
Video: buffer size = 4096
https://user-images.githubusercontent.com/48436368/146335813-2427e2e0-8053-4a82-8dd7-d86ac1199305.mp4

On RP2040, the speed measured of bubble-code.py is 15.2


Two fixes for pdf_count_pages()

There is no SAFE defines in gs_init.ps.
And file foomatic-i89GMn MUST be a) full path b) reside in $TMPDIR|$TEMP|$TMP|/temp|/tmp directory.

Oops, you are right about no existent -dSAFE.
Currently, I am debugging a problem with cups on OpenBSD.
The error message from error_log was:
D [04/Mar/2020:09:54:08 +0100] [Job 675] Storing temporary files in /var/spool/cups/tmp
D [04/Mar/2020:09:54:08 +0100] [Job 675] GPL Ghostscript 9.07: Unrecoverable error, exit code 1
D [04/Mar/2020:09:54:08 +0100] [Job 675] File contains -1 pages.
D [04/Mar/2020:09:54:08 +0100] [Job 675] Unexpected page_count

So I tried to (manually) reproduce the command-line used in pdf_count_pages().
Removing -dSAFER from command-line used in pkg_count_pages() makes the file to be printed, whereas with it is failing.

I have been pointed that the problem could be related to the version of ghostscript used on OpenBSD side: it is 9.07 (an old version) and -dSAFER changed a lot since. I will look on this side.

Your problem in $TMPDIR/$TMP path.
# cp /tmp/foomatic-04MIpw /var/spool/cups/tmp/foomatic-04MIpw
# ls -l /tmp/foomatic-04MIpw /var/spool/cups/tmp/foomatic-04MIpw
-rw------- 1 lp   lp   431015 Feb 26 10:29 /tmp/foomatic-04MIpw
-rw------- 1 root root 431015 Mar  4 14:03 /var/spool/cups/tmp/foomatic-04MIpw
# gs -dNODISPLAY -dSAFER -dNOPAUSE -q -c '/pdffile (/tmp/foomatic-04MIpw) (r) file runpdfbegin (PageCount: ) print pdfpagecount = quit'
PageCount: 1
# gs -dNODISPLAY -dSAFER -dNOPAUSE -q -c '/pdffile (/var/spool/cups/tmp/foomatic-04MIpw) (r) file runpdfbegin (PageCount: ) print pdfpagecount = quit'
Error: /invalidfileaccess in --file--
Operand stack:
   pdffile   (/var/spool/cups/tmp/foomatic-04MIpw)   (r)
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--
Dictionary stack:
   --dict:728/1123(ro)(G)--   --dict:0/20(G)--   --dict:75/200(L)--
Current allocation mode is local
Last OS error: Permission denied
GPL Ghostscript 9.50: Unrecoverable error, exit code 1
# TMPDIR=/var/spool/cups/tmp/ gs -dNODISPLAY -dSAFER -dNOPAUSE -q -c '/pdffile (/var/spool/cups/tmp/foomatic-04MIpw) (r) file runpdfbegin (PageCount: ) print pdfpagecount = quit'
PageCount: 1

Yeah, 9.07 don't contain code for comparing filepath with environment vars $TMP|$TMPDIR|$TEMP.
Read CVE-2019-6116 for example, how systems compromised with gs. https://github.com/vulhub/vulhub/tree/master/ghostscript
@tillkamppeter maybe check gs version in test_gs_output_redirection() and print BIG FAT WARNING or refuse using it if gs too old?


$err:line-number

Plugin does not know $err:line-number, though it knows $err:column-number and others known $err:* variables.

Thanks for reporting this issue a fix for this has now been pushed, there was a typo in the list of $err:* variables.


[Feature Request] [question] Release wheels for SimpleITK with Elastix for Ubuntu

Is there a whay to get the built binaries for Python of SimpleITk and Elastix for Ubuntu similar to this:
https://pypi.org/project/SimpleITK-SimpleElastix/#files
So far only the Mac compatible wheels seem available.
Reading the documentation, the proposed solution is to build the library from source. However, I am unable to built f (due to dependency errors ) in the ubuntu server. I have limited rights but heavily depend on Elastix
Thank you in advance!

Hello @mariamonzon,
Currently the core SimpleITK team does not have plans for supporting a binary distribution which includes SimpleElastix, we have limited bandwidth. This is a long term commitment in terms of maintenance.
@mstaring, @N-Dekker would you be able to provide this support?


Missing Devtools in Live Preview

Hello!
I'm not sure, but triggering Simple Browser doesn't have the option to trigger the devtools. I guess it doesn't exists for Simple Browser and would be glad if you could add it.

Click on the hamburger icon and select "Open Devtools Pane".
Also, what stops you from opening a browser, resize the editor and the browser 50%/50% and use it this way with proper tools?
I guess this issue can be closed.

Click on the hamburger icon and select "Open Devtools Pane".
Also, what stops you from opening a browser, resize the editor and the browser 50%/50% and use it this way with proper tools?
I guess this issue can be closed.

Hi! Are you asking to add devtools to Simple Browser? Because if so, you'll need to file that in the vs code core repo instead.


Tail recursive foldl

The implementation of foldl looks to be tail recursive; however, it gets compiled into:
function (o) {
    return function (b) {
        return function (_87) {
            if (_87 instanceof Nil) {
                return b;
            };
            if (_87 instanceof Cons) {
                return Data_Foldable.foldl(foldableList)(o)(o(b)(_87.value0))(_87.value1);
            };
            throw new Error("Failed pattern match: " + [ o.constructor.name, b.constructor.name, _87.constructor.name ]);
        };
    };

This is the reason for the custom implementation in CatList. I was getting stack overflows from List's foldl.

That certainly should be optimized. I'm not sure why it isn't.

This is a real problem for every program that tries to work with lists bigger than 20000 Elements (which is not unreasonable).
I hit this problem in practice but it can be reproduced easily with this simple program:
module Main where

import Prelude
import Control.Monad.Eff.Console (log)
import Data.Foldable (foldl)
import Data.List ((..))

main = do

    let numbers = 1 .. 20000
    let sum = foldl (\acc x -> acc + x) 0 numbers
    log $ show sum

Results in:
home/shybyte/workspace/purescript-tail-recursion-bug/output/Data.Foldable/index.js:0
(function (exports, require, module, __filename, __dirname) { // Generated by
^
RangeError: Maximum call stack size exceeded

@paf31 I consider this bug a real blocker. I would love to help to fix this problem, but I guess this is a general compiler problem and can be fixed only by knowing the internals of the purescript compiler.

foldl should be easily implemented in terms of purescript-tailrec.

But this is a bug still, I think. I'll move this over to the compiler repo.


FFMPEG.EXE System Error

"The Code execution cannot proceed because open264-6.dll was not found. reinstalling the program may fix this problem."
I get this error constantly during the rendering animation fram 27 of 30, when "./output/out_%05d.png -> ./output/out_%05d.mp4.
I've tried manually adding the DLL, and nothing seems to work, any tips or tricks?

Looks like a video codec for h264 missing issue
maybe reinstall ffmpeg? run command like "conda install -c conda-forge ffmpeg"
Or install a video player such like VLC


[a11y] Remove maximum scale

Because a11y -> https://a11yproject.com/posts/never-use-maximum-scale/

Good catch, I suggest we align viewport meta with the bootstrap 4 starter template.

Commit amended with the Bootstrap starter template. Anyway, seems to be a very specific Safari 9 fix for a weird behaviour, so it might be removed in a while.
Thanks for this nice theme!

Thank you so much for your contribution.


Add array blanket implementations.

Mirrors the slice implementation. Improves ergonomics when comparing arrays.

Oooh, nice! I wonder if we should put this under a feature flag 🤔 - approx is used pretty widely and I'm not sure how disruptive a MSRV bump would be to the ecosystem.
I also see that we're using Travis CI still - might need to switch to Github Actions 😅

@brendanzab Can't hurt. I've added an array_impl that is not enabled by default.

Would love to see this merged to get rid of all the &arr[..] in approx calls.

Hey there! Just giving this one a gentle bump! Anything else needed to get this closed?
wrt MSRV bump, might make sense to just bump the version to 0.6?


[Feature] Add support for multi-task CD models

Add one SOTA muti-task CD model, ChangeStar (the paper was published in ICCV 2021).
The new multitask_loss_computation function calculates the losses between multiple output logits and multiple masks.
The new field aux_masks in the sample dict is given such a name that it can be used for different tasks. For example, an edge mask can be stored as a aux_mask and used in a semantic segmentation task. Transformation operations on aux_masks have been supported.
A new protocol has been proposed for multi-task CD models. To enable the feature of multi-task training, an nn.Layer object should have an attribute named USE_MULTITASK_DECODER and set the value of it to True. Also, the object should have an attribute named OUT_TYPES, which is a tuple containing LabelType enums, each element in this tuple denoting the label type of the corresponding element in the output list of the forward method during model training.
Now CDDataset accepts an optional argument with_seg_labels and supports either 3 or 5 items in a line of the file_list.

需要解决一下冲突

冲突已解决。因为merge不小心误操作为rebase所以在自己的分支forcely push了一次，不过没有影响到主分支。此外，新增了两个小功能：

变化检测数据集现在能够自动对标签进行二值化处理。在数据集中添加该功能而不是将其实现为一个transform，是考虑到在eval阶段，变化检测任务的transform似乎执行了apply_im_only模式，因此对标签的处理被绕过。
添加了随机交换两个时相影像的transform，这在变化检测模型的训练中常用。


TypeError: client.setCredentials is not a function

Hello everyone! I have been trying to follow the Cloud vision with Node.js codelab. I am able to start the google sign in flow but after I have selected an account to sign in. I get TypeError as explained below.
Sorry for changing the title that many times. I got a bit sloppy there.
Please run down the following list and make sure you've tried the usual "quick fixes":
[done] Search the issues already opened: https://github.com/GoogleCloudPlatform/google-cloud-node/issues
[done] Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
[done] Check our Troubleshooting guide: https://googlecloudplatform.github.io/google-cloud-node/#/docs/guides/troubleshooting
[done]  Check our FAQ: https://googlecloudplatform.github.io/google-cloud-node/#/docs/guides/faq
If you are still having issues, please be sure to include as much information as possible:
Environment details

OS: MacOs
Node.js version:v8.9.1
npm version:5.5.1
google-cloud-node version: v6.11.1

Steps to reproduce
Follow steps from the codelab.
Error shown:
home/user/cloud-vision/start/lib/oauth2.js:172
      client.setCredentials(tokens);
             ^
TypeError: client.setCredentials is not a function
    at /home/user/cloud-vision/start/lib/oauth2.js:172:14
    at /home/user/cloud-vision/start/node_modules/google-auth-library/lib/auth/oauth2client.js:95:13
    at Request._callback (/home/user/cloud-vision/start/node_modules/google-auth-library/lib/transporters.js:113:17)
    at Request.self.callback (/home/user/cloud-vision/start/node_modules/google-auth-library/node_modules/request/request.js:186:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/home/user/cloud-vision/start/node_modules/google-auth-library/node_modules/request/request.js:1163:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:188:7)
    at IncomingMessage.<anonymous> (/home/user/cloud-vision/start/node_modules/google-auth-library/node_modules/request/request.js:1085:12)

Further Information:
The credentials set up is proper because I put in the details into the "Complete" version of the Codelab and I could sigin perfectly. So I thought there must be something wrong with the coding part but I have checked it twice and everything is the same as in the codelab.
Thanks!

This issue was moved to googleapis/nodejs-vision#15


NPK testing

HI,
I see you have developed Active Carbon, Turbidity, Nitrite,Nitrate and Ammonia testing usinng colormeter.
Have you tried or your color sensor able to measure NPK nutrient using reagent?
Another question is you also use AS7431, regarding NPK is AS7431 is more accurate and easier to use?
Thanks;

In my opinion the TSL2591 is better for the measurement of absorbance (extinction).
The spectral responsivity of this sensor is from 415nm to 1100nm.
When you are going for a common molybdenium blue silicate/phosphatetest, you need sensitivity for 810nm or 880nm. You do NOT need to go for a spectrum, because you choose the LED at 850nm to measure the absorbance.
The linear relationship according to the Lambert-Beer-Law is realized and you can quantify the concentration of different Nitrogen-Phosphorus-Potassium-sources (Ammonium at 660nm with Berthelot reaction, Nitrate at 570nm with Azodye, Phosphate with Molybdenium Blue and Potassium with Phenolate -Turbidity at 700nm (white light source is also possible, when you are using a filter). When you want to take an absorbance spectrum in the visible range, than you could take the AS7341 11channel sensor or a Hamamatsu mini-spectrometer.

Thanks for your input. Due to my software engineer background, these chemistry things you mentioned are overwhelming.  So far, I can only get Turbidity working using 850nm

I have been doing research on this for the last 2 weeks. Slow as chemistry is not my specialty. I am looking to build an NPK spectrometer device for farmers by trying to make it as automated as possible and avoid complexity and steps in chemical preparation.
Based on your suggestion, TSL2591 alone can measure NPK but just need to use different LED(570nm, 660nm, 700nm). Am I right?

You need chemicals for a specific chemical Reaktion of Phosphate (PO4)
http://public.iorodeo.com/docs/phosphate/vanadate-molybdate method.html
Or
http://public.iorodeo.com/docs/phosphate/hach_phosver3.html
Nitrate (NO3) , Nitrite
and Ammoniak (NH4)
https://blog.iorodeo.com/ammonia-nitrate-and-nitrite-colorimetric-assays/
And K
https://sites.google.com/iorodeo.com/biorodeo/potassium
in your substrate. According to the Reaktion you choose the LED. Also you
need a calibration with Standards.
Please ready the documentation.
Best regards
Matthias
GarudaOne @.***> schrieb am Do., 30. Mai 2024, 04:47:

I have been doing research on this for the last 2 weeks. Slow as chemistry
is not my specialty. I am looking to build an NPK spectrometer device for
farmers by trying to make it as automated as possible and avoid complexity
and steps in chemical preparation.
Based on your suggestion, TSL2591 alone can measure NPK but just need to
use different LED(570nm, 660nm, 700nm). Am I right?
—
Reply to this email directly, view it on GitHub
https://github.com/iorodeo/open_colorimeter/issues/1#issuecomment-2138573574,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOH3QCEKGYSGLJ6B5G53SYDZE2HKPAVCNFSM6AAAAABA7OOQR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZYGU3TGNJXGQ
.
You are receiving this because you commented.Message ID:
@.***>

You need chemicals for a specific chemical Reaktion of Phosphate (PO4) http://public.iorodeo.com/docs/phosphate/vanadate-molybdate method.html Or http://public.iorodeo.com/docs/phosphate/hach_phosver3.html Nitrate (NO3) , Nitrite and Ammoniak (NH4) https://blog.iorodeo.com/ammonia-nitrate-and-nitrite-colorimetric-assays/ And K https://sites.google.com/iorodeo.com/biorodeo/potassium in your substrate. According to the Reaktion you choose the LED. Also you need a calibration with Standards. Please ready the documentation. Best regards Matthias GarudaOne @.> schrieb am Do., 30. Mai 2024, 04:47:
…
I have been doing research on this for the last 2 weeks. Slow as chemistry is not my specialty. I am looking to build an NPK spectrometer device for farmers by trying to make it as automated as possible and avoid complexity and steps in chemical preparation. Based on your suggestion, TSL2591 alone can measure NPK but just need to use different LED(570nm, 660nm, 700nm). Am I right? — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOH3QCEKGYSGLJ6B5G53SYDZE2HKPAVCNFSM6AAAAABA7OOQR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZYGU3TGNJXGQ . You are receiving this because you commented.Message ID: @.>

Thank you very much for your input,. I am looking into them

Dear GarudaOne,
there is no possibility to do that without chemicals, because phosphate,
nitrate, ammonia and potassium themselves do not absorb light in the
visible range. The chemistry behind is 100 years old and
ONLY for nitrate there is an alternative in the UV-absorbtion at two
wavelengthes (APHA). This is only appropriate for clear drinking water and
you need the UV-version of the iorodeo-photometer as well.
Please do not contact me again, because everything is well documented on
the iorodeo platform and the world wide web. Thank you for your
understanding.
Best regards
Matthias
--
Matthias Birkicht
Georg-Seebeck-Straße 47
27570 Bremerhaven
mobile: 01609 48 68 28 7
phone: +49 471 306608
work: +49 421 23 800 34
skype: matthias.birkicht
www.oberton.info
GarudaOne @.***> schrieb am Do. 30. Mai 2024 um 16:59:

You need chemicals for a specific chemical Reaktion of Phosphate (PO4)
http://public.iorodeo.com/docs/phosphate/vanadate-molybdate method.html
Or http://public.iorodeo.com/docs/phosphate/hach_phosver3.html Nitrate
(NO3) , Nitrite and Ammoniak (NH4)
https://blog.iorodeo.com/ammonia-nitrate-and-nitrite-colorimetric-assays/
And K https://sites.google.com/iorodeo.com/biorodeo/potassium in your
substrate. According to the Reaktion you choose the LED. Also you need a
calibration with Standards. Please ready the documentation. Best regards
Matthias GarudaOne @.
> schrieb am Do., 30. Mai 2024, 04:47: … <#m_-4740617266292446308_> I
have been doing research on this for the last 2 weeks. Slow as chemistry is
not my specialty. I am looking to build an NPK spectrometer device for
farmers by trying to make it as automated as possible and avoid complexity
and steps in chemical preparation. Based on your suggestion, TSL2591 alone
can measure NPK but just need to use different LED(570nm, 660nm, 700nm). Am
I right? — Reply to this email directly, view it on GitHub <#1 (comment)
https://github.com/iorodeo/open_colorimeter/issues/1#issuecomment-2138573574>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOH3QCEKGYSGLJ6B5G53SYDZE2HKPAVCNFSM6AAAAABA7OOQR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZYGU3TGNJXGQ
https://github.com/notifications/unsubscribe-auth/AOH3QCEKGYSGLJ6B5G53SYDZE2HKPAVCNFSM6AAAAABA7OOQR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZYGU3TGNJXGQ
. You are receiving this because you commented.Message ID: @.>
Thank you very much for your input,. I am looking into them
—
Reply to this email directly, view it on GitHub
https://github.com/iorodeo/open_colorimeter/issues/1#issuecomment-2139820009,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOH3QCBILIKHKN4TUBCDUUTZE45FDAVCNFSM6AAAAABA7OOQR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZHAZDAMBQHE
.
You are receiving this because you commented.Message ID:
@.***>


Feature request: PR templates for Dependabot PRs

Similar to how GitHub lets me define a pull_request_template.md or .github/pull_request_template.md file in my repo that it uses for the body of a new PR description, it would be extremely helpful if there was something like dependabot_pull_request_message.md that we could define and Dependabot would add that Markdown to the top or bottom of its PR descriptions.
For context, our use case is for checklists. Before merging a Dependabot PR we want to make sure we do certain things, and it would be helpful if we could have all of our Dependabot PRs include this checklist, for example:

[ ] Confirm that the gem is still used
[ ] Confirm that the gem cannot be trivially removed
[ ] Confirm that the changes for the gem version bump do not require additional code changes that may be in untested paths
[ ] Confirm you feel comfortable QAing this change

Does that make sense?

+1 for this feature, it would make a big difference to our workflow and ability to get most value out of the power of Dependabot, given we run it across 100s of repos. Adding GitHub actions to handle it would be far more difficult to implement than a simple PR template

+1 This would help us streamline all PRs on any given app/repo

+1 for the feature. Can someone share their GH actions workaround discussed above solution? :)

+1 for this feature, people might review and forget eg. to start some website manually and check it still works...

Related (but about commit messages not PR messages):

https://github.com/dependabot/dependabot-core/issues/1460

+1 for this feature

+1 this would be a great feature

We have a special code block in the PR message that is used by our CI as change notes. Would be great if we could also make dependabot inject that into the PR message.

My use case for this is I have a check list in the PR template for ci jobs, only checked CIs will be run.
Hopefully this feature will exist

+1 for this feature, it would be super helpful for our process. Our use case is also just checking that all QA steps were done before merge.

+1 for this

Are there any updates on this one ?

+1 for this

+1 for this

+1 for this


mmap returns EBADF

mmap fails to keep the file descriptor alive long enough to pass to mmap.  The file descriptor gets closed and then mmap fails with EBADF.  This shows the bug:
use std::fs::File;
use std::num::NonZeroUsize;

use nix::sys::mman::{MapFlags, ProtFlags};

fn main() {
    unsafe {
        let fd = File::open("/dev/mem").expect("open");
        nix::sys::mman::mmap(None, NonZeroUsize::new(4096).unwrap(), ProtFlags::PROT_READ,
            MapFlags::MAP_SHARED, Some(fd), 0).expect("mamp");
    }
}

Resulting output:
thread 'main' panicked at src/main.rs:10:48:
mamp: EBADF
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

mmap fails to keep the file descriptor alive long enough to pass to mmap.

// nix 0.27.1

pub unsafe fn mmap<F: AsFd>(
    addr: Option<NonZeroUsize>,
    length: NonZeroUsize,
    prot: ProtFlags,
    flags: MapFlags,
    f: Option<F>,
    offset: off_t,
) -> Result<*mut c_void> {
    let ptr =
        addr.map_or(std::ptr::null_mut(), |a| usize::from(a) as *mut c_void);

    // `f` dropped here, making `fd` an invalid file descriptor
    let fd = f.map(|f| f.as_fd().as_raw_fd()).unwrap_or(-1);
    let ret =
        libc::mmap(ptr, length.into(), prot.bits(), flags.bits(), fd, offset);

This is right, if you move an owned file descriptor (like the std::fs::File in this issue) to it, then the fd will be closed before being passed to libc::mmap().
A workaround would be passing fd by reference:
        nix::sys::mman::mmap(None, NonZeroUsize::new(4096).unwrap(), ProtFlags::PROT_READ,
                             MapFlags::MAP_SHARED, Some(&fd), 0).expect("mamp");

But anyway, workarounds are just workarounds, let me file a PR to get this issue fixed so that the file descriptor can survive the underlying mmap() usage.

Just realized that this issue does not exist in the master branch as we have separated this API into

mmap()
mmap_anonymous()

so that the f argument in mmap() no longer takes an Option<F>, and thus eliminates the usage of Option::map(self), which would ensure that f will be alive within the whole function.


Fix CVE-2022-28391 by bumping alpine from 3.15 to 3.16

addresses https://github.com/distribution/distribution/issues/3648

@milosgajdos @silvin-lubecki PTAL

Codecov Report

Merging #3649 (9f2bc25) into main (c202b9b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3649   +/-   ##
=======================================
  Coverage   56.58%   56.58%
=======================================
  Files         103      103
  Lines        7520     7520
=======================================
  Hits         4255     4255
  Misses       2596     2596
  Partials      669      669

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 c202b9b...9f2bc25. Read the comment docs.


Wallet details. Single wallet multisig. Signatories tab shows same lines.

Description
For the signle wallet multisig wallet details, tab with signatories shows the same wallets.


Mitigate crash in AudioStreamPlayer3D when a camera has null viewport

Stops cases of AudioStreamPlayer3D crashing.

So this should fix https://github.com/godotengine/godot/issues/52853?

#52853?

Yes, I've tested and confirmed that it fixes your reproducer there.

Thanks!


Revert change for sorting records for log flush

Reverted the change added recently:
https://github.com/eBay/Jungle/pull/109/files#diff-3a78ea2725a657dcdbe49cbad743cc2de9c82b14b4218546e86e32c91788ab91R1326-R1338

Sorting records in a key order will not help, because there is a
seq-index in table file. Sorting records by key makes them random
for seq-index, thus there is no benefit.

@smallsmallc @tobecontinued @mohiuddin-shuvo please review it thanks.


#region nesting doesn't recognise last #endregion if there's no code after it at the end of the file on a non-"root" indent level

Sorry for the monster title, just check the video and you'll see what I mean
Type: Bug

Behaviour
Expected vs. Actual

Have a #region block that ends at the end of the file that is on a second level of indenting
There should be no code on that level after it
Expected: it works and folds right
Actual: it does not get recognised and does not fold

https://user-images.githubusercontent.com/1302278/188624489-64185c21-0dcb-4364-909e-d395916da126.mov
video above: after deleting the second _, the region on line 540 unfolds because it doesn't think it is a region anymore
Steps to reproduce:

Open VSCode with a Python editor
Write some code like described
Make a #region block that ends at the end of the file, with no code following it
try to fold the block

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.9.13
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings

venvPath: "<placeholder>"

languageServer: "Pylance"

linting
• flake8Args: "<placeholder>"
• flake8Enabled: true
• mypyEnabled: true

sortImports
• args: "<placeholder>"

formatting
• provider: "black"

testing
• pytestArgs: "<placeholder>"
• pytestEnabled: true
• unittestEnabled: true

Extension version: 2022.14.0
VS Code version: Code 1.71.0 (Universal) (784b0177c56c607789f9638da7b6bf3230d47a8c, 2022-09-01T07:25:38.437Z)
OS version: Darwin arm64 22.1.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Apple M1 (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
3, 4, 4

Memory (System)
16.00GB (0.05GB free)

Process Argv
--crash-reporter-id cf9a22bc-bfd6-4435-a340-7efeb83080bd

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30557514
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
pylanb8912:30545647
vsclangdf:30486550
c4g48928:30535728
hb751961:30553087
dsvsc012cf:30540253
azure-dev_surveyone:30548225
i497e931:30553904

Can you provide a code sample that reproduces this issue? I was only able to reproduce similar behavior when my code had more #region comments than #endregion comments.
Is that the issue on your side also? We should probably emit a warning for unmatched #region/#endregion comments.

If this is at the bottom of the file, it won't fold right
class tree:
    # region B
    def flower(self):
        return "random words"

    # endregion

But this will work
class tree:
    # region B
    def flower(self):
        return "random words"

    # endregion

    hello = "world" # ←---

@jvacek, thanks for the code sample. I'm able to repro this issue now.
I noticed that the indentation of the hello = "world" line is important and has some unexpected effects:
When that line is fully dedented, only the class and def are foldable:
class tree:
    # region B
    def flower(self):
        return "random words"

    # endregion

hello = "world" # ←---

When it is indented one level, the #region is also foldable:
class tree:
    # region B
    def flower(self):
        return "random words"

    # endregion

    hello = "world" # ←---

And when it is indented one more level (to the body of the function), only the class and #region are foldable (not the def):
class tree:
    # region B
    def flower(self):
        return "random words"

    # endregion

        hello = "world" # ←---

FYI, I also opened an issue to consider warning about unmatched #region/#endregion comments: https://github.com/microsoft/pylance-release/issues/3308

The issue is that VS Code does not allow folding ranges to overlap only partially. One needs to completely surround the other, or else they need to be completely separate.
For example, the following is allowed. [Note that indentation is for readability, but has no effect folding behavior]:
# Range 1 start
  # Range 2 start
  # Range 2 end
# Range 2 end

But this is invalid:
# Range 1 start
  # Range 2 start
# Range 1 end
  # Range 2 end

Ranges that overlap partially like this are considered invalid and are filtered out by VS Code during FoldingModel.update().
Going back to the earlier examples...
In this example, we currently do not include the #endregion comment in the class folding range, so we end up with partially overlapping ranges:
class tree:                    # Range 1 start
    # region B                 # Range 2 start
    def flower(self):
        return "random words"  # Range 1 end

    # endregion                # Range 2 end

hello = "world" # ←---

Whereas, in this case the region's range is fully contained within the class range:
class tree:                    # Range 1 start
    # region B                 # Range 2 start
    def flower(self):
        return "random words"

    # endregion                # Range 2 end

    hello = "world"            # Range 1 end

This issue has been fixed in prerelease version 2023.2.11, which we've just released. You can find the changelog here: CHANGELOG.md


VLAN allowed as parent of same VLAN

When editing a VLAN the VLAN I am editing can be selected as it's own parent.
To Reproduce

Got to: Interfaces: Other Types: VLAN
Click on edit for an existing VLAN
Select the VLAN you are editing in Parent interface
opnsense: /interfaces_vlan_edit.php: The command /sbin/ifconfig 'vlan0' name 'igb2_vlan100_vlan100'' failed to execute`
you now have an additional interface vlan0 with MAC 00:00:00:00:00:00

Expected behavior
If QinQ is supported: Do not show the VLAN interface you are editing as possible Parent interface
If QinQ is not supported: Do not show any VLAN interfaces as possible Parent interface
Screenshots
Relevant log files
Additional context
Environment
OPNsense 19.7.2 (amd64, OpenSSL)
APU4

QinQ is not supported, but this looks buggy indeed.
get_interface_list() seem to suggests it doesn't want to return these entries:
https://github.com/opnsense/core/blob/ab75fbb673e1298eade55367d3605ad4101ae829/src/etc/inc/util.inc#L813-L815
But since other consumers seem to expect these entries as a result from the same function (and only omit types like pfsync, pflog from the list) , we probably shouldn't try to repair this here.


Fix bug on elastic search

When input two words or some Unicode texts on the search box, the default elastic search highting plugin will return word1 word2. So the previous codes will try to find word1 word2 and return startIndex = endIndex = -1 which will resutl in panic.
Should fix #12791
Since the new mapping option "term_vector": "with_positions_offsets" added, you have to delete your index previously.
You can try
curl -XDELETE http://localhost:9200/gitea_codes.v1

And restart gitea, the index will be rebuilt.
The new option will increse the space of the index but get faster on returning words positions.

Codecov Report

Merging #12811 into master will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #12811      +/-   ##
==========================================
- Coverage   43.19%   43.17%   -0.03%
==========================================
  Files         651      651
  Lines       72138    72158      +20
==========================================
- Hits        31163    31155       -8
- Misses      35928    35952      +24
- Partials     5047     5051       +4

Impacted Files
Coverage Δ

modules/indexer/code/elastic_search.go
0.00% <0.00%> (ø)

modules/indexer/stats/queue.go
64.70% <0.00%> (-11.77%)
:arrow_down:

modules/indexer/stats/db.go
43.47% <0.00%> (-8.70%)
:arrow_down:

services/pull/check.go
47.69% <0.00%> (-6.16%)
:arrow_down:

services/pull/temp_repo.go
26.59% <0.00%> (-3.20%)
:arrow_down:

services/pull/patch.go
66.37% <0.00%> (-2.59%)
:arrow_down:

modules/git/command.go
88.34% <0.00%> (-1.95%)
:arrow_down:

modules/log/event.go
57.54% <0.00%> (-1.89%)
:arrow_down:

modules/queue/workerpool.go
58.77% <0.00%> (-1.23%)
:arrow_down:

services/mirror/mirror.go
19.93% <0.00%> (+1.35%)
:arrow_up:

... and 5 more

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 25c870f...8cf40ee. Read the comment docs.

@zeripath done.

@zeripath done.

So need to figure out what happens with  content

@zeripath Updated on the first comment of mine.


refactor(wallet): added second wallet to e2e test

Context
added second wallet to e2e test

I think it's just missing TIME_SETTINGS_PROVIDER variable in workflow config


vaadin-combo-box with label and placeholder are not displayed correctly when the material design is applied.

Description
The vaadin-combo-box's label and placeholder are one over the other when the material design custom style is applied.

Expected outcome

The vaadin-combo-box label is display and when we click the vaadin-combo-box label go on top and the placeholder appear.
The vaadin-combo-box label is fixed on top when there is a placeholder.

Actual outcome
The placeholder and the label are one over the other
Steps to reproduce

Put a vaadin-combo-box element in the page.
Put a vaadin-text-field element in the page.
Add the vaadin-text-field material design theme.
Open the page in a web browser.
See the bug

<link rel="import" href="../bower_components/vaadin-material-theme/vaadin-text-field.html">
<link rel="import" href="../bower_components/vaadin-combo-box/vaadin-combo-box.html">
<link rel="import" href="../bower_components/vaadin-text-field/vaadin-text-field.html">

<vaadin-combo-box label="City" placeholder="Enter or Choose a City" items="{{cities}}"></vaadin-combo-box>
<vaadin-text-field label="City" placeholder="Enter a City"></vaadin-text-field>

Browsers Affected

[x] Chrome
[x] Firefox
(Can't test) Safari
[x] Edge
[x] IE 11
(Can't test) iOS Safari
(Can't test) Android Chrome

Issue open first in vaadin-combo-box #586

Thanks a lot for reporting this issue. We have identified many issues with material-theme so please be patient with us if we do not get to this issue you reported soon enough.

This is fixed in master. Tested using the latest vaadin-combo-box version (4.0.1)


Use separate KV library

https://github.com/SteamDatabase/ValveKeyValue
We can switch as soon as KV3 is supported. Should we be using nuget or merely have a reference to the project?

I have some progress rewriting KV3 text parser here: https://github.com/SteamDatabase/ValveKeyValue/pull/61


64bit support for Adobe AIR .ane extension

Hi
According to https://developer.apple.com/news/?id=10202014a all ios application and anes must have 64-bit iOS compatibility since 1 feb 2015 . Adobe supports it in AIR 16 SDK. Do you have plans to rebuild your extension?
Error message while packaging .ipa file:
Error: libMobileTracking.a are required to have universal iOS libraries. Please contact the ANE developer(s) to get the same.
Thx

I, too, am very interested in this. Any update here?

Hi all, we're testing the 16.0 build for release later this week. In the meantime you may try using the ANEs from the "beta" branch that we used 16.0 beta to build.

Please try the latest ANE release which has 64-bit iOS compatibility.


Build a House Price Predictor with SAP AI Core

Tutorials: https://developers.sap.com/tutorials/ai-core-code.html

Hello!
I've noticed in Step 13, the tutorial text mentions to use

docker upload docker.io/<YOUR_DOCKER_USERNAME>/house-price:02

However, this throws an error that upload is not a docker command. The correct version:

docker push docker.io/<YOUR_DOCKER_USERNAME>/house-price:02

can be seen corrected in the image right below this text.
Hope this helps!
Cheers, Kai

Dhrubajyoti, can you please follow up on this issue?

Hi @jmmargo , @Kai-Klatt ,
Thanks for the feedback. It has been fixed now.
Please note that it will take some time to reflect in the tutorials.
Regards,
Neelesh.
(cc: @dhrubpaul)