Dashrews/ROX-15331 batch call to delete by query

Description
SQL only allows a parameter list. up to 65535 items due to constraints within SQL.  In the instance with this ticket there were a large number of process indicators deleted and when we sent that large list of ideas to the delete by query it failed.  In order to resolve this quickly I did 2 things:

batch the calls to delete by query when process indicators are removed.
Updated the searcher parser to truncate arguments when there are 65535 arguments.

We may want a follow up ticket to update the search framework to handle and batch these scenarios within the framework itself.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
~- [ ] Evaluated and added CHANGELOG entry if required~
~- [ ] Determined and documented upgrade steps~
~- [ ] Documented user facing changes (create PR based on [openshift/openshift-docs]~(https://github.com/openshift/openshift-docs) and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Added a test to test the batching.

Thanks for the fix.

Updated the searcher parser to truncate arguments when there are 65535 arguments.

It sound like a good defense measure, but usually it's rather dangerous to have more than several thousands of parameters due to memory pressure (the exact value depends on the amount of available memory of course, the worst case result is OOM of a db backend). Would it make sense to do a warning if the number is over a certain threshold?


Vertices containing arrays of objects - part 2

Unfortunately, (closed) issue #26 is still seems to be a problem, sorry.
Exceptions are still thrown when you try to save a vertex where a property is an array of objects. This seems fine if it's an array of simple types like integers or strings. But if you write your own class and try to store an array (or collection) of those objects it will fail with an exception.
For repo steps, see issue #26, the code posted there will still fail.
Thanks.

Out of interest, I noticed that this is a problem even when the property is not an array or list.  Consider the following:
[Label("person")]
public class PersonVertex : VertexBase
{
    public int[] Ages { get; set; }
    public string Name { get; set; }
    public PersonLink Link { get; set; }
}

public class PersonLink
{
    public int Reference { get; set; }
    public string Name { get; set; }
}

So ... in this case, the Link property is just a single PersonLink object.  If we now store a PersonVertex in the graph, like this:
var personV = new PersonVertex
{
    Ages = new[] { 4, 6, 23 },
    Id = "person-12345",
    Label = "some-label",
    Name = "my name",
    Link = new PersonLink { Name = "ExternalLink", Reference = 1234 }
};
var test = g.AddV(personV).As("person");
var resp = await graphClient.QueryAsync(test);

...this is interesting, because the vertex will be stored in the graph, but the code will also throw an exception:
Error converting value "{"Reference":1234,"Name":"ExternalLink"}" to type 'GremlinSample.Schema.PersonLink'. Path 'Link'.
...and there is an inner exception:
Could not cast or convert from System.String to GremlinSample.Schema.PersonLink.
Despite the exception, if you look in the database, the vertex will be there.  So I'm guessing there is a serialization issue when you try to store properties other than the built in types.  I though this information might help.  Thanks!

Hmm. I'm not exactly sure how this should be solved. My team and I are just handling the serialization/de-serialization of complex properties on our own before submitting the vertices we're saving to the graph, so this isn't a feature I'll be able to invest time into at the moment.
My best guess is that you'll need to update the Gremlin.Net.CosmosDb.Serializaton.VertexBaseJsonConverter (and probably the EdgeBaseJsonConverter) to correctly convert serialized string property values to its object/array de-serialized equivalent if/when the property it's saturating is not a string or string-like property (date/time, url, GUID, etc.). I would do this work within the ConvertPropertiesObject method where you have access to the object contract.
Sorry I can't help more than that at the moment. It would be really cool to get this fully working if you can spare any time!

Thanks.  I totally understand.  You have been very helpful already.  I would love to spend more time on this, but I have limited time to invest as well.  Let me see what I can do.  Our dev team is currently trying to decide if we're happy to use CosmosDB in production, if we go ahead then I will probably be able to put more effort into this.  It would be a very cool feature.


Profile Page

Changes:

Locations does not go anywhere (https://garage.asrg.io/account/locations/)
Need to add "My Projects" to the menu list.
What is the difference between Locations and Saved Locations
We should probably add a city field as well.
When you add a phone number, it should check the format.
When you add a phone number, it should confirm by sending an SMS.
When you change the email it should ask to confirm by sending an email.
When you update your profile, it should go back to the My Profile screen with the profile updated message.
The color of the menu buttons and the footer are the same. Need to change this to different colors.

Locations do not go anywhere (https://garage.asrg.io/account/locations/) Removed
Need to add "My Projects" to the menu list. Done
What is the difference between Locations and Saved Locations A user can save their favorite locations so they can access them from "saved locations" easily
We should probably add a city field as well. Done
When you add a phone number, it should check the format. Done
When you add a phone number, it should confirm by sending an SMS.
When you change the email it should ask to confirm by sending an email. Done
When you update your profile, it should go back to the My Profile screen with the profile updated message. Done
The color of the menu buttons and the footer are the same. Need to change this to different colors. Done

SMS thing is a long task so will add that as a new card in the todo list

The phone number format needs to take into consideration all country codes. Maybe a drop down for the country code first and then it will check the format of the expected phone number.
I think the SMS is still not working. Which third party apps might work here?
Also, at the bottom the last menu item of the profile page needs some more space between the footer and the last menu item.

Regarding the SMS, I am thinking of this plugin https://plugins.miniorange.com/wordpress-otp-verification
I have requested a demo so we can test it before purchasing. Also, we need an SMS gateway to do the OTP verification. These are the gateways this plugin accepts please have a look. https://plugins.miniorange.com/supported-sms-email-gateways
I will fix the account menu and the margin issue is fixed.

SMS is on hold for now.  Prabath to check with Jet Engine regarding the world wide telephone numbers


Getting test script to run

Hi,
I've been using sunode for over 2 months now. It's a great project and I've really benefited from the speed.
I'm interested in using sunode with pyMC4. I ran the test script in the readMe and recieved a strange error that I'm not sure how to fix.
Traceback (most recent call last):
    idata = pm.sample(tune=1000, draws=1000, chains=6, cores=6)
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/pymc/sampling.py", line 524, in sample
    step = assign_step_methods(model, step, methods=pm.STEP_METHODS, step_kwargs=kwargs)
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/pymc/sampling.py", line 215, in assign_step_methods
    tg.grad(model_logp, var)
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 635, in grad
    rval = _populate_grad_dict(var_to_app_to_idx, grad_dict, wrt, cost_name)
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1440, in _populate_grad_dict
    rval = [access_grad_cache(elem) for elem in wrt]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1440, in <listcomp>
    rval = [access_grad_cache(elem) for elem in wrt]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1393, in access_grad_cache
    term = access_term_cache(node)[idx]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1064, in access_term_cache
    output_grads = [access_grad_cache(var) for var in node.outputs]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1064, in <listcomp>
    output_grads = [access_grad_cache(var) for var in node.outputs]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1393, in access_grad_cache
    term = access_term_cache(node)[idx]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1064, in access_term_cache
    output_grads = [access_grad_cache(var) for var in node.outputs]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1064, in <listcomp>
    output_grads = [access_grad_cache(var) for var in node.outputs]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1393, in access_grad_cache
    term = access_term_cache(node)[idx]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1064, in access_term_cache
    output_grads = [access_grad_cache(var) for var in node.outputs]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1064, in <listcomp>
    output_grads = [access_grad_cache(var) for var in node.outputs]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1393, in access_grad_cache
    term = access_term_cache(node)[idx]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1064, in access_term_cache
    output_grads = [access_grad_cache(var) for var in node.outputs]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1064, in <listcomp>
    output_grads = [access_grad_cache(var) for var in node.outputs]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1393, in access_grad_cache
    term = access_term_cache(node)[idx]
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/gradient.py", line 1219, in access_term_cache
    input_grads = node.op.L_op(inputs, node.outputs, new_output_grads)
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/graph/op.py", line 371, in L_op
    return self.grad(inputs, output_grads)
  File "/home/aarcher/research/pdo_pathway_pymc/sunode/sunode/wrappers/as_aesara.py", line 261, in grad
    lamda, gradient = backward(y0, params, params_fixed, g)
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/graph/op.py", line 296, in __call__
    node = self.make_node(*inputs, **kwargs)
  File "/home/aarcher/anaconda3/envs/pymc_env/lib/python3.10/site-packages/aesara/graph/op.py", line 240, in make_node
    raise TypeError(
TypeError: Invalid input types for Op SolveODEAdjointBackward{_solver_id=140214287550256, _t0=1900, _tvals_id=140214298068912}:
Input 3/4: Expected TensorType(float64, (None,)), got TensorType(float64, (1,))

Your help would be much appreciated. Thank you in advance!

Can you share an example that produces this error? That would make it easier to debug.

Oh, sorry you said it's the example from the readme, my mistake...

Thank you for the report, I can reproduce this issue.
I think this was introduced by a small change in the behavior of the Op.make_node function in aesara, I'll have to experiment a bit more for a fix though.

Thank you for your quick response!

Should be fixed if https://github.com/aesara-devs/aesara/pull/1010 gets merged

The PR in aesara is merged now, so if you use the development version this should work now. If you have any more trouble with this (or installing the dev version) just ping me again.
I'll leave the issue open for now until the next release of aesara.

Great. Thanks!


Not displayed methods names

Methods folded correct, names of methods not displayed:
30 class Zend_Locale
31 {
...

1051 +--  8 lines folded
1059 +--  7 lines folded
1066 +--  7 lines folded
1073 +--  7 lines folded
1080 +--  7 lines folded
1087 +--  7 lines folded
1094 +--  7 lines folded
1101 +-- 18 lines folded
1119 +-- 10 lines folded
1129 +-- 10 lines folded
1139 +-- 11 lines folded
1150 +-- 25 lines folded
1175 +-- 45 lines folded
1220 +-- 59 lines folded
1279 +-- 65 lines folded
1344 +-- 34 lines folded
1378 +-- 11 lines folded
1389 +-- 15 lines folded
1404 +-- 33 lines folded
1437 +-- 15 lines folded
1452 +-- 22 lines folded
1474 +-- 13 lines folded
1487 +-- 13 lines folded
1500 +-- 13 lines folded
1513 +-- 14 lines folded
1527 +-- 21 lines folded
1548 +-- 14 lines folded
1562 +-- 14 lines folded
1576 +-- 14 lines folded
1590 +-- 15 lines folded
1605 +-- 23 lines folded
1628 +-- 44 lines folded
1672 +-- 58 lines folded
1730 +-- 40 lines folded
1770 +-- 16 lines folded
1786 +-- 17 lines folded
1803 +-- 11 lines folded
1814 +-- 12 lines folded
1826 +-- 11 lines folded
1837 +-- 11 lines folded
1848 +-- 12 lines folded
1860 +-- 12 lines folded
1872 +-- 76 lines folded
1948 +-- 31 lines folded
}

What is a sample of the non-folded text?

https://github.com/zendframework/zf1/blob/master/library/Zend/Locale.php


yt-dlp interface json error cause?

it seems to happen randomly out of nowhere, i wonder what causes it to happen?

You don't give any details, so I have no idea what you're referring to. JSON errors can happen in different situations (for example when getting data for a newly added URL, or when checking GithGub for a new version). Also, the text of the error is critical to understanding why it happens. Please post a screenshot or something, and I might be able to tell you why it happens.

You don't give any details, so I have no idea what you're referring to. JSON errors can happen in different situations (for example when getting data for a newly added URL, or when checking GitHub for a new version). Also, the text of the error is critical to understanding why it happens. Please post a screenshot, and I might be able to tell you why it happens.

hello again, sorry about not giving more info. i forgot to take a screenshot the last time it happened.

That happens because the contents of the settings file is missing when the program tries to load it. In other words, the file ytdlp-interface.json has a size of zero when you start the program.
I'm not sure how that could happen. Maybe some external process does it, or maybe the program fails to write the file when exiting, truncating it instead. In the next version, the program will display an error if it fails to write the settings file. It doesn't currently, because I never expected this would happen (I guess I should have known better).


Need to figure out how we upgrade existing accounts that don't have 2fa but are logging into an organisation that has it mandated.

We can just force the 2f setup screen on login if 1 or more orgs have a field force_2fa

Frontend is ready on the flag force_2fa via https://github.com/Flagsmith/flagsmith/issues/411.
Basically, the backend just needs to persist a field called "force_2fa" and return it on the organisations endpoint.
The frontend will send up this bool in the put to the organisation

If a user does not have 2fa and has an organisation with this as true they will see this post login. This will also be the case if the user attempts to disable 2fa.

This was marked as done on the roadmap, but from what I can see the feature flag hasn't been enabled in production?

Just to double-check if this is enabled, user should not be allowed to log in from the API as well? And not the UI? @dabeeeenster  @matthewelwell

Questions:

Scenario 1: org admin has enabled force 2fa but some of the users have not enabled 2fa. What should happen in that case?
Option 1. They should not be allowed to log in
problems: How are they going to enable 2fa in that case?

Solution: only allow org admin to enable 2fa if all the user have 2fa configured in that organisation.

I think we can not implement a general BE enforcement for 2FA, until we provide an alternative for enterprise customers to access our API. Currently, I think the only way we provide is by using an API Key related with a user right? So we should either provide exceptions (Which will be either a vulnerability or will complicate things), or an alternative API Key though the roles as I understand is planned, right?


Clone message

Hi,
I'm writing a bot to 'save' messages in my private chat.
I want a code that clone the replyed message and send it to my private chat
Is some funztion able to do it without check video, photo, document, animations, gif and so on ?

You should be able to use forwardMessage to redirect any type of message. Have a look at this: https://core.telegram.org/bots/api#forwardmessage

@Shyghar If you literally want to send a new message, take a look at the sendBack method here, as an example for you to implement yourself:
https://github.com/php-telegram-bot/core/blob/956371f2e83fa86c05165ea617f1758df3ccb6bd/src/Commands/AdminCommands/SendtochannelCommand.php#L285-L313


[dLSR failures] Default MRTK Cursors should not write to depth map. This impacts hologram stabilization

Describe the bug
The default cursor prefab writes to the depth map.  This causes interference with Hologram stabilization, especially when using the Eye/GGV Cursor.   That is, when using the GGV cursor, stabilization is always incorrect, since what your looking at is being stabilized using the cursor's depth.
Note, when an app is "sharing depth" with unity, Holograms will be stabilized with the app's depth map.
To reproduce
Steps to reproduce the behavior:

Turn on depth sharing
Setup HoloLens 2 app to use GGV cursor only
Remove colliders from your other meshes (not needed, but makes it easier to see problem when cursor doesn't collide with meshes)
Play app on hololens 2.
Ensure GGV cursor is visible
See stabilization of mesh objects, around GGV cursor, is incorrect.

Expected behavior
Hologram stabilization shouldn't be impacted but the cursor
Your Setup (please complete the following information)

Unity Version (2018 and 2019)
MRTK Version: v2.0 - v2.1

Target Platform (please complete the following information)

HoloLens (auto planar LSR will also be incorrect)
HoloLens 2

@thalbern, can you please assign this bug to someone on your team?  This is impacting stabilization of holograms in our partner applications

Remove colliders from your other meshes (not needed, but makes it easier to see problem when cursor doesn't collide with meshes)

Is this a common scenario? I feel like in the majority of cases, the cursor is going to raycast against and align with content in the app.

Remove colliders from your other meshes (not needed, but makes it easier to see problem when cursor doesn't collide with meshes)

Is this a common scenario? I feel like in the majority of cases, the cursor is going to raycast against and align with content in the app.

Removing coliders not needed, there is still error.   But regardless this is impacting partners who render large meshes without colliders (I can follow-up offline with details)

@Cameron-Micka Is this something we can change as a setting on the MRTKStandard shader?

On the cursor materials we can disable depth write by changing the render mode to "custom" and then turning off "depth write".

While this might introduce some rendering artifacts on opaque materials, it might look fine as well since the geometry is pretty simple and the material is unlit. Something to try and see how it looks!

Removing from 2.5 - looks like a simple enough change, but getting appropriate coverage of it might be hard.

Closing based on conversation with @AMollis where he expressed that the team has improved dLSR since this bug was opened and stabilization is much better now.


Empty space before Slack messages

I'm having empty spaces before most of the messages. I don't have the same problem with other Slack plugins. Is anyone else having the same issues?

I don't see that with 1.8.1 nor the 2.0-snapshot

I've upgraded to 2.0 and it's still present. It looks like it prints ---------------- in that space.
This is the output when I copy / paste that part:

Jenkins BOT [6:58 PM]
----------------
console-test - #56 Started by user Armagan Amcalar (Open)

[6:59]
----------------
console-test - #56 Back to normal after 5 days 6 hr (Open)
No Tests found.

[6:59]
----------------
No Changes.

It displays JUnit style tests which is XML collected by Jenkins.

I've never seen this... Feel free to comment or reopen a new issue if its still a problem


Installs correctly, but won't run

The package seems to have installed correctly, but doesn't appear to be running.
I'm seeing the following in the console when the package is enabled:
Uncaught (in promise) Error: Missing filePath or not a Typescript file(…)   typescriptBuffer.js:75

Same thing here. Doesn't compile nor rewrites tsconfig file.

@benvmatheson the error means that either you haven't saved your file yet or the grammar is not set to Typescript. In both of those cases, the plugin will no do anything.
@Xakaloz if you mean the behavior of compileOnSave, then it's different from the previous version. Unless set to true in tsconfig.json, it will not emit anything. It also doesn't rewrite the tsconfig file anymore because it supports all the options Typescript does so no need to update the files array, for example.

It is not working for me either now, I recently updated to the Linter 2.0, I'm wondering if this is causing issues?

@guncha Yes, i mean the "rewriteTsconfig": true option.
I have to manually add new files to files array in order to have the compilation working.
If I just use the filesGlob property, I have "Duplicate identifier" errors with Linter 2.0.
Here you have my tsconfig.json configuration, maybe I am doing something wrong or misunderstanding some subtility:
{
  "compileOnSave": false,
  "compilerOptions": {
    "noImplicitAny": true,
    "removeComments": true,
    "preserveConstEnums": true,
    "target": "es5",
    "outFile": "js/app.js",
    "sourceMap": true,
    "module": "system",
    "allowJs": true
  },
  "filesGlob": [
    "**/*.ts",
    "!node_modules/**"
  ],
  "files": [
    "ts/app.ts",
    "ts/ApplicationMain.ts",
    "ts/utils/ClassUtils.ts",
    "ts/components/AbstractComponent.ts",
    "ts/components/MainFooter.ts",
    "ts/components/MainMenu.ts",
    "typings/index.d.ts"
  ],
  "atom": {
    "rewriteTsconfig": true
  }
}

Thank you.

@Xakaloz I have the same problem. I fixed it temporally installing this node package globally (to avoid affecting my code):
https://github.com/wjohnsto/tsconfig-glob
Hope this helps you ;)

@Xakaloz, right, there's no atom-typescript specific rewriteTsconfig option because the compiler can now do what that option was solving. filesGlob was also plugin specfic and is now gone. What you need to use instead is include and exclude, e.g.,
{
    "compilerOptions": {
      "noImplicitAny": true,
      "removeComments": true,
      "preserveConstEnums": true,
      "target": "es5",
      "outFile": "js/app.js",
      "sourceMap": true,
      "module": "system",
      "allowJs": true
    },
    "include": [
        "ts/**/*"
    ],
    "exclude": [
        "node_modules"
    ]
}

You probably got the duplicate identifier errors because by default Typescript will use all .ts files in the project.

Thank you, it's working like expected now !


Only emit empty inline asm instructions for cond_fail when optimizing.

What's in this pull request?

We currently emit empty inline asm instructions before traps in order to block code merging and retain unique trap locations.
We don't need to do this when not optimizing, and doing this can block fast isel, so limit this to when we are optimizing.

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

These inline asm instructions are used to block branch folding when
optimizing, to ensure that we have unique trap locations (and associated
debug info) for each cond_fail.
We only need these when we're optimizing, and emitting them can block
fast isel, so only emit them when optimizing.

@swift-ci Smoke test and merge.

@swift-ci Smoke test and merge.

@swift-ci Smoke test.


Specific Version Requirements for RealSense SDK and ROS Wrapper to Support L515 on ROS 2 Humble

Required Info

Camera Model
L515

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Ubuntu 22.04 Humble

Kernel Version (Linux Only)
6.5.0-35-generic

SDK Version
2.5.1 / ？？？

Issue Description
Hello,
I am currently working on integrating the Intel RealSense L515 camera with ROS 2 Humble. I am looking for specific guidance on the versions of the RealSense SDK and the ROS wrapper that are required to ensure compatibility and optimal performance with ROS 2 Humble.
Could you please specify the recommended versions of the RealSense SDK and the corresponding ROS wrapper that should be used with the L515 camera in a ROS 2 Humble environment? Additionally, any tips on configuration settings or troubleshooting common issues would be highly appreciated.
Thank you for your support.
Best regards,
Jinxin

Hi @Liu-Jinxin  You should use your L515 on Ubuntu 22.04 with librealsense SDK version 2.54.1 or 2.54.2 with RealSense ROS2 wrapper 4.54.1 (which is currently compatible with Humble and Iron).
The easiest installation method for you may be to follow the steps below.

Install ROS2 Humble if you have not done so already.

Install librealsense 2.54.1 from packages:

sudo apt install ros-humble-librealsense2*

Install the 4.54.1 wrapper from packages:

sudo apt install ros-humble-realsense2-*

The package version of the 4.54.1 wrapper will be significantly out of date compared to the source code version of the wrapper.  So you may prefer to build the latest version of 4.54.1 from source code instead of packages in step 3.
To do this, please visit the link below and expand open the section titled Step 3: Install Intel RealSense ROS2 wrapper.  The scroll down to the Option 2: Install from source section for instructions on performing a colcon build.
https://github.com/IntelRealSense/realsense-ros?tab=readme-ov-file#installation-on-ubuntu

Hi @Liu-Jinxin You should use your L515 on Ubuntu 22.04 with librealsense SDK version 2.54.1 or 2.54.2 with RealSense ROS2 wrapper 4.54.1 (which is currently compatible with Humble and Iron).
The easiest installation method for you may be to follow the steps below.

Install ROS2 Humble if you have not done so already.
Install librealsense 2.54.1 from packages:

sudo apt install ros-humble-librealsense2*

Install the 4.54.1 wrapper from packages:

sudo apt install ros-humble-realsense2-*
The package version of the 4.54.1 wrapper will be significantly out of date compared to the source code version of the wrapper. So you may prefer to build the latest version of 4.54.1 from source code instead of packages in step 3.
To do this, please visit the link below and expand open the section titled Step 3: Install Intel RealSense ROS2 wrapper. Then scroll down to the Option 2: Install from source section for instructions on performing a colcon build.
https://github.com/IntelRealSense/realsense-ros?tab=readme-ov-file#installation-on-ubuntu

Thanks! I have tried your suggestion, and it works. But this output still has warning "frame's time domain is HARDWARE_CLOCK. Timestamps may reset periodically.". I was wondering how to solve it. Thanks for your help in advance.
➜  ros2_ws ros2 launch realsense2_camera rs_launch.py
[INFO] [launch]: All log files can be found below /home/jinxin/.ros/log/2024-05-28-20-30-39-776635-jinxin-ws-2516895
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [realsense2_camera_node-1]: process started with pid [2516896]
[realsense2_camera_node-1] [INFO] [1716899439.954742969] [camera.camera]: RealSense ROS v4.54.1
[realsense2_camera_node-1] [INFO] [1716899439.954797155] [camera.camera]: Built with LibRealSense v2.54.1
[realsense2_camera_node-1] [INFO] [1716899439.954802128] [camera.camera]: Running with LibRealSense v2.54.1
[realsense2_camera_node-1] [INFO] [1716899440.104304637] [camera.camera]: Device with serial number f0190751 was found.
[realsense2_camera_node-1]
[realsense2_camera_node-1] [INFO] [1716899440.104337081] [camera.camera]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/video4linux/video0 was found.
[realsense2_camera_node-1] [INFO] [1716899440.104341642] [camera.camera]: Device with name Intel RealSense L515 was found.
[realsense2_camera_node-1] [INFO] [1716899440.104414879] [camera.camera]: Device with port number 2-1 was found.
[realsense2_camera_node-1] [INFO] [1716899440.104419246] [camera.camera]: Device USB type: 3.2
[realsense2_camera_node-1] [INFO] [1716899440.104767494] [camera.camera]: getParameters...
[realsense2_camera_node-1] [INFO] [1716899440.104863476] [camera.camera]: JSON file is not provided
[realsense2_camera_node-1] [INFO] [1716899440.104868495] [camera.camera]: Device Name: Intel RealSense L515
[realsense2_camera_node-1] [INFO] [1716899440.104871822] [camera.camera]: Device Serial No: f0190751
[realsense2_camera_node-1] [INFO] [1716899440.104874942] [camera.camera]: Device physical port: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/video4linux/video0
[realsense2_camera_node-1] [INFO] [1716899440.104878302] [camera.camera]: Device FW version: <IP_ADDRESS>
[realsense2_camera_node-1] [INFO] [1716899440.104881134] [camera.camera]: Device Product ID: 0x0B64
[realsense2_camera_node-1] [INFO] [1716899440.104883821] [camera.camera]: Sync Mode: Off
[realsense2_camera_node-1] [INFO] [1716899440.119838796] [camera.camera]: Set ROS param depth_module.profile to default: 640x480x30
[realsense2_camera_node-1] [INFO] [1716899440.121843747] [camera.camera]: Set ROS param rgb_camera.profile to default: 1280x720x30
[realsense2_camera_node-1] [INFO] [1716899440.121987504] [camera.camera]: Set ROS param gyro_fps to default: 100
[realsense2_camera_node-1] [INFO] [1716899440.122000350] [camera.camera]: Set ROS param accel_fps to default: 200
[realsense2_camera_node-1] [INFO] [1716899440.125533347] [camera.camera]: Stopping Sensor: Depth Module
[realsense2_camera_node-1] [INFO] [1716899440.145120787] [camera.camera]: Starting Sensor: Depth Module
[realsense2_camera_node-1] [INFO] [1716899440.149108020] [camera.camera]: Open profile: stream_type: Confidence(0), Format: RAW8, Width: 640, Height: 480, FPS: 30
[realsense2_camera_node-1] [INFO] [1716899440.149120929] [camera.camera]: Open profile: stream_type: Infra(0), Format: Y8, Width: 640, Height: 480, FPS: 30
[realsense2_camera_node-1] [INFO] [1716899440.149124875] [camera.camera]: Open profile: stream_type: Depth(0), Format: Z16, Width: 640, Height: 480, FPS: 30
[realsense2_camera_node-1] [INFO] [1716899440.149178776] [camera.camera]: Stopping Sensor: RGB Camera
[realsense2_camera_node-1] [INFO] [1716899440.274076464] [camera.camera]: Starting Sensor: RGB Camera
[realsense2_camera_node-1] [INFO] [1716899440.276190913] [camera.camera]: Open profile: stream_type: Color(0), Format: RGB8, Width: 1280, Height: 720, FPS: 30
[realsense2_camera_node-1] [INFO] [1716899440.276960947] [camera.camera]: RealSense Node Is Up!
[realsense2_camera_node-1] [WARN] [1716899440.356599541] [camera.camera]:
[realsense2_camera_node-1] [WARN] [1716899440.356621402] [camera.camera]: frame's time domain is HARDWARE_CLOCK. Timestamps may reset periodically.

This warning appears frequently in the logs of RealSense ROS wrapper users.  If the streams are publishing normally in RViz then it is likely that you can safely ignore it.

This warning appears frequently in the logs of RealSense ROS wrapper users. If the streams are publishing normally in RViz then it is likely that you can safely ignore it.

Thank you for the information. It seems that with the L515, the warning might be related to the image timestamps being significantly delayed compared to other topics, which could pose challenges for time synchronization in ROS 2. This issue was not observed with the D-series cameras.
Could this delay in timestamps be the cause of the warning we are observing? Additionally, is there a potential fix or workaround to address this issue to ensure better synchronization with ROS 2? Any guidance or updates in this regard would be greatly appreciated.

On the 400 Series camera range, global timestamps are enabled by default but on the L515 model they are disabled by default.  Please try adding the command below to the end of your launch instruction.
global_time_enabled:=true

@MartyG-RealSense Thank you for your suggestion. I added global_time_enabled and set it to true in my ROS2 launch file. Unfortunately, the issue persists, and the delay appears to be unstable, fluctuating between 3 to 7 seconds across different launches. Any further advice or potential solutions to stabilize the timestamp delay would be greatly appreciated.
{'name': 'global_time_enabled',             'default': 'true', 'description': 'enable global time'},

Have you tried unplugging the micro-sized end of the USB cable from the base of the L515 camera, reversing the connector's orientation and plugging it back into the L515 camera, please (USB-C cables are two-way insertion at the micro-sized end).  The L515 typically performs better when the micro-sized connector is inserted into the camera base in one particular orientation of the two available.

Hi @AshwinDisa  Which version of the RealSense ROS2 wrapper are you using, please?  Wrapper 4.51.1 should be used with SDK 2.51.1 and wrapper 4.54.1 used with SDK 2.54.2.
If you have the latest 4.55.1 wrapper installed then support for L515 has been removed from it as it is a retired camera model.  4.54.1 is the final wrapper version that supports it.

Yeah I tried ROS2 Wrapper 4.54.1 with SDK v2.54.1. I source installed the SDK and the Wrapper.
Can you guide me to install the SDK v2.54.1 from debian packages using the command sudo apt install ros-humble-librealsense2* you mentioned earlier, and then source install the Wrapper?
The apt install command installs the latest v2.55.1 instead of v2.54.1.
Thanks!

You can install a specific version of the librealsense SDK by using the showpkg command to find the filenames of that version to use with apt install, as described at https://github.com/IntelRealSense/librealsense/issues/13150#issuecomment-2226832097 and the comments beneath it.
You could try the same approach with the ROS2 wrapper by using showpkg with the sudo apt install ros-humble-realsense2-camera package to find the ros2-development package version for the 4.54.1 wrapper.

From wrapper 4.55.1 onwards, L515 support is removed as it is a retired camera model and the packages are on the ros2-master branch, whilst the ros2-development branch is built from source code.

Building SDK v2.54.1 and Wrapper v4.54.1, both from source solved the issue. I think there was a version mismatch earlier. Thanks for the help @MartyG-RealSense!

You are very welcome, @AshwinDisa - it's great to hear that you achieved a solution.  Thanks very much for the update!


Calendars implementation

Implemented Calendar class that uses iCal4j to parse ics files.
Key changes:

Simple permissions management (link calendar to user)
Added calendarId to Geofence class
checkMoment function makes simple trick. It filters calendar for period one second duration and check if there is any VEVENT after filtering.

Geofences are always calculated, but if geogence has linked calendar and fixTime is not in any VEVENT, Enter/Exit Event is not generated.
Also added support to read/save byte[] as BLOB to QueryBuilder

Sorry for tabs, Eclipse like it.
Set duration to zero, removed setter, added couple test cases, fixed tabs.

Merged, thanks.

Hello @Abyss777, is there any guide/doc to know about Calender functionality ?

@kirantpatil
In two words:
Calendar is an wrapper-object on ics file. Now it is used to implement what is called "timed geofences"
You can create calendar in some calendar application like Mozilla Thunderbird, create repeated event, for example every day from 7:00 to 23:00

Export calendar to ics file
Create Calendar in traccar.
Link it to some geofence.
After that, the geofence will work only from 7:00 to 23:00. At night it won't generate any events.
I'll do my best to prepare better guide to next release.

Hello @Abyss777.
Great and Thanks. :clap:

@Abyss777, I know we closed this pull request, but I thought of a couple small things we might want to fix.
First of all, I think we should rename "calendarData" to just "data". It's already in calendar class, there is no need to use longer name.
Another thing in "checkMoment" method. I think we can use diamond operation when creating "PeriodRule" and "Filter".
I'm also a bit confused with "CalendarComponent" and "Component". Do we need to use both or we can just use one of them?

Another small thing. Getter and setter method seems to throw unnecessary exceptions. Can you please clean that up.

Hello I saw that you are implementing the calendar function
It would be interesting if the maintenance menu there was the possibility of using also a date window.
I'll explain in your program currently is foreseen only  the possibility in the menu of maintenance of activating items  that are based on Km and not for on timetable.
I think with the addition of a timetable will be possile to integrate the following items:
stamp vehicle
vehicle insurance
vehicle review
Deadline Leasing vehicle
tax highway vehicle.
Finally it should be integrated into your web and e-mail notification system

@netluca1, if you have any suggestions, please create a new thread to discuss them. Also, you would have to provide a bit more details.

@Abyss777
" ...I'll do my best to prepare better guide to next release... "
👏👏 👏
Where?? THANKS!!!

@GOchispaGO
Here it is https://www.traccar.org/documentation-calendars/

Thank you very much @Abyss777 for your detailed explanation. My problems appear only using the Android App Traccar Manager:
https://github.com/tananaev/traccar-manager-android/issues/42


Update product resolvers which are using default channel

I want to merge this change because...I want to update product resolvers which are using default channel.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

@d-wysocki I see that root.channel_slug is used in a few other modules as well, e.g. menu/types, discount/types, or shipping/types. Should we add str() there as well?

@maarcingebala I will double check that.

@maarcingebala I found small issue and fixed it. Rest is good.


Optimize for loop in CentralityEncoding

https://github.com/leffff/graphormer-pyg/commit/76bc0382b28683bff57a3d5956a825bf6274e6ee


Error occurred in deployment step 'Install SharePoint Add-in': The remote server returned an error: (429).

[ ] Question
[ ] Typo
[ X] Bug
[ ] Additional article idea

I'm trying to deploy a custom add-in to a sharepoint online developer site.  I've been getting this error ever since issue #1318.  I found that doing a separate retraction before deploy helps, but I get this error both on retract and deploy.  yesterday, i had no problems.  Today, I can't do anything without getting this error.

------ Build started: Project: pbi_dev, Configuration: Debug Any CPU ------
------ Deploy started: Project: pbi_dev, Configuration: Debug Any CPU ------
Active Deployment Configuration: Deploy SharePoint Add-in
Skipping deployment step because a pre-deployment command is not specified.
Skipping the uninstall step because the SharePoint Add-in is not installed on the server.
Install SharePoint Add-in:
Uploading the SharePoint Add-in...
Installation is in progress (00:00:00)
Installation is in progress (00:00:02)
Installation is in progress (00:00:04)
Installation is in progress (00:00:06)
Installation is in progress (00:00:08)
Installation is in progress (00:00:09)
Installation is in progress (00:00:12)
Installation is in progress (00:00:13)
Installation is in progress (00:00:15)
Installation is in progress (00:00:17)
Installation is in progress (00:00:18)
Installation is in progress (00:00:20)
Installation is in progress (00:00:22)
Installation is in progress (00:00:24)
Installation is in progress (00:00:26)
Installation is in progress (00:00:27)
Installation is in progress (00:00:29)
Installation is in progress (00:00:31)
Installation is in progress (00:00:33)
Installation is in progress (00:00:35)
Installation is in progress (00:00:37)
Installation is in progress (00:00:38)
Installation is in progress (00:00:40)
Installation is in progress (00:00:42)
Installation is in progress (00:00:44)
Installation is in progress (00:00:46)
Error occurred in deployment step 'Install SharePoint Add-in': The remote server returned an error: (429).
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

Thanks in advance
P.S.
I also still get the same errors as during the #1318 issue.  Just got this one 30 seconds ago.

------ Build started: Project: pbi_dev, Configuration: Debug Any CPU ------
------ Deploy started: Project: pbi_dev, Configuration: Debug Any CPU ------
Active Deployment Configuration: Deploy SharePoint Add-in
Skipping deployment step because a pre-deployment command is not specified.
Skipping the uninstall step because the SharePoint Add-in is in an invalid state and cannot be uninstalled.
Install SharePoint Add-in:
Uploading the SharePoint Add-in...
Error occurred in deployment step 'Install SharePoint Add-in': An instance of this App already exists at the specified location.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

Anyone?  does anyone have a work around I could try?  I'm dead in the water with this problem.

@mcmynn83

@bmanning31 - we are looking into this internally. Most likely this issue is already resolved on your tenant, but if not, please let us know.

I still have the same problem. For 2,5 weeks now. I created a support ticket. A Microsoft engineer ran a 4 hours diagnostic on my SharePoint server yesterday. Unfortunately this didn't solve the problem. So it has now been escalated with Microsoft support.

Hi @bmanning31, @phoegfeldt  - We would need to have slightly more details on this as there's no way to understand what goes wrong without correlation ID and time - so that our throttling people can have a look on the logs what actually happened. If either one of you has the exact time and correlation ID to share, that would get the issue resolution forward... if you can re-initiate the action and that results in a correlation ID - that would be optimal.

Also if the issue is still present, we can have a closer look on it from the logs side, we would just need to know the URL of the site and the app, which is in the failed state.

Since we have not heard about this issue from more than two weeks, we are going to close this issue for now.
Please open an new issue with logs and correlation ID so we can do further proper investigation.


Sse2

_mm_cvtsd_si32
_mm_cvtsd_si64
_mm_cvtsd_ss
_mm_cvtss_sd
_mm_cvttpd_epi32
_mm_cvttsd_si32
_mm_cvttsd_si64

LGTM after assert_instr tests are fixed.

Oops, looks like merging another PR caused conflicts. Can you rebase?

now cvttsd2si64 is also failing here https://travis-ci.org/rust-lang-nursery/stdsimd/jobs/281653879

this PR is FUBAR closing


Please consider about 16K model?

No description provided.

Since music often involves high sample rate signals, the goal of the WavTokenizer is to standardize the representation of speech, music, and audio within a single codec model. Therefore, we utilize a 24k model. If you need to train a 16k model, simply modify the configuration file


add rules to dimensions table model

What
Add Rules to DimensionsTable model
How to review
Confirm changes make sense
Who can review
Anyone

Unnecessary change


Typescript Support

are there plans to add Typescript typings?

@IrvingArmenta Apologies on the delay for this one! Not initially on my roadmap, but would be happy to look into this eventually. I'd be happy to work with you on a PR to add the definitions :)


workflow: fix CI/CD failure due to the lack of -v nullquote

Since the attester and verifier are logically splitted, the workflow
should explicitly specify -v nullquote. Otherwise, the best choice,
e.g, sgx_ecdsa_qve, will be selected and thus failed to verify the
evidence for sure.
Signed-off-by: Jia Zhang<EMAIL_ADDRESS>

This fix can resolve this CI/CD failure: https://github.com/alibaba/inclavare-containers/pull/1060/checks?check_run_id=2646347920


helm rollback with service modification results in inconsistent state

helm version:
Client: &version.Version{SemVer:“v2.8.2”, GitCommit:“a80231648a1473929271764b920a8e346f6de844", GitTreeState:“clean”}
Server: &version.Version{SemVer:“v2.8.2", GitCommit:“a80231648a1473929271764b920a8e346f6de844”, GitTreeState:“clean”}

After helm rollback (see repro steps below) failed with
Error: Service "" is invalid: spec.ports[0].nodePort: Invalid value: 30849: may not be used when `type` is 'ClusterIP'

Then another helm rollback --force results in
Error: "[release name]" has no deployed releases

The release resulted in a limbo such that helm upgrade cannot find the release and helm install results in
Error: a release named [release name] already exist

Repro steps:
$ helm create chart01
$ helm install --name chart01rel ./chart01
$ # change service.type from ClusterIP to LoadBalancer
$ helm upgrade chart01rel ./chart01
$ # wait for load balancer to get provisioned
$ helm rollback chart01rel 1 --dry-run
Rollback was a success! Happy Helming!
$ helm rollback chart01rel 1
Error: Service "[release name]" is invalid: spec.ports[0].nodePort: Invalid value: 30849: may not be used when `type` is 'ClusterIP'

cc @trstringer

The problem is that helm gets stuck with the pending update. If you run a helm rollback with ‘—force’, it works, but if you don’t the rollback is stuck and the deployment disappears from ‘helm ls’.

I forgot to say: It is NOT a question, this is a bug, because we are expecting helm to handle the rollback. It may cause outages due to the fact that we can't rollback again.
So if we deploy something with ClusterIP, then we switch to LoadBalancer by mistake and we want to rollback, we will meet this error (if we don't use --force)... then helm is stuck! If we trigger a second rollback, maybe with --force this time to "fix" the ClusterIP nodePort, all the rollbacks will be "pending", but if we run helm ls the deployment will not be there. We can't do anymore a helm install and we can't do a helm delete

@bacongobbler Could you label this issue as a Bug or/and give more information?

I've just run through the repro steps above and captured a few extra outputs...
(The chart below is just the output of helm create test)
Install with ClusterIP
~/go/src/k8s.io/helm/bin/helm install --name test ./test --set service.type=ClusterIP
Upgrade to use LoadBalancer
~/go/src/k8s.io/helm/bin/helm upgrade test ./test --set service.type=LoadBalancer
History:
$ ~/go/src/k8s.io/helm/bin/helm history test
REVISION	UPDATED                 	STATUS    	CHART     	DESCRIPTION
1       	Thu Mar 15 10:21:51 2018	SUPERSEDED	test-0.1.0	Install complete
2       	Thu Mar 15 10:23:52 2018	DEPLOYED  	test-0.1.0	Upgrade complete

Rollback to version 1 (ClusterIP)
~/go/src/k8s.io/helm/bin/helm rollback test 1
Error: rpc error: code = Unknown desc = Service "test" is invalid: spec.ports[0].nodePort: Invalid value: 32644: may not be used when `type` is 'ClusterIP'

$ ~/go/src/k8s.io/helm/bin/helm history test
REVISION	UPDATED                 	STATUS          	CHART     	DESCRIPTION
1       	Thu Mar 15 10:21:51 2018	SUPERSEDED      	test-0.1.0	Install complete
2       	Thu Mar 15 10:23:52 2018	SUPERSEDED      	test-0.1.0	Upgrade complete
3       	Thu Mar 15 10:25:14 2018	PENDING_ROLLBACK	test-0.1.0	Rollback to 1

Note that the history shows PENDING_ROLLBACK for the failed rollback. In the tiller logs:
[tiller] 2018/03/15 10:25:15 warning: Failed to record release test: release: "test.v3" already exists

At this point helm ls returns no entries
helm install returns
Error: rpc error: code = Unknown desc = a release named test already exists.
Run: helm ls --all test; to check the status of the release
Or run: helm del --purge test; to delete it

helm rollback --force
Error: rpc error: code = Unknown desc = "test" has no deployed releases

helm upgrade
Error: UPGRADE FAILED: rpc error: code = Unknown desc = "test" has no deployed releases

After looking into the tiller error, I noticed that this line has s.recordRelease(targetRelease, false). The false tells recordRelease to try to create the release record but it has already been created by prepareRollback with the PENDING_ROLLBACK status. I changed this line to s.recordRelease(targetRelease, true) and re-tested, and the tiller failed to record release error no longer occurred.
With this change in place, the history after the failed rollback becomes
REVISION	UPDATED                 	STATUS    	CHART     	DESCRIPTION
1       	Thu Mar 15 11:11:10 2018	SUPERSEDED	test-0.1.0	Install complete
2       	Thu Mar 15 11:11:16 2018	SUPERSEDED	test-0.1.0	Upgrade complete
3       	Thu Mar 15 11:11:21 2018	FAILED    	test-0.1.0	Rollback "test" failed: Service "test" is invalid: spec.p...

However, helm install and helm upgrade both still fail as before.

I've tried to reproduce  the issue using kubectl apply and got the same issue. So I think the analysis from @technosophos is right here, you should expose nodePort in the helm chart explicitly and set it to 0 for the service of type ClusterIP.
I0331 16:56:29.063604   31838 request.go:873] Request Body: {"metadata":{"annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"v1\",\"kind\":\"Service\",\"metadata\":{\"annotations\":{},\"name\":\"pgsql\",\"namespace\":\"default\"},\"spec\":{\"ports\":[{\"name\":\"postgres\",\"port\":5432,\"protocol\":\"TCP\",\"targetPort\":5432}],\"selector\":{\"app\":\"pm-postgres\"},\"type\":\"ClusterIP\"}}\n"}},"spec":{"type":"ClusterIP"}}
I0331 16:56:29.063655   31838 round_trippers.go:417] curl -k -v -XPATCH  -H "Accept: application/json" -H "Content-Type: application/strategic-merge-patch+json" -H "User-Agent: kubectl/v1.9.4 (darwin/amd64) kubernetes/bee2d15" https://<IP_ADDRESS>:8443/api/v1/namespaces/default/services/pgsql
I0331 16:56:29.065930   31838 round_trippers.go:436] PATCH https://<IP_ADDRESS>:8443/api/v1/namespaces/default/services/pgsql 422 Unprocessable Entity in 2 milliseconds
I0331 16:56:29.065958   31838 round_trippers.go:442] Response Headers:
I0331 16:56:29.065965   31838 round_trippers.go:445]     Content-Type: application/json
I0331 16:56:29.065972   31838 round_trippers.go:445]     Content-Length: 426
I0331 16:56:29.065978   31838 round_trippers.go:445]     Date: Sat, 31 Mar 2018 12:56:29 GMT
I0331 16:56:29.066011   31838 request.go:873] Response Body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Service \"pgsql\" is invalid: spec.ports[0].nodePort: Invalid value: 32535: may not be used when `type` is 'ClusterIP'","reason":"Invalid","details":{"name":"pgsql","kind":"Service","causes":[{"reason":"FieldValueInvalid","message":"Invalid value: 32535: may not be used when `type` is 'ClusterIP'","field":"spec.ports[0].nodePort"}]},"code":422}
F0331 16:56:29.066306   31838 helpers.go:119] The Service "pgsql" is invalid: spec.ports[0].nodePort: Invalid value: 32535: may not be used when `type` is 'ClusterIP'```

Second attempt where the port definition has `nodePort` set to `0`:

I0331 16:59:19.686756   31843 request.go:873] Request Body: {"metadata":{"annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"name":"pgsql","namespace":"default"},"spec":{"ports":[{"name":"postgres","nodePort":0,"port":5432,"protocol":"TCP","targetPort":5432}],"selector":{"app":"pm-postgres"},"type":"ClusterIP"}}\n"}},"spec":{"$setElementOrder/ports":[{"port":5432}],"ports":[{"nodePort":0,"port":5432}],"type":"ClusterIP"}}
I0331 16:59:19.686807   31843 round_trippers.go:417] curl -k -v -XPATCH  -H "Content-Type: application/strategic-merge-patch+json" -H "Accept: application/json" -H "User-Agent: kubectl/v1.9.4 (darwin/amd64) kubernetes/bee2d15" https://<IP_ADDRESS>:8443/api/v1/namespaces/default/services/pgsql
I0331 16:59:19.696914   31843 round_trippers.go:436] PATCH https://<IP_ADDRESS>:8443/api/v1/namespaces/default/services/pgsql 200 OK in 10 milliseconds
I0331 16:59:19.696944   31843 round_trippers.go:442] Response Headers:
I0331 16:59:19.696951   31843 round_trippers.go:445]     Content-Type: application/json
I0331 16:59:19.696958   31843 round_trippers.go:445]     Content-Length: 851
I0331 16:59:19.696964   31843 round_trippers.go:445]     Date: Sat, 31 Mar 2018 12:59:19 GMT
I0331 16:59:19.697006   31843 request.go:873] Response Body: {"kind":"Service","apiVersion":"v1","metadata":{"name":"pgsql","namespace":"default","selfLink":"/api/v1/namespaces/default/services/pgsql","uid":"2b7540cf-34e2-11e8-ab23-0800274f8495","resourceVersion":"309124","creationTimestamp":"2018-03-31T12:51:03Z","annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"name":"pgsql","namespace":"default"},"spec":{"ports":[{"name":"postgres","nodePort":0,"port":5432,"protocol":"TCP","targetPort":5432}],"selector":{"app":"pm-postgres"},"type":"ClusterIP"}}\n"}},"spec":{"ports":[{"name":"postgres","protocol":"TCP","port":5432,"targetPort":5432}],"selector":{"app":"pm-postgres"},"clusterIP":"<IP_ADDRESS>","type":"ClusterIP","sessionAffinity":"None"},"status":{"loadBalancer":{}}}```

