NAVIGATION BAR IS NOT PERFECTLY ALIGNED and your profile icon is also not at correct place

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I CAN ADD FLOATING EFFECT IN DIVS AND ALSO PROFILE PIFCTURE IS AT WRONG PLACE
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hey People,
I have a couple of suggestions to enhance the website:
Floating Effect in Divs: Adding a floating effect can make the interface more dynamic and visually engaging.
Profile Picture Misplacement: The profile picture is currently positioned incorrectly. This needs to be fixed for a better user experience.
Could you please assign me this task? I'd also appreciate it if you could tag it for GSSoC and Hacktoberfest.

@anuragverma108 CAN YOU HELP ME WHAT IS THE CONFLICT IN THIS REPOSITORY ,IF NOT THEN PLEASE CONSIDER TO MERGE


Make language code matching case insensitive

LanguageToLexvo now matches three-letter language codes independent of case.

:+1:


Support for Basic and OAuth2.0 Authentication

I am not aware how to set any type of authentication for the target endpoint in CastleMock. As in my project, basic authentication and Oauth2.0 are widely used so I am curious whether there is any option available to configure these types of authentication in CastleMock.
I am expecting if I could get options similar to a tool called Postman where I could select the type of needed authentication from a dropdown.

Hi @GK2021-CTS.
Are you referring to authentication towards Castle Mock or allowing authentication for your mocked services? Could you elaborate a little bit more? Thanks!

Hi @karldahlgren
I am referring towards allowing the authentication for the mocked services. In my projects, most of the backend services are secured so I want to replicate the same authentication while setting up the mock services in CastleMock.

@karldahlgren Could you elaborate further exactly what you want Castle Mock to support? What is the expected behavior? Do you want it to actually authenticate each request towards Castle Mock? If so, why? Couldn't you do header matching and verify that the request contains the expected authentication header? If not, return a 401 response code.
Thanks!

For Basic authentication, I have added the header matching strategy but how should I configure 401 response code. I can only configure success status code. How to configure http status code for failure scenario in CastleMock ?

@GK2021-CTS I have attached an example on how you can configure your mocked endpoint. This example will check for the Authorization header. If missing, then it will fallback to a 401 Unauthorized.
UnauthorizedExample.zip

@karldahlgren , thanks for sharing this example. It is working as expected with your example but when I am trying to replicate the same in my service, I am getting 500 error instead of 401.

@karldahlgren , my bad, it is working now. It seems there was a spelling mistake error because of which I was not getting the desired 401 response.

@karldahlgren , it seems that I cannot apply basic authentication check for mocking SOAP services as there is no option in the response strategy for header query. Could you please confirm the same.


XDN03 - xlang type system

Note, this XDN is not complete. I'm putting it into PR to enable comments on the content that is available.

FYI, all the feedback in this PR has been addressed. I want to start on a new revision of this doc, so I'm going to go ahead and accept this PR. New PR w/ new changes coming soon


ci: add passphrase handling to update Nordix repos pipeline

Can one of the admins verify this patch?

ssh-agent will do the trick and handle key passphrase correctly


New domain name

My school has changed their email domain name so I'm updating it here too.

@claymorwan Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


tls = "letsencrypt" client still use ACMEv1?

time="2019-10-17T07:29:13Z" level=info msg="http: TLS handshake error from $IP: 403 urn:acme:error:unauthorized: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details."

the time of ACMEv1 is over...

Which version of acme-dns are you using at the moment?

Ok, so this is related to the Golang autocert package. The ACMEv2 was added as default just a few days ago.
I'll do a new release of acme-dns shortly.

ok, thx.
I've struggled into huge problems because of this, because it looks like the acme-dns REST api can't be access thru http-only. It always redirects to their own https endpoint (the documentation doesn't mentioned this) and therefore a ssl-cert is always needed to access the acme-dns rest api.

On the upcoming weekend I'm planning to finish work towards migrating from autocert to certmagic, a few DNS RFC fixes and moving to automated challenge responses using DNS validation. This will fix a wide array of issues along with this one.

I've struggled into huge problems because of this, because it looks like the acme-dns REST api can't be access thru http-only. It always redirects to their own https endpoint (the documentation doesn't mentioned this) and therefore a ssl-cert is always needed to access the acme-dns rest api.

Acme-dns REST api can be accessed through HTTP, if you set tls = "none" in the config.cfg

This was implemented in #190 and is included in v0.8 just released!


show in the Push tab if we've linked with OneSignal

We're using OneSignal for the time being for push. Would be great if you could reference this in the Push tab UI somewhere and redirect us to the linked OneSignal account. Similar to the redirect you provide to (for example) Application Insights.

Thanks @sogogolf for the request! @jwargo would you mind taking a look please?

@SogoGolf that's an interesting suggestion, we don't actually do any integration with OneSignal except for that redirect you already saw, so we have no way of knowing that you have OneSignal configured. I'll file this as a feature request as we see what we do next here.

@SogoGolf would you be willing to have an email conversation or chat about how you use push in your app(s)

Hi John, yes of course would love to help. Call would probably be best/most efficient.


Running on Kubernetes

Description:
For the user who has experiences with kubernetes, it's much easier to deal with kubernetes than the docker compose.
Kubernetes is much better than docker compose for the users who want to run their own instance of the stack.
Desired solution
Provide necessary manifest files for kubernetes cluster and provide detail instructions for some recommended kubernetes environments.

Kompose might be helpful here

Please assign this to me if this is a good feature to implement.

This would be ideal for us (need to deploy on a cluster running services behind a firewall which we can't access from a deployment outside).
I did try to use Compose (which I have used for similar in the past), but it did not work out of the box, so probably a more bespoke approach is needed.  A Helm chart would be great, but at least a set of yamls for k8s/openshift deployment would be good.

We should provide a helm chart with all the external dependencies optional so that you can swap them out in the cloud.
Bitnami charts are a good starting point.
https://github.com/bitnami/charts/blob/main/bitnami/mlflow/Chart.yaml#L16
@akihikokuroda are you still up for it?

If we use helm, we can put core bee services into the main chart and other dependencies as the subchart.  So that we can replace the dependency components easily.

Agree Helm would give the flexibility (through sub charts) to easily swap the dependencies.  It also allows for easy substitution of configuration options through a config values file.

++ agree. I also find compose awkard, and it can get difficult to keep as configurations get more complex. Though there are many people who still prefer it, especially if they don't have k8s skills
My preference would probably be for a helm chart as it's an easier 'packaging'. However, it's not so good at >day0 ops. So if any reconfiguration/control is needed an operator would be even better, but that's typically a lot more work - including in the design of the custom resources to model . I'd therefore be inclined to leave that for a future option.
Happy to help out with any k8s setup/testing as needed. We should have something that works in a typical 'desktop' environment (KinD / podman desktop / rancher desktop etc) as well a cloud (int or ext) - perhaps openshift sufficient. Just mentioning as permissions (ids/root), resources etc typically cause pain...

I'm making a very primitive helm chart now.  I'll make a [WIP] PR in a day or two.

WIP PR: https://github.com/i-am-bee/bee-stack/pull/14

Hey, I'm looking at the PR and it's a good start, thanks @akihikokuroda!
We'd like to align it with the kubernetes configuration we use for deployment so that we have a single unified way how to deploy the application :)
This means:

[ ] Add support for external infrastructure (mongo, redis, milvus)
[ ] Properly handle seeders and migrations - make them optional init containers / helm hooks
[ ] Standardize values.yml format to follow bitnami conventions
[ ] Proper secret management - add support for production secrets as well as dummy auth currently used locally
[ ] Add support for production UI image (pre-built with different NEXT build arguments)
[ ] Proper scaling configuration and support for worker pods - (RUN_BULLMQ_WORKERS API configuration)

Since this requires specific knowledge from the existing internal deployments and application internals, I'll take over the PR and make the necessary changes.
It might take some time, so in the meantime we'll be maintaining the docker-compose version of the stack.
cc @matoushavlena

@jezekra1 Would you make this issue an epic/story and create issues for each item?  So the others can contribute some pieces?

Sure! I created the epic here:
https://github.com/i-am-bee/bee-stack/issues/27

closing this as duplicate of #27


Error: :en is not a valid locale

if I do not have in available_locales :en, I get an error:
Showing<EMAIL_ADDRESS>where line #78 raised:
:en is not a valid locale
This error occurs because the project multiple times specifying an explicit locale: :en.

I also met this error. Is there any way to change the default locale used by railsadmin?

@x-ji I was tired of looking for some good solution so I fixed it with workaround. So go to source code of the gem file like: /home/user/.rvm/gems/ruby-2.1.5/gems/rails_admin-0.6.7/app/views/rails_admin/main/index.html.haml and change :en into suitable translation. In your case it is 'zh-CN'. And it works.

Same thing for me, the fix in https://github.com/sferik/rails_admin/wiki/Troubleshoot do not work.
My site is only in french.

Finally I had to overwrite the file views/main/index.html.haml and change line 78 to put :fr instead of :en.

Take a look also here: https://github.com/sferik/rails_admin/blob/dcb774d7a5629ae129436669f43be63adc455a49/lib/rails_admin/i18n_support.rb

Thanks for this


Importing structs through their public re-export

Hello 👋🏻
I'm trying to use this crate to automatically list my routes and models in the the utoipa macro. I tried to modularize my API into nested modules, each containing a models and a routes private submodule, with their contents re-exported publicly by mod.rs (pub use models::*; pub use routes::*;). However, because the structures are defined in a private module, I get the following error:
error[E0603]: module `routes` is private
  --> src/v1/routes.rs:12:10
   |
12 | #[derive(OpenApi)]
   |          ^^^^^^^ private module
   |
note: the module `routes` is defined here
  --> src/v1/members/mod.rs:7:1
   |
7  | mod routes;
   | ^^^^^^^^^^^
help: consider importing this struct through its public re-export instead
   |
12 | #[derive(crate::v1::members::__path_get_members)]
   |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

error[E0603]: module `models` is private
  --> src/v1/routes.rs:11:1
   |
11 | #[utoipauto]
   | ^^^^^^^^^^^^ private module
   |
note: the module `models` is defined here
  --> src/v1/members/mod.rs:6:1
   |
6  | mod models;
   | ^^^^^^^^^^^
help: consider importing this struct through its public re-export instead
   |
11 | crate::v1::members::Member
   |

warning: unused import: `super::members`
 --> src/v1/routes.rs:6:5
  |
6 | use super::members;
  |     ^^^^^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

For more information about this error, try `rustc --explain E0603`.

My src folder has the following structure
src
├── helpers
│   └── mod.rs
├── main.rs
└── v1
    ├── members
    │   ├── mod.rs
    │   ├── models.rs
    │   └── routes.rs
    ├── mod.rs
    ├── routes.rs # Here is the `utoipa` route
    └── server
        ├── features
        │   ├── compliance_tests
        │   │   ├── mod.rs
        │   │   ├── models.rs
        │   │   └── routes.rs
        │   ├── config
        │   │   ├── mod.rs
        │   │   ├── models.rs
        │   │   └── routes.rs
        │   └── mod.rs
        └── mod.rs

Do you know a way to work around this issue, other than putting routes and models in the same mod.rs file (which I'd like to avoid) or having the modules public (which generates a bad-looking OpenAPI spec)?
Edit: As a workaround, I switched the submodules to be public and I added a tag field in all utoipa::path macros so the generated tags are not ugly (i.e. members instead of crate::v1::members::routes).

Hey,
I don't really see how this can be solved easily...
Do you know how you'd want to declare it ?
Maybe a new macro on the public reexport ?
But tbh I feel like it would start to be very complex for such simple tool.
As you said, you can make the routes public or use the utoipa_ignore macro and import the privates paths manually.

Or maybe we could add an argument to the #[utoipauto] macro to only add the function name to utoipa, and you would add the use by yourself.
This seems like a great idea, what do you think about it ?

right now, utoipauto add the function by full path.
#[utoipauto]
#[derive(OpenApi)]
#[openapi(
    paths(
        test_controller::service::func_get_1,
    ),
)]
pub struct ApiDoc;

This work as is, however, this means that the full path as to be guess by utoipauto
We could add a argument to the macro to only add function name
#[utoipauto(disable_full_path)] //terrible name but we can figure out something better
#[derive(OpenApi)]
#[openapi(
    paths(
        func_get_1, // here, utoipauto would only add the function name
    ),
)]
pub struct ApiDoc;

