Please release Rails 5 version

Is this gem completely unsupported? Would be nice to get a Rails-5 ready version, there are lots of forks that do that already

thanks everyone for bugging me about this! I just merged the various efforts from @prosanelli @shanna @PikachuEXE @Fuffi @spastorino @Flarra @tomdracz on #43 #42 #36 and done some cleanup to get a green ci. It is merged on master but I haven't released a gem yet.
Problem is I don't run mandrill with any rails 5 apps yet, so my confidence this actually works is only as good as the unit-like testing. can someone does us all a favour and test this out for real and give a thumbs up/down?

I will update the gem and try it at some point, thanks a lot!

Hey there, @tardate Thanks for merges!
I've been running my fork in production (Rails 5.1) for close to two weeks and so far so good, no errors encountered.
Think we've got everything we need merged namely:

change the _filter to _action
add raise: false to callbacks
change setup in tests

If I encounter anything, I'll comment here but I think it's good to go.
One thing to note, dropping _filter callbacks meant we've dropped support for Rails below version 4. Might be worth mentioning in the readme that people still running those should use 1.4.1 version of gem

@tardate Actually looking at Gemspec, we dropped anything below Rails 5. Are there any issues with CI if we use active support >= 4 as dependency? Think that was done in one of the pull requests but has been changed since to depend on version >= 5
One way or another, we can just use current version as Rails 5 and advise users of previous ones to point gemfiles at version 1.4.1

@tomdracz thanks for the feedback, yes we can probably wind back the active support dependency, depending on when the _filter to _action change first appeared. Can anyone help with a definitive version that should be in the dependencies?
NB: I've added the comment in the readme to point non-rails 5 users to 1.4.1, I think that's fine for now. @spastorino had some suggestions for backwards compatibility on #42, but I've left that as a "todo" for anyone keen to help make that a reality.

@tardate Looks like before_action first appeared in Rails 4 so putting active support at >= 4 should work.
Think the backwards compatibility might be neat, but if we point users to 1.4.1, it should be enough. Bundler will warn about dependencies mismatch and 1.4.1 will be the only one they can use.
Actually Rails team has been discussing brining back before_filter as aliases here: https://github.com/rails/rails/issues/29030 but the consensus is that the ship has sailed. Think we should move along here also

thanks folks. I dropped the requirement back to >= 4 and published 1.5.0. Raise more issues as they arise!
$ gem list -r mandrill-rails

*** REMOTE GEMS ***

mandrill-rails (1.5.0)


New version: XK72.Charles version 4.6.7

Created by 🥟 Dumplings in workflow run #6968.

Log
Updated: 4.6.6 → 4.6.7
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

/azp run


[498] Add ADR for form objects

Context

https://trello.com/c/RQB9IgPZ/498-add-adr-re-form-objects

Changes proposed in this pull request

Add ADR for form object

Guidance to review
The ADR
Checklist

[x] Make sure all information from the Trello card is in here
[x] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

 Add ADR re: form objects


Console

make pumaLogoAscii smaller
puma_console add
summarizer cleanup

Just thinking out loud about console art, ideally the best result would be if we know the resolution of the terminal window and could scale the logo accordingly. Not sure though that it worths it. Maybe approximated size is quite a good start.
https://stackoverflow.com/a/10081642

Just thinking out loud about console art, ideally the best result would be if we know the resolution of the terminal window and could scale the logo accordingly. Not sure though that it worths it. Maybe approximated size is quite a good start.

@skyylex for that then we'll need to generate ascii by ourselves and also we'll need to generate per run, what I did now is I just generated one considering the default size of a mac os terminal 80 colums x 24 rows.
But, thanks for the suggestion, let's think of something for the future releases, but for now, I think this should be enough.


Add a module docstring

I use PkgTemplates just infrequently enough that I forget how to use it every time. This adds a shortened version of the README usage as a module docstring.

Yes, that solution works as well.


Decrement counter after removal in TileCache

Closes #5524 thanks to @gzhebrunov for pointing this out.

I'll add a unit test.

@ahocevar seems this function is not used anymore in the library?

Oh. Would be good to know since when it is unused. It seems to me that this function is important.

Unless I'm misreading things, it was not even used in 3.0.0, which means it was never used?

Can't find it used in any of the 3.x.0 releases

Ok cool, so let's get rid of it.

the function was added in #850 and removed in #1551

thanks @fredj


Not working for me

How do u install it?
i used thunderstore to install but it dont seem to work

i installed it manually first BepInEx following their "Installation (manual)" instructions (https://thunderstore.io/c/lethal-company/p/BepInEx/BepInExPack/).
ran the game once to generate configs etc.
and put the plugin in side the BepInEx/plugins/ folder.
and started the game.
In the cmd windows started besides the actual game (might need to alt+tab if game is fullscreen) you should see a line like, can you verify the plugin gets loaded correctly?
[LethalMod] Plugin LethalMod is loaded!

it did say it was loaded

it seems to work now on v0.10
was on v0.8 back then
top left had the things saying if it is on or not


[SURE-7747] Run fsck for loopdevices

In elemental-toolkit < v2 all OSes run from a loop device. The filesystem holding the loop device get a run of fsck at boot, but the filesystem inside the loop device doesn't. This turns to be problematic in case a filesystem corruption happens inside the loop device (the nested filesystem) as then there is no chance from fsck to actually catch the inconsistent state and attempt to fix it.
For toolkit v1.1.x this has a couple of challenges:

the loop device created from a read-only partition, hence the loop device is read-only, fsck can't modify it.
the loop device is created by systemd with a mount unit as RO, in order to call fsck we should create the device before hand.

For toolkit v2 on loopdevice snapshotter the state partition is not on read-only mode. In that case we could create the loop device before hand and call fsck.
For toolkit v2 on btrfs this is not an issue at all, fsck is executed at partition level and in applies to all subvolumes.

Closing it, this is already fixed by using BTRFS subvolumes instead.


File where account.lock.handler.login.fail.timeout.ratio needs to be set is not included in the doc

Suggested Labels
Affected : 5.8.0- alpha2
Severity: Major
Priority: Highest
Component: Account Locking
Type-Doc
In [1] under Lock Timeout Increment Factor details mentioned in the table (Tip section) include in which file we need to set the account.lock.handler.login.fail.timeout.ratio.
[1]. https://docs.wso2.com/display/IS580/Account+Locking+by+Failed+Login+Attempts

Fixed in versions 5.3.0 - 5.8.0 [1]
[1] https://docs.wso2.com/display/IS540/Account+Locking+by+Failed+Login+Attempts


seata2.0.0，修改数据库报错，配置没问题，用了很多办法都不行

服务器、客户端都是2.0版，SpringCloudAlibaba是2<IP_ADDRESS>，SpringCloud是2023.0.1，SpringBoot是3.2.4，完全匹配
以下是报错信息：（异常信息已加粗）
被调用的RM的报错：
Hibernate: update stock set goods_id=?,total=? where id=?
level-ERROR - 0104
java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0
level-ERROR - wait response error:null ,cost: 15003 ms,ip:<IP_ADDRESS>:8091,request:BranchRegisterRequest{xid='<IP_ADDRESS>:8091:4531141310104130350', branchType=AT, resourceId='jdbc:mysql:///alibaba', lockKey='stock:1', applicationData='{"autoCommit":false}'}
level-ERROR - Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed: org.springframework.orm.jpa.JpaSystemException: Unable to commit against JDBC Connection] with root cause
java.util.concurrent.TimeoutException: null ,cost: 15003 ms
调用者TM的报错：
2024-05-11T16:41:44.623+08:00 ERROR 12060 --- [business] [nio-8080-exec-4] i.s.c.rpc.netty.AbstractNettyRemoting    : wait response error:null ,cost: 30004 ms,ip:/<IP_ADDRESS>:8091,request:GlobalRollbackRequest{xid='<IP_ADDRESS>:8091:4531141310104130350', extraData='null'}
2024-05-11T16:41:44.625+08:00 ERROR 12060 --- [business] [nio-8080-exec-4] i.seata.tm.api.DefaultGlobalTransaction  : Failed to report global rollback [<IP_ADDRESS>:8091:4531141310104130350],Retry Countdown: 4, reason: RPC timeout
2024-05-11T16:41:44.683+08:00 ERROR 12060 --- [business] [nio-8080-exec-4] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed: feign.RetryableException: Read timed out executing PUT http://stock?goodsId=1&count=2] with root cause
java.net.SocketTimeoutException: Read timed out
服务器TC的报错：
java.lang.NoClassDefFoundError: Could not initialize class io.seata.server.cluster.raft.RaftServerFactory$SingletonHandler