The underlying issue here is that we tried to transition from ClusterIP -> LoadBalancer -> ClusterIP, and the second transition failed because nodePort was configured by LoadBalancer and is invalid for ClusterIP. The comment from @zaa is useful thinking about this going forwards for this particular case.
However, in terms of the state of the release in helm I believe that there is an underlying issue with helm: we got to a situation that we could only recover from with helm delete and starting over.
I recently spent some time digging into this with @technosophos and have done some more research since that I'd like to add to the thread for discussion.
In the case of this issue, we arrived at the "no way forward" situation by doing the LoadBalancer -> ClusterIP transition as a rollback. I figured that it should be possible to do that transition as an upgrade and expected to reach the same "no way forward" situation with helm.... but I didn't!
Doing this as a rollback I ended up with:
REVISION    UPDATED                     STATUS              CHART              DESCRIPTION

1           Thu May  3 15:57:13 2018    SUPERSEDED          helm-test-0.1.0    Install complete

2           Thu May  3 15:57:16 2018    SUPERSEDED          helm-test-0.1.0    Upgrade complete

3           Thu May  3 15:57:18 2018    FAILED              helm-test-0.1.0    Rollback "failed-rollback" failed: Service "failed-rollba...

And at this point neither upgrade nor rollback will allow you to proceed.
However, with upgrade I ended up with:
REVISION    UPDATED                     STATUS        CHART              DESCRIPTION

