Update automation-windows-hrw-install.md

The login prompt that comes up for accessing the subscript won't work on Window Server browser unless JavaScript is enabled (which is not by default for security).
Performing this on Window Server 2016 server I am giving this response:

I don't know if it would be best state that you basically need to ensure IE Enhanced Security Configuration is turned off for administrators?

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

@wsmelton Reaching back out to see if you can update your PR.  There is a merge conflict now that would need to be resolved.  Let me know otherwise I will request this pr to be closed.

We can just close it.


Android 64-bit support

Soon Android will force all play store apps to support 64-bit architecture.
Does this plugin fulfill that restriction?
https://developer.android.com/distribute/best-practices/develop/64-bit

Yes, the plugin doesn't use any .so file for different architectures, so it supports all.


SceneTree.CreateTimer() does not free the timer after its time elapses

Godot version
4.0.beta10.mono.official [d0398f62f]
System information
Windows 11 Home 64-bit (Build 22621.963), Intel Core i5 11400F, NVIDIA GeForce RTX 3070
Issue description
While the document says "The timer will be automatically freed after its time elapses.", the Debugger says the opposite.
The timer created by SceneTree.CreateTimer() is not freed automatically after its time elapses. The Object count and Memory usage in the Debugger tab keep increasing.
Steps to reproduce

Create new project.
Create C# script CreateTimerTester.cs with the following contents:

using Godot;
public partial class CreateTimerTester : Node2D
{
    public override void _Ready()
    {
        base._Ready();
        TestCreateTimer();
    }

    private async void TestCreateTimer()
    {
        var tree = GetTree();
        do
        {
            await ToSignal(tree.CreateTimer(0.1, true, false, true), "timeout");
        }
        while (true);
    }
}

Create new scene. Create a Node2D. Attach the script to the node.
Play the scene. Observe the Object count and Memory usage in the Debugger tab.

(Optional) 5. If you call TestCreateTimer(); multiple times with a for-loop, it can be more effective. Here is a screenshot of calling it 5000 times and then stopping the loops by a cancellation token after 10 seconds:

The full code for step 5 is in the reproduction project.
Minimal reproduction project
TestCreateTimer.zip

To make sure the issue is not caused by Object.ToSignal(), I have also changed the script as follow and tested again:
using Godot;
public partial class CreateTimerTester : Node2D
{
    public override void _Ready()
    {
        base._Ready();
        TestCreateTimer();
    }

    private void TestCreateTimer() =>
        GetTree().CreateTimer(0.1, true, false, true).Timeout += OnTimeOut;

    private void OnTimeOut() => TestCreateTimer();
}

Result is the same.


cmd/preguide: appear to hang if the docker image cannot be downloaded

Perhaps some back error handling now that we've moved to concurrent guide processing?
Seen randomly locally immediately after upgrading to a later preguide version in PWG.

This was fixed in https://github.com/play-with-go/preguide/commit/cc79a71d80d51a5f1093474e879df03ac437f942


Sweep: create a chat function like completion in upsonic_on_prem/utils/ai/ai.py  (✓ Sandbox Passed)

Description
This pull request adds a new chat function to the AI class in upsonic_on_prem/utils/ai/ai.py.
Summary

Added a new chat function to the AI class in upsonic_on_prem/utils/ai/ai.py
The chat function uses the GPT-3.5-turbo model to generate chat responses
If an exception occurs during chat generation, a failure message is logged

Fixes #87.

🎉 Latest improvements to Sweep:

New dashboard launched for real-time tracking of Sweep issues, covering all stages from search to coding.
Integration of OpenAI's latest Assistant API for more efficient and reliable code planning and editing, improving speed by 3x.
Use the GitHub issues extension for creating Sweep issues directly from your editor.

💡 To get Sweep to edit this pull request, you can:

Comment below, and Sweep can edit the entire PR
Comment on a file, Sweep will only modify the commented file
Edit the original issue to get Sweep to recreate the PR from scratch

Rollback Files For Sweep

[ ] Rollback changes to  upsonic_on_prem/utils/ai/ai.py

This is an automated message generated by Sweep AI.

Apply Sweep Rules to your PR?

[ ] Apply:  All new business logic should have corresponding unit tests.
[ ] Apply:  Refactor large functions to be more modular.
[ ] Apply:  Add docstrings to all functions and file headers.

This is an automated message generated by Sweep AI.


[WIP] feat: Added display_mode Property to Language Segment

Prerequisites

[x] I have read and understand the CONTRIBUTING guide
[x] The commit message follows the conventional commits guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Description
It would be nice if language segments (for example python) could always be displayed
This PR adds an 'display_mode' property to the language segment which determines when the segment is displayed.
Following values are allowed for the display_mode property:

always: The segment is always displayed
when_in_context: The segment is only displayed if the current folder contains files with certain extensions
never: The segment is never displayed

Default value is: when_in_context
Example:
{
    "type": "python",
    "style": "plain",
    "foreground": "magenta",
    "properties": {
        "display_mode": "when_in_context",
	"display_version": true
    }
},

@moritz-meier perfect, can you rebase so there's only 1 commit? An interactive rebase with fixups should do the job. There's no need for a historical context to contain PR comment rework 🙏🏻

Added this to #255 to avoid having to ask to once again rebase, thanks for all the work @moritz-meier 🙏🏻


Using pivots and getTrProps()

Problem Description
I pivot (more than 1 pivot columns) the table as well as dynamically style the selected row using getTrProps. However this causes the groups to collapse each time the row is clicked/styled. Is there a way to prevent this from happening or is there a better way of doing this? I want to indicate which row was selected.
Code Snippet(s)
getTrProps={(state, rowInfo, column) => {
                            return {
                            onClick: e => {this.showDetailView(rowInfo)},
                            style: {
                                color: (rowInfo != undefined && rowInfo.row != null && rowInfo.row != undefined
                                    && this.props.currentLineItemDetail !== null && rowInfo.row.cashLineItemId === this.props.currentLineItemDetail.cashLineItemId)
                                ? "#E65100"  : null

                            }
                            }
                        }}

Steps to Reproduce

Specify pivotBy entries on the grid.
Use getTrProps to style the row that was currently clicked on (something similar to code shown above)
This causes the groups to collapse.

System Information

Chrome

Is your showDetailView() causing the data reference to change?
If so you might play around with the collapseOnDataChange: false table setting.

I do remove the styling on the previously highlighted row. I have specified both collapseOnDataChange={false} and freezeWhenExpanded={true}

That's strange then. If you could recreate it on codepen that would be helpful.

http://codepen.io/neojones/pen/XRagjg?editors=1111

If I understand what you're trying to accomplish, then collapseOnDataChange={false} works just fine. Also the removeSelected is unnecessary to remove the styling since the getTrProps is recomputed every time the current row changes.
http://codepen.io/aaronschwartz/pen/dWzzgG?editors=0010

Yes it did work in codepen...the code is however oversimplified. Need to debug my app to see what is happening.

Also you don't even need collapseOnDataChange={false} as long as you use the same references to data, columns, pivotBy, sorting, showFilters, filtering.
http://codepen.io/aaronschwartz/pen/bWrrJL?editors=0010

Yes none of that is changing however I do have conditional logic on the pivotBy field

In that case you will need the collapseOnDataChange={false} but other than that I'm not sure what is wrong without seeing more of your code. Are you changing filtering or sorting table props?

no sorting and filter props don't change

Ok. Maybe if you paste your entire react-table options I can take a look. You might just have to start simplifying it as much as possible to find the culprit.

Oh ok..so if I add defaultSorting={[{id: 'firstName'}, {id: 'lastName'}]} it collapses.
When I remove that...it does not collapse
http://codepen.io/neojones/pen/XRagjg

Ah yes. Since the defaultSorting is technically changing since the array reference is changing, it thinks that the sorting has changed.
You can either make the defaultSorting constant:
http://codepen.io/aaronschwartz/pen/ZKJaLL?editors=0010
Or you can set collapseOnSortingChange={false}
http://codepen.io/aaronschwartz/pen/QvMOpj?editors=0010

I see. Let me give that a try.

That seems to work. Thanks for your help.


update commit messages to be more descriptive

initial transcription using tstbtc tool is non-descript and is going to be a frequently seen commit in bitcoin transcripts. Add the title of the file being transcribed as well as top level dir to help better describe the commit

does something like this work? added PCs don’t stand a chance… in sob1 by masterchief164 where added PCs don’t stand a chance… is the file name, sob1/2021 was the loc provided and masterchief164 was the username

https://github.com/masterchief164/bitcointranscripts/pull/23 is the sample PR

The title should sufffice. You can gather the rest of the context from the PR.


the system environment variable of Linux system does not work

I use the "spring-cloud-starter-config : 2.1.2.RELEASE"
in the git project ".yml" file, I set "spring: datasource: url:
jdbc:mysql://www.exampleA.com"

in the k8s.yaml file I put a new system environment variable "SPRING_DATASOURCE_URL" and "SPRING_PROFILES_ACTIVE" But "SPRING_DATASOURCE_URL"  does not work.

this is bootstrap.yml of my client application

I'm sorry, I'm unsure what this has to do with spring cloud config. Also, screenshots are difficult to read

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


html/template: JS context breaks after a quoted

What version of Go are you using (go version)?

$ go version
go version go1.15.6 darwin/amd64

Does this issue reproduce with the latest release?

The existence of a tag </script> inside a Javascript string breaks the context and can cause code injection.
In the following example, the first variable is properly quoted, but the variables after "</script>", are not treated as Javascript string, and the go representation is displayed
https://play.golang.org/p/_XqZ3NtXYVE
What did you expect to see?
<script>var b = {"foo": "foo", "script": "</script>", "bar": "bar"}</script>

What did you see instead?
<script>var b = {"foo": "foo", "script": "</script>", "bar": bar}</script>

This is the expected behavior. To get your expected result, you should use something like "<" + "/script>" or "<\/script>" instead of "</script>".

This is the expected behavior. To get your expected result, you should use something like "<" + "/script>" or "<\/script>" instead of "</script>".

Browsers behave the same way.

Browsers behave the same way.

I've checked, and yes, browsers behave the same way. I suppose we can close this issue.

I've checked, and yes, browsers behave the same way. I suppose we can close this issue.


Add options to parse a lc3 bitstream without the custom header in dlc3

It would be nice to be able to parse a raw lc3 bitstream with dlc3 by providing the frame_us, srate_hz, hrmode, nchannels, nsamples and the block bytes directly on the command line.

