Updated  s3-deploy to use s3-deploy-action

I tested changing topBranches and it worked:
https://activity-player.concord.org/index-update-s3-deploy-02-21-2023.html
I'm going to revert that change and rebase this into one commit.


fix(spinner): add new fix

Spinner Fix2
Description
Previous fix doesn't fix the issue.
Related Issue
Spinner issue
Types of changes

[ ] 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 change)
[ ] Documentation update
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

To understand what the issue is here's a codepen to explain the issue: https://codepen.io/torgeadelin/pen/ExWvzEY
null scss variables translate to "" (empty string) and when the scss is built the css code looks like: color: var(,someColor) whici is wrong.

Because of the introduction of --null instead of the scss null, in mixins, when both the scss variable and css variable are null, the property using them will result in property: var(--null,) which breaks the style in some places.
From now one, all changes related to theming in mixins should be wrapped in
@if $scssVariable {
  property: $scssVariable;
  property: var(--css-var, $scssVariable);
}

to prevent the whole property to be applied on the element with the broken property: var(--null,).
Again, when you need to change other scss (not mixins) you shouldn't have to wrap the property with @if because the scss variable would most likely have a defined values and won't be null (like in mixins).

Also, first one seems like it's moved?? It was flaky on my local machine.
Regarding the Percy issues with the icon, I think it's due to timing issues?


fix: some bech32 addresses were not recognised

Fix for https://github.com/OutCast3k/coinbin/issues/207
Coinbin was relying on base58check to throw an error in order to do a check for bech32 address format.  However if base58check passed (as is the case with this issue), the code would continue to test the checksum and declare its input as invalid and return without checking if the input was a valid bech32 address.

Thanks. Nice work, will test some more later today and accept it shortly.


Set transaction parameters manually (advanced)

What is this feature about? (1 sentence)
When initiating a new transaction, it is possible to set the transaction nonce, gas price and gas limit manually as an advance feature.
Why is it needed? What is the value? For whom do we build it?

As an advanced user I want to be able to set the transaction parameters manually so that I can have full control over the transaction for special use cases or in case there are some issues with the interface
Some owner wallets such as hardware wallets don't allow to modify the gas limit and price later on. We got the feedback several times that users are missing this.

High-level overview of the feature

This feature should work for all tx modals, i.e. send assets, contract interaction, settings change, Safe apps, etc.

This is an an advanced feature, meaning it should not clutter the interface for regular users.

There could be an advanced section on the tx modal access this hidden feature (e.g. through a gear icon or a "advanced settings" dropdown or similar)
Alternative: First activate this in the Safe settings (we could introduce a new "Advanced features" tab in the settings where features such as this can be toggled on/off).

Parameters to set in this version:

Safe transaction parameters: Safe nonce, safeTxGas
Ethereum transaction parameters:  Nonce, Gas limit, Gas price

Note: Safe transaction parameters will be taken into account no matter if the confirmation happens on or off-chain. Ethereum tx params are only relevant for on-chain confirmations and executions. But we don't know that upfront.

Updates

Nov 5, Tobi: Add more details
Nov 5, Tobi: Added params and note

Also to consider: When using our direct Ledger integration, users aren't able to set the gas price on the Ledger. So that would have to be done via our interface (cf. gnosis/safe#314)

Just received some user feedback where the following scenario leads to inconveniences:
- 2/3 Safe with owners a,b,c
- there's a disagreement, a and b want to remove c
- before they can trigger the tx, owner c "spams" the safe with transactions so send all company funds to itself, re-creating the same txs multiple times.
-> Currently, A and B would have to manually reject all those spam txs before they can get their tx to remove the owner through.

@rmeissner
I have 2 open questions about this feature:

Should we differentiate between base gas and safetxgas?
Should this feature only be available when the user executes a tx or confirms on-chain, i.e. not for off chain signatures?

I think "yes" in both cases. Do you agree?

@posthnikova this is another upcoming web feature that would require design.

@rmeissner
I have 2 open questions about this feature:

Should we differentiate between base gas and safetxgas?
Should this feature only be available when the user executes a tx or confirms on-chain, i.e. not for off chain signatures?

I think "yes" in both cases. Do you agree?

We don't necessarily know if the user will end up confirming on-chain or off-chain when creating a transaction. As this should be a "hidden / advanced feature" anyways, I think it's not that critical to also have it enabled when the user eventually ends up confirming off-chain though. There's not much downside if someone sets the gas price manually and then signs off chain as this only means the user doesn't have to pay any gas at all & confirmation is instant.

Just to recap (primarily for myself)
There are 2 types of advanced settings:

Safe transaction settings (e.g. Safe transaction nonce, safe tx gas, ...)
Ethereum transaction settings/ Wallet settings (e.g. gas limit, gas price, nonce, ...)

I think first we should define which of these should be able to be set before I can tell you what do differentiate.
For 1. I would only allow to adjust the nonce and the safeTxGas of the Safe transaction. And have the option to set a refund in a later version. But if we allow to specify really all parameter then we definetly need to differentiate between baseGas and safeTxGas (as they have totally different purposes).
For 2. As Lukas said, we actually don't know ahead of time how the confirmation will be created so I would also always display this.

Okay, thank you both for your responses! I updated the ticket description. I think we should start with the following params then in this version:

Safe transaction parameters: Safe nonce, safeTxGas
Ethereum transaction parameters: Nonce, Gas limit, Gas price

I'm for activating it first in advanced settings. This way it doesn't clutter the interface for everyone.
A proposal for sending funds:
https://invis.io/BRZDPI8XPG5
When it's enabled there will be an additional step in send popups. I assume you can leave any field or all fields empty.

Activating this in the settings assumes that there are two kinds of users:

Users that want to set the parameters manually most of the times
Users that don't want to set them manually.

However, I would assume that the lines aren't that clear. And users occasionally would like to set the parameters manually, but most of the time don't want to do so. This is why I would vote for not having to activate the feature in the settings. Also, this would probably make the feature less discoverable and would maybe mean more effort/complexity as there needs to be two different flows depending on whether the setting is activated.

Having a simple "advanced options" setting doesn't clutter the interface that much in my opinion.

There could also be a third option, i.e.

Option 1: toggle in settings and then there's always that additional step in the tx flow
Option 2: No toggle in settings, there's always this "advanced options" thing in the tx flow (so like Metamask)
Option 3: Combining the other 2 options by having a toggle in the settings and only then you see the Metamask-like "advanced options" button

Or always show the transaction details in the review screen and have a "Edit" button to customize. I think that would add value also to users that don't want to set the parameters manually. As even if a user doesn't want to edit the parameters, knowing them before triggering the transaction might be of benefit to users.

Also, we should probably also have seperate screens for confirmations/executions. As there, compared to initial transaction creation, the SafeTxGas and Safe nonce cannot be set. Potentially we can still display it there, but show that they are non-modifiable.

Also, we should probably also have seperate screens for confirmations/executions. As there, compared to initial transaction creation, the SafeTxGas and Safe nonce cannot be set. Potentially we can still display it there, but show that they are non-modifiable.

Hm, I generally agree with you, but that's something to check with the devs as they told me that it'll be tricky to figure out if it's an execution/on-chain or off-chain confirmation.

I wouldn't try to anticipate whether it's on- or off-chain. I meant that there should be a difference between:

Creating a new Tx (Send funds, new contract interaction, new Safe App interaction)
Conirming / executing transaction

As with the former category, the user can potentially set the SafeTxGas and Safe nonce, but with the latter, this is not possible anymore.

ah, yes, the safe related items can only be set when creating the tx, not afterwards when confirming  / executing.
I was referring to the Ethereum related items.

I have 2 versions, from settings and from Send popup https://invis.io/BRZDPI8XPG5. We don't have data what users prefer, I can include it in the upcoming user test.

Or always show the transaction details in the review screen and have a "Edit" button to customize.
I think that would add value also to users that don't want to set the parameters manually. As even if
a user doesn't want to edit the parameters, knowing them before triggering the transaction might be of
benefit to users.

I wouldn't show parameters the user didn't configure on Review screen. I would offer to edit them earlier.

I like the version with the "Advanced options" button a bit more. But you're right, we don't have data. We just know how Metamask does it.

Hey team, just found this while searching for a way to manually set gas limit, since our transactions (inner, not outer) are failing due to out-of-gas. Is there a workaround while this feature is being developed?

@illuzen in case you are triggering transactions via Safe apps, then there's a new feature in the Safe apps SDK available to set the safeTxGas (gnosis/safe-apps-sdk#21).
If that's not an option, then the only workaround is to trigger a transaction via our API at https://safe-transaction.gnosis.io/. There is a POST endpoint that allows you to create new transactions which then popup at https://gnosis-safe.io/app/ when you sign them with an owner of the Safe. Would that work?

People preferred the option with 'Advanced' in Send popup so now it's the main version: https://invis.io/BRZDPI8XPG5.
Small change: popup height is the same (except the Review step when advanced parameters were set). We don't know on step 1 whether advanced parameters would be changed so it doesn't make sense to make the height of popup match the 'Review with advanced' height.

Hey team, just found this while searching for a way to manually set gas limit, since our transactions (inner, not outer) are failing due to out-of-gas. Is there a workaround while this feature is being developed?

@illuzen We released a fix for the Safe Multisig interface today (v2.15.1.) that should fix the gas limit estimation issues related to Safe Apps.

People preferred the option with 'Advanced' in Send popup so now it's the main version: https://invis.io/BRZDPI8XPG5.
Small change: popup height is the same (except the Review step when advanced parameters were set). We don't know on step 1 whether advanced parameters would be changed so it doesn't make sense to make the height of popup match the 'Review with advanced' height.

We should also have versions for:

Safe App transactions
Collectible transfers
Contract Interactions
Confirmations

For Safe App transactions, regular asset transfers, contract interactions and collectible transfers, the Ethereum transaction parameters only make sense if it's a 1-oo-x Safe, as or >1 threshold the Ethereum transaction parameters are set with the final (executing) confirmation. Should we still display those in all cases?
For the pure confirmation/execution case, the Safe Transaction parameters should not be able to set, only the Ethereum transaction parameters. As at this point the Safe transaction parameters cannot be changed.

For Safe App transactions, regular asset transfers, contract interactions and collectible transfers, the Ethereum transaction parameters only make sense if it's a 1-oo-x Safe, as or >1 threshold the Ethereum transaction parameters are set with the final (executing) confirmation. Should we still display those in all cases?

Ideally no, only the configurable things should be dislpayed, if possible, i.e.
Safe-related params: Only when initiating a transaction as the first signer. It can't be modified afterwards. - Perhaps a read-only display of those would make sense?
Ethereum-related params: Only when the current signer can also execute, otherwise it doesn't make sense. - How about on-chain confirmations in that case though?