This obviously won't work because Rust won't find it, but it allows you to add the 'use' line by yourself.
like
use crate::v1::members::routes::* //the reexported path, added by you

#[utoipauto(disable_full_path)]
#[derive(OpenApi)]
#[openapi(
    paths(
        func_get_1,
    ),
)]
pub struct ApiDoc;

I think this can be solved similiar to how I implemented the generic support.
We coud build a map of all public reexports and then match if the struct has been reexported and replace it with the reexport.
This will increase compile times and ram usage but I am not really concered about it.
The generic feature is only noticable in large projects and there we build a map of every import for every file.
And we could put this feature behind a feature flag so only users who want this are effected.
Although we have to build the map across multiple files.
We have to look how we solve this because currently the generic feature drops the map after a file is scanned.
And we need to add support for public reexports for the utoipa_ignore macro so that we can define which reexports we want to ignore.
But maybe someone has a better idea or some critic to this approach.


chore(proposal): add ESLint rule for consistent Boolean conversion for 'enabled' property

This PR introduces a custom ESLint rule that enforces the consistent use of the !! operator instead of the Boolean() function when converting values to a boolean for the enabled property within objects. This rule aims to standardize the boolean conversion practice across the codebase, enhancing code readability and consistency
Inspiration coming from this conversation: https://github.com/team-monite/monite-sdk/pull/200#discussion_r1695703430

This PR introduces a custom ESLint rule that enforces the consistent use of the !! operator instead of the Boolean() function when converting values to a boolean for the enabled property within objects. This rule aims to standardize the boolean conversion practice across the codebase, enhancing code readability and consistency
Inspiration coming from this conversation: #200 (comment)

@vkuprin : Vitaly, I suggest we use Boolean(...) instead of !! for converting values to booleans. Boolean(...) is more readable and self-explanatory, making our code more approachable, especially for those new to our codebase or JavaScript in general (remember, we have clients reading our code). The performance difference is minimal and not a concern. While !! is a concise shorthand, Boolean(...) prioritizes clarity and maintainability, which are crucial in our case of a public codebase.
So, to sum up, I am 100% for maintaining the uniformity of the repository, we should all strive to improve it, but let's also follow the readability and maintainability.

@vkuprin : please also add @chebum to reviewers.

This PR introduces a custom ESLint rule that enforces the consistent use of the !! operator instead of the Boolean() function when converting values to a boolean for the enabled property within objects. This rule aims to standardize the boolean conversion practice across the codebase, enhancing code readability and consistency
Inspiration coming from this conversation: #200 (comment)

@vkuprin : Vitaly, I suggest we use Boolean(...) instead of !! for converting values to booleans. Boolean(...) is more readable and self-explanatory, making our code more approachable, especially for those new to our codebase or JavaScript in general (remember, we have clients reading our code). The performance difference is minimal and not a concern. While !! is a concise shorthand, Boolean(...) prioritizes clarity and maintainability, which are crucial in our case of a public codebase.
So, to sum up, I am 100% for maintaining the uniformity of the repository, we should all strive to improve it, but let's also follow the readability and maintainability.

We discussed directly to keep consistency in chat https://github.com/team-monite/monite-sdk/pull/200#discussion_r1695681477 We can use different format Boolean everywhere

I believe, the issue isn't important enough to spend anymore time on it at the moment.


Update tag/release description for 2.122.1 to include TFS 2017.3

This is just a meta issue about updating the description/title for https://github.com/Microsoft/vsts-agent/releases/tag/v2.122.1 since it is also the agent shipped with 2017.3.
Maybe "v2.122.1 (TFS 2018 RTW and TFS2017 QU3)"

@nschonni the agent is always back compat, you can use latest version agent from github and it should works with even TFS 2017 (Win) Tfs2015 (Linux/OSX).
the release tag is us to remember which version of agent is packaged with which On-Prem TFS release. :)

Yup, I was asking the description to be updated because it is the version that shipped with on-prem 2017.3/3.1 (as well as TFS 2018 RTW) :wink:

No agent ships with on-prem - there's just a default one it pointed to for the download button.
I'm fine with adding a table on the front page of TFS release to sprint / release branch.

Sorry, I forgot to link to https://github.com/MicrosoftDocs/vsts-docs/issues/924 where someone flagged that the version table was out of date. I've put in a PR to fix that part already.

No agent ships with on-prem - there's just a default one it pointed to for the download button.

Right, I'm just using the wrong terms today 😝

I update the release to include TFS 2017 Qu3 info.
https://github.com/Microsoft/vsts-agent/releases/tag/v2.122.1


v2.0.0

Changelog

:warning: Min supported node version is now 16
Fixed action deprecation warning
Various dependencies update

cc @susnux

I tested on one of my repos and the workflow runs successfully, so it works fine :sparkles:


Black dependency missing

Nbdev seems to use black during the export, but its missing from the environment.
Could add that to optional dev requirements or at least list it in the README.

black is in the dev_requirements in settings.ini
does this not come with the pip install?

Ah right, I was certain it had to be listed somewhere...
Looks like I just forgot the [dev] install, at least it worked when I now tried again...


Add licence please

Looks very good Sam. To use this library will be good if you can insert a licence file so that users know how to distribute the code

Hi @gitkundan , I have added a license now. Thanks for the suggestion.

On there now, thanks.


Panic error

I get a panic error when using your hlcli with a Huawei B525S 23a.
Where could I get the documentation to check if the API protocol did change or is different from your ?
hlcli  SignalInfo -endpoint=<IP_ADDRESS> -v
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x48 pc=0x12b8f26]
goroutine 1 [running]:
net/http/httputil.DumpResponse(0x0, 0xc42012c101, 0x0, 0x13b58a0, 0xc4200edea0, 0x13b58a0, 0xc4200ede40)
/usr/local/go/src/net/http/httputil/dump.go:284 +0x46
github.com/knq/hilink.(*httpLogger).RoundTrip(0xc4200edd80, 0xc42012c100, 0xc4200edd80, 0xbed174508d15c166, 0x6fc4b765e)
/Users/meessen/Sources/go/src/github.com/knq/hilink/opts.go:59 +0xd8
net/http.send(0xc42012c000, 0x13b55e0, 0xc4200edd80, 0xbed174508d15c166, 0x6fc4b765e, 0x1547da0, 0xc42000e9e0, 0xbed174508d15c166, 0xc420055ae8, 0x1)
/usr/local/go/src/net/http/client.go:252 +0x185
net/http.(*Client).send(0xc420085a70, 0xc42012c000, 0xbed174508d15c166, 0x6fc4b765e, 0x1547da0, 0xc42000e9e0, 0x0, 0x1, 0x0)
/usr/local/go/src/net/http/client.go:176 +0xfa
net/http.(*Client).Do(0xc420085a70, 0xc42012c000, 0x24, 0x0, 0x0)
/usr/local/go/src/net/http/client.go:615 +0x28d
github.com/knq/hilink.(*Client).doReq(0xc420094410, 0x137a8d2, 0x18, 0x0, 0x0, 0xc420055d01, 0x0, 0x0, 0x0, 0x0)
/Users/meessen/Sources/go/src/github.com/knq/hilink/hilink.go:131 +0x116
github.com/knq/hilink.(*Client).NewSessionAndTokenID(0xc420094410, 0x0, 0x0, 0xc420126401, 0x2, 0x8, 0x12c06ad)
/Users/meessen/Sources/go/src/github.com/knq/hilink/hilink.go:242 +0x62
github.com/knq/hilink.NewClient(0xc420126410, 0x2, 0x2, 0x1, 0x2, 0xc420126410)
/Users/meessen/Sources/go/src/github.com/knq/hilink/hilink.go:76 +0x157
main.main()
/Users/meessen/Sources/go/src/github.com/knq/hilink/cmd/hlcli/main.go:210 +0x7d4

The verbose setting is bad. The problem here is that you need to pass the -endpoint= with the full URL: -endpoint=http://<IP>/. If you're using the default IP (ie, <IP_ADDRESS>) you don't need to specify the endpoint.

Thank you for answering so quick. Unfortunately the ˋhlcli SignalInfo ˋ doesn't work.
This is what I get
$ hlcli SignalInfo
error: invalid response

No idea if it works at all or if it ever did. Those commands were written based on possibly bad documentation. Update the code base and try again with -v, I fixed the error handling so it shouldn't panic.

I need to have a continuously updating SignalInfo to adjust an external antenna.
From your output it seam that we need to do the call with the returned session id to get the result back. Do you think we need to get the session id at every call or just once, if the time interval between to calls is small ?

What is needed is that the session token needs to be read from the cookie (ie the Set-Cookie header). The hilink firmware on the modems I'm using return it as part of the XML, as you can see between the differences between what you sent and the output I copied above.

