[no-conditional-assignment]

Feature request
I'd like to request the feature discussed in the original implementation of the no-conditional-assignment rule.
The code I'm cleaning up has the following:
let varName: SomeType | null;
while (varName = maybeNullExpensiveCalculation()) {
  // Do stuff with varName, requiring that it not be null
}

It would be great to be able to just add another set of parens around the assignment, which I think is more or less standard, to avoid having to add a tslint annotation.
Another alternative here is to make it into a while (true) loop with a check and break at the top, but that's a little ugly:
while (true) {
  const varName = maybeNullExpensiveCalculation();
  if (varName === null) break;
  // Do stuff with varName, requiring that it not be null
}

@felipeochoa there's always a third option: disable the rule for the line, making it clear that this assignment is intentional.
let varName: SomeType | null;
// tslint:disable-next-line:no-conditional-assignment
while (varName = maybeNullExpensiveCalculation()) {
  // Do stuff with varName, requiring that it not be null
}

Oh yes. Forgot to mention that somehow!

Is your featuer request that the rule no-conditional-assignment should not show an error when writing the following code:
let varName: SomeType | null;
while ((varName = maybeNullExpensiveCalculation())) {
  // Do stuff with varName, requiring that it not be null
}

?
I would not like such exception since it is not obvious for me how this is different from the code you posted.

The surrounding parentheses are a common convention to tell the linter that you're assigning on purpose

common convention

@felipeochoa can you provide references for that?

GCC has the -Wparentheses option which behaves in this way. (See e.g., this comment)
ESLint defaults to this style (except-parens) for their no-cond-assign rule.
Python assignment expressions are usually required to be enclosed in parens for readability
Etc.

The same applies also fore RegExp assignment in conditionals, such as:
while ((match = someRegExp.exec("string")) {
    ....
}

or
while ((match = someRegExp.exec("string") !== null) {
    ....
}

I see clear condition here and don't think that it's right to mark as a potential problem.

I think both oft these examples are missing one closing paren.
And all the time I'm asking myself: the additional parents are not making a technical difference in the resulting value, right?
So if those are not a problem in your code base, why don't you just disable the rule (on the next-line, file or on the global level...)?
But I the question might be beyond the scope of this feature request.

Closing due to low priority and the deprecation roadmap #4534

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


Integrate pickling support for the Headers object.

This combined with a persisted hash of the file underlying Headers, can be used to load the state quickly avoiding the 4 seconds or so of delay. It is also a lot less invasive than an extension module.

I was hesitant to change __init__, the new version resembles what you suggested :-)

Unit test added. I think the core need from unit testing is to act as a watchdog that the pickling/unpickling works, in case the implementation accidentally breaks it. One cursory check that the restored object is the same as the original one should suffice, because at some point you are just testing the pickling concept in general.
I can't work out how to get the original headers object to release the file, so I can't call basic_setup as it hits a PermissionError in trying to open it.

Ok, should be all done.


Release new version with ios implementation

Describe the bug
The master branch has ios implementation but the latest release (0.0.4) implement only android platform.

I can confirm this is still happening and it is a critical issue for any user that want support for iOS...
Please just launch a new release from master asap.
Current content of Plugin.swift in the latest release (0.0.4)
`import Foundation
import Capacitor
/**

Please read the Capacitor iOS Plugin Development Guide

here: https://capacitor.ionicframework.com/docs/plugins/ios
*/
@objc(SpeechRecognition)
public class SpeechRecognition: CAPPlugin {
@objc func echo(_ call: CAPPluginCall) {
let value = call.getString("value") ?? ""
call.success([
"value": value
])
}
}
`
That is: the default content for a new Plugin. I believe it is a mistake.

@priyankpat could you please publish a new version on npm with the fixes iOS-Implementation? The plugin isn't working otherwise.

released version v1.0.0 to npm


Fix BlobStoreStats exception

We shouldn't log an error message when the blob store stats is shutting down.

Codecov Report

Merging #2183 (4f9092f) into master (05e2b40) will decrease coverage by 58.14%.
The diff coverage is 0.00%.

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


Feature Requester: export certchain from SET_CERTIFICATE

spdm-dump supports export the cert chain from GET_CERTIFICATE command.
Would you help expand it to support SET_CERTIFICATE as well?
[--cert_chain_format] is required before any cert chain file parameter. Default is SPDM.
SPDM means cert chain file includes the Length, Reserved, or RootHash fields. It is needed if root_cert is absent.
RAW means cert chain file does not include the Length, Reserved, or RootHash fields.
[--req_cert_chain_slot_id] is required just before [--req_cert_chain]
[--req_cert_chain] is required to if encapsulated GET_CERTIFICATE is not sent
[--rsp_cert_chain_slot_id] is required just before [--rsp_cert_chain]
[--rsp_cert_chain] is required to if GET_CERTIFICATE is not sent
[--out_req_cert_chain_slot_id] is required just before [--out_req_cert_chain]
[--out_req_cert_chain] can be used if encapsulated GET_CERTIFICATE is sent
[--out_rsp_cert_chain_slot_id] is required just before [--out_rsp_cert_chain]
[--out_rsp_cert_chain] can be used if GET_CERTIFICATE is sent
format: A file containing certificates defined in SPDM spec 'certificate chain format'.
It is one or more ASN.1 DER-encoded X.509 v3 certificates.
It may include multiple certificates, starting from root cert to leaf cert.
It is defined by [--cert_chain_format].

I am OK with that.
@rw8896 , do you want to propose a patch?


still can't work

My friend and I followed all the steps but.....   we can register and login, but then nothing. When you want to start a new conversation, "Seems like you are alone in this world". This is the only thing we can see. If you give me your email, I can send you the screen  shot. Maybe there are still some big bug...

@aa88bb @aslanyanhaik Same issue!!!

@aa88bb @yarodevuci the contacts are appearing from database/Users. Can you please check if there are more than one users in Database?

@aslanyanhaik I have register of course multiple emails and confirmed them. Users are not showing up

okay, will look on that

thank you guys for your feedback

@aslanyanhaik please improve 👍

@aslanyanhaik there is also a hint for you man, why u always login user? Instead you can check for FIRAuth.auth()?.currentUser != nil and if not nil just present the chat VC..

#16

@rahulroxx was checking, seems like the default authentication for db is the one you have suggested.
@yarodevuci @aa88bb have you checked the db access rules? I'm testing the app over and over again and yet can't find that bug.
@yarodevuci app is logs in after initial start to make sure the user is registered in backend. Does
FIRAuth.auth()?.currentUser != nil checks with backend for the user?

I figured out. First you are force to put a picture when registering, or the callback creating the user in the database won't be called. Then you have to change the rules of your storage or the file will never be uploaded to :
 match /{allPaths=**} {       allow read, write;     }


Unrecognized log date

Describe the bug
My log is below
[12/Apr/2021:15:30:20 +0800]<PHONE_NUMBER> <IP_ADDRESS> 28754

and I capture the date field "12/Apr/2021:15:30:20 +0800" for logtime，but kibana show his type is text, Why not time type ?
Does fluentd support this date format?
Your Environment

td-agent version: 4.1
Operating system: centos7.6
Kernel version: 3.10

Your Configuration
my parse config is below
<parse>
    @type multiline
    format_firstline /^---\w{8}---A--/
    format1 /---(?<mod_id>\w{8})---A--.*\[(?<logtime>.*0800)\](?<content>.*)/
    keep_time_key true
    time_key logtime
    localtime true
    time_type string
    timezone "+0800"
    time_format "%d/%b/%Y:%H:%M:%S %z"
  </parse>

Additional context
And I open kibana, the logtime field not time type but text type.
the picture is show this

It is expected behavior because you use keep_time_key true.
The problem is you don't specify proper date format in elasticsearch mapping.
Check ES document first: https://www.elastic.co/guide/en/elasticsearch/reference/current/date.html


Uppercase python -> Python

Minor updates to get rid of python in favour of Python.

Looks good to me


Problem of using the latest API to dump runtime memory

Hi there,
I encountered a problem when using the wasm_runtime_dump_mem_consumption function to dump runtime memory.
When I build with -DWAMR_BUILD_MEMORY_PROFLING=1, It would say undefined referenced to wasm_runtime_dump_mem_consumption(). So I manually removed the condition check before this function.
Then I have another problem which is the following:
../wamr/core/iwasm/common/wasm_runtime_common.c: In function 'wasm_runtime_dump_mem_consumption':
../wamr/core/iwasm/common/wasm_runtime_common.c:905:50: error: 'WASMModuleInstance' {aka 'struct WASMModuleInstance'} has no member named 'max_aux_stack_used'
  905 |             max_aux_stack_used = wasm_module_inst->max_aux_stack_used;
      |                                                  ^~
../wamr/core/iwasm/common/wasm_runtime_common.c:945:23: error: 'WASMExecEnv' {aka 'struct WASMExecEnv'} has no member named 'max_wasm_stack_used'
  945 |               exec_env->max_wasm_stack_used);

Does anyone know how to fix these? I am passing wasm_exec_env_t as the parameter to the function.

Never mind, it's my problem


Given up on semver?

Looking at all the 2.x releases i don't see any attempt to follow semver, with breaking changes and features dotted around in each patch version. Are we expected to just rely on package-lock to stop CI picking up breaking changes unexpectedly now?

There are no changes to the API in 2.x.  If you have a specific bug, please provide actual information.

The changelog says otherwise
On 7 Aug 2018 16:05, johnjbarton<EMAIL_ADDRESS>wrote:
There are no changes to the API in 2.x. If you have a specific bug, please provide actual information.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/karma-runner/karma/issues/3105#issuecomment-411089354, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIDP0iyiq0-GvCIa2Aq14_0fJGyA9esBks5uOayigaJpZM4VyDZZ.

You are welcome to review changes as they occur and suggest improvements.
What breaking changes occurred in 2.0.3?
v3 dropped node 4, a breaking change.

@johnjbarton

What breaking changes occurred in 2.0.3?

I'm afraid I already clearly stated that in my comment:

v3 dropped node 4, a breaking change.

This is correct. However, as visible from the link I put into my comment, I was referring to the releases page: https://github.com/karma-runner/karma/releases/tag/v3.0.0
There it does not include that change. Apparently, the breaking change got documented later in
commit ab9333f4283dded1527d41148fc2d1081afbaa83 specifically in the CHANGELOG.md 10 hours ago. I usually refer to the releases page first and only if those are unmaintained do I consult any changelog files.

v2.0.3 had no breaking change; the docs were wrong due to an old error, and they were corrected.
v3.0.0 had breaking changes; the docs omitted these, turns out 'chore' commits are omitted from the change log. The error has also been corrected.
Next time please consider sending a PR to fix docs.

@johnjbarton Any chance to add this breaking change in https://github.com/karma-runner/karma/releases ?
Missed that when scanning the changelog through this page.

Ugh, 2 changelogs? We should delete one.
I updated the second one as well, thanks.


Suggestion: Hyper + MSYS bash

What about Hyper and Git's MSYS bash?
I'm pretty happy with the setup, plus: the Unicode support!

Closed due inactivity.


AttributeError: module 'tensorflow' has no attribute 'GraphDef'

got an error trying your project...
AttributeError: module 'tensorflow' has no attribute 'GraphDef'
do i need some tweaks to get it working with tensorflow 2.2 ?
appreciate some hints...thx..

i saw your commit-comments for tensorflow 2.x, but overlooked the file ...
https://github.com/blaueck/tf-mtcnn/blob/master/mtcnn_tfv2.py
got it working , great, thanks!

glad you found it. this project it's a little messy.

i got i working and compared it with some of my test mtcnn
i got perfect results on my jetson nano with this: https://github.com/jkjung-avt/tensorrt_demos
but your implemtation hit it , because it recognized all faces in my test image.
great work!!!