Let me break down the options here. There are cases when you can set some of the parameters and cases when you can set none. Plus some parameters could be modified by other owners before you.

@posthnikova Nice over view, thank you. This all looks correct to me.

@posthnikova a case for on-chain confirmations are missing. e.g. when the owner of a safe is another Safe or e.g. argent, then it would be an on-chain approval. In that case, Ethereum params could be set for that confirmation tx.
As far as I understood the devs, we don't know upfront, if the wallet wants to do an on or off chain approval. So that needs to be clarified again.

Richard: Please note, currently for 1.0.0 Safes, we force on-chain confirmations.

Was done to make people update their contract
No other reasons, could be changed.

As far as I understood the devs, we don't know upfront, if the wallet wants to do an on or off chain approval. So that needs to be clarified again.

In a v1, we could say to always show the Ethereum tx params in all cases.

As far as I understood the devs, we don't know upfront, if the wallet wants to do an on or off chain
approval. So that needs to be clarified again.

Do you mean at the moment of creation we don't know this? Or at the moment of confirmation? Because we shouldn't say that this confirmation is off-chain then.

Or at the moment of confirmation? Because we shouldn't say that this confirmation is off-chain then.

At the moment of confirmation. But someone from the dev team needs to comment on this if this is actually true.

@illuzen We released a fix for the Safe Multisig interface today (v2.15.1.) that should fix the gas limit estimation issues related to Safe Apps.

Thanks @lukasschor, any ETA on when this upgrade will be available thru the web interface? We are still experiencing the same gas limit issues.

Thanks @lukasschor, any ETA on when this upgrade will be available thru the web interface? We are still experiencing the same gas limit issues.

This issue was added to the next release which we plan to release in ~2 weeks.

@rmeissner I'm not sure to understand how safeTxGas works, do we have documentation on this?
@tschubotz can we assume all the users will know what safeTxGas means? In case we can't, should we add an explanation in the UI?

@nicosampler you can find the docs here: https://docs.gnosis.io/safe/docs/contracts_tx_execution/#safe-transaction-gas-limit-estimation
This is an advanced feature and in a first version I would be fine without an explainer, but we could also link to the docs as a simple workaround in a first iteration :)

safeTxGas attempt of explanation:
It's the amount of gas excectTransaction can use. If the parameter was set to 0, the contract will assume it can spend all remaining gas, if it's > 0 the gas set by the Wallet should be always greater than safeTxGas, otherwise it will fail.
https://github.com/gnosis/safe-contracts/blob/development/contracts/GnosisSafe.sol#L145

Regarding Sasha's designs and Lukas's comment https://github.com/gnosis/safe-react/issues/838#issuecomment-726053014, I will implement it so the review screen always includes the details. I believe this information is important.
If in the future the users complain about it, we can modify it so it's only shown if the user clicked on advanced options.

@tschubotz @posthnikova @lukasschor
I would like to suggest a change (it was previously mentioned before).
I think it would be better if we remove the "Advanced options" link for the TX screen and show it instead on the review screen.
The main reason for this change is that if the user clicks on "Advanced options" and then in "Confirm" it will be redirected to the "Review screen" and perhaps he didn't finish with the TX parameters (Address, value, etc). Also, it would be kinda weird if in the "review screen" he clicks on "back" and is redirected to the TX parameters instead of "Advanced options".
If you accept this change, the "Advanced options" screen should only have 1 button "confirm". It will help the user to understand that if he did not edit the inputs, the default values will be used.

I like that proposal since it would be similar to what metamask does. However I wouldn't allow the user to confirm a tx right from the advanced parameters screen. I think they should get back to the review screen again where they have to click "confirm"

Initially it was intended that 'Confirm' from Advanced parameters goes back to tx parameters (recipient, amount).

I think they should get back to the review screen again where they have to click "confirm"
Yes that's what I wanted to say

Initially it was intended that 'Confirm' from Advanced parameters goes back to tx parameters (recipient, amount).

@posthnikova that means though that if they notice on the review page that they want to change something in the advanced params, they would have to

Go back
Open advanced params
Save, so they end up on the tx param screen.
Review

Whereas when we allow them to modify the advanced params from the review screen, that would be way shorter. What do you think about that? Wouldn't that be simpler?

Wouldn't that be simpler?

I think they should get back to the review screen again where they have to click "confirm"

There's a additional click to 'Submit' transaction so the number of clicks is equal. For me both solutions are ok. We don't know how many users would want to configure advanced parameters. Always showing them on Review screen assumes everyone would want to see them.

regarding the gas price I can bet everyone wants to see it :stuck_out_tongue_closed_eyes:

@posthnikova what do you think if in this screen we make "tx details" collapsible?

Do you mean recipient and amount?

no I mean this

We can do this but the popup would scroll anyway in expanded state.

yes, I suggest it as an intermediate alternative to "show it always" or "when the user changed the options".
If we make it collapsible the UI is barely modified and we have the best of the two options. if some users don't want to pay attention to the gas cost they won't expand it.

Updated structure with advanced options on Review step.
Send funds, 1 out of x Safe or hardware wallet:

Send funds, >1 out of x Safe:

Other popups are pretty much the same, parameters you can't set are disabled:

Send collectible:

Contract interaction:

Safe app transaction:

awesome, love it!

I like this new version as well! Main reasons:

Clearly marked as "advacned options"
I can review it even though I don't edit it.
I see more clearly what can be changed and what cannot.

Zeplin screens:

Advanced Settings: https://zpl.io/a3L0K0Y

Send Funds

Send Funds (Review):https://zpl.io/Vx7nkkg

Send Funds (Review - Advanced Expanded): https://zpl.io/bAenmzO

Advanced Popup: https://zpl.io/a7XeGEv

Send Funds (Review, disabled Ethereum parameters): https://zpl.io/VKX6EgA (for >1 out of x Safes and hardware wallets)

Advanced Popup, disabled Ethereum parameters: https://zpl.io/bPw1rpM (for >1 out of x Safes and hardware wallets)

Contract Interaction

Contract Interaction (Review): https://zpl.io/2yr17m9

Contract Interaction (Review - Advanced Expanded): https://zpl.io/a3M90my

Send Collectible

Send Collectible (Review): https://zpl.io/adgRM7L

Send Collectible (Review - Advanced Expanded): https://zpl.io/VOl1XzY

Safe Apps

Safe Apps Transaction (Review): https://zpl.io/amQeMzK

Safe Apps Transaction (Review - Advanced Expanded): https://zpl.io/2ppPxnN

Confirmation and execution popups will be later.

@rmeissner can you help me to elaborate on a list of validations for the form?

safeTxGas can not be lower than eth gas limit
safeNonce and ethNonce: it can be empty, but if the user enters a number, what should I check? for example if the nonce should be greater than the last one mined.
of course, all values should be > 0.

@rmeissner can you help me to elaborate on a list of validations for the form?

safeTxGas can not be lower than eth gas limit
safeNonce and ethNonce: it can be empty, but if the user enters a number, what should I check? for example if the nonce should be greater than the last one mined.
of course, all values should be > 0.

For 2. Inwould check agaibst on-chain info (or no check atball isbalso fine for me in a first version, up to @tschubotz )
For 3. safeTxGas can be 0 (the nonces too actually)
Aldo this should be added to the issue description ;)

For 2. Inwould check agaibst on-chain info (or no check atball isbalso fine for me in a first version, up to @tschubotz )
For 3. safeTxGas can be 0 (the nonces too actually)
Aldo this should be added to the issue description ;)

the nonces too actually

yes, I wanted to say no negative values

the nonces too actually

yes, I wanted to say no negative values

For 2. Inwould check agaibst on-chain info (or no check atball isbalso fine for me in a first version, up to @tschubotz )

Both fine for me too. I think there is no need add more logic. It's an advanced feature, so people should know what they are doing in my opinion.

For 2. Inwould check agaibst on-chain info (or no check atball isbalso fine for me in a first version, up to @tschubotz )

Both fine for me too. I think there is no need add more logic. It's an advanced feature, so people should know what they are doing in my opinion.


A few UI improvement suggestions

Make the link image (chain image) clickable

Shall we make the "read only" part look like a label? Currently it looks like a button.

Use  the standard download button

Except for Read only label improvement other 2 suggestions were fixed in https://github.com/wso2/carbon-apimgt/pull/10420


Revert "Handle Multiple Models in deployment"

Reverts microsoft/dstoolkit-mlops-base#61
The scoring.py currently supports only one model. It is needed to change too.

Accepted Revert


Timestamp in video

I wold like it when i cold set it up to split videos with preexisting timestamps. I seek such a downloader since i cold think about the use of it.

What do you mean by "split"? Do you mean start the video from a specific timestamp like YouTube allows you to?

I think what he means is to be able to clip video based on timestamps. So if there are 3 timestamps in the video, the downloader will download it in 4 separate pieces.

I mean what arsinclair wrote. Sorry English is not my native language.

I think it's pushing the scope of the project a bit too wide. I'd suggest downloading the whole video and then splitting them in specialized tools like FFmpeg or video editors.


Logo request: Tekton Results

cc @adambkaplan (feel free to correct / add any additional details!)
Project Objective
Tekton Results is a Tekton sub-project that aims to help users logically group CI/CD workload history and separate out long term result storage away from the Pipeline controller. This allows you to:

Provide custom Result metadata about your CI/CD workflows not available in the Tekton TaskRun/PipelineRun CRDs (for example: post-run actions)
Group related workloads together (e.g. bundle related TaskRuns and PipelineRuns into a single unit)
Make long-term result history independent of the Pipeline CRD controller, letting you free up etcd resources for Run execution.
Store logs produced by the TaskRuns/PipelineRuns so that completed Runs can be cleaned to save resources.

