Script download button does not work on Linux since 1.0.15

On 1.0.15 and 1.0.16 the download button for scripts does not work any more on my Gentoo Linux.
I have to start 2.0.18 to download the script, then I can open 1.0.15 or 1.0.16 and click "install".

I also have this problem with the Appimage file. On 1.0.15/16 the download button for the scripts does not work.

Same issue here with both 1.0.15 and 1.0.16 appimage on fedora 39. Developer tools or bash do not show any error/failure, the button just does not work.

Same here. Downloaded appimage, made it executable.
Download buttons have no effect.
I opened the dev tools, tried to open the url in ffox and file explorer with no success.
Example url
pinokio://download?uri=https://github.com/cocktailpeanutlabs/magnet
The pinokio protocol seems to not be attached to a program
v1.0.16 on mint 21.2, krnl 6.5

solved in 1.1.0
Thank you

Also solved for me in 1.1.0, ... closing


Output G3DJ With Optimisations

New command option -s
Outputs JSON without any whitespace
and removes unnecessary trailing zeros after decimal point

What's the use-case for this?

On mobile it saves us time downloading and parsing g3dj files.

Well that's why there's g3db

We are moving towards the binary format soon, just thought this would be a nice addition.
Anyway, its your call.

I'd rather not complicate the code without having at least one valid use-case for it.


Navigation breaks when slidesToShow and slidesToScroll are not equal values

I would like to be able to scroll by 1 slide throughout all breakpoints no mater how many slides I have set to show. This currently breaks the carousels navigation.
To re-create the issue:
Please use this most basic example I have set up to test and demonstrate the bug.
http://jsfiddle.net/FreznoSmooth/wnp8up64/
Test uses the "responsive display" example http://kenwheeler.github.io/slick/

Set slidesToShow to be different for all 3 breakpoints
Set slidesToScroll to be the same (1) for all 3 breakpoints
Resize window so that only 1 slide is being shown.
Select the last slide.
Resize window so that 2 slides are being shown
The current slide index seems to be incorrect now and the carousel navigation (button and swipe) is broken. In this instance you can click the prev navigation button twice and it will come right (not ideal).
Refresh and restart the test from step 3, however this time at step 5 resize your browser larger so that 3 slides are being shown. Now the carousel navigation (button and swipe) is completely broken.

Seems the current slide index may not be re calculating correctly on resize?
Would be great to get this issue resolved as otherwise slick is a great plugin!

This can be fixed with #2152
Fiddle with #2152

Looks like this got fixed when #2152 got merged. Closing.


Spice added to GRSISort

Spice is now added to the master branch of grsisort;
Additionally some small bug fixes are included; the largest was a strict comparision to the TChannels that would cause the Fragment sort to crash at write time if multiple tchannels with the same name existed.

Unless I'm being massively blind I think the TS3Data.h file is missing.

I forgot to add both TS3Data .h and TSiLiData.h to the repo.  I just fixed
this.
On Fri, Aug 28, 2015 at 1:03 AM, jhenderson88<EMAIL_ADDRESS>wrote:

Unless I'm being massively blind I think the TS3Data.h file is missing.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/pull/462#issuecomment-135636660
.


Create the document of the repository

@all-contributors please add  for

@all-contributors please add Mogakamo for

@all-contributors please add Mogakamo for documentations

@all-contributors please add @Mogakamo  for documentation

@all-contributors please add @Mogakamo  for maintenance

@all-contributors please add @Mogakamo  for ownership

@all-contributors please add @Mogakamo for owner

@all-contributors please add @Mogakamo as owner

@all-contributors please add @Mogakamo for design


refactor oauth authenticators

Codecov Report

Merging #311 (c1f030b) into master (bed7d02) will decrease coverage by 0.16%.
The diff coverage is 89.60%.

@@            Coverage Diff             @@
##           master     #311      +/-   ##
==========================================
- Coverage   85.63%   85.47%   -0.17%
==========================================
  Files          56       56
  Lines        4400     4385      -15
==========================================
- Hits         3768     3748      -20
- Misses        632      637       +5

Impacted Files
Coverage Δ

quetz/main.py
88.11% <55.55%> (-0.33%)
:arrow_down:

quetz/authentication/oauth2.py
88.15% <88.15%> (ø)

quetz/authentication/auth_dao.py
92.30% <100.00%> (ø)

quetz/authentication/github.py
100.00% <100.00%> (ø)

quetz/authentication/google.py
100.00% <100.00%> (ø)

...s/versions/53f81aba78ce_use_biginteger_for_size.py
56.25% <0.00%> (-18.75%)
:arrow_down:

...ns/versions/30241b33d849_add_task_pending_state.py
80.00% <0.00%> (-13.34%)
:arrow_down:

...ons/a3ffa287d074_case_insensitive_channel_names.py
68.75% <0.00%> (-6.25%)
:arrow_down:

...ions/versions/8dfb7c4bfbd7_new_package_versions.py
82.35% <0.00%> (-5.89%)
:arrow_down:

...s/versions/8d1e9a9e0b1f_adding_download_metrics.py
72.22% <0.00%> (-5.56%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #311 (c1f030b) into master (bed7d02) will decrease coverage by 0.16%.
The diff coverage is 89.60%.

@@            Coverage Diff             @@
##           master     #311      +/-   ##
==========================================
- Coverage   85.63%   85.47%   -0.17%
==========================================
  Files          56       56
  Lines        4400     4385      -15
==========================================
- Hits         3768     3748      -20
- Misses        632      637       +5

Impacted Files
Coverage Δ

quetz/main.py
88.11% <55.55%> (-0.33%)
:arrow_down:

quetz/authentication/oauth2.py
88.15% <88.15%> (ø)

quetz/authentication/auth_dao.py
92.30% <100.00%> (ø)

quetz/authentication/github.py
100.00% <100.00%> (ø)

quetz/authentication/google.py
100.00% <100.00%> (ø)

...s/versions/53f81aba78ce_use_biginteger_for_size.py
56.25% <0.00%> (-18.75%)
:arrow_down:

...ns/versions/30241b33d849_add_task_pending_state.py
80.00% <0.00%> (-13.34%)
:arrow_down:

...ons/a3ffa287d074_case_insensitive_channel_names.py
68.75% <0.00%> (-6.25%)
:arrow_down:

...ions/versions/8dfb7c4bfbd7_new_package_versions.py
82.35% <0.00%> (-5.89%)
:arrow_down:

...s/versions/8d1e9a9e0b1f_adding_download_metrics.py
72.22% <0.00%> (-5.56%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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


fix(presto): check for valid datasource types when fetching ds names

SUMMARY
Make sure we have a valid datasource_type before performing Presto query to fetch all tables or views
ADDITIONAL INFORMATION

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

Codecov Report

Merging #11952 (f2c282f) into master (a7bba92) will decrease coverage by 0.48%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##           master   #11952      +/-   ##
==========================================
- Coverage   64.45%   63.97%   -0.49%
==========================================
  Files         937      465     -472
  Lines       45319    28550   -16769
  Branches     4317        0    -4317
==========================================
- Hits        29211    18265   -10946
+ Misses      15948    10285    -5663
+ Partials      160        0     -160

Flag
Coverage Δ

cypress
?

javascript
?

python
63.97% <83.33%> (-0.22%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/db_engine_specs/presto.py
73.56% <50.00%> (-8.20%)
:arrow_down:

superset/connectors/base/models.py
90.62% <100.00%> (+0.13%)
:arrow_up:

superset/connectors/druid/models.py
82.18% <100.00%> (ø)

superset/connectors/sqla/models.py
90.37% <100.00%> (-0.41%)
:arrow_down:

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/db_engine_specs/sqlite.py
65.62% <0.00%> (-9.38%)
:arrow_down:

superset/utils/celery.py
96.42% <0.00%> (-3.58%)
:arrow_down:

superset/examples/world_bank.py
97.10% <0.00%> (-2.90%)
:arrow_down:

superset/examples/birth_names.py
96.51% <0.00%> (-2.33%)
:arrow_down:

... and 476 more

Continue to review full report at Codecov.

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

Going to close, this method is always called indirectly and datasource_type here is not datasource.type db column


Update troubleshooting section in docs.md

• Steps to fix error when install 3 packages globally at once

Awesome thank you!

Any time!
Have a nice day


Move to Go modules

This is the result of:
go mod init github.com/golang/gddo
go mod tidy

@freeformz - does your change need to be rebased? Since it's almost a month since the last activity on https://go-review.googlesource.com/c/gddo/+/178597, I sent another shot to add go.mod in https://go-review.googlesource.com/c/gddo/+/187717 - hopefully either one or another can resolve this in a near future 😄


Error: You need either xclip or xsel for emoji-keyboard to work

"You need either xclip or xsel for emoji-keyboard to work" error message is presented with emoji-keyboard 2.2.0 on Linux Mint 18.2. All dependencies listed in the README were installed correctly, and the previous release (2.1.0) didn't have this issue.
Was able to resolve the issue by installing one of the mentioned packages, but this should be taken care of as part of the dependencies during installation.

I kinda rushed with this release...
These aren't dependencies because they should only be used when Gtk clipboard fails (e.g. under KDE).
Instead they are currently used by default which will be fixed in the next release.
That's gonna take a bit tho, because I'm currently pressed for spare time. Apologies.

No worries, thank you for the information.

Fixed in the latest release (2.3.0), correctly falling back on gtk clipboard now.
It's still better to have either xclip or xsel available, as gtk clipboard is rather buggy via python bindings at least.


gdb plugin: Encapsulate the gdb native command gcore as nxgcore

Modify elf with nxgcore and call gcore:
(gdb) nxgcore --help
usage: [-h] [-o OUTPUT] [-t OBJCOPY] [-r MEMRANGE]
options:
-h, --help            show this help message and exit
-o OUTPUT, --output OUTPUT
Gcore output file
-t OBJCOPY, --objcopy OBJCOPY
Select the appropriate architecture for the objcopy
tool
-r MEMRANGE, --memrange MEMRANGE
examples:
(gdb) nxgcore -t arm-none-eabi-objcopy -r 0x40200000,0x48000000,0x07
Summary
Impact
Testing

Typo in PR name:
gdb plugin: Encapsulate the gdb native command gcore as nxgore
should become:
gdb plugin: Encapsulate the gdb native command gcore as nxgcore

@W-M-R please lint error.

Please include Documentation/
https://nuttx.apache.org/docs/latest/search.html?q=nxgcore&check_keywords=yes&area=default

The tools/gdb directory may require a separate patch to be added next, as the previous ones were not added either


Add deploy with docker in doc

We will provide docker image recently. We already have pr(https://github.com/wu-sheng/sky-walking/pull/163) and issue(https://github.com/wu-sheng/sky-walking/issues/162). When we finish those two, we will provide documents.

Here are the documents about deploy image .
EN:Deploy collector image
ZH:部署Collector镜像


[release/1.2] Update cri to 0d5cabd006cb5319dc965046067b8432d9fa5ef8

Fix a bug that a container can't be stopped or inspected when its corresponding image is deleted;
Fix a bug that the cri plugin handles containerd events outside of k8s.io namespace.

Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

LGTM


Show service class tags in order service wizard

Fixes #54
cc @serenamarie125

I'll let you decide
On Mar 30, 2017 1:29 PM, "Sam Padgett"<EMAIL_ADDRESS>wrote:

@spadgett commented on this pull request.
In src/styles/order-service.less
https://github.com/openshift/origin-web-catalog/pull/59#discussion_r108987483
:

height: 30%;

padding-left: 180px;
padding-right: 180px;

.wizard-pf-steps-indicator .visited .wizard-pf-step-number {

 cursor: pointer;

 color: @color-pf-black;

 background-color: @color-pf-white;

 border-color: @color-pf-blue-300;

}

.order-service-description {
clear: both;
margin-top: 15px;
}
.tag {
margin-right: 5px;

I have it working and it seems to work well, but I can take it back out.
FWIW I think Bootstrap uses the same technique in its grid
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/openshift/origin-web-catalog/pull/59#discussion_r108987483,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZk7fnm9vdxyP6fw3br1Gm1r2H9D2C3ks5rq-ZygaJpZM4MupV0
.


Get logged in user in @azure/msal-browser": "^2.0.0-beta.3"

Please follow the issue template below. Failure to do so will result in a delay in answering your question.
Library
@azure/msal-browser": "^2.0.0-beta.3
Description
I see in the new beta 3 version we getAccountByUsername and getAllAccounts which could return more than one account.
It is not clear to me how come we know longer have getAccount.    If I getAllAccounts, how do I know which is the one that they just signed in with (if there is more than one)?   If I don't know whom is signed in, then I cannot getAccountByUsername since I don't know the username yet of the person signed in.   Normally that is what getAccount would let me know.

Another is example is that previously, to get the loginHint, I was getting the member name
this.msalInstance.getAccount() which would give me the user information and from there I could get the loginHint.
It seems in Beta 3 it isn't possible anymore to figure out the username you want when getAllAccounts returns more than 1 account.

There is an example of how we use getAllAccounts in our sample. If there is only one signed in user it will return that one user just like getAccount did. When there are multiple accounts, you will need to have some logic to determine which one you want to get.

Ok, so essentially we need to store the user's username in a cookie to track who they last signed in with?   That way we  can call in getAccountByUsername (username).  If we don't store the username somewhere we wouldn't know who they have last signed in with.
Is that correct?
Isn't anyway MSAL can do that for us so we can keep getAccount() ?

@jrmcdona MSAL will track the account info you have signed in, but we don't support keeping track of a current account session. If you want to ensure your application is always a single account application, you can do that yourself by ensuring you don't present a sign-in screen after the initial login.
I am investigating the bug filed in #1844 where the getAllAccounts() API is returning bad data, but ideally 1 login = 1 account.

Ok, so essentially we need to store the user's username in a cookie to track who they last signed in with? That way we can call in getAccountByUsername (username). If we don't store the username somewhere we wouldn't know who they have last signed in with.
Is that correct?

We can discuss adding an API or object for single account scenarios if this is difficult to manage, but ideally yes, you would have to store the username of the currently signed in user somewhere if you want to use MSAL as before.

@pkanher617  thanks .   Would you be able to add the last username they logged in with into the localStorage/sessionStorage so we can get that via MSAL API instead of rolling our own?

@pkanher617 @jmckennon
I think the MSAL API should let us know the username that is currently logged in so that we don't have to create a separate cookie and manage this cookie and logic.  It seems very incomplete on a part of the MSAL API.  It is not a streamlined .
getAllAcounts should give us all the accounts.
getAccount should give us the account that it is currently signed in/active.
How comes this is an issue?

Closing as this was resolved offline.  MSAL.js will not keep track of the currently signed in account - developers must track that themselves.

@pkanher617

If you want to ensure your application is always a single account application, you can do that yourself by ensuring you
don't present a sign-in screen after the initial login.

If I understand correctly, this is not always possible to ensure by just don't presenting the sign-in screen after the initial login in my application. For example, if I use my admin Azure AD user to login to portal.azure.com and then I go to my own application and try to log in with my personal user, MSAL.js will keep track of both accounts, even though one of the logins didn't happen in my own application. Is that right?
Is there any piece of documentation on how to achieve the same single account behaviour that we had in MSAL v1 using loginPopup?


Elinor Tyrell effect in set up.

When you play Elinor Tyrell in set up, teki allows you to play 2 limited cards in the set up.

I ran into this one in a game I played just now. It's definitely a bug -- all cards come into play simultaneously for setup, so elinor's ability doesn't allow for an extra limited during setup.


Experiment with Alternate Searches

Create a testbed and experiment with alternate searches.
One focus will be to test the features and performance of the textmatch functionality in kypher.
Another focus will be to prejoin label, pagerank, and description for enhanced search.
select node1, label, pagerank, description
from searchtable
where textmatch(upper_case_label)
order by pagerank, label
limit 20 # in practice, a variable that can be changed in the query API.
We want to compare the functionality and performance of the current search (glob), the current search
with a leading *, the various forms of textmatch, and the elastic search server.

Done, closing


chore: add telemetry reminder if meeting type/feature

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Replaced the pull_request_target with pull_request to test the code. Refer to https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#pull_request_target

This event runs in the context of the base of the pull request, rather than in the context of the merge commit, as the pull_request event does. This prevents execution of unsafe code from the head of the pull request that could alter your repository or steal any secrets you use in your workflow. This event allows your workflow to do things like label or comment on pull requests from forks. Avoid using this event if you need to build or run code from the pull request.

And the github-actions bot label type/feature won't trigger this workflow. Refer to https://github.com/peaceiris/actions-label-commenter?tab=readme-ov-file#work-with-other-auto-label-actions

When you use the repository's GITHUB_TOKEN to perform tasks, events triggered by the GITHUB_TOKEN, with the exception of workflow_dispatch and repository_dispatch, will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's GITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.

Generally LGTM.
I found that ~30% of the PRs are labeled as type/feature. I am not sure how effective the reminder can be if only a portion of them requires adding telemetry. I think reminder from the reviewers is still required.

How about user-facing-changes + type/feature? which restricts to the features that really matters to users.

Just user-facing-changes seems okay. Telemetry focus mainly on user-facing PRs.
The action may not have the ability to handle AND logic within labels.


Add PG13 support

What feature are you requesting?
The latest Supabase wrappers in our fork adds PG13 support. We should add that.
Why are you requesting this feature?
Support all PGDG.
What is your proposed implementation for this feature?
N/A
Full Name:
Philippe Noël
Affiliation:
ParadeDB

Edit: We're now on latest wrappers. We could add PG13 support


Preferred syntax for @param

It seems there are two competing versions in the wild, and I was wondering if one should be preferred over the other.
Yard's own docs describe:
@param name [Types] description

The source code itself seems to lean towards:
@param [Types] name description

Anecdotally, latter feels more common.
What's the "right" way? Should one even worry about this?

Either syntax is supported and "correct". The former are part of the new official recommendation, the latter being more legacy (and therefore more widespread), but it's not going away. You can decide which one you like more.

Marking this as closed since the question is (hopefully) answered. Feel free to comment or reopen if you think there is something else to discuss.


Ancient Greninja form loss

Describe the bug
Killing a pokemon in battle with Ancient Greninja will cause it to turn into ash greninja due to its ability, removing its ancient form.
To Reproduce
Steps to reproduce the behavior:

Give self Ancient Greninja
Enter battle and kill a Pokemon
See error

Expected behavior
You should see that Ancient Greninja turns into a normal Greninja after battle.

Fixed, next datapack update removes Battle Bond from being a valid ability with Ancient Form Greninja. All existing Ancient Greninja will need to be updated to match manually.


Exporting PDF

Issue
When exporting an individual note to the pdf, css looking code is also exported in the document. For example a one and a half page document is exported with the theming as well and becomes 11 pages.
Ways to replicate
Export a note when the theme is turned on. If you disable the plugin and export again you can see that it exports normally.
Thanks for this great plugin

@Xindi7 This should be fixed in version 1.2.5. Do let me know if that is not the case. Thanks for reporting!


monaco-tree-row

Hello everyone
As I can see ".monaco-tree-row" height is hardcoded, could you add option to customize it's height?

Not exactly. Which component of the workbench would you like to increase the height of each row?

@joaomoreno project explorer in sidebar area and command palette.

I can change it via css, but it brokes keyboard navigation in command palette.

Thanks for letting us know. It is currently not supported, but we'll take it into account. This is a good issue to follow: #3112


Performance enhancements for single and multi-thread evaluations

Experiments show that with few changes huge boosts (synthetic tests 3x faster) can be achieved
(caused by less synchronization + much better JIT code generation)

Perf enhancements speedup:
Before:
$ ./threads.sh 1
Testing THREADS=1 TIME=3000
Finished 17 tests  sum=2.605197E11
Thread test finished total=17
$ ./threads.sh 4
Testing THREADS=4 TIME=3000
Finished 12 tests  sum=1.689628E11
Finished 12 tests  sum=1.929169E11
Finished 12 tests  sum=2.02259E11
Finished 11 tests  sum=1.705385E11
Thread test finished total=47
After:
$ ./threads.sh 1
Testing THREADS=1 TIME=3000
Finished 42 tests  sum=6.101973E11
Thread test finished total=42
$ ./threads.sh 4
Testing THREADS=4 TIME=3000
Finished 26 tests  sum=3.680051E11
Finished 22 tests  sum=3.780026E11
Finished 26 tests  sum=4.324088E11
Finished 27 tests  sum=3.765051E11
Thread test finished total=101

maybe update the performance numbers in the README?


Support for HTTP proxying of event emissions?

It looks like support existed at one point (https://github.com/getsentry/raven-java/pull/1), but the code has changed a lot since then, and it doesn't currently seem to be supported. It seems like it would support could be added by passing a proxy here: https://github.com/getsentry/raven-java/blob/fd5a44c11d851180909ab7fe8c23cc3dc7773617/raven/src/main/java/net/kencochrane/raven/connection/HttpConnection.java#L101 via https://docs.oracle.com/javase/7/docs/api/java/net/URL.html#openConnection(java.net.Proxy).
I'm envisioning that the proxy settings could be set as additional GET params on the DSN, e.g.: https://public:private@host:port/1?http_proxy_host=127.0.01&http_proxy_port=1234, but wanted to get feedback on this approach before submitting a pull request (which I am more than happy to do). Another approach could be modifying RavenFactory to add another constructor accepting the proxy arguments.
Please let me know if I'm missing something and that this is already supported.
/cc @mnussbaum

This seems reasonable to me. I'd use the query parameters on the DSN as you mentioned (probably raven.http.proxy.host and raven.http.proxy.port for consistency with the style of the other configuration parameters) rather than modifying the factory.

@tkaemming so we tried again today, and it turns out that the java.net APIs used actually do support -Dhttps.proxyHost and -Dhttps.proxyPort -- I think we may have been typoing the properties.
Given that, I think we can just document this in the README.md -- we can put together a PR for that.

I think it's OK to reopen this one (specifically to allow providing a Proxy instance to HttpConnection.)

Hi, is someone already working on this ? Are you open to an external contribution ?

I haven't started on anything. We're definitely open to contributions.

Just a heads up, I have a PR up that I'll be finishing today.

Merged this, will be publishing with 7.5.0 soon.


Constraint ignored in ruleset, but respected as standalone.

Trying to constrain an element width to be half of another container's width. Defining the constraint in a ruleset is ignored, but it is accepted when defined as standalone constraint.
#lead {
    /* This does not work as expected */
    width: == #hero[width] / 2;
}

/* This works as expected. */
#lead[width] == #hero[width] / 2;

See example:
http://codepen.io/oslego/pen/eNavPP

I believe this is a result of how scoped selectors work. The first ruleset is looking for and element with the ID of hero inside of an element with the ID of lead.
#lead {
    /* This may work depending on your markup */
    width: == ^#hero[width] / 2;
}

Ah, I missed that. Indeed, unintended nesting was the problem.
Thanks for the clarification, @paulyoung!


feat(service): Add Plivo service

Added support for Plivo as a backend service with unit tests and documentation.

@prashanthpai appreciate your contribution. I will look over it asap. I saw that you have mocked the service, which I find very interesting. We are having a discussion about how we can best test all services reasonably. If you are interested in sharing your experience with us, please tell us here #1.


including sail.h when using vcpkg

When using vcpkg to manage the sail library, including sail looks like:
#include <sail/sail/sail.h (notice the two "sail/" folders)
This leads to compiler errors in the sail.h file because it cannot open include file notifying us that it cant find them. I found a temporary fix by moving the "include/sail/sail" folder to "include/" and therefore I can simply do #include <sail/sail.h> and there aren't any errors anymore.

Please see https://github.com/HappySeaFox/sail/issues/75
TL;DR Use CMake integration or add VcpkgInstalledDir/include/sail to the project include path. CMake does that automatically.

Thank you for the quick response!


How to train YOLO_NAS?

💡 Your Question
How to train YOLO_NAS on datasets, like coco?
Versions
No response

Go to the YOLONAS.md, link on the homepage. There is documentation and even a google colab for finetuning.
YOLO_NAS is already trained on coco


Combine assets, NFT, destroyed to asset item in the header

[x] Implemented

figma link
web
https://www.figma.com/file/bSUF8SniEtSOWNGsnHTEpI/statescan?node-id=2920%3A12686
mobile
https://www.figma.com/file/bSUF8SniEtSOWNGsnHTEpI/statescan?node-id=2920%3A12304
source
Assets > https://statemine.statescan.io/assets
NFT > https://statemine.statescan.io/nft
Destroyed > disabled now
preview
web

mobile

[ ] Hide "Destroyed"
@YoshiyukiSakura

preview


fix: configuration example for selector

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
Fixes example for metasrv config about selector
Checklist

[ ] I have written the necessary rustdoc comments.
[ ] I have added the necessary unit tests and integration tests.
[ ] This PR requires documentation updates.

@sunng87 don't forget to run make config-docs(just notice the develop.yaml workflow ignore the config/**).


API for masking signals

If you have a program with real-time requirements, e g if you're running low-latency audio, you're having one thread of critical priority which does this and other threads at normal priority. You would probably prefer if signals (that the program handles) are happening in some other thread than the real-time critical one.
It would be nice if there was a safe abstraction to masking signals in specific thread(s) for this reason.

OK, I've just released a new version that links to the nix crate in documentation.
Feel free to reopen if there's a reason to have it in this crate too (eg. it should in some more direct way interact with the API this crate offers).


Please invite me to the GitHub Community Organization

Oh sorry, if you want to join the Chryz-Hub community. You need to use this invitational issue


Use native tls instead of curl/openssl

Hi all
I am currently forced to work on a mac and can not use my favorite cargo extensions like cargo-update or cargo-tree because they depend on curl/openssl.
This evening I tried to patch git2-rs but I failed.
Did you ever consider using native-tls?

Thanks for the report! The dependency comes from libgit2, though, not from the Rust code, which is much harder to change.


payments API implementation details

I discussed with @pstan26 about possibly building a "coin-operated file viewer" protocol. But @shea256 mentioned that I'd need Blockstack's JS payments API feature in order to do so.
At a high level, what are the implementation details required to get this done? Would love to start a discussion about it to see if there's any way that I, or other community members, could help.

@larrysalibra any ideas?

In my mind, this should be something that is built on top of or that works with bitcoin's lightning network.

Maybe @roasbeef can assist? I think this would be a huge app if done properly and potentially a perfect first app for marriage of Blockstack + Lighting.


Readme: Fix link to Yadda docs

Thanks @lolmaus, I don't really know if people still use this but this won't hurt. 😄

Oh yeah, that's my favorite thing.
I've been hired without a technical interview thanks to my experience in it.
And I'm building a follow-up addon, gonna share a link soon.

I’ve sent you an invite for contributor. As you are much more likely to use it then me. 😊

@albertjan Thx, accepted!
As I understood, you're no longer using ember-cli-yadda yourself. Why? Are you no longer writing acceptance tests? Or have you switched to a different testing library? Or a different frontend framework?
Even though you're no longer using ember-cli-yadda, I still need your opinion on Yadda and ember-cli-yadda.

For us at https://kaliber5.de , Yadda and ember-cli-yadda have a lot of value. We use them in every project, and can't imaging writing tests without them.
That said, I've found traditional Yadda approach to be problematic and have come up with a number of know-hows and tricks to make using Yadda easier and more enjoyable.
Thanks to support from my employer kaliber5, I've built my approach into a follow-up addon.
Today I've published docs for it, please have a look: https://kaliber5.github.io/ember-cli-yadda-opinionated/versions/addon-docs/
The docs are still WIP, but should give you a good idea of the direction I'm taking Yadda to.
Now that you've made me a maintainer of ember-cli-yadda, I have a big temptation to move my approaches into ember-cli-yadda and make them the default.
The problem is that, though I strongly believe my approaches are very efficient, they are at the same time extremely opinionated and won't suit every app, especially existing ones.
So it makes total sense to have my approaches in a follow-up addon. Unfortunately, to use the follow-up addon, a developer must undo some of the work ember-cli-yadda is doing, which is also not optimal.
I have some ideas how to merge the two addons and keep the flexibility, but they require validation.

So please read through the docs of my addon and tell me what you think. Where should we draw the line, or should we merge the efforts into a single addon?

CC @simonihmig

@albertjan What do you think? ☝

I've been studying the docs, they look very good! I like the more modern approach. But I have to think a bit more about the ramifications 😄. With that I mean we could/should do away with some of the more esoteric things in ember-cli-yadda and adopt the opinionated way. But I do think we should keep the escape hatch to be able to do plain yadda tests.

All in all I'm v-much in favour of merging the projects. I would also not mind transferring the repo to @kaliber5.

Hi @albertjan :) Chiming in here...

All in all I'm v-much in favour of merging the projects.

I would object here! 😆 At least if that means literally making one addon out of the two. I think having a nicely layered approach, where ember-cli-yadda provides the foundation, which people can use by itself, and having the opinionated one on top makes sense in general. Where there is friction between the two, there are hopefully ways to reduce/eliminate that without giving up the layered approach. I guess we can discuss this, here or in direct conversations mit @lolmaus ...

I would also not mind transferring the repo to @kaliber5.

I am open to that. Given my experience maintaining a bunch of addons, I tend to be a bit afraid of taking over the responsibility burden nowadays. :wink: But given that we are pretty much invested into the addon anyways, and thus have to take the maintenance burden anyways, if we want it or not, and both of us (me and Andrey) already have collaborator status and you seem to not use in anymore (that much), I guess this move would make sense!
So if you agree and this move is also preferable to you, feel free to do that! I guess you have to initiate this as the repo's owner?

I would object here! 😆

It makes sense to have the opinionated things in a separate plugin. But the api for the non opinionated version feels old and the step inheritance problems @lolmaus describes in the docs would also help the non-opinionated version. It would make adding the opinionated version later also easier because those things look much more alike.


Install CMake config files into lib${LIB_SIFFIX}

The CMake config files should be installed in the same location as the libraries and pkg-config files.
Dispite what the documentation for find_package states, CMake will look into directories like /usr/lib32 for CMake config files (and has done for ages). The documentation has been fixed in the latest git master:
https://cmake.org/cmake/help/git-master/command/find_package.html

Merged in 88bb3f89a5782cd95a781277c4f665239fc914cc and cherry-pick to branch 2.5.1


Update free-courses-ru.md

Add three new courses
What does this PR do?
Add resource(s)
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Followup

Check the output of Travis-CI for linter errors!

Add instructor names to disambiguate.

Well, I think i added authors

for the python courses, one is titled "Поколение Python": курс для продвинутых while the other is "Поколение Python": курс для начинающих
Don't invent titles! Use the title given by the resource.

for the python courses, one is titled "Поколение Python": курс для продвинутых while the other is "Поколение Python": курс для начинающих
Don't invent titles! Use the title given by the resource.

Its original titles

Thanks!


:brut.apktool.smali:dexlib2:test FAILED when compiling repo

org.jf.dexlib2.AccessorTest > testAccessors FAILED
junit.framework.AssertionFailedError: expected:<12> but was:<1>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:277)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at junit.framework.Assert.assertEquals(Assert.java:201)
at org.jf.dexlib2.AccessorTest.testAccessors(AccessorTest.java:125)
105 tests completed, 1 failed
:brut.apktool.smali:dexlib2:test FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':brut.apktool.smali:dexlib2:test'.

Can't duplicate here. Test is from smali anyhow.

I have just did a clean install of Ubuntu 14.04.2 and tried to build and gotten the same error as my windows

Same error on Mac OS X - investigating further...


Change readme to use the top level package.

This is cleanup prep work for a pending release next week.


How to correctly use Protpardelle to obtain results consistent with the paper?

First, I did not modify the default parameter configuration of the model and used the all-atom mode.
When running the code of "main"， I found that in the first and second stages of sampling, the protein backbone is different.
I found that in the default parameters, ‘cond information’ is not injected in the following two places.
https://github.com/ProteinDesignLab/protpardelle/blob/7d42fc99d57fe46c7cb55282d1c1e9880bb43aa0/models.py#L1033
https://github.com/ProteinDesignLab/protpardelle/blob/7d42fc99d57fe46c7cb55282d1c1e9880bb43aa0/models.py#L141

Sorry for replying late. the problem was solved. Please check the new codes.


Changing number of epochs

Hello,
I'm trying to run the UniSRec model from scratch (using 'python finetune.py -d Scientific') and I want to change the number of epochs. How can I do this?
Thanks!

Hi, thanks for your interest!
You can use python finetune.py -d Scientific --epochs=50 to change the maximum number of training epochs. In default, epochs is 300.
Or you can use python finetune.py -d Scientific --stopping_step=30 to change the early stopping. If stopping_step is 30, it means that the training may stop earlier if the validation metric does not update (to a better result) for 30 epochs. In default, stopping_step is 10.
More details and parameters can be found in the API doc of RecBole


SFTP

I selected SFTP as upload but i cant give my ftp details and it just uploads to imgur while i have sftp selected
I am on windows

Once you select the upload option the tab on the far right changes to offer the settings. Once your done changing settings close the window to save.


popup.html is updated

What does this PR do?

Any background context you want to provide?

Screenshots and/or Live Demo

@RishabMangal Can you please provide some context here as to what this PR is supposed to do?

Closing this due to inactivity.


Tweaks to data frame example

Remove non-existent cell editing functionality
Add filter feature

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Refactor member list to remove duplicates

Refactored member email array to remove duplicates using Set and map for clean MultiSelect display in alert modal.

we refactored the useGetOrgMembers hook to return the owner along with the other members so this check is no longer needed.


GMail stopped labeling 'mention' from GitHub

My rule on GMail:
<EMAIL_ADDRESS>OR (from:notifications@github.com)) AND<EMAIL_ADDRESS>OR<EMAIL_ADDRESS>AND AND ("FIRSTn LASTn" OR @130s)) OR (gitlab.com AND ((("Reviewer changed to" OR "Assignee: ") AND "FIRSTn MID1_MID2 LASTn") OR @130s))))

