udpate/delete  with routing key in parentheses not supported

I encouter a problem, udpate/delete  with routing key in parentheses not supported.
for example I have a table messages with route key page, sql like this : delete from messages where page = 1 is ok, but delete from messages where (page = 1) is not supported (unsupported: multi-shard where clause in DML).
I use third party client which generate sql like where (page=xxx) and (xxx) and ...., Is there any other suggests to resolve this problem?

This new PR should address your use case.
Changing splitAndExpressions wouldn't have helped the above use case because the DML analyzers don't use that function. Also, the analysis of where and having clauses already drill down into parenthesized expressions. So, it wouldn't have helped there either.
In this fix, I've changed it such that the analyzers drill down instead of stripping parenthesis from the AST. So, this should overall work out better.

yes, it works well, thank you !


Use py-bcrypt not bcrypt by default

Use py-bcrypt not bcrypt by default, so as to not make flask-user depend on python development headers and a C compiler and FFI etc

Is this waiting on anything?

@revmischa : py-bcrypt (a while back) seems to have some security issues, and bcrypt was recommended. See https://github.com/lingthio/Flask-User/issues/82


Add Visibility for UpdateHandle

This PR adds support for setting the visibility of uploaded UGC files. The newly implemented enum may find implementation in a couple more spots, though I didn't check that.

Also added a missing function for setting metadata of an item.


Add full breadcrumb

Context
Models => Model has breadcrumb support, the prediction page should continue to use this norm:
Actions:

[x] Update Prediction Component to use breadcrump as title

vs.

Example of Fix:
Models > Alpha Retrain > v1.0.0

or

Models > 12 > v1.0.0

cc/ @martham93
Ref: https://github.com/developmentseed/ml-enabler/issues/47

nice looks good cc @ingalls


[todo-mvp] Ensure generic type at BaseView is a BasePresenter

Ensure generic type at BaseView extends BasePresenter.

@JoseAlcerreca any updates on this?

@florina-muntenescu, @JoseAlcerreca any updates on this?

I don't have strong feelings about it. Anyone else?

@JoseAlcerreca, technically you could implement a presenter that does not implement the BasePresenter interface and it would not violate the presenter-view contract.
Thus, if the method stop be added to BasePresenter (or any other change), no compilation error would be detected.

Yeah, but if the stop method is ever called, there would be a compilation error.


[DO NOT MERGE] Do not disable italic text

I did some investigation, and this will affect 2974 editions in the live content store.  A bit of break-down:
   9 /aaib-reports/
   1 /corporation-tax-rates
 443 /dfid-research-outputs/
   2 /drug-device-alerts/
   3 /drug-safety-update/
1790 /government/
  51 /guidance/
 672 /hmrc-internal-manuals/
   1 /individual-savings-accounts
   1 /junior-individual-savings-accounts
   1 /vat-rates

And the /government pages:
   2 /government/case-studies/
   1 /government/collections/
  25 /government/consultations/
   5 /government/fatalities/
1060 /government/news/
   2 /government/organisations/
 489 /government/publications/
 194 /government/speeches/
   1 /government/statistical-data-sets/
  11 /government/statistics/

There's a full list in the trello card.

Component guide for this PR:
https://govuk-publishing-compon-pr-487.herokuapp.com/component-guide/

Trello card

Marking this as [DO NOT MERGE] until someone has said the effects are fine.

@barrucadu any updates on this?

@alex-ju We got an update yesterday on this, looks like italics is still forbidden:

This went back to content 'style council' and the leads agreed that, based on all the findings, it wouldn't be acceptable to allow italics.
We shared the findings with the department which is primarily interested in including italics in the style guide (and therefore 'switching them on' in Whitehall) - I think it's helped to show them the myriad reasons we're saying no.


fix(estree/compat): Adjust loc.col

Description:
Minor update to compat translation to the loc to match with what acorn does.

Testing for bindings are failing with version conflict? 🤔


CRUNCH-677 Source and Target accept FileSystem

The change to Source, Target, and SourceTarget obviously breaks compatibility for implementors of these interfaces as we're still building against Java 7 so I can't provide a default implementation for these new methods.
Also, there is an expectation that Target implementations will need to update the asSourceTarget() method to copy the FileSystem along.

Merge mistakes are now fixed and build is passing.


The problem of camera parameters

Hello, thank you for your excellent work！
I am a beginner of 3D reconstruction，There are some doubts when reading your code
class OptimzeCamLayer(nn.Module):
    def __init__(self):
        super(OptimzeCamLayer, self).__init__()

        self.img_res = 500 / 2
        self.cam_param = nn.Parameter(torch.rand((1,3)))

    def forward(self, pose3d):
        output = pose3d[:, :, :2] + self.cam_param[None, :, 1:]
        output = output * self.cam_param[None, :, :1] * self.img_res + self.img_res
        return output

def get_model():
    model = OptimzeCamLayer()

    return model

Why are camera parameters random and how can they work correctly？
Hope to get your answer, thank you

Hi @moondabaojian,
First, Pose2Mesh does not use that module (OptimizeCamLayer). Pose2Mesh is fully supervised by 3D groundtruth and there is no 2D loss.
Second, I tried to use the module for the visualization purpose, but I noticed that it tend to downgrade the performance. So I just removed it. Now, the visualization (mesh overlay on images) is done by iterative fitting as you can see in the demo codes.
Last, the module (OptimizeCamLayer) has learning parameters and the randomness is just an initialization.

Thank you for your quick reply！I've got it
In addition, I have a puzzle about camera parameters，When I try to reconstruct 3D human body based on graph convolution（like GraphCMR）,I found that some dataset networks can learn the correct camera parameters, but some can't.
Especially scale in camera parameters, It makes me confused, Can you give me some advice?
Thank you!

Hmm... Could you clarify what 'dataset networks' indicate?
Anyway, I think learning camera parameters by graph convolution is not a good idea. Graph convolution exploits the topology of a mesh or a skeleton but the camera parameters are nothing to do with the topology. Simple fully connected layers will be enough.

Thank you for your reply
There are some mistakes in my statement，I mean, when learning camera parameters, my network works on some datasets and some don't
In addition, what kind of data do you think should be input into the full connection layer, to learn camera parameters

Hi @moondabaojian

If the scale or the location of human in the cropped image is inconsistent, the network may fail.  In general, most of the 3D pose estimation methods learn 'pseudo' camera parameters. Regardless of whether they are based on weak-perspective or pin-hole projection, the target camera parameters are just fitting an estimated 3D pose to a 2D pose from the cropped image (ex. 224x224). In other words, I think the network is trying to memorize(?) or learn some kind of 3D pose and 2D pose pairs and thus similar 3D poses should have similar 2D poses in the cropped image.

The data can be either 2D pose or image feature. For 2D pose case you can check RepNet. For image feature case, you can check HMR or SPIN.

Thank you for your reply. Your suggestion is very helpful to me
The following is a screenshot of the training process

Can this be caused by improper data preprocessing？（Although sc has been increasing, it is very slow）

Hi @moondabaojian,
Happy New Year!
I am not sure, but that kind of result can occur even with the proper data preprocessing.
I observed similar phenomenon when 2D loss kept increasing while 3D loss kept decreasing.
The average 3D test error (mm) was reasonable, but the scale of projection tend to appear weird when the target pose was difficult as in your example.

Hi @moondabaojian,
Happy New Year!
I am not sure, but that kind of result can occur even with the proper data preprocessing.
I observed similar phenomenon when 2D loss kept increasing while 3D loss kept decreasing.
The average 3D test error (mm) was reasonable, but the scale of projection tend to appear weird when the target pose was difficult as in your example.

Happy New Year! Thank you for your answer
I'm taking your 'loss_edge_length' added to my program,but training error
Break in ' U, S, V = torch.svd(A[i])'
'RuntimeError: Lapack Error gesdd : 2 superdiagonals failed to converge'
There is no error in calculating 'loss_edge_length', only when it is added to total loss, an error will be reported

Happy New Year! Thank you for your answer
I'm taking your 'loss_edge_length' added to my program,but training error
Break in ' U, S, V = torch.svd(A[i])'
'RuntimeError: Lapack Error gesdd : 2 superdiagonals failed to converge'
There is no error in calculating 'loss_edge_length', only when it is added to total loss, an error will be reported

Hi @moondabaojian,
Using the edge loss at the beginning of the training could lead to extreme local optima, and actually I used the loss after several epochs for that reason.
I recommend you also to add the edge loss after sufficient training.

Hi @moondabaojian,
Using the edge loss at the beginning of the training could lead to extreme local optima, and actually I used the loss after several epochs for that reason.
I recommend you also to add the edge loss after sufficient training.


Fix and update wiki pages

