[Bug] Windows application has stopped working

Bug Description
Displays an error
  "error": true,
  "message": "Failed to fetch"
}

Steps to Reproduce

Open applications
type something in the new chat

Expected Behavior
Returning response
Screenshots

Deployment Method

[ ] Docker
[ ] Vercel
[ ] Server

Desktop OS
Windows 11 NextChat v2.11.3
Desktop Browser
No response
Desktop Browser Version
No response
Smartphone Device
No response
Smartphone OS
No response
Smartphone Browser
No response
Smartphone Browser Version
No response
Additional Logs
No response

Same issue under Windows 11, worked before

Thank you for your feedback，we're dealing with it as a matter of urgency, and will be back soon

We had some issues with our deployment, which has now been restored


@case without brackets doesn't work

Laravel Version: master
PHP Version: any

Description:
@case without brackets doesn't work
Steps To Reproduce:
Run the following test:
<?php

namespace Illuminate\Tests\View\Blade;

class BladeSwitchTest extends AbstractBladeTestCase
{
    public function testCaseWithoutBrackets()
    {
        $this->assertEquals("<?php switch(\$a): case 1: ?> <?php endswitch; ?>", $this->compiler->compileString("@switch(\$a) @case 1 @endswitch"));
    }
}

bracket is mandatory yes.


How can I get the datasets?

Thanks for your excellent work on prostate segmentation, I am interested in your work and would like to implement it, could you please do me a favour for giving me access to the dataset.

Unfortunately, due to privacy concerns, we are currently unable to share our dataset. However, I would like to suggest that there are a few open-source datasets available online that might be of interest to you. Thank you for your understanding!

Thanks a lot for your reply. Could you please give me any information about the open-source datasets you mentioned above, I would be very appreciate.


RFC: deref coercions

Add the following coercions:

From &T to &U when T: Deref<U>.
From &mut T to &U when T: Deref<U>.
From &mut T to &mut U when T: DerefMut<U>

These coercions eliminate the need for "cross-borrowing" (things like &**v) and calls to as_slice.
Rendered

:+1: I had the same initial concerns, but the more I think about this while being annoyed at writing '&*' or '&**', the more I like this proposal.

Is this going to be merged? Going from a Vec<T> to a &[T] has recently suffered an ergonomic regression; it used to be that one could write x[], but now it's &x[]. This "both ends" syntax is really unfortunate with long expressions like &foo.bar(y).zoo(z).goo(w)[] (extra painful when split across lines); one's eye has to go backwards and forwards to find the relevant syntax.
With this RFC, we get &x which is arguably even nicer than x[]. Certainly shorter (1 char vs 2).

@Valloric since Vec derefs to a slice you can just do &*foo.bar(y).zoo(z).goo(w) or foo.bar(y).zoo(z).goo(w).as_slice().and have it only on one side of your choice, and I imagine your case is relatively rare since you usually want to store a Vec returned from a bunch of methods somewhere or it'll get dropped immediatelly and your slice will not live long enough.
I oppose this RFC because I don't think having to type as_slice less often is awesome enough to make the semantics of & more complex.

I was +0 when I first read this, but since then I’ve repeatedly written code that would have been nicer with it. Big +1.

@Thiez Syntax like &*foo would rightfully produce a WTF-stream from any Rust newcomer. It's not the API we should be proposing for a common operation like taking a slice out of a vector.

@Valloric And syntax like &'a foo would also produce a WTF-stream. And syntax like |&: n| { ... }. I think once a person understands the basics of pointers in Rust, (which are quite simple: & creates a reference, and * dereferences) and knows about Deref they should be able to understand &*foo, because it is very simple and works exactly how one would expect.
If you're going to learn a new language, you have to learn the syntax. That is not a bad thing. And while the syntax certainly shouldn't be made more complex that it needs to be, I don't think making the semantics of & more complex is going to make the language easier to learn.

+1
2015年1月14日 上午7:19于 "Val Markovic"<EMAIL_ADDRESS>
@Thiez https://github.com/Thiez Syntax like &*foo would rightfully
produce a WTF-stream from any Rust newcomer. It's not the API we should be
proposing for a common operation like taking a slice out of a vector.
—
Reply to this email directly or view it on GitHub
https://github.com/rust-lang/rfcs/pull/241#issuecomment-69841077.

+1
This RFC seems like it manages to retain enough explicitness while making a relatively common task simpler to write.
I have one question though, given T: Deref<U> if a function takes a generic which is impl'd for both T and U, and I pass &T, does it result in ambiguity or simply take the option with the least derefs?

There is an implementation now, and there seems to be a lot of positive sentiment for this change, should we push forward with it?
@aturon are there any open questions you're aware of? (I haven't re-read the whole conversation here, but I will if we are going to move on to this. But I'm mostly checking you don't have any new concerns which aren't already here).
I'm still a little uneasy about the 'searching' aspect of the coercion, but I think it is worth it for the ergonomic benefit.

@retep998

I have one question though, given T: Deref<U> if a function takes a generic which is impl'd for both T and U, and I pass &T, does it result in ambiguity or simply take the option with the least derefs?

The & operator by itself keeps the same meaning it has always had: it gives you a &T. The only time the deref coercion kicks in is if you then use this &T value in a place where some &U is expected an T != U.

@retep998
Note that this is one reason why the slice syntax &v[] is still desirable: when you're invoking a generic function and want to pass  a slice, not a reference to the vector.

@nick29581
Yes, we're ready to move forward with this; this way we can gain some experience before the beta.

Note: this RFC has now been merged, after some significant digestion on all our parts :-)
I won't recap the motivation/arguments here, which are well-represented in the RFC and thread. However, I will note that an implementation is nearly ready to land, and so we should have time to gain some experience here before shipping beta.


PHOENIX-2256: Correct two bugs in PMetaDataImpl

PHOENIX-2256: More entries than necessary could end up being evicted.
This PR also adds a new test to catch one of the bugs.
Previously, one of the bugs (> should have been >=) was being picked up on Java 8, but not Java 7, because the traversal ordering of one of the JDK collections happened to have changed. The bug was still present in Java 7, but the collection ordering meant that the test didn't pick it up.
The second bug (if should have been while) is picked up by the new test on both Java 7 and Java 8. The essence of the bug is that if several things are queued for eviction, and something large and old gets added to the eviction queue, the implementation was only considering removing one element from the eviction queue, whereas it should have removed as many as possible from the eviction queue while still leaving enough to clear space for the new element being added to the table.

+1 to the patch. Thanks for the contribution, @chiastic-security. I've pushed it to master and will push to other branches soon.

Thanks. Did this get pushed? The PR is still coming up as open in github.


⚠ Bofrost.de has degraded performance

In 9c7e678, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2364 ms

Resolved: Bofrost.de performance has improved in 3cdaaed after 6 minutes.


Project setup

Steps Taken

Created a new branch from the main branch
Created a github workflow and configured it
Created a .gitignore file and included node_modules
Installed and configured the linters
Created an HTML file with header
Added a CSS file and linked it up with the HTML file
Added a test.md file and included it in the .gitignore

Thanks for the review. The changes will be implemented immediately.


Support passing a callback to .resolves()

Currently, you can only pass a static object to .resolves(). This is okay if your requests contain different input you can match on, but if you want to pass different results for two calls that use the same input, I don't see a way to do this currently.
Allowing a function to be passed instead of an object would allow tests to do things such as returning an error for the first request, but returning a success response when that request happens a second time.
I would think this could be a quick addition, but I'm quite bad with typescript, so I'm hoping someone else can submit a PR for this

Passing callback would be a nice addition, I think I can add this.
For now:

if you want custom logic, you can use .callsFake()
if you want different responses on next calls, you can use the solution from here

