fix RCQ::cancel miss calling notify_all

What problem does this PR solve?
Issue Number: close #8141
Problem Summary:
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/hold

/run-unit-test

/merge


Syntax highlighting

Also, make the link tappable.
Problem
The code blocks aren't currently using syntax highlighting, they are easier to read if the syntax is highlighted.
Also, the link to Twitter's other projects isn't tappable (not detected as a link).
Solution
Add language names to the code blocks. Code is now highlighted.
Add https:// to the link, it's now tappable.

This got pulled into the internal repository. It will be included in coming release.


fix(from): Changed the priority of observable detection

Description:
This PR ensures that Observable.from uses Observable Symbol interop mechanism before attempting any others.
Related issue (if exists):
Closes #3779

Coverage increased (+0.2%) to 96.862% when pulling b170c1d2174f2ee467e2769e8eecd5d005adb883 on taras:from-change-priority into db2ac691310e679c81eeddc3c88e1b776a14e933 on ReactiveX:master.

Thanks @taras!


Should our promises be documented as first class?

Continuing https://github.com/GoogleCloudPlatform/google-cloud-node/pull/1697#discussion_r83665859:
Should we be promoting promise use first, as in "this is the way to use our library", with a mention about callbacks? Since the demand for promises is so strong, I'm wondering if we might be better off changing our position to a promise library that supports callbacks instead of the other way around.

/cc @jgeewax @omaray @jmdobry

As a complete outsider, I vote yes!
Especially with async await on the horizon, it's a way better way of writing async code

This issue may no longer be relevant due to its age. Feel free to re-open.

I am no longer on the team


Is it not possible to have a page with a path /maintenance ? Possibly because of maintenance mode somehow?

Laravel Version
9.52.5
PHP Version
8.1.4
Database Driver & Version
MySQL 8
Description
Have built a light CMS using Jetstream for a few small clients I have and one of them has created a page with the slug /maintenance for the page path. The page throws a 404 when you try to navigate to the page from a Jetstream link, but will load fine if I load the URL directly. I can't seem to find any other reason why it might do so. As soon as I change the path e.g. to /maintain it works fine.
It's probably not that big a deal to change the URL path, but trying to find out if anybody has the same behaviour as a bit of googling doesn't seem to reveal an issue before.
Steps To Reproduce

Create a new Laravel Jetstream set up.
Create a route with the url {domain}/maintenance.
Navigate to the URL via a <Link /> component.

Sorry, realised this doesn't apply to a regular Laravel install so moving to the Jetstream repo.


User "system:anonymous" cannot get path "/apis/constraints.gatekeeper.sh/v1beta1//

Hello, i wanted to try your dashboard so i could try runing it for my company, but that didn't worked.
On my local machine i used :
docker run -v ~/.kube/config:/home/gpm/.kube/config -p 8080:8080 quay.io/sighup/gatekeeper-policy-manager:v0.5.1

It loaded my kubeconfig file correctly, when i click  "Get constraints status", it give me following error:
(403) Reason: Forbidden HTTP response headers: HTTPHeaderDict({'Audit-Id': '2b44e6b7-e43e-449b-a608-83d4347fde9e', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'e8915a47-326c-450c-af43-f297c36367a6', 'X-Kubernetes-Pf-Prioritylevel-Uid': '38bf4b6b-d54e-4289-b143-c225265af301', 'Date': 'Tue, 01 Mar 2022 13:36:38 GMT', 'Content-Length': '225'}) HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"forbidden: User \"system:anonymous\" cannot get path \"/apis/constraints.gatekeeper.sh/v1beta1//\"","reason":"Forbidden","details":{},"code":403}

[2022-03-01 13:27:34 +0000] [1] [INFO] Starting gunicorn 20.1.0
[2022-03-01 13:27:34 +0000] [1] [INFO] Listening at: http://<IP_ADDRESS>:8080 (1)
[2022-03-01 13:27:34 +0000] [1] [INFO] Using worker: gthread
[2022-03-01 13:27:34 +0000] [9] [INFO] Booting worker with pid: 9
[2022-03-01 13:27:34 +0000] [11] [INFO] Booting worker with pid: 11
[2022-03-01 13:27:38,405] INFO: RUNNING WITH AUTHENTICATION DISABLED
[2022-03-01 13:27:38,405] INFO: RUNNING WITH AUTHENTICATION DISABLED
[2022-03-01 13:27:38,407] INFO: Attempting init with KUBECONFIG from path '~/.kube/config'
[2022-03-01 13:27:38,407] INFO: Attempting init with KUBECONFIG from path '~/.kube/config'
[2022-03-01 13:27:38,691] ERROR: [Errno 2] No such file or directory: 'aws-iam-authenticator'
[2022-03-01 13:27:38,693] ERROR: [Errno 2] No such file or directory: 'aws-iam-authenticator'

I have gatekeeper 3.7 installed on my EKS cluster and its up and running.
gatekeeper-system   gatekeeper-audit-59d4b6fd4c-lw8hj                1/1     Running   0          82d
gatekeeper-system   gatekeeper-controller-manager-66f474f785-448pz   1/1     Running   0          82d
gatekeeper-system   gatekeeper-controller-manager-66f474f785-895ng   1/1     Running   0          82d
gatekeeper-system   gatekeeper-controller-manager-66f474f785-cl8sz   1/1     Running   0          82d

We use STS assume role and use the aws-auth mechanism provided by AWS,  could that be the issue , as it seems the client run by default in anonymous, and ofc we don't provide access to anonymous user in our clusters
Thanks

Hello @steve-heslouin
You seem to be using https://github.com/kubernetes-sigs/aws-iam-authenticator to authenticate to EKS. GPM's docker image doesn't include the aws-aim-authenticator binary. You could try mounting also the binary to somewhere in $PATH together with the KUBECONFIG when you run the docker image, maybe that's enough.

@ralgozino Thanks a lot for your feedback, let me try it and i will let you know ;)

What version of kubectl do you have installed?
Could you please check your kubeconfig and see if you have a section like this:
# [...]
users:
- name: kubernetes-admin
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      command: aws-iam-authenticator
      args:
        - "token"
        - "-i"
        - "REPLACE_ME_WITH_YOUR_CLUSTER_ID"
        - "-r"
        - "REPLACE_ME_WITH_YOUR_ROLE_ARN"
  # no client certificate/key needed here!

if you do, check that the apiVersion is client.authentication.k8s.io/v1beta1.
I think it could be a mismatch between the Kubernetes client version included in GPM and your kubeconfig format.
I would suggest trying with the unstable tag of GPM instead of v0.5.1 that has a newer version of the Kubernetes client.

Ok so i edited my kubeconfig to target v1beta1 instead and that worked great, i logged in and saw my constraints.
Thanks a lot @ralgozino , i will be testing it in dev envs, see how it goes, and if that work, well, we will surely
will propose PRs to help for any improvements ;)

Great to hear that!
We'll be waiting for your feedback 🙂

 name: arn:aws:eks:......
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - --region
      - us-east-1
      - eks
      - get-token
      - --cluster-name
      - cluster_name
      command: aws
      env:
      - name: AWS_PROFILE
        value: dev
      interactiveMode: IfAvailable
      provideClusterInfo: false

Turns out i also had some cluster that were relying on aws cli, and by adding it to your image, it also worked, maybe that'd be cool to have those 2 binary installed by default ?

I need to think about it, as first thought, I would prefer not to include them in order to no couple GPM version to AWS's tooling. What we can do instead is to add documentation on how to do it so everyone can easily build the image with the versions they need


OKCOIN response Gone

Hello, when I enter the command "bin / console bot: trade" in the console, I get the following error message,
"Client error: `GET https://www.okcoin.com/api/v1/ticker.do?symbol=btc_usd`
  resulted in a `410 Gone` response:
  Gone
"

, can you help me?

Hello, I have a ubuntu 18.04 desktop version on which I install your software as follows, see attachment (Ubuntu.txt). These installations are also error-free. But as soon as I enter the composer install command I get the error as can be seen in the appendix (Fehler.txt, Airbitrade.jpg). Can someone help me there?

fehler.txt
ubuntu.txt

About your first question, you get '410 Gone' because the OKCoin API V1 is gone :-)
The API is at v3 now, and the request for the ticker should be at
https://www.okcoin.com/api/spot/v3/instruments/BTC-USDT/ticker. (I think)
The code that calls it is in the src/AppBundle/Service/OkcoinService.php but needs to be rewritten a bit, since
$responseJson->ticker->buy and $responseJson->ticker->sell dont exist in the new api. There is ask and bid now, but I'm not sure what it means.


Testsuite hides important error messages

It seems that the InitializationFailed exceptions do not appear in the testsuite output. All I see are the "&&& hit other exception" messages with no previous traceback.

I merged invalid-pipeline-hides-package-errors into v2.2. I'm attaching the looping version to this issue.

#1165 is a replacement for invalid-pipeline-hides-package-errors_/loops. I was not able to merge, so I am just reusing the test case. Are there other parts of that branch that we need?
The looping has been replaced by handle_invalid_pipeline recursing. It now only need to be called once, creating an upgrade for each recursion level. The advantages are that the recursion is useful for other places where handle_invalid_pipeline is called, and that handle_invalid_pipeline knows when recursion is needed by looking at the status of the final exceptions. All tests pass.


Bluetooth: controller: Fix handling of Read Static Addrs cmd

The status in the Command Complete event was uninitialized, leading to
incorrect contents of the event parsed by the Host. Correctly initialize
the status to success.
Signed-off-by: Carles Cufi<EMAIL_ADDRESS>

@mringwal, can you give this a try?


Feature: Image annotations

The purpose of this PR is to add the ability to annotate a line (whether it has a visible width or not) with an image or an icon. The user on his side needs to load the image as a future, which is standard Flutter stuff.
There are some whitespace changes. We should consider adding a git hook to dartfmt and enforce style rules. Unfortunately the last PR submitter did not use our formatter settings probably because he has an overriding global VSCode setup or uses a different editor.

This PR is tracking dev branch


rocketchat-desktop ServiceWorker segfaults unexpectedtly

My Setup

Operating System: 5.10.18-1-MANJARO
App Version: 3.1.1-1
Installation type: AUR install using yay

[x] I have tested with the latest version
[ ] I can simulate the issue easily

Description

When the application is idle, it unexpectedly crashes. Looking up system logs, it seems like a ServiceWorker segfaults.
I have no lead on what causes the segfault, as it can happen whenever the app is open, even if not in use.
ServiceWorker t[357858]: segfault at 3d8 ip 000055e32ea5740b sp 00007fbb5ace4aa0 error 4 in electron[55e328ce1000+5e77000]