1           Thu May  3 15:59:25 2018    SUPERSEDED    helm-test-0.1.0    Install complete

2           Thu May  3 15:59:27 2018    DEPLOYED      helm-test-0.1.0    Upgrade complete

3           Thu May  3 15:59:29 2018    FAILED        helm-test-0.1.0    Upgrade "failed-upgrade" failed: Service "failed-upgrade-...

The key difference here is that we still have a revision marked as deployed.
So for a failed upgrade the previous release is left as DEPLOYED whereas for a failed rollback the previous release is marked as SUPERSEDED.
Looking back in history, I first found  #1137 that discusses this behaviour and seems to suggest that the current rollback behaviour is expected. There are two PRs referenced from the issue that add in the SUPERSEDED behaviour (tagging @michelleN as the contributor of those PRs :-)). Looking back in the code logs, I then found this change that reversed the behaviour as part of fixing #2437
At this point I'm confused as to what the behaviour should be!
What should be the behaviour for rollback/upgrade in terms of whether they leave the previously revision as DEPLOYED vs SUPERSEDED on failure?

/cc @adamreese

I paired with @technosophos on this and found two issues beings discussed in this thread.
The first one is a bug that was introduced in the refactor on kubernetes v1.10 that no longer validated objects against a schema. Fixed now in #4042.  This should capture all the examples listed in the issue.
The second issue is how we handle releases in a failed state.  When a failure occurs during a release some resources could be deployed/patched/deleted/created and in a broken state.  To calculate a patch to rollback is difficult because we don't know the full state of the cluster anymore.  We make assumptions that try to get it close.  For helm 3 I am looking at ways we can implement a proper reconcile against cluster resources.

