Building with Borland C++ Builder 6 - 1

I have some issues building tinyxml2 with Borland C++ Builder 6 (Yes I know it's old, but I have no option there :-( ).
The first one was easy to fix with the following patch:
`--- C:/Users/Wilfred/AppData/Local/Temp/TortoiseGit/tin93BA.tmp/tinyxml2-c8dad95-left.cpp	Tue Feb 23 11:21:43 2016
+++ C:/MyFiles/CPP/tinyxml2/tinyxml2.cpp	Tue Feb 16 16:44:28 2016
@@ -24,7 +24,7 @@
#include "tinyxml2.h"
#include 		// yes, this one new style header, is in the Android SDK.
-#if defined(ANDROID_NDK) || defined(QNXNTO)
+#if defined(ANDROID_NDK) || defined(BORLANDC) || defined(QNXNTO)
include <stddef.h>
include <stdarg.h>
#else
`

Could you submit a Pull Request? Thanks!

Done: https://github.com/leethomason/tinyxml2/pull/427

Thanks!


Social media and MSME links to be opened in the new tab.

Is your feature request related to a problem? Please describe.
The social media and the MSME links in the footer section are open in the same tab. It would look good if they open in a new tab.
Describe the solution you'd like
I would like to change the code such that they open in a new tab.
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@AshAman999  I would like to contribute to this issue. Please assign me this issue under Gssoc'23.


breadcrumb overlap problem on chrome

Hi, mini.css looks lovely.
I noticed that the demo for breadcrumbs has a visual bug on Chrome OS X Version 57.0.2987.133 (64-bit) (note the middle breadcrumb "Folder":

the problem is not visible if you hover on the middle breadcrumb.

This is a sizing bug by the looks of it, which means that the breadcrumb does not fit its assigned column's area. I will change the layout a bit to make sure that this is not an issue in the future. Thank you for reporting this!

I have resolved this locally, will push tomorrow morning (~12 hours from now) along with the next release, which will change a couple of things in the docs and flavors. Stay tuned for the update! :wink:


Use tenacity to retry event_fetcher's web3 calls

We retry and log warnings forever at the moment. This most probably
will need some tuning.
For documentation on tenacity please visit
https://tenacity.readthedocs.io/en/latest/
See https://github.com/trustlines-protocol/blockchain/issues/320

Not what I had in mind, but also fine with me.
For the record, here's what I meant:
def retry_local_logger(method):
    def decorated_method(self, *args, **kwargs):
        local_retry = retry(..., before_sleep=before_sleep_log(self.logger, logging.WARN)
        return local_retry(method)(self, *args, **kwargs)
    return decorated_method

I would have probably used that if you posted it before. What's nice about doing the retry stuff explicitly is that the caller may decide to retry or not retry method/function calls. Though we don't need that in the event fetcher.


az capi management delete should delete the cluster

Expected behavior:
Using az capi management delete should delete the entire cluster with some confirmation.

Closing this issue in favor of #133


run dependency on rosidl_generator_cpp

Needs to be avoided.

Openned PR here https://github.com/ros2/rmw_dds_common/pull/10

Appears resolved by #10


glfw3 3.1

Hmm. Those failed checks look like a problem with the tester

Yeah. Failure was unrelated. Is okay now.

Thanks for your contribution to Homebrew, Appreciated!


Delete entries

Need a way to remove none validated time entries.

Created a removal system in the timeEntryModel that will check if an entry is validated or not. If not validated it will remove the entry.


fix: Handle serialization and deserialization of bigint as ByteString

Issue:
PlutusData.deserialize() doesn't handle BigInteger properly when it is encoded as a ByteString. Instead, it decodes BigInteger as BytesPlutusData.
BigInteger can also be represented as bytes.
big_int = int / big_uint / big_nint
big_uint = #6.2(bounded_bytes)
big_nint = #6.3(bounded_bytes)

Fix

Read Tag of the ByteString to identify if it's a positive and negative number

Example (Datum):
d8798b581c217a7bf7a6494a0165ae2cb77aabeadb865d33d5be5f9f57b9b0e8f6581c276ba8bb7fe700d0d21b7da11edeb650729efe0b1595af0e643e31844b4e656f6e50756e6b3033311a3b9aca005563687447785a454339663038514d504b6970773073d87980d87980c2410040c241005820dee0b6f2b41b1a75244ec7b83c77c45d5cda5ad4ff3a4964340bb6089d5256e5

Fyi, @nau
Removed encodeAsByteString()

To fix: #399


Our javalib tests use @Test methods in traits, which don't work in M5+JUnit 4

As of Scala 2.12.0-M5, forwarder methods to trait's default methods are not created anymore if they can be avoided. This is problem for @Test methods in traits, since JUnit 4 does not look for default methods. JUnit 5 will fix this issue, but it is not released yet.
We need to do something about it.

We also need to figure out what to do about that in our JUnit compiler plugin.

This was fixed in #2468.


No longer syncing with Garmin

Since the introduction of ECG on some Garmin watches, they have made two factor authentication over email mandatory so it can no longer be disabled. This seems to be causing issues with syncing.
When I attempt to sync scale data I get an error about missing cookies but I see that the attempt is triggering a TFA code to be sent to my email. I just have no way to input that code into the app and continue syncing the data.

Thanks for the info. The 2FA is only mandatory for some watch owners? I own Fenix 6 and this morning I measured myself and uploaded the data without any problem. But I don't have 2FA enabled.
Can you change the settings?
https://www.garmin.com/en-GB/account/security/mfa/

Yes, I believe, at this point, it is only mandatory for some watch owners but as ECG rolls out to more watches it will become an issue unless Garmin changes their policy.
Unfortunately I can't change the settings. It is permanent 2FA.

I did some research and unfortunately the open source projects I found that use Garmin's unofficial API have problems with 2FA and do not support it. Maybe when Garmin starts forcing more users to use 2FA, someone will find a solution to this problem.

Good News!
I just released new version with 2FA/MFA Support.
Update in Google Play store should be available soon.
https://github.com/lswiderski/mi-scale-exporter/releases/tag/v2.1.0


ISPN-14102 JVM GC Logs never set on the server

https://issues.redhat.com/browse/ISPN-14102

Merged, thanks @ryanemerson


i got error on page.title

thanks your library.
when i try, i got this error.
do you have any idea?
code on lamda

exports.handler = async (event) => {
    const puppeteerLambda = require('puppeteer-lambda');
    const browser = await puppeteerLambda.getBrowser({
    headless: true
    });
    const page = await browser.newPage();
    await page.goto('https://www.yahoo.co.jp');
    let title = await page.title;

    await browser.close();

    // TODO implement
    const response = {
        statusCode: 200,
        body: JSON.stringify(`hello ${title}`),
    };
    return response;
};

response
{
  "statusCode": 200,
  "body": "\"hello function (...args) {\\n        const syncStack = new Error();\\n        return method.call(this, ...args).catch(e => {\\n          const stack = syncStack.stack.substring(syncStack.stack.indexOf('\\\\n') + 1);\\n          const clientStack = stack.substring(stack.indexOf('\\\\n'));\\n          if (!e.stack.includes(clientStack))\\n            e.stack += '\\\\n  -- ASYNC --\\\\n' + stack;\\n          throw e;\\n        });\\n      }\""
}

log
START RequestId: 621187f0-e6f0-4508-b3dd-75028fd1a93d Version: $LATEST
2019-03-02T00:32:51.136Z	621187f0-e6f0-4508-b3dd-75028fd1a93d	Launch chrome: HeadlessChrome/69.0.3497.81
2019-03-02T00:32:52.738Z	621187f0-e6f0-4508-b3dd-75028fd1a93d	******************************************************************************************************************************
2019-03-02T00:32:52.739Z	621187f0-e6f0-4508-b3dd-75028fd1a93d	Suggest not to close browser in Lambda ENV, if close it , the Browser object is considered disposed and cannot be used anymore.
2019-03-02T00:32:52.739Z	621187f0-e6f0-4508-b3dd-75028fd1a93d	******************************************************************************************************************************
END RequestId: 621187f0-e6f0-4508-b3dd-75028fd1a93d
REPORT RequestId: 621187f0-e6f0-4508-b3dd-75028fd1a93d	Duration: 7945.49 ms	Billed Duration: 8000 ms 	Memory Size: 768 MB	Max Memory Used: 433 MB

i set env
CUSTOM_CHROME true

@muners  seems due to your response body issue , have u tried console.log the response and see whether it's correctly ?


installation failure on ubuntu 16.04.1 LTS (Desktop) loaded in Hyper-V VM

unable to connect to upstart: failed to connect to socket /com/ubuntu/upstart: connection refused.
I followed instructions here:
https://zulip.readthedocs.io/en/latest/prod-install.html#step-3-configure-zulip
I setup openssl certificate.
How do I troubleshoot?
I tried a fix according to this suggestion, but the same error:
http://askubuntu.com/questions/614970/vivid-failed-to-connect-to-upstart-connection-refused

Hi @denfromufa!  I think you need to uninstall the upstart package; it was replaced by systemd in Ubuntu 16.04, but having it installed confuses some Ubuntu packages into trying to connect to it.
Then you should be able to just rerun the install script.

Hi @timabbott ! this worked, but maybe docs need to be updated to address this?

Yeah, agreed; I actually think we can probably do better by adding a check in the install script with a nice error message.  Can you post a bit more of the traceback to show where in the installer script the error happened?  /var/log/zulip/install.log should have it.

this is after 2nd or 3rd attempt

OK, cool, so it's in the puppet stage; that's enough info to know we can fix this by just putting code in the install script before we start puppet.  Thanks for the debugging info @denfromufa!

(I think we should do this via adding a script scripts/lib/check-upstart and call it both from the install script and the upgrade script).

This has now been fixed in master; thanks @denfromufa for the bug report!


Fix --wait in manifest apply not being used.

Fix: https://github.com/istio/istio/issues/19602

@elfinhe: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mesh_operator
2ba38c58488aa7d1cedec352fd37d5dec26d00f5
link
/test mesh_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elfinhe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mesh_operator
2ba38c58488aa7d1cedec352fd37d5dec26d00f5
link
/test mesh_operator

mandiff_operator
2ba38c58488aa7d1cedec352fd37d5dec26d00f5
link
/test mandiff_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@elfinhe: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

mesh_operator
2ba38c58488aa7d1cedec352fd37d5dec26d00f5
link
/test mesh_operator

mandiff_operator
2ba38c58488aa7d1cedec352fd37d5dec26d00f5
link
/test mandiff_operator

lint_operator
2ba38c58488aa7d1cedec352fd37d5dec26d00f5
link
/test lint_operator

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

In response to a cherrypick label: #725 failed to apply on top of branch "release-1.4":
error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	cmd/mesh/manifest-apply.go
M	cmd/mesh/manifest-common.go
M	cmd/mesh/profile-diff.go
M	cmd/mesh/upgrade.go
Falling back to patching base and 3-way merge...
Auto-merging cmd/mesh/upgrade.go
Auto-merging cmd/mesh/profile-diff.go
Auto-merging cmd/mesh/manifest-common.go
CONFLICT (content): Merge conflict in cmd/mesh/manifest-common.go
Auto-merging cmd/mesh/manifest-apply.go
CONFLICT (content): Merge conflict in cmd/mesh/manifest-apply.go
Patch failed at 0001 Fix args.wait not being used.


iOS - Playback stops when returning from a phone call

Issue
Just discovered today that if the video is playing, and you receive a phone call, when you return to the app (either by declining the call, or ending it), the video playback is stopped, and does not start unless the app is exited and launched again.
Research
I tried other weird cases to see if playback stops when coming back from sleep, notification center or control center, and everything (except receiving a phone call) works great.
Environment
I discovered the issue under iOS 10.0.1

This is I think a failing in iOS 10.  If there is another workaround I'm yet to find it 😕

As it is not a huge deal for me right now, I'm not likely to spend time on a fix for this. I mostly wanted to raise the issue so we can gather information and see if we can identify the problem properly upon fixing it.

I'm also been experiencing this issue for ios. The strange thing is that this isn't happening on Android as it resumes playback when declining or hanging up on a call.
Is this something that's still being looked at being fixed soon?

Also experiencing the same issue. I tried looking for a good way to detect phone calls, but haven't found any good solutions for React Native.
Does anyone have any pointers for detecting calls in RN?

+1

@axelphunter How did you restart the video? There doesn't seem to be a resume method.

Create a ref on the video player and an AppState listener. Within the listener do something similar to the following:
handleAppStateChange(nextAppState) {
        if (this.state.appState.match(/inactive|background/) && nextAppState === 'active') {
            if (this.player) {
                this.player.setNativeProps({
                    rate: 1
                });
            }
        }
}

Easy!

Thanks @axelphunter!
I ended up pretty much what you have above except with setNativeProps({paused: false});


Look for a default config file in $HOME/.svglintrc.js

This application was exactly what I was look for. Thank you!
I'd like to have a global default config file that I can keep with my environment files: $HOME/.svglintrc.js. This pull looks in your home directory for a .svglintrc.js file if there are no other candidates (i.e. in the working directory or any of its parents). To help me I added the name of the configuration file used to the debug output, and incorporated it in the configuration file tests.

Thank you for the Pull Request @kcaran. I think the idea of adding this make sense. Unfortunately I'll be quite busy for the rest of this month so it might take a while before I can review+merge this.

Thanks for the review. Now I'm on vacation for the next couple of weeks! But I'll make the updates when I get back.


Vulnerability type Click Jacking

Hi team,
This time i founded this vulnerability in your website:
https://nuxtjs.org/

Click jacking (User Interface redress attack, UI redress attack, UI redressing) is a malicious technique of tricking a Web user into clicking on something different from what the user perceives they are clicking on, thus potentially revealing confidential information or taking control of their computer while clicking on seemingly innocuous web pages.
The server didn't return an X-Frame-Options header which means that this website could be at risk of a click jacking attack. The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a  or . Sites can use this to avoid click jacking attacks, by ensuring that their content is not embedded into other sites.
This vulnerability affects Web Server.
Here are the steps to reproduce the vulnerability:
1.open notepad and paste the following code.

i Frame

This is clickjacking vulnerable

2.save it as .html eg s.html
3.and just simply open that...
OR
Copy the link below and paste on your updated browser (Chrome,Firefox).
https://clickjacker.io/test?url=https://nuxtjs.org/
As far as i know this data is enough to prove that your site is vulnerable to Click jacking
according to OWASP its more than enough.
https://www.owasp.org/index.php/Testing_for_Clickjacking_(OWASP-CS-004)
SOLUTION:
https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet
Check this out and here is the solution for that.
I Hope that you will fix this issue as soon as possible. Looking forward to hear from you. Thank you
Sincerely,
Hassan Raza

Yes I still can reproduce this issue after you update you version.
Here are the steps to reproduce the vulnerability:
1.open notepad and paste the following code.
i Frame
This is clickjacking vulnerable

2.save it as .html eg s.html
3.and just simply open that...
OR
Copy the link below and paste on your updated browser (Chrome,Firefox).
https://clickjacker.io/test?url=https://nuxtjs.org/

This still applies to nuxt.com. Mitigating this potential issue would mean that the docs can't be used inside an iframe anymore.


implement node labels

Implement node labels. Bascially porting the same PR in official CLI:
https://github.com/Azure/azure-cli/pull/12418
This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/xizhamsft/azure-cli-extensions.git@xizha-nodelabels#subdirectory=src/$EXT&egg=$EXT"

aks

HI @xizhamsft could you pls sync with master branch then this PR ready to merge.


Type 'List' does not conform to protocol 'RangeReplaceableCollectionType'

Hi there,
since yesterday a new problem with swift-2.0 branch:
.../Pods/RealmSwift/RealmSwift/List.swift:308:1: Type 'List' does not conform to protocol 'RangeReplaceableCollectionType'
won't compile

Swift 2 build is now required Xcode 7 beta4 from https://github.com/realm/realm-cocoa/commit/0cd7a8ef9637b608ce14cabb673ea0230a42318b
Please upgrade your Xcode to beta4.

thanks, working on beta4.


Support SpiderMonkey 128

Overview

Testing recommendations

Related Issues or Pull Requests

Checklist

[x] Code is written and works correctly
[ ] Changes are covered by tests
[ ] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[x] Documentation changes were made in the src/docs folder
[ ] Documentation changes were backported (separated PR) to affected branches

Closing in favour of https://github.com/apache/couchdb/pull/5314


Wildcard subdomains / hostnames

Is your feature request related to a problem? Please describe.
I have recently found myself working on a project that does sub-domain routing based on generated data
(e.g. {UUID}.demo.myapp.com).
While developing I found it a bit cumbersome to add new hostnames to the configuration file and restart ddev
everytime I added a new demo page. That in turn made me wish for wildcard subdomains / hostnames
Describe the solution you'd like
Ideally, it would be possible to use wildcards in additional_hostnames like this:
additional_hostnames:
    - '*.demo.myapp'

Additional context
While trying to find out whether or not this already existed I stumbled over the implementation detail, that
the ddev.site domain is actually registered and just points to <IP_ADDRESS> to make setup easier. If a user is
offline however, entries in /etc/hosts are being generated.
With the online DNS setup wildcards should be fairly easy to support since you would just need to tell
ddev-router (which runs haproxy I think?) about the wildcard.
I suspect that the offline /etc/hosts setup is why wildcard hostnames could be an issue since there
are no wildcards in /etc/hosts.

Well, I didn't mean to but I fiddled with it a bit and #2391 seems to make it work. It can never work if /etc/hosts is in play, only when ddev.site or a similar TLD is used.


Selection the Harder difficulty sometimes crashes the game

When doing the fake rate sometimes the second you click on "Harder" face the game crashes

On where? DIfficulty selection?

Also, send the crashlog

Yes on the difficulty selection. Geode didn't generate a new crashlog and it didn't even say Crashed or anything when i reopened the game. It was some windows error thingy or smth but your mod was referenced in it.

I can't reproduce this issue. What level did you try to rate as Harder?

"dorabaebasic7" was what failed. I had previously rated it Hard 5* in gd 2.204.

Ok it crashed again but with a log this time
2024-06-27_20-28-17.log

boom, now it deleted all my fake rates... :(

I'm sorry to hear that.
I'll get to fixing.

This was caused by me not properly checking if the More Difficulties mod was enabled. Bug has existed since v1.2.0, probably.
Fixed in v1.2.3


fix: remove logs to print config and correct integration test names

What this PR does / why we need it:

Remove the logging of generated plugin config to avoid sensitive information in debug logs
Update names of integration tests on validating secrets

Which issue this PR fixes:

following fix of #5203.
Special notes for your reviewer:

PR Readiness Checklist:
Complete these before marking the PR as ready to review:
~- [ ] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR~ I think No need to update CHANGELOG

Seems that the added test is flaky: https://github.com/Kong/kubernetes-ingress-controller/actions/runs/7178831047/job/19547840672?pr=5320. @czeslavo  Do you think it is a good way to fix in this PR, or create another issue and fix it later?

Seems that the added test is flaky: https://github.com/Kong/kubernetes-ingress-controller/actions/runs/7178831047/job/19547840672?pr=5320. @czeslavo Do you think it is a good way to fix in this PR, or create another issue and fix it later?

I cannot see this PR adding any new test so I think it's fine to fix it separately. 🤔


[Dropdown] Dropdown is not opening if clicked on the label circle.

http://semantic-ui.com/modules/dropdown.html#search-in-menu

Select any value (first you might need to enter some text to be able to select, it's another bug). The dropdown will close and show the selected value.
Now click exactly on the circle next to the selected tag. Nothing will happen despite the highlight.

Happens in Chrome 56 and Firefox 51.

See #5113.


Fix inaccurate item name in README

Why:
This PR intends to fix an inaccurate item name.
What's being changed:
Step4 in README.
Description of the item name on the screen to be checked in step 4 .
Check off the following:

[x] For workflow changes, I have verified the Actions workflows function as expected.
[x] For content changes, I have reviewed the style guide.

dd

dddd

fff

I'll go ahead and merge this as is, I've internally requested an instructional designer to review this course given the comments on it.


Tests failing with pip 24.0

$ python --version
Python 3.11.9
$ pip --version
pip 24.0 from /home/sudhackar/.pyenv/versions/3.11.9/envs/venv-soss/lib/python3.11/site-packages/pip (python 3.11)
$ tox p -e py311-linux
.pkg: recreate env because python changed version_info=[3, 12, 3, 'final', 0]->[3, 11, 9, 'final', 0] | executable='/usr/bin/python3.12'->'/home/sudhackar/.pyenv/versions/3.11.9/bin/python3.11'
...
======================================================================
FAIL: test_pip_install (__main__.SetuptoolsWheel.test_pip_install)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/dev/shm/python-versioneer-upstream/test/git/test_invocations.py", line 465, in test_pip_install
    self.run_in_venv(venv, venv,
  File "/dev/shm/python-versioneer-upstream/test/git/test_invocations.py", line 85, in run_in_venv
    return self.command(*bin_args, *args, workdir=workdir)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/dev/shm/python-versioneer-upstream/test/git/common.py", line 16, in command
    self.fail("problem running command %s" % cmd)
AssertionError: problem running command /tmp/tmp5aim3n9h/venvs/setuptools-wheel-pip-install/bin/python

----------------------------------------------------------------------
Ran 28 tests in 250.710s

FAILED (failures=15)
  py311-linux: FAIL code 1 (316.33=setup[4.39]+cmd[0.15,0.07,0.33,0.05,60.55,250.80] seconds)
  evaluation failed :( (316.36 seconds)

pinning pip version to something like 23.2.1 will make the tests pass
$ GIT_PAGER= gd
diff --git a/test/git/test_invocations.py b/test/git/test_invocations.py
index 1f61ffb..e7e6b5a 100644
--- a/test/git/test_invocations.py
+++ b/test/git/test_invocations.py
@@ -58,6 +58,8 @@ class _Invocations(common.Common):
             self.run_in_venv(venv_dir, venv_dir,
                              'pip', 'install', '-U',
                              'pip', 'wheel', 'packaging')
+            self.run_in_venv(venv_dir, venv_dir, 'pip', 'install',
+                             'pip==23.2.1', '--upgrade')
         if sys.version_info.major == 3 and sys.version_info.minor >= 12:
             # Py 3.12 no longer default-installs setuptools in environments
             # See PEP-632

will pass
$ tox p -e py311-linux
  py311-linux: OK (492.07=setup[2.03]+cmd[0.14,0.06,0.13,0.04,60.69,428.31,0.13,0.06,0.05,0.07,0.24,0.11] seconds)
  congratulations :) (492.10 seconds)

Based on https://github.com/pypa/pip/issues/12933#issuecomment-2306623165 I'll raise a PR to move to tar.gz as standard

Thank you for the report and fix, I expect to review within the week (might be today, but not sure yet)
Just wanted to let you know that I saw this!


Table API query results no Timestamp property

Package Name: azure-data-tables
Package Version: 12.4.0
Operating System: MacOS Monterey 12.5
Python Version: 3.9.13

Describe the bug
When I query table entities, I don't get Timestamp in the outputs. When I try to access Timestamp directly from the entity, I got AttributeError: 'TableEntity' object has no attribute 'Timestamp'.
To Reproduce
filter = f"SpaceId eq '{space_id}' and DataType eq '{data_type}'"
entities = client.query_entities(query_filter=filter)
[entity.Timestamp for entity in entities]
Expected behavior
Timestamp property should be part of the query results if select properties is not specified.

Thanks @edgarhuichen - I think you should be able to find this information in TableEntity.metadata
For example, something like this:
filter = f"SpaceId eq '{space_id}' and DataType eq '{data_type}'"
entities = client.query_entities(query_filter=filter)

[entity.metadata['timestamp'] for entity in entities]

@annatisch Thanks for the quick response. Yes, after checking another similar issue report and dig in to the source code, I found out Timestamp is indeed accessed via metadata. However, I'd prefer to have it directly accessible as a entity property. Now I have to add extra code to extract timestamp.

Hi @edgarhuichen - Thanks for your feedback! We'll discuss adding this feature and get back to you as soon as possible.

One more remark: because of the extra code, I can't use list comprehension to get all the entities out. It affects performance of my code.

Second this feature, timestamp in metadata needs additional wrapper to merge with contents in entity.

Thanks for the feedback @Tjianke!
We are actively investigating approaches we could take to address this in a non-breaking way :)

@edgarhuichen , thanks for your waiting!
We are working on re-factoring the de/serialization of TableEntity type in this semester, we'll take your feedback into consideration. Stay tuned!

any news on this topic ?

Thanks for your interest @crapitouille - we are still working on this, with the new refactoring currently in development and early review. We will make a comment here once it has been released in beta.


Middleware: Add RPCs needed for the base setup

This adds the RPCs to the middleware needed to setup the Base in the App. In combination with https://github.com/digitalbitbox/bitbox-wallet-app/pull/506.

Added doc strings for runBBBCmdScript and runBBBConfigScript.


Run bugfix release to pull in Bulk Indexer Memory Leak

I've been using the Bulk Indexer as part of a production application and noticed frequent OOMs on high throughput scenarios. This lead me here, where I saw the fix was landed to main on this PR. But there hasn't been a release since this has landed and I now have to pull off main to prevent OOMs from happening.
Is there any chance we can get a minor release to pull this in?

Hi @wmorgan6796
This fix is due for the next 8.0 release, there is already an v8.0.0-alpha pre-release that you can use right now for testing!

@Anaethelion our team is stuck on ES 7. Is ES 8 version compatible ES 7?

@wmorgan6796 While there is no guarantee for forward compatibility you already are using the code for the 8 version if you are currently running main, in your use case you should be fine.
Backporting this change to the 7 branch would unfortunately break the API which is currently not in our plan.


Support migrating NFS blob to Azure store account.

Can anyone here can help to review the PR, and advise if it can be accepted? @calebwashburn ? @malston ?


Dynamically adding 'import' to Angular 4 TypeScript source code causes very very slow build (10x slower)

Do you want to request a feature or report a bug?
bug

What is the current behavior?
Extremely slow build when dynamically adding 'import' (e.g. import { Component } from '@angular/core';)
Project size
TypeScript files: 255
Html files: 26
Scss files: 44
Adding 'import' dynamically

576661ms building modules
75ms sealing
0ms optimizing
0ms basic module optimization
37ms module optimization
2ms advanced module optimization
13ms basic chunk optimization
0ms chunk optimization
1ms advanced chunk optimization
0ms module and chunk tree optimization
25ms module reviving
17ms module order optimization
23ms module id optimization
22ms chunk reviving
1ms chunk order optimization
92ms chunk id optimization
64ms hashing
5ms module assets processing
149ms chunk assets processing
208ms additional chunk assets processing
1ms recording
6ms additional asset processing
292ms chunk asset optimization
94% asset optimization
[at-loader] Checking started in a separate process...
[at-loader] Checking finished with 151 errors
1191ms asset optimization
918ms emitting
Hash: 6b931d385d4dbac813af
Version: webpack 2.3.2
Time: 580267ms

Without adding 'import' dynamically

38328ms building modules
113ms sealing
0ms optimizing
0ms basic module optimization
70ms module optimization
10ms advanced module optimization
106ms basic chunk optimization
1ms chunk optimization
3ms advanced chunk optimization
4ms module and chunk tree optimization
123ms module reviving
59ms module order optimization
7ms module id optimization
48ms chunk reviving
1ms chunk order optimization
47ms chunk id optimization
61ms hashing
8ms module assets processing
283ms chunk assets processing
237ms additional chunk assets processing
1ms recording
0ms additional asset processing
224ms chunk asset optimization
94% asset optimization
[at-loader] Checking started in a separate process...
[at-loader] Checking finished with 93 errors
1296ms asset optimization
904ms emitting
Hash: 5a81fdcff97e66a09525
Version: webpack 2.3.2
Time: 42163ms

If the current behavior is a bug, please provide the steps to reproduce.
Using custom loader - ts-loader
"use strict";
module.exports = function (source, sourceMap) {
    // Not cacheable during unit tests;
    this.cacheable && this.cacheable();

    source = `import { Component } from '@angular/core';\nconsole.log(Component);\n` + source;

    // Support for tests
    if (this.callback) {
        this.callback(null, source, sourceMap)
    } else {
        return source;
    }
}

Config files
webpack.common.zip

What is the expected behavior?
No much differences on build speed
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Webpack: 2.3.2
OS: Windows 10
Node: 6.9.4

can you add the files as a gist or link to an example repo instead of a zip file?:)

I uploaded the sample code to https://github.com/feng-xiao/webpack-build-issues. You just need to change line 7 by commenting or uncommenting it to see the build time differences.
With this sample application from Angular Class template it's about 5 times slower, in my own angular 4 template, it's 10 times slower.
Build command
npm run build:dev

Without commenting

38072ms building modules
22ms sealing
0ms optimizing
0ms basic module optimization
15ms module optimization
11ms advanced module optimization
18ms basic chunk optimization
1ms chunk optimization
2ms advanced chunk optimization
1ms module and chunk tree optimization
5ms module reviving
1ms module order optimization
1ms module id optimization
6ms chunk reviving
0ms chunk order optimization
5ms chunk id optimization
24ms hashing
0ms module assets processing
33ms chunk assets processing
37ms additional chunk assets processing
0ms recording
1ms additional asset processing
76ms chunk asset optimization
94% asset optimization
[at-loader] Checking started in a separate process...
[at-loader] Ok, 0.647 sec.
877ms asset optimization
498ms emitting
Hash: b7ef9ceeaee86e8f686f
Version: webpack 2.3.1
Time: 47407ms

Commenting line 7

9624ms building modules
16ms sealing
1ms optimizing
1ms basic module optimization
13ms module optimization
5ms advanced module optimization
4ms basic chunk optimization
0ms chunk optimization
1ms advanced chunk optimization
0ms module and chunk tree optimization
7ms module reviving
1ms module order optimization
2ms module id optimization
5ms chunk reviving
0ms chunk order optimization
8ms chunk id optimization
12ms hashing
0ms module assets processing
30ms chunk assets processing
77ms additional chunk assets processing
22ms recording
16ms additional asset processing
73ms chunk asset optimization
94% asset optimization
[at-loader] Checking started in a separate process...
[at-loader] Ok, 0.687 sec.
882ms asset optimization
589ms emitting
Hash: e8e2cff100adc14db6c9
Version: webpack 2.3.1
Time: 11914ms

The repo is too complex. Could you strip it down to a minimal repo?

Hi Sokra,
I already removed files as much as I can

any updates on this issues? it's very annoying. Basically, I have a custom loader to do typescript code generation, this problem gave me headache now. I need to think how to get around it... It would be much appreciated if someone can fix it ASAP


ImportError

Hello guys , i've been trying to solve this error for hours , but i keep gettin' it , can someone come up with a solution?
The error : Traceback (most recent call last):
File "C:\Users\Bogdan\Desktop\TapoP100-main\PyP100\PyP100.py", line 10, in
from . import tp_link_cipher
ImportError: attempted relative import with no known parent package

It's most likely you are running the file from the incorrect directory which is PyP100\PyP100.py. It's saying that it does not know any parent package which is correct because the PyP100.py file is the one you are most likely running as "main.py". To fix this you should write either main.py in folder above or try to use this like a library which is simply (in your outside script) call from PyP100 import PyP100 which is what you probably want to do.


openExternal allows a malicious script to execute arbitrary local files

Since addEventListener with 7new-window' can receive file: scheme, this code will allows a remote user to execute arbitrary local files via injected window.open().
https://github.com/atom/electron/blob/master/docs/api/web-view-tag.md#event-new-window

webview.addEventListener('new-window', function(e) {
require('electron').shell.openExternal(e.url);
});

This script in wevbiew with event listener described above could execute calc.exe:
window.open('c:/windows/system32/calc.exe')
I tested it with electron v0.37.2 on windows.
I think this sample code should validate e.url before execution with openExternal or file: scheme should be prohibited on openExternal.

Good catch - the correct answer here is that environments with disabled node-integration shouldn't be able to open new windows that do have Node integration, meaning that openExternal should not be available in a hostile/non-friendly environment, together with all other Node APIs.
I know that @kevinsawicki did some work around that, so if we have new windows locked down, we could close this issue.

Thank you for a new document. :)
However, I confirmed that I could open file scheme with chrome by using this url:
http://www.example.com/#" "file://c:/
It seems that lack of escaping of openExternal cause this strange behavior:
https://github.com/atom/electron/blob/master/atom/common/platform_util_win.cc#L308
This escaping flaw should be addressed to path valid url.


fix unhandled undefined or null for feePerByte

📝 Description
t.feePerByte can be undefined, triggering a Cannot read properties of null (reading 'toNumber') error and potentially crashing the app.
This PR handles this case properly.
Introduced by this line -> https://github.com/LedgerHQ/ledger-live/pull/1705/files#diff-9481356d1850289b630777fce1fef96c6ace0798ba31894f9357b85cf043c7e3R120
cf. this CI run failing due to this issue for example
❓ Context

Impacted projects: LLC
Linked resource(s): https://github.com/LedgerHQ/ledger-live/pull/1705

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Re-targeting the PR to develop to consider it for a future release.

@chabroA Can you please link a CI run showing the issue this is solving?

Looks all good, would be perfect to have CI runs to compare to validate the fix.

Sure, here is an example run failing -> https://github.com/LedgerHQ/ledger-live/actions/runs/3533577647/jobs/5929402610#step:8:6639


fr: screen position

would be nice to have the lower left corner as a parameter, in order to move it around for speaker panel layouts e.g.

added some params for left and bottom offset as well as width, do let me know if that works for you

works now! thanks!


Signup modal

Added a test modal as per the UI given.
Brought most of the components necessary from Account-Manager to the website for modals and forms.
Installed necessary packages ( formik, react-select, @types/react-select ).
Test modal can be accessed from route "/account".

Do we want all of the Formik components copied here, even though most of them are not being used right now? @thesanjeevsharma @lapstjup

@charnysh-dev  Yeah can be done ofc, I kept it that way to maintain the consistency between both the projects, account-manager and this. In account manager, we're already using stuff from both components/FormElements and components/FormComponents.

@charnysh-dev Yeah can be done ofc, I kept it that way to maintain the consistency between both the projects, account-manager and this. In account manager, we're already using stuff from both components/FormElements and components/FormComponents.

Ok, then we could resolve some conflicts


Add a TextInputAction property to DropdownMenu

I usually use DropdownMenu as my go-to widget when I need a TextField with a dropdown where I can search for items. I use it in a form where there is at least one other form field (usually TextFormField) coming after it. It would be such a nice feature for DropdownMenu to have a textInputAction property so we can use something like TextInputAction.next to go to the next form field. Right now, it can only be TextInputAction.done (as a default value for the internal TextField it uses) which is not really helpful.

By using a FocusNode and onChanged on DropDown, you can programmatically control the focus to move to the next field when the user selects a value from the dropdown. You achieve the TextInputAction.next functionality even though the DropdownMenu doesn't provide this property out of the box.

Create a FocusNode for both the DropdownMenu and the next form field (like a TextFormField).
Listen to the onChanged  event on the DropdownMenu's internal TextField to move the focus to the next field.

Here's the example implementation of the given approach :
`import 'package:flutter/material.dart';
class CustomDropdownForm extends StatefulWidget {
@override
_CustomDropdownFormState createState() => _CustomDropdownFormState();
}
class _CustomDropdownFormState extends State {
final _dropdownFocusNode = FocusNode();
final _textFieldFocusNode = FocusNode();
String? _selectedItem;
@override
void dispose() {
_dropdownFocusNode.dispose();
_textFieldFocusNode.dispose();
super.dispose();
}
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(title: Text('Custom Dropdown Form')),
body: Padding(
padding: const EdgeInsets.all(16.0),
child: Form(
child: Column(
children: [
DropdownButtonFormField(
focusNode: _dropdownFocusNode,
value: _selectedItem,
items: ['Option 1', 'Option 2', 'Option 3']
.map((option) => DropdownMenuItem(
value: option,
child: Text(option),
))
.toList(),
onChanged: (value) {
setState(() {
_selectedItem = value;
});
FocusScope.of(context).requestFocus(_textFieldFocusNode);
},
decoration: const InputDecoration(
labelText: 'Select an Option',
),
onTap: () {
FocusScope.of(context).requestFocus(_dropdownFocusNode);
},
),
const SizedBox(height: 16),
TextFormField(
focusNode: _textFieldFocusNode,
decoration: InputDecoration(labelText: 'Next Field'),
),
],
),
),
),
);
}
}
class DropdownMenu extends StatelessWidget {
final FocusNode? focusNode;
final T? initialSelection;
final List<DropdownMenuEntry> dropdownMenuEntries;
final ValueChanged<T?>? onSelected;
final TextFieldConfiguration textFieldConfiguration;
const DropdownMenu({
Key? key,
this.focusNode,
this.initialSelection,
required this.dropdownMenuEntries,
this.onSelected,
required this.textFieldConfiguration,
}) : super(key: key);
@override
Widget build(BuildContext context) {
return DropdownButtonFormField(
focusNode: focusNode,
value: initialSelection,
items: dropdownMenuEntries
.map((entry) =>
DropdownMenuItem(value: entry.value, child: entry.label))
.toList(),
onChanged: (value) => onSelected?.call(value),
decoration: InputDecoration(
labelText: 'Dropdown',
),
);
}
}
class DropdownMenuEntry {
final T value;
final Widget label;
const DropdownMenuEntry({
required this.value,
required this.label,
});
}
class TextFieldConfiguration {
final ValueChanged? onSubmitted;
final TextInputAction textInputAction;
TextFieldConfiguration({
this.onSubmitted,
this.textInputAction = TextInputAction.done,
});
}
`
Now, when an item is selected in the dropdown, the focus will automatically move to the next form field. This workaround simulates the behavior of TextInputAction.next for DropdownButtonFormField.
I hope it'll help you.

Thanks @princetomar27 for the answer. This can be considered as a workaround just for TextInputAction.next, but my proposal is to add the property so that other types of TextInputAction can also be supported!


Updates for docker-compose sources.

Coverage remained the same at 52.154% when pulling 914255d6c2ee6df7ef4c1db5f8372d902e5955fd on wknet123:harbor-clarity-integration into abc2bcbf2a8d4263c9e1840575a584de2eb8b000 on vmware:harbor-clarity-integration.


Updated C1 packages to latest, enabled ImplicitUsings, updated description, added license

Summary
Changes to FlexGridShowcaseDemo sample:

Updated C1 packages to latest;
Enabled ImplicitUsings;
Updated description;
Added license.

@dotnet-policy-service agree [company="GrapeCity"]

Hi, @adegeo, @RussKie,
I'm sorry to interrupt whatever you're doing, but could someone take a look?
Thank you!

Guys, thank you for taking a look.
Could you tell, who is in charge to merge everything to target branch?

Guys, thank you for taking a look. Could you tell, who is in charge to merge everything to target branch?

@denjmpr, there was an open question internally on the license inclusion. I will get it resolved today/tomorrow and merge it.

@dreddy-work, thank you so much!
One last question - how long to wait when changes will be available on corresponding code samples page - https://learn.microsoft.com/en-us/samples/dotnet/samples/winforms-flexgridshowcase-cs/ ?
Will it appear automatically since some period of time?

@dreddy-work Devendar Reddy A FTE, thank you so much! One last question - how long to wait when changes will be available on corresponding code samples page - learn.microsoft.com/en-us/samples/dotnet/samples/winforms-flexgridshowcase-cs ? Will it appear automatically since some period of time?

This is more a question for @adegeo.
@gewarren would you know anything about this flow?

This is more a question for @adegeo. @gewarren would you know anything about this flow?

@mtrilbybassett or @Taojunshen When can we expect https://github.com/MicrosoftDocs/samples/pull/2841 to get merged?

@gewarren merges to live are to happen Tuesday and Friday. It looks like there may have been an issue with this past Friday -- expect the merge to be completed today.
cc @Taojunshen

Thank you all so much!


[FR] Support for service broker dashboards

Is your feature request related to a problem? Please describe.
As a cloud-service-broker user (e.g a CF developer provisionning AWS RDS through CSB)

in order to finely manage the provisionned resource

AWS RDS backups/snapshots
access to AWS RDS metrics

I need CSB to enable returning a service dashboard

Currently, CSB seems to always return an empty dashboard url
https://github.com/pivotal/cloud-service-broker/blob/99dab14683fc429dbcb04bb4c025cfa6fe378480/brokerapi/brokers/service_broker.go#L168
https://github.com/pivotal/cloud-service-broker/blob/99dab14683fc429dbcb04bb4c025cfa6fe378480/brokerapi/brokers/service_broker.go#L584
Describe the solution you'd like
A way to specify the dashboard in the provision action by selecting an input.
Describe alternatives you've considered

Additional Context
Regarding ways cloudfoundry end user would authentify to the AWS RDS dashboard, I would expect that support for AWS IAM external users would enable a brokerpak to provision web identity federation and restricted IAM role so that a CF signed in user would be granted just enough permission to access the AWS RDS console to list backups/snapshots and restore them in a self service maneer.
Priority

Priority Context
Platform

Applicable Services

Does this apply to all services? Just one? Let us know

Most data services need access to backup/restore/metrics/logs.
The OSB API group has not yet prioritized associated work, see https://github.com/openservicebrokerapi/servicebroker/issues/486 https://github.com/openservicebrokerapi/servicebroker/issues/485 https://github.com/openservicebrokerapi/servicebroker/issues/107, therefore service providers have no other choices than direct users to a web ui through the dashboard url.

Keep the Issues coming!

@gberche-orange This is a great idea, but probably won't work with the current OSBAPI spec.
The problem is that the URL must be generated during the provision call. Since the provision is async, the values that would be used to generate the URL aren't known and there is no current support in OSBAPI to update the URL.
From https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md
The URL of a web-based management user interface for the Service Instance; we refer to this as a service dashboard. The URL MUST contain enough information for the dashboard to identify the resource being accessed (9189kdfsk0vfnku in the example below). Note: a Service Broker that wishes to return dashboard_url for a Service Instance MUST return it with the initial response to the provision request, even if the service is provisioned asynchronously.```

thanks for looking into this suggestion @erniebilling
What about returning a static dashboard url served by CSB (e.g. including the service instance guid as param). When this dashboard url is queried by developers, it then redirects to the (asynchronously computed) value of a terraform output, possibly an url to a provisionned cloud resource (such as an RDS instance guid) ?

We're adding the ability for the bokerpak terraform to set a custom message that will be displayed as part of the output from cf service <service instance>  This message is updated once the async provision operation is complete. Here's some sample output I've been playing with:
name:            test-mssql
service:         csb-azure-mssql
tags:
plan:            small
description:     Azure SQL Database is a fully managed service for the Azure Platform
documentation:   https://docs.microsoft.com/en-us/azure/sql-database/
dashboard:

Showing status of last operation from service test-mssql...

status:    create succeeded
message:   created db csb-db (id:
           /subscriptions/899bf076-632b-4143-b015-43da8179e53f/resourceGroups/broker-cf-test/providers/Microsoft.Sql/servers/csb-azsql-9a19e6ea-5350-4377-9cd8-d7686bbb93a2/databases/csb-db) on
           server csb-azsql-9a19e6ea-5350-4377-9cd8-d7686bbb93a2 (id:
           /subscriptions/899bf076-632b-4143-b015-43da8179e53f/resourceGroups/broker-cf-test/providers/Microsoft.Sql/servers/csb-azsql-9a19e6ea-5350-4377-9cd8-d7686bbb93a2) URL:
<EMAIL_ADDRESS>started:   2020-09-17T19:54:32Z
updated:   2020-09-17T19:56:40Z

There are no bound apps for this service.

Thanks, this is a nice 1st step! Any reason not to try to return the url into the dashboard field ?
As you probably know, using the status message to provide dashboard urls has the following limitations:

discoverability and formatting. Cf UIs such as PWS or stratos don't display status message in most views, or don't detect Urls in status messages, making is harder for users to click on the url. Dashboards are properly formatted as hrefs with proper UX (manage href in PWS)

status message might be ephemeral (see for instance recent related CAPI regression at https://github.com/cloudfoundry/cloud_controller_ng/issues/1847) and disappear upon service instance plan update, or params update if the broker does not reissue it.

It may not always be possible to generate the URL before the terraform has completed. But we can investigate adding support for those cases when it can be generated.

As mentionned in https://github.com/pivotal/cloud-service-broker/issues/81#issuecomment-693695021, one possibility is to return a static dashboard url served by CSB e.g. https://csb-deployment.domain/dashboard?service-instance-guid=guid.  When the user requests this endpoint, then CSB looks up the URL stored in database (once terraform apply completes) and returns one if available or an error page such  as "dashboard is not yet available while the instance is being provisionned".
To avoid returning dashboard urls that always redirect to an error page, the dashboard feature would be an opt-in actionned by brokerpak authors.

hey @gberche-orange, we have unfortunately de-prioritized this feature as it may be difficult to implement for customers leveraging multiple accounts (which we have nascent plans to begin supporting).
If I don't hear back from you, I'll close this issue! Sorry to disappoint.

Thanks @omerbensaadon for the follow up. I don't quite understand the 'multiple account' use-case you mentioned that would not be supported by the dashboard feature. Can you please elaborate that use-case more precisely?

@gberche-orange I will have ENG follow up in a bit here...

You are right @gberche-orange, the multiple account use case probably doesn't impact this feature, but unfortunately, the priority for this feature is pretty low at this time. Happy to take a PR from some intrepid contributor that feels this feature is in their wheel house.

Implementation of this feature for cloudfoundry clients is now made much easier with https://github.com/cloudfoundry/cloud_controller_ng/issues/1390#issuecomment-775888553 contributed by @FelisiaM in https://github.com/cloudfoundry/cloud_controller_ng/pull/2116 : the dashboard url can now be returned in the GET /v2/service_instances/:instance_id/last_operation, i.e. once the terraform apply has complete, and one output variable was returned specifying the dashboard URL value.
This makes it possible to have the returned dashboard url be more precise and include reference to ids generated during terraform apply, such as https://console.cloud.google.com/sql/instances//overview?project=&authuser=2

thanks for the update macela.


TypeError: BaseTransportService.run() takes 1 positional argument but 2 were given

I'm running 01-say-one-thing.py - having made no modifications to it, just passing it a URL and token. I see this cryptic error:
File "/Users/ddd/daily-ai-sdk/src/examples/foundational/01-say-one-thing.py", line 51, in
asyncio.run(main(url))
File "/Users/ddd/opt/anaconda3/envs/py311/lib/python3.11/asyncio/runners.py", line 190, in run
return runner.run(main)
^^^^^^^^^^^^^^^^
File "/Users/ddd/opt/anaconda3/envs/py311/lib/python3.11/asyncio/runners.py", line 118, in run
return self._loop.run_until_complete(task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/ddd/opt/anaconda3/envs/py311/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/Users/ddd/daily-ai-sdk/src/examples/foundational/01-say-one-thing.py", line 45, in main
await transport.run(pipeline)
^^^^^^^^^^^^^^^^^^^^^^^
TypeError: BaseTransportService.run() takes 1 positional argument but 2 were given

I believe this should be fixed now. Thank you @philtsip !


[Apple Reminders] Ability to set hashtags

Extension
https://www.raycast.com/raycast/apple-reminders
Description
it'd be useful to allow users to also set hashtags
Who will benefit from this feature?
users who categorize their reminders with tags
Anything else?
No response

Thanks for the feature request! However, Apple doesn't provide that feature in their APIs unfortunately, so I'll mark this issue as not planned.


Invalid road classification for link roads

Recently came across some link roads which are tagged with wrong road classification. I think it's possible to write linter for this cases and detect all the mistagged roads.
Example:

This is not a priority. I would like to take this as a learning experience and learn how to write this linter.
cc:// @Rub21

A valid condition for a motorway_link is that one of its end is connected to another segment of motorway_link or motorway. This could be extended to any class of road as well.

Yep, this is the logic I am thinking as well @planemad, every link road should be connected to the same class of road at least at one end. If this condition is not satisfied it should be detected by this linter.


Add Fygraph API

Fygraph revolutionizes real-time cryptocurrency and fiat data access with its GraphQL API, offering the latest updates on over 1,000 cryptocurrencies and 167 fiat currencies refreshed every minute. Empower your applications with seamless integration, ensuring users have access to the most up-to-date and comprehensive financial data in the rapidly evolving world of digital assets.

Links looks dead


[tvla] Fix trace_start argument handling, auto-determine x-label res for t-test step figure

Please see commit messages for details.

Thanks for the review @vrozic !


Koji upload

Depends on PR#706.  3 commits to implement koji_upload plugin

Now that https://github.com/projectatomic/atomic-reactor/pull/706 is merged you could rebase onto master to avoid conflicts.

Alright, I can update those docs.

Sanity test in an integrated environment passed.

Updated release notes.


Create Meta Passthrough tutorial doc

Adds a tutorial document to introduce users to the Meta passthrough functionality.
I also restructured image storage a tiny bit concerning the scene manager tutorial, since dropping all images in one directory might get a little messy.

@devloglogan Can you update the changelog inCHANGES.md as well.


feature: add a failure notice message to pod rollout failures

Checklist

[ ] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[ ] PR title is ready for changelog and subsystem label(s) applied

Sometimes it isn't clear where a build has failed, and what information is useful for debugging. This reduces the verbosity of the failure script, and adds a failure notice block to help identify where the failure debugging starts.

This is much easier to read and see what's wrong
2022-03-30T15:38:08+11:00 Waiting for deployment "nginx" rollout to finish: 0 of 1 updated replicas are available...
2022-03-30T15:48:00+11:00 error: deployment "nginx" exceeded its progress deadline
2022-03-30T15:48:00+11:00 ##############################################
2022-03-30T15:48:00+11:00 STEP Applying Deployments: Failed at 2022-03-30 04:48:00 (UTC)
2022-03-30T15:48:00+11:00 The information below could be useful in helping debug what went wrong
2022-03-30T15:48:00+11:00 ##############################################
2022-03-30T15:48:00+11:00 Terminated
2022-03-30T15:48:00+11:00 Rollout for nginx failed, tried to gather some startup logs of the containers, hope this helps debugging:
2022-03-30T15:48:00+11:00 ======== /tmp/kubectl-build-deploy/logs/container/nginx/nginx-6559d96654-pbcwv-nginx.log =========
2022-03-30T15:48:00+11:00 2022-03-30T15:38:10.061695539+11:00 Setting up Healthz routing
2022-03-30T15:48:00+11:00 2022-03-30T15:38:10.061859916+11:00 Healthz routing - using PHP
2022-03-30T15:48:00+11:00 2022-03-30T15:38:10.091246663+11:00 2022/03/30 04:38:10 [emerg] 6#6: unexpected end of file, expecting ";" or "}" in /etc/nginx/redirects-map.conf:28
2022-03-30T15:48:00+11:00 2022-03-30T15:38:10.091277565+11:00 nginx: [emerg] unexpected end of file, expecting ";" or "}" in /etc/nginx/redirects-map.conf:28
2022-03-30T15:48:00+11:00
2022-03-30T15:48:00+11:00 ======== /tmp/kubectl-build-deploy/logs/container/nginx/nginx-6559d96654-pbcwv-php.log =========
2022-03-30T15:48:00+11:00 2022-03-30T15:38:19.928182212+11:00 [30-Mar-2022 04:38:19] NOTICE: fpm is running, pid 6
2022-03-30T15:48:00+11:00 2022-03-30T15:38:19.930308565+11:00 [30-Mar-2022 04:38:19] NOTICE: ready to handle connections
2022-03-30T15:48:00+11:00
2022-03-30T15:48:00+11:00 ##############################################
2022-03-30T15:48:00+11:00 If there is any additional information about the status of pods, it will be available here
2022-03-30T15:48:00+11:00 POD/SERVICE NAME	STATUS	CONDITION	MESSAGE
2022-03-30T15:48:00+11:00 nginx-6559d96654-pbcwv	Running	Initialized
2022-03-30T15:48:00+11:00 nginx-6559d96654-pbcwv	Running	Ready	containers with unready status: [nginx]
2022-03-30T15:48:00+11:00 nginx-6559d96654-pbcwv	Running	ContainersReady	containers with unready status: [nginx]
2022-03-30T15:48:00+11:00 nginx-6559d96654-pbcwv	Running	PodScheduled


feat: add ground truth columns to prediction output

What this PR does / why we need it:

The current inference schema does not include columns for ground truth, which is required for batch workflow.
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

NONE

Checklist

[ ] Added unit test, integration, and/or e2e tests
[ ] Tested locally
[ ] Updated documentation
[ ] Update Swagger spec if the PR introduce API changes
[ ] Regenerated Golang and Python client if the PR introduce API changes

Closing this in favor of https://github.com/caraml-dev/merlin/pull/504


Update eufy-security-ws to 0.9.x

When can this be done? The battery bug is supposed to be fixed there (along with many others):
https://github.com/bropat/eufy-security-ws/issues/57#event-6528066794

I copied the eufy-security-addon config to my local add-on folder and incremented the eufy-security-ws version to 0.9.1. Just had to make one change to the eufy-security integration to get the lock entity for my T8500 added to HA after the eufy-security-ws upgrade:
https://github.com/fuatakgun/eufy_security/issues/322#issuecomment-1126903959
I only have the T8500 lock, so not sure if other changes might be needed for other device types, but this was the only major breaking change that I had to resolve.

@jdilly , any documentation online on how to do this?

This has been merged.


Add storybook-sandboxes extension

Description
This extension makes it easy to create new Storybook sandboxes, locally or online. Storybook sandboxes are projects that combines a UI framework (React, Vue, Angular) with a Storybook configuration, so that Storybook can be opened and tested with the framework immediately. This is useful for Storybook contributors that tests out different UI frameworks often.
This extension is a nice wrapper around npx storybook@latest sandbox <TEMPLATE> (for local sandboxes) and storybook.new for online sandboxes.

Screencast
https://github.com/raycast/extensions/assets/5678122/89f6424d-cfb3-426e-a136-eeed49b09f86

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi @JReinhold 👋
Do you mind fixing the linter errors 🙂

@pernielsentikaer should be fixed now.


Create a RoaringBitmap from a long[] starting with an offset: BitSetUtil.bitmapOf(offset, long[])

Create a RoaringBitmap from the given long[], but add offset to each bit from long[].
I have bigger bitsets split as long[] of fixed length n, so if seen as a single bitset, each chunk has an offset. I want to transform these bitsets into a single RoaringBitmap.

map each long[] into RoaringBitmap via BitSetUtil.bitmapOf(offset, long[])
join all results via OR to the final RoaringBitmap

Right now, i have to translate a long[] to an even bigger long[], that can become as big as 512MB, if i have a high offset.
The alternative is to collect each index individually, which takes quite some time.

@okrische
If it is just a matter of adding support for an offset, I think it can be done with an extra function without too much fuss.
We do not currently support 64-bit integers in Roaring. We know that @samytto  did some work elsewhere, but it is not yet in this library.

@okrische
If you do in-place ORs, it shouldn't be too bad performance-wise.

It is not about 64bit (thank goodness). It is just about a single Bitset, that was split into chunks/buckets, kind of in the same way as RoaringBitmap does with containers.

@okrische
I understand. I think.
Don't we just want to add BitSetUtil.bitmapOf(offset, long[]) which is nearly a trivial change?
BTW your membership in the RoaringBitmap organization is private: https://github.com/orgs/RoaringBitmap/people/okrische You may want to make it public (and get a nice badge on your GitHub profile page.)


Update terragrunt support to use terragrunt run-all plan / apply / destroy

Hello I have these version setup on a mac:
go version go1.16.3 darwin/amd64
terragrunt version v0.29.2
Terraform v0.15.3
terragrunt mostly work but I got this for destroy:
     	Error Trace:	destroy.go:18
    	Error:      	Received unexpected error:
    	            	FatalError{Underlying: error while running command: exit status 1; time=2021-05-11T17:41:27+01:00 level=warning msg='destroy-all' is deprecated. Running 'terragrunt run-all destroy -force -input=false -lock=false' instead. Please update your workflows to use 'terragrunt run-all destroy -force -input=false -lock=false', as 'destroy-all' may be removed in the future!

    	            	time=2021-05-11T17:41:27+01:00 level=info msg=Stack at ...:
    	            	╷
    	            	│ Error: Failed to parse command-line flags
    	            	│
    	            	│ flag provided but not defined: -force
    	            	╵
    	            	╷
    	            	│ Error: Too many command line arguments
    	            	│
    	            	│ Expected at most one positional argument.

I looked at the code:
https://github.com/gruntwork-io/terratest/blob/8ef5dc3151259bfdc80a271e10e7e68d0b56d854/modules/terraform/apply.go#L59
https://github.com/gruntwork-io/terratest/blob/8ef5dc3151259bfdc80a271e10e7e68d0b56d854/modules/terraform/plan.go#L124
https://github.com/gruntwork-io/terratest/blob/8ef5dc3151259bfdc80a271e10e7e68d0b56d854/modules/terraform/destroy.go#L33
does it make sense to have these change to:
terragrunt run-all apply

etc...?
or at the very least remove -force in destroy so that it works?

Oh, good point! Yes, we should switch to run-all and remove the deprecated flags. A PR to do this is very welcome, as we're buried at the moment.

ok thanks I will try creating a PR...


Modified code new changes made into index.html file and style.css file @kroy96 @rexyagami

Modified code new changes made into index.html file and style.css file @kroy96 @rexyagami please verify my changes made to the code files.

@bunty12345-blip Sure we will, Good Work :)


python310Packages.BTrees: 4.11.0 -> 4.11.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.BTrees is: "Scalable persistent components"
meta.homepage for python310Packages.BTrees is: "http://packages.python.org/BTrees"
meta.changelog for python310Packages.BTrees is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.11.1 with grep in /nix/store/dc08lvkd9v45zzxg6lymf4r4c55r55fi-python3.10-btrees-4.11.1
found 4.11.1 in filename of file in /nix/store/dc08lvkd9v45zzxg6lymf4r4c55r55fi-python3.10-btrees-4.11.1

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.BTrees
python310Packages.zodb
python39Packages.BTrees
python39Packages.zodb
vulnix

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dc08lvkd9v45zzxg6lymf4r4c55r55fi-python3.10-btrees-4.11.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.BTrees https://github.com/r-ryantm/nixpkgs/archive/3ede217f2dabb1597233f99ec66fde921fde8a2a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dc08lvkd9v45zzxg6lymf4r4c55r55fi-python3.10-btrees-4.11.1
ls -la /nix/store/dc08lvkd9v45zzxg6lymf4r4c55r55fi-python3.10-btrees-4.11.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

python310Packages.BTrees
python310Packages.zodb
python39Packages.BTrees
python39Packages.zodb
vulnix

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.BTrees is: "Scalable persistent components"
meta.homepage for python310Packages.BTrees is: "http://packages.python.org/BTrees"
meta.changelog for python310Packages.BTrees is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.11.2 with grep in /nix/store/wzdy0bm8qzarg02gy3pzknaivh9fqjaw-python3.10-btrees-4.11.2
found 4.11.2 in filename of file in /nix/store/wzdy0bm8qzarg02gy3pzknaivh9fqjaw-python3.10-btrees-4.11.2

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.BTrees
python310Packages.zodb
python39Packages.BTrees
python39Packages.zodb
vulnix

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wzdy0bm8qzarg02gy3pzknaivh9fqjaw-python3.10-btrees-4.11.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.BTrees https://github.com/r-ryantm/nixpkgs/archive/3beee8cca9af765da1d9851744431bc012f2ebe2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wzdy0bm8qzarg02gy3pzknaivh9fqjaw-python3.10-btrees-4.11.2
ls -la /nix/store/wzdy0bm8qzarg02gy3pzknaivh9fqjaw-python3.10-btrees-4.11.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

python310Packages.BTrees
python310Packages.zodb
python39Packages.BTrees
python39Packages.zodb
vulnix

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.BTrees is: "Scalable persistent components"
meta.homepage for python310Packages.BTrees is: "http://packages.python.org/BTrees"
meta.changelog for python310Packages.BTrees is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.11.3 with grep in /nix/store/29kk6nnbn14164bki2wajhnb6zahir02-python3.10-btrees-4.11.3
found 4.11.3 in filename of file in /nix/store/29kk6nnbn14164bki2wajhnb6zahir02-python3.10-btrees-4.11.3

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.BTrees
python310Packages.zodb
python39Packages.BTrees
python39Packages.zodb
vulnix

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/29kk6nnbn14164bki2wajhnb6zahir02-python3.10-btrees-4.11.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.BTrees https://github.com/r-ryantm/nixpkgs/archive/0353f6bc3bbfd29e4f89a85de764b315d2046613.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/29kk6nnbn14164bki2wajhnb6zahir02-python3.10-btrees-4.11.3
ls -la /nix/store/29kk6nnbn14164bki2wajhnb6zahir02-python3.10-btrees-4.11.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

python310Packages.BTrees
python310Packages.zodb
python39Packages.BTrees
python39Packages.zodb
vulnix

Maintainer pings


Add a OnceCell type

This PR adds a OnceCell type similar to the types found in the once_cell crate and the tokio crate. It is usable from both blocking and non-blocking code.

@smol-rs/admins Don't release this yet. I'd like event-listener#30 to be completed so that the changes there can be reflected in the new APIs, to prevent any major version bumps being necessary.

I guess adding no-std support to this crate would require a major version bump anyway. (no-std support would be a breaking change for users who disable the default features)


Let apm list only enabled packages

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
As @lee-dohm  say here right now apm let you list installed packages with apm list --installed --bare > package-list.txt (for backup or to install same packages on several computers with apm install --packages-file package-list.txt).
Would be greatly appreciated a --enabled parameter to list only enabled installed packages, the ones we really use. With the huge amount of packages out there is very common to install/try some and then just disable them to give another try later instead of uninstalling it, so the difference between the list of installed and the subset of enabled could be really big.
Steps to Reproduce

Go to terminal
Run apm list --installed --bare --enabled

Expected behavior: List only installed enabled packages.
Actual behavior: List all installed packages.
Reproduces how often: 100%
Versions
$ lsb_release -d
Description:    Ubuntu 16.04.2 LTS

$ atom --version
Atom    : 1.13.1
Electron: 1.3.13
Chrome  : 52.0.2743.82
Node    : 6.5.0

$ apm --version
apm  1.14.1
npm  3.10.5
node 4.4.5
python 2.7.12
git 2.7.4

Thanks @pabloab :bow:  I couldn't have sworn there's an existing issue for this request but couldn't find it.  If you don't mind, can you re-open in https://github.com/atom/apm so we have it in the right place?

Sorry, my mistake @rsese, reopened on apm, issue #732.


chore: pretty-print => as ↦

Possible since https://github.com/leanprover/lean4/pull/1984.  Thank you, Lean devs!

bors merge


Link from anchor link are break

Description
When I try to use anchor link the link don't work, because # is encode as %23.
In my code :
import { Link } from "@/i18n/routing";
<Link href="/#test"> Test </Link>

In HTML:
<a href="/fr/%23test"> test </a>
Verifications

[X] I've verified that the problem I'm experiencing isn't covered in the docs.
[X] I've searched for similar, existing issues on GitHub and Stack Overflow.
[X] I've compared my app to a working example to look for differences.

Mandatory reproduction URL
...
Reproduction description
Create multiple section with ID as achor.
Create anchor link to access this div.
Expected behaviour
...

3.23.1 -> 3.23.2 fix this problem

Having the same issue at v3.24.0.
I am trying to set up anchor links like this
"/path/[slug][anchor]": {
    de: "/path/[slug][anchor]",
  },

or
"/path/[slug]/[anchor]": {
    de: "/path/[slug]/[anchor]",
  },

or
"/path/[slug]/#[anchor]": {
    de: "/path/[slug]/#[anchor]",
  },

Using it like this:
href={{
    pathname: "/path/[slug][anchor]",
    params: {
      slug: slug,
      anchor: `#${anchor}`,
    },
  }}
