cmd/link: package doc contains outdated linker flags

Go version
go version devel go1.22-bb8a96fa54 Fri Nov 17 21:25:34 2023 +0000 windows/amd64
What operating system and processor architecture are you using (go env)?
set GOARCH=amd64
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
...

What did you do?
I ran go doc cmd/link and go tool link to see what flags are available.
What did you expect to see?
The list of valid flags should be the same in both results. The descriptions might be a little different (e.g. the doc might have more detailed info).
What did you see instead?
The lists of flags are different.
Example: -u is in go doc cmd/link:
    -u
        Reject unsafe packages.

However, this flag was removed a few years ago in https://go-review.googlesource.com/c/go/+/236117 and doesn't show up in go tool link --help.

Thanks for reporting. I added Suggested since this seems like a good issue for someone looking to send a CL to fix.
CC @golang/compiler.

Thanks! I was thinking about submitting a CL myself, but figured I probably didn't have the context to make a full proper update so filed this first. 🙂


feat(options): customSVGIcons API 变更

👀 PR includes

✨ Feature

[x] New feature

📝 Description

BREAKING CHANGE: svg 变更为 src

const s2Options = {
  customSVGIcons: [
    {
      name: 'CustomIcon',
-     svg: 'https://gw.alipayobjects.com/zos/bmw-prod/f44eb1f5-7cea-45df-875e-76e825a6e0ab.svg',
+     src: 'https://gw.alipayobjects.com/zos/bmw-prod/f44eb1f5-7cea-45df-875e-76e825a6e0ab.svg',
    },
  ]
}

内置 icon 格式优化

🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

🔍 Self-Check before the merge

[ ] Add or update relevant docs.
[ ] Add or update relevant demos.
[ ] Add or update test case.
[ ] Add or update relevant TypeScript definitions.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 80.04%. Comparing base (ecdc9c8) to head (c0685e0).
Report is 341 commits behind head on next.

Additional details and impacted files
@@            Coverage Diff             @@
##             next    #2700      +/-   ##
==========================================
+ Coverage   75.77%   80.04%   +4.27%
==========================================
  Files         257      176      -81
  Lines       11994    10090    -1904
  Branches     2464     2313     -151
==========================================
- Hits         9088     8077    -1011
+ Misses       1398      618     -780
+ Partials     1508     1395     -113

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:tada: This PR is included in version @antv/s2-v2.0.0-next.20 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-react-v2.0.0-next.19 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


🚀 [Feature Request] - Want to add left to right animation on navbar element

Is your feature request related to a problem ? Please describe. ✍
I want to add left to right animation on the navbar element  when someone hover over their, The underline animate form left to right
Describe briefly how you would implement this enhancement.
Some steps to implement this enhancement-
1. Step 1 Added Underline pro
2. Step 2 Added animation effect on underline
3. Step 3Added hover effect

Additional context or screenshots
Additional context

Are you contributing for a program?
GSSoC2023
Code of Conduct

[X] I have read and agree to the Contributing Guidelines of this project.

Can I work on this issue?

navbar hover issue already open


Android Compose Generics Objects and Extensions

Name of the Codelab or Codelab URL
https://developer.android.com/codelabs/basic-android-kotlin-compose-generics?authuser=1&continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-3-pathway-1%3Fhl%3Den%26authuser%3D1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-generics&hl=en#6
Describe the problem
A clear and concise description of what the problem is.
It's just a typo but a compiler will throw an error. A var property should actually be val.
In which lesson and step of the codelab can this issue be found?
Lesson number + step number.
Lesson 7, step 2
How to reproduce?
interface ProgressPrintable {
var ProgressText: String
}
This is the code block in codelab. Here ProgressText should be val.
Versions

What version of Android Studio are you using? - Kotlin playground 1.8.10 with JVM
What API level are you targeting?

Additional information
Add any other context about the problem here.
codelab:
https://developer.android.com/codelabs/basic-android-kotlin-compose-generics?authuser=1&continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-3-pathway-1%3Fhl%3Den%26authuser%3D1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-generics&hl=en

Hi @Harman-Haiilo
Thank you for taking the time to document this issue.
It has been fixed and the change is now live in production.
Hope you are enjoying the course!
Regards.


Add array_min Spark function

In presto, array_min return NULL when input contains any NULL element.
In spark,  NULL elements are skipped. If the array is empty or contains only NULL elements, NULL is returned.
Spark 3.2 ref: https://github.com/apache/spark/blob/v3.2.2/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/collectionOperations.scala#L1779

@rui-mo @mbasmanova prestosql array_min seems not to take into count NaN for float/double, Should I don't reuse presto implementation， just rewrite in sparksql？

@rui-mo @mbasmanova prestosql array_min seems not to take into count NaN for float/double, Should I don't reuse presto implementation， just rewrite in sparksql？

@Ma-Jian1 The skipNull flag and NaN checking look redundant for presto sql. Maybe rewriting a function in spark sql is better. How do you think?

@rui-mo @mbasmanova prestosql array_min seems not to take into count NaN for float/double, Should I don't reuse presto implementation， just rewrite in sparksql？

@Ma-Jian1 The skipNull flag and NaN checking look redundant for presto sql. Maybe rewriting a function in spark sql is better. How do you think?

OK, I'll don't touch prestosql, just copy to sparksql

@mbasmanova Do you have time to review this PR? Thanks.

@mbasmanova Do you have time to review this PR? Thanks.

Can you also add ArrayMinMaxBenchmark as PrestoSql?

@mbasmanova any comments left？ Or Is it ok to be approved？

Hi @mbasmanova, could you please take a further review? Thanks!

Hi @mbasmanova, I am taking over this work. If you have any other comment, please let me know. Thanks!

Hi @mbasmanova, could you please take a further review? Thanks!


Unix/Linux line endings in CLI need to be enforced

bin/mocha and bin/_mocha need to have Unix line endings. Currently Git's autocrlf setting can screw this up. (See also #2799 for an example of when this goes wrong.) Our tests don't check for it either.
We will need to either check for or fix the line endings in these files as part of publishing. Or, if doing it on publish isn't feasible (prepublish vs. prepublishOnly seems to be a bit of an issue?), on version (most of our other publishing prep is in versioning already anyway...).
Ideally, I'd like to just run a Node command and convert the line endings, so it doesn't matter what Git did (or the user, etc) -- this isn't something that should have to be fixed manually when it is detected.

Actually, since this affects potentially any cross-platform CLI package, we ought to submit a fix to https://github.com/npm/npm/issues/13203 I am thinking maybe do "\r\n"->"\n" conversion on the files that are being linked in node_modules/.bin at install time?

https://github.com/npm/npm/issues/12371 actually has a very similar suggestion as its main post (I guess 13203 is more of a duplicate)...


Status Bar and Tool Bar Info

Quite useful types of bars for GUIs, that noticed wasn't on your todo list.  Maybe it should be considered.

Status Bar
Oops, and so it is.  Don't know how I overlooked that, but glad it is there.

Tool Bar is supported with a complex api.
And a simple implementation would likely be fine, from the perspective of probably a lot of users.  Also good to see that you are thinking about it.

Interestingly and to add more info, a user can create a quasi status and tool bar by using y_offset or yn_offset with emojis, as is shown in the mui notepad example. Instead of the y_offset, perhabs make it an actual bar where thickness is resizable based on window.  The other advantage is if text size is implemented, button emoji can be set to different sizes too.
https://github.com/malisipi/mui/blob/main/examples/notepad.v

You can use statusbar and toolbar with latest commit.

Set height of statusbar/toolbar
mut app:=m.create(title:"MUI Examples", ... toolbar:25, statusbar:25)

Add widgets
app.button(id:"open", x:0, y:0, ...frame:"@toolbar") for toolbar
app.button(id:"open", x:0, y:0, ...frame:"@statusbar") for statusbar

For full example just browse notepad.v.


Allow selecting docker as cri.name

How to categorize this PR?

/kind enhancement
What this PR does / why we need it:
Allow selecting docker as cri.name, such that users can explicitly choose docker once we switched the default to containerd. This decouples the choice of the container runtime from the next k8s update and allows for switching back to docker without downgrading your k8s version.
Which issue(s) this PR fixes:
related #4110
Release note:

Allow explicit configuration of `docker` as a container runtime for backwards compatibility. Select this only if your workload doesn't run nicely with `containerd`. This configuration option will be removed in the future!

/cc @BeckerMax

cc @grolu @petersutter @holgerkoser

