Go template dependencies are outdated

The go template uses some older dependencies, like:

Golang 1.14
Cloudevents SDK 2.5.0

See: https://github.com/knative/func/blob/main/templates/go/cloudevents/go.mod#L3-L5
Would it be reasonable to bump those to:

Golang 1.18
SDK 2.12

@matzew let's see how this PR plays out https://github.com/knative/func/pull/1451

@lance what's the update on this PR?

if there is still a need for upgradation then we can label this issue as the good first issue?

if there is still a need for upgradation then we can label this issue as the good first issue?

@ShlokMohanty we are discussing some bigger changes to the Go templates in #1451 which would make this issue obsolete. I'd like to hold off for now on making any changes until we get the questions in 1451 resolved.

/kind good-first-issue

@lance is the good first issue label removed from this issue ?

@lance is the good first issue label removed from this issue ?

Yes, mainly because these issues will likely be resolved in some form via #1451

Related: #1469


[$250] Web - Pay - Not here page opens when Gmail user Pay with Expensify

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

Version Number: 9.0.38-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:

Open 1:1 chat with other user
Go to Pay
Select USD -$ currency>Enter amount> Next> Pay with Expensify

Expected Result:
Add bank account page should open
Actual Result:
Not here page opens when Gmail user Pay with Expensify
Workaround:
Unknown
Platforms:

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

Screenshots/Videos
https://github.com/user-attachments/assets/b9c18590-c3bb-44f9-b8c3-e875c378dbb8

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021837168425885571920
Upwork Job ID:<PHONE_NUMBER>885571920
Last Price Increase: 2024-09-20

Issue OwnerCurrent Issue Owner: @ikevin127

We think that this bug might be related to #wave-collect - Release 1

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

Proposal
Please re-state the problem that we are trying to solve in this issue.
Pay - Not here page opens when gmail user Pay with Expensify
What is the root cause of that problem?
When user is not validated and navigates to bankAccountRoute (settings/wallet/add-bank-account) hmm it not page is displayed
https://github.com/Expensify/App/blob/d009d8ed4830c7d0562c524c991b8a688e2b4869/src/components/MoneyRequestConfirmationList.tsx#L849
https://github.com/Expensify/App/blob/d009d8ed4830c7d0562c524c991b8a688e2b4869/src/pages/AddPersonalBankAccountPage.tsx#L70
What changes do you think we should make in order to solve the problem?
We should check if the user is validated first before we display pay with expensify button

get currentUserPersoanlDetails using

const currentUserPersonalDetails = useCurrentUserPersonalDetails();

Display paywith Expensify button when the user is validated

const canUseWallet = !isExpenseReport && !isInvoiceReport && currency === CONST.CURRENCY.USD && currentUserPersonalDetails.validated;

https://github.com/Expensify/App/blob/d009d8ed4830c7d0562c524c991b8a688e2b4869/src/components/SettlementButton/index.tsx#L98
What alternative solutions did you explore? (Optional)

@davidcardoza, I can't add this issue to the bill pay project. Can you please help? Thanks!

Not able to reproduce!

♻ Reviewing proposals in progress.

🎉 Thanks everybody for the proposals and great variety in solutions!

From reviewing the existing proposals, three variants are surfacing (see below) and I'm not sure whether this is a design or business decision but I'll tag @Expensify/design anyways to get their take on this before assignment since the team was active recently in PR #49230.
ℹ As reviewer, I lean towards proposal 3 because, given PR #49230, we can agree that some work was put into this flow already specifically for the case when user account is not validated yet. My second option would be proposal 2 since it's the closest to what I think will be preferred here, and we wouldn't need to HOLD if we were to go with this version.

Proposal 1: ♻ Hide Pay with Expensify button via canUseWallet when using unvalidated account, ⏳ Can be implemented right away
Proposal 2: ♻ Display ValidateAccountMessage component when pressing Pay with Expensify with unvalidated account, ⏳ Can be implemented right away
Proposal 3 [HOLD #49230]: ♻ Display new VERIFY_ACCOUNT screen when pressing Pay with Expensify with unvalidated account, ⚠ Can be implemented as soon as https://github.com/Expensify/App/pull/49230 is merged

Yeah I kinda wanna hear what @JmillsExpensify and @trjExpensify thinks too. I can see an argument for both 1 and 3. 2 feels weird to me

Agree that I'd like to hear from Jason and Tom, but my understanding was that Proposal 3 was how we wanted to handle all these unvalidated account situations (basically just add the validate screen to the beginning of whatever flow the user was trying to go through) so I have a strong preference for that option.

Yep, same. Proposal 3 for the win.
I'd also say let's make sure that copy gives them a hint to go check their mail to grab the magic code we just fired off. I.e "This feature requires you to validate your account. Enter the magic code sent to your email."

Based on the latest discussions looks like @cretadn22's proposal is the way to go here. The RCA is correct and the proposed solution was verified by the design team.
Note: Even though we assign the contributor now, we should HOLD https://github.com/Expensify/App/pull/49230 until the PR is merged since the proposed solution is dependent on that PRs additions.
🎀👀🎀 C+ reviewed

Even though we assign the contributor now, we should [HOLD #49230] until the PR is merged since the assigned solution is dependent on that PRs additions.

ℹ Status update:

PR https://github.com/Expensify/App/pull/49230 was merged which means we can move forward with our selected proposal solution and open the PR with the fix for this issue

♻ PR https://github.com/Expensify/App/pull/50169 is in review

@ikevin127 @cretadn22, can you please provide an update? Did the PR cause a regression? What's next here?

@isabelastisser Yes, we had the following regression:

https://github.com/Expensify/App/issues/50284

which was caused by lack of testing on both PR reviewer and author sides. The issue mentioned above is open for proposals, unless the author wants to fix the issue given that we're still within the regression period.
Note: The issue was that we relied on the other PRs implementation of the new route without actually testing if the implementation works, ignoring this issue's Expected result which states Add bank account page should open as we stopped the testing at "seeing the magic code input showing up in RHP".

@cretadn22 No. Truth is that because neither of us actually tested what happens once the validation code is inputted - we're both going to get the regression penalty here.
It's also true that the issue of being logged out was not caused directly by logic you introduced in the PR, but rather an edge case / side effect of using the logic of the other PR in our specific case.
Given this, as I mentioned in the regression issue -> it's open for proposals.

[x]  [@ikevin127] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/37174.
[x]  [@ikevin127] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/37174/files#r1797481938.
[x]  [@ikevin127] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A.
[x]  [@ikevin127] Determine if we should create a regression test for this bug.
[x]  [@ikevin127] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Proposal

Login to new account (unverified).
Start a chat with an existing user > [+] > Pay [userName].
Select USD > Pay with Expensify.
Verify that the 'verify account page' shows up in RHP prompting user to enter the magic code.

Do we agree 👍 or 👎.

@isabelastisser As for payment, there was one regression:

https://github.com/Expensify/App/issues/50284

which wasn't caused directly by the code implemented by this issue's fix but as a side effect of our previous logic not being adjusted to handle updating the authToken while logged in - more details in issue https://github.com/Expensify/App/issues/50284#issuecomment-2408136449.
Given this, both me (reviewer) and contributor should get a -50% penalty on the issue's bounty.

I was OOO yesterday. I will review this today!

@ikevin127, thanks for the detailed explanation above! I've processed the payments in Upwork now.


Error while updating property display on Android

Seems like Android native <HorizontalScrollView> element doesn't like to receive display: 'block' styles, and therefore is throwing an error.

I'm not sure what to do to fix that, since on iOS seems to work just fine

I don't think we rely on the display property on either os so we can probably just remove it in the generateNewStylesheet function


[tool_crash] String: <57 characters>

Command
flutter --no-color run --machine --device-id=emulator-5554 --start-paused --profile --dart-define=flutter.inspector.structuredErrors=true lib\main.dart

Steps to Reproduce

...
...
...

Logs
String: <57 characters>

[✓] Flutter (Channel stable, 3.24.3, on Microsoft Windows [Version 10.0.22631.4037], locale fr-CA)
    • Flutter version 3.24.3 on channel stable at C:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2663184aa7 (5 weeks ago), 2024-09-11 16:27:48 -0500
    • Engine revision 36335019a8
    • Dart version 3.5.3
    • DevTools version 2.37.3

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at C:\Users\ouali\AppData\Local\Android\sdk
    • Platform android-UpsideDownCakePrivacySandbox, build-tools 34.0.0
    • Java binary at: C:\Program Files\Android\Android Studio1\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-b2043.56-10550314)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.8.6)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.8.34525.116
    • Windows 10 SDK version 10.0.22621.0

[!] Android Studio (version 2022.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to determine bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Android Studio (version 2023.1)
    • Android Studio at C:\Program Files\Android\Android Studio1
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-b2043.56-10550314)

[✓] VS Code (version 1.94.1)
    • VS Code at C:\Users\ouali\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 13 (API 33) (emulator)
    • Windows (desktop)            • windows       • windows-x64    • Microsoft Windows [Version 10.0.22631.4037]
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 129.0.6668.70
    • Edge (web)                   • edge          • web-javascript • Microsoft Edge 129.0.2792.89

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 2663184aa79047d0a33a14a3b607954f8fdd8730

Closing this as a duplicate of https://github.com/flutter/flutter/issues/108812


nixos/sourcehut: fix module and update

Description of changes

[x] Add some basic tests for sourcehut
[x] Update the services to their latest versions
[x] Fix #201425, #201424 and #199778
[x] Fix the broken git, hg and build services

What still does not work:

[ ] Pulling hg repositories over http(s)
[ ] You tell me.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Maintainer Highlight: @tomberek

