feat: implement PaperRepositoryList()

Follows #5

Codecov Report

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

:exclamation: Current head 73217d0 differs from pull request most recent head 7e932eb. Consider uploading reports for the commit 7e932eb to get more accurate results

@@           Coverage Diff           @@
##             main       #6   +/-   ##
=======================================
  Coverage        ?   49.33%
=======================================
  Files           ?        5
  Lines           ?       75
  Branches        ?        0
=======================================
  Hits            ?       37
  Misses          ?       32
  Partials        ?        6

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0c53b19...7e932eb. Read the comment docs.


Provide info on how to use HOMEBREW_NO_ENV_HINTS

Provide a detailed description of the proposed feature
By default, after a fresh brew installation, for every brew install SOMETHING command that is run the output ends with:
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).

I propose we update either the man pages or this line with suggestion on how to use the HOMEBREW_NO_ENV_HINTS variable to hide the hints.
What is the motivation for the feature?
It took me a lot of time to figure out how to HOMEBREW_NO_ENV_HINTS , and I can imagine it could be the case for many other users.
How will the feature be relevant to at least 90% of Homebrew users?
Everyone will be able to just use HOMEBREW_NO_ENV_HINTS and get rid of the message appearing after each brew install SOMETHING command.
What alternatives to the feature have been considered?
Writing a blog post about it so it can be found when googling.

Is the information in man brew not sufficient?

Is the information in man brew not sufficient?

Until we have more people asking: I think it is.

Is the information in man brew not sufficient?

Thank you for asking this @carlocab ! 🙇♂
@MikeMcQuaid has a point 👌, in my case the informtion from man brew felt like just repeating the same amount of information from the output 🤷♂


NIFI-2323: Fixed Oracle timestamp handling in DB fetch processors

I tested this on Oracle 11g XE with tables containing TIMESTAMP and DATE fields. The state is now stored as timestamps (dates have a time-of-day of zero/midnight)

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

This looks good to me. Code is clean and makes sense. Contrib-check passes with all unit tests. +1 merged to master.


Get APNS Token returns NULL

cordova-plugin-firebasex 13.0.1 "Google Firebase Plugin"
Cordova iOS 6.0.0
IOS 14.7.1
8.4.0 - [Firebase/Messaging][I-FCM012002] Error in application:didFailToRegisterForRemoteNotificationsWithError: no valid 'aps-environment' entitlement string found for application
and i did requested uesr presmissions

Did you find the solution???


Add docker support for blutter

I spent an afternoon trying to run Blutter on Windows.But I failed.
Then I thought I can create a Docker image to simplify(?) my usage process.
As an alternative to running directly on the operating system, docker provides some advantages,such as avoiding many dependency or OS issues.

duplicate to #50


[Feature]Filter the application list to exclude apps that users cannot access.

Even though I've set certain apps as inaccessible for a particular user in the permissions list, they are still visible in the home page app list.

I believe the home page app list could include an API, something like "/api/get-user-applications," to filter the applications accessible to the user.

@anyidea no need, just use /api/get-applications, filter out the ones that don't have access. BTW, can you make a PR?

@anyidea no need, just use /api/get-applications, filter out the ones that don't have access. BTW, can you make a PR?

We can apply permission filtering for non-admin users in the GetOrganizationApplications method.

Fixed by: https://github.com/casdoor/casdoor/commit/498cd02d49db6b48d58c651485f5a2e5045e316d


chore(analytic): send install event on nfs-provisioner start

Why is this PR required? What issue does it fix?:
What this PR does?:
This PR enable nfs-provisioner to send Installation and Ping event
Does this PR require any upgrade changes?:
If the changes in this PR are manually verified, list down the scenarios covered::
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[ ] Fixes #
[x] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Does this PR change require updating NFS-Provisioner Chart? If yes, mention the Helm Chart PR #
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

Codecov Report

Merging #109 (a0362a5) into develop (23d4176) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop     #109      +/-   ##
===========================================
- Coverage    46.97%   46.91%   -0.06%
===========================================
  Files           29       29
  Lines         2378     2381       +3
===========================================
  Hits          1117     1117
- Misses        1182     1185       +3
  Partials        79       79

Impacted Files
Coverage Δ

provisioner/controller.go
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 23d4176...a0362a5. Read the comment docs.


[BLD]: SQLite3 file to help with debugging problems with SQLite DB in single-node Chroma

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

sqlite3 package install in chroma base image

Test plan
How are these changes tested?
Manual image build
Documentation Changes
N/A

I think we should just document this somehow instead - users are sensitive to the docker image contents so it should be minimal


Fixed Circle ci

Fixed Circle CI

Codecov Report

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

@@           Coverage Diff           @@
##           master      #14   +/-   ##
=======================================
  Coverage   52.36%   52.36%
=======================================
  Files          12       12
  Lines         254      254
=======================================
  Hits          133      133
  Misses        121      121

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 87feaff...d980422. Read the comment docs.


Refresh when i swipe without being on top

I am trying to use this pull to refresh, but im having an issue. I've looked for other issues like this, but didnt found any answer that solve my problem, so I submited this issue. I tried with 0.1.14 and 0.1.17 versions and none worked. My app is built using cordova and i tested both in mobile and browser.
Bug report

Current behavior:
When i scroll, my app refresh.
Expected behavior:
My app refresh only its on top.
** for demo with bug:**
https://jsfiddle.net/L4dypo8n/
Browsers affected:
Google chrome / android

Hello @narcisao so much thanks for your input, however I was not able to run your demo.

https://jsfiddle.net/L4dypo8n/4/ try with this new one. changed the source code from html

Did you confirmed it replicates the same issue?

I checked on another computer. For this app, im using cordova. I opened the console and for a reason (that i dont know why) my parameter "window.scrollY" is ALWAYS 0, so, when PTR calls the function "shouldPullToRefresh" the answer is TRUE, even if im not at the top of screen. Any sugest?

Try providing your own shouldPullToRefresh() function in order to see why window.scrollY is always zero, there you can test other props on window (cordova-specific may be?) to see of any works for you.

I'm closing this issue, the JSFiddle is not working and therefore we aren't able to reproduce the issue. Please feel free to open another issue making sure the JSFiddle is working, as well as testing it on web and mobile browsers.

Thanks for the help guys. :)


Change timeout for email resend to 10 Minutes

🍰 Pullrequest

Issues

None

Todo

[X] None

Sorry, another branch is slipped into this PR also.
It's add the basis for a new Test ( Test Json Create Transaction call ) and handle an error which occure not really often.


When I set a different difficulty for each hole in the terminal room, I don’t know how to set the difficulty for CustomWarp: true of 2A or 5AB.

CustomWarps are assumed to be "free" transitions. If you need one of them to be gated by something, you should put it in a subroom, and add an internal edge between your subrooms which has requirements attached.

Ah thanks i get it


Client error HTTP 413 when pushing

Trying to push a large amount of data through LFS I can upload a significant portion of it, but then I get an HTTP error 413 ("Request entity too large").
$ git lfs version
git-lfs/0.5.4 (GitHub; darwin amd64; go 1.4.2)
$ git lfs status
On branch lfs
Git LFS objects to be pushed to origin/lfs:

[ 28 files totalling ~ 37 GB ]

Git LFS objects to be committed:

Git LFS objects not staged for commit:

$ git push
(10 of 28 files) 5.01 GB 13m29s
Validation Failed
Docs: https://help.github.com/enterprise
Validation Failed
Docs: https://help.github.com/enterprise
Validation Failed
Docs: https://help.github.com/enterprise
Validation Failed
Docs: https://help.github.com/enterprise
Validation Failed
Docs: https://help.github.com/enterprise
Validation Failed
Docs: https://help.github.com/enterprise
Validation Failed
Docs: https://help.github.com/enterprise
Client error: https://GH_DOMAIN/files/media/GH_USER/REPO/object/SOME_HASH from HTTP 413
error: failed to push some refs to 'git@GH_DOMAIN:GH_USER/REPO.git'

(where GH_DOMAIN is our GitHub Enterprise instance, GH_USER and REPO are my user account and the repository there, respectively, and SOME_HASH appears to refer to a file stored under .git/lfs/objects/SO/ME/SOME_HASH that is 1.4 GB in size.)

There's a 1GB limit for single objects in GitHub Enterprise. We plan to increase this to 2GB in the next 2.2/2.3/2.4 releases. Closing this since it has nothing to do with the OSS project.  Please hit up<EMAIL_ADDRESS>(or go through your normal Enterprise support procedure) if you want to talk further about it.

I see, thanks for the explanation!


Support MemConfs with very deep memories

Checklist

[x] Did you specify the type of improvement?
[x] Did you state the API impact?
[x] Did you specify the code generation impact?
[x] Did you request a desired merge strategy?

Type of Improvement

bug fix
new feature/API

API Impact
Fixes API to properly support very deep memories.
Backend Code Generation Impact
No impact
Desired Merge Strategy

