Implement APIs for texture update in a non-GL thread.

Several changes included.

Introduced GVRFutureOnGlThread. This is a special implementation of RunnableFuture.
This should be used when you want a return value and run it with GVRContext.runOnGlThread(Runnable).

Add new APIs safeUpdate with GVRBitmapTexture. Previously GVRBitmapTexture.update
running on a non-GL thread won't return or report any error but you can't see your
update on screen. Using safeUpdate will make any update call from a non-GL thread
successful on screen.

Add new API GVRContext.isCurrentThreadGLThread. Previously, we only have API
assertGLThread inside GVRF to check if current thread is GL thread or throws an
Exception. I think it should be fine to open an API to check if current thread is
GL thread to judge if we should directly call anything that requires GL thread and
to see if we should use GVRFutureOnGlThread.

Fix GVRConsole. Previously, if you want to call GVRConsole.writeLine in a non-GL
thread, ex, through an input event, it won't update anything on screen. With
GVRBitmapTexture.safeUpdate, this is fixed.

Sample added for showing the fix on GVRConsole and safeUpdate on a non-GL thread.

GearVRf-DCO-1.0-Signed-off-by: Chao Chen

The change itself is fine but:

I'd say completely hide the old update(); safeUpdate does the right thing depending on which thread it is getting called. My reason is the more apis are exposed, the harder it will be on people to know which one when to use and they have to work out the difference between safe and unsafe update..

As GVRF seems to focus a lot on convenience, then next comes the GVRBitmapTexture ctor.. which has to be run on the GL thread. The users have to be completely oblivious of the GL thread (or at least that should be the goal); it is very confusing if the threading "leaks" here and there.

Some update according to Mihail's comment. May further update after discussion with you tomorrow.

Hi @liaxim
Just as you concerned, I just found that constructor of GVRBitmapTexture (actually of all kinds of GVRTexture) need to be called at gl thread. I will try to figure out this one.

Just talked to Mihail, I will make another pull request for the broader issues in Texture related classes. But as a pull request only for update() API, is there any other concern? If no, I am going to merge it.
@jason2kim @thomasflynn

Updated. @jason2kim @thomasflynn

it looks good to me


Add github action tht 'll send auto request to the mentors to review pr

Is your feature request related to a problem? Please describe.
After the contributors push their code , the mentors will be automatically be assigned to review the changes
Describe the solution you'd like
Add a github action that will send auto request to the mentors to kindly review the opened pr
Are you willing to contribute to this issue? [Yes]
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Thanks for your interest, Don't think we would be needing this atm :)


 I feel like you'd have to re-write most of their ai as they don't attack anything normally. Or perhaps were you thinking of neutral mobs?

Good! It makes races more real... It would be too sad for the enderian could be attacked by enderman...

seeing as origins are data driven, maybe something using teams could do the job for turning hostile mobs into passives, but i don't know how to do it the other way around or how to add neutral mobs to the equation

Please add this.


Fix: Enable Request Preview disables metric-config

Description
Disable metric config gear menu when request preview is on: It obstructs column preview and doesn't give enough functionality
Proposed Changes

Removes gear icon when the enableRequestPreview flag is on

License
I confirm that this contribution is made under an MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

There's probably some feature flag dependent logic we can remove from the metric-config component

@daniellevinson okay removed metric-config logic.


Windows Commands/fsutil: symlinkevaluation typo

Description:
As reported in issue ticket #4133 (switched), the description for the table entry symlinkevaluation shows R2R and R2L as values for the opposite lines in the last 2 of the 4 description lines. See also my previous attempt to resolve this issue on April 6, 2020, in PR #4134 .
Thanks to @alysdexia for reporting this issue.
Proposed change:

Make the parameter values R2R and R2L switch places to match their descriptions.

Ticket closure or reference:
Closes #4133

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

#sign-off

@illfated: I'm sorry - only the author of this article, @toklima, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Intermittent 'DP Wait' error on St boards causes bad state

OS: MacOS 10.14.5
Mbed OS: 5.13.1
Compiler: GCC or AC6.11
pyOCD: 0.21.0
Targets: ST boards (seen on F411, F413, F042K6, F475IOT)
When deploying or debugging ST targets, occasionally a DP Wait error is thrown. This puts the board into a state which still allows updates via mass storage device but any pyOCD interaction continues to show this error even after a hard reset.
0002309:CRITICAL:__main__:STLink error (20): DP wait
Traceback (most recent call last):
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/__main__.py", line 338, in run
    self._COMMANDS[self._args.cmd](self)
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/__main__.py", line 566, in do_gdbserver
    with session:
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/core/session.py", line 287, in __enter__
    self.open()
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/core/session.py", line 367, in open
    self._board.init()
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/board/board.py", line 83, in init
    self.target.init()
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/core/coresight_target.py", line 158, in init
    seq.invoke()
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/utility/sequencer.py", line 201, in invoke
    resultSequence = call()
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/coresight/dap.py", line 121, in power_up_debug
    self.write_reg(DP_SELECT, 0)
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/coresight/dap.py", line 117, in write_reg
    self.write_dp(addr, data)
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/coresight/dap.py", line 243, in write_dp
    self.link.write_dp(addr, data)
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/probe/stlink_probe.py", line 168, in write_dp
    result = self._link.write_dap_register(STLink.DP_PORT, addr, data)
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/probe/stlink/stlink.py", line 425, in write_dap_register
    self._check_status(response)
  File "/Users/robmor01/mbed-studio-tools/python/lib/python2.7/site-packages/pyocd/probe/stlink/stlink.py", line 292, in _check_status
    raise self._ERROR_CLASSES[status](error_message)
TransferTimeoutError: STLink error (20): DP wait

With reference to https://github.com/mbedmicro/pyOCD/issues/623, the environment isn't in a VM and all firmware is up to date.
It would be good to understand how to recover from this state.

Are you using the most recent STLink firmware?
An infinite wait response normally means a stuck transaction. But pyOCD has code to issue an abort, which should recover from this state (and does, in the few cases I've seen).

Have updated to the latest ST firmware and can confirm this problem still exists.

Update: I'm now able to reproduce this issue. It requires power cycling the board after programming firmware. The connect_mode=under-reset option on my feature/connect_mode branch allows you to connect successfully. But there are still questions about what's causing the problem that need to be resolved.

Thanks @flit

Hi
When you connect pyOCD, target is already on I think ?
With latest mbed-os version, target could now is sleep or deep sleep.
So I am wondering how pyOCD can sync with target to attach it during a "wake up" ?
@schstm

Note: mbed-os offers a DEBUG profile that would prevent deep-sleep to be entered and can be used for easy debug.

Update: I'm now able to reproduce this issue. It requires power cycling the board after programming firmware. The connect_mode=under-reset option on my feature/connect_mode branch allows you to connect successfully. But there are still questions about what's causing the problem that need to be resolved.

I'm having the same issue but I cannot find your linked branch anymore.

Closing this issue.
There were two fixes implemented long ago:

PyOCD was failing to abort a stuck transfer.
Implemented the connect_mode option, now accessible via --connect/-M on the command line.

If this is still a problem for anyone, please create a new issue.

Closing this issue.

still opened :-)

Oops, thanks @jeromecoutant :)


Delayed transitions / animations

[ ] Delayed / Staggered (line, bar, etc)
[ ] Bar chart race
[ ] One-to-many line chart transition
[ ] Line transition

D3 path transition

[ ] Animated transition of y-axis scales
[ ] Pie to stacked bar transition
[ ] Scale transition
[ ] Smoother area transitions under a series line
[ ] Animated line chart

The first example is exactly what I am looking for!
What would you say the status is on transitions?

Hey @johanohly 👋, thanks for checking out LayerChart.
Have you seen these examples:

Bar/Column Charts

https://www.layerchart.com/docs/examples/Columns#tween_on_mount
https://www.layerchart.com/docs/examples/Columns#stagger_tween_on_mount
https://www.layerchart.com/docs/examples/Columns#grouped,_stacked,_or_both_(transition)

Area Charts

https://www.layerchart.com/docs/examples/Area#clip_tween_on_mount
https://www.layerchart.com/docs/examples/Area#clip_tween_on_mount

I plan to integrate animations/transitions into the "simplified charts" more (BarChart, LineChart, etc), but you can override slots (such as marks) to accomplish the same thing now.

Oh perfect, I must have missed those examples.
Thank you for creating this awesome library! The amount of examples is (clearly) overwhelming :sweat_smile:

@johanohly Very welcome 😁.  I just added the bar stagger example today (as it was one I hadn't realized was missing).  There is a lot of space to explore with transitions / animations, but definitely have some progress.

I have my area charts animating how I want to, but I can't figure out how to animate a pie chart other than the very basic parameters of CircleClipPath. I preferably want something like this:

https://www.layerchart.com/docs/components/Pie#tweened
More work is planned as well.   https://github.com/techniq/layerchart/issues/120

layerchart.com/docs/components/Pie#tweened
More work is planned as well. #120

Oh, I remember looking at that example and wondering why it wasn't animating or had a button to trigger it. It animates before you scroll down to it when not linked directly, thank you again.

Welcome 😁. Yeah, I need to add a show/hide toggle. Btw I started a branch to improve Pie/Arc animations a few months ago, but never finished as it required more thought on some scenarios.

Added a show/hide toggle for the example.
https://github.com/user-attachments/assets/7c268135-abaa-465a-bbc6-201036a0ead1

Added a show/hide toggle for the example.
CleanShot.2024-10-29.at.08.03.23.mp4

Awesome, this animation is more than sufficient and thanks again for the help!


Missing "Archive..." context menu

I'm running a fresh installation of the mobile development workload in VS 2019 Preview and after creating a new solution with the fabulous-app template, I cannot find a way to create an APK from the Android project. The Archive... context menu is not present on the project (whereas I see it when I create a solution in VS using the standard Xamarin.Forms template) and while I can open the Archive Manager via Tools, there's nothing that would let me start the process there. This is my first time trying Xamarin, so apologies if I'm missing something obvious. Thanks.
I've just noticed that on the Android Manifest tab in project propertie it says it cannot find AndroidManifest.xml even though it's both on disk and in fsproj.

Your issue seems more like a tooling issue in VS 2019.
It's still in early preview for now, and as far as I can tell it has some issues with the Xamarin/F# tooling (for instance, this repo won't open in VS 2019).

Good to know, thank you.


Add association Storage Clusters to Automate Storage Service Model.

Add association Storage Clusters to Automate Storage Service Model.
https://bugzilla.redhat.com/show_bug.cgi?id=1335658
/cc @gmcculloug

👍
cc @jameswnl

Thanks for plugging that 👍


RBAC: Remove the ability to directly assign users and groups to permission policies

What do you want to improve?
With the implementation of Roles in the RBAC plugin, we should remove the ability to directly assign users and groups to permission policies.
What is the current behavior?
Users, groups, and roles can be assigned to permission policies.
What will the new behavior be?
Only roles will be allowed to be assigned to permission policies.

Moving this to close as we are tracking this in Jira


Infer implicit params and apply terms.

don't display correctly symbol names that are backquoted. Should be fixed by this https://github.com/scalacenter/scalafix/pull/1252
don't work for one for types that look like fix.WidenSingleType#strings.type

One more comment. I suggest to rename the explicitResultTypes package in the scalafix/input folder to migrate.


Fixes Empty circuit names

Fixes #851
Describe the changes you have made in this PR -
Empty Circuit names is replaced with Untitled which fixes breaking bar height.
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Coverage remained the same at 84.279% when pulling 74a53f6e791debead0a97ef9c16c714fd5fa77d3 on Shivansh2407:patch-37 into 705506dafa84cf5fe885d2db6b07a5c45ea4eee4 on CircuitVerse:master.

@satu0king Please review and merge 👍


Add OrbStack

Add support for OrbStack ("Fast, light, simple Docker & Linux on macOS")
The tool creates .orbstack and OrbStack directories in $HOME ( 😿 )
Added links to discussions about XDG and directories: https://github.com/orbstack/orbstack/issues/60 & https://github.com/orbstack/orbstack/issues/239

Thanks!


XIVY-10632 db-demo fixing components

merge
start release build
merge release build pr
move story to acceptance


[QUESTION] how can i identify traffic that goes to kinesis video

I'm trying to do some traffic shaping so an offline upload of a file doesn't flood my network connection.
But to create these tc rules i need to know either the destination ip address and/or the ports that are used for uploading.
Is there a default port that gets used ? I noticed the kinesis video end-point is a dns, and apparently it can resolve to multiple ip addresses.. so i'm just wondering what would be the best way to identify kvssink -> kinesis video traffic ..

i did a network capture and it looks like it is a tcp connection to port 443 ? is that right ?

KVS is using HTTP (1.1) with TLS to communicate with AWS and to upload the stream so the ports would be 443. Another issue is the actual IP ports which for streaming can and will be a range and not a preset IP or DNS entry. Before KVS can stream, it should get the endpoint to stream to and that can vary. Perhaps AWS folks can help with the IP ranges I am not sure.

thank you, i've started with re:post, but may escalate it to the support centre if needed.


Improve Rotary Encoder Driver

The rotary encoder sometimes has glitchy behavior. Most probably because of the encoder callback algorithm and debounce. This issue address this problem in the low-level driver of the rotary encoder.

This issue follows up on #41.


[Hub Generated] Review request for Microsoft.Web to add version stable/2020-06-01

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run automation - sdk

/azp run unifiedPipeline

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@andimarc
Is it convenient for you to let reviewer know which commit is for updating/adding API since 2020-09-01?
Also I think 2020-09-01 is not deployed yet.
No registered resource provider found for location 'eastus' and API version '2020-09-01' for type 'serverFarms'. The supported api-versions are '2020-06-01, 2019-08-01, 2018-11-01, 2018-02-01, 2017-08-01, 2016-09-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01, 2014-04-01-preview, 2018-12-01-alpha'. The supported locations are 'southcentralus, msftwestus, msfteastus, msfteastasia, msftnortheurope, eastus2stage, centralusstage, southafricanorth, australiaeast, brazilsouth, southeastasia, centralus, japanwest, centralindia, uksouth, canadaeast, koreacentral, francecentral, northeurope, westus2, westindia, eastus2, australiacentral, germanywestcentral, norwayeast, uaenorth, switzerlandnorth, northcentralus, ukwest, australiasoutheast, koreasouth, canadacentral, westeurope, southindia, westcentralus, eastasiastage, northcentralusstage, eastasia, japaneast, eastus2euap, centraluseuap, westus, eastus'.

@andimarc
Is it convenient for you to let reviewer know which commit is for updating/adding API since 2020-09-01?
Also I think 2020-09-01 is not deployed yet.
No registered resource provider found for location 'eastus' and API version '2020-09-01' for type 'serverFarms'. The supported api-versions are '2020-06-01, 2019-08-01, 2018-11-01, 2018-02-01, 2017-08-01, 2016-09-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01, 2014-04-01-preview, 2018-12-01-alpha'. The supported locations are 'southcentralus, msftwestus, msfteastus, msfteastasia, msftnortheurope, eastus2stage, centralusstage, southafricanorth, australiaeast, brazilsouth, southeastasia, centralus, japanwest, centralindia, uksouth, canadaeast, koreacentral, francecentral, northeurope, westus2, westindia, eastus2, australiacentral, germanywestcentral, norwayeast, uaenorth, switzerlandnorth, northcentralus, ukwest, australiasoutheast, koreasouth, canadacentral, westeurope, southindia, westcentralus, eastasiastage, northcentralusstage, eastasia, japaneast, eastus2euap, centraluseuap, westus, eastus'.

@andimarc
Is it convenient for you to let reviewer know which commit is for updating/adding API since 2020-09-01?
Also I think 2020-09-01 is not deployed yet.
No registered resource provider found for location 'eastus' and API version '2020-09-01' for type 'serverFarms'. The supported api-versions are '2020-06-01, 2019-08-01, 2018-11-01, 2018-02-01, 2017-08-01, 2016-09-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01, 2014-04-01-preview, 2018-12-01-alpha'. The supported locations are 'southcentralus, msftwestus, msfteastus, msfteastasia, msftnortheurope, eastus2stage, centralusstage, southafricanorth, australiaeast, brazilsouth, southeastasia, centralus, japanwest, centralindia, uksouth, canadaeast, koreacentral, francecentral, northeurope, westus2, westindia, eastus2, australiacentral, germanywestcentral, norwayeast, uaenorth, switzerlandnorth, northcentralus, ukwest, australiasoutheast, koreasouth, canadacentral, westeurope, southindia, westcentralus, eastasiastage, northcentralusstage, eastasia, japaneast, eastus2euap, centraluseuap, westus, eastus'.

@panchagnula, @calvinsID - When do we plan to deploy 2020-09-01?

