libarchive-qt 2.0.4 -> 2.0.6

Motivation for this change
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 139520 at 9e1a79a0 run on x86_64-linux 1

3 packages built successfully:

corearchiver
coregarage
libarchive-qt


TUI navigation

There is no keyboard navigation between panes in the TUI at the moment. Maybe something like ctrl + (h, j, k, l) and/or ctrl + (arrow keys) to allow user to shift focus between editor and the results table.

I added better navigation in v0.2.2. Once I make the table list pane interactive, I'll add navigation to that pane too.

Navigation to the table list pane is set to be included in the next release.


Improve channels BBEs

Codecov Report

:exclamation: No coverage uploaded for pull request base (next-release@28bd3b9). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff               @@
##             next-release   #12477   +/-   ##
===============================================
  Coverage                ?   58.07%
  Complexity              ?      659
===============================================
  Files                   ?     2060
  Lines                   ?   100938
  Branches                ?    12831
===============================================
  Hits                    ?    58622
  Misses                  ?    37574
  Partials                ?     4742

Continue to review full report at Codecov.

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


[dashboard] Transparent Background option not working

Screenshot

Description
'Transparent background' setting does not work when using inside a tab(which is not a top level tab).
Design input
[describe any input/collaboration you'd like from designers, and
tag accordingly. For design review, add the
label design:review. If this includes a design proposal,
include the label design:suggest]

Keeping this active

Interesting... I could go either way on this one. On one hand, sure, I can see the allure of tabs having a transparent background, so that the background of the dash shoes through consistently. On the other hand, the area of a tab is kind of a "widget" in a dashboard in its own right... and if you took away the white background it'd be a bit ambiguous where the tab area ends and the charts below begin.
If we want to keep the tab area opaque (which I think might make more sense than transparent, actually), perhaps we should hide/remove this control for chart rows within the tabs, since it's irrelevant unless the row is moved out. Thoughts @kasiazjc?

@rusackas Got your point. Our concern with the current behavior of tabs is that all the big number charts in a tab are almost merged in white background, but with transparent background we can make it out where a certain chart or a column/group of charts end.
I guess the best solution would be to bring in a new feature of 'Borders' to each widget in dashboard. We can set the borders to whichever bunch of elements we prefer.
I had raised it as a feature request a long time ago, https://github.com/apache/superset/issues/15161. Although some of them can be achieved with CSS(I think), but still it requires an extra skill to be able to personalize a dashboard. A bunch of format features in the dashboard can be considered. Just like position_json, we can have a format_json holding format settings(border, title text size, title text color, etc..) of each widget in the dashboard.
Let me know what you think and I can start a discussion for the same.

Closing this as stale since it's been silent for so long, and we're trying to steer toward a more actionable Issues backlog. If people are still encountering seeing this as a bug in current versions (currently 3.x) please open a new Issue or a PR to address the problem. We're also happy to discuss deprecating/adding/redesigning these features as a Github Discussion or a SIP. Thanks!


rm efd related roles & profiles (replaced by influxdb efd)

The https://github.com/lsst-it/puppet-efd repo has been archived.


Not able to connect to both postgres instances running as container trough host ( localhost )

Hello,
I do a lot of research but still not able to find how to fix this.
My image look like this:
  pgsql:
    image: postgres:10.1
    container_name: "first-pgsql"
    environment:
      - 'DB_USER=${DB_USER}'
      - 'DB_PASS=${DB_PASS}'
    volumes:
      - '${DB_VOLUME_LOCATION}:/var/lib/postgresql/data'
    ports:
      - 5432:5432
    restart: 'always'

And when I do docker-compose up  -d and docker ps
I get results for column PORTS as:
<IP_ADDRESS>:5432->5432/tcp  and that is good because I'm able to connect to this database from host machine using localhost:5432
Now I'm adding a new container in paraller with this configuration:
  pgsql2:
    image: postgres:10.1
    container_name: "second-pgsql"
    environment:
      - 'DB_USER=${DB_USER}'
      - 'DB_PASS=${DB_PASS}'
    volumes:
      - '${DB_VOLUME_LOCATION}:/var/lib/postgresql/data'
    ports:
      - 6666:6666
    restart: 'always'

As you can see above port is changed to 6666.
Now I am getting results for column PORTS as:
5432/tcp, <IP_ADDRESS>:6666->6666/tcp and that is not good because I'm not able to connect to another instance of postgres from my host using localhost:6666
It seems how it works very well only for default pg port 5432 when we come to connecting on host machine to postgres container instance. For any other port it doesn't work.

Hi,

5432 is the  exposed port,

see https://github.com/docker-library/postgres/blob/master/10/Dockerfile#L132

if you want to Publish or expose port, try this:

    ports:
      - 6666:5432

or
    ports:
      - <IP_ADDRESS>:6666:5432

see: https://docs.docker.com/engine/reference/commandline/run/#publish-or-expose-port--p---expose
I hope this helps!

@ImreSamu is correct; you just need to specify the desired host port but keep the container port on 5432. Otherwise you are forwarding 6666 from the host to 6666 in the container and nothing is listening there.


Cancel outstanding tasks on document edit in the language server

Dramatically reduces system load and increases responsiveness of the language server. In my tests, I was not able to get the server above 100% CPU anymore.
The check_system calls inside pure Lean functions are a bit problematic. I did not find any process terminations from cancellation anymore after blacklisting two of them in the last commit but I may have missed some of them.

!bench

@Kha This was reverted due to crashes, and I have a worker stack trace at https://gist.github.com/collares/ae3a8d5b5f7c6976b8d46b5bfb6e945b. It seems like the kernel calls check_interrupted() directly in for_each_fn::apply.

FWIW, https://github.com/leanprover/lean4/pull/2036#issuecomment-1382659486


Redirect to the new deploy guides location

What kind of changes does this PR include?

Something else!

Description
#849 moved the deploy guides from /[lang]/deploy/[service] to /[lang]/guides/deploy/[service] causing some 404s from old links like in Discord threads. This Netlify redirect makes sure we redirect from the old URLs to the new ones.

LGTM!


[DF] Add COT math function

Is your feature request related to a problem? Please describe.
Cotangent function is not supported out of the box with DataFusion. Register a COT math function and provide all bindings.
Describe the solution you'd like
Register a function in DaskSQLContext for COT that calculates cotangent
Describe alternatives you've considered
None
Additional context
None

Can be closed, thanks!

closed via #657


Possible fix for pivot models $table variable not respected / overridden

This is more a proof of concept for a possible solution for issue #51410 as it adds functionality to the ->using() function for a belongs to many relation that may be unnecessary.
I added a test that demonstrates that this fix solves the ->attach() issue but the ->get() functionality is still broken as it seems to not take in consideration the logic in the ->using() function and defaults back to using the wrong table name (The error is also present in the test).
Keeping it as a draft for now as I'm not sure we want to add this extra complexity to the code base and also not sure if my solution is making any sense 😅 also the get functionality is still not working as expected/broken...

See the related issue for the reason this PR is getting closed


Feature request: support sql module for python api

With command line version of trace_processor_shell, we can split complex queries into different sql files and imported via --add-sql-module. However, python api doesn't support this kind of feature. It's inconvenient to write sql module and reuse.