Squash: The PR will be squashed and merged (choose this if you have no preference

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

General question: at what point should things be Int vs BigInt?


Move github event host infra to github.common, consume the installation even in the PullRequestQuantifier.Repository.Service ( use diff subscription name for it in service bus)

1.Move github event host infra to github.common, consume the installation even in the PullRequestQuantifier.Repository.Service ( use diff subscription name for it in service bus)
2. No logic changes in this PR

Codecov Report

Merging #133 (58635c7) into main (1b6cdb2) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #133   +/-   ##
=======================================
  Coverage   60.09%   60.09%
=======================================
  Files          47       47
  Lines        1318     1318
=======================================
  Hits          792      792
  Misses        526      526

Impacted Files
Coverage Δ

...tHub.Client/Controllers/GitHubWebhookController.cs
100.00% <ø> (ø)

...er.GitHub.Client/Events/PullRequestEventHandler.cs
81.81% <ø> (ø)

...s/PullRequestQuantifier.GitHub.Client/Registrar.cs
100.00% <ø> (ø)

...Quantifier.GitHub.Common/Events/GitHubEventHost.cs
78.57% <ø> (ø)

....Common/GitHubClient/GitHubClientMessageHandler.cs
0.00% <ø> (ø)

...r.GitHub.Common/Events/InstallationEventHandler.cs
34.61% <100.00%> (ø)

...mon/Events/InstallationRepositoriesEventHandler.cs
26.92% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1b6cdb2...ac401f3. Read the comment docs.


Make TryInsert functions within the packages module use INSERT ... ON CONFLICT

The TryInsert* functions within the packages models make incorrect assumptions
about transactional isolation within most databases. It is perfectly possible for
a SELECT to return nothing but an INSERT fail with a duplicate in most DBs as it
is only INSERT that the locking occurs.
This PR introduces a common InsertOnConflictDoNothing function which will attempt
to INSERT provided bean but will return 0 as the number of rows affected if there is a
conflict.
Fix #19586
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

ugh looks like my worries about transactions were right - we're gonna need to use an upsert style...

I'm going to have to mark this WIP as we actually have to use the UPSERT forms otherwise the transactions will fail.

OK I think this is now ready for review.
I do think this kind of upsert style is a far better way of doing this than the current hacky and really quite racy style.

Are there dedicated tests for InsertOnConflictDoNothing with all databases? Otherwise it would be very difficult to debug or improve it.

Codecov Report

Merging #21063 (a941cba) into main (769be87) will decrease coverage by 0.01%.
The diff coverage is 46.87%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main   #21063      +/-   ##
==========================================
- Coverage   47.37%   47.36%   -0.01%
==========================================
  Files        1111     1111
  Lines      150018   150290     +272
==========================================
+ Hits        71065    71185     +120
- Misses      70531    70669     +138
- Partials     8422     8436      +14

Impacted Files
Coverage Δ

models/db/common.go
41.24% <41.26%> (+1.24%)
:arrow_up:

models/packages/package_version.go
85.23% <75.00%> (+0.87%)
:arrow_up:

models/packages/package.go
47.50% <76.47%> (+0.91%)
:arrow_up:

models/packages/package_file.go
76.61% <77.77%> (+1.41%)
:arrow_up:

modules/migration/issue.go
63.63% <0.00%> (-16.37%)
:arrow_down:

modules/indexer/stats/queue.go
50.00% <0.00%> (-9.10%)
:arrow_down:

modules/process/manager_exec.go
86.04% <0.00%> (-6.98%)
:arrow_down:

modules/notification/mail/mail.go
29.41% <0.00%> (-2.95%)
:arrow_down:

modules/log/event.go
58.18% <0.00%> (-2.10%)
:arrow_down:

modules/notification/ui/ui.go
60.34% <0.00%> (-1.73%)
:arrow_down:

... and 19 more

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

If I understand correctly, the test cases haven't cover the behavior of comment:

// This function will update the ID of the provided bean if there is an insertion

If I understand correctly, there are still some problems in code:

the has is misleading.

If insertion succeeds, it returns true, nil, if insertion fails, it returns false, nil
So the meaning of bool in (bool, error) is: whether the insertion succeeds, not about  whether the record existed before.

assert.NotEqual(t, int(0), int64(0)) always succeeds, But the ID is a int64, so you must use NotEqualValues or NotEmpty, otherwise the test code like assert.NotEqual(t, 0, toInsert.ID) always succeeds.

There is only one ON CONFLICT DO NOTHING for SQLite3, I do not understand why it would return the ID for the duplicated insertion.

The MySQL is highly like to use update id=last_insert_id(id), but not update id=id, the second one doesn't seem the proper way to update the LAST_INSERT_ID for MySQL.

Looks like things become too complex to difficult to review.

If I understand correctly, the test cases haven't cover the behavior of comment:

It feels a bit like you're being deliberately obstructive and I don't quite understand why you're being this way.
This might be a language issue - but there are better ways to say I think you should add a line that checks if the ID remains at 0.
To which I might reply why would we care and why are you being so bloody difficult about it? That the ID remains unchanged is irrelevant. Fine I'll add it but honestly it's just making the test less clear and less easy to read for zero real world benefit.
It feels like you're targeting me for some reason and I don't understand why. You left maintainers - was it because of me?

If I understand correctly, there are still some problems in code:

the has is misleading.

If insertion succeeds, it returns true, nil, if insertion fails, it returns false, nil
So the meaning of bool in (bool, error) is: whether the insertion succeeds, not about  whether the record existed before.

I was using has as in «has been inserted» but I agree inserted would be better. Frankly its minor and you should just say use inserted instead of has instead of making some major issue about it.

assert.NotEqual(t, int(0), int64(0)) always succeeds, But the ID is a int64, so you must use NotEqualValues or NotEmpty, otherwise the test code like assert.NotEqual(t, 0, toInsert.ID) always succeeds.

Again just make a suggestion. It's a good catch that I forgot about it but your tone is frankly insulting.

There is only one ON CONFLICT DO NOTHING for SQLite3, I do not understand why it would return the ID for the duplicated insertion.

I don't understand your question?
There are two cases:

INSERT proceeds because there is no conflict. The SQLite driver will return the inserted id because SQLite always does not.
INSERT fails because there is a conflict.

In the second case we do not get an ID. Nor do we attempt to use it because 0 rows are affected.

The MySQL is highly likely needed to use update id=last_insert_id(id), but not update id=id. The second one doesn't seem the proper way to update the LAST_INSERT_ID for MySQL.

This code is not attempting to update the id in fact it is deliberately not attempting to cause an update to the id - without the ON DUPLICATE KEY UPDATE id = id there is no ON CONFLICT DO NOTHING.

It feels a bit like you're being deliberately obstructive and I don't quite understand why you're being this way.

I am not obstructive, but really want to help, I have tested a lot on my side.
I have tested SQLite3 and MySQL. I do not think your code could work for these cases, and the tests were incorrect.
For SQLite, you need: insert ... on conflict update set id=id returning id
For MySQL, you need: insert ... on duplicate key update id=last_insert_id(id)
That's all.

but your tone is frankly insulting.

Sorry I didn't mean that. But just want make the problem clear. Could you suggest about how to express the problem more gently.
We can have a private chat with the SQL problems later.

We don't use or get the ID when the INSERT fails because there is a conflict because OnConflictDoNothing.

I have tested SQLite3 and MySQL. I do not think your code could work for some cases, and the tests were incorrect.
For SQLite, insert ... on conflict update set id=id returning id (do nothing doesn't work and won't return the id)

Clearly I need to separate out the code paths here.
There is no RETURNING in the SQLite code. The RETURNING is only used in Postgres.
SQLite will always return the last inserted ID as part of its driver so we don't need to do that.
If there is a conflict we don't use it - we do nothing.

For MySQL, insert ... on duplicate key update id=last_insert_id(id)

No. As far as I can see that would cause every conflict to cause an update of the primary key (or fail.)
The code as written: ON DUPLICATE KEY UPDATE id = id makes the UPDATE a no-op so that no row is changed i.e. NOTHING happens when there is a conflict.
Again the code is not attempting to return the ID when there is a conflict.

And the test has to cover: insert(keyA), insert(keyB), insert(keyA) and assert getting A-id

See above, the code does not promise to get the ID when there is a conflict. It promises to do nothing.

There is still no comment about why INSERT IGNORE doesn't work for MySQL in such case. (there was just a joking for the first question #21063 (comment) , I am not good enough to guess).

Using INSERT IGNORE didn't work in my testing when there was a primary key with autoincrement - and if I didn't instead use the ON DUPLICATE KEY UPDATE no-op it would error out. This may have been warnings being returned rather than errors.
It seems however now that INSERT IGNORE will just work by itself but I do wonder if the warnings that IGNORE could cause failures or complaints by users.

And, maybe I really misunderstood something -- about the design or about the logic (no comment nor test at the beginning), I do not know. Maybe the divergence starts here #21063 (comment): "The code auto fills the ID of the bean in the same way that xorm's Insert() does.": The bean should has the ID filled when there is no error.

Ah. Perhaps that is the problem.
I'm not promising to get the ID when there is no insert.
The function has comment on it that says it will update the ID of the provided bean if it is inserted. It doesn't say it will do that when it's not inserted - and in fact it will NOT do that - instead on conflict it will do nothing as the function name suggests.
// InsertOnConflictDoNothing will attempt to insert the provided bean but if there is a conflict it will not error out
// This function will update the ID of the provided bean if there is an insertion
// This does not do all of the conversions that xorm would do automatically but it does quite a number of them
// once xorm has a working InsertOnConflictDoNothing this function could be removed.

There were always tests - just not specific ones. The package repositories code has good coverage of this function. As requested though I've added some specific tests and covered and fixed some more edge cases which should make the function usable in other contexts too.

Using INSERT IGNORE didn't work in my testing when there was a primary key with autoincrement - and if I didn't instead use the ON DUPLICATE KEY UPDATE no-op it would error out. This may have been warnings being returned rather than errors.
It seems however now that INSERT IGNORE will just work by itself but I do wonder if the warnings that IGNORE could cause failures or complaints by users.

From my knowledge, I always use INSERT IGNORE for all cases  and  haven't got any problem. That's why the question first came ....  because in my mind:

INSERT IGNORE should  be fine  for all cases, I  never  thought any user  would be surprised or affected by the warning. If  XORM is affected  by the warning, that's  another story. (if there was a comment for it, I  could also get the point as early as  possible).
Then after being told that the  IGNORE  doesn't work for autoincrement, I thought that  since the insert  on dup update id=id trick is used, it must be done by purpose to get  the conflicted ID according to  another comment, then the discussion happens.

Thank you for letting me  know more  details.
Anyway, it's clear for me now. I think this PR is good  to have,  maybe it could help  to remove the workaround mutex for the package code after it gets merged:

#21862
https://github.com/go-gitea/gitea/pull/21862/files#diff-239d7f1fa93717ce75c12a91af1cc9f9d585993f7a1da9b5a507606689df4994R39-R41

Ah yes that mutex can be removed too.
Apologies for the confusion earlier - it just felt we were going round and round in circles for no good reason and I couldn't understand why.

Thanks for your hard-working @zeripath . It really should be a part of XORM. :)

How about taking this PR now, and move to XORM in the future?
The "workaround mutex" really seems fragile, if there is a chance, we could use a DB insert-ignore instead of that in-progress mutex for a stable release.