@andimarc
Is it convenient for you to let reviewer know which commit is for updating/adding API since 2020-09-01?
Also I think 2020-09-01 is not deployed yet.
No registered resource provider found for location 'eastus' and API version '2020-09-01' for type 'serverFarms'. The supported api-versions are '2020-06-01, 2019-08-01, 2018-11-01, 2018-02-01, 2017-08-01, 2016-09-01, 2016-03-01, 2015-08-01, 2015-07-01, 2015-06-01, 2015-05-01, 2015-04-01, 2015-02-01, 2014-11-01, 2014-06-01, 2014-04-01, 2014-04-01-preview, 2018-12-01-alpha'. The supported locations are 'southcentralus, msftwestus, msfteastus, msfteastasia, msftnortheurope, eastus2stage, centralusstage, southafricanorth, australiaeast, brazilsouth, southeastasia, centralus, japanwest, centralindia, uksouth, canadaeast, koreacentral, francecentral, northeurope, westus2, westindia, eastus2, australiacentral, germanywestcentral, norwayeast, uaenorth, switzerlandnorth, northcentralus, ukwest, australiasoutheast, koreasouth, canadacentral, westeurope, southindia, westcentralus, eastasiastage, northcentralusstage, eastasia, japaneast, eastus2euap, centraluseuap, westus, eastus'.

@panchagnula, @calvinsID - When do we plan to deploy 2020-09-01?

@andimarc Yes 2020-09-01 is not deployed yet - It's pending a review before I can apply the ARM manifest, and then do an SDK update (Pull request 3700170: Update manifest to include endpoint: /providers/Microsoft.Web/generategithubAccessTokenForAppserviceCLI - Repos (visualstudio.com))

@andimarc Yes 2020-09-01 is not deployed yet - It's pending a review before I can apply the ARM manifest, and then do an SDK update (Pull request 3700170: Update manifest to include endpoint: /providers/Microsoft.Web/generategithubAccessTokenForAppserviceCLI - Repos (visualstudio.com))

@weidongxu-microsoft
I have split up the commits. The second commit  is adding the APIs that are new for API version 2020-10-01.
Also, API version 2020-09-01has been deployed now.

@weidongxu-microsoft
I have split up the commits. The second commit  is adding the APIs that are new for API version 2020-10-01.
Also, API version 2020-09-01has been deployed now.

@weidongxu-microsoft
How can I get the error suppressions in readme.md approved?
Also, can you help me understand why the "SDK azure-sdk-for-go" validation is failing and how I can resolve it?

@weidongxu-microsoft
How can I get the error suppressions in readme.md approved?
Also, can you help me understand why the "SDK azure-sdk-for-go" validation is failing and how I can resolve it?

@ArcturusZhang Please take a look on Go SDK failure. It seems CI problem.
command	sh ./initScript.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
command	go run ./tools/generator/main.go ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"}
HttpError: Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"}
    at /home/vsts/work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/@octokit/request@5.4.9/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async workflowPkgUpdatePR (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflowPackage.js:305:21)
    at async Object.exports.workflowPkgMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflowPackage.js:40:5)
    at async workflowHandleReadmeMd (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflow.js:170:9)
    at async Object.exports.workflowMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflow.js:83:9)
    at async Object.exports.sdkAutoMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/entrypoint.js:152:13)
    at async /home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/cli/cli.js:18:20

@ArcturusZhang Please take a look on Go SDK failure. It seems CI problem.
command	sh ./initScript.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
command	go run ./tools/generator/main.go ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"}
HttpError: Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"}
    at /home/vsts/work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/@octokit/request@5.4.9/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async workflowPkgUpdatePR (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflowPackage.js:305:21)
    at async Object.exports.workflowPkgMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflowPackage.js:40:5)
    at async workflowHandleReadmeMd (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflow.js:170:9)
    at async Object.exports.workflowMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflow.js:83:9)
    at async Object.exports.sdkAutoMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/entrypoint.js:152:13)
    at async /home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/cli/cli.js:18:20

@pilor - Can you please review the new changes I have pushed to address your comments?

@ArcturusZhang Please take a look on Go SDK failure. It seems CI problem.
command	sh ./initScript.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
command	go run ./tools/generator/main.go ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"}
HttpError: Validation Failed: {"resource":"PullRequest","field":"head","code":"invalid"}
    at /home/vsts/work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/@octokit/request@5.4.9/node_modules/@octokit/request/dist-node/index.js:66:23
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async workflowPkgUpdatePR (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflowPackage.js:305:21)
    at async Object.exports.workflowPkgMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflowPackage.js:40:5)
    at async workflowHandleReadmeMd (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflow.js:170:9)
    at async Object.exports.workflowMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/workflow.js:83:9)
    at async Object.exports.sdkAutoMain (/home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/automation/entrypoint.js:152:13)
    at async /home/vsts/work/1/a/unified-pipeline-runtime/private/openapi-sdk-automation/lib/cli/cli.js:18:20

we get this occasionally... usually rerun will fix it.

/azp run

/azp run

/azp run

@jorgecotillo, @pilor - I have pushed new changes addressing your comments.

If CI passes, this PR is good to merge. Let me know when (better be around the time that it onboards).

If CI passes, this PR is good to merge. Let me know when (better be around the time that it onboards).

@weidongxu-microsoft - This can be merged now.


xDnsServerDiagnostics: Added this resource to configure additional diagnostic settings.

Pull Request (PR) description
Added the xDnsServerDiagnostics resource to configure additional diagnostic settings. Tests have been added.
This Pull Request (PR) fixes the following issues
- Fixes #86- Fixes #124

Task list

[x] Added an entry under the Unreleased section of the change log in the README.md.
Entry should say what was changed, and how that affects users (if applicable).
[x] Resource documentation added/updated in README.md.
[x] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[x] Comment-based help added/updated.
[x] Localization strings added/updated in all localization files as appropriate.
[x] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[x] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #90 into dev will decrease coverage by 22.01%.
The diff coverage is 75.75%.

@@             Coverage Diff             @@
##              dev      #90       +/-   ##
===========================================
- Coverage   72.88%   50.87%   -22.02%
===========================================
  Files          10       11        +1
  Lines         520      745      +225
===========================================
  Hits          379      379
- Misses        141      366      +225

Impacted Files
Coverage Δ

...sServerDiagnostics/MSFT_xDnsServerDiagnostics.psm1
0% <ø> (ø)

...MSFT_xDnsServerSetting/MSFT_xDnsServerSetting.psm1
75.75% <75.75%> (ø)
:arrow_up:

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 051cc63...b38c95d. Read the comment docs.


Document the drop address for testing

Hello @brandonmwest,Thanks for your suggestion or question! In an attempt to clear out our backlog,                                              we are closing out issues over 90 days old.                                             If this is still an issue, please feel free to reopen it.                                             Team SendGrid DX-Docs


NavigationView selection change and child items

When changing the selection state through the API, the newly selected item is not always visible, and might sometimes be hidden if it is a child item of a NavigationViewItem.
Should the behavior change in that regard? Should changing the selected item also result in the newly selected item being visible and on screen?
See this PR for more context: https://github.com/microsoft/Xaml-Controls-Gallery/pull/478

This issue has been mentioned in https://github.com/microsoft/microsoft-ui-xaml/issues/2845 and in my opinion should be fixed. I expect the selected item to show up as such in the NavigationView pane.

Sounds like we need to scroll into view the selected item? I think this is what list view does for instance.

Yes in addition to scrolling the selected item into view, we also need to expand the necessary NavigationViewItems, which might be a bit problematic, if the NavigationViewItems don't know their parent items.

When the navigationViewItem raises its selected changed event we can have the parent navigation view expand the tree it is in right?

Yes, the parent NavigationView could or rather should do that. Does the NavigationView know the parent of each of the NavigationViewItems? Is that the same as the VisualTreeParent?

I feel like @ojhad and I had discussed this scenario, but it's been too long and I can't recall the details 😕
I think I was more focused on making each item aware of whether it was expanded or had a selected descendent. I don't believe that we added any such tracking to NavigationView itself. So items have an IsChildSelected property, but no knowledge about their ancestors.
In XCG, we should be able to keep track of the newly selected item's parent and expand the correct subtree using the parent's IsExpanded property. Is there a straight-forward mechanism for bringing the newly-selected item into view? If there is, I think we can fix the strange behavior I was seeing in XCG.

I feel like @ojhad and I had discussed this scenario, but it's been too long and I can't recall the details 😕
I think I was more focused on making each item aware of whether it was expanded or had a selected descendent. I don't believe that we added any such tracking to NavigationView itself. So items have an IsChildSelected property, but no knowledge about their ancestors.
In XCG, we should be able to keep track of the newly selected item's parent and expand the correct subtree using the parent's IsExpanded property. Is there a straight-forward mechanism for bringing the newly-selected item into view? If there is, I think we can fix the strange behavior I was seeing in XCG.

UIElement.BringIntoView() should do the trick.  I think this is a bug in NavView though, I feel like you shouldn't need to call that.

@ranjeshj @StephenLPeters Would you be fine with me working on this issue?

That would be great @chingucoding !