How the logo would be used, where it will be placed
Primarily on the repo (https://github.com/tektoncd/results) + any external materials (e.g. talks, blogs, etc).
Logo ideas
Would like to stay on-theme with the other sub-project logos https://github.com/cdfoundation/artwork/tree/main/tekton/additional-artwork

"Archives" - e.g. file cabinets, floppy disks, etc.

Deadline / Timelines
None

Thanks @wlynch.
We submitted an LF Design Request and will get back to you as soon as we get response to the request.

I started a poll on the Results project to get direct community feedback: https://github.com/tektoncd/results/discussions/451

@fdegir feedback from the community (source):
Concepts A and B combined had the plurality of votes. Consensus is that using "B" as the base (with the file icon in the background) with design elements from A could work. The "circuit board" design elements in B didn't resonate. For reference/inspiration, I used a "cat in file cabinet" image in my cdCon presentation for Results, and that elicited positive reaction from the audience.
Concept E had a large number of votes, but many of the active contributors rejected it in subsequent working group meetings. Concepts C and D had the least votes.

Thanks @adambkaplan. I passed the community feedback to our team and will get back to you under this issue as soon as I hear back.

@wlynch @adambkaplan Our team updated the design based on community feedback. Could you please take a look at it in this file and let me know of your feedback?

@fdegir apologies it's taken a while to get back - based on our discussion, this version feels too cluttered an can be simplified. We suggested the following:

The "folder" can be made smaller so only the top is visible.
The two extra lines near the cat's neck can be removed.
Padding around the cat's face doesn't appear to be consistent (especially around the ears).
Remaining icons can be adjusted (and/or removed) to achieve a balanced look and feel.

See also https://github.com/tektoncd/results/discussions/451#discussioncomment-6191062

Thanks @adambkaplan! I passed the feedback to our team and get back to you once I hear back.

@adambkaplan Please find the new concept attached and let me know of the feedback from the community.
TektonResults-LogoConcepts-v3.pdf

@fdegir apologies for the delay on this, it was on my queue and slipped through the cracks.
:+1: on v3 of the logo! https://github.com/tektoncd/results/discussions/451#discussioncomment-6627199

@adambkaplan @wlynch Sent the Tekton Result logos based on v3 via a pull request to artwork repo. Could you please take a look?


Update ReadMe

Added links to ReadMe.
Add more information about device sync

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.056%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2775

Relevant Lines:
3116

💛  - Coveralls

@mongodben I will appreciate it if you can review this ReamMe.


Emacs lock files cause an UnhandledPromiseRejectionWarning in ng serve

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[X] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Description
Emacs lock files cause an UnhandledPromiseRejectionWarning. The lock file .#filename is actually a symlink pointing nowhere and seems to break the webpack watcher. Also, the lock file is generated once I type anything into the emacs buffer (and not while saving), so there is no point in watching the lock files.
$ npm run start
[...]
chunk {main} main.js, main.js.map (main) 57.7 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 141 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.15 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 12.9 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 2.41 MB [initial] [rendered]
Date: 2020-07-23T08:30:17.123Z - Hash: 86e8ae79c0fc07f7c92b - Time: 5696ms
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
: Compiled successfully.
(node:3270950) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, stat '/home/vbraun/myproject/src/.#main.ts'
(node:3270950) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

Apart from flooding the console with spurious errors the watch&rebuild seems to work
🔬 Minimal Reproduction

$ npx ng new
$ cd myproject
$ npm run start
$ emacs src/main.ts

🌍 Your Environment

$ npx ng version

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 10.0.4
Node: 12.16.3
OS: linux x64

Angular: 2.4.10
... compiler, compiler-cli, core
Ivy Workspace:

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1000.4
@angular-devkit/core         10.0.4
@angular-devkit/schematics   10.0.4
@angular/cli                 10.0.4
@angular/tsc-wrapped         0.5.2
@ngtools/json-schema         1.1.0
@ngtools/webpack             1.10.2
@schematics/angular          10.0.4
@schematics/update           0.1000.4
rxjs                         6.5.5
typescript                   2.0.10
webpack                      2.2.0

An even easier repro is to just create a dangling symlink in the project root:
$ ln -sf foo bar
$ npx ng serve
[...]
(node:3427060) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, stat '/home/vbraun/myproject/bar'

@vbraun, I tried to replicate this but I didn't get the mentioned error
test git:(master) ✗ ln -sf foo bar
➜  test git:(master) ✗ ng serve

chunk {main} main.js, main.js.map (main) 60.6 kB [initial] [rendered]
chunk {polyfills} polyfills.js, polyfills.js.map (polyfills) 141 kB [initial] [rendered]
chunk {runtime} runtime.js, runtime.js.map (runtime) 6.15 kB [entry] [rendered]
chunk {styles} styles.js, styles.js.map (styles) 13.5 kB [initial] [rendered]
chunk {vendor} vendor.js, vendor.js.map (vendor) 2.64 MB [initial] [rendered]
Date: 2020-07-23T14:18:30.115Z - Hash:<PHONE_NUMBER>55d0f39f47 - Time: 4809ms
** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
: Compiled successfully.

Hmm, package version mismatch? I've just installed the newest from npm.
Downgrading to<EMAIL_ADDRESS>kludges around the issue for me (either by downgrading to watchpack 1.6.1 or getting rid of watchpack's vendored version):
$ npm install<EMAIL_ADDRESS>$ rm -rf node_modules/watchpack/node_modules/chokidar
$ npx run serve
... no more UnhandledPromiseRejectionWarning ...

I also tried node v10 and v14, but no dice: Still get the same UnhandledPromiseRejectionWarning

@vbraun, so I did try to replicate this again this time in a Linux container and I did manage to replicate it.
This will need some digging.

This is probably https://github.com/paulmillr/chokidar/issues/955

Exactly the same here, a temporal solution waiting the release might be to add this line in .emacs file:
(setq create-lockfiles nil)
But this solution should only be temporary and/or rely on more often backup files.

Exactly the same here, a temporal solution waiting the release might be to add this line in .emacs file:
(setq create-lockfiles nil)
But this solution should only be temporary and/or rely on more often backup files.

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.


Implement Interpreter::is_user_function() using std::option

It could be cleaner and would be more idiomatic to implement the Interpreter::is_user_function() method using the Option return type from the std::option module.

Implemented on development branch (0.20.4). Will merge into main in the near future.


Update supported hardware: works on TI84P

I've been using this program on my TI84P extensively since November, so I can confirm that it does work. I think this amount of testing suffices.
Also, it was working on an older OS version too because I forgot to update it when I bought the calculator, but we'll just encourage latest ver.

Thanks for the testing the app!
I can't add the wording as you have written it, because I don't own the 84+, so I would be lying to say that I have personally tested it. I have replaced the 2 instances of this sentence with
https://github.com/bxparks/rpn83p/commit/95b2d61a6a5b1b0da816add5960d9823e871483b

Yeah, seeing you point it out, I realised that wording works better.


Uable to render new file in the PDFViewer

Hi,
I'm trying to render different files in the PDFViewer, but however, it always shows the first selected file and does not update when other files are selected through the props!
This is how my component looks like:
>  <PDFViewer
>                   document = {data.docInfo[0].docUrl}
>               />

and the render method for PDFViewer.js looks like
render() {
  const source = this.props.document;
  console.log('Source in render: ', source);
    const {
      loader,
      navigation,
      css,
    } = this.props;
    const {
      page,
      pages,
    } = this.state;
    const NavigationElement = navigation;
    const pdf = (
      <PDF
        file = {{url: source}}
         />

The value of the source changes each time i select a new file, but the Viewer always shows the old PDF file.

Hi,
The document prop of PDFviewer should be an object with url field, while you are passing url directly. Try to change this and let me know if that works
Best,
Nikita

Well by making the document prop of the PDFviewer to be an object with url field,
<PDFViewer
   document = {{ url: data.docInfo[0].docUrl}}
              />

I get an error in the console:  GET http://localhost:3001/[object Object] 404 (Not Found)
the const pdf console logs as given below:
pdf: $$typeof: Symbol(react.element)
key: null
props:
cMapPacked: false
cMapUrl: "../node_modules/pdfjs-dist/cmaps/"
file:
url: {url: "https://s3.us-east-2.amazonaws.com/mobimed-data/%2…0fae49b8d12195b9624b75a06303984ff883f5b6d345e598b"}
__proto__: Object
loading: undefined
onDocumentComplete: ƒ (pages)
page: 1
scale: 0.5
__proto__: Object
ref: null
type: ƒ ReactPdfJs()
_owner: ReactCompositeComponentWrapper {_currentElement: {…}, _rootNodeID: 0, _compositeType: 0, _instance: PDFViewer, _hostParent: ReactDOMComponent, …}
_store: {validated: true}
_self: null
_source: null
__proto__: Object

When I see the React Debugger console, i see that the url in the file changes when i select different PDFs, but they don't show up on the canvas somehow! I was wondering why


Edit model fine tuning example

Hey, I suggest that you change the model fine tuning example in two points:

Change AveragePooling2D to GlobalAveragePooling2D
Add a softmax layer. I was so retarded to try to optimize a model without for two hours.
Thanks :D

Yes, you are right, good catch! Thank you, I will change it.

Thanks!


chore: update axios due to CVE

There's a CVE for axios < 0.21.1.
See https://github.com/advisories/GHSA-4w2v-q235-vp99
Closes #633

Note - Haven't yet tested, but have emailed asking for a token.

Just testing this now. I'll merge once the tests pass.

Just testing this now. I'll merge once the tests pass.


Add NewFile for instantiating File from *os.File

Thanks for this great library.

Hello @cedws
Thanks for your contribution.
Normally, an API like New() should take an io.Reader but because we are using memory mapped APIs to map the file, we need a file descriptor, so I believe it's ok to have NewFile.

A new tag v1.5.6 is released that contains this feature.


Delete account and all data

Story
As a user I want to be able to delete my account with all its data, in order to leave no trace (GDPR).
Preconditions

user is logged in

Post conditions

user profile is deleted in the database
all ads created by the user are deleted in the database

Dependencies
This story can only be started after Story Nr. 59 has been completed.

DoR

[x] External dependencies are identified or eliminated
[x] Design (at least LoFi?)
[x] Has acceptance criteria

Acceptance Criteria

[x] the user is able to delete all his data under settings/mein profil ->
[x] with the press of a button, all related user data and ads created by the user are deleted in the database. ->
[x] when pressing the "delete my profil and all data", a modal/pop-up must show up that warns the user a last time about the not reversible action.
[x] The message on the button must be in context of the language of the member

DoD

[x] Story is tested against acceptance criteria
[x] Unit test should be passed
[x] Integration test is done ( if applicable)
[x] Non-functional requirements are met
[ ] Story ok-ed by Product Owner
[x] Peer Code Review performed
[x] Any configuration or build changes documented
[x] any database changes are documented Database

This ticket is for analysing and working on for the BA. It may be splitted into a part "update" ad or "delete" ad or "delete all my data".

@TimmyAeberli and @akrguda please verify if ticket is ready for refinement. Any feedback is welcomed!

Test Environment: Goolge Chrome Browser
Test OS: Windows
Test_Case_1 As a user I want to be able to delete my account with all its data, in order to leave no trace (GDPR)
Test-Steps:

Open the Webpage.
Click on the top right on "anmelden".
Click on “Login”.
Login in to your Profil.
Click in the Profil-Icon top right.
Click in the Dropdown on "Mein Profil".
Click in the Button "Mein Profil und alle Daten löschen".
Confirm the deletion of your data by clicking on “Löschen”
Try to Login in with the same profil as before.
Confirm deletion of all data from the database.

Result:
The user account is deleted and can no longer be used. All data will be deleted from the database.
Test pass 08.02.2023 - 08:00 Uhr


Not Support in laravel 5.4

Problem - sofa/eloquence v5.3.2 requires illuminate/database 5.3.*
don't install laravel/framework v5.4.0

thanks


verified flatpak support for linux.

Please give official support for flatpak
https://flathub.org/apps/com.visualstudio.code
Kindly verified flatpak is really helpful.
### Tasks

No this not duplicate the app that is found in flathub that does not have verified badge.

It's not verified because it's not published by us. We still do not plan on officially supporting it.

Ok but maybe you don't have plan but if you keep this open maybe someone will plan and do it.
@Tyriar

This is just how we run the project. Managing this amount of issues isn't easy and we therefore aggressively close issues that aren't likely to be implemented sometimes, see https://github.com/microsoft/vscode/wiki/Issue-Grooming#out-of-scope-feature-requests

Does the functionality described in the feature request have any reasonable chance to be implemented in the next 24 months?

The answer to that is most likely no due to resources on our end and the burden of maintaining a new package. It was already discussed in https://github.com/microsoft/vscode/issues/7112 and the package is currently maintained by the community.


Arabic translation

From<EMAIL_ADDRESS>on January 30, 2011 20:43:24
Hello
You need to add "ar" to AVAILABLE_LOCALES:
AVAILABLE_LOCALES:["ar","en","fr","de","cs","pl","pt_BR","es","ru","eo"]
:)
Attachment: ar.xml
Original issue: http://code.google.com/p/wwwsqldesigner/issues/detail?id=116

From ondrej.zara on January 30, 2011 23:13:46
Status: Accepted
Owner: ondrej.zara
Labels: -Type-Defect Type-Enhancement

From ondrej.zara on January 30, 2011 23:13:58
Issue 115 has been merged into this issue.

From ondrej.zara on March 14, 2011 00:20:38
Commited in rev. 119, thanks!
Status: Fixed


OI Management/Matrix

Your Vatsim CID
1340265
What do you suggest?
It's definitely a low-priority item.
An OI matrix (AA-ZZ) shows which OI is in use by a home controller or a visitor and probably even a hyperlink to the control profile.
OI validation when changing OI in the controller profile, prompting if the OI is already in use or unavailable (OK, FU).
The old site allows lowercase OIs so people can be AB and ab the same time and that shouldn't be allowed.
Why do you need that?
To make my life easier.
Alternatives
No response
Additional info
No response
Validation

[X] I have searched for other requests and did not find any alike
[X] I have also checked the roadmap, and this is not planned

Also making sure OI's get assigned on first login

Will be added on next update

Low priority. Is there any chance we could assign OIs from here or somewhere similar? Like if I could click on a controller's name from a roster like this https://vzdc.org/controllers/roster/home, it leads to the controller management page. There can be a separate field for the OI, and when I click on it, it leads to the OI matrix, and I can click an available OI within the matrix to assign that OI to the controller. I hope this makes sense.

I can make a drop-down when you click on an operating initial to choose a controller and assign it there.


User in interpreter context

What is this PR for?
The goal of the PR is to pass userName/userInfo from front-end to interpreters.
The PR uses Shiro authentication(https://github.com/apache/incubator-zeppelin/pull/586).
What type of PR is it?
Improvement
Todos

[x] - Change RemoteInterpreterService.thrift signature
[x] - Change InterpreterContext/RemoteInterpreterContext signature
[x] - Modify all existing interpreters to above signature

Is there a relevant Jira issue?
N/A

This is a requisite first step for getting to multi-user scenarios. I believe this should get discussed a little bit in terms of approach.

This is ready for review.

@rconline how would you want to discuss? Should we open a JIRA - or a JIRA parent with subtests for this multi-user auth use cases?

@prabhjyotsingh could you explain more on the reason for this change?
Also this seems like a somewhat big change - could you open a JIRA on this so it could be tracked?

@felixcheung @prabhjyotsingh  The purpose of this discussion should be to get to an approach that allows us zeppelin to do a couple of things - pass user identity to the underlying spark cluster, and thereby support multi-tenancy. There is JIRA open - https://issues.apache.org/jira/browse/ZEPPELIN-645 which we could use to discuss this further. Does that make sense?

I think it make sense to let access authentication info through InterpreterContext.
But i think authentication info will be more than a user name in the future. It can have some credentials/token stuff from Authentication system (shiro), so interpreter process can reuse it without asking authentication again, when they're required.
So my suggestion is, create such class AuthenticationInfo, and pass it into InterpreterContext instead of String userName, for further extension in the future.

Thank you for the suggestion @Leemoonsoo. Have added AuthenticationInfo class, and made relevant changes.

I have tried and it works well.
One thing is, org.apache.zeppelin.display package supposed to have Display System related codes.
I think AuthenticationInfo is less related to Display System. Could you suggest other package name?

Thanks you @Leemoonsoo, that does make a lot of sense.

Thanks @prabhjyotsingh.
It looks good to me.

LGTM

Let's rebase and merge this?

Thank you for reviewing this. Have merged this with master.


ERROR: function takes at most 8 arguments (10 given)

Hey discovered this plugin recently, very cool.
Just started getting this error after running :PluginUpdate this morning when activating CtrlP. Running OS X.
Commenting out
let g:ctrlp_match_func = {'match': 'cpsm#CtrlPMatch'}

fixes the issue.

You need to re-run install.sh after updating to rebuild the Python extension.

That did it, thanks!


[fixes #7348]Changed the SummaryAdmin view to have the same "New Translation" link as the Editor view

This change should prevent the creation of culture duplicates that was caused by having a different "New
Translation" link between the two views.
fixes #7348

I made the changes as per @sebastienros comments.
I also made a couple more changes to the driver because I found that if I deleted a MasterContentItem and then attempted to create a New Translation from a content, the list of cultures to choose from would not be correct.
I am reluctant to change the Setter used for the MasterContentItem (see in LocalizationPartHandler) because I am not 100% what that would impact.

I made that change we discussed in the comments to the earlier version.
I also fixed the line where the MasterContentItem is assigned in the TranslatePOST method of the AdminController.

The way things work in this PR, I use the fact that part.MasterContentItem is not null when the MasterContentItem has been deleted, so at this point I am happy with the way the Setter for it works.
Down the line, it may make sense to consider how to rewrite that so there's less hoops to jump through to make things happen. I would expect no major rework for it: it may be enough to add a check in the LocalizationPart's MasterContentItem's getter.


Update rpoject name

test

@captcha17 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


Web Mercator (EPSG:3857) not detected correctly

I'm attaching a sample DEM file in webmercator coordinates. geotiff-geokeys-to-proj4 gives a Proj4 string for an ellipsoid, which is incorrect:
+proj=merc +lat_0=0 +lon_0=0 +x_0=0 +y_0=0 +ellps=WGS84 +a=6378137 +b=6356752.314245179 +pm=0 +axis=en +no_defs

gdalinfo gives a correct string:
+proj=merc +a=6378137 +b=6378137 +lat_ts=0 +lon_0=0 +x_0=0 +y_0=0 +k=1 +units=m +nadgrids=@null +wktext +no_defs

These are the geokeys:
{
  "GTModelTypeGeoKey": 1,
  "GTRasterTypeGeoKey": 1,
  "GTCitationGeoKey": "WGS 84 / Pseudo-Mercator",
  "GeogCitationGeoKey": "WGS 84",
  "GeogAngularUnitsGeoKey": 9102,
  "ProjectedCSTypeGeoKey": 3857,
  "ProjLinearUnitsGeoKey": 9001
}

And here is the file:
dem.tif.zip

Hello, thanks for reporting this! I'll be able to check this at the end of this week. Wanted to do that today but forgot that I have unfinished work for this project to do. I'm sorry for the delay.

Thanks for looking! I haven't had time to look at the source code to find a possible fix... I did look at the GeoTIFF spec and noticed that ProjectedCSTypeGeoKey belongs to GeoJSON version 1.0, and has been replaced by ProjectedCRSGeoKey...  I wonder if the key change is related to this issue.

I wonder if the key change is related to this issue

Good call! I've recently introduced GeoTIFF 1.1 support, maybe alias is broken. There's also wrong ellipsoid axis, and +lat_0 being used instead of +lat_ts. I can't tell right away what's wrong, need to look into EPSG database.

Hello! I've got some information regarding ellipsoid axes. I've manually traced everything down to ellipsoid, here's my steps:

CRS code is 3857 as you can see in the geokeys.
This CRS doesn't have a datum, but it has a base CRS with 4326 code:

The base CRS has a datum with 6326 code:

This datum is actually a datum ensemble:

This ensemble has 7 members:

My library takes one with the greatest datum_sequence field. Just in case I checked all 7 members, all of them have an ellipsoid with 7030 code.

This ellipsoid has semi-major axis and inverse flattening set:

So there you have it, two different axes.

Moreover, GDAL will give you WKT with a semi-major axes and inverse flattening as well, but proj4 string is indeed like yours:

Since I'm using a EPSG database (geokeys are just EPSG codes, so database from epsg.org is one true data source), and GDAL itself gives the same ellipsoid in WKT, the only sane conclusion is that GDAL's proj4 string building algorithm produces incorrect ellipsoid.

I still have to check why +lat_0 is used instead of +lat_ts, so stay tuned :)

I still have to check why +lat_0 is used instead of +lat_ts, so stay tuned :)

Looks like a different name for the same parameter, added an override. Please try new 2024.4.12 release which should be available in like 10 minutes.
I guess this issue is resolved, but if you have another opinion, feel free to reopen it. Thanks for the report!

Huh, in both QGIS and my viewer, GDAL's proj4 string yields right results. I even tried converting to another format, and QGIS still ignores inverse flattening. I'll check against another GIS, but still, am I missing something?

I see your point, it seems kind of crazy to translate the WGS84 ellpsoid to spherical axes (+a=6378137 +b=6378137) in the Proj4 string. But that's what you have to do if you use +proj=merc for your projection name. If you pair merc with ellipsoidal axes, like your library is doing, then the resulting Proj4 string will produce incorrect results. That's because Proj4's merc is not the same as "Popular Visualisation Pseudo-Mercator."
The form that GDAL produces is in common use, and it works. It's what you find on the EPSG website (https://epsg.io/3857).
There's another Proj.4 string for Web Mercator that is more correct-seeming, and it's what the Proj website currently gives you: (https://proj.org/en/9.4/operations/projections/webmerc.html). This form is
+proj=webmerc +datum=WGS84.  Here, webmerc is the equivalent of WKT's "Popular Visualisation Pseudo-Mercator." It's a more literal translation for the WKT string that you find in the EPSG database.
To sum up, there are two valid Proj4 strings for Web Mercator/EPSG:3857. One is closer to the WKT form, the other is in common use and is compatible with more software.
If you want to maintain compatibility with proj4js, I suggest that you treat EPSG:3857 as a special case and use the same string as GDAL. Or, you could switch to webmerc to give a more correct-seeming string, and lose backwards compatibility with software that hasn't implemented webmerc. I would vote for the first option.

Ah, I see, thank you! I have mappings of EPSG conversion codes to +proj parameters. I don't remember what my exact sources were, but it seems to work in most cases. For cases like yours, I'll just create exceptions.
Do you happen to know other such projections? I'd happily populate the list tomorrow :)

I've added an override which will set a sphere even if geokeys define an ellipsoid. While normally geokeys will override original CRS, I believe, we should make an exception for Web Mercator.
Please update to the 2024.04.13 release, it should be ready in 10 minutes.

Thanks for this update :) I'm not aware of other special cases relating to WKT <-> Proj4 translation, but I'll keep my eyes out for others.

Thank you for your help, appreciate the effort :) It warms my heart knowing there's less potential problems :D


Write documentation for binary message formats

Body
Besides JSON StreamPipes supports other, binary event serialization formats as mentioned in our documentation:

Events are serialized in JSON, although StreamPipes can be configured to use other (binary) serial formats.
https://streampipes.apache.org/docs/technicals-architecture/#data-model

Let's write some documentation for the advanced user audience that would like to make use of this feature. This should encompass which message formats are supported and how they are activated.
StreamPipes Committer
I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.

@bossenti I would like to work on this issue

@nitin-pandita I really appreciate your intention to contribute here!
However, this issue requires a good understanding of the inner working of StreamPipes and one would need to really delve in our codebase.
If you are not reluctant to do so, feel free to give it a try 🙂
But its definitely not beginner friendly

Close as not planned


Add content

You could also list the PaaS services that can be enabled using Arc.

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

ID: 6c0c36de-1d68-dad7-3218-d3e33fb8145b
Version Independent ID: 32a28486-8028-b727-c742-437f6505e720
Content: Azure Arc overview - Azure Arc
Content Source: articles/azure-arc/overview.md
Service: azure-arc
GitHub Login: @JnHs
Microsoft Alias: jenhayes

@sqlsolver Thanks for your comment! We will review and provide an update as appropriate.

Thank you @sqlsolver and apologies for the delay in responding. Are there particular PaaS scenarios you feel should be mentioned here?

Hi @sqlsolver, as I haven't heard back I'm going to close this issue, but we will keep this feedback in mind as we adjust the content. Thanks for taking the time to share your feedback and help us improve the docs.
#please-close


PD: support mixed tip racks

overview
As a PD user, I would like pipettes to take tips from appropriate tipracks.
behavior
With eg a p10 and a p300, pipette should use appropriate tips. Currently, PD tip selection will not differentiate between different tip rack sizes.
TBD

P10 uses 10uL tips; P1000 uses 1000uL tips -- but P300 can use 20uL, 100uL, 200uL, 300uL, etc. How does PD choose tips when multiple options would work (it's only P300 that's ambiguous, right)?

Exactly what tiprack sizes are supported?

See #1573


Move keyframe code out of selector context for Libsass compatibility

The keyframes used for the pulsate etc. animations are currently included inside of a selector context. Ruby Sass simply moves them outside on compile, but Libsass doesn't, resulting in invalid CSS. This splits up the @keyframes and animation parts of those mixins so that one can be used outside of selector context and the other inside, producing a valid build.

Great job, I hope this will be merged. :)

On a side note, this fix is only relevant until Libsass 3.2 is released, since that version will be fixed to be more clever about nested media queries. :)