Current Behavior

The application segfaults unexpectedly.
Expected Behavior

I expect the application to not segfault, especially when not actively in use.

Let me know if I can provide more context in any way!
I am not an administrator on the remote server and this issue has been going on for a couple of months.
I have not tried on another remote server.

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.
Thank you!


[CMake] Add missing deps found via LLVM's -DBUILD_SHARED_LIBS=TRUE

Top-of-tree builds just fine with: -DBUILD_SHARED_LIBS=TRUE

@swift-ci please smoke test

Hi @compnerd – Any tips on how to get this reviewed and merged? GitHub won't even let me add you as a reviewer.

Hi @bob-wilson – Any tips on how to get this integrated?

Should the tools/libclang dependency go to upstream Clang? I can't tell if that is specific to swift-clang.

Sorry if the earlier comment wasn't clear, vanilla (no Swift changes) llvm+clang builds just fine with BUILD_SHARED_LIBS=TRUE, so it seems to me that this patch "must" be Swift specific, right?

I guess so. I'll go ahead and merge it.
If you want to get it to the stable branch, please make a PR to cherry-pick it to swift-5.1-branch. ("stable" is basically an alias for the latest release branch.)


Remote shell fixes

Fixes
1. Remote Shell Form is now set to double-buffered.
    - Fixes an issue with the Remote Shell Form flickering.
2. Handling "exit" commands.
    - No longer directly sends an "exit" command to the client because this.Close() is called. In such context, the Remote Shell Form is closed. The Remote Shell Form is subscribed to an event that will send an "exit" command to the client when the Remote Shell Form is closing. There is no need to send two "exit" commands.
3. The output TextBox for the Remote Shell Form is now a RichTextBox.
    - Allows correct colorization of appended text.
Changes
1. Handling "exit" commands.
    - Changed how it is handled: correctly parsed from a command and handled correctly.
2. Dispose(bool).
    - Dispose(bool) should not suppress finalization. Finalization suppression should be determined by Dispose().
    - Now disposes of the new ManualResetEvent objects.
Additions
1. Added a property to RemoteShellCommandResponse (IsError).
    - This new property denotes how it should be handled: it the RemoteShellCommand responded with an error (IsError = true), we should print it differently (red).
2. Added an interface (IRemoteShell) for the RemoteShellForm.
    - Provides methods to use specifically for printing regular messages or errors.
    - More readable.
    - By routing all of the output messages and error messages to the same spot, changing or extending on these features are significantly easier.
3. Multi-threaded output chaining.
    - Created new thread that handles the output of errors in the shell.
    - Added a new method that queues up the threads used to chain the two different outputs together.

@d3agle Would you mind helping me test this new one out? I just wrote it today so it may have something I didn't catch yet.

Fixes the following issues:
- Issue 223
- Issue 216

Sure thing.  :)

Everything looks good so far from what I can tell.  One little thing I noticed was, say I have a directory with many dirs/files inside and i run the dir command.  While it's returning the output to the server, it's also taking input from the server.  Say I spam pause while its sending the server the output of executing dir.  It will look like this: http://i.gyazo.com/4b5c3638f195449e46ee8ea4a26f30a7.mp4

I'm assuming that the command had already completed and the output is still being sent, it mixes the two together

I couldn't help but notice the Riot Games part... I only play ARAM these days, but I usually spend free-time programming and learning! ;)
Also, I think this issue is, as you stated, issues with packet order... Hmmm...

@d3agle Please try to remove the Thread.Sleep(200); for both redirecting methods. It seems as though that is butchering the output by stopping the message chain too long when handling more data. I am not sure why that was in the original logic anyways... Probably to ensure ordered packets I would assume...

Haha :D I had installed League of Legends a while back, and played for probably 10 minutes before losing interest. Just wasn't a game I could get into.  I will remove that call and see if it fixes the issue.  Everything other than that looks good,  I think I might have a hard time inputting text that might not tolerate well on the client, but I'll see if I can break it.

Now the output is extremely fast, which is nice.  This is what it looks like: http://i.gyazo.com/eb1cbe540425c5f4503d4a0b34684e61.mp4
It appears a little weird, but I think its because of gyazo.  looks fine on my screen.
I'm assuming the end goal would be to have a shell that operates similar to what opening a command prompt would display, so theres a bit more work as far as behaviors.  For example, in that .gif, executing pause on a new line won't display the output until another command is executed

This does not correctly kill the spawned process cmd.exe please fix this!!

Done.


Exposing Deployment-ID variable

Hi!
Thanks for the contribution.
Did you perform any testing as part of the changes? If so it'd be helpful to include that in the PR.
Are you OK with submitting this contribution under the Apache License 2.0?


Not removing all the files

I have more no of duplicate files but it removes only one .. have a look at your map addition

fixed check it!


[vx.dev] implements #102

[vx.dev] This PR implements #102, created by vx.dev.

[vx.dev]: This code snippet creates a payment form with a green theme, as per the provided wireframe. The form includes a toggle group for selecting the payment method, input fields for name, city, card number, expiration date, and CVC, and a green "Continue" button. The expiration date fields use dropdown selects for month and year. The form is styled with Tailwind CSS classes for layout, spacing, and colors.

[vx.dev]: Based on the provided wireframe and code, I'll create an updated version of the payment form with a green theme. I'll also ensure that the "Year" label is visible and aligned with the other labels.
This updated code includes the following changes:

The main title now uses the text-green-600 class for a green-themed color.
The "Year" label now has the block class to ensure it is visible and aligned with the other labels.
The "Continue" button uses bg-green-600 for a green-themed background and hover:bg-green-700 for a darker green on hover.

The form should now meet the new requirements and maintain a consistent green theme throughout.


Proxy protocol for Mining Core

I've been trying to wedge haproxy without losing miningcore's banning functionality but to no avail. I tried send-proxy and send-proxy-v2 versions which was alluded to in the Wiki/Configuration, but that results in an error.

If running behind something like HAProxy be sure to enable 'tcpProxyProtocol', otherwise you'll end up banning your own IP address (and therefore all workers).

This is in our wiki? I didn't write that for sure. I'm not sure how this would ever work without haproxy being able to communicate the real IP to MC.

Yeah it's in there. I don't think it's possible either unless MC starts supporting proxy protocols or via transparent proxying. The latter being more of a workaround and not quite ideal.

Proxy Protocol
Haproxy TProxy
Transpareny Proxy via a proxy app

Could you elaborate a bit on your specific use-case?

As for where that appears in the wiki it's in the example configuration at https://github.com/coinfoundry/miningcore/wiki/Configuration and appears to have been copied over from the example configuration in the Readme of NOMP at https://github.com/zone117x/node-stratum-pool
NOMP has this extra configuration option which is what that statement refers to
     /* Enable for client IP addresses to be detected when using a load balancer with TCP proxy
       protocol enabled, such as HAProxy with 'send-proxy' param:
       http://haproxy.1wt.eu/download/1.5/doc/configuration.txt */
    "tcpProxyProtocol": false,

I use (or at least want to use) HAProxy to automatically switch slave (external stratum) MC servers that are down for maintenance (or are just down) to other servers.
So far using HAProxy works, but it runs without MC's banning feature.
@bitspill thanks for pointing out the source.

@bitspill @rymdluo I've cleaned up wiki page.

I just tried it out. I keep getting the Received spoofed Proxy-Protocol header message. This is the debug log.
[2018-04-15 19:25:07.8798] [D] [monero-testnet] [Pool] Accepting connection [0HLD30Q6QV807] from ###.###.###.###:33856
[2018-04-15 19:25:07.8798] [E] [StratumClient] [0HLD30Q6QV807] Received spoofed Proxy-Protocol header from ###.###.###.###
[2018-04-15 19:25:07.8798] [D] [StratumClient] [0HLD30Q6QV807] Last subscriber disconnected from receiver stream

@rymdluo Of course the first person to try it out would hit the shortcut I took with the implementation 😁 . Right now the proxy-header is only accepted when sent from localhost. I'm going to improve this tommorow.

@oliverw No worries, please hit me again when I can test it out!

Pushed an update to dev. Updated configuration options:
            "ports": {
                "4032": {
                    "difficulty": 1000,
                    "tcpProxyProtocol": {
                        "enable": true,
                        "mandatory": false,
                        "proxyAddresses": []
                    }
                }
            },

It appears to be working quite well, MC is able to expose the ip address of the miner through HAProxy. Great work!
There is a small bug I noticed though, the program seems to refuse to fully shut down now via CTRL-C. It takes a pid kill to do it.
^C
[2018-04-17 10:28:37.9765] [I] [Program] SIGINT received. Exiting.
SIGINT received. Exiting.
[2018-04-17 10:28:37.9778] [I] [Program] Shutdown ...
Shutdown...
[2018-04-17 10:28:37.9778] [I] [ShareRecorder] Stopping ..
[2018-04-17 10:28:37.9778] [I] [ShareRecorder] Stopped
[2018-04-17 10:28:37.9778] [I] [StatsRecorder] Stopping ..
[2018-04-17 10:28:37.9778] [I] [StatsRecorder] Stopped
[2018-04-17 10:28:39.5596] [I] [StratumClient] [0HLD49N47KLV0] Real-IP via Proxy-Protocol: ###.###.###.###
[2018-04-17 10:28:41.5604] [I] [StratumClient] [0HLD49N47KLV1] Real-IP via Proxy-Protocol: ###.###.###.###

@rymdluo looks like this is the same bug I filed at #260 .


K8s imds proxy

Enable running metadata proxy under kubernetes. Includes some minor refactorings and removal of dead code.

I was a little bit more critical and nit-picky than normal, given this is a big, critical feature, and that this is a big jump into the codebase. Feel free to ignore me on most of the nit-picks. If you disagree with me, I'm happy to change me opinion.

@sargun I believe I have addressed all of your comments?

I thought you were going to implement a CRI which injected pods? :P. Let me take a look tomorrow. Is that okay?

:-D A couple of days is fine, there is no rush.
On Tue, Apr 21, 2020 at 8:55 PM Sargun Dhillon<EMAIL_ADDRESS>wrote:

I thought you were going to implement a CRI which injected pods? :P. Let
me take a look tomorrow. Is that okay?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Netflix/titus-executor/pull/381#issuecomment-617534099,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGC56LIX3L5KKYJUZCQJ7DRNZTEXANCNFSM4MDTHSEA
.


[Live Preview] Missing optional closing tag on last sibling treated as syntax error