I think we need to rethink this a bit more. If an item has not been realized (which is the case quite often as we might recycle them), the NavigationView and the NavigationViewItems are disconnected meaning that you can tell either side that the NVI is selected, yet beside saying "yup the NVI is selected", they can't do much more.
We have no fast way to determine the parent of a NVI. We could ask every on level 0 if they have their children selected, and ask the one with a selected child which of it's children is selected, and so on, but this would be quite expensive.
So the question now is how do we deal with this? When items are not realized, APIs like FrameworkElement.Parent don't work.
No matter what solution we might choose, it will probably require a lot of work. We will need to tell every NVI (realized or not) what NavigationView or NavigationViewItem it reports to in case of selection change, and similarly, the NavigationView or NavigationViewItem needs to be able to get a path of all NavigationViewItems from layer 0 down to the selected item.

Trying to catch up to this conversation. Is the intention that the selected item should always visible.  This is currently not possible through the UI, since you have to bring the item into view in order to select it but possible if done programatically (like the case you mention with search)
Changing selection programmatically causing expanding and bringing items in view sounds a like a lot of side effects. I wonder if this needs to be a separate API  (like RealizeAndBringIntoView that takes a dataItem or a NVI). That way you can programmatically set selection and optionally bring that into view.
There are two different issues being discussed if I understand correctly.

What happens when you programmatically select an item that is not under a fully expanded tree.
Should currently selected item (or its parent) be always visible.

For (1) If a child is programmatically selected, selection model should reflect that and the parent chain should react appropriately. If the child is collapsed, the parent will show as selected (same as what happens when you manually select a child and collapse its parent). If the child is not in the parent chain, we should update it when that child enters the tree, not when the IsSelected property changes (since we don't know the child's index path to update selection model)

That's a very good point you are raising here. Changing selection should probably not have those side effects. Having a separate API for this is probably the better solution here, that way we don't force so many UI updates on simple operations such as selection change.
Regarding the IsSelected what would the expected behavior for #3149 be then? Only update the SelectedItem once that item get's added to the visual tree? What if multiple items with IsSelected set to true show up in the visual tree? Is it a first come first serve or will the latest that has IsSelected set to true be the selected item?

@ranjeshj

Should currently selected item (or its parent) be always visible.

What definitely should work is the following issue: https://github.com/microsoft/microsoft-ui-xaml/issues/2814
I would look into that issue but it seems to me @chingucoding is also focusing on that area for now and he perhaps plans to fix that.

This issue and #2814 are orthogonal I think and have little overlap. Given that this issue might need a bit more consideration, I would say, feel free to work on #2814 .

@Felix-Dev I agree that #2814 is a bug and likely orthogonal to this. After switching to top, the parent should show selected. If we are using the same selection model, I wonder why it does not show up selected already. In any case, that sounds like a bug.
@chingucoding  I would say last one with IsSelected=true added to the tree wins. That is likely the simplest to implement and likely cover most scenarios. @anawishnoff and @YuliKl  can pitch in if they feel otherwise.

I would say last one with IsSelected=true added to the tree wins.

@ranjeshj I'm sorry, I'm not quite following. What do you mean by the last item added to the tree?

The last item added to the tree would essentially mean, the last item we got to render. For example:

Item 1
Item 2 (Collapsed)

Item 3 (IsSelected=true)
Item 4
Item 5 (IsSelected=true)

If we expand Item 2, the last item added to the tree with IsSelected=true would be Item 5, thus this will be the selected item. All other items which have IsSelected item set to true will be ignored.

Oh, I see, thank you for the explanation @chingucoding! NavigationView doesn't support multiselect as a concept, but IsSelected is a property on the item and we're not enforcing any sort of exclusivity.
Yes, this approach sounds good to me.

@Felix-Dev I assume you would like to work on #2814 right? To prevent merge conflicts, would you like me to wait with #3149 or would you like to tackle that too?

Oh, I see, thank you for the explanation @chingucoding! NavigationView doesn't support multiselect as a concept, but IsSelected is a property on the item and we're not enforcing any sort of exclusivity.
Yes, this approach sounds good to me.

I think we do enforce exclusivity, but we can't while the item is not realized.  Both of these elements are getting realized at the "same" time and thus we have to pick one.   So in Marcel's case the IsSelected property of Item3 would be set to false.  @chingucoding to make sure I'm remembering this correctly?

Setting IsSelected on multiple items in XAML leaves us with the multiple items having IsSelected set to true. The same does not happen if you set IsSelected to true on multiple items. In that case it's last man standing. So in the example, as Stephen correctly said, we would set IsSelected to false on Item3.

@chingucoding

I assume you would like to work on #2814 right? To prevent merge conflicts, would you like me to wait with #3149 or would you like to tackle that too?

Hmm, for #2814, at least in data-binding mode, I would also need to find the top-level parent of a selected child (as only the top-level parent is shown in the pane).
So if I have something like this:

Item 1
[...]
Item 10 (in overflow menu in Top mode typically)

Item 10.1 (selected)

and then switch from Left mode to Top pane display mode, I need to show Item 10 as the right-most top-level item right left to the overflow menu.
I could iterate through the NavViewItem containers available and check if they are a top-level item and if NavVigationViewItem.IsChildSelected is true. But...what happens if virtualization kicks in and there are currently no Item containers for Item 10 and its child Item 10.1? I'm not sure right now how to show Item 10 in the Top pane then as I have no item container to work with here.
Reading through the discussion here, I believe the same problem is being discussed here:

For (1) If a child is programmatically selected, selection model should reflect that and the parent chain should react appropriately. If the child is collapsed, the parent will show as selected (same as what happens when you manually select a child and collapse its parent). If the child is not in the parent chain, we should update it when that child enters the tree, not when the IsSelected property changes (since we don't know the child's index path to update selection model)

It appears to me whatever is decided here and for issue#3149 would also apply to how issue #2814 will be handled then. As such, if I'm not mistaken, I think issue #2814 should be handled together together with these issues you have reported.

I am not sure if I correctly understood the issue, but let me try to recap here:
When switching from left to top, we would like the top most parent of the selected item be present in the list of visible items and be selected And for that to work, we need to figure a way out to find the parent of a selected item which might not be realized.
Regarding Item 10 not being realized, you can "force" create that item, after all we NEED that to be realized if we want to show it being selected. And given that the overflow menu already seems to have some logic in that regard, I think this is not the difficult part of #2814 .
The main pain point I see here is that for unrealized items, we don't really have a way to link them to their parent. They are not aware of their parent NavigationView nor their parent NavigationViewItem.
I totally agree with your assessment that we those probably need to be tackled together. However I currently don't know how we would fix this issue with the unknown parents. Realizing all items to walk their children, and their children and so on, doesn't sound that good of a idea as this could be very expensive if we are talking about hundred of items.


req.route is assigned the correct middleware if multiple are present

closes #407

@talentlessguy

there seems to be a coverage decrease, is it related to the PR?


Static websites hosting policy

Rendered
cc @rust-lang/infra

@shepmaster added the rationale for each of the requirements.

Addressed all the comments from Alex and added a new section on fixing GitHub Pages redirects when it sits behind CloudFront.

@rfcbot fcp merge

Are the people who want the website supposed to do all of the deploy steps themselves?

Nope, clarified the steps are meant to be executed by a member of the infra team.

@rfcbot reviewed

We got most checkboxes, so merging this!


Update to jdk 22

The foreign API is finally out of preview in jdk 22, which would make it a more desirable target than 21
https://openjdk.org/jeps/454
Is there any plan to update?

Since I'm not actively using rapier or rapier-ffi anymore, I'm not really working on this repo anymore. At the time that I wrote this code, Java 21 wasn't out yet, and I couldn't use Java 20 because of my environment setup, so I was stuck with 19.
However, this shouldn't be too hard to update to Java 21 (I would prefer 21 instead of 22 since 21 is an LTS, unless I'm misunderstanding how preview features work?). Most of the work to update from 19 to 21 is just manually replacing MemorySession with Arena iirc. I would accept a PR that updates it, you could probably even just pass it through an AI and get it to do the replacement. The entire build process with the Gradle scripts is admittedly hacky, but I think it should still work. Haven't tested it in a while though.
Even if rapier-ffi itself is updated, Rapier's probably a few versions ahead by now, so eventually that would need to be updated as well, but that's a conversation for a different issue.

JDK 22 is IMO more desirable than 21. Preview features require explicit enabling and are likely to change across versions (in this case, would only work on jdk 21 and nothing else). Not much point using LTS for an outdated API.
Hope somebody can come around and do the updating.

I might try to update it so my fork of rattle to support minecraft 1.21.4 can be not imposible


"Berindești" is listed in the drop-down menu

Description:
"Berindești" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Berindești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Berindești, Argeș (Corbeni)".


