Support for the is="" attribute

Subclassing native HTML Elements doesn't work as expected.
My guess is that elements need to be created using the overload document.createElement('button', {is: 'fancy-button'}) and special treatment is needed here to support the is="" attribute.
E.g.
// extends some different native constructor
class MyButton extends HTMLButtonElement {
  constructor () {
    super()
    this.textContent = 'Hey'
  }
}

// define it specifying what's extending
customElements.define('my-button', MyButton, { extends: 'button' })

let button = document.createElement('button', { is: 'my-button' })
button.textContent = 'My button!'
document.body.appendChild(button)

The above works in Chrome 55 but if the same element is created with the idom api, the constructor isn't invoked.
Has anyone else encountered this?

See https://github.com/google/incremental-dom/issues/297.

Thanks @jridgewell
Totally missed that in my search. I'll go ahead and close this then.


Configure Nextcloud LDAP lookup via CLI

https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/occ_command.html#apps-commands

https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/occ_command.html#ldap-commands-label

Closing as a duplicate of #8


I followed someone using this client and lost all my contacts

Hi,
This client promises but I followed someone using this client and then the list of people I was following was erased.

I am very sorry for that.
sometimes the following list didn't refresh and this is a known bug. I will try roll out a recover fix. before that, you can use other clients to recover your history following.

https://github.com/digi-monkey/flycat-web/pull/34

@bitcoinuser just push a simple fix for this. if 0 followings bugs happen again, flycat will ask you to confirm before submitting.
I also add a temp way to recovery the old followings, if you are sign-in, you will see a history followings in your contact page(click the Contact menu on leftSide to get there), you can click recovery to re-sign the old followings and broadcast to relays. Some relays are deleting the old-followings events, since flycat does not storing ANY data of users,  if you can't find any, we can only rely on relays so maybe just add more relays to try if anyone does have old following datas.

should not be happening after this patch. so I am closing it. if you have any problems feel free to reopen it


List of expected errors

Hi,
Is there a list of all the expected errors for upload/download/transfer?
Thanks!

Hi @Ilanak Please provide more info on what you're looking for? Is it the error codes for transfer or common failures encountered or other info? It'd be easier if you perhaps elaborate the usecase.


Installation causes 'Unknown OpenXR Runtime Error'

Installation causes 'Unknown OpenXR Runtime Error' in Open XR Tools, this doesn't seem to affect any VR functionality though:
XrResult failure (XR_ERROR_RUNTIME_FAILURE)
Origin: xrCreateInstance

As per instructions the files need to be installed in your program files dir due to the way WMR works.


Add dependency on slf4j-nop to silence warning

Fixes #4679
See https://ge.detekt.dev/s/lotfhvt2gspyq for a run without the SLF4J warning.

And this won't work :/ We might need to use the shadow plugin for the formatting jar.


The "sidebar" (and also the "sidebarSticky") area cannot keep on the right side

As the topic, the "sidebar" area and also the "sidebarSticky" area cannot keep on the right side (like the demo) but stay on the bottom of the page. Please fix this problem.
By the way, do you have a tutorial about how to install this template and the settings?

Thanks for the report. Please try following the template installation guide at https://bstrap.inputekno.com/2023/06/install-bstrap-template-blogger.html

So will you release the next version soon or you won't update this project?

Thanks for the report. Please try following the template installation guide at https://bstrap.inputekno.com/2023/06/install-bstrap-template-blogger.html

thanks for this template


Add Nuri Exchange

[### Entry type

New addition

App info
URL: https://www.nuri.exchange
Manifest.json URL: https://www.nuri.exchange/manifest.json
Name: Nuri Exchange
Description: Nuri is a next-generation AMM designed to serve as Scroll's central liquidity hub, combining the secure and battle-tested superiority of Uniswap v3 with a custom incentive engine, vote-lock governance model, and streamlined user experience.
Icon (PNG, 180x180):

It's minified via https://tinypng.com: yes
Homepage: https://www.nuri.exchange
Twitter: https://x.com/NuriExchange
GitHub: https://github.com/RamsesExchange
Discord: https://discord.gg/jhqz9RgdAs
App supports batching multiple transactions via Safe: yes
Supported networks
- Scroll

Revision checks

[x] Used smart contracts were audited.
[x] You have implemented the app using the Safe Apps SDK
[x] Your Safe App includes a manifest.json file at the root with the required data
[x] The app can be loaded as a custom Safe App in the Apps section of https://app.safe.global.
[x] The app auto-connects to the Safe as a wallet
[x] It doesn't try to connect to the browser wallet (e.g. MetaMask)
[x] You are able to trigger and execute one transaction with a Safe.
[x] RPC requests are optimized (not triggering many requests in a very short time period).

Audit document
https://code4rena.com/reports/2024-10-ramses-exchange#disclosures
Code for review
https://github.com/code-423n4/2024-10-ramses-exchange
Team information
Company: Kingdom
Official website: https://kingdom.one
Point of contact: 0xshad0w
Email/Telegram: @a0xshad0w

Application approved by the product team.
Note: Ramses, Nile, Pharaoh, Cleopatra and Nuri are effectively one application but branded differently for different chains for business reasons. They share the same codebase.

@0xShad0w Thank you for your submission! Could you please share the front-end repository link for review? The provided link appears to be just the audit results.


feat: hide_context fn

I want to explicitly hide or show context virtual texts, M.toggle_context() is not covering that case, as I can't provide the state I want it to be in.
Not sure whether this is enough, or whether I should also set opts.enabled in each fn, similar to what M.toggle_context() does, but instead in their respective methods.

Not sure whether this is enough

Let me know and we'll work something out :)

, or whether I should also set opts.enabled in each fn, similar to what M.toggle_context() does, but instead in their respective methods.

Alternatively, the toggle_context could take an optional argument to set the enabled state instead of flipping it like it does now.

Yeah I was thinking of just adding an arg. I'll double check with my configuration tomorrow and might open another PR :)
Thanks for the quick response <3


Add link to a live demo app with shinyapps.io

It could be fun/useful to give a live demo link with something like shinyapps.io. I have made at least one example of a shinyapps.io thing before and can try to help if interested!

Nice, this is a good idea!
Do you have the link for the one you've already made?

https://github.com/GMOD/jbrowse-components/pull/3732

examples are in readme now


Add test for AOD data

Inconsistencies between Cassandra data Simulation3HourlyAODOutput and the NetCDF files were found.

@babreu-ncsa, This seems like a familiar problem I've caused again. Would you help me try to provision the reversion of my recent change?
I was hoping to add the nbformat module to the gordon_2_0_0 kernel. This is so I can call Notebooks from other Notebooks. (I would be working from base Python if I had access to the cartopy module from there. The base kernel does have nbformat.) However, I can't check its compatibility with the modules I have now without trying to add it and then reinstalling the kernel, which is somewhat time consuming. Is there another way of installing a module for use on the C3 server? For example, maybe one could install a module through a terminal from the Jupyter directory, but I don't have admin privileges for that.

@JamesCarzon unfortunately there is not a direct way to install the package in the server, and debugging it when you add a package to the kernel is time-consuming if you go that route. There's a different approach, though. You can create a conda environment locally, in your machine, with the same Python version and the same packages versions that you have in your ActionRuntime that goes into c3. When you want to add a new package, you do a conda install locally, see what version of the package you get (conda will solve dependencies), and then check on the version that got installed, add that to the ActionRuntime, and then you know it will work.

From the error it seems like the manager nodes are busy... I think I have an action running that might be blocking it, I'll clean it up and re-trigger provisioning

It worked, so nbformat should be available now


[GenReflection] Emit associated type reflection metadata via extensions

Don't leave behind conformances gotten through extensions when
emitting associated type reflection metadata.

@swift-ci Please smoke test


Add DAP Strategy

This adds a dap strategy to the runner, letting you "debug test" from Neotest.
The ruby-dap adapter doesn't support directly debugging a sub-process - so we have to start the tests in a subprocess and run that subprocess "under" the debugger - then use DAP to connect to the debug server that neotest just started for us.

Thanks @stephenprater! 🚀


Treesitter support

I like this theme but It would be even better with Treesitter support.
Treesitter defines the following highlight groups (the color definitions are from Onedark).
hi! TSError        ctermfg=203 guifg=#f44747
hi! TSPunctDelimiter ctermfg=249 guifg=#abb2bf
hi! TSPunctBracket ctermfg=249 guifg=#abb2bf
hi! TSPunctSpecial ctermfg=249 guifg=#abb2bf
hi! TSConstant     ctermfg=75 guifg=#61afef
hi! TSConstBuiltin ctermfg=173 guifg=#d19a66
hi! TSConstMacro   ctermfg=73 guifg=#56b6c2
hi! TSStringRegex  ctermfg=114 guifg=#98c379
hi! TSString       ctermfg=114 guifg=#98c379
hi! TSStringEscape ctermfg=73 guifg=#56b6c2
hi! TSCharacter    ctermfg=114 guifg=#98c379
hi! TSNumber       ctermfg=173 guifg=#d19a66
hi! TSBoolean      ctermfg=173 guifg=#d19a66
hi! TSFloat        ctermfg=114 guifg=#98c379
hi! TSAnnotation   ctermfg=180 guifg=#e5c07b
hi! TSAttribute    ctermfg=73 guifg=#56b6c2
hi! TSNamespace    ctermfg=201 guifg=#ff00ff
hi! TSFuncBuiltin  ctermfg=75 guifg=#61afef
hi! TSFunction     ctermfg=75 guifg=#61afef
hi! TSFuncMacro    ctermfg=180 guifg=#e5c07b
hi! TSParameter    ctermfg=73 guifg=#56b6c2
hi! TSParameterReference ctermfg=73 guifg=#56b6c2
hi! TSMethod       ctermfg=75 guifg=#61afef
hi! TSField        ctermfg=168 guifg=#e06c75
hi! TSProperty     ctermfg=180 guifg=#e5c07b
hi! TSConstructor  ctermfg=73 guifg=#56b6c2
hi! TSConditional  ctermfg=175 guifg=#c586c0
hi! TSRepeat       ctermfg=175 guifg=#c586c0
hi! TSLabel        ctermfg=75 guifg=#61afef
hi! TSKeyword      ctermfg=175 guifg=#c586c0
hi! TSKeywordFunction ctermfg=175 guifg=#c586c0
hi! TSKeywordOperator ctermfg=175 guifg=#c586c0
hi! TSOperator     ctermfg=249 guifg=#abb2bf
hi! TSException    ctermfg=175 guifg=#c586c0
hi! TSType         ctermfg=75 guifg=#61afef
hi! TSTypeBuiltin  ctermfg=75 guifg=#61afef
hi! TSStructure    ctermfg=201 guifg=#ff00ff
hi! TSInclude      ctermfg=175 guifg=#c586c0
hi! TSVariable     ctermfg=73 guifg=#56b6c2
hi! TSVariableBuiltin ctermfg=180 guifg=#e5c07b
hi! TSText         ctermfg=226 guifg=#ffff00
hi! TSStrong       ctermfg=226 guifg=#ffff00
hi! TSEmphasis     ctermfg=226 guifg=#ffff00
hi! TSUnderline    ctermfg=226 guifg=#ffff00
hi! TSTitle        ctermfg=226 guifg=#ffff00
hi! TSLiteral      ctermfg=226 guifg=#ffff00
hi! TSURI          ctermfg=226 guifg=#ffff00
hi! TSTag          ctermfg=168 guifg=#e06c75
hi! TSTagDelimiter ctermfg=241 guifg=#5c6370

FYI: I added some settings and achieved this colorful code.
hi TSConditional guifg=#88c0d0
hi TSConstant guifg=#d8dee9 gui=bold
hi TSConstructor guifg=#ebcb8b gui=bold
hi TSException guifg=#88c0d0 gui=italic
hi TSKeyword guifg=#9a6590 gui=bold
hi TSMethod guifg=#ebcb8b
hi TSProperty guifg=#8fbcbb gui=italic
hi TSRepeat guifg=#88c0d0
hi TSTypeBuiltin guifg=#81a1c1 gui=bold
hi TSVariableBuiltin guifg=#d08770

are you sure that this is according to the Nord color scheme? seems like this orange/ yellow is not from nord

Yes. This is #ebcb8b - nord13.

This theme is super cool, but with treesitter is not as good, leaves us 2 choices, stop using treesitter in order tu use this scheme, or don't use the scheme, which is not cool since treesitter is super fast even on very large files.

How could I use this in my settings to work properly? I really like nord but with treesitter feels very plain imo.

How could I use this in my settings to work properly? I really like nord but with treesitter feels very plain imo

Checkout this plugin https://github.com/ChristianChiarulli/nvcode-color-schemes.vim , it has several colorschemes with support for treesitter (nord is among them).

@luisiacc many thanks!

@luisiacc @mrswats  i have tried  this one but it doesn’t have airline support and some colors were  strange, so I merged official  nord and this for treesitter, and I have those 2 files (colors its folder with colorschemes and airline contains nord and badwolf airline theme, you can delete badwolf)
colors.zip
airline.zip

@s-u-d-o-e-r Thank you for that. Could you open a PR upstream?

its hand made merge and I know almost nothing about themes syntax, so it would be good if someone else will review and clean those files and then make PR

@s-u-d-o-e-r I wish I had the time!

I am happy to provide a PR if someone can give me some pointers!

I am happy to provide a PR if someone can give me some pointers!

Sure thing. Clone the repository (it will appear under your own github), make the changes and commit then, then go to the upstream and do a PR. It might be good to open an issue first with a screen shot before and after -- I would add the after in the PR. I know there are some unit test framework for vim but I never used them… And it does not look like nvcode-color-schemes.vim uses them.
Does that help?

@kierun I know how to create a PR for an OSS project on github. I meant it in a more technical sense, would committing these two files as @s-u-d-o-e-r sent them in the appropriate locations would be enough?

@mrswats Ah, my apologies for misunderstanding.
I would start with just replacing them and see what happens.

Opened PR :) Feel free to continue the technical discussion over there!