I think this will add two much complexity to the tools usage.
You can try the decoder.py and encoder.py using the python wrapper, to easily customize the I/O. This will be merged soon.
I will add documentation on the binary header, it's not a custom header, it's defined in the testing docs.
(LC3 - TS <IP_ADDRESS>)[https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=502301].


Update document, add a colab example for reading data, upgrade numpy dependency

What changes do you make in this PR?

Please describe why you create this PR

Checklist

[x] I have merged the latest main branch into current branch.
[x] I have run bash scripts/format.sh before merging.
Please use "squash and merge" mode.

@QuanyiLi Please double check and merge.


Add Component to

In order to have a even more interactive website, would it be convenient to let users add component to <Redirect>? This would allow them to have a mid-component on redirections, like a loading bar or notification that the user is being redirected.
Sample Code:
<Route path="/" component={App}>
      <Route path="user/:userID" component={User}>
        <Route path="tasks/:taskID" component={Task} />
        <Redirect from="todos/:taskID" to="tasks/:taskID" component={Load} />
      </Route>
    </Route>

We don't actually render at all on redirects – the redirect happens entirely in the router.

Hypothetically: Could we leave  component as optional and render the redirect if component is supplied to it?

No, we don't render anything for redirects – the transition manager listen callback (normally) won't fire at all until the redirect is fully resolved.
We should have something better in place for async handling in routes, but it's not really redirect-specific. A redirect is just a route that redirects you in onEnter.


ProgressBar has no tempplate or render function

I was trying to make my own component which included Progress as a child component.
When I tried to render, the Progress component was commented and my console displayed the following message:
[Vue warn]: Component is missing template or render function.
  at <BProgress value=20 min=0 max=100  ... >
  at <SkillBar value=20 >
  at <App>

After digging around a bit I think it's not the Progress component but the ProgressBar component. It doesn't have a template defined.
This was m y(redacted) code:
<template>

      <BProgress :value="value" :min="0" :max="100" height="2rem" variant='succes'/>

</template>

Strange, I don't see this message.
I've looked at the docs pages were b-progress is used as well as added it to app.vue and neither produce the message.
Where do you see this message? In browser console? or in your IDE
The BProgessBar has a render function but it's returned from the setup function instead of a separate render function.
Anyway, I added a dummy template for BProgressBar in PR #227., can you test this please?

My apologies. It was litteraly the difference between:
import BProgress from 'bootstrap-vue-3'; // Wrong, doesn't render

and
import { BProgress } from 'bootstrap-vue-3'; // Good, does render


⚠ DDoS-Relay US-E-ash-2 has degraded performance

In a06399a, DDoS-Relay US-E-ash-2 (http://<IP_ADDRESS>:42069/;csv) experienced degraded performance:

HTTP code: 200
Response time: 47 ms

Resolved: DDoS-Relay US-E-ash-2 performance has improved in bba24bc after 13 minutes.


Add option to filter by job posting industry

we can use what linkedin already has for this filter but it would be really cool to filter a little bit more. For those that want to work in a particular area. (eg. on linkedin it shows “computer software”, it could add a filter if the user wants to work in a particular area related, like retail, e-commerce, start up, fashion, grocery etc)

Yeah %2C is a url encoded comma.
Great!
I didn't know it was possible to filter this on the url.
Feel free to open a PR with this 👍


Fix managers' array function

This pr fixes managers' array function.
Fixed bug: Some structures need more args than just client and data, and most managers' array function didn't pass those args.

Looks good, is this tested?

Not all things are tested, but everything should work because I fixed everything by same method.


Setup project using react-native link

Is this a bug report?
NO, Is there any way to install this package and then link to android and IOS project using react-native link command?. Because I am getting lots of error while using the installation instruction and also I have installed other package through react-native link therefore that's needs be updated

dupe of #2289, #1954


Impact of shadowing underestimated

Where to find the issue
In https://github.com/corona-warn-app/cwa-documentation/blob/master/cwa-risk-assessment.md
Describe the issue

Even minor impediments, such as a person between the two smartphones or a signal-impeding smartphone case, can cause the distance to appear to be twice as large as it actually is.

This underestimates the impact of shadowing.
Suggested change

Even minor impediments, such as a person between the two smartphones or a signal-impeding smartphone case, can cause the distance to appear to be ten times as large as it actually is.

Indeed, a body sitting between phones represents around a factor of 10 in the error on the distance calculation. See here for various sources, for instance this one, which has the merit of being very visual:
https://www.youtube.com/watch?v=SAi24ctpyZQ

Internal Tracking ID: EXPOSUREAPP-1918

Funny to see my video popping up ;) I also have my doubts about distance measurement with Bluetooth, it has been discussed at length in this MIT webinar. It suggests that these errors could statistically cancel out if we had frequent independent measurement (100 times during 10 minutes, so very 6 seconds), but right now it seems to be every 5 minutes.
Statements like this from the risk assessment:

All exposures for a diagnosis key that lasted less than 10 minutes in total (regardless of how close the smartphones came during that time) or during which the smartphones were more than 8 meters (73 dB attenuation) apart on average (regardless of how long the exposure lasted) are discarded as harmless.

Seems way to optimistic - we cannot put equal sign between 73 dB and 8 meters, it can be 1 meter as well, depending on where the person keeps the phone. Maybe it would average out over time, but if scanning is every 5 minutes for 2 seconds then there is no way that it will average out. If it was up to me I'd just notify everyone about exposure regardless of duration / signal strength until we have better tech available (UWB)

Hi pdehaye,
Thank you for raising this issue. The team will get back to you soon.
Best regards
MC
Your Corona Warn-App Open Source Team

Related: https://github.com/corona-warn-app/cwa-app-android/issues/523

@pdehaye

Even minor impediments, such as a person between the two smartphones ...

... signal-impeding smartphone case ...

Similar to have the smartphone in the back pocket?
I think, some impediments might be also impediments to the particles we are worried about.
And some may exist because the persons are not aware of the technical limitations or the proper usage.

@keugens Unless you have your mouth on your back, I don't get your point  ;-)

Sorry, maybe I missed your point: this factor shouldn't be 2 but 10.
I can agree with that, but not much more.

... minor impediments, such as a person ...

Not agreed. This seems to be a larger impediment, no free space between the phones, does not match factor 10.
And, assuming the persons wearing their phones on the front-side of their bodies, it seems this impediment is also an impediment for the infectious particles. This additional signal attenuation is pointing at least in the right direction. Therefore it is not clear for me why you call this an error. The final goal is not distance measurement, but detecting situations with more or less infectious particles around.
Re. phone cases: for me, this is a matter of proper usage (like wearing the phone in the back pocket) and not about an error.
Re. error: for a normal free space situation I would roughly estimate an error of factor 2 for all (95%) phones using the app. To talk about the errors you mentioned, without talking about systematic errors, is misleading and does not inspire confidence in my honest opinion.

... distance calculation

It's a measurement, I would say. Which does not exclude parameters, formula and - unfortunately - massive systematic errors.

... ten times as large as it actually is.

... as it is measured by the phone under normal free space condition, I would say.
And due to systematic errors, it could be 20 times as large as it actually is.

@keugens My point was that this two should be replaced by ten. A person in the beam (either passing by or always in between because of how the phone is carried) is a difference of close to 20db, i.e. a factor of 10. Leaving it as is conveys the wrong impression about the possible error.

https://github.com/corona-warn-app/cwa-documentation/pull/435 was closed without being merged. I'm unsure how to proceed with this issue. I don't like the idea of leaving issues open fore 2 years without any movement on it, so either this should be fixed or the wont fix label should be applied and this issue closed.


up eslint packages + type check and format in pre-commit

Description:
Updated pre-commit hook so that it does:

Type check: By doing this we make sure that type error don't get into our code.

eslint / typescript-eslint doesn't do typescheck ref and that why this happened

lint check: we were already doing this.
format: This is helpful for json files, by default eslint does not format json files, but prettier is able to do it nicely. This way we make sure people don't commit unformatted json files especially extensions.json file

Also updated the eslint related packages because on the main branch in eslint.config.json I was getting this:

And also a small error at line where we were using eslintPluginPrettierRecommended (not able to reproduce now though)

Not sure what I'm doing wrong but pre-commit doesn't work for me at all, I can add whatever I want to any files, like asdfasdf, even in main branch. Do you know what can cause it? Files are not ignored, for example any ts file inside src folder

Also, I'm getting an error when linting
yarn lint

/Users/liana/Documents/prog/buidl-guidl/create-eth/src/utils/system-validation.ts
  7:12  error  'error' is defined but never used  @typescript-eslint/no-unused-vars

✖ 1 problem (1 error, 0 warnings)

Not sure what I'm doing wrong but lefthook and hence pre-commit doesn't work for me at all, I can add whatever I want to any files, like asdfasdf, even in main branch. Do you know what can cause it? Files are not ignored, for example any .ts file inside src folder

Umm not sure what's the problem is, but can re-clone the repo and then  yarn install and then switching this branch and see if it works?
Also maybe try running :
yarn lefthook run pre-commit

To see if lefhook is working?

Lol today it works. I didn't change anything, just restarted mac yesterday but not sure it could be cause of the fix :suspect:
Now everything works as expected! Lgtm, thank you!


fix: use dispatcher interface, not the static class

Fixes a small non-test friendly bit of code that slipped through, which depends on a static class, instead of an interface.
Fixes #71

Merged, thanks!


fix: Add Cmd Default/Input support to cleanup

Bring post action step into consistency with main for changes introduced in #154.
Without this change, sshAgentCmd is undefined when passed to execFileSync() during cleanup and post is never successful.
Post job cleanup consistently showing:
Stopping SSH agent
The "file" argument must be of type string. Received undefined
Error stopping the SSH agent, proceeding anyway

Makes sense!
Could you please update dist/cleanup.js as well by running npm run build?

Thanks for the gentle reminder @mpdude.
Updated via docker using:
$ docker run \
  --interactive \
  --rm \
  --tty \
  --volume ${PWD}:/var/task \
  --workdir /var/task \
  node:16-buster \
  sh -c 'yarn install && npm run build'

Please advise if the update looks incorrect or if you'd like me to use a different version of node or run a modified command.

@mpdude Is there anything else blocking this?

I'd love to see this PR released. I've got self-hosted runners with tons of ssh-agent processes hanging around.
This fixes it nicely.

Gentle bump on this PR being merged. This would really help with the cleanup of the ssh-agent processes running in the context of non-containerised environments!