Hey might I ask why you marked this as a draft?

Hey might I ask why you marked this as a draft?

Well, this doesn't apply anymore. So I tried to rebase this on current master, solve the conflicts and update the packages to their latest versions (as this PR is almost half a year old now). Then I noticed that

not a single package builds anymore, upstream changed everything
after fixing the builds, nothing works anymore
I have no clue why the version in this PR works as well as it does.

Each service (gitsrht, hgsrt, buildsrht, todosrht …) has its own client-id and secret which are supposed to go into the oauth database of metasrht. We never did that and it wasn't really an issue, but now it is and the web interfaces don't work anymore. Since the oauth keys belong to users, in order to put the service oauth keys into the database, we need to also declaratively provision an admin user we can assign these keys to. The nixos module with the dozens of different services (up to 4 per "sourcehut service") and different PreExec-tasks (initializing the databases, generating the config.inis with the secrets plugged in etc) is already quite complicated and I wasn't sure what the best way to do this is.
While I'm sure that it's possible to fix this, because of the complexity of the project, rate of upstream changes, lack of documentation and generally no interest in the nixos community (after all, the sourcehut module in nixos is completely broken for a long time now), it's hard to find people willing to review changes that would be neccessary to make this work. Every few months when upstream breaks everything again.
I think that the best way to use sourcehut on nixos would be to

massively simplify the module to be in a position to better react to upstream changes. For example I'd get rid of the different per service configs and drop the redis unix socket defaults since upstream doesn't use these and it's somewhere between fiddly and impossible to use (the different services expect different formats of the unix-socket uri or don't support unix sockets at all)
maintain it as a flake outside of nixpkgs.

I might attempt this when I feel more motivated.

Realistically, I won't be pursuing this anymore. Feel free to pick it up.


Tutorial/advanced min fulcro - routing finished

@hukka I have pushed an update adressing some of your comments


fix(colorscheme): don't set theme on win with theme already set

if a plugin - e.g. levouh/tint.nvim - changes a windows hl_ns on WinLeave, styler overwrites these changes.
WinLeave - tint sets new hl_ns
WinNew - styler sets hl_ns on all windows containing the buffer of new window overwriting the changes on WinLeave

ty!


How to stop automatic sliding?

Hi, i just want to manually slide the image , i don't like to slide it on it's own. how can i do that?

@cabuhatprince mDemoSlider.stopAutoCycle();


why not support algorithm SM2/3/4/9 and ZUC in provider?

Which version of the provider are you looking at? We already support SM2/3/4.

java.security.NoSuchAlgorithmException: no such algorithm: SM2 for provider BC
1.60

Cipher cipher = Cipher.getInstance("SM2", new BouncyCastleProvider());
cipher.init(Cipher.ENCRYPT_MODE, privateKey);
java.security.NoSuchAlgorithmException: No such algorithm: SM2
at javax.crypto.Cipher.getInstance(Cipher.java:687)
1.60

@bcgit I am using 1.61 release version, but same error comes out.
SM2Cipher: Exception: java.security.NoSuchAlgorithmException: No such algorithm: SM2
java.security.NoSuchAlgorithmException: No such algorithm: SM2
at javax.crypto.Cipher.getInstance(Cipher.java:687)
at javax.crypto.Cipher.getInstance(Cipher.java:595)
at org.bouncycastle.jce.provider.test.SM2CipherTest.performTest(SM2CipherTest.java:56)
at org.bouncycastle.util.test.SimpleTest.perform(Unknown Source)
at org.bouncycastle.util.test.SimpleTest.runTest(Unknown Source)
at org.bouncycastle.util.test.SimpleTest.runTest(Unknown Source)
at org.bouncycastle.jce.provider.test.SM2CipherTest.main(SM2CipherTest.java:116)

I've checked, it's there. It might be worth checking your class path, it looks like an older version of the provider may have gotten introduced as well.

Zuc is now supported in the current beta of 1.63.


Remove version: Jackett.Jackett version 0.20.2697

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.20.2697/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


Use address(0) instead of 0x0

Make it clear that it's an address

Interesting! I like the idea, thanks @doraemondrian.


contract-verifier Dockerfile - The script may not have permission to execute

🐛 Bug Report
https://github.com/matter-labs/zksync-era/blame/main/docker/contract-verifier/Dockerfile#L33
📝 Description
here no  chmod +x   possible may not have permission to execute
Provide a clear and concise description of the bug.
🔄 Reproduction Steps
Steps to reproduce the behaviour
🤔 Expected Behavior
Describe what you expected to happen.
😯 Current Behavior
Describe what actually happened.
🖥 Environment
Any relevant environment details.
📋 Additional Context
Add any other context about the problem here. If applicable, add screenshots to help explain.
📎 Log Output
Paste any relevant log output here.

nice catch there.


When replay fails (SC2 4.9.1)

Dear All,
Usually it is pleasant to generate mpq files from a bot game and look at them after, by moving wisely the camera independently of the bot move_camera. Unfortunately the replay of such pysc2 files is no more working. Remember that the replay files, are written by agent.bin.play.
My current SC2 version is 4.9.1 and i am using pysc2 which is 4.8.x compatible.
When I am launching the replay with BattleNet, connected or not, SC2 tells me that it cant play the file.
Trying to solve this problem, I tried many things :

to add arguments inside BattleNet interface, by adding something like this as command line argument :
-dataVersion B6D73C85DFB70F5D01DEABB2517BF11C
(that is supposed to call Base65384 version)

to see if it is supported by pysc2 dev branch (probably not because it did the same...)

to modify pysc2/run_configs/lib.py file,
by using pysc2/bin/gen_versions.py and copy-past new versions with keys into the file
...
Version("4.8.5", 73559, "B2465E73AED597C74D0844112D582595", None),
Version("4.8.6", 73620, "AA18FEAD6573C79EF707DF44ABF1BE61", None),
Version("4.9.0", 74071, "70C74A2DCA8A0D8E7AE8647CAC68ACCA", None),
...

to do the same with version 4.9.1 from reading logs of the launcher
...
Version("4.9.1", 74456, "218CB2271D4E2FA083470D30B1A05F02", None),

to use many of these data version numbers inside the BattleNet interface

Thus if you have any ideas about this problem, please let me know.
Best

Does it work with the newest versions of the game and pysc2 now?


No bitmask hash table for joins

Create a Join dwarf version with no-bitmask hash table.

Added with #26


refactor: webpack & eslint - disable autofix on startup compile

📦  Config-UI / Webpack

[x] Refactor Disable ESLint autofix on Webpack startup

This PR turns OFF the ESLint autofix setting for Webpack which was appropriate during early stages of development. With recent changes to the Global ESLint  & adopting Prettier configuration, however, this creates an undesirable situation for developers with older versions of main when trying to rebase or update, Webpack's ESLint's auto-fix will try to enforce the new standards while the server is starting or re-compile if it is running already running, which will automatically try to write changes to local files which will cause workflow conflicts.
...
...
      new ESLintPlugin({
        // Do NOT auto-fix w/ eslint on webpack startup!
        fix: false,
        context: path.resolve(__dirname, './'),
        exclude: ['dist', 'packages', 'cypress', 'config', 'node_modules']
      }),
...
...

Does this close any open issues?
Closes #3152

LGTM.


[Feature] Branch allows for setting expiration times.

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Branch supports expiration time
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

Why we need this feature?

Why we need this feature?

By setting an expiration time, you can automatically manage the lifecycle of branches. For example, you can automatically delete them when experimental branches are no longer needed.   Same meaning as "tag.defilt-time-retained" in tag

I doubt this, branch is a heavy concept to me, it should no be quietly expired.

I doubt this, branch is a heavy concept to me, it should no be quietly expired.

Branches that have not been maintained for a long time can be cleared, especially test branches that allow for setting retention time

I doubt this, branch is a heavy concept to me, it should no be quietly expired.

For important branches, you can set no retention time, allowing for long-term existence;
For some unimportant branches, such as test branches or fix branches, a retention time can be set for easy cleaning;
Actually, I think that most branches do not need to exist for a long time and need to be cleaned up after verification

Because branches are not created frequently or regularly. So I think this kind of branch can be deleted manually.


[SUP1-161] Support multiple Application

E.g. Staging and Production

From SyncLinear.com | SUP1-161

chatted with @tomkit. we're goin to assume single-tenant, no roles. Given that, we don't need to build any join table for applications <→ sg_users. we can just drop relation between applications and sg_users table


Update http4s-circe, http4s-dsl to 0.23.17

Updates

org.http4s:http4s-circe
org.http4s:http4s-dsl

from 0.23.4 to 0.23.17.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.http4s" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #425.


Reply to this email directly, view it on GitHub
https://github.com/KMODs-dev/ModMenu-FreeFire-Esp/issues/1, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASDHIK7SI4WHNQRHYDK5CS3SXICTJANCNFSM4VNM2JRQ
.

@Ascarre i want to talk to you can u dm me please. I cant find u on telegram..
@Ascarre is my tlg id....


Mappings Changes

Rename RenderTrains to MainRenderer
Use -server builds for Minecraft Transit Railway (without the assets) for smaller library sizes
Remove shouldNotRender (this has been removed from Minecraft Transit Railway)

What are the ways to get MTR assets working in Minecraft Debug Mode now that it depends on the server build?

Oh I haven't thought about that, I think using a clientside resource pack (with all the assets) might be the best option. I thought using a JAR file without assets would make it much smaller (70 MB down to 11 MB), since always uploading large JAR files to GitHub doesn't seem like a good idea in the long run. For example, diffs are usually unable to be shown properly or it just takes a long time to load.