I think the key problem is the package property table have no unique keys. per https://github.com/go-gitea/gitea/pull/30335#issuecomment-2051982310


[Question] Locally run

Hi, would it be possible to have one that runs locally (stable diffusion and oobabooga webui) since it would be fun run for my friends
If anyone does this let me know!

Maybe you could create a fork that does this, I don't think it will work as good tho, and you would need a model like llava that has vision capabilities running in local, at least until someone makes Mixtral moe with vision and the bloke makes the quant version

sure, the docker-compose already has a local redis and a minio (replacing redis cloud and s3). all you'd need to add are local model servers and then some routing. feel free to fork or PR


Allow README.md to be blog index file name

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
see packages/docusaurus-plugin-content-blog/src/blogUtils.ts:146:
  const text = blogSourceRelative.replace(/(?:\/index)?\.mdx?$/, '');
  const slug = `/${text}`;
  return {date: undefined, text, slug};

It's easy to add the support of rendering index.md, readme.md, etc. to be the index page if there are only one unique file (with these possible names) under a specific folder.
As far as I know, many blog framewroks support both index.md and readme.md to be rendered as the index page.
Has this been requested on Canny?
No response
Motivation
The github use the default readme.md (or README.md, which is case-insensitive) as the default rendered file.
Hence, there are a lot of projects (including blog) with their introduction file naming with readme.md rather than index.md.
So it would be quite delightful if we docusaurus can support this design.
API design
I feel it OK with either an extra API field for our users to manually point out what index filename is the best, or just do a litter more work in our blogUtils logic, in order to translate the md file to slug accuarately.
Have you tried building it?
No response
Self-service

[X] I'd be willing to contribute this feature to Docusaurus myself.

We should allow README.md as index page as well, yes. At least removing it from the URL. We can re-use the category index logic from the docs plugin.
Any more ideas @slorber?

Note: ./blog/xyz/readme.md already works, it's just it will have a weird URL like /blog/abc/readme

That makes sense to me to reuse the same category index logic by default.
/blog/xyz/xyz.md should also lead to /blog/xyz instead of /blog/xyz/xyz
Not sure it's worth it to make configurable considering it only affects the URL, and we already have the slug frontmatter for overrides
Do you want to submit a PR @MarkShawn2020 ?

Note: ./blog/xyz/readme.md already works, it's just it will have a weird URL like /blog/abc/readme
That makes sense to me to reuse the same category index logic by default.
/blog/xyz/xyz.md should also lead to /blog/xyz instead of /blog/xyz/xyz
Not sure it's worth it to make configurable considering it only affects the URL, and we already have the slug frontmatter for overrides
Do you want to submit a PR @MarkShawn2020 ?

I do think it worthwhile to offer better experience for our users.
And what you mentioned here 'xyz/xyz.md  --> /xyz' is also reasonable since I do have some document named as the same as its folder (e.g. at first, you wrote a markdown file, and later you leveled it up with a same-named directory, and moved the file into it, and you would expect the slug to be rendered as the folder name rather than the file path).
I'm afraid that I had to check the category index logic first before I decided to submit a PR, in order to provide a best engineering.

Note: ./blog/xyz/readme.md already works, it's just it will have a weird URL like /blog/abc/readme
That makes sense to me to reuse the same category index logic by default.
/blog/xyz/xyz.md should also lead to /blog/xyz instead of /blog/xyz/xyz
Not sure it's worth it to make configurable considering it only affects the URL, and we already have the slug frontmatter for overrides
Do you want to submit a PR @MarkShawn2020 ?

BTW, I'm not a fan of front-matters, lol. I prefer using as less front-matter fields as I can for compatability reasons.

If you make blog/x/x.md aliased as blog/x then users should have a way to make blog/x/index.md a 404 in case someone doesn't want this behavior and explicitly doesn't want an index file.


Apply develocity and gradle-enterprise-conventions-plugin to included build

Otherwise it complains:

The build cache configuration of the root build differs from the
build cache configuration of the early evaluated ':build-logic-settings'
included build. It is recommended to keep them consistent.

I have squashed this PR as 24a190c1e6a81d0a6c7d05a3e867608d0975fcea

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build


fix(plugin-legacy): wrap chunks in IIFE

Description
Solving the same problem as #2972, but contains tests and source map support (sorry for the duplicate, but original PR is not changed since the April and this bug block migration of the large codebase from the CRA to Vite).
If someone comes from google, it solves global scope pollution issues like:

Can't create duplicate variable: '_excludes', redeclaration of const _excludes or Identifier '_excludes' has already been declared errors caused by @babel/plugin-desctructuring (example)

Issues with styled-components or emotion caused by @babel/plugin-transform-template-literals (example)

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

I think we would need to keep the map from babel, and that's why the original PR get blocked since MagicString does not take source map input, while I am not familiar with babel transforming to support sourcemap

@antfu thanks for the quick review! I've changed implementation to use babel plugin for transformations, so source map behavior should not change

@antfu @patak-js sorry if I'm being annoying, but is there any release plan for that fix?

We'll do a release on Monday or Tuesday including this fix

@umidbekk<EMAIL_ADDRESS>has been released including this PR


wsus + timeline updates

Rendered articles for review:
Managing WebView2 applications
https://review.docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/enterprise?branch=pr-en-us-1568
Introduction to Microsoft Edge WebView2
https://review.docs.microsoft.com/en-us/microsoft-edge/webview2/?branch=pr-en-us-1568

Docs Build status updates of commit 25a4708:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 28b90cd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/concepts/enterprise.md
:white_check_mark:Succeeded
View

microsoft-edge/webview2/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 678e860:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/concepts/enterprise.md
:white_check_mark:Succeeded
View

microsoft-edge/webview2/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1643c8f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/concepts/enterprise.md
:white_check_mark:Succeeded
View

microsoft-edge/webview2/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit d94e3ce:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/concepts/enterprise.md
:white_check_mark:Succeeded
View

microsoft-edge/webview2/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


database/sql: Ability to timeout when wating for the connection from the pool

Issue is partially related to golang/go#8874.
We are facing a problem under heavy load when the connection pool is full and lots of connection requests are in internal database/sql queue.
The result is that all go routines that suppose to handle queries stacks and accumulates on the background. Query time itself can be at least controlled by driver specific statement timeout. But nothing controls connection queue. So if you have enough clients, query can be executed few seconds / minutes after client hits API. Obviously for no reason since API already returned timeout. Support for go context would be the best for query and connections but it would require lot of invasive changes, i guess.
So my proposal is to have poolTimeout.
type DB struct {
    ....
    var poolTimeout time.Duration
}

func (db *DB) SetPoolTimeout(t time.Duration) {
	db.mu.Lock()
	db.poolTimeout = t
	if t < 0 {
		db.poolTimeout = 0
	}
	db.mu.Unlock()
}