Failed to capture e.g. https://github.com/CCNYRoboticsLab/scan_tools/issues/75 which doesn't seem to match the rule.

Particularly this part is excluding unintentionally. Removing this seems to be working.
<EMAIL_ADDRESS>OR<EMAIL_ADDRESS>AND


idk how to install 1.19.3 version

im too stoopid for github

Too bad

@hhhzzzsss you should build a release for 1.19.3 people

I added a 1.19.3 version to the releases just now


creates get_column_from_sql and fetch macro

Opening a draft PR for feedback.
To-do:

[x] Documentation in README.md
[x] Tests

Closes #122

This is awesome

Closing this PR to open a fetch macro branch/PR that is more limited in scope


Add Docker 20.10.7

https://github.com/moby/moby/releases/tag/v20.10.7

Add to https://github.com/rancher/install-docker/

Verified on Rancher master-head version 6b430f3
Create AWS infrastructure provider with 3 nodes, 1 role each.

Change Docker Install URL to https://releases.rancher.com/install-docker/20.10.7.sh in node template.
Launch cluster and wait for cluster to become available.
Docker version on all nodes is 20.10.7

Create DO infrastructure provider with 3 nodes, 1 role each.

Change Docker Install URL to https://releases.rancher.com/install-docker/20.10.7.sh in node template.
Launch cluster and wait for cluster to become available.
Docker version on all nodes is 20.10.7