Ideally dependency should be pulled from elsewhere instead of stored in the repo, but if there's no other way then I guess I'll have to use the client RP method

I agree, ideally we would do that, but I just don't have anything set up yet. Perhaps after I start uploading to Modrinth, we can use their API to easily import the mod as a dependency through Gradle.


Storage BlobInfo createdTime not present in library

Hello,
I have been using the library and checking the [JSON API exposes] 1, as a reference to use Google Cloud Storage, I haven't been able to find these fields:

timeCreated
any of the encryption attributes

However one can find them in the library this library is relying on: https://developers.google.com/resources/api-libraries/documentation/storage/v1/java/latest/com/google/api/services/storage/model/StorageObject.html
Would it be possible to at least expose the timeCreated field?
Thank you!

Hi @txomon,
thanks for the report. Sure thing, I'll add support for timeCreated ASAP.
We also plan to support customer-supplied encryption keys but that might take I bit longer. I'll keep you posted.

@txomon createTime was added in  #1034, it will be available in the next release of gcloud-java (that should be out by the end of this week). I added #1037 to track the encryption key issue.


Fix issue #17 and added support for setting target URL

Fixed the minor issue with --target-url-ref and added support for --target-url

Please see PR for issue #20 - I think we need the same here.


Apply exclusions to original files

The problem the component solves
Users may way to exclude lists of messages or folders that they want to exclude from a mailbag. Thus, we'll have to remove these from the original input files, such as MBOX and PST when including them the mailbag.
Relevant part of mailbag spec?
Type of component

[ ] Core
[x] Input
[ ] Attachments
[ ] Derivatives conversion
[ ] Reporting/Exporting
[ ] GUI
[ ] Distribution

Expected contribution

[x] Pull Request
[ ] Comment with proposed solution

Major challenges or things to keep in mind

This is on hold because excluding messages from PSTs in particular isn't feasible. We have to reexamine what the purpose and priority of this is.

IMHO It might make more sense to implement this as a separate tool/tools or
even defer to a guide to existing tools?  Like, bagging is a metadata +
fixity step at core, and it's a little weird maybe to have this kind of
alteration as a part of a tool aimed at fixity operations?
I guess the counter argument is that doing it in-tool would allow for
recording metadata about the exclusions in the mailbag, I'm I think outside
my expertise re: archival process here tbh.
On Wed, Jan 19, 2022 at 11:55 AM Gregory Wiedeman @.***>
wrote:

This is on hold because excluding messages from PSTs in particular isn't
feasible. We have to reexamine what the purpose and priority of this is.
—
Reply to this email directly, view it on GitHub
https://github.com/UAlbanyArchives/mailbag/issues/25#issuecomment-1016666378,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAIH4CYKMUSQX6PRRJCC3DUW3UIFANCNFSM5CQ7CD4Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@pobocks 's comment is reasonable. The issue is that there isn't great upstream tooling for, say, PSTs, and the filtering described by #28 would be useful if we ever implement IMAP or API sources. As described with #28, we would have to not package the source files which has limitations. Thus I'm closing this and leaving #28 open as the single issue for this. This feature is de-prioritized unless we get community feedback valuing it, or whenever IMAP or API parsers are implemented.


Add error handling UI for ZEC send UI

Is your feature request related to a problem? Please describe.
The user can provide bad input to the ZEC send form
Describe the solution you'd like
The send ZEC screen should provide good feedback to the user about errors on the form input.

Amount too small (cannot cover fee)
Amount too large (exceeds current balance)
Bad address

Amount too small (cannot cover fee)

Does that imply that the fee is deducted from the amount entered? That seems not a good UI to have by default: normally, I want to guarantee that the recipient will get the amount of money I enter.

This may be related to Electric-Coin-Company/zashi#39 and Electric-Coin-Company/zashi#40


Don't cache service-worker.js when using pwa plugin

Hello, thanks for this and the apollo plugins! Just a real quick change here.
I'm using this plugin along with the pwa plugin and am receiving the following warning on Chrome 69.0.3497.92

The last argument to serve needs to either be omitted or changed to false on the following line: https://github.com/Akryum/vue-cli-plugin-ssr/blob/master/lib/app.js#L80
Thanks!

@Akryum As this should probably be fixed and is an easy change (https://github.com/Akryum/vue-cli-plugin-ssr/blob/master/lib/app.js#L83), would you accept a MR for this?


Added pre save hooks for pojos

Thanks Daniel!

Sorry, for some reason you do not seem to be mentioned in the list of contributoors, Daniel?! My fault I guess, but usure why.


2404 general issue ensure argument name is correct in error messages

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Review the Cheat Sheet. Make any required updates to it by editing the file inst/cheatsheet/admiral_cheatsheet.pptx and re-upload a PDF version of it to the same folder.
[x] Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md under the header # admiral (development version) if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers). A Developer Notes section is available in NEWS.md for tracking developer-facing issues.
[x] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

ummm...something is amiss here :) 290 files changed seems a bit much!!

I add you to admiraldev repo.  Let me know if you need any help!

Closing this PR in light of changes being made in admiraldev instead - see here


Can not visualize image via show_cam_on_image

To replicate error:
target_layers = [
        model.layer4[-1]
    ]  # last layer before classfier
cam = GradCAM(model=model, target_layers=target_layers, use_cuda=True)
transform_test = transforms.Compose(
        [
            transforms.ToTensor(),
            transforms.Normalize((0.4914, 0.4822, 0.4465), (0.2023, 0.1994, 0.2010)),
        ]
    )
test_set = CIFAR10(
        root="./data",
        train=False,
        download=True,
        transform=transform_test,
    )
eva_loader = DataLoader(
        dataset=test_set,
        batch_size=256,
        shuffle=False,
        num_workers=8,
        pin_memory=True,  # 256
    )
for i, (images, labels) in enumerate(eva_loader):
        print(images.shape, labels.shape) # output: torch.Size([256, 3, 32, 32]) torch.Size([256])
        img = Variable(images).cuda()
        targets = None
        cam.batch_size = 256
        grayscale_cam = cam(input_tensor=img, targets=targets)
        print(grayscale_cam.shape) # output: (256, 32, 32)
        grayscale_cam = grayscale_cam[0, :]
        visualization = show_cam_on_image(
            images[0, :, :, :], grayscale_cam, use_rgb=True
        )