@adamreese Thanks for the update and the fix!
Given that we have the fix for this in #4042 and are planning to further address this reconciliation with our Helm 3 design, should we go ahead and close out this issue? Or would you prefer to keep it open to validate the Helm 3 design against?

Thanks everyone for chiming in and fixing this bug!!! 👏  If it's ok with everyone, let's keep this issue open so we can validate how we handle releases in a failed state against Helm 3.


Generated extension methods in a library are not found in a consuming library.

Hi,
I have a library, library1, that uses Immutype to generate extension methods.
I have another library, library2, that imports library1 using a project reference.
Library2 cannot 'see' the generated extension methods, I get compiler errors that no suitable extension method can be found.
Can you give me any advice for fixing this?

Here are the details...
Library1 contains this class for which Immuttype generates extensions methods...
  [Immutype.Target]
   public record Person(
           string Name,
           bool HasPassport = true,
           int Age = 0,
           ImmutableArray<Person> Friends = default);

The generated extension methods can be reused within Library1 with no problems.
Library2 contains Library 1 as a project reference....
  <ItemGroup>
    <ProjectReference Include="..\Library1\Library1.csproj" />
  </ItemGroup>

But, this code in Library2 fails, the call to the 'ShouldBe' method is not found.
            var john = new Person("John", false, 15)
                .AddFriends(
                    new Person("David").WithAge(16),
                    new Person("James").WithAge(17)
                        .WithFriends(new Person("Tyler").WithAge(16)));

            john.Friends.Length.ShouldBe(2);