thanks, glad to hear that.


topic delete button should not be shown if current user has no rights

If the topic/delete role is not present for the current logged user, it does not make sense to render the topic delete buttons.

a bit more information perhaps how this is occurring. In our config, there are no default roles, so anonymous users should not be able to do anything. So the security -> default roles section is empty. It turns out that the delete button is still present for anonymous users, but is correctly hidden once logged in.

I've just try just now, I can't reproduce the bug.
Are you talking about the topic list ?
When I remove the role topic/delete role on the last dev version (with group based roles), the delete button is remove.
Need more information on this one please :)

Is the dev version published as a jar somewhere ? We don't run docker in our org here...

You can find instruction to get the jar from the docker image from your laptop here : https://github.com/tchiotludo/kafkahq#development-environment


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 315

Questions ?
Please refer to the Backport tool documentation


Handle score 0.0

Handle no impact on system using a lookup exception.

Closing because of conflicts. However, the logic seems sound, so I will get it in the code in a different PR or direct commit.


Update to latest version v1.6.109

Mod version: v1.0.7-a
Game version: v1.6.109
Melon loader version: v0.6.1
Issue: Currently getting repeating error messages and would love to try out some fun debug stuff. Would love to see an update. Thanks!

Sorry for the late response/Lack of updates as I have been busy porting other mods for other games over to a new platform whilst also dealing with life stuff.
But as I tried working on DebugMode but VSMenuModHelper throws a error when I try to make a Tick box detailed in my issue here so stay tuned for a fix hopefully soon.


[release-1.12] Fix service and cluster update missing reason

This is an automated cherry-pick of #35919

@googlebot I consent.


Add a new claim to the existing tenants/organizations

Is your suggestion related to an experience ? Please describe.
From the feature[1] we have introduced a new claim to store the organization which the user is originally managed after sharing to a sub organization. PR[2].
Introduced Identity Claim : http://wso2.org/claims/identity/managedOrg
[1]
[2] https://github.com/wso2/carbon-identity-framework/pull/4879
Describe the improvement

Additional context

Hi team,
This newly introduced claim will be created in the organization creation process. But as for now we are checking whether the data is available for the claim and based on that we are executing a listener. This needs to be improved by checking whether the claim is available in the organization and then proceed with the listener execution. [1] will track down the fixing.
[1] https://github.com/wso2/product-is/issues/17687
Best regards,
Shan.

According to https://github.com/wso2/product-is/issues/17633#issuecomment-1803115638 and the feature design new claim is required only for organizations.
The organization creation is introduced to default IS in IS-7.0.0 as a new feature.
Therefore, no need to add the new claim to migrating users' existing tenants.
Hence closing the migration issue

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Improve Type checking on related properties

Is your feature request related to a problem? Please describe.
I spent a while today investigating why the following template didn't work.  The problem ultimately being that the logAnalytics resource was using the wrong type (it should be Microsoft.OperationalInsights/workspace), and thus produced the wrong resource id
resource appInsights 'Microsoft.Insights/components@2020-02-02' = {
  properties: {
    WorkspaceResourceId: logAnalytics.id
  }
}

resource logAnalytics 'Microsoft.OperationalInsights/clusters@2021-06-01' existing = {
  name: workspaceName
}

This feels like an error the bicep type system could capture.
Describe the solution you'd like
Ideally bicep should know that WorkspaceResourceId is looking for a resource id of a Microsoft.OperationalInsights/workspace.  The bicep type system could then know that logAnalytics.id is not a resource id of Microsoft.OperationalInsights/workspace and produce a compile error.
This would require some kind of annotation in the API specs so that bicep would know that WorkspaceResoruceId maps to the resoruce id of a Microsoft.OperationalInsights/workspace resource.  OpenApi's format property could be useful here e.g.
        "WorkspaceResourceId": {
          "type": "string",
          "format": "Microsoft.OperationalInsights/workspace.id",
          "description": "Resource Id of the log analytics workspace which the data will be ingested to. This property is required to create an application with this API version. Applications from older versions will not have this property."
        },

https://github.com/Azure/azure-rest-api-specs/blob/5582a35deb1bfa4aa22bac8f1d51b7934ead94ac/specification/applicationinsights/resource-manager/Microsoft.Insights/stable/2020-02-02/components_API.json#L585-L588
The problem with this solution is you still need to support arbitrary strings for backwards compatibility.  This brings you back to the problem with name for child resources today where the compiler sometimes detects errors, but not always
An alternative solution for scenarios like this is to generate a property that takes the resource type directly.
resource appInsights 'Microsoft.Insights/components@2020-02-02' = {
  properties: {
    Workspace: logAnalytics
  }
}

The bicep compiler would ultimately lower this to use WorkspaceResourceId:
resource appInsights 'Microsoft.Insights/components@2020-02-02' = {
  properties: {
    WorkspaceResourceId: logAnalytics.id
  }
}

This has the advantage of knowing that when you use Workspace, you always get the compiler validation, and when you use WorkspaceResourceId you never get validation (beyond it being a string), but it may cause confusion now there is both Workspace and WorkspaceResourceId.

We agree that Bicep should be able to capture these sorts of things and it could definitely be added, but the hard part is getting this type information properly catalogued in swagger. From our experience with what-if, this is..hard. We would need a top-down initiative to drive this.
Will leave this open to collect reactions, comments, etc.


parseFloat vs timeParse inconsistent

"parse" should either be the first or second word.

Yes and no. parseFloat is consistent with the JS method. timeParse is consistent with timeFormat, etc which is consistent with D3. I see the point here, but not sure it is important enough to warrant breaking changes.

Also, timeParse is not defined in this repo, so closing the issue here.


[MINOR] [ML] remove MLlibTestsSparkContext from ImpuritySuite

ImpuritySuite doesn't need SparkContext.

Test build #45882 has started for PR 9698 at commit a58ab3b.

Test build #45882 has finished for PR 9698 at commit a58ab3b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class ImpuritySuite extends SparkFunSuite \n

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

Merged build finished. Test PASSed.

Merged into master and branch-1.6.


DO NOT REVIEW: test JenkinsFile

Just test jenkinsfile grammar, will close later.

Jenkins job istio/presubmit passed


Write-HostColor - Bringing color to your console

This introduces an internal command - Write-HostColor - that allows printing colored messages to the screen. This is now called by Write-Message allowing us to provide colored messages for the end user.
Example:
Write-Message -Level Output -Message "Connecting to <c="green">$SqlInstance</c>"

LOL alright


New Joint Velocity Error On Example Effort Controller.