@mpdude, I've rebased my branch from upstream and re-run/updated the dist/ folder.
$ docker run \
    --interactive \
    --rm \
    --tty \
    --volume ${PWD}:/var/task \
    --workdir /var/task \
    node:20-buster \
    sh -c 'npm install -g<EMAIL_ADDRESS>&& yarn install && NODE_OPTIONS=--openssl-legacy-provider npm run build'

Like others above, I'd love to get this into a release.

Also would love to see this one in for our self hosted runners.

Hi guys, I would love to see this one merged also :pray: :pray:

pls merge this @mpdude

Have this warning in Post Loads private SSH key as well on Github hosted runners. If this PR fixes it, would love to see it merged
Stopping SSH agent
The "file" argument must be of type string. Received undefined
Error stopping the SSH agent, proceeding anyway

y u no merge dis? 😄

🙏 please merge this PR

@mpdude It'd be nice to see this merged. Anything the community can do to help?

does anyone have a stable fork with this fix?

@mpdude Hi, I hope you're doing well and I really hope this doesn't bother you, but are there any plans to merge this solution?

Hi everyone! What's missing for this PR to be merged? Is there anything to help?
Because of this bug, a lot of ssh-agent processes are piling up on my stand-alone GHA runner. I'd be happy to help if there is anything I can do.


Automatically shuffle deck on search & Pokémon of Towering Perfection

Trainers still need done.
@axpendix Tried to add auto deck shuffling any time the deck is searched and seems to work. Would appreciate you take a look to make sure it doesn't seem like it will break anything.

I am okay with deck shuffle change


Guidance on Playback Position persistance

Problem
I'm currently trying to migrate my audiobook player Voice to media3 session, but I'm having a difficult time doing so. The main problem is that media3 seems to be designed primarily for music playback, with the assumption that the user can freely browse and play individual tracks. However, in the audiobook (or podcast) use case, the user wants to play a book as a whole, rather than individual tracks. Additionally, the user wants the ability to resume playback from where they left off.
Example
When interacting with android auto, which uses the legacy media APIs and calls onPlayFromMediaId, media3 internally calls onAddMediaItems with a searchQuery and prepares and plays the first track of the audiobook. This doesn't meet the needs of the audiobook use case, as the user does not want to start playback at the beginning of the book every time.
Solution
I would love to get some guidance on how media3 is supposed to work with use cases that involve persisting the playback position. It would be helpful to have more information on how media3 is intended to be used in scenarios like audiobook playback, where the user wants to play a book as a whole and maintain their position within the book.