I couldn't find a solution of how could I reject conditionally, not just resolve. I assume it should look like this?
snsMock
    .callsFake(input => {
        if (input.Message === 'Bob') {
            return {MessageId: '12345678-1111-2222-3333-111122223333'};
        } else if (input.Message === 'Lisa') {
            return {MessageId: '12345678-4444-5555-6666-111122223333'};
        } else {
            throw new Error('not found');
        }
    });
    ```


add support for setting saved view in set-view operator

What changes are proposed in this pull request?
add support for setting a saved view with the set_view built-in operator
Usage: setting a view using the name of a saved view
def execute(self, ctx):
    ctx.trigger("set_view", {"name": "my-saved-view-name"})

How is this patch tested? If it is not, please explain why.
Using an example operator with a snippet above
Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[ ] No. You can skip the rest of this section.
[x] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

add support for setting a saved view with the set_view built-in operator
What areas of FiftyOne does this PR affect?

[x] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[ ] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

Thanks @manivoxel51! Yes, the URL slug as well as the saved view dropdown selected state changes when this operator is invoked


Di, fixed resolve bug

if pass array of class name with parameters array, it'll not work as expect.
fail case: $di->resolve(['Ice\Test' => [1, 2, 3]])

php -r "$a=[1];var_dump($a=='array');"
bool(false)


Can not apply plugin in configure block

configure(subprojects - listOf(project(":PlexxiCorePythonAPI"), project(":PlexxiInstall"))) {
    apply {
        plugin("java") // This shows up as an error in intellij
    }
}

The current workaround is to do this:
configure(subprojects - listOf(project(":PlexxiCorePythonAPI"), project(":PlexxiInstall"))) {
    apply(delegateClosureOf<ObjectConfigurationAction> {
        plugin("java")
    })
}

Blocked by #157

The original code is correct and works even though IntelliJ marks it as an error.

Resolved in a7308886672047171bcddcb9979c0a22295f925f.


usable on pancakeswap?

hi, can we use it for trading on panckaeswap?

No, this is for binance chain, not smart chain


Bug: Promise Not Resolved: W/AppAuth: No stored state - unable to handle response

Capacitor version:
 "@auth0/angular-jwt": "^4.2.0",
 "@auth0/auth0-spa-js": "^1.9.0",

Run npx cap doctor:
   @capacitor/cli: 2.1.2

  @capacitor/core: 2.1.2

  @capacitor/android: 2.1.2

  @capacitor/electron: 2.1.2

  @capacitor/ios: 2.1.2

Library version:

2.0.0

OAuth Provider:
Auth0
Your Plugin Configuration
{
    appId: '3vRB3......',
    authorizationBaseUrl: 'https://.../authorize',
    accessTokenEndpoint: 'https://.../oauth/token',
    resourceUrl: 'https://.../userinfo',
    responseType: 'code',
    redirectUrl: 'com.####.######://home',
    pkceEnabled: true,
    scope: 'openid profile',
    state: null,
    additionalParameters: {
      nonce: nanoid(),
      audience: 'https://###.####.com'
    },
     android: {
      appId: '3vRB3......',
      responseType: 'code',
    redirectUrl: 'com.####.######://home'
    }
}

Affected Platform(s):

Android
Emulated with Android Studio

Current Behavior
I call onOAuthBtnClick() on button click per the "Use it" instructions.
In the console, I get:
D/Capacitor: App Stopped
D/Capacitor: Saving instance state!
The app is redirected to the Auth0 login flow.  I enter valid credentials and log in.  I check the Auth0 log and it shows a successful login.
The console now shows:
D/Capacitor: App Restarted
D/Capacitor: App Started
W/AppAuth: No stored state - unable to handle response
...
D/Capacitor: Resumed
...
The app has redirected to the configured redirectURL, but the promise is never resolved/no promise error either.
Interestingly enough, no matter what redirect URL I use, it always goes back to the initial page.
Expected Behavior
I would expect the promise to be resolved so that I can check the state of the response object for the token.
Sample Code or Sample Application Repo
Reproduction Steps
Angular 9.1.9 app, using Capacitor + this plugin.
Other Information

My fault.  My eyes skipped over the "Register the plugin" example, because I thought I did that in the AppComonent.
Just needed to register the plugin in class MainActivity.


min temperature to high

Version of the custom_component
0.1.11
Describe the bug
in Gecko App the min temperature is 8C in HA its 15C. because i dont use my Spa in Winter i would lover to save the Power to keep it that warm. Anything is setting it back to 15C after using Gecko App to Set it to 8C

+1

What spa pack do you have? Mine won't go below 15C (59F), even using the topside.
8C seems a bit risky, and the pumps probably will have to come on for their freeze protect cycle more frequently, as the water in the plumbing typically cools the fastest when the pumps are stopped. Also keep power outages and equipment failure in mind. The lower set temp does not give you much "buffer" time before freezing occurs.
If you really want to go lower, open the climate.py file for the integration and change self._automation_entity.min_temp to the literal number that you want to use as the minimum, then restart HA.

My Spa is a Swimspa with 7500 liters and extra isolation. So the buffer time is not so critical like in normal Spas. Gecko is set to minimum 8 °C by the manufacturer.
But I'm new in Home assistant. I can find
homeassistant/custom_components/gecko/climate.py
But there is no 15 inside, which I can change to 8.
Where am I wrong?

My Spa is a Swimspa with 7500 liters and extra isolation. So the buffer time is not so critical like in normal Spas. Gecko is set to minimum 8 °C by the manufacturer.
But I'm new in Home assistant. I can find homeassistant/custom_components/gecko/climate.py But there is no 15 inside, which I can change to 8. Where am I wrong?

I am not too familiar with the code, but self._automation_entity.min_temp should be the value returned by the library used by the integration. Instead of using the value of 15, which would normally get returned, you would be replacing it with 8. I have never tested this in Celsius and decreasing it, but it should be the same process as when I did it with Farenheight and increasing it.

Let us know if it works. If you upgrade the integration to a new version in the future, you may need to make the change again.


Radar hack doesnt work when inside smoke

Radar hack doesnt work when I or the enemy is inside smoke

game mechanic. pretty sure that cant be fixed.

THIS IS AS THE GAME INTENDED AND WHEN WILL PEOPLE EVER LEARN ABOUT THIS

THIS IS AS THE GAME INTENDED AND WHEN WILL PEOPLE EVER LEARN ABOUT THIS

Its still fixable

THIS IS AS THE GAME INTENDED AND WHEN WILL PEOPLE EVER LEARN ABOUT THIS

I mean you still get info about their positions all you gotta do is draw them on the minimap

I mean you still get info about their positions all you gotta do is draw them on the minimap
why, all what you have to do is just to hook draw points on radar func and disable "check if enemy is in smoke"

I mean you still get info about their positions all you gotta do is draw them on the minimap

why, all what you have to do is just to hook draw points on radar func and disable "check if enemy is in smoke"

ah that works thanks


fix: respect rueidisotel.MetricAttrs options, and avoid copy them repeatedly

Fixes #463

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

Comparison is base (3d21559) 95.66% compared to head (f3cfb13) 95.65%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #471      +/-   ##
==========================================
- Coverage   95.66%   95.65%   -0.01%
==========================================
  Files          63       63
  Lines       31765    31765
==========================================
- Hits        30387    30384       -3
- Misses       1184     1185       +1
- Partials      194      196       +2

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


Owner and Maintenance

Hey everyone,
I've been using sharejs for some time now, and I've seen that the maintenance and issue answering is not the greatest at the moment. @josephg seems to have stopped working on this pretty much right now, and I only see @nateps pushing some updates. For that reason I wanted to ask what the plans are for the future and if you plan on working more on it in the future.
As I probably use sharejs for the foreseeable future and already need to maintain a fork I wanted to ask if you might want some help, as I'd rather try and keep the main repos up to date then to maintain independent and ever more diverging forks.
//cc @josephg @nateps @nornagon

Thanks for bringing up the question. @josephg and I are going to sync up about it this week, and I'll send an update.

@nateps on that conversation?

bump.

Also curious about this.

@dbryand Check Joseph post here: https://groups.google.com/forum/#!forum/sharejs

@Dignifiedquire:

try and keep the main repos up to date then to maintain independent and ever more diverging forks.

Exactly. I agree, as I'll also be using ShareJS for a project for a while and be able to collaborate somehow. So the easier we can make to maintain, develop and move forward ShareJS (by far the most developed OT library out there) the better.

Hey all, thanks for the interest, and Joseph's post was indeed the outcome of our discussion. Joseph is going to own completing a new version of ShareJS that is single server only and a basic implementation to get a realtime editor up and running quickly. I'll be running with ShareDB, which will be a variant that will share as much as possible (particularly the same OT types), and it will essentially be the merging of what is currently LiveDB + ShareJS 0.7. I'm currently spending a good amount of time on ShareDB making it more scalable and efficient. Joseph is working on the new JSON OT type that is going to be a huge step forward. Going to close this issue, since it is resolved now.

So Devon Govett's suggestion of keeping everything modular is a no-go? I was really hoping to keep all components modular as well.

Modularity and sharing code is always a goal. We will share code where it makes sense and as much as reasonable without impacting the clarity and maintainability of the code.

@nateps seems like a good roadmap. Sharing the OT types and the modular goal it's wise.

Just another note. As ShareJS, OT and Derby gains momentum, I think it would be wise to continue the effort to keep the communication going between all stakeholders - when presenting and discussing ideas, roadmaps, API's, etc. :+1:


added check to update cookies config if it is not null

Description
Thanks for contributing this Pull Request. Make sure that you submit this Pull Request against the develop branch of this repository, add a brief description, and tag the relevant issue(s) and PR(s) below.

Relevant Issues : Getting PolyglotException when set cookies is null
Relevant PRs : (optional)
Type of change :

Bug fix for existing feature

@ptrthomas Added the same IF condition which was removed from below PR,
https://github.com/karatelabs/karate/pull/1965/commits/c7163a049d38bf8fcf25a426943bbe5b6865e1b9

@bipin-k thanks, but we won't accept a PR without tests or some decent explanation

closing as change already made, see #1983


moment('1_/__/____', 'MM/DD/YYYY').isValid() returns true

Hi, I think the title pretty much explains the issue.
Is it intended that below code returns true?
moment('1_/__/____', 'MM/DD/YYYY').isValid()

Yes.
Use strict mode if you don't want that:
moment('1_/__/____', 'MM/DD/YYYY', true).isValid(); // false

But what is the reasoning behind this logic?

Guessing: original developers had a choice between making the default parsing behaviour lenient or strict, and they chose to make it lenient.
It's too late to change the default behaviour now (as it'd break a lot of code.)

Thanks for the explanation ❤


Add a metric to capture how many times Dora falls back to UFS

What changes are proposed in this pull request?
Add a metric to capture how many times Dora falls back to UFS when opening files.
Why are the changes needed?
N/A
Does this PR introduce any user facing changes?
N/A

alluxio-bot, check this please

alluxio-bot, check this please

alluxio-bot, merge this please


There was a typo in docstr

for memory, the unit is MB
for disk, the unit is KB

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.374%

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
1663

Relevant Lines:
1820

💛  - Coveralls

I think we'd better use MB all time.

Sure I agree. Maybe we wrap up in alea (and also outsource) into MB-only units. We probably cannot do anything for Pegasus.

On Sep 4, 2024, at 7:54 PM, Dacheng Xu @.***> wrote:
I think we'd better use MB all time.
—
Reply to this email directly, view it on GitHub https://github.com/XENONnT/alea/pull/198#issuecomment-2330393269, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALG57AUW4HRSJFYQI7PHEG3ZU6TTNAVCNFSM6AAAAABNVMGU2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZQGM4TGMRWHE.
You are receiving this because you authored the thread.


for index block should have variable start

You should be able to change the start (0) to whatever number you want - otherwise, then we would have to add a constant whenever we reference index and do more math to determine the difference which is kind of annoying.

code.org:

I think that is good, but you could probably hide the count by {number} part behind an expanding thingamabob.


Development roadmap

Hey @gmazzap. I mentioned you in another WP framework project and in connection was wondering what the status of this templating project is. Feature complete? 0.7 coming some time or too busy? Did someone else produce something even better?

Hwy @lkraav
let me try to answer:

Feature complete?

Yes. I don't want to add features (not before going stable, which is still long), but there are things that needs to be done better.

0.7 coming some time or too busy?

Not coming soon. My time for OS is quite limited these days, and I actively follow few projects now. Foil is one of them, but if no one helps me here, I don't foresee room for much progress any time soom. 0.7 could happen in 2018, but hard to be more precise.

Did someone else produce something even better?

If you want to stay in the field of PHP templates, I think that Plates is the alternative. I build Foil because I had issues with that, but it is actively developed and more mature than Foil.


Big files are uploaded with broken permissions

Issue Summary
Files bigger than 2.48 MB are uploaded with wrong permissions and are not readable from /media/
Steps to Reproduce
Create two files with content size 2600000 bytes and 2700000 bytes. The second file gets its access rights mangled.
Reproducible for me on two separate installations.
wagtail 1.12.2, Django==1.11, python 3.5.2+ (ubuntu 16.10)
and
1.13. with python 3.5.3 (ubuntu 17.04):
django-analytical==2.3.0
django-compressor==2.2
django-redis==4.8.0
django-sekizai==0.10.0
libsass==0.13.3
psycopg2==<IP_ADDRESS>
wagtail==1.13.1
waitress==1.1.0
requests==2.18.4

This is how the files get saved in media
with the smaller ones working as expected:

Any ideas on how to resolve this issues or where to start digging?

Hey @5in4, thank you for reporting this. I'm not the best place to investigate this issue, but can definitely reproduce on Wagtail's bakerydemo Vagrant setup (Ubuntu 14.04.2 LTS):
-rw------- 1 vagrant vagrant 5233997 Nov 23 12:16 jeremy-thomas-98201.jpg
-rw-r--r-- 1 vagrant vagrant 1092783 Nov 23 12:16 nasa-53884.jpg

Django uses different internal representations of newly-uploaded files (in-memory vs. temporary file) depending on file size, so I guess this could be related to that...
I'd suggest seeing if this can be replicated outside of Wagtail - define a model with a FileField and set it up to be editable through the Django admin, and see if the same behaviour occurs there.

Did you try setting FILE_UPLOAD_PERMISSIONS?

I'm sure @BertrandBordage's hint is the right one. From the Django documentation:

If [FILE_UPLOAD_PERMISSIONS] isn’t given or is None, you’ll get operating-system dependent behavior. On most platforms, temporary files will have a mode of 0o600, and files saved from memory will be saved using the system’s standard umask.

I agree. If FILE_UPLOAD_PERMISSIONS doesn't help and testing with a FileField shows that this is Wagtail-specific, let us know and we'll reopen.


New Package-Profile-Page

As a customer
Iw ant to have an overview over my booked license
in order to adjust the package to my needs.

Closed in https://github.com/tactilenews/100eyes/pull/1549


Add Go win32_event_log check

What does this PR do?

Add a new Go implementation of the win32_event_log check, shares common code foundation with the Event Log tailer.
See https://github.com/DataDog/integrations-core/pull/16108 for the now deprecated implementation, and details on the legacy_mode and legacy_mode_v2 options.
Motivation

Part of effort to consolidate the event log collection implementations.
https://datadoghq.atlassian.net/browse/WINA-519
Additional Notes

The timeout option for the win32_event_log check is no longer applicable and can be removed. If the option is set the check will log a deprecation warning and ignore the option. https://datadoghq.atlassian.net/browse/WINA-515
The win32_event_log check now continuously collects and reports events instead of waiting for min_collection_interval and then collecting as much as possible before waiting again. min_collection_interval now controls how frequently the check attempts to reconnect when the event subscription is in an error state.
Possible Drawbacks / Trade-offs

Go uses a different regular expression implementation than Python, so while the rest of the configuration is backwards compatible with the legacy_mode: false options, some regular expressions used in the included_messages and excluded_messages options may not be supported. For example, Go regular expressions do not support lookahead or lookbehind assertions.
If any issues arise, set legacy_mode_v2: true to revert to the Python implementation of the check. However, this is a temporary fix as the Python implementation may be removed in a future version of the agent.
Describe how to test/QA your changes

Follow Events Tests QA plan
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

have to rebase main to pull in changes to mockConfig.Set


Include AbortController/Signal polyfill automatically?

AbortController/Signal needs to be polyfilled separately, before including the yetch polyfill. It's not currently included automatically because they aren't technically specific to window.fetch (just like Promises aren't). It was thought that perhaps they may already have their own preferred polyfill.
However, right now very few people will use AbortController/Signal for things other than fetch. My gut says it's very confusing to the average dev that they need to include the extra polyfill, and many not realize that even though we have warnings as such.
Should we include a polyfill for AbortController/Signal automatically? e.g. https://github.com/mo/abortcontroller-polyfill/
I imagine we'd import the CJS exports from mo/abortcontroller-polyfill, re-export them from the "main" and then do the patching of the globals ourselves if they use import 'yetch/polyfill'. That way we don't update the global if they just do import { fetch } from 'yetch'
Cc/ @jamesplease @stefanpenner

I suspect auto-including would make sense, "principle of least surprise"

However, right now very few people will use AbortController/Signal for things other than fetch.

This seems likely to me.

My gut says it's very confusing to the average dev that they need to include the extra polyfill, and many not realize that even though we have warnings as such.

Agreed.

I imagine we'd import the CJS exports from mo/abortcontroller-polyfill, re-export them from the "main" and then do the patching of the globals ourselves if they use import 'yetch/polyfill'. That way we don't update the global if they just do import { fetch } from 'yetch'

:+1: This approach sounds good to me.
Are you thinking that we would check for the existence of an existing AbortController/AbortSignal, and only patch them if they don't exist?


Write Terraform for the ReindexShardTracker table

📑

The reindex-job-creator is tested and working. \o/


various bug fixes

Hi,
I'm using Dr. Gadget with IDA 6.95 on Windows 10 and I encountered and fixed some issues:

there was a wrong reference to idaapi in gadgetfinder.py
the keyboard shortcut for placing comments didn't work

I plan on tackling some more issues and adding some functionality, please let me know where you stand on the subject.

Hi,
thank you for your contributions!
In order to make collaboration and maintenance a bit more convenient, may I ask you to separate bug fixes and new features from each other please? For new features, it'd probably also be a good idea to create a branch for each, so they can be merged individually:
https://gist.github.com/Chaser324/ce0505fbed06b947d962
If feasible, new features should also be implemented as an extension/plugin in order to keep the "core" code as minimal as possible.

Oh wow, this did not happen the way I intended x.x
I was originally planning to submit a couple of bug fixes, not this whole mess as a single PR.
I forgot that GitHub will try merge my master, wherever that is, and continued working.
I'll split this into small chunks and send them to you one by one.


add ollama build container to packages

adds ollama docker build to jetson-containers packages. test scripts hang on my system, but the containers build successfully.

@dusty-nv I could use some help with insight into the testing/build process if you have some time. I've created a PR to add an ollama package to jetson-containers. The container seems to build correctly but it keeps hanging on the test phase regardless of what I change in the test script or in the config.py file.
I removed the test.sh scripts from the Dockerfile and the config.py, but it still tries to load them and hangs and I have to ctrl-c to exit. I even let it sit for a couple hours once with no update to the command line.
Here's the end of the log after the build:
Successfully built 9fd96e933ff4
Successfully tagged <IP_ADDRESS>:5001/ollama-r35.4.1-ollama:latest
-- Testing container <IP_ADDRESS>:5001/ollama-r35.4.1-ollama (ollama/test.sh)

docker run -t --rm --runtime=nvidia --network=host \
--volume /home/tegra/ok3d/ollama-container/dev/jetson-containers/packages/llm/ollama:/test \
--volume /home/tegra/ok3d/ollama-container/dev/jetson-containers/data:/data \
--workdir /test \
<IP_ADDRESS>:5001/ollama-r35.4.1-ollama \
/bin/bash -c '/bin/bash test.sh' \
2>&1 | tee /home/tegra/ok3d/ollama-container/dev/jetson-containers/logs/20240404_165837/test/<IP_ADDRESS>_5001_ollama-r35.4.1-ollama_test.sh.txt; exit ${PIPESTATUS[0]}

root@ok3d-1:/test#

^CTraceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/tegra/ok3d/ollama-container/dev/jetson-containers/jetson_containers/build.py", line 102, in <module>
    build_container(args.name, args.packages, args.base, args.build_flags, args.simulate, args.skip_tests, args.test_only, args.push, args.no_github_api)
  File "/home/tegra/ok3d/ollama-container/dev/jetson-containers/jetson_containers/container.py", line 150, in build_container
    test_container(container_name, pkg, simulate)
  File "/home/tegra/ok3d/ollama-container/dev/jetson-containers/jetson_containers/container.py", line 322, in test_container
    status = subprocess.run(cmd.replace(_NEWLINE_, ' '), executable='/bin/bash', shell=True, check=True)
  File "/usr/lib/python3.8/subprocess.py", line 495, in run
    stdout, stderr = process.communicate(input, timeout=timeout)
  File "/usr/lib/python3.8/subprocess.py", line 1020, in communicate
    self.wait()
  File "/usr/lib/python3.8/subprocess.py", line 1083, in wait
    return self._wait(timeout=timeout)
  File "/usr/lib/python3.8/subprocess.py", line 1806, in _wait
    (pid, sts) = self._try_wait(0)
  File "/usr/lib/python3.8/subprocess.py", line 1764, in _try_wait
    (pid, sts) = os.waitpid(self.pid, wait_flags)
KeyboardInterrupt

Thanks @remy415, we appreciate it!  🙏😄
I will ty this and figure out what is going on with the tests!   The tests aside, are you actually able to run a model through ollama in the container?

The bottom screenshot green GPU area was nearly 100% usage throughout the response. It answered my question very quickly, I expected it to take longer as I'm used to running Mistral 7b but it worked fantastically.
I did need to ensure I set OLLAMA_HOST=<node ip> on the "client" side to make sure it knew where to connect.
tegra@ok3d-1:~/ok3d/ollama-container/dev/jetson-containers$ docker run -d --gpus=all -v ollama:/root/.ollama -p 11434:11434 --name ollama-rc4 <IP_ADDRESS>:5001/ollama-r35.4.1-ollama:latest
71964ec5430e741ac7778fab3fdf6d2035d3d12a8054f87d8c37283d782249da
tegra@ok3d-1:~/ok3d/ollama-container/dev/jetson-containers$ docker logs ollama-rc4
time=2024-04-04T20:51:03.561Z level=INFO source=images.go:793 msg="total blobs: 5"
time=2024-04-04T20:51:03.562Z level=INFO source=images.go:800 msg="total unused blobs removed: 0"
[GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.

[GIN-debug] [WARNING] Running in "debug" mode.
CUDA (Computational Understanding for Dynamic Assessment) is an open-source software that provides comprehensive and automated tools for analyzing complex real-world
problems in various domains, such as engineering, finance, and healthcare. It allows users to model, simulate, and analyze complex systems in a fast, efficient, and
error-free manner, with minimal human intervention. CUDA is designed to help solve critical problems in fields such as energy, materials science, and biomedical
research, among others.

>>> /bye

Note that with the -v ollama:/root/.ollama flag, it will create a local docker volume and mount it in the container at /root/.ollama. ollama will automatically download model files and store them there. If you wish to have a directory or location outside of the container to store those, should change it to -v <path to local folder>:/root/.ollama

14 seconds to execute the docker run, type in "What is CUDA?", get a response, and type in "/bye". Tinyllama is fast on the Orin Nano, though I think it's a bit confused as to the meaning of CUDA. Can't complain though, the model is <1Gb.
tegra@ok3d-1:~/ok3d/ollama-container/dev/jetson-containers$ date
Thu 04 Apr 2024 09:34:25 PM UTC
tegra@ok3d-1:~/ok3d/ollama-container/dev/jetson-containers$ docker run -itu0 --rm -e OLLAMA_HOST=<IP_ADDRESS> <IP_ADDRESS>:5001/ollama-r35.4.1-ollama:latest '/bin/ollama run tinyllama'
>>> What is CUDA?
CUDA, or Comprehensive Undergraduate Data Analytics, is an undergraduate analytics program offered by the University of Pennsylvania (Penn). The program emphasizes the
use of statistical computing and data analysis techniques to solve complex business problems. It provides a foundation in mathematics and statistics, as well as
practical applications in various industries such as finance, marketing, and healthcare. The program is designed for students who want to pursue careers in analytics
and is offered on campus and online.

>>> /bye
tegra@ok3d-1:~/ok3d/ollama-container/dev/jetson-containers$ date
Thu 04 Apr 2024 09:34:39 PM UTC
tegra@ok3d-1:~/ok3d/ollama-container/dev/jetson-containers$tegra@ok3d-1:~/ok3d/ollama-container/dev/jetson-containers$ date
Thu 04 Apr 2024 09:34:25 PM UTC
tegra@ok3d-1:~/ok3d/ollama-container/dev/jetson-containers$ docker run -itu0 --rm -e OLLAMA_HOST=<IP_ADDRESS> <IP_ADDRESS>:5001/ollama-r35.4.1-ollama:latest '/bin/ollama run tinyllama'
>>> What is CUDA?
CUDA, or Comprehensive Undergraduate Data Analytics, is an undergraduate analytics program offered by the University of Pennsylvania (Penn). The program emphasizes the
use of statistical computing and data analysis techniques to solve complex business problems. It provides a foundation in mathematics and statistics, as well as
practical applications in various industries such as finance, marketing, and healthcare. The program is designed for students who want to pursue careers in analytics
and is offered on campus and online.

>>> /bye
tegra@ok3d-1:~/ok3d/ollama-container/dev/jetson-containers$ date
Thu 04 Apr 2024 09:34:39 PM UTC

Ok great, seems like it is working good and using GPU, awesome work!
When I merge/test this, I will add jetson-containers/data/models/ollama and symlink it to /root/.ollama inside the container, so the models will automatically be cached there (that jetson-containers/data location is automatically mounted into the container under /data if you use run.sh)

@dusty-nv great, thank you!
I forgot to mention that I couldn’t find a lot of documentation on the implementation of the various benchmarks I found in the packages folder. The benchmark I have set up will run the server on the current terminal then will attempt to curl the api. It may be better to assume the backend is running and just pass in the server ip for the curl.

@remy415 ok!, made some minor tweaks to ollama container in https://github.com/dusty-nv/jetson-containers/commit/413d5aff9d3120b29fdef697575ed762979e6a89 , got it working, pushed images for JP5/JP6 to DockerHub, and merged it into master - thank you for everything and all the upstream work to enable this on Jetson!
Given your contributions, please feel free to make a new topic on the Jetson Projects forum announcing this, I know the community has been asking for it.  Otherwise I will post it next week.
Some notes:

the test.sh script was hanging because of the bash ENTRYPOINT not exiting.  Removed that, kept the startup ollama serve CMD though, all works as expected
there isn't a set framework for the benchmarks, they are all API specific, they just tend to follow a similar pattern
I think we should take a deeper look at what CUDA options ollama is building llama.cpp with, which differ from mine:

https://github.com/ollama/ollama/blob/c5d5c4a96ca53b703d48edd10a58235dd9e1d13a/llm/generate/gen_linux.sh#L166
LLAMA_CUDA_F16 is disabled for the original Nano, but should be able to just detect if 53 is in CMAKE_CUDA_ARCHITECTURES (and if not, enable FP16 for Xavier/Orin which are the primary platforms for edge LLM nowadays)
Correct me if I'm wrong, but I believe LLAMA_CUDA_FORCE_MMQ=on is for batching, which Jetson users aren't using really and instead could benefit from CUDA_USE_TENSOR_CORES instead

by default, /root/.ollama is now symlinked to jetson-containers/data/models/ollama but this can be overridden with -v /my/ollama/dir:/root/.ollama when you start the container
The images uploaded are dustynv/ollama:r35.4.1 and dustynv/ollama:r36.2.0 and can be automatically pulled/started with autotag like so: cd jetson-containers
 git pull
 ./run.sh $(./autotag ollama)

 # open another terminal (or start the above with -d)
 ./run.sh $(./autotag ollama) ollama run tinyllama


Skip username format validation when getSkipUsernamePatternValidationThreadLocal() returns true

Skip username format validation if UserCoreUtil.getSkipUsernamePatternValidationThreadLocal() returns true. That we will only set to true, if the username format validation has happened in another listener with higher priority.
Related PR:

https://github.com/wso2/carbon-identity-framework/pull/4428

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4096689340

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4096689340
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4096981189

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4096981189
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4097001483

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4097001483
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4100322075

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4100322075
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4101092212

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4101092212
Status: success


'wide ' is prepended to metric names

Describe the bug
I create a query with regex resulting in multiple metrics: metric names / aliases are "hostname: item name".
When I create an abritary second one, the names of the first query change to "wide hostname: item name".
It does not matter, if regex is in 'Host' or 'Item'. SetAlias function does not help: new name is applied, but 'wide' keeps to be displayed in front.
Also order of the queries do not matter.
Expected behavior
On adding a second query, names of first one keep the same.
Screenshots

Software versions

Grafana
Zabbix
Grafana-Zabbix Plugin

8.2.3
5.4.7
4.2.4

This happens after I upgraded from Grafana 7.5.4 / Grafana-Zabbix 4.1.5.
Can anyone reproduce that, has an idea what can cause this behavior or know a workaround?

Also having this issue. "wide" is prepended to almost all of my legend items after upgrading. I have toggled both "Use Zabbix value mapping" and "Disable data alignment" options witch fixes this issue briefly but then it goes back to showing "wide". Some inconsistent behavior there. Not sure which option is fixing it. Sometimes fixes it instantly and sometimes doesn't. Very Odd.
Grafana - 8.2.5
Zabbix - 5.0.4
Grafana-Zabbix Plugin - 4.2.4

I confirm the problem. Very strange thing.

It's not so strange after some investigation. It's surely connected with data alignment, when it's disabled I don't have the issue.
I think the root of the issue is somewhere here: https://github.com/alexanderzobnin/grafana-zabbix/blob/f6e25409f163530b1affc61e47807a0b1e105715/src/datasource-zabbix/responseHandler.ts#L343
And as a result, I'm getting answer in the Inspector that looks like this:
wide-cut.json.gz

I disabled data alignment just now and it did not fix the issue for me. But the first time I was playing around with those settings, it did get fixed briefly. Can't seem to put my finger on it.

I have the same issue.

Grafana
Zabbix
Grafana-Zabbix Plugin

8.3.1
5.0.18
4.2.4

It happens for each query that return multiple metrics series.

I got this too.

Also still experiencing this issue.


List props returns invalid empty list

When not initialized the list properties return an empty list rather than None. This is confusing as in the case below, that is not even a valid thing:
import properties
class Array(properties.HasProperties):
    shape = properties.List(
        'shape of the 2d array',
        prop=properties.Integer('', min=1),
        min_length=2,
        max_length=2,
    )
a = Array()
print(a.shape)
#> []

What is worse is that if the property is also not required, it will fail validation.

I disagree that the first comment is a bug, it's just the way things are designed (for now...). A container property's _class_default value is an empty container, regardless of anything else. Looking through the documentation, though, looks like that's never stated... You can always set default=properties.undefined; then a.shape is None. In this case, though, a.validate() will still fail until shape is set correctly. Whether or not this is the correct behavior is a different story...
...which brings up your second comment. I agree that is a very bad bug-like consequence that I hadn't thought of (if there is no min_length requirement and the list property is unset, None vs [] shouldn't be a big difference). Anyway, I think this is probably enough reason to change the default behavior.
That has possible implications for existing code that may assume the list is instantiated by default. Needs some investigation before acting.
~Another possibly safer but definitely more complicated solution is making the default undefined if required=False but [] otherwise... Something to consider, but I really don't like this. Yeah. Really don't like it.~
Anyway, as a temporary fix, just set default=properties.undefined. Then things should behave as you expect.

I guess really it's just a question of taste. Do we require users who do not want an initialized list to set default=properties.undefined? or do we require users who do want an initialized list to set default=list?

Another related bug-like thing here with defaults that are not undefined. Given something like this:
    values = properties.Union(
        'Lists of similar type values',
        props=[
            properties.List('', properties.Integer(''), min_length=2),
            properties.List('', properties.Float(''), min_length=2),
            properties.List('', properties.DateTime(''), min_length=2),
        ],
        default=properties.undefined,
    )

I'd expect the undefined default to override the list [] default. But it does not, the default instead is set to the list default.
This leads a bit into another question - do we want union properties to grab sub-props's defaults? Makes more sense if you look at something like this:
    value = properties.Union(
        'Float, Int, or DateTime',
        props=[
            properties.Integer('', default=5),
            properties.Float(''),
            properties.DateTime(''),
        ],
    )

The the default for the union property will be 5 as well. But maybe that isn't what we want either...?
Anyway, definitely need to rethink the empty list default.

Empty list defaults have been removed with #219 - the backwards incompatibility means the next release is 0.4.0, but this is a necessary change to fix the above behaviour and add some consistency to property defaults


Add binary in release

Hello, I discovered Gogs and I wonder if it is possible to deploy a release in an archive containing only a binary and libraries? When I want to propose a repo on my release, Gogs only shows a link to download the source. I think this is normal, but there is no option to upload my compiled program?
thank you

Maybe a way to upload files that are associated with a repository and that can be linked to in the readme or the description is a simple and straight forward solution, isn't it?

Good feature, it's import to store the distribution release version that includes the everything such as deps package, runtime env that git ignored.

Sorry I'm starting getting confused about this thread.... is is a feature request for adding attachments for repository release feature, or something else?

yes, just attachments that could be anything else, such as released binary files, or whole repo excluded .git folder. Sometimes we want to store the files and folders that git ignored, so that we can recover it for these attachments when bad things happened.

@melote thanks your explanation!

I'd love to see the ability to attach files to releases! :+1:

Bump. First thanks for the awesome app you built.
I think that being able to attach a binaries to a release (+ maybe a hook that we could trigger from a CI service (travis, gitlab ci, jenkins, etc) to auto-attach the binary when a new release is available).
I :+1: this feature request. :)

:+1:

For anyone else, I know it's not a great, but a quick workaround I've been using is creating a new branch in your repo called 'bin' or something similar and creating the release for your repo from that

Merge this thread to https://github.com/gogits/gogs/issues/1614


Update README.md

mostly whitespace changes....putting sentences on one line
However:

did you mis-state N and N-1?
some capitalization
typos
rewording the sentence about sort order

What do you have against paragraphs? :)

I'll butt in here: git is line oriented, so if you have a whole paragraph on one line, a single typo will cause git to track the whole paragraph as being changed.  If you have each sentence in their own line, then a single typo will not affect the whole paragraph, but only that sentence.  This is easier for looking back on history and seeing documentation changes, and a reasonable compromise.  Perhaps I just don't read raw markdown and so don't need it to "look good" in markdown format (i.e. paragraphs on the same line), and rely on the rendering?

But GitHub renders separate lines with a newline between them. Or at least that's how it appears when I look at the rendered readme here https://github.com/yfarjoun/stitch/tree/patch-1.

my bad....removed the spaces after the end of lines....I hope it's better now...

@yfarjoun I think you're right - should be N and N + 1

I don't have merge permission here...go ahead!


Fix bug with MorphologicalRuleOrder.Linear for LT-21988

There was a bug in AnalysisStratumRule.Apply when the MorphologicalRuleOrder was Linear.  It did not include the case where there were morphological rules but no templates.  This did not match what SynthesisStratumRule.Apply was doing.  I fixed the bug and extended a unit test to cover this case.

This change is

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

Project coverage is 70.16%. Comparing base (3b98936) to head (1e77851).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #279      +/-   ##
==========================================
+ Coverage   70.14%   70.16%   +0.02%
==========================================
  Files         385      385
  Lines       31962    31957       -5
  Branches     4489     4488       -1
==========================================
+ Hits        22420    22424       +4
+ Misses       8499     8493       -6
+ Partials     1043     1040       -3

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


chore(sdk): Add github issue links to TODOs

Codecov Report
Patch and project coverage have no change.

Comparison is base (365ccaa) 89.66% compared to head (4d11094) 89.66%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #474   +/-   ##
=======================================
  Coverage   89.66%   89.66%
=======================================
  Files          88       88
  Lines        3270     3270
=======================================
  Hits         2932     2932
  Misses        221      221
  Partials      117      117

Impacted Files
Coverage Δ

pkg/openid4ci/models.go
100.00% <ø> (ø)

pkg/openid4ci/openid4ci.go
89.01% <ø> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[6.0] Implement --checksum option on swift sdk install

Cherry-pick of https://github.com/swiftlang/swift-package-manager/pull/7722.
Explanation: This option was specified in the corresponding proposal for Swift SDKs:

For Swift SDKs installed from remote URLs an additional --checksum option is required, through which users of a Swift SDK can specify a checksum provided by a publisher of the SDK. The latter can produce a checksum by running swift package compute-checksum command (introduced in SE-0272) with the Swift SDK bundle archive as an argument.

Scope: the change is isolated to swift sdk install and swift package compute-checksum subcommands.
Risk: low due to isolation to only two rarely used subcommands with corresponding automated test cases provided.
Testing: updated existing test cases.
Issue: rdar://130590711
Reviewer: @bnbarham

@swift-ci test

@swift-ci test


In Dutch specifying both alias and area doesn't work

In Dutch, turning on lights only works if you specify the alias or the area. It does not work if you specify both

Thanks for the report, I'll look into it


Correct way to install posh-sshell

System Details

posh-sshell version/path: ??
PowerShell version: 6.0.2
Operating system name and version: Windows 10 1809
OpenSSH / Putty version: <IP_ADDRESS>

Issue Description
I am trying to set up ssh-agent to work with Windows' OpenSSH client but apparently, posh-git doesn't work perfectly with windows' OpenSSH and it keeps asking my for my passphrase everytime. I then came across this project, and it seems like I'll need to install posh-sshell to make posh-git work with OpenSSH-Win32?
When I install this extension, I get this error:
> PowerShellGet\Install-Module posh-git -Scope CurrentUser -AllowPrerelease -Force
> PowerShellGet\Install-Module posh-sshell -Scope CurrentUser -AllowPrerelease -Force
PackageManagement\Install-Package : The following commands are already available on this system:'Add-SshKey,Get-SshAgent,Get-
SshPath,Start-SshAgent,Stop-SshAgent'. This module 'posh-sshell' may override the existing commands.

What is the recommended way to install both modules?

Hi, if you want both modules installed you'll need to grab the code of posh-git from master, rather than installing a release. These functions were removed from posh-git into posh-sshell after the lastest release of posh-git was made (1.0-beta2), so you will end up with these conflicts if you use the latest release of posh-git.
@dahlbyk is there a chance of getting a 1.0-beta3 of posh-git sometime soon so both modules can be installed from the gallery?


Title bar style custom: vscode icon overlaps file menu after restart

VSCode Version: 1.25.0
OS Version: Microsoft Windows [Version 10.0.16299.431]

Steps to Reproduce:

Press F11 to enter fullscreen mode
Set "window.titleBarStyle": "custom"
Restart vscode
Press F11 to exist fullscreen mode

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

duplicate of #52952


Idea: Put troubleshooting guide in wiki

To hopefully reduce the number of people asking how they messed up in getting code coming from the DefaultModBase, I would like to propose starting a wiki with a page about troubleshooting common problems. It can include advice on
*opening up the jar with 7-Zip to make sure the json and other resources are the most current
*making sure the source code has no compilation problems before it's jarred
*running the code through a debugger if the above don't work

Also, the wiki would be the place to put explanations about multiword keywords.

You may see multiword keyword names separated by what looks like spaces in some mods. Those are actually non-breaking spaces designed to help with centering of text. The non-breaking spaces are replaced with regular spaces when you view them on the web and, by default, when you paste them into an IntelliJ editor.


你好，docker部署卡在Module"jsdom"这一步

docker部署卡在了这里，
Starting nginx: nginx.

yarn run v1.22.19

$ NODE_ENV=production ts-node src/start.ts

[09:40:26.615] INFO (46): Logger initialized: info

[09:40:33.047] INFO (config/46): Config file path: /app/server/config.json

[09:40:33.596] INFO (db/46): Database connected

[09:40:33.785] INFO (db/46): Database synced

[09:40:33.799] INFO (redis/46): Redis connected

[09:40:33.862] WARN (ai/46): No anthropic tokens provided

[09:40:33.863] INFO (ai/46): anthropic clients initialized

[09:40:33.863] WARN (ai/46): No openai tokens provided

[09:40:33.863] INFO (ai/46): openai clients initialized

[09:40:33.866] WARN (ai/46): No stability tokens provided

[09:40:33.867] INFO (ai/46): stability clients initialized

(sequelize) Warning: Model "User" is declaring public class fields for attribute(s): "nickname", "account", "password", "avatar", "role", "integral", "invite_code", "invite_by", "level", "level_expire_time", "vip_expire_time", "svip_expire_time", "status", "ip", "create_time", "update_time".

These class fields are shadowing Sequelize's attribute getters & setters.

See https://sequelize.org/main/manual/model-basics.html#caveat-with-public-class-fields

[09:40:33.895] INFO (app/46): Server running on port 5174

[09:40:33.896] INFO (db/46): Administrator initialized: admin_brbn  sQXnB6921

[09:40:35.210] INFO (plugins/46): stdout:

added 1 package, and audited 2 packages in 882ms

found 0 vulnerabilities

[09:40:35.210] INFO (plugins/46): Module "dayjs" has been installed at /app/server/plugins.

[09:40:46.406] INFO (plugins/46): stdout:

added 43 packages, and audited 45 packages in 11s

6 packages are looking for funding

  run `npm fund` for details

found 0 vulnerabilities

[09:40:46.407] INFO (plugins/46): Module "pinyin" has been installed at /app/server/plugins.

[09:40:49.381] INFO (plugins/46): stdout:

added 1 package, and audited 46 packages in 3s

6 packages are looking for funding

  run `npm fund` for details

found 0 vulnerabilities

[09:40:49.381] INFO (plugins/46): Module "lodash" has been installed at /app/server/plugins.

[09:40:54.686] INFO (plugins/46): stdout:

added 88 packages, and audited 134 packages in 5s

12 packages are looking for funding

  run `npm fund` for details

found 0 vulnerabilities

[09:40:54.686] INFO (plugins/46): Module "puppeteer-core" has been installed at /app/server/plugins.

[09:40:58.818] INFO (plugins/46): stdout:

added 45 packages, and audited 179 packages in 4s

14 packages are looking for funding

  run `npm fund` for details

found 0 vulnerabilities

[09:40:58.818] INFO (plugins/46): Module "jsdom" has been installed at /app/server/plugins.

[09:40:58.818] INFO (app/46): Plugins initialized

这是已经好了吧

这是已经好了吧

啊，我试过进不去啊，不论是http://ip:6789，还是nginx反代

5174端口显示{"code":404,"data":{},"message":"The current access API address does not exist"}

这是已经好了吧

对不起，我蠢了，容器的80端口才是网页...我一直在看6789端口。。。


Notice: Aegis.Server NuGet Package Unavailable - Pending ID Reservation

I recently published the Aegis licensing library to NuGet. I am now attempting to publish an extension package for server-side functionality called "Aegis.Server". However, I encountered an error during the NuGet upload:
"The package ID is reserved. You can upload your package with a different package ID. Reach out to<EMAIL_ADDRESS>if you have questions."
This is despite the fact that no package with the ID "Aegis.Server" currently exists on NuGet. I believe this is a logical and appropriate name for the extension, clearly indicating its relationship to the core "Aegis" library.
Latest Commit Update:
In the latest commit, I separated the core Aegis.Server library from the sample ASP.NET Core project. Unfortunately, the NuGet package upload for Aegis.Server still encounters the package ID reservation issue. I have contacted NuGet support and am currently proceeding with the package ID reservation process.
Workaround:
The sample Aegis.Server.AspNetCore project, which demonstrates server-side integration, works fine. However, Aegis.Server is not yet available on NuGet.
If you require the server-side functionality, you can temporarily use the Aegis.Server library directly from this repository until the NuGet package issue is resolved.
Status:

Package ID reservation request submitted to NuGet support.
Awaiting approval for the "Aegis.Server" package ID.

Issue Addressed
"Aegis" prefix has been reserved for us, thanks to Nuget support team.
Package Aegis.Server uploaded successfully to Nuget

Issue Addressed
"Aegis" prefix has been reserved for us, thanks to Nuget support team.
Package Aegis.Server uploaded successfully to Nuget


Make battery percentage consistent with official app

Should resolve https://github.com/home-assistant/core/issues/100521

Anyone able to approve and merge this? It has been open for 2 months. It's a very simple change.
Thanks

Hi @onegambler, thank you for the reminder. I'll try to take a look at this and provide a response next week.

I would consider making the battery voltages user configurable.
In my case the web app was telling me I had 40% battery life and airthings-ble was indicating 10% battery life.  My airthings wave+ stopped working the next day because of low battery voltage. The airthings-ble was more accurate.
Some of the issue may be voltage differences vs battery percentage remaining between alkaline and lithium batteries.  Making the voltages configurable would allow the user to make a decision that meets their needs.

The biggest issue that I see is consistency, having different readings between the app and this library is not great.

Hi @arnerek, we have another PR #27 on the way (currently in testing). The PR is bringing a robust solution for all devices and should resolve the issue. I suggest waiting with the rebase or closing the PR. Anyway, thank you for your contribution and patience.

The battery sensor was fixed in this PR: https://github.com/Airthings/airthings-ble/pull/27
Closing this ticket.


[Feature request] Show full path/ Name during transfer

Hello,
during transfer the file Name are cut off... is it possible to add an mode to show the complete file Name?
Problem, when you are use long file names you can´t read witch file are in process...
Regards
Massaguana
If you've just got a question or aren't sure if you've found a bug then please use the rclone forum instead of filing an issue.

What is your rclone version (eg output from rclone -V)
v1.35
Which OS you are using and how many bits (eg Windows 7, 64 bit)
MacOS, CentOS7 64Bit
Which cloud storage system are you using? (eg Google Drive)
GSuite Business
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone -v sync "path" "path"
A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)

Do you mean in the stats output? The one which tells you which files are transferring?  Or in the log lines that print what has been copied?

Is this a duplicate of #1206 ?

I mean the status window.. What i Can see during transfer in Terminal...

Do you mean the same as #1206 ?

it looks an little bit different but i think it is the same... but not sure because i can see the filename end... something like MovieName.mkv

Can you attach a screenshot of the output you would like to change?

OK, that is what is being proposed in #1206 so I'll close this one in favour of that one.
Can you subscribe to that issue?
Thanks


Spotify: error while loading shared libraries: libxcb.so.1

Issue description
$ spotify
/run/current-system/sw/bin/spotify: error while loading shared libraries: libxcb.so.1: cannot open shared object file: No such file or directory

Technical details
Unstable (09c91f5fea73746c2ea85b37834e7ec450923d18) and master (35dfdc9277511351cb757317e9cac0dc47473596).

https://github.com/NixOS/nixpkgs/pull/24342 (3c090f0e5a61b9b16a95059c6bfaa6a59abe2ccd) broke spotify
cc @WilliButz @joachifm

Turned out to be easy to fix https://github.com/NixOS/nixpkgs/commit/ffd29517dd05e92dbc8a71d3dde835862b48f121


Blitzform not work whit async QSelect or any select components

QSelect not work inside BlitzForm schema, options is pased in schema, but change in options after filtering never show in select list

I believe you have to make options a dynamic prop for i to be reactive. Can you try it.

I believe you have to make options a dynamic prop for it to be reactive. Can you try it.
@mesqueeb i haven't try that before, but not work too

if options is a ref the listed options is ever empty.
If is an array it shows initial items but no items added later.

I check with vue dev tools and whit a DOM ref:

both ref and array updates internally, but nothing changes in QSelect.
i try explicitly call  refresh() on DOM ref after pushed new items, but also not work.

Try making it a dynamic prop, there's documentation on this in the blitzar docs.

Try making it a dynamic prop, there's documentation on this in the blitzar docs.

already try it... no work, nothing changes

Can you share a code snippet ? I can try and have a look.

Can you share a code snippet ? I can try and have a look.

I put a standalone QSelect aside blitzar's QSelect, inside Standalone QSelect options is array of "Reactive" types but inside Blitzar QSelect options is array of "Object"

Hey! It is probably because blitzform creates a copy of the schema passed to for performance reasons.
I had a look at your code, and can you try this?
https://gist.github.com/vici0uz/4bc07b6f2b787c0d7f3e50e0526df6b7#file-qselectblitzform-vue-L46
dynamicPros ['options'],
options: () => select_options_ref.value // change ref value but not options shown in component

When marking a prop as a dynamic prop, you have to pass it as a function. Please try this snippet and let me know!

dynamicProps ['options'],
options: () => select_options_ref.value // change ref value but not options shown in component

That's work, thanks.


Check validity of target property descriptions

See https://www.lf-lang.org/docs/reference/target-declaration

[ ] Rust (@chanijjani, @oowekyala)
[ ] TypeScript (@lhstrh, @hokeun)
[ ] Cpp (@cmnrd)
[ ] C (@lsk567 )
[ ] Python (@vinzbarbuto)

Rust validation (Please give me any better method or suggestion!)

Example and method used
: Run the binary of CounterProgram.lf after applying the target property and compiling with lfc-dev (version)
Target properties not tested since those are not supported
: auth, build, compiler, docker, files, ~logging~, ~no-compile~, no-runtime-validation, protobufs
Target properties tested

buildtype: Debug (binary size:40671312bytes) = default, Release (binary size:4450760bytes), RelWithDebInfo (binary size:27350408bytes), and MinSizeRel (binary size:4179936bytes)
cargo-dependencies
cargo-features
(TBA)

Validity check for Python target properties
Methodology: A toy example was executed for each target property to verify successful program compilation and execution. The programs were compiled using lfc (version 0.8.0)
Unsupported Properties
Properties: auth, build, cargo-dependencies, cargo-features, compiler, external-runtime-path, export-dependency-graph, no-runtime-validation, runtime-version, rust-include, scheduler, single-file-project
Supported Properties
Overview

Target Property
Support (Web)
Support (Actual)
Comments

build
:x:
:orange_circle:
Review

build-type
:x:
:white_check_mark:
Update

docker
:white_check_mark:
:white_check_mark:
It works

fast
:white_check_mark:
:white_check_mark:
It works

files
:white_check_mark:
:orange_circle:
Review

logging
:white_check_mark:
:white_check_mark:
It works

no-compile
:white_check_mark:
:white_check_mark:
It works

protobufs
:white_check_mark:
:white_check_mark:
Suggestion

single-threaded
:white_check_mark:
:white_check_mark:
It works

timeout
:white_check_mark:
:white_check_mark:
It works

workers
:white_check_mark:
:white_check_mark:
It works

Comments
build

Support:

Web: :x:
Actual: :orange_circle:

Review
The build property for the Python target is not supported according to the website documentation. However, when I set this property, it does compile the program without indicating that the property is unsupported. The issue arises when it struggles to resolve the path to the executable file. For instance, let's say I have a compile.sh script in the src/ directory. If I set:
target Python {
    build: "./compile.sh"
}

After compiling the program, I get the following error:
lfc: error: The command ./compile.sh could not be found in the current working directory or in your PATH.

Even when using the absolute path, I encounter the same error.
build-type

Support:

Web: :x:
Actual: :white_check_mark:

Review
Althought the build-type property for the Python target is not supported according to the website documentation, I was able to compile and run an LF program with the Python target using this property. It accepts four different arguments: Debug, Release, RelWithDebInfo, and MinSizeRel. The default is Release.
files

Support:

Web: :white_check_mark:
Actual: :orange_circle:

Review
The target property functions smoothly for regular LF programs. However, for federated LF programs, it requires absolute paths for included files; otherwise, compilation will fail. If using absolute paths is the intended approach, it should be clearly stated in the documentation.
Additionally, the website mistakenly displays both Python and C target examples. This seems to be an oversight.
protobufs

Support:

Web: :white_check_mark:
Actual: :white_check_mark:

Review
The target property works smoothly. However, I suggest improving the documentation on how to correctly install and set up protobuf on a local machine.


Adding fix for llama CI failure caused by ttnn.experimental.tensor.typecast

What's changed
Changing calls to ttnn.experimental.tensor.typecast to ttnn.experimental.typecast to resolve failure on CI.
Checklist

[ ] Post commit CI passes
[ ] Model regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

[ ]


Implement Coindesk BPI API?

http://www.coindesk.com/api/

Big "issue days destroyed" on this one ;-)

yeah! digging deep.


Fix serialization of Place/Transition identifier attribute

I won't merge this pull-request, because I'm currently working on the code. To be honest, I don't understand the intention of the PR, too. I will soon publish a (pre-)release of this library, you may then open an issue if you encounter any problems.


ulauncher, wrong executable path at shipped systemd user service.

Describe the bug
nix/store/xxxxxx-ulauncher-5.15.0/share/systemd/user/ulauncher.service has ExecStart=env GDK_BACKEND=x11 /usr/bin/ulauncher --hide-window instead of nix/store executable path.
Steps To Reproduce
Steps to reproduce the behavior:

Install ulauncher
systemctl --user enable --now ulauncher.service

Expected behavior
Launch ulauncher on the background
Additional context
Installed using home-manager.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.95, NixOS, 23.05 (Stoat), 23.05.20230225.b1f87ca`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.2`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Please submit a pr replacing the path with substituteInPlace


[Fixes #198] x and y are required to be the same length

This PR is related to #198.
I hope I got it right 😄

Looks good. Thanks for adding the tests as well -- that is certainly always appreciated.

Please feel free to submit PRs for anything else you see.


example: Use torch in mnist example

Signed-off-by: Jinjing.Zhou<EMAIL_ADDRESS>Fix #881

Please fix the lint with make envd-fmt


add tests to test query parameters and redirection

Add two new tests to:

test query parameters, including values with % encoding
test redirection

Codecov Report

Merging #165 into master will increase coverage by 1.76%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #165      +/-   ##
==========================================
+ Coverage   66.84%   68.61%   +1.76%
==========================================
  Files          20       20
  Lines        1300     1300
==========================================
+ Hits          869      892      +23
+ Misses        431      408      -23

Flag
Coverage Δ

#KituraNet
68.61% <ø> (+1.76%)
:arrow_up:

Impacted Files
Coverage Δ

Sources/KituraNet/HTTP/HTTPServerRequest.swift
73.29% <0%> (+0.62%)
:arrow_up:

Sources/KituraNet/ClientRequest.swift
74.5% <0%> (+6.23%)
:arrow_up:

Continue to review full report at Codecov.

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

Yes, the redirection test does test ClientRequest.
Regarding the query params test, though we are running the Kitura test suite on every pull request, we decided that every time a regression escapes Kitura-NIO/Kitura-net and is found by the Kitura tests, we'd add/port the corresponding test to Kitura-net/NIO. #154 was one such regression.


Remove unneccessary AppsandFeaturesEntries * manifests/r/RandomEngy/VidCoder/9.20/RandomEngy.VidCoder.installer.yaml

Microsoft Reviewers: Open in CodeFlow

URL:
Invalid URI: The hostname could not be parsed.
(Automated message - build 899)


Increase HSTS to one year

This increases the HTTP Strict Transport Security to 1 year which is the recommended minimum. This is also the required minimum to be added to the preload list.
This has a few implications:

Once a browser sees this setting, it will not ever attempt to connect to our site over plain HTTP for 1 year! Any browser will transparently try https://pythonsd.org whenever you type http://pythonsd.org into the browser.
Because we are applying this to subdomains (SECURE_HSTS_INCLUDE_SUBDOMAINS), this means we can't host anything at http://*.pythonsd.org or http://*.sandiegopython.org. Everything would have to be HTTPS.

Codecov Report

Merging #40 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #40   +/-   ##
=======================================
  Coverage   98.92%   98.92%
=======================================
  Files           8        8
  Lines          93       93
  Branches        6        6
=======================================
  Hits           92       92
  Misses          1        1

Continue to review full report at Codecov.

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


Guest contribution gets associated with a registered account

Describe the bug
A Guest contribution gets associated with a registered account if the emails match, without acknowledgement of the registered user.
To Reproduce
Steps to reproduce the behavior:

As an unregistered user (not logged in), go to make a donation (e.g. https://opencollective.com/compost/donate)
Click on Incognito to make a guest donation without registering
Enter the email address of a registered user

Proceed to make the donation
Observe that the donation of the anonymous user is now associated with the profile of a registered user

Expected behavior
The anonymous user should receive a message that says "this account belongs to a registered user" and prompt for login.
Desktop (please complete the following information):

OS: MacOS
Browser Firefox

Additional context
This happened to me. A email came in saying I made a $100 donation, and I obviously didn't make that. It's a Collective under my own host, so I was able to check the record in Stripe, and it's not a credit card I recognize, but everything went through and it was a legitimate donation (from someone, but who?!)
This was confusing because I thought someone gained access to my OC account. The donor probably saw the Guest contribution page and thought "ahh this is like Paypal, let me enter the recipient email address", which is my address, when OC really wanted their email address... so the payment went and got associated to my account.
I verified this behaviour by making a donation as Guest to another Collective, and yes it did get associated with my account again.

Allowing contributions with existing emails was creating a minor security issue

leading to:

I immediately assumed my account was accessed by a third party, reset all my OC sessions and called my credit card company to check whether my card was used for the donation (because my card is stored on file for recurrings).

sounds like a bit of a misjudgement to me, and one I would worry about more as we start to support bigger projects. I think either of the propsed solutions is acceptable:

The anonymous user should receive a message that says "this account belongs to a registered user" and prompt for login.

In the "thank you" email, there's a small message for people to contact support if there's something wrong

I think it's worth some digging to find out what impact this has currently and whether we should look to improve the login method to lower barriers there if it's an issue for some...

I don't think the account being accessed by a third party is a misjudgement though. If my Twitter RTs something that I didn't do myself, I'd immediately conclude it as access by a third party. Especially so since I have used the OC account on a device that does not belong to me.
I think the general user does not have the full bg context of OC staff, that the action originating from an unauthenticated event would never have come to mind. My second hypothesis was that there was a bug in the platform itself and the Tx would soon be rejected. So at that time I also emailed @alanna to inquiry if it was a platform iseue.

if a guest contributor goes on to register with the same email, will their previous contributions as a guest become associated with their new profile? There are lots of semi-related issues about this and I'm struggling to work out what the current state is?
In short: I have a guest contributor who I'd like to register, and I'd like their existing guest contributions to be associated with their new user profile

if a guest contributor goes on to register with the same email, will their previous contributions as a guest become associated with their new profile? There are lots of semi-related issues about this and I'm struggling to work out what the current state is?

You can contribute as a guest using the same email multiple times. However, as soon as users verify their accounts (aka. they confirm their emails by signing up), the system will ask them to sign in when they try to contribute. This is not yet enforced on all hosts, but for the long term we're looking into closing this issue.

In short: I have a guest contributor who I'd like to register, and I'd like their existing guest contributions to be associated with their new user profile

While we recognize that this is a simpler UX, it creates some security challenges (mostly the ones exposed in this issue) that we want to protect against.
To smoothen the experience, we need to make sign-in from the contribution flow as simple as possible. The main challenge is the embedded contribution flow, which has limited options.
The alternative would be to not associate a contribution to an account until users sign in to confirm it, but that could create even more friction and complexity.

OK thanks @Betree it sounds like it's already all working as I'd like it to and I just need to get my guest contributor to register...


LightGLue is slower than LoFTR

Hi,
I am doing keypoint matching with 1280x720 images, with a GTX 1080 Ti ( 11.2 GiB of memory ) and found that LightGlue is slower than LoFTR, while it's supposed to be ~x4 faster according to the paper.
LoFTR takes ~0.45s to match, while LightGLue took 0.05s (superpoint)+0.63s (lightglue). There was ~900-1000 keypoints.
What could be the reason ? Even if the hardware is old it should not change the fact that LoFTR should be slower ?
EDIT: I am using Pytorch 2.x

Hi, that should definitely not be the case. I suspect there is some overhead involved. Do you use compilation with LightGlue? If so, the compilation is done just-in-time, so when you call LightGlue the first time in your script it will take some time to compile, with the benefit of it being faster in the long run (assuming you run it over many pairs).

There is no way LightGlue is so slow, it usually takes like 0.02sec per 1024 points, unless you run on CPU (even though) or do the compilation.

I am running on the GPU. I used the base demo notebook and changed no code (except for for the input images).
I ran the model several times and the matching time has the same order of magnitude (~0.5 or 0.6s).
Maybe my GPU is too old ?

What is your GPU then? And how exactly do you measure time? Could you please put full code snippet here?

Hi, as I said earlier I have a  GTX 1080 Ti with 12 GB of VRAM.
I use the following code :
`from lightglue import LightGlue, SuperPoint, DISK, SIFT, ALIKED
from lightglue.utils import load_image, rbd
import time
import torch
device = 'cuda' if torch.cuda.is_available() else 'cpu'
SuperPoint+LightGlue
extractor = SuperPoint(max_num_keypoints=2048).eval().to(device)  # load the extractor
matcher = LightGlue(features='superpoint').eval().to(device) # load the matcher
# or DISK+LightGlue, ALIKED+LightGlue or SIFT+LightGlue
extractor = DISK(max_num_keypoints=2048).eval().cuda()  # load the extractor
matcher = LightGlue(features='disk').eval().cuda()  # load the matcher
load each image as a torch.Tensor on GPU with shape (3,H,W), normalized in [0,1]
image0 = load_image('./assets/sacre_coeur1.jpg').to(device)
image1 = load_image('./assets/sacre_coeur2.jpg').to(device)
WARMING GPU - 10 matching
for i in range(10) :
# extract local features
feats0 = extractor.extract(image0)  # auto-resize the image, disable with resize=None
feats1 = extractor.extract(image1)
# match the features
matches01 = matcher({'image0': feats0, 'image1': feats1})