https://github.com/apache/incubator-seata/issues/6445

#6445

could you tell me how to do?brother,I really can't understand what you say from it

#6445

Hey,brother,did you mean that I should use the latest version?I installed the Seata version is the latest.What should I do?I actually haven't any solution now.Please answer me.

#6445

I cant't see the version 2.1.0 anywhere for download.The latest version is still 2.0.0

#6445

I cant't see the version 2.1.0 anywhere for download.The latest version is still 2.0.0

兄弟搞清楚为什么了没，换版本确实就没问题了


it doesn't work for me

For some reason on android just nothing happens.
Only in fallback desktop browser is executed
Can anyone tell me what's going on?

@mderazon can you help please?
`
var express = require('express');
var deeplink = require('node-deeplink');
var app = express();
// mount deeplink middleware
app.get(
'/deeplink',
deeplink({
fallback: 'https://fallbacklink',
})
);
app.use(express.static('public'));
app.listen(port);
console.log('deeplink service listening on port 3000');
`
This is the code that I have.
When I open this link on android, it always goes to the fallback option, instead of the deeplink.
I have tried the deeplink by making an  tag, and that opens up the app as expected.
Can you tell what I might be missing?

@shikharsrivastava23 I found several problems myself to use this deeplink, and I found it very problematic. And I gave up using it.
But now I'm using Firebase's "Dynamic Links" which are Deeplinks, and very easy to use, and solved my problem.

@despossivel I am able to generate deep links for my app in the form myapp://category/42.

@shikharsrivastava23  I had also created a deeplink just like you, and when I saw firebase, it was much easier than I thought to adapt.
you just need to enter your firebase console first and create your dynamic link for your app
just follow here if it is RN that everything will be very clear to you
https://rnfirebase.io/dynamic-links/usage

Thanks for pointing out Firebase dynamic links @despossivel, it does look great indeed.
A lot have change in the landscape of deeplinks over the years, Apple / iOS made breaking changes multiple times and some things became just impossible with only using Javascript.
I will update the README with the recommendation to consider Firebase's solution 👍🏼


ceph-mon is failing to show the right version of osd and this can be problematic

For some unknown reason, after upgrading all ceph-osds to pacific on partner cloud, ceph-mon still says that osd's are on octopus.
E.g:
{
    "mon": {
        "ceph version 16.2.14 (238ba602515df21ea7ffc75c88db29f9e5ef12c9) pacific (stable)": 3
    },
    "mgr": {
        "ceph version 16.2.14 (238ba602515df21ea7ffc75c88db29f9e5ef12c9) pacific (stable)": 3
    },
    "osd": {
        "ceph version 15.2.17 (8a82819d84cf884bd39c17e3236e0632ac146dc4) octopus (stable)": 18
    },
    "mds": {},
    "rgw": {
        "ceph version 15.2.17 (8a82819d84cf884bd39c17e3236e0632ac146dc4) octopus (stable)": 3
    },
    "overall": {
        "ceph version 15.2.17 (8a82819d84cf884bd39c17e3236e0632ac146dc4) octopus (stable)": 21,
        "ceph version 16.2.14 (238ba602515df21ea7ffc75c88db29f9e5ef12c9) pacific (stable)": 6
    }
}

This is problematic because it pass the set_require_osd_release_option once that the  require-osd-release is also on octopusand this will let the cloud continue upgrading. I guess the right thing is to halt the execution if we see that there is more than one ceph version in the cloud.

After rebooting a ceph-osd machine (not necessary) and restarting the services using sudo systemctl restart ceph.target, ceph-osd versions got updated like in the payload:
{
    "mon": {
        "ceph version 16.2.14 (238ba602515df21ea7ffc75c88db29f9e5ef12c9) pacific (stable)": 2,
        "ceph version 16.2.15 (618f440892089921c3e944a991122ddc44e60516) pacific (stable)": 1
    },
    "mgr": {
        "ceph version 16.2.14 (238ba602515df21ea7ffc75c88db29f9e5ef12c9) pacific (stable)": 2,
        "ceph version 16.2.15 (618f440892089921c3e944a991122ddc44e60516) pacific (stable)": 1
    },
    "osd": {
        "ceph version 16.2.15 (618f440892089921c3e944a991122ddc44e60516) pacific (stable)": 18
    },
    "mds": {},
    "rgw": {
        "ceph version 15.2.17 (8a82819d84cf884bd39c17e3236e0632ac146dc4) octopus (stable)": 2,
        "ceph version 16.2.14 (238ba602515df21ea7ffc75c88db29f9e5ef12c9) pacific (stable)": 1
    },
    "overall": {
        "ceph version 15.2.17 (8a82819d84cf884bd39c17e3236e0632ac146dc4) octopus (stable)": 2,
        "ceph version 16.2.14 (238ba602515df21ea7ffc75c88db29f9e5ef12c9) pacific (stable)": 5,
        "ceph version 16.2.15 (618f440892089921c3e944a991122ddc44e60516) pacific (stable)": 20
    }
}

rgw had the same issue as osd

Hi, also was affected by this one during Octopus -> Pacific upgrade of ceph-osd during the last step of Victoria -> Wallaby upgrade. Reported ceph-osd charm LP2068151 bug also, as it is not clear why charm hasn't done any restarts.

I guess the right thing is to halt the execution if we see that there is more than one ceph version in the cloud.

I'm looking into this, and adding a pre-upgrade sanity check for this is not as simple as it seems, as there is a lot to consider:

How do we handle the case where there are multiple ceph-osd applications related?

If cou was restarted in the middle of an upgrade, one ceph-osd may be upgraded but not the other yet.

If cou was restarted in the middle of an upgrade, it's normal that there may be mismatched versions, so we'd need to compare the output from ceph-mon ceph versions with the channel and workload versions of related ceph applications.

Maybe I'm over-engineering this, but it's looking like it's going to be tricky to get it right for all cases. And if we're talking about a blocking error, then we need to get it right for all cases to avoid blocking a cloud upgrade unnecessarily.
Perhaps we can go with something much simpler:

Check for mismatched versions from ceph-mon ceph versions.
If any mismatched versions, output a warning (nonblocking) to the user with the details, recommending they only continue the upgrade if this is expected.
Do the above pre and post upgrade.

Thoughts?


Unhandled Exception: Exception: Unsupported Font: Roboto

Thanks for the awesome package.
Why does the package seek for Robot? I am on Android but not using Robot.
How can we pick a supported font? Is it possible in Export Options?
Thanks.

Hey, thanks for the feedback!
Currently the package only supports the following ExportOptions :

textFieldOptions
checkboxOptions
pageFormatOptions

Meaning only the style/decoration of TextFields  and Checkboxes can be overridden. This can be used if one desires to have these widgets in a different style in the exported PDF than in the app.
For Text widgets the TextStyle is also applied to the corresponding PDF element. If you set the fontFamily property of a Text widget's  style property to  Courier, Helvetica, Times, ZapfDingbats, or Symbol, the text element in the PDF will have said font.
There is already a feature request for custom font support https://github.com/joseph-grabinger/flutter_to_pdf/issues/46.
Regarding the Unhandled Exception: Unsupported Font: Roboto I would need a little more insight, e.g. a minimal reproduction of the bug and maybe also your flutter doctor -v output  since I wasn't able to reproduce the issue on Android when setting the fontFamily in the example.
If you are looking for additional ExportOptions for Text widgets, feel free to open a feature request for it :)