Hi to all participants in this issue :wave:, and thanks @s-u-d-o-e-r for your contribution :+1:
I know that the main development origin for tree-sitter was to be used as new parser for Atom back then, but when most of the users switched to the more stable and advanced Visual Studio Code (and Microsoft bought GitHub) I thought that Atom (and tree-sitter) was going to be sunset sooner or later. Nice to see that it was decoupled from Atom and developed actively.
Anyway, adding support for the [nvim-treesitter][] plugin should not be a problem, even when it is only available for Neovim. My only concern, albeit a small one, is that sooner or later there might be a collision of highlighting group names. The TS prefix of the nvim-treesitter plugin could also be used by another plugin that is targeted for TypeScript. Would have been better if they'd choose TreeSitter instead.

This project is a tree-sitter implementation of Nord. It might not be compatible with Nord as-is but might be of interest.

Hi, thanks for linking my port!
I've tried to stay to Nord and followed the directions in the readme in terms of syntax groups. All colors used in the port are part of the 16 colors present in the nord theme, except for the cursor line color which is taken from the vscode version.
The main changes I made were yellow (nord13) instead of Snow White (Nord 4) for constants, and light blue (Nord 7) instead of Snow White (Nord 4) for function names, as I feel it gives a little more pop to the theme. The biggest difference is my theme is made in lua, which means it isn't backwards compatible with Nord-vim. Ideally I wanted to submit it as a separate Nord port for Neovim, but if tree sitter is integrated into the main repository it's somewhat unnecessary.
You can find my issue/request to create a neovim theme here: https://github.com/arcticicestudio/nord/issues/157, since work is being done on this branch, I can close it if needed.
The benefits of having neovim have its own theme are:

You can work on neovim-specfic features without cluttering up the vim port (e.g. lualine / nvim-tree support)
The Nord.nvim theme loads much quicker since its in lua (about 2 for the nvim vs 6 ms for the vim port on average for me)

On the other hand, the main drawback would be having to maintain two themes instead of just one, and the nord theme has quite a backlog of work already.
If you want a slightly more color-accurate theme, then https://github.com/kunzaatko/nord.nvim might interest you as well

Support has been implemented and merged in #253 🎉
⚠ Note that this is the first iteration and it is very likely that there will be inconsistencies compared to the current highlighting when using "normal" Vim plugins per language. Please report any problem you find so that the support for tree-sitter can be improved continuously!


[BUG] : Icon cannot visible in Dark mode fixed

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #2153
Description
[Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.]

Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
Before
Screencast from 2024-06-26 07-53-27.webm
After
Screencast from 2024-06-26 08-01-19.webm
Checklist:

[x] I have made this change from my own.
[ ] I have taken help from some online resources.
[ ] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers and screenshots after making the changes.

@huamanraj please add the level label because I'm gssoc contributor.


fix: allow sender verkey to be null in iOS when packing with anoncrypt

Does Android already allow null to be passed?

There's been no issues with Android that @JamesKEbert and I have observed.


Use inquirer instead of prompt-for

Fixes #61.
I removed test from scripts because it seemed redundant. Will fix it if I'm wrong.

@yyx990803 any feedback for the PR? I started it because #61 has help wanted label.

Sorry, the issues are a bit misleading. The two issues actually need to be worked on together. khaos-forked is using prompt-for-forked under the hood, in a rewrite we would get rid of both and directly use metalsmith + inquirer.

Thanks, I'll see what I can do.

Closing in favor of #67.


Typo "**Select～branch **page"→"Select～branch page"

https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/merge-folders-files?view=azure-devops

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks.

Looks good; thanks.


It crashes in Alpine Linux 3.13 and 3.14