Due to
https://github.com/gardener/gardener/blob/77e09dd522d7bfb682cc35d0be437201b606061b/extensions/pkg/controller/worker/machines.go#L146-L152
, I think this will trigger a(n undesired) rolling update of the shoot worker nodes if somebody with .spec.provider.workers[].cri=nil starts to specify .spec.provider.workers[].cri.name=docker (although, it's semantically equal).
I guess we need some special handling in above mentioned function, right?

That's a great observation, I should have put this context in the above summary! @BeckerMax and I decided to do this in a separate change, because technically it is an optimization and can be treated as a separate concern. I've added this to the tracking issue (#4110) and we'll get to it later, does this make sense?

A side note: In order to be able to select docker as cri.name, you'd have to edit your CloudProfile such that the used MachineImage contains docker in the list of suppported CRIs. This seems actually useful, because we want to remove docker from the images at a future point in time, actually resulting in images which are no longer compatible with the choice of docker as container runtime.
The error message you get could be more helpful to figure out what to do, though
shoots.core.gardener.cloud "shoot-gcp-contd" is forbidden: [spec.provider.workers[0].cri.name: Unsupported value: "docker": supported values: "containerd"]

Discussing with @timebertt we came to the conclusion this still needs an additional change.
Do not merge yet!

/author-action

/unassign

Overall looks good.
I think you have to add one improvement in the worker pool hash
[...]
This way the nodes rolling update will be avoided when worker.cri=nil is re-configured as worker.cri.name=docker.

Thanks for spotting this! As discussed with @rfranzke above we're doing this in an extra change: #4237


Optimize dot product of vector, min and max of matrix

And finally, please, drop branch commits history...


Fix for Improper TFTP Sequence Wraps

Bug Fix
If the size of the file being transferred via TFTP is a multiple of the block size then improper sequence wrapping occurs causing issues with file transfers. See #94 for details.

This was actually two separate fixes. While making TFTP sequence wraps work, I discovered that if the file we're sending is a multiple of the blocksize, we don't send the final empty block to signal that we're done. It works most of the time because if the file isn't a multiple of the blocksize, the last block is short, and the receiver interprets that as being finished.


Get ms alias from github identity

Summary
The PR is using opensource rest API call to get ms alias from github identity.
Expect returns:

200 status.
Return ms alias directly when call the scripts.
error response.
Print the API call error response and exit 1.

Testing locally

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

Combined this PR with https://github.com/Azure/azure-sdk-tools/pull/2581
Closed this one.


Not setting BaseUri in the Spec is translated to setting BaseUri to http://localhost by default

For Key Vault SDK, some of the public APIs accept a key ID or secret ID, which is made up of a vault URL, key/secret name and the collection title.
E.g.:
public async Task GetKeyAsync(string keyIdentifier, CancellationToken cancellationToken = default(CancellationToken))
Here is an example of a KeyIdentifier: https://vaultName.vault.azure.net:443/keys/keyName/keyVersion
The default baseUri should be set to an empty string if not provided in the spec to support the above scenario.

The host (name or ip) serving the API. This MUST be the host only and does not include the scheme nor sub-paths. It MAY include a port. If the host is not included, the host serving the documentation is to be used (including the port). The host does not support path templating.

via the Swagger spec
Could you use the Parameterized Host Extension for this?

Thanks. But there are some problems with Parameterized Host:

By defaults http:// is added to the start of BaseUri. So for host =  {vault} the BaseUri will be http://https://vaultName.vault.azure.net
Specifying the order of the parameters in the path and host template is not supported when APIs get generated. So for host = {vault} and a path parameter {value}, instead of of having Foo(string vault, string value) it will be Foo(string value, string vault).
Having more than one baseUri is not supported. Key Vault APIs accept keyIdentifier and secretIdentifiers, which are different URLs, but using parameterized host it is not supported to have multiple host templates.

I believe this issue has been handled by @amarzavery. Do you feel this is adequately resolved?

Thanks @devigned and @amarzavery. Yes, this is adequately resolved and we are unblocked. Well done! :+1:


Sorting in Table View Breaks with Aliases Added to Model Fields

When aliases are added to any field within the model, the sorting functionality in the table view becomes compromised. This issue arises specifically when attempting to sort data either in ascending or descending order.
I've successfully addressed this problem within my local environment by implementing a patch. To ensure the resolution is properly reviewed and integrated, I've submitted a pull request for your assessment.
Please review the changes and consider merging them into the main branch to rectify this sorting inconsistency.

Hi @cquintini,
First of all, thanks for your pull request.
It's an interesting approach, but we prefer to use the client-side approach in the List component to reduce complexity.
You are the first one to make a pull request outside of us, thanks for that. And of course, feel free to make more  🙌

This bug was fix on v3.2.7 🚀
Feel free to give feedback


Sparrow 1.8.0 does not connect to the Bitcoin node via electrs

With RaspiBlitz v1.9.0, Sparrow 1.8. It does not connect through electrs:
"Error getting fee estimates for target blocks"
I mean, it doesn't connect to Rasp on a local network, nor through Tor remotely...
With Sparrow v1.7.9-1 yes, in both cases.

There have been no changes from v1.7.9 to v1.8.0 I can think of that would affect this - and I would expect it to have been widely reported already if there was a problem. Can you test again? What version of Electrs are you connecting to?

Sorry for the delay, you know the time...and the work.
In raspiblitz electrs v0.9.11
In VM Proxmox electrs v0.9.13

See #899 - I suspect this is a server hardware related issue, where Bitcoin Core can't handle certain requests as the mempool fills up. Can you try making  the following requests directly to your node?
bitcoin-cli estimatesmartfee 1
bitcoin-cli estimatesmartfee 10
bitcoin-cli estimatesmartfee 50

They should return almost instantly.
Also, please take a look in sparrow.log (Help menu) and report any related errors you see there - and anything from the electrs log file.

I just reinstalled v1.8.0 and it works!!!!
I really don't know what happened...I'll look at the logs.
Thank you.
I close the issue


Replace macros with methods on wrappers

Great work, thanks!
I've published the 0.2-SNAPSHOT to Sonatype.

Hello,
Thanks for merging, I'll work next on improving the
https://groups.google.com/forum/#!topic/scala-js/IQLZYp-kwHA
On 30/01/2015 23:33, jokade wrote:

Great work, thanks!
I've published the 0.2-SNAPSHOT to Sonatype.
—
Reply to this email directly or view it on GitHub
https://github.com/jokade/scalajs-angulate/pull/24#issuecomment-72282209.

Well, I've published the 0.1 for SJS 0.6.0 a few hours ago. Current problem for angulate is, that utest has not been published for SJS 0.6.0...

Hello,
Thanks for merging, I'll work next on improving the way declarative
markup is handled for functions. The idea is to wrap a js.Dictionary in
an AnyVal. The wrapper and the implicit function converting scala
functions to it will be more reusable, I'll need that for ui-router.
There's a release of sjs 0.6, but as you've noted (sorry, my mail was
sent while writing it, I don't know why, just pressed enter key...)
uTest is not yet ready for it.
https://groups.google.com/forum/#!topic/scala-js/IQLZYp-kwHA
Cheers,
Ludovic
On 30/01/2015 23:33, jokade wrote:

Great work, thanks!
I've published the 0.2-SNAPSHOT to Sonatype.
—
Reply to this email directly or view it on GitHub
https://github.com/jokade/scalajs-angulate/pull/24#issuecomment-72282209.

That explains your first post :)
Could you give an example for "declarative markup" for functions?
Cheers,
Johannes

The correct term is 'inline array annotation', I was reading the Angular
doc too fast.
It looks like this
["$scope", "MyService", function($scope, MyService) {...}]
Ludovic
On 31/01/2015 00:00, jokade wrote:

That explains your first post :)
Could you give an example for "declarative markup" for functions?
Cheers,
Johannes
—
Reply to this email directly or view it on GitHub
https://github.com/jokade/scalajs-angulate/pull/24#issuecomment-72285848.

Ahh, so you want to generalize the support for function DI (as supported by Module.run and Module.config)? If so, maybe you could open an issue for this topic (for any further discussion)?


How to get your polymer progressive webapp working on http2?

To use http/2, you'll need to use SSL with a certificate, or have a hosting provider that does that for you. AppEngine will provide http/2 automatically, while if you make your own server you can follow the instructions for enabling http/2 on your webserver of choice (https://mozilla.github.io/server-side-tls/ssl-config-generator/ is very handy for generating configs)


Feat/delete  blog posts

What does this PR do?
This PR implements an endpoint for deleting a blog post from the database. The endpoint is restricted to super admin users only and provides appropriate responses for various scenarios.

Added DELETE /api/v1/blogs/:id Endpoint: Allows superadmins to delete existing blog posts.
Authentication and Authorization: Requires a JWT token and superadmin role for access.
Response Handling: Provides appropriate responses for successful deletion, blog not found, unauthorized access, and other error scenarios.

How should this be manually tested?
Login Superadmin User:

Make a POST request to /api/v1/auth/login with a superadmin user's credentials.
Check the response for a valid JWT token.

Delete Blog Post:

Make a DELETE request to /api/v1/blogs/:id with the blog ID in the path parameter and a valid JWT token in the header.
Verify the response confirms the blog has been deleted.

Edge Cases:

Invalid Token: Test with an invalid token to ensure the endpoint returns a 401 Unauthorized status with the correct message.
Missing Token: Test without a token to ensure the endpoint returns a 401 Unauthorized status with the correct message.
Non-superadmin User: Test with a valid token of a non-superadmin user to ensure the endpoint returns a 403 Forbidden status.
Non-existent Blog: Test with a non-existent blog ID to ensure the endpoint returns a 404 Not Found status.
Internal Server Error: Simulate a server error to ensure the endpoint returns a 500 Internal Server Error status.

Checklist

[x] Implemented DELETE /api/v1/blogs/:id endpoint in the blogs.controller.ts.
[x] Added deleteBlogPost method in the blogs.service.ts.
[x] Modified blogs.controller.ts to provide appropriate responses for various cases.
[x] Tested endpoint functionality to ensure it correctly handles valid and invalid tokens.
[x] Added appropriate HTTP status codes and response messages for edge cases.
[x] Added tests for this endpoint.

Response Examples
Success:
{
  "message": "Blog successfully deleted",
  "status_code": 202
}

Forbidden:
{
  "message": "You are not authorized to perform this action",
  "status_code": 403
}

Not Found:
{
  "message": "Blog with the given Id does not exist",
  "status_code": 404
}

Internal Server Error:
{
  "message": "Internal server error.",
  "status_code": 500
}

Invalid Method:
{
  "message": "This method is not allowed.",
  "status_code": 405
}

Bad Request:
{
  "message": "An invalid request was sent.",
  "status_code": 400
}

Link to Issue
Link to this issue: #108

Fix the title please


Replace circular-json with flatted

Closes #35 .

So is the CI error due to Mocha switching to ES6+ syntax but flat-cache enforcing "use strict" in the tests? How can that be corrected? or can it be safely ignored for the PR to get merged?
/home/travis/build/royriojas/flat-cache/node_modules/mocha/bin/mocha:10
const spawn = require('child_process').spawn;
^^^^^
SyntaxError: Use of const in strict mode.
    at exports.runInThisContext (vm.js:73:16)
    at Module._compile (module.js:443:25)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)
    at startup (node.js:129:16)
    at node.js:814:3
npm ERR! Test failed.  See above for more details.
The command "npm test" exited with 1.


Azure DevOps pipeline tasks

Brings Azure DevOps CI strategy inline with github & gitlab. Favouring a more composable approach with InfracostSetup & InfracostComment tasks. Updates docs with examples of known cases.
Current WIP. Use this as the staging branch for task related changes.

@alikhajeh1 could you work your magic and give the docs a review now. @vdmgolub is still wrestling with some azure repos bugs with the InfracostComment task but the copy/examples won't change

Based on the issues we've been having with azure repos, I think it's clear we need to modify the quickstart/setup steps in readme to have two cases: Github & Azure Repos.


Redacts x-ms-copy-source header.

Redacts x-ms-copy-source header. Optimize comments for highlevel.

Close as sending from forked branch is not supported temporarily.


[Not for merge] Madam optimizer with OOM handling

Put it here for discussion. Not ready for merge.
It contains

madam optimizer from Dan
Handle OOM when using a larger max-duration (e.g., from 200 to 350)

tensorboard log: https://tensorboard.dev/experiment/WCQbgwK2T0OI9kCWjHPOSw/#scalars

I will port OOM handling to LF-MMI training as well.


transaction.create doesn't deduct fee from outputs