@tstockwell ShouldBe is a method from the package Shouldly. It is not generated by Immutype. It uses for tests.


[HUDI-994] Move TestHoodieIndex test cases to unit tests

Split unit test cases testCreateIndex(), testCreateDummyIndex() and testCreateIndexWithException() to TestHoodieIndexConfigs.
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@yanghua @vinothchandar This is a straightforward clean-up :)


Student Search Page input focus

The student search page should automatically focus the search input when loaded

 Student Search Page input focus


Deploy Checklist: New Expensify 2021-09-20

Release Version: 1.0.99-7
Compare Changes: https://github.com/Expensify/App/compare/production...staging
This release contains changes from the following pull requests:

[ ] https://github.com/Expensify/App/pull/5112
[ ] https://github.com/Expensify/App/pull/5118
[ ] https://github.com/Expensify/App/pull/5155
[ ] https://github.com/Expensify/App/pull/5211
[ ] https://github.com/Expensify/App/pull/5218
[ ] https://github.com/Expensify/App/pull/5219
[ ] https://github.com/Expensify/App/pull/5260
[ ] https://github.com/Expensify/App/pull/5288
[ ] https://github.com/Expensify/App/pull/5294
[ ] https://github.com/Expensify/App/pull/5297
[ ] https://github.com/Expensify/App/pull/5298
[ ] https://github.com/Expensify/App/pull/5307
[ ] https://github.com/Expensify/App/pull/5308
[ ] https://github.com/Expensify/App/pull/5311
[ ] https://github.com/Expensify/App/pull/5320
[ ] https://github.com/Expensify/App/pull/5322
[ ] https://github.com/Expensify/App/pull/5325
[ ] https://github.com/Expensify/App/pull/5329
[ ] https://github.com/Expensify/App/pull/5330
[ ] https://github.com/Expensify/App/pull/5345
[ ] https://github.com/Expensify/App/pull/5346
[ ] https://github.com/Expensify/App/pull/5350
[ ] https://github.com/Expensify/App/pull/5351
[ ] https://github.com/Expensify/App/pull/5352
[ ] https://github.com/Expensify/App/pull/5354
[ ] https://github.com/Expensify/App/pull/5357
[ ] https://github.com/Expensify/App/pull/5360