We are now using the GitHub pages (https://princetonuniversity.github.io/STELLOPT/) as the official site for hosting all the wikis and documentation.
I have converted all the wikis into markdown format, but most of them need to be minorly fixed. Incompatibilities are found such as,

[ ] Tables, code snippets, etc need revisions
[ ] Equations should be fixed.
[ ] Table of Contents needs to be inserted.
[ ] Links are broken and other issues.

Besides, some contents need to be updated, such as compiling instructions.
All the markdown source files are stored in the branch gh-pages. I have created a project at fix the wikis to track the progress.
Everyone is welcome to contribute. For more information, please view README.md.

Excuse me,I have see the [DESCUR] code and the [NMORPH] code in VMEC wiki,but there are neither in the release version.how cloud i use those 2 code.also,there are some code appear in github,but  not in the VMEC wiki.

@lazersos might know the history.

Much of the wiki precedes the existence of the git repository.  NMORPH is maintained by Michael Drevlak at IPP.  If you wish to use that code please contact him.
DESCUR can be found in the DESCUR branch, but it no longer part of the public release of STELLOPT because it uses routines which are not technically open source.


Housekeeping updates

Just cleaning up the config scripts a bit.

90% of the reason for doing this is because right now Travis is showing:

because we have Travis builds enabled for non-master branches.

And this won't disable Travis for v0.13.x, because Travis looks at the .travis.yml on the pushed branch, not the one on master.

Wait - I'm definitely not okay with reverting this PR wholesale; it wasn't just the ES6 usage on the config files. The Karma setup made the debug info from normal test runs useless because it was instrumenting everything with the coverage data here. The corresponding reversion on the history side also took out all of the coverage reporting there.
I'm as much a fan of reasonable config as anyone, but nuking actual fixes for the sake of merging karma.conf.babel.js into karma.conf.js is not good!

Can you make another PR that only includes the coverage fixes?
On Tue, Nov 10, 2015 at 5:08 PM Jimmy Jia<EMAIL_ADDRESS>wrote:

Wait - I'm definitely not okay with reverting this PR wholesale; it wasn't
just the ES6 usage on the config files. The Karma setup made the debug
info from normal test runs useless because it was instrumenting everything
with the coverage data here. The corresponding reversion on the history
side also took out all of the coverage reporting there.
I'm as much a fan of reasonable config as anyone, but nuking actual fixes
for the sake of merging karma.conf.babel.js into karma.conf.js is not
good!
—
Reply to this email directly or view it on GitHub
https://github.com/rackt/react-router/pull/2492#issuecomment-155583252.

In general we should keep PRs as small as possible. Fixes shouldn't be in a PR titled "housekeeping".

I think we actively want ES6 for the Karma config for adding coverage. Specifically stuff like https://github.com/rackt/react-router/blob/v1.0.0/karma.conf.babel.js#L136 is a lot cleaner and easier to read than the ES5 equivalent.
I didn't cut it over to Babel just to replace require and var with import and const.

Jimmy, you keep saying that. I'm saying that I don't want two files for
doing one thing. It's just syntax.
I appreciate the contributions you've made to the router, really I do. But
you don't need to fix stuff that isn't broken. In this case, it's just a
matter of preference.
On Tue, Nov 10, 2015 at 5:22 PM Jimmy Jia<EMAIL_ADDRESS>wrote:

I think we actively want ES6 for the Karma config for adding coverage.
Specifically stuff like
https://github.com/rackt/react-router/blob/v1.0.0/karma.conf.babel.js#L136
is a lot cleaner and easier to read than the ES5 equivalent.
I didn't cut it over to Babel just to replace require and var with import
and const.
—
Reply to this email directly or view it on GitHub
https://github.com/rackt/react-router/pull/2492#issuecomment-155586826.

I'm fine with that, and we can resolve those separately.
I don't have time to manually port the Karma config over from ES6 to ES5 right now. Are you okay with adding back the rest of the changes per my new PRs and treating moving the config code back to ES5 as a separate issue?
The PR actually did address real misconfigurations that I think we do care about, like the Karma debugger being unusable for the tests because of the instrumentation from isparta. I can take some time later to cut the configs back over to ES5, but reverting the entire PR throws out a lot more baby than bathwater.

Part of the problem here is that when you changed the whole file it made it
really difficult for me to see which pieces were actually new stuff and
which pieces were just syntax/style. I spent the better part of a week a
few months back getting our testing infrastructure setup from end to end
(it's not easy, and there aren't a lot of great examples out there to
follow), and every decision that I made was intentional: the # of files,
their extensions, the syntax we used, etc.
Honestly, I'm fine with coverage being broken until we can get a PR that
only adds back just the coverage fixes. coverage isn't a bug in the code.
It's not essential. If there are other issues with debugging in Karma,
let's address those in a separate issue. But if we change a bunch of stuff
that wasn't broken in the same PR it makes it very difficult for me to
follow.
On Tue, Nov 10, 2015 at 5:32 PM Jimmy Jia<EMAIL_ADDRESS>wrote:

I'm fine with that, and we can resolve those separately.
I don't have time to manually port the Karma config over from ES6 to ES5
right now. Are you okay with adding back the rest of the changes per my new
PRs and treating moving the config code back to ES5 as a separate issue?
The PR actually did address real misconfigurations that I think we do care
about, like the Karma debugger being unusable for the tests because of the
instrumentation from isparta. I can take some time later to cut the configs
back over to ES5, but reverting the entire PR throws out a lot more baby
than bathwater.
—
Reply to this email directly or view it on GitHub
https://github.com/rackt/react-router/pull/2492#issuecomment-155589077.

I don't really care about whether the configs are in ES5 or ES6. Personally I feel a twinge of annoyance at not using template strings for patterns like https://github.com/rackt/react-router/blob/0fabc18fdfa317ef85f54ec4d7c086d9f6d38b3b/karma.conf.js#L109, but that's not important.
My issue is that I don't think it makes sense to directly back out a PR that was also signed off on by another member of the project - this wasn't a stack of commits I just pushed directly to the repo, and it had already gone through review.
I also intentionally submitted both this and the corresponding history PR as individual PRs with multiple commits because that seemed the best way to present this data - it's a number of small updates to config scripts, and would have just contributed to noise had they been submitted as separate PRs. Within the PR itself I've taken pains to make each of the commits as atomic and clear in its intention and action as possible.
I agree that coverage isn't the most important thing in the world, but e.g. on React Router, the Karma config to which you've reverted makes it very difficult to debug tests running locally because the tests are always run against code with coverage instrumentation. I also think that both coverage and being able to debug tests in Karma are worth more than ES5 v ES6 for config scripts.
I'm willing to take the time to move the configs back to ES5, but I feel that the reversion leaves both repos in a worse state in terms of code quality overall.


pip guides, docs devshell fix

[X] pillow example
[X] python-local-development example
[ ] devshell with editables
[ ] editables options docs
[ ] pdm example & comparision
[ ] more elaborate flattenDependencies option docs

@purepani For some reason, I can't select you as reviewer here, but this might be of interest to you :)


Warning about missing .gitignore despite not missing

stryker init in $gitWorkingCopyDir/someSubDir/
stryker seems to expect to be executed in the repository root, next to .gitignore, or have a local .gitignore available.
Ideally it should use the same logic as git (look in parent directories for file) AND if not found, just create a .gitignore file in the current directory. It is valid to have multiple ignorefiles in subdirs in git.

Yeah, I agree it would be helpful, however, it now works as intended. The warning specifies that you can add it yourself:

No .gitignore file could be found. Please add the following to your .gitignore file: *.stryker-tmp


Feature for auto commenting on a new issue creation

I would like an automated feature that posts a predefined comment on an issue as soon as it is created. This feature aims to address the problem of delayed and inconsistent communication following the creation of issues. By automatically commenting on issues as soon as they are created, it ensures that contributors receive immediate feedback and acknowledgment for their efforts. This fosters a positive and supportive environment for collaboration, encouraging continued participation and engagement from contributors.
Could you please assign me this issue under GSSOC'24.

Can you please explain more on what types of comments will be there?

@suhanipaliwal can you show me up that with some short video how it works and what types of comments will it raise up ?

I will be adding a YAML file in the .github/workflows directory which will add the feature of auto commenting as soon as a new issue created. Whenever a new issue will be made, this comment will be added immediately on the issue.

Cool, Go ahead


Document follow-up attributes

It seems like
#[distributed_slice(FOO)]
#[linkme(crate=::mycrate::linkme)]
static BENCH_DESERIALIZE: fn(&mut Bencher) = bench_deserialize;

causes distributed_slice to refer to the linkme crate as ::mycrate::linkme.  But, I don't see this documented anywhere.  I don't quite understand it well enough to write those docs myself :)

Would definitely appreciate this being documented -- I spent a bit of time trying to find another solution before finding it. My use case was to to wrap linkme declarations with your own macro_rules macro to simplify this for users of an API and to do that you do need to re-write the paths -- I suspect this is a fairly common pattern.


Update init.py

Hi @sepehrmizani
Because you already submitted a more descriptive pull requests on the quite similar changes
I'm going to close this one so we proceed with discussion on the latest pull request you submitted
Thanks for taking your time to contribute, Highly appreciated
Best
Kalebu


Minor change to the test package name

Minor change to allow vim-go to appropriately locate the package github.com/ant0ine/go-json-rest/rest/test

Interesting, but this is a breaking change. So, I tagged it with "v4 idea"

@ant0ine
Out of curiosity what makes this a breaking change?
Also, do you have any suggestions on how to make this a non-breaking change?
Thanks,
-Dom

@domthinks "test" is a public package used by developers to test their APIs. Changing the name of the package would break their code.

I'm gonna close this PR since it's a breaking change.


[App] Completely messed up style on Microsoft Edge

Also, the entirety of the middle and right panes aren't loading at all.

I was unable to reproduce this on windows + edge. @ShimonD-KlimaDAO are you still seeing this?

Almost a year old, have not seen any recent user reports about this. Closing.


[CARBONDATA-3446] Support read schema of complex data type from carbon file folder path

Backgroud:
SDK can't read schema of complex data type from carbon file folder path
Support:
Support read schema of complex data type from carbon file folder path

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

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

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3649/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11923/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3859/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3652/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3862/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11926/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/17/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/543/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/546/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/544/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1269/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/1248/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1258/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/29/

Build Failed  with Spark 2.4.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/492/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/943/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2653/

@jackylk Please review it

@Indhumathi27 optimized, please check it again.

@jackylk Please review it.

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1180/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2896/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1181/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2897/

LGTM


Decoding 1310-byte-long image takes more than 5 seconds