[Usage]: Why is the useage information missing in the streaming call. Not streaming is there.

Your current environment
data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"role":"assistant"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"我是"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"阿里"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"云"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"开发"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"的一款"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"超"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"大规模"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"语言"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"模型"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"，"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"我"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"叫"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"通"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"义"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"千"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"问"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":"。"},"logprobs":null,"finish_reason":null}]}

data: {"id":"cmpl-840312ff78664572bb504e606140b952","object":"chat.completion.chunk","created":1719969577,"model":"Qwen-v","choices":[{"index":0,"delta":{"content":""},"logprobs":null,"finish_reason":"stop","stop_reason":null}]}

data: [DONE]

How would you like to use vllm
I want to run inference of a [specific model](put link here). I don't know how to integrate it with vllm.

You should pass stream_options={"include_usage": True} to include usage information in the streaming output.

All right, thank you very much.


Refactor CreatesNewPublicationPage action to use the existing YAML converter

This is gonna need some normalizing https://github.com/hydephp/develop/commit/d55d6e3babe47ed0b1d52ba9366340dc91ca388d


Added 2 new generator fucntions for the Tribonacci Series

Created 2 new generator for the Tribonacci Series

tribonacci_series
nth_tribonacci_number

Thanks!


How to get Cloud Storage usage?

Is it possible to somehow get the data usage of GCS?
I am looking at the Cloud Monitoring class, but it seems to be based on the older API (v2) and even if that version can do it, I'm unsure how to get it working.
I want to be able to see how much space is being used in total, maybe with the billing cost?

See The Storage FAQ for an answer to this question:

How can I get a summary of daily space usage?
You can use the gsutil du command to display the total space used by all objects for a specified bucket. For example, to get the total space used by all objects in the bucket "bucketname", use the command:
gsutil du -sh gs://bucketname

See the du command help for more options you can use, including how to return the size of all objects underneath a prefix.
You can also set up bucket logging where the total size of a bucket is automatically reported once a day. For more information, see Access Logs & Storage Data. If the number of objects in your bucket is large (e.g., hundreds of thousands or millions), this is a much more efficient way to track space usage. The gsutil du command calculates space usage by making bucket listing requests, which can take a long time for large buckets.

So, no way other then using command line?

Do you know of any way what-so-ever to do this via PHP?

Please note that this issue tracker is only for this client library. We do not maintain the APIs that this client library talks to. If you have an issue or questions with how to use a particular API, you are better off posting on Stackoverflow under the google-api tag.
That being said, you could try using the JSON API to pull down the access logs and derive your usage from there.


UriEndpoint should override ToString

It's ToString() should return Uri.ToString()

Hi, first timer here looking at first issues.  Where exactly is the ToString that should be converted?  How do you see?