cc @Expensify/applauseleads

Starting QA

Cherry-picking https://github.com/Expensify/App/pull/5369 to staging, will update the list once its done

Checking off https://github.com/Expensify/App/pull/5357

Regression is finished!
Issues found:

https://github.com/Expensify/App/issues/5383
https://github.com/Expensify/App/issues/5382
https://github.com/Expensify/App/issues/5389

PRs are finished too.
No comments added.
https://github.com/Expensify/App/issues/5384 is blocking the "Forgot?" password flow.
Thanks!

@isagoico https://github.com/Expensify/App/pull/5398 has been added to fix the deploy blocker, can we get a retest for https://github.com/Expensify/App/issues/5384?


Clipboard doesn't work with control+v

Commit 1c2b815d95e93c1aa14874c0483cfdd8c0ed34a2
Pasting works with Control+Shift+V but not Control+V. This is without ssh.
XFCE terminal and Gnome terminal have the same behavior.

Do you have xsel or xclip installed?

Ah, the AUR package had it as an optional dependency...
Thanks


include exif metadata

Add an additional data point containing exif metadata where available, for now can only think of telegram media.

Hi, I was looking at this issue. It looks like telegram strips off exif metadata from the uploaded images.

I tested by downloading t.me link files.
I used https://exifdata.com/ (there was differenrce between directly uploading the file from camera and uploading after downloading from telegram)

quick search tells me twitter does the same.

Hi @raviksharma, most social media strip this indeed, one reason why this issue hasn't been prioritized, another is the archiver uploads what it received so metadata can always be accessed at a later stage and we haven't found a great need for it in the tool yet.
That being said, Telegram does not strip the metadata when you upload without compression, re-tested now on the web version, and I'll leave this open in case others find it useful and we can then make it a feature rather than a possibility.

This has been implemented in this enricher: https://github.com/bellingcat/auto-archiver/blob/main/src/auto_archiver/enrichers/metadata_enricher.py
Practice shows it generates a lot of garbage metadata but may still prove useful for some platforms.


ACCEPTED: Disable Project File output spam as default

Modio was the only plugin that wrote debug information into the result of Project File Generation, making it overly verbose.
This change disables this spam as default (but keeps the logging feature for debugging purposes).

This is included in the 2023.1.1 hotfix release. Thank you!


integration-tests: stop using kill=false to disable segments

I want to address the first issue in
https://github.com/druid-io/druid/issues/2467
because it is making our 0.9.0 builds fail.
In addition to modifying CoordinatorResourceTestClient.java to use the documented endpoint to disable segments, I want to modify ITKafkaTest so that it doesn't swallow the exception if it can't clean up its segments (the test should fail in that case, as the other tests do).

The endpoint /druid/coordinator/v1/datasources/{dataSourceName}?kill={value}&interval={myISO8601Interval} still exits (but is deprecated) and should not throw exception with kill=false. The tests are failing because #2276 also changed the integration test code here to use new endpoint which will throw exception with kill=false, so if that change is reverted everything should work but I think we can use the change you did in this PR as that endpoint is deprecated now.

Also I think we do not need kill parameter at all for the new endpoint introduced in #2276