// and change function
func (db *DB) conn(strategy connReuseStrategy) (*driverConn, error) {
...

//from
req := make(chan connRequest, 1)
db.connRequests = append(db.connRequests, req)
db.mu.Unlock()
ret := <-req

//to
req := make(chan connRequest, 1)
db.connRequests = append(db.connRequests, req)
db.mu.Unlock()
if db.poolTimeout == 0 {
  ret := <-req
} else {
  select {
  case ret := <-req:
  	return ret.conn, ret.err
  case <- time.After(db.poolTimeout):
  	go func(result chan connRequest) {
  		c := <- result
  		if !db.closed {
  		  	db.putConn(c.conn, nil)
  		}
  	}(req)
  	return nil, driver.ErrPoolTimeout
  }
}

Yes, I face this problem too, when I use SetMaxOpenConns.
Your solution is a good way.
I think there is a small place to be able to modify
db.putConn(c.conn, nil)
---->
db.putConn(c.conn, c.err)

the same issue with SetMaxOpenConns

This can be solved with the addition of Context #15123 and should probably be merged in.

Closing in favor of #15123


MSC2192: Inline widgets (including polls and buttons)

Rendered
Disclaimer: This is currently a set of ideas and may not be complete or ideal.
Early implementation: https://github.com/matrix-org/matrix-react-sdk/pull/3252
For https://github.com/vector-im/riot-web/issues/10060 and related issues.

It could interesting to allow to set links in options value for m.buttons (for simple webhooks).
Like:
        "options": [
            {
                "label": "Do that",
                "value": "https://example.org/api/do?param=xxx"
            }

In this case the compatibilty body would construct links:
[Do that](https://example.org/api/do?param=xxx) -> Do that
Clients SHOULD probably ask users permissions (once) to share data with this domain

Any recommandation for edits / redacts of m.response or m.options ?

Any recommandation for poll result display by client?

See results before voting?
Display results as percent? abs value?
Show a visual indicator of current user vote

@BillCarsonFr please always use threads so things can be replied to. I've moved your comments.

Allowed HTML tags can be extended instead.


Update pvc example accordingly

What this PR does / why we need it:
In the kfserving PVC examples, we mentioned training model and store into PVC by following kubeflow/examples mnist example, recently the mnist example has been updated removed related parts. The PR is going to update readme to reasonable place for training and store model to PVC and then using KFServing to deploy InferenceService.

This change is

/lgtm

/lgtm
/approve


Typos

This is mostly about grammar and spelling, though there are a few wording changes which I think are more technically accurate.  Of course, review this and make sure you agree and that nothing normative is changing.
I was going to gather all of these and just do one PR at the end.  But other people appear to be reading the spec so I'll do this intermediate PR so that others don't duplicate the effort.  Then I'll do another PR for later chapters soon.

Thanks much!


Mut to immut impls

Objective

Provide impls for mutable types to relevant immutable types.
Closes #2005

Solution

impl From for Res
impl From for NonSend
Mut to &/&mut already impl'd in change_detection_impl! macro

So, I have a few arguments in favor of supporting why we should add this functionality:

this is trivially correct to support
it is logically consistent with the ability to cast other pointers from mutable to immutable forms
it makes it possible to cleanly write APIs that take in a Res. In most cases you're going to want to take a &R, like you point out, but in some edge cases you may want to verify that the type was constructed as a resource. This is particularly interesting because of the way that users can't actually manually construct a raw Res<T> from a T
if we add more metadata to resources eventually (like which world they belong to), APIs that take a Res rather than a & become increasingly useful

I'm on board!

bors r+


Update opam with angstrom version

Angstrom.take_bigstring_while was introduced some time later than version 0.7.0. It seems 0.8.0 introduced it.

Thanks!


source-controller: Only build amd64 in presubmit

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jaxesn
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jaxesn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jaxesn: Updated the job-config configmap in namespace default at cluster default using the following files:

key source-controller-presubmits.yaml using file jobs/aws/eks-anywhere-build-tooling/source-controller-presubmits.yaml

In response to this:

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

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


Range identity got broken somehow

Fixed - it was because diagram cells are clones from atoms now - and so it needed to apply the stamp to the clone (not the original value)


Add existing issues to the Development Board

Description
A clear and concise description of what the problem is or how is this feature missing.
Possible Solution(s)
A clear and concise description of what you want to happen.
Objectives
Please specify what the finished feature should accomplish (one or more objectives):

No code changes required.
[ ] Assign the Development Board to existing item's projects
[ ] Preserve old "Sprint" projects in existing items.
[ ] Assign the Start Date and Target Date for the projects based on their original sprint
[ ] Assign the latest sprint they fall into.

Additional Context
Add any other context or screenshots about the feature request here.

Blocks:

#27

Blocked by:

#28
#29

No longer blocked by any of:

#28
#29

Blocks:

#32

Have added all existing issues to the Development Board. Had to assign all of them to Sprint 1, since we could not sync their original sprints to the new Development Board iterations.


[Feature] Add Wrap Text option

Is your feature request related to a problem? Please describe.
I'm having a hard time reading the text inside the code block because there is no wrap text option.
Describe the solution you'd like
Add a wrap text option for the text inside the code block to make the text easier for users to read.
Describe alternatives you've considered
Um, nothing.
Additional context

maybe we should enable wrap text by default on mobile screen? i will add this feature later.

maybe we should enable wrap text by default on mobile screen? i will add this feature later.

Thanks for that! I really appreciate it.

I tried to enable line breaks, but it looked very strange when reading the code. So I think it's better not to enable it.
For your scenario, if you need to enable line breaks, you can use the prompt:

Do not use code block to wrap the reply, just return it in plain text format.

Alternatively, you can manually modify this part of the forked project and delete this line of code:
https://github.com/Yidadaa/ChatGPT-Next-Web/blob/9d1a84858cdd9e0c3567f54940da51c73a763b57/app/styles/markdown.scss#L826

I tried to enable line breaks, but it looked very strange when reading the code. So I think it's better not to enable it.
For your scenario, if you need to enable line breaks, you can use the prompt:

Do not use code block to wrap the reply, just return it in plain text format.

Alternatively, you can manually modify this part of the forked project and delete this line of code:
https://github.com/Yidadaa/ChatGPT-Next-Web/blob/9d1a84858cdd9e0c3567f54940da51c73a763b57/app/styles/markdown.scss#L826

Can you show me the screenshot?
Regarding the prompt, I've tried not to use a code block. But ChatGPT doesn't follow the prompt and instead explains what I input.

What screenshot do you need? Prompt, Code or ...?

What screenshot do you need? Prompt, Code or ...?

Code block with line breaks enabled.

In chat:

You can just fork this project, and delete that line of code, and deploy it on Vercel, and you will get your personalized web ui.


Obtaining operation name in LogGraph

When building a graph (#32), it is very important to obtain the name of the function that was executed to obtain each Tracked variable.
e.g.
x = param(rand(2,2))
y = param(rand(2,2))
z = x*y

I want to find the symbol * from z alone.

So far I have tried the following, but these are not consistent.
z.tracker.f.func.f
methods(z.tracker.f.func).ms[1].name
methods(z.tracker.f.func).ms[1].roots[4]
methods(z.tracker.f.func).mt.name
This may work for some operation but for other operations, I end up getting :back or Symbol(#<somenumber>))
I'm absolutely stuck here


Remove deadcode for pkg/kube

Please provide a description of this PR:

/ok-to-test

@my-git9: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
c931f7e1b075de56aad9b85762ef349d722b5e97
link
true
/test lint

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


Pseudorange can't be calculated

Satellites' signal can be received, but it can't calculate the pseudorange. What could be the reason?

there could be multiple issues

SV clock error
user clock error
ephemeris parameters error

are you feeding the latest ephemeris?

@Imtiaz08 , Hi there, in my experiment, I conducted a conductive test with u-blox receiver. In u-centre, pos. is pretty good. Then, I tested the observation file from u-blox using RTKLIB. Unfortunately, the single point positioning result is bad. I looked into the pseudorange, which is weird. Perhaps, as you mentioned, the clock terms have some issues.

@pbingxu Yes, that's because the satellite position is being calculated wrongly due to the incorrect time which is resulting in a very abnormal pseudorange.
You can try using the overtime TOE and TOC to the scenario time and then check the rhos calculated from the signal you will see a difference.

@Imtiaz08 , hi Imtiaz, thank you for your reply. (1) I'm not sure why u-center works fine, but the RINEX file is not working. Attached is the RTKPOST results using SPP mode.
(2) From a receiver's perspective, the time for calculating satellite pos. is relying on the signals that are being processed. We find it's time of transmission, which is used for calculating satellite pos. I don't understand your solution, "using the overtime TOE and TOC to the scenario time", please elaborate more. Thank you very much!

(2) when a receiver receives a signal it uses its own clock and the
satellite clock to find the time of transmission just as you mentioned.
Let's say the brdc3540.14n file was fed to the GNSS SIM and an IF signal
was generated from that file. Technically the signal will contain Toe and
Toc values as is in the RINEX file right?
While calculating the time of transmission you will see a huge difference
which will obviously calculate the position wrong and as a result, the user
position will have a very large pseudorange since rho = c*t. I hope you are
getting my point.
Now for question 1: Can you start receiving the spoofing signal and check
the pseudo-range values in the U-center, please?
On Wed, Feb 16, 2022 at 8:25 AM pbingxu @.***> wrote:

@Imtiaz08 https://github.com/Imtiaz08 , hi Imtiaz, thank you for your
reply. (1) I'm not sure why u-center works fine, but the RINEX file is not
working. Attached is the RTKPOST results using SPP mode. [image: RTKPOST
Results (SPP)]
https://user-images.githubusercontent.com/74028152/154189739-eff82f7c-4b0e-4baa-88c4-ac1937470adc.png
(2) From a receiver's perspective, the time for calculating satellite pos.
is relying on the signals that are being processed. We find it's time of
transmission, which is used for calculating satellite pos. I don't
understand your solution, "using the overtime TOE and TOC to the scenario
time", please elaborate more. Thank you very much!
—
Reply to this email directly, view it on GitHub
https://github.com/osqzss/gps-sdr-sim/issues/299#issuecomment-1041057886,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOCLKYXMG4TLQ4D4SP54LKLU3MKMBANCNFSM5EXPQUYA
.
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 were mentioned.Message ID:
@.***>

U-center takes current time for the calculation of signal transmission
time. While the signal contains toe and toc values depending on what the
RINEX file has
On Wed, Feb 16, 2022 at 9:00 AM Imtiaz Nabi @.***> wrote:

(2) when a receiver receives a signal it uses its own clock and the
satellite clock to find the time of transmission just as you mentioned.
Let's say the brdc3540.14n file was fed to the GNSS SIM and an IF signal
was generated from that file. Technically the signal will contain Toe and
Toc values as is in the RINEX file right?
While calculating the time of transmission you will see a huge difference
which will obviously calculate the position wrong and as a result, the user
position will have a very large pseudorange since rho = c*t. I hope you are
getting my point.
Now for question 1: Can you start receiving the spoofing signal and check
the pseudo-range values in the U-center, please?
On Wed, Feb 16, 2022 at 8:25 AM pbingxu @.***> wrote:

@Imtiaz08 https://github.com/Imtiaz08 , hi Imtiaz, thank you for your
reply. (1) I'm not sure why u-center works fine, but the RINEX file is not
working. Attached is the RTKPOST results using SPP mode. [image: RTKPOST
Results (SPP)]
https://user-images.githubusercontent.com/74028152/154189739-eff82f7c-4b0e-4baa-88c4-ac1937470adc.png
(2) From a receiver's perspective, the time for calculating satellite
pos. is relying on the signals that are being processed. We find it's time
of transmission, which is used for calculating satellite pos. I don't
understand your solution, "using the overtime TOE and TOC to the scenario
time", please elaborate more. Thank you very much!
—
Reply to this email directly, view it on GitHub
https://github.com/osqzss/gps-sdr-sim/issues/299#issuecomment-1041057886,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOCLKYXMG4TLQ4D4SP54LKLU3MKMBANCNFSM5EXPQUYA
.
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.

On Wed, Feb 16, 2022 at 9:03 AM Imtiaz Nabi @.***> wrote:

U-center takes current time for the calculation of signal transmission
time. While the signal contains toe and toc values depending on what the
RINEX file has
On Wed, Feb 16, 2022 at 9:00 AM Imtiaz Nabi @.***> wrote:

(2) when a receiver receives a signal it uses its own clock and the
satellite clock to find the time of transmission just as you mentioned.
Let's say the brdc3540.14n file was fed to the GNSS SIM and an IF signal
was generated from that file. Technically the signal will contain Toe and
Toc values as is in the RINEX file right?
While calculating the time of transmission you will see a huge difference
which will obviously calculate the position wrong and as a result, the user
position will have a very large pseudorange since rho = c*t. I hope you are
getting my point.
Now for question 1: Can you start receiving the spoofing signal and check
the pseudo-range values in the U-center, please?
On Wed, Feb 16, 2022 at 8:25 AM pbingxu @.***> wrote:

@Imtiaz08 https://github.com/Imtiaz08 , hi Imtiaz, thank you for your
reply. (1) I'm not sure why u-center works fine, but the RINEX file is not
working. Attached is the RTKPOST results using SPP mode. [image:
RTKPOST Results (SPP)]
https://user-images.githubusercontent.com/74028152/154189739-eff82f7c-4b0e-4baa-88c4-ac1937470adc.png
(2) From a receiver's perspective, the time for calculating satellite
pos. is relying on the signals that are being processed. We find it's time
of transmission, which is used for calculating satellite pos. I don't
understand your solution, "using the overtime TOE and TOC to the scenario
time", please elaborate more. Thank you very much!
—
Reply to this email directly, view it on GitHub
https://github.com/osqzss/gps-sdr-sim/issues/299#issuecomment-1041057886,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOCLKYXMG4TLQ4D4SP54LKLU3MKMBANCNFSM5EXPQUYA
.
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 were mentioned.Message ID:
@.***>

Ground truth location: 22.3221720833333<PHONE_NUMBER>63889 20.2386

@Imtiaz08 , I will follow your suggestions. Will update you later. Thank you so much!


[stable/mongodb] Authentication failure with mongodb

Describe the bug
When installing stable/mongodb through helm install  --name first-mongo --set "persistence.size=2Gi" stable/mongodb --namespace personservice as of version 7.0.2 (and greater) the command mongo admin --host first-mongo-mongodb --authenticationDatabase admin -u root -p $MONGODB_ROOT_PASSWORD fails to execute inside the container with the following message:
I have no name!@first-mongo-mongodb-6647bdd594-6csg6:/$ mongo admin --host first-mongo-mongodb --authenticationDatabase admin -u root -p $MONGODB_ROOT_PASSWORD
MongoDB shell version v4.0.11
connecting to: mongodb://first-mongo-mongodb:27017/admin?authSource=admin&gssapiServiceName=mongodb
2020-02-27T05:10:23.587+0000 E QUERY    [js] Error: Authentication failed. :
connect@src/mongo/shell/mongo.js:344:17
@(connect):2:6
exception: connect failed
I have no name!@first-mongo-mongodb-6647bdd594-6csg6:/$ exit
exit
command terminated with exit code 1

Version of Helm and Kubernetes:
Kubernetes version is: v1.14.10-gke.17
Helm Version is: v2.10.0
Istio: 1.3.5
Which chart:
stable/mongodb (>= 7.0.2)
What happened:
Can't authenticate with MONGODB_ROOT_PASSWORD
What you expected to happen:
Can authenticate with MONGODB_ROOT_PASSWORD
How to reproduce it (as minimally and precisely as possible):
kubectl create ns personservice
helm install  --name first-mongo --set "persistence.size=2Gi" stable/mongodb --namespace personservice
kubectl exec -n personservice <podname> /bin/bash
mongo admin --host first-mongo-mongodb --authenticationDatabase admin -u root -p $MONGODB_ROOT_PASSWORD

Anything else we need to know:
I can observe the same behaviour as described in https://github.com/istio/istio/issues/11675

Hi,
Could you confirm if you are using istio or any sidecar injection?

@javsalgar: It is definetly related. however chart version 7.0.1 works with istio. 7.0.2 does not. My hypothesis is that the script inside the container image has changed.

Hi all,
a potential workaround for this is to disable sidecar injection and to tell istio to not use mtls for all connections to the mongo db. with automatic sidecar injection enabled on the ns this can be achived as follows:

Hi,
We are currently in version 7.8.6, so there have been several changes in the container. You could try using the container version that was available in 7.0.1 to see if that helps. However, thanks for sharing the workaround, let's see if the isitio issue gets resolved :)


Editor should not squiggle R Markdown chunk name

Need special treatment of the {r ...} blocks in the parser.

Change was lost in refactorig

https://github.com/Microsoft/RTVS/commit/970cb420468cd69f0b6148d55a4847f8cd362731


Kubelet failing to come up during kube-up

During our Jenkins run, a cluster failed to initialize with a pattern like so:
Waiting for cluster initialization.

  This will continually check to see if the API for kubernetes is reachable.
  This might loop forever if there was some uncaught error during start
  up.

.......................
Attempt 1 to check Docker on node e2e-test-jenkins-minion-0t3k ... [working]
Attempt 1 to check Docker on node e2e-test-jenkins-minion-kwe2 ...

I logged into the second node to see what was going on, and found the kubelet logs seemed to be repeating themselves every couple of minutes:
I0311 18:00:36.149229    5616 server.go:329] Watching apiserver
I0311 18:00:36.150968    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/cadvisor.manifest": default.cadvisor-agent-e2e-test-jenkins-minion-kwe2 (539b5573073fb416c4943fa34aa1d813)
I0311 18:00:36.151701    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/fluentd-gcp.manifest": default.fluentd-to-gcp-e2e-test-jenkins-minion-kwe2 (cb4343fe02c5b3fdf4d3c6a277cf5c15)
I0311 18:00:56.153205    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/cadvisor.manifest": default.cadvisor-agent-e2e-test-jenkins-minion-kwe2 (539b5573073fb416c4943fa34aa1d813)
I0311 18:00:56.155224    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/fluentd-gcp.manifest": default.fluentd-to-gcp-e2e-test-jenkins-minion-kwe2 (cb4343fe02c5b3fdf4d3c6a277cf5c15)
I0311 18:01:16.156559    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/cadvisor.manifest": default.cadvisor-agent-e2e-test-jenkins-minion-kwe2 (539b5573073fb416c4943fa34aa1d813)
I0311 18:01:16.157086    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/fluentd-gcp.manifest": default.fluentd-to-gcp-e2e-test-jenkins-minion-kwe2 (cb4343fe02c5b3fdf4d3c6a277cf5c15)
I0311 18:01:36.158518    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/cadvisor.manifest": default.cadvisor-agent-e2e-test-jenkins-minion-kwe2 (539b5573073fb416c4943fa34aa1d813)
I0311 18:01:36.159168    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/fluentd-gcp.manifest": default.fluentd-to-gcp-e2e-test-jenkins-minion-kwe2 (cb4343fe02c5b3fdf4d3c6a277cf5c15)
I0311 18:01:56.160666    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/cadvisor.manifest": default.cadvisor-agent-e2e-test-jenkins-minion-kwe2 (539b5573073fb416c4943fa34aa1d813)
I0311 18:01:56.161282    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/fluentd-gcp.manifest": default.fluentd-to-gcp-e2e-test-jenkins-minion-kwe2 (cb4343fe02c5b3fdf4d3c6a277cf5c15)
I0311 18:02:16.162795    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/cadvisor.manifest": default.cadvisor-agent-e2e-test-jenkins-minion-kwe2 (539b5573073fb416c4943fa34aa1d813)
I0311 18:02:16.163565    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/fluentd-gcp.manifest": default.fluentd-to-gcp-e2e-test-jenkins-minion-kwe2 (cb4343fe02c5b3fdf4d3c6a277cf5c15)
I0311 18:02:36.165060    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/cadvisor.manifest": default.cadvisor-agent-e2e-test-jenkins-minion-kwe2 (539b5573073fb416c4943fa34aa1d813)
I0311 18:02:36.165626    5616 file.go:209] Got pod from file "/etc/kubernetes/manifests/fluentd-gcp.manifest": default.fluentd-to-gcp-e2e-test-jenkins-minion-kwe2 (cb4343fe02c5b3fdf4d3c6a277cf5c15)
I0311 18:02:36.256496    6116 server.go:149] Using root directory: /var/lib/kubelet
I0311 18:02:36.256574    6116 docker.go:798] Connecting to docker on unix:///var/run/docker.sock
I0311 18:02:36.257908    6116 util.go:40] Sending events to api server.
I0311 18:02:36.258010    6116 server.go:315] Adding manifest file: /etc/kubernetes/manifests
I0311 18:02:36.258027    6116 file.go:51] Watching path "/etc/kubernetes/manifests"
I0311 18:02:36.258039    6116 server.go:329] Watching apiserver