Create a custom cluster on CentOS 8.3.2011 x86_64 docker version 20.10.7, 1 node all roles.

Provision 1 CentOS 8.3.2011 node
Install docker on node with curl -sSL https://releases.rancher.com/install-docker/20.10.7.sh |sh
Provision custom cluster using Rancher registration command with all roles.
Cluster comes up successfully


Use nyc instead of old istanbul 0.4.

Istanbul 0.4 is not able to parse async/await correctly. So, we must switch to the current version of Istanbul and its CLI nyc.
connects to plossys/plossys#1467

LGTM

:tada: This PR is included in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add CODEOWNERS file to the repo

Thanks for such a wonderful repo. I think the repo could really benefit from a codeowners file so that the PRs can get auto reviewers added.
More info on codeOwners -
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#about-code-owners

Thanks for the suggestion! I'll add it!

Done!


ImportError: libboost_filesystem.so.1.65.1 in Collab

Did anyone run into this error?

Does this  help?


Add some WKT Empty tests

Also, remove noisy build flags, and add an editorconfig file for consistent spacing, etc, to match project defaults.

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (ab80d43) 19.69% compared to head (2784b22) 32.57%.

Files
Patch %
Lines

src/s2geography/wkt-reader.cc
0.00%
2 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           master      #15       +/-   ##
===========================================
+ Coverage   19.69%   32.57%   +12.88%
===========================================
  Files          14       14
  Lines        1488     1458       -30
  Branches       29       28        -1