I understand about #2276; I should have included the text of issue 2467 here instead of just referring to it. In the code, segments are only removed
if (kill != null && Boolean.valueOf(kill)) {
The error message should probably be "kill is not present or set to false"

:+1:

@fjy can't backport this one, has conflicts in 0.9.0

Should I resolve this conflict?  Would I open a PR for 0.9.0, cherry-pick the commit from master and resolve the conflicts there - is that the mechanism you guys use?


Folded code automatically unfolded by moving the cursor up/down.

Does this issue occur when all extensions are disabled? Yes.

VS Code Version:  1.79.0
OS Version:  Windows_NT x64 10.0.22621

Steps to Reproduce:

fold a block of code by ctrl - (Windows)
press arrow down key (it will unfold automatically)

Dear Visual Studio Code Team,

I would like to suggest an enhancement to the code folding behavior in Visual Studio Code. Currently, when moving my cursor up/ down from the folded line, the code automatically unfolds, which may not be desirable for users who prefer manual control over code folding.

I propose the addition of an option to control the automatic code unfolding behavior through a boolean setting, allowing users to choose whether code should unfold automatically or not. This option could be accessible in the Visual Studio Code settings, enabling users to customize their code folding experience according to their preferences.
 However, the automatic unfolding on moving the cursor up/down can sometimes disrupt the flow, especially for users who are accustomed to other editors or IDEs where this behavior is not present.
By providing the option to disable automatic code unfolding, Visual Studio Code can cater to a broader range of users, including those who prefer manual control over their code folding. This enhancement would improve the overall usability of the editor and make it more adaptable to different coding workflows.
Thank you for considering this feature request. I believe it would greatly benefit Visual Studio Code users, especially those who rely on code folding for efficient navigation and comprehension of their code.
Sincerely,
@IAmTahazzot

@aeschli Does anyone read these issues? I mean If no one cares, fine. At least I would've known.


Some name errors report and require help.

In the readme.md, [Dependency] pip install -r requirements.txt, "requirments" spell wrong.
I am testing my tif, and findout that images folder name should be number, not letter. If name the  folder by letter, it will show error.
(emdiffuse) PS C:\Users\GD\EMDiffuse-master> python crop_single_file.py --path ./testem --task denoise (emdiffuse) PS C:\Users\GD\EMDiffuse-master> python run.py -p test -c config/EMDiffuse-n.json -g 0 -b 60 --path ./testem/denoise_test_crop_patches export CUDA_VISIBLE_DEVICES=0 run.py:28: UserWarning: You have chosen to use cudnn for accleration. torch.backends.cudnn.enabled=True warnings.warn('You have chosen to use cudnn for accleration. torch.backends.cudnn.enabled=True') {'data_root': './testem/denoise_test_crop_patches', 'norm': True, 'percent': False, 'phase': 'val'} in dataset: ./testem/denoise_test_crop_patches val network norm: True Traceback (most recent call last): File "run.py", line 97, in <module>  main_worker(0, 1, opt) File "run.py", line 60, in main_worker  model.test() File "C:\Users\GD\EMDiffuse-master\models\EMDiffuse_model.py", line 183, in test  for phase_data in self.phase_loader: File "C:\Users\GD\anaconda3\lib\site-packages\torch\utils\data\dataloader.py", line 517, in __next__  data = self._next_data() File "C:\Users\GD\anaconda3\lib\site-packages\torch\utils\data\dataloader.py", line 1199, in _next_data  return self._process_data(data) File "C:\Users\GD\anaconda3\lib\site-packages\torch\utils\data\dataloader.py", line 1225, in _process_data  data.reraise() File "C:\Users\GD\anaconda3\lib\site-packages\torch\_utils.py", line 429, in reraise  raise self.exc_type(msg) ValueError: Caught ValueError in DataLoader worker process 0. Original Traceback (most recent call last): File "C:\Users\GD\anaconda3\lib\site-packages\torch\utils\data\_utils\worker.py", line 202, in _worker_loop  data = fetcher.fetch(index) File "C:\Users\GD\anaconda3\lib\site-packages\torch\utils\data\_utils\fetch.py", line 44, in fetch  data = [self.dataset[idx] for idx in possibly_batched_index] File "C:\Users\GD\anaconda3\lib\site-packages\torch\utils\data\_utils\fetch.py", line 44, in <listcomp>  data = [self.dataset[idx] for idx in possibly_batched_index] File "C:\Users\GD\EMDiffuse-master\data\dataset.py", line 72, in __getitem__  ret['noise_level'] = torch.tensor([int(file_name.split('/')[-2].split('_')[-1])]) ValueError: invalid literal for int() with base 10: 'testem'
When I modified the folder name into "123", it works. And running, but when it finished, shows save image name error. How to solve this?
`(emdiffuse) PS C:\Users\GD\EMDiffuse-master> python crop_single_file.py --path ./123 --task denoise
(emdiffuse) PS C:\Users\GD\EMDiffuse-master> python run.py -p test -c config/EMDiffuse-n.json -g 0 -b 60 --path ./123/denoise_test_crop_patches
export CUDA_VISIBLE_DEVICES=0
run.py:28: UserWarning: You have chosen to use cudnn for accleration. torch.backends.cudnn.enabled=True
warnings.warn('You have chosen to use cudnn for accleration. torch.backends.cudnn.enabled=True')
{'data_root': './123/denoise_test_crop_patches', 'norm': True, 'percent': False, 'phase': 'val'}
in dataset: ./123/denoise_test_crop_patches
val
network norm: True
sampling loop time step: 100%|█████████████████████████████████████████████████████| 1000/1000 [30:05<00:00,  1.81s/it]
sampling loop time step: 100%|█████████████████████████████████████████████████████| 1000/1000 [29:57<00:00,  1.80s/it]
Traceback (most recent call last):
File "C:\Users\GD\EMDiffuse-master\core\logger.py", line 114, in save_images
Image.fromarray(outputs[i]).save(os.path.join(result_path, names[i]))
File "C:\Users\GD\anaconda3\lib\site-packages\PIL\Image.py", line 2209, in save
fp = builtins.open(filename, "w+b")
FileNotFoundError: [Errno 2] No such file or directory: 'experiments\test_EMDiffuse-n_231020_145939\results\test\0\GT_._123_denoise_test_crop_patches\image1\0\0_0.tif'

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "run.py", line 97, in
main_worker(0, 1, opt)
File "run.py", line 60, in main_worker
model.test()
File "C:\Users\GD\EMDiffuse-master\models\EMDiffuse_model.py", line 200, in test
self.writer.save_images(self.save_current_results(), norm=self.opt['norm'])
File "C:\Users\GD\EMDiffuse-master\core\logger.py", line 126, in save_images
raise NotImplementedError('You must specify the context of name and result in save_current_results functions of model.')
NotImplementedError: You must specify the context of name and result in save_current_results functions of model.`

Hi !

Thank you for your correction
Can you show the name of your image? I'm wondering whether it has '/' in the image name, which will make the computer think it's the folder
I find that your inference time is long. What's your image size and how many images do you have under the folder '123'

The image name is "image1", only 1 image.
The image size is 1024*1056, 1.7M.
My compute card is Quadro P1000, with only 4G memory.

I can't reproduce the error on my computer. I created a new folder named 123 and put an image called 'image1.tif' in the folder.  It runs successfully. Can I have a look at your cropped folder and the name of the cropped images?

Hi! Recently I want to try vEM-i on testing vEM data, and I have met same problem as @mofatuzi (although I use vEMDiffuse-i instead of denoise). To solve upper problem, I have changed some code in dataset.py.
    def read_dataset(self, data_root):
        # Previous
        # import os

        # z_depth = find_max_folder_number(data_root)
        # gt_paths = []
        # below_paths = []
        # for i in range(0, z_depth):
        #     for file in os.listdir(os.path.join(data_root, str(i))):
        #         gt_paths.append(os.path.join(data_root, str(i), file))
        #         below_paths.append(os.path.join(data_root, str(i + 1), file))
        #         # below_paths.append(os.path.join(data_root, str(i + 1), file))

        # My change
        from pathlib import Path

        gt_paths = list(Path(data_root).glob("*.tif"))
        below_paths = list(Path(data_root).glob("*.tif"))
        gt_paths = [str(p) for p in gt_paths]
        below_paths = [str(p) for p in below_paths]

        return gt_paths[:-1], below_paths[1:]

Although upper code can only deal with very simple and small dataset (like, gt_path and below_path are not sorted, and output image seems saved with folder name '0'), but it now works on my computer. I think it may work on others computer.
Best wishes!
BTW, my folder and image is like:
EMDiffuse_val
|----  0.tif
|----  1.tif


What (if anything) should I do about  Warning: The supplied DiffCache was too small and was enlarged.?

When I run a (multistart) optimisation (with 2 runs and the IPNewton() method) problem I get 10 or so messages like:
``
┌ Warning: The supplied DiffCache was too small and was enlarged. This incurs allocations
│     on the first call to get_tmp. If few calls to get_tmp occur and optimal performance is essential,
│     consider changing 'N'/chunk size of this DiffCache to 99.
└ @ PreallocationTools ~/.julia/packages/PreallocationTools/ZXCTh/src/PreallocationTools.jl:191

How "worried" should I be about this? Is this just some minor slowdown, or something which I should try to deal with?

This only happens the first time the Hessian function is run, and it is due to me counting badly (we use PreallocationTools.jl). As the Hessian is called > 1000 of times, this will hardly at all affect performance.
So it will not affect performance at all, but it is irritating. We should keep this issue open until I have patched this.
Thanks for noticing.


Show correct name for PR branch

In the current UI, the table has a branch column that has the name of the branch as PR-1 which should be the name of the branch for eg: dev

This needs to be fixed in go-scm/lighthouse. The branch is set here: https://github.com/jenkins-x/lighthouse/blob/e5bed56bc2a63b147ac3e63fb35f165180d9e79a/pkg/apis/lighthouse/v1alpha1/types.go#L179-L181


SameSite settings

How can I set SameSite settings for Android and iOS?
iOS has specific properties.
Is there a different property that can be used to set SameSite or can we use one of the existing?
name: 'myCookie',
value: 'myValue',
domain: 'some domain',
origin: 'some origin',
path: '/',
version: '1',
expiration: '2015-05-30T12:30:00.00-05:00'

@apinkhasov You can add SameSite to the Cookie object when you set
CookieManager.set({
  name: 'myCookie',
  value: 'myValue',
  domain: 'some domain',
  origin: 'some origin',
  path: '/',
  version: '1',
  expiration: '2015-05-30T12:30:00.00-05:00',
  SameSite: 'None'
});

However, this is not reflected in the type file. I'll take this issue to support that. Let me know if this works!

Adding SameSite to Cookie object didn't work. When do you think type file will be updated? I'm not sure if passing new property without changing code to handle it would work.

Hello, I have the same question regarding Secure and HttpOnly cookie flags.

A workaround could be to use setFromResponse(), you can probably set any cookie flag you want that way (Secure, SameSite, HttpOnly...):
CookieManager.setFromResponse(
  'http://example.com',
  'user_session=abcdefg; path=/; expires=Thu, 1 Jan 2030 00:00:00 -0000; SameSite=Lax')
    .then((res) => {
      // `res` will be true or false depending on success.
      console.log('CookieManager.setFromResponse =>', res);
    });


Custom name section isn't that custom

The web assembly specification points out that "name" is a custom section, yet it is also defined, including the subsections. This is directly mapped to the text format and implementations rely on this knowledge for round-tripping and debug information.
Right now, we leave "name" as a custom section because wasm.Module is defined needing to be the binary representation. OTOH, binary is only one representation, there's also text and the abstract representation. Moreover, implementors are not required to name types exactly to the spec. In other words, we can choose to top level the type in a way that helps including in round-tripping from the text format as well any future debug information.
Aside: Being flexible where it helps implementation isn't uncommon, even in standard implementations. For example, the %.wat parser is actually the wast parser in Wasm-tools, for convenience. That said, this doesn't mean declaring a type for the representation of the name section ends up more useful than decoding it each time, either!

A good reason to do this is it prevents a potential encoding problem from being unknown until Instantiate. Right now, for example, the custom name section is decoded as it is helpful when building function instances.
	functionNames, _ := module.DecodeCustomNameSection()
	if functionNames == nil {
		// We cannot guarantee the existence of "name" custom section
		// in the binary. That is because the custom section is optional
		// in the spec. Also, some compilers optimize it out to reduce
		// the binary size.
		functionNames = map[uint32]string{}
	}

It makes less sense to defer this as the decoding outcome could happen at the same time as everything else (in DecodeModule). It is only that we don't have a place to store the names that this awkwardness persists.
The easiest way would be to allow either names to be attached to their corresponding types, or an optional struct in wasm.Module that holds the names and indexes used later like ^^


[CMT-794-1144] Update en.md - Newsletter 41 - spanish - new procedure - RM3

Description

Please include a summary of the change and which issue is fixed.
Please also include relevant motivation and context.

This pull request ...
Fixed issue

Please indicate the fixed issues with this exact format Fixes #232 where 232 is the number of the issue. This will trigger an auto-close if the issue when this PR is merged.
Supported keywords:
Fixes #1,#2,#3
close #1, #2, #3
fix #1 #2 #3
resolve #1,#2 #3
Resolves: #1,#2,#3
closed : #1, #2, #3

Fixes #(issue)
Type of change

Please delete options that are not relevant and check the box.

[ ] Add a new article/page
[ ] Fix a Typo
[ ] Add a new translation
[ ] Other

Resources

Any screenshots, links or relevant resources to explain better the changes.

Your translated the english file you need to make a new file called es.md in the same folder and add you translations there. Copy your translation, close this pr, then make a new pr.

https://github.com/yearn/yearn-comms/pull/1158 let me know if is ok
On Tue, Mar 15, 2022 at 3:14 AM Dark Ghosty @.***>
wrote:

Your translated the english file you need to make a new file called es.md
in the same folder and add you translations there. Copy your translation,
close this pr, then make a new pr.
—
Reply to this email directly, view it on GitHub
https://github.com/yearn/yearn-comms/pull/1144#issuecomment-1067489159,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIKGRB6FXXUETTTVXHCQ5SLU77XAPANCNFSM5QMPIXVQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Usage of a LET variable in a FILTER prevent usage of underlying indexes

Hello,
Using latest 3.5.x and 3.4.x series, a (yet constant) LET variable in a FILTER clause prevent usage of underlying indexes by the engine.
Ie:
LET test = document("test/123")
return LENGTH(FOR c IN demo FILTER c.reference == test._key RETURN 1)

Will not use an index on reference in the collection demo while the following query will use the same index:
return LENGTH(FOR c IN demo FILTER c.reference == '123' RETURN 1)

I guess the engine discard the index because the test variable could change (even if it doesn't), is there a way to declare this variable constant to let the engine keep benefit from the index on the reference field of the demo collection in this case?
I can provide a SSCCE if needed.
Many thanks in advance.

Hi @soualid, thanks for the report.
Note that 3.4 is EOL: https://www.arangodb.com/eol-notice/.
I cannot reproduce your problem with 3.5.6. Which exact version are you using?
Query String (86 chars, cacheable: false):
 LET doc = DOCUMENT('col/139')
 RETURN LENGTH(FOR d IN col FILTER d.i == doc.i RETURN d)

Execution plan:
 Id   NodeType          Est.   Comment
  1   SingletonNode        1   * ROOT
  2   CalculationNode      1     - LET doc = DOCUMENT("col/139")   /* simple expression */
  8   SubqueryNode         1     - LET #2 = ...   /* subquery */
  3   SingletonNode        1       * ROOT
 11   CalculationNode      1         - LET #8 = true   /* json expression */   /* const assignment */
 12   IndexNode            1         - FOR d IN col   /* persistent index scan, scan only */
  7   ReturnNode           1           - RETURN #8
  9   CalculationNode      1     - LET #6 = LENGTH(#2)   /* simple expression */
 10   ReturnNode           1     - RETURN #6

Indexes used:
 By   Name                      Type         Collection   Unique   Sparse   Selectivity   Fields    Ranges
 12   idx_1680424634026033152   persistent   col          false    false       100.00 %   [ `i` ]   (d.`i` == doc.`i`)

Best,
Tobias

Thanks Tobias, I tested this behaviour under 3.5.5-1.
I will check under 3.5.6 right now and give feedback here afterward.

I am reproducing the issue under 3.5.6, I create a SSCCE.

Here it is, but it doesn't reproduce the issue. I think it is related to indexes migration from older version of the engine, I'm checking this out, the good news is that a freshly created collection and indexes handle correctly this use case.
db._useDatabase('_system')
db._dropDatabase('repro')
db._createDatabase('repro')
db._useDatabase('repro')
db._drop('reproCollection')
db._createDocumentCollection('reproCollection')
db.reproCollection.ensureIndex({fields:['reference.id'], type: 'hash', unique: false})
db.reproCollection.insert([
  {
    "reference": {"id": 123}
  },
  {
    "reference": {"id": 123}
  },
  {
    "reference": {"id": 456}
  }
])
db._drop('reproAnotherCollection')
db._createDocumentCollection('reproAnotherCollection')
db.reproCollection.insert([{
	_key: "123"
}])
db._explain(`LET doc = DOCUMENT('reproAnotherCollection/123')
FOR r IN reproCollection FILTER r.reference.id == doc._key
RETURN r`)

Properly use the index:
Query String (116 chars, cacheable: false):
 LET doc = DOCUMENT('reproAnotherCollection/123')
 FOR r IN reproCollection FILTER r.reference.id == doc._key
 RETURN r

Execution plan:
 Id   NodeType          Est.   Comment
  1   SingletonNode        1   * ROOT
  2   CalculationNode      1     - LET doc = DOCUMENT("reproAnotherCollection/123")   /* simple expression */
  7   IndexNode            1     - FOR r IN reproCollection   /* hash index scan */
  6   ReturnNode           1       - RETURN r

Indexes used:
 By   Name                      Type   Collection        Unique   Sparse   Selectivity   Fields               Ranges
  7   idx_1680433618798772224   hash   reproCollection   false    false        75.00 %   [ `reference.id` ]   (r.`reference`.`id` == doc.`_key`)

Functions used:
 Name       Deterministic   Cacheable   Uses V8
 DOCUMENT   false           false       false

Optimization rules applied:
 Id   RuleName
  1   use-indexes
  2   remove-filter-covered-by-index
  3   remove-unnecessary-calculations-2

I can confirm that recreated the index solve the issue, it was migrated from previous versions of ArangoDB and was still a hash index and not a persistent one.
Maybe the --database.auto-upgrade procedure should take care of this and force index migration / recreation?

Hi,
in the rocksdb storage engine hash/skiplist are only aliases for persistent; Support for the mmfiles-Storage-engine has been dropped with ArangoDB 3.7

Hi @dothebart I have no clue on how this happened on this database (even if we do have changed the storage engine from mmfiles to rocksdb when migrating from 2.x to 3.x years ago).
Maybe the index was corrupted somehow (but I don't explain why it was used when not using a LET variable).
Anyway, recreating the index solved the issue, which is now always a pleasure now that they can be created in the background. 😄


{WIP} Release version 2.0.0

Just testing some things out... Closing so folks don't get the wrong idea 😉

Just testing some things out... Closing so folks don't get the wrong idea 😉

I was going to celebrate with an emoji 🎉


fix contextMenuHidden link

fix contextMenuHidden link

Do we need to apply the same fix to the docs/ variant?

yes, I was looking for master doc but couldn't find one

It's in the docs/ folder. I can see that version has the same mistake: https://github.com/facebook/react-native-website/blob/master/docs/textinput.md

Alright, fixed.


Graphql error on the template

What is the location of your example repository?
template repo
Which package or tool is having this issue?
Hydrogen
What version of that package or tool are you using?
1.0.5
What version of Remix are you using?
1.15.0
Steps to Reproduce
In the template created open app/routes/($lang).products._index.tsx, on the line 157, in const ALL_PRODUCTS_QUERY you're going to find a warning: Syntax Error: Unexpected <EOF>.GraphQL: Syntax.
This error is present on basically all queries that concatenate strings from other variables.

Expected Behavior
No warning or error is show
Actual Behavior
Shows ``Syntax Error: Unexpected .GraphQL: Syntax.

I haven't dug deeply into it, but it appears to be an issue with the GraphQL Plugin for our IDEs. The query still works, but the GraphQL plugin struggles with the syntax.
For example: https://github.com/graphql/graphiql/issues/1842#issuecomment-700400645
We could fix it by putting the fragment at the end of the query, instead of at the beginning.


ASR Mobility Agent missing

We have ASR deployed with private endpoint, as per MS article we need to manually update all agents but latest agent installaton file is missong on source E:\Software\agents on config server. I have already updated config server to lates version. From where I can download the latest mobility agent version?
https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview#prerequisites-1

@mzafzal790
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!

@mzafzal790 It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!

Hi @TPavanBalaji - I have updated my query with link I am following.

Hi @TPavanBalaji - I have updated my query with link I am following.

@mzafzal790
Instead of downloading latest version, you can automatically upgrade it to the latest version whenever the new version releases. Please follow this article, it shows how to upgrade to latest version automatically.

@mzafzal790 Instead of downloading latest version, you can automatically upgrade it to the latest version whenever the new version releases. Please follow this article, it shows how to upgrade to latest version automatically.

Hi @TPavanBalaji, we are using private endpoint, When you enable private endpoints, automatic updates won't be available. You need to manually update mobility agent using command line.

When you enable private endpoints, automatic updates won't be available. You need to manually update mobility agent using command line.

@mzafzal790
As mentioned in the article, if you are using private endpoints, automatic updates are blocked for the protected machines. Make sure to use a new Azure Site Recovery replication appliance when you set up Site Recovery on your machine.

@mzafzal790
Thanks for your feedback and your contribution to Azure docs.
Feedback for this repository is moving away from GitHub to a system specific to the Microsoft Learn platform. Issues for this repository will soon be disabled, and additional comments from GitHub will no longer be possible. However, we are now tracking and triaging this issue in the new feedback system.
To learn more about our feedback systems, please see Provide feedback for Microsoft Learn content.

@mzafzal790
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

I'm having same issue with latest Rollup 76 update and private endpoint with no updated mobility clients found, did you ever figure it out?


How to suppress the Perfetto sidebar when opening a file?

The sidebar is open when there is no content loaded, and also every time that I load a new file from my tool, this re-opens.  I don't really need the "open trace file", since my app is opening the traces.   Also these popups don't work without more work on WKWebView to allow them.
If someone needs the Query/Viz/Metrics, then the hamburger menu can pop it back open.   I'm trying to look at profiles across all of clang, and it's a lot of trace files.  So having to constantly collapse that side-bar isn't ideal for the user.
Seems like there are commands to suppress it, but these are only registered after a trace is loaded.  I want to post a "perfetto" object, and have the side-bar remain suppressed.  Eventually I'll even make my file list a popover, so it doesn't wasted profiling real-estate.
The idea here is to have a consistent timeline scale as you look across all files, sort the ones to the top that are the worst offenders, etc.

You can pass hideSidebar=true in the URL to suppress the sidebar entirely: https://ui.perfetto.dev/?hideSidebar=true This hides the sidebar forever (you can't bring it back) which is how the UI is used by some folks who embed it as a component (as done by Flutter devtools)

Again, perfect!  Thanks for the responses.  The tool is looking much more usable now.


New version: ThaUnknown.Miru version 5.0.11

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

No errors to post.

(Automated response - build 876.)


Error when running

When i try to run this is what i get

what does your config.json look like?

Most probably he kept the 2nd element of botToken array as it was in config.json file.
By the way I haven't executed this program yet, was looking at your code. Nice work! This code smells good, Simple, Clean and easily readable code! I was feeling like reading my own codes.

what does your config.json look like?
{
"botToken": "TOKEN"
"prefix": "/"
}
exactly that but the TOKEN is my actual token

what does your config.json look like?
{
"botToken": "TOKEN"
"prefix": "/"
}
exactly that but the TOKEN is my actual token

Put a comma (,) after your token:
{
"botToken": "TOKEN",
"prefix": "/"
}

@Perditrix mystcuro is correct, you need the comma at the end of the botToken line. Please let me know if this resolves your issue :)


Fixed an error with a very short video file.

The following URL is a sample of problematic videos.

https://drive.google.com/open?id=0B_7NjEtAkMGselZOa2JrOENfVXM

Swapped the order of skip_frame and read_frame.
Removed next_frame_func which is no longer used.

dhcp44-80:~ hasegaw$ python3 test.py
self.lock.acquire
self.lock.release
dhcp44-80:~ hasegaw$ cat test.py
def hoge():
    try:
        print('self.lock.acquire')
        if False:
            return None

    finally:
        print('self.lock.release')

hoge()

dhcp44-80:~ hasegaw$ python test.py
self.lock.acquire
self.lock.release
dhcp44-80:~ hasegaw$

You're right. I didn't know that!


Wrong address in registry when loading .aasx files

Hi there,
I've noticed that when I load in .aasx files a part of the URL for submodels on the registry server is wrong. To be precise, it seems that the "shells" part in the URL is missing.
For example it shows like that:
http://localhost:4001/aasServer/DemoAAS_iD/aas/submodels/DemoSubmodel/submodel
where as the correct form should be:
http://localhost:4001/aasServer/**shells**/DemoAAS_iD/aas/submodels/DemoSubmodel/submodel
The code that I use to load .aasx files is this one:
AASXPackageManager aasx_packman = new AASXPackageManager("C:/blub/demo_aas.aasx");

Set<AASBundle> bundles = aasx_packman.retrieveAASBundles();

AASBundleHelper.integrate(new AASAggregatorProxy(AASSERVERPATH), bundles);

AASRegistryProxy proxy = new AASRegistryProxy(REGISTRYPATH);
AASBundleHelper.register(proxy, bundles, AASSERVERPATH);

I'm not sure if I did something wrong or if it is a bug.
Best,
Samed

I recently stumbled across the same thing.
The AASAggregatorProxy doesn't want the AAS server path but the AAS Aggregator path, which includes the /shells:
http://localhost:4001/aasServer/shells in your example.
See this example line 47

Many thanks for pointing this out. The AASRegistryProxy checks for existence of this /shells suffix and adds it, if necessary. However, the AASBundleHelper does not contain this failsafe logic. Thus, the described behavior is exposed.
We will add the failsafe logic to the AASBundleHelper to create a consistent handling of paths.
I'll update this ticket accordingly.

Your remark is addressed in https://github.com/eclipse-basyx/basyx-java-sdk/pull/42 and will be included in the upcoming 1.1 release.
Many thanks again for pointing this out!


Make it easy to open a documentation bug from the docs themselves

Fixes #98.
A typical "Report an Issue" button will link to:
https://github.com/GoogleCloudPlatform/gcloud-python/issues/new?title=[Documentation+Issue]+&body=Page+Name%3A+datastore-api
Release%3A 0.4.1
The release in the link will either be a stable release (as in http://googlecloudplatform.github.io/gcloud-python/0.4.1/index.html) or will be a commit hash (as in http://googlecloudplatform.github.io/gcloud-python/master/)
(The "release" may need some URL escaping.)

I took a stab at handling the media queries for devices with not-so-wide screens.
Under 50em we have:

and above (hopefully the default experience for people actively coding) we have:

Coverage remained the same at 100.0% when pulling 0f237b9cc02000f6c585578f0b9d518f9cc62444 on dhermes:fix-98 into 0e41dc35455da7f01e69cd9bdfb2969c12defcf5 on GoogleCloudPlatform:master.

Coverage remained the same at 100.0% when pulling d95dd4750f27a815f648742c069dac8e4eb89c35 on dhermes:fix-98 into 0e41dc35455da7f01e69cd9bdfb2969c12defcf5 on GoogleCloudPlatform:master.

LGTM

https://travis-ci.org/GoogleCloudPlatform/gcloud-python/builds/52161440 (build 1192) has finished but still shows as pending due to https://twitter.com/traviscistatus/status/570637064019914752
Going to merge this now


check whether comparator is a function

check whether comparator is a function

@Tong-Huang this will fail silently,  I'd rather it throw/fail explicitly if comparator is not a function

@dcousens ok, I agree with you.