feats0, feats1, matches01 = [rbd(x) for x in [feats0, feats1, matches01]]  # remove batch dimension
matches = matches01['matches']  # indices with shape (K,2)
points0 = feats0['keypoints'][matches[..., 0]]  # coordinates in image #0, shape (K,2)
points1 = feats1['keypoints'][matches[..., 1]]  # coordinates in image #1, shape (K,2)

Timing inference
start = torch.cuda.Event(enable_timing=True)
end = torch.cuda.Event(enable_timing=True)
start.record()
feats0 = extractor.extract(image0)  # auto-resize the image, disable with resize=None
feats1 = extractor.extract(image1)
matches01 = matcher({'image0': feats0, 'image1': feats1})
end.record()
Waits for everything to finish running
torch.cuda.synchronize()
print(start.elapsed_time(end), 'ms')`
I know I should run it several time to average-out the inference time but it always end up with ~450ms +- 50ms with the following images.

It seems you don't turn the gradients off.
How about following:
torch.cuda.synchronize()
with torch.inference_mode():
    feats0 = extractor.extract(image0)  # auto-resize the image, disable with resize=None
    feats1 = extractor.extract(image1)
    matches01 = matcher({'image0': feats0, 'image1': feats1})
torch.cuda.synchronize()

It is still roughly the same order of magnitude...

It seems you don't turn the gradients off. How about following:
torch.cuda.synchronize()
with torch.inference_mode():
    feats0 = extractor.extract(image0)  # auto-resize the image, disable with resize=None
    feats1 = extractor.extract(image1)
    matches01 = matcher({'image0': feats0, 'image1': feats1})
torch.cuda.synchronize()

I added your advice :
start.record()
torch.cuda.synchronize()
with torch.inference_mode():
feats0 = extractor.extract(image0)  # auto-resize the image, disable with resize=None
feats1 = extractor.extract(image1)
matches01 = matcher({'image0': feats0, 'image1': feats1})
Waits for everything to finish running
torch.cuda.synchronize()
end.record()
But I still have the same order of magnitude of inference.
Note that I have also tried on a T4 GPU from Google COlab with the same snippet, and it only took ~110ms this time, but still far from the expected latency...

Tried your code on 1080Ti without FlashAttention, it only takes 96.ms
/home/***/code/LightGlue/lightglue/lightglue.py:141: UserWarning: FlashAttention is not available. For optimal speed, consider installing torch >= 2.0 or flash-attn.
self.inner_attn = Attention(flash)
96.60598754882812 ms
Besides, I think you should exclude the timing of feature extraction when measuring LightGlue, since SuperPoint may be slower than expected.
After excluding feature extraction time, LG takes only 46.83689498901367 ms on 1080Ti.

feats0 = extractor.extract(image0)  # auto-resize the image, disable with resize=None
feats1 = extractor.extract(image1)
torch.cuda.synchronize()
start.record()
with torch.inference_mode():
       matches01 = matcher({'image0': feats0, 'image1': feats1})

# Waits for everything to finish running
torch.cuda.synchronize()

end.record()

Using pytorch 2.0 slightly speed up inference on 1080Ti.

Header
Header

With Extraction
Without Extraction

96.6
46.8

81.8
41.9

Well then I do not know where the overhead is coming from...

@tcourat are you sure that your machine doesn't do any background process at the time of bechmarking?

Hy, do you have any updates on this? I'm facing the same issue on RTX 3070 also


Fix regex in lininfile in Ubuntu rule <IP_ADDRESS>

There is a missing equals sign, causing incorrect replacement if GRUB_CMDLINE_LINUX_DEFAULT is also present in /etc/default/grub.
Overall Review of Changes:
Corrects the lineinfile regex for Ubuntu rule <IP_ADDRESS> by adding a missing equals sign after GRUB_CMDLINE_LINUX.
Issue Fixes:
N/A
Enhancements:
N/A
How has this been tested?:
Tested on Ubuntu Jammy. Reverted the previous incorrect replacement, then used the fixed playbook to reapply the rule.

hi @MoteHue
Thanks for finding this and taking the time in raising the PR. Unfortunately this is not being seen as GPG signed, happy to accept if you can add the gpg signature please.
Many thanks
uk-bolly

Hi @uk-bolly
I've added the GPG signature now :)

Hi @uk-bolly I've added the GPG signature now :)

Rapid work
thank you all approved.
uk-bolly


Multitouch: objects receive wrong touchend event

BUG:
If two sprites are handling touchstart and touchend events, sometimes one sprite receives BOTH touchend events, and the other sprite does not receive any touchend events.
Here is a gif demonstrating the effect: https://gfycat.com/PleasingIncompleteAardwolf
As you can see in the console, a sprite will receive a touchstart event, then remember the touch 'identifier' that is embedded in the event. All sprites receive ALL unrelated touchmove events, therefore the sprite must filter out events which pertain to itself by checking the identifier in each event (not printed to console). However, sometimes one sprite receives all the touchend events, including those that contain identifiers associated with the other sprites. These other sprites don't get their touchend events.
SOLUTION:
The workaround stated here involving adding checks to the processTouchStart and processTouchEnd:
http://www.html5gamedevs.com/topic/19273-can-container-get-touchup-event-when-touchdown-of-other-container-press/
Alternatively, perhaps all sprites should receive all touchend events, just like they receive all touchmove events, and allow each sprite to remember its own touchstart identifier, and then listen for a touchend which has the same identifier.

This should be fixed with the better use of touch identifiers in #3546.


Gamblr

Gamblr initial

I guess this PR is accidental, we will not change Dash to "Gamblr" anytime soon :)
Good luck coin #916 - instead of cloning you should seriously consider contributing to already existing coins ;)


ContextualHelp with scrollbar is not keyboard accessibile

Provide a general summary of the issue here
I have a ContextHelp which can be long and at times displays a vertical scrollbar.
It is not possible to get to the content at the bottom using just a keyboard.
🤔 Expected Behavior?
Should be able to scroll the help content with the keyboard
😯 Current Behavior
Can not scroll the help content with the keyboard.
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce
Reduce the height of your browser window.
Run https://reactspectrum.blob.core.windows.net/reactspectrum/169b0467b0c1a2638bee97d25cd432c45f27cfc8/storybook/index.html?path=/story/contextualhelp--default&providerSwitcher-express=false
and keyboard to the button. Press the button.

Version
3.31.0
What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge
If other, please specify.
No response
What operating system are you using?
macOs
🧢 Your Company/Team
Adobe/Admin Console
🕷 Tracking Issue
No response

Reproduced locally, problem is that we don't have a focusable element with the dialog's scrollable region. Ideally the scrollable region itself would be focusable but this is currently using Dialog which has the tabIndex applied to the div wrapping the scrollable region...

Chromium will be releasing Keyboard focusable scroll containers, similar to the way Firefox makes scroll containers receive focus very soon: https://chromestatus.com/feature/5231964663578624.


Article and Highlight template note variable breaks template with complex text

Importing an article with a note or highlight note, containing bullet points and/or : characters causes the template to fail at the invalid character.
For example, if you're importing an article with the following note it will fail after the :. Not sure if it's the colon character or the bullet point that breaks the import.
Some text

And other thoughts:
 - Thought 1
 - Thought 2

Some more text.

Expected Result
The importer should be able to get all text written in Omnivore's note fields even if all of the formatting characters cannot be successfully brought through to logseq.

As a temporary workaround, in your template, you can put your notes in a codeblock (```) to make sure all of the content makes it through into logseq.
Ex:
## {{{title}}}
{{#note}}
```
{{{note}}}
```
{{/note}}


Iris 1.6.0 compat

According to your testing, does the issue occur with ONLY Immersive Portals mod and Fabric API?
No
Describe the issue
.

Probably fixed in 2.6.3


Use previously saved Drawing  for editing

I saved the image in base64 string in my database now I want to use it again for editing to add new content in the same drawing. Is there a way to do it?

if you want to add new content to previously saved image maybe you can use it as bg image then start add new content
but if you want to edit previously saved image then you must save all strokes and shapes instead of base64 image and for now it can't

Alright so what if we draw the image again in canvas by getting the canvas from the canvas id and then just draw the image that we have so far?

so you trying to save the canvas element then on the new page you use the canvas  you saved before and start drawing on it?

I tried to do it but the problem I am facing is that the image do get redrawn and rendered but once you start to edit the old one altogether gets lost.

what if I add a new method to get all the strokes and shapes, then you can render a new canvas with the initial image?
but first i need to make sure no issue on this idea

Sorry for that I was kind of busy these days. So I just wanted to know will this way somehow be able to edit the previous image if the new canvas is rendered.

yes you can, but you must change your saved data from base64 image to all strokes path
please kindly check this example. try draw something and press "Save All Strokes" button then refresh codesandbox workspace to see your previously saved image as an initial image.

Yes something like this, you used localStorage so if I save the image in my database as using this method instead of local storage and getting it in the initial image I guess it would work for me too right?

Yep, added on 1.0.7
closing this now, thanks


Cow: Watch wandersky.in

Cow requests the watch of the watch_keyword wandersky\.in. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

wandersky\.in has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by double-beep in Charcoal HQ


Add 'Android SDK Platform 23' to check list

Add 'Android SDK Platform 23' to the check list when install the proper Android SDK.
Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:

Unless you are a React Native release maintainer and cherry-picking an existing commit into a current release, ensure your pull request is targeting the master React Native branch.

Explain the motivation for making this change. What existing problem does the pull request solve?
Prefer small pull requests. These are much easier to review and more likely to get merged. Make sure the PR does only one thing, otherwise please split it.
Test plan (required)
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
Make sure tests pass on both Travis and Circle CI.
Code formatting
Look around. Match the style of the rest of the codebase. See also the simple style guide.
For more info, see the "Pull Requests" section of our "Contributing" guidelines.

Hmm, I must have missed this item during my last install. Do you have a screencap of this screen that shows this item?

Have you signed the CLA yet?

I think not yet. Where do I sign the CLA?

Thank you!


Android - Payment -Missing the dropdown for payment option, so Pay with Venmo isn't visible

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

Action Performed:

Sign-up to Expensify.cash with a US phone number and validate that account (Account A)
Create another account with a different US phone number (Account B) that has the Venmo app installed on their mobile device.
As account A, Complete the request money flow and send a payment request to account B
Log-in as account B and click the pay button
Verify that Pay with Venmo is visible as an option in the dropdown

Expected Result:
Pay with Venmo` is visible as an option in the dropdown
Actual Result:
Missing the dropdown for payment option, so Pay with Venmo isn't visible
Workaround:
No workaround found to pay with venmo app.
Platform:
Where is this issue occurring?
Web
iOS
Android ✔
Desktop App
Mobile Web
Version Number: 1.0.72-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Issue is not reproducible with the same account in iOS.

Expensify/Expensify Issue URL:
View all open jobs on Upwork

Triggered auto assignment to @luacmartins (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@isagoico Were you logged in to Venmo when you reproduced this issue?

Waiting on answer from @isagoico while trying to change default IOU currency to USD on test accounts so addVenmoPaymentOptionIfAvailable() runs.

Mmmm I think the option should show if the user has the app installed which was the case on the issue. She tried the same (with the same account) in iOS and the option to pay via Venmo appeared.  I'll confirm with the tester if the she was logged in or not.

Managed to reproduce the issue. Currently investigating the diffrence in iOS and Android responses.

@isagoico Can we retest this and check it off if resolved?

Seems like the PR is still not in staging. We're still able to reproduce the issue in build 1.0.73-0

@roryabraham how can we get this PR to staging? https://github.com/Expensify/Expensify.cash/pull/3713

CP staging label is needed.

Added CP Staging label to PR.

@luacmartins and I got this settled 1:1, but yes in general the CP Staging label should be applied before the PR is merged, and then it will be immediately CP'd upon merge. However, if we forget to do that, then Expensify employees can just ping me in the #deployers slack channel to ask for an E.cash PR to be CP'd after-the-fact. Right now only @AndrewGable and myself have permission to manually CP, but we will probably open that up to other Expensify employees soon.

Issue is fixed in build 1.0.73-2 🎉