Example response:
{
  "data": {
    "result": "complete",
    "transactions": [
      {
        "fee": {
          "amount": 1,
          "currency": "0x0000000000000000000000000000000000000000"
        },
        "inputs": [
          {
            "amount":<PHONE_NUMBER>0000000,
            "blknum": 138000,
            "creating_txhash": "0xf9b02554e85ed7ed291c0a7657519d38de7ec2660db1e7e5bb0b8f0b435c0fc4",
            "currency": "0x0000000000000000000000000000000000000000",
            "inserted_at": "2020-10-29T14:20:53Z",
            "oindex": 1,
            "otype": 1,
            "owner": "0x31bc9ea3093d5a4faeff8fdf24499cea3f7c1f92",
            "spending_txhash": null,
            "txindex": 0,
            "updated_at": "2020-10-29T14:20:53Z",
            "utxo_pos":<PHONE_NUMBER>00001
          },
          {
            "amount": 3000,
            "blknum": 142000,
            "creating_txhash": "0x8fe5f64976fdca50c15bd6d6a1b9aa473227b5d5650dc2136a8f5fceb5d0b75a",
            "currency": "0xd5b83b1fdbc00bfe3679a60b2cb6252418df0d99",
            "inserted_at": "2020-10-29T14:58:36Z",
            "oindex": 0,
            "otype": 1,
            "owner": "0x31bc9ea3093d5a4faeff8fdf24499cea3f7c1f92",
            "spending_txhash": null,
            "txindex": 0,
            "updated_at": "2020-10-29T14:58:36Z",
            "utxo_pos":<PHONE_NUMBER>00000
          }
        ],
        "metadata": "0x0000000000000000000000000000000000000000000000000000000000000000",
        "outputs": [
          {
            "amount": 700,
            "currency": "0xd5b83b1fdbc00bfe3679a60b2cb6252418df0d99",
            "owner": "0xbdba40131ec2d16f067cc242644ea69e8afd0d4a"
          },
          {
            "amount":<PHONE_NUMBER>0000000,
            "currency": "0x0000000000000000000000000000000000000000",
            "owner": "0x31bc9ea3093d5a4faeff8fdf24499cea3f7c1f92"
          },
          {
            "amount": 2300,
            "currency": "0xd5b83b1fdbc00bfe3679a60b2cb6252418df0d99",
            "owner": "0x31bc9ea3093d5a4faeff8fdf24499cea3f7c1f92"
          }
        ],
        "sign_hash": "0x6f8a85fee13ab63fdb319537e3ff8b068875b85d3f2b01f5e92f5e8b729f3656",
        "txbytes": "0xf8fe01f842a000000000000000000000000000000000000000000000000000007d82a0faa001a000000000000000000000000000000000000000000000000000008125f38ee000f895ef01ed94bdba40131ec2d16f067cc242644ea69e8afd0d4a94d5b83b1fdbc00bfe3679a60b2cb6252418df0d998202bcf401f29431bc9ea3093d5a4faeff8fdf24499cea3f7c1f9294000000000000000000000000000000000000000087b150e16cbd5fffef01ed9431bc9ea3093d5a4faeff8fdf24499cea3f7c1f9294d5b83b1fdbc00bfe3679a60b2cb6252418df0d998208fc80a00000000000000000000000000000000000000000000000000000000000000000",
        "typed_data": {
          "domain": {
            "name": "OMG Network",
            "salt": "0xfad5c7f626d80f9256ef01929f3beb96e058b8b4b0e3fe52d84f054c0e2a7a83",
            "verifyingContract": "0xb43f53394d86deab35bc2d8356d6522ced6429b5",
            "version": "1"
          },
          "message": {
            "input0": {
              "blknum": 138000,
              "oindex": 1,
              "txindex": 0
            },
            "input1": {
              "blknum": 142000,
              "oindex": 0,
              "txindex": 0
            },
            "input2": {
              "blknum": 0,
              "oindex": 0,
              "txindex": 0
            },
            "input3": {
              "blknum": 0,
              "oindex": 0,
              "txindex": 0
            },
            "metadata": "0x0000000000000000000000000000000000000000000000000000000000000000",
            "output0": {
              "amount": 700,
              "currency": "0xd5b83b1fdbc00bfe3679a60b2cb6252418df0d99",
              "owner": "0xbdba40131ec2d16f067cc242644ea69e8afd0d4a"
            },
            "output1": {
              "amount":<PHONE_NUMBER>0000000,
              "currency": "0x0000000000000000000000000000000000000000",
              "owner": "0x31bc9ea3093d5a4faeff8fdf24499cea3f7c1f92"
            },
            "output2": {
              "amount": 2300,
              "currency": "0xd5b83b1fdbc00bfe3679a60b2cb6252418df0d99",
              "owner": "0x31bc9ea3093d5a4faeff8fdf24499cea3f7c1f92"
            },
            "output3": {
              "amount": 0,
              "currency": "0x0000000000000000000000000000000000000000",
              "owner": "0x0000000000000000000000000000000000000000"
            }
          },
          "primaryType": "Transaction",
          "types": {
            "EIP712Domain": [
              {
                "name": "name",
                "type": "string"
              },
              {
                "name": "version",
                "type": "string"
              },
              {
                "name": "verifyingContract",
                "type": "address"
              },
              {
                "name": "salt",
                "type": "bytes32"
              }
            ],
            "Input": [
              {
                "name": "blknum",
                "type": "uint256"
              },
              {
                "name": "txindex",
                "type": "uint256"
              },
              {
                "name": "oindex",
                "type": "uint256"
              }
            ],
            "Output": [
              {
                "name": "outputType",
                "type": "uint256"
              },
              {
                "name": "outputGuard",
                "type": "bytes20"
              },
              {
                "name": "currency",
                "type": "address"
              },
              {
                "name": "amount",
                "type": "uint256"
              }
            ],
            "Transaction": [
              {
                "name": "txType",
                "type": "uint256"
              },
              {
                "name": "input0",
                "type": "Input"
              },
              {
                "name": "input1",
                "type": "Input"
              },
              {
                "name": "input2",
                "type": "Input"
              },
              {
                "name": "input3",
                "type": "Input"
              },
              {
                "name": "output0",
                "type": "Output"
              },
              {
                "name": "output1",
                "type": "Output"
              },
              {
                "name": "output2",
                "type": "Output"
              },
              {
                "name": "output3",
                "type": "Output"
              },
              {
                "name": "txData",
                "type": "uint256"
              },
              {
                "name": "metadata",
                "type": "bytes32"
              }
            ]
          }
        }
      }
    ]
  },
  "service_name": "watcher_info",
  "success": true,
  "version": "1.0.5+54305bb"
}

Alright, so if you look at this function that builds a transaction’s outputs, you see that the fee is passed in along with the payments for the derivation of the “change” amount. So the “change” output takes into account the fee.  If you look at the test suite, the deduction of the fees is also clearly covered in multiple tests (see : here. – it’s not explicit but you can conclude with some simple arithmetic) (edited)

Call to https://watcher-info.rinkeby.v1.omg.network/transaction.create with OMG fee:
Request Parameters:
{
  "fee" : {"currency": "0x942f123b3587ede66193aa52cf2bf9264c564f87"},
  "owner":  "0x8cb0de6206f459812525f2ba043b14155c2230c0",
  "payments": [
    {
      "amount": 30,
      "currency": "0x0000000000000000000000000000000000000000",
      "owner": "0xc139e1d7358e4faf76f0fcf792255016af5dc742"
    }
  ]
}

Response:
...
 "inputs": [
          {
            "amount":<PHONE_NUMBER>0000000,
            "blknum": 144000,
            "creating_txhash": "0x206d1e58aab14f339bfa03b54b39e9c6cb0cb6c912823ae38fcbadb04266d6b8",
            "currency": "0x0000000000000000000000000000000000000000",
            "inserted_at": "2020-10-29T19:59:19Z",
            "oindex": 1,
            "otype": 1,
            "owner": "0x8cb0de6206f459812525f2ba043b14155c2230c0",
            "spending_txhash": null,
            "txindex": 0,
            "updated_at": "2020-10-29T19:59:19Z",
            "utxo_pos":<PHONE_NUMBER>00001
          },
          {
            "amount":<PHONE_NUMBER>00000000000,
            "blknum": 176000,
            "creating_txhash": "0x879ecb82e49904152adac6764546177be666cedc42421f29c87f4e129c769bf6",
            "currency": "0x942f123b3587ede66193aa52cf2bf9264c564f87",
            "inserted_at": "2020-11-01T21:40:05Z",
            "oindex": 1,
            "otype": 1,
            "owner": "0x8cb0de6206f459812525f2ba043b14155c2230c0",
            "spending_txhash": null,
            "txindex": 0,
            "updated_at": "2020-11-01T21:40:05Z",
            "utxo_pos":<PHONE_NUMBER>00001
          }
        ],
        "metadata": null,
        "outputs": [
          {
            "amount": 1,
            "currency": "0x0000000000000000000000000000000000000000",
            "owner": "0xc139e1d7358e4faf76f0fcf792255016af5dc742"
          },
          {
            "amount":<PHONE_NUMBER>9999999,
            "currency": "0x0000000000000000000000000000000000000000",
            "owner": "0x8cb0de6206f459812525f2ba043b14155c2230c0"
          },
          {
            "amount":<PHONE_NUMBER>4020039393,
            "currency": "0x942f123b3587ede66193aa52cf2bf9264c564f87",
            "owner": "0x8cb0de6206f459812525f2ba043b14155c2230c0"
          }
        ]
...

The fee is clearly being deducted in the fee output.

Above call was made with the same address as the inputs owner in the issue: "0x31bc9ea3093d5a4faeff8fdf24499cea3f7c1f92"

closing as this is indeed not a bug in the watcher but an implementation detail in the clients environment. (big number rounding)


docs(angular-mocks): replace $rootScope with scope

use scope instead of $rootScope in the code example

Why not $rootScope.$new()? then you don't have to use the injector.

I need to get the $rootScope in some way. So the other option would be:
var scope, $rootScope;
/* ... */
$rootScope = $injector.get('$rootScope');
scope = $rootScope.$new();

Yeah, sorry I didn't see that the $rootScope was not available before.

i'm not sure this is that useful, I think for documentation purposes, it's better to clearly spell out the services being used. In real apps, you can test it however you want of course

@Narretz if you agree please close it, otherwise land at will

@marcin-wosinek What was your goal in changing this? Do you think this reflects testing reality more? Angular core uses both in tests, $rootScope and a derived scope.

I was confused by the $rootScope in test code. The controller doesn't use any $methods from scope, and even empty object would be enough for the test to work. Because of $rootScope in the test code I was searching for some hacks related to promise resolution - as $rootScope.$digest() when testing code that uses $q