Error message:
Traceback (most recent call last):
  File "gradcam.py", line 117, in <module>
    gradcam()
  File "gradcam.py", line 107, in gradcam
    visualization = show_cam_on_image(
  File "python3.8/site-packages/pytorch_grad_cam/utils/image.py", line 53, in show_cam_on_image
    if np.max(img) > 1:
  File "<__array_function__ internals>", line 180, in amax
  File "python3.8/site-packages/numpy/core/fromnumeric.py", line 2793, in amax
    return _wrapreduction(a, np.maximum, 'max', axis, None, out,
  File "python3.8/site-packages/numpy/core/fromnumeric.py", line 84, in _wrapreduction
    return reduction(axis=axis, out=out, **passkwargs)
TypeError: max() received an invalid combination of arguments - got (out=NoneType, axis=NoneType, ), but expected one of:
 * ()
 * (name dim, bool keepdim)
      didn't match because some of the keywords were incorrect: out, axis
 * (Tensor other)
 * (int dim, bool keepdim)
      didn't match because some of the keywords were incorrect: out, axis

Same here. Even there's no transforms.Normalize(), same error still exists.
Anyone has comments ?

Accidentally I reproduced your problem today, after looking at the source code in my env, I saw that this is caused by the fact that you pass to "show_cam_on_image" as the first argument a tensor (images[0, :, :, :]) instead of a np.array()

Hi all,
show_cam_on_image expects a numpy image with the format rows x cols x 3.
In the code above, images[0, :, :, :] is a pytorch tensor with the shape 3 x rows x cols.


darklua: 0.10.2 -> 0.10.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/seaofvoices/darklua/releases.
meta.description for darklua is: A command line tool that transforms Lua code
meta.homepage for darklua is: https://darklua.com
meta.changelog for darklua is: https://github.com/seaofvoices/darklua/blob/v0.10.3/CHANGELOG.md
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.10.3 with grep in /nix/store/9g8p8bas11iq7cyfsrv6bphyrkb4ynbm-darklua-0.10.3
found 0.10.3 in filename of file in /nix/store/9g8p8bas11iq7cyfsrv6bphyrkb4ynbm-darklua-0.10.3

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
darklua

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9g8p8bas11iq7cyfsrv6bphyrkb4ynbm-darklua-0.10.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A darklua https://github.com/r-ryantm/nixpkgs/archive/a973a1ea4f1cdd2079e3a05e4dd47311dbc77d9b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a973a1ea4f1cdd2079e3a05e4dd47311dbc77d9b#darklua

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9g8p8bas11iq7cyfsrv6bphyrkb4ynbm-darklua-0.10.3
ls -la /nix/store/9g8p8bas11iq7cyfsrv6bphyrkb4ynbm-darklua-0.10.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

darklua

Maintainer pings
cc @tomodachi94 for testing.

Result of nixpkgs-review pr 259686 run on x86_64-linux 1

1 package built:

darklua


OpenID Connect issue with Azure AD: implicit vs code authorization flow

Gitea version (or commit ref): docker gitea/gitea:1 (67f9ff4a24c9)
Git version: gitea/gitea:1 (67f9ff4a24c9)
Operating system: gitea/gitea:1 (67f9ff4a24c9) running on Ubuntu 16.04
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
I want to use Azure Active Directory as an OAUTH2.0 provider via the OpenID Connect feature. Gitea contacts the AD correctly and the workflow on AD side executes correctly but then the callback fails.

According to microsoft docs response_type | Must include id_token for OpenID Connect sign-in but Gitea sends response_type: code as shown in the screenshot.
I did some research on the matter and it seems that Msft is following the implicit flow whereas Gitea uses the Authorization Code Flow.
What are your thoughts on the matter? Is this something that should be changed in the OpenID Connect adapter of Gitea or rather add an Azure AD OAUTH provider directly?

That actually seems questionable.  Authorization Code Flow should always be used for hosted servers, like Gitea.  Implicit Flow is designed for things like public javascript apps.  I'd wager there is probably some mis-set setting in Azure or so as you really don't want to be using the implicit flow for a hosted server (just as you really exceptionally don't want to use authorization code flow for a SPA).

Thanks for those insights, I don't know that much about the OpenID format. I will get in contact with Msft support and discuss this issue, will update with a solution.

I think this should be improved in Gitea as oauth should return token/flow that has been requested

@OvermindDL1 was correct, there was a configuration missing on Azure AD side. The docs are a mess about this.
If anyone ever comes across this issue again, you need to configure the AD application on Azure side to Default Client Type: yes. This forces AAD to follow the code flow.

Good afternoon,
I'm having the same issue. I followed @anoff answer and I still have the same problem.
I followed this link for the setup: https://blog.anoff.io/2019-03-23-configure-azure-ad-for-gitea/
I'm using Gitea 1.8 with MySQL on openSUSE Leap 42.1 and I have 2FA enabled in my Azure account.

Hey @Mr-Reca,
did you create a native app in Azure? When looking at your app registration the Authentication tab should be configured like this

Did you also set the correct tenant for the OpenID URL? Maybe you can share your config (w/o secret) and error messages you receive.

Hey @anoff
Where can I check if my app is native or not? I've just followed your blog. I check the Authentication settings (Default client type) and I also checked the secrets, keys & IDs.
The only thing is that Azure forced me to use https. I created a certificate using gitea cert --host <hostname>.<domain> and I change the config file.
When I log in, I do the MFA and then the browser shows me the error AADSTS50011: The reply url specified in the request does not match the reply urls configured for the application: <client_id>.
The reply URL is the next one:
https://<hostname>.<domain>:3000/user/oauth2/<app_name>/callback
The OpenID URL is the next one:
https://login.microsoftonline.com/<tenant>/v2.0/.well-known/openid-configuration
Do you want the config and some log files in case I missed something?
Thank you so much,

Let's discuss the details offsite, Twitter DM https://twitter.com/an0xff or
email<EMAIL_ADDRESS>a screenshot of your gitea oauth setup
On Thu, May 2, 2019, 22:09 Mr-Reca<EMAIL_ADDRESS>wrote:

Hey @anoff https://github.com/anoff
Where can I check if my app is native or not? I've just followed your
blog. I check the Authentication settings (Default client type) and I
also checked the secrets, keys & IDs.
The only thing is that Azure forced me to use https. I created a
certificate using gitea cert --host . and I change the
config file.
When I log in, I do the MFA and then the browser shows me the error AADSTS50011:
The reply url specified in the request does not match the reply urls
configured for the application: <client_id>.
The reply URL is the next one:
https://.:3000/user/oauth2/<app_name>/callback
The OpenID URL is the next one:
https://login.microsoftonline.com/
/v2.0/.well-known/openid-configuration
Do you want the config and some log files in case I missed something?
Thank you so much,
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/go-gitea/gitea/issues/6345#issuecomment-488814197,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABWPZWWEHUL4RXQ2JSRV2DTPTNDBNANCNFSM4G7BBJXQ
.

If you're using Azure App Proxy make sure you add the root url as a Reply URI in addition to the OpenID URI. This fixes the "not match the reply urls" error


Cannot start linux / run sudo startxfce4..

I followed every step correctly, unfortunately this is the error I get after doing sudo startxfce4...
`Entering /mnt/stateful_partition/crouton/chroots/xenial...
/usr/bin/startxfce4: Starting X server
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.19.5
Release Date: 2017-10-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-101-generic armv7l Ubuntu
Current Operating System: Linux localhost 3.8.11 #1 SMP Mon Nov 13 16:28:54 PST 2017 armv7l
Kernel command line: cros_secure console= console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=f087c549-d73b-7740-829e-3cda57c258b9/PARTNROFF=1 hashtree=PARTUUID=f087c549-d73b-7740-829e-3cda57c258b9/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=cb0652fe268f3ed387337531c4521f5b4e413293 salt=e317721aeae38191facdc54f87c50a4c2d181fd3041e9a365b7deedab02607bf" noinitrd vt.global_cursor_default=0 kern_guid=f087c549-d73b-7740-829e-3cda57c258b9
Build Date: 24 November 2017  09:45:24AM
xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Tue Jan 16 17:32:05 2018
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Error org.freedesktop.DBus.Error.UnknownMethod: Method "ReleaseDisplayOwnership" with signature "" on interface "org.chromium.LibCrosServiceInterface" doesn't exist
method return time=1516152725.622391 sender=:1.11 -> destination=:1.79 serial=1925 reply_serial=2
boolean true
MESA-LOADER: failed to retrieve device information
gbm: failed to open any driver (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
gbm: Last dlopen error: /usr/lib/dri/exynos_dri.so: cannot open shared object file: No such file or directory
failed to load driver: exynos
EGL_MESA_drm_image required.
(EE)
Fatal server error:
(EE) AddScreen/ScreenInit failed for driver 1
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/tmp/Xorg.crouton.1.log" for additional information.
(EE)
Error org.freedesktop.DBus.Error.UnknownMethod: Method "TakeDisplayOwnership" with signature "" on interface "org.chromium.LibCrosServiceInterface" doesn't exist
method return time=1516152726.419518 sender=:1.11 -> destination=:1.81 serial=1927 reply_serial=2
boolean true
(EE) Server terminated with error (1). Closing log file.
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Connection refused
/usr/bin/xinit: server error
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
I also then ran sudo edit-chroot -all as instructed on a related post and this was the output...
name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
crouton: version 1-20171230152552~master:de1361af
release: xenial
architecture: armhf
xmethod: xorg
targets: xfce
host: version 9901.77.0 (Official Build) stable-channel daisy
kernel: Linux localhost 3.8.11 #1 SMP Mon Nov 13 16:28:54 PST 2017 armv7l armv7l armv7l GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

I have no idea how to fix this and it seems like other don't either. No one has helped/responded to this issue on other post, so I just decided to post my issue to bring more awareness to this. If you do know how to fix this please help, thanks!
This issue is related to #3606

Seems this issue has been around for quite a while now and is related to video-armsoc drivers.
Take a look at this comment for a little more info.: https://github.com/dnschneid/crouton/issues/3611
For a couple of workarounds, see this comment: https://github.com/dnschneid/crouton/issues/3291#issuecomment-309564813
Note that in Solution 1 above you may have to substitute 'startxfce4' with your start script.
Hope this helps,
-DennisLfromGA


Update init.py for macOS on brave

Hi, I'm new to GitHub, I hope I did things correctly! This little changing of these 4 lines of code allows you to get the correct keyboard input when selecting the search bar when using the script in brave browser from MacOS

Can you make this pull request against the develop branch instead of master? That is where all new features go.
I have never tested this on Mac OS, so it doesn't suprise me that the keyboard shortcuts don't work out of the box. Sorry about that.
However, seems like changing the shortcut outright will break compatibility with other platforms. There will need to be some check to detect the platform I think. What happens with Key.cmd is used on a non-Mac platform I wonder?


Move rust dependency to the Prerequisites section

Better fix for #718.

Hey, thanks for the update on Arch Rust dep. I was trying to avoid calling out a specific compiler version in the README to allow the minimum version to change without having to update docs. Do you think we should go back to specifying a version?

Well it was defined on step 3, I merely moved it upwards 🙂 Good point, how would you phrase it?

Oh, I somehow missed that. "Most recent stable Rust compiler" is probably the phrasing we want.

Done 🙂

Thanks!


plots: add smooth template example

https://github.com/iterative/dvc/pull/4046#issuecomment-644437731
CC @pared @dmpetrov

Probably also mention the smooth template is available in the section where templates are explained as well.

@dmpetrov can we use the plot from original issue? https://github.com/iterative/dvc/issues/3906?

@pared @efiop can you take this please?

Added to the sprint, will try to take a look.


support higher granularity weighting in WeightedCluster

Currently weighted clusters must have weights that sum to 100. This limits the minimum percentage of traffic that can be sent to a weighted cluster to 1%.
We'd like to be able to select weights less than 1% (in addition to finer control than 1% increments).
It seems that the existing total weight limit stems from a combination of not wanting to (re)compute the total each time a cluster is selected (RouteEntryImplBase::clusterEntry) and the ability to modify cluster weights via the runtime configuration system. Absent runtime configuration of weights, the total weight could be computed in the RouteEntryImplBase constructor and then used during selection.
I propose to add a field to the WeightedCluster proto that allows an optional total_weight to be specified, defaulting to 100 for backwards compatibility. Would need to remove the <= 100 validation on the weights and update documentation in several places as well. The new total weight would be used in place of RouteEntryImplBase::WeightedClusterEntry::MAX_CLUSTER_WEIGHT, but otherwise the existing cluster selection code would remain as is.
(I discarded the idea of making the total weight itself a runtime-configurable value because it requires the runtime configuration and LDS implementation to agree on the value in order to produce valid configurations. I've also assumed removing runtime configuration of cluster weights is not a viable option.)

@zuercher +1. Unfortunately we've (I) done a poor job of being consistent about random chance %. In some places it's out of 100, in some places out of 10,000. Anyway, this sounds like a reasonable proposal to me.


Attempting to execute unmapped methods now triggers Exceptions

Previously, attempting to execute a method which had not been registered in the Engine's dispatcher would return a null because without a valid callable method, Dispatcher::invokeMethod() eventually falls through to Loader::load() which returns null by default if the method isn't defined in the classes list.
This removes that behaviour by throwing exceptions when undefined methods are accessed in the  Engine's dispatcher which are not otherwise mapped.
It also has the added benefit of no longer incorrectly instantiating classes when there is a crossover between a defined Flight internal class name and an incorrectly accessed method name - this undefined behaviour could be very confusing to developers.
Issue enhancement reference: https://github.com/mikecao/flight/issues/203

Some minor changes in b30d5e5fa2de08c3e91c1165ee226fd83f29ba9b. I had to move the logic to the Engine level because some people may use the app instance instead of the global static class. Also it was failing some tests.


feat: add some constructions about StrictSeries

reverse a StrictSeries to give another StrictSeries in opposite order
put a smaller element in the front
put a larger element in the end
chop off the first element

Can you add more details to the title to distinguish this from https://github.com/leanprover-community/mathlib4/pull/3858.

See zulip thread for discussion about the design here.

bors r-
bors d+
There seem to be some errors from this PR

bors r+


ocamlPackages.wasm: 1.1 -> 1.1.1

Motivation for this change
See https://opam.ocaml.org/packages/wasm/wasm.1.1.1
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build wasm ocaml-ng.ocamlPackages_4_10.wasm


[Tagger] Migrate to ES High Level REST client

Migrate to ES High Level REST client, using ARLAS core classes.

closed by #67


Slider: should be able to label each thumb with a different aria-label

Slider's aria-label prop is a string, and that same string gets applied to all thumbs. Ideally it should also accept a string array, and apply each string to each thumb, similar to how value and defaultValue can be arrays of numbers.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
<Slider aria-label={["myFirstLabel", "mySecondLabel"]} value={[10, 20]} />
renders markup that looks like

Expected Behavior 🤔
each string in the array should go to its corresponding thumb's aria-label
Steps to Reproduce 🕹
https://codesandbox.io/s/create-react-app-qmlsu
Inspect the markup of this code sandbox
Context 🔦

I am trying to improve accessibility of range sliders. Also, this would make it much easier to test range sliders using @testing-library/react
Your Environment 🌎

Tech
Version

Material-UI
v4.3.3

React
16.9.0

Browser
Chrome  76.0.3809.100 (Official Build) (64-bit)

Extra
You can see an example of multi thumb sliders with different label per thumb here
https://www.w3.org/TR/wai-aria-practices/examples/slider/multithumb-slider.html
It looks like this would be pretty easy to fix. I am happy to send in a PR with the fix if that is desired.

@city41 Thank you for the link toward w3.org. It does make sense, I believe that we can replicate the same strategy that we use with aria-valuetext (getAriaValueText).

each string in the array should go to its corresponding thumb's aria-label

We decided not to override existing native types to avoid confusion in the past: https://github.com/mui-org/material-ui/pull/15703#discussion_r289791687.

Sounds good. I will take a look this weekend and hopefully get a PR out. Thanks Olivier.


chore: remove komenci related code

Description
This PR cleans up what is left of komenci.

remove unused redux state from redux stores, add migrations
remove unused actions, selectors, sagas
remove unused utility functions
remove unused consts
remove komenci diagram

Test plan
n/a
Related issues

Fixes RET-504

Backwards compatibility
Y

Looks like the branch needs rebase/merge now.

Looks like the branch needs rebase/merge now.

Thanks @jeanregisser ! This is ready for review again, I've resolved the conflicts. Unfortunately I indulged in a little scope creep but figured that it's less painful to make this PR slightly larger than to create another follow up. I found some unused functions around the old invite flow and unused analytics events + variables that mention attestations. I removed them 🫣


[NHentaiViewer][v1.0.3]Failed to install the app.

Actual Behaviour
App fail to install in my device.
Expected Behaviour
I expected that i can install and use the app successfully.
Step to reproduce

Download the app from release page
click the app to install
see the error

Information

App version:v1.0.3
Os:Android 8.1.0
Device: symphony i72

Recording of the bug
https://youtu.be/oU5egQ9IY6Y

Try the signed version, that one should work for your device
https://github.com/ttdyce/NHentaiViewer/releases/download/1.0.3/nhviewer-1.0.3-signed.apk

Ok


Proper implementation of equals(Object) and hashCode()

In order to be able to check Uris (and their components) for equality and put them into Sets or use them as keys in a Map, as a developer I want proper support for equals(Object) and hashCode().

Before we can approach this we need to define the correct behavior. For instance as per RFC 3986, two URIs are considered to represent the same resource if their normalized forms are equal. What does this mean with respect to equals(Object)? Should we normalize the Uris before we compare them or do we leave that to the developer?
In general this could potentially result in a lot of duplicate code, if every implementation has its own equals(Object) and hashCode() methods. So the idea is to create decorators or adapters that add the ability to use equals(Object) and hashCode(). Something like new Hashable(uri) or new Equalable(uri). However since all other objects still have a default implementation of these methods a developer could easily do it wrong without noticing. The current idea to handle this is to throw an UnsupportedOperationException in equals(Object) and hashCode() of objects which do not support hashing and comparison. The behavior would be similar to adding non-hashable objects to a set in Python. This could be achieved by inheriting from an abstract base object class.

Is this still on the roadmap?

Kind of but in a slightly different way than described above. I want to approach this with an adapter class as described in dmfs/jems#182.
This allows to compare URIs in different ways. For instance, a simple UriKey would just compare the string representations. A more sophisticated version NormalizedUriKey would compare the normalized versions. An even more sophisticated HttpUriKey might be able to figure that https://example.com and https://example.com:443 are equal.

It would be nice to have a similar approach to toString, if there isn't one already.

@gordom6 what exactly do you mean? There is a Text class which implements CharSequence and supports toString.
So you can do
String uriSring = new Text(uri).toString();

I must have misunderstood you. I thought you were going to do composition so that the Uri instance has the methods (equals, hashCode toString), instead of relying on code like the above.
So
Uri uri = new ToStringableUri(new LazyUri(...))
Such that uri.toString() works. the equals equivalent would be
Uri uri = new EquatableUri(key, new LazyUri(...))
Such that uri.equals and uri.hashCode have implementations.
I love your library, but having to call a helper to get a string representation is awkward. I was thinking about doing something like the above for 'toString'. I don't understand the nuances of 'equals' and 'hashCode' as well.

I don't consider Text a helper. It's the CharSequence representation of a Uri. My issue with ToStringableUri is, it extends the original Uri contract. In other words, when you hold a Uri you can't be sure whether toString returns what you expect or not.
A Text, on the other hand, is a CharSequence and toString returns the String representation of it, by contract.
The same applies to EqualableUri or HashableUri. It's just too easy to use them incorrectly.
For instance, you can only compare EqualableUri with another EqualableUri. Otherwise equals contract is easily violated (because the equals relation wouldn't be symmetric). Having a dedicated type (and class) which adapts Uris to the equals contact sounds like the better solution to me.


Remove App Engine from Marketplace

Summary:
It probably doesn't make sense to publish AppEngine as an app of its own in the marketplace.  Can we remove it from the marketplace?
If we want to keep it in the marketplace for CLI purposes, then would it be possible to have it displayed in the marketplace similarly to NavStation and other system apps?
Screenshots:

Failure Logs
Please include any relevant log snippets or files here.
Checklist

[ ] I am running the latest version
[ ] I checked the documentation and found no answer
[ ] I checked to make sure that this issue has not already been filed
[ ] I'm reporting the issue to the correct repository (for multi-repository projects)
[ ] I have provided sufficient information for the team

In the short term, we could hide it.  Medium term would be to enable a UI which will allow for folks to visually create/edit app manifests.


No closing brackets for media query

If your app or site use css aggregation, you get broken stylesheets.

Thanks for your patch @blackiceua 😄


Proper pronounciation of multicharacter symbols

https://direct.mit.edu/artl/article/29/2/198/115422/Interdependent-Self-Organizing-Mechanisms-for?searchresult=1

At the above article, there are many math expressions whose symbols are multicharacter. NVDA speels these out character-by-character, and when you drill down into the expression via mathcat, each character becomes a node in the tree.
WOuld it be possible to treat these as single atomic units?
I don't know MathML well, so not sure if multicharacter symbols are possible in MathML.

I'm not sure what exactly you are asking to change. Can you point to an example piece of math?
I tried something that I thought you might be asking about -- some math at the end of 2.3.3. The display equation reads as:
u     sub      i     raised to the      c      r   d     power    is is equal to 2 cases
case 1   0      if    r     is greater than or equal to     t       h
case 2     negative  u    of   open paren   p   sub   i   comma    m   comma    r     close paren  otherwise

[ignore the random spacing -- I copied this from NVDA's speech viewer]
You can see "crd" and "TH" are spelled out. However, that's not surprising since they are single character tokens in the MathML.
I suspect that is a mistake in the MathML generator or by the author. The equation at the end of 4.2.2 is definitely wrong in this respect. "ReceivedOffer", "agent", etc., have each letter as an individual mi. "ReceivedOffer" should be a single mi, etc. Besides being more mathematically correct to be a single identifier, it will also look better visually because it won't be in italics. The screen reader would read it as "ReceivedOffer" rather than spelling it out, which is very likely what is desired.
I strongly suggest looking at your tool chain. It is producing lots of "HTML math" (use of <em>, <sub>, and <sup>) for the math. This turns into an accessibility disaster. Besides not getting the braille right (there's a separate math code for braille), the speech is wrong if (as is often the case, the screen reader's speech settings have "punctuation" set to some lower level than "most" or "all" -- people don't like to hear all the commas and periods in sentences. With those settings, the inline math example at the end of 2.3.3 speaks as:
where the utility mapping U p i M R is specified in link  section 4.1

Notice that the parens, commas, and subscript don't get spoken.
If the author meant some content to be math, it should be in MathML. Otherwise, it will likely not be accessible.

4.2.2 is definitely wrong in this respect. "ReceivedOffer", "agent", etc., have each letter as an individual mi. "ReceivedOffer" should be a single mi, etc. Besides being more mathematically correct to be a single identifier, it will also look better visually because it won't be in italics. The screen reader would read it as "ReceivedOffer" rather than spelling it out, which is very likely what is desired.

Thank you; that was my thought as well.

I strongly suggest looking at your tool chain. It is producing lots of "HTML math" (use of , , and ) for the math. This turns into an accessibility disaster.

I know there are probably lots of correct answers to this question, but do you have a suggestion for a toolchain? This example came from an open access journal article, and I'd like to comment on it, but I have no direct experience producing mathML, and of course, have no idea what the original article submission might have looked like.
Thank you for all you do!
-- Rich Caloggero, MIT Disability and Access Services

If it starts in TeX, tex4ht, pandoc, and latexml are good. I think pandoc uses MathJaX, but I could be misremembering.
If you start with a Word doc, it matters whether the math was created with MathType or Word's editor. Again, pandoc is one solution. Creating an ebook using the (free) DAISY Word->EPUB converter) and then pulling out the HTML file from the ebook is another option.


Rocket 5.0 release updates

Updates to support the change of Outcome so that Future has an error code and that the Outcome enum value isn't Failure it is Error.

Sorry I missed this email, I'll make the change as soon as possible.
On Sun, Dec 24, 2023, 4:33 AM Owen Griffiths @.***>
wrote:

@.**** requested changes on this pull request.
In Cargo.toml
https://github.com/Owez/rocket-basicauth/pull/8#discussion_r1435809443:

@@ -1,7 +1,7 @@
[package]
name = "rocket-basicauth"
description = "A high-level basic access authentication request guard for Rocket.rs"
-version = "2.1.1"
+version = "2.1.2"

Could you bump the version to 3 thanks, will be a breaking change
—
Reply to this email directly, view it on GitHub
https://github.com/Owez/rocket-basicauth/pull/8#pullrequestreview-1795559163,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJWU3MURCYHYRXUBLLJR36TYLAHITAVCNFSM6AAAAABBAD7Y5WVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTOOJVGU2TSMJWGM
.
You are receiving this because you were assigned.Message ID:
@.***>


Option to install to program files for all users

Description of the new feature / enhancement
Currently, the installation can't be performed to the program files folder. This possibility is really needed for security reason and using with multi-user configuration.
📸 Screenshots
No response

If you like the idea, add a 👍 reaction to this post

SpotX uses the official Spotify installer, and it is their choice to install their client in the "\AppData\Roaming\Spotify" path. While this path can be changed using various workarounds, I believe it's not worth the effort as it may cause more confusion than benefit. If you really need to change the installation path, you can request it on their forum, or try creating your own isolated environment - some people create portable builds for this purpose (google search).


Restore local creds

When using a local server and relying on the server to set the creds for you (i.e. not explicitly setting them in the config), the client will store the credentials provided by the server in local storage and restore them in the Server Connect Modal upon a click of Restore Defaults.
As a fun little bonus, this has allowed us to eliminate the dreadful "Record your settings..." warning!

Hurrah


ionic emulate livereload not exposed on localhost

We used to start the simular using the following command:
ionic emulate ios -l --address=localhost

One of the benefits of this was that the contents of the simulator are also available on localhost:8100. Updating my CLI to 1.4.3 broke this and only exposed the app on the IP address. By inspecting the code I found a hidden flag which is not documented:
ionic emulate ios -l --allIps

This works like a charm, but isn't documented anywhere. Could you please elaborate on this whether this is the correct approach? If so, could you please document this? :-)

@jasperkuperus You bet. On it now.

@jasperkuperus The documentation for run/emulate shows the --all option.
I've updated the code to respect that flag in this commit.
Published 1.4.4 with this change. Hope this helps!

Ok, great, that works. Would it be an idea to also document this in the CLI help text? E.g.:
emulate [options] <PLATFORM> ..............  Emulate an Ionic project on a simulator or emulator
        [--livereload|-l]  ................  Live reload app dev files from the device (beta)
        [--all]  ..........................  Have the server listen on all addresses (<IP_ADDRESS>)


upgrade CI tests to include python3.11

Coverage: 87.396% (+0.7%) from 86.671% when pulling ed704986a97708ae4bada686e4f9e6831ebb604e on ci-py3.11 into bbbca9c9fcdf52290ec4d4add544bf3f02d33a0c on main.


Blender S64 importing plugin

Hello! Firstly, thank you for the spectacular work on this modeling ecosystem :)
I was wondering if you had any plans to write a Blender plugin to import S64 files?
I'm working on modding tools for the N64 release of Glover and the S64 format is perfectly suited to its actor data, but as-is I'm not sure if any modeling tools can read the format and it would be nice to have symmetry between the asset import and export workflows.

Hi, thanks for your interest in the project :smile:
I hadn't really considered it, especially because I've never messed with Blender's model import API. It can be done in the distant future, but definitely low priority for me.

Two years late on this, but I have basically begun work on an import plugin: f7c7417
Apologies for the silence, but I have been finishing my Masters degree, so I put all of my personal project stuff on hold until that was done. Now I'm tackling some Sausage64 stuff to get back into the swing of doing N64 related work, and this is something I'm currently working on.
The commit I made will read and parse the S64 file perfectly, now I just need to actually make it generate the meshes in Blender, and to animate them.
Now, since the S64 exporter doesn't export everything, the import process is somewhat lossy. One thing that isn't exported currently is bone parenting, because the library was designed to avoid the matrix stack in order to work around potential stack depth limitations. However, importing bones which aren't connected to one another is less than ideal for most people, so I'm going to have to modify the exporter to add a PARENT keyword to the mesh data in order for me to be able to connect bones. I won't be making long bones, however, I'll be doing something similar to what the Source Engine importer does where bones are made into spheres:

Amazing! Welcome back :) . My modding tools are on hold themselves, but it's good to know this will be there when I get back to them!

Finished as of 9122abc, tested working in 2.7 and onwards. As explained, due to the S64 format, bone parenting information is lost, as well as texture data (meaning you have to re-assign the images to the materials). Everything else should work as expected (UVs, vertex colors, animations, etc...).


Parse TLS mode from ALS

Set up TLS mode property to Service and instance relationship source, which intends to parse TLS mode from envoy AccessLog.
The type of TLS mode is "String"  instead of "Enum" due to the issues of variable receivers. In this PR only ALS relevant TLS mode is supported. Tracing or other analyzers might adopt to different terms to identify TLS mode.

Waiting for https://github.com/apache/skywalking-data-collect-protocol/pull/32


Docker builder update

added pgmodeler plugins support
added Github action to generate pgmodeler build (user can directly download pgmodeler build from Github actions pages). (In the next step we can add automatic release build)
By default build for latest source unless user specifies version tag
Update DockerFile syntax

Just hold this pull request for sometime. I need to check the Github action result too with latest changes.

Thanks very much for the contribution!  One thing about the GitHub Actions script, I assume the purpose is to automatically build pgModeler and host the binaries on this project?  I have a (minor) objection to that.
Let me explain why I made this project... I wanted to make it simpler to create binaries for pgModeler because I had purchased it once in the past and then was unable to download a new or even old copy after trying to do so a year later.  But I understand why Raphael (pgModeler's author) is doing what he's doing.  He wants to keep the project open source but if he makes it too easy to get binaries fewer people are going to pay for it.  I want to try and respect that by not making it too easy to get binaries.

Yeah. I had the same thought initially but then I though normal user won't be able to traverse Github action builds. That is why there is no mention of these builds in the Readme section. But OK I think you are right automatic release builds should be avoided.
I will update this pull request to remove automatic builds.


Fix shader preprocessor include resource check

Fixes https://github.com/godotengine/godot/issues/73925
This extra check is needed because both Shader and ShaderInclude implement their resource loader (which gets eventually called by ResourceLoader::load()) in a somewhat strange way comapred to many other loaders. Neither loader can never really "fail" and they don't check for any errors, they will always return a valid resource, but with empty text content. In short, previously almost all include paths "worked" even if the file did not even exist and these places simply included an empty string without raising any erros.
A more fundamental fix would be to add error checking to both resource loaders, but that would be a high-risk fix as much of the exisiting codebase might not be prepared for these loaders to suddenly start returning null resources.
I can make a separarete PR to add error checking if that sounds like a good idea. It could be tested and merged later when 4.0 is out and there is more room for risky changes.

Thanks!

Is this related to shaders precompiling?
In rc5 I was getting lag when a shader appeared. In rc6 that seems to be fixed for me.
So that's good


Regarding Value of Long Object conversion to JSON

In Java, if I want to convert a Long value greater than<PHONE_NUMBER>740991 to JSON, then it's not working.
If I put value<PHONE_NUMBER>740993 then it's rounding to<PHONE_NUMBER>740992.


Add commands for worker build id based versioning

DRAFT until SDK portion is merged
What was changed
Add commands to interact with the new versioning feature: https://github.com/Sushisource/proposals/blob/83dce63ad681d8dccc9fb2f6996304942a7ca04e/versioning/worker-versions.md
Why?
This is likely the most common way users will interact with the version graphs
Checklist

Closes https://github.com/temporalio/cli/issues/165

How was this tested:
Manually verified

Any docs updates needed?
Will need corresponding docs changes

Closing in favor of https://github.com/temporalio/cli/pull/166


chore: Only show published heroes even for admins DIA-75

Quick little PR to reverse the behavior of the app from including unpublished hero units to excluding them even for admins. My thought was that they would want to see them so that they could do QA but web is sufficient for this. More chatter here:
https://artsy.slack.com/archives/C054P6V8HQQ/p1689948709667389
https://artsyproduct.atlassian.net/browse/DIA-75
/cc @artsy/diamond-devs

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against eacded185d9bba54bbd29d8d64c515ee2f1bf77c

@jonallured please don't remove the PR template, we use some automation to get the changelog for the release, we aim to help release captains with it(#superImportant).

@araujobarret hrm but I have my own PR template... 🤔

Why don't you use the template of the repo? 😂
We need to rely on the current template because of the automation and the release process we have, otherwise, we make the release captain tasks harder when comes to collecting changing, ping all teams related, condensing release notes and etc.

I open my PRs from the command line and included in the arguments to that PR is a standard template that I use for all my Artsy PRs. I will try to remember this and open Eigen PRs from the GitHub UI but I wish the automation could be achieved another way...


Fix issue where timestamps could be erroneously converted by strtotime

Ticket: #1085
Reviewer: @jarednova
Issue
Bug in the date filter where some timestamps were being dubiously evaluated with strtotime() instead of their actual value because some timestamps can be interpreted as differing dates by strtotime, such as strtotime('1457395200') =><PHONE_NUMBER>59.
Solution
Only use strtotime on numeric values that are 8 characters in length (assuming they will be in format YYYYMMDD).
Impact
Timestamps that are 8 chars in length will suffer, but this is preferable to previous behaviour. Most dates in WordPress will probably not be timestamps
Testing
Added a test with a timestamp that strtotime will interpret as a valid, different date.

Coverage increased (+3.2%) to 91.694% when pulling a4b1a80486a6e30664909c9bf5ee87d7026f8613 on thedamon:1085-fix-date-bug into 1871b873c4eaa6ba9e89693ad6998181b23213e8 on timber:master.

@thedamon as I understand the risk of this is that if someone had an 8-digit timestamp from the early 70s (It seems between 4/26/1970 - 3/3/1973) it will result in an error. Yes? Or anything else I'm missing?

@jarednova yes.. though it's not a new problem.
Not sure any way to know for sure whether 19970402 should be treated as YYYYMMDD or a timestamp without further information. the current code would treat it as YYYYMMDD as well.

Sounds good — I'll review over the next few days and merge in!

Thanks @thedamon — this will go out in the next releasse!


CASSANDRA-13112 Populate rows in test_multidatacenter_local_quorum so that read_iteration_delay property takes effect

This test was added for CASSANDRA-13074 and multiplexed to make sure it would pass.
Unfortunately, this multiplex run took place before CASSANDRA-13050 was committed, which changed the behavior of the read_iteration_delay property such that it didn't take effect for reads that returned empty results.
We need to populate data to be returned by the selects. A multiplex run here shows the test passing on trunk 100 times after this PR. I also tested it on 3.X and 3.11 locally.

+1


Global Filter with Paging

When using global filters with paging (take/skip) the the generated SQL looks something like:
SELECT *
FROM (
SELECT *  FROM GL.Account   ORDER BY   Id asc  OFFSET 0 ROWS FETCH NEXT 50 ROWS ONLY
) AS [t]
WHERE [t].[CompanyId] = 1
ORDER BY [t].[XPath]
As Noted from above the filter applied to the outer query which means that the inner query will fetch first 50 records regardless of their tenant or companyId, you may have thousands of records for company 1 and get only 10 records from above statement because the first 50 recrods has 40 records in other tanant and only 10 records from filtered company.
Further technical details
EF Core version: 2
Database Provider:  Microsoft.EntityFrameworkCore.SqlServer
Operating system:  Windows 10 x64
IDE:  Visual Studio 2017 15.7

This issue is lacking enough information for us to effectively reproduce. Please post a runnable project/solution or complete code listing that demonstrates the behavior you are seeing.

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.


Failed to start dhcpd : start: Job is already running: isc-dhcp-server

Button "start dhcp" always write "Start Server"
On pressed write:
"Failed to start dhcpd :
start: Job is already running: isc-dhcp-server"

What do you get in Gray Theme?

Could you please tell me what do you get in Gray Theme?

I am sorry for such a long answer. In Grey theme similar mistake. it's not
your bug ;)
вс, 3 июл. 2016 г. в 20:04, Ilia Rostovtsev<EMAIL_ADDRESS>
Could you please tell me what do you get in Gray Theme?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/qooob/authentic-theme/issues/502#issuecomment-230163610,
or mute the thread
https://github.com/notifications/unsubscribe/ADSdXBV6ZnydoBBGhOt9-GQgaS9hbde0ks5qR-uggaJpZM4JDByj
.


python-flask: Bump stack version to put src and image in index

Checklist:

[x] Read the Code of Conduct and Contributing Guidelines.

[x] Followed the commit message guidelines.

[x] Stack adheres to Appsody stack structure.

Modifying an existing stack:

[x] Updated the stack version in stack.yaml

We made some changes to the behaviour of appsody stack create and appsody stack package in the last release. Now, when you package your stack the fully qualified image is put in the index.yaml along with the source url of the stack. The latter will enable people to copy non public stacks when they run appsody stack create. This PR just bumps the version to put these values in.
cc @henrynash - Please take a look :)

LGTM


Could not connect to the server.

Issue Type: Bug
Start collaboration session fails.
Either using Code or Web browser login.
Error is the same:
Starting collaboration session: Could not connect to the server. Check that you are connected to the internet.
Source Live Share Extension.
Extension version: 1.0.1245
VS Code version: Code - Insiders 1.41.0-insider (1c9fd8a59787487ca71d8c5ce140569a0e036a15, 2019-11-19T06:28:41.868Z)
OS version: Windows_NT x64 10.0.17763

Hi, thanks for reporting the issue and attaching your logs. I think you are behind the proxy.  Please refer to the following documentation. Please let us know if it doesn't help https://github.com/MicrosoftDocs/live-share/blob/master/docs/reference/connectivity.md

Closing as no more activity


Cancel download without producing resume data in tmp folder

[x] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

What did you do?
We are using DownloadRequest and are calling its cancel-method when the user explicitly cancels the download. This method is calling the cancel(byProducingResumeData on URLSessionDownloadTask which will move the partially downloaded file to the tmp-folder.
What did you expect to happen?
I would like to have a way of cancelling this download request without producing the resume-data.
What happened instead?
I need to import Alamofire with @testable and call the URLSessionDownloadTask's cancel explicitly for this to not happend.
Alamofire Environment
**Alamofire version: 4.8.2
**Xcode version: 10.2.1
**Swift version: 5
**Platform(s) running Alamofire: iOS
**macOS version running Xcode: 10.14.5

You're right, there's no way to cancel a DownloadRequest without producing resume data. This was done under the assumption that anyone cancelling a download would want to resume it in the future, if possible. Unfortunately it's not a behavior we can change for Alamofire 4, as other users may be depending on it. For testing, I would suggest clearing your temp directory between test runs if you want to cleanup this file.
For Alamofire 5, we could make this behavioral change, both to match URLSessionDownloadTask's behavior, and because the current cancellation behavior is a bit awkward to use without a callback when resume data is available. Users have to access it in response handlers, which is non-obvious. I have a callback version in my inline-docs-update branch, but both versions still produce resume data. @cnoon Any thoughts on this? I can easily make cancel() not produce resume data and have a cancel(byProducingResumeData:) with an optional closure, but that changes a fundamental behavior Alamofire has had for 5 years.

Seems like something we should probably support IMO. I think your suggestion @jshier is probably the best approach. Let users call the Request.cancel() API if that's what they actually want, then add a resume data variant on DownloadRequest that has the exactly same logic currently, it just calls the completion when finished generating the resume data.

What are the odds that a function i.e. cancel(createResumeData: Bool = true) will find its way into Alamofire 4.8.2? Would this be a candidate for a PR? By adding that parameter, no unexpected behaviour will appear for users as long as the parameter defaults to true

Is there any possibility for this PR to be merged into 4.8.2?

@jshier Any updates on this? We need it desperately and have problems using our fork together with AlamofireImage and other add-ons.

We do plan to do a 4.9 release with this change and some bug fixes just before our 5.0 RC1 release. I'll see if we can accelerate that release, but we're in the midst of finalizing 5.0 RC1, so there isn't much free time.

I understand, thanks for the reply! I look forward to both the RC and the 4.9 release 👍

This has been released as part of 4.9.0 and is already in Alamofire 5. Thanks everyone!


[Autocomplete] Fix maker autocomplete field template path

Q
A

Bug fix?
yes

New feature?
no

Tickets
-

License
MIT

Thanks - fixed already in #611... I just wasn't at a computer when I originally approved that (then, holidays).


Automate Accepting EULA LICENSE in case of Devops requirement

setup-environment.sh is having manual steps for accepting the EULA fsl license.

@johnweber can you please help me on this

We want some hack to automate this since in the case of DevOps manual accepts of license is not possible

@ankit-lathiya :
The step can be skipped by putting ACCEPT_FSL_EULA = "1" in conf/local.conf
BR,
Richard


Windows Magnifier not following text caret when accessibility support is enabled

VSCode Version: Code 1.48.2 (a0479759d6e9ea56afa657e454193f72aef85bd0, 2020-08-25T10:13:11.295Z)
OS Version: Windows_NT x64 10.0.19041

Steps to Reproduce:

Launch VSCode and make sure accessibility support is enabled.
2.open/create a file. The file should be on multiple lines with decent length of lines. IE settings.json.
Launch magnifier, and ensure that it is set to follow the text cursor.
Try to navigate the file without editing it (IE with just the arrow keys).

Expected behaviour

Magnifier should follow the caret as it moves.

Actual behaviour

Magnifier may initially follow the caret, but will drift away from it over time.
Inserting new characters seems to reset the detected caret position to the actual one, but deleting characters doesn't.

I conjecture that this is because the textbox used for the accessible editor isn't properly syncronised with the displayed editor, but I'm not familiar enough with the internals to know for sure.
There are a number of closed issues for this bug, but, testing both in stable and nightly, I am still experiencing it.

Does this issue occur when all extensions are disabled?: Yes

@SaschaCowley thanks a lot for filling this. I can reproduce this.
The textbox used for the accessible editor is properly synchronised with what is displayed - we always properly update the cursor position (otherwise many more things would be broken).
I just checked and this works fine with just Chrome 83.
So I believe that what is confusing the Magnifier is that we are hidding our textArea.
Alternative would be that we are just putting a subset of the whole text in the textArea but that can be controlled via accessibility.pageSize setting and changing that did not help.
I am also open to ideas.
@alexdima might you have some idea, I know you tackled similar issue in the past.

It looks like we have a regression from #83276 , I'm not sure what has changed.

@alexdima I can look into all the changes and do some bisection.

Just investigated a bit more and actually nothing changed. It seems like the original issue was not fixed when "editor.accessibilitySupport": "on" in settings. If accessibilitySupport is disabled then all works perfectly both then and now.
I have verified that the issue is here. If we return TextAreaState.EMPTY then all works fine (and that is the case when accessibilitySupport is turned off).
@alexdima I see the method getScreenReaderContent is only used here but I do not know how that would influence the behavior of the magnifier. Might you have an idea?
I thought that there might be a problem because we write a subset of the actual editor content to the hidden textArea, however I can reproduce this problem even if I increased the editor.accessibilityPageSize setting so that we would write the whole editor content.

@isidorn I'm sorry, I don't really know. I can speculate that perhaps the textarea is positioned at the cursor location, but the text inside the textarea overflows the 1px by 1px textarea and the native cursor is somewhere else. And perhaps the magnifier follows the native cursor?

@alexdima no worries. Good ideas. I will investigate further in debt week.

I have investigated a bit more into this and this is happening because as Alex suspected the cursor overflows out of the hidden textArea content. Windows Magnifier follows the cursor that is outside of the textArea and since the native curser is off the whole magnifier gets off.
I sent some email to the magnifier team and we can see if they have ideas on a work around in vscode on how to tackle this. We basically need to tell the magnifier to follow our cursor and not the native hidden cursor.
In the meantime, the workaround for this issue is to set the following setting
editor.accessibilityPageSize: 2

Any news on this @isidorn ? I reported this as well #77842 last year.

@coryj627 unfortunately no news, the Windows Magnifier team did not yet respond to my email. I will ping them again.

I use ZoomText and Fusion, from AI Squared and Freedom Scientific, as screen magnifier. The behavior is exactly the same as described. I thought it was a specific problem of these softwares, but now I see it's related to VS Code.
Cursor tracking works perfectly when editor.accessibility is off, but it causes VS Code to be unaccessible to screen readers like JAWS or NVDA. Yes, I'm parcially visual impared, so I use both screen reader and magnifier.
It would be great if this issue was solved.
Maybe you could try to get in touch with AI Squared and Freedom Scientific to get some help about this issue. They have a lot of experience about accessibility.

@rafa11rodrigues I suggest to use the workaround for now In the meantime, set editor.accessibilityPageSize: 2 in your vscode settings.
I just emailed AI Squared and Freedom Scientific, however let's also check with @ggordon-vispero if he knows how do magnifiers follow native cursors and if VS Code could tell the magnifier to follow our cursor and not the native one.

I am trying to reactivate this issue, it is important, is ruining my experience for sure.
I am using both screenreader and magnifier together, and this cursor tracking issue is annoying when you want a smooth experience.
@isidorn you said in #149166 " this is one of those issue that we should invest in the future. I could not get far when contacting the magnifier software people to try to figure out how the magnifier follow the native cursor and if we could "trick it"."
I would appreciate your help in raising this issue, and get it solved finally.
can someone do something about that, it cannot be left unsolved, it's a serious UX issue.
VS team is doing great job regarding accessibility issues, someone needs to investigate this properly.
Is it possible to escalate this issue a bit, it seriously important, of course is not a major problem, but it breaks the experience as I mentioned previously.
@isidorn @@alexdima @kieferrm @Tyriar I would appreciate your help and input.

@snufas we have plans to fix this issue, and as we get more details I will comment here.
Thank you.

@isidorn  Please give more priority to this issue, it is very annoying to code while using magnifier... Because I cannot use magnifier  properly in VS code, my back actually hurts... I have to  use VS code more and more, and it is very annoying now to be honest, please track  it down and fix that issue.
I have to say most of the issues are fixed very quickly, but not this 1...
I am asking as a developer, please make my job easier, and save my back from pain, seriously... How much do I have to mention this issue until it's fixed???
I would really, really, really appreciate if this issue get some priority, because I will repeat myself again, it's getting very annoying, because I have to use this editor more and more daily.

@snufas thanks for your feedback, as I mentioned above we do have plans to fix this, however the issue is not trivial. Let me assign it to September for an initial investigation.

@isidorn  Thanks

@isidorn I do not have my windows computer with me. Could you pls test this on Windows given we think it might now be fixed?

I have just tried it out on my windows machine and the issue seems to be fixed for me. With the caveat that the following setting has to be set "editor.accessibilityPageSize": 1.
User that hit this issue can you please verify if the issue is indeed fixed for you. You can tryout vscode insiders https://code.visualstudio.com/insiders/ or wait for the stable release next week.
I am going to go ahead and close this issue, and if you still see the issue we will reopen. Thank you!

@isidorn @meganrogge  The .scrollTop inside the <textarea> is currently only set on mac. If we would set it on all OSes I think that would help with the need to define "editor.accessibilityPageSize": 1

Thanks! Created a follow up issue https://github.com/microsoft/vscode/issues/164591

@isidorn
This issue is not fixed, because tracking doesn't work using left and right arrow keys. The cursor tracking works fine when you use
Up
Down
ctrl + up,down, left, right.
But doesn't work when you use left and right arrow keys on its own. So basically, the tracking does not work when you go through the code letter by letter.
As you understand, it is quite an issue when you're trying to edit the existing code...
I recommend to reopen this issue and keep it open until it's fully resolved.
I have the latest VS code stable release running.

I just updated VS Code to last stable release, and it doesn't work even with ctrl+arrows.
The issue is more evident when you have a long line. For example:
def foo():
    return 'Lets have a very long line to check if cursor track works fine with screen reader and magnifier enabled'

When I was typing, it worked perfectly, the screen moved so I could see the exact position of the cursor. But after typing, if I move by letter or word, it moves to somewhere else. Also happens when I try to select (holding shift).
And the most weird part is that the internal cursor looks to follow the blinking carret. I use JAWS as screen reader and ZoomText as screen magnifier, and ZoomText has a focus enhancement to highlight where the system cursor is. Before the VS Code update the highlight always got stuck at the first character of the line, now it's moving correctly following the blinking carret. But somehow the screen doesn't follow it correctly...
Why cannot it work as a regular text box? Even in Java applications the cursor is tracked correctly, and Java accessibility is a mess...

Hi @isidorn is there any update on work for this issue? I asked 2 years ago, and this issue is even older than this ticket. :(

@coryj627 no updates. I agree we should do another investigation here. I will try for us to get it on the plan again. Thank you

@meganrogge pushed a fix for this issue. We have verified that this indeed improves the behaviour of ZoomText software on Windows.
Please try it VS Code Insiders from next Monday (23 October) and let us know if this is indeed fixed for you. Thank you 🙏


Specify Type for ProducesResponseType

Later in the article, this is highlighted as one of the differences between using IActionResult and ActionResult

@rahulpnath  why update the 2.1 sample?

@rahulpnath  why update the 2.1 sample?

@scottaddie @wadepickett @guardrex  this build error was announced on teams and is being investigated.

@scottaddie @wadepickett @guardrex  this build error was announced on teams and is being investigated.

@rahulpnath why update the 2.1 sample?

The doc here uses that file to render the code. Am I missing something?

@rahulpnath why update the 2.1 sample?

The doc here uses that file to render the code. Am I missing something?

@Rick-Anderson From what I understand, the doc does not have a 3.1 version for that part of the code.

@Rick-Anderson From what I understand, the doc does not have a 3.1 version for that part of the code.

Thank you for fixing this, @rahulpnath!

Thank you for fixing this, @rahulpnath!


Extension doesn't work with overlay_support package

Hello,
I have been using your package for 2 months and I am very satisfied.
However I realized that by adding the overlay_support package, the rebirth method had no effect. Do you know why?

Hi,
I finally found a work around, see below

Instead of put Phoenix around MyApp, I put it around MaterialApp.


legislators-historical.yaml: Add missing Congresspeople

This was scraped from congress.gov/members. It just gives the term
years, so I just put '01-03' for the month/day.

There are no missing congresspeople in our data. The legislators you added are currently serving and so are in the legislators-current.yaml file.

Ooops.