cargo-package ignores sub-directories containing Cargo.toml

Problem

I am trying to publish a crate which builds adhoc crates during run-time. For this reason, I include_dir::include_dir!("assets/libadhoc"). This assets/libadhoc/ contains a Cargo.toml which is then written to disk and modified during run-time. However, on a cargo publish this directory is not copied to target/package/, even with package.include = ["*"] in the parent Cargo.toml.
Steps

$ cargo init --bin project && cd project
$ mkdir assets
$ touch assets/Cargo.toml
$ cargo package --list
Cargo.toml
src/main.rs

Possible Solution(s)

I figure **/Cargo.toml are ignored for a reason, but this is not documented in cargo-package(1). I suggest an amend.
Further, I cannot find a way to override this behavior. I suggest making that possible. Alternatively/additionally, I suggest adding an environmental variable that points to the generated target/package/project-0.1.0/ so that I can copy the files myself.
For now, I'll rename the file to not-Cargo.toml and rename it during run-time so that I can publish my crate.
Notes
Output of cargo version: cargo 1.52.0 (69767412a 2021-04-21)

I'm having a similar problem with system-deps. My tests use a bunch of sub-directories containing a Cargo.toml which are not included in the package.
I think it's because cargo package does not recurse in dir containing a Cargo.toml. While it makes sense for the default, it should be overridable using the package.include field but it's not at the moment.

I'll close this in favor of https://github.com/rust-lang/cargo/issues/8597, as this seems a duplicate. Thank you for the input and MRE!


modified functions to have better accuracy

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

my first pull request


[SR-10174] Childen of a MemberDeclListSyntax are no longer typed

Previous ID
SR-10174

Radar
None

Original Reporter
@Jeehut

Type
Bug

Environment
Xcode 10.2, macOS 10.14.3.

Additional Detail from JIRA

Votes
0

Component/s
SwiftSyntax

Labels
Bug

Assignee
None

Priority
Medium

md5: 308b17bfa083679803f5f2d92c489f53

Issue Description:
In the Swift 4.2 release, childen of a `MemberDeclListSyntax` type were typed, thus the following code was working:
let enumCaseDeclarations: [EnumCaseDeclSyntax] = enumDeclaration.members.members.children.compactMap { $0 as? EnumCaseDeclSyntax }

But after updating to Xcode 10.2 today, which includes the Swift 5.0 release, all `children` members are of type `Syntax` and casting to `EnumCaseDeclSyntax` fails, although that's the type I'm expecting here. You can find an example Swift file being parsed here.
Why was this API changed to be less informative? And how am I supposed to cast it to the appropriate type going forward with the 5.0 release?
It would be great to get feedback soon, so I can make a Xcode 10.2 compatible release of my tool BartyCrouch. See also the appropriate line here.
Thank you for your help in advance!

Closing this issue because the issue appears to be fixed. If you don’t agree, please re-open the issue.


add readme and faq

This PR adds a basic file for frequently asked questions.

@husky-parul Would love to get your thoughts on the current format as someone who's been in this space for a while.


Wiki - URL for fork of wiki

The documented link:
https://github.com/TIBCOSoftware/tci.wiki.git
either isn't public or isn't valid.  There are numerous typo's that i'd like to fix and i'd like to augment the getting started doc to help someone as ignorant as i am to get up to speed.

Ah! Thanks for catching that one. The correct URL should have been https://github.com/TIBCOSoftware/tci-webintegrator.wiki.git (reflecting the repo name). As you're making updates please submit a pull request so one of the admins can review it.

That link doesn't work either ....
------ Original Message ------
From: "Leon Stigter"<EMAIL_ADDRESS>To: "TIBCOSoftware/tci-webintegrator"
<EMAIL_ADDRESS>Cc: "Andy Hampshire"<EMAIL_ADDRESS>"Author"
<EMAIL_ADDRESS>Sent: 01/09/2017 18:23:23
Subject: Re: [TIBCOSoftware/tci-webintegrator] Wiki - URL for fork of
wiki (#2)

Ah! Thanks for catching that one. The correct URL should have been
https://github.com/TIBCOSoftware/tci-webintegrator.wiki.git (reflecting
the repo name). As you're making updates please submit a pull request
so one of the admins can review it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TIBCOSoftware/tci-webintegrator/issues/2#issuecomment-326637755,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ02ls6BzlJwjg1z9HFFJ7nvLFszWgYYks5seD2LgaJpZM4PKHst.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/TIBCOSoftware/tci-webintegrator","title":"TIBCOSoftware/tci-webintegrator","subtitle":"GitHub
repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open
in
GitHub","url":"https://github.com/TIBCOSoftware/tci-webintegrator"}},"updates":{"snippets":[{"icon":"PERSON","message":"@retgits
in #2: Ah! Thanks for catching that one. The correct URL should have
been https://github.com/TIBCOSoftware/tci-webintegrator.wiki.git
(reflecting the repo name). As you're making updates please submit a
pull request so one of the admins can review
it."}],"action":{"name":"View
Issue","url":"https://github.com/TIBCOSoftware/tci-webintegrator/issues/2#issuecomment-326637755"}}}

Hi! Where do you see that link? The readme points to https://github.com/TIBCOSoftware/tci-webintegrator/wiki (which is the correct link), to clone and edit it you should use
git clone https://github.com/TIBCOSoftware/tci-webintegrator.wiki.git

On the bottom of the wiki page is says:
Fork it and send a pull request.
that's what you get when you click it ....  but looking at it again, i
have no idea why it's a clickable link.
The clone link [on the right] is correct  (same as your clone command)
------ Original Message ------
From: "Leon Stigter"<EMAIL_ADDRESS>To: "TIBCOSoftware/tci-webintegrator"
<EMAIL_ADDRESS>Cc: "Andy Hampshire"<EMAIL_ADDRESS>"Author"
<EMAIL_ADDRESS>Sent: 01/09/2017 20:40:26
Subject: Re: [TIBCOSoftware/tci-webintegrator] Wiki - URL for fork of
wiki (#2)

Hi! Where do you see that link? The readme points to
https://github.com/TIBCOSoftware/tci-webintegrator/wiki (which is the
correct link), to clone and edit it you should use
git clone https://github.com/TIBCOSoftware/tci-webintegrator.wiki.git
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TIBCOSoftware/tci-webintegrator/issues/2#issuecomment-326667605,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ02ltTQpCO_ElSJ6m2PPT3Ka7h2Mk3Vks5seF2pgaJpZM4PKHst.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/TIBCOSoftware/tci-webintegrator","title":"TIBCOSoftware/tci-webintegrator","subtitle":"GitHub
repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open
in
GitHub","url":"https://github.com/TIBCOSoftware/tci-webintegrator"}},"updates":{"snippets":[{"icon":"PERSON","message":"@retgits
in #2: Hi! Where do you see that link? The readme points to
https://github.com/TIBCOSoftware/tci-webintegrator/wiki (which is the
correct link), to clone and edit it you should use \r\n\r\ngit clone  https://github.com/TIBCOSoftware/tci-webintegrator.wiki.git\r\n"}],"action":{"name":"View
Issue","url":"https://github.com/TIBCOSoftware/tci-webintegrator/issues/2#issuecomment-326667605"}}}


load and updateView, there are only tilesvisited but no render data

I have one 3dtiles file, when I use cesium-native to load and updateView, there are only tilesvisited but no render data. I think this is because of the issue with ViewState. I get the transform from root tileset.json as follows.

dmat4x4((-0.890310, -0.455354, 0.000000, 0.000000), (0.188912, -0.369362, 0.909881, 0.000000), (-0.413837, 0.809136, 0.417180, 0.000000), (-2641045.873043, 5163786.710629, 2644556.901013, 1.000000))