So, the examples previously worked on system version 5.6, and libfranka version 0.13, but on some of our arms, we have system version 5.7.1 and libfranka version 0.14.0.
On the arms with the newer system software/libfranka, when we run the gravity compensation example controller, we run into a joint velocity error that we previously did not experience on the older software version. We can successfully run the example controllers which command joint velocities such as the joint velocity example controller. It appears that any example controller that commands efforts produces a joint velocity limit error immediately as the arm starts up.
This is preventing us from operating our arms on the new firmware version (5.7). We have re-set the mass properties to the defaults, but the issue still persists. Are there any other troubleshooting steps we can take for this issue?
glvov@BDAI:/workspaces$ ros2 launch franka_bringup gravity_compensation_example_controller.launch.py robot_ip:=<OUR_IP>
[INFO] [launch]: All log files can be found below /home/glvov/.ros/log/2024-11-12-22-28-19-510121-P3-WS02-67120
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [joint_state_publisher-1]: process started with pid [67121]
[INFO] [robot_state_publisher-2]: process started with pid [67123]
[INFO] [ros2_control_node-3]: process started with pid [67125]
[INFO] [spawner-4]: process started with pid [67127]
[INFO] [spawner-5]: process started with pid [67129]
[INFO] [franka_gripper_node-6]: process started with pid [67131]
[INFO] [spawner-7]: process started with pid [67133]
[franka_gripper_node-6] [INFO] [1731450499.924335518] [fr3_gripper]: Trying to establish a connection with the gripper
[franka_gripper_node-6] [INFO] [1731450499.925185459] [fr3_gripper]: Connected to gripper
[ros2_control_node-3] [WARN] [1731450499.944939571] [controller_manager]: [Deprecated] Passing the robot description parameter directly to the control_manager node is deprecated. Use '~/robot_description' topic from 'robot_state_publisher' instead.
[robot_state_publisher-2] [WARN] [1731450499.945051052] [kdl_parser]: The root link fr3_link0 has an inertia specified in the URDF, but KDL does not support a root link with an inertia.  As a workaround, you can add an extra dummy link to your URDF.
[robot_state_publisher-2] [INFO] [1731450499.945110707] [robot_state_publisher]: got segment fr3_hand
[robot_state_publisher-2] [INFO] [1731450499.945132656] [robot_state_publisher]: got segment fr3_hand_tcp
[robot_state_publisher-2] [INFO] [1731450499.945136655] [robot_state_publisher]: got segment fr3_leftfinger
[robot_state_publisher-2] [INFO] [1731450499.945139546] [robot_state_publisher]: got segment fr3_link0
[robot_state_publisher-2] [INFO] [1731450499.945142387] [robot_state_publisher]: got segment fr3_link1
[robot_state_publisher-2] [INFO] [1731450499.945145168] [robot_state_publisher]: got segment fr3_link2
[robot_state_publisher-2] [INFO] [1731450499.945147858] [robot_state_publisher]: got segment fr3_link3
[robot_state_publisher-2] [INFO] [1731450499.945150697] [robot_state_publisher]: got segment fr3_link4
[robot_state_publisher-2] [INFO] [1731450499.945153480] [robot_state_publisher]: got segment fr3_link5
[robot_state_publisher-2] [INFO] [1731450499.945156206] [robot_state_publisher]: got segment fr3_link6
[robot_state_publisher-2] [INFO] [1731450499.945158992] [robot_state_publisher]: got segment fr3_link7
[robot_state_publisher-2] [INFO] [1731450499.945161634] [robot_state_publisher]: got segment fr3_link8
[robot_state_publisher-2] [INFO] [1731450499.945164274] [robot_state_publisher]: got segment fr3_rightfinger
[ros2_control_node-3] [INFO] [1731450499.945144234] [resource_manager]: Loading hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731450499.951567316] [resource_manager]: Initialize hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731450499.951627835] [FrankaHardwareInterface]: Connecting to robot at "<IP_ADDRESS>" ...
[ros2_control_node-3] [INFO] [1731450499.959794707] [FrankaHardwareInterface]: Successfully connected to robot
[ros2_control_node-3] [INFO] [1731450499.962527595] [service_server]: Service started
[ros2_control_node-3] [INFO] [1731450500.066416818] [action_server]: Action server started
[ros2_control_node-3] [INFO] [1731450500.066486343] [resource_manager]: Successful initialization of hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731450500.066651901] [resource_manager]: 'configure' hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731450500.066669786] [resource_manager]: Successful 'configure' of hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731450500.066685614] [resource_manager]: 'activate' hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731450500.067884474] [FrankaHardwareInterface]: Started
[ros2_control_node-3] [INFO] [1731450500.067901969] [resource_manager]: Successful 'activate' of hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731450500.070049416] [controller_manager]: update rate is 1000 Hz
[ros2_control_node-3] [INFO] [1731450500.071813697] [controller_manager]: Successful set up FIFO RT scheduling policy with priority 50.
[joint_state_publisher-1] [INFO] [1731450500.218822661] [joint_state_publisher]: Waiting for robot_description to be published on the robot_description topic...
[ros2_control_node-3] [INFO] [1731450500.230308722] [controller_manager]: Loading controller 'joint_state_broadcaster'
[spawner-4] [INFO] [1731450500.247318774] [spawner_joint_state_broadcaster]: Loaded joint_state_broadcaster
[ros2_control_node-3] [INFO] [1731450500.247964333] [controller_manager]: Configuring controller 'joint_state_broadcaster'
[ros2_control_node-3] [INFO] [1731450500.248058412] [joint_state_broadcaster]: 'joints' or 'interfaces' parameter is empty. All available state interfaces will be published
[spawner-4] [INFO] [1731450500.252504314] [spawner_joint_state_broadcaster]: Configured and activated joint_state_broadcaster
[ros2_control_node-3] [INFO] [1731450500.258843356] [controller_manager]: Loading controller 'franka_robot_state_broadcaster'
[ros2_control_node-3] [INFO] [1731450500.264707912] [controller_manager]: Loading controller 'gravity_compensation_example_controller'
[spawner-5] [INFO] [1731450500.280532937] [spawner_franka_robot_state_broadcaster]: Loaded franka_robot_state_broadcaster
[spawner-7] [INFO] [1731450500.280666064] [spawner_gravity_compensation_example_controller]: Loaded gravity_compensation_example_controller
[ros2_control_node-3] [INFO] [1731450500.281156900] [controller_manager]: Configuring controller 'franka_robot_state_broadcaster'
[ros2_control_node-3] [INFO] [1731450500.301187283] [controller_manager]: Configuring controller 'gravity_compensation_example_controller'
[spawner-5] [INFO] [1731450500.304450348] [spawner_franka_robot_state_broadcaster]: Configured and activated franka_robot_state_broadcaster
[INFO] [spawner-4]: process has finished cleanly [pid 67127]
[INFO] [spawner-5]: process has finished cleanly [pid 67129]
[ros2_control_node-3] terminate called after throwing an instance of 'franka::ControlException'
[ros2_control_node-3]   what():  libfranka: Move command aborted: motion aborted by reflex! ["joint_velocity_violation"]
[ERROR] [ros2_control_node-3]: process has died [pid 67125, exit code -6, cmd '/opt/ros/humble/lib/controller_manager/ros2_control_node --ros-args --params-file /workspaces/bdai/_build/install/franka_bringup/share/franka_bringup/config/controllers.yaml --params-file /tmp/launch_params_bndpm7pl --params-file /tmp/launch_params_tn9dp3vs --params-file /tmp/launch_params_q6gqi342 -r joint_states:=franka/joint_states'].
[INFO] [launch]: process[ros2_control_node-3] was required: shutting down launched system
[INFO] [spawner-7]: sending signal 'SIGINT' to process[spawner-7]
[INFO] [franka_gripper_node-6]: sending signal 'SIGINT' to process[franka_gripper_node-6]
[INFO] [robot_state_publisher-2]: sending signal 'SIGINT' to process[robot_state_publisher-2]
[INFO] [joint_state_publisher-1]: sending signal 'SIGINT' to process[joint_state_publisher-1]
[franka_gripper_node-6] [INFO] [1731450500.554413836] [rclcpp]: signal_handler(signum=2)
[robot_state_publisher-2] [INFO] [1731450500.554733474] [rclcpp]: signal_handler(signum=2)
[INFO] [joint_state_publisher-1]: process has finished cleanly [pid 67121]
[INFO] [franka_gripper_node-6]: process has finished cleanly [pid 67131]
[INFO] [robot_state_publisher-2]: process has finished cleanly [pid 67123]
[ERROR] [spawner-7]: process[spawner-7] failed to terminate '5' seconds after receiving 'SIGINT', escalating to 'SIGTERM'
[INFO] [spawner-7]: sending signal 'SIGTERM' to process[spawner-7]
[ERROR] [spawner-7]: process has died [pid 67133, exit code -15, cmd '/opt/ros/humble/lib/controller_manager/spawner gravity_compensation_example_controller --ros-args'].
glvov@bdai_docker:/workspaces/bdai$ ros2 launch franka_bringup joint_velocity_example_controller.launch.py robot_ip:=<IP_ADDRESS>
[INFO] [launch]: All log files can be found below /home/glvov/.ros/log/2024-11-12-22-36-51-760872-P3-WS02-67371
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [joint_state_publisher-1]: process started with pid [67372]
[INFO] [robot_state_publisher-2]: process started with pid [67374]
[INFO] [ros2_control_node-3]: process started with pid [67376]
[INFO] [spawner-4]: process started with pid [67378]
[INFO] [spawner-5]: process started with pid [67380]
[INFO] [franka_gripper_node-6]: process started with pid [67382]
[INFO] [spawner-7]: process started with pid [67384]
[franka_gripper_node-6] [INFO] [1731451012.160127193] [fr3_gripper]: Trying to establish a connection with the gripper
[franka_gripper_node-6] [INFO] [1731451012.160912236] [fr3_gripper]: Connected to gripper
[robot_state_publisher-2] [WARN] [1731451012.169578644] [kdl_parser]: The root link fr3_link0 has an inertia specified in the URDF, but KDL does not support a root link with an inertia.  As a workaround, you can add an extra dummy link to your URDF.
[robot_state_publisher-2] [INFO] [1731451012.169653794] [robot_state_publisher]: got segment fr3_hand
[robot_state_publisher-2] [INFO] [1731451012.169675664] [robot_state_publisher]: got segment fr3_hand_tcp
[robot_state_publisher-2] [INFO] [1731451012.169679785] [robot_state_publisher]: got segment fr3_leftfinger
[robot_state_publisher-2] [INFO] [1731451012.169682739] [robot_state_publisher]: got segment fr3_link0
[robot_state_publisher-2] [INFO] [1731451012.169685600] [robot_state_publisher]: got segment fr3_link1
[robot_state_publisher-2] [INFO] [1731451012.169688355] [robot_state_publisher]: got segment fr3_link2
[robot_state_publisher-2] [INFO] [1731451012.169691078] [robot_state_publisher]: got segment fr3_link3
[robot_state_publisher-2] [INFO] [1731451012.169693921] [robot_state_publisher]: got segment fr3_link4
[robot_state_publisher-2] [INFO] [1731451012.169696716] [robot_state_publisher]: got segment fr3_link5
[robot_state_publisher-2] [INFO] [1731451012.169699437] [robot_state_publisher]: got segment fr3_link6
[robot_state_publisher-2] [INFO] [1731451012.169702211] [robot_state_publisher]: got segment fr3_link7
[robot_state_publisher-2] [INFO] [1731451012.169704946] [robot_state_publisher]: got segment fr3_link8
[robot_state_publisher-2] [INFO] [1731451012.169707594] [robot_state_publisher]: got segment fr3_rightfinger
[ros2_control_node-3] [WARN] [1731451012.175648683] [controller_manager]: [Deprecated] Passing the robot description parameter directly to the control_manager node is deprecated. Use '~/robot_description' topic from 'robot_state_publisher' instead.
[ros2_control_node-3] [INFO] [1731451012.175954311] [resource_manager]: Loading hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451012.183129767] [resource_manager]: Initialize hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451012.183170223] [FrankaHardwareInterface]: Connecting to robot at "<IP_ADDRESS>" ...
[ros2_control_node-3] [INFO] [1731451012.190776886] [FrankaHardwareInterface]: Successfully connected to robot
[ros2_control_node-3] [INFO] [1731451012.192862889] [service_server]: Service started
[ros2_control_node-3] [INFO] [1731451012.295539532] [action_server]: Action server started
[ros2_control_node-3] [INFO] [1731451012.295598018] [resource_manager]: Successful initialization of hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451012.295753714] [resource_manager]: 'configure' hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451012.295769467] [resource_manager]: Successful 'configure' of hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451012.295783796] [resource_manager]: 'activate' hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451012.296501378] [FrankaHardwareInterface]: Started
[ros2_control_node-3] [INFO] [1731451012.296515538] [resource_manager]: Successful 'activate' of hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451012.298272526] [controller_manager]: update rate is 1000 Hz
[ros2_control_node-3] [INFO] [1731451012.299380046] [controller_manager]: Successful set up FIFO RT scheduling policy with priority 50.
[ros2_control_node-3] [INFO] [1731451012.458456080] [controller_manager]: Loading controller 'joint_state_broadcaster'
[ros2_control_node-3] [INFO] [1731451012.463107504] [controller_manager]: Loading controller 'joint_velocity_example_controller'
[ros2_control_node-3] [INFO] [1731451012.465550564] [controller_manager]: Loading controller 'franka_robot_state_broadcaster'
[spawner-4] [INFO] [1731451012.482403340] [spawner_joint_state_broadcaster]: Loaded joint_state_broadcaster
[ros2_control_node-3] [INFO] [1731451012.483010827] [controller_manager]: Configuring controller 'joint_state_broadcaster'
[ros2_control_node-3] [INFO] [1731451012.483096190] [joint_state_broadcaster]: 'joints' or 'interfaces' parameter is empty. All available state interfaces will be published
[spawner-7] [INFO] [1731451012.483889370] [spawner_joint_velocity_example_controller]: Loaded joint_velocity_example_controller
[ros2_control_node-3] [INFO] [1731451012.484746571] [controller_manager]: Configuring controller 'joint_velocity_example_controller'
[ros2_control_node-3] [INFO] [1731451012.486332885] [joint_velocity_example_controller]: Extracted Robot Name: fr3
[ros2_control_node-3] [INFO] [1731451012.488744365] [joint_velocity_example_controller]: Default collision behavior set.
[spawner-5] [INFO] [1731451012.490476340] [spawner_franka_robot_state_broadcaster]: Loaded franka_robot_state_broadcaster
[joint_state_publisher-1] [INFO] [1731451012.491610252] [joint_state_publisher]: Waiting for robot_description to be published on the robot_description topic...
[ros2_control_node-3] [INFO] [1731451012.503637726] [controller_manager]: Configuring controller 'franka_robot_state_broadcaster'
[spawner-4] [INFO] [1731451012.525918537] [spawner_joint_state_broadcaster]: Configured and activated joint_state_broadcaster
[spawner-7] [INFO] [1731451012.529965636] [spawner_joint_velocity_example_controller]: Configured and activated joint_velocity_example_controller
[spawner-5] [INFO] [1731451012.532054806] [spawner_franka_robot_state_broadcaster]: Configured and activated franka_robot_state_broadcaster
[INFO] [spawner-5]: process has finished cleanly [pid 67380]
[INFO] [spawner-4]: process has finished cleanly [pid 67378]
[INFO] [spawner-7]: process has finished cleanly [pid 67384]
^C[WARNING] [launch]: user interrupted with ctrl-c (SIGINT)
[ros2_control_node-3] [INFO] [1731451139.009707843] [rclcpp]: signal_handler(signum=2)
[franka_gripper_node-6] [INFO] [1731451139.009707660] [rclcpp]: signal_handler(signum=2)
[robot_state_publisher-2] [INFO] [1731451139.009806835] [rclcpp]: signal_handler(signum=2)
[INFO] [joint_state_publisher-1]: process has finished cleanly [pid 67372]
[INFO] [franka_gripper_node-6]: process has finished cleanly [pid 67382]
[INFO] [robot_state_publisher-2]: process has finished cleanly [pid 67374]
[ERROR] [ros2_control_node-3]: process[ros2_control_node-3] failed to terminate '5' seconds after receiving 'SIGINT', escalating to 'SIGTERM'
[INFO] [ros2_control_node-3]: sending signal 'SIGTERM' to process[ros2_control_node-3]
[ERROR] [ros2_control_node-3]: process has died [pid 67376, exit code -15, cmd '/opt/ros/humble/lib/controller_manager/ros2_control_node --ros-args --params-file /workspaces/bdai/_build/install/franka_bringup/share/franka_bringup/config/controllers.yaml --params-file /tmp/launch_params_ccx1uqcq --params-file /tmp/launch_params_yt7spnlz --params-file /tmp/launch_params_gzaklr54 -r joint_states:=franka/joint_states'].
[INFO] [launch]: process[ros2_control_node-3] was required: shutting down launched system