Another note, if this change is pulled, then it would be nice to have a new version published on npm since that would mean it's compatible with Libsass and Webpack (since recently a variable was added to set a manual font directory, which Webpack requires to find the font files).

Thanks people, I'm sorry for being so slow: I don't have a real Internet connection until the next week 😱


#801

Regarding 801 @abdulhaq-e i checked the typescript version in node modules is 2.0 beta
even @gdi2290 i tried your suggestion but no luck.
i am not sure others are facing this.
Regards

HI I am using webstorm version 2016.2 and
when i am setting tsc compiler to node modules typescript it displaying me lots of error like following
Please help me here
<EMAIL_ADDRESS>Error:(21, 14) TS2300: Duplicate identifier 'PropertyKey'.
Error:(58, 5) TS2687: All declarations of 'name' must have identical modifiers.
Error:(118, 5) TS2403: Subsequent variable declarations must have the same type.  Variable '[Symbol.unscopables]' must be of type '{ copyWithin: boolean; entries: boolean; fill: boolean; find: boolean; findIndex: boolean; keys: ...', but here has type 'any'.
Error:(235, 5) TS2687: All declarations of 'flags' must have identical modifiers.
Error:(249, 5) TS2687: All declarations of 'EPSILON' must have identical modifiers.
Error:(284, 5) TS2687: All declarations of 'MAX_SAFE_INTEGER' must have identical modifiers.
Error:(291, 5) TS2687: All declarations of 'MIN_SAFE_INTEGER' must have identical modifiers.
Error:(430, 5) TS2403: Subsequent variable declarations must have the same type.  Variable '[Symbol.toStringTag]' must be of type '"Symbol"', but here has type 'string'.
Error:(430, 5) TS2687: All declarations of '[Symbol.toStringTag]' must have identical modifiers.
Error:(437, 5) TS2687: All declarations of 'prototype' must have identical modifiers.
Error:(465, 5) TS2687: All declarations of 'hasInstance' must have identical modifiers.
Error:(471, 5) TS2687: All declarations of 'isConcatSpreadable' must have identical modifiers.
Error:(477, 5) TS2687: All declarations of 'iterator' must have identical modifiers.
Error:(483, 5) TS2687: All declarations of 'match' must have identical modifiers.
Error:(489, 5) TS2687: All declarations of 'replace' must have identical modifiers.
Error:(495, 5) TS2687: All declarations of 'search' must have identical modifiers.
Error:(501, 5) TS2687: All declarations of 'species' must have identical modifiers.
Error:(507, 5) TS2687: All declarations of 'split' must have identical modifiers.
Error:(513, 5) TS2687: All declarations of 'toPrimitive' must have identical modifiers.
Error:(519, 5) TS2687: All declarations of 'toStringTag' must have identical modifiers.
Error:(525, 5) TS2687: All declarations of 'unscopables' must have identical modifiers.
Error:(582, 5) TS2403: Subsequent variable declarations must have the same type.  Variable '[Symbol.toStringTag]' must be of type '"Math"', but here has type 'string'.
Error:(582, 5) TS2687: All declarations of '[Symbol.toStringTag]' must have identical modifiers.
Error:(586, 5) TS2403: Subsequent variable declarations must have the same type.  Variable '[Symbol.toStringTag]' must be of type '"JSON"', but here has type 'string'.
Error:(586, 5) TS2687: All declarations of '[Symbol.toStringTag]' must have identical modifiers.
Error:(601, 5) TS2687: All declarations of 'size' must have identical modifiers.
Error:(607, 5) TS2687: All declarations of 'prototype' must have identical modifiers.
Error:(618, 5) TS2687: All declarations of 'size' must have identical modifiers.
Error:(624, 5) TS2687: All declarations of 'prototype' must have identical modifiers.
Error:(639, 5) TS2687: All declarations of 'prototype' must have identical modifiers.
Error:(653, 5) TS2687: All declarations of 'prototype' must have identical modifiers.
Error:(665, 5) TS2687: All declarations of 'value' must have identical modifiers.
Error:(777, 5) TS2687: All declarations of 'prototype' must have identical modifiers.
/Users/vitiwary/Documents/workSpaces/ise_scale_poc/ISE_SPOG_WP/node_modules/typescript/lib/lib.es2015.core.d.ts
Error:(17, 14) TS2300: Duplicate identifier 'PropertyKey'.