And I get the mock camera position in ecef like this:
glm::dvec3 originEcef{-2641045.873043, 5163786.710629, 2644556.901013 };
  // // glm::dvec3 originEcef{-2646780.52544459, 5164537.68626643, 0};
  const LocalHorizontalCoordinateSystem* pCoordinateSystem = new LocalHorizontalCoordinateSystem(originEcef);
  glm::dvec3 originLocal = pCoordinateSystem->ecefPositionToLocal(originEcef);
  std::cout << "originLocal = " << originLocal.x << ":" << originLocal.y << ":" << originLocal.z << std::endl;
  glm::dvec3 cameraLocal = originLocal + glm::dvec3{0, 0, 3000 - 100 * i};
  std::cout << "cameraLocal = " << cameraLocal.x << ":" << cameraLocal.y << ":" << cameraLocal.z << std::endl;
  // glm::dvec3 cameraEcef{-2641045.873043, 5163786.710629, 2644556.901013+3000 };
  glm::dvec3 cameraEcef = pCoordinateSystem->localPositionToEcef(cameraLocal);
  std::cout << std::cout.setf(ios::fixed) << "cameraEcef = " << cameraEcef.x << ":" << cameraEcef.y << ":" << cameraEcef.z << std::endl;
  glm::dvec3 viewUp{0.0, 0.0, 1.0};
  double verticalFOV = Math::degreesToRadians(60);
  const glm::dvec2 viewPortSize{1080.0, 1080.0};
  double aspect = viewPortSize.x / viewPortSize.y;
  double horizontalFOV =
      2 * glm::atan(aspect * glm::tan(verticalFOV * 0.5));
  std::vector<ViewState> result;
  glm::dvec3 direction = glm::normalize(originEcef - cameraEcef);
  result.push_back(ViewState::create(
      cameraEcef,
      direction,
      glm::normalize(viewUp),
      viewPortSize,
      horizontalFOV,
      verticalFOV));

But the result looks strange, the printed log is as follows, please give me some guidance, thanks very much~

[2024-01-13 23:00:36.688] [info] [test_read_3dtiles2.cpp:651] Creating Cesium3DTilesSelection::Tileset DONE
update view state = 0
originLocal = 0:0:0
cameraLocal = 0:0:3000
4098cameraEcef = -2643716.804489:5162420.648693:2644556.901013
viewPosition = -2642551.000000:5165899.000000:2646305.000000
viewStates size = 1
[2024-01-13 23:00:36.689] [info] [test_read_3dtiles2.cpp:207] ViewUpdateResult:
tilesToRenderThisFrame : 1
ID error 2000 height 2
tilesVisited : 413
tilesCulled : 0
maxDepthVisited : 2
render
update view state = 1
originLocal = 0.000000:0.000000:0.000000
cameraLocal = 0.000000:0.000000:2900.000000
4102cameraEcef = -2643627.773440:5162466.184091:2644556.901013
viewPosition = -2642509.612611:5165818.092169:2646263.274625
viewStates size = 1
[2024-01-13 23:00:38.690] [info] [test_read_3dtiles2.cpp:207] ViewUpdateResult:
tilesToRenderThisFrame : 1
ID error 2000 height 2
tilesVisited : 413
tilesCulled : 0
maxDepthVisited : 2
render
update view state = 2
originLocal = 0.000000:0.000000:0.000000
cameraLocal = 0.000000:0.000000:2800.000000
4102cameraEcef = -2643538.742392:5162511.719489:2644556.901013
viewPosition = -2642468.225223:5165737.184338:2646221.549250
viewStates size = 1
[2024-01-13 23:00:40.693] [info] [test_read_3dtiles2.cpp:207] ViewUpdateResult:
tilesToRenderThisFrame : 1
ID error 2000 height 2
tilesVisited : 453
tilesCulled : 0
maxDepthVisited : 4
render
update view state = 3
originLocal = 0.000000:0.000000:0.000000
cameraLocal = 0.000000:0.000000:2700.000000
4102cameraEcef = -2643449.711344:5162557.254887:2644556.901013
viewPosition = -2642426.837834:5165656.276507:2646179.823875
viewStates size = 1
[2024-01-13 23:00:42.695] [info] [test_read_3dtiles2.cpp:207] ViewUpdateResult:
tilesToRenderThisFrame : 1
ID error 2000 height 2
tilesVisited : 453
tilesCulled : 0
maxDepthVisited : 4
render
update view state = 4
originLocal = 0.000000:0.000000:0.000000
cameraLocal = 0.000000:0.000000:2600.000000
4102cameraEcef = -2643360.680296:5162602.790284:2644556.901013
viewPosition = -2642385.450445:5165575.368676:2646138.098500
viewStates size = 1
[2024-01-13 23:00:44.698] [info] [test_read_3dtiles2.cpp:207] ViewUpdateResult:
tilesToRenderThisFrame : 1
ID error 2000 height 2
tilesVisited : 494
tilesCulled : 0
maxDepthVisited : 5
render
update view state = 5
originLocal = 0.000000:0.000000:0.000000
cameraLocal = 0.000000:0.000000:2500.000000
4102cameraEcef = -2643271.649248:5162648.325682:2644556.901013
viewPosition = -2642344.063056:5165494.460845:2646096.373125
viewStates size = 1
[2024-01-13 23:00:46.700] [info] [test_read_3dtiles2.cpp:207] ViewUpdateResult:
tilesToRenderThisFrame : 1
ID error 2000 height 2
tilesVisited : 494
tilesCulled : 0
maxDepthVisited : 5
render
update view state = 6
originLocal = 0.000000:0.000000:0.000000
cameraLocal = 0.000000:0.000000:2400.000000
4102cameraEcef = -2643182.618199:5162693.861080:2644556.901013
viewPosition = -2642302.675668:5165413.553014:2646054.647749
viewStates size = 1
[2024-01-13 23:00:48.703] [info] [test_read_3dtiles2.cpp:207] ViewUpdateResult:
tilesToRenderThisFrame : 1
ID error 2000 height 2
tilesVisited : 534
tilesCulled : 0
maxDepthVisited : 5
render
update view state = 7
originLocal = 0.000000:0.000000:0.000000
cameraLocal = 0.000000:0.000000:2300.000000
4102cameraEcef = -2643093.587151:5162739.396478:2644556.901013
viewPosition = -2642261.288279:5165332.645182:2646012.922374
viewStates size = 1
[2024-01-13 23:00:50.706] [info] [test_read_3dtiles2.cpp:207] ViewUpdateResult:
tilesToRenderThisFrame : 1
ID error 2000 height 2
tilesVisited : 533
tilesCulled : 1
maxDepthVisited : 5
render
update view state = 8
originLocal = 0.000000:0.000000:0.000000
cameraLocal = 0.000000:0.000000:2200.000000
4102cameraEcef = -2643004.556103:5162784.931876:2644556.901013
viewPosition = -2642219.900890:5165251.737351:2645971.196999
viewStates size = 1
[2024-01-13 23:00:52.709] [info] [test_read_3dtiles2.cpp:207] ViewUpdateResult:
tilesToRenderThisFrame : 1
ID error 2000 height 2
tilesVisited : 567
tilesCulled : 7
maxDepthVisited : 5
render
update view state = 9
originLocal = 0.000000:0.000000:0.000000
cameraLocal = 0.000000:0.000000:2100.000000
4102cameraEcef = -2642915.525055:5162830.467274:2644556.901013
viewPosition = -2642178.513502:5165170.829520:2645929.471624
viewStates size = 1
[2024-01-13 23:00:54.711] [info] [test_read_3dtiles2.cpp:207] ViewUpdateResult:
tilesToRenderThisFrame : 1
ID error 2000 height 2
tilesVisited : 554
tilesCulled : 22
maxDepthVisited : 5
render

Can you break it down for me? You've shared a lot of code and a lot of output, but I can't tell what the actual problem is. We have high confidence in updateView for general use-cases because it's used in all our game engine integrations. Perhaps it's useful to take a look at one of those (cesium-unreal or cesium-unity perhaps?) to see how it is meant to be used.

