git stderr: Permission denied (publickey)

What does this error mean and how can i fix it
$ cap production deploy
00:00 git:wrapper
01 mkdir -p /tmp
✔ 01<EMAIL_ADDRESS>2.883s
✔ 01<EMAIL_ADDRESS>2.903s
✔ 01<EMAIL_ADDRESS>2.955s
Uploading /tmp/git-ssh--production-imdad.sh 100.0%
Uploading /tmp/git-ssh--production-imdad.sh 100.0%
Uploading /tmp/git-ssh--production-imdad.sh 100.0%
02 chmod 700 /tmp/git-ssh--production-imdad.sh
✔ 02<EMAIL_ADDRESS>0.392s
✔ 02<EMAIL_ADDRESS>0.388s
✔ 02<EMAIL_ADDRESS>0.414s
00:07 git:check
01 git ls-remote git@github.com:youtoo-inc/unicircles.git HEAD
01 Permission denied (publickey).
01 fatal: Could not read from remote repository.
01
01 Please make sure you have the correct access rights
01 and the repository exists.
01 724449f266dec2c4d23b4611fcf0093600d849e2	HEAD
✔ 01<EMAIL_ADDRESS>1.934s
01 724449f266dec2c4d23b4611fcf0093600d849e2	HEAD
✔ 01<EMAIL_ADDRESS>2.001s
(Backtrace restricted to imported tasks)
cap aborted!
SSHKit::Runner::ExecuteError: Exception while executing as<EMAIL_ADDRESS>git exit status: 128
git stdout: Nothing written
git stderr: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Caused by:
SSHKit::Command::Failed: git exit status: 128
git stdout: Nothing written
git stderr: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Tasks: TOP => deploy:check => git:check
(See full trace by running task with --trace)
The deploy has failed with an error: Exception while executing as<EMAIL_ADDRESS>git exit status: 128
git stdout: Nothing written
git stderr: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
** DEPLOY FAILED
** Refer to log/capistrano.log for details. Here are the last 20 lines:
INFO [c8d06c66] Running /usr/bin/env chmod 700 /tmp/git-ssh--production-imdad.sh as<EMAIL_ADDRESS>DEBUG [c8d06c66] Command: ( export RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.2.2" ; /usr/bin/env chmod 700 /tmp/git-ssh--production-imdad.sh )
INFO [c00e8a00] Finished in 0.392 seconds with exit status 0 (successful).
INFO [3382f9e2] Finished in 0.388 seconds with exit status 0 (successful).
INFO [c8d06c66] Finished in 0.414 seconds with exit status 0 (successful).
INFO [8331e4e8] Running /usr/bin/env git ls-remote git@github.com:youtoo-inc/unicircles.git HEAD as<EMAIL_ADDRESS>DEBUG [8331e4e8] Command: ( export RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.2.2" GIT_ASKPASS="/bin/echo" GIT_SSH="/tmp/git-ssh--production-imdad.sh" ; /usr/bin/env git ls-remote git@github.com:youtoo-inc/unicircles.git HEAD )
INFO [9cc0ffec] Running /usr/bin/env git ls-remote git@github.com:youtoo-inc/unicircles.git HEAD as<EMAIL_ADDRESS>DEBUG [9cc0ffec] Command: ( export RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.2.2" GIT_ASKPASS="/bin/echo" GIT_SSH="/tmp/git-ssh--production-imdad.sh" ; /usr/bin/env git ls-remote git@github.com:youtoo-inc/unicircles.git HEAD )
INFO [cf8dfef8] Running /usr/bin/env git ls-remote git@github.com:youtoo-inc/unicircles.git HEAD as<EMAIL_ADDRESS>DEBUG [cf8dfef8] Command: ( export RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.2.2" GIT_ASKPASS="/bin/echo" GIT_SSH="/tmp/git-ssh--production-imdad.sh" ; /usr/bin/env git ls-remote git@github.com:youtoo-inc/unicircles.git HEAD )
DEBUG [9cc0ffec] 	Permission denied (publickey).
DEBUG [9cc0ffec] 	fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
DEBUG [8331e4e8] 	724449f266dec2c4d23b4611fcf0093600d849e2	HEAD
INFO [8331e4e8] Finished in 1.934 seconds with exit status 0 (successful).
DEBUG [cf8dfef8] 	724449f266dec2c4d23b4611fcf0093600d849e2	HEAD
INFO [cf8dfef8] Finished in 2.001 seconds with exit status 0 (successful).

Please read the issue template before deleting it and asking in the wrong forum. We provide some limited support on StackOverflow.com for configuration issues such as this.


Image Styles - Regular, wide and full.

First off, great theme! I'm just starting out with my blog and I'll be using this for sure!
I've just been trialling some things and comparing them to the Casper theme (and maybe others?).
When setting an image to be 'wide', the image shows slightly wider in the editor but when I view the image, the image seems to have the behaviour of a 'full' width image.
See https://duncanbain.io/blog/test-post/
Is this intended behaviour? I would have thought setting 'wide' would have the image slightly larger than the content area, as with Casper. But not full width like 'full'.

@duncanjbain Thank you for considering using Fizzy Theme.
The problem you mentioned is a bug, I will fix that soon.
The problem is caused because I have only tested to embed images from Unsplash which the image is automatically cropped with 1080px wide. But apparently uploaded images won't be cropped.
Thank you for posting this bug!

Great! I had a quick look at implementing it, but I see you've already pushed a fix :)

Yep, I had a quick fix with that, but feel free to implement a better or elegant way to do that and post a PR.
Cheers.


Align IlpOverHttp Settings with CustomProperties

In the current implementation, it's possible that an IlpOverHttpLinkSettings object will have differing values in its map of custom settings as compared to the Java code. For example, a test-case might load an instance of IlpOverHttpLinkSettings by calling IlpOverHttpLinkSettings.fromCustomSettings but then manually set the value of the auth-subject, for example.
We should tighten this up, perhaps in the Immutable, such that an instance of IlpOverHttpLinkSettings that has values set in Java uses those instead of any divergent value in the CustomSettings Map.
This gets weird though when the two values differ -- which one should take precedence? If we say Java always takes precendence, then what if Java is unset, but the Map is set. Perhaps we should look into the Immutables normalization method here to work this out.

Another thing that shouldn't be possible this is:
IncomingLinkSettings.builder()
            .authType(IlpOverHttpLinkSettings.AuthType.SIMPLE)
            .tokenIssuer(HttpUrl.parse("https://incoming-issuer.example.com"))
            .tokenAudience(HttpUrl.parse("https://incoming-audience.example.com/"))
            .encryptedTokenSharedSecret(SHH)
            .minMessageWindow(Duration.ofMillis(30))
            .build();

 assertThat(incomingLinksettings.tokenIssuer().get())
        .isEqualTo(HttpUrl.parse("https://incoming-issuer.example.com/"));
    assertThat(incomingLinksettings.tokenAudience().get())
        .isEqualTo(HttpUrl.parse("https://incoming-audience.example.com/"));

There should maybe be a normalization check in the Immutable to prevent this from happening.

@nhartner can you add examples of our new custom-property scheme for the simple & JWT auth properties?

New property scheme:
Simple:
"ilpOverHttp.incoming.simple.auth_token": "password",
"ilpOverHttp.outgoing.simple.auth_token": "password",
"ilpOverHttp.outgoing.url": "http://java1.connector.com/accounts/foo/ilp"

JWT HS256
    "ilpOverHttp.incoming.jwt.shared_secret": "adsfasdfads",
    "ilpOverHttp.incoming.jwt.subject": "foo@me",
    "ilpOverHttp.outgoing.jwt.shared_secret": "adsfasdfads",
    "ilpOverHttp.outgoing.jwt.subject": "foo@them",
    "ilpOverHttp.outgoing.jwt.expiryDuration": "100s" ???
    "ilpOverHttp.outgoing.url": "http://java1.connector.com/accounts/foo/ilp"

JWT RS256
    "ilpOverHttp.incoming.jwt.issuer": "http://them.example.com",
    "ilpOverHttp.incoming.jwt.jwks_url": "http://them.example.com/.well-known/jwks",
    "ilpOverHttp.incoming.jwt.audience": "https://me.example.com",
    "ilpOverHttp.incoming.jwt.subject": "foo@me",
    "ilpOverHttp.outgoing.jwt.issuer": "http://me.example.com",
    "ilpOverHttp.outgoing.jwt.audience": "https://me.example.com",
    "ilpOverHttp.outgoing.jwt.subject": "foo@me",
    "ilpOverHttp.outgoing.jwt.expiryDuration": "100s" ???
    "ilpOverHttp.outgoing.url": "http://java1.connector.com/accounts/foo/ilp"

@nhartner This is complete now since #408 was merged? If so let's close it.

After speaking more with @nhartner, we think the best solution here is to decouple the API object (e.g., the thing with customSettings) from the internal business object, which is strongly typed and has no customSettings map). This will avoid any ambiguity in code.
As background, there generally shouldn't be a case where a LinkSettings object is being created by a developer who is setting both customSettings and setting Java properties in the immutables builder directly. The reason being is that customSettings really only exists to placate the REST API, whereas we expect a Java developer constructing links to not use custom settings.
This falls down in two places. The first is the ITs, many of which were written in a "customeSettings" world, so we see examples where ITs construct Links using both customSettings and overt Java builder calls.
The second place this falls down is in the LinkFactory, where it accepts a LinkSettings object, and then overrides any build properties with custom settings.
To make it clearer for everyone, we can have two objects - one for the REST API, and one for the internal business logic, that more clearly defines what's involved and allowed for each object.


Location Icon associated with an observation should change based on geoprivacy across the app

[ ] Update the location pin icon's state to change depending on the observation's geoprivacy on every screen associated with that observation, including home screen/my observations, explore, and obs detail
[ ] Ensure that the location section on obs detail as well as the location detail (map view) display properly based on geoprivacy and location permissions - there are designs for all states of the map view.

Location Pin Updates: 3 states based on Geoprivacy
Right now, every observation has a location pin and a location associated with it. This shows up on the observations list, as well as on obsdetail under the photo at the very top. I would like for this location pin to change based on the geoprivacy of the observation.
Here's an example of viewing 3 observations in my observations with open, obscured, and private geoprivacy. I can see the locations because they are my observations.

Here's an example of viewing other peoples' observations in explore: I can't see the location details because I don't have permissions to see the location, and I can see the pin change based on geoprivacy

These location pin designs should appear everywhere that location pin appears in conjunction with an observation: My observations, explore (observations view), observation detail, location section on observation detail, and the map view on observation detail.
Text and view of location section on obs detail and Map view
Please reference these designs to see examples of every type of view for the obs detail page depending on geoprivacy, whether it is the user's observation, and whether they have permission to view the observation's location.

FWIW, I think Angie implemented this as specified... but I don't think it was specified correctly. What we want to communicate is whether the coordinates are obscured, not what the user's geoprivacy choice was. I want to be sure that the coordinates of the threatened species I saw are obscured, whether they're obscured because I said they should be OR if the taxon has a conservation status.

I don't think I understand exactly what you'd like to be different. Do you want more explicit text explaining "This organism has a sensitive status, and its location is obscured. You can always see the location of your own observations." when you observe a threatened species?


no gene in target_of section for GO

Sorry about that.  I've just fixed it and I'm re-releasing the site now.


Undo of damage to actor with initially negative HP

Foundry Virtual Tabletop version 0.8.8
System: 3.5 SRD version 0.94.5
Damage Log version 1.1.0
So here's a situation. Actor has -14 HP initially. I apply 1 dmg, taking it down to -15 HP. Then undo that damage using right-click on Damage Log entry. The actor now has 0 HP. Here's a screenshot that I believe captures the situation:

I am unfamiliar with D&D 3.5.  What does negative HP mean?
Anyway, Damage Log currently prevents you reducing HP past zero.  Should be easy enough to fix.

Negative HP in 3.5e is not really different from positive HP. In 3.5e there is a negative HP threshold at which things actually die. There's no "Death Saving Throws" in 3.5e. Anyways... In my imagination, undoing damage should be agnostic to this right? It should just go back to the previous HP value if I undo the damage.

I've been playing with the D&D v3.5 system, and I noticed that it is actually possible to reduce the HP of an actor below its minimum value.  E.g. the min HP for an Ape is -100, but you can reduce it to e.g. -200 if you wanted to.  I think this is a bug in the 3.5 system, but am happy to be corrected, because as I said, I don't know anything about v3.5.
Damage Log will try to cap values to the min and max values when reverting/redoing damage.  Should I continue to cap to the minimum value for 3.5?  Or should I allow it to go below that?

Looks to be the same in PF1 as well.

537c441831760292ec961c58fa1ca855b61ed2e4

Fixed in v1.2.0


BOXFolderViewController hidden search bar

Hi.
Having a gap between navigation bar and top cell in BOXFolderViewController. Search bar is placed there as table view header but it's being hidden and never brought back to visible.
This line from setupForSearch method hides it:
self.searchController.searchBar.hidden = YES; // Starts of hidden, and only when we've fetched items do we bring it in.
I think it should set to visible somewhere in fetchItems completion block. Or do I miss something?
Thanks.

Thank you very much. The CR is pending:
https://github.com/box/box-ios-browse-sdk/pull/61
Please let me know if this addresses your issue.

@jdizoglio, yes, it's related to my issue. But, as far as I see, It doesn't fix it. In code search bar still not being revealed (at least the gap is gone). self.searchController.searchBar.hidden never set to NO. There is a check in new code:
if (self.searchController.searchBar.hidden) {
    self.tableView.tableHeaderView = nil;
} else {
    self.tableView.tableHeaderView = self.searchController.searchBar;
}

So the else case will not be fired and search bar will still be hidden.
Under this scenario, I guess self.searchController.searchBar.hidden should be set to NO in callback when items count > 0
Currently I have folderViewControllerShouldShowSearchBar delegate method which always returns true, but search bar is not displayed.

@RafaelKayumov. I misunderstood the folder class use. The correction is in the latest commit. Thank you for being patient and for reviewing the code!!!
https://github.com/box/box-ios-browse-sdk/pull/64

@jdizoglio, looks fixed now. Thanks.


Milestone2 Theme added

Live Version http://translator-albert-75345.bitballoon.com/#/speakers

@juslee , You can merge it .

There is a minor font issue
downloadable font: download failed (font-family: "Glyphicons Halflings" style:normal weight:normal stretch:normal src index:1): bad URI or cross-site access not allowed source: http://d33wubrfki0l68.cloudfront.net/css/e9f8121ff973fe1b1a0f032d6118e2c7f463b4cc/fonts/glyphicons-halflings-regular.woff2

@aayusharora also any idea why the session are not showing up ?

@championswimmer  , locally its working correct , font is failing saying the Cross domain request . I will do it .

Cool. merging this


Update Grafana to latest version to fix CVE-2024-8986

Image builder highlights:
github.com/grafana/grafana-plugin-sdk-go | CVE-2024-8986 | 0.250.0 | CRITICAL
By bumping this image fixes this error.

I think you are missing container tags
Also, needs a reno


Branch stable/0.14 is failing

Trying to build stable/0.14 at commit 99f97b00269624b57203685437fb951af4b4e103 failed.
More info at: https://travis-ci.com/Qiskit/qiskit-terra/jobs/334531236

Moved to https://github.com/Qiskit/qiskit-ibmq-provider/issues/673


Issue when viewing pages on a portrait mode monitor.

Where is the problem?
When I look at this page - https://docs.konghq.com/konnect-platform/plans/#plan-comparison on my portrait monitor I see the following embedded markup(?)

But on my laptop monitor in landscape mode it appears as expected?
What is your suggestion?
Not sure what tools are being used, but suggest, if not already doing so, testing on both landscape and portrait mode monitors?
Code of Conduct and Community Expectations

[X] I agree to follow this project's Code of Conduct
[X] I agree to abide by the Community Expectations

@rkazak can you refresh the page and see if it still happens?

We have removed this page, as it is a duplicate of https://konghq.com/pricing/.
I couldn't reproduce the issue either with mobile or by resizing pages. If you run into it again on another page, please open another issue.


New feature: Set a custom replacement palette via Game Boy Color

Hello!
Thanks for considering my pull request. I have done this because it seemed like a popular feature request in the community Discord.
What is the new behavior (if this is a feature change)?
This change allows users to set their own 4 custom 15-bit colors to replace the standard Game Boy colors in both ROM and web deployments. In the World settings panel, users can select the color in the palette, then either type in the 0-31 RGB values or paste in an HTML Hex color code to see the color update in real-time.
The ROMs generated by this change have been tested on many different types of hardware by community member Veund. It was found that the custom colors worked on everything that supports Gameboy Color (including the GBA Player for the Gamecube).
I have noticed that the colors output by the emulators are a little washed out compared to the preview colors I generate in GB Studio. It could be a colorspace issue (I'm currently just multiplying by 8 to expand from 0-31 to 0-255) but I'll need to do more testing to see if there's a problem there.
In the future, it would be nice to also add support for Super Game Boy custom palettes. As it stands, GBDK doesn't provide the necessary functions for sending the palettes and I currently don't have enough experience with assembly to add the needed functions.
Does this PR introduce a breaking change?
Using an existing project file or creating a new one should both function. I have only tested using the English localization file so it's possible that using a different language may break things.
Other information
I was hoping to also add to the documentation but it appears that it does not reside on this repository.
Additionally, no tests have been added either.
Special thanks to community Discord members:

Dramakins for initial inspiration
rulz for assistance in developing the Game Boy ROM changes
Veund for feedback and extensive hardware testing
personitis, Darkhog, Kenney, Kazy, and TOXWORKS for feedback during UI development

Hi @fydo Thanks for this pull request, sorry it took a while to get back to you on this one, I've been busy refactoring almost the entire frontend and event system which I've just merged into develop.
I'm going to clone your repo and have a full look through your implementation, and do some testing before I can merge this.
Luckily you completely avoided merge conflicts with my changes so that makes it a bit easier!
I'm thinking of putting features like this and probably things like the Cartridge Type under an "Advanced Settings" section where I've got a few other ideas (custom keyboard controls, inject CSS/JS into the head of the web player) eventually but I think leaving it where you have it is fine for now. I'll try to get back to you soon.

Hey there! Thanks for the response. No worries on taking your time, I'm certainly not in any kind of hurry. :) I think I can speak for the community when I say that we really appreciate the time and care that you put into GB Studio. Please let me know if you require me to make any changes to my commits thus far.
Also, sorry about the Softagram spam. I was playing around with it and I didn't expect it to post a comment in here.

Hi @fydo Thanks for your work on this, I really appreciate you helping out on this highly requested feature.
I've had a little time to do some testing, I think there might be a few issues on your implementation though. Some of colours aren't coming through correctly when the ROM is being built.
e.g. See this one where blue has become a darker green and orange has become red in the build.

Also I noticed when reloading that file the blue had changed to the green (but strangely the orange wasn't red)

I've attached the project so you can see
UntitledDX.zip
I think the blue become green is because of a bug around here
https://github.com/fydo/gb-studio/blob/e62466458a06b2f3a2fce145b1a6b6848f2cd776/src/components/forms/CustomPalettePicker.js#L128-L155
You store changes with this.setState() then call this.saveToSettings(); straight afterwards that reads the state using this.state. which isn't guaranteed to work as this.setState is asynchronous.
One thing you could do is use the callback argument on setState (see https://medium.learnreact.com/setstate-takes-a-callback-1f71ad5d2296)
I think adding the saveToSettings call to the callback on the four setState calls might be enough to fix this.
      this.setState({whiteHex:  this.decimalToHexString(r * 8) +
                                this.decimalToHexString(g * 8) +
                                this.decimalToHexString(b * 8)}, this.saveToSettings);

I'm not sure why the orange becomes red though, the colour seems to being stored correctly in the .gbsproj file as "CustomColors_White": "F0A800", but for some reason this hex comes through as red.
Here's a few more tests I did with similar issues:

I'm using macOS if it makes a difference.

Hello! Thanks for the great feedback. You were absolutely right with regards to the issue being React's state change being async. What was happening in your first screenshot is that you typed in 2,25,30 but since the most recent event wasn't getting applied to the state you ended up with a color that was 2,25,3.
I just checked in a fix that appears to solve this issue.

Just to follow up on my "washed out colors" comment. I found some information here: http://emulation.gametechwiki.com/index.php/Game_Boy/Game_Boy_Color_emulators#Oversaturation
It seems that GBC emulators will attempt to emulate the under-saturation of the GBC screen. I don't know if this is something we want to account for but I am personally happy with how the implementation is at the moment.

@fydo yeah I think we can leave the colours as is for the moment but thanks for investigating.
Just to let you know I've just pushed a build that moves this feature into a Settings section now (I've not deleted it! :D)

Haha, thanks for the heads up!


Serialization broken with double? type

_DefaultValueSerializer code:
    if (_typeList is List<double> && json is int) {
      return json.toDouble() as T;
    }

This doesn't catch List<double?> and thus double? columns, like RealColumn? get myColumn => real().nullable()();
This exception will be thrown on generated code serializer.fromJson<double?>(json['my_column']) when json['my_column'] is an int:
_CastError (type 'int' is not a subtype of type 'double?' in type cast)
I believe the fix is:
    if (_typeList is List<double?> && json is int) {
      return json.toDouble() as T;
    }

Thanks for the report, I've fixed this on develop.


How to visualize the train porcess

like this

You could use tensorboardx to visualize traning log. Training script will automatically save training log.


Undefined index 'required' when using sanitize_callback as function

Kirki 4.0.20

I have this:
'active_callback' => function() {
	return true;
},

and get the above error.
There's 2 issues that I see (only looking briefly):

Needs an isset( $field['required'] ) here:

There is only a check for is_array( $field['active_callback'] ). It needs to check if callable somewhere in there too, right?

Fixed. Will go live with the next update. Thanks for reporting! :) @JiveDig

I added the fix manually test and all good here 👍. Thanks :)


Sampler2D.SampleCmp() has confusing parameters

First, let me say thank you for addressing my previous issue re: SV_ViewID so quickly.
Now, I am trying to do hardware PCF for my shadows by utilizing the SampleCmp method of Sampler2DArray, but for that and even for Sampler2D's the first parameter is a SamplerComparisonState. All state referenced by that structure is defined in the combined image sampler itself, so I don't understand why this struct needs to be passed.
Is this just one of the things that's incomplete regarding Sampler types in slang or am I missing something?
Thank you.

That definitely sounds like a bug (or missing feature) in our implementation of SampleCmp in the Slang standard library. Our support for combined texture image/sampler pairs has not yet been put into heavy use in the field, since most of our current users/customers write code that uses separate textures and samplers.
If anybody in the community wants to dive in and help to fix these issues in the context of a codebase that needs combined texture image/sampler pairs, we would appreciate those contributions. I would be happy to set aside time to help get somebody oriented in the codebase in order to help them get started.

So I know next to nothing about spirv compilers, but my intuition makes me think that this shouldn't be so hard to implement considering it's the same work as Texture2D.SampleCmp() except some of the data comes from "inside the sampler"
I forked the repo and can build all projects but one through VS. My email is in my profile if you want to reach out and point me in the right direction.

core.meta.slang:1590 is where we need to fix. Add a if(prefixInfo.combined) there and define the function differently for SamplerXXX.SampleCmp

I'm working on this now. I see the following error when I try to compile, but a slangc.exe is generated no matter what so I wonder if it even matters:
Error	MSB3073	The command "IF EXIST ......\external\slang-llvm\bin\windows-x64\release\slang-llvm.dll\ (xcopy /Q /E /Y /I ......\external\slang-llvm\bin\windows-x64\release\slang-llvm.dll ......\bin\windows-x64\release > nul) ELSE (xcopy /Q /Y /I ......\external\slang-llvm\bin\windows-x64\release\slang-llvm.dll ......\bin\windows-x64\release > nul)
IF EXIST ......\external\slang-glslang\bin\windows-x64\release\slang-glslang.dll\ (xcopy /Q /E /Y /I ......\external\slang-glslang\bin\windows-x64\release\slang-glslang.dll ......\bin\windows-x64\release > nul) ELSE (xcopy /Q /Y /I ......\external\slang-glslang\bin\windows-x64\release\slang-glslang.dll ......\bin\windows-x64\release > nul)
:VCEnd" exited with code 4.	slang	C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Msbuild\Microsoft\VC\v160\Microsoft.CppCommon.targets	155

You need to run .\premake.bat vs2019 --deps=true to pull prebuilt llvm binaries.

Thank you. Not sure how I skipped over that paragraph of the instructions.
I put this in the relevant places:
sb << "float SampleCmp(";
if (!prefixInfo.combined)
    sb << "SamplerComparisonState s, ";

but it doesn't appear to do anything. I still see the typical
no overload for 'SampleCmp' applicable to arguments of type (vector<float,3>, float)
when I try building my own code.
I will continue trying things.

This is now fixed.


OTLP exporters description in the registry is not accurate

What needs to be changed?
I noticed that the description used in the OTLP exporter entries (e.g. the Java one) in the registry is not accurate. It says:

This library allows to export data to the OpenTelemetry Collector using the OpenTelemetry Protocol.

It's not accurate because OTLP exporters also allow sending data to other places outside the collector (e.g., directly to an o11y back-end).
What is the name + path of the page that needs changed?
content/en/registry/exporter-{lang}-otlp
Additional context
I initially spotted and discussed it here https://github.com/open-telemetry/opentelemetry.io/pull/1792#discussion_r984521837
Suggestion:
@svrnm suggested in the PR above to use something like:

This library allows to export telemetry data in the OpenTelemetry Protocol (OTLP) format to the OpenTelemetry Collector and OTLP-compliant backends/receivers

@cartermp, thoughts on how this should be phrased?
@joaopgrassi would you be open to fix that for all the OTLP exporters?

@svrnm yes, I can send a PR to fix all the others, once we agree on the sentence.

@joaopgrassi thanks!
@chalin , @cartermp I am also wondering if this would be something we could fix via a short code or other mechanisms? so have that repeated text stored away somewhere

Regarding this proposed sentence:

This library allows to export telemetry data in the OpenTelemetry Protocol (OTLP) format to the OpenTelemetry Collector and OTLP-compliant backends/receivers

I would propose something similar, just with one word change 🙂

This library allows exporting telemetry data in the OpenTelemetry Protocol (OTLP) format to the OpenTelemetry Collector and OTLP-compliant backends/receivers

I open a PR fixing all the registry entries in the upcoming day(s). Feel free to assign this to me if you want :)


Schema Migrator Revert

Description
Changes proposed in this pull request:

Type Correction

Related issue(s)

/hold

/unhold


[Relay][Pytorch] Add support for aten::swapaxes operator

Add support for  aten::swapaxes operator to support compiling the pytorch's  maxvit model.
cc @junrushao

@Hzfengsy Can you review the PR, please?

This looks nice! BTW do you guys want to retrigger the CI and get it green?

@junrushao
Thank you for your comment.
Can you retrigger the CI again?

Thanks @ducnhat-luong @mshr-h for the contribution!


Make UI compatible with JS & IOS

Use Compose experimental features to build the application for WASM and IOS.

JS compatibility with raw compose is unlikely any time soon as text boxes do not work with compose WASM.

May test IOS compatibility when compose multiplatform for IOS becomes better developed and JitPack can build for OSX


Error from plv8 handler is not catchable

Code
https://github.com/deep-foundation/deeplinks/blob/66e9e4f655994aaa1c630533d9afc15475990bf3/tests/sync-handlers.ts#L1241-L1268
Error
    ApolloError: Success! Handler is called

      at new ApolloError (node_modules/@apollo/client/errors/index.js:29:28)
      at node_modules/@apollo/client/core/QueryManager.js:96:47
      at both (node_modules/@apollo/client/utilities/observables/asyncMap.js:16:53)
      at node_modules/@apollo/client/utilities/observables/asyncMap.js:9:72
      at Object.then (node_modules/@apollo/client/utilities/observables/asyncMap.js:9:24)
      at Object.next (node_modules/@apollo/client/utilities/observables/asyncMap.js:17:49)
      at notifySubscription (node_modules/zen-observable/lib/Observable.js:135:18)
      at onNotify (node_modules/zen-observable/lib/Observable.js:179:3)
      at SubscriptionObserver.next (node_modules/zen-observable/lib/Observable.js:235:7)

Expected
Error is thrown from deep.insert therefore try-catch block catches it


Lint and refactor

In preparation for Earthranger integration, code must be linted and readme's updated.

Here are some of the things we want to achieve in this issue:

code passes flake8
code passes pylint
updating of README to reflect how things currently work
some possible renaming of modules (and maybe other identifiers)to reflect changes that have occurred in how the project is organized
some refactoring on how we use our AniML package in CougarVision
further updating of the README based on what we do in steps 4 and 5

The above are in pretty good order for how we should tackle them.  More specifically, I think we should start with the web_scraping.py module and work towards it passing flake8 and pylint and then start looking at other parts of the project.

We hadn't discussed this yet and are basically doing it but to state it outright, this issue is focused on "CougarGram" which is to say the camera trap part of CougarVision i.e. not the streaming IP camera part. So, that is fetch_and_alert.py and all the bits it depends on.  This also brings up the question of whether fetch_and_alert.py should itself be renamed to cougargram.py or some other name that we come up with instead.


Feature/watchlist component

watchlist works but there is work left:

included a red button to add bitcoin to the watchlist for testing purposes. remove button also works.
data is fetched from the API directly but it should probably come from the coins variable in home.js, I just couldn't make it work.
connecting it to the all coins table shouldn't be an issue once that PR is merged.
missing alert for when a coin is already watchlisted, for now just logged to console.

For your Watchlist table component I think you could use the same structure of the Coin Table component:
https://github.com/chingu-voyages/v43-tier2-team-13/blob/e3b23bd3c85444fc38ae9df3ac31d9d9a45579ec/src/pages/Home.js#L188
So it can be responsive like the coin table and also have the same layout.
Let me know what you think


📖 docs: generate list of carry commits for rebasing

Summary
This PR updates the rebase documentation to include a way generate a list of carry commits that need to be considered for rebasing.
This is heavily inspired from the openshift rebase process - https://github.com/openshift/kubernetes/blob/master/REBASE.openshift.md.

This is the list I generated for 1.27 - https://docs.google.com/spreadsheets/d/15k9sih-xBKICuLUHj4HMrqYf60mliaslImqqv6fGSJI/edit?usp=sharing
It mirrors what Andy had generated for the 1.26 rebase - https://github.com/kcp-dev/kcp/issues/2772
Related issue(s)
Related to #2986
Release Notes

NONE

/cc @xrstf @rajaskakodkar

/retest
tests look flaky, so maybe this will help.

/retest

/lgtm
/approve


Fix relative file loading

Fixes https://github.com/arkadiyt/aws_public_ips/issues/8

Pull Request Test Coverage Report for Build 48

6 of 6 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 46:
0.0%

Covered Lines:
318

Relevant Lines:
318

💛  - Coveralls


Mobile sidebar

Add MobileSidebar for screens bellow the sm size as part of #6318 (Mock ups in the RFC)
My goal with this PR is to improve the usability on mobile devices & at the same time keep the needed adjustments from the adopters side low. If people want to customise the mobile sidebar they can do this by using the added SidebarGroup component in their Root.tsx. The component is optional & all pages reachable through the Sidebar at the moment should still be reachable with the mobile sidebar by default. That said the PR can lead to unexpected UI changes & therefor the documentation was updated to easily adjust the Sidebar.
Changed Root.tsx configuration (Device: Pixel 2)

Menu
Search
Settings

Resize behaviour:

Light
Dark

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

There seems to be smth. flaky with the E2E tests - #6899 E2E is also failing because of prettier:check, but at the same time "CI / verify" is passing the prettier check.

Short demo of the submenu in the mobile sidebar
https://user-images.githubusercontent.com/8904624/145407714-27766b9c-b837-4620-94a0-b247fcacbfd5.mp4

WiP - conflicts to resolve

Thanks for the review & also asking more general question - I appreciate this a lot!

I think that the xs-Breakpoint easiest here, as it would have been required anyways (to prevent e.g. iPads from having a weird experience). Agree that we could additionally check for user-agent or use media queries to optimise it in the future.

This brings up another point: If we aim for enabling proper support for mobile devices the logic for "Is the current device mobile?" should probably be provided through some kind of ThemeProvider making it more clear & available to all components instead of hiding it in context related to the Sidebar.

Seems to work for me - do you maybe have a screenshot?:

https://user-images.githubusercontent.com/8904624/147666171-b9d85d27-1608-4307-b809-79adff0762b9.mp4

Think it should work now - increased the z-index

The MUI Drawer was a good point!! Using it now (see video above) & it immediately feels better to toggle the overlay. And yes - you definitely got a point with this & I thought about it, but I couldn't think of a better way to handle this. Open for suggestions here as well.

In your own gif, none of the entries in the "sidebar" are highlighted. If you open the sidebar, press home, and then open the sidebar again, is Home highlighted?

Yup :)
In the case above the "Settings" page is opened & therefor no item in the menu is highlighted. As soon as the overlay menu is closed the "Settings" icon in the bottom navigation is highlighted again.
Bellow an example when the user is on the "Home" page. Items should be highlighted exactly like in the current sidebar as I haven't change anything concerning the items.
https://user-images.githubusercontent.com/8904624/147672797-539cb168-384e-4e65-b19d-dff5d4fcb140.mp4


[BEAM-11196] Cherry-pick #13303 to the 2.26.0 release branch.

#13202 introduces a bug where the algorithm that determines the parents of fused stage can create loops, because the lowest common ancestor algorithm considers a transform to be its own parent. Fusing a single transform A will result cause the fused stage's parent to be set to A. Fusing a transform A with a descendant B will also cause fused stage's parent to be set to A. To fix this, if the parent of the fused stage would be one of transforms to be fused, set the parent to the parent of that transform instead.
This is a cherry pick of #13303.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @tvalentyn

LGTM

LGTM.


[BUG] Failed UT

What is the bug?
public/components/FeatureAnywhereContextMenu/AddAlertingMonitor/AddAlertingMonitor.test.js
● Test suite failed to run
Jest encountered an unexpected token

Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

By default "node_modules" folder is ignored by transformers.

Here's what you can do:
 • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
 • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
 • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
 • If you need a custom transformation specify a "transform" option in your config.
 • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

You'll find more details and examples of these config options in the docs:
https://jestjs.io/docs/configuration
For information about custom transformations, see:
https://jestjs.io/docs/code-transformation

Details:

/Users/ihailong/code/OpenSearch-Dashboards/node_modules/monaco-editor/esm/vs/editor/editor.api.js:5
import { EDITOR_DEFAULTS } from './common/config/editorOptions.js';
^^^^^^

SyntaxError: Cannot use import statement outside a module

  31 | /* eslint-disable @osd/eslint/module_migration */
  32 |
> 33 | import * as monaco from 'monaco-editor/esm/vs/editor/editor.api';
     | ^
  34 |
  35 | import 'monaco-editor/esm/vs/base/common/worker/simpleWorker';
  36 | import 'monaco-editor/esm/vs/base/worker/defaultWorkerFactory';

  at Runtime.createScriptFromCode (../../node_modules/jest-runtime/build/index.js:1728:14)
  at Object.<anonymous> (../../packages/osd-monaco/src/monaco.ts:33:1)
  at Object.<anonymous> (../../packages/osd-monaco/src/index.ts:31:1)
  at Object.<anonymous> (../../src/plugins/data/public/antlr/opensearch_sql/code_completion.ts:6:1)
  at Object.<anonymous> (../../src/plugins/data/public/plugin.ts:96:1)
  at Object.<anonymous> (../../src/plugins/data/public/index.ts:503:1)
  at Object.<anonymous> (../../src/plugins/saved_objects/public/saved_object/helpers/serialize_saved_object.ts:34:1)
  at Object.<anonymous> (../../src/plugins/saved_objects/public/saved_object/helpers/build_saved_object.ts:34:1)
  at Object.<anonymous> (../../src/plugins/saved_objects/public/saved_object/saved_object.ts:42:1)
  at Object.<anonymous> (../../src/plugins/saved_objects/public/saved_object/index.ts:31:1)

How can one reproduce the bug?
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

What is the expected behavior?
A clear and concise description of what you expected to happen.
What is your host/environment?

OS: [e.g. iOS]
Version [e.g. 22]
Plugins

Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.

closing this in favor of #1040


Document that Map.pick can throw KeyNotFoundException

@jlewicki,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

Whoops wrong branch

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/conceptual/collections.array-module-[fsharp].md
:warning:Warning

Details

docs/conceptual/collections.list-module-[fsharp].md
:warning:Warning

Details

docs/conceptual/collections.seq-module-[fsharp].md
:warning:Warning

Details

LICENSE
:white_check_mark:Succeeded

LICENSE-CODE
:white_check_mark:Succeeded

LICENSE.txt
:white_check_mark:Succeeded

README.md
:white_check_mark:Succeeded

ThirdPartyNotices
:white_check_mark:Succeeded

docs/conceptual/array.chunkbysize['t]-function-[fsharp].md
:white_check_mark:Succeeded

docs/conceptual/array.distinctby['t,'key]-function-[fsharp].md
:white_check_mark:Succeeded

docs/conceptual/array.exactlyone['t]-function-[fsharp].md
:white_check_mark:Succeeded

docs/conceptual/array.head['t]-function-[fsharp].md
:white_check_mark:Succeeded

docs/conceptual/list.distinctby['t,'key]-function-[fsharp].md
:white_check_mark:Succeeded

docs/conceptual/list.exactlyone['t]-function-[fsharp].md
:white_check_mark:Succeeded

docs/conceptual/list.truncate['t]-function-[fsharp].md
:white_check_mark:Succeeded

docs/conceptual/map.pick['key,'t,'u]-function-[fsharp].md
:white_check_mark:Succeeded

docs/conceptual/seq.chunkbysize['t]-function-[fsharp].md
:white_check_mark:Succeeded

docs/conceptual/snippets/fsarrays/snippet75.fs
:white_check_mark:Succeeded

docs/conceptual/snippets/fsarrays/snippet76.fs
:white_check_mark:Succeeded

docs/conceptual/snippets/fslists/snippet71.fs
:white_check_mark:Succeeded

docs/conceptual/snippets/fslists/snippet72.fs
:white_check_mark:Succeeded

docs/conceptual/snippets/fssequences/snippet66.fs
:white_check_mark:Succeeded

docs/conceptual/visual-fsharp-development-portal.md
:white_check_mark:Succeeded

docs/conceptual/collections.array-module-[fsharp].md

Line 41: [Warning] Invalid file link:(~/array.chunkBySize['t%5D-function-%5Bfsharp%5D.md).
Line 43: [Warning] Invalid file link:(~/array.comparewith['t%5D-function-%5Bfsharp%5D.md).
Line 45: [Warning] Invalid file link:(~/array.contains['t%5D-function-%5Bfsharp%5D.md).
Line 47: [Warning] Invalid file link:(~/array.countby['t,'key]-function-[fsharp].md).
Line 49: [Warning] Invalid file link:(~/array.distinct['t%5D-function-%5Bfsharp%5D.md).

docs/conceptual/collections.list-module-[fsharp].md

Line 42: [Warning] Invalid file link:(~/list.chunkBySize['t%5D-function-%5Bfsharp%5D.md).
Line 44: [Warning] Invalid file link:(~/list.comparewith['t%5D-function-%5Bfsharp%5D.md).
Line 46: [Warning] Invalid file link:(~/list.contains['t%5D-function-%5Bfsharp%5D.md).
Line 47: [Warning] Invalid file link:(~/list.countby['t,'key%5D-function-%5Bfsharp%5D.md).
Line 48: [Warning] Invalid file link:(~/list.distinct['t%5D-function-%5Bfsharp%5D.md).

docs/conceptual/collections.seq-module-[fsharp].md

Line 44: [Warning] Invalid file link:(~/seq.chunkBySize['t%5D-function-%5Bfsharp%5D.md).
Line 48: [Warning] Invalid file link:(~/seq.contains['t%5D-function-%5Bfsharp%5D.md).
Line 95: [Warning] Invalid file link:(~/seq.tail['t%5D-function-%5Bfsharp%5D.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


HP-1283 Default language set as FI

I agree. This should be resolved server side with existing Keycloak features.
Setting a cookie with javascript and reloading the page is a hack.
UI suddenly changes the language without user interaction.
User might lose inputted data when page is reloaded and reloading is slow.
Also the whole cookie should not be overwritten. All other cookies in the domain are lost.
document.cookie = "KEYCLOAK_LOCALE=fi";


v2.8.0 tag does not match checksum

If you are reporting a problem, please make sure the following information are provided:
Expected behavior and actual behavior:
$ src git:(main) go mod tidy
go: downloading github.com/docker/distribution v2.8.0+incompatible
verifying<EMAIL_ADDRESS>checksum mismatch
        downloaded: h1:u9vuu6qqG7nN9a735Noed0ahoUm30iipVRlhgh72N0M=
        go.sum:     h1:l9EaZDICImO1ngI+uTifW+ZYvvz7fKISBAKpg+MbWbY=

SECURITY ERROR
This download does NOT match an earlier download recorded in go.sum.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.

Steps to reproduce the problem:
Please provide the steps to reproduce this problem.
Versions:
Please specify the versions of following systems.

harbor operator version: [main]
harbor version: [x.y.z]
kubernetes version: [x.y.z]
Any additional relevant versions such as CertManager

Additional context:

Harbor dependent services:

Context info of postgreSQL
Context info of Redis
Context info of storage

Log files: Collect logs and attach them here if have.
Kubernetes: How Kubernetes access was provided (what cloud provider, service-account configuration, ...).

ref: https://github.com/distribution/distribution/issues/3590
ref: https://github.com/goharbor/harbor/issues/17295

/assign


[Feature request] Allow Pandas >= 2

Search before asking

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

Motivation
I ran into a situation where I was trying to install several libraries via pip that had pandas dependencies, and one of them required >= 2 on the pandas version.  While the requirements.txt in source control for the iotdb Python client doesn't indicate a restriction for not using pandas 2+, the metadata in the setup.py file restricts to less than v2.
Solution
If there isn't a functional reason for the limitation then I'd suggest removing the "<1.99.99" restriction.  Also the minimum required version should probably be updated to agree with what is in the requirements.txt file, which it currently doesn't.
Alternatives
No real alternative comes to mind.  Pandas v2 has been out for quite awhile now.
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Hi, I don't think we have such "<1.99.99" restriction for pandas.
https://github.com/apache/iotdb/blob/baf37c3711d907ed15cc7a99f8d9b16e7c7eceea/iotdb-client/client-py/requirements.txt#L20
Moreover, the python CI is using the latest pandas v2.2.2, and it works well.
https://github.com/apache/iotdb/actions/runs/9262251482/job/25478871454

Oh..okay, I know where the problem is...
https://github.com/apache/iotdb/blob/baf37c3711d907ed15cc7a99f8d9b16e7c7eceea/iotdb-client/client-py/resources/setup.py#L44

Awesome, ty!  I should have mentioned setup.py, apologies for that.  I had to hunt around a bit for it myself.   I was seeing the effect of the constraint from Jenkins build logs, but it took a little poking around before I could see the root problem.

Any problem of this PR? https://github.com/apache/iotdb/pull/12601 You can give an approval if there is no problem and then I'll merge it.

Commented on the PR, thumbs up.  I think you can close this now.


Fixed !roletip

Fixed !roletip
Just test it . my Discord account   ### chocolate#4014

nice catch, thanks!

It works ??

Yes, were you going to take a look at the private version?


Implement GHA CopyDocs

Let's implement the documentation GHA that will copy all release documentation to the open-horizon.github.io repo so that it gets added to the documentation web site.  In the process, we should determine if the README file is the only doc file, or if there will be multiple pages, they should all be collected in a new /docs folder in this repo and created using GitHub Pages flavored markdown syntax.
@blakep7 and @bencourliss will there be more than one page of documentation?

Fixed GHA error when pushing to origin.  Needed to update my personal access token that I used to connect to GitHub following these directions: https://github.com/orgs/community/discussions/26254#discussioncomment-6101339


optimize(Displayserver): performance up

Replace stdio with the posix api, and drop fscanf.
It shows a huge performance up in my local benchmarks.
About 35~40% faster per modefile than the old one.
Here is the highlights of benchmarks:
Running ./bench_linux_amd64
Run on (8 X 1800.01 MHz CPU s)
CPU Caches:
  L1 Data 32 KiB (x4)
  L1 Instruction 32 KiB (x4)
  L2 Unified 256 KiB (x4)
  L3 Unified 6144 KiB (x1)
Load Average: 0.12, 0.19, 0.16
-------------------------------------------------------
Benchmark             Time             CPU   Iterations
-------------------------------------------------------
BenchStdIO         1712 ns         1712 ns       341076
BenchPOSIXIO        998 ns          998 ns       655856

updates #634

Do you really think this PR can address any performance issues?
You are right that parsing string manually is always faster than fscanf, but why fscanf exists?
Come on! 1ms = 1000000ns. Several nanoseconds are not bottleneck, because it's executed only once. In addition, as for #634, this code is NOT executed unless --ds-force-drm is used.
Since @flipflop133 was using X11, the real bottleneck was the xrandr stuff. If you really want to improve fastfetch, please check that.

这个pr真是闲的蛋疼，好比是想让sleep

Don't get me wrong, I like performance improvements, and I'm accepting changes to improve performance at the cost of code complexity, but ONLY in common code.
Closing.

5x more lines of code and one more magic number are complexity.

it even costs twice as much in performance

1712ns -> 998ns can be called twice.
500 * 1000 * 1000ns + 1712ns -> 500 * 1000 * 1000ns + 998ns can't.


Pass in browser instance

This PR removes Puppeteer browser instantiation from jxl-pdf. Instead, an instance is passed in from the calling code. The three test configurations work as before.

LGTM


Features for v9.0.0

Given the PR sitting in TypeStyle: https://github.com/typestyle/typestyle/pull/245, I think it makes sense to setup a PR for CSX to see what it looks like to migrate types to csstype.
Since this is a major change, I think we should plan to go to v9.0.0.  So the question is, what other breaking changes should we put out at the same time?  What are your pain points with this lib or things that prevent us from extending features in natural ways?  We should avoid breaking code where possible, but if we need to alter the api, this is a good time to do it.
One of the things I think we should do is remove named colors.  It accounts for most of size of the bundle and I don't believe it provides a lot of utility.  The only one I think we should keep is transparent.
Reference (https://github.com/typestyle/csx/issues/35)

Tracking changes here: https://github.com/typestyle/csx/tree/next

[x] Remove named colors (for bundle size issue)
[ ] Switch to csstype

This has been merged


Error code: 10 - BadAccess

E1205 09:27:47.794860 12305 wm.cpp:372] Received X error:
    Request: 2    Error code: 10 - BadAccess (attempt to access private resource denied)
    Resource ID: 620

Forgot to say that the wm looks dope, congrats. I just wanna try it :grin:

Hello,

I usually bring up my wm by typing startx. But before that, you should put exec Wmderland at the end of ~/.xinitrc (also make sure there's only one exec statement, don't invoke other wm!)
Please re-clone this repo, I've replaced the hardcoded SCREEN_WIDTH and SCREEN_HEIGHT with a flexible alternative way. (Sorry about that!)

Sorry for late reply! Please let me know if it helped! Thanks!

At the end of my .xinitrc says exec startkde. That's because I'm running my wm with KDE.

hmm that was fast actually. I didn't modify my xinitrc, I'm using the default elementary OS desktop, will it work with that?

Maybe replacing gala by Wmderland in pantheon.session works

Maybe replacing gala by Wmderland in pantheon.session works

I found a related discussion here on reddit


Provenance: Simplify the matches() function a bit

Not comparing the hash value in some cases adds an execution
branch and thus makes testing harder. It is not needed as the
performance gains likely are neglectible and thus removed now.
Signed-off-by: Frank Viernau<EMAIL_ADDRESS>

Commit message nit: "neglectable".

Not comparing the hash value in some cases adds an execution
branch and thus makes testing harder.

I'm not getting this... shouldn't the initial "not" be dropped? How exactly does testing become easier by removing this conditional?

BTW, we actually had a TODO to implement the hash comparison, which I did, and now we're removing it again :roll_eyes:

How exactly does testing become easier by removing this conditional?

One code branch less to test, no need to cover canVerify

BTW, we actually had a TODO to implement the hash comparison, which I did, and now we're removing it again

Apart from the todo and the testing, do you think this change is an improvement or not?

Apart from the todo and the testing, do you think this change is an improvement or not?

That depends on the aspect to look at: Readability-wise I think it is an improvement as it makes the code simpler and thus easier to understand. Performance-wise I don't think it is an improvement, but then again this code path certainly is not performance-critical.

I have no problem throwing it away.

And I have no problem merging it now that it's there, provided that we have a convincing rationale in the commit message. Could we maybe say something like "... makes unit testing easier as fewer code paths need to be covered"?

Merge as the failing tests are only for the analyzer while the modified code is not used by the analyzer.


Anchor configuration parameters

I am currently testing different anchor configurations. For this. I changed the anchor configuration in
this line to self.anchors, self.anchors_cut = self.generate_anchors(lateral_n=0, bottom_n=1)
I would expect that the anchors will only originate from the bottom of the image. However, I get anchors on the right side of the image.  Could you please elaborate.

I found this is just an issue with the configured image width, setting the drawn image size in gen_anchor_mask.py to the one specified as the input size in the network solved it.
However, I am still not  sure what cut_ys exactly are and how the matching procedure works in detail. I understand that the cut_ys are used to pool the features alone the anchor lines but Ia m not sure how that works exactly. Is there any additional information on this or could you explain in a few sentences here?
Much appreciated.

The procedure is described in the paper on Section 3.3. In terms of the implementation, the code generates (in the compute_anchor_cut_indices function) three vectors (cut_xs, cut_ys and cut_zs) that contain the indexes of the points in the image that compose an anchor. That is, the indexes of the image that intersect that anchor, as explained in the paper. Then, during the forward propagation those indices are used to pool each anchor's features.


incremental training clarification

Hi,
Just to make things clear. If for a given engine I have at time t=0 domainA.en and domainA.it
I create the engine and if later on I have 2 more files domainB.en and domainB.it that I drop in the same folder. will ./mmt create start from scratch or do incremental training ? or can we use the ./mmt add command with "files" ?
thanks

First sorry, being this a functionality of the Alpha release it has not been documented yet.
If you run
./mmt create

you are building from scratch a new engine with DomainA+DomainB
If you want to add data you can use the command line
./mmt import -x ~/demo/netplan.tmx

Or use the API

Thanks Marco. Your link is dead but if this is your video I watched it.
I was able to train a model with > 20 Mio segements, took some time.
One thing could be helpful though, it's to log some stats about the number of segments imported, size of the PT or SAPT, number of n-grams for the LMs ...
It is now difficult to size properly the RAM when you load the model.
Actually my model loading just crashed on a 30GB machine (so I will allot more) and there is a residual java process that I cannot kill, I may need to reboot.
One last thing: my experience with Moses showed that in most cases you can use cube pruning limit to 400 instead of the defaut value 1000, with no loss in quality and big improvement in speed...
Just letting you know.
Anyhow great work, all of this.

Hi @vince62s
I confirm the first link is dead.
But the second one about the API is working:

https://github.com/ModernMT/MMT/wiki/API-Documentation#add-a-sentence-to-a-domain-incremental-learning

Hopefully you can find it useful.

Link to tutorial fixed.
Thanks for the pruning tip, to @davidecaroselli the final decision.
This alpha was very basic to allow the tutorial at AMTA. In a few weeks we should be able to push a solid and documented build.


adds the SingleQuantum driver with a test file for a real instrument

This PR adds the qcodes driver for SingleQuantum, along with a test file which works on a real instrument.
The code has some wrappers to communicate using JSON.
Any tips or comments are appreciated :)

The checks fail on creating the docs:
class reference target not found: qcodes.instrument.ip.IPInstrument
Because https://qcodes.github.io/Qcodes/api/instrument/index.html does not contain it.
I know the use of IPInstrument is discouraged, so any tips to not use it, or to fix the check is appreciated !

@jenshnielsen @WilliamHPNielsen

See issue !70 about the pipeline fail due to missing docstring IPInstrument.


Fix createdb to work with Django 1.7 and 1.8.

Django 1.8 changed the way optional args are added to management commands. This patch adds optional args "the old way" for Django 1.7 in Command.__init__(), and then uses "the new way" for Django 1.8, which is via a call to the new class method add_arguments().
There is a downside. In Django 1.7 we can get all args for migrate by simply extending migrate.Command.option_list. In Django 1.8, this returns an empty tuple, and I have no idea how to actually get the args from the migrate command, so I manually implemented --noinput and --nodata. This means in the end that createdb has less command line options available in Django 1.8 than in 1.7. If you want to have all options available, they are available here and can be directly copy-pasted. I do consider that --noinput and --nodata are good enough for createdb, any other task can call migrate directly.

Looks good enough to me Ed, thanks a lot!


Remove "Remote test distribution enabled" log

It was for debugging purpose, and now we no longer need it. We can find this information in trace.json.

@bot-gradle test and merge

OK, I've already triggered a build for you.


discussion for idk why

here now we can talk

lol

bruh my wellness class is notes on suicide
time to play suicide mouse hehe

xd

and i got sent to the hall
i forgor to turn off my volume so all they heard was HO HO HO HO HOOOOOOOOOOOOO

oop

yep
no cap

i have not slept for 3 days
im in mental pain

ah

i ported qt with extra keys, then someone commented said that it was unoptomized (and im a nub at porting), so i spent 3 days trying to optomize it

lol. i wish it wasn't on itch.io so i can play like a replit or something

i think i can find a way to put it on github
itll take a bit but ill do it

lol, for some reason at my school github.io are blocked but at home they arent

so like https://tylertehidiot.github.io/FNF-Battle-Of-The-Gods is blocked?

bruh you have not seen my fnf folder bookmark wise

more besides just that

yup thats blocked xd

matt week 2 psych?

its a mobile port (its blocked on your side)

send the link so i can play it at my house lmao

https://v6p9d9t4.ssl.hwcdn.net/html/5839353/bin/index.html

its not blocked for me lmao, i moved schools

oh ok

bruh
my classmates in front of me are trying to download fortnite on a free trial apponfly vm

and the trial is 30 min and then it kicks you out

xd

brb chromebook update

brb chromebook update

kk

shit it commented twice i thought my internet went down

xdd

ok i back

dope

(HAND REVEAL?!?!)
they changed our lock screen

Google Play Services: Downloading management protocols
me: NO NO NOT THAT SHIT I WANT YOU TO REMOVE IT

xd

what's your chromebook wallpaper?
mine is locked to a blue domain wallpaper

thats the domain one

mines black idk lol, im gonna change mine

bruh my account is associated with my personal email so my spark email service cant keep up with github emails lmao

im still the same person now but i changed my name

xd

i thought fnf unblocked was a little harsh

yup lmao

xd i might change my user

ok

dude someone made a asain joke about how they eat cat and dog witch isnt true, but im asian so i find that every rude

sorry bro

nah its good

gtg english class

lol

xd

no joke

sad

yeah she had to be transported out by ambulance

sad day

sad sad day

xd

mornin bro

i got a world record last night on funky friday
virus 99.96 accuracy

THE GRIND IS FINALLY OVER. THE END REMASTERED FC!!!

dope

mornin bro

hey bro quick question: would you be willing to help me finish my shaggy port?

hm whats all left?

just the assets folder

thats the one im having the most trouble with

whats wrong with it?

data folder

the jsons is all thats the problem with the rest im finishing right now

they shouldnt be broken.

just the names must be messed up

alright thanks

hewwo

and yes thats on canon (im like almost a god at 7k)

if there wasnt a file size limit on github i would record

bruh im finishing my port, and no joke theres a meme in the shaggy code lmao

https://user-images.githubusercontent.com/99343223/201364203-0ef3ba5f-7509-4f4a-b614-09095a0ef31d.mp4

@LEVIXDDLMAO help i cant access my own ports

?

i enter my github website name and it says “site not found”
:)
“And there’s a million things I haven’t done…. but just you wait…..” Alexander Hamilton
Sent with Spark
On Nov 15, 2022 at 7:33 PM -0500, LeviXD @.***>, wrote:

?
—
Reply to this email directly, view it on GitHub, or unsubscribe.

YEAH I KNOW WHAT HENT IS, AND YES IT WAS EASY

someone full combod the 6k version

it wasn’t easy

i’m a god at 6 and 7k and yet i missed 15 times

someone full combod the 6k version

I CAN, IM JUST TOO GOOD I SFC TERMAITION

SO HAVE I

XD

I DID IT ONCE AND YELLED “LETS FUCKING GO PFC”

also i MFC’d fisticuffs on matt wiik 3

all marvelous rating

I SFC BOXING MATCH ON KADE ENGINE

idk why people still use kade engine as a engine for mods, the literal engine is now a archive on github

i’ve pfc’d purgatory

with the effects

THE FRIST BOXING MATCH MADE

which one is the original?

gtg gn

ORIGINAL

WHICH IS THE ORIGINAL? THE CUSTOM BUILD MATT WIIK 3 RUNS ON?

CAUSE WIIK 4 RUNS ON KE 1.6.2

https://user-images.githubusercontent.com/99343223/202061612-26a844a7-0de1-4cc3-9e97-06d2f19e16ba.MOV
well well well

WHATEVER BOXING MATCH WAS MADE ON

yeah it was made on a custom build of KE 1.4

ya bois got a date levi

cap

no cal

no cap*

yup

i have proof 😀

ya bois taken 😌

i was so happy when she asked me out cause she’s always been my crush


yolox-s with default config cannnot converge in mini-coco128

yolox-s with default config cannnot converge in mini-coco128 provided in https://github.com/Megvii-BaseDetection/YOLOX/blob/main/docs/train_custom_data.md

Training code is python tools/train.py -f ./exps/default/yolox_s.py -d 1 -b 4 --fp16 -o -c ./models/yolox_s.pth
Nothing else is changed.

@LLsmile Training on mini-coco128 will probably produce unexpected behavior. Please try on standard COCO.

ok, thanks.


Add Airbnb, Uber, TripAdvisor, WeChat, Weixin, and WhatsApp

Why not add another two Uber colors, white and blue? IMHO it makes sense.

I agree with @devgru, could you add the white and blue as well? Thanks for doing this!

Updated, with more brand colors.

Thanks again for doing this!


Translation

Hello. I'd like to volunteer Korean translation work. Do you have plan for translation in the nearest future?

We currently have no plans for translation at the moment. That being said, we don't mind to see some translation work done for the repo.


DefaultValueConverter: Is this a viable option?

This isn't an issue as much as a question and/or suggestion:
What if, as a last-ditch effort to convert an object to a specific type, as the last block of code we added this:
try
{
	destValue = JsonConvert.DeserializeObject(JsonConvert.SerializeObject(origValue), destType);
	return true;
}
catch (Exception) { }

destValue = null;
return false;

You are already tightly coupled with Newtonsoft.Json, so this could catch some edge cases (like enum and Guid, for example).

Indeed this is a good suggession. DefaultValueConverter could totally rely on json.net for type conversion. I'll try this, thanks

Thanks @sonicmouse
this changes is included in v1.0.3

Thanks for all the work on this project -- I have totally pulled WCF out of my project in favor for your project. Speed has increased 10 fold and memory usage has decreased 10 fold.

I'm glad that it helps 😁


Introduce ContainerElement as SubmodelElement interface

Is your feature request related to a problem? Please describe.
In documentation and implementation we often describe special aspects of SubmodelElements, that may contain other SubmodelElements. It would be handsome to define a corresponding interface, so that we can talk about them.
For reference / completeness checks it would be handsome to have that interface, so that a developer could easily identify all SubmodelElements, that require more attention.
Describe the solution you'd like
Introduce an interface "ContainerElement" comparable to DataElement and apply it to AnnotatedRelationshipElement, Entity, SubmodelElementCollection, SubmodelElementList.
Handsome enhancements:

Operation "isIdShortRequired" -> returning true for all SubmodelElements except from SubmodelElementList
Operation "getContainedElements" -> returning Elements contained (values, statements, annotations, ....)

These operations should be seen as recommendations to SDK implementations, what they could provide as convenience operations.
Interface and operations have no effect on serialization.

TF AAS Part 1 2024-05-15

Introduction of abstract class "ContainerElement" would be backward compatible
it might make Value-Only explanation easier
to include operations would break concept of Part 1: there are no operations in classes so far ==> do not add operations here
not necessarily impact on existing implementations, only for those who reflect also all abstract classes etc.
==> Decision Proposal: accept

Workstream AAS Spec 2024-06-13
Approved to add an abstract class "ContainerElement". These classes will inherit from this class:

AnnotatedRelationshipElement,
Entity,
SubmodelElementCollection,
SubmodelElementList

Operation might need to be reconsidered later to be added as well

compare to https://github.com/admin-shell-io/aas-specs/issues/434: removing abstract class was considered to be risky to change. So I wonder whether introducing a new abstract class has the same effect.

2024-11-27 TF Metamodel
reconfirm that we want to add this abstract class but do not want to remove abstract class HasKind


New version: Parallels.Parallels version 19.4.25062

Pull request has been created with komac v2.3.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Hi @myrandor,
This manifest adds Apps and Features entries that aren't present in previous PR versions. These entries should be added to the previous versions, or removed from this version.
(Automated response - build 887.)


Automatic Layers and Not-Quite Infinity

This is a pull request for something that I have been working when I could these past few days. Most of the changes are regarding the new layer management lib. (yes, it should support implementation of photoshop/gimp style layering; no, I did not implement it)
It should make some things more efficient, and others easier. It also supports multi-resolution, (aligned layers with different resolutions), as well as canvas with different sizes (a step to infinity).
This is a draft for now, to test for potential bugs and because after the revamp there are some very annoying half-a-pixel offsets when putting images and things that I want to try fixing.

Oh, controls: ctrl + wheel is canvas zoom; middle mouse + drag is canvas move; rest should be as always.

This is a pull request for something that I have been working when I could these past few days.

oh sure, just a tiny little adjustment here and there whenever you've got a few seconds ;)
spent like 10 minutes trying to figure out why /sdapi/v1/txt2img was 404ing until i noticed i was surprisingly getting CORS errors, and even more surprisingly they stopped when i cleared out my localstorage which i don't even know what to think about that
i also experienced the reticle "decentering" from the cursor at a few zoom levels but i suspect https://github.com/zero01101/openOutpaint/pull/60/commits/6b0a25c15e2d8fe6f464bd1c64a4c843c9af688f fixes that nicely
love the "more" button after generation completes :D
haven't had a chance to go through all of this particularly deeply yet but i suspect i'll learn some new concepts as your commits generally have that effect :)  what i've seen so far looks wonderful as always though, thanks!

spent like 10 minutes trying to figure out why /sdapi/v1/txt2img was 404ing until i noticed i was surprisingly getting CORS errors, and even more surprisingly they stopped when i cleared out my localstorage which i don't even know what to think about that

That is... Weird. Probably something about the loading of the host from the storage? If there was something strange it should have asked you to re-enter the host though.

i also experienced the reticle "decentering" from the cursor at a few zoom levels but i suspect https://github.com/zero01101/openOutpaint/pull/60/commits/6b0a25c15e2d8fe6f464bd1c64a4c843c9af688f fixes that nicely

That should not have fixed anything, really. It's just a fix for the debug part of the ui. About decentering, maybe it is with a odd number of scale? I noticed it is snapping to both tile center and corners.

love the "more" button after generation completes :D

We should do more of these small quality of life updates, actually

haven't had a chance to go through all of this particularly deeply yet but i suspect i'll learn some new concepts as your commits generally have that effect :)  what i've seen so far looks wonderful as always though, thanks!

No worries, any questions please tell.

-edit
minor visual bug, if you refresh the page with devtools open and then close them, checkerboard pans down the screen to "compensate"

Could you file this as an issue? I can give it a look later.

That is... Weird

right?? it handled the OPTIONS and GET calls to extra-single-image fine and dandy, but i honestly don't even remember seeing OPTIONS calls to txt2img while it was doing that... look, i've got a pretty singular talent for ruining everything around me so i sorta suspect this one's on me ;)

That should not have fixed anything, really.

:badpokerface: welp i just saw the addition of the offset and decided "yes, that must've been it, jolly good" :D

We should do more of these small quality of life updates, actually

genuinely agreed! actually on that, i wanted to apologize for not pushing more stuff recently; you keep just cranking out these PRs that are fantastic if a bit over my head sometimes and i'm simple and need time to catch up, and admittedly, like 97% of the functionality i wanted at first is functionally here already and i just can't stop playing with it lol
i may have also wasted some time trying to learn how to talk to SD2 over the weekend

Could you file this as an issue? I can give it a look later.
done and done; it's really quite minor in the fact that a user could quite easily just... pan the canvas back to origin :D https://github.com/zero01101/openOutpaint/issues/61

That is... Weird

right?? it handled the OPTIONS and GET calls to extra-single-image fine and dandy, but i honestly don't even remember seeing OPTIONS calls to txt2img while it was doing that... look, i've got a pretty singular talent for ruining everything around me so i sorta suspect this one's on me ;)

Now that I think about it, it may have been my fault, as I basically reimplemented the full pipeline of dream() in general. If I remember correctly, when I saw the fetch() call used for dream, I removed most of the headers that I considered redundant.
Probably there was a cache-related header that triggered some issues, and cleaning site data may have resolved the cache issue.

That should not have fixed anything, really.

:badpokerface: welp i just saw the addition of the offset and decided "yes, that must've been it, jolly good" :D

If you could create an issue for this one too, it would be perfect!

We should do more of these small quality of life updates, actually

genuinely agreed! actually on that, i wanted to apologize for not pushing more stuff recently; you keep just cranking out these PRs that are fantastic if a bit over my head sometimes and i'm simple and need time to catch up, and admittedly, like 97% of the functionality i wanted at first is functionally here already and i just can't stop playing with it lol

No problems whatsoever! I am quite satisfied with the current state of the app, actually.

I may have also wasted some time trying to learn how to talk to SD2 over the weekend

That is something I have to give a deeper look; Interestingly, even though I created the discussion on SD2, I have still not used it myself.

Could you file this as an issue? I can give it a look later.

done and done; it's really quite minor in the fact that a user could quite easily just... pan the canvas back to origin :D #61

Yeah, that's what I was thinking. I'm not really sure how to address this issue, as we don't really receive any information as to how the window was resized. Only that it was, indeed, resized, and the new window size.

Fixed canvas on chrome. It seems chrome doesn't like to transform layer coords based on CSS transforms, so we will have to do this manually.
Windows now are kept inside the viewable area. No more losing them when resizing the window or dragging them outside.
Fix for image gen shortcuts, now "+" generates more images.

Viewport also starts in the center now, maybe could be a fix to #61.

you are legitimately a machine

That should not have fixed anything, really.
:badpokerface: welp i just saw the addition of the offset and decided "yes, that must've been it, jolly good" :D
If you could create an issue for this one too, it would be perfect!

if i could reproduce it, i'd be glad to but it hasn't happened since lol; it was very similar to how it behaved long before i even pushed this to github if i was using it with devtools open and i was scrolled down the page, it was definitely offsetting incorrectly due to actual mouseX/Y vs canvasX/Y (ergo the coord monitors) back then... hasn't occurred since though, but if it does i'll try to recreate it reliably :)
locking the floating windows to the active viewport is a little pinch of genius

Fixed canvas on chrome. It seems chrome doesn't like to transform layer coords based on CSS transforms, so we will have to do this manually.

sigh i need to start testing things on more than firefox because i didn't even know that was a thing lol

Viewport also starts in the center now, maybe could be a fix to https://github.com/zero01101/openOutpaint/issues/61.

hah, i was 100% prepared to completely write off the checkerboard positioning as not-a-bug, wontfix, this is literally just how browsers work but here you are with more fixes already!
i just noticed that if you answer N to an img2img batch, it leaves the previous marching ants behind - will open an issue :)

Hi, could you specify what exactly? I'm uncertain if there is a way for me to see what you are referring to...

Are you talking about the body scroll fix?

i haven't experienced much in those offsets you mentioned in the initial PR message but that's probably because i'm simply inobservant :D

And this is probably less of a lack of attention and more that I kinda gave up on fixing small canvas offsets for now and just used a full-sized layer for the dream image insertion overlay: b2d51d40d45e881c4f1f82c1f8f90681fb463fbe

oh did i mention that i learned if you leave your prompt field empty and use img2img on a chunk of existing image, it works as a very effective "alternative" of what currently exists, like a more literal mutate button and it's wonderful :D
...this has literally nothing to do with the PR, did i mention i'm inobservant

That's cool! I need to play more with some of the features.

lmao i'm bad at github, i warned you :P i meant my little brushed mask clearing fix https://github.com/zero01101/openOutpaint/pull/60/commits/4dafe502485ea0d87a5b3e0c9946187933866842; layers sensibly only permit deleting the whole thing, but i figured i might have missed a better way to manage the boundary box than a for loop

lmao i'm bad at github, i warned you :P i meant my little brushed mask clearing fix 4dafe50;

Is this for clearing mask where the image was put? If so, that could use the ctx.clearRect() function. Should work wonders for clearing a square area! (ex: https://github.com/zero01101/openOutpaint/commit/4dafe502485ea0d87a5b3e0c9946187933866842#r91620767)

layers sensibly only permit deleting the whole thing, but i figured i might have missed a better way to manage the boundary box than a for loop

All layers have both their canvas and context accessible, and for the main ones (mask for example) I continued exposing the canvas and Ctx with the same names as before for backwards compatibility, as seen in my previous line comment.
So, don't be afraid to use the canvases as normal.

So, when referencing a specific line, I would recommend you to comment on the line itself of the changes:

When hovering the line you should see a blue plus thing on the side. Clicking that allows you to comment on a specific line.

your guidance is hugely appreciated as always, clearRect() is precisely what i should have been using the whole time

Added one more comment to your commit, regarding imagedata objects.
https://github.com/zero01101/openOutpaint/commit/4dafe502485ea0d87a5b3e0c9946187933866842#r91621617
Some more info that may be useful for you in the future.

I will then be merging the pull for now.

i'll spiff up the readme tomorrow after work, many thanks again!


wallet closes, right after login

using win10 64bit
added logfile
mwcwallet.log

Logs show that the password started with a "-" and that's what caused a problem. After asking the user to change to a different password it worked. Should either prevent users from setting a password that starts with a "-" or ensure it works.

Will try to fix it. Also probably '--' will not work too because of the same reason.

Add validation for first '-' symbol.  We have to deal with mwc713  config parser.


Crop black margins from screenshots

🚀 Feature

Motivation
Currently, the screenshot functionality from the command produces screenshots with black margins around the image, making these screenshots not directly useable in any figures etc without cropping.
Pitch
It would be nice to add an option to be able to automatically crop the black margins from the image. An example function to do something along those lines could be something like this:

def crop_black_margins(img: Image.Image, output_path: str) -> None:
   """
   This function takes a PIL Image as input, detects and crops black margins from the image,
   and saves the cropped image to a specified path.

   Parameters
   ----------
   image : PIL.Image.Image
       The input image from which to crop black margins.
   output_path : str
       The path at which to save the cropped image.

   Returns
   -------
   None
   """
   image = Image.open(img)

   # Convert image to grayscale for simpler processing
   img_gray = image.convert('L')

   # Convert to numpy array for easier processing
   img_array = np.array(img_gray)

   # Detect left margin
   for margin_left in range(img_array.shape[1]):
       if np.any(img_array[:, margin_left] != 0):
           break

   # Detect right margin
   for margin_right in range(img_array.shape[1]-1, -1, -1):
       if np.any(img_array[:, margin_right] != 0):
           break

   # Detect top margin
   for margin_top in range(img_array.shape[0]):
       if np.any(img_array[margin_top, :] != 0):
           break

   # Detect bottom margin
   for margin_bottom in range(img_array.shape[0]-1, -1, -1):
       if np.any(img_array[margin_bottom, :] != 0):
           break

   # Crop the image
   img_cropped = image.crop((margin_left, margin_top, margin_right, margin_bottom))

   # Save the cropped image
   img_cropped.save(output_path)
   ```

## Alternatives

Alternatively, the way screenshots with `canvas_only = TRUE` work could be adjusted to not have black margins to start with.

Hi @FloWuenne,
Thanks for opening this issue! Recently, there has been some talk on forum.image.sc. I think we indeed should look into this.
As we talked about earlier today and also just for record keeping for the others. One thing that would be a possible addition to a feature like this is to also make sure that a scale_bar can be visualized on top of the data as this is a typical requirement for publication images.

I think this is sort of a duplicate of https://github.com/napari/napari/issues/4943
I agree that we should make this a priority. The approach in #4943 I think it would probably solve the scale_bar positioning gratis.

We indeed tried by changing the canvas size and resetting the view, but we didn't get it to work correctly yet:)


[CPT] New project to deploy CPT tools

/test rhoai-light cpt

/test rhoai-light cpt

/test rhoai-light cpt

smoke test passed:

backend
frontend
merging as a first step.


Got error while exporting csv in dashboards

I was trying to export the data from dashboards by clicking Export CSV, like below, but got error saying {"message":"Error: Error (planning_exception): {'error': {'root_cause': [{'type': 'planning_exception', 'reason': 'The maximum LIMIT for aggregate sorting is [65536], received [100000]'}], 'type': 'planning_exception', 'reason': 'The maximum LIMIT for aggregate sorting is [65536], received [100000]'}, 'status': 400}"}

However, if I go to 'view chart in Explore' and exporting csv by click 'CSV icon', then the whole queried data can be exported successfully. Does anyone know how it was caused and how to solve it?
Expected results
export and download CSV from the dashboards tab.
Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ V] I have reproduced the issue with at least the latest released version of superset.
[ V] I have checked the issue tracker for the same issue and I haven't found one similar.

Please provide version? @lukelin-linkernetworks

Please provide version? @lukelin-linkernetworks

I directly pull the latest docker image few days ago, and the sha is 3c3cb8e7f2249b0427470253788ec3dc5fd5c5caad74d35ca42e0243f9b4f444
however, when i go with sperset version, it shows Superset 0.0.0dev

gotcha, thanks for the info. @jinghua-qa can you double check and add test:case? thanks!

I tried latest master and it seems csv download work fine in dashboard, can you provide more detail of repro steps?
https://user-images.githubusercontent.com/81597121/141395686-1a4f44c3-68b3-4f57-8789-f71cb378bde3.mov

I directly pulled the image and deployed on machine instead of using the latest master branch, but I think this isn't the version difference unless the image version is far behind the master branch. Also, I was using Elasticsearch api to connect the superset with database, and others should be pretty normal as making dataset, aggregating, making chart. The most important weird thing is that you can download csv in charts but not in dashboard, so any idea why it shows the error The maximum LIMIT for aggregate sorting is [65536], received [100000]' ?

@jinghua-qa the error is specific to elasticsearch, so we'll need to be using that as a db connection to repro, fyi.

Hi @eschutho, @jinghua-qa, @junlincc, any update for this issue?

Hi @eschutho, @jinghua-qa , @junlincc,again, any update for this issue? or anything I can provide to better understand this issue? thanks

@rosemarie-chiu can you try to reproduce? thanks

I am able to reproduce this issue on 2.0.1 with an Elasticsearch backend. In our environment, we set ROW_LIMIT=200000 and SQL_MAX_ROW=200000. The chart has ROW_LIMIT set to 50000.
Now, Elasticsearch has a limitation that for sorted queries, the maximum LIMIT is 65535 rows (https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-limitations.html#_sorting_by_aggregation)
The problem seems to be introduced in: https://github.com/apache/superset/blob/65fffe974b6d881dabbf6600fe034f1e5ae809f0/superset-frontend/src/dashboard/components/gridComponents/Chart.jsx#L354 where the chart row limit is overwritten with maxRows property.
We've patched Chart.jsx so that the chart property does not get overwritten and verified that the export is working.

This problem caused by your Elasticsearch server query limit,  just update superset config params `SQL_MAX_ROW , the value less than  65536 , it can deal your problem. my Elasticsearch server limit is 10000, so i set  SQL_MAX_ROW=9999

This problem caused by your Elasticsearch server query limit.
just update superset config params SQL_MAX_ROW , the value less than 65536 , it can deal your problem.
my Elasticsearch server limit is 10000, so i set SQL_MAX_ROW=9999.

This problem caused by your Elasticsearch server query limit.
just update superset config params SQL_MAX_ROW , the value less than 65536, (you can config Elasticsearch server query limit number also) it can deal your problem.
my Elasticsearch server limit is 10000, so i set SQL_MAX_ROW=9999.

Thank you for the suggestion. I was aware of this solution. But, in my case it doesn't work as we need the 200000 limit for other charts.


New query syntax with operators and modifiers

Check out the updated README for an explanation. Creates a way to write compact queries without a bunch of Dict constructors, i.e.
find(collection, (query("job" => "Fireman"), orderby("age" => -1)))

This is great, thanks!


ESP32 not supported?

nodemcu-uploader fails on NodeMCU for ESP32 on my esp32 dev board. No idea why. The 'terminal' works normally, but the 'upload' dies this way:
$ python nodemcu-uploader.py -p /dev/ttyUSB0 -t 30 upload init.lua
opening port /dev/ttyUSB0 with 115200 baud
Traceback (most recent call last):
  File "nodemcu-uploader.py", line 10, in <module>
    main.main_func()
  File "/tmp/nodemcu-uploader/nodemcu_uploader/main.py", line 252, in main_func
    uploader = Uploader(args.port, args.baud, start_baud=args.start_baud)
  File "/tmp/nodemcu-uploader/nodemcu_uploader/uploader.py", line 78, in __init__
    __sync()
  File "/tmp/nodemcu-uploader/nodemcu_uploader/uploader.py", line 76, in __sync
    raise DeviceNotFoundException('Device not found or wrong port')
nodemcu_uploader.exceptions.DeviceNotFoundException: Device not found or wrong port

$ python nodemcu-uploader.py -p /dev/ttyUSB0 -t 30 terminal
--- Miniterm on /dev/ttyUSB0  115200,8,N,1 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---

>

I have same problem here :( Found a solution ??

Just a work-around. IIRC https://github.com/4refr0nt/luatool worked OK.

need to get me a esp32 i think.
Looks as if the method of detecting a working device is not working as it should.

I've had the same issue when trying to communicate with the ESP8266 chip on my Adafruit Feather Huzzah. Installing the cp210x.ko kernel module driver from Silicon Labs (which the Adafruit guide links to) didn't fix it either.
Just like for @joysfera, I can communicate with my device using nodemcu-uploader terminal  or screen /dev/ttyUSB0 9600. However, I need access to init.lua because lua: cannot open init.lua.
Whenever I try nodemcu-uploader download init.lua --port /dev/ttyUSB0 I get
nodemcu_uploader.exceptions.DeviceNotFoundException: Device not found or wrong port as well.

As a workaround comment next line in uploader.py
self.__expect('%sync%\r\n> ')

But NodeMCU on ESP32 does print the '>' char prompt, just like on the ESP8266, doesn't it?
Does it perhaps omit the '\r' or what's up?

I don't know, I haven't check. I am not really good at python. I'll try to check.

I split the expect sync line to two lines and got me further, but now I'm hitting a different problem.
                self.__expect('%sync%\r\n')
                self.__expect()

Uploading binary file in verbose mode causes it to print garbage. This patch fixes it. Hope it helps somebody.
diff --git a/nodemcu_uploader/uploader.py b/nodemcu_uploader/uploader.py
index e12d243..b8a15e2 100644
--- a/nodemcu_uploader/uploader.py
+++ b/nodemcu_uploader/uploader.py
@@ -74,7 +74,8 @@ class Uploader(object):
                 time.sleep(self.autobaud_time) # Wait for autobaud timer to expire
                 self.__exchange(';') # Get a defined state
                 self.__writeln('print("%sync%");')
-                self.__expect('%sync%\r\n> ')
+                self.__expect('%sync%\r\n')
+                self.__expect()
             except CommunicationTimeout:
                 raise DeviceNotFoundException('Device not found or wrong port')

@@ -375,7 +376,7 @@ class Uploader(object):
             log.debug('pad with %d characters', padding)
             data = data + (' ' * padding)
         log.debug("packet size %d", len(data))
-        self.__write(data)
+        self.__write(data, True)
         self._port.flush()
         return self.__got_ack()

Tried all above mentioned patches, nothing helped.

FYI, working on a real fix. Seems like the issue is related to multiple Lua commands in one line. Doesn't make sense but spliting the commands to separate lines seems to help so I'm giving it a try.

I too had this problem, and I started out trying to track the problem down.
Since I'm rather Python v3 focused, I had installed nodemcu-uploader with:
pip3 install nodemcu-uploader

Made a copy of the contents of ~/.local/lib/python3.6/site-packages/nodemcu_uploader
into an empty directory to start debugging. Immediately had the following error:
ImportError: No module named serial

Weird? Checked sys.path and it was pointing to python2.7 libraries.
Changed the first line in nodemcu-uploader.py
#!/usr/bin/python3

Re-testing and upload worked.
I guess that was to be expected. Ubuntu 18.04 LTS defaults to Python v2.7.
Wondering whether this single character "fix" might work for others.

I'm using a SparkFun ESP-32 Thing and had to rebuild the firmware for 26MHz.
I found that commenting out the auto-baud code in uploader.py, i.e.
      #self.__writeln('UUUUUUUUUUUU') # Send enough characters for auto-baud
       self.__clear_buffers()
       #time.sleep(0.30) # Wait for autobaud timer to expire

helps. BUT not all the time.
When I get the usual error, then I connect as a terminal, enter =print 'please work', exit and try again.  The actual string printed doesn't matter.


fatal error: tensorflow/core/common_runtime/gpu/gpu_process_state.h: No such file or directory

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Arch Linux (Kernel 5.3.18, glibc 2.30-3)
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): Source
TensorFlow version: bd56e040ba4a8272163357a2f8786a128deb4aaf from r2.1 branch.
Python version: Not Applicable
Installed using virtualenv? pip? conda?: Not Applicable
Bazel version (if compiling from source): 0.29.1
GCC/Compiler version (if compiling from source): Host GCC 9.2.0; Cuda GCC 6.5.0
CUDA/cuDNN version: CUDA 10.0; cuDNN 7
GPU model and memory: RTX 2070 8GB

Describe the problem
I'm trying to upgrade the TensorFlow dependency in our project from 42c4f4ab6b53bce8639c203d7839d27eac11bd2f (from r1.13 branch) to bd56e040ba4a8272163357a2f8786a128deb4aaf (from r2.1 branch). The problem is that gpu_process_state.h is missing. The error line in our project is here.
/home/abcdabcd987/work/nexus/src/nexus/backend/tensorflow_model.cpp:6:10: fatal error: tensorflow/core/common_runtime/gpu/gpu_process_state.h: No such file or directory
    6 | #include "tensorflow/core/common_runtime/gpu/gpu_process_state.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

I checked the cloned TensorFlow source code. I can see that gpu_process_state.h exists. However, when I checked that build output that bazel produces, it was not there:
$ pwd
/home/abcdabcd987/work/nexus/build/tensorflow/execroot/org_tensorflow/bazel-out/k8-opt/bin/tensorflow/include

$ ls -la tensorflow/core/common_runtime/gpu/
total 28
drwxr-xr-x 2 abcdabcd987 abcdabcd987 4096 Jan  3 20:37 ./
drwxr-xr-x 3 abcdabcd987 abcdabcd987 4096 Jan  3 20:37 ../
-rw-r--r-- 1 abcdabcd987 abcdabcd987 7639 Jan  3 20:37 gpu_event_mgr.h
-rw-r--r-- 1 abcdabcd987 abcdabcd987 4091 Jan  3 20:37 gpu_id.h
-rw-r--r-- 1 abcdabcd987 abcdabcd987 1617 Jan  3 20:37 gpu_id_manager.h
-rw-r--r-- 1 abcdabcd987 abcdabcd987 1665 Jan  3 20:37 gpu_init.h

I tried to figure out the difference of the BUILD files between the old and the new version, but since the //tensorflow:install_headers target is quite complicated, I cannot get it straight. Any help is much appreciated! Thanks!
Provide the exact sequence of commands / steps that you executed before running into the problem
TensorFlow in our project is built with the following command:
bazel --output_base=../build/tensorflow build \
  --config=opt \
  --action_env CUDA_TOOLKIT_PATH=/usr/local/cuda-10.0 \
  --action_env CUDNN_INSTALL_PATH=/usr/local/cuda-10.0 \
  --action_env GCC_HOST_COMPILER_PATH=/usr/bin/gcc-6 \
  //tensorflow:libtensorflow_cc.so \
  //tensorflow:libtensorflow_framework.so \
  //tensorflow:install_headers

The .tf_configure.bazelrc is the following:
build:xla --define with_xla_support=false
build --action_env TF_NEED_OPENCL_SYCL="0"
build --action_env TF_NEED_ROCM="0"
build --action_env TF_NEED_CUDA="1"
build --action_env TF_CUDA_VERSION="10.0"
build --action_env TF_CUDNN_VERSION="7"
build --action_env TF_NCCL_VERSION=""
build --action_env TF_CUDA_COMPUTE_CAPABILITIES="6.0,7.5"
build --action_env TF_CUDA_CLANG="0"
build --config=cuda
build:opt --copt=-march=native
build:opt --copt=-Wno-sign-compare
build:opt --host_copt=-march=native
build:opt --define with_default_optimizations=true
test --flaky_test_attempts=3
test --test_size_filters=small,medium
test --test_tag_filters=-benchmark-test,-no_oss,-oss_serial
test --build_tag_filters=-benchmark-test,-no_oss
test --test_tag_filters=-gpu
test --build_tag_filters=-gpu
build --action_env TF_CONFIGURE_IOS="0"

Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@abcdabcd987, I believe this has been fixed in 2.2.0rc2. Let me know if you are still seeing this issue with the latest version.

Hi @yifeif , as of v2.2.1, the problem still exists. The built target doesn't include gpu related headers, such as gpu_process_state.h.
root@355caa9c629e:/tensorflow# git show --oneline -s
25fba035f3 (HEAD, tag: v2.2.1, origin/r2.2) Merge pull request #43445 from tensorflow-jenkins/version-numbers-2.2.1-25147
root@355caa9c629e:/tensorflow# ls bazel-out/k8-opt/bin/tensorflow/include/tensorflow/core/common_runtime/gpu/
gpu_event_mgr.h  gpu_id.h  gpu_id_manager.h  gpu_init.h

I believe PR #36013 is still relevant.