Checking monit, yup:
[UTC Mar 11 18:44:38] error    : 'kubelet' failed, cannot open a connection to INET[localhost:10250/healthz] via TCP
[UTC Mar 11 18:44:38] info     : 'kubelet' trying to restart
[UTC Mar 11 18:44:38] info     : 'kubelet' stop: /etc/init.d/kubelet
[UTC Mar 11 18:44:38] info     : 'kubelet' start: /etc/init.d/kubelet
[UTC Mar 11 18:46:38] error    : 'kubelet' failed, cannot open a connection to INET[localhost:10250/healthz] via TCP
[UTC Mar 11 18:46:38] info     : 'kubelet' trying to restart
[UTC Mar 11 18:46:38] info     : 'kubelet' stop: /etc/init.d/kubelet
[UTC Mar 11 18:46:38] info     : 'kubelet' start: /etc/init.d/kubelet

Jenkins is currently disabled to allow live debugging of the issue. Raising to P0 until we get Jenkins back.
cc @dchen1107 @ixdy

I can login to the node and working on it now.

Here is what happened: Docker daemon is hung during startup phase:
root@e2e-test-jenkins-minion-kwe2:/var/log# date
Wed Mar 11 20:43:07 UTC 2015

root@e2e-test-jenkins-minion-kwe2:/var/log# cat docker.log
...
time="2015-03-11T17:58:24Z" level="info" msg="Received signal 'terminated', starting shutdown of docker..."
time="2015-03-11T17:58:24Z" level="error" msg="Error logging event die for 78c08a2f5bf3258d62513769345c87a062f0c734a27ea3fbb566a341630a0b0a: engine is shutdown"
time="2015-03-11T17:58:24Z" level="info" msg="+job release_interface(78c08a2f5bf3258d62513769345c87a062f0c734a27ea3fbb566a341630a0b0a)"
time="2015-03-11T17:58:24Z" level="error" msg="Error on iptables delete: iptables failed: iptables -t nat -D DOCKER -p tcp -d 0/0 --dport 4194 ! -i docker0 -j DNAT --to-destination <IP_ADDRESS>:8080: iptables: No chain/target/match by that name.\n (exit status 1)"
time="2015-03-11T17:58:24Z" level="info" msg="-job release_interface(78c08a2f5bf3258d62513769345c87a062f0c734a27ea3fbb566a341630a0b0a) = OK (0)"
time="2015-03-11T17:58:24Z" level="error" msg="Error logging event die for 8bc1008627c5437ce802da3f9bb07a841d4066085bd805680789dc1d0f48c7ec: engine is shutdown"
time="2015-03-11T17:58:25Z" level="info" msg="+job init_networkdriver()"
time="2015-03-11T17:58:25Z" level="info" msg="-job init_networkdriver() = OK (0)"
time="2015-03-11T17:58:25Z" level="info" msg="WARNING: Your kernel does not support cgroup swap limit."
time="2015-03-11T17:58:25Z" level="info" msg="Loading containers: start."
....
time="2015-03-11T17:58:25Z" level="info" msg="Loading containers: done."
time="2015-03-11T17:58:25Z" level="info" msg="docker daemon: 1.5.0 a8a31ef; execdriver: native-0.2; graphdriver: aufs"
time="2015-03-11T17:58:25Z" level="info" msg="+job acceptconnections()"
time="2015-03-11T17:58:25Z" level="info" msg="-job acceptconnections() = OK (0)"
time="2015-03-11T17:58:24Z" level="info" msg="+job serveapi(unix:///var/run/docker.sock)"
time="2015-03-11T17:58:25Z" level="info" msg="Listening for HTTP on unix (/var/run/docker.sock)"