Can you break it down for me? You've shared a lot of code and a lot of output, but I can't tell what the actual problem is. We have high confidence in updateView for general use-cases because it's used in all our game engine integrations. Perhaps it's useful to take a look at one of those (cesium-unreal or cesium-unity perhaps?) to see how it is meant to be used.

OK，thanks for your reply. I hava tested my 3dtiles in unity3d, and it works well. I know the cesium-native lib is fine, my core problem is that there are only tilesvisited but no render data when I load and updateview data in cesium-native, the compact log message is :

[2024-01-13 23:00:50.706] [info] [test_read_3dtiles2.cpp:207] ViewUpdateResult:
tilesToRenderThisFrame : 1
ID error 2000 height 2
tilesVisited : 533
tilesCulled : 1
maxDepthVisited : 5

I suspect it's a problem with my viewstate construction, but I don't have a clear answer, so I hope you give me some guidance.

I can't debug your application for you, but as I guess: the camera parameters are probably incorrect, so the camera isn't "looking" where you think it is. Set up a similar configuration in one of the game engines, take a look at the camera parameters it passes into updateView, and compare to yours.

I can't debug your application for you, but as I guess: the camera parameters are probably incorrect, so the camera isn't "looking" where you think it is. Set up a similar configuration in one of the game engines, take a look at the camera parameters it passes into updateView, and compare to yours.

Okay, I'll try. Thanks~


Uplift direct dependencies and fixed compilation issues

May need a .d.ts file
Pushed, please take a look at this PR.

'Unit Tests' failed

'Unit Tests' failed

Fixed. Thank you


Add documentation for BatchingStrategy in vector stores

Explain the need for batching due to embedding model thresholds
Describe the BatchingStrategy interface and its purpose
Detail the default TokenCountBatchingStrategy implementation
Provide information on using and customizing batching strategies
Mention that several vector stores are pre-configured with the default strategy

Added new constructor for custom TokenCountEstimator in TokenCountBatchingStrategy and null checks in ctors
updated doc with example usage of additional constructors
merged in 4c8a6ee8b0deec797901f1164cb63dc5340f0b84


[SPARK-38901][SQL] DS V2 supports push down misc functions

What changes were proposed in this pull request?

Currently, Spark have some misc functions. Please refer
https://github.com/apache/spark/blob/2f8613f22c0750c00cf1dcfb2f31c431d8dc1be7/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/FunctionRegistry.scala#L688
These functions show below:
AES_ENCRYPT,
AES_DECRYPT,
SHA1,
SHA2,
MD5,
CRC32

Function
PostgreSQL
ClickHouse
H2
MySQL
Oracle
Redshift
Snowflake
DB2
Vertica
Exasol
SqlServer
Yellowbrick
Mariadb
Singlestore

AesEncrypt
Yes
Yes
Yes
Yes
Yes
NO
Yes
Yes
NO
NO
NO
Yes
Yes
Yes

AesDecrypt
Yes
Yes
Yes
Yes
Yes
NO
Yes
Yes
NO
NO
NO
Yes
Yes
Yes

Sha1
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Sha2
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Md5
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes

Crc32
No
Yes
No
Yes
NO
Yes
NO
Yes
NO
NO
NO
NO
NO
Yes

DS V2 should supports push down these misc functions.
Why are the changes needed?

DS V2 supports push down misc functions.
Does this PR introduce any user-facing change?

'No'.
New feature.
How was this patch tested?

New tests.

ping @huaxingao cc @cloud-fan

Can one of the admins verify this patch?

retest this please

@chenzhx Please rebase master

thanks, merging to master!

@cloud-fan @beliefer  Thank you for you review.


feat: issue58 users api 명세 작성

https://docs.github.com/ko/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue 문법을 사용해주세요


Calculate and log token usage

To track costs and token usage we should implement a feature to show the current tokens used and overall token usage after Swarm run.
https://github.com/openai/tiktoken
https://github.com/openai/openai-cookbook/blob/main/examples/How_to_count_tokens_with_tiktoken.ipynb

can be easily done using the engines. All current interactions with the apis happen over engines: swarmai/utils/ai_engines. Probably possible to introduce a global counter attribute in the swarm or the logger


unreliable channels?

Looking through the DataChannel.hpp channel types, there doesn't seem to be an unreliable option. Perhaps I am mis-understanding what webRTC means by unreliable -- is "reliable_unordered" what I am looking for? What I was expecting unreliable to be would be both unordered (of course) but also no guarantee of sending the data, whereas reliable_unordered sounds to me like it would be unordered but data would be re-sent until acknowledged on the other side (which I don't care about).

Here are the explanations from https://tools.ietf.org/html/draft-ietf-rtcweb-data-protocol-08#section-5.1.
I think the "PARTIAL_RELIABLE" ones might be the what you are looking for.
      DATA_CHANNEL_RELIABLE (0x00):  The Data Channel provides a
         reliable in-order bi-directional communication.

      DATA_CHANNEL_RELIABLE_UNORDERED (0x80):  The Data Channel provides
         a reliable unordered bi-directional communication.

      DATA_CHANNEL_PARTIAL_RELIABLE_REXMIT (0x01):  The Data Channel
         provides a partially-reliable in-order bi-directional
         communication.  User messages will not be retransmitted more
         times than specified in the Reliability Parameter.

      DATA_CHANNEL_PARTIAL_RELIABLE_REXMIT_UNORDERED (0x81):  The Data
         Channel provides a partial reliable unordered bi-directional
         communication.  User messages will not be retransmitted more
         times than specified in the Reliability Parameter.

      DATA_CHANNEL_PARTIAL_RELIABLE_TIMED (0x02):  The Data Channel
         provides a partial reliable in-order bi-directional
         communication.  User messages might not be transmitted or
         retransmitted after a specified life-time given in milliseconds
         in the Reliability Parameter.  This life-time starts
         when providing the user message to the protocol stack.

      DATA_CHANNEL_PARTIAL_RELIABLE_TIMED_UNORDERED (0x82):  The Data
         Channel provides a partial reliable unordered bi-directional
         communication.  User messages might not be transmitted or
         retransmitted after a specified life-time given in milli-
         seconds in the Reliability Parameter.  This life-time starts
         when providing the user message to the protocol stack.

Ah. I think you're right.
Still, in the WebRTC documentation and tutorials, typically the behavior of these unreliable channels is controlled by a 'maxRetries' or 'maxTimeout' style parameter. I can't seem to find where such a parameter might be set in librtcdcpp. And in the absence of a such a parameter, what would the behavior PARTIAL_RELIABLE data channels be?
In fact, scanning through the DataChannel.cpp source code, the chan_type parameter seems to be unused.

Still, in the WebRTC documentation and tutorials, typically the behavior of these unreliable channels is controlled by a 'maxRetries' or 'maxTimeout' style parameter. I can't seem to find where such a parameter might be set in librtcdcpp. And in the absence of a such a parameter, what would the behavior PARTIAL_RELIABLE data channels be?

That parameter would be the reliability parameter for which the proper API is not yet implemented in this library.

In fact, scanning through the DataChannel.cpp source code, the chan_type parameter seems to be unused.

The library does not support creating a data channel yet. I have a PR for this, but I hardcoded the RELIABLE chan_type and other params like reliability. Plus it would need more tweaks to actually make it work accordingly at the SCTP layer.

I've added the chan_type and reliability features to the API: https://github.com/chadnickbok/librtcdcpp/pull/30/commits/f20cf66815448f4068a0d00f972e7603c0f133d7


Replace every occurrence of :: in $PATH with :

See https://github.com/travis-ci/travis-ci/issues/5363

Tested here: https://staging.travis-ci.org/BanzaiMan/travis_staging_test/jobs/506080#L169


proper serialization support for LazyList and Stream