We are aware that the use case of Android Auto is not yet possible. We are working on an enhancement of onAddMediaItems that allows to expand a single item/search to a list of item and also specify the start index and position in that index (see also #156).
Besides this, an app needs to persist the playlist (list of media IDs), the current media item and the position in that media item itself.  This probably happens when the service (or the activity housing the player) is destroyed or oat another moment that makes sense for the app. Then when playback is resumed, the app needs to add the items of the playlist to the player, prepare and start playback.
With the Media3 API this would be something like:
player.setMediaItems(listOfMediaItems, startIndex, startPositionMs);
player.prepare();
player.play();

It is possible. I do use media3 with Android Auto in https://play.google.com/store/apps/details?id=com.vanniktech.rssreader

Thanks Niklas! Yeah, I wasn't clear. What I meant with the use case of Android Auto is that it is not possible to expand from a single item sent by a legacy API call like playFromMediaId() to a list of items and then start playback at a different windowIndex then 0.

Oh yes. I work around that by reshuffling the list so that my dedicated item is at 0 even if it should be at another index ..

We are aware that the use case of Android Auto is not yet possible. We are working on an enhancement of onAddMediaItems that allows to expand a single item/search to a list of item and also specify the start index and position in that index (see also https://github.com/androidx/media/issues/156).

Is there any timeline for this? I'd like to be an early adopter of media3 but with the current limitations I would need to drop the Android Auto support.
Or is there alternatively a way to overwrite the legacy callbacks and handle it myself?

Besides this, an app needs to persist the playlist (list of media IDs), ...

Yes, that's clear. The question was more targeting Android Auto and how other Apps interact with the media session that I provide.
Let's assume one day Android Auto no longer uses the legacy apis. How would it handle the playback? How would I ensure that it does not prepare the media items with a position of zero but rather picks up my locally persisted playback position?

Oh another fun thing that I remember is this one. Had to also work around the fact that extras are null. Ended up working around that by putting a JSON string as my mediaId which contains some data and then I'm able to interact with it ...

[..] Android Auto no longer uses the legacy apis. How would it handle the playback? How would I ensure that it does not prepare the media items with a position of zero but rather picks up my locally persisted playback position?

I don't know how Auto will use the new API. That's up to them. They could do a similar thing like they do today and let the app set the start position.
The user browses the media library you provide and then selects an item. AA could call
player.setMediaItem(mediaItem);
player.prepare();
player.play();

This would then call your callback with the media item selected and leaves it to the app to for instance expand the item to a list of items and to select the start index and position. The new MediaSession.Callback method mentioned above will allow this to provide the feature requested with #156.

Is there any timeline for this?

I think this will be included in the next release. Can't tell when that actually will be but probably Jan/Feb.
I'm closing this issue as a duplicate of #156. Please re-open if you think there's something to add.


Powertoys Icon Disappearing from Tray

Microsoft PowerToys version
0.59.1
Running as admin

[X] Yes

Area(s) with issue?
System tray interaction
Steps to reproduce
Load PowerToys, wait a while...
As you can see PowerToys is working, just not showing the icon in the system tray

PowerToysReport_2022-06-21-20-22-48.zip
I'm not too sure the bug report zip will help much since I needed to end task on PowerToys.Runner in taskmanager and then reload the program since the tray icon was missing so I couldn't upload a report while its bugged.
The icon only shows whenever I end task and reload PowerToys, then after a while it just disappears for whatever reason.
✔ Expected Behavior
Tray icon to not disappear
❌ Actual Behavior
Tray icon disappears
Other Software
N/A

Hi, so according to your description, the icon disappears after a while.
Can't really find anything in the logs.
Your Desktop seems quite customized. Are you using some software to make your task bar look like that? I wonder if there's some incompatibility here. /needinfo

Hi, so according to your description, the icon disappears after a while. Can't really find anything in the logs. Your Desktop seems quite customized. Are you using some software to make your task bar look like that? I wonder if there's some incompatibility here. /needinfo

I've not changed anything to do with my taskbar in a while, and only noticed the PowerToys icon disappearing with the latest update.
Only thing I've done was update TaskbarX which I did before updating PowerToys

May be a duplicate of #12557

May be a duplicate of #12557
I've used TaskbarX for as long as I can remember and this has never been an issue for me, only started since the recent update of PT.

I've tried using an older version of tbx and got the same issue.

Incompatibility with TaskBarX has been known for a while, perhaps this option helps? https://github.com/microsoft/PowerToys/issues/12557#issuecomment-908629618
/needinfo


Fix the menu

Hello!
Not working menu in 2.0. Watch here:

In older version all working.

@TTATPuOT share your code please

@moxet https://gist.github.com/TTATPuOT/9319dfe6e35d2e7b5069

Looks ok to me: http://jsfiddle.net/09towerm/
Seems to be something else in your css?

Same code in a fiddle looks ok, apart from the missing search form, which you didn't include?
http://jsfiddle.net/09towerm/

Not seeing any issue
http://jsfiddle.net/7m62kfLe/


Support .net core 3.x +?

Are there any plans to support.net core 3 or above￼?

Hi there
Probably this past issue still applies (#185 ), in particular from this comment on: https://github.com/nspec/NSpec/issues/185#issuecomment-293923394
PS sorry for the quick reply


Release 2.2.0

Pull request for changes on existing TIGL code from Airbus Defence and Space.
Major changes:

Wing Profile code changed for requesting profile geometry with sharp and flat trailing edge
New class CCPACSModel for use as root component
Support for "simple" transformations in CTiglTransformation for performance increase
extended implementation of CCPACSWingComponentSegment

Thanks for this pull request. Just a general comment to the commit. This is a pretty huge commit, making it really hard to review. It would be great, if you would split it up into smaller commits in future.
By scanning quickly over the code, I saw a range of potential problems, which we should discuss:

[ ] Renaming of CCPACSComponentSegemt::findSegment into CCPACSComponentSegemt::FindSegment. It would be good, if existing signatures are not changed without good reason.

[ ] Duplicate IGES export code (CTiglExportIGES (DLR) vs. CTiglIGESWriter (Airbus)). It would be good if you could integrate your IGES stuff into CTiglExportIGES. BTW, what does  XSAlgo::AlgoContainer()->ProcessShape do?

[ ] Duplicate common functions: src/common/CTiglCommon vs src/common/tiglcommonfunctions.

[ ] Why getProfiles() methods in CCPACSFuselages and CCPACSWings? This is somewhat duplicate to getProfile(index) and blows up the class interface.

[ ] Why the destiction between open and closed wing profiles? The CPACS file should specify, whether a wing profile is open or closed (last and first point are identical).

[ ] The class CCPACSWingComponentSegment seems to be pretty blown up with methods. Many of them seem to be convenience methods, which is not considered as good design. Is this really necessary. Wouldn't a helper class not serve the same purpose?

Also, it would be great, if pull request would compile successfully. This would allow us to see also, whether all test cases still run successfully. Currently, travis fails to compile: https://travis-ci.org/DLR-SC/tigl/builds/124866357
You can also enable travis CI in you github fork, such that you directly get feedback after commiting.

Sorry for this big chunk, i'll try to split up the changes in smaller pieces in future.
Comments on your points:

Renaming of CCPACSWingComponentSegemt::findSegment into CCPACSWingComponentSegemt::FindSegment: renaming was probably done out of consistency reasons (public methods seem to be all upper case), but is of course not necessary. I will revert this change in order to not break the API
Duplicate IGES export code (CTiglExportIGES (DLR) vs. CTiglIGESWriter (Airbus)): CTiglIGESWriter is used by additional methods in CTiglExportIges, which will be merged in a separate step. So i'll remove CTiglIGESWriter for now
Duplicate common functions: CTiglCommon was created at a time where tiglcommonfunctions was not existing. I'll merge the functionality, which is currently used, into tiglcommonfunctions
Why getProfiles() methods in CCPACSFuselages and CCPACSWings: external functionality requires adding/removal of profiles during runtime. This was realized by adding new methods AddProfileand DeleteProfile to the CCPACSWingProfiles and CCPACSFuselageProfiles classes. In order to get access to these classes the getters were implemented in CCPACSWings and CCPACSFuselages classes. Proposals for alternative implementations are welcome.
open and closed wing profiles are required for different meshes. The wing geometry (shape) is used as a basis for meshing for the generation of analysis meshes for FEM, but also for aero codes. FE meshes require a sharp trailing edge, while aero meshes require an edge at the trailing edge of the wing. The same CPACS model should be used for the generation of both meshes, so the code for opening the closed profile was added. The current modification we did in the profile code is not CPACS conform, since it actively changes the profile points (e.g. extends or trims to x==1). My proposal would be that the modification of profile points (if required) is done by us outside of the TIGL code, so we can ensure in our application that all profiles have a sharp trailing edge (required for FE mesh) without modifying the existing profile code in TIGL. But we need the logic for getting a modified profile geometry with a "flat" trailing edge for the generation of the aero mesh.
The class CCPACSWingComponentSegment seems to be pretty blown up with methods: correct, sepearation in helper classes will be investigated

The current version of the source code compiled perfectly locally on my machine. Probably the used OCE version 0.16.1 is too old for the release-2.2.0 branch, which version is required? I have no experience with travis CI, but will have a look at it

Probably the used OCE version 0.16.1 is too old for the release-2.2.0 branch, which version is required?

Minimum required version is OCE 0.15 / OCCT 6.7.0.
The code should also compile up to 6.9.1. The TiGL master branch works also on OCCT 7.0.0.
Travis uses OCE 0.17 / OCCT 6.8.0 packages from here: https://build.opensuse.org/package/show/home:martinsiggel/OCE
To enable travis for TiGL, just create a travis account and enable it for TiGL. It will then automatically build for each commit. You don't need to configure anything, as this is already done in .travis.yml.

How are we dealing with the failing tests? Are you working on it? Do you need help?

I'm currently trying to run the tests on my machine in order to find out the reason for the failed tests. Thx, I'll contact you as soon as i need help.

Last commit is a proposal for fixing the test case tiglExportSimple.check_face_traits: The problem arises because we introduced the new class CCPACSModel as root component in the CTiglAbstractPhysicalComponent tree. This was done in order to support the definition of CPACS models, where absolute coordinates were used for the wing or fuselage transformations. Using the CCPACSModel as root component allows to keep the existing tree structure logic. The test failed because the CCPACSModel does not have a shape itself, so the generation of the fused plane geometry (CTiglFusePlane) did not support components without shape.
The proposed fix allows now for components without shape.

This fix looks okay. I somehow don't really like to have an separate CCPACSModel class, as this should be the CCPACSConfiguration class (which implements the CPACS aircraftModelType node). But it should be okay.
Now lets get the other tests working ;)

@RlanderRISCSW Since the 2.2.0 branch is pretty old and was never compiling successfully, I try to fix all problems that occur in the code before your pull request.

@RlanderRISCSW I put OpenCASCADE 6.80 fixes to the 2.2.0 branch. Please sync them with yours (its, best to make a rebase, if possible).
I have no failing tests on my side.

I added some note to my first post regarding CTiglTransformation. Please have a look to it.

Added support for requesting shapes of CCPACSWingSegment relative to Wing coordinate system, because the CCPACSWingComponentSegment code (and code for internal structures which will be merged separately) works in this coordinate system. The optional CoordinateSystem arguments were added in order to keep the original behavior (return shapes in global coordinates) so that client code does not break.

I reverted the findSegment method to the original TIGL code (as in release-2.2.0 branch), and added the separate private method findSegmentViaShape. The reason for the second method is that we got problems with the new implementation, which computes the eta/xsi values for the passed point. This computation fails in several cases, e.g.:

14:57:27 [ERROR] (CTiglOptimizer.cpp:74) Line search cannot find sufficient decrease, abort
14:57:27 [ERROR] (CTiglPointTranslator.cpp:172) Error in CTiglPointTranslator::translate: p = 11333.930200000001,0,-1212.05 x1 = 10916.5,0,-1212.05 x2 = 10916.5,747,-1212.05 x3 = 14711.32,0,-1212.05 x4 = 14709.330801269476,747,-1334.9049768693042
14:57:27 [ERROR] (CTiglPointTranslator.cpp:179) Resulting eta/xsi: 1.28885e-014,0.11

This is most probably caused by the use of millimeter-units in our CPACS files. Since this is not CPACS conform we plan to change our models for using meters as units, but this means additional conversions and testing in order to ensure that our other models (which are based on the CPACS geometry) still work (e.g. FE model). Therefore we need a solution which also works with millimeters for the moment.

Hej, almost all tests are working. Well done!

Modifications are finished now from my point of view. Please have a look at the changes and inform us when further modifications of the code should be made

Remarks have been checked and according code changes have been reverted. We are finished for now, please check again and tell us in case further code modifications should be executed


Add -i switch to hide resource errors from output

This fixes #153 by adding an -i switch to hide resource errors.

I would not use -i but only --ignore-resource-errors . its verbose but this option should be rare - 404s are generally bugs unless its testing handing of these conditions.
Also a test for this please.

In the tests we're running we call an api via ajax, and the api replies
with non 200 codes. It may reply with 404 when an item is not found, which
is something we test for.
We also test for malformed input which also makes the api reply with non
200 codes.
These api calls show up in logs.
See here for an example:
https://travis-ci.org/deployd/deployd/builds/45888892
Scroll to the bottom.
I will rename it, but I'm not sure how to test it or if a test is really
relevant since the change is so minor and straight forward.

I pushed another commit where it is renamed as per your suggestion @nathanboktae
Regarding tests, I looked a bit at them and I don't know how to test this without a web server. All the tests seem to be local right now, and resource errors only happen with remote requests. Any ideas?

Yeah I was thinking about it more, and it is tricky as there is no depedency outside the box the build is running on, and no local server yet. Also no test for the existing functionality either.... I'll take a crack at it.
Yes thanks for removing -i - I just checked and mocha uses it to invert -g, so we'll use it that way too when we implement -g (#145)

Yeah I was thinking about the test, and it is tricky to implement as we do not have a dependency outside the box for the CI build, nor a server running during tests. Also nor do we have tests for the existing functionality! I'll take a look at it later.
Also I did double-check and mocha uses -i to invert grep results, so we'll implement that when -g gets implemented (tracked in #145)

Thought I already left this comment but I didn't release resource errors trigger for XHRs - I only thought they triggered for missing resources like scripts, images, CSS. Now it makes it a more common scenario. Maybe the shorthand could be -I - thoughts @metaskills ?

TL;DR - Just pick anything that makes sense.
Names of args is hard :( which side do we lean too. I think there are seldom good answers and we should just be careful and cognitive. So first side (mocha) or (phantomjs) to implement the need is maybe our winner :)

By the way, a new release having this new functionality would be great so we can plug it into deployd and have our Travis logs look cleaner. :)

You can point directly at master for the moment. I started working on the test for this and it's easy with a bad css, script, or image url, so I'll add it soon.

Is there a way to use this option within grunt config object with mocha_phantomjs plugin?
E.g.:
mocha_phantomjs: {
  all: {
    options: {
      '--ignore-resource-errors': 'true'
    }
  }
}

Sorry if a silly question, I'm new to all this.

@michasko no mate, the '--ignore-resource-errors' option is for mocha-phantomjs only.

Not true - we are using it in our gruntfile. remove the --:
    mocha_phantomjs: {
      all: ['tests.html'],
      options: {
        'ignore-resource-errors': true
      }
    }

@nathanboktae yes, after a lot of tries (camelCase, single dash at the beginning) I went through the code and figured it out. I forgot to update my post for others, though. Thanks!


Did elastic.NewClient at loop cause memory leak?

I run it with es mode,then I found the RES grow up from about 40MB to 2.8GB after startup three days. Does it occur memory leak? I am newbee at go,so I guess the esclient may cause this or something elase~

I think elastic.NewClient at loop is not reason to memory leak. Normally last elastic client will clear when golang gc.
Could you use pprof tools to analyze memory?

I think elastic.NewClient at loop is not reason to memory leak. Normally last elastic client will clear when golang gc. Could you use pprof tools to analyze memory?

Not yet. I am learning to use pprof. Currently I reuse the elastic client which is the most quickly way for me. The most different is that stat data maybe too big. When I launch with log mode, the generated file size is 22MB at every fetch. My Elasticsearch version is 8.1.0. As I known there is no something special. So I will try to use tools to analysis it.


✨ Fully merge Pydantic Field with SQLAlchemy Column constructor

Abstract
The proposed changes modify the Field constructor to take all parameters defined on the SQLAlchemy Column directly, instead of just a few.
This makes the parameters sa_column, sa_column_args, and sa_column_kwargs completely obsolete!
There is no negative impact on current functionality. All test cases still pass without me modifying them. Test coverage is also not reduced.
Rationale
The definition of model fields should be fully in line with the goals of SQLModel, as stated in the documentation.
Intuitive to write
People coming from an SQLAlchemy background will immediately feel at home with the Field constructor, just as people from a Pydantic background already see all the familiar features of it. This honors the project's intent:

Designed to be easy to use and learn. Less time reading docs.

Until now, leveraging all Column features was a little cumbersome and unclear, as evidenced by numerous issues/questions (see below) for trying to figure out how to design all but the most simple database models. The sa_column-parameters did allow all that functionality, but sometimes led to unexpected behavior for many people.
Easy to use
Here are just a few examples of how these changes would make SQLModel easier to use.
Defining custom SQL types until now required initializing and passing a Column instance to sa_column. This led to almost all database-related Field arguments to be ignored. This is how you had to do it:
class MyModel(SQLModel, table=True):
    custom_field: int = Field(
        sa_column=Column(
            CustomType(impl=Integer()),
            index=True,
        )
    )

Whereas now, you can now write this:
class MyModel(SQLModel, table=True):
    custom_field: int = Field(
        type_=CustomType(impl=Integer()),
        index=True,
    )

Adding additional constraints, defining a different DB column name, etc. all required using sa_column_args/sa_column_kwargs like this:
class AnotherModel(SQLModel, table=True):
    foo: int = Field(
        default=42,
        sa_column_args=[
            CheckConstraint('>0')
        ],
        sa_column_kwargs={
            'name': 'bar',
            'server_onupdate': FetchedValue(),
        }
    )

Now you just need to do this:
class AnotherModel(SQLModel, table=True):
    foo: int = Field(
        CheckConstraint('>0'),
        default=42,
        name='bar',
        server_onupdate=FetchedValue(),
    )

Compatible
The package remains just as compatible with FastAPI, Pydantic and SQLAlchemy as before. If anything, allowing to pass all column parameters directly makes that compatibility even more obvious to people coming from SQLAlchemy to SQLModel.
Extensible/Short
see above
Implementation

Details (click me)
The changes cover basically only three things: The FieldInfo class, the Field function, and the get_column_from_field function. Here are the broad points:
class FieldInfo

SQLModel's custom FieldInfo class (inheriting from the Pydantic one) has been extended to incorporate all the column parameters that have been missing.
Corresponding __slots__ were defined mimicking the Pydantic approach.
Additionally, the attributes were all explicitly type-annotated for easier use "down the line".
The __init__ method has been streamlined, but a new helper method get_defined_column_kwargs was added which comes into play later to construct a corresponding Column.

def Field

Obviously, this is where the new function parameters have been added to be passed along to the above mentioned FieldInfo.
DeprecationWarnings have been added for the sa_column-parameters.
The default function parameter has been made keyword-only (like all the rest) and placed behind the newly added variable-length positional arguments *args. (This is technically the only backwards incompatible change.)

def get_column_from_field

Refactored and extensively commented.
Constructs the *args and **kwargs for the Column based on the provided field as before, but supporting all possible parameters now.
Still sets sensible defaults, such as deriving a column type (if it was not provided) based on the field type, and deciding "nullability" based on other field settings.

Affected issues (updated 2023-01-04)

#63 - partially fixed
#93 - simplified, more intuitive
#137 - obvious solution
#178 - partially solved
#292 - solved
#298 - simplified, more intuitive
#314 - fixed
#319 - obvious solution
#326 - simplified, more intuitive
#404 - less verbose solution
#447 - simplified
#464 - fixed
#466 - fixed
#491 - should be fixed, not sure
#503 - made irrelevant
#521 - gets more intuitive solution

A major anticipated benefit of the proposed changes is the reduction of questions about "how to do SQLAlchemy-thing XYZ".
Affected PRs (updated 2023-01-04)

#111 - made obsolete
#158 - made obsolete
#251 - conflicting, but can be easily combined/rebased
#366 - arguably made obsolete, since you could directly pass the SQL type like Field(YourType(**your_kwargs)), but this is debateable
#372 - made obsolete, if the sa_column-style parameters are dropped/deprecated, as I would suggest
#505 - made obsolete

It is obviously not my intention to trash other people's work. I respect the effort they put in, just think that those changes are no longer needed/sensible in conjunction with this PR.
Caveats & arguments against this

Details (click me)
Huge function signature
The Field function's signature will be even larger and perhaps overwhelming for newcomers.
My response would be that a large function signature is not an argument per se, and that all arguments remain optional, which allows the actual code to be as concise as possible.
Commitment to incorporate future additions
Changes/additions to the Column parameters in SQLAlchemy in the future would necessitate adjusting the SQLModel Field function accordingly. Although this is no different from how Pydantic changes already need to be propagated to the custom Field constructor, going the route suggested in this PR would require keeping track of both base packages (Pydantic and SQLAlchemy) in the future, to ensure maximum compatibility/familiarity.
I don't think this is such a bad thing, since SQLModel aims combine their functionality. If/when SQLAlchemy 2 drops, major changes (maybe even backwards incompatible) may be necessary anyway.
Possible future parameter conflicts
Parameter names for Pydantic's Field and SQLAlchemy's Column might conflict in the future.
This is hypothetical and it would not necessarily even cause problems, but if it does, a possible solution would be to distinguish parameters that are completely unrelated with prefixes like sa_param and py_param or something similar.
Backwards incompatible default parameter
The default parameter for the Field function is now keyword-only.
This is technically the only backwards incompatible change in this PR. However I have a few arguments for this:

The documentation so far used the explicit keyword-argument notation everywhere already. This is also why all test cases still pass. Nowhere was a default passed as a positional argument.
I see no reason for the "preferential treatment" of the default parameter in the  Field function. This may somewhat make sense with the original Pydantic version of Field because there you would normally assign the default value to your model field directly. However, I don't find it intuitive/appropriate at all in the context of SQLModel since models are intended to represent database tables and fields represent database columns. The default value for a field/column is just one of many parameters and should not be treated differently. I do concede however that this makes is slightly less familiar to people that come from a Pydantic background, because they may be used to using a positional default.
This is the only way to reasonably allow using positional arguments as with SQLAlchemy's Column.
SQLModel is still in its infancy, so 100% backwards compatibility may not even be a requirement yet. This is ultimately for @tiangolo  to decide, of course.

Future To-Dos

Details (click me)

Make it possible to provide the column type as the first positional argument to Field as it is with SQLAlchemy Column. This should be fairly straight-forward.
Expand the same logic of dropping the sa_-style parameters in favor of full integration to Relationship attributes. This may be more difficult; I haven't had the time to look into that.
Add documentation examples demonstrating that all familiar Column configurations work the same with SQLModel fields.

I hope you will find the time to consider this, @tiangolo. I am looking forward to discussions, counter-arguments, and proposed changes to this from other contributors and am willing to keep working on this.

It would be nice if ForeignKey.ondelete and ForeignKey.onupdate were also included, to avoid having to explicitly instantiate ForeignKey in such common use cases.
class AnotherModel(SQLModel, table=True):
    foo: int = Field(foreign_key='mymodel.custom_field`, ondelete='CASCADE', onupdate='CASCADE')

@nuno-andre I appreciate your suggestion, but I don't think this is a good idea for two reasons:
1) PEP 20
The only reason I didn't remove the foreign_key parameter from the Field function altogether in my PR, is that I wanted to honor @tiangolo's original intent (presumably) of having a shortcut for the most common use case, namely simply referencing the column to point the key to, which I think is a valid approach. And because this keeps my proposed changes backwards compatible.
However, my actual intent with this PR is to mirror Pydantic's Field and SQLAlchemy's Column interfaces in this one function as closely as possible to make it instantly familiar to people from both backgrounds. I think this is accomplished here. You can define foreign keys with non-default attributes just like you would in SQLAlchemy:
Field(ForeignKey("table.key", ondelete="CASCADE", onupdate="CASCADE"), ...)

If we had the two parameters you proposed in addition, we would have yet another way to do the same thing. As I argued in my response to @amisadmin above:

There should be one-- and preferably only one --obvious way to do it.

I would argue that this obvious way is there now, and that it is not a big ask (or a lot of added verbosity) to pass a ForeignKey instance with those same keyword arguments, if you need them. And actually, with my proposed approach (ForeignKey as a positional argument like in SQLA), there is about the same amount of code as there would be with your suggestion and the foreign_key keyword-argument.
2) Inconsistency & partially meaningless parameters
The ondelete and onupdate parameters are only ever meaningful in conjunction with foreign keys. Yet most fields typically aren't foreign keys. In those cases these parameters are meaningless. Most (though not all) other Field parameters on the other hand are meaningful, even if used with their default values. Note that even foreign_key arguably is more meaningful since its default means that the field is not a foreign key. The default to ondelete means nothing at all, unless foreign_key is passed explicitly.
Conversely, a ForeignKey instance encapsulates all the foreign key logic in one object and thus abstracts it from Field. That way for Field the meaning is either "this will be a foreign key" or "this will not be a foreign key". A foreign key will be treated the same as any other of the countless parameters a field/column may have. Why should it be treated differently than the column type or a constraint for example? In my opinion, consistency is important, especially when the interface is so complex already.