I thought about this again and I have agree with @caitp that replacing rootScope with scope doesn't add much clarity to the test. Nevertheless, thanks for your contribution!


Can't display number of RFCs per country

Describe the issue
I'm trying to display the number of RFC authors per country:
https://datatracker.ietf.org/stats/document/yearly/country/?type=rfc
But the result is blank.
Tested on Linux Debian 11 with Firefox 123.0 and Chrome 122.0.6261.94

(see screenshot1)
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

See #3712. The stats module is known to be broken in many places and will be removed and later reimplemented.

Closing this as won't fix - it's linked to #3712, so it'll be captured in the re-implementation.


Small change in the README

This is a small change, but adding which units are used for an certain argument is really handy.

This would be incorrect, as you can use any time measurement (seconds, minutes, hours, etc.)

Yep, just put the unit after, e.g. 5m/h (haven't tried days or seconds)

(See previous comments to why it was closed)


feat: refactor entire sdk to be async

CorrespondingPr:
https://github.com/awslabs/smithy-swift/pull/389
Issue #

Closes #497
Conventional Commits

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This PR is blocked by a swift compiler bug on Linux reported here: https://bugs.swift.org/browse/SR-15659
Apple will prioritize this bug in January for us.

Update here for anyone following this PR, apple will do a release end of Jan/early Feb and once that happens, this PR will be merged in and released! https://forums.swift.org/t/development-open-for-swift-5-5-3-for-linux-and-windows/54553


rpc_execute.hpp 中 147, 275行的 connnect 这个拼写错误, 给改成 connection

Search before asking

[ ] I searched the issues and found no similar issues.

What happened + What you expected to happen
Reproduction way
Anything else
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Yes, thanks for your issue.

Fixed by #169


Custom vibration pattern not used

1 - Describe the bug
The custom vibration pattern is not being registered in a simple example.
2 - Provide us as much information as possible
To help us to understand your issue, provide with your bug report all the relevant informations, such as:

Your plugins list inside the file pubspec.yaml (at least all notification plugins): awesome_notifications: ^0.7.4+1
What platform did you found the issue: Android
What devices did you found the issue: Xiaomi Mi 9T Pro
The output of flutter doctor command: No issues found!

Simple application using custom vibration pattern:
const String channelKey = 'vibration_issue';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();

  AwesomeNotifications().initialize(
    null,
    [
      NotificationChannel(
        channelKey: channelKey,
        channelName: 'Vibration Issue',
        channelDescription: 'Vibration Issue Description',
        enableVibration: true,
        vibrationPattern: Int64List.fromList([0, 2000]),
      )
    ],
  );

  AwesomeNotifications().isNotificationAllowed().then((isAllowed) {
    if (!isAllowed) {
      AwesomeNotifications().requestPermissionToSendNotifications(
        channelKey: channelKey,
        permissions: NotificationPermission.values,
      );
    }
  });

  await AwesomeNotifications().createNotification(
    content: NotificationContent(
      id: 0,
      channelKey: channelKey,
      title: 'Simple Notification',
      body: 'Simple body',
      actionType: ActionType.Default,
    ),
  );

  runApp(const MaterialApp(title: 'Vibration Issue'));
}

3 - How To Reproduce the Error
Steps to reproduce the behavior:

Create new application with above source code
Run flutter pub add awesome_notifications
Go through https://pub.dev/packages/awesome_notifications#-configuring-android
Run application on Android

4 - Expected behavior
Use of the provided custom vibration pattern. Instead, the default one is used.
5 - Screenshots
N/A
6 - Additional context
I did uninstall the app and renamed the channelKey multiple times but it did not change the issue.
The custom vibration pattern is working correctly on the same device using package:flutter_local_notifications along with the minimal code below.
Minimal working custom vibration pattern example using package:flutter_local_notifications (on the same android device):
void main() async {
  WidgetsFlutterBinding.ensureInitialized();

  await FlutterLocalNotificationsPlugin()
      .resolvePlatformSpecificImplementation<
          AndroidFlutterLocalNotificationsPlugin>()!
      .requestPermission();

  await FlutterLocalNotificationsPlugin().initialize(
    const InitializationSettings(
        android: AndroidInitializationSettings('@mipmap/ic_launcher')));

  FlutterLocalNotificationsPlugin().show(
    0,
    "Vibration Working",
    "Vibration Working",
    NotificationDetails(
        android: AndroidNotificationDetails(
      "vibration_working",
      "Vibration Working",
      vibrationPattern: Int64List.fromList([0, 2000]),
    )),
  );

  runApp(const MaterialApp(title: 'Vibration Working'));
}

I'm trying to find an Android 13 device to test it out. I'll post my tests here soon. But for now, you can try using asset images instead of native resources.

I would just like to add that I tried to use package:vibration/vibration.dart (vibration: ^1.7.6) to generate custom vibration patterns (still on the same exact android device).
When I call await Vibration.vibrate(pattern: [0, 2000]); it is working exactly as expected.
It does not seem to be an issue with my device or with flutter/android/vibration combination.

Can we reopen please ?

Sure!

Could you please provide an estimation of when will this be fixed ?
This is currently putting a project of mine on halt.
I understand that you cannot fix it at the moment, but can you please give some kind of ETA ?
Thanks a lot.

Hi @gruvw, i just uploaded the new release versions of 0.7.5-dev.2+1 versions of awesome_notifications and awesome_notifications_fcm to fix this issue. Please, check it out to see if this issue is solved on these new versions.
Also, don't forget to join in your Discord Beta team to request fixes and new updates.

Thx, I can't find the commit that solved the issue, can you reference it please ?

I get an error in your library while compiling the fix you provided (@rafaelsetragni):
: Error: The argument type 'ImmutableBuffer' can't be assigned to the parameter type 'Image'.
resource_image_provider.dart:61
 - 'ImmutableBuffer' is from 'dart:ui'.
 - 'Image' is from 'dart:ui'.
    return decode(buffer);
                  ^
: Error: A value of type 'void' can't be returned from an async function with return type 'Future<Codec>'.
resource_image_provider.dart:61
 - 'Future' is from 'dart:async'.
 - 'Codec' is from 'dart:ui'.
    return decode(buffer);

Remembering that iOS does not have custom vibration patterns, unfortunately. And also some android distributions have some disturbance control to not allow abuse of this feature, as is the case with Xiaomi devices.

The issue is resolved for me.


Logo must be in left side and navbar list should be on right side

Logo should be on left side as per the modern website. Navbar list should be on right side of logo. And one more thing header section should always be on top even we are scrolling down.
Please assign me this necessary issue to me under GSSoC 2023.

Please assign me this necessary issue to me under GSSoC 2023

please assign me this (GSsoc 23)


reading the BRO data from XML files

Separate the reading of XML files from the API request so users can read manually downloaded XML files.
Discussed in https://github.com/ArtesiaWater/hydropandas/discussions/104

Originally posted by rt84ro March  2, 2023
Hi every one,
I have downloaded some wells from the BROloket website but their format is .xml. I want to read them using the HydroPandas but actually I do not know how I should open these files. could you please let me know how to read them?

I would like to implement this function. My starting point is to add an elif-statement to  from_bro, like code below. And a new function get_obs_list_from_file. Do you agree?
if bro_id is None and (extent is not None):
            obs_list = get_obs_list_from_extent(
                extent,
                [..]
            )
            meta = {}
elif bro_id is not None:
            obs_list, meta = get_obs_list_from_gmn(
                [..]
            )
            name = meta.pop("name")
elif (extent is None) and (bro_id is None) and (fn is not None):
            obs_list = get_obs_list_from_file(
                extent,
                [..]
                ignore_max_obs=ignore_max_obs,
            )
            meta = {}
else:
            raise ValueError("specify bro_id or extent")