What about the global TypeScript binary?
Run tsc -v in a terminal.

@abdulhaq-e
thats also 2.0

https://github.com/AngularClass/angular2-webpack-starter/blob/master/tsconfig.json
see if this works. replace es6 with es5

@gdi2290 it solves the problem but can you please explain whats going on for my understanding.

core-js and es6 both are providing es6 type definitions and they're conflicting

@gdi2290 I don't thing tsconfig target pulls in typings, it's just for the compiler right? I'm not seeing this resolve the issue. Could something else be pulling type definitions? I keep running into these odd ball issues.

Was having the same issue, thanks for the solution... Nonetheless, could we update tsconfig.json accordingly since probably everyone is having/going to have the same problem?

I resolved my issue my adding es6 target in tsconfig, removing @types/core-js, and keeping core-js dependency.

I think this is resolved with ee0c85e1483b7f77ad728ab8c177d4370eb07250. But, you should not change the target from es5 to es6 as because of best browser support. See Compiler Options.

It is indeed resolved by removing core-js from the types array in tsconfig.json.
No need to resort to changing the compiler target to es6.

I have same issue,If I change target es5 to es6 I am getting these error in browser, My application is not loaded ,Please help me,


Running Android Container using LXD

Dear,
I am having a problem with Android Container on LXD.
I am deploying Android Container using LXD. I already deploy successfully Android Container using LXC and now i wanna move to LXD because LXD has Nova-LXD to integrated into OpenStack Platform.
Android Container needs more devices to start Android OS. When I used LXC, all devices from host were automatically mounted in /dev folder of container. However, when I deploy Android Container using LXD, Container cannot start because there was not enough mounted devices in /dev folder, only: cpuctl  fscklogs  pts  socket . Devices were not mounted automatically like LXC.
I would like to ask you how to solve this problem: devices are not automatically mounted in /dev folder?
The following pictures are from LXC and LXD:
LXC:

LXD:

What was your container's configuration under LXC (/var/lib/lxc/android/config)?
And what's the one generated by LXD? (/var/log/lxd/and1/lxc.conf)?

Hi stgraber,
This is LXC's configuration:

And this is LXD's configuration:

Looks like you should at least set "raw.lxc" to:
lxc.cgroup.devices.allow=
lxc.cgroup.devices.allow=a

Your pre-start script also won't run with LXD so that may be a problem since that may well be what sets up most of those devices for you.