glvov@bdai_docker:/workspaces/bdai$ ros2 launch franka_bringup gravity_compensation_example_controller.launch.py robot_ip:=<OUR_IP>
[INFO] [launch]: All log files can be found below /home/glvov/.ros/log/2024-11-12-22-39-08-283605-P3-WS02-67616
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [joint_state_publisher-1]: process started with pid [67617]
[INFO] [robot_state_publisher-2]: process started with pid [67619]
[INFO] [ros2_control_node-3]: process started with pid [67621]
[INFO] [spawner-4]: process started with pid [67623]
[INFO] [spawner-5]: process started with pid [67625]
[INFO] [franka_gripper_node-6]: process started with pid [67627]
[INFO] [spawner-7]: process started with pid [67629]
[franka_gripper_node-6] [INFO] [1731451148.673444851] [fr3_gripper]: Trying to establish a connection with the gripper
[franka_gripper_node-6] [INFO] [1731451148.674298481] [fr3_gripper]: Connected to gripper
[robot_state_publisher-2] [WARN] [1731451148.685419471] [kdl_parser]: The root link fr3_link0 has an inertia specified in the URDF, but KDL does not support a root link with an inertia.  As a workaround, you can add an extra dummy link to your URDF.
[robot_state_publisher-2] [INFO] [1731451148.685484450] [robot_state_publisher]: got segment fr3_hand
[robot_state_publisher-2] [INFO] [1731451148.685508305] [robot_state_publisher]: got segment fr3_hand_tcp
[robot_state_publisher-2] [INFO] [1731451148.685512760] [robot_state_publisher]: got segment fr3_leftfinger
[robot_state_publisher-2] [INFO] [1731451148.685515866] [robot_state_publisher]: got segment fr3_link0
[robot_state_publisher-2] [INFO] [1731451148.685518720] [robot_state_publisher]: got segment fr3_link1
[robot_state_publisher-2] [INFO] [1731451148.685521434] [robot_state_publisher]: got segment fr3_link2
[robot_state_publisher-2] [INFO] [1731451148.685524104] [robot_state_publisher]: got segment fr3_link3
[robot_state_publisher-2] [INFO] [1731451148.685526834] [robot_state_publisher]: got segment fr3_link4
[robot_state_publisher-2] [INFO] [1731451148.685529640] [robot_state_publisher]: got segment fr3_link5
[robot_state_publisher-2] [INFO] [1731451148.685532404] [robot_state_publisher]: got segment fr3_link6
[robot_state_publisher-2] [INFO] [1731451148.685534994] [robot_state_publisher]: got segment fr3_link7
[robot_state_publisher-2] [INFO] [1731451148.685537659] [robot_state_publisher]: got segment fr3_link8
[robot_state_publisher-2] [INFO] [1731451148.685540264] [robot_state_publisher]: got segment fr3_rightfinger
[ros2_control_node-3] [WARN] [1731451148.694218078] [controller_manager]: [Deprecated] Passing the robot description parameter directly to the control_manager node is deprecated. Use '~/robot_description' topic from 'robot_state_publisher' instead.
[ros2_control_node-3] [INFO] [1731451148.694625036] [resource_manager]: Loading hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451148.704797385] [resource_manager]: Initialize hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451148.704851448] [FrankaHardwareInterface]: Connecting to robot at "<IP_ADDRESS>" ...
[ros2_control_node-3] [INFO] [1731451148.712672683] [FrankaHardwareInterface]: Successfully connected to robot
[ros2_control_node-3] [INFO] [1731451148.714686300] [service_server]: Service started
[ros2_control_node-3] [INFO] [1731451148.817034987] [action_server]: Action server started
[ros2_control_node-3] [INFO] [1731451148.817081036] [resource_manager]: Successful initialization of hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451148.817230885] [resource_manager]: 'configure' hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451148.817253381] [resource_manager]: Successful 'configure' of hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451148.817267826] [resource_manager]: 'activate' hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451148.817844283] [FrankaHardwareInterface]: Started
[ros2_control_node-3] [INFO] [1731451148.817850945] [resource_manager]: Successful 'activate' of hardware 'FrankaHardwareInterface'
[ros2_control_node-3] [INFO] [1731451148.819400915] [controller_manager]: update rate is 1000 Hz
[ros2_control_node-3] [INFO] [1731451148.833534367] [controller_manager]: Successful set up FIFO RT scheduling policy with priority 50.
[ros2_control_node-3] [INFO] [1731451148.955645018] [controller_manager]: Loading controller 'joint_state_broadcaster'
[joint_state_publisher-1] [INFO] [1731451148.959268501] [joint_state_publisher]: Waiting for robot_description to be published on the robot_description topic...
[spawner-4] [INFO] [1731451148.970933518] [spawner_joint_state_broadcaster]: Loaded joint_state_broadcaster
[ros2_control_node-3] [INFO] [1731451148.971317920] [controller_manager]: Configuring controller 'joint_state_broadcaster'
[ros2_control_node-3] [INFO] [1731451148.971376225] [joint_state_broadcaster]: 'joints' or 'interfaces' parameter is empty. All available state interfaces will be published
[spawner-4] [INFO] [1731451148.975304944] [spawner_joint_state_broadcaster]: Configured and activated joint_state_broadcaster
[ros2_control_node-3] [INFO] [1731451148.975964718] [controller_manager]: Loading controller 'franka_robot_state_broadcaster'
[ros2_control_node-3] [INFO] [1731451148.983490300] [controller_manager]: Loading controller 'gravity_compensation_example_controller'
[spawner-5] [INFO] [1731451148.994684039] [spawner_franka_robot_state_broadcaster]: Loaded franka_robot_state_broadcaster
[ros2_control_node-3] [INFO] [1731451148.995185044] [controller_manager]: Configuring controller 'franka_robot_state_broadcaster'
[spawner-7] [INFO] [1731451148.998272254] [spawner_gravity_compensation_example_controller]: Loaded gravity_compensation_example_controller
[ros2_control_node-3] [INFO] [1731451149.014988304] [controller_manager]: Configuring controller 'gravity_compensation_example_controller'
[spawner-5] [INFO] [1731451149.018510863] [spawner_franka_robot_state_broadcaster]: Configured and activated franka_robot_state_broadcaster
[ros2_control_node-3] terminate called after throwing an instance of 'franka::ControlException'
[ros2_control_node-3]   what():  libfranka: Move command aborted: motion aborted by reflex! ["joint_velocity_violation"]
[ERROR] [ros2_control_node-3]: process has died [pid 67621, exit code -6, cmd '/opt/ros/humble/lib/controller_manager/ros2_control_node --ros-args --params-file /workspaces/bdai/_build/install/franka_bringup/share/franka_bringup/config/controllers.yaml --params-file /tmp/launch_params_g7ouwz43 --params-file /tmp/launch_params_gc16jfmb --params-file /tmp/launch_params_9khey5b3 -r joint_states:=franka/joint_states'].
[INFO] [launch]: process[ros2_control_node-3] was required: shutting down launched system
[INFO] [spawner-7]: sending signal 'SIGINT' to process[spawner-7]
[INFO] [franka_gripper_node-6]: sending signal 'SIGINT' to process[franka_gripper_node-6]
[INFO] [spawner-5]: sending signal 'SIGINT' to process[spawner-5]
[INFO] [spawner-4]: sending signal 'SIGINT' to process[spawner-4]
[INFO] [robot_state_publisher-2]: sending signal 'SIGINT' to process[robot_state_publisher-2]
[INFO] [joint_state_publisher-1]: sending signal 'SIGINT' to process[joint_state_publisher-1]
[franka_gripper_node-6] [INFO] [1731451149.078741991] [rclcpp]: signal_handler(signum=2)
[robot_state_publisher-2] [INFO] [1731451149.079940118] [rclcpp]: signal_handler(signum=2)
[ERROR] [spawner-4]: process has died [pid 67623, exit code -2, cmd '/opt/ros/humble/lib/controller_manager/spawner joint_state_broadcaster --ros-args'].
[ERROR] [spawner-5]: process has died [pid 67625, exit code -2, cmd '/opt/ros/humble/lib/controller_manager/spawner franka_robot_state_broadcaster --ros-args --params-file /tmp/launch_params_mpyyc7n9'].
[INFO] [joint_state_publisher-1]: process has finished cleanly [pid 67617]
[INFO] [franka_gripper_node-6]: process has finished cleanly [pid 67627]
[INFO] [robot_state_publisher-2]: process has finished cleanly [pid 67619]
[ERROR] [spawner-7]: process[spawner-7] failed to terminate '5' seconds after receiving 'SIGINT', escalating to 'SIGTERM'
[INFO] [spawner-7]: sending signal 'SIGTERM' to process[spawner-7]
[ERROR] [spawner-7]: process has died [pid 67629, exit code -15, cmd '/opt/ros/humble/lib/controller_manager/spawner gravity_compensation_example_controller --ros-args'].
glvov@BDAI:/workspaces/$

@glvov-bdai

Resolved by power cycling the arm

Hi @glvov-bdai ,
if you use libfranka version 0.14.0, then I can recommend to use 0.14.2. Especially, if you use libfranka with ROS 2, it has some juicy fixes on board :smile:
Cheers,
Andreas


Upgrade cs

This change is

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[WIP] [stdlib] Require collection indices to be Hashable

Testing the impact of requiring Collection.Index to be Hashable.

@swift-ci Please test source compatibility.

Closing this, as SE-0188 has been accepted without this additional requirement.


CompatibleProcessor does not convet currency simbol "\u00a5" to JPY

JPY has mainly 2 symbols "\u00a5" or "\xa5" (1 byte char) and "￥" (2 bytes char) and CompatibleProcessor only converts 2 bytes one.
In my environment, YouTube displays JPY super chat with 1 byte symbol, and CompatibleProcessor returns snippet.superChatDetails.currency as just "\u00a5", not "JPY".

When I added context > client > hl as "ja" to request parameter, YouTube returns JPY symbol as "￥" (\uffe5).
https://github.com/StardustSorcery/pytchat/blob/6c7dc03d069136d9ae124b7d47a26660a7c48a0c/pytchat/util/__init__.py#L64-L69

When I added context > client > hl as "ja" to request parameter, YouTube returns JPY symbol as "￥" (\uffe5).
https://github.com/StardustSorcery/pytchat/blob/6c7dc03d069136d9ae124b7d47a26660a7c48a0c/pytchat/util/__init__.py#L64-L69

#3


I think its broken

I was just trying this today and i got this.

Also getting the same issue while using github actions

Working on it

Similar issue in v1.2.2


added spinner and loading state to btns

https://user-images.githubusercontent.com/23319212/189668518-d4d0f81a-db76-47cf-ab53-bc519ff554fa.mov


 This could be much, much better.
Particularly:

Locking - can we switch to a properly-multithreaded sqlite? Or just a real RDBMS? Locking is killing us
DB Profiling - figure out database queries that could be easily optimized - some ranking queries are almost certainly very poorly planned

Late update for anyone following progress in this fork:
Addressed between https://github.com/edelkas/inne/commit/507d90538594636b1d4d7072e3977beab4177024 and https://github.com/edelkas/inne/commit/03a0e8a7affbce071562eb32e05473704262a65d, between 24 Nov 2020 and 29 Nov 2020, optimized rankings 100x, the other functions by similar ratios.


Using shouldBypassCache, should it still return stale-while-revalidate headers?