Yes, seems logical to me. And in ``io_brothe code to parse the XML file would then be separated and called in each of theget_obs_list_from_*` methods?
Thanks for picking this up!

Yesterday I started with this issue. I think we need two extra variables to implement this issue: origin and local_path .
My personal issue is added in the last line of the table.

User case
Comment
value origin
value local_path

Get data from Broloket.nl
Like current behaviour of function
internet
None

Get data from Broloket.nl, and save Bro XMLs for future use
Like above, but save downloaded data
internet
path where zip will be created

Use downloaded data from Broloket.nl
User has downloaded data available, via manual download or case in row above
local
path to zip

Local GMW files that have to be uploaded to bronhouderportaal-bro
To check data in these files before submission
local_bronhouder
path to zip

I added bronhouder to origin  in the last use case, because these files have some minor changes compared to broloket.nl-files. E.g. the BROid is not available, because the file has not yet been sent to broloket.nl. The easiest way is to use a separate value.
What do you think about this approach @dbrakenhoff?

Thanks for the clear overview!
I think we should create two routes for getting data from the BRO, one API (internet) route and one local file route. So both ObsCollection and GroundwaterObs should get a from_bro() method for downloading data from the internet through the BRO API. I like your suggestion for storing this downloaded data, so these methods should accept some sort of directory or filename for storing the downloaded data.
Then I would suggest a separate route for reading the local files, from_bro_file/dir/local(), not sure what the name should be yet, but something along those lines. These methods accept a a directory/zip (in the case of ObsCollection), or a filename (in the case of Observation).
I think separating these two is probably clearest and makes the code less complicated.
Then bro.py should contain something like the following functions:

read_bro_xml() --> reads single BRO XML file
read_bro_dir() --> reads directory or zipfile with one or multiple XML files, basically calls the read_bro_xml() method in a loop.
replace the XML parsing in the current API functions with the read functions listed above.

@HMEUW, let me know what you think about this?
PS. I realize we're probably not very consistent across data sources in how we expose local vs API routes, but we shold probably address that in a separate issue. At this moment I'd vote for separating the two routes for each data source.

I just completed first version to read XMLs for newly construced wells. These are submitted to https://www.bronhouderportaal-bro.nl. @OnnoEbbens please have a look for this code. The full_meta function is not yet working. Code is in the 'add-bronh'-branch.

Started reading local BROloket files in the branch import-broloket-from file. Cannot make a direct link here.

Just comitted my work. I have holiday after this week. I cannot work on it before, and expect I have the two after my holiday no time either.
If someone else want to pickup in July or August. It is okay.


Lithuanian translations for validation.php

Sure thing!

Can you translate validation.file please ?
Thanks in advance

If you have in mind lt/validation.php file, I see that it is fully translated now.

No, you can see todo.md et the file attribut is not translated


CLI

Add a CLI to nanocoin that allows issuing the same queries/commands that the RPC interface does.

Initial work being done on PR #17

Implemented in PR #17


[2.7] MGMT-13551 Move reconcilePause control to automationControlData

reconcilePause control flag is currently only used by onChangeAutomationTemplate function inside automationControlData. The function relies on the control to be defined in the controlData otherwise an error occurs when trying to set reconcilePause.active value. Since the reconcilePause control was defined in clusterDetailsControlData, for the wizards (e.g. CIM or AI) which don't use this step the error occurred.
To fix this, we're moving the reconcilePause control to automationControlData which is only controlData which actually uses that flag.
Signed-off-by: Jiri Tomasek<EMAIL_ADDRESS>Cherry-picked from 405b2654

/retest

/retest

/hold pending 2.7.1 approval

/test pr-image-mirror-mce

/retest

@crizzo71 Can we get approval to merge this in 2.7.1? This is the UI crash when selecting an automation template for AI clusters.

/retest

/unhold


In services, when overload resolution fails, create a union signature

Fixes #19474
(getUnionSignatures seems like it would be useful but it returns a Signature[] and I just want a Signature.)

@sandersn Could you review?

@sandersn #17819 Works well (if I remember, the only change it had were visible in the .type baselines when we had them and they were always improvements); but that's just for contextual types, not actual overload resolution. I believe we've been hesitant to go so far as to change overload resolution, since in the past we've found people who depend on its current behavior. It's also worth noting that I think this, as written, doesn't just affect services; this could also affect inference and resolution in JS (which I believe also has diagnostic reporting off).
@andy-ms Would you be willing to check that the merged signature creation going on here functions the same as in #17819? It looks like you don't bother with setting the return type, and your rest parameter handling is a bit different, and you don't combine type parameters. If this is just a best-effort thing intended for the LS's quickinfo and such, why not set a flag on the signature we return today and generate the combined signature in the language service? createSignature is (internally) exposed, after all. I think the bar would be much lower for that.

@weswigham It looks like #17819 is doing a different thing than this -- that only modifies getContextualSignature. Meaning it will affect you if you write (x, y) => ... and need a type for x, but won't affect you if you call a function and need a contextual type for the argument.
Since this is for a different use case I'm not actually sure what the correct behavior for using type parameters would be -- type inference failed the first time or we wouldn't get here, so if we synthesized type parameters for the union signature we would have to do type inference again, but that might fail again... I think it's best to avoid that case and just leave it as an error. We can't expect to get a good contextual type from a call to a generic function that fails anyway.
As for the return type I think it would make sense to use an intersection type as in your PR, that way if you have:
declare function f(x: number): number;
declare function f(x: string): string;
f().toUpperCase();

You won't get an "extra" error at toUpperCase() since it's number & string. But you will get an error if you write toUperCase.
We can't accomplish this PR's goal by trying to create a new signature after the fact, because outside of the checker we don't know where a contextual type is coming from.


Incompatibility with PHP 7.4 line 52 src/Util/Str.php

ERROR 500 - Internal Server Error
substr() expects parameter 1 to be string, bool given [/var/www/html/vendor/vlucas/phpdotenv/src/Util/Str.php:52]
[vendor/vlucas/phpdotenv/src/Util/Str.php:52] substr()
[vendor/vlucas/phpdotenv/src/Store/File/Reader.php:76] Dotenv\Util\Str::utf8()
[vendor/phpoption/phpoption/src/PhpOption/Some.php:108] Dotenv\Store\File\Reader::Dotenv\Store\File\{closure}()
[vendor/vlucas/phpdotenv/src/Store/File/Reader.php:79] PhpOption\Some->flatMap()
[vendor/vlucas/phpdotenv/src/Store/File/Reader.php:48] Dotenv\Store\File\Reader::readFromFile()
[vendor/vlucas/phpdotenv/src/Store/FileStore.php:62] Dotenv\Store\File\Reader::read()
[vendor/vlucas/phpdotenv/src/Dotenv.php:222] Dotenv\Store\FileStore->read()
[global.php:32] Dotenv\Dotenv->load()
[process_tables.php:3] require('/var/www/html/global.php')
To fix this, I changed line 52  in /src/Util/Str.php from:
if (\substr($converted, 0, 3) == "\xEF\xBB\xBF") {
to
if (\substr("$converted", 0, 3) == "\xEF\xBB\xBF") {
That appears to have "fixed" my problem.

 Thanks for pointing this out. This happens when decoding fails. I'll adjust the code so the proper error is bubbled up for you. I think the change you made will instead result in the .env file being thrown away.

Thank you!

What encoding were you trying to use btw? My "fix" will just make your app crash with an error saying "UTF-8 decoding failed." instead.

What encoding were you trying to use btw? My "fix" will just make your app crash with an error saying "UTF-8 decoding failed." instead.

Not sure, just plain text I suppose. I know it's UTF-8 though. No weird characters or BOM's introduced.

What's happening is mb_convert_encoding($input, 'UTF-8') is returning false on your machine.

You could try installing ext-mbstring. We use a symfony provided polyfill which may contain bugs. Using the extension may fix this issue for you.

I ran composer require ext-mbstring and that installed fine. Same error.
My .env file looks like this:
PMA_HOSTNAME = "phpmyadmin.localhost"
MYSQL_DATABASE = m00000685
MYSQL_USER = m00000685
MYSQL_PASSWORD = redacted
MYSQL_ROOT_PASSWORD = redacted
MYSQL_PORT = 3306

Don't know if that helps.
The PHP loader looks like this:
<?php

require_once("/var/www/html/vendor/autoload.php");
$env = Dotenv\Dotenv::createImmutable("/var/www");
$env->load();
extract($_ENV);
$dsn = "mysql:host=mysql;dbname=${MYSQL_DATABASE};port=${MYSQL_PORT};charset=utf8mb4;";
...

It is not possible to install PHP extensions using composer. It's likely the extension is still not installed.
Can you run this code on your server:
<?php

var_dump(function_exists('mb_convert_encoding'));

I found the php7-mbstring package for Alpine Linux, 3.15.0 which is what I am building for my lightweight Nginx + PHP-FPM container which my application runs in.
I've gone ahead and added the Alpine php7-mbstring package so now that core function made available.
After doing this, the problem went away. This is not a bug in your software. This was the lack of the proper core PHP function being available after upgrading my container to PHP 7.4.
Thank you for helping me pinpoint this.

I am also getting Internal Server Error when trying to load dotenv in a production server.
If I comment out the following two lines, the internal server error goes away, so I know it has to do with dotenv
$dotenv = Dotenv\Dotenv::createImmutable(__DIR__);
$dotenv->safeload();

I tried your suggestion and ran var_dump(function_exists('mb_convert_encoding')); and I get: bool(true)
I am running the same php version locally and on my production server. Please help?


PowerToys connect to the internet without permission

Microsoft PowerToys version
"0.35.0"
Running as admin
Area(s) with issue?
General
Steps to reproduce
Start Power Toys.
Application tries to connect to somewhere.
✔ Expected Behavior
No initiated internet connections.
❌ Actual Behavior
Power Toys try to connect to <IP_ADDRESS>.
Other Software
No response
This utility should not ever connect to anything without explicit permission, ie update check or something else.
There should be an update check, yes, but it should be togglable.
In addition, if there is the .NET runtime missing, don't just to blindly try to download it, ask for permission to do this. This is inpolite, not to ask for such permissions to do so.

@shakeyourbunny We're fully open source and you can see exactly what happens E2E :)

<IP_ADDRESS> is GitHub IP, that is us every 24 hours seeing if there is an update.

This is still not a v1 piece of software yet, we want people on the latest to reduce support issues.
This behavior is no different than most software.  More so with an pre-release software.
We could have a toggle but this would be post stability push.

Good feedback but our readme does clearly state this is a requirement. By installing, you've made the choice to get the needed requirements to run the software. We are thinking about that in #10126 for a install better experience but opt'ing out would cancel install then as a required dependency.  If you have the up-to-date version installed, it doesn't download.


Write Cluster testbed research plan

I think this is blocked until I finish #4, #5, #6, and #7 for a baseline of what we already have. If it feels like I can do this before I finish those entirely, I will.

I can move ahead without finishing those other issues. Working on a draft in google docs now because google has better writing collaboration tools, and then will move to this repo when it is a little more finalized.

We now have a pretty nice research plan :) In the end, it looks like we should provide a test suite for users to measure performance (in addition to questions to evaluate use cases, and evaluate user understanding of IPFS and Cluster systems). I'm checking with the team to see if it makes sense to break these two goals apart (general questions + performance testing), or (say, if the test suite isn't far off), reach out to participants at the same time to participate in both activities.

This issue is stale. Closing.


yf.download hangs on last item if downloading more than 79 tickers

I'm calling yf.download(tickers, start="2019-01-01", end="2019-05-29", auto_adjust=True, group_by="ticker")
I've tried this with tickers as a space separated string or a list, aa=F, gb=columns, no start or end, different lists of tickers, threads=False . Same result with anaconda 3.7.1 and collaboratory 3.6.7.

Ok, I tried putting yf.download() into a for loop and staying below 79 tickers per call:
ticks = dfs.loc[:,'symbol'].to_list()[:200]
df = []
for i in range((len(ticks) // 75) + 1):
  time.sleep(1)
  ticker = ticks[-75:]
  ticks = ticks[:-75]
  df.append(download(ticker, start="2019-05-20", end="2019-05-29", auto_adjust=True, group_by="ticker", threads=False))

This hung on the second list of 75 tickers (149/200 overall).
Next I pasted the source into a jupyter notebook and tried inserting _time.sleep(1) into the for loops at line 460 and 474. By doing this I discovered that the code was only using the multi-threaded version (line 460 isinstance(threads, int) evaluates to true if threads = False because bool is considered int for its purposes (False is 0 and True is 1 - and both evaluate as int and bool for isinstance(), not what I expected ). Recommend changing 460 to if threads > 1: to enable single threading with threads = False or threads = 1, while preserving multithreading for threads = True and threads = 2 or more.
Once I enabled single threading with the change to 460, the problem went away in both the looped approach and single batch without any need to slow things down. Would love to know if anyone can reproduce the problem with the threaded version before I go any further.

Fixed. Please update yfinance and report back please :)

Confirmed works with both threading and sequential. Obviously I should have checked for duplicate tickers in the lists I used to test. Out of curiosity, how did you know this was the issue?
Thanks!

I have no good answer to that... Just a hunch  :)

I am still facing this issue. The last few symbols does not get downloaded and the download is stuck with no error message.
Call:
price=yf.download(sym_list,startdate,enddate)
sym_list is a list of 8318 syms


feat(form-group): update story to Storybook v7

Related Ticket(s)
Closes #11385
Description
Adjustments to form-group component stories to be compatible with Storybook v7.
Changelog
Changed

Updated form-group Storybook stories for Storybook v7

Looks like the submit button styles are off as well (exists in production). I'll create an issue so we can follow up after the SB7 work is complete.


Suggestion: Swipe to change image

Generally speaking, behaviour similar to the stock Gallery app in which swiping left or right changes to the next or previous image result respectively (assuming reverse chronological order).

working on it :)

Aand done. Coming with the next release, tho I did not add fancy animations.


after update of authentic-theme i was redirected to my 'Default module for Webmin'

If i don't have set any 'Default module for Webmin' i get redirected to the Dashboard but if i have set the 'Default module for Webmin' i get redirected to this page after an update of the authentic-theme.
Is this really correct?

By default, when you reload the page, you will be taken not to default module for Webmin but to previously used page.
After theme update - page reload happens. You should be taken to Theme Settings in case you run update from there or to System Information page or to any other page, in case you trigger update from the Side Slider.

I that case something is wrong. I will get to the 'Default module for Webmin' every time after an update. To get to the Dashboard i need to empty the 'Default module for Webmin'...

Yes, in case you clear default module, System Information becomes default.
If you go to any page, let's say Webmin Configuration and then reload the page after few seconds. Will you get back to exact the same page after the reload?

In that case the 'Default module for Webmin' is useless for me. I want to get back to the Dashboard but it is sad that i can't use the Webmin button because now that button do nothing :(

When you click Webmin switch (top of navigation menu) you must get to default Webmin module, that is set in theme's settings (that corresponds with Webmin Configuration by the way). Same happens in case you click on Virtualmin/Cloudmin switch.
In case you click on Dashboard switch (which is only visible if there is no Virtualmin/Cloudmin modules installed), then you must get to System Page (always).
If you reload the page, then you should get to the previously used page. Isn't that what's happening for you?

What i do is:

Open theme configuration.
Set Default module for Webmin to Read user mail and save it.
Go back to the Dashboard by clicking the Dashboard switch.
To update i open the theme configuration.
I use the Force update theme.
When it is finished it will now show the Read user mail page instead of the Dashboard.

The Webmin switch seems to be nice to use as a shortcut button or something, but i don't want it to be the default page after an update. But i leave the Default module for Webmin empty and use it as i did before, or should i say i don't use it.

Alright, I don't disagree. I like the idea is returning to System Information page after update. I will do it.
Plus I will add a control to Side Slider, where you could run theme info, apply update and do more with one click.

Give it a try.
Thanks.


Feature request: Activate local SD recording

Hi and thank you for a great integration!
Would it be possible to implement a feature to activate local recording on the camera's internal SD card?
It would be preferable to activate recording upon a trigger activation, e.g. a external motion sensor or triggered alarm.

If I am not mistaken it does exist in current version of the product. (I am using it) Please @TPMunster  check and close this issue.

@cpainchaud the camera itself has local SD recording. I can toggle whether it is activated or not from Home Assistant. But, when activated the camera records on its SD card when it detects motion in its own image - not based on e.g. an automation.
I cannot seem to fire a "camera.record.local" action, but please do guide me if you have it working?! 🙏
Thank you in advance.

this is a setting that you must configure in the camera application from your smartphone. You want to configure the Schedule menu : disable everything in Timer section and select what you want in Alarm section.
This will not be added to this integration because HA is not meant to be a device configurator. Only what is useful for automation will be implemented in my opinion.
Current "SD Card recording" button will enable/disable recording feature entirely but you will still need to configure the "Schedule" part within your camera directly

I am not quite sure i'm explaining myself correctly.
Perhaps if I explain the scenario it would make more sense:
Here goes:
If the Alarm is triggered in my house, I would like to tell the camera to start recording - locally. How do I achieve this with the current integration?
It should not record at any other time.

You should create an automation, triggered by the alarm. The automation should turn on the recording switch. Also create an automation to turn it off again after x minutes for example.

Exactly yes

Well, that is not how it works IRL. When you toggle that switch you toggle the setting within the camera, and not starting a recording. It will still only start recording if it detects motion within its picture.
Here is my documentation:
Activated Recording switch in HA @ 12:07:

Screenshot from the Reolink app, showing no recording on the timestamp of my activation of switch in HA.

Instead it toggles the camera setting within itself, and still only records when motion is detected

Edit record scheduling to enable everything in the Timer tab
On Wed, Sep 29, 2021, 12:22 TPMunster @.***> wrote:

Well, that is not how it works IRL. When you toggle that switch you toggle
the setting within the camera, and not starting a recording. It will still
only start recording if it detects motion within its picture.
Here is my documentation:
Activated Recording switch in HA @ 12:07:
https://user-images.githubusercontent.com/68892864/135249687-d8cc7cf6-639a-41ba-bd90-d108cd509cbc.png
Screenshot from the Reolink app, showing no recording on the timestamp of
my activation of switch in HA.
https://user-images.githubusercontent.com/68892864/135250006-3bda1211-dadf-456a-95d5-1287936f32a5.jpg
Instead it toggles the camera setting within itself, and still only
records when motion is detected
https://user-images.githubusercontent.com/68892864/135250342-95bd2d2c-dd0b-4a6a-8388-6225f3333dc5.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fwestenberg/reolink_dev/issues/246#issuecomment-930046741,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTC5PSBTMDKMHGGKGU3CDLUELSHHANCNFSM5CLMZ3IA
.
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.

@cpainchaud @fwestenberg ABSOLUTLY correct! Thanks a million, it works as intended! 🙏


Example app: Unable to navigate using table of contents

Using the example app, I'm unable to navigate to the selected page. The modal closes but it doesn't perform the navigation.
Upon further investigation, I found out that onPress parameter on TableOfContents component returns a Link and not a Locator.
I also attempted to use the returned Link object as the initialLocation but it didn't work too.
Swipe navigation works as expected.

@adesege ahh yes. Links and Locators are not identical. The link needs to be converted into a locator before navigation is called. A primitive way of doing this is:
setLocation({
  href: link.href,
  type: 'application/xhtml+xml',
})

You can see more detail on this here

Ok, noted. Do you think this should be handled automatically from the native side, in the library's javascript side or the example app?

Happy to help, @jspizziri. Here's the PR https://github.com/5-stones/react-native-readium/pull/37.
I'll resume working on the PDF #8 support and let you know if I have questions.
Cheers!


Flex sensor

@mmoskal can you check my adc code modifications?

We have to use a different ADC conversion routine for channels 15, 16, and 17.


Exposure Analysis / Cigarette Smoking Example

For the example exposure analysis an "undefined error, please try again," is displaying on the "4. Estimate Effects" tab, "Estimate causal effects" section. The "Run now" button is grayed out.

https://github.com/microsoft/showwhy/issues/399#issuecomment-1511473185


link APK files and install them quickly

          Our customer's LOB is based Android. in this scenario link .apk to the WSA can allow our customers easily deploy they Android LOB app on our Surface Pro. or is there any other way to massively deploy Android LOB App to the WSA.

Originally posted by @TAMSHUI in https://github.com/microsoft/WSA/issues/61#issuecomment-1849658503

use wsa-pacman to install apps directly. but it is not recommended to use this because you have to turn on developer mode and adb forever, which will use recourses in your system.


Validating packages are listed under "Unlisted" on "Manage Packages" page

When package is in "Validating" state it appers under "Unlisted" on "Manage packages" page, which is a bit confusing.

Always wanted to fix this but in a better way. I have good idea on what to do here 🙂
Will put my thoughts as some rough sketches soon.


DynamicLinks patch version for c99 compatibility fix

Include c99 compatible fix in Firebase 5.11.0 so that FDL works with Unity

cc: @dmandar @stewartmiles


feat: Disable user Gnome extensions & user-installation of them

please add a screenshot of local testing

please add a screenshot of local testing

It seems that disable-user-extensions disables all extensions actually, including system ones.
Setting allow-extension-installation to false will disable further install of all user extensions (currently installed user extensions will remain)
What is your preference to this?

Here's how Extension Manager behaves when GNOME user extension installation is disabled:
https://github.com/user-attachments/assets/dfc51ee1-9f6a-4e2f-a202-7560d738503b


Task - Mark as complete button shows up on cancelled task report

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.47-0
Reproducible in staging?:. yes
Reproducible in production?: yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:

Go to staging.new.expensify.com
Go to chat.
Create a task.
Click on the task.
Click 3-dot menu > Delete > Delete the task.
Go to the cancelled task report from LHN.

Expected Result:
Mark as complete button will not show up on cancelled task report.
Actual Result:
Mark as complete button shows up on cancelled task report. Clicking on the button leads to error.
On mweb, Android and iOS app, the button appears and disappears after opening the cancelled task report.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/eedb683a-b9f1-469e-9a4b-be9ecebee0bc

View all open jobs on GitHub

We think that this bug might be related to #vip-vsb
cc @quinthar

FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

Asking in Slack - https://expensify.slack.com/archives/C066HJM2CAZ/p1709658682543139

Added to #vip-vsb. @situchan can you review the proposal here when you get a chance?

Proposal
Please re-state the problem that we are trying to solve in this issue.
After creating a new task and then deleting it, the mark as complete button should also not be shown on the page.
For instance, in the below image, the "Mark as complete" button should not be visible because the task has been deleted.

An error being displayed when the button is clicked is a side-effect of this problem, and ensuring that the button is not visible should also fix this.
What is the root cause of that problem?
The ReportUtils.isOpenTaskReport function call in HeaderView.js is not being passed the parentReportAction.
https://github.com/Expensify/App/blob/a79c119a85b4f71cf902e047f4b73615f0f4f3db/src/pages/home/HeaderView.js#L362
This is necessary because the isOpenTaskReport function calls isCanceledTaskReport which required a parentReportAction value to determine if a task is deleted or not.
https://github.com/Expensify/App/blob/a79c119a85b4f71cf902e047f4b73615f0f4f3db/src/libs/ReportUtils.ts#L671
https://github.com/Expensify/App/blob/a79c119a85b4f71cf902e047f4b73615f0f4f3db/src/libs/ReportUtils.ts#L652
What changes do you think we should make in order to solve the problem?

Pass the parentReportAction to the ReportUtils.isOpenTaskReport function call in HeaderView.js. The parentReportAction has already been defined in the component and is being used in multiple places.
https://github.com/Expensify/App/blob/a79c119a85b4f71cf902e047f4b73615f0f4f3db/src/pages/home/HeaderView.js#L362

The above step should fix this issue, but we are using the ReportActionsUtils.getParentReportAction function to define the parentReportAction but this method has been deprecated.
https://github.com/Expensify/App/blob/a79c119a85b4f71cf902e047f4b73615f0f4f3db/src/pages/home/HeaderView.js#L113
If the reviewer feels this should also be addressed in the scope of this PR. We can pass the parentReportAction as a prop to the HeaderView component. Alternatively, we can also create a new method which uses Onyx.connect() or withOnyx().

What alternative solutions did you explore? (Optional)

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~0153fc53185acededc

@situchan could you review?

Bump @situchan

There's viable proposal. I will test shortly and approve.

Any update @situchan?

updating today

@dukenv0307 thanks for the proposal. Can you confirm that your solution covers this bug as well?
As seen in video, task view briefly shows:
https://github.com/Expensify/App/assets/108292595/97f06bf9-4a9f-4f7e-98bf-6d24614d569b

@dukenv0307's proposal looks good to me.
🎀 👀 🎀 C+ reviewed

Assigning @dukenv0307 🚀

@dukenv0307 - Do we need a regression test for this one?

Payment summary:

Contributor: @dukenv0307 $500 (paid in Upwork)
Contributor+: @situchan $500 (paid in Upwork)


Redis errors when visiting Commons sites

Describe the bug
Multiple user sites and Commons network homepage are experiencing an issue where users receive an error message that reads, "Error establishing a Redis connection" "To disable Redis, delete the object-cache.php file in the /wp-content/directory." This error is sporadic, in that it does not appear for all users and occurs across devices and browsers. For example, one user of HASTAC Commons has reported the issue on mobile in private browsing, while another reported it only in a non-private window.
One user reported they only receive the message when they type their site's URL into the browser. When they link to it from other sources it works.
The sites that this error has been reported are:
https://introdigitalstudies2024.commons.msu.edu
https://aicommons.commons.msu.edu/
Mobile only: hastac.hcommons.org
Mobile only: up.hcommons.org

Fixed


Break Backward Compatibility

Someday soon we're going to have to break backwards compatibility, and we may as well rip the bandage off. This is a tracking ticket for all the backwards incompatible changes that should go into the next breaking release (1.0?).

#6 allow arbitrary shard names
#95 separate shard and replicaset names
#153 remove references to 10gen
#158 support compound sharding keys
#179 stop creating a mongodb_instance in mongodb::default
#262 update default paths to match mongodb defaults
#309 use yaml format config, incompatible with < 2.6 mongo

Moved to https://github.com/chef-brigade/mongodb-cookbook/issues/78


Build failure: linuxKernel.kernels.linux_5_4_hardened

Steps To Reproduce
Steps to reproduce the behavior:

build linuxKernel.kernels.linux_5_4_hardened (with NIXPKGS_ALLOW_BROKEN=1)

Build log
[...]
QUESTION: Debug boot parameters, NAME: DEBUG_BOOT_PARAMS, ALTS: Y/n/?, ANSWER:
GOT:
QUESTION: CPA self-test code, NAME: CPA_DEBUG, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Debug low-level entry code, NAME: DEBUG_ENTRY, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: NMI Selftest, NAME: DEBUG_NMI_SELFTEST, ALTS: N/y/?, ANSWER:
GOT:
QUESTION: Debug the x86 FPU code, NAME: X86_DEBUG_FPU, ALTS: Y/n/?, ANSWER:
GOT:
QUESTION: ATOM Punit debug driver, NAME: PUNIT_ATOM_DEBUG, ALTS: M/n/y/?, ANSWER:
GOT:
GOT: Choose kernel unwinder
GOT: > 1. ORC unwinder (UNWINDER_ORC)
GOT:   2. Frame pointer unwinder (UNWINDER_FRAME_POINTER)
CHOICE: 1-2?, ANSWER:
GOT:
GOT: #
GOT: # configuration written to .config
GOT: #
GOT: make: Leaving directory '/build/linux-5.4.240'
warning: unused option: DEBUG_INFO_BTF
warning: unused option: INET_DIAG_DESTROY
warning: unused option: INET_MPTCP_DIAG
warning: unused option: INET_RAW_DIAG
warning: unused option: INET_TCP_DIAG
warning: unused option: INET_UDP_DIAG
warning: unused option: IO_STRICT_DEVMEM
error: unused option: REFCOUNT_FULL
warning: unused option: SECURITY_WRITABLE_HOOKS
warning: unused option: STRICT_DEVMEM

Additional context
This causes many failure in Hydra (one per module).
The non-hardened version works fine.
Other kernel versions work fine.
Notify maintainers
@TredwellGit
@Ma27
@NeQuissimus
@alyssais
@thoughtpolice
@RaitoBezarius (for previous ZHF discussion)
ZHF: https://github.com/NixOS/nixpkgs/issues/230712
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.2.13, NixOS, 22.11 (Raccoon), 22.11.20230430.db1e4ee`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.1`
 - channels(root): `"nixos-22.11"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