I already set the configuration like you said however, it also did not start (cannot mounting devices from host to /dev folder of container).
The pre-start scripts in my LXC does not have more configurations, only mount the rootfs for the container.
I already allow all for cgroup devices, unconfined apparmor profile, set permission for seccomp but didnot work well.
Do you think the problem causing by setting permissions in source code LXD?

The other difference in config is that LXD sets "lxc.autodev=1" which has LXC setup a tmpfs on /dev, hiding any device node that may come with your rootfs.
You could try adding "lxc.autodev=0" in raw.lxc to undo that behavior.

I also set "lxc.autodev=0" but I still did  not work, devices were not automatically mounted in LXD container like using LXC.
"lxc.aa_allow_incomplete = 1
lxc.cgroup.devices.allow =
lxc.cgroup.devices.allow = a
lxc.aa_profile = unconfined
lxc.autodev=0"

So to be clear, there is no code in either LXC or LXD that creates those devices.
The devices you saw in your old LXC container were either a part of the rootfs on disk or were created by something inside the container, LXC didn't create them for you.
The LXD configuration you seem to be running with now should make sure that /dev is left alone (lxc.autodev=0) and that you can create whatever devices you want (lxc.cgroup.devices.allow=a).
It could be that your rootfs just doesn't have those device nodes, or whatever usually creates them in the container isn't running somehow or something in the container is over-mounting /dev and hiding the devices.

Basically, LXD written by Go language and based on liblxc to create container. I saw a project from you: go-lxc. Does LXD uses go-lxc to interact with liblxc?

yes it does


api call seems to return nothing

Hi, I copied the code below from the example page, it used to work but have stopped working recently, returning an empty list.
from pmaw import PushshiftAPI

api = PushshiftAPI()
comments = api.search_comments(subreddit="science", limit=1000)
comment_list = [comment for comment in comments]
comment_list

returns
[]
search_submissions also returns nothing....
Thank you so much.

I am seeing the same thing. Nothing returned.

Same here, nothing is being returned.
However, the Pushshift API itself is working

Same here, returning nothing despite the parameters being used

same

Same here;
Pushshift API is working, just pmaw wrapper does not.  An example with results from pushshift without any wrapper (and empty results from pmaw):
import pandas as pd
from pmaw import PushshiftAPI
import datetime as dt
import requests
import time

start_date = dt.date(2022, 12, 1)
end_date = dt.date(2022, 12, 15)

start_date = dt.datetime.fromordinal(start_date.toordinal())
end_date = dt.datetime.fromordinal(end_date.toordinal())

api = PushshiftAPI()

start_epoch = int(start_date.timestamp())
end_epoch = int(end_date.timestamp())

submissions = api.search_submissions(subreddit='politics', q='biden', after=start_epoch,
                                     before=end_epoch, num_workers=20)

sub_df = pd.DataFrame(submissions)
print('---------------------------------------------------------------')
print(f'pmaw df size: {sub_df.shape}')
print(sub_df.head())

time.sleep(10)
# Pushsift api directily
api_query = 'https://api.pushshift.io/reddit/submission/search/?q=' + 'biden' \
            + '&after=' + str(start_epoch) \
            + '&before=' + str(end_epoch) \
            + '&subreddit=' + 'politics' \
            + '&limit=' + str(100)

r = requests.get(api_query)
json = r.json()
df_pushshift = pd.DataFrame(json['data'])

print('---------------------------------------------------------------')
print(f'Pushshift direct df size: {df_pushshift.shape}')
print(df_pushshift.head())
print('---------------------------------------------------------------')

Results:
---------------------------------------------------------------
pmaw df size: (0, 0)
Empty DataFrame
Columns: []
Index: []
---------------------------------------------------------------
Pushshift direct df size: (100, 89)
  subreddit selftext  ... updated_utc     utc_datetime_str
0  politics           ...<PHONE_NUMBER>  2022-12-14 21:33:38
1  politics           ...<PHONE_NUMBER>  2022-12-14 21:23:28
2  politics           ...<PHONE_NUMBER>  2022-12-14 20:15:13
3  politics           ...<PHONE_NUMBER>  2022-12-14 20:07:17
4  politics           ...<PHONE_NUMBER>  2022-12-14 17:20:01

[5 rows x 89 columns]
---------------------------------------------------------------

I've added some changes to the code (see it here), using it two new parameters exist for calling Pushshift: sort_var='order' and check_totals=False.
Using these changes, it works with recent data only (older data cannot be queried even using Pushshift directly either yet).
 For some reason, implementing those makes PMAW very slow for responses. What used to be done in ~ 30 seconds, after these changes is taking 5+ minutes.

this will be fixed in v3.0.0 after #52 is merged + released

There's no working alternative version in the meantime?

I also encountered this issue.
Using "api.pushshift.io/reddit/submission/search/" directly is useful but it seems only work for very limited period of time (i.e., one month or so).
If I want to retrieve something earlier than a month, say, something in 12 months ago, calling this link (see below) in browser will only generate blank list:
link: https://api.pushshift.io/reddit/submission/search?q=&after=1633010400&before=1640236250&subreddit=science&limit=999
Specific return:
{"data":[],"error":null,"metadata":{"es":{"took":8,"timed_out":false,"_shards":{"total":4,"successful":4,"skipped":3,"failed":0},"hits":{"total":{"value":0,"relation":"eq"},"max_score":null}},"es_query":{"size":999,"query":{"bool":{"must":[{"bool":{"must":[{"range":{"created_utc":{"gte":1633010400000}}},{"range":{"created_utc":{"lt":1640236250000}}}]}},{"bool":{"should":[{"match":{"subreddit":"science"}}],"minimum_should_match":1}}]}},"aggs":{},"sort":{"created_utc":"desc"}},"es_query2":"{"size":999,"query":{"bool":{"must":[{"bool":{"must":[{"range":{"created_utc":{"gte":1633010400000}}},{"range":{"created_utc":{"lt":1640236250000}}}]}},{"bool":{"should":[{"match":{"subreddit":"science"}}],"minimum_should_match":1}}]}},"aggs":{},"sort":{"created_utc":"desc"}}"}}

Any idea why even the Pushshift API is not working for older data?

There's no working alternative version in the meantime?

Not right now. I'm hesitant to release a version that I havent fully tested, however, if everything goes well I will be able to release today 🙏🏾

I also encountered this issue.
Using "api.pushshift.io/reddit/submission/search/" directly is useful but it seems only work for very limited period of time (i.e., one month or so).
If I want to retrieve something earlier than a month, say, something in 12 months ago, calling this link (see below) in browser will only generate blank list:
link: https://api.pushshift.io/reddit/submission/search?q=&after=1633010400&before=1640236250&subreddit=science&limit=999
Specific return: {"data":[],"error":null,"metadata":{"es":{"took":8,"timed_out":false,"_shards":{"total":4,"successful":4,"skipped":3,"failed":0},"hits":{"total":{"value":0,"relation":"eq"},"max_score":null}},"es_query":{"size":999,"query":{"bool":{"must":[{"bool":{"must":[{"range":{"created_utc":{"gte":1633010400000}}},{"range":{"created_utc":{"lt":1640236250000}}}]}},{"bool":{"should":[{"match":{"subreddit":"science"}}],"minimum_should_match":1}}]}},"aggs":{},"sort":{"created_utc":"desc"}},"es_query2":"{"size":999,"query":{"bool":{"must":[{"bool":{"must":[{"range":{"created_utc":{"gte":1633010400000}}},{"range":{"created_utc":{"lt":1640236250000}}}]}},{"bool":{"should":[{"match":{"subreddit":"science"}}],"minimum_should_match":1}}]}},"aggs":{},"sort":{"created_utc":"desc"}}"}}

theres been some parameter changes: until is the new before and since is the new after
looking at the COLO switchover bug thread, it looks like some other people have had the 1 month of data issue

closing this as the COLO switch over fixes have been merged!

I am still getting the same issue in version 3.0.0 with this code:
api = PushshiftAPI(praw=reddit)
posts = api.search_submissions(subreddit="science", limit=10000)
post_list = [p for p in posts]
print(len(post_list))

The print call returns 0.


EnableImplicitTyping problem caused by issue #528

Hello,
sorry for late reply, I had some problems with reproducing this issue. This is a new problem caused by your fix for Issue 528.
Combining implicit and explicit types leads to deserialization problem. Please see the attached solution.
SerializerTestsWithoutNamespaces.zip
Thanks,
Jakub

Doh... thank you for reporting this @Trhac.  Can you post the code to a repository, by chance?  It is far more preferred to a zip file.

Actually @Trhac I was able to reproduce this simply by adding EnableImplicitTyping onto the test for #528.
Looking into this now.

Alright @Trhac please try the following build:
https://github.com/ExtendedXmlSerializer/home/pull/546#issuecomment-910338669
If everything looks OK to you I will send this out probably in the next day or so as this might be an impacting change that others will be running into with 3.7.3

Thanks Mike, your fix works great! So far no problems. Thank you.

Woohoo... OK I am going to send this out ASAP.  Thank you for verifying, @Trhac!


cannot compile on Fedora 34

qlite3-binding.c: In function ‘sqlite3SelectNew’:
sqlite3-binding.c:125322:10: warning: function may return address of local variable [-Wreturn-local-addr]
125322 |   return pNew;
|          ^~~~
sqlite3-binding.c:125282:10: note: declared here
125282 |   Select standin;
|          ^~~~~~~
github.com/joohoi/acme-dns
/usr/bin/ld: $WORK/b001/pkg1.a(_x011.o): undefined reference to symbol 'pthread_mutexattr_settype@@GLIBC_2.2.5'
/usr/bin/ld: /usr/lib64/libpthread.so.0: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
thanks