===========================================
+ Hits          293      475      +182
+ Misses       1189      975      -214
- Partials        6        8        +2

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

Codecov seems a little magical to me... there's almost no tests written, but it finds my new signature in WKTReader and complains. Why doesn't it complain about all the other classes that have non-tested methods? Does it have a list of classes to check? Where?


Add operator * to Plane

Adds the asterisk (*) operator to the Plane class. It does the same thing that Transform.xform(plane) does in 3.x.
Fixes https://github.com/godotengine/godot/issues/63489.

Thanks!


How to redirect titian's log?

I have a question about how to redirect titan's log?
I try to redirect log like this,but have no use.
BaseConfiguration baseConfiguration = new BaseConfiguration();
baseConfiguration.setProperty("storage.backend", "hbase");
baseConfiguration.setProperty("storage.hostname", HostName);
baseConfiguration.setProperty("log4j.appender.stdout", "org.apache.log4j.ConsoleAppender");
baseConfiguration.setProperty("log4j.appender.stdout.Target", "System.out");
baseConfiguration.setProperty("log4j.appender.stdout.layout", "org.apache.log4j.PatternLayout");
baseConfiguration.setProperty("log4j.appender.stdout.layout.ConversionPattern", "%d{ABSOLUTE} %5p %c{1}:%L - %m%n");
baseConfiguration.setProperty("log4j.rootLogger", "warn, stdout"); baseConfiguration.setProperty("log4j.logger.com.thinkaurelius.titan", "WARN");

In the future, please use the Titan mailing list for questions like this. The issue tracker is used for bugs.
Logging is done with Log4j. Refer to the $TITAN_HOME/conf/log4j-console.properties for the configuration. It is used by $TITAN_HOME/bin/gremlin.sh by passing the configuration as a property when starting the console via -Dlog4j.configuration=conf/log4j-console.properties.


bottlerocket with mulitple cluster-dns

Description
Observed Behavior:
Not able to set mulitple ips for cluster-dns-ip
bottlerocket allows you to set it via
# Valid, single IP
[settings.kubernetes]
"cluster-dns-ip" = "<IP_ADDRESS>"

# Also valid, multiple nameserver IPs
[settings.kubernetes]
"cluster-dns-ip" = ["<IP_ADDRESS>", "<IP_ADDRESS>"]

Trying to set it like
[settings.kubernetes]
"cluster-dns-ip" = ["<IP_ADDRESS>", "<IP_ADDRESS>"]

Gives the following log
karpenter-f7cdc49f4-25kbx controller 2023-10-15T02:10:53.850Z	ERROR	controller	Reconciler error	{"commit": "322822a", "controller": "machine.lifecycle", "controllerGroup": "karpenter.sh", "controllerKind": "Machine", "Machine": {"name":"workers-gmsx5"}, "namespace": "", "name": "workers-gmsx5", "reconcileID": "8ace2c6e-45f7-4bb4-84d8-79388dde83b0", "error": "launching machine, creating instance, getting launch template configs, getting launch templates, creating launch template, invalid UserData toml: cannot decode TOML array into struct field bootstrap.BottlerocketKubernetes.ClusterDNSIP of type *string"}

Looking at the code it takes a string but even if you do it with a comma it always just has one which is the default kube-dns
https://github.com/aws/karpenter/blob/main/pkg/providers/amifamily/bootstrap/bottlerocket.go#L59
Expected Behavior:
be able to have a /etc/resolv.conf in pods like
node-local helps to stop against loading a lot of coredns servers so we aren't rate limited by the vpc resolver.
$ cat /etc/resolv.conf
search testing.svc.cluster.local svc.cluster.local cluster.local ec2.internal
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>

Reproduction Steps (Please include YAML):
Tried both of the following
     userData: |
        [settings.kubernetes]
        "cluster-dns-ip" = ["<IP_ADDRESS>","<IP_ADDRESS>"]

and
     userData: |
        [settings.kubernetes]
        "cluster-dns-ip" = "<IP_ADDRESS>,<IP_ADDRESS>"

Versions:

Chart Version:
Kubernetes Version (kubectl version):

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

This one is a little painful since our support for Bottlerocket merging is driven by our own struct, meaning that if we were to just do something simple like change this *string value to []string, we would be breaking users on the newer version. I'd like to be able to just update our type for ClusterDNS in the bottlerocketsettings.go file to be a []string but I think we're going to have to support both *string and []string like Bottlerocket does.
I haven't dug in enough to understand exactly how to achieve this through a TOML parse, since I doubt that the default toml library in go supports this functionality.

I'm also going to change this to a feature request since we have had support for the ClusterDNSIP feature with Bottlerocket, but it looks like they added the support for this to be a string or an array in this PR.

Looks like this can be closed out as part of Bottlerocket v1.8.0. https://github.com/bottlerocket-os/bottlerocket/issues/2132#issuecomment-1151807660
Can you confirm @mzupan @z0rc if this works on this version?

@njtran incorrect. Bottlerocket 1.8.0 introduced support of setting cluster-dns as array. Kaprenter still doesn't support this, previous comment still stands.
OP mentions setting cluster-dns-ip via user data, which is another case and isn't supported, see https://github.com/aws/karpenter-provider-aws/issues/5584#issuecomment-1922665533.

Just wanted to add that we would really need this feature.  We deal with Conntrack issues, so node-local DNS would be a easy fix, but without being able to pass 2 IP's we would be creating a new problem where anytime that local cache pod went down, the host would lose DNS access.