This is linked with commit bfef542b67ccfff0cfdc6f827db72910c965092e (Feb 21 23:41:34 2023): "use meta.broken, not assert"

linuxKernel.kernels.linux_5_4_hardened was introduced in 3af43aa8792e654f77f3e63749a6d0f5b948fb70 and seems to build fine at this commit. I am going to git bisect from this point.

The commit breaking linuxKernel.kernels.linux_5_4_hardened is 52f8cf58a4504e5e219faebffa51033e400e3aec (found via bisect).

Could this be the same as #232303?
Since the build failure is actually in kernel.configfile, not the actual kernel build.

I confirm that the build failure is linuxKernel.kernels.linux_5_4_hardened.configfile.
It seems that pkgs/top-level/linux-kernels.nix specifies that linux_5_4_hardened uses gcc10:
     linux_5_4_hardened = recurseIntoAttrs (hardenedPackagesFor kernels.linux_5_4 {
       stdenv = gcc10Stdenv;
       buildPackages = buildPackages // { stdenv = buildPackages.gcc10Stdenv; };
     });

but adding echo ${buildPackages.stdenv.cc} in https://github.com/NixOS/nixpkgs/blob/8ee5a6fcbf8d98936fe1a336ac21ef1f31d28310/pkgs/os-specific/linux/kernel/generic.nix#L150 outputs /nix/store/7wkshj58fcsl1f3zyi67qsxgl1p8nki1-gcc-wrapper-12.2.0.
There is definitely something off in these Nix expressions. I don't understand why the configfile derivation sees gcc12 rather than gcc10.