This is from brackets-dev forum.
Recipe

Open page below in Live Preview
Start typing

Results
Text is not updated in browser. Line is not shown as invalid until after typing starts.
Brackets treats missing
,
, and
 as syntax error. Also

<!doctype html>

<meta charset="utf-8">
<title>Clearing floats using ‘overflow’ - 002</title>

About FooML

FooML is a markup language written in XML.

FooML namespace

http://example.org/2005/fooml

FooML MIME type

application/x-fooml+xml

This outer DIV element, div#content, has a green background.

I fixed this in #12057, can someone please take a look at that pull request?


Extensions filter for publisher should be exact

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

VS Code Version:  1.62.3
OS Version: Windows 10

Steps to Reproduce:

Go to an extension by a verified publisher in the extensions view, example: "GitHub Pull Requests and Issues"
Click the publisher name next to the shiny tick star to see other extensions by "this" publisher.
Note the inclusion of any publisher with the original publisher in the name. For example "Github Octo", "Correia GitHub Gruvbox".
This could confuse an unwary user into installing an unverified extension thinking it was by a trusted publisher.

Suggestion for fixing: Publisher filter should be an exact, not partial, match.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.67.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Thanks @SaiKanth007. I am not aware of this filter type. Moving this to VS Code repo to support it.

@SaiKanth007 thanks for letting us know. Might there be some other filters we are not using and we should? Thanks

@isidorn currently we don't have any public documentation of the API to list down the different filterTypes we support. So sharing you the details on the teams chat.

@SaiKanth007 Does this filter takes publisher id or publisher display name?

It accepts publisher id.
I just saw that filtering on publisher id works as expected when there is no search text. (Unlike other VSCode calls which hit AzureSearch/Marketplace cache this hits marketplace DB - could become expensive as the load for this scenario increases)
Also, it breaks when we provide search text along with publisherId filtering (which I guess is what users eventually need). I will create an issue for both of this on our side and track it.
We are working on migrating search scenarios to our new platform, and I will check if this can be fixed there. Otherwise, we will try to fix it in the existing code.

It accepts publisher id.

@isidorn It means this breaks when publisher name is Microsoft because not all Microsoft extensions have same publisher id.

@sandy081 that sucks. That would be worse than the current state of things.
@SaiKanth007 is there some way to do the filtering based on publisher display name due to the case Sandeep described.

This is fixed in the latest Insiders. @aquarion Could you try it?

Is publisher title unique? For example, clicking on the publisher title in VSCode:

Publisher id still doesn't work:

Version: 1.73.0-insider (user setup)
Commit: 266ff5b78fc4a128994194e828e55b2bbeb0acbe

Yes, unfortunately the display name is not unique.
@prashantvc ideally we would make this unique. Not sure if this is possible or planned?

We do make sure that Display Name is unique for enterprises and well-known publishers. But, not for everyone, this is something we have on the backlog but not planned

Closing this as no further plans to improve here I think.


lsp: handle textDocument/definition requests

This was rather simple, as this was already handled by the opa oracle find-definition command. The API for that was however internal, so I've copied the single file handling that from OPA.
PR marked WIP as two things warrants some discussion:

Similarly to formatting, this LSP feature seems to conflict with client side implementations, and you'll see duplicate "definitions" in VS Code when this is enabled both in the client and from the LSP server. We should probably make this conditional on Regal in VS Code.
The GetAllModules function that exists on the cache does not seem to take into account files that have been marked as ignored via .regal/config.yaml. This lead to an annoying situation when this was used in the Regal repo, as some files we've ignored did not compile, and that caused go to definition to fail.

Fixes #645

The GetAllModules function that exists on the cache does not seem to take into account

So now that we know this was a misleading error relating to inlay hints, fixed in #669. We can have a think about:

Similarly to formatting, this LSP feature seems to conflict with client side implementations

I think it makes sense to just disable the provider in the client when regal is on. I did the same for formatting so I'll do that now.


Can you share the codes about train the camvid dataset ?

 Can you share the codes about train the camvid dataset , or tell me how to preprocessing camvid dataset for training!
Thanks!

 Can you share the codes about train the camvid dataset , or tell me how to preprocessing camvid dataset for training!
Thanks!

Hello! Did you finally get codes for train the camvid dataset?

We used the same code and procedure for the Camvid dataset. Please change the loadData.py file for CamVid dataset and you should be good to go


fern init generates bad yml code against NestJS/Swagger's localhost-based yaml endpoint