Hi there, just want to follow up here as I just stumbled over the same problem.
I can see that there is already string[] used here: https://github.com/aws/karpenter-provider-aws/blob/e0cd8a470ab533c1f6643a763c0c65575a0fd631/pkg/providers/amifamily/bootstrap/bottlerocketsettings.go#L60C3-L60C118
can't we "just" change ClusterDNSIP here https://github.com/aws/karpenter-provider-aws/blob/e0cd8a470ab533c1f6643a763c0c65575a0fd631/pkg/providers/amifamily/bootstrap/bottlerocketsettings.go#L51 to just be of type string[] as well and assign the full array here https://github.com/aws/karpenter-provider-aws/blob/e0cd8a470ab533c1f6643a763c0c65575a0fd631/pkg/providers/amifamily/bootstrap/bottlerocket.go#L55
I haven't seen where the merging you have mentioned is happening, maybe you could give me a hint @jonathan-innis
I'm happy to take a look and create a PR to adress this.


v4: Carousel animation bouncing on Microsoft Edge

I'm having this issue with Bootstrap carousel on Microsoft Edge:

This gif is from official documentation page.
OS: Windows 10
Browser: Microsoft Edge 38.14393.0.0

Same as : #21751

Also a dupe of #21685.


Rename Licenses trait to License and make it an object

Partical fix for #93 addressing the first two tasks.

@hseeberger: The third task in #93 is to make all License implementations objects with an apply method taking the year and copy right owner as parameters and returning the license text. I don't know how to implement this for the Custom license. Any idea?

codacy failed because of val HeaderLicense in autoImport. Codacy wants fields to start with lower case.

Codacy should Take a Look at scala.Predef and the scala Package object ;-)

@britter I think you have to introduce StandardLicense extends License and add def text(yyyy, owner) to that instead of License. When pattern matching on the license you have to disambiguate btw. Custom and StandardLicense.

@hseeberger I'm gave that a try but ran into the following problem:
sealed trait License {
  def apply(text: String) = text
}

sealed trait SpdxLicense extends License {
  val identifier: String
  val apply(yyyy: String, copyrightOwner: String)
}

final case object Custom extends License

final case object ALv2 extends SpdxLicense {
  override val identifier = "Apache-2.0"
  override def apply(yyyy: String, copyrightOwner: String)

  // what to do here? We want ALv2 to only have apply(yyyy: String, copyrightOwner: String)
  override def apply(text: String) = ???
}

The License trait should 't have text.
And don't use abstract vals, use defs unsträflich.

@hseeberger how about ff25a03 ?


Utility functions to cpp

Completed writing and wrapping cpp implementations of utility functions, and TRIAD. Testing has also been done. Unit testing for functions, and validation testing for TRIAD. Pytest results are seen below.

@pdetrempe I deleted one of the test_orbit scripts. Let me know if that's okay. I deleted it out of the bottom of the repo (py_funcs folder) and left the one in the test folder alone.


Adding Subscribers with Test PLMN 001 01

Hi all,
it seems like adding subscribers does not work properly when the PLMN has leading zeroes, like Test PLMN 001 01.
Adding a subscriber:

In the overview, the leading zeroes are gone:

Same when modifying the user:

2022-03-03T23:15:15+01:00 [INFO][WebUI][App] webconsole version:

        free5GC version: v3.0.6-7-gd8267b4
        build time:      2022-03-03T22:13:38Z
        commit hash:     +c26286b
        commit time:     2022-02-09T17:45:03Z
        go version:      go1.14.4 linux/amd64

Hi @mrlnc
If this issue hasn't been resolved yet, would the following URL be helpful to you?
https://github.com/free5gc/free5gc/issues/330

Fix in https://github.com/free5gc/webconsole/pull/24


Feature/email change improvements

According to issue #60 I've implemented logic for verification email changing.
Previous logic for email change verification was moved to common GET /verify handler that now can handle new type of requests - email_change.

@awalias check it please=)


Need parens around reference to PREFIX variable.

$PREFIX needs to be $(PREFIX), or "make install" will fail if the user's shell is a variant of csh.