linuxKernel.packages.linux_5_4_hardened.kernel.stdenv.cc:

«derivation /nix/store/ch69410hjaid50ahciri4qq5fxwb5dmp-gcc-wrapper-10.4.0.drv»

linuxKernel.kernels.linux_5_4_hardened.stdenv.cc

«derivation /nix/store/c3hq1kg9ylf72b2rp0n6xj13nl8zd8xf-gcc-wrapper-12.2.0.drv»

It looks like there is another definition here which doesn't override the stdenv:
https://github.com/NixOS/nixpkgs/blob/859e3f35c8877a5c55585ca15c6956b4fc255102/pkgs/top-level/linux-kernels.nix#L266
But since the failures are happening in the kernel package-set, I don't believe the kernel with the missing stdenv is related.


Rng

This is on top of ndec PR
Fixed the typo in case name and verfied on db410c and db820c
Fixed case for other two as module name is msm_prng

Rebased and merged locally.


SecondaryVisbilityStore validation failed

Expected Behavior
I want to migrate the visibility store from ES to Postgres using Dual Visibility Store feature. Expected behavior to be able to dual write to both ES and Postgres. Temporal config:
  visibilityStore: es-visibility
  secondaryVisibilityStore: pg-visibility
  datastores:
    pg-visibility:
      SQL:
    es-visibility:
      elasticsearch:

Actual Behavior
Upon starting the server, I got the following error persistence config: cannot set secondaryVisibilityStore when visibilityStore is setting elasticsearch datastore
Steps to Reproduce the Problem

Setup the config as above
Start temporal server

Specifications

Version: 1.22.3
Platform: Linux

The error persistence config: cannot set secondaryVisibilityStore when visibilityStore is setting elasticsearch datastore is a known limitation in Temporal Server versions prior to 1.23.  This is because dual Visibility is a new feature introduced in Temporal Server 1.21 and later. You can use dual Visibility with SQL databases like PostgreSQL for advanced Visibility, but not with Elasticsearch.
Here's a breakdown of the issue and a solution:
Problem:

You are attempting to configure dual Visibility with Elasticsearch as the primary Visibility store and PostgreSQL as the secondary.
However, before Temporal Server 1.23, the code did not support dual Visibility with Elasticsearch.

Solution:

Upgrade to Temporal Server 1.23 or later: Dual Visibility with Elasticsearch is supported in Temporal Server 1.23 and later.

Update your configuration: You can then configure your temporal-server.yaml file to use Elasticsearch as the primary Visibility store and PostgreSQL as the secondary Visibility store:
persistence:
  visibilityStore: es-visibility
  secondaryVisibilityStore: pg-visibility
  datastores:
    pg-visibility:
      SQL:
        pluginName: "postgres12"
        databaseName: "temporal_visibility"
        connectAddr: "your_postgres_host:5432" # Replace with your PostgreSQL connection details
        connectProtocol: "tcp"
        user: "your_postgres_user"
        password: "your_postgres_password"
        maxConns: 2
        maxIdleConns: 2
        maxConnLifetime: "1h"
    es-visibility:
      elasticsearch:
        version: "v7" # Or "v8"
        url:
          scheme: "http"
          host: "your_elasticsearch_host:9200" # Replace with your Elasticsearch connection details
        indices:
          visibility: temporal_visibility_v1
          secondary_visibility: temporal_visibility_v1_new

Additional Information:

Dual Visibility Setup Guide: For a detailed guide on how to set up and manage dual Visibility, refer to How to set up Dual Visibility.
Migrating Visibility Databases: You can use dual Visibility to migrate your Visibility store data from Elasticsearch to PostgreSQL. Refer to the How to migrate Visibility database guide for a step-by-step process.
Temporal Server Release Notes: For details about new features and changes, you can always check the Temporal Server release notes.
Temporal Configuration Reference: You can find detailed information about all the configuration options for Temporal Server in the Temporal Server configuration reference.

By upgrading to Temporal Server 1.23 or later and updating your configuration, you can leverage the dual Visibility feature to migrate your Visibility data from Elasticsearch to PostgreSQL.