Discussed in https://github.com/unjs/nitro/discussions/2714

Originally posted by kaitoqueiroz September  5, 2024
Environment:
Operating System: Linux
Node Version: v20.15.0
Nuxt Version: 3.13.0
Package Manager<EMAIL_ADDRESS>Reproduction
https://stackblitz.com/edit/nuxt-starter-kjhdkn?file=server%2Fapi%2Ftest.get.js
⚠ Please be aware that the problem I'm describing can't be reproduced in the stackblitz preview feature, once it runs with ServiceWorker. The code should be downloaded and run locally: npm install then npm run dev
Context:
I'm working on a feature that uses SWR to cache the API responses for a certain period and revalidate after the TTL.
When I switch pages, I make a request to the API, and I want the cache to be bypassed when I set the preview=true query parameter.
The problem is that the browser caches the response regardless, and when the user navigates, it still serves cached data.

Response headers in the first request (uncached):

Code:
export default defineCachedEventHandler(
  async (event) => {
    return new Date();
  },
  {
    // explicitly enable SWR
    swr: true,
    maxAge: 30,
    staleMaxAge: 60 * 60 * 24 * 7, // 1 week
    shouldBypassCache: (event) => {
      const { preview } = getQuery(event);

      return preview === 'true';
    },
  }
);

Is it possible to avoid the response being cached in the browser when the cache is bypassed? Using shouldBypassCache, should it still return stale-while-revalidate headers?
Could anyone help me with that, please?

I'm also facing this problem, no idea how to work around it yet. It seems to me that shouldBypassCache should run every request regardless of other parameters because in it's current state it seems pointless as you cannot bypass cache using it. Same thing goes for shouldInvalidateCache() - runs only when the response wasn't cached yet which makes it unusable (at least i don't see the point of using it in this state).
I've even tried to manually invalidate the cache before the request with an endpoint setup like so:
export default defineEventHandler(async (event) => {
  const storage = useStorage("cache");
  try {
    const cacheKeys = await storage.getKeys("nitro:handlers");

    // Remove all cache items concurrently
    await Promise.all(cacheKeys.map((element) => storage.removeItem(element)));

    return { success: true };
  } catch (error: any) {
    console.error("Error invalidating cache:", error);
    throw createError({
      statusCode: error.statusCode || 500,
      statusMessage: error.message || "Failed to invalidate cache",
    });
  }
});

I've noticed it correctly removes the file from the cache folders in nitro but even after running it, my api endpoint still serves cached response.

@kaitoqueiroz I've opened a new issue with a workaround which might work for you, try it out and let me know if it worked.

I'm facing the same problem. I think we may have to use a caching solution other than Nitro however would love to hear if/when there's a fix

I'm facing the same problem. The workaround in #2738 by @dencs08 just saved me. Also, It would be nice if the Nitro Cache Guide included examples using shouldBypassCache and shouldInvalidateCache


Register Copilot relatedFilesProvider for C#

registerRelatedFilesProvider is a new method on the copilot extension. RelatedDocumentsHandler is implemented here in Roslyn language server.

@dibarbet Could you please take another look? (also I think this doesn't require https://github.com/dotnet/roslyn/pull/75176 to work, since the protocol is still compatible with change in this PR, pls correct me if I was wrong)


Added Final Streak to the overlay

Phant wanted this feature last night so I went ahead and added it, let me know if I made any silly mistakes I usually don't use C#.

Used the wrong account, rebased to fix it and apparently broke it, I'll resubmit it later


Tweak command not found

Running ox db --help outputs:
$ ox db --help
[info] Using github.com/wawandco/ox/cmd/ox

Usage of create:
      --conn string   the name of the connection to use (default "development")
Usage of drop:
      --conn string   the name of the connection to use (default "development")
Usage of reset:
      --conn string   the name of the connection to use (default "development")
Usage of new:
  -f, --force   clear existing folder if found.
Usage of standard/builder:
  -o, --output string   the path the binary will be generated at
      --static          build a static binary using  --ldflags '-linkmode external -extldflags "-static"' (default true)
      --tags strings    tags to pass the go build command
Usage of type:
  -t, --type string   the type of the migration (default "fizz")
[error] unable to find pop config file
[error] subcommand `--help` not found

Seems that it needs a bit of tweaking.

This one is fixed with #25.


[Design QA] View Collective Page - icon alignment / Mobile + Desktop

icons and text should have center alignment
Devs:

Design:

Technical Implementation
To align icons and text to the center in the ViewCollective component, you need to adjust the styles of the elements containing the icons and text. Here's a step-by-step guide on how to modify the code:

Update Icon and Text Container Styles:
For every container that holds an icon and a text, ensure that its style promotes center alignment. This can be achieved with alignItems: 'center' and justifyContent: 'center' properties for a flex container.
Update the styles for collectiveDetailsMobile, icons, and any other relevant container:
collectiveDetailsMobile: {
  flexDirection: 'row',
  alignItems: 'center', // Center items vertically in the row
  justifyContent: 'center', // Center items horizontally
  gap: 8,
},

icons: {
  marginTop: 5,
  flexDirection: 'row',
  alignSelf: 'center',
  alignItems: 'center', // Add this for vertical alignment
  justifyContent: 'space-between', // If you want even spacing between icons
  gap: 24,
},

Text Alignment:
For text elements, ensure that the textAlign property is set to 'center' if you want the text itself to be centered within its container.
title: {
  ...InterSemiBold,
  fontSize: 20,
  color: Colors.black,
  textAlign: 'center', // Center align text
},

informationLabel: {
  ...InterSemiBold,
  fontSize: 14,
  color: Colors.black,
  marginBottom: 16,
  textAlign: 'center', // Center align text
},

Check RowItem Component:
If the RowItem component is used for rendering items with icons and text, ensure it also supports center alignment. You might need to update the styles within the RowItem component as well.

Ensure Consistency Across Resolutions:
Since you have different styles for desktop and mobile (collectiveDesktopData, collectiveDetailsMobile), make sure the alignment is consistent across both.

Test the Changes:
After making these changes, test your application on different devices or screen sizes to ensure that the icons and text are properly aligned and the layout appears as expected.

By following these steps, you'll be able to ensure that icons and text in the ViewCollective component are centered according to the design requirements. Remember to check all related components and styles to maintain consistency throughout the application.

verified on web and mobile


Identifier "Summator" not declared in the current scope

Description:
The Summator example class is not recognized inside GDScript after compiling Godot 4, godot-cpp and the GDExtensionSummator.
Platform: Windows 10, 64 bits
Godot commit version: 622806397
godot-cpp commit version: c4f12ccc3cd19b8fd535d179efd0471386c7f8e9
Steps:

Clone Godot master branch
Run scons platform=windows
Clone GDExtensionSummator repository
Go inside godot-cpp and run scons target=debug generate_bindings=yes
Go back to GDExtensionSummator root and run scons target=debug
Launch Godot from godot/bin/godot.windows.tools.64.exe
Create new project, add script to scene and write var test = Summator.new()

Result:
In the GDScript editor, we can see that Summator is not recognized:
  res://Player.gd:5 - Parse Error: Identifier "Summator" not declared in the current scope.
  modules\gdscript\gdscript.cpp:874 - Method/function failed. Returning: ERR_PARSE_ERROR

Running the scene does not help, it fails at the line where I try to instanciate the Summator object.
I also tried building the release versions for all components and got the same issue.

@CarlCochet Would you mind running the project with the new Alpha 5 again? And with the latest version of godot-cpp. I tried it on both Mac and Windows and it works for me without any flaws.

I tried again this morning, removed every Godot instances from my computer and cloned the newest master branch along with the newest godot-cpp + the extension, I followed the same steps again and it seems to work now! Thanks for the help

Good to hear👍🏻


linear scale for account balances

the logarithmic scale can be confusing in regards to understanding actual trends

Agree. However, the linear scale looks very poor if an account holds a substantial amount of some asset.
I'll add a switch linear|logarithmic scale. By default, a linear scale will be used.

Yeah, a switch would be great.
I think that the root cause of this issue is displaying multiple assets on the same scale. A possible long term solution is introduce multiple scales (similar tho how coinmarketcap do it in history price charts with USD and BTC).

I stumbled on a few accounts that own more than 20 different assets. In case of multiple assets the page may become clogged with charts.
What about a dropdown with asset selector? By default the chart shows all assets in linear scale. A user can switch between log and linear scale and choose a single asset to show on the chart, hiding all other. Both a switch and dropdown are located under the chart.
What do you think?

Yeah, I share your concern.
I think there's very little value in having multiple asset balance history on the same chart when the scales are not individually adjusted (like the cointmarketcap example). Furthermore, even if the scales are adjusted - I'm not sure this is actually important - when do we care about the ratio between the different asset balances for the same account? maybe for super specific market making accounts.
Here's a proposal for a low hanging fruit solution:
Have a single chart, linear scale, with a single asset that defaults to XLM.
Below that - a list of all other assets, along with current balances. When you click on one of them, the chart changes it's data to that asset balance history.
A more comprehensive, yet not necessarily better solution is to have a dropdown like you suggest, but with check-boxes. All checked assets will be displayed together, but with the scale adjusted individually.

Implemented


Add release/v1.22 branch

Now that we have a v1.22 release it would be useful to add a branch for backporting and release testing
cc @mattklein123

https://github.com/envoyproxy/envoy/tree/release/v1.22.0

thanks


Feature/add transactions

What
Add a simple but powerful Transaction interface to the mongodb library
How to review
Review code for sanity/ensure new tests and examples for transactions are clear and passing
Who can review
Anyone, but familiarity with mongodb a bonus

Hi Patrick, your code looks good but VSCode (I've given up with GoLand) is telling me there are problems in the steps.go file at lines 337 and 339. These could be fixed as follows:
update := bson.D{{Key: "$set", Value: bson.D{{Key: "age", Value: age}}}}

Hi Ella thanks for reviewing, but I'm not sure about that change - it's not code that I touched in my PR (seems to have been there since the start of the year), and I'm not getting an issue in my IDE or in the tests?


Checks.hasMaxLength "method doesn't exist" error

Describe the bug
Seems that hasMaxLength method from checks module has some implementation issue.
To Reproduce

A demo spark dataframe was generated as follows:

data = [(1, 'Alice', 34), (2, 'Bob', 36), (3, 'Charlie', 30)]
df = spark.createDataFrame(data, ['id', 'name', 'age'])

Pydeequ modules imported:

from pydeequ.checks import *
from pydeequ.verification import *

Check class instantiated and VerificationSuite ran:

check_length = Check(spark, CheckLevel.Warning, "Check if the column length")

checkResult = (
    VerificationSuite(spark)
    .onData(df)
    .addCheck(check_length.hasMaxLength(column = 'name', assertion = lambda x: x >= 3))
    .run())

Main Py4JException raised:

py4j.Py4JException: Method hasMaxLength([class java.lang.String, class com.sun.proxy.$Proxy93, class scala.None$]) does not exist

Full traceback:

---------------------------------------------------------------------------
Py4JError                                 Traceback (most recent call last)
<command-2160774200945294> in <cell line: 7>()
      7     VerificationSuite(spark)
      8     .onData(df)
----> 9     .addCheck(check_length.hasMaxLength(column = 'name', assertion = lambda x: x >= 3))
     10     .run())
     11

/local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.9/site-packages/pydeequ/checks.py in hasMaxLength(self, column, assertion, hint)
    424         assertion_func = ScalaFunction1(self._spark_session.sparkContext._gateway, assertion)
    425         hint = self._jvm.scala.Option.apply(hint)
--> 426         self._Check = self._Check.hasMaxLength(column, assertion_func, hint)
    427         return self
    428

/databricks/spark/python/lib/py4j-<IP_ADDRESS>-src.zip/py4j/java_gateway.py in __call__(self, *args)
   1319
   1320         answer = self.gateway_client.send_command(command)
-> 1321         return_value = get_return_value(
   1322             answer, self.gateway_client, self.target_id, self.name)
   1323

/databricks/spark/python/pyspark/sql/utils.py in deco(*a, **kw)
    194     def deco(*a: Any, **kw: Any) -> Any:
    195         try:
--> 196             return f(*a, **kw)
    197         except Py4JJavaError as e:
    198             converted = convert_exception(e.java_exception)

/databricks/spark/python/lib/py4j-<IP_ADDRESS>-src.zip/py4j/protocol.py in get_return_value(answer, gateway_client, target_id, name)
    328                     format(target_id, ".", name), value)
    329             else:
--> 330                 raise Py4JError(
    331                     "An error occurred while calling {0}{1}{2}. Trace:\n{3}\n".
    332                     format(target_id, ".", name, value))

Py4JError: An error occurred while calling o829.hasMaxLength. Trace:
py4j.Py4JException: Method hasMaxLength([class java.lang.String, class com.sun.proxy.$Proxy93, class scala.None$]) does not exist
	at py4j.reflection.ReflectionEngine.getMethod(ReflectionEngine.java:341)
	at py4j.reflection.ReflectionEngine.getMethod(ReflectionEngine.java:349)
	at py4j.Gateway.invoke(Gateway.java:297)
	at py4j.commands.AbstractCommand.invokeMethod(AbstractCommand.java:132)
	at py4j.commands.CallCommand.execute(CallCommand.java:79)
	at py4j.ClientServerConnection.waitForCommands(ClientServerConnection.java:195)
	at py4j.ClientServerConnection.run(ClientServerConnection.java:115)
	at java.lang.Thread.run(Thread.java:750)

Expected behavior
The expected was just having en VerificationResult object.
Additional context

environment: Databricks (AWS)
pydeequ version: 1.1.1
deequ version: com.amazon.deequ:deequ:2.0.4-spark-3.3
databricks runtime: 11.3 LTS (includes Apache Spark 3.3.0, Scala 2.12)

Indeed a bug, for a workaround you can give it an actual hint, e.g.
https://github.com/awslabs/python-deequ/blob/e74e974e739f24cccb827a6378cd50e97697a0e8/tests/test_checks.py#L987

Hi Giving hint also giving me the same error
Example:
checkResult = VerificationSuite(spark).onData(df).addCheck(check.hasMaxLength('JobID',lambda x: x == 18,"Column JobID has 18 characters max")).run()
@peixeirodata  is it working for you?

I'm running locally with the same environment and it worked fine - this may have something to do with Databricks runtime.
see code -
    data = [(1, 'Alice', 34), (2, 'Bob', 36), (3, 'Charlie', 30)]
    df = spark.createDataFrame(data, ['id', 'name', 'age'])

    check_length = Check(spark, CheckLevel.Warning, "Check if the column length")

    checkResult = (
        VerificationSuite(spark).onData(df).addCheck(check_length.hasMaxLength(column='name', assertion=lambda x: x >= 3)).run())

    check_result_df = VerificationResult.checkResultsAsDataFrame(spark, checkResult)
    check_result_df.show()

Output:
+--------------------+-----------+------------+--------------------+-----------------+------------------+
|               check|check_level|check_status|          constraint|constraint_status|constraint_message|
+--------------------+-----------+------------+--------------------+-----------------+------------------+
|Check if the colu...|    Warning|     Success|MaxLengthConstrai...|          Success|                  |
+--------------------+-----------+------------+--------------------+-----------------+------------------+

Hey guys. I just tested here again first in the same databricks environment, after that locally with jupyter lab. Same error was raised on both 😔

@peixeirodata could you share details how the jupyter lab environment is setup? Perhaps provide some reproducible Conda like steps.
My local environment is setup like https://github.com/awslabs/python-deequ/blob/master/.github/workflows/base.yml#L35-L39

This probably will have something to do with the API change in Deequ side during different versions. Generally Scala default parameters might be hard to deal with from Python, see https://github.com/awslabs/python-deequ/pull/168#issuecomment-1780329147. I will discuss internally to see the best path forward

What's the SPARK_VERSION variable you are setting in the failure cases? @Ashokgoa @peixeirodata

Sorry for my delay in replying guys.
@chenliu0831 I'll check if I can provide you a conda file. About the variable:
SPARK_VERSION=3.3.2

Ok - I think I figured out why I cannot reproduce this. com.amazon.deequ:deequ:2.0.4-spark-3.3 wasn't a supported version yet due to breaking Scala API (optional parameter introduced in Scala).  This has caused multiple issues and we have to discuss internally to fix it in Scala land.
If possible use deequ 2.0.3 which will work. https://github.com/awslabs/python-deequ/blob/master/pydeequ/configs.py#L8

Sorry i am off for few days ..Thanks @chenliu0831

This will be resolved in next release which will include https://github.com/awslabs/python-deequ/issues/169.


"az vm image terms accept" failure in AzureUSGovernment sovereign cloud when using --urn to identify image

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
When connected with to Azure Government using az cli when I go to accept the terms of a Marketplace image with az vm image terms accept --urn {your image urn} it throws the below error:

(NoRegisteredProviderFound) No registered resource provider found for location 'global' and API version '2020-12->01' for type 'locations/publishers'. The supported api-versions are '2015-05-01-preview, 2015-06-15, 2016-03-30, >2016-04-30-preview, 2016-08-30, 2017-03-30, 2017-12-01, 2018-04-01, 2018-06-01, 2018-10-01, 2019-03-01, 2019->07-01, 2019-12-01, 2020-06-01, 2020-09-30, 2020-12-01, 2021-03-01'. The supported locations are 'usgoviowa, >usgovvirginia, usdodcentral, usdodeast, usgovtexas, usgovarizona'.

To Reproduce

Log into Azure Government
Launch a new Cloud Shell session
Run the following command:  az vm image terms accept --urn cisco:cisco-csr-1000v:16_10-payg-sec:16.10.120190108 --debug

Expected behavior

I would expect to be able to accept the license terms programmatically with the above command.

Environment summary

Leveraging AZ CLI 2.23.0, from within an Azure Government Cloud Shell Session (pre-installed)

Additional context
N/A

seems caused by reosurce API version upgrading.

Super excited for this to be patched in August. Lot's of automation around marketplace terms agreement. Please reach out if you need someone to test the newest build

@avlind @adamdost-msft  Hi, it seems that this issue cannot be reproduced in the latest version of CLI. Could you please upgrade the CLI version and then try again? You can use the command az upgrade to upgrade CLI.
If you can reproduce this issue in the latest version, please send me the debug log by email. My email address is Zhou.Xing@microsoft, thanks

Current version i'm using is 2.26.0 as that's what is available via CloudShell in MAG. If 2.26.1 has this fixed then I will need to have the CloudShell team upgrade it to 2.26.1.

@adamdost-msft This issue is not fixed in 2.26.1. Actually, this issue can't be reproduced in version 2.26.0 on my side. Can you reproduce it in version 2.26.0?