my original intention was to clone https://github.com/scala/bug/issues/10679 to this project.
after checking out the project and cloning the test I found out LazyList is not serializable at all.
is this intentional? if not will you accept a pr implementing proper serialization for LazyList avoiding the issue Stream serialization encounters (described in the linked issue).
Once fixed, re-enable the tests in test/files/run/serialize-stream.scala, test/files/jvm/serialization-new.scala, test/files/jvm/serialization.scala and run--update-check (marked with TODO-newColl).

Lukas has a few remarks on this at #541 (which I've closed as a duplicate)

Serializing unevaluated thunks is probably a bad idea but it should at least be possible to perform cycle detection so you could serialize cyclic streams but not infinite ones.

Just looking it this again. Serializing unevaluated thunks is apparently what we did in 2.12 and not such a bad idea after all. It will make streams like Stream.from(1) serializable. I can only guess what @eyalfa's plan for serialization of forced streams was but the only solution I can think of is to start with a proxy and switch back to regular serialization when you hit the unevaluated part. The downside is that this would serialize multiple copies in case of loops going back to the evaluated part (if it works at all). I'll give it a try.

@szeiger , my plans (back at the time, when I has some time) were to serialize the value if available or the closure otherwise,
this forced me to modify the LazyList class to represent the closures as ()=>A instead of =>A, at this point I hit what seemed to be a change of behavior when some of the tests started failing, funny thing was the tests didn't make sense in the first place and were actually later removed...
I can grab the leftovers of this code and push a branch so you can consider the approach, please LMK if you're interested.


[Feature]Disable Filer UI via configuration

Describe the issue
We have the Filer exposed publically and we can't require a JWT for reads due to our client's(client that reads from the Filer) limitations. This exposes all data stored in Seaweed to the public with no access control.
Expected behavior
The current behavior is expected.
Desired feature
A configuration value that allows the UI to be disabled in the same way the Volume UI can be disabled. We don't want the request for a directory's metadata/contents to be exposed either.
Let me know if you have questions!
Additional context
We have tried to block requests to the Filer that return the UI while allowing requests to media that are from our clients but we cannot block certain headers because of the nature of our client.
This is somewhat time-sensitive for our product's development.
PS. If you start working on this could you let me know? If I don't receive a response on this one soon I'll start on it myself. If you know how, but don't have the time I'd appreciate a few pointers on the implementation of this feature.

there is an existing option to make filer ui readonly.

there is an existing option to make filer ui readonly.

Is this documented somewhere? If not, where is the option located?

Ah, you said readonly. It's still exposed to the public though, which is not what we want.

See: https://github.com/seaweedfs/seaweedfs/pull/5297

@chrislusf Are you able to merge #5297? If there need to be changes made before it can be merged I'd love to know what they are.

added one comment

Merged in #5297
Thanks Chris!


NPM installation fails if not called against typescript

Bug Report

TSLint version: Irrelevant
TypeScript version: 2.1.4
Running TSLint via: npm installation
Platform: Windows
Node version: 6.5.0 LTS