Thanks for reporting the issue. This is currently a known limitation with Temporal 1.22.3 and earlier, where dual writing to both ES and Postgres is not supported. You can find more information about dual visibility and the limitation in the Dual Visibility dynamic configuration reference.
You will need to upgrade to Temporal Server v1.21 or later to have dual visibility enabled.

Thanks for reporting this issue.
This error message "persistence config: cannot set secondaryVisibilityStore when visibilityStore is setting elasticsearch datastore" indicates that the Temporal Server does not support setting a secondary Visibility store when the primary Visibility store is Elasticsearch.
The Dual Visibility feature is designed to work with SQL-based Visibility stores (MySQL, PostgreSQL, SQLite).  You can't use Elasticsearch as a primary Visibility store and then add a secondary SQL store.
As a workaround, you could try the following:

Use SQL as your primary Visibility store:  Switch to using MySQL, PostgreSQL, or SQLite as your primary Visibility store. Then, you can configure Elasticsearch as your secondary store for dual writing.
Migrate to Temporal Cloud: Temporal Cloud supports both Elasticsearch and SQL databases for advanced Visibility features, along with automated failover and 99.99% uptime.

For more information about setting up a Visibility store and advanced Visibility features, refer to the documentation here: https://docs.temporal.io/visibility

Thanks for reporting the issue. You are encountering this error because the secondaryVisibilityStore setting can only be used with a visibilityStore that uses a SQL datastore, and in your configuration, you are using the elasticsearch datastore for the visibilityStore.
To work around this, you can use a SQL datastore for the visibilityStore and then set the secondaryVisibilityStore to your ES store. For example:
  visibilityStore: pg-visibility
  secondaryVisibilityStore: es-visibility
  datastores:
    pg-visibility:
      SQL:
    es-visibility:
      elasticsearch:

You can find more information on the configuration options in the Temporal Service configuration documentation.

Thanks for reporting the issue. You are encountering this error because dual Visibility Store feature currently only supports SQL based datastores, not elasticsearch. To migrate your Visibility Store from ES to Postgres, first set up a secondary Postgres Visibility Store. Then enable dual Visibility Store feature by setting secondaryVisibilityStore and  system.secondaryVisibilityWritingMode  in dynamic config, and write to both stores. Once the data is migrated, you can disable writing to the ES store and  then make your Postgres Visibility Store the primary store. This is the suggested workaround.

Thanks for reporting this issue. It appears you are encountering a known issue where Temporal does not allow setting a secondary Visibility store when using Elasticsearch as the primary.  You can work around this by using one of the following supported databases for your visibility store:

MySQL (v5.7 and later,  v8.0.17 and later for advanced features with Temporal Server v1.20 and later)
PostgreSQL (v9.6 and later,  v12 and later for advanced features with Temporal Server v1.20 and later)
SQLite (v3.31.0 and later for advanced features)
Elasticsearch (supported versions)
For more information on setting up the Visibility store, you can consult this documentation: https://docs.temporal.io/self-hosted-guide/visibility


Make Docker build errors more useful

Closes #367
Overview
It was the case that errors during Docker builds were uncaught and surfaced as if they were exceptions thrown by the Garden app. This meant that the user got a big Typer stack trace that had nothing to do with their build issue.
We expect build errors to happen during normal usage, say if a user has a bug in their notebook or a bad requirements file. This PR makes it so that if there is a build error, we display the full build log so the user can diagnose the issue. We also display a helpful message at the end.
Discussion
For the case where there is a bug in the user's notebook code, we now put the relevant traceback right where they can see it and act on it.

Testing
I tested manually with the notebook publish command. I used a notebook where I divided by 0 to test the "build" segment and a known-bad requirements.txt to test the "prebuild" segment. I also added a new unit test.
Documentation
No docs changes.

📚 Documentation preview 📚: https://garden-ai--399.org.readthedocs.build/en/399/

Codecov Report
Attention: 11 lines in your changes are missing coverage. Please review.

Comparison is base (6006881) 75.32% compared to head (0877408) 75.63%.

Files
Patch %
Lines

garden_ai/app/notebook.py
74.19%
8 Missing :warning:

garden_ai/containers.py
87.50%
3 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #399      +/-   ##
==========================================
+ Coverage   75.32%   75.63%   +0.30%
==========================================
  Files          45       45
  Lines        2614     2643      +29
==========================================
+ Hits         1969     1999      +30
+ Misses        645      644       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


How to add today's view background

There is a need to set the context of the day apart. How to do that

There is a need to set the context of the day apart. How to do that

There is a need to set the context of the day apart. How to do that

There is a need to set the context of the day apart. How to do that


Missing parameters used in Dialog.enable expressions inside annotations

Describe the bug
Variables not present in the model are used in Dialog annotations.
To Reproduce

Enable Dymola pedantic mode from Simulation Setup.
Navigate to TRANSFORM top directory
Right click on TRANSFORM and select Check
See the errors in the messages view:

Undeclared variable: modelStructure_shell
in the Dialog.enable attribute of steamGenerator.lumpPressureAt_shell declared in class TRANSFORM.HeatExchangers.GenericDistributed_HX
Undeclared variable: modelStructure_tube
in the Dialog.enable attribute of steamGenerator.lumpPressureAt_tube declared in class TRANSFORM.HeatExchangers.GenericDistributed_HX
Undeclared variable: modelStructure
in the Dialog.enable attribute of coreSubchannel.lumpPressureAt declared in class TRANSFORM.Nuclear.CoreSubchannels.Regions_3

This happens for TRANSFORM.Nuclear.CoreSubchannels.Regions_1, Regions_2, Regions_3.
Expected behavior
To check the library without any errors.
Computer Configuration (please complete the following information):**

OS: Windows 10
Modelica IDE and version: Dymola 2021

Thank you for mentioning this. This prompted me to go ahead and do a library wide pedantic check. Many issues were fixed with #72.


Fix for animations with relative loop mode.

Related forum issue: https://forum.babylonjs.com/t/ace-input-value-doesnt-change/46022
The reason for the errors in ACE was that, when editing values/moving the playhead/etc, the _interpolate function was called, but the animation state's offsetValue is undefined at the time. Since offsetValue is defined as optional, I added a check for the undefined case, returning the previously defined _staticOffsetValueXXX values.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14560/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14560/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14560/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14560/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14560/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14560/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14560/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14560/merge#BCU1XR#0


Add all contributors project

@all-contributors please add @Hongarc for projectManagement, review, tests and code

@all-contributors please add @Hongarc for projectManagement, review, tests and code

@all-contributors please add @Schmavery for ideas

@all-contributors please add @23phy for talk

@all-contributors please add @23phy for talk


[BUG] LaTex formulae vanish in dark mode

Our equations and formulae coded by LaTex will disappear when change the contrast into dark mode.

@AakashGfude can you please work on this tomorrow.


Ruby files have known CVEs

Install chef-18.4.12-1.el9.x86_64.rpm
view file /opt/chef/embedded/lib/ruby/gems/3.1.0/gems/rbs-2.1.0/steep/Gemfile.lock
Active Support version is listed as vulnerable to CVE-2023-22796
view file /opt/chef/embedded/lib/ruby/gems/3.1.0/gems/typeprof-0.21.2/vscode/package-lock.json
semver version is listed as vulnerable to CVE-2022-25883
view file /opt/chef/embedded/lib/ruby/gems/3.1.0/gems/typeprof-0.21.2/vscode/package-lock.json
minimatch version is listed as vulnerable to CVE-2022-3517
can you upgrade these libraries?

@simonsteiner1984 I believe these may be part of the Ruby install itself, and not directly included in Chef or related/dependent projects. Looking at an upgrade to Ruby 3.1.4 for an upcoming release for other CVEs and these should also be included in that upgrade if the 3.1.4 install I have is any indication.

With newer rpm:
https://packages.chef.io/repos/yum/stable/el/9/x86_64/chef-18.5.0-1.el9.x86_64.rpm
/opt/chef/embedded/lib/ruby/gems/3.1.0/gems/rbs-2.7.0/steep/Gemfile.lock
Active Support version is listed as vulnerable to CVE-2023-22796

@simonsteiner1984 upgrading 18.6.1 to 3.1.6... working on the release right now. However, some of these may be coming from sources beyond chef/chef itself.


Jenkinsfile tweaks.

Move to a newer agent type which should perform
better.
Set default timeout of 1hr in case of stuck
jobs.
Removes redundant agent declarations

oops, needed to add back the agents to each stage or it will try to run them all in parallel on the same node..


AssocArray API methods used to compare objects are sometimes not available

Issue: We parse some data,
rawData = "{items:[item1,item2,item3]}"
data = ParseJson(rawData)

data is an object, but it is now missing parts of its ifAssociativeArray interface – namely https://sdkdocs.roku.com/display/sdkdoc/ifAssociativeArray#ifAssociativeArray-Items()asObject.
This currently conflicts with BrsHamcrest coreDoMatch() which uses various AssocArray API to traverse the object being matched.
The only way to avoid this is to change our coreDoMatch() method to avoid using dangerously named API members.
So, to avoid clashes the following API members should not be used in this matching;

ifAssociativeArray:items
ifAssociativeArray:keys

We can't solve this with direct json comparison. Because we also want to be able to compare objects with properties that are not json compliant that stops us from just format as json and doing a string/hash comparison. So we need to traverse the object to compare its elements one at a time.
We are currently using items(). We could switch to using the api member keys() but this just swifts the problem sideways. Likewise finding a dat element has been named count would be a total blocker as well.
Therefore, I don't think that this is something that can be resolved. Our best option would be to detect the overwrite and throw a BrsHamcrest error when an overwrite is detected.

If the ifEnum API is not destroyed then we can still use FOR EACH to recreate, at least, the items() and count() methods that are needed for the matching task. Then we don't care if they have been overwritten. This might work. I'll investigate.


testproject-run 0.1.0

What to do if the build fails?
At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.
New Pull Request Checklist
Please mark the points which you did / accept.

[ x] I will not move an already shared step version's tag to another commit
[ x] I read the Step Development Guideline
[x ] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x ] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x ] I read and accept the Abandoned Step policy

New Step
Thank you for the new Step share! The CI check might will fail due to our extended validation engine. Nothing to worry about yet, we will get back to you shortly.

sorry I'm not too sure how long to wait to reach out to review this PR?
@godrei can you help?

@yj looking into this PR now, sorry about the wait!

thanks @shams-ahmed I'll close the pr, make the updates and recreate the pr as in:
https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/sharing-steps-with-all-bitrise-users.html#sharing-with-the-share-this-step-workflow