It looks like the first transaction sends the session id in the response. The token is to be hashed with the password when we need a logged in session. I looked at some php code doing this (https://github.com/HSPDev/Huawei-E5180-API).
Apparently there is no set cookie from the router. I suspect that the protocol is that the first time the API is called, we get back a response with the session id and token. We have to call it a second time with the session id as cookie. There is another field referenced in the PHP code, but it isn't apparently required from your output sample.


ARROW-2843: [Format] Removing field layout from Schema.fbs breaks bac…

Fix backward compatibility of Schema

I think adding this field back in will make metadata written with 0.8.0 or 0.9.0 unreadable. I can confirm if that would be helpful. I don't think we should break the metadata two more times (adding this would take us to V5, then removing it again would take us to V6).

You cannot delete fields you don't use anymore from the schema, but you can simply stop writing them into your data for almost the same effect. Additionally you can mark them as deprecated as in the example above, which will prevent the generation of accessors in the generated C++, as a way to enforce the field not being used any more. (careful: this may break code!).

This suggests that maintaining backwards compatibility would require keeping a deprecated field in the schema forever. We should confirm, though

regarding typing for deprecated fields - yes looks like it could be a placeholder per say:

https://github.com/google/flatbuffers/issues/4385
There was a question
Would it be safe then to simply put some "placeholder" with arbitrary type ? ie go from
table { a:int; b:int; c:int } to: table { deprecated0 : empty (deprecated); b:int; c:int } where "empty" is some type (an empty table for example).
And and answer

Yes, a placeholder would be fine. In fact that was one of the suggestions above: the ability to have placeholders without a name or a type. Using some kind of type specifically for this purpose sounds like an ok alternative.

Here is some test code in Python to write a schema to a file, then read it, so different codebase revisions can be compared:
import pyarrow as pa

fields = [
    pa.field('foo', pa.int32()),
    pa.field('bar', pa.string()),
    pa.field('baz', pa.list_(pa.int8()))
]
metadata = {b'foo': b'bar', b'pandas': b'badger'}

schema = pa.schema(fields, metadata=metadata)

buf = schema.serialize()

with open('test2.schema', 'wb') as f:
    f.write(buf.to_pybytes())

with open('test.schema', 'rb') as f:
    schema_serialized = f.read()
    schema2 = pa.read_schema(pa.py_buffer(schema_serialized))

I will double check but it seems that these changes do not impact data written with 0.9.x. I'm concerned about having a lot of cruft lying around in our protocol, particularly when the justification for the cruft is based on a contraindicated use for Arrow that has not reached a stage of maturity where we have committed to maintaining backward compatibility.

Regarding data generated with arrow 0.8, 0.9 - very good point. We definitely need to test it.
I expect it to have issues.
Flatbuffers guarantee both backward and forward compatibility, but with no removal of fields.
Ironically this is not the last field - if it were it wouldn't be a problem.

Sorry that test that I gave is not sufficient because it's the field metadata that's impacted. I'll post an updated one

import pyarrow as pa

field_metadata = {b'foo': b'bar', b'pandas': b'badger'}

fields = [
    pa.field('foo', pa.int32(), metadata=field_metadata),
    pa.field('bar', pa.string(), metadata=field_metadata),
    pa.field('baz', pa.list_(pa.int8()), metadata=field_metadata)
]

schema = pa.schema(fields)

buf = schema.serialize()

with open('test.schema', 'wb') as f:
    f.write(buf.to_pybytes())

with open('test.schema', 'rb') as f:
    schema_serialized = f.read()
    schema2 = pa.read_schema(pa.py_buffer(schema_serialized))

Data written by 0.9.0 or master branch, after this patch the metadata seems to be dropped from reads (but the process doesn't crash in this example at least).

You mean when you write with 0.9 and read with my patch, right?
I would imagine since field is added we have one more field and somehow (probably not the case all the time) it considers that metadata is absent - since it reads length of metadata first. I would not trust it much. In some cases it should throw IndexOutOfBoundsException

Yes, write with 0.9.0, then read with this patch. The generated C++ bindings don't validate by default; it's possible that using a Verifier would catch the table VTable mismatch

Ok, Let me see what to do with versions 0.8 and 0.9 - we can't abandon them.
But at least we should keep in mind that blind removal fields from FlatBuffers can cause a lot of trouble.

Yes, let me get back on that. Need to think if/how we can keep "wolfs fed and sheep not eaten" :).

One option to help with migrating persisted data: you can write these schemas to JSON with Arrow 0.7.x, then parse the JSON (which has not changed, save for the omission of the vector layout) with 0.9.x/0.10.x and write out the new binary data.

Thank you for the suggestion. Though not sure why would I need to write it out to JSON first - I could probably write it directly to binary withe the omission of vector layout (after reading with earlier version)? Am I missing anything?

Ah, I was suggesting as an alternative to having to fashion a reader for the old protocol and a writer for the new protocol in the same process. If you made a simple CLI for JSON <-> Binary (like the integration tests do) and to run it against two JARs (one to read, the other to write).

Understood. Thank you for the suggestion. Will see.

I am going to close this PR and JIRA.
Just want to make sure that in the future we do not remove fields from "fbs", but mark them deprecated.


Split lines according to both dos and unix conventions

The current implementation could be simpler, but it would need the stream feature from tokio. In this way there is no compile-time overhead and the code should be understandable.
Closes #3

I'm pretty sure the FTP RFC only specifies \r\n as a valid line ending, but I can't look it up, do you know of any server that does otherwise? That said, it shouldn't be a problem for the client to be a bit more lenient in what it accepts.

Unfortunately this bit me as well: according to RFC 959 about the LIST command:

The data transfer is over the data connection in type ASCII or type EBCDIC. (The user must ensure that the TYPE is appropriately ASCII or EBCDIC). Since the information on a file may vary widely from system to system, this information may be hard to use automatically in a program, but may be quite useful to a human user.

This means that LIST could theoretically be any sort of human-friendly text, without any sort of format (or newline) specification. I did not like the FTP protocol before digging into these details, things are not getting any better :roll_eyes:

do you know of any server that does otherwise?

Yes, ftp.sda.it uses unix newlines (and it does not use any security protocol, but that's another story). You need to be authenticated, therefore you need to trust me on this, sorry :man_shrugging:.

Oh I know the pain of underspecified specs and system dependend behaviour 🤣
I was hoping that seeing as FTP is a pretty simple protocol, the spec would be better defined but apparently not.


Problem while installing nixos 18.09 on a kimsufi

See https://discourse.nixos.org/t/nixos-on-ovh-kimsufi-cloning-builder-process-operation-not-permitted/1494/2

A big thank you for writing this guide by the way ;)

This is great, thank you!


Is there any option to get translation results into new file on generation?

❓ Questions and Help
Before asking:

search the issues.
done
search the docs.
done

What is your question?
I trained a new model from my dataset and conducted generation. It is very useful to calculate bleu score directly.
However, I want to evaluate my model using METEOR and analyze its result qualitatively. For the purpose, i need an output file containing translation results from my test data.
Is there any option to save it on command-line tools?
Code

What have you tried?
What's your environment?

fairseq Version (e.g., 1.0 or master): 0. 9. 0
PyTorch Version (e.g., 1.0) 1. 3. 1
OS (e.g., Linux): Linux
How you installed fairseq (pip, source): source
Build command you used (if compiling from source):
Python version: 3. 6. 9
CUDA/cuDNN version: 10.0
GPU models and configuration: GTX 1080
Any other relevant information:

I think --results-file should work: https://github.com/pytorch/fairseq/blob/b65a85b692544e36f9e83ada91cf4ef529791c69/fairseq/options.py#L474-L475

Hi,
Is this the fastest way to evaluate generation with different scores other than BLEU (METEOR, TER, etc.) ?


Does not kill child process on MacOS

In some cases I want to kill a child process spawned from node, but even if I use this package giving the process's PID number, the process lives happily and does not close. Any idea?

Does the callback function gets executed?
var kill = require('tree-kill');
kill(1, 'SIGKILL', function(err) {
    // Do things
});

Same problem in mac. The default SIGTERM cause self  pid can not be killed.
This is also work:
kill(1, 'SIGKILL', function(err) {
    // Do things
    setTimeout(() => {
      process.kill(1)
    }, 200)
});

Same issue here.
I've found out that the solution by ps-tree works:
psTree(child.pid, function (err, children) {
  cp.spawn('kill', ['-9'].concat(children.map(function (p) { return p.PID })));
});

I do wonder if there's much point for this package to replicate the logic already in ps-tree? Just have ps-tree as a dependency and use in buildProcessTree?


File IDs are integers

The fileID type should probably be an integer under the hood, as that's what the API really uses for both return values and structure fields.
There's a chance this might break some stuff - specifically, I'm wondering if we've documented some API parameters as being "fileIDs" when in fact they can be either a file ID or a file name.

I don't see any uses where it would be a string so it was a mistake 😅


Explore lazy property merge

Background
Function.prototype.length can be an indicator if a function expects one argument or more.  If we can reliably use it, we could merge lazyProperties with regular ones and force jsiqle to evaluate the length of each one deciding how to handle it.
Argument lengths are pretty logical, with the exception of 0. In that case it's ambiguous due to it referring to either 0 arguments or variadic arguments. Practically, restricting the API to not use fully variadic arguments could be a solution.
Proposal
Such a change will mean merging the lazy properties API into the regular properties API. It will also mean altering the lazy property definition API from this:
{
  lazyProperty: ({ models, serializers }) => value => value.x;
}

to this:
{
  lazyProperty: (value, { models, serializers }) => value.x;
}

This will also require some argument binding in such a way that the first argument is bound to the schema's output.
Distinguishing between properties (lazy, non-lazy) is easy using Function.prototype.length:

An argument length of 0 would be handled as a regular (non-lazy) property (e.g. static properties).
An argument length of 1 would be handled as a regular (non-lazy) property.
An argument length of 2 would be handled as a lazy property.
Other argument length values would throw an error.

Considerations
Method mapping, while in the same ballpark is not as easy to perform, due to methods expecting any number of arguments.
On the same note, lazy methods will remain in their special key indefinitely due to them being impossible to map reasonably. Checking for single argument length and a return type of function is the only idea so far and it won't work due to methods being able to take any number of arguments and return any type, even functions.
Due to the above note, the lazyProperties key should not be deprecated entirely but throw a warning in itself that it's not the best practice any more. This will ensure backwards compatibility and make the API less confusing for beginners.

Update
Implementation has been pushed to v2. As such, this will be a breaking change and will completely deprecate the old API. It's not worth supporting both in the next major version.

Resolved in #22.


Create utility scripts for generating database documentation

Pull Request Test Coverage Report for Build 982499568

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 94.515%

Totals

Change from base Build 975165438:
0.0%

Covered Lines:
1120

Relevant Lines:
1185

💛  - Coveralls


[BB2-896] Responsive Design NodeJS React Sample

JIRA Ticket:
BB2-896
User Story or Bug Summary:

As a 3rd party app, I should be able to understand what to do when I receive certain error messages from BB2 so that I can properly respond to my own users
AC:
Draft documentation for review for:

What to do when receiving a 403 error
What to do when receiving a 404 error
What to do when receiving a 500 error
how to implement exponential backoff

In the Node.JS and Python sample apps add in responsive design to show:

What to do when receiving a 403 error
What to do when receiving a 404 error
What to do when receiving a 500 error
how to implement exponential backoff

What Does This PR Do?

Create a document BB2 API Error Responses & Handling where Blue Button 2.0 API Error Responses (HTTP status codes) and Recommended Error Handling Are Documented, including, among other things, how to retry request upon certain error responses.
Add improved error reporting to the sample app where it is applicable, and implement retry logic (exponential back off) when applicable.

Extra:
Avoid tweaking of the code for native OS run or in Docker run, introduce a shell script to start the sample in native OS or in Docker, make client and server code context aware such that the AUTH2 authentication flow functions when the sample is running in docker or on native OS.

What Should Reviewers Watch For?

Are error responses from API calls handled as instructed by the document?
Are any additional documentation updates needed?
Are there any unhandled and/or untested edge cases you can think of?
Is the retry work as expected?

If you're reviewing this PR, please check these things, in particular:

Review the document on API error responses
Verify the retry logic works (exponential back off)

To facilitate the verification of retry failed requests, an instrumented BB2 server is deployed to sandbox canary:
put below line into your host file on you local machine:
<IP_ADDRESS>	sandbox.bluebutton.cms.gov
then:

create an app on sandbox (or using an existing one)
make sure the url is among the redirect urls: http://server:3001/api/bluebutton/callback/
copy the client_id, client_secret to the sample app server config.ts
start sample app in docker: go to local repo base and run ./start.sh docker

Wait until the server and client components are up and running.
note, a waffle switch "simulate_500_error" is provisioned on sandbox which when "active", will produce a 500 error on fhir request, with error message: "Service temporarily unavailable, try again later, network connection refused".
From client webUI, click button "Authorize" to complete the beneficiary medicare.gov login, and grant access to the app, the corresponding EOB search will hit the simulated 500 network connection error, and the failed EOB request met the criteria for retry.
below is a sample server stdout showing the retry process, the 3rd attempt succeeded (by setting switch "simulate_500_error" to false soon after 2nd retry ...)
server_1  | [2021-11-19T00:16:56.149Z] INFO: [object Object] server_1  | Error message: [ Request failed with status code 500 ] server_1  | response code: 500 server_1  | response text: [object Object] server_1  | Request failed and is retryable, entering retry process... server_1  | wait  5  seconds... server_1  | retry attempts:  1 server_1  | retry error: [ Request failed with status code 500 ] server_1  | response code:  500 server_1  | response data:  { server_1  |   detail: 'Service temporarily unavailable, try again later, network connection refused. ' server_1  | } server_1  | wait  10  seconds... server_1  | retry attempts:  2 server_1  | retry error: [ Request failed with status code 500 ] server_1  | response code:  500 server_1  | response data:  { server_1  |   detail: 'Service temporarily unavailable, try again later, network connection refused. ' server_1  | } server_1  | wait  20  seconds... server_1  | retry attempts:  3 server_1  | retry successful: server_1  | { server_1  |   resourceType: 'Bundle', server_1  |   id: '787094eb-dca9-4af4-9b39-87e040f65417', server_1  |   meta: { lastUpdated: '2021-09-23T13:36:42.530-04:00' }, server_1  |   type: 'searchset', server_1  |   total: 51, server_1  |   link: [ server_1  |     { server_1  |       relation: 'first', server_1  |       url: 'https://sandbox.bluebutton.cms.gov/v2/fhir/ExplanationOfBenefit?_format=appl ication%2Fjson%2Bfhir&startIndex=0&_count=10&patient=-20000000000002' server_1  |     }, server_1  |     { server_1  |       relation: 'next', server_1  |       url: 'https://sandbox.bluebutton.cms.gov/v2/fhir/ExplanationOfBenefit?_format=appl ication%2Fjson%2Bfhir&startIndex=10&_count=10&patient=-20000000000002' server_1  |     }, server_1  |     { server_1  |       relation: 'last', server_1  |       url: 'https://sandbox.bluebutton.cms.gov/v2/fhir/ExplanationOfBenefit?_format=appl ication%2Fjson%2Bfhir&startIndex=50&_count=10&patient=-20000000000002' server_1  |     }, server_1  |     { server_1  |       relation: 'self', server_1  |       url: 'https://sandbox.bluebutton.cms.gov/v2/fhir/ExplanationOfBenefit/?_count=10&_ format=application%2Fjson%2Bfhir&patient=-20000000000002&startIndex=0' server_1  |     } server_1  |   ], server_1  |   entry: [ server_1  |     { resource: [Object] }, server_1  |     { resource: [Object] }, server_1  |     { resource: [Object] }, server_1  |     { resource: [Object] }, server_1  |     { resource: [Object] }, server_1  |     { resource: [Object] }, server_1  |     { resource: [Object] }, server_1  |     { resource: [Object] }, server_1  |     { resource: [Object] }, server_1  |     { resource: [Object] } server_1  |   ] server_1  | } server_1  | config: server_1  | { server_1  |   url: 'https://sandbox.bluebutton.cms.gov/v2/fhir/ExplanationOfBenefit/', server_1  |   method: 'get', server_1  |   headers: { server_1  |     Accept: 'application/json, text/plain, */*', server_1  |     Authorization: 'Bearer k8O6XDxBf2RCLmD0xzAiGKlWvnOcRS', server_1  |     'User-Agent': 'axios/0.21.1' server_1  |   }, server_1  |   params: { server_1  |     code: 'mRpSQkterTO9xzIfXEab6hRCun4ka0', server_1  |     state: 'k6hb1zQg_TnBOsmozJVEyDwFxxLHd2tJrD8Q39WPjzE' server_1  |   }, server_1  |   transformRequest: [ [Function: transformRequest] ], server_1  |   transformResponse: [ [Function: transformResponse] ], server_1  |   timeout: 0, server_1  |   adapter: [Function: httpAdapter], server_1  |   xsrfCookieName: 'XSRF-TOKEN', server_1  |   xsrfHeaderName: 'X-XSRF-TOKEN', server_1  |   maxContentLength: -1, server_1  |   maxBodyLength: -1, server_1  |   validateStatus: [Function: validateStatus], server_1  |   data: undefined server_1  | }
What Security Implications Does This PR Have?
Submitters should complete the following questionnaire:

If the answer to any of the questions below is Yes, then here's a link to the associated Security Impact Assessment (SIA), security checklist, or other similar document in Confluence: N/A.

Does this PR add any new software dependencies? No.
Does this PR modify or invalidate any of our security controls? No.
Does this PR store or transmit data that was not stored or transmitted before? No.

If the answer to any of the questions below is Yes, then please add @StewGoin as a reviewer, and note that this PR should not be merged unless/until he also approves it.

Do you think this PR requires additional review of its security implications for other reasons? No.

What Needs to Be Merged and Deployed Before this PR?

This PR cannot be either merged or deployed until the following pre-requisite changes have been fully deployed:

CMSgov/some_repo#42

Any Migrations?

[ ] Yes, there are migrations

[ ] The migrations should be run PRIOR to the code being deployed
[ ] The migrations should be run AFTER the code is deployed
[ ] There is a more complicated migration plan (downtime, etc)

[x] No migrations

Submitter Checklist

I have gone through and verified that...:

[x] This PR is reasonably limited in scope, to help ensure that:

It doesn't unnecessarily tie a bunch of disparate features, fixes, refactorings, etc. together.
There isn't too much of a burden on reviewers.
Any problems it causes have a small "blast radius".
It'll be easier to rollback if that becomes necessary.

[x] I have named this PR and its branch such that they'll be automatically be linked to the (most) relevant Jira issue, per: https://confluence.atlassian.com/adminjiracloud/integrating-with-development-tools-776636216.html.
[x] This PR includes any required documentation changes, including README updates and changelog / release notes entries.
[x] All new and modified code is appropriately commented, such that the what and why of its design would be reasonably clear to engineers, preferably ones unfamiliar with the project.
[x] All tech debt and/or shortcomings introduced by this PR are detailed in TODO and/or FIXME comments, which include a JIRA ticket ID for any items that require urgent attention.
[x] Reviews are requested from both:

At least two other engineers on this project, at least one of whom is a senior engineer or owns the relevant component(s) here.
Any relevant engineers on other projects (e.g. BFD, SLS, etc.).

[x] Any deviations from the other policies in the DASG Engineering Standards are specifically called out in this PR, above.

Please review the standards every few months to ensure you're familiar with them.
… docker or natively.

@JFU-GIT We really shouldn't be creating new startup scripts. I think the idea of using docker was that it was platform agnostic. Now adding in the shell scripts makes it less so. I think we are just going to have to work with what is there, or somehow integrate it into the docker setup. I think this PR shouldn't change any of that though.

@JFU-GIT We really shouldn't be creating new startup scripts. I think the idea of using docker was that it was platform agnostic. Now adding in the shell scripts makes it less so. I think we are just going to have to work with what is there, or somehow integrate it into the docker setup. I think this PR shouldn't change any of that though.

understand the point, but sometime start script reduce the manual steps...

@JFU-GIT Reminder that this also has to be done for the python app as well

@nbragdon @dtisza1 rebased and retested plus some final touches on error handling - server logs error with code + details, while client got generic message on failed auth or failed fhir query.

@nbragdon @dtisza1 addressed feedbacks in the last commit, also deployed a sbx canary with instrumented BB2:
put below in hosts if want to test retry:
<IP_ADDRESS> sandbox.bluebutton.cms.gov


Assign acronyms to the mappool

Is your feature request related to a problem? Please describe.
Sometimes the referee might not know which map is which and most players type for example "pick NM5" but to the referee it's displayed as a map name. Yes, you can add the mappool IDs in order but it would definitely make it easier. This will also help to reduce the size of the referee settings and fit smaller screens better.
Describe the solution you'd like
Currently the mappool editor looks like this. It would be nice to have a acronym part there which could be text shown in the referee settings to avoid less confusion.
The acronym can also help reduce the width of the entire section by making the mod-pools to square selections. Quick concept. Left click for red pick and Right click for blue click. Hold shift to ban instead. Ctrl to reset.
These squares can obviously be smaller so the entire parts width can be reduced.
Describe alternatives you've considered
Separate mappool to a different sidebar.

Mod acronyms are actually a thing already:

When you have entered a mod acronym for the mod bracket(s), it'll recognize  (NM1/HD3/FM4/etc.) being typed in chat and it'll be clickable like so:

As for changing the sidebar, will probably change it to look somewhat like your concept but with a ban/change picked by button attached to it


Add a dependency to the cq-content bundle

Add a dependency to the cq-content bundle as to make sure the primary… types are available before actually installing this bundle
fixes #1110

Changes Unknown when pulling ad0c2ec9407876a6aad2013ecf6b8f8bfee7f9fb on royteeuwen:defect/content/set-dependency-on-cq-content into ** on Adobe-Consulting-Services:master**.

This would limit installation to 6.3 and above. I don't think that's desired.
@davidjgonzalez are we good to limit installation to 6.2 and above?

Perfect, would have gladly done it myself @justinedelson ! I was just starting up an AEM 6.2 to see which version was needed :)