TypeScript code being linted
npm install typescript -g followed by npm install tslint -g throws an error and quits despite the fact that typescript is actually greater than 2.0.0.
If called together as npm install tslint typescript -g, then all is fine.
Actual behavior
called seperately
`-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

called together
+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>
Expected behavior
+--<EMAIL_ADDRESS>

duplicate of #815


Ci: Use GitHub concurrency feature to deploy app to ECS

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Other non-breaking change (enhancement, tests, documentation, chore and the like)

And

[x] This Pull Request DOES NOT target the main (production) branch on this repository (if so it must point to a feature branch or to the develop (staging) branch).
[x] I have read the CONTRIBUTING document.
[ ] I have added/updated tests to cover my changes.
[x] All new and existing tests passed.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] There are no other open Pull Requests for the same update/change.

Changes

Add dependency to org.wcdevs.blog.cdk
Create awsdeployer submodule to hold the cloudformation instructions to deploy the app to the ECS
Update GitHub Action send the deployment signal directly to aws from the job. An if had to be added to each deploy step to not execute them if the env is not for staging or prod, there's no way to "early"-exit the job, see https://github.com/actions/runner/issues/662
Add environment and dockerImageTag as outputs from the build workflow
Use java temurin distro as it's the same used to build the docker image
Rename some steps with a better wording
Update README.md
Ignore node_modules folder

Codecov Report

Merging #91 (6ce9432) into develop (8fe4dfa) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop      #91   +/-   ##
==========================================
  Coverage      97.49%   97.49%
  Complexity       264      264
==========================================
  Files             38       38
  Lines            519      519
  Branches          32       32
==========================================
  Hits             506      506
  Misses             1        1
  Partials          12       12

Continue to review full report at Codecov.

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


Needed Solution: Majority Element-2

Link - https://leetcode.com/problems/majority-element-ii/
Preferred Languages: - C++, Java, Python, Javascript
Code along with an easy-to-understand, and proper explanation of the solution will make a valid contribution.
Instructions: -
Make a folder, and rename it to the problem's title.
Add your code file along with a markdown containing the code's explanation and problem link inside the folder.
Do add your name and Github ID at the top of the markdown and code if you wish to seek credits.

can you assign this to me?

Hi @Jimmy290901,
I am interested in this. Can you assign it to me?
Thanks


Add type signatures in support of strict type-review on example.py

This PR does not take the last step of adding the --strict flag in type review.
This PR satisfies a run of the type checker in strict mode against the script /example.py and all of the library functions that script depends on.  Additionally, all touched __init__ methods observed to not have *args & **kwargs catch-alls had those added and incorporated into super() calls (which will assist with tying to, e.g., knowledge base namespace helpers available in the ultimate parent class UcoThing).
The first patch also adjusted one class position, moving MessageThread under ObservableObject instead of UcoObject.  The third patch does the same for CaseInvestigation, entailing a few more classes.
Two effects reflected back into the example script are:

The EXIF dictionary incorporation logic needed its own keyword parameter, because the **kwargs catch-all parameter being used was an atypical usage versus the pass-through-to-superclass functionality of **kwargs.
Compilation, ContextualCompilation, and their subclasses now must be initialized with at least one object UcoObject linked in the core_objects keyword parameter.  Documentation is added to note this is to guarantee minimum cardinality constraints in the ontology are always satisfied.

Hi Alex,
I don't have any objections to approve this PR. To tell you the truth I don't well understand the reasons why you introduced the new classes Compilation , ContextualCompilation and EnclosingCompilation  to guarantee minimum cardinality constraints in the ontology. It's a rather selfish consideration but the XML parsers seem to work as usual. Thanks!

@fabrizio-turchi The reason for introducing those classes into the Python class hierarchy is that they are in the UCO ontology class hierarchy, but hadn't been implemented in the Python class hierarchy yet.  They are parent classes of case-investigation:Investigation, and seemed like more appropriate places to house some of the Python code around bundling objects.
I'm glad there was no downstream effect.  That was one of the goals of this PR.


adding events to vs-pagination on goTo(page), nextPage() & prevPage()

Is there a way to add events on vs-pagination component when we click page, next and previous buttons to be able to request api calls and refresh some table data and pagination data.
Maybe adding "this.$emit('clicked')" inside goTo(page), nextPage(), prevPage() methods on vsPagination.vue, could resolve this...

You can add a watcher on the vs-pagination v-model attribute and trigger data loads when the page changes.

Hello @Cuacha07, you can use @input to watch the page change event.
<vs-pagination
    :total="totalPages"
    :max="6"
    @input="handlePageChange"
    v-model="currentPage" />

  methods: {
    handlePageChange (page) {
      // handle the page change here!
    }
  }

input watch is not the right way, such functionality should have an event.
i'm stuck with pagination, and I think i will not use such a library in the future, as it does not implement the basic logic for such component.

any news? I did a server side pagination with this component, however the goto field does not update the value as it navigates through the pages

1st time trying Vuesax and was stuck for an hour. At least, @input method should be in the documentation.

1st time trying Vuesax and was stuck for an hour. At least, @input method should be in the documentation.


Fixed -h/--help

optimist.help() just returns the help as a string and doesn’t print it.

the travis failure isn’t my fault btw.


JBPM-5038 - DeploymentStore is not set in the DeploymentSynchronizerE…

…JBImpl if DeploymentSynchronizer is turned off
(cherry picked from commit a0764c1b351bbe532d8fab3d46830eb4e6b0bcde)

merged into 6.4.x


Fixed TmTheme scope issue for monaco-editor

Fixes issue: https://github.com/NeekSandhu/monaco-textmate/issues/5
API maintains backward compatibility. Optionally pass editor instance to
wireTmGrammars(...args, editor) to filter for appropriate token scope.
Implementation borrowed from: https://github.com/NeekSandhu/monaco-textmate/issues/5#issuecomment-496412139
Before:

After:

Thanks, @Nishkalkashyap!
The patch will be pushed in next minor release.
Please yarn add monaco-editor-textmate again to upgrade to 2.2.0
cc @CompuIves this patch implements "proper" token scope inheritance. Token will take color of its parent scope if itself doesn't have any color mapped directly.

This is really cool, thanks for the update @Nishkalkashyap! Also very cool that you made a CodeSandbox demo!


Why CTRL+ALT+I to toggle dev tools?

Shouldn't it be CTRL+SHIFT+I to reflect how one actually brings up devtools in Chrome?

Tanxxx


Add viewport meta for better UI on mobile devices

Viewport instruction will make the browser render UI elements with a natural scale.
Before this change:

After this change:

Nice, thanks.


Config inconsistency when adding an additional cluster CIDR in native routing mode

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
There is an inconsistency in available configuration options if a user wants to add an additional cluster CIDR in a certain deployment scenario.
Relevant config:
auto-direct-node-routes: "true"
ipam: cluster-pool
ipv4-native-routing-cidr: <IP_ADDRESS>/16
routing-mode: native

The cilium-operator runs with an additional --cluster-pool-ipv4-cidr=<IP_ADDRESS>/16
In this scenario, if a user needs to expand the cluster IP network space, according to the docs one should not change/grow the value of an already set CIDR, but instead add an additional one.
This works on the IPAM side, since cluster-pool-ipv4-cidr is a string slice option, however the routing side ipv4-native-routing-cidr only takes a single CIDR as string which doesn't let the user add another CIDR if it's not directly adjacent to the existing one and/or cannot be expressed as one new CIDR.
Cilium Version
v1.14.3 (including all available newer ones)
Kernel Version
Linux pool-xcp3y 6.1.0-12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.52-1 (2023-09-07) x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
v1.28.2
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Still relevant.

Appreciate if this could be triaged.

Keep alive.


[stable/prometheus-operator] NetworkTransmitErrors alert potentially too sensitive

Describe the bug
Using prometheus-operator helm installation and the following query is triggering an alarm for every node in my cluster:

It seems to suggest that there is always going to be a non-0 value returned by this query. So either there is a problem at the networking layer on all of my nodes, or alerting on > 0 might be too restrictive and not allow for a natural/minor level of network transmit errors.
I noticed that there is a node_exporter mixin as well which seems to have the following alert:
https://github.com/prometheus/node_exporter/blob/855a1f1d18b82f24c1e517da44ef36f2ffa35b19/docs/node-mixin/alerts/alerts.libsonnet#L176
Would be good to hear your view on whether we should bump > 0 to > 0.1 or > 0.5 in the query?
Version of Helm and Kubernetes:
Kubernetes: 1.10
Helm: 2.10.0
Which chart:
stable/prometheus-operator

@sdanbury, all alerts and dashboards are sourced from upstream repos and just synced into the chart. Please raise the relevant issues there. Please see this section: https://github.com/helm/charts/tree/master/stable/prometheus-operator#developing-prometheus-rules-and-grafana-dashboards

Thanks! Apologies, closing.


Try to reproduce left over data columns

In #280 I posted a comment where I saw left over data columns.  Need to try to reproduce this with an IT.

I created an IT that would recreate the problem. The IT would try to modify a few rows using lots of threads.  I found the following bugs :+1:

LoadTask and WorkTask both retry when a collision occurs.  When the code retries it creates a new TransactionImpl but does not  close the one from the previous attempt.  Not closing the TransactionImpl when retrying prevents updating state in ZK needed for GC.
  It should use its start timestamp.  This could cause deletion of notification that was not processed.
Found that when a weak notification is created, it uses the start timestamp.  Should use the commit timestamp.   This could cause notification to be deleted w/o changes made being processed.


make compatible with new return types spec

Context:
With Pennylane PR #3957: https://github.com/PennyLaneAI/pennylane/pull/3957 , the new return types system is enabled by default.
To make sure lightning works with pennylane master, we need to change the return shape from adjoint_jacobian. The return shape from execute in handled inside QubitDevice.
Description of the Change:
The changes to the source code are:

Change the output of adjoint_jacobian to match the new nested tuples specification
Change use of tape.get_parameters to eliminate deprecation warning
Remove reshape in vjp as it is no longer necessary
Wrap the vjp in a tuple if it is not already a tuple and reduction="extend" is requested.

The changes to the tests are:

change expected shape in a couple places
switch finite_diff to param_shift, as finite diff was causing errors with float32
Cast output to a numpy array from a tuple when using autograd, as autograd cannot differentiate a tuple

Benefits:
It works with PennyLane master.
Possible Drawbacks:
None
Related GitHub Issues:
None

[sc-35004]

Just a note, the broken MacOS builds are being worked on in https://github.com/PennyLaneAI/pennylane-lightning/pull/428 and I will notify here once complete and ready for review.

Note, once the PR #428 is approved, we can merge onto this PR and then go to master


[Feature Request] Piano roll akin to pxtone

I think the pianoroll interface is easier to newcomers and people coming from pxtone. Would be nice if Wavetracker would offer piano roll as an option, though obviously more convenient to use that pxtone's. For example, stuff like pitchbends could be done via adjusting a curve visually, same for stuff like effects.
This would offer user a choice between a tracker interface and piano roll, whichever works better for them.

Just some thoughts:
A tracker with a piano roll essentially has to act as a "visual editor" for the pattern data itself, and with that comes certain limitations.  Effect commands are not tied to notes directly, so you cannot easily move a note and automatically know which effects to move, not to mention that where you move the note might have no room for effects. Volume column changes can get in the way, instrument changes can get in the way.
I only know of a few trackers that have tried this. Patatracker lets you set or delete note blocks in a grid, but they cannot be directly dragged or resized. Instead, separate Note-Off markers have to be placed, just as you would in a tracker:

At the bottom, it also shows 3 rows for the instrument and two effects, directly assigned to each step. Zooming in/out is not possible with this solution.  And it only lets you see the first 32 steps, I can't even get it to scroll if the pattern has more steps, so maybe it was not finished.
There's also FMComposer (has since been discontinued/deleted from the internet), which tried this, but never fully realized it. It mostly just lets you drag notes up or down to change the pitch, and drag the start and end of each note, but it's buggy and doesn't quite act as you expect. You also can't add new notes in the 'piano roll'.
Buzz does its own thing with a vertical piano roll, but most piano rolls are expected to be horizontal, so that is still difficult to wrap your head around as a DAW user:

I'm not against the idea, but it seems like quite a project and may never be able to compete with a piano roll like Reaper or FL.

True, but Wavetracker already has a visualizer, and pianoroll is just one step from that by instead of just displaying data, allow to modify it as well (and maybe rotate it 90 degrees, but that's not really necessary).

I'm going to close this because it's way beyond the scope of what I would want WaveTracker to be. The existing piano roll visualizer doesn't display the pattern data. It only displays the output of the channels during playback. It has no concept of what waves/instrument/effects are being used at what time, all it knows is pitch and volume. While it certainly would be cool to see, making a piano roll editor would mean building a second editing interface entirely from the ground up, which is something I feel would be better as a separate project than this one.


Remove Istio specific constants (to be moved to net-istio).

Move Istio stuff to net-istio.
Unless I missed a repository, this is only used in net-istio.
Wait for corresponding net-istio PR.
/hold
/assign @tcnghia

/assign @ZhiminXiang

/lgtm
/approve

/hold cancel

@tcnghia do you know why the /lgtm and /approve of @ZhiminXiang are not adding labels?
He is in the OWNERS file.

@ZhiminXiang can you retry the command, there was a Prow issue earlier.

/lgtm
/approve

This OWNERS file is out of sync with https://github.com/knative/serving/blob/master/OWNERS_ALIASES . I've created https://github.com/knative/networking/pull/106 to sync.


[TE] Added link to help page

What's new:
Adding link to anomaly help page.

Test:
Tested Locally

Fyi @ttbach This feature lives in the legacy app (no sass, no mixin, no link-to)


Fix multiple licence warning

Codecov Report

Merging #353 (45824aa) into main (9c3242e) will decrease coverage by 0.60%.
The diff coverage is 91.47%.

@@            Coverage Diff             @@
##             main     #353      +/-   ##
==========================================
- Coverage   91.30%   90.70%   -0.61%
==========================================
  Files          17       16       -1
  Lines        1576     1581       +5
==========================================
- Hits         1439     1434       -5
- Misses        137      147      +10

Flag
Coverage Δ

unittests
90.70% <91.47%> (-0.61%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

setup.py
0.00% <0.00%> (ø)

grayskull/base/github.py
72.83% <72.83%> (ø)

grayskull/license/discovery.py
94.87% <78.12%> (-2.28%)
:arrow_down:

grayskull/strategy/abstract_strategy.py
83.33% <83.33%> (ø)

grayskull/utils.py
91.01% <88.18%> (-8.99%)
:arrow_down:

grayskull/__main__.py
95.40% <92.50%> (-2.75%)
:arrow_down:

grayskull/base/factory.py
91.17% <93.33%> (+1.17%)
:arrow_up:

grayskull/strategy/py_base.py
95.40% <95.40%> (ø)

grayskull/config.py
96.77% <96.77%> (ø)

grayskull/strategy/pypi.py
98.00% <98.00%> (ø)

... and 7 more


Mayastor is unrecoverable if etcd cluster is broken

Summary
If etcd cluster is broken, mayastor is unrecoverable since etcd is deployed without using Persistent Volumes and not part of a StatefulSet as required by Mayastor basic architecture [0]
This means that everything using mayastor is lost and needs to be redeployed.

https://mayastor.gitbook.io/introduction/basic-architecture

SQA Team has seen this error multiple times in the last days in our labs. Here's some logs, please contact the SQA Team for more details.
Layer logs: https://people.canonical.com/~mbenzan/juju-crashdump-snapped-microk8s-2023-08-06-22.44.55.tar.gz


fix(android): add buildFeatures.buildConfig for AGP8+ compatibility

Summary
Upcoming react-native 0.73+ includes android gradle plugin 8+ which needs namespace in build.gradle but also needs buildFeatures.buildConfig enabled as well for modules that use it
It is not sufficient to enable this at the top-level app build.gradle, specific modules that use it (such as those that implement new architecture, it seems) must also enable it at the module level
This change was necessary and is in-use in my work app via patch-package as I work through android-gradle-plugin 8+ issues in prep for react-native 0.73 launching for everyone
This change is not backwards compatible but I notice the namespace addition here also is not. So this will not work on android gradle plugin < 7, but neither does the namespace addition. It will work with android gradle plugin 7 though
It is similar to changes I needed to do as react-native-firebase maintainer --> https://github.com/invertase/react-native-firebase/commit/b52d0ce6723c077190618641ce0f33ced9fd4090
Test Plan
What's required for testing (prerequisites)?
With apologies, you have to alter an app that integrates this module to use android gradle plugin 8, it's difficult to do that in repos I'm proposing these changes in because bumping to android gradle plugin 8 requries a large amount of transitive dependency changes in CI
I have integrated this in an app and tested it, and done similar work as maintainer of react-native-firebase, react-native-netinfo and react-native-device-info, and I'm now pushing these out to the repos
What are the steps to reproduce (after prerequisites)?
run the build for android

Thanks for your PR! However I'm not sure I fully understand/agree with the premise. For me it works fine in a fresh react-native init 0.73 project which I assumed is using AGP8? Also the project has AGP7 support by keeping the namespace in the xml, so if we don't have to I would very much like to keep BW support for now.

It is possible that in the react-native-gradle-plugin they added some auto-magic config for gradle to enable the buildConfig option on all auto-linked modules, there was some chatter about that, thus a 0.73 clean project as released may work now
I was testing with 0.72 and AGP8 in order to fuzzbust problems prior to 0.73 release during it's rc phase and noticed this.
At this point, the patch may only be necessary for whatever niche population both stays on rn 0.72 and updates to AGP8
I think there is something to be said for a module that uses a gradle feature (buildConfig) to correctly configure itself for that feature vs relying on react-native magic, but I recognize that's a stylistic opinion and no one needs to agree with it
In particular, you are the maintainer, so obviously feel free to disagree with me and discard the PR :-). I can obviously patch-package if it's something I need and if rn73 does something that makes it work with AGP8 without the buildConfig toggle on in the local build.gradle, awesome
Either way, I continue to appreciate react-native-vector-icons and your work here. Cheers!

My project was running react-native 0.72.6 and I am upgrading to 0.73.9 AGP 8 and Gradle 8.3.
This package and some other packages started to have this issue related to buildFeatures.buildConfig, most of them applied the fix adding the buildConfig parameter, vector-icons is one of that is not yet implementing this.
For now I will patch node_modules (and it worked without any issues) but it would be extremely important to have this enabled so I or others could bump the react-native version.


Offline Plugin

This plugin would be a high level wrapper around  offline API.
More information and context in https://github.com/mapbox/mapbox-gl-native/issues/7289.

A common scenario we hear from developers is being able to automatically launch the download of a few offline regions in the background to provide pre-cached data to users early on. One possible way to facilitate this would be to create sample code that uses a new OfflineService which would be in charge of downloading regions in the background without having to show the map or other user interaction.

cc: @Guardiola31337

I have been kicking tires on an initial implementation. Focus for this version is:

Providing an easy way to download offline tiles through a foreground service.

While we could add all features mentioned in OP. I'm focussing on a minimal viable plugin and iterate on the concept with future versions. I'm trying to get a SNAPSHOT released asap with content shared in this comment.
API proposal
Foreground service

A foreground service performs some operation that is noticeable to the user. For example, an audio app would use a foreground service to play an audio track. Foreground services must display a status bar icon. Foreground services continue running even when the user isn't interacting with the app.

Using this type of service matches requirements set out in https://github.com/mapbox/mapbox-gl-native/issues/7289. This requires users to add a AndroidManifest.xml entry and will show a notification to the users while downloading.
Explicit broadcasting results/errors
One way of providing communication to developer from a Service is sending out a explicit broadcast containing information if a download has succeeded or failed. This gives the user the ability to start a download in one Android SDK lifecycle aware component and receive results in another.
Bound service status updates
While intent broadcasting is a robust way of sending out final results and errors. It does introduce some additional computational overhead which makes them less fit for notifying download status updates. For this I'm thinking about making the service boundable. This allows the user to both show download progress in a notification while showing progress in an Activity (this matches the UX that is available in Google play when you downloading an app).


limit to django <=2.2

Drops Django3.0 compatibility so that builds off master branch work.
Closed #150

Codecov Report

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

@@          Coverage Diff          @@
##           master   #152   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          17     17
  Lines         256    256
  Branches       28     28
=====================================
  Hits          256    256

Continue to review full report at Codecov.

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


Update column-formatting.md

Q
A

content fix?
no - yes?

New article?
no - yes?

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
Guidance
You can delete this section when you are submitting the pull request.

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to 'master' branch. Released documents are in live branch.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/declarative-customization/column-formatting.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Wow, no description on the changes! @ldemaris, you needs some github etiquette!

Thx Lincoln, appreciated.