CLI Version from fern.config.json
0.45.2
Generator & Version from generators.yml
fernapi/fern-typescript-node-sdk 0.39.3
Minimal API Specification
{"openapi":"3.0.0","paths":{"/":{"get":{"operationId":"AppController_getHello","parameters":[],"responses":{"200":{"description":""}},"tags":["App"]}},"/users":{"post":{"operationId":"UserController_create","parameters":[],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/CreateUserDto"}}}},"responses":{"201":{"description":"The user has been successfully created.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/UserResponseDto"}}}},"400":{"description":"Invalid input"},"409":{"description":"User with this email already exists"}},"summary":"Create a new user","tags":["users"]},"get":{"operationId":"UserController_findAll","parameters":[],"responses":{"200":{"description":"List of all users","content":{"application/json":{"schema":{"type":"array","items":{"$ref":"#/components/schemas/UserResponseDto"}}}}}},"summary":"Get all users","tags":["users"]}},"/users/{id}":{"get":{"operationId":"UserController_findOne","parameters":[{"name":"id","required":true,"in":"path","schema":{"type":"string"}}],"responses":{"200":{"description":"The found user","content":{"application/json":{"schema":{"$ref":"#/components/schemas/UserResponseDto"}}}},"404":{"description":"User not found"}},"summary":"Get a user by id","tags":["users"]},"delete":{"operationId":"UserController_remove","parameters":[{"name":"id","required":true,"in":"path","schema":{"type":"string"}}],"responses":{"200":{"description":"User successfully deleted"},"404":{"description":"User not found"}},"summary":"Delete a user","tags":["users"]}},"/exercises":{"post":{"operationId":"ExercisesController_create","parameters":[],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/CreateExerciseDto"}}}},"responses":{"201":{"description":""}},"tags":["Exercises"]},"get":{"operationId":"ExercisesController_findAll","parameters":[],"responses":{"200":{"description":""}},"tags":["Exercises"]}},"/exercises/{id}":{"get":{"operationId":"ExercisesController_findOne","parameters":[{"name":"id","required":true,"in":"path","schema":{"type":"string"}}],"responses":{"200":{"description":""}},"tags":["Exercises"]},"patch":{"operationId":"ExercisesController_update","parameters":[{"name":"id","required":true,"in":"path","schema":{"type":"string"}}],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/UpdateExerciseDto"}}}},"responses":{"200":{"description":""}},"tags":["Exercises"]},"delete":{"operationId":"ExercisesController_remove","parameters":[{"name":"id","required":true,"in":"path","schema":{"type":"string"}}],"responses":{"200":{"description":""}},"tags":["Exercises"]}},"/workouts":{"post":{"operationId":"WorkoutsController_create","parameters":[],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/CreateWorkoutDto"}}}},"responses":{"201":{"description":""}},"tags":["Workouts"]},"get":{"operationId":"WorkoutsController_findAll","parameters":[],"responses":{"200":{"description":""}},"tags":["Workouts"]}},"/workouts/{id}":{"get":{"operationId":"WorkoutsController_findOne","parameters":[{"name":"id","required":true,"in":"path","schema":{"type":"string"}}],"responses":{"200":{"description":""}},"tags":["Workouts"]},"patch":{"operationId":"WorkoutsController_update","parameters":[{"name":"id","required":true,"in":"path","schema":{"type":"string"}}],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/UpdateWorkoutDto"}}}},"responses":{"200":{"description":""}},"tags":["Workouts"]},"delete":{"operationId":"WorkoutsController_remove","parameters":[{"name":"id","required":true,"in":"path","schema":{"type":"string"}}],"responses":{"200":{"description":""}},"tags":["Workouts"]}},"/notifications":{"post":{"operationId":"NotificationsController_create","parameters":[],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/CreateNotificationDto"}}}},"responses":{"201":{"description":""}},"tags":["Notifications"]},"get":{"operationId":"NotificationsController_findAll","parameters":[],"responses":{"200":{"description":""}},"tags":["Notifications"]}},"/notifications/{id}":{"get":{"operationId":"NotificationsController_findOne","parameters":[{"name":"id","required":true,"in":"path","schema":{"type":"string"}}],"responses":{"200":{"description":""}},"tags":["Notifications"]},"patch":{"operationId":"NotificationsController_update","parameters":[{"name":"id","required":true,"in":"path","schema":{"type":"string"}}],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/UpdateNotificationDto"}}}},"responses":{"200":{"description":""}},"tags":["Notifications"]},"delete":{"operationId":"NotificationsController_remove","parameters":[{"name":"id","required":true,"in":"path","schema":{"type":"string"}}],"responses":{"200":{"description":""}},"tags":["Notifications"]}}},"info":{"title":"Workout Texts","description":"OpenAPI spec for the Workout Texts API backend","version":"1.0","contact":{}},"tags":[{"name":"workouts","description":""}],"servers":[],"components":{"schemas":{"CreateUserDto":{"type":"object","properties":{"email":{"type":"string","example":"user@example.com","description":"The email address of the user"},"password":{"type":"string","example":"password123","description":"The user password - minimum 8 characters","minimum":8}},"required":["email","password"]},"UserResponseDto":{"type":"object","properties":{"id":{"type":"number","example":1,"description":"The unique identifier of the user"},"email":{"type":"string","example":"user@example.com","description":"The email address of the user"},"created_at":{"format":"date-time","type":"string","example":"2024-01-01T00:00:00Z","description":"When the user was created"},"updated_at":{"format":"date-time","type":"string","example":"2024-01-01T00:00:00Z","description":"When the user was last updated"}},"required":["id","email","created_at","updated_at"]},"CreateExerciseDto":{"type":"object","properties":{}},"UpdateExerciseDto":{"type":"object","properties":{}},"CreateWorkoutDto":{"type":"object","properties":{}},"UpdateWorkoutDto":{"type":"object","properties":{}},"CreateNotificationDto":{"type":"object","properties":{}},"UpdateNotificationDto":{"type":"object","properties":{}}}}}

Actual Generated Code
# fern/openapi/openapi.yml

>

  <!DOCTYPE html>

    <meta charset="UTF-8">
    <title>Swagger UI</title>
    <link rel="stylesheet" type="text/css" href="./api/swagger-ui.css" >
    <link rel="icon" type="image/png" href="./api/favicon-32x32.png" sizes="32x32" /><link rel="icon" type="image/png" href="./api/favicon-16x16.png" sizes="16x16" />

  <svg xmlns="http://www.w3.org/2000/svg"
  xmlns:xlink="http://www.w3.org/1999/xlink"
  style="position:absolute;width:0;height:0">
    <defs>
      <symbol viewBox="0 0 20 20" id="unlocked">
        <path d="M15.8 8H14V5.6C14 2.703 12.665 1 10 1 7.334 1 6 2.703 6 5.6V6h2v-.801C8 3.754 8.797 3 10 3c1.203 0 2 .754 2 2.199V8H4c-.553 0-1 .646-1 1.199V17c0 .549.428 1.139.951 1.307l1.197.387C5.672 18.861 6.55 19 7.1 19h5.8c.549 0 1.428-.139 1.951-.307l1.196-.387c.524-.167.953-.757.953-1.306V9.199C17 8.646 16.352 8 15.8 8z"></path>
      </symbol>

      <symbol viewBox="0 0 20 20" id="locked">
        <path d="M15.8 8H14V5.6C14 2.703 12.665 1 10 1 7.334 1 6 2.703 6 5.6V8H4c-.553 0-1 .646-1 1.199V17c0 .549.428 1.139.951 1.307l1.197.387C5.672 18.861 6.55 19 7.1 19h5.8c.549 0 1.428-.139 1.951-.307l1.196-.387c.524-.167.953-.757.953-1.306V9.199C17 8.646 16.352 8 15.8 8zM12 8H8V5.199C8 3.754 8.797 3 10 3c1.203 0 2 .754 2 2.199V8z"/>
      </symbol>

      <symbol viewBox="0 0 20 20" id="close">
        <path d="M14.348 14.849c-.469.469-1.229.469-1.697 0L10 11.819l-2.651 3.029c-.469.469-1.229.469-1.697 0-.469-.469-.469-1.229 0-1.697l2.758-3.15-2.759-3.152c-.469-.469-.469-1.228 0-1.697.469-.469 1.228-.469 1.697 0L10 8.183l2.651-3.031c.469-.469 1.228-.469 1.697 0 .469.469.469 1.229 0 1.697l-2.758 3.152 2.758 3.15c.469.469.469 1.229 0 1.698z"/>
      </symbol>

      <symbol viewBox="0 0 20 20" id="large-arrow">
        <path d="M13.25 10L6.109 2.58c-.268-.27-.268-.707 0-.979.268-.27.701-.27.969 0l7.83 7.908c.268.271.268.709 0 .979l-7.83 7.908c-.268.271-.701.27-.969 0-.268-.269-.268-.707 0-.979L13.25 10z"/>
      </symbol>

      <symbol viewBox="0 0 20 20" id="large-arrow-down">
        <path d="M17.418 6.109c.272-.268.709-.268.979 0s.271.701 0 .969l-7.908 7.83c-.27.268-.707.268-.979 0l-7.908-7.83c-.27-.268-.27-.701 0-.969.271-.268.709-.268.979 0L10 13.25l7.418-7.141z"/>
      </symbol>

      <symbol viewBox="0 0 24 24" id="jump-to">
        <path d="M19 7v4H5.83l3.58-3.59L8 6l-6 6 6 6 1.41-1.41L5.83 13H21V7z"/>
      </symbol>

      <symbol viewBox="0 0 24 24" id="expand">
        <path d="M10 18h4v-2h-4v2zM3 6v2h18V6H3zm3 7h12v-2H6v2z"/>
      </symbol>

    </defs>
  </svg>

Expected Generated Code
NestJS/TypeScript API built using @nestjs/swagger lib, running at http://localhost:3000
Steps to reproduce:

Ran command: fern init --openapi http://localhost:3000/api
fern dir generates, but with problematic data

One glaring issue is that it seems like HTML code got generated and put into a .yml file - also, at line 1 there's a leading ">" char which shouldn't be there
UPDATE:
You know what, I just realized that I passed in the URL for the actual UI of the swagger doc, when I needed to pass in the endpoint for just the JSON or YML... so dumb.
I'd recommend having an error/warning that throws at run time when trying to consume the data to ensure that it's either JSON or YML and not the actual HTML page 👍
CONCLUSION:
Not a bug, instead, this is maybe a feature suggestion that'll drastically improve DX with some pretty minimal effort
UPDATE:
Never mind, there is still a bug - ran the code against the proper yaml endpoint and I'm still getting an error:

Ran command: fern init --openapi http://localhost:3000/api-yaml
fern dir got generated, and openapi.yml looks much better, but there was a leading "|" char which broke the code and the subsequent call to fern generate --> error: [api]: Document must be JSON object, got string

After manually editing the openapi.yml and removing the "|" and then re-running the fern generate command - I was able to get the typescript sdk to successfully generate
UPDATE:
Ran the code against NestJS/Swagger's /json endpoint and the fern init --openapi http://localhost:3000/api-json command worked flawlessly in generating the fern/openapi/openapi.yml file
With that said, this bug seems isolated to the yaml endpoint. One thing to note is that this library uses the .yaml file extension vs fern's .yml -- not sure if this is causing the problem, but just something to bring attention to (figured it's worth bringing up since the issue seems related to a single character being off)

FINAL CONCLUSION:

Fix the fern init command when consuming yaml-based documents that are being served via localhost to ensure that there is no leading "|" char which leads to invalid yaml
Add a simple validator when user runs the fern init command to ensure they aren't running the code against their swagger HTML page (I'm guilty of doing this now on two separate occasions)

Environment Details (Optional)
macOS 14.5, Node.js v23.3.0

@dannysheridan Was able to recreate the bug! Check it out 👍

I think this should be split out into it's own Bug report. I've ran into this before where it fails fern check, has an unclear error message as to why, and then finally I figure out I need to remove the leading "|".

Fix the fern init command when consuming yaml-based documents that are being served via localhost to ensure that there is no leading "|" char which leads to invalid yaml

I think this should be split out into a Feature request.

Add a simple validator when user runs the fern init command to ensure they aren't running the code against their swagger HTML page (I'm guilty of doing this now on two separate occasions)

Once you open those two issues, let's close this one.

@dannysheridan Done!
https://github.com/fern-api/fern/issues/5342
https://github.com/fern-api/fern/issues/5343


Add version capabilities to Pipeline

Add a numeric version field to the Pipeline json file
and enable in-place migration when reading an old
pipeline version
Fixes #647
Note: to be merged after #656
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

I believe the one open question I have is regarding in-place auto update versus ask for confirmation before update.

With the recent updates, we now ask for user confirmation before migrating the pipeline

The only remaining issue is to close the "tab" if user cancel the migration.

The most recent dialogs:
Migration to recent version is needed:

Newer version found, Elyra needs to be upgraded:


Emptying TextInput by pressing Enter causes app to crash on Windows

Description
Empty TextField value in TextField's on_submit causes app to crash.
I encountered this problem when we ran the sample code on Windows, which worked fine in the browser.
Code example to reproduce the issue:
import flet as ft

class Message():
    def __init__(self, user_name: str, text: str, message_type: str):
        self.user_name = user_name
        self.text = text
        self.message_type = message_type

class ChatMessage(ft.Row):
    def __init__(self, message: Message):
        super().__init__()
        self.vertical_alignment="start"
        self.controls=[
                ft.CircleAvatar(
                    content=ft.Text(self.get_initials(message.user_name)),
                    color=ft.colors.WHITE,
                    bgcolor=self.get_avatar_color(message.user_name),
                ),
                ft.Column(
                    [
                        ft.Text(message.user_name, weight="bold"),
                        ft.Text(message.text, selectable=True),
                    ],
                    tight=True,
                    spacing=5,
                ),
            ]

    def get_initials(self, user_name: str):
        return user_name[:1].capitalize()

    def get_avatar_color(self, user_name: str):
        colors_lookup = [
            ft.colors.AMBER,
            ft.colors.BLUE,
            ft.colors.BROWN,
            ft.colors.CYAN,
            ft.colors.GREEN,
            ft.colors.INDIGO,
            ft.colors.LIME,
            ft.colors.ORANGE,
            ft.colors.PINK,
            ft.colors.PURPLE,
            ft.colors.RED,
            ft.colors.TEAL,
            ft.colors.YELLOW,
        ]
        return colors_lookup[hash(user_name) % len(colors_lookup)]

def main(page: ft.Page):
    page.horizontal_alignment = "stretch"
    page.title = "Flet Chat"

    def join_chat_click(e):
        if not join_user_name.value:
            join_user_name.error_text = "Name cannot be blank!"
            join_user_name.update()
        else:
            page.session.set("user_name", join_user_name.value)
            page.dialog.open = False
            new_message.prefix = ft.Text(f"{join_user_name.value}: ")
            page.pubsub.send_all(Message(user_name=join_user_name.value, text=f"{join_user_name.value} has joined the chat.", message_type="login_message"))
            page.update()

    def send_message_click(e):
        if new_message.value != "":
            page.pubsub.send_all(Message(page.session.get("user_name"), new_message.value, message_type="chat_message"))
            new_message.value = ""
            new_message.focus()
            page.update()

    def on_message(message: Message):
        if message.message_type == "chat_message":
            m = ChatMessage(message)
        elif message.message_type == "login_message":
            m = ft.Text(message.text, italic=True, color=ft.colors.BLACK45, size=12)
        chat.controls.append(m)
        page.update()

    page.pubsub.subscribe(on_message)

    # A dialog asking for a user display name
    join_user_name = ft.TextField(
        label="Enter your name to join the chat",
        autofocus=True,
        on_submit=join_chat_click,
    )
    page.dialog = ft.AlertDialog(
        open=True,
        modal=True,
        title=ft.Text("Welcome!"),
        content=ft.Column([join_user_name], width=300, height=70, tight=True),
        actions=[ft.ElevatedButton(text="Join chat", on_click=join_chat_click)],
        actions_alignment="end",
    )

    # Chat messages
    chat = ft.ListView(
        expand=True,
        spacing=10,
        auto_scroll=True,
    )

    # A new message entry form
    new_message = ft.TextField(
        hint_text="Write a message...",
        autofocus=True,
        shift_enter=True,
        min_lines=1,
        max_lines=5,
        filled=True,
        expand=True,
        on_submit=send_message_click,
    )

    # Add everything to the page
    page.add(
        ft.Container(
            content=chat,
            border=ft.border.all(1, ft.colors.OUTLINE),
            border_radius=5,
            padding=10,
            expand=True,
        ),
        ft.Row(
            [
                new_message,
                ft.IconButton(
                    icon=ft.icons.SEND_ROUNDED,
                    tooltip="Send message",
                    on_click=send_message_click,
                ),
            ]
        ),
    )

ft.app(port=8550, target=main)

Describe the results you received:
No error and Crash App.
Describe the results you expected:
I want the value of TextInput to be empty when the Enter key is pressed when input is complete.
The application should not crash at this time.
Additional information you deem important (e.g. issue happens only occasionally):
The Enter key is the trigger.
If the same method is executed from the Submit button, this error will not occur.
Flet version (pip show flet):
Name: flet
Version: 0.7.1
Summary: Flet for Python - easily build interactive multi-platform apps in Python
Home-page:
Author: Appveyor Systems Inc.
Author-email<EMAIL_ADDRESS>License: Apache-2.0
Location: d:\github\testflet\.venv\lib\site-packages
Requires: packaging, oauthlib, websockets, httpx, flet-core, websocket-client, watchdog
Required-by:

Operating system:
Windows11
Additional environment details:

Add information.
For the time being, it seems that this event can be avoided by giving up using shift_enter.
Therefore, the conflict with shift_enter may be the cause.

I also encountered this situation on onsubmit version 0.7.4. As long as the value of this text box is changed in onsubmit, the program will crash. Because there are no logs, it is impossible to know what happened.

Is the bug still present in the latest flet version?


BLUESKY: unable to authenticate with domain handle

Sorry for the spartan bug report. I am on mobile.
I use<EMAIL_ADDRESS>as my handle at BlueSky. I am unable to authenticate from this page.
I was able to get this working by using my DID, which is a TXT record off my tedt.org that BlueSky uses to validate I own the domain name.  Brid.gy then gets my name right and works ok.
I suspect you don't have a case in the code to do the DNS lookup.
https://brid.gy/bluesky/start

Hmm, sorry for the trouble! Looks like you're @tedt.org on Bluesky. I'll look into it.

No troubles.  I might have been "Holding it wrong"
But once I got the DID, as I saw it was looking that up in the Error Messages, everything worked.  I also didn't quite know what format you wanted the handle in.  Was it @tedt.org or<EMAIL_ADDRESS>or<EMAIL_ADDRESS>or or or or...
Perhaps this defect is a UI/UX 'error'

Bluesky handles are just domains, not email addresses or fediverse-style webfinger addresses, so your Bluesky handle is tedt.org, or stylized, @tedt.org.
Bridgy has a couple bugs to fix here. First, it needs to validate handles better, including stripping any leading @. Second, it needs to convert input handles to lower case before using them in Bluesky API calls.
We'll fix both of those. Thanks again for reporting!

Yep, looks like I'm in this boat too. Seeing your comment and changing TechLifeWeb.bsky.social to lower case enabled me to authenticate.

Fixed! Thanks again for reporting!


Adds first pass at jupyter magic

To use:
%load_ext hamilton.plugins.jupyter_magic

%%with_functions -m MODULE_NAME
def my_hamilton_funcs(): ...

The above directive does three things:

it creates a module with the contents of this cell
it imports the module under the name MODULE_NAME.
if changes are made to the module, it will be reloaded automatically. If you constructed a driver with this module, you won't need to re-create it (in most cases). Note, it skips the case where adapters are passed because I couldn't get it to work. We should think about what to change to make the internal APIs less dependend on here. I don't think this will support multi-processing drivers either.

Changes

adds to plugins

How I tested this

ran it locally

Notes
Checklist

[ ] PR has an informative and human-readable title (this will be pulled into the release notes)
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future TODOs are captured in comments
[ ] Project documentation has been updated if adding/changing functionality.

My current API
# %%cell 1
%load_ext hamilton_magic  # add Stefan's plugin import structure

# %%cell 2
%%cell_to_module -m my_cell -v True

def hello() -> str:
    return "hello"

def world(hello: str) -> str:
    return hello + " " + "world"

The option -m specifies a module name that will exist in the notebook space and -v is for "view" and any value will automatically call display_all_functions()
Code snippets:
from hamilton import ad_hoc_utils, driver

def create_module(source: str) -> ModuleType:
    """Create a temporary module from source code"""
    module_name = ad_hoc_utils._generate_unique_temp_module_name()
    module_object = ModuleType(module_name, "")
    sys.modules[module_name] = module_object
    exec(source, module_object.__dict__)
    return module_object

@magics_class
class HamiltonMagics(Magics):
    """Magics to facilitate Hamilton development in Jupyter notebooks"""

    @magic_arguments()  # needed on top to enable parsing
    @argument("-m", "--module_name", help="Optional module name.")  # keyword / optional arg
    @argument("-v", "--view", help="Flag to visualize dataflow.")  # keyword / optional arg
    @cell_magic
    def cell_to_module(self, line, cell):
        """Compile the cell as a module and make it available to notebook"""
        self.shell.ex(cell)

        args = parse_argstring(self.cell_to_module, line)  # specify how to parse by passing method
        module_name = "jupyter" if args.module_name is None else args.module_name
        module_object = create_module(cell)
        self.shell.push({module_name: module_object})

        if args.view:
            dr = driver.Builder().with_modules(module_object).build()
            return display(dr.display_all_functions(None))

@elijahbenizzy should allow by default .enable_dynamic_execution(allow_experimental_mode=True) in the Builder we use behind the scene? are there downsides to having the Parallel mode on?


[iOS] hello-gltf example crashes at loadResources.

Describe the bug
Post setting up the iOS Project hello-gltf sample, and running with DamagedHelmet.glb as asset App crashes.
To Reproduce

Build Filament project v1.26.0 as described in its Readme and iOS Readme file.
Build iOS Project hello-gltf.xcodeproj located under ios/samples for filament v1.26.0

Expected behavior
No Crash should be observed.
Screenshots

Logs
2022-09-01 18:43:52.583117+0530 hello-gltf[649:83044] Metal API Validation Enabled
FEngine (64 bits) created at 0x106027a00 (threading is enabled)
FEngine resolved backend: Metal
Selected physical device 'Apple A14 GPU'
FEngine feature level: 1
Missing texture provider for image/jpeg
Missing texture provider for image/jpeg
Missing texture provider for image/jpeg
Missing texture provider for image/jpeg
Missing texture provider for image/jpeg
Desktop (please complete the following information):

OS: iOS
GPU: Inbuilt
Backend: Metal

Smartphone (please complete the following information):

Device: iPhone 12
OS: iOS 15.3.1

Additional context

I also tried other glb and gltf files located in thirdparty/models folder AnimatedTriangle.gltf and lucy.glb, but similar issue persists.

Interesting, I'm able to load DamagedHelmet.glb without any issues. However, I don't see the missing texture provider warnings, which might be relevant. @kaustubh-seachange can you confirm this line is present in your build?
    _resourceLoader->addTextureProvider("image/jpeg", _stbDecoder);

Thanks @bejado for quick reply, this line doesnt exist in the Hello-gltf.xcodeprroj. _resourceLoader->addTextureProvider("image/jpeg", _stbDecoder);


add @interval feature

Sometimes we want only one job working at the same time, but when the time you cost in once the job is longer than your job interval time, you may have mutilated job working at the same time.
So the @interval schedule can help, each job will be executed at the interval time after the previous job is completed.

Sorry, I'm not interested in adding non-standard extensions.
There is a related feature already implemented: DelayIfStillRunning, introduced in https://github.com/robfig/cron/commit/d279950244fbe93cdf8ea3639e120551ca4068f3


Template params break url encoded strings

Environment
main branch
Reproduction
diff --git a/test/fixtures.ts b/test/fixtures.ts
index 111dc51..56bf241 100644
--- a/test/fixtures.ts
+++ b/test/fixtures.ts
@@ -38,6 +38,10 @@ export const basicSchema: Head = {
     {
       charset: 'utf-8',
     },
+    {
+      property: 'twitter:image',
+      content: 'https://cdn.example.com/some%20image.jpg'
+    }
   ],
   link: [
     {

Describe the bug
The templateParams plugin incorrectly assumes the %20 is a template parameter and tries to replace it, causing the content value to be truncated to just https://cdn.example.com/some

Additional context
Possible solutions:

decode strings before searching for template params
ignore template params for which no replacement value was configured

Logs
FAIL  test/unhead/ssr/ssr.test.ts > ssr > basic
AssertionError: Snapshot `ssr > basic 1` mismatched
 ❯ test/unhead/ssr/ssr.test.ts:18:17
     16|
     17|     const ctx = await renderSSRHead(head)
     18|     expect(ctx).toMatchInlineSnapshot(`
       |                 ^
     19|       {
     20|         "bodyAttrs": " class=\\"dark\\"",

  - Expected  - 0
  + Received  + 1

      bodyTags": "",
      "bodyTagsOpen": "",
      "headTags": "<meta charset="utf-8">
    <script src="https://cdn.example.com/script.js"></script>
  + <meta property="twitter:image" content="https://cdn.example.com/some">
    <link rel="icon" type="image/x-icon" href="https://cdn.example.com/favicon.ico">",
      "htmlAttrs": " lang="de"",
    }

Thanks for the detailed issue @pimlie
This is fixed in 1.1.23

Awesome, can confirm it works. Thx for the quick fix!


Rename target iree_opt_library to iree_opt_main

The target iree_opt_library includes a main function. Hence, renaming.

Rebased onto master, should be ready to pull.

Looks like you missed some additional uses in the integrations directory, e.g.
https://sourcegraph.com/github.com/google/iree/-/blob/integrations/tensorflow/compiler/BUILD
Could you get those as well please?

Thanks for catching this! I missed to grep through the integrations subdirectory. Fixed that as well for the iree-tf-translate target in #903.


**add_options invalid syntax

Installing syncarr on Ubuntu server 18.04, when executing the command 'python index.py' i get
File "index.py", line 64
**add_options,
^
SyntaxError: invalid syntax
Version
pulled 4/25/2020
Config
[radarr]
url = http://radarr.mydomain.com
key = xxxxxxxx
profile_id = 1
path = /mnt/unionfs/Media/Movies
[radarr1080remux]
url = http://radarr1080remux.mydomain.com
key = xxxxxxxx
profile_id = 1
path = /mnt/unionfs/Media/Movies1080
[general]
sync_bidirectionally = 0
Debug logs
Enable debugging with
[general]
log_level=10

or for docker LOG_LEVEL=10

Additional context
Add any other context about the problem here.

check your python version


Page not reloaded on logout in another tab

When the storageChangedReload is set to true in the config file. There is no reload of pages that are opened in other tabs.
Is it possible to reload all the tabs on a logout() event?

@ShauniArima Not that I'm aware of. I know someone did something similar, but I can't remember the outcome.

@RWOverdijk It seems like storage events are not triggered when the logout() remove the key in the storage...

Interesting. The next click should log the user out though, right?

Yes the logout works fine but the others tabs are not reloaded. The user is redirected to the login page on the next token refresh.

Hm... If you find an answer to this, please do share.

Yes, I will investigate. Thanks for your help!

the fix of https://github.com/SpoonX/aurelia-authentication/issues/327 causes this. the problem here was actually anticipated. maybe we'll find a better fix for issue327


add note/c_abi.md

Signed-off-by: dm4<EMAIL_ADDRESS>

@dm4 seems like our stack build ci should not run in this case, maybe let it only triggered by *.hs and *.cabal?


Stop auto-formatting package.json files

Codecov Report

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

@@           Coverage Diff           @@
##           master     #144   +/-   ##
=======================================
  Coverage   91.13%   91.13%
=======================================
  Files          81       81
  Lines        1049     1049
  Branches      168      168
=======================================
  Hits          956      956
  Misses         77       77
  Partials       16       16

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 7ee246c...49b0a6f. Read the comment docs.


Research object support

Plan

[ ] depend on https://github.com/ResearchObject/ro-python
[ ] similar to snakemake --report, create research objects on request, from the info that is already captured via the persistence module under .snakemake

Hi, I would be happy to contribute and provide source code on that topic (in particular provenance / PROV-O).

@albangaignard your help is greatly appreciated. I have added a skeleton. Basically, one just needs to feed the information that is retrieved in the skeleton with the python-ro API.

This would be a nice addition to snakemake. How does this compare to cwlprov and dataprov?

This would be a nice addition to snakemake. How does this compare to cwlprov and dataprov?

Thanks very much for your feedback. This would be completely in line with the PROV profile of CWLprov (https://github.com/common-workflow-language/cwlprov/blob/main/prov.md). Regarding dataprov the approach is interesting but apparently it does leverage a standard for representing provenance metadata as proposed by the W3C (https://www.w3.org/TR/prov-primer/).

@johanneskoester, I recently reviewed the code quality based on the automatic checks (SonarCloud), and code formatting best practicies (Black tool). Would you have time to review this pull request ?
In summary :

--provenance option
provenance capture in the AbstractExecutor,
two provenance serializations (RDF and JSON) in the working directory

I am so sorry for the late response. This completely slipped my attention (I get so many Github notifications that I sometimes miss one). Nice work, please see my comments above.


Release/3.0.0

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@8882d9c). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #563   +/-   ##
=======================================
  Coverage        ?   63.93%
=======================================
  Files           ?       50
  Lines           ?     1877
  Branches        ?        0
=======================================
  Hits            ?     1200
  Misses          ?      677
  Partials        ?        0

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


swaylock-plugin: init at 1.8.0

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Opened a PR upstream to fix the maybe-unitialized GCC error there: https://github.com/mstoeckl/swaylock-plugin/pull/14

Upstream merged the above PR, I'm considering pointing to the current main HEAD instead of the latest release :thinking:

Good catch for the bash completion issue. I'll have a look at that tonight.


add badges to README

The Circle CI badge is not here yet. It has some display issues since we haven't even set the CI up.
Will add it back once we finished CI setup.

Blocked by PR https://github.com/pairmesh/pairmesh/pull/28.


bandmath added to orders

Even without specifying a bandmath operation, it is added to order:
{
"bandmath": {}
}

I think this is fixed in master: https://github.com/samapriya/porder/commit/ef0afd76554b0bc7f4ed406f83f210f44faf1f71


High Unicode values (>= 0x010000) not supported

Copied from Felix Meschberger's bug report at SourceForge.net: https://sourceforge.net/p/kxml/bugs/17/
Currently high Unicode values >= 0x01000 (outside the 16bit range) are not supported correctly. When parsing a character reference &#x; the high value should be stored as a surrogate pair. When serializing the surrogate pair should be stored as a single character reference &#x;.
A patch is attached to the original bug report, see link above

Fixed with commit 49758b466ca9a20069bdab3518f6e4c8cb12d6b0


Amend pnpm_lock_sync_test to fail anytime pnpm is sad (not just if the lockfile is out of date)

Amend pnpm_lock_sync_test to fail anytime pnpm is sad (not just if the lockfile is out of date)
Move pnpm test into presubmit (it breaks out of the sandbox)
Amend pnpm lock sync test accounting for upstream fix.
https://github.com/pnpm/pnpm/issues/6913#event-10016924188
Revert all changes to package.json since lockfile test was broken.

Stack created with Sapling. Best reviewed with ReviewStack.

#3603
-> #3606

This IS currently broken, but I don't want anything else being pushed to main, because Mend is still generating patches that don't have lockfile changes in them.

rip to the build


How to get TOC info after open a book?

I have successfully opened a book using readium-js.
I looked through readium object and readium.reader, but none of them contain data of TOC?
Where should I look at?
Thanks.

Hi @hz0324
You would think that it would be there but it's actually a part of the packageDocument object.
You get an instance of that as the first param value of the callback when you call openPackageDocument.
readium.openPackageDocument('someEbookUrl', function(packageDocument, options) {
    packageDocument.generateTocListDOM(function(tocDocument) {
        $(navDocDom).find('li > a').each(function() {
            console.log($(this).text(), $(this).attr('href'));
        });
    });
}, somePageRequest);

There are some edge cases to account for in the code snippet above.
If you would prefer to get data back in a JSON format like this:
https://github.com/readium/readium-2/blob/develop/readium1-data-samples/accessible-epub-3 /toc.json
Then I have some new code for that, but I need to make a pull request for it.

Thank you for your excellent answer, it is really helpful.
I appreciate it a lot. ^_^

By the way, is there a doc about this?

We have this site:
http://readium.github.io/index.html
That has an API reference link on the side, but it looks to be outdated or has missing info.
http://readium.github.io/api/index.html

Yep, they are not enough for deep usage


Feat(eos_validate_state): Add ANTA integration to eos_validate_state role

Change Summary
Integration of ANTA Python framework to eos_validate_state role.
Tasks List

[X] (hardware) Validate environment (power supplies status)
[X] (hardware) Validate environment (fan status).
[X] (hardware) Validate environment (temperature).
[X] (hardware) Validate transceivers manufacturer.
[X] (NTP) Validate NTP status.
[X] (interface_state) Validate Ethernet interfaces admin and operational status.
[X] (interface_state) Validate Port-Channel interfaces admin and operational status.
[X] (interface_state) Validate VLAN interfaces admin and operational status.
[X] (interface_state) Validate VXLAN interfaces admin and operational status.
[X] (interface_state) Validate Loopback interfaces admin and operational status.
[X] (lldp_topology_fqdn) Validate LLDP topology when there is a domain name configured.
[X] (lldp_topology_no_fqdn) Validate LLDP topology when there is no domain name configured.
[X] (MLAG) Validate MLAG status.
[X] (ip_reachability) Validate IP reachability (on directly connected interfaces).
[X] (loopback_reachability) Validate loopback reachability (between devices).
[X] (bgp_check) Validate ArBGP is configured and operating.
[X] (bgp_check) Validate IP BGP and BGP EVPN sessions state.
[X] (reload_cause) Validate last reload cause. (Optional)

Change of behavior as now there is a new reload cause that is valid: https://github.com/arista-netdevops-community/anta/blob/main/anta/tests/system.py#L72C1-L75C11

[X] (routing_table) Validate remote Lo0 addresses and remote Lo1 addresses are in the routing table (based on devices type).
[x] schema -> probably not needed as part of this PR except if we want to add the 3 accepted_ values - later discussion
[x] make eos_validate_state agnostic of eos_designs -> by adding knobs in structured_config where it is required #1047 - will be addressed after this PR
[x] discuss mode strict behavior (vs mode loose) - not implemented for anta mode
[x] Usage of display (ansible future proofing) ? Do we need all of them that exist today or are some present only because of the impossibility to remove "skipped" messages on Ansible -> make it a logger
[x] Release tag for anta - with CACHE
[x] Use check flag in ansible
[x] module documentation -> DONE need review - the module is considered as preview
[ ] eos_validate_state preview validation -  make the "feature" a preview for first release

[x] add warning to state that loose mode is ignored
[x] Add all input variables as per documented in the current overview document

[ ] testing current eos_validate_state and anta based eos_validate_test and make sure there is no change - document the changes for the tests
[x] Use anta variable instead of tag for running eos_validate_state.
[x] Fixes #3138

Postponed Tasks List

[ ] fix loopback_reachability tags support when running anta -> PR for existing validate state + rebase.
[ ] Remove even further the ties to ansible in the plugins_utils
[ ] Hardware tests are now grouped together in the final report. Will need to add a functionality in ANTA to get more specific results per test.
[ ] Adding  unit tests for module and Handler
[ ] https://github.com/aristanetworks/ansible-avd/issues/3182
[ ] https://github.com/aristanetworks/ansible-avd/issues/3183
[ ] https://github.com/aristanetworks/ansible-avd/issues/3188
[ ] https://github.com/aristanetworks/ansible-avd/issues/3189

Component(s) name
arista.avd.eos_validate_state
Proposed changes

eos_validate_state_runner.py is an action plugin to run the ANTA framework. It calls the get_anta_results function to grab the test results.
get_anta_results.py is responsible of creating the ANTA tests catalog and the other required objects to run ANTA.
Connections to the devices are made with the regular Ansible httpapi connection plugin.
Results from ANTA are returned as JSON and registered as the anta_results variable in Ansible.
ANTA related tasks have been added to eos_validate_state tasks/main.yml and tagged anta to keep the legacy eos_validate_state working.
A new task has been added to tasks/reports.yml to generate ANTA results, leveraging yaml_templates_to_facts plugin and template/generate_anta_report_results.j2 template specific to ANTA results but keeping the same format.
The following Python classes have been created to replace the existing eos_validate_state tests:

__all__ = [
    "AvdTestP2PIPReachability",
    "AvdTestLoopback0Reachability",
    "AvdTestLLDPTopology",
    "AvdTestInbandReachability",
    "AvdTestHardware",
    "AvdTestMLAG",
    "AvdTestNTP",
    "AvdTestReloadCause",
    "AvdTestInterfacesState",
    "AvdTestRoutingTable",
    "AvdTestBGP",
]

How to test

Install the main branch of anta:
pip install git+https://github.com/arista-netdevops-community/anta.git
eos_validate_state can be used as usual, with --tags anta if you want to run the role with ANTA:
ansible-playbook playbooks/fabric-validate.yaml --tags anta
Not providing the anta tag will run the regular eos_validate_state
Legacy Ansible tags are also supported if you want to run/skip tests:
ansible-playbook playbooks/fabric-validate.yaml --tags anta,routing_table

The variable skipped_tests can now be used for running/skipping tests:
skipped_tests:
    AvdTestHardware:

You can also decide to skip specific subtests (ANTA test) for more granularity:
skipped_tests:
    AvdTestHardware:
        - VerifyTransceiversTemperature

Checklist
User Checklist

N/A

Repository Checklist

[X] My code has been rebased from devel before I start
[X] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation and documentation have been updated accordingly.
[ ] I have updated molecule CI testing accordingly. (check the box if not applicable)

Remove anta_ from the module parameters

In my tests, when I set dc2-leaf1c and dc2-leaf2c (the L2 leave) and set shutdown_interfaces_towards_undeployed_peers: True, I noticed:

the interface check on interfaces towards the L2 Leafs were set to check for 'down' status as expected
The LLDP neighborchip check on L3 Leafs still expected to find the L2 Leaf downstream I think this is a bug

When an interface is shutdown, I can still see VerifyReachability tests created for the peer IP address on that interface.
This is an existing behaviour in current eos_validate_state that has caused confusion/grip about false positives before as well.

Similarly - when an interface is shutdown, the BGP peer check VerifyBGPSpecificPeers is still created for the peer on that interface. Is this in scope to be solved in this PR ? Without this, we would still have false positive when some devices are not still deployed.

When the devices are not present, I see that the eos_validate_state was successful , even though these devices are not reachable. I would expect that the task Run eos_validate_state_runner leveraging ANTA would fail for unreachable devices.

VerifyRoutingProtocolModel is being run on devices that do not have BGP configuration which is not the actual behavior of eos_validate_state.

When an interface is shutdown, I can still see VerifyReachability tests created for the peer IP address on that interface. This is an existing behaviour in current eos_validate_state that has caused confusion/grip about false positives before as well.

https://github.com/aristanetworks/ansible-avd/issues/3182

When the devices are not present, I see that the eos_validate_state was successful , even though these devices are not reachable. I would expect that the task Run eos_validate_state_runner leveraging ANTA would fail for unreachable devices.

@chetryan Fixed in dd1c8c0
The task should fail and stop the play if the device is unreachable or there is a connection problem (e.g. wrong password or SSL problem).
Also, if for some reason we lose connectivity to the device during the tests, you should see a log with the failed commands and the tests associated with the failed commands will be marked as FAIL in the report.
It would be great if you can confirm these behaviors on your end.
Thanks

Follow up to this PR is tracked in avd-internal repo: https://github.com/aristanetworks/avd-internal/issues/119


i18n: Added and changed Dutch translations

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for validating the changes?
[ ] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[ ] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry
Description

Added and changed Dutch translations. Now all strings are translated and I've changed some strings to sound better to me.

Added

All missing translations

Changed

Some translations

Deprecated

[List any deprecated functionality or features that have been removed]

Removed

[List any removed features, files, or functionalities]

Fixed

[List any fixes, corrections, or bug fixes]

Security

[List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

[Insert any additional context, notes, or explanations for the changes]

[Reference any related issues, commits, or other relevant information]

Screenshots or Videos

[Attach any relevant screenshots or videos demonstrating the changes]

Thanks!


Failure: hostname cannot be empty

I updated portainer on my server, after that I wanted to change the ldap settings and got this error:
Failure hostname cannot be empty.
In logs:
http error: Invalid request payload (err=hostname cannot be empty) (code=400)
I tried to disable ldap, but I got the same message. Reinstalling portainer completely didnt help.

I am seeing this same error on a fresh Portainer-CE  standalone deployment.
The error pops up on the settings page when trying to save after adding a custom logo URL.

I am seeing this error as well on an updated Portainer-CE. Error occurs when I try to save a change to the App Templates URL. Any change to settings page causes this?

Same error here on 2.13.0, completely fresh install on a new machine, cannot change the App Templates URL.
http error: Invalid request payload (err=hostname cannot be empty) (code=400)

Also experiencing same error, after updating to 2.13.0 mine is also a fresh installation.
Environment:
Debian GNU/Linux 11 (bullseye 64bit)
OMV6
Portainer 2.13.0

As a workaround, does it work if you set a bogus ldap server?

nope, even with ldap set up it still gives the same error (I wanted to link my portainer to my ipaserver to get around the new password rules #6904, that way I would at least have the same rules everywhere...)

I can confirm the issue.
All changes in "Settings" are blocked. We actual use the LDAP-Auth. So all fields (ce-version) are filled.
We rollbacked from 2.13.0-alpine to 2.11.1-alpine. After this all was working fine again.

Wanted to add, hostname cannot be empty is also thrown when I try to change the app template url in Portainer CE after updating to 2.13.0

I can confirm the issue.
Same error when trying to set up OAuth Provider in Portainer CE 2.13.
It seems that all changes in settings are blocked. Rollback to 2.11.1.

seeing this on 2.13 as well when trying to save custom oauth provider

No go, I just restarted docker, did a Portainer pull, cleared cache/cookie, still getting error: "Failure
hostname cannot be empty."
Let me know if there is any information you may need to help troubleshoot this issue.

I, too, am getting the same error. Fresh installation.

i can confirm, version 2.13.1 is fixed

Raspberry PI4B; Raspbian GNU/Linux 11
cat /etc/debian_version
11.3
Linux Docker 5.15.32-v7l+ #1538 SMP Thu Mar 31 19:39:41 BST 2022 armv7l GNU/Linux
I did upgrade from 2.13.0 to 2.13.1 and cannot access portainer GUI on 9443 port. Did try to set 9000 port the same
I did install again 2.13.0 and works again.
conclusion there is again a bug in 2.13.1
docker stop portainer
docker rm portainer
docker pull portainer/portainer-ce:2.13.0
docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:2.13.0
but portainer cointener check box is now grayout:

you should open a new issue for that.

That was changed on purpose in CE-2.11.1: https://github.com/portainer/portainer/issues/5121
Instead, to make port 9443 accessible, you can run:
docker run -d -p 8000:8000 -p 9000:9000 -p9443:9443 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:2.13.0

I just tried again to upgrade for5th time to 2.13.1 and now pointer GUI works but only on :9000

but portainer cointener check box is still grayout:


AttributeError: module 'openai' has no attribute 'Embedding'

I've installed openai via:
pip install openai
pip install --upgrade openai
and yet when I try to run an example like:
import openai
print(openai.Embedding)

I get the error
Traceback (most recent call last):
  File "/Users/travisbarton/.conda/envs/work3.6/lib/python3.6/site-packages/IPython/core/interactiveshell.py", line 3343, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-15-c5f5985add60>", line 1, in <module>
    openai.Embedding
AttributeError: module 'openai' has no attribute 'Embedding'

the version I have is 0.8.0
this happens for full examples, but this is just the most simple case.
any idea why?

Hey @Travis-Barton, thanks for the issue!
This repo is currently on version 0.15.0 which makes me think something is up with that upgrade command.  Does pip show openai show an up to date version?

@hallacy  It shows:
Name: openai
Version: 0.8.0
Summary: Python client library for the OpenAI API
Home-page: https://github.com/openai/openai-python
Author: OpenAI
Author-email<EMAIL_ADDRESS>License: UNKNOWN
Location: /Users/travisbarton/.conda/envs/work3.6/lib/python3.6/site-packages
Requires: requests, tqdm
Required-by: open-humans

Ah, python 3.6 would do it.
We stopped supporting python 3.6 so that we could support pandas 1.2 which requires python 3.7+.  That wasn't actually updated until 0.10.5 so the last version that works with 3.6 is 0.8.0.

That makes sense, thanks!

Try to use openai version 0.28.1
pip install openai==0.28.1


feat(date-picker): add panel icon slots

close #3570

Codecov Report

Merging #3713 (b7c0eda) into main (1747c36) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #3713      +/-   ##
==========================================
+ Coverage   62.84%   62.88%   +0.04%
==========================================
  Files        1058     1058
  Lines       22061    22086      +25
  Branches     5766     5766
==========================================
+ Hits        13864    13889      +25
  Misses       6698     6698
  Partials     1499     1499

Impacted Files
Coverage Δ

src/date-picker/src/DatePicker.tsx
62.06% <ø> (ø)

src/date-picker/src/panel/date.tsx
68.42% <100.00%> (+3.71%)
:arrow_up:

src/date-picker/src/panel/daterange.tsx
67.34% <100.00%> (+6.37%)
:arrow_up:

src/date-picker/src/panel/datetime.tsx
68.29% <100.00%> (+4.40%)
:arrow_up:

src/date-picker/src/panel/datetimerange.tsx
62.71% <100.00%> (+5.84%)
:arrow_up:

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


Added sdl2_ttf library to OSX install

without this lib, sbt run would produce the following errors
[error] ld: library not found for -lSDL2_ttf
[error] clang: error: linker command failed with exit code 1 (use -v to see invocation)

link to weird non-https appstore page describing sdl2_ttf
my autoformatter also picked up some whitespace inconsistencies near the bottom of the README, hope that's not a big deal :)

Looks great, thanks!


fix(remix): Deprecate loadUser, loadSession and loadOrganization on rootAuthLoader

Currently, rootAuthLoader types suggest the usage of loadUser, loadSession and loadOrganization boolean options. Using any of these will result to a call to Clerk Backend API on each root loader execution. This results in rate limiting issues for apps with many users and affects scalability.
This PR deprecates these 3 options so that they're not misused.
Relevant issue: #1043
Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

@anagstef @octoper I feel like these should have been removed with the Core 2 launch, was this an oversight on our part ?

@panteliselef Yes, we should have removed them.

I think we should also use the import { deprecated } from "@clerk/shared" to add a deprecation warning in the server logs.
cc: @anagstef


ctrl + enter doesn't work if gaps between CTEs

Is your feature request related to a problem? Please describe.
It seems I can either get code folding by putting spaces between each CTE or I can get the ctrl + enter functionality by not putting spaces between each CTE but cannot have both. Is it possible to get ctrl + enter to look further up when running.
Scenario 1: Space between each CTE:
✔ code folding  ❌ ctrl + enter

Scenario 2: No Space between each CTE
❌ code folding  ✔ ctrl + enter

If my mouse is in the middle of the cte_2 section, it seems it only tries to run these contiguous lines rather than running the code above and below.
, cte_2 as (
   select *
   from department
)

Describe the solution you'd like
I'd like ctrl + enter to look for statement delimiters and run all code in-between otherwise run the entire script
and
I'd like code folding to work at each set of parentheses, otherwise, it doesn't provide much use.
Describe alternatives you've considered
Highlighting all of the code each time (frustrating) or using a different IDE.

Hello @rjake
Can you disable "Blank line is statement delimiter" setting and then test again, please?

Test CTEs DDL will be very helpful also.

I see it now. Should I close the issue or will you?

@rjake
Thanks for feedback. I close.


[WFLY-7068] Typo in help for Infinispan subsystem

Jira: https://issues.jboss.org/browse/WFLY-7068
JBEAP 7.x JIRA: https://issues.jboss.org/browse/JBEAP-5031
JBEAP 7.x PR: https://github.com/jbossas/jboss-eap7/pull/841

Please link a 7.x PR as we are not merging changes to WildFly full without also updating 7.x.

@bstansberry done


YUNIKORN-450: Better representation of memory and vcores in yunikorn web

rebuild

hi @akhilpb001 can we change the vcore to CPU? Wonder if this makes sense to use the terminology closer to K8s: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#meaning-of-cpu.

hi @akhilpb001 can we change the vcore to CPU? Wonder if this makes sense to use the terminology closer to K8s: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#meaning-of-cp

@yangwwei  sure, we can change that.


Duplicate Dashboards

We currently do have multiple dashboards showing similar graphs - especially:

Mileage
Projected Range
Charge Level

While I do see additional value in Charge Level Dashboard with the additional data that has been added recently the Mileage Dashboard seems obsolete with having a Projected Range Dashboard that has Mileage in it's first graph.
Type of installation
Docker
Version
v1.30.1

Screenshots: https://docs.teslamate.org/docs/screenshots/

the Mileage Dashboard seems obsolete with having a Projected Range Dashboard that has Mileage in it's first graph.

I tend to agree. What do you think @DrMichael, should we remove Mileage Dashboard?

I tend to agree. What do you think @DrMichael, should we remove Mileage Dashboard?

Yes, fine with me. One could also think about the States dashboard...

One could also think about the States dashboard...

Yes and no, imo this is something to quickly check just the states, otherwise harder to find which dashboard does have the states, if you do not know overview or on mobile where overview is not ideal for checking states.

Ah, mobile is a good point...

If anyone comes up with a good name under which those 3 Dashboards could be combined I'll do it


To delay evaluation for newly created host

Proposal
Use case. Why is this important?
“Nice to have” is not a good use case. :)

Use case:
It filters unwanted alert getting triggered. Newly provisioned instances will take 5 mins atleast stabilize. If rules are evaluated before that time unwanted alerts gets triggered. This feature is very useful for cloud instances with ASG enabled.

This is something to handle in your rules themselves (such as a predicate on uptime), as Prometheus has no notion of hosts being created.
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


tools/test.dart seems to sometimes unable to kill subprocesses if they hit the timeout limit

It seems like tools/test.dart is sometimes unable to kill subprocesses if the test hits the timeout. From this log we know that this doesn't just happen with transitive subprocesses, but with the direct subprocess that tools/test.dart launches:
he debug timer of test.dart expired. Please report this issue to dart-engprod@ and provide the following information:

Graph is sealed: true

Count[Initialized] = 0
Count[Enqueuing] = 0
Count[Waiting] = 0
Count[Running] = 1
Count[Successful] = 3057
Count[Failed] = 212
Count[UnableToRun] = 818

Commands in state 'Running':
=================================

  Command: DART_CONFIGURATION=DebugSIMARM out/DebugSIMARM/dart_precompiled_runtime --enable-isolate-groups --disable-heap-verification --ignore-unrecognized-flags --packages=/b/s/w/ir/.packages /b/s/w/ir/out/DebugSIMARM/generated_compilations/dartkp/runtime_tests_vm_dart_isolates_ring_gc_sendAndExit_test/out.aotsnapshot
    Enqueued by: dartkp-dart_precompiled debug_simarm -- vm/dart/isolates/ring_gc_sendAndExit_test

Tentatively assigning to @whesse . Please re-assign if someone else is better to look at this.

Thanks for filing the issue.  I was starting to suspect that there was something like this going on - many recent problems giving infra failures seemed to have in common that the test runner was hanging (not making progress), even though every test and command should have had a firm timeout that would kill it and make progress.
I'll look into this, and see if I can find cases where it isn't working.  The biggest help would be reproducible test cases, but I can try and make them myself from the output of the failing runs.


What's the point of the size parameter?

Is it the number of cached input to output mappings?

Yes, it's for the tier-2 cache.
https://github.com/dai-shi/proxy-memoize/blob/44c7979b1923aba924587596e2d7d6b5d17817aa/README.md?plain=1#L57


Added and used AppiumElement

This allows, for the time being, the ability to call .click() on a returned Appium element. This is essential for developing future Appium calls that we will want to call as methods.

Any suite examples at this time? Plans for docs around the extra setup required for Appium suites?

Had not yet planned docs for extra setup, but I will now.
Here's a small suite example that currently works:
`import flagpole from "flagpole";
flagpole("Basic Smoke Test of Site", async (suite) => {
suite
.scenario("Homepage Loads", "appium", {
deviceName: "Android Emulator",
platformName: "Android",
automationName: "Uiautomator2",
app: "/Users/nick/Downloads/connect-<IP_ADDRESS>-staging-release.apk",
appWaitActivity:
"echelon_android.fitnation.viatek.com.echelon_android_new.SetupActivity",
})
.next(async (context) => {
context.comment("hello");
const hello = await context.find("id/pager_signin_button");
context.comment(hello);
context.assert(hello).exists();
hello.click();
const login = await context.find("id/username");
context.comment(login);
context.assert(login).exists();
});
});`


Add secretOptions to LogConfiguration

secretOptions is silently passed through to the underlying logConfiguration anyways. See https://github.com/pulumi/pulumi-aws/issues/1345. This just adjusts the typings to support it.

/run-acceptance-tests


Add do_not_annotate_directly to multi-organism process

Note we have this E coli gene that is annotated directly to MOP:
http://amigo.geneontology.org/amigo/reference/PMID:23667443
Can we not provide a more specific term in cases like this? cc @jimhu-tamu

This term is on my list for the next batch to block. I sent them in an e-mail to the QC group but I'll open a ticket instead.

no in this list for  blocking direct annotation
https://github.com/geneontology/go-ontology/issues/16101
I'll transfer to a spreadsheet soon for implementation

Direct annotation was removed - I now added the restriction.


Request for Edits

Hello! I stumbled across this datapack yesterday while I was searching for a superflat datapack that'd also retain the water in aquatic biomes like oceans and rivers, as all other superflat datapacks I've tried would just turn those biomes into barren empty plains, and yours does exactly what I've been looking for! If it wouldn't be too much to ask, I'd like if you could possibly make some edits to both the Flat Dimensions datapacks (both the one with and without caves) for me or show me how to make these edits myself, as I'm not sure what to edit to get each datapack to do what I'd like to change.
For the version without caves, I noticed a strange inconsistency while I was testing both this datapack and the version with caves. I use another datapack called Geophilic that adds extra decor to most overworld biomes like these spikes in Stony Shore biomes shown below, and these generate like normal when using the version with caves.

However, these don't generate when using the version without caves for some reason as you can see here:

To try and fix this, I tried using your No Caves datapack alongside the Flat Dimensions datapack with caves, and this fixes surface features like the stone spikes not generating. However, this then causes Ancient Cities to not generate at all for some reason. I'm assuming the simplest fix would be to take the version with caves and disable cave generation while retaining whatever code is allowing for surface features to still generate that isn't present in the version without caves, but I'm not sure what files to modify to do this. Could you help me figure this out?
And for the version with caves, could you help me make an edit to it that incorporates your Retro Caves datapack so that only the old caves and ravines will generate? I much prefer the old caves from a Survival standpoint as lighting up the new caves can be a bit of a chore, but attempting to use Retro Caves alongside Flat Dimensions with Caves results in the same bug I ran into when I tried using the No Caves datapack alongside it where Ancient Cities won't generate at all.
If it wouldn't be too much to ask, could we also make it so both these edited datapacks only affect the overworld instead of affecting all 3 dimensions? I've been using a datapack that affects the End dimension called Nullscape for a while and trying to use both it and either version of Flat Dimensions results in a game crash once the Ender Dragon is defeated as I found out while I was initially testing both datapacks yesterday, so ideally I'd like for just the overworld to be flat if possible.
Thank you for your time!

Thanks for responding so soon with a quick fix! I've gone and edited the base version of Flat Dimensions with your immediate fix and the modded surface features now properly generate again, with the added bonus of there being only the old caves and ravines generating below the surface. As a sidenote, one extra thing that also had to be removed that wasn't mentioned in your step process was the glowstone_extra.json file in the data/minecraft/worldgen/configured_feature folder. Leaving this file results in the desired vanilla nether dimension but filled with all the extra chunks of Glowstone floating around so it's definitely important to remove that file/folder too as part of making the datapack only affect the overworld.
Aside from that, yeah the immediate fix worked perfectly and I now have a version of the datapack that only affects the overworld with all the modded surface features and the desired old caves only, so the version with caves is all done and the only thing left that I'd like is a version of the datapack with no caves as well if possible. Thanks again for your responding so quickly with that immediate fix!

I have officially updated all versions to 1.20.5 and fixed the cave/biome incompatibility thing! Thanks for bringing this up.
Additionally, because of the new cave fix, you'll need to delete data/minecraft/worldgen/configured_carver/nether_cave.json to stop it from removing nether caves.


[No QA] Ping deployers when mobile prod deploys fail

Details
Ping mobile-deployers in #deployer when mobile prod deploys fail.
Fixed Issues
$ https://github.com/Expensify/App/issues/4955
Tests
Not 100% sure how to test this. Maybe the following:

Merge this PR
Retry this production deploy
When iOS prod deploy fails, verify that we post in slack with the given message.

Two potential issues with this testing plan I see:

In step 2, I think it might use the previous version of the GH workflow code and not the code including this PR.
It doesn't test Android (although that might be fine)

QA Steps
None.

Updated to include link to stores

This change did not take effect in the latest iOS prod deploy (which failed), so need to remember to re-check in the next failed mobile deploy.

🚀 Deployed to production by @roryabraham in version: 1.0.92-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