Yes I can. Here is the debug output from version 2.26.0 in Azure Government.
cli.knack.cli: Command arguments: ['vm', 'image', 'terms', 'accept', '--urn', 'cisco:cisco-csr-1000v:16_10-payg-sec:16.10.120190108', '--debug']
cli.knack.cli: __init__ debug log:
Enable color in terminal.
cli.knack.cli: Event: Cli.PreExecute []
cli.knack.cli: Event: CommandParser.OnGlobalArgumentsCreate [<function CLILogging.on_global_arguments at 0x7fa470483bf8>, <function OutputProducer.on_global_arguments at 0x7fa4703b9730>, <function CLIQuery.on_global_arguments at 0x7fa4703d1840>]
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableCreate []
cli.azure.cli.core: Modules found from index for 'vm': ['azure.cli.command_modules.vm']
cli.azure.cli.core: Loading command modules:
cli.azure.cli.core: Name                  Load Time    Groups  Commands
cli.azure.cli.core: vm                        0.123        45       235
cli.azure.cli.core: Total (1)                 0.123        45       235
cli.azure.cli.core: These extensions are not installed and will be skipped: ['azext_next']
cli.azure.cli.core: Loading extensions:
cli.azure.cli.core: Name                  Load Time    Groups  Commands  Directory
cli.azure.cli.core: ai-examples               0.082         1         1  /opt/az/lib/python3.6/site-packages/azure-cli-extensions/ai-examples
cli.azure.cli.core: Total (1)                 0.082         1         1
cli.azure.cli.core: Loaded 46 groups, 236 commands.
cli.azure.cli.core: Found a match in the command table.
cli.azure.cli.core: Raw command  : vm image terms accept
cli.azure.cli.core: Command table: vm image terms accept
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableTruncate [<function AzCliLogging.init_command_file_logging at 0x7fa46fefc048>]
cli.azure.cli.core.azlogging: metadata file logging enabled - writing logs to '/home/adam/.azure/commands/2021-07-24.22-06-49.vm_image_terms_accept.271.log'.
az_command_data_logger: command args: vm image terms accept --urn {} --debug
cli.knack.cli: Event: CommandInvoker.OnPreArgumentLoad [<function register_global_subscription_argument.<locals>.add_subscription_parameter at 0x7fa46ff20f28>, <function register_global_query_examples_argument.<locals>.register_query_examples at 0x7fa46fe89158>]
cli.knack.cli: Event: CommandInvoker.OnPostArgumentLoad []
cli.knack.cli: Event: CommandInvoker.OnPostCommandTableCreate [<function register_ids_argument.<locals>.add_ids_arguments at 0x7fa46fe891e0>, <function register_cache_arguments.<locals>.add_cache_arguments at 0x7fa46fe892f0>]
cli.knack.cli: Event: CommandInvoker.OnCommandTableLoaded []
cli.knack.cli: Event: CommandInvoker.OnPreParseArgs []
cli.knack.cli: Event: CommandInvoker.OnPostParseArgs [<function OutputProducer.handle_output_argument at 0x7fa4703b97b8>, <function CLIQuery.handle_query_parameter at 0x7fa4703d18c8>,<function register_global_query_examples_argument.<locals>.handle_example_parameter at 0x7fa46fe890d0>, <function register_ids_argument.<locals>.parse_ids_arguments at 0x7fa46fe89268>]
cli.azure.cli.core.commands.client_factory: Getting management service client client_type=SubscriptionClient
cli.azure.cli.core.adal_authentication: AdalAuthentication.get_token invoked by Track 2 SDK with scopes=('https://management.core.usgovcloudapi.net//.default',)
cli.azure.cli.core._profile: Retrieving token from ADAL for resource 'https://management.core.usgovcloudapi.net/'
urllib3.connectionpool: Starting new HTTP connection (1): localhost:50342
urllib3.connectionpool: http://localhost:50342 "POST /oauth2/token HTTP/1.1" 200 2464
msrestazure.azure_active_directory: MSI: Retrieving a token from http://localhost:50342/oauth2/token, with payload {'resource': 'https://management.core.usgovcloudapi.net/'}
urllib3.connectionpool: Starting new HTTP connection (1): localhost:50342
urllib3.connectionpool: http://localhost:50342 "POST /oauth2/token HTTP/1.1" 200 2464
msrestazure.azure_active_directory: MSI: Retrieving a token from http://localhost:50342/oauth2/token, with payload {'resource': 'https://management.core.usgovcloudapi.net/'}
cli.azure.cli.core.sdk.policies: Request URL: 'https://management.usgovcloudapi.net/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations?api-version=2019-11-01'
cli.azure.cli.core.sdk.policies: Request method: 'GET'
cli.azure.cli.core.sdk.policies: Request headers:
cli.azure.cli.core.sdk.policies:     'Accept': 'application/json'
cli.azure.cli.core.sdk.policies:     'x-ms-client-request-id': '7167979e-eccb-11eb-a890-0a580af4cd9f'
cli.azure.cli.core.sdk.policies:     'CommandName': 'vm image terms accept'
cli.azure.cli.core.sdk.policies:     'ParameterSetName': '--urn --debug'
cli.azure.cli.core.sdk.policies:     'User-Agent': 'AZURECLI/2.26.0 (DEB) azsdk-python-azure-mgmt-resource/18.0.0 Python/3.6.10 (Linux-5.4.0-1055-azure-x86_64-with-debian-10.2) cloud-shell/1.0'
cli.azure.cli.core.sdk.policies:     'Authorization': '*****'
cli.azure.cli.core.sdk.policies: Request body:
cli.azure.cli.core.sdk.policies: This request has no body
urllib3.connectionpool: Starting new HTTPS connection (1): management.usgovcloudapi.net:443
urllib3.connectionpool: https://management.usgovcloudapi.net:443 "GET /subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations?api-version=2019-11-01 HTTP/1.1" 200 735
cli.azure.cli.core.sdk.policies: Response status: 200
cli.azure.cli.core.sdk.policies: Response headers:
cli.azure.cli.core.sdk.policies:     'Cache-Control': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Pragma': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Content-Type': 'application/json; charset=utf-8'
cli.azure.cli.core.sdk.policies:     'Content-Encoding': 'gzip'
cli.azure.cli.core.sdk.policies:     'Expires': '-1'
cli.azure.cli.core.sdk.policies:     'Vary': 'Accept-Encoding'
cli.azure.cli.core.sdk.policies:     'x-ms-ratelimit-remaining-subscription-reads': '14998'
cli.azure.cli.core.sdk.policies:     'x-ms-request-id': '43335063-551c-442b-8bbf-62822dc585d3'
cli.azure.cli.core.sdk.policies:     'x-ms-correlation-request-id': '43335063-551c-442b-8bbf-62822dc585d3'
cli.azure.cli.core.sdk.policies:     'x-ms-routing-request-id': 'USDODEAST:20210724T220650Z:43335063-551c-442b-8bbf-62822dc585d3'
cli.azure.cli.core.sdk.policies:     'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
cli.azure.cli.core.sdk.policies:     'X-Content-Type-Options': 'nosniff'
cli.azure.cli.core.sdk.policies:     'Date': 'Sat, 24 Jul 2021 22:06:50 GMT'
cli.azure.cli.core.sdk.policies:     'Content-Length': '735'
cli.azure.cli.core.sdk.policies: Response content:
cli.azure.cli.core.sdk.policies: {"value":[{"id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/global","name":"global","displayName":"Global","regionalDisplayName":"Global","metadata":{"regionType":"Logical","regionCategory":"Other"}},{"id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usdodcentral","name":"usdodcentral","displayName":"USDoD Central","regionalDisplayName":"(US) USDoD Central","metadata":{"regionType":"Physical","regionCategory":"Other","geographyGroup":"US","longitude":"-93.6091","latitude":"41.6005","physicalLocation":"Iowa","pairedRegion":[{"name":"usdodeast","id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usdodeast"}]}},{"id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usdodeast","name":"usdodeast","displayName":"USDoD East","regionalDisplayName":"(US) USDoD East","metadata":{"regionType":"Physical","regionCategory":"Other","geographyGroup":"US","longitude":"-78.3875","latitude":"36.6676","physicalLocation":"Virginia","pairedRegion":[{"name":"usdodcentral","id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usdodcentral"}]}},{"id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usgovarizona","name":"usgovarizona","displayName":"USGov Arizona","regionalDisplayName":"(US) USGov Arizona","metadata":{"regionType":"Physical","regionCategory":"Other","geographyGroup":"US","longitude":"-112.0740","latitude":"33.4484","physicalLocation":"Arizona","pairedRegion":[{"name":"usgovtexas","id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usgovtexas"}]}},{"id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usgoviowa","name":"usgoviowa","displayName":"USGov Iowa","regionalDisplayName":"(US) USGov Iowa","metadata":{"regionType":"Physical","regionCategory":"Other","geographyGroup":"US","longitude":"-93.6208","latitude":"41.5908","physicalLocation":"Iowa","pairedRegion":[{"name":"usgovvirginia","id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usgovvirginia"}]}},{"id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usgovtexas","name":"usgovtexas","displayName":"USGov Texas","regionalDisplayName":"(US) USGov Texas","metadata":{"regionType":"Physical","regionCategory":"Other","geographyGroup":"US","longitude":"-98.4936","latitude":"29.4241","physicalLocation":"Texas","pairedRegion":[{"name":"usgovarizona","id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usgovarizona"}]}},{"id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usgovvirginia","name":"usgovvirginia","displayName":"USGov Virginia","regionalDisplayName":"(US) USGov Virginia","metadata":{"regionType":"Physical","regionCategory":"Other","geographyGroup":"US","longitude":"-79.8164","latitude":"37.3719","physicalLocation":"Virginia","pairedRegion":[{"name":"usgovtexas","id":"/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/locations/usgovtexas"}]}}]}
cli.azure.cli.core.commands.client_factory: Getting management service client client_type=ComputeManagementClient
cli.azure.cli.core.adal_authentication: AdalAuthentication.get_token invoked by Track 2 SDK with scopes=('https://management.core.usgovcloudapi.net//.default',)
cli.azure.cli.core._profile: Retrieving token from ADAL for resource 'https://management.core.usgovcloudapi.net/'
urllib3.connectionpool: Starting new HTTP connection (1): localhost:50342
urllib3.connectionpool: http://localhost:50342 "POST /oauth2/token HTTP/1.1" 200 2464
msrestazure.azure_active_directory: MSI: Retrieving a token from http://localhost:50342/oauth2/token, with payload {'resource': 'https://management.core.usgovcloudapi.net/'}
urllib3.connectionpool: Starting new HTTP connection (1): localhost:50342
urllib3.connectionpool: http://localhost:50342 "POST /oauth2/token HTTP/1.1" 200 2464
msrestazure.azure_active_directory: MSI: Retrieving a token from http://localhost:50342/oauth2/token, with payload {'resource': 'https://management.core.usgovcloudapi.net/'}
cli.azure.cli.core.sdk.policies: Request URL: 'https://management.usgovcloudapi.net/subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/providers/Microsoft.Compute/locations/global/publishers/cisco/artifacttypes/vmimage/offers/cisco-csr-1000v/skus/16_10-payg-sec/versions/16.10.120190108?api-version=2021-03-01'
cli.azure.cli.core.sdk.policies: Request method: 'GET'
cli.azure.cli.core.sdk.policies: Request headers:
cli.azure.cli.core.sdk.policies:     'Accept': 'application/json'
cli.azure.cli.core.sdk.policies:     'x-ms-client-request-id': '7167979e-eccb-11eb-a890-0a580af4cd9f'
cli.azure.cli.core.sdk.policies:     'CommandName': 'vm image terms accept'
cli.azure.cli.core.sdk.policies:     'ParameterSetName': '--urn --debug'
cli.azure.cli.core.sdk.policies:     'User-Agent': 'AZURECLI/2.26.0 (DEB) azsdk-python-azure-mgmt-compute/21.0.0 Python/3.6.10 (Linux-5.4.0-1055-azure-x86_64-with-debian-10.2) cloud-shell/1.0'
cli.azure.cli.core.sdk.policies:     'Authorization': '*****'
cli.azure.cli.core.sdk.policies: Request body:
cli.azure.cli.core.sdk.policies: This request has no body
urllib3.connectionpool: Starting new HTTPS connection (1): management.usgovcloudapi.net:443
urllib3.connectionpool: https://management.usgovcloudapi.net:443 "GET /subscriptions/827ed6d0-6545-432d-ac5e-75c4078da112/providers/Microsoft.Compute/locations/global/publishers/cisco/artifacttypes/vmimage/offers/cisco-csr-1000v/skus/16_10-payg-sec/versions/16.10.120190108?api-version=2021-03-01 HTTP/1.1" 400 564
cli.azure.cli.core.sdk.policies: Response status: 400
cli.azure.cli.core.sdk.policies: Response headers:
cli.azure.cli.core.sdk.policies:     'Cache-Control': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Pragma': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Content-Type': 'application/json; charset=utf-8'
cli.azure.cli.core.sdk.policies:     'Expires': '-1'
cli.azure.cli.core.sdk.policies:     'x-ms-failure-cause': 'gateway'
cli.azure.cli.core.sdk.policies:     'x-ms-request-id': '05354e05-8ce1-4d21-af95-f004dd27b619'
cli.azure.cli.core.sdk.policies:     'x-ms-correlation-request-id': '05354e05-8ce1-4d21-af95-f004dd27b619'
cli.azure.cli.core.sdk.policies:     'x-ms-routing-request-id': 'USDODEAST:20210724T220650Z:05354e05-8ce1-4d21-af95-f004dd27b619'
cli.azure.cli.core.sdk.policies:     'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
cli.azure.cli.core.sdk.policies:     'X-Content-Type-Options': 'nosniff'
cli.azure.cli.core.sdk.policies:     'Date': 'Sat, 24 Jul 2021 22:06:49 GMT'
cli.azure.cli.core.sdk.policies:     'Content-Length': '564'
cli.azure.cli.core.sdk.policies: Response content:
cli.azure.cli.core.sdk.policies: {"error":{"code":"NoRegisteredProviderFound","message":"No registered resource provider found for location 'global' and API version '2021-03-01' for type 'locations/publishers'. The supported api-versions are '2015-05-01-preview, 2015-06-15, 2016-03-30, 2016-04-30-preview, 2016-08-30, 2017-03-30, 2017-12-01, 2018-04-01, 2018-06-01, 2018-10-01, 2019-03-01, 2019-07-01, 2019-12-01, 2020-06-01, 2020-09-30, 2020-12-01, 2021-03-01, 2021-04-01, 2021-07-01'. The supported locations are 'usgoviowa, usgovvirginia, usdodcentral, usdodeast, usgovtexas, usgovarizona'."}}
cli.azure.cli.core.util: azure.cli.core.util.handle_exception is called with an exception:
cli.azure.cli.core.util: Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
    raise ex
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 691, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/vm/custom.py", line 1949, in accept_terms
    return _accept_cancel_terms(cmd, urn, publisher, offer, plan, True)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/vm/custom.py", line 1925, in _accept_cancel_terms
    publisher, offer, plan = _terms_prepare(cmd, urn, publisher, offer, plan)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/vm/custom.py", line 1912, in _terms_prepare
    image = show_vm_image(cmd, urn)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/vm/custom.py", line 1862, in show_vm_image
    return client.virtual_machine_images.get(location, publisher, offer, sku, version)
  File "/opt/az/lib/python3.6/site-packages/azure/mgmt/compute/v2021_03_01/operations/_virtual_machine_images_operations.py", line 108, in get
    raise HttpResponseError(response=response, error_format=ARMErrorFormat)
azure.core.exceptions.HttpResponseError: (NoRegisteredProviderFound) No registered resource provider found for location 'global' and API version '2021-03-01' for type 'locations/publishers'. The supported api-versions are '2015-05-01-preview, 2015-06-15, 2016-03-30, 2016-04-30-preview, 2016-08-30, 2017-03-30, 2017-12-01, 2018-04-01, 2018-06-01, 2018-10-01, 2019-03-01, 2019-07-01, 2019-12-01, 2020-06-01, 2020-09-30, 2020-12-01, 2021-03-01, 2021-04-01, 2021-07-01'. The supported locations are 'usgoviowa, usgovvirginia, usdodcentral, usdodeast, usgovtexas, usgovarizona'.