In conclusion, although I recognize the benefit of having those dedicated parameters, I think the drawbacks outweigh this benefit significantly and therefore I don't think these parameters should be included. If you want to pursue this further, just like I suggested in the other discussion above, maybe you'll want to offer your own PR, when/if this is merged, and @tiangolo may agree with you and disagree with my reasoning.
I hope this makes sense. Thanks for the feedback though.

This is amazing work. Are there any plans on reviewing/merging it, @tiangolo ? Or do we need to provide something extra to make sure that these changes are valid and ready to be merged?

For what it's worth, I just rebased this branch once more on top of the most recent main commits, so as to get rid of the merge conflicts.
I also gave the current state of PRs and issues a cursory review and can add the following to the lists I started above.
Affected issues (continued)

#464 (fixed)
#466 (fixed)
#491 (should be fixed, not sure)
#503 (made irrelevant)
#521 (gets more intuitive solution)

Affected PRs (continued)

#505 (made obsolete)

Would love to get feedback on this soon. I am still willing to continue working on this.

@tiangolo Is there anything missing in order to have this PR merged? It looks like an amazing work has been put here and could give a lot of value to the community as this truly affect lots of PRs and open issues SQLModel currently have.

@daniil-berg In my opinion, the goal of SQLModel is not to replicate SQLAlchemy with a Pydantic syntax, but to add persistence to Pydantic models. Under this point of view, the classes assigned to attributes should signify the attribute typology (as subclasses of FieldInfo) and not reference behaviors outside the data model (like in ForeignKey).
Regarding the inconsistency of including parameters not applicable in all cases, this is something that the Pydantic's Field already manages (gt, pattern, min_lenght...) and validates in each instance. IMO this is a wise design decision that allows to implement a very powerful way to easily define data models avoiding code bloat and reducing the cognitive load.
In any case, this PR seems to me an amazing work that certainly deserves to be merged.

Thank you @daniil-berg for the thorough explanation/argument and all the work! 🤓 🍰
And thanks everyone for the discussion here. ☕
I actually prefer not to fully merge the signatures of both Field and Column. There are several things I'm not very fan of in the design of Column, for example receiving an arbitrary sequence of arguments including name, type, constrains, but that at the same time are not required. This has to be kept like that in SQLAlchemy for backwards compatibility, but I prefer not to adopt the same API in SQLModel.
So I have intentionally simplified and limited the things I support in SQLModel, to work for the majority of use cases (say 90%) in a very simple and intuitive way (at least I hope so) without all the more advanced/exotic features that SQLAlchemy supports.
And then for those advanced use cases, there's a way to escape and use all the features from SQLAlchemy, defining the full column, all the arguments, etc.
I see there are problems this PR would help with, here's my point of view on each of them:

Simplify setting a SQLAlchemy type:

This seems to be a common use case, there were 2 or 3 PRs with variants of it, I took https://github.com/tiangolo/sqlmodel/pull/505, so now there's support for sa_type in the next version, 0.0.11.

sa_column is not compatible with several parameters: sa_column_args, sa_column_kwargs and others like index, nullable:

I added runtime and type checks to ensure sa_column is not used with them. On runtime, an error will be raised, and with the new type tricks the editor will complain if an incompatible parameter is used (https://github.com/tiangolo/sqlmodel/pull/681), this will also be available in 0.0.11.

It's not obvious how to do the equivalent of SQLAlchemy X in SQLModel (for many types of advanced or exotic X):

I will document many of these combinations in the docs, explaining how to use sa_column_args, sa_column_kwargs, sa_column, etc.
I'll add this documentation soon but later, after migrating to SQLAlchemy 2.0 and Pydantic 2.0.

Thanks again for the work and all the help with the rest of the project! 🍰


GLTF2 loader

I think as gltf2 growing as standard model/scene format would be good to have support for it

There is also a fbx to gltf converter, https://github.com/facebookincubator/FBX2glTF

Yeah, I would like to support this, and it shouldn't be terribly hard given that it's a JSON-based format. It probably makes sense to split out individual formats into a separate utility library (libraries?).

This seems to be relevant: https://github.com/KhronosGroup/glTF-CSharp-Loader

Just note here dude, i just update the assimp .net version to 4.1.0 on windows as it supports GLTF.
https://github.com/amerkoleci/assimp-net, https://github.com/assimp/assimp/releases/tag/v4.1.0

@amerkoleci Cool! I remember trying to do that, but I couldn't get it to load GLTF files even when building from source. I kept getting an error of some sort -- can't recall anymore.
I would probably be happier getting assimp working easily with Veldrid than I would be doing something GLTF-specific. I'm using assimp in my projects personally.

I'm working towards Veldrid-based GLTF viewer. I have some progress:
https://gyazo.com/81b59aa949681832bea8954837d142ab
@amerkoleci would you help me with the project? :)

@gleblebedev that looks cool, actually I'm working on my C++ game engine during my spare time (https://github.com/amerkoleci/alimer)


Could not find the drag and drop manager in the context of ResourceEvents.

Hi guys,
Could you please help me fix this error?
this is my component:
          <Scheduler
            schedulerData={viewModel}
            prevClick={this.prevClick}
            nextClick={this.nextClick}
            onSelectDate={this.onSelectDate}
            onViewChange={this.onViewChange}
          />

this is how I export it:
export default withDragDropContext(Basic);
I have tried to wrap schedule in:
<DndProvider backend={HTML5Backend}>
          <Scheduler
            schedulerData={viewModel}
            prevClick={this.prevClick}
            nextClick={this.nextClick}
            onSelectDate={this.onSelectDate}
            onViewChange={this.onViewChange}
          />
</DndProvider>

and export it
export default Basic;
then i get the error that the component is not being rendered properly:
` React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
Check the render method of Basic.
in Basic (created by Context.Consumer)`
I am using the latest packages:
"react-big-scheduler": "^0.2.7",
 "react-dnd": "^7.5.0",     "react-dnd-html5-backend": "^7.5.0",
Thanks!

the versions of these packages should work for you "react-big-scheduler": "^0.2.6",
"react-dnd": "^5.0.0","react-dnd-html5-backend": "^5.0.1" and also make sure you
then wrap your component like this, withDragDropContext(component) while exporting it

Thanks! It works! I had to remove the "reacd-dnd" and "html-backend", from packages.json, reinstalled everything and now works perfect! :)

Is anybody able to get this to work with latest version of react-dnd?  I've tried

/* Your Drag-and-Drop Application /

and
const DndContext = createDndContext(Backend);

/ Your Drag-and-Drop Application */

etc...
But none of these works.

Is anybody able to have this works with the latest version of reac-dnd?  I have tried wrapping with DndProvider, DndContext, etc.  but nothing seems to work.

Basic example worked for me with these versions:
"react-big-scheduler": "^0.2.6",
"react-dnd": "^7.5.0",
"react-dnd-html5-backend": "^7.5.0",
exported with withDndContext(MyScheduler)
import {DragDropContext} from 'react-dnd'
import HTML5Backend from 'react-dnd-html5-backend'
export default DragDropContext(HTML5Backend);

It's not working, tried with every version. with react 17.0.2. need help


If possible,what about add automated change setting?

Your applicalition is wonderful !!
But in macos,there is still no app can get wallheaven's pictures and automateky set to the screen.
Hope you can realize it!

Thanks! I thought about this feature but gave up since you can set your download folder as a default folder for mac wallpapers, if you still think this feature can be useful let me know!

Thanks for your reply!
I think your app is the only independent app for mac using wallheaven’s wallpaper. I really appreciate it.
Of course, we can set a folder as a place to switch downloaded wallpapers, while if we can switch pictures only automatically by random scratch in website，and the pictures we set are cached, maybe it will be another way to use amost limitless pictures.
发件人: Luis @.>
日期: 星期三, 2023年3月15日 08:37
收件人: luisflorido/wallhaven-desktop @.>
抄送: Panamaz @.>, Author @.>
主题: Re: [luisflorido/wallhaven-desktop] If possible,what about add automated change setting? (Issue #2)
Thanks! I thought about this feature but gave up since you can set your download folder as a default folder for mac wallpapers, if you still think this feature can be useful let me know!
―
Reply to this email directly, view it on GitHubhttps://github.com/luisflorido/wallhaven-desktop/issues/2#issuecomment-1469058619, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASXFW2LFTWWXQO7QYTE5FU3W4EFNHANCNFSM6AAAAAAVOJ2X5E.
You are receiving this because you authored the thread.Message ID: @.***>


Win compilation fix

The two new definitions can go in the same add_definition as the one for Qt6 widgets.

PR has been changed accordingly.

Why is windows.h needed?

New version uses only the required defines, instead of windows.h.

Better, but since windows.h is no longer included, NOMINMAX can also be deleted, right?

Indeed, PR updated.


Fixbfs

fixes a bytemap bug and also the bfs benchmark implementation

Codecov Report
Base: 80.92% // Head: 80.95% // Increases project coverage by +0.02% :tada:

Coverage data is based on head (4991bb8) compared to base (d583080).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #91      +/-   ##
==========================================
+ Coverage   80.92%   80.95%   +0.02%
==========================================
  Files          46       46
  Lines        4749     4751       +2
==========================================
+ Hits         3843     3846       +3
+ Misses        906      905       -1

Impacted Files
Coverage Δ

src/sparsebytemaplevels.jl
91.00% <100.00%> (+0.42%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


fix crash in presence degradation reporter

Today if you try to use Presence Degradation Reporter with a Ditto SDK >= 4.8.0 the app will crash with the following stack trace:
Process: live.ditto.dittoupdatetest, PID: 24145
java.lang.NoSuchMethodError: No static method upsert$default(Llive/ditto/DittoScopedWriteTransaction;Ljava/lang/Object;Llive/ditto/DittoWriteStrategy;ILjava/lang/Object;)Llive/ditto/DittoDocumentId; in class Llive/ditto/DittoScopedWriteTransaction; or its super classes (declaration of 'live.ditto.DittoScopedWriteTransaction' appears in /data/app/~~_AShLrljJsZ9i23CNU4Lpg==/live.ditto.dittoupdatetest-hI_e-kQ92pOsuTCw8rdjuQ==/base.apk!classes6.dex)
	at live.ditto.presencedegradationreporter.repositories.PeersRepository$upsertPeers$2$1.invoke(PeersRepository.kt:43)
	at live.ditto.presencedegradationreporter.repositories.PeersRepository$upsertPeers$2$1.invoke(PeersRepository.kt:41)
	at live.ditto.DittoStore$write$1$1.invoke(DittoStore.kt:354)
	at live.ditto.DittoStore$write$1$1.invoke(DittoStore.kt:347)
	at live.ditto.TransactionsKt.commitAndReturn(transactions.kt:37)
	at live.ditto.TransactionsKt.commitAndReturn$default(transactions.kt:31)
	at live.ditto.DittoStore$write$1.invoke(DittoStore.kt:347)
	at live.ditto.DittoStore$write$1.invoke(DittoStore.kt:346)
	at live.ditto.internal.ffi.DittoHandle$withUnwrapped$1.invoke(DittoHandle.kt:33)
	at live.ditto.internal.ffi.DittoHandle$withUnwrapped$1.invoke(DittoHandle.kt:31)
	at live.ditto.internal.ffi.DittoHandleWrapper.with(DittoHandleWrapper.kt:43)
	at live.ditto.internal.ffi.DittoHandle$DefaultImpls.withUnwrapped(DittoHandle.kt:31)
	at live.ditto.internal.ffi.DittoHandleWrapper.withUnwrapped(DittoHandleWrapper.kt:9)
	at live.ditto.DittoStore.write(DittoStore.kt:346)
	at live.ditto.presencedegradationreporter.repositories.PeersRepository$upsertPeers$2.invokeSuspend(PeersRepository.kt:41)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:115)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:103)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:793)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:697)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:684)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@1ff0f6c, Dispatchers.Main.immediate]

This is a runtime exception and occurs because the JVM couldn't find a method that matches the above method signature. A method that matches this does not match the generated java bytecode so it crashes with this exception.
The workaround for now is to explicitly add argument labels to functions so that it calls the right method. I am still investigating what work may need to be done on the SDK side to fix this.
I have isolated it to Ditto SDK 4.8.0 and above because of changes in this PR: https://github.com/getditto/ditto/pull/13336

Yikes! So, adding the optional hint parameter to DittoScopedWriteTransaction.upsert caused bytecode incompatibility.
Can this be resolved with a gradle clean?

clean didn't seem to fix it.
I imagine the same would be true for DittoCollection.upsert() as well, but I haven't tested that.

@rajramsaroop @phatblat did we log something upsteam on the SDK end to dig deeper? If so, can we link it here?


Travel advice index countries as links

Allow synonyms in travel advice items, and update example of travel
advice index to show expanded links rather than explicit countries
items in details.
(Test failures are in downstream builds and appear unrelated.)

Is there a plan to use this sort of link on travel advice documents as well as the index?


[docs] Translate the documentation to Chinese / 将文档翻译成中文

Summary 💡
There is a huge community of Chinese developers https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_speakers

But very few actually speak English: https://www.quora.com/What-of-Chinese-speak-English, likely fewer than 10%.
Translating the docs could be a great growth opportunity, especially for MUI X, Base UI, and MUI System which are a lot less design-dependent.
Examples 🌈

https://recharts.org/zh-CN/
https://www.qt.io/zh-cn/

Context

https://mui-org.notion.site/Docs-localization-what-s-next-3f370280b58f446fbb5559dfc08fe03e
Struggle to communicate with Chinese users https://www.notion.so/mui-org/Lee-jijyun-f4786a2f39344d428564b8722d74a3fa?pvs=4#6ed6fb0ac5f74be7904dfb1e33dac17a