This is already done (see https://github.com/aspnet/AspNetCore/pull/12668), @halter73 forgot to close the issue 😄

ok thanks.  Just wondering, how did they see where the code was to change?

ok thanks. Just wondering, how did they see where the code was to change?

You could search the codebase for UriEndPoint.cs. In this particular case, #12668 and #14384 were both earlier attempts to address this issue, so you can take a look for how this was fixed.

Good point.  Thank you!


How to add too tip to datatable header columns

I'm submitting a ...  (check one with "x")
[X] bug report => search github for a similar issue or PR before submitting
**Current behavior**

Hi Team ,

Could you please let me know how to add tool tip to the header columns in the data table. Is there any specific directive to perform this action ?

Below is my configuration for one of the columns .

 <ngx-datatable-column name="Sent" width="80" [cellClass]="custDatatableHeader">
          <ng-template let-row="row" let-expanded="expanded" ngx-datatable-cell-template>
             {{row?.cdaSentCnt}}
          </ng-template>
 </ngx-datatable-column>

May i have any update on this please?

Resolved with ngx-datatable-header-template syntax.


[login sso] Ensure that the RepoConfig Directory and file exists before writting team ID and API url

Edge case on new repo when .turbo/config.json doesn't exist.
Normally the .turbo/config.json would be written on yarn turbo link.
yarn turbo link is not applicable after logging in to an --sso-team

>   Waiting for your authorization...
>>> Success! Turborepo CLI authorized for<EMAIL_ADDRESS>
Error: failed to save teamId: open .turbo/config.json: no such file or directory
Usage:
  turbo login [flags]

Flags:
  -h, --help              help for turbo
      --sso-team string   attempt to authenticate to the specified team using SSO

 ERROR  failed to save teamId: open .turbo/config.json: no such file or directory
error Command failed with exit code 1.


asm-cli display unusual

OS : Linux VM-0-6-ubuntu 4.4.0-91-generic #114-Ubuntu SMP Tue Aug 8 11:56:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
build asm-cli go version : go version go1.12.9 linux/amd64
Press the backspace key after the prompt is displayed register info disappear

汗😓
我也不知道咋回事，要不试试换个shell，比如zsh之类的

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @ZeroKill1024, @hongmaoxiao, @fishjar, @GaiheiluKamei, @jqrj, @zhendexuebuhui, @shidongjian, @Nibnahsoaix, @Hao-Wu, @

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!arriqaaq, @Dadiselef20, @SpecIRK, @Nicojohnzz, @latermaeseus, @ajaberi6868, @bianchiso, @marian1223, @Mirtah69, @derekbar90, @orcomdoritaieh, @remsorunu, @crocodilly, @maciusbrudzewski, @KursatCAKAL, @EricRektitude, @BhavikSojitra, @Chidubemkingsley, @nainglinn82, @CF119

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

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

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
OmidCandy, @Yusufali77, @didiclubbbbb, @JosepBove, @Realmrd, @earnings4all, @0xMelkor, @Tyronedill99, @Maddiaa0, @Fwlla7, @rangerss77, @mutjan, @Questan-t, @Paxosgold, @db0x0db, @HoseinNikmaramOfficial, @murka, @thameengal, @khongkroma, @ssutingh

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

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

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
streaps, @cliffordscott, @gatecrasher777, @ctfarrell, @echowill, @3Elijah, @JoaquimEsteves, @Flavio0834, @GrapeBaBa, @thinkhero, @unkletayo, @toto, @fekie, @Chris-Baker, @treyceraso, @sebpalluel, @ednhmn, @73muz, @Pranit-02, @robertmarsal


[$1000] Split bill - Contacts section is hidden when selecting a user from the recents section

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

Action Performed:

Click on Add button
Click on split bill
Select user from Recent section
Unselect user from selected list

Expected Result:
Contacts section below recent section should be visible all the time
Actual Result:
When selecting a user from the recent section, contacts sections hides and after unselecting a user contacts section again visible
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

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

[x] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/235689286-d6453281-7eee-4aa4-af2f-0c8c9ad2bf1d.mp4
https://user-images.githubusercontent.com/43996225/235689312-0000b3e1-4fbc-4dc9-87f4-64456166bf77.mp4
Expensify/Expensify Issue URL:
Issue reported by: @jaydipramani
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1682784313391979
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~019fa0e3244439fb8a
Upwork Job ID:<PHONE_NUMBER>181461504
Last Price Increase: 2023-05-03

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Proposal
Please re-state the problem that we are trying to solve in this issue.
Recents section in split bill is not consistent with the new group Recents section where the selection of the options from it doesn't reduce the number of options from it.
What is the root cause of that problem?
For getting the data for these sections(Recents, Contacts) by toggling the option we are passing the selected options, which will return the new data excluding the selected options. So each time we are having the new 5 options for the Recent section and it doesn't reduce the numbers on a selection of the options as all are new entries(unselected).
https://github.com/Expensify/App/blob/200ca8591b8c342718f1a7ab3ff4296270783f42/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js#L201
What changes do you think we should make in order to solve the problem?
To make it consistent with the newGroup page we need to make the same steps that we have in there.

Pass an empty array here instead of passing the selected options to get the same Recents data all the time
https://github.com/Expensify/App/blob/200ca8591b8c342718f1a7ab3ff4296270783f42/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js#L201
https://github.com/Expensify/App/blob/200ca8591b8c342718f1a7ab3ff4296270783f42/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js#L152

In the getSections, filter out the sections data based on selected participants like the same way we did for newGroup page.
https://github.com/Expensify/App/blob/200ca8591b8c342718f1a7ab3ff4296270783f42/src/pages/NewChatPage.js#L103-L105

const filterText = _.reduce(this.props.participants, (str, {login}) => `${str} ${login}`, '');
const recentReportsWithoutSelected = _.filter(this.state.recentReports, ({login}) => !filterText.includes(login));
const personalDetailsWithoutSelected = _.filter(this.state.personalDetails, ({login}) => !filterText.includes(login));

With that pass these variables to the respective sections data.

Job added to Upwork: https://www.upwork.com/jobs/~019fa0e3244439fb8a

Reproduced and opened up.

Current assignee @garrettmknight is eligible for the External assigner, not assigning anyone new.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @Santhosh-Sellavel (External)

Triggered auto assignment to @yuwenmemon (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@Santhosh-Sellavel can you see if the proposal we received before this was open works?

@garrettmknight Sorry I missed there was a proposal earlier before the external label.
Can you reproduce this issue? I am unable to
https://user-images.githubusercontent.com/85645967/236538181-481091dd-3078-4246-b504-bffa295a8146.mov

@Santhosh-Sellavel it seems in your case only 2 items are there in Recents but if you have 10 items for example then this issue can be seen where Recent numbers won't be decreased on selection and show again 5 rows with a new option.

@garrettmknight @yuwenmemon
This is not a bug, it's behavior by design. We show 5 recent users always on the list when selecting one of the users from Recents Next Recent users are added to the recent section from the contacts section thus hiding the Contacts section itself only when the users count is when between 5-10 users. But for more users, this will be useful.

Ah, that makes sense. Confirmed the behavior and closing!


Why?

Only really useful if you're trying to migrate from axios to the fetch

It might be helpful to indicate why someone would be inclined to make this migration. At least, as a sample of 1, count me as curious.

Greetings!  We were originally using axios, but created this for a few reasons:

Axios has been relatively unmaintained recently
It didn't support proxy support out of the box
It didn't support retry out of the box
It duplicated a lot of client side logic we just didn't need here

Axios is a great library, but we wanted something built on the much lighter node-fetch.  Hope this helps!


Unknown field 'fields' on type 'File!'.

hi,
i just downloaded your site after reading your article about Modal in React.
i followed the instructions, and when i run it as a fresh install i get:
error GraphQL Error Encountered 1 error(s):
- Unknown field 'fields' on type 'File!'.

      file: /usr/local/projects/aa_working/Active/janosh.io/src/pages/nature.js

certainly not a big deal on this end, but if you think of what i might be, let me know.
Thanks,
m

Same for me. Having the same error on a lot of non static queries just lately. Sure wish I could figure it out.

Unknown field 'fields' on type 'File!'.

That's interesting. Thanks for letting me know. I can't reproduce that error on my end. One thing I can think of that might be causing this issue is that exports.onCreateNode in gatsby-node.js should really be an asynchronous function awaiting the fs.readFile call, which might only cause problems on machines with slower file system access.
Could you try to replace exports.onCreateNode with the following code snippet and let me know if that has any effect?
exports.onCreateNode = async ({ node, actions }) => {
  if (node.dir && node.dir.includes(`content/photos`) && node.ext === `.jpg`) {
    await fs.readFile(node.absolutePath, async (err, data) => {
      if (err) throw err
      const tags = ExifReader.load(data.buffer)
      const meta = {
        lat: tags.GPSLatitude.description,
        lng: tags.GPSLongitude.description,
        caption: tags.Headline.description,
      }
      await actions.createNodeField({
        node,
        name: `meta`,
        value: meta,
      })
    })
  }
}

Ignore what I wrote above. After running gatsby clean followed by gatsby develop I was able to reproduce the problem. So maybe that error only shows up when running gatsby develop with a clean cache, since on the second try it simply fetches the results of the async calls to fs.readFile from the first run where they didn't finish in time.
In any case, I was able to fiddle with the problem locally now and awaiting fs.readFile seems insufficient. However, refactoring to fs.readFileSync as follows solves the problem.
exports.onCreateNode = ({ node, actions }) => {
  if (node.dir && node.dir.includes(`content/photos`) && node.ext === `.jpg`) {
    const buffer = fs.readFileSync(node.absolutePath)
    const tags = ExifReader.load(buffer)
    const meta = {
      lat: tags.GPSLatitude.description,
      lng: tags.GPSLongitude.description,
      caption: tags.Headline.description,
    }
    actions.createNodeField({
      node,
      name: `meta`,
      value: meta,
    })
  }
}

Either replace exports.onCreateNode in gatsby-node.js with the above snippet or do a git pull in the coming days as I'll be pushing this fix soon.
I'll close this issue but feel free to reopen if questions/problems remain.

Thank You
Very Excellent Work!
Will wait for the Update.
Donald Boulton

I just pushed the fix. Merged into master by #55.

Tested the changes after adding fs-extra as fs will not install properly on a Windows machine. You get
"fs": "^0.0.1-security",
Which you want in your package.json to reference fs to fs-extra, as
 "fs": "^0.0.1-security",
 "fs-extra": "^7.0.1",
I installed fs-extra and then changing gatsby-node.js to
const fs = require(fs-extra)
By adding fs-extra, all references to fs are somehow taken over by fs-extra.
After fixing the fs issue it built correctly.

@donaldboulton Glad to hear it!


authy-devise adds a  call to warden.authenticate? before all application actions

In a recent project I have two classes of users, one who signs in only via an API (users) and one who signs in via a browser (admins). I had stopped warden from storing current_users in the session, but adding authy-devise, even though it was only added for admins, still broke this. It's because https://github.com/authy/authy-devise/blob/87731bec3e6bd5ecd84aa174bacec15da1f24687/lib/devise-authy/rails.rb does:
    ActiveSupport.on_load(:action_controller) do
      include DeviseAuthy::Controllers::Helpers
    end

and that calls
included do
  before_action :check_request_and_redirect_to_verify_token, :if => :is_signing_in?
end

and :is_signing_in? calls the devise helper signed_in? which will authenticate with warden and store it in the session 😞
This is a pain point in devise that is not unique to this gem, but could we solve some of it in this scenario by removing the attempt to verify in the following method?
      def is_signing_in?
        if devise_controller? && signed_in?(resource_name) &&
          is_devise_sessions_controller? &&
          self.action_name == "create"
          return true
        end

        return false
      end

It seems like it should be unnecessary since check_request_and_redirect_to_verify_token is implemented as:
      def check_request_and_redirect_to_verify_token
        if signed_in?(resource_name) &&
           warden.session(resource_name)[:with_authy_authentication] &&
           require_token?
          # login with 2fa
          id = warden.session(resource_name)[:id]

          remember_me = (params.fetch(resource_name, {})[:remember_me].to_s == "1")
          return_to = session["#{resource_name}_return_to"]
          sign_out

          session["#{resource_name}_id"] = id
          # this is safe to put in the session because the cookie is signed
          session["#{resource_name}_password_checked"] = true
          session["#{resource_name}_remember_me"] = remember_me
          session["#{resource_name}_return_to"] = return_to if return_to

          redirect_to verify_authy_path_for(resource_name)
          return
        end
      end

FWIW, I personally got around this by implementing the following in my ApplicationController:
  def is_signing_in?
    if request.format.json?
      false
    else
      super
    end
  end

YMMV.

Hi!
I know this issue is from a long time ago, but I took over maintaining the library a couple of months ago and I want to address all the open issues.
I understand that you fixed this for yourself by over-riding is_signing_in? but I wanted to understand the overall issue.
Is it that signed_in?(resource_name) is called twice, in both the guard is_signing_in? and the before_action check_request_and_redirect_to_verify_token?
In your case, would is_signing_in? shortcut out for one of the other conditionals; devise_controller?, is_devise_sessions_controller? or self.action_name == "create"?
So, would removing signed_in?(resource_name) from is_signing_in?, but keeping it as part of check_request_and_redirect_to_verify_token fix this for you and allow you to remove your own defined is_signing_in??
Thanks!

Hey, I appreciate you addressing this. I haven't dealt with this project/devise since around the time I raised this issue, so my instinct might be off, but I believe you hit upon what my preferred solution was - don't called signed_in? in is_signing_in?. If that causes other issues elsewhere I have no idea, but it made sense to me at the time 😄
Again, thanks for maintaining this, let me know if I can add anything else!

I think you're right, just wanted to make sure too! Will try to get this fix into the library when I find a bit of time.
I don't know if it'd be possible, but would be great if you were able to test the updated version within your app? I don't have anything set up that doesn't expect current_user to be set for part of the app.


use release-2.6 clusterimageset

Signed-off-by: ldpliu<EMAIL_ADDRESS>https://github.com/stolostron/backlog/issues/23927

/cc @KevinFCormier


Anne flix kevin

Setting of b.e for fetching movies for a specific category

Setting up b.e for fetching movies for a specific category


Clean up some removed options

The base glance-api.conf template file includes some options which were already removed. This removes these options to make the file clean.

/ok-to-test


[10.x] Standardise prohibited rules

Problem
The prohibited rules are inconsistent from an implementation and documentation point of view. Not only does the documented definition of "prohibited" change on a rule by rule basis, sometimes the implementation does not match the intended documented functionality of the rule iteself.
Definition of present
We need to make sure we are on the same page about how I'm using the word "present". I'm using this only in relation to the key, i.e. present = exist.
Intended definitions

The key must not be present in the payload.
The key may be present. If it is present it must be an empty string. An empty string may contain whitespace (tabs / spaces, new lines, etc).

The parts of the docs that back up these definitions are:

... may not be present ...
prohibited rule

... no fields in anotherfield can be present, even if empty ...
prohibits rule

... must be an empty string or not present ...
prohibited_if rule + prohibited_unless rule

Implemented definitions
To show these definitions via tests, the following currently pass. The first array is are the rules. The second array is the data. The third boolean is if the validation passes:
// prohibited...
[['p' => 'prohibited'], [], true],
[['p' => 'prohibited'], ['p' => ''], true],
[['p' => 'prohibited'], ['p' => ' '], true],
[['p' => 'prohibited'], ['p' => null], false],
[['p' => 'prohibited'], ['p' => []], false],
[['p' => 'prohibited'], ['p' => $emptyCountable], false],
[['p' => 'prohibited'], ['p' => 'foo'], false],

// prohibited_if...
[['p' => 'prohibited_if:bar,1'], ['bar' => 1], true],
[['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => ''], true],
[['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => ' '], true],
[['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => null], true],
[['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => []], true],
[['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => $emptyCountable], true],
[['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => 'foo'], false],

// prohibitedIf...
[['p' => new ProhibitedIf(true)], [], true],
[['p' => new ProhibitedIf(true)], ['p' => ''], true],
[['p' => new ProhibitedIf(true)], ['p' => ' '], true],
[['p' => new ProhibitedIf(true)], ['p' => null], false],
[['p' => new ProhibitedIf(true)], ['p' => []], false],
[['p' => new ProhibitedIf(true)], ['p' => $emptyCountable], false],
[['p' => new ProhibitedIf(true)], ['p' => 'foo'], false],

// // prohibited_unless...
[['p' => 'prohibited_unless:bar,1'], ['bar' => 2], true],
[['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => ''], true],
[['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => ' '], true],
[['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => null], true],
[['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => []], true],
[['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => $emptyCountable], true],
[['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => 'foo'], false],

// // prohibites, with "p" values...
[['p' => 'prohibits:bar'], [], true],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => ''], true],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => ' '], true],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => null], false],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => []], false],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => $emptyCountable], false],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => 'foo'], false],

// prohibites, with "bar" values...
[['p' => 'prohibits:bar'], ['p' => 'foo'], true],
[['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => ''], false],
[['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => ' '], false],
[['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => null], false],
[['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => []], false],
[['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => $emptyCountable], false],
[['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => 'foo'], false],

These test show the following:
"prohibited"
Documented
The field under validation may not be present.
Actual
The field under validation may not be present.
✅ Documentation and implementation match
✅ Implementation correct
📌 Baseline for definition of "prohibited"
"prohibited_if"
Documented
The field under validation must be an empty string or not present if the anotherfield field is equal to any value.
Actual
The field under validation must be an empty string, null, an empty array, an empty countable object, or not present if the anotherfield field is equal to any value.
❌ Documentation and implementation do not match
❌ Definition of prohibited does not match "prohibited" rule.
Rule::prohibited(true)
Documented
This is a paraphrased version of the docs, to account for the closure resolution:
The field under validation must be an empty string or not present if the closure / value evaluates to true.
Actual
The field under validation must be an empty string or not present if the closure / value evaluates to true.
✅ Documentation and implementation match
✅ Definition of prohibited does not match "prohibited" rule.
❌ Implementation does not match the string based "prohibited_if" rule.
"prohibited_unless"
Documented
The field under validation must be an empty string or not present unless the anotherfield field is equal to any value.
Actual
The field under validation must be an empty string, null, an empty array, an empty countable object, or not present unless the anotherfield field is equal to any value.
❌ Documentation and implementation do not match
❌ Definition of prohibited does not match "prohibited" rule.
"prohibits"
Documented
If the field under validation is present, no fields in anotherfield can be present, even if empty.
Actual
If the field under validation is present and not an empty string, no fields in anotherfield can be present, even if empty.
❌ Documentation and implementation do not match
❌ Definition of prohibited does not match "prohibited" rule (because the other key is not allowed to be an empty string).
Proposed solution
I feel in Laravel 10.x we should, at a minimum, standardise what being "prohibited" means: If a field is prohibited, the field must not be present in the payload or its value must be an empty string.
Implemented with https://github.com/laravel/framework/pull/45716/commits/47727dc40311c442fc4a3ef41d595ef809735c75. This results in the following test changes:
// prohibited...
[['p' => 'prohibited'], [], true],
[['p' => 'prohibited'], ['p' => ''], true],
[['p' => 'prohibited'], ['p' => ' '], true],
[['p' => 'prohibited'], ['p' => null], false],
[['p' => 'prohibited'], ['p' => []], false],
[['p' => 'prohibited'], ['p' => $emptyCountable], false],
[['p' => 'prohibited'], ['p' => 'foo'], false],

// prohibited_if...
[['p' => 'prohibited_if:bar,1'], ['bar' => 1], true],
[['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => ''], true],
[['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => ' '], true],
- [['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => null], true],
- [['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => []], true],
- [['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => $emptyCountable], true],
+ [['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => null], false],
+ [['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => []], false],
+ [['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => $emptyCountable], false],
[['p' => 'prohibited_if:bar,1'], ['bar' => 1, 'p' => 'foo'], false],

// prohibitedIf...
[['p' => new ProhibitedIf(true)], [], true],
[['p' => new ProhibitedIf(true)], ['p' => ''], true],
[['p' => new ProhibitedIf(true)], ['p' => ' '], true],
[['p' => new ProhibitedIf(true)], ['p' => null], false],
[['p' => new ProhibitedIf(true)], ['p' => []], false],
[['p' => new ProhibitedIf(true)], ['p' => $emptyCountable], false],
[['p' => new ProhibitedIf(true)], ['p' => 'foo'], false],

// // prohibited_unless...
[['p' => 'prohibited_unless:bar,1'], ['bar' => 2], true],
[['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => ''], true],
[['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => ' '], true],
- [['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => null], true],
- [['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => []], true],
- [['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => $emptyCountable], true],
+ [['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => null], false],
+ [['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => []], false],
+ [['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => $emptyCountable], false],
[['p' => 'prohibited_unless:bar,1'], ['bar' => 2, 'p' => 'foo'], false],

// // prohibites, with "p" values...
[['p' => 'prohibits:bar'], [], true],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => ''], true],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => ' '], true],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => null], false],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => []], false],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => $emptyCountable], false],
[['p' => 'prohibits:bar'], ['bar' => 2, 'p' => 'foo'], false],

// prohibites, with "bar" values...
[['p' => 'prohibits:bar'], ['p' => 'foo'], true],
- [['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => ''], false],
- [['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => ' '], false],
+ [['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => ''], true],
+ [['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => ' '], true],
[['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => null], false],
[['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => []], false],
[['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => $emptyCountable], false],
[['p' => 'prohibits:bar'], ['p' => 'foo', 'bar' => 'foo'], false],

These changes are breaking but in my eye they are really bug fixes, but I've targeted 10.x to be cautious.
Related: https://github.com/laravel/framework/pull/45717

@taylorotwell please check the updated docs to make sure that is what you would expect: https://github.com/laravel/docs/pull/8462
The "prohibits" rule feels a little trickier than the "prohibitied*" rules. I do think this makes it consistent with our definition of what it means for an input to be prohibited.


Switching pages creates URL variation allowing linking directly to a page

[x] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
I have a diagram with multiple pages. I want to show a specific page to a colleague, by giving them a URL to click on. When they open the URL, I want the specific page to be seen. This should be easy and obvious.
Describe the solution you'd like
As with Google Sheets, changing between pages in a diagram should change the hash of the URL to a unique value. Opening that URL should show the corresponding page on open.
For backwards compatibility, existing hashes could be used, and appended with an additional, optional page identifier. For robustness, this page identifier should be a unique ID (seems to already exist and be shown when hovering page tabs), NOT the page number or page name.
For example, my current diagram shows the URL in the address bar:
https://app.diagrams.net/#G1ObcHXNSnnJfulSxYk7ez-swW8maLWk3n
When switching to a different page, the hash in the address bar would change to:
https://app.diagrams.net/#G1ObcHXNSnnJfulSxYk7ez-swW8maLWk3n-Z8_XMVzUDMBFWBjzSCSS
...where Z8_XMVzUDMBFWBjzSCSS is the hash seen in the title attribute for that page.
Describe alternatives you've considered
A feature-creep to the feature would be to allow linking by page number or page title, in addition to the default behavior of link-by-hash, if desired. For example:

Link by hash: https://app.diagrams.net/#G1ObcHXNSnnJfulSxYk7ez-swW8maLWk3n-Z8_XMVzUDMBFWBjzSCSS
Link by number: https://app.diagrams.net/#G1ObcHXNSnnJfulSxYk7ez-swW8maLWk3n-2
Link by title: https://app.diagrams.net/#G1ObcHXNSnnJfulSxYk7ez-swW8maLWk3n-Camera%20FoV

These two additional options would not be exposed by default, but could be options in the current "Link..." dialog?
Additional context
I understand the "Link..." feature for sharing the current state of the document via URL. I do not want this, but instead want to always share the latest version. A live link to edit the document, jumping to the correct page.

See https://www.diagrams.net/doc/faq/supported-url-parameters, page and page-id parameters.

Or try "Link" in the page context menu:

I appreciate that there are ways (some of which I did not know) to create a page link.
The intention of this request odd to make it so that switching pages changes the URL so that copy/paste links straight to the page. Like Google Sheets does with tabs.

The pageID is stored in the URL when the diagram is saved.


[PE-D][Tester D] Enumeration of features is not hyperlinked

It seems that the table listing the features in the User Guide, as shown in the screenshot below, is meant to be hyperlinked but it is not.

Labels: severity.Low type.DocumentationBug
original: parth-io/ped#10

This issue has been fixed in the above PR, the hyperlinks have been added to improve navigability.


Update User-defined type REFERENCES permission

@JuergenHorn : Thanks for your contribution! The author, @edmacauley, has been notified to review your proposed change.

Thank you for that edit, @JuergenHorn. #sign-off


Implement 'Generating' screen

https://github.com/ioxiocom/ioxio-tags/assets/137529618/b43e52d5-e49a-4e5e-ae44-13083d737911

Input becomes half-disabled on generating. Yeah I see in designs it still not grey in this state, but I guess it's the mistake in designs. Can't imagine why should we have checkbox active while other things in the form are disabled

Selected half of the toggle doesn't change on generating. From the user perspective feels a little bit odd. Maybe it should have it's own disabled state, which a little bit darker then unselected part

 not-allowed cursor appears for buttons, but not for inputs, which are interactive elements too. But maybe there're some conventions of how to use this cursor, Idk

It's possible for now to go to generating state with unfilled form. Can't see the separate task for this, but if we already submitting form on this step - maybe it's good moment to add some front end validation - just to check if everything that needs to be filled/selected/checked is actually filled/selected/checked

I thought that was fixed on one of the previous PRs, but on this branch form/description parts still looks like taking around 50/50 of the screen. It looks different in designs

It's possible for now to go to generating state with unfilled form. Can't see the separate task for this, but if we already submitting form on this step

The issue is that this task was done in the wrong order, the API integration should've been first, and it would've included actually submitting the form + basic validation + error handling. It should not do in this.

I thought that was fixed on one of the previous PRs, but on this branch form/description parts still looks like taking around 50/50 of the screen

Agreed with Alina to set it to 50/50 to scale better to larger screens, the discussion for how to tweak it in the future is still open.

Split this into 3 different pull requests

Why do you think it is in any way useful for you to put a random background image behind the QR code?

I've multiple times stated explicitly that this will be implemented to the backend, and just placing a picture on the background in HTML does not make it appear in the download.
This is also not the correct design.


Fixes tiny typo in client mode example

Noticed a really minor typo in the README as I was looking up an example.

:+1: Please see https://github.com/square/ghostunnel/blob/master/CONTRIBUTING.md before I can merge.

Done.

Thanks!


Fable.MochaPuppeteerRunner - Missing method LaunchAsync with Puppeteer 2.0.4

Tried to add the library to SAFE template, but when run I got following exception:
Unhandled exception. System.MissingMethodException: Method not found: 'System.Threading.Tasks.Task`1<PuppeteerSharp.Browser> PuppeteerSharp.Puppeteer.LaunchAsync(PuppeteerSharp.LaunchOptions, Microsoft.Extensions.Logging.ILoggerFactory)'.
   at Puppeteer.runTests@71-4.Invoke(Unit unitVar)
   at Microsoft.FSharp.Control.AsyncPrimitives.CallThenInvoke[T,TResult](AsyncActivation`1 ctxt, TResult result1, FSharpFunc`2 part2) in D:\workspace\_work\1\s\src\fsharp\FSharp.Core\async.fs:line 386
   at Microsoft.FSharp.Control.Trampoline.Execute(FSharpFunc`2 firstAction) in D:\workspace\_work\1\s\src\fsharp\FSharp.Core\async.fs:line 104

resolved versions:
Fable.MochaPuppeteerRunner (1.2)
PuppeteerSharp (2.0.4)
EDIT: works fine if I pin PuppeteerSharp to 1.17.1

Hi there @theimowski the package probably only works with PuppeteerSharp > 1.17 && < 2.0.0  I will update and publish a new version soon that uses latest 😄

Published version v1.3 of the runner and it should work ootb with latest puppeteersharp

yup works fine - thanks!

PuppeteerSharp 3.0 has been released 2 days ago, and now there's a similar issue:
  Unhandled exception. System.MissingMethodException: Method not found: 'System.Threading.Tasks.Task`1<PuppeteerSharp.Browser> PuppeteerSharp.Puppeteer.LaunchAsync(PuppeteerSharp.LaunchOptions, Microsoft.Extensions.Logging.ILoggerFactory, PuppeteerSharp.Product)'.
     at Puppeteer.runTests@71-4.Invoke(Unit unitVar)

Here we go again :/ please pin puppeteersharp for now, I'll update it sometime soon


Jenkinsfile run unit tests under AddressSanitizer

Would running in Valgrind make sense here to check for uninitialized memory?

Would running in Valgrind make sense here to check for uninitialized memory?

Yes absolutely, especially now that we have lockstep and might actually be able to exercise the majority of the code (very slowly).


tvheadend adding icons

how can i add all the cabernet icons to tvheadend so that they will show up in emby?
currently channel icons from cabernet to tvheadend to emby are missing in emby but the epg does show up.

the icons did finally show up in emby. it just took a really long time to come from tvheadend.


Ruby 2.4 support

Ruby 2.4 unifies Fixnum and Bignum into a single Integer class.
As of 2.4, referencing the Fixnum or Bignum constants directly emits a warning.
This pull request replaces the references to Fixnum or Bignum with Integer.
I've also bumped a few development dependencies to get the test suite up and running. It's currently failing with a few encoding related errors.

The encoding issues are fixed as of https://github.com/github/bert/pull/10


Ensure /usr/local/android-sdk/tools/bin is on $PATH

Recent versions of Android tools have essential tools in this
directory, while on older versions used "tools".
In particular, sdkmanager is found in "tools/bin".

This partially addresses https://github.com/travis-ci/travis-ci/issues/7331 by modifying $PATH.


could you provide any hint

Hello, I created a repository based on your puzzle.
https://github.com/Schum-io/BTC-Puzzle-by-Corey-Phillips
I tried brute-forcing over 1 million passphrases without any success.
I need at least some hint about the format of the passphrase. Should it be wrapped in sha256 or used in its raw form?

Still no hints, huh...?

Corey Phillips he said on his twitter "It's not meant to be solved. It's meant to prove the viability of the method" I tested a few thousand combinations using brute force, your method is really safe


[REQUEST] Topic specific news without specifying a website?

Would it be possible to get the tech headlines without specifying a website?

Like this?
 tech_headlines = [Newscatcher(source).get_headlines() for source in urls(topic = 'tech')]

be carful tho it's going to be a huge number of request and probably better doing it it with a try catch in case a website is un reachable.

@0xYasser urls has an optional n parameter to limit results

Yes, that's how you could do it

Like this?
 tech_headlines = [Newscatcher(source).get_headlines() for source in urls(topic = 'tech', language='en')]

be carful tho it's going to be a huge number of requests


Unimplemented in srs/reference_string/mem_reference_string.rs

Mem Reference String
There is a single unimplemented!() here:

[ ] VerifierMemReferenceString::new()`

Then we should add in the accompanying tests from here.

Test

I'll take this one

@colinnielsen how's this cookin'?
Do you have any notes for what we need to get done first? Miller lines/algorithm?

@colinnielsen how's this cookin'?
Do you have any notes for what we need to get done first? Miller lines/algorithm?

Waiting on Claudia's refactor and merge of #60 to move forward with this implementation

@colinnielsen check it out, it's readyish to merge. see Filereferencestring as the example

@colinnielsen does this mean you can get back to this?