But nono docker CLI calls return, including 'docker version'. Monit now does healthcheck on kubelet, which in turns to query docker version, which never response and timeout, and cause a kubelet restart.
Looking into why docker daemon hang forever.

Ok, that docker daemon on a terrible state, and all docker API requests hang. This is known issue from docker since I personally reported twice. The current active one is docker/docker/issues/9605.

I tried to strace docker process for about 20 seconds, and nothing is interesting except one thread stucking at read syscall forever:

root@e2e-test-jenkins-minion-kwe2:/var/log# cat /tmp/docker.out.4644
21:01:43.287143 read(6, root@e2e-test-jenkins-minion-kwe2:/var/log#

I sent SIGQUIT to docker daemon. Docker is shutdown, and restart by monit. From below log, one can notice that there is a huge gap between time="2015-03-11T17:58:25Z" and time="2015-03-11T21:06:06Z"

root@e2e-test-jenkins-minion-kwe2:/var/log# kill -QUIT 4644
root@e2e-test-jenkins-minion-kwe2:/var/log# tail -f docker.log
/usr/bin/docker already running.
time="2015-03-11T17:58:24Z" level="info" msg="Received signal 'terminated', starting shutdown of docker..."
time="2015-03-11T17:58:24Z" level="error" msg="Error logging event die for 78c08a2f5bf3258d62513769345c87a062f0c734a27ea3fbb566a341630a0b0a: engine is shutdown"
time="2015-03-11T17:58:24Z" level="info" msg="+job release_interface(78c08a2f5bf3258d62513769345c87a062f0c734a27ea3fbb566a341630a0b0a)"
time="2015-03-11T17:58:24Z" level="error" msg="Error on iptables delete: iptables failed: iptables -t nat -D DOCKER -p tcp -d 0/0 --dport 4194 ! -i docker0 -j DNAT --to-destination <IP_ADDRESS>:8080: iptables: No chain/target/match by that name.\n (exit status 1)"
time="2015-03-11T17:58:24Z" level="info" msg="-job release_interface(78c08a2f5bf3258d62513769345c87a062f0c734a27ea3fbb566a341630a0b0a) = OK (0)"
time="2015-03-11T17:58:24Z" level="error" msg="Error logging event die for 8bc1008627c5437ce802da3f9bb07a841d4066085bd805680789dc1d0f48c7ec: engine is shutdown"
time="2015-03-11T17:58:25Z" level="info" msg="+job init_networkdriver()"
time="2015-03-11T17:58:25Z" level="info" msg="-job init_networkdriver() = OK (0)"
time="2015-03-11T17:58:25Z" level="info" msg="WARNING: Your kernel does not support cgroup swap limit."
time="2015-03-11T17:58:25Z" level="info" msg="Loading containers: start."
....
time="2015-03-11T17:58:25Z" level="info" msg="Loading containers: done."
time="2015-03-11T17:58:25Z" level="info" msg="docker daemon: 1.5.0 a8a31ef; execdriver: native-0.2; graphdriver: aufs"
time="2015-03-11T17:58:25Z" level="info" msg="+job acceptconnections()"
time="2015-03-11T17:58:25Z" level="info" msg="-job acceptconnections() = OK (0)"
time="2015-03-11T17:58:24Z" level="info" msg="+job serveapi(unix:///var/run/docker.sock)"
time="2015-03-11T17:58:25Z" level="info" msg="Listening for HTTP on unix (/var/run/docker.sock)"
time="2015-03-11T21:06:06Z" level="info" msg="Received signal 'quit', starting shutdown of docker..."
time="2015-03-11T21:06:46Z" level="info" msg="+job serveapi(unix:///var/run/docker.sock)"
time="2015-03-11T21:06:46Z" level="info" msg="Listening for HTTP on unix (/var/run/docker.sock)"
time="2015-03-11T21:06:46Z" level="info" msg="+job init_networkdriver()"
time="2015-03-11T21:06:46Z" level="info" msg="-job init_networkdriver() = OK (0)"
time="2015-03-11T21:06:46Z" level="info" msg="WARNING: Your kernel does not support cgroup swap limit."
time="2015-03-11T21:06:46Z" level="info" msg="Loading containers: start."
....
time="2015-03-11T21:06:46Z" level="info" msg="Loading containers: done."
time="2015-03-11T21:06:46Z" level="info" msg="docker daemon: 1.5.0 a8a31ef; execdriver: native-0.2; graphdriver: aufs"
time="2015-03-11T21:06:46Z" level="info" msg="+job acceptconnections()"
time="2015-03-11T21:06:46Z" level="info" msg="-job acceptconnections() = OK (0)"
time="2015-03-11T21:06:46Z" level="info" msg="GET /version"
time="2015-03-11T21:06:46Z" level="info" msg="+job version()"
time="2015-03-11T21:06:46Z" level="info" msg="-job version() = OK (0)"
time="2015-03-11T21:06:46Z" level="info" msg="GET /containers/json?all=1"
time="2015-03-11T21:06:46Z" level="info" msg="+job containers()"
time="2015-03-11T21:06:46Z" level="info" msg="-job containers() = OK (0)"

Monit now restart docker daemon:

[UTC Mar 11 21:06:46] info     : 'kubelet' start: /etc/init.d/kubelet
[UTC Mar 11 21:06:46] error    : 'docker' process is not running
[UTC Mar 11 21:06:46] info     : 'docker' trying to restart
[UTC Mar 11 21:06:46] info     : 'docker' start: /etc/init.d/docker
[UTC Mar 11 21:08:46] info     : 'kubelet' connection succeeded to INET[localhost:10250/healthz] via TCP
[UTC Mar 11 21:08:46] info     : 'docker' process is running with pid 19863

Assuming there are always docker API request hang issues, we should detect such issue, and restart docker like what I did for kubelet. Meanwhile, we shouldn't fail kubelet's healthcheck when docker API hang.

This is part of #2884

Thanks for the quick fix!


2d dct FLOPs computing method

Hi, I noticed that in your paper you computed FCAnet model FLOPs.
I wonder how do you compute the FLOPs of 2d dct?  Could you provide your formula or code?
Thanks!

We compute the weight of 2d dct during initialization. The dct kernel is fixed and has no extra computation cost in the training phase.

We compute the weight of 2d dct during initialization. The dct kernel is fixed and has no extra computation cost in the training phase.

Thanks.
Leave the paper aside. Do you know how to compute the FLOPs of 2d dct?
If you can provide me some idea or code or fomula about that, I will be thanks so much:)

@TianhaoFu
The realization of 2d dct is actually element product. For a image with a size h x w and a dct basis with a size of h x w, the re would be total hw times of multiplication.

The FLOPs is calculated by: https://github.com/sovrasov/flops-counter.pytorch

Thanks


Grade incomplete solutions?

I’m writing a program intended to check the validity of the tests proposed by the teachers.
The idea is to have them write several “essays”, that are more or less correct copies of students inside an essay directory inside each exercise directories. Each essay will be associated to the grade the teacher expects a student to have for this essay.
Then, the program would grade them to see if the expected grade matches the generated one. The goal is to detect errors in the test function or in the solution.
I’m using the grade functionality of the learn-ocaml command. Sadly, I didn’t find a way to fetch the score obtained by a graded essay (with --grade-student). For example, if I use learn-ocaml grade --display-progression in the exercise directory, I get full points as the solution is tested, which is correct. That also gets printed on the screen. Same if I grade a correct solution. But if I grade an incorrect solution, I only get “Failure” and no more informations, even though some answers are correct. The generated grade misses, so I can’t check it against the defined one.
To put it in a nutshell, I think it would be interesting to give the grade obtained when using grade from the command line instead of just outputting “Failure”.

The interface of the grade command is indeed quite rough (ported directly from the old learnocaml-grader exec) and clearly needs to be rewritten. Adding this to the to-do list.
Related to #41 in this regard.

Closed by #63


[Feature Request] Can Expand/Hide encapsulate into a component

Existing Component
否
Component Name
Expand/Hide
Description
Can Expand/Hide in the document encapsulate into a component
I think it very useful

Sorry, we have no plan to support this.


ell: 0.65 -> 0.66, iwd: 2.17 -> 2.18

Description of changes
iwd: 2.17 -> 2.18
Changes: https://git.kernel.org/pub/scm/network/wireless/iwd.git/tree/ChangeLog?h=2.18
ell: 0.65 -> 0.66
Changes: https://git.kernel.org/pub/scm/libs/ell/ell.git/tree/ChangeLog?h=0.66

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

Fails new dbus test dbus-daemon[8603]: Failed to start message bus: Failed to lookup host/port: "*:14046": Name or service not known (-2)

Fails new dbus test dbus-daemon[8603]: Failed to start message bus: Failed to lookup host/port: "*:14046": Name or service not known (-2)

Added a local revert for newly added test in https://git.kernel.org/pub/scm/libs/ell/ell.git/patch/?id=7863e06b18b9cce56392b65928e927297108337d
I think we are hitting this dbus bug: https://gitlab.freedesktop.org/dbus/dbus/-/issues/28
Ready for review.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4184


Block Virtual keyboard on Request Money Page

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/7023
Tests | QA Steps

Go to staging.new.expensify.com on Mobile Web.
Log in with any account
Tap on Green Plus button
Tap on Split/Request money.
Tap on Amount field.
No virtual keyboard should pop up.