This is a very good idea, but unfortunately not a high priority for us right now. Please, feel free add this (https://perfetto.dev/docs/contributing/getting-started) and we would be happy to review.


openssl secure password generation issue

I noticed in the README that the OpenSSL call to generate a secure password for the postgresql database in this cookbook was broken. I think this may fix it. The server recipe seemed to be using an outdated feature that will go away with a future release of the openssl cookbook. Please feel free to test and verify this method. Thanks.  Best Regards, GitBytes (Ian)

+1 for helping getting rid of the
depends 'openssl', '~> 4.0.0'
contraint
As the random_password method is slightly different from secure_password we might consider using :base64 instead of :hex (random_password(length: 20, mode: :base64))?
Regards, Bernhard

@bottkv488 Just letting you know I have made the adjustment you recommended. Thanks for the suggestion!
Best Regards, GitBytes (Ian)

@GitBytes I'm glad you liked it :)

@slyness Awesome! Thanks for doing that!


I am unable to see or open the console in my preview

Describe the bug
Whenever I create new project whether of simple javascript or new project react in my preview which open on side I am unable to see the console screen. So I could see my console log.
Link to the blitz that caused the error
https://stackblitz.com/edit/vitejs-vite-c6c4qr?file=README.md,src%2FApp.jsx,src%2FApp.css,src%2FShowNameList.jsx
Steps to reproduce

Just write the console.log("Print") in any of the JSX file.
But now you will not see the console screen to open so that you can see you console.log

Expected behavior
To see the conosle screen so that i can see my consoles.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots

Platform
Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 123
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 116771347,
  "usedJSHeapSize": 112197627,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 7dbe22a9

Additional context
No response

hi! :wave: thanks for reporting this issue!
You need to open your browser console window and the logs will appear there!


DevicePortalConnection fails when device is connected via USB, but has an active wifi connection.

I've observed this behavior on HoloLens, so I don't know if this affects other devices as well, but if the HoloLens is connected to WLAN and via USB to a PC, attempting a connection via <IP_ADDRESS>:10080 fails.  I've printed out the status on the ConnectionChanged event, here's the output:
DeterminingConnectionRequirements Connecting Checking secure connection requirements
UpdatingDeviceAddress Connecting Updating device connection
Idle Connected Device connection established
Exception thrown: 'System.Security.Authentication.AuthenticationException' in System.dll
Exception thrown: 'System.Security.Authentication.AuthenticationException' in System.dll
Exception thrown: 'System.Security.Authentication.AuthenticationException' in System.dll
Exception thrown: 'System.Security.Authentication.AuthenticationException' in System.dll
Exception thrown: 'System.Security.Authentication.AuthenticationException' in System.dll
Exception thrown: 'System.ObjectDisposedException' in System.dll
Exception thrown: 'System.Net.WebException' in System.dll
Exception thrown: 'System.Net.WebException' in System.dll
Exception thrown: 'System.Net.Http.HttpRequestException' in mscorlib.dll
Exception thrown: 'System.Net.Http.HttpRequestException' in mscorlib.dll
Exception thrown: 'System.Net.Http.HttpRequestException' in mscorlib.dll
Exception thrown: 'System.Net.Http.HttpRequestException' in mscorlib.dll
Exception thrown: 'System.Net.Http.HttpRequestException' in mscorlib.dll
An error occurred while sending the request.
Exception thrown: 'System.Net.Http.HttpRequestException' in WpfDevicePortal.exe

I've observed that somewhere in the connection process DevicePortal.Address (which is <IP_ADDRESS>:10080 initially) is replaced with the address of the access point the HoloLens is connected to. Does anyone know why this is happening?

This is due to the updateConnection bool being set to true by default on the connectAsync method in DevicePortal.cs: https://github.com/Microsoft/WindowsDevicePortalWrapper/blob/master/WindowsDevicePortalWrapper/WindowsDevicePortalWrapper.Shared/DevicePortal.cs#L252
Can you try changing your code to call portal.ConnectAsync(updateConnection:false);
This should stop your HoloLens from attempting to pick up the WiFi connection

@Holo-Krzysztof, Would an API (breaking) change to support; Update, Don't Update, Try to update (aka return localhost if cannot connect to wifi) be helpful here?

@hpsin,
I'd need to see the contents of the HttpRequestException and what IP the portal was attempting to connect to.

@Holo-Krzysztof, is your app able to successfully talk to the HoloLens via the localhost (usb) connection? Also, can you double check that the IP address that the wrapper is attempting to connect to is valid (ex: not <IP_ADDRESS> or something weird) and post the exception contents (feel free to obfuscate the ip address)?
Thanks!

@hpsin Thanks, that fixed it. The problem was that I always connected via USB and didn't know what "updateConnection" means in that context or why it is done.
@davidkline-ms I don't get more than what I've posted above, it doesn't catch an exception when wrapping the call to ConnectAsync inside a try-catch block (using the dll version via nuget). I assume the exception is handled within the library itself and not propagated upwards.
Yes, I can successfully connect via USB and yes, it is a valid address. It's exactly the address of the HoloLens inside the local network (<IP_ADDRESS> when I checked).

@Holo-Krzysztof,
You may be able to get more information by enabling the debugger to break on first chance exceptions when you hit the HttpRequestException.
To do this, load your project and go to Debug | Windows | Exception Settings, expand Common Language Runtime Exceptions and check . You may have to continue on past a few unrelated exceptions, but this should help diagnose what is going wrong.
Thanks!

Basically this bug will hit you any time you connect over USB to a device that's not on the same local network.  It's to help the HoloLens/phone teams plugin a device over USB, get a connection via Wifi to it, and then unplug the device while retaining the connection, thus allowing you to rapidly setup multiple devices from a "home base".
We should probably change the default to false. @davidkline-ms , would that break any scenarios on your end?

@hpsin, THAT makes sense. Changing the default wont break scenarios, I would just need to explicitly specify true.
Any thoughts on making the parameter a tristate with the default being "TryToChange"?


CLI update auth causing removal of function environment variables

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
yarn global
If applicable, what version of Node.js are you using?
v16.14.2
Amplify CLI Version
10.2.3
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
auth, function
Amplify Commands
update
Describe the bug
When running the amplify update auth cli command, and selecting the Update OAuth social providers option, some function environment variables and their values are being removed from their respective json configurations
Expected behavior
When updating an OAuth social provider, functions should maintain their environment variables and modules.
Reproduction steps
Using an existing Cognito trigger function with a Google integration (NB - Please let me know if I should expand this to creating the integration/hooks too)

Edit an existing function, using amplify update function
Select the Environment variables configuration option
Enter a variable name, and variable value
Exit from the menu, and confirm the variables have been added to the function parameters. (amplify/backend/function/functionName/functionName-cloudformation-template.json and amplify/team-provider-info.json)
Run the amplify update auth command
Select the Update OAuth social providers option
Select the Google option and proceed
Enter Client ID and proceed
Enter Client Secret and proceed
Run amplify status to see that the Function has an Update operation pending
Run git diff and notice that amplify/backend/function/functionName/functionName-cloudformation-template.json and amplify/team-provider-info.json have had the environment variables removed from them.

GraphQL schema(s)
No response
Project Identifier
d269d4a9oyj3sv
Log output

# Put your logs below this line

Additional information
This project started on v6 of the CLI, and has been migrated up incrementally. I have had this issue from the outset and hoping for some help as I constantly have to check that the files haven't had the env variables removed.
If I am missing anything please let me know!

Hey @milespop :wave: thanks for raising this! I was able to reproduce this issue on the latest version of the CLI using the provided reproduction steps. Thank you for including those details!
Marking as a bug 🙂

I have had this issue for a long time, and it's still present in the latest version (12.10.1). Other than the environment variables, "update auth" for me also removes any additional modules from the list in my PreTokenGenerator's parameters.json. It just leaves the default "alter-claims" in the list. Unfortunately, reverting the changes with git is not sufficient in the case of the environment variables, I have to re-add them through the CLI. I find this quite annoying and dangerous.


Post update hook not executing

Hi,
I have following post update hook configured to setup YCM:
Plug 'Valloric/YouCompleteMe', { 'do': 'sudo apt-get install -y build-essential cmake python-dev \| ./install.py' }

While the ./install.py gets executed it seems the apt-get to install the necessary dependencies is never called.

@helpermethod Hello. Remember that whatever is in the string value of do gets executed on the system shell. I think you should try the following set of commands in your shell to see the difference. The last line is what you want. The first is equivalent to what you asked plug to send.
echo "Hello" | echo "Hello2"
echo "Hello" || echo "Hello2"
echo "Hello" && echo "Hello2"

Hint: The '|' operator is the pipe in most shells, hence the output gets redirected into the second command. Where as || is logical or and '&&' is logical and.

Thank you very much for your explanation, that makes sense.


Adding a duplicate detection measurement

The duplicates measurement, by default, will return the fraction of duplicates contained in the input data.
With the list_duplicates = True flag, it will also list the duplicates and return the list of tuples of (string, count).

Alright, I think we're good!

You probably need to update the second example in the docstring since it now returns a dict instead of list of tuples for the doc tests to pass.


Remove lifetime from wrapper types and impl generics

Context: https://github.com/taiki-e/pin-project/pull/357#issuecomment-2435085549
I'm not worried about the compiler making changes that break the current code in the future since the compiler depends on pin-project-lite, but I do like reducing the generated code by this.
-impl<'pin, T, U> _pin_project::__private::Unpin for Struct<T, U>
+impl<T, U> _pin_project::__private::Unpin for Struct<T, U>
     where
-        ::pin_project::__private::PinnedFieldsOf<
-            __Struct<'pin, T, U>,
+        for<'pin> ::pin_project::__private::PinnedFieldsOf<
+           __Struct<T, U>,
         >: _pin_project::__private::Unpin,
     {}

FYI @danielhenrymantilla

Hmm, it seems lifetime in wrapper type in needed in old rustc.
https://github.com/taiki-e/pin-project-lite/actions/runs/11503119119/job/32019681641
https://github.com/taiki-e/pin-project-lite/actions/runs/11503253973/job/32020114753
error[E0277]: the trait bound `std::marker::PhantomPinned: std::marker::Unpin` is not satisfied
   --> tests/lint/lib.rs:93:5
    |
93  | /     pin_project! {
94  | |         /// Testing enum.
95  | |         #[project = EnumProj]
96  | |         #[project_ref = EnumProjRef]
...   |
112 | |         }
113 | |     }
    | |_____^ the trait `std::marker::Unpin` is not implemented for `std::marker::PhantomPinned`
    |
    = help: the following implementations were found:
              <std::marker::PhantomPinned as std::marker::Unpin>
    = help: see issue #48214
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

Nah, for<'a> doesn't seem to work well with the old rustc in the first place.
https://github.com/taiki-e/pin-project-lite/actions/runs/11503435474/job/32020719422?pr=85

Interesting, TIL. Thanks for trying it out anyways!


Images not showing via username

Images not showing via username.
even your demos not showing images from username and only tag images showing.
Instagram Feed: It looks like YOUR network has been temporary banned because of too many requests. See https://github.com/jsanahuja/jquery.instagramFeed/issues/25
ERROR in your demos
Instagram Feed: It looks like YOUR network has been temporary banned because of too many requests. See https://github.com/jsanahuja/jquery.instagramFeed/issues/25 InstagramFeed.min.js:1:1902

What is the purpose of this issue? I think the error is self-explaining.


Add jitter for starting failover queue

What changed?

Add some jitter for starting failover queue processing

Why?

on domain failover, we will create a failover timer/transfer queue for every shard and all of them will start to load tasks at almost the same time. This caused a spike load and CAS latency in our underlying DB to become very high. As a short-term fix, added some jitter so that those failover queues won't start at the same time.
By default, there's no jitter for failover queue.

How did you test it?

Tested locally

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 125d9567-c41b-4763-9c92-622e180917b7

15 of 29 (51.72%)  changed or added relevant lines in 3 files are covered.
184 unchanged lines in 24 files lost coverage.
Overall coverage decreased (-0.08%) to 56.876%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

service/history/queue/timer_queue_processor_base.go
5
10
50.0%

service/history/queue/transfer_queue_processor_base.go
8
17
47.06%

Files with Coverage Reduction
New Missed Lines
%

service/history/queue/timer_queue_processor_base.go
1
77.92%

client/history/client.go
2
39.33%

client/history/metricClient.go
2
46.37%

common/persistence/executionManager.go
2
76.57%

common/task/fifoTaskScheduler.go
2
85.57%

common/task/weightedRoundRobinTaskScheduler.go
2
88.6%

service/history/execution/mutable_state_builder.go
2
69.6%

service/history/handler.go
2
48.56%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
55.49%

service/history/queue/timer_gate.go
3
95.83%

Totals

Change from base Build 6a863d49-45b7-443d-ad73-af2007961e13:
-0.08%

Covered Lines:
82755

Relevant Lines:
145502

💛  - Coveralls


Set Quotients

would it make sense to port this definition of Set quotients from the Coq lib?
https://github.com/HoTT/HoTT/blob/master/theories/hit/quotient.v
The one in old/ makes use of spheres which seems overkill?

I put in something in /lib/types/SetQuotient.agda. Is it what you wanted? The one in old/ was done without truncation; nowadays truncations are more accepted as an inherent part of defining HITs.

@Saizan I am going to assume the new quotient code is satisfactory. Feel free to re-open.