cli.azure.cli.core.azclierror: (NoRegisteredProviderFound) No registered resource provider found for location 'global' and API version '2021-03-01' for type 'locations/publishers'. The supported api-versions are '2015-05-01-preview, 2015-06-15, 2016-03-30, 2016-04-30-preview, 2016-08-30, 2017-03-30, 2017-12-01, 2018-04-01, 2018-06-01, 2018-10-01, 2019-03-01, 2019-07-01, 2019-12-01, 2020-06-01, 2020-09-30, 2020-12-01, 2021-03-01, 2021-04-01, 2021-07-01'. The supported locations are 'usgoviowa, usgovvirginia, usdodcentral, usdodeast, usgovtexas, usgovarizona'.
az_command_data_logger: (NoRegisteredProviderFound) No registered resource provider found for location 'global' and API version '2021-03-01' for type 'locations/publishers'. The supported api-versions are '2015-05-01-preview, 2015-06-15, 2016-03-30, 2016-04-30-preview, 2016-08-30, 2017-03-30, 2017-12-01, 2018-04-01, 2018-06-01, 2018-10-01, 2019-03-01, 2019-07-01, 2019-12-01, 2020-06-01, 2020-09-30, 2020-12-01, 2021-03-01, 2021-04-01, 2021-07-01'. The supported locations are 'usgoviowa, usgovvirginia, usdodcentral, usdodeast, usgovtexas, usgovarizona'.
cli.knack.cli: Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x7fa46fefc268>]
az_command_data_logger: exit code: 1
cli.__main__: Command ran in 1.735 seconds (init: 0.109, invoke: 1.626)
telemetry.save: Save telemetry record of length 3594 in cache
telemetry.check: Returns Positive.
telemetry.main: Begin creating telemetry upload process.
telemetry.process: Creating upload process: "/usr/bin/../../opt/az/bin/python3 /opt/az/lib/python3.6/site-packages/azure/cli/telemetry/__init__.py /home/adam/.azure"
telemetry.process: Return from creating process
telemetry.main: Finish creating telemetry upload process.

We can start an email thread internally if you'd prefer @zhoxing-ms

@adamdost-msft Yes, you can delete the debug log information here, and we will exchange these information by internally email later. My email address is<EMAIL_ADDRESS>thanks~

(NoRegisteredProviderFound) No registered resource provider found for location 'global' and API version '2021-03-01' for type 'locations/publishers'. The supported api-versions are '2015-05-01-preview, 2015-06-15, 2016-03-30, 2016-04-30-preview, 2016-08-30, 2017-03-30, 2017-12-01, 2018-04-01, 2018-06-01, 2018-10-01, 2019-03-01, 2019-07-01, 2019-12-01, 2020-06-01, 2020-09-30, 2020-12-01, 2021-03-01, 2021-04-01, 2021-07-01'. The supported locations are 'usgoviowa, usgovvirginia, usdodcentral, usdodeast, usgovtexas, usgovarizona'

Because this error is returned by the REST service, it is a service issue. Therefore, Therefore, it needs the service team to investigate the cause of this error
'x-ms-correlation-request-id': '05354e05-8ce1-4d21-af95-f004dd27b619'

@olayemio Could you please look into this issue?

@amjads1 can you look into this as it is a Marketplace image issue

Looking into the issue.

@amjads1 any update for this issue?

@yonzhan I think you are already part of the on-going email thread on this topic for latest updates.
@avlind We have some potential leads where the issue could be but trying to validate with the CLI team and update back as soon as I have more information.

@avlind Could you use az upgrade --yes to upgrade the CLI to latest version (2.28.0) and try again? If you still can reproduce this issue, please add parameter --debug to the original command and send me the printed debug log.
My email address is<EMAIL_ADDRESS>thanks

Followed up internally

Confirming, that in my test using 2.28.0 CLI from Azure Government Cloud Shell, I was able to run the previously impacted CLI command to accept terms based on URN.

@avlind OK, so may I ask can this issue be closed?


improve/make new figures for revisions

@teixeirak,
I like Ben's suggestion about the Whittaker plot.
Looking at sites with some data submited to IPCC, quite a few of them are missing map or mat (or both). (in image below the numbers under "TRUE" are the number of sites with missing value

FYI, the 130 missing mat are distributed  in these different types of missing values:
NA  NAC  NI
 20 105   5

We can probably acquire values for some.
For sites that have both info, this is what the Whittaker plot would look like:

This looks nice! Is the code for the bigger background image easy to implement? The advantage of that is that it gives some sense of how common those climates are. This would do better at getting at the reviewer's desire for a better analysis of how representative these  data are.

shouldn't be too hard. I'll work on that tomorrow.

@ValentineHerr , I knew this was super familiar... you've already made it! :-)
https://github.com/forc-db/ForC/blob/master/figures/Climate_of_forC_sites.png

For this paper, let's make the following changes:

try to make the symbols small enough that its possible to see the underlying climate space
same symbols for all site regardless of whether the climate data came from ForC or WorldClim (which we can use to fill the missing climate values)
more emphatic symbols for data sent to EFDB
the colors on Ben's version are nice, if easy to change.

That sounds good. I'll work on that asap. Yesterday I was trying to see if I could color Ben's version by different scales of colors based on biome but sounds like it not worth it. Plus it was not really working. This is what I had left it at:

Oh, that's a super cool idea! But I agree its best to drop it since its not working. If you want to do color coding, I'd use the FAO ecozones and drop the Whittaker biome lines.

@ValentineHerr , and as in the map, we should limit to records relevant to EFBD (not all of ForC).

How is this looking? I made tiny dots for ForC and triangles for EFDB sites.

I love it!

I really don't see anything I'd change.

I pushed the figure on the ForC repo (see commit above)

Thanks! Does this use the same data set as Ben's figure (WorldClim 2, Fick & Hijmans, 2017)?

Actually, could you please change the legend as follows:
(dot) - ForC site with EFDB-relevant data
(triangle) - site with ~some~ data submitted to EFDB
I don't know if a dot will show up well enough. You might just write out "(dot)"

Also, can you please confirm that this is limited to terrestrial area?

Also, please confirm spatial resolution of the data (0.5° in Ben's figure).

Thanks! Does this use the same data set as Ben's figure (WorldClim 2, Fick & Hijmans, 2017)?
Also, can you please confirm that this is limited to terrestrial area?

It uses CRU data. I have in my notes: "summary of CRU data for 1990-2014 given by Ben Bond-Lamberty through GitHub on 8/23/2017".
I am assuming he gave us terrestrial data back then...

Also, please confirm spatial resolution of the data (0.5° in Ben's figure).

It is 0.5 resolution


daemon: Deprecate SockOps

The feature will be removed in v1.14. The relevant docs change PR - https://github.com/cilium/cilium/pull/23554.

I switched the release note label to minor.


Text label in Point layer only supports ascii.

By default, only characters in the Ascii code range 32-128 are included in Deck.gl's TextLayer. Can I use TextLayer's characterSet prop in Kepler.gl?

Unfortunately no at the moment. What language are you using?

@javidhsueh is this something we can add to the text layer support in kepler.gl? We could do a scan on all the strings and get a characterSet domain to set on the textLayer.

I'm using CJK. Thanks.

Closing it for now, please test it and let us know if there is anything else


The cell status color elements move to under cell area

The cell status color elements(<div class='out_prompt_bg prompt'>) move  to under cell area, and overlap to next cell.

Environment:

Jupyter Notebook 5.2.1
Safari 10

In the current environment, this issue does not occur.
Environment:

Jupyter Notebook 5.7.0
Safari 12.0


Improve Helm chart to not fail on simple install

When I install Helm chart, it fails to run the app because of PersistentVolume not specifying local directory. Disabling persistence still generates PVC (sic!)
We need to improve the chart to have a logic:

when no values specified upon chart install, it should use an EmptyDir and just start
when "hostPath" specified without storageClass, it would run fine just like today
when specific storageClass is specified, it is respected
it should allow changing the storageClass via chart reconfiguration

For the context, #206 were not fully good change, I experience different PVC-related failures after it.
Also https://github.com/komodorio/helm-charts/issues/146 is the context of realistic example.

I'd be interested in taking a shot at this one.


Fix a minor error in TH3 (wrong total number of bins)

I believe this is a typo coming from TH2.

Yes, that's right. Thank you!


Move C# Markup Extensions from Forms to Toolkit

Description of Change
Move the full C# Markup functionality from the Xamarin Forms CSharpForMarkup Part 2 PR into the XCT

With full git history from Forms repo
Without experimental feature flags
With working example app, ported from Introducing C# Markup for Xamarin.Forms
100% Unit test coverage; all tests green.Two tests signaling Forms issue 12683 will fail after that issue is fixed; how to fix the tests then is included in TODO comments
As a separate NuGet package Xamarin.CommunityToolkit.Markup (with corresponding namespace), targeting Forms 5; no dependencies on other XCT package(s)

This XCT PR depends on Forms PR 12623; until this is available in a NuGet feed, this XCT PR downloads and unzips the NuGet packages of the Forms PR on the restore build target
Bugs Fixed

Fixes https://github.com/xamarin/XamarinCommunityToolkit/issues/499

API Changes
Add API's documented in PR 29.
PR Checklist

[x] Has tests (if omitted, state reason in description)
[x] Has samples (if omitted, state reason in description)
[x] Rebased on top of main at time of PR
[x] Changes adhere to coding standard

[X] Updated documentation in PR 29

@jfversluis can you help me get the Xamarin.CommunityToolkit.Markup.UnitTests.csproj results visible?
the unit tests run in CI e.g. see log but they are not listed in the test overview and also not present in the test results tab in Azure Devops

@jfversluis is it possible to enable code coverage in CI?
Markup is at 100%

Looks like I can see them just fine?

Note that for the screen in AzDO it filters automatically for only failed tests. If you disable that, they show up.
I'll have a look at the coverage.

@jfversluis

Looks like I can see them just fine?
Nope, those are only the Xamarin.CommunityToolkit.UnitTests.csproj tests.
The tests in Xamarin.CommunityToolkit.Markup.UnitTests.csproj are not included; try filtering on Passed and "Markup".

Once they are included you should see an additional 255 tests

You mean these?

You mean these?

@jfversluis yes! User error - I saw the top tests listed like this:

So I assumed my tests would also include the full namespace and I filtered on "Markup"
But for some reason my tests are shown like this:

(probably some NUnit default - I saw you use XUnit)
So that's why I never saw a result. 1055 is the correct total nr of tests

Yeah I agree, would be great if we can align that and get a bit better naming/categorising, etc. but something for later :)

If you pull in the change from #524 coverage is enabled too

If you pull in the change from #524 coverage is enabled too

@jfversluis merged; works. Thanks! Results:

Not counting tests, C# Markup is just 13% of total XCT blocks. XCT is bigger than I thought 👍

Can we switch this one to pre4 that should have all the bits? Then it's good to go afaic :)

Can we switch this one to pre4 that should have all the bits? Then it's good to go afaic :)

@jfversluis Done. Markup package version 1.0.0-pre4. All tests green; sample updated and tested; all works on Android, UWP and iOS.
Minor visual issue in the sample on iOS : the like button does not display - possibly a forms 5 issue; it uses FontImageSource.GlyphProperty  with characters "\u2764" and "\u2661". Will look into that later but for now this can be released, assuming that the Markup package and build settings for public release are OK (I copied those from the main XCT package but can't verify them for myself)

The version of the package will be overriden at the time of release, but we'll figure that out also in light of #529