Cannot use the package with Avalonia Cross Platform Project

Steps to reproduce

Create a cross platform avalonia project.
Run it.

Expected behavior
The projects runs.
Actual behavior
An exception is thrown.

Crashlog
System.NotImplementedException
HResult=0x80004001
Message=This functionality is not implemented in the portable version of this assembly.  You should reference the NuGet package from your main application project in order to reference the platform-specific implementation.
Source=Plugin.BLE
StackTrace:
at Plugin.BLE.CrossBluetoothLE.get_Current()
at Smart.Galaxy.Star.App.ViewModels.MainViewModel..ctor() in Y:\repos\Smart.Galaxy.Star.App\Smart.Galaxy.Star.App\ViewModels\MainViewModel.cs:line 16
at Smart.Galaxy.Star.App.App.OnFrameworkInitializationCompleted() in Y:\repos\Smart.Galaxy.Star.App\Smart.Galaxy.Star.App\App.axaml.cs:line 21
at Avalonia.AppBuilder.SetupUnsafe()
at Avalonia.AppBuilder.Setup()
at Avalonia.AppBuilder.SetupWithLifetime(IApplicationLifetime lifetime)
at Avalonia.ClassicDesktopStyleApplicationLifetimeExtensions.StartWithClassicDesktopLifetime(AppBuilder builder, String[] args, Action`1 lifetimeBuilder)
at Smart.Galaxy.Star.App.Desktop.Program.Main(String[] args) in Y:\repos\Smart.Galaxy.Star.App\Smart.Galaxy.Star.App.Desktop\Program.cs:line 15
Configuration
Version of the Plugin: 3.1.0-beta.3
Platform: Windows 11 22635.3420

there's support for Avalonia ?

Hm, I'm not very familiar with Avalonia. I guess the most important question is: Which .NET target framework are you using? And maybe: Which Avalonia version?

I'm using the latest stable version(11.0.10) of Avalonia.
I created the solution using their extension.
All the created projects use .NET 8 as their target:

I'm using the latest stable version(11.0.10) of Avalonia. I created the solution using their extension.
All the created projects use .NET 8 as their target:

Thanks for the info. I created a solution from the Avalonia template myself by now (on MacOS using VSCode with the "Avalonia for VSCode" extension).
I assume the .Android and .iOS projects should work well with Plugin.BLE, since they target net8.0-android and net8.0-ios, respectively. I haven't actually tried it, though.
The .Desktop project, however, which you apparently tried to run on Windows, is probably not working because it uses
    <OutputType>WinExe</OutputType>
    <TargetFramework>net8.0</TargetFramework>

The .Desktop project template also includes this comment:
    <!--If you are willing to use Windows/MacOS native APIs you will need to create 3 projects.
    One for Windows with net8.0-windows TFM, one for MacOS with net8.0-macos and one with net8.0 TFM for Linux.-->

If you follow this advice and use a project with target framework net8.0-windows, I assume that this should work with Plugin.BLE on Windows. (Same for MacOS. Linux is currently not supported by Plugin.BLE.)
Could you try that and let us know whether you got it to work?

Yes, it does work, I had to also select the Target OS version for it to work.
Thank you for your help!

Yes, it does work

Awesome, thanks for the feedback. I guess we can close this issue then.

Thank you for your help!

You're welcome :)


Fix: error C2360: initialization of 't' is skipped by 'case' label

Situation:
case ExampleGameState::update:
        /////////////////////////////
        // Add your codes below...like....
        //
        // UpdateJoyStick();
        // UpdatePlayer();
        // UpdatePhysics();
        // ...
        int t = 10;
        break;

THIS PROJECT IS IN DEVELOPMENT MODE. Any pull requests should merge to branch dev, otherwise will be rejected immediately.
Describe your changes
add brakets on each case <nn>:
Issue ticket number and link
Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[x] I have checked readme and add important infos to this PR (if it needed).
[ ] I have added/adapted some tests too.

ready for merge


base graph url config

There should be an option to configure the base graph url for graphs that are automatically created by ldspdi (the ontology graph for instance), so that Dila can have the automated graph accessible on their own /graph/ endpoint

base graph uris are defined here: https://github.com/buda-base/owl-schema/blob/master/ont-policy.rdf
More specifically: see https://github.com/buda-base/owl-schema/blob/master/ont-policy.rdf#L54 for the default ontologyGraph full URI.
Other base uris are defined in the publicUri property of each OntologySpec object (for instance, see https://github.com/buda-base/owl-schema/blob/master/ont-policy.rdf#L63 )
All this data is loaded at ldspdi startup and each time a push occurs in the owl-schema github repo.

ok yes... hmm... let's not mess with that now, it should still be accessible through the a good old query...


I get error

Hi,
Thanks for your app. I get an error when I try to use it.
Pablo
xx@MacBook-Pro ~ % tidal-wave --audio-format 'HiRes'  https://tidal.com/browse/playlist/70bcff2a-ec53-4956-b349-267d9a0cf116
2024-01-18:14:45:14,965 INFO     [models.py:621] TIDAL playlist ID parsed from input: 70bcff2a-ec53-4956-b349-267d9a0cf116
For which of Android [a] or Windows [w] would you like to provide an API token?: w
2024-01-18:14:45:17,876 INFO     [requesting.py:89] Requesting from TIDAL API: playlists/70bcff2a-ec53-4956-b349-267d9a0cf116
2024-01-18:14:45:18,132 INFO     [playlist.py:351] Requesting from TIDAL API: playlists/70bcff2a-ec53-4956-b349-267d9a0cf116/items
2024-01-18:14:45:18,398 INFO     [requesting.py:89] Requesting from TIDAL API: albums/3489559
2024-01-18:14:45:18,465 INFO     [requesting.py:89] Requesting from TIDAL API: tracks/10827167/credits
2024-01-18:14:45:18,531 INFO     [requesting.py:89] Requesting from TIDAL API: tracks/10827167/playbackinfopostpaywall
Traceback (most recent call last):
File "/opt/homebrew/bin/tidal-wave", line 8, in
sys.exit(app())
^^^^^
File "/opt/homebrew/lib/python3.11/site-packages/tidal_wave/main.py", line 116, in main
playlist.get(
File "/opt/homebrew/lib/python3.11/site-packages/tidal_wave/playlist.py", line 317, in get
_get_items = self.get_items(session, audio_format)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/lib/python3.11/site-packages/tidal_wave/playlist.py", line 105, in get_items
track.get(
File "/opt/homebrew/lib/python3.11/site-packages/tidal_wave/track.py", line 519, in get
self.set_manifest()
File "/opt/homebrew/lib/python3.11/site-packages/tidal_wave/track.py", line 87, in set_manifest
self.manifest: Manifest = manifester(self.stream)
^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/lib/python3.11/site-packages/tidal_wave/dash.py", line 137, in manifester
raise TidalManifestException(
tidal_wave.dash.TidalManifestException: Manifest for track 10827167, audio mode STEREO is encrypted

Hi!, I got the token using Charles (in macOS). For the other part, I have the permission to download tracks (on the tidal-dl I can download tracks). maybe the issue is that the tracks are MQA?
thanks in advance,
Pablo

@pablo-reyes-cabrera at the moment, the program doesn’t work with credentials from macOS. But, similar to tidal-dl, you can get tracks from a spoofed Fire TV if you use --audio-format mqa instead of --audio-format hires


Add iamjoe24's file

created a branch, created a file and made a commit, and opened a pull request


tvOS: Performance issues and delays in parallax effects with list of focusables

Description
In tvOS focus navigation is based on scale change on focus/blur. Due to touchpad navigation in tvOS scaling after on focus callback is creating a visible delay in scale and its clearly visible when we do fast swipes in touch pad
React Native version:
0.63.1-4
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Flatlist with list of touchables which scales on focus
Do a fast swipe

Expected Results
Scaling should be smooth similar to opacity change
Proposal
Can we add a new TouchbleScale similar to TouchableOpacity which changes scale factor before calling focus in the framework

The scale change actually happens as part of the native tvOS view code, specifically in React/Views/RCTTVView.m:
- (void)didUpdateFocusInContext:(UIFocusUpdateContext *)context
       withAnimationCoordinator:(UIFocusAnimationCoordinator *)coordinator
{
  if (context.previouslyFocusedView == context.nextFocusedView) {
    return;
  }
  if (context.nextFocusedView == self && self.isTVSelectable ) {
    [self becomeFirstResponder];
    [coordinator addCoordinatedAnimations:^(void){
      [self addParallaxMotionEffects];
      [self sendFocusNotification:context];
    } completion:^(void){}];
  } else {
    [coordinator addCoordinatedAnimations:^(void){
      [self sendBlurNotification:context];
      [self removeParallaxMotionEffects];
    } completion:^(void){}];
    [self resignFirstResponder];
  }
}

One thing you could try is to move the calls to [self sendFocusNotification:context] and [self sendBlurNotification:context] to their respective completion handlers, and see if that improves the behavior.

@dlowder-salesforce thanks for the answer. But for android parallax effect will not work.
We should have a common solution for scale as this is what mostly used in TV's
I can create a PR for the same if it is ok?

Yes it would be great if you can create a separate issue or PR for adding parallax effects to Android.  Let's keep this issue for fixing the performance issues with tvOS.

@prakashjais99  Have you fully optimized the FlatList component, with getItemLayout and windowSize, numItemsToRender, and the actual ListItems as PureComponents.
I noticed a huge change in performance after doing as much optimizing as I could do. I still have slight hiccups if the lists are gigantic like 300 items though.

@prakashjais99  Have you fully optimized the FlatList component, with getItemLayout and windowSize, numItemsToRender, and the actual ListItems as PureComponents.
I noticed a huge change in performance after doing as much optimizing as I could do. I still have slight hiccups if the lists are gigantic like 300 items though.


Patch minimatch to fix CVE-2022-3517

Upgrade minimatch to the earliest version where CVE-2022-3517, a high severity issue (7.5/10) was fixed. https://nvd.nist.gov/vuln/detail/CVE-2022-3517

What happend to this PR?

@forefrontmartingrantz it was merged back in september

@swimmadude66 I see the changes in the repo, but I can't see it being released to npm :(

@forefrontmartingrantz I apologize for the long wait! There was a build issue which apparently stumped me on initial merging of this PR, but I was just able to allocate some time to fixing it and releasing the fix included in the PR.
v1.0.4 should be available now and include the version bump for minimatch. Hopefully this fix should also reduce my turnaround times on any upcoming change requests.


fix TypeError in views.py

Fix bug, that I opened in https://github.com/st4lk/django-rest-social-auth/issues/144

Hey @sputnik5459
Thanks for the fix!


wrong offsets

sorry if you're working on it right now, but offsets are still wrong even though it has been updated

Be more specific please... Which ones? Have you done debugging, etc?

Be more specific please... Which ones? Have you done debugging, etc?

GlobalVars not working 4 me

i cant manage to fix correct timing and view angles. guessing about dwViewMatrix dwViewAngles dwGlobalVars. Also did bones structure changed or no? My code after cs update all bones stucked in one place...

我无法设法修复正确的时间和视角。猜测 dwViewMatrix dwViewAngles dwGlobalVars。骨骼结构是否也发生了变化？我的代码在 cs 更新后，所有骨骼都卡在一个地方……

ME too

Be more specific please... Which ones? Have you done debugging, etc?

GlobalVarsBase and bone offsets are wrong.

same with view angles

The offsets are correct, the structures have just changed it seems.

cs2 updated again @a2x

same with view angles

can u fixd ？ icanot

你能修复吗？ icanot


Add option to change subscription quantity

In combination with #56, this will add functionality to manage subscription quantity.

Copy Subscription.php to your project (into app/Overrides/ for instance), then add this to composer.json
"psr-4": {
        ...
            "LemonSqueezy\\Laravel\\": "app/Overrides/"
        },
        "exclude-from-classmap": [
            "vendor/lemonsqueezy/laravel/src/Checkout.php",
            "vendor/lemonsqueezy/laravel/src/Subscription.php"
        ]
}

This looks quite helpful, my only suggestion would be to add the ability to pass through options to invoice immediately and to prorate. However, looking at the Lemon Squeezy API, it seems there's no actual way to do this?

Any plans to merge this pull request? Would love to see that feature and it is also on the roadmap.

I really want to get metered billing into the package but struggling to find the time atm. In any case I plan to work on this package this fall still so please bear with me.


update API doesn't check minimumWaitDuration

https://developers.google.com/safe-browsing/v4/request-frequency#minimum-wait-duration
According to the spec,

Both the fullHashes.find response and threatListUpdates.fetch response have a minimumWaitDuration field that clients must obey.

If a lot of clients are sending requests and the server has to call excessive api.HashLookup(), will the server result in receiving a response with minimumWaitDuration?
I think the server should check if the response contain minimumWaitDuration.
will sending excessive  "fullHashes.find" cause receiving minimumWaitDuration in response?

@alexwoz. This is a known issue that the code currently doesn't respect the minimum wait duration.

I believe this issue can be closed now that #49 has merged.


check passwd for import private key

Good point about checking, but it's not a good idea to encrypt again for it.


Update favicon

Hey @kaja-osojnik, based on https://app.clickup.com/t/8694b43ju we need to align favicon across apps

FYI for docs.oasis.io I prepared a favicon which supports theming (appears blue on white themes and white on dark themes): https://github.com/oasisprotocol/docs/blob/main/static/img/favicon.svg
Maybe we should use this instead?

Forwarding your question to @don as I am not in charge of design guidelines.

FYI for docs.oasis.io I prepared a favicon which supports theming (appears blue on white themes and white on dark themes): https://github.com/oasisprotocol/docs/blob/main/static/img/favicon.svg
Maybe we should use this instead?


Cluster ready count not updating in git repo when I move cluster to new workspace

Steps:

Create a git repo and target one of your clusters
Wait for it to complete
Move your cluster to another workspace

Results:  Clusters Ready count on Git Repos list page not updating.  Updates on workspaces & Cluster group list pages.

going to fleet -> Clusters (list) -> hit 3 dots on the cluster item -> Choose assign to -> Select another workspace
Request seems to go down fine:
Request URL: https://localhost:8005/v3/clusters/c-m-l8bdcq5f
Request Method: PUT
Status Code: 200 OK

Interface does not update automatically nor, after refresh, we see the move of the cluster assignment to another workspace, so the feature itself is not working at all.
Since a request is done successfully, the problem could be on the BE side, although I don't have the experience to check if the information that we send on the payload from the FE is correct or not.
Also to highlight the fact that the shouldn't be allowed to move the **local ** cluster to another workspace, which the UI allows for. That can create unforeseen problems and, imo, doesn't seem to add up.
So, to sum it up, 2 issues:

Doing "assign to" doesn't work
User shouldn't be able to move the "local" cluster to another workspace

Missing here a bit more knowledge to move on @nwmac . How to proceed here?

Need further information. Thread here: https://suse.slack.com/archives/C02DG8ZUALR/p1645183585238339

In case anything happens to Slack again, this ties to a previous question in https://github.com/rancher/rancher/issues/36132.
For those without Slack access, there's information that the "fleetWorkspaceName" parameter on the v3 Cluster is the correct field here: https://github.com/rancher/rancher/blob/release/v2.6/pkg/apis/management.cattle.io/v3/cluster_types.go#L140
@aalves08 do we need 36132 acted on to unblock this? or what does the backend have to work on to help us?

@gaktive in order to reproduce this issue and also https://github.com/rancher/dashboard/issues/4802 we need this feature to work again.
I believe that the backend needs to tackle what is specified on https://github.com/rancher/rancher/issues/36132  by @richard-cox in order to enable the feature again.

Backend work pushed to 2.6.5. If that tracks with what's expected with the UI, then we'll push this out accordingly. @aalves08 update here if that's not the case.

@aalves08 Is this issue still relevant, or can it be closed?

Tbh @catherineluse I think this is stale for a long time and we might close it since I don't see any action from the BE team for long time... @gaktive what do you think?

As long as the counts are validated as part of https://github.com/rancher/rancher/issues/36132 this can be closed

Closing for now. The onus will be then for the backend to reopen this (or file a new ticket) once they're in a state to work on this.


Multiline block layout widget (Wrap)

The current Flutter flex layout does not allow for handling overflow of child widgets.
There are some situations where you would want the widgets to flow the next line (wrap) instead of being cut off.
In the HTML Flexbox world, this would be the value for  flex-wrap.

@Hixie Bump :)

I think we should implement this as a new layout algorithm with the following features:

It has a list of children.
It has an axis.
It only works in main-axis unbounded environments.
For each child, during layout, it lays the child out with loose main-axis constraints with the incoming max main axis constraint and with unbounded vertical constraints.
In the cross axis, children are aligned according to a cross axis alignment.
In the main axis, children are laid out one after the other in a given direction (ltr/ttb or rtl/btt). Each time one doesn't fit, a new line is started. Lines are stacked adjacent to each other and are as high as needed to accommodate that line's children with the given cross-axis alignment.
Children can have, in their parent data, an explicit minwidth specified. If the remaining space isn't sufficient for that minwidth, a new line is started. If a child has a minwidth, the child is given tight constraints of the remaining space on whatever line they're on.

(The latter bullet point is intended to handle the "text field after a bunch of chips" use case)

The main axis is the reading axis, horizontal for the screenshot above. The cross axis is the axis in which the children wrap, the axis in which new lines are placed.

I believe @abarth did this.

Yes.

hi everyone, is this feature ready yet and how the code will look like?

@sandangel I guess this is about https://docs.flutter.io/flutter/widgets/Wrap-class.html

I dont sure, but you wanna used a Wrap widget? See it in official flutter channel. Maybe it will be help you


Fix Line Overflow in LaTeX templates

Sometimes, if a line is too long it can overflow. Some cases that trigger it:

Very long given name
Very long university name
Lots of skills in a category

The templates that are most affected by it are:

Deedy
Plush
Simple

@IvanIsCoding I'd like to take this one.
Can you please add some screenshots of this issue?

@karankhatavkar yes, the issue is open. I don’t have screenshots but it is not very hard to trigger.
If you use the example JSON (https://github.com/IvanIsCoding/ResuLLMe/blob/main/.github/Turing.json) and replace the university name for something longer e.g. “University of Illinois at Urbana-Champaign” it should trigger it


chore: Update grid nav internal API and include bugfixes

Description
Updated internal grid-navigation util API to use different properties for feature activation and elements suppression.
Fixed a bug in the grid-navigation util allowing to make programmatically focusable content elements user focusable.
How has this been tested?
New unit tests

Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness

Changes include appropriate documentation updates.
Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
Changes do not include unsupported browser features, see CONTRIBUTING.md.
Changes were manually tested for accessibility, see accessibility guidelines.

Security

If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

Changes are covered with new/existing unit tests?
Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Sorry it took a little while!

No worries and many thanks!


Optimize ShEx for EXTRA predicates with non-repeated properties

A common pattern for Shape expressions is:
<S> EXTRA <p> {
 <p> @<T> {min,max},
 ... // other definitions without mentioning <p>
}

The meaning is that we expect between min and max values of property <p> with shape <T> and we don't give any further constraint on the rest of values of property <p>.
Currently, this pattern is checked using a regular expression like: C0{min,max}, C1* where C0 represents the <p> @<T> constraint and C1 represents the <p> NOT @<T> constraint which is very inefficient and can raise stack overflow exceptions as in issue #130
An optimization to validate shapes following this pattern is to count the number of values with property <p> that conform to shape <T> and check that it is between min and max.

The optimization has been implemented and tested. Further optimizations can be done but will have their own issues.


styles: adjust tailwind css & supports theme

Adjust tailwind css
Supports theme
remove postcss repeated config

@murrayee are you trying to get into the contributor role for tea? @Xercesblu3 please add him thanks.

@murrayee are you trying to get into the contributor role for tea? @Xercesblu3 please add him thanks.

Wow, would love to join！


Revenants sometime respawn out in deep space.

Description
Sometimes when a revenant is killed they respawn out in deep space on a different map level.
Reproduction
Had a revenant in an extended round die and respawn out in space, not sure how to replicate.
Additional context
This was during a very long extended round. Station was moved quite a bit away from its starting location. not sure if this was the cause.

pretty sure this is due to how polymorphing doesn't dispose of the old entity when destroyed. Will require some changes to how that stuff works.


Fix threshold regex for equality expressions

This PR improves the retrieval of alert thresholds with the expressions <= > = =.
Btw, I upgraded jsdom to newest version so contextify is no longer downloaded as dependency (the requirement for installed g++ was very painful)
I created .travis.yml so you should enable automatic builds :)

That's very cool! I'll try to test it and merge ASAP.


python311Packages.transformers: 4.35.0 -> 4.35.1

Description of changes
Changelog: https://github.com/huggingface/transformers/releases/tag/v4.35.1
cc @pashashocky @happysalada

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 267479 run on x86_64-linux 1

2 packages marked as broken and skipped:

python310Packages.unstructured-inference
python310Packages.unstructured-inference.dist

106 packages built:

khoj
khoj.dist
libretranslate (python311Packages.libretranslate)
libretranslate.dist (python311Packages.libretranslate.dist)
openai-whisper (python311Packages.openai-whisper)
openai-whisper.dist (python311Packages.openai-whisper.dist)
python310Packages.accelerate
python310Packages.accelerate.dist
python310Packages.argos-translate-files
python310Packages.argos-translate-files.dist
python310Packages.argostranslate
python310Packages.argostranslate.dist
python310Packages.ctranslate2
python310Packages.ctranslate2.dist
python310Packages.dalle-mini
python310Packages.dalle-mini.dist
python310Packages.farm-haystack
python310Packages.farm-haystack.dist
python310Packages.faster-whisper
python310Packages.faster-whisper.dist
python310Packages.gradio
python310Packages.gradio.dist
python310Packages.k-diffusion
python310Packages.k-diffusion.dist
python310Packages.libretranslate
python310Packages.libretranslate.dist
python310Packages.manifest-ml
python310Packages.manifest-ml.dist
python310Packages.minichain
python310Packages.minichain.dist
python310Packages.openai-whisper
python310Packages.openai-whisper.dist
python310Packages.openllm
python310Packages.openllm.dist
python310Packages.optimum
python310Packages.optimum.dist
python310Packages.peft
python310Packages.peft.dist
python310Packages.sentence-transformers
python310Packages.sentence-transformers.dist
python310Packages.shap
python310Packages.shap.dist
python310Packages.spacy-transformers
python310Packages.spacy-transformers.dist
python310Packages.stanza
python310Packages.stanza.dist
python310Packages.torchinfo
python310Packages.torchinfo.dist
python310Packages.transformers
python310Packages.transformers.dist
python310Packages.translatehtml
python310Packages.translatehtml.dist
python310Packages.txtai
python310Packages.txtai.dist
python310Packages.vqgan-jax
python310Packages.vqgan-jax.dist
python311Packages.accelerate
python311Packages.accelerate.dist
python311Packages.argos-translate-files
python311Packages.argos-translate-files.dist
python311Packages.argostranslate
python311Packages.argostranslate.dist
python311Packages.ctranslate2
python311Packages.ctranslate2.dist
python311Packages.dalle-mini
python311Packages.dalle-mini.dist
python311Packages.farm-haystack
python311Packages.farm-haystack.dist
python311Packages.faster-whisper
python311Packages.faster-whisper.dist
python311Packages.gradio
python311Packages.gradio.dist
python311Packages.k-diffusion
python311Packages.k-diffusion.dist
python311Packages.manifest-ml
python311Packages.manifest-ml.dist
python311Packages.openllm
python311Packages.openllm.dist
python311Packages.optimum
python311Packages.optimum.dist
python311Packages.peft
python311Packages.peft.dist
python311Packages.sentence-transformers
python311Packages.sentence-transformers.dist
python311Packages.shap
python311Packages.shap.dist
python311Packages.spacy-transformers
python311Packages.spacy-transformers.dist
python311Packages.stanza
python311Packages.stanza.dist
python311Packages.torchinfo
python311Packages.torchinfo.dist
python311Packages.transformers
python311Packages.transformers.dist
python311Packages.translatehtml
python311Packages.translatehtml.dist
python311Packages.txtai
python311Packages.txtai.dist
python311Packages.vqgan-jax
python311Packages.vqgan-jax.dist
tts
tts.dist
whisper-ctranslate2
whisper-ctranslate2.dist
wyoming-faster-whisper
wyoming-faster-whisper.dist


Addiontal let user select part of photo which one will be profile photo

Container(
                  width: 150,
                  height: 150,
                  decoration: BoxDecoration(
                    shape: BoxShape.circle,
                    color: Colors.white,
                    image: DecorationImage(
                      fit: BoxFit.fill,
                      image: FileImage(photo!),
                    ),
                  ),
                ),

use CircleAvatar

lib/utilites/crop_image/crop_image.dart  ---> where is function
lib/view/app/account/editprofile/view/edit_profile_view.dart ---> where is used
https://pub.dev/packages/image_cropper ---> package
helpful sources
https://www.youtube.com/watch?v=nIMfayjbE4k


sample on raf

samle the returning DOM stream with RAF from main thread.
This is to avoid DOM updates queuing up, when the window is idle, and replaying upon focus.

@MariusKazlauskas @michalvankodev please review if you have a moment


Add RpcClient::connect_with_port() to directly connect to an epmdless node

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 46.135%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
1522

Relevant Lines:
3299

💛  - Coveralls


fail to implement npm on nodejs

followed the example but failed to use dilithium, is there any nodejs example of the implementation?
Error [ERR_REQUIRE_ESM]: require() of ES Module<EMAIL_ADDRESS>from /home/tconrado/genomica/privacy-relay/dist/main.js not supported.
Instead change the require of sign.js in xxxxxxxxxx/dist/main.js to a dynamic import() which is available in all CommonJS modules.
at Object. (xxxxxxxxxxx/dist/main.js:7:36) {
code: 'ERR_REQUIRE_ESM'
}

Hello thank your the support, very helpfull!
Due the use of NestJS it was necessary to make a dynamic import following NestJS ESM import
specifically had to create 2 constants as it returned a premise as follow:
import { Injectable } from '@nestjs/common';
import assert from 'node:assert/strict'
@Injectable()
export class DC5Service {
    async dc5Sign() {
        const signBuilder = (await import('@dashlane/pqc-sign-dilithium5-node') ).default;
        const sign = await signBuilder();
        const message = new Uint8Array([0x44, 0x61, 0x73, 0x68, 0x6c, 0x61, 0x6e, 0x65]);
        const { publicKey, privateKey } = await sign.keypair();
        const { signature } = await sign.sign(message, privateKey);
        const validSignature = await sign.verify(signature, message, publicKey);
        console.log(validSignature)
        assert(validSignature === true);
    }
}


mdc/typography doesn't set new font styles for 5.0.5

When trying to customize the typography or change the font, changing the variables as seen in the example doesn't seem to work.
Code
use '@material/typography/mdc-typography';
use '@material/typography';
$mdc-typography-styles-headline1: (   font-family: unquote("Raleway"),   font-size: 97 );
$mdc-typography-styles-headline2: (   font-family: unquote("Raleway"),   font-size: 61 );
These don't change the aforementioned typing styles to font-family, Raleway.

Hi @PabloG6 thanks for reporting this. A fix was merged in MDC upstream repo yesterday, I'll see how best to incorporate the change. Let ya know.
reference https://github.com/material-components/material-components-web/pull/5643

@PabloG6 Preparing to publish v5.1.0 with upstream fix.

@PabloG6 After upgrading to v5.1.0, use MDC guide for overriding styles.
https://github.com/material-components/material-components-web/tree/master/packages/mdc-typography#overriding-styles

Closed by #2134


Feature Request: Optional exporting query param type and making the $path more type safe

Hey,
I am using remix-routes in my project and it's helpful, but I find a problem with query param typing.
So my whole idea is the following:
// routes/search.tsx

const Page = () => {

}

export type TQuerySearch = {
  productId?: string;
  category?: string;
}

export default Page

// some other file
$path("/search", {
  productId: "okay",
  categoryId: "no okay" // Dude it's an error
})

I can help developing it.

Sounds like a good idea. One thing I'm concerning is what we should name the type. I'd like to propose SearchParams.

The name sounds good to me, can I get the task and complete it? I will get it ready by Sunday.

@HamadTheIronside Yes, take your time.

A question comes to my mind, how can we write type for query strings like ?view=gird&sort=price&sort=size?

A question comes to my mind, how can we write type for query strings like ?view=gird&sort=price&sort=size?

NVM, we can define a type in this way:
export type SearchParams = [
    ['view', 'list' | 'grid'],
    ['sort', 'price' | 'brand'],
];

For ?view=gird&id=1&id=2:
export type SearchParams = [
    ['view', 'list' | 'grid'],
    ...Array<['id', number]>
]

For ?view=gird&id=1&id=2:
export type SearchParams = [
    ['view', 'list' | 'grid'],
    ...Array<['id', number]>
]

What about?
export type SearchParams = [
    ['view', 'list' | 'grid'],
    ['id', number[]]
]

What about?
export type SearchParams = [
    ['view', 'list' | 'grid'],
    ['id', number[]]
]

It won't work, see Playground Link

What about?
export type SearchParams = [
    ['view', 'list' | 'grid'],
    ['id', number[]]
]

It won't work, see Playground Link

I was thinking more like [['view', 'grid'], ['id', [1, 2]]]. but thinking more, you are right. let me test more.

BTW, any Idea about how to extract the type from the file without using external libraries?

A rough idea is directly to import the type from the page file.
export declare function $path(
  route: \\"/\\",
  query?: import('../app/routes/index').SearchParams | URLSearchParams
): string;

BTW, any Idea about how to extract the type from the file without using external libraries?

A rough idea is directly to import the type from the page file.
export declare function $path(
  route: \\"/\\",
  query?: import('../app/routes/index').SearchParams | URLSearchParams
): string;

Oh, didn't know if we can do this, won't we encounter some absolute/relative import errors?
By the way, I was thinking what if the param is required, I have a case in my project but I don't know if it's valid to have a required query param, what do you think?

Oh, didn't know if we can do this, won't we encounter some absolute/relative import errors?

We can ensure remix-routes.d.ts is located in project/node_modules/remix-routes.d.ts so it's safe to use relative import here. One thing we need to do is to check whether the type is defined in the page file.

By the way, I was thinking what if the param is required, I have a case in my project but I don't know if it's valid to have a required query param, what do you think?

If the search params type is defined in the page file then the query param will be required, otherwise, it's optional.


[FLINK-34732][cdc][ci] Add document dead link check for Flink CDC Documentation

…

@leonardBang @PatrickRen First ,I add this ci and quick fix some dead link. Some dead link maybe cannot fix currently.

@leonardBang @PatrickRen First ,I add this ci and quick fix some dead link. Some dead link maybe cannot fix currently.
The link like under: [✖] https://repo1.maven.org/maven2/org/apache/flink/flink-cdc-pipeline-connector-mysql/3.0.0/flink-cdc-pipeline-connector-mysql-3.0.0.jar [✖] https://repo1.maven.org/maven2/org/apache/flink/flink-cdc-pipeline-connector-starrocks/3.0.0/flink-cdc-pipeline-connector-starrocks-3.0.0.jar

Could we use /com/ververica patch to make the url works?

@PatrickRen Rebased to master , PTAL


VerneMQ ARM64 support

VerneMQ Makefile breaks at eleveldb compile stage when building for arm64 CPU architecture.
It is critical at that moment to know if there are plans for arm64 support.
I know about the issue #461, it was closed on Oct 20, 2017 without positive output.

Plans (promises) is a broad word, so...
Plans in as we'll go ahead and fix #461 or just work on this without outside help: not immediately.
Agreeing that it'd be nice to have full ARM64 support: ACK.
There are potentially multiple options in how to fix (e)leveldb on ARM, I don't recall what the core issue is at the moment. Let me know when you feel like helping on this and explore more.
Incidentally, I have a POC completely switching LevelDB with RocksDB backend or Leveled (not LevelDB) backend working on aarch64. It will take a while to release this.

I can take a shot at ARM fixes for eleveldb, no promises to to it quick but i have a personal project where i'll need this.

Thanks much for reply.
I've tried to fix this issue by myself.
Firstly, there was an issue with snappy configuration.
After manually setup without use of snappy -> ./config.guess.
I stuck with level_db -> c_src/leveldb/atomic_pointer.h.
There is a support on several old CPU architectures, like this line of code:
#elif defined(__ARMEL__)

For supported architectures there are two ways to implement AtomicPointer class:
With kernel support, like this:
  (*(LinuxKernelMemoryBarrierFunc)0xffff0fa0)();

or with compiler support with cstdatomic header.
It's obvious, that 0xffff0fa0 is a 32 bit address and is incorrect for ARM64 architecture.
If someone could figure this out, there could be a simple solution.
I also learned, that this is the only issue with compiling the project.

@NikolayVasilyev thanks, that's valuable information. (not that I immediately know what to do with it, but maybe we can research on how others have handled similar porting of 32bit ARM C-code to 64)

@NikolayVasilyev if this still interests you, have some alpha support for building Verne with RocksDB here: https://github.com/ioolkos/vernemq/tree/rocksdb-messagestore/apps/vmq_generic_msg_store
This should build on ARM 64.
Will continue working on it.

In case it's useful for someone, here's a Dockerfile that works.  (Note the "ugly hack" and "ugly hack 2" in the middle.)
FROM erlang:slim
RUN apt-get update &&
apt-get -y install bash procps openssl iproute2 curl jq &&
apt-get -y install build-essential git gnupg2 libssl-dev &&
addgroup --gid 10000 vernemq &&
adduser --uid 10000 --system --ingroup vernemq --home /vernemq --disabled-password vernemq
Defaults
ENV DOCKER_VERNEMQ_KUBERNETES_LABEL_SELECTOR="app=vernemq"
DOCKER_VERNEMQ_LOG__CONSOLE=console
PATH="/vernemq/bin:$PATH"
VERNEMQ_VERSION="1.10.1"
RUN git clone --depth 1 --branch $VERNEMQ_VERSION https://github.com/erlio/vernemq.git vernemq-src
WORKDIR /vernemq-src
ugly hack
RUN make rpi32 || true
WORKDIR /vernemq-src/_build/rpi32/lib/eleveldb/c_src
RUN rm -rf snappy-1.0.4 && tar -xzf snappy-1.0.4.tar.gz
COPY files/config.guess snappy-1.0.4/config.guess
COPY files/config.sub snappy-1.0.4/config.sub
RUN tar cfvz snappy-1.0.4.tar.gz snappy-1.0.4 && rm -rf snappy-1.0.4
WORKDIR /vernemq-src
ugly hack 2
RUN make rpi32 || true
WORKDIR /vernemq-src/_build/rpi32/lib/eleveldb/c_src/leveldb
RUN rm build_config.mk &&
sed -i'' -e 's/cstdatomic/atomic/' build_detect_platform port/atomic_pointer.h &&
sed -i'' -e 's/.*moved below/#include /' port/atomic_pointer.h
WORKDIR /vernemq-src
RUN make rpi32 &&
mv -v _build/rpi32/rel/vernemq/* /vernemq/
WORKDIR /vernemq
RUN rm -rf /vernemq-src /root/.cache/rebar3
COPY --chown=10000:10000 bin/vernemq.sh /usr/sbin/start_vernemq
COPY --chown=10000:10000 files/vm.args /vernemq/etc/vm.args
RUN chown -R 10000:10000 /vernemq &&
ln -s /vernemq/etc /etc/vernemq &&
ln -s /vernemq/data /var/lib/vernemq &&
ln -s /vernemq/log /var/log/vernemq
Ports
1883  MQTT
8883  MQTT/SSL
8080  MQTT WebSockets
44053 VerneMQ Message Distribution
4369  EPMD - Erlang Port Mapper Daemon
8888  Prometheus Metrics
9100 9101 9102 9103 9104 9105 9106 9107 9108 9109  Specific Distributed Erlang Port Range
EXPOSE 1883 8883 8080 44053 4369 8888
9100 9101 9102 9103 9104 9105 9106 9107 9108 9109
VOLUME ["/vernemq/log", "/vernemq/data", "/vernemq/etc"]
HEALTHCHECK CMD vernemq ping | grep -q pong
USER vernemq
CMD ["start_vernemq"]

I'm running RPI4 on arm64 architecture so this is an important feature for me to be able to run VerneMQ in my kubernetes cluster. Has there been any progress or update made with regards to a working multi-architecture image?

I'm running RPI4 on arm64 architecture so this is an important feature for me to be able to run VerneMQ in my kubernetes cluster. Has there been any progress or update made with regards to a working multi-architecture image?

Have you been able to get it to compile on your RPI4? I'm not been able to get anything working

With the pi4 8gig versions out, I am surprised how many containers I run into that doesn't support arm64.  Any word on arm64 support?  Ill be the guy for june asking.

@cranky-coder thanks for asking. I do not currently work on ARM64 support for existing releases, but open to contributions. (my path forward is RocksDB integration to address ARM64)

Thanks you for supporting the VerneMQ project: https://github.com/sponsors/vernemq

I would be willing to play around with it.  Has anyone started playing with the Dockerfile for rocksdb+vernemq?

@cranky-coder there's no Dockerfile for RocksDB+Verne. I meant RocksDB integration as a replacement for LevelDB which creates the compile issues on ARM/Rpi/Windows.

No problem.  I found the dockerfile repo for the normal build.  I am playing with that and the dockerfile earlier in this thread.  Trying to do a build on my pi here.  Ill see what I can make of it.

Using the vernemq docker linux/amd64 image on M1 MacBook Pro, an error occured to me. the qemu stopped, core dump. Docker team says use ARM64 image. We need VerneMQ supported for ARM64.

Using the vernemq docker linux/amd64 image on M1 MacBook Pro, an error occured to me. the qemu stopped, core dump. Docker team says use ARM64 image. We need VerneMQ supported for ARM64

.

I tried to build VerneMQ from scratch in Docker. But I need to compile Erlang for Linux/ARM64 first. When building Erlang on Ubuntu 20.04/ARM64 in Docker I got the same error Signal 11 segmentation fault. Probably that's an architecture error? Someone made it? Appreciate your comments.

FYI I have arm64 images here
https://github.com/ysoftwareab/docker-vernemq/pkgs/container/docker-vernemq
based on @mgithubreq's https://github.com/vernemq/vernemq/issues/1421#issuecomment-609467559
PS: I have only quickly tested the 1.10.3 (which I need), not the newer (1.12.3)

@ioolkos Is this complete? It looks like you still only publish an amd64 image, not an arm64 image
https://hub.docker.com/r/vernemq/vernemq/tags

@SerialVelocity 1.13.0 is not yet on Dockerhub. Currently looking into the best way to build and release multiarch images, or both images (amd64 and arm64).

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

@SerialVelocity Can you let me know whether vernemq/vernemq:1.13.0 on dockerhub works for your on ARM64?

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

@ioolkos It does not:
$ kubectl logs vernemq-0
Permissions ok: Our pod vernemq-0 belongs to StatefulSet vernemq with 1 replicas
/vernemq/bin/vernemq: line 385: /vernemq/bin/../erts-<IP_ADDRESS>/bin/escript: cannot execute binary file: Exec format error
configuration error, exit
/vernemq/bin/vernemq: line 385: /vernemq/bin/../erts-<IP_ADDRESS>/bin/escript: cannot execute binary file: Exec format error

@SerialVelocity thanks for testing. Hm, ok, thanks. I don't see why not, but will try to test. The problem is that with buildx you cannot build and test local images, you have to push them to Docker.

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

@SerialVelocity oh, quick question: are you on Linux, or maybe Mac?

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

Im on vacation but its very easy to build multi container images from
Github Actions with buildx. I'll see next week if its not done ill give it
a shot
On Mon, Jun 12, 2023, 5:12 PM ioolkos @.***> wrote:

@SerialVelocity https://github.com/SerialVelocity oh, quick question:
are you on Linux, or maybe Mac?
👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker)
requires a paid subscription.
—
Reply to this email directly, view it on GitHub
https://github.com/vernemq/vernemq/issues/1421#issuecomment-1587543695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABJD6GN7DPFMKN4LVF7YG3XK4WXPANCNFSM4KQ5UA2A
.
You are receiving this because you commented.Message ID:
@.***>

Hey @codeadict, did you manage to take a look into this? (Not needed for me anymore though as I'm running it on an amd64 host now)

I'm on it but still need some coordination to make it happen

@SerialVelocity just to exclude any doubt: the 1.13.0 images on Dockerhub should now be ARM64 compatible.

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.


alertmanager can't silenced all matched alerts

What did you do?
prometheus run very well unless when I configure the alertmanager silence rules to test if I really can silenced alert, 9 alerts matched, but only 7 can be silenced(without "cache_traffic" and "nodestat_cnc_http_1") , I can't find what's wrong with my configuration
What did you expect to see?
all of the matched alerts can be silenced
What did you see instead? Under which circumstances?

Environment

System information:
Linux 3.10.0-229.el7.x86_64 x86_64

Alertmanager version:
alertmanager, version 0.14.0
build user:       root@37b6a49ebba9
build date:       20180213-08:16:42
go version:       go1.9.2

Prometheus version:
prometheus, version 2.1.0
build user:       root@6e784304d3ff
build date:       20180119-12:01:23
go version:       go1.9.2

Alertmanager configuration file:

global:
  smtp_smarthost: '***'
  smtp_from: '***'
  smtp_auth_username: '***'
  smtp_auth_password: '***'
  smtp_require_tls: false
route:
  group_by: ['group','alertname','severity']
  group_wait: 30s
  group_interval: 10m
  repeat_interval: 1h
  receiver: 'test-mails'
receivers:
- name: 'test-mails'
  email_configs:
  - to<EMAIL_ADDRESS>

Prometheus configuration file:

global:
  scrape_interval:     15s
  evaluation_interval: 1m
alerting:
  alertmanagers:
  - static_configs:
    - targets:
       - localhost:9093
rule_files:
   - "/etc/prometheus/rules/*.yml"
scrape_configs:
  - job_name: 'prometheus'
    static_configs:
      - targets: ['localhost:9090']

  - job_name: 'pushgateway'
    honor_labels: true
    scrape_interval: "60s"
    static_configs:
      - targets: ['localhost:9091']

Alerts are effectively marked as silenced at every group_interval (10m in your case). The Silence page is showing you the alerts that are going to be affected but it might not reflect the current internal state. If you wait for 10m after creating the silence, you should see all matching alerts marked as silenced.
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


Publishing fails due to publish directory tracking

The implementation of publish directory tracking causes publishing to fail because it is checking the publisherFileSystemByBranches for the src file.  This is incorrect for two reasons:

The file hasn't yet been written to the publish location
The check is using the publishFileSystem and the src file.  This is in incorrect combination.  The correct combination is publishFileSystem & dst or writerFileSystem & src

I will fix this


Custom Command errantly states that command does not start with "8"

I have the module set up and am attempting to use the custom command option. The custom command I am trying to use is 8x 01 04 35 02 FF.
The text in the field is red when setting up the command.
After testing the action, the log returns "Error, command "8x 01 04 35 02 FF" does not start with 8"
This is for version 2.4.1+4898-v2-4.1-9646192a

I'm not aware that this module sends custom commands. Are you using companion-module-sony-visca?

The custom command action has been implemented in Companion v3.0.0+5781 (beta). With this implementation you can begin the command with 80 or 81 or any valid hex command.