Create Kubernetes cluster on the local machine

from #1020
After the successful creation of Airy Core, we need to print-out the output for how to access the platform.
Currently we print out:
The webhooks
The API endpoint
Info about how to create the first user.

Definitely part of the requirement here is defining the output. But, to be fair, I think we should start from the way the command UI looks like. Here's some early questions:

We can do providers in two ways (at least I can think of two but probably there's more):

airy create --provider=local --args etc...
airy create local --args etc..
When I thought about this, I assumed I'd like the former more but now that I see them written down I think the latter is better: it's more explicit, no need for funky work on args that are provider dependent, each command gets its own docs/description.

What does the command exactly do? From what I'm reading in #1015 I think there's some confusion about this and lack of clarity (I didn't even think we'd have an airy start command at first as I personally assumed airy create would do the exact same thing that we have now with the bootstrap. after all that's the main goal here: get rid of the bootstrap script in a way we can have multiple providers much more easily)
What's the output? I think we should define this a little upfront. It will also clarify in detail: the steps we have to build, the different responsibilities of each step. I will propose something about this later today. I want to think bout it for a minute and the previous questions are more important

Maybe also adding a link to a docs page that says: horray for installing and running airy. Here are three awesome things you can do with it 🤔 ?

👍 for airy create local. Since the two deployment options are so different it makes sense to also document them in more detail than it would be possible on a flag.
I think it is ok to say Minikube is a requirement for Airy Core and that the users should install it on their own. In case they already have Minikube and are using it for something else they can use the namespace feature.
We should also discuss where the airy.yaml comes into place. We could copy it to the local machine on airy init and ask the user to modify it to their needs before executing the create. This means we should also have a --config flag on the create that you pass the path to the airy.yaml
The next thing we need are the helm charts. I would actually stick with Helm since it does a lot of work for us and can even do more for us with this new way of deploying. For example, we could get the helm charts from the repo directly instead of cloning them to the local machine.

As I understood from the discussion, we split the issues in two big sections:

How do we create the kubernetes cluster (1.1 How do we create it locally, 1.2. How do we create it in AWS, 1.3. How do we create it in GCP, ...)
Once the Kubernetes cluster is there, how do we provision all the airy components, start them one by one and print out the message on how it can be accessed.

I imagined this issue to be only about the 1.1 part. How do we create the Kubernetes cluster locally. As I understood the discussion, talking directly to VirtualBox to create an instance and use Alpine+k3s on top.
In terms of the airy start command, that is a different topic for now. The command which will create Airy Core with all of its components until one can successfully use it is airy create.
About the flag, I vote for having a flag, as it is more clear like that to me. Otherwise, I find airy create aws a bit strange.
airy create --provider=local
airy create --provider=aws
airy create --provider=gcp

Just a note that every different provider will probably require its own flags (example: airy create --provider=aws --aws-profile=prod)

I think now that I can see both proposal on paper, I agree with @ljupcovangelski about the high-level UI. airy create --provider=aws plus aws prefixed args is really nice.
As for creating the cluster locally, I do agree with @pascal-airy that is ok to require them to provide a minikube (technically though, I think we'll ask them to point us to a valid/working kube.conf so we wouldn't even need to depend on minikube. We can suggest to use that in the docs though. And I would because minikube is real nice). Having the local provider working with virtualbox would make the local provider "special" as it's the only one that would require us to create an image so there's that as well. Asking the user to point airy create to a kube.conf is fair enough (I think) and requires a lot less work on our side. Hopefully, we'll make it so easy to run it in the cloud that most people will choose that option anyway.
@pascal-airy raises a good point about the airy.yaml. But I think it's out of the responsibility of the airy create command, at least initially. So I propose this workflow:

airy create creates core according to the provider config provided
the command starts what we think it's good defaults (what we now have as default is good for now)
we write in the docs "use airy.aml" for configuring parts of it

As for the output, I'm thinking we should provide high level step-by-step messages:

⚙ Creating core with provider X
🚀 Starting core with default config (link to the docs for config here)
🎉 Your Airy Core is ready:

link to the api url
link to the ui
link to more docs

Maybe "too fancy" but I'd love to provide a little progressbar next to each message that goes away once the step is completed. It would provide a sense of progress.
As I see it, apart from what I just wrote here in the comments the only missing thing from the description of this issue (so that we can start working on it aka remove the needs discussion label) is a step in the todo list about treafik? As I understand it we don't mention that anywhere but there's no way around it?

* `airy create` creates core according to the provider config provided

Do you mean the kubernetes config perhaps? Because currently airy create doesn't depend on a specific provider.

* we write in the docs "use airy.aml" for configuring parts of it

@pascal-airy if I understand correctly, I like your proposal to do:
airy create --kube-config=kube.conf --config=airy.yaml

At the end of the create command, if a config file is specified we also do config apply

As for the output, I'm thinking we should provide high level step-by-step messages:
* tada Your Airy Core is ready:

  * link to the api url
  * link to the ui
  * link to more docs

For this information we need the loadbalancer, which is provider dependent.

As I see it, apart from what I just wrote here in the comments the only missing thing from the description of this issue (so that we can start working on it aka remove the needs discussion label) is a step in the todo list about treafik? As I understand it we don't mention that anywhere but there's no way around it?
Included.

I don't understand what do we want exactly, do we want to leave the option for different local Kubernetes deployments? I thought that airy create --provider=local is VirtualBox+k3s.

So no I do mean what I said about airy create, from the perspective of the user the details don't matter. airy create creates the core instance "somewhere in the provider".
I don't think it makes sense to mix create and configuration. At least short term. It would also make it harder for people to test things anyway. And the airy config apply is very fast/friendly anyway.
About the output being provider dependent... that's kind of always true. Especially if we want to provide a progress bar. What I wanted to focus on is the formatting/style of the output.
As for the local provider, we should have an issue where we discuss how we do this. (I don't think we should rely on virtualbox, as @pascal-airy said we can get away by asking the user to point airy create to their local cluster via minikube)

I agree for the configuration part. So we would have a two-step process.
airy create... (generates kube.conf file at the end)
airy config apply --kube-config=kube.conf --config=airy.yaml

👍 I really like the way the @lucapette talked about this

The airy command only speaks kubernetes language

Having said that, the output of airy create is a kube.conf file which is stored locally (maybe it points to a cloud provider, but the conf file is always stored locally). So why do we need a airy config apply ?
Isn't airy config apply a step of the create command?

👍 I really like the way the @lucapette talked about this

The airy command only speaks kubernetes language

Having said that, the output of airy create is a kube.conf file which is stored locally (maybe it points to a cloud provider, but the conf file is always stored locally). So why do we need a airy config apply ?
Isn't airy config apply a step of the create command?

I think it can be but it doesn't have to be. And my position short term is "let's ignore the config of the instance itself" as it brings a lot of "catch-22" kind of problems into the conversation (things like: should you have a config already somewhere? does the CLI need to "template it" for you? the UX then looks strange as you first configure then create?). So I'm not saying we should never do this, I'm saying let's ignore the problem and refine it once we have the infra of the airy create command done. That way we'll also have a more informed opinion about how to go with creation vs configuration of the instance

I've update https://github.com/airyhq/airy/pull/1084

Default provider is aws
kubeconfig parameter is hidden
Command "speaks" kubernetes

done in #1240


Make it possible to force GLES usage on Linux

Have you verified that this actually works? For example, there's another instance of this in device rs in the same directory.

Yeah, I'll publish 0.9.6 once this merges.


Mayastor documentation request: minimal realistic hardware requirements

From testing mayastor on a kubeadm created cluster, I have observed that by default, the nodes dedicated to storage bumped memory usage with close to 5GB extra ram and at least one core cpu over 90% of the time used. This is also documented by Mayastor, as suggest even dedicating 2 cores for each storage node.
As observed with other addons, and really enjoying this, I would like to suggest the official team if they can do some initial testing so some MicroK8S suggested minimal requirements would be documented for the addons.
I'd like to remind, that Mayastor recommends 4GB ram per storage node and minimal 1 core dedicated to it.
Probably with some tweaks, MicroK8S might provide Mayastor for smaller deployments, which would be enjoyable.
There is another mention on Mayastor 1.0 release that without minimal 3 nodes Mayastor will not run. Will this be in the case of the MicroK8S same?

Addon enabled, Mayastor started only:

Starting a DB stateful and an application deployment with 2 volumes added using mayastor-3 storage class, did not add any ram usage extra, I saw only expected from MySQL and WordPress pods the extra usage.
I only think that as more volumes get claimed, Mayastor will slightly increase a little the ram usage.
One full core being hammered 99% of the time can be seen clearly from the screenshot.
Personally, I would not deploy it in MicroK8S with a cluster under 3 nodes with 16GB of ram (to be OK with ram needed for apps) and where I can't ensure I have enough cores.

Thank you for this work @madalinignisca
This has been in our plans for some time.

I would also highlight in docs that deploying Mayastor should be done only on virtual servers with dedicated cpu cores, or, like most public cloud providers do, users will see their instances terminated in a few hours, max a few days. doing that load on a core breaks terms of usage on almost all public cloud providers, including AWS (example Mayastor on AWS Lightsail would get nodes terminated in ~24h, and on T* type instances would increase cost above dedicated core instances or simply make cluster unusable if no limit is false).
PS: I guess Mayastor doesn't fit really in the idea of Micro...


Integration with react-redux?

Hi, I've got a question regarding reactstrap and react-redux.
I have the following code
https://stackblitz.com/edit/reactstrap-in7z9q?file=App.js
I want the setoption action to fire upon clicking the "Change option" button but I can't seem to get the onClick prop right. Could anyone suggest a fix?

Hey @07oct2018 ,
I'll try my best to help.
Here's some code to fix the error in your setup:
index.js
import React from 'react';
import ReactDOM from 'react-dom';
import App from './App.js'
import { createStore } from 'redux'
import { Provider } from 'react-redux'

const reducer =
  (state, action) => {
    console.log("STATE",state, action);
    switch (action.type) {
      case 'SET_OPTION_1':
        return {
          ...state,
          option_1: action.value,
        };
      default:
        return state;
    }
  }

const store = createStore(
  reducer,
  {option_1: 'some_value'}
);

const render = () => ReactDOM.render(
  <Provider store={store}>
  <App />
  </Provider>,
  document.querySelector('#root')
);

render();

app.js
import React from 'react';
import ReactDOM from 'react-dom';
import { connect } from 'react-redux';
import { Button } from 'reactstrap';

const MapDispatchToProps = (dispatch) => ({
  setoption : a => dispatch({type: 'SET_OPTION_1', value: 'new_value'})
})

const MapStateToProps = (state) => ({
  option_1 : state.option_1
})

export class App extends React.Component {
  render () {
    return (
      <Button onClick={ () => this.props.setoption() }
      >Change Option</Button>
    )
  }
}

export default connect(MapStateToProps, MapDispatchToProps)(App)

I hope it helps.

Thank you for the advice @TheSharpieOne , I only recently started learning React & Redux and I'm not yet familiar with usage patterns.


Distinguish changes that were made by support in application timeline

Context
Changes are shown to have been made by "System".
Changes proposed in this pull request
In the interest of transparency, change this text to "Apply support" where the change was made by support or the rails console.
Guidance to review
Straightforward hopefully
Link to Trello card
https://trello.com/c/wsT8mcxt/3483-in-the-application-timeline-ascribe-actions-taken-by-support-users-to-apply-support-or-equivalent
Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

I'll raise a separate card to make the activity log do the same sort of thing. They differ currently and the work can be done in a separate PR


feat: allow cors header to be excluded from request headers

Summary
A change was introduce in v8.7.0 that enforces cors in request headers by default. There isn't a way to remove it for users who do not need it. This change allows cors to be removed from request headers by passing '', null, undefined to config.headers['Cross-Origin-Resource-Policy'] on init.
CODE SAMPLE
amplitude.getInstance().init(<API_KEY>, <USER_ID>, {
  headers: {
    'Cross-Origin-Resource-Policy': undefined,
  }
});

Checklist

[x] Does your PR title have the correct title format?
Does your PR have a breaking change?:  No

Thanks for addressing this @kevinpagtakhan and @ajhorst!


Don't skip the first pcodetest artifact if target directory does not exist.

As per the title, the pcodetest artifacts' build script would not copy the first binary if the target directory did not exist on the first run.
Incidentally, this script still depends on Python 2.x, which has been EOL'd 18 months ago.  I've had to port the build scripts to Python 3.7 - should I submit a PR with that as well?

Thanks @agatti ! Please submit a PR for the port to Python 3

PR sent - this can probably be closed since #4307 contains the fix this PR is about...


Deprecate systems and resources internal namespaces

Deprecated

Removes the internal namespaces systems and resources in @pixi/core

Context
This is a followup to discussion in #6849. This change is consistent with #6681 and #6328 and has the added benefit of reducing our api-extractor complexity.

Codecov Report

Merging #6857 into dev will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               dev     #6857   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          671       671
=========================================
  Hits           671       671

Continue to review full report at Codecov.

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

Yeah, I really just want to make a v6 release to remove all deprecations.


Delete Inbox Item

I noticed the Instagram PHP has the deleteItem for inbox, could you implement this? or how do you connect the dots so i can do it my self and post it here?
this is what the other API has
public function deleteItem(
$threadId,
$threadItemId)
{
return $this->ig->request("direct_v2/threads/{$threadId}/items/{$threadItemId}/delete/")
->addPost('_uuid', $this->ig->uuid)
->addPost('_csrftoken', $this->ig->client->getToken())
->setSignedPost(false)
->getResponse(new Response\GenericResponse());
}

You could create your own class extending InstagramPostRequest<ResultClassHere> and add the post fields yourself.

Example of they abstract requests ^ (errors are because I don't use Lombok, but you should get the point)

Thanks buddy, i'll look into this.

any idea why I am getting wrong permission? i've tried many different map items and same error

nvm found a way decline the thread, instead of deleting items. works for what I was trying to do. below is the code for anyone wanting to use it.
`/**

Copyright (C) 2016 Bruno Candido Volpato da Cunha<EMAIL_ADDRESS>
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/
package org.brunocvcunha.instagram4j.requests;

import com.fasterxml.jackson.databind.ObjectMapper;
import lombok.AllArgsConstructor;
import lombok.SneakyThrows;
import lombok.extern.log4j.Log4j;
import org.brunocvcunha.instagram4j.requests.payload.StatusResult;
import java.util.LinkedHashMap;
import java.util.Map;
/**

Decline Inbox Request, can be use for pending and inbox item

@author Anthony  Rodriguez

*/
@AllArgsConstructor
@Log4j
public class InstagramDeclinePendingInboxRequest extends InstagramPostRequest {
private String threadId;

@Override
public String getUrl() {
    return "direct_v2/threads/"+threadId+"/decline/";
}

@Override
@SneakyThrows
public String getPayload() {

    Map<String, Object> DeclineInbox = new LinkedHashMap<>();
    DeclineInbox.put("_uuid", api.getUuid());
    DeclineInbox.put("_uid", api.getUserId());
    DeclineInbox.put("_csrftoken", api.getOrFetchCsrf());
    ObjectMapper mapper = new ObjectMapper();
    String payloadJson = mapper.writeValueAsString(DeclineInbox);

    return payloadJson;
}

@Override
@SneakyThrows
public StatusResult parseResult(int statusCode, String content) {
    return parseJson(statusCode, content, StatusResult.class);
}

}
`


fix(Snowflake): Stricter typing

Please describe the changes this PR makes and why it should be merged:
Minor Snowflake typing changes to make it more stricter

We've done this before but it was reverted due to complaints 😓


Run metrics e2e tests in single-node environments only

What type of PR is this?
/kind flake
What this PR does / why we need it:
This is meant to remove some of the flakiness in our tests. We make the
assumption that our vanilla tests are running in single-node mode only,
so we take advantage of that fact and set a boolean that indicates that
it's a single-node test environment.
Note that this also does changes necessary for the ubuntu setup to
run the Seccomp tests.
Which issue(s) this PR fixes:
None
Does this PR have test?
Yes, the metrics e2e tests
Special notes for your reviewer:
Does this PR introduce a user-facing change?
NONE

Codecov Report

Merging #1059 (49c8f85) into main (ab951bc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1059   +/-   ##
=======================================
  Coverage   50.09%   50.09%
=======================================
  Files          42       42
  Lines        4779     4779
=======================================
  Hits         2394     2394
  Misses       2299     2299
  Partials       86       86

/test all

/retest

Since @JAORMX is on vacation per his Slack status, I took the liberty of rebasing his patches and fixing the issue @pjbgf brought up. There are no other changes.


Fixed Java getStatistics binding.

Fix #268.
The getStatistics for both the master and the outstation used to return a LocalRef that was deleted when the native call returned, causing undefined behaviour on the Java side. Now, the reference is promoted to a global reference that will be garbage collected by the JVM.
I also added a test case to reproduce the issue.

Not sure if I should make another bug for this, but this same issue will pop up in com_automatak_dnp3_impl_ChannelImpl.cpp. Also as an effect of the test for this fix the maven build will fail because it is the only test which makes use of the dll and the java.library.path is not set for the maven-surefire-plugin. What I did to make it work for mine was add this
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>${surefire-plugin.version}</version>
<configuration>
 <argLine>-Djava.library.path=C:\PathToRepo\build\Release</argLine>
 <includes>
   <include>**/*.class</include>
 </includes>
 <reportFormat>brief</reportFormat>
 <useFile>false</useFile>
</configuration>


Enable CD Permissions for plugin-feishu-notification.yml

Link to GitHub repository

https://github.com/jenkinsci/feishu-notification-plugin
When modifying release permission
If you are modifying the release permission of your plugin or component, fill out the following checklist:

### Release permission checklist (for submitters)
- [ ] The usernames of the users added to the "developers" section in the .yml file are the same the users use to log in to [accounts.jenkins.io](https://accounts.jenkins.io/).
- [ ] All users added have logged in to [Artifactory](https://repo.jenkins-ci.org/) and [Jira](https://issues.jenkins.io/) once.
- [ ] I have mentioned an [existing team member](https://github.com/orgs/jenkinsci/teams) of the plugin or component team to approve this request.

When enabling automated releases (cd: true)
Follow the documentation to ensure, your pull request is set up properly. Don't merge it yet.
In case of changes requested by the hosting team, an open PR facilitates future reviews, without derailing work across multiple PRs.
Link to the PR enabling CD in your plugin

### CD checklist (for submitters)
- [x] I have provided a link to the pull request in my plugin, which enables CD according to the documentation.

### Reviewer checklist
- [ ] Check that the `$pluginId Developers` team has `Admin` permissions while granting the access.
- [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
- [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently `@Wadeck`) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it.

The PR template is supposed to be filled out, not to be deleted.

@721806280 Are you still interested in enabling CD? Please address my comment above.

@721806280 Are you still interested in enabling CD? Please address my comment above.

updated

@721806280 Are you still interested in enabling CD? Please address my comment above.

updated

You didn't provide such a link.

updated

updated

The plugin is not incrementalified, nor is there a PR linked to review. Please take a look at the documentation which files you'll need to modify.


Concat & merge for DLT

Would be super good to have concat and merge feature for DLT also and probably for any type of data, which required encode/decode actions.

Duplicate #943


false positive from strings.Split

strings.Split is guaranteed to return a non-nil slice with at least one element, so alerting from calling that is a false positive.
/Users/adam/code/src/github.com/moov-io/base/telemetry/attributes.go:84:19: error: Potential nil panic detected. Observed nil flow from source to dereference point:
	-> strings/strings.go:242:10: literal `nil` returned from `genSplit()` in position 0
	-> strings/strings.go:312:45: result 0 of `genSplit()` returned from `Split()` in position 0
	-> telemetry/attributes.go:84:19: result 0 of `Split()` sliced into

In this case nilaway fails to detect that genSplit is always called from Split with n == -1 so line 242 can never run.
https://cs.opensource.google/go/go/+/refs/tags/go1.21.4:src/strings/strings.go;l=312
https://cs.opensource.google/go/go/+/refs/tags/go1.21.4:src/strings/strings.go;l=241

@adamdecaf: ACK. Thanks for reporting this issue (and @dolmen for providing more context). We will fix this soon.
On a side note, you may want to add the code path of your repository to the include list to have NilAway only analyze first-party code (more details in wiki). This way NilAway won't analyze the standard library, but apply optimistic defaults for all external code. This would have the benefit of restricting the reported errors to only your code, more performance and memory efficient (by skipping analysis of external code). In the context of the issue, this would mean that the output of strings.Split would optimistically be considered to return a nonnil value, and no error would be reported.
Having said that, of course this issue points to a more general code pattern that NilAway should support, and we'll add a fix for it. :)

I think, this is the case with the following code:
https://go.dev/play/p/hvrg3U0Y3aL


Wix installs to Program FIles but doesn't give the program elevated privileges

When using Wix to create an installer, the installer will put the executable into Program Files, but the executable doesn't have access to Program Files, unless the user always runs the program as an admin. Thus, creating a log file just fails. Also, when uninstalling, the log file is left behind.
How could I specify to install to a location which is not "protected" (preferred), or give the program elevated privileges? Sorry, I'm really new to making installers.

Unfortunately the Wix installer at the moment is limited to perMachine installation, which means the default location will be "ProgramFiles". However, we provide an alternative installer NSIS which can be either perMachine or perUser and the perUser option will default to %APPDATA% directory.
You can also choose to give your program elevated privileges but that depends on how you build your executable, if using Rust, you can use embed-manifest crate https://docs.rs/embed-manifest/latest/embed_manifest/manifest/struct.ManifestBuilder.html#method.requested_execution_level


Colab Specific: RuntimeError: inverse_cuda: For batch 0: U(17437184,17437184) is zero, singular U.

Just leaving this here so it's known about (and many others are aware of this problem). This is currently a problem with Magma, Google Colaboratory and the transforms, especially TensorPoint's among others. This problem is currently being worked on here: https://github.com/pytorch/pytorch/issues/29096
You can reproduce this by trying to do the Image Regression problem from the course in Google Colab.
I will update when it's working again. Sylvain if you want this to be closed (instead of left open) go ahead, but I felt having this here would be easier than a million questions opening up from Colab users :)

No worries, thanks for investigating the issue!

The fix is done, should come out with Colab version 1.3.1

This issue has been solved. Recommend requiring torch 1.3.1 as this contains the fix


Automated Package Upgrade

:tada: This PR is included in version 25.3.93 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add destroy alias for connection

To make connections compatible with @rbxts/maid without additional workarounds.
I was trying to migrate from @rbxts/signal, but ran into errors where my maids would not accept the signals created by this package: [Maid.GiveTask] - Gave table task without .Destroy. Adding this alias would make it easier to migrate to this package.

@Scyfren published in v2.1.0


gehrkin-lint thinks that karate .feature files should be json

Why does gehrkin lint think that a karate .feature file should be in json format?  The first line in all of our .feature files is a comment line with copyright and gehrkin lint thinks this is an error:
2023-07-10 23:11:10 [INFO]   Linting [GHERKIN] files...
2023-07-10 23:11:10 [INFO]   ----------------------------------------------
2023-07-10 23:11:10 [INFO]   ----------------------------------------------
2023-07-10 23:11:10 [INFO]   ---------------------------
2023-07-10 23:11:10 [INFO]   File:[/github/workspace/api/karate/_config.feature]
2023-07-10 23:11:10 [ERROR]   Found errors in [gherkin-lint] linter!
2023-07-10 23:11:10 [ERROR]   Error code: 1. Command output:
------
undefined:1
# (C) Copyright 2023 Hewlett Packard Enterprise Development LP
^

SyntaxError: Unexpected token '#', "# (C) Copy"... is not valid JSON
    at JSON.parse (<anonymous>)
    at Object.getConfiguration (/node_modules/gherkin-lint/dist/config-parser.js:28:23)
    at Object.<anonymous> (/node_modules/gherkin-lint/dist/main.js:26:29)
    at Module._compile (node:internal/modules/cjs/loader:1275:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1329:10)
    at Module.load (node:internal/modules/cjs/loader:1133:32)
    at Module._load (node:internal/modules/cjs/loader:972:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
    at node:internal/main/run_main_module:23:47

Node.js v19.7.0

This relates to your .gherkin-lintrc file, not your feature.
You cannot have comments in JSON. The format does not natively support it.


Transparent image infotext + saving support

Title. Transparent images are currently passed to the UI as a uint8 array where Gradio handles it. This properly adds infotext to the image and also adds the option for a user to save these images (in addition to the checkered-patterned image currently saved).

Works! 😊👍
It would be helpful if the checkbox were ticked by default. It took me some time to realize I needed to search for it in the settings. Since the transparent image variant is the one primarily used, I don't see value in saving only the checkerboard version anyway. Enabling the transparent image option by default seems like a sensible choice to me. What do you think?

has some weird blurry efffect if save format is set to webp, any ideas?
Save as PNG

Save as WEBP (and converted to PNG for uploading to GitHub)

An option to not save the "checkerboard" preview would be appreciated. This is useless content to output except for a preview purpose, I don't think it should be saved at all personally, but if someone has a use for it, an option would be alright.

During batch generation when the '*-transparent.png' copy is saved, it has the incorrect seed in the info text.

como la puedo usar?

Thanks for this work ! ヾ(◍°∇°◍)ﾉﾞ
Can someone please describe in detail the steps to resolve the issue? As a user with no programming foundation, how should I operate? (I tried replacing the .py file with the same name, and although the checkbox appeared, the image generated by layerdiffuse became with a solid black background, which seemed worse)


[Feat] Add support for Plotly Dash

Hi maintainers,
Hope this message finds you in good health. I wanted to reach out to ask if it's possible to add support for Plotly Dash. It's useful for creating interactive web-based dashboards but can benefit from all the data exploration part.
Thanks

Hi all,
customers using plotly apps would love this enhancement and data science teams as well.
Thanks for your great library,
Ilona

+1

+1

Same here, it'd be super useful

And allow to export plotly code... That will be awesome! 👌

Thoughts update:
I do believe that allowing graphic-walker/pygwalker to support multiple charts lib is a great idea. Technically, we need to implement a parser layer to transform graphic-walker DSL into other chart code/specification. It's a cool engineering abstract. I will be happy to implement it.
But, I am still not sure why people need a different chart library for visual exploration. I don't find there is much benefit of ploty than vega/vega-lite. Hope someone can share your demands or insights here.

@ObservedObserver
To my opinion, with Plotly Dash you can do much more than visual exploration. It is fast and easy to build a whole Web-application with a lot of different features.

@ObservedObserver , thanks for checking this out. As @IloBe mentioned, the use case is the same as Streamlit. The purpose is not to use Plotly for the charts but more to embed Pygwalker in a Dash (plotly) app (see examples here).

Update: Now you can use pygwalker as a component in Plotly Dash, check this document: Use PyGWalker with Plotly Dash

For hosting pygwalker as a web app (or dashboard), you can also use:

Streamlit: https://docs.kanaries.net/pygwalker/use-pygwalker-with-streamlit
Gradio: How to Use PyGWalker with Gradio
shiny-python: How to Integrate PyGWalker with Shiny-Python

Or even flask or django if you are familiar with web development.

Hey @ObservedObserver , I really looking forward to using it with dash but the code provided is returning the error below when I try to interact with pygwalker.

Session info --------------------------------------------------------------------
Platform: Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-glibc2.35 (64-bit)
Python: 3.12
Packages ------------------------------------------------------------------------
dash-dangerously-set-inner-html==0.0.2
dash==2.18.1
pygwalker==<IP_ADDRESS>


[FEATURE] Allow custom naming of nodes

Description of the change
Introduce variables into the sample config to allow for custom node-names. Additionally, a function for optional envar to warn that it is not set, but not break --verify.
Benefits
Instead of the hostnames of all nodes being "k3s-#" users are now able to set their own node hostnames in the configuration.
Possible drawbacks
I did my best to test backwards compatibility, it should work as intended with existing configurations, however this PR introduces the following variables into the config sample, which were not present previously.
export BOOTSTRAP_ANSIBLE_DEFAULT_CONTROL_NODE_HOSTNAME_PREFIX="k8s-"
export BOOTSTRAP_ANSIBLE_DEFAULT_NODE_HOSTNAME_PREFIX="k8s-"

export BOOTSTRAP_ANSIBLE_HOSTNAME_0=""

While it expects these to be set, it is able to handle cases where any or all of them are unset, to maintain backwards compatibility.
Additionally, the function introduced in configure.sh "_has_optional_envar" duplicates the existing "_has_envar" function but doesn't exit if the variables are unset.
Applicable issues

implements Feature Request #165

Additional information
Special thanks to @onedr0p for helping me through Bash in the Discord.

One thing I see potentially going wrong is that people set these to the same values.
export BOOTSTRAP_ANSIBLE_HOSTNAME_0="test"
export BOOTSTRAP_ANSIBLE_HOSTNAME_1="test"
export BOOTSTRAP_ANSIBLE_HOSTNAME_2="test"

Tested and merged, thanks @enchantednatures !


Add CompletionStage assertion

Summary
AbstractCompletableFutureAssert has methods to run assertions on CompletableFutures.
However, in any given unit test, the given CompletableFuture might not have completed yet, causing the test to be brittle. The exception report can be quite confusing because between the test  failure and the printing of the test error, the future might complete. So even a test asserting isDone() can fail with a message showing a done future.
Coding around this is ugly. Would be real nice if assertj had some waiting (with timeout, with default timeout) function embedded.
Also would be nice if this would work with CompletionStages as well.
Something like
CompletionStage<Foo> fooStage = getFoo();
assertThat(fooStage).completesWithin(1000).hasFailedWithThrowableThat()

Note: I think the awaitility library could also help, but so far did not use it. Could be this is better solved by using both awaitility and assertj.

@tkruse that is good feedback thanks.
I have created an issue for the confusing error (https://github.com/joel-costigliola/assertj-core/issues/1011) it would be great it you could provide a test case and a better error message if you think it is needed ?
I think awaitility is great but AssertJ could provide a better future assertions out of the box and leave awaitability for advanced usage.

I have also renamed this issue to focus on CompletionStage.
Could you elaborate a bit more on what assertions you would like to see in CompletionStage assertions ?

thanks for cleaning up my mess. For CompletionStage, I'd expect the same assertions as for CompletableFuture, I guess, since the latter implements the former. I'll work on reproducing what I see in my project as a PR

In general I would probably change the most current asserts of AbstractCompletableFutureAssert to first check that the future was completed, before asserting anything else. Because most other asserts work on the assumption of completedness.
Then maybe all those methods could be deprecated, because developers should never write tests like that (except maybe for isNotDone());
Then I would introduce an intermediate Class CompletedFuture that captures the result of completion after wait. It may contain the result, the exception, or an indication of timeout.
With that, I can imagine a fluent chain like:
CompletionStage<Foo> fooStage = getFoo();
CompletedFuture<Foo, Throwable> completed = assertThat(fooStage).completesWithin(1000);
completed.hasFailedWithThrowableThat()

Then I would change the interface of most methods to allow for any CompletionStage, and in the asserts starting with something like:
if (!actual instanceof CompletedFuture) {
    actual = actual.toCompletedFuture();
}

(not literally, consider this psuedo-code).
Note I would also suggest checking how Google Truth does things. I have not checked yet myself.

For google truth, maybe also see this
https://github.com/google/mug/blob/master/core/src/test/java/com/google/mu/util/FutureAssertions.java

Adding one more comment / feedback:

hasNotFailed() doesn't join so job may not be complete (passes if job is incomplete)
hasFailedWithThrowableThat() joins so no need to care about unfinished job

Extending the API with wait methods could also include making methods more consistent (or have better naming) about the wait and join behavior


Despite installing it, it doesn't install

I click to install this plugin.
From the console message It looks like it is installing
But when I open the settings it does not show
and the plugins section shows it wasn't installed.

@madmax2 can you copy/paste the console message when you tried to install this plugin?
Also if you can ssh to your Raspberry Pi, can you run pip list | grep OctoPrint-Anywhere and let me know the output of it?

@kennethjiang
Console message
https://pastebin.com/VfDAAhPY
I am not using raspberry pi, I installed octoprint on windows.
If the command you posted is to check if the folders of octoprint-anywhere exists, then it does show in explorer.
I can see there is 2 folders exists in C:\OctoPrint\venv\Lib\site-packages
-octoprint_anywhere
-OctoPrint_Anywhere-0.2.1-py2.7.egg-info

I have not tested my plugin on Windows and I guess that's why you ran into issues.
From the log file it seems that my plugin was indeed installed successfully. I'm 99% sure the reason why it doesn't show up in OctoPrint because of some errors during OctoPrint startup.
If you know how to get OctoPrint log file, please do so and send it to me  at kenneth dot jiang at gmail dot com . Otherwise I'll love to do a quick skype/google hangout chat with you to figure out what went wrong.

Closing it now due to lack of activities. Let me know if you still experience problems @madmax2


with slider but not with rows

@subhadeepchowdhury41 please write better and clearer commit messages next time

@subhadeepchowdhury41 always try to run "npm run build" before committing also please solve this.

Resolve the build errors

Resolve the conflicts and commit the changes


invalid link

The link for GitStatusState above (#9 in this section https://docs.microsoft.com/en-us/azure/devops/repos/git/create-pr-status-server?view=tfs-2018#post-status-to-prs) is no longer valid.
It should now point to
https://docs.microsoft.com/en-us/rest/api/vsts/git/pull request statuses/get?view=vsts-rest-4.1#gitstatusstate

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e8f48d8a-33fb-9f6d-1db1-4cccb5b987d9
Version Independent ID: 3e18fcbf-331d-9de2-62ae-c4e7c888cc48
Content: Create a pull request status server with Node.js - Azure Repos
Content Source: docs/repos/git/create-pr-status-server.md
Product: devops
GitHub Login: @mmitrik
Microsoft Alias: mmitrik

@jgillette Thanks for letting us know, I have merged the related PR to fix this.


Can't get colormap to work properly

I'm trying to make a joyplot and when I set colormap=cm.autumn_r , my plot only uses the first color in the colormap.  I wanted to use cm.tab20c and I eventually got it working by hacking the _get_color function to return colormap(i % len(colormap.colors)) .  I don't think this is the right general solution but I'm not sure what to fix before submitting a pull request.  Any ideas what might be going wrong?  I think there might also be some weird interaction between gradient and named-color colormaps too.
Also, this package is amazing!  Thank you so much for putting it together.

Hi! Could you include a minimal working example? I can't reproduce the issue.
Note that your fix would only work with what matplotlib calls "qualitative colormaps" (see here).
Continuous colormaps (sequential, diverging) don't have the "colors" attribute. Right now the colormap is called with a value between 0 and 1. That should work for all kinds of colormaps, continuous or not.
If the number of subplots is <= the number of available colors, that's what you should get (this is created with cm.tab20c):

The only issue I see is that you might get repeated colors with qualitative colormaps that have a smaller number of colors with respect to the number of subplots. E.g., with cm.tab10, you can get something like this:

which is probably undesirable.

Hello,
I ran into the same problem while trying to run on Python v2.7.13. I posted it to Stack Overflow and was presented a work-around (https://stackoverflow.com/questions/46717394/demo-of-joypy-joyplots-in-python-not-working). It's the addition of from __future__ import division to the top of joyplot.py. Obviously, the intention of this project isn't to support every version of Python, but this hack allows me to use this awesome package!

The suggestion proposed in stackoverflow makes sense. I'll add the required imports so that the next release works also in python 2.7.

Hi @leotac
I have an issue with using the colormaps when the hist=True.
When using histograms instead of the density estimators, the colormap argument is completely ignored.


mr merger

[x] I have signed the Contributor License Agreement.
[x] This pull request is related to an issue.

Microsoft Reviewers: Open in CodeFlow

Close with reason: PR modifies no files;


Fixes gh-898

If HikariDataSource bean gets AOP-proxied more than once, the spring-cloud rebind operation doesn't treat it as never-refreshable.

@ovgusev Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@ovgusev Thank you for signing the Contributor License Agreement!

@ovgusev, thanks for submitting this PR. Since this code is also being used in the Hoxton release train, I'm going to cherry-pick your commit directly to 2.2.x to get it out in the upcoming Hoxton release, and also move the changes under the existing method signature as @ryanjbaxter has suggested.

Closing with b628338e54f638aee1913956c154a73a435e52df.


i am still just walk

2016-08-07 10:40:41,478 [PokemonGoBot] [INFO] [bot_start] Starting bot...
2016-08-07 10:40:41,869 [CollectLevelUpReward] [INFO] [level_up_reward] Received level up reward: []
2016-08-07 10:40:41,870 [IncubateEggs] [INFO] [next_egg_incubates] Next egg incubates in 2.30 km
2016-08-07 10:40:43,056 [FollowSpiral] [INFO] [position_update] Walking from (-37.81777346115879,<PHONE_NUMBER>2690673, 0) to (-37.81777346115879,<PHONE_NUMBER>2690673, 0) (0.0 m)
2016-08-07 10:40:43,832 [FollowSpiral] [INFO] [position_update] Walking from (-37.81777346115879,<PHONE_NUMBER>2690673, 0) to (-37.81714226703499,<PHONE_NUMBER>2690673, 0) (70.1855701193 m)
2016-08-07 10:42:13,033 [FollowSpiral] [INFO] [position_update] Walking from (-37.81714226703499,<PHONE_NUMBER>2690673, 0) to (-37.81714226703499,<PHONE_NUMBER>890661, 0) (65.6489158403 m)
2016-08-07 10:42:44,284 [FollowSpiral] [INFO] [position_update] Walking from (-37.81714226703499,<PHONE_NUMBER>890661, 0) to (-37.81777346115879,<PHONE_NUMBER>890661, 0) (70.1855701193 m)
2016-08-07 10:43:20,897 [FollowSpiral] [INFO] [position_update] Walking from (-37.81777346115879,<PHONE_NUMBER>890661, 0) to (-37.818404655282585,<PHONE_NUMBER>890661, 0) (70.1855701193 m)
2016-08-07 10:43:57,665 [FollowSpiral] [INFO] [position_update] Walking from (-37.818404655282585,<PHONE_NUMBER>890661, 0) to (-37.818404655282585,<PHONE_NUMBER>2690673, 0) (65.6477931638 m)
2016-08-07 10:44:30,091 [FollowSpiral] [INFO] [position_update] Walking from (-37.818404655282585,<PHONE_NUMBER>2690673, 0) to (-37.818404655282585,<PHONE_NUMBER>6474737, 0) (65.6477931638 m)
2016-08-07 10:44:56,639 [FollowSpiral] [INFO] [position_update] Walking from (-37.818404655282585,<PHONE_NUMBER>6474737, 0) to (-37.81777346115879,<PHONE_NUMBER>6474737, 0) (70.1855701193 m)
2016-08-07 10:45:28,543 [FollowSpiral] [INFO] [position_update] Walking from (-37.81777346115879,<PHONE_NUMBER>6474737, 0) to (-37.81714226703499,<PHONE_NUMBER>6474737, 0) (70.1855701193 m)
2016-08-07 10:46:01,242 [FollowSpiral] [INFO] [position_update] Walking from (-37.81714226703499,<PHONE_NUMBER>6474737, 0) to (-37.81651107291119,<PHONE_NUMBER>6474737, 0) (70.1855701193 m)
OS:
Git Commit: 38c2c6ccb5f3896bdb5ad5398e6a5dddf98e19b8
Python Version:Python 2.7.12

That's because the master branch has not yet added support for the new API. Simply wait until the bot has been updated.

the same

please wait for new PR.

when can i use it ,without bot i wanna die

@GucciChen well you can always create another bot with new API.

@GucciChen or go outside until bot is done.


[Backport-v2.2-branch] Bluetooth: controller: split: correct timing calculation in PKT_US

Fixes #23482
A bug in the PKT_US resulted in wrong calculations for the 2M phy since the preamble size was incorrect. This results in reduced throughput since data that should fit in one packet was split in two packets.
Fixes the bug, verified on EBQ.
Also adds some defines for improved readability.
See also PR #23557 which is for the master branch
Signed-off-by: Andries Kruithof<EMAIL_ADDRESS>

@carlescufi Please advise on what more info is required

@carlescufi, is this still waiting for approval?

@carlescufi, is this still waiting for approval?

No, this is in the Ready column of the Backports project. This means that it can be merged at any time, but I will leave it to @jhedberg to decide when.

@carlescufi, is this still waiting for approval?

No, this is in the Ready column of the Backports project. This means that it can be merged at any time, but I will leave it to @jhedberg to decide when.

Fair enough. The sooner the 2.2 backports are merged, the sooner we will start doing serious testing on the branch.


enabling TS strict compiler flags & resulting refactorings

This PR bundles work started in parallel, but related to #88 - a global enabling of TS strict compiler flags. Current status:

[x] update all packages
[ ] verify/update tests
[ ] re-enable strictNullChecks flag (currently/temporarily disabled, I do see the value, but not entirely sure I want to 100% support this everywhere)

So far I've updated packages in topological order, by repeatedly running lerna run build:es6 from the repo root. That build command will eventually succeed (again), but currently bails out on whatever is the next package still needing TLC/refactoring...

Current status:

all packages are updated/refactored and can be built again
updated tests in first batch of packages (~15 pkgs)
updated above TODO list to reflect these updates

All packages are now done & build successfully.


[fix] close file after checking error in http backend

Codecov Report

Merging #71 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master      #71   +/-   ##
=======================================
  Coverage   41.23%   41.23%
=======================================
  Files           3        3
  Lines         742      742
=======================================
  Hits          306      306
  Misses        400      400
  Partials       36       36

Impacted Files
Coverage Δ

http_backend.go
26.92% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

What does this pr fix?

@asciimoo updated PR description.


Change the Position of Cursor

Hello @JiHong88 ,
Is there any way to move the position of the cursor (start/end/between) and select the range of data from the editor with given properties?

@sawanmakwana Editor has are functions related to "range".
setRange
getRange
getSelection
getSelectionNode ...

Is it available in the react version of this editor?
bcoz mkhstar asked to put the question here...
Thanks!

@sawanmakwana The "suneditor-react" has no return object. : (
You can use the "suneditor" to create your own components in React.


Widget.right binding does not work as expected when width changes after being positioned.

Edit:
Originally, I created this issue regarding Labels with size bound to texture_size. But this issue affects any widget where you bind its right property but then its width changes after being positioned. Instead of the widget's right side staying fixed and x changing, x stays the same and the value of right changes (x + width). @matham found that the same problem happens with a Widget in a FloatLayout when using pos_hint: {'right': 1}
Original Issue:
Setting Label.right in KV doesn't work correctly when size is bound to texture_size:
    Label:
        text: 'Label'
        size: self.texture_size
        right: root.right

Instead, the Label is placed with x=root.right. The Label will jump to the correct position when parent/window is resized.
This can be worked around by setting x this way instead:
    Label:
        text: 'Label'
        size: self.texture_size
        x: root.right - self.width

The same issue occurs with top: root.top

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/22027843-widget-right-binding-does-not-work-as-expected-when-width-changes-after-being-positioned?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github).

printing out when x, right, or width change:

initial         x=0 right=100 width=100
call to GraphicUnitTest.render()
window width set to 320, so label.right is set to 320
right_change    x=220 right=320 width=100
x_change        x=220 right=320 width=100
texture renders and texture_size changes label.width to 84
right_change    x=220 right=304 width=84
width_change    x=220 right=304 width=84

When the Label's texture_size is determined, the width is set to 84, but instead of x changing relative to right, right changes relative to x. x:220 + width:84 = right:304

I'm not sure this is a bug exactly. The main issue is that the parent sets Label.right before texture_size updates.
However, even if this were fixed, the issue would still occur if the text were to change after Label was positioned.
For binding in python code there's really nothing that can be done, but this all started with KV language:
Maybe the KV processor can just translate right: EXPRESSION to x: EXPRESSION - self.width and top: EXPRESSION to y: EXPRESSION - self.height

Is this Label inside a GridLayout ? if so it could be related to this issue https://github.com/kivy/kivy/pull/3216 ?

No, it happens with just a Label inside a plain Widget. Though I did notice an issue with GridLayout, I'll comment in #3216.

Well, it's doing exactly what you told it. Set Label.right to it's
parent.right whenever the parent.right changes. You didn't tell it to check
when the Label.width changes (in the second one, you did, hence it worked).
kv only binds to the properties you mention in your expression.
Really, this is the job of Layout widgets.
FloatLayout:
Label:
text: 'label text'
size_hint: None, None
size: self.texture_size
pos_hint: {'right': 1}
On Mon, Jun 15, 2015 at 11:55 PM Arlo<EMAIL_ADDRESS>wrote:

No, it happens with just a Label inside a plain Widget. Though I did
notice an issue with GridLayout, I'll comment in #3216
https://github.com/kivy/kivy/pull/3216.
—
Reply to this email directly or view it on GitHub
https://github.com/kivy/kivy/issues/3430#issuecomment-112291254.

@kived I agree and I'm trying to write docs about this. However, I'm not sure what to suggest to use to make this work, other than hacks of adding e.g. self.width. For example using pos_hint doens't actually work.
Consider
layout = Builder.load_string('''
FloatLayout:
    id: layout
    width: 100
    Widget:
        id: wid
        pos_hint: {'right': 1}
''')

wid = layout.ids.wid
print(layout.right, wid.right)
wid.x = 200
print(layout.right, wid.right)

prints
(100, 100)
(100, 300)

Could it be that FLoatLayout needs to bind to wid's size and pos?

Ok, I didn't realize you could put 'right' in a pos_hint, thanks.
However, there are non-layout situations where you might try setting Label.right relative to another widget.
This seems sensible and unambiguous in KV. (put the Label on the left-side of some_other_widget)
Label:
    right: some_other_widget.x
    size: self.texture_size

I can't think of a situation where you wouldn't want this to account for changes to Label.width.
The problem with my suggestion of substituting right: EXP with x: EXP - self.width is when the developer defines x as well.
But I think the simplest solution is to just print a KV error if you bind x and right at the same time.

ERROR: 'right: some_other_widget.x' was converted to 'x: some_other_widget.x - self.width', but x is already bound.

There's one other situation I was thinking about: someone might try to fix the left and right sides of a Label relative to other widgets, expecting width to be calculated based on these constraints. (In this example the text_size line is necessary to make the Label wrap within width)
Label:
    x: left_widget.right
    right: right_widget.x
    text_size: self.width, None

I'm not sure if this works, but I'm guessing it doesn't. In this example, you could just use BoxLayout, but still, if the KV is logical, maybe it could be made to interpret that correctly.

Actually, AnchorLayout and FloatLayout seem fine to me. @matham Does your code work with size_hint: None, None within the inner widget?
This works fine for me:
from kivy.app import App
from kivy.lang import Builder

_kv = '''
FloatLayout:

    Widget:
        id: widget
        size_hint: None, None
        pos_hint: {'right': 1}
        canvas:
            Rectangle:
                pos: self.pos
                size: self.size

    ToggleButton:
        text: 'Width'
        size: self.texture_size
        padding: dp(10), dp(8)
        size_hint: None, None
        on_state: widget.width = 200 if self.state=='down' else 100
'''

class RightSide(App):
    def build(self):
        return Builder.load_string(_kv)

    def on_start(self):
        print(self.root.ids.widget.pos)

if __name__ == '__main__':
    RightSide().run()

Setting size_hint makes no difference. Did you try my code with size_hint set to None? Because it still doesn't work. In your code you're not setting the position.

@matham  I'm just looking at the Widget with pos_hint: {'right': 1} in my example.
With your code, both Widgets have a width of 100. If you change wid.width to 50 (in KV), it'll print:

(100, 50)
(100, 250)

So the right side isn't lined up to begin with. And I'm confused what you're testing by changing wid.x instead of wid.width.

@matham We do not currently bind to size (it's commented out, not sure
why), but we do bind to pos. In your example, the event loop isn't running
and therefore the clock isn't ticking. If you add Clock.tick() after
setting wid.x = 200 then it prints out (100, 100) as expected.
On Tue, Jun 16, 2015 at 1:14 AM Arlo<EMAIL_ADDRESS>wrote:

Ok, I didn't realize you could put 'right' in a pos_hint, thanks.
However, there are non-layout situations where you might try setting
Label.right relative to another widget.
This seems sensible and unambiguous in KV. (put the Label on the left-side
of some_other_widget)
Label:
right: some_other_widget.x
size: self.texture_size
I can't think of a situation where you wouldn't want this to account for
changes to Label.width.
The problem with my suggestion of substituting right: EXP with *x: EXP

self.width* is when the developer defines x as well.

But I think the simplest solution is to just print a KV error if you bind
x and right at the same time.
ERROR: 'right: some_other_widget.x' was converted to 'x:
some_other_widget.x - self.width', but x is already bound.
There's one other situation I was thinking about: someone might try to fix
the left and right sides of a Label relative to other widgets, expecting
width to be calculated based on these constraints. (In this example the
text_size line is necessary to make the Label wrap within width)
Label:
x: left_widget.right
right: right_widget.x
text_size: self.width, None
I'm not sure if this works, but I'm guessing it doesn't. In this example,
you could just use BoxLayout, but still, if the KV is logical, maybe it
could be made to interpret that correctly.
—
Reply to this email directly or view it on GitHub
https://github.com/kivy/kivy/issues/3430#issuecomment-112306272.

I've been thinking about various ways to close this issue. In order from easiest to hardest...
1. Just document it
Add some commentary to the KV Language page about setting right or top.
2. KV Warnings
The KV interpreter could print a warning if you bind right or top. However, if you're not changing widths the warning is a false positive.
2a. More intelligent KV Warnings
Instead of printing a warning, the KV interpreter could bind a print-warning-function to width changes. This pushes the warning to run-time, but warns the user when there's actually a problem. This code could could be placed in if _debug_ for efficiency.
3. Changes to width shift x or right depending on which was last set

Modify widget.py so that it tracks whether x or right was set last (set a right_sided boolean when x or right changes)
Remove width from right AliasProperty bind.
Make width an Alias property; in set_width:

if self.right_sided:
    self.x = self.right - self.width
else:
    self.right = self.x + self.width

Is the overhead worth addressing this issue? I'm not sure...up to the Kivy devs.

I added docs about this at https://github.com/kivy/kivy/commit/a7eaa867206c88aa5e062e7dcb5bc5f297a3959c, and as kived said, we already have layouts to deal with this so I don't think we should change anything.


Fix #609: Fix reading Transit response stream if data isn't available…

… right-away
InputStream .available only checks if data is available to read right
now. It is possible that data becomes available leter. Read method (used
by Transit internally) will block untill data is available or the stream
is closed.
It is best to let Transit read the stream. Empty streams throws an
exception with Transit, but we can catch that specific case and return
nil like previously.
Two test cases test the existing functionality, and third new test case
checks that Transit data is read correctly when the data becomes
available a bit later.

Merged, thanks again!


Dump and load extensions

Reopening #201

📚 Documentation preview 📚: https://metatensor-models--222.org.readthedocs.build/en/222/

@PicoCentauri Now there are tests that both train and export save the extensions. Their loading is tested as part of eval


operator hive-operator (1.2.4115-5ff17b1)

Update Hive community operator channel alpha to 1.2.4115-5ff17b1

/merge possible

/merge possible


Incompatible with azurerm v2.6.0

Looks like there were changes to the underlying azurerm resources in this module with regards to required arguments since this module was published:
Error: Missing required argument

  on .terraform/modules/docker_vmss.diskencrypt/main.tf line 15, in resource "azurerm_virtual_machine_extension" "vmextension":
  15: resource "azurerm_virtual_machine_extension" "vmextension" {

The argument "virtual_machine_id" is required, but no definition was found.

Error: Unsupported argument

  on .terraform/modules/docker_vmss.diskencrypt/main.tf line 18, in resource "azurerm_virtual_machine_extension" "vmextension":
  18:   location                   = "${data.azurerm_resource_group.test.location}"

An argument named "location" is not expected here.

Error: Unsupported argument

  on .terraform/modules/docker_vmss.diskencrypt/main.tf line 19, in resource "azurerm_virtual_machine_extension" "vmextension":
  19:   resource_group_name        = "${data.azurerm_resource_group.test.name}"

An argument named "resource_group_name" is not expected here.

Error: Unsupported argument

  on .terraform/modules/docker_vmss.diskencrypt/main.tf line 20, in resource "azurerm_virtual_machine_extension" "vmextension":
  20:   virtual_machine_name       = "${var.vm_name}"

An argument named "virtual_machine_name" is not expected here.

Error: Missing required argument

  on .terraform/modules/docker_vmss.diskencrypt/main.tf line 41, in resource "azurerm_virtual_machine_extension" "vmextensionlinux":
  41: resource "azurerm_virtual_machine_extension" "vmextensionlinux" {

The argument "virtual_machine_id" is required, but no definition was found.

Error: Unsupported argument

  on .terraform/modules/docker_vmss.diskencrypt/main.tf line 44, in resource "azurerm_virtual_machine_extension" "vmextensionlinux":
  44:   location                   = "${data.azurerm_resource_group.test.location}"

An argument named "location" is not expected here.

Error: Unsupported argument

  on .terraform/modules/docker_vmss.diskencrypt/main.tf line 45, in resource "azurerm_virtual_machine_extension" "vmextensionlinux":
  45:   resource_group_name        = "${data.azurerm_resource_group.test.name}"

An argument named "resource_group_name" is not expected here.

Error: Unsupported argument

  on .terraform/modules/docker_vmss.diskencrypt/main.tf line 46, in resource "azurerm_virtual_machine_extension" "vmextensionlinux":
  46:   virtual_machine_name       = "${var.vm_name}"

An argument named "virtual_machine_name" is not expected here.

I think the preferred TF resources to use for disk encryption (with Customer Managed Keys) are

azurerm_linux_virtual_machine
disk_encryption_set


🚀 Feature:  cRecy endpoint

🔖 Feature description
We need to create a series of endpoints for CRECY token data, enabling users to access detailed information about their token balance, transactions, earnings, and performance in relation to recycling activities. These endpoints will allow users to track their tokens, market performance, and the rewards earned from their recycling efforts.
Suggested Endpoints:
v1/crecy/price (GET)
Fetch the current price of CRECY, including historical price data (e.g., 24-hour, 7-day, 30-day price history).
v1/crecy/stats (GET)
Fetch key statistics related to CRECY, such as:
Market Cap
Circulating Supply
Total Supply
24-Hour Trading Volume
Price Change (24h)
v1/crecy/balance/:userId (GET)
Get the CRECY balance for a user, including both:
Locked CRECY
Available CRECY (the amount that can be freely transacted)
v1/crecy/transactions (GET)
List all CRECY transactions related to a user, including transaction IDs, amounts, and the type of transaction (e.g., deposit, withdrawal, reward earned).
v1/crecy/earnings/:userId (GET)
Fetch user earnings from recycling efforts in CRECY tokens, based on:
Total residues reported.
Total reports submitted.
Rewards calculated.
🎤 Why is this feature needed ?
This set of endpoints is critical for enabling users to track their CRECY token activities and performance over time. By offering real-time price data, transaction history, and token balance, users can make informed decisions about their token holdings, track their rewards from recycling efforts, and monitor their overall financial participation in the platform.
In my use-case:
Users need to monitor the real-time value of CRECY and how it fluctuates.
Users should be able to track the amount of CRECY they own, including any locked tokens.
Users need access to transaction histories and their earnings related to recycling activities, helping them understand the value they’re generating from the platform.
This feature would provide users with the insights to manage their wallet and decide whether to hold, trade, or redeem tokens.
✌ How do you aim to achieve this?
I want this feature to:
Implement clear token tracking features (price, balance, and transaction data) to improve user experience.
Display accurate, up-to-date CRECY earnings based on reported residues, helping users see their rewards directly linked to their actions.
Provide detailed CRECY transaction history, so users can track every token received, spent, or earned.
Offer CRECY market data, helping users stay informed about the market performance and value fluctuations of the token.
🔄 Additional Information
Follo most used related APIs
CoinGecko API:
CoinGecko API Documentation
Offers endpoints for token prices, market data, token info, and more.
Example endpoints:
/coins/markets: Get current prices and market data for coins.
/coins/{id}/history: Fetch historical data for a specific token.
/coins/{id}/market_chart: Get historical market chart data for a coin (price, market cap, volume).
CoinMarketCap API:
CoinMarketCap API Documentation
Provides detailed data about token prices, market cap, trading volume, and more.
Example endpoints:
/v1/cryptocurrency/listings/latest: Get the latest listings of cryptocurrencies, including token details.
/v1/cryptocurrency/info: Get detailed information about a specific cryptocurrency.
/v1/cryptocurrency/quotes/latest: Get the latest price and market data for a specific token.
Binance API:
Binance API Documentation
One of the largest cryptocurrency exchanges providing real-time market data, order book info, and more.
Example endpoints:
/api/v3/ticker/price: Get the latest price for a specific token pair.
/api/v3/account: Retrieve details of an account, including balances for tokens.
/api/v3/transactions: Retrieve transaction history for a user.
Kraken API:
Kraken API Documentation
Provides data for token price, balances, transaction history, etc.
Example endpoints:
/0/public/Ticker: Get the latest market data for a specific token.
/0/private/Balance: Retrieve account balance details.
/0/private/TradesHistory: Get transaction history for an account.
Gemini API:
Gemini API Documentation
Offers data related to token prices, balances, and transactions on the Gemini exchange.
Example endpoints:
/v1/prices: Get the latest prices for token pairs.
/v1/mywallet: Get the user's wallet balances.
/v1/mytrades: Retrieve a user’s trade history.
CoinGecko API:
CoinGecko API Documentation
Offers endpoints for token prices, market data, token info, and more.
Example endpoints:
/coins/markets: Get current prices and market data for coins.
/coins/{id}/history: Fetch historical data for a specific token.
/coins/{id}/market_chart: Get historical market chart data for a coin (price, market cap, volume).
CoinMarketCap API:
CoinMarketCap API Documentation
Provides detailed data about token prices, market cap, trading volume, and more.
Example endpoints:
/v1/cryptocurrency/listings/latest: Get the latest listings of cryptocurrencies, including token details.
/v1/cryptocurrency/info: Get detailed information about a specific cryptocurrency.
/v1/cryptocurrency/quotes/latest: Get the latest price and market data for a specific token.
Binance API:
Binance API Documentation
One of the largest cryptocurrency exchanges providing real-time market data, order book info, and more.
Example endpoints:
/api/v3/ticker/price: Get the latest price for a specific token pair.
/api/v3/account: Retrieve details of an account, including balances for tokens.
/api/v3/transactions: Retrieve transaction history for a user.
Kraken API:
Kraken API Documentation
Provides data for token price, balances, transaction history, etc.
Example endpoints:
/0/public/Ticker: Get the latest market data for a specific token.
/0/private/Balance: Retrieve account balance details.
/0/private/TradesHistory: Get transaction history for an account.
Gemini API:
Gemini API Documentation
Offers data related to token prices, balances, and transactions on the Gemini exchange.
Example endpoints:
/v1/prices: Get the latest prices for token pairs.
/v1/mywallet: Get the user's wallet balances.
/v1/mytrades: Retrieve a user’s trade history.
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Contributing Guidelines

Are you willing to submit PR?
None

This first version we could create with more used fields and keep simple.


IndexSizeError getting logged in raven code

Do you want to request a feature or report a bug?
bug?
What is the current behavior?
This error keeps getting logged occasionally.
IndexSizeError
~/raven-js/src/raven.js in o.prototype.captureMessage at line 382:0
It doesn't seem to be causing any real problems to the end users and the whole stack trace is within raven.js. I'm not sure if this is really a problem, but I figured I'd write it up here instead of just ignoring it.

Hi Nate - could you post the entire stack trace? Because I associate this error with canvas/dom apis, I have the feeling that this is not a raven.js issue (but could be wrong). Does your page use the canvas?

Yeah, here you go:
at o.prototype.captureMessage(~/raven-js/src/raven.js:382:0)
at o.prototype.captureException(~/raven-js/src/raven.js:329:0)
at r(~/raven-js/src/raven.js:282:0)

I'm not positive it's a raven issue either. We do have a couple canvases in the app, but it looks like they shouldn't have been rendered when the error was thrown.

not quite enough for me to reproduce this, and still inclined to think that this is an error originating in the other code that raven is hiding or displaying in a confusing way. could you try disabling raven? one easy way to do this if you CDN raven and run an adblocker is to add it to your adblocker rules, or otherwise just commenting it out of your build. Thanks nate!

I'll keep an eye on it I guess. I haven't ever seen it locally, so I wouldn't really be able to tell if disabling raven changes anything :/
Thanks for taking a look

This is not a bug in Raven.js – this is just the point at which Raven captured the error by wrapping a function call in try/catch.
I added a comment in getsentry/raven-js#847 to try and address this.