总结💡
有一个庞大的中国开发者社区 https://zh.wikipedia.org/wiki/按人口排列的语言列表

但实际上很少有人会说英语：https://www.quora.com/What-of-Chinese-speak-English，可能不到 10%。
翻译文档可能是一个巨大的增长机会，特别是对于 MUI X、Base UI 和 MUI System 来说，它们对设计的依赖性要小得多。
例子🌈

https://recharts.org/zh-CN/

When it comes to the community, I suspect that we would need to duplicate it. Have a GitHub repository just for issues with Chinese users, and a moderator that would connect them back to English issues, as the source of truth.

Hi Olivier, would love to help with the Chinese translation issue. I saw the note that everything is now removed, please let me know how I can help.

@ChTiSh Upvoting the issue would already be nice.
While I don't believe in the potential of growing Material Design for the Chinese community, I'm convinced that with Base UI, MUI X Data Grid, MUI X Charts, MUI System, it would make sense.
Part of the challenge is visible from https://www.notion.so/mui-org/docs-infra-Chinese-localization-3f370280b58f446fbb5559dfc08fe03e?pvs=4#2d2545623c3346f6b6df298787ede176:
For the localization to truly benefit users, you need a Chinese community

Having a staff who speak Chinese and the docs translated is not enough, e.g. recharts example. We have one team member who speaks Chinese: @mj12albert.
What seems to truly rule a growing Chinese community is: % of issues written in Chinese, number of questions answered in https://www.oschina.net/, https://segmentfault.com/.

In any cases, there is no Chinese community possible without translation, so I think we should do it. As for when, I think that it should match with when we fill a React Engineer - Docs-infra role.

Thank you for the info, Olivier. I've upvoted the issue. The React Engineer - Docs-infra does not appear to work for me.
I understand the trade-offs, but also see great potential. I noticed that MUI has not tried the Google Translate and community support model. I'm curious if this approach could serve as an initiator to attract and keep the Chinese community engaged. While it would definitely introduce some maintenance overhead, the translation work could be an excellent first issue for developers eager to contribute -- especially given the current challenges in getting a PR accepted into any established open source rep. I've also noticed that moving baseUI to a separate repo is a 2024 initiative, could that serve as proof of concept? I would love to get an issue to work on.


Control (Add and remove)  on Checkbox OnChange

Hi,
I am trying to remove FeatureLayer added to Map onChnage of Checkbox.
Please help me how can I do this.

Can you please post some code?  Or a codesandbox demonstrating the issue you are experiencing?  This does not sound like an issue with this plugin rather than a question about how to code something.  Please post a minimal reproducible example.

import React, { useEffect } from "react";
import L  from "leaflet";
import 'leaflet/dist/leaflet.css';
import { MapContainer, TileLayer, GeoJSON, useMap} from "react-leaflet";
import axios from "axios";
import {  FeatureLayer } from "react-esri-leaflet";
const MyData = () => {
const [data, setData] = React.useState();
const map = useMap();
useEffect(() => {
const getData = async () => {
const response = await axios.get(
"https://gist.githubusercontent.com/UmairMughal901/486a7f64d1325ea8cb0c4f91925c5d85/raw/521f91aedb0b08b02ab7746e332041e31dc72360/map.geojson"
);
setData(response.data);
};
getData();
}, []);
if (data) {
// These next 3 lines purely for debuggins:
const geojsonObject = L.geoJSON(data);
//map.fitBounds(geojsonObject.getBounds());
//console.log(geojsonObject);
// end debugging
return <GeoJSON data={data} />;

} else {
return null;
}
};
const Map = (props) => {
return (
<MapContainer
doubleClickZoom={true}
id="mapId"
zoom={5}
center={[32, 71]}
>
  <MyData />

  <FeatureLayer url={'http://<IP_ADDRESS>:6080/arcgis/rest/services/Punjab/PB_irisportal_pg31_v_02112017/MapServer/12'}
  eventHandlers={{
    load: () => console.log('featurelayer loaded')
  }}
  />

  <TileLayer
    url="https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png"
    attribution='© OpenStreetMap contributors'
    maxZoom='13'
  />

</MapContainer>

);
};
export default Map;

Thank you for your prompt reply. I make a sandbox example and share it.

https://codesandbox.io/s/table-of-content-ldvwh?file=/src/Map.js

I don't see any checkbox in your example.  You created a sandbox but I am still very unclear on what you are trying to accomplish.
Ultimately, adding and removing a layer based on the checked status of some input field is the same as conditionally rendering any react component based on a state variable.  That is not specific to react-esri-leaflet, but to react-leaflet in general.  As this is not an issue with this plugin, I am closing this issue.  I recommend you post a question on stack overflow.  If you do that, post a link here and I can take a look and attempt an answer there on SO.


Image width and height are nullable