Alpine Linux is very used in Docker containers because it is very lightweight.
The result is that it always crashes with Java 11:
SIGSEGV (0xb) at pc=0x000000000000b8a6
  com.luciad.imageio.webp.WebP.decode(J[BII[IZ)[I+0
  com.luciad.imageio.webp.WebP.decode(Lcom/luciad/imageio/webp/WebPDecoderOptions;[BII[I)[I+64
  com.luciad.imageio.webp.WebPReader.read(ILjavax/imageio/ImageReadParam;)Ljava/awt/image/BufferedImage;+53
  javax.imageio.ImageIO.read(Ljavax/imageio/stream/ImageInputStream;)Ljava/awt/image/BufferedImage;+55<EMAIL_ADDRESS>  javax.imageio.ImageIO.read(Ljava/io/InputStream;)Ljava/awt/image/BufferedImage;+34<EMAIL_ADDRESS>
Probably it is due to the fact that Alpine uses muslib and the native libray uses glibc.
How can I recompile the native library for Alpine?

In the docker of openjdk:8-alpine ,i meet this  error also,how did you solve this problem


Possible to unpipe highland.js streams?

Hi,
Just curious, is it possible to .unpipe a highland.js stream? If yes, how should I do it? Thanks.
For example..
h().unpipe(stream)
I have two different streams, and I want to unpipe the writable from the readable stream without affecting the other streams still piped to the readable streams..

There is no unpipe method. You should transform the Highland stream into a node stream (by piping to PassThrough if you want to use node stream features that Highland doesn't provide.
// You may need to specify objectMode and/or highWaterMark depending on your use case.
var stream = h(...).pipe(new PassThrough());
stream.pipe(....);

// Later on.
stream.unpipe(...);


URL in description and README broken

The URL in the repository description and README are pointing to GH-DEV-WS-0503's copy of the game instead of yours.
Please fix both, so they point to your copy of the game at https://GH-DEV-WS-0503.github.io/github-games-oshkoshcwpence.

README.md has been updated per the lab.


[cmd] PUSH - view progress on remote peers

Show remote progress bars when connected to peers.
We could start this as a basic dat push that runs until all peers are updated, then exits.

This issue was moved to datproject/dat#648


Keys support for ssh deployer and exec runners

Because there are no password in remote hosts sometimes.
Because it's simpler to authorize key on remote host once, than write password in many build steps.
Selectable auth method, like in VCS configuration, is very useful.

Bitbucket: https://bitbucket.org/nskvortsov/deployer/issue/2
Originally reported by: Fedor Gogolev
Originally created at: 2012-11-21T20:39:39.932

Implemented in this build

Original comment by: Nikita Skvortsov


Allow passing private key to configure method

In our use case, we want to avoid file system access. Therefore, we need a way to pass the private key to the configure method instead of reading it from the file system.
This pull request handles that.

Hello
Quickly reviewing the PR, I am trying to rephrase the requirement just to be sure.
You want to pass the private key as a variable, not through a file read method. Is that correct ?
That is an interesting use-case, I would like to keep future versions of the library backward compatible and the PR doesn't seem to do that. (just a quick review)
I'll look how I can do that from your suggestion.
So this will come but probably not this way.

You want to pass the private key as a variable, not through a file read method. Is that correct ?

Yes, exactly.

That is an interesting use-case, I would like to keep future versions of the library backward compatible and the PR doesn't seem to do that. (just a quick review)

Unless I missed something, everything should be backward-compatible. The configure method takes an additional (optional!) parameter. If not provided everything should work as usual.

My bad @omgMath
I looked at it more seriously today and you just cleaned the code (thanks!) and added the proxy method get_private_key_from_config
I review it and tested and looks great !
This will come this week as pypi release (0.1.7), I'll add some stuff in the doc so people know that this option exist.(I didn't document the configure method yet).
Any twitter account I can give credit to for this release ?

This will come this week as pypi release (0.1.7), I'll add some stuff in the doc so people know that this option exist.(I didn't document the configure method yet).

The configure method is already documented here, which is also extended with this pull request.
Thank you! Looking forward to the new version :+1:

I even forgot I wrote that part :D
What I meant is that, I will also include reference to it on the get-started page.

What I meant is that, I will also include reference to it on the get-started page.

Sounds good!

Any twitter account I can give credit to for this release ?

Sorry, forgot to answer that question. But I don't have twitter account anyway. :smile:
No need to give me credit, it was just a very very small contribution...

There are no small contribution ;)
Especially when you already created it for yourself.
Sharing and making it available to everyone is always appreciated.


More rounded corners in VS Code please!

I believe that there are various places where rounded corners can be implemented, like buttons, drop-down buttons and hovers.

Related to #144962

/duplicate of #140072 which is linked to #115641


docs: First InferenceService instructions with port-forwarding

Adds a small section to the Getting Started > First InferenceService docs on how to curl against a locally running port-forwarded server.

@nimishamehta5 The preview is not rendering the page. Can you check if it is rendering for you in your local machine ?

@sivanantha321 I think that's a different issue unrelated to my change, I reported this in https://github.com/kserve/website/issues/411 and it was fixed, but my branch is not rebased on to the main one

/lgtm
/approve


On-the-fly parallelized+refactored SALSA and SALSA-Lite

Hi there,
Me again. I reimplemented the SALSA and SALSA-Lite features to work on-the-fly with any number of microphones. I wanted to share it with you and the community with the hope it will help advance the field. The implementation can be found in this gist (I'm happy to make a PR if appropriate):
https://gist.github.com/andres-fr/d923e1df7de4dd6e0af34b28a2a7ef04
It should be just plug&play (docstrings contain usage examples), and depends only on numpy and librosa. I'd love some feedback! I did some sandbox tests and results were identical (up to eigenvector +/- sign), but no rigorous utests. Data looks fine though, here is an example from the DCASE 2021 SEDL dataset with the default parameters (wav file fold1_room1_mix001.wav):
LogMel excerpt

SALSA excerpt

SALSA-Lite excerpt

Note that a main visual difference is due to the fact that SALSA has the noise floor + coherence filters, which remove a lot of clutter (for readers: the SALSA-Lite paper kind of shows that these are not really needed).
The parallelized SALSA version yielded a decent speedup that could make it particularly useful for data augmentation techniques that are applied on the waveform. Also (hopefully) the refactoring helps coming up with further exciting variations of SALSA. For the record I like salsa brava.
Cheers!
Andres

Thank you, Andres. Computing the frequency bins in parallel is very useful!

Thanks a lot!
One side note, I am not sure what is the role of the sign invariance of the eigendecomposition. I mean, if we decompose the spatial covariance matrix M (Hermitian) as follows:
M = U * Lambda * U.T

Then we can clearly see that multiplying U by -1 yields the exact same M. This has the effect of adding 180 degrees to the phase. Numerically, it seems that the solutions are consistent (I just saw very few discrepancies with my implementation) but I wonder if this could be introducing some noise or overhead into the network.

Hi @andres-fr, many thanks for working on this and so sorry for the very late reply (both of us have been very very busy lately).
I will discuss more with @thomeou about the sign issue, but a neural network should be robust enough to this kind of noise.
Please feel free to create PR and I will take a look at it. Thank you!

Hi @karnwatcharasupat thanks for getting back.
Taking a closer look at it, integrating this particular enhancement into the repo would require some substantial changes, for 2 main reasons:

I did a pretty good amount of refactoring. My gist does not depend on any of the repo's code, and this was intended:

The script is this way stand-alone
I refactored things like the heuristic SalsaNoiseFloorTracker to make the code more understandable
Refactored the SALSA computations to make them vectorized
General OOP, DRY, on-the-fly changes

The repo is not designed to run on-the-fly computations: it makes a very good job at making the results of the paper reproducible, but this is done so in a batched manner.

Therefore, I think that properly integrating the gist into the repo would require refactoring the repo itself to match the building blocks from the gist, and to make it realtime-ready by basically creating a pipeline and possibly a pip python package with __main__.py functionality.
On the other hand, we can just "add" the gist as a stand-alone script into the repo root and update the README accordingly. This is arguably a much cleaner solution, and way less effort. What do you think?
Cheers and thanks again!
Andres

I like your solution as well. In the future we will probably have to do a major housekeeping to convert the repo into a more package-like style as more people are using it. At the moment, I think you can create a PR (so you are shown as contributor as well), and add the gist into the repo. I think we could put it in a subfolder /contrib/<your contrib name>/ for now, until I have time to better integrate and test it with the main code.
Thanks a lot!

@andres-fr I just gave you access to my old on-the-fly SALSA code for PyTorch. Please feel free to use code snippets from there as well.


Promote Web Actions from Experimental

Promote api/v1/experimental/web to api/v1/web
Allow CORS header to be set from Web Actions in v1/web
Make extensions optional defaulting to .http
Added .svg extension
Inline body when it is not JSON
Includes raw-http annotation support allowing Web Actions to receive query parameters and raw body content in api/v1/web
Prevent invocation of an action multiple times from one request
Display proper error when accept header type does not match actual return type

Closes: https://github.com/openwhisk/openwhisk/issues/1947
Closes: https://github.com/openwhisk/openwhisk/issues/1886
Related: https://github.com/openwhisk/openwhisk/issues/1965

PG2 1218, PG4 59.

PG4 50 approved.

PG1 1262, PG4 60.

@markusthoemmes @cbickel do either of you have bandwidth to review these changes?

will /api/v1/experimental routes continue to work? we have apps that depend on this, and will need some grace period to port over to the non-experimental route

@starpit, the experimental route will remain intact for now.

PG4 65, approved.


Interactive Diagnostics

Problem
JS and TS diagnostic messages can get quite large, especially when dealing with frameworks like Vue or react.   The TS team has worked to significantly improve and shorten diagnostic messages, including replacing complex type information with ..., however there are still cases where you need to see the full type information. Right now, we have to staticly choose to expand the additional information or not. They would like the user to be able to interactively expand types within a diagnostic
In addition, the overall diagnostic experience could be improved. Two areas identified talking with the TS team:

Syntax coloring of inline code in diagnostics
Go to definition in diagnostics

Refs
#11847
Desired User Experience
Consider a diagnostic message  T<...>. We would like the ... to be something like a  link. Clicking it would expand the diagnostic message to T<Array<...>>, which itself contains another expandable link
Requirements
The main focus is on being able dynamically to expand sections of a diagnostic. We need new VS Code API support for this and then will need languages to adopt this API. However, I think the other two features should be considered while designing the new diagnostics API as they are likely something we would like to support and will influence overall api design
For expansion, we want to be able to:

Mark arbitrary spans within a diagnostics as expandable
Lazily compute these expansions, i.e. don't resolve the expansions ahead of time
Allow expansions to contain other expansions
Show a progress indicator of some kind while an expansion is being resolved

Many of these features also make sense for quick info hovers

DiagnosticPart Api sketch
This api sketch proposes making diagnostic messages a list of parts. Parts would be joined together to form the message rendered in the editor:
interface TextDiagnosticPart {
    readonly type: 'text';

    /**
     * Text rendered in the editor
     */
    readonly text: string;
}

interface ExpansionDiagnosticPart {
    readonly type: 'expansion';

    /**
     * Contents rendered for the expansion, such as the text `...`
     */
    readonly contents: ReaonlyArray<DiagnosticPart>;

    /**
     * Lazily resolves the diagnostics.
     *
     * The could also be implemented using a provider or commands.
     */
    expand(): Thenable<ReaonlyArray<DiagnosticPart>>;
}

type DiagnosticPart = TextDiagnosticPart | ExpansionDiagnosticPart;

The diagnostic type would then become:
export class Diagnostic {
    ...

    message: string | ReadonlyArray<DiagnosticPart>;

     ...
}

Extensions
The idea of diagnostic parts could be easily extended to clickable links and code:
interface ClickableDiagnosticPart {
    readonly type: 'clickable';

    /**
     * Contents rendered in the diagnostics
     */
    readonly contents: ReaonlyArray<DiagnosticPart>;

    /**
     * Command executed on click
     */
    readonly command: Command
}

interface CodeDiagnosticPart {
    readonly type: 'code';

    /**
     * Language to use for syntax highlighting
     */
    readonly language: string

    /**
     * Code rendered in the editor
     */
    readonly text: string
}

/cc @sandy081, @jrieken, @dbaeumer, @DanielRosenwasser, @weswigham, @amcasey

FYI @minestarks

Probably worth noting that for the syntax highlighting bit, it's very possible that syntax highlighted and linked/expanded ranges overlap; so them being mutually exclusive parts would seem to prevent that.

@weswigham Good point. I've updated CodeDiagnosticPart to potentially handle nesting better. One difficult thing about colorization is that the snippets may not actually be valid code. T<...> for example would colorize T as a variable.other.constant instead of as a type if we reused the js/ts grammar.
In the TS / editor sync today, we also discussed a proposal that would allow specific spans to marked specially, something like:
interface DiagnosticMessage {
    /**
     * Text rendered in the editor
     */
    readonly text: string;

    /**
     * Ranges within the text that can be expanded.
     */
    readonly expandableRanges?: Range[];

    /**
     * Ranges within the text that should be rendered as code
     */
    readonly codeRanges?: { range: Range, language: string } [];
}

Keeping the range correct on expansions could get tricky

Is this inventing our own markup language? How about using markdown as proposed by @mjbvz here:
https://github.com/Microsoft/vscode/issues/54272

Rendered markdown could be used to implement hyperlinks (though you'd need to ensure file urls with locations work fine in markdown link tags) and if you're lucky syntax highlighting (although what's keeping the editor highlighting and the markdown highlighting consistent?) but I don't think it covers the expandable lazy ranges (the original request) - unless that markdown support goes all the way to full blown html/js support.

It's might also worth noting that for the syntax highlighting part, we'd likely be trying to colorize things in specific contexts, so in addition to the standard markdown language selector, you'd also need to be able to somehow specify a specific tmLanguage rule to start in (instead of the root rule - this way our types get syntax highlighted as types and not statements). So in that regard, getting pre-classified spans (a la quickinfo) back from the language service might be easier than messing with picking apart tmLanguage rulesets; but I'm not the most familiar with them, so I'm not sure.

unless that markdown support goes all the way to full blown html/js support.

Yeah, good point... We could experiment with commands. We already support command-links and we could have a special command that replaces the link text...

you'd also need to be able to somehow specify a specific tmLanguage rule to start in (instead of the root rule - this way our types get syntax highlighted

The markdown rendering picks up any language that's registered (by extensions). So it would require some special code-chunk-language so that MD will use the grammar that came with that language.
Stepping back a bit: The idea is to keep of all this in the editor hover, right? So make that smarter and a bit more interactive? I am asking because the hover is easy to dismiss and maybe not the best place for a UX in which the user invests time configuring its state.

My 2 cents, I would not have asynchronosity in error message which might not have good UX especially in Hovers. Why does this needs to be async first of all Is it expensive to compute complete message?
Also not a big fan of having UI semantics. My first step would be to use MD string. BTW, Is not the related information can be used to show more information? I think we do not restrict this to be used only for multi-diagnostics but also for adding more information.

Why does this needs to be async first of all Is it expensive to compute complete message?

It can be, yes. Our typesystem has the ability to generate new types by mapping old ones, so you can get very complex or large (anonymous) types with a very short sequence of type operators. And when those appear in errors, well... Things can get difficult to grok very quickly since there's simply too much to print - today we're forced to truncate the output, but making it explorable just like how dotting off the object can reveal more info would go a long way toward making it easier to work with.

My 2 cents, I would not have asynchronosity in error message which might not have good UX especially in Hovers.

Ignoring hover over red squiggles for a moment, errors still appear in the problems window and the f8 error bar as well, both of which are much more persistent. I'd think persisting the hover text as it is updated is an extension of those two.

BTW, Is not the related information can be used to show more information?

Nope - in this case the lazy querying is key to making it work. It allows us to gradually expose/generate the shape of complex types as requested, and only the parts requested. We actually have the ability to construct infinitely deep anonymous types - today we cut these off after printing one level of the type with a ..., but being able to expand these to an arbitrary depth as needed would be very nice. We do use related info where we can - it just doesn't help in complex type display/type truncation cases. (And secondarily would be a gratuitious way to "linkify" all the references in the types in an error, TBH - very nonlocal)

Stepping back a bit: The idea is to keep of all this in the editor hover, right? So make that smarter and a bit more interactive? I am asking because the hover is easy to dismiss and maybe not the best place for a UX in which the user invests time configuring its state.

What I was hoping was that diagnostic state was synchronized between the problems window/the f8 error bars/hover strings between full refreshes. That way you can expand within the hover if you want (then go back to it and still see it expanded), but also explore in the other places errors are displayed. In our meeting, someone mentioned that eclipse has the ability to copy things like individual diagnostics (plus stack traces and more) into a project context pane to allow them to persist and be inspected, which could work, too, but is maybe less continuous an experience than just being able to interact with a diagnostic anywhere you see it.

adding @misolori - call for diagnostics UX ideas

Here's the most minimal API for this we could have on the vscode side:

Make Diagnostic::message a markdown string

In the diagnostic messages, allow hyperlinks of the form:
some text [...](command:editor.expandDiagnostic?_typescript.resolveDiagnostic,123) and more text

The editor.expandDiagnostic command is a special VS Code command that delegates out to another command to handle the actual expansion. In this case, it would invoke the _typescript.resolveDiagnostic command with the diagnostic object and the expansion id 123

_typescript.resolveDiagnostic would return a promise to a MarkdownString. VS Code would then replace the original editor.expandDiagnostic link with the rendered string

A few things with this approach:

This would let you use other markdown features like bolds and italics.
Can we improve this so we don't need the command indirection?
Commands don't have good cancellation semantics
This is pretty VS Code specific. TypeScript would still likely want a diagnostic structure api closer to the one I originally proposed.
This approach doesn't address inline syntax highlighting. That's not possible to do in markdown as far as I know

_typescript.resolveDiagnostic would return a promise to a MarkdownString. VS Code would then replace the original editor.expandDiagnostic link with the rendered string

In case TypeScript already knows the omitted text behind [...] it could just add it as argument, [...](command:md.expand?FOO). That would prevent extra commands and round trips.

This would let you use other markdown features like bolds and italics.

Yes. My POV is that it's just like Hover and editor decorations and I believe people can build cool things with it, see GitLens. Sure, there is a risk of folks turning us into a Christmas tree but then I don't use such an extension. We can also consider disabling certain markdown features, e.g. tables or images, in certain places.

This is pretty VS Code specific. TypeScript would still likely want a diagnostic structure api closer to the one I originally proposed.

Haha - better VS Code specific extension API than TypeScript specific extension API. Honestly, the proposal smells very TypeScript-tailored and we should first circle in other languages with complex error messages, maybe rust-lang or lean.

Please allow these to be expanded somehow. It has become VERY frustrating working with types now in typescript. I'm wasting so much time trying to get everything to work with the different intellisense features, and not being able to copy and paste complete types, or even read them properly has become VERY frustrating and time consuming. PLEASE PLEASE PLEASE add SOME way (even just a command) to show the full type without any abbreviations.
One problem is that I don't even know which type is being repeated or if more than one is being repeated. A type variable layout would be more clear.
I'm used to hacking other peoples code, so I am perfectly capable of building an extension or changing the source code, I just don't want to have to do that with everything I use. Why can't the tools just do what they're supposed to do and get out of the way?

I see at the top that this can be staticly chosen, but I have no idea how to do that. Is it a setting?

Just checking in on this. Is there any update to this, or any way to get rid of the ellipses and see the full type of a variable in VS Code?

This is a really annoying issue; honestly there is never a time when I don't want to see the whole thing. Optimize for readability? How is it readable to only see a small part of the relevant information?
Would really really like to see this become a setting that was easy to tweak :-( it would save me a lot of time right now with what I'm working on

Problem solved!
noErrorTruncation: true
At some point someone pointed out the TypeScript tsconfig.json setting compilerOptions.noErrorTruncation. This in fact seems to solve the problem.

@Arlen22 It doesn't work.

// from https://developer.twitter.com/en/docs/tweets/data-dictionary/overview/intro-to-tweet-json
let foo = {
  "text": "My added comments to this Tweet ---> https:\/\/t.co\/LinkToTweet",
  "user": {
    "screen_name": "TweetQuoter"
  },
  "quoted_status": {
    "text": "original message",
    "user": {
      "screen_name": "OriginalTweeter"
    },
    "place": {
    },
    "entities": {
    },
    "extended_entities": {
    }
  },
  "place": {
  },
    "entities": {
      "hashtags": [

      ],
      "urls": [
        {
          "url": "https://t.co/W1FqVrsjQk",
          "expanded_url": "https://twittercommunity.com/t/rt-with-comment-aka-quote-tweets-now-may-have-media-attached-across-twitter-apis/125539",
          "display_url": "twittercommunity.com/t/rt-with-comm…",
          "unwound": {
            "url": "https://twittercommunity.com/t/rt-with-comment-aka-quote-tweets-now-may-have-media-attached-across-twitter-apis/125539",
            "status": 200,
            "title": "RT with comment, aka Quote Tweets, now may have media attached across Twitter APIs",
            "description": "Today we’re announcing a new feature that allows userspeople on Twitter to add a GIF, video, or photo to their Retweet with comments, aka Quote Tweets. Developers will start to see additional media metadata included in the payload for Quote Tweets. Quote Tweets with media will be rendered very similarly to Tweets with media across our APIs. This rendering is an addition to the existing media field, so this should not be a breaking change for application owners, if they are already ingesting med..."
          },
          "indices": [
            162,
            185
          ]
        },
        {
          "url": "https://t.co/lXs26mCkIl",
          "expanded_url": "https://twitter.com/TwitterSupport/status/1125479034513645569",
          "display_url": "twitter.com/TwitterSupport…",
          "indices": [
            186,
            209
          ]
        }
      ],
      "user_mentions": [

      ],
      "symbols": [

      ],
      "media": [
        {
          "id":<PHONE_NUMBER>532657153,
          "id_str": "1125490782532657153",
          "indices": [
            210,
            233
          ],
          "media_url": "http://pbs.twimg.com/tweet_video_thumb/D56L51LV4AEEC8-.jpg",
          "media_url_https": "https://pbs.twimg.com/tweet_video_thumb/D56L51LV4AEEC8-.jpg",
          "url": "https://t.co/T9MBCHZWcD",
          "display_url": "pic.twitter.com/T9MBCHZWcD",
          "expanded_url": "https://twitter.com/TwitterDev/status/1125490788736032770/photo/1",
          "type": "animated_gif",
          "video_info": {
            "aspect_ratio": [
              101,
              165
            ],
            "variants": [
              {
                "bitrate": 0,
                "content_type": "video/mp4",
                "url": "https://video.twimg.com/tweet_video/D56L51LV4AEEC8-.mp4"
              }
            ]
          },
          "sizes": {
            "thumb": {
              "w": 150,
              "h": 150,
              "resize": "crop"
            },
            "small": {
              "w": 202,
              "h": 330,
              "resize": "fit"
            },
            "large": {
              "w": 202,
              "h": 330,
              "resize": "fit"
            },
            "medium": {
              "w": 202,
              "h": 330,
              "resize": "fit"
            }
          }
        }
      ]
    },
    "extended_entities": {
      "media": [
        {
          "id":<PHONE_NUMBER>532657153,
          "id_str": "1125490782532657153",
          "indices": [
            210,
            233
          ],
          "media_url": "http://pbs.twimg.com/tweet_video_thumb/D56L51LV4AEEC8-.jpg",
          "media_url_https": "https://pbs.twimg.com/tweet_video_thumb/D56L51LV4AEEC8-.jpg",
          "url": "https://t.co/T9MBCHZWcD",
          "display_url": "pic.twitter.com/T9MBCHZWcD",
          "expanded_url": "https://twitter.com/TwitterDev/status/1125490788736032770/photo/1",
          "type": "animated_gif",
          "video_info": {
            "aspect_ratio": [
              101,
              165
            ],
            "variants": [
              {
                "bitrate": 0,
                "content_type": "video/mp4",
                "url": "https://video.twimg.com/tweet_video/D56L51LV4AEEC8-.mp4"
              }
            ]
          },
          "sizes": {
            "thumb": {
              "w": 150,
              "h": 150,
              "resize": "crop"
            },
            "small": {
              "w": 202,
              "h": 330,
              "resize": "fit"
            },
            "large": {
              "w": 202,
              "h": 330,
              "resize": "fit"
            },
            "medium": {
              "w": 202,
              "h": 330,
              "resize": "fit"
            }
          }
        }
      ]
    }
  };

The bug to track is this: https://github.com/microsoft/TypeScript/issues/26238

I am also looking for a way to access "computed types" I've posted on StackOverflow about it here. It would be nice to have better tooling / understanding about what a type is, and I'd personally like a CLI tool that could give me a glimpse, rather then trying to get VSCode to show everything in a tooltip on hover.

same issue + 1

Somewhat related is my recently-closed-as-out-of-scope suggestion of being able to cmd-click on types in the tooltip to dig into those types (like you can in Eclipse).  That request is also about having "links" within the tooltip.

I found https://github.com/intellij-rust/intellij-rust/pull/4217 through https://github.com/microsoft/vscode/issues/16221#issuecomment-518658249 and it seems to be doing almost the same thing (it expands all the way with just 1 click). I would imagine it being similar to that except having the option to advance 1 step at a time?

What I'm doing meanwhile is to use simplify from type fest to wrap big types
It successfully expands the type on VSCode and I can freely scroll it.

am also look a way to get something like on hover

instead of this

can we prioritize this, we eagerly need this feature to expand all the complex types in our codebase.
i'm currently doing https://github.com/Microsoft/TypeScript/issues/26238#issuecomment-672086446, but that's undesired because sometimes i don't want to expand the full type.

I'd just like to +1 that this feature would be much appreciated.

@weswigham @jrieken any news on this issue?

We have been waiting for any solution for 5 years now, let us know are you considering it? This problem is really annoying and limiting us

Related: #94679 and #35601.
Related on Stack Overflow:

How can I make VS Code show full TypeScript type definitions on mouse hover?
Is there a way to access typings of a prop in VS Code without having to check the types files?

Right now it's like hanging a steak in front of a canine; as a dev seeing the inferred type in the tooltip and knowing VS Code can expose the complete type yet not being able to copy or extract it in any way... This would be the most effective feature to help us avoid having to manually setup up types from a JSON payload or code-gen'ing our types, especially for those that are combinations of other types.

It would be nice if we can click on the ellipses or more then we can see some more.

This is actually not a VSCode problem but a TypeScript problem.
Proof:

Create a very long type that displays ... 15 more ... when you hover it
Deliberately mis-assign it, for example const foo: VeryLongType = {} missing required properties or something like that
Run npx tsc

You'll see even in your terminal TypeScript collapses the type and outputs ... 15 more ....
But I would also like to see this fixed, because I often need to copy some complex computed types from one project to another, and this would save me a lot of chore work.

Long term solution by @extremegf
in vscode

Using Ctrl+P, Go to node_modules/typescript/lib/tsserver.js
Find line var defaultMaximumTruncationLength = 160
Change it to 1000 or value of your choosing.
Open Ctrl+Shift+P menu, select TypeScript: Select TypeScript Version...
Ensure it's set to Use Workspace Version
Full restart VSCode - reloading workspace is not enough.
Verify that ... abbreviations are gone from type hints.

PS.
cause noErrorTruncation in tsconfig didn't work for me.
and changing tsserver.js of VScode's typescript is anoying every VSCode update
Before:
with ...

After:
You can also drag the bottom border

Have written a quick patcher that I run using yarn like so:
yarn patch-ts
Add the following to scripts in package.json:
  "patch-ts": "./scripts/patch-ts.sh",

Add the following to scripts/patch-ts.sh (and remember to run chmod +x ./scripts/patch-ts.sh
#!/bin/bash

FROM="var defaultMaximumTruncationLength = 160;"
TO="var defaultMaximumTruncationLength = 1e6;"

sed -i -e "s/$FROM/$TO/g" "node_modules/typescript/lib/typescript.js"

echo "Annotation Truncation Length patched successfully"

Long term solution by @extremegf
in vscode
1. Using Ctrl+P, Go to `node_modules/typescript/lib/tsserver.js`

2. Find line `var defaultMaximumTruncationLength = 160`

3. Change it to `1000` or value of your choosing.

4. Open Ctrl+Shift+P menu, select TypeScript: Select TypeScript Version...

5. Ensure it's set to Use Workspace Version

6. Full restart VSCode - reloading workspace is not enough.

7. Verify that ... abbreviations are gone from type hints.

PS.
* cause `noErrorTruncation` in tsconfig didn't work for me.

* and changing tsserver.js of VScode's typescript is anoying every VSCode update

* the extension mentioned in other solution is no copy-pasteable

Before: with ...
After: You can also drag the bottom border

Since TypeScript 5.6 this is now located in node_modules/typescript/lib/typescript.js


Cluster upgrade orchestration - cli implementation

Description
Changes proposed in this pull request:

implementing cluster upgrade command in kcp cli

Related issue(s)

https://github.tools.sap/kyma/backlog/issues/1165

job failed, this needs to be merged first: https://github.com/kyma-project/control-plane/pull/679

Make sure to generate docs via make docs


vm name with punycode international characters fails while migration

Description of problem
This is extended version of BZ1588555, I tried to migrate vm with vmname ytale-v2v-ubuntu-nfs-punycode-джум-ññ and it failed to migrate.

Version-Release
master.20180625230012_9b5c751
How reproducible
100%
Steps to Reproduce

Try to migrate vm with punycode characters in their name
(Infra mapping was normal, for datastores I used nfs at source and nfs at target, I don't think it is matter of datastore)

Actual results
Error while migrating vm
Expected results
VM name with punycode characters should also be get migrated
Internal reference
https://bugzilla.redhat.com/show_bug.cgi?id=1596143

I don't know that this is a UI issue. Are you experiencing issues w/ the migration itself? What is the expected behavior @bthurber ?

FYI @priley86 there was UI issue for it before https://bugzilla.redhat.com/show_bug.cgi?id=1588555

@priley86 investigating.....logs indicate it may on the virt-v2v or RHV side.  Will advise.

Closing this (not a UI issue) - noted as RHEV issue.


Feature/UI template

Problem
What is the problem this work solves, including
#237
Solution
Load the templates from the simulariumio package. This renders the form and submits the values, but I am not yet unpacking those values, so it will have no effect on the trajectory you view.
Type of change
Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

Change summary:

Tidy, well formulated commit message
Another great commit message
Something else I/we did

Steps to Verify:

Start the test app
Click the "load smoldyn" button
Select the example_3D.txt from the simulariumio test data
Leave the form blank, click submit

Screenshots (optional):
Show-n-tell images/animations here

@toloudis @blairlyons this is ready to be looked over, ie, see if we like both this and the template schema setup

This looks like a great start. Couple high level comments:

I'm not sure why exactly it should be implemented in here rather than in the website repo.  It seems that this repo shouldn't have any responsibilities for showing these forms.
It would be nice to do a verbal walkthrough of the main logic for rendering
I wonder if things would be simpler if the "compound" built in types were just their own components too, rather than forcing them to build on the other primitives

This looks like a great start. Couple high level comments:

I'm not sure why exactly it should be implemented in here rather than in the website repo.  It seems that this repo shouldn't have any responsibilities for showing these forms.

this is a prototype to see if we could get everything hooked up without having to mess with the main repo until we feel good about it.

It would be nice to do a verbal walkthrough of the main logic for rendering
I wonder if things would be simpler if the "compound" built in types were just their own components too, rather than forcing them to build on the other primitives

[ ] Add file input as one of the switch options
[ ] Add more typings
[ ] Make list extendable


Grey Theme seems jacked up

What's up with the grey theme?

How did you get this result? I don't see it when I set any of the grey schemes in settings. Was it through onboarding?

Onboarding.


Problem with name resolution when container is up and down periodically

Following #84 issue.
There is also such issue with short leaving (or periodically leaving dying containers). My use case is that I use docker for development and dev containers for project may often go up and down.
When containers is up dnsdock adds its name to DNS table, and when it is down it removes it. The problem occurs when I try to access container (by dns name, usually inside the browser) at the moment when container being down (some times it happens - I either may forget to start it, or it is just starting but not yet). In this case dnsdock forwards request to external server and may return response from forwared request - which will contain some external IP or responses that DNS record for name is not found .
In this case if dns client got a response that there is no dns record found even if containers is up now, I still will not be able not access it because dns client will not try to resolve it any more. The same problem with returned external IP (it will try to resolve only after TTL of external response). To make dns client make request again I need to flush client's dsn cache.
TTL setting may be a save for some cases, but only if containers IP is not changing, because if it is we have the same issue as with external IP, need to way for TTL before next request.
So I see possible solution as following: for certain dns request if not found in table dnsdock should response with timeout, so that client would have to make requests until it resolves it, maybe there is some more sensible solution.

Hi
I've fixed this issue by adidng new flags called --forcettl --all
--all will force dnsdock to process stopped containers so while your containers restarts DNS requests won't be forwarded to external servers.
--forcettl will force the TTL for forwarded response so your client can flush the cache with a ttl=0 even if the response is comihg from an external server..

Ok thanks will see how it will work out.

Ok thanks will see how it will work out. Have you published it on docker hub? There is last version v1.16.1-amd64 (6 days ago)?

it is on the develop branch you can build it to test it. I'll release it officially a little bit later

Ok, can not build it on windows as rocker gives some errors there, so waiting for release.

@aacebedo how is it going?

@aacebedo This problem supposed to be solved in dev branch?

@aacebedo it seems that this problem persists in recently published v1.16.3, is it supposed to be fixed? Maybe reopen the issue?


Support for RS256

The JWT Java library at https://github.com/auth0/java-jwt/blob/master/src/main/java/com/auth0/jwt/JWTVerifier.java currently does not support RS256.
It should be updated in order to support this.
The issue was raised at ticket 6605

@mpaktiti - thanks for raising this issue. Support is now provided.


Attempt to register extension class '...', which appears to already be registered

Godot version
v4.3.stable.official [77dcf97d8]
Plugin version
4.1 (v1.0.8)
System information
Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4070 Ti (NVIDIA; <IP_ADDRESS>14) - AMD Ryzen 9 7950X 16-Core Processor (32 Threads)
Issue description
Debugger yields the following errors after extracting godot-extension-4.1-webrtc.zip to project root as described in release instructions (https://github.com/godotengine/webrtc-native/releases/tag/1.0.8-stable)
E 0:00:01:0038   _register_extension_class_internal: Attempt to register extension class 'WebRTCLibDataChannel', which appears to be already registered.
<C++ Error>    Condition "ClassDB::class_exists(class_name)" is true.
<C++ Source>   core/extension/gdextension.cpp:463 @ _register_extension_class_internal()
E 0:00:01:0038   _register_extension_class_internal: Attempt to register extension class 'WebRTCLibPeerConnection', which appears to be already registered.
<C++ Error>    Condition "ClassDB::class_exists(class_name)" is true.
<C++ Source>   core/extension/gdextension.cpp:463 @ _register_extension_class_internal()
Steps to reproduce
I have not been able to reproduce this yet. When I created a brand new project I did not receive this error.
This happened with an existing project I tried to install this on.
Minimal reproduction project
No response

Welp, I'm dense I guess. Somehow I actually copied the folder in there twice. So yeah it was already registered because I had two copies in there 👯♂


Feature/message composer attachment icon

Changed the Attachment Icon;
I also upgraded the build tool; hopefully the project is ready to increase that. :)

Hello @waleoyediran
Thank you so much for your pr. I don't think we want to change the resource file yet.


Update User Agent to fix issues

Apparently twitter whitelisted several older browsers for the new layout, I changed the user agent to the one that works now, Yes, I have tested it, and it works on my machine, tell me if it doesn't in yours though.

@ZusorCode Please check and merge this PR.


make wallet work with cabal v2 commands and nix-shell

Issue Number

Overview

[ ] I have ...

Comments

It is already possible to use cabal new-build within a nix-shell - instructions on the wiki Building page.
We also have a Buildkite CI job to check that Cabal works this way.
In any case, any PR which adds a dependency list to cabal.project needs to include a mechanism to automatically keep that in sync with stack.yaml. Otherwise it will break within a short time.

@disassembler Is this PR still needed since the Cabal build now works for you? I added the --enable-tests --enable-benchmarks options to the Building instructions.


Use testcontainers to test ocp_resources, add more test - 2232

[Auto generated]
Number: [#2232]

openshift-python-wrapper[pull_request][531b7110-bae1-11ef-985b-a8f41517a54c][PR 2232]: Closing issue for PR: Use testcontainers to test ocp_resources, add more test.
PR was closed.


Introduce GraphQL Interceptors

Description:
The requirement is to have something similar to the HTTP interceptors [1] for GraphQL. The advantage of having this is that the business logic can be completely abstracted out to the resolver level while having the common stuff like authentication, authorization, logging, observability, etc. in the middleware level.
A similar use case can be found at GraphQL official website [2].
A popular library can be found at npm [3].
This requirement is initiated with GraphQL security story completion [4].
[1] https://github.com/ballerina-platform/module-ballerina-http/blob/master/docs/proposals/interceptors.md
[2] https://graphql.org/graphql-js/authentication-and-express-middleware/
[3] https://www.npmjs.com/package/graphql-middleware
[4] https://github.com/ballerina-platform/ballerina-standard-library/issues/1771#issuecomment-932129846

Tasks:

[ ] Research
[ ] Proposal


Nit: Change description passed to the scheduler on the "Change based scheduler"

The reactive_schedule description has a description of "Based on time" but it is actually based on file changes.

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

ID: c0873373-90d0-b221-35be-8e243425cdbe
Version Independent ID: 1c5bfc26-b81e-4883-4913-cb9b378b3785
Content: Schedule Azure Machine Learning pipelines - Azure Machine Learning
Content Source: articles/machine-learning/how-to-schedule-pipelines.md
Service: machine-learning
Sub-service: core
GitHub Login: @lobrien
Microsoft Alias: laobri

@sfilipi we will review your feedback and get back to you shortly. Thanks.

@sfilipi seems you're referring to recurring_schedule.

@sfilipi's edit should stand. There are two schedules, one based on time (recurring_schedule), and one based on file changes (reactive_schedule). I mistakenly used the same time-based description in the creation of reactive_schedule. @sfilipi corrected the mistake.


[QST] Is there a CLI command to record GPU time for all iterations?

There are tags for "nv/cold/time/gpu/stdev/relative" and "nv/cold/time/gpu/mean", but is there a way to record all iterations in the json output?
This is an option  to record all data in pytest-benchmark.

The --jsonbin output writes out binary files will all measurement data.
This needs better documentation (filed #122 to track), but we do have an example script that shows how to parse these outputs: https://github.com/NVIDIA/nvbench/blob/main/scripts/nvbench_histogram.py


Support for directories

Currently if you open the same directory twice with subl ., Sublime will a duplicate window.
Is it possible to prevent that?

I've created a package which implements this functionality. Let me know if you have interest in merging both packages, since the functionality is similar in concept and they complement each other.
https://github.com/aristidesfl/sublime-prevent-duplicate-windows


No more map rendering when zoom enough to propose region download

May be disturbing for users to see something like a map and request a download.
Note that clicking elsewhere does not hide download prompt, can be seen as a feature to help the end-user understand or as a bug as if no Internet connection then hides the rough data already have access to.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. For example:
I'm always frustrated when [...]
Describe the ideal solution
A clear and concise description of what you want to see in Organic Maps.
Describe alternatives you have considered

How do you solve this issue now with Organic Maps or other apps?
Attach any examples, screenshots, or screen recordings from other apps that help us to better understand the idea.

Additional context
Add any other context or screenshots about the feature request here.


added the bellman ford algorithm in python

Signed-off-by: Rakteem Mullick<EMAIL_ADDRESS>Fixes issue:

issue ->  #396
Changes:
added the bellmanford.py file in dynamicprogramming.kadane_algo folder.

Create a folder called graph_algorithms here Create a subfolder of bellman ford in that folder and add your code there.
and remove your changes in the game_projects folder
Kindly refrain from making redundant changes.

okk , I will change it

Create a folder called graph_algorithms here Create a subfolder of bellman ford in that folder and add your code there.
and remove your changes in the game_projects folder
Kindly refrain from making redundant changes.

can you please help me how can i change the 'redundant changes'. @Princeton21

Create a folder called graph_algorithms here Create a subfolder of bellman ford in that folder and add your code there.
and remove your changes in the game_projects folder
Kindly refrain from making redundant changes.

can you please help me how can i change the 'redundant changes'. @Princeton21

Nevermind that, but don't do it next time

Create a folder called graph_algorithms here Create a subfolder of bellman ford in that folder and add your code there.
and remove your changes in the game_projects folder
Kindly refrain from making redundant changes.

can you please help me how can i change the 'redundant changes'. @Princeton21

Nevermind that, but don't do it next time

okk sir

@Princeton21 sir, I have commited changes. I think this will do.

@Princeton21 sir, I relocated the files as per your instructions.


YAML Config for Downloadable Assets

Fixes #1107, or at least gets us prepared for it, but also related to #1215.
Happy to get some initial feedback. The territories tab is not part of the initial version, but this PR already writes the downloadable CSV completely driven by the YAML config file.

Tests will probably fail because... pickles....

@lucasmbrown-usds ready for a new review. I added the tests back as well as the new fields Emma incorporated.


Search filters - Phase 2

What's the Problem?
Phase 1 of the search filters is nearing completion.
I am creating this issue to discuss parsing.
Here is the actual plan.
Phase 1: Picker for date and size and groups.
Phase 2: Parsing for date and size.
Phase 3: Picker + Parsing for kind
Phase 4: Others filters.
Solution/Idea
The detailed content of phase 2

Add a badge on the filter menu button, when there is at least one.
Suggestion on the parsing keys.
Syntax and validation while typing.

When a filter is parsed, it is deleted from the search box, and added to the menu.
The badge allows you to have a visual.
The same filter can have several syntaxes.
modified:01/01/2020, date:>2020, after:2020 are equivalent.
Alternatives
To discuss.
Priorities
No response
Files Version
No response
Windows Version
No response
Comments
Here the actual state

Another milestone this could further be improved would be filter by metadata, maybe coping some syntax form exiftool, for example: -exif:fnumber>5.6

@xdanielc Could you develop your idea? I do not understand.

I would like to search file/folders by attributes, now I'm using Everything for this.

Merging with #4813


Control not showing in custom section (widget)

Issue description:
When I add control into custom section like widgets . It was not showing and i see in the browser code  have inline style
element {
    display: none;
}

Version used:
development version
Using theme_mods or options?
theme_mods
Code to reproduce the issue (config + field(s))
jQuery(document).ready(function() {
	/* Move  widgets */

	wp.customize.section( 'sidebar-widgets-sidebar_frontpage' ).panel( 'theme_options' );
	wp.customize.section( 'sidebar-widgets-sidebar_frontpage' ).priority( '5' );

});

Kirki::add_field( 'advance', array(
    'type'        => 'toggle',
    'settings'    => 'advance_header_checkbox',
    'label'       => esc_attr__( 'Disable Transparent Header ', 'advance' ),
    'section'     => 'sidebar-widgets-sidebar_frontpage',
    'default'     => '1',
    'priority'    => 10,
) );

Hello any suggestion on this issue ?

to be honest I still don't understand what you're trying to do...

Ok i try to explain again
register widgets area into my theme :
```
register_sidebar(array(
'name'          => __('Contact Section ', 'promote-pro'),
'id'            => 'sidebar-contact',
'before_widget' => '',
'after_widget'  => '',
'before_title'  => '',
'after_title'   => ''
));

Add a section into customizer for this widgets area or move widgets  area into this section

if ( ! empty( $our_client_section ) ) {
$our_client_section->panel = 'theme_options';
$our_client_section->title   = __( 'Client section', 'promote-pro' );
$our_client_section->priority = 8;
}
$contact_section = $wp_customize->get_section( 'sidebar-widgets-sidebar-contact' );
if ( ! empty( $contact_section ) ) {
$contact_section->panel = 'theme_options';
$contact_section->title   = __( 'Contact section', 'promote-pro' );
$contact_section->priority = 8;
}

Now I am trying add some kirki fields into this section

Kirki::add_field( 'promote-pro', array(
'type'        => 'checkbox',
'settings'    => 'promote_contactfixed_image',
'label'       => __( 'Disable parallax effect', 'promote-pro' ),
'section'     => 'sidebar-widgets-sidebar-contact',
'default'     => '1',
'priority'    => 10,
		) );

But kirki fields are not showing in this section or if you try to add any kirki fields into customize core section like background color or header it also not working

Kikir fields auto add `display:none` inline code for those fields

Thank you

Does this work if you use the default WordPress API to add fields instead of using Kirki?
I'm not sure WordPress Core allows adding custom controls in widget sections...
When using simple fields like checkboxes, Kirki acts as a simple proxy between your code and the WP-Core API.
To see if this is an issue with Kirki or if this is something that WP simply doesn't currently allow like this, try replacing this code:
Kirki::add_field( 'promote-pro', array(
	'type'        => 'checkbox',
	'settings'    => 'promote_contactfixed_image',
	'label'       => __( 'Disable parallax effect', 'promote-pro' ),
	'section'     => 'sidebar-widgets-sidebar-contact',
	'default'     => '1',
	'priority'    => 10,
) );

with this:
add_action( 'customize_register', function( $wp_customize ) {

	// Register the settings
	$wp_customize->add_setting( 'promote_contactfixed_image', array(
		'default'        => 1,
		'type'           => 'theme_mod',
		'capability'     => 'edit_theme_options',
	) );

	// Add the controls
	$wp_customize->add_control( 'my_setting', array(
		'label'       => __( 'Disable parallax effect', 'promote-pro' ),
		'section'     => 'sidebar-widgets-sidebar-contact',
		'settings'    => 'promote_contactfixed_image',
		'type'        => 'checkbox',
		'priority'    => 10,
    ) );
} );

Ohh !! it is not working if i using default customize API . You can close it
By the way can you please tell me how i can use cropped_image ? and how can i control cropped_image size ?
Thanks

Kirki doesn't include a cropped_image control so if you use it, Kirki will simply act as a  proxy and your arguments will be passed-on to the WordPress API. For an example of what arguments that control accepts you can see https://make.wordpress.org/core/2015/07/16/new-customizer-media-controls-in-4-3-and-4-2/


Fix regression #6864 caused by #6613

Should fix the issue. Calling remove should delete all matching tweens but internally it stops on first match so should work with delayed tweens as before.

You're right @bojidar-bg. I think exposing two almost the same methods to the user has little sense and is not elegant. I've just added additional default param to remove() method.
It's not consistent with three other but now it should work exactly as in 2.1 and will also enable user to remove tweens in packs.
Also updated documentation.
I think I will try find more elegant solution for 3.0.
Is there a way to bind method but not expose it to the user?

@pkowal1982 Well, starting it with _ wouldn't expose it to the user, though they would still be able to call it...

OK, so now it looks consistent with other methods and _remove is bound but still not visible to user. Thanks @bojidar-bg for help and review.


Cherrypick #901 to release/1.0

Revert #902.
Cherrypick #901 to release/1.0.

/test pull-cri-containerd-node-e2e


Update colors when updating data on existing chart

I came across this today and it does make sense given that data and colors are supplied independently to Chartkick, however I'm running into an issue where updating the data on an existing chart puts the data and colors out of sync.
Is there a way to update the color series on an existing chart?

There isn't, but sounds like a good idea. Happy to accept a PR to add a color option to multiple series format.
[{name: "Sales", data: {}, color: "green"}]

Closing out feature requests to clean up GitHub Issues. If there is still interest AND someone wants to add this, please reply and we can continue to discussion.


Feature/boas 225 return status in get application

Describe your changes
added new backend function getAll to get all applications. Changed the CO, CAO and Inspector routes to use this function instead of getByStatus.  getAll returns status field as a string.
BOAS-225 (Backend Subtask) https://pins-ds.atlassian.net/browse/BOAS-225
as part of feature BOAS-164: https://pins-ds.atlassian.net/browse/BOAS-173
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have double checked this work does not include any hardcoded secrets or passwords
[x] I have made corresponding changes to the documentation
[x] I have provided details on how I have tested my code
[x] I have referenced the ticket number above
[x] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

@DavidJWhiteDev there are some conflicts to be resolved before merging


Add .githenv when running from github workflow

Signed-off-by: Dimitris Karnikis<EMAIL_ADDRESS>

Mergin to main (doesn't affect pash behavior)


build(maven): allow maven release plugin to push release changes

This speeds up the release process by removing the push branch and push tag steps.
While also reducing the chance that a release could be but never tagged and pushed.

:construction_worker_man: :no_entry: CI is failing on master as well


dandelion 容器为退出状态，日志如图

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
本地部署 openv2x，发现部署不成功。
查看镜像，发现 dandelion 容器为退出状态。
Expected behavior
Screenshots

If applicable, add screenshots to help explain your problem.
Log Information
If applicable, add more detailed log information to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

https://github.com/open-v2x/dandelion/pull/170


E2E Test execution is failing

Description:
The e2e test execution (Acceptance Test) is failing in the pipeline & locally.
When we ran the below command:
./gradlew test -Pe2e

Error:
No tests found for given includes: com.uk.companieshouse.e2e.*
Log trace:
> Configure project :
********************************************************
                   Executing E2E tests
********************************************************

> Task :compileJava
Note: /Users/abhishekrajput/dev/learn-concourse/spring-boot-microservice-best-practices/src/main/java/com/uk/companieshouse/expectionalhandler/ControllerExceptionHandler.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :compileTestJava
Note: /Users/abhishekrajput/dev/learn-concourse/spring-boot-microservice-best-practices/src/test/java/com/uk/companieshouse/connector/CompaniesHouseConnectorTest.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test'.
> No tests found for given includes: [com.uk.companieshouse.e2e.*](filter.includeTestsMatching)

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 13s
6 actionable tasks: 6 executed

Last successful execution:
https://app.circleci.com/pipelines/github/abhisheksr01/spring-boot-microservice-best-practices/362/workflows/7cf1fcbd-45d9-4c77-9cf1-d34ac2d9387f
Any other context
Tried with the  6.7.1 gradlew & iocucumber dependency of 6.10.0.
The current "./gradlew test" command doesn't execute the e2e directory evident from the build/reports as no cucumber reports are available.

Fixed.


Implement blog upvote downvote on frontend

No backend imple yet so work with dummy stuff

Assign to me plz


Add step counter to IMU API

Enables the step counter in the BMI270, exposing a step_counter_read method as part of the IMU API.
Example usage:
import app
import imu

from events.input import Buttons, BUTTON_TYPES

class ExampleApp(app.App):
    def __init__(self):
        self.button_states = Buttons(self)
        self.acc_read = None
        self.steps_read = None

    def update(self, delta):
        if self.button_states.get(BUTTON_TYPES["CANCEL"]):
            self.button_states.clear()
            self.minimise()
        else:
            self.steps_read = imu.step_counter_read()

    def draw(self, ctx):
        ctx.save()
        ctx.rgb(0.2,0,0).rectangle(-120,-120,240,240).fill()
        if self.steps_read:
            ctx.rgb(1,0,0).move_to(-80,-40).text("steps:\n{}\n".format(self.steps_read))
        else:
            ctx.rgb(1,0,0).move_to(-80,0).text("no readings yet")
        ctx.restore()

__app_export__ = ExampleApp

Thanks for this, it was on my to do list. I've given this a try and it is working for me. Can you add a stub for the sim in sim/fakes/imu.py, then I'll merge it.

Thank you for this, @Gregox273! I've added a simple stub to the simulator and merged this.


Component - Logo

[x] Network Logo

Design review: 3.2-Account & Network
Please review some suggest below:

[ ] Grouping avatar & subIcon


Crosspost: URL of a federated WordPress post reopens the post in the app instead of a browser

Quick summary
This issue was originally filed on the Mastodon repo: https://github.com/mastodon/mastodon-android/issues/739

I'm using the ActivityPub plugin to enable following posts from my WordPress blog. The posts federate as excerpts with a URL pointing to the full post on my site.
Tapping on that URL in the Android app only causes it to reload the post (excerpt) inside the app, instead of opening the URL in either webview or a browser as I'd expect it to.
The (official) IOS app does open the URL a browser, as does Firefox on the desktop, which is why I suspect the Android app being at fault here.

I think with the new feature in the official Mastodon Apps, that try to open links in the App directly (which I like, because it should bring more interaction to the site (comments, likes, boosts, ...)), we need a way to prohibit that for the links we add via the "Post content" settings, to not have an infinite loop (see video in the Mastodon issue).
Steps to reproduce

Install official Mastodon Android App
Click on the Permalink/Shortlink of a Mastodon Post

What you expected to happen
The App should load the URL in the default browser instead.
What actually happened
It results in an infinite loop.
Impact
Some (< 50%)
Available workarounds?
Yes, easy to implement
Logs or notes
No response

I've seen this in Tusky on Mastodon, was assuming it tried to maybe fetch an activitypub+json representation of the URL first. When I again click the link, it opens a browser window (on my Android phone), no infinite loop. But I also typically configure apps to never open links in the "in-frame" browser or whatever it's called.
One "solution" to this might be ... not showing a permalink in the post itself? I mean, I know this isn't actually a solution, but Mastodon statuses are also web pages, and they don't display a URL as part of their post content (yet you can still click "open in browser" for them).
(I like the idea of explicitly showing a permalink, as it raises awareness that "regular" web sites can also be ActivityPub servers, etc.)
Meanwhile, I think it's up to apps to fix this themselves.

In the furture, maybe related https://github.com/mastodon/mastodon/pull/26917 for implementation in Mastodon itself? See discussion https://hachyderm.io/@thisismissem/111076105053359483 https://mastodon.social/@aslakr/111092724148991855 etc.

Unless clients become better at recognising that the post contains links to itself, I suspect it will add to the problem.
I guess solutions might be:

Clients should have better interface on how to open the original page. In that case it might not be necessary to have links to itself in posts.

The links in posts don't respond with activitypub+json. How would that work if/when WordPress redirect to canonical url?

The clients should recognise that links in posts contains links to itself.

One "solution" to this might be ... not showing a permalink in the post itself? I mean, I know this isn't actually a solution, but Mastodon statuses are also web pages, and they don't display a URL as part of their post content (yet you can still click "open in browser" for them).

Unfortunately, I don't think it is one since the link is required to backfeed comments to the blog via webmention.

I was thinking about adding a parameter to disable the return of the application/activity+json accept header, or maybe make Mastodon support link targets (<a href="" target="_blank" />).


Springload -  Multiple Roles

Springload 最新工作信息：

[x] Silverstripe Developer (intermediate - senior) - https://apply.workable.com/springloadjobs/j/B147EDF97B/
[x] Backend Developer Python (senior)- https://apply.workable.com/springloadjobs/j/39BB0A87FC/
[x] Test Engineer (intermediate) - https://apply.workable.com/springloadjobs/j/C57AAE4111/

内推请联系：Alex

closed!


http-proxy-middleware

the library update, you have to make the change in the proxy
OLD
const proxy = require('http-proxy-middleware')
NEW
const { createProxyMiddleware } = require('http-proxy-middleware')
Example
const { createProxyMiddleware } = require('http-proxy-middleware')

module.exports = function(app) {
  const port = process.env.REACT_APP_PORT_SERVER || 5000
  app.use(createProxyMiddleware('/api', { target: `http://localhost:${port}/` }))
}

sure, here is my change


[Spike] polkadot xcm

The Cross-Consensus Message Format, or XCM, is a messaging format and language used to communicate between consensus systems.
One of Polkadot's main functionalities is interoperability amongst parachains and any other participating consensus-driven systems. XCM is the language through which complex, cross-consensus interactions can occur. Two blockchains can "speak" XCM to seamlessly interact with each other using a standard messaging format.
We would like to get a spike going to research and review the following

XCM configurations
Testing connections XCM
Send a message from one parachain to another.

We can close in favor of alternative state-proof verification approach


Feature: Reduce refresh interval

The reduce interval should have an option to be lower than 30s. Given the increments already present, how about something like an option for 2 / 5 seconds?
Related: The "refreshing" message should have an option to be disabled unless the manual refresh button is clicked on. This makes sense because if:
a) The refresh interval is small, it'll just be present on the screen all the time.
b) The refresh interval is large, it serves very little purpose because the implication is that someone is just staring at their phone / tablet screen waiting to get that little bit of data. Anyone who uses a large refresh interval will most likely end up using the manual refresh button when they fire up the app as it is.

eeque the refresh options will be included in release 3.4.x.
Regarding the "Refreshing" message, it will be deleted in release 3.3.0 in few days, because you are right, it doesn't make sense having that message if there is a progress bar that indicates an action is being performed.
Best regards!

Added refreshing options:

5 seconds
10 seconds
15 seconds
20 seconds

They will be included in the next release.


[runtime] prevent deadlock during tests

The tests got stuck here:
[DECI2] Got message: 24 0 0xe042 H -> E
IOP shut down
DMA shut down
dconnect: closed socket at kernel side
[2021-05-12 22:05:47:686] [debug] [VM] Killing
[2021-05-12 22:05:47:686] [debug] [SYSTEM] Thread VM-DMAC is returning
[Listener] Closed connection to target

The runtime was stuck at vm_dead_cv.wait(lk, [&] { return components == 0; });
I think due to a race condition decrementing components and wait_vm_dead going to sleep
  --components; // no mutex locked
  vm_dead_cv.notify_all();

and
  std::unique_lock<std::mutex> lk(status_mutex);

  vm_dead_cv.wait(lk, [&] { return components == 0; });

Pull Request Test Coverage Report for Build 837540070

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 69.162%

Totals

Change from base Build 837488748:
0.002%

Covered Lines:
34330

Relevant Lines:
49637

💛  - Coveralls

good catch... multithreading is such a pain


[HOLD for payment 2024-07-25] [$250] mWeb - Chat - The emoji picker is closed and user unable to select emoji

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

Version Number: 9.0.5-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4701464
Issue reported by: Applause - Internal Team
Action Performed:

Go to https://staging.new.expensify.com/home
Tap on a report
Send a message
Long press the message sent and tap emoji plus icon

Expected Result:
The emoji picker must not be closed and user must be able to select emoji
Actual Result:
The emoji picker is closed and user unable to select emoji
Workaround:
Unnown
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/ffc21801-ec6b-43af-9338-4a82111333f0
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~012d2a5157510d29ca
Upwork Job ID:<PHONE_NUMBER>003336181
Last Price Increase: 2024-07-12
Automatic offers:

ikevin127 | Reviewer | 103132063

Issue OwnerCurrent Issue Owner: @muttmuure

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

We think that this bug might be related to #vip-vsp

Proposal
Please re-state the problem that we are trying to solve in this issue.
The emoji picker is closed immediately when opening it from the context menu.
What is the root cause of that problem?
In the modal component, we set a popstate listener which will close the modal when triggered if shouldHandleNavigationBack is true (it's only true for emoji picker).
https://github.com/Expensify/App/blob/dd96852320612fd5188c95e659fce3814150af82/src/components/Modal/index.tsx#L46-L49
It's triggered when we call back here when the modal is closed if the state contains shouldGoBack property that we push above.
https://github.com/Expensify/App/blob/dd96852320612fd5188c95e659fce3814150af82/src/components/Modal/index.tsx#L23-L29
However, the back is triggered even though we don't close the emoji picker. That's because it's triggered from the context menu hide. When we show the emoji picker, the context menu is closed which triggers the back. shouldGoBack exists in the history state because the emoji picker is shown first which already pushes the new state that sets shouldGoBack to true.
Long-press comment -> context menu shown -> press add emoji reaction -> push state, shouldGoBack: true -> context menu hides -> history.back -> triggers popstate -> emoji picker closes
What changes do you think we should make in order to solve the problem?

We can wait until the context menu is closed before showing the emoji picker using Modal.close. We can apply it here so it's applied to every component that shows an emoji picker, or we can just apply it in context menu case.
https://github.com/Expensify/App/blob/dd96852320612fd5188c95e659fce3814150af82/src/libs/actions/EmojiPickerAction.ts#L52-L66
What alternative solutions did you explore? (Optional)
Only call back if shouldHandleNavigationBack is true, but I think it won't work if in the future multiple modal enable shouldHandleNavigationBack.
https://github.com/Expensify/App/blob/dd96852320612fd5188c95e659fce3814150af82/src/components/Modal/index.tsx#L26-L28

@bernhardoj Thanks for your proposal.

We can wait until the context menu is closed before showing the emoji picker using Modal.close. We can apply it here so it's applied to every component that shows an emoji picker, or we can just apply it in context menu case.

Before I can decide on the RCA / solution, can you please expand on the main solution mentioned above with code example ?
I need enough specifics to be able to apply the solution myself locally and test the fix.

@ikevin127 added the code example

Thank you for the update!

@bernhardoj's updated proposal looks good to me. I verified the RCA as correct and the proposed main solution fixes the issue as per the expected result (the emoji modal will open when the button is tapped).

Video

Android: mWeb

I think it's safe to go with the version which adds Modal.close() within the showEmojiPicker function, such that this issue is covered in all places where showEmojiPicker is currently used.
🎀👀🎀 C+ reviewed

No overdue, issue assigned

PR is ready
cc: @ikevin127

cc @muttmuure

Requested payment in ND.

$250 - @ikevin127 C+
$250 - @bernhardoj  C

Kevin has been paid in Upwork

$250 approved for @bernhardoj


Wrong php version restriction

Project contains composer.lock file and after execute composer install I have following errors:
 Problem 1
    - Installation request for doctrine/annotations v1.5.0 -> satisfiable by doctrine/annotations[v1.5.0].
    - doctrine/annotations v1.5.0 requires php ^7.1 -> your PHP version (7.0.22) does not satisfy that requirement.
  Problem 2
    - Installation request for doctrine/instantiator 1.1.0 -> satisfiable by doctrine/instantiator[1.1.0].
    - doctrine/instantiator 1.1.0 requires php ^7.1 -> your PHP version (7.0.22) does not satisfy that requirement.
  Problem 3
    - doctrine/annotations v1.5.0 requires php ^7.1 -> your PHP version (7.0.22) does not satisfy that requirement.
    - dingo/blueprint v0.2.3 requires doctrine/annotations ~1.2 -> satisfiable by doctrine/annotations[v1.5.0].
    - Installation request for dingo/blueprint v0.2.3 -> satisfiable by dingo/blueprint[v0.2.3].

but minimal version of php in composer.json is 7.0.0.

could you find a solution for that issue?

@brugasoft just remove composer.lock and execute composer install

issue solved. thank you!

Glad this solution was available, thank you @zhdanovartur.

Fixed in the last update, thanks and sorry for the late.


add a completion function for zsh

This adds a file for doing tab-completion for totp-cli subcommands from zsh.
You may want to move this down to a subdirectory but there didn't appear to be an applicable existing directory so I've added it in at the root. When totp-cli is installed, you would ideally want to arrange for this file to be installed into $prefix/share/zsh/site-functions but I'm not especially familiar with how that works for Go programmes so it perhaps needs to be dealt with by packagers or end-users.

I don't think go can do it, maybe it can, but i wouldn't dig deep for that. Can you add instructions to the readme about it please?

The new push adds instructions to the README.
I also noticed a typo a few lines up from it ("Sell" instead of "Shell").


Use uv for running tests

This is an experiment to try to use uv for our CI running the tests and see if it speeds up things.

General Notes
Thank you for contributing to sentry-python!
Please add tests to validate your changes, and lint your code using tox -e linters.
Running the test suite on your PR might require maintainer approval. Some tests (AWS Lambda) additionally require a maintainer to add a special label to run and will fail if the label is not present.
For maintainers
Sensitive test suites require maintainer review to ensure that tests do not compromise our secrets. This review must be repeated after any code revisions.
Before running sensitive test suites, please carefully check the PR. Then, apply the Trigger: tests using secrets label. The label will be removed after any code changes to enforce our policy requiring maintainers to review all code revisions before running sensitive tests.

Ok, sometimes it is really way faster like with our web frameworks 2 test suite:
web frameworks 2:
normal: https://github.com/getsentry/sentry-python/actions/runs/8598128406/job/23558323415?pr=2690
with uv: https://github.com/getsentry/sentry-python/actions/runs/8602095050/job/23570859665?pr=2943
But for example the Django tests are not faster at all. But not sure If I am just holding it wrong:
web frameworks 1:
normal: https://github.com/getsentry/sentry-python/actions/runs/8598128398/job/23558330541?pr=2690
with uv: https://github.com/getsentry/sentry-python/actions/runs/8602095042/job/23570870189?pr=2943

Lot of things have changed since this PR. It did its job and showed that using uv makes things faster. I will close this now.