Fedora 32: first problem is fixed with
export CGO_CFLAGS="-Wno-return-local-addr"
the actual problem is sqlite3 (see similar problem https://github.com/mattn/go-sqlite3/issues/803)
I don't have the ld error


Raised the tolerance for a test in testAxisAngle2QuatAndBack (it failed on some systems before)

retest this please

retest this please


Relax bounds to build on latest lts-19

@thomasjm This is much appreciated, thank you!

No problem! I just rebased #74 on main as well


Not possible to install "Arduino UNO R4 Boards" from Library Manager

Hello everyone,
I face the following issue.
Trying to install the ""add-on" for arduino minima on IDE through the library manager from the service window i can see the message "CRC does not correspond. File is invalid. Could be a temporary problem, tray later" (i have translated from italian because of my ide is configured in such way but the meaning is that...).
Someone have a workaround action?
Because it seems something blocking and i cannot use my evaluation board otherwise...
Thanks for attention.
Waiting for answare as soon as possible.

Just installed the UNO R4 board package from the Arduino IDE (2.2.1).

Could not reproduce issue.
As a solution, you could either try later or use another network. See this comment: https://github.com/arduino/ArduinoCore-samd/issues/364#issuecomment-428777339

Hello @ingpd89, could you please provide the version of the core, version of the IDE, OS, steps to reproduce?


chore: run buf serially

Since googleapis module is large, running multiple buf commands in
parallel lead to file locks erroring out because of deadline exceeded.
Also buf generate on the proto files in the repository was done twice.

We can update to buf format here too!


Not supporting after gradle 8.3.0

Please check the library, it is not working in signed apk with gradle 8.3.0

its not working

@ahmed2146 / @RezaulHridoy99 could you please try again with the new version 1.1.1?


[SPARK-42599][CONNECT][INFRA] Introduce dev/connect-jvm-client-mima-check  instead of CompatibilitySuite

What changes were proposed in this pull request?
The main changes of this pr as follows:

Refactor CompatibilitySuite as a new tool CheckConnectJvmClientCompatibility and move it into tools module
Add a new shell script dev/connect-jvm-client-mima-check, it will use Checkc to check the mima compatibility of connect-jvm-client module.
Add dev/connect-jvm-client-mima-check to github task

Why are the changes needed?
For fix test error report in [VOTE] Release Apache Spark 3.4.0 (RC1) mail list.
Testing CompatibilitySuite with maven requires some pre-work:
build/mvn clean install -DskipTests -pl sql/core -am
build/mvn clean install -DskipTests -pl connector/connect/client/jvm -am

So if we run build/mvn package test to test whole project as before, CompatibilitySuite will failed as follows:
CompatibilitySuite:
- compatibility MiMa tests *** FAILED ***
  java.lang.AssertionError: assertion failed: Failed to find the jar inside folder: /home/bjorn/spark-3.4.0/connector/connect/client/jvm/target
  at scala.Predef$.assert(Predef.scala:223)
  at org.apache.spark.sql.connect.client.util.IntegrationTestUtils$.findJar(IntegrationTestUtils.scala:67)
  at org.apache.spark.sql.connect.client.CompatibilitySuite.clientJar$lzycompute(CompatibilitySuite.scala:57)
  at org.apache.spark.sql.connect.client.CompatibilitySuite.clientJar(CompatibilitySuite.scala:53)
  at org.apache.spark.sql.connect.client.CompatibilitySuite.$anonfun$new$1(CompatibilitySuite.scala:69)
  at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
  at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
  at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
  at org.scalatest.Transformer.apply(Transformer.scala:22)
  at org.scalatest.Transformer.apply(Transformer.scala:20)
  ...
- compatibility API tests: Dataset *** FAILED ***
  java.lang.AssertionError: assertion failed: Failed to find the jar inside folder: /home/bjorn/spark-3.4.0/connector/connect/client/jvm/target
  at scala.Predef$.assert(Predef.scala:223)
  at org.apache.spark.sql.connect.client.util.IntegrationTestUtils$.findJar(IntegrationTestUtils.scala:67)
  at org.apache.spark.sql.connect.client.CompatibilitySuite.clientJar$lzycompute(CompatibilitySuite.scala:57)
  at org.apache.spark.sql.connect.client.CompatibilitySuite.clientJar(CompatibilitySuite.scala:53)
  at org.apache.spark.sql.connect.client.CompatibilitySuite.$anonfun$new$7(CompatibilitySuite.scala:110)
  at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
  at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
  at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
  at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
  at org.scalatest.Transformer.apply(Transformer.scala:22)

So we need to fix this problem for developers.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GitHub Actions

cc @Yikun FYI

This pr often conflicts....

cc @hvanhovell too FYI

@LuciferYang can we close this one in favor of https://github.com/apache/spark/pull/40213?

@LuciferYang can we close this one in favor of #40213?

OK, let me close this one and focus on https://github.com/apache/spark/pull/40213


can't use r/all

Describe the bug
when i give a comment stream all as the subreddit it doesn't get anything, while if i do askreddit i'll get a lot of things
To Reproduce

use this code with a snoowrap client called client

const comments = new CommentStream(client, {
  subreddit: "all",
  limit: 10,
  pollTime: 2000,
});

run
it doesnt work
Expected behavior
It will get a bunch of posts from r/all

System Configuration:
Using TypeScript?
no
Node Version?
 node: '12.14.1',
Snoostorm Version?
^1.5.0
Snoowrap Version?
1.21.0
Additional context
I didn't do anything and it just stopped working? is this a reddit api thing?

Cannot replicate, make sure you are correctly authenticated and you have not exceeded your ratelimit.


Add Github style codeblock fencing

https://help.github.com/articles/github-flavored-markdown/#fenced-code-blocks
I think this would be a handy feature, but I understand if you don't want to poison the implementation with Markdown dialects.
I modified sub _DoCodeBlocks to do two passes. First it tries to find any fenced code blocks using code adapted from sub _DoCodeSpans, hashes them, then proceeds to perform the traditional codeblock check. I did not write any new tests, but it continues to pass existing ones.

I'm down with accepting this, but can you add a new test that tests this syntax?

btw - this PR fixes another issue - it would be great if it could be merged in and CPAN updated...
Here's some markdown that demonstrates the bug...

1. Line 1
1. Line 2
1. Line 3 with code block

   ```
   line 1
   line 2
   ```
1. Line 4 with code block

   ```
   a line

   a line after a blank line
   ```
1. Line 5

The bug renders the blocks as 'code' and fails to detect the block on line 4:
!
...with patch...

Mostly works, but it appears to be double-processing code inside the fences. I.e. # foo -->
foo
 --> <h1>comment</h1>.
Generates strange output given the following markdown:
```
# comment
```

Output:

<h1>comment</h1>

Expected:

# comment


feat: Support scalar function from_days and to_days

Issue Number: close https://github.com/pingcap/tiflash/issues/4678

[x] Unit test
[x] Integration test

Support scalar function `from_days` and `to_days`

/merge

/run-all-tests

/merge

/rebuild

/run-all-tests

/merge

/rebuild

/run-all-tests

/run-integration-test


wrapper for encounter resource to fix conflits between test and drug order

added a wrapper resource to method getEncountersForEncounterType of EncounterService to resolve classCastException in the entire application

 Resolve conflict between drug and test order in POC rest calls

Coverage remained the same at 59.673% when pulling 9211d395e7c387b5653859e03e9a7094613556be on Guimino:fix_conflits_between_drugs_and_test_orders into d7605df2ceac4e8fcc758fe7af286bed83dfbb2d on esaude:master.


Implement a GraphQubit type

Right now QubitLoc is  just a 2d point.  This is very reasonable for our hardware, but there are other qubit types that are very natural and which we should support (lines, staggered grids, general graph connectivities).
Proposal:
Abstract out the interface that describes adjacency, i.e. make an interface type HasAdjacency which requires the method is_adjacent.  (Right  constant two qubit gate assumes that the qubits implement this method).
New Qubit types
GridQubit
LineQubit
Also a way to go from an Adjacency graph to a set of GraphQubits which implement HasAdjacency and  which obey the adjacency relation of the graph.
This would mostly be relevant for defining a single / two qubit gates that respect adjacency, and also for device which use this adjacency in some of their constraints.

It seems more natural for adjacency and gate information to be part of the device rather than the qubit. Why not just give GraphDevice a graph attribute whose vertices can be generic QubitIds?

@bryano Is this related to all of your not-yet-merged pull requests?

Yea, specifically #1181

Can this be closed?


Navigation bar Closes #58

The branch has no conflicts now. Please review.

delete the previous repo. Clone this repo don't use custom css for it. default materialize css with blue text on hover with no bg shadow

delete the previous repo. Clone this repo don't use custom css for it. default materialize css with blue text on hover with no bg shadow

So no blue background box effect? Just have to change the color of text to blue by using blue-text?

I used blue-text class for blue color on active links and removed the background box color. I used as less custom css as possible.

make a new pr just add this logo to it nothing else


vim show more dirs or files error

One day ago, when I type vim /etc/  ,the same time I type tab button, the error  is showing,eg:
_arguments:450: _vim_files: function definition file not found
_arguments:450: _vim_files: function definition file not found
_arguments:450: _vim_files: function definition file not found

Sounds like an issue with your completion setup.
Try rm ~/.zcompdump* and restarting your session.
What do you get for the output of compaudit?

Thanks,But the iterm color is not work, I sad

Thank you very much,But rm this file, I need to install oh-my-zsh againt

You should not need to do that. When that zcompdump file is deleted, oh-my-zsh will regenerate it as part of its startup sequence. If that's not happening, something else is wrong, possibly the permissions on directories in your $FPATH.
What do you get for the output of compaudit?

Okay,but I havent to do it.The compaudit happend on commnd line  type  button

I'm sorry, I just don't understand what you're saying.
What language do you speak? Maybe another OMZ user can help out here.

sorry, I not good at english,ver sorry.I speak chinese, another, the problem is resolved.Tanks againt.

Ok, please close the issue then.

Ok,thanks

I had the exact same issue.
It looks like zsh sets the path of the compdump file as an environment variable ZSH_COMPDUMP. The ~/.zcompdump was also on my system which led to some confusion.
rm $ZSH_COMPDUMP \ exec zsh
This worked for me :+1: .


fix bug/duplicate-extra-url

closes #8116

@charliermarsh ,
please review it. I tested it locally and it met the requirements.


Meta fields are optional for create source and create measurement

Description
Meta fields are optional for create source, create tabular source, and create measurement
New dependencies: None
Fixes #102
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue -> bump patch)
[x] New feature (non-breaking change which adds functionality -> bump minor version)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected -> bump major version)
[ ] Documentation Update

Checklist

[ ] I have added tests that prove that my fix/feature works
[ ] Linters pass locally and I have followed PEP8 code style
[ ] New and existing tests pass locally
[ ] I have updated the documentation if needed
[ ] I have commented hard-to-understand areas in the code

Requirements

[ ] I have updated the MVG version

@tuix Probably we bump the major version here ?

@tuix Probably we bump the major version here ?

We keep the major version at 0 and bump the minor version


fix: metrics validator label to use address instead of pk struct formatting

Closes https://github.com/consensus-shipyard/ipc/issues/1190
I used address instead of the public key hex encoding. Can change that if wanted.

@LePremierHomme nit: the "closing" keyword is not supported by GitHub to link the issue, but "closes", "close", "closed" are. https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