Can confirm this is a valid issue. I get an error of this sort without the above fix:
make[1]: Leaving directory `/home/ubuntu/workspace/pcg-c-0.94/sample'
install src/libpcg_random.a REFIX/lib
install: cannot create regular file ‘REFIX/lib’: No such file or directory
make: *** [install] Error 1

sudo make install after doing this, fixes all my problems.

Merged from another patch.


Can you help me out with the compiling process?

Hi,
I just wanted to change the font height of the SWS note window from 14 to 22 on this file: https://github.com/reaper-oss/sws/blob/master/SnM/SnM.h and then compile it.
Unfortunately, I don't haven't done this before so I don't exactly understand how to proceed.
Trying to follow the compiling instructions you provided under "Usage" I ran git clone --recursive https://github.com/reaper-oss/sws and
cd sws in CMD, changed the font height inside the file, ran that reaper action, saved the generated file under C:\Users\my_name\AppData\Roaming\REAPER
I then ran cmake -B build -DCMAKE_BUILD_TYPE=Debug but got an error that the command "cmake" is either written incorrectly or couldn't be found.
Same thing with cmake --build build
What should I do now?

Did you install the Build Tools for Visual Studio or the Visual Studio IDE? Once installed, CMake and the Microsoft's C++ compiler should be available using the "x64 Native Tools Command Prompt for VS 2019" shortcut (rather than regular cmd.exe).
The next version of SWS in the works adds a setting to S&M.ini for customizing the font size of the notes window's text field. Here's an experimental (and still incomplete) build: https://ci.appveyor.com/api/buildjobs/0ocdljvqbumnwash/artifacts/build%2Fsws-<IP_ADDRESS>-Windows-x64-v2.13-b9f69231.exe.

Thank you for your reply
The file doesn't contain any code worded "Fontsize", so I assume I need to write a line regarding that myself? I don't know how to do it though.

Yes, the line must be added manually. Can you double-check the new version is being loaded (it should show 2.13 in the about window) and the line in S&M.ini is formatted like this:

no idea what I went wrong before but now it works, thank you


Refactor Workflow-output API - Prepare for ThreadedWriter use in Dask

This PR refactors some critical components of the Workflow class to simplify the single-GPU writers.  The goal of this PR is to (1) make it easier to leverage the single-GPU writer code within Dask, and (2) "simplify" the Workflow API a bit.
There are a lot of changes here, so I decided to stop short of actually chagning the Dask-based IO to use the single-gpu writer classes.
Closes #51
General Workflow Changes:

Moving all iteration-based processing into iterate_online method
Moving all dask-graph-based processing into build_and_process_graph method
Simplifying apply method to call one of the above methods
Narrowing scope of update_stats method (using this means the user only wants to update stats, not shuffle/write data or apply unnecessary ops)

IO-Specific Changes:

Removing ds_writer.py
Removing Shuffler (I feel that the shuffling strategy should be decoupled from the writer a bit more, for simplicity)
Introducing a output_format argument to Workflow methods - iterate_online uses this arg to specify the writer to use.
Refactoring ThreadedWriter to decouple metadata packaging/writing - This will make it easier to write global metadata with Dask
Added global _metadata write for ParquetWriter  (Addressed #51)
Moving the write_to_dataset definition from BaseWorkflow to Workflow, and using iterate_online or build_and_process_graph to (optionally) apply ops and write a dataset (with a desired format)

write_to_dataset does not allow statistics gathering - the statistics must already be available. When users want to do stats/transofrms/write altogether, they should use apply.

@jperez999  - Let me know if the CI problem is on my end, otherwise I'm assuming it isn't (for now)

rerun tests

rerun tests


LibWeb/Tests: Add Ref, Layout, and Screenshot test support to add_libweb_test.py

The boilerplate could probably be more helpful for the newer test types. I can fix that up if given recommendations/requests. I found the existing tests a bit irregular 😅
Also updated the docs to reflect the changes. While it's topical, I can also write some stuff up addressing #398. I already have some stubbed in sections for the new test types added in the doc ("the different kinds of tests" to quote the issue), and I myself would like to know more about "what makes a test good". I'll summarize whatever else if given something to work from

Another thing I noticed - currently Ref and Screenshot tests can't be in subdirectories. It might be nice if this script told you so, instead of creating tests that don't get run.

I'll fix this but I'm not understanding the mis-use case yet. What could you do incorrectly that would make a test that doesn't get run?

I'll fix this but I'm not understanding the mis-use case yet. What could you do incorrectly that would make a test that doesn't get run?

Tests/LibWeb/add_libweb_test.py some/subdir/test.html ref creates Tests/LibWeb/Ref/some/subdir/test.html, but only test files directly in Tests/LibWeb/Ref are found by the test runner, so this new test is invisible to it. Same for screenshot tests. It's a quirk of them not having an input/ directory. Maybe it makes most sense to give them an input/ directory instead, but that's out of scope for this PR.
Feel free to just ignore the subdirectory thing!

Tests/LibWeb/add_libweb_test.py some/subdir/test.html ref creates Tests/LibWeb/Ref/some/subdir/test.html

Okay I see, I only considered someone putting in test-name as opposed to path/to/test_name. We could add --subdir as an extra flag and check for valid combinations. Not sure if you'd prefer to freely make new directories or if you want the fat finger insurance. Could also defer that to another commit.

This has a conflict - the documentation changes now need to go in Documentation/Testing.md.
Worrying about subdirectories can be deferred for now. I think making those test types allow subdirectories would be the better option, which is out of scope for your PR.

In #2175 I resolved the subdirectory issue by making Ref/Screenshot tests use the same directory structure as the others (allowing tests in subdirectories).
However, the tests now go in Ref/input and the expectations in Ref/expected instead of Ref/reference, (and same for Screenshot tests) so those paths need updating here.


Will my IP address be block by google if I perform 5 searches every 30 seconds?

There is no clear answer on rate limits provided by google, so all we can do is speculate and use trial and error. I've heard extremely mixed results with some people reporting the ability to do a few 100 searches a day without limits and others reporting under 15 a day.
5 searches back to back seems very high though, even 1 search every 30 seconds seems like quite a lot to me. I don't think that amount will work out for you. If you do get rate limited, your ip won't actually be blocked so there is little harm in trying. You may just have to start doing captchas more often for a little bit.

Thanks for the informative reply. Appreciate it


layout: sharding the blob store

One issue that I'm quite worried about is the performance impact of having too many blobs inside an OCI image. Now, practically speaking I would be surprised if n > 20 in most cases, but some people have expressed that they would like to have the entire universe bottled into an OCI image. I will refrain from commenting on how good of an idea I think that is, but if it's going to be a "valid usecase" then we should reconsider how we've organised the blob directory.
Namely, the current method of blobs/<algo>/<digest> will cause problems if the number of digests becomes quite large, due to implementation issues of filesystems. Essentially all filesystems are not designed to handle accesses of directories with many files well. If you look at how git, camlistore and many other such projects implement their blob storage it looks more like blobs/<algo>/<prefix>/<suffix> (or in camlistore's case, three sets of <prefix>/).
Naturally this would be a backwards incompatible change (you can't really implement this scheme as well as retaining the old one because then you have an exponential number of ways to read the same blob data, almost certainly leading to countless implementation bugs). So we should probably consider this for post-1.0.0.

On Sat, Nov 05, 2016 at 04:50:36PM -0700, Aleksa Sarai wrote:

… but some people have expressed that they would like to have the
entire universe bottled into an OCI image…

That may be me ;).  I'd rather phrase this as “I'd like the whole
universe in one flat CAS namespace, with individual CAS engines biting
off as large a chunk of that universe as they like”.  What I've tried
to supply in opencontainers/runtime-tools#5 is an API that works
regardless of the number of blobs in CAS.
Whether a particular implemenation of that API (e.g. image-layout)
scales to huge blob counts (clearly the tar-backed image-layout does
not) is a less important question.  Folks will just use a different
ref/CAS engine when they have large stores.  But ref/CAS consumers
shouldn't have to worry about that sort of implementation detail.

Namely, the current method of blobs/<algo>/<digest> will cause
problems if the number of digests becomes quite large, due to
implementation issues of filesystems. Essentially all filesystems
are not designed to handle accesses of directories with many files
well.

This has come up before in #94 and #208, with the bulk of the
discussion based on 1.  The consensus (as I understood it) was that
we shouldn't worry about this for now because modern filesystems don't
mind and tar isn't going to care either way.  Having stable, scalable
APIs buffers downstream consumers from any future CAS-storage
optimizations.

Agreed this is a dupe of #208.

@philips It's not a dupe of #208. #208 was about blobs/sha256/<the full digest> rather than blobs/sha256/<three byte>/<rest of digest> (which is what this is about).

@cyphar I guess in particular https://github.com/opencontainers/image-spec/issues/208#issuecomment-242398948 challenges the premise of this issue

This seems not a dupe of #208.
Even though pulling operation should never call getdents(2), pushing may call getdents(2) depending on the distribution protocol and its implementation, and likely to result in poor performance.
Also, there can be 3rd party tools (e.g. malware scanner, back-up) that are not aware of OCI manifest.
Can we reconsider this issue?

Since the layout of blobs/<algo> can be no longer changed, we might need to come up with some alternative layout.
Some my ideas and pros/cons:

blobs-sharded/<algo>/<prefix>/<digest>
Pro: Does not contaminate the existing blobs directory
Con: Maybe it is confusing to have two blobs directory? (blobs and blobs-sharded)

blobs/<algo>-sharded/<prefix>/<digest>
Pro: Single blobs directory
Con: sha256-sharded looks as if it is an algortithm, and can cause some implementation issue

blobs/<algo>/<prefix>/<digest> (identical to the original proposal)
Pro: Single blobs directory, no algorithm namespace contamination
Con: It can be 2X slower to scan the content of blobs/sha256, because the directory is likely to contain traditional blobs as well for compatibility

My preference is 1.
Also, we would need to define new field for the list of supported blob layouts in the oci-layout file. (or index.json maybe)
e.g.
{
    "imageLayoutVersion": "42.0.0"
    "supportedBlobLayouts": [ // if empty, "v1compat" is implicitly selected
        "v1compat",
	"sharded"
        // there can be other layouts that is specific to the distribution protocol? (e.g. "ipfs")
    ]
}


event listening: is only 'change' propagated? or How to set state with script without activating 'change'

No problem using $("#inputID").on('change') but for the life of me I can't attach a click listener to the toggle.  I've tried onClick="console.log(this)" directly on the input and also $("#inputID").on('click') but neither seem to work.
The root of the question is in that I need two listeners. Why? Because my initial script sets the toggle state according to an object property. Whenever this script sets the toggle state using $('#inputID').bootstrapToggle('on') it activates the $("#inputID").on('change') listener. Then when a user actually clicks on the toggle$("#inputID").on('change') is again activated.  I don't want the 'change' to happen twice, once with the initial script and secondly with the click. I want it just once on user click.  So I was thinking I could use the 'click' listener, but it doesn't seem to be propagating from the generated divs/label/span.

Few days ago I had exactly same problem - finally implemented not-so-nice workaround which works by switching state of underlying control without change event raised, and then manually forcing toggle update - also without notifications.
var toggle = $("#inputID").data('bs.toggle');
$("#inputID").prop("checked", isChecked)
if(toggle) toggle.update(true)

I too am in a scenario where I need to differentiate between a click and a change.

In the end this issue has made me abandon bootstrap-toggle.  In it's place I'm using bootstrap-switch http://www.bootstrap-switch.org which has a way to activate the toggle without activating the 'change' event.

I used http://kleinejan.github.io/titatoggle/, works great

Indeed, change fires twice, similar to this issue
https://github.com/Bttstrp/bootstrap-switch/issues/175
Need  a custom even for change, please


FirebaseAuth crashes on iOS when setting photoURL to null

https://github.com/flutter/plugins/blob/a444ad120418d622c4dea2882190968722abbcfe/packages/firebase_auth/ios/Classes/FirebaseAuthPlugin.m#L190
crashes if photoUrl is NSNull.null.

@nickolas-pohilets
The issue at https://github.com/flutter/flutter/issues/27897 has been closed and moved here. Future collaboration on this issue will be done here.

Hi @nickolas-pohilets
If are you still experiencing this issue
with the latest version of Flutter and FlutterFire plugin
can you please provide your flutter doctor -v
and your and your flutter run --verbose/flutter build --verbose ?
Also, to better address the issue, would be helpful
if you could post a self contained app on github
or the steps to reproduce it.
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.


 However, we should have looked at the first line of a commit message ending in that.
Fixes #29

Alright, this is included in v2.0.4 (🥁 Marching Orders) and is live. Thanks again for the contribution!


[Subtask]: Handle TransactionProgress

Task description
TBD
Requirements
TBD
Acceptance criteria
TBD
Creation checklist

[ ] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

Lets leave this open and blocked until we plan exactly how to use this, as the current implementation is a copy of what we used to do and this might not be what we want to do.


Deprecate (Reactive)PulsarListenerEndpointAdapter

This commit deprecates PulsarListenerEndpointAdapter and ReactivePulsarListenerEndpointAdapter in favor of default methods on ListenerEndpoint and its subinterfaces, which makes it a bit easier to provide custom ListenerEndpoint implementations.

Thanks for the PR @vpavic ,
The listener hierarchy side of things is a bit messy currently and refactorings like these are much appreciated. That being said, we are currently in RC and will do a 1.0.0-GA on 2023-11-20. As such, the only changes we are considering at this moment are bug fixes. We can consider the proposal after that though and I am more than happy to review it sooner.
Is the motivation of this change just a general improvement or it is unblocking you from doing something?

No worries, I understand the phase of the 1.0 is such that it's too late to accept this change immediately so close to the GA. There's always next minor release to target this at (that's also why I didn't refer any specific releases in the deprecation markers).
This isn't a blocker of any kind, just a convenience to have a simpler and more flexible listener hierarchy when implementing custom ListenerEndpoints.

Thanks for the contribution @vpavic !


Images not displaying correctly on documentation page

See https://shibuya.lepture.com/writing/media/

Oh, it seems unsplahs stopped this service.

Fixed


Data fetch() from zKillboard failed

Our maps on the public pathfinder (at https://www.pathfinder-w.space) have started failing to pull from zKillboard and displaying an error in the bottom corner:

.

Same issue on my servers. I have not had a chance to dig in.

Might have something to do with this:

https://github.com/zKillboard/zKillboard/wiki/API-(Killmails)
https://www.reddit.com/r/Eve/comments/q8bs4b/zkillboard_all_filters_disabled_with_exception_of/

The error is because the no-items endpoint no longer returns json, but instead a text response to say the endpoint is deprecated. You can try it yourself:
no-items has been permanently disabled.```


