Bugs Debit notes

[x] while doing mark as sent option in kebab button  under pending approval status ,it status change to approved status

[x] remove save as draft button from rejected status

[x] add convert draft option under kebab button :  for rejected status & pending approval status

[x] remove apply credit option from kebab button : under sent status

[x] send debit note not functioning

[x] retainer available is not showing,debit note with the status sent

issue closed

issue closed


types/seat: Clear focus in wlr_seat_destroy()

This fixes use-after-free in surface destroy signal listeners.

I think this makes sense. We do something similar for unmap signals for xdg-shell, by guaranteeing that unmap is always triggered before destroy.

I think this makes sense. We do something similar for unmap signals for xdg-shell, by guaranteeing that unmap is always triggered before destroy.


⚠ Fortnite has degraded performance

In b40ee18, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1533 ms

Resolved: Fortnite performance has improved in 28d9216.


Compatibility Issue: NumPy 2.0+ Causes Errors in Triton Interpret Mode

Description:
Running Triton in interpret mode (TRITON_INTERPRET=1) with NumPy 2.0 or higher can lead to unexpected errors. Downgrading NumPy to a version below 2.0 (e.g., 1.21.x or 1.22.x) resolves these issues.
Steps to Fix:

Check your NumPy version:pip show numpy

If numpy >= 2.0, downgrade with:pip install numpy<2.0

I use numpy==2.1.2 and don't meet errors. It may be the version. It may also have something to do with the version of torch and triton.


syncplay tracebacks upon execution

Traceback (most recent call last):
  File "/home/mikaela/.local/bin/syncplay", line 14, in <module>
    from syncplay import ep_client
  File "/home/mikaela/src/github.com/syncplay/syncplay/syncplay/ep_client.py", line 3, in <module>
    from syncplay.clientManager import SyncplayClientManager
  File "/home/mikaela/src/github.com/syncplay/syncplay/syncplay/clientManager.py", line 2, in <module>
    from syncplay import ui
  File "/home/mikaela/src/github.com/syncplay/syncplay/syncplay/ui/__init__.py", line 9, in <module>
    from syncplay.ui.gui import MainWindow as GraphicalUI
  File "/home/mikaela/src/github.com/syncplay/syncplay/syncplay/ui/gui.py", line 127, in <module>
    class AboutDialog(QtWidgets.QDialog):
TypeError: 'Shiboken.ObjectType' object is not iterable

I am getting this on Debian GNU/Linux bullseye/sid and my friend on Ubuntu 19.10 is getting:
 % ./syncplayClient.py
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, webgl, xcb.

zsh: abort (core dumped)  ./syncplayClient.py

It seems that this is a bug on intersection between Python 3.8 and PySide. I also saw it on my Debian Testing system. As a workaround it's possible to either:

Use older Python 3.7
Upgrade to PySide 5.14 where the issue is fixed (it's in Debian Experimental branch).

In source of PySide 5.13.2 there is explicit lack of Python 3.8 as supported version.
Since this is all an upstream issue, I don't think Syncplay can do much about it. Except maybe providing a clear message about using incompatible versions of libraries. Still it's kinda weird how those two versions happily exist in Debian Testing and Sid repos. Do you want to submit a bug to Debian package team? I can do that if you aren't up to it.


Megacampaign not converting

In particular, the log gives the error
Could not open output/Wessex1836_01_01/history/countries/V18 - BroA<rec.txt

Uploads can be found on this forum post: https://forum.paradoxplaza.com/forum/index.php?threads/vic2-to-hoi4-converter-release-thread.948992/page-27#post-23413273

It's a codificafion problem. The country file is named Broërec and the converter f**ks up any diacritic.

Actually, it looks like it was the less than symbol in the name. Fortunately, commit f5f3151fda94874bb4606dfb8b2b484c234efb3c fixed this for issue #376, and that fix worked here.


Common label for hosted CE

Surprisingly, there's common label for the hosted CE; this makes it impossible to query a namespace for all CE-related pods.
How about we add:
app.kubernetes.io/part-of: osg-hosted-ce

?  From https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/, alternate candidates would be:

app.kubernetes.io/component
app.kubernetes.io/name

@fengpinghu has pushed these changes live in Chart version 4.4.1.


URL Validator does not allow pipes

Laravel Version: 7.x
PHP Version: 7.4.5
Database Driver & Version: MySQL 5.7 (irrelevant)

Description:
For some reason in Laravel 7.x the 'url' validator does not allow pipes (|) while Laravel 6.x does.
Steps To Reproduce:
Using Laravel 7.x run the following code:
$url = "https://laravel.com?foo=one|two";
$validator = Validator::make(
    [
    	'url' => $url
    ],
    [
        'url' => 'url'
    ]
);
$validator->errors()->toArray();

I also came across this error when I try to validate an urlencoded url with the same pipe:
%7C = |
URL
https://laravel.com/somefile%7Cothername.mp4

Validation error in json
{
    "message": "The given data was invalid.",
    "errors": {
        "url": [
            "The url format is invalid."
        ]
    }
}

It looks like the URL validation code was changed in pull request #32315 . I'm not any good with regex, but the answer may lie in there.

@rbarden Yep, saw that while I was backtracking the change. Since this comes from Symfony it might be more than just us changing the regex. I mean I can submit a PR to add the pipe to the regex, I just want to see if the team here will accept it.

You should submit the PR and they'll either accept or reject it. Make sure to give context.

@rbarden I rather wait to get confirmation if they'll accept a PR for this change first since in the past (#17908, #379, #380) I've spent the time creating the PR's and they were closed.

We usually just port this regular expression from Symfony. I would see if ours matches theirs. If it does, you may want to submit a PR to them to fix it on their end and then we can port it over.


fix: Correct typos and formatting

Corrected four misspelled instances of the word "formated" to "formatted" in the documentation.
Added a space after each period to ensure writing standards and readability.

Thank you ! Can you also update the corresponding Python string that generated the typo to make it consistent ?

How about this? https://github.com/mistralai/mistral-finetune/pull/39

Thanks! Can you combine the two PRs? I think the space is also still missing in the Python fix.

will do


Disallow more flavors of property accesses on never in expression space

fixes https://github.com/microsoft/TypeScript/issues/42999
fixes https://github.com/microsoft/TypeScript/issues/56778

@typescript-bot run DT
@typescript-bot user test this
@typescript-bot test top100
@typescript-bot perf test this

@typescript-bot pack this

@typescript-bot run DT
@typescript-bot user test this
@typescript-bot test top100
@typescript-bot perf test this

@gabritto Here are the results of running the top-repos suite comparing main and refs/pull/56780/merge:
Something interesting changed - please have a look.
Details
ant-design/ant-design
backstage/backstage
microsoft/vscode
tldraw/tldraw

Of the new errors on the top repos test, most seem to be because of "defensive programming", where there is an exhaustive check on some variable followed by a branch for when it has an unexpected type. In this defensive branch, the variable has type never, so an element access produces an error.
Those seem to be actual errors:
https://github.com/ant-design/ant-design/blob/4704eb578b8e7caabc502a5204c2ba058ee8266c/components/tree/utils/dictUtil.ts#L22
https://github.com/ant-design/ant-design/blob/4704eb578b8e7caabc502a5204c2ba058ee8266c/components/tree/utils/dictUtil.ts#L22

We discussed this at design meeting today, and the conclusion was that this change is not worth the breaks it causes. As evidenced by the extended tests, most new errors are not really desirable and come from an intentional usage of never, i.e. something has type never in code that is not supposed to be reachable.
There was one error that seemed like a bug, as I pointed out above, where the code looks like function foo(x: A & B) { ... x[key] ... }, and A & B reduces to never.
So it seems like most times, people are using never intentionally and TS shouldn't error, but other times it should, and it's not immediately clear how to tell the difference.

We discussed this at design meeting today, and the conclusion was that this change is not worth the breaks it causes. As evidenced by the extended tests, most new errors are not really desirable and come from an intentional usage of never, i.e. something has type never in code that is not supposed to be reachable.
There was one error that seemed like a bug, as I pointed out above, where the code looks like function foo(x: A & B) { ... x[key] ... }, and A & B reduces to never.
So it seems like most times, people are using never intentionally and TS shouldn't error, but other times it should, and it's not immediately clear how to tell the difference.

I unfortunately missed the meeting, but I find it a little weird that we're saying that it's okay to access any prop on never; if that were the case, then Foo | never should not reduce because a component of the union "has all props", but that's not what never does... It's the empty set of types, with which you can do nothing.
I personally feel like all of the errors this PR showed are real and that never is a type that's okay to have around, and that if you want to touch something that's never you need to cast it to something else to probe at it.

It's the empty set of types, with which you can do nothing.

Since we know never is the empty set of values, once you know you have a value v of type never, you've reached a contradiction. And, by the principle of "from contradiction, anything follows", you can access anything on that value because anything is true about it, including statements like "v has property blah".
If we had a sound type system, at run time we'd never reach that portion of code where v has type never, so it would not matter if you tried to access a property on it.

I unfortunately missed the meeting, but I find it a little weird that we're saying that it's okay to access any prop on never; if that were the case, then Foo | never should not reduce because a component of the union "has all props", but that's not what never does...

Foo | never reduces to Foo because you know whatever value has that type, it can't have type never.
But let's say we didn't reduce it and you have a value v of type Foo | never. v either has type never, in which case you can access any property on v, or it has type Foo, in which case you can only access Foo properties on v. In both of those cases, you can access the Foo properties on v. This is consistent with saying v has type Foo.

Foo | never reduces to Foo because you know whatever value has that type, it can't have type never.
But let's say we didn't reduce it and you have a value v of type Foo | never. v either has type never, in which case you can access any property on v, or it has type Foo, in which case you can only access Foo properties on v. In both of those cases, you can access the Foo properties on v. This is consistent with saying v has type Foo.

Ah, that is true; I had it flipped in my mind; obviously if you have a union of two types, you can only access what they have in common.

I'm OK with the judgment itself but this inconsistency is killing me:
declare const foo: never

foo.prop // error ?????
foo["prop"] // ok
const { prop } = foo // ok

It feels just wildly inconsistent and hard to explain to people. How this difference in behavior would be explained in the docs?
I didn't yet have the time to review carefully everything reported by the extended test suite but I'd definitely call most of those failures improvements. I feel like the only use case that was said to be valid here is the defensive programming case.
And to quote @jakebailey:

if you want to touch something that's never you need to cast it to something else to probe at it.

It would at least give some visual indicator that something funky is going on there. Those would also often appear in the codepaths that would be clearly associated with such defensive programming fallbacks (close to thrown error messages, console.warns etc). I feel like in those contexts people wouldn't mind at all the cast.
On the other hand, I'm quite worried - as the user - that never might accidentally sneak past me like this and I won't notice it at all. For instance, I doubt that this intentionally relies on never this way.
This isn't exactly a new risk though. never is assignable to everything so it's fairly easy (in the same way) to accidentally pass it to a function as an argument. That leads me to be OK with the final judgment. That inconsistency though... if this is the final judgment, shouldn't foo.prop be relaxed to allow this access on never?

I'm OK with the judgment itself but this inconsistency is killing me:
declare const foo: never

foo.prop // error ?????
foo["prop"] // ok
const { prop } = foo // ok

It feels just wildly inconsistent and hard to explain to people. How this difference in behavior would be explained in the docs?

I'm not even sure we did that on purpose, I'll have to investigate.

I feel like in those contexts people wouldn't mind at all the cast.

I'm open to believing that, given evidence, but it could still be a burden to make this update if it's needed in too many places.

On the other hand, I'm quite worried - as the user - that never might accidentally sneak past me like this and I won't notice it at all. For instance, I doubt that this intentionally relies on never this way.

Yeah, that was a genuine error, as I pointed out above.

This isn't exactly a new risk though. never is assignable to everything so it's fairly easy (in the same way) to accidentally pass it to a function as an argument. That leads me to be OK with the final judgment. That inconsistency though... if this is the final judgment, shouldn't foo.prop be relaxed to allow this access on never?

I'm having this thought that never is kind of like an any in the sense that you can do almost anything with it, so I agree that it's risky.
I think this isn't necessarily a "final judgement" in that we'll never ever do it, but we aren't currently convinced this is worth the break.


[FEATURE] : Sidebar dropdown

Description
Provide some padding in dropdown child elements and also remove border from child element.
Screenshots

Additional information
No response
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
Yes I am willing to submit a PR!

I would like to work on this!

@rahulpandey70 good spot, we won't be removing the border as it's to indicate the tool you currently clicked which is a good UX, but you can do the padding.
will assign it to you. Make sure you follow the rules 👉🏽here👈🏽, else your PR will not be accepted and will be closed. Good Luck

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


Enable ExCoveralls with parallel builds

Description
This PR enables ExCoveralls with parallel builds.
With this approach, the 2 builds produced by the matrix strategy between the OTP and Elixir versions are created in parallel, and at the end, they are merged and published to Coveralls.
More info: https://docs.coveralls.io/parallel-build-webhook
The build number is slightly different between pull requests and pushes. See below:
https://github.com/parroty/excoveralls/blob/d1b6b35cee693e0bc461da00c969a79a23276baa/lib/excoveralls/github.ex#L37-L48

Pull Request Test Coverage Report for Build 202da5cb7130dfe3cabe2a8880b98f55ca566904-PR-62

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 8913e91ced37a8df3112a33feaddf36f7690cf4c:
0.0%

Covered Lines:
302

Relevant Lines:
302

💛  - Coveralls

Pull Request Test Coverage Report for Build 202da5cb7130dfe3cabe2a8880b98f55ca566904-PR-62

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 8913e91ced37a8df3112a33feaddf36f7690cf4c:
0.0%

Covered Lines:
302

Relevant Lines:
302

💛  - Coveralls


robot-name: change test structure for bonus fix

Bonus test fails on proposed test command - go test -tags bonus
It's happens because we are taking all available robot names in bonus test, so base test fails
I have changed test structure - moved common parts to separate file and added exclusion build tag to base tests, so running the command go test -tags bonus executes only bonus test.

when is this expected to be merged ?

@h311ion , @hans-d, Sorry for the delay before merge. I had waited for a second approval.


Update README.md

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/test padu

/ok-to-test

/test padu

/test padu

/retest padu

/test

/test


Support phabricator urls with https

This PR will add support for Phabricator URLs of the form "phabricator.example.com" as before but also "http://phabricator.example.com" and "https://phabricator.example.com". My current phabricator setup was not responding to api/harbormaster.sendmessage calls as it was just returning 301s, redirecting the http calls to https. Let me know if you'd like me to do this in a different way. Also sorry for some of the whitespace changes, my IDE automatically made those changes, let me know if you'd like me to revert.
Also, I haven't been able to test this because I don't exactly know how to build the teamcity plugin zip from source. Could you add instructions maybe? Happy to test in depth after I figure that out.

And I know the URI parsing is a bit repetitive here but I wasn't sure where a convenient place for a util class would be. Let me know if you want me to create a common location for some shared code or if you're alright leaving this as is.

Ah I see, building is as simple as running mvn package. I tested this on my TeamCity / Phabricator instances and it worked as expected with an https Phabricator url

cc @halojedi20

Oh, legit. I'll pull it down and give it a run this weekend.

Any luck @halojedi20? I think I'll have another PR incoming for doing something similar on the harbormaster side, i.e. support a TeamCity server behind https.

I got the travis yml integrated but for some reason the build was failing, something to do with the travis configuration but I haven't had time to look into it. Just pulled your pr down though and looks good! Thanks for contributing!


[Browser project monitors] No option for disabling monitor alerting

In 8.7.0, we are introducing alerting, with a toggle that allows you to turn alerting on and off for a particular monitor.
However, there is no way to overwrite alerting for browser project monitors.
We should update the types for the monitor configuration, found here, so that alerts can be added to monitor.use without type errors.
The schema is as follows
{
   status: {
      enabled: boolean
   }
}

A TLS option likely coming later.
I believe we may need a change on the Kibana side as well to support disabling alerting for browser project monitors. Further investigation is needed.

Linking https://github.com/elastic/synthetics/pull/713

closed via https://github.com/elastic/synthetics/pull/713

Post FF testing good


Add offset and max_offset metrics

Are you interested in this pull request? In addition to lag, our burrow is giving us additional metrics that we'd like to report on:

last committed offset of the consumer group (i.e. offset or current-offset)
last offset of the partition, not necessarily read by the consumer group (i.e. max-offset or log-end-offset)

These can be useful when combined with Prometheus' rate function, to see the rate of new message creation as well as the rate that messages are being processed.

Thanks!


Issue #119 fixed

Issue
https://github.com/subeshb1/developer-community-stats/issues/119
Description
Added Tech stack icons with respective links
Checklist

[*] Added contributor object in ascending order in contributors.json
[x] Github action build passing
[*] No merge conflicts

HI @b2pacific Great job and I really appreciate it. Can you also upload the screenshot of the changes?

I am having an issue while running it on my local machine I am getting some error with graphql.
Here's the error.
There was an error in your GraphQL query:
Cannot query field "allContributor" on type "Query".
If you don't expect "allContributor" to exist on the type "Query" it is most likely a typo.

@b2pacific Can you try running it by
ENV_TYPE=mock gatsby develop

Great!


Knex doesn't parse JSON values in connectionURIs causing incompatibility with mysql / node-mysql2

Environment
Knex version: 0.95.9, 0.21.21
Database + version: MariaDB 10.3, mysql package 2.18.1 but also affects node-mysql2
OS: MacOS Monterey
Bug
1. Explain what kind of behaviour you are getting and how you think it should do
I am trying to pass in a connectionURI that contains JSON in the searchParams.
mariadb://foo:bar@foobar.com/foo?ssl={\"ca\": \"--- BEGIN CERTIFICATE --- ...\"}

This might seem funky at first, but it is actually supported by both mysql and node-mysql2
Here's the node-mysql2 implementation:
https://github.com/sidorares/node-mysql2/blob/d74558b605162156b813248a024f7559785de6fb/lib/connection_config.js#L234-L254
and here's the mysql one:
https://github.com/mysqljs/mysql/blob/3430c513d6b0ca279fb7c79b210c9301e9315658/lib/ConnectionConfig.js#L179-L209
As you can see, the parser first tries to parse the search/query parameters with JSON.parse and then fallbacks on just adding the value as string.
knexs parser, however, just assigns them as strings:
https://github.com/knex/knex/blob/1744c8c2655a8362260ba987d706ec3473681a78/lib/knex-builder/internal/parse-connection.js#L70-L73
2. Error message
The SSL configuration always gets parsed as a string, resulting (for example in mysql) in the following:
TypeError: Unknown SSL profile '{"ca":"-----BEGIN CERTIFICATE-----

3. Reduced test code, for example in https://npm.runkit.com/knex or if it needs real
database connection to MySQL or PostgreSQL, then single file example which initializes
needed data and demonstrates the problem.
Codesandbox:
https://codesandbox.io/s/dazzling-burnell-7gsyj?file=/src/index.js:0-197
const knex = require("knex")({
  client: "mysql",
  connection:
    'mariadb://foo:bar@foobar.com/foo?ssl={"ca": "--- BEGIN CERTIFICATE --- ..."}'
});

console.log(knex.client.connectionSettings);

Result:
{
  database: 'foo',
  host: 'foobar.com',
  user: 'foo',
  password: 'bar',
  ssl: '{"ca": "--- BEGIN CERTIFICATE --- ..."}'
}

Expected:
{
  database: 'foo',
  host: 'foobar.com',
  user: 'foo',
  password: 'bar',
  ssl: : {
    ca: "--- BEGIN CERTIFICATE --- ..."
  }
}

Would you be open to send a PR for this?

Hi @kibertoad!
Sent a PR in https://github.com/knex/knex/pull/4629 (first time using GitHub Codespaces to do it 😸 , hopefully it works & tests pass, if not I'll do the changes later locally :))

Released in 0.95.11


issue uploading results to CodeCov

There is an issue uploading test results to codecov. If you take a look at https://github.com/buildtesters/buildtest/runs/6631262688?check_suite_focus=true you will see the following message
Run<EMAIL_ADDRESS>==> macos OS detected
https://uploader.codecov.io/latest/macos/codecov.SHA2[5](https://github.com/buildtesters/buildtest/runs/6631262688?check_suite_focus=true#step:7:6)[6](https://github.com/buildtesters/buildtest/runs/6631262688?check_suite_focus=true#step:7:7)SUM
==> SHASUM file signed by key id 806bb28aed[7](https://github.com/buildtesters/buildtest/runs/6631262688?check_suite_focus=true#step:7:8)79[8](https://github.com/buildtesters/buildtest/runs/6631262688?check_suite_focus=true#step:7:9)69
==> Uploader SHASUM verified (8d3709d957c7115610e764621569728be102d213fee15bc1d1aa9d465eb2c258  codecov)
==> Running version latest
==> Running version v0.2.3
/Users/runner/work/_actions/codecov/codecov-action/v3.1.0/dist/codecov -n  -Q github-action-3.1.0 -C 6[9](https://github.com/buildtesters/buildtest/runs/6631262688?check_suite_focus=true#step:7:10)8d95d6cc37213f9bdd6189606c378071ca885a
[2022-05-27T20:09:16.962Z] ['info']
     _____          _
    / ____|        | |
   | |     ___   __| | ___  ___ _____   __
   | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
   | |___| (_) | (_| |  __/ (_| (_) \ V /
    \_____\___/ \__,_|\___|\___\___/ \_/

  Codecov report uploader 0.2.3
[2022-05-27T20:09:[16](https://github.com/buildtesters/buildtest/runs/6631262688?check_suite_focus=true#step:7:17).977Z] ['info'] => Project root located at: /Users/runner/work/buildtest/buildtest
[2022-05-27T20:09:16.983Z] ['info'] -> No token specified or token is empty
[2022-05-27T20:09:[17](https://github.com/buildtesters/buildtest/runs/6631262688?check_suite_focus=true#step:7:18).[20](https://github.com/buildtesters/buildtest/runs/6631262688?check_suite_focus=true#step:7:21)0Z] ['info'] Searching for coverage files...
[20[22](https://github.com/buildtesters/buildtest/runs/6631262688?check_suite_focus=true#step:7:23)-05-27T20:09:17.[24](https://github.com/buildtesters/buildtest/runs/6631262688?check_suite_focus=true#step:7:25)7Z] ['info'] Warning: Some files located via search were excluded from upload.
[2022-05-27T20:09:17.247Z] ['info'] If Codecov did not locate your files, please review https://docs.codecov.com/docs/supported-report-formats
[2022-05-27T20:09:17.247Z] ['error'] There was an error running the uploader: No coverage files located, please try use `-f`, or change the project root with `-R`

This github action is coming from https://github.com/codecov/codecov-action and is used in https://github.com/buildtesters/buildtest/blob/devel/.github/workflows/regression.yml
Possibly bring this up with developer by reporting an issue at https://github.com/codecov/codecov-action/issues or try a new version (https://github.com/codecov/codecov-action/releases). Currently we are using 3.1.0 which is the latest release as of now. Not sure if downgrading to 3.0.0 will work.

https://github.com/codecov/codecov-action/issues/677


M4b support?

Hey @mas0nwest! Can you elaborate a bit? Does it not work at all? What platform are you using? Thanks!


[feature] Add Twitter redirect endpoint

Purpose:
Allow individuals to get automatically redirected to a user's Twitter account if one is associated with the respective user.
Changes:

Add a new endpoint /@<uid>/ that will automatically redirect to the Twitter account associated with uid if the account is active and has a Twitter handle associated with it.
If either of these conditionals is not met, the user is prompted with a concise error message.

Side Effects:
A new route was added with a respective view.

After that minor change, this is good  to merge.


CLI router device all does not return the full list of devices

The following command
docker exec -it helium_router _build/default/rel/router/bin/router device all

returns
+-------+------------------------------------+-----------------+----+--------+------------+---------+
|running|                 id                 |      name       |fcnt|fcntdown|queue_length|is_active|
+-------+------------------------------------+-----------------+----+--------+------------+---------+
| true  |49dc48da-xx-453xxxxe45e64a7|Atomic xxx t| 0  |   0    |     0      |  true   |
+-------+------------------------------------+-----------------+----+--------+------------+---------+
```

Instead of the list of devices registered in the router (there are more than one registered)

Would it be also possible to have in the details the organization id is belongs to ?

@disk91 can you confirm this is still an issue, if not will close

currently I still see a list limited to 2 devices. this is not including the device I own, so I'm sure there is mire than this.
root@helium-iot:/helium/run/router/log# docker exec -it helium_router router device all
+-------+------------------------------------+-----------------+----+--------+------------+---------+
|running|                 id                 |      name       |fcnt|fcntdown|queue_length|is_active|
+-------+------------------------------------+-----------------+----+--------+------------+---------+
| false |49dc4| xxx | 0  |   0    |     0      |  true   |
| false |2b5bbf|     xxx     | 0  |   0    |     0      |  true   |
+-------+------------------------------------+-----------------+----+--------+------------+---------+

But
docker exec -it helium_postgres psql xxx  xxxx  --command="select id from devices;"
                  id
--------------------------------------
 5525d412-7df1-4b03-b3e9-c15eb3293ae7
 5bdb507a-7141-4341-ad98-9fa5a7b993cf
 a53e0dcc-f8bc-4c2a-8a00-e7b26f31cad0
 e75d6281-ff38-417e-a3fb-39640cd42118
 3e5e5b6a-b747-4fc1-ab4a-d1a720ca67fc
 661b038e-e0ba-4a3b-81fd-4c16f05969cf
 b1438a0c-1e24-4bcc-aab5-a5de868e085c
 0e425b11-850c-474a-8fb3-2fba52b6f168
 ef31b0bc-bc82-42e5-8b4a-178d5e66b9e6
 e20c8af9-6f49-4016-be78-2dd1b936188d
 d26749c6-e7b7-4f15-9664-02ebb76bd1e5
 49dc48da-8ba9-453c-8459-0f1de45e64a7
 2b5bbf89-9e46-4591-9a19-4a7c4cec6b7a
 549ac1cf-cc37-43f3-8c5b-72e519bb38d5
 c563e843-dc17-4fc2-9268-33aa4593b3b0
 427641be-11e8-4907-b30a-42427cbf714e
(16 rows)

I can confirm that we are only getting devices that are in Router, I will update to include all devices also including Console.


Python plugin adds same import multiple times to generated outputs

@nathanielmanistaatgoogle I am filing this based on our discussion yesterday.
You said you'd point me to the place in the code to fix.
I found
https://github.com/grpc/grpc/blob/master/src/compiler/python_plugin.cc
but it doesn't seem to be the right place :grin:

Indeed I did say that, and you're close to the right place. Look at the sibling file python_generator.cc and in particular lines 299-303 and 383-387.

For posterity:
https://github.com/grpc/grpc/blob/c876923bc2a3d9c6bbc03f275a7fe68333b95600/src/compiler/python_generator.cc#L299-L303
https://github.com/grpc/grpc/blob/c876923bc2a3d9c6bbc03f275a7fe68333b95600/src/compiler/python_generator.cc#L383-L387

I don't think I'll ever have the throughput to deal with this. Though I'd suggest using https://docs.python.org/2/library/ast.html instead of trying to deal with the syntax tree in C++.

Maybe. A reasonable short-term action would be to just de-duplicate inside the code generator's C++ for loops. The right long-term solution might be to gather all the required imports, filter out the ones that are of the generated module itself, and then have all the other ones at the top of the generated module. Perhaps sometime in the next few months...

Indeed, perhaps in the next few months...

I now expect this to be obviated by #3867.

OK good

Addressed in #6479


Hi Paul, problem autoplay using iframe tag

Hi Paul, thanks for the great app I can use by your great work.
There is a small matter I walked into , which is indirectly related to the player.html app,
I think. I will shortly describe the situation, maybe you could give a direction on it.
I use the player.html app in combination with a html page.
In the html code I sue a iframe to show a video on the page, where a video is forwarded
by a src tag. I could give you the complete code, but it is probably not necessary for you to know what happens.
The whole thing works good. too good.
I use 2 iframes on my site playing video's that are listed in your videoapp player.html
The problem is on site load, they start playing at once all together, which gives a chaos for the user experience.
A third iframe fowarded to another external source on vk.com, just waits till the user presses play.
Before you ask, yes, I know video forwarding by iframe is old coding, we should use HTML5 and
the  'video'  tag  now.
For the user group however, it i needed to play on all older webrowsers as well.
I don't want people be depended on HTML5 if they live in other parts of the world.
Backwards compatibility.
My question;
since the issue only occurs on iframes that are forwarded to local video's on a path where the player.html
is in use, it could be something in the configuration of player.html
Is there an option to switch off autoplay in player.html?
ps,  I tried to link with a javascript function as well, for example like this:   window.location.assign("video-api-link-player.html")
Same problem it start autoplaying.
Sorry if my perception and attempts are poor.  I am sure I am trying something unusual here.
However, any help is welcome. Thanks in advance.
Dirk.
update:
Paul, in the iframes I mentioned, I use as video source in the src tag, a link which I copied in the browser,
while playing the video by your html script. When a video plays in your script a long line of api like code is displayed in
the url. It is this I use as video source in the iframe. Would it be possible to change something in that link to prevent autoplay?

Hi @leeuwtjex, I'm not sure I'm clear on the exact issue. Are you saying you want it to not autoplay the videos in the iframes? I don't know how you create your iframe embed link but you should be able to do this. The data after the # in the URL is all base64 encode JSON with the playback information. You should be able to create and set those values, base64 encode them, and use that to start playback.
This URL includes this JSON.
URL
https://player-html-remix.glitch.me/src/player.html#eyJsb2NhdGlvbiI6Imh0dHBzOi8vcGxheWVyLWh0bWwtcmVtaXguZ2xpdGNoLm1lL3ZpZGVvcy8iLCJ2aWRlbyI6Imh0dHBzOi8vcGxheWVyLWh0bWwtcmVtaXguZ2xpdGNoLm1lL3ZpZGVvcy9UaGUlMjBMb3MlMjBBbmdlbGVzJTIwTGFrZXJzJTIwLSUyMFNhbWUlMjBhcmVuYS4lMjBTYW1lJTIwYmFza2V0LiUyMFNhbWUlMjBkdW5rLiUyMDE5JTIweWVhcnMlMjBhcGFydC4lMjAlRjAlOUYlOTIlOUMlRjAlOUYlOTIlOUItMTIyNTkzOTM4NTUxNTgyMzEwNC5tcDQiLCJ0aW1lIjo3Ljk0MTE1NH0%3D
JSON
{
  "location": "https://player-html-remix.glitch.me/videos/",
  "video": "https://player-html-remix.glitch.me/videos/The%20Los%20Angeles%20Lakers%20-%20Same%20arena.%20Same%20basket.%20Same%20dunk.%2019%20years%20apart.%20%F0%9F%92%9C%F0%9F%92%9B-1225939385515823104.mp4",
  "time": 7.212118
}

location sets what folder it should start in
video is the URL for what video to play
time is where you want it to start playing.
It does not autoplay by default when loaded this way on my machine.

Hi Paul, I wish you all health and hapiness for you in the new year, and I hoped you had a warm christmas.
Thanks for replying this post. Yes, I remember there was an issue around april last year, however I solved it with a workaround. As far as i remember just a iframe css thing. In the end it worked fine with your player.
Now you mention it, do  have another issue now, which is directly connected to your videoplayer application I believe.
On a site, I use many video's in different directories. Problem is the more video's are added in the directory, the slower the identification process gets. player.html likes to sample all video's before displaying them to the user.
This takes time. For 3 video's it is not a disturbing delay. But for 8+ video's, it takes much time where the viewer just see dark frames with a spinning wheel and click away. First I thought it was an CPU issue on the server, but it is not.
Is there a way to makes this procedure less complex in the script and for example just take 2 or 3 shots without analysing the cpmplete duration of the video? I think the issue is connected to the lenght of the video. The longer the playing time, the longer player.html takes to generate the demo.
Is there a parameter somewhere to limit that process?
Thanks.
Dirk.

Yes, the thumbnail generation can slow things down if you aren't on a very fast connection between your browser and the server.
There are a few ways to handle this:

Disable thumbnail generation: click the setting gear on the right, and toggle "Generate Thumbnails" to "off".

The thumbnails can be pre-rendered on the web server for the videos: https://github.com/pseudosavant/player.html?tab=readme-ov-file#pre-rendered-server-side-thumbnails
Change the thumbnail configuration in your copy of player.html to generate fewer thumbnails by setting thumbnails.timestamps to only have one timestamp value in the array. You can also set the thumbnail to be earlier in the video so that it doesn't have to seek as far into the video for the frame. Setting the array to an empty [] array will completely disable thumbnailing too.: https://github.com/pseudosavant/player.html/blob/2fa71be295eaef6218e207c8bfa9bb50455e28fa/src/player.html#L1145


awkward1.from_iter doesn't handle complex arrays

Probably low priority, as awkward1.from_numpy does.
>>> import awkward1 as ak
>>> import numpy as np

>>> ak.from_iter([0j])

~/venv/awkward/lib/python3.6/site-packages/awkward1/operations/convert.py in from_iter(iterable, highlevel, behavior, allow_record, initial, resize)
    359     out = awkward1.layout.ArrayBuilder(initial=initial, resize=resize)
    360     for x in iterable:
--> 361         out.fromiter(x)
    362     layout = out.snapshot()
    363     if highlevel:

ValueError: cannot convert 0j (type complex) to an array element

>>> ak.from_numpy(np.asarray([0j]))
 <Array [0j] type='1 * complex128'>

The unhandled dtypes are

float16: need to find a C++ library for it
float128: same problem
complex64, complex128: C++'s built-in std::complex can do this; it's just a matter of filling it in everywhere
complex256: complex and non-standard floating-point type
datetime64, timedelta64: these require a little more work than the above, since we need to work around the buffer protocol, which doesn't recognize these, and they also have special rules in reducers (can't add datetimes to each other, but can add timedeltas; multiplication doesn't make sense for either). Nevertheless, this is a somewhat higher priority, since dates and times are ubiquitous in Pandas data.
fixed-width bytestring and string types: variable-length string objects are more common in Pandas data, and they're handled as non-primitive lists with parameter["__array__"] == "bytestring" or "string". The fixed-width bytestrings would come up if someone were analyzing 6-byte MAC addresses or something.

Other than these dtypes, NumPy arrays can contain Python objects (which we won't ever do), record stuctures, which we convert to Awkward records, masked-out data, which we convert to option-type, and non-trivial shapes, which we convert to regular-length lists.
 But if there's ever a strong need for them, they can be added by following the pattern set by the other types (i.e. search for all "float32" and add cases for the complex numbers). It might even be a "good first issue."


install: gce: show should be describe for image inspection

s/show/describe
Fixes: #197
Signed-off-by: Eric Ernst<EMAIL_ADDRESS>

heads up @jon

Thanks -- this was a simple miss on my part. This change LGTM.


Support remote operation via proxy Lambda

To support remote operation via a Lambda proxy:
This will permit migrations for very large databases or complex migrations where I/O transfer is prohibitive to and from an on-prem CLI.
Basic Design

Add Proxy class to relay methods via direct Lambda invoke
Set this.migration to Proxy instance or local OneTable Migrate instance
Update OneTable migrate to ~0.6
Add arn property to migrate.json to specify the lambda
Update doc
New tests

Suggest bumping to 0.6 to align with OneTable.

Added in 0.6.0


nav-title-slide-ios7 doesn’t works with align-title=“left”

I have an animation issue when I use nav-title-slide-ios7 class with align-tittle="left". When is center aligned it works ok, but when is left aligned it flashes when making the animation.
http://codepen.io/asdasd3333/pen/Ixgpn
<ion-nav-bar class="nav-title-slide-ios7 bar-positive" align-title="left">
  <ion-nav-back-button class="button-icon ion-arrow-left-c">
  </ion-nav-back-button>
</ion-nav-bar>

Greetings, @marianico2!
My sensors indicate that this issue has been inactive for a while.
Due to this, the issue will be closed in 7 days.
If you believe the issue has not been fixed, please add a comment.
This will notify us so we can assist you, and will prevent the issue from being automatically closed.
Feel free to include the following information about the issue, so that we may assist you:

Can you provide a detailed description of this issue?
How would a robot go about replicating this issue?
What platform does this happen on? (iOS, Android, all, etc.)
What platform versions does this happen on? (Android 4.2, iOS 7, all, etc.)
Is this an issue with the Ionic Framework, or Ionic CLI?

Thank you for allowing me to assist you.

Greetings @marianico2!
I'm sorry, but my sensors indicate that this issue may no longer apply to recent versions of Ionic.
If you are still experiencing this issue, please feel free to reopen it and provide the following information, so that I may assist you:

Can you provide a detailed description of this issue?
How would a robot go about replicating this issue?
On which platform does this occur? (iOS, Android, all, etc.)
On which platform versions does this occur? (Android 4.2, iOS 7, all, etc.)
Is this an issue with the Ionic Framework or Ionic CLI?

Additionally, providing a codepen that replicates the issue is extremely helpful.
If you wish to get help using the framework itself, I recommended visiting the forum. There are many humans there who can offer sage advice.
Thank you for allowing me to assist you.


run

now，i finished the step of 'make',what should i do next?  please ?

now，i finished the step of 'make',what should i do next? please ?

I also want to know the next step. Could the author please share the complete guideline? Thanks.

Did you have to install any additional dependencies for the ./install step to be successful?


mpi notebook and ipyparallel race conditions

this applies to examples/mpi/overview.ipynb and possibly to any ipyparallel-based notebook tested via nbval
random failures seem to be happening due to this issue in ipyparallel
we're not totally sure this is the actual issue, but it's more than a weak conjecture
currently worked around by adding NBVAL_IGNORE to all non-output cells. This seems to make CI happy for now...

horrible, but we might consider using flaky ... better than nothing?
integration with NBVAL is still missing though


Unzip a tarball to a temporary directory

Relevant crates: temdir, tar, flate2

i'll give it a try

Added in #124.


Add Qwen2-audio example

Description

1. Why the change?

2. User API changes

3. Summary of the change

4. How to test?

[ ] N/A
[ ] Unit test: Please manually trigger the PR Validation here by inputting the PR number (e.g., 1234). And paste your action link here once it has been successfully finished.
[ ] Application test
[ ] Document test
[ ] ...

5. New dependencies

[ ] New Python dependencies
- Dependency1
- Dependency2
- ...
[ ] New Java/Scala dependencies and their license
- Dependency1 and license1
- Dependency2 and license2
- ...

Please add link to https://github.com/intel-analytics/ipex-llm?tab=readme-ov-file#verified-models.


Command-R returngs gibberish since update to 0.1.32, logs: ggml_metal_graph_compute: command buffer 6 failed with status 5

What is the issue?
Since the update, Command-R is no longer producing text, but other models (e.g. openchat) do. Running Command-R from the terminal
$ ollama run command-r
>>> Hey, how are you?
3O>FCMID7BBBM<=>PJT@@FNURWKL=8@N;GWHP6:GJ>F76N86EL5DKLFJFADJ;ESQAV7OBDJTK8HT@Q>Q8@BCJ:I9NJEW=?C>BHIJ3U@87L^C

Looking at the .ollama/logs/server.log logs I seen many lines of
ggml_metal_graph_compute: command buffer 6 failed with status 5
What did you expect to see?
Any kind of English Text Answer.
Steps to reproduce
Start Ollama on the console
ollama run command-r
Ask any question.
Are there any recent changes that introduced the issue?
Upgrading from Ollama 0.1.31 to 0.1.32.
OS
macOS
Architecture
arm64
Platform
No response
Ollama version
0.1.32
GPU
Apple
GPU info
No response
CPU
Apple
Other software
No response

Hi there, sorry about this. May I ask how much memory this Apple Silicon Mac has?

@jmorganca I can recreate this problem in my Apple M1 Pro with 32GB

@jmorganca here are debug logs - https://pastebin.com/raw/GiC2mFPz

Sorry for not including all specs.
It is an Apple M1 Pro, 32GB Ram, German macos Sonoma 14.4.1
The Commad-R Model used to run fine with the privous 0.1.31 Version of Ollama.

thanks @AndreRatzenberger I can confirm that /set parameter num_gpu 0 works for me.

how can this workaround be applied when running ollama serve or perhaps when calling ollama run command-r "prompt text etc.."?
Reading some of the docs here, one idea that came to mind was to create a custom model with a Modelfile, e.g.
FROM command-r
PARAMETER num_gpu 0

and run that model. I'm not sure if my intuition is right - would this config be merged with / overwrite the existing Modelfile or would it blow away other things already set like SYSTEM or TEMPLATE?

I can also confirm that setting GPU number is also working, but I have some doubts about its token/s results.

I believe this is fixed in the latest Ollama version.  If you're still having problems with the latest version, let me know and I'll re-open the issue:
> ollama run command-r --verbose why is the sky blue
The sky appears blue because molecules in the air scatter blue light from the sun more than other colors. This
...

total duration:       29.6602217s
load duration:        16.2283007s
prompt eval count:    11 token(s)
prompt eval duration: 142.614ms
prompt eval rate:     77.13 tokens/s
eval count:           182 token(s)
eval duration:        13.284409s
eval rate:            13.70 tokens/s
> ollama ps
NAME                    ID              SIZE    PROCESSOR       UNTIL
command-r:latest        b8cdfff0263c    24 GB   2%/98% CPU/GPU  4 minutes from now

I want to reopen this (although it may be better as a new issue, as the version is greatly different.)
However I am seeing similar behaviour.
Macbook Pro, Apple M1 Max, 32Gb. Ollama 0.3.13.
Newly pulling Command-R:Latest (18GB model) produces:
ollama run command-r:latest --verbose why is the sky blue  general firebase firebase firebase primarioası firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase  firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase firebase  firebase
and
`ollama run command-r:latest

Hello.
generalası obligatoireasıası firebaseasıasıası
obligatoireasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıasıası
`

Using /set parameter num_gpu 0 (or any figure) appears to fix the issue.
`ollama run command-r:latest --verbose

/set parameter num_gpu 0
Set parameter 'num_gpu' to '0'
why is the sky blue?
The sky appears blue to human observers due to a phenomenon called Rayleigh scattering. When sunlight enters Earth's atmosphere, it encounters gases and particles
that cause its light to scatter in different directions. Blue light has shorter wavelengths compared to other colors in the visible spectrum, which makes it more
prone to scattering by the tiny molecules of air (mostly nitrogen and oxygen). As a result, when you look towards the sky, you see more blue light reaching your
eyes because it has been scattered in all directions by these atmospheric particles.

This phenomenon is named after Lord Rayleigh, the British physicist who first described it in the 19th century. However, keep in mind that the sky can appear
differently at various times of day or under different weather conditions due to other factors like humidity, pollution, and the presence of dust or haze.
total duration:       54.565436458s
load duration:        12.696016792s
prompt eval count:    32 token(s)
prompt eval duration: 9.387385s
prompt eval rate:     3.41 tokens/s
eval count:           166 token(s)
eval duration:        32.472529s
eval rate:            5.11 tokens/s

`


Permission fixes when adding collaborators

Added user_has_organization_role_origins and fix can_become_member to use role_origins
Forbid becoming a collaborator when owner, collaborator or organization owner only

Task linked: DEV-3279 A user that has ADMIN role in an organization cannot be added as a project collaborators for any organization owner projects


move-to-next-paragraph using } doesn't work with CRLF line endings

Possibly related to #910 and #885
Using } goes to the end of the line, and then does not move
Using { simply moves the cursor to the end of the line two lines above.

I think this is fixed via atom/atom#9937. It will be out in Atom versions 1.4.0 and 1.4.0-beta0.


Snakeploy Installation Fails

Hello!
Snakeploy isn't pulling all the required workflow rules, meaning attempts to run the pipeline will give you FileNotFoundError. It's still possible to successfully complete the installation manually from github, of course, it's just a little confusing for non savvy users trying to follow the instructions as written on the workflow catalog.

Ah, I think that is because the version that is pulled (tag v2.0) might be broken, let's see if a v2.1 tag will solve it (after addressing the remaining open issues).


CFITSIO.jl error

Facing this error from CFITSIO.jl
``

ERROR: CFITSIO has encountered an error. Error code 412: datatype conversion overflow
Detailed error message follows:
Numerical overflow during type conversion while writing FITS data.
Stacktrace:
[1] fits_assert_ok
@ ~/.julia/packages/CFITSIO/nSUZm/src/CFITSIO.jl:225 [inlined]
[2] fits_assert_ok
@ ~/.julia/packages/CFITSIO/nSUZm/src/CFITSIO.jl:219 [inlined]
[3] fits_write_col(f::CFITSIO.FITSFile, colnum::Int64, firstrow::Int64, firstelem::Int64, data::Vector{Int16})
@ CFITSIO ~/.julia/packages/CFITSIO/nSUZm/src/CFITSIO.jl:2604
[4] sxt_l2evtlist_merge(l2evtfilelist::String, merged_evtfile::String)
@ SXTMerger ~/.julia/packages/SXTMerger/UGgRo/src/sxt_l2evtlist_merge.jl:96
[5] top-level scope
``

?
I don't think this is related to this project.
@ghost, maybe check out: https://github.com/JuliaAstro/CFITSIO.jl


Server error for<EMAIL_ADDRESS>

https://bundle.run/<EMAIL_ADDRESS>yields the following error:
Cannot find module './common' from '/var/app/current/.tmp/3c70316a8727a02cb9b6de0d1d2c1ba749c33b98/package/node_modules/debug/dist'

I invalided the entry, could you please try again?


Scrolling on the front layer does not work

Is your feature request related to a problem? Please describe.
Scroll does not work at the top of the front layer

Don't use AppBarLayout. There's LinearLayout as alternative.


Fixed data URL bug with share button

Fixed a problem that generated URL is wrong when operating in subdirectory.
Before modification, the setting value at root  of _confi.yml root was ignored.

You are transforming a relative url into an absolute url. I believe config.root+post.path should be enough.

Thanks for your suggestion(I believe config.root+post.path should be enough. ).
However, I think that there is a problem with config.root + post.path.
For example, if you create a post on twitter with a relative URL, you use root / 2018/08/24 / hello-world /. This URL is not valid.
I believe that the URL to be placed on the share button needs to be an absolute URL.

Hey guys :wave: Thanks for giving some ideas for this. I know we're taking a while to get to items since we have so many issues. If you can help close out issues that will be great.
For this type of thing we would want to go the route of using helpers like `url_for:
https://hexo.io/docs/helpers#url-for

root: value should also be included in url: in your _config.yml.
See
https://github.com/hexojs/hexo-starter/blob/571320ba41a83e065d7560e050eb3fa63ad74a57/_config.yml#L15
https://github.com/hexojs/hexo/pull/3604#issuecomment-511323247

https://github.com/hexojs/hexo-util/pull/84 has been merged.
Pending new version of hexo-util and full_url_for() helper.


(FACT-1964) Multiple mountpoints on same directory

Jenkins please test this on redhat7-64a

CLA signed by all contributors.

For this specific issue, I would just do this honestly:
// Skip over rootfs
if (mtype == "rootfs") {
    continue;
}

Even though the Linux kernel allows multiple mounts on the same mountpoint, this is not something you'd often see in the wild... because there are virtually no reasons one should do it, since data from the first mount is shadowed by subsequent mounts.
$ mkdir first_mount
$ mkdir second_mount
$ touch first_mount/1
$ touch second_mount/2
$ mkdir mountpoint
$ mount --bind first_mount mountpoint
$ ls mountpoint
1
$ mount --bind second_mount mountpoint
$ ls mountpoint
2

Jenkins please test this

Jenkins please test this


input json file for swagger-codegen

i have seen in your source code that you use swagger-codegen to generate modules to interact with rest api server.i want to use this code generation tool too in cpp.so can you give me the input file in json or yaml  format like http://editor.swagger.io/.thank you very much.

@dgarcia360 i have seen it.Thank you very much.

@Vektrat Thanks a lot.


add Universal Printer Template

Hi,
i add a universal printer template.
This template is valid for all printer manufacturers and all devices that are attached to the RFC1759 and RFC3805 (Printer-MIB).
The serial number, trays, toner and output trays are discovered (LLD) and monitored. The counter and filling levels are displayed in graphs.
The following components are detected:
Input

Input trays
Manual feed

Media Transfer

Simplex Module
Duplex Module

Supplies

Toner cartridges
Drumps
Transfer Kit
Waste Toner Box

Output

Output trays
Finisher

Tested with HP, Kyocera, Samsung and Xerox
Knowing Issues:
Some manufacturers send the string as a HEX, for example HP. This can't be automaticly converted by Zabbix, please see Bugreport ZBXNEXT-505.

I got around this by deleting the <request_method>post</request_method> lines... This imported the file, BUT it doesn't work with my Zebra printer... (test printer)... Giving no data in most of the OIDs queried....


Addon Kafka-operator

Description of your changes
Adds kafka-operator as an addon
one of the addons mentioned in the issue  https://github.com/kubevela/kubevela/issues/5358

How has this code been tested?

Checklist

I have:

[ ] Title of the PR starts with type (e.g. [Addon] , [example] or [Doc]).
[ ] Updated/Added any relevant documentation and examples.
[ ] New addon should be put in experimental.
[ ] Update addon should modify the version in metadata.yaml to generate a new version.

Verified Addon promotion rules
If this pr wants to promote an experimental addon to verified, you must check whether meet these conditions too:

[ ] This addon must be tested by addon's e2e-test to guarantee this addon can be enabled successfully.
This addon must have some basic but necessary information.

[ ] An accessible icon url and source url defined in addon's metadata.yaml.
[ ] A detail introduction include a basic example about how to use and what's the benefit of this addon in README.md.
[ ] Also provide an introduction in KubeVela documentation.
[ ] It's more likely to be accepted if useful examples provided in example dir.

@wonderflow @wangyikewxgm when I'm running below yaml after enabling the addon with definition kafka-cluster
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: kafka-cluster-sample
spec:
  components:
    - type: "kafka-cluster"
      name: "kafka"
      properties:
        kafka:
          version: "3.3.2"
          replicas: 3
          listeners:
            - name: plain
              port: 9092
              type: internal
              tls: false
            - name: tls
              port: 9093
              type: internal
              tls: true
          config:
            offsets.topic.replication.factor: 3
            transaction.state.log.replication.factor: 3
            transaction.state.log.min.isr: 2
            default.replication.factor: 3
            min.insync.replicas: 2
            inter.broker.protocol.version: '3.3'
          storage:
            type: ephemeral
        zookeeper:
          replicas: 3
          storage:
            type: ephemeral
        entityOperator:
          topicOperator: {}
          userOperator: {}

no pods are getting created and no error occurs. Do you see anything I'm missing or making any mistake.

You can check the status of applied CustomResource.

@wangyikewxgm I've checked and found, resource name kafka gets created with the CRD Kafka for the expected replica set but pods doesn't get created. The same thing is happening with the addon redis-operator in my machine (Pods doesn't get created) can you test the redis-operator in your machine with the YAML:
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: redis-operator-sample
spec:
  components:
    # This component is provided by redis-operator addon.
    # In this example, 2 redis instance and 2 sentinel instance
    # will be created.
    - type: redis-failover
      name: ha-redis
      properties:
        # You can increase/decrease this later to add/remove instances.
        replicas: 3

so that we can address the issue with the kafka-operator.

@wangyikewxgm I've checked and found, resource name kafka gets created with the CRD Kafka for the expected replica set but pods doesn't get created. The same thing is happening with the addon redis-operator in my machine (Pods doesn't get created) can you test the redis-operator in your machine with the YAML:
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: redis-operator-sample
spec:
  components:
    # This component is provided by redis-operator addon.
    # In this example, 2 redis instance and 2 sentinel instance
    # will be created.
    - type: redis-failover
      name: ha-redis
      properties:
        # You can increase/decrease this later to add/remove instances.
        replicas: 3

so that we can address the issue with the kafka-operator.

Ok, will have a try.My slack ID is YikeWong, feel free to discuss on slack.

@wangyikewxgm @wonderflow I have tested it locally, works fine. Let me know If you find anything to be changed or improve :)

@wonderflow here is some details:-
Kafka-cluster: It's the main system/application which will add all core properties.
kafka-cluster must be users controllable.
kafka-bridge: The Kafka Bridge provides a RESTful interface that allows HTTP-based clients to interact with a Kafka cluster.  It offers the advantages of a web API connection to Strimzi, without the need for client applications to interpret the Kafka protocol.
By default It's not configured with kafka-cluster, So it must be configured by users if they want to make HTTP connection possible to kafka-cluster.
kafka-connect: Kafka Connect is an integration toolkit for streaming data between Kafka brokers and other systems using connector plugins. Kafka Connect provides a framework for integrating Kafka with an external data source or target, such as a database, for import or export of data using connectors.
By default It's not configured with kafka-cluster, So it must be configured by users if they want to use external data sources like database etc.
kafka-connector: Kafka Connect uses connectors to integrate with other systems to stream data. A connector is an instance of a Kafka Connector class, which can be one of the following type: Source connector, Sink Connector
kafka-connector is used with kafka-connect for connection purpose of data sources
MirrorMaker or MirrorMaker2: Apache Kafka provides a solution called MirrorMaker which gives the ability to mirror data from a source Kafka cluster to a destination Kafka cluster.
This is also user friendly tool to replicate data from one source to another.
kafka-topic: topic refers to a category or a common name used to store and publish a particular stream of data. Basically, topics in Kafka are similar to tables in the database, but not containing all constraints. In Kafka, we can create n number of topics as we want. It is identified by its name, which depends on the user's choice.
kafka-topic is also user friendly, that's directly used by end-users.
kafka-user: For Kafka users configuration, directly  used by admin or owner to configure users for Kafka.
kafka-rabalance: It is configured to depict every partition of topic to the accurate consumer.
So, kafka-rebalance is directly used by endusers
So, it seems all the components that I added is useful for endusers. What do think?

kafka-bridge seems should be a trait definition.
MirrorMaker or MirrorMaker2 seems should not be a definition.
kafka-user seems should not be a definition, just operated by operator

@wonderflow kafka-bridge creates a deployment with a single pod, so I think correct definition type is component and what about other definitions kafka-connect, kafka-connector, kafka-rebalance?

@wonderflow @wangyikewxgm I've made change like removed definitions MirrorMaker, MirrorMaker2 and kafka-user and updated README. can you have a look on that ?

@wonderflow I've updated Readme, Now Readme explains how kafka can be used as a Producer/Consumer using kafka-topic, Please review it.

@wonderflow we can't create a vela Application because the image producer/consumer uses, runs a shell application that must be connected in interactive mode to interact with Topic otherwise producer/consumer finishes running instantly, So we can create YAMLs to create producer/consumer pods but can't connect to them as they aren't stable to connect.
So, To run producer/consumer we must connect to them in interactive mode at the time of running producer/consumer.

And all the messages that're generated through producer can be consumed using consumer from Topic

@wonderflow I've added instructions in Readme to create a NodePort Service to access kafka-bridge & replaced uses of kubectl with vela Please Review it.

@wonderflow I've fixed CI test.


Update go-releaser.yml

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
11 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-4.2%) to 67.816%

Files with Coverage Reduction
New Missed Lines
%

internal/start_command.go
2
38.95%

internal/server.go
9
71.83%

Totals

Change from base Build<PHONE_NUMBER>:
-4.2%

Covered Lines:
177

Relevant Lines:
261

💛  - Coveralls


Make menus dark blue

Wondering if you would consider making the bordering menu and file list colors a darker blue rather than dark grey, like is seen in the blue mood sublime text theme.

Good suggestion, will do.

@ktbarrett pls see https://marketplace.visualstudio.com/items?itemName=eddy1470669.blue
hope this is what you wanted


Install Docker-py failed

Not sure if this is related to https://github.com/angstwad/docker.ubuntu/issues/27, but I hit this error during the Docker-py install:
{"cmd": "/usr/bin/pip install docker-py", "failed": true}
msg:
:stderr: Traceback (most recent call last):
  File "/usr/bin/pip", line 9, in <module>
    load_entry_point('pip==1.5.4', 'console_scripts', 'pip')()
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 351, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2363, in load_entry_point
    return ep.load()
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2088, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 11, in <module>
    from pip.vcs import git, mercurial, subversion, bazaar  # noqa
  File "/usr/lib/python2.7/dist-packages/pip/vcs/mercurial.py", line 9, in <module>
    from pip.download import path_to_url
  File "/usr/lib/python2.7/dist-packages/pip/download.py", line 25, in <module>
    from requests.compat import IncompleteRead
ImportError: cannot import name IncompleteRead

I was able to solve it by sshing in and running easy_install -U pip which upgraded to 6.0.8

This is more of a python packaging problem than anything else.  :(. It is, BTW, unrelated to #27.
I suggest users that experience this issue regularly should create a pretask to upgrade pip.


[ISSUE #3728] docs: Make the The 'Uses of keys' entry in the document 'Best practices' more complete.

Make sure set the target branch to develop
What is the purpose of the change
For #3728

Coverage decreased (-0.1%) to 53.136% when pulling 7fa824b6b17b9fd960235a55d7eea12d3322bba2 on XiaoyiPeng:docs_uses_of_keys into ed5f4e4eac71849bc479aee2db7cc931d262a184 on apache:develop.

Codecov Report

Merging #3729 (7fa824b) into develop (ed5f4e4) will decrease coverage by 0.12%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #3729      +/-   ##
=============================================
- Coverage      47.29%   47.16%   -0.13%
+ Complexity      5042     5022      -20
=============================================
  Files            628      628
  Lines          41409    41409
  Branches        5379     5379
=============================================
- Hits           19584    19532      -52
- Misses         19395    19452      +57
+ Partials        2430     2425       -5

Impacted Files
Coverage Δ

...rg/apache/rocketmq/common/stats/StatsSnapshot.java
84.61% <0.00%> (-15.39%)
:arrow_down:

...ache/rocketmq/common/stats/MomentStatsItemSet.java
39.13% <0.00%> (-13.05%)
:arrow_down:

.../apache/rocketmq/common/stats/MomentStatsItem.java
38.09% <0.00%> (-9.53%)
:arrow_down:

...in/java/org/apache/rocketmq/test/util/MQAdmin.java
38.88% <0.00%> (-5.56%)
:arrow_down:

...va/org/apache/rocketmq/common/stats/StatsItem.java
50.00% <0.00%> (-5.00%)
:arrow_down:

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-2.99%)
:arrow_down:

...lient/impl/consumer/DefaultMQPushConsumerImpl.java
39.47% <0.00%> (-2.29%)
:arrow_down:

...a/org/apache/rocketmq/filter/util/BloomFilter.java
59.13% <0.00%> (-2.16%)
:arrow_down:

...rocketmq/client/impl/factory/MQClientInstance.java
51.30% <0.00%> (-2.00%)
:arrow_down:

...he/rocketmq/client/trace/AsyncTraceDispatcher.java
78.21% <0.00%> (-1.49%)
:arrow_down:

... and 10 more

Continue to review full report at Codecov.

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


ArcMutexGuard is unsound

The ArcMutexGuard type is unsound because it implements Sync if T: Send, when it should be Sync if T: Sync (just like the regular MutexGuard)
This code causes a race condition: (tested with miri)
(with parking_lot v0.12.1 + feature arc_lock)
(no playground link as it requires an extra feature)
use parking_lot::Mutex;
use std::cell::Cell;
use std::sync::Arc;
use std::thread;

pub fn main() {
    let data = Arc::new(Mutex::new(Cell::new(-1)));

    // this is Sync even though T isn't
    // ArcMutexGuard is Sync if T is Send
    let guard = data.lock_arc();

    thread::scope(|s| {
        for n in 0..10 {
            // closure is move so this moves the ref instead of the whole guard
            // &guard is send even though &cell isnt
            let g = &guard;
            s.spawn(move || {
                let cell: &Cell<i32> = g;
                cell.set(n); // data race
            });
        }
    });

    println!("non-deterministic: {}", guard.get());
}

Yeah I'm the one who wrote this code. I'll fix it tomorrow.


Pass full input_shape to cell.build()

step_input_shape unnecessarily deprives Cell instances of potentially necessary information - namely, custom architectures may require the layer's timesteps at build time (before call()). There are no performance or memory gains from trimming a list by one, nor really in clarity as this isn't being passed to call where the input shape does omit the time dimension (and in that case input_shape as opposed to step_input_shape is misleading anyway).
This commit does not require changing any other code in recurrent or recurrent_v2, as input_shape is indexed via [-1] - though unsure for the rest of the repository; either way, nothing is lost with this commit.

This breaks the API contract that layers.build() method will get the shape of input tensor, which should be same as the one passed in when call() is invoked. So far the cell only rely on the last dim of the inputs to build the weights, but this might not be true for other customized cells, eg if the cell somehow rely on the batch size to do certain behavior, in the time_major input case, the first dim is no longer batch, but timestep if we pass the full input shape.

@qlzh727 Is recurrent_v2 exempt from this contract, then? timesteps is extracted from input_shape, so its call() has a different input_shape than its build() (via super()).

I am not sure what you mean. In LSTM v2, the call() and build() will get same input_shape. Could u be more specific about the different shape here?

@qlzh727 input_shape isn't actually passed in, but extracted as K.int_shape(inputs), and the layer doesn't define its own build(),  but inherits it from recurrent.LSTM - so basically a "trick" to circumvent the contract. Well, such tricks are quite inconvenient to implement for custom RNN layers - one's via re-implementing the base class (RNN), another is to pass timesteps to each layer in the model by fetching it manually from preceding layers.
I'm guessing regardless of who oversees this 'contract', the process for possibly changing it will take months - so instead, how about this: pass full input_shape to both, build() and call() of all recurrent layers. Would that work?

I'm guessing regardless of who oversees this 'contract', the process for possibly changing it will take months - so instead, how about this: pass full input_shape to both, build() and call() of all recurrent layers. Would that work?

All the recurrent layer IS currently getting full input_shape for both build() and call(). All the recurrent cells is getting input shapes without the timestep dimension. I don't think this contract need to be changed for RNN.
My question, however, is why the cell need timestep in the build() method. A cell should handle the input one timestep by one timestep, and it shouldn't care how many timesteps there will be for the whole sequence. Can u be more specific about why the timestep is needed? (Is it related to https://github.com/tensorflow/tensorflow/issues/36559?)

@qlzh727 I include the time dimension in the "full" input shape, as that's what the layer is fed in the model network. And you are correct, this is about recurrent batch normalization - but also IndRNNs, which require timesteps at build time for recurrent_kernel initialization. I've implemented the layer in tf.keras in TF 1 & 2 without publishing - and for the record, it easily dominates LSTMs and GRUs in my application, and I may PR it in the future.
This said, while TF currently doesn't have any layers that need timesteps at build time, some users (like myself) may need it for custom functionality. Nothing is lost from passing it instead of "step input shape" - so omitting the time dimension is unnecessarily prohibitive.

Sorry for the late reply. If your cell need to be timestep aware, then it is no longer a cell, but a RNN layer, since the cell only exposed to one timestep at a time. Maybe you should create subclass RNN layer instead of a cell?

@qlzh727 build() belongs to cells, and RNN base class never passes the full input shape to either the layer or the cell. Hence, since all RNNs inherit RNN - either (1) RNN must be re-implemented, or (2) timesteps must be passed to the layer as an argument. Both add much redundancy.
call() could also be timesteps-dependent, and is for recurrent batchnorm; at inference time, generalizing to timesteps longer than trained uses the last train step's moving average.
Can you suggest an 'API-friendly' means of injecting timesteps information into a cell at build time? If so, I'll consider this resolved - but whatever I thought of so far is overly hackish.

I would suggest you to sub class RNN layer for your normalization case.

Even we pass the full input_shape from RNN layer to cell.build(), it is also very likely that the timestep dimention is None. It is very common for user to build a model with dynamic timestep size. I don't think you can build weights with None as any part of the shape.

In the case of normalization, eg, you will have mean and variance for the batch of the data in your RNN layer, why those value has to aware of the length of timestep? especially at each individual step? I would expect the mean and variance are calculate against the feature dim (which is the last axis, rather than the timestep axis).

For IndRNNs, I check the existing implementation in TF contrib. The IndRNNCell also build with (batch, feature) as input shape,  and doesn't need timestep. The code was in contrib, which is not visible on HEAD, but you can get it from TF 1.15 release. Here is some snippet from the it:

class IndRNNCell(rnn_cell_impl.LayerRNNCell):
  """Independently Recurrent Neural Network (IndRNN) cell
    (cf. https://arxiv.org/abs/1803.04831).

  Args:
    num_units: int, The number of units in the RNN cell.
    activation: Nonlinearity to use.  Default: `tanh`.
    reuse: (optional) Python boolean describing whether to reuse variables
     in an existing scope.  If not `True`, and the existing scope already has
     the given variables, an error is raised.
    name: String, the name of the layer. Layers with the same name will
      share weights, but to avoid mistakes we require reuse=True in such
      cases.
    dtype: Default dtype of the layer (default of `None` means use the type
      of the first input). Required when `build` is called before `call`.
  """

  def __init__(self,
               num_units,
               activation=None,
               reuse=None,
               name=None,
               dtype=None):
    super(IndRNNCell, self).__init__(_reuse=reuse, name=name, dtype=dtype)

    # Inputs must be 2-dimensional.
    self.input_spec = input_spec.InputSpec(ndim=2)

    self._num_units = num_units
    self._activation = activation or math_ops.tanh

  @property
  def state_size(self):
    return self._num_units

  @property
  def output_size(self):
    return self._num_units

  def build(self, inputs_shape):
    if tensor_shape.dimension_value(inputs_shape[1]) is None:
      raise ValueError(
          "Expected inputs.shape[-1] to be known, saw shape: %s" % inputs_shape)

    input_depth = tensor_shape.dimension_value(inputs_shape[1])
    # pylint: disable=protected-access
    self._kernel_w = self.add_variable(
        "%s_w" % rnn_cell_impl._WEIGHTS_VARIABLE_NAME,
        shape=[input_depth, self._num_units])
    self._kernel_u = self.add_variable(
        "%s_u" % rnn_cell_impl._WEIGHTS_VARIABLE_NAME,
        shape=[1, self._num_units],
        initializer=init_ops.random_uniform_initializer(
            minval=-1, maxval=1, dtype=self.dtype))
    self._bias = self.add_variable(
        rnn_cell_impl._BIAS_VARIABLE_NAME,
        shape=[self._num_units],
        initializer=init_ops.zeros_initializer(dtype=self.dtype))
    # pylint: enable=protected-access

    self.built = True

  def call(self, inputs, state):
    """IndRNN: output = new_state = act(W * input + u * state + B)."""

    gate_inputs = math_ops.matmul(inputs, self._kernel_w) + (
        state * self._kernel_u)
    gate_inputs = nn_ops.bias_add(gate_inputs, self._bias)
    output = self._activation(gate_inputs)
    return output, output

@qlzh727 Thanks for the suggestions.

It is even more likely for batch_size to be None, yet we require it for stateful=True; personally I've yet to see a None for timesteps, but just as for stateful, we can require timesteps to be defined for recurrent batchnorm.
I'll clarify; the bottom of page 3 of the paper reads:

... we estimate the population statistics separately for each timestep 1, ..., Tmax, where Tmax is the length of the longest training sequence. When at test time we need to generalize beyond Tmax, we use the population statistics of time Tmax for all time steps beyond it.

Thus, the population statistics variables will be shaped (Tmax, units) - requiring the knowledge of Tmax at build time.

The implementation is flawed; authors note the need for careful weight clipping for a certain range of timesteps to avoid exploding gradients - and is shown in the official implementation (alias seq_len). That implementation uses a safe default for several cases, but not all (and _kernel_w also lacks an initializer).

If the intention for this PR is trying to address your BN RNN issue, then I would suggest take the subclass RNN layer approach, but this will require some work.

In your BN RNN layer, each step has to aware that what the current step number is, and find the corresponding BN variable to use. The current RNN API doesn't pass any step number information to the cell, so finding the corresponding BN variable will be tricky. The implementation in your https://github.com/tensorflow/tensorflow/issues/36559 might not be correct since the step function is called once first to calculate the output shape when creating the output TensorArray. The result of that is ignored.

The step information is available in the loop function in the keras backend.rnn() while iterating through the time sequence, we don't pass that info to the cell since the cell doesn't need to aware of it. In you case, you probably want to create a BN variable in your RNN layer. At the time when calling the cell, you need to reconstruct you input into a nested structure, with the BN variable. The backend.rnn should handle the nested input correctly by sliding on the BN with timestep dim, same as the input. You cell should get real input and the slide of BN variable in the call() as the first parameter, and you might want to return the value for the BN variable in the result as well.

At the end of BN RNN layer call() body, you probably want to gather the result of BN and add update to the original variable. Your cell probably shouldn't worry about updating the BN since they are just using the value.

With that I think your cell don't need to worry about the timestep information since it really shouldn't, and the layer will handle it.

@qlzh727 I suppose I haven't sufficiently considered a _v2-like approach, utilizing K.rnn directly via the layer's call(); since it recieves the complete input, I should be able to build variables at call time, with if not self.bn_built-like logic. I've just been trying to stick to tf.keras layer structuring, as I presume it's more stable and optimized - but this does seem fitting. You are also correct regarding step - I've re-implemented it since and confirmed it works via tf.print.
The intent wasn't just to get RBN working, but that the current policy adds redundancy that's easy to change. Regardless, I've suspended my works on RBN per performance and correctness concerns; perhaps my mistake is trying to use the exact loop function that tf.keras uses, where something else might be more appropriate. I may look into it again in some future, only if TF Profiler's fixed in 2.1+.
In any case, though I've yet to try it, your approach seems promising, and I don't have much else to add on the issue for now - so I'll close the PR. Also, thanks for following through with this, here and on other threads - you are the most responsive TF developer I've seen.


packages should have "PKGARCH=all" set

currently there is no binary in any of the packages, so they can safely be set to PKGARCH=all.
For this we rely on the luci.mk if the luci-feed which defines LUCI_PKGARCH?=$(if $(realpath src/Makefile),,all) (https://github.com/openwrt/luci/blob/c351beea561acafa088a3fd3d82bfec93ee45cd4/luci.mk#L12) for some reason this seems no to be evaluated correctly. So we end up in having ARCH-specifiy packages without any need.

Ping?

Had not a chance to look for the current situation for some time ....

On my build I'm including PR https://github.com/openwrt/luci/pull/2637 which this background link to luci.mk (via freifunk.mk) packages become ARCH=all. tested with OpenWrt-21.02.
For packages not using frefunk.mk wrapper manual adjustments are still needed. I'll see what  @jow- will decide on the mentioned PR and then change our packages to either way.


Open default browser

Todo

src/main_prompt.txt (rename and move)
start_discord.py (move)
trained_agents_data.pkl (move)
index.js (move)

Todo

src/main_prompt.txt (rename and move)// change name to openai_prompt.txt
start_discord.py (move) // All of the folder and files path are manage according to that file. Change this file path will require a major change in whole code.
trained_agents_data.pkl (move) // Move
index.js (move)


unable to create new payment code

First off, great website! Was testing a bit today and tried to create a payment code with a Bolt12 offer and silent payment address, but after > 1 hr it doesn't seem to work.
I noticed the auto-generated usernames have a period in them, which made me wonder how those work with the dns records, e.g., if I wanted to verify the record exists would I use dig txt nearby.anteater.user._bitcoin-payment.twelve.cash or nearbyanteater.user._bitcoin-payment.twelve.cash?
More a general question: how are you managing the txt records for multiple users? From reading BIP353, it seems the idea for Bolt12 is that there is a *.user._bitcoin-payment.twelve.cash record and then some native way to handle the username look via the lightning protocol? But how would this work for something like silent payments, where I want to host potentially millions of users each with their own silent payment address? I realise this is a bit off topic for your project, but was unsure of where to ask this question and figured you might have some insights since you seem to be hosting a potentially unbounded number of txt records for the twelve.cash domain.

I apologize I did not se this message earlier. Ok, thank you for the questions and discussion. Let me give you a better response to this in like 20 minutes when I can focus on what you're asking here.

@josibake

I noticed the auto-generated usernames have a period in them, which made me wonder how those work with the dns records, e.g., if I wanted to verify the record exists would I use dig txt nearby.anteater.user._bitcoin-payment.twelve.cash or nearbyanteater.user._bitcoin-payment.twelve.cash?

For names that have a period in them, you would use the period in the DNS lookup. My understanding of DNS is that you basically have the TLD, the Domain, and then subdomains. There is nothing more granular than that. So for us it looks like nearby.anteater.user._bitcoin-payment.twelve.cash is a sub-sub-sub-sub-domain, it's really just a sub-domain that includes periods in the string.
I can verify that nearby.anteater does not exist in our zonefile. I'm not sure if that is just an example name you created for this issue or if that is the one you actually tried. Feel free to DM me privately if you need to share any troubleshooting details with sensitive user info.
However, it should NOT take an hour to propagate in most normal situations. So my guess is something messed up and the DNS update never fired. If you can tell me how to replicate the issue, we will fix it.

More a general question: how are you managing the txt records for multiple users?

That's pretty simple. We just create a DNS record for each user. So if Alice, Bob, and Chani all sign up, we create 3 records:

alice.user._bitcoin-payment.twelve.cash.     bitcoin:lno123...abc
bob.user._bitcoin-payment.twelve.cash.     bitcoin:lno456...def
chani.user._bitcoin-payment.twelve.cash.     bitcoin:lno789...ghi

From reading BIP353, it seems the idea for Bolt12 is that there is a *.user._bitcoin-payment.twelve.cash record and then some native way to handle the username look via the lightning protocol?

Yes, there are bLIPs for resolving the DNS lookup over lightning. I think it's like "my node sends out a private onion message requesting a DNS lookup, and then some friendly node does the DNS lookup on my behalf and then sends me the DNSSEC signed response over an onion message, and the friendly node has no idea who it did the DNS lookup for". But don't quote me on that. You can DYOR in the bLIPs repo I think.

But how would this work for something like silent payments, where I want to host potentially millions of users each with their own silent payment address?

Just create millions of DNS records =)

Thanks for the questions and thoughtful discussion. We are actually interested in working more with silent payments. We have a field that supports silent payments in our webapp but have not done the necessary promotion of it to gain support in the SP community. Just let me know how I can replicate your issue, and feel free to reach out to me if you want to chat more about BIP353, I think we have each other on Discord.

@josibake are you still experiencing this issue?


[Sign Up Page] Incorrect error message when entering too short password and email

Google Chrome Version 119.0.6045.201 (Official Build) (64-bit)
Always reproducible
Preconditions: Go to page https://zero-waste-staging.onrender.com/en
Steps to reproduce

Click on 'Sign Up' tab
Fill in email address: 56
Fill in Password that consists of 5 characters: 8h
Confirm entering the same Password in the field 'Re-password': 8h
Fill in First Name and Last Name: /[a-zA-Zа-їА-ЯЄІЇ]+-?'?`?/
Choose appropriate country: Ukraine
Click 'Sign up' button

Actual result

An error message 'Password is too short (minimum is 6 characters), Password is too short (minimum is 8 characters), and Password is invalid' appears
An error message 'Email is invalid and Email is too short (minimum is 6 characters)' appears

Expected result

An error message 'Password is too short (minimum is 8 characters)' appears
An error message 'Email is too short (minimum is 6 characters)' appears

User story and test case links:
"User story https://github.com/ita-social-projects/ZeroWaste/issues/626
TC # https://jira.softserve.academy/browse/SWQ-466

https://github.com/ita-social-projects/ZeroWaste/issues/646

The actual result does not match the expected result.
It is necessary to remove:

Email is invalid
The password is invalid

Expected result
An error message 'Password is too short (minimum is 8 characters)' appears
An error message 'Email is too short (minimum is 6 characters)' appears

Related to https://github.com/ita-social-projects/ZeroWaste/issues/660
Clarification from an expert(20.12.2023): If the field is not empty, it is advisable to show the user all other errors. Because the information entered into the field can be both short and invalid at the same time. The user will be aware of all the following mistakes that have been made

Clearly understood


pose node show red

Check version my nodes last v1.0.13
Check file \ComfyUI_portables\ComfyUI\custom_nodes\ComfyUI_Custom_Nodes_AlekPet\PoseNode\js\pose_node.js
Check line 10, it must be import { $el } from "../../scripts/ui.js"; but not import { $el } from "../../../scripts/ui.js";
The latest version fixes this. https://github.com/AlekPet/ComfyUI_Custom_Nodes_AlekPet/commit/17d23aca855ec2ee851c4ecc7244df64dac5bdd4


MacOS support

some xaml markup errors in macOS.
Will there be future support?

some xaml markup errors in macOS.
Will there be future support?

Aura.UI should be executed in MacOS without problems, What is the code that does not run?


Improve designsystem of Alert

Need to improve this component on \<alert><Designsystem.mdx>
Improvements required :
Any reference image?
Any external reference?
You can checkout this one for better understanding.

This issue is already listed and assigned to @Tushar98644  #1296


ENH: Add GA vaccine scraper

I don't think we got definitions quite right.
The data lines up for total and completed, but for the few counties I hand-checked the number for total doses and initiated (1st dose) were the same.
This is not true on the dashboard

This is on purpose -- The first dose column is first dose only so we're summing first dose and second dose to get "at least one dose" which is our total_vaccines_initiated column.
In places where first dose + second dose = total the total_vaccines_initiated and total_doses_administered should line up.


DOC Proposal for achitecture documentation

📚 Documentation
Related to https://github.com/napari/napari/issues/1426 but thought it would be better to start a new issue that would outline specifically what architecture docs could be added and potential people to get information from. Discussed in recent documentation working group meeting. Motivated partly by having a technical writer!
Not expert, please feel free to edit/comment.
Architecture type docs that already exist
Most architecture type docs are in In-depth explanations.

Using magicgui in napari - how to use magicgui to compose GUIs. Also useful for plugin writers.
Asynchronous rendering - talks about Octree implementation and rendering, some information architecture but usage information as well.
An introduction to the event loop in napari - talks about the QtEventLoop - how actions taken by user result in 'events' (functions) added to the queue. User information here as well. Note this is distinct from napari python model events (defined by Event, EventEmitter, and EmitterGroup) see: https://github.com/lucyleeow/napari/pull/7#discussion_r921482283 for more.
Hooking up your own events - I think this is aimed at plugin writers (?). Talks about how to connect user events (e.g., keypress, mouse events) to functions.
Napari models and events - talks about how the 3 main components of napari (python models, qt classes and vispy classes) are connected.
Contexts and expressions - also useful for writing plugin manifests
App-model - app-model provides framework for the declarative schema that napari will be moving to. Describes how to compose the various registries.

New architecture docs and layout
A lot of useful information is contained in existing docs listed above but better organisation of the docs and context could be useful. In particular, information could be thought to target 3 groups of people: plugin devs, napari devs and users. It would be nice if we could have sections targeting each group. I understand there will be some overlap between groups and topic areas where it makes more sense to keep information on the whole topic in one section, but this could probably be resolved by cross-linking.
Potential outline (again not well versed in napari, suggestions welcome):

Broad overview of contents/structure of napari/ folder - e.g., tests live alongside code in _test/ folder, layer model objects describing image data live in napari/layers
Napari dev info:

How data is handled - information about how e.g., the layer classes, LayerList, camera class etc work
How the GUI/widgets are created and work - e.g., how _QtMainWindow and ViewerModle works, including existing docs: Using magicgui in napari and App-model
Information about rendering - how rendering, the canvas, VispyBaseLayer etc works. Maybe some information about async rendering?
How components are connected - information about how changing something in GUI or console results in changes to the viewer events, the QtEventLoop and existing docs: Napari models and events, An introduction to the event loop in napari, Hooking up your own events, Contexts and expressions.

Plugin dev info:

How to connect functions to events
How to add menu items/keybindings - related to App-model
Maybe information/tips about to deal with image data/metadata...?

User info: useful user info currently contained in In-depth explanations could be moved to other appropriate places so they do not live with dev/architecture docs. Since this issue is focused on architecture docs, improving/writing these types of docs are not in scope of this issue.

Other stuff
I recall that we have some vendored code (from qt or vispy..?), maybe some background information about this would be useful. Maybe dev targeted info on how (multi)threading works?
cc @DragaDoncila @chili-chiu

thanks @lucyleeow!
tagging @Nadalyn-CZI here :)

Thanks.

thanks for the detailed summary of what's currently out there.

I am conscious I may have missed something though so please let me know.

overarching categories 'developing napari' and maybe 'extending napari'

Sounds good. Just to clarify, what kind of information do you see in each?

Some of this stuff iirc is documented 'automatically' through npe2

Ah yes I forgot. It would be nice to have one central place to go to for documentation on writing plugins but I guess cross-referencing will do. WDYT?


Missing profile results in misleading error message in chef_gate log

Cookbook version
[0.14.1]
Chef-client version
[12.13.37]
Platform Details
[RHEL 7.2 on AWS]
Scenario:
[When you run the audit cookbook for a profile that does not exist, the chef_gate log will say Authentication failed. Please check your system's clock. This is misleading because the problem is a missing profile, not any authentication or problem with the clock.]
Steps to Reproduce:
[Run the audit cookbook for a profile that doesn't exist, then look at your chef_gate current log.]
Expected Result:
[If an error is because of a missing profile, the error message should state that the profile is missing.]
Actual Result:
[chef_gate current log will say Authentication failed. Please check your system's clock.]

@ricksebak This error should only come up if the authentication between Chef Server and Chef Compliance is not working. Are you able to retrieve available profiles?

In addition we are closely to finalizing the 2.0 version of this cookbook. Could you update the cookbook and verify that this issue still exists with the latest version? Be aware that we changed the syntax for defining profiles https://github.com/chef-cookbooks/audit#configure-node

@chris-rock After I upload the missing profile, audit works fine. Other aspects of authentication also work as expected (such as logging in using the "other provider" link.).
The readme suggests that 2.0 is unreleased. Are you suggesting testing with 2.0? Or the latest currently released version (1.1, apparently)?

Work on 2.0 is finalized and we do the latest testing. It will be released tomorrow.

@ricksebak Is this still valid for 2.0?

I was out all last week, so I haven't tried this yet. We're working on moving to audit 2.1 this week. I'll report back. Thanks.

Unfortunately this misleading error message still does appear in the chef_gate log even when using audit 2.1. When I use a profile named "doesntexist" I can see the "check your clock" error.
When I use a profile that does exist, those profiles work correctly.

We added better error output in https://github.com/chef-cookbooks/audit/pull/208/files#diff-ac3f30b2c66fd1ec1b818a9707a4066dR120 This will highlight that a profile could not be fetched. Therefore I am going to close this issue. Please reopen if this continues to be an issue.


refund doc correction

Doc reference : https://razorpay.com/docs/api/refunds

@sofiya02
Update the Refund - update response
added
got this response from postmen all params are identical with public doc but not in sequence
Fetch a Specific Refund for a Payment change to instance.payments.fetchRefund('pay_JTVtDcN1uRYb5n','rfnd_JTvPLzbhq92ZWD')
added
made correction fetch to fetchRefund


Do torchscript have to fix the batch size and image size?

FYI

image size: with or without torchscript, it should be fixed.
batch size: no need to fix


[support] Unable to load my generator

I recently created a generator: https://github.com/italomaia/hygen-axum-podman-template
Now I'm trying to test it with hygen-add, but I'm getting the following error:
> hygen-add axum-podman

Can't add hygen-axum-podman

 [Error: ENOENT: no such file or directory, scandir 'node_modules/hygen-axum-podman/_templates'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'scandir',
  path: 'node_modules/hygen-axum-podman/_templates'
}

If I create node_modules/hygen-axum-podman/_templates with mkdir, hygen-add manages to download the template, but then npx hygen is unable to use it. Any ideas?

Ok, my issue is a duplicate: https://github.com/jondot/hygen-add/issues/10#issue-1728310616


suggestion: make showKeys default to true

I can't think of a case where you would not want to know the keys of a document. If you do, you should be able to set this to false.

Closed by #51


test: never disable SMP

To turn SMP on pervasively.  Tests should be treated with a combination
of flagging specific cases as "1cpu" where we have short-running tests
that can be independently run in an otherwise SMP environment, and via
setting CONFIG_MP_NUM_CPUS=1 where that's not possible (which still
runs the full SMP kernel config, but with only one CPU available).
We have similar fix, commit: https://github.com/zephyrproject-rtos/zephyr/pull/18531/commits/c0e3b921d3db1328d3fd8a7cbcaa688982834af4, PR: https://github.com/zephyrproject-rtos/zephyr/pull/18531

That said IMHO at least wording of the rationale should be improved.

+1. And there's a typo straight in the subject line: "nerver".
Regarding changes to tests/net/socket/tls* tests done here: I'm not sure why they have CONFIG_SMP=n in the first place (@rlubos, do you have an idea?), but those tests are intended to be unit tests for just socket TLS functionality, so just as well can stays as they are. (Unless there's a specific issue with CONFIG_SMP=n, which I agree is not communicated well in this patch, and would be a deeper issue than just removing it from tests. Otherwise, for as longs as we have CONFIG_SMP config option, it only makes sense to have tests with it being n).

Otherwise, for as long as we have CONFIG_SMP config option, it only makes sense to have tests with it being n.
Not clear what do you mean by that. Could you please elaborate a bit more on that?

@andyross Any comments about this PR?

I would +1 a request for a clearer description, but I can see why this could be useful.
At risk of doubling the number of tests twister has to go through, maybe it's reasonable to get smp vs non-smp variants in yaml?

@IRISZZW could you please revisit this one?

@IRISZZW - needs to be rebased, I think

needs to be rebased, I think

Correct, and some of the tests have already been fixed in separate PRs by Anas. Note that IRISZZW moved on and is no longer working on ARC, @evgeniy-paltsev plans to address the remaining test as part of his work on SMP and ARCv3 cores.