We should make record_metrics() fallible by returning a Result<()>. Then we can avoid having packing code, and the higher level component would log errors in the error event type. @karlem could you drop a link to an example where we use that event type?

Not sure I understand the purpose of having it fallible. To propagate encoding errors?

Would add a TODO so we try to propagate the FVM address in the validator context.

The public key is what's used as the validator key for comparisons. I guess it would be better to just derive Address as a view, or fix it as an additional field in the context. It seems to be currently needed just for the metrics, so I could also just change CheckpointSigned to contain the address instead of the public key.

We should make record_metrics() fallible by returning a Result<()>. This way, we can avoid having packing code, and the higher-level component would log errors using the error event type. @karlem, could you provide a link to an example where we use this event type?
In general, I agree—failing to record a metric should not cause a panic that shuts down the whole node. Here's an example of how to emit a tracing error: https://github.com/consensus-shipyard/ipc/blob/409c1387ddf978a76c999bd8a19c7291dd094fd1/fendermint/vm/interpreter/src/fvm/exec.rs#L200.
However, given point 2:
Would add a TODO so we try to propagate the FVM address in the validator context.
I would suggest we include this change in the current PR. It’s a simple modification—see here: https://github.com/consensus-shipyard/ipc/blob/409c1387ddf978a76c999bd8a19c7291dd094fd1/fendermint/app/src/cmd/run.rs#L128.
By including the address in the event directly, we can skip the conversion altogether and eliminate the need to make record_metrics() fallible. At least for now!

@LePremierHomme , the address is already being converted in run.rs. I suggest including it in the ValidatorContext and then using it directly in the event.

SGTM!

Thank you, @karlem! 🙏


Backport assign to Stan Math

Summary
This backports (up-ports?) the assign functions from the Stan repo into this repo and refactors the assign() function to allow for better slice indexing
The scheme here is that for slicing like A[2:5, 1:10] Vector[1:10] we want to translate that directly into Eigen's block() or .segment()  functions. For functions that slice over rows and columns like A[, {1, 3, 8}] and A[1:N, :N] So that Eigen knows what columns it's slicing by first and then the slice of rows.
Tests
Tests were added for the new overloads and can be run with
./runTests.py ./test/unit/math/prim/fun/assign_test.cpp
./runTests.py ./test/unit/math/prim/ -f index
./runTests.py ./test/unit/math/prim/ -f rvalue

@t4c1 would you have time to help me add the assign() functions here to the expression testing framework? It's not clear to me how to add all the combinations of index types
Side Effects
This should have no side effects until we change the compiler to use the assign function in the stan::math namespace instead of the ones defined in the stan::model namespace
Release notes
Assign statements in Stan have better support for slice indexing
Checklist

[ ] Math issue #(issue number)

[x] Copyright holder: Steve Bronder
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

Assign is a bit different than other math functions. It does not return, it modifies one of the arguments and it accepts the weird index types. So it would be hard to modify expression tests to handle all that. I suggest writing expression tests for this function by hand (you might still want to use expression_test_helpers.hpp).
I would suggest putting all indexing related stuff into its own folder within fun. Also I just noticed assign and lvalue indexing look the same to me. What is the difference between the two?

I like the idea of moving this to Math. If we stay with the current repo structure, my opinion is that Stan should only be algorithms/services stuff, no utility
I am a bit scared how this will play with rstan and StanHeaders and all the CRAN related update issues. Rstan still has problems that occured when moving prim/mat/fun/Eigen.hpp. We might be able to do this once Rstan catches up, before that this could only live in Math as duplicated code from /stan. I dont want to cause more issues to Ben and rstan.

Hmm, if that is the case I would suggest leaving this in stan repo for now. I don't like duplicated code.

Cool just opened up a PR for this in the stan repo


Builder: use register to make the queue nicer

The main while loop in all the queue programs was a little inelegant: the combinational group that guarded the main while loop was preventing access to a key port within the loop.
This PR employs a register to avoid the issue of a combinational group. The resultant code is better in two ways:

It no longer needs a whole separate component just to raise a flag in case of i == 15.
In case the queue returns an err, the main loop correctly simulates a break immediately, instead of stumbling through the rest of the body and then getting broken by the main loop guard.

Closes #1633.

Awesome! The problem you're working around has been a pain point for a while now. The semantics of with operations are not very composable which makes them annoying to use. We should try to fix this issue soon so that it actually becomes a useful operator.


DOCS-11654-http-listener-kt

Rewriting HTTP Connector Listener source documentation

Closing as merged in https://github.com/mulesoft/docs-connectors/pull/1771


Some functions aren't found

A web app.
I want to take a requested an image file, put watermark on it on the fly via LuaJit and return an output image without creating an image file with a watermark. All via nginx.
I've faced with several "not found this functions" errors.
a part of my code:
  local vips = require("vips")
  local img = vips.Image.new_from_file("/path/to/image123.png", {access = "sequential"})
  local text = vips.Image.text("watermark123", {width = 200, dpi = 200, align = "centre", font = "sans bold"})

  -- NOTE 1
  text = text:rotate(-45)

  -- make the text transparent
  text = (text * 0.3):cast("uchar")

  -- NOTE 2
  text = text:gravity("centre", 200, 200)

  -- this block of pixels will be reused many times ... make a copy
  --text = text:copy_memory()

  text = text:replicate(1 + img:width() / text:width(), 1 + img:height() / text:height())
  text = text:crop(0, 0, img:width(), img:height())

  -- we make a constant colour image and attach the text mask as the alpha
  local overlay = text:new_from_image({255, 128, 128}):copy({interpretation = "srgb"})
  overlay = overlay:bandjoin(text)

  -- overlay the text
  img = img:composite(overlay, "over")

  --  buff = img:write_to_buffer(".jpg")
  buff = img:write_to_buffer(".png")

  ngx.print(buff)
  ngx.flush(true)

Errors:

    * VipsOperation: class "rotate" not found

    stack traceback:
    coroutine 0:
      [C]: in function 'error'
      /usr/local/share/lua/5.1/vips/voperation.lua:155: in function 'rotate'

    * VipsOperation: class "gravity" not found

    stack traceback:
    coroutine 0:
      [C]: in function 'error'
      /usr/local/share/lua/5.1/vips/voperation.lua:155: in function 'gravity'

      * lua entry thread aborted: runtime error: /usr/local/share/lua/5.1/vips/gvalue.lua:76: no such enum over
      lua-vips: no such enum type

      stack traceback:
      coroutine 0:
        [C]: in function 'error'
        /usr/local/share/lua/5.1/vips/gvalue.lua:76: in function 'to_enum'
        /usr/local/share/lua/5.1/vips/Image_methods.lua:555: in function 'composite'

What can cause them?

lua -v
Lua 5.1.5  Copyright (C) 1994-2012 Lua.org, PUC-Rio

luajit -v
LuaJIT 2.0.4 -- Copyright (C) 2005-2015 Mike Pall. http://luajit.org/

# or, obtained via nginx itself

LuaJIT 2.1.0-beta3

Ubuntu 18

I commented out the code with "rotate", then got "gravity" error. Then I commented out "gravity" and got the 3rd error.

vips -v
vips-8.2.2-Sat Jan 30 17:12:08 UTC 2016

My libvips turned out to be outdated

Hi, yes, lua-vips is a dynamic binding, so it presents the operations it find in your libvips at run-time.

Ok
In the documentation there's no mention of how to save to a buffer in the png format, only in the jpg. Is this a correct way
  buff = img:write_to_buffer(".png")
?

Hey Alex, yes, it should work.
That will search for a loader that has .png as a save suffix, then run that for you. You can also just call the PNG saver directly:
buff = img:pngsave_buffer()

Thx


Check that we only allow one action at present

Let's test to make sure that at present we prevent the API from allowing multiple actions to be added.
review/ @honkfestival @kmtaylor-github

Getting an odd sense of déjà vu...

Yeah, this was carved out of the other validation one; I'm trying to keep my PRs on topic.

👍


Integration m4j 1 0 0

I just migrated GenericTemplate ReceiptTemplate QuickReply and ReadReceipt for the 1.0.0 API.

Thank you Zoltan for your contribution!


how do applications buy bitcoin/cryptocurrency??

I just want to ask that, if i want to invest in bitcoin then i need to signup on an application like coindcx or coinbase. And then i can buy bitcoin from them by giving money, but from where do these applications buy bitcoin from and give us???

To know how new bitcoins are created please refer to this link: https://river.com/learn/who-creates-new-bitcoin/
Best regards, Cromewar.


[dashboard] Modal for editing dashboard properties & metadata

CATEGORY
Choose one

[ ] Bug Fix
[x] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY

Adds a new modal to the dashboard react app, which allows updating dashboard properties that are currently only updatable from the CRUD editor. This will enable phasing out the CRUD views in favor of a slick new UI.
When the form is submitted, the url also gets updated to reflect any new slug.
Could use some feedback on how I accomplished the dashboard title update, I had to add some new redux flows that work around the undo functionality so that it doesn't trigger a "save" button.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

Need to write some tests still, but I want to open this up to feedback.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[x] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
Not entirely sure. @graceguo-supercat seems active in this area?

Let's clarify the PR title (that will become the commit message on master once we squash & merge) https://chris.beams.io/posts/git-commit/

Oh yeah thanks I forgot to edit the default title 😁

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@cfc1e69). Click here to learn what that means.
The diff coverage is 14.28%.

@@            Coverage Diff            @@
##             master    #8876   +/-   ##
=========================================
  Coverage          ?   58.67%
=========================================
  Files             ?      362
  Lines             ?    11412
  Branches          ?     2800
=========================================
  Hits              ?     6696
  Misses            ?     4538
  Partials          ?      178

Impacted Files
Coverage Δ

...ssets/src/dashboard/containers/DashboardHeader.jsx
100% <ø> (ø)

...src/dashboard/components/HeaderActionsDropdown.jsx
69.56% <ø> (ø)

superset/assets/src/dashboard/reducers/index.js
100% <ø> (ø)

...uperset/assets/src/dashboard/components/Header.jsx
41.46% <0%> (ø)

...t/assets/src/dashboard/reducers/dashboardLayout.js
93% <0%> (ø)

...ssets/src/dashboard/components/PropertiesModal.jsx
7.4% <0%> (ø)

...rset/assets/src/dashboard/actions/dashboardInfo.js
33.33% <33.33%> (ø)

...et/assets/src/dashboard/actions/dashboardLayout.js
95.09% <33.33%> (ø)

...set/assets/src/dashboard/reducers/dashboardInfo.js
66.66% <66.66%> (ø)

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 cfc1e69...5bd8eff. Read the comment docs.

@dpgaspar Ok, I copied the description text from the MVC edit page.