[x] Verify that no errors appear in the JS console

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web | Desktop

Mobile Web

iOS

Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @chiragsalian in version: 1.1.29-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by @roryabraham in version: 1.1.30-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Insert demo data

We want to start the app with demo posts, users, comments and upvotes using https://github.com/kamp-us/monorepo/blob/dev/apps/pano/prisma/seed.ts

Hey, I can handle this issue.


⚠ Bofrost.es has degraded performance

In 2a6121c, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1790 ms

Resolved: Bofrost.es performance has improved in 7bc59a3 after 6 minutes.


Use iterable instead of array?

https://github.com/zendframework/zend-expressive-authentication/blob/2fea5529d78cddc26921e46e87ea886ccb8cc7d1/src/UserInterface.php#L24
I'm looking to implement RBAC and DoctrineORM with this, changing the return type to iterable instead of array would allow the use of a Collection (of RoleInterface's). 7.1 is the minimum version of this component.
Any problems with this approach? I wanted to ask before just submitting a PR.

Works for me.


Support for new NDKs

Are you planning to support new NDKs? Currently, r19c and r20-beta2 don't work with the android example.

Yes, we are adding CMake build which support r19c.

@gasgallo we have supported r19c with CMake build in the latest release.


Add license to gemspec

@kern

Awesome, thanks @etiennebarrie!

@kern thank you for merging the PR, @etiennebarrie sorry for me slow response (I'm on vacation now with very bad internet :(

It was quite alright, thank you very much!


Links broken in documentation

https://fluxml.ai/ParameterSchedulers.jl/stable/
All of the links to methods in the "Available Schedules" section 404.

The rule of thumb for working on an issue like this is that no permission is required :). A tested PR is more than enough.


Pass command-line args to create-env

add additional ops-files or flags like --recreate on the fly.
Co-authored-by: Manuel Dewald<EMAIL_ADDRESS>

Do you mind switching this PR to be against develop? There's a bot that should automatically promote it to master but then at least the code will run through our pipelines.

@mrosecrance thanks for catching up . That makes sense, I switched to develop.


refactor: Change gateway port to 8100

closes #397

@cherrycl this should un-block https://github.com/edgexfoundry/edgex-compose/pull/60
Please recheck on that PR after merging this PR. If passes go ahead and merge it. THX!


fix(demo): Preview component being used outside of Body

This moves the <Preview> component in all of our demo templates into the <Body> to make sure that it doesn't cause problems for anyone.
See #1683

Please see comments I made here. I've found that this still breaks even when inside the body if the text length is >52 chars.


Improving handling of large code sample in where()

When multiline statements are included, the output of where() can be rather long.
Furthermore, currently empty lines are simply skipped, which can be confusing to beginners trying to see where the code is coming from.

Tentative solution:

[ ] If possible, reduce the number of statements based on the total length
[ ] Add explicit empty line, if there is a single one between statements
[ ] Add a line gap marker, (...), if there are many empty lines skipped

Fixed. See the comparison


Add support for blitting from CPU memory

It would be really useful to have support for copying CPU-side data into textures every frame. This would be useful for things like embedded web browsing via the Chromium Embedded Framework.

+1


Custom keyboard - Cant find keyboard button

Hi all!
I am updating a old program that made use of version 10 of this library.
I was able to update everything, apart from this few lines. I dont seme to be able to figure out how to add buttons to a keyboard...
       Dim rkm As Types.ReplyMarkups.ReplyKeyboardMarkup

       Dim rkb(numrows - 1)() As Types.KeyboardButton         ***************

       Dim buttonItem As String() = {}
       For i = 0 To numrows - 1 Step 1
               If dtable.Rows.Count >= i + 1 Then
                        Dim row(0) As Types.KeyboardButton                     ***************
                        row(0) = dtable.Rows(i).Item("playername").ToString
                        rkb(i) = row
               End If
       Next

       rkm.Keyboard = rkb
       rkm.OneTimeKeyboard = True

       Await sendMessagewithkb(m.Message.Chat.Id, "Select the proper name!", rkm)

any help on this is greatly appreciated!

please use issues for bug reporting or feature suggestions. for general discussions consider joining our chat.
you can find working VB example in this link


Using SHA512 for password encryption.

I'm getting this error message:
The sending password for ‘’, encryption algorithm MD5 does not match the effective server configured encryption algorithm SHA512", "File"=>"/scratch_a/release/svrtar21996/vbuild/vertica/Basics/ClientAuthentication.cpp", "Line"=>"410", "Routine"=>"password_verify"}>
Completed 500 Internal Server Error in 17700ms (ActiveRecord: 0.0ms)

SHA512 is not supported by this library currently. I am happy to accept patches, but am unlikely work on this myself

Thanks for your quick response.

+1 for this feature, for a fresh 8.x cluster I had to downgrade to MD5 hash algorithm.


Evaluate polynomials over d8 - will be used in the quotient polynomial

We do use degree 7 constraints for the lookup argument. Therefore, it requires to evaluate over 8*n.

Closing in favor of https://github.com/o1-labs/proof-systems/pull/1999 + other small PRs


NOT READY: Hierarchical debug mode with query timer.

This change is

Closing this out since it's 2 years old.


[1358] add current user id to Raven user context for Sentry

Context
We are getting sporadic Pundit::NotAuthorisedError. This change tries to up our visibility to try to understand the cause.
Changes proposed in this pull request
Add the id for the current user to the Raven user context.
Guidance to review
Wasn't sure this change was worth testing, the rest of the tests should (hopefully) ensure we don't break anything.

 Investigate pundit errors on transition page.


Solving Issue #114

Solving issue #114

@Sirkkuw - can you please assist to check, approve and merge the content for this PR based on issue #114 ?
This is also related to the changes made for PR 275(closed).  Thank you.

@Sirkkuw  @mypil thank you both


Included applies to section

Reserved capacity applies to Synapse Data Flows also

@hurtn : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Adding a easy way to copy string and var name

Hi i have an idea for a useful tool that if you right  click in a var name or method name etc it will be copied automatically.. This is very useful when i have a long name for my variable and it will save a lot of my time😁

Well. added copy/cut word at caret by the v1.2.0.
You can close this issue if the requested feature is implemented correctly

you may wait until the plugin is distributed on the store. or download it now.
Actionable-1.2.0.zip

Wow well that was fast.. thank you so much


Documentation seems wrong regarding kubernetes compatibility

Report
When i've upgraded kubernetes cluster from 1.25 to 1.26 - we noticed a steep increase in Keda Errors
According to the documentation the running version (2.10) should support kubernetes 1.26 - seems like not all scaling triggered correctly as well
All errors were gone when Keda was upgraded to 2.12
Expected Behavior
Kubernetes upgrade should not have affected Keda
according to the Compatibility Matrix
Actual Behavior
Many Keda errors, reported many timeouts in the logs
Not all scaling would trigger
Steps to Reproduce the Problem

Install keda 2.10 on kubernetes 1.25
create scaled objects
upgrade to 1.26
errors

Logs from KEDA operator
No response
KEDA Version
2.10.0
Kubernetes Version
1.26
Platform
Amazon Web Services
Scaler Details
Multiple
Anything else?
I suggest modifying the compatibility matrix - i don't think 1.10 supports kubernetes 1.26
It does seem like 1.11 changelog mentions support for this version

Hello
I can confirm that 2.10 works on 1.26 because we executed smoke tests on it, checking all the k8s integrations. What errors are you seeing? Maybe there is an upgrade issue that we didn't notice, but fresh installations work, 100% sure.
Could you share the logs from KEDA operator and KEDA metrics server?

Hey Yes - i just got back to this ticket to update
seems the issue is not with keda but with the chagnes on the native HPA Object
I will close this issue now


How to add multi background color on pie char?

Before filing an issue please ensure the following boxes are checked, if applicable:

[x] I have searched for existing issues
[x] I have provided detailed instructions that can reproduce the issue (including code and data necessary)

Can you show me how to add multi background color on pie chart?
Thank you.

I am also interested in know that. Did you come up with a solution @veasnabig ?


Set min total salary

How can I set salary constraint on the lineup optimizer? e, g. I want to set a min total salary to be $59900 for all lineups in fanduel. Thanks for the help.

Added min salary constraint in 1.4. You can set it using lineup_optimizer.set_min_salary_cap(min_salary_cap) method

I keep on getting this error:
AttributeError: 'LineupOptimizer' object has no attribute 'set_min_salary_cap'

Did you update library?

Yes, I did an upgrade.
pip install pydfs-lineup-optimizer --upgrade

Can you run this code in console.
import pydfs_lineup_optimizer
print(pydfs_lineup_optimizer.__version__)

It must print 1.4.0 in console if not try to update package again.

Output version shows 1.4.0
import pydfs_lineup_optimizer
print(pydfs_lineup_optimizer.version)
out:  1.4.0


Application build failure

Running nix-build release.nix -A application in a freshly pulled repository failed.
~/m/TypeScript-Demo-Lib ❯❯❯ nix-build release.nix -A application
these derivations will be built:
  /nix/store/ah59sckpkf465lfqwvq7d870xqsyz7c7-node__at_matrixai_slash_typescript-demo-lib-0.0.2.drv
building '/nix/store/ah59sckpkf465lfqwvq7d870xqsyz7c7-node__at_matrixai_slash_typescript-demo-lib-0.0.2.drv'...
unpacking sources
patching sources
configuring
no configure script, doing nothing
building
installing
unpacking source archive /nix/store/42kp35fis2c30fl3i94azzihjjnhn7b0-TypeScript-Demo-Lib
pinpointing versions of dependencies...
patching script interpreter paths in .
<EMAIL_ADDRESS>interpreter directive changed from "/usr/bin/env node" to "/nix/store/2w6ilfh7zmbz9zqvphgxinmbn3wdqa1b-nodejs-12.18.4/bin/node"
npm ERR! code ENOENT5minstall executeActions0mreeKK
npm ERR! syscall chmod
npm ERR! path<EMAIL_ADDRESS>npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod<EMAIL_ADDRESS>npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /build/.npm/_logs/2021-01-14T00_33_23_633Z-debug.log