```

results in the anchor being encoded as "%23". Any ideas how to work around this?


Use sjtc and generate /clock topic

With https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/pull/1145 it is possible to use use the scaled JTC on systems that don't have the scaling state interface available. This way, we won't have to change the controller in the MoveIt configuration anymore in order to use the example MoveIt package with GZ Sim.
Draft until https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/pull/1145 is merged.

Let's hold on that until the SJTC without required scaling interface is released and synced.


Add Notify building block

@lornajane Good spot on the URL. I've updated the event URL and add an event webhook handler.
As far as updating the README I'm not sure what we could add in there short of writing detailed VAPI instructions. As this is consistent with our existing blocks I'd like to merge and get the Notify example in the docs and we can look at the quickstart READMEs as a separate issue (see #28)


Update toggle-scroll-bars-visibility extension

Description

Huge UX improvement: Previously, this extension worked by executing AppleScript, which opens System Settings and clicks on the radio button with the desired value.
Now, everything works in the background.
Also, the new "View Current Scroll Bars Visibility Value" command was added.
Screencast

https://github.com/raycast/extensions/assets/38916225/45901adc-89ff-456b-a77f-dae0e259e994
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer you should provide an argument Automatic/WhenScrolling/Always, e.g.
npm run script:run Always
You don't have to run it, though. It's just for testing how the script works. After building, you should put the executable binary in the assets/scripts directory, and the actual extension will work with it (of course, it's already done by me).

@pernielsentikaer anyway, I have decided to improve the DX of building and running the script.

The script:build script now automatically places the executable binary for the extension into the assets folder after the build process.
When executing the script:run command without an argument, it will display a message indicating that the argument is required and the possible values.

Checked it, works as expected 👍


feat: allow for optional file upload field

Optional Upload fields were being missed by the generated client because they were of type *graphql.Upload and not graphql.Upload. This adds the type to the switch statement and ignore it if its is nil.

Thanks, @Yamashou!


Updated enable PR Previews message

Updated the message in the CLI to reflect the PR Preview naming

tests are failing 😇

ci-composer is failing wirth node v20 as it happens often lately (timeout).
Tests are green on my machine, I think this can land


Disconnecting from cluster displays connecting

Describe the bug
When you disconnect from a cluster by using the hotbar. You are prompted with the connecting screen and the hotbar icon's click action (and right click active action) both do nothing.
To Reproduce
Steps to reproduce the behavior:

Add a cluster to the hotbar
click on the hotbar icon
wait for the cluster to connect
right click the hotbar icon and click disconnect

Expected behavior
The view should return to the catalog and the cluster should be disconnected
Environment (please complete the following information):

Lens Version: master (regression from v5.0.0-beta.2)

fixed by #2703


fixed undefined value key

Motivation
It fixes issue is #325.
Description
Describe the changes made in this PR. How does it solve the above?
It fixes the appKeyPrefix by checking it's coming as undefined.
Checklist

[ ] Read the contributing guidelines
[ ] Commit messages follow the conventional commits spec
[ ] Performed a self-review of the PR
[ ] Added automated tests
[ ] Manually tested the change

Created a new PR regarding this issue because of some problems with the new changes.
https://github.com/near/near-api-js/pull/927


dprint.experimentalLsp prevents config schema from being loaded

If you set "dprint.experimentalLsp": true and open a dprint config file, VS Code says:

Unable to load schema from 'dprint://schemas/config.json': cannot open dprint://schemas/config.json. Detail: Unable to resolve resource dprint://schemas/config.json.

Disable LSP and reload, and the error goes away.
It looks like the schema provider is a part of the legacy system, and probably just needs to be moved out. https://github.com/dprint/dprint-vscode/blob/main/src/legacy/context.ts#L22

I tried my hand at this, but it's a lot more complicated than I thought because the schema provider is so tied to the "legacy" WorkspaceService. 🙁


Transfer repository to xarray-contrib org

:tada: Looks good to me!

I've sent you an invitation to join the xoak-devs team on the xarray-contrib org!