Image width and height are null if not known:
https://developer.spotify.com/documentation/web-api/reference/object-model/#image-object
These should be represented as nullable int in the Image model :(
This will be a breaking change in vNext

@DanielLarsenNZ Can this issue be closed out now with the v3.0.1 release?

Yes! Thanks again 👍


Provision a Container in Kubernetes Provider

Hi @agrare  and @Fryguy ,
I am using appliance_console manageiq version Morphy.
I connected my kubernetes cluster as a container provider in manageiq.
Now, I need to know how to provision a kubernetes container using manageiq. Because I can't see any catalogs service for generic Kubernetes.

Hi,
Please look at this issue.
I have an doubt, we can also run ansible playbook for provisioning a
container in generic kubernetes.
If it done. How?
Kindly advise me..
On Mon, Jun 20, 2022, 6:38 PM Jason Frey @.***> wrote:

I don't think we support creating containers directly in the catalog,
however you might be able to use openshift templates. @agrare
https://github.com/agrare do you know?
—
Reply to this email directly, view it on GitHub
https://github.com/ManageIQ/manageiq/issues/21945#issuecomment-1160428169,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZO3IVSC2K2KCQV2VGF3GGTVQBUOBANCNFSM5ZELXLPQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Correct I don't see catalog support for container providers, provisioning OpenShift Templates is a simple operation.

Yeah certainly you can do anything you want if you create your own automate workflow with ansible scripts to do the work.

Thanks, I'll check it out.
On Tue, Jun 28, 2022, 12:12 AM Adam Grare @.***> wrote:

Yeah certainly you can do anything you want if you create your own
automate workflow with ansible scripts to do the work.
—
Reply to this email directly, view it on GitHub
https://github.com/ManageIQ/manageiq/issues/21945#issuecomment-1167741328,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZO3IVWK7KYYM6HAWS36XTDVRHYYFANCNFSM5ZELXLPQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Space bar should toggle run/pause

Version: 0.8.11
Platform: All
Based upon this Joulescope forum post.
Description
The Joulescope UI Control widget has a run/pause button that controls current/voltage/gpio streaming from the Joulescope instrument.  When you noticed that your Joulescope has captured an interesting event, you may want to quickly stop the capture.  Finding a UI button is fine, but can take extra time and effort.
Expected Behavior
The Joulescope UI should have the simplest and fastest way to run/pause data capture.  It would be great if we could allocate the keyboard space bar to this operation.

Fixed in 0.8.16.


Maintainers file

Hello everyone,
does it make sense to keep this file? https://github.com/keptn/keptn/blob/master/MAINTAINERS
all of the information is in peribolos and keeping this up to date is cumbersome

same for this file https://github.com/keptn/keptn/blob/master/CODEOWNERS

I think we can remove the MAINTAINERS file since those are managed in the community repo by peribolos anyways. The CODEOWNERS file is in use and can't be removed. The code owners file defines, who needs to approve changes to specific parts of the code, which is important for PR reviews.

Since Keptn V1 has reached EOL on December 22nd, 2023, this issue has been closed.


Implement a skeleton for sample app.

Fixes #1
This PR

Adds panel layout to MainActivity.
Fix one critical bug in the library.

Can you rebase to master to have the CI checks also

Rebased and pushed


Outdated getting started instructions

The getting started guide contains instructions for building Dex from source using go get. We should promote using the prebuilt docker images instead.
The source installation instructions should be updated and optionally moved to the development section (see #77)

I've been going through the "running a client" section of the getting started page. As a complete dex beginner, I'm not able to get it running.
It compiles correctly, and this may be an audience level issue, where I'm not the target audience, it seems like there are some steps missing -- I'm not sure what else needs to be running in order for the example to work.

I've been going through the "running a client" section of the getting started page. As a complete dex beginner, I'm not able to get it running.
It compiles correctly, and this may be an audience level issue, where I'm not the target audience, it seems like there are some steps missing -- I'm not sure what else needs to be running in order for the example to work.


RuntimeError: DataLoader worker (pid 1335) is killed by signal: Killed.

Why did I make this error?
Traceback (most recent call last):
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1120, in _try_get_data
data = self._data_queue.get(timeout=timeout)
File "/root/miniconda3/lib/python3.8/multiprocessing/queues.py", line 116, in get
return _ForkingPickler.loads(res)
File "/root/miniconda3/lib/python3.8/site-packages/torch/multiprocessing/reductions.py", line 305, in rebuild_storage_fd
fd = df.detach()
File "/root/miniconda3/lib/python3.8/multiprocessing/resource_sharer.py", line 57, in detach
with _resource_sharer.get_connection(self._id) as conn:
File "/root/miniconda3/lib/python3.8/multiprocessing/resource_sharer.py", line 87, in get_connection
c = Client(address, authkey=process.current_process().authkey)
File "/root/miniconda3/lib/python3.8/multiprocessing/connection.py", line 508, in Client
answer_challenge(c, authkey)
File "/root/miniconda3/lib/python3.8/multiprocessing/connection.py", line 752, in answer_challenge
message = connection.recv_bytes(256)         # reject large message
File "/root/miniconda3/lib/python3.8/multiprocessing/connection.py", line 216, in recv_bytes
buf = self._recv_bytes(maxlength)
File "/root/miniconda3/lib/python3.8/multiprocessing/connection.py", line 414, in _recv_bytes
buf = self._recv(4)
File "/root/miniconda3/lib/python3.8/multiprocessing/connection.py", line 379, in _recv
chunk = read(handle, remaining)
ConnectionResetError: [Errno 104] Connection reset by peer
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "train.py", line 184, in
main(cfg)
File "train.py", line 110, in main
loss = train_one_epoch(
File "/root/autodl-tmp/Bilinear-Matching-Network/engine.py", line 22, in train_one_epoch
for idx, sample in enumerate(data_loader):
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 628, in next
data = self._next_data()
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1316, in _next_data
idx, data = self._get_data()
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1282, in _get_data
success, data = self._try_get_data()
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1120, in _try_get_data
data = self._data_queue.get(timeout=timeout)
File "/root/miniconda3/lib/python3.8/site-packages/torch/utils/data/_utils/signal_handling.py", line 66, in handler
_error_if_any_worker_fails()
RuntimeError: DataLoader worker (pid 1335) is killed by signal: Killed.
my gpu is 2080Ti, menmery is 40G

same problem


Make new release

The current version, 1.4.0, still have the beautifulsoup4==4.5.3 dependency.  Unluckily, beautifulsoup4 really needs to be upgraded, because the previous version uses features deprecated in Python 3.7 and removed in Python 3.8. I noticed that the setup.py is already modified to take the new >=4 version tag in master, so a simple release of the current code should be sufficient to fix the issue.

Same here, running into this issue.

If you hit the problem and want temporary relief, you can use my temporary re-release at https://pypi.org/project/isaacto-html-table-extractor/ .

Thank you for raising the issue :)
I just released the new version 1.4.1.

Thank you!
On Fri, May 1, 2020 at 12:02 AM Justin Li<EMAIL_ADDRESS>wrote:

Closed #20 https://github.com/yuanxu-li/html-table-extractor/issues/20.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/yuanxu-li/html-table-extractor/issues/20#event-3292418936,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABXYSNIZTOMC7IY6LV6MN3DRPJXW3ANCNFSM4JQNNBDQ
.


Radio Imaging App Stopped working in the middle of audio generation

Hello,  Love the app on radio imaging, but unfortunaty is stopped working in the middle of audio generation and I was not able to get back on the page because it had a message saying I needed to contact support.  I had put my API key in already.  Can we get this back up and running again?  Its a great tool. thanks

Thank you for your message. I'm glad to hear you liked our deployment. Yes, it is now up and running.

Awesome. thank you.  I would be interested in buying you lots of coffee to
build my own for me.  ha ha
On Mon, Apr 15, 2024 at 7:02 PM Bilel Aroua @.***>
wrote:

Thank you for your message. I'm glad to hear you liked our deployment.
Yes, it is now up and running.
—
Reply to this email directly, view it on GitHub
https://github.com/bilsimaging/Radio-Imaging-Audio-Generator/issues/1#issuecomment-2058007887,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGRNC3NGZZ7JGR5YC4ZGU7TY5RTB3AVCNFSM6AAAAABGIHKTV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJYGAYDOOBYG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Adam Taylor
(903)-641-1835

I would greatly appreciate your support! If you'd like to buy me a coffee, you can do so through my Ko-fi page: https://ko-fi.com/bilsimaging.

I will do that for sure.  I was able to start again but then
received this error message.  Let me know what your thoughts are.  Dont
feel pressure from me.  I will be the easiest customer ever.  You can
always beta test things on me without any complaints.  Technology breaks
sometimes.  here is the screenshot of what just happened now.
On Mon, Apr 15, 2024 at 7:06 PM Bilel Aroua @.***>
wrote:

I would greatly appreciate your support! If you'd like to buy me a coffee,
you can do so through my Ko-fi page: https://ko-fi.com/bilsimaging.
—
Reply to this email directly, view it on GitHub
https://github.com/bilsimaging/Radio-Imaging-Audio-Generator/issues/1#issuecomment-2058011554,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGRNC3LDGVULTBCLC3IFPFDY5RTRVAVCNFSM6AAAAABGIHKTV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJYGAYTCNJVGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Adam Taylor
(903)-641-1835

Due to resource limitations on Streamlit, the app might occasionally be down. You can clone our GitHub repository and run the app locally on your machine to ensure continuous access.
feel free to contact me if you need any help
thank you adam

Sounds good. How much would you charge me to do that (if you interested).

Adam Taylor
(903)-641-1835
On Mon, Apr 15, 2024 at 7:28 PM Bilel Aroua @.***>
wrote:

Due to resource limitations on Streamlit, the app might occasionally be
down. You can clone our GitHub repository and run the app locally on your
machine to ensure continuous access.
feel free to contact me if you need any help
thank you adam
—
Reply to this email directly, view it on GitHub
https://github.com/bilsimaging/Radio-Imaging-Audio-Generator/issues/1#issuecomment-2058028756,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGRNC3IUDDX4B5ZGBBQYTS3Y5RWBLAVCNFSM6AAAAABGIHKTV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJYGAZDQNZVGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Feel free to buy me a coffee through Ko-fi, and I'll be happy to help you set up the system on your local machine.
😉 thank you adam

just bought you some coffee. let me know what you need from me
On Mon, Apr 15, 2024 at 7:35 PM Bilel Aroua @.***>
wrote:

Feel free to buy me a coffee through Ko-fi, and I'll be happy to help you
set up the system on your local machine.
😉 thank you adam
—
Reply to this email directly, view it on GitHub
https://github.com/bilsimaging/Radio-Imaging-Audio-Generator/issues/1#issuecomment-2058034707,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGRNC3OC4ZVNJPPMVH7LHHTY5RW4LAVCNFSM6AAAAABGIHKTV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJYGAZTINZQG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Adam Taylor
(903)-641-1835

That was great.❤🔥 I am grateful. do you have discord ?
add me, please My username is "bilsimaging."

No problem   Great resource   I don’t have discord yet. Is there another
way?
Adam Taylor
(903)-641-1835
On Mon, Apr 15, 2024 at 7:50 PM Bilel Aroua @.***>
wrote:

That was great.❤🔥 I am grateful. do you have discord ?
add me, please My username is "bilsimaging."
—
Reply to this email directly, view it on GitHub
https://github.com/bilsimaging/Radio-Imaging-Audio-Generator/issues/1#issuecomment-2058045795,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGRNC3KF3WF237JNG2QW573Y5RYUXAVCNFSM6AAAAABGIHKTV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJYGA2DKNZZGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

either your email or whatsapp number, please?

check plz your email


invalid "Duplicate key" error thrown

Here's a simplified test case:
$tmp: (
  in an alert: alert,
  within a toolbar: toolbar
);

And the failure:
/Users/eoneill/workspace/node-sass-test/node_modules/node-sass/lib/index.js:409
  throw util._extend(new Error(), JSON.parse(result.error));
             ^
Error: Duplicate key "within a toolbar" in map (in an alert: toolbar).

This appears to work correctly in libsass (@3.2.5) and in ruby sass (@3.4.14)

which version of node-sass?

Using<EMAIL_ADDRESS>

Thanks. On my shiny development version I cannot reproduce this at the moment.

Node Sass versions are couple to libsass versions. If it works in LibSass 3.2.5 it works in<EMAIL_ADDRESS>It's likely you have grunt/gulp-sass installed and it's using an older version of node-sass.

I created a repo that reproduces consistently (for me).
https://github.com/eoneill/node-sass-issue-1072
I'm using node-sass directly, nothing else.
I tried using .render() vs .renderSync() as well as passing data vs file and each case fails.
I can reproduced across different machines so let me know if you still can't repro. I can try to narrow down more specifics.

I think my problems with reproducing it is good news: it git fixed in the meantime:) need to figure out why

@eoneill thanks heaps for your effort. This is a known issue with LibSass 3.2.5. I was initially mislead by the claim that it was not an issue in LibSass. This has been fixed in LibSass and will hopefully be resolved soon.
Error: Duplicate key "within a toolbar" in map (in an alert: toolbar).
        on line 17 of test.scss
>> $tmp: ( in an alert: alert, within a toolbar: toolbar );

I was able to confirm that pointing my package.json to node-sass HEAD fixed the issue, so it looks like the next release should resolve this.
Apologies for the inaccurate info re: working in libsass 3.2.5. I had test via codepen.io / sassmeister.com which claimed to be using 3.2.5, but should have verified locally.
Feel free to close this ticket per your workflow as the issue seems to already be resolved, just not released.
Thanks again!

Fixed in https://github.com/sass/node-sass/pull/1214. Will be in v3.4.0.


How do I get sftp setup and working?

I am completely unable to post on community support page as the Category selection dropdown is completely empty with NO options.
As such it won't let me post without a category.
Now for my actuall support request...
How do I get sftp setup and working?
I followed the instructions but it's just slow and I get disconnected because of a timeout in filezilla.
And this is my ssh log.
https://hastebin.com/korebugono.cs
I don't know how to remotely upload the sshd config if you needed it.
CentOS 7.? (I don't know exactly what's after the ?"
I changed the "Subsystem sftp" entry to "Subsystem sftp internal-sftp", and set usepam to no,
as was suggested by others in other posts experiancing the same time-out can't log into sftp issue.
But I have yet to actually find a fix for this issue.

We do not use the sshd service anymore, use port 5657 for SFTP.


[SPARK-11019][streaming][flume] Gracefully shutdown Flume receiver th…

…reads.
Wait for a minute for the receiver threads to shutdown before interrupting them.

Merged build triggered.

Merged build started.

Test build #43444 has started for   PR 9041 at commit dba200f.

/cc @tdas

Test build #43444 has finished for   PR 9041 at commit dba200f.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43444/
Test FAILed.

Merged build finished. Test FAILed.

Why is this needed?

This basically makes testing a bit more predictable. Sometimes, we end up hitting a situation where the last transaction is still not completed and the remaining data just stays stuck in Flume.
Also, it removes some unneeded InterruptedException from the logs

Jenkins, test this please

Gotcha. How long generally does it take to shutdown? I mean, how long typically will the awaitTermination wait?

Merged build triggered.

Merged build started.

In most cases, less than 5-10 seconds - just for the last in-flight batch to be done. This is not going to slow our unit test runs down. I mostly hit it in our internal end-to-end tests

Test build #43452 has started for   PR 9041 at commit dba200f.

LGTM. I'd rephrase the description to say "up to a minute" since I was a little scared when reading the original one. "OMG all my apps are going to wait a minute before exiting!"

Merged build triggered.

Merged build started.

Test build #43454 has started for   PR 9041 at commit 6a5be5e.

Test build #43452 has finished for   PR 9041 at commit dba200f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43452/
Test PASSed.

LGTM. Merging it master and branch 1.5

Actually, there were small conflicts in branch 1.5, so I only merged to master. Seems fine, not a highpriority bug that 1.5 should get it.

Test build #43454 has finished for   PR 9041 at commit 6a5be5e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43454/
Test PASSed.


Instructions to run inference on custom data

Hi, thanks for your work! Can you specify how I can run inference with your pretrained models on some custom RGBD data that I have?

Any idea how to do this?