builder for '/nix/store/ah59sckpkf465lfqwvq7d870xqsyz7c7-node__at_matrixai_slash_typescript-demo-lib-0.0.2.drv' failed with exit code 254
error: build of '/nix/store/ah59sckpkf465lfqwvq7d870xqsyz7c7-node__at_matrixai_slash_typescript-demo-lib-0.0.2.drv' failed

npm ERR! path<EMAIL_ADDRESS>
This seems similar failure while packaging js-polykey with nix.
The solution was to prepare a node_modules directory in build phase. Will investigate further.

npm ERR! path<EMAIL_ADDRESS>
This seems similar failure while packaging js-polykey with nix.
The solution was to prepare a node_modules directory in build phase. Will investigate further.

Some reference materials used before.

Example from node2nix readme for using node packages in nix.let
  nodeDependencies = (pkgs.callPackage ./default.nix {}).shell.nodeDependencies;
in

stdenv.mkDerivation {
  name = "my-webpack-app";
  src = ./my-app;
  buildInputs = [nodejs];
  buildPhase = ''
    ln -s ${nodeDependencies}/lib/node_modules ./node_modules
    export PATH="${nodeDependencies}/bin:$PATH"

    # Build the distribution bundle in "dist"
    webpack
    cp -r dist $out/
  '';
}

An existing js package in nixpkgs. https://github.com/NixOS/nixpkgs/pull/86169/commits/5e1cf2dbc31ad4fffa3e019b33f696da76eefcbe

Some reference materials used before.

Example from node2nix readme for using node packages in nix.let
  nodeDependencies = (pkgs.callPackage ./default.nix {}).shell.nodeDependencies;
in

stdenv.mkDerivation {
  name = "my-webpack-app";
  src = ./my-app;
  buildInputs = [nodejs];
  buildPhase = ''
    ln -s ${nodeDependencies}/lib/node_modules ./node_modules
    export PATH="${nodeDependencies}/bin:$PATH"

    # Build the distribution bundle in "dist"
    webpack
    cp -r dist $out/
  '';
}

An existing js package in nixpkgs. https://github.com/NixOS/nixpkgs/pull/86169/commits/5e1cf2dbc31ad4fffa3e019b33f696da76eefcbe

Literally node2nix is doing things incorrectly. I have a feeling we have to rewrite it a little bit.
On 14 January 2021 11:44:47 am AEDT, nzhang-zh<EMAIL_ADDRESS>wrote:

npm ERR! path
<EMAIL_ADDRESS>
This seems similar failure while packaging js-polykey with nix.
The solution was to prepare a node_modules directory in build phase.
Will investigate further.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/MatrixAI/TypeScript-Demo-Lib/issues/15#issuecomment-759849991

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Literally node2nix is doing things incorrectly. I have a feeling we have to rewrite it a little bit.
On 14 January 2021 11:44:47 am AEDT, nzhang-zh<EMAIL_ADDRESS>wrote:

npm ERR! path
<EMAIL_ADDRESS>
This seems similar failure while packaging js-polykey with nix.
The solution was to prepare a node_modules directory in build phase.
Will investigate further.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/MatrixAI/TypeScript-Demo-Lib/issues/15#issuecomment-759849991

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

This is fixed?

This is fixed?


Running multiple FTP servers on multiple ip addresses

I am running several instances of FTP Servers from single script, each on different ip address (basically just multiple ip aliases on single loopback adapter). However when using the FTPHandler class, I have noticed that it has class variables such as an authorizer. This causes issues when different settings are required for different servers (accounts, banner, etc..).
Is there a way to run multiple FTP server instances, each with their own account settings (and banners, etc...)? Only thing that I've come up with is to run separate scripts, but I thought it should be possible from API provided, maybe I am just missing something.

I was able to solve this by creating the FTPHandler classes dynamically (Python is truly marvelous...):
def create_ftp_handler():
    class FTPHandlerMulti(FTPHandler):
      pass
    return FTPHandlerMulti

Then instead of handler = FTPHandler one can just use handler = create_ftp_handler(). Perhaps it has nicer solution using metaclasses, but this works...


Option to disable antialiasing

Is it possible to render images without antialiasing?

Not yet, but there will be a possibility in the next release with the immediate mode: https://github.com/Twinside/Rasterific/blob/17863358fe247195bdeee1c246e80f5635659bd9/src/Graphics/Rasterific/Immediate.hs#L173 I don't know if I want to provide more general mechanism to disable anti aliasing

Great, that should be enough :) Thanks!


sync vagrant folder to guest before provision.

vagrant 1.8.1
aws-plugin: v0.7.0
I currently can not get it to sync the vagrant folders before a provision. Currently is stuck on my original sync of the box.

ubuntu 14.04
rsync installed
no configuration for the default sync of the vagrant folder.

ok closing looked closer at the docs for rsync and looks like its a one time deal, need to setup rsync auto or reload.


There is no "Export" button for Dynamic color scheme

There is no "Export" button for Dynamic color scheme.
Steps to reproduce the behavior:

Launch Figma on desktop and the Material Theme plugin
Click on Dynamic tab.

Expected behavior:
There is an "Export" button at the bottom of the window, as on the "Custom tab"
Screenshots
This is an example of how it should be:

This is an example of what I get:

Hi! Currently dynamic is for previewing purposes only, how designs could look using wallpaper or content colors. Exporting is available for custom themes. Please keep a look out for future updates, as this may change!


Implement dynamically configurable infoview auto-open.

The main refactor here is adding the ability to distinguish between "open", "closed", and "uninitialized". Should also set us up well for persistent infoview state features in the future.

Sorry I wasn't clear about this, will be better about creating/linking issues in the future. The purpose of this PR is to pass this test case.

Aha. Thanks, the clarification helps definitely on what this is trying to do!
Will spend a bit of time with it.

Quick update here -- I have a branch with a medium-sized refactor that personally I'm a lot more comfortable following, and which addresses some of what I was trying to get across (it essentially removes the uninitialized state, makes it impossible for a buffer to be both closed and open, removes lots of intertwined conditionals, handles set_autoopen by just setting or unsetting an autocmd, few other things).
Have a look and let me know what you think. I believe if I follow what you were saying previously about persistent stuff that that should be equally possible even after that branch.
There are still a few more things I want to address, but I think the only major one is a test fails in CI that never fails locally, and I don't see why, so I'll have to diagnose what's different between my machine and the CI setup again...
Other than that one test, all the others pass essentially without modification from what we had previously (and in this PR).

Awesome!!! Will check it out today. In general OOP sounds like a very good idea for infoviews.

Split the commit up

Good call, though I'm not so sure about the extent to which a refactor like this can be made to look incremental at any stage - maybe it's just a matter of reorganizing?

Issues which seem present on current main as well

Both of these I think deserve their own issues,

@Julian Thank you very much for the refactor idea! I've fixed and simplified your branch and I'm pretty certain now that it matches your intentions, but let me know if I missed anything. Also tried to address your checklist (see above comments).

Split the commit up

Good call, though I'm not so sure about the extent to which a refactor like this can be made to look incremental at any stage - maybe it's just a matter of reorganizing?

This was a scribble from an earlier point -- yeah I could reorganize the commit into a few separate ones but at this point given you tidied the code up it's just gonna stay as is which is fine.


Copy repo in moonbeam-presentations

PureStake/moonbeam-presentations

@albertov19 added it to https://github.com/PureStake/moonbeam-presentations/tree/202107-ethcc21
Looks good?

Looks good! If everything is copied we can delete this repo


use Decimal.equal? for coalesce on mixed type

Followup to #3582 . I also added two tags we needed locally, if you don't mind.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Document permissions

Documents minimum permissions required for the action to run in repos with restricted default permissions for workflows or for PRs created by Dependabot. These were established by a bit of trial and error in https://github.com/freckle/megarepo/pull/30954 (private repository).

Great idea! Maybe we should add this to any of our -actions template repositories?

Yeah, this seems good to require as part of minimal documentation for new actions. Is there a repository besides freckle/typescript-action-template?
I think it would be a good rule of thumb for each action repo's CI workflow to specify the minimal required permissions, to flag changes that require more permissive workflow runs.

Is there a repository besides freckle/typescript-action-template?

I trust your ability to search as well as mine, so probably not?

good rule of thumb for each action repo's CI workflow

By that you mean the action's "example" workflow? The permissions needed to CI an action vs use it would differ, so if this is mean to document usage that would be in the example, I think.

Yeah, I was thinking of example.yml workflows (i.e., something that uses: ./. However, I think example.yml should show a representative/common use of the action in a workflow, which is different (in this case) to a test run that exercises the action as a form of CI. Particularly for this action, it's inconvenient to have on.pull_request.types: [opened] since it only runs a single time.
I think two workflows are appropriate to add to this repo:

example.yml complements or removes the existing section on Usage and wouldn't be expected to run in development PRs
test.yml exercises the action with minimal permissions

Oh yeah, this is interesting.

I think example.yml should show a representative/common use of the action in a workflow, which is different (in this case) to a test run that exercises the action as a form of CI

In my experience they are more often basically the same than they are different in meaningful ways, but I guess that doesn't need to stop us from making them distinct always. As an alternative to your suggestion, how about:

example.yml as you describe, but it does run on PRs
ci.yml as it is today, typically with unit test jobs, lint etc, but also with an integration* Job(s) that exercise the action as necessary (i.e. with different arguments, happy/sad paths) and includes minimal permissions.

I prefer this because:

You really do need to exercise example on PRs IMO, otherwise it'll become broken without us knowing and be bad docs
We're talking about adding a form of CI, so I'd prefer extending the existing "CI" over creating a similarly-named "test"


Does dragging the vehicle blueprint to world consider as an actor ?

Hallo
I am having a doubt. I dragged and dropped a car from the carla blueprint.
Then I run the simulation and get the list of actors using the python API.
But it doesnot have the car in it ? Do you have any idea why this is happening ?
Anyway to access the car i just dragged into the world using python ?

What you are doing is drop a blueprint into the scene, not creating an actor, hence why the API doesn't see it. For you to see it, it has to be spawned on runtime (either through the server, your client, or another one). You might be able to use the world.get_level_bbs() function to get its information, but again, it's not an actor, so you won't be able to treat it as one