Found in scheduled fuzzer run (https://github.com/tirr-c/jxl-oxide/actions/runs/8006838200)
timeout-3fa7ec41070fd2afbf6b0b9636a8d7eda19bc008.gz

Slow decoding is tracked at #239.


Add recap status.

Closes #984

Coverage increased (+0.01%) to 79.066% when pulling bfa9a298977e4adc9f1ccf37a87c1e1db1ff29c1 on scsb_controller_item_stauts into a2f23742e96075b59f093df25bf9ffadea0b6779 on alma.

Coverage increased (+0.01%) to 79.066% when pulling bfa9a298977e4adc9f1ccf37a87c1e1db1ff29c1 on scsb_controller_item_stauts into a2f23742e96075b59f093df25bf9ffadea0b6779 on alma.


Update README.md

Updated ReadMe for readability and to link the DOI and associated directories.

Relates to #2 (1st Task)


pick pick #41310 #41969

What problem does this PR solve?
pick #41310 #41969
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


Update favicon

Noticed during the demo that the default React favicon was still being used.
This PR changes it to the Github scroll emoji.

Updated yarn.lock to also close #113, #115 and #119


Unable to find version 'latest'

Describe the bug
When using the GH action w/ the following configuration, GH gives the error message
Getting action download info
Error: Unable to resolve action `dwardu89/aws-ssm-parameter-store@latest`, unable to find version `latest`.

To Reproduce
Steps to reproduce the behavior:
Configuration:
      - name: Add version to SSM parameter store
        uses: dwardu89/aws-ssm-parameter-store@latest
        with:
          ssm-path: ${{ inputs.DEPLOYMENT_VERSION_SSM_PATH }}
          ssm-value: ${{ env.PROJECT_VERSION }}
          aws-region: us-west-2
          ssm-value-type: "String"
          ssm-value-overwrite: true

Expected behavior
The SSM path is updated with the provided value
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Just need to update the readme with each new version, currently @v2.0.2


[AppService] Add az webapp|functionapp config ssl create-managed-certificate

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

Please add at least one test case

Unit test added - although it had to be mocked. It is dependent on a CNAME lookup.

Unit test added - although it had to be mocked. It is dependent on a CNAME lookup.

Why not use scenario test here?

Unit test added - although it had to be mocked. It is dependent on a CNAME lookup.

Why not use scenario test here?

As mentioned in our chat - because scenario test will not be able to handle the CNAME registration part that is necessary for a successful run. You will see the same pattern for e.g. setting domain name.

@madsd this feature is not supported only on SKUs Basic & above - so free & shared don't support this can you add a validation for this & throw an error - the API doesn't handle this currently but the FrontEnds block - so we need to handle this on CLI end, we do the same in portal. Thanks!

@madsd this feature is not supported only on SKUs Basic & above - so free & shared don't support this can you add a validation for this & throw an error - the API doesn't handle this currently but the FrontEnds block - so we need to handle this on CLI end, we do the same in portal. Thanks!

I added a check for Free and Shared, and will throw a CLI error if it is. I updated the unit tests to handle this.


fix: resolve promise when close event is fired for res

Hello,
this PR to change the "close" event handler from reject to resolve in order to make the promise end with no errors.
When a http requested is issued and then cancelled by the client the "finish" event is not triggered (https://nodejs.org/docs/latest-v16.x/api/http.html#event-close_1)
Thanks!

ping @giovanni-bertoncelli


starlark: reject dup keyword args in call to func with **kwargs param

Fixes #21

Oops, must stop force-pushing. This is not gerrit. :(

@alandonovan force pushing to a PR branch before a merge is fine. Did you want to maintain the old commits?

I was advised that GitHub code reviews are most intelligible if one pushes a sequence of commits and only squashed them when merging, rather than rewriting history on the review branch, as we do in the Go project's Gerrit workflow, so that it always appears as a single commit.


EOF Error during inference

I completed training with good results, and attempted to run the inference using this command:
nnUNet_predict -i D:\brats2021\nnunet_raw_data\Task005_prostate\imagesTs -o D:\brats2021\result\predictions -t 5 -m 3d_fullres -tr nnUNetTrainerV2BraTSRegions_DA4_BN_BD --save_npz

but am getting the following error:
starting prediction...
Traceback (most recent call last):
  File "\\?\C:\Users\jim\.conda\envs\pytorch_kaist\Scripts\nnUNet_predict-script.py", line 33, in <module>
    sys.exit(load_entry_point('nnunet', 'console_scripts', 'nnUNet_predict')())
  File "c:\users\jim\src\nnunet_kaist\nnunet\inference\predict_simple.py", line 217, in main
    predict_from_folder(model_folder_name, input_folder, output_folder, folds, save_npz, num_threads_preprocessing,
  File "c:\users\jim\src\nnunet_kaist\nnunet\inference\predict.py", line 658, in predict_from_folder
    return predict_cases(model, list_of_lists[part_id::num_parts], output_files[part_id::num_parts], folds,
  File "c:\users\jim\src\nnunet_kaist\nnunet\inference\predict.py", line 206, in predict_cases
    for preprocessed in preprocessing:
  File "c:\users\jim\src\nnunet_kaist\nnunet\inference\predict.py", line 109, in preprocess_multithreaded
    pr.start()
  File "C:\Users\jim\.conda\envs\pytorch_kaist\lib\multiprocessing\process.py", line 121, in start
    self._popen = self._Popen(self)
  File "C:\Users\jim\.conda\envs\pytorch_kaist\lib\multiprocessing\context.py", line 224, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "C:\Users\jim\.conda\envs\pytorch_kaist\lib\multiprocessing\context.py", line 327, in _Popen
    return Popen(process_obj)
  File "C:\Users\jim\.conda\envs\pytorch_kaist\lib\multiprocessing\popen_spawn_win32.py", line 93, in __init__
    reduction.dump(process_obj, to_child)
  File "C:\Users\jim\.conda\envs\pytorch_kaist\lib\multiprocessing\reduction.py", line 60, in dump
    ForkingPickler(file, protocol).dump(obj)
AttributeError: Can't pickle local object 'nnUNetTrainerV2_DA3_BN.initialize_network.<locals>.<lambda>'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Users\jim\.conda\envs\pytorch_kaist\lib\multiprocessing\spawn.py", line 116, in spawn_main
    exitcode = _main(fd, parent_sentinel)
  File "C:\Users\jim\.conda\envs\pytorch_kaist\lib\multiprocessing\spawn.py", line 126, in _main
    self = reduction.pickle.load(from_parent)
EOFError: Ran out of input
[W C:\cb\pytorch_1000000000000\work\torch\csrc\CudaIPCTypes.cpp:15] Producer process has been terminated before all shared CUDA tensors released. See Note [Sharing CUDA tensors]

The only thing I have to go on is something about can't pickle local object, which mentions a different trainer than the one I used. Is there any hint on what is going wrong here?

I have found out this is a Windows issue, so I am closing it.


suggested optimization: string literal embedding

Take a look at https://github.com/dsymonds/goembed/pull/1 — using string literals speeds up compilation massively. I’ll send another PR on goembed soon to reduce the size of the generated string literal.
Using the same techniques as the goembed PRs should do away with the resource blow-up you mention in your README.md.

go.rice already uses string literals. I've benchmarked both goembed and go.rice, the memory usage and elapsed time for a single, 80 megabyte file are quite similar.
rice embed-go:
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:06.37
Maximum resident set size (kbytes): 1988272

go build with file generated by rice:
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:04.19
Maximum resident set size (kbytes): 570256

goembed:
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:05.72
Maximum resident set size (kbytes): 7272

go build with file generated by goembed:
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:03.47
Maximum resident set size (kbytes): 624816

The only huge difference is the memory required by the rice command.

Did you also measure resident set size of the compiled program?

goembed:
Maximum resident set size (kbytes): 87232
rice:
Maximum resident set size (kbytes): 88312

The rice command uses that much memory because it reads every file into memory first, then generates the entire source code, then parses that and formats it (so it keeps three copies of the file contents in memory).

So, it looks like some optimizations are possible for the rice command itself.. Probably the first thing would be to make the embed command use streams instead of reading the whole file. I'm quite busy these days, if anyone could pick this up that would be great. It could be a while until I find the time to do so.

Closing this isue in favor of #92


uglifyjs depreciation breaks build

Based on this libs dependency on purifycss, uglifyjs depreciation breaks build. See:

https://github.com/purifycss/purifycss/issues/159
https://github.com/mishoo/UglifyJS2/issues/936#issuecomment-301620396

There's not much I can do about that in this plugin. Maybe better wait until Purify gets fixed.

@bebraw yup, agreed. I wanted to ensure it was reported and visible to others digging through dependencies of dependencies trying to work out the path to the original error 😃

https://www.npmjs.com/package/purify-css
Purify has been fixed & bumped to 1.2.1

@newtriks Can you close this issue once you check against the new version?

@bebraw yup 👍

I'm having the same issue, what is the recommended solution?

@rafaeleyng Which version of Purify are you using? I cannot fix the issue here but they published a fixed version.

I'm using:
  └─┬<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └──<EMAIL_ADDRESS>
I understand that they published a fixed version, but I'm not sure how to use that since my dependency of purify-css is through purifycss-webpack

@rafaeleyng try to use npm cache clear and reinstall node_modules

@rafaeleyng Ok, I think I'll push Purify as a peer dependency so you can specify the exact version.

Just pushed it to peer dependency. @evilebottnawi's advice is valid too but it's better to manage this through a peer.

@bebraw Are you going to make a npm release? I'm not sure what should I do

@rafaeleyng Already done. Does it still fail for you?

@bebraw I'm really confused now.
As shown in my comment above, I'm using<EMAIL_ADDRESS>I just checked https://www.npmjs.com/package/purifycss-webpack-plugin and the latest release there is 2.0.3. The link to the git repo in that page refers to this repo, but here the latest version (that was generated 2 hours ago) is 0.8.0. It seems to be 2 unrelated libraries, but the npm package links to this git repo. So I'm still clueless about what to do.
By the way, thank you for all the patience.

I just saw that this package also exists https://www.npmjs.com/package/purifycss-webpack, that seems to be the correct. Trying this one instead.

@rafaeleyng purifycss-webpack-plugin is something separate (deprecated). I had to rename a plugin to continue its development (the original author disappeared and npm took four weeks to transfer, I needed the plugin sooner than that).

@bebraw It seems to work now. I'm having configuration problems now, but the installation seems to be working fine. Thanks!

@rafaeleyng The configuration is very different, yeah.
Time to close this.


Add defaultApiVersion property to Gradle plugin for specifying API version to run snapshots on

Current dependencies on/for this PR:

main

PR #109   👈

This stack of pull requests is managed by Graphite.


Customize verification/password reset/etc email

Is there a way to use a custom template for emails? Or change/translate the title/body text somehow?

meteor-useraccounts uses Meteor Accounts for verification/reset email. (http://docs.meteor.com/#/full/accounts_sendresetpasswordemail)
rtfm material sry.

While it's possible to alter the text following the Meteor guides, is there any way of changing the full HTML template?

Thanks, I just kept digging through the docs for meteor/useraccounts-core and kept missing this info in the official documentation.


Undo and redo

[ ] investigate efficient recording of transformations to support undo and redo
[ ] undo char insert on Ctrl+Z
[ ] redo char insert on Ctrl+Y and Ctrl+Shift+Z
[ ] support undoing all actions that would make sense to be undoable
[ ] support redoing all undoable actions
[ ] write tests
[ ] write benchmarks

Editor is no longer being worked on, and has been removed from the repo. Closing.


Add some multi message signature tests

Based on #165

Odd the errors there. I guess too many sigs makes sense, but wrong order???
Did you raise issue on cosmos sdk to ask about this (or find docs that explain that)?

Oh yeah, it is real. The list of required signers is defined my the messages. The order is fixed and it is exhaustive. This basically makes it impossible to build n/m multisig using the native signing mechanism. All of this is described here: https://github.com/cosmos/cosmos-sdk/blob/v0.38.3/x/auth/types/stdtx.go#L89-L106 So I guess this works as intended.


map.bufferSize not working when setting extent directly on PostGIS Datasource

Trying to set extent on PostGIS Datasource with postgis_settings.extent = bbox.join(','), but get this result. Without setting the extent on datasource, tiles look as they should (but there's a huge performance hit due to PostGIS needing to query for extent).

Talked with experts on freenode, thought it was possibly a bug?
Full script: (put together from async flow, so perhaps not perfectly correct, but I have working code.)
// default settings
var default_postgis_settings = {
	user : 'user',
	password : 'password',
	host : 'host',
	type : 'postgis',
	geometry_field : 'the_geom_3857',
	srid : '3857'
}

bbox = mercator.xyz_to_envelope(parseInt(params.x), parseInt(params.y), parseInt(params.z), false);

// insert layer settings
var postgis_settings = default_postgis_settings;
postgis_settings.dbname = storedLayer.options.database_name;
postgis_settings.table = storedLayer.options.sql;

// this is the line in question: with this, get clipped tiles. without, all good (but performance hit due to postgis needing to query extent by itself)
postgis_settings.extent = bbox.join(',');

postgis_settings.geometry_field = storedLayer.options.geom_column;
postgis_settings.srid = storedLayer.options.srid;

// map
map = new mapnik.Map(256, 256, mercator.proj4);
layer = new mapnik.Layer('layer', mercator.proj4);
postgis = new mapnik.Datasource(postgis_settings);

// set buffer
map.bufferSize = 128;

// set extent
map.extent = bbox;

// set datasource
layer.datasource = postgis;

// add styles
layer.styles = ['layer'];

// add layer to map
map.add_layer(layer);

// parse xml
var options = {
	"srs": "+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0.0 +k=1.0 +units=m +nadgrids=@null +wktext +no_defs +over",
	"Stylesheet": [{
		"id" : 'tile_style',
		"data" : css
	}],
	"Layer" : [layer]
}

// carto renderer
var xml = new carto.Renderer().render(options);

map.fromString(xml, {strict : true}, function (err, map) {

	var map_options = {
		buffer_size : 128,
		variables : {
			zoom : params.z // insert min_max etc
		}
	}

	// raster
	var im = new mapnik.Image(256, 256);

	// render
	map.render(im, map_options, function (err, tile) {
		if (err) return done(err);

		// save png to redis
		store._saveRasterTile(tile, params, done);
	});
});

This is the PostGIS log for tile query with datasource.extent SET (clipped tile):
LOG:  statement: SELECT * FROM (SELECT * FROM  file_fihkdzefoztdeslprwxt) as sub LIMIT 0
LOG:  statement: SET DEFAULT_TRANSACTION_READ_ONLY = TRUE; SET CLIENT_MIN_MESSAGES = WARNING;
LOG:  execute <unnamed>: SELECT ST_AsBinary("the_geom_3857") AS geom,"height","vel" FROM (SELECT * FROM  file_fihkdzefoztdeslprwxt) as sub WHERE "the_geom_3857" && ST_SetSRID('BOX3D(4732980.791418113 4574603.268811227,4733592.287644395 4575214.765037511)'::box3d, 3857)

This is the PostGIS log when PostGIS must find the extent by itself (good-looking, but slow, tile):
LOG:  statement: SET DEFAULT_TRANSACTION_READ_ONLY = TRUE; SET CLIENT_MIN_MESSAGES = WARNING;
LOG:  statement: SELECT * FROM (SELECT * FROM  file_fihkdzefoztdeslprwxt) as sub LIMIT 0
LOG:  statement: SET DEFAULT_TRANSACTION_READ_ONLY = TRUE; SET CLIENT_MIN_MESSAGES = WARNING;
LOG:  statement: SELECT ST_XMin(ext),ST_YMin(ext),ST_XMax(ext),ST_YMax(ext) FROM (SELECT ST_Extent(the_geom_3857) as ext from file_fihkdzefoztdeslprwxt) as tmp
LOG:  execute <unnamed>: SELECT ST_AsBinary("the_geom_3857") AS geom,"height","vel" FROM (SELECT * FROM  file_fihkdzefoztdeslprwxt) as sub WHERE "the_geom_3857" && ST_SetSRID('BOX3D(4732675.043304968 4574297.520698082,4733898.035757537 4575520.513150653)'::box3d, 3857)

The bounding boxes differ.

This is expected behavior in the sense that if you set the extent on the datasource that will limit the data being queried. In this case the buffer will be ignored since the extent is limited by your manual extent. The solution should be to set the extent on the datasource to the entire extent of the data (not the tile extent you are querying). What I mean by that is to 1) run ST_Extent manually once, grab the values, 2) set those values in your script the same for each query.

Tested, works swimmingly! Thanks a lot!

i am able to show polygon file with mapnik node js and Postgres. i am able show point layer. please help.


ENet compatibility

As described in this forum topic, someone made a fork of this project that adds support for voice chat when using NetworkedMultiplayerENet: https://github.com/meisamsafavi/Godot-Enet-VOIP
Just leaving this here in this case this is of interest.

Thanks for the notification, I greatly appreciate it.


'Delete Account' header text not visible in Account details settings

Steps:
1.Visit https://apinf.io
2.Sign in
3.Go to Account section

'Delete Account ' header text not visible

Screenshot:

@saralavanip, just checked apinf.io, title is visible now.
I think, it was fixed during style files refactoring.
Please, confirm.

@elnzv , Yes, I verified at apinf.io and the title is visible now.


How can we chat with multiple files?

If we can chat with multiple files at once that will be better for searching & sorting documents rather than opening one by one.
If this can be implemented all the chunk can be uploaded and chat with a clear problem solving & getting which document has what.!
Thank you in advance to consider this request.

Thank you for your suggestion. I will implement this feature next week. Is there anything else I can help with? 😊

FileQueryHub
I have added this feature as a separate application named FileQueryHub. You can have a look at it on _https://allaboutpdf-multiple-filequery-feature.streamlit.app/._ This application allows you to upload multiple textual files like txt, pdf, excel, sql, csv. Is there anything else I can help with? 😊
@MirzaAreebBaig

Hey,
Great thank you for this.
How is this project being progressed as per the road map? The features are exciting which you have mentioned over there.

I have implemented this feature as a separate application. Visit this.
I think this feature will work fine (as this have same logic as chatPDF) but I haven't tested this feature as of now I don't have open-ai API key.
As of now I have checked my log file and got this error.
Retrying langchain.embeddings.openai.embed_with_retry.<locals>._embed_with_retry in 4.0 seconds as it raised RateLimitError: Rate limit reached for default-text-embedding-ada-002 in organization org-9o************Ep on requests per min. Limit: 3 / min. Please try again in 20s. Contact us through our help center at help.openai.com if you continue to have issues. Please add a payment method to your account to increase your rate limit. Visit https://platform.openai.com/account/billing to add a payment method..
and this error messages was generated by a program that is using the OpenAI API. The error messages indicate that the program has exceeded the rate limit for the default-text-embedding-ada-002 model in the org-9otlv*********Ep organization. The rate limit for this model is 3 requests per minute. The program is attempting to retry the request after a delay, but it continues to receive the same error message. The error message suggests adding a payment method to the account to increase the rate limit and provides a link to the OpenAI billing page for this purpose.
One more point, if you are trying to use this application for large textual file let us say 300+ pages then you are preferred to run this application locally as I have hosted it on free tier provided by streamlit which provide a limited compute and storage.
I would be grateful if you could kindly review my application and let me know if there are any issues. I am always here to help and would be happy to assist in any way I can 😊🙏


Async runtimes / parallelization in atomic-lib

atomic-server does a lot of async stuff, as an Actix project.
However, atomic-lib does not. @AlexMikhalev recently added paralellization to Db::all_resources, which helped speed it up. There are probably other places, too, where it might help to spin up some threads.
I'm not sure where we can expect to gain a lot by paralellization, but I expect that Db::query and Commit::apply_opts as costly functions that do a lot of loopy stuff could speed up quite a bit.

Add benchmarks to measure the performance of specific queries and I will have a go at speeding it up - let's chunk this task into multiple subtasks.

We have to rethink async and parallelisation in connection with the discussion https://github.com/atomicdata-dev/atomic-data-rust/issues/433 - Sled:IVec doesn't have Sync implemented so can't scale reads via Arc, we can use https://crates.io/crates/dashmap as cache, serialize it to disk using serde and then at some point migrate from sled if or when we need to. I also saw the news that sled is sunsetting, but I haven't seen confirmation.
For parallel we need to make a choice: are we going to add tokio as a dependency for atomic-data-rust or we need to make calls to parallelized functions - like all_resources sync from atomic-data-server. You can't mix both - tokio async and any other threadpool executors.
It's possible to use tokio for CPU-bound tasks, see here and here but it requires dedicated effort.


Alter links for providing feedback on topic taxonomy

Remove vague links and replace with more specific ones, like,
'Suggest a new topic` takes the user to that actual form where they can
recommend a new topic. Previsously the feedback links would land the user
on the homeopage of the support app with no real connection with what
the link text described.

Remove vague links and replace with more specific ones, like,
'Suggest a new topic` takes the user to that actual form where they can
recommend a new topic. Previsously the feedback links would land the user
on the homeopage of the support app with no real connection with what
the link text described.

:1st_place_medal:


jsx attribute auto complete should  use double quotes

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

MacOS: 12.4
VSCode: 1.69.0-insider
typescript: 4.7.3

https://user-images.githubusercontent.com/41773861/177741064-6031b887-7432-475b-a353-ae651cdd3f8e.mov

@mjbvz

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

as described ag https://github.com/microsoft/vscode/issues/143164#issuecomment-1042328896. I think It would be better to add another setting to let user define the quota style for html string attribute.
@mjbvz


chore(icons): update fontawesome dependency (#3130)

Fixes #3130.
Tested visually, icons are still shown.

Technically looks OK, cc @itsconquest to check if icons are ok in app

@deviantony RTM

cc @xAt0mZ for final review and conflict resolution (if possible, else ask @TimvdEijnden).

@deviantony  I'll fix the conflict

@xAt0mZ Conflict has been resolved, could you please review this?

cc @xAt0mZ for final review + merge

Thanks @TimvdEijnden :+1:


create Pets.jsx pet display page

create the page that displays all of the pets

https://github.com/jjackson0228/Pawsitive-Connection/pull/63![Image](https://github.com/user-attachments/assets/1550f247-59c8-4e5b-b925-9121f63e982e)


Fix Build K8s Upgrade

This PR attempts to fix the build by updating necessary packages. It appears that #299 and #302 broke the build and deploy.
Closes:

https://app.clickup.com/t/86890uc9q

Task linked: CU-86890uc9q Upgrade packages and fix deploy post Python 3.10 upgrade


Upgrading from v1.18.9+k3s1 to v1.19.3+k3s1 is broken

Environmental Info:
K3s Version: v1.18.9+k3s1 (trying to go to v1.19.3+k3s1)
Node(s) CPU architecture, OS, and Version:
Linux sserver 5.4.69-gnu-1-lts #1 SMP Sun, 04 Oct 2020 20:19:52 +0000 x86_64 GNU/Linux
I think this is important: I'm running btrfs, in RAID 1.
Cluster Configuration:
1 master node only.
Describe the bug:
When I try to upgrade k3s, it never completes. A bunch of errors appear in the logs, most notably:
Oct 23 10:39:03 sserver k3s[2828239]: F1023 10:39:03.536403 2828239 kubelet.go:1296] Failed to start ContainerManager failed to get rootfs info: failed to get device for dir "/var/lib/kubelet": could not find device with major: 0, minor: 46 in cached partitions map

What follows is impressively long (~1600 lines long), the start of which looks like this:
Oct 23 10:41:34 sserver k3s[2830467]: goroutine 30629 [running]:
Oct 23 10:41:34 sserver k3s[2830467]: github.com/rancher/k3s/vendor/k8s.io/klog/v2.stacks(0xc000010001, 0xc011152400, 0xe4, 0x1fa)
Oct 23 10:41:34 sserver k3s[2830467]:         /go/src/github.com/rancher/k3s/vendor/k8s.io/klog/v2/klog.go:996 +0xb9
Oct 23 10:41:34 sserver k3s[2830467]: github.com/rancher/k3s/vendor/k8s.io/klog/v2.(*loggingT).output(0x6e952a0, 0xc000000003, 0x0, 0x0, 0xc0092dfc00, 0x6b4d561, 0xa, 0x510, 0x0)
Oct 23 10:41:34 sserver k3s[2830467]:         /go/src/github.com/rancher/k3s/vendor/k8s.io/klog/v2/klog.go:945 +0x191
Oct 23 10:41:34 sserver k3s[2830467]: github.com/rancher/k3s/vendor/k8s.io/klog/v2.(*loggingT).printf(0x6e952a0, 0xc000000003, 0x0, 0x0, 0x451eadb, 0x23, 0xc00ba71cb0, 0x1, 0x1)
Oct 23 10:41:34 sserver k3s[2830467]:         /go/src/github.com/rancher/k3s/vendor/k8s.io/klog/v2/klog.go:733 +0x17a
Oct 23 10:41:34 sserver k3s[2830467]: github.com/rancher/k3s/vendor/k8s.io/klog/v2.Fatalf(...)
Oct 23 10:41:34 sserver k3s[2830467]:         /go/src/github.com/rancher/k3s/vendor/k8s.io/klog/v2/klog.go:1456
Oct 23 10:41:34 sserver k3s[2830467]: github.com/rancher/k3s/vendor/k8s.io/kubernetes/pkg/kubelet.(*Kubelet).initializeRuntimeDependentModules(0xc003fb8a80)
Oct 23 10:41:34 sserver k3s[2830467]:         /go/src/github.com/rancher/k3s/vendor/k8s.io/kubernetes/pkg/kubelet/kubelet.go:1296 +0x385
Oct 23 10:41:34 sserver k3s[2830467]: sync.(*Once).doSlow(0xc003fb92b8, 0xc00b8fbdd0)
Oct 23 10:41:34 sserver k3s[2830467]:         /usr/local/go/src/sync/once.go:66 +0xec
Oct 23 10:41:34 sserver k3s[2830467]: sync.(*Once).Do(...)

Steps To Reproduce:
I installed k3s via the script (curl -sfL https://get.k3s.io | sh -). This happens either when using the auto-update mechanism or via running curl -sfL https://get.k3s.io | INSTALL_K3S_CHANNEL=latest sh -.
Expected behavior:
It should upgrade.
Actual behavior:
Endless loop where k3s never upgrades. Binary has to be manually replaced with 1.18, or curl -sfL https://get.k3s.io | sh - works. Actual services it hosts remain up, but I can't run kubectl (either complains about being "unauthorised" or the server not being able to handle requests).
Additional context / logs:
#471 looks similar, parrticularly because I'm running Parabola which is similar to Arch. Note however I'm not using k3d. #48 is about brfs and could also be related.

Unfortunately this is deep in the kubelet cadvisor code, which means it's probably something that was changed upstream, not in k3s.
It looks like there's some special handling for btrfs just above the code that's producing this error here: https://github.com/rancher/k3s/blob/master/vendor/github.com/google/cadvisor/fs/fs.go#L570 - that was apparently added to fix https://github.com/kubernetes/kubernetes/issues/47046 and https://github.com/kubernetes/kubernetes/issues/65204 but it doesn't seem to handling how you have your system configured.

Thanks for the response. I opened an issue upstream: https://github.com/kubernetes/kubernetes/issues/95826
I'll close this issue and continue over there (feel free to re-open if this should be tracked here too).


Delete orphaned miq workers rows with no pods

DEPENDS on:

[x] New system_uid column
[x] Set system_uid in worker pods based on hostname

synchronize miq_workers rows with the current pods in kubenetes, removing extra rows

Please review with whitespace changes removed.  I had to shuffle indents in some of the tests as I changed the location where we start the pod monitor thread.

Kasparov backport details:
$ git log -1
commit c2a874738937a54fb0b9c6645ffcc20c9150d000
Author: Jason Frey<EMAIL_ADDRESS>Date:   Wed Nov 11 17:08:33 2020 -0500

    Merge pull request #20792 from jrafanie/delete_orphaned_miq_workers_rows_with_no_pods

    Delete orphaned miq workers rows with no pods

    (cherry picked from commit 48cf77bafbd243c815b4cfec049a6cef257b6f14)

Backported to Jansa via https://github.com/ManageIQ/manageiq/pull/20814 (without the schema change)


Review enhancements

Merge with master for a newer version.

Merging to master. After what seems like years ago.


Add URLHaus

Looks promising. Checked few domains from the list in VirusTotal and they all had high detection.
@dimkr give time to Steven @StevenBlack to assess your request.
Are you the curator of the lists,or just passing out the info?
Either way,i think it will be a good addition here 👍

The intersection set is 5 domains.
$ ./hoststools -c https://raw.githubusercontent.com/StevenBlack/hosts/4d295cc30fd7898491128b77dfe93bde56d11cea/data/URLHaus/hosts
--------------------------------------------------------------------------------
Base hosts file summary:
--------------------------------------------------------------------------------
Location: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
Domains: 51,985
Bytes: 1.6 MB
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Compared hosts file summary:
--------------------------------------------------------------------------------
Location: https://raw.githubusercontent.com/StevenBlack/hosts/4d295cc30fd7898491128b77dfe93bde56d11cea/data/URLHaus/hosts
Domains: 1,033
Bytes: 28 kB
--------------------------------------------------------------------------------
Intersection: 5 domains

Dan @dnmTX and Dima @dimkr we've talked about URLHaus before.  See Consider including URLhaus domains which is Issue #1143.
I sent an email in February requesting permission, but received no reply.
The CC0 license — “No Rights Reserved” is nice.
Maybe we should just, do it.

Dan @dnmTX is it actually weird the intersection set is just 5 domains?  That's 0.5% intersection.
URLHaus doesn't list anything from Google, nothing from Doubleclick... It's just, weird.
Your thoughts?

Are you the curator of the lists,or just passing out the info?

Just passing the info. I discovered this source today, after doing some research for a pet project that needs a large domain name blacklist. I decided to use Steven's combined list and found URLHaus when I looked for additional sources it might be missing.

Steve @StevenBlack

Dan @dnmTX and Dima @dimkr we've talked about URLHaus before.

well...never thought about searching for it. Lesson learned 😉

URLHaus doesn't list anything from Google, nothing from Doubleclick... It's just, weird.
Your thoughts?

Looks like they're focused on malware domains only with high antivirus detection. Very likely most of them are gathered from VirusTotal. Nothing wrong with that,small list but valuable.Pure example of quality over quantity.

Maybe we should just, do it.

I partially read the license and it looks like they're waiving all their rights,which,in my book is a green light for us here.
Maybe one more e-mail just as a courtesy and if there no response just add it Steve.All of us will be a bit more safer 👍

Thanks Dan @dnmTX I appreciate your input.
Let's do this.
Dima @dimkr thank you for this pull request; it makes us better.  Thanks also to Quinn @quinncomendant who first suggested this, back in February, in Issue #1143.
Merging!

Thank you @StevenBlack, looking forward to contributing again. Thank you for maintaining this great project!


Adding Features for Student, Teacher Assistants, and professor management and Course Assignment for Students, Teacher Assistants, and professor

I would like to add a set of features to our  academia app. Please implement the following features:

Student Management:

Create an account for each student, including personal information such as name, email, and date of birth.
Record academic information for students, such as university, college, major, and academic level.
Track the academic progress of each student based on their academic performance.
Add each student to a student group based on their academic level and major.

Teacher Assistants and professor management:

Create an account for each teacher assistant and professor, including personal information such as name, email, and academic specialization.
Assign each professor and teacher assistant to teach specific course or multiple courses.
Specify the student groups that each professor or teacher assistant will teach.

Course Assignment:

Assign courses to students based on their major and current academic level.
Update the course assignments for each student based on their major, academic level, and current semester.

I kindly request the development team to consider these features and add them to the existing app.

Thank You @atrab-ahmed. The requested features will be added as soon as possible.


V3: add list filter composition

The PR depends on https://github.com/sajari/sajari-sdk-react/pull/201

I had originally thought the pattern for the Filter compositions would be with a type prop <Filter type="list" />, do you think that would work? Possibly save some double up of logic?

I had originally thought the pattern for the Filter compositions would be with a type prop <Filter type="list" />, do you think that would work? Possibly save some double up of logic?

Will make the update. But the list and color filter do not share the same options so probably the Filter interface will look like:
interface ListProps{
 type: 'list',
 ....
}

interface ColorProps{
  type: 'color',
  ...
}

type FilterProps = ListProps | ColorProps;

Closing in favor of https://github.com/sajari/sajari-sdk-react/pull/206


[hbase10] Turn off info servers during tests

Currently YCSB can't be built on the machine running HBase cluster, because the local testing cluster tries to bind a master info server on the same port with the actual cluster's port. See the following output...
$ mvn clean package
...
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running com.yahoo.ycsb.db.HBaseClient10Test
...
2016/02/13 14:24:06 ERROR org.apache.hadoop.hbase.regionserver.HRegionServer  - Failed binding http info server to port: 16010
2016/02/13 14:24:06 ERROR org.apache.hadoop.hbase.MiniHBaseCluster  - Error starting cluster
java.lang.RuntimeException: Failed construction of Master: class org.apache.hadoop.hbase.master.HMasterAddress already in use
...

This is a bit annoying, so I turn off a master info server during tests. A region info server does not cause a port conflict, but any info server is not necessary during tests, so I turn off region's info server, too.

Thanks!


Fixed typo

I believe that the changed line was trying to fetch the name from "author":{"name":"blah", "email":"blah" etc}.

Thanks for fixing this :+1: Published in 2.0.4


Emit logs frequently for debugging

Instead of only emitting logs at the end of a job completing/finishing instead we should emit logs at a set frequency. This will require the build to potentially be an async process to be able to periodically update the logs on file/object storage.

This is an example of how logs are uploaded https://github.com/Quansight/conda-store/blob/main/conda-store-server/conda_store_server/build.py#L24-L31.
Right now this is only done on success/failure of the build. Instead we would like to be able to successively update/upload the logs.
https://github.com/Quansight/conda-store/blob/main/conda-store-server/conda_store_server/build.py#L147-L159 should be continually uploading logs at a set frequency that is configurable on CondaStore.log_update_frequency = ... [s].

Redis would result long term in the best user experience.

check that redis is enabled
Potentially use redis streams https://redis.io/docs/data-types/streams-tutorial/ (but worth investigating if this is the right approach).

If a build is not completed/failed we can stream the logs via websockets, otherwise redirect the user to the storage for the logs (current behavior).

Closing since frequent logs are currently emited. Please open another issue if more detailed logs are needed. It is hard to balance frequently writing logs and storing them on s3/object storage.


[VS Code] The system cannot find the file specified

Error:
The system cannot find the file specified
Steps to Reproduce:

create folder c:\temp\test and go there in a cmd
dotnet new webapi
code .
click on share
error popup "The system cannot find the file specified"

Attached are the logs
20180314_223113_VSCode.log
20180314_223113_Agent.log

Version Data

extensionName
VSLS

extensionVersion
0.2.206

protocolVersion
2.1

applicationName
VSCode

applicationVersion
1.21.1

platformName
Windows

platformVersion
10.0.14393

Uninstalling and reinstalling the extension or closing and opening VS Code as suggested in a similar issue didn't work for me

I suspect this may be related to #86. VS Code does not pass along proxy settings to extensions and therefore Live Share does not get them.
We have found that setting the HTTPS_PROXY and HTTP_PROXY global environment variables that point to your proxy can help in some cases.   Can you try setting these to see if it solves the problem?

Our proxy is supposed to work without any settings, but that doesn't seem to work. I am back in the office and now I don't get an error for the (probably) proxy IP but instead
[2018-03-15 07:19:23.573 Client I] Did not find user settings at C:\Users\tfenster.vs-liveshare-settings.json
[2018-03-15 07:19:23.583 Client I] Passed version check for Windows: found 10.0.16299
[2018-03-15 07:19:23.683 Client I] Installing dependencies for Live Share...
[2018-03-15 07:19:23.691 Client I] Downloading package '.NET Core Runtime 2.0.5 for win7-x86'
[2018-03-15 07:19:30.207 Client E] Failed at stage: downloadPackages - Dependency download failed. RequestError: tunneling socket could not be established, statusCode=403
The funny is that other extension can download dependencies like e.g.
`Installing C# dependencies...
Platform: win32, x86_64
Downloading package 'OmniSharp for Windows (.NET 4.6 / x64)' (21254 KB) .................... Done!
Downloading package '.NET Core Debugger (Windows / x64)' (39360 KB) .................... Done!
Installing package 'OmniSharp for Windows (.NET 4.6 / x64)'
Installing package '.NET Core Debugger (Windows / x64)'
Finished`
So I would guess that our proxy is blocking (error 403) whatever download does happen here. Curling the URLs mentioned in your troubleshooting document seems kind of fine to me, at least I don't get a 403.
`tfenster@DE00-FM16-L01:~$ curl https://insiders.liveshare.vsengsaas.visualstudio.com/

303 See Other

303 See Other
nginx

tfenster@DE00-FM16-L01:~$ curl download.visualstudio.microsoft.com

500 - Internal Server Error

500 - Internal Server Error

tfenster@DE00-FM16-L01:~$ curl download.microsoft.com
Document Moved
Object MovedThis document may be found heretfenster@DE00-FM16-L01:~$ curl https://insiders.liveshare.vsengsaas.visualstudio.com

303 See Other

303 See Other
nginx

`
Is there any way to see the actual URL that fails? I could then try to see if I can access that in a browser or get it whitelisted in our proxy

The actual url it's trying to download is https://download.microsoft.com/download/1/1/0/11046135-4207-40D3-A795-13ECEA741B32/dotnet-runtime-2.0.5-win-x86.zip
However I think the problem is likely in our extension (or in a library we are calling) since the C# extension is downloading from a similar domain successfully.
Could you please check if you have these two settings defined in your vscode settings - http.proxy and http.proxyStrictSSL? Can you also please run npm config get strict-ssl from your command prompt to see if that returns true or false?

That URL indeed does work in a browser.
My settings look like this, workspace settings are empty

Env variables are not defined (I do set in a terminal and see neither HTTP_PROXY nor HTTPS_PROXY)
'npm config get strict-ssl' returned 'true'. I've changed this to 'false' ('npm config set strict-ssl false') and also set '"http.proxyStrictSSL": false' but still get the same error

It's possible there's two separate issues here.  The dependency download is #86 and is a bug.  Live Share is not always using proxy settings that are set at the OS level.  Consequently even if your proxy is supposed to work transparently, it may not work for Live Share. @avanderhoorn is digging into this.
The "The system cannot find the file specified" error you reported above is strange and perhaps different. It looks like you got past the initial dependency download.  Is that correct?  Was this from home or outside the corp network with the proxy?

No, I wasn't able to download dependencies and actually start live share on that particular machine (Win 10 laptop). It worked on a couple of Win Server 2016 VMs, but not on the laptop.

@tfenster Just so I'm clear, was the "The system cannot find the file specified" error above from the Win Server 2016 VM or the laptop?

Win 10 laptop

@tfenster Got it.  Thanks for clarifying! Okay, I'll let @srivatsn and @avanderhoorn confirm my suspicions here. Interestingly we haven't seen that particular error associated with proxy problems before but there's enough different proxy configurations this may just be a new failure mode.

sorry, 100% my mistake: I didn't realize live share is using npm to load the dependencies. I had an old .npmrc in my home folder where the proxy was manually set from the time where we had to do this in our network. After removing that setting, it now works. Once more: sorry!

In case anyone is wondering, Live Share doesn't precisely use npm to download the dependencies, but it (indirectly) uses a node package that automatically tries to get proxy settings from npm config, if the proxy environment variables are not set.

ok, jumping to conclusions on my side :) thanks for the clarification


add shimo style for android

There is a weird underline on the drop markers when using "shimo" style. Is this intended? Or should we fix it?
here is screenshot:


Level screen looks a bit weird on first load

On commit 4df5008, building on macOS.
Opening the game everything looks a bit weird:

But then after resizing it looks good:

That never happened to me. Probably because I use tiling wm that resizes the window right after starting the application. I'll try to check that on a non-tiling wm.
Thanks for reporting that!

I imagine this never get ran then: https://github.com/tsoding/nothing/blob/master/src/game/level_picker.c#L153

Resolved by #969


[Table]: Add Quick search and stateful table support search

Server-side search too...

After talking with Amy Millett we decided for search to check every field of the issue.

@amymillett can you attach a screenshot to this for the quick search

:tada: This issue has been resolved in version 1.16.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.16.0 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


Multiplayer issues in game

Start turn call after earning a token
A start turn event is emitted when the user earns a token.
Question dialog closes unexpectedly
The turn does not change when a player won 3 tokens in a row

Because turn event was called before the players who won the tokens has made his last movement.

I think this is a known issue but i'll leave it here:
Sometimes, the multiplayer question dialog question closes before the player answers it. This might be caused by a setTimeout that isn't properly cleaned.

Start turn call after earning a token && change player turn after 3 tokens in a row issues have been fixed in commit 9fc1483
Question dialog issue hasn't been fixed yet


[WIP] Add thread sanitizer support

[ ] Make it work for parallel test runner
[ ] Add tests
[ ] Test on linux
[ ] Cleanup and documentation

In keeping with how this is exposed in the compiler, I would prefer to expose this as —sanitize=thread (and to pave the way for all the other sanitizers)

Hi! It’s awesome to see SPM integrating with TSan.
In this Swift PR, Carl Brown added support for the Sanitizer on Linux. If you have any trouble with the Linux tests, maybe you can ask him for help. He’s the most knowledgable user of TSan on Linux that I know of ^^

Closing until I get time to work on this.

@aciidb0mb3r Did Apple resolve this issue?


MySQL cdc table sql in rw_tables syntax error

Describe the bug
The sql in rw_tables cannot create table successfully due to syntax error. The following should be FROM sbtest TABLE 'mydb.sbtest10'
dev=> select definition from rw_tables limit 1;
                                                          definition
-------------------------------------------------------------------------------------------------------------------------------
 CREATE TABLE sbtest10 (id INT PRIMARY KEY, k INT, c CHARACTER VARYING, pad CHARACTER VARYING) FROM sbtest TABLE mydb.sbtest10
(1 row)

dev=>  CREATE TABLE sbtest10 (id INT PRIMARY KEY, k INT, c CHARACTER VARYING, pad CHARACTER VARYING) FROM sbtest TABLE mydb.sbtest10;
ERROR:  QueryError: sql parser error: Expected end of statement, found: . at line:1, column:118
Near "VARYING) FROM sbtest TABLE mydb"

Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
nightly-20231108
Additional context
No response

Why the single quote (FROM sbtest TABLE 'mydb.sbtest10') is eliminated? 👀  @yezizp2012

Why the single quote (FROM sbtest TABLE 'mydb.sbtest10') is eliminated? 👀 @yezizp2012

I believe it was eliminated by the parser, let me take a look.

Quote should be included in Display:
https://github.com/risingwavelabs/risingwave/blob/1abe9e82eb17d61aa9279a5cb8275af90083f504/src/sqlparser/src/ast/mod.rs#L1574-L1577
Add a test here and you can see whether quotes are preserved or not in formatted_sql
https://github.com/risingwavelabs/risingwave/tree/main/src/sqlparser/tests/testdata

Oh, that is my bad. 🥵


Substitute fmt with format

Hey,
Thank you very much for the project. I was wondering if fmt should be kept instead of format?
Every command is a full word, while we used an abbreviation for this, although it's not a really long word.
Thanks in advance!

Hi! Thanks, first issue 😃.
I prefer fmt since it's used by cargo, which pyrgo inspires from and also the format command used by various tools like Terraform.
I would say it's a matter of getting used to it.
That said, if more people puch for it I'd change it.


Weird linters command syntax ?

gcc -S -x c++ -fsyntax-only -iquote /tmp/test -std=c++14 -Wall - < /tmp/vEBHKPH/16/main.cpp

Why don't just pass the target file name to it directly ?
gcc -S -x c++ -fsyntax-only -iquote /tmp/test -std=c++14 -Wall /tmp/vEBHKPH/16/main.cpp

It's because the file used to be sent directly from Vim via stdin, without writing a temporary file. I might do that again in the future. Vim supports it, but some versions of MacVim don't implement it correctly.


Update obsolete api calls in .NET 6

https://docs.microsoft.com/en-us/dotnet/api/system.security.cryptography.rngcryptoserviceprovider?view=net-6.0
https://docs.microsoft.com/en-us/dotnet/api/system.security.cryptography.x509certificates.x509certificate2.privatekey?view=net-6.0#System_Security_Cryptography_X509Certificates_X509Certificate2_PrivateKey

I found more usages should be updated. Check from here.

I found more usages should be updated. Check from here.

Updated those too.


Need for self-adapted horizontalSafetyDistance

Description
As horizontalSafetyDistance is a fixed parameter, it cannot be self-adapted while the driving envrionment is changing.  So its value is sometimes too large and sometimes too small among different driving envrionments.
Hazard
In my testing, if horizontalSafetyDistance is:

Too large: ego will stop due to a close NPC within the horizontalSafetyDistance, sometimes the the place that ego stops is dangerous (e.g.,highway) and cause collisions.

Video: https://youtu.be/r0Pz3-s_nDI. In this video the ego stops since the bicycle is too close, and a rear-end collision happend.

Too small: ego sometimes is too close to obstacles, this is also dangerous.

Recall that the driving environment may change over time, so a fixed horizontalSafetyDistance won't fit for all driving environment. So a self-adapted horizontalSafetyDistance might be needed.

Even if you make too small for slow speed.
One design objective of having this safety rectangle is to compensate for Localization & detection errors.
If you know that lateral localization error is +- 5 cm. then additional safety margin of 10 cm should be added at each direction.
Same applied to detection.


Issue with IMU config. ( Livox Horizon w/ External IMU )

Hi
I am having some trouble getting LIO-SAM working  with my own hardware.
I am observing behaviour like described in issue #94.
For these tests, the LiDAR and IMU are not moving.

I'm using ptpd2 for synchronization. These are two headers recorded at the same time. There is a difference on the "nsecs" parameter, which is around 95 ms.
IMU message header:
header:
  seq: 4133
  stamp:
    secs:<PHONE_NUMBER>
    nsecs: 194799837
  frame_id: "imu_link"

LiDAR point cloud message header:
header:
  seq: 91
  stamp:
    secs:<PHONE_NUMBER>
    nsecs:  99923849
  frame_id: "livox_frame"
height: 1
width: 24000

It runs without any problem when working with the provided Livox dataset (I am using TixiaoShan  livox_ros_driver package, also had "useImuHeadingInitialization: false" when playing the dataset).
- Hardware:
Livox Horizon
Xsens MTi-680G
The IMU alignment is the same as the LiDAR so I have set both  "extrinsicRot" and "extrinsicRPY" to identity matrices.
- params.yaml
What I have changed on the LIO-SAM  params.yaml:
  # Topics
  pointCloudTopic: "points_raw"
  imuTopic: "imu/data"
  odomTopic: "odometry/imu"
  gpsTopic: "odometry/gpsz"

  # Frames
  lidarFrame: "base_link"
  baselinkFrame: "base_link"
  odometryFrame: "odom"
  mapFrame: "map"

    # GPS Settings
  useImuHeadingInitialization: false

    # Sensor Settings
  sensor: livox
  N_SCAN: 6
  Horizon_SCAN: 4000
  downsampleRate: 1
  lidarMinRange: 1.0
  lidarMaxRange: 1000.0

  # Extrinsics: T_lb (lidar -> imu)
  extrinsicTrans: [-115.0, 0.0, 63,26.0] # x y z
  extrinsicRot: [1, 0, 0,
              				  0, 1, 0,
               				  0, 0, 1]
  extrinsicRPY: [1, 0, 0,
               				  0, 1, 0,
               				  0, 0, 1]

With the provided bag file I use the default values for extrinsicTrans, extrinsicRot, extrinsicRPY and use /imu_raw instead of /imu/data.
On the recorded bag I'm pointing the LiDAR at a corner (from the ground pointing at the roof), that's why it looks like it is tilted.
- tf tree

- bag file
Here is a bag file recorded with my setup.
https://drive.google.com/file/d/1vHyeEK8l7XN48wCtQlUm2okEzSpmU_vc/view?usp=sharing
Any suggestions on what I should tweak?

Update:
The issue I was facing was wrong extrinsic parameters. While I had the IMU oriented the same way as the LiDAR (according to each device's datasheet) the LiDAR orientation was configured differently, noticed this after checking the LiDAR's configuration with Livox Viewer.
I had to input the extrinsic parameters in both extrinsicRot and extrinsicRPY.
Also the tf tree I uploaded may be incorrect. After remapping /imu/data to /imu_raw and using /imu_raw  in LIO-SAM's params.yaml the "imu_link" is now a child of "chassis link".

Update: The issue I was facing was wrong extrinsic parameters. While I had the IMU oriented the same way as the LiDAR (according to each device's datasheet) the LiDAR orientation was configured differently, noticed this after checking the LiDAR's configuration with Livox Viewer.
I had to input the extrinsic parameters in both extrinsicRot and extrinsicRPY.
Also the tf tree I uploaded may be incorrect. After remapping /imu/data to /imu_raw, and using /imu_raw in LIO-SAM's params.yaml, the "imu_link" is now a child of "chassis link".

Hi! Could you tell me how you set the extrinsicRot and extrinsicRPY, finally?

Sure, they were:
  extrinsicRot: [0, 0, 1,                  0, -1, 0,                  1, 0, 0]   extrinsicRPY: [0, 0, 1,                  0, -1, 0,                  1, 0, 0]
Here is the full configuration file:
params.yaml

Sure, they were:  extrinsicRot: [0, 0, 1, 0, -1, 0, 1, 0, 0] extrinsicRPY: [0, 0, 1, 0, -1, 0, 1, 0, 0]
Here is the full configuration file: params.yaml

Thanks! By the way, why these matrices can work? Shouldn't we set the calibrated extrinsic parameters?

There isn't necessarily a "calibration" for this matrices, it can be manually calculated but that depends on your hardware setup.
The IMU and the LiDAR each have their own orientation and a transformation from one to another has to be provided.
Let me borrow this part of the LIO-SAM description:

IMU alignment. LIO-SAM transforms IMU raw data from the IMU frame to the Lidar frame, which follows the ROS REP-105 convention (x - forward, y - left, z - upward). To make the system function properly, the correct extrinsic transformation needs to be provided in "params.yaml" file. The reason why there are two extrinsics is that my IMU (Microstrain 3DM-GX5-25) acceleration and attitude have different cooridinates. Depend on your IMU manufacturer, the two extrinsics for your IMU may or may not be the same. Using our setup as an example:
we need to set the readings of x-z acceleration and gyro negative to transform the IMU data in the lidar frame, which is indicated by "extrinsicRot" in "params.yaml."
The transformation of attitude readings might be slightly different. IMU's attitude measurement q_wb usually means the rotation of points in the IMU coordinate system to the world coordinate system (e.g. ENU). However, the algorithm requires q_wl, the rotation from lidar to world. So we need a rotation from lidar to IMU q_bl, where q_wl = q_wb * q_bl. For convenience, the user only needs to provide q_lb as "extrinsicRPY" in "params.yaml" (same as the "extrinsicRot" if acceleration and attitude have the same coordinate).

This website may help you understand this parameters.

Thank you very much! Your replies help me a lot!


Not available on android

Hi,
I check on my phone and this addon is not working on Android (Firefox) :(.

It's a known issue, I'm looking into it but I can't promise anything.


compatible

The current version is not compatible with rxswift6.0. When can I update it

@sayGoodLolita Can't you solve it with 3.0.0?


Dataset download

Hi,
I'm having trouble downloading your dataset. It seems that your link is disabled, probably due to bandwidth limitations of DropBox?

Hi,
Are you still having problem downloading the data? I currently have no problem downloading it, even after signing out of my own Dropbox account.
If you are still experiencing the same error, maybe try to download again in a few days?

Hello，
I ran into the same problem when downloading the dataset，the Dropbox link provided appears to be inactive or expired, preventing me from accessing the dataset files.
I have tried accessing the dataset on multiple occasions, but the link consistently returns an error indicating that it is no longer available. I believe this may be due to the link being shared or downloaded excessively within a short period of time. I was wondering if there is an alternative way to access the dataset or if the link can be updated. I would greatly appreciate your assistance in resolving this matter.

Thanks for reaching out for this issue. It seems that the subscribed plan for our Dropbox account has expired. That's why the download link is disabled. I have contacted our lab admin to make the payment and renew the subscribed plan. But she wouldn't be able to do so until next Monday. I'll update with you guys once the plan is renewed and the download link is working again.
Thanks for bringing this to my attention and thanks for your patience in waiting.

Hi @z7r7y7 @phquentin, the download link should be working again. Thanks for bringing this issue to my attention. This issue is closed now.


Charts[Network Node]: Add a new docker container definition which provides BATS included in the bitnami kubectl base image

:tada: This issue has been resolved in version 0.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fixing the context of calling ubar enable/disable methods

Found this issue integrating Ubar with Gilt's account pages. The context of these methods is incorrect... The new tests I added will fail if the code change un ubar.js is reverted.

:hamburger: :fries:

Mmmmm :hamburger: :fries:


refactor(@angular-devkit/build-angular): remove deprecated i18n options from server and browser builder

BREAKING CHANGE:
Removal of deprecated browser and server command options.
-i18nFile,  use locales object in the project metadata instead.

i18nFormat, No longer needed as the format will be determined automatically.
i18nLocale, use localize option instead.

Blocked until https://github.com/angular/angular-cli/pull/20407 is landed.


Mark Tufin as FIPS Compliant in app metadata

Mark the app as fips_compliant
Fix Verbose Period failing test

Static failing tests:

Min Platform Version


homework1

Hey @YanaHaivoronska Please fix linter errors

Hey @YanaHaivoronska Please fix linter errors

Hello , thank you for checking,  I will do it as fast as can get to my pc .

@YanaHaivoronska you can find specific linter errors on the 'Files' tab. Look for the comment right under the line that needs fixing."

@anna-vrana-moc just get all fixed. Check again,please.

@YanaHaivoronska please use font-family Roboto for the content

Hey, @YanaHaivoronska, I'm closing this pr, because of deadline is gone

Yes , I'm totally understand that . Look like i fix it , but it's bit too late .

Ou, @YanaHaivoronska, I've just not seen your commits after the last comments from your mentor. Probably you've not pushed it to GitHub.
And yes, it is too late a bit. The deadline was on Monday.🤷♂


Support query delegates on collection classes

Originally filed as https://github.com/querydsl/querydsl/issues/3327
@QueryDelegate is a powerful feature that does not work properly with collections. QueryDSL creates Q-classes, but they extend BeanPath. As a result, one can't use expressions already available in these classes and can't pass appropriately typed Path parameters to custom extensions.
Actual:
public class QSet extends BeanPath<Set<?>> {
  ...
}

Expected:
public class QSet<V, E extends SimpleExpression<V>> extends SetPath<V, E> {
  ...
}

public class QEntity extends BeanPath<Entity> {
  public final QSet<String, ext.java.lang.QString> s =
    new QSet<String, ext.java.lang.QString>(forProperty("s"));
}

I tried to tinker around the annotation processor, but it does not look like it generally supports the generation of parameterized classes.

Seems no one is working on this, I'm closing to clear the board.  Feel free to reopen after a PR is submitted.


Array of items is duplicated on model after update

Describe the bug
When model as an Array of items (in test case type was [String]?) updating using Amplify.API.mutate(.update(model)) the new model appends all contents of the array to the existing model creating duplicates. Updating a model will cause exponential growth of all array properties.
To Reproduce
Create a schema with [String]? property.
Create a new model with this property populated and sync
Update this model, with or without changing any value

The value of the array property on the model returned will have duplicated values.

Expected behavior
Models returned by update query should match what was updated
Environment(please complete the following information):

Amplify Framework Version: 4.21.1
Dependency Manager: cocoapods
Swift Version : 5.0

Device Information (please complete the following information):

Device: Simulator
iOS Version:  iOS 11
Specific to simulators:

Hi @jaivia, thanks for reporting this issue. I tried to reproduce this but could not. The schema i'm using is
type Todo @model {
  id: ID!
  colors: [String]
}

I tried creating a todo, then querying for the todo by Id, and updating the queried data. the todo's colors is not duplicated. I also tried creating a todo, and directly using the locally created todo and updating it.
Are you able to reproduce this in Amplify 1.0.4 and Amplify CLI 4.22.0? There were a few changes related schemas containing an array of types such as this one. So once you upgrade to 4.22.0, you will have to re-run amplify codegen models to regenerate the new models. Make sure you are on the latest Amplify Library by running pod cache clean --all && pod install --repo-update and checking your Podfile.lock is using Amplify 1.0.4 libraries.

Closing this issue due to inactivity. Feel free to re-open if you're still facing the same issue.


update a command in post_check.md

What this PR does / why we need it:
Update post-check with the suggestions from @zhaosimon
Does this PR introduce a user-facing change?
NONE

cc @zhaosimon

approved!