A duplicate code with same name overwrites the existing

Shouldn't be able to create a code with a name that matches an existing.

Fixed by 242dad4


What's New 104 & updated Experiments

Rendered page for review:
https://review.docs.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104?branch=pr-en-us-2072

Docs Build status updates of commit 28532fc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f3ebee6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/a11y-detached-elements.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/network-tool-ws-arrows.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 863d46e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/a11y-detached-elements.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-long.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-short.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/network-tool-ws-arrows.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8dda1c7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/a11y-detached-elements.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-long.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-short.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/network-tool-ws-arrows.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8ed7573:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/a11y-detached-elements.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-long.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-short.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/network-tool-ws-arrows.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit cca1339:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/a11y-detached-elements.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-long.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-short.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/network-tool-ws-arrows.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ec88c5c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/a11y-detached-elements.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/green-up-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-long.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-short.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/network-tool-ws-arrows.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/red-down-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit efb5df4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/a11y-detached-elements.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/green-up-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-long.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-short.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/network-tool-ws-arrows.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/red-down-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit d08a0f2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/a11y-detached-elements.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/green-up-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-long.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-short.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/network-tool-ws-arrows.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/red-down-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a0a5871:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/a11y-detached-elements.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/green-up-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-long.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/issues-request-urls-short.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/network-tool-ws-arrows.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/07/devtools-104-images/red-down-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a5e2f64:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:warning:Warning
View
Details

microsoft-edge/toc.yml
:warning:Warning
View
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/a11y-detached-elements.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/green-up-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/issues-request-urls-long.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/issues-request-urls-short.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/network-tool-ws-arrows.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/red-down-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md

Line 16, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '2022/07/devtools-104.md'.

microsoft-edge/toc.yml

Line 36, Column 21: [Warning: file-not-found - See documentation] Invalid file link: 'devtools-guide-chromium/whats-new/2022/07/devtools-104.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1d37669:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/devtools-guide-chromium/experimental-features/index.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104.md
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/3d-view-composited-layers.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/a11y-detached-elements.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/green-up-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/issues-request-urls-long.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/issues-request-urls-short.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/network-tool-ws-arrows.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104-images/red-down-arrow.png
:white_check_mark:Succeeded
View

microsoft-edge/devtools-guide-chromium/whats-new/whats-new.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


fix doc

fixes #202

@samigithub2022 @RobPasMue
we will need to push a doc release once this lands.  Could one of you show me how to do that?

@samigithub2022 @RobPasMue we will need to push a doc release once this lands. Could one of you show me how to do that?

@koubaa once this PR is merged to main, we can see the updated doc. There is a step (pages build and deployment) that runs after something is merged on to main. @RobPasMue

@koubaa - this is only for dev. for official release, we need to tag a release. @RobPasMue

That's right. Release docs are pushed whenever we do a new release @koubaa. Dev docs will have the change. Do you need it in the release docs as well?

If that's the case, we can hack something temporarily on the release branch but I'd suggest doing a new release.


Analyze Need for Lab Test Compendium

Mentioned as a need by Rishi in 2022-11-01 ETOR Architecture Review


[docs] Websockets example

Describe the solution you'd like

Custom manager.
Shows connection, disconnection lifecycles.
Shows intercepting sub/unsub actions
Shows dispatching receives on message pushes

https://dataclient.io/docs/concepts/managers#data-stream missing reconnection or offline handling logic.
Would love some contributions from those actually doing this as my testing is only theoretical


add Marcum-Q function

Added the Marcum-Q function to SpecialFunctions and its tests to SpecialFunctionsTests.
The paper and the original implementation code can be found at the following URL
https://dl.acm.org/doi/abs/10.1145/2591004

This looks excellent, thank you!
Some of the included helper functions may also be interesting on their own. There may also be some overlap with functions we already have, but we'd have to verify equivalence first before trying to bring them together. So I'm fine with including them internally, in isolation, as implemented.


Popup doesn't work properly if the button triggering the popup is inside another Svelte Component

Current Behavior

<Component  />

Popup Example

Clicking on the button inside Component will confusingly only work on page refresh, but not after navigation between pages using anchors.
Expected Behavior
Clicking on the button located inside the Component should open the popup regardless of any prior 'SPA-like' navigations.
Steps To Reproduce

Click on Open Popup! button
Observe how the popup opens correctly

Then:

Click on Navigate to Second Page link
Click on Navigate to first page link
Click on Open Popup! button
Observe how the popup does not open anymore (unless refreshing the page)

Link to Reproduction / Stackblitz
https://stackblitz.com/edit/sveltejs-kit-template-default-bmwdfj?file=src%2Froutes%2F%2Bpage.svelte
More Information

I have used npm create skeleton-app@latest my-skeleton-app to create the Stackblitz reproduction app.

@mihai-gabriel This is somewhat expected behaviour because of the order the components are rendered in.
so if we go step by step after navigation:

the component is rendered first because it is a child of the page,
which means the popup is initialized and starts searching for the div,
It finds nothing so it replaces it with an empty div
https://github.com/skeletonlabs/skeleton/blob/0bce0ff302b8a7995bf49bbeeb8d19d8614a2ceb/packages/skeleton/src/lib/utilities/Popup/popup.ts#L23

Now to be honest, I am not sure why it is not behaving like this when refreshing but I am suspecting something with how svelte do the initial page load.
and to solve your problem, you can easily move the popup above the component:

Popup Example

<Component  />

@Mahmoud-zino Thanks for the insight. Now that you're pointing it out, it does makes a lot of sense since the script inside the component runs when the component first renders. I got confused by the fact that it worked on page load, but as you said, it is probably because SvelteKit pre-renders all the HTML and then hydrates, which makes it so that the Component script is actually run after all the DOM is available.
I have learnt something new today :)
Thanks again and have a nice day!


hotkeys in lightbox

please provide hotkeys when videos playing in light box, kindly provide the tags on how to use in your documents

where can I find v2 ???

v2 is not released yet. I sadly currently don't have the time to work on afterglow. :(


bug on the option 'editor.bracketPairColorization.enabled'

Does this issue occur when all extensions are disabled?: No (because it needs vue extension)

VS Code Version: 1.60.2 (Universal)
OS Version: Darwin x64 20.4.0

Steps to Reproduce:

set the option "editor.bracketPairColorization.enabled": true
make a sample.vue file like below

<template>
    <div class="row">
        <input ref="key"
                v-model="key"
                class="col q-pr-md"
                label="key"
                outlined
                dense
                :hint="warningMessage"
                :rules="[
                    val => !!val,
                    val => /^[\w-]+?$/.test(val) || 'invalid character in Key'
                ]"
                @blur="checkDeviceKey"
        />
    </div>
</template>

'<>' brackets are colorized in the template tag but it seems like that > bracket in the js arrow function is treated as closing bracket of html tag

While I have used the bracket pair colorizer 2 extension, it did not colorize '<>' brackets.
Maybe it needs more detailed options like which kind of brackets to be colorized

While I have used the bracket pair colorizer 2 extension, it did not colorize '<>' brackets.´

<...> is now removed by default in latest VS Code insiders.
Duplicate of #132476.